Debian Codegraph @

rfc6924.html

raw
1 <pre>Internet Engineering Task Force (IETF) B. Leiba
2 Request for Comments: 6924 Huawei Technologies
3 Updates: <a href="./rfc2648">2648</a> April 2013
4 Category: Informational
5 ISSN: 2070-1721
6
7
8 <span class="h1">Registration of Second-Level URN Namespaces under "ietf"</span>
9
10 Abstract
11
12 <a href="./rfc2648">RFC 2648</a> defines the "ietf" URN namespace and a number of sub-
13 namespaces. <a href="./rfc3553">RFC 3553</a> defines an additional sub-namespace, "params",
14 and creates a registry to document allocations under that. But there
15 is no registry that lists, in one place, all sub-namespaces of
16 "ietf". This document creates and populates such a registry, thereby
17 changing the mechanism defined in <a href="./rfc2648">RFC 2648</a> for adding new sub-
18 namespaces of "ietf".
19
20 Status of This Memo
21
22 This document is not an Internet Standards Track specification; it is
23 published for informational purposes.
24
25 This document is a product of the Internet Engineering Task Force
26 (IETF). It represents the consensus of the IETF community. It has
27 received public review and has been approved for publication by the
28 Internet Engineering Steering Group (IESG). Not all documents
29 approved by the IESG are a candidate for any level of Internet
30 Standard; see <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
31
32 Information about the current status of this document, any errata,
33 and how to provide feedback on it may be obtained at
34 <a href="http://www.rfc-editor.org/info/rfc6924">http://www.rfc-editor.org/info/rfc6924</a>.
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Leiba Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc6924">RFC 6924</a> IETF URN Namespace Registry April 2013</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2013 IETF Trust and the persons identified as the
60 document authors. All rights reserved.
61
62 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
63 Provisions Relating to IETF Documents
64 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
65 publication of this document. Please review these documents
66 carefully, as they describe your rights and restrictions with respect
67 to this document. Code Components extracted from this document must
68 include Simplified BSD License text as described in Section 4.e of
69 the Trust Legal Provisions and are provided without warranty as
70 described in the Simplified BSD License.
71
72 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
73
74 "A URN Namespace for IETF Documents" [<a href="./rfc2648" title="&quot;A URN Namespace for IETF Documents&quot;">RFC2648</a>] defines the "ietf" URN
75 namespace and a number of sub-namespaces. "An IETF URN Sub-namespace
76 for Registered Protocol Parameters" [<a href="./rfc3553" title="&quot;An IETF URN Sub-namespace for Registered Protocol Parameters&quot;">RFC3553</a>] defines an additional
77 sub-namespace, "params", and creates a registry to document
78 allocations under that. But there is no registry that lists, in one
79 place, all sub-namespaces of "ietf". This document creates and
80 populates such a registry, thereby changing the mechanism defined in
81 <a href="./rfc2648">RFC 2648</a> for adding new sub-namespaces of "ietf".
82
83 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. IANA Considerations</span>
84
85 There is currently a top-level registry group called "IETF Protocol
86 Parameter Identifiers", which contains one registry, "IETF URN Sub-
87 namespace for Registered Protocol Parameters". IANA has taken the
88 following three actions:
89
90 Action 1: Renamed the group "IETF Protocol Parameter Identifiers",
91 giving it the new name "Uniform Resource Name (URN) Namespace for
92 IETF Use". The existing registry in that group remains, and its name
93 is unchanged. Its registration procedure has been updated to "IETF
94 Review" (formerly called "IETF Consensus").
95
96 Action 2: Added a new registry to the renamed group. The new
97 registry is called "IETF URN Sub-namespaces", and new registrations
98 will use the IETF Review policy [<a href="./rfc5226" title="">RFC5226</a>], which provides for IETF
99 consensus in order to add a new URN namespace under "ietf". The new
100 registry appears first in the group, to provide a human-friendly,
101 top-down resolution of the namespace hierarchy.
102
103
104
105
106
107
108 <span class="grey">Leiba Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc6924">RFC 6924</a> IETF URN Namespace Registry April 2013</span>
111
112
113 Action 3: Populated the new registry as follows:
114
115 IETF URN Sub-namespaces
116
117 Registration Procedures: IETF Review
118 Reference: [<a href="./rfc6924">RFC6924</a>]
119
120 Note: This is the Official Registry for sub-namespaces of the 'IETF'
121 URN Namespace.
122
123 Sub-namespace | Reference | IANA Registry Reference
124 --------------+-----------+-----------------------------------------
125 rfc | [<a href="./rfc2648" title="&quot;A URN Namespace for IETF Documents&quot;">RFC2648</a>] | none
126 fyi | [<a href="./rfc2648" title="&quot;A URN Namespace for IETF Documents&quot;">RFC2648</a>] | none
127 std | [<a href="./rfc2648" title="&quot;A URN Namespace for IETF Documents&quot;">RFC2648</a>] | none
128 bcp | [<a href="./rfc2648" title="&quot;A URN Namespace for IETF Documents&quot;">RFC2648</a>] | none
129 id | [<a href="./rfc2648" title="&quot;A URN Namespace for IETF Documents&quot;">RFC2648</a>] | none
130 mtg | [<a href="./rfc2648" title="&quot;A URN Namespace for IETF Documents&quot;">RFC2648</a>] | none
131 params | [<a href="./rfc3553" title="&quot;An IETF URN Sub-namespace for Registered Protocol Parameters&quot;">RFC3553</a>] | [http://www.iana.org/assignments/params]
132 --------------+-----------+-----------------------------------------
133
134 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span>
135
136 This is a procedural document and is entirely unrelated to security.
137
138 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Acknowledgments</span>
139
140 Alfred Hoenes noticed the absence of this registry and suggested its
141 creation.
142
143 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. References</span>
144
145 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Normative References</span>
146
147 [<a id="ref-RFC2648">RFC2648</a>] Moats, R., "A URN Namespace for IETF Documents", <a href="./rfc2648">RFC 2648</a>,
148 August 1999.
149
150 [<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
151 IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
152 May 2008.
153
154 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Informative References</span>
155
156 [<a id="ref-RFC3553">RFC3553</a>] Mealling, M., Masinter, L., Hardie, T., and G. Klyne, "An
157 IETF URN Sub-namespace for Registered Protocol
158 Parameters", <a href="https://www.rfc-editor.org/bcp/bcp73">BCP 73</a>, <a href="./rfc3553">RFC 3553</a>, June 2003.
159
160
161
162
163
164 <span class="grey">Leiba Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc6924">RFC 6924</a> IETF URN Namespace Registry April 2013</span>
167
168
169 Author's Address
170
171 Barry Leiba
172 Huawei Technologies
173
174 Phone: +1 646 827 0648
175 EMail: [email protected]
176 URI: <a href="http://internetmessagingtechnology.org/">http://internetmessagingtechnology.org/</a>
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220 Leiba Informational [Page 4]
221 </pre>