8057
INFORMATIONAL
Uniform Resource Name (URN) Namespaces for Broadband Forum
Authors: B. Stark, D. Sinicrope, W. Lupton
Date: January 2017
Working Group: NON WORKING GROUP
Stream: IETF
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.
RFC 8057
INFORMATIONAL
Internet Engineering Task Force (IETF) B. Stark
Request for Comments: 8057 AT&T
Category: Informational D. Sinicrope
ISSN: 2070-1721 Ericsson
W. Lupton
Broadband Forum
January 2017
<span class="h1">Uniform Resource Name (URN) Namespaces for Broadband Forum</span>
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 document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc8057">http://www.rfc-editor.org/info/rfc8057</a>.
<span class="grey">Stark, et al. Informational [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc8057">RFC 8057</a> URN Namespaces for Broadband Forum January 2017</span>
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-1.1">1.1</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2">2</a>. bbf Registration . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3">3</a>. broadband-forum-org Registration . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-4">4</a>. dslforum-org Registration . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-5">5</a>. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-6">6</a>. Namespace Considerations . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-7">7</a>. Community Considerations . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-8">8</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-9">9</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-10">10</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-10.1">10.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-10.2">10.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
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 that address 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
<span class="grey">Stark, et al. Informational [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc8057">RFC 8057</a> URN Namespaces for Broadband Forum January 2017</span>
Uniform Resource Name (URN) [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>] Namespace Identifiers (NIDs)
for use by BBF are being specified in this document, in full
conformance with the NID registration process specified in [<a href="./rfc3406" title=""Uniform Resource Names (URN) Namespace Definition Mechanisms"">RFC3406</a>].
The "bbf" NID is for new work efforts related to data models for
protocols other than the Customer Premises Equipment (CPE) WAN
Management Protocol (CWMP) [<a href="#ref-TR-069" title=""CPE WAN Management Protocol"">TR-069</a>]. The "broadband-forum-org" and
"dslforum-org" NIDs are used for all data models related to CWMP
[<a href="#ref-TR-069" title=""CPE WAN Management Protocol"">TR-069</a>]. BBF has used the 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.
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology</span>
+-----+-----------------------------+
| BBF | Broadband Forum |
| NID | Namespace Identifier |
| NSS | Namespace Specific String |
| RDS | Resolution Discovery System |
| URN | Uniform Resource Name |
+-----+-----------------------------+
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. bbf Registration</span>
Namespace ID:
bbf
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: [email protected]
<span class="grey">Stark, et al. Informational [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc8057">RFC 8057</a> URN Namespaces for Broadband Forum January 2017</span>
Declaration of syntactic structure:
The syntax of namespace-specific strings for the "bbf" namespace
is <NSS> in [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>].
Relevant ancillary documentation:
BBF publishes information regarding the registered resources on
the BBF Assigned Resources web page [<a href="#ref-BBF-RESOURCES">BBF-RESOURCES</a>].
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
[<a href="#ref-BBF-RESOURCES">BBF-RESOURCES</a>] to document the registered resources that use the
"bbf" NID.
Process of identifier assignment:
BBF procedures for URN assignment are provided at [<a href="#ref-BBF-RESOURCES">BBF-RESOURCES</a>].
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
[<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>] apply.
Conformance with URN Syntax:
No special considerations.
<span class="grey">Stark, et al. Informational [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc8057">RFC 8057</a> URN Namespaces for Broadband Forum January 2017</span>
Validation mechanism:
None specified. URN assignment will be handled by procedures
implemented in support of BBF activities.
Scope:
Global
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. broadband-forum-org Registration</span>
Namespace ID:
broadband-forum-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: [email protected]
Declaration of syntactic structure:
The syntax of namespace-specific strings for the
"broadband-forum-org" namespace is <NSS> in [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>].
Relevant ancillary documentation:
BBF publishes information regarding the registered resources on
the BBF Assigned Resources web page [<a href="#ref-BBF-RESOURCES">BBF-RESOURCES</a>].
<span class="grey">Stark, et al. Informational [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc8057">RFC 8057</a> URN Namespaces for Broadband Forum January 2017</span>
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
[<a href="#ref-BBF-RESOURCES">BBF-RESOURCES</a>] to document the registered resources that use the
"broadband-forum-org" NID.
Process of identifier assignment:
BBF procedures for URN assignment are provided at [<a href="#ref-BBF-RESOURCES">BBF-RESOURCES</a>].
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
[<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>] 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
<span class="grey">Stark, et al. Informational [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc8057">RFC 8057</a> URN Namespaces for Broadband Forum January 2017</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. dslforum-org Registration</span>
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: [email protected]
Declaration of syntactic structure:
The syntax of namespace-specific strings for the "dslforum-org"
namespace is <NSS> in [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>].
Relevant ancillary documentation:
BBF publishes information regarding the registered resources on
the BBF Assigned Resources web page [<a href="#ref-BBF-RESOURCES">BBF-RESOURCES</a>].
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.
<span class="grey">Stark, et al. Informational [Page 7]</span><span id="page-8" ></span>
<span class="grey"><a href="./rfc8057">RFC 8057</a> URN Namespaces for Broadband Forum January 2017</span>
Identifier persistence considerations:
BBF will update the BBF Assigned Resources web page
[<a href="#ref-BBF-RESOURCES">BBF-RESOURCES</a>] to document the registered resources that use the
"dslforum-org" NID.
Process of identifier assignment:
BBF procedures for URN assignment are provided at [<a href="#ref-BBF-RESOURCES">BBF-RESOURCES</a>].
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
[<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>] 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
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Examples</span>
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.
<span class="grey">Stark, et al. Informational [Page 8]</span><span id="page-9" ></span>
<span class="grey"><a href="./rfc8057">RFC 8057</a> URN Namespaces for Broadband Forum January 2017</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Namespace Considerations</span>
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"
NIDs have been used for many years by BBF without formal
registration. (Broadband Forum changed its name from DSL Forum in
2008.) As they are referenced by multiple BBF specifications
currently in common use, BBF is formalizing them. The new "bbf" NID
will be used for new work efforts that are not enhancements, updates,
or extensions to work that currently makes use of the "broadband-
forum-org" and "dslforum-org" NIDs.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Community Considerations</span>
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: [<a href="#ref-BBF-RESOURCES">BBF-RESOURCES</a>]. BBF will also maintain the corresponding
specifications where the registered resources are referenced or used.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
This document adds three new entries in the formal urn-namespaces
registry. The namespaces are "bbf", "broadband-forum-org", and
"dslforum-org". This is the defining document. The entries can be
found at <<a href="http://www.iana.org/assignments/urn-namespaces">http://www.iana.org/assignments/urn-namespaces</a>> and any
associated mirrors.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Security Considerations</span>
There are no additional security considerations other than those
normally associated with the use and resolution of URNs in general.
<span class="grey">Stark, et al. Informational [Page 9]</span><span id="page-10" ></span>
<span class="grey"><a href="./rfc8057">RFC 8057</a> URN Namespaces for Broadband Forum January 2017</span>
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span>
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative References</span>
[<a id="ref-RFC2141">RFC2141</a>] Moats, R., "URN Syntax", <a href="./rfc2141">RFC 2141</a>, DOI 10.17487/RFC2141,
May 1997, <<a href="https://www.rfc-editor.org/info/rfc2141">http://www.rfc-editor.org/info/rfc2141</a>>.
[<a id="ref-RFC3406">RFC3406</a>] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
"Uniform Resource Names (URN) Namespace Definition
Mechanisms", <a href="https://www.rfc-editor.org/bcp/bcp66">BCP 66</a>, <a href="./rfc3406">RFC 3406</a>, DOI 10.17487/RFC3406,
October 2002, <<a href="https://www.rfc-editor.org/info/rfc3406">http://www.rfc-editor.org/info/rfc3406</a>>.
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span>
[<a id="ref-BBF-RESOURCES">BBF-RESOURCES</a>]
Broadband Forum, "Broadband Forum Assigned Names", 2016,
<<a href="http://www.broadband-forum.org/assignments">http://www.broadband-forum.org/assignments</a>>.
[<a id="ref-RFC6289">RFC6289</a>] Cardona, E., Channabasappa, S., and J-F. Mule, "A Uniform
Resource Name (URN) Namespace for CableLabs", <a href="./rfc6289">RFC 6289</a>,
DOI 10.17487/RFC6289, June 2011,
<<a href="https://www.rfc-editor.org/info/rfc6289">http://www.rfc-editor.org/info/rfc6289</a>>.
[<a id="ref-TR-069">TR-069</a>] Broadband Forum, "CPE WAN Management Protocol",
<<a href="http://www.broadband-forum.org/technical/trlist.php">http://www.broadband-forum.org/technical/trlist.php</a>>.
<span class="grey">Stark, et al. Informational [Page 10]</span><span id="page-11" ></span>
<span class="grey"><a href="./rfc8057">RFC 8057</a> URN Namespaces for Broadband Forum January 2017</span>
Acknowledgements
The authors acknowledge that the text from [<a href="./rfc6289" title=""A Uniform Resource Name (URN) Namespace for CableLabs"">RFC6289</a>] 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.
Authors' Addresses
Barbara Stark
AT&T
Atlanta, GA
United States of America
Email: [email protected]
David Sinicrope
Ericsson
Cary, NC
United States of America
Email: [email protected]
William Lupton
Broadband Forum
United Kingdom
Email: [email protected]
Stark, et al. Informational [Page 11]
Annotations
Select text to annotate