| 1 |
<pre>Internet Engineering Task Force (IETF) B. Hoeneisen |
| 2 |
Request for Comments: 6117 Ucom.ch |
| 3 |
Obsoletes: <a href="./rfc3761">3761</a> A. Mayrhofer |
| 4 |
Category: Standards Track enum.at |
| 5 |
ISSN: 2070-1721 J. Livingood |
| 6 |
Comcast |
| 7 |
March 2011 |
| 8 |
|
| 9 |
|
| 10 |
<span class="h1">IANA Registration of Enumservices:</span> |
| 11 |
<span class="h1">Guide, Template, and IANA Considerations</span> |
| 12 |
|
| 13 |
Abstract |
| 14 |
|
| 15 |
This document specifies a revision of the IANA Registration |
| 16 |
Guidelines for Enumservices, describes corresponding registration |
| 17 |
procedures, and provides a guideline for creating Enumservice |
| 18 |
Specifications. |
| 19 |
|
| 20 |
Status of This Memo |
| 21 |
|
| 22 |
This is an Internet Standards Track document. |
| 23 |
|
| 24 |
This document is a product of the Internet Engineering Task Force |
| 25 |
(IETF). It represents the consensus of the IETF community. It has |
| 26 |
received public review and has been approved for publication by the |
| 27 |
Internet Engineering Steering Group (IESG). Further information on |
| 28 |
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 29 |
|
| 30 |
Information about the current status of this document, any errata, |
| 31 |
and how to provide feedback on it may be obtained at |
| 32 |
<a href="http://www.rfc-editor.org/info/rfc6117">http://www.rfc-editor.org/info/rfc6117</a>. |
| 33 |
|
| 34 |
Copyright Notice |
| 35 |
|
| 36 |
Copyright (c) 2011 IETF Trust and the persons identified as the |
| 37 |
document authors. All rights reserved. |
| 38 |
|
| 39 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 40 |
Provisions Relating to IETF Documents |
| 41 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 42 |
publication of this document. Please review these documents |
| 43 |
carefully, as they describe your rights and restrictions with respect |
| 44 |
to this document. Code Components extracted from this document must |
| 45 |
include Simplified BSD License text as described in Section 4.e of |
| 46 |
the Trust Legal Provisions and are provided without warranty as |
| 47 |
described in the Simplified BSD License. |
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 55 |
|
| 56 |
|
| 57 |
This document may contain material from IETF Documents or IETF |
| 58 |
Contributions published or made publicly available before November |
| 59 |
10, 2008. The person(s) controlling the copyright in some of this |
| 60 |
material may not have granted the IETF Trust the right to allow |
| 61 |
modifications of such material outside the IETF Standards Process. |
| 62 |
Without obtaining an adequate license from the person(s) controlling |
| 63 |
the copyright in such materials, this document may not be modified |
| 64 |
outside the IETF Standards Process, and derivative works of it may |
| 65 |
not be created outside the IETF Standards Process, except to format |
| 66 |
it for publication as an RFC or to translate it into languages other |
| 67 |
than English. |
| 68 |
|
| 69 |
Table of Contents |
| 70 |
|
| 71 |
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 72 |
<a href="#section-2">2</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 73 |
<a href="#section-3">3</a>. Registration Requirements . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 74 |
<a href="#section-3.1">3.1</a>. Functionality Requirements . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 75 |
<a href="#section-3.2">3.2</a>. Naming Requirements . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 76 |
<a href="#section-3.3">3.3</a>. Security Requirements . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 77 |
<a href="#section-3.4">3.4</a>. Publication Requirements . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 78 |
<a href="#section-4">4</a>. Enumservice Creation Cookbook . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 79 |
<a href="#section-4.1">4.1</a>. General Enumservice Considerations . . . . . . . . . . . . <a href="#page-7">7</a> |
| 80 |
<a href="#section-4.2">4.2</a>. Classification, Type and Subtype . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 81 |
<a href="#section-4.2.1">4.2.1</a>. General Type/Subtype Considerations . . . . . . . . . <a href="#page-9">9</a> |
| 82 |
<a href="#section-4.2.2">4.2.2</a>. Protocol-Based Enumservices Class . . . . . . . . . . <a href="#page-10">10</a> |
| 83 |
<a href="#section-4.2.3">4.2.3</a>. Application-Based Enumservice Classes . . . . . . . . <a href="#page-10">10</a> |
| 84 |
<a href="#section-4.2.4">4.2.4</a>. Data Type-Based Enumservice Class . . . . . . . . . . <a href="#page-12">12</a> |
| 85 |
<a href="#section-4.2.5">4.2.5</a>. Other Enumservice . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a> |
| 86 |
<a href="#section-5">5</a>. Required Sections and Information . . . . . . . . . . . . . . <a href="#page-13">13</a> |
| 87 |
<a href="#section-5.1">5.1</a>. Introduction (REQUIRED) . . . . . . . . . . . . . . . . . <a href="#page-13">13</a> |
| 88 |
<a href="#section-5.2">5.2</a>. IANA Registration (REQUIRED) . . . . . . . . . . . . . . . <a href="#page-13">13</a> |
| 89 |
<a href="#section-5.2.1">5.2.1</a>. Enumservice Class (<class>) . . . . . . . . . . . . . <a href="#page-13">13</a> |
| 90 |
<a href="#section-5.2.2">5.2.2</a>. Enumservice Type (<type>) . . . . . . . . . . . . . . <a href="#page-14">14</a> |
| 91 |
<a href="#section-5.2.3">5.2.3</a>. Enumservice Subtype (<subtype>) . . . . . . . . . . . <a href="#page-14">14</a> |
| 92 |
<a href="#section-5.2.4">5.2.4</a>. URI Scheme(s) (<urischeme>) . . . . . . . . . . . . . <a href="#page-15">15</a> |
| 93 |
<a href="#section-5.2.5">5.2.5</a>. Functional Specification (<functionalspec>) . . . . . <a href="#page-15">15</a> |
| 94 |
<a href="#section-5.2.6">5.2.6</a>. Security Considerations (<security>) . . . . . . . . . <a href="#page-15">15</a> |
| 95 |
<a href="#section-5.2.7">5.2.7</a>. Intended Usage (<usage>) . . . . . . . . . . . . . . . <a href="#page-16">16</a> |
| 96 |
<a href="#section-5.2.8">5.2.8</a>. Enumservice Specification (<registrationdocs>) . . . . <a href="#page-16">16</a> |
| 97 |
<a href="#section-5.2.9">5.2.9</a>. Requesters (<requesters>) . . . . . . . . . . . . . . <a href="#page-17">17</a> |
| 98 |
<a href="#section-5.2.10">5.2.10</a>. Further Information (<additionalinfo>) . . . . . . . . <a href="#page-17">17</a> |
| 99 |
<a href="#section-5.3">5.3</a>. Examples (REQUIRED) . . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a> |
| 100 |
<a href="#section-5.4">5.4</a>. Implementation Recommendations / Notes (OPTIONAL) . . . . <a href="#page-18">18</a> |
| 101 |
<a href="#section-5.5">5.5</a>. DNS Considerations (REQUIRED) . . . . . . . . . . . . . . <a href="#page-18">18</a> |
| 102 |
<a href="#section-5.6">5.6</a>. Security Considerations (REQUIRED) . . . . . . . . . . . . <a href="#page-19">19</a> |
| 103 |
<a href="#section-5.7">5.7</a>. IANA Considerations (REQUIRED) . . . . . . . . . . . . . . <a href="#page-20">20</a> |
| 104 |
<a href="#section-5.8">5.8</a>. Other Sections (OPTIONAL) . . . . . . . . . . . . . . . . <a href="#page-20">20</a> |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 111 |
|
| 112 |
|
| 113 |
<a href="#section-6">6</a>. The Process of Registering New Enumservices . . . . . . . . . <a href="#page-21">21</a> |
| 114 |
<a href="#section-6.1">6.1</a>. Step 1: Read This Document in Detail . . . . . . . . . . . <a href="#page-22">22</a> |
| 115 |
<a href="#section-6.2">6.2</a>. Step 2: Write and Submit Registration Document . . . . . . <a href="#page-22">22</a> |
| 116 |
<a href="#section-6.3">6.3</a>. Step 3: Request Comments From the IETF Community . . . . . <a href="#page-23">23</a> |
| 117 |
<a href="#section-6.3.1">6.3.1</a>. Outcome 1: No Changes Needed . . . . . . . . . . . . . <a href="#page-23">23</a> |
| 118 |
6.3.2. Outcome 2: Changes, But No Further Comments |
| 119 |
Requested . . . . . . . . . . . . . . . . . . . . . . <a href="#page-23">23</a> |
| 120 |
<a href="#section-6.3.3">6.3.3</a>. Outcome 3: Changes and Further Comments Requested . . <a href="#page-23">23</a> |
| 121 |
<a href="#section-6.4">6.4</a>. Step 4: Submit Registration Document to IANA . . . . . . . <a href="#page-24">24</a> |
| 122 |
<a href="#section-6.5">6.5</a>. Step 5: Expert Review . . . . . . . . . . . . . . . . . . <a href="#page-24">24</a> |
| 123 |
6.5.1. Outcome 1: Experts Approve the Registration |
| 124 |
Document . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-25">25</a> |
| 125 |
<a href="#section-6.5.2">6.5.2</a>. Outcome 2: Changes Required . . . . . . . . . . . . . <a href="#page-25">25</a> |
| 126 |
6.5.3. Outcome 3: Experts Reject the Registration Document . 25 |
| 127 |
<a href="#section-6.6">6.6</a>. Step 6: Publication of the Registration Document . . . . . <a href="#page-25">25</a> |
| 128 |
<a href="#section-6.7">6.7</a>. Step 7: Adding Enumservice to the IANA Registry . . . . . <a href="#page-25">25</a> |
| 129 |
<a href="#section-7">7</a>. Expert Review . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-26">26</a> |
| 130 |
<a href="#section-7.1">7.1</a>. Expert Selection Process . . . . . . . . . . . . . . . . . <a href="#page-26">26</a> |
| 131 |
<a href="#section-7.2">7.2</a>. Review Guidelines . . . . . . . . . . . . . . . . . . . . <a href="#page-26">26</a> |
| 132 |
<a href="#section-7.3">7.3</a>. Appeals . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-27">27</a> |
| 133 |
<a href="#section-8">8</a>. Revision of Existing Enumservice Specifications . . . . . . . <a href="#page-27">27</a> |
| 134 |
<a href="#section-9">9</a>. Extension of Existing Enumservice Specifications . . . . . . . <a href="#page-27">27</a> |
| 135 |
<a href="#section-10">10</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-28">28</a> |
| 136 |
<a href="#section-10.1">10.1</a>. Considerations Regarding This Document . . . . . . . . . . <a href="#page-28">28</a> |
| 137 |
<a href="#section-10.2">10.2</a>. Enumservice Security Considerations Guideline . . . . . . <a href="#page-28">28</a> |
| 138 |
<a href="#section-11">11</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-28">28</a> |
| 139 |
<a href="#section-11.1">11.1</a>. Registry Update . . . . . . . . . . . . . . . . . . . . . <a href="#page-28">28</a> |
| 140 |
<a href="#section-11.2">11.2</a>. Registration Template (XML chunk) . . . . . . . . . . . . <a href="#page-28">28</a> |
| 141 |
<a href="#section-11.3">11.3</a>. Location . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-29">29</a> |
| 142 |
<a href="#section-11.4">11.4</a>. Structure . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-30">30</a> |
| 143 |
<a href="#section-11.5">11.5</a>. Expert Review Procedure . . . . . . . . . . . . . . . . . <a href="#page-30">30</a> |
| 144 |
<a href="#section-11.6">11.6</a>. Registration Procedure . . . . . . . . . . . . . . . . . . <a href="#page-30">30</a> |
| 145 |
<a href="#section-11.6.1">11.6.1</a>. Published as an RFC . . . . . . . . . . . . . . . . . <a href="#page-31">31</a> |
| 146 |
<a href="#section-11.6.2">11.6.2</a>. Published as a Non-RFC . . . . . . . . . . . . . . . . <a href="#page-31">31</a> |
| 147 |
<a href="#section-11.7">11.7</a>. Change Control . . . . . . . . . . . . . . . . . . . . . . <a href="#page-32">32</a> |
| 148 |
<a href="#section-11.8">11.8</a>. Restrictions . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-32">32</a> |
| 149 |
<a href="#section-12">12</a>. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-32">32</a> |
| 150 |
<a href="#section-13">13</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-33">33</a> |
| 151 |
<a href="#section-13.1">13.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-33">33</a> |
| 152 |
<a href="#section-13.2">13.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-34">34</a> |
| 153 |
<a href="#appendix-A">Appendix A</a>. IANA Registration Template Examples . . . . . . . . . <a href="#page-36">36</a> |
| 154 |
<a href="#appendix-B">Appendix B</a>. Changes from <a href="./rfc3761">RFC 3761</a> . . . . . . . . . . . . . . . . <a href="#page-39">39</a> |
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 170 |
|
| 171 |
E.164 Number Mapping (ENUM) [<a href="./rfc6116" title=""The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)"">RFC6116</a>] provides an identifier mapping |
| 172 |
mechanism to map E.164 numbers [<a href="#ref-ITU.E164.2005">ITU.E164.2005</a>] to Uniform Resource |
| 173 |
Identifiers (URIs) [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>] using the Domain Name System (DNS) |
| 174 |
[<a href="./rfc1035" title=""Domain names - implementation and specification"">RFC1035</a>]. One of the primary concepts of ENUM is the definition of |
| 175 |
"Enumservices", which allows for providing different URIs for |
| 176 |
different applications of said mapping mechanism. |
| 177 |
|
| 178 |
This document specifies a revision of the IANA registry for |
| 179 |
Enumservices, which was originally described in [<a href="./rfc3761" title=""The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)"">RFC3761</a>]. This |
| 180 |
document obsoletes <a href="./rfc3761#section-3">Section 3 of RFC 3761</a> while <a href="./rfc6116">RFC 6116</a> obsoletes <a href="./rfc3761">RFC</a> |
| 181 |
<a href="./rfc3761">3761</a>. |
| 182 |
|
| 183 |
The new registration processes, which are detailed in <a href="#section-6">Section 6</a>, have |
| 184 |
been specifically designed to be decoupled from the existence of the |
| 185 |
ENUM working group. Compared to <a href="./rfc3761">RFC 3761</a>, the main changes are as |
| 186 |
follows: |
| 187 |
|
| 188 |
o For an Enumservice to be inserted to the IANA registry, |
| 189 |
"Specification Required", which implies the use of a Designated |
| 190 |
Expert, according to "Guidelines for Writing an IANA |
| 191 |
Considerations Section in RFCs" [<a href="./rfc5226" title="">RFC5226</a>], are now sufficient. |
| 192 |
|
| 193 |
o The IANA Registration Template has been supplemented with elements |
| 194 |
for "Enumservice Class" and "Enumservice Specification". |
| 195 |
|
| 196 |
The IETF's ENUM Working Group has encountered an unnecessary amount |
| 197 |
of variation in the format of Enumservice Specifications. The ENUM |
| 198 |
Working Group's view of what particular information is required |
| 199 |
and/or recommended has also evolved, and capturing these best current |
| 200 |
practices is helpful in both the creation of new Enumservice |
| 201 |
Specifications, as well as the revision or refinement of existing |
| 202 |
Enumservice Specifications. |
| 203 |
|
| 204 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span> |
| 205 |
|
| 206 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 207 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 208 |
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 209 |
|
| 210 |
For the purpose of this document: |
| 211 |
|
| 212 |
o "Registration Document" refers to a draft specification that |
| 213 |
defines an Enumservice and proposes its registration following the |
| 214 |
procedures outlined herein. |
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 223 |
|
| 224 |
|
| 225 |
o "Enumservice Specification" refers to a Registration Document that |
| 226 |
has been approved by the experts and published according to |
| 227 |
"Specification Required" as defined in [<a href="./rfc5226" title="">RFC5226</a>]. |
| 228 |
|
| 229 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Registration Requirements</span> |
| 230 |
|
| 231 |
As specified in the Augmented Backus-Naur Form (ABNF, [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>]) |
| 232 |
found in <a href="./rfc6116#section-3.4.3">Section 3.4.3 of [RFC6116]</a>, an Enumservice is made up of |
| 233 |
Types and Subtypes. For any given Type, the allowable Subtypes (if |
| 234 |
any) must be defined in the Enumservice Specification. There is |
| 235 |
currently no concept of a registered Subtype outside the scope of a |
| 236 |
given Type. |
| 237 |
|
| 238 |
While the combination of each Type and all of its Subtypes |
| 239 |
constitutes the allowed values for the "Enumservice" field, it is not |
| 240 |
sufficient to just list their allowed values. To allow for |
| 241 |
interoperability, a complete Enumservice Specification MUST document |
| 242 |
the semantics of the Type and Subtype values to be registered, and |
| 243 |
MUST contain all sections listed in <a href="#section-5">Section 5</a> of this document. |
| 244 |
|
| 245 |
Furthermore, in order for an Enumservice to be registered, the entire |
| 246 |
Registration Document requires approval by the experts according to |
| 247 |
"Specification Required", which implies the use of a Designated |
| 248 |
Expert, as set out in "Guidelines for Writing an IANA Considerations |
| 249 |
Section in RFCs" [<a href="./rfc5226" title="">RFC5226</a>] and <a href="#section-7.2">Section 7.2</a> of this document. |
| 250 |
|
| 251 |
All Enumservice Specifications are expected to conform also to |
| 252 |
various requirements laid out in the following sections. |
| 253 |
|
| 254 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Functionality Requirements</span> |
| 255 |
|
| 256 |
A registered Enumservice must be able to function as a selection |
| 257 |
mechanism for choosing one Naming Authority Pointer (NAPTR) [<a href="./rfc3403" title=""Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database"">RFC3403</a>] |
| 258 |
DNS Resource Record (RR) from a set of such RRs. That means the |
| 259 |
Enumservice Specification MUST define how to use the NAPTR RR and the |
| 260 |
URI(s) the NAPTR RR resolves to. |
| 261 |
|
| 262 |
Specifically, a registered Enumservice MUST specify the URI Scheme(s) |
| 263 |
that may be used for the Enumservice, and, when needed, other |
| 264 |
information that will have to be transferred into the URI resolution |
| 265 |
process itself. |
| 266 |
|
| 267 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Naming Requirements</span> |
| 268 |
|
| 269 |
The name of an Enumservice MUST be unique in order to be useful as a |
| 270 |
selection criteria: |
| 271 |
|
| 272 |
o The Type MUST be unique. |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 279 |
|
| 280 |
|
| 281 |
o The Subtype (being dependent on the Type) MUST be unique within a |
| 282 |
given Type. |
| 283 |
|
| 284 |
Types and Subtypes MUST conform to the ABNF specified in <a href="./rfc6116#section-3.4.3">Section</a> |
| 285 |
<a href="./rfc6116#section-3.4.3">3.4.3 of [RFC6116]</a>. |
| 286 |
|
| 287 |
The ABNF specified in <a href="./rfc6116#section-3.4.3">Section 3.4.3 of [RFC6116]</a> allows the "-" |
| 288 |
(dash) character for Types and Subtypes. To avoid confusion with |
| 289 |
possible future prefixes, a "-" MUST NOT be used as the first nor as |
| 290 |
the second character of a Type nor a Subtype. Furthermore, a "-" |
| 291 |
MUST NOT be used as the last character of a Type nor a Subtype. In |
| 292 |
addition, Types and Subtypes are case insensitive and SHOULD be |
| 293 |
specified in lowercase letters. |
| 294 |
|
| 295 |
Note: The legacy IANA registry of Enumservices contains Type and |
| 296 |
Subtype strings with uppercase letters. Implementors could be |
| 297 |
tempted to refuse handling uppercase Type or Subtype strings, which |
| 298 |
could negatively affect interoperability. |
| 299 |
|
| 300 |
To avoid confusion with Enumservice fields using a deprecated |
| 301 |
(obsolete) syntax, Type and Subtype MUST NOT start with the string |
| 302 |
"e2u". |
| 303 |
|
| 304 |
The Subtype for one Type MAY have the same identifier as a Subtype |
| 305 |
for another Type, but it is not sufficient to simply reference |
| 306 |
another Type's Subtype. The functionality of each Subtype MUST be |
| 307 |
fully specified in the context of the Type being registered. |
| 308 |
|
| 309 |
<a href="#section-4">Section 4</a> contains further naming requirements. |
| 310 |
|
| 311 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Security Requirements</span> |
| 312 |
|
| 313 |
An analysis of security issues is REQUIRED for all registered |
| 314 |
Enumservices. (This is in accordance with the basic requirements for |
| 315 |
all IETF protocols.) |
| 316 |
|
| 317 |
All descriptions of security issues MUST be as accurate and extensive |
| 318 |
as feasible. In particular, a statement that there are "no security |
| 319 |
issues associated with this Enumservice" must not be confused with |
| 320 |
"the security issues associated with this Enumservice have not been |
| 321 |
assessed". |
| 322 |
|
| 323 |
There is no requirement that an Enumservice must be completely free |
| 324 |
of security risks. Nevertheless, all known security risks MUST be |
| 325 |
identified in an Enumservice Specification. |
| 326 |
|
| 327 |
Some of the issues to be looked at in a security analysis of an |
| 328 |
Enumservice are: |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 335 |
|
| 336 |
|
| 337 |
1. Complex Enumservices may include provisions for directives that |
| 338 |
institute actions on a user's resources. In many cases provision |
| 339 |
can be made to specify arbitrary actions in an unrestricted |
| 340 |
fashion which may then have devastating results (especially if |
| 341 |
there is a risk for a new ENUM look-up, and because of that an |
| 342 |
infinite loop in the overall resolution process of the E.164 |
| 343 |
number). |
| 344 |
|
| 345 |
2. Complex Enumservices may include provisions for directives that |
| 346 |
institute actions which, while not directly harmful, may result |
| 347 |
in disclosure of information that either facilitates a subsequent |
| 348 |
attack or else violates the users' privacy in some way. |
| 349 |
|
| 350 |
3. An Enumservice might be targeted for applications that require |
| 351 |
some sort of security assurance but do not provide the necessary |
| 352 |
security mechanisms themselves. For example, an Enumservice |
| 353 |
could be defined for storage of confidential security services |
| 354 |
information such as alarm systems or message service passcodes, |
| 355 |
which in turn require an external confidentiality service. |
| 356 |
|
| 357 |
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Publication Requirements</span> |
| 358 |
|
| 359 |
Enumservices Specifications MUST be published according to the |
| 360 |
requirements for "Specification Required" set out in "Guidelines for |
| 361 |
Writing an IANA Considerations Section in RFCs" [<a href="./rfc5226" title="">RFC5226</a>]. RFCs |
| 362 |
fulfill these requirements. Therefore, it is strongly RECOMMENDED to |
| 363 |
publish Enumservice Specifications as RFCs. |
| 364 |
|
| 365 |
In case the Enumservice Specification is not published as an RFC, |
| 366 |
sufficient information that allows unique identification of the |
| 367 |
Enumservice Specification MUST be provided. |
| 368 |
|
| 369 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Enumservice Creation Cookbook</span> |
| 370 |
|
| 371 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. General Enumservice Considerations</span> |
| 372 |
|
| 373 |
ENUM is an extremely flexible identifier mapping mechanism, using |
| 374 |
E.164 (phone) numbers as input identifiers, and returning URIs as |
| 375 |
output identifiers. Because of this flexibility, almost every use |
| 376 |
case for ENUM could be implemented in several ways. |
| 377 |
|
| 378 |
<a href="#section-2">Section 2</a> of "Guidelines for Writing an IANA Considerations Section |
| 379 |
in RFCs" [<a href="./rfc5226" title="">RFC5226</a>] provides motivation for why management of a |
| 380 |
namespace might be necessary. Even though the namespace for |
| 381 |
Enumservices is rather large (up to 32 alphanumeric characters), |
| 382 |
there are reasons to manage this in accordance with <a href="./rfc5226#section-2">Section 2 of |
| 383 |
[RFC5226]</a>. The following is a list of motivations applying to |
| 384 |
Enumservices: |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 391 |
|
| 392 |
|
| 393 |
o Prevent hoarding or wasting of values: Enumservice Types are not |
| 394 |
an opaque identifier to prevent collisions in the namespace, but |
| 395 |
rather identify the use of a certain technology in the context of |
| 396 |
ENUM. Service Types might also be displayed to end users in |
| 397 |
implementations, so meaningful Type strings having a clear |
| 398 |
relation to the protocols and applications used are strongly |
| 399 |
RECOMMENDED. Therefore, preventing hoarding, wasting, or |
| 400 |
"hijacking" of Enumservice Type strings is important. |
| 401 |
|
| 402 |
o Sanity check to ensure sensible or necessary requests: This |
| 403 |
applies to Enumservices, since especially various Enumservices for |
| 404 |
the same purpose would reduce the chance of successful |
| 405 |
interoperability, and unnecessarily increase confusion among |
| 406 |
implementers. |
| 407 |
|
| 408 |
o Delegation of namespace portions: Theoretically, the Type and/or |
| 409 |
Subtype structure of Enumservices would allow for delegations of |
| 410 |
Type values, and self-supporting management of Subtype values by a |
| 411 |
delegate within the Type value. Such delegates could, for |
| 412 |
example, be other standardization bodies. However, this would |
| 413 |
require clear policies regarding publication and use of such |
| 414 |
Subtypes. Delegation of Enumservice namespace portions is |
| 415 |
therefore currently not supported. |
| 416 |
|
| 417 |
o Interoperability: Since the benefit of an Enumservice rises with |
| 418 |
the number of supporting clients, the registration and use of |
| 419 |
several services for a similar or identical purpose clearly |
| 420 |
reduces interoperability. Operational circumstances suggest to |
| 421 |
keep the space occupied by all services published in the NAPTR |
| 422 |
RRSet at any owner in the e164.arpa domain bounded. Registration |
| 423 |
of nearly identical services and subsequent competing or parallel |
| 424 |
use could easily increase the DNS operational complexity. |
| 425 |
|
| 426 |
Generally, before commencing work on a new Enumservice registration, |
| 427 |
the following should be considered: |
| 428 |
|
| 429 |
o Is there an existing Enumservice that could fulfill the desired |
| 430 |
functionality without overloading it? Check the IANA Enumservice |
| 431 |
Registry at <<a href="http://www.iana.org/assignments/enum-services">http://www.iana.org/assignments/enum-services</a>>. |
| 432 |
|
| 433 |
o Is there work in progress, or previous work, on a similar |
| 434 |
Enumservice? Check the <[email protected]> mailing list archives at |
| 435 |
<<a href="http://www.ietf.org/mail-archive/web/enum/index.html">http://www.ietf.org/mail-archive/web/enum/index.html</a>>, and search |
| 436 |
the Internet-Drafts Archive at <<a href="http://tools.ietf.org/">http://tools.ietf.org/</a>>. Some |
| 437 |
Internet-Drafts may have expired and no longer be available in the |
| 438 |
Internet-Drafts Archive, or some work on Enumservices may have |
| 439 |
been considered outside the IETF; therefore, we also recommend a |
| 440 |
web search. |
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 447 |
|
| 448 |
|
| 449 |
o <a href="#section-4.2">Section 4.2</a> provides three general categories for Enumservice |
| 450 |
classification. In some cases, there might be several options for |
| 451 |
designing an Enumservice. For example, a mapping service using |
| 452 |
HTTP could be considered a "protocol Type" Enumservice (using HTTP |
| 453 |
as the protocol), while it could also be viewed as an "application |
| 454 |
Type" Enumservice, with the application providing access to |
| 455 |
mapping services. In such a case where several options are |
| 456 |
available, defining use cases before commencing work on the |
| 457 |
Enumservice itself might be useful before making a decision on |
| 458 |
which aspect of the Enumservice is more important. |
| 459 |
|
| 460 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Classification, Type and Subtype</span> |
| 461 |
|
| 462 |
Because of their flexibility, Enumservices can be and are used in a |
| 463 |
lot of different ways. This section contains a classification of |
| 464 |
Enumservices, and provides guidance for choosing suitable Type and |
| 465 |
Subtype strings for each individual Enumservice Class. |
| 466 |
|
| 467 |
The Classification of each Enumservice MUST be listed in the |
| 468 |
Registration Document (see <a href="#section-5.2">Section 5.2</a>). If the Enumservice cannot |
| 469 |
be assigned to one of the classes outlined below, the Registration |
| 470 |
Document MUST contain a section on the difficulties encountered while |
| 471 |
trying to classify the service to help the experts in their decision. |
| 472 |
|
| 473 |
<span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a>. General Type/Subtype Considerations</span> |
| 474 |
|
| 475 |
To avoid confusion, the name of a URI Scheme MUST NOT be used as a |
| 476 |
Type string for an Enumservice that is not specifically about the |
| 477 |
respective protocol or URI Scheme. For example, the Type string |
| 478 |
"imap" would be inadequate for use in an Enumservice about "Internet |
| 479 |
mapping" services, because it corresponds to an existing URI Scheme / |
| 480 |
protocol for something different. |
| 481 |
|
| 482 |
If Subtypes are defined, the minimum number SHOULD be two (including |
| 483 |
the empty Subtype, if defined). The choice of just one possible |
| 484 |
Subtype for a given Type does not add any information when selecting |
| 485 |
an ENUM record, and hence can be left out completely. However, |
| 486 |
potential future expansion of a Type towards several Subtypes may |
| 487 |
justify the use of Subtypes, even in the case that just one is |
| 488 |
currently defined, as noted in <a href="#section-9">Section 9</a>. |
| 489 |
|
| 490 |
It is perfectly legal under a certain Type to mix the Enumservice |
| 491 |
without a Subtype (empty Subtype) with Enumservices containing a |
| 492 |
Subtype. In that case, however, the Enumservice with an empty |
| 493 |
Subtype SHOULD be specified to reflect the base service, while the |
| 494 |
other Enumservices SHOULD be specified to reflect variants. |
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 503 |
|
| 504 |
|
| 505 |
<span class="h4"><a class="selflink" id="section-4.2.2" href="#section-4.2.2">4.2.2</a>. Protocol-Based Enumservices Class</span> |
| 506 |
|
| 507 |
Such an Enumservice indicates that an interaction using the named |
| 508 |
protocol will result for use of this NAPTR. The expected behavior of |
| 509 |
a system using this Enumservice MUST be clear from the protocol. |
| 510 |
|
| 511 |
A good indication that an Enumservice belongs to this Class is the |
| 512 |
fact that a client does not need to understand the actual application |
| 513 |
to make use of an instance of this Enumservice. |
| 514 |
|
| 515 |
Examples of such Enumservices include "xmpp" [<a href="./rfc4979" title=""IANA Registration for Enumservice 'XMPP'"">RFC4979</a>] and "sip" |
| 516 |
[<a href="./rfc3764" title=""enumservice registration for Session Initiation Protocol (SIP) Addresses-of-Record"">RFC3764</a>]. |
| 517 |
|
| 518 |
<span class="h5"><a class="selflink" id="section-4.2.2.1" href="#section-4.2.2.1">4.2.2.1</a>. Protocol-Based Enumservice "Type" Strings</span> |
| 519 |
|
| 520 |
A protocol-based Enumservice SHOULD use the lowercase name of the |
| 521 |
protocol as its Type string. Names as registered in the IANA Port |
| 522 |
Number Registry (<<a href="http://www.iana.org/assignments/port-numbers">http://www.iana.org/assignments/port-numbers</a>>, |
| 523 |
defined in <a href="#section-8">Section 8</a> and 9 of [<a href="./rfc2780" title=""IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers"">RFC2780</a>]) are preferred. |
| 524 |
|
| 525 |
<span class="h5"><a class="selflink" id="section-4.2.2.2" href="#section-4.2.2.2">4.2.2.2</a>. Protocol-Based Enumservice "Subtype" Strings</span> |
| 526 |
|
| 527 |
Where there is a single URI Scheme associated with this protocol, a |
| 528 |
Subtype SHOULD NOT be specified for the Enumservice. |
| 529 |
|
| 530 |
Where there are a number of different URI Schemes associated with |
| 531 |
this protocol, the Enumservice Specification MAY use the empty |
| 532 |
Subtype for all URI Schemes that it specifies as mandatory to |
| 533 |
implement. For each URI Scheme that is not mandatory to implement, a |
| 534 |
distinct Subtype string MUST be used. |
| 535 |
|
| 536 |
If Subtypes are defined, it is RECOMMENDED to use the URI Scheme name |
| 537 |
as the Subtype string. |
| 538 |
|
| 539 |
<span class="h4"><a class="selflink" id="section-4.2.3" href="#section-4.2.3">4.2.3</a>. Application-Based Enumservice Classes</span> |
| 540 |
|
| 541 |
Application-based Enumservices are used when the kind of service |
| 542 |
intended is not fully defined by a protocol specification. There are |
| 543 |
three cases here: |
| 544 |
|
| 545 |
o Common Application Enumservice: |
| 546 |
|
| 547 |
The application reflects a kind of interaction that can be |
| 548 |
realized by different protocols, but where the intent of the |
| 549 |
publisher is the same. From a user's perspective, there is a |
| 550 |
common kind of interaction -- how that interaction is implemented |
| 551 |
is not important. The Enumservice Specification MUST describe the |
| 552 |
interaction and expected behavior in enough detail that an |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 559 |
|
| 560 |
|
| 561 |
implementation can decide if this activity is one in which it can |
| 562 |
engage. However, it is RECOMMENDED that the Enumservice be |
| 563 |
defined in a way that will allow others to use it at a later date. |
| 564 |
An Enumservice that defines a generalized application is preferred |
| 565 |
to one that has narrow use. |
| 566 |
|
| 567 |
An example of this flavor of Enumservice is email. Whilst this |
| 568 |
might appear to be a "pure" protocol scheme, it is not. The URI |
| 569 |
Scheme is 'mailto', and it does not identify the protocol used to |
| 570 |
offer or retrieve emails by the sender or the recipient. |
| 571 |
|
| 572 |
Another example is the Short Messaging Service (SMS), where the |
| 573 |
existence of such an Enumservice indicates that the publishing |
| 574 |
entity is capable of engaging in sending or receiving a message |
| 575 |
according to the SMS specifications. The underlying protocol used |
| 576 |
and the URI Scheme for the addressable end point can differ, but |
| 577 |
the "user visible" interaction of sending and receiving an SMS is |
| 578 |
similar. |
| 579 |
|
| 580 |
o Subset Enumservice: |
| 581 |
|
| 582 |
The application interaction reflects a subset of the interactions |
| 583 |
possible by use of a protocol. Use of this Enumservice indicates |
| 584 |
that some options available by use of the protocol will not be |
| 585 |
accepted or are not possible in this case. Any such Enumservice |
| 586 |
Specification MUST define the options available by use of this |
| 587 |
NAPTR in enough detail that an implementation can decide whether |
| 588 |
or not it can use this Enumservice. Examples of this kind of |
| 589 |
Enumservice are "voice:tel" and "fax:tel". In both cases, the URI |
| 590 |
holds a telephone number. However, the essential feature of these |
| 591 |
Enumservices is that the telephone number is capable of receiving |
| 592 |
a voice call or of receiving a Facsimile transmission, |
| 593 |
respectively. These form subsets of the interactions capable of |
| 594 |
using the telephone number, and so have their own Enumservices. |
| 595 |
These allow an end point to decide if it has the appropriate |
| 596 |
capability to engage in the advertised user service (a voice call |
| 597 |
or sending a fax) rather than just being capable of making a |
| 598 |
connection to such a destination address. This is especially |
| 599 |
important where there is no underlying mechanism within the |
| 600 |
protocol to negotiate a different kind of user interaction. |
| 601 |
|
| 602 |
o Ancillary Application Enumservice |
| 603 |
|
| 604 |
Another variant on this is the Ancillary Application. This is one |
| 605 |
in which further processing (potentially using a number of |
| 606 |
different protocols or methods) is the intended result of using |
| 607 |
this Enumservice. An example of this kind of application is the |
| 608 |
"pstn:tel" Enumservice. This indicates that the NAPTR holds |
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 615 |
|
| 616 |
|
| 617 |
number portability data. It implies that the client should engage |
| 618 |
in number portability processing using the associated URI. Note |
| 619 |
that this Enumservice usually does not itself define the kind of |
| 620 |
interaction available using the associated URI. That application |
| 621 |
is negotiated with some other "out of band" means (either through |
| 622 |
prior negotiation, or explicitly through the number portability |
| 623 |
process, or through negotiation following the selection of the |
| 624 |
final destination address). |
| 625 |
|
| 626 |
<span class="h5"><a class="selflink" id="section-4.2.3.1" href="#section-4.2.3.1">4.2.3.1</a>. Application-Based Enumservice "Type" Strings</span> |
| 627 |
|
| 628 |
It is recommended that Application-class Enumservices use the |
| 629 |
lowercase well-known name of the abstract application as the Type |
| 630 |
string. |
| 631 |
|
| 632 |
<span class="h5"><a class="selflink" id="section-4.2.3.2" href="#section-4.2.3.2">4.2.3.2</a>. Application-Based Enumservice "Subtype" Strings</span> |
| 633 |
|
| 634 |
It is RECOMMENDED that the URI Scheme(s) used by the application be |
| 635 |
used as the Subtype string(s). Subtype strings MAY be shared between |
| 636 |
URI Schemes, if all the URI Schemes within the same Subtype are |
| 637 |
mandatory to implement. |
| 638 |
|
| 639 |
If it is foreseen that there is only one URI Scheme ever to be used |
| 640 |
with the application, the empty Subtype string MAY be used. |
| 641 |
|
| 642 |
<span class="h4"><a class="selflink" id="section-4.2.4" href="#section-4.2.4">4.2.4</a>. Data Type-Based Enumservice Class</span> |
| 643 |
|
| 644 |
"Data Type" Enumservices typically refer to a specific data type or |
| 645 |
format, which may be addressed using one or more URI Schemes and |
| 646 |
protocols. Examples of such Enumservices include "vpim" [<a href="./rfc4238" title=""Voice Message Routing Service"">RFC4238</a>] |
| 647 |
and "vcard" [<a href="./rfc4969" title=""IANA Registration for vCard Enumservice"">RFC4969</a>]. |
| 648 |
|
| 649 |
<span class="h5"><a class="selflink" id="section-4.2.4.1" href="#section-4.2.4.1">4.2.4.1</a>. Data Type-Based Enumservice "Type" Strings</span> |
| 650 |
|
| 651 |
It is recommended to use the lowercase well known name of the data |
| 652 |
type or format name as the Type string. |
| 653 |
|
| 654 |
<span class="h5"><a class="selflink" id="section-4.2.4.2" href="#section-4.2.4.2">4.2.4.2</a>. Data Type-Based Enumservice "Subtype" Strings</span> |
| 655 |
|
| 656 |
It is RECOMMENDED to use the URI Schemes used to access the service |
| 657 |
as Subtype strings. Subtype strings MAY be shared between URI |
| 658 |
Schemes, if all the URI Schemes within the same Subtype are mandatory |
| 659 |
to implement. |
| 660 |
|
| 661 |
If there is only one URI Scheme foreseen to access the data type or |
| 662 |
format, the empty Subtype string MAY be used. |
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 671 |
|
| 672 |
|
| 673 |
<span class="h4"><a class="selflink" id="section-4.2.5" href="#section-4.2.5">4.2.5</a>. Other Enumservice</span> |
| 674 |
|
| 675 |
In case an Enumservice proposal cannot be assigned to any of the |
| 676 |
classes mentioned above, the <class> element (Enumservice Class) in |
| 677 |
the IANA Registration Template (see <a href="#section-5.2">Section 5.2</a>) MUST be populated |
| 678 |
with "Other". In that case, the Enumservice Specification MUST |
| 679 |
contain a section elaborating on why the Enumservice does not fit |
| 680 |
into the classification structure. |
| 681 |
|
| 682 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Required Sections and Information</span> |
| 683 |
|
| 684 |
There are several sections that MUST appear in an Enumservice |
| 685 |
Specification. These sections are as follows, and they SHOULD be in |
| 686 |
the given order. |
| 687 |
|
| 688 |
The following terms SHOULD begin with a capital letter, whenever they |
| 689 |
refer to the IANA Registration: |
| 690 |
o Class |
| 691 |
o Type |
| 692 |
o Subtype |
| 693 |
o URI Scheme |
| 694 |
|
| 695 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Introduction (REQUIRED)</span> |
| 696 |
|
| 697 |
An introductory section MUST be included. This section will explain, |
| 698 |
in plain English, the purpose and intended use of the proposed |
| 699 |
Enumservice registration. |
| 700 |
|
| 701 |
The Introduction SHOULD start with a short sentence about ENUM, |
| 702 |
introduce the protocol used in the Enumservice, and discuss the |
| 703 |
Enumservice as it refers from the E.164 number to the protocol or |
| 704 |
service. |
| 705 |
|
| 706 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. IANA Registration (REQUIRED)</span> |
| 707 |
|
| 708 |
This section MUST be included in an Enumservice Specification. Where |
| 709 |
a given Enumservice Type has multiple Subtypes, there MUST be a |
| 710 |
separate "IANA Registration" section for each Subtype. The following |
| 711 |
sections list the elements that are to be used in the XML-chunk-based |
| 712 |
Registration Template of an "IANA Registration" section. |
| 713 |
|
| 714 |
<span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>. Enumservice Class (<class>)</span> |
| 715 |
|
| 716 |
This element contains the Class of the Enumservice as defined in |
| 717 |
<a href="#section-4.2">Section 4.2</a>. Its value MUST be one of (without quotes): |
| 718 |
|
| 719 |
o "Protocol-Based": The Enumservice belongs to the Protocol-based |
| 720 |
class as described in <a href="#section-4.2.2">Section 4.2.2</a>. |
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 727 |
|
| 728 |
|
| 729 |
o "Application-Based, Common": The Enumservice is a "common" case of |
| 730 |
the Application-based class as described in <a href="#section-4.2.3">Section 4.2.3</a>. |
| 731 |
|
| 732 |
o "Application-Based, Subset": The Enumservice belongs to the |
| 733 |
"subset" case of the Application-based class as described in |
| 734 |
<a href="#section-4.2.3">Section 4.2.3</a>. |
| 735 |
|
| 736 |
o "Application-Based, Ancillary": The Enumservice is an "ancillary" |
| 737 |
case of the Application-based class, as described in |
| 738 |
<a href="#section-4.2.3">Section 4.2.3</a>. |
| 739 |
|
| 740 |
o "Data Type-Based": The Enumservice belongs to the Data Type-Based |
| 741 |
class as described in <a href="#section-4.2.4">Section 4.2.4</a>. |
| 742 |
|
| 743 |
o "Other": The majority of the functionality of the Enumservice does |
| 744 |
not fall into one of the classes defined. |
| 745 |
|
| 746 |
Class Example |
| 747 |
|
| 748 |
<class>Protocol-Based</class> |
| 749 |
|
| 750 |
<span class="h4"><a class="selflink" id="section-5.2.2" href="#section-5.2.2">5.2.2</a>. Enumservice Type (<type>)</span> |
| 751 |
|
| 752 |
The Type of the Enumservice. All Types SHOULD be listed in lower- |
| 753 |
case. The choice of Type depends on the Enumservice Class. Please |
| 754 |
find further instructions in <a href="#section-4">Section 4</a>. |
| 755 |
|
| 756 |
Type Example |
| 757 |
|
| 758 |
<type>foo</type> |
| 759 |
|
| 760 |
<span class="h4"><a class="selflink" id="section-5.2.3" href="#section-5.2.3">5.2.3</a>. Enumservice Subtype (<subtype>)</span> |
| 761 |
|
| 762 |
The Subtype of the Enumservice. All Subtypes SHOULD be listed in |
| 763 |
lower-case. The choice of Subtype depends on the Enumservice Class. |
| 764 |
Should the Enumservice not utilize a Subtype, then the <subtype> |
| 765 |
element MUST be omitted in the IANA Registration Template. If a |
| 766 |
given Enumservice Type has multiple Subtypes, then there MUST be a |
| 767 |
separate IANA Registration Template for each Subtype. Please find |
| 768 |
further instructions in <a href="#section-4">Section 4</a>. |
| 769 |
|
| 770 |
Subtype Example |
| 771 |
|
| 772 |
<subtype>bar</subtype> |
| 773 |
|
| 774 |
|
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 783 |
|
| 784 |
|
| 785 |
<span class="h4"><a class="selflink" id="section-5.2.4" href="#section-5.2.4">5.2.4</a>. URI Scheme(s) (<urischeme>)</span> |
| 786 |
|
| 787 |
The URI Schemes [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>] that are used with the Enumservice. The |
| 788 |
selection of URI Schemes often depends on the Enumservice Class, |
| 789 |
Type, and/or Subtype. A colon MUST NOT be placed after the URI |
| 790 |
Scheme name. If there is more than one URI Scheme, then one |
| 791 |
<urischeme> element per URI scheme MUST be used in the IANA |
| 792 |
Registration Template. Please find further instructions in |
| 793 |
<a href="#section-4">Section 4</a>. |
| 794 |
|
| 795 |
URI Scheme Example |
| 796 |
|
| 797 |
<urischeme>bar</urischeme> |
| 798 |
<urischeme>sbar</urischeme> |
| 799 |
|
| 800 |
Note: A client cannot choose a specific ENUM record in a record set |
| 801 |
based on the URI Scheme - the selection is only based on Type and |
| 802 |
Subtype, in accordance with [<a href="./rfc3402" title=""Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm"">RFC3402</a>]. |
| 803 |
|
| 804 |
<span class="h4"><a class="selflink" id="section-5.2.5" href="#section-5.2.5">5.2.5</a>. Functional Specification (<functionalspec>)</span> |
| 805 |
|
| 806 |
The Functional Specification describes how the Enumservice is used in |
| 807 |
connection with the URI to which it resolves. |
| 808 |
|
| 809 |
Functional Specification Example |
| 810 |
|
| 811 |
<functionalspec> |
| 812 |
<paragraph> |
| 813 |
This Enumservice indicates that the resource |
| 814 |
identified can be addressed by the associated |
| 815 |
URI in order to foo the bar. |
| 816 |
</paragraph> |
| 817 |
<paragraph> |
| 818 |
[<a href="#ref-...">...</a>] |
| 819 |
</paragraph> |
| 820 |
</functionalspec> |
| 821 |
|
| 822 |
Where the terms used are non-obvious, they should be defined in the |
| 823 |
Enumservice Specification, or a reference to an external document |
| 824 |
containing their definition should be provided. |
| 825 |
|
| 826 |
<span class="h4"><a class="selflink" id="section-5.2.6" href="#section-5.2.6">5.2.6</a>. Security Considerations (<security>)</span> |
| 827 |
|
| 828 |
A reference to the "Security Considerations" section of a given |
| 829 |
Enumservice Specification. |
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 839 |
|
| 840 |
|
| 841 |
Security Considerations Example |
| 842 |
|
| 843 |
<security> |
| 844 |
See <xref type="rfc" data="<a href="./rfc4979">rfc4979</a>"/>, <a href="#section-6">Section 6</a>. |
| 845 |
</security> |
| 846 |
|
| 847 |
<span class="h4"><a class="selflink" id="section-5.2.7" href="#section-5.2.7">5.2.7</a>. Intended Usage (<usage>)</span> |
| 848 |
|
| 849 |
One of the following values (without quotes): |
| 850 |
|
| 851 |
o "COMMON": Indicates that the Enumservice is intended for |
| 852 |
widespread use on the public Internet, and that its scope is not |
| 853 |
limited to a certain environment. |
| 854 |
|
| 855 |
o "LIMITED USE": Indicates that the Enumservice is intended for use |
| 856 |
on a limited scope, for example in private ENUM-like application |
| 857 |
scenarios. The use case provided in the Enumservice Specification |
| 858 |
should describe such a scenario. |
| 859 |
|
| 860 |
o "DEPRECATED": Indicates that the Enumservice has been declared |
| 861 |
deprecated (<a href="#section-11.7">Section 11.7</a>) and is not to be used in new |
| 862 |
deployments. Applications SHOULD however expect to encounter |
| 863 |
legacy instances of this Enumservice. |
| 864 |
|
| 865 |
Intended Usage Example |
| 866 |
|
| 867 |
<usage>COMMON</usage> |
| 868 |
|
| 869 |
<span class="h4"><a class="selflink" id="section-5.2.8" href="#section-5.2.8">5.2.8</a>. Enumservice Specification (<registrationdocs>)</span> |
| 870 |
|
| 871 |
Reference(s) to the Document(s) containing the Enumservice |
| 872 |
Specification. |
| 873 |
|
| 874 |
Enumservice Specification Examples |
| 875 |
|
| 876 |
<registrationdocs> |
| 877 |
<xref type="rfc" data="<a href="./rfc4979">rfc4979</a>"/> |
| 878 |
</registrationdocs> |
| 879 |
|
| 880 |
or |
| 881 |
|
| 882 |
<registrationdocs> |
| 883 |
<xref type="rfc" data="<a href="./rfc2026">rfc2026</a>"/> (obsoleted by <a href="./rfc2551">RFC 2551</a>) |
| 884 |
<xref type="rfc" data="<a href="./rfc2551">rfc2551</a>"/> |
| 885 |
</registrationdocs> |
| 886 |
|
| 887 |
or |
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 895 |
|
| 896 |
|
| 897 |
<registrationdocs> |
| 898 |
[International Telecommunications Union, |
| 899 |
"Enumservice Specification for Foobar", |
| 900 |
ITU-F Recommendation B.193, Release 73, Mar 2009.] |
| 901 |
</registrationdocs> |
| 902 |
|
| 903 |
<span class="h4"><a class="selflink" id="section-5.2.9" href="#section-5.2.9">5.2.9</a>. Requesters (<requesters>)</span> |
| 904 |
|
| 905 |
The persons requesting the registration of the Enumservice. Usually |
| 906 |
these are the authors of the Enumservice Specification. |
| 907 |
|
| 908 |
Requesters Example |
| 909 |
|
| 910 |
<requesters> |
| 911 |
<xref type="person" data="John_Doe"/> |
| 912 |
</requesters> |
| 913 |
|
| 914 |
[<a id="ref-...">...</a>] |
| 915 |
|
| 916 |
<people> |
| 917 |
<person id="John_Doe"> |
| 918 |
<name>John Doe</name> |
| 919 |
<org>ACME Research and Development Inc.</org> |
| 920 |
<uri>mailto:[email protected]</uri> |
| 921 |
<updated>2008-11-20</updated> |
| 922 |
</person> |
| 923 |
</people> |
| 924 |
|
| 925 |
If there is more than one requester, there MUST be one <xref> element |
| 926 |
per requester in the <requesters> element, and one <person> chunk per |
| 927 |
requester in the <people> element. |
| 928 |
|
| 929 |
<span class="h4"><a class="selflink" id="section-5.2.10" href="#section-5.2.10">5.2.10</a>. Further Information (<additionalinfo>)</span> |
| 930 |
|
| 931 |
Any other information the authors deem interesting, including |
| 932 |
artwork. |
| 933 |
|
| 934 |
Further Information Example |
| 935 |
|
| 936 |
<additionalinfo> |
| 937 |
<paragraph>more info goes here</paragraph> |
| 938 |
</additionalinfo> |
| 939 |
|
| 940 |
Note: If there is no such additional information, then the |
| 941 |
<additionalinfo> element is omitted. |
| 942 |
|
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 951 |
|
| 952 |
|
| 953 |
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Examples (REQUIRED)</span> |
| 954 |
|
| 955 |
This section MUST show at least one example of the Enumservice being |
| 956 |
registered, for illustrative purposes. The example(s) shall in no |
| 957 |
way limit the various forms that a given Enumservice may take, and |
| 958 |
this should be noted at the beginning of this section of the |
| 959 |
document. The example(s) MUST show the specific formatting of the |
| 960 |
intended NAPTRs (according to [<a href="./rfc3403" title=""Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database"">RFC3403</a>] and [<a href="./rfc6116" title=""The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)"">RFC6116</a>]), including one |
| 961 |
or more NAPTR example(s), AND a brief textual description, consisting |
| 962 |
of one or more sentences written in plain English, explaining the |
| 963 |
various parts or attributes of the record(s). |
| 964 |
|
| 965 |
The example(s) SHOULD contain a brief description how a client |
| 966 |
supporting this Enumservice could behave, if that description was not |
| 967 |
already given in, e.g., the Introduction or the Functional |
| 968 |
Specification. |
| 969 |
|
| 970 |
The example(s) SHOULD follow any relevant IETF guidelines on the use |
| 971 |
of domain names, phone numbers, and other resource identifier |
| 972 |
examples, such as [<a href="./rfc2606" title=""Reserved Top Level DNS Names"">RFC2606</a>]. |
| 973 |
|
| 974 |
For example: |
| 975 |
$ORIGIN 9.7.8.0.6.9.2.3.6.1.4.4.e164.arpa. |
| 976 |
@ IN NAPTR 100 10 "u" "E2U+foo:bar" "!^.*$!bar://example.com/!" . |
| 977 |
|
| 978 |
<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. Implementation Recommendations / Notes (OPTIONAL)</span> |
| 979 |
|
| 980 |
Recommendations that pertain to implementation and/or operations |
| 981 |
SHOULD be included. Such a section is helpful to someone reading an |
| 982 |
Enumservice Specification and trying to understand how best to use it |
| 983 |
to support their network or service. |
| 984 |
|
| 985 |
<span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. DNS Considerations (REQUIRED)</span> |
| 986 |
|
| 987 |
In case the inclusion of protocols and URI Schemes into ENUM |
| 988 |
specifically introduces new DNS issues, those MUST be described |
| 989 |
within this section. |
| 990 |
|
| 991 |
Such DNS issues include, but are not limited to: |
| 992 |
|
| 993 |
o Assumptions about ownership or administrative control of the |
| 994 |
namespace. |
| 995 |
|
| 996 |
o Requirement or need to use DNS wildcards. |
| 997 |
|
| 998 |
o Incompatibility with DNS wildcards. |
| 999 |
|
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
o Presence or absence of respective NAPTR Resource Records at |
| 1010 |
particular levels in the DNS hierarchy (e.g., only for "full" |
| 1011 |
E.164 numbers or wildcards only). |
| 1012 |
|
| 1013 |
o Use of any Resource Records (especially non-NAPTR) within or |
| 1014 |
beyond the e164.arpa namespace other than those needed to resolve |
| 1015 |
the domain names that appear in the "replacement" URI. |
| 1016 |
|
| 1017 |
o Potential for significant additional load on the nameserver chain |
| 1018 |
due to use of the service, and the mitigation of such additional |
| 1019 |
load. |
| 1020 |
|
| 1021 |
o Mitigation of potential for DNS loops, specifically in cases where |
| 1022 |
the result URI of an Enumservice might be used to trigger |
| 1023 |
additional (subsequent) ENUM queries. This applies in particular |
| 1024 |
to Enumservices using the 'tel' URI Scheme [<a href="./rfc3966" title=""The tel URI for Telephone Numbers"">RFC3966</a>] or any other |
| 1025 |
(future) URI Scheme using (E.164) numbers. "The ENUM Dip |
| 1026 |
Indicator Parameter for the tel URI" [<a href="./rfc4759" title=""The ENUM Dip Indicator Parameter for the "">RFC4759</a>] provides an example |
| 1027 |
of a loop mitigation mechanism. |
| 1028 |
|
| 1029 |
Rationale: some Enumservices try to exploit side effects of the DNS |
| 1030 |
that need to be explicitly discussed. |
| 1031 |
|
| 1032 |
<span class="h3"><a class="selflink" id="section-5.6" href="#section-5.6">5.6</a>. Security Considerations (REQUIRED)</span> |
| 1033 |
|
| 1034 |
A section explaining any potential security threats that are |
| 1035 |
especially applicable to the given registration MUST be included. |
| 1036 |
This MUST also include any information about access to Personally |
| 1037 |
Identifiable Information (PII). |
| 1038 |
|
| 1039 |
An Enumservice Specification SHOULD NOT include general and obvious |
| 1040 |
security recommendations, such as securing servers with strong |
| 1041 |
password authentication. |
| 1042 |
|
| 1043 |
For additional background, please note that [<a href="./rfc3552" title=""Guidelines for Writing RFC Text on Security Considerations"">RFC3552</a>] provides |
| 1044 |
guidance to write a good Security Considerations section. In |
| 1045 |
addition, [<a href="./rfc6116" title=""The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)"">RFC6116</a>] already outlines security considerations |
| 1046 |
affecting ENUM as a whole. Enumservice Specifications do not need to |
| 1047 |
and SHOULD NOT repeat considerations already listed in that document. |
| 1048 |
However, Enumservice Specifications SHOULD include a reference to |
| 1049 |
that section. |
| 1050 |
|
| 1051 |
Also, ENUM refers to resources using existing URI Schemes and |
| 1052 |
protocols. Enumservice Specifications do not need to and SHOULD NOT |
| 1053 |
repeat security considerations affecting those protocols and URI |
| 1054 |
Schemes themselves. |
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
However, in some cases, the inclusion of those protocols and URI |
| 1066 |
Schemes into ENUM specifically could introduce new security issues. |
| 1067 |
In these cases, those issues or risks MUST be covered in the |
| 1068 |
"Security Considerations" section of the Enumservice Specification. |
| 1069 |
Authors should pay particular attention to any indirect risks that |
| 1070 |
are associated with a proposed Enumservice, including cases where the |
| 1071 |
proposed Enumservice could lead to the discovery or disclosure of |
| 1072 |
Personally Identifiable Information (PII). |
| 1073 |
|
| 1074 |
<span class="h3"><a class="selflink" id="section-5.7" href="#section-5.7">5.7</a>. IANA Considerations (REQUIRED)</span> |
| 1075 |
|
| 1076 |
Describe the task IANA needs to fulfill to process the Enumservice |
| 1077 |
Registration Document. |
| 1078 |
|
| 1079 |
For example: |
| 1080 |
This document requests the IANA registration of the Enumservice with |
| 1081 |
Type "foo" and Subtype "bar" according to the definitions in this |
| 1082 |
document, [<a href="./rfc6117">RFC6117</a>], and [<a href="./rfc6116" title=""The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)"">RFC6116</a>]. |
| 1083 |
|
| 1084 |
For example: |
| 1085 |
This document requests an update of the IANA registration of the |
| 1086 |
Enumservice Type "foo" with Subtype "bar", according to the |
| 1087 |
definitions in this document, [<a href="./rfc6117">RFC6117</a>], and [<a href="./rfc6116" title=""The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)"">RFC6116</a>]. Therefore, |
| 1088 |
in the existing IANA registration for this Enumservice, the |
| 1089 |
<registrationdocs> element (Enumservice Specification) is enhanced by |
| 1090 |
adding a supplementary reference that points to this document. |
| 1091 |
|
| 1092 |
For example: |
| 1093 |
This document requests an update of the IANA registration of the |
| 1094 |
Enumservice Type "foo" with all its Subtypes, in order to declare it |
| 1095 |
deprecated. Therefore, in the existing IANA registration for this |
| 1096 |
Enumservice, the <usage> element (Intended Usage) is changed to |
| 1097 |
"DEPRECATED", and the <registrationdocs> element (Enumservice |
| 1098 |
Specification) is enhanced by adding a supplementary reference that |
| 1099 |
points to this document. |
| 1100 |
|
| 1101 |
<span class="h3"><a class="selflink" id="section-5.8" href="#section-5.8">5.8</a>. Other Sections (OPTIONAL)</span> |
| 1102 |
|
| 1103 |
Other sections beyond those required above MAY be included in an |
| 1104 |
Enumservice Specification. These sections may relate to the |
| 1105 |
specifics of the intended use of the Enumservice registration, as |
| 1106 |
well as to any associated technical, operational, administrative, or |
| 1107 |
other concerns. |
| 1108 |
|
| 1109 |
A use case SHOULD be included by the authors of the proposal, so that |
| 1110 |
experts can better understand the problem the proposal seeks to solve |
| 1111 |
(intended use of the Enumservice). The inclusion of such a use case |
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
will both accelerate the Expert Review process, as well as make any |
| 1122 |
eventual registration easier to understand and implement by other |
| 1123 |
parties. |
| 1124 |
|
| 1125 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. The Process of Registering New Enumservices</span> |
| 1126 |
|
| 1127 |
This section is an illustration of the process by which a new |
| 1128 |
Enumservice Registration Document is submitted for review and |
| 1129 |
comment, how such proposed Enumservices are reviewed, and how they |
| 1130 |
are published. This section is a non-normative description of the |
| 1131 |
process. The normative process is described in [<a href="./rfc5226" title="">RFC5226</a>]. |
| 1132 |
|
| 1133 |
Figure 1 shows what authors of a Registration Document describing an |
| 1134 |
Enumservice must carry out before said Registration Document can be |
| 1135 |
formally submitted to IANA for Expert Review. Figure 2 shows the |
| 1136 |
process from Expert Review onwards. |
| 1137 |
|
| 1138 |
|
| 1139 |
|
| 1140 |
|
| 1141 |
|
| 1142 |
|
| 1143 |
|
| 1144 |
|
| 1145 |
|
| 1146 |
|
| 1147 |
|
| 1148 |
|
| 1149 |
|
| 1150 |
|
| 1151 |
|
| 1152 |
|
| 1153 |
|
| 1154 |
|
| 1155 |
|
| 1156 |
|
| 1157 |
|
| 1158 |
|
| 1159 |
|
| 1160 |
|
| 1161 |
|
| 1162 |
|
| 1163 |
|
| 1164 |
|
| 1165 |
|
| 1166 |
|
| 1167 |
|
| 1168 |
|
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
+----------------------------+ |
| 1178 |
| Step 1: Read this document | |
| 1179 |
+----------------------------+ |
| 1180 |
| |
| 1181 |
V |
| 1182 |
+-------------------------------+ |
| 1183 |
| Step 2: Write R-D and submit | |
| 1184 |
+-------------------------------+ |
| 1185 |
| |
| 1186 |
V |
| 1187 |
+--------------------------------------------+ |
| 1188 |
| Step 3: Announce R-D and solicit feedback |<--+ |
| 1189 |
+--------------------------------------------+ | |
| 1190 |
| | |
| 1191 |
V | |
| 1192 |
.^. | |
| 1193 |
. . | |
| 1194 |
+------------+ . Feed- . +------------+ |
| 1195 |
| Update R-D |<---------< back >------------>| Update R-D | |
| 1196 |
| and submit | non-sub- . results . substantial | and submit | |
| 1197 |
+------------+ stantial . in: . changes +------------+ |
| 1198 |
| changes . . needed |
| 1199 |
| needed Y |
| 1200 |
| | no changes needed |
| 1201 |
| V |
| 1202 |
| +-----------------------------+ |
| 1203 |
+-------->| Step 4: Submit R-D to IANA | |
| 1204 |
+-----------------------------+ |
| 1205 |
: |
| 1206 |
: |
| 1207 |
V |
| 1208 |
|
| 1209 |
R-D: Registration Document |
| 1210 |
|
| 1211 |
Figure 1 |
| 1212 |
|
| 1213 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Step 1: Read This Document in Detail</span> |
| 1214 |
|
| 1215 |
This document, particularly in Sections <a href="#section-3">3</a>, <a href="#section-4">4</a>, and <a href="#section-5">5</a>, describes all of |
| 1216 |
the recommended and required sections, as well as requirements and |
| 1217 |
suggestions for content of an Enumservice Specification. |
| 1218 |
|
| 1219 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Step 2: Write and Submit Registration Document</span> |
| 1220 |
|
| 1221 |
An Internet-Draft (or another specification as appropriate) must be |
| 1222 |
written and made publicly available (submitted). The Registration |
| 1223 |
Document shall follow the guidelines according to Sections <a href="#section-4">4</a> and <a href="#section-5">5</a> of |
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
this document. The Review Guidelines for experts are defined in |
| 1234 |
<a href="#section-7.2">Section 7.2</a>. |
| 1235 |
|
| 1236 |
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Step 3: Request Comments From the IETF Community</span> |
| 1237 |
|
| 1238 |
The authors shall send an email to <[email protected]>, in which comments |
| 1239 |
on the Registration Document are requested. A proper public |
| 1240 |
reference (a URL is recommended) to the Registration Document must be |
| 1241 |
included in this email. |
| 1242 |
|
| 1243 |
Note: The ENUM WG mailing list <[email protected]> will be kept open |
| 1244 |
after conclusion of the ENUM WG. |
| 1245 |
|
| 1246 |
The authors should allow a reasonable period of time to elapse, such |
| 1247 |
as two to four weeks, in order to collect any feedback. The authors |
| 1248 |
then consider whether or not to take any of those comments into |
| 1249 |
account, by making changes to the Registration Document and |
| 1250 |
submitting a revision, or otherwise proceeding. The following |
| 1251 |
outcomes are open to the authors. The choice of path is left to the |
| 1252 |
authors' judgement. |
| 1253 |
|
| 1254 |
Note: Whatever the outcome is, the experts performing the Expert |
| 1255 |
Review later in the process are not bound to any decision during this |
| 1256 |
phase. |
| 1257 |
|
| 1258 |
<span class="h4"><a class="selflink" id="section-6.3.1" href="#section-6.3.1">6.3.1</a>. Outcome 1: No Changes Needed</span> |
| 1259 |
|
| 1260 |
No changes to the Registration Document are made, and the authors |
| 1261 |
proceed to Step 4 below. |
| 1262 |
|
| 1263 |
This outcome is recommended when the feedback received does not lead |
| 1264 |
to a new revision of the Registration Document. |
| 1265 |
|
| 1266 |
<span class="h4"><a class="selflink" id="section-6.3.2" href="#section-6.3.2">6.3.2</a>. Outcome 2: Changes, But No Further Comments Requested</span> |
| 1267 |
|
| 1268 |
The authors update the Registration Document and is/are confident |
| 1269 |
that all issues are resolved and do not require further discussion. |
| 1270 |
The authors proceed to Step 4 below. |
| 1271 |
|
| 1272 |
This outcome is recommended when minor objections have been raised, |
| 1273 |
or minor changes have been suggested. |
| 1274 |
|
| 1275 |
<span class="h4"><a class="selflink" id="section-6.3.3" href="#section-6.3.3">6.3.3</a>. Outcome 3: Changes and Further Comments Requested</span> |
| 1276 |
|
| 1277 |
The authors update and submit the Registration Document, and proceed |
| 1278 |
to Step 3 above, which involves sending another email to |
| 1279 |
<[email protected]> to request additional comments for the updated |
| 1280 |
version. |
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
This outcome is recommended when substantial objections have been |
| 1290 |
raised, or substantial changes have been suggested. |
| 1291 |
|
| 1292 |
<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. Step 4: Submit Registration Document to IANA</span> |
| 1293 |
|
| 1294 |
The authors submit the Registration Document to IANA (using the |
| 1295 |
<<a href="http://www.iana.org/">http://www.iana.org/</a>> website) for Expert Review. |
| 1296 |
|
| 1297 |
: |
| 1298 |
: |
| 1299 |
V |
| 1300 |
+-----------------------+ |
| 1301 |
| Step 5: Expert Review |<-------------+ |
| 1302 |
+-----------------------+ | |
| 1303 |
| | |
| 1304 |
V | |
| 1305 |
.^. | |
| 1306 |
. . | |
| 1307 |
.---------. . Expert . +------------+ |
| 1308 |
( Bad luck! )<-------- < Review >------------>| Update R-D | |
| 1309 |
`---------' experts . results . changes | and submit | |
| 1310 |
reject . in: . required +------------+ |
| 1311 |
. . |
| 1312 |
Y |
| 1313 |
| experts approve |
| 1314 |
V |
| 1315 |
+-----------------------------------+ |
| 1316 |
| Step 6: Publication of R-D | |
| 1317 |
+-----------------------------------+ |
| 1318 |
| |
| 1319 |
V |
| 1320 |
+---------------------------------------------+ |
| 1321 |
| Step 7: Adding Enumservice to IANA Registry | |
| 1322 |
+---------------------------------------------+ |
| 1323 |
|
| 1324 |
R-D: Registration Document |
| 1325 |
|
| 1326 |
Figure 2 |
| 1327 |
|
| 1328 |
<span class="h3"><a class="selflink" id="section-6.5" href="#section-6.5">6.5</a>. Step 5: Expert Review</span> |
| 1329 |
|
| 1330 |
IANA will take care of the "Expert Review" according to [<a href="./rfc5226" title="">RFC5226</a>]. |
| 1331 |
The Expert Review guidelines are outlined in <a href="#section-7.2">Section 7.2</a> of this |
| 1332 |
document. The authors must be prepared for further interaction with |
| 1333 |
IANA and the experts. |
| 1334 |
|
| 1335 |
|
| 1336 |
|
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
<span class="h4"><a class="selflink" id="section-6.5.1" href="#section-6.5.1">6.5.1</a>. Outcome 1: Experts Approve the Registration Document</span> |
| 1346 |
|
| 1347 |
No (more) changes to the Registration Document are made. IANA will |
| 1348 |
inform the authors, who then will proceed to Step 6 below. |
| 1349 |
|
| 1350 |
<span class="h4"><a class="selflink" id="section-6.5.2" href="#section-6.5.2">6.5.2</a>. Outcome 2: Changes Required</span> |
| 1351 |
|
| 1352 |
The experts might require changes before they can approve the |
| 1353 |
Registration Document. The authors update and submit the |
| 1354 |
Registration Document. The authors inform the experts about the |
| 1355 |
available update, who then continue the Expert Review Process. |
| 1356 |
|
| 1357 |
<span class="h4"><a class="selflink" id="section-6.5.3" href="#section-6.5.3">6.5.3</a>. Outcome 3: Experts Reject the Registration Document</span> |
| 1358 |
|
| 1359 |
The expert might reject the Registration, which means the Expert |
| 1360 |
Review process is discontinued. |
| 1361 |
|
| 1362 |
<span class="h3"><a class="selflink" id="section-6.6" href="#section-6.6">6.6</a>. Step 6: Publication of the Registration Document</span> |
| 1363 |
|
| 1364 |
The authors are responsible for ensuring that the Registration |
| 1365 |
Document is published according to "Specification Required" as |
| 1366 |
defined in [<a href="./rfc5226" title="">RFC5226</a>]. |
| 1367 |
|
| 1368 |
As set out in <a href="#section-3.4">Section 3.4</a> it is strongly RECOMMENDED that Enumservice |
| 1369 |
Specifications be published RFCs. As to every RFC, the normal IETF |
| 1370 |
publication process applies (see [<a href="#ref-Instructions2authors">Instructions2authors</a>]); i.e., the |
| 1371 |
Registration Document is submitted in the form of an Internet Draft |
| 1372 |
(e.g. via an IETF Working Group or a sponsoring Area Director). |
| 1373 |
[<a href="#ref-Instructions2authors">Instructions2authors</a>] also contains an option to publish an RFC as |
| 1374 |
'Independent Submission', which is further described in "Independent |
| 1375 |
Submissions to the RFC Editor" [<a href="./rfc4846" title=""Independent Submissions to the RFC Editor"">RFC4846</a>]. |
| 1376 |
|
| 1377 |
<span class="h3"><a class="selflink" id="section-6.7" href="#section-6.7">6.7</a>. Step 7: Adding Enumservice to the IANA Registry</span> |
| 1378 |
|
| 1379 |
In cases where the Registration Document is to be published as an |
| 1380 |
RFC, the RFC publication process ensures that IANA will add the |
| 1381 |
Enumservice to the registry. |
| 1382 |
|
| 1383 |
In cases where the Registration Document is to be published in a |
| 1384 |
specification other than RFC, the authors must inform IANA, as soon |
| 1385 |
as the Enumservice Specification has been published according to |
| 1386 |
"Specification Required" as defined in [<a href="./rfc5226" title="">RFC5226</a>]. The |
| 1387 |
<registrationdocs> element in the IANA Registration Template must |
| 1388 |
contain an unambiguous reference to the Enumservice Specification |
| 1389 |
(see also <a href="#section-5.2">Section 5.2</a>). In addition, the authors must provide IANA |
| 1390 |
with a stable URL to the Enumservice Specification, in order that |
| 1391 |
IANA may obtain the information included in the Enumservice |
| 1392 |
Specification. IANA will then add the Enumservice to the registry. |
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Expert Review</span> |
| 1402 |
|
| 1403 |
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Expert Selection Process</span> |
| 1404 |
|
| 1405 |
According to <a href="./rfc5226#section-3.2">Section 3.2 of [RFC5226]</a>, experts are appointed by the |
| 1406 |
IESG. The IESG is responsible for ensuring that there is always a |
| 1407 |
sufficient pool of experts available. |
| 1408 |
|
| 1409 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Review Guidelines</span> |
| 1410 |
|
| 1411 |
Generally, the "Expert Review" process of an Enumservice follows the |
| 1412 |
guidelines documented in <a href="#section-3.3">Section 3.3</a> of "Guidelines for Writing an |
| 1413 |
IANA Considerations Section in RFCs" [<a href="./rfc5226" title="">RFC5226</a>]. Note that <a href="./rfc5226">RFC 5226</a> |
| 1414 |
says 'The review may be wide or narrow, depending on the situation |
| 1415 |
and the judgment of the designated expert'. Therefore, the following |
| 1416 |
list should be considered a guideline, rather than a binding list. |
| 1417 |
|
| 1418 |
In case of conflicts between [<a href="./rfc5226" title="">RFC5226</a>] and the guidelines in this |
| 1419 |
section, [<a href="./rfc5226" title="">RFC5226</a>] remains authoritative. |
| 1420 |
|
| 1421 |
The expert evaluates the criteria as set out in [<a href="./rfc5226" title="">RFC5226</a>], and should |
| 1422 |
additionally consider the following: |
| 1423 |
|
| 1424 |
o Verify conformance with the ENUM specification [<a href="./rfc6116" title=""The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)"">RFC6116</a>]. |
| 1425 |
|
| 1426 |
o Verify that the requirements set out in this document (Sections <a href="#section-3">3</a> |
| 1427 |
and 5) are met. This includes checking for completeness and |
| 1428 |
whether all the aspects described in Sections <a href="#section-3">3</a> and <a href="#section-5">5</a> are |
| 1429 |
sufficiently addressed. |
| 1430 |
|
| 1431 |
o If a use case is provided, the experts should verify whether the |
| 1432 |
proposed Enumservice does actually match the use case. The |
| 1433 |
experts should also determine whether the use case could be |
| 1434 |
covered by an existing Enumservice. |
| 1435 |
|
| 1436 |
o Verify that the Enumservice proposed cannot be confused with |
| 1437 |
identical (or similar) other Enumservices already registered. |
| 1438 |
|
| 1439 |
o If the Enumservice is classified according to <a href="#section-4.2">Section 4.2</a>, the |
| 1440 |
experts must verify that the principles of the Class in question |
| 1441 |
are followed. |
| 1442 |
|
| 1443 |
o In case the Enumservice is not classified, the experts must verify |
| 1444 |
whether a convincing reason for the deviation is provided in the |
| 1445 |
Registration Document. |
| 1446 |
|
| 1447 |
|
| 1448 |
|
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
o Investigate whether the proposed Enumservice has any negative side |
| 1458 |
effects on existing clients and infrastructure, particularly the |
| 1459 |
DNS. |
| 1460 |
|
| 1461 |
o If the output of processing an Enumservice might be used for input |
| 1462 |
to more ENUM processing (especially services returning 'tel' |
| 1463 |
URIs), the experts should verify that the authors have adequately |
| 1464 |
addressed the issue of potential query loops. |
| 1465 |
|
| 1466 |
<span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a>. Appeals</span> |
| 1467 |
|
| 1468 |
Appeals of Expert Review decisions follow the process described in |
| 1469 |
<a href="./rfc5226#section-7">Section 7 of [RFC5226]</a> and <a href="./rfc2026#section-6.5">Section 6.5 of [RFC2026]</a>. |
| 1470 |
|
| 1471 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Revision of Existing Enumservice Specifications</span> |
| 1472 |
|
| 1473 |
Many Enumservice registrations, published via IETF RFCs, already |
| 1474 |
exist at the time of the development of this document. These |
| 1475 |
existing Enumservice Specifications MAY be revised to comply with the |
| 1476 |
specifications contained herein. All revisions of Enumservice |
| 1477 |
Specifications MUST be compliant with the specifications contained |
| 1478 |
herein. |
| 1479 |
|
| 1480 |
Note: Enumservice Specifications updated only by [<a href="./rfc6118" title=""Update of Legacy IANA Registrations of Enumservices"">RFC6118</a>] are not |
| 1481 |
compliant with the specifications contained herein! |
| 1482 |
|
| 1483 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Extension of Existing Enumservice Specifications</span> |
| 1484 |
|
| 1485 |
There are cases where it is more sensible to extend an existing |
| 1486 |
Enumservice registration rather than propose a new one. Such cases |
| 1487 |
include adding a new Subtype to an existing Type. Depending on the |
| 1488 |
nature of the extension, the original Enumservice Specification needs |
| 1489 |
to be extended (Updates) or replaced (Obsoletes) [<a href="./rfc2223" title=""Instructions to RFC Authors"">RFC2223</a>]. |
| 1490 |
Specifically, an update is appropriate when a new Subtype is being |
| 1491 |
added without changes to the existing repertoire. A replacement is |
| 1492 |
needed if there is a change to the default, or changes to the |
| 1493 |
assumptions of URI support in clients. |
| 1494 |
|
| 1495 |
Any Enumservice Specifications for existing Enumservices that are |
| 1496 |
extended MUST comply with the specifications contained herein. As a |
| 1497 |
consequence, revisions of existing Enumservice Specifications may be |
| 1498 |
required according to <a href="#section-8">Section 8</a>. |
| 1499 |
|
| 1500 |
|
| 1501 |
|
| 1502 |
|
| 1503 |
|
| 1504 |
|
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Security Considerations</span> |
| 1514 |
|
| 1515 |
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Considerations Regarding This Document</span> |
| 1516 |
|
| 1517 |
Since this document does not introduce any new technology, protocol, |
| 1518 |
or Enumservice Specification, there are no specific security issues |
| 1519 |
to be considered for this document. However, as this is a guide to |
| 1520 |
authors of new Enumservice Specifications, the next section should be |
| 1521 |
considered closely by authors and experts. |
| 1522 |
|
| 1523 |
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Enumservice Security Considerations Guideline</span> |
| 1524 |
|
| 1525 |
Guidelines concerning the Security Considerations section of an |
| 1526 |
Enumservice Specification can be found in <a href="#section-5.6">Section 5.6</a>. |
| 1527 |
|
| 1528 |
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. IANA Considerations</span> |
| 1529 |
|
| 1530 |
<span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. Registry Update</span> |
| 1531 |
|
| 1532 |
IANA updated the registry "Enumservice Registrations" as defined in |
| 1533 |
(this) <a href="#section-11">Section 11</a>, which replaces the old mechanism as defined in |
| 1534 |
[<a href="./rfc3761" title=""The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)"">RFC3761</a>]. |
| 1535 |
|
| 1536 |
It is noted that the process described herein applies only to |
| 1537 |
ordinary Enumservice registrations (i.e., the registration process of |
| 1538 |
"X-" Enumservices is beyond the scope of this document, and as per |
| 1539 |
[<a href="./rfc6116" title=""The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)"">RFC6116</a>] "P-" Enumservices will not be registered at all). |
| 1540 |
|
| 1541 |
<span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. Registration Template (XML chunk)</span> |
| 1542 |
|
| 1543 |
<record> |
| 1544 |
<class> <!-- Enumservice Class --> </class> |
| 1545 |
<type> <!-- Type --> </type> |
| 1546 |
<subtype> <!-- Subtype --> </subtype> |
| 1547 |
<urischeme> <!-- URI Schema Name --> </urischeme> |
| 1548 |
<urischeme> <!-- another URI Schema Name --> </urischeme> |
| 1549 |
<functionalspec> |
| 1550 |
<paragraph> |
| 1551 |
<!-- Text that explains the functionality of |
| 1552 |
the Enumservice to be registered --> |
| 1553 |
</paragraph> |
| 1554 |
</functionalspec> |
| 1555 |
<security> |
| 1556 |
<!-- Security Considerations of the |
| 1557 |
Enumservice to be registered --> |
| 1558 |
</security> |
| 1559 |
<usage> <!-- COMMON, LIMITED USE, or OBSOLETE --> </usage> |
| 1560 |
<registrationdocs> |
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 28]</span></pre> |
| 1565 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1566 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
<!-- Change accordingly --> |
| 1570 |
<xref type="rfc" data="<a href="./rfc2551">rfc2551</a>"/> |
| 1571 |
</registrationdocs> |
| 1572 |
<requesters> |
| 1573 |
<!-- Change accordingly --> |
| 1574 |
<xref type="person" data="John_Doe"/> |
| 1575 |
<xref type="person" data="Jane_Dale"/> |
| 1576 |
</requesters> |
| 1577 |
<additionalinfo> |
| 1578 |
<paragraph> |
| 1579 |
<!-- Text with additional information about |
| 1580 |
the Enumservice to be registered --> |
| 1581 |
</paragraph> |
| 1582 |
<artwork> |
| 1583 |
<!-- There can be artwork sections, too --> |
| 1584 |
:-) |
| 1585 |
</artwork> |
| 1586 |
</additionalinfo> |
| 1587 |
</record> |
| 1588 |
|
| 1589 |
<people> |
| 1590 |
<person id="John_Doe"> |
| 1591 |
<name> <!-- Firstname Lastname --> </name> |
| 1592 |
<org> <!-- Organisation Name --> </org> |
| 1593 |
<uri> <!-- mailto: or http: URI --> </uri> |
| 1594 |
<updated> <!-- date format YYYY-MM-DD --> </updated> |
| 1595 |
</person> |
| 1596 |
<!-- repeat person section for each person --> |
| 1597 |
</people> |
| 1598 |
|
| 1599 |
Authors of an Enumservice Specification are encouraged to use these |
| 1600 |
XML chunks as a template to create the IANA Registration Template. |
| 1601 |
Examples for the use of this template are contained in <a href="#appendix-A">Appendix A</a>. |
| 1602 |
|
| 1603 |
<span class="h3"><a class="selflink" id="section-11.3" href="#section-11.3">11.3</a>. Location</span> |
| 1604 |
|
| 1605 |
Approved Enumservice registrations are published in the IANA registry |
| 1606 |
named "Enumservice Registrations", which is available at the |
| 1607 |
following URI: |
| 1608 |
<<a href="http://www.iana.org/assignments/enum-services">http://www.iana.org/assignments/enum-services</a>>. |
| 1609 |
|
| 1610 |
This registry publishes representations derived from the IANA |
| 1611 |
Registration Template as described in <a href="#section-11.2">Section 11.2</a> and specified in |
| 1612 |
<a href="#section-5.2">Section 5.2</a>. |
| 1613 |
|
| 1614 |
Where the Enumservice Specification is not an RFC, IANA must hold an |
| 1615 |
escrow copy of that Enumservice Specification. Said escrow copy will |
| 1616 |
act as the master reference for that Enumservice registration. |
| 1617 |
|
| 1618 |
|
| 1619 |
|
| 1620 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 29]</span></pre> |
| 1621 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1622 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 1623 |
|
| 1624 |
|
| 1625 |
<span class="h3"><a class="selflink" id="section-11.4" href="#section-11.4">11.4</a>. Structure</span> |
| 1626 |
|
| 1627 |
IANA maintains the Enumservice Registry sorted in alphabetical order. |
| 1628 |
The first sort field is Type, the second is Subtype. |
| 1629 |
|
| 1630 |
[<a id="ref-RFC6118">RFC6118</a>] updates the existing Enumservices by transforming them into |
| 1631 |
the new XML-chunk-based IANA Registration Template (see also |
| 1632 |
<a href="#section-8">Section 8</a>). |
| 1633 |
|
| 1634 |
<span class="h3"><a class="selflink" id="section-11.5" href="#section-11.5">11.5</a>. Expert Review Procedure</span> |
| 1635 |
|
| 1636 |
Whenever a Registration Document is submitted via the IANA website, |
| 1637 |
IANA will take care of the "Expert Review" process according to |
| 1638 |
"Guidelines for Writing an IANA Considerations Section in RFCs" |
| 1639 |
[<a href="./rfc5226" title="">RFC5226</a>]. |
| 1640 |
|
| 1641 |
To prevent clashes, IANA will check whether a request with identical |
| 1642 |
"type:subtype" (or "type" without Subtype) was submitted for Expert |
| 1643 |
Review earlier and will inform the experts accordingly. The experts |
| 1644 |
are authorized to resolve clashes as they see fit. The requesters |
| 1645 |
may need to update their registration request before getting expert |
| 1646 |
approval. |
| 1647 |
|
| 1648 |
Once the experts have conditionally approved the Enumservice, IANA |
| 1649 |
will inform the authors. This information should also include a |
| 1650 |
reminder that (i) the authors are now responsible for publication of |
| 1651 |
the Registration Document (see also <a href="#section-6.6">Section 6.6</a>) and (ii) the |
| 1652 |
Enumservice will be added to the IANA registry only after its |
| 1653 |
Enumservice Specification is published according to the |
| 1654 |
"Specification Required" policy as defined in [<a href="./rfc5226" title="">RFC5226</a>] (see also |
| 1655 |
<a href="#section-6.7">Section 6.7</a>). |
| 1656 |
|
| 1657 |
Note: After sending the approval note to the authors, IANA has no |
| 1658 |
further responsibilities besides keeping internal records of approved |
| 1659 |
Registration Documents. IANA will be involved again at registration |
| 1660 |
of the Enumservice (see <a href="#section-11.6">Section 11.6</a>). |
| 1661 |
|
| 1662 |
<span class="h3"><a class="selflink" id="section-11.6" href="#section-11.6">11.6</a>. Registration Procedure</span> |
| 1663 |
|
| 1664 |
There is a slight difference in process depending on whether or not |
| 1665 |
the Enumservice Specification will be published as an RFC. The |
| 1666 |
reason for this difference lies in the current RFC publication |
| 1667 |
process that includes IANA interaction shortly before publication of |
| 1668 |
an RFC. |
| 1669 |
|
| 1670 |
|
| 1671 |
|
| 1672 |
|
| 1673 |
|
| 1674 |
|
| 1675 |
|
| 1676 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 30]</span></pre> |
| 1677 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1678 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 1679 |
|
| 1680 |
|
| 1681 |
<span class="h4"><a class="selflink" id="section-11.6.1" href="#section-11.6.1">11.6.1</a>. Published as an RFC</span> |
| 1682 |
|
| 1683 |
As per the RFC publication process, IANA will receive the Enumservice |
| 1684 |
Specification to carry out IANA actions shortly before publication of |
| 1685 |
the RFC. The IANA action will be to register the Enumservice, i.e., |
| 1686 |
add the Enumservice to the IANA "Enumservice Registrations" registry |
| 1687 |
(see also <a href="#section-11.3">Section 11.3</a>). |
| 1688 |
|
| 1689 |
IANA must only add Enumservices to the Registry, if the experts have |
| 1690 |
(conditionally) approved the corresponding Enumservice Specification. |
| 1691 |
IANA should attempt to resolve possible conflicts arising from this |
| 1692 |
together with the experts. In case there are substantial changes |
| 1693 |
between the (conditionally) approved and the to be published version, |
| 1694 |
IANA may reject the request after consulting the experts. |
| 1695 |
|
| 1696 |
IANA must ensure that any further substantial changes the Enumservice |
| 1697 |
Specification might undergo before final RFC publication are approved |
| 1698 |
by the experts. |
| 1699 |
|
| 1700 |
Note: Clearly editorial changes (such as typos) or minor changes in |
| 1701 |
purely editorial sections (such as Authors' Addresses, |
| 1702 |
Acknowledgments, References, and alike) are not considered |
| 1703 |
substantial. |
| 1704 |
|
| 1705 |
<span class="h4"><a class="selflink" id="section-11.6.2" href="#section-11.6.2">11.6.2</a>. Published as a Non-RFC</span> |
| 1706 |
|
| 1707 |
Once the authors have informed IANA about the publication, IANA must |
| 1708 |
ensure that the requirements for "Specification Required" as defined |
| 1709 |
in [<a href="./rfc5226" title="">RFC5226</a>] are met, the reference to the specification is |
| 1710 |
unambiguous, and the content of the Enumservice Specification is |
| 1711 |
identical to the Registration Document as approved by the experts. |
| 1712 |
IANA will then register the Enumservice, i.e., add the Enumservice to |
| 1713 |
the IANA "Enumservice Registrations" registry, and make an escrow |
| 1714 |
copy (see also <a href="#section-11.3">Section 11.3</a>). |
| 1715 |
|
| 1716 |
IANA must only add Enumservices to the Registry, if the experts have |
| 1717 |
approved the corresponding Enumservice Specification. IANA should |
| 1718 |
attempt to resolve possible conflicts arising from this together with |
| 1719 |
the experts. In case there are substantial changes between the |
| 1720 |
approved and the published version, IANA may reject the request after |
| 1721 |
consulting the experts. |
| 1722 |
|
| 1723 |
Note: Clearly editorial changes (such as typos) or minor changes in |
| 1724 |
purely editorial sections (such as Authors' Addresses, |
| 1725 |
Acknowledgments, References, and alike) are not considered |
| 1726 |
substantial. |
| 1727 |
|
| 1728 |
|
| 1729 |
|
| 1730 |
|
| 1731 |
|
| 1732 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 31]</span></pre> |
| 1733 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span> |
| 1734 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 1735 |
|
| 1736 |
|
| 1737 |
<span class="h3"><a class="selflink" id="section-11.7" href="#section-11.7">11.7</a>. Change Control</span> |
| 1738 |
|
| 1739 |
Change control of any Enumservice registrations is done by |
| 1740 |
"Specification Required", which implies the use of a Designated |
| 1741 |
Expert, according to [<a href="./rfc5226" title="">RFC5226</a>]. Updates of Enumservice |
| 1742 |
Specifications MUST comply with the requirements described in this |
| 1743 |
document. Updates are handled the same way as initial Enumservice |
| 1744 |
registrations. |
| 1745 |
|
| 1746 |
Authorized Change Controllers are the experts and the IESG. |
| 1747 |
|
| 1748 |
Enumservice registrations must not be deleted. An Enumservice that |
| 1749 |
is believed to be no longer appropriate for use can be declared |
| 1750 |
deprecated by publication of a new Enumservice Specification, |
| 1751 |
changing the Enumservice <usage> element (Intended Usage) to |
| 1752 |
"DEPRECATED"; such Enumservices will be clearly marked in the lists |
| 1753 |
published by IANA. As obsoletions are updates, they are also handled |
| 1754 |
the same way as initial Enumservice registrations. Alternatively, |
| 1755 |
Enumservices may be declared deprecated by an IESG action. |
| 1756 |
|
| 1757 |
<span class="h3"><a class="selflink" id="section-11.8" href="#section-11.8">11.8</a>. Restrictions</span> |
| 1758 |
|
| 1759 |
As stated in <a href="#section-3.2">Section 3.2</a>, a "-" (dash) MUST NOT be used as the first |
| 1760 |
nor as the second nor as the last character of a Type or a Subtype. |
| 1761 |
Furthermore, Type or Subtype of any Enumservice MUST NOT be set to, |
| 1762 |
nor start with, "E2U". Any Enumservice registration requests not |
| 1763 |
following these restrictions must be rejected by IANA, and the Expert |
| 1764 |
Review process should not be initiated. |
| 1765 |
|
| 1766 |
<a href="#section-5.2">Section 5.2</a> contains examples for Enumservice registrations. |
| 1767 |
Therefore, IANA must not register an Enumservice with Type or Subtype |
| 1768 |
set to "foo", "bar", or "sbar", unless the experts explicitly confirm |
| 1769 |
an exception. |
| 1770 |
|
| 1771 |
<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Acknowledgments</span> |
| 1772 |
|
| 1773 |
The authors would like to thank the following people who have |
| 1774 |
provided feedback or significant contributions to the development of |
| 1775 |
this document: Jari Arkko, Stewart Bryant, Gonzalo Camarillo, |
| 1776 |
Lawrence Conroy, Michelle Cotton, Miguel Garcia, David Harrington, |
| 1777 |
Alfred Hoenes, Ari Keranen, Peter Koch, Edward Lewis, Alexey |
| 1778 |
Melnikov, Jon Peterson, Pekka Savola, and Peter Saint-Andre. |
| 1779 |
|
| 1780 |
Lawrence Conroy has provided extensive text for the Enumservice |
| 1781 |
Classification section. |
| 1782 |
|
| 1783 |
|
| 1784 |
|
| 1785 |
|
| 1786 |
|
| 1787 |
|
| 1788 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 32]</span></pre> |
| 1789 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span> |
| 1790 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 1791 |
|
| 1792 |
|
| 1793 |
<a href="./rfc3761#section-3">Section 3 of [RFC3761]</a>, which was edited by Patrik Faltstrom and |
| 1794 |
Michael Mealling, has been incorporated into this document. Please |
| 1795 |
see the Acknowledgments section in <a href="./rfc3761">RFC 3761</a> for additional |
| 1796 |
acknowledgments. |
| 1797 |
|
| 1798 |
<span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. References</span> |
| 1799 |
|
| 1800 |
<span class="h3"><a class="selflink" id="section-13.1" href="#section-13.1">13.1</a>. Normative References</span> |
| 1801 |
|
| 1802 |
[<a id="ref-RFC2026">RFC2026</a>] Bradner, S., "The Internet Standards Process -- Revision |
| 1803 |
3", <a href="https://www.rfc-editor.org/bcp/bcp9">BCP 9</a>, <a href="./rfc2026">RFC 2026</a>, October 1996. |
| 1804 |
|
| 1805 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 1806 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 1807 |
|
| 1808 |
[<a id="ref-RFC3402">RFC3402</a>] Mealling, M., "Dynamic Delegation Discovery System (DDDS) |
| 1809 |
Part Two: The Algorithm", <a href="./rfc3402">RFC 3402</a>, October 2002. |
| 1810 |
|
| 1811 |
[<a id="ref-RFC3403">RFC3403</a>] Mealling, M., "Dynamic Delegation Discovery System (DDDS) |
| 1812 |
Part Three: The Domain Name System (DNS) Database", |
| 1813 |
<a href="./rfc3403">RFC 3403</a>, October 2002. |
| 1814 |
|
| 1815 |
[<a id="ref-RFC3761">RFC3761</a>] Faltstrom, P. and M. Mealling, "The E.164 to Uniform |
| 1816 |
Resource Identifiers (URI) Dynamic Delegation Discovery |
| 1817 |
System (DDDS) Application (ENUM)", <a href="./rfc3761">RFC 3761</a>, April 2004. |
| 1818 |
|
| 1819 |
[<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform |
| 1820 |
Resource Identifier (URI): Generic Syntax", STD 66, |
| 1821 |
<a href="./rfc3986">RFC 3986</a>, January 2005. |
| 1822 |
|
| 1823 |
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an |
| 1824 |
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>, |
| 1825 |
May 2008. |
| 1826 |
|
| 1827 |
[<a id="ref-RFC6116">RFC6116</a>] Bradner, S., Conroy, L., and K. Fujiwara, "The E.164 to |
| 1828 |
Uniform Resource Identifiers (URI) Dynamic Delegation |
| 1829 |
Discovery System (DDDS) Application (ENUM)", <a href="./rfc6116">RFC 6116</a>, |
| 1830 |
March 2011. |
| 1831 |
|
| 1832 |
|
| 1833 |
|
| 1834 |
|
| 1835 |
|
| 1836 |
|
| 1837 |
|
| 1838 |
|
| 1839 |
|
| 1840 |
|
| 1841 |
|
| 1842 |
|
| 1843 |
|
| 1844 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 33]</span></pre> |
| 1845 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span> |
| 1846 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 1847 |
|
| 1848 |
|
| 1849 |
<span class="h3"><a class="selflink" id="section-13.2" href="#section-13.2">13.2</a>. Informative References</span> |
| 1850 |
|
| 1851 |
[<a id="ref-ITU.E164.2005">ITU.E164.2005</a>] |
| 1852 |
International Telecommunications Union, "The International |
| 1853 |
Public Telecommunication Numbering Plan", ITU- |
| 1854 |
T Recommendation E.164, Feb 2005. |
| 1855 |
|
| 1856 |
[<a id="ref-Instructions2authors">Instructions2authors</a>] |
| 1857 |
Reynolds, J. and R. Braden, "Instructions to Request for |
| 1858 |
Comments (RFC) Authors", RFC Editor <a href="http://www.rfc-editor.org/rfc-editor/instructions2authors.txt">http://</a> |
| 1859 |
<a href="http://www.rfc-editor.org/rfc-editor/instructions2authors.txt">www.rfc-editor.org/rfc-editor/instructions2authors.txt</a>, |
| 1860 |
August 2004. |
| 1861 |
|
| 1862 |
[<a id="ref-RFC1035">RFC1035</a>] Mockapetris, P., "Domain names - implementation and |
| 1863 |
specification", STD 13, <a href="./rfc1035">RFC 1035</a>, November 1987. |
| 1864 |
|
| 1865 |
[<a id="ref-RFC2223">RFC2223</a>] Postel, J. and J. Reynolds, "Instructions to RFC Authors", |
| 1866 |
<a href="./rfc2223">RFC 2223</a>, October 1997. |
| 1867 |
|
| 1868 |
[<a id="ref-RFC2606">RFC2606</a>] Eastlake, D. and A. Panitz, "Reserved Top Level DNS |
| 1869 |
Names", <a href="https://www.rfc-editor.org/bcp/bcp32">BCP 32</a>, <a href="./rfc2606">RFC 2606</a>, June 1999. |
| 1870 |
|
| 1871 |
[<a id="ref-RFC2780">RFC2780</a>] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For |
| 1872 |
Values In the Internet Protocol and Related Headers", |
| 1873 |
<a href="https://www.rfc-editor.org/bcp/bcp37">BCP 37</a>, <a href="./rfc2780">RFC 2780</a>, March 2000. |
| 1874 |
|
| 1875 |
[<a id="ref-RFC3552">RFC3552</a>] Rescorla, E. and B. Korver, "Guidelines for Writing RFC |
| 1876 |
Text on Security Considerations", <a href="https://www.rfc-editor.org/bcp/bcp72">BCP 72</a>, <a href="./rfc3552">RFC 3552</a>, |
| 1877 |
July 2003. |
| 1878 |
|
| 1879 |
[<a id="ref-RFC3764">RFC3764</a>] Peterson, J., "enumservice registration for Session |
| 1880 |
Initiation Protocol (SIP) Addresses-of-Record", <a href="./rfc3764">RFC 3764</a>, |
| 1881 |
April 2004. |
| 1882 |
|
| 1883 |
[<a id="ref-RFC3966">RFC3966</a>] Schulzrinne, H., "The tel URI for Telephone Numbers", |
| 1884 |
<a href="./rfc3966">RFC 3966</a>, December 2004. |
| 1885 |
|
| 1886 |
[<a id="ref-RFC4238">RFC4238</a>] Vaudreuil, G., "Voice Message Routing Service", <a href="./rfc4238">RFC 4238</a>, |
| 1887 |
October 2005. |
| 1888 |
|
| 1889 |
[<a id="ref-RFC4759">RFC4759</a>] Stastny, R., Shockey, R., and L. Conroy, "The ENUM Dip |
| 1890 |
Indicator Parameter for the "tel" URI", <a href="./rfc4759">RFC 4759</a>, |
| 1891 |
December 2006. |
| 1892 |
|
| 1893 |
[<a id="ref-RFC4846">RFC4846</a>] Klensin, J. and D. Thaler, "Independent Submissions to the |
| 1894 |
RFC Editor", <a href="./rfc4846">RFC 4846</a>, July 2007. |
| 1895 |
|
| 1896 |
|
| 1897 |
|
| 1898 |
|
| 1899 |
|
| 1900 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 34]</span></pre> |
| 1901 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span> |
| 1902 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 1903 |
|
| 1904 |
|
| 1905 |
[<a id="ref-RFC4969">RFC4969</a>] Mayrhofer, A., "IANA Registration for vCard Enumservice", |
| 1906 |
<a href="./rfc4969">RFC 4969</a>, August 2007. |
| 1907 |
|
| 1908 |
[<a id="ref-RFC4979">RFC4979</a>] Mayrhofer, A., "IANA Registration for Enumservice 'XMPP'", |
| 1909 |
<a href="./rfc4979">RFC 4979</a>, August 2007. |
| 1910 |
|
| 1911 |
[<a id="ref-RFC5234">RFC5234</a>] Crocker, D. and P. Overell, "Augmented BNF for Syntax |
| 1912 |
Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>, January 2008. |
| 1913 |
|
| 1914 |
[<a id="ref-RFC6118">RFC6118</a>] Hoeneisen, B. and A. Mayrhofer, "Update of Legacy IANA |
| 1915 |
Registrations of Enumservices", <a href="./rfc6118">RFC 6118</a>, March 2011. |
| 1916 |
|
| 1917 |
|
| 1918 |
|
| 1919 |
|
| 1920 |
|
| 1921 |
|
| 1922 |
|
| 1923 |
|
| 1924 |
|
| 1925 |
|
| 1926 |
|
| 1927 |
|
| 1928 |
|
| 1929 |
|
| 1930 |
|
| 1931 |
|
| 1932 |
|
| 1933 |
|
| 1934 |
|
| 1935 |
|
| 1936 |
|
| 1937 |
|
| 1938 |
|
| 1939 |
|
| 1940 |
|
| 1941 |
|
| 1942 |
|
| 1943 |
|
| 1944 |
|
| 1945 |
|
| 1946 |
|
| 1947 |
|
| 1948 |
|
| 1949 |
|
| 1950 |
|
| 1951 |
|
| 1952 |
|
| 1953 |
|
| 1954 |
|
| 1955 |
|
| 1956 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 35]</span></pre> |
| 1957 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span> |
| 1958 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 1959 |
|
| 1960 |
|
| 1961 |
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. IANA Registration Template Examples</span> |
| 1962 |
|
| 1963 |
This section contains non-normative examples of the XML-chunk-based |
| 1964 |
IANA Registration Template: |
| 1965 |
|
| 1966 |
This is the first example: |
| 1967 |
|
| 1968 |
<record> |
| 1969 |
<class>Protocol-Based</class> |
| 1970 |
<type>email</type> |
| 1971 |
<subtype>mailto</subtype> |
| 1972 |
<urischeme>mailto</urischeme> |
| 1973 |
<functionalspec> |
| 1974 |
<paragraph> |
| 1975 |
This Enumservice indicates that the resource |
| 1976 |
can be addressed by the associated URI in |
| 1977 |
order to send an email. |
| 1978 |
</paragraph> |
| 1979 |
</functionalspec> |
| 1980 |
<security> |
| 1981 |
See <xref type="rfc" data="<a href="./rfc4355">rfc4355</a>"/>, <a href="#section-6">Section 6</a>. |
| 1982 |
</security> |
| 1983 |
<usage>COMMON</usage> |
| 1984 |
<registrationdocs> |
| 1985 |
<xref type="rfc" data="<a href="./rfc4355">rfc4355</a>"/> |
| 1986 |
</registrationdocs> |
| 1987 |
<requesters> |
| 1988 |
<xref type="person" data="Lawrence_Conroy"/> |
| 1989 |
</requesters> |
| 1990 |
</record> |
| 1991 |
|
| 1992 |
<people> |
| 1993 |
<person id="Lawrence_Conroy"> |
| 1994 |
<name>Lawrence Conroy</name> |
| 1995 |
<org>Siemens Roke Manor Research</org> |
| 1996 |
<uri>mailto:[email protected]</uri> |
| 1997 |
<updated>2008-11-20</updated> |
| 1998 |
</person> |
| 1999 |
</people> |
| 2000 |
|
| 2001 |
|
| 2002 |
|
| 2003 |
|
| 2004 |
|
| 2005 |
|
| 2006 |
|
| 2007 |
|
| 2008 |
|
| 2009 |
|
| 2010 |
|
| 2011 |
|
| 2012 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 36]</span></pre> |
| 2013 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span> |
| 2014 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 2015 |
|
| 2016 |
|
| 2017 |
This is the second example. |
| 2018 |
|
| 2019 |
<record> |
| 2020 |
<class>Protocol-Based</class> |
| 2021 |
<type>xmpp</type> |
| 2022 |
<urischeme>xmpp</urischeme> |
| 2023 |
<functionalspec> |
| 2024 |
<paragraph> |
| 2025 |
This Enumservice indicates that the |
| 2026 |
resource identified is an XMPP entity. |
| 2027 |
</paragraph> |
| 2028 |
</functionalspec> |
| 2029 |
<security> |
| 2030 |
See <xref type="rfc" data="<a href="./rfc4979">rfc4979</a>"/>, <a href="#section-6">Section 6</a>. |
| 2031 |
</security> |
| 2032 |
<usage>COMMON</usage> |
| 2033 |
<registrationdocs> |
| 2034 |
<xref type="rfc" data="<a href="./rfc4979">rfc4979</a>"/> |
| 2035 |
</registrationdocs> |
| 2036 |
<requesters> |
| 2037 |
<xref type="person" data="Alexander_Mayrhofer"/> |
| 2038 |
</requesters> |
| 2039 |
</record> |
| 2040 |
|
| 2041 |
<people> |
| 2042 |
<person id="Alexander_Mayrhofer"> |
| 2043 |
<name>Alexander Mayrhofer</name> |
| 2044 |
<org>enum.at GmbH</org> |
| 2045 |
<uri>mailto:[email protected]</uri> |
| 2046 |
<updated>2008-10-10</updated> |
| 2047 |
</person> |
| 2048 |
</people> |
| 2049 |
|
| 2050 |
|
| 2051 |
|
| 2052 |
|
| 2053 |
|
| 2054 |
|
| 2055 |
|
| 2056 |
|
| 2057 |
|
| 2058 |
|
| 2059 |
|
| 2060 |
|
| 2061 |
|
| 2062 |
|
| 2063 |
|
| 2064 |
|
| 2065 |
|
| 2066 |
|
| 2067 |
|
| 2068 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 37]</span></pre> |
| 2069 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span> |
| 2070 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 2071 |
|
| 2072 |
|
| 2073 |
This is the third example: |
| 2074 |
|
| 2075 |
<record> |
| 2076 |
<class>Application-Based</class> |
| 2077 |
<type>voicemsg</type> |
| 2078 |
<subtype>sip</subtype> |
| 2079 |
<urischeme>sip</urischeme> |
| 2080 |
<functionalspec> |
| 2081 |
<paragraph> |
| 2082 |
This Enumservice indicates that the resource |
| 2083 |
identified can be addressed by the associated |
| 2084 |
URI scheme in order to initiate a voice |
| 2085 |
communication session to a voice messaging system. |
| 2086 |
</paragraph> |
| 2087 |
</functionalspec> |
| 2088 |
<security> |
| 2089 |
See <xref type="rfc" data="<a href="./rfc4279">rfc4279</a>"/>, <a href="#section-3">Section 3</a>. |
| 2090 |
</security> |
| 2091 |
<usage>COMMON</usage> |
| 2092 |
<registrationdocs> |
| 2093 |
<xref type="rfc" data="<a href="./rfc4279">rfc4279</a>"/> |
| 2094 |
</registrationdocs> |
| 2095 |
<requesters> |
| 2096 |
<xref type="person" data="Jason_Livingood"/> |
| 2097 |
<xref type="person" data="Donald_Troshynski"/> |
| 2098 |
</requesters> |
| 2099 |
<additionalinfo> |
| 2100 |
<paragraph> |
| 2101 |
Implementers should review a non-exclusive list of |
| 2102 |
examples in <xref type="rfc" data="<a href="./rfc4279">rfc4279</a>"/>, |
| 2103 |
<a href="#section-7">Section 7</a>. |
| 2104 |
</paragraph> |
| 2105 |
</additionalinfo> |
| 2106 |
</record> |
| 2107 |
|
| 2108 |
<people> |
| 2109 |
<person id="Jason_Livingood"> |
| 2110 |
<name>Jason Livingood</name> |
| 2111 |
<org>Comcast Cable Communications</org> |
| 2112 |
<uri>mailto:[email protected]</uri> |
| 2113 |
<updated>2008-11-20</updated> |
| 2114 |
</person> |
| 2115 |
|
| 2116 |
|
| 2117 |
|
| 2118 |
|
| 2119 |
|
| 2120 |
|
| 2121 |
|
| 2122 |
|
| 2123 |
|
| 2124 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 38]</span></pre> |
| 2125 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span> |
| 2126 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 2127 |
|
| 2128 |
|
| 2129 |
<person id="Donald_Troshynski"> |
| 2130 |
<name>Donald Troshynski</name> |
| 2131 |
<org>Acme Packet</org> |
| 2132 |
<uri>mailto:[email protected]</uri> |
| 2133 |
<updated>2008-11-20</updated> |
| 2134 |
</person> |
| 2135 |
</people> |
| 2136 |
|
| 2137 |
In the third IANA Registration Template example above, the "voicemsg" |
| 2138 |
Enumservice is used. This Enumservice actually has several Subtypes, |
| 2139 |
and one of those is shown in the example. For each Subtype, an |
| 2140 |
individual Registration Template must be submitted to IANA, so that |
| 2141 |
an Enumservice with several Subtypes will have several corresponding |
| 2142 |
IANA Registration Templates. This is to avoid any ambiguity of the |
| 2143 |
relation between <subtype> and <urischeme> elements. |
| 2144 |
|
| 2145 |
<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. Changes from <a href="./rfc3761">RFC 3761</a></span> |
| 2146 |
|
| 2147 |
This section lists the changes applied to the Enumservice |
| 2148 |
registration process and the IANA registry definition, compared to |
| 2149 |
<a href="./rfc3761">RFC 3761</a>. |
| 2150 |
|
| 2151 |
o While <a href="./rfc3761">RFC 3761</a> required "Standards track or Experimental" RFCs for |
| 2152 |
an Enumservice to be registered, this document mandates |
| 2153 |
"Specification Required", which implies the use of a Designated |
| 2154 |
Expert. |
| 2155 |
|
| 2156 |
o This document defines the classification of Enumservices. The |
| 2157 |
IANA Registration Template has been complemented to contain a |
| 2158 |
<class> element (Enumservice Class). |
| 2159 |
|
| 2160 |
o A new element <registrationdocs> (Enumservice Specification) has |
| 2161 |
been added to the IANA Registration Template. |
| 2162 |
|
| 2163 |
o The former field "Any other information that the author deems |
| 2164 |
interesting" of the IANA Registration Template turned into the |
| 2165 |
<additionalinfo> element (Further Information). |
| 2166 |
|
| 2167 |
o The Enumservice "Name" field has been removed from the IANA |
| 2168 |
Registration Template. |
| 2169 |
|
| 2170 |
o The Registration Template is now a chunk of XML data, reflecting |
| 2171 |
IANA's recent work to convert registries to XML. |
| 2172 |
|
| 2173 |
|
| 2174 |
|
| 2175 |
|
| 2176 |
|
| 2177 |
|
| 2178 |
|
| 2179 |
|
| 2180 |
<span class="grey">Hoeneisen, et al. Standards Track [Page 39]</span></pre> |
| 2181 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span> |
| 2182 |
<span class="grey"><a href="./rfc6117">RFC 6117</a> IANA Registration of Enumservices March 2011</span> |
| 2183 |
|
| 2184 |
|
| 2185 |
Authors' Addresses |
| 2186 |
|
| 2187 |
Bernie Hoeneisen |
| 2188 |
Ucom Standards Track Solutions GmbH |
| 2189 |
CH-8000 Zuerich |
| 2190 |
Switzerland |
| 2191 |
|
| 2192 |
Phone: +41 44 500 52 44 |
| 2193 |
EMail: [email protected] (bernhard.hoeneisen AT ucom.ch) |
| 2194 |
URI: <a href="http://www.ucom.ch/">http://www.ucom.ch/</a> |
| 2195 |
|
| 2196 |
|
| 2197 |
Alexander Mayrhofer |
| 2198 |
enum.at GmbH |
| 2199 |
Karlsplatz 1/9 |
| 2200 |
Wien A-1010 |
| 2201 |
Austria |
| 2202 |
|
| 2203 |
Phone: +43 1 5056416 34 |
| 2204 |
EMail: [email protected] |
| 2205 |
URI: <a href="http://www.enum.at/">http://www.enum.at/</a> |
| 2206 |
|
| 2207 |
|
| 2208 |
Jason Livingood |
| 2209 |
Comcast Cable Communications |
| 2210 |
One Comcast Center |
| 2211 |
1701 John F. Kennedy Boulevard |
| 2212 |
Philadelphia, PA 19103 |
| 2213 |
USA |
| 2214 |
|
| 2215 |
Phone: +1-215-286-7813 |
| 2216 |
EMail: [email protected] |
| 2217 |
URI: <a href="http://www.comcast.com/">http://www.comcast.com/</a> |
| 2218 |
|
| 2219 |
|
| 2220 |
|
| 2221 |
|
| 2222 |
|
| 2223 |
|
| 2224 |
|
| 2225 |
|
| 2226 |
|
| 2227 |
|
| 2228 |
|
| 2229 |
|
| 2230 |
|
| 2231 |
|
| 2232 |
|
| 2233 |
|
| 2234 |
|
| 2235 |
|
| 2236 |
Hoeneisen, et al. Standards Track [Page 40] |
| 2237 |
</pre> |