Re: [payload] I-D Action: draft-ietf-payload-flexible-fec-scheme-10.txt

"Roni Even (A)" <roni.even@huawei.com> Thu, 06 December 2018 11:03 UTC

Return-Path: <roni.even@huawei.com>
X-Original-To: payload@ietfa.amsl.com
Delivered-To: payload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA62F130DE9 for <payload@ietfa.amsl.com>; Thu, 6 Dec 2018 03:03:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id egVcisoQWirx for <payload@ietfa.amsl.com>; Thu, 6 Dec 2018 03:03:37 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CB00126F72 for <payload@ietf.org>; Thu, 6 Dec 2018 03:03:37 -0800 (PST)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 7E0A55EACD02C; Thu, 6 Dec 2018 11:03:33 +0000 (GMT)
Received: from DGGEMM421-HUB.china.huawei.com (10.1.198.38) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 6 Dec 2018 11:03:35 +0000
Received: from DGGEMM526-MBX.china.huawei.com ([169.254.8.140]) by dggemm421-hub.china.huawei.com ([10.1.198.38]) with mapi id 14.03.0415.000; Thu, 6 Dec 2018 19:03:29 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, Giridhar Mandyam <mandyam@qti.qualcomm.com>
CC: "Ali C. Begen" <ali.begen@networked.media>, "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>, Ben Campbell <ben@nostrum.com>, "payload@ietf.org" <payload@ietf.org>
Thread-Topic: [payload] I-D Action: draft-ietf-payload-flexible-fec-scheme-10.txt
Thread-Index: AQHUdKHUsCqCGfwu2UO8myfbHJx9L6Vxu7iA
Date: Thu, 06 Dec 2018 11:03:29 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD18C85C10@dggemm526-mbx.china.huawei.com>
References: <154137912756.31875.5347836180455863963@ietfa.amsl.com> <A6E85ACB-7039-45B4-8854-0B9161093CB0@nostrum.com> <9C1381B7-A4A0-48FB-A811-FCD8EFA54BAF@networked.media> <e5732f8e-4714-1c14-4d8d-ea58fbc07b3d@nostrum.com> <CAA4MczsFdDHE-LSco9t+bV3Zie3iz1j1Ct=570XmTpT6RbpD9A@mail.gmail.com> <3CAF95D1-2D49-4EA2-9939-B0E4EC9D8C3B@nostrum.com> <8bd36e09cfe845758d52cc0b2aeb166f@NASANEXM01C.na.qualcomm.com> <CAA4Mczt8DwdZWn4AG3XUprxZGCgfjbH+tJ6ToFZDfCGAK9kpHg@mail.gmail.com> <62166FDE-60E2-4C39-97EB-2CE9A21FC9BD@nostrum.com> <DA7E59C1-ED41-4901-810B-0C83B6F197D6@networked.media> <D8A33513-5AD6-4782-919E-B9B166E30498@nostrum.com> <1d9e52a0143b4959b6ae3645846fe7a8@NASANEXM01C.na.qualcomm.com> <9816C546-A722-49CC-8DE2-1055631771A9@nostrum.com> <AM6PR07MB498223FF49ADC9F1B2ED82B095A90@AM6PR07MB4982.eurprd07.prod.outlook.com>
In-Reply-To: <AM6PR07MB498223FF49ADC9F1B2ED82B095A90@AM6PR07MB4982.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.202.135]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/payload/5bGfFEnNt8EIdh1N0PqCYxFEUKs>
Subject: Re: [payload] I-D Action: draft-ietf-payload-flexible-fec-scheme-10.txt
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Payloads working group discussion list <payload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/payload>, <mailto:payload-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/payload/>
List-Post: <mailto:payload@ietf.org>
List-Help: <mailto:payload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/payload>, <mailto:payload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Dec 2018 11:03:42 -0000

Hi,
Can you send these messages to the list.
I am wondering about ToP, I saw a previous question from Magnus about using for example ToP 0,3 (FEC plus retransmission) not allowed by current definition in 5.1.1 but if I read section 4.2.2.3 first paragraph correctly it is allowed
I also assume that Magnus asked for the default value for ToP and I did not see any text in 5.1.1
Roni Even 


-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com] 
Sent: Thursday, December 06, 2018 10:32 AM
To: Ben Campbell
Cc: Ali C. Begen; Mo Zanaty (mzanaty); Roni Even (A); ART ADs; Giridhar Mandyam
Subject: Re: [payload] I-D Action: draft-ietf-payload-flexible-fec-scheme-10.txt

Hi,

I have responded on the first question. Although I don't understand why that went off-list.

I want to comment on the second paragraph below.

On 2018-12-05 19:36, Ben Campbell wrote:
>> On Dec 5, 2018, at 12:28 PM, Giridhar Mandyam <mandyam@qti.qualcomm.com> wrote:
>>
>> I believe his first comment on ToP needs to be addressed in the revision.  I believe his second comment is more problematic, because it refers to a standards-track document that has not achieved RFC status yet (i.e. it may undergo changes), and I am not sure it will help the document.
>>
>>
Considering that draft-ietf-avtext-rid is approved and stuck in RFC-editor missref state on cluster 238 I don't see this as a reason for not addressing my raised issue.

The reason I do want to raise this is that flexfec could be used in a sub-set of cases, but is not necessary in any cases as the linking to the source flow is provided in the FLEXFEC RTP packet. Thus, for making it clear that it is not needed, I think an explicit statement should be added to that effect. If we don't have a statement we might find situations where people will attempt to apply it and gets into the confusion if they try the FEC mode with multiple source SSRCs where it doesn't work.

Cheers 

Magnus Westerlund 

----------------------------------------------------------------------
Network Architecture & Protocols, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------