[AVT] draft-flaks-avt-rtp-ac3-03.txt

"Hager, Todd" <THH@dolby.com> Thu, 30 January 2003 20:31 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09796 for <avt-archive@odin.ietf.org>; Thu, 30 Jan 2003 15:31:05 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0UKYF627473 for avt-archive@odin.ietf.org; Thu, 30 Jan 2003 15:34:15 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UKWeJ27408; Thu, 30 Jan 2003 15:32:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0UJ8rJ22790 for <avt@optimus.ietf.org>; Thu, 30 Jan 2003 14:08:53 -0500
Received: from scandium.dolby.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA07235 for <avt@ietf.org>; Thu, 30 Jan 2003 14:05:07 -0500 (EST)
Received: from platinum.dolby.net ([172.16.33.28]) by 192.168.16.253 with InterScan Messaging Security Suite; Thu, 30 Jan 2003 11:08:01 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C2C892.E7017420"
Subject: [AVT] draft-flaks-avt-rtp-ac3-03.txt
Date: Thu, 30 Jan 2003 11:07:58 -0800
Message-ID: <5FCCC03CAF7C5C4C8E2F995E3D72E1330167381B@platinum.dolby.net>
X-MS-Has-Attach: yes
Thread-Topic: [AVT] draft-flaks-avt-rtp-ac3-03.txt
Thread-Index: AcLGJNPVyZsHEa9KRaWRq8w0MdI3sQCaw3EQ
From: "Hager, Todd" <THH@dolby.com>
To: avt@ietf.org
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>

Hello,

Please find attached the latest version of the RTP Payload Format for
AC-3 Streams
draft, draft-flaks-avt-rtp-ac3-03.txt.  This has just been submitted to
internet-drafts@ietf.org. 

This is the first draft submission with myself replacing Jason Flaks as
the document author. Changes are mostly editorial.

The single technical change in this revision was made to the NDU field 
described in 2.1.1. Previously, the NDU was designated as the high 4 
bits of a byte with the low 4 bits marked as reserved.  Now the NDU is
an 
8-bit number so that no bit shifting is required to process it.

Next efforts will involve reviewing the redundant data mechanism
descibed in 2.3 for conformance with RFC 2198. I expect to issue a -04
release in time for the March 3 deadline.

Regards,
Todd Hager
Dolby Laboratories





Internet Draft                                                 T. Hager
January 2003                                         Dolby Laboratories
Expires: June 2003                                             J. Flaks
                                                  Microsoft Corporation

                  RTP Payload Format for AC-3 Streams
                   <draft-flaks-avt-rtp-ac3-03.txt>


Abstract 

This document describes an RTP payload format for transporting AC-3 
encoded audio data.  AC-3 is a high quality multichannel audio coding 
system used in ATSC HDTV, DVD, film, and other media.  The RTP payload 
format presented in this document provides mechanisms for interleaving 
redundant data, which can increase packet loss resilience.  An 
intelligent method for fragmenting AC-3 frames that exceed the maximum 
transfer unit (MTU) is also described. 


This message (including any attachments) may contain confidential information intended for a specific individual and purpose. If you are not the intended recipient, delete this message. If you are not the intended recipient, disclosing, copying, distributing, or taking any action based on this message is strictly prohibited.