RFC 8057

Uniform Resource Name (URN) Namespaces for Broadband Forum

📅 published January 2017, from ietf

Title Block 🎀

Okay bestie, this is RFC 8057, and it's called "Uniform Resource Name (URN) Namespaces for Broadband Forum" 🦋 It's an IETF document from January 2017. Its category is Informational, which means it's published for information and is not an Internet Standards Track spec ✨ The ISSN is 2070-1721, and the RFC number is 8057.

The authors are B. Stark from AT&T, D. Sinicrope from Ericsson, and W. Lupton from the Broadband Forum 💜 The title block doesn't list anything this RFC obsoletes or updates, so there's no drama there 🙈

Abstract ✨

This doc describes three URN Namespace Identifiers (NIDs), "bbf", "broadband-forum-org", and "dslforum-org", for URNs that identify resources published by the Broadband Forum (BBF) 💖 BBF specifies and manages the resources that use these three URN identification models. Management of these and other resource types is handled by BBF 🌸

Status of This Memo 🧚

Okay, the status part is important: this document is not an Internet Standards Track specification. It's published for informational purposes 📚

It's a product of the Internet Engineering Task Force (IETF) 🫶 It represents the consensus of the IETF community, got public review, and was approved for publication by the Internet Engineering Steering Group (IESG). Not every IESG-approved doc is a candidate for any level of Internet Standard, so check out Section 2 of RFC 7841 if you want the deets 💅

For the current status, any errata, and how to send feedback, go to http://www.rfc-editor.org/info/rfc8057 ✨

Copyright Notice 🌈

This doc is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) as they stand on the publication date. Read these carefully, bestie, because they explain your rights and restrictions with regard to this document 🧐 Any Code Components pulled out of this document must include Simplified BSD License text, as described in Section 4.e of the Trust Legal Provisions, and they come with no warranty, as described in the Simplified BSD License 🔥

Table of Contents 🍓

1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
  1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
2.  bbf Registration  . . . . . . . . . . . . . . . . . . . . . .   3
3.  broadband-forum-org Registration  . . . . . . . . . . . . . .   5
4.  dslforum-org Registration . . . . . . . . . . . . . . . . . .   7
5.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   8
6.  Namespace Considerations  . . . . . . . . . . . . . . . . . .   9
7.  Community Considerations  . . . . . . . . . . . . . . . . . .   9
8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
9.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
  10.1.  Normative References . . . . . . . . . . . . . . . . . .  10
  10.2.  Informative References . . . . . . . . . . . . . . . . .  10
Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  11
Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1. Introduction 🦋

Okay so, the Broadband Forum (BBF) is a non-profit industry alliance 💖 It drives broadband wireline solutions and helps converged packet networks worldwide meet the needs of vendors, service providers, and their customers. BBF writes multi-service broadband packet networking specs covering interoperability, architecture, and management. Its work powers home, business, and converged broadband services, across customer, access, and backbone networks ✨

Sometimes BBF spec efforts need identifiers from a managed namespace so they stay unique and persistent 🎀 To make sure that uniqueness is absolute, three specific Uniform Resource Name (URN) [RFC2141] Namespace Identifiers (NIDs) are being specified for BBF in this document, following the NID registration process in full conformance with [RFC3406] 💅

The "bbf" NID is for new work related to data models for protocols other than the CPE WAN Management Protocol (CWMP) [TR-069] 🧚 The "broadband-forum-org" and "dslforum-org" NIDs are used for all data models related to CWMP [TR-069]. BBF has been using those last two NIDs for years without formally registering them, and it has published widely implemented specs that use them 🙈 The "dslforum-org" NID was already in use before the organization changed its name from DSL Forum to Broadband Forum in 2008 👑

1.1. Terminology 💜

+-----+-----------------------------+
| BBF | Broadband Forum             |
| NID | Namespace Identifier        |
| NSS | Namespace Specific String   |
| RDS | Resolution Discovery System |
| URN | Uniform Resource Name       |
+-----+-----------------------------+

2. bbf Registration 🌸

Here's the "bbf" registration, bestie 💖 Let's go through it field by field:

Namespace ID: bbf

Registration Information: registration version number 1, registration date 2016-12-05.

Declared registrant of the namespace: the registering organization is Broadband Forum, at 5177 Brandin Court, Fremont, CA 94538, USA 🏢 The designated contact has the role "Manager, Namespace" and can be reached at help@broadband-forum.org 💌

Declaration of syntactic structure: the syntax of namespace-specific strings for the "bbf" namespace is <NSS> in [RFC2141] ✨

Relevant ancillary documentation: BBF publishes info about the registered resources on the BBF Assigned Resources web page [BBF-RESOURCES] 📖

Identifier uniqueness considerations: BBF will manage resource classes using the "bbf" NID, and it'll be the authority for managing resources and the strings that come after them. BBF is expected to guarantee the uniqueness of the strings themselves, or it may permit secondary responsibility for certain defined resources 🔥

BBF may, at the namespace resource manager's discretion, designate or allocate experimental type values for testing purposes only. Heads up: using experimental types may create collisions, since multiple users may end up using the same values for resources and specific strings ⚠️

Identifier persistence considerations: BBF will update the BBF Assigned Resources web page [BBF-RESOURCES] to document the registered resources that use the "bbf" NID 🦋

Process of identifier assignment: BBF procedures for URN assignment are provided at [BBF-RESOURCES] 🧚

Process for identifier resolution: the namespace isn't listed with a resolution discovery system, so this doesn't apply to this URN registration 🙅‍♀️

Rules for Lexical Equivalence: no special considerations. The rules for lexical equivalence of [RFC2141] apply ✨

Conformance with URN Syntax: no special considerations 💅

Validation mechanism: none specified. URN assignment is handled by procedures implemented in support of BBF activities 🎀

Scope: Global 🌍

3. broadband-forum-org Registration 💜

Next up is the "broadband-forum-org" registration, and it's giving a lot of the same energy 👑 Here are the fields:

Namespace ID: broadband-forum-org

Registration Information: registration version number 1, registration date 2016-12-05.

Declaration of syntactic structure: the syntax of namespace-specific strings for the "broadband-forum-org" namespace is <NSS> in [RFC2141] ✨

Relevant ancillary documentation: BBF publishes info about the registered resources on the BBF Assigned Resources web page [BBF-RESOURCES] 📖

Identifier uniqueness considerations: BBF will manage resource classes using the "broadband-forum-org" NID, and it'll be the authority for managing resources and the strings that come after them. BBF is expected to guarantee the uniqueness of the strings themselves, or it may permit secondary responsibility for certain defined resources 🔥

Identifier persistence considerations: BBF will update the BBF Assigned Resources web page [BBF-RESOURCES] to document the registered resources that use the "broadband-forum-org" NID 🦋

Process of identifier assignment: BBF procedures for URN assignment are provided at [BBF-RESOURCES] 🧚

Process for identifier resolution: the namespace isn't listed with a resolution discovery system, so this doesn't apply to this URN registration 🙅‍♀️

Rules for Lexical Equivalence: no special considerations. The rules for lexical equivalence of [RFC2141] apply ✨

Conformance with URN Syntax: no special considerations 💅

Validation mechanism: none specified. URN assignment is handled by procedures implemented in support of BBF activities 🎀

Scope: Global 🌍

Part 1 of 2 💖 Part 2 is coming, so stay tuned!

4. dslforum-org Registration ✨

okay so this is the registration form for the "dslforum-org" NID 💖 the whole thing is in one block below so you can see every field exactly as written, bestie 🎀

Namespace ID:

   dslforum-org

   Registration Information:

      registration version number: 1
      registration date: 2016-12-05

   Declared registrant of the namespace:

      Registering organization

      Name: Broadband Forum
      Address: 5177 Brandin Court, Fremont, CA 94538, USA

      Designated contact

      Role: Manager, Namespace
      Email: help@broadband-forum.org

   Declaration of syntactic structure:

      The syntax of namespace-specific strings for the "dslforum-org"
      namespace is <NSS> in [RFC2141].

   Relevant ancillary documentation:

      BBF publishes information regarding the registered resources on
      the BBF Assigned Resources web page [BBF-RESOURCES].

   Identifier uniqueness considerations:

      BBF will manage resource classes using the "dslforum-org" NID and
      will be the authority for managing resources and associated
      subsequent strings.  BBF is expected to guarantee the uniqueness
      of the strings themselves, or it may permit secondary
      responsibility for certain defined resources.

      BBF may, at the namespace resource manager's discretion,
      designate/allocate experimental type values for testing purposes
      only.  Note that using experimental types may create collisions,
      as multiple users may use the same values for resources and
      specific strings.

   Identifier persistence considerations:

      BBF will update the BBF Assigned Resources web page
      [BBF-RESOURCES] to document the registered resources that use the
      "dslforum-org" NID.

   Process of identifier assignment:

      BBF procedures for URN assignment are provided at [BBF-RESOURCES].

   Process for identifier resolution:

      The namespace is not listed with a resolution discovery system;
      this is not applicable for this URN registration.

   Rules for Lexical Equivalence:

      No special considerations; the rules for lexical equivalence of
      [RFC2141] apply.

   Conformance with URN Syntax:

      No special considerations.

   Validation mechanism:

      None specified.  URN assignment will be handled by procedures
      implemented in support of BBF activities.

   Scope:

      Global

5. Examples 🌸

okay, so these are the hypothetical URNs that BBF could end up assigning, just to show you what they'd look like in the wild 👀

urn:broadband-forum-org:cwmp:datamodel-1-5

urn:bbf:yang:fast

the first one is for CPE WAN Management Protocol (CWMP) data models that follow the rules of BBF's CWMP suite of specifications, and that's giving very organised energy 🧚

6. Namespace Considerations 💜

so BBF makes a whole bunch of specs that need data models, and URN namespaces are the thing that keeps those data model definitions reliable, persistent, and unique. literally the backbone 🦋

authors who want to keep track of different versions of URNs, and the dependencies between those URNs across different versions of BBF specs, can also use URNs to do that, if they want to 💅

there are three NIDs defined here. The "broadband-forum-org" and "dslforum-org" NIDs have been used by BBF for many years without any formal registration. (Broadband Forum changed its name from DSL Forum in 2008.) since lots of BBF specs that are in common use reference them, BBF is making it official 🎀 the new "bbf" NID is for new work that isn't an enhancement, update, or extension of anything already using "broadband-forum-org" or "dslforum-org" 🌈

7. Community Considerations 🫶

people who build and use Broadband Forum specs are going to be so happy about this, because the namespace gives them consistent, reliable names for XML namespaces, schema locations, and similar identifiers for physical data models published in BBF specs ✨

the BBF specs are publicly available, and they're licensed to manufacturers on a reasonable and nondiscriminatory basis. BBF will keep the resource allocations for the "bbf", "broadband-forum-org", and "dslforum-org" NIDs at this publicly viewable location: [BBF-RESOURCES]. BBF will also keep the matching specs up to date wherever the registered resources are referenced or used 🍓

8. IANA Considerations 🦋

this document adds three new entries to the formal urn-namespaces registry: "bbf", "broadband-forum-org", and "dslforum-org". this is the defining document for them, and you can find the entries at <http://www.iana.org/assignments/urn-namespaces> and any associated mirrors 🧚

9. Security Considerations 💀

okay the security part is short but it's important 😭 there are no additional security considerations beyond the ones that normally come with using and resolving URNs in general 🔥

10. References 👑

10.1. Normative References

[RFC2141]  Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141,
           May 1997, <http://www.rfc-editor.org/info/rfc2141>.

[RFC3406]  Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
           "Uniform Resource Names (URN) Namespace Definition
           Mechanisms", BCP 66, RFC 3406, DOI 10.17487/RFC3406,
           October 2002, <http://www.rfc-editor.org/info/rfc3406>.

10.2. Informative References

[BBF-RESOURCES]
           Broadband Forum, "Broadband Forum Assigned Names", 2016,
           <http://www.broadband-forum.org/assignments>.

[RFC6289]  Cardona, E., Channabasappa, S., and J-F. Mule, "A Uniform
           Resource Name (URN) Namespace for CableLabs", RFC 6289,
           DOI 10.17487/RFC6289, June 2011,
           <http://www.rfc-editor.org/info/rfc6289>.

[TR-069]   Broadband Forum, "CPE WAN Management Protocol",
           <http://www.broadband-forum.org/technical/trlist.php>.

Acknowledgements 🫶

the authors want to say that the text from [RFC6289] was the base for the first version of this document 💖 huge thanks to Mahesh Jethanandani, Al Morton, Joel Halpern, and Yaron Sheffer for their review and guidance, which was so appreciated 🌸

Authors' Addresses 💜

Barbara Stark
AT&T
Atlanta, GA
United States of America

Email: barbara.stark@att.com


David Sinicrope
Ericsson
Cary, NC
United States of America

Email: david.sinicrope@ericsson.com


William Lupton
Broadband Forum
United Kingdom

Email: wlupton@broadband-forum.org

📦 where this page comes from

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