Re: [AVT] Adoption of new milestones

"Van Caenegem, Tom (Tom)" <tom.van_caenegem@alcatel-lucent.com> Tue, 16 November 2010 11:01 UTC

Return-Path: <tom.van_caenegem@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 C61563A6DB9 for <avt@core3.amsl.com>; Tue, 16 Nov 2010 03:01:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.199
X-Spam-Level:
X-Spam-Status: No, score=-3.199 tagged_above=-999 required=5 tests=[AWL=-0.950, BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 3-Uw-4hU8B+g for <avt@core3.amsl.com>; Tue, 16 Nov 2010 03:01:59 -0800 (PST)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by core3.amsl.com (Postfix) with ESMTP id 976943A6DB7 for <avt@ietf.org>; Tue, 16 Nov 2010 03:01:58 -0800 (PST)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id oAGB2XhI004796 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <avt@ietf.org>; Tue, 16 Nov 2010 12:02:39 +0100
Received: from FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com ([135.120.45.43]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Tue, 16 Nov 2010 12:02:30 +0100
From: "Van Caenegem, Tom (Tom)" <tom.van_caenegem@alcatel-lucent.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, "avt@ietf.org" <avt@ietf.org>
Date: Tue, 16 Nov 2010 12:02:29 +0100
Thread-Topic: Adoption of new milestones
Thread-Index: AcuB+tHTdl113lt0S4mJWz/5TRVeTQDggMuw
Message-ID: <EC3FD58E75D43A4F8807FDE07491754616614468@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
References: <EDC0A1AE77C57744B664A310A0B23AE21E03AD3E@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE21E03AD3E@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Accept-Language: nl-NL, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: nl-NL, 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: Tue, 16 Nov 2010 11:01:59 -0000

Hi,

On the item: "RTCP indication for retransmission suppression as proposed standard"

As expressed in various emails I am not convinced there is need for such a new draft/mile stone, as RFC 4585 has addressed the problem IMO. The authors should first clarify what use cases are addressed that are not covered by RFC 4585, and linked to that, why a new RTCP message needs to be defined.  

(Note that the name is wrong: it is actually about feedback suppression, not retransmission suppression!!)

Tom


-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of DRAGE, Keith (Keith)
Sent: vrijdag 12 november 2010 0:48
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-level-exthdr/
https://datatracker.ietf.org/doc/draft-wu-avt-retransmission-supression-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