idnits 2.17.1 draft-higgs-oipf-urn-00.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: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 3) being 102 lines == It seems as if not all pages are separated by form feeds - found 7 form feeds but 9 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 3 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (August 13, 2012) is 4272 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'OIPF1' is defined on line 315, but no explicit reference was found in the text == Unused Reference: 'OIPF2' is defined on line 318, but no explicit reference was found in the text == Unused Reference: 'OIPF3' is defined on line 321, but no explicit reference was found in the text == Unused Reference: 'OIPF4' is defined on line 324, but no explicit reference was found in the text == Unused Reference: 'OIPF5' is defined on line 327, but no explicit reference was found in the text == Unused Reference: 'OIPF6' is defined on line 330, but no explicit reference was found in the text == Unused Reference: 'OIPF7' is defined on line 333, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3406 (Obsoleted by RFC 8141) Summary: 2 errors (**), 0 flaws (~~), 10 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IESG P. Higgs 2 P. Szucs 3 Internet Draft Open IPTV Forum e.V. 4 Intended status: Informational August 13, 2012 5 Expires: February 2013 7 A Uniform Resource Name (URN) Namespace for the Open IPTV Forum 8 (OIPF) 9 11 Status of this Memo 13 This Internet-Draft is submitted to IETF in full conformance with the 14 provisions of BCP 78 and BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress". 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html 32 This Internet-Draft will expire on February 13, 2013. 34 Copyright Notice 36 Copyright (c) 2012 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal Provisions 40 Relating to IETF Documents (http://trustee.ietf.org/license-info) in 41 effect on the date of publication of this document. 42 Please review these documents carefully, as they describe your rights 43 and restrictions with respect to this document. 45 Abstract 47 This document describes a Uniform Resource Name (URN) namespace for 48 the Open IPTV Forum (OIPF) for naming persistent resources defined 49 within OIPF specifications. Example resources include technical 50 documents and specifications, eXtensible Markup Language (XML) 51 Schemas, classification schemes, XML Document Type Definitions 52 (DTDs), namespaces, style sheets, media assets, and other types of 53 resources produced or managed by the OIPF. 55 Table of Contents 57 1. Introduction...................................................2 58 2. URN Specification for the OIPF Namespace Identifier (NID)......3 59 3. Examples.......................................................5 60 4. Namespace Considerations.......................................6 61 5. Community Considerations.......................................7 62 6. Security Considerations........................................7 63 7. IANA Considerations............................................7 64 8. References.....................................................7 65 8.1. Normative References......................................7 66 8.2. Informative References....................................7 67 9. Acknowledgments................................................8 69 1. Introduction 71 The Open IPTV Forum (OIPF) is a pan-industry initiative with the 72 purpose of producing end-to-end specifications for IPTV that will 73 take the next generation of IPTV into the mass market. The Forum, 74 which is fully open to participation from the communications, 75 entertainment and other relevant industries, will focus on the 76 development of specifications that will help streamline and 77 accelerate deployments of IPTV technologies, and maximize the 78 benefits of IPTV for consumers, network operators, content providers, 79 service providers, consumer electronics manufacturers and home and 80 network infrastructure providers. 82 The main objective of the Open IPTV Forum is to produce end-to-end 83 specifications for IPTV including: 85 o Architecture and interfaces 87 o Network and terminal functionality 89 o Interactive and personalized services 91 o Technology choices for all major functionalities 93 o A common UNI (User-Network Interface) for the Open Internet and 94 Managed Networks 96 o Certification of equipment including end user devices and service 97 provider offerings 99 The end-to-end specifications support: 101 o A variety of IPTV and Internet multimedia services 103 o Managed networks and the Open Internet 105 o Integration with communication services 107 o Convergence of IPTV and multimedia services across different 108 access technologies 110 o Easy integration of 3rd party content offerings 112 o Authentication and content protection 114 o Various devices in the home network 116 The OIPF is basing its end-to-end IPTV specifications on relevant 117 standards produced by other bodies, and collaborating with them to 118 encourage convergence where appropriate, and address any shortcomings 119 or gaps. 121 In the creation of the end-to-end IPTV specification, some new 122 resources need to be defined. 124 The OIPF would like to assign unique, permanent, location-independent 125 names based on URNs for some resources it produces or manages. These 126 URNs will be constructed according to the URN syntax defined in 127 [RFC2141]. 129 This namespace specification is for a formal namespace to be 130 registered according to the procedures set forth in [RFC3406]. 132 2. URN Specification for the OIPF Namespace Identifier (NID) 134 This section provides the information required to register a formal 135 namespace according to the registration procedure defined in 136 [RFC3406]. The URNs conform to the syntax defined in [RFC2141]. 138 Namespace ID: 140 "oipf" 142 Registration Information: 144 Version: 1 146 Date: 2012-08-13 148 Declared registrant of the namespace: 150 Name: Dr. Nilo Mitra 152 Title: President 154 Affiliation: Open IPTV Forum 156 Address: Open IPTV Forum e.V. Secretariat, 157 650 Route des Lucioles, 158 06921 Sophia Antipolis Cedex, France. 160 Phone: +33 492 94 43 83 162 Email: contact@oipf.tv 164 Declaration of structure: 166 URNs assigned by the OIPF will have the following structure based 167 on the organizational structure of the resources specified in the 168 OIPF IPTV Solution specifications: 170 urn:oipf: 172 where the syntax of "" is specified in Section 2.2 of the URN 173 Syntax requirements ([RFC2141]). 175 The individual URNs will be assigned by the OIPF through the 176 process of development of OIPF specifications. 178 Relevant ancillary documentation: 180 None. 182 Identifier uniqueness considerations: 184 The OIPF will establish unique identifiers as appropriate and will 185 ensure that an assigned string is never reassigned. 187 Identifier persistence considerations: 189 The OIPF is committed to maintaining the accessibility and 190 persistence of all resources that are officially assigned URNs by 191 the organization. The registration tables and information will be 192 published and maintained by the OIPF on its web site. 194 Process of identifier assignment: 196 The assignment of identifiers is fully controlled and managed by 197 the OIPF. 199 Process of identifier resolution: 201 Not applicable; the "oipf" namespace is not listed with a 202 Resolution Discovery System. 204 Rules for Lexical Equivalence: 206 The "" is case-insensitive. 208 Conformance with URN Syntax: 210 No special considerations. 212 Validation mechanism: 214 None specified. URN assignment will be managed completely and 215 published by the OIPF. 217 Scope: 219 Global 221 3. Examples 223 The following examples of schemas and classification schemes are 224 taken from the current OIPF Release 1 IPTV Solution specification: 226 urn:oipf:device:ig:1 228 urn:oipf:config:oitf:oitfCapabilities:2009 229 urn:oipf:iptv:IPTVProfile:2008 231 urn:oipf:cs:AVMediaFormatCS:2008 233 urn:oipf:cs:ApplicationTypeCS:2009 235 4. Namespace Considerations 237 A unique formal namespace is required by the OIPF in order to specify 238 how the various existing standards can be linked in order to create a 239 true end-to-end ecosystem for standards-based IPTV deployments, and 240 to provide the necessary system-wide resources. 242 URN assignment procedures: 244 The individual URNs shall be assigned through the process of 245 development of OIPF specifications by the Open IPTV Forum e.v 246 (OIPF). The latest information about OIPF defined specifications 247 can always be found at the owner's website at 249 http://www.oipf.tv/specifications 251 URN resolution/delegation: 253 The resolution and delegation shall be determined through the 254 process of development of specifications by the Open IPTV Forum. 256 Since the implementations envisaged cover a wide range of devices 257 with quite different access methods and capabilities, no single 258 resolution or delegation mechanism can be referenced in this 259 document. 261 Type of resources to be identified: 263 Types of resources to be identified include XML schema definition 264 files, classification schemes and identification systems defined 265 and published by OIPF. These resources being identified constitute 266 a metadata system to describe digital multimedia broadcast services 267 or content conveyed as part of such services. 269 The latest OIPF defined specifications can always be found at 271 http://www.oipf.tv/specifications 273 5. Community Considerations 275 URNs defined by the OIPF will be used by implementers of IPTV 276 systems, services, products, and applications based on the OIPF IPTV 277 Solution specification. They are an essential component of the open 278 IPTV ecosystem that is being facilitated by the OIPF. 280 6. Security Considerations 282 There are no additional security considerations other than those 283 normally associated with the use and resolution of URNs in general, 284 which are described in [RFC1737], [RFC2141], and [RFC3406]. 286 This document registers a namespace for URNs. OIPF may assign 287 special meaning to certain of the characters of the Namespace 288 Specific String in its specifications. Any security consideration 289 resulting from such assignment is outside the scope of this document. 291 7. IANA Considerations 293 This document defines a URN NID registration of "oipf". IANA is 294 requested to include it in the URN Namespaces registry. 296 8. References 298 8.1. Normative References 300 [RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for 301 Uniform Resource Names", RFC 1737, December 1994. 303 [RFC2141] Moats, R., "URN Syntax", RFC 2124, May 1997. 305 [RFC3406] Daigle, L., van Gulik, D., Iannella, R. and P. Faltstrom, 306 "Uniform Resource Names (URN) Namespace Definition 307 Mechanisms", October 2002. 309 8.2. Informative References 311 The following specifications are available freely at: 313 http://www.oipf.tv/specifications.html 315 [OIPF1] Open IPTV Forum, "Release 1 Specification, Volume 1 - 316 Overview", V1.1, October 2009. 318 [OIPF2] Open IPTV Forum, "Release 1 Specification, Volume 2 - Media 319 Formats", V1.1, October 2009. 321 [OIPF3] Open IPTV Forum, "Release 1 Specification, Volume 3 - 322 Content Metadata", V1.1, October 2009. 324 [OIPF4] Open IPTV Forum, "Release 1 Specification, Volume 4 - 325 Protocols", V1.1, October 2009. 327 [OIPF5] Open IPTV Forum, "Release 1 Specification, Volume 5 - 328 Declarative Application Environment", V1.1, October 2009. 330 [OIPF6] Open IPTV Forum, "Release 1 Specification, Volume 6 - 331 Procedural Application Environment", V1.1, October 2009. 333 [OIPF7] Open IPTV Forum, "Release 1 Specification, Volume 7 - 334 Authentication, Content Protection and Service Protection", 335 V1.1, October 2009. 337 9. Acknowledgments 339 This document was prepared using 2-Word-v2.0.template.dot. 341 Authors' Address 343 Paul Higgs 344 Chair, OIPF IOT Working Group 345 c/o Ericsson Inc, 6 Concourse Parkway, suite 3000, 346 Atlanta, GA 30328, USA 348 Phone: +1-650-580-1731 349 Email: paul.higgs@ericsson.com 351 Paul Szucs 352 Board Member, OIPF, 353 c/o Sony Europe, Hedelfinger Str. 61, 354 D-70327 Stuttgart, Germany 356 Phone: +49-711-5858-583 357 Email: paul.szucs@eu.sony.com