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

Abstract

This document describes the Namespace Identifier (NID) 'cablelabs' for Uniform Resource Names (URNs) used to identify resources published by Cable Television Laboratories, Inc. (CableLabs). CableLabs specifies and manages resources that utilize this URN identification model. Management activities for these and other resource types are handled by the manager of the CableLabs' Assigned Names and Numbers registry.

Status of this Memo

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 28, 2010.

Copyright Notice

Copyright (c) 2010 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.

This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.

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.  Acknowledgements
9.  References
    9.1.  Normative References
    9.2.  Informative References
§  Authors' Addresses

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 within focus teams. Product vendors, manufacturers, and cable operator members are invited to join the focus teams that create technical specifications.

Occasionally, CableLabs 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 a specific Uniform Resource Name (URN) [RFC2141] Namespace ID (NID) for use by CableLabs is being specified in this document, in full conformance with the NID registration process specified in [RFC3406] (Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, “Uniform Resource Names (URN) Namespace Definition Mechanisms,” October 2002.).

2.  URN Specification for CableLabs

Namespace ID:

cablelabs

Registration Information:

registration version number: 1
registration date: YYYY-MM-DD [RFC Editor: Please replace YYYY-MM-DD with the date of approval of this document for publication as an RFC.]

Declared registrant of the namespace:

Registering organization

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

Designated contact

Role: Manager, Standards
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:

{CLclass}:{CLClassSpecificString}

The "CLclass" is a US-ASCII string that conforms to the URN syntax requirements specified in [RFC2141] (Moats, R., “URN Syntax,” May 1997.) and defines a specific class of resource type. Each class will have a specific labeling scheme that is covered by "CLClassSpecificString", 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,” 2009.) specification that will contain the assignment of CableLabs resource classes, and the specific registration values assigned for each resource class.

Relevant ancillary documentation:

CableLabs publishes information regarding the registered resources in the CableLabs' Assigned Names and Numbers specification ([CANN] (Cable Television Laboratories Inc., “CableLabs' Assigned Names and Numbers,” 2009.)).

Identifier uniqueness considerations:

CableLabs will manage resource classes using the "cablelabs" NID and will be the authority for managing 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 CableLabs' Assigned Names and Numbers specification (ref: [CANN] (Cable Television Laboratories Inc., “CableLabs' Assigned Names and Numbers,” 2009.)) to document the registered resources that use 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 a hypothetical URN that could be assigned by CableLabs.

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

Defines the URN to be used for User Equipment (UE) conforming to the sample Residential SIP Telephony (RST) application specified within CableLabs' PacketCable RST specification suite.

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 on 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

This document adds a new entry in the urn-namespaces registry. The namespace should be "cablelabs". This is the defining document. The entry 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.  Acknowledgements

The authors thank Alfred Hoenes (TR-Sys) for his useful comments and suggestions. The authors also acknowledge that the text from this RFC - [RFC4358] (Smith, D., “A Uniform Resource Name (URN) Namespace for the Open Mobile Alliance (OMA),” January 2006.) - formed the basis for the intial version of this document.

9.  References

9.1. Normative References

9.2. Informative References

Authors' Addresses