RFC 5279

A Uniform Resource Name (URN) Namespace for the 3rd Generation Partnership Project (3GPP)

📅 published July 2008, from ietf

RFC 5279 💖 A Uniform Resource Name (URN) Namespace for the 3rd Generation Partnership Project (3GPP)

okay bestie, the title block first! 🎀 This is from the Network Working Group, written by Atle Monrad and Salvatore Loreto (both at Ericsson 💅). It's Informational, dated July 2008. The header doesn't list anything it obsoletes or updates, so it's standing on its own ✨

Status of This Memo ✨

Okay so this one is just here to inform you, not to set any Internet standard 🫶 Distribution is totally unlimited, so share it with everyone 💜

Abstract 🦋

This doc defines the Namespace Identifier (NID) for URN resources published by the 3rd Generation Partnership Project (3GPP). 3GPP makes and manages resources that use this URN name model, and the 3GPP Support Team handles management for these and other resource types 🧚

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

1. Introduction 🍓

3GPP is a team-up of international telecom standards bodies that build the tech behind cellular networks 📱 It's backed by members like network operators, equipment vendors, content providers, and other suppliers in the mobile market, so it's a whole ecosystem 👑

Some of the stuff 3GPP is building needs URN namespaces that are managed so they stay unique and persistent 🔥 To make the uniqueness absolute, registering a specific NID for 3GPP felt like the right move. A full and complete registration will follow the namespace specification process defined in RFC 3406 [RFC3406] 💅

2. URN Specification for the 3GPP Namespace Identifier (NID) 🎀

Here's the full spec, bestie, so take notes 📝

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 every URN that uses the "3gpp" NID will look like this 🦋

      urn:3gpp:{3gpp-urn}

The "3gpp-urn" part is a US-ASCII string that follows the NSS (Namespace Specific String) Syntax from RFC 2141 [RFC2141] and names one specific resource type ✨

Relevant ancillary documentation:

3GPP shares info about registering each URN. You can find more about 3GPP, the registration activities, and the procedures to follow at:

      http://www.3gpp.org/tb/Other/URN/URN.htm

Identifier uniqueness considerations:

3GPP manages resources under the "3gpp" NID and is the authority for the "3gpp-urn" strings 👑 In its procedures, 3GPP will make sure the strings themselves are unique, or it shall let secondary parties manage well-defined sub-trees.

3GPP may allow experimental type values that never get registered. That means multiple users might end up using the same value for different things, which is a little chaotic 💀 Unregistered type values are only allowed in sub-namespaces that are clearly marked experimental, so implementers don't accidentally let experimental values "leak" into real use 🙈

Identifier persistence considerations:

3GPP will clearly document the registered uses of the "3gpp" NID 📚 The docs will be structured so each "3gpp-urn" gets its own description and registration table, if it needs one.

3GPP publishes and maintains the registration tables and info on its website 🌈

Process of identifier assignment:

3GPP provides procedures for registering each type of resource it maintains. Each resource can have three kinds of registration activity:

Registered values tied to 3GPP specifications or services
Registration of values or sub-trees for other entities
Name models for experimental purposes

New Namespace Identifier (NID) labels:

The registration table entries are:

      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 isn't listed with a Resolution Discovery System (RDS), since that isn't relevant here 🤷‍♀️

Rules for Lexical Equivalence:

No special considerations. The lexical equivalence rules from RFC 2141 [RFC2141] apply ✨

Conformance with URN Syntax:

No special considerations 💖

Validation mechanism:

None specified. URN assignment is handled by procedures that 3GPP supports and maintains 🫶

Scope:

Global 🌍

3. Examples 🧚

These are representative URNs that 3GPP could assign. They are not actual assigned strings, so don't go copying them into prod 😭

urn:3gpp:featurephones

This defines the "3gpp-urn" to be used for "featurephones" 📞

urn:3gpp:acme.foo-serv

This defines the URN for the operator identified by the "3gpp-urn" value "acme", which has decided to register and provide info about its service identified by the value "foo-serv" 💅

4. Namespace Considerations 🌸

3GPP is building a whole bunch of enablers and applications, and some of them need their information fully specified 🔥

For things to work properly, descriptions of that needed information have to exist for the URNs, and they have to be available in a unique, reliable, and persistent way 💜

3GPP covers a LOT of technical areas, so binding to various other namespace repositories was deemed impractical 😅 Each object or description defined in 3GPP could be related to several other namespaces, which could cause more association conflicts. So the plan is to have the 3GPP specifications manager act as the naming authority for 3GPP-defined URNs and their descriptions 👑

5. Community Considerations 🦋

The objects and descriptions needed for 3GPP enablers are generally available for other organizations to use 🌈 The 3rd Generation Partnership Project Support Office gives those organizations access and support for name requests, and that support can happen quickly as new objects and descriptions come out ✨

6. Security Considerations 💀

There are no security considerations other than those normally associated with the use and resolution of URNs in general. Stay safe and handle URNs the usual way 🔒

7. IANA Considerations 🎀

This section registers a new URN NID using the registration from Section 2 📝

The "3gpp-urn" strings are identified by a label that 3GPP manages, so creating a new label doesn't need any IANA action 💅

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: atle.monrad@ericsson.com


Salvatore Loreto
Ericsson
Hirsalantie 11
Jorvas  02420
Finland

EMail: Salvatore.Loreto@ericsson.com

Full Copyright Statement ⭐

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 doesn't take a position on whether any Intellectual Property Rights or other rights claimed to cover the technology in this document are valid or in scope, or whether any license under those rights would be available. It also doesn't say it has tried independently to find any such rights 🧐 For info on how rights work for RFC documents, check BCP 78 and BCP 79.

Copies of IPR disclosures sent to the IETF Secretariat, plus any assurances of licenses, or the results of an attempt to get a general license or permission for implementers or users to use those proprietary rights, are available from the IETF's online IPR repository at http://www.ietf.org/ipr 📂

The IETF invites anyone to point out any copyrights, patents, patent applications, or other proprietary rights that might cover technology needed to implement this standard. Send that info to the IETF at ietf-ipr@ietf.org 💌

That's the whole RFC, bestie! 🌈✨💖

📦 where this page comes from

ietf: rfc5279 2008-07
💖 girlified by claude-haiku-5-5 on 2026-10-17: a language model's rewrite of the original, under its terms