idnits 2.17.1 draft-bbf-bbf-urn-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (November 25, 2016) is 2709 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 2141 (Obsoleted by RFC 8141) ** Obsolete normative reference: RFC 3406 (Obsoleted by RFC 8141) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group B. Stark 3 Internet-Draft AT&T 4 Intended status: Informational D. Sinicrope 5 Expires: May 29, 2017 Ericsson 6 W. Lupton 7 Broadband Forum 8 November 25, 2016 10 Uniform Resource Name (URN) Namespaces for Broadband Forum 11 draft-bbf-bbf-urn-04 13 Abstract 15 This document describes the Namespace Identifiers (NIDs) 'bbf', 16 'broadband-forum-org', and 'dslforum-org' for Uniform Resource Names 17 (URNs) used to identify resources published by Broadband Forum (BBF). 18 BBF specifies and manages resources that utilize these three URN 19 identification models. Management activities for these and other 20 resource types are handled by BBF. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on May 29, 2017. 39 Copyright Notice 41 Copyright (c) 2016 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 58 2. bbf Registration . . . . . . . . . . . . . . . . . . . . . . 3 59 3. broadband-forum-org Registration . . . . . . . . . . . . . . 5 60 4. dslforum-org Registration . . . . . . . . . . . . . . . . . . 6 61 5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 62 6. Namespace Considerations . . . . . . . . . . . . . . . . . . 8 63 7. Community Considerations . . . . . . . . . . . . . . . . . . 9 64 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 65 9. Security Considerations . . . . . . . . . . . . . . . . . . . 9 66 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 67 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 68 11.1. Normative References . . . . . . . . . . . . . . . . . . 9 69 11.2. Informative References . . . . . . . . . . . . . . . . . 10 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 72 1. Introduction 74 Broadband Forum (BBF) is a non-profit industry alliance driving 75 broadband wireline solutions and empowering converged packet networks 76 worldwide to better meet the needs of vendors, service providers and 77 their customers. BBF develops multi-service broadband packet 78 networking specifications addressing interoperability, architecture 79 and management. Its work enables home, business and converged 80 broadband services; encompassing customer, access and backbone 81 networks. 83 Occasionally, BBF specification efforts require identifiers in a 84 managed namespace so that they are unique and persistent. To ensure 85 that the uniqueness is absolute, the registration of three specific 86 Uniform Resource Name (URN) [RFC2141] Namespace IDs (NID) for use by 87 BBF are being specified in this document, in full conformance with 88 the NID registration process specified in [RFC3406]. 90 The 'bbf' NID is for new work efforts related to data models for 91 protocols other than its CPE WAN Management Protocol (CWMP) [TR-069]. 92 The 'broadband-forum-org' and 'dslforum-org' NIDs are used for all 93 data models related to CWMP [TR-069]. BBF has used these latter two 94 NIDs for many years without formally registering them and has 95 published widely-implemented specifications that use these NIDs. Use 96 of the 'dslforum-org' NID started prior the organization's 2008 name 97 change from DSL Forum to Broadband Forum. 99 1.1. Terminology 101 +-----+-----------------------------+ 102 | BBF | Broadband Forum | 103 | NID | Namespace Identifier | 104 | NSS | Namespace Specific String | 105 | RDS | Resolution Discovery System | 106 | URN | Uniform Resource Name | 107 +-----+-----------------------------+ 109 2. bbf Registration 111 Namespace ID: 113 bbf 115 Registration Information: 117 registration version number: 1 118 registration date: YYYY-MM-DD [RFC Editor: Please replace YYYY-MM- 119 DD with the date of approval of this document for publication as 120 an RFC.] 122 Declared registrant of the namespace: 124 Registering organization 126 Name: Broadband Forum 127 Address: 48377 Fremont Boulevard, #117, Fremont, CA 94538, USA 129 Designated contact 131 Role: Manager, Namespace 132 Email: help@broadband-forum.org 134 Declaration of syntactic structure: 136 The syntax of namespace specific strings for the 'bbf' namespace 137 is in [RFC2141]. 139 Relevant ancillary documentation: 141 BBF publishes information regarding the registered resources on 142 the BBF Assigned Resources web page [BBF-RESOURCES]. 144 Identifier uniqueness considerations: 146 BBF will manage resource classes using the "bbf" NID and will be 147 the authority for managing resources and associated subsequent 148 strings. BBF is expected to guarantee the uniqueness of the 149 strings themselves or it may permit secondary responsibility for 150 certain defined resources. 152 BBF may, at the namespace resource manager's discretion, 153 designate/allocate experimental type values for testing purposes 154 only. Note that using experimental types may create collisions as 155 multiple users may use the same values for resources and specific 156 strings. 158 Identifier persistence considerations: 160 BBF will update the BBF Assigned Resources web page 161 [BBF-RESOURCES] to document the registered resources that use the 162 "bbf" NID. 164 Process of identifier assignment: 166 BBF procedures for URN assignment are provided at [BBF-RESOURCES]. 168 Process for identifier resolution: 170 The namespace is not listed with a resolution discovery system; 171 this is not applicable for this URN registration. 173 Rules for Lexical Equivalence: 175 No special considerations; the rules for lexical equivalence of 176 [RFC2141] apply. 178 Conformance with URN Syntax: 180 No special considerations. 182 Validation mechanism: 184 None specified. URN assignment will be handled by procedures 185 implemented in support of BBF activities. 187 Scope: 189 Global 191 3. broadband-forum-org Registration 193 Namespace ID: 195 broadband-forum-org 197 Registration Information: 199 registration version number: 1 200 registration date: YYYY-MM-DD [RFC Editor: Please replace YYYY-MM- 201 DD with the date of approval of this document for publication as 202 an RFC.] 204 Declared registrant of the namespace: 206 Registering organization 208 Name: Broadband Forum 209 Address: 48377 Fremont Boulevard, #117, Fremont, CA 94538, USA 211 Designated contact 213 Role: Manager, Namespace 214 Email: help@broadband-forum.org 216 Declaration of syntactic structure: 218 The syntax of namespace specific strings for the 'broadband-forum- 219 org' namespace is in [RFC2141]. 221 Relevant ancillary documentation: 223 BBF publishes information regarding the registered resources on 224 the BBF Assigned Resources web page [BBF-RESOURCES]. 226 Identifier uniqueness considerations: 228 BBF will manage resource classes using the "broadband-forum-org" 229 NID and will be the authority for managing resources and 230 associated subsequent strings. BBF is expected to guarantee the 231 uniqueness of the strings themselves or it may permit secondary 232 responsibility for certain defined resources. 234 BBF may, at the namespace resource manager's discretion, 235 designate/allocate experimental type values for testing purposes 236 only. Note that using experimental types may create collisions as 237 multiple users may use the same values for resources and specific 238 strings. 240 Identifier persistence considerations: 242 BBF will update the BBF Assigned Resources web page 243 [BBF-RESOURCES] to document the registered resources that use the 244 "broadband-forum-org" NID. 246 Process of identifier assignment: 248 BBF procedures for URN assignment are provided at [BBF-RESOURCES]. 250 Process for identifier resolution: 252 The namespace is not listed with a resolution discovery system; 253 this is not applicable for this URN registration. 255 Rules for Lexical Equivalence: 257 No special considerations; the rules for lexical equivalence of 258 [RFC2141] apply. 260 Conformance with URN Syntax: 262 No special considerations. 264 Validation mechanism: 266 None specified. URN assignment will be handled by procedures 267 implemented in support of BBF activities. 269 Scope: 271 Global 273 4. dslforum-org Registration 275 Namespace ID: 277 dslforum-org 279 Registration Information: 281 registration version number: 1 282 registration date: YYYY-MM-DD [RFC Editor: Please replace YYYY-MM- 283 DD with the date of approval of this document for publication as 284 an RFC.] 286 Declared registrant of the namespace: 288 Registering organization 290 Name: Broadband Forum 291 Address: 48377 Fremont Boulevard, #117, Fremont, CA 94538, USA 293 Designated contact 295 Role: Manager, Namespace 296 Email: help@broadband-forum.org 298 Declaration of syntactic structure: 300 The syntax of namespace specific strings for the 'dslforum-org' 301 namespace is in [RFC2141]. 303 Relevant ancillary documentation: 305 BBF publishes information regarding the registered resources on 306 the BBF Assigned Resources web page [BBF-RESOURCES]. 308 Identifier uniqueness considerations: 310 BBF will manage resource classes using the "dslforum-org" NID and 311 will be the authority for managing resources and associated 312 subsequent strings. BBF is expected to guarantee the uniqueness 313 of the strings themselves or it may permit secondary 314 responsibility for certain defined resources. 316 BBF may, at the namespace resource manager's discretion, 317 designate/allocate experimental type values for testing purposes 318 only. Note that using experimental types may create collisions as 319 multiple users may use the same values for resources and specific 320 strings. 322 Identifier persistence considerations: 324 BBF will update the BBF Assigned Resources web page 325 [BBF-RESOURCES] to document the registered resources that use the 326 "dslforum-org" NID. 328 Process of identifier assignment: 330 BBF procedures for URN assignment are provided at [BBF-RESOURCES]. 332 Process for identifier resolution: 334 The namespace is not listed with a resolution discovery system; 335 this is not applicable for this URN registration. 337 Rules for Lexical Equivalence: 339 No special considerations; the rules for lexical equivalence of 340 [RFC2141] apply. 342 Conformance with URN Syntax: 344 No special considerations. 346 Validation mechanism: 348 None specified. URN assignment will be handled by procedures 349 implemented in support of BBF activities. 351 Scope: 353 Global 355 5. Example 357 The following examples represent hypothetical URNs that could be 358 assigned by BBF. 360 urn:broadband-forum-org:cwmp:datamodel-1-5 362 urn:bbf:yang:fast 364 The first of these defines an URN to be used for CPE WAN Management 365 Protocol (CWMP) data models conforming to rules for BBF's CWMP suite 366 of specifications. 368 6. Namespace Considerations 370 BBF develops various specifications that require the use of data 371 models. URN Namespaces are key constructs to manage the definitions 372 of those data models reliably with persistence and uniqueness. 374 The use of URNs should also help specification authors to maintain 375 different versions of URNs and dependencies between URNs, across 376 different versions of BBF specifications, if they so wish. 378 Three NIDs are defined. The "broadband-forum-org" and "dslforum-org" 379 (Broadband Forum changed its name from DSL Forum in 2008) NIDs have 380 been used for many years by BBF without formal registration. As they 381 are referenced by multiple BBF specifications currently in common 382 use, BBF is requesting to formalize them. The new "bbf" NID will be 383 used for new work efforts. 385 7. Community Considerations 387 Participants involved in the development and usage of Broadband Forum 388 specifications will benefit from the publication of this namespace by 389 providing consistent and reliable names for the XML namespaces, 390 schema locations, and similar identifiers of physical data models 391 published within BBF specifications. 393 The BBF specifications are publicly available and are licensed to 394 manufacturers on a reasonable and nondiscriminatory basis. BBF will 395 maintain the allocation of resources for the "bbf", "broadband-forum- 396 org", and "dslforum-org" NIDs at the following publicly-viewable 397 location: [BBF-RESOURCES]. BBF will also maintain the corresponding 398 specifications where the registered resources are referenced or used. 400 8. IANA Considerations 402 This document adds three new entries in the formal urn-namespaces 403 registry. The namespaces should be "bbf", "broadband-forum-org", and 404 "dslforum-org". This is the defining document. The entries can be 405 found at: http://www.iana.org/assignments/urn-namespaces and any 406 associated mirrors. 408 9. Security Considerations 410 There are no additional security considerations other than those 411 normally associated with the use and resolution of URNs in general. 413 10. Acknowledgements 415 The authors acknowledge that the text from [RFC6289] formed the basis 416 for the initial version of this document. Review and guidance from 417 Mahesh Jethanandani, Al Morton, Joel Halpern, and Yaron Sheffer were 418 much appreciated. 420 11. References 422 11.1. Normative References 424 [RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141, 425 May 1997, . 427 [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, 428 "Uniform Resource Names (URN) Namespace Definition 429 Mechanisms", BCP 66, RFC 3406, DOI 10.17487/RFC3406, 430 October 2002, . 432 11.2. Informative References 434 [BBF-RESOURCES] 435 Broadband Forum, "Broadband Forum Assigned Names", 2016, 436 . 438 [RFC6289] Cardona, E., Channabasappa, S., and J-F. Mule, "A Uniform 439 Resource Name (URN) Namespace for CableLabs", RFC 6289, 440 DOI 10.17487/RFC6289, June 2011, 441 . 443 [TR-069] Broadband Forum, "CPE WAN Management Protocol", 444 . 446 Authors' Addresses 448 Barbara Stark 449 AT&T 450 Atlanta, GA 451 US 453 Email: barbara.stark@att.com 455 David Sinicrope 456 Ericsson 457 Cary, NC 458 US 460 Email: david.sinicrope@ericsson.com 462 William Lupton 463 Broadband Forum 464 UK 466 Email: wlupton@broadband-forum.org