1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
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
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
|
<pre>Network Working Group M. Rose
Request for Comments: 3349 Dover Beach Consulting, Inc.
BCP: 59 July 2002
Category: Best Current Practice
<span class="h1">A Transient Prefix for Identifying Profiles under Development by the</span>
<span class="h1">Working Groups of the Internet Engineering Task Force</span>
Status of this Memo
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract
As a part of their deliverables, working groups of the IETF may
develop BEEP profiles. During the development process, it is
desirable to assign a transient identifier to each profile. If the
profile is subsequently published as an RFC, then a permanent
identifier is subsequently assigned by the IANA.
<span class="grey">Rose Best Current Practice [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc3349">RFC 3349</a> Transient IDs for BEEP Profiles July 2002</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2">2</a>. Practice . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3">3</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#appendix-A">A</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#appendix-B">B</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
Author's Address . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
Full Copyright Statement . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<span class="grey">Rose Best Current Practice [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc3349">RFC 3349</a> Transient IDs for BEEP Profiles July 2002</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
Each BEEP profile [<a href="#ref-1" title=""The Blocks Extensible Exchange Protocol Core"">1</a>] is identified by a URI [<a href="#ref-2" title=""Uniform Resource Identifiers (URI): Generic Syntax"">2</a>]. The BEEP
specification uses URIs to identify a BEEP profile both:
o statically, when a profile is formally defined (<a href="./rfc3080">RFC 3080</a>'s <a href="#section-5.1">Section</a>
<a href="#section-5.1">5.1</a>); and,
o dynamically, during channel management (<a href="./rfc3080">RFC 3080</a>'s <a href="#section-2.3.1">Section 2.3.1</a>).
If the BEEP profile appears on the standards-track [<a href="#ref-3" title=""The Organizations Involved in the IETF Standards Process"">3</a>], then the IANA
is responsible for assigning the URI associated with the BEEP
profile. Otherwise, the entity specifying the BEEP profile is free
to assign a URI under its administration to the profile.
If a working group of the IETF is developing a BEEP profile, then,
during the development process, it is desirable to use a transient
identifier for the profile. Further, it is desirable that the
transient identifier be associated with the working group.
This memo defines the practice for making such an assignment. Note
that this practice does not apply to activities outside of working
groups -- anyone able to assign a URL is capable of defining a URI
for the purposes of identifying the BEEP profiles that they develop.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Practice</span>
When a working group is formed, the IETF secretariat assigns a brief
mnemonic prefix to the working group, e.g., "provreg" or "sacred".
When a working group begins development of a document which specifies
a BEEP profile, the working group chair assigns a transient
identifier of the form "<a href="http://iana.org/beep/transient/XXX/YYY">http://iana.org/beep/transient/XXX/YYY</a>" where
"XXX" is the working group's mnemonic and "YYY" is a unique string.
Although the resulting URI must conform to the URI syntax, the "YYY"
portion is otherwise arbitrary. For example, it may contain a sub-
hierarchy (e.g., "epp/1.0").
For example,
<a href="http://iana.org/beep/transient/provreg/epp/1.0">http://iana.org/beep/transient/provreg/epp/1.0</a>
<a href="http://iana.org/beep/transient/sacred/pdm">http://iana.org/beep/transient/sacred/pdm</a>
might be assigned by the chairs of the "provreg" and "sacred" working
groups, respectively.
Following this, the working group chair completes a BEEP profile
registration template, and submits this information to the IANA.
<span class="grey">Rose Best Current Practice [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc3349">RFC 3349</a> Transient IDs for BEEP Profiles July 2002</span>
Note that although the IETF hasn't established a practice with
respect to the use of capitalization in URLs employed for namespace
purposes, the W3C has a lowercase-only policy. Working group chairs
are encouraged to consider this when making assignments.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span>
This document describes an administrative convention and raises no
additional security considerations. Of course, each BEEP-based
protocol has its own set of security considerations, which should be
described in the relevant specification.
References
[<a id="ref-1">1</a>] Rose, M., "The Blocks Extensible Exchange Protocol Core", <a href="./rfc3080">RFC</a>
<a href="./rfc3080">3080</a>, March 2001.
[<a id="ref-2">2</a>] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource
Identifiers (URI): Generic Syntax", <a href="./rfc2396">RFC 2396</a>, August 1998.
[<a id="ref-3">3</a>] Hovey, R. and S. Bradner, "The Organizations Involved in the
IETF Standards Process", <a href="https://www.rfc-editor.org/bcp/bcp11">BCP 11</a>, <a href="./rfc2028">RFC 2028</a>, October 1996.
<span class="grey">Rose Best Current Practice [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc3349">RFC 3349</a> Transient IDs for BEEP Profiles July 2002</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Acknowledgements</span>
The author gratefully acknowledges the contributions of: Dan Kohn and
Bob Wyman.
<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. IANA Considerations</span>
The IANA maintains a registry of transient identifiers used for BEEP
profiles under development in the IETF, using the profile
registration template defined in Section 5.1 of [<a href="#ref-1" title=""The Blocks Extensible Exchange Protocol Core"">1</a>].
Note that unlike the registration procedures defined in <a href="#appendix-B">Appendix B</a> of
[<a href="#ref-1" title=""The Blocks Extensible Exchange Protocol Core"">1</a>], the working group chair (instead of the IESG) is responsible for
authorizing the registration.
Author's Address
Marshall T. Rose
Dover Beach Consulting, Inc.
POB 255268
Sacramento, CA 95865-5268
US
Phone: +1 916 483 8878
EMail: mrose@dbc.mtview.ca.us
<span class="grey">Rose Best Current Practice [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc3349">RFC 3349</a> Transient IDs for BEEP Profiles July 2002</span>
Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Rose Best Current Practice [Page 6]
</pre>
|
