Re: [AVT] Comments on EAC-3 RTP payload format
Colin Perkins <csp@csperkins.org> Tue, 04 April 2006 15:24 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FQnOd-0002KZ-8g; Tue, 04 Apr 2006 11:24:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FQnOc-0002KU-JC for avt@ietf.org; Tue, 04 Apr 2006 11:24:42 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FQnOb-00031G-AM for avt@ietf.org; Tue, 04 Apr 2006 11:24:42 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:51101) by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42) id 1FQnOa-0002ku-CB; Tue, 04 Apr 2006 16:24:40 +0100
In-Reply-To: <44326327.7080902@ericsson.com>
References: <44326327.7080902@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v749.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <871DC521-AA69-47CC-89DB-A635B4A9D3A4@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Comments on EAC-3 RTP payload format
Date: Tue, 04 Apr 2006 16:24:37 +0100
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.749.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: "Link, Brian" <BDL@dolby.com>, IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
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>
Errors-To: avt-bounces@ietf.org
On 4 Apr 2006, at 13:14, Magnus Westerlund wrote: > I have reviewed draft-ietf-avt-rtp-eac3-00.txt and have two comments: > > 1. The definition of bitStreamConfig parameter is not clear on how > to determine which streams belong to which program. I think there > needs to be some explanation on the seperator. From the example it > seems that a requirement to order "i" before "d" and any new "i" is > a new program would solve the issue. > > 2. Section 5.2: > "To ensure interoperability with > receivers which support the AC-3 payload format, but not the > E-AC-3 payload format, a sender which desires to send an AC-3 > bit > stream in the E-AC-3 payload format SHOULD also offer the > session > in the AC-3 payload format by including attribute lines for both > media sub-types: 'ac3' and 'eac3'." > > I would propose to change "including attribute lines for both" to > "include payload types for both" If these changes are acceptable, I suggest we take them as last call comments and submit an updated draft containing them when the last call period ends. Colin _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] Comments on EAC-3 RTP payload format Magnus Westerlund
- Re: [AVT] Comments on EAC-3 RTP payload format Colin Perkins
- [AVT] RE: Comments on EAC-3 RTP payload format Link, Brian