
From wwwrun@core3.amsl.com  Tue Jan 25 15:22:59 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: avtext@ietf.org
Delivered-To: avtext@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id F22583A68EE; Tue, 25 Jan 2011 15:22:58 -0800 (PST)
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Cc: keith.drage@alcatel-lucent.com, magnus.westerlund@ericsson.com, avtext@ietf.org
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110125232258.F22583A68EE@core3.amsl.com>
Date: Tue, 25 Jan 2011 15:22:58 -0800 (PST)
Subject: [avtext] WG Action: Audio/Video Transport Extensions (AVTEXT)
X-BeenThere: avtext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Extensions working group discussion list <avtext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avtext>, <mailto:avtext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avtext>
List-Post: <mailto:avtext@ietf.org>
List-Help: <mailto:avtext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avtext>, <mailto:avtext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jan 2011 23:22:59 -0000

A new IETF working group has been formed in the Real-time Applications and
Infrastructure Area.  For additional information, please contact the Area
Directors or the WG Chairs.

Audio/Video Transport Extensions (AVTEXT)
---------------------------------------------------
Current Status: Active Working Group

Chairs:
  * Keith Drage <keith.drage@alcatel-lucent.com>
  * Magnus Westerlund <magnus.westerlund@ericsson.com>

Real-time Applications and Infrastructure Area Director(s):
  * Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
  * Robert Sparks <rjsparks@nostrum.com>

Real-time Applications and Infrastructure Area Advisor:
  * Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>

Mailing Lists:
  General Discussion: avtext@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/avtext
  Archive: http://www.ietf.org/mail-archive/web/avtext/index.html

Description of Working Group:

The Full-Standard Real-time Transport Protocol, RTP [RFC 3550], along
with its associated profiles and payload formats provides for real-
time transmission of audio and video over unicast and multicast
transports. RTP is widely implemented, and deployed for a wide range
of applications, ranging from telephony to television over IP. As new
applications have emerged, the need for guidelines for the use of the
RTP/RTCP protocols and extensions specific to those applications
has been identified.

The AVTEXT working group is charted to develop application-specific
guidelines for the use of RTP/RTCP protocols with the AVP, SAVP,
AVPF, and SAVPF profiles, and extensions to those protocols that are
driven by application-specific needs. Proposals for extensions with
general applicability to many different RTP/RTCP usages should be
taken to the AVTCORE working group.

The AVTEXT working group is constrained to use the protocol extension
mechanisms defined in the core protocols (such as RTP Header
extensions [RFC5285], AVPF Feedback Messages [RFC4585], and
SDES Items [RFC3550]). If new ways to extend the core protocols are
needed, they will be developed in the AVTCORE working group.

In addition to the milestones called out below, the AVTEXT working
group's initial tasks will include completing any new work identified
during IESG evaluation for the Rapid Acquisition of Multicast RTP
Sessions.

Goals and Milestones:

Jun 2011  Submit Considerations for RAMS Scenarios for Informational
Oct 2011  Submit RTP Header extension for mixer to client audio level 
          indication as Proposed Standard
Oct 2011  Submit RTP Header extension for client to mixer audio level 
          indication as proposed standard
Dec 2011  Submit Support for multiple clock rates in an RTP session for 
          Proposed Standard
Dec 2011  Submit SRTP Store-and-Forward Use Cases and Requirements for 
          Informational
Dec 2011  Submit Use of the Secure Real-time Transport Protocol (SRTP) 
          in Store-and-Forward Applications for Proposed Standard

From keith.drage@alcatel-lucent.com  Thu Jan 27 06:53:28 2011
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: avtext@core3.amsl.com
Delivered-To: avtext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2383B3A68C6; Thu, 27 Jan 2011 06:53:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.626
X-Spam-Level: 
X-Spam-Status: No, score=-105.626 tagged_above=-999 required=5 tests=[AWL=0.623, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, 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 lbsBjI06fSZT; Thu, 27 Jan 2011 06:53:27 -0800 (PST)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by core3.amsl.com (Postfix) with ESMTP id 0FCF53A68C0; Thu, 27 Jan 2011 06:53:23 -0800 (PST)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p0REu3xa031355 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 27 Jan 2011 15:56:26 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Thu, 27 Jan 2011 15:56:21 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: IETF AVT WG <avt@ietf.org>, "avtext@ietf.org" <avtext@ietf.org>
Date: Thu, 27 Jan 2011 15:56:19 +0100
Thread-Topic: Call for adoption of text for audio level milestones
Thread-Index: Acu+MlsFvM0YX6CeQySkhDVDbOUeWQ==
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE21E70B57A@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.83
Subject: [avtext] Call for adoption of text for audio level milestones
X-BeenThere: avtext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Extensions working group discussion list <avtext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avtext>, <mailto:avtext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avtext>
List-Post: <mailto:avtext@ietf.org>
List-Help: <mailto:avtext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avtext>, <mailto:avtext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jan 2011 14:53:28 -0000

(As AVTEXT WG cochair)

This message is copied to the AVTCORE list for those who are not yet on the=
 new list.

AVTEXT has two milestones relating to audio levels.

Oct 2011  Submit RTP Header extension for mixer to client audio level indic=
ation as Proposed Standard=20
=20
Oct 2011  Submit RTP Header extension for client to mixer audio level indic=
ation as proposed standard =20

We have the following author drafts providing candidate text for these mile=
stones:

A Real-Time Transport Protocol (RTP) Extension Header for Mixer-to-client A=
udio Level Indication
http://www.ietf.org/id/draft-ivov-avt-slic-04.txt

A Real-Time Transport Protocol (RTP) Header Extension for Client-to-Mixer A=
udio Level Indication
http://tools.ietf.org/id/draft-lennox-avt-rtp-audio-level-exthdr-02.txt

respectively.

This is a WG consensus call to adopt the above text as baseline text for th=
ese milestones. At this stage the text does not have to be regarded perfect=
, the question is more "Does this text form a better basis for completing t=
he work in the working group that some text yet to be submitted?"

While the prime intention of this call is to adopt the entire text of the a=
uthor draft, if you consider that some of the text is appropriate, but that=
 some of the text does not form a reasonable start for the work, then pleas=
e indicate that text and we will make a separate call on it (and adopt the =
rest).

Please respond by Thursday 10th February 2011 with your positions.=20

######### Please respond to the AVTEXT list only #############

Regards

Keith


From peter.musgrave@magorcorp.com  Thu Jan 27 06:58:33 2011
Return-Path: <peter.musgrave@magorcorp.com>
X-Original-To: avtext@core3.amsl.com
Delivered-To: avtext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 510403A68C0; Thu, 27 Jan 2011 06:58:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.435
X-Spam-Level: 
X-Spam-Status: No, score=-103.435 tagged_above=-999 required=5 tests=[AWL=0.164, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 PvGC441-ukIH; Thu, 27 Jan 2011 06:58:31 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id BB4973A68B0; Thu, 27 Jan 2011 06:58:31 -0800 (PST)
Received: by iyi42 with SMTP id 42so1709405iyi.31 for <multiple recipients>; Thu, 27 Jan 2011 07:01:35 -0800 (PST)
Received: by 10.231.35.201 with SMTP id q9mr1037756ibd.185.1296140493815; Thu, 27 Jan 2011 07:01:33 -0800 (PST)
Received: from petermac.magor.local ([72.1.217.106]) by mx.google.com with ESMTPS id z4sm13929511ibg.19.2011.01.27.07.01.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 27 Jan 2011 07:01:28 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Peter Musgrave <peter.musgrave@magorcorp.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE21E70B57A@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Date: Thu, 27 Jan 2011 10:00:59 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <1C6EB1CB-3A15-4A74-9FDE-47EF194454D7@magorcorp.com>
References: <EDC0A1AE77C57744B664A310A0B23AE21E70B57A@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1082)
Cc: "avtext@ietf.org" <avtext@ietf.org>, IETF AVT WG <avt@ietf.org>
Subject: Re: [avtext] Call for adoption of text for audio level milestones
X-BeenThere: avtext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Extensions working group discussion list <avtext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avtext>, <mailto:avtext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avtext>
List-Post: <mailto:avtext@ietf.org>
List-Help: <mailto:avtext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avtext>, <mailto:avtext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jan 2011 14:58:33 -0000

This text is a good starting point.=20

Peter

On 2011-01-27, at 9:56 AM, DRAGE, Keith (Keith) wrote:

> (As AVTEXT WG cochair)
>=20
> This message is copied to the AVTCORE list for those who are not yet =
on the new list.
>=20
> AVTEXT has two milestones relating to audio levels.
>=20
> Oct 2011  Submit RTP Header extension for mixer to client audio level =
indication as Proposed Standard=20
>=20
> Oct 2011  Submit RTP Header extension for client to mixer audio level =
indication as proposed standard =20
>=20
> We have the following author drafts providing candidate text for these =
milestones:
>=20
> A Real-Time Transport Protocol (RTP) Extension Header for =
Mixer-to-client Audio Level Indication
> http://www.ietf.org/id/draft-ivov-avt-slic-04.txt
>=20
> A Real-Time Transport Protocol (RTP) Header Extension for =
Client-to-Mixer Audio Level Indication
> =
http://tools.ietf.org/id/draft-lennox-avt-rtp-audio-level-exthdr-02.txt
>=20
> respectively.
>=20
> This is a WG consensus call to adopt the above text as baseline text =
for these milestones. At this stage the text does not have to be =
regarded perfect, the question is more "Does this text form a better =
basis for completing the work in the working group that some text yet to =
be submitted?"
>=20
> While the prime intention of this call is to adopt the entire text of =
the author draft, if you consider that some of the text is appropriate, =
but that some of the text does not form a reasonable start for the work, =
then please indicate that text and we will make a separate call on it =
(and adopt the rest).
>=20
> Please respond by Thursday 10th February 2011 with your positions.=20
>=20
> ######### Please respond to the AVTEXT list only #############
>=20
> Regards
>=20
> Keith
>=20
> _______________________________________________
> avtext mailing list
> avtext@ietf.org
> https://www.ietf.org/mailman/listinfo/avtext


From ray.vanbrandenburg@tno.nl  Fri Jan 28 03:00:14 2011
Return-Path: <ray.vanbrandenburg@tno.nl>
X-Original-To: avtext@core3.amsl.com
Delivered-To: avtext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 177C03A6784; Fri, 28 Jan 2011 03:00:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.244
X-Spam-Level: 
X-Spam-Status: No, score=-0.244 tagged_above=-999 required=5 tests=[AWL=0.260,  BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
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 g+PQvl-CW2wO; Fri, 28 Jan 2011 03:00:13 -0800 (PST)
Received: from mailoutb.tno.nl (mailoutb.tno.nl [134.221.1.17]) by core3.amsl.com (Postfix) with ESMTP id 850BC3A635F; Fri, 28 Jan 2011 03:00:09 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.60,391,1291590000"; d="scan'208";a="11302653"
Received: from unknown (HELO mail.tno.nl) ([134.221.225.220]) by mailhost1b.tno.nl with ESMTP; 28 Jan 2011 12:03:14 +0100
Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.220]) by EXC-CASHUB01.tsn.tno.nl ([134.221.225.220]) with mapi id 14.01.0270.001; Fri, 28 Jan 2011 12:03:14 +0100
From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Thread-Topic: [avtext] Call for adoption of text for audio level milestones
Thread-Index: Acu+MlsFvM0YX6CeQySkhDVDbOUeWf//8ImA//6fc+A=
Date: Fri, 28 Jan 2011 11:03:14 +0000
Message-ID: <FCC100FC8D6B034CB88CD8173B2DA1585B5846@EXC-MBX03.tsn.tno.nl>
References: <EDC0A1AE77C57744B664A310A0B23AE21E70B57A@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <1C6EB1CB-3A15-4A74-9FDE-47EF194454D7@magorcorp.com>
In-Reply-To: <1C6EB1CB-3A15-4A74-9FDE-47EF194454D7@magorcorp.com>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [134.221.225.191]
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: "avtext@ietf.org" <avtext@ietf.org>, IETF AVT WG <avt@ietf.org>
Subject: Re: [avtext] Call for adoption of text for audio level milestones
X-BeenThere: avtext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Extensions working group discussion list <avtext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avtext>, <mailto:avtext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avtext>
List-Post: <mailto:avtext@ietf.org>
List-Help: <mailto:avtext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avtext>, <mailto:avtext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jan 2011 11:00:14 -0000

I agree.=20

Ray van Brandenburg=20

-----Original Message-----
From: avtext-bounces@ietf.org [mailto:avtext-bounces@ietf.org] On Behalf Of=
 Peter Musgrave
Sent: donderdag 27 januari 2011 16:01
To: DRAGE, Keith (Keith)
Cc: avtext@ietf.org; IETF AVT WG
Subject: Re: [avtext] Call for adoption of text for audio level milestones

This text is a good starting point.=20

Peter

On 2011-01-27, at 9:56 AM, DRAGE, Keith (Keith) wrote:

> (As AVTEXT WG cochair)
>=20
> This message is copied to the AVTCORE list for those who are not yet on t=
he new list.
>=20
> AVTEXT has two milestones relating to audio levels.
>=20
> Oct 2011  Submit RTP Header extension for mixer to client audio level=20
> indication as Proposed Standard
>=20
> Oct 2011  Submit RTP Header extension for client to mixer audio level=20
> indication as proposed standard
>=20
> We have the following author drafts providing candidate text for these mi=
lestones:
>=20
> A Real-Time Transport Protocol (RTP) Extension Header for=20
> Mixer-to-client Audio Level Indication=20
> http://www.ietf.org/id/draft-ivov-avt-slic-04.txt
>=20
> A Real-Time Transport Protocol (RTP) Header Extension for=20
> Client-to-Mixer Audio Level Indication=20
> http://tools.ietf.org/id/draft-lennox-avt-rtp-audio-level-exthdr-02.tx
> t
>=20
> respectively.
>=20
> This is a WG consensus call to adopt the above text as baseline text for =
these milestones. At this stage the text does not have to be regarded perfe=
ct, the question is more "Does this text form a better basis for completing=
 the work in the working group that some text yet to be submitted?"
>=20
> While the prime intention of this call is to adopt the entire text of the=
 author draft, if you consider that some of the text is appropriate, but th=
at some of the text does not form a reasonable start for the work, then ple=
ase indicate that text and we will make a separate call on it (and adopt th=
e rest).
>=20
> Please respond by Thursday 10th February 2011 with your positions.=20
>=20
> ######### Please respond to the AVTEXT list only #############
>=20
> Regards
>=20
> Keith
>=20
> _______________________________________________
> avtext mailing list
> avtext@ietf.org
> https://www.ietf.org/mailman/listinfo/avtext

_______________________________________________
avtext mailing list
avtext@ietf.org
https://www.ietf.org/mailman/listinfo/avtext
This e-mail and its contents are subject to the DISCLAIMER at http://www.tn=
o.nl/disclaimer/email.html


From Even.roni@huawei.com  Sun Jan 30 02:22:44 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: avtext@core3.amsl.com
Delivered-To: avtext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3E39C3A6940; Sun, 30 Jan 2011 02:22:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.475
X-Spam-Level: 
X-Spam-Status: No, score=-103.475 tagged_above=-999 required=5 tests=[AWL=1.020, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1, 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 waBF+3bjmY+f; Sun, 30 Jan 2011 02:22:43 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id E99773A692E; Sun, 30 Jan 2011 02:22:42 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LFT00GKXZMVCJ@szxga03-in.huawei.com>; Sun, 30 Jan 2011 18:25:43 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LFT00ERTZMVVX@szxga03-in.huawei.com>; Sun, 30 Jan 2011 18:25:43 +0800 (CST)
Received: from windows8d787f9 ([109.64.31.233]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LFT00JDFZMOWC@szxml02-in.huawei.com>; Sun, 30 Jan 2011 18:25:43 +0800 (CST)
Date: Sun, 30 Jan 2011 12:21:20 +0200
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <1C6EB1CB-3A15-4A74-9FDE-47EF194454D7@magorcorp.com>
To: 'Peter Musgrave' <peter.musgrave@magorcorp.com>, "'DRAGE, Keith (Keith)'" <keith.drage@alcatel-lucent.com>
Message-id: <097201cbc067$74afbdb0$5e0f3910$%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: Acu+MxtApWZmcHkvRnO/moF7XHF/HACNE1NQ
References: <EDC0A1AE77C57744B664A310A0B23AE21E70B57A@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <1C6EB1CB-3A15-4A74-9FDE-47EF194454D7@magorcorp.com>
Cc: avtext@ietf.org, 'IETF AVT WG' <avt@ietf.org>
Subject: Re: [avtext] Call for adoption of text for audio level milestones
X-BeenThere: avtext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Extensions working group discussion list <avtext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avtext>, <mailto:avtext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avtext>
List-Post: <mailto:avtext@ietf.org>
List-Help: <mailto:avtext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avtext>, <mailto:avtext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jan 2011 10:22:44 -0000

I agree
Roni Even

> -----Original Message-----
> From: avtext-bounces@ietf.org [mailto:avtext-bounces@ietf.org] On
> Behalf Of Peter Musgrave
> Sent: Thursday, January 27, 2011 5:01 PM
> To: DRAGE, Keith (Keith)
> Cc: avtext@ietf.org; IETF AVT WG
> Subject: Re: [avtext] Call for adoption of text for audio level
> milestones
> 
> This text is a good starting point.
> 
> Peter
> 
> On 2011-01-27, at 9:56 AM, DRAGE, Keith (Keith) wrote:
> 
> > (As AVTEXT WG cochair)
> >
> > This message is copied to the AVTCORE list for those who are not yet
> on the new list.
> >
> > AVTEXT has two milestones relating to audio levels.
> >
> > Oct 2011  Submit RTP Header extension for mixer to client audio level
> indication as Proposed Standard
> >
> > Oct 2011  Submit RTP Header extension for client to mixer audio level
> indication as proposed standard
> >
> > We have the following author drafts providing candidate text for
> these milestones:
> >
> > A Real-Time Transport Protocol (RTP) Extension Header for Mixer-to-
> client Audio Level Indication
> > http://www.ietf.org/id/draft-ivov-avt-slic-04.txt
> >
> > A Real-Time Transport Protocol (RTP) Header Extension for Client-to-
> Mixer Audio Level Indication
> > http://tools.ietf.org/id/draft-lennox-avt-rtp-audio-level-exthdr-
> 02.txt
> >
> > respectively.
> >
> > This is a WG consensus call to adopt the above text as baseline text
> for these milestones. At this stage the text does not have to be
> regarded perfect, the question is more "Does this text form a better
> basis for completing the work in the working group that some text yet
> to be submitted?"
> >
> > While the prime intention of this call is to adopt the entire text of
> the author draft, if you consider that some of the text is appropriate,
> but that some of the text does not form a reasonable start for the
> work, then please indicate that text and we will make a separate call
> on it (and adopt the rest).
> >
> > Please respond by Thursday 10th February 2011 with your positions.
> >
> > ######### Please respond to the AVTEXT list only #############
> >
> > Regards
> >
> > Keith
> >
> > _______________________________________________
> > avtext mailing list
> > avtext@ietf.org
> > https://www.ietf.org/mailman/listinfo/avtext
> 
> _______________________________________________
> avtext mailing list
> avtext@ietf.org
> https://www.ietf.org/mailman/listinfo/avtext

