RFC 4358

A Uniform Resource Name (URN) Namespace for the Open Mobile Alliance (OMA)

📅 published January 2006, from ietf

RFC 4358: A Uniform Resource Name (URN) Namespace for the Open Mobile Alliance (OMA) 💖

Okay bestie, the title block is giving main character energy 🎀. Dwight Smith wrote this one for the Open Mobile Alliance (OMA), under the Network Working Group 🦋. It's filed as Informational, so it's sharing information and is not an Internet standard 🫶. It's dated January 2006, and it doesn't obsolete or update any other RFC.

Status of This Memo 📜

No cap, this part is just the legal-ish vibe check. The memo is for the Internet community as information only. It does not specify an Internet standard of any kind, and distribution is unlimited ✨.

Copyright Notice ©️

Abstract 🌈

Okay so this doc describes the Namespace Identifier (NID) for URN resources published by OMA 💅. OMA defines and manages resources that use this URN name model, and the Open Mobile Naming Authority (OMNA) handles management for these and other resource types 🧚.

Table of Contents 🍓

   1. Introduction ....................................................2
   2. URN Specification for "oma" NID .................................2
   3. Examples ........................................................4
   4. Namespace Considerations ........................................4
   5. Community Considerations ........................................5
   6. Security Considerations .........................................5
   7. IANA Considerations .............................................5
   8. Informative References ..........................................5

1. Introduction 🫶

OMA is a specification development body that builds technologies for mobile devices 📱. It's backed by a membership of network operators, equipment vendors, content providers, and other suppliers in the mobile market 💜.

Some OMA technologies need XML namespaces that are managed so they stay unique and persistent 🔥. To make the uniqueness absolute, registering a specific NID for OMA was seen as the right move 👑. So a full and complete registration will follow the namespace specification process defined in [RFC3406] ✨.

2. URN Specification for "oma" NID 🎀

This is the big spec section, so let's go step by step 💅.

Namespace ID

The NID "oma" is requested 🦋.

Registration Information

registration version number: 1
registration date:           2005-07-18

Declared registrant of the namespace

Registering organization
   Name:    Open Mobile Alliance
   Address: 4275 Executive Square
            Suite 240s
            La Jolla, CA 92037

Designated contact
   Role:    Technical Program Manager
   Email:   TPM@omaorg.org

Declaration of syntactic structure

Every URN that uses the "oma" NID has a Namespace Specific String (NSS) with this structure 🌸:

urn:oma:{OMAresource}:{ResourceSpecificString}

The "OMAresource" part is a US-ASCII string that follows the URN syntax requirements in [RFC2141], and it names a specific class of resource type 🧚. Each resource type has its own labeling scheme, which lives in "ResourceSpecificString". That part also has to follow the naming requirements of [RFC2141] 💖.

OMA keeps a naming authority, the Open Mobile Naming Authority (OMNA) ✨. OMNA is the one that manages the assignment of "OMAresources" and the specific registration values for each resource class 👑.

Relevant ancillary documentation

OMNA shares info on the registered resources and the registrations for each one 📚. You can find more about OMNA, plus the registration activities and procedures, at:

http://www.openmobilealliance.org/tech/omna

Identifier uniqueness considerations

OMNA manages resources under the "oma" NID, and it's the authority for those resources and the strings tied to them 🔥. Through its procedures, OMNA makes sure the strings themselves are unique, or it allows secondary responsibility for well-defined sub-trees 🫶.

OMA may allow experimental type values that won't be registered 🧪. That means several users could end up using the same value for different things. Since experimental usage is only meant for testing, this shouldn't be a real issue 😌.

Identifier persistence considerations

OMNA documents the registered uses of the "oma" NID clearly 📖. Each OMAresource gets its own description and registration table 💅.

OMNA publishes and maintains the registration tables and info on its web site 🌐.

Process of identifier assignment

OMNA provides procedures for registering each type of resource it maintains 🦋. Each resource may have three kinds of registration activity 🎀:

1) Registered values associated with OMA specs or services
2) Registration of values or sub-trees to other entities
3) Name models for use in experimental purposes

Process for identifier resolution

The namespace isn't listed with an RDS, and that's not relevant here 🙈.

Rules for Lexical Equivalence

No special considerations. The rules for lexical equivalence in [RFC2141] apply 💜.

Conformance with URN Syntax

No special considerations 🌸.

Validation mechanism

None specified. URN assignment is handled by procedures set up to support OMNA activities 🧚.

Scope

Global 🌍

3. Examples 🍓

Okay these are representative URNs that OMNA could assign. They might not be the actual strings that end up getting assigned, so don't take them as gospel 🙈.

urn:oma:ac:oma-presence
urn:oma:drms:org-foobar

urn:oma:ac:oma-presence is the URN for the Application Characteristic object definition, which gives attributes to the Presence enabler defined in OMA ✨.

urn:oma:drms:org-foobar is the URN for the Digital Rights Management System object definition allocated to foobar 🔐. Foobar is an external organization that asked OMNA for a drms URN 🫶.

4. Namespace Considerations 🌈

OMA is building a bunch of application and service enablers 🚀. Some of these need their supporting info (like data descriptions and attributes) fully specified 📋. For things to work properly, those descriptions have to exist and be available in a unique, reliable, and persistent way 💎. That dependency is the reason namespaces are needed, one way or another 💅.

OMA's work is ongoing and covers lots of technical areas 🌸. So binding to the various other namespace repositories was judged impractical 🙅‍♀️. Each object or description defined in OMA could be related to several different namespaces, which could create more conflicts of association 😭. So the plan is to use the Open Mobile Naming Authority, operated by OMA, as the naming authority for OMA-defined objects and descriptions 👑.

5. Community Considerations 🫶

The objects and descriptions needed for enablers OMA produces are generally available for other organizations to use 🌍. OMNA will provide access and support for name requests from those organizations ✨. That support can be delivered in a timely and responsive way as new objects and descriptions come out 🦋. It'll work in a similar way to current OMNA support 💖.

6. Security Considerations 🔐

Okay, real talk, there are no additional security considerations beyond the ones that normally come with using and resolving URNs in general 🛡️.

7. IANA Considerations 🧚

The requested NID has been entered into the IANA registry for URN NIDs 🎉. You can find the update at:

http://www.iana.org/assignments/urn-namespaces

and at any associated mirrors 🌸.

8. Informative References 📚

[RFC2141]   Moats, R., "URN Syntax", RFC 2141, May 1997.

[RFC3406]   Daigle, L., van Gulik, D., Iannella, R., and P.
            Faltstrom, "Uniform Resource Names (URN) Namespace
            Definition Mechanisms", BCP 66, RFC 3406, October 2002.

Author's Address 🖋️

Dwight Smith (Chair, Operations and Process Committee, OMA)
Motorola
5555 N Beach Street
Ft. Worth, TX  76137

EMail: dwight.smith@motorola.com

This document is subject to the rights, licenses, and restrictions in BCP 78. Except as BCP 78 sets out, the authors keep all their rights 🎀.

The document and the info in it are provided "AS IS" 😬. The contributor, the organization they represent or are sponsored by (if any), the Internet Society, and the Internet Engineering Task Force all disclaim every warranty, express or implied 💀. That includes, but isn't limited to, any warranty that using the info won't infringe any rights, and any implied warranties of merchantability or fitness for a particular purpose ⚠️.

Intellectual Property 🦋

The IETF takes no position on the validity or scope of any Intellectual Property Rights or other rights that someone might claim apply to implementing or using the technology in this document 🤷‍♀️. It also doesn't say whether any license under those rights is or isn't available, and it hasn't independently tried to find any such rights 🙈. The procedures for rights in RFC documents are in BCP 78 and BCP 79 📜.

Copies of IPR disclosures sent to the IETF Secretariat, plus any assurances of licenses to be made available, or the results of an attempt to get a general license or permission for implementers or users, are available from the IETF's online IPR repository:

http://www.ietf.org/ipr

The IETF invites anyone interested to bring to its attention any copyrights, patents, patent applications, or other proprietary rights that might cover technology needed to implement this standard. Send that info to ietf-ipr@ietf.org 📬.

Acknowledgement 🌷

Funding for the RFC Editor function comes from the IETF Administrative Support Activity (IASA) 💖.

📦 where this page comes from

ietf: rfc4358 2006-01
💖 girlified by claude-haiku-5-5 on 2026-10-16: a language model's rewrite of the original, under its terms