Network Working Group E.C. Cardona
Internet-Draft S.C. Channabasappa
Intended status: Informational J-F.M. Mule
Expires: September 14, 2011 CableLabs
March 13, 2011

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

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.

The IETF has been notified of intellectual property rights claimed in regard to some or all of the specification contained in this document. For more information consult the online list of claimed rights.

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 September 14, 2011.

Copyright Notice

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

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

2. URN Specification for CableLabs

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:

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

Participants involved in the development and usage of CableLabs specifications, and cable industry deployments 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 CableLabs specifications.

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 within the following specification: [CANN], which will be publicly available for viewing. CableLabs will also maintain the corresponding specifications where the registered 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 wish to thank Alfred Hoenes, Ted Hardie, and Peter Saint-Andre for their useful comments and suggestions. The authors also acknowledge that the text from [RFC4358] formed the basis for the initial version of this document.

9. References

9.1. Normative References

[RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.
[RFC3406] Daigle, L., van Gulik, D., Iannella, R. and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, October 2002.

9.2. Informative References

[RFC4358] Smith, D., "A Uniform Resource Name (URN) Namespace for the Open Mobile Alliance (OMA)", RFC 4358, January 2006.
[CANN] Cable Television Laboratories Inc., "CableLabs' Assigned Names and Numbers", 2009.

Authors' Addresses

Eduardo Cardona CableLabs 858 Coal Creek Circle Louisville, CO 80027 USA Phone: +1 303 661 3375 EMail: e.cardona@cablelabs.com
Sumanth Channabasappa CableLabs 858 Coal Creek Circle Louisville, CO 80027 USA Phone: +1 303 661 3307 EMail: sumanth@cablelabs.com
Jean-Francois Mule CableLabs 858 Coal Creek Circle Louisville, CO 80027 USA Phone: +1 303 661 9100 EMail: jf.mule@cablelabs.com