Requests For Comments ... for the community
Welcome to OpenRFC
Home Full RFC index RFC humour Our technology
<< Previous <<      RFC 5279      >> Next >>    
A Uniform Resource Name (URN) Namespace for the 3rd Generation Partnership Project (3GPP).
A. Monrad, S. Loreto. July 2008.

[Direct link][Download PDF version][Download text version]

Network Working Group A. Monrad Request for Comments: 5279 S. Loreto Category: Informational Ericsson July 2008 A Uniform Resource Name (URN) Namespace for the 3rd Generation Partnership Project (3GPP) Status of This Memo This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Abstract This document describes the Namespace Identifier (NID) for Uniform Resource Namespace (URN) resources published by the 3rd Generation Partnership Project (3GPP). 3GPP defines and manages resources that utilize this URN name model. Management activities for these and other resource types are provided by the 3GPP Support Team. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. URN Specification for the 3GPP Namespace Identifier (NID) . . . 2 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Namespace Considerations . . . . . . . . . . . . . . . . . . . 5 5. Community Considerations . . . . . . . . . . . . . . . . . . . 5 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 8. Normative References . . . . . . . . . . . . . . . . . . . . . 6 Monrad & Loreto Informational [Page 1]
RFC 5279 URN Namespace for 3GPP July 2008 1. Introduction 3GPP is a cooperation of international telecommunication standards bodies developing technologies for cellular networks. This activity is supported by a membership composed of network operators, equipment vendors, content providers, and other suppliers to the mobile market. Some of the technologies being developed by 3GPP need URN namespaces that are managed so that they are unique and persistent. To assure that the uniqueness is absolute, the registration of a specific NID for use by 3GPP was deemed appropriate. Therefore, a full and complete registration will follow the namespace specification process as defined in RFC 3406 [RFC3406]. 2. URN Specification for the 3GPP Namespace Identifier (NID) Namespace ID: 3gpp Registration Information: registration version number: 1 registration date: 2007-11-16 Declared registrant of the namespace: Registering organization Name: 3rd Generation Partnership Project Address: ETSI Mobile Competence Centre 650, route des Luciole 06921 Sophia-Antipolis Cedex France Designated contact Role: Specifications Manager Email: Declaration of syntactic structure: The Namespace Specific String (NSS) of all URNs that use the "3gpp" NID will have the following structure: urn:3gpp:{3gpp-urn} Monrad & Loreto Informational [Page 2]
RFC 5279 URN Namespace for 3GPP July 2008 where the "3gpp-urn" is a US-ASCII string that conforms to the NSS(Namespace Specific String) Syntax described in RFC 2141 [RFC2141] and defines a specific resource type. Relevant ancillary documentation: 3GPP provides information on registration for each URN. More information about 3GPP and the registration activities and procedures to be followed are available at: Identifier uniqueness considerations: 3GPP will manage resources using the "3gpp" NID and will be the authority for managing the "3gpp-urn" strings. In the associated procedures, 3GPP will ensure the uniqueness of the strings themselves or shall permit secondary responsibility for management of well-defined sub-trees. 3GPP may permit use of experimental type values that will not be registered. As a consequence, multiple users may end up using the same value for separate uses. Unregistered type values will only be allowed in sub-namespaces clearly marked as experimental, to help implementors avoid "leaking" experimental values into real use. Identifier persistence considerations: 3GPP will provide clear documentation of the registered uses of the "3gpp" NID. This will be structured such that each "3gpp- urn", if needed, will have a separate description and registration table. The registration tables and information will be published and maintained by 3GPP on its web site. Process of identifier assignment: 3GPP will provide procedures for registration of each type of resource that it maintains. Each such resource may have three types of registration activities: 1. Registered values associated with 3GPP specifications or services 2. Registration of values or sub-trees to other entities Monrad & Loreto Informational [Page 3]
RFC 5279 URN Namespace for 3GPP July 2008 3. Name models for use in experimental purposes New Namespace Identifier (NID) labels The Entries in the registration table will be the following: 3gpp-urn: the registered value; Description: description of the registered value; Reference: 3GPP spec that defines the value; Contact: person requesting the URN assignment. Process for identifier resolution: The namespace is not listed with a Resolution Discovery System (RDS), as this is not relevant. Rules for Lexical Equivalence: No special considerations; the rules for lexical equivalence of RFC 2141 [RFC2141] apply. Conformance with URN Syntax: No special considerations. Validation mechanism: None specified. URN assignment will be handled by procedures supported and maintained by 3GPP. Scope: Global 3. Examples The following examples are representative URNs that could be assigned by 3GPP. They are not actual strings that are assigned. urn:3gpp:featurephones Defines the "3gpp-urn" to be used for "featurephones". Defines the URN associated with the operator identified by the "3gpp-urn" value "acme", which has decided to register and provide information about its service identified by value "foo-serv". Monrad & Loreto Informational [Page 4]
RFC 5279 URN Namespace for 3GPP July 2008 4. Namespace Considerations The 3rd Generation Partnership Project is developing a variety of enablers and applications. Some of these require information to be fully specified. For proper operation, descriptions of the needed information must exist for the URNs and be available in a unique, reliable, and persistent manner. As 3GPP is ongoing and covers many technical areas, the possibility of binding to various other namespace repositories has been deemed impractical. Each object or description, as defined in 3GPP, could possibly be related to multiple different other namespaces, so further conflicts of association could occur. Thus, the intent is to utilize the 3GPP specifications manager as the naming authority for 3GPP-defined URNs and its descriptions. 5. Community Considerations The objects and descriptions required for enablers produced by 3GPP are generally available for use by other organizations. The 3rd Generation Partnership Project Support Office will provide access and support for name requests by these organizations. This support can be enabled in a timely and responsive fashion as new objects and descriptions are produced. 6. Security Considerations There are no security considerations other than those normally associated with the use and resolution of URNs in general. 7. IANA Considerations This section registers a new URN NID with the registration provided in Section 2. "3gpp-urn" strings are identified by label managed by 3GPP. Thus, creating a new label does not require any IANA action. Monrad & Loreto Informational [Page 5]
RFC 5279 URN Namespace for 3GPP July 2008 8. Normative References [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, October 2002. [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. Authors' Addresses Atle Monrad Ericsson Televeien 1 Grimstad 4898 Norway EMail: Salvatore Loreto Ericsson Hirsalantie 11 Jorvas 02420 Finland EMail: Monrad & Loreto Informational [Page 6]
RFC 5279 URN Namespace for 3GPP July 2008 Full Copyright Statement Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at Monrad & Loreto Informational [Page 7]


[Home] [Full RFC index] [RFC humour] [Our technology]

Copyright © Inter-Corporate Computer & Network Services, Inc.  All rights reserved.
All trademarks and RFC contents are the property of their respective owners.