Network Working Group | B. Stark |
Internet-Draft | AT&T |
Intended status: Informational | D. Sinicrope |
Expires: October 6, 2016 | Ericsson |
W. Lupton | |
Broadband Forum | |
April 4, 2016 |
Uniform Resource Name (URN) Namespaces for Broadband Forum
draft-bbf-bbf-urn-01
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.
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 October 6, 2016.
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.
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 | Broadband Forum |
NID | Namespace Identifier |
NSS | Namespace Specific String |
RDS | Resolution Discovery System |
URN | Uniform Resource Name |
Namespace ID:
Registration Information:
Declared registrant of the namespace:
Declaration of syntactic structure:
Relevant ancillary documentation:
Identifier uniqueness considerations:
Identifier persistence considerations:
Process of identifier assignment:
Process for identifier resolution:
Rules for Lexical Equivalence:
Conformance with URN Syntax:
Validation mechanism:
Scope:
Namespace ID:
Registration Information:
Declared registrant of the namespace:
Declaration of syntactic structure:
Relevant ancillary documentation:
Identifier uniqueness considerations:
Identifier persistence considerations:
Process of identifier assignment:
Process for identifier resolution:
Rules for Lexical Equivalence:
Conformance with URN Syntax:
Validation mechanism:
Scope:
Namespace ID:
Registration Information:
Declared registrant of the namespace:
Declaration of syntactic structure:
Relevant ancillary documentation:
Identifier uniqueness considerations:
Identifier persistence considerations:
Process of identifier assignment:
Process for identifier resolution:
Rules for Lexical Equivalence:
Conformance with URN Syntax:
Validation mechanism:
Scope:
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.
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.
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.
This document adds threee new entries in the 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.
There are no additional security considerations other than those normally associated with the use and resolution of URNs in general.
The authors acknowledge that the text from [RFC6289] formed the basis for the initial version of this document.
[RFC2141] | Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141, May 1997. |
[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. |
[BBF-RESOURCES] | Broadband Forum, "Broadband Forum Assigned Names", 2016. |
[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. |
[TR-069] | Broadband Forum, "CPE WAN Management Protocol" |