Re: [AVT] Adoption of new milestones

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Sat, 20 November 2010 21:18 UTC

Return-Path: <keith.drage@alcatel-lucent.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 7873D28C114 for <avt@core3.amsl.com>; Sat, 20 Nov 2010 13:18:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.778
X-Spam-Level:
X-Spam-Status: No, score=-103.778 tagged_above=-999 required=5 tests=[AWL=-1.529, BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
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 tVXlyGX5epYv for <avt@core3.amsl.com>; Sat, 20 Nov 2010 13:18:47 -0800 (PST)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by core3.amsl.com (Postfix) with ESMTP id 4064B28C10D for <avt@ietf.org>; Sat, 20 Nov 2010 13:18:46 -0800 (PST)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id oAKLJZgX006238 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <avt@ietf.org>; Sat, 20 Nov 2010 22:19:36 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Sat, 20 Nov 2010 22:19:35 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "avt@ietf.org" <avt@ietf.org>
Date: Sat, 20 Nov 2010 22:19:30 +0100
Thread-Topic: Adoption of new milestones
Thread-Index: AcuB+tHTdl113lt0S4mJWz/5TRVeTQACMmqgAbznqnA=
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE21E26DF4C@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <EDC0A1AE77C57744B664A310A0B23AE21E03AD3E@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <EDC0A1AE77C57744B664A310A0B23AE21E03AD3F@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE21E03AD3F@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.84
Subject: Re: [AVT] Adoption of new milestones
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: Sat, 20 Nov 2010 21:18:48 -0000

(As WG cochair)

For the question on adoption of milestones on:

-	RTP Header extension for mixer to client audio level indication as proposed standard
-	RTP Header extension for client to mixer audio level indication as proposed standard
-	RTCP indication for retransmission suppression as proposed standard
-	Guidelines for the use of Variable Bit Rate Audio with Secure RTP as informational (or possibly BCP)

In general the comments have been positive on adopting these and there was only one comment against "RTCP indication for retransmission suppression as proposed standard"

So we take this as consensus that the group is happy to work on these four deliverables.

What happens next:

1)	Roni and I will agree proposed dates next week and ask the AD to adopt the milestones.

If authors have not sent us a suggested milestone date and wish to do so, then that option is still open. In any case Roni and I will use our judgement based on the load on the working group in making a proposal.

2)	Various comments have been received as part of this process on the various related author drafts. Authors please feel free to update your documents prior to us asking to adopt drafts for these milestones. If you consider a comment requires further discussion, please feel free to open a specific thread on the avt list concentrating on that comment raised.

3)	If any AVT participant feels that an alternative proposal is worthwhile of consideration for these milestones, please feel free to submit your own author draft to cover any of these milestones.

4)	Once the milestones are set (probably in about two or so weeks), we will be looking to adopt baseline text / drafts as the working group draft to progress. So do try and complete 2) and 3) above in that timescale. If anyone believes more time is needed, then please send mail.

regards

Keith

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On 
> Behalf Of DRAGE, Keith (Keith)
> Sent: Friday, November 12, 2010 12:52 AM
> To: avt@ietf.org
> Subject: Re: [AVT] Adoption of new milestones
> 
> I neglected to put a deadline on this.
> 
> Please respond to the chairs by close of business on Friday 
> November 19th.
> 
> regards
> 
> Keith 
> 
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On 
> Behalf Of 
> > DRAGE, Keith (Keith)
> > Sent: Thursday, November 11, 2010 11:48 PM
> > To: avt@ietf.org
> > Subject: [AVT] Adoption of new milestones
> > 
> > (As AVT WG cochair)
> > 
> > We are looking to see if we should adopt a number of new 
> milestones in 
> > AVT. This is the adoption of the milestone, not the selection and 
> > adoption of an particular draft to fulfil that milestone 
> (that comes 
> > later).
> > 
> > There are four potential new milestones:
> > 
> > -	RTP Header extension for mixer to client audio level 
> > indication as proposed standard
> > -	RTP Header extension for client to mixer audio level 
> > indication as proposed standard
> > -	RTCP indication for retransmission suppression as 
> > proposed standard
> > -	Guidelines for the use of Variable Bit Rate Audio with 
> > Secure RTP as informational (or possibly BCP)
> > 
> > We took a brief show of hands in the meeting room in Beijing to see 
> > that there was a community that would support the work, and 
> to see if 
> > others thought that these either should not be performed or 
> interfered 
> > with the existing workload. So if you wish to add your opinion to 
> > these please:
> > 
> > For each of the above proposals indicate to the chairs at 
> > avt-chairs@tools.ietf.org (or to the list if you wish) if:
> > 
> > A)	you are prepared to support the work in AVT by reviews, 
> > comments proposed text or other appropriate means.
> > 
> > B)	you believe creation of this milestone is either 
> > inappropriate or will have a detrimental impact on 
> resources available 
> > to other work in AVT.
> > 
> > If you already represented your view in the meeting room in Beijing 
> > (or by Jabber), or do not wish to indicate eother A) or B), 
> you do not 
> > need to respond.
> > 
> > There are candidate author drafts for all of these 
> milestones if you 
> > wish to review the potential work.
> > 
> > https://datatracker.ietf.org/doc/draft-ivov-avt-slic/
> > https://datatracker.ietf.org/doc/draft-lennox-avt-rtp-audio-le
> > vel-exthdr/
> > https://datatracker.ietf.org/doc/draft-wu-avt-retransmission-s
> > upression-rtp/
> > https://datatracker.ietf.org/doc/draft-perkins-avt-srtp-vbr-audio/
> > 
> > regards
> > 
> > Keith
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
> > 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>