idnits 2.17.1 draft-higgs-hbbtv-urn-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (January 12, 2015) is 3390 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 3406 (Obsoleted by RFC 8141) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IESG P. Higgs 2 Internet Draft J. Piesing 3 Intended status: Informational HbbTV Association 4 Expires: July 2015 January 12, 2015 6 A Uniform Resource Name (URN) Namespace for the HbbTV Association 7 draft-higgs-hbbtv-urn-01.txt 9 Status of this Memo 11 This Internet-Draft is submitted in full conformance with the 12 provisions of BCP 78 and BCP 79. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that 16 other groups may also distribute working documents as Internet- 17 Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference 22 material or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html 30 This Internet-Draft will expire on July 12, 2015. 32 Copyright Notice 34 Copyright (c) 2015 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. 44 Abstract 46 This document describes a Uniform Resource Name (URN) namespace for 47 the Hybrid Broadcast Broadband TV Association (HbbTV) for naming 48 persistent resources defined within HbbTV specifications. Example 49 resources include technical documents and specifications, eXtensible 50 Markup Language (XML) Schemas, classification schemes, XML Document 51 Type Definitions (DTDs), namespaces, style sheets, media assets, and 52 other types of resources produced or managed by HbbTV. 54 Table of Contents 56 1. Introduction...................................................2 57 2. URN Specification for the HbbTV Namespace Identifier (NID).....3 58 3. Examples.......................................................5 59 4. Namespace considerations.......................................5 60 5. Community Considerations.......................................6 61 6. Security Considerations........................................6 62 7. IANA Considerations............................................6 63 8. References.....................................................7 64 8.1. Normative References......................................7 65 8.2. Informative References....................................7 66 9. Acknowledgments................................................7 68 1. Introduction 70 HbbTV (Hybrid Broadcast Broadband TV) is a new industry standard 71 providing an open and business neutral technology platform that 72 seamlessly combines TV services delivered via broadcast with services 73 delivered via broadband and also enables access to Internet only 74 services for consumers using connected TVs and set-top boxes. The 75 founding members of the HbbTV consortium together with a large group 76 of supporters jointly developed the HbbTV specification to create a 77 global standard for hybrid entertainment services. Version 1.2.1 of 78 this specification was published by ETSI as ETSI TS 102 796 [HbbTV12] 79 in November 2012. 81 The HbbTV specification is based on existing standards and web 82 technologies including OIPF (Open IPTV Forum), CEA, DVB and W3C. The 83 standard provides the features and functionality required to deliver 84 feature rich broadcast and internet services. Utilizing standard 85 Internet technology it enables rapid application development. It 86 defines minimum requirements simplifying the implementation in 87 devices and leaving room for differentiation, this limits the 88 investment required by CE manufacturers to build compliant devices. 90 The HbbTV association is a pan.European initiative aimed at providing 91 an alternative to proprietary technologies and delivering an open 92 platform for broadcasters to deliver value added on.demand services 93 to the end consumer. 95 HbbTV has a wide range of supporters from across the broadcaster and 96 CE industries. 98 HbbTV would like to assign unique, permanent, location-independent 99 names based on URNs for some resources it produces or manages. These 100 URNs will be constructed according to the URN syntax defined in 101 [RFC2141]. This namespace specification is for a formal namespace to 102 be registered according to the procedures set forth in [RFC3406]. 104 2. URN Specification for the HbbTV Namespace Identifier (NID) 106 This section provides the information required to register a formal 107 namespace according to the registration procedure defined in 108 [RFC3406]. The URNs conform to the syntax defined in [RFC2141]. 110 Namespace ID: 112 "hbbtv" 114 Registration Information: 116 Version: 1 118 Date: 2014-08-07 120 Declared registrant of the namespace: 122 Name: Mr. Peter Macavock 124 Title: Administrator 126 Affiliation: HbbTV Association 128 Address: L'Ancienne-Route 17A, 130 CH-1218 Grand-Saconnex, Suisse 132 Phone: + 41 22 717 27 14 Email: info@hbbtv.org 134 Declaration of structure: 136 URNs assigned by HbbTV will have the following structure based on 137 the organizational structure of the resources specified in the 138 HbbTV specifications: 140 urn:hbbtv: 142 where the syntax of "" is specified in Section 2.2 of the 143 URN Syntax requirements ([RFC2141]). 145 The individual URNs will be assigned by HbbTV through the process 146 of development of the HbbTV specifications. 148 Relevant ancillary documentation: 150 None. 152 Identifier uniqueness considerations: 154 HbbTV will establish unique identifiers as appropriate and will 155 ensure that an assigned string is never reassigned. 157 Identifier persistence considerations: 159 HbbTV is committed to maintaining the accessibility and 160 persistence of all resources that are officially assigned URNs by 161 the organization. The registration tables and information will be 162 published and maintained by HbbTV on its web site. 164 Process of identifier assignment: 166 The assignment of identifiers is fully controlled and managed by 167 HbbTV. 169 Process of identifier resolution: 171 Not applicable; the "hbbtv" namespace is not listed with a 172 Resolution Discovery System. 174 Rules for Lexical Equivalence: 176 The "" is case-insensitive. 178 Conformance with URN Syntax: 180 No special considerations. 182 Validation mechanism: 184 None specified. URN assignment will be managed completely and 185 published by HbbTV. 187 Scope: 189 Global 191 3. Examples 193 The following example of schemas and classification schemes is taken 194 from the current HbbTV specification [HbbTV12] 196 urn:hbbtv:dash:profile:isoff-live:2012 198 The following examples of schemas and classification schemes are 199 under consideration for inclusion in a future version of the HbbTV 200 specification currently under development. 202 urn:hbbtv:sync:timeline:ebu-tt-d 204 urn:hbbtv:config:oitf:oitfCapabilities:2014-1 206 4. Namespace considerations 208 A unique formal namespace is required by HbbTV in order to specify 209 how the various existing standards can be linked in order to create a 210 true end-to-end ecosystem for standards-based IPTV deployments, and 211 to provide the necessary system-wide resources. 213 URN assignment procedures: 215 The individual URNs shall be assigned through the process of 216 development of HbbTV specifications by the Hybrid Broadcast 217 Broadband TV Association. The latest information about HbbTV 218 defined specifications can always be found at the owner's website 219 at 221 https://hbbtv.org/pages/about_hbbtv/specification.php 223 URN resolution/delegation: 225 The resolution and delegation shall be determined through the 226 process of development of specifications by the HbbTV 227 Association. 229 Since the implementations envisaged cover a wide range of devices 230 with quite different access methods and capabilities, no single 231 resolution or delegation mechanism can be referenced in this 232 document. 234 Type of resources to be identified: 236 Types of resources to be identified include XML schema definition 237 files, classification schemes and identification systems defined 238 and published by HbbTV. These resources being identified 239 constitute a metadata system to describe digital multimedia 240 broadcast services or content conveyed as part of such services. 242 The latest HbbTV defined specifications can always be found at 244 https://hbbtv.org/pages/about_hbbtv/specification.php 246 5. Community Considerations 248 URNs defined by HbbTV will be used by implementers of hybrid 249 broadcast/broadband systems, services, products, and applications 250 based on the HbbTV specification. They are an essential component of 251 the open ecosystem that is being facilitated by HbbTV. 253 HbbTV specifications are developed through a consensus based process 254 by member organizations representing most aspects of the digital 255 television ecosystem, a full list of HbbTV members can be found at 256 http://hbbtv.org/pages/hbbtv_association/members.php 258 6. Security Considerations 260 There are no additional security considerations other than those 261 normally associated with the use and resolution of URNs in general, 262 which are described in [RFC1737], [RFC2141], and [RFC3406]. 264 This document registers a namespace for URNs. HbbTV may assign 265 special meaning to certain of the characters of the Namespace 266 Specific String in its specifications. Any security consideration 267 resulting from such assignment is outside the scope of this document. 269 7. IANA Considerations 271 This document defines a URN NID registration of "hbbtv". IANA is 272 requested to include it in the URN Namespaces registry. 274 8. References 276 8.1. Normative References 278 [RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for 279 Uniform Resource Names", RFC 1737, December 1994. 281 [RFC2141] Moats, R., "URN Syntax", RFC 2124, May 1997. 283 [RFC3406] Daigle, L., van Gulik, D., Iannella, R. and P. Faltstrom, 284 "Uniform Resource Names (URN) Namespace Definition 285 Mechanisms", October 2002. 287 8.2. Informative References 289 [HbbTV12] ETSI TS 102 796 v1.2.1, "Hybrid Broadcast Broadband TV" 291 9. Acknowledgments 293 This document was prepared using 2-Word-v2.0.template.dot. 295 Authors' Addresses 297 Paul Higgs 298 HbbTV Association 299 c/o Ericsson Inc, 6 Concourse Parkway, suite 3000, 300 Atlanta, GA 30328, USA 302 Phone: +1-650-580-1731 303 Email: paul.higgs@ericsson.com 305 Jon Piesing 306 Chair, Technical Specification Group, 307 HbbTV Association 308 c/o TP Vision, Pathoekeweg 11, 8000 Brugge, Belgium 310 Phone: +32 484 430 060 311 Email: jon.piesing@tpvision.com