
From Even.roni@huawei.com  Mon Jun  1 07:16:24 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 780693A7156 for <avt@core3.amsl.com>; Mon,  1 Jun 2009 07:16:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.105
X-Spam-Level: **
X-Spam-Status: No, score=2.105 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 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 GyT4F7wA1ZHF for <avt@core3.amsl.com>; Mon,  1 Jun 2009 07:16:23 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id AC1BD3A6F55 for <avt@ietf.org>; Mon,  1 Jun 2009 07:16:23 -0700 (PDT)
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 <0KKK006WYCZ16U@szxga04-in.huawei.com> for avt@ietf.org; Mon, 01 Jun 2009 22:16:13 +0800 (CST)
Received: from huawei.com ([172.24.1.3]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KKK00BVOCZ1A9@szxga04-in.huawei.com> for avt@ietf.org; Mon, 01 Jun 2009 22:16:13 +0800 (CST)
Received: from windows8d787f9 (bzq-79-177-124-209.red.bezeqint.net [79.177.124.209]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KKK00BNACYSNZ@szxml01-in.huawei.com>; Mon, 01 Jun 2009 22:16:13 +0800 (CST)
Date: Mon, 01 Jun 2009 17:15:10 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <81B9B88E2F9D574AA5328A85547CDE9101495636@xmb-rtp-21d.amer.cisco.com>
To: "'Bill Ver Steeg (versteb)'" <versteb@cisco.com>, avt@ietf.org
Message-id: <011701c9e2c3$6a75b990$3f612cb0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcnS4FBFJRh0kTNdSKKujynDJmWrDwAJMQ/AAC+GL9AAAGUFAAAXW2jQAA+eDnAASHsCkALEQgYwAIvU5CA=
References: <fa05fd7ad709f.d709ffa05fd7a@huawei.com> <81B9B88E2F9D574AA5328A85547CDE91013038E4@xmb-rtp-21d.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE9101303DA5@xmb-rtp-21d.amer.cisco.com> <00dc01c9d3c5$7a323aa0$6e96afe0$%roni@huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D54094C3DBF@xmb-sjc-215.amer.cisco.com> <000a01c9d461$813bdcb0$83b39610$%roni@huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D540954DB8A@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE9101495636@xmb-rtp-21d.amer.cisco.com>
Subject: [AVT] Calling for comments on changes to RAMS draft 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/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, 01 Jun 2009 14:16:24 -0000

Bill,
Are you going to add all the comments from the rdiff.

Also please send this email not under the above subject since it does not
describe the purpose of the email

Roni

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Bill
Ver Steeg (versteb)
Sent: Friday, May 29, 2009 10:40 PM
To: avt@ietf.org
Subject: Re: [AVT] Adopting Rapid Acquisition of Multicast RTP
Sessions(RAMS) as a working group item

Fellow AVT folks-

We are continuing to solicit comments on the RAMS design points identified
in Ali's email from May 15 (diff enclosed). We have received some valuable
feedback. We hope to have a new draft mid next week, and will incorporate
comments that we receive through Monday or Tuesday in that draft.

Thanks in advance



Bill VerSteeg

-----Original Message-----
From: Ali C. Begen (abegen)
Sent: Friday, May 15, 2009 1:32 PM
To: Roni Even; Bill Ver Steeg (versteb); avt@ietf.org
Subject: RE: [AVT] Adopting Rapid Acquisition of Multicast RTP
Sessions(RAMS) as a working group item

Hi Roni, All,

Here is a diff for sections 7 and 13. 

Comments are welcome.
-acbegen


From Borilin@spiritdsp.com  Mon Jun  1 13:50:33 2009
Return-Path: <Borilin@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 0FED43A6B5C for <avt@core3.amsl.com>; Mon,  1 Jun 2009 13:50:33 -0700 (PDT)
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 ZpULyBOZa+OR for <avt@core3.amsl.com>; Mon,  1 Jun 2009 13:50:31 -0700 (PDT)
Received: from mail3.spiritcorp.com (mail3.spiritcorp.com [85.13.194.167]) by core3.amsl.com (Postfix) with ESMTP id C09293A6F8A for <avt@ietf.org>; Mon,  1 Jun 2009 13:49:45 -0700 (PDT)
Received: from mail-srv.spiritcorp.com (mail-srv.spiritcorp.com [192.168.125.3]) by mail3.spiritcorp.com (8.13.8/8.14.3) with SMTP id n51KnhF8044710; Tue, 2 Jun 2009 00:49:44 +0400 (MSD) (envelope-from Borilin@spiritdsp.com)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9E2FA.7A0FFA62"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 2 Jun 2009 00:49:37 +0400
Message-ID: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG 
Thread-Index: Acni+nnnMWC61lG/QBqkK6Rn/iXR9Q==
From: "Slava Borilin" <Borilin@spiritdsp.com>
To: <jean-marc.valin@octasic.com>
X-Scanned-By: MIMEDefang 2.64 on 192.168.125.15
Cc: avt@ietf.org, Jason Fischl <jason.fischl@skype.net>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 01 Jun 2009 20:52:33 -0000

This is a multi-part message in MIME format.

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

Agree with Jean-Marc.
SPIRIT is interested to contribute as well - having a dozen of
proprietary codecs developed, including=20
one specifically desgined for internet (SPIRIT IP-MR, which is now under
WGLC on draft-ietf-avt-rtp-ipmr-04) -=20
multi-rate, scalable, adaptive, wideband codec.
=20
We can also continue this work with IETF.
=20
Moreover, most if not all efforts coming from ITU on codecs
unfortunately are NOT really focused on=20
internet-specific codecs (that's why several companies have had to
invent) - as ITU preference is mainly=20
specific (i.e. cellular) networks at first.
=20
however, as we see the greant rise of pure "internet-basd
communications" (skype, webex/citrix, and many others) -=20
we all (and users) are suffering from inefficiency in all currently
"standard" codecs and ambiguity in the choice of=20
internet-targeted ones.
=20
Again, we probably can put together enough number of contributors to the
WG to have the expertise.
=20
regards,
Slava Borilin
=20
--
John Lazzaro wrote:

	A traditional response to this type of request is to note that
the IETF
	really doesn't have much in the way of expertise in audio codec
design.
	I don't see many of the regulars who present at the AES codec
paper sessions
	posting here on AVT (ditto ICASSP paper sessions for voice
codecs). It's
	a full-time job to keep up-to-date and contribute to that
	signal-processing lore.
=09
=09

Well, there's no reason that the IETF cannot build such an expertise in
audio codecs. This is actually something in which I'd be interested in
getting involved and I'm sure others at Xiph.Org would be interested as
well. We have several people with audio codec expertise from working on
Vorbis, Speex and (more recently) CELT. It turns out that the CELT codec
currently under development at Xiph actually meets most of the
requirements from the original proposal in being a very low delay codec
with adaptive bit-rate and sampling rate (up to 48 kHz), scalable
complexity, and good robustness to packet loss. We'd be willing to
continue the development with the IETF. Even if not with CELT, it's
still like to be involved in such a new WG.=20
Cheers,

   Jean-Marc

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16640" name=3DGENERATOR></HEAD>
<BODY><PRE style=3D"MARGIN: 0em"><SPAN class=3D062123620-01062009>Agree =
with Jean-Marc.</SPAN></PRE>
<DIV align=3Dleft><PRE style=3D"MARGIN: 0em"><SPAN =
class=3D062123620-01062009>SPIRIT is interested to contribute as well - =
having a dozen of proprietary codecs developed, including =
</SPAN></PRE><PRE style=3D"MARGIN: 0em"><SPAN =
class=3D062123620-01062009>one specifically desgined for internet =
(SPIRIT IP-MR, which is now under WGLC on draft-ietf-avt-rtp-ipmr-04) - =
</SPAN></PRE><PRE style=3D"MARGIN: 0em"><SPAN =
class=3D062123620-01062009>multi-rate, scalable, adaptive, wideband =
codec.</SPAN></PRE><PRE style=3D"MARGIN: 0em"><SPAN =
class=3D062123620-01062009></SPAN>&nbsp;</PRE><PRE style=3D"MARGIN: =
0em"><SPAN class=3D062123620-01062009>We can also continue this work =
with IETF.</SPAN></PRE><PRE style=3D"MARGIN: 0em"><SPAN =
class=3D062123620-01062009></SPAN>&nbsp;</PRE><PRE style=3D"MARGIN: =
0em"><SPAN class=3D062123620-01062009>Moreover, most if not all efforts =
coming from ITU on codecs unfortunately are NOT really focused on =
</SPAN></PRE><PRE style=3D"MARGIN: 0em"><SPAN =
class=3D062123620-01062009>internet-specific codecs (that's </SPAN><SPAN =
class=3D062123620-01062009>why several companies have had to invent) - =
as ITU preference is mainly </SPAN></PRE><PRE style=3D"MARGIN: =
0em"><SPAN class=3D062123620-01062009>specific (i.e. cellular) networks =
at first.</SPAN></PRE><PRE style=3D"MARGIN: 0em"><SPAN =
class=3D062123620-01062009></SPAN>&nbsp;</PRE><PRE style=3D"MARGIN: =
0em"><SPAN class=3D062123620-01062009>however, as we see the greant rise =
of pure "internet-basd communications" (skype, webex/citrix, and many =
others) - </SPAN></PRE><PRE style=3D"MARGIN: 0em"><SPAN =
class=3D062123620-01062009>we all (and users) are suffering from =
inefficiency in all currently "standard" codecs and ambiguity in the =
choice of </SPAN></PRE><PRE style=3D"MARGIN: 0em"><SPAN =
class=3D062123620-01062009>internet-targeted ones.</SPAN></PRE><PRE =
style=3D"MARGIN: 0em"><SPAN =
class=3D062123620-01062009></SPAN>&nbsp;</PRE><PRE style=3D"MARGIN: =
0em"><SPAN class=3D062123620-01062009>Again, we probably can put =
together enough number of contributors to the WG to have the =
expertise.</SPAN></PRE><PRE style=3D"MARGIN: 0em"><SPAN =
class=3D062123620-01062009></SPAN>&nbsp;</PRE><PRE style=3D"MARGIN: =
0em"><SPAN class=3D062123620-01062009>regards,</SPAN></PRE><PRE =
style=3D"MARGIN: 0em"><SPAN class=3D062123620-01062009>Slava =
Borilin</SPAN></PRE></DIV><PRE style=3D"MARGIN: 0em"><SPAN =
class=3D062123620-01062009></SPAN>&nbsp;</PRE><PRE style=3D"MARGIN: =
0em"><SPAN class=3D062123620-01062009>--</SPAN></PRE><PRE =
style=3D"MARGIN: 0em">John Lazzaro wrote:
</PRE>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 0.85em; MARGIN: 0em; BORDER-LEFT: #5555ee 0.2em =
solid"><PRE style=3D"MARGIN: 0em">A traditional response to this type of =
request is to note that the IETF
really doesn't have much in the way of expertise in audio codec design.
I don't see many of the regulars who present at the AES codec paper =
sessions
posting here on AVT (ditto ICASSP paper sessions for voice codecs). It's
a full-time job to keep up-to-date and contribute to that
signal-processing lore.</PRE><PRE style=3D"MARGIN: 0em">
</PRE><TT></TT></BLOCKQUOTE><PRE style=3D"MARGIN: 0em"></PRE><TT>Well, =
there's no reason that the IETF cannot=20
build such an expertise in </TT><TT>audio codecs. This is actually =
something in=20
which I'd be interested in </TT><TT>getting involved and I'm sure others =
at=20
Xiph.Org would be interested as </TT><TT>well. We have several people =
with audio=20
codec expertise from working on </TT><TT>Vorbis, Speex and (more =
recently) CELT.=20
It turns out that the CELT codec </TT><TT>currently under development at =
Xiph=20
actually meets most of the </TT><TT>requirements from the original =
proposal in=20
being a very low delay codec </TT><TT>with adaptive bit-rate and =
sampling rate=20
(up to 48 kHz), scalable </TT><TT>complexity, and good robustness to =
packet=20
loss. We'd be willing to </TT><TT>continue the development with the =
IETF. Even=20
if not with CELT, it's </TT><TT>still like to be involved in such a new =
WG.=20
</TT><PRE style=3D"MARGIN: 0em">Cheers,

   Jean-Marc
</PRE><!--X-Body-of-Message-End--><!--X-MsgBody-End--><!--X-Follow-Ups-->=
</BODY></HTML>

------_=_NextPart_001_01C9E2FA.7A0FFA62--

From stephen.botzko@gmail.com  Mon Jun  1 14:07:17 2009
Return-Path: <stephen.botzko@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 BE2413A693C for <avt@core3.amsl.com>; Mon,  1 Jun 2009 14:07:17 -0700 (PDT)
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 b+9CkU-nW84N for <avt@core3.amsl.com>; Mon,  1 Jun 2009 14:07:16 -0700 (PDT)
Received: from mail-bw0-f222.google.com (mail-bw0-f222.google.com [209.85.218.222]) by core3.amsl.com (Postfix) with ESMTP id 10F523A6843 for <avt@ietf.org>; Mon,  1 Jun 2009 14:07:15 -0700 (PDT)
Received: by bwz22 with SMTP id 22so7737662bwz.37 for <avt@ietf.org>; Mon, 01 Jun 2009 14:07:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=O+dgeyDzM+JfaqOD2uJR7RtA353xFHvUxkcgxTIluWY=; b=ZdJ3g/Z97I0hjfUOduBOGg7qnJymYHvANeAeyyMlHHbgqkEd+g3BldRpSPiwNj//gK fEapz8dP5Nbaf3qvov0QmZ5xFn25xfOeIAOPrwyA7S8pANJws+HNvc76qYhMIPwibD/g I6rmXLLit4OBUHs2kvuhQPTUFkZV91fEtS5Es=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Q+9FPhaTt6EpwxACGo/FcDlKL5Zqy3sbddn9gJdptTgxeiGYQgyIC0dKSMYvvF/nn8 vDbnX15Bm+HKgtMH6LhcWq+TQRrnw4gqY/zeTIa1XXar1GBjTud87ijHyXi6iaoC71xm tS90H4m5jh5T+t44tJk9mpLS6XKn6G0Fa/2xk=
MIME-Version: 1.0
Received: by 10.103.177.18 with SMTP id e18mr3455786mup.65.1243890432989; Mon,  01 Jun 2009 14:07:12 -0700 (PDT)
In-Reply-To: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com>
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com>
Date: Mon, 1 Jun 2009 17:07:12 -0400
Message-ID: <6e9223710906011407g2c9932a3x55b6fcf53f295a12@mail.gmail.com>
From: stephen botzko <stephen.botzko@gmail.com>
To: Slava Borilin <Borilin@spiritdsp.com>
Content-Type: multipart/alternative; boundary=001636416c4965db1a046b4fcf30
Cc: avt@ietf.org, Jason Fischl <jason.fischl@skype.net>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 01 Jun 2009 21:07:17 -0000

--001636416c4965db1a046b4fcf30
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

The ITU (like the IETF) is contribution-driven; it is certainly possible to
standardize internet codecs there.  G.719 is one example.

Regards,
Stephen Botzko

On Mon, Jun 1, 2009 at 4:49 PM, Slava Borilin <Borilin@spiritdsp.com> wrote:

> Agree with Jean-Marc.
>
> SPIRIT is interested to contribute as well - having a dozen of proprietary codecs developed, including
>
> one specifically desgined for internet (SPIRIT IP-MR, which is now under WGLC on draft-ietf-avt-rtp-ipmr-04) -
>
> multi-rate, scalable, adaptive, wideband codec.
>
>
>
> We can also continue this work with IETF.
>
>
>
> Moreover, most if not all efforts coming from ITU on codecs unfortunately are NOT really focused on
>
> internet-specific codecs (that's why several companies have had to invent) - as ITU preference is mainly
>
> specific (i.e. cellular) networks at first.
>
>
>
> however, as we see the greant rise of pure "internet-basd communications" (skype, webex/citrix, and many others) -
>
> we all (and users) are suffering from inefficiency in all currently "standard" codecs and ambiguity in the choice of
>
> internet-targeted ones.
>
>
>
> Again, we probably can put together enough number of contributors to the WG to have the expertise.
>
>
>
> regards,
>
> Slava Borilin
>
>
>
> --
>
> John Lazzaro wrote:
>
> A traditional response to this type of request is to note that the IETF
> really doesn't have much in the way of expertise in audio codec design.
> I don't see many of the regulars who present at the AES codec paper sessions
> posting here on AVT (ditto ICASSP paper sessions for voice codecs). It's
> a full-time job to keep up-to-date and contribute to that
> signal-processing lore.
>
> Well, there's no reason that the IETF cannot build such an expertise in audio
> codecs. This is actually something in which I'd be interested in getting
> involved and I'm sure others at Xiph.Org would be interested as well. We
> have several people with audio codec expertise from working on Vorbis,
> Speex and (more recently) CELT. It turns out that the CELT codec currently
> under development at Xiph actually meets most of the requirements from the
> original proposal in being a very low delay codec with adaptive bit-rate
> and sampling rate (up to 48 kHz), scalable complexity, and good robustness
> to packet loss. We'd be willing to continue the development with the IETF.
> Even if not with CELT, it's still like to be involved in such a new WG.
>
> Cheers,
>
>    Jean-Marc
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>
>

--001636416c4965db1a046b4fcf30
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The ITU (like the IETF) is contribution-driven; it is certainly possible to=
 standardize internet codecs there.=A0 G.719 is one example.<br><br>Regards=
,<br>Stephen Botzko<br><br><div class=3D"gmail_quote">On Mon, Jun 1, 2009 a=
t 4:49 PM, Slava Borilin <span dir=3D"ltr">&lt;<a href=3D"mailto:Borilin@sp=
iritdsp.com">Borilin@spiritdsp.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">



<div><pre style=3D"margin: 0em;"><span>Agree with Jean-Marc.</span></pre>
<div align=3D"left"><pre style=3D"margin: 0em;"><span>SPIRIT is interested =
to contribute as well - having a dozen of proprietary codecs developed, inc=
luding </span></pre><pre style=3D"margin: 0em;"><span>one specifically desg=
ined for internet (SPIRIT IP-MR, which is now under WGLC on draft-ietf-avt-=
rtp-ipmr-04) - </span></pre>
<pre style=3D"margin: 0em;"><span>multi-rate, scalable, adaptive, wideband =
codec.</span></pre><pre style=3D"margin: 0em;"><span></span>=A0</pre><pre s=
tyle=3D"margin: 0em;"><span>We can also continue this work with IETF.</span=
></pre>
<pre style=3D"margin: 0em;"><span></span>=A0</pre><pre style=3D"margin: 0em=
;"><span>Moreover, most if not all efforts coming from ITU on codecs unfort=
unately are NOT really focused on </span></pre><pre style=3D"margin: 0em;">=
<span>internet-specific codecs (that&#39;s </span><span>why several compani=
es have had to invent) - as ITU preference is mainly </span></pre>
<pre style=3D"margin: 0em;"><span>specific (i.e. cellular) networks at firs=
t.</span></pre><pre style=3D"margin: 0em;"><span></span>=A0</pre><pre style=
=3D"margin: 0em;"><span>however, as we see the greant rise of pure &quot;in=
ternet-basd communications&quot; (skype, webex/citrix, and many others) - <=
/span></pre>
<pre style=3D"margin: 0em;"><span>we all (and users) are suffering from ine=
fficiency in all currently &quot;standard&quot; codecs and ambiguity in the=
 choice of </span></pre><pre style=3D"margin: 0em;"><span>internet-targeted=
 ones.</span></pre>
<pre style=3D"margin: 0em;"><span></span>=A0</pre><pre style=3D"margin: 0em=
;"><span>Again, we probably can put together enough number of contributors =
to the WG to have the expertise.</span></pre><pre style=3D"margin: 0em;"><s=
pan></span>=A0</pre>
<pre style=3D"margin: 0em;"><span>regards,</span></pre><pre style=3D"margin=
: 0em;"><span>Slava Borilin</span></pre></div><pre style=3D"margin: 0em;"><=
span></span>=A0</pre><font color=3D"#888888"><pre style=3D"margin: 0em;"><s=
pan>--</span></pre>
</font><div class=3D"im"><pre style=3D"margin: 0em;">John Lazzaro wrote:
</pre>
<blockquote style=3D"border-left: 0.2em solid rgb(85, 85, 238); margin: 0em=
; padding-left: 0.85em;"><pre style=3D"margin: 0em;">A traditional response=
 to this type of request is to note that the IETF
really doesn&#39;t have much in the way of expertise in audio codec design.
I don&#39;t see many of the regulars who present at the AES codec paper ses=
sions
posting here on AVT (ditto ICASSP paper sessions for voice codecs). It&#39;=
s
a full-time job to keep up-to-date and contribute to that
signal-processing lore.</pre><pre style=3D"margin: 0em;"></pre><tt></tt></b=
lockquote><pre style=3D"margin: 0em;"></pre><tt>Well, there&#39;s no reason=
 that the IETF cannot=20
build such an expertise in </tt><tt>audio codecs. This is actually somethin=
g in=20
which I&#39;d be interested in </tt><tt>getting involved and I&#39;m sure o=
thers at=20
Xiph.Org would be interested as </tt><tt>well. We have several people with =
audio=20
codec expertise from working on </tt><tt>Vorbis, Speex and (more recently) =
CELT.=20
It turns out that the CELT codec </tt><tt>currently under development at Xi=
ph=20
actually meets most of the </tt><tt>requirements from the original proposal=
 in=20
being a very low delay codec </tt><tt>with adaptive bit-rate and sampling r=
ate=20
(up to 48 kHz), scalable </tt><tt>complexity, and good robustness to packet=
=20
loss. We&#39;d be willing to </tt><tt>continue the development with the IET=
F. Even=20
if not with CELT, it&#39;s </tt><tt>still like to be involved in such a new=
 WG.=20
</tt><pre style=3D"margin: 0em;">Cheers,

   Jean-Marc
</pre></div></div>
<br>_______________________________________________<br>
Audio/Video Transport Working Group<br>
<a href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/avt</a><br>
<br></blockquote></div><br>

--001636416c4965db1a046b4fcf30--

From Even.roni@huawei.com  Tue Jun  2 06:49:30 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 628743A697B for <avt@core3.amsl.com>; Tue,  2 Jun 2009 06:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.494
X-Spam-Level: 
X-Spam-Status: No, score=-0.494 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  HTML_MESSAGE=0.001, 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 UE7HcguZPwyA for <avt@core3.amsl.com>; Tue,  2 Jun 2009 06:49:29 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 2663D3A6C8F for <avt@ietf.org>; Tue,  2 Jun 2009 06:49:18 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KKM004816DVQT@szxga02-in.huawei.com> for avt@ietf.org; Tue, 02 Jun 2009 21:49:07 +0800 (CST)
Received: from huawei.com ([172.24.1.3]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KKM008LX6DV05@szxga02-in.huawei.com> for avt@ietf.org; Tue, 02 Jun 2009 21:49:07 +0800 (CST)
Received: from windows8d787f9 (bzq-79-182-66-238.red.bezeqint.net [79.182.66.238]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KKM009UE6C6X2@szxml01-in.huawei.com>; Tue, 02 Jun 2009 21:49:07 +0800 (CST)
Date: Tue, 02 Jun 2009 16:47:07 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com>
To: 'Slava Borilin' <Borilin@spiritdsp.com>, jean-marc.valin@octasic.com
Message-id: <00a401c9e388$b25c2350$171469f0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_GVmuQLhOBRTw9facVjrZjw)"
Content-language: en-us
Thread-index: Acni+nnnMWC61lG/QBqkK6Rn/iXR9QAjPhIA
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com>
Cc: avt@ietf.org, 'Jason Fischl' <jason.fischl@skype.net>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec	WG
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, 02 Jun 2009 13:49:30 -0000

This is a multipart message in MIME format.

--Boundary_(ID_GVmuQLhOBRTw9facVjrZjw)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hi,

I am not sure what prevented you from doing it today at the ITU or MPEG, why
do you see the IETF handling it differently.

I would also like to remind you and Jean-Marc that once you are bringing
work to a standard body it may require collaboration with other people who
will have other proposals that will also address the same requirements and
you may need to invest money in comparative testing by independent listening
labs.

I also think that you will need to supply the codec in source code and
provide copy right to the IETF. 

 

Roni 

 

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Slava
Borilin
Sent: Monday, June 01, 2009 11:50 PM
To: jean-marc.valin@octasic.com
Cc: avt@ietf.org; Jason Fischl
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec
WG

 

Agree with Jean-Marc.
SPIRIT is interested to contribute as well - having a dozen of proprietary
codecs developed, including 
one specifically desgined for internet (SPIRIT IP-MR, which is now under
WGLC on draft-ietf-avt-rtp-ipmr-04) - 
multi-rate, scalable, adaptive, wideband codec.
 
We can also continue this work with IETF.
 
Moreover, most if not all efforts coming from ITU on codecs unfortunately
are NOT really focused on 
internet-specific codecs (that's why several companies have had to invent) -
as ITU preference is mainly 
specific (i.e. cellular) networks at first.
 
however, as we see the greant rise of pure "internet-basd communications"
(skype, webex/citrix, and many others) - 
we all (and users) are suffering from inefficiency in all currently
"standard" codecs and ambiguity in the choice of 
internet-targeted ones.
 
Again, we probably can put together enough number of contributors to the WG
to have the expertise.
 
regards,
Slava Borilin
 
--
John Lazzaro wrote:

A traditional response to this type of request is to note that the IETF
really doesn't have much in the way of expertise in audio codec design.
I don't see many of the regulars who present at the AES codec paper sessions
posting here on AVT (ditto ICASSP paper sessions for voice codecs). It's
a full-time job to keep up-to-date and contribute to that
signal-processing lore.
 

Well, there's no reason that the IETF cannot build such an expertise in
audio codecs. This is actually something in which I'd be interested in
getting involved and I'm sure others at Xiph.Org would be interested as
well. We have several people with audio codec expertise from working on
Vorbis, Speex and (more recently) CELT. It turns out that the CELT codec
currently under development at Xiph actually meets most of the requirements
from the original proposal in being a very low delay codec with adaptive
bit-rate and sampling rate (up to 48 kHz), scalable complexity, and good
robustness to packet loss. We'd be willing to continue the development with
the IETF. Even if not with CELT, it's still like to be involved in such a
new WG. 

Cheers,
 
   Jean-Marc

--Boundary_(ID_GVmuQLhOBRTw9facVjrZjw)
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: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: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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
tt
	{mso-style-priority:99;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle20
	{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'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I am not sure what prevented you from doing it today at =
the ITU
or MPEG, why do you see the IETF handling it =
differently.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I would also like to remind you and Jean-Marc that once =
you are
bringing work to a standard body it may require collaboration with other =
people
who will have other proposals that will also address the same =
requirements and
you may need to invest money in comparative testing by independent =
listening labs.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I also think that you will need to supply the codec in =
source
code and provide copy right to the IETF. <o:p></o:p></span></p>

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

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Roni <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
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"'>
avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] <b>On Behalf Of =
</b>Slava
Borilin<br>
<b>Sent:</b> Monday, June 01, 2009 11:50 PM<br>
<b>To:</b> jean-marc.valin@octasic.com<br>
<b>Cc:</b> avt@ietf.org; Jason Fischl<br>
<b>Subject:</b> Re: [AVT] [dispatch] Proposal to form Internet Wideband =
Audio
Codec WG<o:p></o:p></span></p>

</div>

</div>

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

<pre>Agree with Jean-Marc.<o:p></o:p></pre><pre>SPIRIT is interested to =
contribute as well - having a dozen of proprietary codecs developed, =
including <o:p></o:p></pre><pre>one specifically desgined for internet =
(SPIRIT IP-MR, which is now under WGLC on draft-ietf-avt-rtp-ipmr-04) - =
<o:p></o:p></pre><pre>multi-rate, scalable, adaptive, wideband =
codec.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>We can also =
continue this work with =
IETF.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Moreover, most if =
not all efforts coming from ITU on codecs unfortunately are NOT really =
focused on <o:p></o:p></pre><pre>internet-specific codecs (that's why =
several companies have had to invent) - as ITU preference is mainly =
<o:p></o:p></pre><pre>specific (i.e. cellular) networks at =
first.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>however, as we =
see the greant rise of pure &quot;internet-basd communications&quot; =
(skype, webex/citrix, and many others) - <o:p></o:p></pre><pre>we all =
(and users) are suffering from inefficiency in all currently =
&quot;standard&quot; codecs and ambiguity in the choice of =
<o:p></o:p></pre><pre>internet-targeted =
ones.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Again, we =
probably can put together enough number of contributors to the WG to =
have the =
expertise.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>regards,<o:p>=
</o:p></pre><pre>Slava =
Borilin<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>--<o:p></o:p></p=
re><pre>John Lazzaro wrote:<o:p></o:p></pre>

<blockquote style=3D'border:none;border-left:solid #5555EE =
2.25pt;padding:0in 0in 0in 10.0pt;
margin-left:0in;margin-right:0in'><pre>A traditional response to this =
type of request is to note that the IETF<o:p></o:p></pre><pre>really =
doesn't have much in the way of expertise in audio codec =
design.<o:p></o:p></pre><pre>I don't see many of the regulars who =
present at the AES codec paper sessions<o:p></o:p></pre><pre>posting =
here on AVT (ditto ICASSP paper sessions for voice codecs). =
It's<o:p></o:p></pre><pre>a full-time job to keep up-to-date and =
contribute to that<o:p></o:p></pre><pre>signal-processing =
lore.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre></blockquote>

<p class=3DMsoNormal><tt><span style=3D'font-size:10.0pt'>Well, there's =
no reason
that the IETF cannot build such an expertise in audio codecs. This is =
actually
something in which I'd be interested in getting involved and I'm sure =
others at
Xiph.Org would be interested as well. We have several people with audio =
codec
expertise from working on Vorbis, Speex and (more recently) CELT. It =
turns out
that the CELT codec currently under development at Xiph actually meets =
most of
the requirements from the original proposal in being a very low delay =
codec
with adaptive bit-rate and sampling rate (up to 48 kHz), scalable =
complexity,
and good robustness to packet loss. We'd be willing to continue the =
development
with the IETF. Even if not with CELT, it's still like to be involved in =
such a
new WG. </span></tt><o:p></o:p></p>

<pre>Cheers,<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>&nbsp;&nbsp=
; Jean-Marc<o:p></o:p></pre></div>

</body>

</html>

--Boundary_(ID_GVmuQLhOBRTw9facVjrZjw)--

From rjesup@wgate.com  Tue Jun  2 07:57:01 2009
Return-Path: <rjesup@wgate.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 493C43A6C78 for <avt@core3.amsl.com>; Tue,  2 Jun 2009 07:57:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.734
X-Spam-Level: 
X-Spam-Status: No, score=-1.734 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RDNS_DYNAMIC=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 Ctm13a6Le9i9 for <avt@core3.amsl.com>; Tue,  2 Jun 2009 07:57:00 -0700 (PDT)
Received: from exchange1.wgate.com (pr-66-150-46-254.wgate.com [66.150.46.254]) by core3.amsl.com (Postfix) with ESMTP id 682D13A6965 for <avt@ietf.org>; Tue,  2 Jun 2009 07:57:00 -0700 (PDT)
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 2 Jun 2009 10:57:00 -0400
To: Roni Even <Even.roni@huawei.com>
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Tue, 02 Jun 2009 10:57:37 -0400
In-Reply-To: <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> (Roni Even's message of "Tue\, 02 Jun 2009 16\:47\:07 +0300")
Message-ID: <ybu7hzu7kf2.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.101 (Gnus v5.10.10) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 02 Jun 2009 14:57:00.0963 (UTC) FILETIME=[623C7730:01C9E392]
Cc: 'Slava Borilin' <Borilin@spiritdsp.com>, avt@ietf.org, 'Jason Fischl' <jason.fischl@skype.net>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec	WG
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
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, 02 Jun 2009 14:57:01 -0000

Roni Even <Even.roni@huawei.com> writes:
>I am not sure what prevented you from doing it today at the ITU or MPEG, why
>do you see the IETF handling it differently.

Last I knew, ITU was a *far* more closed group (and I think MPEG as well).
I would not even think of going through the hassle to participate in the
ITU standards process, while we might be interested helping with this idea,
though we may not be able to provide a large amount of resources to it.

The "associate" membership fee in ITU-T is more than I could justify,
especially since IETF/ITU work is largely personal for me:

     For the period 2008-2009, the annual financial contribution for an
     Associate in ITU-R, or ITU-T is CHF 10,600.00

>I would also like to remind you and Jean-Marc that once you are bringing
>work to a standard body it may require collaboration with other people who
>will have other proposals that will also address the same requirements and
>you may need to invest money in comparative testing by independent listening
>labs.
>
>I also think that you will need to supply the codec in source code and
>provide copy right to the IETF. 

Right, similar to was done with iLBC (though that was a 'donation' from a
single company).

-- 
Randell Jesup, Worldgate (developers of the Ojo videophone), ex-Amiga OS team
rjesup@wgate.com
"The fetters imposed on liberty at home have ever been forged out of the weapons
provided for defence against real, pretended, or imaginary dangers from abroad."
		- James Madison, 4th US president (1751-1836)


From jean-marc.valin@octasic.com  Tue Jun  2 08:13:39 2009
Return-Path: <jean-marc.valin@octasic.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 E717C3A6C78; Tue,  2 Jun 2009 08:13:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.299
X-Spam-Level: 
X-Spam-Status: No, score=-0.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MANGLED_INXPNS=2.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 UvztSh8hFe8U; Tue,  2 Jun 2009 08:13:38 -0700 (PDT)
Received: from MAILEXCH.octasic.com (mail.octasic.com [216.208.79.2]) by core3.amsl.com (Postfix) with ESMTP id 986B93A682D; Tue,  2 Jun 2009 08:13:38 -0700 (PDT)
Received: from [142.138.24.19] ([142.138.24.19]) by MAILEXCH.octasic.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 2 Jun 2009 11:13:39 -0400
Message-ID: <4A2541B9.2000805@octasic.com>
Date: Tue, 02 Jun 2009 11:14:01 -0400
From: Jean-Marc Valin <jean-marc.valin@octasic.com>
User-Agent: Thunderbird 2.0.0.21 (X11/20090409)
MIME-Version: 1.0
To: Roni Even <Even.roni@huawei.com>
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com>
In-Reply-To: <00a401c9e388$b25c2350$171469f0$%roni@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Jun 2009 15:13:39.0041 (UTC) FILETIME=[B5231510:01C9E394]
Cc: dispatch@ietf.org, hsinnrei@adobe.com, 'Slava Borilin' <Borilin@spiritdsp.com>, avt@ietf.org, 'Jason Fischl' <jason.fischl@skype.net>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 02 Jun 2009 15:13:40 -0000

Hi,

Roni Even wrote:
>
> I am not sure what prevented you from doing it today at the ITU or 
> MPEG, why do you see the IETF handling it differently.
>
> I would also like to remind you and Jean-Marc that once you are 
> bringing work to a standard body it may require collaboration with 
> other people who will have other proposals that will also address the 
> same requirements and you may need to invest money in comparative 
> testing by independent listening labs.
>
> I also think that you will need to supply the codec in source code and 
> provide copy right to the IETF.
>

I am well aware that bringing work to the IETF would require 
collaboration with others. I am not seeking control over the work I am 
currently doing and would really welcome such collaboration. The idea is 
only to have the best wideband codec possible without IPR issues. Given 
the ITU and MPEG track record, I think it would be very unlikely for any 
of those organisations to work on an IPR-free codec.

I also agree with Henry that "the Internet has different criteria than 
ITU-T networks may have". Internet adoption follows different patterns 
than adoption in the ITU primary target markets. For example, the 
Internet has more consumer-reconfigurable software, while the ITU has to 
deal with a lot of fixed hardware deployments. At the ITU, it makes 
sense to invest large sums of money into testing and characterisation of 
codecs because the codecs deployed there usually stay around for a long 
time and the infrastructure investments are usually very large. On the 
other hand, I would say the investments in codecs for the Internet are 
comparatively smaller and, while testing is still important, it is not 
as critical as it is for the ITU.

It's also a choice one has to make. It is unlikely that companies would 
invest money in expensive testing if they are not going to obtain 
royalties in return. However, I think we may be able to define some more 
lightweight (collaborative?) testing that is sufficient and doesn't 
involve as much investments as what the ITU does. For the Internet, I 
believe an IPR-free codec that everyone agrees performs well is better 
than a patent-encumbered codec that has had more extensive testing. This 
is again another difference with the ITU: patent-encumbered codecs tend 
to hurt a lot more on the Internet because many applications (e.g. 
giving away the client) are very hard (or impossible) when one has to 
pay per-channel royalties.

As for the source code issue you pointed out, all the Xiph codecs are 
already published under a very permissive open source license (BSD), so 
this would not really change.

    Jean-Marc

> Roni
>
>  
>
> *From:* avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] *On Behalf 
> Of *Slava Borilin
> *Sent:* Monday, June 01, 2009 11:50 PM
> *To:* jean-marc.valin@octasic.com
> *Cc:* avt@ietf.org; Jason Fischl
> *Subject:* Re: [AVT] [dispatch] Proposal to form Internet Wideband 
> Audio Codec WG
>
>  
>
> Agree with Jean-Marc.
> SPIRIT is interested to contribute as well - having a dozen of proprietary codecs developed, including 
> one specifically desgined for internet (SPIRIT IP-MR, which is now under WGLC on draft-ietf-avt-rtp-ipmr-04) - 
> multi-rate, scalable, adaptive, wideband codec.
>  
> We can also continue this work with IETF.
>  
> Moreover, most if not all efforts coming from ITU on codecs unfortunately are NOT really focused on 
> internet-specific codecs (that's why several companies have had to invent) - as ITU preference is mainly 
> specific (i.e. cellular) networks at first.
>  
> however, as we see the greant rise of pure "internet-basd communications" (skype, webex/citrix, and many others) - 
> we all (and users) are suffering from inefficiency in all currently "standard" codecs and ambiguity in the choice of 
> internet-targeted ones.
>  
> Again, we probably can put together enough number of contributors to the WG to have the expertise.
>  
> regards,
> Slava Borilin
>  
> --
> John Lazzaro wrote:
>
>     A traditional response to this type of request is to note that the IETF
>
>     really doesn't have much in the way of expertise in audio codec design.
>
>     I don't see many of the regulars who present at the AES codec paper sessions
>
>     posting here on AVT (ditto ICASSP paper sessions for voice codecs). It's
>
>     a full-time job to keep up-to-date and contribute to that
>
>     signal-processing lore.
>
>      
>
> Well, there's no reason that the IETF cannot build such an expertise 
> in audio codecs. This is actually something in which I'd be interested 
> in getting involved and I'm sure others at Xiph.Org would be 
> interested as well. We have several people with audio codec expertise 
> from working on Vorbis, Speex and (more recently) CELT. It turns out 
> that the CELT codec currently under development at Xiph actually meets 
> most of the requirements from the original proposal in being a very 
> low delay codec with adaptive bit-rate and sampling rate (up to 48 
> kHz), scalable complexity, and good robustness to packet loss. We'd be 
> willing to continue the development with the IETF. Even if not with 
> CELT, it's still like to be involved in such a new WG.
>
> Cheers,
>  
>    Jean-Marc


From shpungin@cs.bgu.ac.il  Sun May 31 23:25:01 2009
Return-Path: <shpungin@cs.bgu.ac.il>
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 A1CDD3A6879 for <avt@core3.amsl.com>; Sun, 31 May 2009 23:25:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[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 48v4VID9UFTy for <avt@core3.amsl.com>; Sun, 31 May 2009 23:25:00 -0700 (PDT)
Received: from indigo.cs.bgu.ac.il (indigo.cs.bgu.ac.il [132.72.42.23]) by core3.amsl.com (Postfix) with ESMTP id 3550F3A67A7 for <avt@ietf.org>; Sun, 31 May 2009 23:24:58 -0700 (PDT)
Received: from shpungin (frodo [132.72.41.75]) by indigo.cs.bgu.ac.il (8.13.6/8.13.6) with SMTP id n516OsIk023019 for <avt@ietf.org>; Mon, 1 Jun 2009 09:24:55 +0300 (IDT)
Date: Mon, 1 Jun 2009 09:24:54 +0300 (IDT)
Message-Id: <200906010624.n516OsIk023019@indigo.cs.bgu.ac.il>
From: Hanan Shpungin <shpungin@cs.bgu.ac.il>
To: avt@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Organization: CS Department
X-Mailer: CS Webmail v3.10
Priority: normal
X-Priority: 3 (Normal)
X-Mailman-Approved-At: Tue, 02 Jun 2009 08:59:45 -0700
Subject: [AVT] IFIP MedHocNet'09: Call for Participation (Haifa, Israel, June 2009)
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, 01 Jun 2009 06:25:01 -0000

* Apologies if you receive multiple copies of this message *

--- Call for Participation ---

The 8th IFIP Annual Mediterranean Ad Hoc Networking Workshop,
Med-Hoc-Net 2009

Haifa, Israel
Viterbi Computech Center,
Department of Electrical Engineering,
Technion-Israel Institute of Technology,
June 29-July 1, 2009

Technically sponsored by:
IEEE Communications Society and Euro-NF Network of Excellence
http://www.ee.technion.ac.il/med-hoc-net2009/index.htm

The registration form can be found in:
http://www.ee.technion.ac.il/med-hoc-net2009/registration.html

----------------------------------------------------------------

Med-Hoc-Net is a major annual international workshop, aiming to
serve as a platform for researchers and visionaries from academia,
research labs, and industry. Following Sicily (2006), Corfu (2007),
and Palma de Mallorca (2008), Med-Hoc-Net 2009 will take place in
Haifa (Israel).

We invite you to attend this year's workshop, which will be held
in the Viterbi Computech Center in the Department of Electrical
Engineering at the Technion-Israel Institute of Technology.

This year's keynote speaker is Prof. Mario Gerla from the Department
of Computer Science at UCLA.

The program includes 24 exciting talks spanning both theory and
practice, and focusing on various topics related to mobile ad hoc
networks, wireless mesh networks, sensor networks, vehicular networks,
and cognitive radio networks.

The full program can be viewed at:
http://www.ee.technion.ac.il/med-hoc-net2009/program.html

If you have any questions, please contact the General Chair, Adrian
Segall (segall@ee.technion.ac.il), or the Publicity Chair, Hanan
Shpungin (shpungin@cs.bgu.ac.il).




From Even.roni@huawei.com  Tue Jun  2 09:00:33 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D23263A68DD; Tue,  2 Jun 2009 09:00:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.831
X-Spam-Level: 
X-Spam-Status: No, score=0.831 tagged_above=-999 required=5 tests=[AWL=-1.325,  BAYES_00=-2.599, FRT_ADOBE2=2.455, MANGLED_INXPNS=2.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 3x-J11suuf71; Tue,  2 Jun 2009 09:00:31 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 7A39E3A6FFC; Tue,  2 Jun 2009 08:58:43 -0700 (PDT)
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 <0KKM00DASCDTRW@szxga04-in.huawei.com>; Tue, 02 Jun 2009 23:58:41 +0800 (CST)
Received: from huawei.com ([172.24.1.6]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KKM00KHMCDTTW@szxga04-in.huawei.com>; Tue, 02 Jun 2009 23:58:41 +0800 (CST)
Received: from windows8d787f9 (bzq-79-182-66-238.red.bezeqint.net [79.182.66.238]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KKM0091DCD2K7@szxml02-in.huawei.com>; Tue, 02 Jun 2009 23:58:41 +0800 (CST)
Date: Tue, 02 Jun 2009 18:57:16 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <4A2541B9.2000805@octasic.com>
To: 'Jean-Marc Valin' <jean-marc.valin@octasic.com>
Message-id: <00d501c9e39a$dcbbbe50$96333af0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcnjlMn504Jo+DIAQwytQ2cXiyrF0wABKOlw
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <4A2541B9.2000805@octasic.com>
Cc: dispatch@ietf.org, hsinnrei@adobe.com, 'Slava Borilin' <Borilin@spiritdsp.com>, avt@ietf.org, 'Jason Fischl' <jason.fischl@skype.net>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 02 Jun 2009 16:00:33 -0000

Hi,
I do not want to sound like someone who is for IPR (I am not), but why stop
at codec, let's require it for all IETF work. There are IPR on IETF work
which is must simpler, in my view, than wide band audio codecs.

I think that we can start with "royalty free" even though I am not sure that
it will accepted as part of the charter of any other work group so why pick
on codecs which require more work.

This leaves the other reasons I heard for doing it at the IETF which is the
price of participating (cheaper than being an ITU-T member) and maybe design
less expensive characterization tests.

Roni


-----Original Message-----
From: Jean-Marc Valin [mailto:jean-marc.valin@octasic.com] 
Sent: Tuesday, June 02, 2009 6:14 PM
To: Roni Even
Cc: 'Slava Borilin'; avt@ietf.org; 'Jason Fischl'; dispatch@ietf.org;
hsinnrei@adobe.com
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec
WG

Hi,

Roni Even wrote:
>
> I am not sure what prevented you from doing it today at the ITU or 
> MPEG, why do you see the IETF handling it differently.
>
> I would also like to remind you and Jean-Marc that once you are 
> bringing work to a standard body it may require collaboration with 
> other people who will have other proposals that will also address the 
> same requirements and you may need to invest money in comparative 
> testing by independent listening labs.
>
> I also think that you will need to supply the codec in source code and 
> provide copy right to the IETF.
>

I am well aware that bringing work to the IETF would require 
collaboration with others. I am not seeking control over the work I am 
currently doing and would really welcome such collaboration. The idea is 
only to have the best wideband codec possible without IPR issues. Given 
the ITU and MPEG track record, I think it would be very unlikely for any 
of those organisations to work on an IPR-free codec.

I also agree with Henry that "the Internet has different criteria than 
ITU-T networks may have". Internet adoption follows different patterns 
than adoption in the ITU primary target markets. For example, the 
Internet has more consumer-reconfigurable software, while the ITU has to 
deal with a lot of fixed hardware deployments. At the ITU, it makes 
sense to invest large sums of money into testing and characterisation of 
codecs because the codecs deployed there usually stay around for a long 
time and the infrastructure investments are usually very large. On the 
other hand, I would say the investments in codecs for the Internet are 
comparatively smaller and, while testing is still important, it is not 
as critical as it is for the ITU.

It's also a choice one has to make. It is unlikely that companies would 
invest money in expensive testing if they are not going to obtain 
royalties in return. However, I think we may be able to define some more 
lightweight (collaborative?) testing that is sufficient and doesn't 
involve as much investments as what the ITU does. For the Internet, I 
believe an IPR-free codec that everyone agrees performs well is better 
than a patent-encumbered codec that has had more extensive testing. This 
is again another difference with the ITU: patent-encumbered codecs tend 
to hurt a lot more on the Internet because many applications (e.g. 
giving away the client) are very hard (or impossible) when one has to 
pay per-channel royalties.

As for the source code issue you pointed out, all the Xiph codecs are 
already published under a very permissive open source license (BSD), so 
this would not really change.

    Jean-Marc

> Roni
>
>  
>
> *From:* avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] *On Behalf 
> Of *Slava Borilin
> *Sent:* Monday, June 01, 2009 11:50 PM
> *To:* jean-marc.valin@octasic.com
> *Cc:* avt@ietf.org; Jason Fischl
> *Subject:* Re: [AVT] [dispatch] Proposal to form Internet Wideband 
> Audio Codec WG
>
>  
>
> Agree with Jean-Marc.
> SPIRIT is interested to contribute as well - having a dozen of proprietary
codecs developed, including 
> one specifically desgined for internet (SPIRIT IP-MR, which is now under
WGLC on draft-ietf-avt-rtp-ipmr-04) - 
> multi-rate, scalable, adaptive, wideband codec.
>  
> We can also continue this work with IETF.
>  
> Moreover, most if not all efforts coming from ITU on codecs unfortunately
are NOT really focused on 
> internet-specific codecs (that's why several companies have had to invent)
- as ITU preference is mainly 
> specific (i.e. cellular) networks at first.
>  
> however, as we see the greant rise of pure "internet-basd communications"
(skype, webex/citrix, and many others) - 
> we all (and users) are suffering from inefficiency in all currently
"standard" codecs and ambiguity in the choice of 
> internet-targeted ones.
>  
> Again, we probably can put together enough number of contributors to the
WG to have the expertise.
>  
> regards,
> Slava Borilin
>  
> --
> John Lazzaro wrote:
>
>     A traditional response to this type of request is to note that the
IETF
>
>     really doesn't have much in the way of expertise in audio codec
design.
>
>     I don't see many of the regulars who present at the AES codec paper
sessions
>
>     posting here on AVT (ditto ICASSP paper sessions for voice codecs).
It's
>
>     a full-time job to keep up-to-date and contribute to that
>
>     signal-processing lore.
>
>      
>
> Well, there's no reason that the IETF cannot build such an expertise 
> in audio codecs. This is actually something in which I'd be interested 
> in getting involved and I'm sure others at Xiph.Org would be 
> interested as well. We have several people with audio codec expertise 
> from working on Vorbis, Speex and (more recently) CELT. It turns out 
> that the CELT codec currently under development at Xiph actually meets 
> most of the requirements from the original proposal in being a very 
> low delay codec with adaptive bit-rate and sampling rate (up to 48 
> kHz), scalable complexity, and good robustness to packet loss. We'd be 
> willing to continue the development with the IETF. Even if not with 
> CELT, it's still like to be involved in such a new WG.
>
> Cheers,
>  
>    Jean-Marc


From hgs@cs.columbia.edu  Tue Jun  2 09:16:31 2009
Return-Path: <hgs@cs.columbia.edu>
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 3A5903A6F2D; Tue,  2 Jun 2009 09:16:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.844
X-Spam-Level: 
X-Spam-Status: No, score=-1.844 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_ADOBE2=2.455, MANGLED_INXPNS=2.3, 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 RtHrmCP8GIPz; Tue,  2 Jun 2009 09:16:30 -0700 (PDT)
Received: from brinza.cc.columbia.edu (brinza.cc.columbia.edu [128.59.29.8]) by core3.amsl.com (Postfix) with ESMTP id D1F103A6BDE; Tue,  2 Jun 2009 09:16:29 -0700 (PDT)
Received: from ice.cs.columbia.edu (ice.cs.columbia.edu [128.59.18.177]) (user=hgs10 mech=PLAIN bits=0) by brinza.cc.columbia.edu (8.14.3/8.14.3) with ESMTP id n52GFqU0013510 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 2 Jun 2009 12:15:52 -0400 (EDT)
Message-Id: <D1611ACB-4739-4A65-94F0-403FC24CDC43@cs.columbia.edu>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
To: Roni Even <Even.roni@huawei.com>
In-Reply-To: <00d501c9e39a$dcbbbe50$96333af0$%roni@huawei.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 2 Jun 2009 12:15:51 -0400
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <4A2541B9.2000805@octasic.com> <00d501c9e39a$dcbbbe50$96333af0$%roni@huawei.com>
X-Mailer: Apple Mail (2.935.3)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.65 on 128.59.29.8
Cc: dispatch@ietf.org, 'Jason Fischl' <jason.fischl@skype.net>, avt@ietf.org, hsinnrei@adobe.com, 'Slava Borilin' <Borilin@spiritdsp.com>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 02 Jun 2009 16:16:31 -0000

I view this as a trade-off. If we pursue this, there are risks:

- nothing may come of it since there are no experts willing to help
- somebody will claim IPR on the resulting work
- the quality of the codec may not be competitive

However, if we don't do this, we are stuck with the status quo, which  
is not all that satisfactory. Thus, unless there are significant costs  
for "innocent bystanders", I see this as a risk worth taking. In the  
worst case, we are no worse off than we are today. In all other cases,  
we'll have an additional choice for a wideband codec, even if it's not  
"the best", just "good enough". After all, most people use G.711  
today, which has a really hard time making that claim.

Most real work in the IETF is done by very small teams, typically less  
than 10, so as long as we have a handful of people that are willing to  
contribute, this can work. It might even work better, since you may  
get fewer people who have half-baked opinions - we may skip the binary  
vs. XML debates...

We can set some ground rules ("must be tested with packet loss of 5%")  
and then see what happens. Compared to most network protocols, the  
likely negative impacts (such as security or congestion control  
issues) of even a badly-designed codec are pretty limited.

Henning

On Jun 2, 2009, at 11:57 AM, Roni Even wrote:

> Hi,
> I do not want to sound like someone who is for IPR (I am not), but  
> why stop
> at codec, let's require it for all IETF work. There are IPR on IETF  
> work
> which is must simpler, in my view, than wide band audio codecs.
>
> I think that we can start with "royalty free" even though I am not  
> sure that
> it will accepted as part of the charter of any other work group so  
> why pick
> on codecs which require more work.
>
> This leaves the other reasons I heard for doing it at the IETF which  
> is the
> price of participating (cheaper than being an ITU-T member) and  
> maybe design
> less expensive characterization tests.
>
> Roni
>
>
> -----Original Message-----
> From: Jean-Marc Valin [mailto:jean-marc.valin@octasic.com]
> Sent: Tuesday, June 02, 2009 6:14 PM
> To: Roni Even
> Cc: 'Slava Borilin'; avt@ietf.org; 'Jason Fischl'; dispatch@ietf.org;
> hsinnrei@adobe.com
> Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband  
> Audio Codec
> WG
>
> Hi,
>
> Roni Even wrote:
>>
>> I am not sure what prevented you from doing it today at the ITU or
>> MPEG, why do you see the IETF handling it differently.
>>
>> I would also like to remind you and Jean-Marc that once you are
>> bringing work to a standard body it may require collaboration with
>> other people who will have other proposals that will also address the
>> same requirements and you may need to invest money in comparative
>> testing by independent listening labs.
>>
>> I also think that you will need to supply the codec in source code  
>> and
>> provide copy right to the IETF.
>>
>
> I am well aware that bringing work to the IETF would require
> collaboration with others. I am not seeking control over the work I am
> currently doing and would really welcome such collaboration. The  
> idea is
> only to have the best wideband codec possible without IPR issues.  
> Given
> the ITU and MPEG track record, I think it would be very unlikely for  
> any
> of those organisations to work on an IPR-free codec.
>
> I also agree with Henry that "the Internet has different criteria than
> ITU-T networks may have". Internet adoption follows different patterns
> than adoption in the ITU primary target markets. For example, the
> Internet has more consumer-reconfigurable software, while the ITU  
> has to
> deal with a lot of fixed hardware deployments. At the ITU, it makes
> sense to invest large sums of money into testing and  
> characterisation of
> codecs because the codecs deployed there usually stay around for a  
> long
> time and the infrastructure investments are usually very large. On the
> other hand, I would say the investments in codecs for the Internet are
> comparatively smaller and, while testing is still important, it is not
> as critical as it is for the ITU.
>
> It's also a choice one has to make. It is unlikely that companies  
> would
> invest money in expensive testing if they are not going to obtain
> royalties in return. However, I think we may be able to define some  
> more
> lightweight (collaborative?) testing that is sufficient and doesn't
> involve as much investments as what the ITU does. For the Internet, I
> believe an IPR-free codec that everyone agrees performs well is better
> than a patent-encumbered codec that has had more extensive testing.  
> This
> is again another difference with the ITU: patent-encumbered codecs  
> tend
> to hurt a lot more on the Internet because many applications (e.g.
> giving away the client) are very hard (or impossible) when one has to
> pay per-channel royalties.
>
> As for the source code issue you pointed out, all the Xiph codecs are
> already published under a very permissive open source license (BSD),  
> so
> this would not really change.
>
>    Jean-Marc
>
>> Roni
>>
>>
>>
>> *From:* avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] *On Behalf
>> Of *Slava Borilin
>> *Sent:* Monday, June 01, 2009 11:50 PM
>> *To:* jean-marc.valin@octasic.com
>> *Cc:* avt@ietf.org; Jason Fischl
>> *Subject:* Re: [AVT] [dispatch] Proposal to form Internet Wideband
>> Audio Codec WG
>>
>>
>>
>> Agree with Jean-Marc.
>> SPIRIT is interested to contribute as well - having a dozen of  
>> proprietary
> codecs developed, including
>> one specifically desgined for internet (SPIRIT IP-MR, which is now  
>> under
> WGLC on draft-ietf-avt-rtp-ipmr-04) -
>> multi-rate, scalable, adaptive, wideband codec.
>>
>> We can also continue this work with IETF.
>>
>> Moreover, most if not all efforts coming from ITU on codecs  
>> unfortunately
> are NOT really focused on
>> internet-specific codecs (that's why several companies have had to  
>> invent)
> - as ITU preference is mainly
>> specific (i.e. cellular) networks at first.
>>
>> however, as we see the greant rise of pure "internet-basd  
>> communications"
> (skype, webex/citrix, and many others) -
>> we all (and users) are suffering from inefficiency in all currently
> "standard" codecs and ambiguity in the choice of
>> internet-targeted ones.
>>
>> Again, we probably can put together enough number of contributors  
>> to the
> WG to have the expertise.
>>
>> regards,
>> Slava Borilin
>>
>> --
>> John Lazzaro wrote:
>>
>>    A traditional response to this type of request is to note that the
> IETF
>>
>>    really doesn't have much in the way of expertise in audio codec
> design.
>>
>>    I don't see many of the regulars who present at the AES codec  
>> paper
> sessions
>>
>>    posting here on AVT (ditto ICASSP paper sessions for voice  
>> codecs).
> It's
>>
>>    a full-time job to keep up-to-date and contribute to that
>>
>>    signal-processing lore.
>>
>>
>>
>> Well, there's no reason that the IETF cannot build such an expertise
>> in audio codecs. This is actually something in which I'd be  
>> interested
>> in getting involved and I'm sure others at Xiph.Org would be
>> interested as well. We have several people with audio codec expertise
>> from working on Vorbis, Speex and (more recently) CELT. It turns out
>> that the CELT codec currently under development at Xiph actually  
>> meets
>> most of the requirements from the original proposal in being a very
>> low delay codec with adaptive bit-rate and sampling rate (up to 48
>> kHz), scalable complexity, and good robustness to packet loss. We'd  
>> be
>> willing to continue the development with the IETF. Even if not with
>> CELT, it's still like to be involved in such a new WG.
>>
>> Cheers,
>>
>>   Jean-Marc
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>


From jmpolk@cisco.com  Tue Jun  2 09:16:33 2009
Return-Path: <jmpolk@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 8C80E28C29C; Tue,  2 Jun 2009 09:16:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level: 
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5 tests=[AWL=-2.377, BAYES_00=-2.599, FRT_ADOBE2=2.455, MANGLED_INXPNS=2.3, 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 Qz-BDaRFzs87; Tue,  2 Jun 2009 09:16:32 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 3A8513A6FC2; Tue,  2 Jun 2009 09:16:32 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.41,291,1241395200"; d="scan'208";a="171678238"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-2.cisco.com with ESMTP; 02 Jun 2009 16:16:33 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n52GGXSB019885;  Tue, 2 Jun 2009 09:16:33 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n52GGXMA015591; Tue, 2 Jun 2009 16:16:33 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 2 Jun 2009 09:16:33 -0700
Received: from jmpolk-wxp01.cisco.com ([10.89.0.152]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 2 Jun 2009 09:16:32 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 02 Jun 2009 11:16:31 -0500
To: Henry Sinnreich <hsinnrei@adobe.com>, Roni Even <Even.roni@huawei.com>, Jean-Marc Valin <jean-marc.valin@octasic.com>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <C64AB99A.3E55%hsinnrei@adobe.com>
References: <00d501c9e39a$dcbbbe50$96333af0$%roni@huawei.com> <C64AB99A.3E55%hsinnrei@adobe.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <XFE-SJC-212wys7rhEc0000bd67@xfe-sjc-212.amer.cisco.com>
X-OriginalArrivalTime: 02 Jun 2009 16:16:32.0704 (UTC) FILETIME=[7E6A5C00:01C9E39D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=7706; t=1243959393; x=1244823393; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jmpolk@cisco.com; z=From:=20=22James=20M.=20Polk=22=20<jmpolk@cisco.com> |Subject:=20Re=3A=20[dispatch]=20[AVT]=20Proposal=20to=20fo rm=20Internet=20Wideband=20Audio=0A=20=20Codec=20WG |Sender:=20; bh=iScs2EaZ+GLpaCSs1vNnyMWptupqhMRFmxvY19FRjb0=; b=rEvBuThACgVGd3LO6bu9FCn41q0MIIRgn59qOgd7tgFwzynPZJqo0luMBE K3YDlvee3ReKlPKaSr9vI15M+ocXcmom02oyNcaCnqDdlyZNwd/JNUVyfUN8 C4VVCGtaLz;
Authentication-Results: sj-dkim-4; header.From=jmpolk@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Cc: "dispatch@ietf.org" <dispatch@ietf.org>, Slava Borilin <Borilin@spiritdsp.com>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 02 Jun 2009 16:16:33 -0000

At 11:12 AM 6/2/2009, Henry Sinnreich wrote:
>Content-Language: en
>Content-Type: multipart/alternative;
>         boundary="_000_C64AB99A3E55hsinnreiadobecom_"
>
> >This leaves the other reasons I heard for doing it at the IETF which is the
> >price of participating
>
>This is an important point.
>Given the travel constraints for some of the most valuable potential 
>contributors and reviewers, could we envisage online work until the 
>economy improves, so that an eventual BOF to start with should not 
>be starved of attendees?

Henry

this economic constraint will exist no matter which SDO this work 
eventually gets done in.

>An online BOF?
>
>There are several free online meeting tools available...
>
>How can this be done within the IETF policy?
>
>Henry
>
>
>On 6/2/09 10:57 AM, "Roni Even" 
><<Even.roni@huawei.htm>Even.roni@huawei.com> wrote:
>
>Hi,
>I do not want to sound like someone who is for IPR (I am not), but why stop
>at codec, let's require it for all IETF work. There are IPR on IETF work
>which is must simpler, in my view, than wide band audio codecs.
>
>I think that we can start with "royalty free" even though I am not sure that
>it will accepted as part of the charter of any other work group so why pick
>on codecs which require more work.
>
>This leaves the other reasons I heard for doing it at the IETF which is the
>price of participating (cheaper than being an ITU-T member) and maybe design
>less expensive characterization tests.
>
>Roni
>
>
>-----Original Message-----
>From: Jean-Marc Valin 
>[<mailto:jean-marc.valin@octasic.com>mailto:jean-marc.valin@octasic.com]
>Sent: Tuesday, June 02, 2009 6:14 PM
>To: Roni Even
>Cc: 'Slava Borilin'; <avt@ietf.htm>avt@ietf.org; 'Jason Fischl'; 
><dispatch@ietf.htm>dispatch@ietf.org;
><hsinnrei@adobe.htm>hsinnrei@adobe.com
>Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec
>WG
>
>Hi,
>
>Roni Even wrote:
> >
> > I am not sure what prevented you from doing it today at the ITU or
> > MPEG, why do you see the IETF handling it differently.
> >
> > I would also like to remind you and Jean-Marc that once you are
> > bringing work to a standard body it may require collaboration with
> > other people who will have other proposals that will also address the
> > same requirements and you may need to invest money in comparative
> > testing by independent listening labs.
> >
> > I also think that you will need to supply the codec in source code and
> > provide copy right to the IETF.
> >
>
>I am well aware that bringing work to the IETF would require
>collaboration with others. I am not seeking control over the work I am
>currently doing and would really welcome such collaboration. The idea is
>only to have the best wideband codec possible without IPR issues. Given
>the ITU and MPEG track record, I think it would be very unlikely for any
>of those organisations to work on an IPR-free codec.
>
>I also agree with Henry that "the Internet has different criteria than
>ITU-T networks may have". Internet adoption follows different patterns
>than adoption in the ITU primary target markets. For example, the
>Internet has more consumer-reconfigurable software, while the ITU has to
>deal with a lot of fixed hardware deployments. At the ITU, it makes
>sense to invest large sums of money into testing and characterisation of
>codecs because the codecs deployed there usually stay around for a long
>time and the infrastructure investments are usually very large. On the
>other hand, I would say the investments in codecs for the Internet are
>comparatively smaller and, while testing is still important, it is not
>as critical as it is for the ITU.
>
>It's also a choice one has to make. It is unlikely that companies would
>invest money in expensive testing if they are not going to obtain
>royalties in return. However, I think we may be able to define some more
>lightweight (collaborative?) testing that is sufficient and doesn't
>involve as much investments as what the ITU does. For the Internet, I
>believe an IPR-free codec that everyone agrees performs well is better
>than a patent-encumbered codec that has had more extensive testing. This
>is again another difference with the ITU: patent-encumbered codecs tend
>to hurt a lot more on the Internet because many applications (e.g.
>giving away the client) are very hard (or impossible) when one has to
>pay per-channel royalties.
>
>As for the source code issue you pointed out, all the Xiph codecs are
>already published under a very permissive open source license (BSD), so
>this would not really change.
>
>     Jean-Marc
>
> > Roni
> >
> >
> >
> > *From:* <avt-bounces@ietf.htm>avt-bounces@ietf.org 
> [mailto:avt-bounces@ietf.org] *On Behalf
> > Of *Slava Borilin
> > *Sent:* Monday, June 01, 2009 11:50 PM
> > *To:* <jean-marc.valin@octasic.htm>jean-marc.valin@octasic.com
> > *Cc:* <avt@ietf.htm>avt@ietf.org; Jason Fischl
> > *Subject:* Re: [AVT] [dispatch] Proposal to form Internet Wideband
> > Audio Codec WG
> >
> >
> >
> > Agree with Jean-Marc.
> > SPIRIT is interested to contribute as well - having a dozen of proprietary
>codecs developed, including
> > one specifically desgined for internet (SPIRIT IP-MR, which is now under
>WGLC on draft-ietf-avt-rtp-ipmr-04) -
> > multi-rate, scalable, adaptive, wideband codec.
> >
> > We can also continue this work with IETF.
> >
> > Moreover, most if not all efforts coming from ITU on codecs unfortunately
>are NOT really focused on
> > internet-specific codecs (that's why several companies have had to invent)
>- as ITU preference is mainly
> > specific (i.e. cellular) networks at first.
> >
> > however, as we see the greant rise of pure "internet-basd communications"
>(skype, webex/citrix, and many others) -
> > we all (and users) are suffering from inefficiency in all currently
>"standard" codecs and ambiguity in the choice of
> > internet-targeted ones.
> >
> > Again, we probably can put together enough number of contributors to the
>WG to have the expertise.
> >
> > regards,
> > Slava Borilin
> >
> > --
> > John Lazzaro wrote:
> >
> >     A traditional response to this type of request is to note that the
>IETF
> >
> >     really doesn't have much in the way of expertise in audio codec
>design.
> >
> >     I don't see many of the regulars who present at the AES codec paper
>sessions
> >
> >     posting here on AVT (ditto ICASSP paper sessions for voice codecs).
>It's
> >
> >     a full-time job to keep up-to-date and contribute to that
> >
> >     signal-processing lore.
> >
> >
> >
> > Well, there's no reason that the IETF cannot build such an expertise
> > in audio codecs. This is actually something in which I'd be interested
> > in getting involved and I'm sure others at Xiph.Org would be
> > interested as well. We have several people with audio codec expertise
> > from working on Vorbis, Speex and (more recently) CELT. It turns out
> > that the CELT codec currently under development at Xiph actually meets
> > most of the requirements from the original proposal in being a very
> > low delay codec with adaptive bit-rate and sampling rate (up to 48
> > kHz), scalable complexity, and good robustness to packet loss. We'd be
> > willing to continue the development with the IETF. Even if not with
> > CELT, it's still like to be involved in such a new WG.
> >
> > Cheers,
> >
> >    Jean-Marc
>
>
>_______________________________________________
>dispatch mailing list
>dispatch@ietf.org
>https://www.ietf.org/mailman/listinfo/dispatch


From stephen.botzko@gmail.com  Tue Jun  2 10:31:47 2009
Return-Path: <stephen.botzko@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 779443A6A98; Tue,  2 Jun 2009 10:31:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.221
X-Spam-Level: 
X-Spam-Status: No, score=-0.221 tagged_above=-999 required=5 tests=[AWL=-2.377, BAYES_00=-2.599, FRT_ADOBE2=2.455, HTML_MESSAGE=0.001, MANGLED_INXPNS=2.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 osBeYUdR697a; Tue,  2 Jun 2009 10:31:45 -0700 (PDT)
Received: from mail-bw0-f222.google.com (mail-bw0-f222.google.com [209.85.218.222]) by core3.amsl.com (Postfix) with ESMTP id 9238E3A6A67; Tue,  2 Jun 2009 10:31:44 -0700 (PDT)
Received: by bwz22 with SMTP id 22so8322580bwz.37 for <multiple recipients>; Tue, 02 Jun 2009 10:31:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=jkgqDHIpZ6KxglHw47dOJDV66Sr19ceaA57LXBLDBa4=; b=ZFUPck9V+oxspYr4lAd8gUipdsmz8vdZm737zDg3+n2sjj0mh0OCukghUVzur8Xo63 GelUjxMPQymA4eUPSf4omJ0+2yCpAzQzqJUhjghAsbAmV3NfYVjAXI52ESuzej5AvROF MYSzBYyQwNzr0eJSjsemPl37FBuTdY9g4ViaY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=NL+k3qvpjGJos1pqDCTyizg4V1h7XIWlbnOj2yFtjMEv15DPRdSgWwC83nPuwVoeex 0aZh+bk6HEVlb7P765mqLcAd2uFFCZJ8OjH2CITYqalqzhSL4iscnnk8UBkNYoVte0ok iBNqRPmQv9xXCAEUCeWIg9I5s0hTycQE66sok=
MIME-Version: 1.0
Received: by 10.103.176.20 with SMTP id d20mr4127295mup.27.1243963899982; Tue,  02 Jun 2009 10:31:39 -0700 (PDT)
In-Reply-To: <D1611ACB-4739-4A65-94F0-403FC24CDC43@cs.columbia.edu>
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <4A2541B9.2000805@octasic.com> <00d501c9e39a$dcbbbe50$96333af0$%roni@huawei.com> <D1611ACB-4739-4A65-94F0-403FC24CDC43@cs.columbia.edu>
Date: Tue, 2 Jun 2009 13:31:39 -0400
Message-ID: <6e9223710906021031i31e024dam5673ca9608017d73@mail.gmail.com>
From: stephen botzko <stephen.botzko@gmail.com>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Content-Type: multipart/alternative; boundary=00163641759b5f3983046b60ea82
Cc: dispatch@ietf.org, Jason Fischl <jason.fischl@skype.net>, avt@ietf.org, Roni Even <Even.roni@huawei.com>, hsinnrei@adobe.com, Slava Borilin <Borilin@spiritdsp.com>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 02 Jun 2009 17:31:47 -0000

--00163641759b5f3983046b60ea82
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

>>> - the quality of the codec may not be competitive

I think its very important that the codec quality be competitive.  People
expect excellence from IETF standards  Standardizing non-competitive codecs
because they are cheap does not seem to be a good choce.

Steve B.

On Tue, Jun 2, 2009 at 12:15 PM, Henning Schulzrinne <hgs@cs.columbia.edu>wrote:

> I view this as a trade-off. If we pursue this, there are risks:
>
> - nothing may come of it since there are no experts willing to help
> - somebody will claim IPR on the resulting work
> - the quality of the codec may not be competitive
>
> However, if we don't do this, we are stuck with the status quo, which is
> not all that satisfactory. Thus, unless there are significant costs for
> "innocent bystanders", I see this as a risk worth taking. In the worst case,
> we are no worse off than we are today. In all other cases, we'll have an
> additional choice for a wideband codec, even if it's not "the best", just
> "good enough". After all, most people use G.711 today, which has a really
> hard time making that claim.
>
> Most real work in the IETF is done by very small teams, typically less than
> 10, so as long as we have a handful of people that are willing to
> contribute, this can work. It might even work better, since you may get
> fewer people who have half-baked opinions - we may skip the binary vs. XML
> debates...
>
> We can set some ground rules ("must be tested with packet loss of 5%") and
> then see what happens. Compared to most network protocols, the likely
> negative impacts (such as security or congestion control issues) of even a
> badly-designed codec are pretty limited.
>
> Henning
>
>
> On Jun 2, 2009, at 11:57 AM, Roni Even wrote:
>
>  Hi,
>> I do not want to sound like someone who is for IPR (I am not), but why
>> stop
>> at codec, let's require it for all IETF work. There are IPR on IETF work
>> which is must simpler, in my view, than wide band audio codecs.
>>
>> I think that we can start with "royalty free" even though I am not sure
>> that
>> it will accepted as part of the charter of any other work group so why
>> pick
>> on codecs which require more work.
>>
>> This leaves the other reasons I heard for doing it at the IETF which is
>> the
>> price of participating (cheaper than being an ITU-T member) and maybe
>> design
>> less expensive characterization tests.
>>
>> Roni
>>
>>
>> -----Original Message-----
>> From: Jean-Marc Valin [mailto:jean-marc.valin@octasic.com]
>> Sent: Tuesday, June 02, 2009 6:14 PM
>> To: Roni Even
>> Cc: 'Slava Borilin'; avt@ietf.org; 'Jason Fischl'; dispatch@ietf.org;
>> hsinnrei@adobe.com
>> Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio
>> Codec
>> WG
>>
>> Hi,
>>
>> Roni Even wrote:
>>
>>>
>>> I am not sure what prevented you from doing it today at the ITU or
>>> MPEG, why do you see the IETF handling it differently.
>>>
>>> I would also like to remind you and Jean-Marc that once you are
>>> bringing work to a standard body it may require collaboration with
>>> other people who will have other proposals that will also address the
>>> same requirements and you may need to invest money in comparative
>>> testing by independent listening labs.
>>>
>>> I also think that you will need to supply the codec in source code and
>>> provide copy right to the IETF.
>>>
>>>
>> I am well aware that bringing work to the IETF would require
>> collaboration with others. I am not seeking control over the work I am
>> currently doing and would really welcome such collaboration. The idea is
>> only to have the best wideband codec possible without IPR issues. Given
>> the ITU and MPEG track record, I think it would be very unlikely for any
>> of those organisations to work on an IPR-free codec.
>>
>> I also agree with Henry that "the Internet has different criteria than
>> ITU-T networks may have". Internet adoption follows different patterns
>> than adoption in the ITU primary target markets. For example, the
>> Internet has more consumer-reconfigurable software, while the ITU has to
>> deal with a lot of fixed hardware deployments. At the ITU, it makes
>> sense to invest large sums of money into testing and characterisation of
>> codecs because the codecs deployed there usually stay around for a long
>> time and the infrastructure investments are usually very large. On the
>> other hand, I would say the investments in codecs for the Internet are
>> comparatively smaller and, while testing is still important, it is not
>> as critical as it is for the ITU.
>>
>> It's also a choice one has to make. It is unlikely that companies would
>> invest money in expensive testing if they are not going to obtain
>> royalties in return. However, I think we may be able to define some more
>> lightweight (collaborative?) testing that is sufficient and doesn't
>> involve as much investments as what the ITU does. For the Internet, I
>> believe an IPR-free codec that everyone agrees performs well is better
>> than a patent-encumbered codec that has had more extensive testing. This
>> is again another difference with the ITU: patent-encumbered codecs tend
>> to hurt a lot more on the Internet because many applications (e.g.
>> giving away the client) are very hard (or impossible) when one has to
>> pay per-channel royalties.
>>
>> As for the source code issue you pointed out, all the Xiph codecs are
>> already published under a very permissive open source license (BSD), so
>> this would not really change.
>>
>>   Jean-Marc
>>
>>  Roni
>>>
>>>
>>>
>>> *From:* avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] *On Behalf
>>> Of *Slava Borilin
>>> *Sent:* Monday, June 01, 2009 11:50 PM
>>> *To:* jean-marc.valin@octasic.com
>>> *Cc:* avt@ietf.org; Jason Fischl
>>> *Subject:* Re: [AVT] [dispatch] Proposal to form Internet Wideband
>>> Audio Codec WG
>>>
>>>
>>>
>>> Agree with Jean-Marc.
>>> SPIRIT is interested to contribute as well - having a dozen of
>>> proprietary
>>>
>> codecs developed, including
>>
>>> one specifically desgined for internet (SPIRIT IP-MR, which is now under
>>>
>> WGLC on draft-ietf-avt-rtp-ipmr-04) -
>>
>>> multi-rate, scalable, adaptive, wideband codec.
>>>
>>> We can also continue this work with IETF.
>>>
>>> Moreover, most if not all efforts coming from ITU on codecs unfortunately
>>>
>> are NOT really focused on
>>
>>> internet-specific codecs (that's why several companies have had to
>>> invent)
>>>
>> - as ITU preference is mainly
>>
>>> specific (i.e. cellular) networks at first.
>>>
>>> however, as we see the greant rise of pure "internet-basd communications"
>>>
>> (skype, webex/citrix, and many others) -
>>
>>> we all (and users) are suffering from inefficiency in all currently
>>>
>> "standard" codecs and ambiguity in the choice of
>>
>>> internet-targeted ones.
>>>
>>> Again, we probably can put together enough number of contributors to the
>>>
>> WG to have the expertise.
>>
>>>
>>> regards,
>>> Slava Borilin
>>>
>>> --
>>> John Lazzaro wrote:
>>>
>>>   A traditional response to this type of request is to note that the
>>>
>> IETF
>>
>>>
>>>   really doesn't have much in the way of expertise in audio codec
>>>
>> design.
>>
>>>
>>>   I don't see many of the regulars who present at the AES codec paper
>>>
>> sessions
>>
>>>
>>>   posting here on AVT (ditto ICASSP paper sessions for voice codecs).
>>>
>> It's
>>
>>>
>>>   a full-time job to keep up-to-date and contribute to that
>>>
>>>   signal-processing lore.
>>>
>>>
>>>
>>> Well, there's no reason that the IETF cannot build such an expertise
>>> in audio codecs. This is actually something in which I'd be interested
>>> in getting involved and I'm sure others at Xiph.Org would be
>>> interested as well. We have several people with audio codec expertise
>>> from working on Vorbis, Speex and (more recently) CELT. It turns out
>>> that the CELT codec currently under development at Xiph actually meets
>>> most of the requirements from the original proposal in being a very
>>> low delay codec with adaptive bit-rate and sampling rate (up to 48
>>> kHz), scalable complexity, and good robustness to packet loss. We'd be
>>> willing to continue the development with the IETF. Even if not with
>>> CELT, it's still like to be involved in such a new WG.
>>>
>>> Cheers,
>>>
>>>  Jean-Marc
>>>
>>
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>>
>>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>

--00163641759b5f3983046b60ea82
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

&gt;&gt;&gt; - the quality of the codec may not be competitive<br><br>I thi=
nk its very important that the codec quality be competitive.=A0 People expe=
ct excellence from IETF standards=A0 Standardizing non-competitive codecs b=
ecause they are cheap does not seem to be a good choce.<br>
<br>Steve B.<br><br><div class=3D"gmail_quote">On Tue, Jun 2, 2009 at 12:15=
 PM, Henning Schulzrinne <span dir=3D"ltr">&lt;<a href=3D"mailto:hgs@cs.col=
umbia.edu">hgs@cs.columbia.edu</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin=
: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I view this as a trade-off. If we pursue this, there are risks:<br>
<br>
- nothing may come of it since there are no experts willing to help<br>
- somebody will claim IPR on the resulting work<br>
- the quality of the codec may not be competitive<br>
<br>
However, if we don&#39;t do this, we are stuck with the status quo, which i=
s not all that satisfactory. Thus, unless there are significant costs for &=
quot;innocent bystanders&quot;, I see this as a risk worth taking. In the w=
orst case, we are no worse off than we are today. In all other cases, we&#3=
9;ll have an additional choice for a wideband codec, even if it&#39;s not &=
quot;the best&quot;, just &quot;good enough&quot;. After all, most people u=
se G.711 today, which has a really hard time making that claim.<br>

<br>
Most real work in the IETF is done by very small teams, typically less than=
 10, so as long as we have a handful of people that are willing to contribu=
te, this can work. It might even work better, since you may get fewer peopl=
e who have half-baked opinions - we may skip the binary vs. XML debates...<=
br>

<br>
We can set some ground rules (&quot;must be tested with packet loss of 5%&q=
uot;) and then see what happens. Compared to most network protocols, the li=
kely negative impacts (such as security or congestion control issues) of ev=
en a badly-designed codec are pretty limited.<br>
<font color=3D"#888888">
<br>
Henning</font><div><div></div><div class=3D"h5"><br>
<br>
On Jun 2, 2009, at 11:57 AM, Roni Even wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
I do not want to sound like someone who is for IPR (I am not), but why stop=
<br>
at codec, let&#39;s require it for all IETF work. There are IPR on IETF wor=
k<br>
which is must simpler, in my view, than wide band audio codecs.<br>
<br>
I think that we can start with &quot;royalty free&quot; even though I am no=
t sure that<br>
it will accepted as part of the charter of any other work group so why pick=
<br>
on codecs which require more work.<br>
<br>
This leaves the other reasons I heard for doing it at the IETF which is the=
<br>
price of participating (cheaper than being an ITU-T member) and maybe desig=
n<br>
less expensive characterization tests.<br>
<br>
Roni<br>
<br>
<br>
-----Original Message-----<br>
From: Jean-Marc Valin [mailto:<a href=3D"mailto:jean-marc.valin@octasic.com=
" target=3D"_blank">jean-marc.valin@octasic.com</a>]<br>
Sent: Tuesday, June 02, 2009 6:14 PM<br>
To: Roni Even<br>
Cc: &#39;Slava Borilin&#39;; <a href=3D"mailto:avt@ietf.org" target=3D"_bla=
nk">avt@ietf.org</a>; &#39;Jason Fischl&#39;; <a href=3D"mailto:dispatch@ie=
tf.org" target=3D"_blank">dispatch@ietf.org</a>;<br>
<a href=3D"mailto:hsinnrei@adobe.com" target=3D"_blank">hsinnrei@adobe.com<=
/a><br>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Code=
c<br>
WG<br>
<br>
Hi,<br>
<br>
Roni Even wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
I am not sure what prevented you from doing it today at the ITU or<br>
MPEG, why do you see the IETF handling it differently.<br>
<br>
I would also like to remind you and Jean-Marc that once you are<br>
bringing work to a standard body it may require collaboration with<br>
other people who will have other proposals that will also address the<br>
same requirements and you may need to invest money in comparative<br>
testing by independent listening labs.<br>
<br>
I also think that you will need to supply the codec in source code and<br>
provide copy right to the IETF.<br>
<br>
</blockquote>
<br>
I am well aware that bringing work to the IETF would require<br>
collaboration with others. I am not seeking control over the work I am<br>
currently doing and would really welcome such collaboration. The idea is<br=
>
only to have the best wideband codec possible without IPR issues. Given<br>
the ITU and MPEG track record, I think it would be very unlikely for any<br=
>
of those organisations to work on an IPR-free codec.<br>
<br>
I also agree with Henry that &quot;the Internet has different criteria than=
<br>
ITU-T networks may have&quot;. Internet adoption follows different patterns=
<br>
than adoption in the ITU primary target markets. For example, the<br>
Internet has more consumer-reconfigurable software, while the ITU has to<br=
>
deal with a lot of fixed hardware deployments. At the ITU, it makes<br>
sense to invest large sums of money into testing and characterisation of<br=
>
codecs because the codecs deployed there usually stay around for a long<br>
time and the infrastructure investments are usually very large. On the<br>
other hand, I would say the investments in codecs for the Internet are<br>
comparatively smaller and, while testing is still important, it is not<br>
as critical as it is for the ITU.<br>
<br>
It&#39;s also a choice one has to make. It is unlikely that companies would=
<br>
invest money in expensive testing if they are not going to obtain<br>
royalties in return. However, I think we may be able to define some more<br=
>
lightweight (collaborative?) testing that is sufficient and doesn&#39;t<br>
involve as much investments as what the ITU does. For the Internet, I<br>
believe an IPR-free codec that everyone agrees performs well is better<br>
than a patent-encumbered codec that has had more extensive testing. This<br=
>
is again another difference with the ITU: patent-encumbered codecs tend<br>
to hurt a lot more on the Internet because many applications (e.g.<br>
giving away the client) are very hard (or impossible) when one has to<br>
pay per-channel royalties.<br>
<br>
As for the source code issue you pointed out, all the Xiph codecs are<br>
already published under a very permissive open source license (BSD), so<br>
this would not really change.<br>
<br>
 =A0 Jean-Marc<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Roni<br>
<br>
<br>
<br>
*From:* <a href=3D"mailto:avt-bounces@ietf.org" target=3D"_blank">avt-bounc=
es@ietf.org</a> [mailto:<a href=3D"mailto:avt-bounces@ietf.org" target=3D"_=
blank">avt-bounces@ietf.org</a>] *On Behalf<br>
Of *Slava Borilin<br>
*Sent:* Monday, June 01, 2009 11:50 PM<br>
*To:* <a href=3D"mailto:jean-marc.valin@octasic.com" target=3D"_blank">jean=
-marc.valin@octasic.com</a><br>
*Cc:* <a href=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.org</a>; J=
ason Fischl<br>
*Subject:* Re: [AVT] [dispatch] Proposal to form Internet Wideband<br>
Audio Codec WG<br>
<br>
<br>
<br>
Agree with Jean-Marc.<br>
SPIRIT is interested to contribute as well - having a dozen of proprietary<=
br>
</blockquote>
codecs developed, including<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
one specifically desgined for internet (SPIRIT IP-MR, which is now under<br=
>
</blockquote>
WGLC on draft-ietf-avt-rtp-ipmr-04) -<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
multi-rate, scalable, adaptive, wideband codec.<br>
<br>
We can also continue this work with IETF.<br>
<br>
Moreover, most if not all efforts coming from ITU on codecs unfortunately<b=
r>
</blockquote>
are NOT really focused on<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
internet-specific codecs (that&#39;s why several companies have had to inve=
nt)<br>
</blockquote>
- as ITU preference is mainly<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
specific (i.e. cellular) networks at first.<br>
<br>
however, as we see the greant rise of pure &quot;internet-basd communicatio=
ns&quot;<br>
</blockquote>
(skype, webex/citrix, and many others) -<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
we all (and users) are suffering from inefficiency in all currently<br>
</blockquote>
&quot;standard&quot; codecs and ambiguity in the choice of<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
internet-targeted ones.<br>
<br>
Again, we probably can put together enough number of contributors to the<br=
>
</blockquote>
WG to have the expertise.<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
regards,<br>
Slava Borilin<br>
<br>
--<br>
John Lazzaro wrote:<br>
<br>
 =A0 A traditional response to this type of request is to note that the<br>
</blockquote>
IETF<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
 =A0 really doesn&#39;t have much in the way of expertise in audio codec<br=
>
</blockquote>
design.<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
 =A0 I don&#39;t see many of the regulars who present at the AES codec pape=
r<br>
</blockquote>
sessions<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
 =A0 posting here on AVT (ditto ICASSP paper sessions for voice codecs).<br=
>
</blockquote>
It&#39;s<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
 =A0 a full-time job to keep up-to-date and contribute to that<br>
<br>
 =A0 signal-processing lore.<br>
<br>
<br>
<br>
Well, there&#39;s no reason that the IETF cannot build such an expertise<br=
>
in audio codecs. This is actually something in which I&#39;d be interested<=
br>
in getting involved and I&#39;m sure others at Xiph.Org would be<br>
interested as well. We have several people with audio codec expertise<br>
from working on Vorbis, Speex and (more recently) CELT. It turns out<br>
that the CELT codec currently under development at Xiph actually meets<br>
most of the requirements from the original proposal in being a very<br>
low delay codec with adaptive bit-rate and sampling rate (up to 48<br>
kHz), scalable complexity, and good robustness to packet loss. We&#39;d be<=
br>
willing to continue the development with the IETF. Even if not with<br>
CELT, it&#39;s still like to be involved in such a new WG.<br>
<br>
Cheers,<br>
<br>
 =A0Jean-Marc<br>
</blockquote>
<br>
_______________________________________________<br>
Audio/Video Transport Working Group<br>
<a href=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/avt</a><br>
<br>
</blockquote>
<br>
_______________________________________________<br>
Audio/Video Transport Working Group<br>
<a href=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/avt</a><br>
</div></div></blockquote></div><br>

--00163641759b5f3983046b60ea82--

From Borilin@spiritdsp.com  Tue Jun  2 10:34:42 2009
Return-Path: <Borilin@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 081FE3A6B0A; Tue,  2 Jun 2009 10:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.188
X-Spam-Level: 
X-Spam-Status: No, score=0.188 tagged_above=-999 required=5 tests=[AWL=-1.969,  BAYES_00=-2.599, FRT_ADOBE2=2.455, HTML_MESSAGE=0.001, MANGLED_INXPNS=2.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 1jjpmJKmbzZw; Tue,  2 Jun 2009 10:34:40 -0700 (PDT)
Received: from mail3.spiritcorp.com (mail3.spiritcorp.com [85.13.194.167]) by core3.amsl.com (Postfix) with ESMTP id 236F03A6F44; Tue,  2 Jun 2009 10:34:36 -0700 (PDT)
Received: from mail-srv.spiritcorp.com (mail-srv.spiritcorp.com [192.168.125.3]) by mail3.spiritcorp.com (8.13.8/8.14.3) with SMTP id n52HXu8Z066709; Tue, 2 Jun 2009 21:33:57 +0400 (MSD) (envelope-from Borilin@spiritdsp.com)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9E3A8.4D82F4FA"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 2 Jun 2009 21:33:54 +0400
Message-ID: <AA5A65FC22B6F145830AC0EAC7586A6C04BF9091@mail-srv.spiritcorp.com>
In-Reply-To: <6e9223710906021031i31e024dam5673ca9608017d73@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
Thread-Index: AcnjqANErfh4GUqeQ4SC5NZuzNxHZgAAB2LQ
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <4A2541B9.2000805@octasic.com> <00d501c9e39a$dcbbbe50$96333af0$%roni@huawei.com> <D1611ACB-4739-4A65-94F0-403FC24CDC43@cs.columbia.edu> <6e9223710906021031i31e024dam5673ca9608017d73@mail.gmail.com>
From: "Slava Borilin" <Borilin@spiritdsp.com>
To: "stephen botzko" <stephen.botzko@gmail.com>, "Henning Schulzrinne" <hgs@cs.columbia.edu>
X-Scanned-By: MIMEDefang 2.64 on 192.168.125.15
Cc: hsinnrei@adobe.com, dispatch@ietf.org, avt@ietf.org, Roni Even <Even.roni@huawei.com>, Jason Fischl <jason.fischl@skype.net>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 02 Jun 2009 17:34:42 -0000

This is a multi-part message in MIME format.

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

I do not beleive the one that will come wil be low quality.
at least people from the potential contributors (at least Skype, Speex,
SPIRIT) are already pretty-good in the commercially exploiting their own
codecs on the market.
i think this is probably false alert.
=20
regards,
Slava Borilin
=20
=20

________________________________

From: stephen botzko [mailto:stephen.botzko@gmail.com]=20
Sent: Tuesday, June 02, 2009 9:32 PM
To: Henning Schulzrinne
Cc: Roni Even; dispatch@ietf.org; Jason Fischl; avt@ietf.org;
hsinnrei@adobe.com; Slava Borilin
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio
Codec WG


>>> - the quality of the codec may not be competitive

I think its very important that the codec quality be competitive.
People expect excellence from IETF standards  Standardizing
non-competitive codecs because they are cheap does not seem to be a good
choce.

Steve B.


On Tue, Jun 2, 2009 at 12:15 PM, Henning Schulzrinne
<hgs@cs.columbia.edu> wrote:


	I view this as a trade-off. If we pursue this, there are risks:
=09
	- nothing may come of it since there are no experts willing to
help
	- somebody will claim IPR on the resulting work
	- the quality of the codec may not be competitive
=09
	However, if we don't do this, we are stuck with the status quo,
which is not all that satisfactory. Thus, unless there are significant
costs for "innocent bystanders", I see this as a risk worth taking. In
the worst case, we are no worse off than we are today. In all other
cases, we'll have an additional choice for a wideband codec, even if
it's not "the best", just "good enough". After all, most people use
G.711 today, which has a really hard time making that claim.
=09
	Most real work in the IETF is done by very small teams,
typically less than 10, so as long as we have a handful of people that
are willing to contribute, this can work. It might even work better,
since you may get fewer people who have half-baked opinions - we may
skip the binary vs. XML debates...
=09
	We can set some ground rules ("must be tested with packet loss
of 5%") and then see what happens. Compared to most network protocols,
the likely negative impacts (such as security or congestion control
issues) of even a badly-designed codec are pretty limited.
=09
	Henning=20


	On Jun 2, 2009, at 11:57 AM, Roni Even wrote:
=09
=09

		Hi,
		I do not want to sound like someone who is for IPR (I am
not), but why stop
		at codec, let's require it for all IETF work. There are
IPR on IETF work
		which is must simpler, in my view, than wide band audio
codecs.
	=09
		I think that we can start with "royalty free" even
though I am not sure that
		it will accepted as part of the charter of any other
work group so why pick
		on codecs which require more work.
	=09
		This leaves the other reasons I heard for doing it at
the IETF which is the
		price of participating (cheaper than being an ITU-T
member) and maybe design
		less expensive characterization tests.
	=09
		Roni
	=09
	=09
		-----Original Message-----
		From: Jean-Marc Valin
[mailto:jean-marc.valin@octasic.com]
		Sent: Tuesday, June 02, 2009 6:14 PM
		To: Roni Even
		Cc: 'Slava Borilin'; avt@ietf.org; 'Jason Fischl';
dispatch@ietf.org;
		hsinnrei@adobe.com
		Subject: Re: [AVT] [dispatch] Proposal to form Internet
Wideband Audio Codec
		WG
	=09
		Hi,
	=09
		Roni Even wrote:
	=09


			I am not sure what prevented you from doing it
today at the ITU or
			MPEG, why do you see the IETF handling it
differently.
		=09
			I would also like to remind you and Jean-Marc
that once you are
			bringing work to a standard body it may require
collaboration with
			other people who will have other proposals that
will also address the
			same requirements and you may need to invest
money in comparative
			testing by independent listening labs.
		=09
			I also think that you will need to supply the
codec in source code and
			provide copy right to the IETF.
		=09
		=09


		I am well aware that bringing work to the IETF would
require
		collaboration with others. I am not seeking control over
the work I am
		currently doing and would really welcome such
collaboration. The idea is
		only to have the best wideband codec possible without
IPR issues. Given
		the ITU and MPEG track record, I think it would be very
unlikely for any
		of those organisations to work on an IPR-free codec.
	=09
		I also agree with Henry that "the Internet has different
criteria than
		ITU-T networks may have". Internet adoption follows
different patterns
		than adoption in the ITU primary target markets. For
example, the
		Internet has more consumer-reconfigurable software,
while the ITU has to
		deal with a lot of fixed hardware deployments. At the
ITU, it makes
		sense to invest large sums of money into testing and
characterisation of
		codecs because the codecs deployed there usually stay
around for a long
		time and the infrastructure investments are usually very
large. On the
		other hand, I would say the investments in codecs for
the Internet are
		comparatively smaller and, while testing is still
important, it is not
		as critical as it is for the ITU.
	=09
		It's also a choice one has to make. It is unlikely that
companies would
		invest money in expensive testing if they are not going
to obtain
		royalties in return. However, I think we may be able to
define some more
		lightweight (collaborative?) testing that is sufficient
and doesn't
		involve as much investments as what the ITU does. For
the Internet, I
		believe an IPR-free codec that everyone agrees performs
well is better
		than a patent-encumbered codec that has had more
extensive testing. This
		is again another difference with the ITU:
patent-encumbered codecs tend
		to hurt a lot more on the Internet because many
applications (e.g.
		giving away the client) are very hard (or impossible)
when one has to
		pay per-channel royalties.
	=09
		As for the source code issue you pointed out, all the
Xiph codecs are
		already published under a very permissive open source
license (BSD), so
		this would not really change.
	=09
		  Jean-Marc
	=09
	=09

			Roni
		=09
		=09
		=09
			*From:* avt-bounces@ietf.org
[mailto:avt-bounces@ietf.org] *On Behalf
			Of *Slava Borilin
			*Sent:* Monday, June 01, 2009 11:50 PM
			*To:* jean-marc.valin@octasic.com
			*Cc:* avt@ietf.org; Jason Fischl
			*Subject:* Re: [AVT] [dispatch] Proposal to form
Internet Wideband
			Audio Codec WG
		=09
		=09
		=09
			Agree with Jean-Marc.
			SPIRIT is interested to contribute as well -
having a dozen of proprietary
		=09

		codecs developed, including
	=09

			one specifically desgined for internet (SPIRIT
IP-MR, which is now under
		=09

		WGLC on draft-ietf-avt-rtp-ipmr-04) -
	=09

			multi-rate, scalable, adaptive, wideband codec.
		=09
			We can also continue this work with IETF.
		=09
			Moreover, most if not all efforts coming from
ITU on codecs unfortunately
		=09

		are NOT really focused on
	=09

			internet-specific codecs (that's why several
companies have had to invent)
		=09

		- as ITU preference is mainly
	=09

			specific (i.e. cellular) networks at first.
		=09
			however, as we see the greant rise of pure
"internet-basd communications"
		=09

		(skype, webex/citrix, and many others) -
	=09

			we all (and users) are suffering from
inefficiency in all currently
		=09

		"standard" codecs and ambiguity in the choice of
	=09

			internet-targeted ones.
		=09
			Again, we probably can put together enough
number of contributors to the
		=09

		WG to have the expertise.
	=09


			regards,
			Slava Borilin
		=09
			--
			John Lazzaro wrote:
		=09
			  A traditional response to this type of request
is to note that the
		=09

		IETF
	=09


			  really doesn't have much in the way of
expertise in audio codec
		=09

		design.
	=09


			  I don't see many of the regulars who present
at the AES codec paper
		=09

		sessions
	=09


			  posting here on AVT (ditto ICASSP paper
sessions for voice codecs).
		=09

		It's
	=09


			  a full-time job to keep up-to-date and
contribute to that
		=09
			  signal-processing lore.
		=09
		=09
		=09
			Well, there's no reason that the IETF cannot
build such an expertise
			in audio codecs. This is actually something in
which I'd be interested
			in getting involved and I'm sure others at
Xiph.Org would be
			interested as well. We have several people with
audio codec expertise
			from working on Vorbis, Speex and (more
recently) CELT. It turns out
			that the CELT codec currently under development
at Xiph actually meets
			most of the requirements from the original
proposal in being a very
			low delay codec with adaptive bit-rate and
sampling rate (up to 48
			kHz), scalable complexity, and good robustness
to packet loss. We'd be
			willing to continue the development with the
IETF. Even if not with
			CELT, it's still like to be involved in such a
new WG.
		=09
			Cheers,
		=09
			 Jean-Marc
		=09


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


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



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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16640" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D203403217-02062009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I do not beleive the one that will come wil be =
low=20
quality.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D203403217-02062009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>at least people from the potential contributors =
(at least=20
Skype, Speex, SPIRIT) are already pretty-good in the commercially =
exploiting=20
their own codecs on the market.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D203403217-02062009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>i think this is probably false =
alert.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>regards,</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Slava Borilin</FONT></DIV>
<DIV align=3Dleft><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN>&nbsp;</DIV>
<DIV>&nbsp;</DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> stephen botzko=20
[mailto:stephen.botzko@gmail.com] <BR><B>Sent:</B> Tuesday, June 02, =
2009 9:32=20
PM<BR><B>To:</B> Henning Schulzrinne<BR><B>Cc:</B> Roni Even; =
dispatch@ietf.org;=20
Jason Fischl; avt@ietf.org; hsinnrei@adobe.com; Slava =
Borilin<BR><B>Subject:</B>=20
Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec=20
WG<BR></FONT><BR></DIV>
<DIV></DIV>&gt;&gt;&gt; - the quality of the codec may not be=20
competitive<BR><BR>I think its very important that the codec quality be=20
competitive.&nbsp; People expect excellence from IETF standards&nbsp;=20
Standardizing non-competitive codecs because they are cheap does not =
seem to be=20
a good choce.<BR><BR>Steve B.<BR><BR>
<DIV class=3Dgmail_quote>On Tue, Jun 2, 2009 at 12:15 PM, Henning =
Schulzrinne=20
<SPAN dir=3Dltr>&lt;<A=20
href=3D"mailto:hgs@cs.columbia.edu">hgs@cs.columbia.edu</A>&gt;</SPAN> =
wrote:<BR>
<BLOCKQUOTE class=3Dgmail_quote=20
style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid">I=20
  view this as a trade-off. If we pursue this, there are risks:<BR><BR>- =
nothing=20
  may come of it since there are no experts willing to help<BR>- =
somebody will=20
  claim IPR on the resulting work<BR>- the quality of the codec may not =
be=20
  competitive<BR><BR>However, if we don't do this, we are stuck with the =
status=20
  quo, which is not all that satisfactory. Thus, unless there are =
significant=20
  costs for "innocent bystanders", I see this as a risk worth taking. In =
the=20
  worst case, we are no worse off than we are today. In all other cases, =
we'll=20
  have an additional choice for a wideband codec, even if it's not "the =
best",=20
  just "good enough". After all, most people use G.711 today, which has =
a really=20
  hard time making that claim.<BR><BR>Most real work in the IETF is done =
by very=20
  small teams, typically less than 10, so as long as we have a handful =
of people=20
  that are willing to contribute, this can work. It might even work =
better,=20
  since you may get fewer people who have half-baked opinions - we may =
skip the=20
  binary vs. XML debates...<BR><BR>We can set some ground rules ("must =
be tested=20
  with packet loss of 5%") and then see what happens. Compared to most =
network=20
  protocols, the likely negative impacts (such as security or congestion =
control=20
  issues) of even a badly-designed codec are pretty limited.<BR><FONT=20
  color=3D#888888><BR>Henning</FONT>
  <DIV>
  <DIV></DIV>
  <DIV class=3Dh5><BR><BR>On Jun 2, 2009, at 11:57 AM, Roni Even =
wrote:<BR><BR>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid">Hi,<BR>I=20
    do not want to sound like someone who is for IPR (I am not), but why =

    stop<BR>at codec, let's require it for all IETF work. There are IPR =
on IETF=20
    work<BR>which is must simpler, in my view, than wide band audio=20
    codecs.<BR><BR>I think that we can start with "royalty free" even =
though I=20
    am not sure that<BR>it will accepted as part of the charter of any =
other=20
    work group so why pick<BR>on codecs which require more =
work.<BR><BR>This=20
    leaves the other reasons I heard for doing it at the IETF which is=20
    the<BR>price of participating (cheaper than being an ITU-T member) =
and maybe=20
    design<BR>less expensive characterization=20
    tests.<BR><BR>Roni<BR><BR><BR>-----Original Message-----<BR>From: =
Jean-Marc=20
    Valin [mailto:<A href=3D"mailto:jean-marc.valin@octasic.com"=20
    target=3D_blank>jean-marc.valin@octasic.com</A>]<BR>Sent: Tuesday, =
June 02,=20
    2009 6:14 PM<BR>To: Roni Even<BR>Cc: 'Slava Borilin'; <A=20
    href=3D"mailto:avt@ietf.org" target=3D_blank>avt@ietf.org</A>; =
'Jason Fischl';=20
    <A href=3D"mailto:dispatch@ietf.org"=20
    target=3D_blank>dispatch@ietf.org</A>;<BR><A =
href=3D"mailto:hsinnrei@adobe.com"=20
    target=3D_blank>hsinnrei@adobe.com</A><BR>Subject: Re: [AVT] =
[dispatch]=20
    Proposal to form Internet Wideband Audio =
Codec<BR>WG<BR><BR>Hi,<BR><BR>Roni=20
    Even wrote:<BR>
    <BLOCKQUOTE class=3Dgmail_quote=20
    style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid"><BR>I=20
      am not sure what prevented you from doing it today at the ITU =
or<BR>MPEG,=20
      why do you see the IETF handling it differently.<BR><BR>I would =
also like=20
      to remind you and Jean-Marc that once you are<BR>bringing work to =
a=20
      standard body it may require collaboration with<BR>other people =
who will=20
      have other proposals that will also address the<BR>same =
requirements and=20
      you may need to invest money in comparative<BR>testing by =
independent=20
      listening labs.<BR><BR>I also think that you will need to supply =
the codec=20
      in source code and<BR>provide copy right to the=20
    IETF.<BR><BR></BLOCKQUOTE><BR>I am well aware that bringing work to =
the IETF=20
    would require<BR>collaboration with others. I am not seeking control =
over=20
    the work I am<BR>currently doing and would really welcome such=20
    collaboration. The idea is<BR>only to have the best wideband codec =
possible=20
    without IPR issues. Given<BR>the ITU and MPEG track record, I think =
it would=20
    be very unlikely for any<BR>of those organisations to work on an =
IPR-free=20
    codec.<BR><BR>I also agree with Henry that "the Internet has =
different=20
    criteria than<BR>ITU-T networks may have". Internet adoption follows =

    different patterns<BR>than adoption in the ITU primary target =
markets. For=20
    example, the<BR>Internet has more consumer-reconfigurable software, =
while=20
    the ITU has to<BR>deal with a lot of fixed hardware deployments. At =
the ITU,=20
    it makes<BR>sense to invest large sums of money into testing and=20
    characterisation of<BR>codecs because the codecs deployed there =
usually stay=20
    around for a long<BR>time and the infrastructure investments are =
usually=20
    very large. On the<BR>other hand, I would say the investments in =
codecs for=20
    the Internet are<BR>comparatively smaller and, while testing is =
still=20
    important, it is not<BR>as critical as it is for the =
ITU.<BR><BR>It's also a=20
    choice one has to make. It is unlikely that companies =
would<BR>invest money=20
    in expensive testing if they are not going to obtain<BR>royalties in =
return.=20
    However, I think we may be able to define some more<BR>lightweight=20
    (collaborative?) testing that is sufficient and doesn't<BR>involve =
as much=20
    investments as what the ITU does. For the Internet, I<BR>believe an =
IPR-free=20
    codec that everyone agrees performs well is better<BR>than a=20
    patent-encumbered codec that has had more extensive testing. =
This<BR>is=20
    again another difference with the ITU: patent-encumbered codecs =
tend<BR>to=20
    hurt a lot more on the Internet because many applications =
(e.g.<BR>giving=20
    away the client) are very hard (or impossible) when one has =
to<BR>pay=20
    per-channel royalties.<BR><BR>As for the source code issue you =
pointed out,=20
    all the Xiph codecs are<BR>already published under a very permissive =
open=20
    source license (BSD), so<BR>this would not really =
change.<BR><BR>&nbsp;=20
    Jean-Marc<BR><BR>
    <BLOCKQUOTE class=3Dgmail_quote=20
    style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid">Roni<BR><BR><BR><BR>*From:*=20
      <A href=3D"mailto:avt-bounces@ietf.org"=20
      target=3D_blank>avt-bounces@ietf.org</A> [mailto:<A=20
      href=3D"mailto:avt-bounces@ietf.org" =
target=3D_blank>avt-bounces@ietf.org</A>]=20
      *On Behalf<BR>Of *Slava Borilin<BR>*Sent:* Monday, June 01, 2009 =
11:50=20
      PM<BR>*To:* <A href=3D"mailto:jean-marc.valin@octasic.com"=20
      target=3D_blank>jean-marc.valin@octasic.com</A><BR>*Cc:* <A=20
      href=3D"mailto:avt@ietf.org" target=3D_blank>avt@ietf.org</A>; =
Jason=20
      Fischl<BR>*Subject:* Re: [AVT] [dispatch] Proposal to form =
Internet=20
      Wideband<BR>Audio Codec WG<BR><BR><BR><BR>Agree with =
Jean-Marc.<BR>SPIRIT=20
      is interested to contribute as well - having a dozen of=20
    proprietary<BR></BLOCKQUOTE>codecs developed, including<BR>
    <BLOCKQUOTE class=3Dgmail_quote=20
    style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid">one=20
      specifically desgined for internet (SPIRIT IP-MR, which is now=20
    under<BR></BLOCKQUOTE>WGLC on draft-ietf-avt-rtp-ipmr-04) -<BR>
    <BLOCKQUOTE class=3Dgmail_quote=20
    style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid">multi-rate,=20
      scalable, adaptive, wideband codec.<BR><BR>We can also continue =
this work=20
      with IETF.<BR><BR>Moreover, most if not all efforts coming from =
ITU on=20
      codecs unfortunately<BR></BLOCKQUOTE>are NOT really focused on<BR>
    <BLOCKQUOTE class=3Dgmail_quote=20
    style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid">internet-specific=20
      codecs (that's why several companies have had to =
invent)<BR></BLOCKQUOTE>-=20
    as ITU preference is mainly<BR>
    <BLOCKQUOTE class=3Dgmail_quote=20
    style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid">specific=20
      (i.e. cellular) networks at first.<BR><BR>however, as we see the =
greant=20
      rise of pure "internet-basd =
communications"<BR></BLOCKQUOTE>(skype,=20
    webex/citrix, and many others) -<BR>
    <BLOCKQUOTE class=3Dgmail_quote=20
    style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid">we=20
      all (and users) are suffering from inefficiency in all=20
    currently<BR></BLOCKQUOTE>"standard" codecs and ambiguity in the =
choice=20
    of<BR>
    <BLOCKQUOTE class=3Dgmail_quote=20
    style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid">internet-targeted=20
      ones.<BR><BR>Again, we probably can put together enough number of=20
      contributors to the<BR></BLOCKQUOTE>WG to have the expertise.<BR>
    <BLOCKQUOTE class=3Dgmail_quote=20
    style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid"><BR>regards,<BR>Slava=20
      Borilin<BR><BR>--<BR>John Lazzaro wrote:<BR><BR>&nbsp; A =
traditional=20
      response to this type of request is to note that=20
the<BR></BLOCKQUOTE>IETF<BR>
    <BLOCKQUOTE class=3Dgmail_quote=20
    style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid"><BR>&nbsp;=20
      really doesn't have much in the way of expertise in audio=20
    codec<BR></BLOCKQUOTE>design.<BR>
    <BLOCKQUOTE class=3Dgmail_quote=20
    style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid"><BR>&nbsp;=20
      I don't see many of the regulars who present at the AES codec=20
    paper<BR></BLOCKQUOTE>sessions<BR>
    <BLOCKQUOTE class=3Dgmail_quote=20
    style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid"><BR>&nbsp;=20
      posting here on AVT (ditto ICASSP paper sessions for voice=20
    codecs).<BR></BLOCKQUOTE>It's<BR>
    <BLOCKQUOTE class=3Dgmail_quote=20
    style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid"><BR>&nbsp;=20
      a full-time job to keep up-to-date and contribute to =
that<BR><BR>&nbsp;=20
      signal-processing lore.<BR><BR><BR><BR>Well, there's no reason =
that the=20
      IETF cannot build such an expertise<BR>in audio codecs. This is =
actually=20
      something in which I'd be interested<BR>in getting involved and =
I'm sure=20
      others at Xiph.Org would be<BR>interested as well. We have several =
people=20
      with audio codec expertise<BR>from working on Vorbis, Speex and =
(more=20
      recently) CELT. It turns out<BR>that the CELT codec currently =
under=20
      development at Xiph actually meets<BR>most of the requirements =
from the=20
      original proposal in being a very<BR>low delay codec with adaptive =

      bit-rate and sampling rate (up to 48<BR>kHz), scalable complexity, =
and=20
      good robustness to packet loss. We'd be<BR>willing to continue the =

      development with the IETF. Even if not with<BR>CELT, it's still =
like to be=20
      involved in such a new=20
    =
WG.<BR><BR>Cheers,<BR><BR>&nbsp;Jean-Marc<BR></BLOCKQUOTE><BR>___________=
____________________________________<BR>Audio/Video=20
    Transport Working Group<BR><A href=3D"mailto:avt@ietf.org"=20
    target=3D_blank>avt@ietf.org</A><BR><A=20
    href=3D"https://www.ietf.org/mailman/listinfo/avt"=20
    =
target=3D_blank>https://www.ietf.org/mailman/listinfo/avt</A><BR><BR></BL=
OCKQUOTE><BR>_______________________________________________<BR>Audio/Vid=
eo=20
  Transport Working Group<BR><A href=3D"mailto:avt@ietf.org"=20
  target=3D_blank>avt@ietf.org</A><BR><A=20
  href=3D"https://www.ietf.org/mailman/listinfo/avt"=20
  =
target=3D_blank>https://www.ietf.org/mailman/listinfo/avt</A><BR></DIV></=
DIV></BLOCKQUOTE></DIV><BR></BODY></HTML>

------_=_NextPart_001_01C9E3A8.4D82F4FA--

From gherlein@herlein.com  Tue Jun  2 10:37:47 2009
Return-Path: <gherlein@herlein.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 666D43A6C33 for <avt@core3.amsl.com>; Tue,  2 Jun 2009 10:37:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level: 
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 lruLlfFjoT-f for <avt@core3.amsl.com>; Tue,  2 Jun 2009 10:37:46 -0700 (PDT)
Received: from mail-px0-f187.google.com (mail-px0-f187.google.com [209.85.216.187]) by core3.amsl.com (Postfix) with ESMTP id 1E0DB3A6B0A for <avt@ietf.org>; Tue,  2 Jun 2009 10:37:45 -0700 (PDT)
Received: by pxi17 with SMTP id 17so1592830pxi.29 for <avt@ietf.org>; Tue, 02 Jun 2009 10:37:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.82.6 with SMTP id f6mr2638036wfb.182.1243964265415; Tue,  02 Jun 2009 10:37:45 -0700 (PDT)
In-Reply-To: <00a401c9e388$b25c2350$171469f0$%roni@huawei.com>
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com>
Date: Tue, 2 Jun 2009 10:37:45 -0700
Message-ID: <31d1be720906021037p5fb36135s56ad35885a3d9929@mail.gmail.com>
From: Greg Herlein <gherlein@herlein.com>
To: Roni Even <Even.roni@huawei.com>
Content-Type: multipart/alternative; boundary=001636e90d942743f5046b6100f2
Cc: Slava Borilin <Borilin@spiritdsp.com>, avt@ietf.org, Jason Fischl <jason.fischl@skype.net>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 02 Jun 2009 17:37:47 -0000

--001636e90d942743f5046b6100f2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

The source code has been available since day one.  Can you help me
understand why the copyright of the source code would need to be transferred
to the IETF?

Greg

On Tue, Jun 2, 2009 at 6:47 AM, Roni Even <Even.roni@huawei.com> wrote:

>  Hi,
>
> I am not sure what prevented you from doing it today at the ITU or MPEG,
> why do you see the IETF handling it differently.
>
> I would also like to remind you and Jean-Marc that once you are bringing
> work to a standard body it may require collaboration with other people who
> will have other proposals that will also address the same requirements and
> you may need to invest money in comparative testing by independent listening
> labs.
>
> I also think that you will need to supply the codec in source code and
> provide copy right to the IETF.
>
>
>
> Roni
>
>
>
> *From:* avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] *On Behalf Of *Slava
> Borilin
> *Sent:* Monday, June 01, 2009 11:50 PM
> *To:* jean-marc.valin@octasic.com
> *Cc:* avt@ietf.org; Jason Fischl
> *Subject:* Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio
> Codec WG
>
>
>
> Agree with Jean-Marc.
>
> SPIRIT is interested to contribute as well - having a dozen of proprietary codecs developed, including
>
> one specifically desgined for internet (SPIRIT IP-MR, which is now under WGLC on draft-ietf-avt-rtp-ipmr-04) -
>
> multi-rate, scalable, adaptive, wideband codec.
>
>
>
> We can also continue this work with IETF.
>
>
>
> Moreover, most if not all efforts coming from ITU on codecs unfortunately are NOT really focused on
>
> internet-specific codecs (that's why several companies have had to invent) - as ITU preference is mainly
>
> specific (i.e. cellular) networks at first.
>
>
>
> however, as we see the greant rise of pure "internet-basd communications" (skype, webex/citrix, and many others) -
>
> we all (and users) are suffering from inefficiency in all currently "standard" codecs and ambiguity in the choice of
>
> internet-targeted ones.
>
>
>
> Again, we probably can put together enough number of contributors to the WG to have the expertise.
>
>
>
> regards,
>
> Slava Borilin
>
>
>
> --
>
> John Lazzaro wrote:
>
> A traditional response to this type of request is to note that the IETF
>
> really doesn't have much in the way of expertise in audio codec design.
>
> I don't see many of the regulars who present at the AES codec paper sessions
>
> posting here on AVT (ditto ICASSP paper sessions for voice codecs). It's
>
> a full-time job to keep up-to-date and contribute to that
>
> signal-processing lore.
>
>
>
> Well, there's no reason that the IETF cannot build such an expertise in
> audio codecs. This is actually something in which I'd be interested in
> getting involved and I'm sure others at Xiph.Org would be interested as
> well. We have several people with audio codec expertise from working on
> Vorbis, Speex and (more recently) CELT. It turns out that the CELT codec
> currently under development at Xiph actually meets most of the requirements
> from the original proposal in being a very low delay codec with adaptive
> bit-rate and sampling rate (up to 48 kHz), scalable complexity, and good
> robustness to packet loss. We'd be willing to continue the development with
> the IETF. Even if not with CELT, it's still like to be involved in such a
> new WG.
>
> Cheers,
>
>
>
>    Jean-Marc
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>
>


-- 
Greg Herlein
www.herlein.com

--001636e90d942743f5046b6100f2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The source code has been available since day one.=A0 Can you help me unders=
tand why the copyright of the source code would need to be transferred to t=
he IETF?<br><br>Greg<br><br><div class=3D"gmail_quote">On Tue, Jun 2, 2009 =
at 6:47 AM, Roni Even <span dir=3D"ltr">&lt;<a href=3D"mailto:Even.roni@hua=
wei.com">Even.roni@huawei.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">








<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US">

<div>

<p><span style=3D"font-size: 11pt; color: rgb(31, 73, 125);">Hi,</span></p>

<p><span style=3D"font-size: 11pt; color: rgb(31, 73, 125);">I am not sure =
what prevented you from doing it today at the ITU
or MPEG, why do you see the IETF handling it differently.</span></p>

<p><span style=3D"font-size: 11pt; color: rgb(31, 73, 125);">I would also l=
ike to remind you and Jean-Marc that once you are
bringing work to a standard body it may require collaboration with other pe=
ople
who will have other proposals that will also address the same requirements =
and
you may need to invest money in comparative testing by independent listenin=
g labs.</span></p>

<p><span style=3D"font-size: 11pt; color: rgb(31, 73, 125);">I also think t=
hat you will need to supply the codec in source
code and provide copy right to the IETF. </span></p>

<p><span style=3D"font-size: 11pt; color: rgb(31, 73, 125);">=A0</span></p>

<p><span style=3D"font-size: 11pt; color: rgb(31, 73, 125);">Roni </span></=
p>

<p><span style=3D"font-size: 11pt; color: rgb(31, 73, 125);">=A0</span></p>

<div>

<div style=3D"border-style: solid none none; border-color: rgb(181, 196, 22=
3) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium=
; padding: 3pt 0in 0in;">

<p><b><span style=3D"font-size: 10pt;">From:</span></b><span style=3D"font-=
size: 10pt;">
<a href=3D"mailto:avt-bounces@ietf.org" target=3D"_blank">avt-bounces@ietf.=
org</a> [mailto:<a href=3D"mailto:avt-bounces@ietf.org" target=3D"_blank">a=
vt-bounces@ietf.org</a>] <b>On Behalf Of </b>Slava
Borilin<br>
<b>Sent:</b> Monday, June 01, 2009 11:50 PM<br>
<b>To:</b> <a href=3D"mailto:jean-marc.valin@octasic.com" target=3D"_blank"=
>jean-marc.valin@octasic.com</a><br>
<b>Cc:</b> <a href=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.org</=
a>; Jason Fischl<br>
<b>Subject:</b> Re: [AVT] [dispatch] Proposal to form Internet Wideband Aud=
io
Codec WG</span></p>

</div>

</div><div><div></div><div class=3D"h5">

<p>=A0</p>

<pre>Agree with Jean-Marc.</pre><pre>SPIRIT is interested to contribute as =
well - having a dozen of proprietary codecs developed, including </pre><pre=
>one specifically desgined for internet (SPIRIT IP-MR, which is now under W=
GLC on draft-ietf-avt-rtp-ipmr-04) - </pre>
<pre>multi-rate, scalable, adaptive, wideband codec.</pre><pre>=A0</pre><pr=
e>We can also continue this work with IETF.</pre><pre>=A0</pre><pre>Moreove=
r, most if not all efforts coming from ITU on codecs unfortunately are NOT =
really focused on </pre>
<pre>internet-specific codecs (that&#39;s why several companies have had to=
 invent) - as ITU preference is mainly </pre><pre>specific (i.e. cellular) =
networks at first.</pre><pre>=A0</pre><pre>however, as we see the greant ri=
se of pure &quot;internet-basd communications&quot; (skype, webex/citrix, a=
nd many others) - </pre>
<pre>we all (and users) are suffering from inefficiency in all currently &q=
uot;standard&quot; codecs and ambiguity in the choice of </pre><pre>interne=
t-targeted ones.</pre><pre>=A0</pre><pre>Again, we probably can put togethe=
r enough number of contributors to the WG to have the expertise.</pre>
<pre>=A0</pre><pre>regards,</pre><pre>Slava Borilin</pre><pre>=A0</pre><pre=
>--</pre><pre>John Lazzaro wrote:</pre>

<blockquote style=3D"border-style: none none none solid; border-color: -moz=
-use-text-color -moz-use-text-color -moz-use-text-color rgb(85, 85, 238); b=
order-width: medium medium medium 2.25pt; padding: 0in 0in 0in 10pt; margin=
-left: 0in; margin-right: 0in;">
<pre>A traditional response to this type of request is to note that the IET=
F</pre><pre>really doesn&#39;t have much in the way of expertise in audio c=
odec design.</pre><pre>I don&#39;t see many of the regulars who present at =
the AES codec paper sessions</pre>
<pre>posting here on AVT (ditto ICASSP paper sessions for voice codecs). It=
&#39;s</pre><pre>a full-time job to keep up-to-date and contribute to that<=
/pre><pre>signal-processing lore.</pre><pre>=A0</pre></blockquote>

<p><tt><span style=3D"font-size: 10pt;">Well, there&#39;s no reason
that the IETF cannot build such an expertise in audio codecs. This is actua=
lly
something in which I&#39;d be interested in getting involved and I&#39;m su=
re others at
Xiph.Org would be interested as well. We have several people with audio cod=
ec
expertise from working on Vorbis, Speex and (more recently) CELT. It turns =
out
that the CELT codec currently under development at Xiph actually meets most=
 of
the requirements from the original proposal in being a very low delay codec
with adaptive bit-rate and sampling rate (up to 48 kHz), scalable complexit=
y,
and good robustness to packet loss. We&#39;d be willing to continue the dev=
elopment
with the IETF. Even if not with CELT, it&#39;s still like to be involved in=
 such a
new WG. </span></tt></p>

<pre>Cheers,</pre><pre>=A0</pre><pre>=A0=A0 Jean-Marc</pre></div></div></di=
v>

</div>


<br>_______________________________________________<br>
Audio/Video Transport Working Group<br>
<a href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/avt</a><br>
<br></blockquote></div><br><br clear=3D"all"><br>-- <br>Greg Herlein<br><a =
href=3D"http://www.herlein.com">www.herlein.com</a><br>

--001636e90d942743f5046b6100f2--

From Even.roni@huawei.com  Tue Jun  2 10:52:56 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A10E53A6D01 for <avt@core3.amsl.com>; Tue,  2 Jun 2009 10:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.494
X-Spam-Level: 
X-Spam-Status: No, score=-0.494 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  HTML_MESSAGE=0.001, 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 4wHnzHZtrS5I for <avt@core3.amsl.com>; Tue,  2 Jun 2009 10:52:55 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id E95803A69B8 for <avt@ietf.org>; Tue,  2 Jun 2009 10:52:54 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KKM00C5FHNXKI@szxga02-in.huawei.com> for avt@ietf.org; Wed, 03 Jun 2009 01:52:45 +0800 (CST)
Received: from huawei.com ([172.24.1.3]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KKM00CDKHNXV4@szxga02-in.huawei.com> for avt@ietf.org; Wed, 03 Jun 2009 01:52:45 +0800 (CST)
Received: from windows8d787f9 (bzq-79-183-125-11.red.bezeqint.net [79.183.125.11]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KKM009V5HN2X2@szxml01-in.huawei.com>; Wed, 03 Jun 2009 01:52:45 +0800 (CST)
Date: Tue, 02 Jun 2009 20:51:13 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <31d1be720906021037p5fb36135s56ad35885a3d9929@mail.gmail.com>
To: 'Greg Herlein' <gherlein@herlein.com>
Message-id: <011b01c9e3aa$cc775d50$656617f0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_Jpt4ipwJ/S7NF16BWt3T0w)"
Content-language: en-us
Thread-index: AcnjqNmCp91Pu/8HSQ649fifatTnnQAAYe8A
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <31d1be720906021037p5fb36135s56ad35885a3d9929@mail.gmail.com>
Cc: 'Slava Borilin' <Borilin@spiritdsp.com>, avt@ietf.org, 'Jason Fischl' <jason.fischl@skype.net>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec	WG
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, 02 Jun 2009 17:52:56 -0000

This is a multipart message in MIME format.

--Boundary_(ID_Jpt4ipwJ/S7NF16BWt3T0w)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hi,

This can be discussed later but I would expect that the change control for
the codec will be the IETF and not the contributor, this is the meaning of a
standard track document. 

Like I said the final results will either be a collaboration between all
offered technologies or we will need a selection process.

Roni

 

From: Greg Herlein [mailto:gherlein@herlein.com] 
Sent: Tuesday, June 02, 2009 8:38 PM
To: Roni Even
Cc: Slava Borilin; jean-marc.valin@octasic.com; avt@ietf.org; Jason Fischl
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec
WG

 

The source code has been available since day one.  Can you help me
understand why the copyright of the source code would need to be transferred
to the IETF?

Greg

On Tue, Jun 2, 2009 at 6:47 AM, Roni Even <Even.roni@huawei.com> wrote:

Hi,

I am not sure what prevented you from doing it today at the ITU or MPEG, why
do you see the IETF handling it differently.

I would also like to remind you and Jean-Marc that once you are bringing
work to a standard body it may require collaboration with other people who
will have other proposals that will also address the same requirements and
you may need to invest money in comparative testing by independent listening
labs.

I also think that you will need to supply the codec in source code and
provide copy right to the IETF. 

 

Roni 

 

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Slava
Borilin
Sent: Monday, June 01, 2009 11:50 PM
To: jean-marc.valin@octasic.com
Cc: avt@ietf.org; Jason Fischl
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec
WG

 

Agree with Jean-Marc.
SPIRIT is interested to contribute as well - having a dozen of proprietary
codecs developed, including 
one specifically desgined for internet (SPIRIT IP-MR, which is now under
WGLC on draft-ietf-avt-rtp-ipmr-04) - 
multi-rate, scalable, adaptive, wideband codec.
 
We can also continue this work with IETF.
 
Moreover, most if not all efforts coming from ITU on codecs unfortunately
are NOT really focused on 
internet-specific codecs (that's why several companies have had to invent) -
as ITU preference is mainly 
specific (i.e. cellular) networks at first.
 
however, as we see the greant rise of pure "internet-basd communications"
(skype, webex/citrix, and many others) - 
we all (and users) are suffering from inefficiency in all currently
"standard" codecs and ambiguity in the choice of 
internet-targeted ones.
 
Again, we probably can put together enough number of contributors to the WG
to have the expertise.
 
regards,
Slava Borilin
 
--
John Lazzaro wrote:

A traditional response to this type of request is to note that the IETF
really doesn't have much in the way of expertise in audio codec design.
I don't see many of the regulars who present at the AES codec paper sessions
posting here on AVT (ditto ICASSP paper sessions for voice codecs). It's
a full-time job to keep up-to-date and contribute to that
signal-processing lore.
 

Well, there's no reason that the IETF cannot build such an expertise in
audio codecs. This is actually something in which I'd be interested in
getting involved and I'm sure others at Xiph.Org would be interested as
well. We have several people with audio codec expertise from working on
Vorbis, Speex and (more recently) CELT. It turns out that the CELT codec
currently under development at Xiph actually meets most of the requirements
from the original proposal in being a very low delay codec with adaptive
bit-rate and sampling rate (up to 48 kHz), scalable complexity, and good
robustness to packet loss. We'd be willing to continue the development with
the IETF. Even if not with CELT, it's still like to be involved in such a
new WG. 

Cheers,
 
   Jean-Marc


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




-- 
Greg Herlein
www.herlein.com


--Boundary_(ID_Jpt4ipwJ/S7NF16BWt3T0w)
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:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" 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;}
@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: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;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
tt
	{mso-style-priority:99;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.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 =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>This can be discussed later but I would expect that the =
change
control for the codec will be the IETF and not the contributor, this is =
the meaning
of a standard track document. <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Like I said the final results will either be a =
collaboration
between all offered technologies or we will need a selection =
process.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Roni<o:p></o:p></span></p>

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

<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"'> Greg =
Herlein
[mailto:gherlein@herlein.com] <br>
<b>Sent:</b> Tuesday, June 02, 2009 8:38 PM<br>
<b>To:</b> Roni Even<br>
<b>Cc:</b> Slava Borilin; jean-marc.valin@octasic.com; avt@ietf.org; =
Jason
Fischl<br>
<b>Subject:</b> Re: [AVT] [dispatch] Proposal to form Internet Wideband =
Audio
Codec WG<o:p></o:p></span></p>

</div>

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

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>The source code has =
been
available since day one.&nbsp; Can you help me understand why the =
copyright of
the source code would need to be transferred to the IETF?<br>
<br>
Greg<o:p></o:p></p>

<div>

<p class=3DMsoNormal>On Tue, Jun 2, 2009 at 6:47 AM, Roni Even &lt;<a
href=3D"mailto:Even.roni@huawei.com">Even.roni@huawei.com</a>&gt; =
wrote:<o:p></o:p></p>

<div>

<div>

<p><span =
style=3D'font-size:11.0pt;color:#1F497D'>Hi,</span><o:p></o:p></p>

<p><span style=3D'font-size:11.0pt;color:#1F497D'>I am not sure what =
prevented
you from doing it today at the ITU or MPEG, why do you see the IETF =
handling it
differently.</span><o:p></o:p></p>

<p><span style=3D'font-size:11.0pt;color:#1F497D'>I would also like to =
remind you
and Jean-Marc that once you are bringing work to a standard body it may =
require
collaboration with other people who will have other proposals that will =
also
address the same requirements and you may need to invest money in =
comparative
testing by independent listening labs.</span><o:p></o:p></p>

<p><span style=3D'font-size:11.0pt;color:#1F497D'>I also think that you =
will need
to supply the codec in source code and provide copy right to the IETF. =
</span><o:p></o:p></p>

<p><span =
style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><o:p></o:p></p>

<p><span style=3D'font-size:11.0pt;color:#1F497D'>Roni =
</span><o:p></o:p></p>

<p><span =
style=3D'font-size:11.0pt;color:#1F497D'>&nbsp;</span><o:p></o:p></p>

<div>

<div style=3D'border:none;border-top:solid windowtext =
1.0pt;padding:3.0pt 0in 0in 0in;
border-color:-moz-use-text-color -moz-use-text-color'>

<p><b><span style=3D'font-size:10.0pt'>From:</span></b><span =
style=3D'font-size:
10.0pt'> <a href=3D"mailto:avt-bounces@ietf.org" =
target=3D"_blank">avt-bounces@ietf.org</a>
[mailto:<a href=3D"mailto:avt-bounces@ietf.org" =
target=3D"_blank">avt-bounces@ietf.org</a>]
<b>On Behalf Of </b>Slava Borilin<br>
<b>Sent:</b> Monday, June 01, 2009 11:50 PM<br>
<b>To:</b> <a href=3D"mailto:jean-marc.valin@octasic.com" =
target=3D"_blank">jean-marc.valin@octasic.com</a><br>
<b>Cc:</b> <a href=3D"mailto:avt@ietf.org" =
target=3D"_blank">avt@ietf.org</a>;
Jason Fischl<br>
<b>Subject:</b> Re: [AVT] [dispatch] Proposal to form Internet Wideband =
Audio
Codec WG</span><o:p></o:p></p>

</div>

</div>

<div>

<div>

<p>&nbsp;<o:p></o:p></p>

<pre>Agree with Jean-Marc.<o:p></o:p></pre><pre>SPIRIT is interested to =
contribute as well - having a dozen of proprietary codecs developed, =
including <o:p></o:p></pre><pre>one specifically desgined for internet =
(SPIRIT IP-MR, which is now under WGLC on draft-ietf-avt-rtp-ipmr-04) - =
<o:p></o:p></pre><pre>multi-rate, scalable, adaptive, wideband =
codec.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>We can also =
continue this work with =
IETF.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Moreover, most if =
not all efforts coming from ITU on codecs unfortunately are NOT really =
focused on <o:p></o:p></pre><pre>internet-specific codecs (that's why =
several companies have had to invent) - as ITU preference is mainly =
<o:p></o:p></pre><pre>specific (i.e. cellular) networks at =
first.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>however, as we =
see the greant rise of pure &quot;internet-basd communications&quot; =
(skype, webex/citrix, and many others) - <o:p></o:p></pre><pre>we all =
(and users) are suffering from inefficiency in all currently =
&quot;standard&quot; codecs and ambiguity in the choice of =
<o:p></o:p></pre><pre>internet-targeted =
ones.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Again, we =
probably can put together enough number of contributors to the WG to =
have the =
expertise.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>regards,<o:p>=
</o:p></pre><pre>Slava =
Borilin<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>--<o:p></o:p></p=
re><pre>John Lazzaro wrote:<o:p></o:p></pre>

<blockquote style=3D'border:none;border-left:solid windowtext =
2.25pt;padding:
0in 0in 0in 10.0pt;margin-left:0in;margin-top:5.0pt;margin-right:0in;
margin-bottom:5.0pt;border-color:-moz-use-text-color -moz-use-text-color =
-moz-use-text-color rgb(85, 85, 238)'><pre>A traditional response to =
this type of request is to note that the =
IETF<o:p></o:p></pre><pre>really doesn't have much in the way of =
expertise in audio codec design.<o:p></o:p></pre><pre>I don't see many =
of the regulars who present at the AES codec paper =
sessions<o:p></o:p></pre><pre>posting here on AVT (ditto ICASSP paper =
sessions for voice codecs). It's<o:p></o:p></pre><pre>a full-time job to =
keep up-to-date and contribute to =
that<o:p></o:p></pre><pre>signal-processing =
lore.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre></blockquote>

<p><tt><span style=3D'font-size:10.0pt'>Well, there's no reason that the =
IETF
cannot build such an expertise in audio codecs. This is actually =
something in
which I'd be interested in getting involved and I'm sure others at =
Xiph.Org
would be interested as well. We have several people with audio codec =
expertise
from working on Vorbis, Speex and (more recently) CELT. It turns out =
that the
CELT codec currently under development at Xiph actually meets most of =
the
requirements from the original proposal in being a very low delay codec =
with
adaptive bit-rate and sampling rate (up to 48 kHz), scalable complexity, =
and
good robustness to packet loss. We'd be willing to continue the =
development
with the IETF. Even if not with CELT, it's still like to be involved in =
such a
new WG. </span></tt><o:p></o:p></p>

<pre>Cheers,<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>&nbsp;&nbsp=
; Jean-Marc<o:p></o:p></pre></div>

</div>

</div>

</div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br>
_______________________________________________<br>
Audio/Video Transport Working Group<br>
<a href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/avt</a><o:p></o:p=
></p>

</div>

<p class=3DMsoNormal><br>
<br clear=3Dall>
<br>
-- <br>
Greg Herlein<br>
<a href=3D"http://www.herlein.com">www.herlein.com</a><o:p></o:p></p>

</div>

</body>

</html>

--Boundary_(ID_Jpt4ipwJ/S7NF16BWt3T0w)--

From stephen.botzko@gmail.com  Tue Jun  2 11:13:17 2009
Return-Path: <stephen.botzko@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 A8FDD28C133; Tue,  2 Jun 2009 11:13:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.968
X-Spam-Level: 
X-Spam-Status: No, score=0.968 tagged_above=-999 required=5 tests=[AWL=-1.189,  BAYES_00=-2.599, FRT_ADOBE2=2.455, HTML_MESSAGE=0.001, MANGLED_INXPNS=2.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 LgXl-tmn6var; Tue,  2 Jun 2009 11:13:15 -0700 (PDT)
Received: from mail-bw0-f222.google.com (mail-bw0-f222.google.com [209.85.218.222]) by core3.amsl.com (Postfix) with ESMTP id D3B1328C12A; Tue,  2 Jun 2009 11:13:14 -0700 (PDT)
Received: by bwz22 with SMTP id 22so8347888bwz.37 for <multiple recipients>; Tue, 02 Jun 2009 11:13:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=kAh8a/DuAVpEEz58lf3r3fiqzsCQV7ZU6G+WM7tSUSo=; b=f1kQkkz3hGhUsIAfrV0NmGDUyWElYnBxg48sIn2VYL3A12rukSCDW8qdJXZps2i2/Y ZDjEw5U1s5fLVEpHzsjxmi0ht1eHRx78TqKIiA0lFDZ8FTCQ0tidfvaxtN7Ied7PIRaf YslbuFAQqA/NCgJfEsyk2V53yYZIbgoYAr6BU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=HYcTohrGrtWpjlOuM8P4RMf3s5jIqQ7O+MyJ/eIyBgWFD+9YgzVwhbTrk3oml0/Rtm QuOTFiHoPmptdRc+XicRD7shtTR0lZ1LSceXkNzMR/L5h484tRK3a5XBCSrKC2l+lMw5 o5yGzVWqKbk6A9wCMyF5Uk4KotZ6vaGKQIzMg=
MIME-Version: 1.0
Received: by 10.103.241.15 with SMTP id t15mr4118708mur.85.1243966393155; Tue,  02 Jun 2009 11:13:13 -0700 (PDT)
In-Reply-To: <AA5A65FC22B6F145830AC0EAC7586A6C04BF9091@mail-srv.spiritcorp.com>
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <4A2541B9.2000805@octasic.com> <00d501c9e39a$dcbbbe50$96333af0$%roni@huawei.com> <D1611ACB-4739-4A65-94F0-403FC24CDC43@cs.columbia.edu> <6e9223710906021031i31e024dam5673ca9608017d73@mail.gmail.com> <AA5A65FC22B6F145830AC0EAC7586A6C04BF9091@mail-srv.spiritcorp.com>
Date: Tue, 2 Jun 2009 14:13:13 -0400
Message-ID: <6e9223710906021113w30a16a6cg7347f83c0162ba58@mail.gmail.com>
From: stephen botzko <stephen.botzko@gmail.com>
To: Slava Borilin <Borilin@spiritdsp.com>
Content-Type: multipart/alternative; boundary=001636b430c8fa044c046b617ead
Cc: dispatch@ietf.org, Jason Fischl <jason.fischl@skype.net>, avt@ietf.org, Roni Even <Even.roni@huawei.com>, hsinnrei@adobe.com, Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 02 Jun 2009 18:13:17 -0000

--001636b430c8fa044c046b617ead
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

>>> i think this is probably false alert.
I would hope so.  I think its important that the characterization testing
(however it is done) prevent the standardization of a codec that is
sub-standard.

So I'd prefer Henning's last risk item to be that "a standardizable codec
might not result".

Steve B.

On Tue, Jun 2, 2009 at 1:33 PM, Slava Borilin <Borilin@spiritdsp.com> wrote:

>  I do not beleive the one that will come wil be low quality.
> at least people from the potential contributors (at least Skype, Speex,
> SPIRIT) are already pretty-good in the commercially exploiting their own
> codecs on the market.
> i think this is probably false alert.
>
> regards,
> Slava Borilin
>
>
>
>  ------------------------------
> *From:* stephen botzko [mailto:stephen.botzko@gmail.com]
> *Sent:* Tuesday, June 02, 2009 9:32 PM
> *To:* Henning Schulzrinne
> *Cc:* Roni Even; dispatch@ietf.org; Jason Fischl; avt@ietf.org;
> hsinnrei@adobe.com; Slava Borilin
>
> *Subject:* Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio
> Codec WG
>
> >>> - the quality of the codec may not be competitive
>
> I think its very important that the codec quality be competitive.  People
> expect excellence from IETF standards  Standardizing non-competitive codecs
> because they are cheap does not seem to be a good choce.
>
> Steve B.
>
> On Tue, Jun 2, 2009 at 12:15 PM, Henning Schulzrinne <hgs@cs.columbia.edu>wrote:
>
>> I view this as a trade-off. If we pursue this, there are risks:
>>
>> - nothing may come of it since there are no experts willing to help
>> - somebody will claim IPR on the resulting work
>> - the quality of the codec may not be competitive
>>
>> However, if we don't do this, we are stuck with the status quo, which is
>> not all that satisfactory. Thus, unless there are significant costs for
>> "innocent bystanders", I see this as a risk worth taking. In the worst case,
>> we are no worse off than we are today. In all other cases, we'll have an
>> additional choice for a wideband codec, even if it's not "the best", just
>> "good enough". After all, most people use G.711 today, which has a really
>> hard time making that claim.
>>
>> Most real work in the IETF is done by very small teams, typically less
>> than 10, so as long as we have a handful of people that are willing to
>> contribute, this can work. It might even work better, since you may get
>> fewer people who have half-baked opinions - we may skip the binary vs. XML
>> debates...
>>
>> We can set some ground rules ("must be tested with packet loss of 5%") and
>> then see what happens. Compared to most network protocols, the likely
>> negative impacts (such as security or congestion control issues) of even a
>> badly-designed codec are pretty limited.
>>
>> Henning
>>
>>
>> On Jun 2, 2009, at 11:57 AM, Roni Even wrote:
>>
>> Hi,
>>> I do not want to sound like someone who is for IPR (I am not), but why
>>> stop
>>> at codec, let's require it for all IETF work. There are IPR on IETF work
>>> which is must simpler, in my view, than wide band audio codecs.
>>>
>>> I think that we can start with "royalty free" even though I am not sure
>>> that
>>> it will accepted as part of the charter of any other work group so why
>>> pick
>>> on codecs which require more work.
>>>
>>> This leaves the other reasons I heard for doing it at the IETF which is
>>> the
>>> price of participating (cheaper than being an ITU-T member) and maybe
>>> design
>>> less expensive characterization tests.
>>>
>>> Roni
>>>
>>>
>>> -----Original Message-----
>>> From: Jean-Marc Valin [mailto:jean-marc.valin@octasic.com]
>>> Sent: Tuesday, June 02, 2009 6:14 PM
>>> To: Roni Even
>>> Cc: 'Slava Borilin'; avt@ietf.org; 'Jason Fischl'; dispatch@ietf.org;
>>> hsinnrei@adobe.com
>>> Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio
>>> Codec
>>> WG
>>>
>>> Hi,
>>>
>>> Roni Even wrote:
>>>
>>>>
>>>> I am not sure what prevented you from doing it today at the ITU or
>>>> MPEG, why do you see the IETF handling it differently.
>>>>
>>>> I would also like to remind you and Jean-Marc that once you are
>>>> bringing work to a standard body it may require collaboration with
>>>> other people who will have other proposals that will also address the
>>>> same requirements and you may need to invest money in comparative
>>>> testing by independent listening labs.
>>>>
>>>> I also think that you will need to supply the codec in source code and
>>>> provide copy right to the IETF.
>>>>
>>>>
>>> I am well aware that bringing work to the IETF would require
>>> collaboration with others. I am not seeking control over the work I am
>>> currently doing and would really welcome such collaboration. The idea is
>>> only to have the best wideband codec possible without IPR issues. Given
>>> the ITU and MPEG track record, I think it would be very unlikely for any
>>> of those organisations to work on an IPR-free codec.
>>>
>>> I also agree with Henry that "the Internet has different criteria than
>>> ITU-T networks may have". Internet adoption follows different patterns
>>> than adoption in the ITU primary target markets. For example, the
>>> Internet has more consumer-reconfigurable software, while the ITU has to
>>> deal with a lot of fixed hardware deployments. At the ITU, it makes
>>> sense to invest large sums of money into testing and characterisation of
>>> codecs because the codecs deployed there usually stay around for a long
>>> time and the infrastructure investments are usually very large. On the
>>> other hand, I would say the investments in codecs for the Internet are
>>> comparatively smaller and, while testing is still important, it is not
>>> as critical as it is for the ITU.
>>>
>>> It's also a choice one has to make. It is unlikely that companies would
>>> invest money in expensive testing if they are not going to obtain
>>> royalties in return. However, I think we may be able to define some more
>>> lightweight (collaborative?) testing that is sufficient and doesn't
>>> involve as much investments as what the ITU does. For the Internet, I
>>> believe an IPR-free codec that everyone agrees performs well is better
>>> than a patent-encumbered codec that has had more extensive testing. This
>>> is again another difference with the ITU: patent-encumbered codecs tend
>>> to hurt a lot more on the Internet because many applications (e.g.
>>> giving away the client) are very hard (or impossible) when one has to
>>> pay per-channel royalties.
>>>
>>> As for the source code issue you pointed out, all the Xiph codecs are
>>> already published under a very permissive open source license (BSD), so
>>> this would not really change.
>>>
>>>   Jean-Marc
>>>
>>> Roni
>>>>
>>>>
>>>>
>>>> *From:* avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] *On Behalf
>>>> Of *Slava Borilin
>>>> *Sent:* Monday, June 01, 2009 11:50 PM
>>>> *To:* jean-marc.valin@octasic.com
>>>> *Cc:* avt@ietf.org; Jason Fischl
>>>> *Subject:* Re: [AVT] [dispatch] Proposal to form Internet Wideband
>>>> Audio Codec WG
>>>>
>>>>
>>>>
>>>> Agree with Jean-Marc.
>>>> SPIRIT is interested to contribute as well - having a dozen of
>>>> proprietary
>>>>
>>> codecs developed, including
>>>
>>>> one specifically desgined for internet (SPIRIT IP-MR, which is now under
>>>>
>>> WGLC on draft-ietf-avt-rtp-ipmr-04) -
>>>
>>>> multi-rate, scalable, adaptive, wideband codec.
>>>>
>>>> We can also continue this work with IETF.
>>>>
>>>> Moreover, most if not all efforts coming from ITU on codecs
>>>> unfortunately
>>>>
>>> are NOT really focused on
>>>
>>>> internet-specific codecs (that's why several companies have had to
>>>> invent)
>>>>
>>> - as ITU preference is mainly
>>>
>>>> specific (i.e. cellular) networks at first.
>>>>
>>>> however, as we see the greant rise of pure "internet-basd
>>>> communications"
>>>>
>>> (skype, webex/citrix, and many others) -
>>>
>>>> we all (and users) are suffering from inefficiency in all currently
>>>>
>>> "standard" codecs and ambiguity in the choice of
>>>
>>>> internet-targeted ones.
>>>>
>>>> Again, we probably can put together enough number of contributors to the
>>>>
>>> WG to have the expertise.
>>>
>>>>
>>>> regards,
>>>> Slava Borilin
>>>>
>>>> --
>>>> John Lazzaro wrote:
>>>>
>>>>   A traditional response to this type of request is to note that the
>>>>
>>> IETF
>>>
>>>>
>>>>   really doesn't have much in the way of expertise in audio codec
>>>>
>>> design.
>>>
>>>>
>>>>   I don't see many of the regulars who present at the AES codec paper
>>>>
>>> sessions
>>>
>>>>
>>>>   posting here on AVT (ditto ICASSP paper sessions for voice codecs).
>>>>
>>> It's
>>>
>>>>
>>>>   a full-time job to keep up-to-date and contribute to that
>>>>
>>>>   signal-processing lore.
>>>>
>>>>
>>>>
>>>> Well, there's no reason that the IETF cannot build such an expertise
>>>> in audio codecs. This is actually something in which I'd be interested
>>>> in getting involved and I'm sure others at Xiph.Org would be
>>>> interested as well. We have several people with audio codec expertise
>>>> from working on Vorbis, Speex and (more recently) CELT. It turns out
>>>> that the CELT codec currently under development at Xiph actually meets
>>>> most of the requirements from the original proposal in being a very
>>>> low delay codec with adaptive bit-rate and sampling rate (up to 48
>>>> kHz), scalable complexity, and good robustness to packet loss. We'd be
>>>> willing to continue the development with the IETF. Even if not with
>>>> CELT, it's still like to be involved in such a new WG.
>>>>
>>>> Cheers,
>>>>
>>>>  Jean-Marc
>>>>
>>>
>>> _______________________________________________
>>> Audio/Video Transport Working Group
>>> avt@ietf.org
>>> https://www.ietf.org/mailman/listinfo/avt
>>>
>>>
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>>
>
>

--001636b430c8fa044c046b617ead
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

&gt;&gt;&gt; <span><font size=3D"2" color=3D"#0000ff" face=3D"Arial">i thin=
k this is probably false alert.<br>I
would hope so.=A0 I think its important that the characterization testing
(however it is done) prevent the standardization of a codec that is
sub-standard.=A0 <br>
<br>So I&#39;d prefer Henning&#39;s last risk item to be that &quot;a stand=
ardizable codec might not result&quot;.<br><br>Steve B.<br></font></span><b=
r><div class=3D"gmail_quote">On Tue, Jun 2, 2009 at 1:33 PM, Slava Borilin =
<span dir=3D"ltr">&lt;<a href=3D"mailto:Borilin@spiritdsp.com">Borilin@spir=
itdsp.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">



<div>
<div dir=3D"ltr" align=3D"left"><span><font size=3D"2" color=3D"#0000ff" fa=
ce=3D"Arial">I do not beleive the one that will come wil be low=20
quality.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font size=3D"2" color=3D"#0000ff" fa=
ce=3D"Arial">at least people from the potential contributors (at least=20
Skype, Speex, SPIRIT) are already pretty-good in the commercially exploitin=
g=20
their own codecs on the market.</font></span></div>
<div dir=3D"ltr" align=3D"left"><span><font size=3D"2" color=3D"#0000ff" fa=
ce=3D"Arial">i think this is probably false alert.</font></span></div>
<div><font size=3D"2" color=3D"#0000ff" face=3D"Arial"></font>=A0</div>
<div align=3D"left"><font size=3D"2" face=3D"Arial">regards,</font></div>
<div align=3D"left"><font size=3D"2" face=3D"Arial">Slava Borilin</font></d=
iv>
<div align=3D"left"><span style=3D"font-size: 10pt; font-family: Arial;" la=
ng=3D"EN-US"></span>=A0</div>
<div>=A0</div><br>
<div dir=3D"ltr" align=3D"left" lang=3D"en-us">
<hr>
<font size=3D"2" face=3D"Tahoma"><b>From:</b> stephen botzko=20
[mailto:<a href=3D"mailto:stephen.botzko@gmail.com" target=3D"_blank">steph=
en.botzko@gmail.com</a>] <br><b>Sent:</b> Tuesday, June 02, 2009 9:32=20
PM<br><b>To:</b> Henning Schulzrinne<br><b>Cc:</b> Roni Even; <a href=3D"ma=
ilto:dispatch@ietf.org" target=3D"_blank">dispatch@ietf.org</a>;=20
Jason Fischl; <a href=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.or=
g</a>; <a href=3D"mailto:hsinnrei@adobe.com" target=3D"_blank">hsinnrei@ado=
be.com</a>; Slava Borilin<div><div></div><div class=3D"h5"><br><b>Subject:<=
/b>=20
Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec=20
WG<br></div></div></font><br></div><div><div></div><div class=3D"h5">
<div></div>&gt;&gt;&gt; - the quality of the codec may not be=20
competitive<br><br>I think its very important that the codec quality be=20
competitive.=A0 People expect excellence from IETF standards=A0=20
Standardizing non-competitive codecs because they are cheap does not seem t=
o be=20
a good choce.<br><br>Steve B.<br><br>
<div class=3D"gmail_quote">On Tue, Jun 2, 2009 at 12:15 PM, Henning Schulzr=
inne=20
<span dir=3D"ltr">&lt;<a href=3D"mailto:hgs@cs.columbia.edu" target=3D"_bla=
nk">hgs@cs.columbia.edu</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I=20
  view this as a trade-off. If we pursue this, there are risks:<br><br>- no=
thing=20
  may come of it since there are no experts willing to help<br>- somebody w=
ill=20
  claim IPR on the resulting work<br>- the quality of the codec may not be=
=20
  competitive<br><br>However, if we don&#39;t do this, we are stuck with th=
e status=20
  quo, which is not all that satisfactory. Thus, unless there are significa=
nt=20
  costs for &quot;innocent bystanders&quot;, I see this as a risk worth tak=
ing. In the=20
  worst case, we are no worse off than we are today. In all other cases, we=
&#39;ll=20
  have an additional choice for a wideband codec, even if it&#39;s not &quo=
t;the best&quot;,=20
  just &quot;good enough&quot;. After all, most people use G.711 today, whi=
ch has a really=20
  hard time making that claim.<br><br>Most real work in the IETF is done by=
 very=20
  small teams, typically less than 10, so as long as we have a handful of p=
eople=20
  that are willing to contribute, this can work. It might even work better,=
=20
  since you may get fewer people who have half-baked opinions - we may skip=
 the=20
  binary vs. XML debates...<br><br>We can set some ground rules (&quot;must=
 be tested=20
  with packet loss of 5%&quot;) and then see what happens. Compared to most=
 network=20
  protocols, the likely negative impacts (such as security or congestion co=
ntrol=20
  issues) of even a badly-designed codec are pretty limited.<br><font color=
=3D"#888888"><br>Henning</font>
  <div>
  <div></div>
  <div><br><br>On Jun 2, 2009, at 11:57 AM, Roni Even wrote:<br><br>
  <blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204=
, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>I=20
    do not want to sound like someone who is for IPR (I am not), but why=20
    stop<br>at codec, let&#39;s require it for all IETF work. There are IPR=
 on IETF=20
    work<br>which is must simpler, in my view, than wide band audio=20
    codecs.<br><br>I think that we can start with &quot;royalty free&quot; =
even though I=20
    am not sure that<br>it will accepted as part of the charter of any othe=
r=20
    work group so why pick<br>on codecs which require more work.<br><br>Thi=
s=20
    leaves the other reasons I heard for doing it at the IETF which is=20
    the<br>price of participating (cheaper than being an ITU-T member) and =
maybe=20
    design<br>less expensive characterization=20
    tests.<br><br>Roni<br><br><br>-----Original Message-----<br>From: Jean-=
Marc=20
    Valin [mailto:<a href=3D"mailto:jean-marc.valin@octasic.com" target=3D"=
_blank">jean-marc.valin@octasic.com</a>]<br>Sent: Tuesday, June 02,=20
    2009 6:14 PM<br>To: Roni Even<br>Cc: &#39;Slava Borilin&#39;; <a href=
=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.org</a>; &#39;Jason Fis=
chl&#39;;=20
    <a href=3D"mailto:dispatch@ietf.org" target=3D"_blank">dispatch@ietf.or=
g</a>;<br><a href=3D"mailto:hsinnrei@adobe.com" target=3D"_blank">hsinnrei@=
adobe.com</a><br>Subject: Re: [AVT] [dispatch]=20
    Proposal to form Internet Wideband Audio Codec<br>WG<br><br>Hi,<br><br>=
Roni=20
    Even wrote:<br>
    <blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(2=
04, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>I=20
      am not sure what prevented you from doing it today at the ITU or<br>M=
PEG,=20
      why do you see the IETF handling it differently.<br><br>I would also =
like=20
      to remind you and Jean-Marc that once you are<br>bringing work to a=
=20
      standard body it may require collaboration with<br>other people who w=
ill=20
      have other proposals that will also address the<br>same requirements =
and=20
      you may need to invest money in comparative<br>testing by independent=
=20
      listening labs.<br><br>I also think that you will need to supply the =
codec=20
      in source code and<br>provide copy right to the=20
    IETF.<br><br></blockquote><br>I am well aware that bringing work to the=
 IETF=20
    would require<br>collaboration with others. I am not seeking control ov=
er=20
    the work I am<br>currently doing and would really welcome such=20
    collaboration. The idea is<br>only to have the best wideband codec poss=
ible=20
    without IPR issues. Given<br>the ITU and MPEG track record, I think it =
would=20
    be very unlikely for any<br>of those organisations to work on an IPR-fr=
ee=20
    codec.<br><br>I also agree with Henry that &quot;the Internet has diffe=
rent=20
    criteria than<br>ITU-T networks may have&quot;. Internet adoption follo=
ws=20
    different patterns<br>than adoption in the ITU primary target markets. =
For=20
    example, the<br>Internet has more consumer-reconfigurable software, whi=
le=20
    the ITU has to<br>deal with a lot of fixed hardware deployments. At the=
 ITU,=20
    it makes<br>sense to invest large sums of money into testing and=20
    characterisation of<br>codecs because the codecs deployed there usually=
 stay=20
    around for a long<br>time and the infrastructure investments are usuall=
y=20
    very large. On the<br>other hand, I would say the investments in codecs=
 for=20
    the Internet are<br>comparatively smaller and, while testing is still=
=20
    important, it is not<br>as critical as it is for the ITU.<br><br>It&#39=
;s also a=20
    choice one has to make. It is unlikely that companies would<br>invest m=
oney=20
    in expensive testing if they are not going to obtain<br>royalties in re=
turn.=20
    However, I think we may be able to define some more<br>lightweight=20
    (collaborative?) testing that is sufficient and doesn&#39;t<br>involve =
as much=20
    investments as what the ITU does. For the Internet, I<br>believe an IPR=
-free=20
    codec that everyone agrees performs well is better<br>than a=20
    patent-encumbered codec that has had more extensive testing. This<br>is=
=20
    again another difference with the ITU: patent-encumbered codecs tend<br=
>to=20
    hurt a lot more on the Internet because many applications (e.g.<br>givi=
ng=20
    away the client) are very hard (or impossible) when one has to<br>pay=
=20
    per-channel royalties.<br><br>As for the source code issue you pointed =
out,=20
    all the Xiph codecs are<br>already published under a very permissive op=
en=20
    source license (BSD), so<br>this would not really change.<br><br>=A0=20
    Jean-Marc<br><br>
    <blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(2=
04, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Roni<br><br><=
br><br>*From:*=20
      <a href=3D"mailto:avt-bounces@ietf.org" target=3D"_blank">avt-bounces=
@ietf.org</a> [mailto:<a href=3D"mailto:avt-bounces@ietf.org" target=3D"_bl=
ank">avt-bounces@ietf.org</a>]=20
      *On Behalf<br>Of *Slava Borilin<br>*Sent:* Monday, June 01, 2009 11:5=
0=20
      PM<br>*To:* <a href=3D"mailto:jean-marc.valin@octasic.com" target=3D"=
_blank">jean-marc.valin@octasic.com</a><br>*Cc:* <a href=3D"mailto:avt@ietf=
.org" target=3D"_blank">avt@ietf.org</a>; Jason=20
      Fischl<br>*Subject:* Re: [AVT] [dispatch] Proposal to form Internet=
=20
      Wideband<br>Audio Codec WG<br><br><br><br>Agree with Jean-Marc.<br>SP=
IRIT=20
      is interested to contribute as well - having a dozen of=20
    proprietary<br></blockquote>codecs developed, including<br>
    <blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(2=
04, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">one=20
      specifically desgined for internet (SPIRIT IP-MR, which is now=20
    under<br></blockquote>WGLC on draft-ietf-avt-rtp-ipmr-04) -<br>
    <blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(2=
04, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">multi-rate,=
=20
      scalable, adaptive, wideband codec.<br><br>We can also continue this =
work=20
      with IETF.<br><br>Moreover, most if not all efforts coming from ITU o=
n=20
      codecs unfortunately<br></blockquote>are NOT really focused on<br>
    <blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(2=
04, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">internet-spec=
ific=20
      codecs (that&#39;s why several companies have had to invent)<br></blo=
ckquote>-=20
    as ITU preference is mainly<br>
    <blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(2=
04, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">specific=20
      (i.e. cellular) networks at first.<br><br>however, as we see the grea=
nt=20
      rise of pure &quot;internet-basd communications&quot;<br></blockquote=
>(skype,=20
    webex/citrix, and many others) -<br>
    <blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(2=
04, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">we=20
      all (and users) are suffering from inefficiency in all=20
    currently<br></blockquote>&quot;standard&quot; codecs and ambiguity in =
the choice=20
    of<br>
    <blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(2=
04, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">internet-targ=
eted=20
      ones.<br><br>Again, we probably can put together enough number of=20
      contributors to the<br></blockquote>WG to have the expertise.<br>
    <blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(2=
04, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>regards,<=
br>Slava=20
      Borilin<br><br>--<br>John Lazzaro wrote:<br><br>=A0 A traditional=20
      response to this type of request is to note that=20
the<br></blockquote>IETF<br>
    <blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(2=
04, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>=A0=20
      really doesn&#39;t have much in the way of expertise in audio=20
    codec<br></blockquote>design.<br>
    <blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(2=
04, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>=A0=20
      I don&#39;t see many of the regulars who present at the AES codec=20
    paper<br></blockquote>sessions<br>
    <blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(2=
04, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>=A0=20
      posting here on AVT (ditto ICASSP paper sessions for voice=20
    codecs).<br></blockquote>It&#39;s<br>
    <blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(2=
04, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>=A0=20
      a full-time job to keep up-to-date and contribute to that<br><br>=A0=
=20
      signal-processing lore.<br><br><br><br>Well, there&#39;s no reason th=
at the=20
      IETF cannot build such an expertise<br>in audio codecs. This is actua=
lly=20
      something in which I&#39;d be interested<br>in getting involved and I=
&#39;m sure=20
      others at Xiph.Org would be<br>interested as well. We have several pe=
ople=20
      with audio codec expertise<br>from working on Vorbis, Speex and (more=
=20
      recently) CELT. It turns out<br>that the CELT codec currently under=
=20
      development at Xiph actually meets<br>most of the requirements from t=
he=20
      original proposal in being a very<br>low delay codec with adaptive=20
      bit-rate and sampling rate (up to 48<br>kHz), scalable complexity, an=
d=20
      good robustness to packet loss. We&#39;d be<br>willing to continue th=
e=20
      development with the IETF. Even if not with<br>CELT, it&#39;s still l=
ike to be=20
      involved in such a new=20
    WG.<br><br>Cheers,<br><br>=A0Jean-Marc<br></blockquote><br>____________=
___________________________________<br>Audio/Video=20
    Transport Working Group<br><a href=3D"mailto:avt@ietf.org" target=3D"_b=
lank">avt@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/=
avt" target=3D"_blank">https://www.ietf.org/mailman/listinfo/avt</a><br><br=
></blockquote>
<br>_______________________________________________<br>Audio/Video=20
  Transport Working Group<br><a href=3D"mailto:avt@ietf.org" target=3D"_bla=
nk">avt@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/av=
t" target=3D"_blank">https://www.ietf.org/mailman/listinfo/avt</a><br></div=
></div>
</blockquote></div><br></div></div></div>
</blockquote></div><br>

--001636b430c8fa044c046b617ead--

From hgs@cs.columbia.edu  Tue Jun  2 11:14:19 2009
Return-Path: <hgs@cs.columbia.edu>
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 9EA7628C24B; Tue,  2 Jun 2009 11:14:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level: 
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5 tests=[AWL=2.377,  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 bnVWJztc8x6U; Tue,  2 Jun 2009 11:14:19 -0700 (PDT)
Received: from serrano.cc.columbia.edu (serrano.cc.columbia.edu [128.59.29.6]) by core3.amsl.com (Postfix) with ESMTP id B69C528C217; Tue,  2 Jun 2009 11:13:49 -0700 (PDT)
Received: from ice.cs.columbia.edu (ice.cs.columbia.edu [128.59.18.177]) (user=hgs10 mech=PLAIN bits=0) by serrano.cc.columbia.edu (8.14.3/8.14.3) with ESMTP id n52ICIqj002364 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 2 Jun 2009 14:12:19 -0400 (EDT)
Message-Id: <2B4B0335-916C-4CD4-9E40-63BBA6B1DF8B@cs.columbia.edu>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
To: stephen botzko <stephen.botzko@gmail.com>
In-Reply-To: <6e9223710906021031i31e024dam5673ca9608017d73@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 2 Jun 2009 14:12:18 -0400
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <4A2541B9.2000805@octasic.com> <00d501c9e39a$dcbbbe50$96333af0$%roni@huawei.com> <D1611ACB-4739-4A65-94F0-403FC24CDC43@cs.columbia.edu> <6e9223710906021031i31e024dam5673ca9608017d73@mail.gmail.com>
X-Mailer: Apple Mail (2.935.3)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.65 on 128.59.29.6
Cc: dispatch@ietf.org, Jason Fischl <jason.fischl@skype.net>, avt@ietf.org, Roni Even <Even.roni@huawei.com>, hsinnrei@adobe.com, Slava Borilin <Borilin@spiritdsp.com>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 02 Jun 2009 18:14:19 -0000

On Jun 2, 2009, at 1:31 PM, stephen botzko wrote:

> >>> - the quality of the codec may not be competitive
>
> I think its very important that the codec quality be competitive.   
> People expect excellence from IETF standards  Standardizing non- 
> competitive codecs because they are cheap does not seem to be a good  
> choce.

This is an engineering trade-off. Ogg Vorbis is probably not the  
"best" codec out there, but fills a need.

From versteb@cisco.com  Tue Jun  2 11:14:20 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 903A228C12D for <avt@core3.amsl.com>; Tue,  2 Jun 2009 11:14:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.949
X-Spam-Level: 
X-Spam-Status: No, score=-6.949 tagged_above=-999 required=5 tests=[AWL=-0.350, 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 clfg2fGI1SeD for <avt@core3.amsl.com>; Tue,  2 Jun 2009 11:14:19 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 2B47028C274 for <avt@ietf.org>; Tue,  2 Jun 2009 11:14:10 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.41,292,1241395200"; d="scan'208";a="315329203"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by sj-iport-6.cisco.com with ESMTP; 02 Jun 2009 18:14:06 +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 n52IE6cf024565;  Tue, 2 Jun 2009 14:14:06 -0400
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 n52IE6rm025915; Tue, 2 Jun 2009 18:14:06 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);  Tue, 2 Jun 2009 14:14:06 -0400
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, 2 Jun 2009 14:14:05 -0400
Message-ID: <81B9B88E2F9D574AA5328A85547CDE91014FFAE5@xmb-rtp-21d.amer.cisco.com>
In-Reply-To: <011701c9e2c3$6a75b990$3f612cb0$%roni@huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Calling for comments on changes to RAMS draft 00
Thread-Index: AcnS4FBFJRh0kTNdSKKujynDJmWrDwAJMQ/AAC+GL9AAAGUFAAAXW2jQAA+eDnAASHsCkALEQgYwAIvU5CAAOrRN4A==
References: <fa05fd7ad709f.d709ffa05fd7a@huawei.com> <81B9B88E2F9D574AA5328A85547CDE91013038E4@xmb-rtp-21d.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE9101303DA5@xmb-rtp-21d.amer.cisco.com> <00dc01c9d3c5$7a323aa0$6e96afe0$%roni@huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D54094C3DBF@xmb-sjc-215.amer.cisco.com> <000a01c9d461$813bdcb0$83b39610$%roni@huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D540954DB8A@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE9101495636@xmb-rtp-21d.amer.cisco.com> <011701c9e2c3$6a75b990$3f612cb0$%roni@huawei.com>
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "Roni Even" <Even.roni@huawei.com>, <avt@ietf.org>
X-OriginalArrivalTime: 02 Jun 2009 18:14:06.0103 (UTC) FILETIME=[EA91A270:01C9E3AD]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1535; t=1243966446; x=1244830446; 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=20Calling=20for=20comments=20on=20changes =20to=20RAMS=20draft=2000 |Sender:=20 |To:=20=22Roni=20Even=22=20<Even.roni@huawei.com>,=20<avt@i etf.org>; bh=DlTF/j1PWRUqjXsUn5bTITBVXkdnc+c+Op1MAiOkCnQ=; b=ZRWDzTNrwbM4S2O7EiO2dFeGunoHoR9hGWzJKhtusCex4ob07Cd4oigf8y Z6Pf2ixP2PZpb6rqS4sFt+rGSO1sBC3HOWjrmefsevMxUizFoqHLN/B3zaua qQEU1ewSiB;
Authentication-Results: rtp-dkim-2; header.From=versteb@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); 
Subject: Re: [AVT] Calling for comments on changes to RAMS draft 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/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, 02 Jun 2009 18:14:20 -0000

Roni-

Yes, we plan to add all of the comments from the diff. I will be sure to
update the "subject line" when we do.

Bvs
=20

-----Original Message-----
From: Roni Even [mailto:Even.roni@huawei.com]=20
Sent: Monday, June 01, 2009 10:15 AM
To: Bill Ver Steeg (versteb); avt@ietf.org
Subject: Calling for comments on changes to RAMS draft 00

Bill,
Are you going to add all the comments from the rdiff.

Also please send this email not under the above subject since it does
not describe the purpose of the email

Roni

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Bill Ver Steeg (versteb)
Sent: Friday, May 29, 2009 10:40 PM
To: avt@ietf.org
Subject: Re: [AVT] Adopting Rapid Acquisition of Multicast RTP
Sessions(RAMS) as a working group item

Fellow AVT folks-

We are continuing to solicit comments on the RAMS design points
identified in Ali's email from May 15 (diff enclosed). We have received
some valuable feedback. We hope to have a new draft mid next week, and
will incorporate comments that we receive through Monday or Tuesday in
that draft.

Thanks in advance



Bill VerSteeg

-----Original Message-----
From: Ali C. Begen (abegen)
Sent: Friday, May 15, 2009 1:32 PM
To: Roni Even; Bill Ver Steeg (versteb); avt@ietf.org
Subject: RE: [AVT] Adopting Rapid Acquisition of Multicast RTP
Sessions(RAMS) as a working group item

Hi Roni, All,

Here is a diff for sections 7 and 13.=20

Comments are welcome.
-acbegen


From singer@apple.com  Tue Jun  2 11:32:11 2009
Return-Path: <singer@apple.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 CC9B328C18C for <avt@core3.amsl.com>; Tue,  2 Jun 2009 11:32:11 -0700 (PDT)
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 gdZPj6M7qmzx for <avt@core3.amsl.com>; Tue,  2 Jun 2009 11:32:11 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id 322ED28C161 for <avt@ietf.org>; Tue,  2 Jun 2009 11:32:11 -0700 (PDT)
Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out4.apple.com (Postfix) with ESMTP id 66DD765EF7AE; Tue,  2 Jun 2009 11:32:12 -0700 (PDT)
Received: from relay14.apple.com (unknown [127.0.0.1]) by relay14.apple.com (Symantec Brightmail Gateway) with ESMTP id 5326128083; Tue,  2 Jun 2009 11:32:12 -0700 (PDT)
X-AuditID: 11807134-abc8abb0000021f3-58-4a25702bde50
Received: from [10.0.1.8] (singda.apple.com [17.202.35.52]) by relay14.apple.com (Apple SCV relay) with ESMTP id ED1792802B; Tue,  2 Jun 2009 11:32:11 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p062408a4c64b2024e818@[10.0.1.8]>
In-Reply-To: <ybu7hzu7kf2.fsf@jesup.eng.wgate.com>
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <ybu7hzu7kf2.fsf@jesup.eng.wgate.com>
Date: Tue, 2 Jun 2009 11:32:06 -0700
To: Randell Jesup <rjesup@wgate.com>, Roni Even <Even.roni@huawei.com>
From: David Singer <singer@apple.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
Cc: 'Slava Borilin' <Borilin@spiritdsp.com>, avt@ietf.org, 'Jason Fischl' <jason.fischl@skype.net>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec	WG
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, 02 Jun 2009 18:32:11 -0000

At 10:57  -0400 2/06/09, Randell Jesup wrote:
>Roni Even <Even.roni@huawei.com> writes:
>>I am not sure what prevented you from doing it today at the ITU or MPEG, why
>>do you see the IETF handling it differently.
>
>Last I knew, ITU was a *far* more closed group (and I think MPEG as well).

Attending and contributing to MPEG meetings merely means becoming an 
accredited member of your national delegation.  In the US, you join 
the INCITS L3.1 activity, and meet the rules for attendance and 
voting.  It's not hard (much, much, easier than designing an audio 
codec, or even steering it through a standards process).  It's also 
vastly cheaper than the costs of travel, attendance etc.


-- 
David Singer
Multimedia Standards, Apple Inc.

From stephen.botzko@gmail.com  Tue Jun  2 11:32:27 2009
Return-Path: <stephen.botzko@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 0A51C28C244; Tue,  2 Jun 2009 11:32:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.013
X-Spam-Level: 
X-Spam-Status: No, score=-1.013 tagged_above=-999 required=5 tests=[AWL=1.585,  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 JCnw-FOFW+fr; Tue,  2 Jun 2009 11:32:26 -0700 (PDT)
Received: from mail-fx0-f216.google.com (mail-fx0-f216.google.com [209.85.220.216]) by core3.amsl.com (Postfix) with ESMTP id 95C7428C1FF; Tue,  2 Jun 2009 11:32:25 -0700 (PDT)
Received: by fxm12 with SMTP id 12so6722635fxm.37 for <multiple recipients>; Tue, 02 Jun 2009 11:32:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=QnFAfUB+X/eRw6Ucnc7oCRFiXFCUvjl/ccmz654dBQQ=; b=pkgsx941sSrPozCkc79AE/rIhdikwaALrV4Rt4kl8lbgf8qRFMKJJWmf+oBITb7cHJ 1sK+w8/aCGCl8Fhz8NQJCcXlG1LZ9x59qa+s7q2fRYdY9zjpj7ura2TkKF6htndjVvIl QVheE97jcpLPBYncUOn1dhYMJu/1biM2swgbc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=k7M7NnNFz3OwV3JmDKIJvmyJ8tnL4mDgyGbEAWwwnpUv2WNwFsJMKjaK1T+9L5D7et KMacVl5sqX0LfoWbQyte6RBEDtSggXdertCska0kqxaw/aeXVKa+j9FlEe5b/pFaBULn LShesdIKoR+Ye8zY64qGFs2+VjcBGPpOH66QY=
MIME-Version: 1.0
Received: by 10.102.228.19 with SMTP id a19mr30502muh.10.1243967542188; Tue,  02 Jun 2009 11:32:22 -0700 (PDT)
In-Reply-To: <2B4B0335-916C-4CD4-9E40-63BBA6B1DF8B@cs.columbia.edu>
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <4A2541B9.2000805@octasic.com> <00d501c9e39a$dcbbbe50$96333af0$%roni@huawei.com> <D1611ACB-4739-4A65-94F0-403FC24CDC43@cs.columbia.edu> <6e9223710906021031i31e024dam5673ca9608017d73@mail.gmail.com> <2B4B0335-916C-4CD4-9E40-63BBA6B1DF8B@cs.columbia.edu>
Date: Tue, 2 Jun 2009 14:32:21 -0400
Message-ID: <6e9223710906021132wa2d5c5cg4b095fd3e936e575@mail.gmail.com>
From: stephen botzko <stephen.botzko@gmail.com>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Content-Type: multipart/alternative; boundary=0016363ba72076dbd1046b61c3d5
Cc: dispatch@ietf.org, Jason Fischl <jason.fischl@skype.net>, avt@ietf.org, Roni Even <Even.roni@huawei.com>, hsinnrei@adobe.com, Slava Borilin <Borilin@spiritdsp.com>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 02 Jun 2009 18:32:27 -0000

--0016363ba72076dbd1046b61c3d5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Of course there are multiple dimensions in the engineering - including
complexity, delay, bitrate, audio bandwidth, and fidelity.

I'm not saying there is a "best" codec, let alone that the IETF should
attempt to build it.

But I think any codec standardized by IETF should be competitive, and
hopefully would have some advantage (not just price) over other available
codecs for its stated application(s).

Steve B.

On Tue, Jun 2, 2009 at 2:12 PM, Henning Schulzrinne <hgs@cs.columbia.edu>wrote:

>
> On Jun 2, 2009, at 1:31 PM, stephen botzko wrote:
>
>  >>> - the quality of the codec may not be competitive
>>
>> I think its very important that the codec quality be competitive.  People
>> expect excellence from IETF standards  Standardizing non-competitive codecs
>> because they are cheap does not seem to be a good choce.
>>
>
> This is an engineering trade-off. Ogg Vorbis is probably not the "best"
> codec out there, but fills a need.
>

--0016363ba72076dbd1046b61c3d5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Of course there are multiple dimensions in the engineering - including comp=
lexity, delay, bitrate, audio bandwidth, and fidelity. <br><br>I&#39;m not =
saying there is a &quot;best&quot; codec, let alone that the IETF should at=
tempt to build it.=A0 <br>
<br>But I think any codec standardized by IETF should be competitive, and h=
opefully would have some advantage (not just price) over other available co=
decs for its stated application(s).<br><br>Steve B.<br><br><div class=3D"gm=
ail_quote">
On Tue, Jun 2, 2009 at 2:12 PM, Henning Schulzrinne <span dir=3D"ltr">&lt;<=
a href=3D"mailto:hgs@cs.columbia.edu">hgs@cs.columbia.edu</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid r=
gb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class=3D"im"><br>
On Jun 2, 2009, at 1:31 PM, stephen botzko wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
&gt;&gt;&gt; - the quality of the codec may not be competitive<br>
<br>
I think its very important that the codec quality be competitive. =A0People=
 expect excellence from IETF standards =A0Standardizing non-competitive cod=
ecs because they are cheap does not seem to be a good choce.<br>
</blockquote>
<br></div>
This is an engineering trade-off. Ogg Vorbis is probably not the &quot;best=
&quot; codec out there, but fills a need.<br>
</blockquote></div><br>

--0016363ba72076dbd1046b61c3d5--

From singer@apple.com  Tue Jun  2 11:38:13 2009
Return-Path: <singer@apple.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 3753328C180; Tue,  2 Jun 2009 11:38:13 -0700 (PDT)
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 EG8TRJnI8Lg1; Tue,  2 Jun 2009 11:38:12 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id 8A3173A7047; Tue,  2 Jun 2009 11:38:12 -0700 (PDT)
Received: from relay15.apple.com (relay15.apple.com [17.128.113.54]) by mail-out4.apple.com (Postfix) with ESMTP id C8AAA65EFABC; Tue,  2 Jun 2009 11:38:13 -0700 (PDT)
Received: from relay15.apple.com (unknown [127.0.0.1]) by relay15.apple.com (Symantec Brightmail Gateway) with ESMTP id BC28D5A0002; Tue,  2 Jun 2009 11:38:13 -0700 (PDT)
X-AuditID: 11807136-a5cfbbb00000447e-f4-4a257195030a
Received: from [10.0.1.8] (singda.apple.com [17.202.35.52]) by relay15.apple.com (Apple SCV relay) with ESMTP id 7E89F558003; Tue,  2 Jun 2009 11:38:13 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p062408a5c64b21091de5@[10.0.1.8]>
In-Reply-To: <2B4B0335-916C-4CD4-9E40-63BBA6B1DF8B@cs.columbia.edu>
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <4A2541B9.2000805@octasic.com> <00d501c9e39a$dcbbbe50$96333af0$%roni@huawei.com> <D1611ACB-4739-4A65-94F0-403FC24CDC43@cs.columbia.edu> <6e9223710906021031i31e024dam5673ca9608017d73@mail.gmail.com> <2B4B0335-916C-4CD4-9E40-63BBA6B1DF8B@cs.columbia.edu>
Date: Tue, 2 Jun 2009 11:36:40 -0700
To: Henning Schulzrinne <hgs@cs.columbia.edu>, stephen botzko <stephen.botzko@gmail.com>
From: David Singer <singer@apple.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
Cc: dispatch@ietf.org, Jason Fischl <jason.fischl@skype.net>, avt@ietf.org, Roni Even <Even.roni@huawei.com>, hsinnrei@adobe.com, Slava Borilin <Borilin@spiritdsp.com>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec	WG
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, 02 Jun 2009 18:38:13 -0000

It would also be hard to 'object' to transport work being done in 
traditional 'codec shops' (such as the ITU and MPEG) if this goes 
ahead.

A quality codec standard is usually backed by
* testing
* conformance files
* reference software

and a fairly rigorous design process.  When SMPTE took on VC-1 from 
Microsoft, I think both they and Microsoft were surprised by the 
amount of work involved.

FWIW, 3GPP SA4 is also a place with interest in codecs for packet 
networks, and has standardized codecs in the past.  Opening a new 
work item there is not trivial, but can be done.
-- 
David Singer
Multimedia Standards, Apple Inc.

From john.lazzaro@gmail.com  Tue Jun  2 12:07:30 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 17A9928C190 for <avt@core3.amsl.com>; Tue,  2 Jun 2009 12:07:30 -0700 (PDT)
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 ByFSPCZiBk7l for <avt@core3.amsl.com>; Tue,  2 Jun 2009 12:07:29 -0700 (PDT)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.248]) by core3.amsl.com (Postfix) with ESMTP id 1572128C18D for <avt@ietf.org>; Tue,  2 Jun 2009 12:07:29 -0700 (PDT)
Received: by an-out-0708.google.com with SMTP id c3so6205127ana.4 for <avt@ietf.org>; Tue, 02 Jun 2009 12:07:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=XQAjoMgADoQXAyj6TjAQbk1XXxT/kwiXte+LqPSQrXQ=; b=eygpKhoQVN2AnXPAIduyYzn9giVus1C40P07AJBK7wN8gxlcmIW/B0ndMgWIwbEl0L NhOEZuMfDYaOeP/MDBWCwTN2MlO5sHKk2R1BHhrXyUbyCkwNc+9aKJ9PVuSgb9uqbVmB QVi9mYb27v8SzJl2JOTGASbAoNk21uKojDYJ8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=m287Oj6ayNe8+bdnBcHaKoxlWwnx/qbX5dsKfmO4MFWx/Gj2MsmwcvT7Lb6lT0FoAc gIl0escKwJch/UGhuTTeciFFDsSnL8cEhKwGLh6d3/+PujSEfrpSYsTtVO6cA66k8UKO FOYQz7OMEO68MUPJ2UhtTqWIReS0wAj5zs6GQ=
MIME-Version: 1.0
Received: by 10.100.123.17 with SMTP id v17mr43532anc.167.1243969648142; Tue,  02 Jun 2009 12:07:28 -0700 (PDT)
In-Reply-To: <p062408a4c64b2024e818@10.0.1.8>
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <ybu7hzu7kf2.fsf@jesup.eng.wgate.com> <p062408a4c64b2024e818@10.0.1.8>
Date: Tue, 2 Jun 2009 12:07:28 -0700
Message-ID: <302f570906021207g627bf70cmf6685124ad1df13@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: quoted-printable
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 02 Jun 2009 19:07:30 -0000

On Tue, Jun 2, 2009 at 11:32 AM, David Singer<singer@apple.com> wrote:
> Attending and contributing to MPEG meetings merely means becoming an
> accredited member of your national delegation. =A0In the US, you join the
> INCITS L3.1 activity, and meet the rules for attendance and voting. =A0It=
's
> not hard (much, much, easier than designing an audio codec, or even steer=
ing
> it through a standards process). =A0It's also vastly cheaper than the cos=
ts of
> travel, attendance etc.


A data point here of interest ... in the 7+ years it took for RFC 4695 to m=
ake
it through the process, I only "needed" to attend two IETFs -- the one wher=
e
I made the case in person for AVT to choose it as a working group item
in Salt Lake City, and the IETF in San Francisco a few years later to about
half-way through the process, to remind everyone I had a name and a face :-=
).

The total travel costs was a cheap flight OAK-SLC flight, one night in the
SLC hotel, and a round-trip BART ticket from Berkeley to Civic Center :-).

I think if you compared that to, for example, the cumulative travel bill th=
e
MIT Media Labs folks ran up to guide Structured Audio through the MPEG
process, their travel bill would be one-to-two orders of magnitude greater.

So in that sense, I do think the IETF process is a better fit for someone
running on a (very) tight budget ...

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

From rjesup@wgate.com  Tue Jun  2 12:23:00 2009
Return-Path: <rjesup@wgate.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 41D1528C288; Tue,  2 Jun 2009 12:23:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.734
X-Spam-Level: 
X-Spam-Status: No, score=-1.734 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RDNS_DYNAMIC=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 lPPmqRvTVoGp; Tue,  2 Jun 2009 12:22:59 -0700 (PDT)
Received: from exchange1.wgate.com (pr-66-150-46-254.wgate.com [66.150.46.254]) by core3.amsl.com (Postfix) with ESMTP id 4329328C124; Tue,  2 Jun 2009 12:22:59 -0700 (PDT)
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 2 Jun 2009 15:22:58 -0400
To: David Singer <singer@apple.com>
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <4A2541B9.2000805@octasic.com> <00d501c9e39a$dcbbbe50$96333af0$%roni@huawei.com> <D1611ACB-4739-4A65-94F0-403FC24CDC43@cs.columbia.edu> <6e9223710906021031i31e024dam5673ca9608017d73@mail.gmail.com> <2B4B0335-916C-4CD4-9E40-63BBA6B1DF8B@cs.columbia.edu> <p062408a5c64b21091de5@[10.0.1.8]>
From: Randell Jesup <rjesup@wgate.com>
Date: Tue, 02 Jun 2009 15:23:34 -0400
In-Reply-To: <p062408a5c64b21091de5@[10.0.1.8]> (David Singer's message of "Tue\, 2 Jun 2009 11\:36\:40 -0700")
Message-ID: <ybu8wka5tjd.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.101 (Gnus v5.10.10) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 02 Jun 2009 19:22:58.0041 (UTC) FILETIME=[89655690:01C9E3B7]
Cc: dispatch@ietf.org, Jason Fischl <jason.fischl@skype.net>, avt@ietf.org, Roni Even <Even.roni@huawei.com>, hsinnrei@adobe.com, Slava Borilin <Borilin@spiritdsp.com>, stephen botzko <stephen.botzko@gmail.com>, Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec	WG
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
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, 02 Jun 2009 19:23:00 -0000

David Singer <singer@apple.com> writes:
>It would also be hard to 'object' to transport work being done in
>traditional 'codec shops' (such as the ITU and MPEG) if this goes ahead.
>
>A quality codec standard is usually backed by
>* testing
>* conformance files
>* reference software
>
>and a fairly rigorous design process.  When SMPTE took on VC-1 from
>Microsoft, I think both they and Microsoft were surprised by the amount of
>work involved.

All relevant and indicative of the level of work required, but not
disqualifying I think.

>FWIW, 3GPP SA4 is also a place with interest in codecs for packet networks,
>and has standardized codecs in the past.  Opening a new work item there is
>not trivial, but can be done.

Again, I imagine even getting involved in 3GPP is tough with many hoops,
let alone getting the rest of them to sanction a new codec not designed for
radio use specifically.  You can't even directly apply to join; you have to
go through an "Organizational Partner" like ATIS.  Not going to happen here...

-- 
Randell Jesup, Worldgate (developers of the Ojo videophone), ex-Amiga OS team
rjesup@wgate.com
"The fetters imposed on liberty at home have ever been forged out of the weapons
provided for defence against real, pretended, or imaginary dangers from abroad."
		- James Madison, 4th US president (1751-1836)


From singer@apple.com  Tue Jun  2 12:26:25 2009
Return-Path: <singer@apple.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 80F203A6C76 for <avt@core3.amsl.com>; Tue,  2 Jun 2009 12:26:25 -0700 (PDT)
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 J9fEk414rTyZ for <avt@core3.amsl.com>; Tue,  2 Jun 2009 12:26:23 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id 1111F3A67F6 for <avt@ietf.org>; Tue,  2 Jun 2009 12:26:23 -0700 (PDT)
Received: from relay15.apple.com (relay15.apple.com [17.128.113.54]) by mail-out4.apple.com (Postfix) with ESMTP id 552AA65F12CD; Tue,  2 Jun 2009 12:26:24 -0700 (PDT)
Received: from relay15.apple.com (unknown [127.0.0.1]) by relay15.apple.com (Symantec Brightmail Gateway) with ESMTP id 4A9B25A0003; Tue,  2 Jun 2009 12:26:24 -0700 (PDT)
X-AuditID: 11807136-a44f8bb00000447e-00-4a257cdf6517
Received: from [10.0.1.8] (singda.apple.com [17.202.35.52]) by relay15.apple.com (Apple SCV relay) with ESMTP id 01055558002; Tue,  2 Jun 2009 12:26:23 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p062408a9c64b2c6dc94c@[10.0.1.8]>
In-Reply-To: <302f570906021207g627bf70cmf6685124ad1df13@mail.gmail.com>
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <ybu7hzu7kf2.fsf@jesup.eng.wgate.com> <p062408a4c64b2024e818@10.0.1.8> <302f570906021207g627bf70cmf6685124ad1df13@mail.gmail.com>
Date: Tue, 2 Jun 2009 12:24:23 -0700
To: John Lazzaro <john.lazzaro@gmail.com>, avt@ietf.org
From: David Singer <singer@apple.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec	WG
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, 02 Jun 2009 19:26:26 -0000

At 12:07  -0700 2/06/09, John Lazzaro wrote:
>A data point here of interest ... in the 7+ years it took for RFC 4695 to make
>it through the process, I only "needed" to attend two IETFs -- the one where
>I made the case in person for AVT to choose it as a working group item
>in Salt Lake City, and the IETF in San Francisco a few years later to about
>half-way through the process, to remind everyone I had a name and a face :-).
>
>The total travel costs was a cheap flight OAK-SLC flight, one night in the
>SLC hotel, and a round-trip BART ticket from Berkeley to Civic Center :-).
>
>I think if you compared that to, for example, the cumulative travel bill the
>MIT Media Labs folks ran up to guide Structured Audio through the MPEG
>process, their travel bill would be one-to-two orders of magnitude greater.
>
>So in that sense, I do think the IETF process is a better fit for someone
>running on a (very) tight budget ...

On the other hand, the costs of paying for the time to
* write the specification
* write the conformance suite
* write the reference software

dwarf the costs of attendance at meetings.  RFC 4695 is a nice piece 
of work, but it's not a codec.
-- 
David Singer
Multimedia Standards, Apple Inc.

From rjesup@wgate.com  Tue Jun  2 12:27:46 2009
Return-Path: <rjesup@wgate.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 A4CEE3A6F87 for <avt@core3.amsl.com>; Tue,  2 Jun 2009 12:27:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.734
X-Spam-Level: 
X-Spam-Status: No, score=-1.734 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RDNS_DYNAMIC=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 MAtx4J--mUlK for <avt@core3.amsl.com>; Tue,  2 Jun 2009 12:27:44 -0700 (PDT)
Received: from exchange1.wgate.com (pr-66-150-46-254.wgate.com [66.150.46.254]) by core3.amsl.com (Postfix) with ESMTP id C6BC43A6C76 for <avt@ietf.org>; Tue,  2 Jun 2009 12:27:43 -0700 (PDT)
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 2 Jun 2009 15:27:44 -0400
To: David Singer <singer@apple.com>
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <ybu7hzu7kf2.fsf@jesup.eng.wgate.com> <p062408a4c64b2024e818@[10.0.1.8]>
From: Randell Jesup <rjesup@wgate.com>
Date: Tue, 02 Jun 2009 15:28:21 -0400
In-Reply-To: <p062408a4c64b2024e818@[10.0.1.8]> (David Singer's message of "Tue\, 2 Jun 2009 11\:32\:06 -0700")
Message-ID: <ybu4ouy5tbe.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.101 (Gnus v5.10.10) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 02 Jun 2009 19:27:44.0838 (UTC) FILETIME=[34571660:01C9E3B8]
Cc: 'Slava Borilin' <Borilin@spiritdsp.com>, avt@ietf.org, Roni Even <Even.roni@huawei.com>, 'Jason Fischl' <jason.fischl@skype.net>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec	WG
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
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, 02 Jun 2009 19:27:46 -0000

David Singer <singer@apple.com> writes:
>>Roni Even <Even.roni@huawei.com> writes:
>>>I am not sure what prevented you from doing it today at the ITU or MPEG, why
>>>do you see the IETF handling it differently.
>>
>>Last I knew, ITU was a *far* more closed group (and I think MPEG as well).
>
>Attending and contributing to MPEG meetings merely means becoming an
>accredited member of your national delegation.  In the US, you join the
>INCITS L3.1 activity, and meet the rules for attendance and voting.  It's
>not hard (much, much, easier than designing an audio codec, or even
>steering it through a standards process).  It's also vastly cheaper than
>the costs of travel, attendance etc.

You assume that the people involved have real budgets for travel, etc.  Not
always the case.  I attended IETF in Philly only because I live there; my
company isn't going to spend the money to send me or anyone else here to
any distant meetings at this point.  Perhaps in the future, but that's a
huge impediment to participation - we have other work to do as well. I
will, when possible, participate in IETF meetings remotely via audio
streaming (video in the future?) and feed questions and comments via IM.

-- 
Randell Jesup, Worldgate (developers of the Ojo videophone), ex-Amiga OS team
rjesup@wgate.com
"The fetters imposed on liberty at home have ever been forged out of the weapons
provided for defence against real, pretended, or imaginary dangers from abroad."
		- James Madison, 4th US president (1751-1836)


From singer@apple.com  Tue Jun  2 12:32:15 2009
Return-Path: <singer@apple.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 B6D9B3A6D62; Tue,  2 Jun 2009 12:32:15 -0700 (PDT)
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 Ry59NX7lJluL; Tue,  2 Jun 2009 12:32:11 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 41F2028C124; Tue,  2 Jun 2009 12:32:11 -0700 (PDT)
Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out3.apple.com (Postfix) with ESMTP id 84EE062DD73A; Tue,  2 Jun 2009 12:32:12 -0700 (PDT)
Received: from relay16.apple.com (unknown [127.0.0.1]) by relay16.apple.com (Symantec Brightmail Gateway) with ESMTP id 68B9C5A0005; Tue,  2 Jun 2009 12:32:12 -0700 (PDT)
X-AuditID: 11807137-a4d67bb00000380b-2f-4a257e3cc68f
Received: from [10.0.1.8] (singda.apple.com [17.202.35.52]) by relay16.apple.com (Apple SCV relay) with ESMTP id 1C543558016; Tue,  2 Jun 2009 12:32:12 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p062408aac64b2d02ec07@[10.0.1.8]>
In-Reply-To: <ybu8wka5tjd.fsf@jesup.eng.wgate.com>
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <4A2541B9.2000805@octasic.com> <00d501c9e39a$dcbbbe50$96333af0$%roni@huawei.com> <D1611ACB-4739-4A65-94F0-403FC24CDC43@cs.columbia.edu> <6e9223710906021031i31e024dam5673ca9608017d73@mail.gmail.com> <2B4B0335-916C-4CD4-9E40-63BBA6B1DF8B@cs.columbia.edu> <p062408a5c64b21091de5@[10.0.1.8]> <ybu8wka5tjd.fsf@jesup.eng.wgate.com>
Date: Tue, 2 Jun 2009 12:31:53 -0700
To: Randell Jesup <rjesup@wgate.com>
From: David Singer <singer@apple.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
Cc: dispatch@ietf.org, Jason Fischl <jason.fischl@skype.net>, avt@ietf.org, Roni Even <Even.roni@huawei.com>, hsinnrei@adobe.com, Slava Borilin <Borilin@spiritdsp.com>, stephen botzko <stephen.botzko@gmail.com>, Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec	WG
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, 02 Jun 2009 19:32:15 -0000

At 15:23  -0400 2/06/09, Randell Jesup wrote:
>  >FWIW, 3GPP SA4 is also a place with interest in codecs for packet networks,
>>and has standardized codecs in the past.  Opening a new work item there is
>>not trivial, but can be done.
>
>Again, I imagine even getting involved in 3GPP is tough with many hoops,
>let alone getting the rest of them to sanction a new codec not designed for
>radio use specifically.  You can't even directly apply to join; you have to
>go through an "Organizational Partner" like ATIS.  Not going to happen here...

The only hoop is an organizational partner.  For large companies, it 
can be expensive (e.g. ETSI sets your dues based on your telecoms 
related revenue, if I recall correctly).

On a spectrum of desirability of process etc., I'd guess that
* codecs from international bodies with a procedure and track record 
for doing them thoroughly, are preferred (MPEG, ITU, 3GPP)
* codecs from international bodies not normally in the codec field 
offer at least a stable specification and the opportunity for 
critique and refinement, leading to that specification (e.g. IETF)
* codecs developed in open-source  are at least open to anyone, but 
they have the issue that they lack a formal reference, a formal 
consensus process, a stable publication 'home', IPR rules for 
contributors, and so on
* commercial codecs have the backing of a company, and generally 
stability, interop, and so on are well managed (if they want to 
succeed), but are typically confidential and 'take it or leave it'.


And yes, it gets a little cheaper each time we move down a rung here, 
which is the trade-off.
-- 
David Singer
Multimedia Standards, Apple Inc.

From hsinnrei@adobe.com  Tue Jun  2 09:12:50 2009
Return-Path: <hsinnrei@adobe.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 AD12128C28F; Tue,  2 Jun 2009 09:12:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.843
X-Spam-Level: 
X-Spam-Status: No, score=-1.843 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_ADOBE2=2.455, HTML_MESSAGE=0.001, MANGLED_INXPNS=2.3, 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 onZsQ93cTp7L; Tue,  2 Jun 2009 09:12:48 -0700 (PDT)
Received: from exprod6og115.obsmtp.com (exprod6og115.obsmtp.com [64.18.1.35]) by core3.amsl.com (Postfix) with ESMTP id 96EE628C27C; Tue,  2 Jun 2009 09:12:45 -0700 (PDT)
Received: from source ([192.150.8.22]) by exprod6ob115.postini.com ([64.18.5.12]) with SMTP ID DSNKSiVPcdhJ83E2d+kEqESeABgiYpZrBkv6@postini.com; Tue, 02 Jun 2009 09:12:50 PDT
Received: from inner-relay-2.corp.adobe.com ([153.32.1.52]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id n52GCUWG028262; Tue, 2 Jun 2009 09:12:30 -0700 (PDT)
Received: from nacas02.corp.adobe.com (nacas02.corp.adobe.com [10.8.189.100]) by inner-relay-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id n52GCTtQ022330; Tue, 2 Jun 2009 09:12:29 -0700 (PDT)
Received: from nambx05.corp.adobe.com ([10.8.189.124]) by nacas02.corp.adobe.com ([10.8.189.100]) with mapi; Tue, 2 Jun 2009 09:12:29 -0700
From: Henry Sinnreich <hsinnrei@adobe.com>
To: Roni Even <Even.roni@huawei.com>, Jean-Marc Valin <jean-marc.valin@octasic.com>
Date: Tue, 2 Jun 2009 09:12:26 -0700
Thread-Topic: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
Thread-Index: AcnjlMn504Jo+DIAQwytQ2cXiyrF0wABKOlwAADfcI0=
Message-ID: <C64AB99A.3E55%hsinnrei@adobe.com>
In-Reply-To: <00d501c9e39a$dcbbbe50$96333af0$%roni@huawei.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C64AB99A3E55hsinnreiadobecom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 02 Jun 2009 12:43:35 -0700
Cc: "dispatch@ietf.org" <dispatch@ietf.org>, Slava Borilin <Borilin@spiritdsp.com>, "avt@ietf.org" <avt@ietf.org>, Jason Fischl <jason.fischl@skype.net>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 02 Jun 2009 16:12:50 -0000

--_000_C64AB99A3E55hsinnreiadobecom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

>This leaves the other reasons I heard for doing it at the IETF which is th=
e
>price of participating

This is an important point.
Given the travel constraints for some of the most valuable potential contri=
butors and reviewers, could we envisage online work until the economy impro=
ves, so that an eventual BOF to start with should not be starved of attende=
es? An online BOF?

There are several free online meeting tools available...

How can this be done within the IETF policy?

Henry


On 6/2/09 10:57 AM, "Roni Even" <Even.roni@huawei.com> wrote:

Hi,
I do not want to sound like someone who is for IPR (I am not), but why stop
at codec, let's require it for all IETF work. There are IPR on IETF work
which is must simpler, in my view, than wide band audio codecs.

I think that we can start with "royalty free" even though I am not sure tha=
t
it will accepted as part of the charter of any other work group so why pick
on codecs which require more work.

This leaves the other reasons I heard for doing it at the IETF which is the
price of participating (cheaper than being an ITU-T member) and maybe desig=
n
less expensive characterization tests.

Roni


-----Original Message-----
From: Jean-Marc Valin [mailto:jean-marc.valin@octasic.com]
Sent: Tuesday, June 02, 2009 6:14 PM
To: Roni Even
Cc: 'Slava Borilin'; avt@ietf.org; 'Jason Fischl'; dispatch@ietf.org;
hsinnrei@adobe.com
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Code=
c
WG

Hi,

Roni Even wrote:
>
> I am not sure what prevented you from doing it today at the ITU or
> MPEG, why do you see the IETF handling it differently.
>
> I would also like to remind you and Jean-Marc that once you are
> bringing work to a standard body it may require collaboration with
> other people who will have other proposals that will also address the
> same requirements and you may need to invest money in comparative
> testing by independent listening labs.
>
> I also think that you will need to supply the codec in source code and
> provide copy right to the IETF.
>

I am well aware that bringing work to the IETF would require
collaboration with others. I am not seeking control over the work I am
currently doing and would really welcome such collaboration. The idea is
only to have the best wideband codec possible without IPR issues. Given
the ITU and MPEG track record, I think it would be very unlikely for any
of those organisations to work on an IPR-free codec.

I also agree with Henry that "the Internet has different criteria than
ITU-T networks may have". Internet adoption follows different patterns
than adoption in the ITU primary target markets. For example, the
Internet has more consumer-reconfigurable software, while the ITU has to
deal with a lot of fixed hardware deployments. At the ITU, it makes
sense to invest large sums of money into testing and characterisation of
codecs because the codecs deployed there usually stay around for a long
time and the infrastructure investments are usually very large. On the
other hand, I would say the investments in codecs for the Internet are
comparatively smaller and, while testing is still important, it is not
as critical as it is for the ITU.

It's also a choice one has to make. It is unlikely that companies would
invest money in expensive testing if they are not going to obtain
royalties in return. However, I think we may be able to define some more
lightweight (collaborative?) testing that is sufficient and doesn't
involve as much investments as what the ITU does. For the Internet, I
believe an IPR-free codec that everyone agrees performs well is better
than a patent-encumbered codec that has had more extensive testing. This
is again another difference with the ITU: patent-encumbered codecs tend
to hurt a lot more on the Internet because many applications (e.g.
giving away the client) are very hard (or impossible) when one has to
pay per-channel royalties.

As for the source code issue you pointed out, all the Xiph codecs are
already published under a very permissive open source license (BSD), so
this would not really change.

    Jean-Marc

> Roni
>
>
>
> *From:* avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] *On Behalf
> Of *Slava Borilin
> *Sent:* Monday, June 01, 2009 11:50 PM
> *To:* jean-marc.valin@octasic.com
> *Cc:* avt@ietf.org; Jason Fischl
> *Subject:* Re: [AVT] [dispatch] Proposal to form Internet Wideband
> Audio Codec WG
>
>
>
> Agree with Jean-Marc.
> SPIRIT is interested to contribute as well - having a dozen of proprietar=
y
codecs developed, including
> one specifically desgined for internet (SPIRIT IP-MR, which is now under
WGLC on draft-ietf-avt-rtp-ipmr-04) -
> multi-rate, scalable, adaptive, wideband codec.
>
> We can also continue this work with IETF.
>
> Moreover, most if not all efforts coming from ITU on codecs unfortunately
are NOT really focused on
> internet-specific codecs (that's why several companies have had to invent=
)
- as ITU preference is mainly
> specific (i.e. cellular) networks at first.
>
> however, as we see the greant rise of pure "internet-basd communications"
(skype, webex/citrix, and many others) -
> we all (and users) are suffering from inefficiency in all currently
"standard" codecs and ambiguity in the choice of
> internet-targeted ones.
>
> Again, we probably can put together enough number of contributors to the
WG to have the expertise.
>
> regards,
> Slava Borilin
>
> --
> John Lazzaro wrote:
>
>     A traditional response to this type of request is to note that the
IETF
>
>     really doesn't have much in the way of expertise in audio codec
design.
>
>     I don't see many of the regulars who present at the AES codec paper
sessions
>
>     posting here on AVT (ditto ICASSP paper sessions for voice codecs).
It's
>
>     a full-time job to keep up-to-date and contribute to that
>
>     signal-processing lore.
>
>
>
> Well, there's no reason that the IETF cannot build such an expertise
> in audio codecs. This is actually something in which I'd be interested
> in getting involved and I'm sure others at Xiph.Org would be
> interested as well. We have several people with audio codec expertise
> from working on Vorbis, Speex and (more recently) CELT. It turns out
> that the CELT codec currently under development at Xiph actually meets
> most of the requirements from the original proposal in being a very
> low delay codec with adaptive bit-rate and sampling rate (up to 48
> kHz), scalable complexity, and good robustness to packet loss. We'd be
> willing to continue the development with the IETF. Even if not with
> CELT, it's still like to be involved in such a new WG.
>
> Cheers,
>
>    Jean-Marc



--_000_C64AB99A3E55hsinnreiadobecom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec =
WG</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:=
18pt'>&gt;This leaves the other reasons I heard for doing it at the IETF wh=
ich is the <BR>
&gt;price of participating <BR>
<BR>
This is an important point.<BR>
Given the travel constraints for some of the most valuable potential contri=
butors and reviewers, could we envisage online work until the economy impro=
ves, so that an eventual BOF to start with should not be starved of attende=
es? An online BOF?<BR>
<BR>
There are several free online meeting tools available...<BR>
<BR>
How can this be done within the IETF policy?<BR>
<BR>
Henry<BR>
<BR>
<BR>
On 6/2/09 10:57 AM, &quot;Roni Even&quot; &lt;<a href=3D"Even.roni@huawei.c=
om">Even.roni@huawei.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:18pt'>Hi,<BR>
I do not want to sound like someone who is for IPR (I am not), but why stop=
<BR>
at codec, let's require it for all IETF work. There are IPR on IETF work<BR=
>
which is must simpler, in my view, than wide band audio codecs.<BR>
<BR>
I think that we can start with &quot;royalty free&quot; even though I am no=
t sure that<BR>
it will accepted as part of the charter of any other work group so why pick=
<BR>
on codecs which require more work.<BR>
<BR>
This leaves the other reasons I heard for doing it at the IETF which is the=
<BR>
price of participating (cheaper than being an ITU-T member) and maybe desig=
n<BR>
less expensive characterization tests.<BR>
<BR>
Roni<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Jean-Marc Valin [<a href=3D"mailto:jean-marc.valin@octasic.com">mailt=
o:jean-marc.valin@octasic.com</a>]<BR>
Sent: Tuesday, June 02, 2009 6:14 PM<BR>
To: Roni Even<BR>
Cc: 'Slava Borilin'; <a href=3D"avt@ietf.org">avt@ietf.org</a>; 'Jason Fisc=
hl'; <a href=3D"dispatch@ietf.org">dispatch@ietf.org</a>;<BR>
<a href=3D"hsinnrei@adobe.com">hsinnrei@adobe.com</a><BR>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Code=
c<BR>
WG<BR>
<BR>
Hi,<BR>
<BR>
Roni Even wrote:<BR>
&gt;<BR>
&gt; I am not sure what prevented you from doing it today at the ITU or<BR>
&gt; MPEG, why do you see the IETF handling it differently.<BR>
&gt;<BR>
&gt; I would also like to remind you and Jean-Marc that once you are<BR>
&gt; bringing work to a standard body it may require collaboration with<BR>
&gt; other people who will have other proposals that will also address the<=
BR>
&gt; same requirements and you may need to invest money in comparative<BR>
&gt; testing by independent listening labs.<BR>
&gt;<BR>
&gt; I also think that you will need to supply the codec in source code and=
<BR>
&gt; provide copy right to the IETF.<BR>
&gt;<BR>
<BR>
I am well aware that bringing work to the IETF would require<BR>
collaboration with others. I am not seeking control over the work I am<BR>
currently doing and would really welcome such collaboration. The idea is<BR=
>
only to have the best wideband codec possible without IPR issues. Given<BR>
the ITU and MPEG track record, I think it would be very unlikely for any<BR=
>
of those organisations to work on an IPR-free codec.<BR>
<BR>
I also agree with Henry that &quot;the Internet has different criteria than=
<BR>
ITU-T networks may have&quot;. Internet adoption follows different patterns=
<BR>
than adoption in the ITU primary target markets. For example, the<BR>
Internet has more consumer-reconfigurable software, while the ITU has to<BR=
>
deal with a lot of fixed hardware deployments. At the ITU, it makes<BR>
sense to invest large sums of money into testing and characterisation of<BR=
>
codecs because the codecs deployed there usually stay around for a long<BR>
time and the infrastructure investments are usually very large. On the<BR>
other hand, I would say the investments in codecs for the Internet are<BR>
comparatively smaller and, while testing is still important, it is not<BR>
as critical as it is for the ITU.<BR>
<BR>
It's also a choice one has to make. It is unlikely that companies would<BR>
invest money in expensive testing if they are not going to obtain<BR>
royalties in return. However, I think we may be able to define some more<BR=
>
lightweight (collaborative?) testing that is sufficient and doesn't<BR>
involve as much investments as what the ITU does. For the Internet, I<BR>
believe an IPR-free codec that everyone agrees performs well is better<BR>
than a patent-encumbered codec that has had more extensive testing. This<BR=
>
is again another difference with the ITU: patent-encumbered codecs tend<BR>
to hurt a lot more on the Internet because many applications (e.g.<BR>
giving away the client) are very hard (or impossible) when one has to<BR>
pay per-channel royalties.<BR>
<BR>
As for the source code issue you pointed out, all the Xiph codecs are<BR>
already published under a very permissive open source license (BSD), so<BR>
this would not really change.<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;Jean-Marc<BR>
<BR>
&gt; Roni<BR>
&gt;<BR>
&gt; <BR>
&gt;<BR>
&gt; *From:* <a href=3D"avt-bounces@ietf.org">avt-bounces@ietf.org</a> [<a =
href=3D"mailto:avt-bounces@ietf.org">mailto:avt-bounces@ietf.org</a>] *On B=
ehalf<BR>
&gt; Of *Slava Borilin<BR>
&gt; *Sent:* Monday, June 01, 2009 11:50 PM<BR>
&gt; *To:* <a href=3D"jean-marc.valin@octasic.com">jean-marc.valin@octasic.=
com</a><BR>
&gt; *Cc:* <a href=3D"avt@ietf.org">avt@ietf.org</a>; Jason Fischl<BR>
&gt; *Subject:* Re: [AVT] [dispatch] Proposal to form Internet Wideband<BR>
&gt; Audio Codec WG<BR>
&gt;<BR>
&gt; <BR>
&gt;<BR>
&gt; Agree with Jean-Marc.<BR>
&gt; SPIRIT is interested to contribute as well - having a dozen of proprie=
tary<BR>
codecs developed, including<BR>
&gt; one specifically desgined for internet (SPIRIT IP-MR, which is now und=
er<BR>
WGLC on draft-ietf-avt-rtp-ipmr-04) -<BR>
&gt; multi-rate, scalable, adaptive, wideband codec.<BR>
&gt; <BR>
&gt; We can also continue this work with IETF.<BR>
&gt; <BR>
&gt; Moreover, most if not all efforts coming from ITU on codecs unfortunat=
ely<BR>
are NOT really focused on<BR>
&gt; internet-specific codecs (that's why several companies have had to inv=
ent)<BR>
- as ITU preference is mainly<BR>
&gt; specific (i.e. cellular) networks at first.<BR>
&gt; <BR>
&gt; however, as we see the greant rise of pure &quot;internet-basd communi=
cations&quot;<BR>
(skype, webex/citrix, and many others) -<BR>
&gt; we all (and users) are suffering from inefficiency in all currently<BR=
>
&quot;standard&quot; codecs and ambiguity in the choice of<BR>
&gt; internet-targeted ones.<BR>
&gt; <BR>
&gt; Again, we probably can put together enough number of contributors to t=
he<BR>
WG to have the expertise.<BR>
&gt; <BR>
&gt; regards,<BR>
&gt; Slava Borilin<BR>
&gt; <BR>
&gt; --<BR>
&gt; John Lazzaro wrote:<BR>
&gt;<BR>
&gt; &nbsp;&nbsp;&nbsp;&nbsp;A traditional response to this type of request=
 is to note that the<BR>
IETF<BR>
&gt;<BR>
&gt; &nbsp;&nbsp;&nbsp;&nbsp;really doesn't have much in the way of experti=
se in audio codec<BR>
design.<BR>
&gt;<BR>
&gt; &nbsp;&nbsp;&nbsp;&nbsp;I don't see many of the regulars who present a=
t the AES codec paper<BR>
sessions<BR>
&gt;<BR>
&gt; &nbsp;&nbsp;&nbsp;&nbsp;posting here on AVT (ditto ICASSP paper sessio=
ns for voice codecs).<BR>
It's<BR>
&gt;<BR>
&gt; &nbsp;&nbsp;&nbsp;&nbsp;a full-time job to keep up-to-date and contrib=
ute to that<BR>
&gt;<BR>
&gt; &nbsp;&nbsp;&nbsp;&nbsp;signal-processing lore.<BR>
&gt;<BR>
&gt; &nbsp;&nbsp;&nbsp;&nbsp;<BR>
&gt;<BR>
&gt; Well, there's no reason that the IETF cannot build such an expertise<B=
R>
&gt; in audio codecs. This is actually something in which I'd be interested=
<BR>
&gt; in getting involved and I'm sure others at Xiph.Org would be<BR>
&gt; interested as well. We have several people with audio codec expertise<=
BR>
&gt; from working on Vorbis, Speex and (more recently) CELT. It turns out<B=
R>
&gt; that the CELT codec currently under development at Xiph actually meets=
<BR>
&gt; most of the requirements from the original proposal in being a very<BR=
>
&gt; low delay codec with adaptive bit-rate and sampling rate (up to 48<BR>
&gt; kHz), scalable complexity, and good robustness to packet loss. We'd be=
<BR>
&gt; willing to continue the development with the IETF. Even if not with<BR=
>
&gt; CELT, it's still like to be involved in such a new WG.<BR>
&gt;<BR>
&gt; Cheers,<BR>
&gt; <BR>
&gt; &nbsp;&nbsp;&nbsp;Jean-Marc<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--_000_C64AB99A3E55hsinnreiadobecom_--

From spencer@wonderhamster.org  Tue Jun  2 09:46:32 2009
Return-Path: <spencer@wonderhamster.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 5F9753A67CC; Tue,  2 Jun 2009 09:46:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.157
X-Spam-Level: **
X-Spam-Status: No, score=2.157 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_ADOBE2=2.455, HTML_MESSAGE=0.001, MANGLED_INXPNS=2.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 nLppJH6FHq-m; Tue,  2 Jun 2009 09:46:30 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 7AD0E3A6FFC; Tue,  2 Jun 2009 09:45:12 -0700 (PDT)
Received: from S73602b (w173.z064002096.dfw-tx.dsl.cnc.net [64.2.96.173]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1MBX6j3fcO-000cju; Tue, 02 Jun 2009 12:45:09 -0400
Message-ID: <E0F5850494F549508152266797943F87@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Henry Sinnreich" <hsinnrei@adobe.com>, "Roni Even" <Even.roni@huawei.com>, "Jean-Marc Valin" <jean-marc.valin@octasic.com>
References: <C64AB99A.3E55%hsinnrei@adobe.com>
Date: Tue, 2 Jun 2009 11:44:51 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_330A_01C9E377.8A1F24C0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX191DGjPNv7ANdr3PHcraEsSPZydSTH+9ISA8Ip tqJZeWdCDEhUz9iSMjrs4FaJFxz15P9mkScqz97UwkBO6gpPlE YvU5yu1pDMeRa1CHRbxZLqJ0KgDL8MVmYgzycumlqY=
X-Mailman-Approved-At: Tue, 02 Jun 2009 12:43:35 -0700
Cc: dispatch@ietf.org, Slava Borilin <Borilin@spiritdsp.com>, avt@ietf.org
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 02 Jun 2009 16:46:32 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_330A_01C9E377.8A1F24C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WGI =
am not an area director, nor do i play one on IPTV, but my suggestion =
for anyone interested would be to=20

- request a non-WG mailing list (from either of the RAI area directors),

- announce it on this mailing list (and others that seem to be =
appropriate, and=20

- start discussions, which the area directors typically look at when =
judging whether there's enough interest and enough clue to justify =
approving a BOF and/or chartering a working group.

I didn't see a mailing list included in Jason's proposal - if I missed =
one, my apologies.

If people at the IETF can do this work, and want to do this work, IETF =
process policies should not get in the way of that happening.

And I haven't heard of an AD turning down a request for a non-WG mailing =
list yet, keeping in mind that one of said lists is ietf-sailors, for =
people interested in sailing to/from/at IETF meetings - the bar is =
(appropriately) low.

Thanks,

Spencer
  ----- Original Message -----=20
  From: Henry Sinnreich=20
  To: Roni Even ; Jean-Marc Valin=20
  Cc: dispatch@ietf.org ; Slava Borilin ; avt@ietf.org=20
  Sent: Tuesday, June 02, 2009 11:12 AM
  Subject: Re: [dispatch] [AVT] Proposal to form Internet Wideband Audio =
Codec WG


  >This leaves the other reasons I heard for doing it at the IETF which =
is the=20
  >price of participating=20

  This is an important point.
  Given the travel constraints for some of the most valuable potential =
contributors and reviewers, could we envisage online work until the =
economy improves, so that an eventual BOF to start with should not be =
starved of attendees? An online BOF?

  There are several free online meeting tools available...

  How can this be done within the IETF policy?

  Henry


  On 6/2/09 10:57 AM, "Roni Even" <Even.roni@huawei.com> wrote:


    Hi,
    I do not want to sound like someone who is for IPR (I am not), but =
why stop
    at codec, let's require it for all IETF work. There are IPR on IETF =
work
    which is must simpler, in my view, than wide band audio codecs.

    I think that we can start with "royalty free" even though I am not =
sure that
    it will accepted as part of the charter of any other work group so =
why pick
    on codecs which require more work.

    This leaves the other reasons I heard for doing it at the IETF which =
is the
    price of participating (cheaper than being an ITU-T member) and =
maybe design
    less expensive characterization tests.

    Roni


    -----Original Message-----
    From: Jean-Marc Valin [mailto:jean-marc.valin@octasic.com]
    Sent: Tuesday, June 02, 2009 6:14 PM
    To: Roni Even
    Cc: 'Slava Borilin'; avt@ietf.org; 'Jason Fischl'; =
dispatch@ietf.org;
    hsinnrei@adobe.com
    Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband =
Audio Codec
    WG

    Hi,

    Roni Even wrote:
    >
    > I am not sure what prevented you from doing it today at the ITU or
    > MPEG, why do you see the IETF handling it differently.
    >
    > I would also like to remind you and Jean-Marc that once you are
    > bringing work to a standard body it may require collaboration with
    > other people who will have other proposals that will also address =
the
    > same requirements and you may need to invest money in comparative
    > testing by independent listening labs.
    >
    > I also think that you will need to supply the codec in source code =
and
    > provide copy right to the IETF.
    >

    I am well aware that bringing work to the IETF would require
    collaboration with others. I am not seeking control over the work I =
am
    currently doing and would really welcome such collaboration. The =
idea is
    only to have the best wideband codec possible without IPR issues. =
Given
    the ITU and MPEG track record, I think it would be very unlikely for =
any
    of those organisations to work on an IPR-free codec.

    I also agree with Henry that "the Internet has different criteria =
than
    ITU-T networks may have". Internet adoption follows different =
patterns
    than adoption in the ITU primary target markets. For example, the
    Internet has more consumer-reconfigurable software, while the ITU =
has to
    deal with a lot of fixed hardware deployments. At the ITU, it makes
    sense to invest large sums of money into testing and =
characterisation of
    codecs because the codecs deployed there usually stay around for a =
long
    time and the infrastructure investments are usually very large. On =
the
    other hand, I would say the investments in codecs for the Internet =
are
    comparatively smaller and, while testing is still important, it is =
not
    as critical as it is for the ITU.

    It's also a choice one has to make. It is unlikely that companies =
would
    invest money in expensive testing if they are not going to obtain
    royalties in return. However, I think we may be able to define some =
more
    lightweight (collaborative?) testing that is sufficient and doesn't
    involve as much investments as what the ITU does. For the Internet, =
I
    believe an IPR-free codec that everyone agrees performs well is =
better
    than a patent-encumbered codec that has had more extensive testing. =
This
    is again another difference with the ITU: patent-encumbered codecs =
tend
    to hurt a lot more on the Internet because many applications (e.g.
    giving away the client) are very hard (or impossible) when one has =
to
    pay per-channel royalties.

    As for the source code issue you pointed out, all the Xiph codecs =
are
    already published under a very permissive open source license (BSD), =
so
    this would not really change.

        Jean-Marc

    > Roni
    >
    >=20
    >
    > *From:* avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] *On =
Behalf
    > Of *Slava Borilin
    > *Sent:* Monday, June 01, 2009 11:50 PM
    > *To:* jean-marc.valin@octasic.com
    > *Cc:* avt@ietf.org; Jason Fischl
    > *Subject:* Re: [AVT] [dispatch] Proposal to form Internet Wideband
    > Audio Codec WG
    >
    >=20
    >
    > Agree with Jean-Marc.
    > SPIRIT is interested to contribute as well - having a dozen of =
proprietary
    codecs developed, including
    > one specifically desgined for internet (SPIRIT IP-MR, which is now =
under
    WGLC on draft-ietf-avt-rtp-ipmr-04) -
    > multi-rate, scalable, adaptive, wideband codec.
    >=20
    > We can also continue this work with IETF.
    >=20
    > Moreover, most if not all efforts coming from ITU on codecs =
unfortunately
    are NOT really focused on
    > internet-specific codecs (that's why several companies have had to =
invent)
    - as ITU preference is mainly
    > specific (i.e. cellular) networks at first.
    >=20
    > however, as we see the greant rise of pure "internet-basd =
communications"
    (skype, webex/citrix, and many others) -
    > we all (and users) are suffering from inefficiency in all =
currently
    "standard" codecs and ambiguity in the choice of
    > internet-targeted ones.
    >=20
    > Again, we probably can put together enough number of contributors =
to the
    WG to have the expertise.
    >=20
    > regards,
    > Slava Borilin
    >=20
    > --
    > John Lazzaro wrote:
    >
    >     A traditional response to this type of request is to note that =
the
    IETF
    >
    >     really doesn't have much in the way of expertise in audio =
codec
    design.
    >
    >     I don't see many of the regulars who present at the AES codec =
paper
    sessions
    >
    >     posting here on AVT (ditto ICASSP paper sessions for voice =
codecs).
    It's
    >
    >     a full-time job to keep up-to-date and contribute to that
    >
    >     signal-processing lore.
    >
    >    =20
    >
    > Well, there's no reason that the IETF cannot build such an =
expertise
    > in audio codecs. This is actually something in which I'd be =
interested
    > in getting involved and I'm sure others at Xiph.Org would be
    > interested as well. We have several people with audio codec =
expertise
    > from working on Vorbis, Speex and (more recently) CELT. It turns =
out
    > that the CELT codec currently under development at Xiph actually =
meets
    > most of the requirements from the original proposal in being a =
very
    > low delay codec with adaptive bit-rate and sampling rate (up to 48
    > kHz), scalable complexity, and good robustness to packet loss. =
We'd be
    > willing to continue the development with the IETF. Even if not =
with
    > CELT, it's still like to be involved in such a new WG.
    >
    > Cheers,
    >=20
    >    Jean-Marc





-------------------------------------------------------------------------=
-----


  _______________________________________________
  dispatch mailing list
  dispatch@ietf.org
  https://www.ietf.org/mailman/listinfo/dispatch

------=_NextPart_000_330A_01C9E377.8A1F24C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Re: [AVT] [dispatch] Proposal to form Internet =
Wideband Audio Codec WG</TITLE>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18702">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>I am not an area director, nor do i play one on =
IPTV, but my=20
suggestion for anyone interested would be to </FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>- request a non-WG mailing list (from either of the =
RAI area=20
directors),</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>- announce it on this mailing list (and others that =
seem to be=20
appropriate, and </FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>- start discussions, which the area directors =
typically look=20
at when judging whether there's enough interest and enough clue to =
justify=20
approving a BOF and/or chartering a working group.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>I didn't see a mailing list included in Jason's =
proposal - if=20
I missed one, my apologies.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>If people at the IETF can do this work, and want to =
do this=20
work, IETF process policies should not get in the way of that=20
happening.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>And I haven't heard of an AD turning down a request =
for a=20
non-WG mailing list yet, keeping in mind that one of said lists is =
ietf-sailors,=20
for people interested in sailing to/from/at IETF meetings - the bar is=20
(appropriately) low.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Thanks,</FONT></DIV>
<DIV><FONT size=3D2><BR>Spencer</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; =
PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: =
black"><B>From:</B>=20
  <A title=3Dhsinnrei@adobe.com href=3D"mailto:hsinnrei@adobe.com">Henry =

  Sinnreich</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3DEven.roni@huawei.com=20
  href=3D"mailto:Even.roni@huawei.com">Roni Even</A> ; <A=20
  title=3Djean-marc.valin@octasic.com=20
  href=3D"mailto:jean-marc.valin@octasic.com">Jean-Marc Valin</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A =
title=3Ddispatch@ietf.org=20
  href=3D"mailto:dispatch@ietf.org">dispatch@ietf.org</A> ; <A=20
  title=3DBorilin@spiritdsp.com =
href=3D"mailto:Borilin@spiritdsp.com">Slava=20
  Borilin</A> ; <A title=3Davt@ietf.org=20
  href=3D"mailto:avt@ietf.org">avt@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, June 02, 2009 =
11:12=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [dispatch] [AVT] =
Proposal to=20
  form Internet Wideband Audio Codec WG</DIV>
  <DIV><BR></DIV><FONT face=3D"Calibri, Verdana, Helvetica, Arial"><SPAN =

  style=3D"FONT-SIZE: 18pt">&gt;This leaves the other reasons I heard =
for doing it=20
  at the IETF which is the <BR>&gt;price of participating <BR><BR>This =
is an=20
  important point.<BR>Given the travel constraints for some of the most =
valuable=20
  potential contributors and reviewers, could we envisage online work =
until the=20
  economy improves, so that an eventual BOF to start with should not be =
starved=20
  of attendees? An online BOF?<BR><BR>There are several free online =
meeting=20
  tools available...<BR><BR>How can this be done within the IETF=20
  policy?<BR><BR>Henry<BR><BR><BR>On 6/2/09 10:57 AM, "Roni Even" &lt;<A =

  href=3D"mailto:Even.roni@huawei.com">Even.roni@huawei.com</A>&gt;=20
  wrote:<BR><BR></SPAN></FONT>
  <BLOCKQUOTE><FONT face=3D"Calibri, Verdana, Helvetica, Arial"><SPAN=20
    style=3D"FONT-SIZE: 18pt">Hi,<BR>I do not want to sound like someone =
who is=20
    for IPR (I am not), but why stop<BR>at codec, let's require it for =
all IETF=20
    work. There are IPR on IETF work<BR>which is must simpler, in my =
view, than=20
    wide band audio codecs.<BR><BR>I think that we can start with =
"royalty free"=20
    even though I am not sure that<BR>it will accepted as part of the =
charter of=20
    any other work group so why pick<BR>on codecs which require more=20
    work.<BR><BR>This leaves the other reasons I heard for doing it at =
the IETF=20
    which is the<BR>price of participating (cheaper than being an ITU-T =
member)=20
    and maybe design<BR>less expensive characterization=20
    tests.<BR><BR>Roni<BR><BR><BR>-----Original Message-----<BR>From: =
Jean-Marc=20
    Valin [<A=20
    =
href=3D"mailto:jean-marc.valin@octasic.com">mailto:jean-marc.valin@octasi=
c.com</A>]<BR>Sent:=20
    Tuesday, June 02, 2009 6:14 PM<BR>To: Roni Even<BR>Cc: 'Slava =
Borilin'; <A=20
    href=3D"avt@ietf.org">avt@ietf.org</A>; 'Jason Fischl'; <A=20
    href=3D"dispatch@ietf.org">dispatch@ietf.org</A>;<BR><A=20
    href=3D"hsinnrei@adobe.com">hsinnrei@adobe.com</A><BR>Subject: Re: =
[AVT]=20
    [dispatch] Proposal to form Internet Wideband Audio=20
    Codec<BR>WG<BR><BR>Hi,<BR><BR>Roni Even wrote:<BR>&gt;<BR>&gt; I am =
not sure=20
    what prevented you from doing it today at the ITU or<BR>&gt; MPEG, =
why do=20
    you see the IETF handling it differently.<BR>&gt;<BR>&gt; I would =
also like=20
    to remind you and Jean-Marc that once you are<BR>&gt; bringing work =
to a=20
    standard body it may require collaboration with<BR>&gt; other people =
who=20
    will have other proposals that will also address the<BR>&gt; same=20
    requirements and you may need to invest money in comparative<BR>&gt; =
testing=20
    by independent listening labs.<BR>&gt;<BR>&gt; I also think that you =
will=20
    need to supply the codec in source code and<BR>&gt; provide copy =
right to=20
    the IETF.<BR>&gt;<BR><BR>I am well aware that bringing work to the =
IETF=20
    would require<BR>collaboration with others. I am not seeking control =
over=20
    the work I am<BR>currently doing and would really welcome such=20
    collaboration. The idea is<BR>only to have the best wideband codec =
possible=20
    without IPR issues. Given<BR>the ITU and MPEG track record, I think =
it would=20
    be very unlikely for any<BR>of those organisations to work on an =
IPR-free=20
    codec.<BR><BR>I also agree with Henry that "the Internet has =
different=20
    criteria than<BR>ITU-T networks may have". Internet adoption follows =

    different patterns<BR>than adoption in the ITU primary target =
markets. For=20
    example, the<BR>Internet has more consumer-reconfigurable software, =
while=20
    the ITU has to<BR>deal with a lot of fixed hardware deployments. At =
the ITU,=20
    it makes<BR>sense to invest large sums of money into testing and=20
    characterisation of<BR>codecs because the codecs deployed there =
usually stay=20
    around for a long<BR>time and the infrastructure investments are =
usually=20
    very large. On the<BR>other hand, I would say the investments in =
codecs for=20
    the Internet are<BR>comparatively smaller and, while testing is =
still=20
    important, it is not<BR>as critical as it is for the =
ITU.<BR><BR>It's also a=20
    choice one has to make. It is unlikely that companies =
would<BR>invest money=20
    in expensive testing if they are not going to obtain<BR>royalties in =
return.=20
    However, I think we may be able to define some more<BR>lightweight=20
    (collaborative?) testing that is sufficient and doesn't<BR>involve =
as much=20
    investments as what the ITU does. For the Internet, I<BR>believe an =
IPR-free=20
    codec that everyone agrees performs well is better<BR>than a=20
    patent-encumbered codec that has had more extensive testing. =
This<BR>is=20
    again another difference with the ITU: patent-encumbered codecs =
tend<BR>to=20
    hurt a lot more on the Internet because many applications =
(e.g.<BR>giving=20
    away the client) are very hard (or impossible) when one has =
to<BR>pay=20
    per-channel royalties.<BR><BR>As for the source code issue you =
pointed out,=20
    all the Xiph codecs are<BR>already published under a very permissive =
open=20
    source license (BSD), so<BR>this would not really=20
    change.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;Jean-Marc<BR><BR>&gt;=20
    Roni<BR>&gt;<BR>&gt; <BR>&gt;<BR>&gt; *From:* <A=20
    href=3D"avt-bounces@ietf.org">avt-bounces@ietf.org</A> [<A=20
    =
href=3D"mailto:avt-bounces@ietf.org">mailto:avt-bounces@ietf.org</A>] =
*On=20
    Behalf<BR>&gt; Of *Slava Borilin<BR>&gt; *Sent:* Monday, June 01, =
2009 11:50=20
    PM<BR>&gt; *To:* <A=20
    =
href=3D"jean-marc.valin@octasic.com">jean-marc.valin@octasic.com</A><BR>&=
gt;=20
    *Cc:* <A href=3D"avt@ietf.org">avt@ietf.org</A>; Jason =
Fischl<BR>&gt;=20
    *Subject:* Re: [AVT] [dispatch] Proposal to form Internet =
Wideband<BR>&gt;=20
    Audio Codec WG<BR>&gt;<BR>&gt; <BR>&gt;<BR>&gt; Agree with=20
    Jean-Marc.<BR>&gt; SPIRIT is interested to contribute as well - =
having a=20
    dozen of proprietary<BR>codecs developed, including<BR>&gt; one =
specifically=20
    desgined for internet (SPIRIT IP-MR, which is now under<BR>WGLC on=20
    draft-ietf-avt-rtp-ipmr-04) -<BR>&gt; multi-rate, scalable, =
adaptive,=20
    wideband codec.<BR>&gt; <BR>&gt; We can also continue this work with =

    IETF.<BR>&gt; <BR>&gt; Moreover, most if not all efforts coming from =
ITU on=20
    codecs unfortunately<BR>are NOT really focused on<BR>&gt; =
internet-specific=20
    codecs (that's why several companies have had to invent)<BR>- as ITU =

    preference is mainly<BR>&gt; specific (i.e. cellular) networks at=20
    first.<BR>&gt; <BR>&gt; however, as we see the greant rise of pure=20
    "internet-basd communications"<BR>(skype, webex/citrix, and many =
others)=20
    -<BR>&gt; we all (and users) are suffering from inefficiency in all=20
    currently<BR>"standard" codecs and ambiguity in the choice =
of<BR>&gt;=20
    internet-targeted ones.<BR>&gt; <BR>&gt; Again, we probably can put =
together=20
    enough number of contributors to the<BR>WG to have the =
expertise.<BR>&gt;=20
    <BR>&gt; regards,<BR>&gt; Slava Borilin<BR>&gt; <BR>&gt; --<BR>&gt; =
John=20
    Lazzaro wrote:<BR>&gt;<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;A traditional =

    response to this type of request is to note that =
the<BR>IETF<BR>&gt;<BR>&gt;=20
    &nbsp;&nbsp;&nbsp;&nbsp;really doesn't have much in the way of =
expertise in=20
    audio codec<BR>design.<BR>&gt;<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;I =
don't see=20
    many of the regulars who present at the AES codec=20
    paper<BR>sessions<BR>&gt;<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;posting =
here on=20
    AVT (ditto ICASSP paper sessions for voice =
codecs).<BR>It's<BR>&gt;<BR>&gt;=20
    &nbsp;&nbsp;&nbsp;&nbsp;a full-time job to keep up-to-date and =
contribute to=20
    that<BR>&gt;<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;signal-processing=20
    lore.<BR>&gt;<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;<BR>&gt; Well, =
there's=20
    no reason that the IETF cannot build such an expertise<BR>&gt; in =
audio=20
    codecs. This is actually something in which I'd be =
interested<BR>&gt; in=20
    getting involved and I'm sure others at Xiph.Org would be<BR>&gt; =
interested=20
    as well. We have several people with audio codec expertise<BR>&gt; =
from=20
    working on Vorbis, Speex and (more recently) CELT. It turns =
out<BR>&gt; that=20
    the CELT codec currently under development at Xiph actually =
meets<BR>&gt;=20
    most of the requirements from the original proposal in being a =
very<BR>&gt;=20
    low delay codec with adaptive bit-rate and sampling rate (up to =
48<BR>&gt;=20
    kHz), scalable complexity, and good robustness to packet loss. We'd=20
    be<BR>&gt; willing to continue the development with the IETF. Even =
if not=20
    with<BR>&gt; CELT, it's still like to be involved in such a new=20
    WG.<BR>&gt;<BR>&gt; Cheers,<BR>&gt; <BR>&gt;=20
    &nbsp;&nbsp;&nbsp;Jean-Marc<BR><BR><BR></SPAN></FONT></BLOCKQUOTE>
  <P>
  <HR>

  <P></P>_______________________________________________<BR>dispatch =
mailing=20
  =
list<BR>dispatch@ietf.org<BR>https://www.ietf.org/mailman/listinfo/dispat=
ch<BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_330A_01C9E377.8A1F24C0--



From hsinnrei@adobe.com  Tue Jun  2 12:11:00 2009
Return-Path: <hsinnrei@adobe.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 E693128C28B; Tue,  2 Jun 2009 12:11:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.843
X-Spam-Level: 
X-Spam-Status: No, score=-1.843 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_ADOBE2=2.455, HTML_MESSAGE=0.001, MANGLED_INXPNS=2.3, 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 CuPXqTdXXPw2; Tue,  2 Jun 2009 12:10:59 -0700 (PDT)
Received: from exprod6og107.obsmtp.com (exprod6og107.obsmtp.com [64.18.1.208]) by core3.amsl.com (Postfix) with ESMTP id 4A2AE28C284; Tue,  2 Jun 2009 12:10:56 -0700 (PDT)
Received: from source ([192.150.11.134]) by exprod6ob107.postini.com ([64.18.5.12]) with SMTP ID DSNKSiV5NasuM3anKRadEd4fjqNVi/FGHTi2@postini.com; Tue, 02 Jun 2009 12:11:00 PDT
Received: from inner-relay-3.eur.adobe.com ([192.150.8.236]) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id n52J4eao017579; Tue, 2 Jun 2009 12:04:40 -0700 (PDT)
Received: from nahub01.corp.adobe.com (nahub01.corp.adobe.com [10.8.189.97]) by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id n52JAeY2021497; Tue, 2 Jun 2009 12:10:41 -0700 (PDT)
Received: from nambx05.corp.adobe.com ([10.8.189.124]) by nahub01.corp.adobe.com ([10.8.189.97]) with mapi; Tue, 2 Jun 2009 12:10:40 -0700
From: Henry Sinnreich <hsinnrei@adobe.com>
To: Slava Borilin <Borilin@spiritdsp.com>, stephen botzko <stephen.botzko@gmail.com>, Henning Schulzrinne <hgs@cs.columbia.edu>
Date: Tue, 2 Jun 2009 12:10:38 -0700
Thread-Topic: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
Thread-Index: AcnjqANErfh4GUqeQ4SC5NZuzNxHZgAAB2LQAANr4HU=
Message-ID: <C64AE35E.3E6E%hsinnrei@adobe.com>
In-Reply-To: <AA5A65FC22B6F145830AC0EAC7586A6C04BF9091@mail-srv.spiritcorp.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C64AE35E3E6Ehsinnreiadobecom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 02 Jun 2009 12:43:35 -0700
Cc: "dispatch@ietf.org" <dispatch@ietf.org>, "avt@ietf.org" <avt@ietf.org>, Roni Even <Even.roni@huawei.com>, Jason Fischl <jason.fischl@skype.net>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 02 Jun 2009 19:11:01 -0000

--_000_C64AE35E3E6Ehsinnreiadobecom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

>at least people from the potential contributors (at least Skype, Speex, SP=
IRIT) are already pretty-good

As a user of all three codecs and some other as well:
The seem to me clearly among the best technology and in wide-spread use as =
well.

This should put to rest the questions of expertise, quality and availabilit=
y of contributors and reviewers.

Henry


On 6/2/09 12:33 PM, "Slava Borilin" <Borilin@spiritdsp.com> wrote:

I do not beleive the one that will come wil be low quality.
at least people from the potential contributors (at least Skype, Speex, SPI=
RIT) are already pretty-good in the commercially exploiting their own codec=
s on the market.
i think this is probably false alert.

regards,
Slava Borilin



________________________________
From: stephen botzko [mailto:stephen.botzko@gmail.com]
Sent: Tuesday, June 02, 2009 9:32 PM
To: Henning Schulzrinne
Cc: Roni Even; dispatch@ietf.org; Jason Fischl; avt@ietf.org; hsinnrei@adob=
e.com; Slava Borilin
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Code=
c WG

>>> - the quality of the codec may not be competitive

I think its very important that the codec quality be competitive.  People e=
xpect excellence from IETF standards  Standardizing non-competitive codecs =
because they are cheap does not seem to be a good choce.

Steve B.

On Tue, Jun 2, 2009 at 12:15 PM, Henning Schulzrinne <hgs@cs.columbia.edu> =
wrote:
I  view this as a trade-off. If we pursue this, there are risks:

- nothing  may come of it since there are no experts willing to help
- somebody will  claim IPR on the resulting work
- the quality of the codec may not be  competitive

However, if we don't do this, we are stuck with the status  quo, which is n=
ot all that satisfactory. Thus, unless there are significant  costs for "in=
nocent bystanders", I see this as a risk worth taking. In the  worst case, =
we are no worse off than we are today. In all other cases, we'll  have an a=
dditional choice for a wideband codec, even if it's not "the best",  just "=
good enough". After all, most people use G.711 today, which has a really  h=
ard time making that claim.

Most real work in the IETF is done by very  small teams, typically less tha=
n 10, so as long as we have a handful of people  that are willing to contri=
bute, this can work. It might even work better,  since you may get fewer pe=
ople who have half-baked opinions - we may skip the  binary vs. XML debates=
...

We can set some ground rules ("must be tested  with packet loss of 5%") and=
 then see what happens. Compared to most network  protocols, the likely neg=
ative impacts (such as security or congestion control  issues) of even a ba=
dly-designed codec are pretty limited.

Henning




On Jun 2, 2009, at 11:57 AM, Roni Even wrote:


Hi,
I  do not want to sound like someone who is for IPR (I am not), but why  st=
op
at codec, let's require it for all IETF work. There are IPR on IETF  work
which is must simpler, in my view, than wide band audio  codecs.

I think that we can start with "royalty free" even though I  am not sure th=
at
it will accepted as part of the charter of any other  work group so why pic=
k
on codecs which require more work.

This  leaves the other reasons I heard for doing it at the IETF which is  t=
he
price of participating (cheaper than being an ITU-T member) and maybe  desi=
gn
less expensive characterization  tests.

Roni


-----Original Message-----
From: Jean-Marc  Valin [mailto:jean-marc.valin@octasic.com]
Sent: Tuesday, June 02,  2009 6:14 PM
To: Roni Even
Cc: 'Slava Borilin'; avt@ietf.org; 'Jason Fischl';  dispatch@ietf.org;
hsinnrei@adobe.com
Subject: Re: [AVT] [dispatch]  Proposal to form Internet Wideband Audio Cod=
ec
WG

Hi,

Roni  Even wrote:


I  am not sure what prevented you from doing it today at the ITU or
MPEG,  why do you see the IETF handling it differently.

I would also like  to remind you and Jean-Marc that once you are
bringing work to a  standard body it may require collaboration with
other people who will  have other proposals that will also address the
same requirements and  you may need to invest money in comparative
testing by independent  listening labs.

I also think that you will need to supply the codec  in source code and
provide copy right to the  IETF.


I am well aware that bringing work to the IETF  would require
collaboration with others. I am not seeking control over  the work I am
currently doing and would really welcome such  collaboration. The idea is
only to have the best wideband codec possible  without IPR issues. Given
the ITU and MPEG track record, I think it would  be very unlikely for any
of those organisations to work on an IPR-free  codec.

I also agree with Henry that "the Internet has different  criteria than
ITU-T networks may have". Internet adoption follows  different patterns
than adoption in the ITU primary target markets. For  example, the
Internet has more consumer-reconfigurable software, while  the ITU has to
deal with a lot of fixed hardware deployments. At the ITU,  it makes
sense to invest large sums of money into testing and  characterisation of
codecs because the codecs deployed there usually stay  around for a long
time and the infrastructure investments are usually  very large. On the
other hand, I would say the investments in codecs for  the Internet are
comparatively smaller and, while testing is still  important, it is not
as critical as it is for the ITU.

It's also a  choice one has to make. It is unlikely that companies would
invest money  in expensive testing if they are not going to obtain
royalties in return.  However, I think we may be able to define some more
lightweight  (collaborative?) testing that is sufficient and doesn't
involve as much  investments as what the ITU does. For the Internet, I
believe an IPR-free  codec that everyone agrees performs well is better
than a  patent-encumbered codec that has had more extensive testing. This
is  again another difference with the ITU: patent-encumbered codecs tend
to  hurt a lot more on the Internet because many applications (e.g.
giving  away the client) are very hard (or impossible) when one has to
pay  per-channel royalties.

As for the source code issue you pointed out,  all the Xiph codecs are
already published under a very permissive open  source license (BSD), so
this would not really change.

   Jean-Marc


Roni



*From:*  avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]  *On Behalf
Of *Slava Borilin
*Sent:* Monday, June 01, 2009 11:50  PM
*To:* jean-marc.valin@octasic.com
*Cc:* avt@ietf.org; Jason  Fischl
*Subject:* Re: [AVT] [dispatch] Proposal to form Internet  Wideband
Audio Codec WG



Agree with Jean-Marc.
SPIRIT  is interested to contribute as well - having a dozen of  proprietar=
y
codecs developed, including

one  specifically desgined for internet (SPIRIT IP-MR, which is now  under
WGLC on draft-ietf-avt-rtp-ipmr-04) -

multi-rate,  scalable, adaptive, wideband codec.

We can also continue this work  with IETF.

Moreover, most if not all efforts coming from ITU on  codecs unfortunately
are NOT really focused on

internet-specific  codecs (that's why several companies have had to invent)
-  as ITU preference is mainly

specific  (i.e. cellular) networks at first.

however, as we see the greant  rise of pure "internet-basd communications"
(skype,  webex/citrix, and many others) -

we  all (and users) are suffering from inefficiency in all  currently
"standard" codecs and ambiguity in the choice  of

internet-targeted  ones.

Again, we probably can put together enough number of  contributors to the
WG to have the expertise.


regards,
Slava  Borilin

--
John Lazzaro wrote:

  A traditional  response to this type of request is to note that the
IETF


   really doesn't have much in the way of expertise in audio  codec
design.


   I don't see many of the regulars who present at the AES codec  paper
sessions


   posting here on AVT (ditto ICASSP paper sessions for voice  codecs).
It's


   a full-time job to keep up-to-date and contribute to that

   signal-processing lore.



Well, there's no reason that the  IETF cannot build such an expertise
in audio codecs. This is actually  something in which I'd be interested
in getting involved and I'm sure  others at Xiph.Org would be
interested as well. We have several people  with audio codec expertise
from working on Vorbis, Speex and (more  recently) CELT. It turns out
that the CELT codec currently under  development at Xiph actually meets
most of the requirements from the  original proposal in being a very
low delay codec with adaptive  bit-rate and sampling rate (up to 48
kHz), scalable complexity, and  good robustness to packet loss. We'd be
willing to continue the  development with the IETF. Even if not with
CELT, it's still like to be  involved in such a new  WG.

Cheers,

 Jean-Marc

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


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



--_000_C64AE35E3E6Ehsinnreiadobecom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec =
WG</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:=
18pt'>&gt;</SPAN></FONT><SPAN STYLE=3D'font-size:18pt'><FONT COLOR=3D"#0000=
FE"><FONT FACE=3D"Arial">at least people from the potential contributors (a=
t least Skype, Speex, SPIRIT) are already pretty-good<BR>
<BR>
</FONT></FONT><FONT FACE=3D"Arial">As a user of all three codecs and some o=
ther as well:<BR>
The seem to me clearly among the best technology and in wide-spread use as =
well.<BR>
<BR>
This should put to rest the questions of expertise, quality and availabilit=
y of contributors and reviewers.<BR>
<BR>
Henry<BR>
</FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><BR>
<BR>
On 6/2/09 12:33 PM, &quot;Slava Borilin&quot; &lt;<a href=3D"Borilin@spirit=
dsp.com">Borilin@spiritdsp.com</a>&gt; wrote:<BR>
<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT COLOR=3D"#00=
00FF"><FONT FACE=3D"Arial">I do not beleive the one that will come wil be l=
ow quality.<BR>
at least people from the potential contributors (at least Skype, Speex, SPI=
RIT) are already pretty-good in the commercially exploiting their own codec=
s on the market.<BR>
i think this is probably false alert.<BR>
</FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE=3D"Arial">regards,<BR>
Slava Borilin<BR>
</FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> <BR>
&nbsp;<BR>
<BR>
<HR ALIGN=3DCENTER SIZE=3D"3" WIDTH=3D"100%"></FONT><FONT FACE=3D"Tahoma, V=
erdana, Helvetica, Arial"><B>From:</B> stephen botzko [<a href=3D"mailto:st=
ephen.botzko@gmail.com">mailto:stephen.botzko@gmail.com</a>] <BR>
<B>Sent:</B> Tuesday, June 02, 2009 9:32 PM<BR>
<B>To:</B> Henning Schulzrinne<BR>
<B>Cc:</B> Roni Even; <a href=3D"dispatch@ietf.org">dispatch@ietf.org</a>; =
Jason Fischl; <a href=3D"avt@ietf.org">avt@ietf.org</a>; <a href=3D"hsinnre=
i@adobe.com">hsinnrei@adobe.com</a>; Slava Borilin<BR>
<B>Subject:</B> Re: [AVT] [dispatch] Proposal to form Internet Wideband Aud=
io Codec WG<BR>
</FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><BR>
&gt;&gt;&gt; - the quality of the codec may not be competitive<BR>
<BR>
I think its very important that the codec quality be competitive. &nbsp;Peo=
ple expect excellence from IETF standards &nbsp;Standardizing non-competiti=
ve codecs because they are cheap does not seem to be a good choce.<BR>
<BR>
Steve B.<BR>
<BR>
On Tue, Jun 2, 2009 at 12:15 PM, Henning Schulzrinne &lt;<a href=3D"hgs@cs.=
columbia.edu">hgs@cs.columbia.edu</a>&gt; wrote:<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cali=
bri, Verdana, Helvetica, Arial">I &nbsp;view this as a trade-off. If we pur=
sue this, there are risks:<BR>
<BR>
- nothing &nbsp;may come of it since there are no experts willing to help<B=
R>
- somebody will &nbsp;claim IPR on the resulting work<BR>
- the quality of the codec may not be &nbsp;competitive<BR>
<BR>
However, if we don't do this, we are stuck with the status &nbsp;quo, which=
 is not all that satisfactory. Thus, unless there are significant &nbsp;cos=
ts for &quot;innocent bystanders&quot;, I see this as a risk worth taking. =
In the &nbsp;worst case, we are no worse off than we are today. In all othe=
r cases, we'll &nbsp;have an additional choice for a wideband codec, even i=
f it's not &quot;the best&quot;, &nbsp;just &quot;good enough&quot;. After =
all, most people use G.711 today, which has a really &nbsp;hard time making=
 that claim.<BR>
<BR>
Most real work in the IETF is done by very &nbsp;small teams, typically les=
s than 10, so as long as we have a handful of people &nbsp;that are willing=
 to contribute, this can work. It might even work better, &nbsp;since you m=
ay get fewer people who have half-baked opinions - we may skip the &nbsp;bi=
nary vs. XML debates...<BR>
<BR>
We can set some ground rules (&quot;must be tested &nbsp;with packet loss o=
f 5%&quot;) and then see what happens. Compared to most network &nbsp;proto=
cols, the likely negative impacts (such as security or congestion control &=
nbsp;issues) of even a badly-designed codec are pretty limited.<BR>
<FONT COLOR=3D"#888888"><BR>
Henning</FONT> <BR>
&nbsp;<BR>
&nbsp;<BR>
<BR>
<BR>
On Jun 2, 2009, at 11:57 AM, Roni Even wrote:<BR>
<BR>
&nbsp;<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cali=
bri, Verdana, Helvetica, Arial">Hi,<BR>
I &nbsp;do not want to sound like someone who is for IPR (I am not), but wh=
y &nbsp;stop<BR>
at codec, let's require it for all IETF work. There are IPR on IETF &nbsp;w=
ork<BR>
which is must simpler, in my view, than wide band audio &nbsp;codecs.<BR>
<BR>
I think that we can start with &quot;royalty free&quot; even though I &nbsp=
;am not sure that<BR>
it will accepted as part of the charter of any other &nbsp;work group so wh=
y pick<BR>
on codecs which require more work.<BR>
<BR>
This &nbsp;leaves the other reasons I heard for doing it at the IETF which =
is &nbsp;the<BR>
price of participating (cheaper than being an ITU-T member) and maybe &nbsp=
;design<BR>
less expensive characterization &nbsp;tests.<BR>
<BR>
Roni<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Jean-Marc &nbsp;Valin [<a href=3D"mailto:jean-marc.valin@octasic.com"=
>mailto:jean-marc.valin@octasic.com</a>]<BR>
Sent: Tuesday, June 02, &nbsp;2009 6:14 PM<BR>
To: Roni Even<BR>
Cc: 'Slava Borilin'; <a href=3D"avt@ietf.org">avt@ietf.org</a>; 'Jason Fisc=
hl'; &nbsp;<a href=3D"dispatch@ietf.org">dispatch@ietf.org</a>;<BR>
<a href=3D"hsinnrei@adobe.com">hsinnrei@adobe.com</a><BR>
Subject: Re: [AVT] [dispatch] &nbsp;Proposal to form Internet Wideband Audi=
o Codec<BR>
WG<BR>
<BR>
Hi,<BR>
<BR>
Roni &nbsp;Even wrote:<BR>
&nbsp;<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cali=
bri, Verdana, Helvetica, Arial"><BR>
I &nbsp;am not sure what prevented you from doing it today at the ITU or<BR=
>
MPEG, &nbsp;why do you see the IETF handling it differently.<BR>
<BR>
I would also like &nbsp;to remind you and Jean-Marc that once you are<BR>
bringing work to a &nbsp;standard body it may require collaboration with<BR=
>
other people who will &nbsp;have other proposals that will also address the=
<BR>
same requirements and &nbsp;you may need to invest money in comparative<BR>
testing by independent &nbsp;listening labs.<BR>
<BR>
I also think that you will need to supply the codec &nbsp;in source code an=
d<BR>
provide copy right to the &nbsp;IETF.<BR>
<BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cal=
ibri, Verdana, Helvetica, Arial"><BR>
I am well aware that bringing work to the IETF &nbsp;would require<BR>
collaboration with others. I am not seeking control over &nbsp;the work I a=
m<BR>
currently doing and would really welcome such &nbsp;collaboration. The idea=
 is<BR>
only to have the best wideband codec possible &nbsp;without IPR issues. Giv=
en<BR>
the ITU and MPEG track record, I think it would &nbsp;be very unlikely for =
any<BR>
of those organisations to work on an IPR-free &nbsp;codec.<BR>
<BR>
I also agree with Henry that &quot;the Internet has different &nbsp;criteri=
a than<BR>
ITU-T networks may have&quot;. Internet adoption follows &nbsp;different pa=
tterns<BR>
than adoption in the ITU primary target markets. For &nbsp;example, the<BR>
Internet has more consumer-reconfigurable software, while &nbsp;the ITU has=
 to<BR>
deal with a lot of fixed hardware deployments. At the ITU, &nbsp;it makes<B=
R>
sense to invest large sums of money into testing and &nbsp;characterisation=
 of<BR>
codecs because the codecs deployed there usually stay &nbsp;around for a lo=
ng<BR>
time and the infrastructure investments are usually &nbsp;very large. On th=
e<BR>
other hand, I would say the investments in codecs for &nbsp;the Internet ar=
e<BR>
comparatively smaller and, while testing is still &nbsp;important, it is no=
t<BR>
as critical as it is for the ITU.<BR>
<BR>
It's also a &nbsp;choice one has to make. It is unlikely that companies wou=
ld<BR>
invest money &nbsp;in expensive testing if they are not going to obtain<BR>
royalties in return. &nbsp;However, I think we may be able to define some m=
ore<BR>
lightweight &nbsp;(collaborative?) testing that is sufficient and doesn't<B=
R>
involve as much &nbsp;investments as what the ITU does. For the Internet, I=
<BR>
believe an IPR-free &nbsp;codec that everyone agrees performs well is bette=
r<BR>
than a &nbsp;patent-encumbered codec that has had more extensive testing. T=
his<BR>
is &nbsp;again another difference with the ITU: patent-encumbered codecs te=
nd<BR>
to &nbsp;hurt a lot more on the Internet because many applications (e.g.<BR=
>
giving &nbsp;away the client) are very hard (or impossible) when one has to=
<BR>
pay &nbsp;per-channel royalties.<BR>
<BR>
As for the source code issue you pointed out, &nbsp;all the Xiph codecs are=
<BR>
already published under a very permissive open &nbsp;source license (BSD), =
so<BR>
this would not really change.<BR>
<BR>
&nbsp;&nbsp;&nbsp;Jean-Marc<BR>
<BR>
&nbsp;<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cali=
bri, Verdana, Helvetica, Arial">Roni<BR>
<BR>
<BR>
<BR>
*From:* &nbsp;<a href=3D"avt-bounces@ietf.org">avt-bounces@ietf.org</a> [<a=
 href=3D"mailto:avt-bounces@ietf.org">mailto:avt-bounces@ietf.org</a>] &nbs=
p;*On Behalf<BR>
Of *Slava Borilin<BR>
*Sent:* Monday, June 01, 2009 11:50 &nbsp;PM<BR>
*To:* <a href=3D"jean-marc.valin@octasic.com">jean-marc.valin@octasic.com</=
a><BR>
*Cc:* <a href=3D"avt@ietf.org">avt@ietf.org</a>; Jason &nbsp;Fischl<BR>
*Subject:* Re: [AVT] [dispatch] Proposal to form Internet &nbsp;Wideband<BR=
>
Audio Codec WG<BR>
<BR>
<BR>
<BR>
Agree with Jean-Marc.<BR>
SPIRIT &nbsp;is interested to contribute as well - having a dozen of &nbsp;=
proprietary<BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cal=
ibri, Verdana, Helvetica, Arial">codecs developed, including<BR>
&nbsp;<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cali=
bri, Verdana, Helvetica, Arial">one &nbsp;specifically desgined for interne=
t (SPIRIT IP-MR, which is now &nbsp;under<BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cal=
ibri, Verdana, Helvetica, Arial">WGLC on draft-ietf-avt-rtp-ipmr-04) -<BR>
&nbsp;<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cali=
bri, Verdana, Helvetica, Arial">multi-rate, &nbsp;scalable, adaptive, wideb=
and codec.<BR>
<BR>
We can also continue this work &nbsp;with IETF.<BR>
<BR>
Moreover, most if not all efforts coming from ITU on &nbsp;codecs unfortuna=
tely<BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cal=
ibri, Verdana, Helvetica, Arial">are NOT really focused on<BR>
&nbsp;<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cali=
bri, Verdana, Helvetica, Arial">internet-specific &nbsp;codecs (that's why =
several companies have had to invent)<BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cal=
ibri, Verdana, Helvetica, Arial">- &nbsp;as ITU preference is mainly<BR>
&nbsp;<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cali=
bri, Verdana, Helvetica, Arial">specific &nbsp;(i.e. cellular) networks at =
first.<BR>
<BR>
however, as we see the greant &nbsp;rise of pure &quot;internet-basd commun=
ications&quot;<BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cal=
ibri, Verdana, Helvetica, Arial">(skype, &nbsp;webex/citrix, and many other=
s) -<BR>
&nbsp;<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cali=
bri, Verdana, Helvetica, Arial">we &nbsp;all (and users) are suffering from=
 inefficiency in all &nbsp;currently<BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cal=
ibri, Verdana, Helvetica, Arial">&quot;standard&quot; codecs and ambiguity =
in the choice &nbsp;of<BR>
&nbsp;<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cali=
bri, Verdana, Helvetica, Arial">internet-targeted &nbsp;ones.<BR>
<BR>
Again, we probably can put together enough number of &nbsp;contributors to =
the<BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cal=
ibri, Verdana, Helvetica, Arial">WG to have the expertise.<BR>
&nbsp;<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cali=
bri, Verdana, Helvetica, Arial"><BR>
regards,<BR>
Slava &nbsp;Borilin<BR>
<BR>
--<BR>
John Lazzaro wrote:<BR>
<BR>
&nbsp;&nbsp;A traditional &nbsp;response to this type of request is to note=
 that the<BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cal=
ibri, Verdana, Helvetica, Arial">IETF<BR>
&nbsp;<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cali=
bri, Verdana, Helvetica, Arial"><BR>
&nbsp;&nbsp;&nbsp;really doesn't have much in the way of expertise in audio=
 &nbsp;codec<BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cal=
ibri, Verdana, Helvetica, Arial">design.<BR>
&nbsp;<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cali=
bri, Verdana, Helvetica, Arial"><BR>
&nbsp;&nbsp;&nbsp;I don't see many of the regulars who present at the AES c=
odec &nbsp;paper<BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cal=
ibri, Verdana, Helvetica, Arial">sessions<BR>
&nbsp;<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cali=
bri, Verdana, Helvetica, Arial"><BR>
&nbsp;&nbsp;&nbsp;posting here on AVT (ditto ICASSP paper sessions for voic=
e &nbsp;codecs).<BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cal=
ibri, Verdana, Helvetica, Arial">It's<BR>
&nbsp;<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cali=
bri, Verdana, Helvetica, Arial"><BR>
&nbsp;&nbsp;&nbsp;a full-time job to keep up-to-date and contribute to that=
<BR>
<BR>
&nbsp;&nbsp;&nbsp;signal-processing lore.<BR>
<BR>
<BR>
<BR>
Well, there's no reason that the &nbsp;IETF cannot build such an expertise<=
BR>
in audio codecs. This is actually &nbsp;something in which I'd be intereste=
d<BR>
in getting involved and I'm sure &nbsp;others at Xiph.Org would be<BR>
interested as well. We have several people &nbsp;with audio codec expertise=
<BR>
from working on Vorbis, Speex and (more &nbsp;recently) CELT. It turns out<=
BR>
that the CELT codec currently under &nbsp;development at Xiph actually meet=
s<BR>
most of the requirements from the &nbsp;original proposal in being a very<B=
R>
low delay codec with adaptive &nbsp;bit-rate and sampling rate (up to 48<BR=
>
kHz), scalable complexity, and &nbsp;good robustness to packet loss. We'd b=
e<BR>
willing to continue the &nbsp;development with the IETF. Even if not with<B=
R>
CELT, it's still like to be &nbsp;involved in such a new &nbsp;WG.<BR>
<BR>
Cheers,<BR>
<BR>
&nbsp;Jean-Marc<BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cal=
ibri, Verdana, Helvetica, Arial"><BR>
_______________________________________________<BR>
Audio/Video &nbsp;Transport Working Group<BR>
<a href=3D"avt@ietf.org">avt@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt">https://www.ietf.org/=
mailman/listinfo/avt</a><BR>
<BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cal=
ibri, Verdana, Helvetica, Arial"><BR>
_______________________________________________<BR>
Audio/Video &nbsp;Transport Working Group<BR>
<a href=3D"avt@ietf.org">avt@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt">https://www.ietf.org/=
mailman/listinfo/avt</a><BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:18pt'><FONT FACE=3D"Cal=
ibri, Verdana, Helvetica, Arial"><BR>
<BR>
</FONT></SPAN></BLOCKQUOTE>
</BODY>
</HTML>


--_000_C64AE35E3E6Ehsinnreiadobecom_--

From john.lazzaro@gmail.com  Tue Jun  2 13:02:11 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 9C5403A67ED for <avt@core3.amsl.com>; Tue,  2 Jun 2009 13:02:11 -0700 (PDT)
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 ys9sREnjkwKa for <avt@core3.amsl.com>; Tue,  2 Jun 2009 13:02:10 -0700 (PDT)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by core3.amsl.com (Postfix) with ESMTP id 1209528C1FF for <avt@ietf.org>; Tue,  2 Jun 2009 13:02:08 -0700 (PDT)
Received: by yw-out-2324.google.com with SMTP id 3so8656809ywj.49 for <avt@ietf.org>; Tue, 02 Jun 2009 13:02:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=b1UiLF5w+QFFIeaTPicAHje9LED9EZ+nC4ihlOrZLKA=; b=wsrts6dM5cNLjc1wEbs0d/1ZpvbSIVvuW1zW6FTRz5c6pebde4odVwPJPP2eJV8Wi7 dIpvefMfrZNJvB5RADidd2aQDy95OGvPf9l1N3AuE9ksGvWu7g4nl/F+k4dLNDg6LaCf pZfGU6yZt+f0yTIdpq2Wn8g+lynI8+26CINdU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=BqCef0leYFvbcsLlnJVALB+BABU94vp3OSSS72tY14nYJyR0as0uP6GKGJic/FRRld cRUGnPDcnsNs/LE1Fos9djyA+Kwb+WRdxVBwafx9qKcSkXDTm34e/Aal8wVpS7Isxvgu wvQUfCmLUo6937FDtY+29nPUYuebNO2NqLdOM=
MIME-Version: 1.0
Received: by 10.100.131.13 with SMTP id e13mr157983and.93.1243972926289; Tue,  02 Jun 2009 13:02:06 -0700 (PDT)
In-Reply-To: <p062408a9c64b2c6dc94c@10.0.1.8>
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <ybu7hzu7kf2.fsf@jesup.eng.wgate.com> <p062408a4c64b2024e818@10.0.1.8> <302f570906021207g627bf70cmf6685124ad1df13@mail.gmail.com> <p062408a9c64b2c6dc94c@10.0.1.8>
Date: Tue, 2 Jun 2009 13:02:04 -0700
Message-ID: <302f570906021302i73b8f233ydc0991dad42abaee@mail.gmail.com>
From: John Lazzaro <john.lazzaro@gmail.com>
To: David Singer <singer@apple.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: avt@ietf.org
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 02 Jun 2009 20:02:11 -0000

On Tue, Jun 2, 2009 at 12:24 PM, David Singer<singer@apple.com> wrote:
> On the other hand, the costs of paying for the time to
> * write the specification
> * write the conformance suite
> * write the reference software
>
> dwarf the costs of attendance at meetings. =A0RFC 4695 is a nice piece of
> work, but it's not a codec.


In my case, the MIDI equivalent to the above were all done pro-bono by me.
I spent a few years teaching undergraduate classes to earn a salary so
I could finish the RFCs ... And I don't think I'm unique in this regard, so=
me
of the academic IETF contributions are funded by grants from WG acceptance
to RFC issuance, but many of them run on donated author time for at least
part of the process (in my case, the first few years were funded by a Cal
Micro grant).

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

From Borilin@spiritdsp.com  Tue Jun  2 13:28:24 2009
Return-Path: <Borilin@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 B13A63A6E03; Tue,  2 Jun 2009 13:28:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.47
X-Spam-Level: 
X-Spam-Status: No, score=-0.47 tagged_above=-999 required=5 tests=[AWL=-0.326,  BAYES_00=-2.599, FRT_ADOBE2=2.455]
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 VCG4aWOB9mD3; Tue,  2 Jun 2009 13:28:24 -0700 (PDT)
Received: from mail3.spiritcorp.com (mail3.spiritcorp.com [85.13.194.167]) by core3.amsl.com (Postfix) with ESMTP id BD7C03A6D90; Tue,  2 Jun 2009 13:28:23 -0700 (PDT)
Received: from mail-srv.spiritcorp.com (mail-srv.spiritcorp.com [192.168.125.3]) by mail3.spiritcorp.com (8.13.8/8.14.3) with SMTP id n52KRqZe070405; Wed, 3 Jun 2009 00:27:52 +0400 (MSD) (envelope-from Borilin@spiritdsp.com)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Wed, 3 Jun 2009 00:27:45 +0400
Message-ID: <AA5A65FC22B6F145830AC0EAC7586A6C04BF90B8@mail-srv.spiritcorp.com>
In-Reply-To: <p062408a5c64b21091de5@[10.0.1.8]>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec	WG
Thread-Index: AcnjsU5SS3xT32TWQ8uT5QDgSonGngADwutQ
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <4A2541B9.2000805@octasic.com> <00d501c9e39a$dcbbbe50$96333af0$%roni@huawei.com> <D1611ACB-4739-4A65-94F0-403FC24CDC43@cs.columbia.edu> <6e9223710906021031i31e024dam5673ca9608017d73@mail.gmail.com> <2B4B0335-916C-4CD4-9E40-63BBA6B1DF8B@cs.columbia.edu> <p062408a5c64b21091de5@[10.0.1.8]>
From: "Slava Borilin" <Borilin@spiritdsp.com>
To: "David Singer" <singer@apple.com>, "Henning Schulzrinne" <hgs@cs.columbia.edu>, "stephen botzko" <stephen.botzko@gmail.com>
X-Scanned-By: MIMEDefang 2.64 on 192.168.125.15
Cc: hsinnrei@adobe.com, dispatch@ietf.org, avt@ietf.org, Roni Even <Even.roni@huawei.com>, Jason Fischl <jason.fischl@skype.net>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec	WG
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, 02 Jun 2009 20:28:24 -0000

David-

SA4 is definitely the option, but they are focused, again, on LTE only,
around EVRC family, so they has a differetnt roots and different agendas
from IETF now.

regards,
Slava Borilin
=20

-----Original Message-----
From: David Singer [mailto:singer@apple.com]=20
Sent: Tuesday, June 02, 2009 10:37 PM
To: Henning Schulzrinne; stephen botzko
Cc: dispatch@ietf.org; Jason Fischl; avt@ietf.org; Roni Even;
hsinnrei@adobe.com; Slava Borilin
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio
Codec WG

It would also be hard to 'object' to transport work being done in
traditional 'codec shops' (such as the ITU and MPEG) if this goes ahead.

A quality codec standard is usually backed by
* testing
* conformance files
* reference software

and a fairly rigorous design process.  When SMPTE took on VC-1 from
Microsoft, I think both they and Microsoft were surprised by the amount
of work involved.

FWIW, 3GPP SA4 is also a place with interest in codecs for packet
networks, and has standardized codecs in the past.  Opening a new work
item there is not trivial, but can be done.
--
David Singer
Multimedia Standards, Apple Inc.

From pete.mccann@motorola.com  Tue Jun  2 14:22:39 2009
Return-Path: <pete.mccann@motorola.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 D4C9C3A683F; Tue,  2 Jun 2009 14:22:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_14=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 kGg3fCztmSaO; Tue,  2 Jun 2009 14:22:38 -0700 (PDT)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by core3.amsl.com (Postfix) with ESMTP id A234F3A681F; Tue,  2 Jun 2009 14:22:38 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: pete.mccann@motorola.com
X-Msg-Ref: server-4.tower-119.messagelabs.com!1243977756!35317255!1
X-StarScan-Version: 6.0.0; banners=-,-,-
X-Originating-IP: [136.182.1.13]
Received: (qmail 32232 invoked from network); 2 Jun 2009 21:22:36 -0000
Received: from motgate3.mot.com (HELO motgate3.mot.com) (136.182.1.13) by server-4.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Jun 2009 21:22:36 -0000
Received: from il27exr03.cig.mot.com (il27exr03.mot.com [10.17.196.72]) by motgate3.mot.com (8.14.3/8.14.3) with ESMTP id n52LMaQE020383; Tue, 2 Jun 2009 14:22:36 -0700 (MST)
Received: from il27vts02.mot.com (il27vts02.cig.mot.com [10.17.196.86]) by il27exr03.cig.mot.com (8.13.1/Vontu) with SMTP id n52LMZpR010673; Tue, 2 Jun 2009 16:22:35 -0500 (CDT)
Received: from de01exm70.ds.mot.com (de01exm70.am.mot.com [10.176.8.26]) by il27exr03.cig.mot.com (8.13.1/8.13.0) with ESMTP id n52LMZw0010670;  Tue, 2 Jun 2009 16:22:35 -0500 (CDT)
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, 2 Jun 2009 17:22:13 -0400
Message-ID: <274D46DDEB9F2244B2F1EA66B3FF54BC05290DC3@de01exm70.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Gen-ART review of draft-ietf-avt-rtp-mps-02
thread-index: AcnjyDKHGmANVDz0QseGPoUjnVauyw==
From: "McCann Peter-A001034" <pete.mccann@motorola.com>
To: <gen-art@ietf.org>, <draft-ietf-avt-rtp-mps.all@tools.ietf.org>, <avt@ietf.org>
X-CFilter-Loop: Reflected
Subject: [AVT] Gen-ART review of draft-ietf-avt-rtp-mps-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: Tue, 02 Jun 2009 21:22:39 -0000

I have been selected as the General Area Review Team (Gen-ART) reviewer
for this draft (for background on Gen-ART, please see
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html
<http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html> ).=20

Please resolve these comments along with any other Last Call comments
you may receive.=20

Document: draft-ietf-avt-rtp-mps-02
Reviewer: Pete McCann
Review Date: 2 June 2009
IETF LC End Date: 2 June 2009
IESG Telechat date: unknown=20

Summary: Ready for publication as a Proposed Standard.

Major issues:=20

Minor issues:=20

Section 4.1:
   Note that the a=3Dfmtp lines of the example above have been wrapped =
to
   fit the page; they comprise each a single line in the SDP file.
There is only one a=3Dfmtp line, your wording here seems to apply to=20
each of the broken-up lines.  Suggest changing to singular:
   Note that the a=3Dfmtp line of the example above has been wrapped to
   fit the page; it would comprise a single line in the SDP file.

Nits/editorial comments:

From Even.roni@huawei.com  Wed Jun  3 02:57:27 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 79C2F3A6A8E for <avt@core3.amsl.com>; Wed,  3 Jun 2009 02:57:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.021
X-Spam-Level: 
X-Spam-Status: No, score=-1.021 tagged_above=-999 required=5 tests=[AWL=-0.526, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 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 CE3N07RjhY2a for <avt@core3.amsl.com>; Wed,  3 Jun 2009 02:57:26 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 786E13A68FA for <avt@ietf.org>; Wed,  3 Jun 2009 02:57:26 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KKN00GZSQ4OGT@szxga01-in.huawei.com> for avt@ietf.org; Wed, 03 Jun 2009 17:53:12 +0800 (CST)
Received: from huawei.com ([172.24.1.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KKN008BYQ4O5V@szxga01-in.huawei.com> for avt@ietf.org; Wed, 03 Jun 2009 17:53:12 +0800 (CST)
Received: from windows8d787f9 (bzq-79-183-125-11.red.bezeqint.net [79.183.125.11]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KKN00JZ8Q4DT6@szxml01-in.huawei.com>; Wed, 03 Jun 2009 17:53:12 +0800 (CST)
Date: Wed, 03 Jun 2009 12:52:03 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <81B9B88E2F9D574AA5328A85547CDE91014FFAE5@xmb-rtp-21d.amer.cisco.com>
To: "'Bill Ver Steeg (versteb)'" <versteb@cisco.com>, avt@ietf.org
Message-id: <01c701c9e430$ff5f7960$fe1e6c20$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcnS4FBFJRh0kTNdSKKujynDJmWrDwAJMQ/AAC+GL9AAAGUFAAAXW2jQAA+eDnAASHsCkALEQgYwAIvU5CAAOrRN4AAgVN0Q
References: <fa05fd7ad709f.d709ffa05fd7a@huawei.com> <81B9B88E2F9D574AA5328A85547CDE91013038E4@xmb-rtp-21d.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE9101303DA5@xmb-rtp-21d.amer.cisco.com> <00dc01c9d3c5$7a323aa0$6e96afe0$%roni@huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D54094C3DBF@xmb-sjc-215.amer.cisco.com> <000a01c9d461$813bdcb0$83b39610$%roni@huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D540954DB8A@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE9101495636@xmb-rtp-21d.amer.cisco.com> <011701c9e2c3$6a75b990$3f612cb0$%roni@huawei.com> <81B9B88E2F9D574AA5328A85547CDE91014FFAE5@xmb-rtp-21d.amer.cisco.com>
Subject: Re: [AVT] Calling for comments on changes to RAMS draft 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/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, 03 Jun 2009 09:57:27 -0000

Hi Bill,
I looked at the diff file, the content looks fine to me. The changes in
section 7 about the extensions (adding 7.1.1) were not clear editorially so
I will review the section after you submit the new draft.

Do you intend also to start working on the NAT traversal section and add
clarification to the SDP example based on the email thread with Jose Rey.

Regards
Roni

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Bill
Ver Steeg (versteb)
Sent: Tuesday, June 02, 2009 9:14 PM
To: Roni Even; avt@ietf.org
Subject: Re: [AVT] Calling for comments on changes to RAMS draft 00

Roni-

Yes, we plan to add all of the comments from the diff. I will be sure to
update the "subject line" when we do.

Bvs
 

-----Original Message-----
From: Roni Even [mailto:Even.roni@huawei.com] 
Sent: Monday, June 01, 2009 10:15 AM
To: Bill Ver Steeg (versteb); avt@ietf.org
Subject: Calling for comments on changes to RAMS draft 00

Bill,
Are you going to add all the comments from the rdiff.

Also please send this email not under the above subject since it does
not describe the purpose of the email

Roni

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Bill Ver Steeg (versteb)
Sent: Friday, May 29, 2009 10:40 PM
To: avt@ietf.org
Subject: Re: [AVT] Adopting Rapid Acquisition of Multicast RTP
Sessions(RAMS) as a working group item

Fellow AVT folks-

We are continuing to solicit comments on the RAMS design points
identified in Ali's email from May 15 (diff enclosed). We have received
some valuable feedback. We hope to have a new draft mid next week, and
will incorporate comments that we receive through Monday or Tuesday in
that draft.

Thanks in advance



Bill VerSteeg

-----Original Message-----
From: Ali C. Begen (abegen)
Sent: Friday, May 15, 2009 1:32 PM
To: Roni Even; Bill Ver Steeg (versteb); avt@ietf.org
Subject: RE: [AVT] Adopting Rapid Acquisition of Multicast RTP
Sessions(RAMS) as a working group item

Hi Roni, All,

Here is a diff for sections 7 and 13. 

Comments are welcome.
-acbegen

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


From versteb@cisco.com  Wed Jun  3 07:59:01 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 191683A67D8 for <avt@core3.amsl.com>; Wed,  3 Jun 2009 07:59:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.832
X-Spam-Level: 
X-Spam-Status: No, score=-6.832 tagged_above=-999 required=5 tests=[AWL=-0.233, 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 RHqAAW6H12IB for <avt@core3.amsl.com>; Wed,  3 Jun 2009 07:59:00 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id BA07C3A6778 for <avt@ietf.org>; Wed,  3 Jun 2009 07:58:59 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.41,299,1241395200"; d="scan'208";a="46135330"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 03 Jun 2009 14:59:00 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n53Ex0T4000776;  Wed, 3 Jun 2009 10:59:00 -0400
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 n53Ex0DQ015249; Wed, 3 Jun 2009 14:59:00 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);  Wed, 3 Jun 2009 10:59:00 -0400
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: Wed, 3 Jun 2009 10:58:59 -0400
Message-ID: <81B9B88E2F9D574AA5328A85547CDE910154B981@xmb-rtp-21d.amer.cisco.com>
In-Reply-To: <01c701c9e430$ff5f7960$fe1e6c20$%roni@huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Calling for comments on changes to RAMS draft 00
Thread-Index: AcnS4FBFJRh0kTNdSKKujynDJmWrDwAJMQ/AAC+GL9AAAGUFAAAXW2jQAA+eDnAASHsCkALEQgYwAIvU5CAAOrRN4AAgVN0QAArx1NA=
References: <fa05fd7ad709f.d709ffa05fd7a@huawei.com> <81B9B88E2F9D574AA5328A85547CDE91013038E4@xmb-rtp-21d.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE9101303DA5@xmb-rtp-21d.amer.cisco.com> <00dc01c9d3c5$7a323aa0$6e96afe0$%roni@huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D54094C3DBF@xmb-sjc-215.amer.cisco.com> <000a01c9d461$813bdcb0$83b39610$%roni@huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D540954DB8A@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE9101495636@xmb-rtp-21d.amer.cisco.com> <011701c9e2c3$6a75b990$3f612cb0$%roni@huawei.com> <81B9B88E2F9D574AA5328A85547CDE91014FFAE5@xmb-rtp-21d.amer.cisco.com> <01c701c9e430$ff5f7960$fe1e6c20$%roni@huawei.com>
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "Roni Even" <Even.roni@huawei.com>, <avt@ietf.org>
X-OriginalArrivalTime: 03 Jun 2009 14:59:00.0592 (UTC) FILETIME=[D3F42700:01C9E45B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3075; t=1244041140; x=1244905140; c=relaxed/simple; s=rtpdkim1001; 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=20[AVT]=20Calling=20for=20comments=20on=2 0changes=20to=20RAMS=20draft=2000 |Sender:=20 |To:=20=22Roni=20Even=22=20<Even.roni@huawei.com>,=20<avt@i etf.org>; bh=9BkD+qqCkY4m2msGd9BmpnPMJcGKF63/pDXGieGvosE=; b=MPrvzfT+KwvaxWq1y3fYIDLMNcCW7m3+V4Jsj1bzseUnbVCHRB6Ug55xbT CPCj38WBxnqNO8GxfLSaJ1PcMQrxzyQgLCvaxpXbU0AM7CSQp+UglaOiNv95 CDe1iZElC7;
Authentication-Results: rtp-dkim-1; header.From=versteb@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; ); 
Subject: Re: [AVT] Calling for comments on changes to RAMS draft 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/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, 03 Jun 2009 14:59:01 -0000

We definitely are working on NAT and SDP. We have been searching for
innovative NAT solutions, but I think we are realizing that this is
well-trodden ground. The NAT section will lay out how the normal NAT
methods apply to the RAMS transactions. There is some subtlety around
how the port number that the RAMS-R transactions goes to, as well as
some interaction with RTP/RTCP muxing. We will try expose these points
in enough detail to avoid the common pitfalls around port usage.

Bill VerSteeg
=20

-----Original Message-----
From: Roni Even [mailto:Even.roni@huawei.com]=20
Sent: Wednesday, June 03, 2009 5:52 AM
To: Bill Ver Steeg (versteb); avt@ietf.org
Subject: RE: [AVT] Calling for comments on changes to RAMS draft 00

Hi Bill,
I looked at the diff file, the content looks fine to me. The changes in
section 7 about the extensions (adding 7.1.1) were not clear editorially
so I will review the section after you submit the new draft.

Do you intend also to start working on the NAT traversal section and add
clarification to the SDP example based on the email thread with Jose
Rey.

Regards
Roni

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Bill Ver Steeg (versteb)
Sent: Tuesday, June 02, 2009 9:14 PM
To: Roni Even; avt@ietf.org
Subject: Re: [AVT] Calling for comments on changes to RAMS draft 00

Roni-

Yes, we plan to add all of the comments from the diff. I will be sure to
update the "subject line" when we do.

Bvs
=20

-----Original Message-----
From: Roni Even [mailto:Even.roni@huawei.com]
Sent: Monday, June 01, 2009 10:15 AM
To: Bill Ver Steeg (versteb); avt@ietf.org
Subject: Calling for comments on changes to RAMS draft 00

Bill,
Are you going to add all the comments from the rdiff.

Also please send this email not under the above subject since it does
not describe the purpose of the email

Roni

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Bill Ver Steeg (versteb)
Sent: Friday, May 29, 2009 10:40 PM
To: avt@ietf.org
Subject: Re: [AVT] Adopting Rapid Acquisition of Multicast RTP
Sessions(RAMS) as a working group item

Fellow AVT folks-

We are continuing to solicit comments on the RAMS design points
identified in Ali's email from May 15 (diff enclosed). We have received
some valuable feedback. We hope to have a new draft mid next week, and
will incorporate comments that we receive through Monday or Tuesday in
that draft.

Thanks in advance



Bill VerSteeg

-----Original Message-----
From: Ali C. Begen (abegen)
Sent: Friday, May 15, 2009 1:32 PM
To: Roni Even; Bill Ver Steeg (versteb); avt@ietf.org
Subject: RE: [AVT] Adopting Rapid Acquisition of Multicast RTP
Sessions(RAMS) as a working group item

Hi Roni, All,

Here is a diff for sections 7 and 13.=20

Comments are welcome.
-acbegen

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


From eburger@standardstrack.com  Tue Jun  2 18:50:37 2009
Return-Path: <eburger@standardstrack.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 473E33A6A80; Tue,  2 Jun 2009 18:50:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.222
X-Spam-Level: 
X-Spam-Status: No, score=-0.222 tagged_above=-999 required=5 tests=[AWL=-2.377, BAYES_00=-2.599, FRT_ADOBE2=2.455, MANGLED_INXPNS=2.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 6-NZ5ewKEryq; Tue,  2 Jun 2009 18:50:35 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19.inmotionhosting.com [205.134.252.251]) by core3.amsl.com (Postfix) with ESMTP id C16FB3A6850; Tue,  2 Jun 2009 18:50:35 -0700 (PDT)
Received: from [12.46.252.162] (helo=[172.17.136.184]) by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1MBfcX-000621-My; Tue, 02 Jun 2009 18:50:26 -0700
Message-Id: <A4C3A5AB-BC7B-4864-BBA5-23C9B227FCCB@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: Henry Sinnreich <hsinnrei@adobe.com>
In-Reply-To: <E0F5850494F549508152266797943F87@china.huawei.com>
Content-Type: multipart/signed; boundary=Apple-Mail-334--601341967; micalg=sha1; protocol="application/pkcs7-signature"
Mime-Version: 1.0 (Apple Message framework v935.3)
X-Priority: 3
Date: Tue, 2 Jun 2009 21:50:30 -0400
References: <C64AB99A.3E55%hsinnrei@adobe.com> <E0F5850494F549508152266797943F87@china.huawei.com>
X-Mailer: Apple Mail (2.935.3)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Mailman-Approved-At: Wed, 03 Jun 2009 08:50:06 -0700
Cc: dispatch@ietf.org, avt@ietf.org
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 03 Jun 2009 01:50:37 -0000

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

To directly answer Henry, having a mail list and the initial (and  
possibly detailed) discussion hosted at the IETF costs less than the  
discussion we are having here.  If a codec comes out of it, without  
having a BOF or WG, that's great!  If not, at least there was a forum  
for doing it.

I can also offer a SIP Forum list if people still really, really don't  
like the idea of even discussing the topic under even the most  
faintest of auspices of the IETF.

If you think I am schizophrenic by offering we can have a discussion  
in the IETF and at the same time I doubt we could ever have a formal  
work group to create the codec, you would be only slightly  
correct :-)  But seriously: the IETF (AVT in particular) can pickup  
the wire format for a codec, once the codec exists. Having a mail list  
WITHOUT A WORK GROUP give people who want to work on this a venue to  
do the work, without burdening the AD's, IESG, and the rest of the  
community. If a codec pops out, then we can run with it.

On Jun 2, 2009, at 12:44 PM, Spencer Dawkins wrote:

> I am not an area director, nor do i play one on IPTV, but my  
> suggestion for anyone interested would be to
>
> - request a non-WG mailing list (from either of the RAI area  
> directors),
>
> - announce it on this mailing list (and others that seem to be  
> appropriate, and
>
> - start discussions, which the area directors typically look at when  
> judging whether there's enough interest and enough clue to justify  
> approving a BOF and/or chartering a working group.
>
> I didn't see a mailing list included in Jason's proposal - if I  
> missed one, my apologies.
>
> If people at the IETF can do this work, and want to do this work,  
> IETF process policies should not get in the way of that happening.
>
> And I haven't heard of an AD turning down a request for a non-WG  
> mailing list yet, keeping in mind that one of said lists is ietf- 
> sailors, for people interested in sailing to/from/at IETF meetings -  
> the bar is (appropriately) low.
>
> Thanks,
>
> Spencer
> ----- Original Message -----
> From: Henry Sinnreich
> To: Roni Even ; Jean-Marc Valin
> Cc: dispatch@ietf.org ; Slava Borilin ; avt@ietf.org
> Sent: Tuesday, June 02, 2009 11:12 AM
> Subject: Re: [dispatch] [AVT] Proposal to form Internet Wideband  
> Audio Codec WG
>
> >This leaves the other reasons I heard for doing it at the IETF  
> which is the
> >price of participating
>
> This is an important point.
> Given the travel constraints for some of the most valuable potential  
> contributors and reviewers, could we envisage online work until the  
> economy improves, so that an eventual BOF to start with should not  
> be starved of attendees? An online BOF?
>
> There are several free online meeting tools available...
>
> How can this be done within the IETF policy?
>
> Henry
>
>
> On 6/2/09 10:57 AM, "Roni Even" <Even.roni@huawei.com> wrote:
>
> Hi,
> I do not want to sound like someone who is for IPR (I am not), but  
> why stop
> at codec, let's require it for all IETF work. There are IPR on IETF  
> work
> which is must simpler, in my view, than wide band audio codecs.
>
> I think that we can start with "royalty free" even though I am not  
> sure that
> it will accepted as part of the charter of any other work group so  
> why pick
> on codecs which require more work.
>
> This leaves the other reasons I heard for doing it at the IETF which  
> is the
> price of participating (cheaper than being an ITU-T member) and  
> maybe design
> less expensive characterization tests.
>
> Roni
>
>
> -----Original Message-----
> From: Jean-Marc Valin [mailto:jean-marc.valin@octasic.com]
> Sent: Tuesday, June 02, 2009 6:14 PM
> To: Roni Even
> Cc: 'Slava Borilin'; avt@ietf.org; 'Jason Fischl';dispatch@ietf.org;
> hsinnrei@adobe.com
> Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband  
> Audio Codec
> WG
>
> Hi,
>
> Roni Even wrote:
> >
> > I am not sure what prevented you from doing it today at the ITU or
> > MPEG, why do you see the IETF handling it differently.
> >
> > I would also like to remind you and Jean-Marc that once you are
> > bringing work to a standard body it may require collaboration with
> > other people who will have other proposals that will also address  
> the
> > same requirements and you may need to invest money in comparative
> > testing by independent listening labs.
> >
> > I also think that you will need to supply the codec in source code  
> and
> > provide copy right to the IETF.
> >
>
> I am well aware that bringing work to the IETF would require
> collaboration with others. I am not seeking control over the work I am
> currently doing and would really welcome such collaboration. The  
> idea is
> only to have the best wideband codec possible without IPR issues.  
> Given
> the ITU and MPEG track record, I think it would be very unlikely for  
> any
> of those organisations to work on an IPR-free codec.
>
> I also agree with Henry that "the Internet has different criteria than
> ITU-T networks may have". Internet adoption follows different patterns
> than adoption in the ITU primary target markets. For example, the
> Internet has more consumer-reconfigurable software, while the ITU  
> has to
> deal with a lot of fixed hardware deployments. At the ITU, it makes
> sense to invest large sums of money into testing and  
> characterisation of
> codecs because the codecs deployed there usually stay around for a  
> long
> time and the infrastructure investments are usually very large. On the
> other hand, I would say the investments in codecs for the Internet are
> comparatively smaller and, while testing is still important, it is not
> as critical as it is for the ITU.
>
> It's also a choice one has to make. It is unlikely that companies  
> would
> invest money in expensive testing if they are not going to obtain
> royalties in return. However, I think we may be able to define some  
> more
> lightweight (collaborative?) testing that is sufficient and doesn't
> involve as much investments as what the ITU does. For the Internet, I
> believe an IPR-free codec that everyone agrees performs well is better
> than a patent-encumbered codec that has had more extensive testing.  
> This
> is again another difference with the ITU: patent-encumbered codecs  
> tend
> to hurt a lot more on the Internet because many applications (e.g.
> giving away the client) are very hard (or impossible) when one has to
> pay per-channel royalties.
>
> As for the source code issue you pointed out, all the Xiph codecs are
> already published under a very permissive open source license (BSD),  
> so
> this would not really change.
>
>     Jean-Marc
>
> > Roni
> >
> >
> >
> > *From:* avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] *On  
> Behalf
> > Of *Slava Borilin
> > *Sent:* Monday, June 01, 2009 11:50 PM
> > *To:* jean-marc.valin@octasic.com
> > *Cc:* avt@ietf.org; Jason Fischl
> > *Subject:* Re: [AVT] [dispatch] Proposal to form Internet Wideband
> > Audio Codec WG
> >
> >
> >
> > Agree with Jean-Marc.
> > SPIRIT is interested to contribute as well - having a dozen of  
> proprietary
> codecs developed, including
> > one specifically desgined for internet (SPIRIT IP-MR, which is now  
> under
> WGLC on draft-ietf-avt-rtp-ipmr-04) -
> > multi-rate, scalable, adaptive, wideband codec.
> >
> > We can also continue this work with IETF.
> >
> > Moreover, most if not all efforts coming from ITU on codecs  
> unfortunately
> are NOT really focused on
> > internet-specific codecs (that's why several companies have had to  
> invent)
> - as ITU preference is mainly
> > specific (i.e. cellular) networks at first.
> >
> > however, as we see the greant rise of pure "internet-basd  
> communications"
> (skype, webex/citrix, and many others) -
> > we all (and users) are suffering from inefficiency in all currently
> "standard" codecs and ambiguity in the choice of
> > internet-targeted ones.
> >
> > Again, we probably can put together enough number of contributors  
> to the
> WG to have the expertise.
> >
> > regards,
> > Slava Borilin
> >
> > --
> > John Lazzaro wrote:
> >
> >     A traditional response to this type of request is to note that  
> the
> IETF
> >
> >     really doesn't have much in the way of expertise in audio codec
> design.
> >
> >     I don't see many of the regulars who present at the AES codec  
> paper
> sessions
> >
> >     posting here on AVT (ditto ICASSP paper sessions for voice  
> codecs).
> It's
> >
> >     a full-time job to keep up-to-date and contribute to that
> >
> >     signal-processing lore.
> >
> >
> >
> > Well, there's no reason that the IETF cannot build such an expertise
> > in audio codecs. This is actually something in which I'd be  
> interested
> > in getting involved and I'm sure others at Xiph.Org would be
> > interested as well. We have several people with audio codec  
> expertise
> > from working on Vorbis, Speex and (more recently) CELT. It turns out
> > that the CELT codec currently under development at Xiph actually  
> meets
> > most of the requirements from the original proposal in being a very
> > low delay codec with adaptive bit-rate and sampling rate (up to 48
> > kHz), scalable complexity, and good robustness to packet loss.  
> We'd be
> > willing to continue the development with the IETF. Even if not with
> > CELT, it's still like to be involved in such a new WG.
> >
> > Cheers,
> >
> >    Jean-Marc
>
>
>
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch


--Apple-Mail-334--601341967
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGPTCCBjkw
ggUhoAMCAQICEC+VK1RLWxrF8KJZDR9k8p8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVT
MQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VS
VFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQD
Ey1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwODEz
MDAwMDAwWhcNMDkwODEzMjM1OTU5WjCB4TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsg
LSBQRVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m
IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMg
Q29tb2RvIExpbWl0ZWQxFDASBgNVBAMTC0VyaWMgQnVyZ2VyMSkwJwYJKoZIhvcNAQkBFhplYnVy
Z2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTF
RRoA4LgOACMFph0aomRC/UpqoA5C/d6DUTOvTMrYSEqkjwnU4zxDtBcHlcB4AxKAov00MYsUvEU4
loz7BHjfDjv76AIkcwu33VYQbzGmarVnyaXsVb6f/cyRL3fPT0VOVO2tQAEEgwg//CX0jN8Kn2jH
uXD/HEvko7cmpL3Pwevf3+DwB61v7ca79PpEZfn/WhaqRKA4uVNPj/JbieeaLo2v/0RJzrEElZK0
pHCqxiD3mQ8ossPkA9fUCSxLlbdMcPU3be5x8vt8Q8mYTXF5Z3d9RZmYrmNkvTQtdzVpfYWr/hgV
Xqm9tByOOAR+hoN3FKbubR/OrAHL9yDAd4sCAwEAAaOCAhwwggIYMB8GA1UdIwQYMBaAFImCZ33E
nSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBRDWgutb7b8R/L7G3Y3D+molAA3VzAOBgNVHQ8BAf8E
BAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJ
YIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEW
HWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMIGlBgNVHR8EgZ0wgZowTKBKoEiGRmh0dHA6
Ly9jcmwuY29tb2RvY2EuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRF
bWFpbC5jcmwwSqBIoEaGRGh0dHA6Ly9jcmwuY29tb2RvLm5ldC9VVE4tVVNFUkZpcnN0LUNsaWVu
dEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMGwGCCsGAQUFBwEBBGAwXjA2BggrBgEFBQcwAoYq
aHR0cDovL2NydC5jb21vZG9jYS5jb20vVVROQUFBQ2xpZW50Q0EuY3J0MCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC5jb21vZG9jYS5jb20wJQYDVR0RBB4wHIEaZWJ1cmdlckBzdGFuZGFyZHN0cmFj
ay5jb20wDQYJKoZIhvcNAQEFBQADggEBAGeBR7NPCvrY3GQoIi49JOuciatY2r4st905Jw1etp6J
umFFWlaCBl11tFSclk/3S45B+lUv3SEvG4CEjUByPScprVmCqHR+y8BAQaB/CV+N1y14x3MbhJ+Z
8XDGKeUXuuyGd9w0l3/t/QPid6TRXQjQFrLPFs1IALuNpNiFMHEF/xFbMG1Z2vznR/gSPlePekoZ
TqcExIDBNZTBebpZqwAXzPpedNNOclbMLFLWDMOAozVRpkfjI0eiFsk8SF1Ho1Gb9Bx8DeG4peE2
KRVOR9FFnZZgBpFjXYRcglsMOSKCY8HgE+NGvbbqbrMoBV/BlYyxRXwfti71RL9Zs2Cq1eQxggP8
MIID+AIBATCBwzCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh
a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v
d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkNH2TynzAJBgUrDgMCGgUAoIICDTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wOTA2MDMwMTUwMzBaMCMGCSqGSIb3
DQEJBDEWBBTZM67e5GKu6Si7O+kCGqtna/302jCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD
VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU
aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv
lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN
H2TynzANBgkqhkiG9w0BAQEFAASCAQBHOldssPuB8FynCHo0V+WE01yGgYNIi43npT88VYi2B9Fz
H7ZgCWxdeXlfnpadSSefMTzvWlCQTtfKDwYul2dQYIUPTsKTfIsdmPGhnEvo9VXzmZpypaWscz1L
55IAqp7J98v1t1UHyw17URUd26A2DTSVDekMn1zLnXWsI4yX1M1isozujK/NZfTPRvRSVhw5Bmf5
dPn9frYMe1dXKTuKS6PkakVQi8qSAhHmBSsUrqzidSDV8/kjRhTI6w0kqZPCWJrEegCM1zKRjRPj
EFoilO2DrqqK4vM+dAxovDUkAZqG8PqNhEmvBClGjWEPn6UI6z+30eXzNRHUFgg6czUEAAAAAAAA

--Apple-Mail-334--601341967--

From eburger@standardstrack.com  Tue Jun  2 18:51:57 2009
Return-Path: <eburger@standardstrack.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 1B9EC3A6A15; Tue,  2 Jun 2009 18:51:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.005
X-Spam-Level: 
X-Spam-Status: No, score=-2.005 tagged_above=-999 required=5 tests=[AWL=0.594,  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 J9Z0hc2lyZX2; Tue,  2 Jun 2009 18:51:56 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19.inmotionhosting.com [205.134.252.251]) by core3.amsl.com (Postfix) with ESMTP id 4DA393A68DE; Tue,  2 Jun 2009 18:51:56 -0700 (PDT)
Received: from [12.46.252.162] (helo=[172.17.136.184]) by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1MBfdp-00068B-Uk; Tue, 02 Jun 2009 18:51:47 -0700
Message-Id: <B678F1CB-0000-4774-BF03-6B53C333F15D@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <D1611ACB-4739-4A65-94F0-403FC24CDC43@cs.columbia.edu>
Content-Type: multipart/signed; boundary=Apple-Mail-335--601262898; micalg=sha1; protocol="application/pkcs7-signature"
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 2 Jun 2009 21:51:49 -0400
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <4A2541B9.2000805@octasic.com> <00d501c9e39a$dcbbbe50$96333af0$%roni@huawei.com> <D1611ACB-4739-4A65-94F0-403FC24CDC43@cs.columbia.edu>
X-Mailer: Apple Mail (2.935.3)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Mailman-Approved-At: Wed, 03 Jun 2009 08:50:06 -0700
Cc: dispatch@ietf.org, avt@ietf.org
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 03 Jun 2009 01:51:57 -0000

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

I would strike
> - somebody will claim IPR on the resulting work
from the list of risks. The *resulting* work would clearly be  
predicated by both prior art and Note Well.

On Jun 2, 2009, at 12:15 PM, Henning Schulzrinne wrote:

> I view this as a trade-off. If we pursue this, there are risks:
>
> - nothing may come of it since there are no experts willing to help
> - somebody will claim IPR on the resulting work
> - the quality of the codec may not be competitive
>
> However, if we don't do this, we are stuck with the status quo,  
> which is not all that satisfactory. Thus, unless there are  
> significant costs for "innocent bystanders", I see this as a risk  
> worth taking. In the worst case, we are no worse off than we are  
> today. In all other cases, we'll have an additional choice for a  
> wideband codec, even if it's not "the best", just "good enough".  
> After all, most people use G.711 today, which has a really hard time  
> making that claim.
>
> Most real work in the IETF is done by very small teams, typically  
> less than 10, so as long as we have a handful of people that are  
> willing to contribute, this can work. It might even work better,  
> since you may get fewer people who have half-baked opinions - we may  
> skip the binary vs. XML debates...
>
> We can set some ground rules ("must be tested with packet loss of  
> 5%") and then see what happens. Compared to most network protocols,  
> the likely negative impacts (such as security or congestion control  
> issues) of even a badly-designed codec are pretty limited.
>
> Henning

> [snip]

--Apple-Mail-335--601262898
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGPTCCBjkw
ggUhoAMCAQICEC+VK1RLWxrF8KJZDR9k8p8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVT
MQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VS
VFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQD
Ey1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwODEz
MDAwMDAwWhcNMDkwODEzMjM1OTU5WjCB4TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsg
LSBQRVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m
IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMg
Q29tb2RvIExpbWl0ZWQxFDASBgNVBAMTC0VyaWMgQnVyZ2VyMSkwJwYJKoZIhvcNAQkBFhplYnVy
Z2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTF
RRoA4LgOACMFph0aomRC/UpqoA5C/d6DUTOvTMrYSEqkjwnU4zxDtBcHlcB4AxKAov00MYsUvEU4
loz7BHjfDjv76AIkcwu33VYQbzGmarVnyaXsVb6f/cyRL3fPT0VOVO2tQAEEgwg//CX0jN8Kn2jH
uXD/HEvko7cmpL3Pwevf3+DwB61v7ca79PpEZfn/WhaqRKA4uVNPj/JbieeaLo2v/0RJzrEElZK0
pHCqxiD3mQ8ossPkA9fUCSxLlbdMcPU3be5x8vt8Q8mYTXF5Z3d9RZmYrmNkvTQtdzVpfYWr/hgV
Xqm9tByOOAR+hoN3FKbubR/OrAHL9yDAd4sCAwEAAaOCAhwwggIYMB8GA1UdIwQYMBaAFImCZ33E
nSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBRDWgutb7b8R/L7G3Y3D+molAA3VzAOBgNVHQ8BAf8E
BAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJ
YIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEW
HWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMIGlBgNVHR8EgZ0wgZowTKBKoEiGRmh0dHA6
Ly9jcmwuY29tb2RvY2EuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRF
bWFpbC5jcmwwSqBIoEaGRGh0dHA6Ly9jcmwuY29tb2RvLm5ldC9VVE4tVVNFUkZpcnN0LUNsaWVu
dEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMGwGCCsGAQUFBwEBBGAwXjA2BggrBgEFBQcwAoYq
aHR0cDovL2NydC5jb21vZG9jYS5jb20vVVROQUFBQ2xpZW50Q0EuY3J0MCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC5jb21vZG9jYS5jb20wJQYDVR0RBB4wHIEaZWJ1cmdlckBzdGFuZGFyZHN0cmFj
ay5jb20wDQYJKoZIhvcNAQEFBQADggEBAGeBR7NPCvrY3GQoIi49JOuciatY2r4st905Jw1etp6J
umFFWlaCBl11tFSclk/3S45B+lUv3SEvG4CEjUByPScprVmCqHR+y8BAQaB/CV+N1y14x3MbhJ+Z
8XDGKeUXuuyGd9w0l3/t/QPid6TRXQjQFrLPFs1IALuNpNiFMHEF/xFbMG1Z2vznR/gSPlePekoZ
TqcExIDBNZTBebpZqwAXzPpedNNOclbMLFLWDMOAozVRpkfjI0eiFsk8SF1Ho1Gb9Bx8DeG4peE2
KRVOR9FFnZZgBpFjXYRcglsMOSKCY8HgE+NGvbbqbrMoBV/BlYyxRXwfti71RL9Zs2Cq1eQxggP8
MIID+AIBATCBwzCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh
a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v
d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkNH2TynzAJBgUrDgMCGgUAoIICDTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wOTA2MDMwMTUxNDlaMCMGCSqGSIb3
DQEJBDEWBBQHGHkp0ZW8Gr/hmagsT2KDzR616jCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD
VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU
aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv
lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN
H2TynzANBgkqhkiG9w0BAQEFAASCAQAs42o3DaZnnG2dQw40jPH4yGWTphPw5XJI9INmfn5Dy54J
rOBMchzMktJzy7LJPyE6Tkku0NH6bsTUA8Eyxy1nFD/RsVlPhgDg3HcC5OGO3eYwktCfRejcWN2k
g5L6dH/ZnFhrP9NmuosyxIedfdaHpQfaU6cmVd1hhPD1fzHe8beiv7/0qLeKfIi3WBsriogzZ65i
CD/NgEeybA0JjdIQEgK2Q86z04C8qNWmJ9tSnRyxL/sUl935dpBqGFuIQlbWQ5+D0Ir0MWDozRFh
I7I8W05/HEnngn3B63kjOfGCG4KpyJkRKKkJgjaAyDgKO+pmmjFCoCgkAUn6MJuHfvduAAAAAAAA

--Apple-Mail-335--601262898--

From canetti@post.tau.ac.il  Wed Jun  3 03:18:30 2009
Return-Path: <canetti@post.tau.ac.il>
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 CC4523A6C2D; Wed,  3 Jun 2009 03:18:30 -0700 (PDT)
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 N8ftyMZOnxMl; Wed,  3 Jun 2009 03:18:30 -0700 (PDT)
Received: from doar.tau.ac.il (gate.tau.ac.il [132.66.16.26]) by core3.amsl.com (Postfix) with ESMTP id E11143A6BE6; Wed,  3 Jun 2009 03:18:29 -0700 (PDT)
Received: from [10.0.0.5] (unknown [193.37.128.224]) by doar.tau.ac.il (Postfix) with ESMTP id 58F32BEF8; Wed,  3 Jun 2009 13:18:28 +0300 (IDT)
Message-ID: <4A264DE7.6080407@post.tau.ac.il>
Date: Wed, 03 Jun 2009 13:18:15 +0300
From: canetti <canetti@post.tau.ac.il>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: secdir@mit.edu, cfrg@ietf.org, avt@ietf.org, seokung@kisa.or.kr
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 03 Jun 2009 08:50:06 -0700
Subject: [AVT] SECDIR review of  draft-ietf-avt-seed-srtp-11
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, 03 Jun 2009 10:18:30 -0000

***   I have reviewed this document as part of the security directorate's
***   ongoing effort to review all IETF documents being processed by the
***   IESG.  These comments were written primarily for the benefit of the
***   security area directors.  Document editors and WG chairs should treat
***   these comments just like any other last call comments.


The draft describes the use of the SEED cipher (RFC 4269) within the SRTP 
protocol. The document is well written and thorough. I see no problems with it.

My only potential concern is regarding the use of SEED itself. SEED is a 
cipher that's apparently very popular in Korea and less so elsewhere. While 
no weaknesses have been found afaik, it did not receive the level of 
scrutiny that AES did.  Thus, the question arises whether the IETF should 
standardize (and thereby implicitly endorse) the use of this cipher as an 
alternative to AES.

I personally see no problem here, as long as a security comparison is made 
clear in the document. Still, others may feel differently.
In fact, for this purpose I cc'ed the cfrg RG on this evaluation.


Best,
Ran




From Even.roni@huawei.com  Wed Jun  3 10:15:52 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F04C3A6C2F; Wed,  3 Jun 2009 10:15:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.845
X-Spam-Level: 
X-Spam-Status: No, score=-0.845 tagged_above=-999 required=5 tests=[AWL=-0.351, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, 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 Eiips9axHwP7; Wed,  3 Jun 2009 10:15:51 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id AFDE93A6847; Wed,  3 Jun 2009 10:15:50 -0700 (PDT)
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 <0KKO003AYALSGO@szxga03-in.huawei.com>; Thu, 04 Jun 2009 01:15:28 +0800 (CST)
Received: from huawei.com ([172.24.1.6]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KKO00ABSALSPH@szxga03-in.huawei.com>; Thu, 04 Jun 2009 01:15:28 +0800 (CST)
Received: from windows8d787f9 (bzq-79-183-125-11.red.bezeqint.net [79.183.125.11]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KKO00LHJAKSOX@szxml02-in.huawei.com>; Thu, 04 Jun 2009 01:15:28 +0800 (CST)
Date: Wed, 03 Jun 2009 20:14:04 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <021701c9e030$0a5deef0$1f19ccd0$%roni@huawei.com>
To: 'Roni Even' <Even.roni@huawei.com>, dispatch@ietf.org
Message-id: <021201c9e46e$c1459c70$43d0d550$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_lpXgMXCdnGW+Yj9iFz4pwA)"
Content-language: en-us
Thread-index: AcngMAPzVFoLlUEtQjqFgqcok28EywENHJgg
References: <021701c9e030$0a5deef0$1f19ccd0$%roni@huawei.com>
Cc: avt@ietf.org
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 03 Jun 2009 17:15:52 -0000

This is a multipart message in MIME format.

--Boundary_(ID_lpXgMXCdnGW+Yj9iFz4pwA)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hi,

I would like to clarify that I am not against the discussion of codecs at
the IETF  but I think that before deciding to standardize one at the IETF we
should write requirements and analyze current codecs (standard as well as
non-standards) and see if they provide a good fit. 

 

One of my points is that having an IETF standard track codec does not make
it widely deployed as long as the IETF do not mandate codecs. I think that
you can look at the discussion in the SIP forum about specifying a codec.

 

I also think (and I will keep mentioning it) that one of the advantages of
voice on IP or over the Internet is that you can have a higher quality user
experience by using a wideband codec, it is a pity that G.711 is still
widely used taking bigger bandwidth than current wideband audio with lower
quality.

 

Roni Even

 

 

 

All,

 

I would like to request agenda time inside the DISPATCH meeting to propose
the formation of a new working group to define a Proposed Standard wideband
audio codec.

 

The text of the proposal is below. Comments, questions, and suggestions
welcomed.

 

Regards,

Jason

 

 

Internet Wideband Audio Codec (IWAC)

Mailing Lists: TBD

Chairs: TBD

Area Directorate: Real Time Applications (RAI)

 

Purpose:

 

This new working group would be chartered with the purpose of collecting

expertise within the IETF in order to review the design of audio codecs

specifically for use with the Internet. Unlike other SDOs, these codecs

would be optimized for use on the Internet, and as much as possible choose

technology that does not require paying patent royalties.

 

The Internet Low Bit Rate Codec (iLBC)  work was done in AVT but it was felt

that subsequent work should not be done in the AVT working group. This new

working group will have as its primary purpose the standardization of a

multi-purpose audio codec that can be used in various situations on the

Internet. Some of the proposed Internet-specific requirements include:

* scalable and adaptive bit rate;

* various sampling rate profiles from narrow-band to super-wideband;

* scalable complexity;

* low latency; and 

* resilience to packet loss.

 

There are a number of wide-band capable codecs defined by other SDOs. For

instance, G.722 is seeing adoption in Enterprise applications since it is

relatively simple and low-cost to deploy. However, it has a high, fixed

bitrate and is not appropriate for mobile applications where spectrum

efficiency is important or in consumer applications where available

bandwidth is fluctuating or limited. G.722.2 (AMR-wideband) has been adopted

by the 3GPP as a wideband standard for mobile applications. G.722.2 is

relatively high cost due to patent royalties and is seeing minimal

deployments outside of mobile handsets making it challenging to create

wideband experiences on Internet-capable mobile devices when extending

beyond the mobile network. In other cases, proprietary codecs are being

adopted which further create islands with no interoperability unless

widespread transcoding is performed. Transcoding leads to higher costs and

lower quality. 

 

The goal of this working group is to define a single codec with multiple

profiles which can be made available on a wide variety of Internet-capable

devices including low-power, mobile devices as well as devices capable of

utilizing high quality, high bitrate audio.

 

Proposed Deliverables:

 

1) Requirements for wideband, Internet audio codec(s).

2) Algorithm description for wideband, Internet audio codec(s) as Proposed

Standard. 

3) Specification of payload format(s) for defined codecs as Proposed

Standard

 

_______________________________________________

dispatch mailing list

dispatch@ietf.org

https://www.ietf.org/mailman/listinfo/dispatch

 


--Boundary_(ID_lpXgMXCdnGW+Yj9iFz4pwA)
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:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" 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;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{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'>I would like to =
clarify that I am
not against the discussion of codecs at the IETF &nbsp;but I think that =
before
deciding to standardize one at the IETF we should write requirements and =
analyze
current codecs (standard as well as non-standards) and see if they =
provide a
good fit. <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'>One of my points is =
that having
an IETF standard track codec does not make it widely deployed as long as =
the
IETF do not mandate codecs. I think that you can look at the discussion =
in the
SIP forum about specifying a codec.<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 also think (and I =
will keep
mentioning it) that one of the advantages of voice on IP or over the =
Internet
is that you can have a higher quality user experience by using a =
wideband codec,
it is a pity that G.711 is still widely used taking bigger bandwidth =
than
current wideband audio with lower quality.<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'>Roni =
Even<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'><o:p>&nbsp;</o:p></span></p>

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

<p class=3DMsoPlainText>All,<o:p></o:p></p>

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

<p class=3DMsoPlainText>I would like to request agenda time inside the =
DISPATCH meeting
to propose the formation of a new working group to define a Proposed =
Standard
wideband audio codec.<o:p></o:p></p>

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

<p class=3DMsoPlainText>The text of the proposal is below. Comments, =
questions,
and suggestions welcomed.<o:p></o:p></p>

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

<p class=3DMsoPlainText>Regards,<o:p></o:p></p>

<p class=3DMsoPlainText>Jason<o:p></o:p></p>

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

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

<p class=3DMsoPlainText>Internet Wideband Audio Codec =
(IWAC)<o:p></o:p></p>

<p class=3DMsoPlainText>Mailing Lists: TBD<o:p></o:p></p>

<p class=3DMsoPlainText>Chairs: TBD<o:p></o:p></p>

<p class=3DMsoPlainText>Area Directorate: Real Time Applications =
(RAI)<o:p></o:p></p>

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

<p class=3DMsoPlainText>Purpose:<o:p></o:p></p>

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

<p class=3DMsoPlainText>This new working group would be chartered with =
the
purpose of collecting<o:p></o:p></p>

<p class=3DMsoPlainText>expertise within the IETF in order to review the =
design
of audio codecs<o:p></o:p></p>

<p class=3DMsoPlainText>specifically for use with the Internet. Unlike =
other
SDOs, these codecs<o:p></o:p></p>

<p class=3DMsoPlainText>would be optimized for use on the Internet, and =
as much
as possible choose<o:p></o:p></p>

<p class=3DMsoPlainText>technology that does not require paying patent =
royalties.<o:p></o:p></p>

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

<p class=3DMsoPlainText>The Internet Low Bit Rate Codec (iLBC)&nbsp; =
work was
done in AVT but it was felt<o:p></o:p></p>

<p class=3DMsoPlainText>that subsequent work should not be done in the =
AVT
working group. This new<o:p></o:p></p>

<p class=3DMsoPlainText>working group will have as its primary purpose =
the
standardization of a<o:p></o:p></p>

<p class=3DMsoPlainText>multi-purpose audio codec that can be used in =
various
situations on the<o:p></o:p></p>

<p class=3DMsoPlainText>Internet. Some of the proposed Internet-specific
requirements include:<o:p></o:p></p>

<p class=3DMsoPlainText>* scalable and adaptive bit rate;<o:p></o:p></p>

<p class=3DMsoPlainText>* various sampling rate profiles from =
narrow-band to
super-wideband;<o:p></o:p></p>

<p class=3DMsoPlainText>* scalable complexity;<o:p></o:p></p>

<p class=3DMsoPlainText>* low latency; and <o:p></o:p></p>

<p class=3DMsoPlainText>* resilience to packet loss.<o:p></o:p></p>

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

<p class=3DMsoPlainText>There are a number of wide-band capable codecs =
defined by
other SDOs. For<o:p></o:p></p>

<p class=3DMsoPlainText>instance, G.722 is seeing adoption in Enterprise
applications since it is<o:p></o:p></p>

<p class=3DMsoPlainText>relatively simple and low-cost to deploy. =
However, it has
a high, fixed<o:p></o:p></p>

<p class=3DMsoPlainText>bitrate and is not appropriate for mobile =
applications
where spectrum<o:p></o:p></p>

<p class=3DMsoPlainText>efficiency is important or in consumer =
applications where
available<o:p></o:p></p>

<p class=3DMsoPlainText>bandwidth is fluctuating or limited. G.722.2
(AMR-wideband) has been adopted<o:p></o:p></p>

<p class=3DMsoPlainText>by the 3GPP as a wideband standard for mobile
applications. G.722.2 is<o:p></o:p></p>

<p class=3DMsoPlainText>relatively high cost due to patent royalties and =
is
seeing minimal<o:p></o:p></p>

<p class=3DMsoPlainText>deployments outside of mobile handsets making it
challenging to create<o:p></o:p></p>

<p class=3DMsoPlainText>wideband experiences on Internet-capable mobile =
devices
when extending<o:p></o:p></p>

<p class=3DMsoPlainText>beyond the mobile network. In other cases, =
proprietary
codecs are being<o:p></o:p></p>

<p class=3DMsoPlainText>adopted which further create islands with no
interoperability unless<o:p></o:p></p>

<p class=3DMsoPlainText>widespread transcoding is performed. Transcoding =
leads to
higher costs and<o:p></o:p></p>

<p class=3DMsoPlainText>lower quality. <o:p></o:p></p>

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

<p class=3DMsoPlainText>The goal of this working group is to define a =
single
codec with multiple<o:p></o:p></p>

<p class=3DMsoPlainText>profiles which can be made available on a wide =
variety of
Internet-capable<o:p></o:p></p>

<p class=3DMsoPlainText>devices including low-power, mobile devices as =
well as
devices capable of<o:p></o:p></p>

<p class=3DMsoPlainText>utilizing high quality, high bitrate =
audio.<o:p></o:p></p>

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

<p class=3DMsoPlainText>Proposed Deliverables:<o:p></o:p></p>

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

<p class=3DMsoPlainText>1) Requirements for wideband, Internet audio =
codec(s).<o:p></o:p></p>

<p class=3DMsoPlainText>2) Algorithm description for wideband, Internet =
audio
codec(s) as Proposed<o:p></o:p></p>

<p class=3DMsoPlainText>Standard. <o:p></o:p></p>

<p class=3DMsoPlainText>3) Specification of payload format(s) for =
defined codecs
as Proposed<o:p></o:p></p>

<p class=3DMsoPlainText>Standard<o:p></o:p></p>

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

<p =
class=3DMsoPlainText>_______________________________________________<o:p>=
</o:p></p>

<p class=3DMsoPlainText>dispatch mailing list<o:p></o:p></p>

<p class=3DMsoPlainText><a =
href=3D"mailto:dispatch@ietf.org">dispatch@ietf.org</a><o:p></o:p></p>

<p class=3DMsoPlainText><a =
href=3D"https://www.ietf.org/mailman/listinfo/dispatch">https://www.ietf.=
org/mailman/listinfo/dispatch</a><o:p></o:p></p>

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

</div>

</body>

</html>

--Boundary_(ID_lpXgMXCdnGW+Yj9iFz4pwA)--

From versteb@cisco.com  Wed Jun  3 10:57:39 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 588F43A6E57 for <avt@core3.amsl.com>; Wed,  3 Jun 2009 10:57:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.774
X-Spam-Level: 
X-Spam-Status: No, score=-6.774 tagged_above=-999 required=5 tests=[AWL=-0.175, 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 FQgjd517xttw for <avt@core3.amsl.com>; Wed,  3 Jun 2009 10:57:38 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id A11473A6AA6 for <avt@ietf.org>; Wed,  3 Jun 2009 10:57:37 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.41,299,1241395200"; d="scan'208,217";a="46153267"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 03 Jun 2009 17:57:38 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n53HvcZ3020789;  Wed, 3 Jun 2009 13:57:38 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n53HvcMH027761; Wed, 3 Jun 2009 17:57:38 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);  Wed, 3 Jun 2009 13:57:38 -0400
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_01C9E474.C8218598"
Date: Wed, 3 Jun 2009 13:57:37 -0400
Message-ID: <81B9B88E2F9D574AA5328A85547CDE910154BAC0@xmb-rtp-21d.amer.cisco.com>
In-Reply-To: <658E8F78-CF7D-4405-9C73-ABE2837B4E62@csperkins.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] RTP unicast address for retransmssion of multicastsesssion or using RTCP to negotitaion of RTP adddresses
Thread-Index: AcndfPQlq7Hi+VTPRdeRar4LT0tk3gG9IXsw
References: <001701c9dca0$bd465130$37d2f390$%roni@huawei.com><dcad22d80905251225h64bd303cx9de2c1698b8eaa7d@mail.gmail.com> <658E8F78-CF7D-4405-9C73-ABE2837B4E62@csperkins.org>
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "Colin Perkins" <csp@csperkins.org>, "Marshall Eubanks" <marshall.eubanks@gmail.com>
X-OriginalArrivalTime: 03 Jun 2009 17:57:38.0586 (UTC) FILETIME=[C8603FA0:01C9E474]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=11710; t=1244051858; x=1244915858; c=relaxed/simple; s=rtpdkim1001; 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=20[AVT]=20RTP=20unicast=20address=20for=2 0retransmssion=20of=20multicastsesssion=20or=20using=20RTCP= 20to=20negotitaion=20of=20RTP=20adddresses |Sender:=20 |To:=20=22Colin=20Perkins=22=20<csp@csperkins.org>,=0A=20=2 0=20=20=20=20=20=20=22Marshall=20Eubanks=22=20<marshall.euba nks@gmail.com>; bh=9H7V0I5VPIz5JGOAuTY04ssT9YqzmSIGNMGVuBGiSfk=; b=Th1SLYHso7/tW22IMe898euqUirih7lYr5m8XjjWVnbqBJsjwiuRKwgOgC quRIOeipSSPoQiJt6Cy/Dyu/PvVcXlSCPX2Bj4m37MVHRkHg6Gl+O2851rC+ eo3q89EgL6;
Authentication-Results: rtp-dkim-1; header.From=versteb@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; ); 
Cc: "Dave Oran \(oran\)" <oran@cisco.com>, avt@ietf.org, Roni Even <Even.roni@huawei.com>
Subject: Re: [AVT] RTP unicast address for retransmssion of multicastsesssion or using RTCP to negotitaion of RTP adddresses
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, 03 Jun 2009 17:57:39 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9E474.C8218598
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

I am reluctant to recommend a STUN-specific approach to convey the RTCP
port mappings. There are other mechanisms to open pin-holes in NAT.
"UPnP NAT Traversal" is one example.
=20
You could also envision cases when we need to signal RTP/RTCP port
numbers even when there is no NAT between the RTP receiver and the
feedback target.
=20
In my mind, this drives us towards a generic RTCP mechanism to signal
port mappings. We would include that RTCP message in the RAMS-R
transaction.
=20
Bill VerSteeg

________________________________

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Colin Perkins
Sent: Monday, May 25, 2009 5:08 PM
To: Marshall Eubanks
Cc: Dave Oran (oran); avt@ietf.org; Roni Even
Subject: Re: [AVT] RTP unicast address for retransmssion of
multicastsesssion or using RTCP to negotitaion of RTP adddresses


On 25 May 2009, at 20:25, Marshall Eubanks wrote:

	On Sun, May 24, 2009 at 2:51 PM, Roni Even
<Even.roni@huawei.com> wrote:
=09

		One of the issues discussed in Rapid Acquisition of
Multicast RTPSessions (RAMS) has to do with the specific architecture
where the media is sent to an announced multicast  address where there
is no offer answer negotiation between the sender and the receivers.  In
the proposed solution  receivers may ask using RTCP for unicast
retransmission of the RTP stream. The current draft has as part of the
announcement a port number that the receiver should use to receive the
unicast RTP stream.  This port is specified by the retransmission server
and not by the receiver and it assumes that the IP address will be the
same as the one from where the RTCP message came from.


		=20

		The problem we encounter is that this retransmission
stream is flowing from the retransmission server to the receiver who may
be behind a FW/NAT. The simple case is if the RTP and RTCP streams are
multiplexed on the RTCP port since in this case there is an RTCP message
going from the receiver to the retransmission server which will open a
pin hole in the NAT/FW enabling RTP to flow back to the receiver (Will
need some keep alive mechanism)

		The case we are trying to discuss here is when we want
to have a separate RTP channel (not multiplexed with RTCP). In this case
we will need some mechanism to convey an address from the receiver to
the retransmission server.=20


		=20

		We would like to ask if this should be part of RAMS or
do we want a general RTCP message to covey such information.


	I would say that this should be a general RTCP message. This is
a general technique now for getting through firewalls (rfc 5138). H.460
/18 and /19 use it, ICE uses it, it should be made general for RTP.


I agree that a general mechanism should be defined, rather than
something that's narrowly focussed on the RAMS problem. It's not clear
that RTCP is the right place for such an extension, though. RTCP has
focussed on media level issues to date, leaving transport layer
configuration to protocols like STUN. This seems like more of a STUN
extension, than something that should be in RTCP.=20

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




------_=_NextPart_001_01C9E474.C8218598
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16809" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space">
<DIV dir=3Dltr align=3Dleft><SPAN class=3D895583317-03062009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I am reluctant to recommend a STUN-specific =
approach to=20
convey the RTCP port mappings.&nbsp;There are other mechanisms to open =
pin-holes=20
in NAT. "UPnP NAT Traversal" is one example.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D895583317-03062009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D895583317-03062009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>You could also envision&nbsp;cases when we need =
to signal=20
RTP/RTCP port numbers even when there is no NAT between the RTP receiver =
and the=20
feedback target.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D895583317-03062009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D895583317-03062009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>In my mind, this drives us towards a generic =
RTCP mechanism=20
to signal port mappings. We would include that RTCP message in the =
RAMS-R=20
transaction.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D895583317-03062009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D895583317-03062009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Bill VerSteeg</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> avt-bounces@ietf.org=20
[mailto:avt-bounces@ietf.org] <B>On Behalf Of </B>Colin =
Perkins<BR><B>Sent:</B>=20
Monday, May 25, 2009 5:08 PM<BR><B>To:</B> Marshall =
Eubanks<BR><B>Cc:</B> Dave=20
Oran (oran); avt@ietf.org; Roni Even<BR><B>Subject:</B> Re: [AVT] RTP =
unicast=20
address for retransmssion of multicastsesssion or using RTCP to =
negotitaion of=20
RTP adddresses<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>
<DIV>On 25 May 2009, at 20:25, Marshall Eubanks wrote:</DIV>
<BLOCKQUOTE type=3D"cite">
  <DIV class=3Dgmail_quote>On Sun, May 24, 2009 at 2:51 PM, Roni Even =
<SPAN=20
  dir=3Dltr>&lt;<A=20
  =
href=3D"mailto:Even.roni@huawei.com">Even.roni@huawei.com</A>&gt;</SPAN> =

  wrote:<BR>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: =
#ccc 1px solid">
    <DIV lang=3DEN-US vlink=3D"purple" link=3D"blue">
    <DIV>
    <P><SPAN class=3DApple-style-span =
style=3D"-webkit-text-stroke-width: -1">One of=20
    the issues discussed in Rapid Acquisition of Multicast RTPSessions =
(RAMS)=20
    has to do with the specific architecture where the media is sent to =
an=20
    announced multicast&nbsp; address where there is no offer answer =
negotiation=20
    between the sender and the receivers. &nbsp;In the proposed solution =

    &nbsp;receivers may ask using RTCP for unicast retransmission of the =
RTP=20
    stream. The current draft has as part of the announcement a port =
number that=20
    the receiver should use to receive the unicast RTP stream. =
&nbsp;This port=20
    is specified by the retransmission server and not by the receiver =
and it=20
    assumes that the IP address will be the same as the one from where =
the RTCP=20
    message came from.</SPAN></P>
    <DIV><BR class=3Dwebkit-block-placeholder>&nbsp;</DIV>
    <P>The problem we encounter is that this retransmission stream is =
flowing=20
    from the retransmission server to the receiver who may be behind a =
FW/NAT.=20
    The simple case is if the RTP and RTCP streams are multiplexed on =
the RTCP=20
    port since in this case there is an RTCP message going from the =
receiver to=20
    the retransmission server which will open a pin hole in the NAT/FW =
enabling=20
    RTP to flow back to the receiver (Will need some keep alive =
mechanism)</P>
    <P>The case we are trying to discuss here is when we want to have a =
separate=20
    RTP channel (not multiplexed with RTCP). In this case we will need =
some=20
    mechanism to convey an address from the receiver to the =
retransmission=20
    server. </P>
    <DIV><BR class=3Dwebkit-block-placeholder>&nbsp;</DIV>
    <P>We would like to ask if this should be part of RAMS or do we want =
a=20
    general RTCP message to covey such =
information.</P></DIV></DIV></BLOCKQUOTE>
  <DIV><BR></DIV>
  <DIV>I would say that this should be a general RTCP message. This is a =
general=20
  technique now for getting through firewalls (rfc 5138). H.460 /18 and =
/19 use=20
  it, ICE&nbsp;uses it, it should be made general for=20
RTP.</DIV></DIV></BLOCKQUOTE></DIV><BR>I agree that a general mechanism =
should=20
be defined, rather than something that's narrowly focussed on the RAMS =
problem.=20
It's not clear that RTCP is the right place for such an extension, =
though. RTCP=20
has focussed on media level issues to date, leaving transport layer=20
configuration to protocols like STUN. This seems like more of a STUN =
extension,=20
than something that should be in RTCP.
<DIV apple-content-edited=3D"true"><SPAN class=3DApple-style-span=20
style=3D"WORD-SPACING: 0px; FONT: 9px Arial; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; =
-webkit-text-stroke-width: 0; orphans: 2; widows: 2; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto">
<DIV=20
style=3D"WORD-WRAP: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space"><SPAN=20
class=3DApple-style-span=20
style=3D"WORD-SPACING: 0px; FONT: 9px 'Lucida Sans Typewriter'; =
TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: =
normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate; =
-webkit-text-stroke-width: 0px; orphans: 2; widows: 2; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto"><SPAN=20
class=3DApple-style-span=20
style=3D"WORD-SPACING: 0px; FONT: 9px 'Lucida Sans Typewriter'; =
TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: =
normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; =
widows: 2; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto"><SPAN=20
class=3DApple-style-span=20
style=3D"WORD-SPACING: 0px; FONT: 9px 'Lucida Sans Typewriter'; =
TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: =
normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; =
widows: 2; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto"><SPAN=20
class=3DApple-style-span=20
style=3D"WORD-SPACING: 0px; FONT: 9px 'Lucida Sans Typewriter'; =
TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: =
normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; =
widows: 2; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto">
<DIV><BR class=3Dkhtml-block-placeholder></DIV>
<DIV>--&nbsp;</DIV>
<DIV></DIV>
<DIV>Colin Perkins</DIV>
<DIV><A=20
href=3D"http://csperkins.org/">http://csperkins.org/</A></DIV></SPAN></SP=
AN></SPAN><BR=20
class=3DApple-interchange-newline></SPAN><BR=20
class=3DApple-interchange-newline></DIV></SPAN></DIV><BR></BODY></HTML>

------_=_NextPart_001_01C9E474.C8218598--

From jean-marc.valin@octasic.com  Wed Jun  3 11:47:39 2009
Return-Path: <jean-marc.valin@octasic.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 D35343A6E68; Wed,  3 Jun 2009 11:47:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.449
X-Spam-Level: 
X-Spam-Status: No, score=-1.449 tagged_above=-999 required=5 tests=[AWL=1.150,  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 kKgfbGD7tXVL; Wed,  3 Jun 2009 11:47:38 -0700 (PDT)
Received: from MAILEXCH.octasic.com (mail.octasic.com [216.208.79.2]) by core3.amsl.com (Postfix) with ESMTP id B5B553A6E35; Wed,  3 Jun 2009 11:47:38 -0700 (PDT)
Received: from [142.138.24.19] ([142.138.24.19]) by MAILEXCH.octasic.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 3 Jun 2009 14:47:35 -0400
Message-ID: <4A26C563.8030200@octasic.com>
Date: Wed, 03 Jun 2009 14:48:03 -0400
From: Jean-Marc Valin <jean-marc.valin@octasic.com>
User-Agent: Thunderbird 2.0.0.21 (X11/20090409)
MIME-Version: 1.0
To: jmh@joelhalpern.com
References: <021701c9e030$0a5deef0$1f19ccd0$%roni@huawei.com> <021201c9e46e$c1459c70$43d0d550$%roni@huawei.com>
In-Reply-To: <021201c9e46e$c1459c70$43d0d550$%roni@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Jun 2009 18:47:35.0055 (UTC) FILETIME=[C26921F0:01C9E47B]
Cc: dispatch@ietf.org, avt@ietf.org, Roni Even <Even.roni@huawei.com>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 03 Jun 2009 18:47:39 -0000

> So far, what strikes me is that most of the folks who would be called 
> upon to evaluate a requirements document, or an actual protocol, have 
> little or no expertise in codec design either from a mathematical or a 
> software perspective (there are a few exceptions in both those 
> regards, folks like Henning), and have little or no experience in the 
> observed difficulties in actually standardizing codecs. (Folks I ahve 
> talked to who have been down that road have indicated that it involves 
> many aspects that are foreign to IETF experience and practice.) 

Let me start by stating that codec design is no rocket science. There 
are many people out there who know how to write audio codecs and many 
more who have sufficient skills to contribute. At this point, there is 
already interest from several people with actual codec design experience 
at Skype, Xiph.Org and SPIRIT. The internet community has clear and 
considerable needs which are not being adequately met by the existing 
standards bodies. We have parties experienced with codec development who 
want to work together within the IETF. Why do you believe the risk of 
not succeeding justifies not even attempting the effort?

Cheers,

    Jean-Marc

From Even.roni@huawei.com  Wed Jun  3 12:31:35 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0DB7328C1CB for <avt@core3.amsl.com>; Wed,  3 Jun 2009 12:31:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.758
X-Spam-Level: 
X-Spam-Status: No, score=-0.758 tagged_above=-999 required=5 tests=[AWL=-0.263, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 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 BsruMPtFwM4Q for <avt@core3.amsl.com>; Wed,  3 Jun 2009 12:31:34 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 90A0E28C160 for <avt@ietf.org>; Wed,  3 Jun 2009 12:31:25 -0700 (PDT)
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 <0KKO0076QGW2K2@szxga04-in.huawei.com> for avt@ietf.org; Thu, 04 Jun 2009 03:31:14 +0800 (CST)
Received: from huawei.com ([172.24.1.6]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KKO00DY0GW15Z@szxga04-in.huawei.com> for avt@ietf.org; Thu, 04 Jun 2009 03:31:14 +0800 (CST)
Received: from windows8d787f9 (bzq-79-183-125-11.red.bezeqint.net [79.183.125.11]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KKO00L3MGVUOX@szxml02-in.huawei.com>; Thu, 04 Jun 2009 03:31:13 +0800 (CST)
Date: Wed, 03 Jun 2009 22:30:18 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <81B9B88E2F9D574AA5328A85547CDE910154B981@xmb-rtp-21d.amer.cisco.com>
To: "'Bill Ver Steeg (versteb)'" <versteb@cisco.com>, avt@ietf.org
Message-id: <024101c9e481$c0468150$40d383f0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcnS4FBFJRh0kTNdSKKujynDJmWrDwAJMQ/AAC+GL9AAAGUFAAAXW2jQAA+eDnAASHsCkALEQgYwAIvU5CAAOrRN4AAgVN0QAArx1NAACZh3EA==
References: <fa05fd7ad709f.d709ffa05fd7a@huawei.com> <81B9B88E2F9D574AA5328A85547CDE91013038E4@xmb-rtp-21d.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE9101303DA5@xmb-rtp-21d.amer.cisco.com> <00dc01c9d3c5$7a323aa0$6e96afe0$%roni@huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D54094C3DBF@xmb-sjc-215.amer.cisco.com> <000a01c9d461$813bdcb0$83b39610$%roni@huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D540954DB8A@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE9101495636@xmb-rtp-21d.amer.cisco.com> <011701c9e2c3$6a75b990$3f612cb0$%roni@huawei.com> <81B9B88E2F9D574AA5328A85547CDE91014FFAE5@xmb-rtp-21d.amer.cisco.com> <01c701c9e430$ff5f7960$fe1e6c20$%roni@huawei.com> <81B9B88E2F9D574AA5328A85547CDE910154B981@xmb-rtp-21d.amer.cisco.com>
Subject: Re: [AVT] Calling for comments on changes to RAMS draft 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/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, 03 Jun 2009 19:31:35 -0000

Bill,
The draft should not go to new NAT traversal solution. My thinking is that
it should explain the problem, my personal view is that the major problem is
for the unicast RTP port on the receiver and reference RTP/RTCP mux and STUN
or ICE as options to address the issue. 

Roni

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Bill
Ver Steeg (versteb)
Sent: Wednesday, June 03, 2009 5:59 PM
To: Roni Even; avt@ietf.org
Subject: Re: [AVT] Calling for comments on changes to RAMS draft 00

We definitely are working on NAT and SDP. We have been searching for
innovative NAT solutions, but I think we are realizing that this is
well-trodden ground. The NAT section will lay out how the normal NAT
methods apply to the RAMS transactions. There is some subtlety around
how the port number that the RAMS-R transactions goes to, as well as
some interaction with RTP/RTCP muxing. We will try expose these points
in enough detail to avoid the common pitfalls around port usage.

Bill VerSteeg
 

-----Original Message-----
From: Roni Even [mailto:Even.roni@huawei.com] 
Sent: Wednesday, June 03, 2009 5:52 AM
To: Bill Ver Steeg (versteb); avt@ietf.org
Subject: RE: [AVT] Calling for comments on changes to RAMS draft 00

Hi Bill,
I looked at the diff file, the content looks fine to me. The changes in
section 7 about the extensions (adding 7.1.1) were not clear editorially
so I will review the section after you submit the new draft.

Do you intend also to start working on the NAT traversal section and add
clarification to the SDP example based on the email thread with Jose
Rey.

Regards
Roni

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Bill Ver Steeg (versteb)
Sent: Tuesday, June 02, 2009 9:14 PM
To: Roni Even; avt@ietf.org
Subject: Re: [AVT] Calling for comments on changes to RAMS draft 00

Roni-

Yes, we plan to add all of the comments from the diff. I will be sure to
update the "subject line" when we do.

Bvs
 

-----Original Message-----
From: Roni Even [mailto:Even.roni@huawei.com]
Sent: Monday, June 01, 2009 10:15 AM
To: Bill Ver Steeg (versteb); avt@ietf.org
Subject: Calling for comments on changes to RAMS draft 00

Bill,
Are you going to add all the comments from the rdiff.

Also please send this email not under the above subject since it does
not describe the purpose of the email

Roni

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Bill Ver Steeg (versteb)
Sent: Friday, May 29, 2009 10:40 PM
To: avt@ietf.org
Subject: Re: [AVT] Adopting Rapid Acquisition of Multicast RTP
Sessions(RAMS) as a working group item

Fellow AVT folks-

We are continuing to solicit comments on the RAMS design points
identified in Ali's email from May 15 (diff enclosed). We have received
some valuable feedback. We hope to have a new draft mid next week, and
will incorporate comments that we receive through Monday or Tuesday in
that draft.

Thanks in advance



Bill VerSteeg

-----Original Message-----
From: Ali C. Begen (abegen)
Sent: Friday, May 15, 2009 1:32 PM
To: Roni Even; Bill Ver Steeg (versteb); avt@ietf.org
Subject: RE: [AVT] Adopting Rapid Acquisition of Multicast RTP
Sessions(RAMS) as a working group item

Hi Roni, All,

Here is a diff for sections 7 and 13. 

Comments are welcome.
-acbegen

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

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


From Even.roni@huawei.com  Wed Jun  3 12:37:32 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 497BE3A6D0E for <avt@core3.amsl.com>; Wed,  3 Jun 2009 12:37:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.757
X-Spam-Level: 
X-Spam-Status: No, score=-1.757 tagged_above=-999 required=5 tests=[AWL=0.841,  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 648Aa1c9bxgO for <avt@core3.amsl.com>; Wed,  3 Jun 2009 12:37:30 -0700 (PDT)
Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id CCE383A692D for <avt@ietf.org>; Wed,  3 Jun 2009 12:37:29 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KKO0017IH6AHS@szxga02-in.huawei.com> for avt@ietf.org; Thu, 04 Jun 2009 03:37:23 +0800 (CST)
Received: from huawei.com ([172.24.1.3]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KKO00LDSH6AJ0@szxga02-in.huawei.com> for avt@ietf.org; Thu, 04 Jun 2009 03:37:22 +0800 (CST)
Received: from windows8d787f9 (bzq-79-183-125-11.red.bezeqint.net [79.183.125.11]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KKO00AZVH5TVL@szxml01-in.huawei.com>; Thu, 04 Jun 2009 03:37:22 +0800 (CST)
Date: Wed, 03 Jun 2009 22:36:18 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <81B9B88E2F9D574AA5328A85547CDE910154BAC0@xmb-rtp-21d.amer.cisco.com>
To: "'Bill Ver Steeg (versteb)'" <versteb@cisco.com>, 'Colin Perkins' <csp@csperkins.org>, 'Marshall Eubanks' <marshall.eubanks@gmail.com>
Message-id: <024201c9e482$9a7e4e20$cf7aea60$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_vMZUqm/DcG7D5GkuTexKrQ)"
Content-language: en-us
Thread-index: AcndfPQlq7Hi+VTPRdeRar4LT0tk3gG9IXswAAQqU3A=
References: <001701c9dca0$bd465130$37d2f390$%roni@huawei.com> <dcad22d80905251225h64bd303cx9de2c1698b8eaa7d@mail.gmail.com> <658E8F78-CF7D-4405-9C73-ABE2837B4E62@csperkins.org> <81B9B88E2F9D574AA5328A85547CDE910154BAC0@xmb-rtp-21d.amer.cisco.com>
Cc: "'Dave Oran \(oran\)'" <oran@cisco.com>, avt@ietf.org
Subject: Re: [AVT] RTP unicast address for retransmssion of multicastsesssion or using RTCP to negotitaion of RTP adddresses
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, 03 Jun 2009 19:37:32 -0000

This is a multipart message in MIME format.

--Boundary_(ID_vMZUqm/DcG7D5GkuTexKrQ)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Bill,

My major concern is with the RTP port on the RR that according to the
proposal is declared by the RS.  This will not work when there is a NAT in
the middle and will require an outbound packet to establish and keep the
binding. The recommended IETF solution is STUN and other methods like UPnP
may be mentioned

Roni

 

From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com] 
Sent: Wednesday, June 03, 2009 8:58 PM
To: Colin Perkins; Marshall Eubanks
Cc: Dave Oran (oran); avt@ietf.org; Roni Even
Subject: RE: [AVT] RTP unicast address for retransmssion of
multicastsesssion or using RTCP to negotitaion of RTP adddresses

 

I am reluctant to recommend a STUN-specific approach to convey the RTCP port
mappings. There are other mechanisms to open pin-holes in NAT. "UPnP NAT
Traversal" is one example.

 

You could also envision cases when we need to signal RTP/RTCP port numbers
even when there is no NAT between the RTP receiver and the feedback target.

 

In my mind, this drives us towards a generic RTCP mechanism to signal port
mappings. We would include that RTCP message in the RAMS-R transaction.

 

Bill VerSteeg

 

  _____  

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Colin
Perkins
Sent: Monday, May 25, 2009 5:08 PM
To: Marshall Eubanks
Cc: Dave Oran (oran); avt@ietf.org; Roni Even
Subject: Re: [AVT] RTP unicast address for retransmssion of
multicastsesssion or using RTCP to negotitaion of RTP adddresses

On 25 May 2009, at 20:25, Marshall Eubanks wrote:

On Sun, May 24, 2009 at 2:51 PM, Roni Even <Even.roni@huawei.com> wrote:

One of the issues discussed in Rapid Acquisition of Multicast RTPSessions
(RAMS) has to do with the specific architecture where the media is sent to
an announced multicast  address where there is no offer answer negotiation
between the sender and the receivers.  In the proposed solution  receivers
may ask using RTCP for unicast retransmission of the RTP stream. The current
draft has as part of the announcement a port number that the receiver should
use to receive the unicast RTP stream.  This port is specified by the
retransmission server and not by the receiver and it assumes that the IP
address will be the same as the one from where the RTCP message came from.


 

The problem we encounter is that this retransmission stream is flowing from
the retransmission server to the receiver who may be behind a FW/NAT. The
simple case is if the RTP and RTCP streams are multiplexed on the RTCP port
since in this case there is an RTCP message going from the receiver to the
retransmission server which will open a pin hole in the NAT/FW enabling RTP
to flow back to the receiver (Will need some keep alive mechanism)

The case we are trying to discuss here is when we want to have a separate
RTP channel (not multiplexed with RTCP). In this case we will need some
mechanism to convey an address from the receiver to the retransmission
server. 


 

We would like to ask if this should be part of RAMS or do we want a general
RTCP message to covey such information.

 

I would say that this should be a general RTCP message. This is a general
technique now for getting through firewalls (rfc 5138). H.460 /18 and /19
use it, ICE uses it, it should be made general for RTP.


I agree that a general mechanism should be defined, rather than something
that's narrowly focussed on the RAMS problem. It's not clear that RTCP is
the right place for such an extension, though. RTCP has focussed on media
level issues to date, leaving transport layer configuration to protocols
like STUN. This seems like more of a STUN extension, than something that
should be in RTCP. 

 

-- 

Colin Perkins

http://csperkins.org/





 


--Boundary_(ID_vMZUqm/DcG7D5GkuTexKrQ)
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:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" 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)">
<!--[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;}
@font-face
	{font-family:"Lucida Sans Typewriter";
	panose-1:2 11 5 9 3 5 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;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle19
	{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 style=3D'WORD-WRAP: =
break-word;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space'>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Bill,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>My major concern is with the RTP port on the RR that =
according
to the proposal is declared by the RS. &nbsp;This will not work when =
there is a NAT
in the middle and will require an outbound packet to establish and keep =
the binding.
The recommended IETF solution is STUN and other methods like UPnP may be
mentioned<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Roni<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
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"'> Bill Ver =
Steeg
(versteb) [mailto:versteb@cisco.com] <br>
<b>Sent:</b> Wednesday, June 03, 2009 8:58 PM<br>
<b>To:</b> Colin Perkins; Marshall Eubanks<br>
<b>Cc:</b> Dave Oran (oran); avt@ietf.org; Roni Even<br>
<b>Subject:</b> RE: [AVT] RTP unicast address for retransmssion of
multicastsesssion or using RTCP to negotitaion of RTP =
adddresses<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'>I am reluctant to recommend a STUN-specific approach to =
convey the
RTCP port mappings.&nbsp;There are other mechanisms to open pin-holes in =
NAT.
&quot;UPnP NAT Traversal&quot; is one example.</span><o:p></o:p></p>

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

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>You could also envision&nbsp;cases when we need to signal =
RTP/RTCP
port numbers even when there is no NAT between the RTP receiver and the
feedback target.</span><o:p></o:p></p>

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

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>In my mind, this drives us towards a generic RTCP mechanism =
to
signal port mappings. We would include that RTCP message in the RAMS-R
transaction.</span><o:p></o:p></p>

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

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

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

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

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

</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"'> avt-bounces@ietf.org
[mailto:avt-bounces@ietf.org] <b>On Behalf Of </b>Colin Perkins<br>
<b>Sent:</b> Monday, May 25, 2009 5:08 PM<br>
<b>To:</b> Marshall Eubanks<br>
<b>Cc:</b> Dave Oran (oran); avt@ietf.org; Roni Even<br>
<b>Subject:</b> Re: [AVT] RTP unicast address for retransmssion of
multicastsesssion or using RTCP to negotitaion of RTP =
adddresses</span><o:p></o:p></p>

<div>

<div>

<p class=3DMsoNormal>On 25 May 2009, at 20:25, Marshall Eubanks =
wrote:<o:p></o:p></p>

</div>

<blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'>

<div>

<p class=3DMsoNormal>On Sun, May 24, 2009 at 2:51 PM, Roni Even &lt;<a
href=3D"mailto:Even.roni@huawei.com">Even.roni@huawei.com</a>&gt; =
wrote:<o:p></o:p></p>

<div>

<div>

<p><span class=3Dapple-style-span>One of the issues discussed in Rapid
Acquisition of Multicast RTPSessions (RAMS) has to do with the specific
architecture where the media is sent to an announced multicast&nbsp; =
address
where there is no offer answer negotiation between the sender and the
receivers. &nbsp;In the proposed solution &nbsp;receivers may ask using =
RTCP
for unicast retransmission of the RTP stream. The current draft has as =
part of
the announcement a port number that the receiver should use to receive =
the
unicast RTP stream. &nbsp;This port is specified by the retransmission =
server
and not by the receiver and it assumes that the IP address will be the =
same as
the one from where the RTCP message came from.</span><o:p></o:p></p>

<div>

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

</div>

<p>The problem we encounter is that this retransmission stream is =
flowing from
the retransmission server to the receiver who may be behind a FW/NAT. =
The
simple case is if the RTP and RTCP streams are multiplexed on the RTCP =
port
since in this case there is an RTCP message going from the receiver to =
the
retransmission server which will open a pin hole in the NAT/FW enabling =
RTP to
flow back to the receiver (Will need some keep alive =
mechanism)<o:p></o:p></p>

<p>The case we are trying to discuss here is when we want to have a =
separate
RTP channel (not multiplexed with RTCP). In this case we will need some
mechanism to convey an address from the receiver to the retransmission =
server. <o:p></o:p></p>

<div>

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

</div>

<p>We would like to ask if this should be part of RAMS or do we want a =
general
RTCP message to covey such information.<o:p></o:p></p>

</div>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>I would say that this should be a general RTCP =
message. This
is a general technique now for getting through firewalls (rfc 5138). =
H.460 /18
and /19 use it, ICE&nbsp;uses it, it should be made general for =
RTP.<o:p></o:p></p>

</div>

</div>

</blockquote>

</div>

<p class=3DMsoNormal><br>
I agree that a general mechanism should be defined, rather than =
something
that's narrowly focussed on the RAMS problem. It's not clear that RTCP =
is the
right place for such an extension, though. RTCP has focussed on media =
level
issues to date, leaving transport layer configuration to protocols like =
STUN.
This seems like more of a STUN extension, than something that should be =
in
RTCP. <o:p></o:p></p>

<div>

<div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:7.0pt;font-family:"Lucida =
Sans Typewriter";
color:black'><o:p>&nbsp;</o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:7.0pt;font-family:"Lucida =
Sans Typewriter";
color:black'>--&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:7.0pt;font-family:"Lucida =
Sans Typewriter";
color:black'>Colin Perkins<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:7.0pt;font-family:"Lucida =
Sans Typewriter";
color:black'><a =
href=3D"http://csperkins.org/">http://csperkins.org/</a><o:p></o:p></span=
></p>

</div>

<p class=3DMsoNormal><span style=3D'font-size:7.0pt;font-family:"Lucida =
Sans Typewriter";
color:black'><br>
<br>
</span><span style=3D'font-size:7.0pt;font-family:"Arial","sans-serif";
color:black'><o:p></o:p></span></p>

</div>

</div>

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

</div>

</body>

</html>

--Boundary_(ID_vMZUqm/DcG7D5GkuTexKrQ)--

From hsinnrei@adobe.com  Wed Jun  3 13:24:08 2009
Return-Path: <hsinnrei@adobe.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 1FD2C3A698F; Wed,  3 Jun 2009 13:24:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[AWL=2.377,  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 TR0lM8u5q5gX; Wed,  3 Jun 2009 13:24:06 -0700 (PDT)
Received: from exprod6og115.obsmtp.com (exprod6og115.obsmtp.com [64.18.1.35]) by core3.amsl.com (Postfix) with ESMTP id 6CC8028C29A; Wed,  3 Jun 2009 13:23:45 -0700 (PDT)
Received: from source ([192.150.8.22]) by exprod6ob115.postini.com ([64.18.5.12]) with SMTP ID DSNKSibbxAs0V41SpXXx1qKQTTkoshCFi7dA@postini.com; Wed, 03 Jun 2009 13:23:49 PDT
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id n53KNTWG000781; Wed, 3 Jun 2009 13:23:30 -0700 (PDT)
Received: from nacas01.corp.adobe.com (nacas01.corp.adobe.com [10.8.189.99]) by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id n53KNSiq008083; Wed, 3 Jun 2009 13:23:28 -0700 (PDT)
Received: from nacas03.corp.adobe.com (10.8.189.121) by nacas01.corp.adobe.com (10.8.189.99) with Microsoft SMTP Server (TLS) id 8.1.340.0; Wed, 3 Jun 2009 13:23:28 -0700
Received: from nambx05.corp.adobe.com ([10.8.189.124]) by nacas03.corp.adobe.com ([10.8.189.121]) with mapi; Wed, 3 Jun 2009 13:23:28 -0700
From: Henry Sinnreich <hsinnrei@adobe.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "dispatch@ietf.org" <dispatch@ietf.org>
Date: Wed, 3 Jun 2009 13:23:26 -0700
Thread-Topic: [dispatch] [AVT] Proposal to form Internet Wideband Audio Codec WG
Thread-Index: AcnkhYhHhDqOeaeyS3aq802n9l5R9AAA531L
Message-ID: <C64C45EE.3ECE%hsinnrei@adobe.com>
In-Reply-To: <4A26D59B.20905@joelhalpern.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C64C45EE3ECEhsinnreiadobecom_"
MIME-Version: 1.0
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 03 Jun 2009 20:24:08 -0000

--_000_C64C45EE3ECEhsinnreiadobecom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Joel,

>And now, before I start repeating myself

I will also repeat here that it makes no sense to have this huge IETF work =
for voice (mainly) signaling (SIP, XMPP, NSIS) and no standard for an _Inte=
rnet_ voice codec.

Going by your guidance for avoiding a voice codec, the IETF may also just g=
ive up signaling for voice and close down all the voice related signaling W=
Gs. And since we are at it, why not all the A/V codec profiles in AVT? :-)
This is hard to rationalize.

Henry


On 6/3/09 2:57 PM, "Joel M. Halpern" <jmh@joelhalpern.com> wrote:

Let's be clear.  I am not trying to argue that the existing codecs are
good enough.  I hear everyone saying that they are not.
However, the IETF is not the answer to all the worlds standards problems.

In this case, there are a number of existing bodies addressing these
problems.  There also are apparently existing solutions with near the
right properties.
1) The IETF is structurally not well suited to dealing with the kinds of
patent problems that we are dealing with.
2) The IETF, based on history, is not very good at dealing with market
acceptance issues (questions such as why isn't Speex or SILK being
accepted.)
3) IETF WGs are very bad at working out what the real problems are.
THey are good at working out protocol issues.  But this is not primarily
a protocol issue, from what everyone is saying.

I have heard rumors of several other bodies that are working in this
space.  Given that we have lately been working very hard to keep other
folks from encroaching on our patch, we ought to be sensitive to
encroaching on theirs.

And now, before I start repeating myself, I will try to stay quite for a
few days and keep listening.
Yours,
Joel


Dan York wrote:
> I've been reading this thread with great interest as for the past
> probably 6 years or so I've been saying to anyone who will listen (and
> to those who won't ;-) that one factor that will help "IP
> communications/VoIP/UC/whatever-marketing-term-we-want-to-rename-our-prod=
ucts-to-this-week"
> to really find wide adoption is to provide a "rich communication
> experience" better than what people are used to now.
>
> Wideband audio is, to me, a huge part of that.
>
> However, I completely agree with Henning on this point:
>
>> On Jun 2, 2009, at 12:15 PM, Henning Schulzrinne wrote:
>>
>>> However, if we don't do this, we are stuck with the status quo, which
>>> is not all that satisfactory.
>
>
> The status quo is not satisfactory.  If you want to add wideband audio
> to your product, you've got an alphabet soup of mutually incompatible
> options with vastly different licensing terms/fees/options and source
> code availability.
>
> I think we ultimately need a "G.711 for wideband", i.e. a wideband codec
> that anyone can implement in any device.  I'd argue that a large part of
> the reason we are "stuck" with so many people in VoIP using G.711 is
> precisely because ANYONE can implement it in basically ANY device.  You
> can buy a G.711 codec implementation or you can write your own or find
> some code on the Internet (google "G.711 source code"). You can
> implement G.711 in your big softswitch or IP-PBX... or you can implement
> it in some small embedded device.
>
> And it interoperates.
>
> We need that kind of codec for wideband.... which I would say is
> "royalty-free" and needs to have "open source" implementations
> available.   (And yes, I know Speex is out there - I don't have a view
> as to why it is not more widely implemented.  And yes, I know Skype is
> giving away SILK royalty-free, but it's not open source.)
>
> Can the IETF help with this?  I don't know... but I think it's worth a
> shot.  If there is a group that is passionate about this (and there
> seems to be) then lets get the mailing list set up and have it go the
> regular List -> BOF -> Working Group trajectory.
>
> In the best case perhaps we come out with the codec we want/need.  At
> the very worst I think we'd wind up with at least creating some good
> discussions and requirements for what we do need.
>
> My 2 cents,
> Dan
>
_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch


--_000_C64C45EE3ECEhsinnreiadobecom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [dispatch] [AVT] Proposal to form Internet Wideband Audio Codec =
WG</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:=
18pt'>Joel,<BR>
<BR>
&gt;And now, before I start repeating myself<BR>
<BR>
I will also repeat here that it makes no sense to have this huge IETF work =
for voice (mainly) signaling (SIP, XMPP, NSIS) and no standard for an _Inte=
rnet_<I> </I> voice codec. <BR>
<BR>
Going by your guidance for avoiding a voice codec, the IETF may also just g=
ive up signaling for voice and close down all the voice related signaling W=
Gs. And since we are at it, why not all the A/V codec profiles in AVT? :-) =
<BR>
This is hard to rationalize.<BR>
<BR>
Henry<BR>
<BR>
<BR>
On 6/3/09 2:57 PM, &quot;Joel M. Halpern&quot; &lt;<a href=3D"jmh@joelhalpe=
rn.com">jmh@joelhalpern.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:18pt'>Let's be clear. &nbsp;I am not trying to ar=
gue that the existing codecs are<BR>
good enough. &nbsp;I hear everyone saying that they are not.<BR>
However, the IETF is not the answer to all the worlds standards problems.<B=
R>
<BR>
In this case, there are a number of existing bodies addressing these<BR>
problems. &nbsp;There also are apparently existing solutions with near the<=
BR>
right properties.<BR>
1) The IETF is structurally not well suited to dealing with the kinds of<BR=
>
patent problems that we are dealing with.<BR>
2) The IETF, based on history, is not very good at dealing with market<BR>
acceptance issues (questions such as why isn't Speex or SILK being<BR>
accepted.)<BR>
3) IETF WGs are very bad at working out what the real problems are.<BR>
THey are good at working out protocol issues. &nbsp;But this is not primari=
ly<BR>
a protocol issue, from what everyone is saying.<BR>
<BR>
I have heard rumors of several other bodies that are working in this<BR>
space. &nbsp;Given that we have lately been working very hard to keep other=
<BR>
folks from encroaching on our patch, we ought to be sensitive to<BR>
encroaching on theirs.<BR>
<BR>
And now, before I start repeating myself, I will try to stay quite for a<BR=
>
few days and keep listening.<BR>
Yours,<BR>
Joel<BR>
<BR>
<BR>
Dan York wrote:<BR>
&gt; I've been reading this thread with great interest as for the past<BR>
&gt; probably 6 years or so I've been saying to anyone who will listen (and=
<BR>
&gt; to those who won't ;-) that one factor that will help &quot;IP<BR>
&gt; communications/VoIP/UC/whatever-marketing-term-we-want-to-rename-our-p=
roducts-to-this-week&quot;<BR>
&gt; to really find wide adoption is to provide a &quot;rich communication<=
BR>
&gt; experience&quot; better than what people are used to now.<BR>
&gt;<BR>
&gt; Wideband audio is, to me, a huge part of that.<BR>
&gt;<BR>
&gt; However, I completely agree with Henning on this point:<BR>
&gt;<BR>
&gt;&gt; On Jun 2, 2009, at 12:15 PM, Henning Schulzrinne wrote:<BR>
&gt;&gt;<BR>
&gt;&gt;&gt; However, if we don't do this, we are stuck with the status quo=
, which<BR>
&gt;&gt;&gt; is not all that satisfactory.<BR>
&gt;<BR>
&gt;<BR>
&gt; The status quo is not satisfactory. &nbsp;If you want to add wideband =
audio<BR>
&gt; to your product, you've got an alphabet soup of mutually incompatible<=
BR>
&gt; options with vastly different licensing terms/fees/options and source<=
BR>
&gt; code availability.<BR>
&gt;<BR>
&gt; I think we ultimately need a &quot;G.711 for wideband&quot;, i.e. a wi=
deband codec<BR>
&gt; that anyone can implement in any device. &nbsp;I'd argue that a large =
part of<BR>
&gt; the reason we are &quot;stuck&quot; with so many people in VoIP using =
G.711 is<BR>
&gt; precisely because ANYONE can implement it in basically ANY device. &nb=
sp;You<BR>
&gt; can buy a G.711 codec implementation or you can write your own or find=
<BR>
&gt; some code on the Internet (google &quot;G.711 source code&quot;). You =
can<BR>
&gt; implement G.711 in your big softswitch or IP-PBX... or you can impleme=
nt<BR>
&gt; it in some small embedded device.<BR>
&gt;<BR>
&gt; And it interoperates.<BR>
&gt;<BR>
&gt; We need that kind of codec for wideband.... which I would say is<BR>
&gt; &quot;royalty-free&quot; and needs to have &quot;open source&quot; imp=
lementations<BR>
&gt; available. &nbsp;&nbsp;(And yes, I know Speex is out there - I don't h=
ave a view<BR>
&gt; as to why it is not more widely implemented. &nbsp;And yes, I know Sky=
pe is<BR>
&gt; giving away SILK royalty-free, but it's not open source.)<BR>
&gt;<BR>
&gt; Can the IETF help with this? &nbsp;I don't know... but I think it's wo=
rth a<BR>
&gt; shot. &nbsp;If there is a group that is passionate about this (and the=
re<BR>
&gt; seems to be) then lets get the mailing list set up and have it go the<=
BR>
&gt; regular List -&gt; BOF -&gt; Working Group trajectory.<BR>
&gt;<BR>
&gt; In the best case perhaps we come out with the codec we want/need. &nbs=
p;At<BR>
&gt; the very worst I think we'd wind up with at least creating some good<B=
R>
&gt; discussions and requirements for what we do need.<BR>
&gt;<BR>
&gt; My 2 cents,<BR>
&gt; Dan<BR>
&gt;<BR>
_______________________________________________<BR>
dispatch mailing list<BR>
<a href=3D"dispatch@ietf.org">dispatch@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/dispatch">https://www.ietf=
.org/mailman/listinfo/dispatch</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--_000_C64C45EE3ECEhsinnreiadobecom_--

From jmh@joelhalpern.com  Wed Jun  3 10:40:24 2009
Return-Path: <jmh@joelhalpern.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 A4EC53A7074; Wed,  3 Jun 2009 10:40:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.532
X-Spam-Level: 
X-Spam-Status: No, score=-3.532 tagged_above=-999 required=5 tests=[AWL=0.067,  BAYES_00=-2.599, 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 PChoUGB48Dho; Wed,  3 Jun 2009 10:40:23 -0700 (PDT)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id DC9CB3A7075; Wed,  3 Jun 2009 10:39:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id E1F63430254; Wed,  3 Jun 2009 10:39:33 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.100] (pool-71-161-52-172.clppva.btas.verizon.net [71.161.52.172]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTP id E266443023D; Wed,  3 Jun 2009 10:39:32 -0700 (PDT)
Message-ID: <4A26B54D.8070800@joelhalpern.com>
Date: Wed, 03 Jun 2009 13:39:25 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: dispatch@ietf.org
References: <021701c9e030$0a5deef0$1f19ccd0$%roni@huawei.com> <021201c9e46e$c1459c70$43d0d550$%roni@huawei.com>
In-Reply-To: <021201c9e46e$c1459c70$43d0d550$%roni@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 03 Jun 2009 13:45:34 -0700
Cc: avt@ietf.org
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 03 Jun 2009 17:40:24 -0000

To be blunt, without some better explanation of why the IETF ought to do 
this, and how the IETF is likely to be successful in doing this, I think 
it would be a disservice to the folks who want to work on this to 
encourage them to believe that the only obstacle is a clear problem 
definition.

To be clear, I have absolutely no problem with a community using an IETF 
   based email list to discuss their codec ideas, work out why they want 
to work on a new one, organize thier ideas for where that work should be 
done, etc.

So far, what strikes me is that most of the folks who would be called 
upon to evaluate a requirements document, or an actual protocol, have 
little or no expertise in codec design either from a mathematical or a 
software perspective (there are a few exceptions in both those regards, 
folks like Henning), and have little or no experience in the observed 
difficulties in actually standardizing codecs.  (Folks I ahve talked to 
who have been down that road have indicated that it involves many 
aspects that are foreign to IETF experience and practice.)

Yours,
Joel M. Halpern

Roni Even wrote:
> 
> 
> Hi,
> 
> I would like to clarify that I am not against the discussion of codecs 
> at the IETF  but I think that before deciding to standardize one at the 
> IETF we should write requirements and analyze current codecs (standard 
> as well as non-standards) and see if they provide a good fit.
> 
>  
> 
> One of my points is that having an IETF standard track codec does not 
> make it widely deployed as long as the IETF do not mandate codecs. I 
> think that you can look at the discussion in the SIP forum about 
> specifying a codec.
> 
>  
> 
> I also think (and I will keep mentioning it) that one of the advantages 
> of voice on IP or over the Internet is that you can have a higher 
> quality user experience by using a wideband codec, it is a pity that 
> G.711 is still widely used taking bigger bandwidth than current wideband 
> audio with lower quality.
> 
>  
> 
> Roni Even
> 
>  
> 
>  
> 
>  
> 
> All,
> 
>  
> 
> I would like to request agenda time inside the DISPATCH meeting to 
> propose the formation of a new working group to define a Proposed 
> Standard wideband audio codec.
> 
>  
> 
> The text of the proposal is below. Comments, questions, and suggestions 
> welcomed.
> 
>  
> 
> Regards,
> 
> Jason
> 
>  
> 
>  
> 
> Internet Wideband Audio Codec (IWAC)
> 
> Mailing Lists: TBD
> 
> Chairs: TBD
> 
> Area Directorate: Real Time Applications (RAI)
> 
>  
> 
> Purpose:
> 
>  
> 
> This new working group would be chartered with the purpose of collecting
> 
> expertise within the IETF in order to review the design of audio codecs
> 
> specifically for use with the Internet. Unlike other SDOs, these codecs
> 
> would be optimized for use on the Internet, and as much as possible choose
> 
> technology that does not require paying patent royalties.
> 
>  
> 
> The Internet Low Bit Rate Codec (iLBC)  work was done in AVT but it was 
> felt
> 
> that subsequent work should not be done in the AVT working group. This new
> 
> working group will have as its primary purpose the standardization of a
> 
> multi-purpose audio codec that can be used in various situations on the
> 
> Internet. Some of the proposed Internet-specific requirements include:
> 
> * scalable and adaptive bit rate;
> 
> * various sampling rate profiles from narrow-band to super-wideband;
> 
> * scalable complexity;
> 
> * low latency; and
> 
> * resilience to packet loss.
> 
>  
> 
> There are a number of wide-band capable codecs defined by other SDOs. For
> 
> instance, G.722 is seeing adoption in Enterprise applications since it is
> 
> relatively simple and low-cost to deploy. However, it has a high, fixed
> 
> bitrate and is not appropriate for mobile applications where spectrum
> 
> efficiency is important or in consumer applications where available
> 
> bandwidth is fluctuating or limited. G.722.2 (AMR-wideband) has been 
> adopted
> 
> by the 3GPP as a wideband standard for mobile applications. G.722.2 is
> 
> relatively high cost due to patent royalties and is seeing minimal
> 
> deployments outside of mobile handsets making it challenging to create
> 
> wideband experiences on Internet-capable mobile devices when extending
> 
> beyond the mobile network. In other cases, proprietary codecs are being
> 
> adopted which further create islands with no interoperability unless
> 
> widespread transcoding is performed. Transcoding leads to higher costs and
> 
> lower quality.
> 
>  
> 
> The goal of this working group is to define a single codec with multiple
> 
> profiles which can be made available on a wide variety of Internet-capable
> 
> devices including low-power, mobile devices as well as devices capable of
> 
> utilizing high quality, high bitrate audio.
> 
>  
> 
> Proposed Deliverables:
> 
>  
> 
> 1) Requirements for wideband, Internet audio codec(s).
> 
> 2) Algorithm description for wideband, Internet audio codec(s) as Proposed
> 
> Standard.
> 
> 3) Specification of payload format(s) for defined codecs as Proposed
> 
> Standard
> 
>  
> 
> _______________________________________________
> 
> dispatch mailing list
> 
> dispatch@ietf.org <mailto:dispatch@ietf.org>
> 
> https://www.ietf.org/mailman/listinfo/dispatch
> 
>  
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch

From dyork@voxeo.com  Wed Jun  3 12:45:51 2009
Return-Path: <dyork@voxeo.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 CB1143A6DD1; Wed,  3 Jun 2009 12:45:51 -0700 (PDT)
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 Hnz5GI40nFFM; Wed,  3 Jun 2009 12:45:50 -0700 (PDT)
Received: from voxeo.com (mmail.voxeo.com [66.193.54.208]) by core3.amsl.com (Postfix) with SMTP id 91B0F3A698C; Wed,  3 Jun 2009 12:45:50 -0700 (PDT)
Received: from [66.65.231.233] (account dyork HELO pc-00148.lodestar2.local) by voxeo.com (CommuniGate Pro SMTP 5.2.3) with ESMTPSA id 46290963; Wed, 03 Jun 2009 19:45:44 +0000
Message-Id: <CE8BFF1C-6F4D-4AF7-A5A7-20FD7C516D12@voxeo.com>
From: Dan York <dyork@voxeo.com>
To: dispatch@ietf.org
In-Reply-To: <B678F1CB-0000-4774-BF03-6B53C333F15D@standardstrack.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 3 Jun 2009 15:45:42 -0400
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <4A2541B9.2000805@octasic.com> <00d501c9e39a$dcbbbe50$96333af0$%roni@huawei.com> <D1611ACB-4739-4A65-94F0-403FC24CDC43@cs.columbia.edu> <B678F1CB-0000-4774-BF03-6B53C333F15D@standardstrack.com>
X-Mailer: Apple Mail (2.930.3)
X-Mailman-Approved-At: Wed, 03 Jun 2009 13:45:34 -0700
Cc: avt@ietf.org, Eric Burger <eburger@standardstrack.com>, Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 03 Jun 2009 19:45:51 -0000

I've been reading this thread with great interest as for the past  
probably 6 years or so I've been saying to anyone who will listen (and  
to those who won't ;-) that one factor that will help "IP  
communications/VoIP/UC/whatever-marketing-term-we-want-to-rename-our- 
products-to-this-week" to really find wide adoption is to provide a  
"rich communication experience" better than what people are used to now.

Wideband audio is, to me, a huge part of that.

However, I completely agree with Henning on this point:

> On Jun 2, 2009, at 12:15 PM, Henning Schulzrinne wrote:
>
>> However, if we don't do this, we are stuck with the status quo,  
>> which is not all that satisfactory.


The status quo is not satisfactory.  If you want to add wideband audio  
to your product, you've got an alphabet soup of mutually incompatible  
options with vastly different licensing terms/fees/options and source  
code availability.

I think we ultimately need a "G.711 for wideband", i.e. a wideband  
codec that anyone can implement in any device.  I'd argue that a large  
part of the reason we are "stuck" with so many people in VoIP using G. 
711 is precisely because ANYONE can implement it in basically ANY  
device.  You can buy a G.711 codec implementation or you can write  
your own or find some code on the Internet (google "G.711 source  
code"). You can implement G.711 in your big softswitch or IP-PBX... or  
you can implement it in some small embedded device.

And it interoperates.

We need that kind of codec for wideband.... which I would say is  
"royalty-free" and needs to have "open source" implementations  
available.   (And yes, I know Speex is out there - I don't have a view  
as to why it is not more widely implemented.  And yes, I know Skype is  
giving away SILK royalty-free, but it's not open source.)

Can the IETF help with this?  I don't know... but I think it's worth a  
shot.  If there is a group that is passionate about this (and there  
seems to be) then lets get the mailing list set up and have it go the  
regular List -> BOF -> Working Group trajectory.

In the best case perhaps we come out with the codec we want/need.  At  
the very worst I think we'd wind up with at least creating some good  
discussions and requirements for what we do need.

My 2 cents,
Dan

-- 
Dan York, Director of Conversations
Voxeo Corporation   http://www.voxeo.com  dyork@voxeo.com
Phone: +1-407-455-5859    Skype: danyork

Join the Voxeo conversation:
Blogs: http://blogs.voxeo.com  http://www.disruptivetelephony.com
Twitter: http://twitter.com/voxeo  http://twitter.com/danyork
Facebook: http://www.voxeo.com/facebook








From jmh@joelhalpern.com  Wed Jun  3 12:57:22 2009
Return-Path: <jmh@joelhalpern.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 D1F0628C189; Wed,  3 Jun 2009 12:57:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.542
X-Spam-Level: 
X-Spam-Status: No, score=-3.542 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599, 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 N-bhtFBmqVZC; Wed,  3 Jun 2009 12:57:22 -0700 (PDT)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 001E53A67E6; Wed,  3 Jun 2009 12:57:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 1956D43029A; Wed,  3 Jun 2009 12:57:24 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.100] (pool-71-161-52-172.clppva.btas.verizon.net [71.161.52.172]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTP id 4CD0943025E; Wed,  3 Jun 2009 12:57:23 -0700 (PDT)
Message-ID: <4A26D59B.20905@joelhalpern.com>
Date: Wed, 03 Jun 2009 15:57:15 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: dispatch@ietf.org
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com>	<00a401c9e388$b25c2350$171469f0$%roni@huawei.com>	<4A2541B9.2000805@octasic.com>	<00d501c9e39a$dcbbbe50$96333af0$%roni@huawei.com>	<D1611ACB-4739-4A65-94F0-403FC24CDC43@cs.columbia.edu>	<B678F1CB-0000-4774-BF03-6B53C333F15D@standardstrack.com> <CE8BFF1C-6F4D-4AF7-A5A7-20FD7C516D12@voxeo.com>
In-Reply-To: <CE8BFF1C-6F4D-4AF7-A5A7-20FD7C516D12@voxeo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 03 Jun 2009 13:45:34 -0700
Cc: avt@ietf.org
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 03 Jun 2009 19:57:22 -0000

Let's be clear.  I am not trying to argue that the existing codecs are 
good enough.  I hear everyone saying that they are not.
However, the IETF is not the answer to all the worlds standards problems.

In this case, there are a number of existing bodies addressing these 
problems.  There also are apparently existing solutions with near the 
right properties.
1) The IETF is structurally not well suited to dealing with the kinds of 
patent problems that we are dealing with.
2) The IETF, based on history, is not very good at dealing with market 
acceptance issues (questions such as why isn't Speex or SILK being 
accepted.)
3) IETF WGs are very bad at working out what the real problems are. 
THey are good at working out protocol issues.  But this is not primarily 
a protocol issue, from what everyone is saying.

I have heard rumors of several other bodies that are working in this 
space.  Given that we have lately been working very hard to keep other 
folks from encroaching on our patch, we ought to be sensitive to 
encroaching on theirs.

And now, before I start repeating myself, I will try to stay quite for a 
few days and keep listening.
Yours,
Joel


Dan York wrote:
> I've been reading this thread with great interest as for the past 
> probably 6 years or so I've been saying to anyone who will listen (and 
> to those who won't ;-) that one factor that will help "IP 
> communications/VoIP/UC/whatever-marketing-term-we-want-to-rename-our-products-to-this-week" 
> to really find wide adoption is to provide a "rich communication 
> experience" better than what people are used to now.
> 
> Wideband audio is, to me, a huge part of that.
> 
> However, I completely agree with Henning on this point:
> 
>> On Jun 2, 2009, at 12:15 PM, Henning Schulzrinne wrote:
>>
>>> However, if we don't do this, we are stuck with the status quo, which 
>>> is not all that satisfactory.
> 
> 
> The status quo is not satisfactory.  If you want to add wideband audio 
> to your product, you've got an alphabet soup of mutually incompatible 
> options with vastly different licensing terms/fees/options and source 
> code availability.
> 
> I think we ultimately need a "G.711 for wideband", i.e. a wideband codec 
> that anyone can implement in any device.  I'd argue that a large part of 
> the reason we are "stuck" with so many people in VoIP using G.711 is 
> precisely because ANYONE can implement it in basically ANY device.  You 
> can buy a G.711 codec implementation or you can write your own or find 
> some code on the Internet (google "G.711 source code"). You can 
> implement G.711 in your big softswitch or IP-PBX... or you can implement 
> it in some small embedded device.
> 
> And it interoperates.
> 
> We need that kind of codec for wideband.... which I would say is 
> "royalty-free" and needs to have "open source" implementations 
> available.   (And yes, I know Speex is out there - I don't have a view 
> as to why it is not more widely implemented.  And yes, I know Skype is 
> giving away SILK royalty-free, but it's not open source.)
> 
> Can the IETF help with this?  I don't know... but I think it's worth a 
> shot.  If there is a group that is passionate about this (and there 
> seems to be) then lets get the mailing list set up and have it go the 
> regular List -> BOF -> Working Group trajectory.
> 
> In the best case perhaps we come out with the codec we want/need.  At 
> the very worst I think we'd wind up with at least creating some good 
> discussions and requirements for what we do need.
> 
> My 2 cents,
> Dan
> 

From hsinnrei@adobe.com  Wed Jun  3 13:50:24 2009
Return-Path: <hsinnrei@adobe.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 80E573A6D99 for <avt@core3.amsl.com>; Wed,  3 Jun 2009 13:50:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.409
X-Spam-Level: 
X-Spam-Status: No, score=-5.409 tagged_above=-999 required=5 tests=[AWL=1.189,  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 omo3uDqHvF5E for <avt@core3.amsl.com>; Wed,  3 Jun 2009 13:50:23 -0700 (PDT)
Received: from psmtp.com (exprod6ob111.obsmtp.com [64.18.1.26]) by core3.amsl.com (Postfix) with ESMTP id 609F83A6B7A for <avt@ietf.org>; Wed,  3 Jun 2009 13:50:22 -0700 (PDT)
Received: from source ([192.150.8.22]) by exprod6ob111.postini.com ([64.18.5.12]) with SMTP ID DSNKSibiDs9C/q9c0rBJn7U9C3KWjGL9i89u@postini.com; Wed, 03 Jun 2009 13:50:25 PDT
Received: from inner-relay-2.corp.adobe.com ([153.32.1.52]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id n53KoKWG003402; Wed, 3 Jun 2009 13:50:21 -0700 (PDT)
Received: from nahub02.corp.adobe.com (nahub02.corp.adobe.com [10.8.189.98]) by inner-relay-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id n53KoJtQ021781; Wed, 3 Jun 2009 13:50:19 -0700 (PDT)
Received: from nambx05.corp.adobe.com ([10.8.189.124]) by nahub02.corp.adobe.com ([10.8.189.98]) with mapi; Wed, 3 Jun 2009 13:50:19 -0700
From: Henry Sinnreich <hsinnrei@adobe.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Date: Wed, 3 Jun 2009 13:50:17 -0700
Thread-Topic: [dispatch] [AVT] Proposal to form Internet Wideband Audio Codec WG
Thread-Index: AcnkhYhHhDqOeaeyS3aq802n9l5R9AAB14zQ
Message-ID: <C64C4C39.3ED5%hsinnrei@adobe.com>
In-Reply-To: <4A26D59B.20905@joelhalpern.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C64C4C393ED5hsinnreiadobecom_"
MIME-Version: 1.0
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 03 Jun 2009 20:50:24 -0000

--_000_C64C4C393ED5hsinnreiadobecom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Joel,

>And now, before I start repeating myself

I will also repeat here that it makes no sense to have this huge IETF work =
for voice (mainly) signaling (SIP, XMPP, NSIS) and no standard for an _Inte=
rnet_ voice codec.

Going by your guidance for avoiding a voice codec, the IETF may also just g=
ive up signaling for voice and close down all the voice related signaling W=
Gs. And since we are at it, why not all the A/V codec profiles in AVT? :-)
This is hard to rationalize.

Henry


On 6/3/09 2:57 PM, "Joel M. Halpern" <jmh@joelhalpern.com> wrote:

Let's be clear.  I am not trying to argue that the existing codecs are
good enough.  I hear everyone saying that they are not.
However, the IETF is not the answer to all the worlds standards problems.

In this case, there are a number of existing bodies addressing these
problems.  There also are apparently existing solutions with near the
right properties.
1) The IETF is structurally not well suited to dealing with the kinds of
patent problems that we are dealing with.
2) The IETF, based on history, is not very good at dealing with market
acceptance issues (questions such as why isn't Speex or SILK being
accepted.)
3) IETF WGs are very bad at working out what the real problems are.
THey are good at working out protocol issues.  But this is not primarily
a protocol issue, from what everyone is saying.

I have heard rumors of several other bodies that are working in this
space.  Given that we have lately been working very hard to keep other
folks from encroaching on our patch, we ought to be sensitive to
encroaching on theirs.

And now, before I start repeating myself, I will try to stay quite for a
few days and keep listening.
Yours,
Joel


Dan York wrote:
> I've been reading this thread with great interest as for the past
> probably 6 years or so I've been saying to anyone who will listen (and
> to those who won't ;-) that one factor that will help "IP
> communications/VoIP/UC/whatever-marketing-term-we-want-to-rename-our-prod=
ucts-to-this-week"
> to really find wide adoption is to provide a "rich communication
> experience" better than what people are used to now.
>
> Wideband audio is, to me, a huge part of that.
>
> However, I completely agree with Henning on this point:
>
>> On Jun 2, 2009, at 12:15 PM, Henning Schulzrinne wrote:
>>
>>> However, if we don't do this, we are stuck with the status quo, which
>>> is not all that satisfactory.
>
>
> The status quo is not satisfactory.  If you want to add wideband audio
> to your product, you've got an alphabet soup of mutually incompatible
> options with vastly different licensing terms/fees/options and source
> code availability.
>
> I think we ultimately need a "G.711 for wideband", i.e. a wideband codec
> that anyone can implement in any device.  I'd argue that a large part of
> the reason we are "stuck" with so many people in VoIP using G.711 is
> precisely because ANYONE can implement it in basically ANY device.  You
> can buy a G.711 codec implementation or you can write your own or find
> some code on the Internet (google "G.711 source code"). You can
> implement G.711 in your big softswitch or IP-PBX... or you can implement
> it in some small embedded device.
>
> And it interoperates.
>
> We need that kind of codec for wideband.... which I would say is
> "royalty-free" and needs to have "open source" implementations
> available.   (And yes, I know Speex is out there - I don't have a view
> as to why it is not more widely implemented.  And yes, I know Skype is
> giving away SILK royalty-free, but it's not open source.)
>
> Can the IETF help with this?  I don't know... but I think it's worth a
> shot.  If there is a group that is passionate about this (and there
> seems to be) then lets get the mailing list set up and have it go the
> regular List -> BOF -> Working Group trajectory.
>
> In the best case perhaps we come out with the codec we want/need.  At
> the very worst I think we'd wind up with at least creating some good
> discussions and requirements for what we do need.
>
> My 2 cents,
> Dan
>
_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch


--_000_C64C4C393ED5hsinnreiadobecom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [dispatch] [AVT] Proposal to form Internet Wideband Audio Codec =
WG</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:=
18pt'>Joel,<BR>
<BR>
&gt;And now, before I start repeating myself<BR>
<BR>
I will also repeat here that it makes no sense to have this huge IETF work =
for voice (mainly) signaling (SIP, XMPP, NSIS) and no standard for an _Inte=
rnet_<I> </I> voice codec. <BR>
<BR>
Going by your guidance for avoiding a voice codec, the IETF may also just g=
ive up signaling for voice and close down all the voice related signaling W=
Gs. And since we are at it, why not all the A/V codec profiles in AVT? :-) =
<BR>
This is hard to rationalize.<BR>
<BR>
Henry<BR>
<BR>
<BR>
On 6/3/09 2:57 PM, &quot;Joel M. Halpern&quot; &lt;<a href=3D"jmh@joelhalpe=
rn.com">jmh@joelhalpern.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:18pt'>Let's be clear. &nbsp;I am not trying to ar=
gue that the existing codecs are<BR>
good enough. &nbsp;I hear everyone saying that they are not.<BR>
However, the IETF is not the answer to all the worlds standards problems.<B=
R>
<BR>
In this case, there are a number of existing bodies addressing these<BR>
problems. &nbsp;There also are apparently existing solutions with near the<=
BR>
right properties.<BR>
1) The IETF is structurally not well suited to dealing with the kinds of<BR=
>
patent problems that we are dealing with.<BR>
2) The IETF, based on history, is not very good at dealing with market<BR>
acceptance issues (questions such as why isn't Speex or SILK being<BR>
accepted.)<BR>
3) IETF WGs are very bad at working out what the real problems are.<BR>
THey are good at working out protocol issues. &nbsp;But this is not primari=
ly<BR>
a protocol issue, from what everyone is saying.<BR>
<BR>
I have heard rumors of several other bodies that are working in this<BR>
space. &nbsp;Given that we have lately been working very hard to keep other=
<BR>
folks from encroaching on our patch, we ought to be sensitive to<BR>
encroaching on theirs.<BR>
<BR>
And now, before I start repeating myself, I will try to stay quite for a<BR=
>
few days and keep listening.<BR>
Yours,<BR>
Joel<BR>
<BR>
<BR>
Dan York wrote:<BR>
&gt; I've been reading this thread with great interest as for the past<BR>
&gt; probably 6 years or so I've been saying to anyone who will listen (and=
<BR>
&gt; to those who won't ;-) that one factor that will help &quot;IP<BR>
&gt; communications/VoIP/UC/whatever-marketing-term-we-want-to-rename-our-p=
roducts-to-this-week&quot;<BR>
&gt; to really find wide adoption is to provide a &quot;rich communication<=
BR>
&gt; experience&quot; better than what people are used to now.<BR>
&gt;<BR>
&gt; Wideband audio is, to me, a huge part of that.<BR>
&gt;<BR>
&gt; However, I completely agree with Henning on this point:<BR>
&gt;<BR>
&gt;&gt; On Jun 2, 2009, at 12:15 PM, Henning Schulzrinne wrote:<BR>
&gt;&gt;<BR>
&gt;&gt;&gt; However, if we don't do this, we are stuck with the status quo=
, which<BR>
&gt;&gt;&gt; is not all that satisfactory.<BR>
&gt;<BR>
&gt;<BR>
&gt; The status quo is not satisfactory. &nbsp;If you want to add wideband =
audio<BR>
&gt; to your product, you've got an alphabet soup of mutually incompatible<=
BR>
&gt; options with vastly different licensing terms/fees/options and source<=
BR>
&gt; code availability.<BR>
&gt;<BR>
&gt; I think we ultimately need a &quot;G.711 for wideband&quot;, i.e. a wi=
deband codec<BR>
&gt; that anyone can implement in any device. &nbsp;I'd argue that a large =
part of<BR>
&gt; the reason we are &quot;stuck&quot; with so many people in VoIP using =
G.711 is<BR>
&gt; precisely because ANYONE can implement it in basically ANY device. &nb=
sp;You<BR>
&gt; can buy a G.711 codec implementation or you can write your own or find=
<BR>
&gt; some code on the Internet (google &quot;G.711 source code&quot;). You =
can<BR>
&gt; implement G.711 in your big softswitch or IP-PBX... or you can impleme=
nt<BR>
&gt; it in some small embedded device.<BR>
&gt;<BR>
&gt; And it interoperates.<BR>
&gt;<BR>
&gt; We need that kind of codec for wideband.... which I would say is<BR>
&gt; &quot;royalty-free&quot; and needs to have &quot;open source&quot; imp=
lementations<BR>
&gt; available. &nbsp;&nbsp;(And yes, I know Speex is out there - I don't h=
ave a view<BR>
&gt; as to why it is not more widely implemented. &nbsp;And yes, I know Sky=
pe is<BR>
&gt; giving away SILK royalty-free, but it's not open source.)<BR>
&gt;<BR>
&gt; Can the IETF help with this? &nbsp;I don't know... but I think it's wo=
rth a<BR>
&gt; shot. &nbsp;If there is a group that is passionate about this (and the=
re<BR>
&gt; seems to be) then lets get the mailing list set up and have it go the<=
BR>
&gt; regular List -&gt; BOF -&gt; Working Group trajectory.<BR>
&gt;<BR>
&gt; In the best case perhaps we come out with the codec we want/need. &nbs=
p;At<BR>
&gt; the very worst I think we'd wind up with at least creating some good<B=
R>
&gt; discussions and requirements for what we do need.<BR>
&gt;<BR>
&gt; My 2 cents,<BR>
&gt; Dan<BR>
&gt;<BR>
_______________________________________________<BR>
dispatch mailing list<BR>
<a href=3D"dispatch@ietf.org">dispatch@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/dispatch">https://www.ietf=
.org/mailman/listinfo/dispatch</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--_000_C64C4C393ED5hsinnreiadobecom_--

From xiphmont@gmail.com  Wed Jun  3 19:12:50 2009
Return-Path: <xiphmont@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 B25C23A6C35; Wed,  3 Jun 2009 19:12:50 -0700 (PDT)
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 gAxfE+4UYJdD; Wed,  3 Jun 2009 19:12:50 -0700 (PDT)
Received: from mail-qy0-f204.google.com (mail-qy0-f204.google.com [209.85.221.204]) by core3.amsl.com (Postfix) with ESMTP id 608EB3A6BCC; Wed,  3 Jun 2009 19:12:50 -0700 (PDT)
Received: by qyk42 with SMTP id 42so723904qyk.29 for <multiple recipients>; Wed, 03 Jun 2009 19:12:48 -0700 (PDT)
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=fVUQrqqX2sqRuhT5W+DSYKlzPaPovfT/ccYv0Yhrojg=; b=XYSNAD8X3feutZO5dg/TSXIW3t2Q2iY14L5DZJfbFrWh2sDeGObg+PhsYeS5n8MxYm VWjcON6FmRxoHwcxfXjmiLJb+YrxFp8Prx4lkMYeUp8T14t31EPJ94+RgH3I0StMrN4d WmWpqh5Vcg2uPiH4HHamkprzhSoU8oLI1RgQY=
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=P0DtVmRxs06srK+L+Yf0yMx9fMxiftJGPBfs2TaE8WEVDT7LlZOqeSkyrgpW71i90f ThWDRP2x5aPk1+XkT7yY3tEyIsZCaa3RdD0J3w237ctfKGa9Xh3o34YkKzjxxHMgaDAF Q4AXm20NQb3zZX/LT6RBuWXGe4+1rI4FH3iWc=
MIME-Version: 1.0
Received: by 10.231.11.140 with SMTP id t12mr444732ibt.44.1244081568514; Wed,  03 Jun 2009 19:12:48 -0700 (PDT)
Date: Wed, 3 Jun 2009 22:12:48 -0400
Message-ID: <806dafc20906031912u230d418dn55af16feabb84019@mail.gmail.com>
From: Christopher Montgomery <xiphmont@gmail.com>
To: avt@ietf.org, dispatch@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 04 Jun 2009 02:12:50 -0000

I've been following this discussion through the archives, and it seems
time to dip a toe in. Apologies for the vaguely formal language, I'm
speaking for my organization.

I'm happy to see more IETF interest in taking up the subject of
royalty-free codecs for the Internet.  Several of our Xiph.Org members
have been quietly advocating for this within IETF for some time, and
it's nice to see the call coming from other sources as well. It's no
coincidence that the Internet's greatest success stories have all been
unencumbered.  Any new technology that rolls out with a royalty
pricetag has a steep uphill climb to do anything more than fragment
and muddy both social and business interoperability.

The Xiph.Org Foundation is a registered non-profit created toward
designing and deploying unencumered media codecs.  I'd like to
stand up and say officially that we would very much like to work with
the IETF on roaylty-free codecs.

Xiph.Org does two things: we research fundamental codec technology to
further the state of the art, then develop and deploy this research
without royalty or licensing restrictions.  We've created and made
available the Ogg container format and the Vorbis, Speex, FLAC, Theora
and CELT codecs.  Ogg-related protocols are already covered by a few
RFCs.  We exert no IP claims on our specifications and our reference
implementations are all BSD licensed.  Our codecs are a means to an
end, not an end in and of themselves.

Unfortunately, unencumbered access to basic media technology (a level
playing field) has meant reinventing and reimplementing from the
ground up. On the plus side, reinventing and reimplementing has
allowed us to use new [and rediscovered] techniques to better fit the
needs of the Internet.

...so we'd like to toss our hat into this ring and volunteer the
experience our own organization has gained in the past 15 years of
building royalty-free, unencumbered media tech from scratch. We
look forward to working with others who recognize the importance of
open and free media technology.

Monty
Xiph.Org

From jason.fischl@skype.net  Wed Jun  3 15:09:12 2009
Return-Path: <jason.fischl@skype.net>
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 570973A6C6F; Wed,  3 Jun 2009 15:09:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.223
X-Spam-Level: 
X-Spam-Status: No, score=0.223 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_ADOBE2=2.455, MANGLED_INXPNS=2.3, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067]
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 u1wHThb5OjhD; Wed,  3 Jun 2009 15:09:04 -0700 (PDT)
Received: from den-mipot-002.corp.ebay.com (den-mipot-002.corp.ebay.com [216.113.175.153]) by core3.amsl.com (Postfix) with ESMTP id E77A728C164; Wed,  3 Jun 2009 15:08:58 -0700 (PDT)
X-EBay-Corp: Yes
X-IronPort-AV: E=Sophos;i="4.41,300,1241420400"; d="scan'208";a="49412153"
Received: from den-exb-02.corp.ebay.com ([10.101.44.10]) by den-mipot-002.corp.ebay.com with ESMTP; 03 Jun 2009 15:08:59 -0700
Received: from DEN-EXM-04.corp.ebay.com ([10.241.16.37]) by DEN-EXB-02.corp.ebay.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 3 Jun 2009 16:08:59 -0600
Received: from 69.181.180.22 ([69.181.180.22]) by DEN-EXM-04.corp.ebay.com ([10.241.16.74]) via Exchange Front-End Server electron.corp.ebay.com ([10.101.112.26]) with Microsoft Exchange Server HTTP-DAV ; Wed,  3 Jun 2009 22:08:58 +0000
User-Agent: Microsoft-Entourage/12.17.0.090302
Date: Wed, 03 Jun 2009 15:08:41 -0700
From: Jason Fischl <jason.fischl@skype.net>
To: Eric Burger <eburger@standardstrack.com>, Henry Sinnreich <hsinnrei@adobe.com>
Message-ID: <C64C4279.D8F0%jason.fischl@skype.net>
Thread-Topic: [dispatch] [AVT] Proposal to form Internet Wideband Audio Codec WG
Thread-Index: Acnkl9pGVLeMkYWfMECYiGj9wx9NVA==
In-Reply-To: <A4C3A5AB-BC7B-4864-BBA5-23C9B227FCCB@standardstrack.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 03 Jun 2009 22:08:59.0655 (UTC) FILETIME=[E564C170:01C9E497]
X-Mailman-Approved-At: Thu, 04 Jun 2009 11:00:29 -0700
Cc: dispatch@ietf.org, avt@ietf.org
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 03 Jun 2009 22:09:12 -0000

I've requested a mailing list and it has been approved. It should be live in
a day or so. I'll post the details once it is live.

Jason



On 6/2/09 6:50 PM, "Eric Burger" <eburger@standardstrack.com> wrote:

> To directly answer Henry, having a mail list and the initial (and
> possibly detailed) discussion hosted at the IETF costs less than the
> discussion we are having here.  If a codec comes out of it, without
> having a BOF or WG, that's great!  If not, at least there was a forum
> for doing it.
> 
> I can also offer a SIP Forum list if people still really, really don't
> like the idea of even discussing the topic under even the most
> faintest of auspices of the IETF.
> 
> If you think I am schizophrenic by offering we can have a discussion
> in the IETF and at the same time I doubt we could ever have a formal
> work group to create the codec, you would be only slightly
> correct :-)  But seriously: the IETF (AVT in particular) can pickup
> the wire format for a codec, once the codec exists. Having a mail list
> WITHOUT A WORK GROUP give people who want to work on this a venue to
> do the work, without burdening the AD's, IESG, and the rest of the
> community. If a codec pops out, then we can run with it.
> 
> On Jun 2, 2009, at 12:44 PM, Spencer Dawkins wrote:
> 
>> I am not an area director, nor do i play one on IPTV, but my
>> suggestion for anyone interested would be to
>> 
>> - request a non-WG mailing list (from either of the RAI area
>> directors),
>> 
>> - announce it on this mailing list (and others that seem to be
>> appropriate, and
>> 
>> - start discussions, which the area directors typically look at when
>> judging whether there's enough interest and enough clue to justify
>> approving a BOF and/or chartering a working group.
>> 
>> I didn't see a mailing list included in Jason's proposal - if I
>> missed one, my apologies.
>> 
>> If people at the IETF can do this work, and want to do this work,
>> IETF process policies should not get in the way of that happening.
>> 
>> And I haven't heard of an AD turning down a request for a non-WG
>> mailing list yet, keeping in mind that one of said lists is ietf-
>> sailors, for people interested in sailing to/from/at IETF meetings -
>> the bar is (appropriately) low.
>> 
>> Thanks,
>> 
>> Spencer
>> ----- Original Message -----
>> From: Henry Sinnreich
>> To: Roni Even ; Jean-Marc Valin
>> Cc: dispatch@ietf.org ; Slava Borilin ; avt@ietf.org
>> Sent: Tuesday, June 02, 2009 11:12 AM
>> Subject: Re: [dispatch] [AVT] Proposal to form Internet Wideband
>> Audio Codec WG
>> 
>>> This leaves the other reasons I heard for doing it at the IETF
>> which is the
>>> price of participating
>> 
>> This is an important point.
>> Given the travel constraints for some of the most valuable potential
>> contributors and reviewers, could we envisage online work until the
>> economy improves, so that an eventual BOF to start with should not
>> be starved of attendees? An online BOF?
>> 
>> There are several free online meeting tools available...
>> 
>> How can this be done within the IETF policy?
>> 
>> Henry
>> 
>> 
>> On 6/2/09 10:57 AM, "Roni Even" <Even.roni@huawei.com> wrote:
>> 
>> Hi,
>> I do not want to sound like someone who is for IPR (I am not), but
>> why stop
>> at codec, let's require it for all IETF work. There are IPR on IETF
>> work
>> which is must simpler, in my view, than wide band audio codecs.
>> 
>> I think that we can start with "royalty free" even though I am not
>> sure that
>> it will accepted as part of the charter of any other work group so
>> why pick
>> on codecs which require more work.
>> 
>> This leaves the other reasons I heard for doing it at the IETF which
>> is the
>> price of participating (cheaper than being an ITU-T member) and
>> maybe design
>> less expensive characterization tests.
>> 
>> Roni
>> 
>> 
>> -----Original Message-----
>> From: Jean-Marc Valin [mailto:jean-marc.valin@octasic.com]
>> Sent: Tuesday, June 02, 2009 6:14 PM
>> To: Roni Even
>> Cc: 'Slava Borilin'; avt@ietf.org; 'Jason Fischl';dispatch@ietf.org;
>> hsinnrei@adobe.com
>> Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband
>> Audio Codec
>> WG
>> 
>> Hi,
>> 
>> Roni Even wrote:
>>> 
>>> I am not sure what prevented you from doing it today at the ITU or
>>> MPEG, why do you see the IETF handling it differently.
>>> 
>>> I would also like to remind you and Jean-Marc that once you are
>>> bringing work to a standard body it may require collaboration with
>>> other people who will have other proposals that will also address
>> the
>>> same requirements and you may need to invest money in comparative
>>> testing by independent listening labs.
>>> 
>>> I also think that you will need to supply the codec in source code
>> and
>>> provide copy right to the IETF.
>>> 
>> 
>> I am well aware that bringing work to the IETF would require
>> collaboration with others. I am not seeking control over the work I am
>> currently doing and would really welcome such collaboration. The
>> idea is
>> only to have the best wideband codec possible without IPR issues.
>> Given
>> the ITU and MPEG track record, I think it would be very unlikely for
>> any
>> of those organisations to work on an IPR-free codec.
>> 
>> I also agree with Henry that "the Internet has different criteria than
>> ITU-T networks may have". Internet adoption follows different patterns
>> than adoption in the ITU primary target markets. For example, the
>> Internet has more consumer-reconfigurable software, while the ITU
>> has to
>> deal with a lot of fixed hardware deployments. At the ITU, it makes
>> sense to invest large sums of money into testing and
>> characterisation of
>> codecs because the codecs deployed there usually stay around for a
>> long
>> time and the infrastructure investments are usually very large. On the
>> other hand, I would say the investments in codecs for the Internet are
>> comparatively smaller and, while testing is still important, it is not
>> as critical as it is for the ITU.
>> 
>> It's also a choice one has to make. It is unlikely that companies
>> would
>> invest money in expensive testing if they are not going to obtain
>> royalties in return. However, I think we may be able to define some
>> more
>> lightweight (collaborative?) testing that is sufficient and doesn't
>> involve as much investments as what the ITU does. For the Internet, I
>> believe an IPR-free codec that everyone agrees performs well is better
>> than a patent-encumbered codec that has had more extensive testing.
>> This
>> is again another difference with the ITU: patent-encumbered codecs
>> tend
>> to hurt a lot more on the Internet because many applications (e.g.
>> giving away the client) are very hard (or impossible) when one has to
>> pay per-channel royalties.
>> 
>> As for the source code issue you pointed out, all the Xiph codecs are
>> already published under a very permissive open source license (BSD),
>> so
>> this would not really change.
>> 
>>     Jean-Marc
>> 
>>> Roni
>>> 
>>> 
>>> 
>>> *From:* avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] *On
>> Behalf
>>> Of *Slava Borilin
>>> *Sent:* Monday, June 01, 2009 11:50 PM
>>> *To:* jean-marc.valin@octasic.com
>>> *Cc:* avt@ietf.org; Jason Fischl
>>> *Subject:* Re: [AVT] [dispatch] Proposal to form Internet Wideband
>>> Audio Codec WG
>>> 
>>> 
>>> 
>>> Agree with Jean-Marc.
>>> SPIRIT is interested to contribute as well - having a dozen of
>> proprietary
>> codecs developed, including
>>> one specifically desgined for internet (SPIRIT IP-MR, which is now
>> under
>> WGLC on draft-ietf-avt-rtp-ipmr-04) -
>>> multi-rate, scalable, adaptive, wideband codec.
>>> 
>>> We can also continue this work with IETF.
>>> 
>>> Moreover, most if not all efforts coming from ITU on codecs
>> unfortunately
>> are NOT really focused on
>>> internet-specific codecs (that's why several companies have had to
>> invent)
>> - as ITU preference is mainly
>>> specific (i.e. cellular) networks at first.
>>> 
>>> however, as we see the greant rise of pure "internet-basd
>> communications"
>> (skype, webex/citrix, and many others) -
>>> we all (and users) are suffering from inefficiency in all currently
>> "standard" codecs and ambiguity in the choice of
>>> internet-targeted ones.
>>> 
>>> Again, we probably can put together enough number of contributors
>> to the
>> WG to have the expertise.
>>> 
>>> regards,
>>> Slava Borilin
>>> 
>>> --
>>> John Lazzaro wrote:
>>> 
>>>     A traditional response to this type of request is to note that
>> the
>> IETF
>>> 
>>>     really doesn't have much in the way of expertise in audio codec
>> design.
>>> 
>>>     I don't see many of the regulars who present at the AES codec
>> paper
>> sessions
>>> 
>>>     posting here on AVT (ditto ICASSP paper sessions for voice
>> codecs).
>> It's
>>> 
>>>     a full-time job to keep up-to-date and contribute to that
>>> 
>>>     signal-processing lore.
>>> 
>>> 
>>> 
>>> Well, there's no reason that the IETF cannot build such an expertise
>>> in audio codecs. This is actually something in which I'd be
>> interested
>>> in getting involved and I'm sure others at Xiph.Org would be
>>> interested as well. We have several people with audio codec
>> expertise
>>> from working on Vorbis, Speex and (more recently) CELT. It turns out
>>> that the CELT codec currently under development at Xiph actually
>> meets
>>> most of the requirements from the original proposal in being a very
>>> low delay codec with adaptive bit-rate and sampling rate (up to 48
>>> kHz), scalable complexity, and good robustness to packet loss.
>> We'd be
>>> willing to continue the development with the IETF. Even if not with
>>> CELT, it's still like to be involved in such a new WG.
>>> 
>>> Cheers,
>>> 
>>>    Jean-Marc
>> 
>> 
>> 
>> 
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch


From dean.willis@softarmor.com  Wed Jun  3 15:16:30 2009
Return-Path: <dean.willis@softarmor.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 DBD803A6CF7; Wed,  3 Jun 2009 15:16:30 -0700 (PDT)
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 XaW1OwgVa7i0; Wed,  3 Jun 2009 15:16:30 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id AF68128C1AC; Wed,  3 Jun 2009 15:16:25 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-182-198-42.tx.res.rr.com [76.182.198.42]) (authenticated bits=0) by nylon.softarmor.com (8.14.3/8.14.3/Debian-5) with ESMTP id n53MGPSi015788 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 3 Jun 2009 17:16:27 -0500
Message-Id: <94890500-A706-4B1A-9BA9-C0D632257E54@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Dan York <dyork@voxeo.com>
In-Reply-To: <CE8BFF1C-6F4D-4AF7-A5A7-20FD7C516D12@voxeo.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 3 Jun 2009 17:16:20 -0500
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <4A2541B9.2000805@octasic.com> <00d501c9e39a$dcbbbe50$96333af0$%roni@huawei.com> <D1611ACB-4739-4A65-94F0-403FC24CDC43@cs.columbia.edu> <B678F1CB-0000-4774-BF03-6B53C333F15D@standardstrack.com> <CE8BFF1C-6F4D-4AF7-A5A7-20FD7C516D12@voxeo.com>
X-Mailer: Apple Mail (2.935.3)
X-Mailman-Approved-At: Thu, 04 Jun 2009 11:00:29 -0700
Cc: dispatch@ietf.org, avt@ietf.org
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec WG
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, 03 Jun 2009 22:16:31 -0000

On Jun 3, 2009, at 2:45 PM, Dan York wrote:

> I think we ultimately need a "G.711 for wideband", i.e. a wideband  
> codec that anyone can implement in any device.  I'd argue that a  
> large part of the reason we are "stuck" with so many people in VoIP  
> using G.711 is precisely because ANYONE can implement it in  
> basically ANY device.  You can buy a G.711 codec implementation or  
> you can write your own or find some code on the Internet (google "G. 
> 711 source code"). You can implement G.711 in your big softswitch or  
> IP-PBX... or you can implement it in some small embedded device.

We have such a codec: 16 bit sampling at 44.1 khz, aka "what your CD  
player does in stereo", or L16 audio as defined in RFC 1890.

While there might be some IPR on it, it clearly hasn't kept everybody  
and their dog from playing the audio format on devices ranging from a  
$3 CD player on up.


We also have RFC 3190, which does RTP format for 12-bit DAT audio and  
20 and 24 bit linear sampled audio.


So what is it that we need for a "wideband G.711" that isn't already  
in there somewhere?


It sounds like what you want is more a wideband iLBC, which is an  
intellectually much larger challenge.

--
Dean


From drage@alcatel-lucent.com  Thu Jun  4 03:00:38 2009
Return-Path: <drage@alcatel-lucent.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8BC7F3A6DDF; Thu,  4 Jun 2009 03:00:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.649
X-Spam-Level: 
X-Spam-Status: No, score=-2.649 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XF3XncQcRBNy; Thu,  4 Jun 2009 03:00:37 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by core3.amsl.com (Postfix) with ESMTP id 5559B3A6C17; Thu,  4 Jun 2009 03:00:36 -0700 (PDT)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n54A0aDo029072 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 4 Jun 2009 12:00:36 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.47]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Thu, 4 Jun 2009 12:00:36 +0200
From: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
To: Dan York <dyork@voxeo.com>, "dispatch@ietf.org" <dispatch@ietf.org>
Date: Thu, 4 Jun 2009 12:00:34 +0200
Thread-Topic: [dispatch] [AVT] Proposal to form Internet Wideband Audio Codec	WG
Thread-Index: Acnkg+tPW7/Qit8kSMO3DzsL4DUqDgAdZA9w
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE206E9C8D8@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <AA5A65FC22B6F145830AC0EAC7586A6C04BF8E77@mail-srv.spiritcorp.com> <00a401c9e388$b25c2350$171469f0$%roni@huawei.com> <4A2541B9.2000805@octasic.com> <00d501c9e39a$dcbbbe50$96333af0$%roni@huawei.com> <D1611ACB-4739-4A65-94F0-403FC24CDC43@cs.columbia.edu> <B678F1CB-0000-4774-BF03-6B53C333F15D@standardstrack.com> <CE8BFF1C-6F4D-4AF7-A5A7-20FD7C516D12@voxeo.com>
In-Reply-To: <CE8BFF1C-6F4D-4AF7-A5A7-20FD7C516D12@voxeo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
X-Mailman-Approved-At: Thu, 04 Jun 2009 11:00:29 -0700
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVT] [dispatch] Proposal to form Internet Wideband Audio Codec	WG
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, 04 Jun 2009 10:00:38 -0000

I would argue that G.711 is implemented, not because anyone can implement i=
t, but because everyone else has implemented it. It essentially forms the l=
owest common denominator for interoperability. If fancy codec x doesn't wor=
k, then assuming you have the bandwidth availabile, G.711 probably will. An=
d I suspect it is royalty free not because it was always so, but because an=
y IPR that existed has pretty much expired by now.

G.711 is also the one codec that is probably the most neutral to transcodin=
g. I can do to codec A to G.711 and back to codec A with less impact that w=
ith any other intermediate codec.

For wideband there probably is not any one codec that has achieved that pos=
ition.

I don't believe building a better, even royalty free codec, will guarantee =
a position in the market place. The world is littered with better solutions=
 that never made it. You need a market where everyone chooses to implement =
it so that you can use that codec without having to go to transcoding. Past=
ing IETF on the front cover does not achieve that.

I don't really have a problem with people trying to sit down and design a n=
ew codec and IETF then publishing it. Without some other selling point howe=
ver it just becomes yet another codec competing for market place. As such, =
put it somewhere where it does not interfere with other work. Sticking it o=
n a separate mailing list, and not letting it compete for valuable IETF fac=
e to face slots as a working group is fine.

regards

Keith
=20

> -----Original Message-----
> From: dispatch-bounces@ietf.org=20
> [mailto:dispatch-bounces@ietf.org] On Behalf Of Dan York
> Sent: Wednesday, June 03, 2009 8:46 PM
> To: dispatch@ietf.org
> Cc: avt@ietf.org
> Subject: Re: [dispatch] [AVT] Proposal to form Internet=20
> Wideband Audio Codec WG
>=20
> I've been reading this thread with great interest as for the=20
> past probably 6 years or so I've been saying to anyone who=20
> will listen (and to those who won't ;-) that one factor that=20
> will help "IP
> communications/VoIP/UC/whatever-marketing-term-we-want-to-rename-our-
> products-to-this-week" to really find wide adoption is to=20
> provide a "rich communication experience" better than what=20
> people are used to now.
>=20
> Wideband audio is, to me, a huge part of that.
>=20
> However, I completely agree with Henning on this point:
>=20
> > On Jun 2, 2009, at 12:15 PM, Henning Schulzrinne wrote:
> >
> >> However, if we don't do this, we are stuck with the status=20
> quo, which=20
> >> is not all that satisfactory.
>=20
>=20
> The status quo is not satisfactory.  If you want to add=20
> wideband audio =20
> to your product, you've got an alphabet soup of mutually=20
> incompatible =20
> options with vastly different licensing terms/fees/options=20
> and source =20
> code availability.
>=20
> I think we ultimately need a "G.711 for wideband", i.e. a wideband =20
> codec that anyone can implement in any device.  I'd argue=20
> that a large =20
> part of the reason we are "stuck" with so many people in VoIP=20
> using G.=20
> 711 is precisely because ANYONE can implement it in basically ANY =20
> device.  You can buy a G.711 codec implementation or you can write =20
> your own or find some code on the Internet (google "G.711 source =20
> code"). You can implement G.711 in your big softswitch or=20
> IP-PBX... or =20
> you can implement it in some small embedded device.
>=20
> And it interoperates.
>=20
> We need that kind of codec for wideband.... which I would say is =20
> "royalty-free" and needs to have "open source" implementations =20
> available.   (And yes, I know Speex is out there - I don't=20
> have a view =20
> as to why it is not more widely implemented.  And yes, I know=20
> Skype is =20
> giving away SILK royalty-free, but it's not open source.)
>=20
> Can the IETF help with this?  I don't know... but I think=20
> it's worth a =20
> shot.  If there is a group that is passionate about this (and there =20
> seems to be) then lets get the mailing list set up and have=20
> it go the =20
> regular List -> BOF -> Working Group trajectory.
>=20
> In the best case perhaps we come out with the codec we=20
> want/need.  At =20
> the very worst I think we'd wind up with at least creating some good =20
> discussions and requirements for what we do need.
>=20
> My 2 cents,
> Dan
>=20
> --=20
> Dan York, Director of Conversations
> Voxeo Corporation   http://www.voxeo.com  dyork@voxeo.com
> Phone: +1-407-455-5859    Skype: danyork
>=20
> Join the Voxeo conversation:
> Blogs: http://blogs.voxeo.com  http://www.disruptivetelephony.com
> Twitter: http://twitter.com/voxeo  http://twitter.com/danyork
> Facebook: http://www.voxeo.com/facebook
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
> =

From singer@apple.com  Fri Jun  5 11:16:46 2009
Return-Path: <singer@apple.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 4C3683A6D6F for <avt@core3.amsl.com>; Fri,  5 Jun 2009 11:16:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.283
X-Spam-Level: 
X-Spam-Status: No, score=-106.283 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_MILLIONSOF=0.315, 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 aXCFI9qZCF8u for <avt@core3.amsl.com>; Fri,  5 Jun 2009 11:16:45 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id 313BF3A6B58 for <avt@ietf.org>; Fri,  5 Jun 2009 11:16:45 -0700 (PDT)
Received: from relay11.apple.com (relay11.apple.com [17.128.113.48]) by mail-out4.apple.com (Postfix) with ESMTP id 9748F66634D3; Fri,  5 Jun 2009 11:16:48 -0700 (PDT)
Received: from relay11.apple.com (unknown [127.0.0.1]) by relay11.apple.com (Symantec Brightmail Gateway) with ESMTP id 7E6DE28087; Fri,  5 Jun 2009 11:16:48 -0700 (PDT)
X-AuditID: 11807130-a3cd9bb0000025da-cc-4a29610f6abb
Received: from [10.0.1.8] (unknown [17.151.94.143]) by relay11.apple.com (Apple SCV relay) with ESMTP id E278F2807E; Fri,  5 Jun 2009 11:16:47 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p06240804c64f10586260@[10.0.1.8]>
In-Reply-To: <31d1be720905200905o53281cbja084ea69cf30ec0@mail.gmail.com>
References: <p06240865c638d26a3381@10.177.192.68> <31d1be720905200905o53281cbja084ea69cf30ec0@mail.gmail.com>
Date: Fri, 5 Jun 2009 11:16:08 -0700
To: Greg Herlein <gherlein@herlein.com>
From: David Singer <singer@apple.com>
Content-Type: multipart/alternative; boundary="============_-967896689==_ma============"
X-Brightmail-Tracker: AAAAAA==
Cc: http-live-streaming-review@group.apple.com, avt@ietf.org
Subject: Re: [AVT] iPhone streaming Internet-Draft posted
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, 05 Jun 2009 18:16:46 -0000

--============_-967896689==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

Greg, thanks for the comments.  Responses inline...

At 9:05  -0700 20/05/09, Greg Herlein wrote:
>>- in 6.1: "The server MUST create a URI for each media file that 
>>will allow its clients to obtain the file."
>>
>>   - why? Divide the stream into many files and then the client has 
>>to know the file names and ask one by one?
>>
>As discussed earlier the protocol distributes media as discrete 
>files via HTTP to enable use of its caching infrastructure.
>
>
>Yes, it was discussed earlier.  John Lazzaro raised some questions 
>that were raised several years ago in regards to this being a bad 
>idea.  I have not seen anyone from Apple respond to that.
>

We think that those minutes addressed a different idea. It's not 
clear that they apply to this protocol.

>>- you specify a means to reload a playlist but not to signal a 
>>client that there is a new playlist - so you poll.  Poor form.
>>
>
>Our experience is that polling is efficient if the client polls at 
>the right time, and in a real-time playback system it is generally 
>possible to achieve this.
>
>
>I'd like to hear more about that.  It seems that your real-time 
>polling interval is controlled indirectly by the size of the file 
>(see above).  Yet once you provide for trick play this stops being 
>time-based.  This seems to be a distinctly weak approach to 
>controlling polling. 
>

The protocol is tuned for large-scale, non-interactive, 
broadcast-style viewing. Clients can seek within the window presented 
by the playlist. They can implement fast-forward and reverse playback 
within it as well if they choose, but the protocol does not sacrifice 
scalability in return for additional "trickiness" that requires 
one-to-one interaction with the content provider.

>I also raised questions about the choice of playlist format - 
>specifically using a non-standards-based audio playlist format 
>instead of something like SMIL that was designed for this kind of 
>thing.  Comments on that?
>

We looked at SMIL. It's more complicated than M3U and doesn't add 
much value for our uses. We would have had to make a new SMIL profile 
and then extend it to add the same extensions to it that we need for 
M3U.

People who have experimented with the protocol tell us that 
they really like the simplicity of M3U, which makes it easy to do 
things like dynamic playlist generation.

At 14:51  -0700 22/05/09, Greg Herlein wrote:
>If I understand it, the objective of this effort is to leverage the web
>server infrastructure that is already understood and deployed in a way that
>can transport video.  The core use case is a desire to have some video
>source (which may be psuedo-live or recorded) and deliver it to thousands or
>millions of users over the existing internet.   The desire is to design a
>protocol that can operate on the traditional port 80 infrastructure in such
>a way that caching and CDN technology can scale the traffic.  Trick play and
>all playback is handled in the client and is outside the scope of the
>protocol.
>

That's correct.

>If I am correct, is there actually any need for a playlist?  I would suggest
>that all that is needed in a HTTP reply is the URI that will hold the next
>chunk of media and perhaps a time that the URIl will become active.  The
>client could then invoke the logic to go get that URI at the appropriate
>time.
>

We experimented with this approach, but it turns out that adding 
custom headers to the HTTP response is not particularly compatible 
with how the large CDNs work.

The playlist approach has another benefit, in that it allows content 
providers to express a window of previous content that a client can 
seek backward into.
-- 
David Singer
Multimedia Standards, Apple Inc.
--============_-967896689==_ma============
Content-Type: text/html; charset="us-ascii"

<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
 --></style><title>Re: [AVT] iPhone streaming Internet-Draft
posted</title></head><body>
<div>Greg, thanks for the comments.&nbsp; Responses inline...</div>
<div><br></div>
<div>At 9:05&nbsp; -0700 20/05/09, Greg Herlein wrote:</div>
<blockquote type="cite" cite>
<blockquote type="cite" cite>
<blockquote><tt>- in 6.1: &quot;The server MUST create a URI for each
media file that will allow its clients to obtain the file.&quot;<br>
<br>
&nbsp; - why? Divide the stream into many files and then the client
has to know the file names and ask one by one?</tt><br>
</blockquote>
</blockquote>
<blockquote>As discussed earlier the protocol distributes media as
discrete files via HTTP to enable use of its caching
infrastructure.<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br>
Yes, it was discussed earlier.&nbsp; John Lazzaro raised some
questions that were raised several years ago in regards to this being
a bad idea.&nbsp; I have not seen anyone from Apple respond to
that.<br>
</blockquote>
<div><br></div>
<div>We think that those minutes addressed a different idea. It's not
clear that they apply to this protocol.</div>
<div><br></div>
<blockquote type="cite" cite>
<blockquote type="cite" cite>
<blockquote>- you specify a means to reload a playlist but not to
signal a client that there is a new playlist - so you poll.&nbsp; Poor
form.<br>
</blockquote>
</blockquote>
<blockquote><br></blockquote>
<blockquote>Our experience is that polling is efficient if the client
polls at the right time, and in a real-time playback system it
is&nbsp;generally possible to achieve this.<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br>
I'd like to hear more about that.&nbsp; It seems that your real-time
polling interval is controlled indirectly by the size of the file (see
above).&nbsp; Yet once you provide for trick play this stops being
time-based.&nbsp; This seems to be a distinctly weak approach to
controlling polling.&nbsp;<br>
</blockquote>
<div><br></div>
<div>The protocol is tuned for large-scale, non-interactive,
broadcast-style viewing. Clients can seek within the window presented
by the playlist. They can implement fast-forward and reverse playback
within it as well if they choose, but the protocol does not sacrifice
scalability in return for additional &quot;trickiness&quot; that
requires one-to-one interaction with the content provider.</div>
<div><br></div>
<blockquote type="cite" cite>I also raised questions about the choice
of playlist format - specifically using a non-standards-based audio
playlist format instead of something like SMIL that was designed for
this kind of thing.&nbsp; Comments on that?<br>
</blockquote>
<div><br></div>
<div>We looked at SMIL. It's more complicated than M3U and doesn't add
much value for our uses. We would have had&nbsp;to make a new SMIL
profile and then extend it to&nbsp;add the same extensions to it that
we need for M3U.</div>
<div><br></div>
<div>People who have experimented with&nbsp;the protocol tell us that
they&nbsp;really like the simplicity of M3U, which makes it easy to do
things like dynamic playlist generation.</div>
<div><br></div>
<div>At 14:51&nbsp; -0700 22/05/09, Greg Herlein wrote:</div>
<blockquote type="cite" cite>If I understand it, the objective of this
effort is to leverage the web<br>
server infrastructure that is already understood and deployed in a way
that<br>
can transport video. &nbsp;The core use case is a desire to have some
video</blockquote>
<blockquote type="cite" cite>source (which may be psuedo-live or
recorded) and deliver it to thousands or<br>
millions of users over the existing internet. &nbsp;&nbsp;The desire
is to design a<br>
protocol that can operate on the traditional port 80 infrastructure in
such<br>
a way that caching and CDN technology can scale the traffic.
&nbsp;Trick play and<br>
all playback is handled in the client and is outside the scope of
the<br>
protocol.<br>
</blockquote>
<div><br></div>
<div>That's correct.</div>
<div><br></div>
<blockquote type="cite" cite>If I am correct, is there actually any
need for a playlist? &nbsp;I would suggest<br>
that all that is needed in a HTTP reply is the URI that will hold the
next<br>
chunk of media and perhaps a time that the URIl will become active.
&nbsp;The<br>
client could then invoke the logic to go get that URI at the
appropriate<br>
time.<br>
</blockquote>
<div><br></div>
<div>We experimented with this approach, but it turns out that adding
custom headers to the HTTP response is not particularly compatible
with how the large CDNs work.</div>
<div><br></div>
<div>The playlist approach has another benefit, in that it allows
content providers to express a window of previous content that a
client can seek backward into.</div>
<x-sigsep><pre>-- 
</pre></x-sigsep>
<div>David Singer<br>
Multimedia Standards, Apple Inc.</div>
</body>
</html>
--============_-967896689==_ma============--

From alex.giladi@gmail.com  Fri Jun  5 11:27:22 2009
Return-Path: <alex.giladi@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 C5DE03A6D2A for <avt@core3.amsl.com>; Fri,  5 Jun 2009 11:27:22 -0700 (PDT)
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 VnoJAHNZE+Lj for <avt@core3.amsl.com>; Fri,  5 Jun 2009 11:27:21 -0700 (PDT)
Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by core3.amsl.com (Postfix) with ESMTP id 949583A69D8 for <avt@ietf.org>; Fri,  5 Jun 2009 11:27:21 -0700 (PDT)
Received: by bwz9 with SMTP id 9so1688928bwz.37 for <avt@ietf.org>; Fri, 05 Jun 2009 11:27:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=8y3wD249pLeHxLYOxevZ8MsG07zzgVfUUC4P/bo0sSo=; b=OI5mhTrwvZ6zb2D3jU4a4f3X2pFm8NG9Lcih320Wnas+3NOudkHt/zOWMg9IdbE5Hg pcvrGXb82vifjsv8wJplMgarfO/XJ4/1JmIp2JsDlzTYY/TwjxyvLb2zcG9pSvl3HMpy l4AcuonjqW5KCuKE4/UEeQoWDvt9qtxGVoUeI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=TlR63pW1tocTxNFP0XTAvOJWLsMYdNtlm8zJsj76/b5r6wSdeOElvhmjExF157Zh90 oje1cUoR6JaqZ+TA7bjSu96wRTDx01kTDwKcVU5YVJd3WGd8KHIivnQHQSzNAHbJ6hM5 irre/V/38XiuxeShkKRgdoeDu4FLXbXqY0kco=
MIME-Version: 1.0
Received: by 10.204.115.135 with SMTP id i7mr3373774bkq.178.1244226440945;  Fri, 05 Jun 2009 11:27:20 -0700 (PDT)
In-Reply-To: <p06240804c64f10586260@10.0.1.8>
References: <p06240865c638d26a3381@10.177.192.68> <31d1be720905200905o53281cbja084ea69cf30ec0@mail.gmail.com> <p06240804c64f10586260@10.0.1.8>
Date: Fri, 5 Jun 2009 14:27:20 -0400
Message-ID: <57a9e15d0906051127j23e57e13l3e1841789cb5edaf@mail.gmail.com>
From: Alex Giladi <alex.giladi@gmail.com>
To: David Singer <singer@apple.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: http-live-streaming-review@group.apple.com, avt@ietf.org
Subject: Re: [AVT] iPhone streaming Internet-Draft posted
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, 05 Jun 2009 18:27:22 -0000

On Fri, Jun 5, 2009 at 2:16 PM, David Singer <singer@apple.com> wrote:
<...>
> We looked at SMIL. It's more complicated than M3U and doesn't add much va=
lue
> for our uses. We would have had=C2=A0to make a new SMIL profile and then =
extend
> it to=C2=A0add the same extensions to it that we need for M3U.
> People who have experimented with=C2=A0the protocol tell us that they=C2=
=A0really like
> the simplicity of M3U, which makes it easy to do things like dynamic
> playlist generation.

What about ADI?

Alex.

From singer@apple.com  Fri Jun  5 15:01:46 2009
Return-Path: <singer@apple.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 25FD23A6894 for <avt@core3.amsl.com>; Fri,  5 Jun 2009 15:01:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.441
X-Spam-Level: 
X-Spam-Status: No, score=-106.441 tagged_above=-999 required=5 tests=[AWL=0.158, 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 muWGmFUW4MEj for <avt@core3.amsl.com>; Fri,  5 Jun 2009 15:01:45 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 84A523A6886 for <avt@ietf.org>; Fri,  5 Jun 2009 15:01:45 -0700 (PDT)
Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out3.apple.com (Postfix) with ESMTP id 167246353EF3; Fri,  5 Jun 2009 15:01:49 -0700 (PDT)
Received: from relay16.apple.com (unknown [127.0.0.1]) by relay16.apple.com (Symantec Brightmail Gateway) with ESMTP id 00A9F5A0002; Fri,  5 Jun 2009 15:01:48 -0700 (PDT)
X-AuditID: 11807137-aad73bb00000380b-d8-4a2995ccd5e7
Received: from [10.0.1.8] (unknown [17.151.94.143]) by relay16.apple.com (Apple SCV relay) with ESMTP id 89ED1558003; Fri,  5 Jun 2009 15:01:48 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p06240804c64f44559190@[10.0.1.8]>
In-Reply-To: <57a9e15d0906051127j23e57e13l3e1841789cb5edaf@mail.gmail.com>
References: <p06240865c638d26a3381@10.177.192.68> <31d1be720905200905o53281cbja084ea69cf30ec0@mail.gmail.com> <p06240804c64f10586260@10.0.1.8> <57a9e15d0906051127j23e57e13l3e1841789cb5edaf@mail.gmail.com>
Date: Fri, 5 Jun 2009 14:59:45 -0700
To: Alex Giladi <alex.giladi@gmail.com>
From: David Singer <singer@apple.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
Cc: http-live-streaming-review@group.apple.com, avt@ietf.org
Subject: Re: [AVT] iPhone streaming Internet-Draft posted
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, 05 Jun 2009 22:01:46 -0000

At 14:27  -0400 5/06/09, Alex Giladi wrote:
>
>What about ADI?
>

hm...probably not "Aircraft De-Ice and Inhibitor". Less unlikely is 
"AutoCAD Device Interface". I guess we can hope for a link to the 
"American Distilling Institute", we can fear "Advanced Discriminating 
Interceptor", or tune in to "Acoustic Directional Intensity"...

or I could ask...which ADI do you speak of?
-- 
David Singer
Multimedia Standards, Apple Inc.

From Even.roni@huawei.com  Sat Jun  6 01:15:22 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 510E33A67F2 for <avt@core3.amsl.com>; Sat,  6 Jun 2009 01:15:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.014
X-Spam-Level: 
X-Spam-Status: No, score=-2.014 tagged_above=-999 required=5 tests=[AWL=0.585,  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 zYeImQSydODC for <avt@core3.amsl.com>; Sat,  6 Jun 2009 01:15:21 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 7513B3A677C for <avt@ietf.org>; Sat,  6 Jun 2009 01:15:21 -0700 (PDT)
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 <0KKT00IXL5LNW7@szxga04-in.huawei.com> for avt@ietf.org; Sat, 06 Jun 2009 16:15:23 +0800 (CST)
Received: from huawei.com ([172.24.1.6]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KKT00AXH5LN5M@szxga04-in.huawei.com> for avt@ietf.org; Sat, 06 Jun 2009 16:15:23 +0800 (CST)
Received: from windows8d787f9 (bzq-79-183-125-11.red.bezeqint.net [79.183.125.11]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KKT0081L5JRVJ@szxml02-in.huawei.com>; Sat, 06 Jun 2009 16:15:23 +0800 (CST)
Date: Sat, 06 Jun 2009 11:12:56 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <p06240804c64f44559190@[10.0.1.8]>
To: 'David Singer' <singer@apple.com>, 'Alex Giladi' <alex.giladi@gmail.com>
Message-id: <006501c9e67e$c14df7f0$43e9e7d0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcnmKUCuZ/PK8JRMTs2Iyb7RN6c9ZQAVGgHw
References: <p06240865c638d26a3381@10.177.192.68> <31d1be720905200905o53281cbja084ea69cf30ec0@mail.gmail.com> <p06240804c64f10586260@10.0.1.8> <57a9e15d0906051127j23e57e13l3e1841789cb5edaf@mail.gmail.com> <p06240804c64f44559190@[10.0.1.8]>
Cc: http-live-streaming-review@group.apple.com, avt@ietf.org
Subject: Re: [AVT] iPhone streaming Internet-Draft posted
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, 06 Jun 2009 08:15:22 -0000

David,
Adi means an ornament in my mother tongue (it is in the Bible). 
Roni

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of David
Singer
Sent: Saturday, June 06, 2009 1:00 AM
To: Alex Giladi
Cc: http-live-streaming-review@group.apple.com; avt@ietf.org
Subject: Re: [AVT] iPhone streaming Internet-Draft posted

At 14:27  -0400 5/06/09, Alex Giladi wrote:
>
>What about ADI?
>

hm...probably not "Aircraft De-Ice and Inhibitor". Less unlikely is 
"AutoCAD Device Interface". I guess we can hope for a link to the 
"American Distilling Institute", we can fear "Advanced Discriminating 
Interceptor", or tune in to "Acoustic Directional Intensity"...

or I could ask...which ADI do you speak of?
-- 
David Singer
Multimedia Standards, Apple Inc.
_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt


From gherlein@herlein.com  Sat Jun  6 07:54:00 2009
Return-Path: <gherlein@herlein.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 A918E3A6A04 for <avt@core3.amsl.com>; Sat,  6 Jun 2009 07:54:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level: 
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 XcifInDYV4tn for <avt@core3.amsl.com>; Sat,  6 Jun 2009 07:53:59 -0700 (PDT)
Received: from mail-pz0-f177.google.com (mail-pz0-f177.google.com [209.85.222.177]) by core3.amsl.com (Postfix) with ESMTP id 561C63A69D1 for <avt@ietf.org>; Sat,  6 Jun 2009 07:53:59 -0700 (PDT)
Received: by pzk7 with SMTP id 7so247011pzk.29 for <avt@ietf.org>; Sat, 06 Jun 2009 07:54:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.144.9 with SMTP id r9mr1588353wfd.12.1244300040463; Sat,  06 Jun 2009 07:54:00 -0700 (PDT)
In-Reply-To: <p06240804c64f10586260@10.0.1.8>
References: <p06240865c638d26a3381@10.177.192.68> <31d1be720905200905o53281cbja084ea69cf30ec0@mail.gmail.com> <p06240804c64f10586260@10.0.1.8>
Date: Sat, 6 Jun 2009 07:54:00 -0700
Message-ID: <31d1be720906060754x4eb29b34g3629890cb0814495@mail.gmail.com>
From: Greg Herlein <gherlein@herlein.com>
To: David Singer <singer@apple.com>
Content-Type: multipart/alternative; boundary=000e0cd2de44e7e60d046baf2dd1
Cc: http-live-streaming-review@group.apple.com, avt@ietf.org
Subject: Re: [AVT] iPhone streaming Internet-Draft posted
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, 06 Jun 2009 14:54:00 -0000

--000e0cd2de44e7e60d046baf2dd1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

All:

Yes, it was discussed earlier.  John Lazzaro raised some questions that were
> raised several years ago in regards to this being a bad idea.  I have not
> seen anyone from Apple respond to that.
>
>  We think that those minutes addressed a different idea. It's not clear
> that they apply to this protocol.
>

They apllies to the idea of using HTTP to stream media, as far as I can
understand.  I'm sensitive to your desires but wonder about the
implementation/standard.  If there's a market for a solution that solution
will find a way to exist...  choosing a best good way for it to be
standardardized is a *good thing*

>
> The protocol is tuned for large-scale, non-interactive, broadcast-style
> viewing. Clients can seek within the window presented by the playlist. They
> can implement fast-forward and reverse playback within it as well if they
> choose, but the protocol does not sacrifice scalability in return for
> additional "trickiness" that requires one-to-one interaction with the
> content provider.
>

OK, makes sense.

> I also raised questions about the choice of playlist format - specifically
> using a non-standards-based audio playlist format instead of something like
> SMIL that was designed for this kind of thing.  Comments on that?
>
>
> We looked at SMIL. It's more complicated than M3U and doesn't add much
> value for our uses. We would have had to make a new SMIL profile and then
> extend it to add the same extensions to it that we need for M3U.
>
> People who have experimented with the protocol tell us that they really
> like the simplicity of M3U, which makes it easy to do things like dynamic
> playlist generation.
>

"Because M3U is easy and SMIL is hard" seems like a poor reason to use to a
bunch of Engineers.  You are going to have to use extensions to couple it to
HTTP no matter what playlist format you use.  M3U is full screen only - no
regions or overlays can be done.  It's an audio playlist format after all.
Standardizing on M3U gives you absolutely no room later to do a multi-panel
(multi-region) display.

SMIL is not hard to use to do dynamic playlists.  It's no harder than M3U
really - perhaps a few hours more coding time up front.  Make a template,
drop in the data.  M3U is simpler because you can just 'cat' the elements to
the end and SMIL needs some tags to close it off.  It has the advantage of
being a multimedia playlist format that is standardized already, has
excellent reference documentation and even books written about it.  M3U has
nothing but a Wikipedia page, cannot support regions or any of the other
display control tags.  I predict that if you go the M3U route you will end
up organically growing that protocol to add things over time that SMIL
already has.   SMIL, as XML, can also be validated and thus check for
playlists that got borked somewhere.

If I am correct, is there actually any need for a playlist?  I would suggest
> that all that is needed in a HTTP reply is the URI that will hold the next
> chunk of media and perhaps a time that the URIl will become active.  The
> client could then invoke the logic to go get that URI at the appropriate
> time.
>
>
> We experimented with this approach, but it turns out that adding custom
> headers to the HTTP response is not particularly compatible with how the
> large CDNs work.
>
> The playlist approach has another benefit, in that it allows content
> providers to express a window of previous content that a client can seek
> backward into.
>
> OK, I can buy that.  I think playlists are the right thing, but I wanted to
ask you why you did too.

-- 
Greg Herlein
www.herlein.com

--000e0cd2de44e7e60d046baf2dd1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

All:<br><div class=3D"gmail_quote"><br><blockquote class=3D"gmail_quote" st=
yle=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex=
; padding-left: 1ex;"><div><div class=3D"im"><blockquote type=3D"cite">Yes,=
 it was discussed earlier.=A0 John Lazzaro raised some
questions that were raised several years ago in regards to this being
a bad idea.=A0 I have not seen anyone from Apple respond to
that.<br>
</blockquote>
<div></div>
</div><div>We think that those minutes addressed a different idea. It&#39;s=
 not
clear that they apply to this protocol.</div></div></blockquote><div><br>Th=
ey apllies to the idea of using HTTP to stream media, as far as I can under=
stand.=A0 I&#39;m sensitive to your desires but wonder about the implementa=
tion/standard.=A0 If there&#39;s a market for a solution that solution will=
 find a way to exist...=A0 choosing a best good way for it to be standardar=
dized is a *good thing* <br>
</div><blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb=
(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div><=
/div><div class=3D"im">
<div><br></div></div><div>The protocol is tuned for large-scale, non-intera=
ctive,
broadcast-style viewing. Clients can seek within the window presented
by the playlist. They can implement fast-forward and reverse playback
within it as well if they choose, but the protocol does not sacrifice
scalability in return for additional &quot;trickiness&quot; that
requires one-to-one interaction with the content provider.</div><div class=
=3D"im">
<div></div></div></div></blockquote><div><br>OK, makes sense. <br></div><bl=
ockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204=
, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div class=3D"i=
m">

<blockquote type=3D"cite">I also raised questions about the choice
of playlist format - specifically using a non-standards-based audio
playlist format instead of something like SMIL that was designed for
this kind of thing.=A0 Comments on that?<br>
</blockquote>
<div><br></div>
</div><div>We looked at SMIL. It&#39;s more complicated than M3U and doesn&=
#39;t add
much value for our uses. We would have had=A0to make a new SMIL
profile and then extend it to=A0add the same extensions to it that
we need for M3U.</div>
<div><br></div>
<div>People who have experimented with=A0the protocol tell us that
they=A0really like the simplicity of M3U, which makes it easy to do
things like dynamic playlist generation.</div>
<div></div></div></blockquote><div><br>&quot;Because M3U is easy and SMIL i=
s hard&quot; seems like a poor reason to use to a bunch of Engineers.=A0 Yo=
u are going to have to use extensions to couple it to HTTP no matter what p=
laylist format you use.=A0 M3U is full screen only - no regions or overlays=
 can be done.=A0 It&#39;s an audio playlist format after all.=A0 Standardiz=
ing on M3U gives you absolutely no room later to do a multi-panel (multi-re=
gion) display.=A0=A0 <br>
<br>SMIL is not hard to use to do dynamic playlists.=A0 It&#39;s no harder =
than M3U really - perhaps a few hours more coding time up front.=A0 Make a =
template, drop in the data.=A0 M3U is simpler because you can just &#39;cat=
&#39; the elements to the end and SMIL needs some tags to close it off.=A0 =
It has the advantage of being a multimedia playlist format that is standard=
ized already, has excellent reference documentation and even books written =
about it.=A0 M3U has nothing but a Wikipedia page, cannot support regions o=
r any of the other display control tags.=A0 I predict that if you go the M3=
U route you will end up organically growing that protocol to add things ove=
r time that SMIL already has.=A0=A0 SMIL, as XML, can also be validated and=
 thus check for playlists that got borked somewhere.<br>
<br></div><blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid=
 rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><b=
lockquote type=3D"cite">If I am correct, is there actually any
need for a playlist? =A0I would suggest<br>
that all that is needed in a HTTP reply is the URI that will hold the
next<br>
chunk of media and perhaps a time that the URIl will become active.
=A0The<br>
client could then invoke the logic to go get that URI at the
appropriate<br>
time.<br>
</blockquote>
<div><br></div>
<div>We experimented with this approach, but it turns out that adding
custom headers to the HTTP response is not particularly compatible
with how the large CDNs work.</div>
<div><br></div>
<div>The playlist approach has another benefit, in that it allows
content providers to express a window of previous content that a
client can seek backward into.</div><div class=3D"im">
<pre></pre></div></div></blockquote><div>OK, I can buy that.=A0 I think pla=
ylists are the right thing, but I wanted to ask you why you did too.<br></d=
iv></div><br>-- <br>Greg Herlein<br><a href=3D"http://www.herlein.com">www.=
herlein.com</a><br>


--000e0cd2de44e7e60d046baf2dd1--

From alex.giladi@gmail.com  Sat Jun  6 09:35:23 2009
Return-Path: <alex.giladi@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 2126F3A6860 for <avt@core3.amsl.com>; Sat,  6 Jun 2009 09:35:23 -0700 (PDT)
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 IYd37L7iassy for <avt@core3.amsl.com>; Sat,  6 Jun 2009 09:35:22 -0700 (PDT)
Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by core3.amsl.com (Postfix) with ESMTP id AE8463A6805 for <avt@ietf.org>; Sat,  6 Jun 2009 09:35:21 -0700 (PDT)
Received: by bwz9 with SMTP id 9so2136454bwz.37 for <avt@ietf.org>; Sat, 06 Jun 2009 09:35:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=KBhdZBYvjombvJL2GxiBnTV6IQ42MWhyln1pwCMhxI8=; b=tJLzT54jATpp2GujIPdrONOKNOZ7Hw6iXo+vspxtHoahv+/7XWExjdW1sI2VCZVj4F +OMmSXRXTE8GCsEq7P/+y6Dn2/S+WghwC4pYfONjSy9lSaW8iXO4noEzYmufwOwXg3sq p6ExQTfDvQywTjmhWKbKBBOaYlfmqQW++1/sU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=F2SD4aBEo+1UNogRo0yG0nyCvP4BJ2OWZU21r091EV8y5/af/GF9K1SHzZtD2BjZYQ TAB65+oCpdlG6nLTrJKWqwkQbPxG7rzX1fa56sHMzCV62WHdu9fRhUV6cmxg0raHuMr+ plAiEjy5LB2ywcDBP66Y2Hgu7zOda4wB0mQoo=
MIME-Version: 1.0
Received: by 10.204.31.71 with SMTP id x7mr4538432bkc.2.1244306122877; Sat, 06  Jun 2009 09:35:22 -0700 (PDT)
In-Reply-To: <006501c9e67e$c14df7f0$43e9e7d0$%roni@huawei.com>
References: <p06240865c638d26a3381@10.177.192.68> <31d1be720905200905o53281cbja084ea69cf30ec0@mail.gmail.com> <p06240804c64f10586260@10.0.1.8> <57a9e15d0906051127j23e57e13l3e1841789cb5edaf@mail.gmail.com> <p06240804c64f44559190@10.0.1.8> <006501c9e67e$c14df7f0$43e9e7d0$%roni@huawei.com>
Date: Sat, 6 Jun 2009 10:35:22 -0600
Message-ID: <57a9e15d0906060935u87c2b0bm20f3152d7724e42d@mail.gmail.com>
From: Alex Giladi <alex.giladi@gmail.com>
To: Roni Even <Even.roni@huawei.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: http-live-streaming-review@group.apple.com, David Singer <singer@apple.com>, avt@ietf.org
Subject: Re: [AVT] iPhone streaming Internet-Draft posted
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, 06 Jun 2009 16:35:23 -0000

There are a couple of other meanings found in the wikipedia
(http://en.wikipedia.org/wiki/Adi)
As for possible descriptive languages, we have two options here: a
Tibeto-Burmese language and the CableLabs Asset Distribution
Interface.
;-)

On Sat, Jun 6, 2009 at 2:12 AM, Roni Even<Even.roni@huawei.com> wrote:
> David,
> Adi means an ornament in my mother tongue (it is in the Bible).
> Roni
>
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Dav=
id
> Singer
> Sent: Saturday, June 06, 2009 1:00 AM
> To: Alex Giladi
> Cc: http-live-streaming-review@group.apple.com; avt@ietf.org
> Subject: Re: [AVT] iPhone streaming Internet-Draft posted
>
> At 14:27 =C2=A0-0400 5/06/09, Alex Giladi wrote:
>>
>>What about ADI?
>>
>
> hm...probably not "Aircraft De-Ice and Inhibitor". Less unlikely is
> "AutoCAD Device Interface". I guess we can hope for a link to the
> "American Distilling Institute", we can fear "Advanced Discriminating
> Interceptor", or tune in to "Acoustic Directional Intensity"...
>
> or I could ask...which ADI do you speak of?
> --
> David Singer
> Multimedia Standards, Apple Inc.
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>
>

From csp@csperkins.org  Mon Jun  8 08:53:18 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 C86A928C139 for <avt@core3.amsl.com>; Mon,  8 Jun 2009 08:53:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 t4sCzVDuV-9y for <avt@core3.amsl.com>; Mon,  8 Jun 2009 08:53:17 -0700 (PDT)
Received: from anchor-msapost-3.mail.demon.net (anchor-msapost-3.mail.demon.net [195.173.77.166]) by core3.amsl.com (Postfix) with ESMTP id B859A28C0E3 for <avt@ietf.org>; Mon,  8 Jun 2009 08:53:17 -0700 (PDT)
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]) by anchor-post-3.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1MDhA2-00079f-oY; Mon, 08 Jun 2009 15:53:22 +0000
Message-Id: <462D435A-3DE8-4845-95E7-EC925E7222AF@csperkins.org>
From: Colin Perkins <csp@csperkins.org>
To: Roni Even <Even.roni@huawei.com>
In-Reply-To: <004b01c9ddd4$88fe9240$9afbb6c0$%roni@huawei.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 8 Jun 2009 16:53:21 +0100
References: <004b01c9ddd4$88fe9240$9afbb6c0$%roni@huawei.com>
X-Mailer: Apple Mail (2.935.3)
Cc: avt@ietf.org, 'Tom Taylor' <tom.taylor@rogers.com>
Subject: Re: [AVT] WGLC on draft-ietf-avt-rtp-ipmr-04
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, 08 Jun 2009 15:53:18 -0000

On 26 May 2009, at 08:35, Roni Even wrote:
> I would like to start a WGLC on http://tools.ietf.org/html/draft-ietf-avt-rtp-ipmr-04 
>  .
>
> This is the RTP Payload Format for IP-MR Speech Codec.
>
> There was some comments on the mailing list about this work and they  
> were addressed in the 04 draft.
>
> We will start a 3 weeks working group last call.
> Please review the draft and send comments till June 16th

I have several comments on this draft:

The payload header includes flags (the "D" and "A" bits) to signal if  
DTX is allowed, and if the payload format is byte aligned. This is  
unusual. Previous payload formats generally signal such parameters out- 
of-band, for example using an SDP offer/answer exchange. What's the  
rationale for this design, and is there a reason why out-of-band  
parameters cannot be used?

The A bit in the payload header signals whether a byte-aligned mode is  
to be used. There doesn't seem to be any specification of how this  
differs from the non-byte-aligned mode.

Section 3.5 indicates that the decoder "can calculate the frame size  
by its content" and notes that "there is a special service function  
that returns frame size without total decoding which may be used for  
this purpose". A function tied to a particular codec implementation is  
appropriate for a vendor codec, but not for a payload format that is  
to be registered in the standards tree. The draft needs to document  
how to determine the payload length. (this information might be added  
to the table on page 6).

Page 8 includes a table listing the amount of redundancy that might be  
added. This is listed as being class A, B, C, D, E, or F, but no  
details are provided on what each means. If this is to be a standard  
media type, more details must be provided, to allow independent  
implementation of the payload format.

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




From root@core3.amsl.com  Mon Jun  8 16:15:02 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 214D43A6A83; Mon,  8 Jun 2009 16:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090608231502.214D43A6A83@core3.amsl.com>
Date: Mon,  8 Jun 2009 16:15:02 -0700 (PDT)
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-seed-srtp-12.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, 08 Jun 2009 23: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		: The SEED Cipher Algorithm and Its Use with the Secure Real-time Transport Protocol (SRTP)
	Author(s)	: S. Yoon, H. Park, J. Kim, H. Jeong, Y. Won
	Filename	: draft-ietf-avt-seed-srtp-12.txt
	Pages		: 13
	Date		: 2009-6-8
	
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-12.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-12.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--


From singer@apple.com  Tue Jun  9 08:18:05 2009
Return-Path: <singer@apple.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 CB6323A6ACB for <avt@core3.amsl.com>; Tue,  9 Jun 2009 08:18:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.52
X-Spam-Level: 
X-Spam-Status: No, score=-106.52 tagged_above=-999 required=5 tests=[AWL=0.079, 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 InL6s653l3Yr for <avt@core3.amsl.com>; Tue,  9 Jun 2009 08:18:05 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 0FA8228C163 for <avt@ietf.org>; Tue,  9 Jun 2009 08:18:05 -0700 (PDT)
Received: from relay11.apple.com (relay11.apple.com [17.128.113.48]) by mail-out3.apple.com (Postfix) with ESMTP id 32D2B63DB736; Tue,  9 Jun 2009 08:18:11 -0700 (PDT)
Received: from relay11.apple.com (unknown [127.0.0.1]) by relay11.apple.com (Symantec Brightmail Gateway) with ESMTP id 1A8DA28092; Tue,  9 Jun 2009 08:18:11 -0700 (PDT)
X-AuditID: 11807130-aace7bb0000025da-a1-4a2e7d322f7b
Received: from [10.0.1.8] (unknown [17.151.84.10]) by relay11.apple.com (Apple SCV relay) with ESMTP id 9BDAE28083; Tue,  9 Jun 2009 08:18:10 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p06240859c6542b53968f@[10.0.1.8]>
In-Reply-To: <8987F5DB-1395-44F3-A4F0-44725FCC3D7E@gbiv.com>
References: <20090609024502.05A883A67F6@core3.amsl.com> <8987F5DB-1395-44F3-A4F0-44725FCC3D7E@gbiv.com>
Date: Tue, 9 Jun 2009 08:17:40 -0700
To: "Roy T. Fielding" <fielding@gbiv.com>, http-live-streaming-review@group.apple.com
From: David Singer <singer@apple.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
Cc: avt@ietf.org
Subject: Re: [AVT] I-D Action:draft-pantos-http-live-streaming-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: Tue, 09 Jun 2009 15:18:05 -0000

At 13:57  +0200 9/06/09, Roy T. Fielding wrote:
>
>I find this draft to be quite annoying.  It doesn't have anything
>to do with HTTP or live, or really even streaming -- the title is
>just from the marketing term that Apple has chosen to describe this
>concept in general.
>
>What the draft defines is a set of media type extensions to the
>unregistered "audio/x-mpegurl" media type (M3U Playlist format)
>that provide additional information for an indirect request of a
>stream via sequential requests on the listed URIs.  While I think
>that might be a fine idea, it should start by registering the
>media type being extended, and the title/introduction should reflect
>what the document defines so that the right people will review it
>prior to publication.  I don't like it when the IETF is abused
>for marketing purposes.

Roy, I'm sorry that is what you feel we are doing.  We thought we 
were trying to be as open as possible by providing this for 
information and criticism.  We're not trying to standardize it.  I 
don't think we 'own' the MIME type, so even though it's a concern 
it's unregistered, it's not clear it's for us to fix, is it?

The draft covers the delivery of live multimedia information which 
can be essentially indefinite in duration - a stream in common 
parlance - using HTTP.  Given that the content is live and it's an 
indefinite stream being delivered, and we use HTTP, I don't think the 
title is very far off base, if at all.

There have been glimpses of a general debate over how to deliver 
multimedia, here in the AVT list.  There are the upcoming MPEG and 
DVB workshops, where that debate will also continue.  We're not the 
only ones to have tried the 'proper' protocols and found that, after 
many years, there are infrastructure problems with them.  We even 
open-source a streaming server, and (at one point at least) had 
sample code for a proxy, iirc, to try to help them along.
-- 
David Singer
Multimedia Standards, Apple Inc.

From root@core3.amsl.com  Tue Jun  9 14: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 3DF7628C0FA; Tue,  9 Jun 2009 14:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090609210001.3DF7628C0FA@core3.amsl.com>
Date: Tue,  9 Jun 2009 14:00:01 -0700 (PDT)
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-seed-srtp-13.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, 09 Jun 2009 21: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		: The SEED Cipher Algorithm and Its Use with the Secure Real-time Transport Protocol (SRTP)
	Author(s)	: S. Yoon, H. Park, J. Kim, H. Jeong, Y. Won
	Filename	: draft-ietf-avt-seed-srtp-13.txt
	Pages		: 13
	Date		: 2009-6-9
	
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-13.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-13.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--


From fielding@gbiv.com  Tue Jun  9 09:10:05 2009
Return-Path: <fielding@gbiv.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 9629C3A6928 for <avt@core3.amsl.com>; Tue,  9 Jun 2009 09:10:05 -0700 (PDT)
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=-3.600, 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 AT4Bcc5OcRVO for <avt@core3.amsl.com>; Tue,  9 Jun 2009 09:10:01 -0700 (PDT)
Received: from spaceymail-a6.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by core3.amsl.com (Postfix) with ESMTP id 433263A6781 for <avt@ietf.org>; Tue,  9 Jun 2009 09:10:01 -0700 (PDT)
Received: from [10.0.0.125] (bsl-rtr.day.com [62.192.10.254]) by spaceymail-a6.g.dreamhost.com (Postfix) with ESMTP id B41B1CA7D2; Tue,  9 Jun 2009 09:10:02 -0700 (PDT)
In-Reply-To: <p06240859c6542b53968f@[10.0.1.8]>
References: <20090609024502.05A883A67F6@core3.amsl.com> <8987F5DB-1395-44F3-A4F0-44725FCC3D7E@gbiv.com> <p06240859c6542b53968f@[10.0.1.8]>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <126256AE-A133-4628-82C9-B1098C304973@gbiv.com>
Content-Transfer-Encoding: 7bit
From: "Roy T. Fielding" <fielding@gbiv.com>
Date: Tue, 9 Jun 2009 18:10:05 +0200
To: David Singer <singer@apple.com>
X-Mailer: Apple Mail (2.753.1)
X-Mailman-Approved-At: Wed, 10 Jun 2009 08:06:47 -0700
Cc: http-live-streaming-review@group.apple.com, avt@ietf.org
Subject: Re: [AVT] I-D Action:draft-pantos-http-live-streaming-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: Tue, 09 Jun 2009 16:10:05 -0000

On Jun 9, 2009, at 5:17 PM, David Singer wrote:

> At 13:57  +0200 9/06/09, Roy T. Fielding wrote:
>>
>> I find this draft to be quite annoying.  It doesn't have anything
>> to do with HTTP or live, or really even streaming -- the title is
>> just from the marketing term that Apple has chosen to describe this
>> concept in general.
>>
>> What the draft defines is a set of media type extensions to the
>> unregistered "audio/x-mpegurl" media type (M3U Playlist format)
>> that provide additional information for an indirect request of a
>> stream via sequential requests on the listed URIs.  While I think
>> that might be a fine idea, it should start by registering the
>> media type being extended, and the title/introduction should reflect
>> what the document defines so that the right people will review it
>> prior to publication.  I don't like it when the IETF is abused
>> for marketing purposes.
>
> Roy, I'm sorry that is what you feel we are doing.  We thought we  
> were trying to be as open as possible by providing this for  
> information and criticism.  We're not trying to standardize it.  I  
> don't think we 'own' the MIME type, so even though it's a concern  
> it's unregistered, it's not clear it's for us to fix, is it?

If you aren't trying to standardize it (at least a little), then why
isn't this just a page on the Apple site?  Presumably you want other
organizations to be able to produce interoperable M3U playlists, which
seems to be a perfectly good reason to publish a document here.  What
doesn't make any sense is the use of the Apple marketing phrase as
the title, because that phrase does not describe what is being defined.
It has the effect of claiming ownership on a broad use of HTTP,
for which the IETF is the standards caretaker, rather than simply
describing the stuff being engineered.

Somebody should register the media type or invent a new media type
that includes your suggested extensions.  It does not have to be the
owner of the data format.  That is why we have an Internet media type
registry which simply requires a template be inserted in an RFC for
this kind of (non-vendor) type.  It therefore makes sense for you to
include a media type registration as part of this document even if the
draft is only being submitted for publication as an Informational
(not standards-track) RFC.

> The draft covers the delivery of live multimedia information which  
> can be essentially indefinite in duration - a stream in common  
> parlance - using HTTP.  Given that the content is live and it's an  
> indefinite stream being delivered, and we use HTTP, I don't think  
> the title is very far off base, if at all.

The draft covers the data format for a document that might be retrieved
from any source (filesystem, HTTP, FTP, etc.) and which contains a list
of URIs for obtaining the individual data segments that make up the
"stream", said URIs being of whatever schemes the provider thinks is
most appropriate.  It is not limited by HTTP at all.  There are no
changes required of HTTP.  There are no extensions to HTTP.  Thus,
when the HTTP experts go to review it thinking it might be applicable
to their expertise, the result is "WTF?".  AFAICT, the content isn't
required to be "live" either -- it could be playing an old movie.

Just to be clear, I am not objecting to the design at all.  I do not
want you to make the specification dependent on HTTP -- that would
be silly given the orthogonal nature of URIs.  I just see no reason
for HTTP to appear in the title and abstract.  What it should say is
that the document defines a format for describing a sequence of Web
resources for delivery of their individual representations as a
logical stream of data.  The title should be something like
"MPEG3 URI Playlist media type for sequenced data streams".

> There have been glimpses of a general debate over how to deliver  
> multimedia, here in the AVT list.  There are the upcoming MPEG and  
> DVB workshops, where that debate will also continue.  We're not the  
> only ones to have tried the 'proper' protocols and found that,  
> after many years, there are infrastructure problems with them.  We  
> even open-source a streaming server, and (at one point at least)  
> had sample code for a proxy, iirc, to try to help them along.

That's all great.  But when you submit a specification to the IETF,
it should be titled/described according to what the spec defines
so that the right people will know to review it.

....Roy

From Even.roni@huawei.com  Thu Jun 11 00:09:53 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BCC903A692E for <avt@core3.amsl.com>; Thu, 11 Jun 2009 00:09:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.371
X-Spam-Level: 
X-Spam-Status: No, score=-0.371 tagged_above=-999 required=5 tests=[AWL=0.124,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 WoZlvHEHkC3G for <avt@core3.amsl.com>; Thu, 11 Jun 2009 00:09:53 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id EE0FF3A67A7 for <avt@ietf.org>; Thu, 11 Jun 2009 00:09:52 -0700 (PDT)
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 <0KL200H35BTS3V@szxga03-in.huawei.com> for avt@ietf.org; Thu, 11 Jun 2009 15:08:16 +0800 (CST)
Received: from huawei.com ([172.24.1.3]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KL200ISJBTSIV@szxga03-in.huawei.com> for avt@ietf.org; Thu, 11 Jun 2009 15:08:16 +0800 (CST)
Received: from windows8d787f9 (bzq-79-177-76-15.red.bezeqint.net [79.177.76.15]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KL200M5CBTNUJ@szxml01-in.huawei.com> for avt@ietf.org; Thu, 11 Jun 2009 15:08:16 +0800 (CST)
Date: Thu, 11 Jun 2009 10:06:34 +0300
From: Roni Even <Even.roni@huawei.com>
To: avt@ietf.org
Message-id: <001301c9ea63$2b54a800$81fdf800$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcnqXAZHrgJ+hEQZRmyuHzXQCxJJgwABxpFQ
Subject: [AVT] FW: [dispatch] Wideband audio codec proposal dispatched as a regular BOF
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, 11 Jun 2009 07:09:53 -0000

FYI

-----Original Message-----
From: dispatch-bounces@ietf.org [mailto:dispatch-bounces@ietf.org] On Behalf
Of Gonzalo Camarillo
Sent: Thursday, June 11, 2009 9:15 AM
To: DISPATCH
Subject: [dispatch] Wideband audio codec proposal dispatched as a regular
BOF

Folks,

there have been significant list discussions on whether or not the IETF 
should be working on the topics proposed in the email below:

http://www.ietf.org/mail-archive/web/dispatch/current/msg00080.html

As a way forward, we have decided to organize the face-to-face 
discussions around this topic in Stockholm as a regular BOF (i.e., 
outside DISPATCH). We believe that, given the nature of the questions 
that need to be answered, this topic will benefit from discussions from 
a wide range of people. Organizing the meeting as a regular BOF ensures 
such discussions. A regular BOF also provides more time for discussions.

Therefore, from now on, please use the following mailing list (instead 
of the DISPATCH list) for discussions on this topic:

   codec@ietf.org

Thanks,

Gonzalo
DISPATCH co-chair
_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch


From macinnis@broadcom.com  Thu Jun 11 06:38:04 2009
Return-Path: <macinnis@broadcom.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 3F7B23A6919 for <avt@core3.amsl.com>; Thu, 11 Jun 2009 06:38:04 -0700 (PDT)
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 t0PT4iVGoUbH for <avt@core3.amsl.com>; Thu, 11 Jun 2009 06:38:03 -0700 (PDT)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by core3.amsl.com (Postfix) with ESMTP id 659C43A693C for <avt@ietf.org>; Thu, 11 Jun 2009 06:38:03 -0700 (PDT)
Received: from [10.16.192.224] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 11 Jun 2009 06:38:01 -0700
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB01.corp.ad.broadcom.com ([10.16.192.224]) with mapi; Thu, 11 Jun 2009 06:38:01 -0700
From: "Sandy (Alexander) MacInnis" <macinnis@broadcom.com>
To: "avt@ietf.org" <avt@ietf.org>
Date: Thu, 11 Jun 2009 06:37:05 -0700
Thread-Topic: [AVT] FW: [dispatch] Wideband audio codec proposal dispatched as a regular BOF
Thread-Index: AcnqXAZHrgJ+hEQZRmyuHzXQCxJJgwABxpFQAA2QVpA=
Message-ID: <568A92CB079CCF43BA5C8D7B08BCB4AE8150B54F6E@SJEXCHCCR02.corp.ad.broadcom.com>
References: <001301c9ea63$2b54a800$81fdf800$%roni@huawei.com>
In-Reply-To: <001301c9ea63$2b54a800$81fdf800$%roni@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 662FD7333841345202-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [AVT] FW: [dispatch] Wideband audio codec proposal dispatched as a regular BOF
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, 11 Jun 2009 13:38:04 -0000

How does one join the codec@ietf.org mailing list?

I searched the IETF mailing lists and could not find it. There are working =
groups, other lists, and announcement lists, none of which contain codec.

--Sandy

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Roni =
Even
Sent: Thursday, June 11, 2009 3:07 AM
To: avt@ietf.org
Subject: [AVT] FW: [dispatch] Wideband audio codec proposal dispatched as a=
 regular BOF

FYI

-----Original Message-----
From: dispatch-bounces@ietf.org [mailto:dispatch-bounces@ietf.org] On Behal=
f
Of Gonzalo Camarillo
Sent: Thursday, June 11, 2009 9:15 AM
To: DISPATCH
Subject: [dispatch] Wideband audio codec proposal dispatched as a regular
BOF

Folks,

there have been significant list discussions on whether or not the IETF=20
should be working on the topics proposed in the email below:

http://www.ietf.org/mail-archive/web/dispatch/current/msg00080.html

As a way forward, we have decided to organize the face-to-face=20
discussions around this topic in Stockholm as a regular BOF (i.e.,=20
outside DISPATCH). We believe that, given the nature of the questions=20
that need to be answered, this topic will benefit from discussions from=20
a wide range of people. Organizing the meeting as a regular BOF ensures=20
such discussions. A regular BOF also provides more time for discussions.

Therefore, from now on, please use the following mailing list (instead=20
of the DISPATCH list) for discussions on this topic:

   codec@ietf.org

Thanks,

Gonzalo
DISPATCH co-chair
_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch

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



From pbungaro@cisco.com  Thu Jun 11 07:21:44 2009
Return-Path: <pbungaro@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 747553A683D for <avt@core3.amsl.com>; Thu, 11 Jun 2009 07:21:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 C4iWqOxtN1gD for <avt@core3.amsl.com>; Thu, 11 Jun 2009 07:21:43 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id D3FAB3A6977 for <avt@ietf.org>; Thu, 11 Jun 2009 07:21:42 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,203,1243814400"; d="scan'208";a="42600264"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 11 Jun 2009 14:21:48 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n5BELmFT024011;  Thu, 11 Jun 2009 16:21:48 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n5BELmDh015136; Thu, 11 Jun 2009 14:21:48 GMT
Received: from xmb-ams-335.cisco.com ([144.254.231.80]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 11 Jun 2009 16:21:48 +0200
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: Thu, 11 Jun 2009 16:22:00 +0200
Message-ID: <3AFF5CA02835034C8E0E74D825BA92B00574D526@xmb-ams-335.emea.cisco.com>
In-Reply-To: <568A92CB079CCF43BA5C8D7B08BCB4AE8150B54F6E@SJEXCHCCR02.corp.ad.broadcom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] FW: [dispatch] Wideband audio codec proposal dispatched as a regular BOF
Thread-Index: AcnqXAZHrgJ+hEQZRmyuHzXQCxJJgwABxpFQAA2QVpAAAaMrkA==
References: <001301c9ea63$2b54a800$81fdf800$%roni@huawei.com> <568A92CB079CCF43BA5C8D7B08BCB4AE8150B54F6E@SJEXCHCCR02.corp.ad.broadcom.com>
From: "Paola Bungaro (pbungaro)" <pbungaro@cisco.com>
To: "Sandy (Alexander) MacInnis" <macinnis@broadcom.com>, <avt@ietf.org>
X-OriginalArrivalTime: 11 Jun 2009 14:21:48.0150 (UTC) FILETIME=[F49E8960:01C9EA9F]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2570; t=1244730108; x=1245594108; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pbungaro@cisco.com; z=From:=20=22Paola=20Bungaro=20(pbungaro)=22=20<pbungaro@cis co.com> |Subject:=20RE=3A=20[AVT]=20FW=3A=20[dispatch]=20Wideband=2 0audio=20codec=20proposal=20dispatched=20as=20a=20regular=20 BOF |Sender:=20; bh=flBJwto6WgmgvFntj5JRA5HAX+XgJ36hFRnsa2GXXlU=; b=HRXIeS6DpLy/Ta5o0PCQ25gvxz96w9OvLHBSiG6xJwf3FicjJZtw+W4vXj bMahbRtSsx8RtDT9YfgqEVMrfkybqd+KkXYe6w6HO1pKhq8v3LMEpXRUCd/q M0C7ekMGB3;
Authentication-Results: ams-dkim-2; header.From=pbungaro@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); 
Subject: Re: [AVT] FW: [dispatch] Wideband audio codec proposal dispatched as a regular BOF
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, 11 Jun 2009 14:21:44 -0000

 See https://www.ietf.org/mailman/listinfo/codec

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On=20
> Behalf Of Sandy (Alexander) MacInnis
> Sent: 11 June 2009 14:37
> To: avt@ietf.org
> Subject: Re: [AVT] FW: [dispatch] Wideband audio codec=20
> proposal dispatched as a regular BOF
>=20
> How does one join the codec@ietf.org mailing list?
>=20
> I searched the IETF mailing lists and could not find it.=20
> There are working groups, other lists, and announcement=20
> lists, none of which contain codec.
>=20
> --Sandy
>=20
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On=20
> Behalf Of Roni Even
> Sent: Thursday, June 11, 2009 3:07 AM
> To: avt@ietf.org
> Subject: [AVT] FW: [dispatch] Wideband audio codec proposal=20
> dispatched as a regular BOF
>=20
> FYI
>=20
> -----Original Message-----
> From: dispatch-bounces@ietf.org=20
> [mailto:dispatch-bounces@ietf.org] On Behalf Of Gonzalo Camarillo
> Sent: Thursday, June 11, 2009 9:15 AM
> To: DISPATCH
> Subject: [dispatch] Wideband audio codec proposal dispatched=20
> as a regular BOF
>=20
> Folks,
>=20
> there have been significant list discussions on whether or=20
> not the IETF should be working on the topics proposed in the=20
> email below:
>=20
> http://www.ietf.org/mail-archive/web/dispatch/current/msg00080.html
>=20
> As a way forward, we have decided to organize the=20
> face-to-face discussions around this topic in Stockholm as a=20
> regular BOF (i.e., outside DISPATCH). We believe that, given=20
> the nature of the questions that need to be answered, this=20
> topic will benefit from discussions from a wide range of=20
> people. Organizing the meeting as a regular BOF ensures such=20
> discussions. A regular BOF also provides more time for discussions.
>=20
> Therefore, from now on, please use the following mailing list=20
> (instead of the DISPATCH list) for discussions on this topic:
>=20
>    codec@ietf.org
>=20
> Thanks,
>=20
> Gonzalo
> DISPATCH co-chair
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>=20
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>=20

From root@core3.amsl.com  Thu Jun 11 07: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 BF3B83A69E0; Thu, 11 Jun 2009 07:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090611144501.BF3B83A69E0@core3.amsl.com>
Date: Thu, 11 Jun 2009 07:45:01 -0700 (PDT)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-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: Thu, 11 Jun 2009 14: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           : Rapid Synchronisation of RTP Flows
	Author(s)       : C. Perkins, T. Schierl
	Filename        : draft-ietf-avt-rapid-rtp-sync-02.txt
	Pages           : 22
	Date            : 2009-06-11

This memo outlines how RTP 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 synchronisation
delay.  This increase in delay can be unacceptable to some
applications that use layered and/or multi-description codecs.

This memo introduces three mechanisms to reduce the synchronisation
delay for such sessions.  First, it updates the RTP Control Protocol
(RTCP) timing rules to reduce the initial synchronisation delay for
SSM sessions.  Second, 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.  Finally,
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-ietf-avt-rapid-rtp-sync-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-rapid-rtp-sync-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From Even.roni@huawei.com  Thu Jun 11 08:07:37 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0EC7A3A69BD for <avt@core3.amsl.com>; Thu, 11 Jun 2009 08:07:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.433
X-Spam-Level: 
X-Spam-Status: No, score=-0.433 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 0bXUf5a5BllL for <avt@core3.amsl.com>; Thu, 11 Jun 2009 08:07:36 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 0101C3A6876 for <avt@ietf.org>; Thu, 11 Jun 2009 08:07:36 -0700 (PDT)
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 <0KL200JT5Y0L35@szxga03-in.huawei.com> for avt@ietf.org; Thu, 11 Jun 2009 23:07:33 +0800 (CST)
Received: from huawei.com ([172.24.1.6]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KL2000DAY0LD2@szxga03-in.huawei.com> for avt@ietf.org; Thu, 11 Jun 2009 23:07:33 +0800 (CST)
Received: from windows8d787f9 (bzq-79-177-76-15.red.bezeqint.net [79.177.76.15]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KL200CGVY0CV7@szxml02-in.huawei.com>; Thu, 11 Jun 2009 23:07:33 +0800 (CST)
Date: Thu, 11 Jun 2009 18:05:48 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <568A92CB079CCF43BA5C8D7B08BCB4AE8150B54F6E@SJEXCHCCR02.corp.ad.broadcom.com>
To: "'Sandy (Alexander) MacInnis'" <macinnis@broadcom.com>, avt@ietf.org
Message-id: <004901c9eaa6$1fe4f860$5faee920$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcnqXAZHrgJ+hEQZRmyuHzXQCxJJgwABxpFQAA2QVpAAAyycEA==
References: <001301c9ea63$2b54a800$81fdf800$%roni@huawei.com> <568A92CB079CCF43BA5C8D7B08BCB4AE8150B54F6E@SJEXCHCCR02.corp.ad.broadcom.com>
Subject: Re: [AVT] FW: [dispatch] Wideband audio codec proposal dispatched as a regular BOF
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, 11 Jun 2009 15:07:37 -0000

https://www.ietf.org/mailman/listinfo/codec


-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Sandy
(Alexander) MacInnis
Sent: Thursday, June 11, 2009 4:37 PM
To: avt@ietf.org
Subject: Re: [AVT] FW: [dispatch] Wideband audio codec proposal dispatched
as a regular BOF

How does one join the codec@ietf.org mailing list?

I searched the IETF mailing lists and could not find it. There are working
groups, other lists, and announcement lists, none of which contain codec.

--Sandy

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Roni
Even
Sent: Thursday, June 11, 2009 3:07 AM
To: avt@ietf.org
Subject: [AVT] FW: [dispatch] Wideband audio codec proposal dispatched as a
regular BOF

FYI

-----Original Message-----
From: dispatch-bounces@ietf.org [mailto:dispatch-bounces@ietf.org] On Behalf
Of Gonzalo Camarillo
Sent: Thursday, June 11, 2009 9:15 AM
To: DISPATCH
Subject: [dispatch] Wideband audio codec proposal dispatched as a regular
BOF

Folks,

there have been significant list discussions on whether or not the IETF 
should be working on the topics proposed in the email below:

http://www.ietf.org/mail-archive/web/dispatch/current/msg00080.html

As a way forward, we have decided to organize the face-to-face 
discussions around this topic in Stockholm as a regular BOF (i.e., 
outside DISPATCH). We believe that, given the nature of the questions 
that need to be answered, this topic will benefit from discussions from 
a wide range of people. Organizing the meeting as a regular BOF ensures 
such discussions. A regular BOF also provides more time for discussions.

Therefore, from now on, please use the following mailing list (instead 
of the DISPATCH list) for discussions on this topic:

   codec@ietf.org

Thanks,

Gonzalo
DISPATCH co-chair
_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch

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


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


From singer@apple.com  Thu Jun 11 08:23:29 2009
Return-Path: <singer@apple.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 85F6E3A6D22 for <avt@core3.amsl.com>; Thu, 11 Jun 2009 08:23:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.546
X-Spam-Level: 
X-Spam-Status: No, score=-106.546 tagged_above=-999 required=5 tests=[AWL=0.053, 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 GkoPKlT7W-OQ for <avt@core3.amsl.com>; Thu, 11 Jun 2009 08:23:28 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id B84573A6D11 for <avt@ietf.org>; Thu, 11 Jun 2009 08:23:28 -0700 (PDT)
Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out3.apple.com (Postfix) with ESMTP id 065B6644CF2F; Thu, 11 Jun 2009 08:23:31 -0700 (PDT)
Received: from relay16.apple.com (unknown [127.0.0.1]) by relay16.apple.com (Symantec Brightmail Gateway) with ESMTP id EA2B35A0002; Thu, 11 Jun 2009 08:23:30 -0700 (PDT)
X-AuditID: 11807137-ab574bb00000380b-4c-4a3121721282
Received: from [17.202.35.52] (unknown [17.151.85.42]) by relay16.apple.com (Apple SCV relay) with ESMTP id 91C2D558006; Thu, 11 Jun 2009 08:23:30 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p06240823c656d1b20da8@[17.202.35.52]>
In-Reply-To: <004901c9eaa6$1fe4f860$5faee920$%roni@huawei.com>
References: <001301c9ea63$2b54a800$81fdf800$%roni@huawei.com> <568A92CB079CCF43BA5C8D7B08BCB4AE8150B54F6E@SJEXCHCCR02.corp.ad.broadcom.c om> <004901c9eaa6$1fe4f860$5faee920$%roni@huawei.com>
Date: Thu, 11 Jun 2009 08:22:41 -0700
To: Roni Even <Even.roni@huawei.com>, "'Sandy (Alexander) MacInnis'" <macinnis@broadcom.com>, avt@ietf.org
From: David Singer <singer@apple.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [AVT] FW: [dispatch] Wideband audio codec proposal dispatched as a regular BOF
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, 11 Jun 2009 15:23:29 -0000

At 18:05  +0300 11/06/09, Roni Even wrote:
>https://www.ietf.org/mailman/listinfo/codec

should be on <https://datatracker.ietf.org/list/nonwg/>, surely.

>
>
>-----Original Message-----
>From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Sandy
>(Alexander) MacInnis
>Sent: Thursday, June 11, 2009 4:37 PM
>To: avt@ietf.org
>Subject: Re: [AVT] FW: [dispatch] Wideband audio codec proposal dispatched
>as a regular BOF
>
>How does one join the codec@ietf.org mailing list?
>
>I searched the IETF mailing lists and could not find it. There are working
>groups, other lists, and announcement lists, none of which contain codec.
>
>--Sandy
>
>-----Original Message-----
>From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Roni
>Even
>Sent: Thursday, June 11, 2009 3:07 AM
>To: avt@ietf.org
>Subject: [AVT] FW: [dispatch] Wideband audio codec proposal dispatched as a
>regular BOF
>
>FYI
>
>-----Original Message-----
>From: dispatch-bounces@ietf.org [mailto:dispatch-bounces@ietf.org] On Behalf
>Of Gonzalo Camarillo
>Sent: Thursday, June 11, 2009 9:15 AM
>To: DISPATCH
>Subject: [dispatch] Wideband audio codec proposal dispatched as a regular
>BOF
>
>Folks,
>
>there have been significant list discussions on whether or not the IETF
>should be working on the topics proposed in the email below:
>
>http://www.ietf.org/mail-archive/web/dispatch/current/msg00080.html
>
>As a way forward, we have decided to organize the face-to-face
>discussions around this topic in Stockholm as a regular BOF (i.e.,
>outside DISPATCH). We believe that, given the nature of the questions
>that need to be answered, this topic will benefit from discussions from
>a wide range of people. Organizing the meeting as a regular BOF ensures
>such discussions. A regular BOF also provides more time for discussions.
>
>Therefore, from now on, please use the following mailing list (instead
>of the DISPATCH list) for discussions on this topic:
>
>    codec@ietf.org
>
>Thanks,
>
>Gonzalo
>DISPATCH co-chair
>_______________________________________________
>dispatch mailing list
>dispatch@ietf.org
>https://www.ietf.org/mailman/listinfo/dispatch
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>https://www.ietf.org/mailman/listinfo/avt
>
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>https://www.ietf.org/mailman/listinfo/avt
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>https://www.ietf.org/mailman/listinfo/avt


-- 
David Singer
Multimedia Standards, Apple Inc.

From md.1@newtbt.com  Thu Jun 11 09:55:59 2009
Return-Path: <md.1@newtbt.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 934423A68ED for <avt@core3.amsl.com>; Thu, 11 Jun 2009 09:55:59 -0700 (PDT)
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 FCemU5YmMdNI for <avt@core3.amsl.com>; Thu, 11 Jun 2009 09:55:58 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id B57093A6BBE for <avt@ietf.org>; Thu, 11 Jun 2009 09:55:58 -0700 (PDT)
Received: from TBT-Laptop.newtbt.com (ppp-69-237-184-11.dsl.sndg02.pacbell.net [69.237.184.11]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1MEnZM0dpV-000d6S; Thu, 11 Jun 2009 12:56:05 -0400
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 11 Jun 2009 09:17:56 -0700
To: avt@ietf.org
From: Michael A Dolan <md.1@newtbt.com>
In-Reply-To: <20090611144501.BF3B83A69E0@core3.amsl.com>
References: <20090611144501.BF3B83A69E0@core3.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-Id: <0MKpCa-1MEnZM0dpV-000d6S@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX1/iN68AQhwXE1dEH5++rmZjWqELNwlbE45TDh8 rn3WIhE3h4hg8rCuxvL+9EY1nh2imXXJS2Og1Qp65G+CqVwqgp 9Sr6SqTnx4RiSZAPKyROw==
Subject: Re: [AVT] I-D Action:draft-ietf-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: Thu, 11 Jun 2009 16:55:59 -0000

At 07:45 AM 6/11/2009 -0700, Internet-Drafts@ietf.org wrote:
>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           : Rapid Synchronisation of RTP Flows
>         Author(s)       : C. Perkins, T. Schierl
>         Filename        : draft-ietf-avt-rapid-rtp-sync-02.txt
>         Pages           : 22
>         Date            : 2009-06-11
>
>This memo outlines how RTP 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 synchronisation
>delay.  This increase in delay can be unacceptable to some
>applications that use layered and/or multi-description codecs.
>
>This memo introduces three mechanisms to reduce the synchronisation
>delay for such sessions.  First, it updates the RTP Control Protocol
>(RTCP) timing rules to reduce the initial synchronisation delay for
>SSM sessions.  Second, 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.  Finally,
>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-ietf-avt-rapid-rtp-sync-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.
>
>
><ftp://ftp.ietf.org/internet-drafts/draft-ietf-avt-rapid-rtp-sync-02.txt>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>https://www.ietf.org/mailman/listinfo/avt


From md.1@newtbt.com  Thu Jun 11 09:56:06 2009
Return-Path: <md.1@newtbt.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 86C5D3A6C54 for <avt@core3.amsl.com>; Thu, 11 Jun 2009 09:56:06 -0700 (PDT)
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, 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 Krop6VSsn+ep for <avt@core3.amsl.com>; Thu, 11 Jun 2009 09:56:03 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id D16073A6D49 for <avt@ietf.org>; Thu, 11 Jun 2009 09:56:02 -0700 (PDT)
Received: from TBT-Laptop.newtbt.com (ppp-69-237-184-11.dsl.sndg02.pacbell.net [69.237.184.11]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1MEnZO1ysE-000d6S; Thu, 11 Jun 2009 12:56:08 -0400
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 11 Jun 2009 09:56:00 -0700
To: avt@ietf.org
From: Michael A Dolan <md.1@newtbt.com>
In-Reply-To: <49D4AE9D.8060905@hhi.fraunhofer.de>
References: <20090309171502.518513A6359@core3.amsl.com> <4A6ACB13-0CBB-4DA7-84AD-28CDE56DB4C3@csperkins.org> <0MKpCa-1LoLs525qX-000cvA@mrelay.perfora.net> <49D1C793.9050409@hhi.fraunhofer.de> <0MKp8S-1Lof8c1LTC-000fjs@mrelay.perfora.net> <49D4AE9D.8060905@hhi.fraunhofer.de>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_67773984==.ALT"
Message-Id: <0MKpCa-1MEnZO1ysE-000d6S@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX19PsizAu3kABOnGdzgwJYhlYGeu+0/a84DM7tx cddA0Q8FCLSLbedAMbby6XURY9xaHwOZIUcATMWNNsF3J8LtoV g1cqBQBvpn6GdZll8LtfA==
Subject: Re: [AVT] Fwd: I-D  Action:draft-perkins-avt-rapid-rtp-sync-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: Thu, 11 Jun 2009 16:56:06 -0000

--=====================_67773984==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

Thomas and all-

Continuing this in the context of yesterday's WG draft -02:

1. The draft still uses "wallclock".  I believe what's important is 
that the NTP reference clock must have the same reference_ID value as 
the clock used in the RTCP SR records. It's not important that it be 
"wallclock" (or more precisely, one of the values defined in 
NTPv4).  It can be PPS or something else. The draft does mention that 
a common clock should be used.  The problem I see is that the 
language is imprecise WRT NTPv4 terminology and implies a vague 
subset of timebases by using the term, "wallclock". Further, when the 
hdr ext for NTP is not used, it should be stated that the NTP 
timebase reference_ID must be agreed to out of band between the 
senders and receivers.

2. Sync can only occur when the receiver has not only NTP and RTCP SR 
packets, but also a point in every RTP session where there is an 
"access point" for that media stream.  Since these access points are 
customarily considerably further apart than 0.04 seconds, the tables 
are a bit misleading on the practical sync time and recommended RTCP 
SR emission frequency.  It should be noted around all the tables that 
there is no benefit to sending the RTCP SR record more often than the 
media access point frequency, especially in combination with the next 
comment below.

3. It should be recommended that RTCP SR packets be sent near, and 
immediately following, media access points (subject to the 5% 
boundary). Doing so will greatly improve the sync time rather than 
relying on more frequent, and/or randomly timed, RTCP SR packets.

Comment #1 becomes even more important the faster you want to 
sync.  If the RTP sessions are using GPS and the NTP source is using 
UTC (both "wallclock"), there will be errors measured in 
seconds.  This disparity is less likely when the hdr ext is used, of 
course. But in the general case, this language needs tightening up to 
remove the clock errors.

Comments 2 & 3, although true in all scenarios, become more relevant 
in SSM with late joiners.

I hope the above comments are clearer than my attempts below.  I'm 
happy to suggest specific edits to the draft if that will help.

Regards,

         Mike

At 02:25 PM 4/2/2009 +0200, Thomas.Schierl@hhi.fraunhofer.de wrote:
>Hi Michael,
>
>What I can see from the ATSC M/H Transport spec is that there are 
>requirements on encoder and decoder clock precisions, which for sure 
>give a complete different environment than assumed by RFC3550 with 
>respect to the clock precision. If we could assure such clocks for 
>all devices which may potentially encode and stream layered media 
>via multi session transmission, the problem would have been solved 
>anyway. But that is not the case, as I tried to show by pointing to 
>some of the relevant discussions on the mailing list.
>
>About your second point: RTP does not require NTP to be used as 
>wallclock. In RTP, there is much more freedom in selecting the 
>source for this clock. RTP uses the NTP timestamp format just for 
>indicating the wallclock in the RTCP sender reports. Furthermore 
>draft-perkins-avt-rapid-rtp-sync-03 does only require to use the 
>same wallclock as used for the SRs also for the wallclock timestamps 
>in the header extensions.
>
>Another interesting point is that the ATSC Transport spec is not 
>mentioning SVC while mentioning AVC and AAC. If looking at the ATSC 
>Video Systems spec. 
>(<http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-136r7-A153-Part-7-Video-System.pdf>S4-136r7-A153-Part-7-Video-System), 
>there is a solution which requires RTP timestamp synchronization for 
>"SVC Transport in Two RTP Sessions". This for sure solves the clock 
>skew problem, but as discussed in AVT, this is not a general 
>solution and has different implications if applied to all use cases 
>of RTP multi session transmission as, e.g. conversational services. 
>Therefore we now have a solution which seems to be agreeable by the 
>group, which solves the problem and is more in line with RFC 3550, 
>i.e. using the wallclock for the data alignment between the session.
>
>Best regards,
>Thomas
>
>
>Michael A Dolan wrote:
>>Hi Thomas-
>>
>>Thanks.  Yes, I am familiar with the discussion.
>>
>>I'm not necessarily pushing the ATSC solution, but offering some 
>>points to consider, which apply equally to the problem at hand here, I think.
>>
>>Also, it is important to note some more things about the ATSC text:
>>
>>1. The language in the specification very carefully recommends the 
>>clock precision without requiring it.  It is expected to work over 
>>routers with jitter and delays and with media components from 
>>outside the broadcast facility. The difference is that the client 
>>is expected to be able to perform tight sync when the servers are 
>>able to provide the recommended timing model (encoding one hop 
>>away, etc).  It gracefully degrades to "Internet" timing model quality.
>>
>>2. The clock, although "NTP" syntax, is not time of day (e.g. 
>>reference_ID= "GPS"), but "PPS", thus allowing the components to be 
>>encoded and decoded without concern for end-to-end delivery 
>>delay.  This only works when NTP is explicitly signaled as part of 
>>the encoding and both components share a clock (same or closely 
>>coupled encoders). So it will not work in the general case.  But 
>>there are many systems where it will and perhaps consideration 
>>should be given to permitting non-"wall clock" timebases.
>>
>>The NTP hdr ext here is an encoding optimization that indeed has 
>>some other good properties.  Although the draft ties the NTP 
>>timestamp back to the RTCP SR records, the timebase is not 
>>explicitly defined (which is also true of RTCP SR).  Some 
>>reference_ID value must be assumed and there is enough delta 
>>between, for example, GPS and UTC, timebases to cause things to 
>>break if the entire system is not implicitly assumed to be only one 
>>timebase. For example, without an explicit reference_ID, how could 
>>one use other timebases defined in NTPv4?  This is a broader issue 
>>than the hdr ext syntax, but since we're discussing NTP, I thought 
>>I'd bring it up.
>>
>>I think the above and the other points below are relevant here and 
>>not inconsistent with the RTCP SR methods. The fact that the ATSC 
>>design *can* be more precise is not alone cause to discard the 
>>techniques developed there.
>>
>>Regards,
>>
>>          Mike
>>
>>At 09:34 AM 3/31/2009 +0200, 
>><mailto:Thomas.Schierl@hhi.fraunhofer.de>Thomas.Schierl@hhi.fraunhofer.de 
>>wrote:
>>>Dear Michael,
>>>
>>>Thanks for the comments and the reference to the ATSC M/H.
>>>
>>>I guess, what we are looking for in AVT is a solution which also 
>>>works for encoders having non-perfect clocks. There was a long 
>>>discussion on the list, here are two pointers:
>>>
>>><http://www.ietf.org/mail-archive/web/avt/current/msg09144.html>http://www.ietf.org/mail-archive/web/avt/current/msg09144.html
>>>http://www.ietf.org/mail-archive/web/avt/current/msg10491.html
>>>
>>>ATSC surely can assume to have a perfect clock in the NTP streams, 
>>>which will not be the case on PC systems that may be used as an 
>>>encoder for multi session transmission of a layered codec. This is 
>>>one major problem we intended to solve with the header extension 
>>>while keeping the whole approach as close as possible in line with 
>>>the existing RTCP SR method.
>>>
>>>
>>>Best regards,
>>>Thomas
>>>
>>>
>>>
>>>______________________________________________
>>>Thomas Schierl, Dipl.-Ing.
>>>Fraunhofer HHI
>>>Senior Research Engineer
>>>Image Processing Dept. / Multimedia Transport
>>>Einsteinufer 37, 10587 Berlin, Germany
>>>PHONE: +49 30 31002 227 , FAX: +49 30 392 7200
>>>WEB: <http://ip.hhi.de/>http://ip.hhi.de , SKYPE: thomas.schierl
>>>EMAIL: 
>>><mailto:thomas.schierl@hhi.fraunhofer.de>thomas.schierl@hhi.fraunhofer.de
>>>
>>>
>>>
>>>Michael A Dolan wrote:
>>>>Those interested in this topic may also find this interesting:
>>>>
>>>><http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-132r13-A153-Part-3-Transport.pdf>http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-132r13-A153-Part-3-Transport.pdf 
>>>>
>>>>
>>>>Section 10.3.
>>>>
>>>>Some differences are:
>>>>
>>>>1. There is one NTP packet stream per service, rather than the 
>>>>encoding optimization in the hdr ext;
>>>>2. RTCP SR records are emitted "near" video random access points, 
>>>>rather than on a prescribed time schedule; and
>>>>3. The above works in multicast-only, UDLR networks (e.g. 
>>>>television broadcast), rather than requiring a 2-way link.
>>>>
>>>>#2 is interesting since in order to begin a *synchronized* decode 
>>>>(video + audio properly correlated), a client must have acquired all of:
>>>>a. NTP
>>>>b. RTCP SR for each component
>>>>c. video reference frame and decoding metadata (i.e. a random access point)
>>>>d. audio frame
>>>>
>>>>So, the relative timing of the RTCP SR records to the RTP stream 
>>>>content is perhaps more important than the emission 
>>>>period.  Having the RTCP SR records arrive faster than the video 
>>>>reference frames doesn't help of course.  And even if they are 
>>>>"fast enough", having them arrive out of sync with the reference 
>>>>frames delays the service acquisition by half the period on average.
>>>>
>>>>Bandwidth utilization (how many bits to devote to RTCP and NTP) 
>>>>can arguably be more efficiently managed by the server in most 
>>>>cases, not individual client requests for faster RTCP SR packets. 
>>>>And, the client would have no knowledge of the intended (video) 
>>>>reference frame periods being used by the server, so it would 
>>>>not, in general, know what to ask for.
>>>>
>>>>In practice, won't a server that wants to enable faster 
>>>>acquisition and sync do things like the above?  I'm concerned 
>>>>that detailed requests from clients beyond "please use more 
>>>>bandwidth and enable fast sync" won't be as valuable as they seem 
>>>>since in the general case the client doesn't know what to ask for exactly.
>>>>
>>>>FYI, the above ATSC document is in a "candidate" state where 
>>>>public comments are solicited.  Independent of this thread, if 
>>>>anyone has comments on it, I could convey them back to the ATSC.
>>>>
>>>>Regards,
>>>>
>>>>         Mike
>>>>
>>>>At 07:43 PM 3/9/2009 +0000, Colin Perkins wrote:
>>>>>The changes in this version are primarily editorial; we're aware that
>>>>>not all the open issues have been addressed yet. Any further comments
>>>>>are welcomed.
>>>>>
>>>>>Chairs: we'd like this to be considered as an AVT working group
>>>>>draft, as indicated privately.
>>>>>
>>>>>Cheers,
>>>>>Colin
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>Begin forwarded message:
>>>>>>From: <mailto:Internet-Drafts@ietf.org>Internet-Drafts@ietf.org
>>>>>>Date: 9 March 2009 17:15:02 GMT
>>>>>>To: <mailto:i-d-announce@ietf.org>i-d-announce@ietf.org
>>>>>>Subject: I-D Action:draft-perkins-avt-rapid-rtp-sync-03.txt
>>>>>>Reply-To: <mailto:internet-drafts@ietf.org>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-03.txt
>>>>>>         Pages           : 17
>>>>>>         Date            : 2009-03-09
>>>>>>
>>>>>>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>http://www.ietf.org/internet-drafts/draft-perkins-avt-rapid-rtp- 
>>>>>>sync-03.txt
>>>>>>
>>>>>>Internet-Drafts are also available by anonymous FTP at:
>>>>>><ftp://ftp.ietf.org/internet-drafts/>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.
>>>>>>Content-Type: text/plain
>>>>>>Content-ID: 
>>>>>><mailto:2009-03-09100610.I-D@ietf.org><2009-03-09100610.I-D@ietf.org>
>>>>>>
>>>>>>_______________________________________________
>>>>>>I-D-Announce mailing list
>>>>>><mailto:I-D-Announce@ietf.org>I-D-Announce@ietf.org
>>>>>>https://www.ietf.org/mailman/listinfo/i-d-announce
>>>>>>Internet-Draft directories: 
>>>>>><http://www.ietf.org/shadow.html>http://www.ietf.org/shadow.html
>>>>>>or 
>>>>>><ftp://ftp.ietf.org/ietf/1shadow-sites.txt>ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>>>
>>>>>_______________________________________________
>>>>>Audio/Video Transport Working Group
>>>>><mailto:avt@ietf.org>avt@ietf.org
>>>>>https://www.ietf.org/mailman/listinfo/avt
>>>>
>>>>_______________________________________________
>>>>Audio/Video Transport Working Group
>>>><mailto:avt@ietf.org>avt@ietf.org
>>>>https://www.ietf.org/mailman/listinfo/avt
>>>
>>>---
>>>Visit us at
>>>
>>>Web 2.0 Expo / March 31 - April 03 / San Francisco, California / Booth 415
>>><http://www.web2expo.com/webexsf2009>http://www.web2expo.com/webexsf2009
>>>
>>>NAB SHOW 2009 / April 18-23 / Las Vegas, Nevada USA / South Hall 
>>>(Upper), Booth SU9624F
>>><http://www.nabshow.com/>http://www.nabshow.com/
>>
>>
>>
>>
>>_______________________________________________
>>Audio/Video Transport Working Group
>><mailto:avt@ietf.org>avt@ietf.org
>>https://www.ietf.org/mailman/listinfo/avt
>>
>
>
>----
>Visit us at
>
>Web 2.0 Expo / March 31 - April 03 / San Francisco, California / Booth 415
><http://www.web2expo.com/webexsf2009>http://www.web2expo.com/webexsf2009
>
>NAB SHOW 2009 / April 18-23 / Las Vegas, Nevada USA / South Hall 
>(Upper), Booth SU9624F
><http://www.nabshow.com/>http://www.nabshow.com/

--=====================_67773984==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
Thomas and all-<br><br>
Continuing this in the context of yesterday's WG draft -02:<br><br>
1. The draft still uses &quot;wallclock&quot;.&nbsp; I believe what's
important is that the NTP reference clock must have the same reference_ID
value as the clock used in the RTCP SR records. It's not important that
it be &quot;wallclock&quot; (or more precisely, one of the values defined
in NTPv4).&nbsp; It can be PPS or something else. The draft does mention
that a common clock should be used.&nbsp; The problem I see is that the
language is imprecise WRT NTPv4 terminology and implies a vague subset of
timebases by using the term, &quot;wallclock&quot;. Further, when the hdr
ext for NTP is not used, it should be stated that the NTP timebase
reference_ID must be agreed to out of band between the senders and
receivers.<br><br>
2. Sync can only occur when the receiver has not only NTP and RTCP SR
packets, but also a point in every RTP session where there is an
&quot;access point&quot; for that media stream.&nbsp; Since these access
points are customarily considerably further apart than 0.04 seconds, the
tables are a bit misleading on the practical sync time and recommended
RTCP SR emission frequency.&nbsp; It should be noted around all the
tables that there is no benefit to sending the RTCP SR record more often
than the media access point frequency, especially in combination with the
next comment below.<br><br>
3. It should be recommended that RTCP SR packets be sent near, and
immediately following, media access points (subject to the 5% boundary).
Doing so will greatly improve the sync time rather than relying on more
frequent, and/or randomly timed, RTCP SR packets.<br><br>
Comment #1 becomes even more important the faster you want to sync.&nbsp;
If the RTP sessions are using GPS and the NTP source is using UTC (both
&quot;wallclock&quot;), there will be errors measured in seconds.&nbsp;
This disparity is less likely when the hdr ext is used, of course. But in
the general case, this language needs tightening up to remove the clock
errors.<br><br>
Comments 2 &amp; 3, although true in all scenarios, become more relevant
in SSM with late joiners.<br><br>
I hope the above comments are clearer than my attempts below.&nbsp; I'm
happy to suggest specific edits to the draft if that will help.<br><br>
Regards,<br><br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Mike<br>
<br>
At 02:25 PM 4/2/2009 +0200, Thomas.Schierl@hhi.fraunhofer.de wrote:<br>
<blockquote type=cite class=cite cite="">Hi Michael,<br><br>
What I can see from the ATSC M/H Transport spec is that there are
requirements on encoder and decoder clock precisions, which for sure give
a complete different environment than assumed by RFC3550 with respect to
the clock precision. If we could assure such clocks for all devices which
may potentially encode and stream layered media via multi session
transmission, the problem would have been solved anyway. But that is not
the case, as I tried to show by pointing to some of the relevant
discussions on the mailing list.<br><br>
About your second point: RTP does not require NTP to be used as
wallclock. In RTP, there is much more freedom in selecting the source for
this clock. RTP uses the NTP timestamp format just for indicating the
wallclock in the RTCP sender reports. Furthermore
draft-perkins-avt-rapid-rtp-sync-03 does only require to use the same
wallclock as used for the SRs also for the wallclock timestamps in the
header extensions.<br><br>
Another interesting point is that the ATSC Transport spec is not
mentioning SVC while mentioning AVC and AAC. If looking at the ATSC Video
Systems spec.
(<a href="http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-136r7-A153-Part-7-Video-System.pdf">
S4-136r7-A153-Part-7-Video-System</a>), there is a solution which
requires RTP timestamp synchronization for &quot;SVC Transport in Two RTP
Sessions&quot;. This for sure solves the clock skew problem, but as
discussed in AVT, this is not a general solution and has different
implications if applied to all use cases of RTP multi session
transmission as, e.g. conversational services. Therefore we now have a
solution which seems to be agreeable by the group, which solves the
problem and is more in line with RFC 3550, i.e. using the wallclock for
the data alignment between the session.<br>
<br>
Best regards,<br>
Thomas<br><br>
<br>
Michael A Dolan wrote: <br>
<blockquote type=cite class=cite cite="">Hi Thomas-<br><br>
Thanks.&nbsp; Yes, I am familiar with the discussion.<br><br>
I'm not necessarily pushing the ATSC solution, but offering some points
to consider, which apply equally to the problem at hand here, I
think.<br><br>
Also, it is important to note some more things about the ATSC
text:<br><br>
1. The language in the specification very carefully recommends the clock
precision without requiring it.&nbsp; It is expected to work over routers
with jitter and delays and with media components from outside the
broadcast facility. The difference is that the client is expected to be
able to perform tight sync when the servers are able to provide the
recommended timing model (encoding one hop away, etc).&nbsp; It
gracefully degrades to &quot;Internet&quot; timing model
quality.<br><br>
2. The clock, although &quot;NTP&quot; syntax, is not time of day (e.g.
reference_ID= &quot;GPS&quot;), but &quot;PPS&quot;, thus allowing the
components to be encoded and decoded without concern for end-to-end
delivery delay.&nbsp; This only works when NTP is explicitly signaled as
part of the encoding and both components share a clock (same or closely
coupled encoders). So it will not work in the general case.&nbsp; But
there are many systems where it will and perhaps consideration should be
given to permitting non-&quot;wall clock&quot; timebases.<br><br>
The NTP hdr ext here is an encoding optimization that indeed has some
other good properties.&nbsp; Although the draft ties the NTP timestamp
back to the RTCP SR records, the timebase is not explicitly defined
(which is also true of RTCP SR).&nbsp; Some reference_ID value must be
assumed and there is enough delta between, for example, GPS and UTC,
timebases to cause things to break if the entire system is not implicitly
assumed to be only one timebase. For example, without an explicit
reference_ID, how could one use other timebases defined in NTPv4?&nbsp;
This is a broader issue than the hdr ext syntax, but since we're
discussing NTP, I thought I'd bring it up.<br><br>
I think the above and the other points below are relevant here and not
inconsistent with the RTCP SR methods. The fact that the ATSC design
*can* be more precise is not alone cause to discard the techniques
developed there.<br><br>
Regards,<br><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mike<br><br>
At 09:34 AM 3/31/2009 +0200,
<a href="mailto:Thomas.Schierl@hhi.fraunhofer.de">
Thomas.Schierl@hhi.fraunhofer.de</a> wrote:<br>
<blockquote type=cite class=cite cite="">Dear Michael,<br><br>
Thanks for the comments and the reference to the ATSC M/H.<br><br>
I guess, what we are looking for in AVT is a solution which also works
for encoders having non-perfect clocks. There was a long discussion on
the list, here are two pointers:<br><br>
<a href="http://www.ietf.org/mail-archive/web/avt/current/msg09144.html">
http://www.ietf.org/mail-archive/web/avt/current/msg09144.html</a><br>
<a href="http://www.ietf.org/mail-archive/web/avt/current/msg10491.html" eudora="autourl">
http://www.ietf.org/mail-archive/web/avt/current/msg10491.html</a><br><br>
ATSC surely can assume to have a perfect clock in the NTP streams, which
will not be the case on PC systems that may be used as an encoder for
multi session transmission of a layered codec. This is one major problem
we intended to solve with the header extension while keeping the whole
approach as close as possible in line with the existing RTCP SR
method.<br><br>
<br>
Best regards,<br>
Thomas<br><br>
<br><br>
______________________________________________<br>
Thomas Schierl, Dipl.-Ing.<br>
Fraunhofer HHI<br>
Senior Research Engineer<br>
Image Processing Dept. / Multimedia Transport<br>
Einsteinufer 37, 10587 Berlin, Germany<br>
PHONE: +49 30 31002 227 , FAX: +49 30 392 7200<br>
WEB: <a href="http://ip.hhi.de/">http://ip.hhi.de</a> , SKYPE:
thomas.schierl<br>
EMAIL:
<a href="mailto:thomas.schierl@hhi.fraunhofer.de">
thomas.schierl@hhi.fraunhofer.de</a><br><br>
<br><br>
Michael A Dolan wrote:<br>
<blockquote type=cite class=cite cite="">Those interested in this topic
may also find this interesting:<br><br>
<a href="http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-132r13-A153-Part-3-Transport.pdf">
http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-132r13-A153-Part-3-Transport.pdf</a>
 <br><br>
Section 10.3.<br><br>
Some differences are:<br><br>
1. There is one NTP packet stream per service, rather than the encoding
optimization in the hdr ext;<br>
2. RTCP SR records are emitted &quot;near&quot; video random access
points, rather than on a prescribed time schedule; and<br>
3. The above works in multicast-only, UDLR networks (e.g. television
broadcast), rather than requiring a 2-way link.<br><br>
#2 is interesting since in order to begin a *synchronized* decode (video
+ audio properly correlated), a client must have acquired all of:<br>
a. NTP<br>
b. RTCP SR for each component<br>
c. video reference frame and decoding metadata (i.e. a random access
point)<br>
d. audio frame<br><br>
So, the relative timing of the RTCP SR records to the RTP stream content
is perhaps more important than the emission period.&nbsp; Having the RTCP
SR records arrive faster than the video reference frames doesn't help of
course.&nbsp; And even if they are &quot;fast enough&quot;, having them
arrive out of sync with the reference frames delays the service
acquisition by half the period on average.<br><br>
Bandwidth utilization (how many bits to devote to RTCP and NTP) can
arguably be more efficiently managed by the server in most cases, not
individual client requests for faster RTCP SR packets. And, the client
would have no knowledge of the intended (video) reference frame periods
being used by the server, so it would not, in general, know what to ask
for.<br><br>
In practice, won't a server that wants to enable faster acquisition and
sync do things like the above?&nbsp; I'm concerned that detailed requests
from clients beyond &quot;please use more bandwidth and enable fast
sync&quot; won't be as valuable as they seem since in the general case
the client doesn't know what to ask for exactly.<br><br>
FYI, the above ATSC document is in a &quot;candidate&quot; state where
public comments are solicited.&nbsp; Independent of this thread, if
anyone has comments on it, I could convey them back to the ATSC.<br><br>
Regards,<br><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mike<br><br>
At 07:43 PM 3/9/2009 +0000, Colin Perkins wrote:<br>
<blockquote type=cite class=cite cite="">The changes in this version are
primarily editorial; we're aware that<br>
not all the open issues have been addressed yet. Any further
comments<br>
are welcomed.<br><br>
Chairs: we'd like this to be considered as an AVT working group<br>
draft, as indicated privately.<br><br>
Cheers,<br>
Colin<br><br>
<br><br>
<br>
Begin forwarded message:<br>
<blockquote type=cite class=cite cite="">From:
<a href="mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a><br>
Date: 9 March 2009 17:15:02 GMT<br>
To: <a href="mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a><br>
Subject: I-D Action:draft-perkins-avt-rapid-rtp-sync-03.txt<br>
Reply-To:
<a href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a><br>
<br>
A New Internet-Draft is available from the on-line Internet-Drafts<br>
directories.<br><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Rapid
Synchronisation of RTP Flows<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : C. Perkins, T.
Schierl<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
draft-perkins-avt-rapid-rtp-sync-03.txt<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
17<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
2009-03-09<br><br>
This memo outlines how RTP multimedia sessions are synchronised, and<br>
discusses how rapidly such synchronisation can occur.&nbsp; We show
that<br>
most RTP sessions can be synchronised immediately, but that the use<br>
of video switching multipoint conference units (MCUs) or large
source<br>
specific multicast (SSM) groups can greatly increase the initial<br>
synchronisation delay.&nbsp; This increase in delay can be unacceptable
to<br>
some applications that use layered and/or multi-description
codecs.<br><br>
This memo updates the RTP Control Protocol (RTCP) timing rules to<br>
reduce the initial synchronisation delay for SSM sessions.&nbsp; A
new<br>
feedback packet is defined for use with the Extended RTP Profile for<br>
RTCP-based Feedback (RTP/AVPF), allowing video switching MCUs to<br>
rapidly request resynchronisation.&nbsp; Two new RTP header extensions
are<br>
defined to allow rapid synchronisation of late joiners, and
guarantee<br>
correct timestamp based decoding order recovery for layered codecs
in<br>
the presence of clock skew.<br><br>
A URL for this Internet-Draft is:<br>
<a href="http://www.ietf.org/internet-drafts/draft-perkins-avt-rapid-rtp">
http://www.ietf.org/internet-drafts/draft-perkins-avt-rapid-rtp</a>-
sync-03.txt<br><br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href="ftp://ftp.ietf.org/internet-drafts/">
ftp://ftp.ietf.org/internet-drafts/</a><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>
Content-Type: text/plain<br>
Content-ID:
<a href="mailto:2009-03-09100610.I-D@ietf.org">
&lt;2009-03-09100610.I-D@ietf.org&gt;</a><br><br>
_______________________________________________<br>
I-D-Announce mailing list<br>
<a href="mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/i-d-announce" eudora="autourl">
https://www.ietf.org/mailman/listinfo/i-d-announce</a><br>
Internet-Draft directories:
<a href="http://www.ietf.org/shadow.html">
http://www.ietf.org/shadow.html</a><br>
or
<a href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt">
ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a></blockquote><br>
_______________________________________________<br>
Audio/Video Transport Working Group<br>
<a href="mailto:avt@ietf.org">avt@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/avt" eudora="autourl">
https://www.ietf.org/mailman/listinfo/avt</a></blockquote><br>
_______________________________________________<br>
Audio/Video Transport Working Group<br>
<a href="mailto:avt@ietf.org">avt@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/avt" eudora="autourl">
https://www.ietf.org/mailman/listinfo/avt</a></blockquote><br>
---<br>
Visit us at<br><br>
Web 2.0 Expo / March 31 - April 03 / San Francisco, California / Booth
415<br>
<a href="http://www.web2expo.com/webexsf2009">
http://www.web2expo.com/webexsf2009</a><br>
<br>
NAB SHOW 2009 / April 18-23 / Las Vegas, Nevada USA / South Hall (Upper),
Booth SU9624F<br>
<a href="http://www.nabshow.com/">http://www.nabshow.com/</a></blockquote>
<br>
<pre>


_______________________________________________
Audio/Video Transport Working Group
<a href="mailto:avt@ietf.org">avt@ietf.org</a>
<a href="https://www.ietf.org/mailman/listinfo/avt" eudora="autourl">
https://www.ietf.org/mailman/listinfo/avt</a>
&nbsp;
</pre><font face="Courier New, Courier"></font></blockquote><br><br>
----<br>
Visit us at<br><br>
Web 2.0 Expo / March 31 - April 03 / San Francisco, California / Booth
415<br>
<a href="http://www.web2expo.com/webexsf2009">
http://www.web2expo.com/webexsf2009</a><br><br>
NAB SHOW 2009 / April 18-23 / Las Vegas, Nevada USA / South Hall (Upper),
Booth SU9624F<br>
<a href="http://www.nabshow.com/">http://www.nabshow.com/</a></blockquote>
</body>
</html>

--=====================_67773984==.ALT--


From rpantos@apple.com  Thu Jun 11 10:21:32 2009
Return-Path: <rpantos@apple.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 C67323A6BCD for <avt@core3.amsl.com>; Thu, 11 Jun 2009 10:21:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level: 
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 3BH8Jf1kMH88 for <avt@core3.amsl.com>; Thu, 11 Jun 2009 10:21:32 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 1C5BD3A6910 for <avt@ietf.org>; Thu, 11 Jun 2009 10:21:32 -0700 (PDT)
Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out3.apple.com (Postfix) with ESMTP id D5EE66453F33 for <avt@ietf.org>; Thu, 11 Jun 2009 10:21:39 -0700 (PDT)
Received: from relay16.apple.com (unknown [127.0.0.1]) by relay16.apple.com (Symantec Brightmail Gateway) with ESMTP id C3AA05A0002; Thu, 11 Jun 2009 10:21:39 -0700 (PDT)
X-AuditID: 11807137-a9570bb00000380b-bf-4a313d23aebc
Received: from [17.151.92.150] (unknown [17.151.92.150]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay16.apple.com (Apple SCV relay) with ESMTP id 964A2558002; Thu, 11 Jun 2009 10:21:39 -0700 (PDT)
Message-Id: <67B42F8E-605E-4586-8BEB-C503DC7042DA@apple.com>
From: Roger Pantos <rpantos@apple.com>
To: avt@ietf.org
Content-Type: multipart/alternative; boundary=Apple-Mail-1-145728612
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Thu, 11 Jun 2009 10:21:40 -0700
X-Mailer: Apple Mail (2.935.3)
X-Brightmail-Tracker: AAAAAA==
Cc: http-live-streaming-review <http-live-streaming-review@group.apple.com>
Subject: [AVT] new draft-pantos-http-live-streaming posted
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, 11 Jun 2009 17:21:32 -0000

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


An update to draft-pantos-http-live-streaming has been posted at http://tools.ietf.org/html/draft-pantos-http-live-streaming-01

It clarifies the first draft, based on external feedback (thank you),  
and notes that AES-encrypted media files must use PKCS7 padding.

It also specifies a way to embed an MPEG-2 timestamp inside an MPEG  
Audio Elementary Stream. This allows clients to switch back and forth  
between an MPEG Audio Elementary Stream and an MPEG-2 Transport Stream.

As always, we're looking for constructive feedback on the protocol.

thank you,

Roger Pantos.

--Apple-Mail-1-145728612
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: 7bit

<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div>An update to draft-pantos-http-live-streaming has been posted at&nbsp;<a href="http://tools.ietf.org/html/draft-pantos-http-live-streaming-01">http://tools.ietf.org/html/draft-pantos-http-live-streaming-01</a><br><br>It clarifies the first draft, based on external feedback (thank you), and notes that AES-encrypted media files must use PKCS7 padding.<br><br>It also specifies a way to embed an MPEG-2 timestamp inside an MPEG Audio Elementary Stream. This allows clients to switch back and forth between an MPEG Audio Elementary Stream and an MPEG-2 Transport Stream.<br><br>As always, we're looking for constructive feedback on the protocol.<br><br>thank you,<br><br>Roger Pantos.<br></body></html>
--Apple-Mail-1-145728612--

From Thomas.Schierl@hhi.fraunhofer.de  Fri Jun 12 04:36:36 2009
Return-Path: <Thomas.Schierl@hhi.fraunhofer.de>
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 CF9743A6403 for <avt@core3.amsl.com>; Fri, 12 Jun 2009 04:36:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.072
X-Spam-Level: 
X-Spam-Status: No, score=-4.072 tagged_above=-999 required=5 tests=[AWL=-0.729, BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, 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 7WSTa3ZHD8aM for <avt@core3.amsl.com>; Fri, 12 Jun 2009 04:36:34 -0700 (PDT)
Received: from mail.hhi.fraunhofer.de (mail.HHI.FRAUNHOFER.DE [193.174.67.45]) by core3.amsl.com (Postfix) with ESMTP id 25DFC3A6A28 for <avt@ietf.org>; Fri, 12 Jun 2009 04:36:33 -0700 (PDT)
Received: by mail.hhi.fraunhofer.de (Postfix, from userid 65534) id 178A71D88FB0; Fri, 12 Jun 2009 13:36:40 +0200 (CEST)
Received: from imsva.hhi.de (unknown [127.0.0.1]) by IMSA (Postfix) with ESMTP id D190515003F; Fri, 12 Jun 2009 13:36:38 +0200 (CEST)
Message-ID: <4A323DC5.5020004@hhi.fraunhofer.de>
Date: Fri, 12 Jun 2009 13:36:37 +0200
From: Thomas Schierl <Thomas.Schierl@hhi.fraunhofer.de>
Organization: Fraunhofer HHI
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Michael A Dolan <md.1@newtbt.com>
References: <20090309171502.518513A6359@core3.amsl.com>	<4A6ACB13-0CBB-4DA7-84AD-28CDE56DB4C3@csperkins.org>	<0MKpCa-1LoLs525qX-000cvA@mrelay.perfora.net>	<49D1C793.9050409@hhi.fraunhofer.de>	<0MKp8S-1Lof8c1LTC-000fjs@mrelay.perfora.net>	<49D4AE9D.8060905@hhi.fraunhofer.de> <0MKpCa-1MEnZO1ysE-000d6S@mrelay.perfora.net>
In-Reply-To: <0MKpCa-1MEnZO1ysE-000d6S@mrelay.perfora.net>
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-alterMIME: Yes
Cc: avt <avt@ietf.org>, Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Fwd: I-D  Action:draft-perkins-avt-rapid-rtp-sync-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: Fri, 12 Jun 2009 11:36:36 -0000

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Michael,<br>
<br>
I guess your comments are related to
draft-ietf-avt-rapid-rtp-sync-02.txt. Please find
my comments in line.<br>
<br>
Thomas<br>
<br>
Michael A Dolan wrote:
<blockquote cite="mid:0MKpCa-1MEnZO1ysE-000d6S@mrelay.perfora.net"
 type="cite">Thomas and all-<br>
  <br>
Continuing this in the context of yesterday's WG draft -02:<br>
  <br>
1. The draft still uses "wallclock".&nbsp; I believe what's
important is that the NTP reference clock must have the same
reference_ID
value as the clock used in the RTCP SR records. It's not important that
it be "wallclock" (or more precisely, one of the values defined
in NTPv4).&nbsp; It can be PPS or something else. The draft does mention
that a common clock should be used.&nbsp; The problem I see is that the
language is imprecise WRT NTPv4 terminology and implies a vague subset
of
timebases by using the term, "wallclock". Further, when the hdr
ext for NTP is not used, it should be stated that the NTP timebase
reference_ID must be agreed to out of band between the senders and
receivers.<br>
</blockquote>
<br>
See my original comments attached to your message. I think
we do not want to make any additional requirements on the clock to be
used for
generating the wallclock, i.e. we will keep the definitions in RFC
3550 for backward compatibility reasons.<br>
<br>
<blockquote cite="mid:0MKpCa-1MEnZO1ysE-000d6S@mrelay.perfora.net"
 type="cite"><br>
2. Sync can only occur when the receiver has not only NTP and RTCP SR
packets, but also a point in every RTP session where there is an
"access point" for that media stream.&nbsp; Since these access
points are customarily considerably further apart than 0.04 seconds,
the
tables are a bit misleading on the practical sync time and recommended
RTCP SR emission frequency.&nbsp; It should be noted around all the
tables that there is no benefit to sending the RTCP SR record more
often
than the media access point frequency, especially in combination with
the
next comment below.<br>
</blockquote>
<br>
Sure, there is typically a need for a random access point to start
decoding. So on the first glance it makes sense to send SRs not with a
higher frequency than random access points. But there may be a benefit
to send SRs more frequently, e.g., to estimate clock skews.<br>
<br>
<blockquote cite="mid:0MKpCa-1MEnZO1ysE-000d6S@mrelay.perfora.net"
 type="cite"><br>
3. It should be recommended that RTCP SR packets be sent near, and
immediately following, media access points (subject to the 5%
boundary).
Doing so will greatly improve the sync time rather than relying on more
frequent, and/or randomly timed, RTCP SR packets.<br>
</blockquote>
<br>
Generally, it should not be a problem to slightly delay RTCP packets in
order to align
with media random access points, but this would need further analysis
to
document the acceptable bounds. I guess this would require more time
and would further delay the intended solution for layered codecs. In
order to not further delay the solution in this draft, this could
become a topic of another draft. <br>
<br>
<blockquote cite="mid:0MKpCa-1MEnZO1ysE-000d6S@mrelay.perfora.net"
 type="cite"><br>
Comment #1 becomes even more important the faster you want to sync.&nbsp;
If the RTP sessions are using GPS and the NTP source is using UTC (both
"wallclock"), there will be errors measured in seconds.&nbsp;
This disparity is less likely when the hdr ext is used, of course. But
in
the general case, this language needs tightening up to remove the clock
errors.<br>
  <br>
Comments 2 &amp; 3, although true in all scenarios, become more
relevant
in SSM with late joiners.<br>
  <br>
I hope the above comments are clearer than my attempts below.&nbsp; I'm
happy to suggest specific edits to the draft if that will help.<br>
  <br>
Regards,<br>
  <br>
  <x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Mike<br>
  <br>
At 02:25 PM 4/2/2009 +0200, <a class="moz-txt-link-abbreviated" href="mailto:Thomas.Schierl@hhi.fraunhofer.de">Thomas.Schierl@hhi.fraunhofer.de</a> wrote:<br>
  <blockquote type="cite" class="cite" cite="">Hi Michael,<br>
    <br>
What I can see from the ATSC M/H Transport spec is that there are
requirements on encoder and decoder clock precisions, which for sure
give
a complete different environment than assumed by RFC3550 with respect
to
the clock precision. If we could assure such clocks for all devices
which
may potentially encode and stream layered media via multi session
transmission, the problem would have been solved anyway. But that is
not
the case, as I tried to show by pointing to some of the relevant
discussions on the mailing list.<br>
    <br>
About your second point: RTP does not require NTP to be used as
wallclock. In RTP, there is much more freedom in selecting the source
for
this clock. RTP uses the NTP timestamp format just for indicating the
wallclock in the RTCP sender reports. Furthermore
draft-perkins-avt-rapid-rtp-sync-03 does only require to use the same
wallclock as used for the SRs also for the wallclock timestamps in the
header extensions.<br>
    <br>
Another interesting point is that the ATSC Transport spec is not
mentioning SVC while mentioning AVC and AAC. If looking at the ATSC
Video
Systems spec.
(<a moz-do-not-send="true"
 href="http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-136r7-A153-Part-7-Video-System.pdf">
S4-136r7-A153-Part-7-Video-System</a>), there is a solution which
requires RTP timestamp synchronization for "SVC Transport in Two RTP
Sessions". This for sure solves the clock skew problem, but as
discussed in AVT, this is not a general solution and has different
implications if applied to all use cases of RTP multi session
transmission as, e.g. conversational services. Therefore we now have a
solution which seems to be agreeable by the group, which solves the
problem and is more in line with RFC 3550, i.e. using the wallclock for
the data alignment between the session.<br>
    <br>
Best regards,<br>
Thomas<br>
    <br>
    <br>
Michael A Dolan wrote: <br>
    <blockquote type="cite" class="cite" cite="">Hi Thomas-<br>
      <br>
Thanks.&nbsp; Yes, I am familiar with the discussion.<br>
      <br>
I'm not necessarily pushing the ATSC solution, but offering some points
to consider, which apply equally to the problem at hand here, I
think.<br>
      <br>
Also, it is important to note some more things about the ATSC
text:<br>
      <br>
1. The language in the specification very carefully recommends the
clock
precision without requiring it.&nbsp; It is expected to work over routers
with jitter and delays and with media components from outside the
broadcast facility. The difference is that the client is expected to be
able to perform tight sync when the servers are able to provide the
recommended timing model (encoding one hop away, etc).&nbsp; It
gracefully degrades to "Internet" timing model
quality.<br>
      <br>
2. The clock, although "NTP" syntax, is not time of day (e.g.
reference_ID= "GPS"), but "PPS", thus allowing the
components to be encoded and decoded without concern for end-to-end
delivery delay.&nbsp; This only works when NTP is explicitly signaled as
part of the encoding and both components share a clock (same or closely
coupled encoders). So it will not work in the general case.&nbsp; But
there are many systems where it will and perhaps consideration should
be
given to permitting non-"wall clock" timebases.<br>
      <br>
The NTP hdr ext here is an encoding optimization that indeed has some
other good properties.&nbsp; Although the draft ties the NTP timestamp
back to the RTCP SR records, the timebase is not explicitly defined
(which is also true of RTCP SR).&nbsp; Some reference_ID value must be
assumed and there is enough delta between, for example, GPS and UTC,
timebases to cause things to break if the entire system is not
implicitly
assumed to be only one timebase. For example, without an explicit
reference_ID, how could one use other timebases defined in NTPv4?&nbsp;
This is a broader issue than the hdr ext syntax, but since we're
discussing NTP, I thought I'd bring it up.<br>
      <br>
I think the above and the other points below are relevant here and not
inconsistent with the RTCP SR methods. The fact that the ATSC design
*can* be more precise is not alone cause to discard the techniques
developed there.<br>
      <br>
Regards,<br>
      <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mike<br>
      <br>
At 09:34 AM 3/31/2009 +0200,
      <a moz-do-not-send="true"
 href="mailto:Thomas.Schierl@hhi.fraunhofer.de">Thomas.Schierl@hhi.fraunhofer.de</a>
wrote:<br>
      <blockquote type="cite" class="cite" cite="">Dear Michael,<br>
        <br>
Thanks for the comments and the reference to the ATSC M/H.<br>
        <br>
I guess, what we are looking for in AVT is a solution which also works
for encoders having non-perfect clocks. There was a long discussion on
the list, here are two pointers:<br>
        <br>
        <a moz-do-not-send="true"
 href="http://www.ietf.org/mail-archive/web/avt/current/msg09144.html">
http://www.ietf.org/mail-archive/web/avt/current/msg09144.html</a><br>
        <a moz-do-not-send="true"
 href="http://www.ietf.org/mail-archive/web/avt/current/msg10491.html"
 eudora="autourl">
http://www.ietf.org/mail-archive/web/avt/current/msg10491.html</a><br>
        <br>
ATSC surely can assume to have a perfect clock in the NTP streams,
which
will not be the case on PC systems that may be used as an encoder for
multi session transmission of a layered codec. This is one major
problem
we intended to solve with the header extension while keeping the whole
approach as close as possible in line with the existing RTCP SR
method.<br>
        <br>
        <br>
Best regards,<br>
Thomas<br>
        <br>
        <br>
        <br>
______________________________________________<br>
Thomas Schierl, Dipl.-Ing.<br>
Fraunhofer HHI<br>
Senior Research Engineer<br>
Image Processing Dept. / Multimedia Transport<br>
Einsteinufer 37, 10587 Berlin, Germany<br>
PHONE: +49 30 31002 227 , FAX: +49 30 392 7200<br>
WEB: <a moz-do-not-send="true" href="http://ip.hhi.de/">http://ip.hhi.de</a>
, SKYPE:
thomas.schierl<br>
EMAIL:
        <a moz-do-not-send="true"
 href="mailto:thomas.schierl@hhi.fraunhofer.de">thomas.schierl@hhi.fraunhofer.de</a><br>
        <br>
        <br>
        <br>
Michael A Dolan wrote:<br>
        <blockquote type="cite" class="cite" cite="">Those interested
in this topic
may also find this interesting:<br>
          <br>
          <a moz-do-not-send="true"
 href="http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-132r13-A153-Part-3-Transport.pdf">
http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-132r13-A153-Part-3-Transport.pdf</a>
          <br>
          <br>
Section 10.3.<br>
          <br>
Some differences are:<br>
          <br>
1. There is one NTP packet stream per service, rather than the encoding
optimization in the hdr ext;<br>
2. RTCP SR records are emitted "near" video random access
points, rather than on a prescribed time schedule; and<br>
3. The above works in multicast-only, UDLR networks (e.g. television
broadcast), rather than requiring a 2-way link.<br>
          <br>
#2 is interesting since in order to begin a *synchronized* decode
(video
+ audio properly correlated), a client must have acquired all of:<br>
a. NTP<br>
b. RTCP SR for each component<br>
c. video reference frame and decoding metadata (i.e. a random access
point)<br>
d. audio frame<br>
          <br>
So, the relative timing of the RTCP SR records to the RTP stream
content
is perhaps more important than the emission period.&nbsp; Having the RTCP
SR records arrive faster than the video reference frames doesn't help
of
course.&nbsp; And even if they are "fast enough", having them
arrive out of sync with the reference frames delays the service
acquisition by half the period on average.<br>
          <br>
Bandwidth utilization (how many bits to devote to RTCP and NTP) can
arguably be more efficiently managed by the server in most cases, not
individual client requests for faster RTCP SR packets. And, the client
would have no knowledge of the intended (video) reference frame periods
being used by the server, so it would not, in general, know what to ask
for.<br>
          <br>
In practice, won't a server that wants to enable faster acquisition and
sync do things like the above?&nbsp; I'm concerned that detailed requests
from clients beyond "please use more bandwidth and enable fast
sync" won't be as valuable as they seem since in the general case
the client doesn't know what to ask for exactly.<br>
          <br>
FYI, the above ATSC document is in a "candidate" state where
public comments are solicited.&nbsp; Independent of this thread, if
anyone has comments on it, I could convey them back to the ATSC.<br>
          <br>
Regards,<br>
          <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mike<br>
          <br>
At 07:43 PM 3/9/2009 +0000, Colin Perkins wrote:<br>
          <blockquote type="cite" class="cite" cite="">The changes in
this version are
primarily editorial; we're aware that<br>
not all the open issues have been addressed yet. Any further
comments<br>
are welcomed.<br>
            <br>
Chairs: we'd like this to be considered as an AVT working group<br>
draft, as indicated privately.<br>
            <br>
Cheers,<br>
Colin<br>
            <br>
            <br>
            <br>
            <br>
Begin forwarded message:<br>
            <blockquote type="cite" class="cite" cite="">From:
              <a moz-do-not-send="true"
 href="mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a><br>
Date: 9 March 2009 17:15:02 GMT<br>
To: <a moz-do-not-send="true" href="mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a><br>
Subject: I-D Action:draft-perkins-avt-rapid-rtp-sync-03.txt<br>
Reply-To:
              <a moz-do-not-send="true"
 href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a><br>
              <br>
A New Internet-Draft is available from the on-line Internet-Drafts<br>
directories.<br>
              <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Rapid
Synchronisation of RTP Flows<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : C. Perkins, T.
Schierl<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
draft-perkins-avt-rapid-rtp-sync-03.txt<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
17<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
2009-03-09<br>
              <br>
This memo outlines how RTP multimedia sessions are synchronised, and<br>
discusses how rapidly such synchronisation can occur.&nbsp; We show
that<br>
most RTP sessions can be synchronised immediately, but that the use<br>
of video switching multipoint conference units (MCUs) or large
source<br>
specific multicast (SSM) groups can greatly increase the initial<br>
synchronisation delay.&nbsp; This increase in delay can be unacceptable
to<br>
some applications that use layered and/or multi-description
codecs.<br>
              <br>
This memo updates the RTP Control Protocol (RTCP) timing rules to<br>
reduce the initial synchronisation delay for SSM sessions.&nbsp; A
new<br>
feedback packet is defined for use with the Extended RTP Profile for<br>
RTCP-based Feedback (RTP/AVPF), allowing video switching MCUs to<br>
rapidly request resynchronisation.&nbsp; Two new RTP header extensions
are<br>
defined to allow rapid synchronisation of late joiners, and
guarantee<br>
correct timestamp based decoding order recovery for layered codecs
in<br>
the presence of clock skew.<br>
              <br>
A URL for this Internet-Draft is:<br>
              <a moz-do-not-send="true"
 href="http://www.ietf.org/internet-drafts/draft-perkins-avt-rapid-rtp">
http://www.ietf.org/internet-drafts/draft-perkins-avt-rapid-rtp</a>-
sync-03.txt<br>
              <br>
Internet-Drafts are also available by anonymous FTP at:<br>
              <a moz-do-not-send="true"
 href="ftp://ftp.ietf.org/internet-drafts/">
ftp://ftp.ietf.org/internet-drafts/</a><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>
Content-Type: text/plain<br>
Content-ID:
              <a moz-do-not-send="true"
 href="mailto:2009-03-09100610.I-D@ietf.org">&lt;2009-03-09100610.I-D@ietf.org&gt;</a><br>
              <br>
_______________________________________________<br>
I-D-Announce mailing list<br>
              <a moz-do-not-send="true"
 href="mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org</a><br>
              <a moz-do-not-send="true"
 href="https://www.ietf.org/mailman/listinfo/i-d-announce"
 eudora="autourl">
https://www.ietf.org/mailman/listinfo/i-d-announce</a><br>
Internet-Draft directories:
              <a moz-do-not-send="true"
 href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a><br>
or
              <a moz-do-not-send="true"
 href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a></blockquote>
            <br>
_______________________________________________<br>
Audio/Video Transport Working Group<br>
            <a moz-do-not-send="true" href="mailto:avt@ietf.org">avt@ietf.org</a><br>
            <a moz-do-not-send="true"
 href="https://www.ietf.org/mailman/listinfo/avt" eudora="autourl">
https://www.ietf.org/mailman/listinfo/avt</a></blockquote>
          <br>
_______________________________________________<br>
Audio/Video Transport Working Group<br>
          <a moz-do-not-send="true" href="mailto:avt@ietf.org">avt@ietf.org</a><br>
          <a moz-do-not-send="true"
 href="https://www.ietf.org/mailman/listinfo/avt" eudora="autourl">
https://www.ietf.org/mailman/listinfo/avt</a></blockquote>
        <br>
---<br>
Visit us at<br>
        <br>
Web 2.0 Expo / March 31 - April 03 / San Francisco, California / Booth
415<br>
        <a moz-do-not-send="true"
 href="http://www.web2expo.com/webexsf2009">
http://www.web2expo.com/webexsf2009</a><br>
        <br>
NAB SHOW 2009 / April 18-23 / Las Vegas, Nevada USA / South Hall
(Upper),
Booth SU9624F<br>
        <a moz-do-not-send="true" href="http://www.nabshow.com/">http://www.nabshow.com/</a></blockquote>
      <br>
      <pre>

_______________________________________________
Audio/Video Transport Working Group
<a moz-do-not-send="true" href="mailto:avt@ietf.org">avt@ietf.org</a>
<a moz-do-not-send="true"
 href="https://www.ietf.org/mailman/listinfo/avt" eudora="autourl">
https://www.ietf.org/mailman/listinfo/avt</a>
&nbsp;
      </pre>
    </blockquote>
    <br>
    <br>
----<br>
Visit us at<br>
    <br>
Web 2.0 Expo / March 31 - April 03 / San Francisco, California / Booth
415<br>
    <a moz-do-not-send="true" href="http://www.web2expo.com/webexsf2009">
http://www.web2expo.com/webexsf2009</a><br>
    <br>
NAB SHOW 2009 / April 18-23 / Las Vegas, Nevada USA / South Hall
(Upper),
Booth SU9624F<br>
    <a moz-do-not-send="true" href="http://www.nabshow.com/">http://www.nabshow.com/</a></blockquote>
  <pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Audio/Video Transport Working Group
<a class="moz-txt-link-abbreviated" href="mailto:avt@ietf.org">avt@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/avt">https://www.ietf.org/mailman/listinfo/avt</a>
  </pre>
</blockquote>
<BR>
<br>
----<br>
Visit us at<br><br>

IEEE ICC 2009 / June 14-18 / Dresden, Germany / International Congress Center<br>
<a href="http://www.comsoc.org/confs/icc/2009/">http://www.comsoc.org/confs/icc/2009/</a><br><br>

Laser World of Photonics 2009 / June 15-18 / Munich, Germay / Hall B1, Booth 461<br>
<a href="http://world-of-photonics.net/de/laser/start">http://world-of-photonics.net/de/laser/start</a><BR>
</body>
</html>


From fluffy@cisco.com  Fri Jun 12 10:28:03 2009
Return-Path: <fluffy@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 B414D3A69D1; Fri, 12 Jun 2009 10:28:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.577
X-Spam-Level: 
X-Spam-Status: No, score=-106.577 tagged_above=-999 required=5 tests=[AWL=0.022, 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 DLkFl7gALcT7; Fri, 12 Jun 2009 10:27:59 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id E5D193A69EA; Fri, 12 Jun 2009 10:27:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,210,1243814400"; d="scan'208";a="322588397"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 12 Jun 2009 17:28:01 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n5CHS112011583;  Fri, 12 Jun 2009 10:28:01 -0700
Received: from [192.168.0.101] (sjc-vpn7-1408.cisco.com [10.21.149.128]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n5CHR8sA016154; Fri, 12 Jun 2009 17:28:00 GMT
Message-Id: <2E380046-B986-4F34-9246-C818383B27DD@cisco.com>
From: Cullen Jennings <fluffy@cisco.com>
To: dispatch@ietf.org, IETF AVT WG <avt@ietf.org>, rai@ietf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 12 Jun 2009 11:28:00 -0600
X-Mailer: Apple Mail (2.935.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=651; t=1244827681; x=1245691681; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20<fluffy@cisco.com> |Subject:=20CODEC=20BOF |Sender:=20; bh=wfkcTHM0n2sN63DfLRfMASTlZ4MM1mtyyyNSYvGSwvc=; b=yEJTjj+dIColrydll6m5Ad1bDMZU/SN8It7C1/6eUPdbyhm1hvF1eNHUPV vy/no62/68VhmQJ9VPihRK8U6LYqk6rFDeSl0GYRry147b3eiyTSi2k+PwPn 8Zztng7xIC;
Authentication-Results: sj-dkim-2; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Subject: [AVT] CODEC BOF
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, 12 Jun 2009 17:28:04 -0000

The CODEC proposal to form a WG on Internet Wideband Audio Codecs has  
been raised many issues - I think it is better to consider this in the  
context of a formal BOF instead of discussing it in the DISPATCH WG. I  
have approved this BOF for the next meeting but there are many issues  
that have been raised and need discussion before this would be  
approved as a WG.  I encourage people to take those to the codec@ietf.org 
  list.

Please to not reply to this email (particularly since I cross posted  
to three WG), but instead go join the threads on the codec@ietf.org  
mailing list to discuss this.

Thanks,
Cullen <RAI AD>



From fluffy@cisco.com  Fri Jun 12 10:59:35 2009
Return-Path: <fluffy@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 8FFFC3A6B29; Fri, 12 Jun 2009 10:59:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.578
X-Spam-Level: 
X-Spam-Status: No, score=-106.578 tagged_above=-999 required=5 tests=[AWL=0.021, 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 lqsWY7elylsv; Fri, 12 Jun 2009 10:59:34 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 69A0E28C244; Fri, 12 Jun 2009 10:59:03 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,210,1243814400"; d="scan'208";a="80563146"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-5.cisco.com with ESMTP; 12 Jun 2009 17:59:11 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n5CHxB0W016218;  Fri, 12 Jun 2009 10:59:11 -0700
Received: from [192.168.0.101] (sjc-vpn7-1408.cisco.com [10.21.149.128]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n5CHwImO006518; Fri, 12 Jun 2009 17:59:08 GMT
Message-Id: <8867B97F-7929-47BF-9483-9158AA8300CD@cisco.com>
From: Cullen Jennings <fluffy@cisco.com>
To: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <2E380046-B986-4F34-9246-C818383B27DD@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 12 Jun 2009 11:59:07 -0600
References: <2E380046-B986-4F34-9246-C818383B27DD@cisco.com>
X-Mailer: Apple Mail (2.935.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=842; t=1244829551; x=1245693551; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20<fluffy@cisco.com> |Subject:=20Re=3A=20CODEC=20BOF |Sender:=20; bh=8zKkT3sdJct9hm/aLwNlpnvwYX7uw/ZRdQ3mOJO0s5E=; b=MjxIdzDJTkA/cN6dGLZmUekpZjSwoshBNMDxbmBtx7U+yCUEJewmQLYUMd bSSlSO92hKgSiwro8OKziShd1thkaYrsLz2/pm9+xgi5y1VHjK7e7IAIl6D6 HCGFSXlE986EPe4lfmLkLJQmV0UeYNNXhe50oJUINVHH/kS8KEa2M=;
Authentication-Results: sj-dkim-1; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Cc: dispatch@ietf.org, rai@ietf.org, IETF AVT WG <avt@ietf.org>
Subject: Re: [AVT] CODEC BOF
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, 12 Jun 2009 17:59:35 -0000

I forgot to add, you can join the codec@ietf list at
https://www.ietf.org/mailman/listinfo/codec


On Jun 12, 2009, at 11:28 , Cullen Jennings wrote:

>
> The CODEC proposal to form a WG on Internet Wideband Audio Codecs  
> has been raised many issues - I think it is better to consider this  
> in the context of a formal BOF instead of discussing it in the  
> DISPATCH WG. I have approved this BOF for the next meeting but there  
> are many issues that have been raised and need discussion before  
> this would be approved as a WG.  I encourage people to take those to  
> the codec@ietf.org list.
>
> Please to not reply to this email (particularly since I cross posted  
> to three WG), but instead go join the threads on the codec@ietf.org  
> mailing list to discuss this.
>
> Thanks,
> Cullen <RAI AD>
>
>


From Thomas.Schierl@hhi.fraunhofer.de  Mon Jun 15 01:50:10 2009
Return-Path: <Thomas.Schierl@hhi.fraunhofer.de>
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 CAFFA3A6CB5 for <avt@core3.amsl.com>; Mon, 15 Jun 2009 01:50:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.437
X-Spam-Level: 
X-Spam-Status: No, score=-4.437 tagged_above=-999 required=5 tests=[AWL=0.365,  BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, 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 ahBEFXGUUooy for <avt@core3.amsl.com>; Mon, 15 Jun 2009 01:50:09 -0700 (PDT)
Received: from mail.hhi.fraunhofer.de (mail.HHI.FRAUNHOFER.DE [193.174.67.45]) by core3.amsl.com (Postfix) with ESMTP id 513AB3A6CAD for <avt@ietf.org>; Mon, 15 Jun 2009 01:50:09 -0700 (PDT)
Received: by mail.hhi.fraunhofer.de (Postfix, from userid 65534) id B09DC1D8901B; Mon, 15 Jun 2009 10:46:57 +0200 (CEST)
Received: from imsva.hhi.de (unknown [127.0.0.1]) by IMSA (Postfix) with ESMTP id C2B461500D2; Mon, 15 Jun 2009 10:46:56 +0200 (CEST)
Received: from [10.8.0.150] (unknown [10.8.0.150]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Thomas Schierl", Issuer "Fraunhofer-Gesellschaft Root-CA v2" (not verified)) by mail.hhi.fraunhofer.de (Postfix) with ESMTP id ECEC01D89012; Mon, 15 Jun 2009 10:46:55 +0200 (CEST)
Message-ID: <4A360A7E.4090400@hhi.fraunhofer.de>
Date: Mon, 15 Jun 2009 10:46:54 +0200
From: Thomas Schierl <Thomas.Schierl@hhi.fraunhofer.de>
Organization: Fraunhofer HHI
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: avt <avt@ietf.org>
Content-Type: multipart/mixed; boundary="------------000504050107040606080402"
X-alterMIME: Yes
Cc: Roni Even <ron.even.tlv@gmail.com>, Tom Taylor <tom.taylor@rogers.com>, Colin Perkins <csp@csperkins.org>
Subject: [AVT] [Fwd: I-D Action:draft-ietf-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: Mon, 15 Jun 2009 08:50:10 -0000

This is a multi-part message in MIME format.
--------------000504050107040606080402
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear all,

Please find pointer to the revised version -02 of 
draft-ietf-avt-rapid-rtp-sync below.

We addressed the reaming open issues and completed all sections.

Any comments are welcome. Due to the timing constraints, we would like 
to ask if we can go ahead with WGLC for this draft.

Best regards,
Thomas

-- 
Thomas Schierl
--------------
Fraunhofer HHI


---
Visit us at

IEEE ICC 2009 / June 14-18 / Dresden, Germany / International Congress Center
http://www.hhi.fraunhofer.de/icc

Laser World of Photonics 2009 / June 15-18 / Munich, Germay / Hall B1, Booth 461
http://world-of-photonics.net/de/laser/start
--------------000504050107040606080402
Content-Type: message/rfc822;
 name="I-D Action:draft-ietf-avt-rapid-rtp-sync-02.txt.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="I-D Action:draft-ietf-avt-rapid-rtp-sync-02.txt.eml"

X-Account-Key: account2
X-Mozilla-Keys: 
Return-Path: <i-d-announce-bounces@ietf.org>
Received: from mail.hhi.fraunhofer.de ([unix socket])
	by mail (Cyrus v2.2.3) with LMTP; Thu, 11 Jun 2009 16:45:49 +0200
X-Sieve: CMU Sieve 2.2
Received: by mail.hhi.fraunhofer.de (Postfix, from userid 65534)
	id E98BE1D88FF7; Thu, 11 Jun 2009 16:45:49 +0200 (CEST)
Received: from imsva.hhi.de (unknown [127.0.0.1])
	by IMSA (Postfix) with ESMTP id 3523415003F
	for <schierl@localhost.hhi.fraunhofer.de>; Thu, 11 Jun 2009 16:45:49 +0200 (CEST)
Received: from mail.ietf.org (mail.ietf.org [64.170.98.32])
	by mail.hhi.fraunhofer.de (Postfix) with ESMTP id 377AC1D88FE6
	for <schierl@hhi.fhg.de>; Thu, 11 Jun 2009 16:45:49 +0200 (CEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5AC5628C0E7;
	Thu, 11 Jun 2009 07:45:03 -0700 (PDT)
X-Original-To: i-d-announce@ietf.org
Delivered-To: i-d-announce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id BF3B83A69E0; Thu, 11 Jun 2009 07:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-avt-rapid-rtp-sync-02.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090611144501.BF3B83A69E0@core3.amsl.com>
Date: Thu, 11 Jun 2009 07:45:01 -0700 (PDT)
Cc: avt@ietf.org
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/i-d-announce>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
Sender: i-d-announce-bounces@ietf.org
Errors-To: i-d-announce-bounces@ietf.org


--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           : Rapid Synchronisation of RTP Flows
	Author(s)       : C. Perkins, T. Schierl
	Filename        : draft-ietf-avt-rapid-rtp-sync-02.txt
	Pages           : 22
	Date            : 2009-06-11

This memo outlines how RTP 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 synchronisation
delay.  This increase in delay can be unacceptable to some
applications that use layered and/or multi-description codecs.

This memo introduces three mechanisms to reduce the synchronisation
delay for such sessions.  First, it updates the RTP Control Protocol
(RTCP) timing rules to reduce the initial synchronisation delay for
SSM sessions.  Second, 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.  Finally,
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-ietf-avt-rapid-rtp-sync-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-rapid-rtp-sync-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

--NextPart--



--------------000504050107040606080402--


From root@core3.amsl.com  Mon Jun 15 03: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 9F96928C101; Mon, 15 Jun 2009 03:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090615103001.9F96928C101@core3.amsl.com>
Date: Mon, 15 Jun 2009 03:30:01 -0700 (PDT)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-seed-srtp-14.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, 15 Jun 2009 10: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)       : S. Yoon, et al.
	Filename        : draft-ietf-avt-seed-srtp-14.txt
	Pages           : 13
	Date            : 2009-06-15

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-14.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-14.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From emil@sip-communicator.org  Mon Jun 15 07:36:18 2009
Return-Path: <emil@sip-communicator.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 888A03A6CCA for <avt@core3.amsl.com>; Mon, 15 Jun 2009 07:36:18 -0700 (PDT)
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.000,  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 z19UQdcVIxiA for <avt@core3.amsl.com>; Mon, 15 Jun 2009 07:36:17 -0700 (PDT)
Received: from mail-ew0-f210.google.com (mail-ew0-f210.google.com [209.85.219.210]) by core3.amsl.com (Postfix) with ESMTP id 8773E3A67E7 for <avt@ietf.org>; Mon, 15 Jun 2009 07:36:17 -0700 (PDT)
Received: by ewy6 with SMTP id 6so5076938ewy.37 for <avt@ietf.org>; Mon, 15 Jun 2009 07:35:12 -0700 (PDT)
Received: by 10.210.27.20 with SMTP id a20mr3157359eba.67.1245076511694; Mon, 15 Jun 2009 07:35:11 -0700 (PDT)
Received: from porcinet.local (shm67-5-88-165-90-188.fbx.proxad.net [88.165.90.188]) by mx.google.com with ESMTPS id 10sm56545eyz.11.2009.06.15.07.35.10 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 15 Jun 2009 07:35:11 -0700 (PDT)
Message-ID: <4A365C1E.6030803@sip-communicator.org>
Date: Mon, 15 Jun 2009 16:35:10 +0200
From: Emil Ivov <emcho@sip-communicator.org>
Organization: SIP Communicator
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: "Audio/Video Transport (AVT) WG" <avt@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [AVT] Sound Level Indicators
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, 15 Jun 2009 14:36:18 -0000

Hi all,

We have just submitted the following draft:

http://www.ietf.org/internet-drafts/draft-ivov-avt-slic-00.txt

The draft proposes a solution for a problem that's been extensively
discussed on the dispatch mailing list during the past few weeks. It
concerned a means of transporting sound level in conferences in a way
that would allow presenting it to the user and extending the active
speaker concept.

We are looking forward to hearing any comments and would especially
appreciate suggestions about how to address the open issues listed in
the last section of the draft.

Cheers
Enrico and Emil


From vsemanic@yahoo.com  Mon Jun 15 07:03:12 2009
Return-Path: <vsemanic@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 BAB7F3A6CCC for <avt@core3.amsl.com>; Mon, 15 Jun 2009 07:03:12 -0700 (PDT)
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 flLmAL1ob5eX for <avt@core3.amsl.com>; Mon, 15 Jun 2009 07:03:11 -0700 (PDT)
Received: from n65.bullet.mail.sp1.yahoo.com (n65.bullet.mail.sp1.yahoo.com [98.136.44.190]) by core3.amsl.com (Postfix) with SMTP id BA9DF3A6CC3 for <avt@ietf.org>; Mon, 15 Jun 2009 07:03:11 -0700 (PDT)
Received: from [216.252.122.217] by n65.bullet.mail.sp1.yahoo.com with NNFMP; 15 Jun 2009 14:03:13 -0000
Received: from [69.147.65.155] by t2.bullet.sp1.yahoo.com with NNFMP; 15 Jun 2009 14:03:13 -0000
Received: from [127.0.0.1] by omp403.mail.sp1.yahoo.com with NNFMP; 15 Jun 2009 14:03:13 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 312715.57236.bm@omp403.mail.sp1.yahoo.com
Received: (qmail 62007 invoked by uid 60001); 15 Jun 2009 14:03:13 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1245074593; bh=2QN3fK4MVbrEQgKOUfH1QbpDC8xWCYglyDvp83Z03gg=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=1nOds2QLrkCvs05JN3lWc4QOpARCn3uZN6cYJoPhiLy1uEGG8uWEvv/EiKC93+vRvbxPH8HRwllDpEkNA+ArLwUyY3lJfZsvfUI4MbwdYJwXKei2E6QxUoDSThU7LJjuQ7t7Jq3IQWy2NvXyIG1FNA7pcxy8p+KxZaXkptDj3Ho=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=KHw3V3nejtR0uk+tqqIyukPTTxKmiIUg3FydAxtPT+PjLUY0394PZBVjrBRad1H0lDm6FC620O0fBUGGyY9GiwkHAjqoNk6nQ5iy2Jg6vvm5ZJrY6sh0F5fEMEGKWiTKvFy0rYo9k87Owt+S/F/76GYcWldkHlMxqPyvqYUuoUg=;
Message-ID: <173301.58986.qm@web45012.mail.sp1.yahoo.com>
X-YMail-OSG: a.0OvvEVM1n7KoBJDqOpZus1ZgFW3qWmGbDFyfuGp8D5iEWAl7rTyQSbgMiAEyVAQ6cWHnNU0bzM6y7aMTZgvwt7kwG101Lnn09AyEJZ685oE.kLmiv1Cby8ChUsMwXGSNI6S1ikmq_z2WyJCAnDYkWKueR4uaNL6SeLVw6HZpP.9Cw8_YsZcmDEj5qjpc32i65eq95N6LsBd5BZbrUDf60m6nJb2_bKRTF7nW.38YzbjZ2hLlfgXXaSK6FtVJHQd5XcwhUMveZ5_8hM
Received: from [135.245.10.2] by web45012.mail.sp1.yahoo.com via HTTP; Mon, 15 Jun 2009 07:03:12 PDT
X-Mailer: YahooMailClassic/5.4.12 YahooMailWebService/0.7.289.15
Date: Mon, 15 Jun 2009 07:03:12 -0700 (PDT)
From: Victor Semanic <vsemanic@yahoo.com>
To: avt@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-761572944-1245074592=:58986"
X-Mailman-Approved-At: Mon, 15 Jun 2009 14:00:00 -0700
Subject: [AVT] SSRC in SRTP
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, 15 Jun 2009 14:03:12 -0000

--0-761572944-1245074592=:58986
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hello:

SRTP says that a cryptographic context is uniquely
identified by the tuple
{SSRC, destination network address, destination port}.

Given this, assume that an SRTP stack has been primed
with the master key, salt, and other parameters except
SSRC through the key management protocol, and the
sender is ready to send the very first SRTP packet.

When a sender sends the very first packet, RFC 3711 says
that the sender determines which cryptographic context
to use.=A0 Since this is the first packet, the sender
uses *it's* SSRC, destination network address and
destination port and creates a cryptographic context.
Let's assume that the sender's SSRC is 0x2ab6,
destination address is IP-B and destination port is
PORT-B.=A0 So, the cryptographic context for the
sender is:

=A0 {0x2ab6, IP-B, PORT-B}

The packet is then encrypted and transmitted to the
recipient.=A0 Do I have it right so far?

When the recipient receives the SRTP packet, it proceeds
to decrypt it.=A0 RFC 3711 says that the receipient shall
first determine which cryptographic context is to be
used.=A0 As before, the cryptographic context is:

{SSRC, destination network address, destination port}

But here's where I have a doubt: I presume that the
destination network address and destination port are
retrieved from the IP header (i.e., they correspond to
the receiving host IP address and receiving host port -- IP-B
and PORT-B, respectively.)=A0 And the SSRC is obtained
from the SRTP header (is that right?)=A0 So, the cryptographic=20
context for the recipient is the same as that of the=20
sender, namely:

=A0=A0 {0x2ab6, IP-B, PORT-B}

Am I correct?=A0 Can someone please confirm this.
Assuming this is so, then when the recipient prepares to
send the first SRTP packet to its peer (IP-A, PORT-A),
it will create a new cryptographic context by deriving a
SSRC (0x67af) and using IP-A, PORT-A in the tuple:

=A0=A0 {0x67af, IP-A, PORT-A}

Similarly, when the peer receives the SRTP packet, it will
create a new cryptographic context consisting of the same
tuple.

So for each participant, there are two cryptographic contexts:
one to send and one to receive.=A0 Am I correct?=A0 I will
appreciate if someone can confirm this or help me understand
where I am in error.

Thank you.
=0A=0A=0A      
--0-761572944-1245074592=:58986
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;">Hello:<br><br>SRTP says that a cryptographic =
context is uniquely<br>identified by the tuple<br>{SSRC, destination networ=
k address, destination port}.<br><br>Given this, assume that an SRTP stack =
has been primed<br>with the master key, salt, and other parameters except<b=
r>SSRC through the key management protocol, and the<br>sender is ready to s=
end the very first SRTP packet.<br><br>When a sender sends the very first p=
acket, RFC 3711 says<br>that the sender determines which cryptographic cont=
ext<br>to use.&nbsp; Since this is the first packet, the sender<br>uses *it=
's* SSRC, destination network address and<br>destination port and creates a=
 cryptographic context.<br>Let's assume that the sender's SSRC is 0x2ab6,<b=
r>destination address is IP-B and destination port is<br>PORT-B.&nbsp; So, =
the cryptographic context for the<br>sender is:<br><br>&nbsp; {0x2ab6, IP-B=
,
 PORT-B}<br><br>The packet is then encrypted and transmitted to the<br>reci=
pient.&nbsp; Do I have it right so far?<br><br>When the recipient receives =
the SRTP packet, it proceeds<br>to decrypt it.&nbsp; RFC 3711 says that the=
 receipient shall<br>first determine which cryptographic context is to be<b=
r>used.&nbsp; As before, the cryptographic context is:<br><br>{SSRC, destin=
ation network address, destination port}<br><br>But here's where I have a d=
oubt: I presume that the<br>destination network address and destination por=
t are<br>retrieved from the IP header (i.e., they correspond to<br>the rece=
iving host IP address and receiving host port -- IP-B<br>and PORT-B, respec=
tively.)&nbsp; And the SSRC is obtained<br>from the SRTP header (is that ri=
ght?)&nbsp; So, the cryptographic <br>context for the recipient is the same=
 as that of the <br>sender, namely:<br><br>&nbsp;&nbsp; {0x2ab6, IP-B, PORT=
-B}<br><br>Am I correct?&nbsp; Can someone please confirm
 this.<br>Assuming this is so, then when the recipient prepares to<br>send =
the first SRTP packet to its peer (IP-A, PORT-A),<br>it will create a new c=
ryptographic context by deriving a<br>SSRC (0x67af) and using IP-A, PORT-A =
in the tuple:<br><br>&nbsp;&nbsp; {0x67af, IP-A, PORT-A}<br><br>Similarly, =
when the peer receives the SRTP packet, it will<br>create a new cryptograph=
ic context consisting of the same<br>tuple.<br><br>So for each participant,=
 there are two cryptographic contexts:<br>one to send and one to receive.&n=
bsp; Am I correct?&nbsp; I will<br>appreciate if someone can confirm this o=
r help me understand<br>where I am in error.<br><br>Thank you.<br></td></tr=
></table><br>=0A=0A      
--0-761572944-1245074592=:58986--


From hoene@uni-tuebingen.de  Tue Jun 16 02:09:12 2009
Return-Path: <hoene@uni-tuebingen.de>
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 68F453A69B4; Tue, 16 Jun 2009 02:09:12 -0700 (PDT)
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_DE=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 HkTzrhl+6sDB; Tue, 16 Jun 2009 02:09:11 -0700 (PDT)
Received: from mx05.uni-tuebingen.de (mx05.uni-tuebingen.de [134.2.3.4]) by core3.amsl.com (Postfix) with ESMTP id 539573A69E1; Tue, 16 Jun 2009 02:09:11 -0700 (PDT)
Received: from hoeneLenovoT60 (isc-router6.urz.tu-dresden.de [141.30.3.115]) (authenticated bits=0) by mx05.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id n5G98g8d023646 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 16 Jun 2009 11:08:48 +0200
From: "Christian Hoene" <hoene@uni-tuebingen.de>
To: <avt@ietf.org>, <codec@ietf.org>
Date: Tue, 16 Jun 2009 11:08:40 +0200
Message-ID: <00fc01c9ee62$0e1fa390$2a5eeab0$@de>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcnuXwUA0d2/AKpzTI+fH2V/Y9HOpgAATGbQ
Content-Language: de
X-AntiVirus-Spam-Check: clean (checked by Avira MailGate: version: 3.0.0-4; spam filter version: 3.0.0/2.0; host: mx05)
X-AntiVirus: checked by Avira MailGate (version: 3.0.0-4; AVE: 8.2.0.187; VDF: 7.1.4.97; host: mx05); id=16854-wx6tmP
Subject: [AVT] FW: New Version Notification for draft-hoene-avt-rtp-sbc-03
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jun 2009 09:09:12 -0000

Dear all,

we have uploaded a new version of the RTP payload format for the =
Bluetooth SBC audio codec. SBC support mono and stereo audio coding =
supporting variable frame- and bit rates and having a very low =
complexity. It is part of the open-source BlueZ protocol stack for =
supporting Bluetooth device in Linux. To the best of our knowledge, its =
IPRs will expire in one year and then its usage will be license-free =
even for non-Bluetooth systems.=20

Having these features, the SBC is can be considered as a candidate for =
the Internet Wideband Audio Codecs working group (CODEC BOF). While its =
audio quality does not reach the efficiency of CELT, its much complexity =
is lower.

Best regards,

 Christian Hoene

-----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]=20
Sent: Tuesday, June 16, 2009 10:47 AM
To: hoene@uni-tuebingen.de
Cc: frans.de.bont@philips.com
Subject: New Version Notification for draft-hoene-avt-rtp-sbc-03=20


A new version of I-D, draft-hoene-avt-rtp-sbc-03.txt has been =
successfuly submitted by Christian Hoene and posted to the IETF =
repository.

Filename:	 draft-hoene-avt-rtp-sbc
Revision:	 03
Title:		 RTP Payload Format for Bluetooth's SBC audio codec
Creation_date:	 2009-06-15
WG ID:		 Independent Submission
Number_of_pages: 23

Abstract:
This document specifies a Real-time Transport Protocol (RTP) payload=20
format to be used for the low complexity subband codec (SBC), which=20
is the mandatory audio codec of the Advanced Audio Distribution=20
Profile (A2DP) Specification written by the Bluetooth(r) Special=20
Interest Group (SIG). The payload format is designed to be able to=20
interoperate with existing Bluetooth A2DP devices, to provide high=20
streaming audio quality, interactive audio transmission over the=20
internet, and ultra-low delay coding for jam sessions on the=20
internet. This document contains also a media type registration which=20
specifies the use of the RTP payload format.
                                                                         =
        =20


The IETF Secretariat.



From web-usrn@ISI.EDU  Tue Jun 16 04:58:37 2009
Return-Path: <web-usrn@ISI.EDU>
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 49A353A6897 for <avt@core3.amsl.com>; Tue, 16 Jun 2009 04:58:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.312
X-Spam-Level: 
X-Spam-Status: No, score=-17.312 tagged_above=-999 required=5 tests=[AWL=0.287, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
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 3j8-cfI+SkgZ for <avt@core3.amsl.com>; Tue, 16 Jun 2009 04:58:36 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 474D93A6A87 for <avt@ietf.org>; Tue, 16 Jun 2009 04:58:36 -0700 (PDT)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n5GBv2WO024666 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 16 Jun 2009 04:57:03 -0700 (PDT)
Received: (from web-usrn@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id n5GBuv6K024657; Tue, 16 Jun 2009 04:56:57 -0700 (PDT)
Date: Tue, 16 Jun 2009 04:56:57 -0700 (PDT)
Message-Id: <200906161156.n5GBuv6K024657@boreas.isi.edu>
To: gunnar.hellstrom@omnitor.se, paulej@packetizer.com, rjsparks@nostrum.com,  fluffy@cisco.com, even.roni@huawei.com, tom.taylor@rogers.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: web-usrn@boreas.isi.edu
Cc: gunnar.hellstrom@omnitor.se, avt@ietf.org, rfc-editor@rfc-editor.org
Subject: [AVT] [Technical Errata Reported] RFC4103 (1793)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jun 2009 11:58:37 -0000

The following errata report has been submitted for RFC4103,
"RTP Payload for Text Conversation".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=4103&eid=1793

--------------------------------------
Type: Technical
Reported by: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>

Section: 7.1

Original Text
-------------
The value of the "R2 block length" would be set to zero in order to represent the empty T140block.

  0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |V=2|P|X| CC=0  |M|  "RED" PT   |   sequence number of primary  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               timestamp of primary encoding "P"               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           synchronization source (SSRC) identifier            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |1|   T140 PT   |  timestamp offset of "R2" | "R2" block length |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |1|   T140 PT   |  timestamp offset of "R1" | "R1" block length |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |0|   T140 PT   | "R1" T.140 encoded redundant data             |
   +-+-+-+-+-+-+-+-+                               +---------------+
   |                                               |               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+         +-+-+-+
   |              "P" T.140 encoded primary data             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


Corrected Text
--------------
The value of the "R1 block length" would be set to zero in order to represent the empty T140block.

  0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |V=2|P|X| CC=0  |M|  "RED" PT   |   sequence number of primary  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               timestamp of primary encoding "P"               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           synchronization source (SSRC) identifier            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |1|   T140 PT   |  timestamp offset of "R2" | "R2" block length |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |1|   T140 PT   |  timestamp offset of "R1" | "R1" block length |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |0|   T140 PT   | "R2" T.140 encoded redundant data             |
   +-+-+-+-+-+-+-+-+                               +---------------+
   |                                               |               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+         +-+-+-+
   |              "P" T.140 encoded primary data             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


Notes
-----


Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC4103 (draft-ietf-avt-rfc2793bis-09)
--------------------------------------
Title               : RTP Payload for Text Conversation
Publication Date    : June 2005
Author(s)           : G. Hellstrom, P. Jones
Category            : PROPOSED STANDARD
Source              : Audio/Video Transport
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG

From Berlizova@spiritDSP.com  Tue Jun 16 07:29:06 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 85E4A3A69C4 for <avt@core3.amsl.com>; Tue, 16 Jun 2009 07:29:06 -0700 (PDT)
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 r0aAHowRtVLM for <avt@core3.amsl.com>; Tue, 16 Jun 2009 07:29:05 -0700 (PDT)
Received: from mail3.spiritcorp.com (mail3.spiritcorp.com [85.13.194.167]) by core3.amsl.com (Postfix) with ESMTP id 7FD3F3A6D79 for <avt@ietf.org>; Tue, 16 Jun 2009 07:28:38 -0700 (PDT)
Received: from mail-srv.spiritcorp.com (mail-srv.spiritcorp.com [192.168.125.3]) by mail3.spiritcorp.com (8.13.8/8.14.3) with SMTP id n5GEReAx037279 for <avt@ietf.org>; Tue, 16 Jun 2009 18:27:40 +0400 (MSD) (envelope-from Berlizova@spiritDSP.com)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 16 Jun 2009 18:27:34 +0400
Message-ID: <AA5A65FC22B6F145830AC0EAC7586A6C04C35B60@mail-srv.spiritcorp.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RE: [AVT] WGLC on draft-ietf-avt-rtp-ipmr-04
Thread-Index: AcnoUUm6Dh61+ZypQ1KUP8V2afOg3gAAEopwAVaetwAAOI/AAA==
From: "Elena Berlizova" <Berlizova@spiritDSP.com>
To: <avt@ietf.org>
X-Scanned-By: MIMEDefang 2.64 on 192.168.125.15
Subject: Re: [AVT] WGLC on draft-ietf-avt-rtp-ipmr-04
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jun 2009 14:29:06 -0000

-----Original Message-----
From: Elena Berlizova=20
Sent: Monday, June 15, 2009 3:33 PM
To: 'avt-bounces@ietf.org'
Cc: 'Tom Taylor'; 'Roni Even'; Sergey Ikonin
Subject: RE: [AVT] WGLC on draft-ietf-avt-rtp-ipmr-04

Hi all,

Addressing Colin's comments:=20

The payload header includes flags (the "D" and "A" bits) to signal if =20
DTX is allowed, and if the payload format is byte aligned. This is =20
unusual. Previous payload formats generally signal such parameters out-=20
of-band, for example using an SDP offer/answer exchange. What's the =20
rationale for this design, and is there a reason why out-of-band =20
parameters cannot be used?

	[SI]-> When we developed payload format we tend to maximize
flexibility of codec usage in real-time to allow rapid channel
adaptation. Because of that we put all codec setting in-band to allow
quick changing of it without re-negotiation. Now we think these two
can be placed out-of-band. But some our customers already deployed
this format and we need to keep interoperability with them.

The A bit in the payload header signals whether a byte-aligned mode is =20
to be used. There doesn't seem to be any specification of how this =20
differs from the non-byte-aligned mode.


	[SI]-> In sec 4.2 we have example of payload format in which the
A=3D1. 	In this example all speech frames are padded with zero bits for
byte 	alignment. This is the difference from non-byte-aligned mode.


Section 3.5 indicates that the decoder "can calculate the frame size =20
by its content" and notes that "there is a special service function =20
that returns frame size without total decoding which may be used for =20
this purpose". A function tied to a particular codec implementation is =20
appropriate for a vendor codec, but not for a payload format that is =20
to be registered in the standards tree. The draft needs to document =20
how to determine the payload length. (This information might be added =20
to the table on page 6).


	[SI]-> We can add some table to indicate frame size depending of
first 	bits and codec settings. But we afraid that table will be big
enough 	and not clear for usage. Another option which we can do - to add
some 	function in c-code or pseudo-code that return frame size
depending of 	frame content and codec settings.
=09

Yours sincerely
Elena Berlizova



-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Colin Perkins
Sent: Monday, June 08, 2009 7:53 PM
To: Roni Even
Cc: avt@ietf.org; 'Tom Taylor'
Subject: Re: [AVT] WGLC on draft-ietf-avt-rtp-ipmr-04

On 26 May 2009, at 08:35, Roni Even wrote:
> I would like to start a WGLC on
http://tools.ietf.org/html/draft-ietf-avt-rtp-ipmr-04=20
>  .
>
> This is the RTP Payload Format for IP-MR Speech Codec.
>
> There was some comments on the mailing list about this work and they =20
> were addressed in the 04 draft.
>
> We will start a 3 weeks working group last call.
> Please review the draft and send comments till June 16th

I have several comments on this draft:

The payload header includes flags (the "D" and "A" bits) to signal if =20
DTX is allowed, and if the payload format is byte aligned. This is =20
unusual. Previous payload formats generally signal such parameters out-=20
of-band, for example using an SDP offer/answer exchange. What's the =20
rationale for this design, and is there a reason why out-of-band =20
parameters cannot be used?

The A bit in the payload header signals whether a byte-aligned mode is =20
to be used. There doesn't seem to be any specification of how this =20
differs from the non-byte-aligned mode.

Section 3.5 indicates that the decoder "can calculate the frame size =20
by its content" and notes that "there is a special service function =20
that returns frame size without total decoding which may be used for =20
this purpose". A function tied to a particular codec implementation is =20
appropriate for a vendor codec, but not for a payload format that is =20
to be registered in the standards tree. The draft needs to document =20
how to determine the payload length. (this information might be added =20
to the table on page 6).

Page 8 includes a table listing the amount of redundancy that might be =20
added. This is listed as being class A, B, C, D, E, or F, but no =20
details are provided on what each means. If this is to be a standard =20
media type, more details must be provided, to allow independent =20
implementation of the payload format.

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



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

From root@core3.amsl.com  Tue Jun 16 08: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 5B37B28C188; Tue, 16 Jun 2009 08:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090616154501.5B37B28C188@core3.amsl.com>
Date: Tue, 16 Jun 2009 08:45:01 -0700 (PDT)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-rapid-acquisition-for-rtp-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: Tue, 16 Jun 2009 15: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           : Unicast-Based Rapid Acquisition of Multicast RTP Sessions
	Author(s)       : B. Steeg, et al.
	Filename        : draft-ietf-avt-rapid-acquisition-for-rtp-01.txt
	Pages           : 41
	Date            : 2009-06-16

When an RTP receiver joins a primary multicast session, it may need
to acquire and parse certain Reference Information before it can
process any data sent in the multicast session.  Depending on the
join time, length of the Reference Information repetition interval,
size of the Reference Information as well as the application and
transport properties, the time lag before an RTP receiver can
usefully consume the multicast data, which we refer to as the
Acquisition Delay, varies and may be large.  This is an undesirable
phenomenon for receivers that frequently switch among different
multicast sessions, such as video broadcasts.

In this document, we describe a method using the existing RTP and
RTCP protocol machinery that reduces the acquisition delay.  In this
method, an auxiliary unicast RTP session carrying the Reference
Information to the receiver precedes/accompanies the primary
multicast stream.  This unicast RTP flow may be transmitted at a
faster than natural rate to further accelerate the acquisition.  The
motivating use case for this capability is multicast applications
that carry real-time compressed audio and video.  However, the
proposed method can also be used in other types of multicast
applications where the acquisition delay is long enough to be a
problem.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rapid-acquisition-for-rtp-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-rapid-acquisition-for-rtp-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From versteb@cisco.com  Tue Jun 16 08:57:04 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 5D15D3A6DA3 for <avt@core3.amsl.com>; Tue, 16 Jun 2009 08:57:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.715
X-Spam-Level: 
X-Spam-Status: No, score=-6.715 tagged_above=-999 required=5 tests=[AWL=-0.117, 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 nnZPKSUaFXRd for <avt@core3.amsl.com>; Tue, 16 Jun 2009 08:57:03 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 8F9FA3A6804 for <avt@ietf.org>; Tue, 16 Jun 2009 08:57:03 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,229,1243814400";  d="scan'208,217";a="325080065"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 16 Jun 2009 15:57:08 +0000
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n5GFv8q1021869 for <avt@ietf.org>; Tue, 16 Jun 2009 08:57:08 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by sj-core-4.cisco.com (8.13.8/8.13.8) with ESMTP id n5GFv4nQ006348 for <avt@ietf.org>; Tue, 16 Jun 2009 15:57:08 GMT
Received: from xmb-rtp-21d.amer.cisco.com ([64.102.31.116]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 16 Jun 2009 11:57:07 -0400
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_01C9EE9B.19A7FD61"
Date: Tue, 16 Jun 2009 11:57:07 -0400
Message-ID: <81B9B88E2F9D574AA5328A85547CDE91016FF154@xmb-rtp-21d.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-01 of "Rapid Acquisition of RTP Sessions" has been posted
Thread-Index: Acnumxm3oQk3JKajR0CETD1yRPzWlg==
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 16 Jun 2009 15:57:07.0661 (UTC) FILETIME=[19C767D0:01C9EE9B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3038; t=1245167828; x=1246031828; c=relaxed/simple; s=sjdkim3002; 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:=20draft-01=20of=20=22Rapid=20Acquisition=20of=20R TP=20Sessions=22=20has=20been=20posted |Sender:=20; bh=PkzwJ/4q1YWjrvivwLoEwRtI6roByEv/jMfK/9JZZPc=; b=ShItXlJVJciaVfvR2iZ1IBPZYfrcJzFg3HJnWcHENmheLwbjF5I12C/GoP gclDRpeFE4biDMq7JVCfBNQgOjwdkf8F1fWzAzqRMLuVo6trDkvRiht7lfj3 dE2CnGOZHN;
Authentication-Results: sj-dkim-3; header.From=versteb@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Subject: [AVT] draft-01 of "Rapid Acquisition of RTP Sessions" has been posted
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jun 2009 15:57:04 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9EE9B.19A7FD61
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Draft 01 of Rapid Acquisition of RTP Sessions (RAMS)" has been posted to
http://www.ietf.org/internet-drafts/draft-ietf-avt-rapid-acquisition-for
-rtp-01.txt
=20
We have updated the document to include -=20
=20
1- The detailed feedback from San Francisco, which was posted to the
list as diffs a few weeks ago.
2- Two new sections for NAT traversal, including a general-purpose RTP
method for signaling port numbers using a construct called "PUBPORTS" .
This is in section 9 and section 10. The authors are particularly
interested in feedback on these sections of the document.
3- A clean up of the SDP section
=20
=20
=20
Bill VerSteeg

------_=_NextPart_001_01C9EE9B.19A7FD61
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16809" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D308514015-16062009><FONT face=3DArial size=3D2>Draft =
01 of Rapid=20
Acquisition of RTP Sessions (RAMS)" has been posted to <A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-avt-rapid-acquisit=
ion-for-rtp-01.txt">http://www.ietf.org/internet-drafts/draft-ietf-avt-ra=
pid-acquisition-for-rtp-01.txt</A></FONT></SPAN></DIV>
<DIV><SPAN class=3D308514015-16062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D308514015-16062009><FONT face=3DArial size=3D2>We =
have updated the=20
document to include - </FONT></SPAN></DIV>
<DIV><SPAN class=3D308514015-16062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D308514015-16062009><FONT face=3DArial size=3D2>1- The =
detailed=20
feedback from San Francisco, which was posted to the list as diffs a few =
weeks=20
ago.</FONT></SPAN></DIV>
<DIV><SPAN class=3D308514015-16062009><FONT face=3DArial =
size=3D2>2-&nbsp;Two&nbsp;new=20
sections for NAT traversal, including&nbsp;a general-purpose RTP method =
for=20
signaling port numbers using a construct called&nbsp;"PUBPORTS" . This =
is in=20
section 9 and section 10.&nbsp;The authors&nbsp;are particularly =
interested in=20
feedback on these sections of the document.</FONT></SPAN></DIV>
<DIV><SPAN class=3D308514015-16062009><FONT face=3DArial size=3D2>3- A =
clean up of the=20
SDP section</FONT></SPAN></DIV>
<DIV><SPAN class=3D308514015-16062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D308514015-16062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D308514015-16062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D308514015-16062009><FONT face=3DArial size=3D2>Bill=20
VerSteeg</FONT></SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C9EE9B.19A7FD61--

From md.1@newtbt.com  Tue Jun 16 09:42:33 2009
Return-Path: <md.1@newtbt.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 491193A6C5F for <avt@core3.amsl.com>; Tue, 16 Jun 2009 09:42:33 -0700 (PDT)
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 ZEgaTOuG1Gkh for <avt@core3.amsl.com>; Tue, 16 Jun 2009 09:42:29 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 666553A6B58 for <avt@ietf.org>; Tue, 16 Jun 2009 09:42:29 -0700 (PDT)
Received: from TBT-Laptop.newtbt.com (ppp-69-237-184-11.dsl.sndg02.pacbell.net [69.237.184.11]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1MGbjS2vGp-000cit; Tue, 16 Jun 2009 12:42:01 -0400
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 16 Jun 2009 09:37:13 -0700
To: avt@ietf.org
From: Michael A Dolan <md.1@newtbt.com>
In-Reply-To: <4A323DC5.5020004@hhi.fraunhofer.de>
References: <20090309171502.518513A6359@core3.amsl.com> <4A6ACB13-0CBB-4DA7-84AD-28CDE56DB4C3@csperkins.org> <0MKpCa-1LoLs525qX-000cvA@mrelay.perfora.net> <49D1C793.9050409@hhi.fraunhofer.de> <0MKp8S-1Lof8c1LTC-000fjs@mrelay.perfora.net> <49D4AE9D.8060905@hhi.fraunhofer.de> <0MKpCa-1MEnZO1ysE-000d6S@mrelay.perfora.net> <4A323DC5.5020004@hhi.fraunhofer.de>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_498927890==.ALT"
Message-Id: <0MKpCa-1MGbjS2vGp-000cit@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX1/jH5CBIQg8VsO1+KBB2F+dn8F2bfU/676q4vm B4K9iWESAJ0M7jLyw++Wpuoi1A3qS7ly+dN1guR0AXTmBMIzhb TEBodSOIVx48WMNjEXi5Q==
Subject: Re: [AVT] Fwd: I-D Action:draft-perkins-avt-rapid-rtp-sync-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: Tue, 16 Jun 2009 16:42:33 -0000

--=====================_498927890==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

Thomas and all-

I decided to reply to the earlier email/draft so we have the thread 
context since the comments apply to both that draft and the one 
posted the other day. Sorry for any confusion.

I think you might misunderstand my comment about the timebase.  I am 
not proposing you force applications to use any specific timebase.  I 
am proposing that senders and receivers have to agree (implicitly 
since it cannot be signaled) what timebase is being used in specific 
NTPv4 terms.  "wallclock" is ambiguous, but more importantly will not 
result in the improved sync time you desire without such an out of 
band agreement.

Regarding the relationship to the media stream access points, again 
there may be a misunderstanding.  I did not propose faster RTCP SR 
records be forbidden, or even discouraged.  I am proposing clarifying 
text explaining the important sync-related relationship that would 
change one's interpretation of the tables and desired RTCP SR 
frequency.  I believe the tables are misleading where they imply 
actual sync times remotely near 0.04 seconds.

Since I am only proposing (albeit important in my opinion) clarifying 
material and am not actually opposing what is there now; and I am 
willing to craft specific text changes (your option); I am not sure I 
understand the offhand rejection of the comments.

Based on offline emails with you and the chair, I understood this 
work to be THE authority on rapid sync of RTP sessions.  Maybe I 
misunderstood and its scope is more narrow than that. If that's the 
case, then perhaps we can narrow the scope of the work and I'll 
author another draft on RTP sync. But I think the proposed changes 
are relatively minor in the grand scheme of things and hope you will 
consider addressing them in this draft.

Regards,

         Mike

At 01:36 PM 6/12/2009 +0200, Thomas Schierl wrote:
>Hi Michael,
>
>I guess your comments are related to 
>draft-ietf-avt-rapid-rtp-sync-02.txt. Please find my comments in line.
>
>Thomas
>
>Michael A Dolan wrote:
>>Thomas and all-
>>
>>Continuing this in the context of yesterday's WG draft -02:
>>
>>1. The draft still uses "wallclock".  I believe what's important is 
>>that the NTP reference clock must have the same reference_ID value 
>>as the clock used in the RTCP SR records. It's not important that 
>>it be "wallclock" (or more precisely, one of the values defined in 
>>NTPv4).  It can be PPS or something else. The draft does mention 
>>that a common clock should be used.  The problem I see is that the 
>>language is imprecise WRT NTPv4 terminology and implies a vague 
>>subset of timebases by using the term, "wallclock". Further, when 
>>the hdr ext for NTP is not used, it should be stated that the NTP 
>>timebase reference_ID must be agreed to out of band between the 
>>senders and receivers.
>
>See my original comments attached to your message. I think we do not 
>want to make any additional requirements on the clock to be used for 
>generating the wallclock, i.e. we will keep the definitions in RFC 
>3550 for backward compatibility reasons.
>
>>
>>2. Sync can only occur when the receiver has not only NTP and RTCP 
>>SR packets, but also a point in every RTP session where there is an 
>>"access point" for that media stream.  Since these access points 
>>are customarily considerably further apart than 0.04 seconds, the 
>>tables are a bit misleading on the practical sync time and 
>>recommended RTCP SR emission frequency.  It should be noted around 
>>all the tables that there is no benefit to sending the RTCP SR 
>>record more often than the media access point frequency, especially 
>>in combination with the next comment below.
>
>Sure, there is typically a need for a random access point to start 
>decoding. So on the first glance it makes sense to send SRs not with 
>a higher frequency than random access points. But there may be a 
>benefit to send SRs more frequently, e.g., to estimate clock skews.
>
>>
>>3. It should be recommended that RTCP SR packets be sent near, and 
>>immediately following, media access points (subject to the 5% 
>>boundary). Doing so will greatly improve the sync time rather than 
>>relying on more frequent, and/or randomly timed, RTCP SR packets.
>
>Generally, it should not be a problem to slightly delay RTCP packets 
>in order to align with media random access points, but this would 
>need further analysis to document the acceptable bounds. I guess 
>this would require more time and would further delay the intended 
>solution for layered codecs. In order to not further delay the 
>solution in this draft, this could become a topic of another draft.
>
>>
>>Comment #1 becomes even more important the faster you want to 
>>sync.  If the RTP sessions are using GPS and the NTP source is 
>>using UTC (both "wallclock"), there will be errors measured in 
>>seconds.  This disparity is less likely when the hdr ext is used, 
>>of course. But in the general case, this language needs tightening 
>>up to remove the clock errors.
>>
>>Comments 2 & 3, although true in all scenarios, become more 
>>relevant in SSM with late joiners.
>>
>>I hope the above comments are clearer than my attempts below.  I'm 
>>happy to suggest specific edits to the draft if that will help.
>>
>>Regards,
>>
>>         Mike
>>
>>At 02:25 PM 4/2/2009 +0200, 
>><mailto:Thomas.Schierl@hhi.fraunhofer.de>Thomas.Schierl@hhi.fraunhofer.de 
>>wrote:
>>>Hi Michael,
>>>
>>>What I can see from the ATSC M/H Transport spec is that there are 
>>>requirements on encoder and decoder clock precisions, which for 
>>>sure give a complete different environment than assumed by RFC3550 
>>>with respect to the clock precision. If we could assure such 
>>>clocks for all devices which may potentially encode and stream 
>>>layered media via multi session transmission, the problem would 
>>>have been solved anyway. But that is not the case, as I tried to 
>>>show by pointing to some of the relevant discussions on the mailing list.
>>>
>>>About your second point: RTP does not require NTP to be used as 
>>>wallclock. In RTP, there is much more freedom in selecting the 
>>>source for this clock. RTP uses the NTP timestamp format just for 
>>>indicating the wallclock in the RTCP sender reports. Furthermore 
>>>draft-perkins-avt-rapid-rtp-sync-03 does only require to use the 
>>>same wallclock as used for the SRs also for the wallclock 
>>>timestamps in the header extensions.
>>>
>>>Another interesting point is that the ATSC Transport spec is not 
>>>mentioning SVC while mentioning AVC and AAC. If looking at the 
>>>ATSC Video Systems spec. 
>>>(<http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-136r7-A153-Part-7-Video-System.pdf> 
>>>S4-136r7-A153-Part-7-Video-System), there is a solution which 
>>>requires RTP timestamp synchronization for "SVC Transport in Two 
>>>RTP Sessions". This for sure solves the clock skew problem, but as 
>>>discussed in AVT, this is not a general solution and has different 
>>>implications if applied to all use cases of RTP multi session 
>>>transmission as, e.g. conversational services. Therefore we now 
>>>have a solution which seems to be agreeable by the group, which 
>>>solves the problem and is more in line with RFC 3550, i.e. using 
>>>the wallclock for the data alignment between the session.
>>>
>>>Best regards,
>>>Thomas
>>>
>>>
>>>Michael A Dolan wrote:
>>>>Hi Thomas-
>>>>
>>>>Thanks.  Yes, I am familiar with the discussion.
>>>>
>>>>I'm not necessarily pushing the ATSC solution, but offering some 
>>>>points to consider, which apply equally to the problem at hand here, I think.
>>>>
>>>>Also, it is important to note some more things about the ATSC text:
>>>>
>>>>1. The language in the specification very carefully recommends 
>>>>the clock precision without requiring it.  It is expected to work 
>>>>over routers with jitter and delays and with media components 
>>>>from outside the broadcast facility. The difference is that the 
>>>>client is expected to be able to perform tight sync when the 
>>>>servers are able to provide the recommended timing model 
>>>>(encoding one hop away, etc).  It gracefully degrades to 
>>>>"Internet" timing model quality.
>>>>
>>>>2. The clock, although "NTP" syntax, is not time of day (e.g. 
>>>>reference_ID= "GPS"), but "PPS", thus allowing the components to 
>>>>be encoded and decoded without concern for end-to-end delivery 
>>>>delay.  This only works when NTP is explicitly signaled as part 
>>>>of the encoding and both components share a clock (same or 
>>>>closely coupled encoders). So it will not work in the general 
>>>>case.  But there are many systems where it will and perhaps 
>>>>consideration should be given to permitting non-"wall clock" timebases.
>>>>
>>>>The NTP hdr ext here is an encoding optimization that indeed has 
>>>>some other good properties.  Although the draft ties the NTP 
>>>>timestamp back to the RTCP SR records, the timebase is not 
>>>>explicitly defined (which is also true of RTCP SR).  Some 
>>>>reference_ID value must be assumed and there is enough delta 
>>>>between, for example, GPS and UTC, timebases to cause things to 
>>>>break if the entire system is not implicitly assumed to be only 
>>>>one timebase. For example, without an explicit reference_ID, how 
>>>>could one use other timebases defined in NTPv4?  This is a 
>>>>broader issue than the hdr ext syntax, but since we're discussing 
>>>>NTP, I thought I'd bring it up.
>>>>
>>>>I think the above and the other points below are relevant here 
>>>>and not inconsistent with the RTCP SR methods. The fact that the 
>>>>ATSC design *can* be more precise is not alone cause to discard 
>>>>the techniques developed there.
>>>>
>>>>Regards,
>>>>
>>>>          Mike
>>>>
>>>>At 09:34 AM 3/31/2009 +0200, 
>>>><mailto:Thomas.Schierl@hhi.fraunhofer.de>Thomas.Schierl@hhi.fraunhofer.de 
>>>>wrote:
>>>>>Dear Michael,
>>>>>
>>>>>Thanks for the comments and the reference to the ATSC M/H.
>>>>>
>>>>>I guess, what we are looking for in AVT is a solution which also 
>>>>>works for encoders having non-perfect clocks. There was a long 
>>>>>discussion on the list, here are two pointers:
>>>>>
>>>>><http://www.ietf.org/mail-archive/web/avt/current/msg09144.html>http://www.ietf.org/mail-archive/web/avt/current/msg09144.html
>>>>>http://www.ietf.org/mail-archive/web/avt/current/msg10491.html
>>>>>
>>>>>ATSC surely can assume to have a perfect clock in the NTP 
>>>>>streams, which will not be the case on PC systems that may be 
>>>>>used as an encoder for multi session transmission of a layered 
>>>>>codec. This is one major problem we intended to solve with the 
>>>>>header extension while keeping the whole approach as close as 
>>>>>possible in line with the existing RTCP SR method.
>>>>>
>>>>>
>>>>>Best regards,
>>>>>Thomas
>>>>>
>>>>>
>>>>>
>>>>>______________________________________________
>>>>>Thomas Schierl, Dipl.-Ing.
>>>>>Fraunhofer HHI
>>>>>Senior Research Engineer
>>>>>Image Processing Dept. / Multimedia Transport
>>>>>Einsteinufer 37, 10587 Berlin, Germany
>>>>>PHONE: +49 30 31002 227 , FAX: +49 30 392 7200
>>>>>WEB: <http://ip.hhi.de/>http://ip.hhi.de , SKYPE: thomas.schierl
>>>>>EMAIL: 
>>>>><mailto:thomas.schierl@hhi.fraunhofer.de>thomas.schierl@hhi.fraunhofer.de
>>>>>
>>>>>
>>>>>
>>>>>Michael A Dolan wrote:
>>>>>>Those interested in this topic may also find this interesting:
>>>>>>
>>>>>><http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-132r13-A153-Part-3-Transport.pdf>http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-132r13-A153-Part-3-Transport.pdf 
>>>>>>
>>>>>>
>>>>>>Section 10.3.
>>>>>>
>>>>>>Some differences are:
>>>>>>
>>>>>>1. There is one NTP packet stream per service, rather than the 
>>>>>>encoding optimization in the hdr ext;
>>>>>>2. RTCP SR records are emitted "near" video random access 
>>>>>>points, rather than on a prescribed time schedule; and
>>>>>>3. The above works in multicast-only, UDLR networks (e.g. 
>>>>>>television broadcast), rather than requiring a 2-way link.
>>>>>>
>>>>>>#2 is interesting since in order to begin a *synchronized* 
>>>>>>decode (video + audio properly correlated), a client must have acquired all of:
>>>>>>a. NTP
>>>>>>b. RTCP SR for each component
>>>>>>c. video reference frame and decoding metadata (i.e. a random 
>>>>>>access point)
>>>>>>d. audio frame
>>>>>>
>>>>>>So, the relative timing of the RTCP SR records to the RTP 
>>>>>>stream content is perhaps more important than the emission 
>>>>>>period.  Having the RTCP SR records arrive faster than the 
>>>>>>video reference frames doesn't help of course.  And even if 
>>>>>>they are "fast enough", having them arrive out of sync with the 
>>>>>>reference frames delays the service acquisition by half the period on average.
>>>>>>
>>>>>>Bandwidth utilization (how many bits to devote to RTCP and NTP) 
>>>>>>can arguably be more efficiently managed by the server in most 
>>>>>>cases, not individual client requests for faster RTCP SR 
>>>>>>packets. And, the client would have no knowledge of the 
>>>>>>intended (video) reference frame periods being used by the 
>>>>>>server, so it would not, in general, know what to ask for.
>>>>>>
>>>>>>In practice, won't a server that wants to enable faster 
>>>>>>acquisition and sync do things like the above?  I'm concerned 
>>>>>>that detailed requests from clients beyond "please use more 
>>>>>>bandwidth and enable fast sync" won't be as valuable as they 
>>>>>>seem since in the general case the client doesn't know what to ask for exactly.
>>>>>>
>>>>>>FYI, the above ATSC document is in a "candidate" state where 
>>>>>>public comments are solicited.  Independent of this thread, if 
>>>>>>anyone has comments on it, I could convey them back to the ATSC.
>>>>>>
>>>>>>Regards,
>>>>>>
>>>>>>         Mike
>>>>>>
>>>>>>At 07:43 PM 3/9/2009 +0000, Colin Perkins wrote:
>>>>>>>The changes in this version are primarily editorial; we're aware that
>>>>>>>not all the open issues have been addressed yet. Any further comments
>>>>>>>are welcomed.
>>>>>>>
>>>>>>>Chairs: we'd like this to be considered as an AVT working group
>>>>>>>draft, as indicated privately.
>>>>>>>
>>>>>>>Cheers,
>>>>>>>Colin
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>Begin forwarded message:
>>>>>>>>From: <mailto:Internet-Drafts@ietf.org>Internet-Drafts@ietf.org
>>>>>>>>Date: 9 March 2009 17:15:02 GMT
>>>>>>>>To: <mailto:i-d-announce@ietf.org>i-d-announce@ietf.org
>>>>>>>>Subject: I-D Action:draft-perkins-avt-rapid-rtp-sync-03.txt
>>>>>>>>Reply-To: <mailto:internet-drafts@ietf.org>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-03.txt
>>>>>>>>         Pages           : 17
>>>>>>>>         Date            : 2009-03-09
>>>>>>>>
>>>>>>>>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>http://www.ietf.org/internet-drafts/draft-perkins-avt-rapid-rtp- 
>>>>>>>>sync-03.txt
>>>>>>>>
>>>>>>>>Internet-Drafts are also available by anonymous FTP at:
>>>>>>>><ftp://ftp.ietf.org/internet-drafts/>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.
>>>>>>>>Content-Type: text/plain
>>>>>>>>Content-ID: 
>>>>>>>><mailto:2009-03-09100610.I-D@ietf.org><2009-03-09100610.I-D@ietf.org>
>>>>>>>>
>>>>>>>>_______________________________________________
>>>>>>>>I-D-Announce mailing list
>>>>>>>><mailto:I-D-Announce@ietf.org>I-D-Announce@ietf.org
>>>>>>>>https://www.ietf.org/mailman/listinfo/i-d-announce
>>>>>>>>Internet-Draft directories: 
>>>>>>>><http://www.ietf.org/shadow.html>http://www.ietf.org/shadow.html
>>>>>>>>or 
>>>>>>>><ftp://ftp.ietf.org/ietf/1shadow-sites.txt>ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>>>>>
>>>>>>>_______________________________________________
>>>>>>>Audio/Video Transport Working Group
>>>>>>><mailto:avt@ietf.org>avt@ietf.org
>>>>>>>https://www.ietf.org/mailman/listinfo/avt
>>>>>>
>>>>>>_______________________________________________
>>>>>>Audio/Video Transport Working Group
>>>>>><mailto:avt@ietf.org>avt@ietf.org
>>>>>>https://www.ietf.org/mailman/listinfo/avt
>>>>>
>>>>>---
>>>>>Visit us at
>>>>>
>>>>>Web 2.0 Expo / March 31 - April 03 / San Francisco, California / Booth 415
>>>>><http://www.web2expo.com/webexsf2009>http://www.web2expo.com/webexsf2009
>>>>>
>>>>>NAB SHOW 2009 / April 18-23 / Las Vegas, Nevada USA / South Hall 
>>>>>(Upper), Booth SU9624F
>>>>><http://www.nabshow.com/>http://www.nabshow.com/
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>_______________________________________________
>>>>Audio/Video Transport Working Group
>>>><mailto:avt@ietf.org>avt@ietf.org
>>>>
>>>>https://www.ietf.org/mailman/listinfo/avt
>>>>
>>>>
>>>
>>>
>>>----
>>>Visit us at
>>>
>>>Web 2.0 Expo / March 31 - April 03 / San Francisco, California / Booth 415
>>><http://www.web2expo.com/webexsf2009>http://www.web2expo.com/webexsf2009
>>>
>>>NAB SHOW 2009 / April 18-23 / Las Vegas, Nevada USA / South Hall 
>>>(Upper), Booth SU9624F
>>><http://www.nabshow.com/>http://www.nabshow.com/
>>
>>
>>
>>
>>
>>_______________________________________________
>>Audio/Video Transport Working Group
>><mailto:avt@ietf.org>avt@ietf.org
>>https://www.ietf.org/mailman/listinfo/avt
>>
>
>
>----
>Visit us at
>
>IEEE ICC 2009 / June 14-18 / Dresden, Germany / International Congress Center
><http://www.comsoc.org/confs/icc/2009/>http://www.comsoc.org/confs/icc/2009/
>
>Laser World of Photonics 2009 / June 15-18 / Munich, Germay / Hall 
>B1, Booth 461
><http://world-of-photonics.net/de/laser/start>http://world-of-photonics.net/de/laser/start

--=====================_498927890==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
Thomas and all-<br><br>
I decided to reply to the earlier email/draft so we have the thread
context since the comments apply to both that draft and the one posted
the other day. Sorry for any confusion.<br><br>
I think you might misunderstand my comment about the timebase.&nbsp; I am
not proposing you force applications to use any specific timebase.&nbsp;
I am proposing that senders and receivers have to agree (implicitly since
it cannot be signaled) what timebase is being used in specific NTPv4
terms.&nbsp; &quot;wallclock&quot; is ambiguous, but more importantly
will not result in the improved sync time you desire without such an out
of band agreement.<br><br>
Regarding the relationship to the media stream access points, again there
may be a misunderstanding.&nbsp; I did not propose faster RTCP SR records
be forbidden, or even discouraged.&nbsp; I am proposing clarifying text
explaining the important sync-related relationship that would change
one's interpretation of the tables and desired RTCP SR frequency.&nbsp; I
believe the tables are misleading where they imply actual sync times
remotely near 0.04 seconds.<br><br>
Since I am only proposing (albeit important in my opinion) clarifying
material and am not actually opposing what is there now; and I am willing
to craft specific text changes (your option); I am not sure I understand
the offhand rejection of the comments.<br><br>
Based on offline emails with you and the chair, I understood this work to
be THE authority on rapid sync of RTP sessions.&nbsp; Maybe I
misunderstood and its scope is more narrow than that. If that's the case,
then perhaps we can narrow the scope of the work and I'll author another
draft on RTP sync. But I think the proposed changes are relatively minor
in the grand scheme of things and hope you will consider addressing them
in this draft.<br><br>
Regards,<br><br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Mike<br>
<br>
At 01:36 PM 6/12/2009 +0200, Thomas Schierl wrote:<br>
<blockquote type=cite class=cite cite="">Hi Michael,<br><br>
I guess your comments are related to
draft-ietf-avt-rapid-rtp-sync-02.txt. Please find my comments in
line.<br><br>
Thomas<br><br>
Michael A Dolan wrote: <br>
<blockquote type=cite class=cite cite="">Thomas and all-<br><br>
Continuing this in the context of yesterday's WG draft -02:<br><br>
1. The draft still uses &quot;wallclock&quot;.&nbsp; I believe what's
important is that the NTP reference clock must have the same reference_ID
value as the clock used in the RTCP SR records. It's not important that
it be &quot;wallclock&quot; (or more precisely, one of the values defined
in NTPv4).&nbsp; It can be PPS or something else. The draft does mention
that a common clock should be used.&nbsp; The problem I see is that the
language is imprecise WRT NTPv4 terminology and implies a vague subset of
timebases by using the term, &quot;wallclock&quot;. Further, when the hdr
ext for NTP is not used, it should be stated that the NTP timebase
reference_ID must be agreed to out of band between the senders and
receivers.</blockquote><br>
See my original comments attached to your message. I think we do not want
to make any additional requirements on the clock to be used for
generating the wallclock, i.e. we will keep the definitions in RFC 3550
for backward compatibility reasons.<br><br>
<blockquote type=cite class=cite cite=""><br>
2. Sync can only occur when the receiver has not only NTP and RTCP SR
packets, but also a point in every RTP session where there is an
&quot;access point&quot; for that media stream.&nbsp; Since these access
points are customarily considerably further apart than 0.04 seconds, the
tables are a bit misleading on the practical sync time and recommended
RTCP SR emission frequency.&nbsp; It should be noted around all the
tables that there is no benefit to sending the RTCP SR record more often
than the media access point frequency, especially in combination with the
next comment below.</blockquote><br>
Sure, there is typically a need for a random access point to start
decoding. So on the first glance it makes sense to send SRs not with a
higher frequency than random access points. But there may be a benefit to
send SRs more frequently, e.g., to estimate clock skews.<br><br>
<blockquote type=cite class=cite cite=""><br>
3. It should be recommended that RTCP SR packets be sent near, and
immediately following, media access points (subject to the 5% boundary).
Doing so will greatly improve the sync time rather than relying on more
frequent, and/or randomly timed, RTCP SR packets.</blockquote><br>
Generally, it should not be a problem to slightly delay RTCP packets in
order to align with media random access points, but this would need
further analysis to document the acceptable bounds. I guess this would
require more time and would further delay the intended solution for
layered codecs. In order to not further delay the solution in this draft,
this could become a topic of another draft. <br><br>
<blockquote type=cite class=cite cite=""><br>
Comment #1 becomes even more important the faster you want to sync.&nbsp;
If the RTP sessions are using GPS and the NTP source is using UTC (both
&quot;wallclock&quot;), there will be errors measured in seconds.&nbsp;
This disparity is less likely when the hdr ext is used, of course. But in
the general case, this language needs tightening up to remove the clock
errors.<br><br>
Comments 2 &amp; 3, although true in all scenarios, become more relevant
in SSM with late joiners.<br><br>
I hope the above comments are clearer than my attempts below.&nbsp; I'm
happy to suggest specific edits to the draft if that will help.<br><br>
Regards,<br><br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Mike<br>
<br>
At 02:25 PM 4/2/2009 +0200,
<a href="mailto:Thomas.Schierl@hhi.fraunhofer.de">
Thomas.Schierl@hhi.fraunhofer.de</a> wrote:<br>
<blockquote type=cite class=cite cite="">Hi Michael,<br><br>
What I can see from the ATSC M/H Transport spec is that there are
requirements on encoder and decoder clock precisions, which for sure give
a complete different environment than assumed by RFC3550 with respect to
the clock precision. If we could assure such clocks for all devices which
may potentially encode and stream layered media via multi session
transmission, the problem would have been solved anyway. But that is not
the case, as I tried to show by pointing to some of the relevant
discussions on the mailing list.<br><br>
About your second point: RTP does not require NTP to be used as
wallclock. In RTP, there is much more freedom in selecting the source for
this clock. RTP uses the NTP timestamp format just for indicating the
wallclock in the RTCP sender reports. Furthermore
draft-perkins-avt-rapid-rtp-sync-03 does only require to use the same
wallclock as used for the SRs also for the wallclock timestamps in the
header extensions.<br><br>
Another interesting point is that the ATSC Transport spec is not
mentioning SVC while mentioning AVC and AAC. If looking at the ATSC Video
Systems spec.
(<a href="http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-136r7-A153-Part-7-Video-System.pdf">
 S4-136r7-A153-Part-7-Video-System</a>), there is a solution which
requires RTP timestamp synchronization for &quot;SVC Transport in Two RTP
Sessions&quot;. This for sure solves the clock skew problem, but as
discussed in AVT, this is not a general solution and has different
implications if applied to all use cases of RTP multi session
transmission as, e.g. conversational services. Therefore we now have a
solution which seems to be agreeable by the group, which solves the
problem and is more in line with RFC 3550, i.e. using the wallclock for
the data alignment between the session.<br><br>
Best regards,<br>
Thomas<br><br>
<br>
Michael A Dolan wrote: <br>
<blockquote type=cite class=cite cite="">Hi Thomas-<br><br>
Thanks.&nbsp; Yes, I am familiar with the discussion.<br><br>
I'm not necessarily pushing the ATSC solution, but offering some points
to consider, which apply equally to the problem at hand here, I
think.<br><br>
Also, it is important to note some more things about the ATSC
text:<br><br>
1. The language in the specification very carefully recommends the clock
precision without requiring it.&nbsp; It is expected to work over routers
with jitter and delays and with media components from outside the
broadcast facility. The difference is that the client is expected to be
able to perform tight sync when the servers are able to provide the
recommended timing model (encoding one hop away, etc).&nbsp; It
gracefully degrades to &quot;Internet&quot; timing model
quality.<br><br>
2. The clock, although &quot;NTP&quot; syntax, is not time of day (e.g.
reference_ID= &quot;GPS&quot;), but &quot;PPS&quot;, thus allowing the
components to be encoded and decoded without concern for end-to-end
delivery delay.&nbsp; This only works when NTP is explicitly signaled as
part of the encoding and both components share a clock (same or closely
coupled encoders). So it will not work in the general case.&nbsp; But
there are many systems where it will and perhaps consideration should be
given to permitting non-&quot;wall clock&quot; timebases.<br><br>
The NTP hdr ext here is an encoding optimization that indeed has some
other good properties.&nbsp; Although the draft ties the NTP timestamp
back to the RTCP SR records, the timebase is not explicitly defined
(which is also true of RTCP SR).&nbsp; Some reference_ID value must be
assumed and there is enough delta between, for example, GPS and UTC,
timebases to cause things to break if the entire system is not implicitly
assumed to be only one timebase. For example, without an explicit
reference_ID, how could one use other timebases defined in NTPv4?&nbsp;
This is a broader issue than the hdr ext syntax, but since we're
discussing NTP, I thought I'd bring it up.<br><br>
I think the above and the other points below are relevant here and not
inconsistent with the RTCP SR methods. The fact that the ATSC design
*can* be more precise is not alone cause to discard the techniques
developed there.<br><br>
Regards,<br><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mike<br><br>
At 09:34 AM 3/31/2009 +0200,
<a href="mailto:Thomas.Schierl@hhi.fraunhofer.de">
Thomas.Schierl@hhi.fraunhofer.de</a> wrote:<br>
<blockquote type=cite class=cite cite="">Dear Michael,<br><br>
Thanks for the comments and the reference to the ATSC M/H.<br><br>
I guess, what we are looking for in AVT is a solution which also works
for encoders having non-perfect clocks. There was a long discussion on
the list, here are two pointers:<br><br>
<a href="http://www.ietf.org/mail-archive/web/avt/current/msg09144.html">
http://www.ietf.org/mail-archive/web/avt/current/msg09144.html</a><br>
<a href="http://www.ietf.org/mail-archive/web/avt/current/msg10491.html" eudora="autourl">
http://www.ietf.org/mail-archive/web/avt/current/msg10491.html</a><br><br>
ATSC surely can assume to have a perfect clock in the NTP streams, which
will not be the case on PC systems that may be used as an encoder for
multi session transmission of a layered codec. This is one major problem
we intended to solve with the header extension while keeping the whole
approach as close as possible in line with the existing RTCP SR
method.<br><br>
<br>
Best regards,<br>
Thomas<br><br>
<br><br>
______________________________________________<br>
Thomas Schierl, Dipl.-Ing.<br>
Fraunhofer HHI<br>
Senior Research Engineer<br>
Image Processing Dept. / Multimedia Transport<br>
Einsteinufer 37, 10587 Berlin, Germany<br>
PHONE: +49 30 31002 227 , FAX: +49 30 392 7200<br>
WEB: <a href="http://ip.hhi.de/">http://ip.hhi.de</a> , SKYPE:
thomas.schierl<br>
EMAIL:
<a href="mailto:thomas.schierl@hhi.fraunhofer.de">
thomas.schierl@hhi.fraunhofer.de</a><br><br>
<br><br>
Michael A Dolan wrote:<br>
<blockquote type=cite class=cite cite="">Those interested in this topic
may also find this interesting:<br><br>
<a href="http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-132r13-A153-Part-3-Transport.pdf">
http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-132r13-A153-Part-3-Transport.pdf</a>
 <br><br>
Section 10.3.<br><br>
Some differences are:<br><br>
1. There is one NTP packet stream per service, rather than the encoding
optimization in the hdr ext;<br>
2. RTCP SR records are emitted &quot;near&quot; video random access
points, rather than on a prescribed time schedule; and<br>
3. The above works in multicast-only, UDLR networks (e.g. television
broadcast), rather than requiring a 2-way link.<br><br>
#2 is interesting since in order to begin a *synchronized* decode (video
+ audio properly correlated), a client must have acquired all of:<br>
a. NTP<br>
b. RTCP SR for each component<br>
c. video reference frame and decoding metadata (i.e. a random access
point)<br>
d. audio frame<br><br>
So, the relative timing of the RTCP SR records to the RTP stream content
is perhaps more important than the emission period.&nbsp; Having the RTCP
SR records arrive faster than the video reference frames doesn't help of
course.&nbsp; And even if they are &quot;fast enough&quot;, having them
arrive out of sync with the reference frames delays the service
acquisition by half the period on average.<br><br>
Bandwidth utilization (how many bits to devote to RTCP and NTP) can
arguably be more efficiently managed by the server in most cases, not
individual client requests for faster RTCP SR packets. And, the client
would have no knowledge of the intended (video) reference frame periods
being used by the server, so it would not, in general, know what to ask
for.<br><br>
In practice, won't a server that wants to enable faster acquisition and
sync do things like the above?&nbsp; I'm concerned that detailed requests
from clients beyond &quot;please use more bandwidth and enable fast
sync&quot; won't be as valuable as they seem since in the general case
the client doesn't know what to ask for exactly.<br><br>
FYI, the above ATSC document is in a &quot;candidate&quot; state where
public comments are solicited.&nbsp; Independent of this thread, if
anyone has comments on it, I could convey them back to the ATSC.<br><br>
Regards,<br><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mike<br><br>
At 07:43 PM 3/9/2009 +0000, Colin Perkins wrote:<br>
<blockquote type=cite class=cite cite="">The changes in this version are
primarily editorial; we're aware that<br>
not all the open issues have been addressed yet. Any further
comments<br>
are welcomed.<br><br>
Chairs: we'd like this to be considered as an AVT working group<br>
draft, as indicated privately.<br><br>
Cheers,<br>
Colin<br><br>
<br><br>
<br>
Begin forwarded message:<br>
<blockquote type=cite class=cite cite="">From:
<a href="mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a><br>
Date: 9 March 2009 17:15:02 GMT<br>
To: <a href="mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a><br>
Subject: I-D Action:draft-perkins-avt-rapid-rtp-sync-03.txt<br>
Reply-To:
<a href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a><br>
<br>
A New Internet-Draft is available from the on-line Internet-Drafts<br>
directories.<br><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Rapid
Synchronisation of RTP Flows<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : C. Perkins, T.
Schierl<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
draft-perkins-avt-rapid-rtp-sync-03.txt<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
17<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
2009-03-09<br><br>
This memo outlines how RTP multimedia sessions are synchronised, and<br>
discusses how rapidly such synchronisation can occur.&nbsp; We show
that<br>
most RTP sessions can be synchronised immediately, but that the use<br>
of video switching multipoint conference units (MCUs) or large
source<br>
specific multicast (SSM) groups can greatly increase the initial<br>
synchronisation delay.&nbsp; This increase in delay can be unacceptable
to<br>
some applications that use layered and/or multi-description
codecs.<br><br>
This memo updates the RTP Control Protocol (RTCP) timing rules to<br>
reduce the initial synchronisation delay for SSM sessions.&nbsp; A
new<br>
feedback packet is defined for use with the Extended RTP Profile for<br>
RTCP-based Feedback (RTP/AVPF), allowing video switching MCUs to<br>
rapidly request resynchronisation.&nbsp; Two new RTP header extensions
are<br>
defined to allow rapid synchronisation of late joiners, and
guarantee<br>
correct timestamp based decoding order recovery for layered codecs
in<br>
the presence of clock skew.<br><br>
A URL for this Internet-Draft is:<br>
<a href="http://www.ietf.org/internet-drafts/draft-perkins-avt-rapid-rtp">
http://www.ietf.org/internet-drafts/draft-perkins-avt-rapid-rtp</a>-
sync-03.txt<br><br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href="ftp://ftp.ietf.org/internet-drafts/">
ftp://ftp.ietf.org/internet-drafts/</a><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>
Content-Type: text/plain<br>
Content-ID:
<a href="mailto:2009-03-09100610.I-D@ietf.org">
&lt;2009-03-09100610.I-D@ietf.org&gt;</a><br><br>
_______________________________________________<br>
I-D-Announce mailing list<br>
<a href="mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/i-d-announce" eudora="autourl">
https://www.ietf.org/mailman/listinfo/i-d-announce</a><br>
Internet-Draft directories:
<a href="http://www.ietf.org/shadow.html">
http://www.ietf.org/shadow.html</a><br>
or
<a href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt">
ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a></blockquote><br>
_______________________________________________<br>
Audio/Video Transport Working Group<br>
<a href="mailto:avt@ietf.org">avt@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/avt" eudora="autourl">
https://www.ietf.org/mailman/listinfo/avt</a></blockquote><br>
_______________________________________________<br>
Audio/Video Transport Working Group<br>
<a href="mailto:avt@ietf.org">avt@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/avt" eudora="autourl">
https://www.ietf.org/mailman/listinfo/avt</a></blockquote><br>
---<br>
Visit us at<br><br>
Web 2.0 Expo / March 31 - April 03 / San Francisco, California / Booth
415<br>
<a href="http://www.web2expo.com/webexsf2009">
http://www.web2expo.com/webexsf2009</a><br><br>
NAB SHOW 2009 / April 18-23 / Las Vegas, Nevada USA / South Hall (Upper),
Booth SU9624F<br>
<a href="http://www.nabshow.com/">http://www.nabshow.com/</a></blockquote>
<br><br>
<br>
<pre>

_______________________________________________
Audio/Video Transport Working Group
<a href="mailto:avt@ietf.org">avt@ietf.org</a>

<a href="https://www.ietf.org/mailman/listinfo/avt" eudora="autourl">
https://www.ietf.org/mailman/listinfo/avt</a>
&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</pre><font face="Courier New, Courier"></font></blockquote><br><br>
----<br>
Visit us at<br><br>
Web 2.0 Expo / March 31 - April 03 / San Francisco, California / Booth
415<br>
<a href="http://www.web2expo.com/webexsf2009">
http://www.web2expo.com/webexsf2009</a><br><br>
NAB SHOW 2009 / April 18-23 / Las Vegas, Nevada USA / South Hall (Upper),
Booth SU9624F<br>
<a href="http://www.nabshow.com/">http://www.nabshow.com/</a></blockquote>
<br><br>
<pre>


_______________________________________________
Audio/Video Transport Working Group
<a href="mailto:avt@ietf.org">avt@ietf.org</a>
<a href="https://www.ietf.org/mailman/listinfo/avt" eudora="autourl">
https://www.ietf.org/mailman/listinfo/avt</a>
&nbsp;
</pre><font face="Courier New, Courier"></font></blockquote><br><br>
----<br>
Visit us at<br><br>
IEEE ICC 2009 / June 14-18 / Dresden, Germany / International Congress
Center<br>
<a href="http://www.comsoc.org/confs/icc/2009/">
http://www.comsoc.org/confs/icc/2009/</a><br><br>
Laser World of Photonics 2009 / June 15-18 / Munich, Germay / Hall B1,
Booth 461<br>
<a href="http://world-of-photonics.net/de/laser/start">
http://world-of-photonics.net/de/laser/start</a></blockquote></body>
</html>

--=====================_498927890==.ALT--


From Even.roni@huawei.com  Tue Jun 16 09:45:02 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 907E43A6B76 for <avt@core3.amsl.com>; Tue, 16 Jun 2009 09:45:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level: 
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mMGUENvCjIZ5 for <avt@core3.amsl.com>; Tue, 16 Jun 2009 09:45:01 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id A34743A6A9C for <avt@ietf.org>; Tue, 16 Jun 2009 09:45:01 -0700 (PDT)
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 <0KLC000JEBV2JD@szxga03-in.huawei.com> for avt@ietf.org; Wed, 17 Jun 2009 00:45:02 +0800 (CST)
Received: from huawei.com ([172.24.1.3]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLC0090BBV22Z@szxga03-in.huawei.com> for avt@ietf.org; Wed, 17 Jun 2009 00:45:02 +0800 (CST)
Received: from windows8d787f9 (bzq-79-176-13-151.red.bezeqint.net [79.176.13.151]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KLC00IQEBUTJF@szxml01-in.huawei.com>; Wed, 17 Jun 2009 00:45:02 +0800 (CST)
Date: Tue, 16 Jun 2009 19:43:08 +0300
From: Roni Even <Even.roni@huawei.com>
To: avt@ietf.org, "'Bill Ver Steeg (versteb)'" <versteb@cisco.com>
Message-id: <00a101c9eea1$8f8b34a0$aea19de0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_IdjXmcaSPBCfcHgQYc0vKA)"
Content-language: en-us
Thread-index: AcnuoYbkyqRebdzsTVGh9YuZTv/2dg==
Cc: 'Tom Taylor' <tom.taylor@rogers.com>
Subject: [AVT] Publish Ports (PubPorts) RTCP Message in draft-ietf-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: Tue, 16 Jun 2009 16:45:02 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_IdjXmcaSPBCfcHgQYc0vKA)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hi,

I do not think that this message should be in this draft, it is not in the
charter of this work. 

If you want to suggest a general message please write an individual draft
and we will have a discussion.

The individual draft should also discuss the use cases for this message .

 

 

Regards

Roni Even

AVT co-chair


--Boundary_(ID_IdjXmcaSPBCfcHgQYc0vKA)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<html 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" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="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="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 link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal>Hi,<o:p></o:p></p>

<p class=MsoNormal>I do not think that this message should be in this draft, it
is not in the charter of this work. <o:p></o:p></p>

<p class=MsoNormal>If you want to suggest a general message please write an individual
draft and we will have a discussion.<o:p></o:p></p>

<p class=MsoNormal>The individual draft should also discuss the use cases for
this message .<o:p></o:p></p>

<p class=MsoNormal><o:p>&nbsp;</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>

</body>

</html>

--Boundary_(ID_IdjXmcaSPBCfcHgQYc0vKA)--

From Even.roni@huawei.com  Tue Jun 16 10:09:19 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F7B73A6A22 for <avt@core3.amsl.com>; Tue, 16 Jun 2009 10:09:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level: 
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mh6ZFhNCxxfQ for <avt@core3.amsl.com>; Tue, 16 Jun 2009 10:09:18 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 7EE233A6BA6 for <avt@ietf.org>; Tue, 16 Jun 2009 10:09:18 -0700 (PDT)
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 <0KLC00KJGCZSRY@szxga03-in.huawei.com> for avt@ietf.org; Wed, 17 Jun 2009 01:09:28 +0800 (CST)
Received: from huawei.com ([172.24.1.6]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLC0060LCZSTT@szxga03-in.huawei.com> for avt@ietf.org; Wed, 17 Jun 2009 01:09:28 +0800 (CST)
Received: from windows8d787f9 (bzq-79-176-13-151.red.bezeqint.net [79.176.13.151]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KLC00JI7CZLBJ@szxml02-in.huawei.com> for avt@ietf.org; Wed, 17 Jun 2009 01:09:28 +0800 (CST)
Date: Tue, 16 Jun 2009 20:07:39 +0300
From: Roni Even <Even.roni@huawei.com>
To: avt@ietf.org
Message-id: <00b801c9eea4$f90f3360$eb2d9a20$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_udO4tOLT0tpYt84sIBuh5A)"
Content-language: en-us
Thread-index: AcnupPP7shhfq4AdRG2dZ9bI0Xe2fQ==
Subject: [AVT] comments on section 10 of draft-ietf-avt-rapid-acquisition-for-rtp-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: Tue, 16 Jun 2009 17:09:19 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_udO4tOLT0tpYt84sIBuh5A)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hi,

I looked at section 10 and have some comments

 

1.       If RTP/RTCP multiplexing is used, there is no need for any specific
operation from the RR side. The RR sends the RAMS-R message to the RS from
the port it wants to receive the RAMS-I and RTP payload. The RS just sends
the information to the port from which it received the RAMS-R and not to the
one in the SDP

2.       In the case where there is no RTP/RTCP multiplexing, the RAMS-R
RTCP message will go to the RS and the RAMS-I will go to the port on the RR
from where the RAMS-R was received. For the RTP, the RR does not know if it
has a NAT on the way to the RS and should try to get a routable address
(using STUN for example) and providing the port to the RS ( we still need to
agree on how to do it)

3.       If the above two points are correct than the RR receive port in the
SDP is not really useful

 

Roni Even


--Boundary_(ID_udO4tOLT0tpYt84sIBuh5A)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<html 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" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="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;}
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;}
.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:981621948;
	mso-list-type:hybrid;
	mso-list-template-ids:1300420444 -1357878042 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="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 link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal>Hi,<o:p></o:p></p>

<p class=MsoNormal>I looked at section 10 and have some comments<o:p></o:p></p>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=LTR></span>If RTP/RTCP multiplexing is used,
there is no need for any specific operation from the RR side. The RR sends the
RAMS-R message to the RS from the port it wants to receive the RAMS-I and RTP
payload. The RS just sends the information to the port from which it received
the RAMS-R and not to the one in the SDP<o:p></o:p></p>

<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=LTR></span>In the case where there is no
RTP/RTCP multiplexing, the RAMS-R RTCP message will go to the RS and the RAMS-I
will go to the port on the RR from where the RAMS-R was received. For the RTP,
the RR does not know if it has a NAT on the way to the RS and should try to get
a routable address (using STUN for example) and providing the port to the RS (
we still need to agree on how to do it)<o:p></o:p></p>

<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=LTR></span>If the above two points are
correct than the RR receive port in the SDP is not really useful<o:p></o:p></p>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal>Roni Even<o:p></o:p></p>

</div>

</body>

</html>

--Boundary_(ID_udO4tOLT0tpYt84sIBuh5A)--

From abegen@cisco.com  Tue Jun 16 10:46:41 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 E3BB228C1A0 for <avt@core3.amsl.com>; Tue, 16 Jun 2009 10:46:41 -0700 (PDT)
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 8F2jtYcEm49J for <avt@core3.amsl.com>; Tue, 16 Jun 2009 10:46:41 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 1CCA928C1B0 for <avt@ietf.org>; Tue, 16 Jun 2009 10:46:41 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,230,1243814400"; d="scan'208";a="170416173"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-3.cisco.com with ESMTP; 16 Jun 2009 17:46:26 +0000
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n5GHkQ06012450;  Tue, 16 Jun 2009 10:46:26 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id n5GHkNkl010864; Tue, 16 Jun 2009 17:46:23 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 16 Jun 2009 10:46:23 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 16 Jun 2009 10:46:19 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D54098D8362@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <00a101c9eea1$8f8b34a0$aea19de0$%roni@huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Publish Ports (PubPorts) RTCP Message in draft-ietf-avt-rapid-rtp-sync-02
Thread-Index: AcnuoYbkyqRebdzsTVGh9YuZTv/2dgACAO6Q
References: <00a101c9eea1$8f8b34a0$aea19de0$%roni@huawei.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Roni Even" <Even.roni@huawei.com>, <avt@ietf.org>, "Bill Ver Steeg (versteb)" <versteb@cisco.com>
X-OriginalArrivalTime: 16 Jun 2009 17:46:23.0212 (UTC) FILETIME=[5D311AC0:01C9EEAA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1034; t=1245174387; x=1246038387; c=relaxed/simple; s=sjdkim1004; 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]=20Publish=20Ports=20(PubPorts)=20 RTCP=20Message=20in=20draft-ietf-avt-rapid-rtp-sync-02 |Sender:=20; bh=q5TptFQfdt3NpWbd3trzXa2SvYE0amD7ekWmjlgKI2A=; b=VbtaMweYLZChYSgMDX2xAYBCQtffcT3xGBCsIBPXZjXvbzyu8i7et4qeWt KDPbzDWPddqkkS6V8mCWojE/sE+UkknNatce3luOwhKqauCq0PDbWp+GeGjm E2+wir0RsNuQ4+pTW8MNoE0RKcI4ENL4woDbVTDFgIZazOUHMn8kU=;
Authentication-Results: sj-dkim-1; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Cc: Tom Taylor <tom.taylor@rogers.com>
Subject: Re: [AVT] Publish Ports (PubPorts) RTCP Message in draft-ietf-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: Tue, 16 Jun 2009 17:46:42 -0000

Hi Roni,

We simply wanted to get the feedback from AVT on this approach as it =
nicely applies to the RAMS problem. If this turns out to be a good =
solution (for RAMS or other scenarios as well), we will be happy to =
separate it from the RAMS draft and refer to it normatively.=20

-acbegen

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of =
Roni Even
> Sent: Tuesday, June 16, 2009 9:43 AM
> To: avt@ietf.org; Bill Ver Steeg (versteb)
> Cc: 'Tom Taylor'
> Subject: [AVT] Publish Ports (PubPorts) RTCP Message in =
draft-ietf-avt-rapid-rtp-sync-02
>=20
> Hi,
>=20
> I do not think that this message should be in this draft, it is not in =
the charter of this
> work.
>=20
> If you want to suggest a general message please write an individual =
draft and we will have
> a discussion.
>=20
> The individual draft should also discuss the use cases for this =
message .
>=20
>=20
>=20
>=20
>=20
> Regards
>=20
> Roni Even
>=20
> AVT co-chair


From abegen@cisco.com  Tue Jun 16 12:01:39 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 860293A6DAB for <avt@core3.amsl.com>; Tue, 16 Jun 2009 12:01:39 -0700 (PDT)
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 UsVNWSHcVtzA for <avt@core3.amsl.com>; Tue, 16 Jun 2009 12:01:38 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id CA42B28C0DC for <avt@ietf.org>; Tue, 16 Jun 2009 12:01:30 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,231,1243814400"; d="scan'208";a="200914104"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-1.cisco.com with ESMTP; 16 Jun 2009 19:01:40 +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 n5GJ1fO9027767;  Tue, 16 Jun 2009 12:01:41 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n5GJ1f2o009030; Tue, 16 Jun 2009 19:01:41 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 16 Jun 2009 12:01:41 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 16 Jun 2009 11:59:37 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D54098D83DD@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <00b801c9eea4$f90f3360$eb2d9a20$%roni@huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] comments on section 10 ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
Thread-Index: AcnupPP7shhfq4AdRG2dZ9bI0Xe2fQABeZQA
References: <00b801c9eea4$f90f3360$eb2d9a20$%roni@huawei.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Roni Even" <Even.roni@huawei.com>, <avt@ietf.org>
X-OriginalArrivalTime: 16 Jun 2009 19:01:41.0319 (UTC) FILETIME=[E2318570:01C9EEB4]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1798; t=1245178901; x=1246042901; 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]=20comments=20on=20section=2010=20 ofdraft-ietf-avt-rapid-acquisition-for-rtp-01 |Sender:=20; bh=o09w4pf7dx37cW+aWVJYmOxT6ZgD8SsBdSiBooihYug=; b=QQtTooZK8felmi32ah0+r3dVnsK0tIeyijOIarVJWnL7eK6avwdGUlp7ZD 0RfIxkovkiz0ImM3o/lZ1Tb2eB8xJVZTetKndG0OevgClazoeL2RaEdLZx94 SjJmCcmyha;
Authentication-Results: sj-dkim-4; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Subject: Re: [AVT] comments on section 10 ofdraft-ietf-avt-rapid-acquisition-for-rtp-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: Tue, 16 Jun 2009 19:01:39 -0000

Remember that the RAMS-R (RR->RS) message is NOT on the retransmission =
(unicast) session, it's on the primary session since it is sent to the =
feedback target of the primary SSM session. Thus, the source port RR =
uses to send RAMS-R "cannot" be assumed to be the destination port it =
wishes to receive the unicast burst on.

If you agree with this statement, it is clear why we need port =
signaling. Muxing will not help much here. It will just reduce the =
number of signaled ports from 2 to 1.

-acbegen


> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of =
Roni Even
> Sent: Tuesday, June 16, 2009 10:08 AM
> To: avt@ietf.org
> Subject: [AVT] comments on section 10 =
ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
> Hi,
>=20
> I looked at section 10 and have some comments
>=20
>=20
>=20
> 1.       If RTP/RTCP multiplexing is used, there is no need for any =
specific operation
> from the RR side. The RR sends the RAMS-R message to the RS from the =
port it wants to
> receive the RAMS-I and RTP payload. The RS just sends the information =
to the port from
> which it received the RAMS-R and not to the one in the SDP
>=20
> 2.       In the case where there is no RTP/RTCP multiplexing, the =
RAMS-R RTCP message will
> go to the RS and the RAMS-I will go to the port on the RR from where =
the RAMS-R was
> received. For the RTP, the RR does not know if it has a NAT on the way =
to the RS and
> should try to get a routable address (using STUN for example) and =
providing the port to
> the RS ( we still need to agree on how to do it)
>=20
> 3.       If the above two points are correct than the RR receive port =
in the SDP is not
> really useful
>=20
>=20
>=20
> Roni Even


From csp@csperkins.org  Tue Jun 16 12:23:23 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 10FD428C19D for <avt@core3.amsl.com>; Tue, 16 Jun 2009 12:23:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 qklGyUAxSHjn for <avt@core3.amsl.com>; Tue, 16 Jun 2009 12:23:19 -0700 (PDT)
Received: from anchor-msapost-2.mail.demon.net (anchor-msapost-2.mail.demon.net [195.173.77.165]) by core3.amsl.com (Postfix) with ESMTP id 4A6033A6BA4 for <avt@ietf.org>; Tue, 16 Jun 2009 12:23:19 -0700 (PDT)
Received: from starkperkins.demon.co.uk ([80.176.158.71] helo=[192.168.254.8]) by anchor-post-2.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1MGeFk-0003I7-m3; Tue, 16 Jun 2009 19:23:30 +0000
Message-Id: <C0A963AC-4B17-49FC-904C-44A43DF0B8D7@csperkins.org>
From: Colin Perkins <csp@csperkins.org>
To: Michael A Dolan <md.1@newtbt.com>
In-Reply-To: <0MKpCa-1MGbjS2vGp-000cit@mrelay.perfora.net>
Content-Type: multipart/alternative; boundary=Apple-Mail-6-585026478
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 16 Jun 2009 20:23:18 +0100
References: <20090309171502.518513A6359@core3.amsl.com> <4A6ACB13-0CBB-4DA7-84AD-28CDE56DB4C3@csperkins.org> <0MKpCa-1LoLs525qX-000cvA@mrelay.perfora.net> <49D1C793.9050409@hhi.fraunhofer.de> <0MKp8S-1Lof8c1LTC-000fjs@mrelay.perfora.net> <49D4AE9D.8060905@hhi.fraunhofer.de> <0MKpCa-1MEnZO1ysE-000d6S@mrelay.perfora.net> <4A323DC5.5020004@hhi.fraunhofer.de> <0MKpCa-1MGbjS2vGp-000cit@mrelay.perfora.net>
X-Mailer: Apple Mail (2.935.3)
Cc: avt@ietf.org
Subject: Re: [AVT] Fwd: I-D Action:draft-perkins-avt-rapid-rtp-sync-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: Tue, 16 Jun 2009 19:23:23 -0000

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

Michael,

On 16 Jun 2009, at 17:37, Michael A Dolan wrote:
> I decided to reply to the earlier email/draft so we have the thread  
> context since the comments apply to both that draft and the one  
> posted the other day. Sorry for any confusion.
>
> I think you might misunderstand my comment about the timebase.  I am  
> not proposing you force applications to use any specific timebase.   
> I am proposing that senders and receivers have to agree (implicitly  
> since it cannot be signaled) what timebase is being used in specific  
> NTPv4 terms.  "wallclock" is ambiguous, but more importantly will  
> not result in the improved sync time you desire without such an out  
> of band agreement.

To the extent that you can perform synchronisation given the ambiguity  
about the timebase, the mechanisms specified in our draft will improve  
synchronisation times. Signalling additional details on the clocks and  
timebase will also help synchronisation, clearly, but is an orthogonal  
issue (and might be something for MMUSIC to consider, rather than AVT,  
since it's primarily a signalling problem).

> Regarding the relationship to the media stream access points, again  
> there may be a misunderstanding.  I did not propose faster RTCP SR  
> records be forbidden, or even discouraged.  I am proposing  
> clarifying text explaining the important sync-related relationship  
> that would change one's interpretation of the tables and desired  
> RTCP SR frequency.  I believe the tables are misleading where they  
> imply actual sync times remotely near 0.04 seconds.

I'm not sure I see the problem here - can you clarify?

> Since I am only proposing (albeit important in my opinion)  
> clarifying material and am not actually opposing what is there now;  
> and I am willing to craft specific text changes (your option); I am  
> not sure I understand the offhand rejection of the comments.
>
> Based on offline emails with you and the chair, I understood this  
> work to be THE authority on rapid sync of RTP sessions.  Maybe I  
> misunderstood and its scope is more narrow than that. If that's the  
> case, then perhaps we can narrow the scope of the work and I'll  
> author another draft on RTP sync. But I think the proposed changes  
> are relatively minor in the grand scheme of things and hope you will  
> consider addressing them in this draft.

If there is an issue with timing of media access points affecting the  
synchronisation latency, then that fits with the discussion in our  
draft. However, I think signalling to define the timebase for  
synchronisation is a broader problem, separate to the additional  
mechanisms we define, and would be better suited to a separate draft.

Cheers,
Colin



> Regards,
>
>         Mike
>
> At 01:36 PM 6/12/2009 +0200, Thomas Schierl wrote:
>> Hi Michael,
>>
>> I guess your comments are related to draft-ietf-avt-rapid-rtp- 
>> sync-02.txt. Please find my comments in line.
>>
>> Thomas
>>
>> Michael A Dolan wrote:
>>> Thomas and all-
>>>
>>> Continuing this in the context of yesterday's WG draft -02:
>>>
>>> 1. The draft still uses "wallclock".  I believe what's important  
>>> is that the NTP reference clock must have the same reference_ID  
>>> value as the clock used in the RTCP SR records. It's not important  
>>> that it be "wallclock" (or more precisely, one of the values  
>>> defined in NTPv4).  It can be PPS or something else. The draft  
>>> does mention that a common clock should be used.  The problem I  
>>> see is that the language is imprecise WRT NTPv4 terminology and  
>>> implies a vague subset of timebases by using the term,  
>>> "wallclock". Further, when the hdr ext for NTP is not used, it  
>>> should be stated that the NTP timebase reference_ID must be agreed  
>>> to out of band between the senders and receivers.
>>
>> See my original comments attached to your message. I think we do  
>> not want to make any additional requirements on the clock to be  
>> used for generating the wallclock, i.e. we will keep the  
>> definitions in RFC 3550 for backward compatibility reasons.
>>
>>>
>>> 2. Sync can only occur when the receiver has not only NTP and RTCP  
>>> SR packets, but also a point in every RTP session where there is  
>>> an "access point" for that media stream.  Since these access  
>>> points are customarily considerably further apart than 0.04  
>>> seconds, the tables are a bit misleading on the practical sync  
>>> time and recommended RTCP SR emission frequency.  It should be  
>>> noted around all the tables that there is no benefit to sending  
>>> the RTCP SR record more often than the media access point  
>>> frequency, especially in combination with the next comment below.
>>
>> Sure, there is typically a need for a random access point to start  
>> decoding. So on the first glance it makes sense to send SRs not  
>> with a higher frequency than random access points. But there may be  
>> a benefit to send SRs more frequently, e.g., to estimate clock skews.
>>
>>>
>>> 3. It should be recommended that RTCP SR packets be sent near, and  
>>> immediately following, media access points (subject to the 5%  
>>> boundary). Doing so will greatly improve the sync time rather than  
>>> relying on more frequent, and/or randomly timed, RTCP SR packets.
>>
>> Generally, it should not be a problem to slightly delay RTCP  
>> packets in order to align with media random access points, but this  
>> would need further analysis to document the acceptable bounds. I  
>> guess this would require more time and would further delay the  
>> intended solution for layered codecs. In order to not further delay  
>> the solution in this draft, this could become a topic of another  
>> draft.
>>
>>>
>>> Comment #1 becomes even more important the faster you want to  
>>> sync.  If the RTP sessions are using GPS and the NTP source is  
>>> using UTC (both "wallclock"), there will be errors measured in  
>>> seconds.  This disparity is less likely when the hdr ext is used,  
>>> of course. But in the general case, this language needs tightening  
>>> up to remove the clock errors.
>>>
>>> Comments 2 & 3, although true in all scenarios, become more  
>>> relevant in SSM with late joiners.
>>>
>>> I hope the above comments are clearer than my attempts below.  I'm  
>>> happy to suggest specific edits to the draft if that will help.
>>>
>>> Regards,
>>>
>>>         Mike
>>>
>>> At 02:25 PM 4/2/2009 +0200, Thomas.Schierl@hhi.fraunhofer.de wrote:
>>>> Hi Michael,
>>>>
>>>> What I can see from the ATSC M/H Transport spec is that there are  
>>>> requirements on encoder and decoder clock precisions, which for  
>>>> sure give a complete different environment than assumed by  
>>>> RFC3550 with respect to the clock precision. If we could assure  
>>>> such clocks for all devices which may potentially encode and  
>>>> stream layered media via multi session transmission, the problem  
>>>> would have been solved anyway. But that is not the case, as I  
>>>> tried to show by pointing to some of the relevant discussions on  
>>>> the mailing list.
>>>>
>>>> About your second point: RTP does not require NTP to be used as  
>>>> wallclock. In RTP, there is much more freedom in selecting the  
>>>> source for this clock. RTP uses the NTP timestamp format just for  
>>>> indicating the wallclock in the RTCP sender reports. Furthermore  
>>>> draft-perkins-avt-rapid-rtp-sync-03 does only require to use the  
>>>> same wallclock as used for the SRs also for the wallclock  
>>>> timestamps in the header extensions.
>>>>
>>>> Another interesting point is that the ATSC Transport spec is not  
>>>> mentioning SVC while mentioning AVC and AAC. If looking at the  
>>>> ATSC Video Systems spec. ( S4-136r7-A153-Part-7-Video-System),  
>>>> there is a solution which requires RTP timestamp synchronization  
>>>> for "SVC Transport in Two RTP Sessions". This for sure solves the  
>>>> clock skew problem, but as discussed in AVT, this is not a  
>>>> general solution and has different implications if applied to all  
>>>> use cases of RTP multi session transmission as, e.g.  
>>>> conversational services. Therefore we now have a solution which  
>>>> seems to be agreeable by the group, which solves the problem and  
>>>> is more in line with RFC 3550, i.e. using the wallclock for the  
>>>> data alignment between the session.
>>>>
>>>> Best regards,
>>>> Thomas
>>>>
>>>>
>>>> Michael A Dolan wrote:
>>>>> Hi Thomas-
>>>>>
>>>>> Thanks.  Yes, I am familiar with the discussion.
>>>>>
>>>>> I'm not necessarily pushing the ATSC solution, but offering some  
>>>>> points to consider, which apply equally to the problem at hand  
>>>>> here, I think.
>>>>>
>>>>> Also, it is important to note some more things about the ATSC  
>>>>> text:
>>>>>
>>>>> 1. The language in the specification very carefully recommends  
>>>>> the clock precision without requiring it.  It is expected to  
>>>>> work over routers with jitter and delays and with media  
>>>>> components from outside the broadcast facility. The difference  
>>>>> is that the client is expected to be able to perform tight sync  
>>>>> when the servers are able to provide the recommended timing  
>>>>> model (encoding one hop away, etc).  It gracefully degrades to  
>>>>> "Internet" timing model quality.
>>>>>
>>>>> 2. The clock, although "NTP" syntax, is not time of day (e.g.  
>>>>> reference_ID= "GPS"), but "PPS", thus allowing the components to  
>>>>> be encoded and decoded without concern for end-to-end delivery  
>>>>> delay.  This only works when NTP is explicitly signaled as part  
>>>>> of the encoding and both components share a clock (same or  
>>>>> closely coupled encoders). So it will not work in the general  
>>>>> case.  But there are many systems where it will and perhaps  
>>>>> consideration should be given to permitting non-"wall clock"  
>>>>> timebases.
>>>>>
>>>>> The NTP hdr ext here is an encoding optimization that indeed has  
>>>>> some other good properties.  Although the draft ties the NTP  
>>>>> timestamp back to the RTCP SR records, the timebase is not  
>>>>> explicitly defined (which is also true of RTCP SR).  Some  
>>>>> reference_ID value must be assumed and there is enough delta  
>>>>> between, for example, GPS and UTC, timebases to cause things to  
>>>>> break if the entire system is not implicitly assumed to be only  
>>>>> one timebase. For example, without an explicit reference_ID, how  
>>>>> could one use other timebases defined in NTPv4?  This is a  
>>>>> broader issue than the hdr ext syntax, but since we're  
>>>>> discussing NTP, I thought I'd bring it up.
>>>>>
>>>>> I think the above and the other points below are relevant here  
>>>>> and not inconsistent with the RTCP SR methods. The fact that the  
>>>>> ATSC design *can* be more precise is not alone cause to discard  
>>>>> the techniques developed there.
>>>>>
>>>>> Regards,
>>>>>
>>>>>          Mike
>>>>>
>>>>> At 09:34 AM 3/31/2009 +0200, Thomas.Schierl@hhi.fraunhofer.de  
>>>>> wrote:
>>>>>> Dear Michael,
>>>>>>
>>>>>> Thanks for the comments and the reference to the ATSC M/H.
>>>>>>
>>>>>> I guess, what we are looking for in AVT is a solution which  
>>>>>> also works for encoders having non-perfect clocks. There was a  
>>>>>> long discussion on the list, here are two pointers:
>>>>>>
>>>>>> http://www.ietf.org/mail-archive/web/avt/current/msg09144.html
>>>>>> http://www.ietf.org/mail-archive/web/avt/current/msg10491.html
>>>>>>
>>>>>> ATSC surely can assume to have a perfect clock in the NTP  
>>>>>> streams, which will not be the case on PC systems that may be  
>>>>>> used as an encoder for multi session transmission of a layered  
>>>>>> codec. This is one major problem we intended to solve with the  
>>>>>> header extension while keeping the whole approach as close as  
>>>>>> possible in line with the existing RTCP SR method.
>>>>>>
>>>>>>
>>>>>> Best regards,
>>>>>> Thomas
>>>>>>
>>>>>>
>>>>>>
>>>>>> ______________________________________________
>>>>>> Thomas Schierl, Dipl.-Ing.
>>>>>> Fraunhofer HHI
>>>>>> Senior Research Engineer
>>>>>> Image Processing Dept. / Multimedia Transport
>>>>>> Einsteinufer 37, 10587 Berlin, Germany
>>>>>> PHONE: +49 30 31002 227 , FAX: +49 30 392 7200
>>>>>> WEB: http://ip.hhi.de , SKYPE: thomas.schierl
>>>>>> EMAIL: thomas.schierl@hhi.fraunhofer.de
>>>>>>
>>>>>>
>>>>>>
>>>>>> Michael A Dolan wrote:
>>>>>>> Those interested in this topic may also find this interesting:
>>>>>>>
>>>>>>> http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-132r13-A153-Part-3-Transport.pdf
>>>>>>>
>>>>>>> Section 10.3.
>>>>>>>
>>>>>>> Some differences are:
>>>>>>>
>>>>>>> 1. There is one NTP packet stream per service, rather than the  
>>>>>>> encoding optimization in the hdr ext;
>>>>>>> 2. RTCP SR records are emitted "near" video random access  
>>>>>>> points, rather than on a prescribed time schedule; and
>>>>>>> 3. The above works in multicast-only, UDLR networks (e.g.  
>>>>>>> television broadcast), rather than requiring a 2-way link.
>>>>>>>
>>>>>>> #2 is interesting since in order to begin a *synchronized*  
>>>>>>> decode (video + audio properly correlated), a client must have  
>>>>>>> acquired all of:
>>>>>>> a. NTP
>>>>>>> b. RTCP SR for each component
>>>>>>> c. video reference frame and decoding metadata (i.e. a random  
>>>>>>> access point)
>>>>>>> d. audio frame
>>>>>>>
>>>>>>> So, the relative timing of the RTCP SR records to the RTP  
>>>>>>> stream content is perhaps more important than the emission  
>>>>>>> period.  Having the RTCP SR records arrive faster than the  
>>>>>>> video reference frames doesn't help of course.  And even if  
>>>>>>> they are "fast enough", having them arrive out of sync with  
>>>>>>> the reference frames delays the service acquisition by half  
>>>>>>> the period on average.
>>>>>>>
>>>>>>> Bandwidth utilization (how many bits to devote to RTCP and  
>>>>>>> NTP) can arguably be more efficiently managed by the server in  
>>>>>>> most cases, not individual client requests for faster RTCP SR  
>>>>>>> packets. And, the client would have no knowledge of the  
>>>>>>> intended (video) reference frame periods being used by the  
>>>>>>> server, so it would not, in general, know what to ask for.
>>>>>>>
>>>>>>> In practice, won't a server that wants to enable faster  
>>>>>>> acquisition and sync do things like the above?  I'm concerned  
>>>>>>> that detailed requests from clients beyond "please use more  
>>>>>>> bandwidth and enable fast sync" won't be as valuable as they  
>>>>>>> seem since in the general case the client doesn't know what to  
>>>>>>> ask for exactly.
>>>>>>>
>>>>>>> FYI, the above ATSC document is in a "candidate" state where  
>>>>>>> public comments are solicited.  Independent of this thread, if  
>>>>>>> anyone has comments on it, I could convey them back to the ATSC.
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>>         Mike
>>>>>>>
>>>>>>> At 07:43 PM 3/9/2009 +0000, Colin Perkins wrote:
>>>>>>>> The changes in this version are primarily editorial; we're  
>>>>>>>> aware that
>>>>>>>> not all the open issues have been addressed yet. Any further  
>>>>>>>> comments
>>>>>>>> are welcomed.
>>>>>>>>
>>>>>>>> Chairs: we'd like this to be considered as an AVT working group
>>>>>>>> draft, as indicated privately.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Colin
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Begin forwarded message:
>>>>>>>>> From: Internet-Drafts@ietf.org
>>>>>>>>> Date: 9 March 2009 17:15:02 GMT
>>>>>>>>> To: i-d-announce@ietf.org
>>>>>>>>> Subject: I-D Action:draft-perkins-avt-rapid-rtp-sync-03.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-03.txt
>>>>>>>>>         Pages           : 17
>>>>>>>>>         Date            : 2009-03-09
>>>>>>>>>
>>>>>>>>> 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-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.
>>>>>>>>> Content-Type: text/plain
>>>>>>>>> Content-ID: <2009-03-09100610.I-D@ietf.org>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> I-D-Announce mailing list
>>>>>>>>> I-D-Announce@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>>>>>>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>>>>>>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Audio/Video Transport Working Group
>>>>>>>> avt@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Audio/Video Transport Working Group
>>>>>>> avt@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>>
>>>>>> ---
>>>>>> Visit us at
>>>>>>
>>>>>> Web 2.0 Expo / March 31 - April 03 / San Francisco,  
>>>>>> California / Booth 415
>>>>>> http://www.web2expo.com/webexsf2009
>>>>>>
>>>>>> NAB SHOW 2009 / April 18-23 / Las Vegas, Nevada USA / South  
>>>>>> Hall (Upper), Booth SU9624F
>>>>>> http://www.nabshow.com/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Audio/Video Transport Working Group
>>>>> avt@ietf.org
>>>>>
>>>>>
>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>
>>>>>
>>>>
>>>>
>>>> ----
>>>> Visit us at
>>>>
>>>> Web 2.0 Expo / March 31 - April 03 / San Francisco, California /  
>>>> Booth 415
>>>> http://www.web2expo.com/webexsf2009
>>>>
>>>> NAB SHOW 2009 / April 18-23 / Las Vegas, Nevada USA / South Hall  
>>>> (Upper), Booth SU9624F
>>>> http://www.nabshow.com/
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Audio/Video Transport Working Group
>>> avt@ietf.org
>>>
>>> https://www.ietf.org/mailman/listinfo/avt
>>>
>>
>>
>> ----
>> Visit us at
>>
>> IEEE ICC 2009 / June 14-18 / Dresden, Germany / International  
>> Congress Center
>> http://www.comsoc.org/confs/icc/2009/
>>
>> Laser World of Photonics 2009 / June 15-18 / Munich, Germay / Hall  
>> B1, Booth 461
>> http://world-of-photonics.net/de/laser/start
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt



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




--Apple-Mail-6-585026478
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; ">Michael,<div><br></div><div>On =
16 Jun 2009, at 17:37, Michael A Dolan wrote:</div><div><div><blockquote =
type=3D"cite"><div>I decided to reply to the earlier email/draft so we =
have the thread context since the comments apply to both that draft and =
the one posted the other day. Sorry for any confusion.<br><br> I think =
you might misunderstand my comment about the timebase.&nbsp; I am not =
proposing you force applications to use any specific timebase.&nbsp; I =
am proposing that senders and receivers have to agree (implicitly since =
it cannot be signaled) what timebase is being used in specific NTPv4 =
terms.&nbsp; "wallclock" is ambiguous, but more importantly will not =
result in the improved sync time you desire without such an out of band =
agreement.<br></div></blockquote><div><br></div><div>To the extent that =
you can perform synchronisation given the ambiguity about the timebase, =
the mechanisms specified in our draft will improve synchronisation =
times.&nbsp;Signalling additional details on the clocks and timebase =
will also help synchronisation, clearly, but is an orthogonal issue (and =
might be something for MMUSIC to consider, rather than AVT, since it's =
primarily a signalling problem).&nbsp;</div><br><blockquote =
type=3D"cite"><div> Regarding the relationship to the media stream =
access points, again there may be a misunderstanding.&nbsp; I did not =
propose faster RTCP SR records be forbidden, or even discouraged.&nbsp; =
I am proposing clarifying text explaining the important sync-related =
relationship that would change one's interpretation of the tables and =
desired RTCP SR frequency.&nbsp; I believe the tables are misleading =
where they imply actual sync times remotely near 0.04 =
seconds.<br></div></blockquote><div><br></div><div>I'm not sure I see =
the problem here - can you clarify?</div><br><blockquote =
type=3D"cite"><div> Since I am only proposing (albeit important in my =
opinion) clarifying material and am not actually opposing what is there =
now; and I am willing to craft specific text changes (your option); I am =
not sure I understand the offhand rejection of the comments.<br><br> =
Based on offline emails with you and the chair, I understood this work =
to be THE authority on rapid sync of RTP sessions.&nbsp; Maybe I =
misunderstood and its scope is more narrow than that. If that's the =
case, then perhaps we can narrow the scope of the work and I'll author =
another draft on RTP sync. But I think the proposed changes are =
relatively minor in the grand scheme of things and hope you will =
consider addressing them in this =
draft.<br></div></blockquote><div><br></div><div>If there is an issue =
with timing of media access points affecting the synchronisation =
latency, then that fits with the discussion in our draft. However, I =
think signalling to define the timebase for synchronisation is a broader =
problem, separate to the additional mechanisms we define, and would be =
better suited to a separate =
draft.</div><div><br></div><div>Cheers,</div><div>Colin</div><div><br></di=
v><div><br></div><br><blockquote type=3D"cite"><div> Regards,<br><br> =
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Mike<br> =
<br> At 01:36 PM 6/12/2009 +0200, Thomas Schierl wrote:<br> <blockquote =
type=3D"cite" class=3D"cite" cite=3D"">Hi Michael,<br><br> I guess your =
comments are related to draft-ietf-avt-rapid-rtp-sync-02.txt. Please =
find my comments in line.<br><br> Thomas<br><br> Michael A Dolan wrote: =
<br> <blockquote type=3D"cite" class=3D"cite" cite=3D"">Thomas and =
all-<br><br> Continuing this in the context of yesterday's WG draft =
-02:<br><br> 1. The draft still uses "wallclock".&nbsp; I believe what's =
important is that the NTP reference clock must have the same =
reference_ID value as the clock used in the RTCP SR records. It's not =
important that it be "wallclock" (or more precisely, one of the values =
defined in NTPv4).&nbsp; It can be PPS or something else. The draft does =
mention that a common clock should be used.&nbsp; The problem I see is =
that the language is imprecise WRT NTPv4 terminology and implies a vague =
subset of timebases by using the term, "wallclock". Further, when the =
hdr ext for NTP is not used, it should be stated that the NTP timebase =
reference_ID must be agreed to out of band between the senders and =
receivers.</blockquote><br> See my original comments attached to your =
message. I think we do not want to make any additional requirements on =
the clock to be used for generating the wallclock, i.e. we will keep the =
definitions in RFC 3550 for backward compatibility reasons.<br><br> =
<blockquote type=3D"cite" class=3D"cite" cite=3D""><br> 2. Sync can only =
occur when the receiver has not only NTP and RTCP SR packets, but also a =
point in every RTP session where there is an "access point" for that =
media stream.&nbsp; Since these access points are customarily =
considerably further apart than 0.04 seconds, the tables are a bit =
misleading on the practical sync time and recommended RTCP SR emission =
frequency.&nbsp; It should be noted around all the tables that there is =
no benefit to sending the RTCP SR record more often than the media =
access point frequency, especially in combination with the next comment =
below.</blockquote><br> Sure, there is typically a need for a random =
access point to start decoding. So on the first glance it makes sense to =
send SRs not with a higher frequency than random access points. But =
there may be a benefit to send SRs more frequently, e.g., to estimate =
clock skews.<br><br> <blockquote type=3D"cite" class=3D"cite" =
cite=3D""><br> 3. It should be recommended that RTCP SR packets be sent =
near, and immediately following, media access points (subject to the 5% =
boundary). Doing so will greatly improve the sync time rather than =
relying on more frequent, and/or randomly timed, RTCP SR =
packets.</blockquote><br> Generally, it should not be a problem to =
slightly delay RTCP packets in order to align with media random access =
points, but this would need further analysis to document the acceptable =
bounds. I guess this would require more time and would further delay the =
intended solution for layered codecs. In order to not further delay the =
solution in this draft, this could become a topic of another draft. =
<br><br> <blockquote type=3D"cite" class=3D"cite" cite=3D""><br> Comment =
#1 becomes even more important the faster you want to sync.&nbsp; If the =
RTP sessions are using GPS and the NTP source is using UTC (both =
"wallclock"), there will be errors measured in seconds.&nbsp; This =
disparity is less likely when the hdr ext is used, of course. But in the =
general case, this language needs tightening up to remove the clock =
errors.<br><br> Comments 2 &amp; 3, although true in all scenarios, =
become more relevant in SSM with late joiners.<br><br> I hope the above =
comments are clearer than my attempts below.&nbsp; I'm happy to suggest =
specific edits to the draft if that will help.<br><br> Regards,<br><br> =
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Mike<br> =
<br> At 02:25 PM 4/2/2009 +0200, <a =
href=3D"mailto:Thomas.Schierl@hhi.fraunhofer.de"> =
Thomas.Schierl@hhi.fraunhofer.de</a> wrote:<br> <blockquote type=3D"cite" =
class=3D"cite" cite=3D"">Hi Michael,<br><br> What I can see from the =
ATSC M/H Transport spec is that there are requirements on encoder and =
decoder clock precisions, which for sure give a complete different =
environment than assumed by RFC3550 with respect to the clock precision. =
If we could assure such clocks for all devices which may potentially =
encode and stream layered media via multi session transmission, the =
problem would have been solved anyway. But that is not the case, as I =
tried to show by pointing to some of the relevant discussions on the =
mailing list.<br><br> About your second point: RTP does not require NTP =
to be used as wallclock. In RTP, there is much more freedom in selecting =
the source for this clock. RTP uses the NTP timestamp format just for =
indicating the wallclock in the RTCP sender reports. Furthermore =
draft-perkins-avt-rapid-rtp-sync-03 does only require to use the same =
wallclock as used for the SRs also for the wallclock timestamps in the =
header extensions.<br><br> Another interesting point is that the ATSC =
Transport spec is not mentioning SVC while mentioning AVC and AAC. If =
looking at the ATSC Video Systems spec. (<a =
href=3D"http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-136r=
7-A153-Part-7-Video-System.pdf"> S4-136r7-A153-Part-7-Video-System</a>), =
there is a solution which requires RTP timestamp synchronization for =
"SVC Transport in Two RTP Sessions". This for sure solves the clock skew =
problem, but as discussed in AVT, this is not a general solution and has =
different implications if applied to all use cases of RTP multi session =
transmission as, e.g. conversational services. Therefore we now have a =
solution which seems to be agreeable by the group, which solves the =
problem and is more in line with RFC 3550, i.e. using the wallclock for =
the data alignment between the session.<br><br> Best regards,<br> =
Thomas<br><br> <br> Michael A Dolan wrote: <br> <blockquote type=3D"cite" =
class=3D"cite" cite=3D"">Hi Thomas-<br><br> Thanks.&nbsp; Yes, I am =
familiar with the discussion.<br><br> I'm not necessarily pushing the =
ATSC solution, but offering some points to consider, which apply equally =
to the problem at hand here, I think.<br><br> Also, it is important to =
note some more things about the ATSC text:<br><br> 1. The language in =
the specification very carefully recommends the clock precision without =
requiring it.&nbsp; It is expected to work over routers with jitter and =
delays and with media components from outside the broadcast facility. =
The difference is that the client is expected to be able to perform =
tight sync when the servers are able to provide the recommended timing =
model (encoding one hop away, etc).&nbsp; It gracefully degrades to =
"Internet" timing model quality.<br><br> 2. The clock, although "NTP" =
syntax, is not time of day (e.g. reference_ID=3D "GPS"), but "PPS", thus =
allowing the components to be encoded and decoded without concern for =
end-to-end delivery delay.&nbsp; This only works when NTP is explicitly =
signaled as part of the encoding and both components share a clock (same =
or closely coupled encoders). So it will not work in the general =
case.&nbsp; But there are many systems where it will and perhaps =
consideration should be given to permitting non-"wall clock" =
timebases.<br><br> The NTP hdr ext here is an encoding optimization that =
indeed has some other good properties.&nbsp; Although the draft ties the =
NTP timestamp back to the RTCP SR records, the timebase is not =
explicitly defined (which is also true of RTCP SR).&nbsp; Some =
reference_ID value must be assumed and there is enough delta between, =
for example, GPS and UTC, timebases to cause things to break if the =
entire system is not implicitly assumed to be only one timebase. For =
example, without an explicit reference_ID, how could one use other =
timebases defined in NTPv4?&nbsp; This is a broader issue than the hdr =
ext syntax, but since we're discussing NTP, I thought I'd bring it =
up.<br><br> I think the above and the other points below are relevant =
here and not inconsistent with the RTCP SR methods. The fact that the =
ATSC design *can* be more precise is not alone cause to discard the =
techniques developed there.<br><br> Regards,<br><br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mike<br><br> At 09:34 =
AM 3/31/2009 +0200, <a href=3D"mailto:Thomas.Schierl@hhi.fraunhofer.de"> =
Thomas.Schierl@hhi.fraunhofer.de</a> wrote:<br> <blockquote type=3D"cite" =
class=3D"cite" cite=3D"">Dear Michael,<br><br> Thanks for the comments =
and the reference to the ATSC M/H.<br><br> I guess, what we are looking =
for in AVT is a solution which also works for encoders having =
non-perfect clocks. There was a long discussion on the list, here are =
two pointers:<br><br> <a =
href=3D"http://www.ietf.org/mail-archive/web/avt/current/msg09144.html"> =
http://www.ietf.org/mail-archive/web/avt/current/msg09144.html</a><br> =
<a href=3D"http://www.ietf.org/mail-archive/web/avt/current/msg10491.html"=
 eudora=3D"autourl"> =
http://www.ietf.org/mail-archive/web/avt/current/msg10491.html</a><br><br>=
 ATSC surely can assume to have a perfect clock in the NTP streams, =
which will not be the case on PC systems that may be used as an encoder =
for multi session transmission of a layered codec. This is one major =
problem we intended to solve with the header extension while keeping the =
whole approach as close as possible in line with the existing RTCP SR =
method.<br><br> <br> Best regards,<br> Thomas<br><br> <br><br> =
______________________________________________<br> Thomas Schierl, =
Dipl.-Ing.<br> Fraunhofer HHI<br> Senior Research Engineer<br> Image =
Processing Dept. / Multimedia Transport<br> Einsteinufer 37, 10587 =
Berlin, Germany<br> PHONE: +49 30 31002 227 , FAX: +49 30 392 7200<br> =
WEB: <a href=3D"http://ip.hhi.de/">http://ip.hhi.de</a> , SKYPE: =
thomas.schierl<br> EMAIL: <a =
href=3D"mailto:thomas.schierl@hhi.fraunhofer.de"> =
thomas.schierl@hhi.fraunhofer.de</a><br><br> <br><br> Michael A Dolan =
wrote:<br> <blockquote type=3D"cite" class=3D"cite" cite=3D"">Those =
interested in this topic may also find this interesting:<br><br> <a =
href=3D"http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-132r=
13-A153-Part-3-Transport.pdf"> =
http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-132r13-A153-=
Part-3-Transport.pdf</a> <br><br> Section 10.3.<br><br> Some differences =
are:<br><br> 1. There is one NTP packet stream per service, rather than =
the encoding optimization in the hdr ext;<br> 2. RTCP SR records are =
emitted "near" video random access points, rather than on a prescribed =
time schedule; and<br> 3. The above works in multicast-only, UDLR =
networks (e.g. television broadcast), rather than requiring a 2-way =
link.<br><br> #2 is interesting since in order to begin a *synchronized* =
decode (video + audio properly correlated), a client must have acquired =
all of:<br> a. NTP<br> b. RTCP SR for each component<br> c. video =
reference frame and decoding metadata (i.e. a random access point)<br> =
d. audio frame<br><br> So, the relative timing of the RTCP SR records to =
the RTP stream content is perhaps more important than the emission =
period.&nbsp; Having the RTCP SR records arrive faster than the video =
reference frames doesn't help of course.&nbsp; And even if they are =
"fast enough", having them arrive out of sync with the reference frames =
delays the service acquisition by half the period on average.<br><br> =
Bandwidth utilization (how many bits to devote to RTCP and NTP) can =
arguably be more efficiently managed by the server in most cases, not =
individual client requests for faster RTCP SR packets. And, the client =
would have no knowledge of the intended (video) reference frame periods =
being used by the server, so it would not, in general, know what to ask =
for.<br><br> In practice, won't a server that wants to enable faster =
acquisition and sync do things like the above?&nbsp; I'm concerned that =
detailed requests from clients beyond "please use more bandwidth and =
enable fast sync" won't be as valuable as they seem since in the general =
case the client doesn't know what to ask for exactly.<br><br> FYI, the =
above ATSC document is in a "candidate" state where public comments are =
solicited.&nbsp; Independent of this thread, if anyone has comments on =
it, I could convey them back to the ATSC.<br><br> Regards,<br><br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mike<br><br> At 07:43 PM =
3/9/2009 +0000, Colin Perkins wrote:<br> <blockquote type=3D"cite" =
class=3D"cite" cite=3D"">The changes in this version are primarily =
editorial; we're aware that<br> not all the open issues have been =
addressed yet. Any further comments<br> are welcomed.<br><br> Chairs: =
we'd like this to be considered as an AVT working group<br> draft, as =
indicated privately.<br><br> Cheers,<br> Colin<br><br> <br><br> <br> =
Begin forwarded message:<br> <blockquote type=3D"cite" class=3D"cite" =
cite=3D"">From: <a =
href=3D"mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a><br> =
Date: 9 March 2009 17:15:02 GMT<br> To: <a =
href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a><br> =
Subject: I-D Action:draft-perkins-avt-rapid-rtp-sync-03.txt<br> =
Reply-To: <a =
href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a><br> =
<br> A New Internet-Draft is available from the on-line =
Internet-Drafts<br> directories.<br><br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
Rapid Synchronisation of RTP Flows<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : C. Perkins, T. =
Schierl<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
draft-perkins-avt-rapid-rtp-sync-03.txt<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
17<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
2009-03-09<br><br> This memo outlines how RTP multimedia sessions are =
synchronised, and<br> discusses how rapidly such synchronisation can =
occur.&nbsp; We show that<br> most RTP sessions can be synchronised =
immediately, but that the use<br> of video switching multipoint =
conference units (MCUs) or large source<br> specific multicast (SSM) =
groups can greatly increase the initial<br> synchronisation delay.&nbsp; =
This increase in delay can be unacceptable to<br> some applications that =
use layered and/or multi-description codecs.<br><br> This memo updates =
the RTP Control Protocol (RTCP) timing rules to<br> reduce the initial =
synchronisation delay for SSM sessions.&nbsp; A new<br> feedback packet =
is defined for use with the Extended RTP Profile for<br> RTCP-based =
Feedback (RTP/AVPF), allowing video switching MCUs to<br> rapidly =
request resynchronisation.&nbsp; Two new RTP header extensions are<br> =
defined to allow rapid synchronisation of late joiners, and =
guarantee<br> correct timestamp based decoding order recovery for =
layered codecs in<br> the presence of clock skew.<br><br> A URL for this =
Internet-Draft is:<br> <a =
href=3D"http://www.ietf.org/internet-drafts/draft-perkins-avt-rapid-rtp"> =
http://www.ietf.org/internet-drafts/draft-perkins-avt-rapid-rtp</a>- =
sync-03.txt<br><br> Internet-Drafts are also available by anonymous FTP =
at:<br> <a href=3D"ftp://ftp.ietf.org/internet-drafts/"> =
ftp://ftp.ietf.org/internet-drafts/</a><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> =
Content-Type: text/plain<br> Content-ID: <a =
href=3D"mailto:2009-03-09100610.I-D@ietf.org"> =
&lt;2009-03-09100610.I-D@ietf.org&gt;</a><br><br> =
_______________________________________________<br> I-D-Announce mailing =
list<br> <a =
href=3D"mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org</a><br> <a =
href=3D"https://www.ietf.org/mailman/listinfo/i-d-announce" =
eudora=3D"autourl"> =
https://www.ietf.org/mailman/listinfo/i-d-announce</a><br> =
Internet-Draft directories: <a href=3D"http://www.ietf.org/shadow.html"> =
http://www.ietf.org/shadow.html</a><br> or <a =
href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt"> =
ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a></blockquote><br> =
_______________________________________________<br> Audio/Video =
Transport Working Group<br> <a =
href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br> <a =
href=3D"https://www.ietf.org/mailman/listinfo/avt" eudora=3D"autourl"> =
https://www.ietf.org/mailman/listinfo/avt</a></blockquote><br> =
_______________________________________________<br> Audio/Video =
Transport Working Group<br> <a =
href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br> <a =
href=3D"https://www.ietf.org/mailman/listinfo/avt" eudora=3D"autourl"> =
https://www.ietf.org/mailman/listinfo/avt</a></blockquote><br> ---<br> =
Visit us at<br><br> Web 2.0 Expo / March 31 - April 03 / San Francisco, =
California / Booth 415<br> <a =
href=3D"http://www.web2expo.com/webexsf2009"> =
http://www.web2expo.com/webexsf2009</a><br><br> NAB SHOW 2009 / April =
18-23 / Las Vegas, Nevada USA / South Hall (Upper), Booth SU9624F<br> <a =
href=3D"http://www.nabshow.com/">http://www.nabshow.com/</a></blockquote> =
<br><br> <br> <pre>
_______________________________________________
Audio/Video Transport Working Group
<a href=3D"mailto:avt@ietf.org">avt@ietf.org</a>

<a href=3D"https://www.ietf.org/mailman/listinfo/avt" eudora=3D"autourl">
https://www.ietf.org/mailman/listinfo/avt</a>
&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</pre><font face=3D"Courier New, Courier"></font></blockquote><br><br> =
----<br> Visit us at<br><br> Web 2.0 Expo / March 31 - April 03 / San =
Francisco, California / Booth 415<br> <a =
href=3D"http://www.web2expo.com/webexsf2009"> =
http://www.web2expo.com/webexsf2009</a><br><br> NAB SHOW 2009 / April =
18-23 / Las Vegas, Nevada USA / South Hall (Upper), Booth SU9624F<br> <a =
href=3D"http://www.nabshow.com/">http://www.nabshow.com/</a></blockquote> =
<br><br> <pre>

_______________________________________________
Audio/Video Transport Working Group
<a href=3D"mailto:avt@ietf.org">avt@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" eudora=3D"autourl">
https://www.ietf.org/mailman/listinfo/avt</a>
&nbsp;
</pre><font face=3D"Courier New, Courier"></font></blockquote><br><br> =
----<br> Visit us at<br><br> IEEE ICC 2009 / June 14-18 / Dresden, =
Germany / International Congress Center<br> <a =
href=3D"http://www.comsoc.org/confs/icc/2009/"> =
http://www.comsoc.org/confs/icc/2009/</a><br><br> Laser World of =
Photonics 2009 / June 15-18 / Munich, Germay / Hall B1, Booth 461<br> <a =
href=3D"http://world-of-photonics.net/de/laser/start"> =
http://world-of-photonics.net/de/laser/start</a></blockquote></div>  =
_______________________________________________<br>Audio/Video Transport =
Working Group<br><a =
href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br>https://www.ietf.org/mail=
man/listinfo/avt<br></blockquote></div><br><div =
apple-content-edited=3D"true"> <span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Arial; font-size: 9px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Lucida Sans Typewriter'; font-size: 9px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; color: rgb(0, 0, 0); =
font-family: 'Lucida Sans Typewriter'; font-size: 9px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; -webkit-text-decorations-in-effect: none; =
text-indent: 0px; -webkit-text-size-adjust: auto; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; color: rgb(0, 0, 0); font-family: 'Lucida Sans Typewriter'; =
font-size: 9px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; =
-webkit-text-decorations-in-effect: none; text-indent: 0px; =
-webkit-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; color: rgb(0, 0, 0); font-family: 'Lucida Sans Typewriter'; =
font-size: 9px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; =
-webkit-text-decorations-in-effect: none; text-indent: 0px; =
-webkit-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"khtml-block-placeholder"></div><div>--&nbsp;</div><div></div><div=
>Colin Perkins</div><div><a =
href=3D"http://csperkins.org/">http://csperkins.org/</a></div></span></spa=
n></span><br class=3D"Apple-interchange-newline"></span><br =
class=3D"Apple-interchange-newline"></div></span> =
</div><br></div></body></html>=

--Apple-Mail-6-585026478--

From Even.roni@huawei.com  Tue Jun 16 12:49:28 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3AEEF3A6BA4 for <avt@core3.amsl.com>; Tue, 16 Jun 2009 12:49:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.238
X-Spam-Level: 
X-Spam-Status: No, score=-1.238 tagged_above=-999 required=5 tests=[AWL=0.742,  BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2oBGjbkQTNYg for <avt@core3.amsl.com>; Tue, 16 Jun 2009 12:49:27 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 67A5C3A6B11 for <avt@ietf.org>; Tue, 16 Jun 2009 12:49:27 -0700 (PDT)
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 <0KLC000N1KBIJD@szxga03-in.huawei.com> for avt@ietf.org; Wed, 17 Jun 2009 03:47:42 +0800 (CST)
Received: from huawei.com ([172.24.1.3]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLC0064TKBITT@szxga03-in.huawei.com> for avt@ietf.org; Wed, 17 Jun 2009 03:47:42 +0800 (CST)
Received: from windows8d787f9 (bzq-79-179-78-100.red.bezeqint.net [79.179.78.100]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KLC00I9DKBAJF@szxml01-in.huawei.com>; Wed, 17 Jun 2009 03:47:42 +0800 (CST)
Date: Tue, 16 Jun 2009 22:45:55 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <04CAD96D4C5A3D48B1919248A8FE0D54098D8362@xmb-sjc-215.amer.cisco.com>
To: "'Ali C. Begen (abegen)'" <abegen@cisco.com>, avt@ietf.org, "'Bill Ver Steeg (versteb)'" <versteb@cisco.com>
Message-id: <00d001c9eebb$168f60c0$43ae2240$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcnuoYbkyqRebdzsTVGh9YuZTv/2dgACAO6QAAQgTmA=
References: <00a101c9eea1$8f8b34a0$aea19de0$%roni@huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D8362@xmb-sjc-215.amer.cisco.com>
Cc: 'Tom Taylor' <tom.taylor@rogers.com>
Subject: Re: [AVT] Publish Ports (PubPorts) RTCP Message in draft-ietf-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: Tue, 16 Jun 2009 19:49:28 -0000

Ali,
This should be discussed either on the mailing list or by having an
individual draft and not as part of a WG draft
Roni

-----Original Message-----
From: Ali C. Begen (abegen) [mailto:abegen@cisco.com] 
Sent: Tuesday, June 16, 2009 8:46 PM
To: Roni Even; avt@ietf.org; Bill Ver Steeg (versteb)
Cc: Tom Taylor
Subject: RE: [AVT] Publish Ports (PubPorts) RTCP Message in
draft-ietf-avt-rapid-rtp-sync-02

Hi Roni,

We simply wanted to get the feedback from AVT on this approach as it nicely
applies to the RAMS problem. If this turns out to be a good solution (for
RAMS or other scenarios as well), we will be happy to separate it from the
RAMS draft and refer to it normatively. 

-acbegen

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Roni
Even
> Sent: Tuesday, June 16, 2009 9:43 AM
> To: avt@ietf.org; Bill Ver Steeg (versteb)
> Cc: 'Tom Taylor'
> Subject: [AVT] Publish Ports (PubPorts) RTCP Message in
draft-ietf-avt-rapid-rtp-sync-02
> 
> Hi,
> 
> I do not think that this message should be in this draft, it is not in the
charter of this
> work.
> 
> If you want to suggest a general message please write an individual draft
and we will have
> a discussion.
> 
> The individual draft should also discuss the use cases for this message .
> 
> 
> 
> 
> 
> Regards
> 
> Roni Even
> 
> AVT co-chair


From Even.roni@huawei.com  Tue Jun 16 13:49:05 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5FB913A6C74 for <avt@core3.amsl.com>; Tue, 16 Jun 2009 13:49:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.557
X-Spam-Level: 
X-Spam-Status: No, score=-0.557 tagged_above=-999 required=5 tests=[AWL=-0.681, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_SORBS_WEB=0.619, 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 JYOwIsCj-UFJ for <avt@core3.amsl.com>; Tue, 16 Jun 2009 13:49:04 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 4CA333A6BA4 for <avt@ietf.org>; Tue, 16 Jun 2009 13:48:47 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLC00DPIN2VHF@szxga02-in.huawei.com> for avt@ietf.org; Wed, 17 Jun 2009 04:47:20 +0800 (CST)
Received: from huawei.com ([172.24.1.3]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLC00DA0N2VHM@szxga02-in.huawei.com> for avt@ietf.org; Wed, 17 Jun 2009 04:47:19 +0800 (CST)
Received: from windows8d787f9 (bzq-79-179-78-100.red.bezeqint.net [79.179.78.100]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KLC00IBWN2OJF@szxml01-in.huawei.com>; Wed, 17 Jun 2009 04:47:19 +0800 (CST)
Date: Tue, 16 Jun 2009 23:45:35 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <04CAD96D4C5A3D48B1919248A8FE0D54098D83DD@xmb-sjc-215.amer.cisco.com>
To: "'Ali C. Begen (abegen)'" <abegen@cisco.com>, avt@ietf.org
Message-id: <00dc01c9eec3$6a8b3070$3fa19150$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcnupPP7shhfq4AdRG2dZ9bI0Xe2fQABeZQAAAWPwrA=
References: <00b801c9eea4$f90f3360$eb2d9a20$%roni@huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D83DD@xmb-sjc-215.amer.cisco.com>
Subject: Re: [AVT] comments on section 10 ofdraft-ietf-avt-rapid-acquisition-for-rtp-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: Tue, 16 Jun 2009 20:49:05 -0000

Ali,
>From figure 2 and the text that follows

" A Retransmission Source may equally act as a Burst Source.  The
   Retransmission Source may also incorporate the Feedback Target
   ([I-D.ietf-avt-rtcpssm] permits the feedback target to be a
   retransmission server, since it is a logical function to which RRs
   send their unicast feedback), and we will use the term Retransmission
   Server (RS) in the remainder of the document to refer to a single
   physical entity comprising these three entities that share state.
   Note that the same method (with the identical message flows) would
   also apply in a scenario where rapid acquisition is performed by a
   feedback target co-located with the media source."

I assumed that we are only dealing with the case that the RS is a single
entity and not three different entities with different addresses

I also thought that this was agreed in previous discussions

If my understanding is not correct I will review the draft since the current
text is not explicit enough to specify which part is doing each message. I
saw that RAMS-R is going to feedback target but RAMS-T is going to RS which
is not specifying a specific address according to you.

Roni

-----Original Message-----
From: Ali C. Begen (abegen) [mailto:abegen@cisco.com] 
Sent: Tuesday, June 16, 2009 10:00 PM
To: Roni Even; avt@ietf.org
Subject: RE: [AVT] comments on section 10
ofdraft-ietf-avt-rapid-acquisition-for-rtp-01

Remember that the RAMS-R (RR->RS) message is NOT on the retransmission
(unicast) session, it's on the primary session since it is sent to the
feedback target of the primary SSM session. Thus, the source port RR uses to
send RAMS-R "cannot" be assumed to be the destination port it wishes to
receive the unicast burst on.

If you agree with this statement, it is clear why we need port signaling.
Muxing will not help much here. It will just reduce the number of signaled
ports from 2 to 1.

-acbegen


> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Roni
Even
> Sent: Tuesday, June 16, 2009 10:08 AM
> To: avt@ietf.org
> Subject: [AVT] comments on section 10
ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> 
> Hi,
> 
> I looked at section 10 and have some comments
> 
> 
> 
> 1.       If RTP/RTCP multiplexing is used, there is no need for any
specific operation
> from the RR side. The RR sends the RAMS-R message to the RS from the port
it wants to
> receive the RAMS-I and RTP payload. The RS just sends the information to
the port from
> which it received the RAMS-R and not to the one in the SDP
> 
> 2.       In the case where there is no RTP/RTCP multiplexing, the RAMS-R
RTCP message will
> go to the RS and the RAMS-I will go to the port on the RR from where the
RAMS-R was
> received. For the RTP, the RR does not know if it has a NAT on the way to
the RS and
> should try to get a routable address (using STUN for example) and
providing the port to
> the RS ( we still need to agree on how to do it)
> 
> 3.       If the above two points are correct than the RR receive port in
the SDP is not
> really useful
> 
> 
> 
> Roni Even


From md.1@newtbt.com  Tue Jun 16 13:49:56 2009
Return-Path: <md.1@newtbt.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 7FD023A6C41 for <avt@core3.amsl.com>; Tue, 16 Jun 2009 13:49:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[AWL=-0.698,  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 c2kOFhVG+Rbe for <avt@core3.amsl.com>; Tue, 16 Jun 2009 13:49:53 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 024F63A690C for <avt@ietf.org>; Tue, 16 Jun 2009 13:49:49 -0700 (PDT)
Received: from TBT-Laptop.newtbt.com (ppp-69-237-184-11.dsl.sndg02.pacbell.net [69.237.184.11]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1MGfai3tWQ-000d7b; Tue, 16 Jun 2009 16:49:16 -0400
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 16 Jun 2009 13:27:53 -0700
To: avt@ietf.org
From: Michael A Dolan <md.1@newtbt.com>
In-Reply-To: <C0A963AC-4B17-49FC-904C-44A43DF0B8D7@csperkins.org>
References: <20090309171502.518513A6359@core3.amsl.com> <4A6ACB13-0CBB-4DA7-84AD-28CDE56DB4C3@csperkins.org> <0MKpCa-1LoLs525qX-000cvA@mrelay.perfora.net> <49D1C793.9050409@hhi.fraunhofer.de> <0MKp8S-1Lof8c1LTC-000fjs@mrelay.perfora.net> <49D4AE9D.8060905@hhi.fraunhofer.de> <0MKpCa-1MEnZO1ysE-000d6S@mrelay.perfora.net> <4A323DC5.5020004@hhi.fraunhofer.de> <0MKpCa-1MGbjS2vGp-000cit@mrelay.perfora.net> <C0A963AC-4B17-49FC-904C-44A43DF0B8D7@csperkins.org>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_513762156==.ALT"
Message-Id: <0MKpCa-1MGfai3tWQ-000d7b@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX19bqpOtj669rXrDOH6O2YblMNtxYXrJ+bz93yu KT8KIWTuu3ZUBxOZIImlMuqvoyX04XtbvBrl5iC135CrdXzcbr xGLARhPMDKe4djINLAe2Q==
Subject: Re: [AVT] Fwd: I-D  Action:draft-perkins-avt-rapid-rtp-sync-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: Tue, 16 Jun 2009 20:49:56 -0000

--=====================_513762156==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

Colin-

FYI, I started out in March with a number of comments, some related 
to multicast UDLR with 1-2 links and I sense that's too big a topic 
to try and add at this point.  My comments therefore have distilled 
to addressing two major factors in syncing RTP sessions that I 
believe overshadow the time resolutions being discussed in the draft, 
and therefore it is an omission not to address them:

1. Common timebase
2. Media-specific access points

I stopped short of suggesting we should design anything. Therefore I 
still believe both topics belong here, and in this draft, and they 
are not so big as to defer at this point.

For clarification, I wasn't proposing we define a timebase signaling 
mechanism (although I do think that's a good idea).  All I am 
proposing is to add some text that explains that a common timebase is 
needed to achieve anything near the implied sync times discussed in 
this draft. How the senders and receivers figure that out is out of 
band. But if they don't and just go along with "wallclock", it makes 
much of the rest of this draft irrelevant since the timebase error 
will be huge by comparison.

Regarding the issue about access points, I'm not sure how much 
background to add, so apologies if this is obvious to everyone. Every 
media stream type has "access points" that arrive periodically - the 
point where a decoder can begin to decode the stream. In general, 
these are a function of the encoding, not constant per type, and not 
constant per stream. For example in H.264, these typically center 
around the presence of an IDR frame.  HE AAC has a simpler coding 
structure, but one still can't start decoding anywhere in the 
stream.  The "typical" periods of the H.264 access points range from 
0.5 to 2 seconds, depending on the coding.  The exact period is 
application dependent, but is not relevant.  The point is that these 
periods greatly exceed the times shown in the tables which are 
implied to be the sync times - going as low as 0.04 seconds.  The 
tables in this draft suggesting that RTCP SR packets be sent 0.04 
seconds apart for high rate streams. This is interesting (as Thomas 
notes) for jitter management and clock settling, but that high rate 
does not help you sync since you can't even start decoding the video 
for a relatively long time after the 0.04 seconds. This is mostly 
related to issues of late joiners of course.  Therefore, I was 
suggesting we make note of this fact to clarify there are other 
factors to sync and acquisition beyond receipt of NTP and the RTCP SR 
packet, and that these other times far exceed 0.04 seconds.

Co-locating in time the RTCP SR packets with their related access 
points further improves the sync time.  For example, if the IDR is 
every 2 seconds, there is no benefit (for syncing) to sending the 
RTCP SR more frequently than that, especially if it is aligned with 
this access point in time.  If the RTCP SR packets are sent randomly 
in time, the sync time is the IDR period plus 1/2 the RTCP SR packet 
period, on average. This is more of an optimization, but then, that's 
what this whole draft is about - optimizing the sync time.

I believe the text to address the above is minor, does not alter the 
core design, and will improve the sync time.

Regards,

         Mike

At 08:23 PM 6/16/2009 +0100, Colin Perkins wrote:
>Michael,
>
>On 16 Jun 2009, at 17:37, Michael A Dolan wrote:
>>I decided to reply to the earlier email/draft so we have the thread 
>>context since the comments apply to both that draft and the one 
>>posted the other day. Sorry for any confusion.
>>
>>I think you might misunderstand my comment about the timebase.  I 
>>am not proposing you force applications to use any specific 
>>timebase.  I am proposing that senders and receivers have to agree 
>>(implicitly since it cannot be signaled) what timebase is being 
>>used in specific NTPv4 terms.  "wallclock" is ambiguous, but more 
>>importantly will not result in the improved sync time you desire 
>>without such an out of band agreement.
>
>To the extent that you can perform synchronisation given the 
>ambiguity about the timebase, the mechanisms specified in our draft 
>will improve synchronisation times. Signalling additional details on 
>the clocks and timebase will also help synchronisation, clearly, but 
>is an orthogonal issue (and might be something for MMUSIC to 
>consider, rather than AVT, since it's primarily a signalling problem).
>
>>Regarding the relationship to the media stream access points, again 
>>there may be a misunderstanding.  I did not propose faster RTCP SR 
>>records be forbidden, or even discouraged.  I am proposing 
>>clarifying text explaining the important sync-related relationship 
>>that would change one's interpretation of the tables and desired 
>>RTCP SR frequency.  I believe the tables are misleading where they 
>>imply actual sync times remotely near 0.04 seconds.
>
>I'm not sure I see the problem here - can you clarify?
>
>>Since I am only proposing (albeit important in my opinion) 
>>clarifying material and am not actually opposing what is there now; 
>>and I am willing to craft specific text changes (your option); I am 
>>not sure I understand the offhand rejection of the comments.
>>
>>Based on offline emails with you and the chair, I understood this 
>>work to be THE authority on rapid sync of RTP sessions.  Maybe I 
>>misunderstood and its scope is more narrow than that. If that's the 
>>case, then perhaps we can narrow the scope of the work and I'll 
>>author another draft on RTP sync. But I think the proposed changes 
>>are relatively minor in the grand scheme of things and hope you 
>>will consider addressing them in this draft.
>
>If there is an issue with timing of media access points affecting 
>the synchronisation latency, then that fits with the discussion in 
>our draft. However, I think signalling to define the timebase for 
>synchronisation is a broader problem, separate to the additional 
>mechanisms we define, and would be better suited to a separate draft.
>
>Cheers,
>Colin
>
>
>
>>Regards,
>>
>>         Mike
>>
>>At 01:36 PM 6/12/2009 +0200, Thomas Schierl wrote:
>>>Hi Michael,
>>>
>>>I guess your comments are related to 
>>>draft-ietf-avt-rapid-rtp-sync-02.txt. Please find my comments in line.
>>>
>>>Thomas
>>>
>>>Michael A Dolan wrote:
>>>>Thomas and all-
>>>>
>>>>Continuing this in the context of yesterday's WG draft -02:
>>>>
>>>>1. The draft still uses "wallclock".  I believe what's important 
>>>>is that the NTP reference clock must have the same reference_ID 
>>>>value as the clock used in the RTCP SR records. It's not 
>>>>important that it be "wallclock" (or more precisely, one of the 
>>>>values defined in NTPv4).  It can be PPS or something else. The 
>>>>draft does mention that a common clock should be used.  The 
>>>>problem I see is that the language is imprecise WRT NTPv4 
>>>>terminology and implies a vague subset of timebases by using the 
>>>>term, "wallclock". Further, when the hdr ext for NTP is not used, 
>>>>it should be stated that the NTP timebase reference_ID must be 
>>>>agreed to out of band between the senders and receivers.
>>>
>>>See my original comments attached to your message. I think we do 
>>>not want to make any additional requirements on the clock to be 
>>>used for generating the wallclock, i.e. we will keep the 
>>>definitions in RFC 3550 for backward compatibility reasons.
>>>
>>>>
>>>>2. Sync can only occur when the receiver has not only NTP and 
>>>>RTCP SR packets, but also a point in every RTP session where 
>>>>there is an "access point" for that media stream.  Since these 
>>>>access points are customarily considerably further apart than 
>>>>0.04 seconds, the tables are a bit misleading on the practical 
>>>>sync time and recommended RTCP SR emission frequency.  It should 
>>>>be noted around all the tables that there is no benefit to 
>>>>sending the RTCP SR record more often than the media access point 
>>>>frequency, especially in combination with the next comment below.
>>>
>>>Sure, there is typically a need for a random access point to start 
>>>decoding. So on the first glance it makes sense to send SRs not 
>>>with a higher frequency than random access points. But there may 
>>>be a benefit to send SRs more frequently, e.g., to estimate clock skews.
>>>
>>>>
>>>>3. It should be recommended that RTCP SR packets be sent near, 
>>>>and immediately following, media access points (subject to the 5% 
>>>>boundary). Doing so will greatly improve the sync time rather 
>>>>than relying on more frequent, and/or randomly timed, RTCP SR packets.
>>>
>>>Generally, it should not be a problem to slightly delay RTCP 
>>>packets in order to align with media random access points, but 
>>>this would need further analysis to document the acceptable 
>>>bounds. I guess this would require more time and would further 
>>>delay the intended solution for layered codecs. In order to not 
>>>further delay the solution in this draft, this could become a 
>>>topic of another draft.
>>>
>>>>
>>>>Comment #1 becomes even more important the faster you want to 
>>>>sync.  If the RTP sessions are using GPS and the NTP source is 
>>>>using UTC (both "wallclock"), there will be errors measured in 
>>>>seconds.  This disparity is less likely when the hdr ext is used, 
>>>>of course. But in the general case, this language needs 
>>>>tightening up to remove the clock errors.
>>>>
>>>>Comments 2 & 3, although true in all scenarios, become more 
>>>>relevant in SSM with late joiners.
>>>>
>>>>I hope the above comments are clearer than my attempts 
>>>>below.  I'm happy to suggest specific edits to the draft if that will help.
>>>>
>>>>Regards,
>>>>
>>>>         Mike
>>>>
>>>>At 02:25 PM 4/2/2009 +0200, 
>>>><mailto:Thomas.Schierl@hhi.fraunhofer.de>Thomas.Schierl@hhi.fraunhofer.de 
>>>>wrote:
>>>>>Hi Michael,
>>>>>
>>>>>What I can see from the ATSC M/H Transport spec is that there 
>>>>>are requirements on encoder and decoder clock precisions, which 
>>>>>for sure give a complete different environment than assumed by 
>>>>>RFC3550 with respect to the clock precision. If we could assure 
>>>>>such clocks for all devices which may potentially encode and 
>>>>>stream layered media via multi session transmission, the problem 
>>>>>would have been solved anyway. But that is not the case, as I 
>>>>>tried to show by pointing to some of the relevant discussions on 
>>>>>the mailing list.
>>>>>
>>>>>About your second point: RTP does not require NTP to be used as 
>>>>>wallclock. In RTP, there is much more freedom in selecting the 
>>>>>source for this clock. RTP uses the NTP timestamp format just 
>>>>>for indicating the wallclock in the RTCP sender reports. 
>>>>>Furthermore draft-perkins-avt-rapid-rtp-sync-03 does only 
>>>>>require to use the same wallclock as used for the SRs also for 
>>>>>the wallclock timestamps in the header extensions.
>>>>>
>>>>>Another interesting point is that the ATSC Transport spec is not 
>>>>>mentioning SVC while mentioning AVC and AAC. If looking at the 
>>>>>ATSC Video Systems spec. 
>>>>>(<http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-136r7-A153-Part-7-Video-System.pdf> 
>>>>>S4-136r7-A153-Part-7-Video-System), there is a solution which 
>>>>>requires RTP timestamp synchronization for "SVC Transport in Two 
>>>>>RTP Sessions". This for sure solves the clock skew problem, but 
>>>>>as discussed in AVT, this is not a general solution and has 
>>>>>different implications if applied to all use cases of RTP multi 
>>>>>session transmission as, e.g. conversational services. Therefore 
>>>>>we now have a solution which seems to be agreeable by the group, 
>>>>>which solves the problem and is more in line with RFC 3550, i.e. 
>>>>>using the wallclock for the data alignment between the session.
>>>>>
>>>>>Best regards,
>>>>>Thomas
>>>>>
>>>>>
>>>>>Michael A Dolan wrote:
>>>>>>Hi Thomas-
>>>>>>
>>>>>>Thanks.  Yes, I am familiar with the discussion.
>>>>>>
>>>>>>I'm not necessarily pushing the ATSC solution, but offering 
>>>>>>some points to consider, which apply equally to the problem at 
>>>>>>hand here, I think.
>>>>>>
>>>>>>Also, it is important to note some more things about the ATSC text:
>>>>>>
>>>>>>1. The language in the specification very carefully recommends 
>>>>>>the clock precision without requiring it.  It is expected to 
>>>>>>work over routers with jitter and delays and with media 
>>>>>>components from outside the broadcast facility. The difference 
>>>>>>is that the client is expected to be able to perform tight sync 
>>>>>>when the servers are able to provide the recommended timing 
>>>>>>model (encoding one hop away, etc).  It gracefully degrades to 
>>>>>>"Internet" timing model quality.
>>>>>>
>>>>>>2. The clock, although "NTP" syntax, is not time of day (e.g. 
>>>>>>reference_ID= "GPS"), but "PPS", thus allowing the components 
>>>>>>to be encoded and decoded without concern for end-to-end 
>>>>>>delivery delay.  This only works when NTP is explicitly 
>>>>>>signaled as part of the encoding and both components share a 
>>>>>>clock (same or closely coupled encoders). So it will not work 
>>>>>>in the general case.  But there are many systems where it will 
>>>>>>and perhaps consideration should be given to permitting 
>>>>>>non-"wall clock" timebases.
>>>>>>
>>>>>>The NTP hdr ext here is an encoding optimization that indeed 
>>>>>>has some other good properties.  Although the draft ties the 
>>>>>>NTP timestamp back to the RTCP SR records, the timebase is not 
>>>>>>explicitly defined (which is also true of RTCP SR).  Some 
>>>>>>reference_ID value must be assumed and there is enough delta 
>>>>>>between, for example, GPS and UTC, timebases to cause things to 
>>>>>>break if the entire system is not implicitly assumed to be only 
>>>>>>one timebase. For example, without an explicit reference_ID, 
>>>>>>how could one use other timebases defined in NTPv4?  This is a 
>>>>>>broader issue than the hdr ext syntax, but since we're 
>>>>>>discussing NTP, I thought I'd bring it up.
>>>>>>
>>>>>>I think the above and the other points below are relevant here 
>>>>>>and not inconsistent with the RTCP SR methods. The fact that 
>>>>>>the ATSC design *can* be more precise is not alone cause to 
>>>>>>discard the techniques developed there.
>>>>>>
>>>>>>Regards,
>>>>>>
>>>>>>          Mike
>>>>>>
>>>>>>At 09:34 AM 3/31/2009 +0200, 
>>>>>><mailto:Thomas.Schierl@hhi.fraunhofer.de>Thomas.Schierl@hhi.fraunhofer.de 
>>>>>>wrote:
>>>>>>>Dear Michael,
>>>>>>>
>>>>>>>Thanks for the comments and the reference to the ATSC M/H.
>>>>>>>
>>>>>>>I guess, what we are looking for in AVT is a solution which 
>>>>>>>also works for encoders having non-perfect clocks. There was a 
>>>>>>>long discussion on the list, here are two pointers:
>>>>>>>
>>>>>>><http://www.ietf.org/mail-archive/web/avt/current/msg09144.html>http://www.ietf.org/mail-archive/web/avt/current/msg09144.html
>>>>>>>http://www.ietf.org/mail-archive/web/avt/current/msg10491.html
>>>>>>>
>>>>>>>ATSC surely can assume to have a perfect clock in the NTP 
>>>>>>>streams, which will not be the case on PC systems that may be 
>>>>>>>used as an encoder for multi session transmission of a layered 
>>>>>>>codec. This is one major problem we intended to solve with the 
>>>>>>>header extension while keeping the whole approach as close as 
>>>>>>>possible in line with the existing RTCP SR method.
>>>>>>>
>>>>>>>
>>>>>>>Best regards,
>>>>>>>Thomas
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>______________________________________________
>>>>>>>Thomas Schierl, Dipl.-Ing.
>>>>>>>Fraunhofer HHI
>>>>>>>Senior Research Engineer
>>>>>>>Image Processing Dept. / Multimedia Transport
>>>>>>>Einsteinufer 37, 10587 Berlin, Germany
>>>>>>>PHONE: +49 30 31002 227 , FAX: +49 30 392 7200
>>>>>>>WEB: <http://ip.hhi.de/>http://ip.hhi.de , SKYPE: thomas.schierl
>>>>>>>EMAIL: 
>>>>>>><mailto:thomas.schierl@hhi.fraunhofer.de>thomas.schierl@hhi.fraunhofer.de
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>Michael A Dolan wrote:
>>>>>>>>Those interested in this topic may also find this interesting:
>>>>>>>>
>>>>>>>><http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-132r13-A153-Part-3-Transport.pdf>http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-132r13-A153-Part-3-Transport.pdf 
>>>>>>>>
>>>>>>>>
>>>>>>>>Section 10.3.
>>>>>>>>
>>>>>>>>Some differences are:
>>>>>>>>
>>>>>>>>1. There is one NTP packet stream per service, rather than 
>>>>>>>>the encoding optimization in the hdr ext;
>>>>>>>>2. RTCP SR records are emitted "near" video random access 
>>>>>>>>points, rather than on a prescribed time schedule; and
>>>>>>>>3. The above works in multicast-only, UDLR networks (e.g. 
>>>>>>>>television broadcast), rather than requiring a 2-way link.
>>>>>>>>
>>>>>>>>#2 is interesting since in order to begin a *synchronized* 
>>>>>>>>decode (video + audio properly correlated), a client must have acquired all of:
>>>>>>>>a. NTP
>>>>>>>>b. RTCP SR for each component
>>>>>>>>c. video reference frame and decoding metadata (i.e. a random 
>>>>>>>>access point)
>>>>>>>>d. audio frame
>>>>>>>>
>>>>>>>>So, the relative timing of the RTCP SR records to the RTP 
>>>>>>>>stream content is perhaps more important than the emission 
>>>>>>>>period.  Having the RTCP SR records arrive faster than the 
>>>>>>>>video reference frames doesn't help of course.  And even if 
>>>>>>>>they are "fast enough", having them arrive out of sync with 
>>>>>>>>the reference frames delays the service acquisition by half 
>>>>>>>>the period on average.
>>>>>>>>
>>>>>>>>Bandwidth utilization (how many bits to devote to RTCP and 
>>>>>>>>NTP) can arguably be more efficiently managed by the server 
>>>>>>>>in most cases, not individual client requests for faster RTCP 
>>>>>>>>SR packets. And, the client would have no knowledge of the 
>>>>>>>>intended (video) reference frame periods being used by the 
>>>>>>>>server, so it would not, in general, know what to ask for.
>>>>>>>>
>>>>>>>>In practice, won't a server that wants to enable faster 
>>>>>>>>acquisition and sync do things like the above?  I'm concerned 
>>>>>>>>that detailed requests from clients beyond "please use more 
>>>>>>>>bandwidth and enable fast sync" won't be as valuable as they 
>>>>>>>>seem since in the general case the client doesn't know what to ask for exactly.
>>>>>>>>
>>>>>>>>FYI, the above ATSC document is in a "candidate" state where 
>>>>>>>>public comments are solicited.  Independent of this thread, 
>>>>>>>>if anyone has comments on it, I could convey them back to the ATSC.
>>>>>>>>
>>>>>>>>Regards,
>>>>>>>>
>>>>>>>>         Mike
>>>>>>>>
>>>>>>>>At 07:43 PM 3/9/2009 +0000, Colin Perkins wrote:
>>>>>>>>>The changes in this version are primarily editorial; we're aware that
>>>>>>>>>not all the open issues have been addressed yet. Any further comments
>>>>>>>>>are welcomed.
>>>>>>>>>
>>>>>>>>>Chairs: we'd like this to be considered as an AVT working group
>>>>>>>>>draft, as indicated privately.
>>>>>>>>>
>>>>>>>>>Cheers,
>>>>>>>>>Colin
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>Begin forwarded message:
>>>>>>>>>>From: <mailto:Internet-Drafts@ietf.org>Internet-Drafts@ietf.org
>>>>>>>>>>Date: 9 March 2009 17:15:02 GMT
>>>>>>>>>>To: <mailto:i-d-announce@ietf.org>i-d-announce@ietf.org
>>>>>>>>>>Subject: I-D Action:draft-perkins-avt-rapid-rtp-sync-03.txt
>>>>>>>>>>Reply-To: <mailto:internet-drafts@ietf.org>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-03.txt
>>>>>>>>>>         Pages           : 17
>>>>>>>>>>         Date            : 2009-03-09
>>>>>>>>>>
>>>>>>>>>>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>http://www.ietf.org/internet-drafts/draft-perkins-avt-rapid-rtp- 
>>>>>>>>>>sync-03.txt
>>>>>>>>>>
>>>>>>>>>>Internet-Drafts are also available by anonymous FTP at:
>>>>>>>>>><ftp://ftp.ietf.org/internet-drafts/>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.
>>>>>>>>>>Content-Type: text/plain
>>>>>>>>>>Content-ID: 
>>>>>>>>>><mailto:2009-03-09100610.I-D@ietf.org><2009-03-09100610.I-D@ietf.org>
>>>>>>>>>>
>>>>>>>>>>_______________________________________________
>>>>>>>>>>I-D-Announce mailing list
>>>>>>>>>><mailto:I-D-Announce@ietf.org>I-D-Announce@ietf.org
>>>>>>>>>>https://www.ietf.org/mailman/listinfo/i-d-announce
>>>>>>>>>>Internet-Draft directories: 
>>>>>>>>>><http://www.ietf.org/shadow.html>http://www.ietf.org/shadow.html
>>>>>>>>>>or 
>>>>>>>>>><ftp://ftp.ietf.org/ietf/1shadow-sites.txt>ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>>>>>>>
>>>>>>>>>_______________________________________________
>>>>>>>>>Audio/Video Transport Working Group
>>>>>>>>><mailto:avt@ietf.org>avt@ietf.org
>>>>>>>>>https://www.ietf.org/mailman/listinfo/avt
>>>>>>>>
>>>>>>>>_______________________________________________
>>>>>>>>Audio/Video Transport Working Group
>>>>>>>><mailto:avt@ietf.org>avt@ietf.org
>>>>>>>>https://www.ietf.org/mailman/listinfo/avt
>>>>>>>
>>>>>>>---
>>>>>>>Visit us at
>>>>>>>
>>>>>>>Web 2.0 Expo / March 31 - April 03 / San Francisco, California 
>>>>>>>/ Booth 415
>>>>>>><http://www.web2expo.com/webexsf2009>http://www.web2expo.com/webexsf2009
>>>>>>>
>>>>>>>NAB SHOW 2009 / April 18-23 / Las Vegas, Nevada USA / South 
>>>>>>>Hall (Upper), Booth SU9624F
>>>>>>><http://www.nabshow.com/>http://www.nabshow.com/
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>_______________________________________________
>>>>>>Audio/Video Transport Working Group
>>>>>><mailto:avt@ietf.org>avt@ietf.org
>>>>>>
>>>>>>
>>>>>>https://www.ietf.org/mailman/listinfo/avt
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>----
>>>>>Visit us at
>>>>>
>>>>>Web 2.0 Expo / March 31 - April 03 / San Francisco, California / Booth 415
>>>>><http://www.web2expo.com/webexsf2009>http://www.web2expo.com/webexsf2009
>>>>>
>>>>>NAB SHOW 2009 / April 18-23 / Las Vegas, Nevada USA / South Hall 
>>>>>(Upper), Booth SU9624F
>>>>><http://www.nabshow.com/>http://www.nabshow.com/
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>_______________________________________________
>>>>Audio/Video Transport Working Group
>>>><mailto:avt@ietf.org>avt@ietf.org
>>>>
>>>>https://www.ietf.org/mailman/listinfo/avt
>>>>
>>>
>>>
>>>----
>>>Visit us at
>>>
>>>IEEE ICC 2009 / June 14-18 / Dresden, Germany / International 
>>>Congress Center
>>><http://www.comsoc.org/confs/icc/2009/>http://www.comsoc.org/confs/icc/2009/
>>>
>>>Laser World of Photonics 2009 / June 15-18 / Munich, Germay / Hall 
>>>B1, Booth 461
>>><http://world-of-photonics.net/de/laser/start>http://world-of-photonics.net/de/laser/start
>>_______________________________________________
>>Audio/Video Transport Working Group
>><mailto:avt@ietf.org>avt@ietf.org
>>https://www.ietf.org/mailman/listinfo/avt
>
>
>
>--
>Colin Perkins
><http://csperkins.org/>http://csperkins.org/
>

--=====================_513762156==.ALT
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<body>
Colin-<br><br>
FYI, I started out in March with a number of comments, some related to
multicast UDLR with 1-2 links and I sense that's too big a topic to try
and add at this point.&nbsp; My comments therefore have distilled to
addressing two major factors in syncing RTP sessions that I believe
overshadow the time resolutions being discussed in the draft, and
therefore it is an omission not to address them:<br><br>
1. Common timebase<br>
2. Media-specific access points<br><br>
I stopped short of suggesting we should design anything. Therefore I
still believe both topics belong here, and in this draft, and they are
not so big as to defer at this point.<br><br>
For clarification, I wasn't proposing we define a timebase signaling
mechanism (although I do think that's a good idea).&nbsp; All I am
proposing is to add some text that explains that a common timebase is
needed to achieve anything near the implied sync times discussed in this
draft. How the senders and receivers figure that out is out of band. But
if they don't and just go along with &quot;wallclock&quot;, it makes much
of the rest of this draft irrelevant since the timebase error will be
huge by comparison.<br><br>
Regarding the issue about access points, I'm not sure how much background
to add, so apologies if this is obvious to everyone. Every media stream
type has &quot;access points&quot; that arrive periodically - the point
where a decoder can begin to decode the stream. In general, these are a
function of the encoding, not constant per type, and not constant per
stream. For example in H.264, these typically center around the presence
of an IDR frame.&nbsp; HE AAC has a simpler coding structure, but one
still can't start decoding anywhere in the stream.&nbsp; The
&quot;typical&quot; periods of the H.264 access points range from 0.5 to
2 seconds, depending on the coding.&nbsp; The exact period is application
dependent, but is not relevant.&nbsp; The point is that these periods
greatly exceed the times shown in the tables which are implied to be the
sync times - going as low as 0.04 seconds.&nbsp; The tables in this draft
suggesting that RTCP SR packets be sent 0.04 seconds apart for high rate
streams. This is interesting (as Thomas notes) for jitter management and
clock settling, but that high rate does not help you sync since you can't
even start decoding the video for a relatively long time after the 0.04
seconds. This is mostly related to issues of late joiners of
course.&nbsp; Therefore, I was suggesting we make note of this fact to
clarify there are other factors to sync and acquisition beyond receipt of
NTP and the RTCP SR packet, and that these other times far exceed 0.04
seconds.<br><br>
Co-locating in time the RTCP SR packets with their related access points
further improves the sync time.&nbsp; For example, if the IDR is every 2
seconds, there is no benefit (for syncing) to sending the RTCP SR more
frequently than that, especially if it is aligned with this access point
in time.&nbsp; If the RTCP SR packets are sent randomly in time, the sync
time is the IDR period plus 1/2 the RTCP SR packet period, on average.
This is more of an optimization, but then, that's what this whole draft
is about - optimizing the sync time.<br><br>
I believe the text to address the above is minor, does not alter the core
design, and will improve the sync time.<br><br>
Regards,<br><br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Mike<br>
<br>
At 08:23 PM 6/16/2009 +0100, Colin Perkins wrote:<br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Michael,<br><br>
On 16 Jun 2009, at 17:37, Michael A Dolan wrote:<br>
<blockquote type=3Dcite class=3Dcite cite=3D"">I decided to reply to the
earlier email/draft so we have the thread context since the comments
apply to both that draft and the one posted the other day. Sorry for any
confusion.<br><br>
I think you might misunderstand my comment about the timebase.&nbsp; I am
not proposing you force applications to use any specific timebase.&nbsp;
I am proposing that senders and receivers have to agree (implicitly since
it cannot be signaled) what timebase is being used in specific NTPv4
terms.&nbsp; &quot;wallclock&quot; is ambiguous, but more importantly
will not result in the improved sync time you desire without such an out
of band agreement.</blockquote><br>
To the extent that you can perform synchronisation given the ambiguity
about the timebase, the mechanisms specified in our draft will improve
synchronisation times. Signalling additional details on the clocks and
timebase will also help synchronisation, clearly, but is an orthogonal
issue (and might be something for MMUSIC to consider, rather than AVT,
since it's primarily a signalling problem). <br><br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Regarding the relationship to
the media stream access points, again there may be a
misunderstanding.&nbsp; I did not propose faster RTCP SR records be
forbidden, or even discouraged.&nbsp; I am proposing clarifying text
explaining the important sync-related relationship that would change
one's interpretation of the tables and desired RTCP SR frequency.&nbsp; I
believe the tables are misleading where they imply actual sync times
remotely near 0.04 seconds.</blockquote><br>
I'm not sure I see the problem here - can you clarify?<br><br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Since I am only proposing
(albeit important in my opinion) clarifying material and am not actually
opposing what is there now; and I am willing to craft specific text
changes (your option); I am not sure I understand the offhand rejection
of the comments.<br><br>
Based on offline emails with you and the chair, I understood this work to
be THE authority on rapid sync of RTP sessions.&nbsp; Maybe I
misunderstood and its scope is more narrow than that. If that's the case,
then perhaps we can narrow the scope of the work and I'll author another
draft on RTP sync. But I think the proposed changes are relatively minor
in the grand scheme of things and hope you will consider addressing them
in this draft.</blockquote><br>
If there is an issue with timing of media access points affecting the
synchronisation latency, then that fits with the discussion in our draft.
However, I think signalling to define the timebase for synchronisation is
a broader problem, separate to the additional mechanisms we define, and
would be better suited to a separate draft.<br><br>
Cheers,<br>
Colin<br><br>
<br><br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Regards,<br><br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Mike<br>
<br>
At 01:36 PM 6/12/2009 +0200, Thomas Schierl wrote:<br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Hi Michael,<br><br>
I guess your comments are related to
draft-ietf-avt-rapid-rtp-sync-02.txt. Please find my comments in
line.<br><br>
Thomas<br><br>
Michael A Dolan wrote: <br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Thomas and all-<br><br>
Continuing this in the context of yesterday's WG draft -02:<br><br>
1. The draft still uses &quot;wallclock&quot;.&nbsp; I believe what's
important is that the NTP reference clock must have the same reference_ID
value as the clock used in the RTCP SR records. It's not important that
it be &quot;wallclock&quot; (or more precisely, one of the values defined
in NTPv4).&nbsp; It can be PPS or something else. The draft does mention
that a common clock should be used.&nbsp; The problem I see is that the
language is imprecise WRT NTPv4 terminology and implies a vague subset of
timebases by using the term, &quot;wallclock&quot;. Further, when the hdr
ext for NTP is not used, it should be stated that the NTP timebase
reference_ID must be agreed to out of band between the senders and
receivers.</blockquote><br>
See my original comments attached to your message. I think we do not want
to make any additional requirements on the clock to be used for
generating the wallclock, i.e. we will keep the definitions in RFC 3550
for backward compatibility reasons.<br><br>
<blockquote type=3Dcite class=3Dcite cite=3D""><br>
2. Sync can only occur when the receiver has not only NTP and RTCP SR
packets, but also a point in every RTP session where there is an
&quot;access point&quot; for that media stream.&nbsp; Since these access
points are customarily considerably further apart than 0.04 seconds, the
tables are a bit misleading on the practical sync time and recommended
RTCP SR emission frequency.&nbsp; It should be noted around all the
tables that there is no benefit to sending the RTCP SR record more often
than the media access point frequency, especially in combination with the
next comment below.</blockquote><br>
Sure, there is typically a need for a random access point to start
decoding. So on the first glance it makes sense to send SRs not with a
higher frequency than random access points. But there may be a benefit to
send SRs more frequently, e.g., to estimate clock skews.<br><br>
<blockquote type=3Dcite class=3Dcite cite=3D""><br>
3. It should be recommended that RTCP SR packets be sent near, and
immediately following, media access points (subject to the 5% boundary).
Doing so will greatly improve the sync time rather than relying on more
frequent, and/or randomly timed, RTCP SR packets.</blockquote><br>
Generally, it should not be a problem to slightly delay RTCP packets in
order to align with media random access points, but this would need
further analysis to document the acceptable bounds. I guess this would
require more time and would further delay the intended solution for
layered codecs. In order to not further delay the solution in this draft,
this could become a topic of another draft. <br><br>
<blockquote type=3Dcite class=3Dcite cite=3D""><br>
Comment #1 becomes even more important the faster you want to sync.&nbsp;
If the RTP sessions are using GPS and the NTP source is using UTC (both
&quot;wallclock&quot;), there will be errors measured in seconds.&nbsp;
This disparity is less likely when the hdr ext is used, of course. But in
the general case, this language needs tightening up to remove the clock
errors.<br><br>
Comments 2 &amp; 3, although true in all scenarios, become more relevant
in SSM with late joiners.<br><br>
I hope the above comments are clearer than my attempts below.&nbsp; I'm
happy to suggest specific edits to the draft if that will help.<br><br>
Regards,<br><br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Mike<br>
<br>
At 02:25 PM 4/2/2009 +0200,
<a href=3D"mailto:Thomas.Schierl@hhi.fraunhofer.de">
Thomas.Schierl@hhi.fraunhofer.de</a> wrote:<br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Hi Michael,<br><br>
What I can see from the ATSC M/H Transport spec is that there are
requirements on encoder and decoder clock precisions, which for sure give
a complete different environment than assumed by RFC3550 with respect to
the clock precision. If we could assure such clocks for all devices which
may potentially encode and stream layered media via multi session
transmission, the problem would have been solved anyway. But that is not
the case, as I tried to show by pointing to some of the relevant
discussions on the mailing list.<br><br>
About your second point: RTP does not require NTP to be used as
wallclock. In RTP, there is much more freedom in selecting the source for
this clock. RTP uses the NTP timestamp format just for indicating the
wallclock in the RTCP sender reports. Furthermore
draft-perkins-avt-rapid-rtp-sync-03 does only require to use the same
wallclock as used for the SRs also for the wallclock timestamps in the
header extensions.<br><br>
Another interesting point is that the ATSC Transport spec is not
mentioning SVC while mentioning AVC and AAC. If looking at the ATSC Video
Systems spec.
(<a href=3D"http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-13=
6r7-A153-Part-7-Video-System.pdf">
 S4-136r7-A153-Part-7-Video-System</a>), there is a solution which
requires RTP timestamp synchronization for &quot;SVC Transport in Two RTP
Sessions&quot;. This for sure solves the clock skew problem, but as
discussed in AVT, this is not a general solution and has different
implications if applied to all use cases of RTP multi session
transmission as, e.g. conversational services. Therefore we now have a
solution which seems to be agreeable by the group, which solves the
problem and is more in line with RFC 3550, i.e. using the wallclock for
the data alignment between the session.<br><br>
Best regards,<br>
Thomas<br><br>
<br>
Michael A Dolan wrote: <br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Hi Thomas-<br><br>
Thanks.&nbsp; Yes, I am familiar with the discussion.<br><br>
I'm not necessarily pushing the ATSC solution, but offering some points
to consider, which apply equally to the problem at hand here, I
think.<br><br>
Also, it is important to note some more things about the ATSC
text:<br><br>
1. The language in the specification very carefully recommends the clock
precision without requiring it.&nbsp; It is expected to work over routers
with jitter and delays and with media components from outside the
broadcast facility. The difference is that the client is expected to be
able to perform tight sync when the servers are able to provide the
recommended timing model (encoding one hop away, etc).&nbsp; It
gracefully degrades to &quot;Internet&quot; timing model
quality.<br><br>
2. The clock, although &quot;NTP&quot; syntax, is not time of day (e.g.
reference_ID=3D &quot;GPS&quot;), but &quot;PPS&quot;, thus allowing the
components to be encoded and decoded without concern for end-to-end
delivery delay.&nbsp; This only works when NTP is explicitly signaled as
part of the encoding and both components share a clock (same or closely
coupled encoders). So it will not work in the general case.&nbsp; But
there are many systems where it will and perhaps consideration should be
given to permitting non-&quot;wall clock&quot; timebases.<br><br>
The NTP hdr ext here is an encoding optimization that indeed has some
other good properties.&nbsp; Although the draft ties the NTP timestamp
back to the RTCP SR records, the timebase is not explicitly defined
(which is also true of RTCP SR).&nbsp; Some reference_ID value must be
assumed and there is enough delta between, for example, GPS and UTC,
timebases to cause things to break if the entire system is not implicitly
assumed to be only one timebase. For example, without an explicit
reference_ID, how could one use other timebases defined in NTPv4?&nbsp;
This is a broader issue than the hdr ext syntax, but since we're
discussing NTP, I thought I'd bring it up.<br><br>
I think the above and the other points below are relevant here and not
inconsistent with the RTCP SR methods. The fact that the ATSC design
*can* be more precise is not alone cause to discard the techniques
developed there.<br><br>
Regards,<br><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mike<br><br>
At 09:34 AM 3/31/2009 +0200,
<a href=3D"mailto:Thomas.Schierl@hhi.fraunhofer.de">
Thomas.Schierl@hhi.fraunhofer.de</a> wrote:<br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Dear Michael,<br><br>
Thanks for the comments and the reference to the ATSC M/H.<br><br>
I guess, what we are looking for in AVT is a solution which also works
for encoders having non-perfect clocks. There was a long discussion on
the list, here are two pointers:<br><br>
<a href=3D"http://www.ietf.org/mail-archive/web/avt/current/msg09144.html">
http://www.ietf.org/mail-archive/web/avt/current/msg09144.html</a><br>
<a href=3D"http://www.ietf.org/mail-archive/web/avt/current/msg10491.html" e=
udora=3D"autourl">
http://www.ietf.org/mail-archive/web/avt/current/msg10491.html</a><br><br>
ATSC surely can assume to have a perfect clock in the NTP streams, which
will not be the case on PC systems that may be used as an encoder for
multi session transmission of a layered codec. This is one major problem
we intended to solve with the header extension while keeping the whole
approach as close as possible in line with the existing RTCP SR
method.<br><br>
<br>
Best regards,<br>
Thomas<br><br>
<br><br>
______________________________________________<br>
Thomas Schierl, Dipl.-Ing.<br>
Fraunhofer HHI<br>
Senior Research Engineer<br>
Image Processing Dept. / Multimedia Transport<br>
Einsteinufer 37, 10587 Berlin, Germany<br>
PHONE: +49 30 31002 227 , FAX: +49 30 392 7200<br>
WEB: <a href=3D"http://ip.hhi.de/">http://ip.hhi.de</a> , SKYPE:
thomas.schierl<br>
EMAIL:
<a href=3D"mailto:thomas.schierl@hhi.fraunhofer.de">
thomas.schierl@hhi.fraunhofer.de</a><br><br>
<br><br>
Michael A Dolan wrote:<br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Those interested in this topi=
c
may also find this interesting:<br><br>
<a href=3D"http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-132=
r13-A153-Part-3-Transport.pdf">
http://www.atsc.org/standards/cs_documents/a153-2009-03-13/S4-132r13-A153-Pa=
rt-3-Transport.pdf</a>
 <br><br>
Section 10.3.<br><br>
Some differences are:<br><br>
1. There is one NTP packet stream per service, rather than the encoding
optimization in the hdr ext;<br>
2. RTCP SR records are emitted &quot;near&quot; video random access
points, rather than on a prescribed time schedule; and<br>
3. The above works in multicast-only, UDLR networks (e.g. television
broadcast), rather than requiring a 2-way link.<br><br>
#2 is interesting since in order to begin a *synchronized* decode (video
+ audio properly correlated), a client must have acquired all of:<br>
a. NTP<br>
b. RTCP SR for each component<br>
c. video reference frame and decoding metadata (i.e. a random access
point)<br>
d. audio frame<br><br>
So, the relative timing of the RTCP SR records to the RTP stream content
is perhaps more important than the emission period.&nbsp; Having the RTCP
SR records arrive faster than the video reference frames doesn't help of
course.&nbsp; And even if they are &quot;fast enough&quot;, having them
arrive out of sync with the reference frames delays the service
acquisition by half the period on average.<br><br>
Bandwidth utilization (how many bits to devote to RTCP and NTP) can
arguably be more efficiently managed by the server in most cases, not
individual client requests for faster RTCP SR packets. And, the client
would have no knowledge of the intended (video) reference frame periods
being used by the server, so it would not, in general, know what to ask
for.<br><br>
In practice, won't a server that wants to enable faster acquisition and
sync do things like the above?&nbsp; I'm concerned that detailed requests
from clients beyond &quot;please use more bandwidth and enable fast
sync&quot; won't be as valuable as they seem since in the general case
the client doesn't know what to ask for exactly.<br><br>
FYI, the above ATSC document is in a &quot;candidate&quot; state where
public comments are solicited.&nbsp; Independent of this thread, if
anyone has comments on it, I could convey them back to the ATSC.<br><br>
Regards,<br><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mike<br><br>
At 07:43 PM 3/9/2009 +0000, Colin Perkins wrote:<br>
<blockquote type=3Dcite class=3Dcite cite=3D"">The changes in this version a=
re
primarily editorial; we're aware that<br>
not all the open issues have been addressed yet. Any further
comments<br>
are welcomed.<br><br>
Chairs: we'd like this to be considered as an AVT working group<br>
draft, as indicated privately.<br><br>
Cheers,<br>
Colin<br><br>
<br><br>
<br>
Begin forwarded message:<br>
<blockquote type=3Dcite class=3Dcite cite=3D"">From:
<a href=3D"mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a><br>
Date: 9 March 2009 17:15:02 GMT<br>
To: <a href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a><br>
Subject: I-D Action:draft-perkins-avt-rapid-rtp-sync-03.txt<br>
Reply-To:
<a href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a><br>
<br>
A New Internet-Draft is available from the on-line Internet-Drafts<br>
directories.<br><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Rapid
Synchronisation of RTP Flows<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : C. Perkins, T.
Schierl<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
draft-perkins-avt-rapid-rtp-sync-03.txt<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
17<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
2009-03-09<br><br>
This memo outlines how RTP multimedia sessions are synchronised, and<br>
discusses how rapidly such synchronisation can occur.&nbsp; We show
that<br>
most RTP sessions can be synchronised immediately, but that the use<br>
of video switching multipoint conference units (MCUs) or large
source<br>
specific multicast (SSM) groups can greatly increase the initial<br>
synchronisation delay.&nbsp; This increase in delay can be unacceptable
to<br>
some applications that use layered and/or multi-description
codecs.<br><br>
This memo updates the RTP Control Protocol (RTCP) timing rules to<br>
reduce the initial synchronisation delay for SSM sessions.&nbsp; A
new<br>
feedback packet is defined for use with the Extended RTP Profile for<br>
RTCP-based Feedback (RTP/AVPF), allowing video switching MCUs to<br>
rapidly request resynchronisation.&nbsp; Two new RTP header extensions
are<br>
defined to allow rapid synchronisation of late joiners, and
guarantee<br>
correct timestamp based decoding order recovery for layered codecs
in<br>
the presence of clock skew.<br><br>
A URL for this Internet-Draft is:<br>
<a href=3D"http://www.ietf.org/internet-drafts/draft-perkins-avt-rapid-rtp">
http://www.ietf.org/internet-drafts/draft-perkins-avt-rapid-rtp</a>-
sync-03.txt<br><br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/">
ftp://ftp.ietf.org/internet-drafts/</a><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>
Content-Type: text/plain<br>
Content-ID:
<a href=3D"mailto:2009-03-09100610.I-D@ietf.org">
&lt;2009-03-09100610.I-D@ietf.org&gt;</a><br><br>
_______________________________________________<br>
I-D-Announce mailing list<br>
<a href=3D"mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i-d-announce" eudora=3D"aut=
ourl">
https://www.ietf.org/mailman/listinfo/i-d-announce</a><br>
Internet-Draft directories:
<a href=3D"http://www.ietf.org/shadow.html">
http://www.ietf.org/shadow.html</a><br>
or
<a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt">
ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a></blockquote><br>
_______________________________________________<br>
Audio/Video Transport Working Group<br>
<a href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" eudora=3D"autourl">
https://www.ietf.org/mailman/listinfo/avt</a></blockquote><br>
_______________________________________________<br>
Audio/Video Transport Working Group<br>
<a href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" eudora=3D"autourl">
https://www.ietf.org/mailman/listinfo/avt</a></blockquote><br>
---<br>
Visit us at<br><br>
Web 2.0 Expo / March 31 - April 03 / San Francisco, California / Booth
415<br>
<a href=3D"http://www.web2expo.com/webexsf2009">
http://www.web2expo.com/webexsf2009</a><br><br>
NAB SHOW 2009 / April 18-23 / Las Vegas, Nevada USA / South Hall (Upper),
Booth SU9624F<br>
<a href=3D"http://www.nabshow.com/">http://www.nabshow.com/</a></blockquote>
<br><br>
<br><br>
<br>
<pre>
_______________________________________________
Audio/Video Transport Working Group
<a href=3D"mailto:avt@ietf.org">avt@ietf.org</a>


<a href=3D"https://www.ietf.org/mailman/listinfo/avt" eudora=3D"autourl">
https://www.ietf.org/mailman/listinfo/avt</a>
&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;=20
</pre><font face=3D"Courier New, Courier"></font></blockquote><br><br>
----<br>
Visit us at<br><br>
Web 2.0 Expo / March 31 - April 03 / San Francisco, California / Booth
415<br>
<a href=3D"http://www.web2expo.com/webexsf2009">
http://www.web2expo.com/webexsf2009</a><br><br>
NAB SHOW 2009 / April 18-23 / Las Vegas, Nevada USA / South Hall (Upper),
Booth SU9624F<br>
<a href=3D"http://www.nabshow.com/">http://www.nabshow.com/</a></blockquote>
<br><br>
<br><br>
<pre>

_______________________________________________
Audio/Video Transport Working Group
<a href=3D"mailto:avt@ietf.org">avt@ietf.org</a>

<a href=3D"https://www.ietf.org/mailman/listinfo/avt" eudora=3D"autourl">
https://www.ietf.org/mailman/listinfo/avt</a>
&nbsp;
</pre><font face=3D"Courier New, Courier"></font></blockquote><br><br>
----<br>
Visit us at<br><br>
IEEE ICC 2009 / June 14-18 / Dresden, Germany / International Congress
Center<br>
<a href=3D"http://www.comsoc.org/confs/icc/2009/">
http://www.comsoc.org/confs/icc/2009/</a><br><br>
Laser World of Photonics 2009 / June 15-18 / Munich, Germay / Hall B1,
Booth 461<br>
<a href=3D"http://world-of-photonics.net/de/laser/start">
http://world-of-photonics.net/de/laser/start</a></blockquote>
_______________________________________________<br>
Audio/Video Transport Working Group<br>
<a href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" eudora=3D"autourl">
https://www.ietf.org/mailman/listinfo/avt</a></blockquote><br><br>
<br>
-- <br>
Colin Perkins<br>
<a href=3D"http://csperkins.org/">http://csperkins.org/</a><br><br>
</blockquote></body>
</html>

--=====================_513762156==.ALT--


From abegen@cisco.com  Tue Jun 16 14:16:05 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 514B63A6DC2 for <avt@core3.amsl.com>; Tue, 16 Jun 2009 14:16:05 -0700 (PDT)
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 MOOd0DtJZHdf for <avt@core3.amsl.com>; Tue, 16 Jun 2009 14:16:04 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 3B77A3A6D71 for <avt@ietf.org>; Tue, 16 Jun 2009 14:16:04 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,232,1243814400"; d="scan'208";a="325307503"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 16 Jun 2009 21:14:42 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n5GLEgdQ006888;  Tue, 16 Jun 2009 14:14:42 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n5GLEgF9026192; Tue, 16 Jun 2009 21:14:42 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.3959);  Tue, 16 Jun 2009 14:14:41 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 16 Jun 2009 14:12:44 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D54098D84B9@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <00dc01c9eec3$6a8b3070$3fa19150$%roni@huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] comments on section 10 ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
Thread-Index: AcnupPP7shhfq4AdRG2dZ9bI0Xe2fQABeZQAAAWPwrAAAUCvIA==
References: <00b801c9eea4$f90f3360$eb2d9a20$%roni@huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D83DD@xmb-sjc-215.amer.cisco.com> <00dc01c9eec3$6a8b3070$3fa19150$%roni@huawei.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Roni Even" <Even.roni@huawei.com>, <avt@ietf.org>
X-OriginalArrivalTime: 16 Jun 2009 21:14:41.0946 (UTC) FILETIME=[77048FA0:01C9EEC7]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4300; t=1245186882; x=1246050882; c=relaxed/simple; s=sjdkim1004; 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]=20comments=20on=20section=2010=20 ofdraft-ietf-avt-rapid-acquisition-for-rtp-01 |Sender:=20; bh=pP9xjzgzzqKrAcQgHRnv/thMcyIRXnKVs7twGBp6nUg=; b=IiUnfgEentGz0FpzmBJkXvAHrgbYE1QJraoqj1udb0IwfUbj+7EuYoj2dB Nx6xfvYgULG22ZOSnzR6cyX+dxXjfUY3ZNE8VkEmBWsYWvh9hxuuEQTOqC05 rao+yiq5n1Z/rEsGgzHxVCJXzrxtxOAzv3bYZKo82Npbnw68IoOKw=;
Authentication-Results: sj-dkim-1; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Subject: Re: [AVT] comments on section 10 ofdraft-ietf-avt-rapid-acquisition-for-rtp-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: Tue, 16 Jun 2009 21:16:05 -0000

Inline.

> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: Tuesday, June 16, 2009 1:46 PM
> To: Ali C. Begen (abegen); avt@ietf.org
> Subject: RE: [AVT] comments on section 10 =
ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
> Ali,
> From figure 2 and the text that follows
>=20
> " A Retransmission Source may equally act as a Burst Source.  The
>    Retransmission Source may also incorporate the Feedback Target
>    ([I-D.ietf-avt-rtcpssm] permits the feedback target to be a
>    retransmission server, since it is a logical function to which RRs
>    send their unicast feedback), and we will use the term =
Retransmission
>    Server (RS) in the remainder of the document to refer to a single
>    physical entity comprising these three entities that share state.
>    Note that the same method (with the identical message flows) would
>    also apply in a scenario where rapid acquisition is performed by a
>    feedback target co-located with the media source."
>=20
> I assumed that we are only dealing with the case that the RS is a =
single
> entity and not three different entities with different addresses

You are correct. There is a single retransmission server that does all =
the work. Other types of scenarios may be considered in the future.
=20
> I also thought that this was agreed in previous discussions

Yup.

=20
> If my understanding is not correct I will review the draft since the =
current
> text is not explicit enough to specify which part is doing each =
message. I
> saw that RAMS-R is going to feedback target but RAMS-T is going to RS =
which
> is not specifying a specific address according to you.

Right, RAMS-T goes to RS as well but it goes to the RTCP port of the =
unicast session not the FT of the primary session (since it is to =
terminate the unicast burst). What I am trying to say below is =
different, though, which is that we cannot make an assumption on the =
port RR wants to use in the unicast session (e.g., to receive the burst) =
based on the port it used for the primary session.

-acbegen
=20

> Roni
>=20
> -----Original Message-----
> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> Sent: Tuesday, June 16, 2009 10:00 PM
> To: Roni Even; avt@ietf.org
> Subject: RE: [AVT] comments on section 10
> ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
> Remember that the RAMS-R (RR->RS) message is NOT on the retransmission
> (unicast) session, it's on the primary session since it is sent to the
> feedback target of the primary SSM session. Thus, the source port RR =
uses to
> send RAMS-R "cannot" be assumed to be the destination port it wishes =
to
> receive the unicast burst on.
>=20
> If you agree with this statement, it is clear why we need port =
signaling.
> Muxing will not help much here. It will just reduce the number of =
signaled
> ports from 2 to 1.
>=20
> -acbegen
>=20
>=20
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf =
Of Roni
> Even
> > Sent: Tuesday, June 16, 2009 10:08 AM
> > To: avt@ietf.org
> > Subject: [AVT] comments on section 10
> ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > Hi,
> >
> > I looked at section 10 and have some comments
> >
> >
> >
> > 1.       If RTP/RTCP multiplexing is used, there is no need for any
> specific operation
> > from the RR side. The RR sends the RAMS-R message to the RS from the =
port
> it wants to
> > receive the RAMS-I and RTP payload. The RS just sends the =
information to
> the port from
> > which it received the RAMS-R and not to the one in the SDP
> >
> > 2.       In the case where there is no RTP/RTCP multiplexing, the =
RAMS-R
> RTCP message will
> > go to the RS and the RAMS-I will go to the port on the RR from where =
the
> RAMS-R was
> > received. For the RTP, the RR does not know if it has a NAT on the =
way to
> the RS and
> > should try to get a routable address (using STUN for example) and
> providing the port to
> > the RS ( we still need to agree on how to do it)
> >
> > 3.       If the above two points are correct than the RR receive =
port in
> the SDP is not
> > really useful
> >
> >
> >
> > Roni Even


From abegen@cisco.com  Tue Jun 16 19:53:49 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 CDF413A6A98 for <avt@core3.amsl.com>; Tue, 16 Jun 2009 19:53:49 -0700 (PDT)
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 d3jCjUdid2bt for <avt@core3.amsl.com>; Tue, 16 Jun 2009 19:53:49 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 6CB873A68B0 for <avt@ietf.org>; Tue, 16 Jun 2009 19:53:44 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,234,1243814400"; d="scan'208";a="177152554"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-2.cisco.com with ESMTP; 17 Jun 2009 02:53:55 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n5H2rtTl024011 for <avt@ietf.org>; Tue, 16 Jun 2009 19:53:55 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n5H2rtLh024920 for <avt@ietf.org>; Wed, 17 Jun 2009 02:53:55 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.3959);  Tue, 16 Jun 2009 19:53:55 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Date: Tue, 16 Jun 2009 19:53:49 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D54098D8627@xmb-sjc-215.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New Version Notification for draft-ietf-avt-post-repair-rtcp-xr-05 
Thread-Index: Acnu9dYeVnKKfUv6Rw6gKTI+YTWW5QAAGnqQ
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 17 Jun 2009 02:53:55.0821 (UTC) FILETIME=[DADF69D0:01C9EEF6]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2804; t=1245207235; x=1246071235; c=relaxed/simple; s=sjdkim2002; 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:=20FW=3A=20New=20Version=20Notification=20for=20=2 0=20=20=20=20=20=20=20=20draft-ietf-avt-post-repair-rtcp-xr- 05=20 |Sender:=20; bh=HMfp32hPUQRIZQg9pw9o1gGzOp4ijYWxHafENO+eXT4=; b=P+MSYDaugu56GIvMSJ/WsDcCCziE8X786rLHn4ddj+DuyPsFhNGEW9B2U8 7ySQq+nXZluKjF0kHtffNUa7IC6B9yL1tzCmx3cjFjXF543XHJwddcSKEPwI 05XAnSJ8Tg;
Authentication-Results: sj-dkim-2; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Subject: [AVT] FW: New Version Notification for draft-ietf-avt-post-repair-rtcp-xr-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: Wed, 17 Jun 2009 02:53:49 -0000

VGhpcyBkcmFmdCAoLTA0IHZlcnNpb24pIGhhcyBiZWVuIHdpdGggSUVTRyBzaW5jZSBlYXJseSB0
aGlzIHllYXIuIFdlIGluaXRpYWxseSByZWNlaXZlZCBzb21lIGNvbW1lbnRzIGFuZCB1cGRhdGVk
IHRoZSBkb2N1bWVudCBmb3IgdGhlIC0wNSB2ZXJzaW9uIChkaWQgbm90IHN1Ym1pdCBpdCBhdCB0
aGF0IHRpbWUsIHRob3VnaCkuIER1cmluZyB0aGUgcmV2aWV3LCBJRVNHIHJlYWxpemVkIHRoYXQg
dGhlIEFWVCBjaGFydGVyIGhhZCB0byBiZSB1cGRhdGVkIHRvIHJlZmxlY3QgdGhpcyB3b3JrLiBX
ZSBhcmUgc3RpbGwgd2FpdGluZyBmb3IgaXQuIFVudGlsIHRoZSBjaGFydGVyIGlzIGZpeGVkLCBo
ZXJlIGlzIHRoZSB1cGRhdGVkIHZlcnNpb24uDQoNCi1hY2JlZ2VuDQoNCg0KLS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS0NCkZyb206IElFVEYgSS1EIFN1Ym1pc3Npb24gVG9vbCBbbWFpbHRvOmlk
c3VibWlzc2lvbkBpZXRmLm9yZ10gDQpTZW50OiBUdWVzZGF5LCBKdW5lIDE2LCAyMDA5IDc6NDYg
UE0NClRvOiBBbGkgQy4gQmVnZW4gKGFiZWdlbikNCkNjOiBEb25nIEhzdSAoZG9oc3UpOyBNaWNo
YWVsIExhZ3VlIChtbGFndWUpDQpTdWJqZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9y
IGRyYWZ0LWlldGYtYXZ0LXBvc3QtcmVwYWlyLXJ0Y3AteHItMDUgDQoNCg0KQSBuZXcgdmVyc2lv
biBvZiBJLUQsIGRyYWZ0LWlldGYtYXZ0LXBvc3QtcmVwYWlyLXJ0Y3AteHItMDUudHh0IGhhcyBi
ZWVuIHN1Y2Nlc3NmdWx5IHN1Ym1pdHRlZCBieSBBbGkgQmVnZW4gYW5kIHBvc3RlZCB0byB0aGUg
SUVURiByZXBvc2l0b3J5Lg0KDQpGaWxlbmFtZToJIGRyYWZ0LWlldGYtYXZ0LXBvc3QtcmVwYWly
LXJ0Y3AteHINClJldmlzaW9uOgkgMDUNClRpdGxlOgkJIFBvc3QtUmVwYWlyIExvc3MgUkxFIFJl
cG9ydCBCbG9jayBUeXBlIGZvciBSVENQIFhSDQpDcmVhdGlvbl9kYXRlOgkgMjAwOS0wNi0xNg0K
V0cgSUQ6CQkgYXZ0DQpOdW1iZXJfb2ZfcGFnZXM6IDEwDQoNCkFic3RyYWN0Og0KVGhpcyBkb2N1
bWVudCBkZWZpbmVzIGEgbmV3IHJlcG9ydCBibG9jayB0eXBlIHdpdGhpbiB0aGUgZnJhbWV3b3Jr
IG9mDQpSVFAgQ29udHJvbCBQcm90b2NvbCAoUlRDUCkgRXh0ZW5kZWQgUmVwb3J0cyAoWFIpLiAg
T25lIG9mIHRoZQ0KaW5pdGlhbCBYUiByZXBvcnQgYmxvY2sgdHlwZXMgaXMgdGhlIExvc3MgUnVu
IExlbmd0aCBFbmNvZGluZyAoUkxFKQ0KUmVwb3J0IEJsb2NrLiAgVGhpcyByZXBvcnQgY29udmV5
cyB0aGUgaW5mb3JtYXRpb24gcmVnYXJkaW5nIHRoZQ0KaW5kaXZpZHVhbCBSZWFsLXRpbWUgVHJh
bnNwb3J0IFByb3RvY29sIChSVFApIHBhY2tldCByZWNlaXB0IGFuZCBsb3NzDQpldmVudHMgZXhw
ZXJpZW5jZWQgZHVyaW5nIHRoZSBSVENQIGludGVydmFsIHByZWNlZGluZyB0aGUNCnRyYW5zbWlz
c2lvbiBvZiB0aGUgcmVwb3J0LiAgVGhlIG5ldyByZXBvcnQsIHdoaWNoIGlzIHJlZmVycmVkIHRv
IGFzDQp0aGUgUG9zdC1yZXBhaXIgTG9zcyBSTEUgUmVwb3J0LCBjYXJyaWVzIHRoZSBpbmZvcm1h
dGlvbiByZWdhcmRpbmcNCnRoZSByZW1haW5pbmcgbG9zdCBwYWNrZXRzIGFmdGVyIGFsbCBsb3Nz
LXJlcGFpciBtZXRob2RzIGFyZSBhcHBsaWVkLg0KQnkgY29tcGFyaW5nIHRoZSBSVFAgcGFja2V0
IHJlY2VpcHRzL2xvc3NlcyBiZWZvcmUgYW5kIGFmdGVyIHRoZSBsb3NzDQpyZXBhaXIgaXMgY29t
cGxldGVkLCBvbmUgY2FuIGRldGVybWluZSB0aGUgZWZmZWN0aXZlbmVzcyBvZiB0aGUgbG9zcy0N
CnJlcGFpciBtZXRob2RzIGluIGFuIGFnZ3JlZ2F0ZWQgZmFzaGlvbi4gIFRoaXMgZG9jdW1lbnQg
YWxzbyBkZWZpbmVzDQp0aGUgc2lnbmFsaW5nIG9mIHRoZSBQb3N0LXJlcGFpciBMb3NzIFJMRSBS
ZXBvcnQgaW4gdGhlIFNlc3Npb24NCkRlc2NyaXB0aW9uIFByb3RvY29sIChTRFApLg0KICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIA0KDQoNClRoZSBJRVRGIFNlY3JldGFyaWF0Lg0KDQoNCg==

From root@core3.amsl.com  Tue Jun 16 20: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 875963A6BB3; Tue, 16 Jun 2009 20:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090617030001.875963A6BB3@core3.amsl.com>
Date: Tue, 16 Jun 2009 20:00:01 -0700 (PDT)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-post-repair-rtcp-xr-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, 17 Jun 2009 03: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           : Post-Repair Loss RLE Report Block Type for RTCP XR
	Author(s)       : A. Begen, et al.
	Filename        : draft-ietf-avt-post-repair-rtcp-xr-05.txt
	Pages           : 10
	Date            : 2009-06-16

This document defines a new report block type within the framework of
RTP Control Protocol (RTCP) Extended Reports (XR).  One of the
initial XR report block types is the Loss Run Length Encoding (RLE)
Report Block.  This report conveys the information regarding the
individual Real-time Transport Protocol (RTP) packet receipt and loss
events experienced during the RTCP interval preceding the
transmission of the report.  The new report, which is referred to as
the Post-repair Loss RLE Report, carries the information regarding
the remaining lost packets after all loss-repair methods are applied.
By comparing the RTP packet receipts/losses before and after the loss
repair is completed, one can determine the effectiveness of the loss-
repair methods in an aggregated fashion.  This document also defines
the signaling of the Post-repair Loss RLE Report in the Session
Description Protocol (SDP).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-post-repair-rtcp-xr-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-post-repair-rtcp-xr-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From gunnar.hellstrom@omnitor.se  Wed Jun 17 00:59:33 2009
Return-Path: <gunnar.hellstrom@omnitor.se>
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 6DA193A6D49 for <avt@core3.amsl.com>; Wed, 17 Jun 2009 00:59:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xL4y9aM1Swxs for <avt@core3.amsl.com>; Wed, 17 Jun 2009 00:59:32 -0700 (PDT)
Received: from s87.loopia.se (s87.loopia.se [194.9.95.112]) by core3.amsl.com (Postfix) with ESMTP id 99DCB3A6B73 for <avt@ietf.org>; Wed, 17 Jun 2009 00:59:31 -0700 (PDT)
Received: (qmail 73016 invoked from network); 17 Jun 2009 07:59:42 -0000
Received: from s34.loopia.se (HELO s57.loopia.se) ([194.9.94.70]) (envelope-sender <gunnar.hellstrom@omnitor.se>) by s87.loopia.se (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for <avt@ietf.org>; 17 Jun 2009 07:59:42 -0000
Received: (qmail 94499 invoked from network); 17 Jun 2009 07:59:39 -0000
Received: from 136.240.13.217.in-addr.dgcsystems.net (HELO GunnarH) (gunnar.hellstrom@omnitor.se@[217.13.240.136]) (envelope-sender <gunnar.hellstrom@omnitor.se>) by s57.loopia.se (qmail-ldap-1.03) with SMTP for <avt@ietf.org>; 17 Jun 2009 07:59:39 -0000
From: "Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se>
To: "'RFC Errata System'" <rfc-editor@rfc-editor.org>, <paulej@packetizer.com>, <rjsparks@nostrum.com>, <fluffy@cisco.com>, <even.roni@huawei.com>, <tom.taylor@rogers.com>
References: <200906161156.n5GBuv6K024657@boreas.isi.edu>
Date: Wed, 17 Jun 2009 09:59:40 +0200
Message-ID: <017c01c9ef21$9118f160$e800a8c0@GunnarH>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-reply-to: <200906161156.n5GBuv6K024657@boreas.isi.edu>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Thread-Index: AcnueeUqQ9bDVd8BTGGDp0+JX27XugApe7Og
Cc: avt@ietf.org
Subject: Re: [AVT] [Technical Errata Reported] RFC4103 (1793)
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, 17 Jun 2009 07:59:33 -0000

This Errata is the result of a discussion we had in the AVT list under the
subject " RFC 4103 - RTP Payload for Text Conversation" around April 14.

It is a minor adjustment of the text belonging to a packet layout example
and one field in the example to make the example totally consistent with the
packetization description. 

There is no change in the rules for packetization.

Gunnar
-------------------------------------------------------------------

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of RFC
Errata System
Sent: Tuesday, June 16, 2009 1:57 PM
To: gunnar.hellstrom@omnitor.se; paulej@packetizer.com;
rjsparks@nostrum.com; fluffy@cisco.com; even.roni@huawei.com;
tom.taylor@rogers.com
Cc: gunnar.hellstrom@omnitor.se; avt@ietf.org; rfc-editor@rfc-editor.org
Subject: [AVT] [Technical Errata Reported] RFC4103 (1793)


The following errata report has been submitted for RFC4103, "RTP Payload for
Text Conversation".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=4103&eid=1793

--------------------------------------
Type: Technical
Reported by: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>

Section: 7.1

Original Text
-------------
The value of the "R2 block length" would be set to zero in order to
represent the empty T140block.

  0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |V=2|P|X| CC=0  |M|  "RED" PT   |   sequence number of primary  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               timestamp of primary encoding "P"               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           synchronization source (SSRC) identifier            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |1|   T140 PT   |  timestamp offset of "R2" | "R2" block length |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |1|   T140 PT   |  timestamp offset of "R1" | "R1" block length |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |0|   T140 PT   | "R1" T.140 encoded redundant data             |
   +-+-+-+-+-+-+-+-+                               +---------------+
   |                                               |               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+         +-+-+-+
   |              "P" T.140 encoded primary data             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


Corrected Text
--------------
The value of the "R1 block length" would be set to zero in order to
represent the empty T140block.

  0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |V=2|P|X| CC=0  |M|  "RED" PT   |   sequence number of primary  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               timestamp of primary encoding "P"               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           synchronization source (SSRC) identifier            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |1|   T140 PT   |  timestamp offset of "R2" | "R2" block length |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |1|   T140 PT   |  timestamp offset of "R1" | "R1" block length |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |0|   T140 PT   | "R2" T.140 encoded redundant data             |
   +-+-+-+-+-+-+-+-+                               +---------------+
   |                                               |               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+         +-+-+-+
   |              "P" T.140 encoded primary data             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


Notes
-----


Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please use
"Reply All" to discuss whether it should be verified or rejected. When a
decision is reached, the verifying party (IESG) can log in to change the
status and edit the report, if necessary. 

--------------------------------------
RFC4103 (draft-ietf-avt-rfc2793bis-09)
--------------------------------------
Title               : RTP Payload for Text Conversation
Publication Date    : June 2005
Author(s)           : G. Hellstrom, P. Jones
Category            : PROPOSED STANDARD
Source              : Audio/Video Transport
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG
_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt

__________ NOD32 4158 (20090616) Information __________

Detta meddelande dr genomsvkt av NOD32 Antivirus.
http://www.nod32.com



From Tom.Van_Caenegem@alcatel-lucent.be  Wed Jun 17 01:17:25 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 1A5E23A6E02 for <avt@core3.amsl.com>; Wed, 17 Jun 2009 01:17:25 -0700 (PDT)
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_FR=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 xg04awAXe-Gw for <avt@core3.amsl.com>; Wed, 17 Jun 2009 01:17:23 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [62.23.212.57]) by core3.amsl.com (Postfix) with ESMTP id 97FD83A6DFF for <avt@ietf.org>; Wed, 17 Jun 2009 01:17:23 -0700 (PDT)
Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.dc-m.alcatel-lucent.com [155.132.6.75]) by smail2.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5H8HPVJ013950 for <avt@ietf.org>; Wed, 17 Jun 2009 10:17:28 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.52]) by FRVELSBHS03.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 17 Jun 2009 10:17:27 +0200
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: Wed, 17 Jun 2009 10:17:26 +0200
Message-ID: <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <mailman.10085.1245185397.4936.avt@ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] comments on section 10 of draft-ietf-avt-rapid-acquisition-for-rtp-01
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97g
References: <mailman.10085.1245185397.4936.avt@ietf.org>
From: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>
To: <avt@ietf.org>
X-OriginalArrivalTime: 17 Jun 2009 08:17:27.0834 (UTC) FILETIME=[0D5587A0:01C9EF24]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.80
Subject: Re: [AVT] comments on section 10 of draft-ietf-avt-rapid-acquisition-for-rtp-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: Wed, 17 Jun 2009 08:17:25 -0000

Hi Roni,

I think your understanding was indeed different from the general
assumptions in this draft. Previously we agreed to only consider the
case where there is only one physical entity involved (called the
Retransmission Server in the draft), which allows us to NOT consider and
discuss cases where for instance the feedback target (which is defined
in the rtcpssm draft/RFC) is not in the same box as the retransmission
source or burst source, the entities sourcing retransmision/burst
packets. In that case we then would also need to describe how these
separate entities communicate. =20
The fact that these different entities are now in the same box does not
necessarily mean that all interactions and data exchange with the RRs is
part of the same RTP session, which is in this case the SSM RTP session.
As Ali explained, the NACK and RAMS-R RTCP FB messages are directed to
the FB target, where we do not  defer from the rtcpssm draft. The RTP
retransmission/burst packets that are sent as a response to the NACK and
the RAMS-R can be either session multiplexed with respect to the
original SSM RTP session or SSRC muxed (same session), following RFC
4588. As the retransmission packets in this case are addressing the RR
in unicast, we obviously have a dedicated RTP session for the
retransmission/burst packets. We had some internal discussion on whether
considering the use case of having a separate session between RS and RR
for RTP retransmission packets triggered by an RTCP FB NACK and a
separate session for RTP burst packets triggered by an RTCP RAMS-R made
sense, but we ended up agreeing that allowing a single session was the
easiest way out, without imposing serious limitations to the general
architecture.=20

This means that the ports used by the (single) RTP retransmission/burst
session are in principle decoupled from the primary SSM session. Hence
if an RR wants to receive the burst/retransmission packets and
associated RTCP messages on the same port the RR sent out the RTCP
RAMS-R/ NACK FB messages, this should either be signaled by the RR, OR
such port usage scheme is considered the "default" case -which also
means the RR supports RTP/RTCP port muxing for the retransmission/burst
session-, and then the RR needs to signal the ports for receiving the
RTP and RTCP packets in the retransmission session when it requires
dedicated ports. =20

The RAMS-I (RS-> RR) and RAMS-T (RR-> RS) messages are only relevant to
a specific RR requesting the RTP burst stream and the RS, and carry
information/signaling related to the retransmission/burst session and
have nothing to do with the SSM session. Hence the FB target as logical
entity is not involved here.=20

I hope this clarifies rather than it contributes to your confusion. But
we may need to rephrase the part you quoted, as your interpretation was
different from its intended meaning. We also tried to be more explicit
in which session which RAMS or other RTCP (e.g. Bye) messages needed to
be exchanged compared to a previous version of the draft, but we are
open of course to any other suggestions from your side if this is not
clear enough in your opinion.

Tom     =20






" A Retransmission Source may equally act as a Burst Source.  The
   Retransmission Source may also incorporate the Feedback Target
   ([I-D.ietf-avt-rtcpssm] permits the feedback target to be a
   retransmission server, since it is a logical function to which RRs
   send their unicast feedback), and we will use the term Retransmission
   Server (RS) in the remainder of the document to refer to a single
   physical entity comprising these three entities that share state.
   Note that the same method (with the identical message flows) would
   also apply in a scenario where rapid acquisition is performed by a
   feedback target co-located with the media source."

I assumed that we are only dealing with the case that the RS is a single
entity and not three different entities with different addresses

I also thought that this was agreed in previous discussions

If my understanding is not correct I will review the draft since the
current text is not explicit enough to specify which part is doing each
message. I saw that RAMS-R is going to feedback target but RAMS-T is
going to RS which is not specifying a specific address according to you.

Roni

-----Original Message-----
From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
Sent: Tuesday, June 16, 2009 10:00 PM
To: Roni Even; avt@ietf.org
Subject: RE: [AVT] comments on section 10
ofdraft-ietf-avt-rapid-acquisition-for-rtp-01

Remember that the RAMS-R (RR->RS) message is NOT on the retransmission
(unicast) session, it's on the primary session since it is sent to the
feedback target of the primary SSM session. Thus, the source port RR
uses to send RAMS-R "cannot" be assumed to be the destination port it
wishes to receive the unicast burst on.

If you agree with this statement, it is clear why we need port
signaling.
Muxing will not help much here. It will just reduce the number of
signaled ports from 2 to 1.

-acbegen


> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of=20
> Roni
Even
> Sent: Tuesday, June 16, 2009 10:08 AM
> To: avt@ietf.org
> Subject: [AVT] comments on section 10
ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
> Hi,
>=20
> I looked at section 10 and have some comments
>=20
>=20
>=20
> 1.       If RTP/RTCP multiplexing is used, there is no need for any
specific operation
> from the RR side. The RR sends the RAMS-R message to the RS from the=20
> port
it wants to
> receive the RAMS-I and RTP payload. The RS just sends the information=20
> to
the port from
> which it received the RAMS-R and not to the one in the SDP
>=20
> 2.       In the case where there is no RTP/RTCP multiplexing, the
RAMS-R
RTCP message will
> go to the RS and the RAMS-I will go to the port on the RR from where=20
> the
RAMS-R was
> received. For the RTP, the RR does not know if it has a NAT on the way

> to
the RS and
> should try to get a routable address (using STUN for example) and
providing the port to
> the RS ( we still need to agree on how to do it)
>=20
> 3.       If the above two points are correct than the RR receive port
in
the SDP is not
> really useful
>=20
>=20
>=20
> Roni Even



From Even.roni@huawei.com  Wed Jun 17 03:03:36 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3841B3A6A53 for <avt@core3.amsl.com>; Wed, 17 Jun 2009 03:03:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.382
X-Spam-Level: 
X-Spam-Status: No, score=-1.382 tagged_above=-999 required=5 tests=[AWL=0.598,  BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L6mcNvoJxHSi for <avt@core3.amsl.com>; Wed, 17 Jun 2009 03:03:35 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 046313A67A6 for <avt@ietf.org>; Wed, 17 Jun 2009 03:03:35 -0700 (PDT)
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 <0KLD002P4NU7UC@szxga03-in.huawei.com> for avt@ietf.org; Wed, 17 Jun 2009 18:01:20 +0800 (CST)
Received: from huawei.com ([172.24.1.6]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLD008UZNU6XB@szxga03-in.huawei.com> for avt@ietf.org; Wed, 17 Jun 2009 18:01:19 +0800 (CST)
Received: from windows8d787f9 (bzq-79-179-78-100.red.bezeqint.net [79.179.78.100]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KLD00EOANTXJF@szxml02-in.huawei.com>; Wed, 17 Jun 2009 18:01:18 +0800 (CST)
Date: Wed, 17 Jun 2009 12:59:35 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <04CAD96D4C5A3D48B1919248A8FE0D54098D84B9@xmb-sjc-215.amer.cisco.com>
To: "'Ali C. Begen (abegen)'" <abegen@cisco.com>, avt@ietf.org
Message-id: <015201c9ef32$575066a0$05f133e0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcnupPP7shhfq4AdRG2dZ9bI0Xe2fQABeZQAAAWPwrAAAUCvIAAYQoMw
References: <00b801c9eea4$f90f3360$eb2d9a20$%roni@huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D83DD@xmb-sjc-215.amer.cisco.com> <00dc01c9eec3$6a8b3070$3fa19150$%roni@huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D84B9@xmb-sjc-215.amer.cisco.com>
Subject: Re: [AVT] comments on section 10 ofdraft-ietf-avt-rapid-acquisition-for-rtp-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: Wed, 17 Jun 2009 10:03:36 -0000

Ali,
Thanks, I understand the RAMS-R and RAMS-T port usage and the logic behind
it.
As for the RAMS-I section 6.2 says

" Note that RS learns the IP address information for RR from the
       RAMS-R message it received.  (This description glosses over the
       NAT details.  Refer to Section 10 for a discussion of NAT-related
       issues.)"

So according to the above if using RTP/RTCP multiplexing, the RTP unicast
stream is sent to the address from which the RAMS-R has arrived. 
Roni

-----Original Message-----
From: Ali C. Begen (abegen) [mailto:abegen@cisco.com] 
Sent: Wednesday, June 17, 2009 12:13 AM
To: Roni Even; avt@ietf.org
Subject: RE: [AVT] comments on section 10
ofdraft-ietf-avt-rapid-acquisition-for-rtp-01

Inline.

> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: Tuesday, June 16, 2009 1:46 PM
> To: Ali C. Begen (abegen); avt@ietf.org
> Subject: RE: [AVT] comments on section 10
ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> 
> Ali,
> From figure 2 and the text that follows
> 
> " A Retransmission Source may equally act as a Burst Source.  The
>    Retransmission Source may also incorporate the Feedback Target
>    ([I-D.ietf-avt-rtcpssm] permits the feedback target to be a
>    retransmission server, since it is a logical function to which RRs
>    send their unicast feedback), and we will use the term Retransmission
>    Server (RS) in the remainder of the document to refer to a single
>    physical entity comprising these three entities that share state.
>    Note that the same method (with the identical message flows) would
>    also apply in a scenario where rapid acquisition is performed by a
>    feedback target co-located with the media source."
> 
> I assumed that we are only dealing with the case that the RS is a single
> entity and not three different entities with different addresses

You are correct. There is a single retransmission server that does all the
work. Other types of scenarios may be considered in the future.
 
> I also thought that this was agreed in previous discussions

Yup.

 
> If my understanding is not correct I will review the draft since the
current
> text is not explicit enough to specify which part is doing each message. I
> saw that RAMS-R is going to feedback target but RAMS-T is going to RS
which
> is not specifying a specific address according to you.

Right, RAMS-T goes to RS as well but it goes to the RTCP port of the unicast
session not the FT of the primary session (since it is to terminate the
unicast burst). What I am trying to say below is different, though, which is
that we cannot make an assumption on the port RR wants to use in the unicast
session (e.g., to receive the burst) based on the port it used for the
primary session.

-acbegen
 

> Roni
> 
> -----Original Message-----
> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> Sent: Tuesday, June 16, 2009 10:00 PM
> To: Roni Even; avt@ietf.org
> Subject: RE: [AVT] comments on section 10
> ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> 
> Remember that the RAMS-R (RR->RS) message is NOT on the retransmission
> (unicast) session, it's on the primary session since it is sent to the
> feedback target of the primary SSM session. Thus, the source port RR uses
to
> send RAMS-R "cannot" be assumed to be the destination port it wishes to
> receive the unicast burst on.
> 
> If you agree with this statement, it is clear why we need port signaling.
> Muxing will not help much here. It will just reduce the number of signaled
> ports from 2 to 1.
> 
> -acbegen
> 
> 
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Roni
> Even
> > Sent: Tuesday, June 16, 2009 10:08 AM
> > To: avt@ietf.org
> > Subject: [AVT] comments on section 10
> ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > Hi,
> >
> > I looked at section 10 and have some comments
> >
> >
> >
> > 1.       If RTP/RTCP multiplexing is used, there is no need for any
> specific operation
> > from the RR side. The RR sends the RAMS-R message to the RS from the
port
> it wants to
> > receive the RAMS-I and RTP payload. The RS just sends the information to
> the port from
> > which it received the RAMS-R and not to the one in the SDP
> >
> > 2.       In the case where there is no RTP/RTCP multiplexing, the RAMS-R
> RTCP message will
> > go to the RS and the RAMS-I will go to the port on the RR from where the
> RAMS-R was
> > received. For the RTP, the RR does not know if it has a NAT on the way
to
> the RS and
> > should try to get a routable address (using STUN for example) and
> providing the port to
> > the RS ( we still need to agree on how to do it)
> >
> > 3.       If the above two points are correct than the RR receive port in
> the SDP is not
> > really useful
> >
> >
> >
> > Roni Even


From Even.roni@huawei.com  Wed Jun 17 04:25:20 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B2743A6B0D for <avt@core3.amsl.com>; Wed, 17 Jun 2009 04:25:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.479
X-Spam-Level: 
X-Spam-Status: No, score=-0.479 tagged_above=-999 required=5 tests=[AWL=-0.603, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_SORBS_WEB=0.619, 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 QROQg6Cd70Gs for <avt@core3.amsl.com>; Wed, 17 Jun 2009 04:25:19 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 247893A6A49 for <avt@ietf.org>; Wed, 17 Jun 2009 04:25:19 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLD002X1RQ6DL@szxga01-in.huawei.com> for avt@ietf.org; Wed, 17 Jun 2009 19:25:18 +0800 (CST)
Received: from huawei.com ([172.24.1.6]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLD00JPTRQ5BW@szxga01-in.huawei.com> for avt@ietf.org; Wed, 17 Jun 2009 19:25:17 +0800 (CST)
Received: from windows8d787f9 (bzq-79-179-78-100.red.bezeqint.net [79.179.78.100]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KLD00GCXRPXFD@szxml02-in.huawei.com>; Wed, 17 Jun 2009 19:25:17 +0800 (CST)
Date: Wed, 17 Jun 2009 14:23:37 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com>
To: 'VAN CAENEGEM Tom' <Tom.Van_Caenegem@alcatel-lucent.be>, avt@ietf.org
Message-id: <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdA=
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com>
Subject: Re: [AVT] comments on section 10 of	draft-ietf-avt-rapid-acquisition-for-rtp-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: Wed, 17 Jun 2009 11:25:20 -0000

Tom,
I understand the RAMS-R and RAMS-T, the text is not clear enough in section
6.2

It still leaves open the issue of the addresses for the RR in the case of
declarative SDP when there is no answer SDP from the RR.

About RTP/RTCP multiplexing, the declarative SDP can show that the RS
supports it and I still think that some information about the addressing
(like support for RTP/RTCP mux) should be supplied in the RAMS-R for the
declarative case.

Roni

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> VAN CAENEGEM Tom
> Sent: Wednesday, June 17, 2009 11:17 AM
> To: avt@ietf.org
> Subject: Re: [AVT] comments on section 10 of draft-ietf-avt-rapid-
> acquisition-for-rtp-01
> 
> Hi Roni,
> 
> I think your understanding was indeed different from the general
> assumptions in this draft. Previously we agreed to only consider the
> case where there is only one physical entity involved (called the
> Retransmission Server in the draft), which allows us to NOT consider
> and
> discuss cases where for instance the feedback target (which is defined
> in the rtcpssm draft/RFC) is not in the same box as the retransmission
> source or burst source, the entities sourcing retransmision/burst
> packets. In that case we then would also need to describe how these
> separate entities communicate.
> The fact that these different entities are now in the same box does not
> necessarily mean that all interactions and data exchange with the RRs
> is
> part of the same RTP session, which is in this case the SSM RTP
> session.
> As Ali explained, the NACK and RAMS-R RTCP FB messages are directed to
> the FB target, where we do not  defer from the rtcpssm draft. The RTP
> retransmission/burst packets that are sent as a response to the NACK
> and
> the RAMS-R can be either session multiplexed with respect to the
> original SSM RTP session or SSRC muxed (same session), following RFC
> 4588. 
>As the retransmission packets in this case are addressing the RR
> in unicast, we obviously have a dedicated RTP session for the
> retransmission/burst packets. We had some internal discussion on
> whether
> considering the use case of having a separate session between RS and RR
> for RTP retransmission packets triggered by an RTCP FB NACK and a
> separate session for RTP burst packets triggered by an RTCP RAMS-R made
> sense, but we ended up agreeing that allowing a single session was the
> easiest way out, without imposing serious limitations to the general
> architecture.
> 
> This means that the ports used by the (single) RTP retransmission/burst
> session are in principle decoupled from the primary SSM session. Hence
> if an RR wants to receive the burst/retransmission packets and
> associated RTCP messages on the same port the RR sent out the RTCP
> RAMS-R/ NACK FB messages, this should either be signaled by the RR, OR
> such port usage scheme is considered the "default" case -which also
> means the RR supports RTP/RTCP port muxing for the retransmission/burst
> session-, and then the RR needs to signal the ports for receiving the
> RTP and RTCP packets in the retransmission session when it requires
> dedicated ports.
> 
> The RAMS-I (RS-> RR) and RAMS-T (RR-> RS) messages are only relevant to
> a specific RR requesting the RTP burst stream and the RS, and carry
> information/signaling related to the retransmission/burst session and
> have nothing to do with the SSM session. Hence the FB target as logical
> entity is not involved here.
> 
> I hope this clarifies rather than it contributes to your confusion. But
> we may need to rephrase the part you quoted, as your interpretation was
> different from its intended meaning. We also tried to be more explicit
> in which session which RAMS or other RTCP (e.g. Bye) messages needed to
> be exchanged compared to a previous version of the draft, but we are
> open of course to any other suggestions from your side if this is not
> clear enough in your opinion.
> 
> Tom
> 
> 
> 
> 
> 
> 
> " A Retransmission Source may equally act as a Burst Source.  The
>    Retransmission Source may also incorporate the Feedback Target
>    ([I-D.ietf-avt-rtcpssm] permits the feedback target to be a
>    retransmission server, since it is a logical function to which RRs
>    send their unicast feedback), and we will use the term
> Retransmission
>    Server (RS) in the remainder of the document to refer to a single
>    physical entity comprising these three entities that share state.
>    Note that the same method (with the identical message flows) would
>    also apply in a scenario where rapid acquisition is performed by a
>    feedback target co-located with the media source."
> 
> I assumed that we are only dealing with the case that the RS is a
> single
> entity and not three different entities with different addresses
> 
> I also thought that this was agreed in previous discussions
> 
> If my understanding is not correct I will review the draft since the
> current text is not explicit enough to specify which part is doing each
> message. I saw that RAMS-R is going to feedback target but RAMS-T is
> going to RS which is not specifying a specific address according to
> you.
> 
> Roni
> 
> -----Original Message-----
> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> Sent: Tuesday, June 16, 2009 10:00 PM
> To: Roni Even; avt@ietf.org
> Subject: RE: [AVT] comments on section 10
> ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> 
> Remember that the RAMS-R (RR->RS) message is NOT on the retransmission
> (unicast) session, it's on the primary session since it is sent to the
> feedback target of the primary SSM session. Thus, the source port RR
> uses to send RAMS-R "cannot" be assumed to be the destination port it
> wishes to receive the unicast burst on.
> 
> If you agree with this statement, it is clear why we need port
> signaling.
> Muxing will not help much here. It will just reduce the number of
> signaled ports from 2 to 1.
> 
> -acbegen
> 
> 
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> > Roni
> Even
> > Sent: Tuesday, June 16, 2009 10:08 AM
> > To: avt@ietf.org
> > Subject: [AVT] comments on section 10
> ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > Hi,
> >
> > I looked at section 10 and have some comments
> >
> >
> >
> > 1.       If RTP/RTCP multiplexing is used, there is no need for any
> specific operation
> > from the RR side. The RR sends the RAMS-R message to the RS from the
> > port
> it wants to
> > receive the RAMS-I and RTP payload. The RS just sends the information
> > to
> the port from
> > which it received the RAMS-R and not to the one in the SDP
> >
> > 2.       In the case where there is no RTP/RTCP multiplexing, the
> RAMS-R
> RTCP message will
> > go to the RS and the RAMS-I will go to the port on the RR from where
> > the
> RAMS-R was
> > received. For the RTP, the RR does not know if it has a NAT on the
> way
> 
> > to
> the RS and
> > should try to get a routable address (using STUN for example) and
> providing the port to
> > the RS ( we still need to agree on how to do it)
> >
> > 3.       If the above two points are correct than the RR receive port
> in
> the SDP is not
> > really useful
> >
> >
> >
> > Roni Even
> 
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From Tom.Van_Caenegem@alcatel-lucent.be  Wed Jun 17 05:23:36 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 7232C28C0E4 for <avt@core3.amsl.com>; Wed, 17 Jun 2009 05:23:36 -0700 (PDT)
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_FR=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 nMmhrjUZMe7H for <avt@core3.amsl.com>; Wed, 17 Jun 2009 05:23:34 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by core3.amsl.com (Postfix) with ESMTP id 680E528C0DB for <avt@ietf.org>; Wed, 17 Jun 2009 05:23:34 -0700 (PDT)
Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.dc-m.alcatel-lucent.com [155.132.6.76]) by smail3.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5HCN3Ew010687;  Wed, 17 Jun 2009 14:23:19 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.52]) by FRVELSBHS04.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 17 Jun 2009 14:23:09 +0200
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: Wed, 17 Jun 2009 14:23:08 +0200
Message-ID: <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] comments on section 10 ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4A==
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com>
From: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>
To: "Roni Even" <Even.roni@huawei.com>, <avt@ietf.org>
X-OriginalArrivalTime: 17 Jun 2009 12:23:09.0411 (UTC) FILETIME=[5FFFAB30:01C9EF46]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.83
Subject: Re: [AVT] comments on section 10 ofdraft-ietf-avt-rapid-acquisition-for-rtp-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: Wed, 17 Jun 2009 12:23:36 -0000

 Hi Roni,

Perhaps the start of section 6.2 can be rewritten as follows:


<START>

6.2.  Message Flows

   Figure 2 shows the main entities involved in rapid acquisition:

   o  Multicast Source

   o  Feedback Target (FT)

   o  Burst/ Retransmission Source

   o  RTP Receiver (RR)

(fig 2)

=20
The feedback target (FT) is the entity as defined in [rtcpssm draft], to
which the RR sends its RTCP FB messages, indicating packet loss in the
ssm primary stream by means of a NACK or indicating the RR's desire to
have rapid acquisition of the ssm primary stream (by means of an RTCP FB
message as defined in this document). While the burst/retransmission
source is responsible for responding on these messages and, in the case
of rapid acquisition, further RTCP interaction with the RR during this
acquisition process, it is assumed in the remainder of the document that
these two logical entities (FT and burst/retransmission source) are
combined in a single physical entity and share state. In the remainder
of the text, the term retransmission server is used whenever
appropriate, to refer to the combined functionality of the FT and
retransmission/burst source. However, it must be noted that only the FT
is involved in the primary ssm RTP session, whereas the
burst/retransmission source transmits unicast RTP burst and RTP
retransmissions packets (both formatted  as RTP retransmission packets
[RFC4585]) in a single separate unicast RTP retransmission session to
each RR.

Note also that the same method (with the identical message flows) would
also apply in a scenario where rapid acquisition is performed by a
feedback target co-located with the media source.

(...)

<END>

Tom: As we mandate the retransmission source and burst source to be in
the same session, I think it is no longer required to split-up among
these two logical entities. I invite other people, including the
co-authors to comment on this new text proposal.

With respect to your comments on the RTP/RTCP port muxing support
indication by the RR inside the RAMS-R message. That would be needed,
but is not sufficient as, if only declarative SDP is used, and we want
to have the possibility that the RTP/RTCP packets in the retransmission
session can be received by the RR on the same port the RR issues the
RTCP RAMS-R, we need also a way by which the RR can signal this too. We
provided a possible solution in the draft, but I understood that you
think such a solution should be proposed in a separate draft proposal?
But I guess that would also apply then to the signaling of support for
RTP/RTCP port muxing by the RR?

Tom

-----Original Message-----
From: Roni Even [mailto:Even.roni@huawei.com]=20
Sent: woensdag 17 juni 2009 13:24
To: VAN CAENEGEM Tom; avt@ietf.org
Subject: RE: [AVT] comments on section 10
ofdraft-ietf-avt-rapid-acquisition-for-rtp-01

Tom,
I understand the RAMS-R and RAMS-T, the text is not clear enough in
section
6.2

It still leaves open the issue of the addresses for the RR in the case
of declarative SDP when there is no answer SDP from the RR.

About RTP/RTCP multiplexing, the declarative SDP can show that the RS
supports it and I still think that some information about the addressing
(like support for RTP/RTCP mux) should be supplied in the RAMS-R for the
declarative case.

Roni

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of=20
> VAN CAENEGEM Tom
> Sent: Wednesday, June 17, 2009 11:17 AM
> To: avt@ietf.org
> Subject: Re: [AVT] comments on section 10 of draft-ietf-avt-rapid-
> acquisition-for-rtp-01
>=20
> Hi Roni,
>=20
> I think your understanding was indeed different from the general =20
>assumptions in this draft. Previously we agreed to only consider the =20
>case where there is only one physical entity involved (called the =20
>Retransmission Server in the draft), which allows us to NOT consider =20
>and  discuss cases where for instance the feedback target (which is=20
>defined  in the rtcpssm draft/RFC) is not in the same box as the=20
>retransmission  source or burst source, the entities sourcing=20
>retransmision/burst  packets. In that case we then would also need to=20
>describe how these  separate entities communicate.
> The fact that these different entities are now in the same box does=20
>not  necessarily mean that all interactions and data exchange with the=20
>RRs  is  part of the same RTP session, which is in this case the SSM=20
>RTP  session.
> As Ali explained, the NACK and RAMS-R RTCP FB messages are directed to

>the FB target, where we do not  defer from the rtcpssm draft. The RTP =20
>retransmission/burst packets that are sent as a response to the NACK =20
>and  the RAMS-R can be either session multiplexed with respect to the =20
>original SSM RTP session or SSRC muxed (same session), following RFC =20
>4588.
>As the retransmission packets in this case are addressing the RR  in=20
>unicast, we obviously have a dedicated RTP session for the =20
>retransmission/burst packets. We had some internal discussion on =20
>whether  considering the use case of having a separate session between=20
>RS and RR  for RTP retransmission packets triggered by an RTCP FB NACK=20
>and a  separate session for RTP burst packets triggered by an RTCP=20
>RAMS-R made  sense, but we ended up agreeing that allowing a single=20
>session was the  easiest way out, without imposing serious limitations=20
>to the general  architecture.
>=20
> This means that the ports used by the (single) RTP=20
> retransmission/burst session are in principle decoupled from the=20
> primary SSM session. Hence if an RR wants to receive the=20
> burst/retransmission packets and associated RTCP messages on the same=20
> port the RR sent out the RTCP RAMS-R/ NACK FB messages, this should=20
> either be signaled by the RR, OR such port usage scheme is considered=20
> the "default" case -which also means the RR supports RTP/RTCP port=20
> muxing for the retransmission/burst session-, and then the RR needs to

> signal the ports for receiving the RTP and RTCP packets in the=20
> retransmission session when it requires dedicated ports.
>=20
> The RAMS-I (RS-> RR) and RAMS-T (RR-> RS) messages are only relevant=20
> to a specific RR requesting the RTP burst stream and the RS, and carry

> information/signaling related to the retransmission/burst session and=20
> have nothing to do with the SSM session. Hence the FB target as=20
> logical entity is not involved here.
>=20
> I hope this clarifies rather than it contributes to your confusion.=20
> But we may need to rephrase the part you quoted, as your=20
> interpretation was different from its intended meaning. We also tried=20
> to be more explicit in which session which RAMS or other RTCP (e.g.=20
> Bye) messages needed to be exchanged compared to a previous version of

> the draft, but we are open of course to any other suggestions from=20
> your side if this is not clear enough in your opinion.
>=20
> Tom
>=20
>=20
>=20
>=20
>=20
>=20
> " A Retransmission Source may equally act as a Burst Source.  The
>    Retransmission Source may also incorporate the Feedback Target
>    ([I-D.ietf-avt-rtcpssm] permits the feedback target to be a
>    retransmission server, since it is a logical function to which RRs
>    send their unicast feedback), and we will use the term=20
> Retransmission
>    Server (RS) in the remainder of the document to refer to a single
>    physical entity comprising these three entities that share state.
>    Note that the same method (with the identical message flows) would
>    also apply in a scenario where rapid acquisition is performed by a
>    feedback target co-located with the media source."
>=20
> I assumed that we are only dealing with the case that the RS is a=20
> single entity and not three different entities with different=20
> addresses
>=20
> I also thought that this was agreed in previous discussions
>=20
> If my understanding is not correct I will review the draft since the=20
> current text is not explicit enough to specify which part is doing=20
> each message. I saw that RAMS-R is going to feedback target but RAMS-T

> is going to RS which is not specifying a specific address according to

> you.
>=20
> Roni
>=20
> -----Original Message-----
> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> Sent: Tuesday, June 16, 2009 10:00 PM
> To: Roni Even; avt@ietf.org
> Subject: RE: [AVT] comments on section 10
> ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
> Remember that the RAMS-R (RR->RS) message is NOT on the retransmission
> (unicast) session, it's on the primary session since it is sent to the

> feedback target of the primary SSM session. Thus, the source port RR=20
> uses to send RAMS-R "cannot" be assumed to be the destination port it=20
> wishes to receive the unicast burst on.
>=20
> If you agree with this statement, it is clear why we need port=20
> signaling.
> Muxing will not help much here. It will just reduce the number of=20
> signaled ports from 2 to 1.
>=20
> -acbegen
>=20
>=20
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf=20
> > Of Roni
> Even
> > Sent: Tuesday, June 16, 2009 10:08 AM
> > To: avt@ietf.org
> > Subject: [AVT] comments on section 10
> ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > Hi,
> >
> > I looked at section 10 and have some comments
> >
> >
> >
> > 1.       If RTP/RTCP multiplexing is used, there is no need for any
> specific operation
> > from the RR side. The RR sends the RAMS-R message to the RS from the

> > port
> it wants to
> > receive the RAMS-I and RTP payload. The RS just sends the=20
> > information to
> the port from
> > which it received the RAMS-R and not to the one in the SDP
> >
> > 2.       In the case where there is no RTP/RTCP multiplexing, the
> RAMS-R
> RTCP message will
> > go to the RS and the RAMS-I will go to the port on the RR from where

> > the
> RAMS-R was
> > received. For the RTP, the RR does not know if it has a NAT on the
> way
>=20
> > to
> the RS and
> > should try to get a routable address (using STUN for example) and
> providing the port to
> > the RS ( we still need to agree on how to do it)
> >
> > 3.       If the above two points are correct than the RR receive
port
> in
> the SDP is not
> > really useful
> >
> >
> >
> > Roni Even
>=20
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From abegen@cisco.com  Wed Jun 17 07:13:20 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 B7E663A6C93 for <avt@core3.amsl.com>; Wed, 17 Jun 2009 07:13:20 -0700 (PDT)
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=[AWL=0.000,  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 kDGExxdEzGUg for <avt@core3.amsl.com>; Wed, 17 Jun 2009 07:13:19 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 7846828C27A for <avt@ietf.org>; Wed, 17 Jun 2009 07:13:19 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,236,1243814400"; d="scan'208";a="37712604"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-4.cisco.com with ESMTP; 17 Jun 2009 14:13:30 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n5HEDTNF018931;  Wed, 17 Jun 2009 07:13:29 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n5HEDTPa019297; Wed, 17 Jun 2009 14:13:29 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 17 Jun 2009 07:13:29 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 17 Jun 2009 07:12:27 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D54098D86E1@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <015201c9ef32$575066a0$05f133e0$%roni@huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] comments on section 10 ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
Thread-Index: AcnupPP7shhfq4AdRG2dZ9bI0Xe2fQABeZQAAAWPwrAAAUCvIAAYQoMwAAt5n9A=
References: <00b801c9eea4$f90f3360$eb2d9a20$%roni@huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D83DD@xmb-sjc-215.amer.cisco.com> <00dc01c9eec3$6a8b3070$3fa19150$%roni@huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D84B9@xmb-sjc-215.amer.cisco.com> <015201c9ef32$575066a0$05f133e0$%roni@huawei.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Roni Even" <Even.roni@huawei.com>, <avt@ietf.org>
X-OriginalArrivalTime: 17 Jun 2009 14:13:29.0362 (UTC) FILETIME=[C9CC0720:01C9EF55]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5981; t=1245248009; x=1246112009; c=relaxed/simple; s=sjdkim3002; 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]=20comments=20on=20section=2010=20 ofdraft-ietf-avt-rapid-acquisition-for-rtp-01 |Sender:=20; bh=Vrbj/ohMzdgAh6Zuo2xP0irTBsaPWJjbiGcBpBT4dC4=; b=tEnLVXnclVl6BK+jjVC7NgCn8yd11b0hn1JyePE08Vk14ZfxjGlklRRte2 72mTsQty4MzjsqZxl3CGfHq2k1a0VGVr7jHR27lNjh61julzyV6s21uqwiyO aewTY3f9eA;
Authentication-Results: sj-dkim-3; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Subject: Re: [AVT] comments on section 10 ofdraft-ietf-avt-rapid-acquisition-for-rtp-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: Wed, 17 Jun 2009 14:13:20 -0000

> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: Wednesday, June 17, 2009 3:00 AM
> To: Ali C. Begen (abegen); avt@ietf.org
> Subject: RE: [AVT] comments on section 10 =
ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
> Ali,
> Thanks, I understand the RAMS-R and RAMS-T port usage and the logic =
behind
> it.
> As for the RAMS-I section 6.2 says
>=20
> " Note that RS learns the IP address information for RR from the
>        RAMS-R message it received.  (This description glosses over the
>        NAT details.  Refer to Section 10 for a discussion of =
NAT-related
>        issues.)"
>=20
> So according to the above if using RTP/RTCP multiplexing, the RTP =
unicast
> stream is sent to the address from which the RAMS-R has arrived.

Yes. Whether there is a NAT or not (or whether muxing is used or not), =
the RAMS-R will always indicate RR's public IP address and RS sends its =
packets to that IP address. But, this part does not say anything =
regarding the ports. The ports to be used depend on whether there is a =
NAT or not and the signaling in the RAMS-R/pubports/etc.

-acbegen

> Roni
>=20
> -----Original Message-----
> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> Sent: Wednesday, June 17, 2009 12:13 AM
> To: Roni Even; avt@ietf.org
> Subject: RE: [AVT] comments on section 10
> ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
> Inline.
>=20
> > -----Original Message-----
> > From: Roni Even [mailto:Even.roni@huawei.com]
> > Sent: Tuesday, June 16, 2009 1:46 PM
> > To: Ali C. Begen (abegen); avt@ietf.org
> > Subject: RE: [AVT] comments on section 10
> ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > Ali,
> > From figure 2 and the text that follows
> >
> > " A Retransmission Source may equally act as a Burst Source.  The
> >    Retransmission Source may also incorporate the Feedback Target
> >    ([I-D.ietf-avt-rtcpssm] permits the feedback target to be a
> >    retransmission server, since it is a logical function to which =
RRs
> >    send their unicast feedback), and we will use the term =
Retransmission
> >    Server (RS) in the remainder of the document to refer to a single
> >    physical entity comprising these three entities that share state.
> >    Note that the same method (with the identical message flows) =
would
> >    also apply in a scenario where rapid acquisition is performed by =
a
> >    feedback target co-located with the media source."
> >
> > I assumed that we are only dealing with the case that the RS is a =
single
> > entity and not three different entities with different addresses
>=20
> You are correct. There is a single retransmission server that does all =
the
> work. Other types of scenarios may be considered in the future.
>=20
> > I also thought that this was agreed in previous discussions
>=20
> Yup.
>=20
>=20
> > If my understanding is not correct I will review the draft since the
> current
> > text is not explicit enough to specify which part is doing each =
message. I
> > saw that RAMS-R is going to feedback target but RAMS-T is going to =
RS
> which
> > is not specifying a specific address according to you.
>=20
> Right, RAMS-T goes to RS as well but it goes to the RTCP port of the =
unicast
> session not the FT of the primary session (since it is to terminate =
the
> unicast burst). What I am trying to say below is different, though, =
which is
> that we cannot make an assumption on the port RR wants to use in the =
unicast
> session (e.g., to receive the burst) based on the port it used for the
> primary session.
>=20
> -acbegen
>=20
>=20
> > Roni
> >
> > -----Original Message-----
> > From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> > Sent: Tuesday, June 16, 2009 10:00 PM
> > To: Roni Even; avt@ietf.org
> > Subject: RE: [AVT] comments on section 10
> > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > Remember that the RAMS-R (RR->RS) message is NOT on the =
retransmission
> > (unicast) session, it's on the primary session since it is sent to =
the
> > feedback target of the primary SSM session. Thus, the source port RR =
uses
> to
> > send RAMS-R "cannot" be assumed to be the destination port it wishes =
to
> > receive the unicast burst on.
> >
> > If you agree with this statement, it is clear why we need port =
signaling.
> > Muxing will not help much here. It will just reduce the number of =
signaled
> > ports from 2 to 1.
> >
> > -acbegen
> >
> >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf =
Of
> Roni
> > Even
> > > Sent: Tuesday, June 16, 2009 10:08 AM
> > > To: avt@ietf.org
> > > Subject: [AVT] comments on section 10
> > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > >
> > > Hi,
> > >
> > > I looked at section 10 and have some comments
> > >
> > >
> > >
> > > 1.       If RTP/RTCP multiplexing is used, there is no need for =
any
> > specific operation
> > > from the RR side. The RR sends the RAMS-R message to the RS from =
the
> port
> > it wants to
> > > receive the RAMS-I and RTP payload. The RS just sends the =
information to
> > the port from
> > > which it received the RAMS-R and not to the one in the SDP
> > >
> > > 2.       In the case where there is no RTP/RTCP multiplexing, the =
RAMS-R
> > RTCP message will
> > > go to the RS and the RAMS-I will go to the port on the RR from =
where the
> > RAMS-R was
> > > received. For the RTP, the RR does not know if it has a NAT on the =
way
> to
> > the RS and
> > > should try to get a routable address (using STUN for example) and
> > providing the port to
> > > the RS ( we still need to agree on how to do it)
> > >
> > > 3.       If the above two points are correct than the RR receive =
port in
> > the SDP is not
> > > really useful
> > >
> > >
> > >
> > > Roni Even


From abegen@cisco.com  Wed Jun 17 07:15:26 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 5DC6E3A6E42 for <avt@core3.amsl.com>; Wed, 17 Jun 2009 07:15:26 -0700 (PDT)
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 QQoCVCEtNCDo for <avt@core3.amsl.com>; Wed, 17 Jun 2009 07:15:24 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 017E63A6E53 for <avt@ietf.org>; Wed, 17 Jun 2009 07:15:23 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,236,1243814400"; d="scan'208";a="325811439"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 17 Jun 2009 14:15:29 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n5HEFTu6001331;  Wed, 17 Jun 2009 07:15:29 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n5HEFT2m027458; Wed, 17 Jun 2009 14:15:29 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 17 Jun 2009 07:15:29 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 17 Jun 2009 07:15:27 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] comments on section 10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQ
References: <mailman.10085.1245185397.4936.avt@ietf.org><238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com><015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>, "Roni Even" <Even.roni@huawei.com>, <avt@ietf.org>
X-OriginalArrivalTime: 17 Jun 2009 14:15:29.0369 (UTC) FILETIME=[1153A490:01C9EF56]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=11851; t=1245248129; x=1246112129; c=relaxed/simple; s=sjdkim1004; 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]=20comments=20on=20section=2010ofd raft-ietf-avt-rapid-acquisition-for-rtp-01 |Sender:=20; bh=62r7uVuq4Ix8qEC/G6F43/GfpLeQKHJR8cqL1xL4x8k=; b=s/atDeb08oKtCW6UAsZrBV6OD8FgHuaYBiJG9BWsdI+eiEi1wC9SbHULy/ WSeY0fknxHzwP8Jga0zstPxnQYTrN0jQd6FaVr1yry83d0sYxL2YZl5ULu73 XM6iG/Rd/w+4mIlV+mUCXZwwzyN1Zkvlv3sHo65+eXFkkG5Prkcg4=;
Authentication-Results: sj-dkim-1; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Subject: Re: [AVT] comments on section 10ofdraft-ietf-avt-rapid-acquisition-for-rtp-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: Wed, 17 Jun 2009 14:15:26 -0000

The proposed text looks good to me. We should probably put the burst and =
retransmission sources in the same block in Figure 2 as well.

-acbegen


> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of =
VAN CAENEGEM Tom
> Sent: Wednesday, June 17, 2009 5:23 AM
> To: Roni Even; avt@ietf.org
> Subject: Re: [AVT] comments on section =
10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
>=20
>  Hi Roni,
>=20
> Perhaps the start of section 6.2 can be rewritten as follows:
>=20
>=20
> <START>
>=20
> 6.2.  Message Flows
>=20
>    Figure 2 shows the main entities involved in rapid acquisition:
>=20
>    o  Multicast Source
>=20
>    o  Feedback Target (FT)
>=20
>    o  Burst/ Retransmission Source
>=20
>    o  RTP Receiver (RR)
>=20
> (fig 2)
>=20
>=20
> The feedback target (FT) is the entity as defined in [rtcpssm draft], =
to
> which the RR sends its RTCP FB messages, indicating packet loss in the
> ssm primary stream by means of a NACK or indicating the RR's desire to
> have rapid acquisition of the ssm primary stream (by means of an RTCP =
FB
> message as defined in this document). While the burst/retransmission
> source is responsible for responding on these messages and, in the =
case
> of rapid acquisition, further RTCP interaction with the RR during this
> acquisition process, it is assumed in the remainder of the document =
that
> these two logical entities (FT and burst/retransmission source) are
> combined in a single physical entity and share state. In the remainder
> of the text, the term retransmission server is used whenever
> appropriate, to refer to the combined functionality of the FT and
> retransmission/burst source. However, it must be noted that only the =
FT
> is involved in the primary ssm RTP session, whereas the
> burst/retransmission source transmits unicast RTP burst and RTP
> retransmissions packets (both formatted  as RTP retransmission packets
> [RFC4585]) in a single separate unicast RTP retransmission session to
> each RR.
>=20
> Note also that the same method (with the identical message flows) =
would
> also apply in a scenario where rapid acquisition is performed by a
> feedback target co-located with the media source.
>=20
> (...)
>=20
> <END>
>=20
> Tom: As we mandate the retransmission source and burst source to be in
> the same session, I think it is no longer required to split-up among
> these two logical entities. I invite other people, including the
> co-authors to comment on this new text proposal.
>=20
> With respect to your comments on the RTP/RTCP port muxing support
> indication by the RR inside the RAMS-R message. That would be needed,
> but is not sufficient as, if only declarative SDP is used, and we want
> to have the possibility that the RTP/RTCP packets in the =
retransmission
> session can be received by the RR on the same port the RR issues the
> RTCP RAMS-R, we need also a way by which the RR can signal this too. =
We
> provided a possible solution in the draft, but I understood that you
> think such a solution should be proposed in a separate draft proposal?
> But I guess that would also apply then to the signaling of support for
> RTP/RTCP port muxing by the RR?
>=20
> Tom
>=20
> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: woensdag 17 juni 2009 13:24
> To: VAN CAENEGEM Tom; avt@ietf.org
> Subject: RE: [AVT] comments on section 10
> ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
> Tom,
> I understand the RAMS-R and RAMS-T, the text is not clear enough in
> section
> 6.2
>=20
> It still leaves open the issue of the addresses for the RR in the case
> of declarative SDP when there is no answer SDP from the RR.
>=20
> About RTP/RTCP multiplexing, the declarative SDP can show that the RS
> supports it and I still think that some information about the =
addressing
> (like support for RTP/RTCP mux) should be supplied in the RAMS-R for =
the
> declarative case.
>=20
> Roni
>=20
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf =
Of
> > VAN CAENEGEM Tom
> > Sent: Wednesday, June 17, 2009 11:17 AM
> > To: avt@ietf.org
> > Subject: Re: [AVT] comments on section 10 of draft-ietf-avt-rapid-
> > acquisition-for-rtp-01
> >
> > Hi Roni,
> >
> > I think your understanding was indeed different from the general
> >assumptions in this draft. Previously we agreed to only consider the
> >case where there is only one physical entity involved (called the
> >Retransmission Server in the draft), which allows us to NOT consider
> >and  discuss cases where for instance the feedback target (which is
> >defined  in the rtcpssm draft/RFC) is not in the same box as the
> >retransmission  source or burst source, the entities sourcing
> >retransmision/burst  packets. In that case we then would also need to
> >describe how these  separate entities communicate.
> > The fact that these different entities are now in the same box does
> >not  necessarily mean that all interactions and data exchange with =
the
> >RRs  is  part of the same RTP session, which is in this case the SSM
> >RTP  session.
> > As Ali explained, the NACK and RAMS-R RTCP FB messages are directed =
to
>=20
> >the FB target, where we do not  defer from the rtcpssm draft. The RTP
> >retransmission/burst packets that are sent as a response to the NACK
> >and  the RAMS-R can be either session multiplexed with respect to the
> >original SSM RTP session or SSRC muxed (same session), following RFC
> >4588.
> >As the retransmission packets in this case are addressing the RR  in
> >unicast, we obviously have a dedicated RTP session for the
> >retransmission/burst packets. We had some internal discussion on
> >whether  considering the use case of having a separate session =
between
> >RS and RR  for RTP retransmission packets triggered by an RTCP FB =
NACK
> >and a  separate session for RTP burst packets triggered by an RTCP
> >RAMS-R made  sense, but we ended up agreeing that allowing a single
> >session was the  easiest way out, without imposing serious =
limitations
> >to the general  architecture.
> >
> > This means that the ports used by the (single) RTP
> > retransmission/burst session are in principle decoupled from the
> > primary SSM session. Hence if an RR wants to receive the
> > burst/retransmission packets and associated RTCP messages on the =
same
> > port the RR sent out the RTCP RAMS-R/ NACK FB messages, this should
> > either be signaled by the RR, OR such port usage scheme is =
considered
> > the "default" case -which also means the RR supports RTP/RTCP port
> > muxing for the retransmission/burst session-, and then the RR needs =
to
>=20
> > signal the ports for receiving the RTP and RTCP packets in the
> > retransmission session when it requires dedicated ports.
> >
> > The RAMS-I (RS-> RR) and RAMS-T (RR-> RS) messages are only relevant
> > to a specific RR requesting the RTP burst stream and the RS, and =
carry
>=20
> > information/signaling related to the retransmission/burst session =
and
> > have nothing to do with the SSM session. Hence the FB target as
> > logical entity is not involved here.
> >
> > I hope this clarifies rather than it contributes to your confusion.
> > But we may need to rephrase the part you quoted, as your
> > interpretation was different from its intended meaning. We also =
tried
> > to be more explicit in which session which RAMS or other RTCP (e.g.
> > Bye) messages needed to be exchanged compared to a previous version =
of
>=20
> > the draft, but we are open of course to any other suggestions from
> > your side if this is not clear enough in your opinion.
> >
> > Tom
> >
> >
> >
> >
> >
> >
> > " A Retransmission Source may equally act as a Burst Source.  The
> >    Retransmission Source may also incorporate the Feedback Target
> >    ([I-D.ietf-avt-rtcpssm] permits the feedback target to be a
> >    retransmission server, since it is a logical function to which =
RRs
> >    send their unicast feedback), and we will use the term
> > Retransmission
> >    Server (RS) in the remainder of the document to refer to a single
> >    physical entity comprising these three entities that share state.
> >    Note that the same method (with the identical message flows) =
would
> >    also apply in a scenario where rapid acquisition is performed by =
a
> >    feedback target co-located with the media source."
> >
> > I assumed that we are only dealing with the case that the RS is a
> > single entity and not three different entities with different
> > addresses
> >
> > I also thought that this was agreed in previous discussions
> >
> > If my understanding is not correct I will review the draft since the
> > current text is not explicit enough to specify which part is doing
> > each message. I saw that RAMS-R is going to feedback target but =
RAMS-T
>=20
> > is going to RS which is not specifying a specific address according =
to
>=20
> > you.
> >
> > Roni
> >
> > -----Original Message-----
> > From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> > Sent: Tuesday, June 16, 2009 10:00 PM
> > To: Roni Even; avt@ietf.org
> > Subject: RE: [AVT] comments on section 10
> > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > Remember that the RAMS-R (RR->RS) message is NOT on the =
retransmission
> > (unicast) session, it's on the primary session since it is sent to =
the
>=20
> > feedback target of the primary SSM session. Thus, the source port RR
> > uses to send RAMS-R "cannot" be assumed to be the destination port =
it
> > wishes to receive the unicast burst on.
> >
> > If you agree with this statement, it is clear why we need port
> > signaling.
> > Muxing will not help much here. It will just reduce the number of
> > signaled ports from 2 to 1.
> >
> > -acbegen
> >
> >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
> > > Of Roni
> > Even
> > > Sent: Tuesday, June 16, 2009 10:08 AM
> > > To: avt@ietf.org
> > > Subject: [AVT] comments on section 10
> > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > >
> > > Hi,
> > >
> > > I looked at section 10 and have some comments
> > >
> > >
> > >
> > > 1.       If RTP/RTCP multiplexing is used, there is no need for =
any
> > specific operation
> > > from the RR side. The RR sends the RAMS-R message to the RS from =
the
>=20
> > > port
> > it wants to
> > > receive the RAMS-I and RTP payload. The RS just sends the
> > > information to
> > the port from
> > > which it received the RAMS-R and not to the one in the SDP
> > >
> > > 2.       In the case where there is no RTP/RTCP multiplexing, the
> > RAMS-R
> > RTCP message will
> > > go to the RS and the RAMS-I will go to the port on the RR from =
where
>=20
> > > the
> > RAMS-R was
> > > received. For the RTP, the RR does not know if it has a NAT on the
> > way
> >
> > > to
> > the RS and
> > > should try to get a routable address (using STUN for example) and
> > providing the port to
> > > the RS ( we still need to agree on how to do it)
> > >
> > > 3.       If the above two points are correct than the RR receive
> port
> > in
> > the SDP is not
> > > really useful
> > >
> > >
> > >
> > > Roni Even
> >
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt

From Even.roni@huawei.com  Wed Jun 17 07:37:34 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C04D3A685E for <avt@core3.amsl.com>; Wed, 17 Jun 2009 07:37:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.411
X-Spam-Level: 
X-Spam-Status: No, score=-1.411 tagged_above=-999 required=5 tests=[AWL=0.569,  BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KSZx5H2oY7LF for <avt@core3.amsl.com>; Wed, 17 Jun 2009 07:37:28 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 4AEEB3A69BB for <avt@ietf.org>; Wed, 17 Jun 2009 07:37:28 -0700 (PDT)
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 <0KLE00D580K24D@szxga03-in.huawei.com> for avt@ietf.org; Wed, 17 Jun 2009 22:36:02 +0800 (CST)
Received: from huawei.com ([172.24.1.3]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLE002D10K2RE@szxga03-in.huawei.com> for avt@ietf.org; Wed, 17 Jun 2009 22:36:02 +0800 (CST)
Received: from windows8d787f9 (bzq-79-179-78-100.red.bezeqint.net [79.179.78.100]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KLE00IU40JSWI@szxml01-in.huawei.com>; Wed, 17 Jun 2009 22:36:02 +0800 (CST)
Date: Wed, 17 Jun 2009 17:33:47 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <4A360A7E.4090400@hhi.fraunhofer.de>
To: 'Thomas Schierl' <Thomas.Schierl@hhi.fraunhofer.de>, 'avt' <avt@ietf.org>
Message-id: <01a201c9ef58$ba490d40$2edb27c0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: Acntllq9OLGNiUiOQUGlLJVvGmbjNABwXfzA
References: <4A360A7E.4090400@hhi.fraunhofer.de>
Cc: 'Roni Even' <ron.even.tlv@gmail.com>, 'Tom Taylor' <tom.taylor@rogers.com>, 'Colin Perkins' <csp@csperkins.org>
Subject: Re: [AVT] [Fwd: I-D Action:draft-ietf-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: Wed, 17 Jun 2009 14:37:34 -0000

Thomas,
I read the draft, the major comment I have is that section 4.3 looks to me
like it describe one use case and should be in formational. It just repeats
text from SVC. Maybe, if you want to have it, it should be a separate
section that will be specified as an informational section.
Roni

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Thomas Schierl
> Sent: Monday, June 15, 2009 11:47 AM
> To: avt
> Cc: Roni Even; Tom Taylor; Colin Perkins
> Subject: [AVT] [Fwd: I-D Action:draft-ietf-avt-rapid-rtp-sync-02.txt]
> 
> Dear all,
> 
> Please find pointer to the revised version -02 of draft-ietf-avt-rapid-
> rtp-sync below.
> 
> We addressed the reaming open issues and completed all sections.
> 
> Any comments are welcome. Due to the timing constraints, we would like
> to ask if we can go ahead with WGLC for this draft.
> 
> Best regards,
> Thomas
> 
> --
> Thomas Schierl
> --------------
> Fraunhofer HHI
> 
> 
> ---
> Visit us at
> 
> IEEE ICC 2009 / June 14-18 / Dresden, Germany / International Congress
> Center
> http://www.hhi.fraunhofer.de/icc
> 
> Laser World of Photonics 2009 / June 15-18 / Munich, Germay / Hall B1,
> Booth 461
> http://world-of-photonics.net/de/laser/start


From Even.roni@huawei.com  Wed Jun 17 07:43:19 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4275528C26A for <avt@core3.amsl.com>; Wed, 17 Jun 2009 07:43:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.506
X-Spam-Level: 
X-Spam-Status: No, score=-1.506 tagged_above=-999 required=5 tests=[AWL=0.474,  BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1iT0iP7W7HVf for <avt@core3.amsl.com>; Wed, 17 Jun 2009 07:43:13 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 2F91D28B56A for <avt@ietf.org>; Wed, 17 Jun 2009 07:43:13 -0700 (PDT)
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 <0KLE00D2W0UZ4E@szxga03-in.huawei.com> for avt@ietf.org; Wed, 17 Jun 2009 22:42:35 +0800 (CST)
Received: from huawei.com ([172.24.1.6]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLE001MW0UZ6T@szxga03-in.huawei.com> for avt@ietf.org; Wed, 17 Jun 2009 22:42:35 +0800 (CST)
Received: from windows8d787f9 (bzq-79-179-78-100.red.bezeqint.net [79.179.78.100]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KLE00G3Z0UNFD@szxml02-in.huawei.com>; Wed, 17 Jun 2009 22:42:35 +0800 (CST)
Date: Wed, 17 Jun 2009 17:40:51 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <4A360A7E.4090400@hhi.fraunhofer.de>
To: 'Thomas Schierl' <Thomas.Schierl@hhi.fraunhofer.de>, 'avt' <avt@ietf.org>
Message-id: <01a301c9ef59$a4322f90$ec968eb0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: Acntllq9OLGNiUiOQUGlLJVvGmbjNABwffaQ
References: <4A360A7E.4090400@hhi.fraunhofer.de>
Cc: 'Roni Even' <ron.even.tlv@gmail.com>, 'Tom Taylor' <tom.taylor@rogers.com>, 'Colin Perkins' <csp@csperkins.org>
Subject: Re: [AVT] [Fwd: I-D Action:draft-ietf-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: Wed, 17 Jun 2009 14:43:19 -0000

Hi,
I will wait for your response to the last email from Mike. 
I will try to start WGLC next week
Roni

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Thomas Schierl
> Sent: Monday, June 15, 2009 11:47 AM
> To: avt
> Cc: Roni Even; Tom Taylor; Colin Perkins
> Subject: [AVT] [Fwd: I-D Action:draft-ietf-avt-rapid-rtp-sync-02.txt]
> 
> Dear all,
> 
> Please find pointer to the revised version -02 of draft-ietf-avt-rapid-
> rtp-sync below.
> 
> We addressed the reaming open issues and completed all sections.
> 
> Any comments are welcome. Due to the timing constraints, we would like
> to ask if we can go ahead with WGLC for this draft.
> 
> Best regards,
> Thomas
> 
> --
> Thomas Schierl
> --------------
> Fraunhofer HHI
> 
> 
> ---
> Visit us at
> 
> IEEE ICC 2009 / June 14-18 / Dresden, Germany / International Congress
> Center
> http://www.hhi.fraunhofer.de/icc
> 
> Laser World of Photonics 2009 / June 15-18 / Munich, Germay / Hall B1,
> Booth 461
> http://world-of-photonics.net/de/laser/start


From versteb@cisco.com  Wed Jun 17 08:39:54 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 148733A6E50 for <avt@core3.amsl.com>; Wed, 17 Jun 2009 08:39:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.699
X-Spam-Level: 
X-Spam-Status: No, score=-6.699 tagged_above=-999 required=5 tests=[AWL=-0.100, 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 DoJmiE997Cwo for <avt@core3.amsl.com>; Wed, 17 Jun 2009 08:39:52 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 1C7CB3A6D6B for <avt@ietf.org>; Wed, 17 Jun 2009 08:39:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,236,1243814400"; d="scan'208";a="47638321"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 17 Jun 2009 15:40:02 +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 n5HFe290004222;  Wed, 17 Jun 2009 11:40:02 -0400
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 n5HFe2kF014540; Wed, 17 Jun 2009 15:40:02 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.3959);  Wed, 17 Jun 2009 11:40:02 -0400
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: Wed, 17 Jun 2009 11:40:00 -0400
Message-ID: <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzA=
References: <mailman.10085.1245185397.4936.avt@ietf.org><238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com><015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com><238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com>
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "Ali C. Begen (abegen)" <abegen@cisco.com>, "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>, "Roni Even" <Even.roni@huawei.com>, <avt@ietf.org>, <zeevvax@microsoft.com>
X-OriginalArrivalTime: 17 Jun 2009 15:40:02.0157 (UTC) FILETIME=[E0F1A9D0:01C9EF61]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=13003; t=1245253202; x=1246117202; 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=20[AVT]=20comments=20on=20section10ofdraf t-ietf-avt-rapid-acquisition-for-rtp-01 |Sender:=20 |To:=20=22Ali=20C.=20Begen=20(abegen)=22=20<abegen@cisco.co m>,=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=22Roni=20Even=22=20<Even.roni@huawei.com>,=20<avt@ietf.o rg>,=0A=20=20=20=20=20=20=20=20<zeevvax@microsoft.com>; bh=EkWXs3QnQNtqWFqurELRLrWJ4ZtN374wHcFmKNL+fkU=; b=Mut8vSUi60dzLX7Qw6cnsuNcC3bc5rHfmmPhM7LQuRjXEMovumcqeeQEKv XewmDzX9KKjvcSAuYTczFnNT1NlxRS2g49nreZu8uMyrP0TTISocp8/fQqcI QSqW/mYmgt;
Authentication-Results: rtp-dkim-2; header.From=versteb@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); 
Subject: Re: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-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: Wed, 17 Jun 2009 15:39:54 -0000

Tom-

These words looks good to me as well, with the following clarification.=20

We do need to consider how we handle RTP/RTCP port muxing throughout the
document, and make the wording consistent wherever we reference the
ports in use. I am in favor of allowing (but not mandating) the RR to
signal RTP/RTCP port muxing. This would require the RS to support both
methods. This is just my opinion, and we need to come to consensus on
this matter.


Bill VerSteeg

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Ali C. Begen (abegen)
Sent: Wednesday, June 17, 2009 10:15 AM
To: VAN CAENEGEM Tom; Roni Even; avt@ietf.org
Subject: Re: [AVT] comments on
section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01

The proposed text looks good to me. We should probably put the burst and
retransmission sources in the same block in Figure 2 as well.

-acbegen


> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of=20
> VAN CAENEGEM Tom
> Sent: Wednesday, June 17, 2009 5:23 AM
> To: Roni Even; avt@ietf.org
> Subject: Re: [AVT] comments on section=20
> 10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
>=20
>  Hi Roni,
>=20
> Perhaps the start of section 6.2 can be rewritten as follows:
>=20
>=20
> <START>
>=20
> 6.2.  Message Flows
>=20
>    Figure 2 shows the main entities involved in rapid acquisition:
>=20
>    o  Multicast Source
>=20
>    o  Feedback Target (FT)
>=20
>    o  Burst/ Retransmission Source
>=20
>    o  RTP Receiver (RR)
>=20
> (fig 2)
>=20
>=20
> The feedback target (FT) is the entity as defined in [rtcpssm draft],=20
> to which the RR sends its RTCP FB messages, indicating packet loss in=20
> the ssm primary stream by means of a NACK or indicating the RR's=20
> desire to have rapid acquisition of the ssm primary stream (by means=20
> of an RTCP FB message as defined in this document). While the=20
> burst/retransmission source is responsible for responding on these=20
> messages and, in the case of rapid acquisition, further RTCP=20
> interaction with the RR during this acquisition process, it is assumed

> in the remainder of the document that these two logical entities (FT=20
> and burst/retransmission source) are combined in a single physical=20
> entity and share state. In the remainder of the text, the term=20
> retransmission server is used whenever appropriate, to refer to the=20
> combined functionality of the FT and retransmission/burst source.=20
> However, it must be noted that only the FT is involved in the primary=20
> ssm RTP session, whereas the burst/retransmission source transmits=20
> unicast RTP burst and RTP retransmissions packets (both formatted  as=20
> RTP retransmission packets
> [RFC4585]) in a single separate unicast RTP retransmission session to=20
> each RR.
>=20
> Note also that the same method (with the identical message flows)=20
> would also apply in a scenario where rapid acquisition is performed by

> a feedback target co-located with the media source.
>=20
> (...)
>=20
> <END>
>=20
> Tom: As we mandate the retransmission source and burst source to be in

> the same session, I think it is no longer required to split-up among=20
> these two logical entities. I invite other people, including the=20
> co-authors to comment on this new text proposal.
>=20
> With respect to your comments on the RTP/RTCP port muxing support=20
> indication by the RR inside the RAMS-R message. That would be needed,=20
> but is not sufficient as, if only declarative SDP is used, and we want

> to have the possibility that the RTP/RTCP packets in the=20
> retransmission session can be received by the RR on the same port the=20
> RR issues the RTCP RAMS-R, we need also a way by which the RR can=20
> signal this too. We provided a possible solution in the draft, but I=20
> understood that you think such a solution should be proposed in a
separate draft proposal?
> But I guess that would also apply then to the signaling of support for

> RTP/RTCP port muxing by the RR?
>=20
> Tom
>=20
> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: woensdag 17 juni 2009 13:24
> To: VAN CAENEGEM Tom; avt@ietf.org
> Subject: RE: [AVT] comments on section 10
> ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
> Tom,
> I understand the RAMS-R and RAMS-T, the text is not clear enough in=20
> section
> 6.2
>=20
> It still leaves open the issue of the addresses for the RR in the case

> of declarative SDP when there is no answer SDP from the RR.
>=20
> About RTP/RTCP multiplexing, the declarative SDP can show that the RS=20
> supports it and I still think that some information about the=20
> addressing (like support for RTP/RTCP mux) should be supplied in the=20
> RAMS-R for the declarative case.
>=20
> Roni
>=20
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf=20
> > Of VAN CAENEGEM Tom
> > Sent: Wednesday, June 17, 2009 11:17 AM
> > To: avt@ietf.org
> > Subject: Re: [AVT] comments on section 10 of draft-ietf-avt-rapid-
> > acquisition-for-rtp-01
> >
> > Hi Roni,
> >
> > I think your understanding was indeed different from the general=20
> >assumptions in this draft. Previously we agreed to only consider the=20
> >case where there is only one physical entity involved (called the=20
> >Retransmission Server in the draft), which allows us to NOT consider=20
> >and  discuss cases where for instance the feedback target (which is=20
> >defined  in the rtcpssm draft/RFC) is not in the same box as the=20
> >retransmission  source or burst source, the entities sourcing=20
> >retransmision/burst  packets. In that case we then would also need to

> >describe how these  separate entities communicate.
> > The fact that these different entities are now in the same box does=20
> >not  necessarily mean that all interactions and data exchange with=20
> >the RRs  is  part of the same RTP session, which is in this case the=20
> >SSM RTP  session.
> > As Ali explained, the NACK and RAMS-R RTCP FB messages are directed=20
> >to
>=20
> >the FB target, where we do not  defer from the rtcpssm draft. The RTP

> >retransmission/burst packets that are sent as a response to the NACK=20
> >and  the RAMS-R can be either session multiplexed with respect to the

> >original SSM RTP session or SSRC muxed (same session), following RFC=20
> >4588.
> >As the retransmission packets in this case are addressing the RR  in=20
> >unicast, we obviously have a dedicated RTP session for the=20
> >retransmission/burst packets. We had some internal discussion on=20
> >whether  considering the use case of having a separate session=20
> >between RS and RR  for RTP retransmission packets triggered by an=20
> >RTCP FB NACK and a  separate session for RTP burst packets triggered=20
> >by an RTCP RAMS-R made  sense, but we ended up agreeing that allowing

> >a single session was the  easiest way out, without imposing serious=20
> >limitations to the general  architecture.
> >
> > This means that the ports used by the (single) RTP=20
> > retransmission/burst session are in principle decoupled from the=20
> > primary SSM session. Hence if an RR wants to receive the=20
> > burst/retransmission packets and associated RTCP messages on the=20
> > same port the RR sent out the RTCP RAMS-R/ NACK FB messages, this=20
> > should either be signaled by the RR, OR such port usage scheme is=20
> > considered the "default" case -which also means the RR supports=20
> > RTP/RTCP port muxing for the retransmission/burst session-, and then

> > the RR needs to
>=20
> > signal the ports for receiving the RTP and RTCP packets in the=20
> > retransmission session when it requires dedicated ports.
> >
> > The RAMS-I (RS-> RR) and RAMS-T (RR-> RS) messages are only relevant

> > to a specific RR requesting the RTP burst stream and the RS, and=20
> > carry
>=20
> > information/signaling related to the retransmission/burst session=20
> > and have nothing to do with the SSM session. Hence the FB target as=20
> > logical entity is not involved here.
> >
> > I hope this clarifies rather than it contributes to your confusion.
> > But we may need to rephrase the part you quoted, as your=20
> > interpretation was different from its intended meaning. We also=20
> > tried to be more explicit in which session which RAMS or other RTCP
(e.g.
> > Bye) messages needed to be exchanged compared to a previous version=20
> > of
>=20
> > the draft, but we are open of course to any other suggestions from=20
> > your side if this is not clear enough in your opinion.
> >
> > Tom
> >
> >
> >
> >
> >
> >
> > " A Retransmission Source may equally act as a Burst Source.  The
> >    Retransmission Source may also incorporate the Feedback Target
> >    ([I-D.ietf-avt-rtcpssm] permits the feedback target to be a
> >    retransmission server, since it is a logical function to which
RRs
> >    send their unicast feedback), and we will use the term=20
> > Retransmission
> >    Server (RS) in the remainder of the document to refer to a single
> >    physical entity comprising these three entities that share state.
> >    Note that the same method (with the identical message flows)
would
> >    also apply in a scenario where rapid acquisition is performed by
a
> >    feedback target co-located with the media source."
> >
> > I assumed that we are only dealing with the case that the RS is a=20
> > single entity and not three different entities with different=20
> > addresses
> >
> > I also thought that this was agreed in previous discussions
> >
> > If my understanding is not correct I will review the draft since the

> > current text is not explicit enough to specify which part is doing=20
> > each message. I saw that RAMS-R is going to feedback target but=20
> > RAMS-T
>=20
> > is going to RS which is not specifying a specific address according=20
> > to
>=20
> > you.
> >
> > Roni
> >
> > -----Original Message-----
> > From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> > Sent: Tuesday, June 16, 2009 10:00 PM
> > To: Roni Even; avt@ietf.org
> > Subject: RE: [AVT] comments on section 10
> > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > Remember that the RAMS-R (RR->RS) message is NOT on the=20
> > retransmission
> > (unicast) session, it's on the primary session since it is sent to=20
> > the
>=20
> > feedback target of the primary SSM session. Thus, the source port RR

> > uses to send RAMS-R "cannot" be assumed to be the destination port=20
> > it wishes to receive the unicast burst on.
> >
> > If you agree with this statement, it is clear why we need port=20
> > signaling.
> > Muxing will not help much here. It will just reduce the number of=20
> > signaled ports from 2 to 1.
> >
> > -acbegen
> >
> >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf

> > > Of Roni
> > Even
> > > Sent: Tuesday, June 16, 2009 10:08 AM
> > > To: avt@ietf.org
> > > Subject: [AVT] comments on section 10
> > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > >
> > > Hi,
> > >
> > > I looked at section 10 and have some comments
> > >
> > >
> > >
> > > 1.       If RTP/RTCP multiplexing is used, there is no need for
any
> > specific operation
> > > from the RR side. The RR sends the RAMS-R message to the RS from=20
> > > the
>=20
> > > port
> > it wants to
> > > receive the RAMS-I and RTP payload. The RS just sends the=20
> > > information to
> > the port from
> > > which it received the RAMS-R and not to the one in the SDP
> > >
> > > 2.       In the case where there is no RTP/RTCP multiplexing, the
> > RAMS-R
> > RTCP message will
> > > go to the RS and the RAMS-I will go to the port on the RR from=20
> > > where
>=20
> > > the
> > RAMS-R was
> > > received. For the RTP, the RR does not know if it has a NAT on the
> > way
> >
> > > to
> > the RS and
> > > should try to get a routable address (using STUN for example) and
> > providing the port to
> > > the RS ( we still need to agree on how to do it)
> > >
> > > 3.       If the above two points are correct than the RR receive
> port
> > in
> > the SDP is not
> > > really useful
> > >
> > >
> > >
> > > Roni Even
> >
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt

From zeevvax@microsoft.com  Wed Jun 17 10:15:06 2009
Return-Path: <zeevvax@microsoft.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 305AC3A6BF7 for <avt@core3.amsl.com>; Wed, 17 Jun 2009 10:15:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 dkeq9-S0YzYp for <avt@core3.amsl.com>; Wed, 17 Jun 2009 10:15:04 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id 865F83A6A7E for <avt@ietf.org>; Wed, 17 Jun 2009 10:15:04 -0700 (PDT)
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (157.54.79.159) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.99.4; Wed, 17 Jun 2009 09:57:33 -0700
Received: from tk5ex14mbxc105.redmond.corp.microsoft.com ([157.54.79.177]) by TK5EX14MLTC104.redmond.corp.microsoft.com ([157.54.79.159]) with mapi; Wed, 17 Jun 2009 09:45:00 -0700
From: Zeev Vax <zeevvax@microsoft.com>
To: "Bill Ver Steeg (versteb)" <versteb@cisco.com>, "Ali C. Begen (abegen)" <abegen@cisco.com>, VAN CAENEGEM Tom <Tom.Van_Caenegem@alcatel-lucent.be>,  Roni Even <Even.roni@huawei.com>, "avt@ietf.org" <avt@ietf.org>
Thread-Topic: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4A==
Date: Wed, 17 Jun 2009 16:44:52 +0000
Message-ID: <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com>
References: <mailman.10085.1245185397.4936.avt@ietf.org><238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com><015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com><238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com>
In-Reply-To: <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-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: Wed, 17 Jun 2009 17:15:06 -0000

The text proposal looks fine to me.
I don't think we should mandate support both, this would cause extra work i=
n implementation of a solution, and I can't see any benefit. Giving that th=
is is UDP traffic port muxing is a subset of separate ports, so we can mand=
ate port muxing, and make optional the separate ports.

Zeev


-----Original Message-----
From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
Sent: Wednesday, June 17, 2009 8:40 AM
To: Ali C. Begen (abegen); VAN CAENEGEM Tom; Roni Even; avt@ietf.org; Zeev =
Vax
Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisition-=
for-rtp-01

Tom-

These words looks good to me as well, with the following clarification.

We do need to consider how we handle RTP/RTCP port muxing throughout the
document, and make the wording consistent wherever we reference the
ports in use. I am in favor of allowing (but not mandating) the RR to
signal RTP/RTCP port muxing. This would require the RS to support both
methods. This is just my opinion, and we need to come to consensus on
this matter.


Bill VerSteeg

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Ali C. Begen (abegen)
Sent: Wednesday, June 17, 2009 10:15 AM
To: VAN CAENEGEM Tom; Roni Even; avt@ietf.org
Subject: Re: [AVT] comments on
section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01

The proposed text looks good to me. We should probably put the burst and
retransmission sources in the same block in Figure 2 as well.

-acbegen


> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> VAN CAENEGEM Tom
> Sent: Wednesday, June 17, 2009 5:23 AM
> To: Roni Even; avt@ietf.org
> Subject: Re: [AVT] comments on section
> 10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>
>
>  Hi Roni,
>
> Perhaps the start of section 6.2 can be rewritten as follows:
>
>
> <START>
>
> 6.2.  Message Flows
>
>    Figure 2 shows the main entities involved in rapid acquisition:
>
>    o  Multicast Source
>
>    o  Feedback Target (FT)
>
>    o  Burst/ Retransmission Source
>
>    o  RTP Receiver (RR)
>
> (fig 2)
>
>
> The feedback target (FT) is the entity as defined in [rtcpssm draft],
> to which the RR sends its RTCP FB messages, indicating packet loss in
> the ssm primary stream by means of a NACK or indicating the RR's
> desire to have rapid acquisition of the ssm primary stream (by means
> of an RTCP FB message as defined in this document). While the
> burst/retransmission source is responsible for responding on these
> messages and, in the case of rapid acquisition, further RTCP
> interaction with the RR during this acquisition process, it is assumed

> in the remainder of the document that these two logical entities (FT
> and burst/retransmission source) are combined in a single physical
> entity and share state. In the remainder of the text, the term
> retransmission server is used whenever appropriate, to refer to the
> combined functionality of the FT and retransmission/burst source.
> However, it must be noted that only the FT is involved in the primary
> ssm RTP session, whereas the burst/retransmission source transmits
> unicast RTP burst and RTP retransmissions packets (both formatted  as
> RTP retransmission packets
> [RFC4585]) in a single separate unicast RTP retransmission session to
> each RR.
>
> Note also that the same method (with the identical message flows)
> would also apply in a scenario where rapid acquisition is performed by

> a feedback target co-located with the media source.
>
> (...)
>
> <END>
>
> Tom: As we mandate the retransmission source and burst source to be in

> the same session, I think it is no longer required to split-up among
> these two logical entities. I invite other people, including the
> co-authors to comment on this new text proposal.
>
> With respect to your comments on the RTP/RTCP port muxing support
> indication by the RR inside the RAMS-R message. That would be needed,
> but is not sufficient as, if only declarative SDP is used, and we want

> to have the possibility that the RTP/RTCP packets in the
> retransmission session can be received by the RR on the same port the
> RR issues the RTCP RAMS-R, we need also a way by which the RR can
> signal this too. We provided a possible solution in the draft, but I
> understood that you think such a solution should be proposed in a
separate draft proposal?
> But I guess that would also apply then to the signaling of support for

> RTP/RTCP port muxing by the RR?
>
> Tom
>
> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: woensdag 17 juni 2009 13:24
> To: VAN CAENEGEM Tom; avt@ietf.org
> Subject: RE: [AVT] comments on section 10
> ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>
> Tom,
> I understand the RAMS-R and RAMS-T, the text is not clear enough in
> section
> 6.2
>
> It still leaves open the issue of the addresses for the RR in the case

> of declarative SDP when there is no answer SDP from the RR.
>
> About RTP/RTCP multiplexing, the declarative SDP can show that the RS
> supports it and I still think that some information about the
> addressing (like support for RTP/RTCP mux) should be supplied in the
> RAMS-R for the declarative case.
>
> Roni
>
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
> > Of VAN CAENEGEM Tom
> > Sent: Wednesday, June 17, 2009 11:17 AM
> > To: avt@ietf.org
> > Subject: Re: [AVT] comments on section 10 of draft-ietf-avt-rapid-
> > acquisition-for-rtp-01
> >
> > Hi Roni,
> >
> > I think your understanding was indeed different from the general
> >assumptions in this draft. Previously we agreed to only consider the
> >case where there is only one physical entity involved (called the
> >Retransmission Server in the draft), which allows us to NOT consider
> >and  discuss cases where for instance the feedback target (which is
> >defined  in the rtcpssm draft/RFC) is not in the same box as the
> >retransmission  source or burst source, the entities sourcing
> >retransmision/burst  packets. In that case we then would also need to

> >describe how these  separate entities communicate.
> > The fact that these different entities are now in the same box does
> >not  necessarily mean that all interactions and data exchange with
> >the RRs  is  part of the same RTP session, which is in this case the
> >SSM RTP  session.
> > As Ali explained, the NACK and RAMS-R RTCP FB messages are directed
> >to
>
> >the FB target, where we do not  defer from the rtcpssm draft. The RTP

> >retransmission/burst packets that are sent as a response to the NACK
> >and  the RAMS-R can be either session multiplexed with respect to the

> >original SSM RTP session or SSRC muxed (same session), following RFC
> >4588.
> >As the retransmission packets in this case are addressing the RR  in
> >unicast, we obviously have a dedicated RTP session for the
> >retransmission/burst packets. We had some internal discussion on
> >whether  considering the use case of having a separate session
> >between RS and RR  for RTP retransmission packets triggered by an
> >RTCP FB NACK and a  separate session for RTP burst packets triggered
> >by an RTCP RAMS-R made  sense, but we ended up agreeing that allowing

> >a single session was the  easiest way out, without imposing serious
> >limitations to the general  architecture.
> >
> > This means that the ports used by the (single) RTP
> > retransmission/burst session are in principle decoupled from the
> > primary SSM session. Hence if an RR wants to receive the
> > burst/retransmission packets and associated RTCP messages on the
> > same port the RR sent out the RTCP RAMS-R/ NACK FB messages, this
> > should either be signaled by the RR, OR such port usage scheme is
> > considered the "default" case -which also means the RR supports
> > RTP/RTCP port muxing for the retransmission/burst session-, and then

> > the RR needs to
>
> > signal the ports for receiving the RTP and RTCP packets in the
> > retransmission session when it requires dedicated ports.
> >
> > The RAMS-I (RS-> RR) and RAMS-T (RR-> RS) messages are only relevant

> > to a specific RR requesting the RTP burst stream and the RS, and
> > carry
>
> > information/signaling related to the retransmission/burst session
> > and have nothing to do with the SSM session. Hence the FB target as
> > logical entity is not involved here.
> >
> > I hope this clarifies rather than it contributes to your confusion.
> > But we may need to rephrase the part you quoted, as your
> > interpretation was different from its intended meaning. We also
> > tried to be more explicit in which session which RAMS or other RTCP
(e.g.
> > Bye) messages needed to be exchanged compared to a previous version
> > of
>
> > the draft, but we are open of course to any other suggestions from
> > your side if this is not clear enough in your opinion.
> >
> > Tom
> >
> >
> >
> >
> >
> >
> > " A Retransmission Source may equally act as a Burst Source.  The
> >    Retransmission Source may also incorporate the Feedback Target
> >    ([I-D.ietf-avt-rtcpssm] permits the feedback target to be a
> >    retransmission server, since it is a logical function to which
RRs
> >    send their unicast feedback), and we will use the term
> > Retransmission
> >    Server (RS) in the remainder of the document to refer to a single
> >    physical entity comprising these three entities that share state.
> >    Note that the same method (with the identical message flows)
would
> >    also apply in a scenario where rapid acquisition is performed by
a
> >    feedback target co-located with the media source."
> >
> > I assumed that we are only dealing with the case that the RS is a
> > single entity and not three different entities with different
> > addresses
> >
> > I also thought that this was agreed in previous discussions
> >
> > If my understanding is not correct I will review the draft since the

> > current text is not explicit enough to specify which part is doing
> > each message. I saw that RAMS-R is going to feedback target but
> > RAMS-T
>
> > is going to RS which is not specifying a specific address according
> > to
>
> > you.
> >
> > Roni
> >
> > -----Original Message-----
> > From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> > Sent: Tuesday, June 16, 2009 10:00 PM
> > To: Roni Even; avt@ietf.org
> > Subject: RE: [AVT] comments on section 10
> > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > Remember that the RAMS-R (RR->RS) message is NOT on the
> > retransmission
> > (unicast) session, it's on the primary session since it is sent to
> > the
>
> > feedback target of the primary SSM session. Thus, the source port RR

> > uses to send RAMS-R "cannot" be assumed to be the destination port
> > it wishes to receive the unicast burst on.
> >
> > If you agree with this statement, it is clear why we need port
> > signaling.
> > Muxing will not help much here. It will just reduce the number of
> > signaled ports from 2 to 1.
> >
> > -acbegen
> >
> >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf

> > > Of Roni
> > Even
> > > Sent: Tuesday, June 16, 2009 10:08 AM
> > > To: avt@ietf.org
> > > Subject: [AVT] comments on section 10
> > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > >
> > > Hi,
> > >
> > > I looked at section 10 and have some comments
> > >
> > >
> > >
> > > 1.       If RTP/RTCP multiplexing is used, there is no need for
any
> > specific operation
> > > from the RR side. The RR sends the RAMS-R message to the RS from
> > > the
>
> > > port
> > it wants to
> > > receive the RAMS-I and RTP payload. The RS just sends the
> > > information to
> > the port from
> > > which it received the RAMS-R and not to the one in the SDP
> > >
> > > 2.       In the case where there is no RTP/RTCP multiplexing, the
> > RAMS-R
> > RTCP message will
> > > go to the RS and the RAMS-I will go to the port on the RR from
> > > where
>
> > > the
> > RAMS-R was
> > > received. For the RTP, the RR does not know if it has a NAT on the
> > way
> >
> > > to
> > the RS and
> > > should try to get a routable address (using STUN for example) and
> > providing the port to
> > > the RS ( we still need to agree on how to do it)
> > >
> > > 3.       If the above two points are correct than the RR receive
> port
> > in
> > the SDP is not
> > > really useful
> > >
> > >
> > >
> > > Roni Even
> >
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt


From csp@csperkins.org  Wed Jun 17 10:56:57 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 72D7F3A6BD8 for <avt@core3.amsl.com>; Wed, 17 Jun 2009 10:56:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 5xHQz3gkADCR for <avt@core3.amsl.com>; Wed, 17 Jun 2009 10:56:56 -0700 (PDT)
Received: from anchor-msapost-1.mail.demon.net (anchor-msapost-1.mail.demon.net [195.173.77.164]) by core3.amsl.com (Postfix) with ESMTP id B3FDE3A6E9D for <avt@ietf.org>; Wed, 17 Jun 2009 10:56:55 -0700 (PDT)
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]) by anchor-post-1.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1MGzNe-0003eo-ij; Wed, 17 Jun 2009 17:57:02 +0000
Message-Id: <B5806023-20A3-4868-9195-7FA0D4D62053@csperkins.org>
From: Colin Perkins <csp@csperkins.org>
To: Michael A Dolan <md.1@newtbt.com>
In-Reply-To: <0MKpCa-1MGfai3tWQ-000d7b@mrelay.perfora.net>
Content-Type: multipart/alternative; boundary=Apple-Mail-23-666249745
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 17 Jun 2009 18:57:01 +0100
References: <20090309171502.518513A6359@core3.amsl.com> <4A6ACB13-0CBB-4DA7-84AD-28CDE56DB4C3@csperkins.org> <0MKpCa-1LoLs525qX-000cvA@mrelay.perfora.net> <49D1C793.9050409@hhi.fraunhofer.de> <0MKp8S-1Lof8c1LTC-000fjs@mrelay.perfora.net> <49D4AE9D.8060905@hhi.fraunhofer.de> <0MKpCa-1MEnZO1ysE-000d6S@mrelay.perfora.net> <4A323DC5.5020004@hhi.fraunhofer.de> <0MKpCa-1MGbjS2vGp-000cit@mrelay.perfora.net> <C0A963AC-4B17-49FC-904C-44A43DF0B8D7@csperkins.org> <0MKpCa-1MGfai3tWQ-000d7b@mrelay.perfora.net>
X-Mailer: Apple Mail (2.935.3)
Cc: avt@ietf.org
Subject: Re: [AVT] Fwd: I-D  Action:draft-perkins-avt-rapid-rtp-sync-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: Wed, 17 Jun 2009 17:56:57 -0000

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

Michael,

On 16 Jun 2009, at 21:27, Michael A Dolan wrote:
> FYI, I started out in March with a number of comments, some related  
> to multicast UDLR with 1-2 links and I sense that's too big a topic  
> to try and add at this point.  My comments therefore have distilled  
> to addressing two major factors in syncing RTP sessions that I  
> believe overshadow the time resolutions being discussed in the  
> draft, and therefore it is an omission not to address them:
>
> 1. Common timebase
> 2. Media-specific access points
>
> I stopped short of suggesting we should design anything. Therefore I  
> still believe both topics belong here, and in this draft, and they  
> are not so big as to defer at this point.
>
> For clarification, I wasn't proposing we define a timebase signaling  
> mechanism (although I do think that's a good idea).  All I am  
> proposing is to add some text that explains that a common timebase  
> is needed to achieve anything near the implied sync times discussed  
> in this draft. How the senders and receivers figure that out is out  
> of band. But if they don't and just go along with "wallclock", it  
> makes much of the rest of this draft irrelevant since the timebase  
> error will be huge by comparison.

That's already stated in RFC 3550. I'm not sure it needs repeating  
here, but can add something if you want.

> Regarding the issue about access points, I'm not sure how much  
> background to add, so apologies if this is obvious to everyone.  
> Every media stream type has "access points" that arrive periodically  
> - the point where a decoder can begin to decode the stream. In  
> general, these are a function of the encoding, not constant per  
> type, and not constant per stream. For example in H.264, these  
> typically center around the presence of an IDR frame.  HE AAC has a  
> simpler coding structure, but one still can't start decoding  
> anywhere in the stream.  The "typical" periods of the H.264 access  
> points range from 0.5 to 2 seconds, depending on the coding.  The  
> exact period is application dependent, but is not relevant.  The  
> point is that these periods greatly exceed the times shown in the  
> tables which are implied to be the sync times - going as low as 0.04  
> seconds.  The tables in this draft suggesting that RTCP SR packets  
> be sent 0.04 seconds apart for high rate streams. This is  
> interesting (as Thomas notes) for jitter management and clock  
> settling, but that high rate does not help you sync since you can't  
> even start decoding the video for a relatively long time after the  
> 0.04 seconds. This is mostly related to issues of late joiners of  
> course.  Therefore, I was suggesting we make note of this fact to  
> clarify there are other factors to sync and acquisition beyond  
> receipt of NTP and the RTCP SR packet, and that these other times  
> far exceed 0.04 seconds.

Okay, that's what I thought you meant. That certainly affects the join  
times, although I'm not sure I'd call that issue synchronisation  
latency. We can certainly add some wording to highlight it though.

> Co-locating in time the RTCP SR packets with their related access  
> points further improves the sync time.  For example, if the IDR is  
> every 2 seconds, there is no benefit (for syncing) to sending the  
> RTCP SR more frequently than that, especially if it is aligned with  
> this access point in time.  If the RTCP SR packets are sent randomly  
> in time, the sync time is the IDR period plus 1/2 the RTCP SR packet  
> period, on average. This is more of an optimization, but then,  
> that's what this whole draft is about - optimizing the sync time.

I agree that co-locating the SR information in time with the random  
access points helps, and will add something to the draft to say that  
explicitly if it's not already there. I disagree that's sufficient:  
sending the SR information more frequently gives the receiver more  
samples from which to estimate any skew between NTP and RTP  
timestamps, and gives more information to help filter out any  
incorrect mappings.

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




--Apple-Mail-23-666249745
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; ">Michael,<div><br><div><div>On =
16 Jun 2009, at 21:27, Michael A Dolan wrote:</div><blockquote =
type=3D"cite"><div>FYI, I started out in March with a number of =
comments, some related to multicast UDLR with 1-2 links and I sense =
that's too big a topic to try and add at this point.&nbsp; My comments =
therefore have distilled to addressing two major factors in syncing RTP =
sessions that I believe overshadow the time resolutions being discussed =
in the draft, and therefore it is an omission not to address =
them:<br><br> 1. Common timebase<br> 2. Media-specific access =
points<br><br> I stopped short of suggesting we should design anything. =
Therefore I still believe both topics belong here, and in this draft, =
and they are not so big as to defer at this point.<br><br> For =
clarification, I wasn't proposing we define a timebase signaling =
mechanism (although I do think that's a good idea).&nbsp; All I am =
proposing is to add some text that explains that a common timebase is =
needed to achieve anything near the implied sync times discussed in this =
draft. How the senders and receivers figure that out is out of band. But =
if they don't and just go along with "wallclock", it makes much of the =
rest of this draft irrelevant since the timebase error will be huge by =
comparison.<br></div></blockquote><div><br></div><div>That's already =
stated in RFC 3550. I'm not sure it needs repeating here, but can add =
something if you want.</div><br><blockquote type=3D"cite"><div> =
Regarding the issue about access points, I'm not sure how much =
background to add, so apologies if this is obvious to everyone. Every =
media stream type has "access points" that arrive periodically - the =
point where a decoder can begin to decode the stream. In general, these =
are a function of the encoding, not constant per type, and not constant =
per stream. For example in H.264, these typically center around the =
presence of an IDR frame.&nbsp; HE AAC has a simpler coding structure, =
but one still can't start decoding anywhere in the stream.&nbsp; The =
"typical" periods of the H.264 access points range from 0.5 to 2 =
seconds, depending on the coding.&nbsp; The exact period is application =
dependent, but is not relevant.&nbsp; The point is that these periods =
greatly exceed the times shown in the tables which are implied to be the =
sync times - going as low as 0.04 seconds.&nbsp; The tables in this =
draft suggesting that RTCP SR packets be sent 0.04 seconds apart for =
high rate streams. This is interesting (as Thomas notes) for jitter =
management and clock settling, but that high rate does not help you sync =
since you can't even start decoding the video for a relatively long time =
after the 0.04 seconds. This is mostly related to issues of late joiners =
of course.&nbsp; Therefore, I was suggesting we make note of this fact =
to clarify there are other factors to sync and acquisition beyond =
receipt of NTP and the RTCP SR packet, and that these other times far =
exceed 0.04 seconds.<br></div></blockquote><div><br></div><div>Okay, =
that's what I thought you meant. That certainly affects the join times, =
although I'm not sure I'd call that issue synchronisation latency. We =
can certainly add some wording to highlight it =
though.</div><br><blockquote type=3D"cite"><div> Co-locating in time the =
RTCP SR packets with their related access points further improves the =
sync time.&nbsp; For example, if the IDR is every 2 seconds, there is no =
benefit (for syncing) to sending the RTCP SR more frequently than that, =
especially if it is aligned with this access point in time.&nbsp; If the =
RTCP SR packets are sent randomly in time, the sync time is the IDR =
period plus 1/2 the RTCP SR packet period, on average. This is more of =
an optimization, but then, that's what this whole draft is about - =
optimizing the sync time.<br></div></blockquote><div><br></div><div>I =
agree that co-locating the SR information in time with the random access =
points helps, and will add something to the draft to say that explicitly =
if it's not already there. I disagree that's sufficient: sending the SR =
information more frequently gives the receiver more samples from which =
to estimate any skew between NTP and RTP timestamps, and gives more =
information to help filter out any incorrect =
mappings.</div><div><br></div></div><div =
apple-content-edited=3D"true"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Arial; font-size: 9px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Lucida Sans Typewriter'; font-size: 9px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; color: rgb(0, 0, 0); =
font-family: 'Lucida Sans Typewriter'; font-size: 9px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; -webkit-text-decorations-in-effect: none; =
text-indent: 0px; -webkit-text-size-adjust: auto; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; color: rgb(0, 0, 0); font-family: 'Lucida Sans Typewriter'; =
font-size: 9px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; =
-webkit-text-decorations-in-effect: none; text-indent: 0px; =
-webkit-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; color: rgb(0, 0, 0); font-family: 'Lucida Sans Typewriter'; =
font-size: 9px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; =
-webkit-text-decorations-in-effect: none; text-indent: 0px; =
-webkit-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; =
"><div>--&nbsp;</div><div></div><div>Colin Perkins</div><div><a =
href=3D"http://csperkins.org/">http://csperkins.org/</a></div></span></spa=
n></span><br class=3D"Apple-interchange-newline"></span><br =
class=3D"Apple-interchange-newline"></div></span> =
</div><br></div></body></html>=

--Apple-Mail-23-666249745--

From gabor.somogyi@nsn.com  Wed Jun 17 11:27:26 2009
Return-Path: <gabor.somogyi@nsn.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 83B1928C0E6 for <avt@core3.amsl.com>; Wed, 17 Jun 2009 11:27:26 -0700 (PDT)
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 84j-XWBxmLXU for <avt@core3.amsl.com>; Wed, 17 Jun 2009 11:27:25 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [217.115.75.233]) by core3.amsl.com (Postfix) with ESMTP id 4958C28C141 for <avt@ietf.org>; Wed, 17 Jun 2009 11:27:25 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id n5HIRZ2b032739 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <avt@ietf.org>; Wed, 17 Jun 2009 20:27:35 +0200
Received: from demuexc024.nsn-intra.net (demuexc024.nsn-intra.net [10.159.32.11]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id n5HIRZjY010385 for <avt@ietf.org>; Wed, 17 Jun 2009 20:27:35 +0200
Received: from FIESEXC006.nsn-intra.net ([10.159.0.14]) by demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 17 Jun 2009 20:27:34 +0200
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: Wed, 17 Jun 2009 21:27:31 +0300
Message-ID: <45CC8FCA2C24554AA026E01B020D0CFFDF1419@FIESEXC006.nsn-intra.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Codec parameter mismatch in SDP offer and answer
Thread-Index: AcnveUb1qvZMazlvQ56m/PQCrQdozQ==
From: "Somogyi, Gabor (NSN - HU/Budapest)" <gabor.somogyi@nsn.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 17 Jun 2009 18:27:34.0969 (UTC) FILETIME=[48E30A90:01C9EF79]
Subject: [AVT] Codec parameter mismatch in SDP offer and answer
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, 17 Jun 2009 18:27:26 -0000

Sorry if that topic was discussed earlier. I was not able to find the
proper answer, though.

What happens if codec parameters in the SDP answer differ from the ones
in relevant offer? Maybe each codec specific SDP format description
shell address that issue, as it may not be possible to give a generic
answer.

RFC 3952 (iLBC) clearly defines that "mode" parameter is bi-directional,
meaning that in both direction the same "mode" must be used. And if the
parameter differs in the offer and the answer, then value "30" must be
used. That sounds fine.

In rfc3047-bis-09 proposal I saw no such definition. Is it possible for
the answerer to reduce the offered bitrate? Must the same bitrate be
used in both directions?

I saw such interworking issues between live products of different
vendors. G.729 (RFC 3555) defines optional parameter "annexb". If the
offerer indicated the willingness of using Annex B, then could the
answerer indicate that it is not willing to use discontinuous
transmission (as it cannot generate comfort noise)? When the offerer
sent its offer, it may had set up its DSPs, so might not be happy about
even "downgrading" codec settings. Same applies to many other codecs, as
well.

BR,
Gabor Somogyi

From abegen@cisco.com  Wed Jun 17 11:35:59 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 6C90028C24A for <avt@core3.amsl.com>; Wed, 17 Jun 2009 11:35:59 -0700 (PDT)
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=[AWL=0.000,  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 DRfz1rcz0L91 for <avt@core3.amsl.com>; Wed, 17 Jun 2009 11:35:58 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 1F11428B56A for <avt@ietf.org>; Wed, 17 Jun 2009 11:35:58 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,239,1243814400"; d="scan'208";a="81371904"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-5.cisco.com with ESMTP; 17 Jun 2009 18:36:10 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n5HIaAkC024047;  Wed, 17 Jun 2009 11:36:10 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n5HIaAwI001850; Wed, 17 Jun 2009 18:36:10 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 17 Jun 2009 11:36:09 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 17 Jun 2009 11:36:06 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D54098D8893@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <B5806023-20A3-4868-9195-7FA0D4D62053@csperkins.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Fwd: I-D  Action:draft-perkins-avt-rapid-rtp-sync-03.txt
Thread-Index: AcnvdQqqNMxMU9aMQXWzfTUZTZeOBwABKQRQ
References: <20090309171502.518513A6359@core3.amsl.com><4A6ACB13-0CBB-4DA7-84AD-28CDE56DB4C3@csperkins.org><0MKpCa-1LoLs525qX-000cvA@mrelay.perfora.net><49D1C793.9050409@hhi.fraunhofer.de><0MKp8S-1Lof8c1LTC-000fjs@mrelay.perfora.net><49D4AE9D.8060905@hhi.fraunhofer.de><0MKpCa-1MEnZO1ysE-000d6S@mrelay.perfora.net><4A323DC5.5020004@hhi.fraunhofer.de><0MKpCa-1MGbjS2vGp-000cit@mrelay.perfora.net><C0A963AC-4B17-49FC-904C-44A43DF0B8D7@csperkins.org><0MKpCa-1MGfai3tWQ-000d7b@mrelay.perfora.net> <B5806023-20A3-4868-9195-7FA0D4D62053@csperkins.org>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Colin Perkins" <csp@csperkins.org>, "Michael A Dolan" <md.1@newtbt.com>
X-OriginalArrivalTime: 17 Jun 2009 18:36:09.0932 (UTC) FILETIME=[7BD428C0:01C9EF7A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=6375; t=1245263770; x=1246127770; c=relaxed/simple; s=sjdkim1004; 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]=20Fwd=3A=20I-D=20=20Action=3Adraf t-perkins-avt-rapid-rtp-sync-03.txt |Sender:=20; bh=poeP1iDQfHeCauze3ApRCZP/pwCdjP0eKvP48909eek=; b=MECJNl6x67RFyrf/ndp8s/eE9OOHYWRJGfkcOsgdyDl+MvGN+oy2uxBHtc eRUEUWVd4ebWJGgUIobw4b+acwz5DS+aw2IV+PtxGJj6jplN07q3wj9Eug9q hgkbqG5ifMgZEp9FSML5el4OMODmxY/GjMuRs0XoDbO3dMMhXZ2pw=;
Authentication-Results: sj-dkim-1; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Cc: avt@ietf.org
Subject: Re: [AVT] Fwd: I-D  Action:draft-perkins-avt-rapid-rtp-sync-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: Wed, 17 Jun 2009 18:35:59 -0000

Hi Colin,

> Okay, that's what I thought you meant. That certainly affects the join =
times, although I'm
> not sure I'd call that issue synchronisation latency. We can certainly =
add some wording to
> highlight it though.

That is part of something we call "acquisition delay" and this problem =
is addressed in a separate draft:
http://tools.ietf.org/id/draft-ietf-avt-rapid-acquisition-for-rtp-01.txt

=20
> 	Co-locating in time the RTCP SR packets with their related access =
points further
> improves the sync time.  For example, if the IDR is every 2 seconds, =
there is no benefit
> (for syncing) to sending the RTCP SR more frequently than that, =
especially if it is
> aligned with this access point in time.  If the RTCP SR packets are =
sent randomly in time,
> the sync time is the IDR period plus 1/2 the RTCP SR packet period, on =
average. This is
> more of an optimization, but then, that's what this whole draft is =
about - optimizing the
> sync time.
>=20
>=20
>=20
> I agree that co-locating the SR information in time with the random =
access points helps,
> and will add something to the draft to say that explicitly if it's not =
already there. I
> disagree that's sufficient: sending the SR information more frequently =
gives the receiver
> more samples from which to estimate any skew between NTP and RTP =
timestamps, and gives
> more information to help filter out any incorrect mappings.

Have you considered sending an SR as a part of the unicast burst (or =
RAMS-I message that describes the burst) that we provide for rapid =
acquisition? We may end up sending an SR this way since it will be =
required for figuring out the extended seqnums.

-acbegen


> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of =
Colin Perkins
> Sent: Wednesday, June 17, 2009 10:57 AM
> To: Michael A Dolan
> Cc: avt@ietf.org
> Subject: Re: [AVT] Fwd: I-D =
Action:draft-perkins-avt-rapid-rtp-sync-03.txt
>=20
> Michael,
>=20
> On 16 Jun 2009, at 21:27, Michael A Dolan wrote:
>=20
> 	FYI, I started out in March with a number of comments, some related =
to multicast UDLR
> with 1-2 links and I sense that's too big a topic to try and add at =
this point.  My
> comments therefore have distilled to addressing two major factors in =
syncing RTP sessions
> that I believe overshadow the time resolutions being discussed in the =
draft, and therefore
> it is an omission not to address them:
>=20
> 	1. Common timebase
> 	2. Media-specific access points
>=20
> 	I stopped short of suggesting we should design anything. Therefore I =
still believe
> both topics belong here, and in this draft, and they are not so big as =
to defer at this
> point.
>=20
> 	For clarification, I wasn't proposing we define a timebase signaling =
mechanism
> (although I do think that's a good idea).  All I am proposing is to =
add some text that
> explains that a common timebase is needed to achieve anything near the =
implied sync times
> discussed in this draft. How the senders and receivers figure that out =
is out of band. But
> if they don't and just go along with "wallclock", it makes much of the =
rest of this draft
> irrelevant since the timebase error will be huge by comparison.
>=20
>=20
>=20
> That's already stated in RFC 3550. I'm not sure it needs repeating =
here, but can add
> something if you want.
>=20
>=20
> 	Regarding the issue about access points, I'm not sure how much =
background to add, so
> apologies if this is obvious to everyone. Every media stream type has =
"access points" that
> arrive periodically - the point where a decoder can begin to decode =
the stream. In
> general, these are a function of the encoding, not constant per type, =
and not constant per
> stream. For example in H.264, these typically center around the =
presence of an IDR frame.
> HE AAC has a simpler coding structure, but one still can't start =
decoding anywhere in the
> stream.  The "typical" periods of the H.264 access points range from =
0.5 to 2 seconds,
> depending on the coding.  The exact period is application dependent, =
but is not relevant.
> The point is that these periods greatly exceed the times shown in the =
tables which are
> implied to be the sync times - going as low as 0.04 seconds.  The =
tables in this draft
> suggesting that RTCP SR packets be sent 0.04 seconds apart for high =
rate streams. This is
> interesting (as Thomas notes) for jitter management and clock =
settling, but that high rate
> does not help you sync since you can't even start decoding the video =
for a relatively long
> time after the 0.04 seconds. This is mostly related to issues of late =
joiners of course.
> Therefore, I was suggesting we make note of this fact to clarify there =
are other factors
> to sync and acquisition beyond receipt of NTP and the RTCP SR packet, =
and that these other
> times far exceed 0.04 seconds.
>=20
>=20
>=20
> Okay, that's what I thought you meant. That certainly affects the join =
times, although I'm
> not sure I'd call that issue synchronisation latency. We can certainly =
add some wording to
> highlight it though.
>=20
>=20
> 	Co-locating in time the RTCP SR packets with their related access =
points further
> improves the sync time.  For example, if the IDR is every 2 seconds, =
there is no benefit
> (for syncing) to sending the RTCP SR more frequently than that, =
especially if it is
> aligned with this access point in time.  If the RTCP SR packets are =
sent randomly in time,
> the sync time is the IDR period plus 1/2 the RTCP SR packet period, on =
average. This is
> more of an optimization, but then, that's what this whole draft is =
about - optimizing the
> sync time.
>=20
>=20
>=20
> I agree that co-locating the SR information in time with the random =
access points helps,
> and will add something to the draft to say that explicitly if it's not =
already there. I
> disagree that's sufficient: sending the SR information more frequently =
gives the receiver
> more samples from which to estimate any skew between NTP and RTP =
timestamps, and gives
> more information to help filter out any incorrect mappings.
>=20
> --
> Colin Perkins
> http://csperkins.org/
>=20
>=20


From md.1@newtbt.com  Wed Jun 17 12:46:26 2009
Return-Path: <md.1@newtbt.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 0BE6428C2E9 for <avt@core3.amsl.com>; Wed, 17 Jun 2009 12:46:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.726
X-Spam-Level: 
X-Spam-Status: No, score=-1.726 tagged_above=-999 required=5 tests=[AWL=-0.524, 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 WbMCaId4-Vvn for <avt@core3.amsl.com>; Wed, 17 Jun 2009 12:46:24 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 3D9FB28C277 for <avt@ietf.org>; Wed, 17 Jun 2009 12:46:24 -0700 (PDT)
Received: from TBT-Laptop.newtbt.com (ppp-69-237-184-11.dsl.sndg02.pacbell.net [69.237.184.11]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MKp8S-1MH15V3qqW-000fpm; Wed, 17 Jun 2009 15:46:28 -0400
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 17 Jun 2009 12:46:21 -0700
To: avt@ietf.org
From: Michael A Dolan <md.1@newtbt.com>
In-Reply-To: <B5806023-20A3-4868-9195-7FA0D4D62053@csperkins.org>
References: <20090309171502.518513A6359@core3.amsl.com> <4A6ACB13-0CBB-4DA7-84AD-28CDE56DB4C3@csperkins.org> <0MKpCa-1LoLs525qX-000cvA@mrelay.perfora.net> <49D1C793.9050409@hhi.fraunhofer.de> <0MKp8S-1Lof8c1LTC-000fjs@mrelay.perfora.net> <49D4AE9D.8060905@hhi.fraunhofer.de> <0MKpCa-1MEnZO1ysE-000d6S@mrelay.perfora.net> <4A323DC5.5020004@hhi.fraunhofer.de> <0MKpCa-1MGbjS2vGp-000cit@mrelay.perfora.net> <C0A963AC-4B17-49FC-904C-44A43DF0B8D7@csperkins.org> <0MKpCa-1MGfai3tWQ-000d7b@mrelay.perfora.net> <B5806023-20A3-4868-9195-7FA0D4D62053@csperkins.org>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_596395625==.ALT"
Message-Id: <0MKp8S-1MH15V3qqW-000fpm@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX19Zq/nk1q4qOYAA8UzKSj90oJQKZSp0XVaXVeO uNpSKd1vOuBdSMu+DzK05lZuOS0+LI8uYfgbJqSp32I+9eO8Y6 +7pFB8yqTQNJuiVh3jnLQ==
Subject: Re: [AVT] Fwd: I-D Action:draft-perkins-avt-rapid-rtp-sync-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: Wed, 17 Jun 2009 19:46:26 -0000

--=====================_596395625==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

Colin-

Thanks.  I think we're close.

3550 only imprecisely recommends (not requires) using a common clock, 
and when it does, it uses the term, "wallclock", without defining 
it.  In order for the sync to even approach the numbers implied in 
this draft, the clocks must indeed be synchronized and they must use 
the same timebase.  Failing to minimally recommend this (even if you 
believe it is a restatement of 3550), it is not possible to achieve 
the implied sync times.  I really think you need to say MUST, but I 
leave that to you and Thomas.  And, it should be tied back to NTP 
fields since that it is a popular source of clock.  Here's a suggestion:

>2.3 Clock Synchronization
>In order to achieve more rapid and accurate sync, as recommended in 
>RFC 3550, all senders and receivers should use a common reference 
>clock. When NTPv4 is used, all instances of NTP packets should set 
>the Reference ID (refid) field to the same timebase value (e.g. 
>"GPS" - see NTPv4 Figure 12). Signaling for what Reference ID value 
>is tp be used is accomplished out of band. When NTPv3 is used, all 
>instances of NTP packets should use the same timebase, even if it is 
>not explicitly signaled in the Reference ID field.
>==============
>Replace all uses of "wallclock", "NTP format clock", "NTP format 
>wallclock", etc with a single term, such as "common reference 
>clock", to be consistent with the first use in section 1, and to 
>remove the ambiguity of all the varying uses in the text.
>==============
>Add a reference to NTPv4 (or maybe replace [7] RFC 1305?):
>https://datatracker.ietf.org/drafts/draft-ietf-ntp-ntpv4-proto/

Regarding the access point timing, I think a note would be good 
surrounding the tables to diffuse the implication that the 0.04 times 
in the table are realistic for an expected sync time (even if good 
for other purposes). We all agree there are other good reasons to 
send more frequent RTCP SR records that also improve clock accuracy, 
and are thus directly relevant to this draft. I did not mean to imply 
otherwise.  But I think it would be helpful to more clearly separate 
those reasons (e.g. decoder clock stability) from sync time 
expectations.  Let me know if you want a specific text suggestion.

Co-locating the RTCP SR records and the media access points is a 
helpful recommendation, and less systemic than the above points.

Thanks for considering these improvements (I think).

Regards,

         Mike


At 06:57 PM 6/17/2009 +0100, Colin Perkins wrote:
>Michael,
>
>On 16 Jun 2009, at 21:27, Michael A Dolan wrote:
>>FYI, I started out in March with a number of comments, some related 
>>to multicast UDLR with 1-2 links and I sense that's too big a topic 
>>to try and add at this point.  My comments therefore have distilled 
>>to addressing two major factors in syncing RTP sessions that I 
>>believe overshadow the time resolutions being discussed in the 
>>draft, and therefore it is an omission not to address them:
>>
>>1. Common timebase
>>2. Media-specific access points
>>
>>I stopped short of suggesting we should design anything. Therefore 
>>I still believe both topics belong here, and in this draft, and 
>>they are not so big as to defer at this point.
>>
>>For clarification, I wasn't proposing we define a timebase 
>>signaling mechanism (although I do think that's a good idea).  All 
>>I am proposing is to add some text that explains that a common 
>>timebase is needed to achieve anything near the implied sync times 
>>discussed in this draft. How the senders and receivers figure that 
>>out is out of band. But if they don't and just go along with 
>>"wallclock", it makes much of the rest of this draft irrelevant 
>>since the timebase error will be huge by comparison.
>
>That's already stated in RFC 3550. I'm not sure it needs repeating 
>here, but can add something if you want.
>
>>Regarding the issue about access points, I'm not sure how much 
>>background to add, so apologies if this is obvious to everyone. 
>>Every media stream type has "access points" that arrive 
>>periodically - the point where a decoder can begin to decode the 
>>stream. In general, these are a function of the encoding, not 
>>constant per type, and not constant per stream. For example in 
>>H.264, these typically center around the presence of an IDR 
>>frame.  HE AAC has a simpler coding structure, but one still can't 
>>start decoding anywhere in the stream.  The "typical" periods of 
>>the H.264 access points range from 0.5 to 2 seconds, depending on 
>>the coding.  The exact period is application dependent, but is not 
>>relevant.  The point is that these periods greatly exceed the times 
>>shown in the tables which are implied to be the sync times - going 
>>as low as 0.04 seconds.  The tables in this draft suggesting that 
>>RTCP SR packets be sent 0.04 seconds apart for high rate streams. 
>>This is interesting (as Thomas notes) for jitter management and 
>>clock settling, but that high rate does not help you sync since you 
>>can't even start decoding the video for a relatively long time 
>>after the 0.04 seconds. This is mostly related to issues of late 
>>joiners of course.  Therefore, I was suggesting we make note of 
>>this fact to clarify there are other factors to sync and 
>>acquisition beyond receipt of NTP and the RTCP SR packet, and that 
>>these other times far exceed 0.04 seconds.
>
>Okay, that's what I thought you meant. That certainly affects the 
>join times, although I'm not sure I'd call that issue 
>synchronisation latency. We can certainly add some wording to 
>highlight it though.
>
>>Co-locating in time the RTCP SR packets with their related access 
>>points further improves the sync time.  For example, if the IDR is 
>>every 2 seconds, there is no benefit (for syncing) to sending the 
>>RTCP SR more frequently than that, especially if it is aligned with 
>>this access point in time.  If the RTCP SR packets are sent 
>>randomly in time, the sync time is the IDR period plus 1/2 the RTCP 
>>SR packet period, on average. This is more of an optimization, but 
>>then, that's what this whole draft is about - optimizing the sync time.
>
>I agree that co-locating the SR information in time with the random 
>access points helps, and will add something to the draft to say that 
>explicitly if it's not already there. I disagree that's sufficient: 
>sending the SR information more frequently gives the receiver more 
>samples from which to estimate any skew between NTP and RTP 
>timestamps, and gives more information to help filter out any 
>incorrect mappings.
>
>--
>Colin Perkins
><http://csperkins.org/>http://csperkins.org/
>
>

--=====================_596395625==.ALT
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<body>
Colin-<br><br>
Thanks.&nbsp; I think we're close.<br><br>
3550 only imprecisely recommends (not requires) using a common clock, and
when it does, it uses the term, &quot;wallclock&quot;, without defining
it.&nbsp; In order for the sync to even approach the numbers implied in
this draft, the clocks must indeed be synchronized and they must use the
same timebase.&nbsp; Failing to minimally recommend this (even if you
believe it is a restatement of 3550), it is not possible to achieve the
implied sync times.&nbsp; I really think you need to say MUST, but I
leave that to you and Thomas.&nbsp; And, it should be tied back to NTP
fields since that it is a popular source of clock.&nbsp; Here's a
suggestion:<br><br>
<blockquote type=3Dcite class=3Dcite cite=3D"">2.3 Clock Synchronization<br>
In order to achieve more rapid and accurate sync, as recommended in RFC
3550, all senders and receivers should use a common reference clock. When
NTPv4 is used, all instances of NTP packets should set the Reference ID
(refid) field to the same timebase value (e.g. &quot;GPS&quot; - see
NTPv4 Figure 12). Signaling for what Reference ID value is tp be used is
accomplished out of band. When NTPv3 is used, all instances of NTP
packets should use the same timebase, even if it is not explicitly
signaled in the Reference ID field. <br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
Replace all uses of &quot;wallclock&quot;, &quot;NTP format clock&quot;,
&quot;NTP format wallclock&quot;, etc with a single term, such as
&quot;common reference clock&quot;, to be consistent with the first use
in section 1, and to remove the ambiguity of all the varying uses in the
text.<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
Add a reference to NTPv4 (or maybe replace [7] RFC 1305?):<br>
<a href=3D"https://datatracker.ietf.org/drafts/draft-ietf-ntp-ntpv4-proto/" =
eudora=3D"autourl">
https://datatracker.ietf.org/drafts/draft-ietf-ntp-ntpv4-proto/</a>
</blockquote><br>
Regarding the access point timing, I think a note would be good
surrounding the tables to diffuse the implication that the 0.04 times in
the table are realistic for an expected sync time (even if good for other
purposes). We all agree there are other good reasons to send more
frequent RTCP SR records that also improve clock accuracy, and are thus
directly relevant to this draft. I did not mean to imply otherwise.&nbsp;
But I think it would be helpful to more clearly separate those reasons
(e.g. decoder clock stability) from sync time expectations.&nbsp; Let me
know if you want a specific text suggestion.<br><br>
Co-locating the RTCP SR records and the media access points is a helpful
recommendation, and less systemic than the above points.<br><br>
Thanks for considering these improvements (I think).<br><br>
Regards,<br><br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Mike<br>
<br>
<br>
At 06:57 PM 6/17/2009 +0100, Colin Perkins wrote:<br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Michael,<br><br>
On 16 Jun 2009, at 21:27, Michael A Dolan wrote:<br>
<blockquote type=3Dcite class=3Dcite cite=3D"">FYI, I started out in March w=
ith
a number of comments, some related to multicast UDLR with 1-2 links and I
sense that's too big a topic to try and add at this point.&nbsp; My
comments therefore have distilled to addressing two major factors in
syncing RTP sessions that I believe overshadow the time resolutions being
discussed in the draft, and therefore it is an omission not to address
them:<br><br>
1. Common timebase<br>
2. Media-specific access points<br><br>
I stopped short of suggesting we should design anything. Therefore I
still believe both topics belong here, and in this draft, and they are
not so big as to defer at this point.<br><br>
For clarification, I wasn't proposing we define a timebase signaling
mechanism (although I do think that's a good idea).&nbsp; All I am
proposing is to add some text that explains that a common timebase is
needed to achieve anything near the implied sync times discussed in this
draft. How the senders and receivers figure that out is out of band. But
if they don't and just go along with &quot;wallclock&quot;, it makes much
of the rest of this draft irrelevant since the timebase error will be
huge by comparison.</blockquote><br>
That's already stated in RFC 3550. I'm not sure it needs repeating here,
but can add something if you want.<br><br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Regarding the issue about acc=
ess
points, I'm not sure how much background to add, so apologies if this is
obvious to everyone. Every media stream type has &quot;access
points&quot; that arrive periodically - the point where a decoder can
begin to decode the stream. In general, these are a function of the
encoding, not constant per type, and not constant per stream. For example
in H.264, these typically center around the presence of an IDR
frame.&nbsp; HE AAC has a simpler coding structure, but one still can't
start decoding anywhere in the stream.&nbsp; The &quot;typical&quot;
periods of the H.264 access points range from 0.5 to 2 seconds, depending
on the coding.&nbsp; The exact period is application dependent, but is
not relevant.&nbsp; The point is that these periods greatly exceed the
times shown in the tables which are implied to be the sync times - going
as low as 0.04 seconds.&nbsp; The tables in this draft suggesting that
RTCP SR packets be sent 0.04 seconds apart for high rate streams. This is
interesting (as Thomas notes) for jitter management and clock settling,
but that high rate does not help you sync since you can't even start
decoding the video for a relatively long time after the 0.04 seconds.
This is mostly related to issues of late joiners of course.&nbsp;
Therefore, I was suggesting we make note of this fact to clarify there
are other factors to sync and acquisition beyond receipt of NTP and the
RTCP SR packet, and that these other times far exceed 0.04
seconds.</blockquote><br>
Okay, that's what I thought you meant. That certainly affects the join
times, although I'm not sure I'd call that issue synchronisation latency.
We can certainly add some wording to highlight it though.<br><br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Co-locating in time the RTCP =
SR
packets with their related access points further improves the sync
time.&nbsp; For example, if the IDR is every 2 seconds, there is no
benefit (for syncing) to sending the RTCP SR more frequently than that,
especially if it is aligned with this access point in time.&nbsp; If the
RTCP SR packets are sent randomly in time, the sync time is the IDR
period plus 1/2 the RTCP SR packet period, on average. This is more of an
optimization, but then, that's what this whole draft is about -
optimizing the sync time.</blockquote><br>
I agree that co-locating the SR information in time with the random
access points helps, and will add something to the draft to say that
explicitly if it's not already there. I disagree that's sufficient:
sending the SR information more frequently gives the receiver more
samples from which to estimate any skew between NTP and RTP timestamps,
and gives more information to help filter out any incorrect
mappings.<br><br>
-- <br>
Colin Perkins<br>
<a href=3D"http://csperkins.org/">http://csperkins.org/</a><br><br>
<br>
</blockquote></body>
</html>

--=====================_596395625==.ALT--


From jonathan@vidyo.com  Wed Jun 17 13:11:54 2009
Return-Path: <jonathan@vidyo.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 35EF73A6A6B for <avt@core3.amsl.com>; Wed, 17 Jun 2009 13:11:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 RymZjj+EWhKw for <avt@core3.amsl.com>; Wed, 17 Jun 2009 13:11:53 -0700 (PDT)
Received: from mx1.myoutlookonline.com (mx1.myoutlookonline.com [64.95.72.238]) by core3.amsl.com (Postfix) with ESMTP id 6466F3A6EB7 for <avt@ietf.org>; Wed, 17 Jun 2009 13:11:53 -0700 (PDT)
Received: from be150.mail.lan ([10.110.20.150]) by mx1.myoutlookonline.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 17 Jun 2009 16:11:54 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
x-cr-puzzleid: {D76304C3-0FCA-408E-B546-721AC5F636DC}
x-cr-hashedpuzzle: Jms= Aktq BLsl BmL2 B/+Z ED+e EV2f FYSg FtOr HZPA HorY Ijks I1/D JJD4 K5K2 LVAV; 1; YQB2AHQAQABpAGUAdABmAC4AbwByAGcA; Sosha1_v1; 7; {D76304C3-0FCA-408E-B546-721AC5F636DC}; agBvAG4AYQB0AGgAYQBuAEAAdgBpAGQAeQBvAC4AYwBvAG0A; Wed, 17 Jun 2009 20:11:39 GMT; UwBvAHUAbgBkACAAbABlAHYAZQBsACAAaQBuAGQAaQBjAGEAdABvAHIAcwA=
Content-class: urn:content-classes:message
Date: Wed, 17 Jun 2009 16:11:39 -0400
Message-ID: <6B55710E7F51AD4B93F336052113B85FA4B16F@be150.mail.lan>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Sound level indicators
Thread-Index: Acnvh9LvP0i7bNgVTdO+sJvRX2yGkA==
From: "Jonathan Lennox" <jonathan@vidyo.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 17 Jun 2009 20:11:54.0240 (UTC) FILETIME=[DBB40000:01C9EF87]
Subject: [AVT] Sound level indicators
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, 17 Jun 2009 20:11:54 -0000

Hi all,

I've just submitted the following draft:

http://www.ietf.org/internet-drafts/draft-lennox-avt-rtp-audio-level-ext
hdr-00.txt

The draft addresses a similar, though not identical, issue, to
draft-ivov-avt-slic-00.

It defines an RTP extension header which indicates the audio level, and
voice activity detection state, of a packet's RTP audio payload.  In
large conferences, this can reduce the load on an audio mixer or other
middlebox which wants to forward only a few of the loudest audio
streams, without requiring it to decode and measure every stream it's
receiving.

Comments are welcome!

--=20
Jonathan Lennox
Vidyo, Inc
jonathan@vidyo.com



From AAllison@nab.org  Wed Jun 17 13:13:00 2009
Return-Path: <AAllison@nab.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 367AA28C2F1 for <avt@core3.amsl.com>; Wed, 17 Jun 2009 13:13:00 -0700 (PDT)
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 y-jHYk48VacI for <avt@core3.amsl.com>; Wed, 17 Jun 2009 13:12:58 -0700 (PDT)
Received: from exprod6og101.obsmtp.com (exprod6og101.obsmtp.com [64.18.1.181]) by core3.amsl.com (Postfix) with SMTP id B2D2428C2AF for <avt@ietf.org>; Wed, 17 Jun 2009 13:12:57 -0700 (PDT)
Received: from source ([63.210.44.42]) by exprod6ob101.postini.com ([64.18.5.12]) with SMTP ID DSNKSjlOR+a+6oUMCIBFvG1gf0BuDDfkQu0U@postini.com; Wed, 17 Jun 2009 13:13:10 PDT
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_01C9EF88.16A67249"
Date: Wed, 17 Jun 2009 16:13:33 -0400
Message-ID: <71C9EC0544D1F64D8B7D91EDCC6220200320E99A@NABSREX027324.NAB.ORG>
In-Reply-To: <0MKp8S-1MH15V3qqW-000fpm@mrelay.perfora.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Fwd: I-D Action:draft-perkins-avt-rapid-rtp-sync-03.txt
Thread-Index: AcnvhG9L7ABkO6iyRu+Xmr0Wn/8lwAAAPZiA
References: <20090309171502.518513A6359@core3.amsl.com><4A6ACB13-0CBB-4DA7-84AD-28CDE56DB4C3@csperkins.org><0MKpCa-1LoLs525qX-000cvA@mrelay.perfora.net><49D1C793.9050409@hhi.fraunhofer.de><0MKp8S-1Lof8c1LTC-000fjs@mrelay.perfora.net><49D4AE9D.8060905@hhi.fraunhofer.de><0MKpCa-1MEnZO1ysE-000d6S@mrelay.perfora.net><4A323DC5.5020004@hhi.fraunhofer.de><0MKpCa-1MGbjS2vGp-000cit@mrelay.perfora.net><C0A963AC-4B17-49FC-904C-44A43DF0B8D7@csperkins.org><0MKpCa-1MGfai3tWQ-000d7b@mrelay.perfora.net><B5806023-20A3-4868-9195-7FA0D4D62053@csperkins.org> <0MKp8S-1MH15V3qqW-000fpm@mrelay.perfora.net>
From: "Allison, Art" <AAllison@nab.org>
To: <avt@ietf.org>
Subject: Re: [AVT] Fwd: I-D Action:draft-perkins-avt-rapid-rtp-sync-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: Wed, 17 Jun 2009 20:13:00 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9EF88.16A67249
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I also think that the RFC should say MUST to accomplish its purpose. If
a common timebase is not used, then the time differences make this draft
essentially moot. It is a conditional MUST.
=20
Text:=20
In order to achieve more rapid and accurate sync, as recommended in RFC
3550, all senders and receivers MUST use a common reference clock.
=20
Art
Art Allison

Senior Director Advanced Engineering, Science and Technology
=20
National Association of Broadcasters
1771 N Street NW
Washington, DC 20036
Phone  202 429 5418=20
Fax  202 775 4981
www.nab.org <blocked::http://www.nab.org>=20

Advocacy  Education  Innovation


________________________________

	From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
Behalf Of Michael A Dolan
	Sent: Wednesday, June 17, 2009 3:46 PM
	To: avt@ietf.org
	Subject: Re: [AVT] Fwd: I-D
Action:draft-perkins-avt-rapid-rtp-sync-03.txt
=09
=09
	Colin-
=09
	Thanks.  I think we're close.
=09
	3550 only imprecisely recommends (not requires) using a common
clock, and when it does, it uses the term, "wallclock", without defining
it.  In order for the sync to even approach the numbers implied in this
draft, the clocks must indeed be synchronized and they must use the same
timebase.  Failing to minimally recommend this (even if you believe it
is a restatement of 3550), it is not possible to achieve the implied
sync times.  I really think you need to say MUST, but I leave that to
you and Thomas.  And, it should be tied back to NTP fields since that it
is a popular source of clock.  Here's a suggestion:
=09
=09

		2.3 Clock Synchronization
		In order to achieve more rapid and accurate sync, as
recommended in RFC 3550, all senders and receivers should use a common
reference clock. When NTPv4 is used, all instances of NTP packets should
set the Reference ID (refid) field to the same timebase value (e.g.
"GPS" - see NTPv4 Figure 12). Signaling for what Reference ID value is
tp be used is accomplished out of band. When NTPv3 is used, all
instances of NTP packets should use the same timebase, even if it is not
explicitly signaled in the Reference ID field.=20
		=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
		Replace all uses of "wallclock", "NTP format clock",
"NTP format wallclock", etc with a single term, such as "common
reference clock", to be consistent with the first use in section 1, and
to remove the ambiguity of all the varying uses in the text.
		=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
		Add a reference to NTPv4 (or maybe replace [7] RFC
1305?):
=09
https://datatracker.ietf.org/drafts/draft-ietf-ntp-ntpv4-proto/=20


	Regarding the access point timing, I think a note would be good
surrounding the tables to diffuse the implication that the 0.04 times in
the table are realistic for an expected sync time (even if good for
other purposes). We all agree there are other good reasons to send more
frequent RTCP SR records that also improve clock accuracy, and are thus
directly relevant to this draft. I did not mean to imply otherwise.  But
I think it would be helpful to more clearly separate those reasons (e.g.
decoder clock stability) from sync time expectations.  Let me know if
you want a specific text suggestion.
=09
	Co-locating the RTCP SR records and the media access points is a
helpful recommendation, and less systemic than the above points.
=09
	Thanks for considering these improvements (I think).
=09
	Regards,
=09
	        Mike
=09
=09
	At 06:57 PM 6/17/2009 +0100, Colin Perkins wrote:
=09

		Michael,
	=09
		On 16 Jun 2009, at 21:27, Michael A Dolan wrote:
	=09

			FYI, I started out in March with a number of
comments, some related to multicast UDLR with 1-2 links and I sense
that's too big a topic to try and add at this point.  My comments
therefore have distilled to addressing two major factors in syncing RTP
sessions that I believe overshadow the time resolutions being discussed
in the draft, and therefore it is an omission not to address them:
		=09
			1. Common timebase
			2. Media-specific access points
		=09
			I stopped short of suggesting we should design
anything. Therefore I still believe both topics belong here, and in this
draft, and they are not so big as to defer at this point.
		=09
			For clarification, I wasn't proposing we define
a timebase signaling mechanism (although I do think that's a good idea).
All I am proposing is to add some text that explains that a common
timebase is needed to achieve anything near the implied sync times
discussed in this draft. How the senders and receivers figure that out
is out of band. But if they don't and just go along with "wallclock", it
makes much of the rest of this draft irrelevant since the timebase error
will be huge by comparison.


		That's already stated in RFC 3550. I'm not sure it needs
repeating here, but can add something if you want.
	=09
	=09

			Regarding the issue about access points, I'm not
sure how much background to add, so apologies if this is obvious to
everyone. Every media stream type has "access points" that arrive
periodically - the point where a decoder can begin to decode the stream.
In general, these are a function of the encoding, not constant per type,
and not constant per stream. For example in H.264, these typically
center around the presence of an IDR frame.  HE AAC has a simpler coding
structure, but one still can't start decoding anywhere in the stream.
The "typical" periods of the H.264 access points range from 0.5 to 2
seconds, depending on the coding.  The exact period is application
dependent, but is not relevant.  The point is that these periods greatly
exceed the times shown in the tables which are implied to be the sync
times - going as low as 0.04 seconds.  The tables in this draft
suggesting that RTCP SR packets be sent 0.04 seconds apart for high rate
streams. This is interesting (as Thomas notes) for jitter management and
clock settling, but that high rate does not help you sync since you
can't even start decoding the video for a relatively long time after the
0.04 seconds. This is mostly related to issues of late joiners of
course.  Therefore, I was suggesting we make note of this fact to
clarify there are other factors to sync and acquisition beyond receipt
of NTP and the RTCP SR packet, and that these other times far exceed
0.04 seconds.


		Okay, that's what I thought you meant. That certainly
affects the join times, although I'm not sure I'd call that issue
synchronisation latency. We can certainly add some wording to highlight
it though.
	=09
	=09

			Co-locating in time the RTCP SR packets with
their related access points further improves the sync time.  For
example, if the IDR is every 2 seconds, there is no benefit (for
syncing) to sending the RTCP SR more frequently than that, especially if
it is aligned with this access point in time.  If the RTCP SR packets
are sent randomly in time, the sync time is the IDR period plus 1/2 the
RTCP SR packet period, on average. This is more of an optimization, but
then, that's what this whole draft is about - optimizing the sync time.


		I agree that co-locating the SR information in time with
the random access points helps, and will add something to the draft to
say that explicitly if it's not already there. I disagree that's
sufficient: sending the SR information more frequently gives the
receiver more samples from which to estimate any skew between NTP and
RTP timestamps, and gives more information to help filter out any
incorrect mappings.
	=09
		--=20
		Colin Perkins
		http://csperkins.org/
	=09
	=09
	=09


------_=_NextPart_001_01C9EF88.16A67249
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3562" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D235175419-17062009><FONT =
face=3DArial>I also=20
think that the RFC should say&nbsp;MUST to accomplish its purpose. If a =
common=20
timebase is not used, then the time differences make this draft =
essentially=20
moot. It is a conditional MUST.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D235175419-17062009><FONT=20
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D235175419-17062009><FONT =
face=3DArial>Text:=20
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D235175419-17062009><FONT=20
face=3D"Times New Roman">In order to achieve more rapid and accurate =
sync, as=20
recommended in RFC 3550, all senders and receivers MUST use a common =
reference=20
clock.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D235175419-17062009><FONT=20
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D235175419-17062009><FONT=20
face=3DArial>Art</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D235175419-17062009>
<DIV align=3Dleft><FONT size=3D4>
<P align=3Dleft><SPAN class=3D824485019-14012008></SPAN><STRONG><FONT =
face=3DArial>Art=20
Allison</FONT></STRONG></P>
<DIV align=3Dleft><FONT face=3DArial size=3D3>Senior Director Advanced =
Engineering,=20
Science and Technology</FONT></DIV>
<DIV align=3Dleft><SPAN style=3D"FONT-FAMILY: Arial"><FONT face=3DArial=20
size=3D3></FONT></SPAN>&nbsp;</DIV>
<DIV align=3Dleft><SPAN style=3D"FONT-FAMILY: Arial"><FONT =
size=3D3>National=20
Association of Broadcasters<BR>1771 N Street NW<BR><?xml:namespace =
prefix =3D st1=20
ns =3D "urn:schemas-microsoft-com:office:smarttags" /><st1:place=20
w:st=3D"on"><st1:City w:st=3D"on">Washington</st1:City>, <st1:State=20
w:st=3D"on">DC</st1:State> <st1:PostalCode=20
w:st=3D"on">20036</st1:PostalCode></st1:place><BR>Phone<SPAN =
class=3DGramE>&nbsp;=20
202</SPAN> 429 5418 <BR>Fax&nbsp; 202 775 498<SPAN=20
class=3D824485019-14012008>1</SPAN></FONT></SPAN></DIV>
<DIV align=3Dleft><SPAN style=3D"FONT-FAMILY: Arial"><SPAN=20
class=3D824485019-14012008></SPAN></SPAN><SPAN style=3D"FONT-FAMILY: =
Arial"><A=20
href=3D"blocked::http://www.nab.org"><STRONG><FONT=20
size=3D3>www.nab.org</FONT></STRONG></A></SPAN></DIV>
<P class=3DMsoNormal align=3Dleft><SPAN><STRONG><FONT size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: #ff8000; FONT-FAMILY: Arial">Advocacy=20
&nbsp;Education&nbsp;=20
Innovation</SPAN></FONT></STRONG></SPAN></P></FONT></DIV></SPAN></DIV><BR=
>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 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>Michael A=20
  Dolan<BR><B>Sent:</B> Wednesday, June 17, 2009 3:46 PM<BR><B>To:</B>=20
  avt@ietf.org<BR><B>Subject:</B> Re: [AVT] Fwd: I-D=20
  Action:draft-perkins-avt-rapid-rtp-sync-03.txt<BR></FONT><BR></DIV>
  <DIV></DIV>Colin-<BR><BR>Thanks.&nbsp; I think we're =
close.<BR><BR>3550 only=20
  imprecisely recommends (not requires) using a common clock, and when =
it does,=20
  it uses the term, "wallclock", without defining it.&nbsp; In order for =
the=20
  sync to even approach the numbers implied in this draft, the clocks =
must=20
  indeed be synchronized and they must use the same timebase.&nbsp; =
Failing to=20
  minimally recommend this (even if you believe it is a restatement of =
3550), it=20
  is not possible to achieve the implied sync times.&nbsp; I really =
think you=20
  need to say MUST, but I leave that to you and Thomas.&nbsp; And, it =
should be=20
  tied back to NTP fields since that it is a popular source of =
clock.&nbsp;=20
  Here's a suggestion:<BR><BR>
  <BLOCKQUOTE class=3Dcite cite=3D"" type=3D"cite">2.3 Clock =
Synchronization<BR>In=20
    order to achieve more rapid and accurate sync, as recommended in RFC =
3550,=20
    all senders and receivers should use a common reference clock. When =
NTPv4 is=20
    used, all instances of NTP packets should set the Reference ID =
(refid) field=20
    to the same timebase value (e.g. "GPS" - see NTPv4 Figure 12). =
Signaling for=20
    what Reference ID value is tp be used is accomplished out of band. =
When=20
    NTPv3 is used, all instances of NTP packets should use the same =
timebase,=20
    even if it is not explicitly signaled in the Reference ID field.=20
    <BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>Replace all uses =
of "wallclock", "NTP format clock",=20
    "NTP format wallclock", etc with a single term, such as "common =
reference=20
    clock", to be consistent with the first use in section 1, and to =
remove the=20
    ambiguity of all the varying uses in the =
text.<BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>Add a=20
    reference to NTPv4 (or maybe replace [7] RFC 1305?):<BR><A=20
    =
href=3D"https://datatracker.ietf.org/drafts/draft-ietf-ntp-ntpv4-proto/" =

    =
eudora=3D"autourl">https://datatracker.ietf.org/drafts/draft-ietf-ntp-ntp=
v4-proto/</A>=20
  </BLOCKQUOTE><BR>Regarding the access point timing, I think a note =
would be=20
  good surrounding the tables to diffuse the implication that the 0.04 =
times in=20
  the table are realistic for an expected sync time (even if good for =
other=20
  purposes). We all agree there are other good reasons to send more =
frequent=20
  RTCP SR records that also improve clock accuracy, and are thus =
directly=20
  relevant to this draft. I did not mean to imply otherwise.&nbsp; But I =
think=20
  it would be helpful to more clearly separate those reasons (e.g. =
decoder clock=20
  stability) from sync time expectations.&nbsp; Let me know if you want =
a=20
  specific text suggestion.<BR><BR>Co-locating the RTCP SR records and =
the media=20
  access points is a helpful recommendation, and less systemic than the =
above=20
  points.<BR><BR>Thanks for considering these improvements (I=20
  =
think).<BR><BR>Regards,<BR><BR><X-TAB>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;</X-TAB>Mike<BR><BR><BR>At=20
  06:57 PM 6/17/2009 +0100, Colin Perkins wrote:<BR>
  <BLOCKQUOTE class=3Dcite cite=3D"" type=3D"cite">Michael,<BR><BR>On 16 =
Jun 2009,=20
    at 21:27, Michael A Dolan wrote:<BR>
    <BLOCKQUOTE class=3Dcite cite=3D"" type=3D"cite">FYI, I started out =
in March=20
      with a number of comments, some related to multicast UDLR with 1-2 =
links=20
      and I sense that's too big a topic to try and add at this =
point.&nbsp; My=20
      comments therefore have distilled to addressing two major factors =
in=20
      syncing RTP sessions that I believe overshadow the time =
resolutions being=20
      discussed in the draft, and therefore it is an omission not to =
address=20
      them:<BR><BR>1. Common timebase<BR>2. Media-specific access=20
      points<BR><BR>I stopped short of suggesting we should design =
anything.=20
      Therefore I still believe both topics belong here, and in this =
draft, and=20
      they are not so big as to defer at this point.<BR><BR>For =
clarification, I=20
      wasn't proposing we define a timebase signaling mechanism =
(although I do=20
      think that's a good idea).&nbsp; All I am proposing is to add some =
text=20
      that explains that a common timebase is needed to achieve anything =
near=20
      the implied sync times discussed in this draft. How the senders =
and=20
      receivers figure that out is out of band. But if they don't and =
just go=20
      along with "wallclock", it makes much of the rest of this draft =
irrelevant=20
      since the timebase error will be huge by =
comparison.</BLOCKQUOTE><BR>That's=20
    already stated in RFC 3550. I'm not sure it needs repeating here, =
but can=20
    add something if you want.<BR><BR>
    <BLOCKQUOTE class=3Dcite cite=3D"" type=3D"cite">Regarding the issue =
about=20
      access points, I'm not sure how much background to add, so =
apologies if=20
      this is obvious to everyone. Every media stream type has "access =
points"=20
      that arrive periodically - the point where a decoder can begin to =
decode=20
      the stream. In general, these are a function of the encoding, not =
constant=20
      per type, and not constant per stream. For example in H.264, these =

      typically center around the presence of an IDR frame.&nbsp; HE AAC =
has a=20
      simpler coding structure, but one still can't start decoding =
anywhere in=20
      the stream.&nbsp; The "typical" periods of the H.264 access points =
range=20
      from 0.5 to 2 seconds, depending on the coding.&nbsp; The exact =
period is=20
      application dependent, but is not relevant.&nbsp; The point is =
that these=20
      periods greatly exceed the times shown in the tables which are =
implied to=20
      be the sync times - going as low as 0.04 seconds.&nbsp; The tables =
in this=20
      draft suggesting that RTCP SR packets be sent 0.04 seconds apart =
for high=20
      rate streams. This is interesting (as Thomas notes) for jitter =
management=20
      and clock settling, but that high rate does not help you sync =
since you=20
      can't even start decoding the video for a relatively long time =
after the=20
      0.04 seconds. This is mostly related to issues of late joiners of=20
      course.&nbsp; Therefore, I was suggesting we make note of this =
fact to=20
      clarify there are other factors to sync and acquisition beyond =
receipt of=20
      NTP and the RTCP SR packet, and that these other times far exceed =
0.04=20
      seconds.</BLOCKQUOTE><BR>Okay, that's what I thought you meant. =
That=20
    certainly affects the join times, although I'm not sure I'd call =
that issue=20
    synchronisation latency. We can certainly add some wording to =
highlight it=20
    though.<BR><BR>
    <BLOCKQUOTE class=3Dcite cite=3D"" type=3D"cite">Co-locating in time =
the RTCP SR=20
      packets with their related access points further improves the sync =

      time.&nbsp; For example, if the IDR is every 2 seconds, there is =
no=20
      benefit (for syncing) to sending the RTCP SR more frequently than =
that,=20
      especially if it is aligned with this access point in time.&nbsp; =
If the=20
      RTCP SR packets are sent randomly in time, the sync time is the =
IDR period=20
      plus 1/2 the RTCP SR packet period, on average. This is more of an =

      optimization, but then, that's what this whole draft is about - =
optimizing=20
      the sync time.</BLOCKQUOTE><BR>I agree that co-locating the SR =
information=20
    in time with the random access points helps, and will add something =
to the=20
    draft to say that explicitly if it's not already there. I disagree =
that's=20
    sufficient: sending the SR information more frequently gives the =
receiver=20
    more samples from which to estimate any skew between NTP and RTP =
timestamps,=20
    and gives more information to help filter out any incorrect=20
    mappings.<BR><BR>-- <BR>Colin Perkins<BR><A=20
    =
href=3D"http://csperkins.org/">http://csperkins.org/</A><BR><BR><BR></BLO=
CKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C9EF88.16A67249--

From Borilin@spiritdsp.com  Wed Jun 17 13:21:11 2009
Return-Path: <Borilin@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 454BB28C113 for <avt@core3.amsl.com>; Wed, 17 Jun 2009 13:21:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.948
X-Spam-Level: 
X-Spam-Status: No, score=-1.948 tagged_above=-999 required=5 tests=[AWL=0.651,  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 5AUmoi5WyVEL for <avt@core3.amsl.com>; Wed, 17 Jun 2009 13:21:10 -0700 (PDT)
Received: from mail3.spiritcorp.com (mail3.spiritcorp.com [85.13.194.167]) by core3.amsl.com (Postfix) with ESMTP id 3BBD028C2EE for <avt@ietf.org>; Wed, 17 Jun 2009 13:21:10 -0700 (PDT)
Received: from mail-srv.spiritcorp.com (mail-srv.spiritcorp.com [192.168.125.3]) by mail3.spiritcorp.com (8.13.8/8.14.3) with SMTP id n5HKLK2e068130; Thu, 18 Jun 2009 00:21:21 +0400 (MSD) (envelope-from Borilin@spiritdsp.com)
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: Thu, 18 Jun 2009 00:21:13 +0400
Message-ID: <AA5A65FC22B6F145830AC0EAC7586A6C04C693C0@mail-srv.spiritcorp.com>
In-Reply-To: <6B55710E7F51AD4B93F336052113B85FA4B16F@be150.mail.lan>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Sound level indicators
Thread-Index: Acnvh9LvP0i7bNgVTdO+sJvRX2yGkAAAUl0w
References: <6B55710E7F51AD4B93F336052113B85FA4B16F@be150.mail.lan>
From: "Slava Borilin" <Borilin@spiritdsp.com>
To: "Jonathan Lennox" <jonathan@vidyo.com>, <avt@ietf.org>
X-Scanned-By: MIMEDefang 2.64 on 192.168.125.15
Subject: Re: [AVT] Sound level indicators
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, 17 Jun 2009 20:21:11 -0000

Jonathan,=20

You link doesn't open (

regards,
Slava Borilin
=20

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Jonathan Lennox
Sent: Thursday, June 18, 2009 12:12 AM
To: avt@ietf.org
Subject: [AVT] Sound level indicators

Hi all,

I've just submitted the following draft:

http://www.ietf.org/internet-drafts/draft-lennox-avt-rtp-audio-level-ext
hdr-00.txt

The draft addresses a similar, though not identical, issue, to
draft-ivov-avt-slic-00.

It defines an RTP extension header which indicates the audio level, and
voice activity detection state, of a packet's RTP audio payload.  In
large conferences, this can reduce the load on an audio mixer or other
middlebox which wants to forward only a few of the loudest audio
streams, without requiring it to decode and measure every stream it's
receiving.

Comments are welcome!

--=20
Jonathan Lennox
Vidyo, Inc
jonathan@vidyo.com


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

From jonathan@vidyo.com  Wed Jun 17 13:27:10 2009
Return-Path: <jonathan@vidyo.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 E71DB28C2DB for <avt@core3.amsl.com>; Wed, 17 Jun 2009 13:27:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 xC4-1wOHtgHB for <avt@core3.amsl.com>; Wed, 17 Jun 2009 13:27:10 -0700 (PDT)
Received: from mx1.myoutlookonline.com (mx1.myoutlookonline.com [64.95.72.238]) by core3.amsl.com (Postfix) with ESMTP id B6CD028C2DE for <avt@ietf.org>; Wed, 17 Jun 2009 13:27:09 -0700 (PDT)
Received: from be150.mail.lan ([10.110.20.150]) by mx1.myoutlookonline.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 17 Jun 2009 16:27:21 -0400
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_01C9EF8A.042393EC"
Date: Wed, 17 Jun 2009 16:23:40 -0400
Message-ID: <6B55710E7F51AD4B93F336052113B85F073AE0@be150.mail.lan>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Sound level indicators
Thread-Index: Acnvh9LvP0i7bNgVTdO+sJvRX2yGkAAAUl0wAAAZHis=
References: <6B55710E7F51AD4B93F336052113B85FA4B16F@be150.mail.lan> <AA5A65FC22B6F145830AC0EAC7586A6C04C693C0@mail-srv.spiritcorp.com>
From: "Jonathan Lennox" <jonathan@vidyo.com>
To: "Slava Borilin" <Borilin@spiritdsp.com>, <avt@ietf.org>
X-OriginalArrivalTime: 17 Jun 2009 20:27:21.0484 (UTC) FILETIME=[046234C0:01C9EF8A]
Subject: Re: [AVT] Sound level indicators
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, 17 Jun 2009 20:27:11 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9EF8A.042393EC
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Apologies -- my e-mail client seems to have decided to word-wrap the =
URL.

I'm sending this again using another client.  The URL should be:

http://www.ietf.org/internet-drafts/draft-lennox-avt-rtp-audio-level-exth=
dr-00.txt

The URL ends with ".txt" in case it's word-wrapped again.

-----Original Message-----
From: Slava Borilin [mailto:Borilin@spiritdsp.com]
Sent: Wed 6/17/2009 4:21 PM
To: Jonathan Lennox; avt@ietf.org
Subject: RE: [AVT] Sound level indicators
=20
Jonathan,=20

You link doesn't open (

regards,
Slava Borilin
=20

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Jonathan Lennox
Sent: Thursday, June 18, 2009 12:12 AM
To: avt@ietf.org
Subject: [AVT] Sound level indicators

Hi all,

I've just submitted the following draft:

http://www.ietf.org/internet-drafts/draft-lennox-avt-rtp-audio-level-ext
hdr-00.txt

The draft addresses a similar, though not identical, issue, to
draft-ivov-avt-slic-00.

It defines an RTP extension header which indicates the audio level, and
voice activity detection state, of a packet's RTP audio payload.  In
large conferences, this can reduce the load on an audio mixer or other
middlebox which wants to forward only a few of the loudest audio
streams, without requiring it to decode and measure every stream it's
receiving.

Comments are welcome!

--=20
Jonathan Lennox
Vidyo, Inc
jonathan@vidyo.com


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


------_=_NextPart_001_01C9EF8A.042393EC
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7655.2">
<TITLE>RE: [AVT] Sound level indicators</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>

<P><FONT SIZE=3D2>Apologies -- my e-mail client seems to have decided to =
word-wrap the URL.<BR>
<BR>
I'm sending this again using another client.&nbsp; The URL should =
be:<BR>
<BR>
<A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-lennox-avt-rtp-audio-le=
vel-exthdr-00.txt">http://www.ietf.org/internet-drafts/draft-lennox-avt-r=
tp-audio-level-exthdr-00.txt</A><BR>
<BR>
The URL ends with &quot;.txt&quot; in case it's word-wrapped again.<BR>
<BR>
-----Original Message-----<BR>
From: Slava Borilin [<A =
HREF=3D"mailto:Borilin@spiritdsp.com">mailto:Borilin@spiritdsp.com</A>]<B=
R>
Sent: Wed 6/17/2009 4:21 PM<BR>
To: Jonathan Lennox; avt@ietf.org<BR>
Subject: RE: [AVT] Sound level indicators<BR>
<BR>
Jonathan,<BR>
<BR>
You link doesn't open (<BR>
<BR>
regards,<BR>
Slava Borilin<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: avt-bounces@ietf.org [<A =
HREF=3D"mailto:avt-bounces@ietf.org">mailto:avt-bounces@ietf.org</A>] On =
Behalf Of<BR>
Jonathan Lennox<BR>
Sent: Thursday, June 18, 2009 12:12 AM<BR>
To: avt@ietf.org<BR>
Subject: [AVT] Sound level indicators<BR>
<BR>
Hi all,<BR>
<BR>
I've just submitted the following draft:<BR>
<BR>
<A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-lennox-avt-rtp-audio-le=
vel-ext">http://www.ietf.org/internet-drafts/draft-lennox-avt-rtp-audio-l=
evel-ext</A><BR>
hdr-00.txt<BR>
<BR>
The draft addresses a similar, though not identical, issue, to<BR>
draft-ivov-avt-slic-00.<BR>
<BR>
It defines an RTP extension header which indicates the audio level, =
and<BR>
voice activity detection state, of a packet's RTP audio payload.&nbsp; =
In<BR>
large conferences, this can reduce the load on an audio mixer or =
other<BR>
middlebox which wants to forward only a few of the loudest audio<BR>
streams, without requiring it to decode and measure every stream =
it's<BR>
receiving.<BR>
<BR>
Comments are welcome!<BR>
<BR>
--<BR>
Jonathan Lennox<BR>
Vidyo, Inc<BR>
jonathan@vidyo.com<BR>
<BR>
<BR>
_______________________________________________<BR>
Audio/Video Transport Working Group<BR>
avt@ietf.org<BR>
<A =
HREF=3D"https://www.ietf.org/mailman/listinfo/avt">https://www.ietf.org/m=
ailman/listinfo/avt</A><BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C9EF8A.042393EC--

From Even.roni@huawei.com  Thu Jun 18 02:52:25 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 66EB628C140 for <avt@core3.amsl.com>; Thu, 18 Jun 2009 02:52:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.521
X-Spam-Level: 
X-Spam-Status: No, score=-0.521 tagged_above=-999 required=5 tests=[AWL=-0.645, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_SORBS_WEB=0.619, 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 2ZFJgLpN5igy for <avt@core3.amsl.com>; Thu, 18 Jun 2009 02:52:24 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id AEF2E3A687F for <avt@ietf.org>; Thu, 18 Jun 2009 02:52:23 -0700 (PDT)
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 <0KLF00DNRI3A73@szxga03-in.huawei.com> for avt@ietf.org; Thu, 18 Jun 2009 17:52:22 +0800 (CST)
Received: from huawei.com ([172.24.1.3]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLF00E9LI2VPZ@szxga03-in.huawei.com> for avt@ietf.org; Thu, 18 Jun 2009 17:52:21 +0800 (CST)
Received: from windows8d787f9 (bzq-79-179-78-100.red.bezeqint.net [79.179.78.100]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KLF007MOHXEVO@szxml01-in.huawei.com>; Thu, 18 Jun 2009 17:48:55 +0800 (CST)
Date: Thu, 18 Jun 2009 12:47:17 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com>
To: 'VAN CAENEGEM Tom' <Tom.Van_Caenegem@alcatel-lucent.be>, avt@ietf.org
Message-id: <025301c9eff9$cbc5c1c0$63514540$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAslt0g
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com>
Subject: Re: [AVT] comments on section 10 ofdraft-ietf-avt-rapid-acquisition-for-rtp-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: Thu, 18 Jun 2009 09:52:25 -0000

Hi Tom,
My comment about the text was more about the steps described later in
section 6.2

In step 2 the RS will send the RAMS-I from the RTCP port for the
burst/retransmission stream. This will help the RR to learn his address

In step 4 - update RAM-R, will it be sent to the FT target or to the
burst/retransmission.

In step 8 - specify where to send the RAMS-T not to the RS but to the
burst/retransmission address. 




As for the RTP/RTCP port multiplexing, I do not think that this is a
separate draft. We need to discuss the solution and decide where to it
should go. If the declarative SDP will include RTP/RTCP mux the RAM-R should
acknowledge that it is supported by the RR.

The need for a separate draft discussion is if the RR wants to offer
different ports for receiving the RTP and RTCP, and this needs to be
discussed. The major question is if we need a general mechanism which
requires a new RTCP message or is it just for this case and we can add the
information to the RAMS messages..

Roni

> -----Original Message-----
> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> Sent: Wednesday, June 17, 2009 3:23 PM
> To: Roni Even; avt@ietf.org
> Subject: RE: [AVT] comments on section 10 ofdraft-ietf-avt-rapid-
> acquisition-for-rtp-01
> 
> 
>  Hi Roni,
> 
> Perhaps the start of section 6.2 can be rewritten as follows:
> 
> 
> <START>
> 
> 6.2.  Message Flows
> 
>    Figure 2 shows the main entities involved in rapid acquisition:
> 
>    o  Multicast Source
> 
>    o  Feedback Target (FT)
> 
>    o  Burst/ Retransmission Source
> 
>    o  RTP Receiver (RR)
> 
> (fig 2)
> 
> 
> The feedback target (FT) is the entity as defined in [rtcpssm draft],
> to
> which the RR sends its RTCP FB messages, indicating packet loss in the
> ssm primary stream by means of a NACK or indicating the RR's desire to
> have rapid acquisition of the ssm primary stream (by means of an RTCP
> FB
> message as defined in this document). While the burst/retransmission
> source is responsible for responding on these messages and, in the case
> of rapid acquisition, further RTCP interaction with the RR during this
> acquisition process, it is assumed in the remainder of the document
> that
> these two logical entities (FT and burst/retransmission source) are
> combined in a single physical entity and share state. In the remainder
> of the text, the term retransmission server is used whenever
> appropriate, to refer to the combined functionality of the FT and
> retransmission/burst source. However, it must be noted that only the FT
> is involved in the primary ssm RTP session, whereas the
> burst/retransmission source transmits unicast RTP burst and RTP
> retransmissions packets (both formatted  as RTP retransmission packets
> [RFC4585]) in a single separate unicast RTP retransmission session to
> each RR.
> 
> Note also that the same method (with the identical message flows) would
> also apply in a scenario where rapid acquisition is performed by a
> feedback target co-located with the media source.
> 
> (...)
> 
> <END>
> 
> Tom: As we mandate the retransmission source and burst source to be in
> the same session, I think it is no longer required to split-up among
> these two logical entities. I invite other people, including the
> co-authors to comment on this new text proposal.
> 
> With respect to your comments on the RTP/RTCP port muxing support
> indication by the RR inside the RAMS-R message. That would be needed,
> but is not sufficient as, if only declarative SDP is used, and we want
> to have the possibility that the RTP/RTCP packets in the retransmission
> session can be received by the RR on the same port the RR issues the
> RTCP RAMS-R, we need also a way by which the RR can signal this too. We
> provided a possible solution in the draft, but I understood that you
> think such a solution should be proposed in a separate draft proposal?
> But I guess that would also apply then to the signaling of support for
> RTP/RTCP port muxing by the RR?
> 
> Tom
> 
> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: woensdag 17 juni 2009 13:24
> To: VAN CAENEGEM Tom; avt@ietf.org
> Subject: RE: [AVT] comments on section 10
> ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> 
> Tom,
> I understand the RAMS-R and RAMS-T, the text is not clear enough in
> section
> 6.2
> 
> It still leaves open the issue of the addresses for the RR in the case
> of declarative SDP when there is no answer SDP from the RR.
> 
> About RTP/RTCP multiplexing, the declarative SDP can show that the RS
> supports it and I still think that some information about the
> addressing
> (like support for RTP/RTCP mux) should be supplied in the RAMS-R for
> the
> declarative case.
> 
> Roni
> 
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> > VAN CAENEGEM Tom
> > Sent: Wednesday, June 17, 2009 11:17 AM
> > To: avt@ietf.org
> > Subject: Re: [AVT] comments on section 10 of draft-ietf-avt-rapid-
> > acquisition-for-rtp-01
> >
> > Hi Roni,
> >
> > I think your understanding was indeed different from the general
> >assumptions in this draft. Previously we agreed to only consider the
> >case where there is only one physical entity involved (called the
> >Retransmission Server in the draft), which allows us to NOT consider
> >and  discuss cases where for instance the feedback target (which is
> >defined  in the rtcpssm draft/RFC) is not in the same box as the
> >retransmission  source or burst source, the entities sourcing
> >retransmision/burst  packets. In that case we then would also need to
> >describe how these  separate entities communicate.
> > The fact that these different entities are now in the same box does
> >not  necessarily mean that all interactions and data exchange with the
> >RRs  is  part of the same RTP session, which is in this case the SSM
> >RTP  session.
> > As Ali explained, the NACK and RAMS-R RTCP FB messages are directed
> to
> 
> >the FB target, where we do not  defer from the rtcpssm draft. The RTP
> >retransmission/burst packets that are sent as a response to the NACK
> >and  the RAMS-R can be either session multiplexed with respect to the
> >original SSM RTP session or SSRC muxed (same session), following RFC
> >4588.
> >As the retransmission packets in this case are addressing the RR  in
> >unicast, we obviously have a dedicated RTP session for the
> >retransmission/burst packets. We had some internal discussion on
> >whether  considering the use case of having a separate session between
> >RS and RR  for RTP retransmission packets triggered by an RTCP FB NACK
> >and a  separate session for RTP burst packets triggered by an RTCP
> >RAMS-R made  sense, but we ended up agreeing that allowing a single
> >session was the  easiest way out, without imposing serious limitations
> >to the general  architecture.
> >
> > This means that the ports used by the (single) RTP
> > retransmission/burst session are in principle decoupled from the
> > primary SSM session. Hence if an RR wants to receive the
> > burst/retransmission packets and associated RTCP messages on the same
> > port the RR sent out the RTCP RAMS-R/ NACK FB messages, this should
> > either be signaled by the RR, OR such port usage scheme is considered
> > the "default" case -which also means the RR supports RTP/RTCP port
> > muxing for the retransmission/burst session-, and then the RR needs
> to
> 
> > signal the ports for receiving the RTP and RTCP packets in the
> > retransmission session when it requires dedicated ports.
> >
> > The RAMS-I (RS-> RR) and RAMS-T (RR-> RS) messages are only relevant
> > to a specific RR requesting the RTP burst stream and the RS, and
> carry
> 
> > information/signaling related to the retransmission/burst session and
> > have nothing to do with the SSM session. Hence the FB target as
> > logical entity is not involved here.
> >
> > I hope this clarifies rather than it contributes to your confusion.
> > But we may need to rephrase the part you quoted, as your
> > interpretation was different from its intended meaning. We also tried
> > to be more explicit in which session which RAMS or other RTCP (e.g.
> > Bye) messages needed to be exchanged compared to a previous version
> of
> 
> > the draft, but we are open of course to any other suggestions from
> > your side if this is not clear enough in your opinion.
> >
> > Tom
> >
> >
> >
> >
> >
> >
> > " A Retransmission Source may equally act as a Burst Source.  The
> >    Retransmission Source may also incorporate the Feedback Target
> >    ([I-D.ietf-avt-rtcpssm] permits the feedback target to be a
> >    retransmission server, since it is a logical function to which RRs
> >    send their unicast feedback), and we will use the term
> > Retransmission
> >    Server (RS) in the remainder of the document to refer to a single
> >    physical entity comprising these three entities that share state.
> >    Note that the same method (with the identical message flows) would
> >    also apply in a scenario where rapid acquisition is performed by a
> >    feedback target co-located with the media source."
> >
> > I assumed that we are only dealing with the case that the RS is a
> > single entity and not three different entities with different
> > addresses
> >
> > I also thought that this was agreed in previous discussions
> >
> > If my understanding is not correct I will review the draft since the
> > current text is not explicit enough to specify which part is doing
> > each message. I saw that RAMS-R is going to feedback target but RAMS-
> T
> 
> > is going to RS which is not specifying a specific address according
> to
> 
> > you.
> >
> > Roni
> >
> > -----Original Message-----
> > From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> > Sent: Tuesday, June 16, 2009 10:00 PM
> > To: Roni Even; avt@ietf.org
> > Subject: RE: [AVT] comments on section 10
> > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > Remember that the RAMS-R (RR->RS) message is NOT on the
> retransmission
> > (unicast) session, it's on the primary session since it is sent to
> the
> 
> > feedback target of the primary SSM session. Thus, the source port RR
> > uses to send RAMS-R "cannot" be assumed to be the destination port it
> > wishes to receive the unicast burst on.
> >
> > If you agree with this statement, it is clear why we need port
> > signaling.
> > Muxing will not help much here. It will just reduce the number of
> > signaled ports from 2 to 1.
> >
> > -acbegen
> >
> >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
> > > Of Roni
> > Even
> > > Sent: Tuesday, June 16, 2009 10:08 AM
> > > To: avt@ietf.org
> > > Subject: [AVT] comments on section 10
> > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > >
> > > Hi,
> > >
> > > I looked at section 10 and have some comments
> > >
> > >
> > >
> > > 1.       If RTP/RTCP multiplexing is used, there is no need for any
> > specific operation
> > > from the RR side. The RR sends the RAMS-R message to the RS from
> the
> 
> > > port
> > it wants to
> > > receive the RAMS-I and RTP payload. The RS just sends the
> > > information to
> > the port from
> > > which it received the RAMS-R and not to the one in the SDP
> > >
> > > 2.       In the case where there is no RTP/RTCP multiplexing, the
> > RAMS-R
> > RTCP message will
> > > go to the RS and the RAMS-I will go to the port on the RR from
> where
> 
> > > the
> > RAMS-R was
> > > received. For the RTP, the RR does not know if it has a NAT on the
> > way
> >
> > > to
> > the RS and
> > > should try to get a routable address (using STUN for example) and
> > providing the port to
> > > the RS ( we still need to agree on how to do it)
> > >
> > > 3.       If the above two points are correct than the RR receive
> port
> > in
> > the SDP is not
> > > really useful
> > >
> > >
> > >
> > > Roni Even
> >
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt


From Even.roni@huawei.com  Thu Jun 18 02:54:10 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F366B3A6767 for <avt@core3.amsl.com>; Thu, 18 Jun 2009 02:54:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.493
X-Spam-Level: 
X-Spam-Status: No, score=-1.493 tagged_above=-999 required=5 tests=[AWL=0.487,  BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qN8cVulFm9Ka for <avt@core3.amsl.com>; Thu, 18 Jun 2009 02:54:08 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 318C028C2E0 for <avt@ietf.org>; Thu, 18 Jun 2009 02:53:47 -0700 (PDT)
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 <0KLF00M7SI429A@szxga04-in.huawei.com> for avt@ietf.org; Thu, 18 Jun 2009 17:52:50 +0800 (CST)
Received: from huawei.com ([172.24.1.6]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLF00MW5I422K@szxga04-in.huawei.com> for avt@ietf.org; Thu, 18 Jun 2009 17:52:50 +0800 (CST)
Received: from windows8d787f9 (bzq-79-179-78-100.red.bezeqint.net [79.179.78.100]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KLF009IJI27DV@szxml02-in.huawei.com>; Thu, 18 Jun 2009 17:51:50 +0800 (CST)
Date: Thu, 18 Jun 2009 12:50:08 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com>
To: 'Zeev Vax' <zeevvax@microsoft.com>, "'Bill Ver Steeg (versteb)'" <versteb@cisco.com>, "'Ali C. Begen (abegen)'" <abegen@cisco.com>, 'VAN CAENEGEM Tom' <Tom.Van_Caenegem@alcatel-lucent.be>, avt@ietf.org
Message-id: <025401c9effa$34040170$9c0c0450$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqg
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com>
Subject: Re: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-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: Thu, 18 Jun 2009 09:54:10 -0000

Zeev,
This is a question I had in the past. I think that it merits a separate
thread in order to get a consensus on the issue. Mandating RTP/RTCP
multiplexing for the unicast burst make it simpler and faster to start. 

Note the two ports may still be used for the retransmission case.

Roni



> -----Original Message-----
> From: Zeev Vax [mailto:zeevvax@microsoft.com]
> Sent: Wednesday, June 17, 2009 7:45 PM
> To: Bill Ver Steeg (versteb); Ali C. Begen (abegen); VAN CAENEGEM Tom;
> Roni Even; avt@ietf.org
> Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-
> acquisition-for-rtp-01
> 
> The text proposal looks fine to me.
> I don't think we should mandate support both, this would cause extra
> work in implementation of a solution, and I can't see any benefit.
> Giving that this is UDP traffic port muxing is a subset of separate
> ports, so we can mandate port muxing, and make optional the separate
> ports.
> 
> Zeev
> 
> 
> -----Original Message-----
> From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> Sent: Wednesday, June 17, 2009 8:40 AM
> To: Ali C. Begen (abegen); VAN CAENEGEM Tom; Roni Even; avt@ietf.org;
> Zeev Vax
> Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-
> acquisition-for-rtp-01
> 
> Tom-
> 
> These words looks good to me as well, with the following clarification.
> 
> We do need to consider how we handle RTP/RTCP port muxing throughout
> the
> document, and make the wording consistent wherever we reference the
> ports in use. I am in favor of allowing (but not mandating) the RR to
> signal RTP/RTCP port muxing. This would require the RS to support both
> methods. This is just my opinion, and we need to come to consensus on
> this matter.
> 
> 
> Bill VerSteeg
> 
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Ali C. Begen (abegen)
> Sent: Wednesday, June 17, 2009 10:15 AM
> To: VAN CAENEGEM Tom; Roni Even; avt@ietf.org
> Subject: Re: [AVT] comments on
> section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> 
> The proposed text looks good to me. We should probably put the burst
> and
> retransmission sources in the same block in Figure 2 as well.
> 
> -acbegen
> 
> 
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> > VAN CAENEGEM Tom
> > Sent: Wednesday, June 17, 2009 5:23 AM
> > To: Roni Even; avt@ietf.org
> > Subject: Re: [AVT] comments on section
> > 10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> >
> >  Hi Roni,
> >
> > Perhaps the start of section 6.2 can be rewritten as follows:
> >
> >
> > <START>
> >
> > 6.2.  Message Flows
> >
> >    Figure 2 shows the main entities involved in rapid acquisition:
> >
> >    o  Multicast Source
> >
> >    o  Feedback Target (FT)
> >
> >    o  Burst/ Retransmission Source
> >
> >    o  RTP Receiver (RR)
> >
> > (fig 2)
> >
> >
> > The feedback target (FT) is the entity as defined in [rtcpssm draft],
> > to which the RR sends its RTCP FB messages, indicating packet loss in
> > the ssm primary stream by means of a NACK or indicating the RR's
> > desire to have rapid acquisition of the ssm primary stream (by means
> > of an RTCP FB message as defined in this document). While the
> > burst/retransmission source is responsible for responding on these
> > messages and, in the case of rapid acquisition, further RTCP
> > interaction with the RR during this acquisition process, it is
> assumed
> 
> > in the remainder of the document that these two logical entities (FT
> > and burst/retransmission source) are combined in a single physical
> > entity and share state. In the remainder of the text, the term
> > retransmission server is used whenever appropriate, to refer to the
> > combined functionality of the FT and retransmission/burst source.
> > However, it must be noted that only the FT is involved in the primary
> > ssm RTP session, whereas the burst/retransmission source transmits
> > unicast RTP burst and RTP retransmissions packets (both formatted  as
> > RTP retransmission packets
> > [RFC4585]) in a single separate unicast RTP retransmission session to
> > each RR.
> >
> > Note also that the same method (with the identical message flows)
> > would also apply in a scenario where rapid acquisition is performed
> by
> 
> > a feedback target co-located with the media source.
> >
> > (...)
> >
> > <END>
> >
> > Tom: As we mandate the retransmission source and burst source to be
> in
> 
> > the same session, I think it is no longer required to split-up among
> > these two logical entities. I invite other people, including the
> > co-authors to comment on this new text proposal.
> >
> > With respect to your comments on the RTP/RTCP port muxing support
> > indication by the RR inside the RAMS-R message. That would be needed,
> > but is not sufficient as, if only declarative SDP is used, and we
> want
> 
> > to have the possibility that the RTP/RTCP packets in the
> > retransmission session can be received by the RR on the same port the
> > RR issues the RTCP RAMS-R, we need also a way by which the RR can
> > signal this too. We provided a possible solution in the draft, but I
> > understood that you think such a solution should be proposed in a
> separate draft proposal?
> > But I guess that would also apply then to the signaling of support
> for
> 
> > RTP/RTCP port muxing by the RR?
> >
> > Tom
> >
> > -----Original Message-----
> > From: Roni Even [mailto:Even.roni@huawei.com]
> > Sent: woensdag 17 juni 2009 13:24
> > To: VAN CAENEGEM Tom; avt@ietf.org
> > Subject: RE: [AVT] comments on section 10
> > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > Tom,
> > I understand the RAMS-R and RAMS-T, the text is not clear enough in
> > section
> > 6.2
> >
> > It still leaves open the issue of the addresses for the RR in the
> case
> 
> > of declarative SDP when there is no answer SDP from the RR.
> >
> > About RTP/RTCP multiplexing, the declarative SDP can show that the RS
> > supports it and I still think that some information about the
> > addressing (like support for RTP/RTCP mux) should be supplied in the
> > RAMS-R for the declarative case.
> >
> > Roni
> >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
> > > Of VAN CAENEGEM Tom
> > > Sent: Wednesday, June 17, 2009 11:17 AM
> > > To: avt@ietf.org
> > > Subject: Re: [AVT] comments on section 10 of draft-ietf-avt-rapid-
> > > acquisition-for-rtp-01
> > >
> > > Hi Roni,
> > >
> > > I think your understanding was indeed different from the general
> > >assumptions in this draft. Previously we agreed to only consider the
> > >case where there is only one physical entity involved (called the
> > >Retransmission Server in the draft), which allows us to NOT consider
> > >and  discuss cases where for instance the feedback target (which is
> > >defined  in the rtcpssm draft/RFC) is not in the same box as the
> > >retransmission  source or burst source, the entities sourcing
> > >retransmision/burst  packets. In that case we then would also need
> to
> 
> > >describe how these  separate entities communicate.
> > > The fact that these different entities are now in the same box does
> > >not  necessarily mean that all interactions and data exchange with
> > >the RRs  is  part of the same RTP session, which is in this case the
> > >SSM RTP  session.
> > > As Ali explained, the NACK and RAMS-R RTCP FB messages are directed
> > >to
> >
> > >the FB target, where we do not  defer from the rtcpssm draft. The
> RTP
> 
> > >retransmission/burst packets that are sent as a response to the NACK
> > >and  the RAMS-R can be either session multiplexed with respect to
> the
> 
> > >original SSM RTP session or SSRC muxed (same session), following RFC
> > >4588.
> > >As the retransmission packets in this case are addressing the RR  in
> > >unicast, we obviously have a dedicated RTP session for the
> > >retransmission/burst packets. We had some internal discussion on
> > >whether  considering the use case of having a separate session
> > >between RS and RR  for RTP retransmission packets triggered by an
> > >RTCP FB NACK and a  separate session for RTP burst packets triggered
> > >by an RTCP RAMS-R made  sense, but we ended up agreeing that
> allowing
> 
> > >a single session was the  easiest way out, without imposing serious
> > >limitations to the general  architecture.
> > >
> > > This means that the ports used by the (single) RTP
> > > retransmission/burst session are in principle decoupled from the
> > > primary SSM session. Hence if an RR wants to receive the
> > > burst/retransmission packets and associated RTCP messages on the
> > > same port the RR sent out the RTCP RAMS-R/ NACK FB messages, this
> > > should either be signaled by the RR, OR such port usage scheme is
> > > considered the "default" case -which also means the RR supports
> > > RTP/RTCP port muxing for the retransmission/burst session-, and
> then
> 
> > > the RR needs to
> >
> > > signal the ports for receiving the RTP and RTCP packets in the
> > > retransmission session when it requires dedicated ports.
> > >
> > > The RAMS-I (RS-> RR) and RAMS-T (RR-> RS) messages are only
> relevant
> 
> > > to a specific RR requesting the RTP burst stream and the RS, and
> > > carry
> >
> > > information/signaling related to the retransmission/burst session
> > > and have nothing to do with the SSM session. Hence the FB target as
> > > logical entity is not involved here.
> > >
> > > I hope this clarifies rather than it contributes to your confusion.
> > > But we may need to rephrase the part you quoted, as your
> > > interpretation was different from its intended meaning. We also
> > > tried to be more explicit in which session which RAMS or other RTCP
> (e.g.
> > > Bye) messages needed to be exchanged compared to a previous version
> > > of
> >
> > > the draft, but we are open of course to any other suggestions from
> > > your side if this is not clear enough in your opinion.
> > >
> > > Tom
> > >
> > >
> > >
> > >
> > >
> > >
> > > " A Retransmission Source may equally act as a Burst Source.  The
> > >    Retransmission Source may also incorporate the Feedback Target
> > >    ([I-D.ietf-avt-rtcpssm] permits the feedback target to be a
> > >    retransmission server, since it is a logical function to which
> RRs
> > >    send their unicast feedback), and we will use the term
> > > Retransmission
> > >    Server (RS) in the remainder of the document to refer to a
> single
> > >    physical entity comprising these three entities that share
> state.
> > >    Note that the same method (with the identical message flows)
> would
> > >    also apply in a scenario where rapid acquisition is performed by
> a
> > >    feedback target co-located with the media source."
> > >
> > > I assumed that we are only dealing with the case that the RS is a
> > > single entity and not three different entities with different
> > > addresses
> > >
> > > I also thought that this was agreed in previous discussions
> > >
> > > If my understanding is not correct I will review the draft since
> the
> 
> > > current text is not explicit enough to specify which part is doing
> > > each message. I saw that RAMS-R is going to feedback target but
> > > RAMS-T
> >
> > > is going to RS which is not specifying a specific address according
> > > to
> >
> > > you.
> > >
> > > Roni
> > >
> > > -----Original Message-----
> > > From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> > > Sent: Tuesday, June 16, 2009 10:00 PM
> > > To: Roni Even; avt@ietf.org
> > > Subject: RE: [AVT] comments on section 10
> > > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > >
> > > Remember that the RAMS-R (RR->RS) message is NOT on the
> > > retransmission
> > > (unicast) session, it's on the primary session since it is sent to
> > > the
> >
> > > feedback target of the primary SSM session. Thus, the source port
> RR
> 
> > > uses to send RAMS-R "cannot" be assumed to be the destination port
> > > it wishes to receive the unicast burst on.
> > >
> > > If you agree with this statement, it is clear why we need port
> > > signaling.
> > > Muxing will not help much here. It will just reduce the number of
> > > signaled ports from 2 to 1.
> > >
> > > -acbegen
> > >
> > >
> > > > -----Original Message-----
> > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> Behalf
> 
> > > > Of Roni
> > > Even
> > > > Sent: Tuesday, June 16, 2009 10:08 AM
> > > > To: avt@ietf.org
> > > > Subject: [AVT] comments on section 10
> > > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > > >
> > > > Hi,
> > > >
> > > > I looked at section 10 and have some comments
> > > >
> > > >
> > > >
> > > > 1.       If RTP/RTCP multiplexing is used, there is no need for
> any
> > > specific operation
> > > > from the RR side. The RR sends the RAMS-R message to the RS from
> > > > the
> >
> > > > port
> > > it wants to
> > > > receive the RAMS-I and RTP payload. The RS just sends the
> > > > information to
> > > the port from
> > > > which it received the RAMS-R and not to the one in the SDP
> > > >
> > > > 2.       In the case where there is no RTP/RTCP multiplexing, the
> > > RAMS-R
> > > RTCP message will
> > > > go to the RS and the RAMS-I will go to the port on the RR from
> > > > where
> >
> > > > the
> > > RAMS-R was
> > > > received. For the RTP, the RR does not know if it has a NAT on
> the
> > > way
> > >
> > > > to
> > > the RS and
> > > > should try to get a routable address (using STUN for example) and
> > > providing the port to
> > > > the RS ( we still need to agree on how to do it)
> > > >
> > > > 3.       If the above two points are correct than the RR receive
> > port
> > > in
> > > the SDP is not
> > > > really useful
> > > >
> > > >
> > > >
> > > > Roni Even
> > >
> > >
> > > _______________________________________________
> > > Audio/Video Transport Working Group
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From Tom.Van_Caenegem@alcatel-lucent.be  Thu Jun 18 04:45:22 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 CF02D28C316 for <avt@core3.amsl.com>; Thu, 18 Jun 2009 04:45:22 -0700 (PDT)
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_FR=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 HpLxIKKXmR3W for <avt@core3.amsl.com>; Thu, 18 Jun 2009 04:45:21 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id A428828C30E for <avt@ietf.org>; Thu, 18 Jun 2009 04:45:20 -0700 (PDT)
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 n5IBjEGZ032585;  Thu, 18 Jun 2009 13:45:14 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.52]) by FRVELSBHS04.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 18 Jun 2009 13:45:14 +0200
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: Thu, 18 Jun 2009 13:45:13 +0200
Message-ID: <238382595265324EA50F6134BB42DCAF04047746@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <025301c9eff9$cbc5c1c0$63514540$%roni@huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] comments on section 10 ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAslt0gAAPNq9A=
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <025301c9eff9$cbc5c1c0$63514540$%roni@huawei.com>
From: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>
To: "Roni Even" <Even.roni@huawei.com>, <avt@ietf.org>
X-OriginalArrivalTime: 18 Jun 2009 11:45:14.0458 (UTC) FILETIME=[3E6F23A0:01C9F00A]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Subject: Re: [AVT] comments on section 10 ofdraft-ietf-avt-rapid-acquisition-for-rtp-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: Thu, 18 Jun 2009 11:45:22 -0000

Hi Roni,

I 100% agree with your remarks, and in fact I had proposed additional
text for step 2 and step 8 that clarified which message was sent in
which session and/or to/by whom, but now I notice these clarifying text
fragments seem to have been missed by the main editor in the last draft
release. Bill, can you add these phrases in a subsequent release?

Step 2:=20

Add text: "Both the unicast burst and the RAMS-I message are transmitted
by the burst/retransmission source logical entity that is part of the
RS."


Step 8:=20

Replace "Note that RR MUST send at least one RAMS-T message" by=20

"Note that RR MUST send at least one RAMS-T message, and the RAMS-T
message MUST be addressed to the Burst source logical entity that is
part of the RS." =20


On step 4, I took it kind of for granted that, as RAMS-R update messages
are the same as RAMS-R messages, the RAMS-R update message has to be
sent towards the FT... But you are right, that this should be explicitly
mentioned in the draft. One could even argue this message should be sent
to the Burst/Retransmission Source entity  as it services the purpose of
controling the RTP burst (similar as an RAMS-T message), but I would
suggest that this message is addressed to the FT, based on my previous
reasoning.=20

So for Step 4,  I'd propose to change the current sentence  "RR MAY send
a new RAMS-R message with a different value for one or more fields of an
earlier RAMS-R message."  to  "RR MAY send a new RAMS-R message to the
FT entity of the RS, with a different value for one or more fields of an
earlier RAMS-R  message."


Tom

  =20

-----Original Message-----
From: Roni Even [mailto:Even.roni@huawei.com]=20
Sent: donderdag 18 juni 2009 11:47
To: VAN CAENEGEM Tom; avt@ietf.org
Subject: RE: [AVT] comments on section 10
ofdraft-ietf-avt-rapid-acquisition-for-rtp-01

Hi Tom,
My comment about the text was more about the steps described later in
section 6.2

In step 2 the RS will send the RAMS-I from the RTCP port for the
burst/retransmission stream. This will help the RR to learn his address

In step 4 - update RAM-R, will it be sent to the FT target or to the
burst/retransmission.

In step 8 - specify where to send the RAMS-T not to the RS but to the
burst/retransmission address.=20




As for the RTP/RTCP port multiplexing, I do not think that this is a
separate draft. We need to discuss the solution and decide where to it
should go. If the declarative SDP will include RTP/RTCP mux the RAM-R
should acknowledge that it is supported by the RR.

The need for a separate draft discussion is if the RR wants to offer
different ports for receiving the RTP and RTCP, and this needs to be
discussed. The major question is if we need a general mechanism which
requires a new RTCP message or is it just for this case and we can add
the information to the RAMS messages..

Roni

> -----Original Message-----
> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> Sent: Wednesday, June 17, 2009 3:23 PM
> To: Roni Even; avt@ietf.org
> Subject: RE: [AVT] comments on section 10 ofdraft-ietf-avt-rapid-
> acquisition-for-rtp-01
>=20
>=20
>  Hi Roni,
>=20
> Perhaps the start of section 6.2 can be rewritten as follows:
>=20
>=20
> <START>
>=20
> 6.2.  Message Flows
>=20
>    Figure 2 shows the main entities involved in rapid acquisition:
>=20
>    o  Multicast Source
>=20
>    o  Feedback Target (FT)
>=20
>    o  Burst/ Retransmission Source
>=20
>    o  RTP Receiver (RR)
>=20
> (fig 2)
>=20
>=20
> The feedback target (FT) is the entity as defined in [rtcpssm draft],=20
> to which the RR sends its RTCP FB messages, indicating packet loss in=20
> the ssm primary stream by means of a NACK or indicating the RR's=20
> desire to have rapid acquisition of the ssm primary stream (by means=20
> of an RTCP FB message as defined in this document). While the=20
> burst/retransmission source is responsible for responding on these=20
> messages and, in the case of rapid acquisition, further RTCP=20
> interaction with the RR during this acquisition process, it is assumed

> in the remainder of the document that these two logical entities (FT=20
> and burst/retransmission source) are combined in a single physical=20
> entity and share state. In the remainder of the text, the term=20
> retransmission server is used whenever appropriate, to refer to the=20
> combined functionality of the FT and retransmission/burst source.=20
> However, it must be noted that only the FT is involved in the primary=20
> ssm RTP session, whereas the burst/retransmission source transmits=20
> unicast RTP burst and RTP retransmissions packets (both formatted  as=20
> RTP retransmission packets
> [RFC4585]) in a single separate unicast RTP retransmission session to=20
> each RR.
>=20
> Note also that the same method (with the identical message flows)=20
> would also apply in a scenario where rapid acquisition is performed by

> a feedback target co-located with the media source.
>=20
> (...)
>=20
> <END>
>=20
> Tom: As we mandate the retransmission source and burst source to be in

> the same session, I think it is no longer required to split-up among=20
> these two logical entities. I invite other people, including the=20
> co-authors to comment on this new text proposal.
>=20
> With respect to your comments on the RTP/RTCP port muxing support=20
> indication by the RR inside the RAMS-R message. That would be needed,=20
> but is not sufficient as, if only declarative SDP is used, and we want

> to have the possibility that the RTP/RTCP packets in the=20
> retransmission session can be received by the RR on the same port the=20
> RR issues the RTCP RAMS-R, we need also a way by which the RR can=20
> signal this too. We provided a possible solution in the draft, but I=20
> understood that you think such a solution should be proposed in a
separate draft proposal?
> But I guess that would also apply then to the signaling of support for

> RTP/RTCP port muxing by the RR?
>=20
> Tom
>=20
> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: woensdag 17 juni 2009 13:24
> To: VAN CAENEGEM Tom; avt@ietf.org
> Subject: RE: [AVT] comments on section 10
> ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
> Tom,
> I understand the RAMS-R and RAMS-T, the text is not clear enough in=20
> section
> 6.2
>=20
> It still leaves open the issue of the addresses for the RR in the case

> of declarative SDP when there is no answer SDP from the RR.
>=20
> About RTP/RTCP multiplexing, the declarative SDP can show that the RS=20
> supports it and I still think that some information about the=20
> addressing (like support for RTP/RTCP mux) should be supplied in the=20
> RAMS-R for the declarative case.
>=20
> Roni
>=20
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf=20
> > Of VAN CAENEGEM Tom
> > Sent: Wednesday, June 17, 2009 11:17 AM
> > To: avt@ietf.org
> > Subject: Re: [AVT] comments on section 10 of draft-ietf-avt-rapid-
> > acquisition-for-rtp-01
> >
> > Hi Roni,
> >
> > I think your understanding was indeed different from the general=20
> >assumptions in this draft. Previously we agreed to only consider the=20
> >case where there is only one physical entity involved (called the=20
> >Retransmission Server in the draft), which allows us to NOT consider=20
> >and  discuss cases where for instance the feedback target (which is=20
> >defined  in the rtcpssm draft/RFC) is not in the same box as the=20
> >retransmission  source or burst source, the entities sourcing=20
> >retransmision/burst  packets. In that case we then would also need to

> >describe how these  separate entities communicate.
> > The fact that these different entities are now in the same box does=20
> >not  necessarily mean that all interactions and data exchange with=20
> >the RRs  is  part of the same RTP session, which is in this case the=20
> >SSM RTP  session.
> > As Ali explained, the NACK and RAMS-R RTCP FB messages are directed
> to
>=20
> >the FB target, where we do not  defer from the rtcpssm draft. The RTP

> >retransmission/burst packets that are sent as a response to the NACK=20
> >and  the RAMS-R can be either session multiplexed with respect to the

> >original SSM RTP session or SSRC muxed (same session), following RFC=20
> >4588.
> >As the retransmission packets in this case are addressing the RR  in=20
> >unicast, we obviously have a dedicated RTP session for the=20
> >retransmission/burst packets. We had some internal discussion on=20
> >whether  considering the use case of having a separate session=20
> >between RS and RR  for RTP retransmission packets triggered by an=20
> >RTCP FB NACK and a  separate session for RTP burst packets triggered=20
> >by an RTCP RAMS-R made  sense, but we ended up agreeing that allowing

> >a single session was the  easiest way out, without imposing serious=20
> >limitations to the general  architecture.
> >
> > This means that the ports used by the (single) RTP=20
> > retransmission/burst session are in principle decoupled from the=20
> > primary SSM session. Hence if an RR wants to receive the=20
> > burst/retransmission packets and associated RTCP messages on the=20
> > same port the RR sent out the RTCP RAMS-R/ NACK FB messages, this=20
> > should either be signaled by the RR, OR such port usage scheme is=20
> > considered the "default" case -which also means the RR supports=20
> > RTP/RTCP port muxing for the retransmission/burst session-, and then

> > the RR needs
> to
>=20
> > signal the ports for receiving the RTP and RTCP packets in the=20
> > retransmission session when it requires dedicated ports.
> >
> > The RAMS-I (RS-> RR) and RAMS-T (RR-> RS) messages are only relevant

> > to a specific RR requesting the RTP burst stream and the RS, and
> carry
>=20
> > information/signaling related to the retransmission/burst session=20
> > and have nothing to do with the SSM session. Hence the FB target as=20
> > logical entity is not involved here.
> >
> > I hope this clarifies rather than it contributes to your confusion.
> > But we may need to rephrase the part you quoted, as your=20
> > interpretation was different from its intended meaning. We also=20
> > tried to be more explicit in which session which RAMS or other RTCP
(e.g.
> > Bye) messages needed to be exchanged compared to a previous version
> of
>=20
> > the draft, but we are open of course to any other suggestions from=20
> > your side if this is not clear enough in your opinion.
> >
> > Tom
> >
> >
> >
> >
> >
> >
> > " A Retransmission Source may equally act as a Burst Source.  The
> >    Retransmission Source may also incorporate the Feedback Target
> >    ([I-D.ietf-avt-rtcpssm] permits the feedback target to be a
> >    retransmission server, since it is a logical function to which
RRs
> >    send their unicast feedback), and we will use the term=20
> > Retransmission
> >    Server (RS) in the remainder of the document to refer to a single
> >    physical entity comprising these three entities that share state.
> >    Note that the same method (with the identical message flows)
would
> >    also apply in a scenario where rapid acquisition is performed by
a
> >    feedback target co-located with the media source."
> >
> > I assumed that we are only dealing with the case that the RS is a=20
> > single entity and not three different entities with different=20
> > addresses
> >
> > I also thought that this was agreed in previous discussions
> >
> > If my understanding is not correct I will review the draft since the

> > current text is not explicit enough to specify which part is doing=20
> > each message. I saw that RAMS-R is going to feedback target but=20
> > RAMS-
> T
>=20
> > is going to RS which is not specifying a specific address according
> to
>=20
> > you.
> >
> > Roni
> >
> > -----Original Message-----
> > From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> > Sent: Tuesday, June 16, 2009 10:00 PM
> > To: Roni Even; avt@ietf.org
> > Subject: RE: [AVT] comments on section 10
> > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > Remember that the RAMS-R (RR->RS) message is NOT on the
> retransmission
> > (unicast) session, it's on the primary session since it is sent to
> the
>=20
> > feedback target of the primary SSM session. Thus, the source port RR

> > uses to send RAMS-R "cannot" be assumed to be the destination port=20
> > it wishes to receive the unicast burst on.
> >
> > If you agree with this statement, it is clear why we need port=20
> > signaling.
> > Muxing will not help much here. It will just reduce the number of=20
> > signaled ports from 2 to 1.
> >
> > -acbegen
> >
> >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf

> > > Of Roni
> > Even
> > > Sent: Tuesday, June 16, 2009 10:08 AM
> > > To: avt@ietf.org
> > > Subject: [AVT] comments on section 10
> > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > >
> > > Hi,
> > >
> > > I looked at section 10 and have some comments
> > >
> > >
> > >
> > > 1.       If RTP/RTCP multiplexing is used, there is no need for
any
> > specific operation
> > > from the RR side. The RR sends the RAMS-R message to the RS from
> the
>=20
> > > port
> > it wants to
> > > receive the RAMS-I and RTP payload. The RS just sends the=20
> > > information to
> > the port from
> > > which it received the RAMS-R and not to the one in the SDP
> > >
> > > 2.       In the case where there is no RTP/RTCP multiplexing, the
> > RAMS-R
> > RTCP message will
> > > go to the RS and the RAMS-I will go to the port on the RR from
> where
>=20
> > > the
> > RAMS-R was
> > > received. For the RTP, the RR does not know if it has a NAT on the
> > way
> >
> > > to
> > the RS and
> > > should try to get a routable address (using STUN for example) and
> > providing the port to
> > > the RS ( we still need to agree on how to do it)
> > >
> > > 3.       If the above two points are correct than the RR receive
> port
> > in
> > the SDP is not
> > > really useful
> > >
> > >
> > >
> > > Roni Even
> >
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt


From Thomas.Schierl@hhi.fraunhofer.de  Thu Jun 18 06:51:24 2009
Return-Path: <Thomas.Schierl@hhi.fraunhofer.de>
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 3247628C127 for <avt@core3.amsl.com>; Thu, 18 Jun 2009 06:51:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.801
X-Spam-Level: 
X-Spam-Status: No, score=-4.801 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, 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 6GtrgDPaQfaX for <avt@core3.amsl.com>; Thu, 18 Jun 2009 06:51:23 -0700 (PDT)
Received: from mail.hhi.fraunhofer.de (mail.HHI.FRAUNHOFER.DE [193.174.67.45]) by core3.amsl.com (Postfix) with ESMTP id A690628C13E for <avt@ietf.org>; Thu, 18 Jun 2009 06:51:22 -0700 (PDT)
Received: by mail.hhi.fraunhofer.de (Postfix, from userid 65534) id AE5AC1D88FB1; Thu, 18 Jun 2009 15:51:30 +0200 (CEST)
Received: from imsva.hhi.de (unknown [127.0.0.1]) by IMSA (Postfix) with ESMTP id E151F150036; Thu, 18 Jun 2009 15:51:31 +0200 (CEST)
Received: from [172.19.40.6] (ipamfw.iphhi.de [212.202.149.138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Thomas Schierl", Issuer "Fraunhofer-Gesellschaft Root-CA v2" (not verified)) by mail.hhi.fraunhofer.de (Postfix) with ESMTP id C8C341D88F4D; Thu, 18 Jun 2009 15:51:29 +0200 (CEST)
Message-ID: <4A3A4662.9020203@hhi.fraunhofer.de>
Date: Thu, 18 Jun 2009 15:51:30 +0200
From: Thomas Schierl <Thomas.Schierl@hhi.fraunhofer.de>
Organization: Fraunhofer HHI
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Roni Even <Even.roni@huawei.com>
References: <4A360A7E.4090400@hhi.fraunhofer.de> <01a201c9ef58$ba490d40$2edb27c0$%roni@huawei.com>
In-Reply-To: <01a201c9ef58$ba490d40$2edb27c0$%roni@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-alterMIME: Yes
Cc: 'Roni Even' <ron.even.tlv@gmail.com>, 'Colin Perkins' <csp@csperkins.org>, 'avt' <avt@ietf.org>, 'Tom Taylor' <tom.taylor@rogers.com>
Subject: Re: [AVT] [Fwd: I-D Action:draft-ietf-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: Thu, 18 Jun 2009 13:51:24 -0000

Hi Roni,
No problem to put it as an informal section.
Thomas

-- 
Thomas Schierl
--------------
Fraunhofer HHI




Roni Even wrote:
> Thomas,
> I read the draft, the major comment I have is that section 4.3 looks to me
> like it describe one use case and should be in formational. It just repeats
> text from SVC. Maybe, if you want to have it, it should be a separate
> section that will be specified as an informational section.
> Roni
>
>   
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
>> Thomas Schierl
>> Sent: Monday, June 15, 2009 11:47 AM
>> To: avt
>> Cc: Roni Even; Tom Taylor; Colin Perkins
>> Subject: [AVT] [Fwd: I-D Action:draft-ietf-avt-rapid-rtp-sync-02.txt]
>>
>> Dear all,
>>
>> Please find pointer to the revised version -02 of draft-ietf-avt-rapid-
>> rtp-sync below.
>>
>> We addressed the reaming open issues and completed all sections.
>>
>> Any comments are welcome. Due to the timing constraints, we would like
>> to ask if we can go ahead with WGLC for this draft.
>>
>> Best regards,
>> Thomas
>>
>> --
>> Thomas Schierl
>> --------------
>> Fraunhofer HHI
>>
>>
>> ---
>> Visit us at
>>
>> IEEE ICC 2009 / June 14-18 / Dresden, Germany / International Congress
>> Center
>> http://www.hhi.fraunhofer.de/icc
>>
>> Laser World of Photonics 2009 / June 15-18 / Munich, Germay / Hall B1,
>> Booth 461
>> http://world-of-photonics.net/de/laser/start
>>     
>
>
>   


From Tom.Van_Caenegem@alcatel-lucent.be  Thu Jun 18 07:17:20 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 856D228C2E8 for <avt@core3.amsl.com>; Thu, 18 Jun 2009 07:17:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.248
X-Spam-Level: 
X-Spam-Status: No, score=-4.248 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 neJk5si1gZxj for <avt@core3.amsl.com>; Thu, 18 Jun 2009 07:17:15 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id A0B2D3A6A70 for <avt@ietf.org>; Thu, 18 Jun 2009 07:17:13 -0700 (PDT)
Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.dc-m.alcatel-lucent.com [155.132.6.76]) by smail2.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5IEGwv8011062 for <avt@ietf.org>; Thu, 18 Jun 2009 16:17:21 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.52]) by FRVELSBHS04.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 18 Jun 2009 16:17:18 +0200
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_01C9F01F.7C774478"
Date: Thu, 18 Jun 2009 16:17:17 +0200
Message-ID: <238382595265324EA50F6134BB42DCAF0408CAE6@FRVELSMBS22.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Some comments on " Multicast Acquisition Report Block Type for RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-01)
Thread-Index: AcnwH3wb2QndKgItQv2Gbyp/65/cCA==
From: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>
To: <avt@ietf.org>
X-OriginalArrivalTime: 18 Jun 2009 14:17:18.0134 (UTC) FILETIME=[7C919D60:01C9F01F]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.80
Subject: [AVT] Some comments on " Multicast Acquisition Report Block Type for RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-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: Thu, 18 Jun 2009 14:17:20 -0000

This is a multi-part message in MIME format.

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

Hi Ali,

I have a few comments/questions related to the draft:

Comment 1:  The abstract now has a sentence: "For quality reporting,
monitoring and diagnostics purposes, it is important to collect detailed
information from the RTP receivers about their acquisition experiences."
Doesn't it go beyond "RTP (receivers)" and "acquisition" as you also
define e.g. a TLV related to presentation time delay (sometimes the MC
RTP delivered content may not even be displayed) and application delay.
I have no problem with the definition of such fields, but IMO it makes
sense to make this clear in the abstract.=20

Comment 2: Base Report

The only informational field here is "response". It is still not
defined, but you refer to the response code in RAMS draft (e.g.
"success", etc).

I guess it is not possible to signal to an RR which additional info to
send, i.e which TLV fields to use...From that point of view, would it
not make sense to have some basic information -now defined in some TLV
fields in the base report- that is always present, to enhance
interoperability. I know we need to find the right balance between
useful information reporting ,  bandwidth efficiency, and receiver
reporting capabilities.

Candidate fields that could be inside this fixed base report are:
-flag/field indicating whether the report refers to a normal acquisition
(based on SFGMP)  or rapid MC RTP acquisition (or rather  the intention
by the RR to perform  a rapid acquisition) for instance by means of RAMS
-a response code which you have indeed defined and its interpretation
should be dependent on the previously mentioned flag/field
-initial launched request (either 1st RAMS-R for rapid acquisition,
either 1st IGMP-join in case of normal acquisition) to 1st received RTP
packet (always a multicast packet for normal acquisition and "normally"
a burst packet when a rapid acquisition process was involved) delta time
-application request to initial launched request (either 1st RAMS-R for
rapid acquisition, either 1st IGMP-join in case of normal acquisition)
delta time=20

For these last two fields, a value must be specified that would indicate
that the field is not filled out (because the receiver client
implementation may not support it).
There could still be other fields that apply to both acquisition
processes and fit in the base report, but they should be application
independent (e.g. delta to presentation time is clearly app dependent)

Regards
Tom

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7655.1">
<TITLE>Some comments on &quot; Multicast Acquisition Report Block Type =
for RTCP XR&quot; (draft-begen-avt-rapid-sync-rtcp-xr-01)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Hi =
Ali,</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">I have a few =
comments/questions related to the draft:</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Comment 1:&nbsp; =
The abstract now has a sentence: &quot;</FONT><FONT FACE=3D"Times New =
Roman">For quality reporting, monitoring and diagnostics purposes, it is =
important to collect detailed information from the RTP receivers about =
their acquisition experiences.&quot;&nbsp; Doesn't it go beyond =
&quot;RTP (receivers)&quot; and &quot;acquisition&quot; as you also =
define e.g. a TLV related to presentation time delay (sometimes the MC =
RTP delivered content may not even be displayed) and application delay. =
I have no problem with the definition of such fields, but IMO it makes =
sense to make this clear in the abstract. </FONT></SPAN></P>

<P><SPAN LANG=3D"nl-be"><FONT SIZE=3D2 FACE=3D"Arial">Comment 2: Base =
Report</FONT></SPAN>
</P>

<P><SPAN LANG=3D"nl-be"><FONT SIZE=3D2 FACE=3D"Arial">The only =
informational field here is &quot;response&quot;. It is still not =
defined, but you refer to the response code in RAMS draft (e.g. =
&quot;success&quot;, etc).</FONT></SPAN></P>

<P><SPAN LANG=3D"nl-be"><FONT SIZE=3D2 FACE=3D"Arial">I guess it is not =
possible to signal to an RR which additional info to send, i.e which TLV =
fields to use&#8230;From that point of view, would it not make sense to =
have some basic information -now defined in some TLV fields in the base =
report- that is always present, to enhance interoperability. I know we =
need to find the right balance between useful information reporting =
,&nbsp; bandwidth efficiency, and receiver reporting =
capabilities.</FONT></SPAN></P>

<P><SPAN LANG=3D"nl-be"><FONT SIZE=3D2 FACE=3D"Arial">Candidate fields =
that could be inside this fixed base report are:</FONT></SPAN>

<BR><SPAN LANG=3D"nl-be"><FONT SIZE=3D2 FACE=3D"Arial">-flag/field =
indicating whether the report refers to a normal acquisition (based on =
SFGMP)&nbsp; or rapid MC RTP acquisition (or rather&nbsp; the intention =
by the RR to perform&nbsp; a rapid acquisition) for instance by means of =
RAMS</FONT></SPAN></P>

<P><SPAN LANG=3D"nl-be"><FONT SIZE=3D2 FACE=3D"Arial">-a response code =
which you have indeed defined and its interpretation should be dependent =
on the previously mentioned flag/field</FONT></SPAN></P>

<P><SPAN LANG=3D"nl-be"><FONT SIZE=3D2 FACE=3D"Arial">-initial launched =
request (either 1st RAMS-R for rapid acquisition, either 1st IGMP-join =
in case of normal acquisition) to 1st received RTP packet (always a =
multicast packet for normal acquisition and &quot;normally&quot; a burst =
packet when a rapid acquisition process was involved) delta =
time</FONT></SPAN></P>

<P><SPAN LANG=3D"nl-be"><FONT SIZE=3D2 FACE=3D"Arial">-application =
request to initial launched request (either 1st RAMS-R for rapid =
acquisition, either 1st IGMP-join in case of normal acquisition) delta =
time </FONT></SPAN></P>

<P><SPAN LANG=3D"nl-be"><FONT SIZE=3D2 FACE=3D"Arial">For these last two =
fields, a value must be specified that would indicate that the field is =
not filled out (because the receiver client implementation may not =
support it).</FONT></SPAN></P>

<P><SPAN LANG=3D"nl-be"><FONT SIZE=3D2 FACE=3D"Arial">There could still =
be other fields that apply to both acquisition processes and fit in the =
base report, but they should be application independent (e.g. delta to =
presentation time is clearly app dependent)</FONT></SPAN></P>

<P><SPAN LANG=3D"nl-be"><FONT SIZE=3D2 =
FACE=3D"Arial">Regards</FONT></SPAN>

<BR><SPAN LANG=3D"nl-be"><FONT SIZE=3D2 FACE=3D"Arial">Tom</FONT></SPAN>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C9F01F.7C774478--

From enrico.marocco@telecomitalia.it  Thu Jun 18 07:24:48 2009
Return-Path: <enrico.marocco@telecomitalia.it>
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 5488D3A69F7 for <avt@core3.amsl.com>; Thu, 18 Jun 2009 07:24:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level: 
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 g6h2pcmg0d+o for <avt@core3.amsl.com>; Thu, 18 Jun 2009 07:24:47 -0700 (PDT)
Received: from GRFEDG702BA020.telecomitalia.it (grfedg702ba020.telecomitalia.it [156.54.233.201]) by core3.amsl.com (Postfix) with ESMTP id 174933A67F2 for <avt@ietf.org>; Thu, 18 Jun 2009 07:24:47 -0700 (PDT)
Received: from GRFHUB701BA020.griffon.local (10.188.101.111) by GRFEDG702BA020.telecomitalia.it (10.188.45.101) with Microsoft SMTP Server (TLS) id 8.1.340.0; Thu, 18 Jun 2009 16:24:57 +0200
Received: from [10.229.8.41] (10.229.8.41) by smtp.telecomitalia.it (10.188.101.114) with Microsoft SMTP Server (TLS) id 8.1.359.3; Thu, 18 Jun 2009 16:24:56 +0200
Message-ID: <4A3A4E40.2060801@telecomitalia.it>
Date: Thu, 18 Jun 2009 16:25:04 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103)
MIME-Version: 1.0
To: Jonathan Lennox <jonathan@vidyo.com>
References: <6B55710E7F51AD4B93F336052113B85FA4B16F@be150.mail.lan>
In-Reply-To: <6B55710E7F51AD4B93F336052113B85FA4B16F@be150.mail.lan>
X-Enigmail-Version: 0.95.0
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms020109010307000804040008"
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVT] Sound level indicators
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, 18 Jun 2009 14:24:48 -0000

--------------ms020109010307000804040008
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Jonathan Lennox wrote:
> http://www.ietf.org/internet-drafts/draft-lennox-avt-rtp-audio-level-ext
> hdr-00.txt
> 
> The draft addresses a similar, though not identical, issue, to
> draft-ivov-avt-slic-00.
> 
> It defines an RTP extension header which indicates the audio level, and
> voice activity detection state, of a packet's RTP audio payload.  In
> large conferences, this can reduce the load on an audio mixer or other
> middlebox which wants to forward only a few of the loudest audio
> streams, without requiring it to decode and measure every stream it's
> receiving.

I may have not given enough thought to all the side issues, but it seems
to me that the two drafts deal with the very same kind of information
(and thus its encoding should be specified in only one place).

To me, the main issue with passing the sound level of a non-mixed stream
has to do with the fact that the RTP header is not going to be encrypted
when using SRTP: an in-line attacker could mute a conference participant
just mangling such value or, if the header is integrity protected,
dropping those packets where voice activity is reported.

-- 
Ciao,
Enrico

--------------ms020109010307000804040008
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJwTCC
AzswggKkoAMCAQICEEIEYmjMZBX3Us1Th/pMjJYwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDMxNjE3NTMwMloX
DTEwMDMxNjE3NTMwMlowejEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEuMCwG
CSqGSIb3DQEJARYfZW5yaWNvLm1hcm9jY29AdGVsZWNvbWl0YWxpYS5pdDEnMCUGCSqGSIb3
DQEJARYYZW5yaWNvLm1hcm9jY29AZ21haWwuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAvd38YWuquonbz4lP4GKp0qij0v4MgXpK/BW87GvoqHz3iQvO1Tb6f4yEtFel
vpK2drtUHWyY+ww6QQSOGJvSWEKTRVX5KsXpN2yNeY4kceezCjsXBvwNPlGHrzJifUByvwzD
QSnQLocE1i89x7P2T5brcaGBBgricwQL1Cggg97zp1yGrj2VIJE03GSpEL01d+omAFUou3mx
8R/9XOnGnSlDpcOV6s2Ww3NN07+7sSBaE0vcvlYF8pr1BWDl2JJobG9qpC9DlplpDZOdmsAG
u/qwsI0AsucY5ZBFKqzKizQ5PGhrh3u2PHRGNncuHUANF0cPfVs7AHjHjudH7PzU2wIDAQAB
o1YwVDBEBgNVHREEPTA7gR9lbnJpY28ubWFyb2Njb0B0ZWxlY29taXRhbGlhLml0gRhlbnJp
Y28ubWFyb2Njb0BnbWFpbC5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOBgQB3
Mi6SymgE1cfsbmr5LWvWVdO58/a0O95kXL2puRn9kGjFN1tAzHQc/UxJs0gIyRRs3gGBR+p6
TT1gmnucO8Ji0gJBMBL+ogcfyaV30hZtUceiRevemXvZW2QOCLdYUf6KdB6ccX7r3a58SRRL
l5YTZ7bIhyAEmeI60ioyMI8U5jCCAzswggKkoAMCAQICEEIEYmjMZBX3Us1Th/pMjJYwDQYJ
KoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5n
IChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5n
IENBMB4XDTA5MDMxNjE3NTMwMloXDTEwMDMxNjE3NTMwMlowejEfMB0GA1UEAxMWVGhhd3Rl
IEZyZWVtYWlsIE1lbWJlcjEuMCwGCSqGSIb3DQEJARYfZW5yaWNvLm1hcm9jY29AdGVsZWNv
bWl0YWxpYS5pdDEnMCUGCSqGSIb3DQEJARYYZW5yaWNvLm1hcm9jY29AZ21haWwuY29tMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvd38YWuquonbz4lP4GKp0qij0v4MgXpK
/BW87GvoqHz3iQvO1Tb6f4yEtFelvpK2drtUHWyY+ww6QQSOGJvSWEKTRVX5KsXpN2yNeY4k
ceezCjsXBvwNPlGHrzJifUByvwzDQSnQLocE1i89x7P2T5brcaGBBgricwQL1Cggg97zp1yG
rj2VIJE03GSpEL01d+omAFUou3mx8R/9XOnGnSlDpcOV6s2Ww3NN07+7sSBaE0vcvlYF8pr1
BWDl2JJobG9qpC9DlplpDZOdmsAGu/qwsI0AsucY5ZBFKqzKizQ5PGhrh3u2PHRGNncuHUAN
F0cPfVs7AHjHjudH7PzU2wIDAQABo1YwVDBEBgNVHREEPTA7gR9lbnJpY28ubWFyb2Njb0B0
ZWxlY29taXRhbGlhLml0gRhlbnJpY28ubWFyb2Njb0BnbWFpbC5jb20wDAYDVR0TAQH/BAIw
ADANBgkqhkiG9w0BAQUFAAOBgQB3Mi6SymgE1cfsbmr5LWvWVdO58/a0O95kXL2puRn9kGjF
N1tAzHQc/UxJs0gIyRRs3gGBR+p6TT1gmnucO8Ji0gJBMBL+ogcfyaV30hZtUceiRevemXvZ
W2QOCLdYUf6KdB6ccX7r3a58SRRLl5YTZ7bIhyAEmeI60ioyMI8U5jCCAz8wggKooAMCAQIC
AQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENh
cGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAm
BgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0
ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1h
aWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNV
BAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQD
EyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEF
AAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B
1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79A
gAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8E
CDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3
dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEa
MBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7M
DaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUa
C4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk1
3iSx0x1G/11fZU8xggNxMIIDbQIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3
dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJl
ZW1haWwgSXNzdWluZyBDQQIQQgRiaMxkFfdSzVOH+kyMljAJBgUrDgMCGgUAoIIB0DAYBgkq
hkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wOTA2MTgxNDI1MDRaMCMG
CSqGSIb3DQEJBDEWBBTI3V5W47cd2X4p6+7S3KzI5KjOEDBfBgkqhkiG9w0BCQ8xUjBQMAsG
CWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAw
BwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMC
WkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1Ro
YXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhBCBGJozGQV91LNU4f6TIyWMIGH
BgsqhkiG9w0BCRACCzF4oHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25z
dWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJ
c3N1aW5nIENBAhBCBGJozGQV91LNU4f6TIyWMA0GCSqGSIb3DQEBAQUABIIBAAlHCJz3S+Bd
WmD/tPZXRZbqLaOnKvZ6lZxh35S2GFbPS4VyN3OGKZAZba5n2AquKRy9BF3BDVCYQhpdFIre
aGDUMnWkAl0MrhTNH61MVgouj9kif1CkE68pAPr25iA3W5VS4mtOCD9aKa9oGCwY1QgrsiOw
eaXJygFFcYNjZc+eO7shhSi5ElfOz+6Gjcd2nfMkRE4cKVaYuihv7Z9nB0hMNVIEgL7mERIK
RwrX+pfKUbWjnwrab1q7mCBOTiJ7L0daRXzzValhmCTyQoOymP/ZHdRQnvDd65XbwQBtlVdY
H/QmWBv/TM5ZOvJhEemlG3PAECEpZUbMYH4JE4HmS8EAAAAAAAA=
--------------ms020109010307000804040008--

From rjesup@wgate.com  Thu Jun 18 07:47:54 2009
Return-Path: <rjesup@wgate.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 38CE828C316 for <avt@core3.amsl.com>; Thu, 18 Jun 2009 07:47:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.434
X-Spam-Level: 
X-Spam-Status: No, score=-1.434 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, J_CHICKENPOX_62=0.6, RDNS_DYNAMIC=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 uUa9YpZILCT1 for <avt@core3.amsl.com>; Thu, 18 Jun 2009 07:47:53 -0700 (PDT)
Received: from exchange1.wgate.com (pr-66-150-46-254.wgate.com [66.150.46.254]) by core3.amsl.com (Postfix) with ESMTP id 4957828C0E1 for <avt@ietf.org>; Thu, 18 Jun 2009 07:47:53 -0700 (PDT)
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 18 Jun 2009 10:48:05 -0400
To: "Somogyi\, Gabor \(NSN - HU\/Budapest\)" <gabor.somogyi@nsn.com>
References: <45CC8FCA2C24554AA026E01B020D0CFFDF1419@FIESEXC006.nsn-intra.net>
From: Randell Jesup <rjesup@wgate.com>
Date: Thu, 18 Jun 2009 10:47:48 -0400
Message-ID: <ybuab4538ff.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 18 Jun 2009 14:48:05.0466 (UTC) FILETIME=[C9AA1BA0:01C9F023]
Cc: avt@ietf.org
Subject: Re: [AVT] Codec parameter mismatch in SDP offer and answer
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
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, 18 Jun 2009 14:47:54 -0000

"Somogyi, Gabor (NSN - HU/Budapest)" <gabor.somogyi@nsn.com> writes:
>What happens if codec parameters in the SDP answer differ from the ones
>in relevant offer? Maybe each codec specific SDP format description
>shell address that issue, as it may not be possible to give a generic
>answer.

It's codec/RFC-dependent, however you can generally say that unless
otherwise mentioned, each side defines what it's willing/expecting to
receive, and the other side needs to provide that (modulo anything
defined by the relevant RFC, such as the way RFC 3952 (iLBC) deals with
the 'mode' parameter in offer-answer.  Note that due to early-media
issues, the offerer generally needs to be ready and willing to receive
what it indicated, even if the answer might cause the expectations to
change.   For example, if you offer iLBC with mode=20, you must be ready
to receive either 20 or 30ms iLBC packets (until you get the answer).
You don't *have* to play 30ms packets, though it would be highly
advised, but you have to be ready to handle them and shouldn't do
anything stupid.

>RFC 3952 (iLBC) clearly defines that "mode" parameter is bi-directional,
>meaning that in both direction the same "mode" must be used. And if the
>parameter differs in the offer and the answer, then value "30" must be
>used. That sounds fine.
>
>In rfc3047-bis-09 proposal I saw no such definition. Is it possible for
>the answerer to reduce the offered bitrate? Must the same bitrate be
>used in both directions?

The spec should discuss offer-answer implications; if not specified then 
asymmetric bitrates, etc is probably implied as supported.

>I saw such interworking issues between live products of different
>vendors. G.729 (RFC 3555) defines optional parameter "annexb". If the
>offerer indicated the willingness of using Annex B, then could the
>answerer indicate that it is not willing to use discontinuous
>transmission (as it cannot generate comfort noise)? When the offerer
>sent its offer, it may had set up its DSPs, so might not be happy about
>even "downgrading" codec settings. Same applies to many other codecs, as
>well.

G.729 probably is ok with asymmetric use of annexb=no (I haven't
reviewed it).  It defines what each side is willing to receive.

-- 
Randell Jesup, Worldgate (developers of the Ojo videophone), ex-Amiga OS team
rjesup@wgate.com
"The fetters imposed on liberty at home have ever been forged out of the weapons
provided for defence against real, pretended, or imaginary dangers from abroad."
		- James Madison, 4th US president (1751-1836)

From versteb@cisco.com  Thu Jun 18 08:18:02 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 32A1B3A6814 for <avt@core3.amsl.com>; Thu, 18 Jun 2009 08:18:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.686
X-Spam-Level: 
X-Spam-Status: No, score=-6.686 tagged_above=-999 required=5 tests=[AWL=-0.087, 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 vH41FT-owPUL for <avt@core3.amsl.com>; Thu, 18 Jun 2009 08:18:00 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id DCD733A686A for <avt@ietf.org>; Thu, 18 Jun 2009 08:17:59 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,245,1243814400"; d="scan'208";a="47834196"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 18 Jun 2009 15:18:11 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n5IFIBRb003428;  Thu, 18 Jun 2009 11:18:11 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n5IFIBOe020961; Thu, 18 Jun 2009 15:18:11 GMT
Received: from xmb-rtp-21d.amer.cisco.com ([64.102.31.116]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 18 Jun 2009 11:18:11 -0400
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: Thu, 18 Jun 2009 11:18:10 -0400
Message-ID: <81B9B88E2F9D574AA5328A85547CDE910174ECBC@xmb-rtp-21d.amer.cisco.com>
In-Reply-To: <238382595265324EA50F6134BB42DCAF04047746@FRVELSMBS22.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] comments on section 10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAslt0gAAPNq9AABzJ84A==
References: <mailman.10085.1245185397.4936.avt@ietf.org><238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com><015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com><238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com><025301c9eff9$cbc5c1c0$63514540$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF04047746@FRVELSMBS22.ad2.ad.alcatel.com>
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>, "Roni Even" <Even.roni@huawei.com>, <avt@ietf.org>
X-OriginalArrivalTime: 18 Jun 2009 15:18:11.0753 (UTC) FILETIME=[FE4BA190:01C9F027]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=15573; t=1245338291; x=1246202291; c=relaxed/simple; s=rtpdkim1001; 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=20[AVT]=20comments=20on=20section=2010ofd raft-ietf-avt-rapid-acquisition-for-rtp-01 |Sender:=20 |To:=20=22VAN=20CAENEGEM=20Tom=22=20<Tom.Van_Caenegem@alcat el-lucent.be>,=0A=20=20=20=20=20=20=20=20=22Roni=20Even=22=2 0<Even.roni@huawei.com>,=20<avt@ietf.org>; bh=IC4hBhGeL/Oyf9/KzX9lynvAXs5Xx1ESmuEm6d46xTs=; b=ZecyztIiSKTq2zEHZtujH3DZSNqoHbCgjPzjv4p5E+5KLGu3KARi8cx5PX IMezkG0wFntepoGhEGYDIrk4adQlHMj0UUWXqHRUWJRymWBmFtk2UvZwfFVa esQ5G6xO4n;
Authentication-Results: rtp-dkim-1; header.From=versteb@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; ); 
Subject: Re: [AVT] comments on section 10ofdraft-ietf-avt-rapid-acquisition-for-rtp-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: Thu, 18 Jun 2009 15:18:02 -0000

Tom/Roni-

We need to clarify the text to make the port relationships more clear.
We are still getting reader confusion when considering the relationship
between the ports associated with the primary multicast flow, the ports
associated with the RTCP feedback on the initial flow, and the ports
associated with the acceleration flow.

These proposed words are an improvement. I will start with your new
words and make further clarifications for consideration. I hope to have
some words tonight.

bvs

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
VAN CAENEGEM Tom
Sent: Thursday, June 18, 2009 7:45 AM
To: Roni Even; avt@ietf.org
Subject: Re: [AVT] comments on section
10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01

Hi Roni,

I 100% agree with your remarks, and in fact I had proposed additional
text for step 2 and step 8 that clarified which message was sent in
which session and/or to/by whom, but now I notice these clarifying text
fragments seem to have been missed by the main editor in the last draft
release. Bill, can you add these phrases in a subsequent release?

Step 2:=20

Add text: "Both the unicast burst and the RAMS-I message are transmitted
by the burst/retransmission source logical entity that is part of the
RS."


Step 8:=20

Replace "Note that RR MUST send at least one RAMS-T message" by=20

"Note that RR MUST send at least one RAMS-T message, and the RAMS-T
message MUST be addressed to the Burst source logical entity that is
part of the RS." =20


On step 4, I took it kind of for granted that, as RAMS-R update messages
are the same as RAMS-R messages, the RAMS-R update message has to be
sent towards the FT... But you are right, that this should be explicitly
mentioned in the draft. One could even argue this message should be sent
to the Burst/Retransmission Source entity  as it services the purpose of
controling the RTP burst (similar as an RAMS-T message), but I would
suggest that this message is addressed to the FT, based on my previous
reasoning.=20

So for Step 4,  I'd propose to change the current sentence  "RR MAY send
a new RAMS-R message with a different value for one or more fields of an
earlier RAMS-R message."  to  "RR MAY send a new RAMS-R message to the
FT entity of the RS, with a different value for one or more fields of an
earlier RAMS-R  message."


Tom

  =20

-----Original Message-----
From: Roni Even [mailto:Even.roni@huawei.com]
Sent: donderdag 18 juni 2009 11:47
To: VAN CAENEGEM Tom; avt@ietf.org
Subject: RE: [AVT] comments on section 10
ofdraft-ietf-avt-rapid-acquisition-for-rtp-01

Hi Tom,
My comment about the text was more about the steps described later in
section 6.2

In step 2 the RS will send the RAMS-I from the RTCP port for the
burst/retransmission stream. This will help the RR to learn his address

In step 4 - update RAM-R, will it be sent to the FT target or to the
burst/retransmission.

In step 8 - specify where to send the RAMS-T not to the RS but to the
burst/retransmission address.=20




As for the RTP/RTCP port multiplexing, I do not think that this is a
separate draft. We need to discuss the solution and decide where to it
should go. If the declarative SDP will include RTP/RTCP mux the RAM-R
should acknowledge that it is supported by the RR.

The need for a separate draft discussion is if the RR wants to offer
different ports for receiving the RTP and RTCP, and this needs to be
discussed. The major question is if we need a general mechanism which
requires a new RTCP message or is it just for this case and we can add
the information to the RAMS messages..

Roni

> -----Original Message-----
> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> Sent: Wednesday, June 17, 2009 3:23 PM
> To: Roni Even; avt@ietf.org
> Subject: RE: [AVT] comments on section 10 ofdraft-ietf-avt-rapid-
> acquisition-for-rtp-01
>=20
>=20
>  Hi Roni,
>=20
> Perhaps the start of section 6.2 can be rewritten as follows:
>=20
>=20
> <START>
>=20
> 6.2.  Message Flows
>=20
>    Figure 2 shows the main entities involved in rapid acquisition:
>=20
>    o  Multicast Source
>=20
>    o  Feedback Target (FT)
>=20
>    o  Burst/ Retransmission Source
>=20
>    o  RTP Receiver (RR)
>=20
> (fig 2)
>=20
>=20
> The feedback target (FT) is the entity as defined in [rtcpssm draft],=20
> to which the RR sends its RTCP FB messages, indicating packet loss in=20
> the ssm primary stream by means of a NACK or indicating the RR's=20
> desire to have rapid acquisition of the ssm primary stream (by means=20
> of an RTCP FB message as defined in this document). While the=20
> burst/retransmission source is responsible for responding on these=20
> messages and, in the case of rapid acquisition, further RTCP=20
> interaction with the RR during this acquisition process, it is assumed

> in the remainder of the document that these two logical entities (FT=20
> and burst/retransmission source) are combined in a single physical=20
> entity and share state. In the remainder of the text, the term=20
> retransmission server is used whenever appropriate, to refer to the=20
> combined functionality of the FT and retransmission/burst source.
> However, it must be noted that only the FT is involved in the primary=20
> ssm RTP session, whereas the burst/retransmission source transmits=20
> unicast RTP burst and RTP retransmissions packets (both formatted  as=20
> RTP retransmission packets
> [RFC4585]) in a single separate unicast RTP retransmission session to=20
> each RR.
>=20
> Note also that the same method (with the identical message flows)=20
> would also apply in a scenario where rapid acquisition is performed by

> a feedback target co-located with the media source.
>=20
> (...)
>=20
> <END>
>=20
> Tom: As we mandate the retransmission source and burst source to be in

> the same session, I think it is no longer required to split-up among=20
> these two logical entities. I invite other people, including the=20
> co-authors to comment on this new text proposal.
>=20
> With respect to your comments on the RTP/RTCP port muxing support=20
> indication by the RR inside the RAMS-R message. That would be needed,=20
> but is not sufficient as, if only declarative SDP is used, and we want

> to have the possibility that the RTP/RTCP packets in the=20
> retransmission session can be received by the RR on the same port the=20
> RR issues the RTCP RAMS-R, we need also a way by which the RR can=20
> signal this too. We provided a possible solution in the draft, but I=20
> understood that you think such a solution should be proposed in a
separate draft proposal?
> But I guess that would also apply then to the signaling of support for

> RTP/RTCP port muxing by the RR?
>=20
> Tom
>=20
> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: woensdag 17 juni 2009 13:24
> To: VAN CAENEGEM Tom; avt@ietf.org
> Subject: RE: [AVT] comments on section 10
> ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
> Tom,
> I understand the RAMS-R and RAMS-T, the text is not clear enough in=20
> section
> 6.2
>=20
> It still leaves open the issue of the addresses for the RR in the case

> of declarative SDP when there is no answer SDP from the RR.
>=20
> About RTP/RTCP multiplexing, the declarative SDP can show that the RS=20
> supports it and I still think that some information about the=20
> addressing (like support for RTP/RTCP mux) should be supplied in the=20
> RAMS-R for the declarative case.
>=20
> Roni
>=20
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf=20
> > Of VAN CAENEGEM Tom
> > Sent: Wednesday, June 17, 2009 11:17 AM
> > To: avt@ietf.org
> > Subject: Re: [AVT] comments on section 10 of draft-ietf-avt-rapid-
> > acquisition-for-rtp-01
> >
> > Hi Roni,
> >
> > I think your understanding was indeed different from the general=20
> >assumptions in this draft. Previously we agreed to only consider the=20
> >case where there is only one physical entity involved (called the=20
> >Retransmission Server in the draft), which allows us to NOT consider=20
> >and  discuss cases where for instance the feedback target (which is=20
> >defined  in the rtcpssm draft/RFC) is not in the same box as the=20
> >retransmission  source or burst source, the entities sourcing=20
> >retransmision/burst  packets. In that case we then would also need to

> >describe how these  separate entities communicate.
> > The fact that these different entities are now in the same box does=20
> >not  necessarily mean that all interactions and data exchange with=20
> >the RRs  is  part of the same RTP session, which is in this case the=20
> >SSM RTP  session.
> > As Ali explained, the NACK and RAMS-R RTCP FB messages are directed
> to
>=20
> >the FB target, where we do not  defer from the rtcpssm draft. The RTP

> >retransmission/burst packets that are sent as a response to the NACK=20
> >and  the RAMS-R can be either session multiplexed with respect to the

> >original SSM RTP session or SSRC muxed (same session), following RFC=20
> >4588.
> >As the retransmission packets in this case are addressing the RR  in=20
> >unicast, we obviously have a dedicated RTP session for the=20
> >retransmission/burst packets. We had some internal discussion on=20
> >whether  considering the use case of having a separate session=20
> >between RS and RR  for RTP retransmission packets triggered by an=20
> >RTCP FB NACK and a  separate session for RTP burst packets triggered=20
> >by an RTCP RAMS-R made  sense, but we ended up agreeing that allowing

> >a single session was the  easiest way out, without imposing serious=20
> >limitations to the general  architecture.
> >
> > This means that the ports used by the (single) RTP=20
> > retransmission/burst session are in principle decoupled from the=20
> > primary SSM session. Hence if an RR wants to receive the=20
> > burst/retransmission packets and associated RTCP messages on the=20
> > same port the RR sent out the RTCP RAMS-R/ NACK FB messages, this=20
> > should either be signaled by the RR, OR such port usage scheme is=20
> > considered the "default" case -which also means the RR supports=20
> > RTP/RTCP port muxing for the retransmission/burst session-, and then

> > the RR needs
> to
>=20
> > signal the ports for receiving the RTP and RTCP packets in the=20
> > retransmission session when it requires dedicated ports.
> >
> > The RAMS-I (RS-> RR) and RAMS-T (RR-> RS) messages are only relevant

> > to a specific RR requesting the RTP burst stream and the RS, and
> carry
>=20
> > information/signaling related to the retransmission/burst session=20
> > and have nothing to do with the SSM session. Hence the FB target as=20
> > logical entity is not involved here.
> >
> > I hope this clarifies rather than it contributes to your confusion.
> > But we may need to rephrase the part you quoted, as your=20
> > interpretation was different from its intended meaning. We also=20
> > tried to be more explicit in which session which RAMS or other RTCP
(e.g.
> > Bye) messages needed to be exchanged compared to a previous version
> of
>=20
> > the draft, but we are open of course to any other suggestions from=20
> > your side if this is not clear enough in your opinion.
> >
> > Tom
> >
> >
> >
> >
> >
> >
> > " A Retransmission Source may equally act as a Burst Source.  The
> >    Retransmission Source may also incorporate the Feedback Target
> >    ([I-D.ietf-avt-rtcpssm] permits the feedback target to be a
> >    retransmission server, since it is a logical function to which
RRs
> >    send their unicast feedback), and we will use the term=20
> > Retransmission
> >    Server (RS) in the remainder of the document to refer to a single
> >    physical entity comprising these three entities that share state.
> >    Note that the same method (with the identical message flows)
would
> >    also apply in a scenario where rapid acquisition is performed by
a
> >    feedback target co-located with the media source."
> >
> > I assumed that we are only dealing with the case that the RS is a=20
> > single entity and not three different entities with different=20
> > addresses
> >
> > I also thought that this was agreed in previous discussions
> >
> > If my understanding is not correct I will review the draft since the

> > current text is not explicit enough to specify which part is doing=20
> > each message. I saw that RAMS-R is going to feedback target but
> > RAMS-
> T
>=20
> > is going to RS which is not specifying a specific address according
> to
>=20
> > you.
> >
> > Roni
> >
> > -----Original Message-----
> > From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> > Sent: Tuesday, June 16, 2009 10:00 PM
> > To: Roni Even; avt@ietf.org
> > Subject: RE: [AVT] comments on section 10
> > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > Remember that the RAMS-R (RR->RS) message is NOT on the
> retransmission
> > (unicast) session, it's on the primary session since it is sent to
> the
>=20
> > feedback target of the primary SSM session. Thus, the source port RR

> > uses to send RAMS-R "cannot" be assumed to be the destination port=20
> > it wishes to receive the unicast burst on.
> >
> > If you agree with this statement, it is clear why we need port=20
> > signaling.
> > Muxing will not help much here. It will just reduce the number of=20
> > signaled ports from 2 to 1.
> >
> > -acbegen
> >
> >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf

> > > Of Roni
> > Even
> > > Sent: Tuesday, June 16, 2009 10:08 AM
> > > To: avt@ietf.org
> > > Subject: [AVT] comments on section 10
> > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > >
> > > Hi,
> > >
> > > I looked at section 10 and have some comments
> > >
> > >
> > >
> > > 1.       If RTP/RTCP multiplexing is used, there is no need for
any
> > specific operation
> > > from the RR side. The RR sends the RAMS-R message to the RS from
> the
>=20
> > > port
> > it wants to
> > > receive the RAMS-I and RTP payload. The RS just sends the=20
> > > information to
> > the port from
> > > which it received the RAMS-R and not to the one in the SDP
> > >
> > > 2.       In the case where there is no RTP/RTCP multiplexing, the
> > RAMS-R
> > RTCP message will
> > > go to the RS and the RAMS-I will go to the port on the RR from
> where
>=20
> > > the
> > RAMS-R was
> > > received. For the RTP, the RR does not know if it has a NAT on the
> > way
> >
> > > to
> > the RS and
> > > should try to get a routable address (using STUN for example) and
> > providing the port to
> > > the RS ( we still need to agree on how to do it)
> > >
> > > 3.       If the above two points are correct than the RR receive
> port
> > in
> > the SDP is not
> > > really useful
> > >
> > >
> > >
> > > Roni Even
> >
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt

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

From jonathan@vidyo.com  Thu Jun 18 08:31:55 2009
Return-Path: <jonathan@vidyo.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 7815D28C3DB for <avt@core3.amsl.com>; Thu, 18 Jun 2009 08:31:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, 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 5rver-IWYaVR for <avt@core3.amsl.com>; Thu, 18 Jun 2009 08:31:54 -0700 (PDT)
Received: from mx1.myoutlookonline.com (mx1.myoutlookonline.com [64.95.72.238]) by core3.amsl.com (Postfix) with ESMTP id 9821A28C3D4 for <avt@ietf.org>; Thu, 18 Jun 2009 08:31:54 -0700 (PDT)
Received: from be150.mail.lan ([10.110.20.150]) by mx1.myoutlookonline.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 18 Jun 2009 11:32:06 -0400
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: Thu, 18 Jun 2009 11:32:04 -0400
Message-ID: <6B55710E7F51AD4B93F336052113B85FA4B223@be150.mail.lan>
In-Reply-To: <4A3A4E40.2060801@telecomitalia.it>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Sound level indicators
Thread-Index: AcnwIJCRh1qG860hTsekZytIgZYa8wABRIaA
References: <6B55710E7F51AD4B93F336052113B85FA4B16F@be150.mail.lan> <4A3A4E40.2060801@telecomitalia.it>
From: "Jonathan Lennox" <jonathan@vidyo.com>
To: "Enrico Marocco" <enrico.marocco@telecomitalia.it>
X-OriginalArrivalTime: 18 Jun 2009 15:32:06.0636 (UTC) FILETIME=[EFECAAC0:01C9F029]
Cc: avt@ietf.org
Subject: Re: [AVT] Sound level indicators
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, 18 Jun 2009 15:31:55 -0000

Enrico Marocco [mailto:enrico.marocco@telecomitalia.it] writes:=20


> I may have not given enough thought to all the side issues, but it=20
> seems to me that the two drafts deal with the very same kind of
> information (and thus its encoding should be specified in only one
> place).

I absolutely agree that these drafts should be aligned as closely as
possible.

I also agree that standardizing encoding is a good idea -- this is why
my draft copies its definition and encoding of audio level from the
Comfort Noise payload.=20

I'd be open to combining the two drafts, if the WG agrees that both
issues are worth working on, and feels that having a single document
addressing multiple issues is better than having two documents that
inevitably repeat or cross-reference information.

(Technically, I believe that having separate extension headers for "ssrc
level" and "csrc levels" is a good idea, but that's orthogonal to the
issue of document structure.)

> To me, the main issue with passing the sound level of a non-mixed
> stream to do with the fact that the RTP header is not going to be
> encrypted when using SRTP: an in-line attacker could mute a
> conference participant just mangling such value or, if the header
> is integrity protected, dropping those packets where voice activity
> is reported.

I'm not so worried about the first point -- SRTP strongly disrecommends
using encryption without authentication (which covers headers), and any
environment in which you're not willing to pay for the bandwidth
overhead of SRTP authentication is probably one in which you're not
willing to have extension headers either.

The second point is more of an issue, but the issue I'm most concerned
about is the fact (with either draft) that a passive attacker can see a
real-time waveform (at ptime resolution) of a participant's, or each
participant's, audio.

I've been pondering an SRTP extension to encrypt selected extension
headers; I think this might end up being necessary for both of these
drafts.

--=20
Jonathan Lennox
Vidyo, Inc
jonathan@vidyo.com

From abegen@cisco.com  Thu Jun 18 08:34:20 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 89DF43A6814 for <avt@core3.amsl.com>; Thu, 18 Jun 2009 08:34:20 -0700 (PDT)
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 dzfy+mBb-dDP for <avt@core3.amsl.com>; Thu, 18 Jun 2009 08:34:19 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 69A9E3A6832 for <avt@ietf.org>; Thu, 18 Jun 2009 08:34:19 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,245,1243814400"; d="scan'208";a="326648391"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 18 Jun 2009 15:34:31 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n5IFYVGk014533;  Thu, 18 Jun 2009 08:34:31 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n5IFYVDp019533; Thu, 18 Jun 2009 15:34:31 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 18 Jun 2009 08:34:31 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 18 Jun 2009 08:33:32 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D54098D8C33@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <238382595265324EA50F6134BB42DCAF0408CAE6@FRVELSMBS22.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Some comments on " Multicast Acquisition Report Block Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-01)
Thread-Index: AcnwH3wb2QndKgItQv2Gbyp/65/cCAACF+jg
References: <238382595265324EA50F6134BB42DCAF0408CAE6@FRVELSMBS22.ad2.ad.alcatel.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>, <avt@ietf.org>
X-OriginalArrivalTime: 18 Jun 2009 15:34:31.0748 (UTC) FILETIME=[466B0040:01C9F02A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4572; t=1245339271; x=1246203271; 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]=20Some=20comments=20on=20=22=20Mu lticast=20Acquisition=20Report=20Block=20Typefor=20RTCP=20XR =22=20(draft-begen-avt-rapid-sync-rtcp-xr-01) |Sender:=20; bh=GQBx9qCsQQZ4Ls83gqIkdmUZkr9Bs0SXzH9jnGY8Lg8=; b=il3feckKnT1qwuxC8VYDZmoOlKf4HPigeko4b/DEn9MbY6zFZ8hshgWk2c u+UbHH61Ij0sufmqasJSelipULBcz4eMSPQGl56LV7KUQBw8HGgqc4ChaLX1 L2RZibVy2N;
Authentication-Results: sj-dkim-4; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Subject: Re: [AVT] Some comments on " Multicast Acquisition Report Block Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-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: Thu, 18 Jun 2009 15:34:20 -0000

Hi Tom,

Thanks for reading the draft.

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of =
VAN CAENEGEM Tom
> Sent: Thursday, June 18, 2009 7:17 AM
> To: avt@ietf.org
> Subject: [AVT] Some comments on " Multicast Acquisition Report Block =
Typefor RTCP XR"
> (draft-begen-avt-rapid-sync-rtcp-xr-01)
>=20
> Hi Ali,
>=20
> I have a few comments/questions related to the draft:
>=20
> Comment 1:  The abstract now has a sentence: "For quality reporting, =
monitoring and
> diagnostics purposes, it is important to collect detailed information =
from the RTP
> receivers about their acquisition experiences."  Doesn't it go beyond =
"RTP (receivers)"
> and "acquisition" as you also define e.g. a TLV related to =
presentation time delay
> (sometimes the MC RTP delivered content may not even be displayed) and =
application delay.
> I have no problem with the definition of such fields, but IMO it makes =
sense to make this
> clear in the abstract.

I am not sure what else I can use instead of "RTP receivers" as I don't =
wanna specifically say decoders, set-tops, etc. Instead of "acquisition =
experiences", maybe we can call it "acquisition and presentation =
experiences"?

Would that help?
=20
> Comment 2: Base Report
>=20
> The only informational field here is "response". It is still not =
defined, but you refer to
> the response code in RAMS draft (e.g. "success", etc).

I believe using the same codes will make it more useful.

=20
> I guess it is not possible to signal to an RR which additional info to =
send, i.e which TLV
> fields to use=85From that point of view, would it not make sense to =
have some basic
> information -now defined in some TLV fields in the base report- that =
is always present, to

By always present, you mean "mandatory"? If yes, we indeed need to =
decide which ones.

> enhance interoperability. I know we need to find the right balance =
between useful
> information reporting ,  bandwidth efficiency, and receiver reporting =
capabilities.
>=20
> Candidate fields that could be inside this fixed base report are:
> -flag/field indicating whether the report refers to a normal =
acquisition (based on SFGMP)
> or rapid MC RTP acquisition (or rather  the intention by the RR to =
perform  a rapid
> acquisition) for instance by means of RAMS

One reason behind this base report vs extensions separation was to be =
able to handle other rapid multicast acquisition methods. So, IMO, if we =
will have to make something mandatory, it should not relate to a =
specific method. It is true that I am heavily considering RAMS in =
designing this report, but it just works for other methods, if they =
become interested in supporting this report.

Will this flag/field be able to specify which method was used? Or will =
it simply specify whether it was a rapid or normal acquisition?

> -a response code which you have indeed defined and its interpretation =
should be dependent
> on the previously mentioned flag/field

So, the flag/field above will indeed specify which method was use to =
make RR rapidly acquire the content. Yes/no?

=20
> -initial launched request (either 1st RAMS-R for rapid acquisition, =
either 1st IGMP-join
> in case of normal acquisition) to 1st received RTP packet (always a =
multicast packet for
> normal acquisition and "normally" a burst packet when a rapid =
acquisition process was
> involved) delta time
>=20
> -application request to initial launched request (either 1st RAMS-R =
for rapid acquisition,
> either 1st IGMP-join in case of normal acquisition) delta time
>=20
> For these last two fields, a value must be specified that would =
indicate that the field is
> not filled out (because the receiver client implementation may not =
support it).

Oh, then these fields are not mandatory since the client has the option =
to leave them blank. Then, I would recommend leaving the current report =
as it is, but we can use a stronger language (like "SHOULD/RECOMMENDED") =
for some of the fields (like the ones you have above) to promote =
interoperability.=20

Would you be OK with that?

=20
> There could still be other fields that apply to both acquisition =
processes and fit in the
> base report, but they should be application independent (e.g. delta to =
presentation time
> is clearly app dependent)

Agree, application dependent fields are optional and should stay so.

T,
-acbegen

>=20
> Regards
> Tom


From emil@sip-communicator.org  Thu Jun 18 10:07:36 2009
Return-Path: <emil@sip-communicator.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 C667928C33B for <avt@core3.amsl.com>; Thu, 18 Jun 2009 10:07:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.343
X-Spam-Level: 
X-Spam-Status: No, score=-1.343 tagged_above=-999 required=5 tests=[AWL=0.906,  BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VfJD+PJNk1XO for <avt@core3.amsl.com>; Thu, 18 Jun 2009 10:07:36 -0700 (PDT)
Received: from mail-fx0-f212.google.com (mail-fx0-f212.google.com [209.85.220.212]) by core3.amsl.com (Postfix) with ESMTP id C892D3A69D9 for <avt@ietf.org>; Thu, 18 Jun 2009 10:07:35 -0700 (PDT)
Received: by fxm8 with SMTP id 8so1220824fxm.37 for <avt@ietf.org>; Thu, 18 Jun 2009 10:07:43 -0700 (PDT)
Received: by 10.103.173.15 with SMTP id a15mr1184294mup.59.1245344863240; Thu, 18 Jun 2009 10:07:43 -0700 (PDT)
Received: from porcinet.u-strasbg.fr (porcinet.u-strasbg.fr [130.79.91.167]) by mx.google.com with ESMTPS id s10sm557827muh.57.2009.06.18.10.07.41 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 18 Jun 2009 10:07:42 -0700 (PDT)
Message-ID: <4A3A745C.6060402@sip-communicator.org>
Date: Thu, 18 Jun 2009 19:07:40 +0200
From: Emil Ivov <emcho@sip-communicator.org>
Organization: SIP Communicator
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: Jonathan Lennox <jonathan@vidyo.com>
References: <6B55710E7F51AD4B93F336052113B85FA4B16F@be150.mail.lan>	<4A3A4E40.2060801@telecomitalia.it> <6B55710E7F51AD4B93F336052113B85FA4B223@be150.mail.lan>
In-Reply-To: <6B55710E7F51AD4B93F336052113B85FA4B223@be150.mail.lan>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: avt@ietf.org
Subject: Re: [AVT] Sound level indicators
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, 18 Jun 2009 17:07:36 -0000

Jonathan Lennox wrote:
> I also agree that standardizing encoding is a good idea -- this is why
> my draft copies its definition and encoding of audio level from the
> Comfort Noise payload. 

Sounds reasonable. We were thinking of using relative non-normalized
sound levels to avoid conversion but using the comfort noise level
evaluation mechanism is also an option (especially in the use case you
describe).

> I'd be open to combining the two drafts, if the WG agrees that both
> issues are worth working on, and feels that having a single document
> addressing multiple issues is better than having two documents that
> inevitably repeat or cross-reference information.

Agreed.

> (Technically, I believe that having separate extension headers for "ssrc
> level" and "csrc levels" is a good idea, 

I guess this depends on what you mean by "separate extension headers".

If it's only a matter of defining an extra URN then that's probably
alright. One could still wonder why we needed to explicitly
differentiate them though since they would hardly ever travel together.

I definitely think, however, that header syntax should be identical in
both cases.

> but that's orthogonal to the issue of document structure.)

Agreed again.

Cheers
Emil

From zeevvax@microsoft.com  Thu Jun 18 14:26:48 2009
Return-Path: <zeevvax@microsoft.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 952AA3A67E1 for <avt@core3.amsl.com>; Thu, 18 Jun 2009 14:26:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 qzzUA9SS7W2g for <avt@core3.amsl.com>; Thu, 18 Jun 2009 14:26:46 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 748B63A67E2 for <avt@ietf.org>; Thu, 18 Jun 2009 14:26:46 -0700 (PDT)
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.99.4; Thu, 18 Jun 2009 14:26:58 -0700
Received: from tk5ex14mbxc105.redmond.corp.microsoft.com ([169.254.2.249]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi; Thu, 18 Jun 2009 14:26:58 -0700
From: Zeev Vax <zeevvax@microsoft.com>
To: Roni Even <Even.roni@huawei.com>, "'Bill Ver Steeg (versteb)'" <versteb@cisco.com>, "'Ali C. Begen (abegen)'" <abegen@cisco.com>, 'VAN CAENEGEM Tom' <Tom.Van_Caenegem@alcatel-lucent.be>, "avt@ietf.org" <avt@ietf.org>
Thread-Topic: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVA=
Date: Thu, 18 Jun 2009 21:26:57 +0000
Message-ID: <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com>
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com>
In-Reply-To: <025401c9effa$34040170$9c0c0450$%roni@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-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: Thu, 18 Jun 2009 21:26:48 -0000

Roni,

As I said I support mandating the multiplexing, but not the multiple ports.=
 If there are no other opinions, we can add that to draft.

Zeev

-----Original Message-----
From: Roni Even [mailto:Even.roni@huawei.com]
Sent: Thursday, June 18, 2009 2:50 AM
To: Zeev Vax; 'Bill Ver Steeg (versteb)'; 'Ali C. Begen (abegen)'; 'VAN CAE=
NEGEM Tom'; avt@ietf.org
Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisition-=
for-rtp-01

Zeev,
This is a question I had in the past. I think that it merits a separate
thread in order to get a consensus on the issue. Mandating RTP/RTCP
multiplexing for the unicast burst make it simpler and faster to start.

Note the two ports may still be used for the retransmission case.

Roni



> -----Original Message-----
> From: Zeev Vax [mailto:zeevvax@microsoft.com]
> Sent: Wednesday, June 17, 2009 7:45 PM
> To: Bill Ver Steeg (versteb); Ali C. Begen (abegen); VAN CAENEGEM Tom;
> Roni Even; avt@ietf.org
> Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-
> acquisition-for-rtp-01
>
> The text proposal looks fine to me.
> I don't think we should mandate support both, this would cause extra
> work in implementation of a solution, and I can't see any benefit.
> Giving that this is UDP traffic port muxing is a subset of separate
> ports, so we can mandate port muxing, and make optional the separate
> ports.
>
> Zeev
>
>
> -----Original Message-----
> From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> Sent: Wednesday, June 17, 2009 8:40 AM
> To: Ali C. Begen (abegen); VAN CAENEGEM Tom; Roni Even; avt@ietf.org;
> Zeev Vax
> Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-
> acquisition-for-rtp-01
>
> Tom-
>
> These words looks good to me as well, with the following clarification.
>
> We do need to consider how we handle RTP/RTCP port muxing throughout
> the
> document, and make the wording consistent wherever we reference the
> ports in use. I am in favor of allowing (but not mandating) the RR to
> signal RTP/RTCP port muxing. This would require the RS to support both
> methods. This is just my opinion, and we need to come to consensus on
> this matter.
>
>
> Bill VerSteeg
>
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Ali C. Begen (abegen)
> Sent: Wednesday, June 17, 2009 10:15 AM
> To: VAN CAENEGEM Tom; Roni Even; avt@ietf.org
> Subject: Re: [AVT] comments on
> section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>
> The proposed text looks good to me. We should probably put the burst
> and
> retransmission sources in the same block in Figure 2 as well.
>
> -acbegen
>
>
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> > VAN CAENEGEM Tom
> > Sent: Wednesday, June 17, 2009 5:23 AM
> > To: Roni Even; avt@ietf.org
> > Subject: Re: [AVT] comments on section
> > 10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> >
> >  Hi Roni,
> >
> > Perhaps the start of section 6.2 can be rewritten as follows:
> >
> >
> > <START>
> >
> > 6.2.  Message Flows
> >
> >    Figure 2 shows the main entities involved in rapid acquisition:
> >
> >    o  Multicast Source
> >
> >    o  Feedback Target (FT)
> >
> >    o  Burst/ Retransmission Source
> >
> >    o  RTP Receiver (RR)
> >
> > (fig 2)
> >
> >
> > The feedback target (FT) is the entity as defined in [rtcpssm draft],
> > to which the RR sends its RTCP FB messages, indicating packet loss in
> > the ssm primary stream by means of a NACK or indicating the RR's
> > desire to have rapid acquisition of the ssm primary stream (by means
> > of an RTCP FB message as defined in this document). While the
> > burst/retransmission source is responsible for responding on these
> > messages and, in the case of rapid acquisition, further RTCP
> > interaction with the RR during this acquisition process, it is
> assumed
>
> > in the remainder of the document that these two logical entities (FT
> > and burst/retransmission source) are combined in a single physical
> > entity and share state. In the remainder of the text, the term
> > retransmission server is used whenever appropriate, to refer to the
> > combined functionality of the FT and retransmission/burst source.
> > However, it must be noted that only the FT is involved in the primary
> > ssm RTP session, whereas the burst/retransmission source transmits
> > unicast RTP burst and RTP retransmissions packets (both formatted  as
> > RTP retransmission packets
> > [RFC4585]) in a single separate unicast RTP retransmission session to
> > each RR.
> >
> > Note also that the same method (with the identical message flows)
> > would also apply in a scenario where rapid acquisition is performed
> by
>
> > a feedback target co-located with the media source.
> >
> > (...)
> >
> > <END>
> >
> > Tom: As we mandate the retransmission source and burst source to be
> in
>
> > the same session, I think it is no longer required to split-up among
> > these two logical entities. I invite other people, including the
> > co-authors to comment on this new text proposal.
> >
> > With respect to your comments on the RTP/RTCP port muxing support
> > indication by the RR inside the RAMS-R message. That would be needed,
> > but is not sufficient as, if only declarative SDP is used, and we
> want
>
> > to have the possibility that the RTP/RTCP packets in the
> > retransmission session can be received by the RR on the same port the
> > RR issues the RTCP RAMS-R, we need also a way by which the RR can
> > signal this too. We provided a possible solution in the draft, but I
> > understood that you think such a solution should be proposed in a
> separate draft proposal?
> > But I guess that would also apply then to the signaling of support
> for
>
> > RTP/RTCP port muxing by the RR?
> >
> > Tom
> >
> > -----Original Message-----
> > From: Roni Even [mailto:Even.roni@huawei.com]
> > Sent: woensdag 17 juni 2009 13:24
> > To: VAN CAENEGEM Tom; avt@ietf.org
> > Subject: RE: [AVT] comments on section 10
> > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > Tom,
> > I understand the RAMS-R and RAMS-T, the text is not clear enough in
> > section
> > 6.2
> >
> > It still leaves open the issue of the addresses for the RR in the
> case
>
> > of declarative SDP when there is no answer SDP from the RR.
> >
> > About RTP/RTCP multiplexing, the declarative SDP can show that the RS
> > supports it and I still think that some information about the
> > addressing (like support for RTP/RTCP mux) should be supplied in the
> > RAMS-R for the declarative case.
> >
> > Roni
> >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
> > > Of VAN CAENEGEM Tom
> > > Sent: Wednesday, June 17, 2009 11:17 AM
> > > To: avt@ietf.org
> > > Subject: Re: [AVT] comments on section 10 of draft-ietf-avt-rapid-
> > > acquisition-for-rtp-01
> > >
> > > Hi Roni,
> > >
> > > I think your understanding was indeed different from the general
> > >assumptions in this draft. Previously we agreed to only consider the
> > >case where there is only one physical entity involved (called the
> > >Retransmission Server in the draft), which allows us to NOT consider
> > >and  discuss cases where for instance the feedback target (which is
> > >defined  in the rtcpssm draft/RFC) is not in the same box as the
> > >retransmission  source or burst source, the entities sourcing
> > >retransmision/burst  packets. In that case we then would also need
> to
>
> > >describe how these  separate entities communicate.
> > > The fact that these different entities are now in the same box does
> > >not  necessarily mean that all interactions and data exchange with
> > >the RRs  is  part of the same RTP session, which is in this case the
> > >SSM RTP  session.
> > > As Ali explained, the NACK and RAMS-R RTCP FB messages are directed
> > >to
> >
> > >the FB target, where we do not  defer from the rtcpssm draft. The
> RTP
>
> > >retransmission/burst packets that are sent as a response to the NACK
> > >and  the RAMS-R can be either session multiplexed with respect to
> the
>
> > >original SSM RTP session or SSRC muxed (same session), following RFC
> > >4588.
> > >As the retransmission packets in this case are addressing the RR  in
> > >unicast, we obviously have a dedicated RTP session for the
> > >retransmission/burst packets. We had some internal discussion on
> > >whether  considering the use case of having a separate session
> > >between RS and RR  for RTP retransmission packets triggered by an
> > >RTCP FB NACK and a  separate session for RTP burst packets triggered
> > >by an RTCP RAMS-R made  sense, but we ended up agreeing that
> allowing
>
> > >a single session was the  easiest way out, without imposing serious
> > >limitations to the general  architecture.
> > >
> > > This means that the ports used by the (single) RTP
> > > retransmission/burst session are in principle decoupled from the
> > > primary SSM session. Hence if an RR wants to receive the
> > > burst/retransmission packets and associated RTCP messages on the
> > > same port the RR sent out the RTCP RAMS-R/ NACK FB messages, this
> > > should either be signaled by the RR, OR such port usage scheme is
> > > considered the "default" case -which also means the RR supports
> > > RTP/RTCP port muxing for the retransmission/burst session-, and
> then
>
> > > the RR needs to
> >
> > > signal the ports for receiving the RTP and RTCP packets in the
> > > retransmission session when it requires dedicated ports.
> > >
> > > The RAMS-I (RS-> RR) and RAMS-T (RR-> RS) messages are only
> relevant
>
> > > to a specific RR requesting the RTP burst stream and the RS, and
> > > carry
> >
> > > information/signaling related to the retransmission/burst session
> > > and have nothing to do with the SSM session. Hence the FB target as
> > > logical entity is not involved here.
> > >
> > > I hope this clarifies rather than it contributes to your confusion.
> > > But we may need to rephrase the part you quoted, as your
> > > interpretation was different from its intended meaning. We also
> > > tried to be more explicit in which session which RAMS or other RTCP
> (e.g.
> > > Bye) messages needed to be exchanged compared to a previous version
> > > of
> >
> > > the draft, but we are open of course to any other suggestions from
> > > your side if this is not clear enough in your opinion.
> > >
> > > Tom
> > >
> > >
> > >
> > >
> > >
> > >
> > > " A Retransmission Source may equally act as a Burst Source.  The
> > >    Retransmission Source may also incorporate the Feedback Target
> > >    ([I-D.ietf-avt-rtcpssm] permits the feedback target to be a
> > >    retransmission server, since it is a logical function to which
> RRs
> > >    send their unicast feedback), and we will use the term
> > > Retransmission
> > >    Server (RS) in the remainder of the document to refer to a
> single
> > >    physical entity comprising these three entities that share
> state.
> > >    Note that the same method (with the identical message flows)
> would
> > >    also apply in a scenario where rapid acquisition is performed by
> a
> > >    feedback target co-located with the media source."
> > >
> > > I assumed that we are only dealing with the case that the RS is a
> > > single entity and not three different entities with different
> > > addresses
> > >
> > > I also thought that this was agreed in previous discussions
> > >
> > > If my understanding is not correct I will review the draft since
> the
>
> > > current text is not explicit enough to specify which part is doing
> > > each message. I saw that RAMS-R is going to feedback target but
> > > RAMS-T
> >
> > > is going to RS which is not specifying a specific address according
> > > to
> >
> > > you.
> > >
> > > Roni
> > >
> > > -----Original Message-----
> > > From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> > > Sent: Tuesday, June 16, 2009 10:00 PM
> > > To: Roni Even; avt@ietf.org
> > > Subject: RE: [AVT] comments on section 10
> > > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > >
> > > Remember that the RAMS-R (RR->RS) message is NOT on the
> > > retransmission
> > > (unicast) session, it's on the primary session since it is sent to
> > > the
> >
> > > feedback target of the primary SSM session. Thus, the source port
> RR
>
> > > uses to send RAMS-R "cannot" be assumed to be the destination port
> > > it wishes to receive the unicast burst on.
> > >
> > > If you agree with this statement, it is clear why we need port
> > > signaling.
> > > Muxing will not help much here. It will just reduce the number of
> > > signaled ports from 2 to 1.
> > >
> > > -acbegen
> > >
> > >
> > > > -----Original Message-----
> > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> Behalf
>
> > > > Of Roni
> > > Even
> > > > Sent: Tuesday, June 16, 2009 10:08 AM
> > > > To: avt@ietf.org
> > > > Subject: [AVT] comments on section 10
> > > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > > >
> > > > Hi,
> > > >
> > > > I looked at section 10 and have some comments
> > > >
> > > >
> > > >
> > > > 1.       If RTP/RTCP multiplexing is used, there is no need for
> any
> > > specific operation
> > > > from the RR side. The RR sends the RAMS-R message to the RS from
> > > > the
> >
> > > > port
> > > it wants to
> > > > receive the RAMS-I and RTP payload. The RS just sends the
> > > > information to
> > > the port from
> > > > which it received the RAMS-R and not to the one in the SDP
> > > >
> > > > 2.       In the case where there is no RTP/RTCP multiplexing, the
> > > RAMS-R
> > > RTCP message will
> > > > go to the RS and the RAMS-I will go to the port on the RR from
> > > > where
> >
> > > > the
> > > RAMS-R was
> > > > received. For the RTP, the RR does not know if it has a NAT on
> the
> > > way
> > >
> > > > to
> > > the RS and
> > > > should try to get a routable address (using STUN for example) and
> > > providing the port to
> > > > the RS ( we still need to agree on how to do it)
> > > >
> > > > 3.       If the above two points are correct than the RR receive
> > port
> > > in
> > > the SDP is not
> > > > really useful
> > > >
> > > >
> > > >
> > > > Roni Even
> > >
> > >
> > > _______________________________________________
> > > Audio/Video Transport Working Group
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt



From abegen@cisco.com  Thu Jun 18 14:46:19 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 750013A67E1 for <avt@core3.amsl.com>; Thu, 18 Jun 2009 14:46:19 -0700 (PDT)
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 x3rlieJvsXrJ for <avt@core3.amsl.com>; Thu, 18 Jun 2009 14:46:17 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id AD7333A6874 for <avt@ietf.org>; Thu, 18 Jun 2009 14:46:17 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,246,1243814400"; d="scan'208";a="202231872"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-1.cisco.com with ESMTP; 18 Jun 2009 21:46:30 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n5ILkU0v031154;  Thu, 18 Jun 2009 14:46:30 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n5ILkUtN027458; Thu, 18 Jun 2009 21:46:30 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.3959);  Thu, 18 Jun 2009 14:46:30 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 18 Jun 2009 14:46:06 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MA==
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Zeev Vax" <zeevvax@microsoft.com>, "Roni Even" <Even.roni@huawei.com>, "Bill Ver Steeg (versteb)" <versteb@cisco.com>, "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>, <avt@ietf.org>
X-OriginalArrivalTime: 18 Jun 2009 21:46:30.0404 (UTC) FILETIME=[3D5FA440:01C9F05E]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=16745; t=1245361590; x=1246225590; c=relaxed/simple; s=sjdkim3002; 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]=20comments=20on=20section10ofdraf t-ietf-avt-rapid-acquisition-for-rtp-01 |Sender:=20; bh=f+JcHNfz/ySk7zbjwIBI0M7DRZPszI6MAO4oAK3Ik8g=; b=STN9NU555Pdhs21VTAfYOHNQeCoYGL0KTPcjH88nwes3Z+zI2xvUvPMxxL LPVhVEDNsj/RgiNTOasTG0hARmA60ka1Ij3CxXDMnHTI4ZxApEXELoDC7xzb K3xEgCulFY;
Authentication-Results: sj-dkim-3; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Subject: Re: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-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: Thu, 18 Jun 2009 21:46:19 -0000

Zeev,

I agree that mandating both is not a good idea. But, you should note =
that muxing does not solve our issues. So, mandating it will not be the =
cure for everything. See my email from Tuesday.

-acbegen

> -----Original Message-----
> From: Zeev Vax [mailto:zeevvax@microsoft.com]
> Sent: Thursday, June 18, 2009 2:27 PM
> To: Roni Even; Bill Ver Steeg (versteb); Ali C. Begen (abegen); 'VAN =
CAENEGEM Tom';
> avt@ietf.org
> Subject: RE: [AVT] comments on =
section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
> Roni,
>=20
> As I said I support mandating the multiplexing, but not the multiple =
ports. If there are
> no other opinions, we can add that to draft.
>=20
> Zeev
>=20
> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: Thursday, June 18, 2009 2:50 AM
> To: Zeev Vax; 'Bill Ver Steeg (versteb)'; 'Ali C. Begen (abegen)'; =
'VAN CAENEGEM Tom';
> avt@ietf.org
> Subject: RE: [AVT] comments on =
section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
> Zeev,
> This is a question I had in the past. I think that it merits a =
separate
> thread in order to get a consensus on the issue. Mandating RTP/RTCP
> multiplexing for the unicast burst make it simpler and faster to =
start.
>=20
> Note the two ports may still be used for the retransmission case.
>=20
> Roni
>=20
>=20
>=20
> > -----Original Message-----
> > From: Zeev Vax [mailto:zeevvax@microsoft.com]
> > Sent: Wednesday, June 17, 2009 7:45 PM
> > To: Bill Ver Steeg (versteb); Ali C. Begen (abegen); VAN CAENEGEM =
Tom;
> > Roni Even; avt@ietf.org
> > Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-
> > acquisition-for-rtp-01
> >
> > The text proposal looks fine to me.
> > I don't think we should mandate support both, this would cause extra
> > work in implementation of a solution, and I can't see any benefit.
> > Giving that this is UDP traffic port muxing is a subset of separate
> > ports, so we can mandate port muxing, and make optional the separate
> > ports.
> >
> > Zeev
> >
> >
> > -----Original Message-----
> > From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> > Sent: Wednesday, June 17, 2009 8:40 AM
> > To: Ali C. Begen (abegen); VAN CAENEGEM Tom; Roni Even; =
avt@ietf.org;
> > Zeev Vax
> > Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-
> > acquisition-for-rtp-01
> >
> > Tom-
> >
> > These words looks good to me as well, with the following =
clarification.
> >
> > We do need to consider how we handle RTP/RTCP port muxing throughout
> > the
> > document, and make the wording consistent wherever we reference the
> > ports in use. I am in favor of allowing (but not mandating) the RR =
to
> > signal RTP/RTCP port muxing. This would require the RS to support =
both
> > methods. This is just my opinion, and we need to come to consensus =
on
> > this matter.
> >
> >
> > Bill VerSteeg
> >
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf =
Of
> > Ali C. Begen (abegen)
> > Sent: Wednesday, June 17, 2009 10:15 AM
> > To: VAN CAENEGEM Tom; Roni Even; avt@ietf.org
> > Subject: Re: [AVT] comments on
> > section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > The proposed text looks good to me. We should probably put the burst
> > and
> > retransmission sources in the same block in Figure 2 as well.
> >
> > -acbegen
> >
> >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf =
Of
> > > VAN CAENEGEM Tom
> > > Sent: Wednesday, June 17, 2009 5:23 AM
> > > To: Roni Even; avt@ietf.org
> > > Subject: Re: [AVT] comments on section
> > > 10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > >
> > >
> > >  Hi Roni,
> > >
> > > Perhaps the start of section 6.2 can be rewritten as follows:
> > >
> > >
> > > <START>
> > >
> > > 6.2.  Message Flows
> > >
> > >    Figure 2 shows the main entities involved in rapid acquisition:
> > >
> > >    o  Multicast Source
> > >
> > >    o  Feedback Target (FT)
> > >
> > >    o  Burst/ Retransmission Source
> > >
> > >    o  RTP Receiver (RR)
> > >
> > > (fig 2)
> > >
> > >
> > > The feedback target (FT) is the entity as defined in [rtcpssm =
draft],
> > > to which the RR sends its RTCP FB messages, indicating packet loss =
in
> > > the ssm primary stream by means of a NACK or indicating the RR's
> > > desire to have rapid acquisition of the ssm primary stream (by =
means
> > > of an RTCP FB message as defined in this document). While the
> > > burst/retransmission source is responsible for responding on these
> > > messages and, in the case of rapid acquisition, further RTCP
> > > interaction with the RR during this acquisition process, it is
> > assumed
> >
> > > in the remainder of the document that these two logical entities =
(FT
> > > and burst/retransmission source) are combined in a single physical
> > > entity and share state. In the remainder of the text, the term
> > > retransmission server is used whenever appropriate, to refer to =
the
> > > combined functionality of the FT and retransmission/burst source.
> > > However, it must be noted that only the FT is involved in the =
primary
> > > ssm RTP session, whereas the burst/retransmission source transmits
> > > unicast RTP burst and RTP retransmissions packets (both formatted  =
as
> > > RTP retransmission packets
> > > [RFC4585]) in a single separate unicast RTP retransmission session =
to
> > > each RR.
> > >
> > > Note also that the same method (with the identical message flows)
> > > would also apply in a scenario where rapid acquisition is =
performed
> > by
> >
> > > a feedback target co-located with the media source.
> > >
> > > (...)
> > >
> > > <END>
> > >
> > > Tom: As we mandate the retransmission source and burst source to =
be
> > in
> >
> > > the same session, I think it is no longer required to split-up =
among
> > > these two logical entities. I invite other people, including the
> > > co-authors to comment on this new text proposal.
> > >
> > > With respect to your comments on the RTP/RTCP port muxing support
> > > indication by the RR inside the RAMS-R message. That would be =
needed,
> > > but is not sufficient as, if only declarative SDP is used, and we
> > want
> >
> > > to have the possibility that the RTP/RTCP packets in the
> > > retransmission session can be received by the RR on the same port =
the
> > > RR issues the RTCP RAMS-R, we need also a way by which the RR can
> > > signal this too. We provided a possible solution in the draft, but =
I
> > > understood that you think such a solution should be proposed in a
> > separate draft proposal?
> > > But I guess that would also apply then to the signaling of support
> > for
> >
> > > RTP/RTCP port muxing by the RR?
> > >
> > > Tom
> > >
> > > -----Original Message-----
> > > From: Roni Even [mailto:Even.roni@huawei.com]
> > > Sent: woensdag 17 juni 2009 13:24
> > > To: VAN CAENEGEM Tom; avt@ietf.org
> > > Subject: RE: [AVT] comments on section 10
> > > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > >
> > > Tom,
> > > I understand the RAMS-R and RAMS-T, the text is not clear enough =
in
> > > section
> > > 6.2
> > >
> > > It still leaves open the issue of the addresses for the RR in the
> > case
> >
> > > of declarative SDP when there is no answer SDP from the RR.
> > >
> > > About RTP/RTCP multiplexing, the declarative SDP can show that the =
RS
> > > supports it and I still think that some information about the
> > > addressing (like support for RTP/RTCP mux) should be supplied in =
the
> > > RAMS-R for the declarative case.
> > >
> > > Roni
> > >
> > > > -----Original Message-----
> > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On =
Behalf
> > > > Of VAN CAENEGEM Tom
> > > > Sent: Wednesday, June 17, 2009 11:17 AM
> > > > To: avt@ietf.org
> > > > Subject: Re: [AVT] comments on section 10 of =
draft-ietf-avt-rapid-
> > > > acquisition-for-rtp-01
> > > >
> > > > Hi Roni,
> > > >
> > > > I think your understanding was indeed different from the general
> > > >assumptions in this draft. Previously we agreed to only consider =
the
> > > >case where there is only one physical entity involved (called the
> > > >Retransmission Server in the draft), which allows us to NOT =
consider
> > > >and  discuss cases where for instance the feedback target (which =
is
> > > >defined  in the rtcpssm draft/RFC) is not in the same box as the
> > > >retransmission  source or burst source, the entities sourcing
> > > >retransmision/burst  packets. In that case we then would also =
need
> > to
> >
> > > >describe how these  separate entities communicate.
> > > > The fact that these different entities are now in the same box =
does
> > > >not  necessarily mean that all interactions and data exchange =
with
> > > >the RRs  is  part of the same RTP session, which is in this case =
the
> > > >SSM RTP  session.
> > > > As Ali explained, the NACK and RAMS-R RTCP FB messages are =
directed
> > > >to
> > >
> > > >the FB target, where we do not  defer from the rtcpssm draft. The
> > RTP
> >
> > > >retransmission/burst packets that are sent as a response to the =
NACK
> > > >and  the RAMS-R can be either session multiplexed with respect to
> > the
> >
> > > >original SSM RTP session or SSRC muxed (same session), following =
RFC
> > > >4588.
> > > >As the retransmission packets in this case are addressing the RR  =
in
> > > >unicast, we obviously have a dedicated RTP session for the
> > > >retransmission/burst packets. We had some internal discussion on
> > > >whether  considering the use case of having a separate session
> > > >between RS and RR  for RTP retransmission packets triggered by an
> > > >RTCP FB NACK and a  separate session for RTP burst packets =
triggered
> > > >by an RTCP RAMS-R made  sense, but we ended up agreeing that
> > allowing
> >
> > > >a single session was the  easiest way out, without imposing =
serious
> > > >limitations to the general  architecture.
> > > >
> > > > This means that the ports used by the (single) RTP
> > > > retransmission/burst session are in principle decoupled from the
> > > > primary SSM session. Hence if an RR wants to receive the
> > > > burst/retransmission packets and associated RTCP messages on the
> > > > same port the RR sent out the RTCP RAMS-R/ NACK FB messages, =
this
> > > > should either be signaled by the RR, OR such port usage scheme =
is
> > > > considered the "default" case -which also means the RR supports
> > > > RTP/RTCP port muxing for the retransmission/burst session-, and
> > then
> >
> > > > the RR needs to
> > >
> > > > signal the ports for receiving the RTP and RTCP packets in the
> > > > retransmission session when it requires dedicated ports.
> > > >
> > > > The RAMS-I (RS-> RR) and RAMS-T (RR-> RS) messages are only
> > relevant
> >
> > > > to a specific RR requesting the RTP burst stream and the RS, and
> > > > carry
> > >
> > > > information/signaling related to the retransmission/burst =
session
> > > > and have nothing to do with the SSM session. Hence the FB target =
as
> > > > logical entity is not involved here.
> > > >
> > > > I hope this clarifies rather than it contributes to your =
confusion.
> > > > But we may need to rephrase the part you quoted, as your
> > > > interpretation was different from its intended meaning. We also
> > > > tried to be more explicit in which session which RAMS or other =
RTCP
> > (e.g.
> > > > Bye) messages needed to be exchanged compared to a previous =
version
> > > > of
> > >
> > > > the draft, but we are open of course to any other suggestions =
from
> > > > your side if this is not clear enough in your opinion.
> > > >
> > > > Tom
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > " A Retransmission Source may equally act as a Burst Source.  =
The
> > > >    Retransmission Source may also incorporate the Feedback =
Target
> > > >    ([I-D.ietf-avt-rtcpssm] permits the feedback target to be a
> > > >    retransmission server, since it is a logical function to =
which
> > RRs
> > > >    send their unicast feedback), and we will use the term
> > > > Retransmission
> > > >    Server (RS) in the remainder of the document to refer to a
> > single
> > > >    physical entity comprising these three entities that share
> > state.
> > > >    Note that the same method (with the identical message flows)
> > would
> > > >    also apply in a scenario where rapid acquisition is performed =
by
> > a
> > > >    feedback target co-located with the media source."
> > > >
> > > > I assumed that we are only dealing with the case that the RS is =
a
> > > > single entity and not three different entities with different
> > > > addresses
> > > >
> > > > I also thought that this was agreed in previous discussions
> > > >
> > > > If my understanding is not correct I will review the draft since
> > the
> >
> > > > current text is not explicit enough to specify which part is =
doing
> > > > each message. I saw that RAMS-R is going to feedback target but
> > > > RAMS-T
> > >
> > > > is going to RS which is not specifying a specific address =
according
> > > > to
> > >
> > > > you.
> > > >
> > > > Roni
> > > >
> > > > -----Original Message-----
> > > > From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> > > > Sent: Tuesday, June 16, 2009 10:00 PM
> > > > To: Roni Even; avt@ietf.org
> > > > Subject: RE: [AVT] comments on section 10
> > > > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > > >
> > > > Remember that the RAMS-R (RR->RS) message is NOT on the
> > > > retransmission
> > > > (unicast) session, it's on the primary session since it is sent =
to
> > > > the
> > >
> > > > feedback target of the primary SSM session. Thus, the source =
port
> > RR
> >
> > > > uses to send RAMS-R "cannot" be assumed to be the destination =
port
> > > > it wishes to receive the unicast burst on.
> > > >
> > > > If you agree with this statement, it is clear why we need port
> > > > signaling.
> > > > Muxing will not help much here. It will just reduce the number =
of
> > > > signaled ports from 2 to 1.
> > > >
> > > > -acbegen
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > Behalf
> >
> > > > > Of Roni
> > > > Even
> > > > > Sent: Tuesday, June 16, 2009 10:08 AM
> > > > > To: avt@ietf.org
> > > > > Subject: [AVT] comments on section 10
> > > > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > > > >
> > > > > Hi,
> > > > >
> > > > > I looked at section 10 and have some comments
> > > > >
> > > > >
> > > > >
> > > > > 1.       If RTP/RTCP multiplexing is used, there is no need =
for
> > any
> > > > specific operation
> > > > > from the RR side. The RR sends the RAMS-R message to the RS =
from
> > > > > the
> > >
> > > > > port
> > > > it wants to
> > > > > receive the RAMS-I and RTP payload. The RS just sends the
> > > > > information to
> > > > the port from
> > > > > which it received the RAMS-R and not to the one in the SDP
> > > > >
> > > > > 2.       In the case where there is no RTP/RTCP multiplexing, =
the
> > > > RAMS-R
> > > > RTCP message will
> > > > > go to the RS and the RAMS-I will go to the port on the RR from
> > > > > where
> > >
> > > > > the
> > > > RAMS-R was
> > > > > received. For the RTP, the RR does not know if it has a NAT on
> > the
> > > > way
> > > >
> > > > > to
> > > > the RS and
> > > > > should try to get a routable address (using STUN for example) =
and
> > > > providing the port to
> > > > > the RS ( we still need to agree on how to do it)
> > > > >
> > > > > 3.       If the above two points are correct than the RR =
receive
> > > port
> > > > in
> > > > the SDP is not
> > > > > really useful
> > > > >
> > > > >
> > > > >
> > > > > Roni Even
> > > >
> > > >
> > > > _______________________________________________
> > > > Audio/Video Transport Working Group
> > > > avt@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/avt
> > >
> > > _______________________________________________
> > > Audio/Video Transport Working Group
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
>=20


From zeevvax@microsoft.com  Thu Jun 18 14:58:08 2009
Return-Path: <zeevvax@microsoft.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 4A8F43A6C39 for <avt@core3.amsl.com>; Thu, 18 Jun 2009 14:58:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 7Bd4hsvm2Slr for <avt@core3.amsl.com>; Thu, 18 Jun 2009 14:58:06 -0700 (PDT)
Received: from smtp.microsoft.com (mail2.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 6CB443A6884 for <avt@ietf.org>; Thu, 18 Jun 2009 14:58:06 -0700 (PDT)
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (157.54.79.159) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.99.4; Thu, 18 Jun 2009 14:58:18 -0700
Received: from tk5ex14mbxc105.redmond.corp.microsoft.com ([169.254.2.249]) by TK5EX14MLTC104.redmond.corp.microsoft.com ([157.54.79.159]) with mapi; Thu, 18 Jun 2009 14:58:18 -0700
From: Zeev Vax <zeevvax@microsoft.com>
To: "Ali C. Begen (abegen)" <abegen@cisco.com>, Roni Even <Even.roni@huawei.com>, "Bill Ver Steeg (versteb)" <versteb@cisco.com>, VAN CAENEGEM Tom <Tom.Van_Caenegem@alcatel-lucent.be>, "avt@ietf.org" <avt@ietf.org>
Thread-Topic: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDg
Date: Thu, 18 Jun 2009 21:58:09 +0000
Message-ID: <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com>
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-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: Thu, 18 Jun 2009 21:58:08 -0000

If we assume all entities are one, why would you need to signal the retrans=
mission port separately ?

Zeev

-----Original Message-----
From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
Sent: Thursday, June 18, 2009 2:46 PM
To: Zeev Vax; Roni Even; Bill Ver Steeg (versteb); VAN CAENEGEM Tom; avt@ie=
tf.org
Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisition-=
for-rtp-01

Zeev,

I agree that mandating both is not a good idea. But, you should note that m=
uxing does not solve our issues. So, mandating it will not be the cure for =
everything. See my email from Tuesday.

-acbegen

> -----Original Message-----
> From: Zeev Vax [mailto:zeevvax@microsoft.com]
> Sent: Thursday, June 18, 2009 2:27 PM
> To: Roni Even; Bill Ver Steeg (versteb); Ali C. Begen (abegen); 'VAN CAEN=
EGEM Tom';
> avt@ietf.org
> Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisitio=
n-for-rtp-01
>
> Roni,
>
> As I said I support mandating the multiplexing, but not the multiple port=
s. If there are
> no other opinions, we can add that to draft.
>
> Zeev
>
> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: Thursday, June 18, 2009 2:50 AM
> To: Zeev Vax; 'Bill Ver Steeg (versteb)'; 'Ali C. Begen (abegen)'; 'VAN C=
AENEGEM Tom';
> avt@ietf.org
> Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisitio=
n-for-rtp-01
>
> Zeev,
> This is a question I had in the past. I think that it merits a separate
> thread in order to get a consensus on the issue. Mandating RTP/RTCP
> multiplexing for the unicast burst make it simpler and faster to start.
>
> Note the two ports may still be used for the retransmission case.
>
> Roni
>
>
>
> > -----Original Message-----
> > From: Zeev Vax [mailto:zeevvax@microsoft.com]
> > Sent: Wednesday, June 17, 2009 7:45 PM
> > To: Bill Ver Steeg (versteb); Ali C. Begen (abegen); VAN CAENEGEM Tom;
> > Roni Even; avt@ietf.org
> > Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-
> > acquisition-for-rtp-01
> >
> > The text proposal looks fine to me.
> > I don't think we should mandate support both, this would cause extra
> > work in implementation of a solution, and I can't see any benefit.
> > Giving that this is UDP traffic port muxing is a subset of separate
> > ports, so we can mandate port muxing, and make optional the separate
> > ports.
> >
> > Zeev
> >
> >
> > -----Original Message-----
> > From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> > Sent: Wednesday, June 17, 2009 8:40 AM
> > To: Ali C. Begen (abegen); VAN CAENEGEM Tom; Roni Even; avt@ietf.org;
> > Zeev Vax
> > Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-
> > acquisition-for-rtp-01
> >
> > Tom-
> >
> > These words looks good to me as well, with the following clarification.
> >
> > We do need to consider how we handle RTP/RTCP port muxing throughout
> > the
> > document, and make the wording consistent wherever we reference the
> > ports in use. I am in favor of allowing (but not mandating) the RR to
> > signal RTP/RTCP port muxing. This would require the RS to support both
> > methods. This is just my opinion, and we need to come to consensus on
> > this matter.
> >
> >
> > Bill VerSteeg
> >
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> > Ali C. Begen (abegen)
> > Sent: Wednesday, June 17, 2009 10:15 AM
> > To: VAN CAENEGEM Tom; Roni Even; avt@ietf.org
> > Subject: Re: [AVT] comments on
> > section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > The proposed text looks good to me. We should probably put the burst
> > and
> > retransmission sources in the same block in Figure 2 as well.
> >
> > -acbegen
> >
> >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> > > VAN CAENEGEM Tom
> > > Sent: Wednesday, June 17, 2009 5:23 AM
> > > To: Roni Even; avt@ietf.org
> > > Subject: Re: [AVT] comments on section
> > > 10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > >
> > >
> > >  Hi Roni,
> > >
> > > Perhaps the start of section 6.2 can be rewritten as follows:
> > >
> > >
> > > <START>
> > >
> > > 6.2.  Message Flows
> > >
> > >    Figure 2 shows the main entities involved in rapid acquisition:
> > >
> > >    o  Multicast Source
> > >
> > >    o  Feedback Target (FT)
> > >
> > >    o  Burst/ Retransmission Source
> > >
> > >    o  RTP Receiver (RR)
> > >
> > > (fig 2)
> > >
> > >
> > > The feedback target (FT) is the entity as defined in [rtcpssm draft],
> > > to which the RR sends its RTCP FB messages, indicating packet loss in
> > > the ssm primary stream by means of a NACK or indicating the RR's
> > > desire to have rapid acquisition of the ssm primary stream (by means
> > > of an RTCP FB message as defined in this document). While the
> > > burst/retransmission source is responsible for responding on these
> > > messages and, in the case of rapid acquisition, further RTCP
> > > interaction with the RR during this acquisition process, it is
> > assumed
> >
> > > in the remainder of the document that these two logical entities (FT
> > > and burst/retransmission source) are combined in a single physical
> > > entity and share state. In the remainder of the text, the term
> > > retransmission server is used whenever appropriate, to refer to the
> > > combined functionality of the FT and retransmission/burst source.
> > > However, it must be noted that only the FT is involved in the primary
> > > ssm RTP session, whereas the burst/retransmission source transmits
> > > unicast RTP burst and RTP retransmissions packets (both formatted  as
> > > RTP retransmission packets
> > > [RFC4585]) in a single separate unicast RTP retransmission session to
> > > each RR.
> > >
> > > Note also that the same method (with the identical message flows)
> > > would also apply in a scenario where rapid acquisition is performed
> > by
> >
> > > a feedback target co-located with the media source.
> > >
> > > (...)
> > >
> > > <END>
> > >
> > > Tom: As we mandate the retransmission source and burst source to be
> > in
> >
> > > the same session, I think it is no longer required to split-up among
> > > these two logical entities. I invite other people, including the
> > > co-authors to comment on this new text proposal.
> > >
> > > With respect to your comments on the RTP/RTCP port muxing support
> > > indication by the RR inside the RAMS-R message. That would be needed,
> > > but is not sufficient as, if only declarative SDP is used, and we
> > want
> >
> > > to have the possibility that the RTP/RTCP packets in the
> > > retransmission session can be received by the RR on the same port the
> > > RR issues the RTCP RAMS-R, we need also a way by which the RR can
> > > signal this too. We provided a possible solution in the draft, but I
> > > understood that you think such a solution should be proposed in a
> > separate draft proposal?
> > > But I guess that would also apply then to the signaling of support
> > for
> >
> > > RTP/RTCP port muxing by the RR?
> > >
> > > Tom
> > >
> > > -----Original Message-----
> > > From: Roni Even [mailto:Even.roni@huawei.com]
> > > Sent: woensdag 17 juni 2009 13:24
> > > To: VAN CAENEGEM Tom; avt@ietf.org
> > > Subject: RE: [AVT] comments on section 10
> > > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > >
> > > Tom,
> > > I understand the RAMS-R and RAMS-T, the text is not clear enough in
> > > section
> > > 6.2
> > >
> > > It still leaves open the issue of the addresses for the RR in the
> > case
> >
> > > of declarative SDP when there is no answer SDP from the RR.
> > >
> > > About RTP/RTCP multiplexing, the declarative SDP can show that the RS
> > > supports it and I still think that some information about the
> > > addressing (like support for RTP/RTCP mux) should be supplied in the
> > > RAMS-R for the declarative case.
> > >
> > > Roni
> > >
> > > > -----Original Message-----
> > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
> > > > Of VAN CAENEGEM Tom
> > > > Sent: Wednesday, June 17, 2009 11:17 AM
> > > > To: avt@ietf.org
> > > > Subject: Re: [AVT] comments on section 10 of draft-ietf-avt-rapid-
> > > > acquisition-for-rtp-01
> > > >
> > > > Hi Roni,
> > > >
> > > > I think your understanding was indeed different from the general
> > > >assumptions in this draft. Previously we agreed to only consider the
> > > >case where there is only one physical entity involved (called the
> > > >Retransmission Server in the draft), which allows us to NOT consider
> > > >and  discuss cases where for instance the feedback target (which is
> > > >defined  in the rtcpssm draft/RFC) is not in the same box as the
> > > >retransmission  source or burst source, the entities sourcing
> > > >retransmision/burst  packets. In that case we then would also need
> > to
> >
> > > >describe how these  separate entities communicate.
> > > > The fact that these different entities are now in the same box does
> > > >not  necessarily mean that all interactions and data exchange with
> > > >the RRs  is  part of the same RTP session, which is in this case the
> > > >SSM RTP  session.
> > > > As Ali explained, the NACK and RAMS-R RTCP FB messages are directed
> > > >to
> > >
> > > >the FB target, where we do not  defer from the rtcpssm draft. The
> > RTP
> >
> > > >retransmission/burst packets that are sent as a response to the NACK
> > > >and  the RAMS-R can be either session multiplexed with respect to
> > the
> >
> > > >original SSM RTP session or SSRC muxed (same session), following RFC
> > > >4588.
> > > >As the retransmission packets in this case are addressing the RR  in
> > > >unicast, we obviously have a dedicated RTP session for the
> > > >retransmission/burst packets. We had some internal discussion on
> > > >whether  considering the use case of having a separate session
> > > >between RS and RR  for RTP retransmission packets triggered by an
> > > >RTCP FB NACK and a  separate session for RTP burst packets triggered
> > > >by an RTCP RAMS-R made  sense, but we ended up agreeing that
> > allowing
> >
> > > >a single session was the  easiest way out, without imposing serious
> > > >limitations to the general  architecture.
> > > >
> > > > This means that the ports used by the (single) RTP
> > > > retransmission/burst session are in principle decoupled from the
> > > > primary SSM session. Hence if an RR wants to receive the
> > > > burst/retransmission packets and associated RTCP messages on the
> > > > same port the RR sent out the RTCP RAMS-R/ NACK FB messages, this
> > > > should either be signaled by the RR, OR such port usage scheme is
> > > > considered the "default" case -which also means the RR supports
> > > > RTP/RTCP port muxing for the retransmission/burst session-, and
> > then
> >
> > > > the RR needs to
> > >
> > > > signal the ports for receiving the RTP and RTCP packets in the
> > > > retransmission session when it requires dedicated ports.
> > > >
> > > > The RAMS-I (RS-> RR) and RAMS-T (RR-> RS) messages are only
> > relevant
> >
> > > > to a specific RR requesting the RTP burst stream and the RS, and
> > > > carry
> > >
> > > > information/signaling related to the retransmission/burst session
> > > > and have nothing to do with the SSM session. Hence the FB target as
> > > > logical entity is not involved here.
> > > >
> > > > I hope this clarifies rather than it contributes to your confusion.
> > > > But we may need to rephrase the part you quoted, as your
> > > > interpretation was different from its intended meaning. We also
> > > > tried to be more explicit in which session which RAMS or other RTCP
> > (e.g.
> > > > Bye) messages needed to be exchanged compared to a previous version
> > > > of
> > >
> > > > the draft, but we are open of course to any other suggestions from
> > > > your side if this is not clear enough in your opinion.
> > > >
> > > > Tom
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > " A Retransmission Source may equally act as a Burst Source.  The
> > > >    Retransmission Source may also incorporate the Feedback Target
> > > >    ([I-D.ietf-avt-rtcpssm] permits the feedback target to be a
> > > >    retransmission server, since it is a logical function to which
> > RRs
> > > >    send their unicast feedback), and we will use the term
> > > > Retransmission
> > > >    Server (RS) in the remainder of the document to refer to a
> > single
> > > >    physical entity comprising these three entities that share
> > state.
> > > >    Note that the same method (with the identical message flows)
> > would
> > > >    also apply in a scenario where rapid acquisition is performed by
> > a
> > > >    feedback target co-located with the media source."
> > > >
> > > > I assumed that we are only dealing with the case that the RS is a
> > > > single entity and not three different entities with different
> > > > addresses
> > > >
> > > > I also thought that this was agreed in previous discussions
> > > >
> > > > If my understanding is not correct I will review the draft since
> > the
> >
> > > > current text is not explicit enough to specify which part is doing
> > > > each message. I saw that RAMS-R is going to feedback target but
> > > > RAMS-T
> > >
> > > > is going to RS which is not specifying a specific address according
> > > > to
> > >
> > > > you.
> > > >
> > > > Roni
> > > >
> > > > -----Original Message-----
> > > > From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> > > > Sent: Tuesday, June 16, 2009 10:00 PM
> > > > To: Roni Even; avt@ietf.org
> > > > Subject: RE: [AVT] comments on section 10
> > > > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > > >
> > > > Remember that the RAMS-R (RR->RS) message is NOT on the
> > > > retransmission
> > > > (unicast) session, it's on the primary session since it is sent to
> > > > the
> > >
> > > > feedback target of the primary SSM session. Thus, the source port
> > RR
> >
> > > > uses to send RAMS-R "cannot" be assumed to be the destination port
> > > > it wishes to receive the unicast burst on.
> > > >
> > > > If you agree with this statement, it is clear why we need port
> > > > signaling.
> > > > Muxing will not help much here. It will just reduce the number of
> > > > signaled ports from 2 to 1.
> > > >
> > > > -acbegen
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > Behalf
> >
> > > > > Of Roni
> > > > Even
> > > > > Sent: Tuesday, June 16, 2009 10:08 AM
> > > > > To: avt@ietf.org
> > > > > Subject: [AVT] comments on section 10
> > > > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > > > >
> > > > > Hi,
> > > > >
> > > > > I looked at section 10 and have some comments
> > > > >
> > > > >
> > > > >
> > > > > 1.       If RTP/RTCP multiplexing is used, there is no need for
> > any
> > > > specific operation
> > > > > from the RR side. The RR sends the RAMS-R message to the RS from
> > > > > the
> > >
> > > > > port
> > > > it wants to
> > > > > receive the RAMS-I and RTP payload. The RS just sends the
> > > > > information to
> > > > the port from
> > > > > which it received the RAMS-R and not to the one in the SDP
> > > > >
> > > > > 2.       In the case where there is no RTP/RTCP multiplexing, the
> > > > RAMS-R
> > > > RTCP message will
> > > > > go to the RS and the RAMS-I will go to the port on the RR from
> > > > > where
> > >
> > > > > the
> > > > RAMS-R was
> > > > > received. For the RTP, the RR does not know if it has a NAT on
> > the
> > > > way
> > > >
> > > > > to
> > > > the RS and
> > > > > should try to get a routable address (using STUN for example) and
> > > > providing the port to
> > > > > the RS ( we still need to agree on how to do it)
> > > > >
> > > > > 3.       If the above two points are correct than the RR receive
> > > port
> > > > in
> > > > the SDP is not
> > > > > really useful
> > > > >
> > > > >
> > > > >
> > > > > Roni Even
> > > >
> > > >
> > > > _______________________________________________
> > > > Audio/Video Transport Working Group
> > > > avt@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/avt
> > >
> > > _______________________________________________
> > > Audio/Video Transport Working Group
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
>



From abegen@cisco.com  Thu Jun 18 15:06:40 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 830993A6884 for <avt@core3.amsl.com>; Thu, 18 Jun 2009 15:06:40 -0700 (PDT)
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=[AWL=0.000,  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 oOtiI+h7Y3y9 for <avt@core3.amsl.com>; Thu, 18 Jun 2009 15:06:37 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 8BCFE3A6826 for <avt@ietf.org>; Thu, 18 Jun 2009 15:06:37 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,246,1243814400"; d="scan'208";a="178019559"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-2.cisco.com with ESMTP; 18 Jun 2009 22:06:50 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n5IM6o3G010206;  Thu, 18 Jun 2009 15:06:50 -0700
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.14.3) with ESMTP id n5IM6ihV020363; Thu, 18 Jun 2009 22:06:50 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.3959);  Thu, 18 Jun 2009 15:06:46 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 18 Jun 2009 15:06:45 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540995BF5A@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDgAAAtbKA=
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Zeev Vax" <zeevvax@microsoft.com>, "Roni Even" <Even.roni@huawei.com>, "Bill Ver Steeg (versteb)" <versteb@cisco.com>, "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>, <avt@ietf.org>
X-OriginalArrivalTime: 18 Jun 2009 22:06:46.0884 (UTC) FILETIME=[1273C240:01C9F061]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=19358; t=1245362810; x=1246226810; c=relaxed/simple; s=sjdkim1004; 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]=20comments=20on=20section10ofdraf t-ietf-avt-rapid-acquisition-for-rtp-01 |Sender:=20; bh=D63JG8Cg0KTQtPY9YqcdzLfh8PjTQPwh7yNKhfjLZm8=; b=it7cZXpeMbPYXXmPT1R005GBFAhNbpxN0PmScuo4CJKHoScdPhZr20C4Sn HGX9AKkeSD7J9AvNXG+enAJT0hm3TNbmX8ZcZkskqcXHoqBkqiUb1TjHGkoV iQCfBlzOYcn4ZDIh8cQqoiAW0HCWOB9vH5HepPSnI99oj0k3/jorw=;
Authentication-Results: sj-dkim-1; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Subject: Re: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-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: Thu, 18 Jun 2009 22:06:40 -0000

I will copy/paste from my earlier email:

<quote>
Remember that the RAMS-R (RR->RS) message is NOT on the retransmission =
(unicast) session, it's on the primary session since it is sent to the =
feedback target of the primary SSM session. Thus, the source port RR =
uses to send RAMS-R "cannot" be assumed to be the destination port it =
wishes to receive the unicast burst on.
</quote>

So, even if muxing is enabled by RR meaning that it can receive RTP and =
RTCP on the same port, we still need to signal that single port somehow. =
One way of doing it is PubPorts message (which is by itself an RTCP =
message and can be appended to the RTCP packet that carries RAMS-R =
message). And frankly speaking, signaling two ports (RTP + RTCP) is not =
any more difficult than signaling a single (muxed) port. Thus, IMO we =
should not be mandating muxing.

-acbegen

> -----Original Message-----
> From: Zeev Vax [mailto:zeevvax@microsoft.com]
> Sent: Thursday, June 18, 2009 2:58 PM
> To: Ali C. Begen (abegen); Roni Even; Bill Ver Steeg (versteb); VAN =
CAENEGEM Tom;
> avt@ietf.org
> Subject: RE: [AVT] comments on =
section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
> If we assume all entities are one, why would you need to signal the =
retransmission port
> separately ?
>=20
> Zeev
>=20
> -----Original Message-----
> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> Sent: Thursday, June 18, 2009 2:46 PM
> To: Zeev Vax; Roni Even; Bill Ver Steeg (versteb); VAN CAENEGEM Tom; =
avt@ietf.org
> Subject: RE: [AVT] comments on =
section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
> Zeev,
>=20
> I agree that mandating both is not a good idea. But, you should note =
that muxing does not
> solve our issues. So, mandating it will not be the cure for =
everything. See my email from
> Tuesday.
>=20
> -acbegen
>=20
> > -----Original Message-----
> > From: Zeev Vax [mailto:zeevvax@microsoft.com]
> > Sent: Thursday, June 18, 2009 2:27 PM
> > To: Roni Even; Bill Ver Steeg (versteb); Ali C. Begen (abegen); 'VAN =
CAENEGEM Tom';
> > avt@ietf.org
> > Subject: RE: [AVT] comments on =
section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > Roni,
> >
> > As I said I support mandating the multiplexing, but not the multiple =
ports. If there are
> > no other opinions, we can add that to draft.
> >
> > Zeev
> >
> > -----Original Message-----
> > From: Roni Even [mailto:Even.roni@huawei.com]
> > Sent: Thursday, June 18, 2009 2:50 AM
> > To: Zeev Vax; 'Bill Ver Steeg (versteb)'; 'Ali C. Begen (abegen)'; =
'VAN CAENEGEM Tom';
> > avt@ietf.org
> > Subject: RE: [AVT] comments on =
section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > Zeev,
> > This is a question I had in the past. I think that it merits a =
separate
> > thread in order to get a consensus on the issue. Mandating RTP/RTCP
> > multiplexing for the unicast burst make it simpler and faster to =
start.
> >
> > Note the two ports may still be used for the retransmission case.
> >
> > Roni
> >
> >
> >
> > > -----Original Message-----
> > > From: Zeev Vax [mailto:zeevvax@microsoft.com]
> > > Sent: Wednesday, June 17, 2009 7:45 PM
> > > To: Bill Ver Steeg (versteb); Ali C. Begen (abegen); VAN CAENEGEM =
Tom;
> > > Roni Even; avt@ietf.org
> > > Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-
> > > acquisition-for-rtp-01
> > >
> > > The text proposal looks fine to me.
> > > I don't think we should mandate support both, this would cause =
extra
> > > work in implementation of a solution, and I can't see any benefit.
> > > Giving that this is UDP traffic port muxing is a subset of =
separate
> > > ports, so we can mandate port muxing, and make optional the =
separate
> > > ports.
> > >
> > > Zeev
> > >
> > >
> > > -----Original Message-----
> > > From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> > > Sent: Wednesday, June 17, 2009 8:40 AM
> > > To: Ali C. Begen (abegen); VAN CAENEGEM Tom; Roni Even; =
avt@ietf.org;
> > > Zeev Vax
> > > Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-
> > > acquisition-for-rtp-01
> > >
> > > Tom-
> > >
> > > These words looks good to me as well, with the following =
clarification.
> > >
> > > We do need to consider how we handle RTP/RTCP port muxing =
throughout
> > > the
> > > document, and make the wording consistent wherever we reference =
the
> > > ports in use. I am in favor of allowing (but not mandating) the RR =
to
> > > signal RTP/RTCP port muxing. This would require the RS to support =
both
> > > methods. This is just my opinion, and we need to come to consensus =
on
> > > this matter.
> > >
> > >
> > > Bill VerSteeg
> > >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf =
Of
> > > Ali C. Begen (abegen)
> > > Sent: Wednesday, June 17, 2009 10:15 AM
> > > To: VAN CAENEGEM Tom; Roni Even; avt@ietf.org
> > > Subject: Re: [AVT] comments on
> > > section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > >
> > > The proposed text looks good to me. We should probably put the =
burst
> > > and
> > > retransmission sources in the same block in Figure 2 as well.
> > >
> > > -acbegen
> > >
> > >
> > > > -----Original Message-----
> > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On =
Behalf Of
> > > > VAN CAENEGEM Tom
> > > > Sent: Wednesday, June 17, 2009 5:23 AM
> > > > To: Roni Even; avt@ietf.org
> > > > Subject: Re: [AVT] comments on section
> > > > 10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > > >
> > > >
> > > >  Hi Roni,
> > > >
> > > > Perhaps the start of section 6.2 can be rewritten as follows:
> > > >
> > > >
> > > > <START>
> > > >
> > > > 6.2.  Message Flows
> > > >
> > > >    Figure 2 shows the main entities involved in rapid =
acquisition:
> > > >
> > > >    o  Multicast Source
> > > >
> > > >    o  Feedback Target (FT)
> > > >
> > > >    o  Burst/ Retransmission Source
> > > >
> > > >    o  RTP Receiver (RR)
> > > >
> > > > (fig 2)
> > > >
> > > >
> > > > The feedback target (FT) is the entity as defined in [rtcpssm =
draft],
> > > > to which the RR sends its RTCP FB messages, indicating packet =
loss in
> > > > the ssm primary stream by means of a NACK or indicating the RR's
> > > > desire to have rapid acquisition of the ssm primary stream (by =
means
> > > > of an RTCP FB message as defined in this document). While the
> > > > burst/retransmission source is responsible for responding on =
these
> > > > messages and, in the case of rapid acquisition, further RTCP
> > > > interaction with the RR during this acquisition process, it is
> > > assumed
> > >
> > > > in the remainder of the document that these two logical entities =
(FT
> > > > and burst/retransmission source) are combined in a single =
physical
> > > > entity and share state. In the remainder of the text, the term
> > > > retransmission server is used whenever appropriate, to refer to =
the
> > > > combined functionality of the FT and retransmission/burst =
source.
> > > > However, it must be noted that only the FT is involved in the =
primary
> > > > ssm RTP session, whereas the burst/retransmission source =
transmits
> > > > unicast RTP burst and RTP retransmissions packets (both =
formatted  as
> > > > RTP retransmission packets
> > > > [RFC4585]) in a single separate unicast RTP retransmission =
session to
> > > > each RR.
> > > >
> > > > Note also that the same method (with the identical message =
flows)
> > > > would also apply in a scenario where rapid acquisition is =
performed
> > > by
> > >
> > > > a feedback target co-located with the media source.
> > > >
> > > > (...)
> > > >
> > > > <END>
> > > >
> > > > Tom: As we mandate the retransmission source and burst source to =
be
> > > in
> > >
> > > > the same session, I think it is no longer required to split-up =
among
> > > > these two logical entities. I invite other people, including the
> > > > co-authors to comment on this new text proposal.
> > > >
> > > > With respect to your comments on the RTP/RTCP port muxing =
support
> > > > indication by the RR inside the RAMS-R message. That would be =
needed,
> > > > but is not sufficient as, if only declarative SDP is used, and =
we
> > > want
> > >
> > > > to have the possibility that the RTP/RTCP packets in the
> > > > retransmission session can be received by the RR on the same =
port the
> > > > RR issues the RTCP RAMS-R, we need also a way by which the RR =
can
> > > > signal this too. We provided a possible solution in the draft, =
but I
> > > > understood that you think such a solution should be proposed in =
a
> > > separate draft proposal?
> > > > But I guess that would also apply then to the signaling of =
support
> > > for
> > >
> > > > RTP/RTCP port muxing by the RR?
> > > >
> > > > Tom
> > > >
> > > > -----Original Message-----
> > > > From: Roni Even [mailto:Even.roni@huawei.com]
> > > > Sent: woensdag 17 juni 2009 13:24
> > > > To: VAN CAENEGEM Tom; avt@ietf.org
> > > > Subject: RE: [AVT] comments on section 10
> > > > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > > >
> > > > Tom,
> > > > I understand the RAMS-R and RAMS-T, the text is not clear enough =
in
> > > > section
> > > > 6.2
> > > >
> > > > It still leaves open the issue of the addresses for the RR in =
the
> > > case
> > >
> > > > of declarative SDP when there is no answer SDP from the RR.
> > > >
> > > > About RTP/RTCP multiplexing, the declarative SDP can show that =
the RS
> > > > supports it and I still think that some information about the
> > > > addressing (like support for RTP/RTCP mux) should be supplied in =
the
> > > > RAMS-R for the declarative case.
> > > >
> > > > Roni
> > > >
> > > > > -----Original Message-----
> > > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On =
Behalf
> > > > > Of VAN CAENEGEM Tom
> > > > > Sent: Wednesday, June 17, 2009 11:17 AM
> > > > > To: avt@ietf.org
> > > > > Subject: Re: [AVT] comments on section 10 of =
draft-ietf-avt-rapid-
> > > > > acquisition-for-rtp-01
> > > > >
> > > > > Hi Roni,
> > > > >
> > > > > I think your understanding was indeed different from the =
general
> > > > >assumptions in this draft. Previously we agreed to only =
consider the
> > > > >case where there is only one physical entity involved (called =
the
> > > > >Retransmission Server in the draft), which allows us to NOT =
consider
> > > > >and  discuss cases where for instance the feedback target =
(which is
> > > > >defined  in the rtcpssm draft/RFC) is not in the same box as =
the
> > > > >retransmission  source or burst source, the entities sourcing
> > > > >retransmision/burst  packets. In that case we then would also =
need
> > > to
> > >
> > > > >describe how these  separate entities communicate.
> > > > > The fact that these different entities are now in the same box =
does
> > > > >not  necessarily mean that all interactions and data exchange =
with
> > > > >the RRs  is  part of the same RTP session, which is in this =
case the
> > > > >SSM RTP  session.
> > > > > As Ali explained, the NACK and RAMS-R RTCP FB messages are =
directed
> > > > >to
> > > >
> > > > >the FB target, where we do not  defer from the rtcpssm draft. =
The
> > > RTP
> > >
> > > > >retransmission/burst packets that are sent as a response to the =
NACK
> > > > >and  the RAMS-R can be either session multiplexed with respect =
to
> > > the
> > >
> > > > >original SSM RTP session or SSRC muxed (same session), =
following RFC
> > > > >4588.
> > > > >As the retransmission packets in this case are addressing the =
RR  in
> > > > >unicast, we obviously have a dedicated RTP session for the
> > > > >retransmission/burst packets. We had some internal discussion =
on
> > > > >whether  considering the use case of having a separate session
> > > > >between RS and RR  for RTP retransmission packets triggered by =
an
> > > > >RTCP FB NACK and a  separate session for RTP burst packets =
triggered
> > > > >by an RTCP RAMS-R made  sense, but we ended up agreeing that
> > > allowing
> > >
> > > > >a single session was the  easiest way out, without imposing =
serious
> > > > >limitations to the general  architecture.
> > > > >
> > > > > This means that the ports used by the (single) RTP
> > > > > retransmission/burst session are in principle decoupled from =
the
> > > > > primary SSM session. Hence if an RR wants to receive the
> > > > > burst/retransmission packets and associated RTCP messages on =
the
> > > > > same port the RR sent out the RTCP RAMS-R/ NACK FB messages, =
this
> > > > > should either be signaled by the RR, OR such port usage scheme =
is
> > > > > considered the "default" case -which also means the RR =
supports
> > > > > RTP/RTCP port muxing for the retransmission/burst session-, =
and
> > > then
> > >
> > > > > the RR needs to
> > > >
> > > > > signal the ports for receiving the RTP and RTCP packets in the
> > > > > retransmission session when it requires dedicated ports.
> > > > >
> > > > > The RAMS-I (RS-> RR) and RAMS-T (RR-> RS) messages are only
> > > relevant
> > >
> > > > > to a specific RR requesting the RTP burst stream and the RS, =
and
> > > > > carry
> > > >
> > > > > information/signaling related to the retransmission/burst =
session
> > > > > and have nothing to do with the SSM session. Hence the FB =
target as
> > > > > logical entity is not involved here.
> > > > >
> > > > > I hope this clarifies rather than it contributes to your =
confusion.
> > > > > But we may need to rephrase the part you quoted, as your
> > > > > interpretation was different from its intended meaning. We =
also
> > > > > tried to be more explicit in which session which RAMS or other =
RTCP
> > > (e.g.
> > > > > Bye) messages needed to be exchanged compared to a previous =
version
> > > > > of
> > > >
> > > > > the draft, but we are open of course to any other suggestions =
from
> > > > > your side if this is not clear enough in your opinion.
> > > > >
> > > > > Tom
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > " A Retransmission Source may equally act as a Burst Source.  =
The
> > > > >    Retransmission Source may also incorporate the Feedback =
Target
> > > > >    ([I-D.ietf-avt-rtcpssm] permits the feedback target to be a
> > > > >    retransmission server, since it is a logical function to =
which
> > > RRs
> > > > >    send their unicast feedback), and we will use the term
> > > > > Retransmission
> > > > >    Server (RS) in the remainder of the document to refer to a
> > > single
> > > > >    physical entity comprising these three entities that share
> > > state.
> > > > >    Note that the same method (with the identical message =
flows)
> > > would
> > > > >    also apply in a scenario where rapid acquisition is =
performed by
> > > a
> > > > >    feedback target co-located with the media source."
> > > > >
> > > > > I assumed that we are only dealing with the case that the RS =
is a
> > > > > single entity and not three different entities with different
> > > > > addresses
> > > > >
> > > > > I also thought that this was agreed in previous discussions
> > > > >
> > > > > If my understanding is not correct I will review the draft =
since
> > > the
> > >
> > > > > current text is not explicit enough to specify which part is =
doing
> > > > > each message. I saw that RAMS-R is going to feedback target =
but
> > > > > RAMS-T
> > > >
> > > > > is going to RS which is not specifying a specific address =
according
> > > > > to
> > > >
> > > > > you.
> > > > >
> > > > > Roni
> > > > >
> > > > > -----Original Message-----
> > > > > From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> > > > > Sent: Tuesday, June 16, 2009 10:00 PM
> > > > > To: Roni Even; avt@ietf.org
> > > > > Subject: RE: [AVT] comments on section 10
> > > > > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > > > >
> > > > > Remember that the RAMS-R (RR->RS) message is NOT on the
> > > > > retransmission
> > > > > (unicast) session, it's on the primary session since it is =
sent to
> > > > > the
> > > >
> > > > > feedback target of the primary SSM session. Thus, the source =
port
> > > RR
> > >
> > > > > uses to send RAMS-R "cannot" be assumed to be the destination =
port
> > > > > it wishes to receive the unicast burst on.
> > > > >
> > > > > If you agree with this statement, it is clear why we need port
> > > > > signaling.
> > > > > Muxing will not help much here. It will just reduce the number =
of
> > > > > signaled ports from 2 to 1.
> > > > >
> > > > > -acbegen
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > Behalf
> > >
> > > > > > Of Roni
> > > > > Even
> > > > > > Sent: Tuesday, June 16, 2009 10:08 AM
> > > > > > To: avt@ietf.org
> > > > > > Subject: [AVT] comments on section 10
> > > > > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I looked at section 10 and have some comments
> > > > > >
> > > > > >
> > > > > >
> > > > > > 1.       If RTP/RTCP multiplexing is used, there is no need =
for
> > > any
> > > > > specific operation
> > > > > > from the RR side. The RR sends the RAMS-R message to the RS =
from
> > > > > > the
> > > >
> > > > > > port
> > > > > it wants to
> > > > > > receive the RAMS-I and RTP payload. The RS just sends the
> > > > > > information to
> > > > > the port from
> > > > > > which it received the RAMS-R and not to the one in the SDP
> > > > > >
> > > > > > 2.       In the case where there is no RTP/RTCP =
multiplexing, the
> > > > > RAMS-R
> > > > > RTCP message will
> > > > > > go to the RS and the RAMS-I will go to the port on the RR =
from
> > > > > > where
> > > >
> > > > > > the
> > > > > RAMS-R was
> > > > > > received. For the RTP, the RR does not know if it has a NAT =
on
> > > the
> > > > > way
> > > > >
> > > > > > to
> > > > > the RS and
> > > > > > should try to get a routable address (using STUN for =
example) and
> > > > > providing the port to
> > > > > > the RS ( we still need to agree on how to do it)
> > > > > >
> > > > > > 3.       If the above two points are correct than the RR =
receive
> > > > port
> > > > > in
> > > > > the SDP is not
> > > > > > really useful
> > > > > >
> > > > > >
> > > > > >
> > > > > > Roni Even
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Audio/Video Transport Working Group
> > > > > avt@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/avt
> > > >
> > > > _______________________________________________
> > > > Audio/Video Transport Working Group
> > > > avt@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/avt
> > > _______________________________________________
> > > Audio/Video Transport Working Group
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
> >
>=20


From zeevvax@microsoft.com  Thu Jun 18 15:48:27 2009
Return-Path: <zeevvax@microsoft.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 3BE763A6976 for <avt@core3.amsl.com>; Thu, 18 Jun 2009 15:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 LeY5q7koSgj0 for <avt@core3.amsl.com>; Thu, 18 Jun 2009 15:48:25 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id 498A93A67ED for <avt@ietf.org>; Thu, 18 Jun 2009 15:48:25 -0700 (PDT)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.99.4; Thu, 18 Jun 2009 15:48:37 -0700
Received: from tk5ex14mbxc105.redmond.corp.microsoft.com ([169.254.2.249]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi; Thu, 18 Jun 2009 15:48:35 -0700
From: Zeev Vax <zeevvax@microsoft.com>
To: "Ali C. Begen (abegen)" <abegen@cisco.com>, Roni Even <Even.roni@huawei.com>, "Bill Ver Steeg (versteb)" <versteb@cisco.com>, VAN CAENEGEM Tom <Tom.Van_Caenegem@alcatel-lucent.be>, "avt@ietf.org" <avt@ietf.org>
Thread-Topic: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDgAAAtbKAAAW1pIA==
Date: Thu, 18 Jun 2009 22:47:53 +0000
Message-ID: <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC974F@tk5ex14mbxc105.redmond.corp.microsoft.com>
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF5A@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D540995BF5A@xmb-sjc-215.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-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: Thu, 18 Jun 2009 22:48:27 -0000

Thanks I read your earlier message before, my point is that if you assume a=
ll entities are one, and assume muxing, you can assume the source port the =
RR use to send the RAMS-R is the same it wishes to receive the burst and co=
ntrol answers.
I.e. - I disagree with your conclusion below
<quote>
Thus, the source port RR uses to send RAMS-R "cannot" be assumed to be the =
destination port it wishes to receive the unicast burst on.
</quote>

Zeev
-----Original Message-----
From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
Sent: Thursday, June 18, 2009 3:07 PM
To: Zeev Vax; Roni Even; Bill Ver Steeg (versteb); VAN CAENEGEM Tom; avt@ie=
tf.org
Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisition-=
for-rtp-01

I will copy/paste from my earlier email:

<quote>
Remember that the RAMS-R (RR->RS) message is NOT on the retransmission (uni=
cast) session, it's on the primary session since it is sent to the feedback=
 target of the primary SSM session. Thus, the source port RR uses to send R=
AMS-R "cannot" be assumed to be the destination port it wishes to receive t=
he unicast burst on.
</quote>

So, even if muxing is enabled by RR meaning that it can receive RTP and RTC=
P on the same port, we still need to signal that single port somehow. One w=
ay of doing it is PubPorts message (which is by itself an RTCP message and =
can be appended to the RTCP packet that carries RAMS-R message). And frankl=
y speaking, signaling two ports (RTP + RTCP) is not any more difficult than=
 signaling a single (muxed) port. Thus, IMO we should not be mandating muxi=
ng.

-acbegen

> -----Original Message-----
> From: Zeev Vax [mailto:zeevvax@microsoft.com]
> Sent: Thursday, June 18, 2009 2:58 PM
> To: Ali C. Begen (abegen); Roni Even; Bill Ver Steeg (versteb); VAN CAENE=
GEM Tom;
> avt@ietf.org
> Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisitio=
n-for-rtp-01
>
> If we assume all entities are one, why would you need to signal the retra=
nsmission port
> separately ?
>
> Zeev
>
> -----Original Message-----
> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> Sent: Thursday, June 18, 2009 2:46 PM
> To: Zeev Vax; Roni Even; Bill Ver Steeg (versteb); VAN CAENEGEM Tom; avt@=
ietf.org
> Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisitio=
n-for-rtp-01
>
> Zeev,
>
> I agree that mandating both is not a good idea. But, you should note that=
 muxing does not
> solve our issues. So, mandating it will not be the cure for everything. S=
ee my email from
> Tuesday.
>
> -acbegen
>
> > -----Original Message-----
> > From: Zeev Vax [mailto:zeevvax@microsoft.com]
> > Sent: Thursday, June 18, 2009 2:27 PM
> > To: Roni Even; Bill Ver Steeg (versteb); Ali C. Begen (abegen); 'VAN CA=
ENEGEM Tom';
> > avt@ietf.org
> > Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisit=
ion-for-rtp-01
> >
> > Roni,
> >
> > As I said I support mandating the multiplexing, but not the multiple po=
rts. If there are
> > no other opinions, we can add that to draft.
> >
> > Zeev
> >
> > -----Original Message-----
> > From: Roni Even [mailto:Even.roni@huawei.com]
> > Sent: Thursday, June 18, 2009 2:50 AM
> > To: Zeev Vax; 'Bill Ver Steeg (versteb)'; 'Ali C. Begen (abegen)'; 'VAN=
 CAENEGEM Tom';
> > avt@ietf.org
> > Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-acquisit=
ion-for-rtp-01
> >
> > Zeev,
> > This is a question I had in the past. I think that it merits a separate
> > thread in order to get a consensus on the issue. Mandating RTP/RTCP
> > multiplexing for the unicast burst make it simpler and faster to start.
> >
> > Note the two ports may still be used for the retransmission case.
> >
> > Roni
> >
> >
> >
> > > -----Original Message-----
> > > From: Zeev Vax [mailto:zeevvax@microsoft.com]
> > > Sent: Wednesday, June 17, 2009 7:45 PM
> > > To: Bill Ver Steeg (versteb); Ali C. Begen (abegen); VAN CAENEGEM Tom=
;
> > > Roni Even; avt@ietf.org
> > > Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-
> > > acquisition-for-rtp-01
> > >
> > > The text proposal looks fine to me.
> > > I don't think we should mandate support both, this would cause extra
> > > work in implementation of a solution, and I can't see any benefit.
> > > Giving that this is UDP traffic port muxing is a subset of separate
> > > ports, so we can mandate port muxing, and make optional the separate
> > > ports.
> > >
> > > Zeev
> > >
> > >
> > > -----Original Message-----
> > > From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> > > Sent: Wednesday, June 17, 2009 8:40 AM
> > > To: Ali C. Begen (abegen); VAN CAENEGEM Tom; Roni Even; avt@ietf.org;
> > > Zeev Vax
> > > Subject: RE: [AVT] comments on section10ofdraft-ietf-avt-rapid-
> > > acquisition-for-rtp-01
> > >
> > > Tom-
> > >
> > > These words looks good to me as well, with the following clarificatio=
n.
> > >
> > > We do need to consider how we handle RTP/RTCP port muxing throughout
> > > the
> > > document, and make the wording consistent wherever we reference the
> > > ports in use. I am in favor of allowing (but not mandating) the RR to
> > > signal RTP/RTCP port muxing. This would require the RS to support bot=
h
> > > methods. This is just my opinion, and we need to come to consensus on
> > > this matter.
> > >
> > >
> > > Bill VerSteeg
> > >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> > > Ali C. Begen (abegen)
> > > Sent: Wednesday, June 17, 2009 10:15 AM
> > > To: VAN CAENEGEM Tom; Roni Even; avt@ietf.org
> > > Subject: Re: [AVT] comments on
> > > section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > >
> > > The proposed text looks good to me. We should probably put the burst
> > > and
> > > retransmission sources in the same block in Figure 2 as well.
> > >
> > > -acbegen
> > >
> > >
> > > > -----Original Message-----
> > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf =
Of
> > > > VAN CAENEGEM Tom
> > > > Sent: Wednesday, June 17, 2009 5:23 AM
> > > > To: Roni Even; avt@ietf.org
> > > > Subject: Re: [AVT] comments on section
> > > > 10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > > >
> > > >
> > > >  Hi Roni,
> > > >
> > > > Perhaps the start of section 6.2 can be rewritten as follows:
> > > >
> > > >
> > > > <START>
> > > >
> > > > 6.2.  Message Flows
> > > >
> > > >    Figure 2 shows the main entities involved in rapid acquisition:
> > > >
> > > >    o  Multicast Source
> > > >
> > > >    o  Feedback Target (FT)
> > > >
> > > >    o  Burst/ Retransmission Source
> > > >
> > > >    o  RTP Receiver (RR)
> > > >
> > > > (fig 2)
> > > >
> > > >
> > > > The feedback target (FT) is the entity as defined in [rtcpssm draft=
],
> > > > to which the RR sends its RTCP FB messages, indicating packet loss =
in
> > > > the ssm primary stream by means of a NACK or indicating the RR's
> > > > desire to have rapid acquisition of the ssm primary stream (by mean=
s
> > > > of an RTCP FB message as defined in this document). While the
> > > > burst/retransmission source is responsible for responding on these
> > > > messages and, in the case of rapid acquisition, further RTCP
> > > > interaction with the RR during this acquisition process, it is
> > > assumed
> > >
> > > > in the remainder of the document that these two logical entities (F=
T
> > > > and burst/retransmission source) are combined in a single physical
> > > > entity and share state. In the remainder of the text, the term
> > > > retransmission server is used whenever appropriate, to refer to the
> > > > combined functionality of the FT and retransmission/burst source.
> > > > However, it must be noted that only the FT is involved in the prima=
ry
> > > > ssm RTP session, whereas the burst/retransmission source transmits
> > > > unicast RTP burst and RTP retransmissions packets (both formatted  =
as
> > > > RTP retransmission packets
> > > > [RFC4585]) in a single separate unicast RTP retransmission session =
to
> > > > each RR.
> > > >
> > > > Note also that the same method (with the identical message flows)
> > > > would also apply in a scenario where rapid acquisition is performed
> > > by
> > >
> > > > a feedback target co-located with the media source.
> > > >
> > > > (...)
> > > >
> > > > <END>
> > > >
> > > > Tom: As we mandate the retransmission source and burst source to be
> > > in
> > >
> > > > the same session, I think it is no longer required to split-up amon=
g
> > > > these two logical entities. I invite other people, including the
> > > > co-authors to comment on this new text proposal.
> > > >
> > > > With respect to your comments on the RTP/RTCP port muxing support
> > > > indication by the RR inside the RAMS-R message. That would be neede=
d,
> > > > but is not sufficient as, if only declarative SDP is used, and we
> > > want
> > >
> > > > to have the possibility that the RTP/RTCP packets in the
> > > > retransmission session can be received by the RR on the same port t=
he
> > > > RR issues the RTCP RAMS-R, we need also a way by which the RR can
> > > > signal this too. We provided a possible solution in the draft, but =
I
> > > > understood that you think such a solution should be proposed in a
> > > separate draft proposal?
> > > > But I guess that would also apply then to the signaling of support
> > > for
> > >
> > > > RTP/RTCP port muxing by the RR?
> > > >
> > > > Tom
> > > >
> > > > -----Original Message-----
> > > > From: Roni Even [mailto:Even.roni@huawei.com]
> > > > Sent: woensdag 17 juni 2009 13:24
> > > > To: VAN CAENEGEM Tom; avt@ietf.org
> > > > Subject: RE: [AVT] comments on section 10
> > > > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > > >
> > > > Tom,
> > > > I understand the RAMS-R and RAMS-T, the text is not clear enough in
> > > > section
> > > > 6.2
> > > >
> > > > It still leaves open the issue of the addresses for the RR in the
> > > case
> > >
> > > > of declarative SDP when there is no answer SDP from the RR.
> > > >
> > > > About RTP/RTCP multiplexing, the declarative SDP can show that the =
RS
> > > > supports it and I still think that some information about the
> > > > addressing (like support for RTP/RTCP mux) should be supplied in th=
e
> > > > RAMS-R for the declarative case.
> > > >
> > > > Roni
> > > >
> > > > > -----Original Message-----
> > > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behal=
f
> > > > > Of VAN CAENEGEM Tom
> > > > > Sent: Wednesday, June 17, 2009 11:17 AM
> > > > > To: avt@ietf.org
> > > > > Subject: Re: [AVT] comments on section 10 of draft-ietf-avt-rapid=
-
> > > > > acquisition-for-rtp-01
> > > > >
> > > > > Hi Roni,
> > > > >
> > > > > I think your understanding was indeed different from the general
> > > > >assumptions in this draft. Previously we agreed to only consider t=
he
> > > > >case where there is only one physical entity involved (called the
> > > > >Retransmission Server in the draft), which allows us to NOT consid=
er
> > > > >and  discuss cases where for instance the feedback target (which i=
s
> > > > >defined  in the rtcpssm draft/RFC) is not in the same box as the
> > > > >retransmission  source or burst source, the entities sourcing
> > > > >retransmision/burst  packets. In that case we then would also need
> > > to
> > >
> > > > >describe how these  separate entities communicate.
> > > > > The fact that these different entities are now in the same box do=
es
> > > > >not  necessarily mean that all interactions and data exchange with
> > > > >the RRs  is  part of the same RTP session, which is in this case t=
he
> > > > >SSM RTP  session.
> > > > > As Ali explained, the NACK and RAMS-R RTCP FB messages are direct=
ed
> > > > >to
> > > >
> > > > >the FB target, where we do not  defer from the rtcpssm draft. The
> > > RTP
> > >
> > > > >retransmission/burst packets that are sent as a response to the NA=
CK
> > > > >and  the RAMS-R can be either session multiplexed with respect to
> > > the
> > >
> > > > >original SSM RTP session or SSRC muxed (same session), following R=
FC
> > > > >4588.
> > > > >As the retransmission packets in this case are addressing the RR  =
in
> > > > >unicast, we obviously have a dedicated RTP session for the
> > > > >retransmission/burst packets. We had some internal discussion on
> > > > >whether  considering the use case of having a separate session
> > > > >between RS and RR  for RTP retransmission packets triggered by an
> > > > >RTCP FB NACK and a  separate session for RTP burst packets trigger=
ed
> > > > >by an RTCP RAMS-R made  sense, but we ended up agreeing that
> > > allowing
> > >
> > > > >a single session was the  easiest way out, without imposing seriou=
s
> > > > >limitations to the general  architecture.
> > > > >
> > > > > This means that the ports used by the (single) RTP
> > > > > retransmission/burst session are in principle decoupled from the
> > > > > primary SSM session. Hence if an RR wants to receive the
> > > > > burst/retransmission packets and associated RTCP messages on the
> > > > > same port the RR sent out the RTCP RAMS-R/ NACK FB messages, this
> > > > > should either be signaled by the RR, OR such port usage scheme is
> > > > > considered the "default" case -which also means the RR supports
> > > > > RTP/RTCP port muxing for the retransmission/burst session-, and
> > > then
> > >
> > > > > the RR needs to
> > > >
> > > > > signal the ports for receiving the RTP and RTCP packets in the
> > > > > retransmission session when it requires dedicated ports.
> > > > >
> > > > > The RAMS-I (RS-> RR) and RAMS-T (RR-> RS) messages are only
> > > relevant
> > >
> > > > > to a specific RR requesting the RTP burst stream and the RS, and
> > > > > carry
> > > >
> > > > > information/signaling related to the retransmission/burst session
> > > > > and have nothing to do with the SSM session. Hence the FB target =
as
> > > > > logical entity is not involved here.
> > > > >
> > > > > I hope this clarifies rather than it contributes to your confusio=
n.
> > > > > But we may need to rephrase the part you quoted, as your
> > > > > interpretation was different from its intended meaning. We also
> > > > > tried to be more explicit in which session which RAMS or other RT=
CP
> > > (e.g.
> > > > > Bye) messages needed to be exchanged compared to a previous versi=
on
> > > > > of
> > > >
> > > > > the draft, but we are open of course to any other suggestions fro=
m
> > > > > your side if this is not clear enough in your opinion.
> > > > >
> > > > > Tom
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > " A Retransmission Source may equally act as a Burst Source.  The
> > > > >    Retransmission Source may also incorporate the Feedback Target
> > > > >    ([I-D.ietf-avt-rtcpssm] permits the feedback target to be a
> > > > >    retransmission server, since it is a logical function to which
> > > RRs
> > > > >    send their unicast feedback), and we will use the term
> > > > > Retransmission
> > > > >    Server (RS) in the remainder of the document to refer to a
> > > single
> > > > >    physical entity comprising these three entities that share
> > > state.
> > > > >    Note that the same method (with the identical message flows)
> > > would
> > > > >    also apply in a scenario where rapid acquisition is performed =
by
> > > a
> > > > >    feedback target co-located with the media source."
> > > > >
> > > > > I assumed that we are only dealing with the case that the RS is a
> > > > > single entity and not three different entities with different
> > > > > addresses
> > > > >
> > > > > I also thought that this was agreed in previous discussions
> > > > >
> > > > > If my understanding is not correct I will review the draft since
> > > the
> > >
> > > > > current text is not explicit enough to specify which part is doin=
g
> > > > > each message. I saw that RAMS-R is going to feedback target but
> > > > > RAMS-T
> > > >
> > > > > is going to RS which is not specifying a specific address accordi=
ng
> > > > > to
> > > >
> > > > > you.
> > > > >
> > > > > Roni
> > > > >
> > > > > -----Original Message-----
> > > > > From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> > > > > Sent: Tuesday, June 16, 2009 10:00 PM
> > > > > To: Roni Even; avt@ietf.org
> > > > > Subject: RE: [AVT] comments on section 10
> > > > > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > > > >
> > > > > Remember that the RAMS-R (RR->RS) message is NOT on the
> > > > > retransmission
> > > > > (unicast) session, it's on the primary session since it is sent t=
o
> > > > > the
> > > >
> > > > > feedback target of the primary SSM session. Thus, the source port
> > > RR
> > >
> > > > > uses to send RAMS-R "cannot" be assumed to be the destination por=
t
> > > > > it wishes to receive the unicast burst on.
> > > > >
> > > > > If you agree with this statement, it is clear why we need port
> > > > > signaling.
> > > > > Muxing will not help much here. It will just reduce the number of
> > > > > signaled ports from 2 to 1.
> > > > >
> > > > > -acbegen
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > > Behalf
> > >
> > > > > > Of Roni
> > > > > Even
> > > > > > Sent: Tuesday, June 16, 2009 10:08 AM
> > > > > > To: avt@ietf.org
> > > > > > Subject: [AVT] comments on section 10
> > > > > ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I looked at section 10 and have some comments
> > > > > >
> > > > > >
> > > > > >
> > > > > > 1.       If RTP/RTCP multiplexing is used, there is no need for
> > > any
> > > > > specific operation
> > > > > > from the RR side. The RR sends the RAMS-R message to the RS fro=
m
> > > > > > the
> > > >
> > > > > > port
> > > > > it wants to
> > > > > > receive the RAMS-I and RTP payload. The RS just sends the
> > > > > > information to
> > > > > the port from
> > > > > > which it received the RAMS-R and not to the one in the SDP
> > > > > >
> > > > > > 2.       In the case where there is no RTP/RTCP multiplexing, t=
he
> > > > > RAMS-R
> > > > > RTCP message will
> > > > > > go to the RS and the RAMS-I will go to the port on the RR from
> > > > > > where
> > > >
> > > > > > the
> > > > > RAMS-R was
> > > > > > received. For the RTP, the RR does not know if it has a NAT on
> > > the
> > > > > way
> > > > >
> > > > > > to
> > > > > the RS and
> > > > > > should try to get a routable address (using STUN for example) a=
nd
> > > > > providing the port to
> > > > > > the RS ( we still need to agree on how to do it)
> > > > > >
> > > > > > 3.       If the above two points are correct than the RR receiv=
e
> > > > port
> > > > > in
> > > > > the SDP is not
> > > > > > really useful
> > > > > >
> > > > > >
> > > > > >
> > > > > > Roni Even
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Audio/Video Transport Working Group
> > > > > avt@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/avt
> > > >
> > > > _______________________________________________
> > > > Audio/Video Transport Working Group
> > > > avt@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/avt
> > > _______________________________________________
> > > Audio/Video Transport Working Group
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
> >
>



From Tom.Van_Caenegem@alcatel-lucent.be  Fri Jun 19 03:40:27 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 48A3A3A6A08 for <avt@core3.amsl.com>; Fri, 19 Jun 2009 03:40:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.749
X-Spam-Level: 
X-Spam-Status: No, score=-5.749 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, HELO_EQ_FR=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 iMU1t82M4F4F for <avt@core3.amsl.com>; Fri, 19 Jun 2009 03:40:26 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [62.23.212.57]) by core3.amsl.com (Postfix) with ESMTP id B61F53A69E9 for <avt@ietf.org>; Fri, 19 Jun 2009 03:40:25 -0700 (PDT)
Received: from FRVELSBHS06.ad2.ad.alcatel.com (frvelsbhs06.dc-m.alcatel-lucent.com [155.132.6.78]) by smail2.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5JAdYiv002025;  Fri, 19 Jun 2009 12:40:32 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.53]) by FRVELSBHS06.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 19 Jun 2009 12:40:21 +0200
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: Fri, 19 Jun 2009 12:40:20 +0200
Message-ID: <238382595265324EA50F6134BB42DCAF0408CFA0@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D54098D8C33@xmb-sjc-215.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Some comments on " Multicast Acquisition Report Block Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-01)
Thread-Index: AcnwH3wb2QndKgItQv2Gbyp/65/cCAACF+jgACdSdNA=
References: <238382595265324EA50F6134BB42DCAF0408CAE6@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D8C33@xmb-sjc-215.amer.cisco.com>
From: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>
To: "Ali C. Begen (abegen)" <abegen@cisco.com>, <avt@ietf.org>
X-OriginalArrivalTime: 19 Jun 2009 10:40:21.0747 (UTC) FILETIME=[589C5430:01C9F0CA]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.80
Subject: Re: [AVT] Some comments on " Multicast Acquisition Report Block Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-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, 19 Jun 2009 10:40:27 -0000

Hi Ali,

Look for "TOM" ...

-----Original Message-----
From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]=20
Sent: donderdag 18 juni 2009 17:34
To: VAN CAENEGEM Tom; avt@ietf.org
Subject: RE: [AVT] Some comments on " Multicast Acquisition Report Block
Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-01)

Hi Tom,

Thanks for reading the draft.

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of=20
> VAN CAENEGEM Tom
> Sent: Thursday, June 18, 2009 7:17 AM
> To: avt@ietf.org
> Subject: [AVT] Some comments on " Multicast Acquisition Report Block
Typefor RTCP XR"
> (draft-begen-avt-rapid-sync-rtcp-xr-01)
>=20
> Hi Ali,
>=20
> I have a few comments/questions related to the draft:
>=20
> Comment 1:  The abstract now has a sentence: "For quality reporting,=20
> monitoring and diagnostics purposes, it is important to collect=20
> detailed information from the RTP receivers about their acquisition
experiences."  Doesn't it go beyond "RTP (receivers)"
> and "acquisition" as you also define e.g. a TLV related to=20
> presentation time delay (sometimes the MC RTP delivered content may
not even be displayed) and application delay.
> I have no problem with the definition of such fields, but IMO it makes

> sense to make this clear in the abstract.

I am not sure what else I can use instead of "RTP receivers" as I don't
wanna specifically say decoders, set-tops, etc. Instead of "acquisition
experiences", maybe we can call it "acquisition and presentation
experiences"?

Would that help?

"TOM" : OK
=20
> Comment 2: Base Report
>=20
> The only informational field here is "response". It is still not=20
> defined, but you refer to the response code in RAMS draft (e.g.
"success", etc).

I believe using the same codes will make it more useful.

"TOM" : OK, but most codes only apply to a rapid acquisition process, so
it makes sense to indicate additionally whether "normal" or "rapid"
acquisition was initiated by the receiver (that is an additional flag)
=20
> I guess it is not possible to signal to an RR which additional info to

> send, i.e which TLV fields to use...From that point of view, would it=20
> not make sense to have some basic information -now defined in some TLV

> fields in the base report- that is always present, to

By always present, you mean "mandatory"? If yes, we indeed need to
decide which ones.

"TOM" : indeed mandatory : when by means of declarative SDP, the RTP
receivers are instructed to send RTCP XR with multicast acquisition
report blocks, AND RTP recievers support these XR messages, these fields
are always there.

> enhance interoperability. I know we need to find the right balance=20
> between useful information reporting ,  bandwidth efficiency, and
receiver reporting capabilities.
>=20
> Candidate fields that could be inside this fixed base report are:
> -flag/field indicating whether the report refers to a normal=20
> acquisition (based on SFGMP) or rapid MC RTP acquisition (or rather =20
> the intention by the RR to perform  a rapid
> acquisition) for instance by means of RAMS

One reason behind this base report vs extensions separation was to be
able to handle other rapid multicast acquisition methods. So, IMO, if we
will have to make something mandatory, it should not relate to a
specific method. It is true that I am heavily considering RAMS in
designing this report, but it just works for other methods, if they
become interested in supporting this report.

Will this flag/field be able to specify which method was used? Or will
it simply specify whether it was a rapid or normal acquisition?

"TOM" : for a 1-bit flag, that should be the latter : normal or rapid
(in whatever way). Alternatively considering a multiple bit field (e.g.
3 bits) where e.g. 001 =3D normal aquisition, 002 =3D RAMS, and all =
other
codes unspecified at this stage looks to me a good solution as well...

> -a response code which you have indeed defined and its interpretation=20
> should be dependent on the previously mentioned flag/field

So, the flag/field above will indeed specify which method was use to
make RR rapidly acquire the content. Yes/no?

"TOM" : see above

=20
> -initial launched request (either 1st RAMS-R for rapid acquisition,=20
> either 1st IGMP-join in case of normal acquisition) to 1st received=20
> RTP packet (always a multicast packet for normal acquisition and=20
> "normally" a burst packet when a rapid acquisition process was
> involved) delta time
>=20
> -application request to initial launched request (either 1st RAMS-R=20
> for rapid acquisition, either 1st IGMP-join in case of normal=20
> acquisition) delta time
>=20
> For these last two fields, a value must be specified that would=20
> indicate that the field is not filled out (because the receiver client
implementation may not support it).

Oh, then these fields are not mandatory since the client has the option
to leave them blank. Then, I would recommend leaving the current report
as it is, but we can use a stronger language (like "SHOULD/RECOMMENDED")
for some of the fields (like the ones you have above) to promote
interoperability.=20

Would you be OK with that?

"TOM" : the reason to have the field in the base report, is to make sure
that a minimum of information is conveyed back to the server/feedback
target. Otherwise, as all TLV fields are optional, how can a server
indicate to a client which TLV fields it is interested in and which ones
not?  The proposed fields I selected/defined are those that provide
useful information  for both a normal and RAMS process, but there may be
other fields equally appropriate to be always present.   Whether we need
an RTP receiver to mandate to fill out these fields (with the right
value) is a separate discussion, IMO.
=20
> There could still be other fields that apply to both acquisition=20
> processes and fit in the base report, but they should be application=20
> independent (e.g. delta to presentation time is clearly app dependent)

Agree, application dependent fields are optional and should stay so.

T,
-acbegen

>=20
> Regards
> Tom


From csp@csperkins.org  Fri Jun 19 08:45:49 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 842873A6828 for <avt@core3.amsl.com>; Fri, 19 Jun 2009 08:45:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, 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 pMOlJe1iJerf for <avt@core3.amsl.com>; Fri, 19 Jun 2009 08:45:48 -0700 (PDT)
Received: from lon1-msapost-1.mail.demon.net (lon1-msapost-1.mail.demon.net [195.173.77.180]) by core3.amsl.com (Postfix) with ESMTP id 93F853A6AD8 for <avt@ietf.org>; Fri, 19 Jun 2009 08:45:48 -0700 (PDT)
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]) by lon1-post-1.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1MHgHx-0002Iv-Xb; Fri, 19 Jun 2009 15:46:01 +0000
Message-Id: <4A818261-E11E-4634-8E0B-E6989DB72F1C@csperkins.org>
From: Colin Perkins <csp@csperkins.org>
To: Emil Ivov <emcho@sip-communicator.org>
In-Reply-To: <4A365C1E.6030803@sip-communicator.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 19 Jun 2009 16:46:01 +0100
References: <4A365C1E.6030803@sip-communicator.org>
X-Mailer: Apple Mail (2.935.3)
Cc: "Audio/Video Transport \(AVT\) WG" <avt@ietf.org>
Subject: Re: [AVT] Sound Level Indicators
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, 19 Jun 2009 15:45:49 -0000

On 15 Jun 2009, at 15:35, Emil Ivov wrote:
> We have just submitted the following draft:
>
> http://www.ietf.org/internet-drafts/draft-ivov-avt-slic-00.txt
>
> The draft proposes a solution for a problem that's been extensively
> discussed on the dispatch mailing list during the past few weeks. It
> concerned a means of transporting sound level in conferences in a way
> that would allow presenting it to the user and extending the active
> speaker concept.


I haven't been following dispatch, but this looks like a good use of  
the RTP header extension mechanism.

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




From alan.d.clark@telchemy.com  Fri Jun 19 09:09:18 2009
Return-Path: <alan.d.clark@telchemy.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 0EE7D3A6A17 for <avt@core3.amsl.com>; Fri, 19 Jun 2009 09:09:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rI3m-UTyOXb8 for <avt@core3.amsl.com>; Fri, 19 Jun 2009 09:09:17 -0700 (PDT)
Received: from mail01.netplexity.net (mail01.netplexity.net [66.129.85.135]) by core3.amsl.com (Postfix) with ESMTP id 34C3A3A6832 for <avt@ietf.org>; Fri, 19 Jun 2009 09:09:17 -0700 (PDT)
Received: from UnknownHost [97.67.102.65] by mail01.netplexity.net with SMTP;  Fri, 19 Jun 2009 12:08:59 -0400
User-Agent: Microsoft-Entourage/12.14.0.081024
Date: Fri, 19 Jun 2009 12:08:51 -0400
From: Alan Clark <alan.d.clark@telchemy.com>
To: Colin Perkins <csp@csperkins.org>, Emil Ivov <emcho@sip-communicator.org>
Message-ID: <C6613053.8349%alan.d.clark@telchemy.com>
Thread-Topic: [AVT] Sound Level Indicators
Thread-Index: Acnw+Dw90X0cz4wLFE+Yk4m4W7udlw==
In-Reply-To: <4A818261-E11E-4634-8E0B-E6989DB72F1C@csperkins.org>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: Org <avt@ietf.org>
Subject: Re: [AVT] Sound Level Indicators
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, 19 Jun 2009 16:09:18 -0000

A parallel problem is the control (rather than indication) of volume and
noise suppression in VoIP calls.  911 operators find that sometimes they do
want noise suppression and sometimes they don't.  Noise suppression can be
helpful when they are trying to understand a caller in a noisy background
environment however it can also suppress background noises that can help to
understand the emergency situation (e.g. if they hearing kids laughing in
the background the call may be a prank (which does happen quite frequently)
but other sounds may indicate how serious a problem is or provide location
information).

Alan



On 6/19/09 11:46 AM, "Colin Perkins" <csp@csperkins.org> wrote:

> On 15 Jun 2009, at 15:35, Emil Ivov wrote:
>> We have just submitted the following draft:
>> 
>> http://www.ietf.org/internet-drafts/draft-ivov-avt-slic-00.txt
>> 
>> The draft proposes a solution for a problem that's been extensively
>> discussed on the dispatch mailing list during the past few weeks. It
>> concerned a means of transporting sound level in conferences in a way
>> that would allow presenting it to the user and extending the active
>> speaker concept.
> 
> 
> I haven't been following dispatch, but this looks like a good use of
> the RTP header extension mechanism.




From abegen@cisco.com  Fri Jun 19 10:45:12 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 0ABB13A6A58 for <avt@core3.amsl.com>; Fri, 19 Jun 2009 10:45:12 -0700 (PDT)
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 3z9d6cKa-WDy for <avt@core3.amsl.com>; Fri, 19 Jun 2009 10:45:10 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id B82A23A68D9 for <avt@ietf.org>; Fri, 19 Jun 2009 10:45:10 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,254,1243814400"; d="scan'208";a="202722838"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-1.cisco.com with ESMTP; 19 Jun 2009 17:45:24 +0000
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n5JHjOOx016203;  Fri, 19 Jun 2009 10:45:24 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id n5JHjO8r022034; Fri, 19 Jun 2009 17:45:24 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 19 Jun 2009 10:45:24 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 19 Jun 2009 10:43:57 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540995C22C@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <238382595265324EA50F6134BB42DCAF0408CFA0@FRVELSMBS22.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Some comments on " Multicast Acquisition Report Block Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-01)
Thread-Index: AcnwH3wb2QndKgItQv2Gbyp/65/cCAACF+jgACdSdNAADh0+sA==
References: <238382595265324EA50F6134BB42DCAF0408CAE6@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D8C33@xmb-sjc-215.amer.cisco.com> <238382595265324EA50F6134BB42DCAF0408CFA0@FRVELSMBS22.ad2.ad.alcatel.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>, <avt@ietf.org>
X-OriginalArrivalTime: 19 Jun 2009 17:45:24.0026 (UTC) FILETIME=[B92749A0:01C9F105]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=7224; t=1245433524; x=1246297524; c=relaxed/simple; s=sjdkim3002; 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]=20Some=20comments=20on=20=22=20Mu lticast=20Acquisition=20Report=20Block=20Typefor=20RTCP=20XR =22=20(draft-begen-avt-rapid-sync-rtcp-xr-01) |Sender:=20; bh=mKnrY6LZNntywaEJwlQWLj5rcRktSTZHfyOVKnPliS8=; b=Ha6QS4l4A1TzSUY7mvHO7UlcuDV3h0U1nL7jNsFtHP548EtNPawqvtBu16 aJEJIlOTtpGaG2vnKQLHX+BmoY+fKrv/Wc7XaBupLe3h6UGswQMpSfUwrfa+ JLi2KtYnya;
Authentication-Results: sj-dkim-3; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Subject: Re: [AVT] Some comments on " Multicast Acquisition Report Block Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-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, 19 Jun 2009 17:45:12 -0000

Hi Tom,

I just feel that mandating some fields but not requiring the receivers =
to fill them in is not a good solution. As I mentioned earlier, I'd =
prefer using a stronger language than "optional" but I prefer not to =
mandate such fields.=20

Any other opinions?

-acbegen

> -----Original Message-----
> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> Sent: Friday, June 19, 2009 3:40 AM
> To: Ali C. Begen (abegen); avt@ietf.org
> Subject: RE: [AVT] Some comments on " Multicast Acquisition Report =
Block Typefor RTCP XR"
> (draft-begen-avt-rapid-sync-rtcp-xr-01)
>=20
> Hi Ali,
>=20
> Look for "TOM" ...
>=20
> -----Original Message-----
> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> Sent: donderdag 18 juni 2009 17:34
> To: VAN CAENEGEM Tom; avt@ietf.org
> Subject: RE: [AVT] Some comments on " Multicast Acquisition Report =
Block
> Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-01)
>=20
> Hi Tom,
>=20
> Thanks for reading the draft.
>=20
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf =
Of
> > VAN CAENEGEM Tom
> > Sent: Thursday, June 18, 2009 7:17 AM
> > To: avt@ietf.org
> > Subject: [AVT] Some comments on " Multicast Acquisition Report Block
> Typefor RTCP XR"
> > (draft-begen-avt-rapid-sync-rtcp-xr-01)
> >
> > Hi Ali,
> >
> > I have a few comments/questions related to the draft:
> >
> > Comment 1:  The abstract now has a sentence: "For quality reporting,
> > monitoring and diagnostics purposes, it is important to collect
> > detailed information from the RTP receivers about their acquisition
> experiences."  Doesn't it go beyond "RTP (receivers)"
> > and "acquisition" as you also define e.g. a TLV related to
> > presentation time delay (sometimes the MC RTP delivered content may
> not even be displayed) and application delay.
> > I have no problem with the definition of such fields, but IMO it =
makes
>=20
> > sense to make this clear in the abstract.
>=20
> I am not sure what else I can use instead of "RTP receivers" as I =
don't
> wanna specifically say decoders, set-tops, etc. Instead of =
"acquisition
> experiences", maybe we can call it "acquisition and presentation
> experiences"?
>=20
> Would that help?
>=20
> "TOM" : OK
>=20
> > Comment 2: Base Report
> >
> > The only informational field here is "response". It is still not
> > defined, but you refer to the response code in RAMS draft (e.g.
> "success", etc).
>=20
> I believe using the same codes will make it more useful.
>=20
> "TOM" : OK, but most codes only apply to a rapid acquisition process, =
so
> it makes sense to indicate additionally whether "normal" or "rapid"
> acquisition was initiated by the receiver (that is an additional flag)
>=20
> > I guess it is not possible to signal to an RR which additional info =
to
>=20
> > send, i.e which TLV fields to use...From that point of view, would =
it
> > not make sense to have some basic information -now defined in some =
TLV
>=20
> > fields in the base report- that is always present, to
>=20
> By always present, you mean "mandatory"? If yes, we indeed need to
> decide which ones.
>=20
> "TOM" : indeed mandatory : when by means of declarative SDP, the RTP
> receivers are instructed to send RTCP XR with multicast acquisition
> report blocks, AND RTP recievers support these XR messages, these =
fields
> are always there.
>=20
> > enhance interoperability. I know we need to find the right balance
> > between useful information reporting ,  bandwidth efficiency, and
> receiver reporting capabilities.
> >
> > Candidate fields that could be inside this fixed base report are:
> > -flag/field indicating whether the report refers to a normal
> > acquisition (based on SFGMP) or rapid MC RTP acquisition (or rather
> > the intention by the RR to perform  a rapid
> > acquisition) for instance by means of RAMS
>=20
> One reason behind this base report vs extensions separation was to be
> able to handle other rapid multicast acquisition methods. So, IMO, if =
we
> will have to make something mandatory, it should not relate to a
> specific method. It is true that I am heavily considering RAMS in
> designing this report, but it just works for other methods, if they
> become interested in supporting this report.
>=20
> Will this flag/field be able to specify which method was used? Or will
> it simply specify whether it was a rapid or normal acquisition?
>=20
> "TOM" : for a 1-bit flag, that should be the latter : normal or rapid
> (in whatever way). Alternatively considering a multiple bit field =
(e.g.
> 3 bits) where e.g. 001 =3D normal aquisition, 002 =3D RAMS, and all =
other
> codes unspecified at this stage looks to me a good solution as well...
>=20
> > -a response code which you have indeed defined and its =
interpretation
> > should be dependent on the previously mentioned flag/field
>=20
> So, the flag/field above will indeed specify which method was use to
> make RR rapidly acquire the content. Yes/no?
>=20
> "TOM" : see above
>=20
>=20
> > -initial launched request (either 1st RAMS-R for rapid acquisition,
> > either 1st IGMP-join in case of normal acquisition) to 1st received
> > RTP packet (always a multicast packet for normal acquisition and
> > "normally" a burst packet when a rapid acquisition process was
> > involved) delta time
> >
> > -application request to initial launched request (either 1st RAMS-R
> > for rapid acquisition, either 1st IGMP-join in case of normal
> > acquisition) delta time
> >
> > For these last two fields, a value must be specified that would
> > indicate that the field is not filled out (because the receiver =
client
> implementation may not support it).
>=20
> Oh, then these fields are not mandatory since the client has the =
option
> to leave them blank. Then, I would recommend leaving the current =
report
> as it is, but we can use a stronger language (like =
"SHOULD/RECOMMENDED")
> for some of the fields (like the ones you have above) to promote
> interoperability.
>=20
> Would you be OK with that?
>=20
> "TOM" : the reason to have the field in the base report, is to make =
sure
> that a minimum of information is conveyed back to the server/feedback
> target. Otherwise, as all TLV fields are optional, how can a server
> indicate to a client which TLV fields it is interested in and which =
ones
> not?  The proposed fields I selected/defined are those that provide
> useful information  for both a normal and RAMS process, but there may =
be
> other fields equally appropriate to be always present.   Whether we =
need
> an RTP receiver to mandate to fill out these fields (with the right
> value) is a separate discussion, IMO.
>=20
> > There could still be other fields that apply to both acquisition
> > processes and fit in the base report, but they should be application
> > independent (e.g. delta to presentation time is clearly app =
dependent)
>=20
> Agree, application dependent fields are optional and should stay so.
>=20
> T,
> -acbegen
>=20
> >
> > Regards
> > Tom


From efriedri@cisco.com  Fri Jun 19 11:00:39 2009
Return-Path: <efriedri@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 428E63A6A22 for <avt@core3.amsl.com>; Fri, 19 Jun 2009 11:00:39 -0700 (PDT)
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 vWQNRhjSaAET for <avt@core3.amsl.com>; Fri, 19 Jun 2009 11:00:37 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 7A1EF3A67A3 for <avt@ietf.org>; Fri, 19 Jun 2009 11:00:37 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,254,1243814400"; d="scan'208";a="47967622"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 19 Jun 2009 18:00:50 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n5JI0oRe005034;  Fri, 19 Jun 2009 14:00:50 -0400
Received: from dhcp-161-44-173-248.cisco.com (dhcp-161-44-173-248.cisco.com [161.44.173.248]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n5JI0nXr020726; Fri, 19 Jun 2009 18:00:49 GMT
Message-Id: <63BA849C-3FC0-4733-A831-46ACE02FB348@cisco.com>
From: efriedri <efriedri@cisco.com>
To: "Ali C. Begen (abegen)" <abegen@cisco.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D540995C22C@xmb-sjc-215.amer.cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 19 Jun 2009 14:00:52 -0400
References: <238382595265324EA50F6134BB42DCAF0408CAE6@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D8C33@xmb-sjc-215.amer.cisco.com> <238382595265324EA50F6134BB42DCAF0408CFA0@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D540995C22C@xmb-sjc-215.amer.cisco.com>
X-Mailer: Apple Mail (2.935.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=8097; t=1245434450; x=1246298450; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=efriedri@cisco.com; z=From:=20efriedri=20<efriedri@cisco.com> |Subject:=20Re=3A=20[AVT]=20Some=20comments=20on=20=22=20Mu lticast=20Acquisition=20Report=20Block=20Typefor=20RTCP=20XR =22=20(draft-begen-avt-rapid-sync-rtcp-xr-01) |Sender:=20 |To:=20=22Ali=20C.=20Begen=20(abegen)=22=20<abegen@cisco.co m>; bh=4emCT1IDYmSm6S4FRvx5KrnaOqu+FB5aRUN35Jgz9H0=; b=KPWNQuBjwRMB1aDNSYNHVpC2nzNR1nhq+sbJyfhTxrJ2x2KqB+LToWNha5 /B9QpY3rI+PD6UBL04k/5ODNwziNSCNlU6+wk5CZWBMkjnJ0zNsDip1NL70L 49AcmqCf7/;
Authentication-Results: rtp-dkim-1; header.From=efriedri@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; ); 
Cc: VAN CAENEGEM Tom <Tom.Van_Caenegem@alcatel-lucent.be>, avt@ietf.org
Subject: Re: [AVT] Some comments on " Multicast Acquisition Report Block Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-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, 19 Jun 2009 18:00:39 -0000

Ali, Tom-
   I think it would be useful to provide some small base set of fields  
that are required for any MA report. They should be fields that do not  
require any special instrumentation on the RTP Receiver and apply to  
RAMS and non-RAMS acquisitions. Looking over our proposed fields, I'd  
like to suggest that "First Multicast Extended Seq Number" and "SFGMP  
Join Time" be required fields. They would provide a small but useful  
amount of information in cases where receivers do not support the  
other fields.

Thanks,
Eric

On Jun 19, 2009, at 1:43 PM, Ali C. Begen (abegen) wrote:

> Hi Tom,
>
> I just feel that mandating some fields but not requiring the  
> receivers to fill them in is not a good solution. As I mentioned  
> earlier, I'd prefer using a stronger language than "optional" but I  
> prefer not to mandate such fields.
>
> Any other opinions?
>
> -acbegen
>
>> -----Original Message-----
>> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
>> Sent: Friday, June 19, 2009 3:40 AM
>> To: Ali C. Begen (abegen); avt@ietf.org
>> Subject: RE: [AVT] Some comments on " Multicast Acquisition Report  
>> Block Typefor RTCP XR"
>> (draft-begen-avt-rapid-sync-rtcp-xr-01)
>>
>> Hi Ali,
>>
>> Look for "TOM" ...
>>
>> -----Original Message-----
>> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
>> Sent: donderdag 18 juni 2009 17:34
>> To: VAN CAENEGEM Tom; avt@ietf.org
>> Subject: RE: [AVT] Some comments on " Multicast Acquisition Report  
>> Block
>> Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-01)
>>
>> Hi Tom,
>>
>> Thanks for reading the draft.
>>
>>> -----Original Message-----
>>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf  
>>> Of
>>> VAN CAENEGEM Tom
>>> Sent: Thursday, June 18, 2009 7:17 AM
>>> To: avt@ietf.org
>>> Subject: [AVT] Some comments on " Multicast Acquisition Report Block
>> Typefor RTCP XR"
>>> (draft-begen-avt-rapid-sync-rtcp-xr-01)
>>>
>>> Hi Ali,
>>>
>>> I have a few comments/questions related to the draft:
>>>
>>> Comment 1:  The abstract now has a sentence: "For quality reporting,
>>> monitoring and diagnostics purposes, it is important to collect
>>> detailed information from the RTP receivers about their acquisition
>> experiences."  Doesn't it go beyond "RTP (receivers)"
>>> and "acquisition" as you also define e.g. a TLV related to
>>> presentation time delay (sometimes the MC RTP delivered content may
>> not even be displayed) and application delay.
>>> I have no problem with the definition of such fields, but IMO it  
>>> makes
>>
>>> sense to make this clear in the abstract.
>>
>> I am not sure what else I can use instead of "RTP receivers" as I  
>> don't
>> wanna specifically say decoders, set-tops, etc. Instead of  
>> "acquisition
>> experiences", maybe we can call it "acquisition and presentation
>> experiences"?
>>
>> Would that help?
>>
>> "TOM" : OK
>>
>>> Comment 2: Base Report
>>>
>>> The only informational field here is "response". It is still not
>>> defined, but you refer to the response code in RAMS draft (e.g.
>> "success", etc).
>>
>> I believe using the same codes will make it more useful.
>>
>> "TOM" : OK, but most codes only apply to a rapid acquisition  
>> process, so
>> it makes sense to indicate additionally whether "normal" or "rapid"
>> acquisition was initiated by the receiver (that is an additional  
>> flag)
>>
>>> I guess it is not possible to signal to an RR which additional  
>>> info to
>>
>>> send, i.e which TLV fields to use...From that point of view, would  
>>> it
>>> not make sense to have some basic information -now defined in some  
>>> TLV
>>
>>> fields in the base report- that is always present, to
>>
>> By always present, you mean "mandatory"? If yes, we indeed need to
>> decide which ones.
>>
>> "TOM" : indeed mandatory : when by means of declarative SDP, the RTP
>> receivers are instructed to send RTCP XR with multicast acquisition
>> report blocks, AND RTP recievers support these XR messages, these  
>> fields
>> are always there.
>>
>>> enhance interoperability. I know we need to find the right balance
>>> between useful information reporting ,  bandwidth efficiency, and
>> receiver reporting capabilities.
>>>
>>> Candidate fields that could be inside this fixed base report are:
>>> -flag/field indicating whether the report refers to a normal
>>> acquisition (based on SFGMP) or rapid MC RTP acquisition (or rather
>>> the intention by the RR to perform  a rapid
>>> acquisition) for instance by means of RAMS
>>
>> One reason behind this base report vs extensions separation was to be
>> able to handle other rapid multicast acquisition methods. So, IMO,  
>> if we
>> will have to make something mandatory, it should not relate to a
>> specific method. It is true that I am heavily considering RAMS in
>> designing this report, but it just works for other methods, if they
>> become interested in supporting this report.
>>
>> Will this flag/field be able to specify which method was used? Or  
>> will
>> it simply specify whether it was a rapid or normal acquisition?
>>
>> "TOM" : for a 1-bit flag, that should be the latter : normal or rapid
>> (in whatever way). Alternatively considering a multiple bit field  
>> (e.g.
>> 3 bits) where e.g. 001 = normal aquisition, 002 = RAMS, and all other
>> codes unspecified at this stage looks to me a good solution as  
>> well...
>>
>>> -a response code which you have indeed defined and its  
>>> interpretation
>>> should be dependent on the previously mentioned flag/field
>>
>> So, the flag/field above will indeed specify which method was use to
>> make RR rapidly acquire the content. Yes/no?
>>
>> "TOM" : see above
>>
>>
>>> -initial launched request (either 1st RAMS-R for rapid acquisition,
>>> either 1st IGMP-join in case of normal acquisition) to 1st received
>>> RTP packet (always a multicast packet for normal acquisition and
>>> "normally" a burst packet when a rapid acquisition process was
>>> involved) delta time
>>>
>>> -application request to initial launched request (either 1st RAMS-R
>>> for rapid acquisition, either 1st IGMP-join in case of normal
>>> acquisition) delta time
>>>
>>> For these last two fields, a value must be specified that would
>>> indicate that the field is not filled out (because the receiver  
>>> client
>> implementation may not support it).
>>
>> Oh, then these fields are not mandatory since the client has the  
>> option
>> to leave them blank. Then, I would recommend leaving the current  
>> report
>> as it is, but we can use a stronger language (like "SHOULD/ 
>> RECOMMENDED")
>> for some of the fields (like the ones you have above) to promote
>> interoperability.
>>
>> Would you be OK with that?
>>
>> "TOM" : the reason to have the field in the base report, is to make  
>> sure
>> that a minimum of information is conveyed back to the server/feedback
>> target. Otherwise, as all TLV fields are optional, how can a server
>> indicate to a client which TLV fields it is interested in and which  
>> ones
>> not?  The proposed fields I selected/defined are those that provide
>> useful information  for both a normal and RAMS process, but there  
>> may be
>> other fields equally appropriate to be always present.   Whether we  
>> need
>> an RTP receiver to mandate to fill out these fields (with the right
>> value) is a separate discussion, IMO.
>>
>>> There could still be other fields that apply to both acquisition
>>> processes and fit in the base report, but they should be application
>>> independent (e.g. delta to presentation time is clearly app  
>>> dependent)
>>
>> Agree, application dependent fields are optional and should stay so.
>>
>> T,
>> -acbegen
>>
>>>
>>> Regards
>>> Tom
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From abegen@cisco.com  Fri Jun 19 15:07:21 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 4F3303A6C1A for <avt@core3.amsl.com>; Fri, 19 Jun 2009 15:07:21 -0700 (PDT)
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 e-P-vMDetSCd for <avt@core3.amsl.com>; Fri, 19 Jun 2009 15:07:19 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id CE0123A6828 for <avt@ietf.org>; Fri, 19 Jun 2009 15:07:19 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,256,1243814400"; d="scan'208";a="202849364"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-1.cisco.com with ESMTP; 19 Jun 2009 22:07:32 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n5JM7XdI012389;  Fri, 19 Jun 2009 15:07:33 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n5JM7Xew021421; Fri, 19 Jun 2009 22:07:33 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.3959);  Fri, 19 Jun 2009 15:07:33 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 19 Jun 2009 15:07:09 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540995C3DF@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <63BA849C-3FC0-4733-A831-46ACE02FB348@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Some comments on " Multicast Acquisition Report Block Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-01)
Thread-Index: AcnxB+ZTSpmPIRTQTtqRFSxt0v9qZAAILfjQ
References: <238382595265324EA50F6134BB42DCAF0408CAE6@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D8C33@xmb-sjc-215.amer.cisco.com> <238382595265324EA50F6134BB42DCAF0408CFA0@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D540995C22C@xmb-sjc-215.amer.cisco.com> <63BA849C-3FC0-4733-A831-46ACE02FB348@cisco.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Eric Friedrich (efriedri)" <efriedri@cisco.com>
X-OriginalArrivalTime: 19 Jun 2009 22:07:33.0222 (UTC) FILETIME=[587C2060:01C9F12A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=9780; t=1245449253; x=1246313253; c=relaxed/simple; s=sjdkim2002; 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]=20Some=20comments=20on=20=22=20Mu lticast=20Acquisition=20Report=20Block=20Typefor=20RTCP=20XR =22=20(draft-begen-avt-rapid-sync-rtcp-xr-01) |Sender:=20; bh=fqi/4DDjwcn1jBuvkjG/f66WadFcWTjTP3+oP+J5osU=; b=mpTscLzJfJgOhWjqxKlNRVMYN4up5tBKel+uGRfVknsdfHFUToVnICuNVJ xmDe1xQCWnLizmuKH3QIwuuUZ+7sN0X2v0ZhveaKFOMBsQdWLQwgWmlLt+M1 +sOGrc4PG3;
Authentication-Results: sj-dkim-2; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: VAN CAENEGEM Tom <Tom.Van_Caenegem@alcatel-lucent.be>, avt@ietf.org
Subject: Re: [AVT] Some comments on " Multicast Acquisition Report Block Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-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, 19 Jun 2009 22:07:21 -0000

Join time and first mcast seqnum would be common to all scenarios. =
However, what if that information is not available, meaning that the =
receiver could not join, i.e., could not receive anything at all from =
the multicast session? In that case, those fields should not exist. =
Using magical numbers is not a good idea.

So, I suggest the following: If join was successful (so at least one =
mcast packet was received), these two fields MUST (not may or should) be =
included in the report. If join was not successful, these fields SHALL =
NOT exist.

This should address Tom's concerns except that this report will not say =
much whether acceleration was requested or not (or if yes, which method =
was requested). I think we can use one of the status codes (we have 256 =
of them anyway) to indicate this. Or, we can separate a block to =
indicate the individual acceleration methods.

How does this sound?

-acbegen

> -----Original Message-----
> From: Eric Friedrich (efriedri)
> Sent: Friday, June 19, 2009 11:01 AM
> To: Ali C. Begen (abegen)
> Cc: VAN CAENEGEM Tom; avt@ietf.org
> Subject: Re: [AVT] Some comments on " Multicast Acquisition Report =
Block Typefor RTCP XR"
> (draft-begen-avt-rapid-sync-rtcp-xr-01)
>=20
> Ali, Tom-
>    I think it would be useful to provide some small base set of fields
> that are required for any MA report. They should be fields that do not
> require any special instrumentation on the RTP Receiver and apply to
> RAMS and non-RAMS acquisitions. Looking over our proposed fields, I'd
> like to suggest that "First Multicast Extended Seq Number" and "SFGMP
> Join Time" be required fields. They would provide a small but useful
> amount of information in cases where receivers do not support the
> other fields.
>=20
> Thanks,
> Eric
>=20
> On Jun 19, 2009, at 1:43 PM, Ali C. Begen (abegen) wrote:
>=20
> > Hi Tom,
> >
> > I just feel that mandating some fields but not requiring the
> > receivers to fill them in is not a good solution. As I mentioned
> > earlier, I'd prefer using a stronger language than "optional" but I
> > prefer not to mandate such fields.
> >
> > Any other opinions?
> >
> > -acbegen
> >
> >> -----Original Message-----
> >> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> >> Sent: Friday, June 19, 2009 3:40 AM
> >> To: Ali C. Begen (abegen); avt@ietf.org
> >> Subject: RE: [AVT] Some comments on " Multicast Acquisition Report
> >> Block Typefor RTCP XR"
> >> (draft-begen-avt-rapid-sync-rtcp-xr-01)
> >>
> >> Hi Ali,
> >>
> >> Look for "TOM" ...
> >>
> >> -----Original Message-----
> >> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> >> Sent: donderdag 18 juni 2009 17:34
> >> To: VAN CAENEGEM Tom; avt@ietf.org
> >> Subject: RE: [AVT] Some comments on " Multicast Acquisition Report
> >> Block
> >> Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-01)
> >>
> >> Hi Tom,
> >>
> >> Thanks for reading the draft.
> >>
> >>> -----Original Message-----
> >>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
> >>> Of
> >>> VAN CAENEGEM Tom
> >>> Sent: Thursday, June 18, 2009 7:17 AM
> >>> To: avt@ietf.org
> >>> Subject: [AVT] Some comments on " Multicast Acquisition Report =
Block
> >> Typefor RTCP XR"
> >>> (draft-begen-avt-rapid-sync-rtcp-xr-01)
> >>>
> >>> Hi Ali,
> >>>
> >>> I have a few comments/questions related to the draft:
> >>>
> >>> Comment 1:  The abstract now has a sentence: "For quality =
reporting,
> >>> monitoring and diagnostics purposes, it is important to collect
> >>> detailed information from the RTP receivers about their =
acquisition
> >> experiences."  Doesn't it go beyond "RTP (receivers)"
> >>> and "acquisition" as you also define e.g. a TLV related to
> >>> presentation time delay (sometimes the MC RTP delivered content =
may
> >> not even be displayed) and application delay.
> >>> I have no problem with the definition of such fields, but IMO it
> >>> makes
> >>
> >>> sense to make this clear in the abstract.
> >>
> >> I am not sure what else I can use instead of "RTP receivers" as I
> >> don't
> >> wanna specifically say decoders, set-tops, etc. Instead of
> >> "acquisition
> >> experiences", maybe we can call it "acquisition and presentation
> >> experiences"?
> >>
> >> Would that help?
> >>
> >> "TOM" : OK
> >>
> >>> Comment 2: Base Report
> >>>
> >>> The only informational field here is "response". It is still not
> >>> defined, but you refer to the response code in RAMS draft (e.g.
> >> "success", etc).
> >>
> >> I believe using the same codes will make it more useful.
> >>
> >> "TOM" : OK, but most codes only apply to a rapid acquisition
> >> process, so
> >> it makes sense to indicate additionally whether "normal" or "rapid"
> >> acquisition was initiated by the receiver (that is an additional
> >> flag)
> >>
> >>> I guess it is not possible to signal to an RR which additional
> >>> info to
> >>
> >>> send, i.e which TLV fields to use...From that point of view, would
> >>> it
> >>> not make sense to have some basic information -now defined in some
> >>> TLV
> >>
> >>> fields in the base report- that is always present, to
> >>
> >> By always present, you mean "mandatory"? If yes, we indeed need to
> >> decide which ones.
> >>
> >> "TOM" : indeed mandatory : when by means of declarative SDP, the =
RTP
> >> receivers are instructed to send RTCP XR with multicast acquisition
> >> report blocks, AND RTP recievers support these XR messages, these
> >> fields
> >> are always there.
> >>
> >>> enhance interoperability. I know we need to find the right balance
> >>> between useful information reporting ,  bandwidth efficiency, and
> >> receiver reporting capabilities.
> >>>
> >>> Candidate fields that could be inside this fixed base report are:
> >>> -flag/field indicating whether the report refers to a normal
> >>> acquisition (based on SFGMP) or rapid MC RTP acquisition (or =
rather
> >>> the intention by the RR to perform  a rapid
> >>> acquisition) for instance by means of RAMS
> >>
> >> One reason behind this base report vs extensions separation was to =
be
> >> able to handle other rapid multicast acquisition methods. So, IMO,
> >> if we
> >> will have to make something mandatory, it should not relate to a
> >> specific method. It is true that I am heavily considering RAMS in
> >> designing this report, but it just works for other methods, if they
> >> become interested in supporting this report.
> >>
> >> Will this flag/field be able to specify which method was used? Or
> >> will
> >> it simply specify whether it was a rapid or normal acquisition?
> >>
> >> "TOM" : for a 1-bit flag, that should be the latter : normal or =
rapid
> >> (in whatever way). Alternatively considering a multiple bit field
> >> (e.g.
> >> 3 bits) where e.g. 001 =3D normal aquisition, 002 =3D RAMS, and all =
other
> >> codes unspecified at this stage looks to me a good solution as
> >> well...
> >>
> >>> -a response code which you have indeed defined and its
> >>> interpretation
> >>> should be dependent on the previously mentioned flag/field
> >>
> >> So, the flag/field above will indeed specify which method was use =
to
> >> make RR rapidly acquire the content. Yes/no?
> >>
> >> "TOM" : see above
> >>
> >>
> >>> -initial launched request (either 1st RAMS-R for rapid =
acquisition,
> >>> either 1st IGMP-join in case of normal acquisition) to 1st =
received
> >>> RTP packet (always a multicast packet for normal acquisition and
> >>> "normally" a burst packet when a rapid acquisition process was
> >>> involved) delta time
> >>>
> >>> -application request to initial launched request (either 1st =
RAMS-R
> >>> for rapid acquisition, either 1st IGMP-join in case of normal
> >>> acquisition) delta time
> >>>
> >>> For these last two fields, a value must be specified that would
> >>> indicate that the field is not filled out (because the receiver
> >>> client
> >> implementation may not support it).
> >>
> >> Oh, then these fields are not mandatory since the client has the
> >> option
> >> to leave them blank. Then, I would recommend leaving the current
> >> report
> >> as it is, but we can use a stronger language (like "SHOULD/
> >> RECOMMENDED")
> >> for some of the fields (like the ones you have above) to promote
> >> interoperability.
> >>
> >> Would you be OK with that?
> >>
> >> "TOM" : the reason to have the field in the base report, is to make
> >> sure
> >> that a minimum of information is conveyed back to the =
server/feedback
> >> target. Otherwise, as all TLV fields are optional, how can a server
> >> indicate to a client which TLV fields it is interested in and which
> >> ones
> >> not?  The proposed fields I selected/defined are those that provide
> >> useful information  for both a normal and RAMS process, but there
> >> may be
> >> other fields equally appropriate to be always present.   Whether we
> >> need
> >> an RTP receiver to mandate to fill out these fields (with the right
> >> value) is a separate discussion, IMO.
> >>
> >>> There could still be other fields that apply to both acquisition
> >>> processes and fit in the base report, but they should be =
application
> >>> independent (e.g. delta to presentation time is clearly app
> >>> dependent)
> >>
> >> Agree, application dependent fields are optional and should stay =
so.
> >>
> >> T,
> >> -acbegen
> >>
> >>>
> >>> Regards
> >>> Tom
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt


From abegen@cisco.com  Fri Jun 19 15:09:15 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 85EA13A6AA1 for <avt@core3.amsl.com>; Fri, 19 Jun 2009 15:09:15 -0700 (PDT)
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 MrKGcuSVvccW for <avt@core3.amsl.com>; Fri, 19 Jun 2009 15:09:14 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id C34493A6828 for <avt@ietf.org>; Fri, 19 Jun 2009 15:09:14 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,256,1243814400"; d="scan'208";a="327695417"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 19 Jun 2009 22:09:28 +0000
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n5JM9S9R020152;  Fri, 19 Jun 2009 15:09:28 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id n5JM9SRC017808; Fri, 19 Jun 2009 22:09:28 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.3959);  Fri, 19 Jun 2009 15:09:28 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 19 Jun 2009 15:09:20 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540995C3E1@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <025301c9eff9$cbc5c1c0$63514540$%roni@huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] comments on section 10 ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAslt0gAAsYx0A=
References: <mailman.10085.1245185397.4936.avt@ietf.org><238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com><015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com><238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <025301c9eff9$cbc5c1c0$63514540$%roni@huawei.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Roni Even" <Even.roni@huawei.com>, "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>, <avt@ietf.org>
X-OriginalArrivalTime: 19 Jun 2009 22:09:28.0187 (UTC) FILETIME=[9D0264B0:01C9F12A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1473; t=1245449368; x=1246313368; c=relaxed/simple; s=sjdkim3002; 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]=20comments=20on=20section=2010=20 ofdraft-ietf-avt-rapid-acquisition-for-rtp-01 |Sender:=20; bh=ruS7F2HcQ9FTFcYq0fbBfzwDcUVns/mzWKZwbS3Ipfc=; b=gw8usyjN9ihBZEeJaNLLqZtbsECmpb0FSsQpwMvtgU7sZxGD1F254crj5Z 2bP9jImKHdWFscp3bLDDwbHJjk08YHwoQ9HnZJno/gUnn5SR4w2S6Xsw20ld a8Rin4L5Ue;
Authentication-Results: sj-dkim-3; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Subject: Re: [AVT] comments on section 10 ofdraft-ietf-avt-rapid-acquisition-for-rtp-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, 19 Jun 2009 22:09:15 -0000

Roni, Tom,

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of =
Roni Even
> Sent: Thursday, June 18, 2009 2:47 AM
> To: 'VAN CAENEGEM Tom'; avt@ietf.org
> Subject: Re: [AVT] comments on section 10 =
ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
> Hi Tom,
> My comment about the text was more about the steps described later in
> section 6.2
>=20
> In step 2 the RS will send the RAMS-I from the RTCP port for the
> burst/retransmission stream. This will help the RR to learn his =
address

Does not RR already know the RTCP port and IP of the RS from the SDP? =
Are you considering a case where e.g., RS is behind a NAT?
=20
> In step 4 - update RAM-R, will it be sent to the FT target or to the
> burst/retransmission.

Yes, this should be clarified. I agree with Tom that the updated RAMS-R =
should go to the FT as the first RAMS-R. We will add this to the next =
version.

=20
> In step 8 - specify where to send the RAMS-T not to the RS but to the
> burst/retransmission address.

I would propose an alternative text to Tom's suggestion:

"Note that RR MUST send at least one RAMS-T message (if an RTCP BYE =
message has not been issued yet as described in step 9), and the RAMS-T =
message MUST be addressed to the RTCP port of the retransmission =
session."

In other words, if a BYE has already been issued, there is no need for =
RAMS-T. Agree with this?

-acbegen


From yekuiwang@huawei.com  Sat Jun 20 14:12:45 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 CA5623A6B44 for <avt@core3.amsl.com>; Sat, 20 Jun 2009 14:12:45 -0700 (PDT)
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 jb0hXW2Q0omv for <avt@core3.amsl.com>; Sat, 20 Jun 2009 14:12:44 -0700 (PDT)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id 75A063A697B for <avt@ietf.org>; Sat, 20 Jun 2009 14:12:44 -0700 (PDT)
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 <0KLK00M4R2XKGI@usaga02-in.huawei.com> for avt@ietf.org; Sat, 20 Jun 2009 14:12:56 -0700 (PDT)
Received: from W90946 ([10.45.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KLK00J3W2X80P@usaga02-in.huawei.com> for avt@ietf.org; Sat, 20 Jun 2009 14:12:54 -0700 (PDT)
Date: Sat, 20 Jun 2009 17:12:41 -0400
From: Ye-Kui Wang <yekuiwang@huawei.com>
In-reply-to: <04CAD96D4C5A3D48B1919248A8FE0D54098D8893@xmb-sjc-215.amer.cisco.com>
To: "'Ali C. Begen (abegen)'" <abegen@cisco.com>, 'Colin Perkins' <csp@csperkins.org>, 'Michael A Dolan' <md.1@newtbt.com>
Message-id: <7EDDBBF20F36462DB056D44C00A29CA4@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: AcnvdQqqNMxMU9aMQXWzfTUZTZeOBwABKQRQAJxKJvA=
References: <20090309171502.518513A6359@core3.amsl.com> <4A6ACB13-0CBB-4DA7-84AD-28CDE56DB4C3@csperkins.org> <0MKpCa-1LoLs525qX-000cvA@mrelay.perfora.net> <49D1C793.9050409@hhi.fraunhofer.de> <0MKp8S-1Lof8c1LTC-000fjs@mrelay.perfora.net> <49D4AE9D.8060905@hhi.fraunhofer.de> <0MKpCa-1MEnZO1ysE-000d6S@mrelay.perfora.net> <4A323DC5.5020004@hhi.fraunhofer.de> <0MKpCa-1MGbjS2vGp-000cit@mrelay.perfora.net> <C0A963AC-4B17-49FC-904C-44A43DF0B8D7@csperkins.org> <0MKpCa-1MGfai3tWQ-000d7b@mrelay.perfora.net> <B5806023-20A3-4868-9195-7FA0D4D62053@csperkins.org> <04CAD96D4C5A3D48B1919248A8FE0D54098D8893@xmb-sjc-215.amer.cisco.com>
Cc: avt@ietf.org
Subject: Re: [AVT] Fwd: I-D  Action:draft-perkins-avt-rapid-rtp-sync-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: Sat, 20 Jun 2009 21:12:45 -0000

> Have you considered sending an SR as a part of the unicast 
> burst (or RAMS-I message that describes the burst) that we 
> provide for rapid acquisition? We may end up sending an SR 
> this way since it will be required for figuring out the 
> extended seqnums.
> 

And the SR herein can also help the RR to fastly establish a-v sync.
However, I think there is no need to make the SR part of the RAMS-I message
(i.e. to change the RAMS-I syntax to include the information the SR
carries), as you can use a compound RTCP packet to include both the RAMS-I
and the SR. Of course you may meant for this.

BR, YK

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On 
> Behalf Of Ali C. Begen (abegen)
> Sent: Wednesday, June 17, 2009 2:36 PM
> To: Colin Perkins; Michael A Dolan
> Cc: avt@ietf.org
> Subject: Re: [AVT] Fwd: I-D 
> Action:draft-perkins-avt-rapid-rtp-sync-03.txt
> 
> Hi Colin,
> 
> > Okay, that's what I thought you meant. That certainly 
> affects the join 
> > times, although I'm not sure I'd call that issue synchronisation 
> > latency. We can certainly add some wording to highlight it though.
> 
> That is part of something we call "acquisition delay" and 
> this problem is addressed in a separate draft:
> http://tools.ietf.org/id/draft-ietf-avt-rapid-acquisition-for-
> rtp-01.txt
> 
>  
> > 	Co-locating in time the RTCP SR packets with their 
> related access 
> > points further improves the sync time.  For example, if the IDR is 
> > every 2 seconds, there is no benefit (for syncing) to 
> sending the RTCP 
> > SR more frequently than that, especially if it is aligned with this 
> > access point in time.  If the RTCP SR packets are sent randomly in 
> > time, the sync time is the IDR period plus 1/2 the RTCP SR packet 
> > period, on average. This is more of an optimization, but 
> then, that's what this whole draft is about - optimizing the 
> sync time.
> > 
> > 
> > 
> > I agree that co-locating the SR information in time with the random 
> > access points helps, and will add something to the draft to 
> say that 
> > explicitly if it's not already there. I disagree that's sufficient: 
> > sending the SR information more frequently gives the receiver more 
> > samples from which to estimate any skew between NTP and RTP 
> timestamps, and gives more information to help filter out any 
> incorrect mappings.
> 
> Have you considered sending an SR as a part of the unicast 
> burst (or RAMS-I message that describes the burst) that we 
> provide for rapid acquisition? We may end up sending an SR 
> this way since it will be required for figuring out the 
> extended seqnums.
> 
> -acbegen
> 
> 
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On 
> Behalf Of 
> > Colin Perkins
> > Sent: Wednesday, June 17, 2009 10:57 AM
> > To: Michael A Dolan
> > Cc: avt@ietf.org
> > Subject: Re: [AVT] Fwd: I-D 
> > Action:draft-perkins-avt-rapid-rtp-sync-03.txt
> > 
> > Michael,
> > 
> > On 16 Jun 2009, at 21:27, Michael A Dolan wrote:
> > 
> > 	FYI, I started out in March with a number of comments, 
> some related 
> > to multicast UDLR with 1-2 links and I sense that's too big 
> a topic to 
> > try and add at this point.  My comments therefore have distilled to 
> > addressing two major factors in syncing RTP sessions that I believe 
> > overshadow the time resolutions being discussed in the 
> draft, and therefore it is an omission not to address them:
> > 
> > 	1. Common timebase
> > 	2. Media-specific access points
> > 
> > 	I stopped short of suggesting we should design 
> anything. Therefore I 
> > still believe both topics belong here, and in this draft, 
> and they are 
> > not so big as to defer at this point.
> > 
> > 	For clarification, I wasn't proposing we define a 
> timebase signaling 
> > mechanism (although I do think that's a good idea).  All I am 
> > proposing is to add some text that explains that a common 
> timebase is 
> > needed to achieve anything near the implied sync times discussed in 
> > this draft. How the senders and receivers figure that out is out of 
> > band. But if they don't and just go along with "wallclock", 
> it makes much of the rest of this draft irrelevant since the 
> timebase error will be huge by comparison.
> > 
> > 
> > 
> > That's already stated in RFC 3550. I'm not sure it needs repeating 
> > here, but can add something if you want.
> > 
> > 
> > 	Regarding the issue about access points, I'm not sure how much 
> > background to add, so apologies if this is obvious to 
> everyone. Every 
> > media stream type has "access points" that arrive 
> periodically - the 
> > point where a decoder can begin to decode the stream. In general, 
> > these are a function of the encoding, not constant per 
> type, and not constant per stream. For example in H.264, 
> these typically center around the presence of an IDR frame.
> > HE AAC has a simpler coding structure, but one still can't start 
> > decoding anywhere in the stream.  The "typical" periods of 
> the H.264 
> > access points range from 0.5 to 2 seconds, depending on the 
> coding.  The exact period is application dependent, but is 
> not relevant.
> > The point is that these periods greatly exceed the times 
> shown in the 
> > tables which are implied to be the sync times - going as 
> low as 0.04 
> > seconds.  The tables in this draft suggesting that RTCP SR 
> packets be 
> > sent 0.04 seconds apart for high rate streams. This is 
> interesting (as 
> > Thomas notes) for jitter management and clock settling, but 
> that high 
> > rate does not help you sync since you can't even start 
> decoding the video for a relatively long time after the 0.04 
> seconds. This is mostly related to issues of late joiners of course.
> > Therefore, I was suggesting we make note of this fact to 
> clarify there 
> > are other factors to sync and acquisition beyond receipt of NTP and 
> > the RTCP SR packet, and that these other times far exceed 
> 0.04 seconds.
> > 
> > 
> > 
> > Okay, that's what I thought you meant. That certainly 
> affects the join 
> > times, although I'm not sure I'd call that issue synchronisation 
> > latency. We can certainly add some wording to highlight it though.
> > 
> > 
> > 	Co-locating in time the RTCP SR packets with their 
> related access 
> > points further improves the sync time.  For example, if the IDR is 
> > every 2 seconds, there is no benefit (for syncing) to 
> sending the RTCP 
> > SR more frequently than that, especially if it is aligned with this 
> > access point in time.  If the RTCP SR packets are sent randomly in 
> > time, the sync time is the IDR period plus 1/2 the RTCP SR packet 
> > period, on average. This is more of an optimization, but 
> then, that's what this whole draft is about - optimizing the 
> sync time.
> > 
> > 
> > 
> > I agree that co-locating the SR information in time with the random 
> > access points helps, and will add something to the draft to 
> say that 
> > explicitly if it's not already there. I disagree that's sufficient: 
> > sending the SR information more frequently gives the receiver more 
> > samples from which to estimate any skew between NTP and RTP 
> timestamps, and gives more information to help filter out any 
> incorrect mappings.
> > 
> > --
> > Colin Perkins
> > http://csperkins.org/
> > 
> > 
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
> 



From abegen@cisco.com  Sat Jun 20 14:21:48 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 E26673A6A42 for <avt@core3.amsl.com>; Sat, 20 Jun 2009 14:21:48 -0700 (PDT)
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 ZmCUDIgx68sD for <avt@core3.amsl.com>; Sat, 20 Jun 2009 14:21:47 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 5CDCE3A697B for <avt@ietf.org>; Sat, 20 Jun 2009 14:21:47 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,260,1243814400"; d="scan'208";a="81950534"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-5.cisco.com with ESMTP; 20 Jun 2009 21:22:01 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n5KLM1XP032300;  Sat, 20 Jun 2009 14:22:01 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n5KLM1iU028952; Sat, 20 Jun 2009 21:22:01 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Sat, 20 Jun 2009 14:22:01 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 20 Jun 2009 14:21:59 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540995C50C@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <7EDDBBF20F36462DB056D44C00A29CA4@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Fwd: I-D  Action:draft-perkins-avt-rapid-rtp-sync-03.txt
Thread-Index: AcnvdQqqNMxMU9aMQXWzfTUZTZeOBwABKQRQAJxKJvAAAI5LEA==
References: <20090309171502.518513A6359@core3.amsl.com> <4A6ACB13-0CBB-4DA7-84AD-28CDE56DB4C3@csperkins.org> <0MKpCa-1LoLs525qX-000cvA@mrelay.perfora.net> <49D1C793.9050409@hhi.fraunhofer.de> <0MKp8S-1Lof8c1LTC-000fjs@mrelay.perfora.net> <49D4AE9D.8060905@hhi.fraunhofer.de> <0MKpCa-1MEnZO1ysE-000d6S@mrelay.perfora.net> <4A323DC5.5020004@hhi.fraunhofer.de> <0MKpCa-1MGbjS2vGp-000cit@mrelay.perfora.net> <C0A963AC-4B17-49FC-904C-44A43DF0B8D7@csperkins.org> <0MKpCa-1MGfai3tWQ-000d7b@mrelay.perfora.net> <B5806023-20A3-4868-9195-7FA0D4D62053@csperkins.org> <04CAD96D4C5A3D48B1919248A8FE0D54098D8893@xmb-sjc-215.amer.cisco.com> <7EDDBBF20F36462DB056D44C00A29CA4@china.huawei.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Ye-Kui Wang" <yekuiwang@huawei.com>, "Colin Perkins" <csp@csperkins.org>,  "Michael A Dolan" <md.1@newtbt.com>
X-OriginalArrivalTime: 20 Jun 2009 21:22:01.0387 (UTC) FILETIME=[2698EFB0:01C9F1ED]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=8415; t=1245532921; x=1246396921; c=relaxed/simple; s=sjdkim2002; 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]=20Fwd=3A=20I-D=20=20Action=3Adraf t-perkins-avt-rapid-rtp-sync-03.txt |Sender:=20; bh=zTdDRbLLcxzZXuFk7slqujIiOH9IsRSwMCzXrW7chHU=; b=OPEZFKjAWl2ho/F9tDUhNGQScDmo7criPLagwQzNfS0TS0EMzH3IWFUE// K+nC1e4GzXXO9g3+AbXo6f73a+g1CJjCumNHorLNDGka2mBdOZJ+NIjZwO9C Rx8FMwDDr6;
Authentication-Results: sj-dkim-2; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: avt@ietf.org
Subject: Re: [AVT] Fwd: I-D  Action:draft-perkins-avt-rapid-rtp-sync-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: Sat, 20 Jun 2009 21:21:49 -0000

> -----Original Message-----
> From: Ye-Kui Wang [mailto:yekuiwang@huawei.com]
> Sent: Saturday, June 20, 2009 2:13 PM
> To: Ali C. Begen (abegen); 'Colin Perkins'; 'Michael A Dolan'
> Cc: avt@ietf.org
> Subject: RE: [AVT] Fwd: I-D =
Action:draft-perkins-avt-rapid-rtp-sync-03.txt
>=20
>=20
> > Have you considered sending an SR as a part of the unicast
> > burst (or RAMS-I message that describes the burst) that we
> > provide for rapid acquisition? We may end up sending an SR
> > this way since it will be required for figuring out the
> > extended seqnums.
> >
>=20
> And the SR herein can also help the RR to fastly establish a-v sync.
> However, I think there is no need to make the SR part of the RAMS-I =
message
> (i.e. to change the RAMS-I syntax to include the information the SR
> carries), as you can use a compound RTCP packet to include both the =
RAMS-I
> and the SR. Of course you may meant for this.

Yep, no need to change the RAMS-I format. I meant compound packet.

-acbegen

=20
> BR, YK
>=20
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > Behalf Of Ali C. Begen (abegen)
> > Sent: Wednesday, June 17, 2009 2:36 PM
> > To: Colin Perkins; Michael A Dolan
> > Cc: avt@ietf.org
> > Subject: Re: [AVT] Fwd: I-D
> > Action:draft-perkins-avt-rapid-rtp-sync-03.txt
> >
> > Hi Colin,
> >
> > > Okay, that's what I thought you meant. That certainly
> > affects the join
> > > times, although I'm not sure I'd call that issue synchronisation
> > > latency. We can certainly add some wording to highlight it though.
> >
> > That is part of something we call "acquisition delay" and
> > this problem is addressed in a separate draft:
> > http://tools.ietf.org/id/draft-ietf-avt-rapid-acquisition-for-
> > rtp-01.txt
> >
> >
> > > 	Co-locating in time the RTCP SR packets with their
> > related access
> > > points further improves the sync time.  For example, if the IDR is
> > > every 2 seconds, there is no benefit (for syncing) to
> > sending the RTCP
> > > SR more frequently than that, especially if it is aligned with =
this
> > > access point in time.  If the RTCP SR packets are sent randomly in
> > > time, the sync time is the IDR period plus 1/2 the RTCP SR packet
> > > period, on average. This is more of an optimization, but
> > then, that's what this whole draft is about - optimizing the
> > sync time.
> > >
> > >
> > >
> > > I agree that co-locating the SR information in time with the =
random
> > > access points helps, and will add something to the draft to
> > say that
> > > explicitly if it's not already there. I disagree that's =
sufficient:
> > > sending the SR information more frequently gives the receiver more
> > > samples from which to estimate any skew between NTP and RTP
> > timestamps, and gives more information to help filter out any
> > incorrect mappings.
> >
> > Have you considered sending an SR as a part of the unicast
> > burst (or RAMS-I message that describes the burst) that we
> > provide for rapid acquisition? We may end up sending an SR
> > this way since it will be required for figuring out the
> > extended seqnums.
> >
> > -acbegen
> >
> >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > Behalf Of
> > > Colin Perkins
> > > Sent: Wednesday, June 17, 2009 10:57 AM
> > > To: Michael A Dolan
> > > Cc: avt@ietf.org
> > > Subject: Re: [AVT] Fwd: I-D
> > > Action:draft-perkins-avt-rapid-rtp-sync-03.txt
> > >
> > > Michael,
> > >
> > > On 16 Jun 2009, at 21:27, Michael A Dolan wrote:
> > >
> > > 	FYI, I started out in March with a number of comments,
> > some related
> > > to multicast UDLR with 1-2 links and I sense that's too big
> > a topic to
> > > try and add at this point.  My comments therefore have distilled =
to
> > > addressing two major factors in syncing RTP sessions that I =
believe
> > > overshadow the time resolutions being discussed in the
> > draft, and therefore it is an omission not to address them:
> > >
> > > 	1. Common timebase
> > > 	2. Media-specific access points
> > >
> > > 	I stopped short of suggesting we should design
> > anything. Therefore I
> > > still believe both topics belong here, and in this draft,
> > and they are
> > > not so big as to defer at this point.
> > >
> > > 	For clarification, I wasn't proposing we define a
> > timebase signaling
> > > mechanism (although I do think that's a good idea).  All I am
> > > proposing is to add some text that explains that a common
> > timebase is
> > > needed to achieve anything near the implied sync times discussed =
in
> > > this draft. How the senders and receivers figure that out is out =
of
> > > band. But if they don't and just go along with "wallclock",
> > it makes much of the rest of this draft irrelevant since the
> > timebase error will be huge by comparison.
> > >
> > >
> > >
> > > That's already stated in RFC 3550. I'm not sure it needs repeating
> > > here, but can add something if you want.
> > >
> > >
> > > 	Regarding the issue about access points, I'm not sure how much
> > > background to add, so apologies if this is obvious to
> > everyone. Every
> > > media stream type has "access points" that arrive
> > periodically - the
> > > point where a decoder can begin to decode the stream. In general,
> > > these are a function of the encoding, not constant per
> > type, and not constant per stream. For example in H.264,
> > these typically center around the presence of an IDR frame.
> > > HE AAC has a simpler coding structure, but one still can't start
> > > decoding anywhere in the stream.  The "typical" periods of
> > the H.264
> > > access points range from 0.5 to 2 seconds, depending on the
> > coding.  The exact period is application dependent, but is
> > not relevant.
> > > The point is that these periods greatly exceed the times
> > shown in the
> > > tables which are implied to be the sync times - going as
> > low as 0.04
> > > seconds.  The tables in this draft suggesting that RTCP SR
> > packets be
> > > sent 0.04 seconds apart for high rate streams. This is
> > interesting (as
> > > Thomas notes) for jitter management and clock settling, but
> > that high
> > > rate does not help you sync since you can't even start
> > decoding the video for a relatively long time after the 0.04
> > seconds. This is mostly related to issues of late joiners of course.
> > > Therefore, I was suggesting we make note of this fact to
> > clarify there
> > > are other factors to sync and acquisition beyond receipt of NTP =
and
> > > the RTCP SR packet, and that these other times far exceed
> > 0.04 seconds.
> > >
> > >
> > >
> > > Okay, that's what I thought you meant. That certainly
> > affects the join
> > > times, although I'm not sure I'd call that issue synchronisation
> > > latency. We can certainly add some wording to highlight it though.
> > >
> > >
> > > 	Co-locating in time the RTCP SR packets with their
> > related access
> > > points further improves the sync time.  For example, if the IDR is
> > > every 2 seconds, there is no benefit (for syncing) to
> > sending the RTCP
> > > SR more frequently than that, especially if it is aligned with =
this
> > > access point in time.  If the RTCP SR packets are sent randomly in
> > > time, the sync time is the IDR period plus 1/2 the RTCP SR packet
> > > period, on average. This is more of an optimization, but
> > then, that's what this whole draft is about - optimizing the
> > sync time.
> > >
> > >
> > >
> > > I agree that co-locating the SR information in time with the =
random
> > > access points helps, and will add something to the draft to
> > say that
> > > explicitly if it's not already there. I disagree that's =
sufficient:
> > > sending the SR information more frequently gives the receiver more
> > > samples from which to estimate any skew between NTP and RTP
> > timestamps, and gives more information to help filter out any
> > incorrect mappings.
> > >
> > > --
> > > Colin Perkins
> > > http://csperkins.org/
> > >
> > >
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
> >
>=20


From csp@csperkins.org  Sun Jun 21 04:54:01 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 0C4123A6C69 for <avt@core3.amsl.com>; Sun, 21 Jun 2009 04:54:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, 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 1P9zbD9Z15Xm for <avt@core3.amsl.com>; Sun, 21 Jun 2009 04:54:00 -0700 (PDT)
Received: from lon1-msapost-3.mail.demon.net (lon1-msapost-3.mail.demon.net [195.173.77.182]) by core3.amsl.com (Postfix) with ESMTP id DD40F3A6A37 for <avt@ietf.org>; Sun, 21 Jun 2009 04:53:59 -0700 (PDT)
Received: from starkperkins.demon.co.uk ([80.176.158.71] helo=[192.168.254.8]) by lon1-post-3.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1MILcj-0000Zp-fu for avt@ietf.org; Sun, 21 Jun 2009 11:54:14 +0000
Message-Id: <91C724EB-3FAD-4745-867D-E350AEFEC922@csperkins.org>
From: Colin Perkins <csp@csperkins.org>
To: "Audio/Video Transport (AVT) WG" <avt@ietf.org>
In-Reply-To: <20090616154501.5B37B28C188@core3.amsl.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Sun, 21 Jun 2009 12:54:03 +0100
References: <20090616154501.5B37B28C188@core3.amsl.com>
X-Mailer: Apple Mail (2.935.3)
Subject: Re: [AVT] I-D Action:draft-ietf-avt-rapid-acquisition-for-rtp-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: Sun, 21 Jun 2009 11:54:01 -0000

On 16 Jun 2009, at 16:45, Internet-Drafts@ietf.org wrote:
> 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     : Unicast-Based Rapid Acquisition of Multicast RTP  
> Sessions
>   Author(s) : B. Steeg, et al.
>   Filename  : draft-ietf-avt-rapid-acquisition-for-rtp-01.txt
>   Pages     : 41
>   Date      : 2009-06-16

I had some minor comments:

Section 6: Do the RR and RS send the usual periodic RTCP reports on  
the retransmission session? I assume they do, but it'd be good to  
state that explicitly to avoid confusion.

Section 7: Are the RAMS messages sent as part of compound RTCP  
packets, or is the non-compound extension assumed? I can see  
advantages to using compound packets, and it would be good if the  
draft explicitly stated that they were used, according to the usual  
rules.

Section 7: Have you considered using several feedback message type  
(FMT) values, one for each of the RAMS-R, RAMS-I, and RAMS-T messages,  
instead of a single value with subtypes? It's not clear that the extra  
level of indirection buys anything.

Section 7.3: The Earliest Multicast Join Time and Burst Duration both  
specify times. The latter is specified in RTP clock units, the former  
says you need to decide between milliseconds and RTP clock units. It  
would make things easier for implementers if these were both the same.

Section 7.3: Is there any reason why a server would switch between  
supporting and not supporting updated requests within a single  
session? If not, then the S bit might be better signalled in the SDP,  
rather than in-band in each message.

Section 7.3 and 7.4: It's not clear why extended RTP sequence numbers  
are used, since the top 16 bits are always zero.

Section 7.3 "Note that if the RAMS requests has been accepted, RS MUST  
send this field as least once": Why is this a MUST? The RR must be  
able to work without this field, since the RAMS-I packet might be  
lost, so while I can see why this should be a SHOULD, I don't see the  
motivation for a MUST.

Section 9: As I've mentioned off-line to the authors, I don't find  
this compelling.

Cheers,
Colin



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




From abegen@cisco.com  Sun Jun 21 12:39:32 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 A151828C121 for <avt@core3.amsl.com>; Sun, 21 Jun 2009 12:39:32 -0700 (PDT)
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 PoR2wVq+7wIl for <avt@core3.amsl.com>; Sun, 21 Jun 2009 12:39:31 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 6C5ED28C0D6 for <avt@ietf.org>; Sun, 21 Jun 2009 12:39:31 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,263,1243814400"; d="scan'208";a="178818307"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-2.cisco.com with ESMTP; 21 Jun 2009 19:39:46 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n5LJdka4015692;  Sun, 21 Jun 2009 12:39:46 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n5LJdkUm016852; Sun, 21 Jun 2009 19:39:46 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.3959);  Sun, 21 Jun 2009 12:39:46 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 21 Jun 2009 12:39:42 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540995C571@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <91C724EB-3FAD-4745-867D-E350AEFEC922@csperkins.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] I-D Action:draft-ietf-avt-rapid-acquisition-for-rtp-01.txt
Thread-Index: AcnyZwRa9Q+kQ8m9Tn++QUNfLUDklgALVZLA
References: <20090616154501.5B37B28C188@core3.amsl.com> <91C724EB-3FAD-4745-867D-E350AEFEC922@csperkins.org>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Colin Perkins" <csp@csperkins.org>, "Audio/Video Transport (AVT) WG" <avt@ietf.org>
X-OriginalArrivalTime: 21 Jun 2009 19:39:46.0350 (UTC) FILETIME=[083E54E0:01C9F2A8]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4650; t=1245613186; x=1246477186; c=relaxed/simple; s=sjdkim3002; 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]=20I-D=20Action=3Adraft-ietf-avt-r apid-acquisition-for-rtp-01.txt |Sender:=20; bh=uAhRYSBl+ZieJuQ6NPX1hMWFqEdTY5q3JaNBLbZAYsg=; b=ho43Nbnv6BMiBi/Aq3tWzaFRp61PWj7L77hKb42rGFrYVzWIY+F7vpyeM6 9A7wrvG4OJq+v7M2fIPZKv9jddfe9RTAb8mD54s8OizUDa2I8eldHd4pgyMG pgNl6RvTD9;
Authentication-Results: sj-dkim-3; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Subject: Re: [AVT] I-D Action:draft-ietf-avt-rapid-acquisition-for-rtp-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: Sun, 21 Jun 2009 19:39:32 -0000

Hi Colin,

Thanks for reading the draft. I am adding my comments below.

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of =
Colin Perkins
> Sent: Sunday, June 21, 2009 4:54 AM
> To: Audio/Video Transport (AVT) WG
> Subject: Re: [AVT] I-D =
Action:draft-ietf-avt-rapid-acquisition-for-rtp-01.txt
>=20
> On 16 Jun 2009, at 16:45, Internet-Drafts@ietf.org wrote:
> > 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     : Unicast-Based Rapid Acquisition of Multicast RTP
> > Sessions
> >   Author(s) : B. Steeg, et al.
> >   Filename  : draft-ietf-avt-rapid-acquisition-for-rtp-01.txt
> >   Pages     : 41
> >   Date      : 2009-06-16
>=20
> I had some minor comments:
>=20
> Section 6: Do the RR and RS send the usual periodic RTCP reports on
> the retransmission session? I assume they do, but it'd be good to
> state that explicitly to avoid confusion.

Yes. We should add this.
=20
> Section 7: Are the RAMS messages sent as part of compound RTCP
> packets, or is the non-compound extension assumed? I can see
> advantages to using compound packets, and it would be good if the
> draft explicitly stated that they were used, according to the usual
> rules.

We assumed compound packets so far. I believe we already have this in =
place. We will check again. But, do you think non-compound packets are =
useful for sending RAMS-R for example?


> Section 7: Have you considered using several feedback message type
> (FMT) values, one for each of the RAMS-R, RAMS-I, and RAMS-T messages,
> instead of a single value with subtypes? It's not clear that the extra
> level of indirection buys anything.

That was the initial plan and based on the feedback in the breakout =
session, we turned into this subtype format. For one thing, it saves FMT =
values. And expansion will be easier if new message formats need to be =
introduced in the future.


> Section 7.3: The Earliest Multicast Join Time and Burst Duration both
> specify times. The latter is specified in RTP clock units, the former
> says you need to decide between milliseconds and RTP clock units. It
> would make things easier for implementers if these were both the same.

There are still a few suggestions for this. ms vs RTP ticks is one =
issue, and delta time vs absolute time is another one. Currently, I am =
personally inclined to delta time signaled in RTP ticks since it can =
signal "join now" semantics. However, absolute time in RTP ticks would =
also be nice since it tells RR to join as soon as it sees a packet whose =
timestamp is equal to or higher than this value. Comments are welcome on =
this issue.

=20
> Section 7.3: Is there any reason why a server would switch between
> supporting and not supporting updated requests within a single
> session? If not, then the S bit might be better signalled in the SDP,
> rather than in-band in each message.

That=92s is a good suggestion. I don't think that is a dynamic feature =
and can be easily signaled in SDP.=20

> Section 7.3 and 7.4: It's not clear why extended RTP sequence numbers
> are used, since the top 16 bits are always zero.

This is an open issue. We are trying to figure out how to support =
extended seqnums. We may need an early sender report to figure this out. =
Suggestions?
=20
> Section 7.3 "Note that if the RAMS requests has been accepted, RS MUST
> send this field as least once": Why is this a MUST? The RR must be
> able to work without this field, since the RAMS-I packet might be
> lost, so while I can see why this should be a SHOULD, I don't see the
> motivation for a MUST.

If RR is not told when to join SSM session, how is it supposed to know? =
You are right that RAMS-I may get lost, but in that case most likely the =
whole RAMS will fail. And at some point, RR will figure that out and =
join the SSM. However, if RAMS-I goes thru and the request was accepted, =
RR needs this info.

> Section 9: As I've mentioned off-line to the authors, I don't find
> this compelling.

I am hoping we will be able to find a good solution for this.

I will also let the co-authors comment on these comments.=20

Thanks again,
-acbegen

=20
> Cheers,
> Colin
>=20
>=20
>=20
> --
> Colin Perkins
> http://csperkins.org/
>=20
>=20
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt

From csp@csperkins.org  Mon Jun 22 05:22:57 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 6E7DE28C1C6 for <avt@core3.amsl.com>; Mon, 22 Jun 2009 05:22:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, 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 tDg2O2898S2j for <avt@core3.amsl.com>; Mon, 22 Jun 2009 05:22:56 -0700 (PDT)
Received: from lon1-msapost-3.mail.demon.net (lon1-msapost-3.mail.demon.net [195.173.77.182]) by core3.amsl.com (Postfix) with ESMTP id 7621F28C17D for <avt@ietf.org>; Mon, 22 Jun 2009 05:22:56 -0700 (PDT)
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]) by lon1-post-3.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1MIiYJ-0007Iz-ds; Mon, 22 Jun 2009 12:23:11 +0000
Message-Id: <4A986AF4-D80A-4682-B6CD-2EBE2D8C9F5E@csperkins.org>
From: Colin Perkins <csp@csperkins.org>
To: Ali C. Begen (abegen) <abegen@cisco.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D540995C571@xmb-sjc-215.amer.cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 22 Jun 2009 13:23:10 +0100
References: <20090616154501.5B37B28C188@core3.amsl.com> <91C724EB-3FAD-4745-867D-E350AEFEC922@csperkins.org> <04CAD96D4C5A3D48B1919248A8FE0D540995C571@xmb-sjc-215.amer.cisco.com>
X-Mailer: Apple Mail (2.935.3)
Cc: "Audio/Video Transport \(AVT\) WG" <avt@ietf.org>
Subject: Re: [AVT] I-D Action:draft-ietf-avt-rapid-acquisition-for-rtp-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: Mon, 22 Jun 2009 12:22:57 -0000

Hi Ali,

On 21 Jun 2009, at 20:39, Ali C. Begen (abegen) wrote:
> Thanks for reading the draft. I am adding my comments below.
...
>> Section 7: Are the RAMS messages sent as part of compound RTCP
>> packets, or is the non-compound extension assumed? I can see
>> advantages to using compound packets, and it would be good if the
>> draft explicitly stated that they were used, according to the usual
>> rules.
>
> We assumed compound packets so far. I believe we already have this  
> in place. We will check again. But, do you think non-compound  
> packets are useful for sending RAMS-R for example?

Depending on what you're doing, I can see use cases for both compound  
and non-compound packets. I'd suggest following the usual rules:  
mandate compound, unless support for non-compound is signalled.

>> Section 7: Have you considered using several feedback message type  
>> (FMT) values, one for each of the RAMS-R, RAMS-I, and RAMS-T  
>> messages, instead of a single value with subtypes? It's not clear  
>> that the extra level of indirection buys anything.
>
> That was the initial plan and based on the feedback in the breakout  
> session, we turned into this subtype format. For one thing, it saves  
> FMT values. And expansion will be easier if new message formats need  
> to be introduced in the future.

I'm not sure saving FMT values is an issue, but okay.

>> Section 7.3: The Earliest Multicast Join Time and Burst Duration both
>> specify times. The latter is specified in RTP clock units, the former
>> says you need to decide between milliseconds and RTP clock units. It
>> would make things easier for implementers if these were both the  
>> same.
>
> There are still a few suggestions for this. ms vs RTP ticks is one  
> issue, and delta time vs absolute time is another one. Currently, I  
> am personally inclined to delta time signaled in RTP ticks since it  
> can signal "join now" semantics. However, absolute time in RTP ticks  
> would also be nice since it tells RR to join as soon as it sees a  
> packet whose timestamp is equal to or higher than this value.  
> Comments are welcome on this issue.

Delta time is easier, since you have to worry less about clock sync.

I tend to prefer RTP ticks rather than milliseconds, since the  
receiver is guaranteed to have a clock running in RTP ticks, but the  
main issue is consistency.

...
>> Section 7.3 and 7.4: It's not clear why extended RTP sequence numbers
>> are used, since the top 16 bits are always zero.
>
> This is an open issue. We are trying to figure out how to support  
> extended seqnums. We may need an early sender report to figure this  
> out. Suggestions?

Why do you need extended sequence numbers? It's not really a well- 
defined concept across receivers in RTP.

>> Section 7.3 "Note that if the RAMS requests has been accepted, RS  
>> MUST send this field as least once": Why is this a MUST? The RR  
>> must be able to work without this field, since the RAMS-I packet  
>> might be lost, so while I can see why this should be a SHOULD, I  
>> don't see the motivation for a MUST.
>
> If RR is not told when to join SSM session, how is it supposed to  
> know? You are right that RAMS-I may get lost, but in that case most  
> likely the whole RAMS will fail. And at some point, RR will figure  
> that out and join the SSM. However, if RAMS-I goes thru and the  
> request was accepted, RR needs this info.

Sure, if it's missing, the RR will have to guess when to join the SSM  
session. That's undesirable, but the RR will need that functionality  
anyway. You gain nothing by making this a MUST, other than confusing  
naive implementers into thinking they can assume this will always be  
received.

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




From john.mattsson@ericsson.com  Mon Jun 22 08:00:49 2009
Return-Path: <john.mattsson@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 6E84B3A6CEA for <avt@core3.amsl.com>; Mon, 22 Jun 2009 08:00:49 -0700 (PDT)
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 Z78TMN+pNuOH for <avt@core3.amsl.com>; Mon, 22 Jun 2009 08:00:48 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 601AE3A6AA4 for <avt@ietf.org>; Mon, 22 Jun 2009 08:00:48 -0700 (PDT)
X-AuditID: c1b4fb3e-b7b99ae0000070a2-ab-4a3f9c01bd95
Received: from esealmw127.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id E9.E6.28834.10C9F3A4; Mon, 22 Jun 2009 16:58:09 +0200 (CEST)
Received: from esealmw121.eemea.ericsson.se ([153.88.200.80]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 22 Jun 2009 16:58:09 +0200
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: Mon, 22 Jun 2009 16:57:29 +0200
Message-ID: <BB048F7D0346F841AA7BEC83644EB78D03B591E2@esealmw121.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New Version Notification for draft-naslund-srtp-saf-01
Thread-Index: AcnzScNoOLDfqZSDQju53kEBSW9MJA==
From: "John Mattsson" <john.mattsson@ericsson.com>
To: "AVT" <avt@ietf.org>
X-OriginalArrivalTime: 22 Jun 2009 14:58:09.0251 (UTC) FILETIME=[DB336330:01C9F349]
X-Brightmail-Tracker: AAAAAA==
Subject: [AVT] New Version Notification for draft-naslund-srtp-saf-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: Mon, 22 Jun 2009 15:00:49 -0000

Dear all,
=20
We have submitted a new version (01) of "The Use of the Secure Real-time
Transport Protocol (SRTP) in Store-and-Forward Applications".
=20
We would like to thank Eric Rescorla for his review of the previous
version.
=20
We have updated the draft based on the comments received on the avt
mailing list. We have expanded the initial part of the draft and added a
new "Design Rationale" section. We have also updated the Security
Considerations.
=20
We have implemented SRTP Store-and-Forward according to version-01 and
generated a test vector (see Appendix B). The use of the CCI field is
now optional. The PUV, SSS and CCI fields now take 3 bytes per default
compared to 10 bytes in the previous version.
=20
Best regards,

   John Mattsson

From abegen@cisco.com  Mon Jun 22 08:52:04 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 859FC28C208 for <avt@core3.amsl.com>; Mon, 22 Jun 2009 08:52:04 -0700 (PDT)
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 9hQatzBEi2hC for <avt@core3.amsl.com>; Mon, 22 Jun 2009 08:52:03 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 692A63A6DFC for <avt@ietf.org>; Mon, 22 Jun 2009 08:52:03 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,269,1243814400"; d="scan'208";a="203827107"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-1.cisco.com with ESMTP; 22 Jun 2009 15:52:18 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n5MFqIfS028988;  Mon, 22 Jun 2009 08:52:18 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n5MFqIu1002859; Mon, 22 Jun 2009 15:52:18 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 22 Jun 2009 08:52:17 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 22 Jun 2009 08:52:11 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540995C692@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <4A986AF4-D80A-4682-B6CD-2EBE2D8C9F5E@csperkins.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] I-D Action:draft-ietf-avt-rapid-acquisition-for-rtp-01.txt
Thread-Index: AcnzNDZiGt5sVRLsS3uuRadeg0lmkgAHEnSg
References: <20090616154501.5B37B28C188@core3.amsl.com> <91C724EB-3FAD-4745-867D-E350AEFEC922@csperkins.org> <04CAD96D4C5A3D48B1919248A8FE0D540995C571@xmb-sjc-215.amer.cisco.com> <4A986AF4-D80A-4682-B6CD-2EBE2D8C9F5E@csperkins.org>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Colin Perkins" <csp@csperkins.org>
X-OriginalArrivalTime: 22 Jun 2009 15:52:17.0421 (UTC) FILETIME=[6B42CBD0:01C9F351]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3392; t=1245685938; x=1246549938; c=relaxed/simple; s=sjdkim3002; 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]=20I-D=20Action=3Adraft-ietf-avt-r apid-acquisition-for-rtp-01.txt |Sender:=20; bh=cTKjBCLw76kafdJZJTtC8DfS3fxj2vaCOC5dVDE9MYA=; b=Qi0neEdaLp0UWyQkbJO0VTKb2FCaOstxq33KI3MBDqzf4itsiiqrtT08fu 8c87YS6OVLHgw+5wQeWnTygENAsdYWK2rZVSIcy9g0h8DKzYLPmyXEXqmewu zjA55kDdT0;
Authentication-Results: sj-dkim-3; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Cc: "Audio/Video Transport \(AVT\) WG" <avt@ietf.org>
Subject: Re: [AVT] I-D Action:draft-ietf-avt-rapid-acquisition-for-rtp-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: Mon, 22 Jun 2009 15:52:04 -0000

Hi Colin,

> > We assumed compound packets so far. I believe we already have this
> > in place. We will check again. But, do you think non-compound
> > packets are useful for sending RAMS-R for example?
>=20
> Depending on what you're doing, I can see use cases for both compound
> and non-compound packets. I'd suggest following the usual rules:
> mandate compound, unless support for non-compound is signalled.

Sounds good to me.
=20
> >> Section 7.3: The Earliest Multicast Join Time and Burst Duration =
both
> >> specify times. The latter is specified in RTP clock units, the =
former
> >> says you need to decide between milliseconds and RTP clock units. =
It
> >> would make things easier for implementers if these were both the
> >> same.
> >
> > There are still a few suggestions for this. ms vs RTP ticks is one
> > issue, and delta time vs absolute time is another one. Currently, I
> > am personally inclined to delta time signaled in RTP ticks since it
> > can signal "join now" semantics. However, absolute time in RTP ticks
> > would also be nice since it tells RR to join as soon as it sees a
> > packet whose timestamp is equal to or higher than this value.
> > Comments are welcome on this issue.
>=20
> Delta time is easier, since you have to worry less about clock sync.

True but note that signaling a TS value and then asking RR to join right =
after he sees that TS value does not require clock sync. If there are no =
objections, we can go with the delta time.
=20
> I tend to prefer RTP ticks rather than milliseconds, since the
> receiver is guaranteed to have a clock running in RTP ticks, but the
> main issue is consistency.

Agree.

=20
> ...
> >> Section 7.3 and 7.4: It's not clear why extended RTP sequence =
numbers
> >> are used, since the top 16 bits are always zero.
> >
> > This is an open issue. We are trying to figure out how to support
> > extended seqnums. We may need an early sender report to figure this
> > out. Suggestions?
>=20
> Why do you need extended sequence numbers? It's not really a well-
> defined concept across receivers in RTP.

What about the really high-bitrate streams where seqnum wrapping might =
be an issue during the course of unicast burst?

=20
> >> Section 7.3 "Note that if the RAMS requests has been accepted, RS
> >> MUST send this field as least once": Why is this a MUST? The RR
> >> must be able to work without this field, since the RAMS-I packet
> >> might be lost, so while I can see why this should be a SHOULD, I
> >> don't see the motivation for a MUST.
> >
> > If RR is not told when to join SSM session, how is it supposed to
> > know? You are right that RAMS-I may get lost, but in that case most
> > likely the whole RAMS will fail. And at some point, RR will figure
> > that out and join the SSM. However, if RAMS-I goes thru and the
> > request was accepted, RR needs this info.
>=20
> Sure, if it's missing, the RR will have to guess when to join the SSM
> session. That's undesirable, but the RR will need that functionality
> anyway. You gain nothing by making this a MUST, other than confusing
> naive implementers into thinking they can assume this will always be
> received.

I see your point. SHOULD makes more sense.

Thanks,
-acbegen

=20
> Cheers,
> --
> Colin Perkins
> http://csperkins.org/
>=20
>=20


From Tom.Van_Caenegem@alcatel-lucent.be  Mon Jun 22 09:28:46 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 250FE3A6845 for <avt@core3.amsl.com>; Mon, 22 Jun 2009 09:28:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.849
X-Spam-Level: 
X-Spam-Status: No, score=-5.849 tagged_above=-999 required=5 tests=[AWL=0.400,  BAYES_00=-2.599, HELO_EQ_FR=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 sF0GjM47kUax for <avt@core3.amsl.com>; Mon, 22 Jun 2009 09:28:44 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by core3.amsl.com (Postfix) with ESMTP id ACD4E3A68F8 for <avt@ietf.org>; Mon, 22 Jun 2009 09:28:43 -0700 (PDT)
Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.dc-m.alcatel-lucent.com [155.132.6.76]) by smail3.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5MGSsfv006589;  Mon, 22 Jun 2009 18:28:54 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.52]) by FRVELSBHS04.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 22 Jun 2009 18:28:53 +0200
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: Mon, 22 Jun 2009 18:28:52 +0200
Message-ID: <238382595265324EA50F6134BB42DCAF0408D9F6@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D540995C3DF@xmb-sjc-215.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Some comments on " Multicast Acquisition Report Block Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-01)
Thread-Index: AcnxB+ZTSpmPIRTQTtqRFSxt0v9qZAAILfjQAIPOkFA=
References: <238382595265324EA50F6134BB42DCAF0408CAE6@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D8C33@xmb-sjc-215.amer.cisco.com> <238382595265324EA50F6134BB42DCAF0408CFA0@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D540995C22C@xmb-sjc-215.amer.cisco.com> <63BA849C-3FC0-4733-A831-46ACE02FB348@cisco.com> <04CAD96D4C5A3D48B1919248A8FE0D540995C3DF@xmb-sjc-215.amer.cisco.com>
From: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>
To: "Ali C. Begen (abegen)" <abegen@cisco.com>, "Eric Friedrich (efriedri)" <efriedri@cisco.com>
X-OriginalArrivalTime: 22 Jun 2009 16:28:53.0842 (UTC) FILETIME=[886E0B20:01C9F356]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.83
Cc: avt@ietf.org
Subject: Re: [AVT] Some comments on " Multicast Acquisition Report Block Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-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: Mon, 22 Jun 2009 16:28:46 -0000

Ali,

I think your proposal is +/- OK. However, I believe there is some room
for improvement here. Suppose we have :


- a dedicated  field X (3 bit is sufficient) "acquisition_method" with a
code indicating which kind of acquisition process was initiated by the
receiver (we can already define two codes in this draft : normal SFGMP
process and RAMS process)

E.g.

X =3D001 =3D Normal MC Acquisition Process
X =3D011 =3D RAMS-based MC Acquisition Process

- a dedicated field Y indicating the MC acquisition "status code" . For
normal acquisition process, only two codes can be defined (success or no
success), and for the RAMS process, your proposal was to refer to codes
defined in RAMS draft, but to me it makes more sense to (additionally)
define a code that provides the success/non success from the receiver
point of view. E.g. "success" code received by the receiver from the
retransmission server in the RAMS-I does not mean the RAMS is a success.
Note also that it would make sense to clearly make a distinction whether
the RAMS was successful or not, and also whether the MC join -following
and as part of the RAMS -was successful. It gives immediate insight by
the retransmission server which part failed. We then can also define per
code which fields must be present, for an RTP receiver supporting this
kind of XR reports.

E.g. the Y code for RAMS could be composed of two sub-fields

-Subfield Y1 (2 bits):

00=3DRAMS unsuccessful, MC join unsuccessful
01=3DRAMS unsuccessful, MC join successful
11=3DRAMS successful, MC join successful

What does 'RAMS successful (/unsuccessful)" mean here? This is not easy
to answer, but I think it should represent the status from the point of
view of the receiver, i.e. receiving a RAMS-I message with code
"successful" is not sufficient (e.g. the RTP burst may not be delivered
to the receiver, e.g. because of bad configuration of the NAPT). So,
reception of the RTP data burst by the receiver as response on a
RAMS-Request, looks like a better condition to call RAMS successful or
not. As discussed in the RAMS draft, if RAMS-I or RAMS-T messages get
dropped in between the receiver and the server, both server and receiver
should be able to cope with that. However, if there is a gap between the
burst and the MC, which was not closed despite retransmission
(attempts), do we still call this a "successful" process from the
receiver point of view? I tend to say "no", so.. "successful RAMS" would
mean that the complete RAMS process -including the MC join- was
succesful, resulting in the fact that all expected RTP data (unicast and
multicast) was successfully and timely transferred by the RTP end-point
to the application.  This makes of course the "10=3DRAMS successful, MC
join unsuccessful" code obsolete.


-Subfield Y2 (same size as defined in RAMS draft) containing the
"Retransmission server response code"  Note that for the Y2 field, we
also need to define a code, when there was no RAMS-I response from the
server.


With the definitions for subfield Y1 as per above, we can make a
selection of which fields are to be provided mandatory by the RTP
receiver



E.g. for normal acquisition process (X=3D 001),=20

Only if Y =3D 1, the following fields shall be present:=20
-SN of 1st MC packet
-delta time between 1st IGMP join and 1st received MC packet =20
-(others?)=20

E.g. for RAMS based acquisition process (X=3D 011):

Y1 =3D 11  (Y2 code=3D "success") where expected fields must be :=20

-SN of 1st MC packet
-delta time between 1st RAMS-R and 1st received burst packet=20
-delta time between 1st IGMP join and 1st received MC packet
-(others?) =20

Y1 =3D 01 (Y2 code =3D could be any code!)where expected fields must be =
:=20

-SN of 1st MC packet
-delta time between 1st RAMS-R and 1st received MC packet
-delta time between 1st IGMP join and 1st received MC packet
-(others?)=20


Y1 =3D 00   (Y2 code =3D could be any code!): no fields are mandatory.


What do you think?

Regards
Tom


-----Original Message-----
From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]=20
Sent: zaterdag 20 juni 2009 0:07
To: Eric Friedrich (efriedri)
Cc: VAN CAENEGEM Tom; avt@ietf.org
Subject: RE: [AVT] Some comments on " Multicast Acquisition Report Block
Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-01)

Join time and first mcast seqnum would be common to all scenarios.
However, what if that information is not available, meaning that the
receiver could not join, i.e., could not receive anything at all from
the multicast session? In that case, those fields should not exist.
Using magical numbers is not a good idea.

So, I suggest the following: If join was successful (so at least one
mcast packet was received), these two fields MUST (not may or should) be
included in the report. If join was not successful, these fields SHALL
NOT exist.

This should address Tom's concerns except that this report will not say
much whether acceleration was requested or not (or if yes, which method
was requested). I think we can use one of the status codes (we have 256
of them anyway) to indicate this. Or, we can separate a block to
indicate the individual acceleration methods.

How does this sound?

-acbegen

> -----Original Message-----
> From: Eric Friedrich (efriedri)
> Sent: Friday, June 19, 2009 11:01 AM
> To: Ali C. Begen (abegen)
> Cc: VAN CAENEGEM Tom; avt@ietf.org
> Subject: Re: [AVT] Some comments on " Multicast Acquisition Report
Block Typefor RTCP XR"
> (draft-begen-avt-rapid-sync-rtcp-xr-01)
>=20
> Ali, Tom-
>    I think it would be useful to provide some small base set of fields

> that are required for any MA report. They should be fields that do not

> require any special instrumentation on the RTP Receiver and apply to=20
> RAMS and non-RAMS acquisitions. Looking over our proposed fields, I'd=20
> like to suggest that "First Multicast Extended Seq Number" and "SFGMP=20
> Join Time" be required fields. They would provide a small but useful=20
> amount of information in cases where receivers do not support the=20
> other fields.
>=20
> Thanks,
> Eric
>=20
> On Jun 19, 2009, at 1:43 PM, Ali C. Begen (abegen) wrote:
>=20
> > Hi Tom,
> >
> > I just feel that mandating some fields but not requiring the=20
> > receivers to fill them in is not a good solution. As I mentioned=20
> > earlier, I'd prefer using a stronger language than "optional" but I=20
> > prefer not to mandate such fields.
> >
> > Any other opinions?
> >
> > -acbegen
> >
> >> -----Original Message-----
> >> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> >> Sent: Friday, June 19, 2009 3:40 AM
> >> To: Ali C. Begen (abegen); avt@ietf.org
> >> Subject: RE: [AVT] Some comments on " Multicast Acquisition Report=20
> >> Block Typefor RTCP XR"
> >> (draft-begen-avt-rapid-sync-rtcp-xr-01)
> >>
> >> Hi Ali,
> >>
> >> Look for "TOM" ...
> >>
> >> -----Original Message-----
> >> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> >> Sent: donderdag 18 juni 2009 17:34
> >> To: VAN CAENEGEM Tom; avt@ietf.org
> >> Subject: RE: [AVT] Some comments on " Multicast Acquisition Report=20
> >> Block Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-01)
> >>
> >> Hi Tom,
> >>
> >> Thanks for reading the draft.
> >>
> >>> -----Original Message-----
> >>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf

> >>> Of VAN CAENEGEM Tom
> >>> Sent: Thursday, June 18, 2009 7:17 AM
> >>> To: avt@ietf.org
> >>> Subject: [AVT] Some comments on " Multicast Acquisition Report=20
> >>> Block
> >> Typefor RTCP XR"
> >>> (draft-begen-avt-rapid-sync-rtcp-xr-01)
> >>>
> >>> Hi Ali,
> >>>
> >>> I have a few comments/questions related to the draft:
> >>>
> >>> Comment 1:  The abstract now has a sentence: "For quality=20
> >>> reporting, monitoring and diagnostics purposes, it is important to

> >>> collect detailed information from the RTP receivers about their=20
> >>> acquisition
> >> experiences."  Doesn't it go beyond "RTP (receivers)"
> >>> and "acquisition" as you also define e.g. a TLV related to=20
> >>> presentation time delay (sometimes the MC RTP delivered content=20
> >>> may
> >> not even be displayed) and application delay.
> >>> I have no problem with the definition of such fields, but IMO it=20
> >>> makes
> >>
> >>> sense to make this clear in the abstract.
> >>
> >> I am not sure what else I can use instead of "RTP receivers" as I=20
> >> don't wanna specifically say decoders, set-tops, etc. Instead of=20
> >> "acquisition experiences", maybe we can call it "acquisition and=20
> >> presentation experiences"?
> >>
> >> Would that help?
> >>
> >> "TOM" : OK
> >>
> >>> Comment 2: Base Report
> >>>
> >>> The only informational field here is "response". It is still not=20
> >>> defined, but you refer to the response code in RAMS draft (e.g.
> >> "success", etc).
> >>
> >> I believe using the same codes will make it more useful.
> >>
> >> "TOM" : OK, but most codes only apply to a rapid acquisition=20
> >> process, so it makes sense to indicate additionally whether=20
> >> "normal" or "rapid"
> >> acquisition was initiated by the receiver (that is an additional
> >> flag)
> >>
> >>> I guess it is not possible to signal to an RR which additional=20
> >>> info to
> >>
> >>> send, i.e which TLV fields to use...From that point of view, would

> >>> it not make sense to have some basic information -now defined in=20
> >>> some TLV
> >>
> >>> fields in the base report- that is always present, to
> >>
> >> By always present, you mean "mandatory"? If yes, we indeed need to=20
> >> decide which ones.
> >>
> >> "TOM" : indeed mandatory : when by means of declarative SDP, the=20
> >> RTP receivers are instructed to send RTCP XR with multicast=20
> >> acquisition report blocks, AND RTP recievers support these XR=20
> >> messages, these fields are always there.
> >>
> >>> enhance interoperability. I know we need to find the right balance

> >>> between useful information reporting ,  bandwidth efficiency, and
> >> receiver reporting capabilities.
> >>>
> >>> Candidate fields that could be inside this fixed base report are:
> >>> -flag/field indicating whether the report refers to a normal=20
> >>> acquisition (based on SFGMP) or rapid MC RTP acquisition (or=20
> >>> rather the intention by the RR to perform  a rapid
> >>> acquisition) for instance by means of RAMS
> >>
> >> One reason behind this base report vs extensions separation was to=20
> >> be able to handle other rapid multicast acquisition methods. So,=20
> >> IMO, if we will have to make something mandatory, it should not=20
> >> relate to a specific method. It is true that I am heavily=20
> >> considering RAMS in designing this report, but it just works for=20
> >> other methods, if they become interested in supporting this report.
> >>
> >> Will this flag/field be able to specify which method was used? Or=20
> >> will it simply specify whether it was a rapid or normal=20
> >> acquisition?
> >>
> >> "TOM" : for a 1-bit flag, that should be the latter : normal or=20
> >> rapid (in whatever way). Alternatively considering a multiple bit=20
> >> field (e.g.
> >> 3 bits) where e.g. 001 =3D normal aquisition, 002 =3D RAMS, and all =

> >> other codes unspecified at this stage looks to me a good solution=20
> >> as well...
> >>
> >>> -a response code which you have indeed defined and its=20
> >>> interpretation should be dependent on the previously mentioned=20
> >>> flag/field
> >>
> >> So, the flag/field above will indeed specify which method was use=20
> >> to make RR rapidly acquire the content. Yes/no?
> >>
> >> "TOM" : see above
> >>
> >>
> >>> -initial launched request (either 1st RAMS-R for rapid=20
> >>> acquisition, either 1st IGMP-join in case of normal acquisition)=20
> >>> to 1st received RTP packet (always a multicast packet for normal=20
> >>> acquisition and "normally" a burst packet when a rapid acquisition

> >>> process was
> >>> involved) delta time
> >>>
> >>> -application request to initial launched request (either 1st=20
> >>> RAMS-R for rapid acquisition, either 1st IGMP-join in case of=20
> >>> normal
> >>> acquisition) delta time
> >>>
> >>> For these last two fields, a value must be specified that would=20
> >>> indicate that the field is not filled out (because the receiver=20
> >>> client
> >> implementation may not support it).
> >>
> >> Oh, then these fields are not mandatory since the client has the=20
> >> option to leave them blank. Then, I would recommend leaving the=20
> >> current report as it is, but we can use a stronger language (like=20
> >> "SHOULD/
> >> RECOMMENDED")
> >> for some of the fields (like the ones you have above) to promote=20
> >> interoperability.
> >>
> >> Would you be OK with that?
> >>
> >> "TOM" : the reason to have the field in the base report, is to make

> >> sure that a minimum of information is conveyed back to the=20
> >> server/feedback target. Otherwise, as all TLV fields are optional,=20
> >> how can a server indicate to a client which TLV fields it is=20
> >> interested in and which ones not?  The proposed fields I=20
> >> selected/defined are those that provide useful information  for=20
> >> both a normal and RAMS process, but there may be
> >> other fields equally appropriate to be always present.   Whether we
> >> need
> >> an RTP receiver to mandate to fill out these fields (with the right
> >> value) is a separate discussion, IMO.
> >>
> >>> There could still be other fields that apply to both acquisition=20
> >>> processes and fit in the base report, but they should be=20
> >>> application independent (e.g. delta to presentation time is=20
> >>> clearly app
> >>> dependent)
> >>
> >> Agree, application dependent fields are optional and should stay
so.
> >>
> >> T,
> >> -acbegen
> >>
> >>>
> >>> Regards
> >>> Tom
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt


From rfc-editor@rfc-editor.org  Mon Jun 22 17:10:50 2009
Return-Path: <rfc-editor@rfc-editor.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 132453A6DEE; Mon, 22 Jun 2009 17:10:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.887
X-Spam-Level: 
X-Spam-Status: No, score=-16.887 tagged_above=-999 required=5 tests=[AWL=0.112, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
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 IVexQEcdO-fc; Mon, 22 Jun 2009 17:10:49 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 240CD3A6DE2; Mon, 22 Jun 2009 17:10:49 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id AFDB52D6515; Mon, 22 Jun 2009 17:09:20 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20090623000920.AFDB52D6515@bosco.isi.edu>
Date: Mon, 22 Jun 2009 17:09:20 -0700 (PDT)
Cc: avt@ietf.org, rfc-editor@rfc-editor.org
Subject: [AVT] RFC 5574 on RTP Payload Format for the Speex Codec
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, 23 Jun 2009 00:10:50 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5574

        Title:      RTP Payload Format for the 
                    Speex Codec 
        Author:     G. Herlein, J. Valin,
                    A. Heggestad, A. Moizard
        Status:     Standards Track
        Date:       June 2009
        Mailbox:    gherlein@herlein.com, 
                    jean-marc.valin@usherbrooke.ca, 
                    aeh@db.org, jack@atosc.org
        Pages:      14
        Characters: 27995
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avt-rtp-speex-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5574.txt

Speex is an open-source voice codec suitable for use in VoIP (Voice
over IP) type applications.  This document describes the payload
format for Speex-generated bit streams within an RTP packet.  Also
included here are the necessary details for the use of Speex with the
Session Description Protocol (SDP).  [STANDARDS TRACK]

This document is a product of the Audio/Video Transport Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From root@core3.amsl.com  Tue Jun 23 05: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 851573A6EAD; Tue, 23 Jun 2009 05:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090623124501.851573A6EAD@core3.amsl.com>
Date: Tue, 23 Jun 2009 05:45:01 -0700 (PDT)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-app-rtp-keepalive-06.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, 23 Jun 2009 12: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           : Application Mechanism for maintaining alive the Network Address Translator (NAT) mappings associated to RTP flows.
	Author(s)       : X. Marjou, A. Sollaud
	Filename        : draft-ietf-avt-app-rtp-keepalive-06.txt
	Pages           : 10
	Date            : 2009-06-23

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.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-app-rtp-keepalive-06.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-app-rtp-keepalive-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From Even.roni@huawei.com  Tue Jun 23 14:12:42 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 76A2228C181 for <avt@core3.amsl.com>; Tue, 23 Jun 2009 14:12:42 -0700 (PDT)
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 aQQ25Djfae2v for <avt@core3.amsl.com>; Tue, 23 Jun 2009 14:12:41 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 6215E28C170 for <avt@ietf.org>; Tue, 23 Jun 2009 14:12:41 -0700 (PDT)
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 <0KLP0070PMXKD7@szxga03-in.huawei.com> for avt@ietf.org; Wed, 24 Jun 2009 05:12:56 +0800 (CST)
Received: from huawei.com ([172.24.1.3]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLP00862MXKRF@szxga03-in.huawei.com> for avt@ietf.org; Wed, 24 Jun 2009 05:12:56 +0800 (CST)
Received: from windows8d787f9 (bzq-79-181-103-217.red.bezeqint.net [79.181.103.217]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KLP000D6MXCM2@szxml01-in.huawei.com> for avt@ietf.org; Wed, 24 Jun 2009 05:12:56 +0800 (CST)
Date: Wed, 24 Jun 2009 00:12:42 +0300
From: Roni Even <Even.roni@huawei.com>
To: avt@ietf.org
Message-id: <010901c9f447$5e0a79d0$1a1f6d70$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_lG71yS5K1kPx4oRj12+MDg)"
Content-language: en-us
Thread-index: Acn0R1h7jVbmDCpdT4OG2e7duKy/rw==
Subject: [AVT] conclusion of WGLC on draft-ietf-avt-rtp-ipmr-04
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, 23 Jun 2009 21:12:42 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_lG71yS5K1kPx4oRj12+MDg)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hi,

We concluded the WGLC, there were some comments and the authors of the draft
will submit a new revision addressing the comments.

Thanks

Roni Even

AVT co-chair


--Boundary_(ID_lG71yS5K1kPx4oRj12+MDg)
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:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" 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>We concluded the WGLC, there were some comments and =
the
authors of the draft will submit a new revision addressing the =
comments.<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>AVT co-chair<o:p></o:p></p>

</div>

</body>

</html>

--Boundary_(ID_lG71yS5K1kPx4oRj12+MDg)--

From csp@csperkins.org  Wed Jun 24 01:53:31 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 62B3728C470 for <avt@core3.amsl.com>; Wed, 24 Jun 2009 01:53:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, 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 g5NkDYNjG-cY for <avt@core3.amsl.com>; Wed, 24 Jun 2009 01:53:30 -0700 (PDT)
Received: from anchor-msapost-2.mail.demon.net (anchor-msapost-2.mail.demon.net [195.173.77.165]) by core3.amsl.com (Postfix) with ESMTP id 20AA028C42D for <avt@ietf.org>; Wed, 24 Jun 2009 01:53:30 -0700 (PDT)
Received: from starkperkins.demon.co.uk ([80.176.158.71] helo=[192.168.254.8]) by anchor-post-2.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1MJOEi-0000Uv-ku; Wed, 24 Jun 2009 08:53:44 +0000
Message-Id: <0F6A1967-073E-4AD4-865C-4867FE8C270C@csperkins.org>
From: Colin Perkins <csp@csperkins.org>
To: Ali C. Begen (abegen) <abegen@cisco.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D540995C692@xmb-sjc-215.amer.cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 24 Jun 2009 09:53:33 +0100
References: <20090616154501.5B37B28C188@core3.amsl.com> <91C724EB-3FAD-4745-867D-E350AEFEC922@csperkins.org> <04CAD96D4C5A3D48B1919248A8FE0D540995C571@xmb-sjc-215.amer.cisco.com> <4A986AF4-D80A-4682-B6CD-2EBE2D8C9F5E@csperkins.org> <04CAD96D4C5A3D48B1919248A8FE0D540995C692@xmb-sjc-215.amer.cisco.com>
X-Mailer: Apple Mail (2.935.3)
Cc: "Audio/Video Transport \(AVT\) WG" <avt@ietf.org>
Subject: Re: [AVT] I-D Action:draft-ietf-avt-rapid-acquisition-for-rtp-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, 24 Jun 2009 08:53:31 -0000

Hi Ali,

On 22 Jun 2009, at 16:52, Ali C. Begen (abegen) wrote:
...
>>>> Section 7.3 and 7.4: It's not clear why extended RTP sequence  
>>>> numbers are used, since the top 16 bits are always zero.
>>>
>>> This is an open issue. We are trying to figure out how to support
>>> extended seqnums. We may need an early sender report to figure this
>>> out. Suggestions?
>>
>> Why do you need extended sequence numbers? It's not really a well-
>> defined concept across receivers in RTP.
>
> What about the really high-bitrate streams where seqnum wrapping  
> might be an issue during the course of unicast burst?

Can't you use modulo arithmetic as usual? I don't see any issues,  
unless the RAMS-T is sent more than a full sequence number cycle ahead  
of time.

Cheers,
Colin

From versteb@cisco.com  Wed Jun 24 05:56:36 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 DD69A3A68D2 for <avt@core3.amsl.com>; Wed, 24 Jun 2009 05:56:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.669
X-Spam-Level: 
X-Spam-Status: No, score=-6.669 tagged_above=-999 required=5 tests=[AWL=-0.070, 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 GLNJJg6fDeyb for <avt@core3.amsl.com>; Wed, 24 Jun 2009 05:56:35 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id AEDD73A63CB for <avt@ietf.org>; Wed, 24 Jun 2009 05:56:35 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,283,1243814400"; d="scan'208";a="204919034"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-1.cisco.com with ESMTP; 24 Jun 2009 12:37:14 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n5OCbEaF016022;  Wed, 24 Jun 2009 05:37:14 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n5OCbDcI022703; Wed, 24 Jun 2009 12:37:14 GMT
Received: from xmb-rtp-21d.amer.cisco.com ([64.102.31.116]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 24 Jun 2009 08:37:14 -0400
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: Wed, 24 Jun 2009 08:37:12 -0400
Message-ID: <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com>
In-Reply-To: <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Port mappings, NAT, and RAMS
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDgARoKBSA=
References: <mailman.10085.1245185397.4936.avt@ietf.org><238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com><015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com><238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com><04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com><81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com><3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com><025401c9effa$34040170$9c0c0450$%roni@huawei.com><3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com><04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com>
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "Zeev Vax" <zeevvax@microsoft.com>, "Ali C. Begen (abegen)" <abegen@cisco.com>, "Roni Even" <Even.roni@huawei.com>, "VANCAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>, <avt@ietf.org>
X-OriginalArrivalTime: 24 Jun 2009 12:37:14.0052 (UTC) FILETIME=[8055E840:01C9F4C8]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4028; t=1245847034; x=1246711034; c=relaxed/simple; s=sjdkim2002; 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:=20Port=20mappings,=20NAT,=20and=20RAMS |Sender:=20; bh=GC/EwIm/PJAUGivOTXuUEJGhN3/Q6xusnrB+udvvvjA=; b=X1c9H/2rtxQU99/WTtZE23XqEqFCCmcSrSXkA9vEACw8uTSzugBF6+gqWL h1N1BAHn+QGLVoFvpvANmNV5fQpYM0nySJ0QcD6FnKKbiVshCBC8dTsKCveA fDEkETsZ4R;
Authentication-Results: sj-dkim-2; header.From=versteb@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Subject: [AVT] Port mappings, NAT, and RAMS
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, 24 Jun 2009 12:56:36 -0000

=20
There has been some discussion around the requirement for a NAT section
in the latest RAMS draft. This note is an attempt to clarify the
requirement to signal RAMS port mappings. Once we come to a consensus as
to the desired behavior, we can update the draft.

This text refers to a ppt document that can be found at
ftp://ftpeng.cisco.com/abegen/PubPorts.pdf

When using RAMS to accelerate acquisition of a multicast flow, there are
two sessions - the primary multicast session and the acceleration
session. These sessions may have multiple socket contexts, depending on
the use of RTP/RTP port muxing. However, the primary multicast session
and the retransmission session are always distinct.

1- The primary multicast session - two logical flows defined by the
Source address, Destination Multicast Address, RTP port (P1) and RTCP
port(P2). This set of flows is shown in RED in the diagram.
2- The retransmission/acceleration session, shown in BLUE in the
diagram. In the most general non-port-muxed, non-NATed case, this stream
consists of 2 flows. The first (RTP) flow is defined by the 5-tuple of
UDP, IP address of the FT, RTP port configured by SDP (P3),  the IP
address of the client and the RTP port dynamically chosen by RR (c3).
The second (RTCP) flow is defined by the 5-tuple of UDP, FT address, the
RTCP port defined by SDP (P4), the IP address of the client and the RTCP
port dynamically chosen by RR (c4). When RTP/RTCP port muxing is used,
the retransmission session is collapsed onto a single 5-tuple.

Note that the feedback target for the primary session is P2 on FT/RS.
Note that the acceleration burst must flow from FT P3/P4 to C c3/c4. In
other words, the first desired data flow on the retransmission session
is "downstream".=20

When we introduce NAT, we need to map c3 to c3' (and in the absence of
port muxing, also c4 to c4') through the NAT device. This diagram shows
the use of STUN in YELLOW to setup the port mappings, but other methods
could be used.



In summary, the ppt describes 4 options-

Drawing 1 - No muxing - Stun request, bind for two ports and send
PubPorts with RAMS-R to signal both, followed by the burst.
Drawing 2 - Muxing - Stun request, bind for one port and send PubPorts
with RAMS-R to signal a single port, followed by the burst.
Drawing 3 - Muxing - No explicit STUN request/bind. Send PubPorts with
RAMS-R to signal RS to use the src port of the incoming RTCP packet as
the destination for both RTP and RTCP in the ret session (We do this by
putting 0's in the pubports messages). Note that this does not work
through all NAT variants. The RAMS-R/PubPorts message is sent from c4 to
P2. The burst is sent from P4 to c4', and certain NATs will not pass
this traffic.
Drawing 4 - Muxing - No explicite STUN request/bind. Send PubPorts from
c4 to P4, initializing NAT bindings. Send RAMS-R, followed by the burst.
This works through all NAT types. There is concern about the decoupling
of the PubPorts from the RAMS-R, as dropped messages may cause problems.

Hopefully this note clarifies the need to signal the ports.

Inputs on ths problem are desired. We need to decide if the PubPorts is
the right way to go, and if the transaction is RAMS specific or is a
generic RTP/RTCP message. Once we make that determination, we need to
lay out the details of the message format.=20

Based on the feedback - we will abandon the idea, keep it in the draft,
or write a separate draft for it.

Bill VerSteeg (with extensive input from Ali Begen and Dan Wing)

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Zeev Vax
Sent: Thursday, June 18, 2009 5:58 PM
To: Ali C. Begen (abegen); Roni Even; Bill Ver Steeg (versteb);
VANCAENEGEM Tom; avt@ietf.org
Subject: Re: [AVT] comments on
section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01

If we assume all entities are one, why would you need to signal the
retransmission port separately ?

Zeev

From versteb@cisco.com  Wed Jun 24 08:01:07 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 D7FE03A6767 for <avt@core3.amsl.com>; Wed, 24 Jun 2009 08:01:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.662
X-Spam-Level: 
X-Spam-Status: No, score=-6.662 tagged_above=-999 required=5 tests=[AWL=-0.063, 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 tDukgOSKpyGN for <avt@core3.amsl.com>; Wed, 24 Jun 2009 08:01:06 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id C9B4F3A6894 for <avt@ietf.org>; Wed, 24 Jun 2009 08:01:06 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,283,1243814400"; d="scan'208";a="204996850"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by sj-iport-1.cisco.com with ESMTP; 24 Jun 2009 14:57:31 +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 n5OEvVn8030502;  Wed, 24 Jun 2009 10:57:31 -0400
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.14.3) with ESMTP id n5OEvVp6005050; Wed, 24 Jun 2009 14:57:31 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.3959);  Wed, 24 Jun 2009 10:57:31 -0400
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: Wed, 24 Jun 2009 10:57:31 -0400
Message-ID: <81B9B88E2F9D574AA5328A85547CDE91017F58E3@xmb-rtp-21d.amer.cisco.com>
In-Reply-To: <91C724EB-3FAD-4745-867D-E350AEFEC922@csperkins.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] I-D Action:draft-ietf-avt-rapid-acquisition-for-rtp-01.txt
Thread-Index: AcnyZwTDrlZYVWn1R6GltvJkoFTseQCc/b5g
References: <20090616154501.5B37B28C188@core3.amsl.com> <91C724EB-3FAD-4745-867D-E350AEFEC922@csperkins.org>
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "Colin Perkins" <csp@csperkins.org>, "Audio/Video Transport (AVT) WG" <avt@ietf.org>
X-OriginalArrivalTime: 24 Jun 2009 14:57:31.0624 (UTC) FILETIME=[19997680:01C9F4DC]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3277; t=1245855451; x=1246719451; 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=20[AVT]=20I-D=20Action=3Adraft-ietf-avt-r apid-acquisition-for-rtp-01.txt |Sender:=20 |To:=20=22Colin=20Perkins=22=20<csp@csperkins.org>,=0A=20=2 0=20=20=20=20=20=20=22Audio/Video=20Transport=20(AVT)=20WG=2 2=20<avt@ietf.org>; bh=keUPNhHldu3R7XGncQocJa8TUEChG1pWYJQnetkM6Jw=; b=j4b9T/dU3LdS4hhh9H1zG1KhyCbmkBG+DHtyT3MJvzuj/D4NKXGK2kScfL zWxkqR0T4roAcxObpKyDvQpdSBBjuvVb7cTwCWb6AMKGJxOuUfmIyxms6zq3 gFFw7eMdoh;
Authentication-Results: rtp-dkim-2; header.From=versteb@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); 
Subject: Re: [AVT] I-D Action:draft-ietf-avt-rapid-acquisition-for-rtp-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, 24 Jun 2009 15:01:07 -0000

Colin -

Thanks for the detailed feedback. I agree with Ali's responses.=20

Regarding your last item - I agree that NAT presents some challenges in
this environment. We have recently sent an analysis of the NAT issues
described in sections 9 an 10 to the AVT list. We have tried to
summarize the 4 alternative NAT solutions that have been suggested,
showing the up-side and down-side of each. I would love to see a more
elegant solution to this dificult problem, and look forward to feedback
from the list.

Bill VerSteeg=20

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Colin Perkins
Sent: Sunday, June 21, 2009 7:54 AM
To: Audio/Video Transport (AVT) WG
Subject: Re: [AVT] I-D
Action:draft-ietf-avt-rapid-acquisition-for-rtp-01.txt

On 16 Jun 2009, at 16:45, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts=20
> directories.
> This draft is a work item of the Audio/Video Transport Working Group=20
> of the IETF.
>
>   Title     : Unicast-Based Rapid Acquisition of Multicast RTP =20
> Sessions
>   Author(s) : B. Steeg, et al.
>   Filename  : draft-ietf-avt-rapid-acquisition-for-rtp-01.txt
>   Pages     : 41
>   Date      : 2009-06-16

I had some minor comments:

Section 6: Do the RR and RS send the usual periodic RTCP reports on the
retransmission session? I assume they do, but it'd be good to state that
explicitly to avoid confusion.


Section 7: Are the RAMS messages sent as part of compound RTCP packets,
or is the non-compound extension assumed? I can see advantages to using
compound packets, and it would be good if the draft explicitly stated
that they were used, according to the usual rules.


Section 7: Have you considered using several feedback message type
(FMT) values, one for each of the RAMS-R, RAMS-I, and RAMS-T messages,
instead of a single value with subtypes? It's not clear that the extra
level of indirection buys anything.

Section 7.3: The Earliest Multicast Join Time and Burst Duration both
specify times. The latter is specified in RTP clock units, the former
says you need to decide between milliseconds and RTP clock units. It
would make things easier for implementers if these were both the same.

Section 7.3: Is there any reason why a server would switch between
supporting and not supporting updated requests within a single session?
If not, then the S bit might be better signalled in the SDP, rather than
in-band in each message.

Section 7.3 and 7.4: It's not clear why extended RTP sequence numbers
are used, since the top 16 bits are always zero.

Section 7.3 "Note that if the RAMS requests has been accepted, RS MUST
send this field as least once": Why is this a MUST? The RR must be able
to work without this field, since the RAMS-I packet might be lost, so
while I can see why this should be a SHOULD, I don't see the motivation
for a MUST.

Section 9: As I've mentioned off-line to the authors, I don't find this
compelling.

Cheers,
Colin



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



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

From Tom.Van_Caenegem@alcatel-lucent.be  Thu Jun 25 03:47:18 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 98BB83A6CE1 for <avt@core3.amsl.com>; Thu, 25 Jun 2009 03:47:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.916
X-Spam-Level: 
X-Spam-Status: No, score=-5.916 tagged_above=-999 required=5 tests=[AWL=0.333,  BAYES_00=-2.599, HELO_EQ_FR=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 LMAYpAEVy+1p for <avt@core3.amsl.com>; Thu, 25 Jun 2009 03:47:17 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by core3.amsl.com (Postfix) with ESMTP id A25993A69E1 for <avt@ietf.org>; Thu, 25 Jun 2009 03:47:16 -0700 (PDT)
Received: from FRVELSBHS02.ad2.ad.alcatel.com (frvelsbhs02.dc-m.alcatel-lucent.com [155.132.6.74]) by smail3.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5PAYnKA018163;  Thu, 25 Jun 2009 12:34:50 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.51]) by FRVELSBHS02.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 25 Jun 2009 12:34:49 +0200
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: Thu, 25 Jun 2009 12:34:48 +0200
Message-ID: <238382595265324EA50F6134BB42DCAF04137224@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Port mappings, NAT, and RAMS
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDgARoKBSAALhpHsA==
References: <mailman.10085.1245185397.4936.avt@ietf.org><238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com><015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com><238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com><04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com><81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com><3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com><025401c9effa$34040170$9c0c0450$%roni@huawei.com><3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com><04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com>
From: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>
To: "Bill Ver Steeg (versteb)" <versteb@cisco.com>, "Zeev Vax" <zeevvax@microsoft.com>, "Ali C. Begen (abegen)" <abegen@cisco.com>, "Roni Even" <Even.roni@huawei.com>, <avt@ietf.org>
X-OriginalArrivalTime: 25 Jun 2009 10:34:49.0697 (UTC) FILETIME=[912C0510:01C9F580]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.83
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 25 Jun 2009 10:47:18 -0000

Bill,

Thanks for presenting so clearly the different options. A few opinions
here:

-For option 3 and 4, a STUN server is not involved, so perhaps the
associated slides should not mention a STUN server there.

-For option 3, the pub-port message is in fact not needed, not from the
NAPT point of view, and not from the RS point of view if we consider a
clause saying that the RR only needs to send a pub-port message to the
RS (Feedback Target) when it does NOT want to receive the RTP/RTCP
burst/retransmission packets on the same port as the source port on
which the RR sent out the RAMS-R or NACK RTCP message (hence no need to
define "zero" port values). Of course the RR can only do so, if it
supports RTP/RTCP muxing itself, and if it knows the RS supports
RTP/RTCP muxing too (as indicated in the declarative sdp received by the
RR)=20

-Don't we also allow that for option 3, the port P2 actually equals port
P4? This is a kind of hybrid of session and SSRC multiplexing of the
primary multicast RTP stream and the retransmission/acceleration session
:  on the unidirectional RTP layer, the primary MC packets and the
unicast retransmission packets are clearly session muxed, but the RTCP
"return" channel for both streams have exactly the same transport
addresses, but are distinguished by means of a different SSRC.  In that
case, the NAPT will always work and there is (again) no need for a
pub-port message. The RTP receiver of course needs to know whether the
RS supports this port/multiplexing scheme and this could be solved  by
means of defining a new atribute in SDP, that is then included in the
declarative SDP.=20

With this, I am not saying that I do not want to define the pub-port
message because RTP receivers that want to choose themselves which ports
are used for the acceleration session should rely on the pub-port
message to signal this to the RS (option 1 and 2) and to circumvent the
NAPT when using option 4.

For option 4, the pub-port message is used to make the NAPT binding. And
each time a RR asks for a retransmission , the RR may have to send a
pubreport message, because the NAPT bindings have a limited lifetime. It
is not clear to me whether for all options you considered, the
pub-report message is always sent whenever a  NACK is sent?  Or would
you recommend saying that it must be sent when a RAMS-R is sent
(obviously), and then during the acceleration/retransmission session it
is never sent anymore for option 1 and 2 (as the RS keeps state), and
for option 4 in your slides it is up to the RR to decide when to
transmit the pub-port, based on its knowledge of NAT binding lifetime?


In summary, my opinions are the following:

-the pub-port message is only used by the RR to signal a dedicated set
of ports to the RS on which it wants to receive the RTP/RTCP burst and
retransmission packets. This is option 1 and 2. For an acceleration
(+retransmission) session, the pub-port is sent once in a compound
together with RAMS-R, and for a retransmission-only session (no
RAMS/acceleration involved), it is sent in a compound together with the
1st issued NACK. For subsequent NACKs, there is no need to send the
pub-report along.
=20
-when the declarative SDP indicates that the RS supports RTP/RTCP
muxing, and the RR does not use the pub-port message, the RR expects the
retransmission/burts packets on the same port on which it sent out the
RAMS-R or the NACK RTCP message.

-when additionally the declarative SDP indicates with a new attribute
that the RS is prepared to use as source port for the
burst/retransmission packets the ports used by the RR for the
burst/retransmission request, the RR expects the RS to use the same
ports (source and destination) for the retransmission/burts packets as
used by the receiver in the RAMS-R or the NACK RTCP message (but
reversed of course). The new SDP attribute could include a range of
ports out which the RTP receiver needs to select a value that it will
use as destination port for the RAMS-R or NACK. =20

I would also be in favour that we mandate an RS to support RTP/RTCP
muxing, such that an RTP receiver can always make a choice which scheme
to follow.

I think it would make more sense to describe this whole solution with
the pub-port message definition and new SDP attribute as well as the
STUN message exchange in a separate draft as it is also applicable to
solutions making use of RTCP FB messages for retransmission only (RTCP
NACK), but with no need for rapid acquisition.=20

Regards,
Tom=20

-----Original Message-----
From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]=20
Sent: woensdag 24 juni 2009 14:37
To: Zeev Vax; Ali C. Begen (abegen); Roni Even; VAN CAENEGEM Tom;
avt@ietf.org
Subject: Port mappings, NAT, and RAMS

=20
There has been some discussion around the requirement for a NAT section
in the latest RAMS draft. This note is an attempt to clarify the
requirement to signal RAMS port mappings. Once we come to a consensus as
to the desired behavior, we can update the draft.

This text refers to a ppt document that can be found at
ftp://ftpeng.cisco.com/abegen/PubPorts.pdf

When using RAMS to accelerate acquisition of a multicast flow, there are
two sessions - the primary multicast session and the acceleration
session. These sessions may have multiple socket contexts, depending on
the use of RTP/RTP port muxing. However, the primary multicast session
and the retransmission session are always distinct.

1- The primary multicast session - two logical flows defined by the
Source address, Destination Multicast Address, RTP port (P1) and RTCP
port(P2). This set of flows is shown in RED in the diagram.
2- The retransmission/acceleration session, shown in BLUE in the
diagram. In the most general non-port-muxed, non-NATed case, this stream
consists of 2 flows. The first (RTP) flow is defined by the 5-tuple of
UDP, IP address of the FT, RTP port configured by SDP (P3),  the IP
address of the client and the RTP port dynamically chosen by RR (c3).
The second (RTCP) flow is defined by the 5-tuple of UDP, FT address, the
RTCP port defined by SDP (P4), the IP address of the client and the RTCP
port dynamically chosen by RR (c4). When RTP/RTCP port muxing is used,
the retransmission session is collapsed onto a single 5-tuple.

Note that the feedback target for the primary session is P2 on FT/RS.
Note that the acceleration burst must flow from FT P3/P4 to C c3/c4. In
other words, the first desired data flow on the retransmission session
is "downstream".=20

When we introduce NAT, we need to map c3 to c3' (and in the absence of
port muxing, also c4 to c4') through the NAT device. This diagram shows
the use of STUN in YELLOW to setup the port mappings, but other methods
could be used.



In summary, the ppt describes 4 options-

Drawing 1 - No muxing - Stun request, bind for two ports and send
PubPorts with RAMS-R to signal both, followed by the burst.
Drawing 2 - Muxing - Stun request, bind for one port and send PubPorts
with RAMS-R to signal a single port, followed by the burst.
Drawing 3 - Muxing - No explicit STUN request/bind. Send PubPorts with
RAMS-R to signal RS to use the src port of the incoming RTCP packet as
the destination for both RTP and RTCP in the ret session (We do this by
putting 0's in the pubports messages). Note that this does not work
through all NAT variants. The RAMS-R/PubPorts message is sent from c4 to
P2. The burst is sent from P4 to c4', and certain NATs will not pass
this traffic.
Drawing 4 - Muxing - No explicite STUN request/bind. Send PubPorts from
c4 to P4, initializing NAT bindings. Send RAMS-R, followed by the burst.
This works through all NAT types. There is concern about the decoupling
of the PubPorts from the RAMS-R, as dropped messages may cause problems.

Hopefully this note clarifies the need to signal the ports.

Inputs on ths problem are desired. We need to decide if the PubPorts is
the right way to go, and if the transaction is RAMS specific or is a
generic RTP/RTCP message. Once we make that determination, we need to
lay out the details of the message format.=20

Based on the feedback - we will abandon the idea, keep it in the draft,
or write a separate draft for it.

Bill VerSteeg (with extensive input from Ali Begen and Dan Wing)

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Zeev Vax
Sent: Thursday, June 18, 2009 5:58 PM
To: Ali C. Begen (abegen); Roni Even; Bill Ver Steeg (versteb);
VANCAENEGEM Tom; avt@ietf.org
Subject: Re: [AVT] comments on
section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01

If we assume all entities are one, why would you need to signal the
retransmission port separately ?

Zeev

From rsf@ns.live555.com  Thu Jun 25 03:57:40 2009
Return-Path: <rsf@ns.live555.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 8554E3A6CAB; Thu, 25 Jun 2009 03:57:40 -0700 (PDT)
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 nxUokl3yp-3H; Thu, 25 Jun 2009 03:57:39 -0700 (PDT)
Received: from ns.live555.com (ns.live555.com [4.79.217.242]) by core3.amsl.com (Postfix) with ESMTP id B25383A6950; Thu, 25 Jun 2009 03:57:39 -0700 (PDT)
Received: from ns.live555.com (localhost.live555.com [127.0.0.1]) by ns.live555.com (8.14.3/8.14.3) with ESMTP id n5PAuvoV027603; Thu, 25 Jun 2009 03:56:57 -0700 (PDT) (envelope-from rsf@ns.live555.com)
Received: (from rsf@localhost) by ns.live555.com (8.14.3/8.14.3/Submit) id n5PAuvpS027596; Thu, 25 Jun 2009 03:56:57 -0700 (PDT) (envelope-from rsf)
Mime-Version: 1.0
Message-Id: <f06240807c668f32010ca@[66.80.62.44]>
In-Reply-To: <p06240859c6542b53968f@[10.0.1.8]>
References: <20090609024502.05A883A67F6@core3.amsl.com> <8987F5DB-1395-44F3-A4F0-44725FCC3D7E@gbiv.com> <p06240859c6542b53968f@[10.0.1.8]>
Date: Thu, 25 Jun 2009 03:56:51 -0700
To: avt@ietf.org, mmusic@ietf.org
From: Ross Finlayson <finlayson@live555.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Subject: Re: [AVT] I-D Action:draft-pantos-http-live-streaming-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, 25 Jun 2009 10:57:40 -0000

I am pleased that Apple submitted this document as an Internet Draft. 
While I feel that much of the subsequent criticism has been 
excessively harsh (or in some cases, misguided), I do agree with the 
criticism that the document's title could be more descriptive.  The 
current title - "HTTP Live Streaming" - suggests that it is a broad, 
architectural overview document, which this really isn't.  A more 
meaningful title for this document might be something like
	"Using URI Playlist Files to Simulate Live Streaming"

Nonetheless, if this approach is seen as being useful, then I would 
like to see the IETF adopting and standardizing it (or something 
similar), because both media streaming and transport protocols 
(including HTTP/TCP - the transport protocol most commonly specified 
within URIs) are clearly within the IETF's arena.

However, this document focuses attention on a much bigger issue - a 
proverbial "elephant in the room" - that at some point the IETF in 
general, and the MMUSIC and AVT working groups in particular, are 
going to have to address:

Thanks to the ever increasing abundance of cheap mass storage, we are 
now in a world where media consumption is increasingly 'on demand' - 
e.g, via DVRs or online services like YouTube - rather than live.  It 
seems inevitable that on-demand media playback will dominate, with 
live media being relegated to relatively minor niches where 
timeliness remains essential.

Given this, we have to ask ourselves whether there is going to 
continue to be a practical role for specialized protocols for live 
media, or whether we will see more and more of the live media niches 
being satisfied by hacks (like the one described by this draft) that 
can make use of the increasingly dominant infrastructure that will 
already be in place for on-demand media?  Telephony currently remains 
a refuge for live media protocols, but how much beyond this in the 
future?  (There are even companies out there now that are providing 
videoconferencing over HTTP, within users' web browsers!)

I believe that, at the very least, the IETF should try to be more 
pragmatic about this (even if it means sometimes tarnishing 
architectural purity).  To give just one specific example, I'm 
disappointed that the IETF did not adopt and standardize Apple's 
earlier mechanism (developed several years ago) for tunneling 
RTSP/RTP over HTTP.  But given the points that I note above, I think 
we're going to have to think hard about the future of RTSP in 
general...

From abegen@cisco.com  Thu Jun 25 09:03:13 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 79F173A6A2E for <avt@core3.amsl.com>; Thu, 25 Jun 2009 09:03:13 -0700 (PDT)
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 RDtJaCFs4cON for <avt@core3.amsl.com>; Thu, 25 Jun 2009 09:03:11 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id C8FA73A6945 for <avt@ietf.org>; Thu, 25 Jun 2009 09:03:11 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,290,1243814400"; d="scan'208";a="331705134"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 25 Jun 2009 15:59:42 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n5PFxgED009178;  Thu, 25 Jun 2009 08:59:42 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n5PFxgZS023454; Thu, 25 Jun 2009 15:59:42 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 25 Jun 2009 08:59:42 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 25 Jun 2009 08:57:46 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D54099DFD1A@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <238382595265324EA50F6134BB42DCAF04137224@FRVELSMBS22.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Port mappings, NAT, and RAMS
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDgARoKBSAALhpHsAAKg7ng
References: <mailman.10085.1245185397.4936.avt@ietf.org><238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com><015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com><238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com><04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com><81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com><3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com><025401c9effa$34040170$9c0c0450$%roni@huawei.com><3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com><04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04137224@FRVELSMBS22.ad2.ad.alcatel.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>, "Bill Ver Steeg (versteb)" <versteb@cisco.com>, "Zeev Vax" <zeevvax@microsoft.com>, "Roni Even" <Even.roni@huawei.com>,  <avt@ietf.org>
X-OriginalArrivalTime: 25 Jun 2009 15:59:42.0279 (UTC) FILETIME=[F3A7FD70:01C9F5AD]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=11859; t=1245945582; x=1246809582; 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=20Port=20mappings,=20NAT,=20and=20RAMS |Sender:=20; bh=CXm4g7yJ3MRn/2fK49bCRg/mdZcQxmw8LTQ/hk4MJFI=; b=HzgF/gd3NLBj9S7dlYZxvsScbIlG9zG/P4b4E0u9khdqcLmlYegn1Px6VE J5Phz6cRUmKxevWRV3qbiIg8T506FpPKLGXi+qh4rBUv6A5MgK2x/Coo8STQ VX+l41AyOB;
Authentication-Results: sj-dkim-4; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 25 Jun 2009 16:03:13 -0000

Hi Tom,

A few quick comments inline.

> -----Original Message-----
> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> Sent: Thursday, June 25, 2009 3:35 AM
> To: Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen (abegen); Roni =
Even; avt@ietf.org
> Subject: RE: Port mappings, NAT, and RAMS
>=20
> Bill,
>=20
> Thanks for presenting so clearly the different options. A few opinions
> here:
>=20
> -For option 3 and 4, a STUN server is not involved, so perhaps the
> associated slides should not mention a STUN server there.

Yup. It can be removed.

=20
> -For option 3, the pub-port message is in fact not needed, not from =
the
> NAPT point of view, and not from the RS point of view if we consider a
> clause saying that the RR only needs to send a pub-port message to the
> RS (Feedback Target) when it does NOT want to receive the RTP/RTCP
> burst/retransmission packets on the same port as the source port on
> which the RR sent out the RAMS-R or NACK RTCP message (hence no need =
to
> define "zero" port values). Of course the RR can only do so, if it

The reason why we need pubports is that it indicates "explicitly" the =
port the client wants to use to receive the burst is the port it used to =
send the RAMS-R/pubports message. I believe we need this explicit =
indication, ow, we will be making an implicit assumption. Note that the =
rams-r/pubports is in the primary session and burst/ret packets are in =
the retransmission session, which is different than the primary.

As far as I can see, not everybody agrees on this point, but we need to =
make a decision here before we mandate anything.


> supports RTP/RTCP muxing itself, and if it knows the RS supports
> RTP/RTCP muxing too (as indicated in the declarative sdp received by =
the
> RR)
>=20
> -Don't we also allow that for option 3, the port P2 actually equals =
port
> P4? This is a kind of hybrid of session and SSRC multiplexing of the
> primary multicast RTP stream and the retransmission/acceleration =
session
> :  on the unidirectional RTP layer, the primary MC packets and the
> unicast retransmission packets are clearly session muxed, but the RTCP
> "return" channel for both streams have exactly the same transport
> addresses, but are distinguished by means of a different SSRC.  In =
that

How? Since SSM and retransmission sessions are session muxed, they have =
the same SSRC. When a client is sending a receiver report, how do we =
identify which session it belongs to? So, I believe P2 should be =
different than P4.

> case, the NAPT will always work and there is (again) no need for a
> pub-port message. The RTP receiver of course needs to know whether the
> RS supports this port/multiplexing scheme and this could be solved  by
> means of defining a new atribute in SDP, that is then included in the
> declarative SDP.
>=20
> With this, I am not saying that I do not want to define the pub-port
> message because RTP receivers that want to choose themselves which =
ports
> are used for the acceleration session should rely on the pub-port
> message to signal this to the RS (option 1 and 2) and to circumvent =
the
> NAPT when using option 4.
>=20
> For option 4, the pub-port message is used to make the NAPT binding. =
And
> each time a RR asks for a retransmission , the RR may have to send a
> pubreport message, because the NAPT bindings have a limited lifetime. =
It
> is not clear to me whether for all options you considered, the
> pub-report message is always sent whenever a  NACK is sent?  Or would

This is a very good point. If RS/FT address changes for each SSM =
session, then a new pubports is needed to bind the correct address/port =
on the NAT. And similar to RAMS-R, NACK would also require a pubports =
message whenever a binding is needed for regular retransmission.=20

But, the main problem here is that we are separating the RAMS-R/NACK =
from the pubports message. Now, assume that we sent RAMS-R and pubports =
for session 1, and suppose pubports message made it but RAMS-R was lost. =
Then, we switched to session 2, sent a new RAMS-R and pubports. Then, we =
switched back to session 1, sending a new RAMS-R and pubports. Now, RS =
may get confused since it may not accurately match the outstanding =
RAMS-R and pubports messages. In the RAMS-R message, the parameters may =
have changed (such as burst bitrate). In the pubports, port mappings may =
have changed. As a result, RS may send the burst to the wrong port =
and/or the burst may be at a lower or higher bitrate than RR wants to =
have.

In other words, we are introducing new failure modes and this is a big =
concern for option 4, IMO.


> you recommend saying that it must be sent when a RAMS-R is sent
> (obviously), and then during the acceleration/retransmission session =
it
> is never sent anymore for option 1 and 2 (as the RS keeps state), and
> for option 4 in your slides it is up to the RR to decide when to
> transmit the pub-port, based on its knowledge of NAT binding lifetime?

As long as the binding does not expire (meaning there is some =
transmission on that path), we should be fine. And I believe there are =
certain guidelines listed in the STUN spec.

-acbegen
=20
>=20
> In summary, my opinions are the following:
>=20
> -the pub-port message is only used by the RR to signal a dedicated set
> of ports to the RS on which it wants to receive the RTP/RTCP burst and
> retransmission packets. This is option 1 and 2. For an acceleration
> (+retransmission) session, the pub-port is sent once in a compound
> together with RAMS-R, and for a retransmission-only session (no
> RAMS/acceleration involved), it is sent in a compound together with =
the
> 1st issued NACK. For subsequent NACKs, there is no need to send the
> pub-report along.
>=20
> -when the declarative SDP indicates that the RS supports RTP/RTCP
> muxing, and the RR does not use the pub-port message, the RR expects =
the
> retransmission/burts packets on the same port on which it sent out the
> RAMS-R or the NACK RTCP message.
>=20
> -when additionally the declarative SDP indicates with a new attribute
> that the RS is prepared to use as source port for the
> burst/retransmission packets the ports used by the RR for the
> burst/retransmission request, the RR expects the RS to use the same
> ports (source and destination) for the retransmission/burts packets as
> used by the receiver in the RAMS-R or the NACK RTCP message (but
> reversed of course). The new SDP attribute could include a range of
> ports out which the RTP receiver needs to select a value that it will
> use as destination port for the RAMS-R or NACK.
>=20
> I would also be in favour that we mandate an RS to support RTP/RTCP
> muxing, such that an RTP receiver can always make a choice which =
scheme
> to follow.
>=20
> I think it would make more sense to describe this whole solution with
> the pub-port message definition and new SDP attribute as well as the
> STUN message exchange in a separate draft as it is also applicable to
> solutions making use of RTCP FB messages for retransmission only (RTCP
> NACK), but with no need for rapid acquisition.
>=20
> Regards,
> Tom
>=20
> -----Original Message-----
> From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> Sent: woensdag 24 juni 2009 14:37
> To: Zeev Vax; Ali C. Begen (abegen); Roni Even; VAN CAENEGEM Tom;
> avt@ietf.org
> Subject: Port mappings, NAT, and RAMS
>=20
>=20
> There has been some discussion around the requirement for a NAT =
section
> in the latest RAMS draft. This note is an attempt to clarify the
> requirement to signal RAMS port mappings. Once we come to a consensus =
as
> to the desired behavior, we can update the draft.
>=20
> This text refers to a ppt document that can be found at
> ftp://ftpeng.cisco.com/abegen/PubPorts.pdf
>=20
> When using RAMS to accelerate acquisition of a multicast flow, there =
are
> two sessions - the primary multicast session and the acceleration
> session. These sessions may have multiple socket contexts, depending =
on
> the use of RTP/RTP port muxing. However, the primary multicast session
> and the retransmission session are always distinct.
>=20
> 1- The primary multicast session - two logical flows defined by the
> Source address, Destination Multicast Address, RTP port (P1) and RTCP
> port(P2). This set of flows is shown in RED in the diagram.
> 2- The retransmission/acceleration session, shown in BLUE in the
> diagram. In the most general non-port-muxed, non-NATed case, this =
stream
> consists of 2 flows. The first (RTP) flow is defined by the 5-tuple of
> UDP, IP address of the FT, RTP port configured by SDP (P3),  the IP
> address of the client and the RTP port dynamically chosen by RR (c3).
> The second (RTCP) flow is defined by the 5-tuple of UDP, FT address, =
the
> RTCP port defined by SDP (P4), the IP address of the client and the =
RTCP
> port dynamically chosen by RR (c4). When RTP/RTCP port muxing is used,
> the retransmission session is collapsed onto a single 5-tuple.
>=20
> Note that the feedback target for the primary session is P2 on FT/RS.
> Note that the acceleration burst must flow from FT P3/P4 to C c3/c4. =
In
> other words, the first desired data flow on the retransmission session
> is "downstream".
>=20
> When we introduce NAT, we need to map c3 to c3' (and in the absence of
> port muxing, also c4 to c4') through the NAT device. This diagram =
shows
> the use of STUN in YELLOW to setup the port mappings, but other =
methods
> could be used.
>=20
>=20
>=20
> In summary, the ppt describes 4 options-
>=20
> Drawing 1 - No muxing - Stun request, bind for two ports and send
> PubPorts with RAMS-R to signal both, followed by the burst.
> Drawing 2 - Muxing - Stun request, bind for one port and send PubPorts
> with RAMS-R to signal a single port, followed by the burst.
> Drawing 3 - Muxing - No explicit STUN request/bind. Send PubPorts with
> RAMS-R to signal RS to use the src port of the incoming RTCP packet as
> the destination for both RTP and RTCP in the ret session (We do this =
by
> putting 0's in the pubports messages). Note that this does not work
> through all NAT variants. The RAMS-R/PubPorts message is sent from c4 =
to
> P2. The burst is sent from P4 to c4', and certain NATs will not pass
> this traffic.
> Drawing 4 - Muxing - No explicite STUN request/bind. Send PubPorts =
from
> c4 to P4, initializing NAT bindings. Send RAMS-R, followed by the =
burst.
> This works through all NAT types. There is concern about the =
decoupling
> of the PubPorts from the RAMS-R, as dropped messages may cause =
problems.
>=20
> Hopefully this note clarifies the need to signal the ports.
>=20
> Inputs on ths problem are desired. We need to decide if the PubPorts =
is
> the right way to go, and if the transaction is RAMS specific or is a
> generic RTP/RTCP message. Once we make that determination, we need to
> lay out the details of the message format.
>=20
> Based on the feedback - we will abandon the idea, keep it in the =
draft,
> or write a separate draft for it.
>=20
> Bill VerSteeg (with extensive input from Ali Begen and Dan Wing)
>=20
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Zeev Vax
> Sent: Thursday, June 18, 2009 5:58 PM
> To: Ali C. Begen (abegen); Roni Even; Bill Ver Steeg (versteb);
> VANCAENEGEM Tom; avt@ietf.org
> Subject: Re: [AVT] comments on
> section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
> If we assume all entities are one, why would you need to signal the
> retransmission port separately ?
>=20
> Zeev

From oran@cisco.com  Thu Jun 25 13:06:12 2009
Return-Path: <oran@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 35D3C3A6AF8 for <avt@core3.amsl.com>; Thu, 25 Jun 2009 13:06:12 -0700 (PDT)
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 ku1JAyq4CGkX for <avt@core3.amsl.com>; Thu, 25 Jun 2009 13:06:11 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 3E4013A6B7C for <avt@ietf.org>; Thu, 25 Jun 2009 13:06:11 -0700 (PDT)
X-Files: PGP.sig : 195
X-IronPort-AV: E=Sophos;i="4.42,292,1243814400";  d="sig'?scan'208";a="205742962"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-1.cisco.com with ESMTP; 25 Jun 2009 20:04:50 +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 n5PK4q24026290 for <avt@ietf.org>; Thu, 25 Jun 2009 13:04:52 -0700
Received: from stealth-10-32-245-158.cisco.com (stealth-10-32-245-158.cisco.com [10.32.245.158]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id n5PK4etw011710 for <avt@ietf.org>; Thu, 25 Jun 2009 20:04:51 GMT
Received: from [127.0.0.1] by stealth-10-32-245-158.cisco.com (PGP Universal service); Thu, 25 Jun 2009 16:04:51 -0400
X-PGP-Universal: processed; by stealth-10-32-245-158.cisco.com on Thu, 25 Jun 2009 16:04:51 -0400
Message-Id: <80B6378F-535F-4D96-B228-F66466ACD809@cisco.com>
From: David R Oran <oran@cisco.com>
To: Alan Clark <alan.d.clark@telchemy.com>
In-Reply-To: <C6613053.8349%alan.d.clark@telchemy.com>
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Thu, 25 Jun 2009 16:04:35 -0400
References: <C6613053.8349%alan.d.clark@telchemy.com>
X-Mailer: Apple Mail (2.935.3)
X-PGP-Encoding-Format: MIME
X-PGP-Encoding-Version: 2.0.2
Content-Type: multipart/signed; boundary="PGP_Universal_8DC5BBED_06843033_42188D73_8434C30E"; protocol="application/pgp-signature"; micalg="pgp-sha1"
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2268; t=1245960292; x=1246824292; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=oran@cisco.com; z=From:=20David=20R=20Oran=20<oran@cisco.com> |Subject:=20Re=3A=20[AVT]=20Sound=20Level=20Indicators |Sender:=20; bh=Yn2zw5l6A18DlxEhTveacbTwTvn/iM8HKnStYxXSHtc=; b=epk2VAK5KsvHiQh0rMvamPl0VBznWnHLSau+oeOPuCMD2hXGVGXCZpO/rn jykc89EQFvaeoIytNd4Pa6i1RFdtSmbfmdG02M1qYCvzr9f/Kucq6/BiNKPw uqElChlj7M;
Authentication-Results: sj-dkim-4; header.From=oran@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Cc: Colin Perkins <csp@csperkins.org>, Org <avt@ietf.org>
Subject: Re: [AVT] Sound Level Indicators
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, 25 Jun 2009 20:06:12 -0000

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


On Jun 19, 2009, at 12:08 PM, Alan Clark wrote:

>
> A parallel problem is the control (rather than indication) of volume  
> and
> noise suppression in VoIP calls.  911 operators find that sometimes  
> they do
> want noise suppression and sometimes they don't.  Noise suppression  
> can be
> helpful when they are trying to understand a caller in a noisy  
> background
> environment however it can also suppress background noises that can  
> help to
> understand the emergency situation (e.g. if they hearing kids  
> laughing in
> the background the call may be a prank (which does happen quite  
> frequently)
> but other sounds may indicate how serious a problem is or provide  
> location
> information).
>
I would think the right mechanism for this would be CCM (Codec Control  
messages), not header extensions.

> Alan
>
>
>
> On 6/19/09 11:46 AM, "Colin Perkins" <csp@csperkins.org> wrote:
>
>> On 15 Jun 2009, at 15:35, Emil Ivov wrote:
>>> We have just submitted the following draft:
>>>
>>> http://www.ietf.org/internet-drafts/draft-ivov-avt-slic-00.txt
>>>
>>> The draft proposes a solution for a problem that's been extensively
>>> discussed on the dispatch mailing list during the past few weeks. It
>>> concerned a means of transporting sound level in conferences in a  
>>> way
>>> that would allow presenting it to the user and extending the active
>>> speaker concept.
>>
>>
>> I haven't been following dispatch, but this looks like a good use of
>> the RTP header extension mechanism.
>
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


--PGP_Universal_8DC5BBED_06843033_42188D73_8434C30E
Content-Type: application/pgp-signature;
	x-mac-type=70674453;
	name=PGP.sig
Content-Disposition: attachment; filename=PGP.sig

-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.10.0 (Build 500)

iQA/AwUBSkPYXY1mhLZU3SrmEQKiDwCgpPX4IXy/bcsE4aICZreY42ZRJxQAnR4e
SaEGT1wRi34vKuECfcVYslSD
=JkND
-----END PGP SIGNATURE-----

--PGP_Universal_8DC5BBED_06843033_42188D73_8434C30E--

From rjesup@wgate.com  Thu Jun 25 14:11:54 2009
Return-Path: <rjesup@wgate.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 A134C3A697A for <avt@core3.amsl.com>; Thu, 25 Jun 2009 14:11:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.643
X-Spam-Level: 
X-Spam-Status: No, score=-1.643 tagged_above=-999 required=5 tests=[AWL=0.091,  BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RDNS_DYNAMIC=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 F4LRSpWtAV9z for <avt@core3.amsl.com>; Thu, 25 Jun 2009 14:11:53 -0700 (PDT)
Received: from exchange1.wgate.com (pr-66-150-46-254.wgate.com [66.150.46.254]) by core3.amsl.com (Postfix) with ESMTP id C2D623A6817 for <avt@ietf.org>; Thu, 25 Jun 2009 14:11:53 -0700 (PDT)
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 25 Jun 2009 16:18:19 -0400
To: David R Oran <oran@cisco.com>
References: <C6613053.8349%alan.d.clark@telchemy.com> <80B6378F-535F-4D96-B228-F66466ACD809@cisco.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Thu, 25 Jun 2009 16:18:53 -0400
In-Reply-To: <80B6378F-535F-4D96-B228-F66466ACD809@cisco.com> (David R. Oran's message of "Thu\, 25 Jun 2009 16\:04\:35 -0400")
Message-ID: <ybu63ek83te.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 25 Jun 2009 20:18:19.0084 (UTC) FILETIME=[146488C0:01C9F5D2]
Cc: Colin Perkins <csp@csperkins.org>, avt@ietf.org
Subject: Re: [AVT] Sound Level Indicators
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
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, 25 Jun 2009 21:11:54 -0000

David R Oran <oran@cisco.com> writes:
>On Jun 19, 2009, at 12:08 PM, Alan Clark wrote:
>
>>
>> A parallel problem is the control (rather than indication) of volume
>> and noise suppression in VoIP calls.  911 operators find that
>> sometimes they do want noise suppression and sometimes they don't.
>> Noise suppression can be helpful when they are trying to understand a
>> caller in a noisy background environment however it can also suppress
>> background noises that can help to understand the emergency situation
>> (e.g. if they hearing kids laughing in the background the call may be
>> a prank (which does happen quite frequently) but other sounds may
>> indicate how serious a problem is or provide location information).
>>
>I would think the right mechanism for this would be CCM (Codec Control
>messages), not header extensions.

CCM seems more correct; header extensions aren't really designed/meant
for a control backchannel -- CCM is.  

The downside is that CCM requires AVPF, which because of how
capabilities work in SDP is a real pain.  Header extensions are easier
to just send and if the other side doesn't understand them, oh well.
Putting AVPF in a negotiation will 'break' attempts to talk to most SIP
equipment in the field.  (Some simply ignore the profile...)  Cap-neg
may make it possible to negotiate the profile, but again most things
don't support that, and needing it in order to use AVPF/CCM adds a
significant amount of additional complexity (plus I don't know if
cap-neg is near finalization).

So, it's a pain.  CCM is "right", but would require either major
compatibility pain OR would require implementing cap-neg, which is a
major pain.

-- 
Randell Jesup, Worldgate (developers of the Ojo videophone), ex-Amiga OS team
rjesup@wgate.com
"The fetters imposed on liberty at home have ever been forged out of the weapons
provided for defence against real, pretended, or imaginary dangers from abroad."
		- James Madison, 4th US president (1751-1836)

From dwing@cisco.com  Thu Jun 25 16:09:18 2009
Return-Path: <dwing@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 556633A67E2 for <avt@core3.amsl.com>; Thu, 25 Jun 2009 16:09:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.395
X-Spam-Level: 
X-Spam-Status: No, score=-6.395 tagged_above=-999 required=5 tests=[AWL=0.204,  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 0ya2IFxwAcMg for <avt@core3.amsl.com>; Thu, 25 Jun 2009 16:09:17 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id EDB433A6840 for <avt@ietf.org>; Thu, 25 Jun 2009 16:09:16 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,293,1243814400"; d="scan'208";a="205812073"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-1.cisco.com with ESMTP; 25 Jun 2009 23:08:57 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n5PN8vUQ022808;  Thu, 25 Jun 2009 16:08:57 -0700
Received: from dwingwxp01 ([10.32.240.195]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n5PN8vUY002581; Thu, 25 Jun 2009 23:08:57 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'VAN CAENEGEM Tom'" <Tom.Van_Caenegem@alcatel-lucent.be>, "'Bill Ver Steeg \(versteb\)'" <versteb@cisco.com>, "'Zeev Vax'" <zeevvax@microsoft.com>, "'Ali C. Begen \(abegen\)'" <abegen@cisco.com>, "'Roni Even'" <Even.roni@huawei.com>, <avt@ietf.org>
References: <mailman.10085.1245185397.4936.avt@ietf.org><238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com><015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com><238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com><04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com><81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com><3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com><025401c9effa$34040170$9c0c0450$%roni@huawei.com><3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com><04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com><3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com><81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04137224@FRVELSMBS22.ad2.ad.alcatel.com>
Date: Thu, 25 Jun 2009 16:08:56 -0700
Message-ID: <08ef01c9f5e9$ead0b020$e5a36b80@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <238382595265324EA50F6134BB42DCAF04137224@FRVELSMBS22.ad2.ad.alcatel.com>
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDgARoKBSAALhpHsAAaLeGg
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=10455; t=1245971337; x=1246835337; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dwing@cisco.com; z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com> |Subject:=20RE=3A=20[AVT]=20Port=20mappings,=20NAT,=20and=2 0RAMS |Sender:=20; bh=5pxhC+dzix5xhdXCaTrrSfvcZTAIcKxsxjSTRzxy+/I=; b=soOjM2jWCi0Pdi8046i8USvXi4rvcN4JQbEgLo8dbG4UxB24b6YZXIinQB eFx45WNrcgn4UDfgp8VAhcwwS+eNTjIWn1ZEow/ceyKYZ60pQ0IASWFDVzBV jWcwBE/paD;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 25 Jun 2009 23:09:18 -0000

 

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On 
> Behalf Of VAN CAENEGEM Tom
> Sent: Thursday, June 25, 2009 3:35 AM
> To: Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen 
> (abegen); Roni Even; avt@ietf.org
> Subject: Re: [AVT] Port mappings, NAT, and RAMS
> 
> Bill,
> 
> Thanks for presenting so clearly the different options. A few opinions
> here:
> 
> -For option 3 and 4, a STUN server is not involved, so perhaps the
> associated slides should not mention a STUN server there.
> 
> -For option 3, the pub-port message is in fact not needed, 
> not from the
> NAPT point of view, and not from the RS point of view if we consider a
> clause saying that the RR only needs to send a pub-port message to the
> RS (Feedback Target) when it does NOT want to receive the RTP/RTCP
> burst/retransmission packets on the same port as the source port on
> which the RR sent out the RAMS-R or NACK RTCP message (hence 
> no need to
> define "zero" port values). Of course the RR can only do so, if it
> supports RTP/RTCP muxing itself, and if it knows the RS supports
> RTP/RTCP muxing too (as indicated in the declarative sdp 
> received by the
> RR) 
> 
> -Don't we also allow that for option 3, the port P2 actually 
> equals port
> P4? This is a kind of hybrid of session and SSRC multiplexing of the
> primary multicast RTP stream and the 
> retransmission/acceleration session
> :  on the unidirectional RTP layer, the primary MC packets and the
> unicast retransmission packets are clearly session muxed, but the RTCP
> "return" channel for both streams have exactly the same transport
> addresses, but are distinguished by means of a different 
> SSRC.  In that
> case, the NAPT will always work and there is (again) no need for a
> pub-port message. The RTP receiver of course needs to know whether the
> RS supports this port/multiplexing scheme and this could be solved  by
> means of defining a new atribute in SDP, that is then included in the
> declarative SDP. 
> 
> With this, I am not saying that I do not want to define the pub-port
> message because RTP receivers that want to choose themselves 
> which ports
> are used for the acceleration session should rely on the pub-port
> message to signal this to the RS (option 1 and 2) and to 
> circumvent the
> NAPT when using option 4.
> 
> For option 4, the pub-port message is used to make the NAPT 
> binding. And
> each time a RR asks for a retransmission , the RR may have to send a
> pubreport message, because the NAPT bindings have a limited 
> lifetime.

The RR can keep the NAT's binding alive by sending periodic STUN
indications (as described for RTP flows in Section 4.4 of 
draft-ietf-avt-app-rtp-keepalive), or maybe we could define a bogus
RTCP message if a STUN indication to keep the binding alive is
offensive.  draft-ietf-avt-app-rtp-keepalive mentions that RTCP
usually doesn't need keepalive traffic to keep a NAT binding alive
because RTCP is sent periodically.  In the situation with RAMS
RTCP messages, the RTCP requesting re-transmission is not sent 
periodicially.  

> It
> is not clear to me whether for all options you considered, the
> pub-report message is always sent whenever a  NACK is sent?  Or would
> you recommend saying that it must be sent when a RAMS-R is sent
> (obviously), and then during the acceleration/retransmission 
> session it
> is never sent anymore for option 1 and 2 (as the RS keeps state), and
> for option 4 in your slides it is up to the RR to decide when to
> transmit the pub-port, based on its knowledge of NAT binding lifetime?

It is difficult-to-impossible to determine the lifetime of a NAT's 
binding with much confidence.

-d

> In summary, my opinions are the following:
> 
> -the pub-port message is only used by the RR to signal a dedicated set
> of ports to the RS on which it wants to receive the RTP/RTCP burst and
> retransmission packets. This is option 1 and 2. For an acceleration
> (+retransmission) session, the pub-port is sent once in a compound
> together with RAMS-R, and for a retransmission-only session (no
> RAMS/acceleration involved), it is sent in a compound 
> together with the
> 1st issued NACK. For subsequent NACKs, there is no need to send the
> pub-report along.
>  
> -when the declarative SDP indicates that the RS supports RTP/RTCP
> muxing, and the RR does not use the pub-port message, the RR 
> expects the
> retransmission/burts packets on the same port on which it sent out the
> RAMS-R or the NACK RTCP message.
> 
> -when additionally the declarative SDP indicates with a new attribute
> that the RS is prepared to use as source port for the
> burst/retransmission packets the ports used by the RR for the
> burst/retransmission request, the RR expects the RS to use the same
> ports (source and destination) for the retransmission/burts packets as
> used by the receiver in the RAMS-R or the NACK RTCP message (but
> reversed of course). The new SDP attribute could include a range of
> ports out which the RTP receiver needs to select a value that it will
> use as destination port for the RAMS-R or NACK.  
> 
> I would also be in favour that we mandate an RS to support RTP/RTCP
> muxing, such that an RTP receiver can always make a choice 
> which scheme
> to follow.
> 
> I think it would make more sense to describe this whole solution with
> the pub-port message definition and new SDP attribute as well as the
> STUN message exchange in a separate draft as it is also applicable to
> solutions making use of RTCP FB messages for retransmission only (RTCP
> NACK), but with no need for rapid acquisition. 
> 
> Regards,
> Tom 
> 
> -----Original Message-----
> From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com] 
> Sent: woensdag 24 juni 2009 14:37
> To: Zeev Vax; Ali C. Begen (abegen); Roni Even; VAN CAENEGEM Tom;
> avt@ietf.org
> Subject: Port mappings, NAT, and RAMS
> 
>  
> There has been some discussion around the requirement for a 
> NAT section
> in the latest RAMS draft. This note is an attempt to clarify the
> requirement to signal RAMS port mappings. Once we come to a 
> consensus as
> to the desired behavior, we can update the draft.
> 
> This text refers to a ppt document that can be found at
> ftp://ftpeng.cisco.com/abegen/PubPorts.pdf
> 
> When using RAMS to accelerate acquisition of a multicast 
> flow, there are
> two sessions - the primary multicast session and the acceleration
> session. These sessions may have multiple socket contexts, 
> depending on
> the use of RTP/RTP port muxing. However, the primary multicast session
> and the retransmission session are always distinct.
> 
> 1- The primary multicast session - two logical flows defined by the
> Source address, Destination Multicast Address, RTP port (P1) and RTCP
> port(P2). This set of flows is shown in RED in the diagram.
> 2- The retransmission/acceleration session, shown in BLUE in the
> diagram. In the most general non-port-muxed, non-NATed case, 
> this stream
> consists of 2 flows. The first (RTP) flow is defined by the 5-tuple of
> UDP, IP address of the FT, RTP port configured by SDP (P3),  the IP
> address of the client and the RTP port dynamically chosen by RR (c3).
> The second (RTCP) flow is defined by the 5-tuple of UDP, FT 
> address, the
> RTCP port defined by SDP (P4), the IP address of the client 
> and the RTCP
> port dynamically chosen by RR (c4). When RTP/RTCP port muxing is used,
> the retransmission session is collapsed onto a single 5-tuple.
> 
> Note that the feedback target for the primary session is P2 on FT/RS.
> Note that the acceleration burst must flow from FT P3/P4 to C 
> c3/c4. In
> other words, the first desired data flow on the retransmission session
> is "downstream". 
> 
> When we introduce NAT, we need to map c3 to c3' (and in the absence of
> port muxing, also c4 to c4') through the NAT device. This 
> diagram shows
> the use of STUN in YELLOW to setup the port mappings, but 
> other methods
> could be used.
> 
> 
> 
> In summary, the ppt describes 4 options-
> 
> Drawing 1 - No muxing - Stun request, bind for two ports and send
> PubPorts with RAMS-R to signal both, followed by the burst.
> Drawing 2 - Muxing - Stun request, bind for one port and send PubPorts
> with RAMS-R to signal a single port, followed by the burst.
> Drawing 3 - Muxing - No explicit STUN request/bind. Send PubPorts with
> RAMS-R to signal RS to use the src port of the incoming RTCP packet as
> the destination for both RTP and RTCP in the ret session (We 
> do this by
> putting 0's in the pubports messages). Note that this does not work
> through all NAT variants. The RAMS-R/PubPorts message is sent 
> from c4 to
> P2. The burst is sent from P4 to c4', and certain NATs will not pass
> this traffic.
> Drawing 4 - Muxing - No explicite STUN request/bind. Send 
> PubPorts from
> c4 to P4, initializing NAT bindings. Send RAMS-R, followed by 
> the burst.
> This works through all NAT types. There is concern about the 
> decoupling
> of the PubPorts from the RAMS-R, as dropped messages may 
> cause problems.
> 
> Hopefully this note clarifies the need to signal the ports.
> 
> Inputs on ths problem are desired. We need to decide if the 
> PubPorts is
> the right way to go, and if the transaction is RAMS specific or is a
> generic RTP/RTCP message. Once we make that determination, we need to
> lay out the details of the message format. 
> 
> Based on the feedback - we will abandon the idea, keep it in 
> the draft,
> or write a separate draft for it.
> 
> Bill VerSteeg (with extensive input from Ali Begen and Dan Wing)
> 
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Zeev Vax
> Sent: Thursday, June 18, 2009 5:58 PM
> To: Ali C. Begen (abegen); Roni Even; Bill Ver Steeg (versteb);
> VANCAENEGEM Tom; avt@ietf.org
> Subject: Re: [AVT] comments on
> section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> 
> If we assume all entities are one, why would you need to signal the
> retransmission port separately ?
> 
> Zeev
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From Even.roni@huawei.com  Fri Jun 26 01:32:30 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC22F3A6917 for <avt@core3.amsl.com>; Fri, 26 Jun 2009 01:32:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.168
X-Spam-Level: 
X-Spam-Status: No, score=0.168 tagged_above=-999 required=5 tests=[AWL=0.663,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 el0RS5myXdZV for <avt@core3.amsl.com>; Fri, 26 Jun 2009 01:32:29 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 6E1E53A687F for <avt@ietf.org>; Fri, 26 Jun 2009 01:32:29 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLU0005I7OM7F@szxga01-in.huawei.com> for avt@ietf.org; Fri, 26 Jun 2009 16:31:34 +0800 (CST)
Received: from huawei.com ([172.24.1.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLU004KK7OMM8@szxga01-in.huawei.com> for avt@ietf.org; Fri, 26 Jun 2009 16:31:34 +0800 (CST)
Received: from windows8d787f9 (bzq-79-182-68-39.red.bezeqint.net [79.182.68.39]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KLU009JO7O5CZ@szxml01-in.huawei.com>; Fri, 26 Jun 2009 16:31:34 +0800 (CST)
Date: Fri, 26 Jun 2009 11:31:03 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com>
To: "'Bill Ver Steeg (versteb)'" <versteb@cisco.com>, 'Zeev Vax' <zeevvax@microsoft.com>, "'Ali C. Begen (abegen)'" <abegen@cisco.com>, 'VANCAENEGEM Tom' <Tom.Van_Caenegem@alcatel-lucent.be>, avt@ietf.org
Message-id: <018901c9f638$7a286940$6e793bc0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDgARoKBSAAW0fO0A==
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com>
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 26 Jun 2009 08:32:30 -0000

Hi Bill,
I think I was the one who started this discussion but it looks to me like it
is going too far since some of this work are not in the AVT charter.

The RAMS solution is based on SSM and Retransmission and if there is a
problem with NATs in these drafts it should be discussed there. My concern
was different. The AVT solution is using SDP for specifying address
information. In the case of both SSM and retransmission, the server can
provide their address (which they may have obtained by using any method they
chose) in the SDP. This works both for offer/answer and declarative SDP. I
see no reason to address this topic in the RAMS draft

The RAMS draft need to provide other addresses which are the RR RTP and RTCP
receive addresses. In the case of offer answer this is clear by for
declarative SDP the RR does not sent an SDP so cannot provide receive
addresses.


In the case of RFC 4588 the retransmission can be based on session or SSRC
multiplexing and defines how to use SDP to provide the addresses. The
difference is that RFC 4588 do not address a unicast retransmission for a
multicast stream which is the special case described here.  In the current
case the SSRC multiplexing mode of RFC 4588 is not relevant so there MUST be
a way for the RR to provide its receiving addresses to the RS. 

Since this solution do not work in offer/answer but is based on declarative
SDP there need to be other way for the RR to provide the addressed


My view based on the text above about SSM and RFC 4588 is that this is a
special case and not a general case and this is why I suggested to add the
address information to the RAMS-R message.

Roni Even
   

> -----Original Message-----
> From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> Sent: Wednesday, June 24, 2009 3:37 PM
> To: Zeev Vax; Ali C. Begen (abegen); Roni Even; VANCAENEGEM Tom;
> avt@ietf.org
> Subject: Port mappings, NAT, and RAMS
> 
> 
> There has been some discussion around the requirement for a NAT section
> in the latest RAMS draft. This note is an attempt to clarify the
> requirement to signal RAMS port mappings. Once we come to a consensus
> as
> to the desired behavior, we can update the draft.
> 
> This text refers to a ppt document that can be found at
> ftp://ftpeng.cisco.com/abegen/PubPorts.pdf
> 
> When using RAMS to accelerate acquisition of a multicast flow, there
> are
> two sessions - the primary multicast session and the acceleration
> session. These sessions may have multiple socket contexts, depending on
> the use of RTP/RTP port muxing. However, the primary multicast session
> and the retransmission session are always distinct.
> 
> 1- The primary multicast session - two logical flows defined by the
> Source address, Destination Multicast Address, RTP port (P1) and RTCP
> port(P2). This set of flows is shown in RED in the diagram.
> 2- The retransmission/acceleration session, shown in BLUE in the
> diagram. In the most general non-port-muxed, non-NATed case, this
> stream
> consists of 2 flows. The first (RTP) flow is defined by the 5-tuple of
> UDP, IP address of the FT, RTP port configured by SDP (P3),  the IP
> address of the client and the RTP port dynamically chosen by RR (c3).
> The second (RTCP) flow is defined by the 5-tuple of UDP, FT address,
> the
> RTCP port defined by SDP (P4), the IP address of the client and the
> RTCP
> port dynamically chosen by RR (c4). When RTP/RTCP port muxing is used,
> the retransmission session is collapsed onto a single 5-tuple.
> 
> Note that the feedback target for the primary session is P2 on FT/RS.
> Note that the acceleration burst must flow from FT P3/P4 to C c3/c4. In
> other words, the first desired data flow on the retransmission session
> is "downstream".
> 
> When we introduce NAT, we need to map c3 to c3' (and in the absence of
> port muxing, also c4 to c4') through the NAT device. This diagram shows
> the use of STUN in YELLOW to setup the port mappings, but other methods
> could be used.
> 
> 
> 
> In summary, the ppt describes 4 options-
> 
> Drawing 1 - No muxing - Stun request, bind for two ports and send
> PubPorts with RAMS-R to signal both, followed by the burst.
> Drawing 2 - Muxing - Stun request, bind for one port and send PubPorts
> with RAMS-R to signal a single port, followed by the burst.
> Drawing 3 - Muxing - No explicit STUN request/bind. Send PubPorts with
> RAMS-R to signal RS to use the src port of the incoming RTCP packet as
> the destination for both RTP and RTCP in the ret session (We do this by
> putting 0's in the pubports messages). Note that this does not work
> through all NAT variants. The RAMS-R/PubPorts message is sent from c4
> to
> P2. The burst is sent from P4 to c4', and certain NATs will not pass
> this traffic.
> Drawing 4 - Muxing - No explicite STUN request/bind. Send PubPorts from
> c4 to P4, initializing NAT bindings. Send RAMS-R, followed by the
> burst.
> This works through all NAT types. There is concern about the decoupling
> of the PubPorts from the RAMS-R, as dropped messages may cause
> problems.
> 
> Hopefully this note clarifies the need to signal the ports.
> 
> Inputs on ths problem are desired. We need to decide if the PubPorts is
> the right way to go, and if the transaction is RAMS specific or is a
> generic RTP/RTCP message. Once we make that determination, we need to
> lay out the details of the message format.
> 
> Based on the feedback - we will abandon the idea, keep it in the draft,
> or write a separate draft for it.
> 
> Bill VerSteeg (with extensive input from Ali Begen and Dan Wing)
> 
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Zeev Vax
> Sent: Thursday, June 18, 2009 5:58 PM
> To: Ali C. Begen (abegen); Roni Even; Bill Ver Steeg (versteb);
> VANCAENEGEM Tom; avt@ietf.org
> Subject: Re: [AVT] comments on
> section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> 
> If we assume all entities are one, why would you need to signal the
> retransmission port separately ?
> 
> Zeev


From Tom.Van_Caenegem@alcatel-lucent.be  Fri Jun 26 01:54:34 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 3C32D3A67A4 for <avt@core3.amsl.com>; Fri, 26 Jun 2009 01:54:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.963
X-Spam-Level: 
X-Spam-Status: No, score=-5.963 tagged_above=-999 required=5 tests=[AWL=0.286,  BAYES_00=-2.599, HELO_EQ_FR=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 dbkr2EsTQR+l for <avt@core3.amsl.com>; Fri, 26 Jun 2009 01:54:32 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id 2FFE13A6890 for <avt@ietf.org>; Fri, 26 Jun 2009 01:54:04 -0700 (PDT)
Received: from FRVELSBHS05.ad2.ad.alcatel.com (frvelsbhs05.dc-m.alcatel-lucent.com [155.132.6.77]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5Q8qOV2014578;  Fri, 26 Jun 2009 10:52:24 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.51]) by FRVELSBHS05.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 26 Jun 2009 10:52:24 +0200
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: Fri, 26 Jun 2009 10:52:23 +0200
Message-ID: <238382595265324EA50F6134BB42DCAF04137758@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <018901c9f638$7a286940$6e793bc0$%roni@huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Port mappings, NAT, and RAMS
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDgARoKBSAAW0fO0AABD/mg
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <018901c9f638$7a286940$6e793bc0$%roni@huawei.com>
From: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>
To: "Roni Even" <Even.roni@huawei.com>, "Bill Ver Steeg (versteb)" <versteb@cisco.com>, "Zeev Vax" <zeevvax@microsoft.com>, "Ali C. Begen (abegen)" <abegen@cisco.com>, <avt@ietf.org>
X-OriginalArrivalTime: 26 Jun 2009 08:52:24.0504 (UTC) FILETIME=[6CC3BB80:01C9F63B]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 26 Jun 2009 08:54:34 -0000

Hi Roni,

The problem I see here is that this is broader than RAMS: if an RTP
receiver in an SSM session does not make use of RAMS, but wants to
receive retransmissions, then integrating the "pub-port" functionality
in the RAMS-R will not help here. That is why it makes most sense to
define a dedicated RTCP "pub-port" message that can be combined with an
RAMS-R or with a NACK.. Or with any other future RTCP request message
that may be defined and relies on the same ssm with feedback target
architecture..
And I also think that we should consider a "default" case that when an
RTP receiver does not signal its ports, the retransmission server
understands the RTP receiver expects the retransmission/burst on the
port, that was used by the RTP receiver as source port to request the
retransmission and burst. But that should imply that the "pub-port" MUST
always be sent in a single compound together with the NACK and/or the
RAMS-R message (either of these) that triggers the retransmission
session.

Tom
=20

-----Original Message-----
From: Roni Even [mailto:Even.roni@huawei.com]=20
Sent: vrijdag 26 juni 2009 10:31
To: 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C. Begen (abegen)'; VAN
CAENEGEM Tom; avt@ietf.org
Subject: RE: Port mappings, NAT, and RAMS

Hi Bill,
I think I was the one who started this discussion but it looks to me
like it is going too far since some of this work are not in the AVT
charter.

The RAMS solution is based on SSM and Retransmission and if there is a
problem with NATs in these drafts it should be discussed there. My
concern was different. The AVT solution is using SDP for specifying
address information. In the case of both SSM and retransmission, the
server can provide their address (which they may have obtained by using
any method they
chose) in the SDP. This works both for offer/answer and declarative SDP.
I see no reason to address this topic in the RAMS draft

The RAMS draft need to provide other addresses which are the RR RTP and
RTCP receive addresses. In the case of offer answer this is clear by for
declarative SDP the RR does not sent an SDP so cannot provide receive
addresses.


In the case of RFC 4588 the retransmission can be based on session or
SSRC multiplexing and defines how to use SDP to provide the addresses.
The difference is that RFC 4588 do not address a unicast retransmission
for a multicast stream which is the special case described here.  In the
current case the SSRC multiplexing mode of RFC 4588 is not relevant so
there MUST be a way for the RR to provide its receiving addresses to the
RS.=20

Since this solution do not work in offer/answer but is based on
declarative SDP there need to be other way for the RR to provide the
addressed


My view based on the text above about SSM and RFC 4588 is that this is a
special case and not a general case and this is why I suggested to add
the address information to the RAMS-R message.

Roni Even
  =20

> -----Original Message-----
> From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> Sent: Wednesday, June 24, 2009 3:37 PM
> To: Zeev Vax; Ali C. Begen (abegen); Roni Even; VANCAENEGEM Tom;=20
> avt@ietf.org
> Subject: Port mappings, NAT, and RAMS
>=20
>=20
> There has been some discussion around the requirement for a NAT=20
> section in the latest RAMS draft. This note is an attempt to clarify=20
> the requirement to signal RAMS port mappings. Once we come to a=20
> consensus as to the desired behavior, we can update the draft.
>=20
> This text refers to a ppt document that can be found at=20
> ftp://ftpeng.cisco.com/abegen/PubPorts.pdf
>=20
> When using RAMS to accelerate acquisition of a multicast flow, there=20
> are two sessions - the primary multicast session and the acceleration=20
> session. These sessions may have multiple socket contexts, depending=20
> on the use of RTP/RTP port muxing. However, the primary multicast=20
> session and the retransmission session are always distinct.
>=20
> 1- The primary multicast session - two logical flows defined by the=20
> Source address, Destination Multicast Address, RTP port (P1) and RTCP=20
> port(P2). This set of flows is shown in RED in the diagram.
> 2- The retransmission/acceleration session, shown in BLUE in the=20
> diagram. In the most general non-port-muxed, non-NATed case, this=20
> stream consists of 2 flows. The first (RTP) flow is defined by the=20
> 5-tuple of UDP, IP address of the FT, RTP port configured by SDP (P3),

> the IP address of the client and the RTP port dynamically chosen by RR

> (c3).
> The second (RTCP) flow is defined by the 5-tuple of UDP, FT address,=20
> the RTCP port defined by SDP (P4), the IP address of the client and=20
> the RTCP port dynamically chosen by RR (c4). When RTP/RTCP port muxing

> is used, the retransmission session is collapsed onto a single=20
> 5-tuple.
>=20
> Note that the feedback target for the primary session is P2 on FT/RS.
> Note that the acceleration burst must flow from FT P3/P4 to C c3/c4.=20
> In other words, the first desired data flow on the retransmission=20
> session is "downstream".
>=20
> When we introduce NAT, we need to map c3 to c3' (and in the absence of

> port muxing, also c4 to c4') through the NAT device. This diagram=20
> shows the use of STUN in YELLOW to setup the port mappings, but other=20
> methods could be used.
>=20
>=20
>=20
> In summary, the ppt describes 4 options-
>=20
> Drawing 1 - No muxing - Stun request, bind for two ports and send=20
> PubPorts with RAMS-R to signal both, followed by the burst.
> Drawing 2 - Muxing - Stun request, bind for one port and send PubPorts

> with RAMS-R to signal a single port, followed by the burst.
> Drawing 3 - Muxing - No explicit STUN request/bind. Send PubPorts with

> RAMS-R to signal RS to use the src port of the incoming RTCP packet as

> the destination for both RTP and RTCP in the ret session (We do this=20
> by putting 0's in the pubports messages). Note that this does not work

> through all NAT variants. The RAMS-R/PubPorts message is sent from c4=20
> to P2. The burst is sent from P4 to c4', and certain NATs will not=20
> pass this traffic.
> Drawing 4 - Muxing - No explicite STUN request/bind. Send PubPorts=20
> from
> c4 to P4, initializing NAT bindings. Send RAMS-R, followed by the=20
> burst.
> This works through all NAT types. There is concern about the=20
> decoupling of the PubPorts from the RAMS-R, as dropped messages may=20
> cause problems.
>=20
> Hopefully this note clarifies the need to signal the ports.
>=20
> Inputs on ths problem are desired. We need to decide if the PubPorts=20
> is the right way to go, and if the transaction is RAMS specific or is=20
> a generic RTP/RTCP message. Once we make that determination, we need=20
> to lay out the details of the message format.
>=20
> Based on the feedback - we will abandon the idea, keep it in the=20
> draft, or write a separate draft for it.
>=20
> Bill VerSteeg (with extensive input from Ali Begen and Dan Wing)
>=20
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of=20
> Zeev Vax
> Sent: Thursday, June 18, 2009 5:58 PM
> To: Ali C. Begen (abegen); Roni Even; Bill Ver Steeg (versteb);=20
> VANCAENEGEM Tom; avt@ietf.org
> Subject: Re: [AVT] comments on
> section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
> If we assume all entities are one, why would you need to signal the=20
> retransmission port separately ?
>=20
> Zeev


From Tom.Van_Caenegem@alcatel-lucent.be  Fri Jun 26 01:55:34 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 CEA283A6929 for <avt@core3.amsl.com>; Fri, 26 Jun 2009 01:55:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599, HELO_EQ_FR=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 1BAbYocim71l for <avt@core3.amsl.com>; Fri, 26 Jun 2009 01:55:33 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by core3.amsl.com (Postfix) with ESMTP id B24B93A6784 for <avt@ietf.org>; Fri, 26 Jun 2009 01:55:32 -0700 (PDT)
Received: from FRVELSBHS06.ad2.ad.alcatel.com (frvelsbhs06.dc-m.alcatel-lucent.com [155.132.6.78]) by smail3.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5Q8sYlt014196;  Fri, 26 Jun 2009 10:54:45 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.51]) by FRVELSBHS06.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 26 Jun 2009 10:54:34 +0200
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: Fri, 26 Jun 2009 10:54:33 +0200
Message-ID: <238382595265324EA50F6134BB42DCAF04137762@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D54099DFD1A@xmb-sjc-215.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Port mappings, NAT, and RAMS
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDgARoKBSAALhpHsAAKg7ngAAPu9/A=
References: <mailman.10085.1245185397.4936.avt@ietf.org><238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com><015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com><238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com><04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com><81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com><3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com><025401c9effa$34040170$9c0c0450$%roni@huawei.com><3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com><04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04137224@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54099DFD1A@xmb-sjc-215.amer.cisco.com>
From: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>
To: "Ali C. Begen (abegen)" <abegen@cisco.com>, "Bill Ver Steeg (versteb)" <versteb@cisco.com>, "Zeev Vax" <zeevvax@microsoft.com>, "Roni Even" <Even.roni@huawei.com>,  <avt@ietf.org>
X-OriginalArrivalTime: 26 Jun 2009 08:54:34.0622 (UTC) FILETIME=[BA5229E0:01C9F63B]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.83
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 26 Jun 2009 08:55:34 -0000

Ali, see inline=20

-----Original Message-----
From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]=20
Sent: donderdag 25 juni 2009 17:58
To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni Even;
avt@ietf.org
Subject: RE: Port mappings, NAT, and RAMS

Hi Tom,

A few quick comments inline.

> -----Original Message-----
> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> Sent: Thursday, June 25, 2009 3:35 AM
> To: Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen (abegen); Roni=20
> Even; avt@ietf.org
> Subject: RE: Port mappings, NAT, and RAMS
>=20
> Bill,
>=20
> Thanks for presenting so clearly the different options. A few opinions
> here:
>=20
> -For option 3 and 4, a STUN server is not involved, so perhaps the=20
> associated slides should not mention a STUN server there.

Yup. It can be removed.

=20
> -For option 3, the pub-port message is in fact not needed, not from=20
> the NAPT point of view, and not from the RS point of view if we=20
> consider a clause saying that the RR only needs to send a pub-port=20
> message to the RS (Feedback Target) when it does NOT want to receive=20
> the RTP/RTCP burst/retransmission packets on the same port as the=20
> source port on which the RR sent out the RAMS-R or NACK RTCP message=20
> (hence no need to define "zero" port values). Of course the RR can=20
> only do so, if it

The reason why we need pubports is that it indicates "explicitly" the
port the client wants to use to receive the burst is the port it used to
send the RAMS-R/pubports message. I believe we need this explicit
indication, ow, we will be making an implicit assumption. Note that the
rams-r/pubports is in the primary session and burst/ret packets are in
the retransmission session, which is different than the primary.

As far as I can see, not everybody agrees on this point, but we need to
make a decision here before we mandate anything.

TOM: I agree with your last line, but I do not completely agree when you
mention "implicit" assumption, especially for option 3, where RAMS-R (or
NACK) and the Pub-port message are in the same compound message. If we
"define" that if no pub-report message is sent by the RR, the
information towards the Retransmission server is exactly the same as
when an RTP receiver sends an RTCP compound message made up of an RTCP
NACK/RAMS-R together with a pub-port message where the ports are "zero"
-as currently proposed in the RAMS draft now.  I agree that this is not
true for option 4, where pub-port and RAMS-R or NACK are separate
messages, but I do not favour the solution of option 4 for the same
reason you mention in your reply (a new failure mode). So, if option 4
is -for that reason- no longer considered, I do not see a problem with
defining this rule/clause as expressed above. In other words, there is
no need for a pub-report message in this scenario and this results NOT
in an "assumption" what-so-ever.  =20


> supports RTP/RTCP muxing itself, and if it knows the RS supports=20
> RTP/RTCP muxing too (as indicated in the declarative sdp received by=20
> the
> RR)
>=20
> -Don't we also allow that for option 3, the port P2 actually equals=20
> port P4? This is a kind of hybrid of session and SSRC multiplexing of=20
> the primary multicast RTP stream and the retransmission/acceleration=20
> session
> :  on the unidirectional RTP layer, the primary MC packets and the=20
> unicast retransmission packets are clearly session muxed, but the RTCP

> "return" channel for both streams have exactly the same transport=20
> addresses, but are distinguished by means of a different SSRC.  In=20
> that

How? Since SSM and retransmission sessions are session muxed, they have
the same SSRC. When a client is sending a receiver report, how do we
identify which session it belongs to? So, I believe P2 should be
different than P4.

TOM: you are right. But notice this: RFC 4588 mandates that when session
muxing is used for retransmission, than the SSRC should be the same.
However the RFC 4588 does not give arguments why it needs to be like
that. So I ask you: what would or can happen if there is a different
SSRC used?  If there are no convincing arguments why we must stick to
the same SSRC, then, if we have a good use case to depart from that
"rule" -and the use case we are discussing here is IMO indeed a valid
use case- I do not see why we should be limited by such a "rule". The
"valid" use case is here that RAMS and Retransmission for SSM sessions
operates fine through any NAPT and without any dedicated RTCP message.=20



> case, the NAPT will always work and there is (again) no need for a=20
> pub-port message. The RTP receiver of course needs to know whether the

> RS supports this port/multiplexing scheme and this could be solved  by

> means of defining a new atribute in SDP, that is then included in the=20
> declarative SDP.
>=20
> With this, I am not saying that I do not want to define the pub-port=20
> message because RTP receivers that want to choose themselves which=20
> ports are used for the acceleration session should rely on the=20
> pub-port message to signal this to the RS (option 1 and 2) and to=20
> circumvent the NAPT when using option 4.
>=20
> For option 4, the pub-port message is used to make the NAPT binding.=20
> And each time a RR asks for a retransmission , the RR may have to send

> a pubreport message, because the NAPT bindings have a limited=20
> lifetime. It is not clear to me whether for all options you=20
> considered, the pub-report message is always sent whenever a  NACK is=20
> sent?  Or would

This is a very good point. If RS/FT address changes for each SSM
session, then a new pubports is needed to bind the correct address/port
on the NAT. And similar to RAMS-R, NACK would also require a pubports
message whenever a binding is needed for regular retransmission.=20

But, the main problem here is that we are separating the RAMS-R/NACK
from the pubports message. Now, assume that we sent RAMS-R and pubports
for session 1, and suppose pubports message made it but RAMS-R was lost.
Then, we switched to session 2, sent a new RAMS-R and pubports. Then, we
switched back to session 1, sending a new RAMS-R and pubports. Now, RS
may get confused since it may not accurately match the outstanding
RAMS-R and pubports messages. In the RAMS-R message, the parameters may
have changed (such as burst bitrate). In the pubports, port mappings may
have changed. As a result, RS may send the burst to the wrong port
and/or the burst may be at a lower or higher bitrate than RR wants to
have.

In other words, we are introducing new failure modes and this is a big
concern for option 4, IMO.


> you recommend saying that it must be sent when a RAMS-R is sent=20
> (obviously), and then during the acceleration/retransmission session=20
> it is never sent anymore for option 1 and 2 (as the RS keeps state),=20
> and for option 4 in your slides it is up to the RR to decide when to=20
> transmit the pub-port, based on its knowledge of NAT binding lifetime?

As long as the binding does not expire (meaning there is some
transmission on that path), we should be fine. And I believe there are
certain guidelines listed in the STUN spec.

TOM: I agree.

-acbegen
=20
>=20
> In summary, my opinions are the following:
>=20
> -the pub-port message is only used by the RR to signal a dedicated set

> of ports to the RS on which it wants to receive the RTP/RTCP burst and

> retransmission packets. This is option 1 and 2. For an acceleration
> (+retransmission) session, the pub-port is sent once in a compound=20
> together with RAMS-R, and for a retransmission-only session (no=20
> RAMS/acceleration involved), it is sent in a compound together with=20
> the 1st issued NACK. For subsequent NACKs, there is no need to send=20
> the pub-report along.
>=20
> -when the declarative SDP indicates that the RS supports RTP/RTCP=20
> muxing, and the RR does not use the pub-port message, the RR expects=20
> the retransmission/burts packets on the same port on which it sent out

> the RAMS-R or the NACK RTCP message.
>=20
> -when additionally the declarative SDP indicates with a new attribute=20
> that the RS is prepared to use as source port for the=20
> burst/retransmission packets the ports used by the RR for the=20
> burst/retransmission request, the RR expects the RS to use the same=20
> ports (source and destination) for the retransmission/burts packets as

> used by the receiver in the RAMS-R or the NACK RTCP message (but=20
> reversed of course). The new SDP attribute could include a range of=20
> ports out which the RTP receiver needs to select a value that it will=20
> use as destination port for the RAMS-R or NACK.
>=20
> I would also be in favour that we mandate an RS to support RTP/RTCP=20
> muxing, such that an RTP receiver can always make a choice which=20
> scheme to follow.
>=20
> I think it would make more sense to describe this whole solution with=20
> the pub-port message definition and new SDP attribute as well as the=20
> STUN message exchange in a separate draft as it is also applicable to=20
> solutions making use of RTCP FB messages for retransmission only (RTCP

> NACK), but with no need for rapid acquisition.
>=20
> Regards,
> Tom
>=20
> -----Original Message-----
> From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> Sent: woensdag 24 juni 2009 14:37
> To: Zeev Vax; Ali C. Begen (abegen); Roni Even; VAN CAENEGEM Tom;=20
> avt@ietf.org
> Subject: Port mappings, NAT, and RAMS
>=20
>=20
> There has been some discussion around the requirement for a NAT=20
> section in the latest RAMS draft. This note is an attempt to clarify=20
> the requirement to signal RAMS port mappings. Once we come to a=20
> consensus as to the desired behavior, we can update the draft.
>=20
> This text refers to a ppt document that can be found at=20
> ftp://ftpeng.cisco.com/abegen/PubPorts.pdf
>=20
> When using RAMS to accelerate acquisition of a multicast flow, there=20
> are two sessions - the primary multicast session and the acceleration=20
> session. These sessions may have multiple socket contexts, depending=20
> on the use of RTP/RTP port muxing. However, the primary multicast=20
> session and the retransmission session are always distinct.
>=20
> 1- The primary multicast session - two logical flows defined by the=20
> Source address, Destination Multicast Address, RTP port (P1) and RTCP=20
> port(P2). This set of flows is shown in RED in the diagram.
> 2- The retransmission/acceleration session, shown in BLUE in the=20
> diagram. In the most general non-port-muxed, non-NATed case, this=20
> stream consists of 2 flows. The first (RTP) flow is defined by the=20
> 5-tuple of UDP, IP address of the FT, RTP port configured by SDP (P3),

> the IP address of the client and the RTP port dynamically chosen by RR
(c3).
> The second (RTCP) flow is defined by the 5-tuple of UDP, FT address,=20
> the RTCP port defined by SDP (P4), the IP address of the client and=20
> the RTCP port dynamically chosen by RR (c4). When RTP/RTCP port muxing

> is used, the retransmission session is collapsed onto a single
5-tuple.
>=20
> Note that the feedback target for the primary session is P2 on FT/RS.
> Note that the acceleration burst must flow from FT P3/P4 to C c3/c4.=20
> In other words, the first desired data flow on the retransmission=20
> session is "downstream".
>=20
> When we introduce NAT, we need to map c3 to c3' (and in the absence of

> port muxing, also c4 to c4') through the NAT device. This diagram=20
> shows the use of STUN in YELLOW to setup the port mappings, but other=20
> methods could be used.
>=20
>=20
>=20
> In summary, the ppt describes 4 options-
>=20
> Drawing 1 - No muxing - Stun request, bind for two ports and send=20
> PubPorts with RAMS-R to signal both, followed by the burst.
> Drawing 2 - Muxing - Stun request, bind for one port and send PubPorts

> with RAMS-R to signal a single port, followed by the burst.
> Drawing 3 - Muxing - No explicit STUN request/bind. Send PubPorts with

> RAMS-R to signal RS to use the src port of the incoming RTCP packet as

> the destination for both RTP and RTCP in the ret session (We do this=20
> by putting 0's in the pubports messages). Note that this does not work

> through all NAT variants. The RAMS-R/PubPorts message is sent from c4=20
> to P2. The burst is sent from P4 to c4', and certain NATs will not=20
> pass this traffic.
> Drawing 4 - Muxing - No explicite STUN request/bind. Send PubPorts=20
> from
> c4 to P4, initializing NAT bindings. Send RAMS-R, followed by the
burst.
> This works through all NAT types. There is concern about the=20
> decoupling of the PubPorts from the RAMS-R, as dropped messages may
cause problems.
>=20
> Hopefully this note clarifies the need to signal the ports.
>=20
> Inputs on ths problem are desired. We need to decide if the PubPorts=20
> is the right way to go, and if the transaction is RAMS specific or is=20
> a generic RTP/RTCP message. Once we make that determination, we need=20
> to lay out the details of the message format.
>=20
> Based on the feedback - we will abandon the idea, keep it in the=20
> draft, or write a separate draft for it.
>=20
> Bill VerSteeg (with extensive input from Ali Begen and Dan Wing)
>=20
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of=20
> Zeev Vax
> Sent: Thursday, June 18, 2009 5:58 PM
> To: Ali C. Begen (abegen); Roni Even; Bill Ver Steeg (versteb);=20
> VANCAENEGEM Tom; avt@ietf.org
> Subject: Re: [AVT] comments on
> section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
>=20
> If we assume all entities are one, why would you need to signal the=20
> retransmission port separately ?
>=20
> Zeev

From Even.roni@huawei.com  Fri Jun 26 02:47:47 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 746C03A6816 for <avt@core3.amsl.com>; Fri, 26 Jun 2009 02:47:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.053
X-Spam-Level: 
X-Spam-Status: No, score=-0.053 tagged_above=-999 required=5 tests=[AWL=0.442,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 FaYJg2DuylGs for <avt@core3.amsl.com>; Fri, 26 Jun 2009 02:47:46 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id B71C93A6784 for <avt@ietf.org>; Fri, 26 Jun 2009 02:47:45 -0700 (PDT)
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 <0KLU00DS5AMVPG@szxga04-in.huawei.com> for avt@ietf.org; Fri, 26 Jun 2009 17:35:19 +0800 (CST)
Received: from huawei.com ([172.24.1.6]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLU00EU1AMVS6@szxga04-in.huawei.com> for avt@ietf.org; Fri, 26 Jun 2009 17:35:19 +0800 (CST)
Received: from windows8d787f9 (bzq-79-182-68-39.red.bezeqint.net [79.182.68.39]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KLU00FDQAL5G8@szxml02-in.huawei.com>; Fri, 26 Jun 2009 17:35:19 +0800 (CST)
Date: Fri, 26 Jun 2009 12:34:02 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <238382595265324EA50F6134BB42DCAF04137758@FRVELSMBS22.ad2.ad.alcatel.com>
To: 'VAN CAENEGEM Tom' <Tom.Van_Caenegem@alcatel-lucent.be>, "'Bill Ver Steeg (versteb)'" <versteb@cisco.com>, 'Zeev Vax' <zeevvax@microsoft.com>, "'Ali C. Begen (abegen)'" <abegen@cisco.com>, avt@ietf.org
Message-id: <018a01c9f641$4a4bd280$dee37780$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDgARoKBSAAW0fO0AABD/mgAAGLzyA=
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <018901c9f638$7a286940$6e793bc0$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF04137758@FRVELSMBS22.ad2.ad.alcatel.com>
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 26 Jun 2009 09:47:47 -0000

Tom,
What bothering me is that I do not want to make RTCP as a general mechanism
to provide addressing information. 

I still do not see this a a general problem. The case you described (SSM
with retransmission), except for the RAMS case there is no other application
that requires that, it requires co-location of the FT and retransmission
source, you send the retransmission request to the feedback target and not
to the retransmission server. 


If this was a general problem it should be addressed in the context of
retransmission or SSM.

Roni



 

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> VAN CAENEGEM Tom
> Sent: Friday, June 26, 2009 11:52 AM
> To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen
> (abegen); avt@ietf.org
> Subject: Re: [AVT] Port mappings, NAT, and RAMS
> 
> Hi Roni,
> 
> The problem I see here is that this is broader than RAMS: if an RTP
> receiver in an SSM session does not make use of RAMS, but wants to
> receive retransmissions, then integrating the "pub-port" functionality
> in the RAMS-R will not help here. That is why it makes most sense to
> define a dedicated RTCP "pub-port" message that can be combined with an
> RAMS-R or with a NACK.. Or with any other future RTCP request message
> that may be defined and relies on the same ssm with feedback target
> architecture..
> And I also think that we should consider a "default" case that when an
> RTP receiver does not signal its ports, the retransmission server
> understands the RTP receiver expects the retransmission/burst on the
> port, that was used by the RTP receiver as source port to request the
> retransmission and burst. But that should imply that the "pub-port"
> MUST
> always be sent in a single compound together with the NACK and/or the
> RAMS-R message (either of these) that triggers the retransmission
> session.
> 
> Tom
> 
> 
> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: vrijdag 26 juni 2009 10:31
> To: 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C. Begen (abegen)';
> VAN
> CAENEGEM Tom; avt@ietf.org
> Subject: RE: Port mappings, NAT, and RAMS
> 
> Hi Bill,
> I think I was the one who started this discussion but it looks to me
> like it is going too far since some of this work are not in the AVT
> charter.
> 
> The RAMS solution is based on SSM and Retransmission and if there is a
> problem with NATs in these drafts it should be discussed there. My
> concern was different. The AVT solution is using SDP for specifying
> address information. In the case of both SSM and retransmission, the
> server can provide their address (which they may have obtained by using
> any method they
> chose) in the SDP. This works both for offer/answer and declarative
> SDP.
> I see no reason to address this topic in the RAMS draft
> 
> The RAMS draft need to provide other addresses which are the RR RTP and
> RTCP receive addresses. In the case of offer answer this is clear by
> for
> declarative SDP the RR does not sent an SDP so cannot provide receive
> addresses.
> 
> 
> In the case of RFC 4588 the retransmission can be based on session or
> SSRC multiplexing and defines how to use SDP to provide the addresses.
> The difference is that RFC 4588 do not address a unicast retransmission
> for a multicast stream which is the special case described here.  In
> the
> current case the SSRC multiplexing mode of RFC 4588 is not relevant so
> there MUST be a way for the RR to provide its receiving addresses to
> the
> RS.
> 
> Since this solution do not work in offer/answer but is based on
> declarative SDP there need to be other way for the RR to provide the
> addressed
> 
> 
> My view based on the text above about SSM and RFC 4588 is that this is
> a
> special case and not a general case and this is why I suggested to add
> the address information to the RAMS-R message.
> 
> Roni Even
> 
> 
> > -----Original Message-----
> > From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> > Sent: Wednesday, June 24, 2009 3:37 PM
> > To: Zeev Vax; Ali C. Begen (abegen); Roni Even; VANCAENEGEM Tom;
> > avt@ietf.org
> > Subject: Port mappings, NAT, and RAMS
> >
> >
> > There has been some discussion around the requirement for a NAT
> > section in the latest RAMS draft. This note is an attempt to clarify
> > the requirement to signal RAMS port mappings. Once we come to a
> > consensus as to the desired behavior, we can update the draft.
> >
> > This text refers to a ppt document that can be found at
> > ftp://ftpeng.cisco.com/abegen/PubPorts.pdf
> >
> > When using RAMS to accelerate acquisition of a multicast flow, there
> > are two sessions - the primary multicast session and the acceleration
> > session. These sessions may have multiple socket contexts, depending
> > on the use of RTP/RTP port muxing. However, the primary multicast
> > session and the retransmission session are always distinct.
> >
> > 1- The primary multicast session - two logical flows defined by the
> > Source address, Destination Multicast Address, RTP port (P1) and RTCP
> > port(P2). This set of flows is shown in RED in the diagram.
> > 2- The retransmission/acceleration session, shown in BLUE in the
> > diagram. In the most general non-port-muxed, non-NATed case, this
> > stream consists of 2 flows. The first (RTP) flow is defined by the
> > 5-tuple of UDP, IP address of the FT, RTP port configured by SDP
> (P3),
> 
> > the IP address of the client and the RTP port dynamically chosen by
> RR
> 
> > (c3).
> > The second (RTCP) flow is defined by the 5-tuple of UDP, FT address,
> > the RTCP port defined by SDP (P4), the IP address of the client and
> > the RTCP port dynamically chosen by RR (c4). When RTP/RTCP port
> muxing
> 
> > is used, the retransmission session is collapsed onto a single
> > 5-tuple.
> >
> > Note that the feedback target for the primary session is P2 on FT/RS.
> > Note that the acceleration burst must flow from FT P3/P4 to C c3/c4.
> > In other words, the first desired data flow on the retransmission
> > session is "downstream".
> >
> > When we introduce NAT, we need to map c3 to c3' (and in the absence
> of
> 
> > port muxing, also c4 to c4') through the NAT device. This diagram
> > shows the use of STUN in YELLOW to setup the port mappings, but other
> > methods could be used.
> >
> >
> >
> > In summary, the ppt describes 4 options-
> >
> > Drawing 1 - No muxing - Stun request, bind for two ports and send
> > PubPorts with RAMS-R to signal both, followed by the burst.
> > Drawing 2 - Muxing - Stun request, bind for one port and send
> PubPorts
> 
> > with RAMS-R to signal a single port, followed by the burst.
> > Drawing 3 - Muxing - No explicit STUN request/bind. Send PubPorts
> with
> 
> > RAMS-R to signal RS to use the src port of the incoming RTCP packet
> as
> 
> > the destination for both RTP and RTCP in the ret session (We do this
> > by putting 0's in the pubports messages). Note that this does not
> work
> 
> > through all NAT variants. The RAMS-R/PubPorts message is sent from c4
> > to P2. The burst is sent from P4 to c4', and certain NATs will not
> > pass this traffic.
> > Drawing 4 - Muxing - No explicite STUN request/bind. Send PubPorts
> > from
> > c4 to P4, initializing NAT bindings. Send RAMS-R, followed by the
> > burst.
> > This works through all NAT types. There is concern about the
> > decoupling of the PubPorts from the RAMS-R, as dropped messages may
> > cause problems.
> >
> > Hopefully this note clarifies the need to signal the ports.
> >
> > Inputs on ths problem are desired. We need to decide if the PubPorts
> > is the right way to go, and if the transaction is RAMS specific or is
> > a generic RTP/RTCP message. Once we make that determination, we need
> > to lay out the details of the message format.
> >
> > Based on the feedback - we will abandon the idea, keep it in the
> > draft, or write a separate draft for it.
> >
> > Bill VerSteeg (with extensive input from Ali Begen and Dan Wing)
> >
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> > Zeev Vax
> > Sent: Thursday, June 18, 2009 5:58 PM
> > To: Ali C. Begen (abegen); Roni Even; Bill Ver Steeg (versteb);
> > VANCAENEGEM Tom; avt@ietf.org
> > Subject: Re: [AVT] comments on
> > section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > If we assume all entities are one, why would you need to signal the
> > retransmission port separately ?
> >
> > Zeev
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From Tom.Van_Caenegem@alcatel-lucent.be  Fri Jun 26 03:11:34 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 5E1E63A68A5 for <avt@core3.amsl.com>; Fri, 26 Jun 2009 03:11:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.027
X-Spam-Level: 
X-Spam-Status: No, score=-6.027 tagged_above=-999 required=5 tests=[AWL=0.222,  BAYES_00=-2.599, HELO_EQ_FR=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 e6HdfmSPegk8 for <avt@core3.amsl.com>; Fri, 26 Jun 2009 03:11:33 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by core3.amsl.com (Postfix) with ESMTP id 910903A6855 for <avt@ietf.org>; Fri, 26 Jun 2009 03:11:32 -0700 (PDT)
Received: from FRVELSBHS02.ad2.ad.alcatel.com (frvelsbhs02.dc-m.alcatel-lucent.com [155.132.6.74]) by smail3.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5QAA6mP007413;  Fri, 26 Jun 2009 12:10:06 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.51]) by FRVELSBHS02.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 26 Jun 2009 12:10:06 +0200
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: Fri, 26 Jun 2009 12:10:05 +0200
Message-ID: <238382595265324EA50F6134BB42DCAF04137859@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <018a01c9f641$4a4bd280$dee37780$%roni@huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Port mappings, NAT, and RAMS
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDgARoKBSAAW0fO0AABD/mgAAGLzyAAALbj8A==
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <018901c9f638$7a286940$6e793bc0$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF04137758@FRVELSMBS22.ad2.ad.alcatel.com> <018a01c9f641$4a4bd280$de! e37780$%r oni@huawei.com>
From: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>
To: "Roni Even" <Even.roni@huawei.com>, "Bill Ver Steeg (versteb)" <versteb@cisco.com>, "Zeev Vax" <zeevvax@microsoft.com>, "Ali C. Begen (abegen)" <abegen@cisco.com>, <avt@ietf.org>
X-OriginalArrivalTime: 26 Jun 2009 10:10:06.0727 (UTC) FILETIME=[47AA8170:01C9F646]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.83
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 26 Jun 2009 10:11:34 -0000

Roni,

See inline=20

-----Original Message-----
From: Roni Even [mailto:Even.roni@huawei.com]=20
Sent: vrijdag 26 juni 2009 11:34
To: VAN CAENEGEM Tom; 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C.
Begen (abegen)'; avt@ietf.org
Subject: RE: [AVT] Port mappings, NAT, and RAMS

Tom,
What bothering me is that I do not want to make RTCP as a general
mechanism to provide addressing information.=20

TOM: I understand

I still do not see this a a general problem. The case you described (SSM
with retransmission), except for the RAMS case there is no other
application that requires that, it requires co-location of the FT and
retransmission source, you send the retransmission request to the
feedback target and not to the retransmission server.=20

TOM: not sure I understand your exact point here. Do you agree that we
need a similar solution for SSM with retransmission (-only)  AND SSM
with RAMS (+ retransmission)?  In that case, it does not make sense to
specify ONLY a RAMS-R with the port information, you also need to do
that then for a NACK message. NACK is already defined, so that is why I
think that specifying a separate RTCP message is the way out here. But
because this is related to ssm and retransmission, it cannot be done in
this RAMS draft only. I do agree that such message can only be used in
the context of ssm with unicast feedback.


If this was a general problem it should be addressed in the context of
retransmission or SSM.

Roni



=20

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of=20
> VAN CAENEGEM Tom
> Sent: Friday, June 26, 2009 11:52 AM
> To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen=20
> (abegen); avt@ietf.org
> Subject: Re: [AVT] Port mappings, NAT, and RAMS
>=20
> Hi Roni,
>=20
> The problem I see here is that this is broader than RAMS: if an RTP=20
> receiver in an SSM session does not make use of RAMS, but wants to=20
> receive retransmissions, then integrating the "pub-port" functionality

> in the RAMS-R will not help here. That is why it makes most sense to=20
> define a dedicated RTCP "pub-port" message that can be combined with=20
> an RAMS-R or with a NACK.. Or with any other future RTCP request=20
> message that may be defined and relies on the same ssm with feedback=20
> target architecture..
> And I also think that we should consider a "default" case that when an

> RTP receiver does not signal its ports, the retransmission server=20
> understands the RTP receiver expects the retransmission/burst on the=20
> port, that was used by the RTP receiver as source port to request the=20
> retransmission and burst. But that should imply that the "pub-port"
> MUST
> always be sent in a single compound together with the NACK and/or the=20
> RAMS-R message (either of these) that triggers the retransmission=20
> session.
>=20
> Tom
>=20
>=20
> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: vrijdag 26 juni 2009 10:31
> To: 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C. Begen (abegen)';=20
> VAN CAENEGEM Tom; avt@ietf.org
> Subject: RE: Port mappings, NAT, and RAMS
>=20
> Hi Bill,
> I think I was the one who started this discussion but it looks to me=20
> like it is going too far since some of this work are not in the AVT=20
> charter.
>=20
> The RAMS solution is based on SSM and Retransmission and if there is a

> problem with NATs in these drafts it should be discussed there. My=20
> concern was different. The AVT solution is using SDP for specifying=20
> address information. In the case of both SSM and retransmission, the=20
> server can provide their address (which they may have obtained by=20
> using any method they
> chose) in the SDP. This works both for offer/answer and declarative=20
> SDP.
> I see no reason to address this topic in the RAMS draft
>=20
> The RAMS draft need to provide other addresses which are the RR RTP=20
> and RTCP receive addresses. In the case of offer answer this is clear=20
> by for declarative SDP the RR does not sent an SDP so cannot provide=20
> receive addresses.
>=20
>=20
> In the case of RFC 4588 the retransmission can be based on session or=20
> SSRC multiplexing and defines how to use SDP to provide the addresses.
> The difference is that RFC 4588 do not address a unicast=20
> retransmission for a multicast stream which is the special case=20
> described here.  In the current case the SSRC multiplexing mode of RFC

> 4588 is not relevant so there MUST be a way for the RR to provide its=20
> receiving addresses to the RS.
>=20
> Since this solution do not work in offer/answer but is based on=20
> declarative SDP there need to be other way for the RR to provide the=20
> addressed
>=20
>=20
> My view based on the text above about SSM and RFC 4588 is that this is

> a special case and not a general case and this is why I suggested to=20
> add the address information to the RAMS-R message.
>=20
> Roni Even
>=20
>=20
> > -----Original Message-----
> > From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> > Sent: Wednesday, June 24, 2009 3:37 PM
> > To: Zeev Vax; Ali C. Begen (abegen); Roni Even; VANCAENEGEM Tom;=20
> > avt@ietf.org
> > Subject: Port mappings, NAT, and RAMS
> >
> >
> > There has been some discussion around the requirement for a NAT=20
> > section in the latest RAMS draft. This note is an attempt to clarify

> > the requirement to signal RAMS port mappings. Once we come to a=20
> > consensus as to the desired behavior, we can update the draft.
> >
> > This text refers to a ppt document that can be found at=20
> > ftp://ftpeng.cisco.com/abegen/PubPorts.pdf
> >
> > When using RAMS to accelerate acquisition of a multicast flow, there

> > are two sessions - the primary multicast session and the=20
> > acceleration session. These sessions may have multiple socket=20
> > contexts, depending on the use of RTP/RTP port muxing. However, the=20
> > primary multicast session and the retransmission session are always
distinct.
> >
> > 1- The primary multicast session - two logical flows defined by the=20
> > Source address, Destination Multicast Address, RTP port (P1) and=20
> > RTCP port(P2). This set of flows is shown in RED in the diagram.
> > 2- The retransmission/acceleration session, shown in BLUE in the=20
> > diagram. In the most general non-port-muxed, non-NATed case, this=20
> > stream consists of 2 flows. The first (RTP) flow is defined by the=20
> > 5-tuple of UDP, IP address of the FT, RTP port configured by SDP
> (P3),
>=20
> > the IP address of the client and the RTP port dynamically chosen by
> RR
>=20
> > (c3).
> > The second (RTCP) flow is defined by the 5-tuple of UDP, FT address,

> > the RTCP port defined by SDP (P4), the IP address of the client and=20
> > the RTCP port dynamically chosen by RR (c4). When RTP/RTCP port
> muxing
>=20
> > is used, the retransmission session is collapsed onto a single=20
> > 5-tuple.
> >
> > Note that the feedback target for the primary session is P2 on
FT/RS.
> > Note that the acceleration burst must flow from FT P3/P4 to C c3/c4.
> > In other words, the first desired data flow on the retransmission=20
> > session is "downstream".
> >
> > When we introduce NAT, we need to map c3 to c3' (and in the absence
> of
>=20
> > port muxing, also c4 to c4') through the NAT device. This diagram=20
> > shows the use of STUN in YELLOW to setup the port mappings, but=20
> > other methods could be used.
> >
> >
> >
> > In summary, the ppt describes 4 options-
> >
> > Drawing 1 - No muxing - Stun request, bind for two ports and send=20
> > PubPorts with RAMS-R to signal both, followed by the burst.
> > Drawing 2 - Muxing - Stun request, bind for one port and send
> PubPorts
>=20
> > with RAMS-R to signal a single port, followed by the burst.
> > Drawing 3 - Muxing - No explicit STUN request/bind. Send PubPorts
> with
>=20
> > RAMS-R to signal RS to use the src port of the incoming RTCP packet
> as
>=20
> > the destination for both RTP and RTCP in the ret session (We do this

> > by putting 0's in the pubports messages). Note that this does not
> work
>=20
> > through all NAT variants. The RAMS-R/PubPorts message is sent from=20
> > c4 to P2. The burst is sent from P4 to c4', and certain NATs will=20
> > not pass this traffic.
> > Drawing 4 - Muxing - No explicite STUN request/bind. Send PubPorts=20
> > from
> > c4 to P4, initializing NAT bindings. Send RAMS-R, followed by the=20
> > burst.
> > This works through all NAT types. There is concern about the=20
> > decoupling of the PubPorts from the RAMS-R, as dropped messages may=20
> > cause problems.
> >
> > Hopefully this note clarifies the need to signal the ports.
> >
> > Inputs on ths problem are desired. We need to decide if the PubPorts

> > is the right way to go, and if the transaction is RAMS specific or=20
> > is a generic RTP/RTCP message. Once we make that determination, we=20
> > need to lay out the details of the message format.
> >
> > Based on the feedback - we will abandon the idea, keep it in the=20
> > draft, or write a separate draft for it.
> >
> > Bill VerSteeg (with extensive input from Ali Begen and Dan Wing)
> >
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf=20
> > Of Zeev Vax
> > Sent: Thursday, June 18, 2009 5:58 PM
> > To: Ali C. Begen (abegen); Roni Even; Bill Ver Steeg (versteb);=20
> > VANCAENEGEM Tom; avt@ietf.org
> > Subject: Re: [AVT] comments on
> > section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > If we assume all entities are one, why would you need to signal the=20
> > retransmission port separately ?
> >
> > Zeev
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From versteb@cisco.com  Fri Jun 26 07:34:49 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 1E60F28C0EF for <avt@core3.amsl.com>; Fri, 26 Jun 2009 07:34:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.657
X-Spam-Level: 
X-Spam-Status: No, score=-6.657 tagged_above=-999 required=5 tests=[AWL=-0.058, 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 PnNoC4KZXEFY for <avt@core3.amsl.com>; Fri, 26 Jun 2009 07:34:47 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id D1A5828C0DF for <avt@ietf.org>; Fri, 26 Jun 2009 07:34:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,297,1243814400"; d="scan'208";a="180733184"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-2.cisco.com with ESMTP; 26 Jun 2009 14:35:05 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n5QEZ59t017160;  Fri, 26 Jun 2009 07:35:05 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n5QEZ5jp011933; Fri, 26 Jun 2009 14:35:05 GMT
Received: from xmb-rtp-21d.amer.cisco.com ([64.102.31.116]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 26 Jun 2009 10:35:04 -0400
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: Fri, 26 Jun 2009 10:35:03 -0400
Message-ID: <81B9B88E2F9D574AA5328A85547CDE910184CD5B@xmb-rtp-21d.amer.cisco.com>
In-Reply-To: <238382595265324EA50F6134BB42DCAF04137859@FRVELSMBS22.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Port mappings, NAT, and RAMS (or is it  Port mappings, NAT and RTCP?)
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDgARoKBSAAW0fO0AABD/mgAAGLzyAAALbj8AAJsJKw
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <018901c9f638$7a286940$6e793bc0$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF04137758@FRVELSMBS22.ad2.ad.alcatel.com> <018a01c9f641$4a4bd280$de! e37780$ %roni@huawei .com> <238382595265324EA50F6134BB42DCAF04137859@FRVELSMBS22.ad2.ad.alcatel.com>
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>, "Roni Even" <Even.roni@huawei.com>, "Zeev Vax" <zeevvax@microsoft.com>,  "Ali C. Begen (abegen)" <abegen@cisco.com>, <avt@ietf.org>
X-OriginalArrivalTime: 26 Jun 2009 14:35:04.0677 (UTC) FILETIME=[4B952950:01C9F66B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=11480; t=1246026905; x=1246890905; c=relaxed/simple; s=sjdkim1004; 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=20[AVT]=20Port=20mappings,=20NAT,=20and=2 0RAMS=20(or=20is=20it=20=20Port=20mappings,=20NAT=20and=20RT CP?) |Sender:=20; bh=eMOwofbbmKcC6Amda0xLvDt8odLywhLNuRUm1+oy+ew=; b=P5xiN7SoHX7UTVDXBoPx3RXPu0G9wfXSdnCjuC7w0sjQ/tXy9WjFdFa5wM lkXdTJXIx1ufKj1NLyRInBpxVJ+xFbUttWgqONGI9Nd9tdUrnARn9tW4C7hh ZYHuvbGUCAgmIEQW9uD3/p556hTBt9wQXU6JxQUZRI1NpsD4DgQ0g=;
Authentication-Results: sj-dkim-1; header.From=versteb@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Subject: Re: [AVT] Port mappings, NAT, and RAMS (or is it  Port mappings, NAT and RTCP?)
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, 26 Jun 2009 14:34:49 -0000

Tom is on the right track here.

Let's try separate the technical issue from the logistical issues.

First - the technical issue- RAMS can be considered a special case of
RTCP/RTP repair. The existing RTCP NACK messages do not "self prime" a
NAT. If we can design a mechanism to make RTCP NACK self-configure a NAT
binding, we should be able to use it for RAMS-R. If we do not have a
mechanism for the baseline RTP repair method to make it NAT friendly, we
need to do something RAMS specific.
=20
Second - the logistics issue - As Roni correctly points out, we do not
have a charter to address this in the more general case. The group needs
to decide if this is an RTP issue or a RAMS issue. Until we have
agreement on how to proceed, we should move this issue to a separate
(non-normative) document and remove it from the RAMS draft.

I (personally, not as a RAMS author) would like to see NAT addressed for
the baseline RTP/RTCP repair case. I feel that there is a need "in the
wild" for standard RTP/RTCP repair through NATs. We are getting ahead of
ourselves from a document structuring standpoint, though.=20

Bill VerSteeg

-----Original Message-----
From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]=20
Sent: Friday, June 26, 2009 6:10 AM
To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen
(abegen); avt@ietf.org
Subject: RE: [AVT] Port mappings, NAT, and RAMS

Roni,

See inline=20

-----Original Message-----
From: Roni Even [mailto:Even.roni@huawei.com]
Sent: vrijdag 26 juni 2009 11:34
To: VAN CAENEGEM Tom; 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C.
Begen (abegen)'; avt@ietf.org
Subject: RE: [AVT] Port mappings, NAT, and RAMS

Tom,
What bothering me is that I do not want to make RTCP as a general
mechanism to provide addressing information.=20

TOM: I understand

I still do not see this a a general problem. The case you described (SSM
with retransmission), except for the RAMS case there is no other
application that requires that, it requires co-location of the FT and
retransmission source, you send the retransmission request to the
feedback target and not to the retransmission server.=20

TOM: not sure I understand your exact point here. Do you agree that we
need a similar solution for SSM with retransmission (-only)  AND SSM
with RAMS (+ retransmission)?  In that case, it does not make sense to
specify ONLY a RAMS-R with the port information, you also need to do
that then for a NACK message. NACK is already defined, so that is why I
think that specifying a separate RTCP message is the way out here. But
because this is related to ssm and retransmission, it cannot be done in
this RAMS draft only. I do agree that such message can only be used in
the context of ssm with unicast feedback.


If this was a general problem it should be addressed in the context of
retransmission or SSM.

Roni



=20

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of=20
> VAN CAENEGEM Tom
> Sent: Friday, June 26, 2009 11:52 AM
> To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen=20
> (abegen); avt@ietf.org
> Subject: Re: [AVT] Port mappings, NAT, and RAMS
>=20
> Hi Roni,
>=20
> The problem I see here is that this is broader than RAMS: if an RTP=20
> receiver in an SSM session does not make use of RAMS, but wants to=20
> receive retransmissions, then integrating the "pub-port" functionality

> in the RAMS-R will not help here. That is why it makes most sense to=20
> define a dedicated RTCP "pub-port" message that can be combined with=20
> an RAMS-R or with a NACK.. Or with any other future RTCP request=20
> message that may be defined and relies on the same ssm with feedback=20
> target architecture..
> And I also think that we should consider a "default" case that when an

> RTP receiver does not signal its ports, the retransmission server=20
> understands the RTP receiver expects the retransmission/burst on the=20
> port, that was used by the RTP receiver as source port to request the=20
> retransmission and burst. But that should imply that the "pub-port"
> MUST
> always be sent in a single compound together with the NACK and/or the=20
> RAMS-R message (either of these) that triggers the retransmission=20
> session.
>=20
> Tom
>=20
>=20
> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: vrijdag 26 juni 2009 10:31
> To: 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C. Begen (abegen)';=20
> VAN CAENEGEM Tom; avt@ietf.org
> Subject: RE: Port mappings, NAT, and RAMS
>=20
> Hi Bill,
> I think I was the one who started this discussion but it looks to me=20
> like it is going too far since some of this work are not in the AVT=20
> charter.
>=20
> The RAMS solution is based on SSM and Retransmission and if there is a

> problem with NATs in these drafts it should be discussed there. My=20
> concern was different. The AVT solution is using SDP for specifying=20
> address information. In the case of both SSM and retransmission, the=20
> server can provide their address (which they may have obtained by=20
> using any method they
> chose) in the SDP. This works both for offer/answer and declarative=20
> SDP.
> I see no reason to address this topic in the RAMS draft
>=20
> The RAMS draft need to provide other addresses which are the RR RTP=20
> and RTCP receive addresses. In the case of offer answer this is clear=20
> by for declarative SDP the RR does not sent an SDP so cannot provide=20
> receive addresses.
>=20
>=20
> In the case of RFC 4588 the retransmission can be based on session or=20
> SSRC multiplexing and defines how to use SDP to provide the addresses.
> The difference is that RFC 4588 do not address a unicast=20
> retransmission for a multicast stream which is the special case=20
> described here.  In the current case the SSRC multiplexing mode of RFC

> 4588 is not relevant so there MUST be a way for the RR to provide its=20
> receiving addresses to the RS.
>=20
> Since this solution do not work in offer/answer but is based on=20
> declarative SDP there need to be other way for the RR to provide the=20
> addressed
>=20
>=20
> My view based on the text above about SSM and RFC 4588 is that this is

> a special case and not a general case and this is why I suggested to=20
> add the address information to the RAMS-R message.
>=20
> Roni Even
>=20
>=20
> > -----Original Message-----
> > From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> > Sent: Wednesday, June 24, 2009 3:37 PM
> > To: Zeev Vax; Ali C. Begen (abegen); Roni Even; VANCAENEGEM Tom;=20
> > avt@ietf.org
> > Subject: Port mappings, NAT, and RAMS
> >
> >
> > There has been some discussion around the requirement for a NAT=20
> > section in the latest RAMS draft. This note is an attempt to clarify

> > the requirement to signal RAMS port mappings. Once we come to a=20
> > consensus as to the desired behavior, we can update the draft.
> >
> > This text refers to a ppt document that can be found at=20
> > ftp://ftpeng.cisco.com/abegen/PubPorts.pdf
> >
> > When using RAMS to accelerate acquisition of a multicast flow, there

> > are two sessions - the primary multicast session and the=20
> > acceleration session. These sessions may have multiple socket=20
> > contexts, depending on the use of RTP/RTP port muxing. However, the=20
> > primary multicast session and the retransmission session are always
distinct.
> >
> > 1- The primary multicast session - two logical flows defined by the=20
> > Source address, Destination Multicast Address, RTP port (P1) and=20
> > RTCP port(P2). This set of flows is shown in RED in the diagram.
> > 2- The retransmission/acceleration session, shown in BLUE in the=20
> > diagram. In the most general non-port-muxed, non-NATed case, this=20
> > stream consists of 2 flows. The first (RTP) flow is defined by the=20
> > 5-tuple of UDP, IP address of the FT, RTP port configured by SDP
> (P3),
>=20
> > the IP address of the client and the RTP port dynamically chosen by
> RR
>=20
> > (c3).
> > The second (RTCP) flow is defined by the 5-tuple of UDP, FT address,

> > the RTCP port defined by SDP (P4), the IP address of the client and=20
> > the RTCP port dynamically chosen by RR (c4). When RTP/RTCP port
> muxing
>=20
> > is used, the retransmission session is collapsed onto a single=20
> > 5-tuple.
> >
> > Note that the feedback target for the primary session is P2 on
FT/RS.
> > Note that the acceleration burst must flow from FT P3/P4 to C c3/c4.
> > In other words, the first desired data flow on the retransmission=20
> > session is "downstream".
> >
> > When we introduce NAT, we need to map c3 to c3' (and in the absence
> of
>=20
> > port muxing, also c4 to c4') through the NAT device. This diagram=20
> > shows the use of STUN in YELLOW to setup the port mappings, but=20
> > other methods could be used.
> >
> >
> >
> > In summary, the ppt describes 4 options-
> >
> > Drawing 1 - No muxing - Stun request, bind for two ports and send=20
> > PubPorts with RAMS-R to signal both, followed by the burst.
> > Drawing 2 - Muxing - Stun request, bind for one port and send
> PubPorts
>=20
> > with RAMS-R to signal a single port, followed by the burst.
> > Drawing 3 - Muxing - No explicit STUN request/bind. Send PubPorts
> with
>=20
> > RAMS-R to signal RS to use the src port of the incoming RTCP packet
> as
>=20
> > the destination for both RTP and RTCP in the ret session (We do this

> > by putting 0's in the pubports messages). Note that this does not
> work
>=20
> > through all NAT variants. The RAMS-R/PubPorts message is sent from
> > c4 to P2. The burst is sent from P4 to c4', and certain NATs will=20
> > not pass this traffic.
> > Drawing 4 - Muxing - No explicite STUN request/bind. Send PubPorts=20
> > from
> > c4 to P4, initializing NAT bindings. Send RAMS-R, followed by the=20
> > burst.
> > This works through all NAT types. There is concern about the=20
> > decoupling of the PubPorts from the RAMS-R, as dropped messages may=20
> > cause problems.
> >
> > Hopefully this note clarifies the need to signal the ports.
> >
> > Inputs on ths problem are desired. We need to decide if the PubPorts

> > is the right way to go, and if the transaction is RAMS specific or=20
> > is a generic RTP/RTCP message. Once we make that determination, we=20
> > need to lay out the details of the message format.
> >
> > Based on the feedback - we will abandon the idea, keep it in the=20
> > draft, or write a separate draft for it.
> >
> > Bill VerSteeg (with extensive input from Ali Begen and Dan Wing)
> >
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf=20
> > Of Zeev Vax
> > Sent: Thursday, June 18, 2009 5:58 PM
> > To: Ali C. Begen (abegen); Roni Even; Bill Ver Steeg (versteb);=20
> > VANCAENEGEM Tom; avt@ietf.org
> > Subject: Re: [AVT] comments on
> > section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> >
> > If we assume all entities are one, why would you need to signal the=20
> > retransmission port separately ?
> >
> > Zeev
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From Even.roni@huawei.com  Fri Jun 26 07:54:12 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B5DB33A68D4 for <avt@core3.amsl.com>; Fri, 26 Jun 2009 07:54:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.216
X-Spam-Level: 
X-Spam-Status: No, score=-1.216 tagged_above=-999 required=5 tests=[AWL=1.384,  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 mpfNadQYorCF for <avt@core3.amsl.com>; Fri, 26 Jun 2009 07:54:11 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id AA9D328C140 for <avt@ietf.org>; Fri, 26 Jun 2009 07:54:07 -0700 (PDT)
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 <0KLU007Q0PE1GV@szxga03-in.huawei.com> for avt@ietf.org; Fri, 26 Jun 2009 22:54:01 +0800 (CST)
Received: from huawei.com ([172.24.1.3]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLU00BJ1PE1CO@szxga03-in.huawei.com> for avt@ietf.org; Fri, 26 Jun 2009 22:54:01 +0800 (CST)
Received: from windows8d787f9 (bzq-79-182-68-39.red.bezeqint.net [79.182.68.39]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KLU006ULPD5U4@szxml01-in.huawei.com>; Fri, 26 Jun 2009 22:54:01 +0800 (CST)
Date: Fri, 26 Jun 2009 17:53:15 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <238382595265324EA50F6134BB42DCAF04137859@FRVELSMBS22.ad2.ad.alcatel.com>
To: 'VAN CAENEGEM Tom' <Tom.Van_Caenegem@alcatel-lucent.be>, "'Bill Ver Steeg (versteb)'" <versteb@cisco.com>, 'Zeev Vax' <zeevvax@microsoft.com>, "'Ali C. Begen (abegen)'" <abegen@cisco.com>, avt@ietf.org
Message-id: <01a101c9f66d$e3317ff0$a9947fd0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDgARoKBSAAW0fO0AABD/mgAAGLzyAAALbj8AAKyqEw
iPlanet-SMTP-Warning: Lines longer than SMTP allows found and truncated.
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <018901c9f638$7a286940$6e793bc0$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF04137758@FRVELSMBS22.ad2.ad.alcatel.com>
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 26 Jun 2009 14:54:12 -0000

Tom,
I do not agree that we need a solution for SSM + retransmission not in the
architecture of RAMS. Can you show me such a use and why not use RAMS.
The assumption is that the first request for retransmission is going to the
FT. If the request goes to the retransmission server, you can use RTP/RTCP
multiplexing.
Roni 

> -----Original Message-----
> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> Sent: Friday, June 26, 2009 1:10 PM
> To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen
> (abegen); avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
> 
> Roni,
> 
> See inline
> 
> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: vrijdag 26 juni 2009 11:34
> To: VAN CAENEGEM Tom; 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C.
> Begen (abegen)'; avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
> 
> Tom,
> What bothering me is that I do not want to make RTCP as a general
> mechanism to provide addressing information.
> 
> TOM: I understand
> 
> I still do not see this a a general problem. The case you described
> (SSM
> with retransmission), except for the RAMS case there is no other
> application that requires that, it requires co-location of the FT and
> retransmission source, you send the retransmission request to the
> feedback target and not to the retransmission server.
> 
> TOM: not sure I understand your exact point here. Do you agree that we
> need a similar solution for SSM with retransmission (-only)  AND SSM
> with RAMS (+ retransmission)?  In that case, it does not make sense to
> specify ONLY a RAMS-R with the port information, you also need to do
> that then for a NACK message. NACK is already defined, so that is why I
> think that specifying a separate RTCP message is the way out here. But
> because this is related to ssm and retransmission, it cannot be done in
> this RAMS draft only. I do agree that such message can only be used in
> the context of ssm with unicast feedback.
> 
> 
> If this was a general problem it should be addressed in the context of
> retransmission or SSM.
> 
> Roni
> 
> 
> 
> 
> 
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> > VAN CAENEGEM Tom
> > Sent: Friday, June 26, 2009 11:52 AM
> > To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen
> > (abegen); avt@ietf.org
> > Subject: Re: [AVT] Port mappings, NAT, and RAMS
> >
> > Hi Roni,
> >
> > The problem I see here is that this is broader than RAMS: if an RTP
> > receiver in an SSM session does not make use of RAMS, but wants to
> > receive retransmissions, then integrating the "pub-port"
> functionality
> 
> > in the RAMS-R will not help here. That is why it makes most sense to
> > define a dedicated RTCP "pub-port" message that can be combined with
> > an RAMS-R or with a NACK.. Or with any other future RTCP request
> > message that may be defined and relies on the same ssm with feedback
> > target architecture..
> > And I also think that we should consider a "default" case that when
> an
> 
> > RTP receiver does not signal its ports, the retransmission server
> > understands the RTP receiver expects the retransmission/burst on the
> > port, that was used by the RTP receiver as source port to request the
> > retransmission and burst. But that should imply that the "pub-port"
> > MUST
> > always be sent in a single compound together with the NACK and/or the
> > RAMS-R message (either of these) that triggers the retransmission
> > session.
> >
> > Tom
> >
> >
> > -----Original Message-----
> > From: Roni Even [mailto:Even.roni@huawei.com]
> > Sent: vrijdag 26 juni 2009 10:31
> > To: 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C. Begen (abegen)';
> > VAN CAENEGEM Tom; avt@ietf.org
> > Subject: RE: Port mappings, NAT, and RAMS
> >
> > Hi Bill,
> > I think I was the one who started this discussion but it looks to me
> > like it is going too far since some of this work are not in the AVT
> > charter.
> >
> > The RAMS solution is based on SSM and Retransmission and if there is
> a
> 
> > problem with NATs in these drafts it should be discussed there. My
> > concern was different. The AVT solution is using SDP for specifying
> > address information. In the case of both SSM and retransmission, the
> > server can provide their address (which they may have obtained by
> > using any method they
> > chose) in the SDP. This works both for offer/answer and declarative
> > SDP.
> > I see no reason to address this topic in the RAMS draft
> >
> > The RAMS draft need to provide other addresses which are the RR RTP
> > and RTCP receive addresses. In the case of offer answer this is clear
> > by for declarative SDP the RR does not sent an SDP so cannot provide
> > receive addresses.
> >
> >
> > In the case of RFC 4588 the retransmission can be based on session or
> > SSRC multiplexing and defines how to use SDP to provide the
> addresses.
> > The difference is that RFC 4588 do not address a unicast
> > retransmission for a multicast stream which is the special case
> > described here.  In the current case the SSRC multiplexing mode of
> RFC
> 
> > 4588 is not relevant so there MUST be a way for the RR to provide its
> > receiving addresses to the RS.
> >
> > Since this solution do not work in offer/answer but is based on
> > declarative SDP there need to be other way for the RR to provide the
> > addressed
> >
> >
> > My view based on the text above about SSM and RFC 4588 is that this
> is
> 
> > a special case and not a general case and this is why I suggested to
> > add the address information to the RAMS-R message.
> >
> > Roni Even
> >
> >
> > > -----Original Message-----
> > > From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> > > Sent: Wednesday, June 24, 2009 3:37 PM
> > > To: Zeev Vax; Ali C. Begen (abegen); Roni Even; VANCAENEGEM Tom;
> > > avt@ietf.org
> > > Subject: Port mappings, NAT, and RAMS
> > >
> > >
> > > There has been some discussion around the requirement for a NAT
> > > section in the latest RAMS draft. This note is an attempt to
> clarify
> 
> > > the requirement to signal RAMS port mappings. Once we come to a
> > > consensus as to the desired behavior, we can update the draft.
> > >
> > > This text refers to a ppt document that can be found at
> > > ftp://ftpeng.cisco.com/abegen/PubPorts.pdf
> > >
> > > When using RAMS to accelerate acquisition of a multicast flow,
> there
> 
> > > are two sessions - the primary multicast session and the
> > > acceleration session. These sessions may have multiple socket
> > > contexts, depending on the use of RTP/RTP port muxing. However, the
> > > primary multicast session and the retransmission session are always
> distinct.
> > >
> > > 1- The primary multicast session - two logical flows defined by the
> > > Source address, Destination Multicast Address, RTP port (P1) and
> > > RTCP port(P2). This set of flows is shown in RED in the diagram.
> > > 2- The retransmission/acceleration session, shown in BLUE in the
> > > diagram. In the most general non-port-muxed, non-NATed case, this
> > > stream consists of 2 flows. The first (RTP) flow is defined by the
> > > 5-tuple of UDP, IP address of the FT, RTP port configured by SDP
> > (P3),
> >
> > > the IP address of the client and the RTP port dynamically chosen by
> > RR
> >
> > > (c3).
> > > The second (RTCP) flow is defined by the 5-tuple of UDP, FT
> address,
> 
> > > the RTCP port defined by SDP (P4), the IP address of the client and
> > > the RTCP port dynamically chosen by RR (c4). When RTP/RTCP port
> > muxing
> >
> > > is used, the retransmission session is collapsed onto a single
> > > 5-tuple.
> > >
> > > Note that the feedback target for the primary session is P2 on
> FT/RS.
> > > Note that the acceleration burst must flow from FT P3/P4 to C
> c3/c4.
> > > In other words, the first desired data flow on the retransmission
> > > session is "downstream".
> > >
> > > When we introduce NAT, we need to map c3 to c3' (and in the absence
> > of
> >
> > > port muxing, also c4 to c4') through the NAT device. This diagram
> > > shows the use of STUN in YELLOW to setup the port mappings, but
> > > other methods could be used.
> > >
> > >
> > >
> > > In summary, the ppt describes 4 options-
> > >
> > > Drawing 1 - No muxing - Stun request, bind for two ports and send
> > > PubPorts with RAMS-R to signal both, followed by the burst.
> > > Drawing 2 - Muxing - Stun request, bind for one port and send
> > PubPorts
> >
> > > with RAMS-R to signal a single port, followed by the burst.
> > > Drawing 3 - Muxing - No explicit STUN request/bind. Send PubPorts
> > with
> >
> > > RAMS-R to signal RS to use the src port of the incoming RTCP packet
> > as
> >
> > > the destination for both RTP and RTCP in the ret session (We do
> this
> 
> > > by putting 0's in the pubports messages). Note that this does not
> > work
> >
> > > through all NAT variants. The RAMS-R/PubPorts message is sent from
> > > c4 to P2. The burst is sent from P4 to c4', and certain NATs will
> > > not pass this traffic.
> > > Drawing 4 - Muxing - No explicite STUN request/bind. Send PubPorts
> > > from
> > > c4 to P4, initializing NAT bindings. Send RAMS-R, followed by the
> > > burst.
> > > This works through all NAT types. There is concern about the
> > > decoupling of the PubPorts from the RAMS-R, as dropped messages may
> > > cause problems.
> > >
> > > Hopefully this note clarifies the need to signal the ports.
> > >
> > > Inputs on ths problem are desired. We need to decide if the
> PubPorts
> 
> > > is the right way to go, and if the transaction is RAMS specific or
> > > is a generic RTP/RTCP message. Once we make that determination, we
> > > need to lay out the details of the message format.
> > >
> > > Based on the feedback - we will abandon the idea, keep it in the
> > > draft, or write a separate draft for it.
> > >
> > > Bill VerSteeg (with extensive input from Ali Begen and Dan Wing)
> > >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
> > > Of Zeev Vax
> > > Sent: Thursday, June 18, 2009 5:58 PM
> > > To: Ali C. Begen (abegen); Roni Even; Bill Ver Steeg (versteb);
> > > VANCAENEGEM Tom; avt@ietf.org
> > > Subject: Re: [AVT] comments on
> > > section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > >
> > > If we assume all entities are one, why would you need to signal the
> > > retransmission port separately ?
> > >
> > > Zeev
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt


From Tom.Van_Caenegem@alcatel-lucent.be  Fri Jun 26 08:41:28 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 DDAFE28C0EC for <avt@core3.amsl.com>; Fri, 26 Jun 2009 08:41:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.049
X-Spam-Level: 
X-Spam-Status: No, score=-4.049 tagged_above=-999 required=5 tests=[AWL=-1.800, BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s-+elMkakpjr for <avt@core3.amsl.com>; Fri, 26 Jun 2009 08:41:27 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by core3.amsl.com (Postfix) with ESMTP id 9D5DB3A6B6C for <avt@ietf.org>; Fri, 26 Jun 2009 08:41:26 -0700 (PDT)
Received: from FRVELSBHS05.ad2.ad.alcatel.com (frvelsbhs05.dc-m.alcatel-lucent.com [155.132.6.77]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5QFfPFO027381;  Fri, 26 Jun 2009 17:41:25 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.51]) by FRVELSBHS05.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 26 Jun 2009 17:41:25 +0200
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: Fri, 26 Jun 2009 17:41:23 +0200
Message-ID: <238382595265324EA50F6134BB42DCAF04137B5C@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <01a101c9f66d$e3317ff0$a9947fd0$%roni@huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Port mappings, NAT, and RAMS
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDgARoKBSAAW0fO0AABD/mgAAGLzyAAALbj8AAKyqEwAABC2oA=
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <018901c9f638$7a286940$6e793bc0$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF04137758@FRVELSMBS22.ad2.ad.alcatel.com> <01a101c9f66d$e3317ff0$a9! 947fd0$%r oni@huawei.com>
From: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>
To: "Roni Even" <Even.roni@huawei.com>, "Bill Ver Steeg (versteb)" <versteb@cisco.com>, "Zeev Vax" <zeevvax@microsoft.com>, "Ali C. Begen (abegen)" <abegen@cisco.com>, <avt@ietf.org>
X-OriginalArrivalTime: 26 Jun 2009 15:41:25.0695 (UTC) FILETIME=[90744CF0:01C9F674]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 26 Jun 2009 15:41:29 -0000

Hi Roni,

My perspective here is the one from real operator networks where
operators are providing IPTV services making use of RTP, including
multicast services. IPTV operators need to address packet loss, and one
way to address this is by making use of RTP retransmissions. I lead the
standardisation effort in DVB in 2007-2008, where we defined the RTP
retransmission solution referring to rtcp-ssm draft, RFC 4585 (defining
AVT-FB profile and RTCP FB message such as NACK) and RFC 4588
(Retransmission), and also the RTP mux draft. Hence this
architecture/solution is based on ssm, and the RTP receiver needs to
send all its RTCP messges , including the RTCP NACK FB, to the feedback
target. The feedback target is also here the same entity as the
retransmission server. DVB has its own way of signaling parameters, but
also here we were facing the fact that parameters are signaled to the
receivers. The receivers do not/cannot signal towards the FT/RET server
which ports they want. So we took a shortcut by allowing that the
destination port of the RTP packet could be defined by the system (so
quite exotic) OR when this port was not signaled, the RTP receiver knew
that the RTP retransmission packet port matches the source port it used
in the NACK messages. There have been some email exchanges from DVB with
AVT when this work was conducted, but there was not that much
interaction.

RAMS is a solution that addresses a different topic, that is: how to
shorten zapping response times. From a service need point of view,
packet loss repair and minimising zapping times are quite separate
topics: some operators may only be interested in achieving high image
quality (relying on retransmissions), others may (also) want to offer
smallest zapping response times without impact on quality (relying on
RAMS messaging). Note also that a "retransmission service" and  -what is
called in DVB-  "fast channel change service" impose quite different
loads onto the networks, especially when these servers are localised
deep in the network. So that may for instance be a reason why some IPTV
service providers do not want "fast channel change" service, but do need
retransmission service.  So, imposing to use "RAMS" for an IPTV service
that provides retransmission(-only) support -to allow a standards way by
which the receiver itself can select its ports- is quite absurd, and
will not work.=20

In short: the architecture for retransmissions-only and for "fast
channel change" service are exactly the same, but RAMS as such has
nothing to do with retransmission service, still faces the same problem
of port signaling.=20

Tom


=20

-----Original Message-----
From: Roni Even [mailto:Even.roni@huawei.com]=20
Sent: vrijdag 26 juni 2009 16:53
To: VAN CAENEGEM Tom; 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C.
Begen (abegen)'; avt@ietf.org
Subject: RE: [AVT] Port mappings, NAT, and RAMS

Tom,
I do not agree that we need a solution for SSM + retransmission not in
the architecture of RAMS. Can you show me such a use and why not use
RAMS.
The assumption is that the first request for retransmission is going to
the FT. If the request goes to the retransmission server, you can use
RTP/RTCP multiplexing.
Roni=20

> -----Original Message-----
> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> Sent: Friday, June 26, 2009 1:10 PM
> To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen=20
> (abegen); avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
>=20
> Roni,
>=20
> See inline
>=20
> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: vrijdag 26 juni 2009 11:34
> To: VAN CAENEGEM Tom; 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C.
> Begen (abegen)'; avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
>=20
> Tom,
> What bothering me is that I do not want to make RTCP as a general=20
> mechanism to provide addressing information.
>=20
> TOM: I understand
>=20
> I still do not see this a a general problem. The case you described=20
> (SSM with retransmission), except for the RAMS case there is no other=20
> application that requires that, it requires co-location of the FT and=20
> retransmission source, you send the retransmission request to the=20
> feedback target and not to the retransmission server.
>=20
> TOM: not sure I understand your exact point here. Do you agree that we

> need a similar solution for SSM with retransmission (-only)  AND SSM=20
> with RAMS (+ retransmission)?  In that case, it does not make sense to

> specify ONLY a RAMS-R with the port information, you also need to do=20
> that then for a NACK message. NACK is already defined, so that is why=20
> I think that specifying a separate RTCP message is the way out here.=20
> But because this is related to ssm and retransmission, it cannot be=20
> done in this RAMS draft only. I do agree that such message can only be

> used in the context of ssm with unicast feedback.
>=20
>=20
> If this was a general problem it should be addressed in the context of

> retransmission or SSM.
>=20
> Roni
>=20
>=20
>=20
>=20
>=20
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf=20
> > Of VAN CAENEGEM Tom
> > Sent: Friday, June 26, 2009 11:52 AM
> > To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen=20
> > (abegen); avt@ietf.org
> > Subject: Re: [AVT] Port mappings, NAT, and RAMS
> >
> > Hi Roni,
> >
> > The problem I see here is that this is broader than RAMS: if an RTP=20
> > receiver in an SSM session does not make use of RAMS, but wants to=20
> > receive retransmissions, then integrating the "pub-port"
> functionality
>=20
> > in the RAMS-R will not help here. That is why it makes most sense to

> > define a dedicated RTCP "pub-port" message that can be combined with

> > an RAMS-R or with a NACK.. Or with any other future RTCP request=20
> > message that may be defined and relies on the same ssm with feedback

> > target architecture..
> > And I also think that we should consider a "default" case that when
> an
>=20
> > RTP receiver does not signal its ports, the retransmission server=20
> > understands the RTP receiver expects the retransmission/burst on the

> > port, that was used by the RTP receiver as source port to request=20
> > the retransmission and burst. But that should imply that the
"pub-port"
> > MUST
> > always be sent in a single compound together with the NACK and/or=20
> > the RAMS-R message (either of these) that triggers the=20
> > retransmission session.
> >
> > Tom
> >
> >
> > -----Original Message-----
> > From: Roni Even [mailto:Even.roni@huawei.com]
> > Sent: vrijdag 26 juni 2009 10:31
> > To: 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C. Begen (abegen)';

> > VAN CAENEGEM Tom; avt@ietf.org
> > Subject: RE: Port mappings, NAT, and RAMS
> >
> > Hi Bill,
> > I think I was the one who started this discussion but it looks to me

> > like it is going too far since some of this work are not in the AVT=20
> > charter.
> >
> > The RAMS solution is based on SSM and Retransmission and if there is
> a
>=20
> > problem with NATs in these drafts it should be discussed there. My=20
> > concern was different. The AVT solution is using SDP for specifying=20
> > address information. In the case of both SSM and retransmission, the

> > server can provide their address (which they may have obtained by=20
> > using any method they
> > chose) in the SDP. This works both for offer/answer and declarative=20
> > SDP.
> > I see no reason to address this topic in the RAMS draft
> >
> > The RAMS draft need to provide other addresses which are the RR RTP=20
> > and RTCP receive addresses. In the case of offer answer this is=20
> > clear by for declarative SDP the RR does not sent an SDP so cannot=20
> > provide receive addresses.
> >
> >
> > In the case of RFC 4588 the retransmission can be based on session=20
> > or SSRC multiplexing and defines how to use SDP to provide the
> addresses.
> > The difference is that RFC 4588 do not address a unicast=20
> > retransmission for a multicast stream which is the special case=20
> > described here.  In the current case the SSRC multiplexing mode of
> RFC
>=20
> > 4588 is not relevant so there MUST be a way for the RR to provide=20
> > its receiving addresses to the RS.
> >
> > Since this solution do not work in offer/answer but is based on=20
> > declarative SDP there need to be other way for the RR to provide the

> > addressed
> >
> >
> > My view based on the text above about SSM and RFC 4588 is that this
> is
>=20
> > a special case and not a general case and this is why I suggested to

> > add the address information to the RAMS-R message.
> >
> > Roni Even
> >
> >
> > > -----Original Message-----
> > > From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> > > Sent: Wednesday, June 24, 2009 3:37 PM
> > > To: Zeev Vax; Ali C. Begen (abegen); Roni Even; VANCAENEGEM Tom;=20
> > > avt@ietf.org
> > > Subject: Port mappings, NAT, and RAMS
> > >
> > >
> > > There has been some discussion around the requirement for a NAT=20
> > > section in the latest RAMS draft. This note is an attempt to
> clarify
>=20
> > > the requirement to signal RAMS port mappings. Once we come to a=20
> > > consensus as to the desired behavior, we can update the draft.
> > >
> > > This text refers to a ppt document that can be found at=20
> > > ftp://ftpeng.cisco.com/abegen/PubPorts.pdf
> > >
> > > When using RAMS to accelerate acquisition of a multicast flow,
> there
>=20
> > > are two sessions - the primary multicast session and the=20
> > > acceleration session. These sessions may have multiple socket=20
> > > contexts, depending on the use of RTP/RTP port muxing. However,=20
> > > the primary multicast session and the retransmission session are=20
> > > always
> distinct.
> > >
> > > 1- The primary multicast session - two logical flows defined by=20
> > > the Source address, Destination Multicast Address, RTP port (P1)=20
> > > and RTCP port(P2). This set of flows is shown in RED in the
diagram.
> > > 2- The retransmission/acceleration session, shown in BLUE in the=20
> > > diagram. In the most general non-port-muxed, non-NATed case, this=20
> > > stream consists of 2 flows. The first (RTP) flow is defined by the

> > > 5-tuple of UDP, IP address of the FT, RTP port configured by SDP
> > (P3),
> >
> > > the IP address of the client and the RTP port dynamically chosen=20
> > > by
> > RR
> >
> > > (c3).
> > > The second (RTCP) flow is defined by the 5-tuple of UDP, FT
> address,
>=20
> > > the RTCP port defined by SDP (P4), the IP address of the client=20
> > > and the RTCP port dynamically chosen by RR (c4). When RTP/RTCP=20
> > > port
> > muxing
> >
> > > is used, the retransmission session is collapsed onto a single=20
> > > 5-tuple.
> > >
> > > Note that the feedback target for the primary session is P2 on
> FT/RS.
> > > Note that the acceleration burst must flow from FT P3/P4 to C
> c3/c4.
> > > In other words, the first desired data flow on the retransmission=20
> > > session is "downstream".
> > >
> > > When we introduce NAT, we need to map c3 to c3' (and in the=20
> > > absence
> > of
> >
> > > port muxing, also c4 to c4') through the NAT device. This diagram=20
> > > shows the use of STUN in YELLOW to setup the port mappings, but=20
> > > other methods could be used.
> > >
> > >
> > >
> > > In summary, the ppt describes 4 options-
> > >
> > > Drawing 1 - No muxing - Stun request, bind for two ports and send=20
> > > PubPorts with RAMS-R to signal both, followed by the burst.
> > > Drawing 2 - Muxing - Stun request, bind for one port and send
> > PubPorts
> >
> > > with RAMS-R to signal a single port, followed by the burst.
> > > Drawing 3 - Muxing - No explicit STUN request/bind. Send PubPorts
> > with
> >
> > > RAMS-R to signal RS to use the src port of the incoming RTCP=20
> > > packet
> > as
> >
> > > the destination for both RTP and RTCP in the ret session (We do
> this
>=20
> > > by putting 0's in the pubports messages). Note that this does not
> > work
> >
> > > through all NAT variants. The RAMS-R/PubPorts message is sent from
> > > c4 to P2. The burst is sent from P4 to c4', and certain NATs will=20
> > > not pass this traffic.
> > > Drawing 4 - Muxing - No explicite STUN request/bind. Send PubPorts

> > > from
> > > c4 to P4, initializing NAT bindings. Send RAMS-R, followed by the=20
> > > burst.
> > > This works through all NAT types. There is concern about the=20
> > > decoupling of the PubPorts from the RAMS-R, as dropped messages=20
> > > may cause problems.
> > >
> > > Hopefully this note clarifies the need to signal the ports.
> > >
> > > Inputs on ths problem are desired. We need to decide if the
> PubPorts
>=20
> > > is the right way to go, and if the transaction is RAMS specific or

> > > is a generic RTP/RTCP message. Once we make that determination, we

> > > need to lay out the details of the message format.
> > >
> > > Based on the feedback - we will abandon the idea, keep it in the=20
> > > draft, or write a separate draft for it.
> > >
> > > Bill VerSteeg (with extensive input from Ali Begen and Dan Wing)
> > >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf

> > > Of Zeev Vax
> > > Sent: Thursday, June 18, 2009 5:58 PM
> > > To: Ali C. Begen (abegen); Roni Even; Bill Ver Steeg (versteb);=20
> > > VANCAENEGEM Tom; avt@ietf.org
> > > Subject: Re: [AVT] comments on
> > > section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > >
> > > If we assume all entities are one, why would you need to signal=20
> > > the retransmission port separately ?
> > >
> > > Zeev
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt


From abegen@cisco.com  Fri Jun 26 08:42:00 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 7D4E328C0EF for <avt@core3.amsl.com>; Fri, 26 Jun 2009 08:42:00 -0700 (PDT)
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 uti1WUeywzJv for <avt@core3.amsl.com>; Fri, 26 Jun 2009 08:41:59 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 8875D3A6B13 for <avt@ietf.org>; Fri, 26 Jun 2009 08:41:59 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,297,1243814400"; d="scan'208";a="206174846"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-1.cisco.com with ESMTP; 26 Jun 2009 15:42:18 +0000
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n5QFgHTj015970;  Fri, 26 Jun 2009 08:42:17 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id n5QFgHAw029991; Fri, 26 Jun 2009 15:42:17 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 26 Jun 2009 08:42:17 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 26 Jun 2009 08:41:12 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D54099E00C4@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <238382595265324EA50F6134BB42DCAF04137762@FRVELSMBS22.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Port mappings, NAT, and RAMS
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDgARoKBSAALhpHsAAKg7ngAAPu9/AALWBagA==
References: <mailman.10085.1245185397.4936.avt@ietf.org><238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com><015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com><238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com><04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com><81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com><3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com><025401c9effa$34040170$9c0c0450$%roni@huawei.com><3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com><04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04137224@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54099DFD1A@xmb-sjc-215.amer.cisco.com> <23838259526532 4EA50F61 34BB42DCAF04137762@FRVELSMBS22.ad2.ad.alcatel.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>, "Bill Ver Steeg (versteb)" <versteb@cisco.com>, "Zeev Vax" <zeevvax@microsoft.com>, "Roni Even" <Even.roni@huawei.com>,  <avt@ietf.org>
X-OriginalArrivalTime: 26 Jun 2009 15:42:17.0729 (UTC) FILETIME=[AF780F10:01C9F674]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4027; t=1246030937; x=1246894937; c=relaxed/simple; s=sjdkim1004; 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=20Port=20mappings,=20NAT,=20and=20RAMS |Sender:=20; bh=bghd0VYZzdvvtK6DLWJLfteoanWDj5YuTbGYFP7pW0M=; b=U4InQov8GrieyGl+B79SNK4FoWSAFhBi1OJ2Pk8x2o+T1J+wpdRsrUwLoD 9rjgybZUkTxX+voh1eA78FdhOYaCCdhdwMgO1wSQSFbbSJxT7G5EWOeyuVvM seOKxnRzHEC0VfUc2BnO9T+3SEmp8zCjrskqBEDkfG/NQCgy9n+Mo=;
Authentication-Results: sj-dkim-1; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 26 Jun 2009 15:42:00 -0000

Hi Tom,

[snip]
> The reason why we need pubports is that it indicates "explicitly" the
> port the client wants to use to receive the burst is the port it used =
to
> send the RAMS-R/pubports message. I believe we need this explicit
> indication, ow, we will be making an implicit assumption. Note that =
the
> rams-r/pubports is in the primary session and burst/ret packets are in
> the retransmission session, which is different than the primary.
>=20
> As far as I can see, not everybody agrees on this point, but we need =
to
> make a decision here before we mandate anything.
>=20
> TOM: I agree with your last line, but I do not completely agree when =
you
> mention "implicit" assumption, especially for option 3, where RAMS-R =
(or
> NACK) and the Pub-port message are in the same compound message. If we
> "define" that if no pub-report message is sent by the RR, the
> information towards the Retransmission server is exactly the same as
> when an RTP receiver sends an RTCP compound message made up of an RTCP
> NACK/RAMS-R together with a pub-port message where the ports are =
"zero"

We "may" be able to say it from RAMS-R but not for NACK since we are not =
defining it, we will be overloading its meaning, IMO. And as you/Bill =
pointed out in other emails, I also believe that this is more general =
problem than just RAMS. We need something like pubports for NACKs as =
well.


> -as currently proposed in the RAMS draft now.  I agree that this is =
not
> true for option 4, where pub-port and RAMS-R or NACK are separate
> messages, but I do not favour the solution of option 4 for the same
> reason you mention in your reply (a new failure mode). So, if option 4
> is -for that reason- no longer considered, I do not see a problem with
> defining this rule/clause as expressed above. In other words, there is
> no need for a pub-report message in this scenario and this results NOT
> in an "assumption" what-so-ever.
>=20
>=20
> > supports RTP/RTCP muxing itself, and if it knows the RS supports
> > RTP/RTCP muxing too (as indicated in the declarative sdp received by
> > the
> > RR)
> >
> > -Don't we also allow that for option 3, the port P2 actually equals
> > port P4? This is a kind of hybrid of session and SSRC multiplexing =
of
> > the primary multicast RTP stream and the retransmission/acceleration
> > session
> > :  on the unidirectional RTP layer, the primary MC packets and the
> > unicast retransmission packets are clearly session muxed, but the =
RTCP
>=20
> > "return" channel for both streams have exactly the same transport
> > addresses, but are distinguished by means of a different SSRC.  In
> > that
>=20
> How? Since SSM and retransmission sessions are session muxed, they =
have
> the same SSRC. When a client is sending a receiver report, how do we
> identify which session it belongs to? So, I believe P2 should be
> different than P4.
>=20
> TOM: you are right. But notice this: RFC 4588 mandates that when =
session
> muxing is used for retransmission, than the SSRC should be the same.
> However the RFC 4588 does not give arguments why it needs to be like
> that. So I ask you: what would or can happen if there is a different
> SSRC used?  If there are no convincing arguments why we must stick to

Good question. If we don't use the same SSRC in session-muxed RTP =
sessions, it will introduce correlation problems. Receiver/XR reports =
coming from a larger number of receivers will be difficult to identify =
and match at the server side. There will be SSRC collisions, which will =
complicate things further.

> the same SSRC, then, if we have a good use case to depart from that
> "rule" -and the use case we are discussing here is IMO indeed a valid
> use case- I do not see why we should be limited by such a "rule". The
> "valid" use case is here that RAMS and Retransmission for SSM sessions
> operates fine through any NAPT and without any dedicated RTCP message.

-acbegen

From Even.roni@huawei.com  Fri Jun 26 08:58:24 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3FFCC3A6922 for <avt@core3.amsl.com>; Fri, 26 Jun 2009 08:58:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.492
X-Spam-Level: 
X-Spam-Status: No, score=-1.492 tagged_above=-999 required=5 tests=[AWL=1.107,  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 qNrpzCPHunn8 for <avt@core3.amsl.com>; Fri, 26 Jun 2009 08:58:22 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id ED93E3A6AE0 for <avt@ietf.org>; Fri, 26 Jun 2009 08:58:21 -0700 (PDT)
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 <0KLU00DXNSD9HJ@szxga03-in.huawei.com> for avt@ietf.org; Fri, 26 Jun 2009 23:58:21 +0800 (CST)
Received: from huawei.com ([172.24.1.3]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLU00BF6SD9CO@szxga03-in.huawei.com> for avt@ietf.org; Fri, 26 Jun 2009 23:58:21 +0800 (CST)
Received: from windows8d787f9 (bzq-79-182-68-39.red.bezeqint.net [79.182.68.39]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KLU007Y6S9A17@szxml01-in.huawei.com>; Fri, 26 Jun 2009 23:58:21 +0800 (CST)
Date: Fri, 26 Jun 2009 18:55:42 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <238382595265324EA50F6134BB42DCAF04137B5C@FRVELSMBS22.ad2.ad.alcatel.com>
To: 'VAN CAENEGEM Tom' <Tom.Van_Caenegem@alcatel-lucent.be>, "'Bill Ver Steeg (versteb)'" <versteb@cisco.com>, 'Zeev Vax' <zeevvax@microsoft.com>, "'Ali C. Begen (abegen)'" <abegen@cisco.com>, avt@ietf.org
Message-id: <01af01c9f676$b970efd0$2c52cf70$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDgARoKBSAAW0fO0AABD/mgAAGLzyAAALbj8AAKyqEwAABC2oAAAel2MA==
iPlanet-SMTP-Warning: Lines longer than SMTP allows found and truncated.
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <018901c9f638$7a286940$6e793bc0$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF04137758@FRVELSMBS22.ad2.ad.alcatel.com>
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 26 Jun 2009 15:58:24 -0000

Tom,
So maybe, since it is the same architecture,  it is a good time to allow
RAMS-R to only signal retransmission.  

Roni

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> VAN CAENEGEM Tom
> Sent: Friday, June 26, 2009 6:41 PM
> To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen
> (abegen); avt@ietf.org
> Subject: Re: [AVT] Port mappings, NAT, and RAMS
> 
> Hi Roni,
> 
> My perspective here is the one from real operator networks where
> operators are providing IPTV services making use of RTP, including
> multicast services. IPTV operators need to address packet loss, and one
> way to address this is by making use of RTP retransmissions. I lead the
> standardisation effort in DVB in 2007-2008, where we defined the RTP
> retransmission solution referring to rtcp-ssm draft, RFC 4585 (defining
> AVT-FB profile and RTCP FB message such as NACK) and RFC 4588
> (Retransmission), and also the RTP mux draft. Hence this
> architecture/solution is based on ssm, and the RTP receiver needs to
> send all its RTCP messges , including the RTCP NACK FB, to the feedback
> target. The feedback target is also here the same entity as the
> retransmission server. DVB has its own way of signaling parameters, but
> also here we were facing the fact that parameters are signaled to the
> receivers. The receivers do not/cannot signal towards the FT/RET server
> which ports they want. So we took a shortcut by allowing that the
> destination port of the RTP packet could be defined by the system (so
> quite exotic) OR when this port was not signaled, the RTP receiver knew
> that the RTP retransmission packet port matches the source port it used
> in the NACK messages. There have been some email exchanges from DVB
> with
> AVT when this work was conducted, but there was not that much
> interaction.
> 
> RAMS is a solution that addresses a different topic, that is: how to
> shorten zapping response times. From a service need point of view,
> packet loss repair and minimising zapping times are quite separate
> topics: some operators may only be interested in achieving high image
> quality (relying on retransmissions), others may (also) want to offer
> smallest zapping response times without impact on quality (relying on
> RAMS messaging). Note also that a "retransmission service" and  -what
> is
> called in DVB-  "fast channel change service" impose quite different
> loads onto the networks, especially when these servers are localised
> deep in the network. So that may for instance be a reason why some IPTV
> service providers do not want "fast channel change" service, but do
> need
> retransmission service.  So, imposing to use "RAMS" for an IPTV service
> that provides retransmission(-only) support -to allow a standards way
> by
> which the receiver itself can select its ports- is quite absurd, and
> will not work.
> 
> In short: the architecture for retransmissions-only and for "fast
> channel change" service are exactly the same, but RAMS as such has
> nothing to do with retransmission service, still faces the same problem
> of port signaling.
> 
> Tom
> 
> 
> 
> 
> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: vrijdag 26 juni 2009 16:53
> To: VAN CAENEGEM Tom; 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C.
> Begen (abegen)'; avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
> 
> Tom,
> I do not agree that we need a solution for SSM + retransmission not in
> the architecture of RAMS. Can you show me such a use and why not use
> RAMS.
> The assumption is that the first request for retransmission is going to
> the FT. If the request goes to the retransmission server, you can use
> RTP/RTCP multiplexing.
> Roni
> 
> > -----Original Message-----
> > From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> > Sent: Friday, June 26, 2009 1:10 PM
> > To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen
> > (abegen); avt@ietf.org
> > Subject: RE: [AVT] Port mappings, NAT, and RAMS
> >
> > Roni,
> >
> > See inline
> >
> > -----Original Message-----
> > From: Roni Even [mailto:Even.roni@huawei.com]
> > Sent: vrijdag 26 juni 2009 11:34
> > To: VAN CAENEGEM Tom; 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C.
> > Begen (abegen)'; avt@ietf.org
> > Subject: RE: [AVT] Port mappings, NAT, and RAMS
> >
> > Tom,
> > What bothering me is that I do not want to make RTCP as a general
> > mechanism to provide addressing information.
> >
> > TOM: I understand
> >
> > I still do not see this a a general problem. The case you described
> > (SSM with retransmission), except for the RAMS case there is no other
> > application that requires that, it requires co-location of the FT and
> > retransmission source, you send the retransmission request to the
> > feedback target and not to the retransmission server.
> >
> > TOM: not sure I understand your exact point here. Do you agree that
> we
> 
> > need a similar solution for SSM with retransmission (-only)  AND SSM
> > with RAMS (+ retransmission)?  In that case, it does not make sense
> to
> 
> > specify ONLY a RAMS-R with the port information, you also need to do
> > that then for a NACK message. NACK is already defined, so that is why
> > I think that specifying a separate RTCP message is the way out here.
> > But because this is related to ssm and retransmission, it cannot be
> > done in this RAMS draft only. I do agree that such message can only
> be
> 
> > used in the context of ssm with unicast feedback.
> >
> >
> > If this was a general problem it should be addressed in the context
> of
> 
> > retransmission or SSM.
> >
> > Roni
> >
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
> > > Of VAN CAENEGEM Tom
> > > Sent: Friday, June 26, 2009 11:52 AM
> > > To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen
> > > (abegen); avt@ietf.org
> > > Subject: Re: [AVT] Port mappings, NAT, and RAMS
> > >
> > > Hi Roni,
> > >
> > > The problem I see here is that this is broader than RAMS: if an RTP
> > > receiver in an SSM session does not make use of RAMS, but wants to
> > > receive retransmissions, then integrating the "pub-port"
> > functionality
> >
> > > in the RAMS-R will not help here. That is why it makes most sense
> to
> 
> > > define a dedicated RTCP "pub-port" message that can be combined
> with
> 
> > > an RAMS-R or with a NACK.. Or with any other future RTCP request
> > > message that may be defined and relies on the same ssm with
> feedback
> 
> > > target architecture..
> > > And I also think that we should consider a "default" case that when
> > an
> >
> > > RTP receiver does not signal its ports, the retransmission server
> > > understands the RTP receiver expects the retransmission/burst on
> the
> 
> > > port, that was used by the RTP receiver as source port to request
> > > the retransmission and burst. But that should imply that the
> "pub-port"
> > > MUST
> > > always be sent in a single compound together with the NACK and/or
> > > the RAMS-R message (either of these) that triggers the
> > > retransmission session.
> > >
> > > Tom
> > >
> > >
> > > -----Original Message-----
> > > From: Roni Even [mailto:Even.roni@huawei.com]
> > > Sent: vrijdag 26 juni 2009 10:31
> > > To: 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C. Begen
> (abegen)';
> 
> > > VAN CAENEGEM Tom; avt@ietf.org
> > > Subject: RE: Port mappings, NAT, and RAMS
> > >
> > > Hi Bill,
> > > I think I was the one who started this discussion but it looks to
> me
> 
> > > like it is going too far since some of this work are not in the AVT
> > > charter.
> > >
> > > The RAMS solution is based on SSM and Retransmission and if there
> is
> > a
> >
> > > problem with NATs in these drafts it should be discussed there. My
> > > concern was different. The AVT solution is using SDP for specifying
> > > address information. In the case of both SSM and retransmission,
> the
> 
> > > server can provide their address (which they may have obtained by
> > > using any method they
> > > chose) in the SDP. This works both for offer/answer and declarative
> > > SDP.
> > > I see no reason to address this topic in the RAMS draft
> > >
> > > The RAMS draft need to provide other addresses which are the RR RTP
> > > and RTCP receive addresses. In the case of offer answer this is
> > > clear by for declarative SDP the RR does not sent an SDP so cannot
> > > provide receive addresses.
> > >
> > >
> > > In the case of RFC 4588 the retransmission can be based on session
> > > or SSRC multiplexing and defines how to use SDP to provide the
> > addresses.
> > > The difference is that RFC 4588 do not address a unicast
> > > retransmission for a multicast stream which is the special case
> > > described here.  In the current case the SSRC multiplexing mode of
> > RFC
> >
> > > 4588 is not relevant so there MUST be a way for the RR to provide
> > > its receiving addresses to the RS.
> > >
> > > Since this solution do not work in offer/answer but is based on
> > > declarative SDP there need to be other way for the RR to provide
> the
> 
> > > addressed
> > >
> > >
> > > My view based on the text above about SSM and RFC 4588 is that this
> > is
> >
> > > a special case and not a general case and this is why I suggested
> to
> 
> > > add the address information to the RAMS-R message.
> > >
> > > Roni Even
> > >
> > >
> > > > -----Original Message-----
> > > > From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> > > > Sent: Wednesday, June 24, 2009 3:37 PM
> > > > To: Zeev Vax; Ali C. Begen (abegen); Roni Even; VANCAENEGEM Tom;
> > > > avt@ietf.org
> > > > Subject: Port mappings, NAT, and RAMS
> > > >
> > > >
> > > > There has been some discussion around the requirement for a NAT
> > > > section in the latest RAMS draft. This note is an attempt to
> > clarify
> >
> > > > the requirement to signal RAMS port mappings. Once we come to a
> > > > consensus as to the desired behavior, we can update the draft.
> > > >
> > > > This text refers to a ppt document that can be found at
> > > > ftp://ftpeng.cisco.com/abegen/PubPorts.pdf
> > > >
> > > > When using RAMS to accelerate acquisition of a multicast flow,
> > there
> >
> > > > are two sessions - the primary multicast session and the
> > > > acceleration session. These sessions may have multiple socket
> > > > contexts, depending on the use of RTP/RTP port muxing. However,
> > > > the primary multicast session and the retransmission session are
> > > > always
> > distinct.
> > > >
> > > > 1- The primary multicast session - two logical flows defined by
> > > > the Source address, Destination Multicast Address, RTP port (P1)
> > > > and RTCP port(P2). This set of flows is shown in RED in the
> diagram.
> > > > 2- The retransmission/acceleration session, shown in BLUE in the
> > > > diagram. In the most general non-port-muxed, non-NATed case, this
> > > > stream consists of 2 flows. The first (RTP) flow is defined by
> the
> 
> > > > 5-tuple of UDP, IP address of the FT, RTP port configured by SDP
> > > (P3),
> > >
> > > > the IP address of the client and the RTP port dynamically chosen
> > > > by
> > > RR
> > >
> > > > (c3).
> > > > The second (RTCP) flow is defined by the 5-tuple of UDP, FT
> > address,
> >
> > > > the RTCP port defined by SDP (P4), the IP address of the client
> > > > and the RTCP port dynamically chosen by RR (c4). When RTP/RTCP
> > > > port
> > > muxing
> > >
> > > > is used, the retransmission session is collapsed onto a single
> > > > 5-tuple.
> > > >
> > > > Note that the feedback target for the primary session is P2 on
> > FT/RS.
> > > > Note that the acceleration burst must flow from FT P3/P4 to C
> > c3/c4.
> > > > In other words, the first desired data flow on the retransmission
> > > > session is "downstream".
> > > >
> > > > When we introduce NAT, we need to map c3 to c3' (and in the
> > > > absence
> > > of
> > >
> > > > port muxing, also c4 to c4') through the NAT device. This diagram
> > > > shows the use of STUN in YELLOW to setup the port mappings, but
> > > > other methods could be used.
> > > >
> > > >
> > > >
> > > > In summary, the ppt describes 4 options-
> > > >
> > > > Drawing 1 - No muxing - Stun request, bind for two ports and send
> > > > PubPorts with RAMS-R to signal both, followed by the burst.
> > > > Drawing 2 - Muxing - Stun request, bind for one port and send
> > > PubPorts
> > >
> > > > with RAMS-R to signal a single port, followed by the burst.
> > > > Drawing 3 - Muxing - No explicit STUN request/bind. Send PubPorts
> > > with
> > >
> > > > RAMS-R to signal RS to use the src port of the incoming RTCP
> > > > packet
> > > as
> > >
> > > > the destination for both RTP and RTCP in the ret session (We do
> > this
> >
> > > > by putting 0's in the pubports messages). Note that this does not
> > > work
> > >
> > > > through all NAT variants. The RAMS-R/PubPorts message is sent
> from
> > > > c4 to P2. The burst is sent from P4 to c4', and certain NATs will
> > > > not pass this traffic.
> > > > Drawing 4 - Muxing - No explicite STUN request/bind. Send
> PubPorts
> 
> > > > from
> > > > c4 to P4, initializing NAT bindings. Send RAMS-R, followed by the
> > > > burst.
> > > > This works through all NAT types. There is concern about the
> > > > decoupling of the PubPorts from the RAMS-R, as dropped messages
> > > > may cause problems.
> > > >
> > > > Hopefully this note clarifies the need to signal the ports.
> > > >
> > > > Inputs on ths problem are desired. We need to decide if the
> > PubPorts
> >
> > > > is the right way to go, and if the transaction is RAMS specific
> or
> 
> > > > is a generic RTP/RTCP message. Once we make that determination,
> we
> 
> > > > need to lay out the details of the message format.
> > > >
> > > > Based on the feedback - we will abandon the idea, keep it in the
> > > > draft, or write a separate draft for it.
> > > >
> > > > Bill VerSteeg (with extensive input from Ali Begen and Dan Wing)
> > > >
> > > > -----Original Message-----
> > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> Behalf
> 
> > > > Of Zeev Vax
> > > > Sent: Thursday, June 18, 2009 5:58 PM
> > > > To: Ali C. Begen (abegen); Roni Even; Bill Ver Steeg (versteb);
> > > > VANCAENEGEM Tom; avt@ietf.org
> > > > Subject: Re: [AVT] comments on
> > > > section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > > >
> > > > If we assume all entities are one, why would you need to signal
> > > > the retransmission port separately ?
> > > >
> > > > Zeev
> > >
> > > _______________________________________________
> > > Audio/Video Transport Working Group
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From zeevvax@microsoft.com  Fri Jun 26 10:31:16 2009
Return-Path: <zeevvax@microsoft.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 EB2AA3A6949 for <avt@core3.amsl.com>; Fri, 26 Jun 2009 10:31:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 Vhw4udn-cNcd for <avt@core3.amsl.com>; Fri, 26 Jun 2009 10:31:15 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id D95553A6861 for <avt@ietf.org>; Fri, 26 Jun 2009 10:31:14 -0700 (PDT)
Received: from TK5EX14MLTC101.redmond.corp.microsoft.com (157.54.79.178) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.99.4; Fri, 26 Jun 2009 10:27:02 -0700
Received: from tk5ex14mbxc105.redmond.corp.microsoft.com ([157.54.79.177]) by TK5EX14MLTC101.redmond.corp.microsoft.com ([157.54.79.178]) with mapi; Fri, 26 Jun 2009 10:27:00 -0700
From: Zeev Vax <zeevvax@microsoft.com>
To: Roni Even <Even.roni@huawei.com>, 'VAN CAENEGEM Tom' <Tom.Van_Caenegem@alcatel-lucent.be>, "'Bill Ver Steeg (versteb)'" <versteb@cisco.com>, "'Ali C. Begen (abegen)'" <abegen@cisco.com>, "avt@ietf.org" <avt@ietf.org>
Thread-Topic: [AVT] Port mappings, NAT, and RAMS
Thread-Index: AQHJ9kFvGjDGuYw0C0iTG7mmhgtOKJBZFWOAgABPHYCAAA1zgIAABAAA//+h8NA=
Date: Fri, 26 Jun 2009 17:26:55 +0000
Message-ID: <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED0E98@tk5ex14mbxc105.redmond.corp.microsoft.com>
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <018901c9f638$7a286940$6e793bc0$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF04137758@FRVELSMBS22.ad2.ad.alcatel.com> <01af01c9f676$b970efd0$2c52cf70$%roni@huawei.com>
In-Reply-To: <01af01c9f676$b970efd0$2c52cf70$%roni@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 26 Jun 2009 17:31:17 -0000

I'm really straggling with why do we need to include port signaling as part=
 of this draft. The port can be signal dynamically or sent to client at sta=
rt up, and we can point out the different options to do so. Saying that, go=
ing to great level of details on this looks to me outside the scope of this=
 draft.
The port muxing gives the means to connect this protocol to the retransmiss=
ion one, and I think we should add that in order to clarify the usage of th=
is protocol.

Zeev

-----Original Message-----
From: Roni Even [mailto:Even.roni@huawei.com]
Sent: Friday, June 26, 2009 8:56 AM
To: 'VAN CAENEGEM Tom'; 'Bill Ver Steeg (versteb)'; Zeev Vax; 'Ali C. Begen=
 (abegen)'; avt@ietf.org
Subject: RE: [AVT] Port mappings, NAT, and RAMS

Tom,
So maybe, since it is the same architecture,  it is a good time to allow
RAMS-R to only signal retransmission.

Roni

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> VAN CAENEGEM Tom
> Sent: Friday, June 26, 2009 6:41 PM
> To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen
> (abegen); avt@ietf.org
> Subject: Re: [AVT] Port mappings, NAT, and RAMS
>
> Hi Roni,
>
> My perspective here is the one from real operator networks where
> operators are providing IPTV services making use of RTP, including
> multicast services. IPTV operators need to address packet loss, and one
> way to address this is by making use of RTP retransmissions. I lead the
> standardisation effort in DVB in 2007-2008, where we defined the RTP
> retransmission solution referring to rtcp-ssm draft, RFC 4585 (defining
> AVT-FB profile and RTCP FB message such as NACK) and RFC 4588
> (Retransmission), and also the RTP mux draft. Hence this
> architecture/solution is based on ssm, and the RTP receiver needs to
> send all its RTCP messges , including the RTCP NACK FB, to the feedback
> target. The feedback target is also here the same entity as the
> retransmission server. DVB has its own way of signaling parameters, but
> also here we were facing the fact that parameters are signaled to the
> receivers. The receivers do not/cannot signal towards the FT/RET server
> which ports they want. So we took a shortcut by allowing that the
> destination port of the RTP packet could be defined by the system (so
> quite exotic) OR when this port was not signaled, the RTP receiver knew
> that the RTP retransmission packet port matches the source port it used
> in the NACK messages. There have been some email exchanges from DVB
> with
> AVT when this work was conducted, but there was not that much
> interaction.
>
> RAMS is a solution that addresses a different topic, that is: how to
> shorten zapping response times. From a service need point of view,
> packet loss repair and minimising zapping times are quite separate
> topics: some operators may only be interested in achieving high image
> quality (relying on retransmissions), others may (also) want to offer
> smallest zapping response times without impact on quality (relying on
> RAMS messaging). Note also that a "retransmission service" and  -what
> is
> called in DVB-  "fast channel change service" impose quite different
> loads onto the networks, especially when these servers are localised
> deep in the network. So that may for instance be a reason why some IPTV
> service providers do not want "fast channel change" service, but do
> need
> retransmission service.  So, imposing to use "RAMS" for an IPTV service
> that provides retransmission(-only) support -to allow a standards way
> by
> which the receiver itself can select its ports- is quite absurd, and
> will not work.
>
> In short: the architecture for retransmissions-only and for "fast
> channel change" service are exactly the same, but RAMS as such has
> nothing to do with retransmission service, still faces the same problem
> of port signaling.
>
> Tom
>
>
>
>
> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: vrijdag 26 juni 2009 16:53
> To: VAN CAENEGEM Tom; 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C.
> Begen (abegen)'; avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
>
> Tom,
> I do not agree that we need a solution for SSM + retransmission not in
> the architecture of RAMS. Can you show me such a use and why not use
> RAMS.
> The assumption is that the first request for retransmission is going to
> the FT. If the request goes to the retransmission server, you can use
> RTP/RTCP multiplexing.
> Roni
>
> > -----Original Message-----
> > From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> > Sent: Friday, June 26, 2009 1:10 PM
> > To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen
> > (abegen); avt@ietf.org
> > Subject: RE: [AVT] Port mappings, NAT, and RAMS
> >
> > Roni,
> >
> > See inline
> >
> > -----Original Message-----
> > From: Roni Even [mailto:Even.roni@huawei.com]
> > Sent: vrijdag 26 juni 2009 11:34
> > To: VAN CAENEGEM Tom; 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C.
> > Begen (abegen)'; avt@ietf.org
> > Subject: RE: [AVT] Port mappings, NAT, and RAMS
> >
> > Tom,
> > What bothering me is that I do not want to make RTCP as a general
> > mechanism to provide addressing information.
> >
> > TOM: I understand
> >
> > I still do not see this a a general problem. The case you described
> > (SSM with retransmission), except for the RAMS case there is no other
> > application that requires that, it requires co-location of the FT and
> > retransmission source, you send the retransmission request to the
> > feedback target and not to the retransmission server.
> >
> > TOM: not sure I understand your exact point here. Do you agree that
> we
>
> > need a similar solution for SSM with retransmission (-only)  AND SSM
> > with RAMS (+ retransmission)?  In that case, it does not make sense
> to
>
> > specify ONLY a RAMS-R with the port information, you also need to do
> > that then for a NACK message. NACK is already defined, so that is why
> > I think that specifying a separate RTCP message is the way out here.
> > But because this is related to ssm and retransmission, it cannot be
> > done in this RAMS draft only. I do agree that such message can only
> be
>
> > used in the context of ssm with unicast feedback.
> >
> >
> > If this was a general problem it should be addressed in the context
> of
>
> > retransmission or SSM.
> >
> > Roni
> >
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
> > > Of VAN CAENEGEM Tom
> > > Sent: Friday, June 26, 2009 11:52 AM
> > > To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen
> > > (abegen); avt@ietf.org
> > > Subject: Re: [AVT] Port mappings, NAT, and RAMS
> > >
> > > Hi Roni,
> > >
> > > The problem I see here is that this is broader than RAMS: if an RTP
> > > receiver in an SSM session does not make use of RAMS, but wants to
> > > receive retransmissions, then integrating the "pub-port"
> > functionality
> >
> > > in the RAMS-R will not help here. That is why it makes most sense
> to
>
> > > define a dedicated RTCP "pub-port" message that can be combined
> with
>
> > > an RAMS-R or with a NACK.. Or with any other future RTCP request
> > > message that may be defined and relies on the same ssm with
> feedback
>
> > > target architecture..
> > > And I also think that we should consider a "default" case that when
> > an
> >
> > > RTP receiver does not signal its ports, the retransmission server
> > > understands the RTP receiver expects the retransmission/burst on
> the
>
> > > port, that was used by the RTP receiver as source port to request
> > > the retransmission and burst. But that should imply that the
> "pub-port"
> > > MUST
> > > always be sent in a single compound together with the NACK and/or
> > > the RAMS-R message (either of these) that triggers the
> > > retransmission session.
> > >
> > > Tom
> > >
> > >
> > > -----Original Message-----
> > > From: Roni Even [mailto:Even.roni@huawei.com]
> > > Sent: vrijdag 26 juni 2009 10:31
> > > To: 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C. Begen
> (abegen)';
>
> > > VAN CAENEGEM Tom; avt@ietf.org
> > > Subject: RE: Port mappings, NAT, and RAMS
> > >
> > > Hi Bill,
> > > I think I was the one who started this discussion but it looks to
> me
>
> > > like it is going too far since some of this work are not in the AVT
> > > charter.
> > >
> > > The RAMS solution is based on SSM and Retransmission and if there
> is
> > a
> >
> > > problem with NATs in these drafts it should be discussed there. My
> > > concern was different. The AVT solution is using SDP for specifying
> > > address information. In the case of both SSM and retransmission,
> the
>
> > > server can provide their address (which they may have obtained by
> > > using any method they
> > > chose) in the SDP. This works both for offer/answer and declarative
> > > SDP.
> > > I see no reason to address this topic in the RAMS draft
> > >
> > > The RAMS draft need to provide other addresses which are the RR RTP
> > > and RTCP receive addresses. In the case of offer answer this is
> > > clear by for declarative SDP the RR does not sent an SDP so cannot
> > > provide receive addresses.
> > >
> > >
> > > In the case of RFC 4588 the retransmission can be based on session
> > > or SSRC multiplexing and defines how to use SDP to provide the
> > addresses.
> > > The difference is that RFC 4588 do not address a unicast
> > > retransmission for a multicast stream which is the special case
> > > described here.  In the current case the SSRC multiplexing mode of
> > RFC
> >
> > > 4588 is not relevant so there MUST be a way for the RR to provide
> > > its receiving addresses to the RS.
> > >
> > > Since this solution do not work in offer/answer but is based on
> > > declarative SDP there need to be other way for the RR to provide
> the
>
> > > addressed
> > >
> > >
> > > My view based on the text above about SSM and RFC 4588 is that this
> > is
> >
> > > a special case and not a general case and this is why I suggested
> to
>
> > > add the address information to the RAMS-R message.
> > >
> > > Roni Even
> > >
> > >
> > > > -----Original Message-----
> > > > From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> > > > Sent: Wednesday, June 24, 2009 3:37 PM
> > > > To: Zeev Vax; Ali C. Begen (abegen); Roni Even; VANCAENEGEM Tom;
> > > > avt@ietf.org
> > > > Subject: Port mappings, NAT, and RAMS
> > > >
> > > >
> > > > There has been some discussion around the requirement for a NAT
> > > > section in the latest RAMS draft. This note is an attempt to
> > clarify
> >
> > > > the requirement to signal RAMS port mappings. Once we come to a
> > > > consensus as to the desired behavior, we can update the draft.
> > > >
> > > > This text refers to a ppt document that can be found at
> > > > ftp://ftpeng.cisco.com/abegen/PubPorts.pdf
> > > >
> > > > When using RAMS to accelerate acquisition of a multicast flow,
> > there
> >
> > > > are two sessions - the primary multicast session and the
> > > > acceleration session. These sessions may have multiple socket
> > > > contexts, depending on the use of RTP/RTP port muxing. However,
> > > > the primary multicast session and the retransmission session are
> > > > always
> > distinct.
> > > >
> > > > 1- The primary multicast session - two logical flows defined by
> > > > the Source address, Destination Multicast Address, RTP port (P1)
> > > > and RTCP port(P2). This set of flows is shown in RED in the
> diagram.
> > > > 2- The retransmission/acceleration session, shown in BLUE in the
> > > > diagram. In the most general non-port-muxed, non-NATed case, this
> > > > stream consists of 2 flows. The first (RTP) flow is defined by
> the
>
> > > > 5-tuple of UDP, IP address of the FT, RTP port configured by SDP
> > > (P3),
> > >
> > > > the IP address of the client and the RTP port dynamically chosen
> > > > by
> > > RR
> > >
> > > > (c3).
> > > > The second (RTCP) flow is defined by the 5-tuple of UDP, FT
> > address,
> >
> > > > the RTCP port defined by SDP (P4), the IP address of the client
> > > > and the RTCP port dynamically chosen by RR (c4). When RTP/RTCP
> > > > port
> > > muxing
> > >
> > > > is used, the retransmission session is collapsed onto a single
> > > > 5-tuple.
> > > >
> > > > Note that the feedback target for the primary session is P2 on
> > FT/RS.
> > > > Note that the acceleration burst must flow from FT P3/P4 to C
> > c3/c4.
> > > > In other words, the first desired data flow on the retransmission
> > > > session is "downstream".
> > > >
> > > > When we introduce NAT, we need to map c3 to c3' (and in the
> > > > absence
> > > of
> > >
> > > > port muxing, also c4 to c4') through the NAT device. This diagram
> > > > shows the use of STUN in YELLOW to setup the port mappings, but
> > > > other methods could be used.
> > > >
> > > >
> > > >
> > > > In summary, the ppt describes 4 options-
> > > >
> > > > Drawing 1 - No muxing - Stun request, bind for two ports and send
> > > > PubPorts with RAMS-R to signal both, followed by the burst.
> > > > Drawing 2 - Muxing - Stun request, bind for one port and send
> > > PubPorts
> > >
> > > > with RAMS-R to signal a single port, followed by the burst.
> > > > Drawing 3 - Muxing - No explicit STUN request/bind. Send PubPorts
> > > with
> > >
> > > > RAMS-R to signal RS to use the src port of the incoming RTCP
> > > > packet
> > > as
> > >
> > > > the destination for both RTP and RTCP in the ret session (We do
> > this
> >
> > > > by putting 0's in the pubports messages). Note that this does not
> > > work
> > >
> > > > through all NAT variants. The RAMS-R/PubPorts message is sent
> from
> > > > c4 to P2. The burst is sent from P4 to c4', and certain NATs will
> > > > not pass this traffic.
> > > > Drawing 4 - Muxing - No explicite STUN request/bind. Send
> PubPorts
>
> > > > from
> > > > c4 to P4, initializing NAT bindings. Send RAMS-R, followed by the
> > > > burst.
> > > > This works through all NAT types. There is concern about the
> > > > decoupling of the PubPorts from the RAMS-R, as dropped messages
> > > > may cause problems.
> > > >
> > > > Hopefully this note clarifies the need to signal the ports.
> > > >
> > > > Inputs on ths problem are desired. We need to decide if the
> > PubPorts
> >
> > > > is the right way to go, and if the transaction is RAMS specific
> or
>
> > > > is a generic RTP/RTCP message. Once we make that determination,
> we
>
> > > > need to lay out the details of the message format.
> > > >
> > > > Based on the feedback - we will abandon the idea, keep it in the
> > > > draft, or write a separate draft for it.
> > > >
> > > > Bill VerSteeg (with extensive input from Ali Begen and Dan Wing)
> > > >
> > > > -----Original Message-----
> > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> Behalf
>
> > > > Of Zeev Vax
> > > > Sent: Thursday, June 18, 2009 5:58 PM
> > > > To: Ali C. Begen (abegen); Roni Even; Bill Ver Steeg (versteb);
> > > > VANCAENEGEM Tom; avt@ietf.org
> > > > Subject: Re: [AVT] comments on
> > > > section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > > >
> > > > If we assume all entities are one, why would you need to signal
> > > > the retransmission port separately ?
> > > >
> > > > Zeev
> > >
> > > _______________________________________________
> > > Audio/Video Transport Working Group
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt



From Even.roni@huawei.com  Fri Jun 26 11:09:36 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 684133A6BC9 for <avt@core3.amsl.com>; Fri, 26 Jun 2009 11:09:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.625
X-Spam-Level: 
X-Spam-Status: No, score=-0.625 tagged_above=-999 required=5 tests=[AWL=-0.130, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 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 SG9k7ZM1Artr for <avt@core3.amsl.com>; Fri, 26 Jun 2009 11:09:33 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 200DF3A6BA8 for <avt@ietf.org>; Fri, 26 Jun 2009 11:09:33 -0700 (PDT)
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 <0KLU00H8XXZ2SP@szxga04-in.huawei.com> for avt@ietf.org; Sat, 27 Jun 2009 01:59:26 +0800 (CST)
Received: from huawei.com ([172.24.1.3]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLU003AOXZ2VZ@szxga04-in.huawei.com> for avt@ietf.org; Sat, 27 Jun 2009 01:59:26 +0800 (CST)
Received: from windows8d787f9 (bzq-79-182-68-39.red.bezeqint.net [79.182.68.39]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KLU0071XXYF17@szxml01-in.huawei.com>; Sat, 27 Jun 2009 01:59:26 +0800 (CST)
Date: Fri, 26 Jun 2009 20:58:48 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED0E98@tk5ex14mbxc105.redmond.corp.microsoft.com>
To: 'Zeev Vax' <zeevvax@microsoft.com>, 'VAN CAENEGEM Tom' <Tom.Van_Caenegem@alcatel-lucent.be>, "'Bill Ver Steeg (versteb)'" <versteb@cisco.com>, "'Ali C. Begen (abegen)'" <abegen@cisco.com>, avt@ietf.org
Message-id: <01b001c9f687$ccf05490$66d0fdb0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AQHJ9kFvGjDGuYw0C0iTG7mmhgtOKJBZFWOAgABPHYCAAA1zgIAABAAA//+h8NCAAAqRoA==
iPlanet-SMTP-Warning: Lines longer than SMTP allows found and truncated.
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <018901c9f638$7a286940$6e793bc0$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF04137758@FRVELSMBS22.ad2.ad.alcatel.com> <01af01c9f676$b970efd0$2c52cf70$%r@szxml01-in.huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED0E98@tk5ex14mbxc105.redmond.corp.microsoft.com>
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 26 Jun 2009 18:09:36 -0000

Zeev,
I assume you mean RTp/RTCP muxing. I am afraid it will not solve the problem
since the RAM-R is going to the FT while the RTP is coming from the burst
server using a different port. This will fail a symmetric NAT since the RTP
is not coming from the same IP/port to where the RAMS-R was sent
Roni

> -----Original Message-----
> From: Zeev Vax [mailto:zeevvax@microsoft.com]
> Sent: Friday, June 26, 2009 8:27 PM
> To: Roni Even; 'VAN CAENEGEM Tom'; 'Bill Ver Steeg (versteb)'; 'Ali C.
> Begen (abegen)'; avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
> 
> I'm really straggling with why do we need to include port signaling as
> part of this draft. The port can be signal dynamically or sent to
> client at start up, and we can point out the different options to do
> so. Saying that, going to great level of details on this looks to me
> outside the scope of this draft.
> The port muxing gives the means to connect this protocol to the
> retransmission one, and I think we should add that in order to clarify
> the usage of this protocol.
> 
> Zeev
> 
> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: Friday, June 26, 2009 8:56 AM
> To: 'VAN CAENEGEM Tom'; 'Bill Ver Steeg (versteb)'; Zeev Vax; 'Ali C.
> Begen (abegen)'; avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
> 
> Tom,
> So maybe, since it is the same architecture,  it is a good time to
> allow
> RAMS-R to only signal retransmission.
> 
> Roni
> 
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> > VAN CAENEGEM Tom
> > Sent: Friday, June 26, 2009 6:41 PM
> > To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen
> > (abegen); avt@ietf.org
> > Subject: Re: [AVT] Port mappings, NAT, and RAMS
> >
> > Hi Roni,
> >
> > My perspective here is the one from real operator networks where
> > operators are providing IPTV services making use of RTP, including
> > multicast services. IPTV operators need to address packet loss, and
> one
> > way to address this is by making use of RTP retransmissions. I lead
> the
> > standardisation effort in DVB in 2007-2008, where we defined the RTP
> > retransmission solution referring to rtcp-ssm draft, RFC 4585
> (defining
> > AVT-FB profile and RTCP FB message such as NACK) and RFC 4588
> > (Retransmission), and also the RTP mux draft. Hence this
> > architecture/solution is based on ssm, and the RTP receiver needs to
> > send all its RTCP messges , including the RTCP NACK FB, to the
> feedback
> > target. The feedback target is also here the same entity as the
> > retransmission server. DVB has its own way of signaling parameters,
> but
> > also here we were facing the fact that parameters are signaled to the
> > receivers. The receivers do not/cannot signal towards the FT/RET
> server
> > which ports they want. So we took a shortcut by allowing that the
> > destination port of the RTP packet could be defined by the system (so
> > quite exotic) OR when this port was not signaled, the RTP receiver
> knew
> > that the RTP retransmission packet port matches the source port it
> used
> > in the NACK messages. There have been some email exchanges from DVB
> > with
> > AVT when this work was conducted, but there was not that much
> > interaction.
> >
> > RAMS is a solution that addresses a different topic, that is: how to
> > shorten zapping response times. From a service need point of view,
> > packet loss repair and minimising zapping times are quite separate
> > topics: some operators may only be interested in achieving high image
> > quality (relying on retransmissions), others may (also) want to offer
> > smallest zapping response times without impact on quality (relying on
> > RAMS messaging). Note also that a "retransmission service" and  -what
> > is
> > called in DVB-  "fast channel change service" impose quite different
> > loads onto the networks, especially when these servers are localised
> > deep in the network. So that may for instance be a reason why some
> IPTV
> > service providers do not want "fast channel change" service, but do
> > need
> > retransmission service.  So, imposing to use "RAMS" for an IPTV
> service
> > that provides retransmission(-only) support -to allow a standards way
> > by
> > which the receiver itself can select its ports- is quite absurd, and
> > will not work.
> >
> > In short: the architecture for retransmissions-only and for "fast
> > channel change" service are exactly the same, but RAMS as such has
> > nothing to do with retransmission service, still faces the same
> problem
> > of port signaling.
> >
> > Tom
> >
> >
> >
> >
> > -----Original Message-----
> > From: Roni Even [mailto:Even.roni@huawei.com]
> > Sent: vrijdag 26 juni 2009 16:53
> > To: VAN CAENEGEM Tom; 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C.
> > Begen (abegen)'; avt@ietf.org
> > Subject: RE: [AVT] Port mappings, NAT, and RAMS
> >
> > Tom,
> > I do not agree that we need a solution for SSM + retransmission not
> in
> > the architecture of RAMS. Can you show me such a use and why not use
> > RAMS.
> > The assumption is that the first request for retransmission is going
> to
> > the FT. If the request goes to the retransmission server, you can use
> > RTP/RTCP multiplexing.
> > Roni
> >
> > > -----Original Message-----
> > > From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> > > Sent: Friday, June 26, 2009 1:10 PM
> > > To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen
> > > (abegen); avt@ietf.org
> > > Subject: RE: [AVT] Port mappings, NAT, and RAMS
> > >
> > > Roni,
> > >
> > > See inline
> > >
> > > -----Original Message-----
> > > From: Roni Even [mailto:Even.roni@huawei.com]
> > > Sent: vrijdag 26 juni 2009 11:34
> > > To: VAN CAENEGEM Tom; 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali
> C.
> > > Begen (abegen)'; avt@ietf.org
> > > Subject: RE: [AVT] Port mappings, NAT, and RAMS
> > >
> > > Tom,
> > > What bothering me is that I do not want to make RTCP as a general
> > > mechanism to provide addressing information.
> > >
> > > TOM: I understand
> > >
> > > I still do not see this a a general problem. The case you described
> > > (SSM with retransmission), except for the RAMS case there is no
> other
> > > application that requires that, it requires co-location of the FT
> and
> > > retransmission source, you send the retransmission request to the
> > > feedback target and not to the retransmission server.
> > >
> > > TOM: not sure I understand your exact point here. Do you agree that
> > we
> >
> > > need a similar solution for SSM with retransmission (-only)  AND
> SSM
> > > with RAMS (+ retransmission)?  In that case, it does not make sense
> > to
> >
> > > specify ONLY a RAMS-R with the port information, you also need to
> do
> > > that then for a NACK message. NACK is already defined, so that is
> why
> > > I think that specifying a separate RTCP message is the way out
> here.
> > > But because this is related to ssm and retransmission, it cannot be
> > > done in this RAMS draft only. I do agree that such message can only
> > be
> >
> > > used in the context of ssm with unicast feedback.
> > >
> > >
> > > If this was a general problem it should be addressed in the context
> > of
> >
> > > retransmission or SSM.
> > >
> > > Roni
> > >
> > >
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> Behalf
> > > > Of VAN CAENEGEM Tom
> > > > Sent: Friday, June 26, 2009 11:52 AM
> > > > To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen
> > > > (abegen); avt@ietf.org
> > > > Subject: Re: [AVT] Port mappings, NAT, and RAMS
> > > >
> > > > Hi Roni,
> > > >
> > > > The problem I see here is that this is broader than RAMS: if an
> RTP
> > > > receiver in an SSM session does not make use of RAMS, but wants
> to
> > > > receive retransmissions, then integrating the "pub-port"
> > > functionality
> > >
> > > > in the RAMS-R will not help here. That is why it makes most sense
> > to
> >
> > > > define a dedicated RTCP "pub-port" message that can be combined
> > with
> >
> > > > an RAMS-R or with a NACK.. Or with any other future RTCP request
> > > > message that may be defined and relies on the same ssm with
> > feedback
> >
> > > > target architecture..
> > > > And I also think that we should consider a "default" case that
> when
> > > an
> > >
> > > > RTP receiver does not signal its ports, the retransmission server
> > > > understands the RTP receiver expects the retransmission/burst on
> > the
> >
> > > > port, that was used by the RTP receiver as source port to request
> > > > the retransmission and burst. But that should imply that the
> > "pub-port"
> > > > MUST
> > > > always be sent in a single compound together with the NACK and/or
> > > > the RAMS-R message (either of these) that triggers the
> > > > retransmission session.
> > > >
> > > > Tom
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Roni Even [mailto:Even.roni@huawei.com]
> > > > Sent: vrijdag 26 juni 2009 10:31
> > > > To: 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C. Begen
> > (abegen)';
> >
> > > > VAN CAENEGEM Tom; avt@ietf.org
> > > > Subject: RE: Port mappings, NAT, and RAMS
> > > >
> > > > Hi Bill,
> > > > I think I was the one who started this discussion but it looks to
> > me
> >
> > > > like it is going too far since some of this work are not in the
> AVT
> > > > charter.
> > > >
> > > > The RAMS solution is based on SSM and Retransmission and if there
> > is
> > > a
> > >
> > > > problem with NATs in these drafts it should be discussed there.
> My
> > > > concern was different. The AVT solution is using SDP for
> specifying
> > > > address information. In the case of both SSM and retransmission,
> > the
> >
> > > > server can provide their address (which they may have obtained by
> > > > using any method they
> > > > chose) in the SDP. This works both for offer/answer and
> declarative
> > > > SDP.
> > > > I see no reason to address this topic in the RAMS draft
> > > >
> > > > The RAMS draft need to provide other addresses which are the RR
> RTP
> > > > and RTCP receive addresses. In the case of offer answer this is
> > > > clear by for declarative SDP the RR does not sent an SDP so
> cannot
> > > > provide receive addresses.
> > > >
> > > >
> > > > In the case of RFC 4588 the retransmission can be based on
> session
> > > > or SSRC multiplexing and defines how to use SDP to provide the
> > > addresses.
> > > > The difference is that RFC 4588 do not address a unicast
> > > > retransmission for a multicast stream which is the special case
> > > > described here.  In the current case the SSRC multiplexing mode
> of
> > > RFC
> > >
> > > > 4588 is not relevant so there MUST be a way for the RR to provide
> > > > its receiving addresses to the RS.
> > > >
> > > > Since this solution do not work in offer/answer but is based on
> > > > declarative SDP there need to be other way for the RR to provide
> > the
> >
> > > > addressed
> > > >
> > > >
> > > > My view based on the text above about SSM and RFC 4588 is that
> this
> > > is
> > >
> > > > a special case and not a general case and this is why I suggested
> > to
> >
> > > > add the address information to the RAMS-R message.
> > > >
> > > > Roni Even
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> > > > > Sent: Wednesday, June 24, 2009 3:37 PM
> > > > > To: Zeev Vax; Ali C. Begen (abegen); Roni Even; VANCAENEGEM
> Tom;
> > > > > avt@ietf.org
> > > > > Subject: Port mappings, NAT, and RAMS
> > > > >
> > > > >
> > > > > There has been some discussion around the requirement for a NAT
> > > > > section in the latest RAMS draft. This note is an attempt to
> > > clarify
> > >
> > > > > the requirement to signal RAMS port mappings. Once we come to a
> > > > > consensus as to the desired behavior, we can update the draft.
> > > > >
> > > > > This text refers to a ppt document that can be found at
> > > > > ftp://ftpeng.cisco.com/abegen/PubPorts.pdf
> > > > >
> > > > > When using RAMS to accelerate acquisition of a multicast flow,
> > > there
> > >
> > > > > are two sessions - the primary multicast session and the
> > > > > acceleration session. These sessions may have multiple socket
> > > > > contexts, depending on the use of RTP/RTP port muxing. However,
> > > > > the primary multicast session and the retransmission session
> are
> > > > > always
> > > distinct.
> > > > >
> > > > > 1- The primary multicast session - two logical flows defined by
> > > > > the Source address, Destination Multicast Address, RTP port
> (P1)
> > > > > and RTCP port(P2). This set of flows is shown in RED in the
> > diagram.
> > > > > 2- The retransmission/acceleration session, shown in BLUE in
> the
> > > > > diagram. In the most general non-port-muxed, non-NATed case,
> this
> > > > > stream consists of 2 flows. The first (RTP) flow is defined by
> > the
> >
> > > > > 5-tuple of UDP, IP address of the FT, RTP port configured by
> SDP
> > > > (P3),
> > > >
> > > > > the IP address of the client and the RTP port dynamically
> chosen
> > > > > by
> > > > RR
> > > >
> > > > > (c3).
> > > > > The second (RTCP) flow is defined by the 5-tuple of UDP, FT
> > > address,
> > >
> > > > > the RTCP port defined by SDP (P4), the IP address of the client
> > > > > and the RTCP port dynamically chosen by RR (c4). When RTP/RTCP
> > > > > port
> > > > muxing
> > > >
> > > > > is used, the retransmission session is collapsed onto a single
> > > > > 5-tuple.
> > > > >
> > > > > Note that the feedback target for the primary session is P2 on
> > > FT/RS.
> > > > > Note that the acceleration burst must flow from FT P3/P4 to C
> > > c3/c4.
> > > > > In other words, the first desired data flow on the
> retransmission
> > > > > session is "downstream".
> > > > >
> > > > > When we introduce NAT, we need to map c3 to c3' (and in the
> > > > > absence
> > > > of
> > > >
> > > > > port muxing, also c4 to c4') through the NAT device. This
> diagram
> > > > > shows the use of STUN in YELLOW to setup the port mappings, but
> > > > > other methods could be used.
> > > > >
> > > > >
> > > > >
> > > > > In summary, the ppt describes 4 options-
> > > > >
> > > > > Drawing 1 - No muxing - Stun request, bind for two ports and
> send
> > > > > PubPorts with RAMS-R to signal both, followed by the burst.
> > > > > Drawing 2 - Muxing - Stun request, bind for one port and send
> > > > PubPorts
> > > >
> > > > > with RAMS-R to signal a single port, followed by the burst.
> > > > > Drawing 3 - Muxing - No explicit STUN request/bind. Send
> PubPorts
> > > > with
> > > >
> > > > > RAMS-R to signal RS to use the src port of the incoming RTCP
> > > > > packet
> > > > as
> > > >
> > > > > the destination for both RTP and RTCP in the ret session (We do
> > > this
> > >
> > > > > by putting 0's in the pubports messages). Note that this does
> not
> > > > work
> > > >
> > > > > through all NAT variants. The RAMS-R/PubPorts message is sent
> > from
> > > > > c4 to P2. The burst is sent from P4 to c4', and certain NATs
> will
> > > > > not pass this traffic.
> > > > > Drawing 4 - Muxing - No explicite STUN request/bind. Send
> > PubPorts
> >
> > > > > from
> > > > > c4 to P4, initializing NAT bindings. Send RAMS-R, followed by
> the
> > > > > burst.
> > > > > This works through all NAT types. There is concern about the
> > > > > decoupling of the PubPorts from the RAMS-R, as dropped messages
> > > > > may cause problems.
> > > > >
> > > > > Hopefully this note clarifies the need to signal the ports.
> > > > >
> > > > > Inputs on ths problem are desired. We need to decide if the
> > > PubPorts
> > >
> > > > > is the right way to go, and if the transaction is RAMS specific
> > or
> >
> > > > > is a generic RTP/RTCP message. Once we make that determination,
> > we
> >
> > > > > need to lay out the details of the message format.
> > > > >
> > > > > Based on the feedback - we will abandon the idea, keep it in
> the
> > > > > draft, or write a separate draft for it.
> > > > >
> > > > > Bill VerSteeg (with extensive input from Ali Begen and Dan
> Wing)
> > > > >
> > > > > -----Original Message-----
> > > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > Behalf
> >
> > > > > Of Zeev Vax
> > > > > Sent: Thursday, June 18, 2009 5:58 PM
> > > > > To: Ali C. Begen (abegen); Roni Even; Bill Ver Steeg (versteb);
> > > > > VANCAENEGEM Tom; avt@ietf.org
> > > > > Subject: Re: [AVT] comments on
> > > > > section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > > > >
> > > > > If we assume all entities are one, why would you need to signal
> > > > > the retransmission port separately ?
> > > > >
> > > > > Zeev
> > > >
> > > > _______________________________________________
> > > > Audio/Video Transport Working Group
> > > > avt@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/avt
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt



From abegen@cisco.com  Fri Jun 26 11:34:13 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 DA3A73A6B00 for <avt@core3.amsl.com>; Fri, 26 Jun 2009 11:34:13 -0700 (PDT)
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=[AWL=0.000,  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 CvcDAB4FYy52 for <avt@core3.amsl.com>; Fri, 26 Jun 2009 11:34:11 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id B2E723A6AC0 for <avt@ietf.org>; Fri, 26 Jun 2009 11:33:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,297,1243814400"; d="scan'208";a="173237145"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-3.cisco.com with ESMTP; 26 Jun 2009 17:28:43 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n5QHShoo009237;  Fri, 26 Jun 2009 10:28:43 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id n5QHShJw027543; Fri, 26 Jun 2009 17:28:43 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 26 Jun 2009 10:28:43 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 26 Jun 2009 10:27:29 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D54099E014B@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <238382595265324EA50F6134BB42DCAF0408D9F6@FRVELSMBS22.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Some comments on " Multicast Acquisition Report Block Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-01)
Thread-Index: AcnxB+ZTSpmPIRTQTtqRFSxt0v9qZAAILfjQAIPOkFAA0hkMkA==
References: <238382595265324EA50F6134BB42DCAF0408CAE6@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D8C33@xmb-sjc-215.amer.cisco.com> <238382595265324EA50F6134BB42DCAF0408CFA0@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D540995C22C@xmb-sjc-215.amer.cisco.com> <63BA849C-3FC0-4733-A831-46ACE02FB348@cisco.com> <04CAD96D4C5A3D48B1919248A8FE0D540995C3DF@xmb-sjc-215.amer.cisco.com> <238382595265324EA50F6134BB42DCAF0408D9F6@FRVELSMBS22.ad2.ad.alcatel.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>, "Eric Friedrich (efriedri)" <efriedri@cisco.com>
X-OriginalArrivalTime: 26 Jun 2009 17:28:43.0399 (UTC) FILETIME=[8D9FF970:01C9F683]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=16485; t=1246037323; x=1246901323; c=relaxed/simple; s=sjdkim3002; 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]=20Some=20comments=20on=20=22=20Mu lticast=20Acquisition=20Report=20Block=20Typefor=20RTCP=20XR =22=20(draft-begen-avt-rapid-sync-rtcp-xr-01) |Sender:=20; bh=QY190zq2cYZ5B9o8VLkt8q3OG+Ry7E7yytos9EGwpgs=; b=OYQYAReHPx/jqWu+cIPGrGtCuang4aiMJFhI4glsZ9P8VGwmVJcgk4xbjp LsPwMG4wW+lvk023J3n8FW7hwRw+q7uOCxy6Y6lEpCOLH40osCfQdZiSdW9G mqtBop1IDE;
Authentication-Results: sj-dkim-3; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Cc: avt@ietf.org
Subject: Re: [AVT] Some comments on " Multicast Acquisition Report Block Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-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, 26 Jun 2009 18:34:13 -0000

Hi Tom,

I am concerned about introducing too much complexity into this XR =
report. I tend to agree to have a field that indicates the method used =
for the multicast join (simple join vs RAMS vs others) where we can have =
an IANA-maintained list.

However, the success/failure terminology seems to complicate things, so =
I believe we should refrain from interpreting anything at the reporting =
instant and let the monitoring agent interpret whatever the clients =
report. This keeps the client side simple and every client provides =
objective (not subjective) numbers even when they use different methods.

Of course, if very method-specific and/or vendor-specific information is =
desired, we have the appropriate extension mechanisms.=20

So, in summary, we should include the "Join time" and "first mcast =
seqnum" in all reports whenever possible. Specifically, if join was =
successful (so at least one mcast packet was received), these two fields =
MUST be included in the report. If join was not successful, these fields =
SHALL NOT exist. Everything else is optional.

-acbegen

> -----Original Message-----
> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> Sent: Monday, June 22, 2009 9:29 AM
> To: Ali C. Begen (abegen); Eric Friedrich (efriedri)
> Cc: avt@ietf.org
> Subject: RE: [AVT] Some comments on " Multicast Acquisition Report =
Block Typefor RTCP XR"
> (draft-begen-avt-rapid-sync-rtcp-xr-01)
>=20
> Ali,
>=20
> I think your proposal is +/- OK. However, I believe there is some room
> for improvement here. Suppose we have :
>=20
>=20
> - a dedicated  field X (3 bit is sufficient) "acquisition_method" with =
a
> code indicating which kind of acquisition process was initiated by the
> receiver (we can already define two codes in this draft : normal SFGMP
> process and RAMS process)
>=20
> E.g.
>=20
> X =3D001 =3D Normal MC Acquisition Process
> X =3D011 =3D RAMS-based MC Acquisition Process
>=20
> - a dedicated field Y indicating the MC acquisition "status code" . =
For
> normal acquisition process, only two codes can be defined (success or =
no
> success), and for the RAMS process, your proposal was to refer to =
codes
> defined in RAMS draft, but to me it makes more sense to (additionally)
> define a code that provides the success/non success from the receiver
> point of view. E.g. "success" code received by the receiver from the
> retransmission server in the RAMS-I does not mean the RAMS is a =
success.
> Note also that it would make sense to clearly make a distinction =
whether
> the RAMS was successful or not, and also whether the MC join =
-following
> and as part of the RAMS -was successful. It gives immediate insight by
> the retransmission server which part failed. We then can also define =
per
> code which fields must be present, for an RTP receiver supporting this
> kind of XR reports.
>=20
> E.g. the Y code for RAMS could be composed of two sub-fields
>=20
> -Subfield Y1 (2 bits):
>=20
> 00=3DRAMS unsuccessful, MC join unsuccessful
> 01=3DRAMS unsuccessful, MC join successful
> 11=3DRAMS successful, MC join successful
>=20
> What does 'RAMS successful (/unsuccessful)" mean here? This is not =
easy
> to answer, but I think it should represent the status from the point =
of
> view of the receiver, i.e. receiving a RAMS-I message with code
> "successful" is not sufficient (e.g. the RTP burst may not be =
delivered
> to the receiver, e.g. because of bad configuration of the NAPT). So,
> reception of the RTP data burst by the receiver as response on a
> RAMS-Request, looks like a better condition to call RAMS successful or
> not. As discussed in the RAMS draft, if RAMS-I or RAMS-T messages get
> dropped in between the receiver and the server, both server and =
receiver
> should be able to cope with that. However, if there is a gap between =
the
> burst and the MC, which was not closed despite retransmission
> (attempts), do we still call this a "successful" process from the
> receiver point of view? I tend to say "no", so.. "successful RAMS" =
would
> mean that the complete RAMS process -including the MC join- was
> succesful, resulting in the fact that all expected RTP data (unicast =
and
> multicast) was successfully and timely transferred by the RTP =
end-point
> to the application.  This makes of course the "10=3DRAMS successful, =
MC
> join unsuccessful" code obsolete.
>=20
>=20
> -Subfield Y2 (same size as defined in RAMS draft) containing the
> "Retransmission server response code"  Note that for the Y2 field, we
> also need to define a code, when there was no RAMS-I response from the
> server.
>=20
>=20
> With the definitions for subfield Y1 as per above, we can make a
> selection of which fields are to be provided mandatory by the RTP
> receiver
>=20
>=20
>=20
> E.g. for normal acquisition process (X=3D 001),
>=20
> Only if Y =3D 1, the following fields shall be present:
> -SN of 1st MC packet
> -delta time between 1st IGMP join and 1st received MC packet
> -(others?)
>=20
> E.g. for RAMS based acquisition process (X=3D 011):
>=20
> Y1 =3D 11  (Y2 code=3D "success") where expected fields must be :
>=20
> -SN of 1st MC packet
> -delta time between 1st RAMS-R and 1st received burst packet
> -delta time between 1st IGMP join and 1st received MC packet
> -(others?)
>=20
> Y1 =3D 01 (Y2 code =3D could be any code!)where expected fields must =
be :
>=20
> -SN of 1st MC packet
> -delta time between 1st RAMS-R and 1st received MC packet
> -delta time between 1st IGMP join and 1st received MC packet
> -(others?)
>=20
>=20
> Y1 =3D 00   (Y2 code =3D could be any code!): no fields are mandatory.
>=20
>=20
> What do you think?
>=20
> Regards
> Tom
>=20
>=20
> -----Original Message-----
> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> Sent: zaterdag 20 juni 2009 0:07
> To: Eric Friedrich (efriedri)
> Cc: VAN CAENEGEM Tom; avt@ietf.org
> Subject: RE: [AVT] Some comments on " Multicast Acquisition Report =
Block
> Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-01)
>=20
> Join time and first mcast seqnum would be common to all scenarios.
> However, what if that information is not available, meaning that the
> receiver could not join, i.e., could not receive anything at all from
> the multicast session? In that case, those fields should not exist.
> Using magical numbers is not a good idea.
>=20
> So, I suggest the following: If join was successful (so at least one
> mcast packet was received), these two fields MUST (not may or should) =
be
> included in the report. If join was not successful, these fields SHALL
> NOT exist.
>=20
> This should address Tom's concerns except that this report will not =
say
> much whether acceleration was requested or not (or if yes, which =
method
> was requested). I think we can use one of the status codes (we have =
256
> of them anyway) to indicate this. Or, we can separate a block to
> indicate the individual acceleration methods.
>=20
> How does this sound?
>=20
> -acbegen
>=20
> > -----Original Message-----
> > From: Eric Friedrich (efriedri)
> > Sent: Friday, June 19, 2009 11:01 AM
> > To: Ali C. Begen (abegen)
> > Cc: VAN CAENEGEM Tom; avt@ietf.org
> > Subject: Re: [AVT] Some comments on " Multicast Acquisition Report
> Block Typefor RTCP XR"
> > (draft-begen-avt-rapid-sync-rtcp-xr-01)
> >
> > Ali, Tom-
> >    I think it would be useful to provide some small base set of =
fields
>=20
> > that are required for any MA report. They should be fields that do =
not
>=20
> > require any special instrumentation on the RTP Receiver and apply to
> > RAMS and non-RAMS acquisitions. Looking over our proposed fields, =
I'd
> > like to suggest that "First Multicast Extended Seq Number" and =
"SFGMP
> > Join Time" be required fields. They would provide a small but useful
> > amount of information in cases where receivers do not support the
> > other fields.
> >
> > Thanks,
> > Eric
> >
> > On Jun 19, 2009, at 1:43 PM, Ali C. Begen (abegen) wrote:
> >
> > > Hi Tom,
> > >
> > > I just feel that mandating some fields but not requiring the
> > > receivers to fill them in is not a good solution. As I mentioned
> > > earlier, I'd prefer using a stronger language than "optional" but =
I
> > > prefer not to mandate such fields.
> > >
> > > Any other opinions?
> > >
> > > -acbegen
> > >
> > >> -----Original Message-----
> > >> From: VAN CAENEGEM Tom =
[mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> > >> Sent: Friday, June 19, 2009 3:40 AM
> > >> To: Ali C. Begen (abegen); avt@ietf.org
> > >> Subject: RE: [AVT] Some comments on " Multicast Acquisition =
Report
> > >> Block Typefor RTCP XR"
> > >> (draft-begen-avt-rapid-sync-rtcp-xr-01)
> > >>
> > >> Hi Ali,
> > >>
> > >> Look for "TOM" ...
> > >>
> > >> -----Original Message-----
> > >> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> > >> Sent: donderdag 18 juni 2009 17:34
> > >> To: VAN CAENEGEM Tom; avt@ietf.org
> > >> Subject: RE: [AVT] Some comments on " Multicast Acquisition =
Report
> > >> Block Typefor RTCP XR" (draft-begen-avt-rapid-sync-rtcp-xr-01)
> > >>
> > >> Hi Tom,
> > >>
> > >> Thanks for reading the draft.
> > >>
> > >>> -----Original Message-----
> > >>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On =
Behalf
>=20
> > >>> Of VAN CAENEGEM Tom
> > >>> Sent: Thursday, June 18, 2009 7:17 AM
> > >>> To: avt@ietf.org
> > >>> Subject: [AVT] Some comments on " Multicast Acquisition Report
> > >>> Block
> > >> Typefor RTCP XR"
> > >>> (draft-begen-avt-rapid-sync-rtcp-xr-01)
> > >>>
> > >>> Hi Ali,
> > >>>
> > >>> I have a few comments/questions related to the draft:
> > >>>
> > >>> Comment 1:  The abstract now has a sentence: "For quality
> > >>> reporting, monitoring and diagnostics purposes, it is important =
to
>=20
> > >>> collect detailed information from the RTP receivers about their
> > >>> acquisition
> > >> experiences."  Doesn't it go beyond "RTP (receivers)"
> > >>> and "acquisition" as you also define e.g. a TLV related to
> > >>> presentation time delay (sometimes the MC RTP delivered content
> > >>> may
> > >> not even be displayed) and application delay.
> > >>> I have no problem with the definition of such fields, but IMO it
> > >>> makes
> > >>
> > >>> sense to make this clear in the abstract.
> > >>
> > >> I am not sure what else I can use instead of "RTP receivers" as I
> > >> don't wanna specifically say decoders, set-tops, etc. Instead of
> > >> "acquisition experiences", maybe we can call it "acquisition and
> > >> presentation experiences"?
> > >>
> > >> Would that help?
> > >>
> > >> "TOM" : OK
> > >>
> > >>> Comment 2: Base Report
> > >>>
> > >>> The only informational field here is "response". It is still not
> > >>> defined, but you refer to the response code in RAMS draft (e.g.
> > >> "success", etc).
> > >>
> > >> I believe using the same codes will make it more useful.
> > >>
> > >> "TOM" : OK, but most codes only apply to a rapid acquisition
> > >> process, so it makes sense to indicate additionally whether
> > >> "normal" or "rapid"
> > >> acquisition was initiated by the receiver (that is an additional
> > >> flag)
> > >>
> > >>> I guess it is not possible to signal to an RR which additional
> > >>> info to
> > >>
> > >>> send, i.e which TLV fields to use...From that point of view, =
would
>=20
> > >>> it not make sense to have some basic information -now defined in
> > >>> some TLV
> > >>
> > >>> fields in the base report- that is always present, to
> > >>
> > >> By always present, you mean "mandatory"? If yes, we indeed need =
to
> > >> decide which ones.
> > >>
> > >> "TOM" : indeed mandatory : when by means of declarative SDP, the
> > >> RTP receivers are instructed to send RTCP XR with multicast
> > >> acquisition report blocks, AND RTP recievers support these XR
> > >> messages, these fields are always there.
> > >>
> > >>> enhance interoperability. I know we need to find the right =
balance
>=20
> > >>> between useful information reporting ,  bandwidth efficiency, =
and
> > >> receiver reporting capabilities.
> > >>>
> > >>> Candidate fields that could be inside this fixed base report =
are:
> > >>> -flag/field indicating whether the report refers to a normal
> > >>> acquisition (based on SFGMP) or rapid MC RTP acquisition (or
> > >>> rather the intention by the RR to perform  a rapid
> > >>> acquisition) for instance by means of RAMS
> > >>
> > >> One reason behind this base report vs extensions separation was =
to
> > >> be able to handle other rapid multicast acquisition methods. So,
> > >> IMO, if we will have to make something mandatory, it should not
> > >> relate to a specific method. It is true that I am heavily
> > >> considering RAMS in designing this report, but it just works for
> > >> other methods, if they become interested in supporting this =
report.
> > >>
> > >> Will this flag/field be able to specify which method was used? Or
> > >> will it simply specify whether it was a rapid or normal
> > >> acquisition?
> > >>
> > >> "TOM" : for a 1-bit flag, that should be the latter : normal or
> > >> rapid (in whatever way). Alternatively considering a multiple bit
> > >> field (e.g.
> > >> 3 bits) where e.g. 001 =3D normal aquisition, 002 =3D RAMS, and =
all
> > >> other codes unspecified at this stage looks to me a good solution
> > >> as well...
> > >>
> > >>> -a response code which you have indeed defined and its
> > >>> interpretation should be dependent on the previously mentioned
> > >>> flag/field
> > >>
> > >> So, the flag/field above will indeed specify which method was use
> > >> to make RR rapidly acquire the content. Yes/no?
> > >>
> > >> "TOM" : see above
> > >>
> > >>
> > >>> -initial launched request (either 1st RAMS-R for rapid
> > >>> acquisition, either 1st IGMP-join in case of normal acquisition)
> > >>> to 1st received RTP packet (always a multicast packet for normal
> > >>> acquisition and "normally" a burst packet when a rapid =
acquisition
>=20
> > >>> process was
> > >>> involved) delta time
> > >>>
> > >>> -application request to initial launched request (either 1st
> > >>> RAMS-R for rapid acquisition, either 1st IGMP-join in case of
> > >>> normal
> > >>> acquisition) delta time
> > >>>
> > >>> For these last two fields, a value must be specified that would
> > >>> indicate that the field is not filled out (because the receiver
> > >>> client
> > >> implementation may not support it).
> > >>
> > >> Oh, then these fields are not mandatory since the client has the
> > >> option to leave them blank. Then, I would recommend leaving the
> > >> current report as it is, but we can use a stronger language (like
> > >> "SHOULD/
> > >> RECOMMENDED")
> > >> for some of the fields (like the ones you have above) to promote
> > >> interoperability.
> > >>
> > >> Would you be OK with that?
> > >>
> > >> "TOM" : the reason to have the field in the base report, is to =
make
>=20
> > >> sure that a minimum of information is conveyed back to the
> > >> server/feedback target. Otherwise, as all TLV fields are =
optional,
> > >> how can a server indicate to a client which TLV fields it is
> > >> interested in and which ones not?  The proposed fields I
> > >> selected/defined are those that provide useful information  for
> > >> both a normal and RAMS process, but there may be
> > >> other fields equally appropriate to be always present.   Whether =
we
> > >> need
> > >> an RTP receiver to mandate to fill out these fields (with the =
right
> > >> value) is a separate discussion, IMO.
> > >>
> > >>> There could still be other fields that apply to both acquisition
> > >>> processes and fit in the base report, but they should be
> > >>> application independent (e.g. delta to presentation time is
> > >>> clearly app
> > >>> dependent)
> > >>
> > >> Agree, application dependent fields are optional and should stay
> so.
> > >>
> > >> T,
> > >> -acbegen
> > >>
> > >>>
> > >>> Regards
> > >>> Tom
> > >
> > > _______________________________________________
> > > Audio/Video Transport Working Group
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt


From zeevvax@microsoft.com  Fri Jun 26 11:52:26 2009
Return-Path: <zeevvax@microsoft.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 0F18528C12A for <avt@core3.amsl.com>; Fri, 26 Jun 2009 11:52:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 wm83kcivCsM5 for <avt@core3.amsl.com>; Fri, 26 Jun 2009 11:52:24 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id E7EB828C122 for <avt@ietf.org>; Fri, 26 Jun 2009 11:52:23 -0700 (PDT)
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.99.4; Fri, 26 Jun 2009 11:51:25 -0700
Received: from tk5ex14mbxc105.redmond.corp.microsoft.com ([157.54.79.177]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi; Fri, 26 Jun 2009 11:51:25 -0700
From: Zeev Vax <zeevvax@microsoft.com>
To: Roni Even <Even.roni@huawei.com>, 'VAN CAENEGEM Tom' <Tom.Van_Caenegem@alcatel-lucent.be>, "'Bill Ver Steeg (versteb)'" <versteb@cisco.com>, "'Ali C. Begen (abegen)'" <abegen@cisco.com>, "avt@ietf.org" <avt@ietf.org>
Thread-Topic: [AVT] Port mappings, NAT, and RAMS
Thread-Index: AQHJ9kFvGjDGuYw0C0iTG7mmhgtOKJBZFWOAgABPHYCAAA1zgIAABAAA//+h8NCAAAqRoIAADycQ
Date: Fri, 26 Jun 2009 18:51:22 +0000
Message-ID: <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED1081@tk5ex14mbxc105.redmond.corp.microsoft.com>
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <018901c9f638$7a286940$6e793bc0$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF04137758@FRVELSMBS22.ad2.ad.alcatel.com> <01af01c9f676$b970efd0$2c52cf70$%r@szxml01-in.huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED0E98@tk5ex14mbxc105.redmond.corp.microsoft.com> <01b001c9f687$ccf05490$66d0fdb0$%roni@huawei.com>
In-Reply-To: <01b001c9f687$ccf05490$66d0fdb0$%roni@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 26 Jun 2009 18:52:26 -0000

my understanding is that port muxing can solve both problems, if we assume =
retransmission server and burst server are running on one physical server. =
For RTP RTCP muxing, the most logical is to use the RTCP port to send the R=
TP traffic, any other way looks to me like unnecessary overhead.

AT this point given the amount of emails we exchange on the subject, I sugg=
est we set a conf call to discuss the issue.

Zeev

-----Original Message-----
From: Roni Even [mailto:Even.roni@huawei.com]
Sent: Friday, June 26, 2009 10:59 AM
To: Zeev Vax; 'VAN CAENEGEM Tom'; 'Bill Ver Steeg (versteb)'; 'Ali C. Begen=
 (abegen)'; avt@ietf.org
Subject: RE: [AVT] Port mappings, NAT, and RAMS

Zeev,
I assume you mean RTp/RTCP muxing. I am afraid it will not solve the proble=
m
since the RAM-R is going to the FT while the RTP is coming from the burst
server using a different port. This will fail a symmetric NAT since the RTP
is not coming from the same IP/port to where the RAMS-R was sent
Roni

> -----Original Message-----
> From: Zeev Vax [mailto:zeevvax@microsoft.com]
> Sent: Friday, June 26, 2009 8:27 PM
> To: Roni Even; 'VAN CAENEGEM Tom'; 'Bill Ver Steeg (versteb)'; 'Ali C.
> Begen (abegen)'; avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
>
> I'm really straggling with why do we need to include port signaling as
> part of this draft. The port can be signal dynamically or sent to
> client at start up, and we can point out the different options to do
> so. Saying that, going to great level of details on this looks to me
> outside the scope of this draft.
> The port muxing gives the means to connect this protocol to the
> retransmission one, and I think we should add that in order to clarify
> the usage of this protocol.
>
> Zeev
>
> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: Friday, June 26, 2009 8:56 AM
> To: 'VAN CAENEGEM Tom'; 'Bill Ver Steeg (versteb)'; Zeev Vax; 'Ali C.
> Begen (abegen)'; avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
>
> Tom,
> So maybe, since it is the same architecture,  it is a good time to
> allow
> RAMS-R to only signal retransmission.
>
> Roni
>
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> > VAN CAENEGEM Tom
> > Sent: Friday, June 26, 2009 6:41 PM
> > To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen
> > (abegen); avt@ietf.org
> > Subject: Re: [AVT] Port mappings, NAT, and RAMS
> >
> > Hi Roni,
> >
> > My perspective here is the one from real operator networks where
> > operators are providing IPTV services making use of RTP, including
> > multicast services. IPTV operators need to address packet loss, and
> one
> > way to address this is by making use of RTP retransmissions. I lead
> the
> > standardisation effort in DVB in 2007-2008, where we defined the RTP
> > retransmission solution referring to rtcp-ssm draft, RFC 4585
> (defining
> > AVT-FB profile and RTCP FB message such as NACK) and RFC 4588
> > (Retransmission), and also the RTP mux draft. Hence this
> > architecture/solution is based on ssm, and the RTP receiver needs to
> > send all its RTCP messges , including the RTCP NACK FB, to the
> feedback
> > target. The feedback target is also here the same entity as the
> > retransmission server. DVB has its own way of signaling parameters,
> but
> > also here we were facing the fact that parameters are signaled to the
> > receivers. The receivers do not/cannot signal towards the FT/RET
> server
> > which ports they want. So we took a shortcut by allowing that the
> > destination port of the RTP packet could be defined by the system (so
> > quite exotic) OR when this port was not signaled, the RTP receiver
> knew
> > that the RTP retransmission packet port matches the source port it
> used
> > in the NACK messages. There have been some email exchanges from DVB
> > with
> > AVT when this work was conducted, but there was not that much
> > interaction.
> >
> > RAMS is a solution that addresses a different topic, that is: how to
> > shorten zapping response times. From a service need point of view,
> > packet loss repair and minimising zapping times are quite separate
> > topics: some operators may only be interested in achieving high image
> > quality (relying on retransmissions), others may (also) want to offer
> > smallest zapping response times without impact on quality (relying on
> > RAMS messaging). Note also that a "retransmission service" and  -what
> > is
> > called in DVB-  "fast channel change service" impose quite different
> > loads onto the networks, especially when these servers are localised
> > deep in the network. So that may for instance be a reason why some
> IPTV
> > service providers do not want "fast channel change" service, but do
> > need
> > retransmission service.  So, imposing to use "RAMS" for an IPTV
> service
> > that provides retransmission(-only) support -to allow a standards way
> > by
> > which the receiver itself can select its ports- is quite absurd, and
> > will not work.
> >
> > In short: the architecture for retransmissions-only and for "fast
> > channel change" service are exactly the same, but RAMS as such has
> > nothing to do with retransmission service, still faces the same
> problem
> > of port signaling.
> >
> > Tom
> >
> >
> >
> >
> > -----Original Message-----
> > From: Roni Even [mailto:Even.roni@huawei.com]
> > Sent: vrijdag 26 juni 2009 16:53
> > To: VAN CAENEGEM Tom; 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C.
> > Begen (abegen)'; avt@ietf.org
> > Subject: RE: [AVT] Port mappings, NAT, and RAMS
> >
> > Tom,
> > I do not agree that we need a solution for SSM + retransmission not
> in
> > the architecture of RAMS. Can you show me such a use and why not use
> > RAMS.
> > The assumption is that the first request for retransmission is going
> to
> > the FT. If the request goes to the retransmission server, you can use
> > RTP/RTCP multiplexing.
> > Roni
> >
> > > -----Original Message-----
> > > From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> > > Sent: Friday, June 26, 2009 1:10 PM
> > > To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen
> > > (abegen); avt@ietf.org
> > > Subject: RE: [AVT] Port mappings, NAT, and RAMS
> > >
> > > Roni,
> > >
> > > See inline
> > >
> > > -----Original Message-----
> > > From: Roni Even [mailto:Even.roni@huawei.com]
> > > Sent: vrijdag 26 juni 2009 11:34
> > > To: VAN CAENEGEM Tom; 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali
> C.
> > > Begen (abegen)'; avt@ietf.org
> > > Subject: RE: [AVT] Port mappings, NAT, and RAMS
> > >
> > > Tom,
> > > What bothering me is that I do not want to make RTCP as a general
> > > mechanism to provide addressing information.
> > >
> > > TOM: I understand
> > >
> > > I still do not see this a a general problem. The case you described
> > > (SSM with retransmission), except for the RAMS case there is no
> other
> > > application that requires that, it requires co-location of the FT
> and
> > > retransmission source, you send the retransmission request to the
> > > feedback target and not to the retransmission server.
> > >
> > > TOM: not sure I understand your exact point here. Do you agree that
> > we
> >
> > > need a similar solution for SSM with retransmission (-only)  AND
> SSM
> > > with RAMS (+ retransmission)?  In that case, it does not make sense
> > to
> >
> > > specify ONLY a RAMS-R with the port information, you also need to
> do
> > > that then for a NACK message. NACK is already defined, so that is
> why
> > > I think that specifying a separate RTCP message is the way out
> here.
> > > But because this is related to ssm and retransmission, it cannot be
> > > done in this RAMS draft only. I do agree that such message can only
> > be
> >
> > > used in the context of ssm with unicast feedback.
> > >
> > >
> > > If this was a general problem it should be addressed in the context
> > of
> >
> > > retransmission or SSM.
> > >
> > > Roni
> > >
> > >
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> Behalf
> > > > Of VAN CAENEGEM Tom
> > > > Sent: Friday, June 26, 2009 11:52 AM
> > > > To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen
> > > > (abegen); avt@ietf.org
> > > > Subject: Re: [AVT] Port mappings, NAT, and RAMS
> > > >
> > > > Hi Roni,
> > > >
> > > > The problem I see here is that this is broader than RAMS: if an
> RTP
> > > > receiver in an SSM session does not make use of RAMS, but wants
> to
> > > > receive retransmissions, then integrating the "pub-port"
> > > functionality
> > >
> > > > in the RAMS-R will not help here. That is why it makes most sense
> > to
> >
> > > > define a dedicated RTCP "pub-port" message that can be combined
> > with
> >
> > > > an RAMS-R or with a NACK.. Or with any other future RTCP request
> > > > message that may be defined and relies on the same ssm with
> > feedback
> >
> > > > target architecture..
> > > > And I also think that we should consider a "default" case that
> when
> > > an
> > >
> > > > RTP receiver does not signal its ports, the retransmission server
> > > > understands the RTP receiver expects the retransmission/burst on
> > the
> >
> > > > port, that was used by the RTP receiver as source port to request
> > > > the retransmission and burst. But that should imply that the
> > "pub-port"
> > > > MUST
> > > > always be sent in a single compound together with the NACK and/or
> > > > the RAMS-R message (either of these) that triggers the
> > > > retransmission session.
> > > >
> > > > Tom
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Roni Even [mailto:Even.roni@huawei.com]
> > > > Sent: vrijdag 26 juni 2009 10:31
> > > > To: 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C. Begen
> > (abegen)';
> >
> > > > VAN CAENEGEM Tom; avt@ietf.org
> > > > Subject: RE: Port mappings, NAT, and RAMS
> > > >
> > > > Hi Bill,
> > > > I think I was the one who started this discussion but it looks to
> > me
> >
> > > > like it is going too far since some of this work are not in the
> AVT
> > > > charter.
> > > >
> > > > The RAMS solution is based on SSM and Retransmission and if there
> > is
> > > a
> > >
> > > > problem with NATs in these drafts it should be discussed there.
> My
> > > > concern was different. The AVT solution is using SDP for
> specifying
> > > > address information. In the case of both SSM and retransmission,
> > the
> >
> > > > server can provide their address (which they may have obtained by
> > > > using any method they
> > > > chose) in the SDP. This works both for offer/answer and
> declarative
> > > > SDP.
> > > > I see no reason to address this topic in the RAMS draft
> > > >
> > > > The RAMS draft need to provide other addresses which are the RR
> RTP
> > > > and RTCP receive addresses. In the case of offer answer this is
> > > > clear by for declarative SDP the RR does not sent an SDP so
> cannot
> > > > provide receive addresses.
> > > >
> > > >
> > > > In the case of RFC 4588 the retransmission can be based on
> session
> > > > or SSRC multiplexing and defines how to use SDP to provide the
> > > addresses.
> > > > The difference is that RFC 4588 do not address a unicast
> > > > retransmission for a multicast stream which is the special case
> > > > described here.  In the current case the SSRC multiplexing mode
> of
> > > RFC
> > >
> > > > 4588 is not relevant so there MUST be a way for the RR to provide
> > > > its receiving addresses to the RS.
> > > >
> > > > Since this solution do not work in offer/answer but is based on
> > > > declarative SDP there need to be other way for the RR to provide
> > the
> >
> > > > addressed
> > > >
> > > >
> > > > My view based on the text above about SSM and RFC 4588 is that
> this
> > > is
> > >
> > > > a special case and not a general case and this is why I suggested
> > to
> >
> > > > add the address information to the RAMS-R message.
> > > >
> > > > Roni Even
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> > > > > Sent: Wednesday, June 24, 2009 3:37 PM
> > > > > To: Zeev Vax; Ali C. Begen (abegen); Roni Even; VANCAENEGEM
> Tom;
> > > > > avt@ietf.org
> > > > > Subject: Port mappings, NAT, and RAMS
> > > > >
> > > > >
> > > > > There has been some discussion around the requirement for a NAT
> > > > > section in the latest RAMS draft. This note is an attempt to
> > > clarify
> > >
> > > > > the requirement to signal RAMS port mappings. Once we come to a
> > > > > consensus as to the desired behavior, we can update the draft.
> > > > >
> > > > > This text refers to a ppt document that can be found at
> > > > > ftp://ftpeng.cisco.com/abegen/PubPorts.pdf
> > > > >
> > > > > When using RAMS to accelerate acquisition of a multicast flow,
> > > there
> > >
> > > > > are two sessions - the primary multicast session and the
> > > > > acceleration session. These sessions may have multiple socket
> > > > > contexts, depending on the use of RTP/RTP port muxing. However,
> > > > > the primary multicast session and the retransmission session
> are
> > > > > always
> > > distinct.
> > > > >
> > > > > 1- The primary multicast session - two logical flows defined by
> > > > > the Source address, Destination Multicast Address, RTP port
> (P1)
> > > > > and RTCP port(P2). This set of flows is shown in RED in the
> > diagram.
> > > > > 2- The retransmission/acceleration session, shown in BLUE in
> the
> > > > > diagram. In the most general non-port-muxed, non-NATed case,
> this
> > > > > stream consists of 2 flows. The first (RTP) flow is defined by
> > the
> >
> > > > > 5-tuple of UDP, IP address of the FT, RTP port configured by
> SDP
> > > > (P3),
> > > >
> > > > > the IP address of the client and the RTP port dynamically
> chosen
> > > > > by
> > > > RR
> > > >
> > > > > (c3).
> > > > > The second (RTCP) flow is defined by the 5-tuple of UDP, FT
> > > address,
> > >
> > > > > the RTCP port defined by SDP (P4), the IP address of the client
> > > > > and the RTCP port dynamically chosen by RR (c4). When RTP/RTCP
> > > > > port
> > > > muxing
> > > >
> > > > > is used, the retransmission session is collapsed onto a single
> > > > > 5-tuple.
> > > > >
> > > > > Note that the feedback target for the primary session is P2 on
> > > FT/RS.
> > > > > Note that the acceleration burst must flow from FT P3/P4 to C
> > > c3/c4.
> > > > > In other words, the first desired data flow on the
> retransmission
> > > > > session is "downstream".
> > > > >
> > > > > When we introduce NAT, we need to map c3 to c3' (and in the
> > > > > absence
> > > > of
> > > >
> > > > > port muxing, also c4 to c4') through the NAT device. This
> diagram
> > > > > shows the use of STUN in YELLOW to setup the port mappings, but
> > > > > other methods could be used.
> > > > >
> > > > >
> > > > >
> > > > > In summary, the ppt describes 4 options-
> > > > >
> > > > > Drawing 1 - No muxing - Stun request, bind for two ports and
> send
> > > > > PubPorts with RAMS-R to signal both, followed by the burst.
> > > > > Drawing 2 - Muxing - Stun request, bind for one port and send
> > > > PubPorts
> > > >
> > > > > with RAMS-R to signal a single port, followed by the burst.
> > > > > Drawing 3 - Muxing - No explicit STUN request/bind. Send
> PubPorts
> > > > with
> > > >
> > > > > RAMS-R to signal RS to use the src port of the incoming RTCP
> > > > > packet
> > > > as
> > > >
> > > > > the destination for both RTP and RTCP in the ret session (We do
> > > this
> > >
> > > > > by putting 0's in the pubports messages). Note that this does
> not
> > > > work
> > > >
> > > > > through all NAT variants. The RAMS-R/PubPorts message is sent
> > from
> > > > > c4 to P2. The burst is sent from P4 to c4', and certain NATs
> will
> > > > > not pass this traffic.
> > > > > Drawing 4 - Muxing - No explicite STUN request/bind. Send
> > PubPorts
> >
> > > > > from
> > > > > c4 to P4, initializing NAT bindings. Send RAMS-R, followed by
> the
> > > > > burst.
> > > > > This works through all NAT types. There is concern about the
> > > > > decoupling of the PubPorts from the RAMS-R, as dropped messages
> > > > > may cause problems.
> > > > >
> > > > > Hopefully this note clarifies the need to signal the ports.
> > > > >
> > > > > Inputs on ths problem are desired. We need to decide if the
> > > PubPorts
> > >
> > > > > is the right way to go, and if the transaction is RAMS specific
> > or
> >
> > > > > is a generic RTP/RTCP message. Once we make that determination,
> > we
> >
> > > > > need to lay out the details of the message format.
> > > > >
> > > > > Based on the feedback - we will abandon the idea, keep it in
> the
> > > > > draft, or write a separate draft for it.
> > > > >
> > > > > Bill VerSteeg (with extensive input from Ali Begen and Dan
> Wing)
> > > > >
> > > > > -----Original Message-----
> > > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> > Behalf
> >
> > > > > Of Zeev Vax
> > > > > Sent: Thursday, June 18, 2009 5:58 PM
> > > > > To: Ali C. Begen (abegen); Roni Even; Bill Ver Steeg (versteb);
> > > > > VANCAENEGEM Tom; avt@ietf.org
> > > > > Subject: Re: [AVT] comments on
> > > > > section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > > > >
> > > > > If we assume all entities are one, why would you need to signal
> > > > > the retransmission port separately ?
> > > > >
> > > > > Zeev
> > > >
> > > > _______________________________________________
> > > > Audio/Video Transport Working Group
> > > > avt@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/avt
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt




From Tom.Van_Caenegem@alcatel-lucent.be  Fri Jun 26 12:07:51 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 8A6EA3A6977 for <avt@core3.amsl.com>; Fri, 26 Jun 2009 12:07:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.885
X-Spam-Level: 
X-Spam-Status: No, score=-5.885 tagged_above=-999 required=5 tests=[AWL=0.364,  BAYES_00=-2.599, HELO_EQ_FR=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 8RJVraYwvHse for <avt@core3.amsl.com>; Fri, 26 Jun 2009 12:07:49 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id C5B473A6AAE for <avt@ietf.org>; Fri, 26 Jun 2009 12:07:48 -0700 (PDT)
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 n5QIUGOG031529;  Fri, 26 Jun 2009 20:30:16 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.51]) by FRVELSBHS04.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 26 Jun 2009 20:30:16 +0200
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: Fri, 26 Jun 2009 20:30:15 +0200
Message-ID: <238382595265324EA50F6134BB42DCAF04137BAB@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <01af01c9f676$b970efd0$2c52cf70$%roni@huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Port mappings, NAT, and RAMS
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDgARoKBSAAW0fO0AABD/mgAAGLzyAAALbj8AAKyqEwAABC2oAAAel2MAAEvUOQ
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <018901c9f638$7a286940$6e793bc0$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF04137758@FRVELSMBS22.ad2.ad.alcatel.com> <01af01c9f676$b970efd0$2c! 52cf70$%r oni@huawei.com>
From: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>
To: "Roni Even" <Even.roni@huawei.com>, "Bill Ver Steeg (versteb)" <versteb@cisco.com>, "Zeev Vax" <zeevvax@microsoft.com>, "Ali C. Begen (abegen)" <abegen@cisco.com>, <avt@ietf.org>
X-OriginalArrivalTime: 26 Jun 2009 18:30:16.0438 (UTC) FILETIME=[26D90160:01C9F68C]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 26 Jun 2009 19:07:51 -0000

Roni,

I am puzzled again. Are you suggesting that we use the RAMS-R message
also as a means to signal to the retransmission server that the RTP
receiver will only send NACKs? I do not get that way of thinking.
What the RAMS draft is about is defining the RAMS messages for rapid MC
acquisition. The architecture as such is not a new item. You can combine
rtcp-ssm and RFC 4585, RFC 4588, and there it is, the architecture.. In
the RAMS draft we only have imposed some constraints saying for instance
that the FT must be the same as the retransmission server (similar as in
DVB by the way). The additional port signaling we need that we are
discussing about now could be done by SDP negotiation or by means of
RTSP. But because of time constraints this is not a good solution,
regardless whether this is retransmission only, or retransmission and
rapid acquisition combined.=20

I can only repeat myself: IF we define a port signaling means it must be
applicable both to retransmission-only (no RAMS messages are involved,
only NACKs) and to rapid acquisition (what the RAMS draft is about).
Hence, the RAMS-R message must be decoupled from the port signaling, and
even stronger:  the solution should be defined in a separate draft.

Tom=20
=20

-----Original Message-----
From: Roni Even [mailto:Even.roni@huawei.com]=20
Sent: vrijdag 26 juni 2009 17:56
To: VAN CAENEGEM Tom; 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C.
Begen (abegen)'; avt@ietf.org
Subject: RE: [AVT] Port mappings, NAT, and RAMS

Tom,
So maybe, since it is the same architecture,  it is a good time to allow
RAMS-R to only signal retransmission. =20

Roni

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of=20
> VAN CAENEGEM Tom
> Sent: Friday, June 26, 2009 6:41 PM
> To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen=20
> (abegen); avt@ietf.org
> Subject: Re: [AVT] Port mappings, NAT, and RAMS
>=20
> Hi Roni,
>=20
> My perspective here is the one from real operator networks where=20
> operators are providing IPTV services making use of RTP, including=20
> multicast services. IPTV operators need to address packet loss, and=20
> one way to address this is by making use of RTP retransmissions. I=20
> lead the standardisation effort in DVB in 2007-2008, where we defined=20
> the RTP retransmission solution referring to rtcp-ssm draft, RFC 4585=20
> (defining AVT-FB profile and RTCP FB message such as NACK) and RFC=20
> 4588 (Retransmission), and also the RTP mux draft. Hence this=20
> architecture/solution is based on ssm, and the RTP receiver needs to=20
> send all its RTCP messges , including the RTCP NACK FB, to the=20
> feedback target. The feedback target is also here the same entity as=20
> the retransmission server. DVB has its own way of signaling=20
> parameters, but also here we were facing the fact that parameters are=20
> signaled to the receivers. The receivers do not/cannot signal towards=20
> the FT/RET server which ports they want. So we took a shortcut by=20
> allowing that the destination port of the RTP packet could be defined=20
> by the system (so quite exotic) OR when this port was not signaled,=20
> the RTP receiver knew that the RTP retransmission packet port matches=20
> the source port it used in the NACK messages. There have been some=20
> email exchanges from DVB with AVT when this work was conducted, but=20
> there was not that much interaction.
>=20
> RAMS is a solution that addresses a different topic, that is: how to=20
> shorten zapping response times. From a service need point of view,=20
> packet loss repair and minimising zapping times are quite separate
> topics: some operators may only be interested in achieving high image=20
> quality (relying on retransmissions), others may (also) want to offer=20
> smallest zapping response times without impact on quality (relying on=20
> RAMS messaging). Note also that a "retransmission service" and  -what=20
> is called in DVB-  "fast channel change service" impose quite=20
> different loads onto the networks, especially when these servers are=20
> localised deep in the network. So that may for instance be a reason=20
> why some IPTV service providers do not want "fast channel change"=20
> service, but do need retransmission service.  So, imposing to use=20
> "RAMS" for an IPTV service that provides retransmission(-only) support

> -to allow a standards way by which the receiver itself can select its=20
> ports- is quite absurd, and will not work.
>=20
> In short: the architecture for retransmissions-only and for "fast=20
> channel change" service are exactly the same, but RAMS as such has=20
> nothing to do with retransmission service, still faces the same=20
> problem of port signaling.
>=20
> Tom
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: vrijdag 26 juni 2009 16:53
> To: VAN CAENEGEM Tom; 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C.
> Begen (abegen)'; avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
>=20
> Tom,
> I do not agree that we need a solution for SSM + retransmission not in

> the architecture of RAMS. Can you show me such a use and why not use=20
> RAMS.
> The assumption is that the first request for retransmission is going=20
> to the FT. If the request goes to the retransmission server, you can=20
> use RTP/RTCP multiplexing.
> Roni
>=20
> > -----Original Message-----
> > From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> > Sent: Friday, June 26, 2009 1:10 PM
> > To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen=20
> > (abegen); avt@ietf.org
> > Subject: RE: [AVT] Port mappings, NAT, and RAMS
> >
> > Roni,
> >
> > See inline
> >
> > -----Original Message-----
> > From: Roni Even [mailto:Even.roni@huawei.com]
> > Sent: vrijdag 26 juni 2009 11:34
> > To: VAN CAENEGEM Tom; 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali
C.
> > Begen (abegen)'; avt@ietf.org
> > Subject: RE: [AVT] Port mappings, NAT, and RAMS
> >
> > Tom,
> > What bothering me is that I do not want to make RTCP as a general=20
> > mechanism to provide addressing information.
> >
> > TOM: I understand
> >
> > I still do not see this a a general problem. The case you described=20
> > (SSM with retransmission), except for the RAMS case there is no=20
> > other application that requires that, it requires co-location of the

> > FT and retransmission source, you send the retransmission request to

> > the feedback target and not to the retransmission server.
> >
> > TOM: not sure I understand your exact point here. Do you agree that
> we
>=20
> > need a similar solution for SSM with retransmission (-only)  AND SSM

> > with RAMS (+ retransmission)?  In that case, it does not make sense
> to
>=20
> > specify ONLY a RAMS-R with the port information, you also need to do

> > that then for a NACK message. NACK is already defined, so that is=20
> > why I think that specifying a separate RTCP message is the way out
here.
> > But because this is related to ssm and retransmission, it cannot be=20
> > done in this RAMS draft only. I do agree that such message can only
> be
>=20
> > used in the context of ssm with unicast feedback.
> >
> >
> > If this was a general problem it should be addressed in the context
> of
>=20
> > retransmission or SSM.
> >
> > Roni
> >
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf

> > > Of VAN CAENEGEM Tom
> > > Sent: Friday, June 26, 2009 11:52 AM
> > > To: Roni Even; Bill Ver Steeg (versteb); Zeev Vax; Ali C. Begen=20
> > > (abegen); avt@ietf.org
> > > Subject: Re: [AVT] Port mappings, NAT, and RAMS
> > >
> > > Hi Roni,
> > >
> > > The problem I see here is that this is broader than RAMS: if an=20
> > > RTP receiver in an SSM session does not make use of RAMS, but=20
> > > wants to receive retransmissions, then integrating the "pub-port"
> > functionality
> >
> > > in the RAMS-R will not help here. That is why it makes most sense
> to
>=20
> > > define a dedicated RTCP "pub-port" message that can be combined
> with
>=20
> > > an RAMS-R or with a NACK.. Or with any other future RTCP request=20
> > > message that may be defined and relies on the same ssm with
> feedback
>=20
> > > target architecture..
> > > And I also think that we should consider a "default" case that=20
> > > when
> > an
> >
> > > RTP receiver does not signal its ports, the retransmission server=20
> > > understands the RTP receiver expects the retransmission/burst on
> the
>=20
> > > port, that was used by the RTP receiver as source port to request=20
> > > the retransmission and burst. But that should imply that the
> "pub-port"
> > > MUST
> > > always be sent in a single compound together with the NACK and/or=20
> > > the RAMS-R message (either of these) that triggers the=20
> > > retransmission session.
> > >
> > > Tom
> > >
> > >
> > > -----Original Message-----
> > > From: Roni Even [mailto:Even.roni@huawei.com]
> > > Sent: vrijdag 26 juni 2009 10:31
> > > To: 'Bill Ver Steeg (versteb)'; 'Zeev Vax'; 'Ali C. Begen
> (abegen)';
>=20
> > > VAN CAENEGEM Tom; avt@ietf.org
> > > Subject: RE: Port mappings, NAT, and RAMS
> > >
> > > Hi Bill,
> > > I think I was the one who started this discussion but it looks to
> me
>=20
> > > like it is going too far since some of this work are not in the=20
> > > AVT charter.
> > >
> > > The RAMS solution is based on SSM and Retransmission and if there
> is
> > a
> >
> > > problem with NATs in these drafts it should be discussed there. My

> > > concern was different. The AVT solution is using SDP for=20
> > > specifying address information. In the case of both SSM and=20
> > > retransmission,
> the
>=20
> > > server can provide their address (which they may have obtained by=20
> > > using any method they
> > > chose) in the SDP. This works both for offer/answer and=20
> > > declarative SDP.
> > > I see no reason to address this topic in the RAMS draft
> > >
> > > The RAMS draft need to provide other addresses which are the RR=20
> > > RTP and RTCP receive addresses. In the case of offer answer this=20
> > > is clear by for declarative SDP the RR does not sent an SDP so=20
> > > cannot provide receive addresses.
> > >
> > >
> > > In the case of RFC 4588 the retransmission can be based on session

> > > or SSRC multiplexing and defines how to use SDP to provide the
> > addresses.
> > > The difference is that RFC 4588 do not address a unicast=20
> > > retransmission for a multicast stream which is the special case=20
> > > described here.  In the current case the SSRC multiplexing mode of
> > RFC
> >
> > > 4588 is not relevant so there MUST be a way for the RR to provide=20
> > > its receiving addresses to the RS.
> > >
> > > Since this solution do not work in offer/answer but is based on=20
> > > declarative SDP there need to be other way for the RR to provide
> the
>=20
> > > addressed
> > >
> > >
> > > My view based on the text above about SSM and RFC 4588 is that=20
> > > this
> > is
> >
> > > a special case and not a general case and this is why I suggested
> to
>=20
> > > add the address information to the RAMS-R message.
> > >
> > > Roni Even
> > >
> > >
> > > > -----Original Message-----
> > > > From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> > > > Sent: Wednesday, June 24, 2009 3:37 PM
> > > > To: Zeev Vax; Ali C. Begen (abegen); Roni Even; VANCAENEGEM Tom;

> > > > avt@ietf.org
> > > > Subject: Port mappings, NAT, and RAMS
> > > >
> > > >
> > > > There has been some discussion around the requirement for a NAT=20
> > > > section in the latest RAMS draft. This note is an attempt to
> > clarify
> >
> > > > the requirement to signal RAMS port mappings. Once we come to a=20
> > > > consensus as to the desired behavior, we can update the draft.
> > > >
> > > > This text refers to a ppt document that can be found at=20
> > > > ftp://ftpeng.cisco.com/abegen/PubPorts.pdf
> > > >
> > > > When using RAMS to accelerate acquisition of a multicast flow,
> > there
> >
> > > > are two sessions - the primary multicast session and the=20
> > > > acceleration session. These sessions may have multiple socket=20
> > > > contexts, depending on the use of RTP/RTP port muxing. However,=20
> > > > the primary multicast session and the retransmission session are

> > > > always
> > distinct.
> > > >
> > > > 1- The primary multicast session - two logical flows defined by=20
> > > > the Source address, Destination Multicast Address, RTP port (P1)

> > > > and RTCP port(P2). This set of flows is shown in RED in the
> diagram.
> > > > 2- The retransmission/acceleration session, shown in BLUE in the

> > > > diagram. In the most general non-port-muxed, non-NATed case,=20
> > > > this stream consists of 2 flows. The first (RTP) flow is defined

> > > > by
> the
>=20
> > > > 5-tuple of UDP, IP address of the FT, RTP port configured by SDP
> > > (P3),
> > >
> > > > the IP address of the client and the RTP port dynamically chosen

> > > > by
> > > RR
> > >
> > > > (c3).
> > > > The second (RTCP) flow is defined by the 5-tuple of UDP, FT
> > address,
> >
> > > > the RTCP port defined by SDP (P4), the IP address of the client=20
> > > > and the RTCP port dynamically chosen by RR (c4). When RTP/RTCP=20
> > > > port
> > > muxing
> > >
> > > > is used, the retransmission session is collapsed onto a single=20
> > > > 5-tuple.
> > > >
> > > > Note that the feedback target for the primary session is P2 on
> > FT/RS.
> > > > Note that the acceleration burst must flow from FT P3/P4 to C
> > c3/c4.
> > > > In other words, the first desired data flow on the=20
> > > > retransmission session is "downstream".
> > > >
> > > > When we introduce NAT, we need to map c3 to c3' (and in the=20
> > > > absence
> > > of
> > >
> > > > port muxing, also c4 to c4') through the NAT device. This=20
> > > > diagram shows the use of STUN in YELLOW to setup the port=20
> > > > mappings, but other methods could be used.
> > > >
> > > >
> > > >
> > > > In summary, the ppt describes 4 options-
> > > >
> > > > Drawing 1 - No muxing - Stun request, bind for two ports and=20
> > > > send PubPorts with RAMS-R to signal both, followed by the burst.
> > > > Drawing 2 - Muxing - Stun request, bind for one port and send
> > > PubPorts
> > >
> > > > with RAMS-R to signal a single port, followed by the burst.
> > > > Drawing 3 - Muxing - No explicit STUN request/bind. Send=20
> > > > PubPorts
> > > with
> > >
> > > > RAMS-R to signal RS to use the src port of the incoming RTCP=20
> > > > packet
> > > as
> > >
> > > > the destination for both RTP and RTCP in the ret session (We do
> > this
> >
> > > > by putting 0's in the pubports messages). Note that this does=20
> > > > not
> > > work
> > >
> > > > through all NAT variants. The RAMS-R/PubPorts message is sent
> from
> > > > c4 to P2. The burst is sent from P4 to c4', and certain NATs=20
> > > > will not pass this traffic.
> > > > Drawing 4 - Muxing - No explicite STUN request/bind. Send
> PubPorts
>=20
> > > > from
> > > > c4 to P4, initializing NAT bindings. Send RAMS-R, followed by=20
> > > > the burst.
> > > > This works through all NAT types. There is concern about the=20
> > > > decoupling of the PubPorts from the RAMS-R, as dropped messages=20
> > > > may cause problems.
> > > >
> > > > Hopefully this note clarifies the need to signal the ports.
> > > >
> > > > Inputs on ths problem are desired. We need to decide if the
> > PubPorts
> >
> > > > is the right way to go, and if the transaction is RAMS specific
> or
>=20
> > > > is a generic RTP/RTCP message. Once we make that determination,
> we
>=20
> > > > need to lay out the details of the message format.
> > > >
> > > > Based on the feedback - we will abandon the idea, keep it in the

> > > > draft, or write a separate draft for it.
> > > >
> > > > Bill VerSteeg (with extensive input from Ali Begen and Dan Wing)
> > > >
> > > > -----Original Message-----
> > > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On
> Behalf
>=20
> > > > Of Zeev Vax
> > > > Sent: Thursday, June 18, 2009 5:58 PM
> > > > To: Ali C. Begen (abegen); Roni Even; Bill Ver Steeg (versteb);=20
> > > > VANCAENEGEM Tom; avt@ietf.org
> > > > Subject: Re: [AVT] comments on
> > > > section10ofdraft-ietf-avt-rapid-acquisition-for-rtp-01
> > > >
> > > > If we assume all entities are one, why would you need to signal=20
> > > > the retransmission port separately ?
> > > >
> > > > Zeev
> > >
> > > _______________________________________________
> > > Audio/Video Transport Working Group avt@ietf.org=20
> > > https://www.ietf.org/mailman/listinfo/avt
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From Tom.Van_Caenegem@alcatel-lucent.be  Mon Jun 29 09:18:01 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 F41E73A6E03 for <avt@core3.amsl.com>; Mon, 29 Jun 2009 09:18:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.916
X-Spam-Level: 
X-Spam-Status: No, score=-5.916 tagged_above=-999 required=5 tests=[AWL=0.333,  BAYES_00=-2.599, HELO_EQ_FR=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 zhv+2fYYDRxm for <avt@core3.amsl.com>; Mon, 29 Jun 2009 09:17:59 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [62.23.212.57]) by core3.amsl.com (Postfix) with ESMTP id 6401B3A6E05 for <avt@ietf.org>; Mon, 29 Jun 2009 09:17:59 -0700 (PDT)
Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.dc-m.alcatel-lucent.com [155.132.6.76]) by smail2.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5TGHU3a008430;  Mon, 29 Jun 2009 18:17:30 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.53]) by FRVELSBHS04.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 29 Jun 2009 18:17:30 +0200
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: Mon, 29 Jun 2009 18:17:29 +0200
Message-ID: <238382595265324EA50F6134BB42DCAF04186C7F@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D54099E00C4@xmb-sjc-215.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Port mappings, NAT, and RAMS
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDgARoKBSAALhpHsAAKg7ngAAPu9/AALWBagACY+iig
References: <mailman.10085.1245185397.4936.avt@ietf.org><238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com><015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com><238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com><04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com><81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com><3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com><025401c9effa$34040170$9c0c0450$%roni@huawei.com><3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com><04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04137224@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54099DFD1A@xmb-sjc-215.amer.cisco.com> <2383825952653! ! 24EA50F 6134BB42DCAF 04137762@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54099E00C4@xmb-sjc-215.amer.cisco.com>
From: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>
To: "Ali C. Begen (abegen)" <abegen@cisco.com>, "Bill Ver Steeg (versteb)" <versteb@cisco.com>, "Zeev Vax" <zeevvax@microsoft.com>, "Roni Even" <Even.roni@huawei.com>,  <avt@ietf.org>
X-OriginalArrivalTime: 29 Jun 2009 16:17:30.0476 (UTC) FILETIME=[1A00EAC0:01C9F8D5]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.80
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 29 Jun 2009 16:18:01 -0000

 Ali,

See some comments below (TOM).

-----Original Message-----
From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]=20
Sent: vrijdag 26 juni 2009 17:41
To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni Even;
avt@ietf.org
Subject: RE: Port mappings, NAT, and RAMS

Hi Tom,

[snip]
> The reason why we need pubports is that it indicates "explicitly" the=20
> port the client wants to use to receive the burst is the port it used=20
> to send the RAMS-R/pubports message. I believe we need this explicit=20
> indication, ow, we will be making an implicit assumption. Note that=20
> the rams-r/pubports is in the primary session and burst/ret packets=20
> are in the retransmission session, which is different than the
primary.
>=20
> As far as I can see, not everybody agrees on this point, but we need=20
> to make a decision here before we mandate anything.
>=20
> TOM: I agree with your last line, but I do not completely agree when=20
> you mention "implicit" assumption, especially for option 3, where=20
> RAMS-R (or
> NACK) and the Pub-port message are in the same compound message. If we

> "define" that if no pub-report message is sent by the RR, the=20
> information towards the Retransmission server is exactly the same as=20
> when an RTP receiver sends an RTCP compound message made up of an RTCP

> NACK/RAMS-R together with a pub-port message where the ports are
"zero"

We "may" be able to say it from RAMS-R but not for NACK since we are not
defining it, we will be overloading its meaning, IMO. And as you/Bill
pointed out in other emails, I also believe that this is more general
problem than just RAMS. We need something like pubports for NACKs as
well.


TOM: indeed, that is why IMO we should define this problem and solution
in a separate draft which applies to any system architecture where a
unicast session from a FT is coupled to a ssm session with that same FT.


> -as currently proposed in the RAMS draft now.  I agree that this is=20
> not true for option 4, where pub-port and RAMS-R or NACK are separate=20
> messages, but I do not favour the solution of option 4 for the same=20
> reason you mention in your reply (a new failure mode). So, if option 4

> is -for that reason- no longer considered, I do not see a problem with

> defining this rule/clause as expressed above. In other words, there is

> no need for a pub-report message in this scenario and this results NOT

> in an "assumption" what-so-ever.
>=20
>=20
> > supports RTP/RTCP muxing itself, and if it knows the RS supports=20
> > RTP/RTCP muxing too (as indicated in the declarative sdp received by

> > the
> > RR)
> >
> > -Don't we also allow that for option 3, the port P2 actually equals=20
> > port P4? This is a kind of hybrid of session and SSRC multiplexing=20
> > of the primary multicast RTP stream and the=20
> > retransmission/acceleration session
> > :  on the unidirectional RTP layer, the primary MC packets and the=20
> > unicast retransmission packets are clearly session muxed, but the=20
> > RTCP
>=20
> > "return" channel for both streams have exactly the same transport=20
> > addresses, but are distinguished by means of a different SSRC.  In=20
> > that
>=20
> How? Since SSM and retransmission sessions are session muxed, they=20
> have the same SSRC. When a client is sending a receiver report, how do

> we identify which session it belongs to? So, I believe P2 should be=20
> different than P4.
>=20
> TOM: you are right. But notice this: RFC 4588 mandates that when=20
> session muxing is used for retransmission, than the SSRC should be the
same.
> However the RFC 4588 does not give arguments why it needs to be like=20
> that. So I ask you: what would or can happen if there is a different=20
> SSRC used?  If there are no convincing arguments why we must stick to

Good question. If we don't use the same SSRC in session-muxed RTP
sessions, it will introduce correlation problems. Receiver/XR reports
coming from a larger number of receivers will be difficult to identify
and match at the server side. There will be SSRC collisions, which will
complicate things further.

TOM: the big difference with when the RFC 4588 was being discussed and
developed, is that now we are capable of advertising in SDP the SSRC of
the media server, that is in this case the retransmission server SSRC
used in the retransmission session. In fact for RAMS, we need to define
the SSRC of the ssm RTP session, so we can as well do it for the
retransmission session. Perhaps we should consider this different SSRC
possibility (hence violating RFC 4588) as part of a new draft, the one I
mentioned above.


> the same SSRC, then, if we have a good use case to depart from that=20
> "rule" -and the use case we are discussing here is IMO indeed a valid=20
> use case- I do not see why we should be limited by such a "rule". The=20
> "valid" use case is here that RAMS and Retransmission for SSM sessions

> operates fine through any NAPT and without any dedicated RTCP message.

-acbegen

From abegen@cisco.com  Tue Jun 30 00:18:21 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 E74F528C339 for <avt@core3.amsl.com>; Tue, 30 Jun 2009 00:18:21 -0700 (PDT)
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 ANvuvOi5Mh9Y for <avt@core3.amsl.com>; Tue, 30 Jun 2009 00:18:20 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 31BA028C338 for <avt@ietf.org>; Tue, 30 Jun 2009 00:18:20 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,315,1243814400"; d="scan'208";a="334516110"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 30 Jun 2009 07:18:37 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n5U7Ibqv014502;  Tue, 30 Jun 2009 00:18:37 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n5U7IbPV011813; Tue, 30 Jun 2009 07:18:37 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 30 Jun 2009 00:18:36 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 30 Jun 2009 00:18:31 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D5409A71F22@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <238382595265324EA50F6134BB42DCAF04186C7F@FRVELSMBS22.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Port mappings, NAT, and RAMS
Thread-Index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDgARoKBSAALhpHsAAKg7ngAAPu9/AALWBagACY+iigAB/UF7A=
References: <mailman.10085.1245185397.4936.avt@ietf.org><238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com><015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com><238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com><04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com><81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com><3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com><025401c9effa$34040170$9c0c0450$%roni@huawei.com><3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com><04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04137224@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54099DFD1A@xmb-sjc-215.amer.cisco.com> <2383825952653! ! 24EA5 0F6134BB42DC AF04137762@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54099E00C4@xmb-sjc-215.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04186C7F@FRVELSMBS22.ad2.ad.alcatel.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.be>, "Bill Ver Steeg (versteb)" <versteb@cisco.com>, "Zeev Vax" <zeevvax@microsoft.com>, "Roni Even" <Even.roni@huawei.com>,  <avt@ietf.org>
X-OriginalArrivalTime: 30 Jun 2009 07:18:36.0775 (UTC) FILETIME=[FC076F70:01C9F952]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5864; t=1246346317; x=1247210317; c=relaxed/simple; s=sjdkim3002; 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=20Port=20mappings,=20NAT,=20and=20RAMS |Sender:=20; bh=A7wNcgS1KCUNhATowyHC1pPXuxysbIjoMrmBjcFmVj4=; b=CBg0tpMFqCPPgtyXtpDcSi1Wul8fnqYaC3RoWFkja/EjuHnIbAuEbsByhR NjjCFGlamN9uvfEpeGBrfj353b2/3K4yz85FSXl2xhQOc2OHetnIh3bxBvnw T7q3xZcZGz;
Authentication-Results: sj-dkim-3; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 30 Jun 2009 07:18:22 -0000

Hi Tom,

Let's get the input from the WG on these points. I believe going for a =
more general solution that will be applicable to both RAMS and NACK is =
more desirable.

BR,
-acbegen



> -----Original Message-----
> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> Sent: Monday, June 29, 2009 9:17 AM
> To: Ali C. Begen (abegen); Bill Ver Steeg (versteb); Zeev Vax; Roni =
Even; avt@ietf.org
> Subject: RE: Port mappings, NAT, and RAMS
>=20
>=20
>  Ali,
>=20
> See some comments below (TOM).
>=20
> -----Original Message-----
> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> Sent: vrijdag 26 juni 2009 17:41
> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni Even;
> avt@ietf.org
> Subject: RE: Port mappings, NAT, and RAMS
>=20
> Hi Tom,
>=20
> [snip]
> > The reason why we need pubports is that it indicates "explicitly" =
the
> > port the client wants to use to receive the burst is the port it =
used
> > to send the RAMS-R/pubports message. I believe we need this explicit
> > indication, ow, we will be making an implicit assumption. Note that
> > the rams-r/pubports is in the primary session and burst/ret packets
> > are in the retransmission session, which is different than the
> primary.
> >
> > As far as I can see, not everybody agrees on this point, but we need
> > to make a decision here before we mandate anything.
> >
> > TOM: I agree with your last line, but I do not completely agree when
> > you mention "implicit" assumption, especially for option 3, where
> > RAMS-R (or
> > NACK) and the Pub-port message are in the same compound message. If =
we
>=20
> > "define" that if no pub-report message is sent by the RR, the
> > information towards the Retransmission server is exactly the same as
> > when an RTP receiver sends an RTCP compound message made up of an =
RTCP
>=20
> > NACK/RAMS-R together with a pub-port message where the ports are
> "zero"
>=20
> We "may" be able to say it from RAMS-R but not for NACK since we are =
not
> defining it, we will be overloading its meaning, IMO. And as you/Bill
> pointed out in other emails, I also believe that this is more general
> problem than just RAMS. We need something like pubports for NACKs as
> well.
>=20
>=20
> TOM: indeed, that is why IMO we should define this problem and =
solution
> in a separate draft which applies to any system architecture where a
> unicast session from a FT is coupled to a ssm session with that same =
FT.
>=20
>=20
> > -as currently proposed in the RAMS draft now.  I agree that this is
> > not true for option 4, where pub-port and RAMS-R or NACK are =
separate
> > messages, but I do not favour the solution of option 4 for the same
> > reason you mention in your reply (a new failure mode). So, if option =
4
>=20
> > is -for that reason- no longer considered, I do not see a problem =
with
>=20
> > defining this rule/clause as expressed above. In other words, there =
is
>=20
> > no need for a pub-report message in this scenario and this results =
NOT
>=20
> > in an "assumption" what-so-ever.
> >
> >
> > > supports RTP/RTCP muxing itself, and if it knows the RS supports
> > > RTP/RTCP muxing too (as indicated in the declarative sdp received =
by
>=20
> > > the
> > > RR)
> > >
> > > -Don't we also allow that for option 3, the port P2 actually =
equals
> > > port P4? This is a kind of hybrid of session and SSRC multiplexing
> > > of the primary multicast RTP stream and the
> > > retransmission/acceleration session
> > > :  on the unidirectional RTP layer, the primary MC packets and the
> > > unicast retransmission packets are clearly session muxed, but the
> > > RTCP
> >
> > > "return" channel for both streams have exactly the same transport
> > > addresses, but are distinguished by means of a different SSRC.  In
> > > that
> >
> > How? Since SSM and retransmission sessions are session muxed, they
> > have the same SSRC. When a client is sending a receiver report, how =
do
>=20
> > we identify which session it belongs to? So, I believe P2 should be
> > different than P4.
> >
> > TOM: you are right. But notice this: RFC 4588 mandates that when
> > session muxing is used for retransmission, than the SSRC should be =
the
> same.
> > However the RFC 4588 does not give arguments why it needs to be like
> > that. So I ask you: what would or can happen if there is a different
> > SSRC used?  If there are no convincing arguments why we must stick =
to
>=20
> Good question. If we don't use the same SSRC in session-muxed RTP
> sessions, it will introduce correlation problems. Receiver/XR reports
> coming from a larger number of receivers will be difficult to identify
> and match at the server side. There will be SSRC collisions, which =
will
> complicate things further.
>=20
> TOM: the big difference with when the RFC 4588 was being discussed and
> developed, is that now we are capable of advertising in SDP the SSRC =
of
> the media server, that is in this case the retransmission server SSRC
> used in the retransmission session. In fact for RAMS, we need to =
define
> the SSRC of the ssm RTP session, so we can as well do it for the
> retransmission session. Perhaps we should consider this different SSRC
> possibility (hence violating RFC 4588) as part of a new draft, the one =
I
> mentioned above.
>=20
>=20
> > the same SSRC, then, if we have a good use case to depart from that
> > "rule" -and the use case we are discussing here is IMO indeed a =
valid
> > use case- I do not see why we should be limited by such a "rule". =
The
> > "valid" use case is here that RAMS and Retransmission for SSM =
sessions
>=20
> > operates fine through any NAPT and without any dedicated RTCP =
message.
>=20
> -acbegen

From Even.roni@huawei.com  Tue Jun 30 03:57:11 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8798828C394 for <avt@core3.amsl.com>; Tue, 30 Jun 2009 03:57:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 rsXakOtAkAzN for <avt@core3.amsl.com>; Tue, 30 Jun 2009 03:57:10 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 256F23A6A47 for <avt@ietf.org>; Tue, 30 Jun 2009 03:57:10 -0700 (PDT)
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 <0KM100EK4T3DHO@szxga03-in.huawei.com> for avt@ietf.org; Tue, 30 Jun 2009 18:57:13 +0800 (CST)
Received: from huawei.com ([172.24.1.3]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KM100HKST3DJL@szxga03-in.huawei.com> for avt@ietf.org; Tue, 30 Jun 2009 18:57:13 +0800 (CST)
Received: from windows8d787f9 (bzq-79-180-107-118.red.bezeqint.net [79.180.107.118]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KM100IJUT1RE6@szxml01-in.huawei.com>; Tue, 30 Jun 2009 18:57:13 +0800 (CST)
Date: Tue, 30 Jun 2009 13:55:56 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <04CAD96D4C5A3D48B1919248A8FE0D5409A71F22@xmb-sjc-215.amer.cisco.com>
To: "'Ali C. Begen (abegen)'" <abegen@cisco.com>, 'VAN CAENEGEM Tom' <Tom.Van_Caenegem@alcatel-lucent.be>, "'Bill Ver Steeg (versteb)'" <versteb@cisco.com>, 'Zeev Vax' <zeevvax@microsoft.com>, avt@ietf.org
Message-id: <00e601c9f971$6a7b0e80$3f712b80$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcnuxB26XvRkvXRRTni4MNRgozvTWAAWU97gAAeQjdAAAolg4AAD9PPQAAKwHzAAAoEH4AAj0yqgABhckVAAAKI+MAAAgrDgARoKBSAALhpHsAAKg7ngAAPu9/AALWBagACY+iigAB/UF7AAB5UIQA==
iPlanet-SMTP-Warning: Lines longer than SMTP allows found and truncated.
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04137224@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54099DFD1A@xmb-sjc-215.amer.cisco.com> <"04CAD96D4C5A3 E0D54099E00C4"@xmb-sjc-215.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04186C7F@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D5409A71F22@xmb-sjc-215.amer.cisco.com>
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 30 Jun 2009 10:57:11 -0000

Hi guys,
My view is that this is not a general NACK problem but only for the case of
SSM and retransmission with similar box architecture to the RAMS solution.
If you have another case please explain
Roni

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Ali C. Begen (abegen)
> Sent: Tuesday, June 30, 2009 10:19 AM
> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni Even;
> avt@ietf.org
> Subject: Re: [AVT] Port mappings, NAT, and RAMS
> 
> Hi Tom,
> 
> Let's get the input from the WG on these points. I believe going for a
> more general solution that will be applicable to both RAMS and NACK is
> more desirable.
> 
> BR,
> -acbegen
> 
> 
> 
> > -----Original Message-----
> > From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> > Sent: Monday, June 29, 2009 9:17 AM
> > To: Ali C. Begen (abegen); Bill Ver Steeg (versteb); Zeev Vax; Roni
> Even; avt@ietf.org
> > Subject: RE: Port mappings, NAT, and RAMS
> >
> >
> >  Ali,
> >
> > See some comments below (TOM).
> >
> > -----Original Message-----
> > From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> > Sent: vrijdag 26 juni 2009 17:41
> > To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni Even;
> > avt@ietf.org
> > Subject: RE: Port mappings, NAT, and RAMS
> >
> > Hi Tom,
> >
> > [snip]
> > > The reason why we need pubports is that it indicates "explicitly"
> the
> > > port the client wants to use to receive the burst is the port it
> used
> > > to send the RAMS-R/pubports message. I believe we need this
> explicit
> > > indication, ow, we will be making an implicit assumption. Note that
> > > the rams-r/pubports is in the primary session and burst/ret packets
> > > are in the retransmission session, which is different than the
> > primary.
> > >
> > > As far as I can see, not everybody agrees on this point, but we
> need
> > > to make a decision here before we mandate anything.
> > >
> > > TOM: I agree with your last line, but I do not completely agree
> when
> > > you mention "implicit" assumption, especially for option 3, where
> > > RAMS-R (or
> > > NACK) and the Pub-port message are in the same compound message. If
> we
> >
> > > "define" that if no pub-report message is sent by the RR, the
> > > information towards the Retransmission server is exactly the same
> as
> > > when an RTP receiver sends an RTCP compound message made up of an
> RTCP
> >
> > > NACK/RAMS-R together with a pub-port message where the ports are
> > "zero"
> >
> > We "may" be able to say it from RAMS-R but not for NACK since we are
> not
> > defining it, we will be overloading its meaning, IMO. And as you/Bill
> > pointed out in other emails, I also believe that this is more general
> > problem than just RAMS. We need something like pubports for NACKs as
> > well.
> >
> >
> > TOM: indeed, that is why IMO we should define this problem and
> solution
> > in a separate draft which applies to any system architecture where a
> > unicast session from a FT is coupled to a ssm session with that same
> FT.
> >
> >
> > > -as currently proposed in the RAMS draft now.  I agree that this is
> > > not true for option 4, where pub-port and RAMS-R or NACK are
> separate
> > > messages, but I do not favour the solution of option 4 for the same
> > > reason you mention in your reply (a new failure mode). So, if
> option 4
> >
> > > is -for that reason- no longer considered, I do not see a problem
> with
> >
> > > defining this rule/clause as expressed above. In other words, there
> is
> >
> > > no need for a pub-report message in this scenario and this results
> NOT
> >
> > > in an "assumption" what-so-ever.
> > >
> > >
> > > > supports RTP/RTCP muxing itself, and if it knows the RS supports
> > > > RTP/RTCP muxing too (as indicated in the declarative sdp received
> by
> >
> > > > the
> > > > RR)
> > > >
> > > > -Don't we also allow that for option 3, the port P2 actually
> equals
> > > > port P4? This is a kind of hybrid of session and SSRC
> multiplexing
> > > > of the primary multicast RTP stream and the
> > > > retransmission/acceleration session
> > > > :  on the unidirectional RTP layer, the primary MC packets and
> the
> > > > unicast retransmission packets are clearly session muxed, but the
> > > > RTCP
> > >
> > > > "return" channel for both streams have exactly the same transport
> > > > addresses, but are distinguished by means of a different SSRC.
> In
> > > > that
> > >
> > > How? Since SSM and retransmission sessions are session muxed, they
> > > have the same SSRC. When a client is sending a receiver report, how
> do
> >
> > > we identify which session it belongs to? So, I believe P2 should be
> > > different than P4.
> > >
> > > TOM: you are right. But notice this: RFC 4588 mandates that when
> > > session muxing is used for retransmission, than the SSRC should be
> the
> > same.
> > > However the RFC 4588 does not give arguments why it needs to be
> like
> > > that. So I ask you: what would or can happen if there is a
> different
> > > SSRC used?  If there are no convincing arguments why we must stick
> to
> >
> > Good question. If we don't use the same SSRC in session-muxed RTP
> > sessions, it will introduce correlation problems. Receiver/XR reports
> > coming from a larger number of receivers will be difficult to
> identify
> > and match at the server side. There will be SSRC collisions, which
> will
> > complicate things further.
> >
> > TOM: the big difference with when the RFC 4588 was being discussed
> and
> > developed, is that now we are capable of advertising in SDP the SSRC
> of
> > the media server, that is in this case the retransmission server SSRC
> > used in the retransmission session. In fact for RAMS, we need to
> define
> > the SSRC of the ssm RTP session, so we can as well do it for the
> > retransmission session. Perhaps we should consider this different
> SSRC
> > possibility (hence violating RFC 4588) as part of a new draft, the
> one I
> > mentioned above.
> >
> >
> > > the same SSRC, then, if we have a good use case to depart from that
> > > "rule" -and the use case we are discussing here is IMO indeed a
> valid
> > > use case- I do not see why we should be limited by such a "rule".
> The
> > > "valid" use case is here that RAMS and Retransmission for SSM
> sessions
> >
> > > operates fine through any NAPT and without any dedicated RTCP
> message.
> >
> > -acbegen
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From oran@cisco.com  Tue Jun 30 06:12:43 2009
Return-Path: <oran@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 713D028C3D0 for <avt@core3.amsl.com>; Tue, 30 Jun 2009 06:12:43 -0700 (PDT)
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 LncnZ78M7hgh for <avt@core3.amsl.com>; Tue, 30 Jun 2009 06:12:41 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 7309828C3AE for <avt@ietf.org>; Tue, 30 Jun 2009 06:12:41 -0700 (PDT)
X-Files: PGP.sig : 195
X-IronPort-AV: E=Sophos;i="4.42,316,1243814400";  d="sig'?scan'208";a="48926903"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 30 Jun 2009 13:10:45 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n5UDAjoE004787;  Tue, 30 Jun 2009 09:10:45 -0400
Received: from dhcp-64-100-112-203.cisco.com (dhcp-64-100-112-203.cisco.com [64.100.112.203]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n5UDAVf0020967; Tue, 30 Jun 2009 13:10:45 GMT
Received: from [127.0.0.1] by dhcp-64-100-112-203.cisco.com (PGP Universal service); Tue, 30 Jun 2009 09:10:45 -0400
X-PGP-Universal: processed; by dhcp-64-100-112-203.cisco.com on Tue, 30 Jun 2009 09:10:45 -0400
Message-Id: <83D31F7D-8D4C-44D1-9AD3-814C4776922F@cisco.com>
From: David R Oran <oran@cisco.com>
To: Roni Even <Even.roni@huawei.com>
In-Reply-To: <00e601c9f971$6a7b0e80$3f712b80$%roni@huawei.com>
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 30 Jun 2009 09:10:26 -0400
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04137224@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54099DFD1A@xmb-sjc-215.amer.cisco.com> <"04CA D96D4C5A3 E0D54099E00C4"@xmb-sjc-215.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04186C7F@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D5409A71F22@xmb-sjc-215.amer.cisco.com> <00e601c9f971$6a7b0e80$3f712b80$%roni@huawei.com>
X-Mailer: Apple Mail (2.935.3)
X-PGP-Encoding-Format: MIME
X-PGP-Encoding-Version: 2.0.2
Content-Type: multipart/signed; boundary="PGP_Universal_071BEA8A_428D8B7C_EA8EC29F_BE9A33DB"; protocol="application/pgp-signature"; micalg="pgp-sha1"
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=9041; t=1246367445; x=1247231445; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=oran@cisco.com; z=From:=20David=20R=20Oran=20<oran@cisco.com> |Subject:=20Re=3A=20[AVT]=20Port=20mappings,=20NAT,=20and=2 0RAMS |Sender:=20 |To:=20Roni=20Even=20<Even.roni@huawei.com>; bh=7jwT8cBs5JaWqOpCpPTdMQ0LGxsy6hIbJcebWrMyW44=; b=YmKlIZPoyELVJn8J5xiAuT1SQJl8eJ/EEAYXJZ/IMSErZokeBIgmbd6RFI XhICzoDAnPfIe2H+qjBLMo/CzopfwpjoRHXsgQ+f1SWk9Nrl4DQaV6I3fnUW /ZG4ULGjHq;
Authentication-Results: rtp-dkim-1; header.From=oran@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; ); 
Cc: 'VAN CAENEGEM Tom' <Tom.Van_Caenegem@alcatel-lucent.be>, avt@ietf.org, "'Bill Ver Steeg \(versteb\)'" <versteb@cisco.com>, 'Zeev Vax' <zeevvax@microsoft.com>
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 30 Jun 2009 13:12:43 -0000

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


On Jun 30, 2009, at 6:55 AM, Roni Even wrote:

> Hi guys,
> My view is that this is not a general NACK problem but only for the  
> case of
> SSM and retransmission with similar box architecture to the RAMS  
> solution.
> If you have another case please explain
I believe it is actually a MORE general problem than NACK or RAMS. I  
arises from mixing SSM sessions and unicast sessions for the same RTP- 
based application. That's because multicast enforces port symmetry  
among all the receivers while unicast needs per-receiver port selection.

So far we have two uses for mixing multicast and unicast:  
retransmission-based repair, and RAMS. I suspect more uses will arise  
in the future. I can think of a few off the top of my head:
- customized per-user overlays (e.g. to be alpha-blended with the  
video) or object-level replacement
- network-coded error recovery streams
- extra media info for re-integration when switching back from unicast  
to multicast in a fast-forward-to-realtime capability when doing  
"pause-live-content" style services
- adaptive switching between multicast and unicast based on number of  
simultaneous receivers.

I have a strong intuition that doing a generic mechanism to atomically  
signal ports for unicast sessions using the RTCP feedback machinery of  
the SSM session would be highly advisable.

So, I think:
a) we need to solve this problem
b) it exists even in the absence of NATs
c) we need a generic mechanism
d) it should be documented in a separate draft, and not part of RAMs  
or AVPF.

If we can agree to these points, then we can have a more detailed  
discussion of the appropriate machinery. I have opinions on that  
subject too.

DaveO.



> Roni
>
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
>> Ali C. Begen (abegen)
>> Sent: Tuesday, June 30, 2009 10:19 AM
>> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni Even;
>> avt@ietf.org
>> Subject: Re: [AVT] Port mappings, NAT, and RAMS
>>
>> Hi Tom,
>>
>> Let's get the input from the WG on these points. I believe going  
>> for a
>> more general solution that will be applicable to both RAMS and NACK  
>> is
>> more desirable.
>>
>> BR,
>> -acbegen
>>
>>
>>
>>> -----Original Message-----
>>> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
>>> Sent: Monday, June 29, 2009 9:17 AM
>>> To: Ali C. Begen (abegen); Bill Ver Steeg (versteb); Zeev Vax; Roni
>> Even; avt@ietf.org
>>> Subject: RE: Port mappings, NAT, and RAMS
>>>
>>>
>>> Ali,
>>>
>>> See some comments below (TOM).
>>>
>>> -----Original Message-----
>>> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
>>> Sent: vrijdag 26 juni 2009 17:41
>>> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni Even;
>>> avt@ietf.org
>>> Subject: RE: Port mappings, NAT, and RAMS
>>>
>>> Hi Tom,
>>>
>>> [snip]
>>>> The reason why we need pubports is that it indicates "explicitly"
>> the
>>>> port the client wants to use to receive the burst is the port it
>> used
>>>> to send the RAMS-R/pubports message. I believe we need this
>> explicit
>>>> indication, ow, we will be making an implicit assumption. Note that
>>>> the rams-r/pubports is in the primary session and burst/ret packets
>>>> are in the retransmission session, which is different than the
>>> primary.
>>>>
>>>> As far as I can see, not everybody agrees on this point, but we
>> need
>>>> to make a decision here before we mandate anything.
>>>>
>>>> TOM: I agree with your last line, but I do not completely agree
>> when
>>>> you mention "implicit" assumption, especially for option 3, where
>>>> RAMS-R (or
>>>> NACK) and the Pub-port message are in the same compound message. If
>> we
>>>
>>>> "define" that if no pub-report message is sent by the RR, the
>>>> information towards the Retransmission server is exactly the same
>> as
>>>> when an RTP receiver sends an RTCP compound message made up of an
>> RTCP
>>>
>>>> NACK/RAMS-R together with a pub-port message where the ports are
>>> "zero"
>>>
>>> We "may" be able to say it from RAMS-R but not for NACK since we are
>> not
>>> defining it, we will be overloading its meaning, IMO. And as you/ 
>>> Bill
>>> pointed out in other emails, I also believe that this is more  
>>> general
>>> problem than just RAMS. We need something like pubports for NACKs as
>>> well.
>>>
>>>
>>> TOM: indeed, that is why IMO we should define this problem and
>> solution
>>> in a separate draft which applies to any system architecture where a
>>> unicast session from a FT is coupled to a ssm session with that same
>> FT.
>>>
>>>
>>>> -as currently proposed in the RAMS draft now.  I agree that this is
>>>> not true for option 4, where pub-port and RAMS-R or NACK are
>> separate
>>>> messages, but I do not favour the solution of option 4 for the same
>>>> reason you mention in your reply (a new failure mode). So, if
>> option 4
>>>
>>>> is -for that reason- no longer considered, I do not see a problem
>> with
>>>
>>>> defining this rule/clause as expressed above. In other words, there
>> is
>>>
>>>> no need for a pub-report message in this scenario and this results
>> NOT
>>>
>>>> in an "assumption" what-so-ever.
>>>>
>>>>
>>>>> supports RTP/RTCP muxing itself, and if it knows the RS supports
>>>>> RTP/RTCP muxing too (as indicated in the declarative sdp received
>> by
>>>
>>>>> the
>>>>> RR)
>>>>>
>>>>> -Don't we also allow that for option 3, the port P2 actually
>> equals
>>>>> port P4? This is a kind of hybrid of session and SSRC
>> multiplexing
>>>>> of the primary multicast RTP stream and the
>>>>> retransmission/acceleration session
>>>>> :  on the unidirectional RTP layer, the primary MC packets and
>> the
>>>>> unicast retransmission packets are clearly session muxed, but the
>>>>> RTCP
>>>>
>>>>> "return" channel for both streams have exactly the same transport
>>>>> addresses, but are distinguished by means of a different SSRC.
>> In
>>>>> that
>>>>
>>>> How? Since SSM and retransmission sessions are session muxed, they
>>>> have the same SSRC. When a client is sending a receiver report, how
>> do
>>>
>>>> we identify which session it belongs to? So, I believe P2 should be
>>>> different than P4.
>>>>
>>>> TOM: you are right. But notice this: RFC 4588 mandates that when
>>>> session muxing is used for retransmission, than the SSRC should be
>> the
>>> same.
>>>> However the RFC 4588 does not give arguments why it needs to be
>> like
>>>> that. So I ask you: what would or can happen if there is a
>> different
>>>> SSRC used?  If there are no convincing arguments why we must stick
>> to
>>>
>>> Good question. If we don't use the same SSRC in session-muxed RTP
>>> sessions, it will introduce correlation problems. Receiver/XR  
>>> reports
>>> coming from a larger number of receivers will be difficult to
>> identify
>>> and match at the server side. There will be SSRC collisions, which
>> will
>>> complicate things further.
>>>
>>> TOM: the big difference with when the RFC 4588 was being discussed
>> and
>>> developed, is that now we are capable of advertising in SDP the SSRC
>> of
>>> the media server, that is in this case the retransmission server  
>>> SSRC
>>> used in the retransmission session. In fact for RAMS, we need to
>> define
>>> the SSRC of the ssm RTP session, so we can as well do it for the
>>> retransmission session. Perhaps we should consider this different
>> SSRC
>>> possibility (hence violating RFC 4588) as part of a new draft, the
>> one I
>>> mentioned above.
>>>
>>>
>>>> the same SSRC, then, if we have a good use case to depart from that
>>>> "rule" -and the use case we are discussing here is IMO indeed a
>> valid
>>>> use case- I do not see why we should be limited by such a "rule".
>> The
>>>> "valid" use case is here that RAMS and Retransmission for SSM
>> sessions
>>>
>>>> operates fine through any NAPT and without any dedicated RTCP
>> message.
>>>
>>> -acbegen
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


--PGP_Universal_071BEA8A_428D8B7C_EA8EC29F_BE9A33DB
Content-Type: application/pgp-signature;
	x-mac-type=70674453;
	name=PGP.sig
Content-Disposition: attachment; filename=PGP.sig

-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.10.0 (Build 500)

iQA/AwUBSkoOzo1mhLZU3SrmEQJmEgCeLmAgPkuJHx6vwINwqmhuSfllLTYAoPOa
Y/0IlNGWONGYXWn92TiCPeTM
=1qdt
-----END PGP SIGNATURE-----

--PGP_Universal_071BEA8A_428D8B7C_EA8EC29F_BE9A33DB--

From lillianlee62@yahoo.com  Tue Jun 30 06:41:55 2009
Return-Path: <lillianlee62@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 E3DAC28C3A2 for <avt@core3.amsl.com>; Tue, 30 Jun 2009 06:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.205
X-Spam-Level: 
X-Spam-Status: No, score=-0.205 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_33=0.6, MIME_BASE64_BLANKS=0.041,  MIME_BASE64_TEXT=1.753]
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 6KJg+RCcDP6v for <avt@core3.amsl.com>; Tue, 30 Jun 2009 06:41:53 -0700 (PDT)
Received: from smtp101-mob.biz.mail.ac4.yahoo.com (smtp101-mob.biz.mail.ac4.yahoo.com [76.13.13.222]) by core3.amsl.com (Postfix) with SMTP id 7E6D228C3CB for <avt@ietf.org>; Tue, 30 Jun 2009 06:41:53 -0700 (PDT)
Received: (qmail 1729 invoked from network); 30 Jun 2009 13:34:33 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:X-rim-org-msg-ref-id:Return-Receipt-To:Message-ID:Content-Transfer-Encoding:Reply-To:X-Priority:References:In-Reply-To:Sensitivity:Importance:To:Subject:From:Date:Content-Type:MIME-Version; b=IKzg0jf3upBRpunNry0S9mnpUasXQ3CW1oSNbu1eRoDZ0K+BItLuLfDXIlXbl9ZaQNNBVt360HyeG43Eu5y2zFltHk58bZXPDcdm66pmkVPY70LZ+dd8TJ8vydpMk69p/RQ44qbWmE5FFMFe130WnbekRUSexd0EP8ygkA59Sp0= ; 
Received: from unknown (HELO bda415.bisx.prod.on.blackberry) (lillianlee62@67.223.71.32 with xymcookie) by smtp101-mob.biz.mail.ac4.yahoo.com with SMTP; 30 Jun 2009 13:34:32 -0000
X-Yahoo-SMTP: k6PZWCeswBBiNLhuYk2Vu4CzcoAKNB20bg--
X-YMail-OSG: lUcAAj0VM1kKiMybfaZPQVyRz_ENFZrg5c2B3ff5qtoodWOBOPmtLjD0OkjGZErc_QC8RYiqNcupCGJ9HqdDB94hgr1Nd4APxSCfkAn8X1E5UINvtA.wCJIRtuvbO_a7C26QBUiSWl8bGx.vpIhZMiqIiVUhjOgmMkiS0eAbssXukhtmVnHnIolCM9Y26ZSSoKFf9bTyfDHVk54vYeHB2LYVuta0h5Gq0XG2z6w6QrlkpshB4vx4UDyaRRM9WmFP6N0IBY.J.p36O3BpW3rZXpDeymE5Gf.bkSyqEE6XixacSeO03T23SScahJrhtqn7.A4gc5or42UXKZcRYoXbBqOq4uWdAAvHd0mdSP6ozUVd8A--
X-Yahoo-Newman-Property: ymail-3
X-rim-org-msg-ref-id: 1226939246
Message-ID: <1226939246-1246368870-cardhu_decombobulator_blackberry.rim.net-977762359-@bxe1304.bisx.prod.on.blackberry>
Content-Transfer-Encoding: base64
X-Priority: Normal
References: <mailman.11847.1246367564.4936.avt@ietf.org>
In-Reply-To: <mailman.11847.1246367564.4936.avt@ietf.org>
Sensitivity: Normal
Importance: Normal
To: avt@ietf.org
From: lillianlee62@yahoo.com
Date: Tue, 30 Jun 2009 13:35:38 +0000
Content-Type: text/plain
MIME-Version: 1.0
Subject: Re: [AVT] avt Digest, Vol 62, Issue 59
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: lillianlee62@yahoo.com
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, 30 Jun 2009 13:41:56 -0000

DQpTZW50IHZpYSBCbGFja0JlcnJ5IGZyb20gVC1Nb2JpbGUNCg0KLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCkZyb206IGF2dC1yZXF1ZXN0QGlldGYub3JnDQoNCkRhdGU6IFR1ZSwgMzAgSnVu
IDIwMDkgMDY6MTI6NDQgDQpUbzogPGF2dEBpZXRmLm9yZz4NClN1YmplY3Q6IGF2dCBEaWdlc3Qs
IFZvbCA2MiwgSXNzdWUgNTkNCg0KDQpJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGRpZ2VzdCB3
aXRob3V0IGFsbCB0aGUgaW5kaXZpZHVhbCBtZXNzYWdlDQphdHRhY2htZW50cyB5b3Ugd2lsbCBu
ZWVkIHRvIHVwZGF0ZSB5b3VyIGRpZ2VzdCBvcHRpb25zIGluIHlvdXIgbGlzdA0Kc3Vic2NyaXB0
aW9uLiAgVG8gZG8gc28sIGdvIHRvIA0KDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL2F2dA0KDQpDbGljayB0aGUgJ1Vuc3Vic2NyaWJlIG9yIGVkaXQgb3B0aW9ucycgYnV0
dG9uLCBsb2cgaW4sIGFuZCBzZXQgIkdldA0KTUlNRSBvciBQbGFpbiBUZXh0IERpZ2VzdHM/IiB0
byBNSU1FLiAgWW91IGNhbiBzZXQgdGhpcyBvcHRpb24NCmdsb2JhbGx5IGZvciBhbGwgdGhlIGxp
c3QgZGlnZXN0cyB5b3UgcmVjZWl2ZSBhdCB0aGlzIHBvaW50Lg0KDQoNCg0KU2VuZCBhdnQgbWFp
bGluZyBsaXN0IHN1Ym1pc3Npb25zIHRvDQoJYXZ0QGlldGYub3JnDQoNClRvIHN1YnNjcmliZSBv
ciB1bnN1YnNjcmliZSB2aWEgdGhlIFdvcmxkIFdpZGUgV2ViLCB2aXNpdA0KCWh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vYXZ0DQpvciwgdmlhIGVtYWlsLCBzZW5kIGEgbWVz
c2FnZSB3aXRoIHN1YmplY3Qgb3IgYm9keSAnaGVscCcgdG8NCglhdnQtcmVxdWVzdEBpZXRmLm9y
Zw0KDQpZb3UgY2FuIHJlYWNoIHRoZSBwZXJzb24gbWFuYWdpbmcgdGhlIGxpc3QgYXQNCglhdnQt
b3duZXJAaWV0Zi5vcmcNCg0KV2hlbiByZXBseWluZywgcGxlYXNlIGVkaXQgeW91ciBTdWJqZWN0
IGxpbmUgc28gaXQgaXMgbW9yZSBzcGVjaWZpYw0KdGhhbiAiUmU6IENvbnRlbnRzIG9mIGF2dCBk
aWdlc3QuLi4iDQoNCg0KVG9kYXkncyBUb3BpY3M6DQoNCiAgIDEuIFJlOiBQb3J0IG1hcHBpbmdz
LCBOQVQsIGFuZCBSQU1TIChBbGkgQy4gQmVnZW4gKGFiZWdlbikpDQogICAyLiBSZTogUG9ydCBt
YXBwaW5ncywgTkFULCBhbmQgUkFNUyAoUm9uaSBFdmVuKQ0KICAgMy4gUmU6IFBvcnQgbWFwcGlu
Z3MsIE5BVCwgYW5kIFJBTVMgKERhdmlkIFIgT3JhbikNCg0KDQotLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCk1l
c3NhZ2U6IDENCkRhdGU6IFR1ZSwgMzAgSnVuIDIwMDkgMDA6MTg6MzEgLTA3MDANCkZyb206ICJB
bGkgQy4gQmVnZW4gKGFiZWdlbikiIDxhYmVnZW5AY2lzY28uY29tPg0KU3ViamVjdDogUmU6IFtB
VlRdIFBvcnQgbWFwcGluZ3MsIE5BVCwgYW5kIFJBTVMNClRvOiAiVkFOIENBRU5FR0VNIFRvbSIg
PFRvbS5WYW5fQ2FlbmVnZW1AYWxjYXRlbC1sdWNlbnQuYmU+LAkiQmlsbCBWZXINCglTdGVlZyAo
dmVyc3RlYikiIDx2ZXJzdGViQGNpc2NvLmNvbT4sCSJaZWV2IFZheCINCgk8emVldnZheEBtaWNy
b3NvZnQuY29tPiwgIlJvbmkgRXZlbiIgPEV2ZW4ucm9uaUBodWF3ZWkuY29tPiwNCgk8YXZ0QGll
dGYub3JnPg0KTWVzc2FnZS1JRDoNCgk8MDRDQUQ5NkQ0QzVBM0Q0OEIxOTE5MjQ4QThGRTBENTQw
OUE3MUYyMkB4bWItc2pjLTIxNS5hbWVyLmNpc2NvLmNvbT4NCkNvbnRlbnQtVHlwZTogdGV4dC9w
bGFpbjsJY2hhcnNldD0iV2luZG93cy0xMjUyIg0KDQpIaSBUb20sDQoNCkxldCdzIGdldCB0aGUg
aW5wdXQgZnJvbSB0aGUgV0cgb24gdGhlc2UgcG9pbnRzLiBJIGJlbGlldmUgZ29pbmcgZm9yIGEg
bW9yZSBnZW5lcmFsIHNvbHV0aW9uIHRoYXQgd2lsbCBiZSBhcHBsaWNhYmxlIHRvIGJvdGggUkFN
UyBhbmQgTkFDSyBpcyBtb3JlIGRlc2lyYWJsZS4NCg0KQlIsDQotYWNiZWdlbg0KDQoNCg0KPiAt
LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBWQU4gQ0FFTkVHRU0gVG9tIFttYWls
dG86VG9tLlZhbl9DYWVuZWdlbUBhbGNhdGVsLWx1Y2VudC5iZV0NCj4gU2VudDogTW9uZGF5LCBK
dW5lIDI5LCAyMDA5IDk6MTcgQU0NCj4gVG86IEFsaSBDLiBCZWdlbiAoYWJlZ2VuKTsgQmlsbCBW
ZXIgU3RlZWcgKHZlcnN0ZWIpOyBaZWV2IFZheDsgUm9uaSBFdmVuOyBhdnRAaWV0Zi5vcmcNCj4g
U3ViamVjdDogUkU6IFBvcnQgbWFwcGluZ3MsIE5BVCwgYW5kIFJBTVMNCj4gDQo+IA0KPiAgQWxp
LA0KPiANCj4gU2VlIHNvbWUgY29tbWVudHMgYmVsb3cgKFRPTSkuDQo+IA0KPiAtLS0tLU9yaWdp
bmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBBbGkgQy4gQmVnZW4gKGFiZWdlbikgW21haWx0bzph
YmVnZW5AY2lzY28uY29tXQ0KPiBTZW50OiB2cmlqZGFnIDI2IGp1bmkgMjAwOSAxNzo0MQ0KPiBU
bzogVkFOIENBRU5FR0VNIFRvbTsgQmlsbCBWZXIgU3RlZWcgKHZlcnN0ZWIpOyBaZWV2IFZheDsg
Um9uaSBFdmVuOw0KPiBhdnRAaWV0Zi5vcmcNCj4gU3ViamVjdDogUkU6IFBvcnQgbWFwcGluZ3Ms
IE5BVCwgYW5kIFJBTVMNCj4gDQo+IEhpIFRvbSwNCj4gDQo+IFtzbmlwXQ0KPiA+IFRoZSByZWFz
b24gd2h5IHdlIG5lZWQgcHVicG9ydHMgaXMgdGhhdCBpdCBpbmRpY2F0ZXMgImV4cGxpY2l0bHki
IHRoZQ0KPiA+IHBvcnQgdGhlIGNsaWVudCB3YW50cyB0byB1c2UgdG8gcmVjZWl2ZSB0aGUgYnVy
c3QgaXMgdGhlIHBvcnQgaXQgdXNlZA0KPiA+IHRvIHNlbmQgdGhlIFJBTVMtUi9wdWJwb3J0cyBt
ZXNzYWdlLiBJIGJlbGlldmUgd2UgbmVlZCB0aGlzIGV4cGxpY2l0DQo+ID4gaW5kaWNhdGlvbiwg
b3csIHdlIHdpbGwgYmUgbWFraW5nIGFuIGltcGxpY2l0IGFzc3VtcHRpb24uIE5vdGUgdGhhdA0K
PiA+IHRoZSByYW1zLXIvcHVicG9ydHMgaXMgaW4gdGhlIHByaW1hcnkgc2Vzc2lvbiBhbmQgYnVy
c3QvcmV0IHBhY2tldHMNCj4gPiBhcmUgaW4gdGhlIHJldHJhbnNtaXNzaW9uIHNlc3Npb24sIHdo
aWNoIGlzIGRpZmZlcmVudCB0aGFuIHRoZQ0KPiBwcmltYXJ5Lg0KPiA+DQo+ID4gQXMgZmFyIGFz
IEkgY2FuIHNlZSwgbm90IGV2ZXJ5Ym9keSBhZ3JlZXMgb24gdGhpcyBwb2ludCwgYnV0IHdlIG5l
ZWQNCj4gPiB0byBtYWtlIGEgZGVjaXNpb24gaGVyZSBiZWZvcmUgd2UgbWFuZGF0ZSBhbnl0aGlu
Zy4NCj4gPg0KPiA+IFRPTTogSSBhZ3JlZSB3aXRoIHlvdXIgbGFzdCBsaW5lLCBidXQgSSBkbyBu
b3QgY29tcGxldGVseSBhZ3JlZSB3aGVuDQo+ID4geW91IG1lbnRpb24gImltcGxpY2l0IiBhc3N1
bXB0aW9uLCBlc3BlY2lhbGx5IGZvciBvcHRpb24gMywgd2hlcmUNCj4gPiBSQU1TLVIgKG9yDQo+
ID4gTkFDSykgYW5kIHRoZSBQdWItcG9ydCBtZXNzYWdlIGFyZSBpbiB0aGUgc2FtZSBjb21wb3Vu
ZCBtZXNzYWdlLiBJZiB3ZQ0KPiANCj4gPiAiZGVmaW5lIiB0aGF0IGlmIG5vIHB1Yi1yZXBvcnQg
bWVzc2FnZSBpcyBzZW50IGJ5IHRoZSBSUiwgdGhlDQo+ID4gaW5mb3JtYXRpb24gdG93YXJkcyB0
aGUgUmV0cmFuc21pc3Npb24gc2VydmVyIGlzIGV4YWN0bHkgdGhlIHNhbWUgYXMNCj4gPiB3aGVu
IGFuIFJUUCByZWNlaXZlciBzZW5kcyBhbiBSVENQIGNvbXBvdW5kIG1lc3NhZ2UgbWFkZSB1cCBv
ZiBhbiBSVENQDQo+IA0KPiA+IE5BQ0svUkFNUy1SIHRvZ2V0aGVyIHdpdGggYSBwdWItcG9ydCBt
ZXNzYWdlIHdoZXJlIHRoZSBwb3J0cyBhcmUNCj4gInplcm8iDQo+IA0KPiBXZSAibWF5IiBiZSBh
YmxlIHRvIHNheSBpdCBmcm9tIFJBTVMtUiBidXQgbm90IGZvciBOQUNLIHNpbmNlIHdlIGFyZSBu
b3QNCj4gZGVmaW5pbmcgaXQsIHdlIHdpbGwgYmUgb3ZlcmxvYWRpbmcgaXRzIG1lYW5pbmcsIElN
Ty4gQW5kIGFzIHlvdS9CaWxsDQo+IHBvaW50ZWQgb3V0IGluIG90aGVyIGVtYWlscywgSSBhbHNv
IGJlbGlldmUgdGhhdCB0aGlzIGlzIG1vcmUgZ2VuZXJhbA0KPiBwcm9ibGVtIHRoYW4ganVzdCBS
QU1TLiBXZSBuZWVkIHNvbWV0aGluZyBsaWtlIHB1YnBvcnRzIGZvciBOQUNLcyBhcw0KPiB3ZWxs
Lg0KPiANCj4gDQo+IFRPTTogaW5kZWVkLCB0aGF0IGlzIHdoeSBJTU8gd2Ugc2hvdWxkIGRlZmlu
ZSB0aGlzIHByb2JsZW0gYW5kIHNvbHV0aW9uDQo+IGluIGEgc2VwYXJhdGUgZHJhZnQgd2hpY2gg
YXBwbGllcyB0byBhbnkgc3lzdGVtIGFyY2hpdGVjdHVyZSB3aGVyZSBhDQo+IHVuaWNhc3Qgc2Vz
c2lvbiBmcm9tIGEgRlQgaXMgY291cGxlZCB0byBhIHNzbSBzZXNzaW9uIHdpdGggdGhhdCBzYW1l
IEZULg0KPiANCj4gDQo+ID4gLWFzIGN1cnJlbnRseSBwcm9wb3NlZCBpbiB0aGUgUkFNUyBkcmFm
dCBub3cuICBJIGFncmVlIHRoYXQgdGhpcyBpcw0KPiA+IG5vdCB0cnVlIGZvciBvcHRpb24gNCwg
d2hlcmUgcHViLXBvcnQgYW5kIFJBTVMtUiBvciBOQUNLIGFyZSBzZXBhcmF0ZQ0KPiA+IG1lc3Nh
Z2VzLCBidXQgSSBkbyBub3QgZmF2b3VyIHRoZSBzb2x1dGlvbiBvZiBvcHRpb24gNCBmb3IgdGhl
IHNhbWUNCj4gPiByZWFzb24geW91IG1lbnRpb24gaW4geW91ciByZXBseSAoYSBuZXcgZmFpbHVy
ZSBtb2RlKS4gU28sIGlmIG9wdGlvbiA0DQo+IA0KPiA+IGlzIC1mb3IgdGhhdCByZWFzb24tIG5v
IGxvbmdlciBjb25zaWRlcmVkLCBJIGRvIG5vdCBzZWUgYSBwcm9ibGVtIHdpdGgNCj4gDQo+ID4g
ZGVmaW5pbmcgdGhpcyBydWxlL2NsYXVzZSBhcyBleHByZXNzZWQgYWJvdmUuIEluIG90aGVyIHdv
cmRzLCB0aGVyZSBpcw0KPiANCj4gPiBubyBuZWVkIGZvciBhIHB1Yi1yZXBvcnQgbWVzc2FnZSBp
biB0aGlzIHNjZW5hcmlvIGFuZCB0aGlzIHJlc3VsdHMgTk9UDQo+IA0KPiA+IGluIGFuICJhc3N1
bXB0aW9uIiB3aGF0LXNvLWV2ZXIuDQo+ID4NCj4gPg0KPiA+ID4gc3VwcG9ydHMgUlRQL1JUQ1Ag
bXV4aW5nIGl0c2VsZiwgYW5kIGlmIGl0IGtub3dzIHRoZSBSUyBzdXBwb3J0cw0KPiA+ID4gUlRQ
L1JUQ1AgbXV4aW5nIHRvbyAoYXMgaW5kaWNhdGVkIGluIHRoZSBkZWNsYXJhdGl2ZSBzZHAgcmVj
ZWl2ZWQgYnkNCj4gDQo+ID4gPiB0aGUNCj4gPiA+IFJSKQ0KPiA+ID4NCj4gPiA+IC1Eb24ndCB3
ZSBhbHNvIGFsbG93IHRoYXQgZm9yIG9wdGlvbiAzLCB0aGUgcG9ydCBQMiBhY3R1YWxseSBlcXVh
bHMNCj4gPiA+IHBvcnQgUDQ/IFRoaXMgaXMgYSBraW5kIG9mIGh5YnJpZCBvZiBzZXNzaW9uIGFu
ZCBTU1JDIG11bHRpcGxleGluZw0KPiA+ID4gb2YgdGhlIHByaW1hcnkgbXVsdGljYXN0IFJUUCBz
dHJlYW0gYW5kIHRoZQ0KPiA+ID4gcmV0cmFuc21pc3Npb24vYWNjZWxlcmF0aW9uIHNlc3Npb24N
Cj4gPiA+IDogIG9uIHRoZSB1bmlkaXJlY3Rpb25hbCBSVFAgbGF5ZXIsIHRoZSBwcmltYXJ5IE1D
IHBhY2tldHMgYW5kIHRoZQ0KPiA+ID4gdW5pY2FzdCByZXRyYW5zbWlzc2lvbiBwYWNrZXRzIGFy
ZSBjbGVhcmx5IHNlc3Npb24gbXV4ZWQsIGJ1dCB0aGUNCj4gPiA+IFJUQ1ANCj4gPg0KPiA+ID4g
InJldHVybiIgY2hhbm5lbCBmb3IgYm90aCBzdHJlYW1zIGhhdmUgZXhhY3RseSB0aGUgc2FtZSB0
cmFuc3BvcnQNCj4gPiA+IGFkZHJlc3NlcywgYnV0IGFyZSBkaXN0aW5ndWlzaGVkIGJ5IG1lYW5z
IG9mIGEgZGlmZmVyZW50IFNTUkMuICBJbg0KPiA+ID4gdGhhdA0KPiA+DQo+ID4gSG93PyBTaW5j
ZSBTU00gYW5kIHJldHJhbnNtaXNzaW9uIHNlc3Npb25zIGFyZSBzZXNzaW9uIG11eGVkLCB0aGV5
DQo+ID4gaGF2ZSB0aGUgc2FtZSBTU1JDLiBXaGVuIGEgY2xpZW50IGlzIHNlbmRpbmcgYSByZWNl
aXZlciByZXBvcnQsIGhvdyBkbw0KPiANCj4gPiB3ZSBpZGVudGlmeSB3aGljaCBzZXNzaW9uIGl0
IGJlbG9uZ3MgdG8/IFNvLCBJIGJlbGlldmUgUDIgc2hvdWxkIGJlDQo+ID4gZGlmZmVyZW50IHRo
YW4gUDQuDQo+ID4NCj4gPiBUT006IHlvdSBhcmUgcmlnaHQuIEJ1dCBub3RpY2UgdGhpczogUkZD
IDQ1ODggbWFuZGF0ZXMgdGhhdCB3aGVuDQo+ID4gc2Vzc2lvbiBtdXhpbmcgaXMgdXNlZCBmb3Ig
cmV0cmFuc21pc3Npb24sIHRoYW4gdGhlIFNTUkMgc2hvdWxkIGJlIHRoZQ0KPiBzYW1lLg0KPiA+
IEhvd2V2ZXIgdGhlIFJGQyA0NTg4IGRvZXMgbm90IGdpdmUgYXJndW1lbnRzIHdoeSBpdCBuZWVk
cyB0byBiZSBsaWtlDQo+ID4gdGhhdC4gU28gSSBhc2sgeW91OiB3aGF0IHdvdWxkIG9yIGNhbiBo
YXBwZW4gaWYgdGhlcmUgaXMgYSBkaWZmZXJlbnQNCj4gPiBTU1JDIHVzZWQ/ICBJZiB0aGVyZSBh
cmUgbm8gY29udmluY2luZyBhcmd1bWVudHMgd2h5IHdlIG11c3Qgc3RpY2sgdG8NCj4gDQo+IEdv
b2QgcXVlc3Rpb24uIElmIHdlIGRvbid0IHVzZSB0aGUgc2FtZSBTU1JDIGluIHNlc3Npb24tbXV4
ZWQgUlRQDQo+IHNlc3Npb25zLCBpdCB3aWxsIGludHJvZHVjZSBjb3JyZWxhdGlvbiBwcm9ibGVt
cy4gUmVjZWl2ZXIvWFIgcmVwb3J0cw0KPiBjb21pbmcgZnJvbSBhIGxhcmdlciBudW1iZXIgb2Yg
cmVjZWl2ZXJzIHdpbGwgYmUgZGlmZmljdWx0IHRvIGlkZW50aWZ5DQo+IGFuZCBtYXRjaCBhdCB0
aGUgc2VydmVyIHNpZGUuIFRoZXJlIHdpbGwgYmUgU1NSQyBjb2xsaXNpb25zLCB3aGljaCB3aWxs
DQo+IGNvbXBsaWNhdGUgdGhpbmdzIGZ1cnRoZXIuDQo+IA0KPiBUT006IHRoZSBiaWcgZGlmZmVy
ZW5jZSB3aXRoIHdoZW4gdGhlIFJGQyA0NTg4IHdhcyBiZWluZyBkaXNjdXNzZWQgYW5kDQo+IGRl
dmVsb3BlZCwgaXMgdGhhdCBub3cgd2UgYXJlIGNhcGFibGUgb2YgYWR2ZXJ0aXNpbmcgaW4gU0RQ
IHRoZSBTU1JDIG9mDQo+IHRoZSBtZWRpYSBzZXJ2ZXIsIHRoYXQgaXMgaW4gdGhpcyBjYXNlIHRo
ZSByZXRyYW5zbWlzc2lvbiBzZXJ2ZXIgU1NSQw0KPiB1c2VkIGluIHRoZSByZXRyYW5zbWlzc2lv
biBzZXNzaW9uLiBJbiBmYWN0IGZvciBSQU1TLCB3ZSBuZWVkIHRvIGRlZmluZQ0KPiB0aGUgU1NS
QyBvZiB0aGUgc3NtIFJUUCBzZXNzaW9uLCBzbyB3ZSBjYW4gYXMgd2VsbCBkbyBpdCBmb3IgdGhl
DQo+IHJldHJhbnNtaXNzaW9uIHNlc3Npb24uIFBlcmhhcHMgd2Ugc2hvdWxkIGNvbnNpZGVyIHRo
aXMgZGlmZmVyZW50IFNTUkMNCj4gcG9zc2liaWxpdHkgKGhlbmNlIHZpb2xhdGluZyBSRkMgNDU4
OCkgYXMgcGFydCBvZiBhIG5ldyBkcmFmdCwgdGhlIG9uZSBJDQo+IG1lbnRpb25lZCBhYm92ZS4N
Cj4gDQo+IA0KPiA+IHRoZSBzYW1lIFNTUkMsIHRoZW4sIGlmIHdlIGhhdmUgYSBnb29kIHVzZSBj
YXNlIHRvIGRlcGFydCBmcm9tIHRoYXQNCj4gPiAicnVsZSIgLWFuZCB0aGUgdXNlIGNhc2Ugd2Ug
YXJlIGRpc2N1c3NpbmcgaGVyZSBpcyBJTU8gaW5kZWVkIGEgdmFsaWQNCj4gPiB1c2UgY2FzZS0g
SSBkbyBub3Qgc2VlIHdoeSB3ZSBzaG91bGQgYmUgbGltaXRlZCBieSBzdWNoIGEgInJ1bGUiLiBU
aGUNCj4gPiAidmFsaWQiIHVzZSBjYXNlIGlzIGhlcmUgdGhhdCBSQU1TIGFuZCBSZXRyYW5zbWlz
c2lvbiBmb3IgU1NNIHNlc3Npb25zDQo+IA0KPiA+IG9wZXJhdGVzIGZpbmUgdGhyb3VnaCBhbnkg
TkFQVCBhbmQgd2l0aG91dCBhbnkgZGVkaWNhdGVkIFJUQ1AgbWVzc2FnZS4NCj4gDQo+IC1hY2Jl
Z2VuDQoNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCk1lc3NhZ2U6IDINCkRh
dGU6IFR1ZSwgMzAgSnVuIDIwMDkgMTM6NTU6NTYgKzAzMDANCkZyb206IFJvbmkgRXZlbiA8RXZl
bi5yb25pQGh1YXdlaS5jb20+DQpTdWJqZWN0OiBSZTogW0FWVF0gUG9ydCBtYXBwaW5ncywgTkFU
LCBhbmQgUkFNUw0KVG86ICInQWxpIEMuIEJlZ2VuIChhYmVnZW4pJyIgPGFiZWdlbkBjaXNjby5j
b20+LAknVkFOIENBRU5FR0VNIFRvbScNCgk8VG9tLlZhbl9DYWVuZWdlbUBhbGNhdGVsLWx1Y2Vu
dC5iZT4sCSInQmlsbCBWZXIgU3RlZWcgKHZlcnN0ZWIpJyINCgk8dmVyc3RlYkBjaXNjby5jb20+
LAknWmVldiBWYXgnIDx6ZWV2dmF4QG1pY3Jvc29mdC5jb20+LCBhdnRAaWV0Zi5vcmcNCk1lc3Nh
Z2UtSUQ6IDwwMGU2MDFjOWY5NzEkNmE3YjBlODAkM2Y3MTJiODAkJXJvbmlAaHVhd2VpLmNvbT4N
CkNvbnRlbnQtVHlwZTogdGV4dC9wbGFpbjsgY2hhcnNldD11cy1hc2NpaQ0KDQpIaSBndXlzLA0K
TXkgdmlldyBpcyB0aGF0IHRoaXMgaXMgbm90IGEgZ2VuZXJhbCBOQUNLIHByb2JsZW0gYnV0IG9u
bHkgZm9yIHRoZSBjYXNlIG9mDQpTU00gYW5kIHJldHJhbnNtaXNzaW9uIHdpdGggc2ltaWxhciBi
b3ggYXJjaGl0ZWN0dXJlIHRvIHRoZSBSQU1TIHNvbHV0aW9uLg0KSWYgeW91IGhhdmUgYW5vdGhl
ciBjYXNlIHBsZWFzZSBleHBsYWluDQpSb25pDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS0NCj4gRnJvbTogYXZ0LWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzphdnQtYm91bmNlc0BpZXRm
Lm9yZ10gT24gQmVoYWxmIE9mDQo+IEFsaSBDLiBCZWdlbiAoYWJlZ2VuKQ0KPiBTZW50OiBUdWVz
ZGF5LCBKdW5lIDMwLCAyMDA5IDEwOjE5IEFNDQo+IFRvOiBWQU4gQ0FFTkVHRU0gVG9tOyBCaWxs
IFZlciBTdGVlZyAodmVyc3RlYik7IFplZXYgVmF4OyBSb25pIEV2ZW47DQo+IGF2dEBpZXRmLm9y
Zw0KPiBTdWJqZWN0OiBSZTogW0FWVF0gUG9ydCBtYXBwaW5ncywgTkFULCBhbmQgUkFNUw0KPiAN
Cj4gSGkgVG9tLA0KPiANCj4gTGV0J3MgZ2V0IHRoZSBpbnB1dCBmcm9tIHRoZSBXRyBvbiB0aGVz
ZSBwb2ludHMuIEkgYmVsaWV2ZSBnb2luZyBmb3IgYQ0KPiBtb3JlIGdlbmVyYWwgc29sdXRpb24g
dGhhdCB3aWxsIGJlIGFwcGxpY2FibGUgdG8gYm90aCBSQU1TIGFuZCBOQUNLIGlzDQo+IG1vcmUg
ZGVzaXJhYmxlLg0KPiANCj4gQlIsDQo+IC1hY2JlZ2VuDQo+IA0KPiANCj4gDQo+ID4gLS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPiBGcm9tOiBWQU4gQ0FFTkVHRU0gVG9tIFttYWlsdG86
VG9tLlZhbl9DYWVuZWdlbUBhbGNhdGVsLWx1Y2VudC5iZV0NCj4gPiBTZW50OiBNb25kYXksIEp1
bmUgMjksIDIwMDkgOToxNyBBTQ0KPiA+IFRvOiBBbGkgQy4gQmVnZW4gKGFiZWdlbik7IEJpbGwg
VmVyIFN0ZWVnICh2ZXJzdGViKTsgWmVldiBWYXg7IFJvbmkNCj4gRXZlbjsgYXZ0QGlldGYub3Jn
DQo+ID4gU3ViamVjdDogUkU6IFBvcnQgbWFwcGluZ3MsIE5BVCwgYW5kIFJBTVMNCj4gPg0KPiA+
DQo+ID4gIEFsaSwNCj4gPg0KPiA+IFNlZSBzb21lIGNvbW1lbnRzIGJlbG93IChUT00pLg0KPiA+
DQo+ID4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPiBGcm9tOiBBbGkgQy4gQmVnZW4g
KGFiZWdlbikgW21haWx0bzphYmVnZW5AY2lzY28uY29tXQ0KPiA+IFNlbnQ6IHZyaWpkYWcgMjYg
anVuaSAyMDA5IDE3OjQxDQo+ID4gVG86IFZBTiBDQUVORUdFTSBUb207IEJpbGwgVmVyIFN0ZWVn
ICh2ZXJzdGViKTsgWmVldiBWYXg7IFJvbmkgRXZlbjsNCj4gPiBhdnRAaWV0Zi5vcmcNCj4gPiBT
dWJqZWN0OiBSRTogUG9ydCBtYXBwaW5ncywgTkFULCBhbmQgUkFNUw0KPiA+DQo+ID4gSGkgVG9t
LA0KPiA+DQo+ID4gW3NuaXBdDQo+ID4gPiBUaGUgcmVhc29uIHdoeSB3ZSBuZWVkIHB1YnBvcnRz
IGlzIHRoYXQgaXQgaW5kaWNhdGVzICJleHBsaWNpdGx5Ig0KPiB0aGUNCj4gPiA+IHBvcnQgdGhl
IGNsaWVudCB3YW50cyB0byB1c2UgdG8gcmVjZWl2ZSB0aGUgYnVyc3QgaXMgdGhlIHBvcnQgaXQN
Cj4gdXNlZA0KPiA+ID4gdG8gc2VuZCB0aGUgUkFNUy1SL3B1YnBvcnRzIG1lc3NhZ2UuIEkgYmVs
aWV2ZSB3ZSBuZWVkIHRoaXMNCj4gZXhwbGljaXQNCj4gPiA+IGluZGljYXRpb24sIG93LCB3ZSB3
aWxsIGJlIG1ha2luZyBhbiBpbXBsaWNpdCBhc3N1bXB0aW9uLiBOb3RlIHRoYXQNCj4gPiA+IHRo
ZSByYW1zLXIvcHVicG9ydHMgaXMgaW4gdGhlIHByaW1hcnkgc2Vzc2lvbiBhbmQgYnVyc3QvcmV0
IHBhY2tldHMNCj4gPiA+IGFyZSBpbiB0aGUgcmV0cmFuc21pc3Npb24gc2Vzc2lvbiwgd2hpY2gg
aXMgZGlmZmVyZW50IHRoYW4gdGhlDQo+ID4gcHJpbWFyeS4NCj4gPiA+DQo+ID4gPiBBcyBmYXIg
YXMgSSBjYW4gc2VlLCBub3QgZXZlcnlib2R5IGFncmVlcyBvbiB0aGlzIHBvaW50LCBidXQgd2UN
Cj4gbmVlZA0KPiA+ID4gdG8gbWFrZSBhIGRlY2lzaW9uIGhlcmUgYmVmb3JlIHdlIG1hbmRhdGUg
YW55dGhpbmcuDQo+ID4gPg0KPiA+ID4gVE9NOiBJIGFncmVlIHdpdGggeW91ciBsYXN0IGxpbmUs
IGJ1dCBJIGRvIG5vdCBjb21wbGV0ZWx5IGFncmVlDQo+IHdoZW4NCj4gPiA+IHlvdSBtZW50aW9u
ICJpbXBsaWNpdCIgYXNzdW1wdGlvbiwgZXNwZWNpYWxseSBmb3Igb3B0aW9uIDMsIHdoZXJlDQo+
ID4gPiBSQU1TLVIgKG9yDQo+ID4gPiBOQUNLKSBhbmQgdGhlIFB1Yi1wb3J0IG1lc3NhZ2UgYXJl
IGluIHRoZSBzYW1lIGNvbXBvdW5kIG1lc3NhZ2UuIElmDQo+IHdlDQo+ID4NCj4gPiA+ICJkZWZp
bmUiIHRoYXQgaWYgbm8gcHViLXJlcG9ydCBtZXNzYWdlIGlzIHNlbnQgYnkgdGhlIFJSLCB0aGUN
Cj4gPiA+IGluZm9ybWF0aW9uIHRvd2FyZHMgdGhlIFJldHJhbnNtaXNzaW9uIHNlcnZlciBpcyBl
eGFjdGx5IHRoZSBzYW1lDQo+IGFzDQo+ID4gPiB3aGVuIGFuIFJUUCByZWNlaXZlciBzZW5kcyBh
biBSVENQIGNvbXBvdW5kIG1lc3NhZ2UgbWFkZSB1cCBvZiBhbg0KPiBSVENQDQo+ID4NCj4gPiA+
IE5BQ0svUkFNUy1SIHRvZ2V0aGVyIHdpdGggYSBwdWItcG9ydCBtZXNzYWdlIHdoZXJlIHRoZSBw
b3J0cyBhcmUNCj4gPiAiemVybyINCj4gPg0KPiA+IFdlICJtYXkiIGJlIGFibGUgdG8gc2F5IGl0
IGZyb20gUkFNUy1SIGJ1dCBub3QgZm9yIE5BQ0sgc2luY2Ugd2UgYXJlDQo+IG5vdA0KPiA+IGRl
ZmluaW5nIGl0LCB3ZSB3aWxsIGJlIG92ZXJsb2FkaW5nIGl0cyBtZWFuaW5nLCBJTU8uIEFuZCBh
cyB5b3UvQmlsbA0KPiA+IHBvaW50ZWQgb3V0IGluIG90aGVyIGVtYWlscywgSSBhbHNvIGJlbGll
dmUgdGhhdCB0aGlzIGlzIG1vcmUgZ2VuZXJhbA0KPiA+IHByb2JsZW0gdGhhbiBqdXN0IFJBTVMu
IFdlIG5lZWQgc29tZXRoaW5nIGxpa2UgcHVicG9ydHMgZm9yIE5BQ0tzIGFzDQo+ID4gd2VsbC4N
Cj4gPg0KPiA+DQo+ID4gVE9NOiBpbmRlZWQsIHRoYXQgaXMgd2h5IElNTyB3ZSBzaG91bGQgZGVm
aW5lIHRoaXMgcHJvYmxlbSBhbmQNCj4gc29sdXRpb24NCj4gPiBpbiBhIHNlcGFyYXRlIGRyYWZ0
IHdoaWNoIGFwcGxpZXMgdG8gYW55IHN5c3RlbSBhcmNoaXRlY3R1cmUgd2hlcmUgYQ0KPiA+IHVu
aWNhc3Qgc2Vzc2lvbiBmcm9tIGEgRlQgaXMgY291cGxlZCB0byBhIHNzbSBzZXNzaW9uIHdpdGgg
dGhhdCBzYW1lDQo+IEZULg0KPiA+DQo+ID4NCj4gPiA+IC1hcyBjdXJyZW50bHkgcHJvcG9zZWQg
aW4gdGhlIFJBTVMgZHJhZnQgbm93LiAgSSBhZ3JlZSB0aGF0IHRoaXMgaXMNCj4gPiA+IG5vdCB0
cnVlIGZvciBvcHRpb24gNCwgd2hlcmUgcHViLXBvcnQgYW5kIFJBTVMtUiBvciBOQUNLIGFyZQ0K
PiBzZXBhcmF0ZQ0KPiA+ID4gbWVzc2FnZXMsIGJ1dCBJIGRvIG5vdCBmYXZvdXIgdGhlIHNvbHV0
aW9uIG9mIG9wdGlvbiA0IGZvciB0aGUgc2FtZQ0KPiA+ID4gcmVhc29uIHlvdSBtZW50aW9uIGlu
IHlvdXIgcmVwbHkgKGEgbmV3IGZhaWx1cmUgbW9kZSkuIFNvLCBpZg0KPiBvcHRpb24gNA0KPiA+
DQo+ID4gPiBpcyAtZm9yIHRoYXQgcmVhc29uLSBubyBsb25nZXIgY29uc2lkZXJlZCwgSSBkbyBu
b3Qgc2VlIGEgcHJvYmxlbQ0KPiB3aXRoDQo+ID4NCj4gPiA+IGRlZmluaW5nIHRoaXMgcnVsZS9j
bGF1c2UgYXMgZXhwcmVzc2VkIGFib3ZlLiBJbiBvdGhlciB3b3JkcywgdGhlcmUNCj4gaXMNCj4g
Pg0KPiA+ID4gbm8gbmVlZCBmb3IgYSBwdWItcmVwb3J0IG1lc3NhZ2UgaW4gdGhpcyBzY2VuYXJp
byBhbmQgdGhpcyByZXN1bHRzDQo+IE5PVA0KPiA+DQo+ID4gPiBpbiBhbiAiYXNzdW1wdGlvbiIg
d2hhdC1zby1ldmVyLg0KPiA+ID4NCj4gPiA+DQo+ID4gPiA+IHN1cHBvcnRzIFJUUC9SVENQIG11
eGluZyBpdHNlbGYsIGFuZCBpZiBpdCBrbm93cyB0aGUgUlMgc3VwcG9ydHMNCj4gPiA+ID4gUlRQ
L1JUQ1AgbXV4aW5nIHRvbyAoYXMgaW5kaWNhdGVkIGluIHRoZSBkZWNsYXJhdGl2ZSBzZHAgcmVj
ZWl2ZWQNCj4gYnkNCj4gPg0KPiA+ID4gPiB0aGUNCj4gPiA+ID4gUlIpDQo+ID4gPiA+DQo+ID4g
PiA+IC1Eb24ndCB3ZSBhbHNvIGFsbG93IHRoYXQgZm9yIG9wdGlvbiAzLCB0aGUgcG9ydCBQMiBh
Y3R1YWxseQ0KPiBlcXVhbHMNCj4gPiA+ID4gcG9ydCBQND8gVGhpcyBpcyBhIGtpbmQgb2YgaHli
cmlkIG9mIHNlc3Npb24gYW5kIFNTUkMNCj4gbXVsdGlwbGV4aW5nDQo+ID4gPiA+IG9mIHRoZSBw
cmltYXJ5IG11bHRpY2FzdCBSVFAgc3RyZWFtIGFuZCB0aGUNCj4gPiA+ID4gcmV0cmFuc21pc3Np
b24vYWNjZWxlcmF0aW9uIHNlc3Npb24NCj4gPiA+ID4gOiAgb24gdGhlIHVuaWRpcmVjdGlvbmFs
IFJUUCBsYXllciwgdGhlIHByaW1hcnkgTUMgcGFja2V0cyBhbmQNCj4gdGhlDQo+ID4gPiA+IHVu
aWNhc3QgcmV0cmFuc21pc3Npb24gcGFja2V0cyBhcmUgY2xlYXJseSBzZXNzaW9uIG11eGVkLCBi
dXQgdGhlDQo+ID4gPiA+IFJUQ1ANCj4gPiA+DQo+ID4gPiA+ICJyZXR1cm4iIGNoYW5uZWwgZm9y
IGJvdGggc3RyZWFtcyBoYXZlIGV4YWN0bHkgdGhlIHNhbWUgdHJhbnNwb3J0DQo+ID4gPiA+IGFk
ZHJlc3NlcywgYnV0IGFyZSBkaXN0aW5ndWlzaGVkIGJ5IG1lYW5zIG9mIGEgZGlmZmVyZW50IFNT
UkMuDQo+IEluDQo+ID4gPiA+IHRoYXQNCj4gPiA+DQo+ID4gPiBIb3c/IFNpbmNlIFNTTSBhbmQg
cmV0cmFuc21pc3Npb24gc2Vzc2lvbnMgYXJlIHNlc3Npb24gbXV4ZWQsIHRoZXkNCj4gPiA+IGhh
dmUgdGhlIHNhbWUgU1NSQy4gV2hlbiBhIGNsaWVudCBpcyBzZW5kaW5nIGEgcmVjZWl2ZXIgcmVw
b3J0LCBob3cNCj4gZG8NCj4gPg0KPiA+ID4gd2UgaWRlbnRpZnkgd2hpY2ggc2Vzc2lvbiBpdCBi
ZWxvbmdzIHRvPyBTbywgSSBiZWxpZXZlIFAyIHNob3VsZCBiZQ0KPiA+ID4gZGlmZmVyZW50IHRo
YW4gUDQuDQo+ID4gPg0KPiA+ID4gVE9NOiB5b3UgYXJlIHJpZ2h0LiBCdXQgbm90aWNlIHRoaXM6
IFJGQyA0NTg4IG1hbmRhdGVzIHRoYXQgd2hlbg0KPiA+ID4gc2Vzc2lvbiBtdXhpbmcgaXMgdXNl
ZCBmb3IgcmV0cmFuc21pc3Npb24sIHRoYW4gdGhlIFNTUkMgc2hvdWxkIGJlDQo+IHRoZQ0KPiA+
IHNhbWUuDQo+ID4gPiBIb3dldmVyIHRoZSBSRkMgNDU4OCBkb2VzIG5vdCBnaXZlIGFyZ3VtZW50
cyB3aHkgaXQgbmVlZHMgdG8gYmUNCj4gbGlrZQ0KPiA+ID4gdGhhdC4gU28gSSBhc2sgeW91OiB3
aGF0IHdvdWxkIG9yIGNhbiBoYXBwZW4gaWYgdGhlcmUgaXMgYQ0KPiBkaWZmZXJlbnQNCj4gPiA+
IFNTUkMgdXNlZD8gIElmIHRoZXJlIGFyZSBubyBjb252aW5jaW5nIGFyZ3VtZW50cyB3aHkgd2Ug
bXVzdCBzdGljaw0KPiB0bw0KPiA+DQo+ID4gR29vZCBxdWVzdGlvbi4gSWYgd2UgZG9uJ3QgdXNl
IHRoZSBzYW1lIFNTUkMgaW4gc2Vzc2lvbi1tdXhlZCBSVFANCj4gPiBzZXNzaW9ucywgaXQgd2ls
bCBpbnRyb2R1Y2UgY29ycmVsYXRpb24gcHJvYmxlbXMuIFJlY2VpdmVyL1hSIHJlcG9ydHMNCj4g
PiBjb21pbmcgZnJvbSBhIGxhcmdlciBudW1iZXIgb2YgcmVjZWl2ZXJzIHdpbGwgYmUgZGlmZmlj
dWx0IHRvDQo+IGlkZW50aWZ5DQo+ID4gYW5kIG1hdGNoIGF0IHRoZSBzZXJ2ZXIgc2lkZS4gVGhl
cmUgd2lsbCBiZSBTU1JDIGNvbGxpc2lvbnMsIHdoaWNoDQo+IHdpbGwNCj4gPiBjb21wbGljYXRl
IHRoaW5ncyBmdXJ0aGVyLg0KPiA+DQo+ID4gVE9NOiB0aGUgYmlnIGRpZmZlcmVuY2Ugd2l0aCB3
aGVuIHRoZSBSRkMgNDU4OCB3YXMgYmVpbmcgZGlzY3Vzc2VkDQo+IGFuZA0KPiA+IGRldmVsb3Bl
ZCwgaXMgdGhhdCBub3cgd2UgYXJlIGNhcGFibGUgb2YgYWR2ZXJ0aXNpbmcgaW4gU0RQIHRoZSBT
U1JDDQo+IG9mDQo+ID4gdGhlIG1lZGlhIHNlcnZlciwgdGhhdCBpcyBpbiB0aGlzIGNhc2UgdGhl
IHJldHJhbnNtaXNzaW9uIHNlcnZlciBTU1JDDQo+ID4gdXNlZCBpbiB0aGUgcmV0cmFuc21pc3Np
b24gc2Vzc2lvbi4gSW4gZmFjdCBmb3IgUkFNUywgd2UgbmVlZCB0bw0KPiBkZWZpbmUNCj4gPiB0
aGUgU1NSQyBvZiB0aGUgc3NtIFJUUCBzZXNzaW9uLCBzbyB3ZSBjYW4gYXMgd2VsbCBkbyBpdCBm
b3IgdGhlDQo+ID4gcmV0cmFuc21pc3Npb24gc2Vzc2lvbi4gUGVyaGFwcyB3ZSBzaG91bGQgY29u
c2lkZXIgdGhpcyBkaWZmZXJlbnQNCj4gU1NSQw0KPiA+IHBvc3NpYmlsaXR5IChoZW5jZSB2aW9s
YXRpbmcgUkZDIDQ1ODgpIGFzIHBhcnQgb2YgYSBuZXcgZHJhZnQsIHRoZQ0KPiBvbmUgSQ0KPiA+
IG1lbnRpb25lZCBhYm92ZS4NCj4gPg0KPiA+DQo+ID4gPiB0aGUgc2FtZSBTU1JDLCB0aGVuLCBp
ZiB3ZSBoYXZlIGEgZ29vZCB1c2UgY2FzZSB0byBkZXBhcnQgZnJvbSB0aGF0DQo+ID4gPiAicnVs
ZSIgLWFuZCB0aGUgdXNlIGNhc2Ugd2UgYXJlIGRpc2N1c3NpbmcgaGVyZSBpcyBJTU8gaW5kZWVk
IGENCj4gdmFsaWQNCj4gPiA+IHVzZSBjYXNlLSBJIGRvIG5vdCBzZWUgd2h5IHdlIHNob3VsZCBi
ZSBsaW1pdGVkIGJ5IHN1Y2ggYSAicnVsZSIuDQo+IFRoZQ0KPiA+ID4gInZhbGlkIiB1c2UgY2Fz
ZSBpcyBoZXJlIHRoYXQgUkFNUyBhbmQgUmV0cmFuc21pc3Npb24gZm9yIFNTTQ0KPiBzZXNzaW9u
cw0KPiA+DQo+ID4gPiBvcGVyYXRlcyBmaW5lIHRocm91Z2ggYW55IE5BUFQgYW5kIHdpdGhvdXQg
YW55IGRlZGljYXRlZCBSVENQDQo+IG1lc3NhZ2UuDQo+ID4NCj4gPiAtYWNiZWdlbg0KPiBfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBBdWRpby9WaWRl
byBUcmFuc3BvcnQgV29ya2luZyBHcm91cA0KPiBhdnRAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9hdnQNCg0KDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLQ0KDQpNZXNzYWdlOiAzDQpEYXRlOiBUdWUsIDMwIEp1biAyMDA5IDA5OjEwOjI2
IC0wNDAwDQpGcm9tOiBEYXZpZCBSIE9yYW4gPG9yYW5AY2lzY28uY29tPg0KU3ViamVjdDogUmU6
IFtBVlRdIFBvcnQgbWFwcGluZ3MsIE5BVCwgYW5kIFJBTVMNClRvOiBSb25pIEV2ZW4gPEV2ZW4u
cm9uaUBodWF3ZWkuY29tPg0KQ2M6ICdWQU4gQ0FFTkVHRU0gVG9tJyA8VG9tLlZhbl9DYWVuZWdl
bUBhbGNhdGVsLWx1Y2VudC5iZT4sDQoJYXZ0QGlldGYub3JnLAkiJ0JpbGwgVmVyIFN0ZWVnIFwo
dmVyc3RlYlwpJyIgPHZlcnN0ZWJAY2lzY28uY29tPiwNCgknWmVldiBWYXgnIDx6ZWV2dmF4QG1p
Y3Jvc29mdC5jb20+DQpNZXNzYWdlLUlEOiA8ODNEMzFGN0QtOEQ0Qy00NEQxLTlBRDMtODE0QzQ3
NzY5MjJGQGNpc2NvLmNvbT4NCkNvbnRlbnQtVHlwZTogdGV4dC9wbGFpbjsgY2hhcnNldD0idXMt
YXNjaWkiOyBGb3JtYXQ9ImZsb3dlZCI7DQoJRGVsU3A9InllcyINCg0KDQpPbiBKdW4gMzAsIDIw
MDksIGF0IDY6NTUgQU0sIFJvbmkgRXZlbiB3cm90ZToNCg0KPiBIaSBndXlzLA0KPiBNeSB2aWV3
IGlzIHRoYXQgdGhpcyBpcyBub3QgYSBnZW5lcmFsIE5BQ0sgcHJvYmxlbSBidXQgb25seSBmb3Ig
dGhlICANCj4gY2FzZSBvZg0KPiBTU00gYW5kIHJldHJhbnNtaXNzaW9uIHdpdGggc2ltaWxhciBi
b3ggYXJjaGl0ZWN0dXJlIHRvIHRoZSBSQU1TICANCj4gc29sdXRpb24uDQo+IElmIHlvdSBoYXZl
IGFub3RoZXIgY2FzZSBwbGVhc2UgZXhwbGFpbg0KSSBiZWxpZXZlIGl0IGlzIGFjdHVhbGx5IGEg
TU9SRSBnZW5lcmFsIHByb2JsZW0gdGhhbiBOQUNLIG9yIFJBTVMuIEkgIA0KYXJpc2VzIGZyb20g
bWl4aW5nIFNTTSBzZXNzaW9ucyBhbmQgdW5pY2FzdCBzZXNzaW9ucyBmb3IgdGhlIHNhbWUgUlRQ
LSANCmJhc2VkIGFwcGxpY2F0aW9uLiBUaGF0J3MgYmVjYXVzZSBtdWx0aWNhc3QgZW5mb3JjZXMg
cG9ydCBzeW1tZXRyeSAgDQphbW9uZyBhbGwgdGhlIHJlY2VpdmVycyB3aGlsZSB1bmljYXN0IG5l
ZWRzIHBlci1yZWNlaXZlciBwb3J0IHNlbGVjdGlvbi4NCg0KU28gZmFyIHdlIGhhdmUgdHdvIHVz
ZXMgZm9yIG1peGluZyBtdWx0aWNhc3QgYW5kIHVuaWNhc3Q6ICANCnJldHJhbnNtaXNzaW9uLWJh
c2VkIHJlcGFpciwgYW5kIFJBTVMuIEkgc3VzcGVjdCBtb3JlIHVzZXMgd2lsbCBhcmlzZSAgDQpp
biB0aGUgZnV0dXJlLiBJIGNhbiB0aGluayBvZiBhIGZldyBvZmYgdGhlIHRvcCBvZiBteSBoZWFk
Og0KLSBjdXN0b21pemVkIHBlci11c2VyIG92ZXJsYXlzIChlLmcuIHRvIGJlIGFscGhhLWJsZW5k
ZWQgd2l0aCB0aGUgIA0KdmlkZW8pIG9yIG9iamVjdC1sZXZlbCByZXBsYWNlbWVudA0KLSBuZXR3
b3JrLWNvZGVkIGVycm9yIHJlY292ZXJ5IHN0cmVhbXMNCi0gZXh0cmEgbWVkaWEgaW5mbyBmb3Ig
cmUtaW50ZWdyYXRpb24gd2hlbiBzd2l0Y2hpbmcgYmFjayBmcm9tIHVuaWNhc3QgIA0KdG8gbXVs
dGljYXN0IGluIGEgZmFzdC1mb3J3YXJkLXRvLXJlYWx0aW1lIGNhcGFiaWxpdHkgd2hlbiBkb2lu
ZyAgDQoicGF1c2UtbGl2ZS1jb250ZW50IiBzdHlsZSBzZXJ2aWNlcw0KLSBhZGFwdGl2ZSBzd2l0
Y2hpbmcgYmV0d2VlbiBtdWx0aWNhc3QgYW5kIHVuaWNhc3QgYmFzZWQgb24gbnVtYmVyIG9mICAN
CnNpbXVsdGFuZW91cyByZWNlaXZlcnMuDQoNCkkgaGF2ZSBhIHN0cm9uZyBpbnR1aXRpb24gdGhh
dCBkb2luZyBhIGdlbmVyaWMgbWVjaGFuaXNtIHRvIGF0b21pY2FsbHkgIA0Kc2lnbmFsIHBvcnRz
IGZvciB1bmljYXN0IHNlc3Npb25zIHVzaW5nIHRoZSBSVENQIGZlZWRiYWNrIG1hY2hpbmVyeSBv
ZiAgDQp0aGUgU1NNIHNlc3Npb24gd291bGQgYmUgaGlnaGx5IGFkdmlzYWJsZS4NCg0KU28sIEkg
dGhpbms6DQphKSB3ZSBuZWVkIHRvIHNvbHZlIHRoaXMgcHJvYmxlbQ0KYikgaXQgZXhpc3RzIGV2
ZW4gaW4gdGhlIGFic2VuY2Ugb2YgTkFUcw0KYykgd2UgbmVlZCBhIGdlbmVyaWMgbWVjaGFuaXNt
DQpkKSBpdCBzaG91bGQgYmUgZG9jdW1lbnRlZCBpbiBhIHNlcGFyYXRlIGRyYWZ0LCBhbmQgbm90
IHBhcnQgb2YgUkFNcyAgDQpvciBBVlBGLg0KDQpJZiB3ZSBjYW4gYWdyZWUgdG8gdGhlc2UgcG9p
bnRzLCB0aGVuIHdlIGNhbiBoYXZlIGEgbW9yZSBkZXRhaWxlZCAgDQpkaXNjdXNzaW9uIG9mIHRo
ZSBhcHByb3ByaWF0ZSBtYWNoaW5lcnkuIEkgaGF2ZSBvcGluaW9ucyBvbiB0aGF0ICANCnN1Ympl
Y3QgdG9vLg0KDQpEYXZlTy4NCg0KDQoNCj4gUm9uaQ0KPg0KPj4gLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCj4+IEZyb206IGF2dC1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86YXZ0LWJvdW5j
ZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZg0KPj4gQWxpIEMuIEJlZ2VuIChhYmVnZW4pDQo+PiBT
ZW50OiBUdWVzZGF5LCBKdW5lIDMwLCAyMDA5IDEwOjE5IEFNDQo+PiBUbzogVkFOIENBRU5FR0VN
IFRvbTsgQmlsbCBWZXIgU3RlZWcgKHZlcnN0ZWIpOyBaZWV2IFZheDsgUm9uaSBFdmVuOw0KPj4g
YXZ0QGlldGYub3JnDQo+PiBTdWJqZWN0OiBSZTogW0FWVF0gUG9ydCBtYXBwaW5ncywgTkFULCBh
bmQgUkFNUw0KPj4NCj4+IEhpIFRvbSwNCj4+DQo+PiBMZXQncyBnZXQgdGhlIGlucHV0IGZyb20g
dGhlIFdHIG9uIHRoZXNlIHBvaW50cy4gSSBiZWxpZXZlIGdvaW5nICANCj4+IGZvciBhDQo+PiBt
b3JlIGdlbmVyYWwgc29sdXRpb24gdGhhdCB3aWxsIGJlIGFwcGxpY2FibGUgdG8gYm90aCBSQU1T
IGFuZCBOQUNLICANCj4+IGlzDQo+PiBtb3JlIGRlc2lyYWJsZS4NCj4+DQo+PiBCUiwNCj4+IC1h
Y2JlZ2VuDQo+Pg0KPj4NCj4+DQo+Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+PiBG
cm9tOiBWQU4gQ0FFTkVHRU0gVG9tIFttYWlsdG86VG9tLlZhbl9DYWVuZWdlbUBhbGNhdGVsLWx1
Y2VudC5iZV0NCj4+PiBTZW50OiBNb25kYXksIEp1bmUgMjksIDIwMDkgOToxNyBBTQ0KPj4+IFRv
OiBBbGkgQy4gQmVnZW4gKGFiZWdlbik7IEJpbGwgVmVyIFN0ZWVnICh2ZXJzdGViKTsgWmVldiBW
YXg7IFJvbmkNCj4+IEV2ZW47IGF2dEBpZXRmLm9yZw0KPj4+IFN1YmplY3Q6IFJFOiBQb3J0IG1h
cHBpbmdzLCBOQVQsIGFuZCBSQU1TDQo+Pj4NCj4+Pg0KPj4+IEFsaSwNCj4+Pg0KPj4+IFNlZSBz
b21lIGNvbW1lbnRzIGJlbG93IChUT00pLg0KPj4+DQo+Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdl
LS0tLS0NCj4+PiBGcm9tOiBBbGkgQy4gQmVnZW4gKGFiZWdlbikgW21haWx0bzphYmVnZW5AY2lz
Y28uY29tXQ0KPj4+IFNlbnQ6IHZyaWpkYWcgMjYganVuaSAyMDA5IDE3OjQxDQo+Pj4gVG86IFZB
TiBDQUVORUdFTSBUb207IEJpbGwgVmVyIFN0ZWVnICh2ZXJzdGViKTsgWmVldiBWYXg7IFJvbmkg
RXZlbjsNCj4+PiBhdnRAaWV0Zi5vcmcNCj4+PiBTdWJqZWN0OiBSRTogUG9ydCBtYXBwaW5ncywg
TkFULCBhbmQgUkFNUw0KPj4+DQo+Pj4gSGkgVG9tLA0KPj4+DQo+Pj4gW3NuaXBdDQo+Pj4+IFRo
ZSByZWFzb24gd2h5IHdlIG5lZWQgcHVicG9ydHMgaXMgdGhhdCBpdCBpbmRpY2F0ZXMgImV4cGxp
Y2l0bHkiDQo+PiB0aGUNCj4+Pj4gcG9ydCB0aGUgY2xpZW50IHdhbnRzIHRvIHVzZSB0byByZWNl
aXZlIHRoZSBidXJzdCBpcyB0aGUgcG9ydCBpdA0KPj4gdXNlZA0KPj4+PiB0byBzZW5kIHRoZSBS
QU1TLVIvcHVicG9ydHMgbWVzc2FnZS4gSSBiZWxpZXZlIHdlIG5lZWQgdGhpcw0KPj4gZXhwbGlj
aXQNCj4+Pj4gaW5kaWNhdGlvbiwgb3csIHdlIHdpbGwgYmUgbWFraW5nIGFuIGltcGxpY2l0IGFz
c3VtcHRpb24uIE5vdGUgdGhhdA0KPj4+PiB0aGUgcmFtcy1yL3B1YnBvcnRzIGlzIGluIHRoZSBw
cmltYXJ5IHNlc3Npb24gYW5kIGJ1cnN0L3JldCBwYWNrZXRzDQo+Pj4+IGFyZSBpbiB0aGUgcmV0
cmFuc21pc3Npb24gc2Vzc2lvbiwgd2hpY2ggaXMgZGlmZmVyZW50IHRoYW4gdGhlDQo+Pj4gcHJp
bWFyeS4NCj4+Pj4NCj4+Pj4gQXMgZmFyIGFzIEkgY2FuIHNlZSwgbm90IGV2ZXJ5Ym9keSBhZ3Jl
ZXMgb24gdGhpcyBwb2ludCwgYnV0IHdlDQo+PiBuZWVkDQo+Pj4+IHRvIG1ha2UgYSBkZWNpc2lv
biBoZXJlIGJlZm9yZSB3ZSBtYW5kYXRlIGFueXRoaW5nLg0KPj4+Pg0KPj4+PiBUT006IEkgYWdy
ZWUgd2l0aCB5b3VyIGxhc3QgbGluZSwgYnV0IEkgZG8gbm90IGNvbXBsZXRlbHkgYWdyZWUNCj4+
IHdoZW4NCj4+Pj4geW91IG1lbnRpb24gImltcGxpY2l0IiBhc3N1bXB0aW9uLCBlc3BlY2lhbGx5
IGZvciBvcHRpb24gMywgd2hlcmUNCj4+Pj4gUkFNUy1SIChvcg0KPj4+PiBOQUNLKSBhbmQgdGhl
IFB1Yi1wb3J0IG1lc3NhZ2UgYXJlIGluIHRoZSBzYW1lIGNvbXBvdW5kIG1lc3NhZ2UuIElmDQo+
PiB3ZQ0KPj4+DQo+Pj4+ICJkZWZpbmUiIHRoYXQgaWYgbm8gcHViLXJlcG9ydCBtZXNzYWdlIGlz
IHNlbnQgYnkgdGhlIFJSLCB0aGUNCj4+Pj4gaW5mb3JtYXRpb24gdG93YXJkcyB0aGUgUmV0cmFu
c21pc3Npb24gc2VydmVyIGlzIGV4YWN0bHkgdGhlIHNhbWUNCj4+IGFzDQo+Pj4+IHdoZW4gYW4g
UlRQIHJlY2VpdmVyIHNlbmRzIGFuIFJUQ1AgY29tcG91bmQgbWVzc2FnZSBtYWRlIHVwIG9mIGFu
DQo+PiBSVENQDQo+Pj4NCj4+Pj4gTkFDSy9SQU1TLVIgdG9nZXRoZXIgd2l0aCBhIHB1Yi1wb3J0
IG1lc3NhZ2Ugd2hlcmUgdGhlIHBvcnRzIGFyZQ0KPj4+ICJ6ZXJvIg0KPj4+DQo+Pj4gV2UgIm1h
eSIgYmUgYWJsZSB0byBzYXkgaXQgZnJvbSBSQU1TLVIgYnV0IG5vdCBmb3IgTkFDSyBzaW5jZSB3
ZSBhcmUNCj4+IG5vdA0KPj4+IGRlZmluaW5nIGl0LCB3ZSB3aWxsIGJlIG92ZXJsb2FkaW5nIGl0
cyBtZWFuaW5nLCBJTU8uIEFuZCBhcyB5b3UvIA0KPj4+IEJpbGwNCj4+PiBwb2ludGVkIG91dCBp
biBvdGhlciBlbWFpbHMsIEkgYWxzbyBiZWxpZXZlIHRoYXQgdGhpcyBpcyBtb3JlICANCj4+PiBn
ZW5lcmFsDQo+Pj4gcHJvYmxlbSB0aGFuIGp1c3QgUkFNUy4gV2UgbmVlZCBzb21ldGhpbmcgbGlr
ZSBwdWJwb3J0cyBmb3IgTkFDS3MgYXMNCj4+PiB3ZWxsLg0KPj4+DQo+Pj4NCj4+PiBUT006IGlu
ZGVlZCwgdGhhdCBpcyB3aHkgSU1PIHdlIHNob3VsZCBkZWZpbmUgdGhpcyBwcm9ibGVtIGFuZA0K
Pj4gc29sdXRpb24NCj4+PiBpbiBhIHNlcGFyYXRlIGRyYWZ0IHdoaWNoIGFwcGxpZXMgdG8gYW55
IHN5c3RlbSBhcmNoaXRlY3R1cmUgd2hlcmUgYQ0KPj4+IHVuaWNhc3Qgc2Vzc2lvbiBmcm9tIGEg
RlQgaXMgY291cGxlZCB0byBhIHNzbSBzZXNzaW9uIHdpdGggdGhhdCBzYW1lDQo+PiBGVC4NCj4+
Pg0KPj4+DQo+Pj4+IC1hcyBjdXJyZW50bHkgcHJvcG9zZWQgaW4gdGhlIFJBTVMgZHJhZnQgbm93
LiAgSSBhZ3JlZSB0aGF0IHRoaXMgaXMNCj4+Pj4gbm90IHRydWUgZm9yIG9wdGlvbiA0LCB3aGVy
ZSBwdWItcG9ydCBhbmQgUkFNUy1SIG9yIE5BQ0sgYXJlDQo+PiBzZXBhcmF0ZQ0KPj4+PiBtZXNz
YWdlcywgYnV0IEkgZG8gbm90IGZhdm91ciB0aGUgc29sdXRpb24gb2Ygb3B0aW9uIDQgZm9yIHRo
ZSBzYW1lDQo+Pj4+IHJlYXNvbiB5b3UgbWVudGlvbiBpbiB5b3VyIHJlcGx5IChhIG5ldyBmYWls
dXJlIG1vZGUpLiBTbywgaWYNCj4+IG9wdGlvbiA0DQo+Pj4NCj4+Pj4gaXMgLWZvciB0aGF0IHJl
YXNvbi0gbm8gbG9uZ2VyIGNvbnNpZGVyZWQsIEkgZG8gbm90IHNlZSBhIHByb2JsZW0NCj4+IHdp
dGgNCj4+Pg0KPj4+PiBkZWZpbmluZyB0aGlzIHJ1bGUvY2xhdXNlIGFzIGV4cHJlc3NlZCBhYm92
ZS4gSW4gb3RoZXIgd29yZHMsIHRoZXJlDQo+PiBpcw0KPj4+DQo+Pj4+IG5vIG5lZWQgZm9yIGEg
cHViLXJlcG9ydCBtZXNzYWdlIGluIHRoaXMgc2NlbmFyaW8gYW5kIHRoaXMgcmVzdWx0cw0KPj4g
Tk9UDQo+Pj4NCj4+Pj4gaW4gYW4gImFzc3VtcHRpb24iIHdoYXQtc28tZXZlci4NCj4+Pj4NCj4+
Pj4NCj4+Pj4+IHN1cHBvcnRzIFJUUC9SVENQIG11eGluZyBpdHNlbGYsIGFuZCBpZiBpdCBrbm93
cyB0aGUgUlMgc3VwcG9ydHMNCj4+Pj4+IFJUUC9SVENQIG11eGluZyB0b28gKGFzIGluZGljYXRl
ZCBpbiB0aGUgZGVjbGFyYXRpdmUgc2RwIHJlY2VpdmVkDQo+PiBieQ0KPj4+DQo+Pj4+PiB0aGUN
Cj4+Pj4+IFJSKQ0KPj4+Pj4NCj4+Pj4+IC1Eb24ndCB3ZSBhbHNvIGFsbG93IHRoYXQgZm9yIG9w
dGlvbiAzLCB0aGUgcG9ydCBQMiBhY3R1YWxseQ0KPj4gZXF1YWxzDQo+Pj4+PiBwb3J0IFA0PyBU
aGlzIGlzIGEga2luZCBvZiBoeWJyaWQgb2Ygc2Vzc2lvbiBhbmQgU1NSQw0KPj4gbXVsdGlwbGV4
aW5nDQo+Pj4+PiBvZiB0aGUgcHJpbWFyeSBtdWx0aWNhc3QgUlRQIHN0cmVhbSBhbmQgdGhlDQo+
Pj4+PiByZXRyYW5zbWlzc2lvbi9hY2NlbGVyYXRpb24gc2Vzc2lvbg0KPj4+Pj4gOiAgb24gdGhl
IHVuaWRpcmVjdGlvbmFsIFJUUCBsYXllciwgdGhlIHByaW1hcnkgTUMgcGFja2V0cyBhbmQNCj4+
IHRoZQ0KPj4+Pj4gdW5pY2FzdCByZXRyYW5zbWlzc2lvbiBwYWNrZXRzIGFyZSBjbGVhcmx5IHNl
c3Npb24gbXV4ZWQsIGJ1dCB0aGUNCj4+Pj4+IFJUQ1ANCj4+Pj4NCj4+Pj4+ICJyZXR1cm4iIGNo
YW5uZWwgZm9yIGJvdGggc3RyZWFtcyBoYXZlIGV4YWN0bHkgdGhlIHNhbWUgdHJhbnNwb3J0DQo+
Pj4+PiBhZGRyZXNzZXMsIGJ1dCBhcmUgZGlzdGluZ3Vpc2hlZCBieSBtZWFucyBvZiBhIGRpZmZl
cmVudCBTU1JDLg0KPj4gSW4NCj4+Pj4+IHRoYXQNCj4+Pj4NCj4+Pj4gSG93PyBTaW5jZSBTU00g
YW5kIHJldHJhbnNtaXNzaW9uIHNlc3Npb25zIGFyZSBzZXNzaW9uIG11eGVkLCB0aGV5DQo+Pj4+
IGhhdmUgdGhlIHNhbWUgU1NSQy4gV2hlbiBhIGNsaWVudCBpcyBzZW5kaW5nIGEgcmVjZWl2ZXIg
cmVwb3J0LCBob3cNCj4+IGRvDQo+Pj4NCj4+Pj4gd2UgaWRlbnRpZnkgd2hpY2ggc2Vzc2lvbiBp
dCBiZWxvbmdzIHRvPyBTbywgSSBiZWxpZXZlIFAyIHNob3VsZCBiZQ0KPj4+PiBkaWZmZXJlbnQg
dGhhbiBQNC4NCj4+Pj4NCj4+Pj4gVE9NOiB5b3UgYXJlIHJpZ2h0LiBCdXQgbm90aWNlIHRoaXM6
IFJGQyA0NTg4IG1hbmRhdGVzIHRoYXQgd2hlbg0KPj4+PiBzZXNzaW9uIG11eGluZyBpcyB1c2Vk
IGZvciByZXRyYW5zbWlzc2lvbiwgdGhhbiB0aGUgU1NSQyBzaG91bGQgYmUNCj4+IHRoZQ0KPj4+
IHNhbWUuDQo+Pj4+IEhvd2V2ZXIgdGhlIFJGQyA0NTg4IGRvZXMgbm90IGdpdmUgYXJndW1lbnRz
IHdoeSBpdCBuZWVkcyB0byBiZQ0KPj4gbGlrZQ0KPj4+PiB0aGF0LiBTbyBJIGFzayB5b3U6IHdo
YXQgd291bGQgb3IgY2FuIGhhcHBlbiBpZiB0aGVyZSBpcyBhDQo+PiBkaWZmZXJlbnQNCj4+Pj4g
U1NSQyB1c2VkPyAgSWYgdGhlcmUgYXJlIG5vIGNvbnZpbmNpbmcgYXJndW1lbnRzIHdoeSB3ZSBt
dXN0IHN0aWNrDQo+PiB0bw0KPj4+DQo+Pj4gR29vZCBxdWVzdGlvbi4gSWYgd2UgZG9uJ3QgdXNl
IHRoZSBzYW1lIFNTUkMgaW4gc2Vzc2lvbi1tdXhlZCBSVFANCj4+PiBzZXNzaW9ucywgaXQgd2ls
bCBpbnRyb2R1Y2UgY29ycmVsYXRpb24gcHJvYmxlbXMuIFJlY2VpdmVyL1hSICANCj4+PiByZXBv
cnRzDQo+Pj4gY29taW5nIGZyb20gYSBsYXJnZXIgbnVtYmVyIG9mIHJlY2VpdmVycyB3aWxsIGJl
IGRpZmZpY3VsdCB0bw0KPj4gaWRlbnRpZnkNCj4+PiBhbmQgbWF0Y2ggYXQgdGhlIHNlcnZlciBz
aWRlLiBUaGVyZSB3aWxsIGJlIFNTUkMgY29sbGlzaW9ucywgd2hpY2gNCj4+IHdpbGwNCj4+PiBj
b21wbGljYXRlIHRoaW5ncyBmdXJ0aGVyLg0KPj4+DQo+Pj4gVE9NOiB0aGUgYmlnIGRpZmZlcmVu
Y2Ugd2l0aCB3aGVuIHRoZSBSRkMgNDU4OCB3YXMgYmVpbmcgZGlzY3Vzc2VkDQo+PiBhbmQNCj4+
PiBkZXZlbG9wZWQsIGlzIHRoYXQgbm93IHdlIGFyZSBjYXBhYmxlIG9mIGFkdmVydGlzaW5nIGlu
IFNEUCB0aGUgU1NSQw0KPj4gb2YNCj4+PiB0aGUgbWVkaWEgc2VydmVyLCB0aGF0IGlzIGluIHRo
aXMgY2FzZSB0aGUgcmV0cmFuc21pc3Npb24gc2VydmVyICANCj4+PiBTU1JDDQo+Pj4gdXNlZCBp
biB0aGUgcmV0cmFuc21pc3Npb24gc2Vzc2lvbi4gSW4gZmFjdCBmb3IgUkFNUywgd2UgbmVlZCB0
bw0KPj4gZGVmaW5lDQo+Pj4gdGhlIFNTUkMgb2YgdGhlIHNzbSBSVFAgc2Vzc2lvbiwgc28gd2Ug
Y2FuIGFzIHdlbGwgZG8gaXQgZm9yIHRoZQ0KPj4+IHJldHJhbnNtaXNzaW9uIHNlc3Npb24uIFBl
cmhhcHMgd2Ugc2hvdWxkIGNvbnNpZGVyIHRoaXMgZGlmZmVyZW50DQo+PiBTU1JDDQo+Pj4gcG9z
c2liaWxpdHkgKGhlbmNlIHZpb2xhdGluZyBSRkMgNDU4OCkgYXMgcGFydCBvZiBhIG5ldyBkcmFm
dCwgdGhlDQo+PiBvbmUgSQ0KPj4+IG1lbnRpb25lZCBhYm92ZS4NCj4+Pg0KPj4+DQo+Pj4+IHRo
ZSBzYW1lIFNTUkMsIHRoZW4sIGlmIHdlIGhhdmUgYSBnb29kIHVzZSBjYXNlIHRvIGRlcGFydCBm
cm9tIHRoYXQNCj4+Pj4gInJ1bGUiIC1hbmQgdGhlIHVzZSBjYXNlIHdlIGFyZSBkaXNjdXNzaW5n
IGhlcmUgaXMgSU1PIGluZGVlZCBhDQo+PiB2YWxpZA0KPj4+PiB1c2UgY2FzZS0gSSBkbyBub3Qg
c2VlIHdoeSB3ZSBzaG91bGQgYmUgbGltaXRlZCBieSBzdWNoIGEgInJ1bGUiLg0KPj4gVGhlDQo+
Pj4+ICJ2YWxpZCIgdXNlIGNhc2UgaXMgaGVyZSB0aGF0IFJBTVMgYW5kIFJldHJhbnNtaXNzaW9u
IGZvciBTU00NCj4+IHNlc3Npb25zDQo+Pj4NCj4+Pj4gb3BlcmF0ZXMgZmluZSB0aHJvdWdoIGFu
eSBOQVBUIGFuZCB3aXRob3V0IGFueSBkZWRpY2F0ZWQgUlRDUA0KPj4gbWVzc2FnZS4NCj4+Pg0K
Pj4+IC1hY2JlZ2VuDQo+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KPj4gQXVkaW8vVmlkZW8gVHJhbnNwb3J0IFdvcmtpbmcgR3JvdXANCj4+IGF2dEBp
ZXRmLm9yZw0KPj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9hdnQNCj4N
Cj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gQXVk
aW8vVmlkZW8gVHJhbnNwb3J0IFdvcmtpbmcgR3JvdXANCj4gYXZ0QGlldGYub3JnDQo+IGh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vYXZ0DQoNCi0tLS0tLS0tLS0tLS0tIG5l
eHQgcGFydCAtLS0tLS0tLS0tLS0tLQ0KQSBub24tdGV4dCBhdHRhY2htZW50IHdhcyBzY3J1YmJl
ZC4uLg0KTmFtZTogUEdQLnNpZw0KVHlwZTogYXBwbGljYXRpb24vcGdwLXNpZ25hdHVyZQ0KU2l6
ZTogMTk1IGJ5dGVzDQpEZXNjOiBub3QgYXZhaWxhYmxlDQpVcmwgOiA8aHR0cDovL3d3dy5pZXRm
Lm9yZy9tYWlsLWFyY2hpdmUvd2ViL2F2dC9hdHRhY2htZW50cy8yMDA5MDYzMC85ODAyYjMwNi9h
dHRhY2htZW50LnNpZz4NCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCl9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpBdWRpby9WaWRlbyBU
cmFuc3BvcnQgV29ya2luZyBHcm91cA0KYXZ0QGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL2F2dA0KDQoNCkVuZCBvZiBhdnQgRGlnZXN0LCBWb2wgNjIsIElz
c3VlIDU5DQoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKg0K



From zeevvax@microsoft.com  Tue Jun 30 09:13:27 2009
Return-Path: <zeevvax@microsoft.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 57E083A6973 for <avt@core3.amsl.com>; Tue, 30 Jun 2009 09:13:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 iIYuODqR2w4O for <avt@core3.amsl.com>; Tue, 30 Jun 2009 09:13:23 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 034433A6767 for <avt@ietf.org>; Tue, 30 Jun 2009 09:13:22 -0700 (PDT)
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.99.4; Tue, 30 Jun 2009 09:06:45 -0700
Received: from tk5ex14mbxc105.redmond.corp.microsoft.com ([157.54.79.177]) by TK5EX14HUBC102.redmond.corp.microsoft.com ([157.54.7.154]) with mapi; Tue, 30 Jun 2009 09:06:45 -0700
From: Zeev Vax <zeevvax@microsoft.com>
To: David R Oran <oran@cisco.com>, Roni Even <Even.roni@huawei.com>
Thread-Topic: [AVT] Port mappings, NAT, and RAMS
Thread-Index: AQHJ+XGL55qnQXLLnEGrAy1spvMJMJBfirkA//+t9sA=
Date: Tue, 30 Jun 2009 16:06:44 +0000
Message-ID: <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED2A46@tk5ex14mbxc105.redmond.corp.microsoft.com>
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04137224@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54099DFD1A@xmb-sjc-215.amer.cisco.com> <"04CA D96D4C5A3 E0D54099E00C4"@xmb-sjc-215.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04186C7F@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D5409A71F22@xmb-sjc-215.amer.cisco.com> <00e601c9f971$6a7b0e80$3f712b80$%roni@huawei.com> <83D31F7D-8D4C-44D1-9AD3-814C4776922F@cisco.com>
In-Reply-To: <83D31F7D-8D4C-44D1-9AD3-814C4776922F@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 'VAN CAENEGEM Tom' <Tom.Van_Caenegem@alcatel-lucent.be>, "avt@ietf.org" <avt@ietf.org>, "'Bill Ver Steeg \(versteb\)'" <versteb@cisco.com>
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 30 Jun 2009 16:13:27 -0000

I agree this should be a separate draft and we should work on a more generi=
c mechanism.
Two comments I have, first being a general problem it might have been solve=
d already so I think we should research the area before investing in anothe=
r draft. Second given such functionality is typically part of an applicatio=
n and not staying only in the lower network layers, the application can sol=
ve it as part of the startup sequence or other data delivery mechanism it h=
as.

Zeev

-----Original Message-----
From: David R Oran [mailto:oran@cisco.com]
Sent: Tuesday, June 30, 2009 6:10 AM
To: Roni Even
Cc: 'Ali C. Begen (abegen)'; 'VAN CAENEGEM Tom'; 'Bill Ver Steeg (versteb)'=
; Zeev Vax; avt@ietf.org
Subject: Re: [AVT] Port mappings, NAT, and RAMS


On Jun 30, 2009, at 6:55 AM, Roni Even wrote:

> Hi guys,
> My view is that this is not a general NACK problem but only for the
> case of
> SSM and retransmission with similar box architecture to the RAMS
> solution.
> If you have another case please explain
I believe it is actually a MORE general problem than NACK or RAMS. I
arises from mixing SSM sessions and unicast sessions for the same RTP-
based application. That's because multicast enforces port symmetry
among all the receivers while unicast needs per-receiver port selection.

So far we have two uses for mixing multicast and unicast:
retransmission-based repair, and RAMS. I suspect more uses will arise
in the future. I can think of a few off the top of my head:
- customized per-user overlays (e.g. to be alpha-blended with the
video) or object-level replacement
- network-coded error recovery streams
- extra media info for re-integration when switching back from unicast
to multicast in a fast-forward-to-realtime capability when doing
"pause-live-content" style services
- adaptive switching between multicast and unicast based on number of
simultaneous receivers.

I have a strong intuition that doing a generic mechanism to atomically
signal ports for unicast sessions using the RTCP feedback machinery of
the SSM session would be highly advisable.

So, I think:
a) we need to solve this problem
b) it exists even in the absence of NATs
c) we need a generic mechanism
d) it should be documented in a separate draft, and not part of RAMs
or AVPF.

If we can agree to these points, then we can have a more detailed
discussion of the appropriate machinery. I have opinions on that
subject too.

DaveO.



> Roni
>
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
>> Ali C. Begen (abegen)
>> Sent: Tuesday, June 30, 2009 10:19 AM
>> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni Even;
>> avt@ietf.org
>> Subject: Re: [AVT] Port mappings, NAT, and RAMS
>>
>> Hi Tom,
>>
>> Let's get the input from the WG on these points. I believe going
>> for a
>> more general solution that will be applicable to both RAMS and NACK
>> is
>> more desirable.
>>
>> BR,
>> -acbegen
>>
>>
>>
>>> -----Original Message-----
>>> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
>>> Sent: Monday, June 29, 2009 9:17 AM
>>> To: Ali C. Begen (abegen); Bill Ver Steeg (versteb); Zeev Vax; Roni
>> Even; avt@ietf.org
>>> Subject: RE: Port mappings, NAT, and RAMS
>>>
>>>
>>> Ali,
>>>
>>> See some comments below (TOM).
>>>
>>> -----Original Message-----
>>> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
>>> Sent: vrijdag 26 juni 2009 17:41
>>> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni Even;
>>> avt@ietf.org
>>> Subject: RE: Port mappings, NAT, and RAMS
>>>
>>> Hi Tom,
>>>
>>> [snip]
>>>> The reason why we need pubports is that it indicates "explicitly"
>> the
>>>> port the client wants to use to receive the burst is the port it
>> used
>>>> to send the RAMS-R/pubports message. I believe we need this
>> explicit
>>>> indication, ow, we will be making an implicit assumption. Note that
>>>> the rams-r/pubports is in the primary session and burst/ret packets
>>>> are in the retransmission session, which is different than the
>>> primary.
>>>>
>>>> As far as I can see, not everybody agrees on this point, but we
>> need
>>>> to make a decision here before we mandate anything.
>>>>
>>>> TOM: I agree with your last line, but I do not completely agree
>> when
>>>> you mention "implicit" assumption, especially for option 3, where
>>>> RAMS-R (or
>>>> NACK) and the Pub-port message are in the same compound message. If
>> we
>>>
>>>> "define" that if no pub-report message is sent by the RR, the
>>>> information towards the Retransmission server is exactly the same
>> as
>>>> when an RTP receiver sends an RTCP compound message made up of an
>> RTCP
>>>
>>>> NACK/RAMS-R together with a pub-port message where the ports are
>>> "zero"
>>>
>>> We "may" be able to say it from RAMS-R but not for NACK since we are
>> not
>>> defining it, we will be overloading its meaning, IMO. And as you/
>>> Bill
>>> pointed out in other emails, I also believe that this is more
>>> general
>>> problem than just RAMS. We need something like pubports for NACKs as
>>> well.
>>>
>>>
>>> TOM: indeed, that is why IMO we should define this problem and
>> solution
>>> in a separate draft which applies to any system architecture where a
>>> unicast session from a FT is coupled to a ssm session with that same
>> FT.
>>>
>>>
>>>> -as currently proposed in the RAMS draft now.  I agree that this is
>>>> not true for option 4, where pub-port and RAMS-R or NACK are
>> separate
>>>> messages, but I do not favour the solution of option 4 for the same
>>>> reason you mention in your reply (a new failure mode). So, if
>> option 4
>>>
>>>> is -for that reason- no longer considered, I do not see a problem
>> with
>>>
>>>> defining this rule/clause as expressed above. In other words, there
>> is
>>>
>>>> no need for a pub-report message in this scenario and this results
>> NOT
>>>
>>>> in an "assumption" what-so-ever.
>>>>
>>>>
>>>>> supports RTP/RTCP muxing itself, and if it knows the RS supports
>>>>> RTP/RTCP muxing too (as indicated in the declarative sdp received
>> by
>>>
>>>>> the
>>>>> RR)
>>>>>
>>>>> -Don't we also allow that for option 3, the port P2 actually
>> equals
>>>>> port P4? This is a kind of hybrid of session and SSRC
>> multiplexing
>>>>> of the primary multicast RTP stream and the
>>>>> retransmission/acceleration session
>>>>> :  on the unidirectional RTP layer, the primary MC packets and
>> the
>>>>> unicast retransmission packets are clearly session muxed, but the
>>>>> RTCP
>>>>
>>>>> "return" channel for both streams have exactly the same transport
>>>>> addresses, but are distinguished by means of a different SSRC.
>> In
>>>>> that
>>>>
>>>> How? Since SSM and retransmission sessions are session muxed, they
>>>> have the same SSRC. When a client is sending a receiver report, how
>> do
>>>
>>>> we identify which session it belongs to? So, I believe P2 should be
>>>> different than P4.
>>>>
>>>> TOM: you are right. But notice this: RFC 4588 mandates that when
>>>> session muxing is used for retransmission, than the SSRC should be
>> the
>>> same.
>>>> However the RFC 4588 does not give arguments why it needs to be
>> like
>>>> that. So I ask you: what would or can happen if there is a
>> different
>>>> SSRC used?  If there are no convincing arguments why we must stick
>> to
>>>
>>> Good question. If we don't use the same SSRC in session-muxed RTP
>>> sessions, it will introduce correlation problems. Receiver/XR
>>> reports
>>> coming from a larger number of receivers will be difficult to
>> identify
>>> and match at the server side. There will be SSRC collisions, which
>> will
>>> complicate things further.
>>>
>>> TOM: the big difference with when the RFC 4588 was being discussed
>> and
>>> developed, is that now we are capable of advertising in SDP the SSRC
>> of
>>> the media server, that is in this case the retransmission server
>>> SSRC
>>> used in the retransmission session. In fact for RAMS, we need to
>> define
>>> the SSRC of the ssm RTP session, so we can as well do it for the
>>> retransmission session. Perhaps we should consider this different
>> SSRC
>>> possibility (hence violating RFC 4588) as part of a new draft, the
>> one I
>>> mentioned above.
>>>
>>>
>>>> the same SSRC, then, if we have a good use case to depart from that
>>>> "rule" -and the use case we are discussing here is IMO indeed a
>> valid
>>>> use case- I do not see why we should be limited by such a "rule".
>> The
>>>> "valid" use case is here that RAMS and Retransmission for SSM
>> sessions
>>>
>>>> operates fine through any NAPT and without any dedicated RTCP
>> message.
>>>
>>> -acbegen
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt



From Even.roni@huawei.com  Tue Jun 30 10:03:11 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CD55D3A6E84 for <avt@core3.amsl.com>; Tue, 30 Jun 2009 10:03:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 029Rk+lhxlY2 for <avt@core3.amsl.com>; Tue, 30 Jun 2009 10:03:10 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 1071A3A6E73 for <avt@ietf.org>; Tue, 30 Jun 2009 10:03:10 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KM200GSUA038B@szxga02-in.huawei.com> for avt@ietf.org; Wed, 01 Jul 2009 01:02:27 +0800 (CST)
Received: from huawei.com ([172.24.1.3]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KM200CMWA03FR@szxga02-in.huawei.com> for avt@ietf.org; Wed, 01 Jul 2009 01:02:27 +0800 (CST)
Received: from windows8d787f9 (bzq-79-180-107-118.red.bezeqint.net [79.180.107.118]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KM200MPV9ZRZF@szxml01-in.huawei.com>; Wed, 01 Jul 2009 01:02:27 +0800 (CST)
Date: Tue, 30 Jun 2009 20:01:59 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED2A46@tk5ex14mbxc105.redmond.corp.microsoft.com>
To: 'Zeev Vax' <zeevvax@microsoft.com>, 'David R Oran' <oran@cisco.com>
Message-id: <012701c9f9a4$8226e670$8674b350$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AQHJ+XGL55qnQXLLnEGrAy1spvMJMJBfirkA//+t9sCAABhAsA==
iPlanet-SMTP-Warning: Lines longer than SMTP allows found and truncated.
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04137224@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54099DFD1A@xmb-sjc-215.amer.cisco.com> <"04CA D96D4C5 C4"@xmb-sjc-215.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04186C7F@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D5409A71F22@xmb-sjc-215.amer.cisco.com> <00e601c9f971$6a7b0e80$3f712b80$%roni@huawei.com> <83D31F7D-8D4C-44D1-9AD3-814C4776922F@cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED2A46@tk5ex14mbxc105.redmond.corp.microsoft.com>
Cc: 'VAN CAENEGEM Tom' <Tom.Van_Caenegem@alcatel-lucent.be>, avt@ietf.org, "'Bill Ver Steeg \(versteb\)'" <versteb@cisco.com>
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 30 Jun 2009 17:03:11 -0000

Zeev,
I think that this is not a general problem, I am not sure that RTCP should
enable a general way to convey transport addresses, we will need to open
this to discussion. 
Dave gave some probable cases but in my view the problem exists when there
are three important conditions:

1. No negotiation between both sides, no offer/answer like in declarative
SDP.  (prevent the receiver to offer a transport address)

2. The NACK /RAMS-R is going to one address while the response is coming
from a different address (like request to Feedback target in SSM and
response (may be RTP or RTCP) from retransmission server. This will prevent
using RTP/RTCP multiplexing

3. New one way communication (Like RTP from retransmission server and no RTP
from the receiver or previous unicast RTP to this receiver (multicast with
unicast retransmission). This prevent the receiver from opening a pinhole to
the source or from the retransmission server to do SSRC multiplexing like in
unicast retransmission. This is less limiting if you use RTP/RTCP
multiplexing based on resolving of condition 2 above in a way that will
enable RTP/RTCP multiplexing.


Roni Even



> -----Original Message-----
> From: Zeev Vax [mailto:zeevvax@microsoft.com]
> Sent: Tuesday, June 30, 2009 7:07 PM
> To: David R Oran; Roni Even
> Cc: 'Ali C. Begen (abegen)'; 'VAN CAENEGEM Tom'; 'Bill Ver Steeg
> (versteb)'; avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
> 
> I agree this should be a separate draft and we should work on a more
> generic mechanism.
> Two comments I have, first being a general problem it might have been
> solved already so I think we should research the area before investing
> in another draft. Second given such functionality is typically part of
> an application and not staying only in the lower network layers, the
> application can solve it as part of the startup sequence or other data
> delivery mechanism it has.
> 
> Zeev
> 
> -----Original Message-----
> From: David R Oran [mailto:oran@cisco.com]
> Sent: Tuesday, June 30, 2009 6:10 AM
> To: Roni Even
> Cc: 'Ali C. Begen (abegen)'; 'VAN CAENEGEM Tom'; 'Bill Ver Steeg
> (versteb)'; Zeev Vax; avt@ietf.org
> Subject: Re: [AVT] Port mappings, NAT, and RAMS
> 
> 
> On Jun 30, 2009, at 6:55 AM, Roni Even wrote:
> 
> > Hi guys,
> > My view is that this is not a general NACK problem but only for the
> > case of
> > SSM and retransmission with similar box architecture to the RAMS
> > solution.
> > If you have another case please explain
> I believe it is actually a MORE general problem than NACK or RAMS. I
> arises from mixing SSM sessions and unicast sessions for the same RTP-
> based application. That's because multicast enforces port symmetry
> among all the receivers while unicast needs per-receiver port
> selection.
> 
> So far we have two uses for mixing multicast and unicast:
> retransmission-based repair, and RAMS. I suspect more uses will arise
> in the future. I can think of a few off the top of my head:
> - customized per-user overlays (e.g. to be alpha-blended with the
> video) or object-level replacement
> - network-coded error recovery streams
> - extra media info for re-integration when switching back from unicast
> to multicast in a fast-forward-to-realtime capability when doing
> "pause-live-content" style services
> - adaptive switching between multicast and unicast based on number of
> simultaneous receivers.
> 
> I have a strong intuition that doing a generic mechanism to atomically
> signal ports for unicast sessions using the RTCP feedback machinery of
> the SSM session would be highly advisable.
> 
> So, I think:
> a) we need to solve this problem
> b) it exists even in the absence of NATs
> c) we need a generic mechanism
> d) it should be documented in a separate draft, and not part of RAMs
> or AVPF.
> 
> If we can agree to these points, then we can have a more detailed
> discussion of the appropriate machinery. I have opinions on that
> subject too.
> 
> DaveO.
> 
> 
> 
> > Roni
> >
> >> -----Original Message-----
> >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
> Of
> >> Ali C. Begen (abegen)
> >> Sent: Tuesday, June 30, 2009 10:19 AM
> >> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni Even;
> >> avt@ietf.org
> >> Subject: Re: [AVT] Port mappings, NAT, and RAMS
> >>
> >> Hi Tom,
> >>
> >> Let's get the input from the WG on these points. I believe going
> >> for a
> >> more general solution that will be applicable to both RAMS and NACK
> >> is
> >> more desirable.
> >>
> >> BR,
> >> -acbegen
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> >>> Sent: Monday, June 29, 2009 9:17 AM
> >>> To: Ali C. Begen (abegen); Bill Ver Steeg (versteb); Zeev Vax; Roni
> >> Even; avt@ietf.org
> >>> Subject: RE: Port mappings, NAT, and RAMS
> >>>
> >>>
> >>> Ali,
> >>>
> >>> See some comments below (TOM).
> >>>
> >>> -----Original Message-----
> >>> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> >>> Sent: vrijdag 26 juni 2009 17:41
> >>> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni
> Even;
> >>> avt@ietf.org
> >>> Subject: RE: Port mappings, NAT, and RAMS
> >>>
> >>> Hi Tom,
> >>>
> >>> [snip]
> >>>> The reason why we need pubports is that it indicates "explicitly"
> >> the
> >>>> port the client wants to use to receive the burst is the port it
> >> used
> >>>> to send the RAMS-R/pubports message. I believe we need this
> >> explicit
> >>>> indication, ow, we will be making an implicit assumption. Note
> that
> >>>> the rams-r/pubports is in the primary session and burst/ret
> packets
> >>>> are in the retransmission session, which is different than the
> >>> primary.
> >>>>
> >>>> As far as I can see, not everybody agrees on this point, but we
> >> need
> >>>> to make a decision here before we mandate anything.
> >>>>
> >>>> TOM: I agree with your last line, but I do not completely agree
> >> when
> >>>> you mention "implicit" assumption, especially for option 3, where
> >>>> RAMS-R (or
> >>>> NACK) and the Pub-port message are in the same compound message.
> If
> >> we
> >>>
> >>>> "define" that if no pub-report message is sent by the RR, the
> >>>> information towards the Retransmission server is exactly the same
> >> as
> >>>> when an RTP receiver sends an RTCP compound message made up of an
> >> RTCP
> >>>
> >>>> NACK/RAMS-R together with a pub-port message where the ports are
> >>> "zero"
> >>>
> >>> We "may" be able to say it from RAMS-R but not for NACK since we
> are
> >> not
> >>> defining it, we will be overloading its meaning, IMO. And as you/
> >>> Bill
> >>> pointed out in other emails, I also believe that this is more
> >>> general
> >>> problem than just RAMS. We need something like pubports for NACKs
> as
> >>> well.
> >>>
> >>>
> >>> TOM: indeed, that is why IMO we should define this problem and
> >> solution
> >>> in a separate draft which applies to any system architecture where
> a
> >>> unicast session from a FT is coupled to a ssm session with that
> same
> >> FT.
> >>>
> >>>
> >>>> -as currently proposed in the RAMS draft now.  I agree that this
> is
> >>>> not true for option 4, where pub-port and RAMS-R or NACK are
> >> separate
> >>>> messages, but I do not favour the solution of option 4 for the
> same
> >>>> reason you mention in your reply (a new failure mode). So, if
> >> option 4
> >>>
> >>>> is -for that reason- no longer considered, I do not see a problem
> >> with
> >>>
> >>>> defining this rule/clause as expressed above. In other words,
> there
> >> is
> >>>
> >>>> no need for a pub-report message in this scenario and this results
> >> NOT
> >>>
> >>>> in an "assumption" what-so-ever.
> >>>>
> >>>>
> >>>>> supports RTP/RTCP muxing itself, and if it knows the RS supports
> >>>>> RTP/RTCP muxing too (as indicated in the declarative sdp received
> >> by
> >>>
> >>>>> the
> >>>>> RR)
> >>>>>
> >>>>> -Don't we also allow that for option 3, the port P2 actually
> >> equals
> >>>>> port P4? This is a kind of hybrid of session and SSRC
> >> multiplexing
> >>>>> of the primary multicast RTP stream and the
> >>>>> retransmission/acceleration session
> >>>>> :  on the unidirectional RTP layer, the primary MC packets and
> >> the
> >>>>> unicast retransmission packets are clearly session muxed, but the
> >>>>> RTCP
> >>>>
> >>>>> "return" channel for both streams have exactly the same transport
> >>>>> addresses, but are distinguished by means of a different SSRC.
> >> In
> >>>>> that
> >>>>
> >>>> How? Since SSM and retransmission sessions are session muxed, they
> >>>> have the same SSRC. When a client is sending a receiver report,
> how
> >> do
> >>>
> >>>> we identify which session it belongs to? So, I believe P2 should
> be
> >>>> different than P4.
> >>>>
> >>>> TOM: you are right. But notice this: RFC 4588 mandates that when
> >>>> session muxing is used for retransmission, than the SSRC should be
> >> the
> >>> same.
> >>>> However the RFC 4588 does not give arguments why it needs to be
> >> like
> >>>> that. So I ask you: what would or can happen if there is a
> >> different
> >>>> SSRC used?  If there are no convincing arguments why we must stick
> >> to
> >>>
> >>> Good question. If we don't use the same SSRC in session-muxed RTP
> >>> sessions, it will introduce correlation problems. Receiver/XR
> >>> reports
> >>> coming from a larger number of receivers will be difficult to
> >> identify
> >>> and match at the server side. There will be SSRC collisions, which
> >> will
> >>> complicate things further.
> >>>
> >>> TOM: the big difference with when the RFC 4588 was being discussed
> >> and
> >>> developed, is that now we are capable of advertising in SDP the
> SSRC
> >> of
> >>> the media server, that is in this case the retransmission server
> >>> SSRC
> >>> used in the retransmission session. In fact for RAMS, we need to
> >> define
> >>> the SSRC of the ssm RTP session, so we can as well do it for the
> >>> retransmission session. Perhaps we should consider this different
> >> SSRC
> >>> possibility (hence violating RFC 4588) as part of a new draft, the
> >> one I
> >>> mentioned above.
> >>>
> >>>
> >>>> the same SSRC, then, if we have a good use case to depart from
> that
> >>>> "rule" -and the use case we are discussing here is IMO indeed a
> >> valid
> >>>> use case- I do not see why we should be limited by such a "rule".
> >> The
> >>>> "valid" use case is here that RAMS and Retransmission for SSM
> >> sessions
> >>>
> >>>> operates fine through any NAPT and without any dedicated RTCP
> >> message.
> >>>
> >>> -acbegen
> >> _______________________________________________
> >> Audio/Video Transport Working Group
> >> avt@ietf.org
> >> https://www.ietf.org/mailman/listinfo/avt
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt



From versteb@cisco.com  Tue Jun 30 14:14:19 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 7FFDE3A6E7F for <avt@core3.amsl.com>; Tue, 30 Jun 2009 14:14:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.653
X-Spam-Level: 
X-Spam-Status: No, score=-6.653 tagged_above=-999 required=5 tests=[AWL=-0.054, 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 976DgFcgXrFi for <avt@core3.amsl.com>; Tue, 30 Jun 2009 14:14:18 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id A40E528C464 for <avt@ietf.org>; Tue, 30 Jun 2009 14:14:13 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,318,1243814400"; d="scan'208";a="49043110"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 30 Jun 2009 21:14:29 +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 n5ULETgH000762;  Tue, 30 Jun 2009 17:14:29 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n5ULET3c020928; Tue, 30 Jun 2009 21:14:29 GMT
Received: from xmb-rtp-21d.amer.cisco.com ([64.102.31.116]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 30 Jun 2009 17:14:29 -0400
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, 30 Jun 2009 17:14:29 -0400
Message-ID: <81B9B88E2F9D574AA5328A85547CDE91018C6ABD@xmb-rtp-21d.amer.cisco.com>
In-Reply-To: <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED2A46@tk5ex14mbxc105.redmond.corp.microsoft.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Port mappings, NAT, and RAMS
Thread-Index: AQHJ+XGL55qnQXLLnEGrAy1spvMJMJBfirkA//+t9sCAADJukA==
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04137224@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54099DFD1A@xmb-sjc-215.amer.cisco.com> <"04CA D96D4C5 A3 E0D54099E 00C4"@xmb-sjc-215.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04186C7F@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D5409A71F22@xmb-sjc-215.amer.cisco.com> <00e601c9f971$6a7b0e80$3f712b80$%roni@huawei.com> <83D31F7D-8D4C-44D1-9AD3-814C4776922F@cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED2A46@tk5ex14mbxc105.redmond.corp.microsoft.com>
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "Zeev Vax" <zeevvax@microsoft.com>, "Dave Oran (oran)" <oran@cisco.com>, "Roni Even" <Even.roni@huawei.com>
X-OriginalArrivalTime: 30 Jun 2009 21:14:29.0592 (UTC) FILETIME=[C16FFD80:01C9F9C7]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=9876; t=1246396469; x=1247260469; 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=20[AVT]=20Port=20mappings,=20NAT,=20and=2 0RAMS |Sender:=20 |To:=20=22Zeev=20Vax=22=20<zeevvax@microsoft.com>,=20=22Dav e=20Oran=20(oran)=22=20<oran@cisco.com>,=0A=20=20=20=20=20=2 0=20=20=22Roni=20Even=22=20<Even.roni@huawei.com>; bh=hJKzMR1QZk/rGKKx+nQpnkF+K2DcEBRQsOm4pyIot7s=; b=FZeGI80SzvJjIdSGAnyYXWSG+7g0lExxBbaSyS2GK09xvozVCY+c3YsNmx womKjaTjghzl6DQQXM5omTW67CvTilKYGWw4wgWxgnPFbD7EQjcwOMeK8DJf xqDKf7l9Rr;
Authentication-Results: rtp-dkim-2; header.From=versteb@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); 
Cc: VAN CAENEGEM Tom <Tom.Van_Caenegem@alcatel-lucent.be>, avt@ietf.org
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 30 Jun 2009 21:14:19 -0000

I agree that we should make a general solution for mapping unicast
sessions onto unicast sessions.=20

We need to solve this problem using data flows that will work across
multiple vendors' solutions, and thus need to do it in a standards
forum. The IETF is the correct place to do this.

Bill VerSteeg=20

-----Original Message-----
From: Zeev Vax [mailto:zeevvax@microsoft.com]=20
Sent: Tuesday, June 30, 2009 9:07 AM
To: Dave Oran (oran); Roni Even
Cc: Ali C. Begen (abegen); 'VAN CAENEGEM Tom'; Bill Ver Steeg (versteb);
avt@ietf.org
Subject: RE: [AVT] Port mappings, NAT, and RAMS

I agree this should be a separate draft and we should work on a more
generic mechanism.
Two comments I have, first being a general problem it might have been
solved already so I think we should research the area before investing
in another draft. Second given such functionality is typically part of
an application and not staying only in the lower network layers, the
application can solve it as part of the startup sequence or other data
delivery mechanism it has.

Zeev

-----Original Message-----
From: David R Oran [mailto:oran@cisco.com]
Sent: Tuesday, June 30, 2009 6:10 AM
To: Roni Even
Cc: 'Ali C. Begen (abegen)'; 'VAN CAENEGEM Tom'; 'Bill Ver Steeg
(versteb)'; Zeev Vax; avt@ietf.org
Subject: Re: [AVT] Port mappings, NAT, and RAMS


On Jun 30, 2009, at 6:55 AM, Roni Even wrote:

> Hi guys,
> My view is that this is not a general NACK problem but only for the=20
> case of SSM and retransmission with similar box architecture to the=20
> RAMS solution.
> If you have another case please explain
I believe it is actually a MORE general problem than NACK or RAMS. I
arises from mixing SSM sessions and unicast sessions for the same RTP-
based application. That's because multicast enforces port symmetry among
all the receivers while unicast needs per-receiver port selection.

So far we have two uses for mixing multicast and unicast:
retransmission-based repair, and RAMS. I suspect more uses will arise in
the future. I can think of a few off the top of my head:
- customized per-user overlays (e.g. to be alpha-blended with the
video) or object-level replacement
- network-coded error recovery streams
- extra media info for re-integration when switching back from unicast
to multicast in a fast-forward-to-realtime capability when doing
"pause-live-content" style services
- adaptive switching between multicast and unicast based on number of
simultaneous receivers.

I have a strong intuition that doing a generic mechanism to atomically
signal ports for unicast sessions using the RTCP feedback machinery of
the SSM session would be highly advisable.

So, I think:
a) we need to solve this problem
b) it exists even in the absence of NATs
c) we need a generic mechanism
d) it should be documented in a separate draft, and not part of RAMs or
AVPF.

If we can agree to these points, then we can have a more detailed
discussion of the appropriate machinery. I have opinions on that subject
too.

DaveO.



> Roni
>
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of

>> Ali C. Begen (abegen)
>> Sent: Tuesday, June 30, 2009 10:19 AM
>> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni Even;=20
>> avt@ietf.org
>> Subject: Re: [AVT] Port mappings, NAT, and RAMS
>>
>> Hi Tom,
>>
>> Let's get the input from the WG on these points. I believe going for=20
>> a more general solution that will be applicable to both RAMS and NACK

>> is more desirable.
>>
>> BR,
>> -acbegen
>>
>>
>>
>>> -----Original Message-----
>>> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
>>> Sent: Monday, June 29, 2009 9:17 AM
>>> To: Ali C. Begen (abegen); Bill Ver Steeg (versteb); Zeev Vax; Roni
>> Even; avt@ietf.org
>>> Subject: RE: Port mappings, NAT, and RAMS
>>>
>>>
>>> Ali,
>>>
>>> See some comments below (TOM).
>>>
>>> -----Original Message-----
>>> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
>>> Sent: vrijdag 26 juni 2009 17:41
>>> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni Even;

>>> avt@ietf.org
>>> Subject: RE: Port mappings, NAT, and RAMS
>>>
>>> Hi Tom,
>>>
>>> [snip]
>>>> The reason why we need pubports is that it indicates "explicitly"
>> the
>>>> port the client wants to use to receive the burst is the port it
>> used
>>>> to send the RAMS-R/pubports message. I believe we need this
>> explicit
>>>> indication, ow, we will be making an implicit assumption. Note that

>>>> the rams-r/pubports is in the primary session and burst/ret packets

>>>> are in the retransmission session, which is different than the
>>> primary.
>>>>
>>>> As far as I can see, not everybody agrees on this point, but we
>> need
>>>> to make a decision here before we mandate anything.
>>>>
>>>> TOM: I agree with your last line, but I do not completely agree
>> when
>>>> you mention "implicit" assumption, especially for option 3, where=20
>>>> RAMS-R (or
>>>> NACK) and the Pub-port message are in the same compound message. If
>> we
>>>
>>>> "define" that if no pub-report message is sent by the RR, the=20
>>>> information towards the Retransmission server is exactly the same
>> as
>>>> when an RTP receiver sends an RTCP compound message made up of an
>> RTCP
>>>
>>>> NACK/RAMS-R together with a pub-port message where the ports are
>>> "zero"
>>>
>>> We "may" be able to say it from RAMS-R but not for NACK since we are
>> not
>>> defining it, we will be overloading its meaning, IMO. And as you/=20
>>> Bill pointed out in other emails, I also believe that this is more=20
>>> general problem than just RAMS. We need something like pubports for=20
>>> NACKs as well.
>>>
>>>
>>> TOM: indeed, that is why IMO we should define this problem and
>> solution
>>> in a separate draft which applies to any system architecture where a

>>> unicast session from a FT is coupled to a ssm session with that same
>> FT.
>>>
>>>
>>>> -as currently proposed in the RAMS draft now.  I agree that this is

>>>> not true for option 4, where pub-port and RAMS-R or NACK are
>> separate
>>>> messages, but I do not favour the solution of option 4 for the same

>>>> reason you mention in your reply (a new failure mode). So, if
>> option 4
>>>
>>>> is -for that reason- no longer considered, I do not see a problem
>> with
>>>
>>>> defining this rule/clause as expressed above. In other words, there
>> is
>>>
>>>> no need for a pub-report message in this scenario and this results
>> NOT
>>>
>>>> in an "assumption" what-so-ever.
>>>>
>>>>
>>>>> supports RTP/RTCP muxing itself, and if it knows the RS supports=20
>>>>> RTP/RTCP muxing too (as indicated in the declarative sdp received
>> by
>>>
>>>>> the
>>>>> RR)
>>>>>
>>>>> -Don't we also allow that for option 3, the port P2 actually
>> equals
>>>>> port P4? This is a kind of hybrid of session and SSRC
>> multiplexing
>>>>> of the primary multicast RTP stream and the=20
>>>>> retransmission/acceleration session
>>>>> :  on the unidirectional RTP layer, the primary MC packets and
>> the
>>>>> unicast retransmission packets are clearly session muxed, but the=20
>>>>> RTCP
>>>>
>>>>> "return" channel for both streams have exactly the same transport=20
>>>>> addresses, but are distinguished by means of a different SSRC.
>> In
>>>>> that
>>>>
>>>> How? Since SSM and retransmission sessions are session muxed, they=20
>>>> have the same SSRC. When a client is sending a receiver report, how
>> do
>>>
>>>> we identify which session it belongs to? So, I believe P2 should be

>>>> different than P4.
>>>>
>>>> TOM: you are right. But notice this: RFC 4588 mandates that when=20
>>>> session muxing is used for retransmission, than the SSRC should be
>> the
>>> same.
>>>> However the RFC 4588 does not give arguments why it needs to be
>> like
>>>> that. So I ask you: what would or can happen if there is a
>> different
>>>> SSRC used?  If there are no convincing arguments why we must stick
>> to
>>>
>>> Good question. If we don't use the same SSRC in session-muxed RTP=20
>>> sessions, it will introduce correlation problems. Receiver/XR=20
>>> reports coming from a larger number of receivers will be difficult=20
>>> to
>> identify
>>> and match at the server side. There will be SSRC collisions, which
>> will
>>> complicate things further.
>>>
>>> TOM: the big difference with when the RFC 4588 was being discussed
>> and
>>> developed, is that now we are capable of advertising in SDP the SSRC
>> of
>>> the media server, that is in this case the retransmission server=20
>>> SSRC used in the retransmission session. In fact for RAMS, we need=20
>>> to
>> define
>>> the SSRC of the ssm RTP session, so we can as well do it for the=20
>>> retransmission session. Perhaps we should consider this different
>> SSRC
>>> possibility (hence violating RFC 4588) as part of a new draft, the
>> one I
>>> mentioned above.
>>>
>>>
>>>> the same SSRC, then, if we have a good use case to depart from that

>>>> "rule" -and the use case we are discussing here is IMO indeed a
>> valid
>>>> use case- I do not see why we should be limited by such a "rule".
>> The
>>>> "valid" use case is here that RAMS and Retransmission for SSM
>> sessions
>>>
>>>> operates fine through any NAPT and without any dedicated RTCP
>> message.
>>>
>>> -acbegen
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt



From versteb@cisco.com  Tue Jun 30 14:14:20 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 05F703A6CD5 for <avt@core3.amsl.com>; Tue, 30 Jun 2009 14:14:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.649
X-Spam-Level: 
X-Spam-Status: No, score=-6.649 tagged_above=-999 required=5 tests=[AWL=-0.050, 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 tSbSLYOUkyxG for <avt@core3.amsl.com>; Tue, 30 Jun 2009 14:14:18 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id CC88528C465 for <avt@ietf.org>; Tue, 30 Jun 2009 14:14:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,318,1243814400"; d="scan'208";a="334978306"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 30 Jun 2009 21:14:37 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n5ULEbaM007348;  Tue, 30 Jun 2009 14:14:37 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n5ULEauO004149; Tue, 30 Jun 2009 21:14:37 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.3959);  Tue, 30 Jun 2009 17:14:36 -0400
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, 30 Jun 2009 17:14:36 -0400
Message-ID: <81B9B88E2F9D574AA5328A85547CDE91018C6AC0@xmb-rtp-21d.amer.cisco.com>
In-Reply-To: <012701c9f9a4$8226e670$8674b350$%roni@huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Port mappings, NAT, and RAMS
Thread-Index: AQHJ+XGL55qnQXLLnEGrAy1spvMJMJBfirkA//+t9sCAABhAsIAAHDbw
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04137224@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54099DFD1A@xmb-sjc-215.amer.cisco.com> <"04CA D96D4C5 C4"@xmb-sjc -215.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04186C7F@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D5409A71F22@xmb-sjc-215.amer.cisco.com> <00e601c9f971$6a7b0e80$3f712b80$%roni@huawei.com> <83D31F7D-8D4C-44D1-9AD3-814C4776922F@cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED2A46@tk5ex14mbxc105.redmond.corp.microsoft.com> <012701c9f9a4$8226e670$8674b350$%roni@huawei.com>
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "Roni Even" <Even.roni@huawei.com>, "Zeev Vax" <zeevvax@microsoft.com>, "Dave Oran (oran)" <oran@cisco.com>
X-OriginalArrivalTime: 30 Jun 2009 21:14:36.0562 (UTC) FILETIME=[C5978720:01C9F9C7]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=12041; t=1246396477; x=1247260477; c=relaxed/simple; s=sjdkim2002; 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=20[AVT]=20Port=20mappings,=20NAT,=20and=2 0RAMS |Sender:=20; bh=o39qOQV9zct24zIE73LQbtEidoDeYcZbnuAAzlICmGI=; b=EfztVYAIFpnevdXLr9811LA0/e5wVlXkE7dEs4ePWJUZIuLOg9zQz2dLOx xbVteqofZjdJGWQlyeU1LI4F9TBaZXAwtAwsR//FL5Hnho1aMBqoVtTP7gka 3w2lFkCAyD;
Authentication-Results: sj-dkim-2; header.From=versteb@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: VAN CAENEGEM Tom <Tom.Van_Caenegem@alcatel-lucent.be>, avt@ietf.org
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 30 Jun 2009 21:14:20 -0000

Roni-

For the 2nd case, this problem also exists when the server's "request
port number" is different than the server's "response port number". This
is a very important case that breaks the port bindings in many NAT-ed
environments, and requires a standard solution.=20

Bill VerSteeg

-----Original Message-----
From: Roni Even [mailto:Even.roni@huawei.com]=20
Sent: Tuesday, June 30, 2009 10:02 AM
To: 'Zeev Vax'; Dave Oran (oran)
Cc: Ali C. Begen (abegen); 'VAN CAENEGEM Tom'; Bill Ver Steeg (versteb);
avt@ietf.org
Subject: RE: [AVT] Port mappings, NAT, and RAMS

Zeev,
I think that this is not a general problem, I am not sure that RTCP
should enable a general way to convey transport addresses, we will need
to open this to discussion.=20
Dave gave some probable cases but in my view the problem exists when
there are three important conditions:

1. No negotiation between both sides, no offer/answer like in
declarative SDP.  (prevent the receiver to offer a transport address)

2. The NACK /RAMS-R is going to one address while the response is coming
from a different address (like request to Feedback target in SSM and
response (may be RTP or RTCP) from retransmission server. This will
prevent using RTP/RTCP multiplexing

3. New one way communication (Like RTP from retransmission server and no
RTP from the receiver or previous unicast RTP to this receiver
(multicast with unicast retransmission). This prevent the receiver from
opening a pinhole to the source or from the retransmission server to do
SSRC multiplexing like in unicast retransmission. This is less limiting
if you use RTP/RTCP multiplexing based on resolving of condition 2 above
in a way that will enable RTP/RTCP multiplexing.


Roni Even



> -----Original Message-----
> From: Zeev Vax [mailto:zeevvax@microsoft.com]
> Sent: Tuesday, June 30, 2009 7:07 PM
> To: David R Oran; Roni Even
> Cc: 'Ali C. Begen (abegen)'; 'VAN CAENEGEM Tom'; 'Bill Ver Steeg=20
> (versteb)'; avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
>=20
> I agree this should be a separate draft and we should work on a more=20
> generic mechanism.
> Two comments I have, first being a general problem it might have been=20
> solved already so I think we should research the area before investing

> in another draft. Second given such functionality is typically part of

> an application and not staying only in the lower network layers, the=20
> application can solve it as part of the startup sequence or other data

> delivery mechanism it has.
>=20
> Zeev
>=20
> -----Original Message-----
> From: David R Oran [mailto:oran@cisco.com]
> Sent: Tuesday, June 30, 2009 6:10 AM
> To: Roni Even
> Cc: 'Ali C. Begen (abegen)'; 'VAN CAENEGEM Tom'; 'Bill Ver Steeg=20
> (versteb)'; Zeev Vax; avt@ietf.org
> Subject: Re: [AVT] Port mappings, NAT, and RAMS
>=20
>=20
> On Jun 30, 2009, at 6:55 AM, Roni Even wrote:
>=20
> > Hi guys,
> > My view is that this is not a general NACK problem but only for the=20
> > case of SSM and retransmission with similar box architecture to the=20
> > RAMS solution.
> > If you have another case please explain
> I believe it is actually a MORE general problem than NACK or RAMS. I=20
> arises from mixing SSM sessions and unicast sessions for the same RTP-

> based application. That's because multicast enforces port symmetry=20
> among all the receivers while unicast needs per-receiver port=20
> selection.
>=20
> So far we have two uses for mixing multicast and unicast:
> retransmission-based repair, and RAMS. I suspect more uses will arise=20
> in the future. I can think of a few off the top of my head:
> - customized per-user overlays (e.g. to be alpha-blended with the
> video) or object-level replacement
> - network-coded error recovery streams
> - extra media info for re-integration when switching back from unicast

> to multicast in a fast-forward-to-realtime capability when doing=20
> "pause-live-content" style services
> - adaptive switching between multicast and unicast based on number of=20
> simultaneous receivers.
>=20
> I have a strong intuition that doing a generic mechanism to atomically

> signal ports for unicast sessions using the RTCP feedback machinery of

> the SSM session would be highly advisable.
>=20
> So, I think:
> a) we need to solve this problem
> b) it exists even in the absence of NATs
> c) we need a generic mechanism
> d) it should be documented in a separate draft, and not part of RAMs=20
> or AVPF.
>=20
> If we can agree to these points, then we can have a more detailed=20
> discussion of the appropriate machinery. I have opinions on that=20
> subject too.
>=20
> DaveO.
>=20
>=20
>=20
> > Roni
> >
> >> -----Original Message-----
> >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
> Of
> >> Ali C. Begen (abegen)
> >> Sent: Tuesday, June 30, 2009 10:19 AM
> >> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni=20
> >> Even; avt@ietf.org
> >> Subject: Re: [AVT] Port mappings, NAT, and RAMS
> >>
> >> Hi Tom,
> >>
> >> Let's get the input from the WG on these points. I believe going=20
> >> for a more general solution that will be applicable to both RAMS=20
> >> and NACK is more desirable.
> >>
> >> BR,
> >> -acbegen
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> >>> Sent: Monday, June 29, 2009 9:17 AM
> >>> To: Ali C. Begen (abegen); Bill Ver Steeg (versteb); Zeev Vax;=20
> >>> Roni
> >> Even; avt@ietf.org
> >>> Subject: RE: Port mappings, NAT, and RAMS
> >>>
> >>>
> >>> Ali,
> >>>
> >>> See some comments below (TOM).
> >>>
> >>> -----Original Message-----
> >>> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> >>> Sent: vrijdag 26 juni 2009 17:41
> >>> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni
> Even;
> >>> avt@ietf.org
> >>> Subject: RE: Port mappings, NAT, and RAMS
> >>>
> >>> Hi Tom,
> >>>
> >>> [snip]
> >>>> The reason why we need pubports is that it indicates "explicitly"
> >> the
> >>>> port the client wants to use to receive the burst is the port it
> >> used
> >>>> to send the RAMS-R/pubports message. I believe we need this
> >> explicit
> >>>> indication, ow, we will be making an implicit assumption. Note
> that
> >>>> the rams-r/pubports is in the primary session and burst/ret
> packets
> >>>> are in the retransmission session, which is different than the
> >>> primary.
> >>>>
> >>>> As far as I can see, not everybody agrees on this point, but we
> >> need
> >>>> to make a decision here before we mandate anything.
> >>>>
> >>>> TOM: I agree with your last line, but I do not completely agree
> >> when
> >>>> you mention "implicit" assumption, especially for option 3, where

> >>>> RAMS-R (or
> >>>> NACK) and the Pub-port message are in the same compound message.
> If
> >> we
> >>>
> >>>> "define" that if no pub-report message is sent by the RR, the=20
> >>>> information towards the Retransmission server is exactly the same
> >> as
> >>>> when an RTP receiver sends an RTCP compound message made up of an
> >> RTCP
> >>>
> >>>> NACK/RAMS-R together with a pub-port message where the ports are
> >>> "zero"
> >>>
> >>> We "may" be able to say it from RAMS-R but not for NACK since we
> are
> >> not
> >>> defining it, we will be overloading its meaning, IMO. And as you/=20
> >>> Bill pointed out in other emails, I also believe that this is more

> >>> general problem than just RAMS. We need something like pubports=20
> >>> for NACKs
> as
> >>> well.
> >>>
> >>>
> >>> TOM: indeed, that is why IMO we should define this problem and
> >> solution
> >>> in a separate draft which applies to any system architecture where
> a
> >>> unicast session from a FT is coupled to a ssm session with that
> same
> >> FT.
> >>>
> >>>
> >>>> -as currently proposed in the RAMS draft now.  I agree that this
> is
> >>>> not true for option 4, where pub-port and RAMS-R or NACK are
> >> separate
> >>>> messages, but I do not favour the solution of option 4 for the
> same
> >>>> reason you mention in your reply (a new failure mode). So, if
> >> option 4
> >>>
> >>>> is -for that reason- no longer considered, I do not see a problem
> >> with
> >>>
> >>>> defining this rule/clause as expressed above. In other words,
> there
> >> is
> >>>
> >>>> no need for a pub-report message in this scenario and this=20
> >>>> results
> >> NOT
> >>>
> >>>> in an "assumption" what-so-ever.
> >>>>
> >>>>
> >>>>> supports RTP/RTCP muxing itself, and if it knows the RS supports

> >>>>> RTP/RTCP muxing too (as indicated in the declarative sdp=20
> >>>>> received
> >> by
> >>>
> >>>>> the
> >>>>> RR)
> >>>>>
> >>>>> -Don't we also allow that for option 3, the port P2 actually
> >> equals
> >>>>> port P4? This is a kind of hybrid of session and SSRC
> >> multiplexing
> >>>>> of the primary multicast RTP stream and the=20
> >>>>> retransmission/acceleration session
> >>>>> :  on the unidirectional RTP layer, the primary MC packets and
> >> the
> >>>>> unicast retransmission packets are clearly session muxed, but=20
> >>>>> the RTCP
> >>>>
> >>>>> "return" channel for both streams have exactly the same=20
> >>>>> transport addresses, but are distinguished by means of a
different SSRC.
> >> In
> >>>>> that
> >>>>
> >>>> How? Since SSM and retransmission sessions are session muxed,=20
> >>>> they have the same SSRC. When a client is sending a receiver=20
> >>>> report,
> how
> >> do
> >>>
> >>>> we identify which session it belongs to? So, I believe P2 should
> be
> >>>> different than P4.
> >>>>
> >>>> TOM: you are right. But notice this: RFC 4588 mandates that when=20
> >>>> session muxing is used for retransmission, than the SSRC should=20
> >>>> be
> >> the
> >>> same.
> >>>> However the RFC 4588 does not give arguments why it needs to be
> >> like
> >>>> that. So I ask you: what would or can happen if there is a
> >> different
> >>>> SSRC used?  If there are no convincing arguments why we must=20
> >>>> stick
> >> to
> >>>
> >>> Good question. If we don't use the same SSRC in session-muxed RTP=20
> >>> sessions, it will introduce correlation problems. Receiver/XR=20
> >>> reports coming from a larger number of receivers will be difficult

> >>> to
> >> identify
> >>> and match at the server side. There will be SSRC collisions, which
> >> will
> >>> complicate things further.
> >>>
> >>> TOM: the big difference with when the RFC 4588 was being discussed
> >> and
> >>> developed, is that now we are capable of advertising in SDP the
> SSRC
> >> of
> >>> the media server, that is in this case the retransmission server=20
> >>> SSRC used in the retransmission session. In fact for RAMS, we need

> >>> to
> >> define
> >>> the SSRC of the ssm RTP session, so we can as well do it for the=20
> >>> retransmission session. Perhaps we should consider this different
> >> SSRC
> >>> possibility (hence violating RFC 4588) as part of a new draft, the
> >> one I
> >>> mentioned above.
> >>>
> >>>
> >>>> the same SSRC, then, if we have a good use case to depart from
> that
> >>>> "rule" -and the use case we are discussing here is IMO indeed a
> >> valid
> >>>> use case- I do not see why we should be limited by such a "rule".
> >> The
> >>>> "valid" use case is here that RAMS and Retransmission for SSM
> >> sessions
> >>>
> >>>> operates fine through any NAPT and without any dedicated RTCP
> >> message.
> >>>
> >>> -acbegen
> >> _______________________________________________
> >> Audio/Video Transport Working Group avt@ietf.org=20
> >> https://www.ietf.org/mailman/listinfo/avt
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt



From csp@csperkins.org  Tue Jun 30 15:03:24 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 B360D3A6A17 for <avt@core3.amsl.com>; Tue, 30 Jun 2009 15:03:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, 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 nWlBldO7kC7S for <avt@core3.amsl.com>; Tue, 30 Jun 2009 15:03:24 -0700 (PDT)
Received: from lon1-msapost-1.mail.demon.net (lon1-msapost-1.mail.demon.net [195.173.77.180]) by core3.amsl.com (Postfix) with ESMTP id E30013A6806 for <avt@ietf.org>; Tue, 30 Jun 2009 15:03:23 -0700 (PDT)
Received: from starkperkins.demon.co.uk ([80.176.158.71] helo=[192.168.254.5]) by lon1-post-1.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1MLlQW-0005zp-Z3; Tue, 30 Jun 2009 22:03:44 +0000
Message-Id: <9E7D97BE-9350-4F7D-9866-4B2414798F1C@csperkins.org>
From: Colin Perkins <csp@csperkins.org>
To: Ali C. Begen (abegen) <abegen@cisco.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D54098D8893@xmb-sjc-215.amer.cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 30 Jun 2009 23:03:33 +0100
References: <20090309171502.518513A6359@core3.amsl.com><4A6ACB13-0CBB-4DA7-84AD-28CDE56DB4C3@csperkins.org><0MKpCa-1LoLs525qX-000cvA@mrelay.perfora.net><49D1C793.9050409@hhi.fraunhofer.de><0MKp8S-1Lof8c1LTC-000fjs@mrelay.perfora.net><49D4AE9D.8060905@hhi.fraunhofer.de><0MKpCa-1MEnZO1ysE-000d6S@mrelay.perfora.net><4A323DC5.5020004@hhi.fraunhofer.de><0MKpCa-1MGbjS2vGp-000cit@mrelay.perfora.net><C0A963AC-4B17-49FC-904C-44A43DF0B8D7@csperkins.org><0MKpCa-1MGfai3tWQ-000d7b@mrelay.perfora.net> <B5806023-20A3-4868-9195-7FA0D4D62053@csperkins.org> <04CAD96D4C5A3D48B1919248A8FE0D54098D8893@xmb-sjc-215.amer.cisco.com>
X-Mailer: Apple Mail (2.935.3)
Cc: avt@ietf.org
Subject: Re: [AVT] Fwd: I-D  Action:draft-perkins-avt-rapid-rtp-sync-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: Tue, 30 Jun 2009 22:03:24 -0000

On 17 Jun 2009, at 19:36, Ali C. Begen (abegen) wrote:
...
> Have you considered sending an SR as a part of the unicast burst (or  
> RAMS-I message that describes the burst) that we provide for rapid  
> acquisition? We may end up sending an SR this way since it will be  
> required for figuring out the extended seqnums.


That's a good idea, but something for the rapid acquisition draft to  
recommend.

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




From csp@csperkins.org  Tue Jun 30 15:12:29 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 7AA353A6C0B for <avt@core3.amsl.com>; Tue, 30 Jun 2009 15:12:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 GJlagWlabneU for <avt@core3.amsl.com>; Tue, 30 Jun 2009 15:12:27 -0700 (PDT)
Received: from anchor-msapost-2.mail.demon.net (anchor-msapost-2.mail.demon.net [195.173.77.165]) by core3.amsl.com (Postfix) with ESMTP id 07D523A695B for <avt@ietf.org>; Tue, 30 Jun 2009 15:12:27 -0700 (PDT)
Received: from starkperkins.demon.co.uk ([80.176.158.71] helo=[192.168.254.5]) by anchor-post-2.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1MLlZH-0005FU-l1; Tue, 30 Jun 2009 22:12:48 +0000
Message-Id: <AAFAF085-54E8-4FF1-968D-588A981C987B@csperkins.org>
From: Colin Perkins <csp@csperkins.org>
To: Michael A Dolan <md.1@newtbt.com>
In-Reply-To: <0MKp8S-1MH15V3qqW-000fpm@mrelay.perfora.net>
Content-Type: multipart/alternative; boundary=Apple-Mail-50--342694573
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 30 Jun 2009 23:12:41 +0100
References: <20090309171502.518513A6359@core3.amsl.com> <4A6ACB13-0CBB-4DA7-84AD-28CDE56DB4C3@csperkins.org> <0MKpCa-1LoLs525qX-000cvA@mrelay.perfora.net> <49D1C793.9050409@hhi.fraunhofer.de> <0MKp8S-1Lof8c1LTC-000fjs@mrelay.perfora.net> <49D4AE9D.8060905@hhi.fraunhofer.de> <0MKpCa-1MEnZO1ysE-000d6S@mrelay.perfora.net> <4A323DC5.5020004@hhi.fraunhofer.de> <0MKpCa-1MGbjS2vGp-000cit@mrelay.perfora.net> <C0A963AC-4B17-49FC-904C-44A43DF0B8D7@csperkins.org> <0MKpCa-1MGfai3tWQ-000d7b@mrelay.perfora.net> <B5806023-20A3-4868-9195-7FA0D4D62053@csperkins.org> <0MKp8S-1MH15V3qqW-000fpm@mrelay.perfora.net>
X-Mailer: Apple Mail (2.935.3)
Cc: avt@ietf.org
Subject: Re: [AVT] Fwd: I-D Action:draft-perkins-avt-rapid-rtp-sync-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: Tue, 30 Jun 2009 22:12:29 -0000

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

Michael,

On 17 Jun 2009, at 20:46, Michael A Dolan wrote:
> Colin-
>
> Thanks.  I think we're close.
>
> 3550 only imprecisely recommends (not requires) using a common  
> clock, and when it does, it uses the term, "wallclock", without  
> defining it.  In order for the sync to even approach the numbers  
> implied in this draft, the clocks must indeed be synchronized and  
> they must use the same timebase.  Failing to minimally recommend  
> this (even if you believe it is a restatement of 3550), it is not  
> possible to achieve the implied sync times.  I really think you need  
> to say MUST, but I leave that to you and Thomas.  And, it should be  
> tied back to NTP fields since that it is a popular source of clock.   
> Here's a suggestion:
>
>> 2.3 Clock Synchronization
>> In order to achieve more rapid and accurate sync, as recommended in  
>> RFC 3550, all senders and receivers should use a common reference  
>> clock. When NTPv4 is used, all instances of NTP packets should set  
>> the Reference ID (refid) field to the same timebase value (e.g.  
>> "GPS" - see NTPv4 Figure 12). Signaling for what Reference ID value  
>> is tp be used is accomplished out of band. When NTPv3 is used, all  
>> instances of NTP packets should use the same timebase, even if it  
>> is not explicitly signaled in the Reference ID field.
>> ==============
>> Replace all uses of "wallclock", "NTP format clock", "NTP format  
>> wallclock", etc with a single term, such as "common reference  
>> clock", to be consistent with the first use in section 1, and to  
>> remove the ambiguity of all the varying uses in the text.
>> ==============
>> Add a reference to NTPv4 (or maybe replace [7] RFC 1305?):
>> https://datatracker.ietf.org/drafts/draft-ietf-ntp-ntpv4-proto/

We can't require that senders and receivers use a common reference  
clock, or a particular clock synchronisation protocol - that's not  
realistic given the range of environments in which RTP is used - but I  
will add some text recommending that a common clock is used where  
possible.

> Regarding the access point timing, I think a note would be good  
> surrounding the tables to diffuse the implication that the 0.04  
> times in the table are realistic for an expected sync time (even if  
> good for other purposes). We all agree there are other good reasons  
> to send more frequent RTCP SR records that also improve clock  
> accuracy, and are thus directly relevant to this draft. I did not  
> mean to imply otherwise.  But I think it would be helpful to more  
> clearly separate those reasons (e.g. decoder clock stability) from  
> sync time expectations.  Let me know if you want a specific text  
> suggestion.

I added some text to section 2.2 of the -03 draft. Is that sufficient?

Cheers,
Colin





> Co-locating the RTCP SR records and the media access points is a  
> helpful recommendation, and less systemic than the above points.
>
> Thanks for considering these improvements (I think).
>
> Regards,
>
>         Mike
>
>
> At 06:57 PM 6/17/2009 +0100, Colin Perkins wrote:
>> Michael,
>>
>> On 16 Jun 2009, at 21:27, Michael A Dolan wrote:
>>> FYI, I started out in March with a number of comments, some  
>>> related to multicast UDLR with 1-2 links and I sense that's too  
>>> big a topic to try and add at this point.  My comments therefore  
>>> have distilled to addressing two major factors in syncing RTP  
>>> sessions that I believe overshadow the time resolutions being  
>>> discussed in the draft, and therefore it is an omission not to  
>>> address them:
>>>
>>> 1. Common timebase
>>> 2. Media-specific access points
>>>
>>> I stopped short of suggesting we should design anything. Therefore  
>>> I still believe both topics belong here, and in this draft, and  
>>> they are not so big as to defer at this point.
>>>
>>> For clarification, I wasn't proposing we define a timebase  
>>> signaling mechanism (although I do think that's a good idea).  All  
>>> I am proposing is to add some text that explains that a common  
>>> timebase is needed to achieve anything near the implied sync times  
>>> discussed in this draft. How the senders and receivers figure that  
>>> out is out of band. But if they don't and just go along with  
>>> "wallclock", it makes much of the rest of this draft irrelevant  
>>> since the timebase error will be huge by comparison.
>>
>> That's already stated in RFC 3550. I'm not sure it needs repeating  
>> here, but can add something if you want.
>>
>>> Regarding the issue about access points, I'm not sure how much  
>>> background to add, so apologies if this is obvious to everyone.  
>>> Every media stream type has "access points" that arrive  
>>> periodically - the point where a decoder can begin to decode the  
>>> stream. In general, these are a function of the encoding, not  
>>> constant per type, and not constant per stream. For example in H. 
>>> 264, these typically center around the presence of an IDR frame.   
>>> HE AAC has a simpler coding structure, but one still can't start  
>>> decoding anywhere in the stream.  The "typical" periods of the H. 
>>> 264 access points range from 0.5 to 2 seconds, depending on the  
>>> coding.  The exact period is application dependent, but is not  
>>> relevant.  The point is that these periods greatly exceed the  
>>> times shown in the tables which are implied to be the sync times -  
>>> going as low as 0.04 seconds.  The tables in this draft suggesting  
>>> that RTCP SR packets be sent 0.04 seconds apart for high rate  
>>> streams. This is interesting (as Thomas notes) for jitter  
>>> management and clock settling, but that high rate does not help  
>>> you sync since you can't even start decoding the video for a  
>>> relatively long time after the 0.04 seconds. This is mostly  
>>> related to issues of late joiners of course.  Therefore, I was  
>>> suggesting we make note of this fact to clarify there are other  
>>> factors to sync and acquisition beyond receipt of NTP and the RTCP  
>>> SR packet, and that these other times far exceed 0.04 seconds.
>>
>> Okay, that's what I thought you meant. That certainly affects the  
>> join times, although I'm not sure I'd call that issue  
>> synchronisation latency. We can certainly add some wording to  
>> highlight it though.
>>
>>> Co-locating in time the RTCP SR packets with their related access  
>>> points further improves the sync time.  For example, if the IDR is  
>>> every 2 seconds, there is no benefit (for syncing) to sending the  
>>> RTCP SR more frequently than that, especially if it is aligned  
>>> with this access point in time.  If the RTCP SR packets are sent  
>>> randomly in time, the sync time is the IDR period plus 1/2 the  
>>> RTCP SR packet period, on average. This is more of an  
>>> optimization, but then, that's what this whole draft is about -  
>>> optimizing the sync time.
>>
>> I agree that co-locating the SR information in time with the random  
>> access points helps, and will add something to the draft to say  
>> that explicitly if it's not already there. I disagree that's  
>> sufficient: sending the SR information more frequently gives the  
>> receiver more samples from which to estimate any skew between NTP  
>> and RTP timestamps, and gives more information to help filter out  
>> any incorrect mappings.
>>
>> -- 
>> Colin Perkins
>> http://csperkins.org/


--Apple-Mail-50--342694573
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; ">Michael,<div><br><div><div>On =
17 Jun 2009, at 20:46, Michael A Dolan wrote:</div><blockquote =
type=3D"cite"><div>Colin-<br><br> Thanks.&nbsp; I think we're =
close.<br><br> 3550 only imprecisely recommends (not requires) using a =
common clock, and when it does, it uses the term, "wallclock", without =
defining it.&nbsp; In order for the sync to even approach the numbers =
implied in this draft, the clocks must indeed be synchronized and they =
must use the same timebase.&nbsp; Failing to minimally recommend this =
(even if you believe it is a restatement of 3550), it is not possible to =
achieve the implied sync times.&nbsp; I really think you need to say =
MUST, but I leave that to you and Thomas.&nbsp; And, it should be tied =
back to NTP fields since that it is a popular source of clock.&nbsp; =
Here's a suggestion:<br><br> <blockquote type=3D"cite" class=3D"cite" =
cite=3D"">2.3 Clock Synchronization<br> In order to achieve more rapid =
and accurate sync, as recommended in RFC 3550, all senders and receivers =
should use a common reference clock. When NTPv4 is used, all instances =
of NTP packets should set the Reference ID (refid) field to the same =
timebase value (e.g. "GPS" - see NTPv4 Figure 12). Signaling for what =
Reference ID value is tp be used is accomplished out of band. When NTPv3 =
is used, all instances of NTP packets should use the same timebase, even =
if it is not explicitly signaled in the Reference ID field. <br> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br> Replace all uses of =
"wallclock", "NTP format clock", "NTP format wallclock", etc with a =
single term, such as "common reference clock", to be consistent with the =
first use in section 1, and to remove the ambiguity of all the varying =
uses in the text.<br> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br> Add =
a reference to NTPv4 (or maybe replace [7] RFC 1305?):<br> <a =
href=3D"https://datatracker.ietf.org/drafts/draft-ietf-ntp-ntpv4-proto/" =
eudora=3D"autourl"> =
https://datatracker.ietf.org/drafts/draft-ietf-ntp-ntpv4-proto/</a></block=
quote></div></blockquote><div><font class=3D"Apple-style-span" =
color=3D"#006312"><br></font></div><font class=3D"Apple-style-span" =
color=3D"#006312">We&nbsp;can't&nbsp;require =
that&nbsp;senders&nbsp;and&nbsp;receivers&nbsp;use a common reference =
clock, or a particular clock synchronisation =
protocol&nbsp;-&nbsp;that's&nbsp;not&nbsp;realistic given the range of =
environments in which RTP is used - but I will add some text =
recommending that a common clock is used where =
possible.</font></div><div><font class=3D"Apple-style-span" =
color=3D"#006312"><br></font><blockquote type=3D"cite"><div> Regarding =
the access point timing, I think a note would be good surrounding the =
tables to diffuse the implication that the 0.04 times in the table are =
realistic for an expected sync time (even if good for other purposes). =
We all agree there are other good reasons to send more frequent RTCP SR =
records that also improve clock accuracy, and are thus directly relevant =
to this draft. I did not mean to imply otherwise.&nbsp; But I think it =
would be helpful to more clearly separate those reasons (e.g. decoder =
clock stability) from sync time expectations.&nbsp; Let me know if you =
want a specific text =
suggestion.<br></div></blockquote><div><br></div>I&nbsp;added&nbsp;some&nb=
sp;text&nbsp;to&nbsp;section 2.2 of&nbsp;the&nbsp;-03&nbsp;draft. Is =
that =
sufficient?</div><div><br></div><div>Cheers,</div><div>Colin</div><div><br=
></div><div><br></div><div><br></div><div><br></div><div><br><blockquote =
type=3D"cite"><div> Co-locating the RTCP SR records and the media access =
points is a helpful recommendation, and less systemic than the above =
points.<br><br> Thanks for considering these improvements (I =
think).<br><br> Regards,<br><br> =
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Mike<br> =
<br> <br> At 06:57 PM 6/17/2009 +0100, Colin Perkins wrote:<br> =
<blockquote type=3D"cite" class=3D"cite" cite=3D"">Michael,<br><br> On =
16 Jun 2009, at 21:27, Michael A Dolan wrote:<br> <blockquote =
type=3D"cite" class=3D"cite" cite=3D"">FYI, I started out in March with =
a number of comments, some related to multicast UDLR with 1-2 links and =
I sense that's too big a topic to try and add at this point.&nbsp; My =
comments therefore have distilled to addressing two major factors in =
syncing RTP sessions that I believe overshadow the time resolutions =
being discussed in the draft, and therefore it is an omission not to =
address them:<br><br> 1. Common timebase<br> 2. Media-specific access =
points<br><br> I stopped short of suggesting we should design anything. =
Therefore I still believe both topics belong here, and in this draft, =
and they are not so big as to defer at this point.<br><br> For =
clarification, I wasn't proposing we define a timebase signaling =
mechanism (although I do think that's a good idea).&nbsp; All I am =
proposing is to add some text that explains that a common timebase is =
needed to achieve anything near the implied sync times discussed in this =
draft. How the senders and receivers figure that out is out of band. But =
if they don't and just go along with "wallclock", it makes much of the =
rest of this draft irrelevant since the timebase error will be huge by =
comparison.</blockquote><br> That's already stated in RFC 3550. I'm not =
sure it needs repeating here, but can add something if you want.<br><br> =
<blockquote type=3D"cite" class=3D"cite" cite=3D"">Regarding the issue =
about access points, I'm not sure how much background to add, so =
apologies if this is obvious to everyone. Every media stream type has =
"access points" that arrive periodically - the point where a decoder can =
begin to decode the stream. In general, these are a function of the =
encoding, not constant per type, and not constant per stream. For =
example in H.264, these typically center around the presence of an IDR =
frame.&nbsp; HE AAC has a simpler coding structure, but one still can't =
start decoding anywhere in the stream.&nbsp; The "typical" periods of =
the H.264 access points range from 0.5 to 2 seconds, depending on the =
coding.&nbsp; The exact period is application dependent, but is not =
relevant.&nbsp; The point is that these periods greatly exceed the times =
shown in the tables which are implied to be the sync times - going as =
low as 0.04 seconds.&nbsp; The tables in this draft suggesting that RTCP =
SR packets be sent 0.04 seconds apart for high rate streams. This is =
interesting (as Thomas notes) for jitter management and clock settling, =
but that high rate does not help you sync since you can't even start =
decoding the video for a relatively long time after the 0.04 seconds. =
This is mostly related to issues of late joiners of course.&nbsp; =
Therefore, I was suggesting we make note of this fact to clarify there =
are other factors to sync and acquisition beyond receipt of NTP and the =
RTCP SR packet, and that these other times far exceed 0.04 =
seconds.</blockquote><br> Okay, that's what I thought you meant. That =
certainly affects the join times, although I'm not sure I'd call that =
issue synchronisation latency. We can certainly add some wording to =
highlight it though.<br><br> <blockquote type=3D"cite" class=3D"cite" =
cite=3D"">Co-locating in time the RTCP SR packets with their related =
access points further improves the sync time.&nbsp; For example, if the =
IDR is every 2 seconds, there is no benefit (for syncing) to sending the =
RTCP SR more frequently than that, especially if it is aligned with this =
access point in time.&nbsp; If the RTCP SR packets are sent randomly in =
time, the sync time is the IDR period plus 1/2 the RTCP SR packet =
period, on average. This is more of an optimization, but then, that's =
what this whole draft is about - optimizing the sync =
time.</blockquote><br> I agree that co-locating the SR information in =
time with the random access points helps, and will add something to the =
draft to say that explicitly if it's not already there. I disagree =
that's sufficient: sending the SR information more frequently gives the =
receiver more samples from which to estimate any skew between NTP and =
RTP timestamps, and gives more information to help filter out any =
incorrect mappings.<br><br> -- <br> Colin Perkins<br> <a =
href=3D"http://csperkins.org/">http://csperkins.org/</a><br></blockquote><=
/div></blockquote></div><br></div></body></html>=

--Apple-Mail-50--342694573--

From root@core3.amsl.com  Tue Jun 30 15:15:02 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 211EB3A6EAE; Tue, 30 Jun 2009 15:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090630221502.211EB3A6EAE@core3.amsl.com>
Date: Tue, 30 Jun 2009 15:15:02 -0700 (PDT)
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-rapid-rtp-sync-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: Tue, 30 Jun 2009 22: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           : Rapid Synchronisation of RTP Flows
	Author(s)       : C. Perkins, T. Schierl
	Filename        : draft-ietf-avt-rapid-rtp-sync-03.txt
	Pages           : 22
	Date            : 2009-06-30

This memo outlines how RTP 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 synchronisation
delay.  This increase in delay can be unacceptable to some
applications that use layered and/or multi-description codecs.

This memo introduces three mechanisms to reduce the synchronisation
delay for such sessions.  First, it updates the RTP Control Protocol
(RTCP) timing rules to reduce the initial synchronisation delay for
SSM sessions.  Second, 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.  Finally,
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-ietf-avt-rapid-rtp-sync-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-rapid-rtp-sync-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From md.1@newtbt.com  Tue Jun 30 15:47:40 2009
Return-Path: <md.1@newtbt.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 E92873A69DC for <avt@core3.amsl.com>; Tue, 30 Jun 2009 15:47:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.202
X-Spam-Level: 
X-Spam-Status: No, score=-1.202 tagged_above=-999 required=5 tests=[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 sXNkWIIMafya for <avt@core3.amsl.com>; Tue, 30 Jun 2009 15:47:39 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id D4F1928C3F0 for <avt@ietf.org>; Tue, 30 Jun 2009 15:47:38 -0700 (PDT)
Received: from TBT-Laptop.newtbt.com ([209.77.27.72]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MKp8S-1MLm0o07oT-000SlS; Tue, 30 Jun 2009 18:41:26 -0400
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 30 Jun 2009 15:41:10 -0700
To: avt@ietf.org
From: Michael A Dolan <md.1@newtbt.com>
In-Reply-To: <AAFAF085-54E8-4FF1-968D-588A981C987B@csperkins.org>
References: <20090309171502.518513A6359@core3.amsl.com> <4A6ACB13-0CBB-4DA7-84AD-28CDE56DB4C3@csperkins.org> <0MKpCa-1LoLs525qX-000cvA@mrelay.perfora.net> <49D1C793.9050409@hhi.fraunhofer.de> <0MKp8S-1Lof8c1LTC-000fjs@mrelay.perfora.net> <49D4AE9D.8060905@hhi.fraunhofer.de> <0MKpCa-1MEnZO1ysE-000d6S@mrelay.perfora.net> <4A323DC5.5020004@hhi.fraunhofer.de> <0MKpCa-1MGbjS2vGp-000cit@mrelay.perfora.net> <C0A963AC-4B17-49FC-904C-44A43DF0B8D7@csperkins.org> <0MKpCa-1MGfai3tWQ-000d7b@mrelay.perfora.net> <B5806023-20A3-4868-9195-7FA0D4D62053@csperkins.org> <0MKp8S-1MH15V3qqW-000fpm@mrelay.perfora.net> <AAFAF085-54E8-4FF1-968D-588A981C987B@csperkins.org>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_764347546==.ALT"
Message-Id: <0MKp8S-1MLm0o07oT-000SlS@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX1/jiSaZCAvBR6nhWrIKQwKbJOBmLh3T8y7cl+W e52ahJq0SY7HZmeBhZUqII2+sVVSGR42RBihTp5qRt1EDUH1fJ 1LRmAC6l2j/Z3zzwAeb5A==
Subject: Re: [AVT] Fwd: I-D  Action:draft-perkins-avt-rapid-rtp-sync-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: Tue, 30 Jun 2009 22:47:41 -0000

--=====================_764347546==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

Colin-

I thought I was very careful to use "should" in my proposed reference 
clock language, and thus it is a recommendation and not 
required.  So, I am not sure I understand your comment below. If you 
prefer, "It is recommended....", that's fine of course.  But I do 
think we need to be much clearer that a common timebase is really 
important for sync.

I'll look at -03 "soon" and reply.

Thanks,

         Mike

At 11:12 PM 6/30/2009 +0100, Colin Perkins wrote:
>Michael,
>
>On 17 Jun 2009, at 20:46, Michael A Dolan wrote:
>>Colin-
>>
>>Thanks.  I think we're close.
>>
>>3550 only imprecisely recommends (not requires) using a common 
>>clock, and when it does, it uses the term, "wallclock", without 
>>defining it.  In order for the sync to even approach the numbers 
>>implied in this draft, the clocks must indeed be synchronized and 
>>they must use the same timebase.  Failing to minimally recommend 
>>this (even if you believe it is a restatement of 3550), it is not 
>>possible to achieve the implied sync times.  I really think you 
>>need to say MUST, but I leave that to you and Thomas.  And, it 
>>should be tied back to NTP fields since that it is a popular source 
>>of clock.  Here's a suggestion:
>>
>>>2.3 Clock Synchronization
>>>In order to achieve more rapid and accurate sync, as recommended 
>>>in RFC 3550, all senders and receivers should use a common 
>>>reference clock. When NTPv4 is used, all instances of NTP packets 
>>>should set the Reference ID (refid) field to the same timebase 
>>>value (e.g. "GPS" - see NTPv4 Figure 12). Signaling for what 
>>>Reference ID value is tp be used is accomplished out of band. When 
>>>NTPv3 is used, all instances of NTP packets should use the same 
>>>timebase, even if it is not explicitly signaled in the Reference ID field.
>>>==============
>>>Replace all uses of "wallclock", "NTP format clock", "NTP format 
>>>wallclock", etc with a single term, such as "common reference 
>>>clock", to be consistent with the first use in section 1, and to 
>>>remove the ambiguity of all the varying uses in the text.
>>>==============
>>>Add a reference to NTPv4 (or maybe replace [7] RFC 1305?):
>>>https://datatracker.ietf.org/drafts/draft-ietf-ntp-ntpv4-proto/
>
>We can't require that senders and receivers use a common reference 
>clock, or a particular clock synchronisation protocol - that's not 
>realistic given the range of environments in which RTP is used - but 
>I will add some text recommending that a common clock is used where possible.
>
>>Regarding the access point timing, I think a note would be good 
>>surrounding the tables to diffuse the implication that the 0.04 
>>times in the table are realistic for an expected sync time (even if 
>>good for other purposes). We all agree there are other good reasons 
>>to send more frequent RTCP SR records that also improve clock 
>>accuracy, and are thus directly relevant to this draft. I did not 
>>mean to imply otherwise.  But I think it would be helpful to more 
>>clearly separate those reasons (e.g. decoder clock stability) from 
>>sync time expectations.  Let me know if you want a specific text suggestion.
>
>I added some text to section 2.2 of the -03 draft. Is that sufficient?
>
>Cheers,
>Colin
>
>
>
>
>
>>Co-locating the RTCP SR records and the media access points is a 
>>helpful recommendation, and less systemic than the above points.
>>
>>Thanks for considering these improvements (I think).
>>
>>Regards,
>>
>>         Mike
>>
>>
>>At 06:57 PM 6/17/2009 +0100, Colin Perkins wrote:
>>>Michael,
>>>
>>>On 16 Jun 2009, at 21:27, Michael A Dolan wrote:
>>>>FYI, I started out in March with a number of comments, some 
>>>>related to multicast UDLR with 1-2 links and I sense that's too 
>>>>big a topic to try and add at this point.  My comments therefore 
>>>>have distilled to addressing two major factors in syncing RTP 
>>>>sessions that I believe overshadow the time resolutions being 
>>>>discussed in the draft, and therefore it is an omission not to address them:
>>>>
>>>>1. Common timebase
>>>>2. Media-specific access points
>>>>
>>>>I stopped short of suggesting we should design anything. 
>>>>Therefore I still believe both topics belong here, and in this 
>>>>draft, and they are not so big as to defer at this point.
>>>>
>>>>For clarification, I wasn't proposing we define a timebase 
>>>>signaling mechanism (although I do think that's a good 
>>>>idea).  All I am proposing is to add some text that explains that 
>>>>a common timebase is needed to achieve anything near the implied 
>>>>sync times discussed in this draft. How the senders and receivers 
>>>>figure that out is out of band. But if they don't and just go 
>>>>along with "wallclock", it makes much of the rest of this draft 
>>>>irrelevant since the timebase error will be huge by comparison.
>>>
>>>That's already stated in RFC 3550. I'm not sure it needs repeating 
>>>here, but can add something if you want.
>>>
>>>>Regarding the issue about access points, I'm not sure how much 
>>>>background to add, so apologies if this is obvious to everyone. 
>>>>Every media stream type has "access points" that arrive 
>>>>periodically - the point where a decoder can begin to decode the 
>>>>stream. In general, these are a function of the encoding, not 
>>>>constant per type, and not constant per stream. For example in 
>>>>H.264, these typically center around the presence of an IDR 
>>>>frame.  HE AAC has a simpler coding structure, but one still 
>>>>can't start decoding anywhere in the stream.  The "typical" 
>>>>periods of the H.264 access points range from 0.5 to 2 seconds, 
>>>>depending on the coding.  The exact period is application 
>>>>dependent, but is not relevant.  The point is that these periods 
>>>>greatly exceed the times shown in the tables which are implied to 
>>>>be the sync times - going as low as 0.04 seconds.  The tables in 
>>>>this draft suggesting that RTCP SR packets be sent 0.04 seconds 
>>>>apart for high rate streams. This is interesting (as Thomas 
>>>>notes) for jitter management and clock settling, but that high 
>>>>rate does not help you sync since you can't even start decoding 
>>>>the video for a relatively long time after the 0.04 seconds. This 
>>>>is mostly related to issues of late joiners of 
>>>>course.  Therefore, I was suggesting we make note of this fact to 
>>>>clarify there are other factors to sync and acquisition beyond 
>>>>receipt of NTP and the RTCP SR packet, and that these other times 
>>>>far exceed 0.04 seconds.
>>>
>>>Okay, that's what I thought you meant. That certainly affects the 
>>>join times, although I'm not sure I'd call that issue 
>>>synchronisation latency. We can certainly add some wording to 
>>>highlight it though.
>>>
>>>>Co-locating in time the RTCP SR packets with their related access 
>>>>points further improves the sync time.  For example, if the IDR 
>>>>is every 2 seconds, there is no benefit (for syncing) to sending 
>>>>the RTCP SR more frequently than that, especially if it is 
>>>>aligned with this access point in time.  If the RTCP SR packets 
>>>>are sent randomly in time, the sync time is the IDR period plus 
>>>>1/2 the RTCP SR packet period, on average. This is more of an 
>>>>optimization, but then, that's what this whole draft is about - 
>>>>optimizing the sync time.
>>>
>>>I agree that co-locating the SR information in time with the 
>>>random access points helps, and will add something to the draft to 
>>>say that explicitly if it's not already there. I disagree that's 
>>>sufficient: sending the SR information more frequently gives the 
>>>receiver more samples from which to estimate any skew between NTP 
>>>and RTP timestamps, and gives more information to help filter out 
>>>any incorrect mappings.
>>>
>>>--
>>>Colin Perkins
>>><http://csperkins.org/>http://csperkins.org/

--=====================_764347546==.ALT
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<body>
Colin-<br><br>
I thought I was very careful to use &quot;should&quot; in my proposed
reference clock language, and thus it is a recommendation and not
required.&nbsp; So, I am not sure I understand your comment below. If you
prefer, &quot;It is recommended....&quot;, that's fine of course.&nbsp;
But I do think we need to be much clearer that a common timebase is
really important for sync.<br><br>
I'll look at -03 &quot;soon&quot; and reply.<br><br>
Thanks,<br><br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Mike<br>
<br>
At 11:12 PM 6/30/2009 +0100, Colin Perkins wrote:<br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Michael,<br><br>
On 17 Jun 2009, at 20:46, Michael A Dolan wrote:<br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Colin-<br><br>
Thanks.&nbsp; I think we're close.<br><br>
3550 only imprecisely recommends (not requires) using a common clock, and
when it does, it uses the term, &quot;wallclock&quot;, without defining
it.&nbsp; In order for the sync to even approach the numbers implied in
this draft, the clocks must indeed be synchronized and they must use the
same timebase.&nbsp; Failing to minimally recommend this (even if you
believe it is a restatement of 3550), it is not possible to achieve the
implied sync times.&nbsp; I really think you need to say MUST, but I
leave that to you and Thomas.&nbsp; And, it should be tied back to NTP
fields since that it is a popular source of clock.&nbsp; Here's a
suggestion:<br><br>
<blockquote type=3Dcite class=3Dcite cite=3D"">2.3 Clock Synchronization<br>
In order to achieve more rapid and accurate sync, as recommended in RFC
3550, all senders and receivers should use a common reference clock. When
NTPv4 is used, all instances of NTP packets should set the Reference ID
(refid) field to the same timebase value (e.g. &quot;GPS&quot; - see
NTPv4 Figure 12). Signaling for what Reference ID value is tp be used is
accomplished out of band. When NTPv3 is used, all instances of NTP
packets should use the same timebase, even if it is not explicitly
signaled in the Reference ID field. <br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
Replace all uses of &quot;wallclock&quot;, &quot;NTP format clock&quot;,
&quot;NTP format wallclock&quot;, etc with a single term, such as
&quot;common reference clock&quot;, to be consistent with the first use
in section 1, and to remove the ambiguity of all the varying uses in the
text.<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
Add a reference to NTPv4 (or maybe replace [7] RFC 1305?):<br>
<a href=3D"https://datatracker.ietf.org/drafts/draft-ietf-ntp-ntpv4-proto/" =
eudora=3D"autourl">
https://datatracker.ietf.org/drafts/draft-ietf-ntp-ntpv4-proto/</a>
</blockquote></blockquote><font color=3D"#006312"><br>
We can't require that senders and receivers use a common reference clock,
or a particular clock synchronisation protocol - that's not realistic
given the range of environments in which RTP is used - but I will add
some text recommending that a common clock is used where
possible.<br><br>
</font><blockquote type=3Dcite class=3Dcite cite=3D"">Regarding the access
point timing, I think a note would be good surrounding the tables to
diffuse the implication that the 0.04 times in the table are realistic
for an expected sync time (even if good for other purposes). We all agree
there are other good reasons to send more frequent RTCP SR records that
also improve clock accuracy, and are thus directly relevant to this
draft. I did not mean to imply otherwise.&nbsp; But I think it would be
helpful to more clearly separate those reasons (e.g. decoder clock
stability) from sync time expectations.&nbsp; Let me know if you want a
specific text suggestion.</blockquote><br>
I added some text to section 2.2 of the -03 draft. Is that
sufficient?<br><br>
Cheers,<br>
Colin<br><br>
<br><br>
<br><br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Co-locating the RTCP SR recor=
ds
and the media access points is a helpful recommendation, and less
systemic than the above points.<br><br>
Thanks for considering these improvements (I think).<br><br>
Regards,<br><br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Mike<br>
<br>
<br>
At 06:57 PM 6/17/2009 +0100, Colin Perkins wrote:<br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Michael,<br><br>
On 16 Jun 2009, at 21:27, Michael A Dolan wrote:<br>
<blockquote type=3Dcite class=3Dcite cite=3D"">FYI, I started out in March w=
ith
a number of comments, some related to multicast UDLR with 1-2 links and I
sense that's too big a topic to try and add at this point.&nbsp; My
comments therefore have distilled to addressing two major factors in
syncing RTP sessions that I believe overshadow the time resolutions being
discussed in the draft, and therefore it is an omission not to address
them:<br><br>
1. Common timebase<br>
2. Media-specific access points<br><br>
I stopped short of suggesting we should design anything. Therefore I
still believe both topics belong here, and in this draft, and they are
not so big as to defer at this point.<br><br>
For clarification, I wasn't proposing we define a timebase signaling
mechanism (although I do think that's a good idea).&nbsp; All I am
proposing is to add some text that explains that a common timebase is
needed to achieve anything near the implied sync times discussed in this
draft. How the senders and receivers figure that out is out of band. But
if they don't and just go along with &quot;wallclock&quot;, it makes much
of the rest of this draft irrelevant since the timebase error will be
huge by comparison.</blockquote><br>
That's already stated in RFC 3550. I'm not sure it needs repeating here,
but can add something if you want.<br><br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Regarding the issue about acc=
ess
points, I'm not sure how much background to add, so apologies if this is
obvious to everyone. Every media stream type has &quot;access
points&quot; that arrive periodically - the point where a decoder can
begin to decode the stream. In general, these are a function of the
encoding, not constant per type, and not constant per stream. For example
in H.264, these typically center around the presence of an IDR
frame.&nbsp; HE AAC has a simpler coding structure, but one still can't
start decoding anywhere in the stream.&nbsp; The &quot;typical&quot;
periods of the H.264 access points range from 0.5 to 2 seconds, depending
on the coding.&nbsp; The exact period is application dependent, but is
not relevant.&nbsp; The point is that these periods greatly exceed the
times shown in the tables which are implied to be the sync times - going
as low as 0.04 seconds.&nbsp; The tables in this draft suggesting that
RTCP SR packets be sent 0.04 seconds apart for high rate streams. This is
interesting (as Thomas notes) for jitter management and clock settling,
but that high rate does not help you sync since you can't even start
decoding the video for a relatively long time after the 0.04 seconds.
This is mostly related to issues of late joiners of course.&nbsp;
Therefore, I was suggesting we make note of this fact to clarify there
are other factors to sync and acquisition beyond receipt of NTP and the
RTCP SR packet, and that these other times far exceed 0.04
seconds.</blockquote><br>
Okay, that's what I thought you meant. That certainly affects the join
times, although I'm not sure I'd call that issue synchronisation latency.
We can certainly add some wording to highlight it though.<br><br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Co-locating in time the RTCP =
SR
packets with their related access points further improves the sync
time.&nbsp; For example, if the IDR is every 2 seconds, there is no
benefit (for syncing) to sending the RTCP SR more frequently than that,
especially if it is aligned with this access point in time.&nbsp; If the
RTCP SR packets are sent randomly in time, the sync time is the IDR
period plus 1/2 the RTCP SR packet period, on average. This is more of an
optimization, but then, that's what this whole draft is about -
optimizing the sync time.</blockquote><br>
I agree that co-locating the SR information in time with the random
access points helps, and will add something to the draft to say that
explicitly if it's not already there. I disagree that's sufficient:
sending the SR information more frequently gives the receiver more
samples from which to estimate any skew between NTP and RTP timestamps,
and gives more information to help filter out any incorrect
mappings.<br><br>
-- <br>
Colin Perkins<br>
<a href=3D"http://csperkins.org/">http://csperkins.org/</a></blockquote>
</blockquote></blockquote></body>
</html>

--=====================_764347546==.ALT--


From zeevvax@microsoft.com  Tue Jun 30 18:12:49 2009
Return-Path: <zeevvax@microsoft.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 0445528C3AE for <avt@core3.amsl.com>; Tue, 30 Jun 2009 18:12:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 IKT5ECEboIgX for <avt@core3.amsl.com>; Tue, 30 Jun 2009 18:12:47 -0700 (PDT)
Received: from smtp.microsoft.com (mail2.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 781E63A65A6 for <avt@ietf.org>; Tue, 30 Jun 2009 18:12:47 -0700 (PDT)
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (157.54.79.159) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.99.4; Tue, 30 Jun 2009 18:13:08 -0700
Received: from tk5ex14mbxc105.redmond.corp.microsoft.com ([157.54.79.177]) by TK5EX14MLTC104.redmond.corp.microsoft.com ([157.54.79.159]) with mapi; Tue, 30 Jun 2009 18:13:08 -0700
From: Zeev Vax <zeevvax@microsoft.com>
To: "Bill Ver Steeg (versteb)" <versteb@cisco.com>, Roni Even <Even.roni@huawei.com>, "Dave Oran (oran)" <oran@cisco.com>
Thread-Topic: [AVT] Port mappings, NAT, and RAMS
Thread-Index: AQHJ+XGL55qnQXLLnEGrAy1spvMJMJBfirkA//+t9sCAABhAsIAAHDbwgABdOHA=
Date: Wed, 1 Jul 2009 01:12:41 +0000
Message-ID: <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED309B@tk5ex14mbxc105.redmond.corp.microsoft.com>
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04137224@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54099DFD1A@xmb-sjc-215.amer.cisco.com> <"04CA D96D4C5	 C4"@xmb-sjc	-215.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04186C7F@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D5409A71F22@xmb-sjc-215.amer.cisco.com> <00e601c9f971$6a7b0e80$3f712b80$%roni@huawei.com> <83D31F7D-8D4C-44D1-9AD3-814C4776922F@cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED2A46@tk5ex14mbxc105.redmond.corp.microsoft.com> <012701c9f9a4$8226e670$8674b350$%roni@huawei.com> <81B9B88E2F9D574AA5328A85547CDE91018C6AC0@xmb-rtp-21d.amer.cisco.com>
In-Reply-To: <81B9B88E2F9D574AA5328A85547CDE91018C6AC0@xmb-rtp-21d.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: VAN CAENEGEM Tom <Tom.Van_Caenegem@alcatel-lucent.be>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 01 Jul 2009 01:12:49 -0000

Roni,

My reference to general solution was beyond RTCP, any interactive two way a=
pplication that have client in the cloud and not using HTTP over TCP, have =
the same issue. As Ethernet gaining more reliability UDP become a more valu=
able network solution, which will result in more application like that.

Zeev



-----Original Message-----
From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
Sent: Tuesday, June 30, 2009 2:15 PM
To: Roni Even; Zeev Vax; Dave Oran (oran)
Cc: Ali C. Begen (abegen); VAN CAENEGEM Tom; avt@ietf.org
Subject: RE: [AVT] Port mappings, NAT, and RAMS

Roni-

For the 2nd case, this problem also exists when the server's "request
port number" is different than the server's "response port number". This
is a very important case that breaks the port bindings in many NAT-ed
environments, and requires a standard solution.

Bill VerSteeg

-----Original Message-----
From: Roni Even [mailto:Even.roni@huawei.com]
Sent: Tuesday, June 30, 2009 10:02 AM
To: 'Zeev Vax'; Dave Oran (oran)
Cc: Ali C. Begen (abegen); 'VAN CAENEGEM Tom'; Bill Ver Steeg (versteb);
avt@ietf.org
Subject: RE: [AVT] Port mappings, NAT, and RAMS

Zeev,
I think that this is not a general problem, I am not sure that RTCP
should enable a general way to convey transport addresses, we will need
to open this to discussion.
Dave gave some probable cases but in my view the problem exists when
there are three important conditions:

1. No negotiation between both sides, no offer/answer like in
declarative SDP.  (prevent the receiver to offer a transport address)

2. The NACK /RAMS-R is going to one address while the response is coming
from a different address (like request to Feedback target in SSM and
response (may be RTP or RTCP) from retransmission server. This will
prevent using RTP/RTCP multiplexing

3. New one way communication (Like RTP from retransmission server and no
RTP from the receiver or previous unicast RTP to this receiver
(multicast with unicast retransmission). This prevent the receiver from
opening a pinhole to the source or from the retransmission server to do
SSRC multiplexing like in unicast retransmission. This is less limiting
if you use RTP/RTCP multiplexing based on resolving of condition 2 above
in a way that will enable RTP/RTCP multiplexing.


Roni Even



> -----Original Message-----
> From: Zeev Vax [mailto:zeevvax@microsoft.com]
> Sent: Tuesday, June 30, 2009 7:07 PM
> To: David R Oran; Roni Even
> Cc: 'Ali C. Begen (abegen)'; 'VAN CAENEGEM Tom'; 'Bill Ver Steeg
> (versteb)'; avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
>
> I agree this should be a separate draft and we should work on a more
> generic mechanism.
> Two comments I have, first being a general problem it might have been
> solved already so I think we should research the area before investing

> in another draft. Second given such functionality is typically part of

> an application and not staying only in the lower network layers, the
> application can solve it as part of the startup sequence or other data

> delivery mechanism it has.
>
> Zeev
>
> -----Original Message-----
> From: David R Oran [mailto:oran@cisco.com]
> Sent: Tuesday, June 30, 2009 6:10 AM
> To: Roni Even
> Cc: 'Ali C. Begen (abegen)'; 'VAN CAENEGEM Tom'; 'Bill Ver Steeg
> (versteb)'; Zeev Vax; avt@ietf.org
> Subject: Re: [AVT] Port mappings, NAT, and RAMS
>
>
> On Jun 30, 2009, at 6:55 AM, Roni Even wrote:
>
> > Hi guys,
> > My view is that this is not a general NACK problem but only for the
> > case of SSM and retransmission with similar box architecture to the
> > RAMS solution.
> > If you have another case please explain
> I believe it is actually a MORE general problem than NACK or RAMS. I
> arises from mixing SSM sessions and unicast sessions for the same RTP-

> based application. That's because multicast enforces port symmetry
> among all the receivers while unicast needs per-receiver port
> selection.
>
> So far we have two uses for mixing multicast and unicast:
> retransmission-based repair, and RAMS. I suspect more uses will arise
> in the future. I can think of a few off the top of my head:
> - customized per-user overlays (e.g. to be alpha-blended with the
> video) or object-level replacement
> - network-coded error recovery streams
> - extra media info for re-integration when switching back from unicast

> to multicast in a fast-forward-to-realtime capability when doing
> "pause-live-content" style services
> - adaptive switching between multicast and unicast based on number of
> simultaneous receivers.
>
> I have a strong intuition that doing a generic mechanism to atomically

> signal ports for unicast sessions using the RTCP feedback machinery of

> the SSM session would be highly advisable.
>
> So, I think:
> a) we need to solve this problem
> b) it exists even in the absence of NATs
> c) we need a generic mechanism
> d) it should be documented in a separate draft, and not part of RAMs
> or AVPF.
>
> If we can agree to these points, then we can have a more detailed
> discussion of the appropriate machinery. I have opinions on that
> subject too.
>
> DaveO.
>
>
>
> > Roni
> >
> >> -----Original Message-----
> >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
> Of
> >> Ali C. Begen (abegen)
> >> Sent: Tuesday, June 30, 2009 10:19 AM
> >> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni
> >> Even; avt@ietf.org
> >> Subject: Re: [AVT] Port mappings, NAT, and RAMS
> >>
> >> Hi Tom,
> >>
> >> Let's get the input from the WG on these points. I believe going
> >> for a more general solution that will be applicable to both RAMS
> >> and NACK is more desirable.
> >>
> >> BR,
> >> -acbegen
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> >>> Sent: Monday, June 29, 2009 9:17 AM
> >>> To: Ali C. Begen (abegen); Bill Ver Steeg (versteb); Zeev Vax;
> >>> Roni
> >> Even; avt@ietf.org
> >>> Subject: RE: Port mappings, NAT, and RAMS
> >>>
> >>>
> >>> Ali,
> >>>
> >>> See some comments below (TOM).
> >>>
> >>> -----Original Message-----
> >>> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> >>> Sent: vrijdag 26 juni 2009 17:41
> >>> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni
> Even;
> >>> avt@ietf.org
> >>> Subject: RE: Port mappings, NAT, and RAMS
> >>>
> >>> Hi Tom,
> >>>
> >>> [snip]
> >>>> The reason why we need pubports is that it indicates "explicitly"
> >> the
> >>>> port the client wants to use to receive the burst is the port it
> >> used
> >>>> to send the RAMS-R/pubports message. I believe we need this
> >> explicit
> >>>> indication, ow, we will be making an implicit assumption. Note
> that
> >>>> the rams-r/pubports is in the primary session and burst/ret
> packets
> >>>> are in the retransmission session, which is different than the
> >>> primary.
> >>>>
> >>>> As far as I can see, not everybody agrees on this point, but we
> >> need
> >>>> to make a decision here before we mandate anything.
> >>>>
> >>>> TOM: I agree with your last line, but I do not completely agree
> >> when
> >>>> you mention "implicit" assumption, especially for option 3, where

> >>>> RAMS-R (or
> >>>> NACK) and the Pub-port message are in the same compound message.
> If
> >> we
> >>>
> >>>> "define" that if no pub-report message is sent by the RR, the
> >>>> information towards the Retransmission server is exactly the same
> >> as
> >>>> when an RTP receiver sends an RTCP compound message made up of an
> >> RTCP
> >>>
> >>>> NACK/RAMS-R together with a pub-port message where the ports are
> >>> "zero"
> >>>
> >>> We "may" be able to say it from RAMS-R but not for NACK since we
> are
> >> not
> >>> defining it, we will be overloading its meaning, IMO. And as you/
> >>> Bill pointed out in other emails, I also believe that this is more

> >>> general problem than just RAMS. We need something like pubports
> >>> for NACKs
> as
> >>> well.
> >>>
> >>>
> >>> TOM: indeed, that is why IMO we should define this problem and
> >> solution
> >>> in a separate draft which applies to any system architecture where
> a
> >>> unicast session from a FT is coupled to a ssm session with that
> same
> >> FT.
> >>>
> >>>
> >>>> -as currently proposed in the RAMS draft now.  I agree that this
> is
> >>>> not true for option 4, where pub-port and RAMS-R or NACK are
> >> separate
> >>>> messages, but I do not favour the solution of option 4 for the
> same
> >>>> reason you mention in your reply (a new failure mode). So, if
> >> option 4
> >>>
> >>>> is -for that reason- no longer considered, I do not see a problem
> >> with
> >>>
> >>>> defining this rule/clause as expressed above. In other words,
> there
> >> is
> >>>
> >>>> no need for a pub-report message in this scenario and this
> >>>> results
> >> NOT
> >>>
> >>>> in an "assumption" what-so-ever.
> >>>>
> >>>>
> >>>>> supports RTP/RTCP muxing itself, and if it knows the RS supports

> >>>>> RTP/RTCP muxing too (as indicated in the declarative sdp
> >>>>> received
> >> by
> >>>
> >>>>> the
> >>>>> RR)
> >>>>>
> >>>>> -Don't we also allow that for option 3, the port P2 actually
> >> equals
> >>>>> port P4? This is a kind of hybrid of session and SSRC
> >> multiplexing
> >>>>> of the primary multicast RTP stream and the
> >>>>> retransmission/acceleration session
> >>>>> :  on the unidirectional RTP layer, the primary MC packets and
> >> the
> >>>>> unicast retransmission packets are clearly session muxed, but
> >>>>> the RTCP
> >>>>
> >>>>> "return" channel for both streams have exactly the same
> >>>>> transport addresses, but are distinguished by means of a
different SSRC.
> >> In
> >>>>> that
> >>>>
> >>>> How? Since SSM and retransmission sessions are session muxed,
> >>>> they have the same SSRC. When a client is sending a receiver
> >>>> report,
> how
> >> do
> >>>
> >>>> we identify which session it belongs to? So, I believe P2 should
> be
> >>>> different than P4.
> >>>>
> >>>> TOM: you are right. But notice this: RFC 4588 mandates that when
> >>>> session muxing is used for retransmission, than the SSRC should
> >>>> be
> >> the
> >>> same.
> >>>> However the RFC 4588 does not give arguments why it needs to be
> >> like
> >>>> that. So I ask you: what would or can happen if there is a
> >> different
> >>>> SSRC used?  If there are no convincing arguments why we must
> >>>> stick
> >> to
> >>>
> >>> Good question. If we don't use the same SSRC in session-muxed RTP
> >>> sessions, it will introduce correlation problems. Receiver/XR
> >>> reports coming from a larger number of receivers will be difficult

> >>> to
> >> identify
> >>> and match at the server side. There will be SSRC collisions, which
> >> will
> >>> complicate things further.
> >>>
> >>> TOM: the big difference with when the RFC 4588 was being discussed
> >> and
> >>> developed, is that now we are capable of advertising in SDP the
> SSRC
> >> of
> >>> the media server, that is in this case the retransmission server
> >>> SSRC used in the retransmission session. In fact for RAMS, we need

> >>> to
> >> define
> >>> the SSRC of the ssm RTP session, so we can as well do it for the
> >>> retransmission session. Perhaps we should consider this different
> >> SSRC
> >>> possibility (hence violating RFC 4588) as part of a new draft, the
> >> one I
> >>> mentioned above.
> >>>
> >>>
> >>>> the same SSRC, then, if we have a good use case to depart from
> that
> >>>> "rule" -and the use case we are discussing here is IMO indeed a
> >> valid
> >>>> use case- I do not see why we should be limited by such a "rule".
> >> The
> >>>> "valid" use case is here that RAMS and Retransmission for SSM
> >> sessions
> >>>
> >>>> operates fine through any NAPT and without any dedicated RTCP
> >> message.
> >>>
> >>> -acbegen
> >> _______________________________________________
> >> Audio/Video Transport Working Group avt@ietf.org
> >> https://www.ietf.org/mailman/listinfo/avt
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt




From zeevvax@microsoft.com  Tue Jun 30 18:12:49 2009
Return-Path: <zeevvax@microsoft.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 249563A65A6 for <avt@core3.amsl.com>; Tue, 30 Jun 2009 18:12:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 xYfOQZd5umK2 for <avt@core3.amsl.com>; Tue, 30 Jun 2009 18:12:47 -0700 (PDT)
Received: from smtp.microsoft.com (mail2.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 9515A28C20C for <avt@ietf.org>; Tue, 30 Jun 2009 18:12:47 -0700 (PDT)
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.99.4; Tue, 30 Jun 2009 18:13:08 -0700
Received: from tk5ex14mbxc105.redmond.corp.microsoft.com ([157.54.79.177]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi; Tue, 30 Jun 2009 18:13:08 -0700
From: Zeev Vax <zeevvax@microsoft.com>
To: "Bill Ver Steeg (versteb)" <versteb@cisco.com>, "Dave Oran (oran)" <oran@cisco.com>, Roni Even <Even.roni@huawei.com>
Thread-Topic: [AVT] Port mappings, NAT, and RAMS
Thread-Index: AQHJ+XGL55qnQXLLnEGrAy1spvMJMJBfirkA//+t9sCAADJukIAAYNvw
Date: Wed, 1 Jul 2009 01:12:42 +0000
Message-ID: <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED30B5@tk5ex14mbxc105.redmond.corp.microsoft.com>
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04137224@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54099DFD1A@xmb-sjc-215.amer.cisco.com> <"04CA D96D4C5	A3 E0D54099E	00C4"@xmb-sjc-215.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04186C7F@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D5409A71F22@xmb-sjc-215.amer.cisco.com> <00e601c9f971$6a7b0e80$3f712b80$%roni@huawei.com> <83D31F7D-8D4C-44D1-9AD3-814C4776922F@cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED2A46@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91018C6ABD@xmb-rtp-21d.amer.cisco.com>
In-Reply-To: <81B9B88E2F9D574AA5328A85547CDE91018C6ABD@xmb-rtp-21d.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: VAN CAENEGEM Tom <Tom.Van_Caenegem@alcatel-lucent.be>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 01 Jul 2009 01:12:49 -0000

I agree IETF is the right form, but I'm not sure the AVT WG is the right fo=
rm as I think it is more general problem.

Zeev

-----Original Message-----
From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
Sent: Tuesday, June 30, 2009 2:14 PM
To: Zeev Vax; Dave Oran (oran); Roni Even
Cc: Ali C. Begen (abegen); VAN CAENEGEM Tom; avt@ietf.org
Subject: RE: [AVT] Port mappings, NAT, and RAMS

I agree that we should make a general solution for mapping unicast
sessions onto unicast sessions.

We need to solve this problem using data flows that will work across
multiple vendors' solutions, and thus need to do it in a standards
forum. The IETF is the correct place to do this.

Bill VerSteeg

-----Original Message-----
From: Zeev Vax [mailto:zeevvax@microsoft.com]
Sent: Tuesday, June 30, 2009 9:07 AM
To: Dave Oran (oran); Roni Even
Cc: Ali C. Begen (abegen); 'VAN CAENEGEM Tom'; Bill Ver Steeg (versteb);
avt@ietf.org
Subject: RE: [AVT] Port mappings, NAT, and RAMS

I agree this should be a separate draft and we should work on a more
generic mechanism.
Two comments I have, first being a general problem it might have been
solved already so I think we should research the area before investing
in another draft. Second given such functionality is typically part of
an application and not staying only in the lower network layers, the
application can solve it as part of the startup sequence or other data
delivery mechanism it has.

Zeev

-----Original Message-----
From: David R Oran [mailto:oran@cisco.com]
Sent: Tuesday, June 30, 2009 6:10 AM
To: Roni Even
Cc: 'Ali C. Begen (abegen)'; 'VAN CAENEGEM Tom'; 'Bill Ver Steeg
(versteb)'; Zeev Vax; avt@ietf.org
Subject: Re: [AVT] Port mappings, NAT, and RAMS


On Jun 30, 2009, at 6:55 AM, Roni Even wrote:

> Hi guys,
> My view is that this is not a general NACK problem but only for the
> case of SSM and retransmission with similar box architecture to the
> RAMS solution.
> If you have another case please explain
I believe it is actually a MORE general problem than NACK or RAMS. I
arises from mixing SSM sessions and unicast sessions for the same RTP-
based application. That's because multicast enforces port symmetry among
all the receivers while unicast needs per-receiver port selection.

So far we have two uses for mixing multicast and unicast:
retransmission-based repair, and RAMS. I suspect more uses will arise in
the future. I can think of a few off the top of my head:
- customized per-user overlays (e.g. to be alpha-blended with the
video) or object-level replacement
- network-coded error recovery streams
- extra media info for re-integration when switching back from unicast
to multicast in a fast-forward-to-realtime capability when doing
"pause-live-content" style services
- adaptive switching between multicast and unicast based on number of
simultaneous receivers.

I have a strong intuition that doing a generic mechanism to atomically
signal ports for unicast sessions using the RTCP feedback machinery of
the SSM session would be highly advisable.

So, I think:
a) we need to solve this problem
b) it exists even in the absence of NATs
c) we need a generic mechanism
d) it should be documented in a separate draft, and not part of RAMs or
AVPF.

If we can agree to these points, then we can have a more detailed
discussion of the appropriate machinery. I have opinions on that subject
too.

DaveO.



> Roni
>
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of

>> Ali C. Begen (abegen)
>> Sent: Tuesday, June 30, 2009 10:19 AM
>> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni Even;
>> avt@ietf.org
>> Subject: Re: [AVT] Port mappings, NAT, and RAMS
>>
>> Hi Tom,
>>
>> Let's get the input from the WG on these points. I believe going for
>> a more general solution that will be applicable to both RAMS and NACK

>> is more desirable.
>>
>> BR,
>> -acbegen
>>
>>
>>
>>> -----Original Message-----
>>> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
>>> Sent: Monday, June 29, 2009 9:17 AM
>>> To: Ali C. Begen (abegen); Bill Ver Steeg (versteb); Zeev Vax; Roni
>> Even; avt@ietf.org
>>> Subject: RE: Port mappings, NAT, and RAMS
>>>
>>>
>>> Ali,
>>>
>>> See some comments below (TOM).
>>>
>>> -----Original Message-----
>>> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
>>> Sent: vrijdag 26 juni 2009 17:41
>>> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni Even;

>>> avt@ietf.org
>>> Subject: RE: Port mappings, NAT, and RAMS
>>>
>>> Hi Tom,
>>>
>>> [snip]
>>>> The reason why we need pubports is that it indicates "explicitly"
>> the
>>>> port the client wants to use to receive the burst is the port it
>> used
>>>> to send the RAMS-R/pubports message. I believe we need this
>> explicit
>>>> indication, ow, we will be making an implicit assumption. Note that

>>>> the rams-r/pubports is in the primary session and burst/ret packets

>>>> are in the retransmission session, which is different than the
>>> primary.
>>>>
>>>> As far as I can see, not everybody agrees on this point, but we
>> need
>>>> to make a decision here before we mandate anything.
>>>>
>>>> TOM: I agree with your last line, but I do not completely agree
>> when
>>>> you mention "implicit" assumption, especially for option 3, where
>>>> RAMS-R (or
>>>> NACK) and the Pub-port message are in the same compound message. If
>> we
>>>
>>>> "define" that if no pub-report message is sent by the RR, the
>>>> information towards the Retransmission server is exactly the same
>> as
>>>> when an RTP receiver sends an RTCP compound message made up of an
>> RTCP
>>>
>>>> NACK/RAMS-R together with a pub-port message where the ports are
>>> "zero"
>>>
>>> We "may" be able to say it from RAMS-R but not for NACK since we are
>> not
>>> defining it, we will be overloading its meaning, IMO. And as you/
>>> Bill pointed out in other emails, I also believe that this is more
>>> general problem than just RAMS. We need something like pubports for
>>> NACKs as well.
>>>
>>>
>>> TOM: indeed, that is why IMO we should define this problem and
>> solution
>>> in a separate draft which applies to any system architecture where a

>>> unicast session from a FT is coupled to a ssm session with that same
>> FT.
>>>
>>>
>>>> -as currently proposed in the RAMS draft now.  I agree that this is

>>>> not true for option 4, where pub-port and RAMS-R or NACK are
>> separate
>>>> messages, but I do not favour the solution of option 4 for the same

>>>> reason you mention in your reply (a new failure mode). So, if
>> option 4
>>>
>>>> is -for that reason- no longer considered, I do not see a problem
>> with
>>>
>>>> defining this rule/clause as expressed above. In other words, there
>> is
>>>
>>>> no need for a pub-report message in this scenario and this results
>> NOT
>>>
>>>> in an "assumption" what-so-ever.
>>>>
>>>>
>>>>> supports RTP/RTCP muxing itself, and if it knows the RS supports
>>>>> RTP/RTCP muxing too (as indicated in the declarative sdp received
>> by
>>>
>>>>> the
>>>>> RR)
>>>>>
>>>>> -Don't we also allow that for option 3, the port P2 actually
>> equals
>>>>> port P4? This is a kind of hybrid of session and SSRC
>> multiplexing
>>>>> of the primary multicast RTP stream and the
>>>>> retransmission/acceleration session
>>>>> :  on the unidirectional RTP layer, the primary MC packets and
>> the
>>>>> unicast retransmission packets are clearly session muxed, but the
>>>>> RTCP
>>>>
>>>>> "return" channel for both streams have exactly the same transport
>>>>> addresses, but are distinguished by means of a different SSRC.
>> In
>>>>> that
>>>>
>>>> How? Since SSM and retransmission sessions are session muxed, they
>>>> have the same SSRC. When a client is sending a receiver report, how
>> do
>>>
>>>> we identify which session it belongs to? So, I believe P2 should be

>>>> different than P4.
>>>>
>>>> TOM: you are right. But notice this: RFC 4588 mandates that when
>>>> session muxing is used for retransmission, than the SSRC should be
>> the
>>> same.
>>>> However the RFC 4588 does not give arguments why it needs to be
>> like
>>>> that. So I ask you: what would or can happen if there is a
>> different
>>>> SSRC used?  If there are no convincing arguments why we must stick
>> to
>>>
>>> Good question. If we don't use the same SSRC in session-muxed RTP
>>> sessions, it will introduce correlation problems. Receiver/XR
>>> reports coming from a larger number of receivers will be difficult
>>> to
>> identify
>>> and match at the server side. There will be SSRC collisions, which
>> will
>>> complicate things further.
>>>
>>> TOM: the big difference with when the RFC 4588 was being discussed
>> and
>>> developed, is that now we are capable of advertising in SDP the SSRC
>> of
>>> the media server, that is in this case the retransmission server
>>> SSRC used in the retransmission session. In fact for RAMS, we need
>>> to
>> define
>>> the SSRC of the ssm RTP session, so we can as well do it for the
>>> retransmission session. Perhaps we should consider this different
>> SSRC
>>> possibility (hence violating RFC 4588) as part of a new draft, the
>> one I
>>> mentioned above.
>>>
>>>
>>>> the same SSRC, then, if we have a good use case to depart from that

>>>> "rule" -and the use case we are discussing here is IMO indeed a
>> valid
>>>> use case- I do not see why we should be limited by such a "rule".
>> The
>>>> "valid" use case is here that RAMS and Retransmission for SSM
>> sessions
>>>
>>>> operates fine through any NAPT and without any dedicated RTCP
>> message.
>>>
>>> -acbegen
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt




From Even.roni@huawei.com  Tue Jun 30 21:59:19 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C21733A67E7 for <avt@core3.amsl.com>; Tue, 30 Jun 2009 21:59:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 BuRKuf7WyDUj for <avt@core3.amsl.com>; Tue, 30 Jun 2009 21:59:18 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 30A1A3A6F04 for <avt@ietf.org>; Tue, 30 Jun 2009 21:59:13 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KM3001LZ770WN@szxga02-in.huawei.com> for avt@ietf.org; Wed, 01 Jul 2009 12:59:24 +0800 (CST)
Received: from huawei.com ([172.24.1.3]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KM300E5G770UO@szxga02-in.huawei.com> for avt@ietf.org; Wed, 01 Jul 2009 12:59:24 +0800 (CST)
Received: from windows8d787f9 (bzq-82-81-144-74.red.bezeqint.net [82.81.144.74]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KM300LDD76JIC@szxml01-in.huawei.com>; Wed, 01 Jul 2009 12:59:23 +0800 (CST)
Date: Wed, 01 Jul 2009 07:58:51 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED309B@tk5ex14mbxc105.redmond.corp.microsoft.com>
To: 'Zeev Vax' <zeevvax@microsoft.com>, "'Bill Ver Steeg (versteb)'" <versteb@cisco.com>, "'Dave Oran (oran)'" <oran@cisco.com>
Message-id: <017d01c9fa08$ab619030$0224b090$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AQHJ+XGL55qnQXLLnEGrAy1spvMJMJBfirkA//+t9sCAABhAsIAAHDbwgABdOHCAAFMX4A==
iPlanet-SMTP-Warning: Lines longer than SMTP allows found and truncated.
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04137224@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54099DFD1A@xmb-sjc-215.amer.cisco.com> <"2383825952653 2DCAF04186C7F"@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D5409A71F22@xmb-sjc-215.amer.cisco.com> <00e601c9f971$6a7b0e80$3f712b80$%roni@huawei.com> <83D31F7D-8D4C-44D1-9AD3-814C4776922F@cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED2A46@tk5ex14mbxc105.redmond.corp.microsoft.com> <012701c9f9a4$8226e670$8674b350$%roni@huawei.com> <81B9B88E2F9D574AA5328A85547CDE91018C6AC0@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED309B@tk5ex14mbxc105.redmond.corp.microsoft.com>
Cc: 'VAN CAENEGEM Tom' <Tom.Van_Caenegem@alcatel-lucent.be>, avt@ietf.org
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 01 Jul 2009 04:59:19 -0000

Zeev,
You are right but I am trying to find the cases where for RTP/RTCP you
cannot address this on the application layer. For our work this means that
you cannot provide the information using SDP in offer/answer or declarative
way.
Roni

> -----Original Message-----
> From: Zeev Vax [mailto:zeevvax@microsoft.com]
> Sent: Wednesday, July 01, 2009 4:13 AM
> To: Bill Ver Steeg (versteb); Roni Even; Dave Oran (oran)
> Cc: Ali C. Begen (abegen); VAN CAENEGEM Tom; avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
> 
> Roni,
> 
> My reference to general solution was beyond RTCP, any interactive two
> way application that have client in the cloud and not using HTTP over
> TCP, have the same issue. As Ethernet gaining more reliability UDP
> become a more valuable network solution, which will result in more
> application like that.
> 
> Zeev
> 
> 
> 
> -----Original Message-----
> From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> Sent: Tuesday, June 30, 2009 2:15 PM
> To: Roni Even; Zeev Vax; Dave Oran (oran)
> Cc: Ali C. Begen (abegen); VAN CAENEGEM Tom; avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
> 
> Roni-
> 
> For the 2nd case, this problem also exists when the server's "request
> port number" is different than the server's "response port number".
> This
> is a very important case that breaks the port bindings in many NAT-ed
> environments, and requires a standard solution.
> 
> Bill VerSteeg
> 
> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: Tuesday, June 30, 2009 10:02 AM
> To: 'Zeev Vax'; Dave Oran (oran)
> Cc: Ali C. Begen (abegen); 'VAN CAENEGEM Tom'; Bill Ver Steeg
> (versteb);
> avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
> 
> Zeev,
> I think that this is not a general problem, I am not sure that RTCP
> should enable a general way to convey transport addresses, we will need
> to open this to discussion.
> Dave gave some probable cases but in my view the problem exists when
> there are three important conditions:
> 
> 1. No negotiation between both sides, no offer/answer like in
> declarative SDP.  (prevent the receiver to offer a transport address)
> 
> 2. The NACK /RAMS-R is going to one address while the response is
> coming
> from a different address (like request to Feedback target in SSM and
> response (may be RTP or RTCP) from retransmission server. This will
> prevent using RTP/RTCP multiplexing
> 
> 3. New one way communication (Like RTP from retransmission server and
> no
> RTP from the receiver or previous unicast RTP to this receiver
> (multicast with unicast retransmission). This prevent the receiver from
> opening a pinhole to the source or from the retransmission server to do
> SSRC multiplexing like in unicast retransmission. This is less limiting
> if you use RTP/RTCP multiplexing based on resolving of condition 2
> above
> in a way that will enable RTP/RTCP multiplexing.
> 
> 
> Roni Even
> 
> 
> 
> > -----Original Message-----
> > From: Zeev Vax [mailto:zeevvax@microsoft.com]
> > Sent: Tuesday, June 30, 2009 7:07 PM
> > To: David R Oran; Roni Even
> > Cc: 'Ali C. Begen (abegen)'; 'VAN CAENEGEM Tom'; 'Bill Ver Steeg
> > (versteb)'; avt@ietf.org
> > Subject: RE: [AVT] Port mappings, NAT, and RAMS
> >
> > I agree this should be a separate draft and we should work on a more
> > generic mechanism.
> > Two comments I have, first being a general problem it might have been
> > solved already so I think we should research the area before
> investing
> 
> > in another draft. Second given such functionality is typically part
> of
> 
> > an application and not staying only in the lower network layers, the
> > application can solve it as part of the startup sequence or other
> data
> 
> > delivery mechanism it has.
> >
> > Zeev
> >
> > -----Original Message-----
> > From: David R Oran [mailto:oran@cisco.com]
> > Sent: Tuesday, June 30, 2009 6:10 AM
> > To: Roni Even
> > Cc: 'Ali C. Begen (abegen)'; 'VAN CAENEGEM Tom'; 'Bill Ver Steeg
> > (versteb)'; Zeev Vax; avt@ietf.org
> > Subject: Re: [AVT] Port mappings, NAT, and RAMS
> >
> >
> > On Jun 30, 2009, at 6:55 AM, Roni Even wrote:
> >
> > > Hi guys,
> > > My view is that this is not a general NACK problem but only for the
> > > case of SSM and retransmission with similar box architecture to the
> > > RAMS solution.
> > > If you have another case please explain
> > I believe it is actually a MORE general problem than NACK or RAMS. I
> > arises from mixing SSM sessions and unicast sessions for the same
> RTP-
> 
> > based application. That's because multicast enforces port symmetry
> > among all the receivers while unicast needs per-receiver port
> > selection.
> >
> > So far we have two uses for mixing multicast and unicast:
> > retransmission-based repair, and RAMS. I suspect more uses will arise
> > in the future. I can think of a few off the top of my head:
> > - customized per-user overlays (e.g. to be alpha-blended with the
> > video) or object-level replacement
> > - network-coded error recovery streams
> > - extra media info for re-integration when switching back from
> unicast
> 
> > to multicast in a fast-forward-to-realtime capability when doing
> > "pause-live-content" style services
> > - adaptive switching between multicast and unicast based on number of
> > simultaneous receivers.
> >
> > I have a strong intuition that doing a generic mechanism to
> atomically
> 
> > signal ports for unicast sessions using the RTCP feedback machinery
> of
> 
> > the SSM session would be highly advisable.
> >
> > So, I think:
> > a) we need to solve this problem
> > b) it exists even in the absence of NATs
> > c) we need a generic mechanism
> > d) it should be documented in a separate draft, and not part of RAMs
> > or AVPF.
> >
> > If we can agree to these points, then we can have a more detailed
> > discussion of the appropriate machinery. I have opinions on that
> > subject too.
> >
> > DaveO.
> >
> >
> >
> > > Roni
> > >
> > >> -----Original Message-----
> > >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
> > Of
> > >> Ali C. Begen (abegen)
> > >> Sent: Tuesday, June 30, 2009 10:19 AM
> > >> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni
> > >> Even; avt@ietf.org
> > >> Subject: Re: [AVT] Port mappings, NAT, and RAMS
> > >>
> > >> Hi Tom,
> > >>
> > >> Let's get the input from the WG on these points. I believe going
> > >> for a more general solution that will be applicable to both RAMS
> > >> and NACK is more desirable.
> > >>
> > >> BR,
> > >> -acbegen
> > >>
> > >>
> > >>
> > >>> -----Original Message-----
> > >>> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-
> lucent.be]
> > >>> Sent: Monday, June 29, 2009 9:17 AM
> > >>> To: Ali C. Begen (abegen); Bill Ver Steeg (versteb); Zeev Vax;
> > >>> Roni
> > >> Even; avt@ietf.org
> > >>> Subject: RE: Port mappings, NAT, and RAMS
> > >>>
> > >>>
> > >>> Ali,
> > >>>
> > >>> See some comments below (TOM).
> > >>>
> > >>> -----Original Message-----
> > >>> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> > >>> Sent: vrijdag 26 juni 2009 17:41
> > >>> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni
> > Even;
> > >>> avt@ietf.org
> > >>> Subject: RE: Port mappings, NAT, and RAMS
> > >>>
> > >>> Hi Tom,
> > >>>
> > >>> [snip]
> > >>>> The reason why we need pubports is that it indicates
> "explicitly"
> > >> the
> > >>>> port the client wants to use to receive the burst is the port it
> > >> used
> > >>>> to send the RAMS-R/pubports message. I believe we need this
> > >> explicit
> > >>>> indication, ow, we will be making an implicit assumption. Note
> > that
> > >>>> the rams-r/pubports is in the primary session and burst/ret
> > packets
> > >>>> are in the retransmission session, which is different than the
> > >>> primary.
> > >>>>
> > >>>> As far as I can see, not everybody agrees on this point, but we
> > >> need
> > >>>> to make a decision here before we mandate anything.
> > >>>>
> > >>>> TOM: I agree with your last line, but I do not completely agree
> > >> when
> > >>>> you mention "implicit" assumption, especially for option 3,
> where
> 
> > >>>> RAMS-R (or
> > >>>> NACK) and the Pub-port message are in the same compound message.
> > If
> > >> we
> > >>>
> > >>>> "define" that if no pub-report message is sent by the RR, the
> > >>>> information towards the Retransmission server is exactly the
> same
> > >> as
> > >>>> when an RTP receiver sends an RTCP compound message made up of
> an
> > >> RTCP
> > >>>
> > >>>> NACK/RAMS-R together with a pub-port message where the ports are
> > >>> "zero"
> > >>>
> > >>> We "may" be able to say it from RAMS-R but not for NACK since we
> > are
> > >> not
> > >>> defining it, we will be overloading its meaning, IMO. And as you/
> > >>> Bill pointed out in other emails, I also believe that this is
> more
> 
> > >>> general problem than just RAMS. We need something like pubports
> > >>> for NACKs
> > as
> > >>> well.
> > >>>
> > >>>
> > >>> TOM: indeed, that is why IMO we should define this problem and
> > >> solution
> > >>> in a separate draft which applies to any system architecture
> where
> > a
> > >>> unicast session from a FT is coupled to a ssm session with that
> > same
> > >> FT.
> > >>>
> > >>>
> > >>>> -as currently proposed in the RAMS draft now.  I agree that this
> > is
> > >>>> not true for option 4, where pub-port and RAMS-R or NACK are
> > >> separate
> > >>>> messages, but I do not favour the solution of option 4 for the
> > same
> > >>>> reason you mention in your reply (a new failure mode). So, if
> > >> option 4
> > >>>
> > >>>> is -for that reason- no longer considered, I do not see a
> problem
> > >> with
> > >>>
> > >>>> defining this rule/clause as expressed above. In other words,
> > there
> > >> is
> > >>>
> > >>>> no need for a pub-report message in this scenario and this
> > >>>> results
> > >> NOT
> > >>>
> > >>>> in an "assumption" what-so-ever.
> > >>>>
> > >>>>
> > >>>>> supports RTP/RTCP muxing itself, and if it knows the RS
> supports
> 
> > >>>>> RTP/RTCP muxing too (as indicated in the declarative sdp
> > >>>>> received
> > >> by
> > >>>
> > >>>>> the
> > >>>>> RR)
> > >>>>>
> > >>>>> -Don't we also allow that for option 3, the port P2 actually
> > >> equals
> > >>>>> port P4? This is a kind of hybrid of session and SSRC
> > >> multiplexing
> > >>>>> of the primary multicast RTP stream and the
> > >>>>> retransmission/acceleration session
> > >>>>> :  on the unidirectional RTP layer, the primary MC packets and
> > >> the
> > >>>>> unicast retransmission packets are clearly session muxed, but
> > >>>>> the RTCP
> > >>>>
> > >>>>> "return" channel for both streams have exactly the same
> > >>>>> transport addresses, but are distinguished by means of a
> different SSRC.
> > >> In
> > >>>>> that
> > >>>>
> > >>>> How? Since SSM and retransmission sessions are session muxed,
> > >>>> they have the same SSRC. When a client is sending a receiver
> > >>>> report,
> > how
> > >> do
> > >>>
> > >>>> we identify which session it belongs to? So, I believe P2 should
> > be
> > >>>> different than P4.
> > >>>>
> > >>>> TOM: you are right. But notice this: RFC 4588 mandates that when
> > >>>> session muxing is used for retransmission, than the SSRC should
> > >>>> be
> > >> the
> > >>> same.
> > >>>> However the RFC 4588 does not give arguments why it needs to be
> > >> like
> > >>>> that. So I ask you: what would or can happen if there is a
> > >> different
> > >>>> SSRC used?  If there are no convincing arguments why we must
> > >>>> stick
> > >> to
> > >>>
> > >>> Good question. If we don't use the same SSRC in session-muxed RTP
> > >>> sessions, it will introduce correlation problems. Receiver/XR
> > >>> reports coming from a larger number of receivers will be
> difficult
> 
> > >>> to
> > >> identify
> > >>> and match at the server side. There will be SSRC collisions,
> which
> > >> will
> > >>> complicate things further.
> > >>>
> > >>> TOM: the big difference with when the RFC 4588 was being
> discussed
> > >> and
> > >>> developed, is that now we are capable of advertising in SDP the
> > SSRC
> > >> of
> > >>> the media server, that is in this case the retransmission server
> > >>> SSRC used in the retransmission session. In fact for RAMS, we
> need
> 
> > >>> to
> > >> define
> > >>> the SSRC of the ssm RTP session, so we can as well do it for the
> > >>> retransmission session. Perhaps we should consider this different
> > >> SSRC
> > >>> possibility (hence violating RFC 4588) as part of a new draft,
> the
> > >> one I
> > >>> mentioned above.
> > >>>
> > >>>
> > >>>> the same SSRC, then, if we have a good use case to depart from
> > that
> > >>>> "rule" -and the use case we are discussing here is IMO indeed a
> > >> valid
> > >>>> use case- I do not see why we should be limited by such a
> "rule".
> > >> The
> > >>>> "valid" use case is here that RAMS and Retransmission for SSM
> > >> sessions
> > >>>
> > >>>> operates fine through any NAPT and without any dedicated RTCP
> > >> message.
> > >>>
> > >>> -acbegen
> > >> _______________________________________________
> > >> Audio/Video Transport Working Group avt@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/avt
> > >
> > > _______________________________________________
> > > Audio/Video Transport Working Group
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
> 



From Even.roni@huawei.com  Tue Jun 30 22:00:15 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B6EF03A691B for <avt@core3.amsl.com>; Tue, 30 Jun 2009 22:00:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 Cp8KbSbJY7I8 for <avt@core3.amsl.com>; Tue, 30 Jun 2009 22:00:14 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id BC9163A6901 for <avt@ietf.org>; Tue, 30 Jun 2009 22:00:13 -0700 (PDT)
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 <0KM300A8978O39@szxga04-in.huawei.com> for avt@ietf.org; Wed, 01 Jul 2009 13:00:25 +0800 (CST)
Received: from huawei.com ([172.24.1.3]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KM300FPI78OUA@szxga04-in.huawei.com> for avt@ietf.org; Wed, 01 Jul 2009 13:00:24 +0800 (CST)
Received: from windows8d787f9 (bzq-82-81-144-74.red.bezeqint.net [82.81.144.74]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KM300LEB78CIC@szxml01-in.huawei.com>; Wed, 01 Jul 2009 13:00:24 +0800 (CST)
Date: Wed, 01 Jul 2009 07:59:59 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <81B9B88E2F9D574AA5328A85547CDE91018C6AC0@xmb-rtp-21d.amer.cisco.com>
To: "'Bill Ver Steeg (versteb)'" <versteb@cisco.com>, 'Zeev Vax' <zeevvax@microsoft.com>, "'Dave Oran (oran)'" <oran@cisco.com>
Message-id: <017e01c9fa08$d02185b0$70649110$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AQHJ+XGL55qnQXLLnEGrAy1spvMJMJBfirkA//+t9sCAABhAsIAAHDbwgACxThA=
iPlanet-SMTP-Warning: Lines longer than SMTP allows found and truncated.
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04137224@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54099DFD1A@xmb-sjc-215.amer.cisco.com> <"2383825952653 2DCAF04186C7F"@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D5409A71F22@xmb-sjc-215.amer.cisco.com> <00e601c9f971$6a7b0e80$3f712b80$%roni@huawei.com> <83D31F7D-8D4C-44D1-9AD3-814C4776922F@cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED2A46@tk5ex14mbxc105.redmond.corp.microsoft.com> <012701c9f9a4$8226e670$8674b350$%roni@huawei.com> <81B9B88E2F9D574AA5328A85547CDE91018C6AC0@xmb-rtp-21d.amer.cisco.com>
Cc: 'VAN CAENEGEM Tom' <Tom.Van_Caenegem@alcatel-lucent.be>, avt@ietf.org
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 01 Jul 2009 05:00:15 -0000

Bill,
If the server's sends the announcement using SDP this is not a problem
Roni

> -----Original Message-----
> From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> Sent: Wednesday, July 01, 2009 12:15 AM
> To: Roni Even; Zeev Vax; Dave Oran (oran)
> Cc: Ali C. Begen (abegen); VAN CAENEGEM Tom; avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
> 
> Roni-
> 
> For the 2nd case, this problem also exists when the server's "request
> port number" is different than the server's "response port number".
> This
> is a very important case that breaks the port bindings in many NAT-ed
> environments, and requires a standard solution.
> 
> Bill VerSteeg
> 
> -----Original Message-----
> From: Roni Even [mailto:Even.roni@huawei.com]
> Sent: Tuesday, June 30, 2009 10:02 AM
> To: 'Zeev Vax'; Dave Oran (oran)
> Cc: Ali C. Begen (abegen); 'VAN CAENEGEM Tom'; Bill Ver Steeg
> (versteb);
> avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
> 
> Zeev,
> I think that this is not a general problem, I am not sure that RTCP
> should enable a general way to convey transport addresses, we will need
> to open this to discussion.
> Dave gave some probable cases but in my view the problem exists when
> there are three important conditions:
> 
> 1. No negotiation between both sides, no offer/answer like in
> declarative SDP.  (prevent the receiver to offer a transport address)
> 
> 2. The NACK /RAMS-R is going to one address while the response is
> coming
> from a different address (like request to Feedback target in SSM and
> response (may be RTP or RTCP) from retransmission server. This will
> prevent using RTP/RTCP multiplexing
> 
> 3. New one way communication (Like RTP from retransmission server and
> no
> RTP from the receiver or previous unicast RTP to this receiver
> (multicast with unicast retransmission). This prevent the receiver from
> opening a pinhole to the source or from the retransmission server to do
> SSRC multiplexing like in unicast retransmission. This is less limiting
> if you use RTP/RTCP multiplexing based on resolving of condition 2
> above
> in a way that will enable RTP/RTCP multiplexing.
> 
> 
> Roni Even
> 
> 
> 
> > -----Original Message-----
> > From: Zeev Vax [mailto:zeevvax@microsoft.com]
> > Sent: Tuesday, June 30, 2009 7:07 PM
> > To: David R Oran; Roni Even
> > Cc: 'Ali C. Begen (abegen)'; 'VAN CAENEGEM Tom'; 'Bill Ver Steeg
> > (versteb)'; avt@ietf.org
> > Subject: RE: [AVT] Port mappings, NAT, and RAMS
> >
> > I agree this should be a separate draft and we should work on a more
> > generic mechanism.
> > Two comments I have, first being a general problem it might have been
> > solved already so I think we should research the area before
> investing
> 
> > in another draft. Second given such functionality is typically part
> of
> 
> > an application and not staying only in the lower network layers, the
> > application can solve it as part of the startup sequence or other
> data
> 
> > delivery mechanism it has.
> >
> > Zeev
> >
> > -----Original Message-----
> > From: David R Oran [mailto:oran@cisco.com]
> > Sent: Tuesday, June 30, 2009 6:10 AM
> > To: Roni Even
> > Cc: 'Ali C. Begen (abegen)'; 'VAN CAENEGEM Tom'; 'Bill Ver Steeg
> > (versteb)'; Zeev Vax; avt@ietf.org
> > Subject: Re: [AVT] Port mappings, NAT, and RAMS
> >
> >
> > On Jun 30, 2009, at 6:55 AM, Roni Even wrote:
> >
> > > Hi guys,
> > > My view is that this is not a general NACK problem but only for the
> > > case of SSM and retransmission with similar box architecture to the
> > > RAMS solution.
> > > If you have another case please explain
> > I believe it is actually a MORE general problem than NACK or RAMS. I
> > arises from mixing SSM sessions and unicast sessions for the same
> RTP-
> 
> > based application. That's because multicast enforces port symmetry
> > among all the receivers while unicast needs per-receiver port
> > selection.
> >
> > So far we have two uses for mixing multicast and unicast:
> > retransmission-based repair, and RAMS. I suspect more uses will arise
> > in the future. I can think of a few off the top of my head:
> > - customized per-user overlays (e.g. to be alpha-blended with the
> > video) or object-level replacement
> > - network-coded error recovery streams
> > - extra media info for re-integration when switching back from
> unicast
> 
> > to multicast in a fast-forward-to-realtime capability when doing
> > "pause-live-content" style services
> > - adaptive switching between multicast and unicast based on number of
> > simultaneous receivers.
> >
> > I have a strong intuition that doing a generic mechanism to
> atomically
> 
> > signal ports for unicast sessions using the RTCP feedback machinery
> of
> 
> > the SSM session would be highly advisable.
> >
> > So, I think:
> > a) we need to solve this problem
> > b) it exists even in the absence of NATs
> > c) we need a generic mechanism
> > d) it should be documented in a separate draft, and not part of RAMs
> > or AVPF.
> >
> > If we can agree to these points, then we can have a more detailed
> > discussion of the appropriate machinery. I have opinions on that
> > subject too.
> >
> > DaveO.
> >
> >
> >
> > > Roni
> > >
> > >> -----Original Message-----
> > >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
> > Of
> > >> Ali C. Begen (abegen)
> > >> Sent: Tuesday, June 30, 2009 10:19 AM
> > >> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni
> > >> Even; avt@ietf.org
> > >> Subject: Re: [AVT] Port mappings, NAT, and RAMS
> > >>
> > >> Hi Tom,
> > >>
> > >> Let's get the input from the WG on these points. I believe going
> > >> for a more general solution that will be applicable to both RAMS
> > >> and NACK is more desirable.
> > >>
> > >> BR,
> > >> -acbegen
> > >>
> > >>
> > >>
> > >>> -----Original Message-----
> > >>> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-
> lucent.be]
> > >>> Sent: Monday, June 29, 2009 9:17 AM
> > >>> To: Ali C. Begen (abegen); Bill Ver Steeg (versteb); Zeev Vax;
> > >>> Roni
> > >> Even; avt@ietf.org
> > >>> Subject: RE: Port mappings, NAT, and RAMS
> > >>>
> > >>>
> > >>> Ali,
> > >>>
> > >>> See some comments below (TOM).
> > >>>
> > >>> -----Original Message-----
> > >>> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> > >>> Sent: vrijdag 26 juni 2009 17:41
> > >>> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni
> > Even;
> > >>> avt@ietf.org
> > >>> Subject: RE: Port mappings, NAT, and RAMS
> > >>>
> > >>> Hi Tom,
> > >>>
> > >>> [snip]
> > >>>> The reason why we need pubports is that it indicates
> "explicitly"
> > >> the
> > >>>> port the client wants to use to receive the burst is the port it
> > >> used
> > >>>> to send the RAMS-R/pubports message. I believe we need this
> > >> explicit
> > >>>> indication, ow, we will be making an implicit assumption. Note
> > that
> > >>>> the rams-r/pubports is in the primary session and burst/ret
> > packets
> > >>>> are in the retransmission session, which is different than the
> > >>> primary.
> > >>>>
> > >>>> As far as I can see, not everybody agrees on this point, but we
> > >> need
> > >>>> to make a decision here before we mandate anything.
> > >>>>
> > >>>> TOM: I agree with your last line, but I do not completely agree
> > >> when
> > >>>> you mention "implicit" assumption, especially for option 3,
> where
> 
> > >>>> RAMS-R (or
> > >>>> NACK) and the Pub-port message are in the same compound message.
> > If
> > >> we
> > >>>
> > >>>> "define" that if no pub-report message is sent by the RR, the
> > >>>> information towards the Retransmission server is exactly the
> same
> > >> as
> > >>>> when an RTP receiver sends an RTCP compound message made up of
> an
> > >> RTCP
> > >>>
> > >>>> NACK/RAMS-R together with a pub-port message where the ports are
> > >>> "zero"
> > >>>
> > >>> We "may" be able to say it from RAMS-R but not for NACK since we
> > are
> > >> not
> > >>> defining it, we will be overloading its meaning, IMO. And as you/
> > >>> Bill pointed out in other emails, I also believe that this is
> more
> 
> > >>> general problem than just RAMS. We need something like pubports
> > >>> for NACKs
> > as
> > >>> well.
> > >>>
> > >>>
> > >>> TOM: indeed, that is why IMO we should define this problem and
> > >> solution
> > >>> in a separate draft which applies to any system architecture
> where
> > a
> > >>> unicast session from a FT is coupled to a ssm session with that
> > same
> > >> FT.
> > >>>
> > >>>
> > >>>> -as currently proposed in the RAMS draft now.  I agree that this
> > is
> > >>>> not true for option 4, where pub-port and RAMS-R or NACK are
> > >> separate
> > >>>> messages, but I do not favour the solution of option 4 for the
> > same
> > >>>> reason you mention in your reply (a new failure mode). So, if
> > >> option 4
> > >>>
> > >>>> is -for that reason- no longer considered, I do not see a
> problem
> > >> with
> > >>>
> > >>>> defining this rule/clause as expressed above. In other words,
> > there
> > >> is
> > >>>
> > >>>> no need for a pub-report message in this scenario and this
> > >>>> results
> > >> NOT
> > >>>
> > >>>> in an "assumption" what-so-ever.
> > >>>>
> > >>>>
> > >>>>> supports RTP/RTCP muxing itself, and if it knows the RS
> supports
> 
> > >>>>> RTP/RTCP muxing too (as indicated in the declarative sdp
> > >>>>> received
> > >> by
> > >>>
> > >>>>> the
> > >>>>> RR)
> > >>>>>
> > >>>>> -Don't we also allow that for option 3, the port P2 actually
> > >> equals
> > >>>>> port P4? This is a kind of hybrid of session and SSRC
> > >> multiplexing
> > >>>>> of the primary multicast RTP stream and the
> > >>>>> retransmission/acceleration session
> > >>>>> :  on the unidirectional RTP layer, the primary MC packets and
> > >> the
> > >>>>> unicast retransmission packets are clearly session muxed, but
> > >>>>> the RTCP
> > >>>>
> > >>>>> "return" channel for both streams have exactly the same
> > >>>>> transport addresses, but are distinguished by means of a
> different SSRC.
> > >> In
> > >>>>> that
> > >>>>
> > >>>> How? Since SSM and retransmission sessions are session muxed,
> > >>>> they have the same SSRC. When a client is sending a receiver
> > >>>> report,
> > how
> > >> do
> > >>>
> > >>>> we identify which session it belongs to? So, I believe P2 should
> > be
> > >>>> different than P4.
> > >>>>
> > >>>> TOM: you are right. But notice this: RFC 4588 mandates that when
> > >>>> session muxing is used for retransmission, than the SSRC should
> > >>>> be
> > >> the
> > >>> same.
> > >>>> However the RFC 4588 does not give arguments why it needs to be
> > >> like
> > >>>> that. So I ask you: what would or can happen if there is a
> > >> different
> > >>>> SSRC used?  If there are no convincing arguments why we must
> > >>>> stick
> > >> to
> > >>>
> > >>> Good question. If we don't use the same SSRC in session-muxed RTP
> > >>> sessions, it will introduce correlation problems. Receiver/XR
> > >>> reports coming from a larger number of receivers will be
> difficult
> 
> > >>> to
> > >> identify
> > >>> and match at the server side. There will be SSRC collisions,
> which
> > >> will
> > >>> complicate things further.
> > >>>
> > >>> TOM: the big difference with when the RFC 4588 was being
> discussed
> > >> and
> > >>> developed, is that now we are capable of advertising in SDP the
> > SSRC
> > >> of
> > >>> the media server, that is in this case the retransmission server
> > >>> SSRC used in the retransmission session. In fact for RAMS, we
> need
> 
> > >>> to
> > >> define
> > >>> the SSRC of the ssm RTP session, so we can as well do it for the
> > >>> retransmission session. Perhaps we should consider this different
> > >> SSRC
> > >>> possibility (hence violating RFC 4588) as part of a new draft,
> the
> > >> one I
> > >>> mentioned above.
> > >>>
> > >>>
> > >>>> the same SSRC, then, if we have a good use case to depart from
> > that
> > >>>> "rule" -and the use case we are discussing here is IMO indeed a
> > >> valid
> > >>>> use case- I do not see why we should be limited by such a
> "rule".
> > >> The
> > >>>> "valid" use case is here that RAMS and Retransmission for SSM
> > >> sessions
> > >>>
> > >>>> operates fine through any NAPT and without any dedicated RTCP
> > >> message.
> > >>>
> > >>> -acbegen
> > >> _______________________________________________
> > >> Audio/Video Transport Working Group avt@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/avt
> > >
> > > _______________________________________________
> > > Audio/Video Transport Working Group
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt



From Even.roni@huawei.com  Tue Jun 30 22:01:58 2009
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8526A3A6ECA for <avt@core3.amsl.com>; Tue, 30 Jun 2009 22:01:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.547
X-Spam-Level: 
X-Spam-Status: No, score=-1.547 tagged_above=-999 required=5 tests=[AWL=1.052,  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 v1ohETmZlLz5 for <avt@core3.amsl.com>; Tue, 30 Jun 2009 22:01:56 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 71F443A691B for <avt@ietf.org>; Tue, 30 Jun 2009 22:01:56 -0700 (PDT)
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 <0KM300HJU7BSQ2@szxga03-in.huawei.com> for avt@ietf.org; Wed, 01 Jul 2009 13:02:16 +0800 (CST)
Received: from huawei.com ([172.24.1.6]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KM300HCE7BSJL@szxga03-in.huawei.com> for avt@ietf.org; Wed, 01 Jul 2009 13:02:16 +0800 (CST)
Received: from windows8d787f9 (bzq-82-81-144-74.red.bezeqint.net [82.81.144.74]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KM3003NH7BFHA@szxml02-in.huawei.com>; Wed, 01 Jul 2009 13:02:16 +0800 (CST)
Date: Wed, 01 Jul 2009 08:01:50 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED30B5@tk5ex14mbxc105.redmond.corp.microsoft.com>
To: 'Zeev Vax' <zeevvax@microsoft.com>, "'Bill Ver Steeg (versteb)'" <versteb@cisco.com>, "'Dave Oran (oran)'" <oran@cisco.com>
Message-id: <017f01c9fa09$1317db30$39479190$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AQHJ+XGL55qnQXLLnEGrAy1spvMJMJBfirkA//+t9sCAADJukIAAYNvwgABSz+A=
iPlanet-SMTP-Warning: Lines longer than SMTP allows found and truncated.
References: <mailman.10085.1245185397.4936.avt@ietf.org> <238382595265324EA50F6134BB42DCAF04046DCF@FRVELSMBS22.ad2.ad.alcatel.com> <015d01c9ef3e$13f25830$3bd70890$%roni@huawei.com> <238382595265324EA50F6134BB42DCAF040470B3@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54098D86E4@xmb-sjc-215.amer.cisco.com> <81B9B88E2F9D574AA5328A85547CDE910174E7C8@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F1174CCA3@tk5ex14mbxc105.redmond.corp.microsoft.com> <025401c9effa$34040170$9c0c0450$%roni@huawei.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC5C1E@tk5ex14mbxc105.redmond.corp.microsoft.com> <04CAD96D4C5A3D48B1919248A8FE0D540995BF39@xmb-sjc-215.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15EC6F77@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91017F57DA@xmb-rtp-21d.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04137224@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D54099DFD1A@xmb-sjc-215.amer.cisco.com> <"04CA D96D4C5 00C4"@xmb-sjc-215.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04186C7F@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D5409A71F22@xmb-sjc-215.amer.cisco.com> <00e601c9f971$6a7b0e80$3f712b80$%roni@huawei.com> <83D31F7D-8D4C-44D1-9AD3-814C4776922F@cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED2A46@tk5ex14mbxc105.redmond.corp.microsoft.com> <81B9B88E2F9D574AA5328A85547CDE91018C6ABD@xmb-rtp-21d.amer.cisco.com> <3B2FD2F513F8E1468C1A9FAE0C61BF2F15ED30B5@tk5ex14mbxc105.redmond.corp.microsoft.com>
Cc: 'VAN CAENEGEM Tom' <Tom.Van_Caenegem@alcatel-lucent.be>, avt@ietf.org
Subject: Re: [AVT] Port mappings, NAT, and RAMS
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, 01 Jul 2009 05:01:58 -0000

Zeev,
The IETF has worked on it as part of BEHAVE WG and defined ICE for SDP based
systems
Roni

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Zeev Vax
> Sent: Wednesday, July 01, 2009 4:13 AM
> To: Bill Ver Steeg (versteb); Dave Oran (oran); Roni Even
> Cc: VAN CAENEGEM Tom; avt@ietf.org
> Subject: Re: [AVT] Port mappings, NAT, and RAMS
> 
> I agree IETF is the right form, but I'm not sure the AVT WG is the
> right form as I think it is more general problem.
> 
> Zeev
> 
> -----Original Message-----
> From: Bill Ver Steeg (versteb) [mailto:versteb@cisco.com]
> Sent: Tuesday, June 30, 2009 2:14 PM
> To: Zeev Vax; Dave Oran (oran); Roni Even
> Cc: Ali C. Begen (abegen); VAN CAENEGEM Tom; avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
> 
> I agree that we should make a general solution for mapping unicast
> sessions onto unicast sessions.
> 
> We need to solve this problem using data flows that will work across
> multiple vendors' solutions, and thus need to do it in a standards
> forum. The IETF is the correct place to do this.
> 
> Bill VerSteeg
> 
> -----Original Message-----
> From: Zeev Vax [mailto:zeevvax@microsoft.com]
> Sent: Tuesday, June 30, 2009 9:07 AM
> To: Dave Oran (oran); Roni Even
> Cc: Ali C. Begen (abegen); 'VAN CAENEGEM Tom'; Bill Ver Steeg
> (versteb);
> avt@ietf.org
> Subject: RE: [AVT] Port mappings, NAT, and RAMS
> 
> I agree this should be a separate draft and we should work on a more
> generic mechanism.
> Two comments I have, first being a general problem it might have been
> solved already so I think we should research the area before investing
> in another draft. Second given such functionality is typically part of
> an application and not staying only in the lower network layers, the
> application can solve it as part of the startup sequence or other data
> delivery mechanism it has.
> 
> Zeev
> 
> -----Original Message-----
> From: David R Oran [mailto:oran@cisco.com]
> Sent: Tuesday, June 30, 2009 6:10 AM
> To: Roni Even
> Cc: 'Ali C. Begen (abegen)'; 'VAN CAENEGEM Tom'; 'Bill Ver Steeg
> (versteb)'; Zeev Vax; avt@ietf.org
> Subject: Re: [AVT] Port mappings, NAT, and RAMS
> 
> 
> On Jun 30, 2009, at 6:55 AM, Roni Even wrote:
> 
> > Hi guys,
> > My view is that this is not a general NACK problem but only for the
> > case of SSM and retransmission with similar box architecture to the
> > RAMS solution.
> > If you have another case please explain
> I believe it is actually a MORE general problem than NACK or RAMS. I
> arises from mixing SSM sessions and unicast sessions for the same RTP-
> based application. That's because multicast enforces port symmetry
> among
> all the receivers while unicast needs per-receiver port selection.
> 
> So far we have two uses for mixing multicast and unicast:
> retransmission-based repair, and RAMS. I suspect more uses will arise
> in
> the future. I can think of a few off the top of my head:
> - customized per-user overlays (e.g. to be alpha-blended with the
> video) or object-level replacement
> - network-coded error recovery streams
> - extra media info for re-integration when switching back from unicast
> to multicast in a fast-forward-to-realtime capability when doing
> "pause-live-content" style services
> - adaptive switching between multicast and unicast based on number of
> simultaneous receivers.
> 
> I have a strong intuition that doing a generic mechanism to atomically
> signal ports for unicast sessions using the RTCP feedback machinery of
> the SSM session would be highly advisable.
> 
> So, I think:
> a) we need to solve this problem
> b) it exists even in the absence of NATs
> c) we need a generic mechanism
> d) it should be documented in a separate draft, and not part of RAMs or
> AVPF.
> 
> If we can agree to these points, then we can have a more detailed
> discussion of the appropriate machinery. I have opinions on that
> subject
> too.
> 
> DaveO.
> 
> 
> 
> > Roni
> >
> >> -----Original Message-----
> >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
> Of
> 
> >> Ali C. Begen (abegen)
> >> Sent: Tuesday, June 30, 2009 10:19 AM
> >> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni Even;
> >> avt@ietf.org
> >> Subject: Re: [AVT] Port mappings, NAT, and RAMS
> >>
> >> Hi Tom,
> >>
> >> Let's get the input from the WG on these points. I believe going for
> >> a more general solution that will be applicable to both RAMS and
> NACK
> 
> >> is more desirable.
> >>
> >> BR,
> >> -acbegen
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: VAN CAENEGEM Tom [mailto:Tom.Van_Caenegem@alcatel-lucent.be]
> >>> Sent: Monday, June 29, 2009 9:17 AM
> >>> To: Ali C. Begen (abegen); Bill Ver Steeg (versteb); Zeev Vax; Roni
> >> Even; avt@ietf.org
> >>> Subject: RE: Port mappings, NAT, and RAMS
> >>>
> >>>
> >>> Ali,
> >>>
> >>> See some comments below (TOM).
> >>>
> >>> -----Original Message-----
> >>> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> >>> Sent: vrijdag 26 juni 2009 17:41
> >>> To: VAN CAENEGEM Tom; Bill Ver Steeg (versteb); Zeev Vax; Roni
> Even;
> 
> >>> avt@ietf.org
> >>> Subject: RE: Port mappings, NAT, and RAMS
> >>>
> >>> Hi Tom,
> >>>
> >>> [snip]
> >>>> The reason why we need pubports is that it indicates "explicitly"
> >> the
> >>>> port the client wants to use to receive the burst is the port it
> >> used
> >>>> to send the RAMS-R/pubports message. I believe we need this
> >> explicit
> >>>> indication, ow, we will be making an implicit assumption. Note
> that
> 
> >>>> the rams-r/pubports is in the primary session and burst/ret
> packets
> 
> >>>> are in the retransmission session, which is different than the
> >>> primary.
> >>>>
> >>>> As far as I can see, not everybody agrees on this point, but we
> >> need
> >>>> to make a decision here before we mandate anything.
> >>>>
> >>>> TOM: I agree with your last line, but I do not completely agree
> >> when
> >>>> you mention "implicit" assumption, especially for option 3, where
> >>>> RAMS-R (or
> >>>> NACK) and the Pub-port message are in the same compound message.
> If
> >> we
> >>>
> >>>> "define" that if no pub-report message is sent by the RR, the
> >>>> information towards the Retransmission server is exactly the same
> >> as
> >>>> when an RTP receiver sends an RTCP compound message made up of an
> >> RTCP
> >>>
> >>>> NACK/RAMS-R together with a pub-port message where the ports are
> >>> "zero"
> >>>
> >>> We "may" be able to say it from RAMS-R but not for NACK since we
> are
> >> not
> >>> defining it, we will be overloading its meaning, IMO. And as you/
> >>> Bill pointed out in other emails, I also believe that this is more
> >>> general problem than just RAMS. We need something like pubports for
> >>> NACKs as well.
> >>>
> >>>
> >>> TOM: indeed, that is why IMO we should define this problem and
> >> solution
> >>> in a separate draft which applies to any system architecture where
> a
> 
> >>> unicast session from a FT is coupled to a ssm session with that
> same
> >> FT.
> >>>
> >>>
> >>>> -as currently proposed in the RAMS draft now.  I agree that this
> is
> 
> >>>> not true for option 4, where pub-port and RAMS-R or NACK are
> >> separate
> >>>> messages, but I do not favour the solution of option 4 for the
> same
> 
> >>>> reason you mention in your reply (a new failure mode). So, if
> >> option 4
> >>>
> >>>> is -for that reason- no longer considered, I do not see a problem
> >> with
> >>>
> >>>> defining this rule/clause as expressed above. In other words,
> there
> >> is
> >>>
> >>>> no need for a pub-report message in this scenario and this results
> >> NOT
> >>>
> >>>> in an "assumption" what-so-ever.
> >>>>
> >>>>
> >>>>> supports RTP/RTCP muxing itself, and if it knows the RS supports
> >>>>> RTP/RTCP muxing too (as indicated in the declarative sdp received
> >> by
> >>>
> >>>>> the
> >>>>> RR)
> >>>>>
> >>>>> -Don't we also allow that for option 3, the port P2 actually
> >> equals
> >>>>> port P4? This is a kind of hybrid of session and SSRC
> >> multiplexing
> >>>>> of the primary multicast RTP stream and the
> >>>>> retransmission/acceleration session
> >>>>> :  on the unidirectional RTP layer, the primary MC packets and
> >> the
> >>>>> unicast retransmission packets are clearly session muxed, but the
> >>>>> RTCP
> >>>>
> >>>>> "return" channel for both streams have exactly the same transport
> >>>>> addresses, but are distinguished by means of a different SSRC.
> >> In
> >>>>> that
> >>>>
> >>>> How? Since SSM and retransmission sessions are session muxed, they
> >>>> have the same SSRC. When a client is sending a receiver report,
> how
> >> do
> >>>
> >>>> we identify which session it belongs to? So, I believe P2 should
> be
> 
> >>>> different than P4.
> >>>>
> >>>> TOM: you are right. But notice this: RFC 4588 mandates that when
> >>>> session muxing is used for retransmission, than the SSRC should be
> >> the
> >>> same.
> >>>> However the RFC 4588 does not give arguments why it needs to be
> >> like
> >>>> that. So I ask you: what would or can happen if there is a
> >> different
> >>>> SSRC used?  If there are no convincing arguments why we must stick
> >> to
> >>>
> >>> Good question. If we don't use the same SSRC in session-muxed RTP
> >>> sessions, it will introduce correlation problems. Receiver/XR
> >>> reports coming from a larger number of receivers will be difficult
> >>> to
> >> identify
> >>> and match at the server side. There will be SSRC collisions, which
> >> will
> >>> complicate things further.
> >>>
> >>> TOM: the big difference with when the RFC 4588 was being discussed
> >> and
> >>> developed, is that now we are capable of advertising in SDP the
> SSRC
> >> of
> >>> the media server, that is in this case the retransmission server
> >>> SSRC used in the retransmission session. In fact for RAMS, we need
> >>> to
> >> define
> >>> the SSRC of the ssm RTP session, so we can as well do it for the
> >>> retransmission session. Perhaps we should consider this different
> >> SSRC
> >>> possibility (hence violating RFC 4588) as part of a new draft, the
> >> one I
> >>> mentioned above.
> >>>
> >>>
> >>>> the same SSRC, then, if we have a good use case to depart from
> that
> 
> >>>> "rule" -and the use case we are discussing here is IMO indeed a
> >> valid
> >>>> use case- I do not see why we should be limited by such a "rule".
> >> The
> >>>> "valid" use case is here that RAMS and Retransmission for SSM
> >> sessions
> >>>
> >>>> operates fine through any NAPT and without any dedicated RTCP
> >> message.
> >>>
> >>> -acbegen
> >> _______________________________________________
> >> Audio/Video Transport Working Group
> >> avt@ietf.org
> >> https://www.ietf.org/mailman/listinfo/avt
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
> 
> 
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt

