RE: [AVT] Comments on draft-ietf-avt-ulp-11
"Adam Li" <adamli@hyervision.com> Thu, 28 July 2005 16:20 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DyB7u-0005WF-1u; Thu, 28 Jul 2005 12:20:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DyB7s-0005W3-9u for avt@megatron.ietf.org; Thu, 28 Jul 2005 12:20:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09882 for <avt@ietf.org>; Thu, 28 Jul 2005 12:20:49 -0400 (EDT)
Received: from mailgate2.dslextreme.com ([66.51.199.95]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DyBdK-0002Kk-Ot for avt@ietf.org; Thu, 28 Jul 2005 12:53:25 -0400
Received: from mail5.dslextreme.com (unknown [192.168.7.93]) by mailgate2.dslextreme.com (Postfix) with SMTP id E78F93A63F4 for <avt@ietf.org>; Thu, 28 Jul 2005 09:20:33 -0700 (PDT)
Received: (qmail 6933 invoked from network); 28 Jul 2005 16:20:28 -0000
Received: from unknown (HELO server.hyervision.com) (66.159.193.111) by mail5.dslextreme.com with (EDH-RSA-DES-CBC3-SHA encrypted) SMTP; Thu, 28 Jul 2005 09:20:28 -0700
Received: from elephant (adsl-66-159-193-142.dslextreme.com [66.159.193.142]) by server.hyervision.com (8.13.3/8.12.11) with ESMTP id j6SGOH1h004035; Thu, 28 Jul 2005 09:24:24 -0700 (PDT)
Message-Id: <200507281624.j6SGOH1h004035@server.hyervision.com>
From: Adam Li <adamli@hyervision.com>
To: 'Andrea Lorenzo VITALI' <andrea.vitali@st.com>
Subject: RE: [AVT] Comments on draft-ietf-avt-ulp-11
Date: Thu, 28 Jul 2005 09:20:21 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
In-Reply-To: <42E5DEC1.6070706@st.com>
Thread-Index: AcWRr9USd0BHf8HSTU2iGS6t46z8PQB3HzcA
X-DSLExtreme-MailGate-Information: Please contact the ISP for more information
X-DSLExtreme-MailGate: Found to be clean
X-MailScanner-From: adamli@hyervision.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
Content-Transfer-Encoding: 7bit
Cc: 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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
Hi Andrea, Thanks for the comments. For your question (1), it will be doable technically, though it will greatly increase the latency of the recovery operation in additional to increasing the complexity and the memory requirement on the receiving end. At this stage of this draft, a better solution may be to include your proposal in other more complex schemes in development? For your question (2), protecting data multiple times is not as straightforward as it looks. The recovery criteria are complicated especially at higher level where the data is only worth recovering when all the lower level data are recoverable. In most cases, multiple protection in higher level is not only helpless, but also wastes bandwidth. In view of that, the multiple protection is not really useful for any level higher than 0. In additional protecting data multiple times would greatly complicate both the protection process and recovery process. It puts more constraint on the protection as the length has to stay constant for all the groups. That's the rationale for that constraint. For your remark (1), great suggestion. When that paragraph of the draft is first read, it is can be a little confusing between the protection level (which is just a number) and strength of protection. I will fix it as you suggested. For your remark (2), thanks for the information. Adam > -----Original Message----- > From: Andrea Lorenzo VITALI [mailto:andrea.vitali@st.com] > Sent: Monday, July 25, 2005 11:57 PM > To: Adam Li > Cc: avt@ietf.org > Subject: Re: [AVT] Comments on draft-ietf-avt-ulp-11 > > I have reviewed the draft and I have a couple of questions. > > 1) Have you considered the possibility to refer to non-consecutive RTP > packets? > > Currently, bits in the mask refer to consecutive RTP packets: starting > from the > base sequence number SN: SN+0, SN+1, SN+2 ... SN+i, where 0<=i<24 in > RFC2733 and > 0<=i<16 or 0<=i<48 in ULP. > > It has been proposed in the MPEG forum to refer to non-consecutive RTP > packets > by specifying an offset L: SN+0*L, SN+1*L, ... SN+i*L, where 0<=i<24 as in > RFC2733. > > Please find attached a document on this extension to RFC2733. > > > 2) What is the rational behind the costraint a) in par.7.5? > > I copy it here for your convenience: > " a. A media packet SHALL be protected only once at each > protection level higher than level 0. A media packet MAY be > protected more than once at level 0 by different packets, > providing the protection lengths of level 0 of these packets > are equal. > " > > This poses constraints on raised bits in masks for level>0. But perhaps it > would > be easier to let the user care and give an hint on the usefulness of the > constraint... > > -- > > I have also a couple of remarks. > > 1) I was confused by reading in the introduction the following phrase: > > " Lower protection levels provide greater protection by using smaller > group sizes (compared to higher protection levels) for generating > the FEC packet. > " > > "Lower protections levels" made me think about a low protection but then I > read > "greater protection". The contradiction (low or great protection?) > confused me. > > Of course, this is a problem only for 1st time readers. However, it may be > useful to rephrase as follows: > > " High priority levels provide greater protection ... > ... (compared to low priority levels ... > " > > Then, it can be specified that levels are numbered from hi-pri to low-pri > starting from 0. > > > 2) I appreciated the introduction and the reference to UXP. > > I think you may find it useful to have a look at the attached presentation, > which compares several proposed FEC schemes: RFC2733, ULP, UXP, etc. > > > Best regards, > > Andrea > > -- > ______________________________________________________________ > > Andrea VITALI andrea.vitali@st.com > > tel (+39) 039 603 7244 mobile (+39) 347 93 08 433 > fax (+39) 039 603 6129 > > STMicroelectronics > Centro Direzionale COLLEONI - Palazzo "DIALETTICA" > 20041 Agrate Brianza (MI) ITALY > ______________________________________________________________ > > _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] Comments on draft-ietf-avt-ulp-11 Magnus Westerlund
- Re: [AVT] Comments on draft-ietf-avt-ulp-11 Andrea Lorenzo VITALI
- Re: [AVT] Comments on draft-ietf-avt-ulp-11 Magnus Westerlund
- RE: [AVT] Comments on draft-ietf-avt-ulp-11 Adam Li