A Uniform Resource Name (URN) Namespace for the 3rd Generation Partnership Project (3GPP)
RFC 5279
Document | Type |
RFC - Informational
(July 2008; Errata)
Was draft-monrad-sipping-3gpp-urn-namespace (individual in gen area)
|
|
---|---|---|---|
Authors | Atle Monrad , Salvatore Loreto | ||
Last updated | 2020-01-21 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized with errata bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 5279 (Informational) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Lisa Dusseault | ||
Send notices to | leslie@thinkingcat.com |
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: john.meredith@etsi.org 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: http://www.3gpp.org/tb/Other/URN/URN.htm 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.Show full document text