Re: [payload] WGLC on draft-ietf-avt-rtp-evrc-nw-03
Roni Even <Even.roni@huawei.com> Wed, 05 October 2011 05:31 UTC
Return-Path: <Even.roni@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 D1A3721F8B46 for <payload@ietfa.amsl.com>; Tue, 4 Oct 2011 22:31:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.32
X-Spam-Level:
X-Spam-Status: No, score=-106.32 tagged_above=-999 required=5 tests=[AWL=0.278, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GASS3DGsPfop for <payload@ietfa.amsl.com>; Tue, 4 Oct 2011 22:31:43 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 1A0E621F8B44 for <payload@ietf.org>; Tue, 4 Oct 2011 22:31:43 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSK00IFDVHZWS@szxga05-in.huawei.com> for payload@ietf.org; Wed, 05 Oct 2011 13:34:47 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSK003JXVHYN9@szxga05-in.huawei.com> for payload@ietf.org; Wed, 05 Oct 2011 13:34:47 +0800 (CST)
Received: from windows8d787f9 (bzq-109-64-200-234.red.bezeqint.net [109.64.200.234]) by szxml11-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LSK00IXTVHSDS@szxml11-in.huawei.com>; Wed, 05 Oct 2011 13:34:46 +0800 (CST)
Date: Wed, 05 Oct 2011 07:31:59 +0200
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <E23CE350F3C94C4A834B4E7069CA5679161C8C@nasanexd01a.na.qualcomm.com>
To: "'Fang, Zheng'" <zfang@qualcomm.com>, payload@ietf.org
Message-id: <044a01cc8320$1d50d2d0$57f27870$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_MSkx+euCmSZWs6dE0G8IHQ)"
Content-language: en-us
Thread-index: AcxdnNfq/+ON2T4BTFKgzifiLMZLbwIopyFwBvqrU4AAILpqQAAPxDrgAAzxWYA=
References: <008801cc5d9c$dd1eb400$975c1c00$%roni@huawei.com> <02b501cc663f$a40278e0$ec076aa0$%roni@huawei.com> <E23CE350F3C94C4A834B4E7069CA567915FD1D@nasanexd01a.na.qualcomm.com> <037101cc82ae$043c8fe0$0cb5afa0$%roni@huawei.com> <E23CE350F3C94C4A834B4E7069CA5679161C8C@nasanexd01a.na.qualcomm.com>
Subject: Re: [payload] WGLC on draft-ietf-avt-rtp-evrc-nw-03
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 05 Oct 2011 05:31:46 -0000
Hi Zheng, OK Regards Roni From: Fang, Zheng [mailto:zfang@qualcomm.com] Sent: Wednesday, October 05, 2011 1:40 AM To: Roni Even; payload@ietf.org Cc: Fang, Zheng Subject: RE: [payload] WGLC on draft-ietf-avt-rtp-evrc-nw-03 Roni, Thanks for the follow-up comments. I will modify the change controller to be the Payload working group. For the last question, regarding declarative use of SDP parameters (copied in below): 1. In section 13 how is "mode-set-recv" used in declarative SDP since it is a decoder capability and not an encoder one. [Zheng] In some two-way conversation scenarios, the traffics can be asymmetric, i.e, incoming and outgoing streams use different sets of modes. It is sufficient to declare decoder capability and the encoder at the other side simply follows. [roni] Declarative is a one way announcement like in SAP for streaming media, so there is no encoder at the other side. I propose to add the following text to Section 13 "Declarative SDP Considerations": o The usage of unidirectional receive only parameters, such as 'mode-set-recv', should be excluded in any declarations, since these parameters are meaningless in one-way streaming applications. Any comments would be appreciated. Thanks, Zheng From: Roni Even [mailto:Even.roni@huawei.com] Sent: Tuesday, October 04, 2011 8:55 AM To: Fang, Zheng; payload@ietf.org Cc: Wang, Min; Sinder, Dan; Huang, Pengjun (Jeff); Kandhadai, Ananthapadmanabhan (Ananth) Subject: RE: [payload] WGLC on draft-ietf-avt-rtp-evrc-nw-03 Hi Zheng, See inline Roni From: Fang, Zheng [mailto:zfang@qualcomm.com] Sent: Tuesday, October 04, 2011 2:44 AM To: Roni Even; payload@ietf.org Cc: Wang, Min; Sinder, Dan; Huang, Pengjun (Jeff); Kandhadai, Ananthapadmanabhan (Ananth); Fang, Zheng Subject: RE: [payload] WGLC on draft-ietf-avt-rtp-evrc-nw-03 Hi Roni, Thank you for your comments and suggestions. I updated the draft based on your suggestions. Please find attached the modified text and diff. I am not sure how to address some of the comments. My answers to those questions are in line. I would appreciate it if you could further comment on it. I will submit a new version once I resolve all the comments. Thanks! Zheng From: Roni Even [mailto:Even.roni@huawei.com] Sent: Monday, August 29, 2011 4:35 AM To: payload@ietf.org Cc: Fang, Zheng Subject: RE: [payload] WGLC on draft-ietf-avt-rtp-evrc-nw-03 Hi, I reviewed the draft and have some comments. 2. It looks to me that this draft updates RFC3558 similar to RFC 4788 and RFC 5188. It should be referenced in the header and in the text [Zheng] Although the payload definition of EVRCNW is similar to EVRCWB (RFC 5188), EVRCB (RFC 4788) and EVRC (RFC 3558), the current draft only defines the payload format for EVRCNW only. This is different than that of RFC 5188, which not only defines a new MIME type (EVRC-WB) but also update an existing MIME type (EVRC-B in RFC 4788). [roni] OK 3. In section 6 first paragraph why not reference 3788 where ToC is defined. [Zheng] Reference is added. 4. In second 9 in the registration template you have sendmode deprecated. This is strange since this registration is a new registration so there is nothing to deprecate . If you want to state that this optional parameter that is used in other EVRC modes is not used, please do it in another section and not in the registration section. [Zheng] The sendmode descriptions are removed from the registration templates. Instead a comment on it is added in Section 10 "SDP mode attributes for EVRC-NW". 5. In section 9 in the published specification you mention RFC3558 without a reference. I think that this document need also to be specified since it defines the RTP header and the usage. [Zheng] References are added. 6. In section 9 in the author field add your email address [Zheng] Done. 7. In section 9 change controller should be " IETF Audio/Video Transport working group delegated from the IESG." [Zheng] I am a little confused. The changed controller was indeed the same as you mentioned. Can you please point it out in case I miss anything? [roni} my mistake should be "IETF Payload working group delegated from the IESG" 8. In section 13 how is "mode-set-recv" used in declarative SDP since it is a decoder capability and not an encoder one. [Zheng] In some two-way conversation scenarios, the traffics can be asymmetric, i.e, incoming and outgoing streams use different sets of modes. It is sufficient to declare decoder capability and the encoder at the other side simply follows. [roni] Declarative is a one way announcement like in SAP for streaming media, so there is no encoder at the other side. Thanks Roni Even From: payload-bounces@ietf.org [mailto:payload-bounces@ietf.org] On Behalf Of Roni Even Sent: Thursday, August 18, 2011 2:49 PM To: payload@ietf.org Subject: [payload] WGLC on draft-ietf-avt-rtp-evrc-nw-03 Hi, I would like to start a Working Group Last Call on draft-ietf-avt-rtp-evrc-nw-03 <http://tools.ietf.org/html/draft-ietf-avt-rtp-evrc-nw-03> , RTP payload format for Enhanced Variable Rate Narrowband-Wideband Codec (EVRC-NW) The WGLC will end on September 9, 2011 Please review the draft and send comments to the list. Roni Even Payload co-chair
- [payload] WGLC on draft-ietf-avt-rtp-evrc-nw-03 Roni Even
- Re: [payload] WGLC on draft-ietf-avt-rtp-evrc-nw-… Roni Even
- Re: [payload] WGLC on draft-ietf-avt-rtp-evrc-nw-… Roni Even
- Re: [payload] WGLC on draft-ietf-avt-rtp-evrc-nw-… Fang, Zheng
- Re: [payload] WGLC on draft-ietf-avt-rtp-evrc-nw-… Roni Even
- Re: [payload] WGLC on draft-ietf-avt-rtp-evrc-nw-… Fang, Zheng
- Re: [payload] WGLC on draft-ietf-avt-rtp-evrc-nw-… Roni Even