wdiff rfc7528.original rfc7528.txt

IESG
Internet Engineering Task Force (IETF) P. Higgs
Internet Draft
Request for Comments: 7528 J. Piesing
Intended status:
Category: Informational HbbTV Association
Expires: July 2015 January 12,
ISSN: 2070-1721 April 2015

A Uniform Resource Name (URN) Namespace
for the HbbTV Hybrid Broadcast Broadband TV (HbbTV) Association
draft-higgs-hbbtv-urn-01.txt

Abstract

This document describes a Uniform Resource Name (URN) namespace for
the Hybrid Broadcast Broadband TV (HbbTV) Association for naming
persistent resources defined within HbbTV specifications. Example
resources include technical documents and specifications, Extensible
Markup Language (XML) Schemas, classification schemes, XML Document
Type Definitions (DTDs), namespaces, style sheets, media assets, and
other types of resources produced or managed by HbbTV.

Status of this This Memo

This Internet-Draft document is submitted in full conformance with the
provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents not an Internet Standards Track specification; it is
published for informational purposes.

This document is a product 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
(IETF). It represents the consensus of six months the IETF community. It has
received public review and may be updated, replaced, or obsoleted has been approved for publication by other the
Internet Engineering Steering Group (IESG). Not all documents at
approved by the IESG are a candidate for any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."

The list level of Internet
Standard; see Section 2 of RFC 5741.

Information about the current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt

The list status of Internet-Draft Shadow Directories can this document, any errata,
and how to provide feedback on it may be accessed obtained at
http://www.ietf.org/shadow.html

This Internet-Draft will expire on July 12, 2015.
http://www.rfc-editor.org/info/rfc7528.

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.

Abstract

This Code Components extracted from this document describes a Uniform Resource Name (URN) namespace for
the Hybrid Broadcast Broadband TV Association (HbbTV) for naming
persistent resources defined within HbbTV specifications. Example
resources must
include technical documents and specifications, eXtensible
Markup Language (XML) Schemas, classification schemes, XML Document
Type Definitions (DTDs), namespaces, style sheets, media assets, and
other types Simplified BSD License text as described in Section 4.e of resources produced or managed by HbbTV.
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.

Table of Contents

1. Introduction...................................................2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. URN Specification for the HbbTV Namespace Identifier (NID).....3 (NID) . 3
3. Examples.......................................................5 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Namespace considerations.......................................5 Considerations . . . . . . . . . . . . . . . . . . 5
5. Community Considerations.......................................6 Considerations . . . . . . . . . . . . . . . . . . 6
6. Security Considerations........................................6 Considerations . . . . . . . . . . . . . . . . . . . 6
7. IANA Considerations............................................6 Considerations . . . . . . . . . . . . . . . . . . . . . 6
8. References.....................................................7 References . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References......................................7 References . . . . . . . . . . . . . . . . . . 6
8.2. Informative References....................................7
9. Acknowledgments................................................7 References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7

1. Introduction

HbbTV (Hybrid Broadcast Broadband TV) is a new industry standard
providing an open and business neutral business-neutral technology platform that
seamlessly combines TV services delivered via broadcast with services
delivered via broadband and also enables access to Internet only Internet-only
services for consumers using connected TVs and set-top boxes. The
founding members of the HbbTV consortium together with a large group
of supporters jointly developed the HbbTV specification to create a
global standard for hybrid entertainment services. Version 1.2.1 of
this specification was published by ETSI as ETSI TS 102 796 [HbbTV12]
in November 2012.

The HbbTV specification is based on existing standards and web
technologies including OIPF (Open the Open IPTV Forum), CEA, DVB and W3C. Forum (OIPF), Consumer
Electronics Association (CEA), Digital Video Broadcasting (DVB), and
World Wide Web Consortium (W3C). The standard provides the features
and functionality required to deliver
feature rich feature-rich broadcast and internet
Internet services. Utilizing standard Internet technology technology, it
enables rapid application development. It defines minimum
requirements simplifying the implementation in devices and leaving
room for differentiation, differentiation; this limits the investment required by CE
consumer electronics manufacturers to build compliant devices. The
HbbTV association Association is a pan.European pan-European initiative aimed at providing an
alternative to proprietary technologies and delivering an open
platform for broadcasters to deliver value added on.demand value-added on-demand services
to the end consumer.

HbbTV has a wide range of supporters from across the broadcaster and
CE
consumer electronics industries.

HbbTV would like to assign unique, permanent, location-independent
names based on URNs for some resources it produces or manages. These
URNs will be constructed according to the URN syntax defined in
[RFC2141]. This namespace specification is for a formal namespace to
be registered according to the procedures set forth in [RFC3406].

2. URN Specification for the HbbTV Namespace Identifier (NID)

This section provides the information required to register a formal
namespace according to the registration procedure defined in
[RFC3406]. The URNs conform to the syntax defined in [RFC2141].

Namespace ID:

"hbbtv"

Registration Information:

Version: 1

Date: 2014-08-07

Declared registrant of the namespace:

Name: Mr. Peter Macavock

Title: Administrator

Affiliation: HbbTV Association

Address: L'Ancienne-Route 17A, CH-1218 Grand-Saconnex, Suisse
Switzerland

Phone: + 41 22 717 27 14

Email: info@hbbtv.org

Declaration of structure:

URNs assigned by HbbTV will have the following structure based on
the organizational structure of the resources specified in the
HbbTV specifications:

urn:hbbtv:<NSS>

where the syntax of "<NSS>" is specified in Section 2.2 of the URN
Syntax requirements ([RFC2141]). [RFC2141].

The individual URNs will be assigned by HbbTV through the process
of development of the HbbTV specifications.

Relevant ancillary documentation:

None.

Identifier uniqueness considerations:

HbbTV will establish unique identifiers as appropriate and will
ensure that an assigned string is never reassigned.

Identifier persistence considerations:

HbbTV is committed to maintaining the accessibility and
persistence of all resources that are officially assigned URNs by
the organization. The registration tables and information will be
published and maintained by HbbTV on its web site.

Process of identifier assignment:

The assignment of identifiers is fully controlled and managed by
HbbTV.

Process of identifier resolution:

Not applicable; the "hbbtv" namespace is not listed with a
Resolution Discovery System.

Rules for Lexical Equivalence:

The "<NSS>" is case-insensitive.

Conformance with URN Syntax:

No special considerations.

Validation mechanism:

None specified. URN assignment will be managed completely and
published by HbbTV.

Scope:

Global

3. Examples

The following example of schemas and classification schemes is taken
from the current HbbTV specification [HbbTV12] [HbbTV12].

urn:hbbtv:dash:profile:isoff-live:2012

The following examples of schemas and classification schemes are
under consideration for inclusion in a future version of the HbbTV
specification currently under development.

urn:hbbtv:sync:timeline:ebu-tt-d

urn:hbbtv:config:oitf:oitfCapabilities:2014-1

4. Namespace considerations Considerations

A unique formal namespace is required by HbbTV in order to specify
how the various existing standards can be linked in order to create a
true end-to-end ecosystem for standards-based IPTV deployments, deployments and to
provide the necessary system-wide resources.

URN assignment procedures:

The individual URNs shall be assigned through the process of
development of HbbTV specifications by the Hybrid Broadcast
Broadband TV Association. The latest information about HbbTV HbbTV-
defined specifications can always be found at the owner's website
at

https://hbbtv.org/pages/about_hbbtv/specification.php

<https://hbbtv.org/pages/about_hbbtv/specification.php>

URN resolution/delegation:

The resolution and delegation shall be determined through the
process of development of specifications by the HbbTV Association.

Since the implementations envisaged cover a wide range of devices
with quite different access methods and capabilities, no single
resolution or delegation mechanism can be referenced in this
document.

Type of resources to be identified:

Types of resources to be identified include XML schema definition
files, classification schemes schemes, and identification systems defined
and published by HbbTV. These resources being identified
constitute a metadata system to describe digital multimedia
broadcast services or content conveyed as part of such services.

The latest HbbTV defined HbbTV-defined specifications can always be found at

https://hbbtv.org/pages/about_hbbtv/specification.php

<https://hbbtv.org/pages/about_hbbtv/specification.php>

5. Community Considerations

URNs defined by HbbTV will be used by implementers of hybrid
broadcast/broadband systems, services, products, and applications
based on the HbbTV specification. They are an essential component of
the open ecosystem that is being facilitated by HbbTV.

HbbTV specifications are developed through a consensus based consensus-based process
by member organizations representing most aspects of the digital
television ecosystem, a ecosystem. A full list of HbbTV members can be found at
http://hbbtv.org/pages/hbbtv_association/members.php

<http://hbbtv.org/pages/hbbtv_association/members.php>

6. 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], and [RFC3406].

This document registers a namespace for URNs. HbbTV may assign
special meaning to certain of the characters of the Namespace
Specific String (NSS) in its specifications. Any security
consideration resulting from such assignment is outside the scope of
this document.

7. IANA Considerations

This document defines a URN NID registration of "hbbtv". IANA is
requested to include has
included it in the URN Namespaces "Uniform Resource Names (URN) Namespaces"
registry.

8. References

8.1. Normative References

[RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for
Uniform Resource Names", RFC 1737, December 1994. 1994,
<http://www.rfc-editor.org/info/rfc1737>.

[RFC2141] Moats, R., "URN Syntax", RFC 2124, 2141, May 1997. 1997,
<http://www.rfc-editor.org/info/rfc2141>.

[RFC3406] Daigle, L., van Gulik, D., Iannella, R. R., and P. Faltstrom,
"Uniform Resource Names (URN) Namespace Definition
Mechanisms", BCP 66, RFC 3406, October 2002. 2002,
<http://www.rfc-editor.org/info/rfc3406>.

8.2. Informative References

[HbbTV12] ETSI, "Hybrid Broadcast Broadband TV", ETSI TS 102 796
v1.2.1, "Hybrid Broadcast Broadband TV"

9. Acknowledgments

This document was prepared using 2-Word-v2.0.template.dot. November 2012.

Authors' Addresses

Paul Higgs
HbbTV Association
c/o Ericsson Inc, 6 Concourse Parkway, suite 3000, 400
Atlanta, GA 30328, USA 30328
United States

Phone: +1-650-580-1731
Email:
EMail: paul.higgs@ericsson.com

Jon

Jonathan Piesing
Chair, Technical Specification Group,
HbbTV Association
c/o TP Vision, Pathoekeweg 11, 11
Brugge 8000 Brugge,
Belgium

Phone: +32 484 430 060
Email:
EMail: jon.piesing@tpvision.com