Subject: [AVT] FW: New Version Notification for draft-schmidt-avt-rfc3016bis-01

From: "BONT, Frans DE" <[email-masked]>
Date: Fri, 27 Feb 2009 15:50:53 +0100

This draft is an update of RFC3016.

From a high level perspective the following points have been addressed:

- The audio payload format (LATM) referenced in RFC 3016 is binary incompatible to the format used in 3GPP.
- The audio signaling format (StreamMuxConfig) referenced in RFC 3016 is binary incompatible to the format used in 3GPP.
- The audio parameter "SBR-enabled" is not defined within RFC 3016 but used by 3GPP
- The rate parameter specification in ambiguous in the presence of SBR (Spectral Band Replication)
- Furthermore some (older) e-mail comments from the AVT list have been addressed and signaling support for MPEG surround was added

Note that to our best knowledge RFC3016 is only used by 3GPP and this work just aligns the specification with the way the format is used in the field. Currently we are not aware that there is an incompatibility.

We'd like this to be considered for adoption as an AVT working group draft.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-schmidt-avt-rfc3016bis-01.txt

Best regards,
Frans

Frans de Bont,
Philips Applied Technologies,
High Tech Campus 5, 5656 AE Eindhoven
Tel: ++31 40 2740234, Fax: ++31 40 2744108
Room HTC-5/5.019
http://www.apptech.philips.com

-----Original Message-----
From: IETF I-D Submission Tool [mailto:[email-masked]]
Sent: 2009 Feb 27 2:55 PM
To: BONT, Frans DE
Cc: [email-masked]; [email-masked]
Subject: New Version Notification for draft-schmidt-avt-rfc3016bis-01

A new version of I-D, draft-schmidt-avt-rfc3016bis-01.txt has been successfuly submitted by Frans Bont and posted to the IETF repository.

Filename:        draft-schmidt-avt-rfc3016bis
Revision:        01
Title:           RTP Payload Format for MPEG-4 Audio/Visual Streams
Creation_date:   2009-02-27
WG ID:           Independent Submission
Number_of_pages: 26

Abstract:
This document describes Real-Time Transport Protocol (RTP) payload
formats for carrying each of MPEG-4 Audio and MPEG-4 Visual
bitstreams without using MPEG-4 Systems.  For the purpose of directly
mapping MPEG-4 Audio/Visual bitstreams onto RTP packets, it provides
specifications for the use of RTP header fields and also specifies
fragmentation rules.  It also provides specifications for
Multipurpose Internet Mail Extensions (MIME) type registrations and
the use of Session Description Protocol (SDP).

Comments are solicited and should be addressed to the working group's
mailing list at [email-masked] and/or the author(s).

The IETF Secretariat.

The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.