| 1 |
<pre>Network Working Group A. Monrad |
| 2 |
Request for Comments: 5279 S. Loreto |
| 3 |
Category: Informational Ericsson |
| 4 |
July 2008 |
| 5 |
|
| 6 |
|
| 7 |
<span class="h1">A Uniform Resource Name (URN) Namespace</span> |
| 8 |
<span class="h1">for the 3rd Generation Partnership Project (3GPP)</span> |
| 9 |
|
| 10 |
Status of This Memo |
| 11 |
|
| 12 |
This memo provides information for the Internet community. It does |
| 13 |
not specify an Internet standard of any kind. Distribution of this |
| 14 |
memo is unlimited. |
| 15 |
|
| 16 |
Abstract |
| 17 |
|
| 18 |
This document describes the Namespace Identifier (NID) for Uniform |
| 19 |
Resource Namespace (URN) resources published by the 3rd Generation |
| 20 |
Partnership Project (3GPP). 3GPP defines and manages resources that |
| 21 |
utilize this URN name model. Management activities for these and |
| 22 |
other resource types are provided by the 3GPP Support Team. |
| 23 |
|
| 24 |
Table of Contents |
| 25 |
|
| 26 |
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a> |
| 27 |
<a href="#section-2">2</a>. URN Specification for the 3GPP Namespace Identifier (NID) . . . <a href="#page-2">2</a> |
| 28 |
<a href="#section-3">3</a>. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 29 |
<a href="#section-4">4</a>. Namespace Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 30 |
<a href="#section-5">5</a>. Community Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 31 |
<a href="#section-6">6</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 32 |
<a href="#section-7">7</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 33 |
<a href="#section-8">8</a>. Normative References . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 34 |
|
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Monrad & Loreto Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc5279">RFC 5279</a> URN Namespace for 3GPP July 2008</span> |
| 55 |
|
| 56 |
|
| 57 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 58 |
|
| 59 |
3GPP is a cooperation of international telecommunication standards |
| 60 |
bodies developing technologies for cellular networks. This activity |
| 61 |
is supported by a membership composed of network operators, equipment |
| 62 |
vendors, content providers, and other suppliers to the mobile market. |
| 63 |
|
| 64 |
Some of the technologies being developed by 3GPP need URN namespaces |
| 65 |
that are managed so that they are unique and persistent. To assure |
| 66 |
that the uniqueness is absolute, the registration of a specific NID |
| 67 |
for use by 3GPP was deemed appropriate. Therefore, a full and |
| 68 |
complete registration will follow the namespace specification process |
| 69 |
as defined in <a href="./rfc3406">RFC 3406</a> [<a href="./rfc3406" title=""Uniform Resource Names (URN) Namespace Definition Mechanisms"">RFC3406</a>]. |
| 70 |
|
| 71 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. URN Specification for the 3GPP Namespace Identifier (NID)</span> |
| 72 |
|
| 73 |
Namespace ID: |
| 74 |
|
| 75 |
3gpp |
| 76 |
|
| 77 |
Registration Information: |
| 78 |
|
| 79 |
registration version number: 1 |
| 80 |
registration date: 2007-11-16 |
| 81 |
|
| 82 |
Declared registrant of the namespace: |
| 83 |
|
| 84 |
Registering organization |
| 85 |
Name: 3rd Generation Partnership Project |
| 86 |
Address: ETSI |
| 87 |
Mobile Competence Centre |
| 88 |
650, route des Luciole |
| 89 |
06921 Sophia-Antipolis Cedex |
| 90 |
France |
| 91 |
|
| 92 |
Designated contact |
| 93 |
Role: Specifications Manager |
| 94 |
Email: [email protected] |
| 95 |
|
| 96 |
|
| 97 |
Declaration of syntactic structure: |
| 98 |
|
| 99 |
The Namespace Specific String (NSS) of all URNs that use the |
| 100 |
"3gpp" NID will have the following structure: |
| 101 |
|
| 102 |
urn:3gpp:{3gpp-urn} |
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Monrad & Loreto Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc5279">RFC 5279</a> URN Namespace for 3GPP July 2008</span> |
| 111 |
|
| 112 |
|
| 113 |
where the "3gpp-urn" is a US-ASCII string that conforms to the |
| 114 |
NSS(Namespace Specific String) Syntax described in <a href="./rfc2141">RFC 2141</a> |
| 115 |
[<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>] and defines a specific resource type. |
| 116 |
|
| 117 |
Relevant ancillary documentation: |
| 118 |
|
| 119 |
3GPP provides information on registration for each URN. More |
| 120 |
information about 3GPP and the registration activities and |
| 121 |
procedures to be followed are available at: |
| 122 |
|
| 123 |
<a href="http://www.3gpp.org/tb/Other/URN/URN.htm">http://www.3gpp.org/tb/Other/URN/URN.htm</a> |
| 124 |
|
| 125 |
Identifier uniqueness considerations: |
| 126 |
|
| 127 |
3GPP will manage resources using the "3gpp" NID and will be the |
| 128 |
authority for managing the "3gpp-urn" strings. In the associated |
| 129 |
procedures, 3GPP will ensure the uniqueness of the strings |
| 130 |
themselves or shall permit secondary responsibility for management |
| 131 |
of well-defined sub-trees. |
| 132 |
|
| 133 |
3GPP may permit use of experimental type values that will not be |
| 134 |
registered. As a consequence, multiple users may end up using the |
| 135 |
same value for separate uses. Unregistered type values will only |
| 136 |
be allowed in sub-namespaces clearly marked as experimental, to |
| 137 |
help implementors avoid "leaking" experimental values into real |
| 138 |
use. |
| 139 |
|
| 140 |
Identifier persistence considerations: |
| 141 |
|
| 142 |
3GPP will provide clear documentation of the registered uses of |
| 143 |
the "3gpp" NID. This will be structured such that each "3gpp- |
| 144 |
urn", if needed, will have a separate description and registration |
| 145 |
table. |
| 146 |
|
| 147 |
The registration tables and information will be published and |
| 148 |
maintained by 3GPP on its web site. |
| 149 |
|
| 150 |
Process of identifier assignment: |
| 151 |
|
| 152 |
3GPP will provide procedures for registration of each type of |
| 153 |
resource that it maintains. Each such resource may have three |
| 154 |
types of registration activities: |
| 155 |
|
| 156 |
1. Registered values associated with 3GPP specifications or |
| 157 |
services |
| 158 |
|
| 159 |
2. Registration of values or sub-trees to other entities |
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Monrad & Loreto Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc5279">RFC 5279</a> URN Namespace for 3GPP July 2008</span> |
| 167 |
|
| 168 |
|
| 169 |
3. Name models for use in experimental purposes |
| 170 |
|
| 171 |
New Namespace Identifier (NID) labels |
| 172 |
|
| 173 |
The Entries in the registration table will be the following: |
| 174 |
|
| 175 |
3gpp-urn: the registered value; |
| 176 |
Description: description of the registered value; |
| 177 |
Reference: 3GPP spec that defines the value; |
| 178 |
Contact: person requesting the URN assignment. |
| 179 |
|
| 180 |
Process for identifier resolution: |
| 181 |
|
| 182 |
The namespace is not listed with a Resolution Discovery System |
| 183 |
(RDS), as this is not relevant. |
| 184 |
|
| 185 |
Rules for Lexical Equivalence: |
| 186 |
|
| 187 |
No special considerations; the rules for lexical equivalence of |
| 188 |
<a href="./rfc2141">RFC 2141</a> [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>] apply. |
| 189 |
|
| 190 |
Conformance with URN Syntax: |
| 191 |
|
| 192 |
No special considerations. |
| 193 |
|
| 194 |
Validation mechanism: |
| 195 |
|
| 196 |
None specified. URN assignment will be handled by procedures |
| 197 |
supported and maintained by 3GPP. |
| 198 |
|
| 199 |
Scope: |
| 200 |
|
| 201 |
Global |
| 202 |
|
| 203 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Examples</span> |
| 204 |
|
| 205 |
The following examples are representative URNs that could be assigned |
| 206 |
by 3GPP. They are not actual strings that are assigned. |
| 207 |
|
| 208 |
urn:3gpp:featurephones |
| 209 |
|
| 210 |
Defines the "3gpp-urn" to be used for "featurephones". |
| 211 |
|
| 212 |
urn:3gpp:acme.foo-serv |
| 213 |
|
| 214 |
Defines the URN associated with the operator identified by the |
| 215 |
"3gpp-urn" value "acme", which has decided to register and provide |
| 216 |
information about its service identified by value "foo-serv". |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Monrad & Loreto Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc5279">RFC 5279</a> URN Namespace for 3GPP July 2008</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Namespace Considerations</span> |
| 226 |
|
| 227 |
The 3rd Generation Partnership Project is developing a variety of |
| 228 |
enablers and applications. Some of these require information to be |
| 229 |
fully specified. |
| 230 |
|
| 231 |
For proper operation, descriptions of the needed information must |
| 232 |
exist for the URNs and be available in a unique, reliable, and |
| 233 |
persistent manner. |
| 234 |
|
| 235 |
As 3GPP is ongoing and covers many technical areas, the possibility |
| 236 |
of binding to various other namespace repositories has been deemed |
| 237 |
impractical. Each object or description, as defined in 3GPP, could |
| 238 |
possibly be related to multiple different other namespaces, so |
| 239 |
further conflicts of association could occur. Thus, the intent is to |
| 240 |
utilize the 3GPP specifications manager as the naming authority for |
| 241 |
3GPP-defined URNs and its descriptions. |
| 242 |
|
| 243 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Community Considerations</span> |
| 244 |
|
| 245 |
The objects and descriptions required for enablers produced by 3GPP |
| 246 |
are generally available for use by other organizations. The 3rd |
| 247 |
Generation Partnership Project Support Office will provide access and |
| 248 |
support for name requests by these organizations. This support can |
| 249 |
be enabled in a timely and responsive fashion as new objects and |
| 250 |
descriptions are produced. |
| 251 |
|
| 252 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span> |
| 253 |
|
| 254 |
There are no security considerations other than those normally |
| 255 |
associated with the use and resolution of URNs in general. |
| 256 |
|
| 257 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span> |
| 258 |
|
| 259 |
This section registers a new URN NID with the registration provided |
| 260 |
in <a href="#section-2">Section 2</a>. |
| 261 |
|
| 262 |
"3gpp-urn" strings are identified by label managed by 3GPP. Thus, |
| 263 |
creating a new label does not require any IANA action. |
| 264 |
|
| 265 |
|
| 266 |
|
| 267 |
|
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Monrad & Loreto Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc5279">RFC 5279</a> URN Namespace for 3GPP July 2008</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Normative References</span> |
| 282 |
|
| 283 |
[<a id="ref-RFC3406">RFC3406</a>] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, |
| 284 |
"Uniform Resource Names (URN) Namespace Definition |
| 285 |
Mechanisms", <a href="https://www.rfc-editor.org/bcp/bcp66">BCP 66</a>, <a href="./rfc3406">RFC 3406</a>, October 2002. |
| 286 |
|
| 287 |
[<a id="ref-RFC2141">RFC2141</a>] Moats, R., "URN Syntax", <a href="./rfc2141">RFC 2141</a>, May 1997. |
| 288 |
|
| 289 |
Authors' Addresses |
| 290 |
|
| 291 |
Atle Monrad |
| 292 |
Ericsson |
| 293 |
Televeien 1 |
| 294 |
Grimstad 4898 |
| 295 |
Norway |
| 296 |
|
| 297 |
EMail: [email protected] |
| 298 |
|
| 299 |
|
| 300 |
Salvatore Loreto |
| 301 |
Ericsson |
| 302 |
Hirsalantie 11 |
| 303 |
Jorvas 02420 |
| 304 |
Finland |
| 305 |
|
| 306 |
EMail: [email protected] |
| 307 |
|
| 308 |
|
| 309 |
|
| 310 |
|
| 311 |
|
| 312 |
|
| 313 |
|
| 314 |
|
| 315 |
|
| 316 |
|
| 317 |
|
| 318 |
|
| 319 |
|
| 320 |
|
| 321 |
|
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Monrad & Loreto Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc5279">RFC 5279</a> URN Namespace for 3GPP July 2008</span> |
| 335 |
|
| 336 |
|
| 337 |
Full Copyright Statement |
| 338 |
|
| 339 |
Copyright (C) The IETF Trust (2008). |
| 340 |
|
| 341 |
This document is subject to the rights, licenses and restrictions |
| 342 |
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors |
| 343 |
retain all their rights. |
| 344 |
|
| 345 |
This document and the information contained herein are provided on an |
| 346 |
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS |
| 347 |
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND |
| 348 |
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS |
| 349 |
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF |
| 350 |
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED |
| 351 |
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 352 |
|
| 353 |
Intellectual Property |
| 354 |
|
| 355 |
The IETF takes no position regarding the validity or scope of any |
| 356 |
Intellectual Property Rights or other rights that might be claimed to |
| 357 |
pertain to the implementation or use of the technology described in |
| 358 |
this document or the extent to which any license under such rights |
| 359 |
might or might not be available; nor does it represent that it has |
| 360 |
made any independent effort to identify any such rights. Information |
| 361 |
on the procedures with respect to rights in RFC documents can be |
| 362 |
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>. |
| 363 |
|
| 364 |
Copies of IPR disclosures made to the IETF Secretariat and any |
| 365 |
assurances of licenses to be made available, or the result of an |
| 366 |
attempt made to obtain a general license or permission for the use of |
| 367 |
such proprietary rights by implementers or users of this |
| 368 |
specification can be obtained from the IETF on-line IPR repository at |
| 369 |
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>. |
| 370 |
|
| 371 |
The IETF invites any interested party to bring to its attention any |
| 372 |
copyrights, patents or patent applications, or other proprietary |
| 373 |
rights that may cover technology that may be required to implement |
| 374 |
this standard. Please address the information to the IETF at |
| 375 |
[email protected]. |
| 376 |
|
| 377 |
|
| 378 |
|
| 379 |
|
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
Monrad & Loreto Informational [Page 7] |
| 389 |
</pre> |