idnits 2.17.1 draft-schmidt-avt-mps-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 21. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 488. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 499. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 506. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 512. 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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC3640, but the abstract doesn't seem to directly say this. It does mention RFC3640 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year (Using the creation date from RFC3640, updated by this document, for RFC5378 checks: 2001-09-21) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 15, 2008) is 5822 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. '14496-1' -- Possible downref: Non-RFC (?) normative reference: ref. '14496-3' -- Possible downref: Non-RFC (?) normative reference: ref. '23003-1' Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 11 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 AVT F. de Bont 3 Internet-Draft Philips Electronics 4 Updates: 3640 (if approved) S. Doehla 5 Intended status: Standards Track Fraunhofer IIS 6 Expires: November 16, 2008 M. Schmidt 7 Dolby Laboratories 8 R. Sperschneider 9 Fraunhofer IIS 10 May 15, 2008 12 RTP Payload Format for Elementary Streams with MPEG Surround multi- 13 channel audio 14 draft-schmidt-avt-mps-00.txt 16 Status of this Memo 18 By submitting this Internet-Draft, each author represents that any 19 applicable patent or other IPR claims of which he or she is aware 20 have been or will be disclosed, and any of which he or she becomes 21 aware will be disclosed, in accordance with Section 6 of BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF), its areas, and its working groups. Note that 25 other groups may also distribute working documents as Internet- 26 Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt. 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html. 39 This Internet-Draft will expire on November 16, 2008. 41 Abstract 43 This memo describes extensions for the RTP payload format defined in 44 RFC3640 for the transport of MPEG Surround multi-channel audio. 45 Additional MIME Type parameters are defined to signal backwards 46 compatible transmission inside an MPEG-4 audio elementary stream. In 47 addition a layered transmission scheme without using the MPEG-4 48 systems framework is presented to transport an MPEG Surround 49 elementary stream via RTP in parallel with an RTP stream containing 50 the downmixed audio data. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 3. Definitions and Abbreviations . . . . . . . . . . . . . . . . 3 57 3.1. Definitions . . . . . . . . . . . . . . . . . . . . . . . 4 58 3.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 4 59 4. Transport of MPEG Surround . . . . . . . . . . . . . . . . . . 4 60 4.1. Embedded spatial audio data in AAC payloads . . . . . . . 5 61 4.2. MPEG Surround Elementary Stream . . . . . . . . . . . . . 6 62 4.2.1. Low Bit-rate MPEG Surround . . . . . . . . . . . . . . 7 63 4.2.2. High Bit-rate MPEG Surround . . . . . . . . . . . . . 8 64 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 65 5.1. MIME Type registration . . . . . . . . . . . . . . . . . . 9 66 5.2. Registration of Mode Definitions with IANA . . . . . . . . 9 67 5.3. Usage of SDP . . . . . . . . . . . . . . . . . . . . . . . 10 68 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 69 7. Normative References . . . . . . . . . . . . . . . . . . . . . 10 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 71 Intellectual Property and Copyright Statements . . . . . . . . . . 12 73 1. Introduction 75 MPEG Surround (Spatial Audio Coding, SAC) [23003-1] is an 76 International Standard that was finalized by MPEG in January 2007. 77 It is capable of re-creating N channels based on M