Re: [AVT] Payload format specifications for adoption as WG items
Roni Even <Even.roni@huawei.com> Wed, 28 April 2010 07:20 UTC
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A1BA3A69F7 for <avt@core3.amsl.com>; Wed, 28 Apr 2010 00:20:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.434
X-Spam-Level:
X-Spam-Status: No, score=0.434 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qil78IMPRC-U for <avt@core3.amsl.com>; Wed, 28 Apr 2010 00:20:35 -0700 (PDT)
Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 9E80F3A6AE2 for <avt@ietf.org>; Wed, 28 Apr 2010 00:19:57 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L1K001WSSB4DA@szxga02-in.huawei.com> for avt@ietf.org; Wed, 28 Apr 2010 15:18:41 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L1K00HITSB4S6@szxga02-in.huawei.com> for avt@ietf.org; Wed, 28 Apr 2010 15:18:40 +0800 (CST)
Received: from windows8d787f9 (bzq-109-64-33-192.red.bezeqint.net [109.64.33.192]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L1K003XKSAXUC@szxml02-in.huawei.com>; Wed, 28 Apr 2010 15:18:40 +0800 (CST)
Date: Wed, 28 Apr 2010 10:17:34 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <EDC0A1AE77C57744B664A310A0B23AE211CCD8A2@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
To: avt@ietf.org
Message-id: <01a701cae6a2$e61b4e00$b251ea00$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset="us-ascii"
Content-language: en-us
Content-transfer-encoding: 7bit
Thread-index: AcrWdCKdh/I96+kCSHef8xkNufgvqgQLl//Q
References: <EDC0A1AE77C57744B664A310A0B23AE211CCD8A2@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Cc: "'DRAGE, Keith (Keith)'" <keith.drage@alcatel-lucent.com>
Subject: Re: [AVT] Payload format specifications for adoption as WG items
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Apr 2010 07:20:36 -0000
Hi, There were no objections to accept these payload specifications as WG items except for APTX where the authors do not want to progress this payload. I will send separate emails for each document to ask the authors to submit them as WG documents Thanks Roni Even AVT co-chair > -----Original Message----- > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of > DRAGE, Keith (Keith) > Sent: Wednesday, April 07, 2010 8:03 PM > To: avt@ietf.org > Subject: [AVT] Payload format specifications for adoption as WG items > > (As WG cochair) > > We have set a number of milestones for the completion of payload > formats, and for each of these we currently have one author draft. We > need drafts to become WG items to progress the payload formats. > > If people have issues with any of the drafts below where they would > like to see something substantially different (or indeed see nothing at > all), or it is currently premature to do this work, then they should > answer "no" to the appropriate question. If we get any "no"s at this > point, we can afford to take another round of discussion on those > specific drafts, before a further call for adoption (it would be useful > if you give the reason for saying no). To answer "yes" the drafts don't > have to be perfect, but you believe they are heading in the right > direction, and normal WG list discussion can take care of the issues. > > This is therefore a formal call for the adoption of drafts as WG items > against specific WG milestones. > > Please respond either to the list (avt@ietf.org), or directly to the > AVT chairs (avt-chairs@tools.ietf.org) by close of business Wednesday > 21st April (i.e. two weeks time). > > > Decision A > ---------- > > Milestone: RTP Payload Format for the iSAC codec for Proposed Standard > > Question: Do you think the latest version of > https://datatracker.ietf.org/doc/draft-legrand-rtp-isac/ provides an > appropriate basis for fulfilling this charter item and should be be > adopted as the working group text for this charter item. > > YES [ ] NO [ ] > > > Decision B > ---------- > > Milestone: RTP Payload Format for Bluetooth's SBC audio codec for > Proposed Standard > > Question: Do you think the latest version of > https://datatracker.ietf.org/doc/draft-hoene-avt-rtp-sbc/ provides an > appropriate basis for fulfilling this charter item and should be be > adopted as the working group text for this charter item. > > YES [ ] NO [ ] > > > Decision C > ---------- > > Milestone: RTP Payload Format for Enhanced Variable Rate Narrowband- > Wideband Codec (EVRC-NW) for Proposed Standard > > Question: Do you think the latest version of > https://datatracker.ietf.org/doc/draft-zfang-avt-rtp-evrc-nw/ provides > an appropriate basis for fulfilling this charter item and should be be > adopted as the working group text for this charter item. > > YES [ ] NO [ ] > > > Decision D > ---------- > > Milestone: RTP profile for the carriage of SMPTE 336M data for Proposed > Standard > > Question: Do you think the latest version of > https://datatracker.ietf.org/doc/draft-arbeiter-rtp-klv/ provides an > appropriate basis for fulfilling this charter item and should be be > adopted as the working group text for this charter item. > > YES [ ] NO [ ] > > > Decision E > ---------- > > Milestone: RTP Payload Format for the APTX codec for Proposed Standard > > Question: Do you think the latest version of > https://datatracker.ietf.org/doc/draft-trainor-avt-rtp-aptx/ provides > an appropriate basis for fulfilling this charter item and should be be > adopted as the working group text for this charter item. > > YES [ ] NO [ ] > > > Decision F > ---------- > > Milestone: RTP Payload Format for the CELT codec for Proposed Standard > > Question: Do you think the latest version of > https://datatracker.ietf.org/doc/draft-valin-celt-rtp-profile/ provides > an appropriate basis for fulfilling this charter item and should be be > adopted as the working group text for this charter item. > > YES [ ] NO [ ] > > Note: The above draft has expired but is available at the link given. > Parallel author draft exists in the codec group. > > > Decision G > ---------- > > Milestone: RTP Payload Format for MVC Video for Proposed Standard > > Question: Do you think the latest version of > https://datatracker.ietf.org/doc/draft-wang-avt-rtp-mvc/ provides an > appropriate basis for fulfilling this charter item and should be be > adopted as the working group text for this charter item. > > YES [ ] NO [ ] > > > > regards > > Keith > _______________________________________________ > Audio/Video Transport Working Group > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt
- [AVT] Payload format specifications for adoption … DRAGE, Keith (Keith)
- Re: [AVT] Payload format specifications for adopt… Roni Even
- Re: [AVT] Payload format specifications for adopt… DRAGE, Keith (Keith)
- Re: [AVT] Payload format specifications for adopt… Ye-Kui Wang
- Re: [AVT] Payload format specifications for adopt… Roni Even