
From avt-bounces@ietf.org  Sun Feb  1 15:42:23 2009
Return-Path: <avt-bounces@ietf.org>
X-Original-To: avt-archive@optimus.ietf.org
Delivered-To: ietfarch-avt-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9855228C1B8; Sun,  1 Feb 2009 15:42:23 -0800 (PST)
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 57FBE28C1B8 for <avt@core3.amsl.com>; Sun,  1 Feb 2009 15:42:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.199
X-Spam-Level: 
X-Spam-Status: No, score=-6.199 tagged_above=-999 required=5 tests=[AWL=0.400,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 SvaFv7fSpQ-i for <avt@core3.amsl.com>; Sun,  1 Feb 2009 15:42:21 -0800 (PST)
Received: from mr1.dcs.gla.ac.uk (mr1.dcs.gla.ac.uk [130.209.249.184]) by core3.amsl.com (Postfix) with ESMTP id 83E4728C17A for <avt@ietf.org>; Sun,  1 Feb 2009 15:42:21 -0800 (PST)
Received: from starkperkins.demon.co.uk ([80.176.158.71]:49531 helo=[192.168.254.14]) by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42) id 1LTlwq-0001PX-OI; Sun, 01 Feb 2009 23:41:56 +0000
In-Reply-To: <49402F05.8000904@8x8.com>
References: <49402F05.8000904@8x8.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <2793A681-E15A-4EF6-80D0-A80AF6D10695@csperkins.org>
From: Colin Perkins <csp@csperkins.org>
Date: Sun, 1 Feb 2009 23:41:48 +0000
To: Eilon Yardeni <eyardeni@8x8.com>
X-Mailer: Apple Mail (2.753.1)
Cc: avt@ietf.org
Subject: Re: [AVT] Question on draft-perkins-avt-rapid-rtp-sync-00
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/pipermail/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org

On 10 Dec 2008, at 21:05, Eilon Yardeni wrote:
> The draft defines a new RTCP feedback message type RTCP-SR-REQ that  
> allows receivers to request RTCP SR from the media source in order  
> to synchronize the streams.
>
> This would allow receivers to send RTCP-SR-REQ as soon as they join  
> for fast synchronization; however, section 4 in the draft says that  
> "receivers using unicast feedback would not be allowed to send  
> immediate RTCP.". If SSM is used, receivers must use unicast  
> feedback (i.e. draft-ietf-avt-rtcpssm-17) for sending RTCP, so how  
> will they be able to send a fast RTCP-SR-REQ?

Using the RTP/AVPF profile. Immediate RTCP is not appropriate here,  
since you want to avoid implosion of messages to the feedback target.

-- 
Colin Perkins
http://csperkins.org/



_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt

From avt-bounces@ietf.org  Mon Feb  2 05:19:08 2009
Return-Path: <avt-bounces@ietf.org>
X-Original-To: avt-archive@ietf.org
Delivered-To: ietfarch-avt-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B046028C20D for <avt-archive@ietf.org>; Mon,  2 Feb 2009 05:19:08 -0800 (PST)
Subject: The results of your email commands
From: avt-bounces@ietf.org
To: avt-archive@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1302308065=="
Message-ID: <mailman.20144.1233580747.4915.avt@ietf.org>
Date: Mon, 02 Feb 2009 05:19:07 -0800
Precedence: bulk
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
X-List-Administrivia: yes
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org

--===============1302308065==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit

The results of your email command are provided below. Attached is your
original message.


- Unprocessed:
    It's the perfect time to get that dream watch you've fantasized about. But there's no need to empty your bank account while doing it!
    http://search.yahoo.com/search?y=Search&p=wallokay%2ecom&fr=sfp&ei=UTF-8
    The watch of your dreams doesn't have to be an overpriced piece of machinery. Nowadays you can get the same functionality and distinctive looks from the next best thing. Vi it Prest1ge R3ps and choose from hundreds of gorgeous models at less than ten percent the price of an original.
    http://search.yahoo.com/search?y=Search&p=wallokay%2ecom&fr=sfp&ei=UTF-8
    Chck out our extensive inventory and enjoy the fastest shipping available online! See you at Prest1ge R3ps!
    Sincerely,
    Mr Head

- Done.


--===============1302308065==
Content-Type: message/rfc822
MIME-Version: 1.0

Return-Path: <ademir@compubras.com.br>
X-Original-To: avt-request@core3.amsl.com
Delivered-To: avt-request@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3983828C1FC;
	Mon,  2 Feb 2009 05:19:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -39.486
X-Spam-Level: 
X-Spam-Status: No, score=-39.486 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, FH_RELAY_NODNS=1.451, GB_PRESTIGE=50,
	HELO_MISMATCH_NET=0.611, J_CHICKENPOX_12=0.6, J_CHICKENPOX_52=0.6,
	RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, 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 NYPE1PGh4wwR; Mon,  2 Feb 2009 05:19:03 -0800 (PST)
Received: from CUSTOMER.VPLS.NET (unknown [89.39.240.44])
	by core3.amsl.com (Postfix) with SMTP id 440C528C1FE;
	Mon,  2 Feb 2009 05:18:56 -0800 (PST)
X-Originating-IP: 136.238.66.16 by smtp.thejaywalker.com; Mon, 02 Feb 2009 06:12:34 -0700
Message-ID: <178O532.4092375avt-archive@ietf.org>
Date: Mon, 02 Feb 2009 08:18:34 -0500
From: "Staci Dixon" <avt-archive@ietf.org>
To: "Allie Head" <avt-archive@ietf.org>
Subject: Rep watches make great gifts
Content-Type: text/plain;
Content-Transfer-Encoding: 7bit

Dear Allie,

It's the perfect time to get that dream watch you've fantasized about. But there's no need to empty your bank account while doing it!
http://search.yahoo.com/search?y=Search&p=wallokay%2ecom&fr=sfp&ei=UTF-8

The watch of your dreams doesn't have to be an overpriced piece of machinery. Nowadays you can get the same functionality and distinctive looks from the next best thing. Vi it Prest1ge R3ps and choose from hundreds of gorgeous models at less than ten percent the price of an original.
http://search.yahoo.com/search?y=Search&p=wallokay%2ecom&fr=sfp&ei=UTF-8

Chck out our extensive inventory and enjoy the fastest shipping available online! See you at Prest1ge R3ps!

Sincerely,
Mr Head





--===============1302308065==--

From behave-bounces@ietf.org  Mon Feb  2 05:19:08 2009
Return-Path: <behave-bounces@ietf.org>
X-Original-To: avt-archive@ietf.org
Delivered-To: ietfarch-avt-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B3B2928C20F for <avt-archive@ietf.org>; Mon,  2 Feb 2009 05:19:08 -0800 (PST)
Subject: The results of your email commands
From: behave-bounces@ietf.org
To: avt-archive@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0767223590=="
Message-ID: <mailman.20145.1233580747.4915.behave@ietf.org>
Date: Mon, 02 Feb 2009 05:19:07 -0800
Precedence: bulk
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
X-List-Administrivia: yes
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

--===============0767223590==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit

The results of your email command are provided below. Attached is your
original message.


- Unprocessed:
    It's the perfect time to get that dream watch you've fantasized about. But there's no need to empty your bank account while doing it!
    http://search.yahoo.com/search?y=Search&p=wallokay%2ecom&fr=sfp&ei=UTF-8
    The watch of your dreams doesn't have to be an overpriced piece of machinery. Nowadays you can get the same functionality and distinctive looks from the next best thing. Vi it Prest1ge R3ps and choose from hundreds of gorgeous models at less than ten percent the price of an original.
    http://search.yahoo.com/search?y=Search&p=wallokay%2ecom&fr=sfp&ei=UTF-8
    Chck out our extensive inventory and enjoy the fastest shipping available online! See you at Prest1ge R3ps!
    Sincerely,
    Mr Head

- Done.


--===============0767223590==
Content-Type: message/rfc822
MIME-Version: 1.0

Return-Path: <ademir@compubras.com.br>
X-Original-To: behave-request@core3.amsl.com
Delivered-To: behave-request@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3983828C1FC;
	Mon,  2 Feb 2009 05:19:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -39.486
X-Spam-Level: 
X-Spam-Status: No, score=-39.486 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, FH_RELAY_NODNS=1.451, GB_PRESTIGE=50,
	HELO_MISMATCH_NET=0.611, J_CHICKENPOX_12=0.6, J_CHICKENPOX_52=0.6,
	RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, 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 NYPE1PGh4wwR; Mon,  2 Feb 2009 05:19:03 -0800 (PST)
Received: from CUSTOMER.VPLS.NET (unknown [89.39.240.44])
	by core3.amsl.com (Postfix) with SMTP id 440C528C1FE;
	Mon,  2 Feb 2009 05:18:56 -0800 (PST)
X-Originating-IP: 136.238.66.16 by smtp.thejaywalker.com; Mon, 02 Feb 2009 06:12:34 -0700
Message-ID: <178O532.4092375avt-archive@ietf.org>
Date: Mon, 02 Feb 2009 08:18:34 -0500
From: "Staci Dixon" <avt-archive@ietf.org>
To: "Allie Head" <avt-archive@ietf.org>
Subject: Rep watches make great gifts
Content-Type: text/plain;
Content-Transfer-Encoding: 7bit

Dear Allie,

It's the perfect time to get that dream watch you've fantasized about. But there's no need to empty your bank account while doing it!
http://search.yahoo.com/search?y=Search&p=wallokay%2ecom&fr=sfp&ei=UTF-8

The watch of your dreams doesn't have to be an overpriced piece of machinery. Nowadays you can get the same functionality and distinctive looks from the next best thing. Vi it Prest1ge R3ps and choose from hundreds of gorgeous models at less than ten percent the price of an original.
http://search.yahoo.com/search?y=Search&p=wallokay%2ecom&fr=sfp&ei=UTF-8

Chck out our extensive inventory and enjoy the fastest shipping available online! See you at Prest1ge R3ps!

Sincerely,
Mr Head





--===============0767223590==--

From avt-bounces@ietf.org  Mon Feb  2 09:46:00 2009
Return-Path: <avt-bounces@ietf.org>
X-Original-To: avt-archive@optimus.ietf.org
Delivered-To: ietfarch-avt-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C1D828C22F; Mon,  2 Feb 2009 09:46:00 -0800 (PST)
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 27C1D28C2E1 for <avt@core3.amsl.com>; Sun,  1 Feb 2009 05:09:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
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 NfKZdYWNxtDy for <avt@core3.amsl.com>; Sun,  1 Feb 2009 05:09:33 -0800 (PST)
Received: from offis3.offis.uni-oldenburg.de (offis3.OFFIS.Uni-Oldenburg.DE [134.106.52.239]) by core3.amsl.com (Postfix) with ESMTP id 62ED328E0F7 for <avt@ietf.org>; Sun,  1 Feb 2009 05:02:46 -0800 (PST)
Received: by offis3.offis.uni-oldenburg.de (Postfix, from userid 1003) id 43D483A8E; Sun,  1 Feb 2009 14:02:26 +0100 (CET)
X-Spam-hits: -1.8
X-Spam-DCC: debian: offis3 1169; Body=1 Fuz1=1 Fuz2=1 
Received: from smtpsec.offis.uni-oldenburg.de (serv1.offis.uni-oldenburg.de [134.106.52.238]) by offis3.offis.uni-oldenburg.de (Postfix) with ESMTP id E63F53A7A; Sun,  1 Feb 2009 14:02:21 +0100 (CET)
Received: from [192.168.2.39] (p5481C47E.dip.t-dialin.net [84.129.196.126]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtpsec.offis.uni-oldenburg.de (Postfix) with ESMTPSA id 80690274E0C; Sun,  1 Feb 2009 14:02:21 +0100 (CET)
Message-Id: <4F7D5D83-237D-41D3-A2EE-384BC2A6EFB1@informatik.uni-oldenburg.de>
From: Susanne Boll <susanne.boll@informatik.uni-oldenburg.de>
To: avt@ietf.org
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Sun, 1 Feb 2009 14:02:20 +0100
References: <79DE523B-5E37-41B0-B544-7E9BB90629BE@informatik.uni-oldenburg.de>
X-Mailer: Apple Mail (2.930.3)
X-Filtered-With: renattach 1.2.4
X-RenAttach-Info: mode=badlist action=rename count=0
X-Mailman-Approved-At: Mon, 02 Feb 2009 09:45:59 -0800
Subject: [AVT] =?windows-1252?q?Call_for_Submissions_=96_ACM_Multimedia_20?= =?windows-1252?q?09_-_Multimedia_networking=2C_sensor_networks=2C_and_sys?= =?windows-1252?q?tems_support_Track?=
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1906031531=="
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org

--===============1906031531==
Content-Type: multipart/alternative; boundary=Apple-Mail-14--364413298


--Apple-Mail-14--364413298
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit


Call for Submissions
17th INTERNATIONAL ACM CONFERENCE ON MULTIMEDIA 2009

Beijing Hotel, Beijing, China
October 19-24, 2009
  www.acmmm09.org
______________________________________________________

General Chairs

Wen Gao, Peking University, China
Yong Rui, Microsoft, China
Alan Hanjalic, Delft University of Technology, The Netherlands

cordially invite you to participate in this premier annual event on  
multimedia research, technology and art. The conference will have an  
excellent technical program, and will be surrounded by a multimedia  
art exhibition and a number of outstanding state-of-the-art tutorials  
and workshops. Special highlights will include an extended and  
carefully designed program of panel discussions, and the new concept  
of Multimedia Grand Challengethat we introduce in 2009 as a part of  
the conference prorgam.

The technical program will consist of the oral/poster sessions and  
invited talks with topics of interest in:
(a) Multimedia content analysis, processing, and retrieval
(b) Multimedia networking, sensor networks, and systems support
(c) Multimedia tools, end-systems, and applications
(d) Human-Centered Multimedia

Full papers are solicited to be presented in oral sessions, while  
short papers will be presented as posters in an interactive setting.

Important Dates for Full and Short Papers:

April 10, 2009              Full Paper Registration (Abstract  
Submission) Deadline
April 17, 2009              Full Paper Submission Deadline
May 8, 2009                 Short Paper Submission Deadline
July 3, 2009                 Notification of Acceptance
July 24, 2009               Camera-ready Submission Deadline

In addition to full and short papers, submissions are also solicited  
for the conference events listed below. The submission guidelines for  
each of the conference events can be found on http://www.acmmm09.org

Panels will consist of discussions on timely and controversial topics.

Tutorials will address the state-of-the-art developments regarding all  
aspects of multimedia, and will be of interest to the entire  
multimedia community, from novices in the world of multimedia to the  
most seasoned researchers, from people working in academia to industry  
professionals.

Workshops will address focused topics pertinent to the main conference  
that demand dedicated coverage due to their relevance to the current  
multimedia research and development.

Open Source Competition 2009 will be the sixth edition of this  
successful competition emphasizing the impact the ACM Multimedia  
conference aims to achieve on multimedia practice.

Brave New Topics track is a special sessions track containing papers  
extending the boundaries of multimedia research.

Technical Demos will show what is currently possible regarding all  
aspects of multimedia technology and its applications.

Video Program allows researchers and artists to demonstrate their  
tools, systems or applications without having to bring the equipment  
for a "live" demo.

Interactive Art Program will include long and short papers describing  
interactive multimedia art works, tools, applications, and technical  
approaches for creative uses of multimedia content and technology. It  
will also include an art exhibition.

NEW in 2009: Multimedia Grand Challenge is a set of challenges from  
various industry leaders, geared to engage the multimedia research  
community in solving relevant, interesting and challenging questions  
about the industry's 2-5 year horizon.

Doctoral Symposium is an opportunity for students involved in the  
preparation of a PhD to interactively discuss their research issues  
and ideas with senior researchers, and receive constructive feedback  
from members of the research community.







--Apple-Mail-14--364413298
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div> </div><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: =
0pt; margin-left: 0cm; "><span class=3D"Apple-style-span" =
style=3D"font-family: Arial; font-size: 13px; ">Call for =
Submissions</span></div><div style=3D"margin-top: 0cm; margin-right: =
0cm; margin-bottom: 0pt; margin-left: 0cm; "><span =
class=3D"Apple-style-span" style=3D"font-family: Arial; font-size: 13px; =
font-weight: bold; ">17th INTERNATIONAL ACM CONFERENCE ON MULTIMEDIA =
2009</span></div><p style=3D"margin-top: 0cm; margin-right: 0cm; =
margin-bottom: 0pt; margin-left: 0cm; "><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; "><font face=3D"Arial" =
size=3D"2"></font></span>&nbsp;</p><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0pt; margin-left: 0cm; "><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial; ">Beijing =
Hotel, Beijing, China</span></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0pt; margin-left: 0cm; "><span =
class=3D"Apple-style-span" style=3D"font-family: Arial; font-size: 13px; =
">October 19-24, 2009</span></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0pt; margin-left: 0cm; "><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial; "><font =
face=3D"Arial" size=3D"2"></font></span>&nbsp;<span =
class=3D"Apple-style-span" style=3D"font-family: Arial; font-size: 13px; =
"><a =
title=3D"https://webmail.ewi.tudelft.nl/exchweb/bin/redir.asp?URL=3Dhttp:/=
/www.acmmm09.org/ http://www.acmmm09.org/ outbind://25/www.acmmm09.org" =
href=3D"https://webmail.ewi.tudelft.nl/exchweb/bin/redir.asp?URL=3Dhttp://=
www.acmmm09.org/" target=3D"_blank">www.acmmm09.org</a></span></div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; =
margin-left: 0cm; "><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; =
">______________________________________________________</span></div><p =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; =
margin-left: 0cm; "><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; "><font face=3D"Arial" =
size=3D"2"></font></span>&nbsp;</p><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0pt; margin-left: 0cm; "><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial; ">General =
Chairs</span></div><p style=3D"margin-top: 0cm; margin-right: 0cm; =
margin-bottom: 0pt; margin-left: 0cm; "><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; "><font face=3D"Arial" =
size=3D"2"></font></span>&nbsp;</p><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0pt; margin-left: 0cm; "><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial; ">Wen Gao, =
Peking University, China</span></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0pt; margin-left: 0cm; "><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial; ">Yong Rui, =
Microsoft, China</span></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0pt; margin-left: 0cm; "><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial; ">Alan =
Hanjalic, Delft University of Technology, The Netherlands</span></div><p =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; =
margin-left: 0cm; "><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; "><font face=3D"Arial" =
size=3D"2"></font></span>&nbsp;</p><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0pt; margin-left: 0cm; "><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial; ">cordially =
invite you to participate in this premier annual event on multimedia =
research, technology and art. The conference will have an excellent =
technical program, and will be surrounded by a multimedia art exhibition =
and a number of outstanding state-of-the-art tutorials and workshops. =
Special highlights will include an extended and carefully designed =
program of panel discussions, and the&nbsp;<span =
class=3D"549120515-14012009">new&nbsp;</span>concept of Multimedia Grand =
Challenge<span class=3D"549120515-14012009">that we introduce in 2009 as =
a part of the conference prorgam</span>.</span></div><p =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; =
margin-left: 0cm; "><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; "><font face=3D"Arial" =
size=3D"2"></font></span>&nbsp;</p><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0pt; margin-left: 0cm; "><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial; ">The =
technical program will consist of the oral/poster sessions and invited =
talks with topics of interest in:</span></div><div style=3D"margin-top: =
0cm; margin-right: 6.25pt; margin-bottom: 0pt; margin-left: 0cm; =
text-indent: 5pt; text-align: justify; "><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; ">(a) Multimedia content =
analysis, processing, and retrieval</span></div><div style=3D"margin-top: =
0cm; margin-right: 6.25pt; margin-bottom: 0pt; margin-left: 0cm; =
text-indent: 5pt; text-align: justify; "><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; "><b>(b) Multimedia =
networking, sensor networks, and systems support</b></span></div><div =
style=3D"margin-top: 0cm; margin-right: 6.25pt; margin-bottom: 0pt; =
margin-left: 0cm; text-indent: 5pt; text-align: justify; "><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial; ">(c) =
Multimedia tools, end-systems, and applications</span></div><div =
style=3D"margin-top: 0cm; margin-right: 6.25pt; margin-bottom: 0pt; =
margin-left: 0cm; text-indent: 5pt; text-align: justify; "><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial; ">(d) =
Human-Centered Multimedia</span></div><div style=3D"margin-top: 0cm; =
margin-right: 6.25pt; margin-bottom: 0pt; margin-left: 0cm; text-align: =
justify; "><b><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; "><font face=3D"Arial" =
size=3D"2"></font></span></b>&nbsp;</div><div style=3D"margin-top: 0cm; =
margin-right: 6.25pt; margin-bottom: 0pt; margin-left: 0cm; text-align: =
justify; "><b><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; ">Full papers</span></b><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; ">&nbsp;are solicited to =
be presented in oral sessions, while&nbsp;<b>short papers</b>&nbsp;will =
be presented as posters in an interactive setting.</span></div><div =
style=3D"margin-top: 0cm; margin-right: 33.25pt; margin-bottom: 0pt; =
margin-left: 0cm; text-align: justify; "><b><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; "><font face=3D"Arial" =
size=3D"2"></font></span></b>&nbsp;</div><div style=3D"margin-top: 0cm; =
margin-right: 33.25pt; margin-bottom: 0pt; margin-left: 0cm; text-align: =
justify; "><b><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; ">Important Dates for Full and Short =
Papers:</span></b></div><div style=3D"margin-top: 0cm; margin-right: =
33.25pt; margin-bottom: 0pt; margin-left: 0cm; text-align: justify; =
"><b><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial; =
"><font face=3D"Arial" size=3D"2"></font></span></b>&nbsp;</div><div =
style=3D"margin-top: 0cm; margin-right: 33.25pt; margin-bottom: 0pt; =
margin-left: 0cm; text-align: justify; "><strong><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; ">April 10, =
2009</span></strong><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span>&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;</span>Full Paper Registration (Abstract Submission) =
Deadline</span></div><div style=3D"margin-top: 0cm; margin-right: =
33.25pt; margin-bottom: 0pt; margin-left: 0cm; text-align: justify; =
"><strong><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: =
Arial; ">April 17, 2009</span></strong><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span>&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;</span>Full Paper Submission Deadline</span></div><div =
style=3D"margin-top: 0cm; margin-right: 33.25pt; margin-bottom: 0pt; =
margin-left: 0cm; text-align: justify; "><strong><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; ">May 8, =
2009</span></strong><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; =
">&nbsp;&nbsp;&nbsp;<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>Short Paper Submission =
Deadline</span></div><div style=3D"margin-top: 0cm; margin-right: =
33.25pt; margin-bottom: 0pt; margin-left: 0cm; text-align: justify; =
"><strong><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: =
Arial; ">July 3, 2009</span></strong><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>Notification of =
Acceptance</span></div><div style=3D"margin-top: 0cm; margin-right: =
33.25pt; margin-bottom: 0pt; margin-left: 0cm; text-align: justify; =
"><strong><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: =
Arial; ">July 24, 2009</span></strong><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span>&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;</span>Camera-ready Submission =
Deadline</span></div><div style=3D"margin-top: 0cm; margin-right: =
6.25pt; margin-bottom: 0pt; margin-left: 0cm; text-align: justify; =
"><b><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial; =
"><font face=3D"Arial" size=3D"2"></font></span></b>&nbsp;</div><div =
style=3D"margin-top: 0cm; margin-right: 6.25pt; margin-bottom: 0pt; =
margin-left: 0cm; text-align: justify; "><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; ">In addition to full and =
short papers, submissions are also solicited for the&nbsp;conference =
events listed below. The&nbsp;<span =
class=3D"549120515-14012009">submission guidelines</span>&nbsp;for each =
of the conference events can be found on&nbsp;<strong><span =
style=3D"font-family: Arial; "><a =
href=3D"http://www.acmmm09.org/">http://www.acmmm09.org</a></span></strong=
></span><strong><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; "></span></strong></div><div style=3D"margin-top: =
0cm; margin-right: 6.25pt; margin-bottom: 0pt; margin-left: 0cm; =
text-align: justify; "><b><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; "><font face=3D"Arial" =
size=3D"2"></font></span></b>&nbsp;</div><div style=3D"margin-top: 0cm; =
margin-right: 6.25pt; margin-bottom: 0pt; margin-left: 0cm; text-align: =
justify; "><b><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; ">Panels&nbsp;</span></b><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; ">will consist of =
discussions on timely and controversial topics.</span><span lang=3D"EN-US"=
 style=3D"font-size: 10pt; font-family: Arial; "></span></div><div =
style=3D"margin-top: 0cm; margin-right: 6.25pt; margin-bottom: 0pt; =
margin-left: 0cm; text-align: justify; "><b><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; "><font face=3D"Arial" =
size=3D"2"></font></span></b>&nbsp;</div><div style=3D"margin-top: 0cm; =
margin-right: 6.25pt; margin-bottom: 0pt; margin-left: 0cm; text-align: =
justify; "><b><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; ">Tutorials&nbsp;</span></b><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; ">will&nbsp;</span><span =
lang=3D"EN-GB" style=3D"font-size: 10pt; font-family: Arial; ">address =
the state-of-the-art developments regarding all aspects of multimedia, =
and will be of interest to the entire multimedia community, from novices =
in the world of multimedia to the most seasoned researchers, from people =
working in academia to industry professionals.</span><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; "></span></div><div =
style=3D"margin-top: 0cm; margin-right: 6.25pt; margin-bottom: 0pt; =
margin-left: 0cm; text-align: justify; "><b><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; "><font face=3D"Arial" =
size=3D"2"></font></span></b>&nbsp;</div><div style=3D"margin-top: 0cm; =
margin-right: 6.25pt; margin-bottom: 0pt; margin-left: 0cm; text-align: =
justify; "><b><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; ">Workshops&nbsp;</span></b><span lang=3D"EN-GB" =
style=3D"font-size: 10pt; font-family: Arial; ">will address focused =
topics pertinent to the main conference that demand dedicated coverage =
due to their relevance to the current multimedia research and =
development.</span><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; "></span></div><div style=3D"margin-top: 0cm; =
margin-right: 6.25pt; margin-bottom: 0pt; margin-left: 0cm; text-align: =
justify; "><b><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; "><font face=3D"Arial" =
size=3D"2"></font></span></b>&nbsp;</div><div style=3D"margin-top: 0cm; =
margin-right: 6.25pt; margin-bottom: 0pt; margin-left: 0cm; text-align: =
justify; "><b><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; ">Open Source Competition</span></b><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;<strong>2009</strong>&nbsp;will be the sixth edition of this =
successful competition emphasizing the impact the ACM Multimedia =
conference aims to achieve on multimedia practice.</span></div><div =
style=3D"margin-top: 0cm; margin-right: 6.25pt; margin-bottom: 0pt; =
margin-left: 0cm; text-align: justify; "><b><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; "><font face=3D"Arial" =
size=3D"2"></font></span></b>&nbsp;</div><div style=3D"margin-top: 0cm; =
margin-right: 6.25pt; margin-bottom: 0pt; margin-left: 0cm; text-align: =
justify; "><b><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; ">Brave New Topics</span></b><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; ">&nbsp;track is a special =
sessions track containing papers extending the boundaries of multimedia =
research.</span></div><div style=3D"margin-top: 0cm; margin-right: =
6.25pt; margin-bottom: 0pt; margin-left: 0cm; text-align: justify; =
"><b><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial; =
"><font face=3D"Arial" size=3D"2"></font></span></b>&nbsp;</div><div =
style=3D"margin-top: 0cm; margin-right: 6.25pt; margin-bottom: 0pt; =
margin-left: 0cm; text-align: justify; "><b><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; ">Technical =
Demos</span></b><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;will show what is currently possible =
regarding all aspects of multimedia technology and its =
applications.</span></div><div style=3D"margin-top: 0cm; margin-right: =
6.25pt; margin-bottom: 0pt; margin-left: 0cm; text-align: justify; =
"><b><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial; =
"><font face=3D"Arial" size=3D"2"></font></span></b>&nbsp;</div><div =
style=3D"margin-top: 0cm; margin-right: 6.25pt; margin-bottom: 0pt; =
margin-left: 0cm; text-align: justify; "><b><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; ">Video =
Program</span></b><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;allows researchers and artists to =
demonstrate their tools, systems or applications without having to bring =
the equipment for a "live" demo.</span></div><p class=3D"MsoNormal" =
style=3D"margin-top: 0cm; margin-right: 6.25pt; margin-bottom: 0pt; =
margin-left: 0cm; text-align: justify; "><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; "><font face=3D"Arial" =
size=3D"2"></font></span>&nbsp;</p><div style=3D"margin-top: 0cm; =
margin-right: 6.25pt; margin-bottom: 0pt; margin-left: 0cm; text-align: =
justify; "><b><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; ">Interactive Art Program</span></b><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;will include long and short papers describing interactive =
multimedia art works, tools, applications, and technical approaches for =
creative uses of multimedia content and technology. It will also include =
an art exhibition.</span></div><div style=3D"margin-top: 0cm; =
margin-right: 6.25pt; margin-bottom: 0pt; margin-left: 0cm; text-align: =
justify; "><strong><span lang=3D"EN-US" style=3D"font-size: 10pt; color: =
red; font-family: Arial; "><font face=3D"Arial" =
size=3D"2"></font></span></strong>&nbsp;</div><div style=3D"margin-top: =
0cm; margin-right: 6.25pt; margin-bottom: 0pt; margin-left: 0cm; =
text-align: justify; "><strong><span lang=3D"EN-US" style=3D"font-size: =
10pt; color: red; font-family: Arial; ">NEW in =
2009:</span></strong><span class=3D"bold1"><b><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; ">&nbsp;Multimedia Grand =
Challenge</span></b></span><span lang=3D"EN-US" style=3D"font-size: =
10pt; font-family: Arial; ">&nbsp;is a set of challenges from various =
industry leaders, geared to engage the multimedia research community in =
solving relevant, interesting and challenging questions about the =
industry's 2-5 year horizon.</span></div><div style=3D"margin-top: 0cm; =
margin-right: 6.25pt; margin-bottom: 0pt; margin-left: 0cm; text-align: =
justify; "><b><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; "><font face=3D"Arial" =
size=3D"2"></font></span></b>&nbsp;</div><div style=3D"margin-top: 0cm; =
margin-right: 6.25pt; margin-bottom: 0pt; margin-left: 0cm; text-align: =
justify; "><b><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Arial; ">Doctoral Symposium</span></b><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Arial; ">&nbsp;is an opportunity =
for students involved in the preparation of a PhD to interactively =
discuss their research issues and ideas with senior =
researchers,&nbsp;<span =
class=3D"549120515-14012009">and&nbsp;</span>receive constructive =
feedback from members of the research =
community.</span></div></div><div><font face=3D"Arial" =
size=3D"2"></font>&nbsp;</div><div dir=3D"ltr" align=3D"left"><font =
face=3D"Times New Roman" size=3D"2"></font>&nbsp;</div><div dir=3D"ltr" =
align=3D"left"><font face=3D"Arial" =
size=3D"2"></font>&nbsp;</div><div>&nbsp;</div></div></div><br></div></div=
><br></body></html>=

--Apple-Mail-14--364413298--

--===============1906031531==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt

--===============1906031531==--

From avt-bounces@ietf.org  Mon Feb  2 17:33:42 2009
Return-Path: <avt-bounces@ietf.org>
X-Original-To: avt-archive@optimus.ietf.org
Delivered-To: ietfarch-avt-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C94063A6967; Mon,  2 Feb 2009 17:33:42 -0800 (PST)
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 0825A3A690D for <avt@core3.amsl.com>; Mon,  2 Feb 2009 17:33:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 wPksfurSb-eQ for <avt@core3.amsl.com>; Mon,  2 Feb 2009 17:33:41 -0800 (PST)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by core3.amsl.com (Postfix) with ESMTP id EE1D43A67A3 for <avt@ietf.org>; Mon,  2 Feb 2009 17:33:40 -0800 (PST)
Received: by yw-out-2324.google.com with SMTP id 3so1615914ywj.49 for <avt@ietf.org>; Mon, 02 Feb 2009 17:33:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=88CaMI+g2ZvsEbIdjHWRoYZOYzcfkIKmeFnMGW6EwKo=; b=UxAeLeSDlj8BTBAI6V3K+JRbW+Mb3T7KY53fi15zMvQRbIoJ+6fb+pAxVY5pC6R1sx EMcawa+PamQh4JYIECnCoaPMR14ktkpUF1poMT7NkulxqBgQneZnmAn1pYz0+0LU6ubR uvz25ZY026Wf2EMq7uZ53bgq3pslAIpanrrhU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=nMPj46T8ynpU3HxhRhBTtew5c8FyUIsKMn4gZlTGZYbz+bsryS6RzDJc1r6uBe8iJu V9HThhffxI8kgMBcrlOt/lYxLjXQyj4i8uNEnPTNo0Rd84+dC3owGoidqCyCde0rYiQ6 neF5RDSPuBmeAHwqZfqnLD0IhcPCvcan+dIfs=
MIME-Version: 1.0
Received: by 10.151.108.5 with SMTP id k5mr4422289ybm.194.1233624800733; Mon,  02 Feb 2009 17:33:20 -0800 (PST)
Date: Mon, 2 Feb 2009 23:33:20 -0200
Message-ID: <6e5aff670902021733x76a49c4ar97883b21b5b56f20@mail.gmail.com>
From: Alejandro Cabrera Obed <aco1967@gmail.com>
To: AVT Lista <avt@ietf.org>
Subject: [AVT] Videoconference many-to-many
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org

Dear all, I've implemented an asterisk 1.4 SIP for videocalling
one-to-one, voip and video at the same time...it works ok.

So my scenario has the possibility to intercommunicate just one person
to another.

Is there any system capable of implement a real videoconference (voip
+ video) among many persons ??? Maybe Asterisk has this feature and I
don't know ???

Can you give me some help in order to think about this scenario ??? I
know multicast is the best way to implement this because the economy
of BW.

Thanks a lot and greetings !!!


-- 
Alejandro Cabrera Obed
aco1967@gmail.com
_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt

From john.lazzaro@gmail.com  Tue Feb  3 14:27:45 2009
Return-Path: <john.lazzaro@gmail.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 A87243A66B4 for <avt@core3.amsl.com>; Tue,  3 Feb 2009 14:27:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 V+wCz9qsG9tp for <avt@core3.amsl.com>; Tue,  3 Feb 2009 14:27:44 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.225]) by core3.amsl.com (Postfix) with ESMTP id 0BBBB3A67D7 for <avt@ietf.org>; Tue,  3 Feb 2009 14:27:44 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id g9so1562874rvb.5 for <avt@ietf.org>; Tue, 03 Feb 2009 14:27:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=2lbNdmH8w2GRzTsQwxQw0IW23/lbNMY2H4BKWgeurpw=; b=IZONnYWkPOpEMTaptD5GkgMk1f4I1aZff9M6SbBV0XjTL25kTlaJfbSZg20yh1rgTp Nn4e280020DsG/FhpKfxi6fQaBEUjYbqm6nP7BGwCyRrcsBCZwtmM5OKhA+57gzM9Bl9 B6lzzuTrev0BONMgDBP45cc3efvoTPySfAwZE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=mIYwWlqu1HUOeDIaSBRmMSwOc+v6ZX7SikgrlOTkuggAcz5qih13oooTQkq/8ALhvH XgQ/dg+Hhq6eFyWrwLzc9KXAdW528y1TI37WeXk28FGJr/lbQiSNAt5buGbKBBhnJNKg EOs9K0sJC/gQlYSknw0gTcSJ+MA6bsZUA8blo=
MIME-Version: 1.0
Received: by 10.142.132.2 with SMTP id f2mr2560613wfd.108.1233700044074; Tue,  03 Feb 2009 14:27:24 -0800 (PST)
Date: Tue, 3 Feb 2009 14:27:24 -0800
Message-ID: <302f570902031427y1b75ab61of5c13a34be2e6ab1@mail.gmail.com>
From: John Lazzaro <john.lazzaro@gmail.com>
To: avt@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [AVT] New I-D: draft-ietf-avt-rfc4695-bis-05
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, 03 Feb 2009 22:27:45 -0000

Hi everyone,

Just updated the RFC 4695 bis I-D (RTP MIDI),
because the previous I-D bis is about to expire.

No changes except for the document name
and the new boilerplate.

-- 
John Lazzaro
http://www.cs.berkeley.edu/~lazzaro
john [dot] lazzaro [at] gmail [dot] com

From root@core3.amsl.com  Tue Feb  3 14:30:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 91BD13A6AF5; Tue,  3 Feb 2009 14:30:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090203223001.91BD13A6AF5@core3.amsl.com>
Date: Tue,  3 Feb 2009 14:30:01 -0800 (PST)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-rfc4695-bis-05.txt
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, 03 Feb 2009 22:30:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.


	Title           : RTP Payload Format for MIDI
	Author(s)       : J. Lazzaro, J.  Wawrzynek
	Filename        : draft-ietf-avt-rfc4695-bis-05.txt
	Pages           : 182
	Date            : 2009-02-03

This memo describes a Real-time Transport Protocol (RTP) payload
format for the MIDI (Musical Instrument Digital Interface) command
language.  The format encodes all commands that may legally appear on
a MIDI 1.0 DIN cable.  The format is suitable for interactive
applications (such as network musical performance) and content-
delivery applications (such as file streaming).  The format may be
used over unicast and multicast UDP and TCP, and it defines tools for
graceful recovery from packet loss.  Stream behavior, including the
MIDI rendering method, may be customized during session setup.  The
format also serves as a mode for the mpeg4-generic format, to support
the MPEG 4 Audio Object Types for General MIDI, Downloadable Sounds
Level 2, and Structured Audio.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc4695-bis-05.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-avt-rfc4695-bis-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-02-03142322.I-D@ietf.org>


--NextPart--

From ron.even.tlv@gmail.com  Tue Feb  3 21:35:19 2009
Return-Path: <ron.even.tlv@gmail.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 F3BCB3A6C5B for <avt@core3.amsl.com>; Tue,  3 Feb 2009 21:35:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.985
X-Spam-Level: 
X-Spam-Status: No, score=-0.985 tagged_above=-999 required=5 tests=[AWL=-0.987, BAYES_50=0.001, HTML_MESSAGE=0.001]
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 j3pLV1iE+jeH for <avt@core3.amsl.com>; Tue,  3 Feb 2009 21:35:18 -0800 (PST)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by core3.amsl.com (Postfix) with ESMTP id DDDA13A6C5C for <avt@ietf.org>; Tue,  3 Feb 2009 21:35:17 -0800 (PST)
Received: by fg-out-1718.google.com with SMTP id l26so1085490fgb.41 for <avt@ietf.org>; Tue, 03 Feb 2009 21:34:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :message-id:mime-version:content-type:x-mailer:thread-index :content-language; bh=sev/M1DFGhUCB1//ZBfTFzISXCl7fi5Nakdy5CaCpDU=; b=UoTzce/iTRYVBUrriLXiEsoMU7P+1gOTWdbbQEIgYw865IDhpOLJcOCm2ObaUxjtO9 NWPj2TOdH6tJfT3AG+Z+WRW1N/8X63pIi5NHaiYmzcM6geoJLLlBhlGr0IZlYuoPTRk6 LaN1OCNEVpdN4SIoIG+qKFo/ME0MFArY6vTk4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language; b=YZKVrzD0rGQaNw3W3MhmPlSEZsDcPnAmrhhCRFRojz8tVIDx3pYYni8wv/jWbMusOb 4wgI8vAxUS4IilqihnHeQLE10CCzQ2Jk3Wkpqep07lH4mPnmnLWfElU8jkEUxAoPIJ2e Vg0ScQYxZjPW4Ll2BRqkXvTBEQHX++xT2Qkwk=
Received: by 10.86.82.16 with SMTP id f16mr1448289fgb.26.1233725697065; Tue, 03 Feb 2009 21:34:57 -0800 (PST)
Received: from windows8d787f9 (bzq-79-179-108-212.red.bezeqint.net [79.179.108.212]) by mx.google.com with ESMTPS id l19sm6347118fgb.47.2009.02.03.21.34.55 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 03 Feb 2009 21:34:56 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'IETF AVT WG'" <avt@ietf.org>
Date: Wed, 4 Feb 2009 07:33:28 +0200
Message-ID: <49892900.1358560a.188b.3e9c@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0014_01C9869A.E0A253B0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcmGihuIcsg75kRCSjigmCw44XnyiQ==
Content-Language: en-us
Subject: [AVT] conclusion of WGLC on draft-ietf-avt-seed-srtp-08
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, 04 Feb 2009 05:35:19 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0014_01C9869A.E0A253B0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

The short WGLC is finished and the document will be sent to publication

 

Thanks to all the reviewers.

 Roni Even


------=_NextPart_000_0014_01C9869A.E0A253B0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>Hi,<o:p></o:p></p>

<p class=3DMsoNormal>The short WGLC is finished and the document will be =
sent to
publication<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Thanks to all the reviewers.<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;Roni Even<o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_0014_01C9869A.E0A253B0--


From tom.taylor@rogers.com  Wed Feb  4 12:12:09 2009
Return-Path: <tom.taylor@rogers.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 03B7A3A689C for <avt@core3.amsl.com>; Wed,  4 Feb 2009 12:12:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.368
X-Spam-Level: 
X-Spam-Status: No, score=-2.368 tagged_above=-999 required=5 tests=[AWL=0.231,  BAYES_00=-2.599]
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 XR8lqOSjLXMF for <avt@core3.amsl.com>; Wed,  4 Feb 2009 12:12:08 -0800 (PST)
Received: from smtp125.rog.mail.re2.yahoo.com (smtp125.rog.mail.re2.yahoo.com [206.190.53.30]) by core3.amsl.com (Postfix) with SMTP id 8FF403A683D for <avt@ietf.org>; Wed,  4 Feb 2009 12:12:08 -0800 (PST)
Received: (qmail 43535 invoked from network); 4 Feb 2009 20:05:09 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:Content-Type:Content-Transfer-Encoding; b=tGjQAeJFgr1rYQbsRDdeHVb/qlaq1/LYqgfUW9L4eH6uqK35GNyOW3PRBwcUm0VIVr+ATL3uZUMLBiYu4eQXfTyyoAtf/6WNBy4uo7T21O0cyiDtJUgjDwQuj95I4dh6GtEYY8zWYd9NaSHPVolFbKpsITsUWgGjDnl2J/VRYsY= ; 
Received: from unknown (HELO ?192.168.0.101?) (tom.taylor@72.140.46.24 with plain) by smtp125.rog.mail.re2.yahoo.com with SMTP; 4 Feb 2009 20:05:09 -0000
X-YMail-OSG: GQh.LloVM1k7W2WtMtRbjzpxddvC9MakGnev_Hl8B31b1Buh.6Ks71dwGPuI.LnFrA--
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4989F4F4.7050006@rogers.com>
Date: Wed, 04 Feb 2009 15:05:08 -0500
From: Tom Taylor <tom.taylor@rogers.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: iesg-secretary@ietf.org, Cullen Jennings <fluffy@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Schmidt , Malte" <malte.schmidt@dolby.com>, IETF AVT WG <avt@ietf.org>, Ralph Sperschneider <ralph.sperschneider@iis.fraunhofer.de>
Subject: [AVT] Publication request -- draft-ietf-avt-rtp-mps-02.txt
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, 04 Feb 2009 20:12:09 -0000

This is a request for publication of draft-ietf-avt-rtp-mps-02.txt, RTP Payload 
Format for Elementary Streams with MPEG Surround multi- channel audio. The 
corresponding AVT WG milestone was "Submit RTP Payload Format for Elementary 
Streams with MPEG Surround multi-channel audio for Proposed Standard", due last 
August.

As required by RFC 4858, this is the current template for the Document Shepherd 
Write-Up. This version is dated September 17, 2008.

     (1.a) Who is the Document Shepherd for this document? Has the
           Document Shepherd personally reviewed this version of the
           document and, in particular, does he or she believe this
           version is ready for forwarding to the IESG for publication?

           The Document Shepherd is Tom Taylor. I have personally reviewed
           this version of the document and believe it is ready for
           publication.

     (1.b) Has the document had adequate review both from key WG members
           and from key non-WG members? Does the Document Shepherd have
           any concerns about the depth or breadth of the reviews that
           have been performed?

           The document has been available to the Working Group since last
           May. The only comments in that time were from Colin Perkins and
           Tom Taylor. These comments were resolved. There were no comments
           on the media types list regarding the addition of new parameters
           to the audio/mpeg-generic media type. While the lack of comment
           could be a source of concern in some cases, the Shepherd believes
           that in this case it springs from the fact that the document was
           well-written in the first place.

     (1.c) Does the Document Shepherd have concerns that the document
           needs more review from a particular or broader perspective,
           e.g., security, operational complexity, someone familiar with
           AAA, internationalization or XML?

           No.

     (1.d) Does the Document Shepherd have any specific concerns or
           issues with this document that the Responsible Area Director
           and/or the IESG should be aware of? For example, perhaps he
           or she is uncomfortable with certain parts of the document, or
           has concerns whether there really is a need for it. In any
           event, if the WG has discussed those issues and has indicated
           that it still wishes to advance the document, detail those
           concerns here. Has an IPR disclosure related to this document
           been filed? If so, please include a reference to the
           disclosure and summarize the WG discussion and conclusion on
           this issue.

           No specific concerns. No IPR disclosures. Note that there is
           a dependency on this document in DVB, ATSC and 3GPP.

     (1.e) How solid is the WG consensus behind this document? Does it
           represent the strong concurrence of a few individuals, with
           others being silent, or does the WG as a whole understand and
           agree with it?

           General WG silence, as noted in (1.b).

     (1.f) Has anyone threatened an appeal or otherwise indicated extreme
           discontent? If so, please summarise the areas of conflict in
           separate email messages to the Responsible Area Director. (It
           should be in a separate email because this questionnaire is
           entered into the ID Tracker.)

           No.

     (1.g) Has the Document Shepherd personally verified that the
           document satisfies all ID nits? (See
           http://www.ietf.org/ID-Checklist.html and
           http://tools.ietf.org/tools/idnits/). Boilerplate checks are
           not enough; this check needs to be thorough. Has the document
           met all formal review criteria it needs to, such as the MIB
           Doctor, media type and URI type reviews?

           No nits displayed by Datatracker. One missing "t" in
           "confidentiality" on line 448 (Security Considerations section).
           The new parameters were presented to the media types list
           with no comment.

     (1.h) Has the document split its references into normative and
           informative? Are there normative references to documents that
           are not ready for advancement or are otherwise in an unclear
           state? If such normative references exist, what is the
           strategy for their completion? Are there normative references
           that are downward references, as described in [RFC3967]? If
           so, list these downward references to support the Area
           Director in the Last Call procedure for them [RFC3967].

           References OK. IDnits concerned about references to ISO
           documents, but these are properly normative.

     (1.i) Has the Document Shepherd verified that the document IANA
           consideration section exists and is consistent with the body
           of the document? If the document specifies protocol
           extensions, are reservations requested in appropriate IANA
           registries? Are the IANA registries clearly identified? If
           the document creates a new registry, does it define the
           proposed initial contents of the registry and an allocation
           procedure for future registrations? Does it suggest a
           reasonable name for the new registry? See [RFC5226]. If the
           document describes an Expert Review process has Shepherd
           conferred with the Responsible Area Director so that the IESG
           can appoint the needed Expert during the IESG Evaluation?

           IANA section OK.

     (1.j) Has the Document Shepherd verified that sections of the
           document that are written in a formal language, such as XML
           code, BNF rules, MIB definitions, etc., validate correctly in
           an automated checker?

           Not applicable.

     (1.k) The IESG approval announcement includes a Document
           Announcement Write-Up. Please provide such a Document
           Announcement Write-Up? Recent examples can be found in the
           "Action" announcements for approved documents. The approval
           announcement contains the following sections:

           Technical Summary
   	    This memo describes extensions for the RTP payload format defined in
   	    RFC3640 for the transport of MPEG Surround multi-channel audio.
   	    Additional Media Type parameters are defined to signal backwards
   	    compatible transmission inside an MPEG-4 audio elementary stream. In
   	    addition a layered transmission scheme without using the MPEG-4
   	    systems framework is presented to transport an MPEG Surround
   	    elementary stream via RTP in parallel with an RTP stream containing
   	    the downmixed audio data.


           Working Group Summary
              There were no objections to making this a WG item, and limited
              comments during WGLC.

           Document Quality
              Colin Perkins was the primary reviewer during Working Group
              Last Call. The proposed parameters were presented for Media Type
              review in a message dated 19/11/2008. DVB, ATSC, and 3GPP have
              dependencies on this document.
(end)





From tom.taylor@rogers.com  Wed Feb  4 13:34:36 2009
Return-Path: <tom.taylor@rogers.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 E696D3A6B6E for <avt@core3.amsl.com>; Wed,  4 Feb 2009 13:34:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.375
X-Spam-Level: 
X-Spam-Status: No, score=-2.375 tagged_above=-999 required=5 tests=[AWL=0.224,  BAYES_00=-2.599]
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 SrQnaVLp0-R7 for <avt@core3.amsl.com>; Wed,  4 Feb 2009 13:34:35 -0800 (PST)
Received: from smtp111.rog.mail.re2.yahoo.com (smtp111.rog.mail.re2.yahoo.com [206.190.37.1]) by core3.amsl.com (Postfix) with SMTP id 8238C3A683D for <avt@ietf.org>; Wed,  4 Feb 2009 13:34:35 -0800 (PST)
Received: (qmail 88551 invoked from network); 4 Feb 2009 21:34:15 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:Content-Type:Content-Transfer-Encoding; b=GZPvLucqcTxyMR89mTH3e63x+g254O5YW1qY42QNSc+zbmkF1/tuBJRY6Cqn5HGFjeo+7SIDeagttG7+Y+Cm8Vf/2UPdMVwSMdQlgSEjQZPKVJW+uLiLl+DbGcysVwAzAEo0o1INkmgLRTpc4sc8n5WQFdAImEGS5vdwZv9aFcc= ; 
Received: from unknown (HELO ?192.168.0.101?) (tom.taylor@72.140.46.24 with plain) by smtp111.rog.mail.re2.yahoo.com with SMTP; 4 Feb 2009 21:34:14 -0000
X-YMail-OSG: X881hu0VM1mY1eay4ehIpgdi8bX9w6Vf3KP59JQqQv7qXelQX8SKvgCOvt_iRznk.w--
X-Yahoo-Newman-Property: ymail-3
Message-ID: <498A09D5.5060907@rogers.com>
Date: Wed, 04 Feb 2009 16:34:13 -0500
From: Tom Taylor <tom.taylor@rogers.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: iesg-secretary@ietf.org, Cullen Jennings <fluffy@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: MARJOU Xavier RD-MAPS-LAN <xavier.marjou@orange-ftgroup.com>, IETF AVT WG <avt@ietf.org>
Subject: [AVT] Request for publication -- draft-ietf-avt-app-rtp-keepalive-05.txt
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, 04 Feb 2009 21:34:37 -0000

This is a request for publication of draft-ietf-avt-app-rtp-keepalive-05, 
"Application Mechanism for maintaining alive the Network Address Translator 
(NAT) mappings associated to RTP flows", as a BCP. This corresponds to AVT WG 
milestone "Aug 2008  Submit draft on Mechanisms to keep NAT bindings for RTP 
flows alive for BCP".

As required by RFC 4858, this is the current template for the Document Shepherd 
Write-Up. This version is dated September 17, 2008.

     (1.a) Who is the Document Shepherd for this document? Has the
           Document Shepherd personally reviewed this version of the
           document and, in particular, does he or she believe this
           version is ready for forwarding to the IESG for publication?

           Tom Taylor is Document Shepherd. I have read this version of the
           document and believe it is ready for publication.

     (1.b) Has the document had adequate review both from key WG members
           and from key non-WG members? Does the Document Shepherd have
           any concerns about the depth or breadth of the reviews that
           have been performed?

           The document has been well reviewed, by participants in the AVT,
           BEHAVE, and MMUSIC Working Groups. It began in 2007 as a BEHAVE work
           proposal with a broader scope, but was eventually focussed on
           RTP keepalive in the absence of ICE support.

     (1.c) Does the Document Shepherd have concerns that the document
           needs more review from a particular or broader perspective,
           e.g., security, operational complexity, someone familiar with
           AAA, internationalization or XML?

           No concern.

     (1.d) Does the Document Shepherd have any specific concerns or
           issues with this document that the Responsible Area Director
           and/or the IESG should be aware of? For example, perhaps he
           or she is uncomfortable with certain parts of the document, or
           has concerns whether there really is a need for it. In any
           event, if the WG has discussed those issues and has indicated
           that it still wishes to advance the document, detail those
           concerns here. Has an IPR disclosure related to this document
           been filed? If so, please include a reference to the
           disclosure and summarize the WG discussion and conclusion on
           this issue.

           No concerns. No IPR disclosures.

     (1.e) How solid is the WG consensus behind this document? Does it
           represent the strong concurrence of a few individuals, with
           others being silent, or does the WG as a whole understand and
           agree with it?

           There is solid WG consensus. As evidenced by the Acknowledgements
           section, a number of people provided comments that helped the
           document take shape along the way.

     (1.f) Has anyone threatened an appeal or otherwise indicated extreme
           discontent? If so, please summarise the areas of conflict in
           separate email messages to the Responsible Area Director. (It
           should be in a separate email because this questionnaire is
           entered into the ID Tracker.)

           No.

     (1.g) Has the Document Shepherd personally verified that the
           document satisfies all ID nits? (See
           http://www.ietf.org/ID-Checklist.html and
           http://tools.ietf.org/tools/idnits/). Boilerplate checks are
           not enough; this check needs to be thorough. Has the document
           met all formal review criteria it needs to, such as the MIB
           Doctor, media type and URI type reviews?

           ID nits is confused about the presence of the RFC 2119
           boilerplate text, but it is there as section 2. All OK
           otherwise.

     (1.h) Has the document split its references into normative and
           informative? Are there normative references to documents that
           are not ready for advancement or are otherwise in an unclear
           state? If such normative references exist, what is the
           strategy for their completion? Are there normative references
           that are downward references, as described in [RFC3967]? If
           so, list these downward references to support the Area
           Director in the Last Call procedure for them [RFC3967].

           All OK.

     (1.i) Has the Document Shepherd verified that the document IANA
           consideration section exists and is consistent with the body
           of the document? If the document specifies protocol
           extensions, are reservations requested in appropriate IANA
           registries? Are the IANA registries clearly identified? If
           the document creates a new registry, does it define the
           proposed initial contents of the registry and an allocation
           procedure for future registrations? Does it suggest a
           reasonable name for the new registry? See [RFC5226]. If the
           document describes an Expert Review process has Shepherd
           conferred with the Responsible Area Director so that the IESG
           can appoint the needed Expert during the IESG Evaluation?

           All OK. The proposed rtp-keepalive SDP parameter drew no
           comments from MMUSIC.

     (1.j) Has the Document Shepherd verified that sections of the
           document that are written in a formal language, such as XML
           code, BNF rules, MIB definitions, etc., validate correctly in
           an automated checker?

           Not applicable.

     (1.k) The IESG approval announcement includes a Document
           Announcement Write-Up. Please provide such a Document
           Announcement Write-Up? Recent examples can be found in the
           "Action" announcements for approved documents. The approval
           announcement contains the following sections:

           Technical Summary
   	   This document lists the different mechanisms that enable applications
   	   using Real-time Transport Protocol (RTP) to maintain their RTP
   	   Network Address Translator (NAT) mappings alive.  It also makes a
   	   recommendation for a preferred mechanism.  This document is not
   	   applicable to Interactive Connectivity Establishment (ICE) agents.

           Working Group Summary
              This document began in 2006 as a proposed BEHAVE work item with
              broader scope. The scope was refined after discussion between
              BEHAVE, MMUSIC, and AVT Working Groups to that indicated above.
              The rtp-keepalive SDP parameter was added by direction of the
              AVT Chair when no comments were received either for or against
              that proposal.

           Document Quality
              This document was shaped by comments from a number of contributors,
              as listed in the Acknoledgements section. As a general application
              guide, it is expected to have broad implementation.

(end)

From jeedward@yahoo.com  Wed Feb  4 16:59:07 2009
Return-Path: <jeedward@yahoo.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 1A8C53A6883 for <avt@core3.amsl.com>; Wed,  4 Feb 2009 16:59:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.79
X-Spam-Level: 
X-Spam-Status: No, score=-0.79 tagged_above=-999 required=5 tests=[AWL=0.412,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
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 FjaLixIgzsWT for <avt@core3.amsl.com>; Wed,  4 Feb 2009 16:59:06 -0800 (PST)
Received: from n22c.bullet.mail.mud.yahoo.com (n22c.bullet.mail.mud.yahoo.com [68.142.206.219]) by core3.amsl.com (Postfix) with SMTP id 55C9D3A67F2 for <avt@ietf.org>; Wed,  4 Feb 2009 16:59:05 -0800 (PST)
Received: from [209.191.108.96] by n22.bullet.mail.mud.yahoo.com with NNFMP; 05 Feb 2009 00:58:45 -0000
Received: from [68.142.201.64] by t3.bullet.mud.yahoo.com with NNFMP; 05 Feb 2009 00:58:45 -0000
Received: from [127.0.0.1] by omp416.mail.mud.yahoo.com with NNFMP; 05 Feb 2009 00:58:44 -0000
X-Yahoo-Newman-Property: ymail-5
X-Yahoo-Newman-Id: 978886.5366.bm@omp416.mail.mud.yahoo.com
Received: (qmail 95605 invoked by uid 60001); 5 Feb 2009 00:58:44 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=AMUs2BQFO3NIvzZ4rqA/3dKjUIDcFbUlxJ/WjDGKUwwKUr81wInI42GPA0cNghsqPELiYpZ+nz7g51qStlchyGtjC+/zUfzavpyHl8AtSZH7Nfy2q/MSy8eyQJ5HqQ/H7RnOT6Y6pkD2/blrvg+NkyNXcUmf4Ao097GEgH8U4eM=;
X-YMail-OSG: Ekio3T8VM1mAP5TlJblFoTXsijLNu1LV4tcTsibE5LIZ4TytHz6hfC2y
Received: from [67.233.188.239] by web45909.mail.sp1.yahoo.com via HTTP; Wed, 04 Feb 2009 16:58:43 PST
X-Mailer: YahooMailWebService/0.7.260.1
Date: Wed, 4 Feb 2009 16:58:43 -0800 (PST)
From: John Edward <jeedward@yahoo.com>
To: avt@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-2053431976-1233795523=:95544"
Message-ID: <136269.95544.qm@web45909.mail.sp1.yahoo.com>
Subject: [AVT] Draft paper submission deadline extended: Audio/Video Transport
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: Thu, 05 Feb 2009 00:59:07 -0000

--0-2053431976-1233795523=:95544
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable


Draft paper submission deadline extended: Audio/Video Transport
=A0
The deadline for draft paper submission at the 2009 International Conferenc=
e on High Performance Computing, Networking and Communication Systems (HPCN=
CS-09) (website: http://www.PromoteResearch.org ) is extended due to numero=
us requests from the authors. As a result, the deadline for paper submissio=
n for the special session on Audio/Video Transport is also extended accordi=
ngly. The conference and the session will be held during July 13-16 2009 in=
 Orlando, FL, USA. We invite draft paper submissions. The conference will t=
ake place at the same time and venue where several other international conf=
erences are taking place. The other conferences include:
=B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Artificial Intellig=
ence and Pattern Recognition (AIPR-09)=20
=B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Automation, Robotic=
s and Control Systems (ARCS-09)
=B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Bioinformatics, Com=
putational Biology, Genomics and Chemoinformatics (BCBGC-09)=20
=B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Enterprise Informat=
ion Systems and Web Technologies (EISWT-09)
=B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Information Securit=
y and Privacy (ISP-09)
=B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Recent Advances in =
Information Technology and Applications (RAITA-09)
=B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Software Engineerin=
g Theory and Practice (SETP-09)=20
=B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Theory and Applicat=
ions of Computational Science (TACS-09)
=B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Theoretical and Mat=
hematical Foundations of Computer Science (TMFCS-09)
=A0
The website http://www.PromoteResearch.org contains more details.
=A0
Sincerely
John Edward
Publicity committee
=A0
=A0
=A0
=A0=0A=0A=0A      
--0-2053431976-1233795523=:95544
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<table cellspacing=3D"0" cellpadding=3D"0" border=3D"0" ><tr><td valign=3D"=
top" style=3D"font: inherit;"><A name=3DOLE_LINK4></A>
<P style=3D"MARGIN: 0in 0in 0pt"><A name=3DOLE_LINK4></A><A name=3DOLE_LINK=
3><SPAN style=3D"mso-bookmark: OLE_LINK4"><FONT face=3D"Times New Roman" si=
ze=3D3>Draft paper submission deadline extended: </FONT></SPAN></A><SPAN st=
yle=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'; mso-fareast=
-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-lang=
uage: EN-US; mso-bidi-language: AR-SA"><SPAN style=3D"FONT-SIZE: 12pt; FONT=
-FAMILY: 'Times New Roman','serif'; mso-fareast-font-family: 'Times New Rom=
an'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-langua=
ge: AR-SA"><SPAN style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: 'Time=
s New Roman','serif'; mso-fareast-font-family: 'Times New Roman'; mso-ansi-=
language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><SP=
AN style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'; mso-fa=
reast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast=
-language:
 EN-US; mso-bidi-language: AR-SA">Audio/Video Transport</SPAN></SPAN></SPAN=
></SPAN></DIV>
<P style=3D"MARGIN: 0in 0in 0pt"><SPAN style=3D"mso-bookmark: OLE_LINK3"><S=
PAN style=3D"mso-bookmark: OLE_LINK4"><?xml:namespace prefix =3D o ns =3D "=
urn:schemas-microsoft-com:office:office" /><o:p><FONT face=3D"Times New Rom=
an" size=3D3>&nbsp;</FONT></o:p></SPAN></SPAN></DIV>
<P style=3D"MARGIN: 0in 0in 0pt"><SPAN style=3D"mso-bookmark: OLE_LINK3"><S=
PAN style=3D"mso-bookmark: OLE_LINK4"><FONT face=3D"Times New Roman" size=
=3D3>The deadline for draft paper submission at the 2009 <SPAN style=3D"COL=
OR: black">International Conference on High Performance Computing, Networki=
ng and Communication Systems (HPCNCS-09) </SPAN>(website: </FONT></SPAN></S=
PAN><A href=3D"http://www.promoteresearch.org/"><FONT color=3D#0000ff><FONT=
 size=3D3><FONT face=3D"Times New Roman"><SPAN style=3D"mso-bookmark: OLE_L=
INK3"><SPAN style=3D"mso-bookmark: OLE_LINK4">http://www.PromoteResearch.or=
g</SPAN></SPAN><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-b=
ookmark: OLE_LINK4"></SPAN></SPAN></FONT></FONT></FONT></A><SPAN style=3D"m=
so-bookmark: OLE_LINK3"><SPAN style=3D"mso-bookmark: OLE_LINK4"><FONT size=
=3D3><FONT face=3D"Times New Roman"> ) is extended due to numerous requests=
 from the authors. As a result, the deadline for paper submission for the s=
pecial session on <SPAN
 style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'; mso-fare=
ast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-l=
anguage: EN-US; mso-bidi-language: AR-SA"><SPAN style=3D"FONT-SIZE: 12pt; F=
ONT-FAMILY: 'Times New Roman','serif'; mso-fareast-font-family: 'Times New =
Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-lan=
guage: AR-SA"><SPAN style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: 'T=
imes New Roman','serif'; mso-fareast-font-family: 'Times New Roman'; mso-an=
si-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">=
<SPAN style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'; mso=
-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fare=
ast-language: EN-US; mso-bidi-language: AR-SA">Audio/Video Transport </SPAN=
></SPAN></SPAN></SPAN>is also extended accordingly. The conference and the =
session will be held during July 13-16 2009 in Orlando, FL, USA. We invite
 draft paper submissions. The conference will take place at the same time a=
nd venue where several other international conferences are taking place. Th=
e other conferences include:<SPAN style=3D"COLOR: black"><o:p></o:p></SPAN>=
</FONT></FONT></SPAN></SPAN></DIV>
<P style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 l=
evel1 lfo1"><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-book=
mark: OLE_LINK4"><SPAN style=3D"COLOR: black; FONT-FAMILY: Symbol; mso-fare=
ast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style=3D"mso-l=
ist: Ignore"><FONT size=3D3>=B7</FONT><SPAN style=3D"FONT: 7pt 'Times New R=
oman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPA=
N><FONT size=3D3><FONT face=3D"Times New Roman"><SPAN style=3D"COLOR: black=
">International Conference on Artificial Intelligence and Pattern Recogniti=
on (AIPR-09)</SPAN> <SPAN style=3D"COLOR: black"><o:p></o:p></SPAN></FONT><=
/FONT></SPAN></SPAN></DIV>
<P style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 l=
evel1 lfo1"><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-book=
mark: OLE_LINK4"><SPAN style=3D"COLOR: black; FONT-FAMILY: Symbol; mso-fare=
ast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style=3D"mso-l=
ist: Ignore"><FONT size=3D3>=B7</FONT><SPAN style=3D"FONT: 7pt 'Times New R=
oman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPA=
N><SPAN style=3D"COLOR: black"><FONT size=3D3><FONT face=3D"Times New Roman=
">International Conference on Automation, Robotics and Control Systems (ARC=
S-09)<o:p></o:p></FONT></FONT></SPAN></SPAN></SPAN></DIV>
<P style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 l=
evel1 lfo1"><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-book=
mark: OLE_LINK4"><SPAN style=3D"COLOR: black; FONT-FAMILY: Symbol; mso-fare=
ast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style=3D"mso-l=
ist: Ignore"><FONT size=3D3>=B7</FONT><SPAN style=3D"FONT: 7pt 'Times New R=
oman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPA=
N><SPAN style=3D"COLOR: black"><FONT size=3D3><FONT face=3D"Times New Roman=
">International Conference on Bioinformatics, Computational Biology, Genomi=
cs and Chemoinformatics (BCBGC-09) <o:p></o:p></FONT></FONT></SPAN></SPAN><=
/SPAN></DIV>
<P style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 l=
evel1 lfo1"><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-book=
mark: OLE_LINK4"><SPAN style=3D"COLOR: black; FONT-FAMILY: Symbol; mso-fare=
ast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style=3D"mso-l=
ist: Ignore"><FONT size=3D3>=B7</FONT><SPAN style=3D"FONT: 7pt 'Times New R=
oman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPA=
N><SPAN style=3D"COLOR: black"><FONT size=3D3><FONT face=3D"Times New Roman=
">International Conference on Enterprise Information Systems and Web Techno=
logies (EISWT-09)<o:p></o:p></FONT></FONT></SPAN></SPAN></SPAN></DIV>
<P style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 l=
evel1 lfo1"><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-book=
mark: OLE_LINK4"><SPAN style=3D"COLOR: black; FONT-FAMILY: Symbol; mso-fare=
ast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style=3D"mso-l=
ist: Ignore"><FONT size=3D3>=B7</FONT><SPAN style=3D"FONT: 7pt 'Times New R=
oman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPA=
N><SPAN style=3D"COLOR: black"><FONT size=3D3><FONT face=3D"Times New Roman=
">International Conference on Information Security and Privacy (ISP-09)<o:p=
></o:p></FONT></FONT></SPAN></SPAN></SPAN></DIV>
<P style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 l=
evel1 lfo1"><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-book=
mark: OLE_LINK4"><SPAN style=3D"COLOR: black; FONT-FAMILY: Symbol; mso-fare=
ast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style=3D"mso-l=
ist: Ignore"><FONT size=3D3>=B7</FONT><SPAN style=3D"FONT: 7pt 'Times New R=
oman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPA=
N><SPAN style=3D"COLOR: black"><FONT size=3D3><FONT face=3D"Times New Roman=
">International Conference on Recent Advances in Information Technology and=
 Applications (RAITA-09)<o:p></o:p></FONT></FONT></SPAN></SPAN></SPAN></DIV=
>
<P style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 l=
evel1 lfo1"><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-book=
mark: OLE_LINK4"><SPAN style=3D"COLOR: black; FONT-FAMILY: Symbol; mso-fare=
ast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style=3D"mso-l=
ist: Ignore"><FONT size=3D3>=B7</FONT><SPAN style=3D"FONT: 7pt 'Times New R=
oman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPA=
N><SPAN style=3D"COLOR: black"><FONT size=3D3><FONT face=3D"Times New Roman=
">International Conference on Software Engineering Theory and Practice (SET=
P-09) <o:p></o:p></FONT></FONT></SPAN></SPAN></SPAN></DIV>
<P style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 l=
evel1 lfo1"><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-book=
mark: OLE_LINK4"><SPAN style=3D"COLOR: black; FONT-FAMILY: Symbol; mso-fare=
ast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style=3D"mso-l=
ist: Ignore"><FONT size=3D3>=B7</FONT><SPAN style=3D"FONT: 7pt 'Times New R=
oman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPA=
N><SPAN style=3D"COLOR: black"><FONT size=3D3><FONT face=3D"Times New Roman=
">International Conference on Theory and Applications of Computational Scie=
nce (TACS-09)<o:p></o:p></FONT></FONT></SPAN></SPAN></SPAN></DIV>
<P style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 l=
evel1 lfo1"><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-book=
mark: OLE_LINK4"><SPAN style=3D"COLOR: black; FONT-FAMILY: Symbol; mso-fare=
ast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style=3D"mso-l=
ist: Ignore"><FONT size=3D3>=B7</FONT><SPAN style=3D"FONT: 7pt 'Times New R=
oman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPA=
N><SPAN style=3D"COLOR: black"><FONT size=3D3><FONT face=3D"Times New Roman=
">International Conference on Theoretical and Mathematical Foundations of C=
omputer Science (TMFCS-09)<o:p></o:p></FONT></FONT></SPAN></SPAN></SPAN></D=
IV>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN style=3D"mso-bookm=
ark: OLE_LINK3"><SPAN style=3D"mso-bookmark: OLE_LINK4"><o:p><FONT face=3D"=
Times New Roman" size=3D3>&nbsp;</FONT></o:p></SPAN></SPAN></DIV>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN style=3D"mso-bookm=
ark: OLE_LINK3"><SPAN style=3D"mso-bookmark: OLE_LINK4"><FONT face=3D"Times=
 New Roman" size=3D3>The website </FONT></SPAN></SPAN><A href=3D"http://www=
..promoteresearch.org/"><FONT color=3D#0000ff><FONT size=3D3><FONT face=3D"T=
imes New Roman"><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-=
bookmark: OLE_LINK4">http://www.PromoteResearch.org</SPAN></SPAN><SPAN styl=
e=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-bookmark: OLE_LINK4"></SPA=
N></SPAN></FONT></FONT></FONT></A><SPAN style=3D"mso-bookmark: OLE_LINK3"><=
SPAN style=3D"mso-bookmark: OLE_LINK4"><FONT face=3D"Times New Roman" size=
=3D3> contains more details.</FONT></SPAN></SPAN></DIV>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN style=3D"mso-bookm=
ark: OLE_LINK3"><SPAN style=3D"mso-bookmark: OLE_LINK4"><o:p><FONT face=3D"=
Times New Roman" size=3D3>&nbsp;</FONT></o:p></SPAN></SPAN></DIV>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN style=3D"mso-bookm=
ark: OLE_LINK3"><SPAN style=3D"mso-bookmark: OLE_LINK4"><FONT face=3D"Times=
 New Roman" size=3D3>Sincerely</FONT></SPAN></SPAN></DIV>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN style=3D"mso-bookm=
ark: OLE_LINK3"><SPAN style=3D"mso-bookmark: OLE_LINK4"><FONT face=3D"Times=
 New Roman" size=3D3>John Edward</FONT></SPAN></SPAN></DIV>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times New =
Roman" size=3D3>Publicity committee</FONT></DIV>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><o:p><FONT face=3D"Times=
 New Roman" size=3D3>&nbsp;</FONT></o:p></DIV>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><o:p><FONT face=3D"Times=
 New Roman" size=3D3>&nbsp;</FONT></o:p></DIV>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><o:p><FONT face=3D"Times=
 New Roman" size=3D3>&nbsp;</FONT></o:p></DIV>
<P style=3D"MARGIN: 0in 0in 0pt">&nbsp;</DIV></td></tr></table><br>=0A=0A  =
    
--0-2053431976-1233795523=:95544--


From root@core3.amsl.com  Fri Feb  6 13:30:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 9F95A3A68C5; Fri,  6 Feb 2009 13:30:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090206213001.9F95A3A68C5@core3.amsl.com>
Date: Fri,  6 Feb 2009 13:30:01 -0800 (PST)
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-seed-srtp-09.txt
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: Fri, 06 Feb 2009 21:30:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.

	Title		: The SEED Cipher Algorithm and Its Use with the Secure Real-time Transport Protocol (SRTP)
	Author(s)	: I. Property
	Filename	: draft-ietf-avt-seed-srtp-09.txt
	Pages		: 11
	Date		: 2009-2-6
	
This document describes the use of the SEED block cipher algorithm 
   in the Secure Real-time Transport Protocol (SRTP) for providing 
   confidentiality for the Real-time Transport Protocol (RTP) traffic 
   and for the control traffic for RTP, the Real-time Transport Control 
   Protocol (RTCP).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-seed-srtp-09.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-avt-seed-srtp-09.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-2-6132813.I-D@ietf.org>


--NextPart--


From seokung@kisa.or.kr  Fri Feb  6 15:01:12 2009
Return-Path: <seokung@kisa.or.kr>
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 B8BC33A67DF for <avt@core3.amsl.com>; Fri,  6 Feb 2009 15:01:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -92.02
X-Spam-Level: 
X-Spam-Status: No, score=-92.02 tagged_above=-999 required=5 tests=[AWL=0.108,  BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HTML_IMAGE_ONLY_28=1.561,  HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_ASCII0=1.5, MIME_CHARSET_FARAWAY=2.45, MIME_HTML_ONLY=1.457, USER_IN_WHITELIST=-100, WEIRD_PORT=0.001]
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 0yUvJk63qyya for <avt@core3.amsl.com>; Fri,  6 Feb 2009 15:01:11 -0800 (PST)
Received: from spam.kisa.or.kr (sniper.kisa.or.kr [211.252.150.22]) by core3.amsl.com (Postfix) with ESMTP id D29453A67CC for <avt@ietf.org>; Fri,  6 Feb 2009 15:01:10 -0800 (PST)
Received: (snipe 15664 invoked by alias); 7 Feb 2009 08:00:16 +0900
Received: from unknown (HELO ekp) (211.252.150.33) by 211.252.150.22 with SMTP; 7 Feb 2009 08:00:16 +0900
Received: from ekp (ekp [211.252.150.33]) by webmail.kisa.or.kr (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0KEO005F52LHW0@webmail.kisa.or.kr> for avt@ietf.org; Sat, 07 Feb 2009 08:00:53 +0900 (KST)
Date: Sat, 07 Feb 2009 08:00:52 +0900 (KST)
From: =?ks_c_5601-1987?B?wLG8rr/1?= <seokung@kisa.or.kr>
In-reply-to: <20090206213001.9F95A3A68C5@core3.amsl.com>
To: avt@ietf.org
Message-id: <26597953.1233961253038.JavaMail.jeus@ekp>
MIME-version: 1.0
X-Mailer: WINipMail2.5.1
Content-type: text/html; charset=ks_c_5601-1987
Content-transfer-encoding: quoted-printable
X-Priority: 3
X-UserInfo: =?ks_c_5601-1987?B?wLG8rr/1L0lUseK53bq4yKO03C+8scDTL3M=?= =?ks_c_5601-1987?B?ZW9rdW5nQGtpc2Eub3Iua3I=?=
X-UserUID: A0600
X-Identifier: 956b-11f4dd27851-8017-ekp
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-seed-srtp-09.txt
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: Fri, 06 Feb 2009 23:01:12 -0000

<html>

<head>
<META http-equiv=3DContent-Type content=3D'text/html; charset=3Dks_c_5601-1=
987'>
<title>WINiPMail Mail</title>
<style>
BODY {font-family:Arial, arial; font-size:10pt;}
P, td, li {font-family:Arial, arial; font-size:10pt; margin-top:2px;margin-=
bottom:2px;}
</style>=20
<title>WINiPMail Mail</title>
<style>
BODY {font-family:=B1=BC=B8=B2=C3=BC, arial; font-size:10pt;}
P, td, li {font-family:=B1=BC=B8=B2=C3=BC, arial; font-size:10pt; margin-to=
p:2px;margin-bottom:2px;}
</style>=20
</head>

<body bgcolor=3D"white" text=3D"black" link=3D"blue" vlink=3D"purple" alink=
=3D"red">
<p>Hi, all</p>
<p>&nbsp;</p>
<p>I&nbsp;just submitted -09 of SEED-SRTP according to Roni's comment.</p>
<p>&nbsp;</p>
<p>I just added the IANA considerations chapter.</p>
<p>&nbsp;</p>
<p>Any comments would be appreciated.</p>
<p>&nbsp;</p>
<p>BR,</p>
<p>Seokung</p>
<DIV>&nbsp;</DIV>-----=09=B8=DE=C0=CF=C0=C7 =BF=F8=B9=AE=09-----
<br><DIV style=3D"BACKGROUND: #e4e4e4; font-color: black">
<b>From: </b>Internet-Drafts@ietf.org</DIV>
<b>Sent:=09</b>Sat Feb 07 06:30:01 KST 2009
<br><b>To:  </b>i-d-announce@ietf.org
<br><b>Cc:  </b>avt@ietf.org
<br><b>Subject:  </b>[AVT] I-D ACTION:draft-ietf-avt-seed-srtp-09.txt
<br><p>A New Internet-Draft is available from the on-line Internet-Drafts <=
br>
directories.<br>
This draft is a work item of the Audio/Video Transport Working Group of the=
 IETF.<br>
<br>
=09Title=09=09: The SEED Cipher Algorithm and Its Use with the Secure Real-=
time Transport Protocol (SRTP)<br>
=09Author(s)=09: I. Property<br>
=09Filename=09: draft-ietf-avt-seed-srtp-09.txt<br>
=09Pages=09=09: 11<br>
=09Date=09=09: 2009-2-6<br>
=09<br>
This document describes the use of the SEED block cipher algorithm <br>
   in the Secure Real-time Transport Protocol (SRTP) for providing <br>
   confidentiality for the Real-time Transport Protocol (RTP) traffic <br>
   and for the control traffic for RTP, the Real-time Transport Control <br=
>
   Protocol (RTCP).<br>
<br>
A URL for this Internet-Draft is:<br>
http://www.ietf.org/internet-drafts/draft-ietf-avt-seed-srtp-09.txt<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
ftp://ftp.ietf.org/internet-drafts/<br>
<br>
Below is the data which will enable a MIME compliant mail reader<br>
implementation to automatically retrieve the ASCII version of the<br>
Internet-Draft.<br>
<BR><HR><BR>_______________________________________________<br>
Audio/Video Transport Working Group<br>
avt@ietf.org<br>
https://www.ietf.org/mailman/listinfo/avt<br>
=20


<img border=3D"0" height=3D"0" width=3D"0" src=3D"http://kisarang.kisa.or.k=
r:8880/servlet/ReadConfirmer?confirmid956b-11f4dd27851-8017-ekp"></body>
</html>
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00

From rkapoor@qualcomm.com  Sun Feb  8 19:54:34 2009
Return-Path: <rkapoor@qualcomm.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 9B9AC3A68C3 for <avt@core3.amsl.com>; Sun,  8 Feb 2009 19:54:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 rBm0gn+Q5BPE for <avt@core3.amsl.com>; Sun,  8 Feb 2009 19:54:33 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id 97BF93A688D for <avt@ietf.org>; Sun,  8 Feb 2009 19:54:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=rkapoor@qualcomm.com; q=dns/txt; s=qcdkim; t=1234151678; x=1265687678; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version:x-ironport-av; z=From:=20"Kapoor,=20Rohit"=20<rkapoor@qualcomm.com>|To: =20HE=20Bing=20<Bing.He@alcatel-sbell.com.cn>,=0D=0A=20 =20=20=20=20=20=20=20"Qiaobing.Xie@Motorola.com"=0D=0A=09 <Qiaobing.Xie@Motorola.com>,=0D=0A=20=20=20=20=20=20=20 =20"avt@ietf.org"=20<avt@ietf.org>|CC:=20"Chen=20(China =20CIV),=20Wei"=20<wchen@ti.com>,=0D=0A=20=20=20=20=20=20 =20=20XU=20Hui=20N=0D=0A=09<Hui.n.Xu@alcatel-sbell.com.cn >|Date:=20Sun,=208=20Feb=202009=2019:52:34=20-0800 |Subject:=20RE:=20When=20and=20where=20to=20specify=20dtx min=20for=20ERVC=20per=20RFC=204788|Thread-Topic:=20When =20and=20where=20to=20specify=20dtxmin=20for=20ERVC=20per =20RFC=204788|Thread-Index:=20AclSzuEFX+oTygrwQ+mFMMMt2LO gwQ19sUMAAGkMYLk=3D|Message-ID:=20<4E0B47B85518394E8D8EBD 38666348D84655E72454@NASANEXMB05.na.qualcomm.com> |References:=20<F86B91A10B14744E88408E80B8A30EF303E22580@ xmb-hkg-412.apac.cisco.com><7DD093E6-2D28-40AF-AF1B-33524 16904A8@csperkins.org><F86B91A10B14744E88408E80B8A30EF303 E22816@xmb-hkg-412.apac.cisco.com>=0D=0A=20<27E87E8B-9FC4 -4173-903E-32F9C5F975F2@csperkins.org>,<F3611473D4B99945B 70C233F2651C4D655FDFE@CNSHGSMBS04.ad4.ad.alcatel.com> |In-Reply-To:=20<F3611473D4B99945B70C233F2651C4D655FDFE@C NSHGSMBS04.ad4.ad.alcatel.com>|Accept-Language:=20en-US |Content-Language:=20en-US|X-MS-Has-Attach: |X-MS-TNEF-Correlator:|acceptlanguage:=20en-US |Content-Type:=20text/plain=3B=20charset=3D"us-ascii" |Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 300,2777,5520"=3B=20a=3D"15334715"; bh=mwrMgvhYSsKL7YD/QnD0ndv7iR9CcyWEf32f2xpAXpI=; b=lr387LmcRJKL9rtZsAMDwa6Mbt1lp1LmKR88iDzpWOonKxgfaBbG1BR8 0YWjTiie6hQfVB4g9J2+H3y36dtKoa1nNQbNZe8L4+kZ9hvzKwIGAkRmK yWntjv0ktN9RH8/aYdNI75J6d4R9r5OpeHHiz9v9h3t0PxPOoMsrHU4KV Y=;
X-IronPort-AV: E=McAfee;i="5300,2777,5520"; a="15334715"
Received: from pdmz-ns-mip.qualcomm.com (HELO ithilien.qualcomm.com) ([199.106.114.10]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Feb 2009 19:54:35 -0800
Received: from msgtransport05.qualcomm.com (msgtransport05.qualcomm.com [129.46.61.150]) by ithilien.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n193sYGt002124 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 8 Feb 2009 19:54:34 -0800
Received: from nasanexhub03.na.qualcomm.com (nasanexhub03.na.qualcomm.com [10.46.93.98]) by msgtransport05.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n193sP7P013164 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 8 Feb 2009 19:54:34 -0800
Received: from NASANEXMB05.na.qualcomm.com ([129.46.52.178]) by nasanexhub03.na.qualcomm.com ([10.46.93.98]) with mapi; Sun, 8 Feb 2009 19:54:24 -0800
From: "Kapoor, Rohit" <rkapoor@qualcomm.com>
To: HE Bing <Bing.He@alcatel-sbell.com.cn>, "Qiaobing.Xie@Motorola.com" <Qiaobing.Xie@Motorola.com>, "avt@ietf.org" <avt@ietf.org>
Date: Sun, 8 Feb 2009 19:52:34 -0800
Thread-Topic: When and where to specify dtxmin for ERVC per RFC 4788
Thread-Index: AclSzuEFX+oTygrwQ+mFMMMt2LOgwQ19sUMAAGkMYLk=
Message-ID: <4E0B47B85518394E8D8EBD38666348D84655E72454@NASANEXMB05.na.qualcomm.com>
References: <F86B91A10B14744E88408E80B8A30EF303E22580@xmb-hkg-412.apac.cisco.com><7DD093E6-2D28-40AF-AF1B-3352416904A8@csperkins.org><F86B91A10B14744E88408E80B8A30EF303E22816@xmb-hkg-412.apac.cisco.com> <27E87E8B-9FC4-4173-903E-32F9C5F975F2@csperkins.org>, <F3611473D4B99945B70C233F2651C4D655FDFE@CNSHGSMBS04.ad4.ad.alcatel.com>
In-Reply-To: <F3611473D4B99945B70C233F2651C4D655FDFE@CNSHGSMBS04.ad4.ad.alcatel.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
Cc: XU Hui N <Hui.n.Xu@alcatel-sbell.com.cn>, "Chen \(China CIV\), Wei" <wchen@ti.com>
Subject: Re: [AVT] When and where to specify dtxmin for ERVC per RFC 4788
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: Mon, 09 Feb 2009 03:54:34 -0000

Hi Bing,

The whole idea behind dtxmin is so that voice capacity gains are still main=
tained. So, even if background noise changed, the sender should not send a =
1/8th rate frame with new silence parameters more frequent than dtxmin.

Thanks,
Rohit
________________________________________
From: HE Bing [Bing.He@alcatel-sbell.com.cn]
Sent: Sunday, February 08, 2009 6:45 PM
To: Qiaobing.Xie@Motorola.com; Kapoor, Rohit; avt@ietf.org
Cc: Chen (China CIV), Wei; XU Hui N
Subject: When and where to specify dtxmin for ERVC per RFC 4788

Hello Mr Xie, Mr Kapoor and other AVT expert,

I feel hard in understanding the use of parameter dtxmin registered for med=
ia type EVRC, EVRC0, EVRC1, EVRCB, EVRCB0 and EVRCB1.

>From perspective of codec, whenever the characteristics of background noise=
 changed during silence period, an SID frame should be sent out to make pee=
r end adjust the regenerate comfort noise accordingly.

But RFC 4788 states in 6.1.
      dtxmin:  Permissible values are from 0 to 255.  Indicates the
         minimum DTX update interval in number of frames.  The RTP
         receiver may use 'dtxmin' to indicate to the RTP sender the
         minimal interval (in number of frames) between any two DTX
         updates it expects to receive from the RTP sender.

         If this parameter is not present, the default value 12, as
         specified in [8] MUST be assumed.  This parameter MUST be
         ignored if silence suppression using DTX is not used for the
         session.

Does it make real sense? If yes, could you share any valid use case?

Thanks!
He Bing


From rkapoor@qualcomm.com  Sun Feb  8 21:20:26 2009
Return-Path: <rkapoor@qualcomm.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 12D1428C132 for <avt@core3.amsl.com>; Sun,  8 Feb 2009 21:20:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 0q5WqBXES9Jq for <avt@core3.amsl.com>; Sun,  8 Feb 2009 21:20:24 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id 5DD6F28C0E7 for <avt@ietf.org>; Sun,  8 Feb 2009 21:20:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=rkapoor@qualcomm.com; q=dns/txt; s=qcdkim; t=1234156829; x=1265692829; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version:x-ironport-av; z=From:=20"Kapoor,=20Rohit"=20<rkapoor@qualcomm.com>|To: =20HE=20Bing=20<Bing.He@alcatel-sbell.com.cn>,=0D=0A=20 =20=20=20=20=20=20=20"Qiaobing.Xie@Motorola.com"=0D=0A=09 <Qiaobing.Xie@Motorola.com>,=0D=0A=20=20=20=20=20=20=20 =20"avt@ietf.org"=20<avt@ietf.org>|CC:=20"Chen=20(China =20CIV),=20Wei"=20<wchen@ti.com>,=0D=0A=20=20=20=20=20=20 =20=20XU=20Hui=20N=0D=0A=09<Hui.n.Xu@alcatel-sbell.com.cn >|Date:=20Sun,=208=20Feb=202009=2021:15:35=20-0800 |Subject:=20RE:=20When=20and=20where=20to=20specify=20dtx min=20for=20ERVC=20per=20RFC=204788|Thread-Topic:=20When =20and=20where=20to=20specify=20dtxmin=20for=20ERVC=20per =20RFC=204788|Thread-Index:=20AclSzuEFX+oTygrwQ+mFMMMt2LO gwQ19sUMAAGkMYLkAAmQdcAAAggu2|Message-ID:=20<4E0B47B85518 394E8D8EBD38666348D84655E72456@NASANEXMB05.na.qualcomm.co m>|References:=20<F86B91A10B14744E88408E80B8A30EF303E2258 0@xmb-hkg-412.apac.cisco.com><7DD093E6-2D28-40AF-AF1B-335 2416904A8@csperkins.org><F86B91A10B14744E88408E80B8A30EF3 03E22816@xmb-hkg-412.apac.cisco.com>=0D=0A=20<27E87E8B-9F C4-4173-903E-32F9C5F975F2@csperkins.org>,<F3611473D4B9994 5B70C233F2651C4D655FDFE@CNSHGSMBS04.ad4.ad.alcatel.com> =0D=0A=20<4E0B47B85518394E8D8EBD38666348D84655E72454@NASA NEXMB05.na.qualcomm.com>,<F3611473D4B99945B70C233F2651C4D 655FFFA@CNSHGSMBS04.ad4.ad.alcatel.com>|In-Reply-To:=20<F 3611473D4B99945B70C233F2651C4D655FFFA@CNSHGSMBS04.ad4.ad. alcatel.com>|Accept-Language:=20en-US|Content-Language: =20en-US|X-MS-Has-Attach:|X-MS-TNEF-Correlator: |acceptlanguage:=20en-US|Content-Type:=20text/plain=3B=20 charset=3D"us-ascii"|Content-Transfer-Encoding:=20quoted- printable|MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee =3Bi=3D"5300,2777,5520"=3B=20a=3D"15335799"; bh=Fy7sSVNJTPxo/vS1oDue/3QN+rM+SdVPy+gG9Lm+fL8=; b=O2p8VTTo4SGHpQRbV4+vgevmkbzalfuN1U7Oshuj/gBpTpGprfCI74Of f2VOArBiaINZj+eHAg7cdTPPTqr270Na76yL3LHeOjw6NpubYxGJj/Gkn O3RWwoGYU9cKcbYE2wJz9p7G2Xo+qWDflufbNNSex1O5Alvf6iCzKi5Hz c=;
X-IronPort-AV: E=McAfee;i="5300,2777,5520"; a="15335799"
Received: from pdmz-ns-mip.qualcomm.com (HELO numenor.qualcomm.com) ([199.106.114.10]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Feb 2009 21:20:29 -0800
Received: from msgtransport05.qualcomm.com (msgtransport05.qualcomm.com [129.46.61.150]) by numenor.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n195KSZt011852 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 8 Feb 2009 21:20:29 -0800
Received: from nasanexhub05.na.qualcomm.com (nasanexhub05.na.qualcomm.com [129.46.134.219]) by msgtransport05.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n195KSvJ029292 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 8 Feb 2009 21:20:28 -0800
Received: from NASANEXMB05.na.qualcomm.com ([129.46.52.178]) by nasanexhub05.na.qualcomm.com ([129.46.134.219]) with mapi; Sun, 8 Feb 2009 21:20:25 -0800
From: "Kapoor, Rohit" <rkapoor@qualcomm.com>
To: HE Bing <Bing.He@alcatel-sbell.com.cn>, "Qiaobing.Xie@Motorola.com" <Qiaobing.Xie@Motorola.com>, "avt@ietf.org" <avt@ietf.org>
Date: Sun, 8 Feb 2009 21:15:35 -0800
Thread-Topic: When and where to specify dtxmin for ERVC per RFC 4788
Thread-Index: AclSzuEFX+oTygrwQ+mFMMMt2LOgwQ19sUMAAGkMYLkAAmQdcAAAggu2
Message-ID: <4E0B47B85518394E8D8EBD38666348D84655E72456@NASANEXMB05.na.qualcomm.com>
References: <F86B91A10B14744E88408E80B8A30EF303E22580@xmb-hkg-412.apac.cisco.com><7DD093E6-2D28-40AF-AF1B-3352416904A8@csperkins.org><F86B91A10B14744E88408E80B8A30EF303E22816@xmb-hkg-412.apac.cisco.com> <27E87E8B-9FC4-4173-903E-32F9C5F975F2@csperkins.org>, <F3611473D4B99945B70C233F2651C4D655FDFE@CNSHGSMBS04.ad4.ad.alcatel.com> <4E0B47B85518394E8D8EBD38666348D84655E72454@NASANEXMB05.na.qualcomm.com>, <F3611473D4B99945B70C233F2651C4D655FFFA@CNSHGSMBS04.ad4.ad.alcatel.com>
In-Reply-To: <F3611473D4B99945B70C233F2651C4D655FFFA@CNSHGSMBS04.ad4.ad.alcatel.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
Cc: XU Hui N <Hui.n.Xu@alcatel-sbell.com.cn>, "Chen \(China CIV\), Wei" <wchen@ti.com>
Subject: Re: [AVT] When and where to specify dtxmin for ERVC per RFC 4788
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: Mon, 09 Feb 2009 05:20:26 -0000

________________________________________
From: HE Bing [Bing.He@alcatel-sbell.com.cn]
Sent: Sunday, February 08, 2009 9:11 PM
To: Kapoor, Rohit; Qiaobing.Xie@Motorola.com; avt@ietf.org
Cc: Chen (China CIV), Wei; XU Hui N
Subject: RE: When and where to specify dtxmin for ERVC per RFC 4788

Hello Rohit,

Thanks for your quick response!

What does voice capacity gains mean? I guess the purpose is that over a
aggregated transmission channel, in order to support N EVRC streams,
upper limits of bandwidth of individual stream should be controlled via
dtxmin.

<Rohit> Voice capacity gains would be lost if too many 1/8th rate frames ar=
e sent. So, one would like to control the rate of 1/8th rate transmission.

Is it right?
If yes, then EVRC codec implementation shall be aware of it and support
it or this requirement should be supported by other entity like radio
sub-system in mobile station?

<Rohit> I don't think this requirement needs to be supported by radio sub-s=
ystem. Rather, it needs to be supported by end points of the call, i.e., Vo=
IP terminals.

Thanks,
Rohit

Best regards!
He Bing

-----Original Message-----
From: Kapoor, Rohit [mailto:rkapoor@qualcomm.com]
Sent: Monday, February 09, 2009 11:53 AM
To: HE Bing; Qiaobing.Xie@Motorola.com; avt@ietf.org
Cc: Chen (China CIV), Wei; XU Hui N
Subject: RE: When and where to specify dtxmin for ERVC per RFC 4788

Hi Bing,

The whole idea behind dtxmin is so that voice capacity gains are still
maintained. So, even if background noise changed, the sender should not
send a 1/8th rate frame with new silence parameters more frequent than
dtxmin.

Thanks,
Rohit
________________________________________
From: HE Bing [Bing.He@alcatel-sbell.com.cn]
Sent: Sunday, February 08, 2009 6:45 PM
To: Qiaobing.Xie@Motorola.com; Kapoor, Rohit; avt@ietf.org
Cc: Chen (China CIV), Wei; XU Hui N
Subject: When and where to specify dtxmin for ERVC per RFC 4788

Hello Mr Xie, Mr Kapoor and other AVT expert,

I feel hard in understanding the use of parameter dtxmin registered for
media type EVRC, EVRC0, EVRC1, EVRCB, EVRCB0 and EVRCB1.

>From perspective of codec, whenever the characteristics of background
noise changed during silence period, an SID frame should be sent out to
make peer end adjust the regenerate comfort noise accordingly.

But RFC 4788 states in 6.1.
      dtxmin:  Permissible values are from 0 to 255.  Indicates the
         minimum DTX update interval in number of frames.  The RTP
         receiver may use 'dtxmin' to indicate to the RTP sender the
         minimal interval (in number of frames) between any two DTX
         updates it expects to receive from the RTP sender.

         If this parameter is not present, the default value 12, as
         specified in [8] MUST be assumed.  This parameter MUST be
         ignored if silence suppression using DTX is not used for the
         session.

Does it make real sense? If yes, could you share any valid use case?

Thanks!
He Bing


From root@core3.amsl.com  Wed Feb 11 16:45:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 4FB3A3A68B8; Wed, 11 Feb 2009 16:45:00 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090212004501.4FB3A3A68B8@core3.amsl.com>
Date: Wed, 11 Feb 2009 16:45:01 -0800 (PST)
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-ipmr-01.txt
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: Thu, 12 Feb 2009 00:45:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.

	Title		: RTP Payload Format for SPIRIT IP-MR Speech Codec Software
	Author(s)	: A. Setsko
	Filename	: draft-ietf-avt-rtp-ipmr-01.txt
	Pages		: 11
	Date		: 2009-2-10
	
This document specifies the payload format for packetization of SPIRIT IP-MR encoded speech signals into the Real-time Transport Protocol (RTP). The payload format supports transmission of multiple frames per payload, introduced redundancy for robustness against packet loss, and payload format extension for future versions compatibility.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-ipmr-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-avt-rtp-ipmr-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-2-11163055.I-D@ietf.org>


--NextPart--


From csp@csperkins.org  Fri Feb 13 09:38:48 2009
Return-Path: <csp@csperkins.org>
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 0C5353A6A1D for <avt@core3.amsl.com>; Fri, 13 Feb 2009 09:38:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 SsbjJ3XNKQGz for <avt@core3.amsl.com>; Fri, 13 Feb 2009 09:38:47 -0800 (PST)
Received: from mr1.dcs.gla.ac.uk (mr1.dcs.gla.ac.uk [130.209.249.184]) by core3.amsl.com (Postfix) with ESMTP id 15B6F3A69E3 for <avt@ietf.org>; Fri, 13 Feb 2009 09:38:47 -0800 (PST)
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:50192) by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42) id 1LY204-0006ez-QN for avt@ietf.org; Fri, 13 Feb 2009 17:38:52 +0000
Mime-Version: 1.0 (Apple Message framework v753.1)
References: <20090213144501.45E803A6B0A@core3.amsl.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C31AC42F-0694-4B91-96AC-939FA0B64539@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Fri, 13 Feb 2009 17:38:50 +0000
To: IETF AVT WG <avt@ietf.org>
X-Mailer: Apple Mail (2.753.1)
Subject: [AVT] Fwd: I-D Action:draft-perkins-avt-rapid-rtp-sync-02.txt
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: Fri, 13 Feb 2009 17:38:48 -0000

This draft is a merger between draft-perkins-avt-rapid-rtp- 
sync-01.txt and draft-schierl-avt-rtp-ntp-for-layered-codecs-00.txt.

Please send any comments to the list. We'd like this to be considered  
for adoption as an AVT working group draft.

Colin



Begin forwarded message:
> From: Internet-Drafts@ietf.org
> Date: 13 February 2009 14:45:01 GMT
> To: i-d-announce@ietf.org
> Subject: I-D Action:draft-perkins-avt-rapid-rtp-sync-02.txt
> Reply-To: internet-drafts@ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts  
> directories.
>
> 	Title           : Rapid Synchronisation of RTP Flows
> 	Author(s)       : C. Perkins, T. Schierl
> 	Filename        : draft-perkins-avt-rapid-rtp-sync-02.txt
> 	Pages           : 18
> 	Date            : 2009-02-13
>
> This memo outlines how RTP multimedia sessions are synchronised, and
> discusses how rapidly such synchronisation can occur.  We show that
> most RTP sessions can be synchronised immediately, but that the use
> of video switching multipoint conference units (MCUs) or large source
> specific multicast (SSM) groups can greatly increase the initial
> synchronisation delay.  This increase in delay can be unacceptable to
> some applications that use layered and/or multi-description codecs.
>
> This memo updates the RTP Control Protocol (RTCP) timing rules to
> reduce the initial synchronisation delay for SSM sessions.  A new
> feedback packet is defined for use with the Extended RTP Profile for
> RTCP-based Feedback (RTP/AVPF), allowing video switching MCUs to
> rapidly request resynchronisation.  Two new RTP header extensions are
> defined to allow rapid synchronisation of late joiners, and guarantee
> correct timestamp based decoding order recovery for layered codecs in
> the presence of clock skew.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-perkins-avt-rapid-rtp- 
> sync-02.txt



-- 
Colin Perkins
http://csperkins.org/




From ron.even.tlv@gmail.com  Fri Feb 13 22:38:05 2009
Return-Path: <ron.even.tlv@gmail.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 2ED633A6AB7 for <avt@core3.amsl.com>; Fri, 13 Feb 2009 22:38:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599]
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 OWL4X3QlbBbv for <avt@core3.amsl.com>; Fri, 13 Feb 2009 22:38:04 -0800 (PST)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by core3.amsl.com (Postfix) with ESMTP id 406133A67F9 for <avt@ietf.org>; Fri, 13 Feb 2009 22:38:03 -0800 (PST)
Received: by fg-out-1718.google.com with SMTP id l26so18358fgb.41 for <avt@ietf.org>; Fri, 13 Feb 2009 22:38:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language; bh=3Fj5tRrwxmpzL6RNFNEjLFPAn6mx6pxT0DyN6FkSCFo=; b=IYzUHBsC8qPfcDS+9nFxFy/3UaNDvdRKjmmujmeWr2eOCOJQ2vAjGZfDKlHBGLifsd RestW+iFzdeCZJZsqJEoKjcxEaMnp01asFZCrLQayc7LW/c0o+L60HdkoxqnhRp7jsEK Gflx2q4dn5nnDPgD9GjnPm8vseOpE7Cp7SKvA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; b=q/cfZZCKC62PzYtaD7G+x1jHwfZBJZ/4hxvMabdwho/noVOs8ClvqGMKaxYe/3Wx59 lcbVXc/iPwDSma0HowrnmklDiZHpwlWJgui3gQdnsgvjzosNUsV2o9TsSjfp+SW5ndzX QunJ7ruBr1UJKCQX+s+r5ZE9anWj3rZLd0t5Q=
Received: by 10.86.51.10 with SMTP id y10mr160419fgy.51.1234593490570; Fri, 13 Feb 2009 22:38:10 -0800 (PST)
Received: from windows8d787f9 (bzq-79-179-0-190.red.bezeqint.net [79.179.0.190]) by mx.google.com with ESMTPS id 4sm3936938fgg.45.2009.02.13.22.38.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 13 Feb 2009 22:38:10 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'IETF AVT WG'" <avt@ietf.org>
Date: Sat, 14 Feb 2009 08:36:21 +0200
Message-ID: <499666d2.0407560a.32a2.ffffd1b1@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcmOJYMHt3TiOfb2TmGl5xws/l6JYQASK30A
Content-Language: en-us
Subject: [AVT] FW: AVT - Requested sessions have been scheduled for IETF 74
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, 14 Feb 2009 06:38:05 -0000

Hi
Below is the AVT scheduled session information for SF.
Note that this is not the final agenda!!

AVT Session 1 (2 hours)
Monday, Afternoon Session I 1300-1500
Room Name: Breakout 6
----------------------------------------------
AVT Session 2 (1 hour)
Thursday, Afternoon Session II 1510-1610
Room Name: Breakout 6
----------------------------------------------

See you in SF
Roni Even
AVT co-chair



From ron.even.tlv@gmail.com  Sun Feb 15 01:03:48 2009
Return-Path: <ron.even.tlv@gmail.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 1D5603A690D for <avt@core3.amsl.com>; Sun, 15 Feb 2009 01:03:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 oz9DItW0E-QF for <avt@core3.amsl.com>; Sun, 15 Feb 2009 01:03:47 -0800 (PST)
Received: from mail-fx0-f20.google.com (mail-fx0-f20.google.com [209.85.220.20]) by core3.amsl.com (Postfix) with ESMTP id 8B3C13A6850 for <avt@ietf.org>; Sun, 15 Feb 2009 01:03:46 -0800 (PST)
Received: by fxm13 with SMTP id 13so4791405fxm.13 for <avt@ietf.org>; Sun, 15 Feb 2009 01:03:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:subject:date :message-id:mime-version:content-type:x-mailer:thread-index :content-language; bh=Vyt+Wi/w0bpF2hH5aoB6N5JnKqlLWrun6KGS7v0HXUY=; b=VBmXsRVDGxv0Llfa4a7YAyHlp9hgGgwAK9do3+T1TNpKSva/TYs01ryfuVv/LuWz9r WRdBd3jY6BXq2xHsvhBIVCjXnU7PDEOAbQrtScAtVrEGzniWCOX6qcegInBS7AWrq9bn pCmjRhjAwoSJr4IXZ+j/W2ztvVRNZOY0eo478=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; b=Ek0MEQyRn6zuMX07P/TI7rL62+DjkbzNcN1+P1oC4xwHSxtZR5AGjbZ0Jk1j1Vvow2 eyqa30TyXC/8KvRjrsLNrSy11VXEow7cxlAOMHlMTwUJzN+HhON7NT1ESK2Q8Ck1sWzJ byEAwMJNG7DlaxLvSPr5W4PzoBHO53q0H40cw=
Received: by 10.103.238.4 with SMTP id p4mr1297184mur.68.1234688633623; Sun, 15 Feb 2009 01:03:53 -0800 (PST)
Received: from windows8d787f9 (bzq-79-179-0-190.red.bezeqint.net [79.179.0.190]) by mx.google.com with ESMTPS id u26sm4607829mug.18.2009.02.15.01.03.51 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 15 Feb 2009 01:03:53 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'IETF AVT WG'" <avt@ietf.org>
Date: Sun, 15 Feb 2009 11:02:15 +0200
Message-ID: <4997da79.1ade660a.0db8.1490@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_008B_01C98F5C.DEA4B830"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcmPTBji13HCCumgSqCPG6+njnvyNw==
Content-Language: en-us
Cc: 'Elena Berlizova' <Berlizova@spiritDSP.com>, 'Slava Borilin' <Borilin@spiritdsp.com>
Subject: [AVT] Comments on IPMR payload
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: Sun, 15 Feb 2009 09:03:48 -0000

This is a multipart message in MIME format.

------=_NextPart_000_008B_01C98F5C.DEA4B830
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

I reviewed the draft I have some comments mostly editorial.

As a general comment you can look at one of the latest payload specification
approved like G.719 as an example. Look also at the layout like to document
headers and the table of contents

 

These are the specific comments

 

 

1.       The document MUST have a IANA consideration section. You can add it
as section 5, currently missing

2.       In the introduction section I suggest you add some text describing
the codec. 

3.       In section 2.1.2 when describing R "If R=0 then speech TOC is the
last section of the payload header". This sentence is not inline with the
payload format described above. TOC is not part of the header.

4.       In section 2.1.2 when describing E bit you mention teRxFrType, what
is this, there is no reference to this parameter.

5.       The last sentence of 2.1.5 you mention special flag, what is
special flag?

6.       In 2.1.7 you say that GetFrameInfo is described in [1] yet [1] does
not point to a document but to a web page where I could not see the
information.

7.       In 2.2.1 the last sentence you add a padding but A=0 in the header
so why padding.

8.       In 2.2.2 the text says that BR and CR =0 but the diagram has BR=1
and CR=2

9.       Section 2.2.3 specifies extended format but does not have any
description of when it is used or any  optional payload extension. If there
are none yet you should not specify it at this time and when you have
optional payload extension you can add it to the draft.

10.   Section 3, media subtype registration is not complete, the
registration template in defined in RFC 4288 and RFC 4855. You can look at
an example in other payload specifications.

11.   Section 3.1 change the title to  Registration of media subtype
audio/ip-mr_v2.5

12.   Is having v2.5 hints that you will need to register other versions. In
this case I suggest you add an optional payload subtype parameter version
and have the default as 2.5.

 

 

Regards

Roni Even

  _____  


------=_NextPart_000_008B_01C98F5C.DEA4B830
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<![if !supportAnnotations]>
<style id=3D"dynCom" type=3D"text/css"><!-- --></style>
<script language=3D"JavaScript"><!--
function msoCommentShow(anchor_id, com_id)
{
	if(msoBrowserCheck())=20
		{
		c =3D document.all(com_id);
		a =3D document.all(anchor_id);
		if (null !=3D c && null =3D=3D c.length && null !=3D a && null =3D=3D =
a.length)
			{
			var cw =3D c.offsetWidth;
			var ch =3D c.offsetHeight;
			var aw =3D a.offsetWidth;
			var ah =3D a.offsetHeight;
			var x  =3D a.offsetLeft;
			var y  =3D a.offsetTop;
			var el =3D a;
			while (el.tagName !=3D "BODY")=20
				{
				el =3D el.offsetParent;
				x =3D x + el.offsetLeft;
				y =3D y + el.offsetTop;
				}
			var bw =3D document.body.clientWidth;
			var bh =3D document.body.clientHeight;
			var bsl =3D document.body.scrollLeft;
			var bst =3D document.body.scrollTop;
			if (x + cw + ah / 2 > bw + bsl && x + aw - ah / 2 - cw >=3D bsl )=20
				{ c.style.left =3D x + aw - ah / 2 - cw; }
			else=20
				{ c.style.left =3D x + ah / 2; }
			if (y + ch + ah / 2 > bh + bst && y + ah / 2 - ch >=3D bst )=20
				{ c.style.top =3D y + ah / 2 - ch; }
			else=20
				{ c.style.top =3D y + ah / 2; }
			c.style.visibility =3D "visible";
}	}	}
function msoCommentHide(com_id)=20
{
	if(msoBrowserCheck())
		{
		c =3D document.all(com_id);
		if (null !=3D c && null =3D=3D c.length)
		{
		c.style.visibility =3D "hidden";
		c.style.left =3D -1000;
		c.style.top =3D -1000;
		} }=20
}
function msoBrowserCheck()
{
	ms =3D navigator.appVersion.indexOf("MSIE");
	vers =3D navigator.appVersion.substring(ms + 5, ms + 6);
	ie4 =3D (ms > 0) && (parseInt(vers) >=3D 4);
	return ie4;
}
if (msoBrowserCheck())
{
	document.styleSheets.dynCom.addRule(".msocomanchor","background: =
infobackground");
	document.styleSheets.dynCom.addRule(".msocomoff","display: none");
	document.styleSheets.dynCom.addRule(".msocomtxt","visibility: hidden");
	document.styleSheets.dynCom.addRule(".msocomtxt","position: absolute");
	document.styleSheets.dynCom.addRule(".msocomtxt","top: -1000");
	document.styleSheets.dynCom.addRule(".msocomtxt","left: -1000");
	document.styleSheets.dynCom.addRule(".msocomtxt","width: 33%");
	document.styleSheets.dynCom.addRule(".msocomtxt","background: =
infobackground");
	document.styleSheets.dynCom.addRule(".msocomtxt","color: infotext");
	document.styleSheets.dynCom.addRule(".msocomtxt","border-top: 1pt solid =
threedlightshadow");
	document.styleSheets.dynCom.addRule(".msocomtxt","border-right: 2pt =
solid threedshadow");
	document.styleSheets.dynCom.addRule(".msocomtxt","border-bottom: 2pt =
solid threedshadow");
	document.styleSheets.dynCom.addRule(".msocomtxt","border-left: 1pt =
solid threedlightshadow");
	document.styleSheets.dynCom.addRule(".msocomtxt","padding: 3pt 3pt 3pt =
3pt");
	document.styleSheets.dynCom.addRule(".msocomtxt","z-index: 100");
}
// --></script>
<![endif]>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoCommentText, li.MsoCommentText, div.MsoCommentText
	{mso-style-priority:99;
	mso-style-link:"Comment Text Char";
	margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";}
span.MsoCommentReference
	{mso-style-priority:99;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.CommentTextChar
	{mso-style-name:"Comment Text Char";
	mso-style-priority:99;
	mso-style-link:"Comment Text";
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:362443247;
	mso-list-type:hybrid;
	mso-list-template-ids:1613413642 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>Hi,<o:p></o:p></p>

<p class=3DMsoNormal>I reviewed the draft I have some comments mostly =
editorial.<o:p></o:p></p>

<p class=3DMsoNormal>As a general comment you can look at one of the =
latest
payload specification approved like G.719 as an example. Look also at =
the
layout like to document headers and the table of contents<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>These are the specific comments<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3DLTR></span>The document MUST have a =
IANA
consideration section. You can add it as section 5, currently =
missing<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3DLTR></span>In the introduction =
section I suggest
you add some text describing the codec. <o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>3.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3DLTR></span>In section 2.1.2 when =
describing R
&quot;If R=3D0 then speech TOC is the last section of the payload =
header&quot;. This
sentence is not inline with the payload format described above. TOC is =
not part
of the header.<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>4.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3DLTR></span>In section 2.1.2 when =
describing E
bit you mention teRxFrType, what is this, there is no reference to this
parameter.<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>5.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3DLTR></span>The last sentence of =
2.1.5 you
mention special flag, what is special flag?<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>6.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3DLTR></span>In 2.1.7 you say that =
GetFrameInfo
is described in [1] yet [1] does not point to a document but to a web =
page
where I could not see the information.<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>7.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3DLTR></span>In 2.2.1 the last =
sentence you add
a padding but A=3D0 in the header so why padding.<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>8.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3DLTR></span>In 2.2.2 the text says =
that BR and
CR =3D0 but the diagram has BR=3D1 and CR=3D2<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>9.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3DLTR></span>Section 2.2.3 specifies =
extended
format but does not have any description of when it is used or any&nbsp;
optional payload extension. If there are none yet you should not specify =
it at
this time and when you have optional payload extension you can add it to =
the draft.<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>10.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;
</span></span><![endif]><span dir=3DLTR></span>Section 3, media subtype
registration is not complete, the registration template in defined in =
RFC 4288
and RFC 4855. You can look at an example in other payload =
specifications.<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>11.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;
</span></span><![endif]><span dir=3DLTR></span>Section 3.1 change the =
title to &nbsp;Registration
of media subtype audio/ip-mr_v2.5<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>12.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;
</span></span><![endif]><span dir=3DLTR></span>Is having v2.5 hints that =
you will
need to register other versions. In this case I suggest you add an =
optional
payload subtype parameter version and have the default as =
2.5.<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Regards<o:p></o:p></p>

<p class=3DMsoNormal>Roni Even<o:p></o:p></p>

</div>

<div style=3D'mso-element:comment-list'><![if !supportAnnotations]>

<hr class=3Dmsocomoff align=3Dleft size=3D1 width=3D"33%">

<![endif]></div>

</body>

</html>

------=_NextPart_000_008B_01C98F5C.DEA4B830--


From ron.even.tlv@gmail.com  Mon Feb 16 22:26:50 2009
Return-Path: <ron.even.tlv@gmail.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 C66AC3A6861 for <avt@core3.amsl.com>; Mon, 16 Feb 2009 22:26:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 UiP1YuHqxVSo for <avt@core3.amsl.com>; Mon, 16 Feb 2009 22:26:50 -0800 (PST)
Received: from mail-fx0-f20.google.com (mail-fx0-f20.google.com [209.85.220.20]) by core3.amsl.com (Postfix) with ESMTP id A76CE3A67EC for <avt@ietf.org>; Mon, 16 Feb 2009 22:26:49 -0800 (PST)
Received: by fxm13 with SMTP id 13so6494767fxm.13 for <avt@ietf.org>; Mon, 16 Feb 2009 22:26:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:subject:date :message-id:mime-version:content-type:x-mailer:thread-index :content-language; bh=ksNSaU8o44vU7ROc3nY2jbIuun0glccplL4EZzdQ7+s=; b=W6rvWRxRTcuWnBxYISv6N71bY78+ENeRTHzM6ABtGsVRxMv1ZhAH9JbUSkSaCzGBj/ o3pHnEgF/Uk6YM95SHu0kz3X8paI9dRtQeRs63O1e2R2djrHmZShhfexi1aXkolTK0GM c3w2z0Y0iBeUtGt7sg1y+lQ9xKTue4W9SR02c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; b=iMJqv6XSecqZoVAFuIMEoBxkVJA8oxfg7tcecnLnYLfgF7CmpDvrzEV87A6JkV7mz2 ZD1tC6OQcDBgTN/GvObl1qKZsqD4rc6l+BHLZP/xcl/t6Umy/fWhT16oL39+z/kk17a1 QNN8eir2/+Vqyn98+xtwjzGpWvG9hA8mHGSIA=
Received: by 10.103.92.8 with SMTP id u8mr1463488mul.12.1234852018528; Mon, 16 Feb 2009 22:26:58 -0800 (PST)
Received: from windows8d787f9 (bzq-79-176-141-57.red.bezeqint.net [79.176.141.57]) by mx.google.com with ESMTPS id j10sm350562mue.56.2009.02.16.22.26.48 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 16 Feb 2009 22:26:58 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Ver Steeg, Bill'" <VersteB@cisco.com>, "'Orit Levin'" <oritl@microsoft.com>, "'VAN CAENEGEM Tom'" <Tom.Van_Caenegem@alcatel-lucent.be>, <oran@cisco.com>, <abegen@cisco.com>, "'Peilin YANG'" <yangpeilin@huawei.com>
Date: Tue, 17 Feb 2009 08:25:05 +0200
Message-ID: <499a58b2.0aa1660a.24ce.ffffc36e@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_002B_01C990D9.42FADE90"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcmQyHjcjWlgubC1Sh2jzSR4f49cjQ==
Content-Language: en-us
Cc: 'IETF AVT WG' <avt@ietf.org>
Subject: [AVT] Rapid synchronization / RTP Burst / RTCP burst
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, 17 Feb 2009 06:26:50 -0000

This is a multipart message in MIME format.

------=_NextPart_000_002B_01C990D9.42FADE90
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

At the Minneapolis the summary was that the parties will try to progress the
work before SF meeting.

The only thing I saw on the AVT list is a new draft from Peilin, so now
there are three drafts.

Is there any other progress or are you all waiting for SF to discuss
progress.

The deadline for contributions is March 2nd for new drafts and March 9th for
the rest.

 

Regards

Roni Even

AVT co-chair


------=_NextPart_000_002B_01C990D9.42FADE90
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>Hi,<o:p></o:p></p>

<p class=3DMsoNormal>At the Minneapolis the summary was that the parties =
will try
to progress the work before SF meeting.<o:p></o:p></p>

<p class=3DMsoNormal>The only thing I saw on the AVT list is a new draft =
from Peilin,
so now there are three drafts.<o:p></o:p></p>

<p class=3DMsoNormal>Is there any other progress or are you all waiting =
for SF to
discuss progress.<o:p></o:p></p>

<p class=3DMsoNormal>The deadline for contributions is March =
2<sup>nd</sup> for
new drafts and March 9<sup>th</sup> for the rest.<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Regards<o:p></o:p></p>

<p class=3DMsoNormal>Roni Even<o:p></o:p></p>

<p class=3DMsoNormal>AVT co-chair<o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_002B_01C990D9.42FADE90--


From Tom.Van_Caenegem@alcatel-lucent.be  Tue Feb 17 00:54:10 2009
Return-Path: <Tom.Van_Caenegem@alcatel-lucent.be>
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 7D4803A6C00 for <avt@core3.amsl.com>; Tue, 17 Feb 2009 00:54:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.248
X-Spam-Level: 
X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 xlvjSL4ugm-B for <avt@core3.amsl.com>; Tue, 17 Feb 2009 00:54:09 -0800 (PST)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27]) by core3.amsl.com (Postfix) with ESMTP id 130CA3A68B2 for <avt@ietf.org>; Tue, 17 Feb 2009 00:54:08 -0800 (PST)
Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.dc-m.alcatel-lucent.com [155.132.6.76]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n1H8rovQ025418;  Tue, 17 Feb 2009 09:53:51 +0100
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.56]) by FRVELSBHS04.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Tue, 17 Feb 2009 09:53:49 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C990DD.4074A84B"
Date: Tue, 17 Feb 2009 09:53:46 +0100
Message-ID: <238382595265324EA50F6134BB42DCAF034F7343@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <499a58b2.0aa1660a.24ce.ffffc36e@mx.google.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Rapid synchronization / RTP Burst / RTCP burst
Thread-Index: AcmQyHjcjWlgubC1Sh2jzSR4f49cjQAE2akQ
References: <499a58b2.0aa1660a.24ce.ffffc36e@mx.google.com>
From: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>
To: "Roni Even" <ron.even.tlv@gmail.com>, "Ver Steeg, Bill" <VersteB@cisco.com>, "Orit Levin" <oritl@microsoft.com>, <oran@cisco.com>, <abegen@cisco.com>, "Peilin YANG" <yangpeilin@huawei.com>
X-OriginalArrivalTime: 17 Feb 2009 08:53:49.0781 (UTC) FILETIME=[404E3850:01C990DD]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Cc: IETF AVT WG <avt@ietf.org>
Subject: Re: [AVT] Rapid synchronization / RTP Burst / RTCP burst
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, 17 Feb 2009 08:54:10 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C990DD.4074A84B
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Dear Roni,
=20
we (that is the authors of the two drafts on "Rapid MC synchronisation")
are in the process of  delivering a new draft that combines some of the
elements in both existing drafts and takes into account the comments
from the ad-hoc meeting. Our ambition is indeed to submit this new draft
before the SF meeting deadline. We decided to go for a two-step
approach, where in the 1st step we sort out the differences among the
two drafts that have already been presented and discussed within the
IETF community, and in the second step (starting with the IETF SF
meeting) , we want to discuss with Peilin and all other interested
people on the new features proposed in his draft on this topic.
=20
Kind Regards,
Tom

________________________________

From: Roni Even [mailto:ron.even.tlv@gmail.com]=20
Sent: dinsdag 17 februari 2009 7:25
To: 'Ver Steeg, Bill'; 'Orit Levin'; VAN CAENEGEM Tom; oran@cisco.com;
abegen@cisco.com; 'Peilin YANG'
Cc: 'IETF AVT WG'
Subject: Rapid synchronization / RTP Burst / RTCP burst



Hi,

At the Minneapolis the summary was that the parties will try to progress
the work before SF meeting.

The only thing I saw on the AVT list is a new draft from Peilin, so now
there are three drafts.

Is there any other progress or are you all waiting for SF to discuss
progress.

The deadline for contributions is March 2nd for new drafts and March 9th
for the rest.

=20

Regards

Roni Even

AVT co-chair


------_=_NextPart_001_01C990DD.4074A84B
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3492" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Calibri","sans-serif"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Calibri","sans-serif"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Calibri","sans-serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: =
personal-compose
}
.MsoChpDefault {
	mso-style-type: export-only
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D058584308-17022009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Dear Roni,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D058584308-17022009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D058584308-17022009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>we (that is the authors of the two drafts on =
"Rapid MC=20
synchronisation") are in the process of&nbsp; delivering a new draft =
that=20
combines some of the elements in both existing drafts and takes into =
account the=20
comments from the ad-hoc meeting. Our ambition is indeed to&nbsp;submit =
this new=20
draft before the SF meeting deadline. We decided to go for a two-step =
approach,=20
where in the 1st step we sort out the differences among the two drafts =
that have=20
already been presented and discussed within the IETF community, and in =
the=20
second step (starting with the IETF SF meeting) , we&nbsp;want to =
discuss with=20
Peilin and all other interested people on the new features proposed in =
his draft=20
on this topic.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D058584308-17022009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D058584308-17022009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Kind Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D058584308-17022009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Tom</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Roni Even =
[mailto:ron.even.tlv@gmail.com]=20
<BR><B>Sent:</B> dinsdag 17 februari 2009 7:25<BR><B>To:</B> 'Ver Steeg, =
Bill';=20
'Orit Levin'; VAN CAENEGEM Tom; oran@cisco.com; abegen@cisco.com; =
'Peilin=20
YANG'<BR><B>Cc:</B> 'IETF AVT WG'<BR><B>Subject:</B> Rapid =
synchronization / RTP=20
Burst / RTCP burst<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal>Hi,<o:p></o:p></P>
<P class=3DMsoNormal>At the Minneapolis the summary was that the parties =
will try=20
to progress the work before SF meeting.<o:p></o:p></P>
<P class=3DMsoNormal>The only thing I saw on the AVT list is a new draft =
from=20
Peilin, so now there are three drafts.<o:p></o:p></P>
<P class=3DMsoNormal>Is there any other progress or are you all waiting =
for SF to=20
discuss progress.<o:p></o:p></P>
<P class=3DMsoNormal>The deadline for contributions is March =
2<SUP>nd</SUP> for=20
new drafts and March 9<SUP>th</SUP> for the rest.<o:p></o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal>Regards<o:p></o:p></P>
<P class=3DMsoNormal>Roni Even<o:p></o:p></P>
<P class=3DMsoNormal>AVT co-chair<o:p></o:p></P></DIV></BODY></HTML>

------_=_NextPart_001_01C990DD.4074A84B--

From yangpeilin@huawei.com  Tue Feb 17 01:30:27 2009
Return-Path: <yangpeilin@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 8B48228C128 for <avt@core3.amsl.com>; Tue, 17 Feb 2009 01:30:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.19
X-Spam-Level: 
X-Spam-Status: No, score=0.19 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45]
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 E8c+UZKlhBZP for <avt@core3.amsl.com>; Tue, 17 Feb 2009 01:30:26 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 8BF2928C114 for <avt@ietf.org>; Tue, 17 Feb 2009 01:30:26 -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 <0KF700DNAEEYDX@szxga03-in.huawei.com> for avt@ietf.org; Tue, 17 Feb 2009 17:30:35 +0800 (CST)
Received: from huawei.com ([172.17.1.31]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KF700ALIEEYYD@szxga03-in.huawei.com> for avt@ietf.org; Tue, 17 Feb 2009 17:30:34 +0800 (CST)
Received: from [172.24.1.33] (Forwarded-For: [10.164.12.15]) by szxmc03-in.huawei.com (mshttpd); Tue, 17 Feb 2009 17:30:34 +0800
Date: Tue, 17 Feb 2009 17:30:34 +0800
From: Peilin YANG <yangpeilin@huawei.com>
In-reply-to: <238382595265324EA50F6134BB42DCAF034F7343@FRVELSMBS22.ad2.ad.alcatel.com>
To: VAN CAENEGEM Tom <Tom.Van_Caenegem@alcatel-lucent.be>
Message-id: <fba0807670d9b.70d9bfba08076@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.14 (built Aug  8 2006)
Content-type: text/plain; charset=gb2312
Content-language: zh-CN
Content-transfer-encoding: quoted-printable
Content-disposition: inline
X-Accept-Language: zh-CN
Priority: normal
References: <499a58b2.0aa1660a.24ce.ffffc36e@mx.google.com> <238382595265324EA50F6134BB42DCAF034F7343@FRVELSMBS22.ad2.ad.alcatel.com>
Cc: oran@cisco.com, IETF AVT WG <avt@ietf.org>
Subject: Re: [AVT] Rapid synchronization / RTP Burst / RTCP burst
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, 17 Feb 2009 09:30:27 -0000

Dear Tom=A3=AC

I am very glad to discuss with you and all other interested guys on this =
topic=2E

Best regards=2C

Peilin
*************************************************************************=
*****************
 This email and its attachments contain confidential information from HUA=
WEI=2C which is intended only for the person or entity whose address is l=
isted above=2E Any use of the information contained here in any way (incl=
uding=2C but not limited to=2C total or partial disclosure=2C reproductio=
n=2C or dissemination) by persons other than the intended recipient(s) is=
 prohibited=2E If you receive this email in error=2C please notify the se=
nder by phone or email
 immediately and delete it!
 ************************************************************************=
*****************

----- =D4=AD=D3=CA=BC=FE -----
=B7=A2=BC=FE=C8=CB=3A VAN CAENEGEM Tom =3CTom=2EVan=5FCaenegem=40alcatel-=
lucent=2Ebe=3E
=C8=D5=C6=DA=3A =D0=C7=C6=DA=B6=FE=2C =B6=FE=D4=C2 17=C8=D5=2C 2009 =CF=C2=
=CE=E75=3A23
=D6=F7=CC=E2=3A RE=3A Rapid synchronization / RTP Burst / RTCP burst
=CA=D5=BC=FE=C8=CB=3A Roni Even =3Cron=2Eeven=2Etlv=40gmail=2Ecom=3E=2C =22=
Ver Steeg=2C Bill=22 =3CVersteB=40cisco=2Ecom=3E=2C Orit Levin =3Coritl=40=
microsoft=2Ecom=3E=2C oran=40cisco=2Ecom=2C abegen=40cisco=2Ecom=2C Peili=
n YANG =3Cyangpeilin=40huawei=2Ecom=3E
=B3=AD=CB=CD=3A IETF AVT WG =3Cavt=40ietf=2Eorg=3E

=3E Dear Roni=2C
=3E =

=3E we (that is the authors of the two drafts on =22Rapid MC =

=3E synchronisation=22)are in the process of  delivering a new draft =

=3E that combines some of the
=3E elements in both existing drafts and takes into account the comments
=3E from the ad-hoc meeting=2E Our ambition is indeed to submit this new =

=3E draftbefore the SF meeting deadline=2E We decided to go for a two-ste=
p
=3E approach=2C where in the 1st step we sort out the differences among t=
he
=3E two drafts that have already been presented and discussed within the
=3E IETF community=2C and in the second step (starting with the IETF SF
=3E meeting) =2C we want to discuss with Peilin and all other interested
=3E people on the new features proposed in his draft on this topic=2E
=3E =

=3E Kind Regards=2C
=3E Tom
=3E =

=3E =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F
=3E =

=3E From=3A Roni Even =5Bmailto=3Aron=2Eeven=2Etlv=40gmail=2Ecom=5D =

=3E Sent=3A dinsdag 17 februari 2009 7=3A25
=3E To=3A =27Ver Steeg=2C Bill=27=3B =27Orit Levin=27=3B VAN CAENEGEM Tom=
=3B oran=40cisco=2Ecom=3B
=3E abegen=40cisco=2Ecom=3B =27Peilin YANG=27
=3E Cc=3A =27IETF AVT WG=27
=3E Subject=3A Rapid synchronization / RTP Burst / RTCP burst
=3E =

=3E =

=3E =

=3E Hi=2C
=3E =

=3E At the Minneapolis the summary was that the parties will try to =

=3E progressthe work before SF meeting=2E
=3E =

=3E The only thing I saw on the AVT list is a new draft from Peilin=2C =

=3E so now
=3E there are three drafts=2E
=3E =

=3E Is there any other progress or are you all waiting for SF to discuss
=3E progress=2E
=3E =

=3E The deadline for contributions is March 2nd for new drafts and =

=3E March 9th
=3E for the rest=2E
=3E =

=3E =

=3E =

=3E Regards
=3E =

=3E Roni Even
=3E =

=3E AVT co-chair
=3E =

=3E 

From ron.even.tlv@gmail.com  Tue Feb 17 01:36:40 2009
Return-Path: <ron.even.tlv@gmail.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 EB5C528C12A for <avt@core3.amsl.com>; Tue, 17 Feb 2009 01:36:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 T0WNdgus0vQQ for <avt@core3.amsl.com>; Tue, 17 Feb 2009 01:36:39 -0800 (PST)
Received: from mail-fx0-f20.google.com (mail-fx0-f20.google.com [209.85.220.20]) by core3.amsl.com (Postfix) with ESMTP id 490093A67BD for <avt@ietf.org>; Tue, 17 Feb 2009 01:36:39 -0800 (PST)
Received: by fxm13 with SMTP id 13so6567494fxm.13 for <avt@ietf.org>; Tue, 17 Feb 2009 01:36:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references :in-reply-to:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=ferlTeHLi0O6846mYT2dfAEiRxTHQsc0ptuYVJVscwE=; b=qV7VFBOTK4TBg223xl+L20roUyCqfCjwvf3gwgZnU12VbsbI5zW2uJtkPS30m47J56 AHGwlQc7dSRvxZlbN+hz46Ccjo5m4hTa1dZ0uCIZNsd2y/03OLPFPF070e5a4z4aaR0Z onyFHbWae9zNqiFMIkMNfaOt6h/zFQjkVvRz0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:x-mailer:thread-index:content-language; b=jMVJPVMDDBFzAK2l8AoaSLlMrKBNnNRWtAQjPzC5OS2J5rf8UyRHG9fU7NPtAbVDAb pIRkbVGU1XtKuzuWitfwpi565g2u+uN+EpslixoSqrrAy4BOCQnOq+sAzjZS93pf+G5k zbLMeiw3q79ddr0ubtkgLX8lAFbD/IAUKmd2A=
Received: by 10.103.49.12 with SMTP id b12mr3493581muk.81.1234863408961; Tue, 17 Feb 2009 01:36:48 -0800 (PST)
Received: from windows8d787f9 (bzq-79-176-141-57.red.bezeqint.net [79.176.141.57]) by mx.google.com with ESMTPS id j10sm20191muh.1.2009.02.17.01.36.46 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 17 Feb 2009 01:36:48 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'VAN CAENEGEM Tom'" <Tom.Van_Caenegem@alcatel-lucent.be>, "'Ver Steeg, Bill'" <VersteB@cisco.com>, "'Orit Levin'" <oritl@microsoft.com>, <oran@cisco.com>, <abegen@cisco.com>, "'Peilin YANG'" <yangpeilin@huawei.com>
References: <499a58b2.0aa1660a.24ce.ffffc36e@mx.google.com> <238382595265324EA50F6134BB42DCAF034F7343@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <238382595265324EA50F6134BB42DCAF034F7343@FRVELSMBS22.ad2.ad.alcatel.com>
Date: Tue, 17 Feb 2009 11:35:03 +0200
Message-ID: <499a8530.0aec660a.29ef.0b97@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_006B_01C990F3.C9431840"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcmQyHjcjWlgubC1Sh2jzSR4f49cjQAE2akQAAE/ykA=
Content-Language: en-us
Cc: 'IETF AVT WG' <avt@ietf.org>
Subject: Re: [AVT] Rapid synchronization / RTP Burst / RTCP burst
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, 17 Feb 2009 09:36:41 -0000

This is a multipart message in MIME format.

------=_NextPart_000_006B_01C990F3.C9431840
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

These are good news, please try to include Peilin in your discussion,
hopefully we will manage to have an ad-hoc meeting in SF to get further
progress. 

 

I think it will be good to include the input from Peilin document as early
as possible in order to expedite the work. 

 

The summary of the ad-hoc meeting that was on the AVT list had a couple of
discussion points. Are there any resolution, my view is that if you post
this to the list early it will help with progressing the work.

 

About the first discussion point I had some other feedback suggesting that
RTCP may be used from retransmission server   to send information that was
previously in the RTP stream if there is no obvious way to fit it in the
retransmission stream.

 

Regards

Roni Even

 

From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be] 
Sent: Tuesday, February 17, 2009 10:54 AM
To: Roni Even; Ver Steeg, Bill; Orit Levin; oran@cisco.com;
abegen@cisco.com; Peilin YANG
Cc: IETF AVT WG
Subject: RE: Rapid synchronization / RTP Burst / RTCP burst

 

Dear Roni,

 

we (that is the authors of the two drafts on "Rapid MC synchronisation") are
in the process of  delivering a new draft that combines some of the elements
in both existing drafts and takes into account the comments from the ad-hoc
meeting. Our ambition is indeed to submit this new draft before the SF
meeting deadline. We decided to go for a two-step approach, where in the 1st
step we sort out the differences among the two drafts that have already been
presented and discussed within the IETF community, and in the second step
(starting with the IETF SF meeting) , we want to discuss with Peilin and all
other interested people on the new features proposed in his draft on this
topic.

 

Kind Regards,

Tom

 

  _____  

From: Roni Even [mailto:ron.even.tlv@gmail.com] 
Sent: dinsdag 17 februari 2009 7:25
To: 'Ver Steeg, Bill'; 'Orit Levin'; VAN CAENEGEM Tom; oran@cisco.com;
abegen@cisco.com; 'Peilin YANG'
Cc: 'IETF AVT WG'
Subject: Rapid synchronization / RTP Burst / RTCP burst

Hi,

At the Minneapolis the summary was that the parties will try to progress the
work before SF meeting.

The only thing I saw on the AVT list is a new draft from Peilin, so now
there are three drafts.

Is there any other progress or are you all waiting for SF to discuss
progress.

The deadline for contributions is March 2nd for new drafts and March 9th for
the rest.

 

Regards

Roni Even

AVT co-chair


------=_NextPart_000_006B_01C990F3.C9431840
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>These are good news, =
please try
to include Peilin in your discussion, hopefully we will manage to have =
an ad-hoc
meeting in SF to get further progress. <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>I think it will be =
good to
include the input from Peilin document as early as possible in order to =
expedite
the work. <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>The summary of the =
ad-hoc
meeting that was on the AVT list had a couple of discussion points. Are =
there
any resolution, my view is that if you post this to the list early it =
will help
with progressing the work.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>About the first =
discussion point
I had some other feedback suggesting that RTCP may be used from =
retransmission
server &nbsp;&nbsp;to send information that was previously in the RTP =
stream if
there is no obvious way to fit it in the retransmission =
stream.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Regards<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>Roni =
Even<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> VAN =
CAENEGEM Tom
[mailto:Tom.Van_Caenegem@alcatel-lucent.be] <br>
<b>Sent:</b> Tuesday, February 17, 2009 10:54 AM<br>
<b>To:</b> Roni Even; Ver Steeg, Bill; Orit Levin; oran@cisco.com;
abegen@cisco.com; Peilin YANG<br>
<b>Cc:</b> IETF AVT WG<br>
<b>Subject:</b> RE: Rapid synchronization / RTP Burst / RTCP =
burst<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Dear Roni,</span><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times =
New Roman","serif"'>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>we (that is the authors of the two drafts on &quot;Rapid MC
synchronisation&quot;) are in the process of&nbsp; delivering a new =
draft that
combines some of the elements in both existing drafts and takes into =
account
the comments from the ad-hoc meeting. Our ambition is indeed =
to&nbsp;submit
this new draft before the SF meeting deadline. We decided to go for a =
two-step
approach, where in the 1st step we sort out the differences among the =
two
drafts that have already been presented and discussed within the IETF
community, and in the second step (starting with the IETF SF meeting) ,
we&nbsp;want to discuss with Peilin and all other interested people on =
the new
features proposed in his draft on this topic.</span><span =
style=3D'font-size:
12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times =
New Roman","serif"'>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Kind Regards,</span><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Tom</span><span style=3D'font-size:12.0pt;font-family:"Times =
New Roman","serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times =
New Roman","serif"'><o:p>&nbsp;</o:p></span></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><span =
style=3D'font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span =
style=3D'font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> Roni Even =
[mailto:ron.even.tlv@gmail.com] <br>
<b>Sent:</b> dinsdag 17 februari 2009 7:25<br>
<b>To:</b> 'Ver Steeg, Bill'; 'Orit Levin'; VAN CAENEGEM Tom; =
oran@cisco.com;
abegen@cisco.com; 'Peilin YANG'<br>
<b>Cc:</b> 'IETF AVT WG'<br>
<b>Subject:</b> Rapid synchronization / RTP Burst / RTCP =
burst</span><span
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal>Hi,<o:p></o:p></p>

<p class=3DMsoNormal>At the Minneapolis the summary was that the parties =
will try
to progress the work before SF meeting.<o:p></o:p></p>

<p class=3DMsoNormal>The only thing I saw on the AVT list is a new draft =
from
Peilin, so now there are three drafts.<o:p></o:p></p>

<p class=3DMsoNormal>Is there any other progress or are you all waiting =
for SF to
discuss progress.<o:p></o:p></p>

<p class=3DMsoNormal>The deadline for contributions is March =
2<sup>nd</sup> for
new drafts and March 9<sup>th</sup> for the rest.<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Regards<o:p></o:p></p>

<p class=3DMsoNormal>Roni Even<o:p></o:p></p>

<p class=3DMsoNormal>AVT co-chair<o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_006B_01C990F3.C9431840--


From ingemar.s.johansson@ericsson.com  Tue Feb 17 01:56:15 2009
Return-Path: <ingemar.s.johansson@ericsson.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 9F98E3A6A99 for <avt@core3.amsl.com>; Tue, 17 Feb 2009 01:56:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 deadRxOSpD0S for <avt@core3.amsl.com>; Tue, 17 Feb 2009 01:56:14 -0800 (PST)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 3C0F03A6A4C for <avt@ietf.org>; Tue, 17 Feb 2009 01:56:14 -0800 (PST)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 4E9B120B8F; Tue, 17 Feb 2009 10:56:17 +0100 (CET)
X-AuditID: c1b4fb3e-af0c1bb000001315-ae-499a89c03576
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.253.125]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 07E8B207BF; Tue, 17 Feb 2009 10:56:17 +0100 (CET)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Tue, 17 Feb 2009 10:56:16 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 17 Feb 2009 10:56:15 +0100
Message-ID: <130EBB38279E9847BAAAE0B8F9905F8C658133@esealmw109.eemea.ericsson.se>
In-Reply-To: <mailman.28.1234555202.2046.avt@ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D Action:draft-perkins-avt-rapid-rtp-sync-02.txt
Thread-Index: AcmOFbYIYfQP323yTYix+zkPoHGsIQCyNieA
References: <mailman.28.1234555202.2046.avt@ietf.org>
From: "Ingemar Johansson S" <ingemar.s.johansson@ericsson.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 17 Feb 2009 09:56:16.0582 (UTC) FILETIME=[F992AE60:01C990E5]
X-Brightmail-Tracker: AAAAAA==
Cc: thomas.schierl@hhi.fraunhofer.de, csp@csperkins.org
Subject: Re: [AVT] I-D Action:draft-perkins-avt-rapid-rtp-sync-02.txt
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, 17 Feb 2009 09:56:15 -0000

Hi

I have read the draft and I believe it is a good collection of
solutions.=20

Medium comments:=20
Section 4.2, page 13. "The frequency of inserting NTP header extensions
in the RTP flows is up to the sender". It is here perhaps worth to
consider the possible impact on header compression algorithms such as
RoHC. Depending on profile used the toggling of the X bit may increase
the packet overhead by 3-5 bytes for a number of packets. This is likely
no big issue for transmission of video but may have an impact for e.g
audio. Anyway, this is not a very impotant issue but I just wanted to
bring this up.

Minor comments(nits):
Section 3
  "repid" -> "rapid"

Section 3.1
  "constraints of RTCP the early..." -> "constraints of the RTCP
early..."

Section 4.1=20
  "are not send.." -> "are not sent.."

  "If synchronously in all flows inserting header extensions as defined
in..." -> "If header extensions are synchronously inserted in all flows
as defined in..."=20

  "trasnported" -> "transported"

Section 4.2=20
   last paragraph: "Such an NTP header extension insertion is only...."
Confusing, is something missing in the end of the sentence?

Regards
Ingemar


> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On=20
> Behalf Of avt-request@ietf.org
> Sent: den 13 februari 2009 21:00
> To: avt@ietf.org
> Subject: avt Digest, Vol 58, Issue 8
>=20
> Send avt mailing list submissions to
> 	avt@ietf.org
>=20
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://www.ietf.org/mailman/listinfo/avt
> or, via email, send a message with subject or body 'help' to
> 	avt-request@ietf.org
>=20
> You can reach the person managing the list at
> 	avt-owner@ietf.org
>=20
> When replying, please edit your Subject line so it is more=20
> specific than "Re: Contents of avt digest..."
>=20
>=20
> Today's Topics:
>=20
>    1. Fwd: I-D Action:draft-perkins-avt-rapid-rtp-sync-02.txt
>       (Colin Perkins)
>=20
>=20
> ----------------------------------------------------------------------
>=20
> Message: 1
> Date: Fri, 13 Feb 2009 17:38:50 +0000
> From: Colin Perkins <csp@csperkins.org>
> Subject: [AVT] Fwd: I-D Action:draft-perkins-avt-rapid-rtp-sync-02.txt
> To: IETF AVT WG <avt@ietf.org>
> Message-ID: <C31AC42F-0694-4B91-96AC-939FA0B64539@csperkins.org>
> Content-Type: text/plain; charset=3DUS-ASCII; delsp=3Dyes; =
format=3Dflowed
>=20
> This draft is a merger between draft-perkins-avt-rapid-rtp-=20
> sync-01.txt and draft-schierl-avt-rtp-ntp-for-layered-codecs-00.txt.
>=20
> Please send any comments to the list. We'd like this to be=20
> considered for adoption as an AVT working group draft.
>=20
> Colin
>=20
>=20
>=20
> Begin forwarded message:
> > From: Internet-Drafts@ietf.org
> > Date: 13 February 2009 14:45:01 GMT
> > To: i-d-announce@ietf.org
> > Subject: I-D Action:draft-perkins-avt-rapid-rtp-sync-02.txt
> > Reply-To: internet-drafts@ietf.org
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts=20
> > directories.
> >
> > 	Title           : Rapid Synchronisation of RTP Flows
> > 	Author(s)       : C. Perkins, T. Schierl
> > 	Filename        : draft-perkins-avt-rapid-rtp-sync-02.txt
> > 	Pages           : 18
> > 	Date            : 2009-02-13
> >
> > This memo outlines how RTP multimedia sessions are=20
> synchronised, and=20
> > discusses how rapidly such synchronisation can occur.  We show that=20
> > most RTP sessions can be synchronised immediately, but that=20
> the use of=20
> > video switching multipoint conference units (MCUs) or large source=20
> > specific multicast (SSM) groups can greatly increase the initial=20
> > synchronisation delay.  This increase in delay can be=20
> unacceptable to=20
> > some applications that use layered and/or multi-description codecs.
> >
> > This memo updates the RTP Control Protocol (RTCP) timing rules to=20
> > reduce the initial synchronisation delay for SSM sessions.  A new=20
> > feedback packet is defined for use with the Extended RTP=20
> Profile for=20
> > RTCP-based Feedback (RTP/AVPF), allowing video switching MCUs to=20
> > rapidly request resynchronisation.  Two new RTP header=20
> extensions are=20
> > defined to allow rapid synchronisation of late joiners, and=20
> guarantee=20
> > correct timestamp based decoding order recovery for layered=20
> codecs in=20
> > the presence of clock skew.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-perkins-avt-rapid-rtp-
> > sync-02.txt
>=20
>=20
>=20
> --=20
> Colin Perkins
> http://csperkins.org/
>=20
>=20
>=20
>=20
>=20
> ------------------------------
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>=20
>=20
> End of avt Digest, Vol 58, Issue 8
> **********************************
>=20

From gerard.babonneau@orange-ftgroup.com  Tue Feb 17 01:56:41 2009
Return-Path: <gerard.babonneau@orange-ftgroup.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 4CE1528C131 for <avt@core3.amsl.com>; Tue, 17 Feb 2009 01:56:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
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 cmkLmkI93p0B for <avt@core3.amsl.com>; Tue, 17 Feb 2009 01:56:40 -0800 (PST)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by core3.amsl.com (Postfix) with ESMTP id 939833A65A5 for <avt@ietf.org>; Tue, 17 Feb 2009 01:56:37 -0800 (PST)
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 17 Feb 2009 10:56:47 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 17 Feb 2009 10:56:45 +0100
Message-ID: <941BA0BF46DB8F4983FF7C8AFE800BC208A3CA3C@ftrdmel3>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Fwd: I-D Action:draft-perkins-avt-rapid-rtp-sync-02.txt
Thread-Index: AcmOAfYXKiMvHv5BQkSqjltGzeNWiACIeNVw
References: <20090213144501.45E803A6B0A@core3.amsl.com> <C31AC42F-0694-4B91-96AC-939FA0B64539@csperkins.org>
From: <gerard.babonneau@orange-ftgroup.com>
To: <csp@csperkins.org>, <avt@ietf.org>
X-OriginalArrivalTime: 17 Feb 2009 09:56:47.0532 (UTC) FILETIME=[0C0546C0:01C990E6]
Subject: Re: [AVT] Fwd: I-D Action:draft-perkins-avt-rapid-rtp-sync-02.txt
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, 17 Feb 2009 09:56:41 -0000

Hi,

OK with this draft that improve the synchronization time between =
multiple sessions. I guess its usage is larger than SVC and =
multi-description codecs.
Some remarks to consider in this document.
1) If a multicast (or broadcast) session has no feedback channel, the =
source must send peiodically synchronization messages, with a short =
period (as ~200ms or less, for example).
2) RTP header extension adds 12 bytes. The source must reserve them in =
all packets in order to avoid fragmentation at IP level, because (I =
suppose?) insertion of this extension header may be independant of the =
RTP payload building. This is very bad when packet losses occur. So =
could be possible to have RTP packets that contain only header and =
extension for synchronization?
3) The receiver must have confidence with synchronization information it =
receives. It is the responsability of the sources to give precize =
information.
4) About variant A and B, it depends the precision that synchronization =
needs: a 16 bit information for ntp fraction and 8 bits for ntp seconds =
could be sufficient, because 16 bit fraction give 15 micro-second =
precision, and period between synchronization messages never exceed 250 =
seconds. Could a 32 bit word contain all these information? This may be =
usefull if extension is in a RTP message with data, according to IP =
fragmentation.

Regards,

Gerard BABONNEAU



-----Message d'origine-----
De : avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] De la part de =
Colin Perkins
Envoy=E9 : vendredi 13 f=E9vrier 2009 18:39
=C0 : IETF AVT WG
Objet : [AVT] Fwd: I-D Action:draft-perkins-avt-rapid-rtp-sync-02.txt

This draft is a merger between draft-perkins-avt-rapid-rtp- sync-01.txt =
and draft-schierl-avt-rtp-ntp-for-layered-codecs-00.txt.

Please send any comments to the list. We'd like this to be considered =
for adoption as an AVT working group draft.

Colin



Begin forwarded message:
> From: Internet-Drafts@ietf.org
> Date: 13 February 2009 14:45:01 GMT
> To: i-d-announce@ietf.org
> Subject: I-D Action:draft-perkins-avt-rapid-rtp-sync-02.txt
> Reply-To: internet-drafts@ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts=20
> directories.
>
> 	Title           : Rapid Synchronisation of RTP Flows
> 	Author(s)       : C. Perkins, T. Schierl
> 	Filename        : draft-perkins-avt-rapid-rtp-sync-02.txt
> 	Pages           : 18
> 	Date            : 2009-02-13
>
> This memo outlines how RTP multimedia sessions are synchronised, and=20
> discusses how rapidly such synchronisation can occur.  We show that=20
> most RTP sessions can be synchronised immediately, but that the use of =

> video switching multipoint conference units (MCUs) or large source=20
> specific multicast (SSM) groups can greatly increase the initial=20
> synchronisation delay.  This increase in delay can be unacceptable to=20
> some applications that use layered and/or multi-description codecs.
>
> This memo updates the RTP Control Protocol (RTCP) timing rules to=20
> reduce the initial synchronisation delay for SSM sessions.  A new=20
> feedback packet is defined for use with the Extended RTP Profile for=20
> RTCP-based Feedback (RTP/AVPF), allowing video switching MCUs to=20
> rapidly request resynchronisation.  Two new RTP header extensions are=20
> defined to allow rapid synchronisation of late joiners, and guarantee=20
> correct timestamp based decoding order recovery for layered codecs in=20
> the presence of clock skew.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-perkins-avt-rapid-rtp-
> sync-02.txt



--=20
Colin Perkins
http://csperkins.org/



_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt

From ron.even.tlv@gmail.com  Thu Feb 19 00:33:58 2009
Return-Path: <ron.even.tlv@gmail.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 56DA628C1EC for <avt@core3.amsl.com>; Thu, 19 Feb 2009 00:33:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 hampfy9ai7QK for <avt@core3.amsl.com>; Thu, 19 Feb 2009 00:33:57 -0800 (PST)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by core3.amsl.com (Postfix) with ESMTP id D8B8928C190 for <avt@ietf.org>; Thu, 19 Feb 2009 00:33:56 -0800 (PST)
Received: by fg-out-1718.google.com with SMTP id l26so848675fgb.41 for <avt@ietf.org>; Thu, 19 Feb 2009 00:34:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :message-id:mime-version:content-type:x-mailer:thread-index :content-language; bh=ZtTG0jDmXg/UUKgLOVsba3Z1s1O8KpOOZjqf2CtZJ/Y=; b=ujlWVsswjpW/vs4j83qRiD4I/bxdkGAOcK25ar4YG1Lh2COrj17wTDXykQmPyRgQcl U33QceL5fTOzCOZ56x9dL9MeRycnSLkclj6jd+nU0vdN1K8ix65xH6EUx6qbXJt7fqn4 7heMikmAyknf4r6M+v/ZKPuKMFS+NLxcDQvZI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language; b=AfikKHJQO9Tblzr0fVlWgTryYlOKLpRLXLf6aLqvBuzIjwAqAPTTrulXAEowNHgPrg KZzqyFYTbvzfw7aEVnIUQ1XZ+if1of8P1tcMCLfSmAaQs8SSghrR8+Si8S1pCikMggM7 bZdrqar8FoQXNPv85UXD1cgOOG1zAXA4v4dGc=
Received: by 10.103.244.10 with SMTP id w10mr199464mur.71.1235032448595; Thu, 19 Feb 2009 00:34:08 -0800 (PST)
Received: from windows8d787f9 (bzq-79-176-141-57.red.bezeqint.net [79.176.141.57]) by mx.google.com with ESMTPS id t10sm1511144muh.58.2009.02.19.00.34.06 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 19 Feb 2009 00:34:07 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'IETF AVT WG'" <avt@ietf.org>
Date: Thu, 19 Feb 2009 10:32:42 +0200
Message-ID: <499d197f.0af6660a.476c.fffff26a@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_026C_01C9927D.672205A0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcmSbKF7zuTD8IXvTmm0f3s4AVfZJA==
Content-Language: en-us
Subject: [AVT] comments draft-perkins-avt-rapid-rtp-sync-02
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: Thu, 19 Feb 2009 08:33:58 -0000

This is a multipart message in MIME format.

------=_NextPart_000_026C_01C9927D.672205A0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

I reviewed the draft and in general find it good.

I have comments

 

1.       You have in the draft RTP flows and RTP Sessions, see for example
first sentence of 4.3. What is the difference. 

2.       The last sentence in 3.1 is not very clear.

3.       Section 4.2 starts with Normative text that is relevant to SVC, yet
in SVC there is no such normative text.

4.       The third paragraph in 4.2 (After the first note) repeats text from
3.2

5.       Section 4.3 tries to be general and not SVC specific but refers to
access unit "If a packet must be inserted for satisfying the above rule, the
NTP timestamp of such an inserted packet MUST be set equal to the NTP
timestamp of a packet of the access unit present in any lower RTP flow and
the lowest RTP flow. "

6.       The informative example in 4.3  does not have specifics of the
usage of the header extension, so what is the purpose of the example.

7.       In the security consideration there is no discussion on the header
extension. Note that according to RFC 3711 and as mentioned in RFC 5285 the
header extension is not part of the encrypted portion and it carries
according to this draft the NTP time stamp that is also carried in the RTCP
encrypted portion.

8.       In the IANA section you also need to register the header extension

 

Roni Even

 


------=_NextPart_000_026C_01C9927D.672205A0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:835534740;
	mso-list-type:hybrid;
	mso-list-template-ids:820939204 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>Hi,<o:p></o:p></p>

<p class=3DMsoNormal>I reviewed the draft and in general find it =
good.<o:p></o:p></p>

<p class=3DMsoNormal>I have comments<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3DLTR></span>You have in the draft RTP =
flows
and RTP Sessions, see for example first sentence of 4.3. What is the
difference. <o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3DLTR></span>The last sentence in 3.1 =
is not
very clear.<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>3.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3DLTR></span>Section 4.2 starts with =
Normative
text that is relevant to SVC, yet in SVC there is no such normative =
text.<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>4.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3DLTR></span>The third paragraph in =
4.2 (After
the first note) repeats text from 3.2<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>5.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3DLTR></span>Section 4.3 tries to be =
general and
not SVC specific but refers to access unit &quot;If a packet must be =
inserted
for satisfying the above rule, the NTP timestamp of such an inserted =
packet
MUST be set equal to the NTP timestamp of a packet of the access unit =
present
in any lower RTP flow and the lowest RTP flow. &quot;<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>6.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3DLTR></span>The informative example =
in 4.3 &nbsp;does
not have specifics of the usage of the header extension, so what is the =
purpose
of the example.<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>7.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3DLTR></span>In the security =
consideration
there is no discussion on the header extension. Note that according to =
RFC 3711
and as mentioned in RFC 5285 the header extension is not part of the =
encrypted
portion and it carries according to this draft the NTP time stamp that =
is also carried
in the RTCP encrypted portion.<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>8.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3DLTR></span>In the IANA section you =
also need
to register the header extension<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Roni Even<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>

------=_NextPart_000_026C_01C9927D.672205A0--


From ron.even.tlv@gmail.com  Thu Feb 19 06:51:07 2009
Return-Path: <ron.even.tlv@gmail.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 C811028C0F6 for <avt@core3.amsl.com>; Thu, 19 Feb 2009 06:51:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_17=0.6]
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 sfgHgqfGAqcz for <avt@core3.amsl.com>; Thu, 19 Feb 2009 06:51:01 -0800 (PST)
Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by core3.amsl.com (Postfix) with ESMTP id 3188528C213 for <avt@ietf.org>; Thu, 19 Feb 2009 06:51:01 -0800 (PST)
Received: by ewy14 with SMTP id 14so400209ewy.13 for <avt@ietf.org>; Thu, 19 Feb 2009 06:51:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:subject:date :message-id:mime-version:content-type:x-mailer:thread-index :content-language; bh=gN2QOF8C7J6SuljjUqXejeWWfcrbYyrfuGPsX2GVsAw=; b=rTG1sJnsbYe5GCPkWhSxHiEZh53UmcC1hmlZd/1NedvaRWu/MarXQgGWoVL3xH5XAp 8rLOUlN8y9A9hB9LfiBXpyo1kUUOWnac144Li7FQygEC09tOgN3ompZSkPFoBZHY4TYq OswTgDQkbgxaRo5yzHqLMB/Wd//o3fGkfKYuY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; b=rB3jg5jeiMVJ5/Jy57NKxkHWu+EIw7XRI7e33+juI75L3sDic0EUx20BIcGEd4Vd0K 1juEhfhBfauOuhO7iEmI/CZnNytpz34RIbJS6cYiB/2qWhjwyXQfKaK+wsVIWOel8gEB UtHVLViBOZ8tcqZ6akBcb+fmlZXUP3sRK3UFo=
Received: by 10.103.240.15 with SMTP id s15mr563810mur.82.1235055072594; Thu, 19 Feb 2009 06:51:12 -0800 (PST)
Received: from windows8d787f9 (bzq-79-176-141-57.red.bezeqint.net [79.176.141.57]) by mx.google.com with ESMTPS id e8sm987520muf.29.2009.02.19.06.51.08 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 19 Feb 2009 06:51:10 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'IETF AVT WG'" <avt@ietf.org>
Date: Thu, 19 Feb 2009 16:49:39 +0200
Message-ID: <499d71de.08b6660a.6012.ffffe5be@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_02E5_01C992B2.149BF950"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcmSoUqeNEHP41s+TTuMifgdZpPFjg==
Content-Language: en-us
Cc: fluffy@cisco.com, 'Tom Taylor' <tom.taylor@rogers.com>, sob@harvard.edu
Subject: [AVT] Liaison from ITU-T SG 16
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: Thu, 19 Feb 2009 14:51:07 -0000

This is a multipart message in MIME format.

------=_NextPart_000_02E5_01C992B2.149BF950
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

We have received the following liaison statement from ITU-T Study group 16.

They are looking for a solution that will enable them to exchange capability
of network elements that are in the bearer path (e.g. echo cancellers) in
order to optimize the processing done by them.

The full specification is available, we will look at how to make it
available.

Please look at the following text and see if you have any suggestions

 

Thanks

Roni Even

AVT co-chair

 

ITU-T Q18 of WP1/16 would like to request your assistance to identify if
there are existing protocols (e.g. RTP packet definitions) that can be
utilized to realize the dynamic coordination mechanism defined in the draft
new Recommendation ITU-T G.MDCSPNE over IP networks.

G.MDCSPNE defines a generic framework and protocol requirements for a
coordination mechanism intended to minimize undesirable interaction of voice
processing functions present on bearer paths of a communication link, for
the purpose of improving overall end-to-end voice quality.  Voice quality
improvement is achieved through the usage of "capability lists", exchanged
among nodes on the bearer path, to identify the state of signal processing
functions (available/unavailable) over a call connection.  This information
is then used to refer to a common "rule book" to cause the de-activation of
redundant functions, and the retention of the signal processing functions
that are in most favourable locations for improving voice quality. One
important aspect of G.MDCSPNE is that it allows dynamic coordination of
signal processing functions/devices during a call.  Dynamic coordination is
needed in response to changes in signal processing function availability due
to, for example, call topology changes such as call transfer or call
handover, all within the same call session. The generic capability list
format structure and the rules for de-activation and retention, based on
this state information, have been finalized in G.MDCSPNE. The scope of
G.MDCSPNE, however, does not cover the definition of protocols for the
exchange of capability list information on the bearer path to realize the
coordination mechanism over IP networks.

ITU-T Q18 of WP1/16 would like to request your assistance in identifying if
there is (are) existing standard specifications that could serve as a
vehicle for exchange of state of availability of voice processing functions
among nodes on a call-path, to satisfy the requirements for a dynamic
coordination mechanism over IP networks as contained in ITU-T Q18/16 draft
G.MDCSPNE. 

ITU-T Q18/16 understands that modification of the generic capability list
format structure in G.MDCSPNE may be needed in order to take advantage of
existing specifications to implement the dynamic coordination mechanism.  If
such should be the case, ITU-T Q18/16 would appreciate very much if you
would provide the modifications needed.  

For information purpose, attached please find the latest version of
G.MDCSPNE for your reference.  G.MDCSPNE is expected to go for consent at
the ITU-T October 2009 SG16 meeting and become an ITU-T standard afterwards.


Attachment


-            Draft 8 of G.MDCSPNE "Mechanism for Dynamic Coordination of
Voice Enhancement SPNE"

 


------=_NextPart_000_02E5_01C992B2.149BF950
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:0in;
	margin-bottom:.0001pt;
	punctuation-wrap:simple;
	text-autospace:none;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
h1
	{mso-style-name:"Heading 1\,l1\,h1\,1st level\,Normal + Font\: =
Helvetica\,Bold\,Space Before 12 pt\,Not Bold\,le1\,heading 1\,1";
	mso-style-link:"Heading 1 Char\,l1 Char1\,h1 Char1\,1st level =
Char1\,Normal + Font\: Helvetica Char1\,Bold Char1\,Space Before 12 pt =
Char1\,Not Bold Char1\,le1 Char1\,heading 1 Char1\,1 Char1";
	margin-top:.25in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:39.7pt;
	margin-bottom:.0001pt;
	text-indent:-39.7pt;
	page-break-after:avoid;
	punctuation-wrap:simple;
	text-autospace:none;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	font-weight:normal;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.Heading1Char
	{mso-style-name:"Heading 1 Char\,l1 Char1\,h1 Char1\,1st level =
Char1\,Normal + Font\: Helvetica Char1\,Bold Char1\,Space Before 12 pt =
Char1\,Not Bold Char1\,le1 Char1\,heading 1 Char1\,1 Char1";
	mso-style-link:"Heading 1\,l1\,h1\,1st level\,Normal + Font\: =
Helvetica\,Bold\,Space Before 12 pt\,Not Bold\,le1\,heading 1\,1";
	font-family:"Times New Roman","serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span lang=3DEN-GB>Hi,<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB>We have received the following =
liaison statement
from ITU-T Study group 16.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB>They are looking for a solution =
that will
enable them to exchange capability of network elements that are in the =
bearer
path (e.g. echo cancellers) in order to optimize the processing done by =
them.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB>The full specification is =
available, we
will look at how to make it available.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB>Please look at the following =
text and see
if you have any suggestions<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB>Thanks<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB>Roni Even<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB>AVT =
co-chair<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB>ITU-T Q18 of WP1/16 would like =
to request
your assistance to identify if there are existing protocols (e.g. RTP =
packet
definitions) that can be utilized to realize the dynamic coordination =
mechanism
defined in the draft new Recommendation ITU-T G.MDCSPNE over IP =
networks.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB>G.MDCSPNE defines a generic =
framework and
protocol requirements for a coordination mechanism intended to minimize
undesirable interaction of voice processing functions present on bearer =
paths
of a communication link, for the purpose of improving overall end-to-end =
voice
quality.&nbsp; Voice quality improvement is achieved through the usage =
of
&#8220;capability lists&#8221;, exchanged among nodes on the bearer =
path, to
identify the state of signal processing functions =
(available/unavailable) over
a call connection.&nbsp; This information is then used to refer to a =
common
&#8220;rule book&#8221; to cause the de-activation of redundant =
functions, and
the retention of the signal processing functions that are in most =
favourable
locations for improving voice quality. One important aspect of G.MDCSPNE =
is
that it allows dynamic coordination of signal processing =
functions/devices
during a call.&nbsp; Dynamic coordination is needed in response to =
changes in
signal processing function availability due to, for example, call =
topology
changes such as call transfer or call handover, all within the same call =
session.
The generic capability list format structure and the rules for =
de-activation
and retention, based on this state information, have been finalized in
G.MDCSPNE. The scope of G.MDCSPNE, however, does not cover the =
definition of
protocols for the exchange of capability list information on the bearer =
path to
realize the coordination mechanism over IP =
networks.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB>ITU-T Q18 of WP1/16 would like =
to request
your assistance in identifying if there is (are) existing standard
specifications that could serve as a vehicle for exchange of state of
availability of voice processing functions among nodes on a call-path, =
to
satisfy the requirements for a dynamic coordination mechanism over IP =
networks
as contained in ITU-T Q18/16 draft G.MDCSPNE. <o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB>ITU-T Q18/16 understands that =
modification
of the generic capability list format structure in G.MDCSPNE may be =
needed in
order to take advantage of existing specifications to implement the =
dynamic
coordination mechanism.&nbsp; If such should be the case, ITU-T Q18/16 =
would
appreciate very much if you would provide the modifications =
needed.&nbsp; <o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB>For information purpose, =
attached please
find the latest version of G.MDCSPNE for your reference.&nbsp; G.MDCSPNE =
is
expected to go for consent at the ITU-T October 2009 SG16 meeting and =
become an
ITU-T standard afterwards.<o:p></o:p></span></p>

<h1><b><span lang=3DEN-GB>Attachment<o:p></o:p></span></b></h1>

<p class=3DMsoNormal =
style=3D'margin-left:39.7pt;text-indent:-39.7pt'><span
lang=3DEN-GB>-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; Draft
8 of G.MDCSPNE &#8220;Mechanism for Dynamic Coordination of Voice =
Enhancement
SPNE&#8221;<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p>

</div>

</body>

</html>

------=_NextPart_000_02E5_01C992B2.149BF950--


From root@core3.amsl.com  Fri Feb 20 05:00:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id CEB4D3A68BF; Fri, 20 Feb 2009 05:00:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090220130001.CEB4D3A68BF@core3.amsl.com>
Date: Fri, 20 Feb 2009 05:00:01 -0800 (PST)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-rtcp-non-compound-09.txt
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: Fri, 20 Feb 2009 13:00:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.


	Title           : Support for Reduced-Size RTCP, Opportunities and Consequences
	Author(s)       : I. Johansson, M. Westerlund
	Filename        : draft-ietf-avt-rtcp-non-compound-09.txt
	Pages           : 17
	Date            : 2009-02-20

This memo discusses benefits and issues that arise when allowing RTCP
packets to be transmitted with reduced size.  The size can be reduced
if the rules on how to create compound packets outlined in RFC3550
are removed or changed.  Based on that analysis this memo defines
certain changes to the rules to allow feedback messages to be sent as
reduced-size RTCP packets under certain conditions when using the RTP
AVPF profile (RFC 4585).  This document updates [RFC3550], [RFC3711]
and [RFC4585].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcp-non-compound-09.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-avt-rtcp-non-compound-09.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-02-20045335.I-D@ietf.org>


--NextPart--

From jeedward@yahoo.com  Fri Feb 20 08:51:06 2009
Return-Path: <jeedward@yahoo.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 216FE28C217 for <avt@core3.amsl.com>; Fri, 20 Feb 2009 08:51:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.83
X-Spam-Level: 
X-Spam-Status: No, score=-0.83 tagged_above=-999 required=5 tests=[AWL=0.372,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
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 QJ22ntJtbzW2 for <avt@core3.amsl.com>; Fri, 20 Feb 2009 08:51:05 -0800 (PST)
Received: from n25.bullet.mail.mud.yahoo.com (n25.bullet.mail.mud.yahoo.com [68.142.206.220]) by core3.amsl.com (Postfix) with SMTP id C94893A6A5B for <avt@ietf.org>; Fri, 20 Feb 2009 08:51:04 -0800 (PST)
Received: from [209.191.108.96] by n25.bullet.mail.mud.yahoo.com with NNFMP; 20 Feb 2009 16:50:56 -0000
Received: from [68.142.201.243] by t3.bullet.mud.yahoo.com with NNFMP; 20 Feb 2009 16:50:56 -0000
Received: from [127.0.0.1] by omp404.mail.mud.yahoo.com with NNFMP; 20 Feb 2009 16:50:56 -0000
X-Yahoo-Newman-Property: ymail-5
X-Yahoo-Newman-Id: 244341.49152.bm@omp404.mail.mud.yahoo.com
Received: (qmail 9270 invoked by uid 60001); 20 Feb 2009 16:50:55 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=k5CBZKMGkpaMnG0VN2p1rn6eMmvVxuEDOpihi4VhbF+/OeEb4nEGAOzaMt7tS2tCb66gkPrSfiWGJ6h7gKVwAad4wf7nyu11guViR5U3E0XXwUcamogtuNGRdMvQdCoyPFTPIeRglEDUNjzJSh+FXFJiruzdcuwcmusMNgQldRY=;
X-YMail-OSG: 42U8hCwVM1lXPVHBpQeP5FMpFndhYYYeg_VRPpPycfO.bEGQaGXEfR3sDkGcTN_4f51VIjDAMAGXLvR8FFe4HMKk2yNCxnTFwOQoP3v1SvKcRUJSVCl1AYFZmTHcEXwLBAdPt20SfmDUMSSSb6VhZ9TefLarzMsTfe2MliKGNF9XWr3M2giyfpjTLcdJctSGWAwgVhbpqA--
Received: from [67.233.188.239] by web45913.mail.sp1.yahoo.com via HTTP; Fri, 20 Feb 2009 08:50:55 PST
X-Mailer: YahooMailWebService/0.7.260.1
Date: Fri, 20 Feb 2009 08:50:55 -0800 (PST)
From: John Edward <jeedward@yahoo.com>
To: avt@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1681929372-1235148655=:2708"
Message-ID: <620118.2708.qm@web45913.mail.sp1.yahoo.com>
Subject: [AVT] Draft paper submission deadline extended: HPCNCS-09
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: Fri, 20 Feb 2009 16:51:06 -0000

--0-1681929372-1235148655=:2708
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Draft paper submission deadline extended: HPCNCS-09
=A0
The deadline for draft paper submission at the 2009 International Conferenc=
e on High Performance Computing, Networking and Communication Systems (HPCN=
CS-09) (website: http://www.PromoteResearch.org ) is extended due to numero=
us requests from the authors. The conference will be held during July 13-16=
 2009 in Orlando, FL, USA. We invite draft paper submissions. The conferenc=
e will take place at the same time and venue where several other internatio=
nal conferences are taking place. The other conferences include:
=B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Artificial Intellig=
ence and Pattern Recognition (AIPR-09)=20
=B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Automation, Robotic=
s and Control Systems (ARCS-09)
=B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Bioinformatics, Com=
putational Biology, Genomics and Chemoinformatics (BCBGC-09)=20
=B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Enterprise Informat=
ion Systems and Web Technologies (EISWT-09)
=B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Information Securit=
y and Privacy (ISP-09)
=B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Recent Advances in =
Information Technology and Applications (RAITA-09)
=B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Software Engineerin=
g Theory and Practice (SETP-09)=20
=B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Theory and Applicat=
ions of Computational Science (TACS-09)
=B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Theoretical and Mat=
hematical Foundations of Computer Science (TMFCS-09)
=A0
The website http://www.PromoteResearch.org contains more details.
=A0
Sincerely
John=A0 Edward
Publicity committee=0A=0A=0A      
--0-1681929372-1235148655=:2708
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<table cellspacing=3D"0" cellpadding=3D"0" border=3D"0" ><tr><td valign=3D"=
top" style=3D"font: inherit;"><P style=3D"MARGIN: 0in 0in 0pt"><A name=3DOL=
E_LINK4></A><A name=3DOLE_LINK3><SPAN style=3D"mso-bookmark: OLE_LINK4"><FO=
NT face=3D"Times New Roman" size=3D3>Draft paper submission deadline extend=
ed: HPCNCS-09</FONT></SPAN></A></DIV>
<P style=3D"MARGIN: 0in 0in 0pt"><SPAN style=3D"mso-bookmark: OLE_LINK3"><S=
PAN style=3D"mso-bookmark: OLE_LINK4"><?xml:namespace prefix =3D o ns =3D "=
urn:schemas-microsoft-com:office:office" /><o:p><FONT face=3D"Times New Rom=
an" size=3D3>&nbsp;</FONT></o:p></SPAN></SPAN></DIV>
<P style=3D"MARGIN: 0in 0in 0pt"><SPAN style=3D"mso-bookmark: OLE_LINK3"><S=
PAN style=3D"mso-bookmark: OLE_LINK4"><FONT face=3D"Times New Roman" size=
=3D3>The deadline for draft paper submission at the 2009 <SPAN style=3D"COL=
OR: black">International Conference on High Performance Computing, Networki=
ng and Communication Systems (HPCNCS-09) </SPAN>(website: </FONT></SPAN></S=
PAN><A href=3D"http://www.promoteresearch.org/"><FONT color=3D#0000ff><FONT=
 size=3D3><FONT face=3D"Times New Roman"><SPAN style=3D"mso-bookmark: OLE_L=
INK3"><SPAN style=3D"mso-bookmark: OLE_LINK4">http://www.PromoteResearch.or=
g</SPAN></SPAN><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-b=
ookmark: OLE_LINK4"></SPAN></SPAN></FONT></FONT></FONT></A><SPAN style=3D"m=
so-bookmark: OLE_LINK3"><SPAN style=3D"mso-bookmark: OLE_LINK4"><FONT size=
=3D3><FONT face=3D"Times New Roman"> ) is extended due to numerous requests=
 from the authors. The conference will be held during July 13-16 2009 in Or=
lando, FL, USA. We invite draft
 paper submissions. The conference will take place at the same time and ven=
ue where several other international conferences are taking place. The othe=
r conferences include:<SPAN style=3D"COLOR: black"><o:p></o:p></SPAN></FONT=
></FONT></SPAN></SPAN></DIV>
<P style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 l=
evel1 lfo1"><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-book=
mark: OLE_LINK4"><SPAN style=3D"COLOR: black; FONT-FAMILY: Symbol; mso-fare=
ast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style=3D"mso-l=
ist: Ignore"><FONT size=3D3>=B7</FONT><SPAN style=3D"FONT: 7pt 'Times New R=
oman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPA=
N><FONT size=3D3><FONT face=3D"Times New Roman"><SPAN style=3D"COLOR: black=
">International Conference on Artificial Intelligence and Pattern Recogniti=
on (AIPR-09)</SPAN> <SPAN style=3D"COLOR: black"><o:p></o:p></SPAN></FONT><=
/FONT></SPAN></SPAN></DIV>
<P style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 l=
evel1 lfo1"><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-book=
mark: OLE_LINK4"><SPAN style=3D"COLOR: black; FONT-FAMILY: Symbol; mso-fare=
ast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style=3D"mso-l=
ist: Ignore"><FONT size=3D3>=B7</FONT><SPAN style=3D"FONT: 7pt 'Times New R=
oman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPA=
N><SPAN style=3D"COLOR: black"><FONT size=3D3><FONT face=3D"Times New Roman=
">International Conference on Automation, Robotics and Control Systems (ARC=
S-09)<o:p></o:p></FONT></FONT></SPAN></SPAN></SPAN></DIV>
<P style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 l=
evel1 lfo1"><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-book=
mark: OLE_LINK4"><SPAN style=3D"COLOR: black; FONT-FAMILY: Symbol; mso-fare=
ast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style=3D"mso-l=
ist: Ignore"><FONT size=3D3>=B7</FONT><SPAN style=3D"FONT: 7pt 'Times New R=
oman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPA=
N><SPAN style=3D"COLOR: black"><FONT size=3D3><FONT face=3D"Times New Roman=
">International Conference on Bioinformatics, Computational Biology, Genomi=
cs and Chemoinformatics (BCBGC-09) <o:p></o:p></FONT></FONT></SPAN></SPAN><=
/SPAN></DIV>
<P style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 l=
evel1 lfo1"><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-book=
mark: OLE_LINK4"><SPAN style=3D"COLOR: black; FONT-FAMILY: Symbol; mso-fare=
ast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style=3D"mso-l=
ist: Ignore"><FONT size=3D3>=B7</FONT><SPAN style=3D"FONT: 7pt 'Times New R=
oman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPA=
N><SPAN style=3D"COLOR: black"><FONT size=3D3><FONT face=3D"Times New Roman=
">International Conference on Enterprise Information Systems and Web Techno=
logies (EISWT-09)<o:p></o:p></FONT></FONT></SPAN></SPAN></SPAN></DIV>
<P style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 l=
evel1 lfo1"><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-book=
mark: OLE_LINK4"><SPAN style=3D"COLOR: black; FONT-FAMILY: Symbol; mso-fare=
ast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style=3D"mso-l=
ist: Ignore"><FONT size=3D3>=B7</FONT><SPAN style=3D"FONT: 7pt 'Times New R=
oman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPA=
N><SPAN style=3D"COLOR: black"><FONT size=3D3><FONT face=3D"Times New Roman=
">International Conference on Information Security and Privacy (ISP-09)<o:p=
></o:p></FONT></FONT></SPAN></SPAN></SPAN></DIV>
<P style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 l=
evel1 lfo1"><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-book=
mark: OLE_LINK4"><SPAN style=3D"COLOR: black; FONT-FAMILY: Symbol; mso-fare=
ast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style=3D"mso-l=
ist: Ignore"><FONT size=3D3>=B7</FONT><SPAN style=3D"FONT: 7pt 'Times New R=
oman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPA=
N><SPAN style=3D"COLOR: black"><FONT size=3D3><FONT face=3D"Times New Roman=
">International Conference on Recent Advances in Information Technology and=
 Applications (RAITA-09)<o:p></o:p></FONT></FONT></SPAN></SPAN></SPAN></DIV=
>
<P style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 l=
evel1 lfo1"><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-book=
mark: OLE_LINK4"><SPAN style=3D"COLOR: black; FONT-FAMILY: Symbol; mso-fare=
ast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style=3D"mso-l=
ist: Ignore"><FONT size=3D3>=B7</FONT><SPAN style=3D"FONT: 7pt 'Times New R=
oman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPA=
N><SPAN style=3D"COLOR: black"><FONT size=3D3><FONT face=3D"Times New Roman=
">International Conference on Software Engineering Theory and Practice (SET=
P-09) <o:p></o:p></FONT></FONT></SPAN></SPAN></SPAN></DIV>
<P style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 l=
evel1 lfo1"><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-book=
mark: OLE_LINK4"><SPAN style=3D"COLOR: black; FONT-FAMILY: Symbol; mso-fare=
ast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style=3D"mso-l=
ist: Ignore"><FONT size=3D3>=B7</FONT><SPAN style=3D"FONT: 7pt 'Times New R=
oman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPA=
N><SPAN style=3D"COLOR: black"><FONT size=3D3><FONT face=3D"Times New Roman=
">International Conference on Theory and Applications of Computational Scie=
nce (TACS-09)<o:p></o:p></FONT></FONT></SPAN></SPAN></SPAN></DIV>
<P style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 l=
evel1 lfo1"><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-book=
mark: OLE_LINK4"><SPAN style=3D"COLOR: black; FONT-FAMILY: Symbol; mso-fare=
ast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style=3D"mso-l=
ist: Ignore"><FONT size=3D3>=B7</FONT><SPAN style=3D"FONT: 7pt 'Times New R=
oman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPA=
N><SPAN style=3D"COLOR: black"><FONT size=3D3><FONT face=3D"Times New Roman=
">International Conference on Theoretical and Mathematical Foundations of C=
omputer Science (TMFCS-09)<o:p></o:p></FONT></FONT></SPAN></SPAN></SPAN></D=
IV>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN style=3D"mso-bookm=
ark: OLE_LINK3"><SPAN style=3D"mso-bookmark: OLE_LINK4"><o:p><FONT face=3D"=
Times New Roman" size=3D3>&nbsp;</FONT></o:p></SPAN></SPAN></DIV>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN style=3D"mso-bookm=
ark: OLE_LINK3"><SPAN style=3D"mso-bookmark: OLE_LINK4"><FONT face=3D"Times=
 New Roman" size=3D3>The website </FONT></SPAN></SPAN><A href=3D"http://www=
..promoteresearch.org/"><FONT color=3D#0000ff><FONT size=3D3><FONT face=3D"T=
imes New Roman"><SPAN style=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-=
bookmark: OLE_LINK4">http://www.PromoteResearch.org</SPAN></SPAN><SPAN styl=
e=3D"mso-bookmark: OLE_LINK3"><SPAN style=3D"mso-bookmark: OLE_LINK4"></SPA=
N></SPAN></FONT></FONT></FONT></A><SPAN style=3D"mso-bookmark: OLE_LINK3"><=
SPAN style=3D"mso-bookmark: OLE_LINK4"><FONT face=3D"Times New Roman" size=
=3D3> contains more details.</FONT></SPAN></SPAN></DIV>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN style=3D"mso-bookm=
ark: OLE_LINK3"><SPAN style=3D"mso-bookmark: OLE_LINK4"><o:p><FONT face=3D"=
Times New Roman" size=3D3>&nbsp;</FONT></o:p></SPAN></SPAN></DIV>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN style=3D"mso-bookm=
ark: OLE_LINK3"><SPAN style=3D"mso-bookmark: OLE_LINK4"><FONT face=3D"Times=
 New Roman" size=3D3>Sincerely</FONT></SPAN></SPAN></DIV><SPAN style=3D"mso=
-bookmark: OLE_LINK4"></SPAN><SPAN style=3D"mso-bookmark: OLE_LINK3"></SPAN=
>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times New =
Roman" size=3D3>John<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Edward<=
/FONT></DIV>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times New =
Roman" size=3D3>Publicity committee</FONT></DIV></td></tr></table><br>=0A=
=0A=0A=0A      
--0-1681929372-1235148655=:2708--


From versteb@cisco.com  Fri Feb 20 10:31:35 2009
Return-Path: <versteb@cisco.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 6AC8A3A680E for <avt@core3.amsl.com>; Fri, 20 Feb 2009 10:31:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 BfHXgXUTtZgK for <avt@core3.amsl.com>; Fri, 20 Feb 2009 10:31:34 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 91D673A6986 for <avt@ietf.org>; Fri, 20 Feb 2009 10:31:33 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,242,1233532800"; d="scan'208,217";a="37832007"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 20 Feb 2009 18:31:47 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n1KIVl2D007735;  Fri, 20 Feb 2009 13:31:47 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n1KIVlnD021243; Fri, 20 Feb 2009 18:31:47 GMT
Received: from xmb-rtp-21d.amer.cisco.com ([64.102.31.116]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 20 Feb 2009 13:31:47 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C99389.7CF23F77"
Date: Fri, 20 Feb 2009 13:31:46 -0500
Message-ID: <81B9B88E2F9D574AA5328A85547CDE919B2D27@xmb-rtp-21d.amer.cisco.com>
In-Reply-To: <49800f21.0305560a.6ffe.31c8@mx.google.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New draft on rapid synchronization
Thread-Index: AcmBHWYLutudGKPhQRSEVDMJbxVIdASa8PKA
References: <49800f21.0305560a.6ffe.31c8@mx.google.com>
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "Roni Even" <ron.even.tlv@gmail.com>, "Orit Levin" <oritl@microsoft.com>,  "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>, "Dave Oran (oran)" <oran@cisco.com>, "Ali C. Begen (abegen)" <abegen@cisco.com>
X-OriginalArrivalTime: 20 Feb 2009 18:31:47.0765 (UTC) FILETIME=[7D3BE650:01C99389]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=13787; t=1235154707; x=1236018707; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=versteb@cisco.com; z=From:=20=22Bill=20Ver=20Steeg=20(versteb)=22=20<versteb@ci sco.com> |Subject:=20RE=3A=20New=20draft=20on=20rapid=20synchronizat ion |Sender:=20 |To:=20=22Roni=20Even=22=20<ron.even.tlv@gmail.com>,=20=22O rit=20Levin=22=20<oritl@microsoft.com>,=0A=20=20=20=20=20=20 =20=20=22VAN=20CAENEGEM=20Tom=22=20<Tom.Van_Caenegem@alcatel -lucent.be>,=0A=20=20=20=20=20=20=20=20=22Dave=20Oran=20(ora n)=22=20<oran@cisco.com>,=0A=20=20=20=20=20=20=20=20=22Ali=2 0C.=20Begen=20(abegen)=22=20<abegen@cisco.com>; bh=otJxyTd5J5OIPvVfxBvmTi484NkGto6PO64Ze4s24uI=; b=BwIbAAMtdr8pd6/ocCSp69rx1wF12NGnNKuM2w145oIOUCzacRxAE6Naaa pm4Cy0YQ2dyfam7sbw4x70cLXReFaxZI7vQ+pAa2pZy01DYgtGF3+nC5IZy7 Bg3SW0CPGZ;
Authentication-Results: rtp-dkim-2; header.From=versteb@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); 
Cc: Tom Taylor <tom.taylor@rogers.com>, IETF AVT WG <avt@ietf.org>
Subject: Re: [AVT] New draft on rapid synchronization
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: Fri, 20 Feb 2009 18:31:35 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C99389.7CF23F77
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20
=20
This note is in response to "Extensions to RTCP for Rapid
Synchronization draft-peilin-avt-rtp-burst-00.txt" from P. Yang and B
Lei. It is encouraging to see that the authors agree with the broad
methodology of the previous drafts around rapid acceleration of
synchronization RTP multicast sessions. Hopefully we are converging on a
common solution. There are some areas of this draft that I need some
clarification on , though.
=20
Steps 1-3 appear to be functionally equivalent to the flows previously
described. As previously stated, this is a promising step.
=20
In step 4, the receiver does an analysis of the incoming unicast burst
to determine the optimum acceleration rate. The underlying assumption
appears to be that packet loss is congestion driven. How does this
method behave if the loss is due to other sources, such as noise on the
last mile plant? Can the receiver differentiate between congestive loss
and non-congestive loss? I have seen some analysis that claims to be
able to differentiate between the two types of loss, but it is not clear
(to me) if this is assumed in this case.
=20
Clearly, if the link is driven into saturation, loss will result. I
would also like to understand the mechanism by which the RR and RS
recover from deterministic (congestion-based) loss. I have personally
been using a mental model in which the loss rate during acceleration is
approximately the same as any other time on the network, and many
(most?) acceleration bursts will complete without the need for
additional repair packets. To be honest, I have not given much thought
to a model in which there may be deterministic loss on every channel
change. What impact does this have on the scalability of the system?
=20
I also realize that I have been assuming a model in which the
acceleration flows can't cause congestive loss in a video flow - either
through admission control or by using different QOS markings for the two
flows. More on this in my questions about step 10.
=20
In steps 6-7, there appears to be a deterministic round-trip-time delay
between the sender catching up to realtime and the cessation of the
unicast flow. In the previous models, the design goal is have the
unicast flow cease at approximately the same time as it catches up to
the multicast flow at the receiver. I am trying to understand the
relative merits of having a handshake (with its resultant RTT-scale
delay) and pre-signaling the transition.  I am particularly interested
in the behavior when one or more of the packets in the handshake are
dropped.
=20
In step 10, the receiver assumes that the steady state found in previous
multicast synchronization attempts is a good starting point. I am also
interested in this stage of the proposal. I have been assuming that the
channel is fairly dynamic, with other devices contending for the
bandwidth resources. In some cases, the video is from the same QOS pool
as acceleration bandwidth and is thus subject to admission control. In
this case, the maximum rate can be determined directly. In other cases,
the video is in a different (hopefully higher) QOS pool than the
acceleration data. In this case, the acceleration burst is contending
with other (presumably rate-adaptive) flows. When contending with other
rate adaptive flows, it is not clear that the available bandwidth of the
bottleneck link is the same as the last instantiation of the protocol.
For most of the modeling I have been doing, I have been assuming that
rate - adaptive  flows do not compete with multicast video flows due to
the detrimental effects of of congestive packet loss on video. Perhaps
this assumption is core to my questions earlier in this note.
=20
=20
I look forward to exploring these issues further.
=20
Bill VerSteeg

________________________________

From: Roni Even [mailto:ron.even.tlv@gmail.com]=20
Sent: Wednesday, January 28, 2009 2:53 AM
To: Bill Ver Steeg (versteb); 'Orit Levin'; 'VAN CAENEGEM Tom'; Dave
Oran (oran); Ali C. Begen (abegen)
Cc: 'Tom Taylor'; 'IETF AVT WG'
Subject: New draft on rapid synchronization



Hi guys,

Please note that
http://tools.ietf.org/id/draft-peilin-avt-rtp-burst-00.txt is discussing
the same topic.

I suggest you review it and take this work into account.

Thanks

Roni Even

=20

=20


------_=_NextPart_001_01C99389.7CF23F77
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16809" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Calibri","sans-serif"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Calibri","sans-serif"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Calibri","sans-serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: =
personal-compose
}
.MsoChpDefault {
	mso-style-type: export-only
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft>
<DIV><SPAN class=3D633275821-19022009><SPAN =
class=3D868272918-20022009><FONT=20
face=3DArial></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D633275821-19022009><FONT =
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D633275821-19022009><FONT face=3DArial>This note is in =
response to=20
"Extensions to RTCP for Rapid Synchronization =
draft-peilin-avt-rtp-burst-00.txt"=20
from P. Yang and B Lei. It is&nbsp;encouraging to see that the authors =
agree=20
with the broad methodology of the previous drafts around rapid =
acceleration of=20
synchronization RTP multicast sessions. Hopefully we are converging on a =
common=20
solution. There are some areas of this draft that I need some =
clarification on ,=20
though.</FONT></SPAN></DIV>
<DIV><SPAN class=3D633275821-19022009><FONT =
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D633275821-19022009><FONT face=3DArial>Steps 1-3 =
appear to be=20
functionally equivalent to the flows previously described. As previously =
stated,=20
this is a promising step.</FONT></SPAN></DIV>
<DIV><SPAN class=3D633275821-19022009><FONT =
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D633275821-19022009><FONT face=3DArial>In step 4, the =
receiver=20
does an analysis of the incoming unicast burst to determine the optimum=20
acceleration rate. The underlying assumption&nbsp;appears to =
be&nbsp;that packet=20
loss is congestion driven. How does this method behave if the loss is =
due to=20
other sources, such as noise on the last mile plant? Can the receiver=20
differentiate between congestive loss and non-congestive loss? I have =
seen some=20
analysis that claims to be able to differentiate between the two types =
of loss,=20
but it is not clear (to me) if this is assumed in this =
case.</FONT></SPAN></DIV>
<DIV><SPAN class=3D633275821-19022009><FONT =
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D633275821-19022009><FONT face=3DArial>Clearly, if the =
link is=20
driven into saturation, loss will result. </FONT></SPAN><SPAN=20
class=3D633275821-19022009><FONT face=3DArial><SPAN =
class=3D633275821-19022009><FONT=20
face=3DArial>I would also like to understand the mechanism by which the =
RR and RS=20
recover from&nbsp;deterministic (congestion-based)&nbsp;loss. I have=20
personally&nbsp;been using a mental model in which the loss rate during=20
acceleration is approximately the same as any other time on the network, =
and=20
many (most?) acceleration bursts will complete without the need for =
additional=20
repair packets. To be honest, I have not given much thought to&nbsp;a =
model in=20
which there may be deterministic loss on every channel change. What =
impact does=20
this have on the scalability of the =
system?</FONT></SPAN></DIV></FONT></SPAN>
<DIV><SPAN class=3D633275821-19022009><FONT =
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D633275821-19022009><FONT face=3DArial>I also realize =
that I have=20
been assuming a model in which the acceleration flows can't cause =
congestive=20
loss in a video flow - either through admission control or by using =
different=20
QOS markings for the two flows. More on this in my questions about step=20
10.</FONT></SPAN></DIV>
<DIV><SPAN class=3D633275821-19022009><FONT =
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D633275821-19022009><FONT face=3DArial>In steps 6-7, =
there appears=20
to be&nbsp;a deterministic&nbsp;round-trip-time delay between the sender =

catching up to realtime and the cessation of the unicast flow. In the =
previous=20
models, the design goal is have the unicast flow cease at approximately =
the same=20
time as&nbsp;it catches up to the&nbsp;multicast flow at the receiver. I =
am=20
trying to understand the relative merits of having a handshake (with its =

resultant RTT-scale delay) and pre-signaling the transition.&nbsp; I am=20
particularly interested in the behavior when one or more of the packets =
in the=20
handshake are dropped.</FONT></SPAN></DIV>
<DIV><SPAN class=3D633275821-19022009><FONT =
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D633275821-19022009><FONT face=3DArial>In step 10, the =
receiver=20
assumes that the steady state found in previous multicast =
synchronization=20
attempts is a good starting point. I am also interested in this stage of =
the=20
proposal. I have been assuming that the channel is fairly dynamic, with =
other=20
devices contending for the bandwidth resources. In&nbsp;some cases, the =
video is=20
from the same QOS pool as acceleration bandwidth and is thus subject to=20
admission control. In this case, the&nbsp;maximum rate can be determined =

directly. In other cases, the video is in a different (hopefully higher) =
QOS=20
pool&nbsp;than the acceleration data. In this case, the acceleration =
burst is=20
contending with other (presumably rate-adaptive) flows. When contending =
with=20
other rate adaptive flows, it is not clear that the available bandwidth =
of the=20
bottleneck link is the same as the last instantiation of the protocol. =
For most=20
of the modeling I have been doing, I have been assuming that rate -=20
adaptive&nbsp; flows do not compete with multicast video flows due to =
the=20
detrimental effects of of congestive packet loss on video. Perhaps this=20
assumption is core to my questions earlier in this =
note.</FONT></SPAN></DIV>
<DIV><SPAN class=3D633275821-19022009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D633275821-19022009></SPAN><SPAN=20
class=3D633275821-19022009></SPAN><SPAN =
class=3D633275821-19022009></SPAN><SPAN=20
class=3D633275821-19022009></SPAN><SPAN class=3D633275821-19022009><FONT =

face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D633275821-19022009><FONT face=3DArial>I look forward =
to exploring=20
these issues further.</FONT></SPAN></DIV>
<DIV><SPAN class=3D633275821-19022009><FONT =
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D633275821-19022009><FONT face=3DArial>Bill=20
VerSteeg</FONT></SPAN></DIV></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Roni Even =
[mailto:ron.even.tlv@gmail.com]=20
<BR><B>Sent:</B> Wednesday, January 28, 2009 2:53 AM<BR><B>To:</B> Bill =
Ver=20
Steeg (versteb); 'Orit Levin'; 'VAN CAENEGEM Tom'; Dave Oran (oran); Ali =
C.=20
Begen (abegen)<BR><B>Cc:</B> 'Tom Taylor'; 'IETF AVT =
WG'<BR><B>Subject:</B> New=20
draft on rapid synchronization<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal>Hi guys,<o:p></o:p></P>
<P class=3DMsoNormal>Please note that <A=20
href=3D"http://tools.ietf.org/id/draft-peilin-avt-rtp-burst-00.txt">http:=
//tools.ietf.org/id/draft-peilin-avt-rtp-burst-00.txt</A>=20
is discussing the same topic.<o:p></o:p></P>
<P class=3DMsoNormal>I suggest you review it and take this work into=20
account.<o:p></o:p></P>
<P class=3DMsoNormal>Thanks<o:p></o:p></P>
<P class=3DMsoNormal>Roni Even<o:p></o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P></DIV></BODY></HTML>

------_=_NextPart_001_01C99389.7CF23F77--

From simao.campos@itu.int  Sun Feb 22 13:34:07 2009
Return-Path: <simao.campos@itu.int>
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 594CA28C11C for <avt@core3.amsl.com>; Sun, 22 Feb 2009 13:34:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_17=0.6]
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 bwQdysN9ofXI for <avt@core3.amsl.com>; Sun, 22 Feb 2009 13:34:00 -0800 (PST)
Received: from protext02.itu.ch (protext02.itu.ch [156.106.192.19]) by core3.amsl.com (Postfix) with ESMTP id 001183A6AD5 for <avt@ietf.org>; Sun, 22 Feb 2009 13:33:59 -0800 (PST)
Received: from protext02.itu.ch ([156.106.192.19]) by protext02.itu.ch with Microsoft SMTPSVC(5.0.2195.6713); Sun, 22 Feb 2009 22:34:14 +0100
Received: From PROTINT1.blue.itu.ch ([156.106.128.47]) by protext02.itu.ch (WebShield SMTP v4.5 MR3) id 1235338453432; Sun, 22 Feb 2009 22:34:13 +0100
Received: from MAILBOX1.blue.itu.ch ([156.106.130.106]) by PROTINT1.blue.itu.ch with Microsoft SMTPSVC(6.0.3790.3959);  Sun, 22 Feb 2009 22:34:13 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C99535.4D7EC49A"
Date: Sun, 22 Feb 2009 22:33:48 +0100
Message-ID: <334A4109C6BEA14ABB48EBCF274A6C8A0409BC80@MAILBOX1.blue.itu.ch>
In-Reply-To: <499d71de.08b6660a.6012.ffffe5be@mx.google.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Liaison from ITU-T SG 16
Thread-Index: AcmSoUqeNEHP41s+TTuMifgdZpPFjgCk8X5w
References: <499d71de.08b6660a.6012.ffffe5be@mx.google.com>
From: <simao.campos@itu.int>
To: <ron.even.tlv@gmail.com>, <avt@ietf.org>
X-OriginalArrivalTime: 22 Feb 2009 21:34:13.0153 (UTC) FILETIME=[4E051110:01C99535]
Cc: fluffy@cisco.com, tom.taylor@rogers.com, sob@harvard.edu
Subject: Re: [AVT] Liaison from ITU-T SG 16
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: Sun, 22 Feb 2009 21:34:07 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C99535.4D7EC49A
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear all,
=20
In reference to the attachment to Liaison Statement, I have made it
available at:
http://wftp3.itu.int/av-arch/MM-framework/ls006-16-att1-Draft8GMDCSPNE.p
df
=20
(no password needed).
=20
Best regards,
Simao

________________________________

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Roni Even
Sent: 19 February 2009 15:50
To: 'IETF AVT WG'
Cc: fluffy@cisco.com; 'Tom Taylor'; sob@harvard.edu
Subject: [AVT] Liaison from ITU-T SG 16



Hi,

We have received the following liaison statement from ITU-T Study group
16.

They are looking for a solution that will enable them to exchange
capability of network elements that are in the bearer path (e.g. echo
cancellers) in order to optimize the processing done by them.

The full specification is available, we will look at how to make it
available.

Please look at the following text and see if you have any suggestions

=20

Thanks

Roni Even

AVT co-chair

=20

ITU-T Q18 of WP1/16 would like to request your assistance to identify if
there are existing protocols (e.g. RTP packet definitions) that can be
utilized to realize the dynamic coordination mechanism defined in the
draft new Recommendation ITU-T G.MDCSPNE over IP networks.

G.MDCSPNE defines a generic framework and protocol requirements for a
coordination mechanism intended to minimize undesirable interaction of
voice processing functions present on bearer paths of a communication
link, for the purpose of improving overall end-to-end voice quality.
Voice quality improvement is achieved through the usage of "capability
lists", exchanged among nodes on the bearer path, to identify the state
of signal processing functions (available/unavailable) over a call
connection.  This information is then used to refer to a common "rule
book" to cause the de-activation of redundant functions, and the
retention of the signal processing functions that are in most favourable
locations for improving voice quality. One important aspect of G.MDCSPNE
is that it allows dynamic coordination of signal processing
functions/devices during a call.  Dynamic coordination is needed in
response to changes in signal processing function availability due to,
for example, call topology changes such as call transfer or call
handover, all within the same call session. The generic capability list
format structure and the rules for de-activation and retention, based on
this state information, have been finalized in G.MDCSPNE. The scope of
G.MDCSPNE, however, does not cover the definition of protocols for the
exchange of capability list information on the bearer path to realize
the coordination mechanism over IP networks.

ITU-T Q18 of WP1/16 would like to request your assistance in identifying
if there is (are) existing standard specifications that could serve as a
vehicle for exchange of state of availability of voice processing
functions among nodes on a call-path, to satisfy the requirements for a
dynamic coordination mechanism over IP networks as contained in ITU-T
Q18/16 draft G.MDCSPNE.=20

ITU-T Q18/16 understands that modification of the generic capability
list format structure in G.MDCSPNE may be needed in order to take
advantage of existing specifications to implement the dynamic
coordination mechanism.  If such should be the case, ITU-T Q18/16 would
appreciate very much if you would provide the modifications needed. =20

For information purpose, attached please find the latest version of
G.MDCSPNE for your reference.  G.MDCSPNE is expected to go for consent
at the ITU-T October 2009 SG16 meeting and become an ITU-T standard
afterwards.


Attachment


-            Draft 8 of G.MDCSPNE "Mechanism for Dynamic Coordination of
Voice Enhancement SPNE"

=20


------_=_NextPart_001_01C99535.4D7EC49A
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16809" name=3DGENERATOR>
<STYLE>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:0in;
	margin-bottom:.0001pt;
	punctuation-wrap:simple;
	text-autospace:none;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
h1
	{mso-style-name:"Heading 1\,l1\,h1\,1st level\,Normal + Font\: =
Helvetica\,Bold\,Space Before 12 pt\,Not Bold\,le1\,heading 1\,1";
	mso-style-link:"Heading 1 Char\,l1 Char1\,h1 Char1\,1st level =
Char1\,Normal + Font\: Helvetica Char1\,Bold Char1\,Space Before 12 pt =
Char1\,Not Bold Char1\,le1 Char1\,heading 1 Char1\,1 Char1";
	margin-top:.25in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:39.7pt;
	margin-bottom:.0001pt;
	text-indent:-39.7pt;
	page-break-after:avoid;
	punctuation-wrap:simple;
	text-autospace:none;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	font-weight:normal;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.Heading1Char
	{mso-style-name:"Heading 1 Char\,l1 Char1\,h1 Char1\,1st level =
Char1\,Normal + Font\: Helvetica Char1\,Bold Char1\,Space Before 12 pt =
Char1\,Not Bold Char1\,le1 Char1\,heading 1 Char1\,1 Char1";
	mso-style-link:"Heading 1\,l1\,h1\,1st level\,Normal + Font\: =
Helvetica\,Bold\,Space Before 12 pt\,Not Bold\,le1\,heading 1\,1";
	font-family:"Times New Roman","serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D312303221-22022009><FONT =
face=3D"Courier New"=20
color=3D#0000ff size=3D2><EM>Dear all,</EM></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D312303221-22022009><EM><FONT=20
face=3D"Courier New" color=3D#0000ff =
size=3D2></FONT></EM></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D312303221-22022009><EM><FONT=20
face=3D"Courier New" color=3D#0000ff size=3D2>In reference to the =
attachment to=20
Liaison Statement, I have made it available at:</FONT></EM></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D312303221-22022009><EM><FONT=20
face=3D"Courier New" color=3D#0000ff size=3D2><A=20
href=3D"http://wftp3.itu.int/av-arch/MM-framework/ls006-16-att1-Draft8GMD=
CSPNE.pdf">http://wftp3.itu.int/av-arch/MM-framework/ls006-16-att1-Draft8=
GMDCSPNE.pdf</A></FONT></EM></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D312303221-22022009><EM><FONT=20
face=3D"Courier New" color=3D#0000ff =
size=3D2></FONT></EM></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D312303221-22022009><EM><FONT=20
face=3D"Courier New" color=3D#0000ff size=3D2>(no password=20
needed).</FONT></EM></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D312303221-22022009><EM><FONT=20
face=3D"Courier New" color=3D#0000ff =
size=3D2></FONT></EM></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D312303221-22022009><EM><FONT=20
face=3D"Courier New" color=3D#0000ff size=3D2>Best =
regards,</FONT></EM></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D312303221-22022009><EM><FONT=20
face=3D"Courier New" color=3D#0000ff =
size=3D2>Simao</FONT></EM></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> avt-bounces@ietf.org=20
[mailto:avt-bounces@ietf.org] <B>On Behalf Of </B>Roni =
Even<BR><B>Sent:</B> 19=20
February 2009 15:50<BR><B>To:</B> 'IETF AVT WG'<BR><B>Cc:</B> =
fluffy@cisco.com;=20
'Tom Taylor'; sob@harvard.edu<BR><B>Subject:</B> [AVT] Liaison from =
ITU-T SG=20
16<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><SPAN lang=3DEN-GB>Hi,<o:p></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN lang=3DEN-GB>We have received the following =
liaison=20
statement from ITU-T Study group 16.<o:p></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN lang=3DEN-GB>They are looking for a solution =
that will=20
enable them to exchange capability of network elements that are in the =
bearer=20
path (e.g. echo cancellers) in order to optimize the processing done by=20
them.<o:p></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN lang=3DEN-GB>The full specification is =
available, we will=20
look at how to make it available.<o:p></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN lang=3DEN-GB>Please look at the following =
text and see if=20
you have any suggestions<o:p></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN lang=3DEN-GB><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal><SPAN lang=3DEN-GB>Thanks<o:p></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN lang=3DEN-GB>Roni Even<o:p></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN lang=3DEN-GB>AVT =
co-chair<o:p></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN lang=3DEN-GB><o:p>&nbsp;</o:p></SPAN></P>
<P class=3DMsoNormal><SPAN lang=3DEN-GB>ITU-T Q18 of WP1/16 would like =
to request=20
your assistance to identify if there are existing protocols (e.g. RTP =
packet=20
definitions) that can be utilized to realize the dynamic coordination =
mechanism=20
defined in the draft new Recommendation ITU-T G.MDCSPNE over IP=20
networks.<o:p></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN lang=3DEN-GB>G.MDCSPNE defines a generic =
framework and=20
protocol requirements for a coordination mechanism intended to minimize=20
undesirable interaction of voice processing functions present on bearer =
paths of=20
a communication link, for the purpose of improving overall end-to-end =
voice=20
quality.&nbsp; Voice quality improvement is achieved through the usage =
of=20
&#8220;capability lists&#8221;, exchanged among nodes on the bearer =
path, to identify the=20
state of signal processing functions (available/unavailable) over a call =

connection.&nbsp; This information is then used to refer to a common =
&#8220;rule book&#8221;=20
to cause the de-activation of redundant functions, and the retention of =
the=20
signal processing functions that are in most favourable locations for =
improving=20
voice quality. One important aspect of G.MDCSPNE is that it allows =
dynamic=20
coordination of signal processing functions/devices during a call.&nbsp; =
Dynamic=20
coordination is needed in response to changes in signal processing =
function=20
availability due to, for example, call topology changes such as call =
transfer or=20
call handover, all within the same call session. The generic capability =
list=20
format structure and the rules for de-activation and retention, based on =
this=20
state information, have been finalized in G.MDCSPNE. The scope of =
G.MDCSPNE,=20
however, does not cover the definition of protocols for the exchange of=20
capability list information on the bearer path to realize the =
coordination=20
mechanism over IP networks.<o:p></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN lang=3DEN-GB>ITU-T Q18 of WP1/16 would like =
to request=20
your assistance in identifying if there is (are) existing standard=20
specifications that could serve as a vehicle for exchange of state of=20
availability of voice processing functions among nodes on a call-path, =
to=20
satisfy the requirements for a dynamic coordination mechanism over IP =
networks=20
as contained in ITU-T Q18/16 draft G.MDCSPNE. <o:p></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN lang=3DEN-GB>ITU-T Q18/16 understands that =
modification=20
of the generic capability list format structure in G.MDCSPNE may be =
needed in=20
order to take advantage of existing specifications to implement the =
dynamic=20
coordination mechanism.&nbsp; If such should be the case, ITU-T Q18/16 =
would=20
appreciate very much if you would provide the modifications =
needed.&nbsp;=20
<o:p></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN lang=3DEN-GB>For information purpose, =
attached please=20
find the latest version of G.MDCSPNE for your reference.&nbsp; G.MDCSPNE =
is=20
expected to go for consent at the ITU-T October 2009 SG16 meeting and =
become an=20
ITU-T standard afterwards.<o:p></o:p></SPAN></P>
<H1><B><SPAN lang=3DEN-GB>Attachment<o:p></o:p></SPAN></B></H1>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 39.7pt; TEXT-INDENT: =
-39.7pt"><SPAN=20
lang=3DEN-GB>-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
Draft 8 of G.MDCSPNE &#8220;Mechanism for Dynamic Coordination of Voice =
Enhancement=20
SPNE&#8221;<o:p></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 11pt; FONT-FAMILY: =
'Calibri','sans-serif'"><o:p>&nbsp;</o:p></SPAN></P></DIV></BODY></HTML>

------_=_NextPart_001_01C99535.4D7EC49A--


From yangpeilin@huawei.com  Mon Feb 23 04:02:05 2009
Return-Path: <yangpeilin@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 2259F3A69F5 for <avt@core3.amsl.com>; Mon, 23 Feb 2009 04:02:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.142
X-Spam-Level: ***
X-Spam-Status: No, score=3.142 tagged_above=-999 required=5 tests=[AWL=-2.952,  BAYES_50=0.001, CN_BODY_35=0.339, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_52=0.6, J_CHICKENPOX_53=0.6, MIME_CHARSET_FARAWAY=2.45, RDNS_NONE=0.1]
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 HRnWqWtyPoCq for <avt@core3.amsl.com>; Mon, 23 Feb 2009 04:02:03 -0800 (PST)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 4ED313A6A3A for <avt@ietf.org>; Mon, 23 Feb 2009 04:02:03 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KFI00CQAPFMP3@szxga04-in.huawei.com> for avt@ietf.org; Mon, 23 Feb 2009 20:02:10 +0800 (CST)
Received: from huawei.com ([172.17.1.31]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KFI002HVPFMM9@szxga04-in.huawei.com> for avt@ietf.org; Mon, 23 Feb 2009 20:02:10 +0800 (CST)
Received: from [172.24.1.33] (Forwarded-For: [10.164.12.15]) by szxmc03-in.huawei.com (mshttpd); Mon, 23 Feb 2009 20:02:10 +0800
Date: Mon, 23 Feb 2009 20:02:10 +0800
From: Peilin YANG <yangpeilin@huawei.com>
In-reply-to: <81B9B88E2F9D574AA5328A85547CDE919B2D27@xmb-rtp-21d.amer.cisco.com>
To: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
Message-id: <f926e42779d91.79d91f926e427@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.14 (built Aug  8 2006)
Content-type: text/plain; charset=gb2312
Content-language: zh-CN
Content-transfer-encoding: quoted-printable
Content-disposition: inline
X-Accept-Language: zh-CN
Priority: normal
References: <49800f21.0305560a.6ffe.31c8@mx.google.com> <81B9B88E2F9D574AA5328A85547CDE919B2D27@xmb-rtp-21d.amer.cisco.com>
Cc: "Dave Oran \(oran\)" <oran@cisco.com>, Tom Taylor <tom.taylor@rogers.com>, IETF AVT WG <avt@ietf.org>, VAN CAENEGEM Tom <Tom.Van_Caenegem@alcatel-lucent.be>
Subject: Re: [AVT] New draft on rapid synchronization
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: Mon, 23 Feb 2009 12:02:05 -0000

Dear Bill=2C

Thank you very much for your review=2E Please see my inline response=2E =


I will be happy to explore these issues further with you=2E And I also ho=
pe I can meet and discuss with you in SF meeting if the Consulate General=
 in Shanghai can grant an American visa to me=2E

Kindly regards=2C

Peilin

*************************************************************************=
*****************
 This email and its attachments contain confidential information from HUA=
WEI=2C which is intended only for the person or entity whose address is l=
isted above=2E Any use of the information contained here in any way (incl=
uding=2C but not limited to=2C total or partial disclosure=2C reproductio=
n=2C or dissemination) by persons other than the intended recipient(s) is=
 prohibited=2E If you receive this email in error=2C please notify the se=
nder by phone or email
 immediately and delete it!
 ************************************************************************=
*****************

----- =D4=AD=D3=CA=BC=FE -----
=B7=A2=BC=FE=C8=CB=3A =22Bill Ver Steeg (versteb)=22 =3Cversteb=40cisco=2E=
com=3E
=C8=D5=C6=DA=3A =D0=C7=C6=DA=C1=F9=2C =B6=FE=D4=C2 21=C8=D5=2C 2009 =C9=CF=
=CE=E72=3A32
=D6=F7=CC=E2=3A Re=3A =5BAVT=5D New draft on rapid synchronization
=CA=D5=BC=FE=C8=CB=3A Roni Even =3Cron=2Eeven=2Etlv=40gmail=2Ecom=3E=2C O=
rit Levin =3Coritl=40microsoft=2Ecom=3E=2C VAN CAENEGEM Tom =3CTom=2EVan=5F=
Caenegem=40alcatel-lucent=2Ebe=3E=2C =22Dave Oran (oran)=22 =3Coran=40cis=
co=2Ecom=3E=2C =22Ali C=2E Begen (abegen)=22 =3Cabegen=40cisco=2Ecom=3E
=B3=AD=CB=CD=3A Tom Taylor =3Ctom=2Etaylor=40rogers=2Ecom=3E=2C IETF AVT =
WG =3Cavt=40ietf=2Eorg=3E

=3E =

=3E =

=3E This note is in response to =22Extensions to RTCP for Rapid
=3E Synchronization draft-peilin-avt-rtp-burst-00=2Etxt=22 from P=2E Yang=
 =

=3E and B
=3E Lei=2E It is encouraging to see that the authors agree with the broad=

=3E methodology of the previous drafts around rapid acceleration of
=3E synchronization RTP multicast sessions=2E Hopefully we are =

=3E converging on a
=3E common solution=2E There are some areas of this draft that I need som=
e
=3E clarification on =2C though=2E
=3E =

=3E Steps 1-3 appear to be functionally equivalent to the flows previousl=
y
=3E described=2E As previously stated=2C this is a promising step=2E
=3E =

=3E In step 4=2C the receiver does an analysis of the incoming unicast bu=
rst
=3E to determine the optimum acceleration rate=2E The underlying assumpti=
on
=3E appears to be that packet loss is congestion driven=2E How does this
=3E method behave if the loss is due to other sources=2C such as noise =

=3E on the
=3E last mile plant=3F Can the receiver differentiate between congestive =

=3E lossand non-congestive loss=3F I have seen some analysis that claims =

=3E to be
=3E able to differentiate between the two types of loss=2C but it is not =

=3E clear(to me) if this is assumed in this case=2E
=3E =

=3E Clearly=2C if the link is driven into saturation=2C loss will result=2E=
 I
=3E would also like to understand the mechanism by which the RR and RS
=3E recover from deterministic (congestion-based) loss=2E I have personal=
ly
=3E been using a mental model in which the loss rate during =

=3E acceleration is
=3E approximately the same as any other time on the network=2C and many
=3E (most=3F) acceleration bursts will complete without the need for
=3E additional repair packets=2E To be honest=2C I have not given much th=
ought
=3E to a model in which there may be deterministic loss on every channel
=3E change=2E What impact does this have on the scalability of the system=
=3F
=3E =

=3E I also realize that I have been assuming a model in which the
=3E acceleration flows can=27t cause congestive loss in a video flow - =

=3E eitherthrough admission control or by using different QOS markings =

=3E for the two
=3E flows=2E More on this in my questions about step 10=2E
=3E =


Peilin=3A The behavior of optimizing acceleration rate is driven by packe=
t loss=2E In fact the rapid synchronization RTP multicast sessions will a=
pply to various network conditions including admission control and QoS as=
 you said=2E I have tested the model with the optimum acceleration rate i=
n the different network conditions=2E The Error resilience mechanism shou=
ld enable a small packet loss which may help with the case when raising t=
he rate may ca
use packet loss=2E
The rapid acceleration synchronization is temporary=2E It is considerable=
 whether network providers are willing to design admission control policy=
 only for rapid acceleration synchronization=2E My view is that it is mor=
e appropriate for rapid acceleration synchronization to contend the bandw=
idth resources=2EIf admission control is considered=2C I think=2C its pol=
icy cannot be only for rapid acceleration synchronization=2E Maybe per ho=
me has a sort of p
olicy=2E In addition=2C my view is that we cannot assume a model that onl=
y works when admission control and QoS are used=2E  =


=3E In steps 6-7=2C there appears to be a deterministic round-trip-time =

=3E delaybetween the sender catching up to realtime and the cessation =

=3E of the
=3E unicast flow=2E In the previous models=2C the design goal is have the=

=3E unicast flow cease at approximately the same time as it catches up to=

=3E the multicast flow at the receiver=2E I am trying to understand the
=3E relative merits of having a handshake (with its resultant RTT-scale
=3E delay) and pre-signaling the transition=2E  I am particularly interes=
ted
=3E in the behavior when one or more of the packets in the handshake are
=3E dropped=2E

Peilin=3A Yes=2C you are right=2C it is possible one or more of the packe=
ts in the handshake are dropped=2E This issue surely happened in the test=
 though its probability is very low=2E In order to reduce the probability=
 of the packets=2C once unicast burst media stream is synchronized with m=
ulticast media stream=2C RS will first decreases its transmitting bitrate=
 to a lower rate=2C and then send the shandshake message to RS to join th=
e multicast session an
d terminate the unicast burst media stream=2E In case the shandshake mess=
age still loses=2Cthe lower rate can hint the RS to join the multicast se=
ssion and terminate the unicast burst media stream=2E =


=3E =

=3E In step 10=2C the receiver assumes that the steady state found in =

=3E previousmulticast synchronization attempts is a good starting =

=3E point=2E I am also
=3E interested in this stage of the proposal=2E I have been assuming =

=3E that the
=3E channel is fairly dynamic=2C with other devices contending for the
=3E bandwidth resources=2E In some cases=2C the video is from the same QO=
S =

=3E poolas acceleration bandwidth and is thus subject to admission =

=3E control=2E In
=3E this case=2C the maximum rate can be determined directly=2E In other =

=3E cases=2Cthe video is in a different (hopefully higher) QOS pool than =
the
=3E acceleration data=2E In this case=2C the acceleration burst is conten=
ding
=3E with other (presumably rate-adaptive) flows=2E When contending with =

=3E otherrate adaptive flows=2C it is not clear that the available =

=3E bandwidth of the
=3E bottleneck link is the same as the last instantiation of the protocol=
=2E
=3E For most of the modeling I have been doing=2C I have been assuming th=
at
=3E rate - adaptive  flows do not compete with multicast video flows =

=3E due to
=3E the detrimental effects of of congestive packet loss on video=2E Perh=
aps
=3E this assumption is core to my questions earlier in this note=2E
=3E =


Peilin=3A I consider the issue many times and also want to look for a bet=
ter way=2E But I cannot=2E Because in the test I found that the steady st=
ate known in previous multicast synchronization attempts can meet bitrate=
 and reduce too much loss due to the change of the conditions=2E But It c=
annot avoid the case of packets loss when user=27s request of multicast s=
ynchronization has long interval and the conditions also changes=2E I als=
o consider an aver
age speed instead of the last optimum speed=2E But It seems not better th=
an the last optimum speed=2E =


=3E =

=3E I look forward to exploring these issues further=2E
=3E =

=3E Bill VerSteeg
=3E =

=3E =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F
=3E =

=3E From=3A Roni Even =5Bmailto=3Aron=2Eeven=2Etlv=40gmail=2Ecom=5D =

=3E Sent=3A Wednesday=2C January 28=2C 2009 2=3A53 AM
=3E To=3A Bill Ver Steeg (versteb)=3B =27Orit Levin=27=3B =27VAN CAENEGEM=
 Tom=27=3B Dave
=3E Oran (oran)=3B Ali C=2E Begen (abegen)
=3E Cc=3A =27Tom Taylor=27=3B =27IETF AVT WG=27
=3E Subject=3A New draft on rapid synchronization
=3E =

=3E =

=3E =

=3E Hi guys=2C
=3E =

=3E Please note that
=3E http=3A//tools=2Eietf=2Eorg/id/draft-peilin-avt-rtp-burst-00=2Etxt is=
 =

=3E discussingthe same topic=2E
=3E =

=3E I suggest you review it and take this work into account=2E
=3E =

=3E Thanks
=3E =

=3E Roni Even
=3E =

=3E =

=3E =

=3E =

=3E =

=3E 

From root@core3.amsl.com  Mon Feb 23 09:15:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id DCEF13A6874; Mon, 23 Feb 2009 09:15:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090223171501.DCEF13A6874@core3.amsl.com>
Date: Mon, 23 Feb 2009 09:15:01 -0800 (PST)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-rtp-rfc3984bis-03.txt
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: Mon, 23 Feb 2009 17:15:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.


	Title           : RTP Payload Format for H.264 Video
	Author(s)       : Y. Wang, et al.
	Filename        : draft-ietf-avt-rtp-rfc3984bis-03.txt
	Pages           : 97
	Date            : 2009-02-23

This memo describes an RTP Payload format for the ITU-T 
Recommendation H.264 video codec and the technically identical 
ISO/IEC International Standard 14496-10 video codec, excluding the 
Scalable Video Coding (SVC) extension and the Multivew Video Coding 
extension, for which the RTP payload formats are defined elsewhere.  
The RTP payload format allows for packetization of one or more 
Network Abstraction Layer Units (NALUs), produced by an H.264 video 
encoder, in each RTP payload.  The payload format has wide 
applicability, as it supports applications from simple low bit-rate 
conversational usage, to Internet video streaming with interleaved 
transmission, to high bit-rate video-on-demand. 

This memo obsoletes RFC 3984.  Changes from RFC 3984 are summarized 
in section 18.  Issues on backward compatibility to RFC 3984 are 
discussed in section 17.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-rfc3984bis-03.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-avt-rtp-rfc3984bis-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-02-23090315.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Mon Feb 23 09:15:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id E1D3628C15A; Mon, 23 Feb 2009 09:15:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090223171501.E1D3628C15A@core3.amsl.com>
Date: Mon, 23 Feb 2009 09:15:01 -0800 (PST)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-rtp-svc-17.txt
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: Mon, 23 Feb 2009 17:15:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.


	Title           : RTP Payload Format for SVC Video
	Author(s)       : S. Wenger, et al.
	Filename        : draft-ietf-avt-rtp-svc-17.txt
	Pages           : 101
	Date            : 2009-02-23

This memo describes an RTP payload format for Scalable Video Coding 
(SVC) as defined in_Annex G of ITU-T Recommendation H.264, which is 
technically identical to Amendment 3 of ISO/IEC International 
Standard 14496-10.  The RTP payload format allows for packetization 
of one or more Network Abstraction Layer (NAL) units in each RTP 
packet payload, as well as fragmentation of a NAL unit in multiple 
RTP packets.  Furthermore, it supports transmission of an SVC stream 
over a single as well as multiple RTP sessions.  The payload format 
defines a new media subtype name "H264-SVC", but is still backwards 
compatible to [I-D.ietf-avt-rtp-rfc3984bis] since the base layer, 
when encapsulated in its own RTP stream, must use the H.264 media 
subtype name ("H264") and the packetization method specified in [I-
D.ietf-avt-rtp-rfc3984bis].  The payload format has wide 
applicability in videoconferencing, Internet video streaming, and 
high bit-rate entertainment-quality video, among others. 

 

Table of Contents 

Status of this Memo...............................................1 
Abstract..........................................................2

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-svc-17.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-avt-rtp-svc-17.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-02-23090426.I-D@ietf.org>


--NextPart--

From yekuiwang@huawei.com  Mon Feb 23 10:29:41 2009
Return-Path: <yekuiwang@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 3FE2F3A68BF for <avt@core3.amsl.com>; Mon, 23 Feb 2009 10:29:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 TlU-PZT8tpVT for <avt@core3.amsl.com>; Mon, 23 Feb 2009 10:29:40 -0800 (PST)
Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180]) by core3.amsl.com (Postfix) with ESMTP id 545A13A6847 for <avt@ietf.org>; Mon, 23 Feb 2009 10:29:40 -0800 (PST)
Received: from huawei.com (usaga04-in [172.18.4.101]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KFJ00FA57DXL2@usaga04-in.huawei.com> for avt@ietf.org; Mon, 23 Feb 2009 12:29:58 -0600 (CST)
Received: from W90946 ([10.51.0.88]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KFJ001OO7DT2E@usaga04-in.huawei.com> for avt@ietf.org; Mon, 23 Feb 2009 12:29:57 -0600 (CST)
Date: Mon, 23 Feb 2009 13:29:05 -0500
From: Ye-Kui Wang <yekuiwang@huawei.com>
In-reply-to: <20090223171501.DCEF13A6874@core3.amsl.com>
To: avt@ietf.org
Message-id: <158D7613BE5D4487A4F8B2FA8741CC4B@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcmV2ld9VIT0oVQhRY+nRmzMTvpw2wAB1xeg
References: <20090223171501.DCEF13A6874@core3.amsl.com>
Subject: Re: [AVT] I-D Action:draft-ietf-avt-rtp-rfc3984bis-03.txt
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: Mon, 23 Feb 2009 18:29:41 -0000

 
We have addressed all the WGLC comments sent to the mailing list. Here is a
summary of main changes related to -02:

- Updated the boiler template
- Updated the definitions of "default sub-profile" and "default level"
- Added an optional media type parameter, in-band-parameter-sets, to enable
a receiver to indicate that it needs in-band parameter sets
- In section 8.4 (parameter set considerations), added a reference of the
rules of in-band and out-of-band parameter sets in section 8.2.2
- Updated section 11 (IANA Consideration)
- Updated authors' addresses (Ye-Kui is now with Huawei Technologies)
- Updated sections 17 (Backward Compatibility to RFC 3984) and 18 (Changes
from RFC 3984)

Thanks again to everyone who has reviewed the draft and provided WGLC
comments!

BR, YK
(on behalf of all authors)

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On 
> Behalf Of Internet-Drafts@ietf.org
> Sent: Monday, February 23, 2009 12:15 PM
> To: i-d-announce@ietf.org
> Cc: avt@ietf.org
> Subject: [AVT] I-D Action:draft-ietf-avt-rtp-rfc3984bis-03.txt
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> This draft is a work item of the Audio/Video Transport 
> Working Group of the IETF.
> 
> 
> 	Title           : RTP Payload Format for H.264 Video
> 	Author(s)       : Y. Wang, et al.
> 	Filename        : draft-ietf-avt-rtp-rfc3984bis-03.txt
> 	Pages           : 97
> 	Date            : 2009-02-23
> 
> This memo describes an RTP Payload format for the ITU-T 
> Recommendation H.264 video codec and the technically 
> identical ISO/IEC International Standard 14496-10 video 
> codec, excluding the Scalable Video Coding (SVC) extension 
> and the Multivew Video Coding extension, for which the RTP 
> payload formats are defined elsewhere.  
> The RTP payload format allows for packetization of one or 
> more Network Abstraction Layer Units (NALUs), produced by an 
> H.264 video encoder, in each RTP payload.  The payload format 
> has wide applicability, as it supports applications from 
> simple low bit-rate conversational usage, to Internet video 
> streaming with interleaved transmission, to high bit-rate 
> video-on-demand. 
> 
> This memo obsoletes RFC 3984.  Changes from RFC 3984 are 
> summarized in section 18.  Issues on backward compatibility 
> to RFC 3984 are discussed in section 17.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-rfc3984
> bis-03.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail 
> reader implementation to automatically retrieve the ASCII 
> version of the Internet-Draft.
> 



From yekuiwang@huawei.com  Mon Feb 23 11:04:33 2009
Return-Path: <yekuiwang@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 B11EF3A69DF for <avt@core3.amsl.com>; Mon, 23 Feb 2009 11:04:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_26=0.6]
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 oFK4GKSokWnf for <avt@core3.amsl.com>; Mon, 23 Feb 2009 11:04:32 -0800 (PST)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id 7BA813A69DB for <avt@ietf.org>; Mon, 23 Feb 2009 11:04:32 -0800 (PST)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KFJ00HLI9019N@usaga02-in.huawei.com> for avt@ietf.org; Mon, 23 Feb 2009 11:04:50 -0800 (PST)
Received: from W90946 ([10.51.0.88]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KFJ00AWH8ZXYP@usaga02-in.huawei.com> for avt@ietf.org; Mon, 23 Feb 2009 11:04:49 -0800 (PST)
Date: Mon, 23 Feb 2009 14:04:03 -0500
From: Ye-Kui Wang <yekuiwang@huawei.com>
In-reply-to: <20090223171501.E1D3628C15A@core3.amsl.com>
To: avt@ietf.org
Message-id: <B895EFA328CC4EFEAC10C404D2933D9F@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcmV2qklreyITtTsT66iClhGwPmFPgACibHg
References: <20090223171501.E1D3628C15A@core3.amsl.com>
Subject: Re: [AVT] I-D Action:draft-ietf-avt-rtp-svc-17.txt
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: Mon, 23 Feb 2009 19:04:33 -0000

 
We have addressed all the WGLC comments sent to the mailing list, as well as
some comments for the 3984bis draft but also affecting this draft. Many
thanks again to all who have reviewed this draft and provided WGLC comments!

Here is a summary of our responses to all the WGLC comments:

******************************************************
*  Start of WGLC Comments and responses  *
******************************************************

*** Colin Perkins 1/17/09:

       As Roni mentioned, the abstract is too long. I suggest keeping the
first
       and last sentences, and deleting the rest.

Ok, done.

       In Section 1, on page 5, the informative note suggests that a MANE
can
       convert a media stream from SVC to H.264/AVC "simply by eliminating
RTP
       packets", provided the stream is structured in a particular way. This
is
       not correct: the MANE is an RTP translator, and so must follow the
rules
       defined in Section 7 of RFC 3550, which mandate rewriting RTCP to
match
       changes made to the RTP stream.

Ok, done.

	Similarly, RFC 3550 section 7 should be referenced from the last
	bullet point of Section 1.2.1, and from section 3.1.2 at the top of
	page 21.

Ok, done.

	Editorial: Section 4.7.1, bottom of page 35, do you mean figure 2,
	rather than figure 3?

Done.

	The discussion of NI-T and NI-TC packetization rules in section
5.2.1
	is unclear in places. In particular:

	- The paragraph after the bullet list on page 49 (starting "If a
            packet must be inserted for satisfying...") could be clarified.
RTP
            packets don't directly contain an NTP timestamp. It might be
better
            phrased as "...the inserted packet must have an RTP timestamp
that
            maps to the same wall-clock (NTP-format) time as the RTP
timestamp
            of a packet of the access unit..."

Ok, done.

	  - The discussion at the end of page 50 and start of page 51,
showing
              how to generate the timestamp for the inserted packet looks
              correct, but I'm not sure it's helpful. The calculation seems
to
              be that which a receiver would do to estimate the timestamp. A
              sender would, on the other hand, know the exact mapping from
              wall-clock (NTP) time to RTP time, and so doesn't need to
              calculate the correct offset from the RTCP SR packets.

We considered that this calculation may have to be done be a MANE, and
that's why it was included. The text is left as-is.

	     - It would be helpful, I think, if section 5.2.1 explained that
                 the mapping between wall-clock (NTP format) timestamps and
RTP
                 timestamps is conveyed from sender to receiver using RTCP
SR
                 packets, or the RTP proposed header extensions.

Ok, done.

	Following on from this, the informative note in section 6.2.1 (page
	54) would perhaps be clearer written as "The mapping between RTP and
	NTP format timestamps is conveyed in RTCP SR packets. In addition,
the
	mechanisms for faster media timestamp synchronisation discussed in
	[...] may be used to speed to acquisition of the RTP-to-wall-clock
	mapping".

Ok, done. We moved the changed informative note to section 5.2.1.

	Also in section 6.2.1, second bullet point on page 55, clarify that
	the "media timestamp" is the NTP-format timestamp derived from the
RTP
	timestamps of the NAL units.

Ok, done.

	Section 7.2.3 discusses how to signal multi-session transmissions of
	SVC in SDP. RFC 4566 section 5.7 defines an alternative mechanism to
	signal such sessions. Is it legal for that alternative to be used?
If
	so, if should be referenced, if not, this draft should explicitly
	prohibit that use.

Done. We explicitly prohibited it.

       Section 11.6 disallows "SSRC multiplexing", but the discussion of MST
in
       section 1.2.2 seems to allow it. I see no reason to disallow it.

Section deleted, since it discusses technical background- it's not an
example, and it's not a specification item.


*** Roni Even (Sri Dharmasanam), 1/16/09:

      The paragraph "The term "layer" is used in various ..." can be moved
      higher up so that its clarified sooner before being used in the doc.

OK, done.

      What does "forbidden_zero_bit" mean and how is it diff from
      "reserved_one_bit" aside from the fact that one must be zero and the
      other one?

These are specified by the SVC coding spec, the payload draft, we only
summarize them. The situation in the coding spec is as follows. The
"forbidden_zero_bit" is specified there as "unspecified", and
"reserved_one_bit" is specified as "reserved". System specs, e.g. RTP
payload format, can specify those fields unspecified in the coding spec, but
must never touch those fields reservied in the coding spec. The value being
zero or one may be randomly chosen, and may also be chosen to avoid
emulation of start codes. 

       "MANEs can aggregate multiple RTP streams, possibly from multiple RTP
      sessions". Not sure if a clear distinction of RTP stream and RTP
session
      has been made.

The distinction is clear per RFC 3550. There may multiple RTP streams
involved one RTP session, wherein all the RTP streams share the same SSRC
value space.


*** Jonathan Lennox, 1/16/09

     Section 4.9 (PACSI), p. 38, first full paragraph following the figure:
     As mentioned later, the bits S and E are defined if the bit Y is 1, not
     if the bit X is 1.  I suggest the wording:

     The bits A, P, and C are specified only if the bit X is equal to 1.
The
     fields TL0PICIDX and IDRPICID are present, and the bits S and E are
     specified, only if the bit Y is equal to 1.

Ok, done.

     Section 5.1 (Packetization rules for SST), p. 47, Paragraph 3
     (Informative note):  This note should mention NI-MTAP as well.

Ok, done.

     Section 7.2.1 (Mapping of Payload Type Parameters to SDP):  I believe
it
     would be useful to be able to represent sprop-scalability-info and
     sprop-operation-point-info in the fmtp source attribute as well.  I
     don't currently see any motivation for including
     sprop-no-NAL-reordering-required or sprop-avc-ready in the fmtp source
     attribute, but they might be worth considering.

Ok, we have enabled all the four parameters to be source specific.

     Editorial: Section 1.1.2, p. 7, third para, last line:
     "conforming to one or more of the profile specified in"... should be
     "profiles"

Ok, done.

     Section 4.3, p. 26, 2nd paragraph: "Fragment Unit" should be
     "Fragmentation Unit".

Ok, done.

******************************************************
*  End of WGLC Comments and responses    *
******************************************************

BR, YK
(on behalf of all authors)

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On 
> Behalf Of Internet-Drafts@ietf.org
> Sent: Monday, February 23, 2009 12:15 PM
> To: i-d-announce@ietf.org
> Cc: avt@ietf.org
> Subject: [AVT] I-D Action:draft-ietf-avt-rtp-svc-17.txt
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> This draft is a work item of the Audio/Video Transport 
> Working Group of the IETF.
> 
> 
> 	Title           : RTP Payload Format for SVC Video
> 	Author(s)       : S. Wenger, et al.
> 	Filename        : draft-ietf-avt-rtp-svc-17.txt
> 	Pages           : 101
> 	Date            : 2009-02-23
> 
> This memo describes an RTP payload format for Scalable Video Coding
> (SVC) as defined in_Annex G of ITU-T Recommendation H.264, 
> which is technically identical to Amendment 3 of ISO/IEC 
> International Standard 14496-10.  The RTP payload format 
> allows for packetization of one or more Network Abstraction 
> Layer (NAL) units in each RTP packet payload, as well as 
> fragmentation of a NAL unit in multiple RTP packets.  
> Furthermore, it supports transmission of an SVC stream over a 
> single as well as multiple RTP sessions.  The payload format 
> defines a new media subtype name "H264-SVC", but is still 
> backwards compatible to [I-D.ietf-avt-rtp-rfc3984bis] since 
> the base layer, when encapsulated in its own RTP stream, must 
> use the H.264 media subtype name ("H264") and the 
> packetization method specified in [I- 
> D.ietf-avt-rtp-rfc3984bis].  The payload format has wide 
> applicability in videoconferencing, Internet video streaming, 
> and high bit-rate entertainment-quality video, among others. 
> 
>  
> 
> Table of Contents 
> 
> Status of this Memo...............................................1
> Abstract..........................................................2
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-svc-17.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail 
> reader implementation to automatically retrieve the ASCII 
> version of the Internet-Draft.
> 



From tom.taylor@rogers.com  Mon Feb 23 13:31:35 2009
Return-Path: <tom.taylor@rogers.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 3C3E628C13E for <avt@core3.amsl.com>; Mon, 23 Feb 2009 13:31:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.39
X-Spam-Level: 
X-Spam-Status: No, score=-0.39 tagged_above=-999 required=5 tests=[AWL=-0.391,  BAYES_50=0.001]
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 tUZnhFlPw1ji for <avt@core3.amsl.com>; Mon, 23 Feb 2009 13:31:34 -0800 (PST)
Received: from smtp103.rog.mail.re2.yahoo.com (smtp103.rog.mail.re2.yahoo.com [206.190.36.81]) by core3.amsl.com (Postfix) with SMTP id 4AC1A3A67E6 for <avt@ietf.org>; Mon, 23 Feb 2009 13:31:31 -0800 (PST)
Received: (qmail 54208 invoked from network); 23 Feb 2009 21:31:49 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding; b=18w1wgMCj84A9zazGxiFCLmrOAERpm5e2D7AD6RI+/glIkwa7l5wm89h995KNi7UBWLfSuqYzalzLiiyKSHNVyh8F9vv6/DLhok9KzwtGze3zrEfPhqFrUlLwotL9v0sVZbej6MkdqT9TmFQSY+S8k7LdBpaQscPQp9bbK1nMC4= ; 
Received: from unknown (HELO ?192.168.0.101?) (tom.taylor@72.140.46.24 with plain) by smtp103.rog.mail.re2.yahoo.com with SMTP; 23 Feb 2009 21:31:49 -0000
X-YMail-OSG: W0JP4OIVM1m_akFumkSkUiccZHuWP0lfg.MzrVloYhsVi9gBvnuasPyoveMklR_6aA--
X-Yahoo-Newman-Property: ymail-3
Message-ID: <49A315C5.6090105@rogers.com>
Date: Mon, 23 Feb 2009 16:31:49 -0500
From: Tom Taylor <tom.taylor@rogers.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [AVT] Additional WGLC review of 3984bis and SVC drafts
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: Mon, 23 Feb 2009 21:31:35 -0000

We will have a one-week additional WGLC review of the latest versions of the 
3984bis and SVC drafts:

draft-ietf-avt-rtp-rfc3984bis-03.txt, and
draft-ietf-avt-rtp-svc-17.txt

Please send any further comments to the authors and the list.

Thanks,
Tom Taylor

From ron.even.tlv@gmail.com  Wed Feb 25 00:50:40 2009
Return-Path: <ron.even.tlv@gmail.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 9BC8F3A679F for <avt@core3.amsl.com>; Wed, 25 Feb 2009 00:50:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 ggXAlYNuFhGZ for <avt@core3.amsl.com>; Wed, 25 Feb 2009 00:50:33 -0800 (PST)
Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.187]) by core3.amsl.com (Postfix) with ESMTP id 72BA03A6781 for <avt@ietf.org>; Wed, 25 Feb 2009 00:50:32 -0800 (PST)
Received: by mu-out-0910.google.com with SMTP id w9so2094353mue.9 for <avt@ietf.org>; Wed, 25 Feb 2009 00:50:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:subject:date :message-id:mime-version:content-type:x-mailer:thread-index :content-language; bh=chNK5B8VFR3ozbbb+kIxZrm87ByjR35cemt7lP3L33Q=; b=d+MoJ8E+krlZTc/VWJc/G10EwOUFoU1pmvY9mZulwJhF2Z/uCluQlLzlPoLB5ocDqg ruH+qv1SnqK7Z7FGrBgEpF7eU4pn3j2TxfErHo3OwEH2n4tTg+RPwW2+NoNAiEXEPJyk GvQFVwHe6J719V0PFmjEATyXoljk4moMfq2sA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; b=mgPJdzaxVHh7ohJ23/oLM9gylFJ+ptT9zHy3+hYF+MF6yTAO6FpDNd475LxizaK2Ec jmV2qULjZjZynK9q093qVACaERbpgWeJaUiPNaq1oX4NUgdxA/WgW92xI/KYv9rs8wBy ioLDNes31ej55Z/lrPKcw/lRYk9juIyxJZOTM=
Received: by 10.103.1.5 with SMTP id d5mr238655mui.29.1235551849475; Wed, 25 Feb 2009 00:50:49 -0800 (PST)
Received: from windows8d787f9 (bzq-79-182-130-108.red.bezeqint.net [79.182.130.108]) by mx.google.com with ESMTPS id y37sm922672mug.23.2009.02.25.00.50.45 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 25 Feb 2009 00:50:49 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'IETF AVT WG'" <avt@ietf.org>
Date: Wed, 25 Feb 2009 10:48:56 +0200
Message-ID: <49a50669.25e2660a.2d60.ffffe066@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_013D_01C99736.AB152E50"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcmXJeSp+21b2RKSS1CdVmA76vUBTQ==
Content-Language: en-us
Cc: avt-chairs@tools.ietf.org
Subject: [AVT] AVT WG requests for agenda time in SF (IETF 74)
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, 25 Feb 2009 08:50:40 -0000

This is a multipart message in MIME format.

------=_NextPart_000_013D_01C99736.AB152E50
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

 

If you wish to have agenda time at the upcoming meeting in San Francisco ,
please send an agenda request to the chairs, before March 10th.

 

 

We have two time slots:

 

1. Monday  March 23    13:00 - 15:00

 

2. Thursday March 26     15:10 - 16:10

 

 

 

Please note that the time slots are not final and may change. The final
agenda for the meeting will be published March 2nd.

 

The meeting time is intended for the following:

 

 

- Discussion of important drafts fundamental for the complete RTP framework.

 

- Discussion of issues that hasn't been possible to resolve on the mailing
list.

 

- Discussion of new work that falls outside of our current charter.

 

- Discussion of important AVT relevant work in other WGs

 

 

So if you want time for discussing your issues in AVT. Then you are required
to request time. These request shall contain the below information. 

 

 

 

A. Presentation Title:

 

B. Name of presenter:

 

C. Draft Reference(s):

 

D. Requested amount of time in minutes:

 

 

 

Thanks

 

Tom Taylor & Roni Even

AVT Chairs

 

 


------=_NextPart_000_013D_01C99736.AB152E50
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>Hi,<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>If you wish to have agenda time at the =
upcoming
meeting in San Francisco , please send an agenda request to the chairs, =
before March
10th.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>We have two time =
slots:<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>1. Monday &nbsp;March =
23&nbsp;&nbsp;&nbsp; 13:00
- 15:00<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>2. Thursday March 26 &nbsp;&nbsp; =
&nbsp;15:10
&#8211; 16:10<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>Please note that the time slots are =
not final
and may change. The final agenda for the meeting will be published March =
2nd.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>The meeting time is intended for the
following:<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>- Discussion of important drafts =
fundamental
for the complete RTP framework.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>- Discussion of issues that hasn't =
been possible
to resolve on the mailing list.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>- Discussion of new work that falls =
outside
of our current charter.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>- Discussion of important AVT relevant =
work
in other WGs<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>So if you want time for discussing =
your
issues in AVT. Then you are required to request time. These request =
shall
contain the below information. <o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>A. Presentation =
Title:<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>B. Name of =
presenter:<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>C. Draft =
Reference(s):<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>D. Requested amount of time in =
minutes:<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>Thanks<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;
font-family:"Arial","sans-serif"'>Tom Taylor &amp; Roni =
Even<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>AVT
Chairs<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p>

</div>

</body>

</html>

------=_NextPart_000_013D_01C99736.AB152E50--


From Berlizova@spiritDSP.com  Wed Feb 25 04:25:33 2009
Return-Path: <Berlizova@spiritDSP.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 984403A6A98 for <avt@core3.amsl.com>; Wed, 25 Feb 2009 04:25:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_35=0.6]
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 QIrHSNhME3Gm for <avt@core3.amsl.com>; Wed, 25 Feb 2009 04:25:26 -0800 (PST)
Received: from mail3.spiritcorp.com (mail3.spiritcorp.com [85.13.194.167]) by core3.amsl.com (Postfix) with ESMTP id 52EDB3A6AB7 for <avt@ietf.org>; Wed, 25 Feb 2009 04:25:24 -0800 (PST)
Received: from mail-srv.spiritcorp.com (mail-srv.spiritcorp.com [192.168.125.3]) by mail3.spiritcorp.com (8.13.8/8.14.2) with SMTP id n1PCPe55083527; Wed, 25 Feb 2009 15:25:40 +0300 (MSK) (envelope-from Berlizova@spiritDSP.com)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C99744.282CDC40"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Wed, 25 Feb 2009 15:25:33 +0300
Message-ID: <AA5A65FC22B6F145830AC0EAC7586A6C0488BDD6@mail-srv.spiritcorp.com>
In-Reply-To: <4997da79.1ade660a.0db8.1490@mx.google.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on IPMR payload
Thread-Index: AcmPTBji13HCCumgSqCPG6+njnvyNwH9cnDQ
References: <4997da79.1ade660a.0db8.1490@mx.google.com>
From: "Elena Berlizova" <Berlizova@spiritDSP.com>
To: "Roni Even" <ron.even.tlv@gmail.com>, "IETF AVT WG" <avt@ietf.org>
X-Scanned-By: MIMEDefang 2.64 on 192.168.125.15
X-Mailman-Approved-At: Wed, 25 Feb 2009 08:14:39 -0800
Cc: Slava Borilin <Borilin@spiritDSP.com>
Subject: Re: [AVT] Comments on IPMR payload
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, 25 Feb 2009 12:25:34 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C99744.282CDC40
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hello,

=20

We have just requested for submission the Internet-Draft "RTP Payload
Format for IP-MR Speech Codec draft-ietf-avt-rtp-ipmr-02.txt"
http://www.ietf.org/proceedings/staging/draft-ietf-avt-rtp-ipmr-02.txt=20

=20

The submission status is here
https://datatracker.ietf.org/idst/status.cgi?submission_id=3D12719.=20

=20

As far as the comments concerns:

=20

1.       The document MUST have a IANA consideration section. You can
add it as section 5, currently missing

[SPIRIT DSP] added

2.      In the introduction section I suggest you add some text
describing the codec.=20

[SPIRIT DSP]added

3.      In section 2.1.2 when describing R "If R=3D0 then speech TOC is
the last section of the payload header". This sentence is not inline
with the payload format described above. TOC is not part of the header.

[SPIRIT DSP] ok, fixed

4.      In section 2.1.2 when describing E bit you mention teRxFrType,
what is this, there is no reference to this parameter.

[SPIRIT DSP] removed

5.      The last sentence of 2.1.5 you mention special flag, what is
special flag?

[SPIRIT DSP] removed

In 2.1.7 you say that GetFrameInfo is described in [1] yet [1] does not
point to a document but to a web page where I could not see the
information.
[SPIRIT DSP] removed

6.      In 2.2.1 the last sentence you add a padding but A=3D0 in the
header so why padding.

[SPIRIT DSP] We suggest that payload itself shoud be byte-aligned. Even
if data sections inside payload are not aligned. We think this is common
practice, for example ARM
(http://tools.ietf.org/html/draft-ietf-avt-rtp-amr-bis-06#section-4.3.5.
1
<http://tools.ietf.org/html/draft-ietf-avt-rtp-amr-bis-06#section-4.3.5.
1> )

7.      In 2.2.2 the text says that BR and CR =3D0 but the diagram has
BR=3D1 and CR=3D2

[SPIRIT DSP] fixed

8.      Section 2.2.3 specifies extended format but does not have any
description of when it is used or any  optional payload extension. If
there are none yet you should not specify it at this time and when you
have optional payload extension you can add it to the draft.

[SPIRIT DSP] ok, let's remove it

9.      Section 3, media subtype registration is not complete, the
registration template in defined in RFC 4288 and RFC 4855. You can look
at an example in other payload specifications.

[SPIRIT DSP] fixed

10.   Section 3.1 change the title to  Registration of media subtype
audio/ip-mr_v2.5

[SPIRIT DSP] fixed

11.   Is having v2.5 hints that you will need to register other
versions. In this case I suggest you add an optional payload subtype
parameter version and have the default as 2.5.

[SPIRIT DSP] We think we need to keep 'audio/ip-mr_v2.5' because some
customers already deploy it.

=20

We look forward your recommendations.=20

Yours sincerely=20
Elena Berlizova=20

________________________________

From: Roni Even [mailto:ron.even.tlv@gmail.com]=20
Sent: Sunday, February 15, 2009 12:02 PM
To: 'IETF AVT WG'
Cc: Elena Berlizova; Slava Borilin
Subject: Comments on IPMR payload

=20

Hi,

I reviewed the draft I have some comments mostly editorial.

As a general comment you can look at one of the latest payload
specification approved like G.719 as an example. Look also at the layout
like to document headers and the table of contents

=20

These are the specific comments

=20

=20

12.   The document MUST have a IANA consideration section. You can add
it as section 5, currently missing

13.   In the introduction section I suggest you add some text describing
the codec.=20

14.   In section 2.1.2 when describing R "If R=3D0 then speech TOC is =
the
last section of the payload header". This sentence is not inline with
the payload format described above. TOC is not part of the header.

15.   In section 2.1.2 when describing E bit you mention teRxFrType,
what is this, there is no reference to this parameter.

16.   The last sentence of 2.1.5 you mention special flag, what is
special flag?

17.   In 2.1.7 you say that GetFrameInfo is described in [1] yet [1]
does not point to a document but to a web page where I could not see the
information.

18.   In 2.2.1 the last sentence you add a padding but A=3D0 in the =
header
so why padding.

19.   In 2.2.2 the text says that BR and CR =3D0 but the diagram has =
BR=3D1
and CR=3D2

20.   Section 2.2.3 specifies extended format but does not have any
description of when it is used or any  optional payload extension. If
there are none yet you should not specify it at this time and when you
have optional payload extension you can add it to the draft.

21.   Section 3, media subtype registration is not complete, the
registration template in defined in RFC 4288 and RFC 4855. You can look
at an example in other payload specifications.

22.   Section 3.1 change the title to  Registration of media subtype
audio/ip-mr_v2.5

23.   Is having v2.5 hints that you will need to register other
versions. In this case I suggest you add an optional payload subtype
parameter version and have the default as 2.5.

=20

=20

Regards

Roni Even


------_=_NextPart_001_01C99744.282CDC40
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40"
xmlns:ns0=3D"http://schemas.microsoft.com/office/2004/12/omml">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--p.MSOCOMMENTTEXT
	{mso-style-priority:99;}
li.MSOCOMMENTTEXT
	{mso-style-priority:99;}
div.MSOCOMMENTTEXT
	{mso-style-priority:99;}
span.MSOCOMMENTREFERENCE
	{mso-style-priority:99;}
a:link
	{mso-style-priority:99;}
span.MSOHYPERLINK
	{mso-style-priority:99;}
a:visited
	{mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
	{mso-style-priority:99;}
p.MSOPLAINTEXT
	{mso-style-priority:99;}
li.MSOPLAINTEXT
	{mso-style-priority:99;}
div.MSOPLAINTEXT
	{mso-style-priority:99;}
p.MSOACETATE
	{mso-style-priority:99;}
li.MSOACETATE
	{mso-style-priority:99;}
div.MSOACETATE
	{mso-style-priority:99;}
p.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
li.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
div.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
span.COMMENTTEXTCHAR
	{mso-style-priority:99;}
span.PLAINTEXTCHAR
	{mso-style-priority:99;}
span.BALLOONTEXTCHAR
	{mso-style-priority:99;}

 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Calibri;}
@font-face
	{font-family:Consolas;}
@font-face
	{font-family:"Arial CYR";
	panose-1:2 11 6 4 2 2 2 2 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
p.MsoCommentText, li.MsoCommentText, div.MsoCommentText
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	font-size:10.0pt;
	font-family:Calibri;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p
	{mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:Tahoma;}
span.CommentTextChar
	{font-family:Calibri;}
span.PlainTextChar
	{font-family:Consolas;}
span.BalloonTextChar
	{font-family:Tahoma;}
p.msolistparagraph, li.msolistparagraph, div.msolistparagraph
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Calibri;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:Calibri;
	color:windowtext;}
span.EmailStyle25
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:362443247;
	mso-list-type:hybrid;
	mso-list-template-ids:1613413642 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DRU link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Hello,<o:p></o:p>=
</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p>=
</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>We have just =
requested
for submission the Internet-Draft &#8220;RTP Payload Format for IP-MR =
Speech
Codec draft-ietf-avt-rtp-ipmr-02.txt&#8221; </span></font><span =
lang=3DEN-US><a
href=3D"http://www.ietf.org/proceedings/staging/draft-ietf-avt-rtp-ipmr-0=
2.txt">http://www.ietf.org/proceedings/staging/draft-ietf-avt-rtp-ipmr-02=
.txt</a>
<o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:
11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:
11.0pt'>The submission status is here <a
href=3D"https://datatracker.ietf.org/idst/status.cgi?submission_id=3D1271=
9">https://datatracker.ietf.org/idst/status.cgi?submission_id=3D12719</a>=
.
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:
11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:
11.0pt'>As far as the comments concerns:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:
11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>1.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>&nbsp;The document MUST have a IANA consideration section. =
You can
add it as section 5, currently missing<o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'margin-left:18.0pt'><b><i><font =
size=3D2
color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy;font-weight:bold;font-style:italic'>[SPIRIT DSP] =
</span></font></i></b><b><i><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy;font-weight:bold;font-style:italic'>added<o:p></o:p></span></f=
ont></i></b></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>2.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>In the introduction section I suggest you add some text =
describing
the codec. <o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'margin-left:18.0pt'><b><i><font =
size=3D2
color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy;font-weight:bold;font-style:italic'>[SPIRIT =
DSP]added</span></font></i></b><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>3.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>In section 2.1.2 when describing R &quot;If R=3D0 then =
speech TOC is
the last section of the payload header&quot;. This sentence is not =
inline with
the payload format described above. TOC is not part of the =
header.<o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'margin-left:18.0pt'><b><i><font =
size=3D2
color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy;font-weight:bold;font-style:italic'>[SPIRIT DSP] ok, =
fixed</span></font></i></b><font
size=3D2 color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;
font-family:Arial;color:navy'><o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>4.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>In section 2.1.2 when describing E bit you mention =
teRxFrType, what
is this, there is no reference to this parameter.<o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'margin-left:18.0pt'><b><i><font =
size=3D2
color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy;font-weight:bold;font-style:italic'>[SPIRIT DSP] =
removed</span></font></i></b><font
size=3D2 color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;
font-family:Arial;color:navy'><o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>5.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>The last sentence of 2.1.5 you mention special flag, what =
is special
flag?<o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'margin-left:18.0pt'><b><i><font =
size=3D2
color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy;font-weight:bold;font-style:italic'>[SPIRIT DSP] =
removed</span></font></i></b><font
size=3D2 color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;
font-family:Arial;color:navy'><o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'margin-left:18.0pt'><font size=3D2 =
face=3DCalibri><span
lang=3DEN-US style=3D'font-size:11.0pt'>In 2.1.7 you say that =
GetFrameInfo is
described in [1] yet [1] does not point to a document but to a web page =
where I
could not see the information.<br>
</span></font><b><i><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'>[SPIRIT DSP] removed</span></font></i></b><font =
size=3D2
color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy'><o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>6.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>In 2.2.1 the last sentence you add a padding but A=3D0 in =
the header
so why padding.<o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'margin-left:18.0pt'><b><i><font =
size=3D2
color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy;font-weight:bold;font-style:italic'>[SPIRIT DSP] We =
suggest
that payload itself shoud be byte-aligned. Even if data sections inside =
payload
are not aligned. We think this is common practice, for example ARM (<a
href=3D"http://tools.ietf.org/html/draft-ietf-avt-rtp-amr-bis-06#section-=
4.3.5.1"
title=3D"http://tools.ietf.org/html/draft-ietf-avt-rtp-amr-bis-06#section=
-4.3.5.1"><font
size=3D2 color=3Dnavy face=3DCalibri><span lang=3DRU =
style=3D'font-size:11.0pt;
font-family:Calibri;color:navy;text-decoration:none'>http://tools.ietf.or=
g/html/draft-ietf-avt-rtp-amr-bis-06#section-4.3.5.1</span></font></a>)</=
span></font></i></b><font
size=3D2 color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;
font-family:Arial;color:navy'><o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>7.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>In 2.2.2 the text says that BR and CR =3D0 but the diagram =
has BR=3D1
and CR=3D2<o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'margin-left:18.0pt'><b><i><font =
size=3D2
color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy;font-weight:bold;font-style:italic'>[SPIRIT DSP] =
fixed</span></font></i></b><font
size=3D2 color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;
font-family:Arial;color:navy'><o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>8.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>Section 2.2.3 specifies extended format but does not have =
any
description of when it is used or any&nbsp; optional payload extension. =
If
there are none yet you should not specify it at this time and when you =
have
optional payload extension you can add it to the =
draft.<o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'margin-left:18.0pt'><b><i><font =
size=3D2
color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy;font-weight:bold;font-style:italic'>[SPIRIT DSP] ok, =
let&#8217;s
remove it</span></font></i></b><font size=3D2 color=3Dnavy =
face=3DArial><span
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p></o:p></span=
></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>9.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>Section 3, media subtype registration is not complete, the
registration template in defined in RFC 4288 and RFC 4855. You can look =
at an
example in other payload specifications.<o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'margin-left:18.0pt'><b><i><font =
size=3D2
color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy;font-weight:bold;font-style:italic'>[SPIRIT DSP] =
fixed</span></font></i></b><font
size=3D2 color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;
font-family:Arial;color:navy'><o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>10.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>Section 3.1 change the title to &nbsp;Registration of media =
subtype
audio/ip-mr_v2.5<o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'margin-left:18.0pt'><b><i><font =
size=3D2
color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy;font-weight:bold;font-style:italic'>[SPIRIT DSP] =
fixed</span></font></i></b><font
size=3D2 color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;
font-family:Arial;color:navy'><o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>11.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>Is having v2.5 hints that you will need to register other =
versions.
In this case I suggest you add an optional payload subtype parameter =
version
and have the default as 2.5.<o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'margin-left:18.0pt'><b><i><font =
size=3D2
color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy;font-weight:bold;font-style:italic'>[SPIRIT DSP] We =
think we
need to keep &#8216;audio/ip-mr_v2.5&#8217; because some customers =
already
deploy it.</span></font></i></b><font size=3D2 color=3Dnavy =
face=3DArial><span
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:
11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>We look forward =
your
recommendations. <o:p></o:p></span></font></p>

<div>

<p><font size=3D2 color=3Dblack face=3D"Arial CYR"><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:"Arial CYR";color:black'>Yours =
sincerely</span></font><font
color=3Dnavy><span lang=3DEN-US style=3D'color:navy'> <br>
</span></font><st1:PersonName w:st=3D"on"><font size=3D2 color=3Dblack
 face=3D"Arial CYR"><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial CYR";
 color:black'>Elena Berlizova</span></font></st1:PersonName><font =
color=3Dnavy><span
lang=3DEN-US style=3D'color:navy'> </span></font><span =
lang=3DEN-US><o:p></o:p></span></p>

</div>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:
"Times New Roman"'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Tahoma'>
Roni Even [mailto:ron.even.tlv@gmail.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Sunday, February =
15, 2009
12:02 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'IETF AVT WG'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> <st1:PersonName =
w:st=3D"on">Elena
 Berlizova</st1:PersonName>; Slava Borilin<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Comments on IPMR =
payload</span></font><font
size=3D3 face=3D"Times New Roman"><span lang=3DEN-US =
style=3D'font-size:12.0pt;
font-family:"Times New Roman"'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:
11.0pt'>Hi,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:
11.0pt'>I reviewed the draft I have some comments mostly =
editorial.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:
11.0pt'>As a general comment you can look at one of the latest payload
specification approved like G.719 as an example. Look also at the layout =
like
to document headers and the table of =
contents<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:
11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:
11.0pt'>These are the specific comments<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:
11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:
11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>12.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>The document MUST have a IANA consideration section. You =
can add it
as section 5, currently missing<o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>13.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>In the introduction section I suggest you add some text =
describing
the codec. <o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>14.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>In section 2.1.2 when describing R &quot;If R=3D0 then =
speech TOC is
the last section of the payload header&quot;. This sentence is not =
inline with
the payload format described above. TOC is not part of the =
header.<o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>15.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>In section 2.1.2 when describing E bit you mention =
teRxFrType, what
is this, there is no reference to this parameter.<o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>16.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>The last sentence of 2.1.5 you mention special flag, what =
is special
flag?<o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>17.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>In 2.1.7 you say that GetFrameInfo is described in [1] yet =
[1] does
not point to a document but to a web page where I could not see the
information.<o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>18.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>In 2.2.1 the last sentence you add a padding but A=3D0 in =
the header
so why padding.<o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>19.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>In 2.2.2 the text says that BR and CR =3D0 but the diagram =
has BR=3D1
and CR=3D2<o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>20.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>Section 2.2.3 specifies extended format but does not have =
any
description of when it is used or any&nbsp; optional payload extension. =
If
there are none yet you should not specify it at this time and when you =
have
optional payload extension you can add it to the =
draft.<o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>21.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>Section 3, media subtype registration is not complete, the
registration template in defined in RFC 4288 and RFC 4855. You can look =
at an
example in other payload specifications.<o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>22.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>Section 3.1 change the title to &nbsp;Registration of media =
subtype
audio/ip-mr_v2.5<o:p></o:p></span></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:11.0pt'><span
style=3D'mso-list:Ignore'>23.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><span
lang=3DEN-US>Is having v2.5 hints that you will need to register other =
versions.
In this case I suggest you add an optional payload subtype parameter =
version
and have the default as 2.5.<o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:
11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:
11.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:
11.0pt'>Regards<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span lang=3DEN-US =
style=3D'font-size:
11.0pt'>Roni Even<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C99744.282CDC40--

From root@core3.amsl.com  Wed Feb 25 10:30:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 5099B28C288; Wed, 25 Feb 2009 10:30:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090225183001.5099B28C288@core3.amsl.com>
Date: Wed, 25 Feb 2009 10:30:01 -0800 (PST)
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-ipmr-02.txt
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, 25 Feb 2009 18:30:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.

	Title		: RTP Payload Format for SPIRIT IP-MR Speech Codec
	Author(s)	: A. Setsko
	Filename	: draft-ietf-avt-rtp-ipmr-02.txt
	Pages		: 11
	Date		: 2009-2-25
	
This document specifies the payload format for packetization of SPIRIT IP-MR encoded speech signals into the Real-time Transport Protocol (RTP). The payload format supports transmission of multiple frames per payload and introduced redundancy for robustness against packet loss.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-ipmr-02.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-avt-rtp-ipmr-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-2-25102423.I-D@ietf.org>


--NextPart--


From root@core3.amsl.com  Wed Feb 25 11:45:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 782CF28C2A4; Wed, 25 Feb 2009 11:45:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090225194501.782CF28C2A4@core3.amsl.com>
Date: Wed, 25 Feb 2009 11:45:01 -0800 (PST)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-rtcp-xr-postrepair-loss-01.txt
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, 25 Feb 2009 19:45:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.


	Title           : RTCP XR Report Block for Post-Repair Loss metric Reporting
	Author(s)       : G. Hunt, A. Clark
	Filename        : draft-ietf-avt-rtcp-xr-postrepair-loss-01.txt
	Pages           : 14
	Date            : 2009-02-25

This document defines an RTCP XR Report Block that allows the
reporting of a simple post-repair loss count metric for use in a
range of RTP applications.  It complements the pre-repair loss count
metric "cumulative number of packets lost" provided by RFC3550.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcp-xr-postrepair-loss-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-avt-rtcp-xr-postrepair-loss-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-02-25113436.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Wed Feb 25 11:45:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 7F32928C2D0; Wed, 25 Feb 2009 11:45:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090225194501.7F32928C2D0@core3.amsl.com>
Date: Wed, 25 Feb 2009 11:45:01 -0800 (PST)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-rtcp-xr-pdv-01.txt
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, 25 Feb 2009 19:45:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.


	Title           : RTCP XR Report Block for Packet Delay Variation Metric Reporting
	Author(s)       : G. Hunt, A. Clark
	Filename        : draft-ietf-avt-rtcp-xr-pdv-01.txt
	Pages           : 15
	Date            : 2009-02-25

This document defines an RTCP XR Report Block that allows the
reporting of Packet Delay Variation metrics for a range of RTP
applications.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcp-xr-pdv-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-avt-rtcp-xr-pdv-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-02-25113702.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Wed Feb 25 11:45:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 8296628C2D1; Wed, 25 Feb 2009 11:45:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090225194501.8296628C2D1@core3.amsl.com>
Date: Wed, 25 Feb 2009 11:45:01 -0800 (PST)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-rtcp-xr-meas-identity-01.txt
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, 25 Feb 2009 19:45:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.


	Title           : RTCP XR Report Block for Measurement Identity
	Author(s)       : G. Hunt, A. Clark
	Filename        : draft-ietf-avt-rtcp-xr-meas-identity-01.txt
	Pages           : 13
	Date            : 2009-02-25

This document defines an RTCP XR Report Block carrying parameters
which identify a measurement, to which one or more other RTCP XR
Report Blocks may refer.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcp-xr-meas-identity-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-avt-rtcp-xr-meas-identity-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-02-25113848.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Wed Feb 25 11:45:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 8F3BE28C2D3; Wed, 25 Feb 2009 11:45:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090225194501.8F3BE28C2D3@core3.amsl.com>
Date: Wed, 25 Feb 2009 11:45:01 -0800 (PST)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-rtcp-xr-loss-conceal-01.txt
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, 25 Feb 2009 19:45:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.


	Title           : RTCP XR Report Block for Loss Concealment metric Reporting
	Author(s)       : G. Hunt, A. Clark
	Filename        : draft-ietf-avt-rtcp-xr-loss-conceal-01.txt
	Pages           : 15
	Date            : 2009-02-25

This document defines an RTCP XR Report Block that allows the
reporting of Loss Concealment metrics primarily for audio
applications of RTP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcp-xr-loss-conceal-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-avt-rtcp-xr-loss-conceal-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-02-25114029.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Wed Feb 25 11:45:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 9302428C2D6; Wed, 25 Feb 2009 11:45:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090225194501.9302428C2D6@core3.amsl.com>
Date: Wed, 25 Feb 2009 11:45:01 -0800 (PST)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-rtcp-xr-jb-01.txt
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, 25 Feb 2009 19:45:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.


	Title           : RTCP XR Report Block for Jitter Buffer Metric Reporting
	Author(s)       : G. Hunt, A. Clark
	Filename        : draft-ietf-avt-rtcp-xr-jb-01.txt
	Pages           : 13
	Date            : 2009-02-25

This document defines an RTCP XR Report Block that allows the
reporting of Jitter Buffer metrics for a range of RTP applications.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcp-xr-jb-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-avt-rtcp-xr-jb-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-02-25114212.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Wed Feb 25 11:45:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id A5D8128C2D0; Wed, 25 Feb 2009 11:45:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090225194501.A5D8128C2D0@core3.amsl.com>
Date: Wed, 25 Feb 2009 11:45:01 -0800 (PST)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-rtcp-xr-discard-01.txt
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, 25 Feb 2009 19:45:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.


	Title           : RTCP XR Report Block for Discard metric Reporting
	Author(s)       : G. Hunt, A. Clark
	Filename        : draft-ietf-avt-rtcp-xr-discard-01.txt
	Pages           : 14
	Date            : 2009-02-25

This document defines an RTCP XR Report Block that allows the
reporting of a simple discard count metric for use in a range of RTP
applications.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcp-xr-discard-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-avt-rtcp-xr-discard-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-02-25114409.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Wed Feb 25 12:00:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 52D0828C161; Wed, 25 Feb 2009 12:00:00 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090225200001.52D0828C161@core3.amsl.com>
Date: Wed, 25 Feb 2009 12:00:01 -0800 (PST)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-rtcp-xr-delay-01.txt
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, 25 Feb 2009 20:00:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.


	Title           : RTCP XR Report Block for Delay metric Reporting
	Author(s)       : G. Hunt, A. Clark
	Filename        : draft-ietf-avt-rtcp-xr-delay-01.txt
	Pages           : 14
	Date            : 2009-02-25

This document defines an RTCP XR Report Block that allows the
reporting of Delay metrics for use in a range of RTP applications.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcp-xr-delay-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-avt-rtcp-xr-delay-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-02-25114512.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Wed Feb 25 12:00:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 5BA3D28C2DC; Wed, 25 Feb 2009 12:00:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090225200001.5BA3D28C2DC@core3.amsl.com>
Date: Wed, 25 Feb 2009 12:00:01 -0800 (PST)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-rtcp-xr-concsec-01.txt
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, 25 Feb 2009 20:00:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.


	Title           : RTCP XR Report Block for Concealed Seconds metric Reporting
	Author(s)       : G. Hunt, A. Clark
	Filename        : draft-ietf-avt-rtcp-xr-concsec-01.txt
	Pages           : 16
	Date            : 2009-02-25

This document defines an RTCP XR Report Block that allows the
reporting of Concealed Seconds metrics primarily for audio
applications of RTP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcp-xr-concsec-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-avt-rtcp-xr-concsec-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-02-25114648.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Wed Feb 25 12:00:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 7A8D428C2E0; Wed, 25 Feb 2009 12:00:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090225200001.7A8D428C2E0@core3.amsl.com>
Date: Wed, 25 Feb 2009 12:00:01 -0800 (PST)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-rtcp-xr-burst-gap-loss-01.txt
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, 25 Feb 2009 20:00:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.


	Title           : RTCP XR Report Block for Burst/Gap Loss metric Reporting
	Author(s)       : G. Hunt, A. Clark
	Filename        : draft-ietf-avt-rtcp-xr-burst-gap-loss-01.txt
	Pages           : 17
	Date            : 2009-02-25

This document defines an RTCP XR Report Block that allows the
reporting of Burst and Gap Loss metrics for use in a range of RTP
applications.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcp-xr-burst-gap-loss-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-avt-rtcp-xr-burst-gap-loss-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-02-25115108.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Wed Feb 25 12:00:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id C5B9B28C161; Wed, 25 Feb 2009 12:00:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090225200001.C5B9B28C161@core3.amsl.com>
Date: Wed, 25 Feb 2009 12:00:01 -0800 (PST)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-rtcp-xr-burst-gap-discard-01.txt
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, 25 Feb 2009 20:00:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.


	Title           : RTCP XR Report Block for Burst/Gap Discard metric Reporting
	Author(s)       : G. Hunt, A. Clark
	Filename        : draft-ietf-avt-rtcp-xr-burst-gap-discard-01.txt
	Pages           : 17
	Date            : 2009-02-25

This document defines an RTCP XR Report Block that allows the
reporting of Burst and Gap Discard metrics for use in a range of RTP
applications.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcp-xr-burst-gap-discard-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-avt-rtcp-xr-burst-gap-discard-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-02-25115238.I-D@ietf.org>


--NextPart--

From tom.taylor@rogers.com  Thu Feb 26 05:45:52 2009
Return-Path: <tom.taylor@rogers.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 3B43E3A692E for <avt@core3.amsl.com>; Thu, 26 Feb 2009 05:45:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[AWL=0.678,  BAYES_00=-2.599]
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 HDiQQcZ8vPn2 for <avt@core3.amsl.com>; Thu, 26 Feb 2009 05:45:51 -0800 (PST)
Received: from smtp106.rog.mail.re2.yahoo.com (smtp106.rog.mail.re2.yahoo.com [68.142.225.204]) by core3.amsl.com (Postfix) with SMTP id C18353A68F6 for <avt@ietf.org>; Thu, 26 Feb 2009 05:45:50 -0800 (PST)
Received: (qmail 12483 invoked from network); 26 Feb 2009 13:46:11 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=gZIu4Z0FP6OzCGLU7NgdV6nmiUXXmpd4ZEFlhmryQIGrPq0kQkYJO2H78RhW5jF5jiBH6o8QCbIyPaFgpaoI6WRU3bJXCBw2Z5RVNMr+98Ef40MwT/arwKlni09ib8vpPYydSbt85Key20JME/eFoXcKFnHam4lJyxPs/1ajzDA= ; 
Received: from unknown (HELO ?192.168.0.101?) (tom.taylor@72.140.46.24 with plain) by smtp106.rog.mail.re2.yahoo.com with SMTP; 26 Feb 2009 13:46:11 -0000
X-YMail-OSG: xoM6XkwVM1lMjnUqzCjkz9wLSF3BX9UPrPLarOjloS3byZIo.eDWNqCUODgb8.yMOw--
X-Yahoo-Newman-Property: ymail-3
Message-ID: <49A69D22.3060604@rogers.com>
Date: Thu, 26 Feb 2009 08:46:10 -0500
From: Tom Taylor <tom.taylor@rogers.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>
References: <49A65012.1050802@astri.org>
In-Reply-To: <49A65012.1050802@astri.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Fu Siu Ming Claudio <claudiof@astri.org>, Richard <richard@astri.org>
Subject: Re: [AVT] [MMUSIC] RTCP and RTCP XR report
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: Thu, 26 Feb 2009 13:45:52 -0000

Forwarded from MMUSIC list.

Richard wrote:
> Hi,
> 
> If the device supports both RTCP and RTCP XR, is there any rule 
> governing the following:
> 1) whether RTCP reports and RTCP XR reports can be sent together, either 
> as a compound packet or 2 separate packets?
> 2) if 2 separate packets are to be sent, how can the receiver determine 
> whether the 2 reports are describing the statistics in the same sequence 
> number interval?
> 
> Thanks.
> Richard
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> This message (including any attachments) is for the named
> addressee(s)'s use only. It may contain sensitive, confidential,
> private proprietary or legally privileged information intended for a
> specific individual and purpose, and is protected by law. If you are
> not the intended recipient, please immediately delete it and all copies
> of it from your system, destroy any hard copies of it
> and notify the sender. Any use, disclosure, copying, or distribution of
> this message and/or any attachments is strictly prohibited.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
> 
> 

From yekuiwang@huawei.com  Thu Feb 26 10:38:59 2009
Return-Path: <yekuiwang@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 6F5163A67D8 for <avt@core3.amsl.com>; Thu, 26 Feb 2009 10:38:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.007
X-Spam-Level: 
X-Spam-Status: No, score=-2.007 tagged_above=-999 required=5 tests=[AWL=-0.292, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001]
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 Ygc+ENFzNqrD for <avt@core3.amsl.com>; Thu, 26 Feb 2009 10:38:58 -0800 (PST)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id 127CA3A67B0 for <avt@ietf.org>; Thu, 26 Feb 2009 10:38:58 -0800 (PST)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KFO00GNWRTI7V@usaga02-in.huawei.com> for avt@ietf.org; Thu, 26 Feb 2009 10:39:18 -0800 (PST)
Received: from W90946 ([10.193.125.102]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KFO00N12RTB14@usaga02-in.huawei.com> for avt@ietf.org; Thu, 26 Feb 2009 10:39:17 -0800 (PST)
Date: Thu, 26 Feb 2009 13:39:11 -0500
From: Ye-Kui Wang <yekuiwang@huawei.com>
In-reply-to: <499a8530.0aec660a.29ef.0b97@mx.google.com>
To: 'Roni Even' <ron.even.tlv@gmail.com>, 'VAN CAENEGEM Tom' <Tom.Van_Caenegem@alcatel-lucent.be>, "'Ver Steeg, Bill'" <VersteB@cisco.com>, 'Orit Levin' <oritl@microsoft.com>,  oran@cisco.com, abegen@cisco.com, 'Peilin YANG' <yangpeilin@huawei.com>
Message-id: <B4AF880CE49641DF90BAD4CDAB0A1176@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_AA2S13oUdAwhimITl9v6WQ)"
Thread-index: AcmQyHjcjWlgubC1Sh2jzSR4f49cjQAE2akQAAE/ykAB15EyIA==
References: <499a58b2.0aa1660a.24ce.ffffc36e@mx.google.com> <238382595265324EA50F6134BB42DCAF034F7343@FRVELSMBS22.ad2.ad.alcatel.com> <499a8530.0aec660a.29ef.0b97@mx.google.com>
Cc: 'IETF AVT WG' <avt@ietf.org>
Subject: Re: [AVT] Rapid synchronization / RTP Burst / RTCP burst
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: Thu, 26 Feb 2009 18:38:59 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_AA2S13oUdAwhimITl9v6WQ)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Folks,
 
Roughly, how much delay can be saved in average by using the basic mechanism
that is common for all the drafts (i.e. using an additioal unicast burst for
the Key Information)? Does anyone have a figure?
 
When trying to make an estimation, I tried to figure out how exactly the
system works, but it turned out that that is still unclear after reading all
the drafts. Can anyone help answer a couple of clarification questions
below?
 
Let's use an example with an H.264/AVC stream. Assume that the network works
perfectly - no packet loss. The video stream structure is as follows. 
 
 ParameterSets IDR0 B1 B2 P3 B4 B5 P6 B7 B8 P9 B10 B11 P12 B13 B14
ParameterSets IDR15 P16 B17 B16 P19 B20 B21 ...
 
>From left to right is the presentation order. IDR0 and IDR15 are random
access points, and the presentation time difference between them is 1
second. In other words, if the presenation time of IDR0 is 0, then the
presentation time of P3 is 0.2s. Assume that a user starts the process of
switching to the channel when other users are displaying the picture P3 (for
simplicity in description, assume that all the users are synchronized in
playback).
 
Questions: 
- What does the Key Information contain, i.e. what information will be sent
to the user via the unicast session? 
- Starting from which picture the playback will be started by the user
equipment?
 
Please feel free to make any other assumptions, e.g. the value of the
unicast session bandwidth, whenever needed. 
 
BR, YK


  _____  

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Roni
Even
Sent: Tuesday, February 17, 2009 4:35 AM
To: 'VAN CAENEGEM Tom'; 'Ver Steeg, Bill'; 'Orit Levin'; oran@cisco.com;
abegen@cisco.com; 'Peilin YANG'
Cc: 'IETF AVT WG'
Subject: Re: [AVT] Rapid synchronization / RTP Burst / RTCP burst



Hi,

These are good news, please try to include Peilin in your discussion,
hopefully we will manage to have an ad-hoc meeting in SF to get further
progress. 

 

I think it will be good to include the input from Peilin document as early
as possible in order to expedite the work. 

 

The summary of the ad-hoc meeting that was on the AVT list had a couple of
discussion points. Are there any resolution, my view is that if you post
this to the list early it will help with progressing the work.

 

About the first discussion point I had some other feedback suggesting that
RTCP may be used from retransmission server   to send information that was
previously in the RTP stream if there is no obvious way to fit it in the
retransmission stream.

 

Regards

Roni Even

 

From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be] 
Sent: Tuesday, February 17, 2009 10:54 AM
To: Roni Even; Ver Steeg, Bill; Orit Levin; oran@cisco.com;
abegen@cisco.com; Peilin YANG
Cc: IETF AVT WG
Subject: RE: Rapid synchronization / RTP Burst / RTCP burst

 

Dear Roni,

 

we (that is the authors of the two drafts on "Rapid MC synchronisation") are
in the process of  delivering a new draft that combines some of the elements
in both existing drafts and takes into account the comments from the ad-hoc
meeting. Our ambition is indeed to submit this new draft before the SF
meeting deadline. We decided to go for a two-step approach, where in the 1st
step we sort out the differences among the two drafts that have already been
presented and discussed within the IETF community, and in the second step
(starting with the IETF SF meeting) , we want to discuss with Peilin and all
other interested people on the new features proposed in his draft on this
topic.

 

Kind Regards,

Tom

 


  _____  


From: Roni Even [mailto:ron.even.tlv@gmail.com] 
Sent: dinsdag 17 februari 2009 7:25
To: 'Ver Steeg, Bill'; 'Orit Levin'; VAN CAENEGEM Tom; oran@cisco.com;
abegen@cisco.com; 'Peilin YANG'
Cc: 'IETF AVT WG'
Subject: Rapid synchronization / RTP Burst / RTCP burst

Hi,

At the Minneapolis the summary was that the parties will try to progress the
work before SF meeting.

The only thing I saw on the AVT list is a new draft from Peilin, so now
there are three drafts.

Is there any other progress or are you all waiting for SF to discuss
progress.

The deadline for contributions is March 2nd for new drafts and March 9th for
the rest.

 

Regards

Roni Even

AVT co-chair


--Boundary_(ID_AA2S13oUdAwhimITl9v6WQ)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v = 
"urn:schemas-microsoft-com:vml" xmlns:o = 
"urn:schemas-microsoft-com:office:office" xmlns:w = 
"urn:schemas-microsoft-com:office:word" xmlns:m = 
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.5726" name=GENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle18 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=220102218-26022009><FONT face=&#23435;&#20307; 
color=#0000ff size=2>Folks,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=220102218-26022009><FONT face=&#23435;&#20307; 
color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=220102218-26022009><FONT face=&#23435;&#20307; 
color=#0000ff size=2>Roughly, how much delay can be saved in average by using 
the basic mechanism that is&nbsp;common for all the drafts (i.e. using an 
additioal unicast burst for the Key Information)? Does anyone have a 
figure?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=220102218-26022009><FONT face=&#23435;&#20307; 
color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=220102218-26022009><FONT face=&#23435;&#20307; 
color=#0000ff size=2>When trying to make an estimation, I tried to figure out 
how exactly the system works, but it turned out that that is still unclear after 
reading all the drafts. Can anyone help answer a couple of clarification 
questions below?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=220102218-26022009><FONT face=&#23435;&#20307; 
color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=220102218-26022009><FONT face=&#23435;&#20307; 
color=#0000ff size=2>Let's use an example with an H.264/AVC stream. Assume that 
the network works perfectly - no packet loss. The video stream structure is as 
follows. </FONT></SPAN></DIV>
<DIV><FONT face=&#23435;&#20307; color=#0000ff size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=220102218-26022009><FONT face=&#23435;&#20307; 
color=#0000ff size=2>&nbsp;ParameterSets IDR0 B1 B2 P3 B4 B5 P6 B7 B8 P9 B10 B11 
P12 B13 B14&nbsp;&nbsp;&nbsp; ParameterSets IDR15 P16 B17 B16 P19 B20 B21 
...</FONT></SPAN></DIV>
<DIV><FONT face=&#23435;&#20307; color=#0000ff size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=220102218-26022009><FONT face=&#23435;&#20307; 
color=#0000ff size=2>From left to right is the presentation order. IDR0 and 
IDR15 are random access points, and the presentation time difference between 
them is 1 second. In other words, if the presenation time of IDR0 is 0, then the 
presentation time of P3 is 0.2s. Assume that a user starts the process of 
switching to the channel when other users are displaying the picture P3 (for 
simplicity in description, assume that all the&nbsp;users are synchronized in 
playback).</FONT></SPAN></DIV>
<DIV><FONT face=&#23435;&#20307; color=#0000ff size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=220102218-26022009><FONT face=&#23435;&#20307; 
color=#0000ff size=2>Questions: <BR>- What does the Key Information contain, 
i.e. what information will be sent to the user via the unicast session? <BR>- 
Starting from which picture the playback will be started by the user 
equipment?</FONT></SPAN></DIV>
<DIV><FONT face=&#23435;&#20307; color=#0000ff size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=220102218-26022009><FONT face=&#23435;&#20307; 
color=#0000ff size=2>Please feel free to make any other assumptions, 
e.g.&nbsp;the value of the unicast session bandwidth, whenever needed. 
</FONT></SPAN></DIV>
<DIV><SPAN class=220102218-26022009></SPAN><SPAN class=220102218-26022009><FONT 
face=&#23435;&#20307; color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=220102218-26022009><FONT face=&#23435;&#20307; 
color=#0000ff size=2>BR, YK</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
  <HR tabIndex=-1>
  <FONT face=Tahoma size=2><B>From:</B> avt-bounces@ietf.org 
  [mailto:avt-bounces@ietf.org] <B>On Behalf Of </B>Roni Even<BR><B>Sent:</B> 
  Tuesday, February 17, 2009 4:35 AM<BR><B>To:</B> 'VAN CAENEGEM Tom'; 'Ver 
  Steeg, Bill'; 'Orit Levin'; oran@cisco.com; abegen@cisco.com; 'Peilin 
  YANG'<BR><B>Cc:</B> 'IETF AVT WG'<BR><B>Subject:</B> Re: [AVT] Rapid 
  synchronization / RTP Burst / RTCP burst<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=Section1>
  <P class=MsoNormal><SPAN style="COLOR: #1f497d">Hi,<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN style="COLOR: #1f497d">These are good news, please 
  try to include Peilin in your discussion, hopefully we will manage to have an 
  ad-hoc meeting in SF to get further progress. <o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=MsoNormal><SPAN style="COLOR: #1f497d">I think it will be good to 
  include the input from Peilin document as early as possible in order to 
  expedite the work. <o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=MsoNormal><SPAN style="COLOR: #1f497d">The summary of the ad-hoc 
  meeting that was on the AVT list had a couple of discussion points. Are there 
  any resolution, my view is that if you post this to the list early it will 
  help with progressing the work.<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=MsoNormal><SPAN style="COLOR: #1f497d">About the first discussion 
  point I had some other feedback suggesting that RTCP may be used from 
  retransmission server &nbsp;&nbsp;to send information that was previously in 
  the RTP stream if there is no obvious way to fit it in the retransmission 
  stream.<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=MsoNormal><SPAN style="COLOR: #1f497d">Regards<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN style="COLOR: #1f497d">Roni 
Even<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p>&nbsp;</o:p></SPAN></P>
  <DIV>
  <DIV 
  style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
  <P class=MsoNormal><B><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> VAN CAENEGEM Tom 
  [mailto:Tom.Van_Caenegem@alcatel-lucent.be] <BR><B>Sent:</B> Tuesday, February 
  17, 2009 10:54 AM<BR><B>To:</B> Roni Even; Ver Steeg, Bill; Orit Levin; 
  oran@cisco.com; abegen@cisco.com; Peilin YANG<BR><B>Cc:</B> IETF AVT 
  WG<BR><B>Subject:</B> RE: Rapid synchronization / RTP Burst / RTCP 
  burst<o:p></o:p></SPAN></P></DIV></DIV>
  <P class=MsoNormal><o:p>&nbsp;</o:p></P>
  <P class=MsoNormal><SPAN 
  style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">Dear 
  Roni,</SPAN><SPAN 
  style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN 
  style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">&nbsp;<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN 
  style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">we 
  (that is the authors of the two drafts on "Rapid MC synchronisation") are in 
  the process of&nbsp; delivering a new draft that combines some of the elements 
  in both existing drafts and takes into account the comments from the ad-hoc 
  meeting. Our ambition is indeed to&nbsp;submit this new draft before the SF 
  meeting deadline. We decided to go for a two-step approach, where in the 1st 
  step we sort out the differences among the two drafts that have already been 
  presented and discussed within the IETF community, and in the second step 
  (starting with the IETF SF meeting) , we&nbsp;want to discuss with Peilin and 
  all other interested people on the new features proposed in his draft on this 
  topic.</SPAN><SPAN 
  style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN 
  style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">&nbsp;<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN 
  style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">Kind 
  Regards,</SPAN><SPAN 
  style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN 
  style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">Tom</SPAN><SPAN 
  style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN 
  style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p>&nbsp;</o:p></SPAN></P>
  <DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><SPAN 
  style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">
  <HR align=center width="100%" SIZE=2>
  </SPAN></DIV>
  <P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><B><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> Roni Even 
  [mailto:ron.even.tlv@gmail.com] <BR><B>Sent:</B> dinsdag 17 februari 2009 
  7:25<BR><B>To:</B> 'Ver Steeg, Bill'; 'Orit Levin'; VAN CAENEGEM Tom; 
  oran@cisco.com; abegen@cisco.com; 'Peilin YANG'<BR><B>Cc:</B> 'IETF AVT 
  WG'<BR><B>Subject:</B> Rapid synchronization / RTP Burst / RTCP 
  burst</SPAN><SPAN 
  style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
  <P class=MsoNormal>Hi,<o:p></o:p></P>
  <P class=MsoNormal>At the Minneapolis the summary was that the parties will 
  try to progress the work before SF meeting.<o:p></o:p></P>
  <P class=MsoNormal>The only thing I saw on the AVT list is a new draft from 
  Peilin, so now there are three drafts.<o:p></o:p></P>
  <P class=MsoNormal>Is there any other progress or are you all waiting for SF 
  to discuss progress.<o:p></o:p></P>
  <P class=MsoNormal>The deadline for contributions is March 2<SUP>nd</SUP> for 
  new drafts and March 9<SUP>th</SUP> for the rest.<o:p></o:p></P>
  <P class=MsoNormal><o:p>&nbsp;</o:p></P>
  <P class=MsoNormal>Regards<o:p></o:p></P>
  <P class=MsoNormal>Roni Even<o:p></o:p></P>
  <P class=MsoNormal>AVT co-chair<o:p></o:p></P></DIV></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_AA2S13oUdAwhimITl9v6WQ)--

From abegen@cisco.com  Thu Feb 26 11:01:25 2009
Return-Path: <abegen@cisco.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 6CEFF28C0D8 for <avt@core3.amsl.com>; Thu, 26 Feb 2009 11:01:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.157
X-Spam-Level: 
X-Spam-Status: No, score=-6.157 tagged_above=-999 required=5 tests=[AWL=-0.442, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 AzFYQkbeugGB for <avt@core3.amsl.com>; Thu, 26 Feb 2009 11:01:23 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id C53003A6818 for <avt@ietf.org>; Thu, 26 Feb 2009 11:01:23 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,272,1233532800";  d="scan'208,217";a="135695035"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-2.cisco.com with ESMTP; 26 Feb 2009 19:01:45 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n1QJ1jrd007911;  Thu, 26 Feb 2009 11:01:45 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n1QJ1jPf020372; Thu, 26 Feb 2009 19:01:45 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 26 Feb 2009 11:01:45 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C99844.AB02A648"
Date: Thu, 26 Feb 2009 11:01:43 -0800
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D5408BCADD8@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <B4AF880CE49641DF90BAD4CDAB0A1176@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Rapid synchronization / RTP Burst / RTCP burst
Thread-Index: AcmQyHjcjWlgubC1Sh2jzSR4f49cjQAE2akQAAE/ykAB15EyIAAAx+CQ
References: <499a58b2.0aa1660a.24ce.ffffc36e@mx.google.com> <238382595265324EA50F6134BB42DCAF034F7343@FRVELSMBS22.ad2.ad.alcatel.com> <499a8530.0aec660a.29ef.0b97@mx.google.com> <B4AF880CE49641DF90BAD4CDAB0A1176@china.huawei.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Ye-Kui Wang" <yekuiwang@huawei.com>, "Roni Even" <ron.even.tlv@gmail.com>, "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>, "Bill Ver Steeg (versteb)" <versteb@cisco.com>, "Orit Levin" <oritl@microsoft.com>, "Dave Oran (oran)" <oran@cisco.com>, "Peilin YANG" <yangpeilin@huawei.com>
X-OriginalArrivalTime: 26 Feb 2009 19:01:45.0495 (UTC) FILETIME=[AB3E3A70:01C99844]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=23275; t=1235674905; x=1236538905; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=abegen@cisco.com; z=From:=20=22Ali=20C.=20Begen=20(abegen)=22=20<abegen@cisco. com> |Subject:=20RE=3A=20[AVT]=20Rapid=20synchronization=20/=20R TP=20Burst=20/=20RTCP=20burst |Sender:=20; bh=EkF/b0Xdbaqr/2KQWaxhEbNMSbnJor1gBj+Lq3yjVKE=; b=mIyo857MxxXnPbWl5+7o3gxzFXHEoIfQ8h5DxVg2Dro2R3oQrvXSh7tETB Rz9pctscSixCxZzQ0fvihWF3QrtW2j553FV9oubt6iRePCdkqzh5cuUGKDTN yzk64UjzAb;
Authentication-Results: sj-dkim-4; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Cc: IETF AVT WG <avt@ietf.org>
Subject: Re: [AVT] Rapid synchronization / RTP Burst / RTCP burst
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: Thu, 26 Feb 2009 19:01:25 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C99844.AB02A648
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

YK,
=20
There are a couple of IEEE papers that explain this scheme in simple
words. They should help with all of your questions. They have results,
too.
=20
I don't want to spam everyone with the pdfs, but here is the citation
info:
=20
Ali C. Begen, Neil Glazebrook and William Ver Steeg, "Reducing channel
change times in IPTV with real-time transport protocol," to appear in
IEEE Internet Comput., Special Issue on IPTV, May/June 2009
=20
Ali C. Begen, Neil Glazebrook and William Ver Steeg, "A unified approach
for repairing packet loss and accelerating channel changes in multicast
IPTV," in Proc. IEEE Consumer Communications and Networking Conf.
(CCNC), Special Session on IPTV Towards Seamless Infotainment, Las
Vegas, NV, Jan. 2009
=20
If you have access to IEEExplore, you can get the 2nd paper. The first
one is inprint. If anybody is interested, pls send me a private message
and I will forward the pdf.
=20
BR,
-acbegen


________________________________

	From: Ye-Kui Wang [mailto:yekuiwang@huawei.com]=20
	Sent: Thursday, February 26, 2009 10:39 AM
	To: 'Roni Even'; 'VAN CAENEGEM Tom'; Bill Ver Steeg (versteb);
'Orit Levin'; Dave Oran (oran); Ali C. Begen (abegen); 'Peilin YANG'
	Cc: 'IETF AVT WG'
	Subject: RE: [AVT] Rapid synchronization / RTP Burst / RTCP
burst
=09
=09
	Folks,
	=20
	Roughly, how much delay can be saved in average by using the
basic mechanism that is common for all the drafts (i.e. using an
additioal unicast burst for the Key Information)? Does anyone have a
figure?
	=20
	When trying to make an estimation, I tried to figure out how
exactly the system works, but it turned out that that is still unclear
after reading all the drafts. Can anyone help answer a couple of
clarification questions below?
	=20
	Let's use an example with an H.264/AVC stream. Assume that the
network works perfectly - no packet loss. The video stream structure is
as follows.=20
	=20
	 ParameterSets IDR0 B1 B2 P3 B4 B5 P6 B7 B8 P9 B10 B11 P12 B13
B14    ParameterSets IDR15 P16 B17 B16 P19 B20 B21 ...
	=20
	From left to right is the presentation order. IDR0 and IDR15 are
random access points, and the presentation time difference between them
is 1 second. In other words, if the presenation time of IDR0 is 0, then
the presentation time of P3 is 0.2s. Assume that a user starts the
process of switching to the channel when other users are displaying the
picture P3 (for simplicity in description, assume that all the users are
synchronized in playback).
	=20
	Questions:=20
	- What does the Key Information contain, i.e. what information
will be sent to the user via the unicast session?=20
	- Starting from which picture the playback will be started by
the user equipment?
	=20
	Please feel free to make any other assumptions, e.g. the value
of the unicast session bandwidth, whenever needed.=20
	=20
	BR, YK


________________________________

		From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]
On Behalf Of Roni Even
		Sent: Tuesday, February 17, 2009 4:35 AM
		To: 'VAN CAENEGEM Tom'; 'Ver Steeg, Bill'; 'Orit Levin';
oran@cisco.com; abegen@cisco.com; 'Peilin YANG'
		Cc: 'IETF AVT WG'
		Subject: Re: [AVT] Rapid synchronization / RTP Burst /
RTCP burst
	=09
	=09

		Hi,

		These are good news, please try to include Peilin in
your discussion, hopefully we will manage to have an ad-hoc meeting in
SF to get further progress.=20

		=20

		I think it will be good to include the input from Peilin
document as early as possible in order to expedite the work.=20

		=20

		The summary of the ad-hoc meeting that was on the AVT
list had a couple of discussion points. Are there any resolution, my
view is that if you post this to the list early it will help with
progressing the work.

		=20

		About the first discussion point I had some other
feedback suggesting that RTCP may be used from retransmission server
to send information that was previously in the RTP stream if there is no
obvious way to fit it in the retransmission stream.

		=20

		Regards

		Roni Even

		=20

		From: VAN CAENEGEM Tom
[mailto:Tom.Van_Caenegem@alcatel-lucent.be]=20
		Sent: Tuesday, February 17, 2009 10:54 AM
		To: Roni Even; Ver Steeg, Bill; Orit Levin;
oran@cisco.com; abegen@cisco.com; Peilin YANG
		Cc: IETF AVT WG
		Subject: RE: Rapid synchronization / RTP Burst / RTCP
burst

		=20

		Dear Roni,

		=20

		we (that is the authors of the two drafts on "Rapid MC
synchronisation") are in the process of  delivering a new draft that
combines some of the elements in both existing drafts and takes into
account the comments from the ad-hoc meeting. Our ambition is indeed to
submit this new draft before the SF meeting deadline. We decided to go
for a two-step approach, where in the 1st step we sort out the
differences among the two drafts that have already been presented and
discussed within the IETF community, and in the second step (starting
with the IETF SF meeting) , we want to discuss with Peilin and all other
interested people on the new features proposed in his draft on this
topic.

		=20

		Kind Regards,

		Tom

		=20

	=09
________________________________


		From: Roni Even [mailto:ron.even.tlv@gmail.com]=20
		Sent: dinsdag 17 februari 2009 7:25
		To: 'Ver Steeg, Bill'; 'Orit Levin'; VAN CAENEGEM Tom;
oran@cisco.com; abegen@cisco.com; 'Peilin YANG'
		Cc: 'IETF AVT WG'
		Subject: Rapid synchronization / RTP Burst / RTCP burst

		Hi,

		At the Minneapolis the summary was that the parties will
try to progress the work before SF meeting.

		The only thing I saw on the AVT list is a new draft from
Peilin, so now there are three drafts.

		Is there any other progress or are you all waiting for
SF to discuss progress.

		The deadline for contributions is March 2nd for new
drafts and March 9th for the rest.

		=20

		Regards

		Roni Even

		AVT co-chair


------_=_NextPart_001_01C99844.AB02A648
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16788" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Calibri","sans-serif"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Calibri","sans-serif"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Calibri","sans-serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: =
personal
}
SPAN.EmailStyle18 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: =
personal-reply
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D590314418-26022009><FONT =
face=3DArial=20
size=3D2>YK,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D590314418-26022009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D590314418-26022009><FONT =
face=3DArial=20
size=3D2>There are a couple of IEEE papers that explain this scheme in =
simple=20
words. They should help with all of your questions. They have results,=20
too.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D590314418-26022009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D590314418-26022009><FONT =
face=3DArial size=3D2>I=20
don't want to spam everyone with the pdfs, but here is the citation=20
info:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D590314418-26022009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D590314418-26022009><FONT =
face=3DArial=20
size=3D2>Ali C. Begen, Neil Glazebrook and William Ver Steeg, "Reducing =
channel=20
change times in IPTV with real-time transport protocol," to appear in =
<I>IEEE=20
Internet Comput., Special Issue on IPTV</I>, May/June =
2009</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D590314418-26022009><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D590314418-26022009><FONT =
face=3DArial=20
size=3D2>Ali C. Begen, Neil Glazebrook and William Ver Steeg, "A unified =
approach=20
for repairing packet loss and accelerating channel changes in multicast =
IPTV,"=20
in <I>Proc. IEEE Consumer Communications and Networking Conf. (CCNC), =
Special=20
Session on IPTV Towards Seamless Infotainment</I>, Las Vegas, NV, Jan.=20
2009</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D590314418-26022009></SPAN><FONT face=3DArial><FONT =
size=3D2>I<SPAN=20
class=3D590314418-26022009>f you have access to IEEExplore, you can get =
the 2nd=20
paper. The first one is inprint. If anybody is interested, pls send me a =
private=20
message and I will forward the pdf.</SPAN></FONT></FONT></DIV>
<DIV><SPAN class=3D590314418-26022009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D590314418-26022009><FONT face=3DArial=20
size=3D2>BR,</FONT></SPAN></DIV>
<DIV><SPAN class=3D590314418-26022009><FONT face=3DArial=20
size=3D2>-acbegen</FONT></SPAN></DIV>
<DIV><BR></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Ye-Kui Wang=20
  [mailto:yekuiwang@huawei.com] <BR><B>Sent:</B> Thursday, February 26, =
2009=20
  10:39 AM<BR><B>To:</B> 'Roni Even'; 'VAN CAENEGEM Tom'; Bill Ver Steeg =

  (versteb); 'Orit Levin'; Dave Oran (oran); Ali C. Begen (abegen); =
'Peilin=20
  YANG'<BR><B>Cc:</B> 'IETF AVT WG'<BR><B>Subject:</B> RE: [AVT] Rapid=20
  synchronization / RTP Burst / RTCP burst<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D220102218-26022009><FONT =
face=3D&#23435;&#20307;=20
  color=3D#0000ff size=3D2>Folks,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D220102218-26022009><FONT =
face=3D&#23435;&#20307;=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D220102218-26022009><FONT =
face=3D&#23435;&#20307;=20
  color=3D#0000ff size=3D2>Roughly, how much delay can be saved in =
average by using=20
  the basic mechanism that is&nbsp;common for all the drafts (i.e. using =
an=20
  additioal unicast burst for the Key Information)? Does anyone have a=20
  figure?</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D220102218-26022009><FONT =
face=3D&#23435;&#20307;=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D220102218-26022009><FONT =
face=3D&#23435;&#20307;=20
  color=3D#0000ff size=3D2>When trying to make an estimation, I tried to =
figure out=20
  how exactly the system works, but it turned out that that is still =
unclear=20
  after reading all the drafts. Can anyone help answer a couple of =
clarification=20
  questions below?</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D220102218-26022009><FONT =
face=3D&#23435;&#20307;=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D220102218-26022009><FONT =
face=3D&#23435;&#20307;=20
  color=3D#0000ff size=3D2>Let's use an example with an H.264/AVC =
stream. Assume=20
  that the network works perfectly - no packet loss. The video stream =
structure=20
  is as follows. </FONT></SPAN></DIV>
  <DIV><FONT face=3D&#23435;&#20307; color=3D#0000ff =
size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D220102218-26022009><FONT =
face=3D&#23435;&#20307;=20
  color=3D#0000ff size=3D2>&nbsp;ParameterSets IDR0 B1 B2 P3 B4 B5 P6 B7 =
B8 P9 B10=20
  B11 P12 B13 B14&nbsp;&nbsp;&nbsp; ParameterSets IDR15 P16 B17 B16 P19 =
B20 B21=20
  ...</FONT></SPAN></DIV>
  <DIV><FONT face=3D&#23435;&#20307; color=3D#0000ff =
size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D220102218-26022009><FONT =
face=3D&#23435;&#20307;=20
  color=3D#0000ff size=3D2>From left to right is the presentation order. =
IDR0 and=20
  IDR15 are random access points, and the presentation time difference =
between=20
  them is 1 second. In other words, if the presenation time of IDR0 is =
0, then=20
  the presentation time of P3 is 0.2s. Assume that a user starts the =
process of=20
  switching to the channel when other users are displaying the picture =
P3 (for=20
  simplicity in description, assume that all the&nbsp;users are =
synchronized in=20
  playback).</FONT></SPAN></DIV>
  <DIV><FONT face=3D&#23435;&#20307; color=3D#0000ff =
size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D220102218-26022009><FONT =
face=3D&#23435;&#20307;=20
  color=3D#0000ff size=3D2>Questions: <BR>- What does the Key =
Information contain,=20
  i.e. what information will be sent to the user via the unicast =
session? <BR>-=20
  Starting from which picture the playback will be started by the user=20
  equipment?</FONT></SPAN></DIV>
  <DIV><FONT face=3D&#23435;&#20307; color=3D#0000ff =
size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D220102218-26022009><FONT =
face=3D&#23435;&#20307;=20
  color=3D#0000ff size=3D2>Please feel free to make any other =
assumptions,=20
  e.g.&nbsp;the value of the unicast session bandwidth, whenever needed. =

  </FONT></SPAN></DIV>
  <DIV><SPAN class=3D220102218-26022009></SPAN><SPAN=20
  class=3D220102218-26022009><FONT face=3D&#23435;&#20307; =
color=3D#0000ff=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D220102218-26022009><FONT =
face=3D&#23435;&#20307;=20
  color=3D#0000ff size=3D2>BR, YK</FONT></SPAN></DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> avt-bounces@ietf.org=20
    [mailto:avt-bounces@ietf.org] <B>On Behalf Of </B>Roni =
Even<BR><B>Sent:</B>=20
    Tuesday, February 17, 2009 4:35 AM<BR><B>To:</B> 'VAN CAENEGEM Tom'; =
'Ver=20
    Steeg, Bill'; 'Orit Levin'; oran@cisco.com; abegen@cisco.com; =
'Peilin=20
    YANG'<BR><B>Cc:</B> 'IETF AVT WG'<BR><B>Subject:</B> Re: [AVT] Rapid =

    synchronization / RTP Burst / RTCP burst<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV class=3DSection1>
    <P class=3DMsoNormal><SPAN style=3D"COLOR: =
#1f497d">Hi,<o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">These are good =
news, please=20
    try to include Peilin in your discussion, hopefully we will manage =
to have=20
    an ad-hoc meeting in SF to get further progress. =
<o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"COLOR: =
#1f497d"><o:p>&nbsp;</o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">I think it will =
be good to=20
    include the input from Peilin document as early as possible in order =
to=20
    expedite the work. <o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"COLOR: =
#1f497d"><o:p>&nbsp;</o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">The summary of =
the ad-hoc=20
    meeting that was on the AVT list had a couple of discussion points. =
Are=20
    there any resolution, my view is that if you post this to the list =
early it=20
    will help with progressing the work.<o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"COLOR: =
#1f497d"><o:p>&nbsp;</o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">About the first =
discussion=20
    point I had some other feedback suggesting that RTCP may be used =
from=20
    retransmission server &nbsp;&nbsp;to send information that was =
previously in=20
    the RTP stream if there is no obvious way to fit it in the =
retransmission=20
    stream.<o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"COLOR: =
#1f497d"><o:p>&nbsp;</o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
style=3D"COLOR: #1f497d">Regards<o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">Roni=20
    Even<o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN style=3D"COLOR: =
#1f497d"><o:p>&nbsp;</o:p></SPAN></P>
    <DIV>
    <DIV=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
#b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: =
medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
    <P class=3DMsoNormal><B><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Tahoma','sans-serif'">From:</SPAN></B><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> VAN =
CAENEGEM=20
    Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be] <BR><B>Sent:</B> =
Tuesday,=20
    February 17, 2009 10:54 AM<BR><B>To:</B> Roni Even; Ver Steeg, Bill; =
Orit=20
    Levin; oran@cisco.com; abegen@cisco.com; Peilin YANG<BR><B>Cc:</B> =
IETF AVT=20
    WG<BR><B>Subject:</B> RE: Rapid synchronization / RTP Burst / RTCP=20
    burst<o:p></o:p></SPAN></P></DIV></DIV>
    <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">Dear=20
    Roni,</SPAN><SPAN=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New =
Roman','serif'"><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New =
Roman','serif'">&nbsp;<o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">we=20
    (that is the authors of the two drafts on "Rapid MC =
synchronisation") are in=20
    the process of&nbsp; delivering a new draft that combines some of =
the=20
    elements in both existing drafts and takes into account the comments =
from=20
    the ad-hoc meeting. Our ambition is indeed to&nbsp;submit this new =
draft=20
    before the SF meeting deadline. We decided to go for a two-step =
approach,=20
    where in the 1st step we sort out the differences among the two =
drafts that=20
    have already been presented and discussed within the IETF community, =
and in=20
    the second step (starting with the IETF SF meeting) , we&nbsp;want =
to=20
    discuss with Peilin and all other interested people on the new =
features=20
    proposed in his draft on this topic.</SPAN><SPAN=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New =
Roman','serif'"><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New =
Roman','serif'">&nbsp;<o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">Kind=20
    Regards,</SPAN><SPAN=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New =
Roman','serif'"><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">Tom</SPAN><SPAN=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New =
Roman','serif'"><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New =
Roman','serif'"><o:p>&nbsp;</o:p></SPAN></P>
    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><SPAN=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">
    <HR align=3Dcenter width=3D"100%" SIZE=3D2>
    </SPAN></DIV>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Tahoma','sans-serif'">From:</SPAN></B><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> Roni =
Even=20
    [mailto:ron.even.tlv@gmail.com] <BR><B>Sent:</B> dinsdag 17 februari =
2009=20
    7:25<BR><B>To:</B> 'Ver Steeg, Bill'; 'Orit Levin'; VAN CAENEGEM =
Tom;=20
    oran@cisco.com; abegen@cisco.com; 'Peilin YANG'<BR><B>Cc:</B> 'IETF =
AVT=20
    WG'<BR><B>Subject:</B> Rapid synchronization / RTP Burst / RTCP=20
    burst</SPAN><SPAN=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New =
Roman','serif'"><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal>Hi,<o:p></o:p></P>
    <P class=3DMsoNormal>At the Minneapolis the summary was that the =
parties will=20
    try to progress the work before SF meeting.<o:p></o:p></P>
    <P class=3DMsoNormal>The only thing I saw on the AVT list is a new =
draft from=20
    Peilin, so now there are three drafts.<o:p></o:p></P>
    <P class=3DMsoNormal>Is there any other progress or are you all =
waiting for SF=20
    to discuss progress.<o:p></o:p></P>
    <P class=3DMsoNormal>The deadline for contributions is March =
2<SUP>nd</SUP>=20
    for new drafts and March 9<SUP>th</SUP> for the rest.<o:p></o:p></P>
    <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
    <P class=3DMsoNormal>Regards<o:p></o:p></P>
    <P class=3DMsoNormal>Roni Even<o:p></o:p></P>
    <P class=3DMsoNormal>AVT=20
co-chair<o:p></o:p></P></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C99844.AB02A648--

From igor.curcio@nokia.com  Fri Feb 27 06:47:06 2009
Return-Path: <igor.curcio@nokia.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 099663A6452; Fri, 27 Feb 2009 06:47:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.998
X-Spam-Level: 
X-Spam-Status: No, score=-5.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_46=0.6, RCVD_IN_DNSWL_MED=-4]
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 LwDyNJ2ayMJM; Fri, 27 Feb 2009 06:47:03 -0800 (PST)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id 2EEAB3A6899; Fri, 27 Feb 2009 06:47:03 -0800 (PST)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id n1REl4pW013315; Fri, 27 Feb 2009 08:47:23 -0600
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 27 Feb 2009 16:47:21 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.5]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 27 Feb 2009 16:47:21 +0200
Received: from NOK-AM1MHUB-05.mgdnok.nokia.com (65.54.30.9) by NOK-am1MHUB-01.mgdnok.nokia.com (65.54.30.5) with Microsoft SMTP Server (TLS) id 8.1.291.1; Fri, 27 Feb 2009 15:47:20 +0100
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.106]) by NOK-AM1MHUB-05.mgdnok.nokia.com ([65.54.30.9]) with mapi; Fri, 27 Feb 2009 15:47:20 +0100
From: <igor.curcio@nokia.com>
To: <mmusic@ietf.org>, <avt@ietf.org>
Date: Fri, 27 Feb 2009 15:47:19 +0100
Thread-Topic: Call for Papers / WoWMoM '09 / Industry Track 
Thread-Index: AcmQyHjcjWlgubC1Sh2jzSR4f49cjQAE2akQAAE/ykAB15EyIAAAx+CQACmrTTA=
Message-ID: <08485F91AF534543877F9738F761DCFE27E902D05A@NOK-EUMSG-01.mgdnok.nokia.com>
References: <499a58b2.0aa1660a.24ce.ffffc36e@mx.google.com> <238382595265324EA50F6134BB42DCAF034F7343@FRVELSMBS22.ad2.ad.alcatel.com> <499a8530.0aec660a.29ef.0b97@mx.google.com> <B4AF880CE49641DF90BAD4CDAB0A1176@china.huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D5408BCADD8@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D5408BCADD8@xmb-sjc-215.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_08485F91AF534543877F9738F761DCFE27E902D05ANOKEUMSG01mgd_"
MIME-Version: 1.0
X-OriginalArrivalTime: 27 Feb 2009 14:47:21.0296 (UTC) FILETIME=[4B7C0D00:01C998EA]
X-Nokia-AV: Clean
Subject: [AVT] Call for Papers / WoWMoM '09 / Industry Track
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: Fri, 27 Feb 2009 14:47:06 -0000

--_000_08485F91AF534543877F9738F761DCFE27E902D05ANOKEUMSG01mgd_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

10th IEEE International Symposium on a World of Wireless, Mobile and Multim=
edia Networks
15-19 June 2009, Kos, Greece


Call For Papers -- Industrial Track

http://www.ics.forth.gr/wowmom09/callforindustrialpapers.html



Important dates:

* Paper submission deadline: 15 March 2009 (HARD DEADLINE)

* Acceptance notification: 29 March 2009

* Camera-ready copy deadline: 11 April 2009



IEEE WoWMoM 2009 http://www.ics.forth.gr/wowmom09/index.html is soliciting =
original and previously unpublished research papers from industry researche=
rs and professionals for a one-day Industry Session. Specific topics of int=
erest include, but are not limited to:

* Conversational Mobile Multimedia

* (Personal) Mobile Broadcast Delivery and Applications

* Mobile broadcast implementation issues (including, but not limited to, DV=
B-H, MBMS, DMB, ATSC-M/H, MediaFLO, etc.)

* Mobile P2P distribution of real-time Multimedia

* Scalable Media architectures for mobile networks

* Social Multimedia and co-creation

* 3D Video modeling and applications

* Context-based real-time media

* Semantic description and scene context extraction of real-time media

* Multimodal sensing and context.



The Industry Session track is intended to specially highlight system experi=
ences and proofs-of-concept in the areas above. Like regular papers, the In=
dustry Session papers will undergo a review process by an International TPC=
 and will appear in the conference proceedings.

However, the selection criteria for Industry Session papers are slightly di=
fferent. In particular, papers should describe applications, prototypes or =
experiences of clear industry relevance. Papers with narrow algorithmic foc=
us or only high-level design details are discouraged. A key goal of this se=
ssion is to present systems-oriented research that exposes the academic and=
 research communities to real-life issues and problems being faced in indus=
try. Accordingly, papers will be evaluated, less on the novelty of specific=
 algorithmic content, but by the originality and general applicability of i=
nsights that can be inferred from the authors' implementation experience.

Papers must be formatted according to the guidelines given in http://www.ic=
s.forth.gr/wowmom09/papersubmission.html and submitted by the authors to BO=
TH the Industry Chairs by midnight US Pacific Time of 15 March 2009.



Industry Chairs:

Igor D.D. Curcio (Nokia Research Center), E-mail: igor.curcio AT nokia.com

Kumar Ramaswamy (Thomson), E-mail: kumar.ramaswamy AT thomson.net

--_000_08485F91AF534543877F9738F761DCFE27E902D05ANOKEUMSG01mgd_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3492" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: pe=
rsonal
}
SPAN.EmailStyle18 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: perso=
nal-reply
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV><FONT face=3DArial><SPAN class=3D553383714-27022009><STRONG>10th IEEE=
=20
International Symposium on a World of Wireless, Mobile and Multimedia=20
Networks</STRONG></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553383714-27022009>15-19 Jun=
e 2009,=20
Kos, Greece</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553383714-27022009></SPAN></FONT>&nbsp;</DIV>
<DIV>
<P><FONT face=3DArial><FONT size=3D2><STRONG>Call For Papers -- Industrial=
=20
Track<SPAN class=3D553383714-27022009> </SPAN></STRONG></FONT></FONT></P>
<P><FONT face=3DArial><FONT size=3D2><STRONG><SPAN=20
class=3D553383714-27022009></SPAN></STRONG><FONT color=3D#0000ff><A=20
href=3D"http://www.ics.forth.gr/wowmom09/callforindustrialpapers.html">http=
://www.ics.forth.gr/wowmom09/callforindustrialpapers.html</A></FONT></FONT>=
</FONT></P>
<P><FONT face=3DArial size=3D2></FONT>&nbsp;</P>
<P><FONT face=3DArial size=3D2><U>Important dates:</U></FONT></P>
<P><FONT face=3DArial size=3D2>* Paper submission deadline: <STRONG>15 Marc=
h=20
2009</STRONG> (HARD DEADLINE)</FONT></P>
<P><FONT face=3DArial size=3D2>* Acceptance notification: 29 March 2009</FO=
NT></P>
<P><FONT face=3DArial size=3D2>* Camera-ready copy deadline: 11 April=20
2009</FONT></P>
<P><FONT face=3DArial size=3D2></FONT>&nbsp;</P>
<P><FONT face=3DArial size=3D2>IEEE WoWMoM 2009 </FONT><A=20
href=3D"http://www.ics.forth.gr/wowmom09/index.html"><FONT face=3DArial=20
size=3D2>http://www.ics.forth.gr/wowmom09/index.html</FONT></A><FONT=20
face=3DArial><FONT size=3D2><SPAN class=3D553383714-27022009></SPAN>&nbsp;i=
s=20
soliciting original and previously unpublished research papers from industr=
y=20
researchers and professionals for a one-day Industry Session. Specific topi=
cs of=20
interest include, but are not limited to:</FONT></FONT></P>
<P><FONT face=3DArial size=3D2>* Conversational Mobile Multimedia</FONT></P=
>
<P><FONT face=3DArial size=3D2>* (Personal) Mobile Broadcast Delivery and=20
Applications</FONT></P>
<P><FONT face=3DArial size=3D2>* Mobile broadcast implementation issues (in=
cluding,=20
but not limited to, DVB-H, MBMS, DMB, ATSC-M/H, MediaFLO, etc.)</FONT></P>
<P><FONT face=3DArial size=3D2>* Mobile P2P distribution of real-time=20
Multimedia</FONT></P>
<P><FONT face=3DArial size=3D2>* Scalable Media architectures for mobile=20
networks</FONT></P>
<P><FONT face=3DArial size=3D2>* Social Multimedia and co-creation</FONT></=
P>
<P><FONT face=3DArial size=3D2>* 3D Video modeling and applications</FONT><=
/P>
<P><FONT face=3DArial size=3D2>* Context-based real-time media</FONT></P>
<P><FONT face=3DArial size=3D2>* Semantic description and scene context ext=
raction=20
of real-time media</FONT></P>
<P><FONT face=3DArial size=3D2>* Multimodal sensing and context.</FONT></P>
<P><FONT face=3DArial size=3D2></FONT>&nbsp;</P>
<P><FONT face=3DArial size=3D2>The Industry Session track is intended to sp=
ecially=20
highlight system experiences and proofs-of-concept in the areas above. Like=
=20
regular papers, the Industry Session papers will undergo a review process b=
y an=20
International TPC and will appear in the conference proceedings.</FONT></P>
<P><FONT face=3DArial size=3D2>However, the selection criteria for Industry=
 Session=20
papers are slightly different. In particular, papers should describe=20
applications, prototypes or experiences of clear industry relevance. Papers=
 with=20
narrow algorithmic focus or only high-level design details are discouraged.=
 A=20
key goal of this session is to present systems-oriented research that expos=
es=20
the academic and research communities to real-life issues and problems bein=
g=20
faced in industry. Accordingly, papers will be evaluated, less on the novel=
ty of=20
specific algorithmic content, but by the originality and general applicabil=
ity=20
of insights that can be inferred from the authors' implementation=20
experience.</FONT></P>
<P><FONT face=3DArial size=3D2>Papers must be formatted according to the gu=
idelines=20
given in </FONT><A=20
href=3D"http://www.ics.forth.gr/wowmom09/papersubmission.html"><U><FONT=20
color=3D#0000ff size=3D2><FONT=20
face=3DArial>http://www.ics.forth.gr/wowmom09/papersubmission.html</FONT></=
U></FONT></A><FONT=20
face=3DArial size=3D2> and submitted by the authors to BOTH the Industry Ch=
airs=20
<STRONG><U>by midnight US Pacific Time of 15 March 2009</U></STRONG>.</FONT=
></P>
<P><FONT face=3DArial size=3D2></FONT>&nbsp;</P>
<P><FONT face=3DArial size=3D2>Industry Chairs:</FONT></P>
<P><FONT face=3DArial size=3D2>Igor D.D. Curcio (Nokia Research Center), E-=
mail:=20
igor.curcio<SPAN class=3D553383714-27022009> AT </SPAN>nokia.com </FONT></P=
>
<P><FONT face=3DArial size=3D2>Kumar Ramaswamy (Thomson), E-mail:=20
kumar.ramaswamy<SPAN class=3D553383714-27022009> AT=20
</SPAN>thomson.net</FONT></P><FONT size=3D2></FONT></DIV></BODY></HTML>

--_000_08485F91AF534543877F9738F761DCFE27E902D05ANOKEUMSG01mgd_--

From frans.de.bont@philips.com  Fri Feb 27 06:51:14 2009
Return-Path: <frans.de.bont@philips.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 3D39C3A6966 for <avt@core3.amsl.com>; Fri, 27 Feb 2009 06:51:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 2vH-jPnN0RPN for <avt@core3.amsl.com>; Fri, 27 Feb 2009 06:51:13 -0800 (PST)
Received: from smtpx.philips.com (smtpx.philips.com [168.87.56.20]) by core3.amsl.com (Postfix) with ESMTP id 125AC3A6452 for <avt@ietf.org>; Fri, 27 Feb 2009 06:51:13 -0800 (PST)
Received: from NLHILEXH03.connect1.local (172.16.153.78) by connect1.philips.com (172.16.156.40) with Microsoft SMTP Server (TLS) id 8.1.340.0; Fri, 27 Feb 2009 15:51:25 +0100
Received: from NLCLUEXM01.connect1.local ([172.16.153.50]) by NLHILEXH03.connect1.local ([15.143.187.34]) with mapi; Fri, 27 Feb 2009 15:51:29 +0100
From: "BONT, Frans DE" <frans.de.bont@philips.com>
To: IETF AVT WG <avt@ietf.org>
Date: Fri, 27 Feb 2009 15:50:53 +0100
Thread-Topic: New Version Notification for draft-schmidt-avt-rfc3016bis-01 
Thread-Index: AcmY4wj0fyFk48Q0TgOBs6X5SwrhwQAAAjfQ
Message-ID: <19FE62CE8D62CF4B96C845DC556B88131CA4F79854@NLCLUEXM01.connect1.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: [AVT] FW: New Version Notification for draft-schmidt-avt-rfc3016bis-01
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: Fri, 27 Feb 2009 14:51:14 -0000

VGhpcyBkcmFmdCBpcyBhbiB1cGRhdGUgb2YgUkZDMzAxNi4NCg0KRnJvbSBhIGhpZ2ggbGV2ZWwg
cGVyc3BlY3RpdmUgdGhlIGZvbGxvd2luZyBwb2ludHMgaGF2ZSBiZWVuIGFkZHJlc3NlZDoNCg0K
LSBUaGUgYXVkaW8gcGF5bG9hZCBmb3JtYXQgKExBVE0pIHJlZmVyZW5jZWQgaW4gUkZDIDMwMTYg
aXMgYmluYXJ5IGluY29tcGF0aWJsZSB0byB0aGUgZm9ybWF0IHVzZWQgaW4gM0dQUC4NCi0gVGhl
IGF1ZGlvIHNpZ25hbGluZyBmb3JtYXQgKFN0cmVhbU11eENvbmZpZykgcmVmZXJlbmNlZCBpbiBS
RkMgMzAxNiBpcyBiaW5hcnkgaW5jb21wYXRpYmxlIHRvIHRoZSBmb3JtYXQgdXNlZCBpbiAzR1BQ
Lg0KLSBUaGUgYXVkaW8gcGFyYW1ldGVyICJTQlItZW5hYmxlZCIgaXMgbm90IGRlZmluZWQgd2l0
aGluIFJGQyAzMDE2IGJ1dCB1c2VkIGJ5IDNHUFANCi0gVGhlIHJhdGUgcGFyYW1ldGVyIHNwZWNp
ZmljYXRpb24gaW4gYW1iaWd1b3VzIGluIHRoZSBwcmVzZW5jZSBvZiBTQlIgKFNwZWN0cmFsIEJh
bmQgUmVwbGljYXRpb24pDQotIEZ1cnRoZXJtb3JlIHNvbWUgKG9sZGVyKSBlLW1haWwgY29tbWVu
dHMgZnJvbSB0aGUgQVZUIGxpc3QgaGF2ZSBiZWVuIGFkZHJlc3NlZCBhbmQgc2lnbmFsaW5nIHN1
cHBvcnQgZm9yIE1QRUcgc3Vycm91bmQgd2FzIGFkZGVkDQoNCk5vdGUgdGhhdCB0byBvdXIgYmVz
dCBrbm93bGVkZ2UgUkZDMzAxNiBpcyBvbmx5IHVzZWQgYnkgM0dQUCBhbmQgdGhpcyB3b3JrIGp1
c3QgYWxpZ25zIHRoZSBzcGVjaWZpY2F0aW9uIHdpdGggdGhlIHdheSB0aGUgZm9ybWF0IGlzIHVz
ZWQgaW4gdGhlIGZpZWxkLiBDdXJyZW50bHkgd2UgYXJlIG5vdCBhd2FyZSB0aGF0IHRoZXJlIGlz
IGFuIGluY29tcGF0aWJpbGl0eS4NCg0KV2UnZCBsaWtlIHRoaXMgdG8gYmUgY29uc2lkZXJlZCBm
b3IgYWRvcHRpb24gYXMgYW4gQVZUIHdvcmtpbmcgZ3JvdXAgZHJhZnQuDQoNCkEgVVJMIGZvciB0
aGlzIEludGVybmV0LURyYWZ0IGlzOg0KaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFm
dHMvZHJhZnQtc2NobWlkdC1hdnQtcmZjMzAxNmJpcy0wMS50eHQNCg0KQmVzdCByZWdhcmRzLA0K
RnJhbnMNCg0KRnJhbnMgZGUgQm9udCwNClBoaWxpcHMgQXBwbGllZCBUZWNobm9sb2dpZXMsDQpI
aWdoIFRlY2ggQ2FtcHVzIDUsIDU2NTYgQUUgRWluZGhvdmVuDQpUZWw6ICsrMzEgNDAgMjc0MDIz
NCwgRmF4OiArKzMxIDQwIDI3NDQxMDgNClJvb20gSFRDLTUvNS4wMTkNCmh0dHA6Ly93d3cuYXBw
dGVjaC5waGlsaXBzLmNvbQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogSUVU
RiBJLUQgU3VibWlzc2lvbiBUb29sIFttYWlsdG86aWRzdWJtaXNzaW9uQGlldGYub3JnXQ0KU2Vu
dDogMjAwOSBGZWIgMjcgMjo1NSBQTQ0KVG86IEJPTlQsIEZyYW5zIERFDQpDYzogbWFsdGUuc2No
bWlkdEBkb2xieS5jb207IHN0ZWZhbi5kb2VobGFAaWlzLmZyYXVuaG9mZXIuZGUNClN1YmplY3Q6
IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQtc2NobWlkdC1hdnQtcmZjMzAxNmJp
cy0wMQ0KDQoNCkEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1zY2htaWR0LWF2dC1yZmMzMDE2
YmlzLTAxLnR4dCBoYXMgYmVlbiBzdWNjZXNzZnVseSBzdWJtaXR0ZWQgYnkgRnJhbnMgQm9udCBh
bmQgcG9zdGVkIHRvIHRoZSBJRVRGIHJlcG9zaXRvcnkuDQoNCkZpbGVuYW1lOiAgICAgICAgZHJh
ZnQtc2NobWlkdC1hdnQtcmZjMzAxNmJpcw0KUmV2aXNpb246ICAgICAgICAwMQ0KVGl0bGU6ICAg
ICAgICAgICBSVFAgUGF5bG9hZCBGb3JtYXQgZm9yIE1QRUctNCBBdWRpby9WaXN1YWwgU3RyZWFt
cw0KQ3JlYXRpb25fZGF0ZTogICAyMDA5LTAyLTI3DQpXRyBJRDogICAgICAgICAgIEluZGVwZW5k
ZW50IFN1Ym1pc3Npb24NCk51bWJlcl9vZl9wYWdlczogMjYNCg0KQWJzdHJhY3Q6DQpUaGlzIGRv
Y3VtZW50IGRlc2NyaWJlcyBSZWFsLVRpbWUgVHJhbnNwb3J0IFByb3RvY29sIChSVFApIHBheWxv
YWQNCmZvcm1hdHMgZm9yIGNhcnJ5aW5nIGVhY2ggb2YgTVBFRy00IEF1ZGlvIGFuZCBNUEVHLTQg
VmlzdWFsDQpiaXRzdHJlYW1zIHdpdGhvdXQgdXNpbmcgTVBFRy00IFN5c3RlbXMuICBGb3IgdGhl
IHB1cnBvc2Ugb2YgZGlyZWN0bHkNCm1hcHBpbmcgTVBFRy00IEF1ZGlvL1Zpc3VhbCBiaXRzdHJl
YW1zIG9udG8gUlRQIHBhY2tldHMsIGl0IHByb3ZpZGVzDQpzcGVjaWZpY2F0aW9ucyBmb3IgdGhl
IHVzZSBvZiBSVFAgaGVhZGVyIGZpZWxkcyBhbmQgYWxzbyBzcGVjaWZpZXMNCmZyYWdtZW50YXRp
b24gcnVsZXMuICBJdCBhbHNvIHByb3ZpZGVzIHNwZWNpZmljYXRpb25zIGZvcg0KTXVsdGlwdXJw
b3NlIEludGVybmV0IE1haWwgRXh0ZW5zaW9ucyAoTUlNRSkgdHlwZSByZWdpc3RyYXRpb25zIGFu
ZA0KdGhlIHVzZSBvZiBTZXNzaW9uIERlc2NyaXB0aW9uIFByb3RvY29sIChTRFApLg0KDQpDb21t
ZW50cyBhcmUgc29saWNpdGVkIGFuZCBzaG91bGQgYmUgYWRkcmVzc2VkIHRvIHRoZSB3b3JraW5n
IGdyb3VwJ3MNCm1haWxpbmcgbGlzdCBhdCBhdnRAaWV0Zi5vcmcgYW5kL29yIHRoZSBhdXRob3Io
cykuDQoNCg0KDQpUaGUgSUVURiBTZWNyZXRhcmlhdC4NCg0KDQoNClRoZSBpbmZvcm1hdGlvbiBj
b250YWluZWQgaW4gdGhpcyBtZXNzYWdlIG1heSBiZSBjb25maWRlbnRpYWwgYW5kIGxlZ2FsbHkg
cHJvdGVjdGVkIHVuZGVyIGFwcGxpY2FibGUgbGF3LiBUaGUgbWVzc2FnZSBpcyBpbnRlbmRlZCBz
b2xlbHkgZm9yIHRoZSBhZGRyZXNzZWUocykuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZCBy
ZWNpcGllbnQsIHlvdSBhcmUgaGVyZWJ5IG5vdGlmaWVkIHRoYXQgYW55IHVzZSwgZm9yd2FyZGlu
ZywgZGlzc2VtaW5hdGlvbiwgb3IgcmVwcm9kdWN0aW9uIG9mIHRoaXMgbWVzc2FnZSBpcyBzdHJp
Y3RseSBwcm9oaWJpdGVkIGFuZCBtYXkgYmUgdW5sYXdmdWwuIElmIHlvdSBhcmUgbm90IHRoZSBp
bnRlbmRlZCByZWNpcGllbnQsIHBsZWFzZSBjb250YWN0IHRoZSBzZW5kZXIgYnkgcmV0dXJuIGUt
bWFpbCBhbmQgZGVzdHJveSBhbGwgY29waWVzIG9mIHRoZSBvcmlnaW5hbCBtZXNzYWdlLg0K

From root@core3.amsl.com  Sat Feb 28 13:45:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id EBBD73A6870; Sat, 28 Feb 2009 13:45:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090228214501.EBBD73A6870@core3.amsl.com>
Date: Sat, 28 Feb 2009 13:45:01 -0800 (PST)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-dtls-srtp-07.txt
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, 28 Feb 2009 21:45:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Working Group of the IETF.


	Title           : Datagram Transport Layer Security (DTLS) Extension to Establish Keys for Secure Real-time Transport Protocol (SRTP)
	Author(s)       : D. McGrew, E. Rescorla
	Filename        : draft-ietf-avt-dtls-srtp-07.txt
	Pages           : 26
	Date            : 2009-02-28

This document describes a Datagram Transport Layer Security (DTLS)
extension to establish keys for secure RTP (SRTP) and secure RTP
Control Protocol (SRTCP) flows.  DTLS keying happens on the media
path, independent of any out-of-band signalling channel present.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-dtls-srtp-07.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-avt-dtls-srtp-07.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-02-28133901.I-D@ietf.org>


--NextPart--
