Re: [AVT] New draft-ietf-avt-mpeg4-simple-07
jan.vandermeer@philips.com Wed, 26 February 2003 22:29 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 RAA29870 for <avt-archive@odin.ietf.org>; Wed, 26 Feb 2003 17:29:50 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1QMdWu17892 for avt-archive@odin.ietf.org; Wed, 26 Feb 2003 17:39:32 -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 h1QMcXp17869; Wed, 26 Feb 2003 17:38:33 -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 h1QMb1p17145 for <avt@optimus.ietf.org>; Wed, 26 Feb 2003 17:37:01 -0500
Received: from gw-nl4.philips.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29835 for <avt@ietf.org>; Wed, 26 Feb 2003 17:26:48 -0500 (EST)
From: jan.vandermeer@philips.com
Received: from smtpscan-nl4.philips.com (smtpscan-nl4.philips.com [130.139.36.24]) by gw-nl4.philips.com (Postfix) with ESMTP id 9B769A3DE1; Wed, 26 Feb 2003 23:30:42 +0100 (MET)
Received: from smtprelay-nl1.philips.com (localhost [127.0.0.1]) by smtpscan-nl4.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id XAA25394; Wed, 26 Feb 2003 23:30:42 +0100 (MET)
Received: from ehv501soh.diamond.philips.com (e3soh01.diamond.philips.com [130.139.54.47]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id XAA26552; Wed, 26 Feb 2003 23:30:41 +0100 (MET)
To: Franceschini Guido <Guido.Franceschini@TILAB.COM>
Cc: avt@ietf.org, Colin Perkins <csp@isi.edu>
Subject: Re: [AVT] New draft-ietf-avt-mpeg4-simple-07
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.9a January 7, 2002
Message-ID: <OFBC61810F.FDBB7ED5-ONC1256CD9.006BFB1F-C1256CD9.007BA2C0@diamond.philips.com>
Date: Wed, 26 Feb 2003 23:28:41 +0100
X-MIMETrack: Serialize by Router on ehv501soh/H/SERVER/PHILIPS(Release 5.0.9a |January 7, 2002) at 26/02/2003 23:28:54, Serialize complete at 26/02/2003 23:28:54
Content-Type: multipart/alternative; boundary="=_alternative 007BA2BAC1256CD9_="
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>
Guido, I agree with Colin to a large extend. We are talking about the case of interleaving where we have a certain interleaving pattern. In case of variable duration, any AU-index value (including zero) only occurs again after the applied interleaving pattern "passed sufficiently". If there are two subsequent RTP packets with the same AU-index value, then this is clearly one of the roll-over problems that the referenced rule states "MUST NOT" occur. But note that the value zero (as any other value) may occur once in a while, but that the AU-index value always differs in subsequent RTP packets in case of variable duration. Which means that the answer to your original question is that you don't need to look further than two subsequent RTP packets. Best regards, Jan Colin Perkins <csp@isi.edu> 2003-02-26 04:49 PM To: Franceschini Guido <Guido.Franceschini@TILAB.COM> cc: Jan vanderMeer/EHV/CE/PHILIPS@EMEA3 avt@ietf.org Subject: Re: [AVT] New draft-ietf-avt-mpeg4-simple-07 Classification: Guido, The paragraph you quoted continues with "When transmitting Access Units of variable duration ... the transmitter MUST use the AU-Index to encode the index information required for reordering..." which implies non-zero values to my reading. Colin --> Franceschini Guido writes: >Colin, > >your reply makes me very happy. I'd love to see this draft becoming an RFC. >So apparently it is already specified that AU-Index will never be 0 when >"useful". That is just perfect -I was assuming that 0 was an acceptable >coded value for the variable duration case-. I failed however to find such >a statement. Could you or Jan point me to it ? > >Thanks again >Guido > >-----Original Message----- >From: Colin Perkins [mailto:csp@isi.edu] >Sent: Wednesday, February 26, 2003 4:19 PM >To: Franceschini Guido >Cc: jan.vandermeer@philips.com; avt@ietf.org >Subject: Re: [AVT] New draft-ietf-avt-mpeg4-simple-07 > > >Guido, > >--> Franceschini Guido writes: >>Jan, >> >>unfortunately I have to disagree with the text you modified with respect >>to Colin's text. >>I am fine with supporting early implementations, but the wording used >>is, IMHO, not suitable. More specifically you wrote: >> >> If the "constantDuration" parameter is not present, then Access >> Units are assumed to have a variable duration, unless the AU-Index >> is present and coded with the value 0 in each RTP packet. >> >>How can a receiver implement the rule above? Should it observe 1, 10, >>1000 or infinite packets before determining that the "AU-Index is >>present and coded with the value 0 in each RTP packet" ? > >One packet is sufficient. If the Access Units have variable duration, the >AU-Index will never be zero, if they have fixed duration it will always be >zero. The rest of the paragraph you quoted makes this explicit. > >>What is the exact legacy that you want to support ? Maybe there is a >>different mechanism to support it. For example, a specific mode >>definition might IMPLY a specific "constantDuration" value, without >>writing this explicitely in the SDP. > >Not if it wishes to comply with this specification. > >Colin >_______________________________________________ >Audio/Video Transport Working Group >avt@ietf.org >https://www1.ietf.org/mailman/listinfo/avt > > >==================================================================== >CONFIDENTIALITY NOTICE >This message and its attachments are addressed solely to the persons >above and may contain confidential information. If you have received >the message in error, be informed that any use of the content hereof >is prohibited. Please return it immediately to the sender and delete >the message. Should you have any questions, please contact us by >replying to MailAdmin@tilab.com. Thank you >==================================================================== >_______________________________________________ >Audio/Video Transport Working Group >avt@ietf.org >https://www1.ietf.org/mailman/listinfo/avt
- [AVT] New draft-ietf-avt-mpeg4-simple-07 jan.vandermeer
- RE: [AVT] New draft-ietf-avt-mpeg4-simple-07 Franceschini Guido
- Re: [AVT] New draft-ietf-avt-mpeg4-simple-07 Colin Perkins
- RE: [AVT] New draft-ietf-avt-mpeg4-simple-07 Franceschini Guido
- Re: [AVT] New draft-ietf-avt-mpeg4-simple-07 Colin Perkins
- Re: [AVT] New draft-ietf-avt-mpeg4-simple-07 jan.vandermeer