[no subject]

Group:

this is the 1st attempt at the receiver configuration draft that was briefly discussed on the list in the past weeks. It missed the IETF deadline by 2 hours so will only be re-submitted after Nov. 7th so not in time for IETF-61 but I suppose ok for the next one.

Marie-Jose

Internet Engineering Task Force Marie-Jose Montpetit Internet Draft MJMontpetit.com Document: draft-mjm-ipdvb-config-00.txt October 2004 Category: Standards Track Expires March 2005 Protocols for MPEG-2 receiver configuration Status of this Memo 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 becomes aware will be disclosed, in accordance with Section 6 of RFC 3668. 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. Copyright (C) The Internet Society (2004), All Rights Reserved Abstract This document describes a method to bind IPv4/IPv6 addresses and flows to MPEG-2 Transport Streams (TS). Methods are required to signal IPv4/v6 addresses to the link receivers and transmitters. In MPEG-2 networks, an IP address must also be associated with a Packet ID (PID) and specific transmission multiplex. In this document the methods are based on standard XML semantics. This method complements current approaches based on SI table with an IP centric approach. Expires March 2005 [page 1] INTERNET DRAFT Protocols for MPEG-2 receiver configuration October 2004 Table of Contents Document History 1. Introduction 2. Convention used in the document 3. Configuration table 4. Protocols 4.1 Simple Autoconfiguration 4.2 Subscriber Service 4.3 Query/response 5. Transport Issues 6. Conclusions and Recommendations 7. Security Considerations 8. Acknowledgements 9. References 10. Author's Addresses 11. IPR Notices 12. Copyright Statements 13. IANA Considerations Document History -00 This draft is intended as a study item for proposed future work by the IP over DVB WG in this area. 1. Introduction The MPEG-2 stream is defined in the specification ISO/IEC 138181. It provides a time-division multiplexed (TDM) stream that may contain audio, video and other information. Each frame, known as an MPEG-2 TS Packet, contains 4 bytes of header and 188 bytes of data. The standard also defines the PES packet (Packetized Elementary Stream) and the Section or Transport Stream (TS) packet. The PES packet can carry video, audio, private data and was originally used for some data streaming applications; this usage is now historical. Each MPEG-2 TS Packet is associated with one Transport Stream (TS) logical channel, which is identified by a 13 bit Packet ID (PID) carried in the MPEG-2 TS Packet header. Expires March 2005 [page 2] INTERNET DRAFT Protocols for MPEG-2 receiver configuration October 2004 MPEG-2 Receivers may optionally be assigned a Network Point of Attachment (NPA) to uniquely identify the L2 node within the MPEG-2 transmission network. An example of an NPA is the IEEE Medium Access Control (MAC) address. Where such addresses are used, these must also be signalled by the address resolution procedure. Finally, address resolution may need to signal the format of the data being transmitted. For example, the encapsulation used or any compression scheme that was used at the sender [ID-IPDVB-ARCH]. The development of IP_layer address resolution has merit particularly for IP-only services and two-way MPEG-2 transmission networks. It releases a Receiver from performing MPEG-2 table processing, it allows much more dynamic association of PIDs to traffic: association/freeing of PIDs in response to join or prune actions taken by multicast routing protocols, or on assignment of new IP addresses using DHCP/DHCPv6. These protocols are implemented above the IP layer in a portable way not dependent on specific receiver hardware/drivers and allows future integration of the functions within IP routers and IP management devices. This document defines a syntax for describing the addressing information and a method to communicate the data. The specification and definition of address resolution mechanisms relating to MPEG-2 PID to/from IP address mapping function, QoS association and other mapping functions (e.g. parameters associated with a PID/Multiplex) will be supported using a table based protocol to be extensible to ensure a wide applicability to different types of MPEG-2 networks and intended applications. The mechanisms introduced here extensively re-use existing protocol machinery. XML schemas are be defined and used to present the required information from the tables. Because XML implements standard grammar and syntax this address resolution information would be common to all MPEG-2 networks. SOAP protocol exchanges may be a suitable method to transfer the table information and SIP could provide the signaling mechanisms in between hosts. Expires March 2005 [page 3] INTERNET DRAFT Protocols for MPEG-2 receiver configuration October 2004 2. Conventions used in this document AIT: Application Information Table specified by the Multimedia Home Platform (MHP) specifications [ETSI-MHP]. This table may carry IPv4/IPv6 to MPEG-2 TS address resolution information. ATSC: Advanced Television Systems Committee [ATSC]. A set of framework and associated standards for the transmission of video, audio, and data, using the ISO MPEG-2 standard. DVB: Digital Video Broadcast [ETSI-DVB]. A set of framework and associated standards for the transmission of video, audio, and data, using the ISO MPEG-2 standard. DVB-RCS: Digital Video Broadcast Return Channel via Satellite. A bi-directional IPv4/IPv6 service employing low-cost Receivers. MPE: Multiprotocol Encapsulation [ETSI-DAT, ETSI-DAT1]. A scheme that encapsulates Ethernet frames or IP Packets, creating a DSM-CC Section. The Section will be sent in a series of TS Packets over a TS Logical Channel. MPEG-2: A set of standards specified by the Motion Picture Experts Group (MPEG), and standardized by the International Standards Organisation (ISO) [ISO-MPEG]. NPA: Network Point of Attachment. Addresses primarily used for station (receiver) identification within a local network (e.g. IEEE MAC address). PES: Packetized Elementary Stream. A format of MPEG-2 TS packet payload usually used for video or audio information in MPEG-2 [ISO-MPEG]. PID: Packet Identifier. A 13-bit field carried in the header of all MPEG-2 Transport Stream packets [ISO-MPEG]. This is used to identify the TS Logical Channel to which it belongs. SI TABLE: Service Information Table. In this document, the term is used to describe any table used to convey information about the service carried in a TS Multiplex (e.g. [ISO-MPEG]). SI tables are carried in MPEG-2 private sections. TS: Transport Stream [ISO-MPEG], a method of transmission at the MPEG-2 level using TS Packets; it represents level 2 of the ISO/OSI reference model. See also TS Logical Channel and TS Multiplex. TS LOGICAL CHANNEL: A channel identified at the MPEG-2 level; it represents level 2 of the ISO/OSI reference model. All packets sent over a channel carry the same PID value. Expires March 2005 [page 4] INTERNET DRAFT Protocols for MPEG-2 receiver configuration October 2004 TS MULTIPLEX: A set of MPEG-2 TS Logical Channels sent over a single common physical bearer (i.e. a link transmitting at a specified symbol rate, FEC setting, and transmission frequency). TS PACKET: A fixed-length 188B unit of data sent over an MPEG-2 multiplex [ISO-MPEG]; it corresponds to the cells, of e.g. ATM networks, and is frequently also referred to as a TS_cell. Each TS Packet carries a 4B header, plus optional overhead. Each TS packet carries a PID value to associate it with a single TS Logical Channel. 3. Configuration Table and Syntax The configuration table is created from known bindings at the Gateway ULE/MPE Encapsulation gateway). Alternatively, future gateways may wish to use the same file format for configuration since similar information is required by a gateway to map IP packets to PIDs and the L2 services. This table is compliant to requirements in [ARCH] to support multicast networks, address scoping and security. The (auto)configuration table can be written into the XML script using a specified syntax. The server either outputs the configuration in XML, or takes an XML input (same format) to build the configuration. There has been work on the use of XML for MPEG-2 configuration [ATSC] Example of the syntax to be used for the receiver configuration include: - version: version of the protocol - system_ID: identifier of the requesting system - system_authentication - server-ID: identifier of the serving system - server_authentication - PID - IP_version: 4/6 - Address_type: unicast/multicast - IP_Address - IP_address_mask - Proprietary_information: a pointer to operator-specific information Other information could include QoS information, MAC information etc. <<< real Implementation information requested >>> Expires March 2005 [page 5] INTERNET DRAFT Protocols for MPEG-2 receiver configuration October 2004 4. Protocol While there is a single syntax for all autoconfiguration the information can be accessed using different approaches: - a simple autoconfiguration where the table information is posted to a web site - a subscriber based service where the configuration information is sent via multicast to subscribing terminals; information that is available is advertised; users can decide which configuration service they are intested into - a query response mechanism where individual terminal can access the server and request specific information 4.1 Simple Autoconfiguration <<< to be added >>> 4.2 Subscriber Service <<< to be added >>> 4.3 Query/response <<< to be added >>> 5. Transport Issues The recommended transport is to be above the IP level. This has the advantages of: - Common operation with other IP protocols and management. - Potential for portable implementations across a variety of platforms - Ability to re-use transport protocols already developed and proven within the IP community - Opens the potential to integrate operations with other ISP functions to perform automated service provision, traffic engineering and operational tasks. 6. Conclusion An open syntax is defined to configure address resolution information for MPEG-2 transmission networks. The syntax may be used to store and manage the mappings between MPEG-2 and IP layer protocols. The document provides guidance on using the syntax and describes methods in which the syntax may be used to provide address resolution within MPEG-2 transmission networks. 7. Security Considerations <<< Not defined at this point; some issues will raise from the use of transport mechanisms as there are know security flaws in SOAP and some SIP mechanisms; the use of digital signatures on the XML information is also perceived to protect information>>> Expires March 2005 [page 6] INTERNET DRAFT Protocols for MPEG-2 receiver configuration October 2004 8. Acknowledgments The author wishes to thank Gorry Fairhurst, Michael Mercurio and the ipdvb WG members for their inputs. The author would also like to acknowledge the support of the European Space Agency. 9. References 9.1 Normative Reference [ISO-MPEG] ISO/IEC DIS 13818-1:2000 "Information technology: Generic coding of moving pictures and associated audio information: Systems", International Standards Organisation (ISO). 9.2 Informative References [ATSC] ATSC Document on XML Specifications [ID-IPDVB-ARCH] Montpetit, M.J., Fairhurst, G., Clausen, H.D., Collini-Nocker, B., and H. Linder, "Architecture for IP transport over MPEG-2 Networks", Internet Draft, draft-ipdvb-arch-00.txt, October 2004, Work in Progress, IPDVB WG. [RFC826] Plummer, D. "An Ethernet Address Resolution Protocol", RFC 826, IETF, November 1982. [RFC1122] B. Braden, ed., "Requirements for Internet Hosts - Communication Layers", RFC 1122. [RFC1112] Deering, S.E., "Host Extensions for IP Multicasting", RFC1112, (STD05), IETF. August 1989. [RFC2461] Narten, T., Nordmark, E., and W. Simpson, "Neighbor Discovery for IP Version 6 (IPv6), RFC 2461, December 1998. [RFC2464] Crawford. M., "Transmission of IPv6 Packets over Ethernet Networks", RFC2464, IETF December 1998. 9. Author's Address Marie-Jose Montpetit Email: marie@mjmontpetit.com Expires March 2005 [page 7] INTERNET DRAFT Protocols for MPEG-2 receiver configuration October 2004 10. IPR Notices 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. 11. Copyright Statement Copyright (C) The Internet Society (2004). 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. 12. IANA Considerations NOT KNOWN AT THIS TIME. Expires March 2005 [page 8]