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
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
|
<pre>Internet Engineering Task Force (IETF) D. Cridland
Request for Comments: 6075 Isode Limited
Updates: <a href="./rfc2244">2244</a> December 2010
Category: Standards Track
ISSN: 2070-1721
The Internet Assigned Number Authority (IANA) Application Configuration
Access Protocol (ACAP) Vendor Subtrees Registry
Abstract
The original Application Configuration Access Protocol (ACAP)
specification included a vendor registry now used in other protocols.
This document updates the description of this registry, removing the
need for a direct normative reference to ACAP and removing ambiguity.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6075">http://www.rfc-editor.org/info/rfc6075</a>.
Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Cridland Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6075">RFC 6075</a> ACAP Vendor Subtrees Registry December 2010</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. Conventions Used in This Document . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-3">3</a>. The Vendor Subtree Registry . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3.1">3.1</a>. Internationalization . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3.2">3.2</a>. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.3">3.3</a>. Examples . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.4">3.4</a>. Changes from <a href="./rfc2244">RFC 2244</a> . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-4">4</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-4.1">4.1</a>. Example Registration . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-6">6</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-7">7</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-7.1">7.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-7.2">7.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The [<a href="#ref-ACAP" title=""ACAP -- Application Configuration Access Protocol"">ACAP</a>] specification includes the specification and creation of
the ACAP Vendor Registry, and this registry has subsequently been
reused by several specifications, including both [<a href="#ref-ANNOTATE">ANNOTATE</a>] and
[<a href="#ref-METADATA">METADATA</a>], and is proving to be a useful mechanism for namespacing
various names to within a specific vendor's scope.
The use of textual rather than numeric identifiers for vendors
benefits engineers and operators who are diagnosing protocol problems
by allowing them some possibility of identifying the origin of a
vendor attribute without having to look it up in a registry (although
that remains a necessary fallback). As such, engineers and operators
already have to be familiar with international technical English to
diagnose textual protocol problems, the restriction to ASCII may help
and is not believed to harm that intended use. Exposure of vendor
attributes directly in end-user user interfaces was not an intended
use of the registry.
This document merely updates the registry to reduce ambiguity in the
original specification and dissociates it from the original document
in all but name, allowing easier referencing. It replaces <a href="#section-7.4">Section</a>
<a href="#section-7.4">7.4</a> and portions of <a href="#section-4">Section 4</a>, particularly <a href="#section-4.3">Section 4.3</a>, of [<a href="#ref-ACAP" title=""ACAP -- Application Configuration Access Protocol"">ACAP</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions Used in This Document</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="#ref-KEYWORDS">KEYWORDS</a>].
<span class="grey">Cridland Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6075">RFC 6075</a> ACAP Vendor Subtrees Registry December 2010</span>
The formal syntax is to be considered normative and is specified
using [<a href="#ref-ABNF" title=""Augmented BNF for Syntax Specifications: ABNF"">ABNF</a>]. Where a formal syntax and the prose are in conflict,
the formal syntax takes precedence.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. The Vendor Subtree Registry</span>
A Vendor Token is a UTF-8 string that begins with "vendor." and that
is followed by the name of the company or product. This name MUST
NOT contain any slash character, period, or the percent and asterisk
characters typically used as wildcards.
Following this may be names, separated from the Vendor Token by a
period, which need not be registered, thus forming a complete Vendor
Name.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Internationalization</span>
Vendor Tokens are able to contain any valid Unicode codepoint,
encoded as [<a href="#ref-UTF-8" title=""UTF-8, a transformation format of ISO 10646"">UTF-8</a>], except the special characters. Since the
publication of [<a href="#ref-ACAP" title=""ACAP -- Application Configuration Access Protocol"">ACAP</a>], however, concerns have been raised on the
handling and comparison of full Unicode strings; therefore, this
specification restricts the current registrations to the ASCII subset
of UTF-8.
Furthermore, characters such as ASCII control characters, most
whitespace, and quotes are likely to be confusing and have been
similarly restricted.
Therefore, this document allows only ASCII letters, digits, the
hyphen, and space to be used in registrations (the <iana-vendor-tag>
ABNF production in <a href="#section-3.2">Section 3.2</a>).
At the time of publication of this document, no existing
registrations violate the new restricted syntax on characters allowed
in registrations. [<a href="#ref-ACAP" title=""ACAP -- Application Configuration Access Protocol"">ACAP</a>] required all Vendor Tokens to be registered
with IANA, so the new restriction is not believed to introduce any
interoperability issue.
Finally, note that this document does not change the requirement on
processors to accept other non-ASCII Unicode codepoints in Vendor
Tokens (the <possible-vendor-tag> ABNF production in <a href="#section-3.2">Section 3.2</a>).
<span class="grey">Cridland Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6075">RFC 6075</a> ACAP Vendor Subtrees Registry December 2010</span>
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Formal Syntax</span>
This syntax draws upon productions found within [<a href="#ref-ABNF" title=""Augmented BNF for Syntax Specifications: ABNF"">ABNF</a>] and [<a href="#ref-UTF-8" title=""UTF-8, a transformation format of ISO 10646"">UTF-8</a>].
Productions replace those in Section 4.3 of [<a href="#ref-ACAP" title=""ACAP -- Application Configuration Access Protocol"">ACAP</a>].
vendor-name = vendor-token *("." name-component)
name-component = *(name-char / UTF8-2 / UTF8-3 / UTF8-4)
name-char = %x01-24 / %x26-29 / %x2B-2D / %x30-7F
;; ASCII-range characters not including ".",
;; "/", "%", or "*".
vendor-token = "vendor." vendor-tag
;; MUST be registered with IANA
vendor-tag = iana-vendor-tag / possible-vendor-tag
iana-vendor-tag = 1*(ALPHA / DIGIT / SP / "-")
;; This production represents
;; allowed forms for registrations
;; under the rules specified in this
;; document.
possible-vendor-tag = name-component
;; This production represents what
;; applications and specifications
;; MUST be able to accept.
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Examples</span>
A company Example, Ltd. might register the Subtree "vendor.example".
This means it may use "vendor.example", or any name at all beginning
"vendor.example.", such as "vendor.example.product".
These names might be used in several protocols, and are reserved in
all the relevant protocols, so "vendor.example" might be an ACAP
[<a href="#ref-ACAP" title=""ACAP -- Application Configuration Access Protocol"">ACAP</a>] dataset class name, and "/vendor/vendor.example" might be a
tree of IMAP ANNOTATE entries [<a href="#ref-ANNOTATE">ANNOTATE</a>].
Example, Ltd. is free to use either "vendor.example", and group
specific products under it using the relevant protocol's hierarchy --
perhaps "/shared/vendor/vendor.example/product" annotation
[<a href="#ref-ANNOTATE">ANNOTATE</a>], or using more specific names, such as "/shared/vendor/
vendor.example.product" annotation.
Note that the solidus ("/") characters in the examples above are
protocol delimiters that are themselves not part of the Vendor Token.
<span class="grey">Cridland Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6075">RFC 6075</a> ACAP Vendor Subtrees Registry December 2010</span>
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Changes from <a href="./rfc2244">RFC 2244</a></span>
This non-normative section details changes from the original
specification of the registry in <a href="./rfc2244">RFC 2244</a>.
o Vendor Tokens are restricted to ASCII for registration purposes.
o Clarifications that "vendor.<company/product name>" means
"vendor.company name" or "vendor.product name" - "vendor.company/
product" is and always has been illegal.
o Made "vendor.company" a name in its own right - <a href="./rfc2244">RFC 2244</a> only
refers to a prefix of "vendor.company.".
o Added example registration, in line with [<a href="#ref-EXAMPLES">EXAMPLES</a>].
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span>
This specification updates the IANA registry named the ACAP "Vendor
Subtrees" registry. IANA has updated the registry to point at this
document.
Vendors may reserve a portion of the ACAP namespace, which is also
used as the namespace for several other protocols, for private use.
Vendor Names are reserved for use by that company or product,
wherever used, once registered. Registration is on a first come,
first served basis. Whenever possible, private attributes and
classes should be eschewed in favour of improving interoperable
protocols.
Vendors may only use names conforming to iana-vendor-tag at the
current time; future revisions of this specification may change this.
To: iana@iana.org
Subject: Registration of ACAP Vendor Subtree
Private Prefix: vendor.name
Person and email address to contact for further information:
(company names and addresses should be included where appropriate)
<span class="grey">Cridland Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6075">RFC 6075</a> ACAP Vendor Subtrees Registry December 2010</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Example Registration</span>
IANA is requested to add the following registration, for use by
specification authors in examples, similarly to the domains specified
in [<a href="#ref-EXAMPLES">EXAMPLES</a>]:
To: iana@iana.org
Subject: Registration of ACAP Vendor Subtree
Private Prefix: vendor.example
Person and email address to contact for further information:
Dave Cridland <dave.cridland@isode.com>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
There are no known security issues with this registry. Individual
protocols using Vendor Subtree names may have security issues, and
the introduction of Unicode has, in itself, security implications --
the restriction of this is thought to mitigate these.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
Thanks must go to Chris Newman, John Myers, and the other designers
of ACAP for the initial creation of the registry. Thanks also to
Alexey Melnikov for advice on this revision.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span>
[<a id="ref-ABNF">ABNF</a>] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>, January 2008.
[<a id="ref-ACAP">ACAP</a>] Newman, C. and J. Myers, "ACAP -- Application
Configuration Access Protocol", <a href="./rfc2244">RFC 2244</a>, November 1997.
[<a id="ref-KEYWORDS">KEYWORDS</a>]
Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-UTF-8">UTF-8</a>] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, <a href="./rfc3629">RFC 3629</a>, November 2003.
<span class="grey">Cridland Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6075">RFC 6075</a> ACAP Vendor Subtrees Registry December 2010</span>
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
[<a id="ref-ANNOTATE">ANNOTATE</a>]
Daboo, C. and R. Gellens, "Internet Message Access
Protocol - ANNOTATE Extension", <a href="./rfc5257">RFC 5257</a>, June 2008.
[<a id="ref-EXAMPLES">EXAMPLES</a>]
Eastlake 3rd, D. and A. Panitz, "Reserved Top Level DNS
Names", <a href="https://www.rfc-editor.org/bcp/bcp32">BCP 32</a>, <a href="./rfc2606">RFC 2606</a>, June 1999.
[<a id="ref-METADATA">METADATA</a>]
Daboo, C., "The IMAP METADATA Extension", <a href="./rfc5464">RFC 5464</a>,
February 2009.
Author's Address
Dave Cridland
Isode Limited
5 Castle Business Village
36, Station Road
Hampton, Middlesex TW12 2BX
GB
EMail: dave.cridland@isode.com
Cridland Standards Track [Page 7]
</pre>
|
