Internet DRAFT - draft-dthakore-scte-urn
draft-dthakore-scte-urn
ART Area General Applications Working Group D. Thakore, Ed.
Internet-Draft CableLabs
Intended status: Informational N. Dang
Expires: October 5, 2016 SCTE
G. Hughes
SeaChange
April 3, 2016
A Uniform Resource Name (URN) Namespace for SCTE
draft-dthakore-scte-urn-00
Abstract
This document describers the Namespace Identifier (NID) 'scte' for
Uniform Resource Names (URNs) used to identify resources published by
the Society of Cable Telecommunications Engineers (SCTE). SCTE
specifies and manages resources that utilize this URN identification
model. Management activities for these and other resource types are
handled by the SCTE.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
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 5, 2016.
Thakore, et al. Expires October 5, 2016 [Page 1]
Internet-Draft SCTE-URN April 2016
Copyright Notice
Copyright (c) 2016 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. URN Specification for SCTE . . . . . . . . . . . . . . . . . 3
3. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Namespace Considerations . . . . . . . . . . . . . . . . . . 5
5. Community Considerations . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
7. Security Considerations . . . . . . . . . . . . . . . . . . . 5
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
9.1. Normative References . . . . . . . . . . . . . . . . . . 6
9.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
The SCTE standards program is an ANSI-accredited forum for the
development of technical specifications supporting cable
telecommunications. SCTE standards work includes: data and telephony
over cable; application platform development; digital video;
emergency alert systems; network monitoring systems; cables,
connectors and amplifiers; construction and maintenance practices;
energy management, and more.
Occasionally, SCTE 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) Namespace Identifier (NID) for use by
SCTE is being speified in this document, in full conformance with the
NID registration process specified in RFC3406 [RFC3406]
Thakore, et al. Expires October 5, 2016 [Page 2]
Internet-Draft SCTE-URN April 2016
2. URN Specification for SCTE
Namespace ID:
scte
Registration Information:
registration version number: 1
registration date: 2016-03-20
Declared registrant of the namespace:
Registering organization
Name: Society of Cable Telecommunications Engineers
Address: 140 Philips Road, Exton, PA 19341-1318, USA
Designated contact
Role: Manager, Standards
Email: TBD
Declaration of syntactic structure:
The Namespace Specific String (NSS) of all URNs that use the
"scte" NID will have the following structure:
urn:scte:{SCTEresource}:{ResourceSpecificString}
where the "SCTEresource" is a US-ASCII string that conforms to the
URN syntax requirements of [RFC2141].
SCTE will maintain a naming authority, the SCTE Assigned Names and
Numbers [SANN] specification, that will contain the assignment of
SCTE resource classes and the specific registration values
assigned for each resource class. This specification will be
published on the SCTE Standards Program website.
Relevant ancillary documentation:
SCTE publishes information regarding the registered resources in
the corresponding SCTE standards.
Identifier uniqueness considerations:
SCTE will manage resource classes using the "scte" NID and will be
the authority for managing resources and associated subsequent
strings. SCTE is expected to guarantee the uniqueness of the
strings themselves.
Thakore, et al. Expires October 5, 2016 [Page 3]
Internet-Draft SCTE-URN April 2016
SCTE 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:
SCTE will update the SCTE Assigned Names and Numbers specification
to document the registered resources that use the "scte" NID.
Process of identifier assignment:
SCTE will provide procedures for registration of each type of
resource that it maintains. Each such resource may have three
types registration activities:
1. Registered values associated with SCTE documents or services
2. Registration of values or sub-trees to other entities
3. Name models for use in experimental purposes
Process of 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] apply.
Validation mechanism:
None specified. URN assignment will be handled by procedures
implemented in support of SCTE activities.
Scope:
Global
3. Example
The following example represents a hypothetical URL that could be
assigned by SCTE.
urn:scte:dash:2015
This example defines the URN to be used for for ANSI/SCTE 214-1 2015
"MPEG DASH for IP-Based Cable Services Part 1: MPD Constraints and
Extensions"
Thakore, et al. Expires October 5, 2016 [Page 4]
Internet-Draft SCTE-URN April 2016
4. Namespace Considerations
SCTE 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 SCTE specifications if they so wish.
5. Community Considerations
Participants involved in the development and usage of SCTE
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 SCTE
specifications.
The SCTE specifications are publicly available and are licensed to
manufacturers on a nondiscriminatory basis. SCTE will maintain the
corresponding specifications where the registered resources are
referenced or used.
6. IANA Considerations
This document adds a new entry ("scte") in the urn-namespaces
registry. This is the defining document for the entry. The entry
can be found in the Uniform Resource Names (URN) Namespaces
[IANA-URN] Registry.
7. Security Considerations
There are no additional security considerations other than those
normally associated with the use and resolution of URNs in general,
which are described in [RFC1737], [RFC2141], [RFC3406]
8. Acknowledgements
The authors acknowledge that the text from [RFC6289] formed the basis
for the initial version of this document.
9. References
Thakore, et al. Expires October 5, 2016 [Page 5]
Internet-Draft SCTE-URN April 2016
9.1. Normative References
[IANA-URN]
IANA, "Uniform Resource Names (URN) Namespaces",
<http://www.iana.org/assignments/urn-namespaces/
urn-namespaces.xhtml>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997,
<http://xml.resource.org/public/rfc/html/rfc2119.html>.
[RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141,
May 1997, <http://www.rfc-editor.org/info/rfc2141>.
[RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
"Uniform Resource Names (URN) Namespace Definition
Mechanisms", BCP 66, RFC 3406, DOI 10.17487/RFC3406,
October 2002, <http://www.rfc-editor.org/info/rfc3406>.
[RFC7749] Reschke, J., "The "xml2rfc" Version 2 Vocabulary",
RFC 7749, DOI 10.17487/RFC7749, February 2016,
<http://www.rfc-editor.org/info/rfc7749>.
9.2. Informative References
[RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for
Uniform Resource Names", RFC 1737, DOI 10.17487/RFC1737,
December 1994, <http://www.rfc-editor.org/info/rfc1737>.
[RFC4234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 4234, DOI 10.17487/RFC4234,
October 2005, <http://www.rfc-editor.org/info/rfc4234>.
[RFC6289] Cardona, E., Channabasappa, S., and J-F. Mule, "A Uniform
Resource Name (URN) Namespace for CableLabs", RFC 6289,
DOI 10.17487/RFC6289, June 2011,
<http://www.rfc-editor.org/info/rfc6289>.
[SANN] Society of Cable Telecommunications Engineers, "SCTE
Assigned Name and Number Registry".
Authors' Addresses
Thakore, et al. Expires October 5, 2016 [Page 6]
Internet-Draft SCTE-URN April 2016
Darshak Thakore (editor)
CableLabs
858 Coal Creek Circle
Louisville, CO 80023
US
Email: d.thakore@cablelabs.com
URI: http://www.cablelabs.com
Niem Dang
Society of Cable Telecommunications Engineers
140 Philips Road
Exton, PA 19341-1318
US
Email: ndang@scte.org
URI: http://www.scte.org
Gary Hughes
SeaChange International Inc.
50 Nagog Park
Acton, MA 01720
US
Email: gary.hughes@schange.com
URI: http://www.schange.com
Thakore, et al. Expires October 5, 2016 [Page 7]