A Uniform Resource Name (URN) Namespace for CableLabs
draft-cardona-cablelabs-urn-00

Status of this Memo

By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.

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.”

The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.

The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.

This Internet-Draft will expire on January 8, 2009.

Abstract

This document describes the Namespace Identifier (NID) for Uniform Resource Namespace (URN) resources published by Cable Television Laboratories Inc. (CableLabs). CableLabs publishes specifications that define unique and persistent resources that make use of the cablelabs URN namespace.

Table of Contents

1.  Introduction
2.  URN Specification for CableLabs
3.  Example
4.  Namespace Considerations
5.  Community Considerations
6.  IANA Considerations
7.  Security Considerations
8.  References
    8.1.  Normative References
    8.2.  Informative References
§  Authors' Addresses
§  Intellectual Property and Copyright Statements

1.  Introduction

CableLabs is a non-profit research and development consortium that is dedicated to pursuing new cable telecommunications technologies and to helping its cable operator members integrate those technical advancements into their business objectives. Within CableLabs, specification activities are organized into projects such as DOCSIS(r), PacketCable(tm), and OpenCable(tm), and technical work is conducted in focus teams. Product vendors, manufacturers, and cable operator members are invited to join the focus teams that create technical specifications.

From time to time, some specifications developed by CableLabs require a URN namespace to uniquely identify resources. CableLabs manages these resource assignments prior to specification publication and ensures they are both unique and persistent.

This document defines a full and complete NID registration that follows [RFC3406] (Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, “Uniform Resource Names (URN) Namespace Definition Mechanisms,” October 2002.) for the purpose of having unique and persistent namespace definitions in CableLabs specifications.

2.  URN Specification for CableLabs

Namespace ID:

The NID "cablelabs" is requested.

Registration Information:

registration version number: 1
registration date: 2008-07-02

Declared registrant of the namespace:

Registering organization

Name: Cable Television Laboratories Inc.
Address: 858 Coal Creek Circle, Louisville, CO 80027, USA

Designated contact

Role: Standards Manager
Email: ietf-standards@cablelabs.com

Declaration of syntactic structure:

The Namespace Specific String (NSS) of all URNs that use the "cablelabs" NID will have the following structure: urn:cablelabs:{CLresource}:{CLResourceSpecificString} where the "CLresource" is a US-ASCII string that conforms to the URN syntax requirements [RFC2141] (Moats, R., “URN Syntax,” May 1997.) and defines a specific class of resource type. Each resource type has a specific labeling scheme that is covered by "CLResourceSpecificString", which also conforms to the naming requirements of [RFC2141] (Moats, R., “URN Syntax,” May 1997.).

CableLabs maintains the CableLabs Assigned Names and Numbers [CANN] (Cable Television Laboratories Inc., “CableLabs' Assigned Names and Numbers,” 2008.) specification that will contain the assignment of "CLresources" and the specific registration values assigned for each resource class.

Relevant ancillary documentation:

CableLabs publishes information on the registered resources in the [CANN] (Cable Television Laboratories Inc., “CableLabs' Assigned Names and Numbers,” 2008.) specification available at: http://www.cablelabs.com/specifications/cpSpecs.html

Identifier uniqueness considerations:

CableLabs will manage resources using the "cablelabs" NID and will be the authority for managing the resources and subsequent strings associated. CableLabs is expected to guarantee the uniqueness of the strings themselves or it may permit secondary responsibility for certain defined resources.

CableLabs could allow the use of 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:

CableLabs will update the [CANN] (Cable Television Laboratories Inc., “CableLabs' Assigned Names and Numbers,” 2008.) specification to document the registered resources in the "cableLabs" NID.

Process of identifier assignment:

CableLabs will provide procedures for registration of each type of resource that it maintains. Each such resource may have three types of registration activities:

1. Registered values associated with CableLabs documents or services
2. Registration of values or sub-trees to other entities
3. Name models for use in experimental purposes

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] (Moats, R., “URN Syntax,” May 1997.) apply.

Conformance with URN Syntax:

No special considerations.

Validation mechanism:

None specified. URN assignment will be handled by procedures implemented in support of CableLabs activities.

Scope:

Global

3.  Example

The following example represents an hypothetical URN that could be assigned by Cablelabs.

urn:cablelabs:packetcable-example:ue:rst-sample

Defines the URN to be used for the User Equipment (UE) implementing the sample Residential SIP Telephony Application (RST) defined in the Packetcable specifications.

4.  Namespace Considerations

CableLabs develops specifications that may 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 CableLabs specifications if they so wish.

5.  Community Considerations

The CableLabs specifications are publicly available or licensed to manufacturers in a nondiscriminatory basis.

CableLabs will maintain the allocation of resources for the "cablelabs" NID and maintain updated the corresponding specifications where those resources are referenced or used.

6.  IANA Considerations

The requested NID has been entered into the IANA registry for URN NIDs. The update can be found at: http://www.iana.org/assignments/urn-namespaces and any associated mirrors.

7.  Security Considerations

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

8.  References

8.1. Normative References

8.2. Informative References

Authors' Addresses

Full Copyright Statement

Copyright © The IETF Trust (2008).

This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.

This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Intellectual Property

The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.

Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.

The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.