Network Working Group S. Aoki Internet-Draft Japan FM Network Expires: August 8, 2005 M. Kawamori NTT February 7, 2005 The broadcast program resource identifier in the MPEG-2 transport stream over ISDB system draft-aoki-arib-uri-00.txt Status of this Memo This document is an Internet-Draft and is subject to all provisions of section 3 of RFC 3667. By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she become aware will be disclosed, in accordance with RFC 3668. This document may not be modified, and derivative works of it may not be created, except to publish it as an RFC and to translate it into languages other than English. Internet-Drafts are working documents 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 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on August 8, 2005. Copyright Notice Copyright (C) The Internet Society (2005). Abstract The Uniform Resource Identifier (URI) scheme "arib:" has been devised to allow acquiring the current or future scheduled publications of broadcast media content from the internet. These broadcast media Aoki & Kawamori Expires August 8, 2005 [Page 1] Internet-Draft draft-aoki-arib-uri-01.txt February 2005 contents are distributed with the MPEG-2 TS [ISO/IEC 13818-1] on the ISDB (Integrated Services Digital Broadcasting) broadcast system, which is specified in the [ITU-R BT.1306] and [ITU-R BS.1114]. The initial intended application is to acquire the digital TV/Radio broadcasting programme from the program guide in the internet or the digital broadcasting set-top box. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Scheme Definition . . . . . . . . . . . . . . . . . . . . . . 3 2.1 The Arib URI Scheme . . . . . . . . . . . . . . . . . . . 3 2.1.1 scheme definition . . . . . . . . . . . . . . . . . . 4 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.1 broadcaster_domain . . . . . . . . . . . . . . . . . . . . 5 3.2 Normal examples . . . . . . . . . . . . . . . . . . . . . 5 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 7 A. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 Intellectual Property and Copyright Statements . . . . . . . . 8 Aoki & Kawamori Expires August 8, 2005 [Page 2] Internet-Draft draft-aoki-arib-uri-01.txt February 2005 1. Introduction The digital broadcasting service has been available to the home in recent years. With the advent of digital broadcasting, each broadcasting program (A/V contents) became identifiable in the digital domain. The TV/Radio broadcasting programme such as entertainment or news service providing audio visual content or private data module are delivered through the broadband internet as well as digital broadcasting. The digital broadcasting has made the EPG (Electronic Programming Guide) service available by which people are able to search-select and acquire the favorite programme. The EPG also informs the user of the most interesting programs that fit specified viewing criteria, and the user can check program availability. This programming guide is available to provide on the internet or on the service in the digital broadcasting. As well as the programming guide (EPG) on the service in the digital broadcasting, the EPG service on the web is also required to identify the actual broadcasted programme material. This document defines the "arib" Uniform Resource Identifier (URI) scheme for audio visual material that is transmitted in the MPEG-2 systems over ISDB broadcasting mechanism [ITU-R BT.1306] and [ITU-R BS.1114] which was standardized in the Association of Radio Industries and Businesses (ARIB). This "arib:" URI is formed in conformity with the URI generic syntax [RFC3986] to have high affinity with the internet. 2. Scheme Definition 2.1 The Arib URI Scheme The "arib" URI scheme is used to refer to the audio visual material transmitted in the MPEG-2 transport stream over ISDB broadcast system as it specified in [ITU-R BT.1306] and [ITU-R BS.1114]. The system overview of the audio/visual transmission mechanism is described as follows. Audio/Visual or Private data components for constituting the Radio/TV program (service) compose the MPEG-2 Transport Stream which is represented in the level 2 of the ISO/OSI reference model. Composed transport stream is transmitted over the satellite or terrestrial media in the form of including associated service information. Aoki & Kawamori Expires August 8, 2005 [Page 3] Internet-Draft draft-aoki-arib-uri-01.txt February 2005 +---------------------------------------------------+ | Broadcasting Network | | (e.g. Satellite, Terrestrial) | | +---------------------------------------+ | | | Channel |-* | | | (a transport stream) | | | | | +-----------------------------+ | | | | | | Service |-* | | | | | | +---------------------+ | | | | | | | | | Audio/Visual and |-* | | | | | | | | | Private data module | | | | | | | | | | | component | | | | | | | | | | +---------------------+ | | | | | | | | | *---------------------* | | | | | | | | | | | | | | | +-----------------------------+ | | | | | | *-----------------------------* | | | | | | | | | +---------------------------------------+ | | | *---------------------------------------* | | | +---------------------------------------------------+ Conceptual Transmission Model 2.1.1 scheme definition The "arib" URI takes the form aribURI = "arib" ":" path path = [ "//" broadcaster_domain ] comp_path The comp_path can not start with two slash ("//") characters when broadcaster_domain is not present. 2.1.1.1 broadcaster_domain < broadcaster_domain > is considered as the unique broadcast authority in the domestic digital broadcasting network. Each authority governs name space ( < comp_path >) of their audio visual material and private data module. The broadcaster_domain component, consists of a sequence of characters separated by ".", is preceded by a double slash ("//") and is terminated by the next slash ("/"). broadcaster_domain = 0*255 ( unreserved / sub-delims ) unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~" Aoki & Kawamori Expires August 8, 2005 [Page 4] Internet-Draft draft-aoki-arib-uri-01.txt February 2005 sub-delims = "!" / "$" / "&" / "'" / "(" / ")" / "*" / "+" / "," / ";" / "=" This element (< broadcaster_domain >) consists of unique name in the whole digital broadcasting network in the country to which administration of the country assigns conforming to the URI. 2.1.1.2 comp_path consists of a sequence of characters separated by a slash ("/") character for defining the audio visual component tag number and private data module ID within the scope of the URI's scheme and naming authority (). comp_path = *( "/" segment ) segment = *pchar pchar = unreserved / pct-encoded / sub-delims / ":" / "@" This , organized in hierarchical form or the non-hierarchical form, serves to identify an audio visual material or private data resource in the MPEG-2 system over ISDB digital broadcasting mechanism. 3. Examples 3.1 broadcaster_domain The normative description of < broadcaster_domain > corresponds to the information of the broadcaster who transmits the broadcasting program by the MPEG-2 transport stream. broadcaster_domain = original_network_id "." transport_stream_id "." service_id [ "." event_id ] [ ";" content_id ] original_network_id = 0*6 ( ALPHA / DIGIT ) transport_stream_id = 0*6 ( ALPHA / DIGIT ) service_id = 0*6 ( ALPHA / DIGIT ) content_id = 0*10 ( ALPHA / DIGIT ) event_id = 0*6 ( ALPHA / DIGIT ) 3.2 Normal examples Examples of valid "arib" URI. For example, both Aoki & Kawamori Expires August 8, 2005 [Page 5] Internet-Draft draft-aoki-arib-uri-01.txt February 2005 arib://ORIGNT.TSNUMB.SERVCE/FF/0000 and arib://ORIGNT.TSNUMB.SERVCE.EVENT/FF/0000 The "arib" URI string on which < broadcaster_domain > was omitted, is transformed to its target URI with default broadcaster_domain name. arib:/FF/0000 = arib://broadcaster_domain/FF/0000 4. Security Considerations The "arib" URI scheme syntax is subject to the same security considerations with the generic URI syntax [RFC3986]. The "arib" URI provides a resolution mechanism to acquire the audio/visual data transmitting in MPEG-2 transport stream over ISDB system. The software that resolves "arib" URI for acquiring the audio/visual material is supposed to have the function of decoding the MPEG-2 transport stream over ISDB broadcast system. 5. IANA Considerations This section provides the information required to register the arib: URI scheme with following registration template in accordance with [RFC 2717]. The IANA registry for URI schemes should be updated to include the arib: URI scheme when the arib: URI scheme is accepted for the publication of an RFC. Registration Template URL scheme name: arib URL scheme syntax: Section 2 Character encoding considerations: conformance with RFC3986, no special considerations. Intended usage: Sections 1 Security considerations: Section 4 Contact: Shigeru Aoki, The Japan FM Network Author/Change Controller: IESG 6 References [RFC3986] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", January 2005. Aoki & Kawamori Expires August 8, 2005 [Page 6] Internet-Draft draft-aoki-arib-uri-01.txt February 2005 [RFC1738] Berners-Lee, T., Masinter, L. and M. McCahill, "Uniform Resource Locators (URL)", December 1994. [RFC2717] Petke, R. and I. King, "Registration Procedures for URL Scheme Names", November 1999. [ISO/IEC 13818-1] Society of Motion Picture and Television Engineers, "Information technology -- Generic coding of moving pictures and associated audio information: Systems", December 2000. [ITU-R BT.1306] International Telecommunication Union, "Error-correction, data framing, modulation and emission methods for digital terrestrial television broadcasting", October 2000. [ITU-R BS.1114] International Telecommunication Union, "Systems for terrestrial digital sound broadcasting to vehicular, portable and fixed receivers in the frequency range 30-3 000 MHz", February 2004. Authors' Addresses Shigeru Aoki Japan FM Network 1-8 Kojimachi Chiyoda-ku, TOKYO 102-0083 JAPAN Phone: +81 3 3221 0244 EMail: shig@center.jfn.co.jp Masahito Kawamori NTT JAPAN Phone: +81 46 859 2517 EMail: kawamori.masahito@lab.ntt.co.jp Appendix A. Acknowledgements The authors would like to acknowledge the support of the members of the Association of Radio Industries and Businesses and their work in the development of the "arib" URI scheme. Aoki & Kawamori Expires August 8, 2005 [Page 7] Internet-Draft draft-aoki-arib-uri-01.txt February 2005 Intellectual Property Statement The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Disclaimer of Validity This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Copyright Statement Copyright (C) The Internet Society (2005). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Aoki & Kawamori Expires August 8, 2005 [Page 8]