idnits 2.17.1 draft-cardona-cablelabs-urn-07.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 seems to contain a disclaimer for pre-RFC5378 work, and may have content which was first submitted before 10 November 2008. The disclaimer is necessary when there are original authors that you have been unable to contact, or if some do not wish to grant the BCP78 rights to the IETF Trust. If you are able to get all authors (current and original) to grant those rights, you can and should remove the disclaimer; otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 14, 2011) is 4792 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 (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group E. Cardona 3 Internet-Draft S. Channabasappa 4 Intended status: Informational J-F. Mule 5 Expires: September 15, 2011 CableLabs 6 March 14, 2011 8 A Uniform Resource Name (URN) Namespace for CableLabs 9 draft-cardona-cablelabs-urn-07 11 Abstract 13 This document describes the Namespace Identifier (NID) 'cablelabs' 14 for Uniform Resource Names (URNs) used to identify resources 15 published by Cable Television Laboratories, Inc. (CableLabs). 16 CableLabs specifies and manages resources that utilize this URN 17 identification model. Management activities for these and other 18 resource types are handled by the manager of the CableLabs' Assigned 19 Names and Numbers registry. 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on September 15, 2011. 38 Copyright Notice 40 Copyright (c) 2011 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 This document may contain material from IETF Documents or IETF 54 Contributions published or made publicly available before November 55 10, 2008. The person(s) controlling the copyright in some of this 56 material may not have granted the IETF Trust the right to allow 57 modifications of such material outside the IETF Standards Process. 58 Without obtaining an adequate license from the person(s) controlling 59 the copyright in such materials, this document may not be modified 60 outside the IETF Standards Process, and derivative works of it may 61 not be created outside the IETF Standards Process, except to format 62 it for publication as an RFC or to translate it into languages other 63 than English. 65 Table of Contents 67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 68 2. URN Specification for CableLabs . . . . . . . . . . . . . . . . 3 69 3. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 70 4. Namespace Considerations . . . . . . . . . . . . . . . . . . . 5 71 5. Community Considerations . . . . . . . . . . . . . . . . . . . 5 72 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 73 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 74 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 75 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 76 9.1. Normative References . . . . . . . . . . . . . . . . . . . 6 77 9.2. Informative References . . . . . . . . . . . . . . . . . . 6 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 80 1. Introduction 82 CableLabs is a non-profit research and development consortium that is 83 dedicated to pursuing new cable telecommunications technologies and 84 to helping its cable operator members integrate those technical 85 advancements into their business objectives. Within CableLabs, 86 specification activities are organized into projects such as 87 DOCSIS(R), PacketCable(TM), and OpenCable(TM), and technical work is 88 conducted within focus teams. Product vendors, manufacturers, and 89 cable operator members are invited to join the focus teams that 90 create technical specifications. 92 Occasionally, CableLabs specification efforts require identifiers in 93 a managed namespace so that they are unique and persistent. To 94 ensure that the uniqueness is absolute, the registration of a 95 specific Uniform Resource Name (URN) [RFC2141] Namespace ID (NID) for 96 use by CableLabs is being specified in this document, in full 97 conformance with the NID registration process specified in [RFC3406]. 99 2. URN Specification for CableLabs 101 Namespace ID: 102 cablelabs 104 Registration Information: 105 registration version number: 1 106 registration date: YYYY-MM-DD [RFC Editor: Please replace YYYY- 107 MM-DD with the date of approval of this document for publication 108 as an RFC.] 110 Declared registrant of the namespace: 111 Registering organization 112 Name: Cable Television Laboratories, Inc. 113 Address: 858 Coal Creek Circle, Louisville, CO 80027, USA 114 Designated contact 115 Role: Manager, Standards 116 Email: ietf_standards@cablelabs.com 118 Declaration of syntactic structure: 119 The Namespace Specific String (NSS) of all URNs that use the 120 "cablelabs" NID will have the following structure: 122 {CLclass}:{CLClassSpecificString} 124 The "CLclass" is a US-ASCII string that conforms to the URN 125 syntax requirements specified in [RFC2141] and defines a 126 specific class of resource type. Each class will have a 127 specific labeling scheme that is covered by 128 "CLClassSpecificString", which also conforms to the naming 129 requirements of [RFC2141]. 130 CableLabs maintains the CableLabs Assigned Names and Numbers 131 [CANN] specification that will contain the assignment of 132 CableLabs resource classes, and the specific registration values 133 assigned for each resource class. 135 Relevant ancillary documentation: 136 CableLabs publishes information regarding the registered 137 resources in the CableLabs' Assigned Names and Numbers 138 specification ([CANN]). 140 Identifier uniqueness considerations: 141 CableLabs will manage resource classes using the "cablelabs" NID 142 and will be the authority for managing resources and subsequent 143 strings associated. CableLabs is expected to guarantee the 144 uniqueness of the strings themselves or it may permit secondary 145 responsibility for certain defined resources. 146 CableLabs could allow the use of experimental type values for 147 testing purposes only. Note that using experimental types may 148 create collisions as multiple users may use the same values for 149 resources and specific strings. 151 Identifier persistence considerations: 152 CableLabs will update the CableLabs' Assigned Names and Numbers 153 specification (ref: [CANN]) to document the registered resources 154 that use the "cablelabs" NID. 156 Process of identifier assignment: 157 CableLabs will provide procedures for registration of each type 158 of resource that it maintains. Each such resource may have 159 three types of registration activities: 160 1. Registered values associated with CableLabs documents or 161 services 162 2. Registration of values or sub-trees to other entities 163 3. Name models for use in experimental purposes 165 Process for identifier resolution: 166 The namespace is not listed with a resolution discovery system; 167 this is not applicable for this URN registration. 169 Rules for Lexical Equivalence: 170 No special considerations; the rules for lexical equivalence of 171 [RFC2141] apply. 173 Conformance with URN Syntax: 175 No special considerations. 177 Validation mechanism: 178 None specified. URN assignment will be handled by procedures 179 implemented in support of CableLabs activities. 181 Scope: 182 Global 184 3. Example 186 The following example represents a hypothetical URN that could be 187 assigned by CableLabs. 189 urn:cablelabs:packetcable-example:ue:rst-sample 191 Defines the URN to be used for User Equipment (UE) conforming to the 192 sample Residential SIP Telephony (RST) application specified within 193 CableLabs' PacketCable RST specification suite. 195 4. Namespace Considerations 197 CableLabs develops specifications that may require the use of data 198 models. URN Namespaces are key constructs to manage the definitions 199 of those data models reliably with persistence and uniqueness. 201 The use of URNs should also help specification authors to maintain 202 different versions of URNs and dependencies between urns, across 203 different versions of CableLabs specifications, if they so wish. 205 5. Community Considerations 207 Participants involved in the development and usage of CableLabs 208 specifications, and cable industry deployments will benefit from the 209 publication of this namespace by providing consistent and reliable 210 names for the XML namespaces, schema locations, and similar 211 identifiers of physical data models published within CableLabs 212 specifications. 214 The CableLabs specifications are publicly available and are licensed 215 to manufacturers on a nondiscriminatory basis. CableLabs will 216 maintain the allocation of resources for the "cablelabs" NID within 217 the following specification: [CANN], which will be publicly available 218 for viewing. CableLabs will also maintain the corresponding 219 specifications where the registered resources are referenced or used. 221 6. IANA Considerations 223 This document adds a new entry in the urn-namespaces registry. The 224 namespace should be "cablelabs". This is the defining document. The 225 entry can be found at: http://www.iana.org/assignments/urn-namespaces 226 and any associated mirrors. 228 7. Security Considerations 230 There are no additional security considerations other than those 231 normally associated with the use and resolution of URNs in general. 233 8. Acknowledgements 235 The authors wish to thank Alfred Hoenes, Ted Hardie, and Peter Saint- 236 Andre for their useful comments and suggestions. The authors also 237 acknowledge that the text from [RFC4358] formed the basis for the 238 initial version of this document. 240 9. References 242 9.1. Normative References 244 [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. 246 [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, 247 "Uniform Resource Names (URN) Namespace Definition 248 Mechanisms", BCP 66, RFC 3406, October 2002. 250 9.2. Informative References 252 [CANN] Cable Television Laboratories Inc., "CableLabs' Assigned 253 Names and Numbers", 2009, 254 . 256 [RFC4358] Smith, D., "A Uniform Resource Name (URN) Namespace for 257 the Open Mobile Alliance (OMA)", RFC 4358, January 2006. 259 Authors' Addresses 261 Eduardo Cardona 262 CableLabs 263 858 Coal Creek Circle 264 Louisville, CO 80027 265 USA 267 Phone: +1 303 661 3375 268 Email: e.cardona@cablelabs.com 270 Sumanth Channabasappa 271 CableLabs 272 858 Coal Creek Circle 273 Louisville, CO 80027 274 USA 276 Phone: +1 303 661 3307 277 Email: sumanth@cablelabs.com 279 Jean-Francois Mule 280 CableLabs 281 858 Coal Creek Circle 282 Louisville, CO 80027 283 USA 285 Phone: +1 303 661 9100 286 Email: jf.mule@cablelabs.com