Uniform Resource Name (URN) Namespaces for Broadband Forum
draft-bbf-bbf-urn-04

Abstract

This document describes the Namespace Identifiers (NIDs) 'bbf', 'broadband-forum-org', and 'dslforum-org' for Uniform Resource Names (URNs) used to identify resources published by Broadband Forum (BBF). BBF specifies and manages resources that utilize these three URN identification models. Management activities for these and other resource types are handled by BBF.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on May 29, 2017.

Copyright Notice

Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

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

1. Introduction

Broadband Forum (BBF) is a non-profit industry alliance driving broadband wireline solutions and empowering converged packet networks worldwide to better meet the needs of vendors, service providers and their customers. BBF develops multi-service broadband packet networking specifications addressing interoperability, architecture and management. Its work enables home, business and converged broadband services; encompassing customer, access and backbone networks.

Occasionally, BBF specification efforts require identifiers in a managed namespace so that they are unique and persistent. To ensure that the uniqueness is absolute, the registration of three specific Uniform Resource Name (URN) [RFC2141] Namespace IDs (NID) for use by BBF are being specified in this document, in full conformance with the NID registration process specified in [RFC3406].

The 'bbf' NID is for new work efforts related to data models for protocols other than its 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 used these latter two NIDs for many years without formally registering them and has published widely-implemented specifications that use these NIDs. Use of the 'dslforum-org' NID started prior the organization's 2008 name change from DSL Forum to Broadband Forum.

1.1. Terminology

2. bbf Registration

Namespace ID:

• bbf

Registration Information:

• registration version number: 1
  registration date: YYYY-MM-DD [RFC Editor: Please replace YYYY-MM-DD with the date of approval of this document for publication as an RFC.]

Declared registrant of the namespace:

• Registering organization

• Name: Broadband Forum
  Address: 48377 Fremont Boulevard, #117, 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 'bbf' 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 "bbf" 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 "bbf" 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

3. broadband-forum-org Registration

Namespace ID:

• broadband-forum-org

Registration Information:

• registration version number: 1
  registration date: YYYY-MM-DD [RFC Editor: Please replace YYYY-MM-DD with the date of approval of this document for publication as an RFC.]

Declared registrant of the namespace:

• Registering organization

• Name: Broadband Forum
  Address: 48377 Fremont Boulevard, #117, 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 'broadband-forum-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 "broadband-forum-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 "broadband-forum-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

4. dslforum-org Registration

Namespace ID:

• dslforum-org

Registration Information:

• registration version number: 1
  registration date: YYYY-MM-DD [RFC Editor: Please replace YYYY-MM-DD with the date of approval of this document for publication as an RFC.]

Declared registrant of the namespace:

• Registering organization

• Name: Broadband Forum
  Address: 48377 Fremont Boulevard, #117, 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. Example

The following examples represent hypothetical URNs that could be assigned by BBF.

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

urn:bbf:yang:fast

The first of these defines an URN to be used for CPE WAN Management Protocol (CWMP) data models conforming to rules for BBF's CWMP suite of specifications.

6. Namespace Considerations

BBF develops various specifications that require the use of data models. URN Namespaces are key constructs to manage the definitions of those data models reliably with persistence and uniqueness.

The use of URNs should also help specification authors to maintain different versions of URNs and dependencies between URNs, across different versions of BBF specifications, if they so wish.

Three NIDs are defined. The "broadband-forum-org" and "dslforum-org" (Broadband Forum changed its name from DSL Forum in 2008) NIDs have been used for many years by BBF without formal registration. As they are referenced by multiple BBF specifications currently in common use, BBF is requesting to formalize them. The new "bbf" NID will be used for new work efforts.

7. Community Considerations

Participants involved in the development and usage of Broadband Forum specifications will benefit from the publication of this namespace by providing consistent and reliable names for the XML namespaces, schema locations, and similar identifiers of physical data models published within BBF specifications.

The BBF specifications are publicly available and are licensed to manufacturers on a reasonable and nondiscriminatory basis. BBF will maintain the allocation of resources for the "bbf", "broadband-forum-org", and "dslforum-org" NIDs at the following publicly-viewable location: [BBF-RESOURCES]. BBF will also maintain the corresponding specifications where the registered resources are referenced or used.

8. IANA Considerations

This document adds three new entries in the formal urn-namespaces registry. The namespaces should be "bbf", "broadband-forum-org", and "dslforum-org". This is the defining document. The entries can be found at: http://www.iana.org/assignments/urn-namespaces and any associated mirrors.

9. Security Considerations

There are no additional security considerations other than those normally associated with the use and resolution of URNs in general.

10. Acknowledgements

The authors acknowledge that the text from [RFC6289] formed the basis for the initial version of this document. Review and guidance from Mahesh Jethanandani, Al Morton, Joel Halpern, and Yaron Sheffer were much appreciated.

11. References

11.1. Normative References

11.2. Informative References

Authors' Addresses