
From Even.roni@huawei.com  Tue Nov  1 05:51:19 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC78011E8882 for <avt@ietfa.amsl.com>; Tue,  1 Nov 2011 05:51:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.335
X-Spam-Level: 
X-Spam-Status: No, score=-105.335 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_TAG_BALANCE_BODY=1.263, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F6AunXmvLvcP for <avt@ietfa.amsl.com>; Tue,  1 Nov 2011 05:51:18 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 71CE511E887F for <avt@ietf.org>; Tue,  1 Nov 2011 05:51:18 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LTZ00II2FPALV@szxga05-in.huawei.com> for avt@ietf.org; Tue, 01 Nov 2011 20:51:10 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LTZ006KRFPAE5@szxga05-in.huawei.com> for avt@ietf.org; Tue, 01 Nov 2011 20:51:10 +0800 (CST)
Received: from windows8d787f9 ([109.65.207.242]) by szxml11-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LTZ00BCWFP5Y4@szxml11-in.huawei.com>; Tue, 01 Nov 2011 20:51:10 +0800 (CST)
Date: Tue, 01 Nov 2011 14:48:43 +0200
From: Roni Even <Even.roni@huawei.com>
To: avt@ietf.org
Message-id: <01cf01cc9894$99858d30$cc90a790$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/mixed; boundary="Boundary_(ID_plDMVtu7DN4DCbDrU/aiBw)"
Content-language: en-us
Thread-index: AcyYlJSrPSGveu0NRPKAJE4cdJKyCg==
Cc: 'Magnus Westerlund' <magnus.westerlund@ericsson.com>
Subject: [AVTCORE] AVTcore Agenda for IETF82
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 01 Nov 2011 12:51:19 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_plDMVtu7DN4DCbDrU/aiBw)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_0ocFumvSTx2n4nz5+jbknA)"


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

Hi,

This is the proposed agenda for the AVTcore session based on the requests we
got. Attached are the txt and HTML version

We will have a busy schedule and the topics are ordered by priority with WG
documents first.

 

 

Audio/Video Transport Core Maintenance  (AVTCore) Working Group

===============================================================

 

CHAIRS:  Magnus Westerlund       <magnus.westerlund@ericsson.com>

         Roni Even         <even.roni@huawei.com>

 

AGENDA

 

Monday, 14 November 2011 at 13:00-15:00 (101 C)

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

13:00   AVTCore Status Update                               (Chairs, 10)

 

13:10   ECN for RTP over UDP                     (Magnus Westerlund, 15)

        draft-ietf-avtcore-ecn-for-rtp-05

 

13:25   RTCP Extension for Feedback Suppression Indication  (Qin Wu, 15)

        draft-ietf-avtcore-feedback-supression-rtp-08

 

13:40   Monitoring Architecture for RTP                     (Qin Wu, 10)

        draft-ietf-avtcore-monarch-05

 

13:50   RTCP for inter-destination media synchronization(Ray van
Brandenburg, 10)

        draft-ietf-avtcore-idms-02

 

14:00   RTP Multiplexing Architecture           (Magnus Westerlund , 25)

        draft-westerlund-avtcore-multiplex-architecture-00

 

14:25   Multiple RTP Session on a Single Lower-Layer Transport(Magnus
Westerlund , 15)

        draft-westerlund-avtcore-transport-multiplexing-01

 

14:40   Duplicating RTP Streams                              (Begen, 10)

        draft-begen-avtcore-rtp-duplication-00

 

14:50   Multipath RTP                                  (Varun Singh, 10)

        draft-singh-avt-mprtp-03

 

15:00   End

 

 

Thanks

Magnus Westerlund and Roni Even.

 

 


--Boundary_(ID_0ocFumvSTx2n4nz5+jbknA)
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 WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></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=WordSection1><p class=MsoNormal>Hi,<o:p></o:p></p><p class=MsoNormal>This is the proposed agenda for the AVTcore session based on the requests we got. Attached are the txt and HTML version<o:p></o:p></p><p class=MsoNormal>We will have a busy schedule and the topics are ordered by priority with WG documents first.<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>Audio/Video Transport Core Maintenance&nbsp; (AVTCore) Working Group<o:p></o:p></p><p class=MsoNormal>===============================================================<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>CHAIRS:&nbsp; Magnus Westerlund&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;magnus.westerlund@ericsson.com&gt;<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Roni Even&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb
 sp;&nbsp
wei.com&gt;<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>AGENDA<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Monday, 14 November 2011 at 13:00-15:00 (101 C)<o:p></o:p></p><p class=MsoNormal>-----------------------------------------------<o:p></o:p></p><p class=MsoNormal>13:00&nbsp;&nbsp; AVTCore Status Update&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (Chairs, 10)<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>13:10&nbsp;&nbsp; ECN for RTP over UDP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (Magnus Westerlund, 15)<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; draft-ietf-avtcore-ecn-for-rtp-05<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=M
 soNormal
xtension for Feedback Suppression Indication&nbsp; (Qin Wu, 15)<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; draft-ietf-avtcore-feedback-supression-rtp-08<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>13:40&nbsp;&nbsp; Monitoring Architecture for RTP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (Qin Wu, 10)<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; draft-ietf-avtcore-monarch-05<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>13:50&nbsp;&nbsp; RTCP for inter-destination media synchronization(Ray van Brandenburg, 10)<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; draft-ietf-avtcore-idms-02<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>14:00&nbsp;&nbsp; RTP Multiplexing Architecture &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp
 ;&nbsp;(
:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; draft-westerlund-avtcore-multiplex-architecture-00<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>14:25&nbsp;&nbsp; Multiple RTP Session on a Single Lower-Layer Transport(Magnus Westerlund , 15)<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; draft-westerlund-avtcore-transport-multiplexing-01<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>14:40&nbsp;&nbsp; Duplicating RTP Streams&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (Begen, 10)<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; draft-begen-avtcore-rtp-duplication-00<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>14:50&nbsp;&nbsp; Multipath RTP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp
 ;&nbsp;&
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (Varun Singh, 10)<o:p></o:p></p><p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; draft-singh-avt-mprtp-03<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>15:00&nbsp;&nbsp; End<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>Thanks<o:p></o:p></p><p class=MsoNormal>Magnus Westerlund and Roni Even.<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p></div></body></html>

--Boundary_(ID_0ocFumvSTx2n4nz5+jbknA)--

--Boundary_(ID_plDMVtu7DN4DCbDrU/aiBw)
Content-type: text/plain; name=a1111.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=a1111.txt

Audio/Video Transport Core Maintenance  (AVTCore) Working Group
===============================================================

CHAIRS:  Magnus Westerlund       <magnus.westerlund@ericsson.com>
         Roni Even         <even.roni@huawei.com>

AGENDA

Monday, 14 November 2011 at 13:00-15:00 (101 C)
-----------------------------------------------
13:00   AVTCore Status Update                               (Chairs, 10)

13:10   ECN for RTP over UDP                     (Magnus Westerlund, 15)
        draft-ietf-avtcore-ecn-for-rtp-05

13:25   RTCP Extension for Feedback Suppression Indication  (Qin Wu, 15)
        draft-ietf-avtcore-feedback-supression-rtp-08

13:40   Monitoring Architecture for RTP                     (Qin Wu, 10)
        draft-ietf-avtcore-monarch-05

13:50   RTCP for inter-destination media synchronization(Ray van Brandenburg, 10)
        draft-ietf-avtcore-idms-02

14:00   RTP Multiplexing Architecture           (Magnus Westerlund , 25)
        draft-westerlund-avtcore-multiplex-architecture-00

14:25   Multiple RTP Session on a Single Lower-Layer Transport(Magnus Westerlund , 15)
        draft-westerlund-avtcore-transport-multiplexing-01

14:40   Duplicating RTP Streams                              (Begen, 10)
        draft-begen-avtcore-rtp-duplication-00

14:50   Multipath RTP                                  (Varun Singh, 10)
        draft-singh-avt-mprtp-03

15:00   End

--Boundary_(ID_plDMVtu7DN4DCbDrU/aiBw)
Content-type: text/html; name=a1111.html
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=a1111.html

<html>
<head>
<title>Audio/Video Transport Core Maintenance  (AVTCore) Working Group Agenda</title>
</head>
<body bgcolor="#ffffff"><h1>Audio/Video Transport Core Maintenance  (AVTCore) Working Group Agenda</h1>
<hr>
<p>
<h3>
Chairs: Magnus Westerlund       <magnus.westerlund@ericsson.com>, Roni Even         <even.roni@huawei.com>
</h3>
<p>
<h2>Monday, 14 November 2011 at 13:00-15:00 (101 C)</h2>
<p>
<table border="0" cellpadding="5">
<tr>
<th align="left">13:00
<th align="left">AVTCore Status Update<th align="left">Chairs
<tr>
<th align="left">13:10
<th align="left">ECN for RTP over UDP<th align="left">Magnus Westerlund
<tr>
<td align="left">
<td align="left"><a href="http://tools.ietf.org/id/draft-ietf-avtcore-ecn-for-rtp-05">draft-ietf-avtcore-ecn-for-rtp-05</a>
<tr>
<th align="left">13:25
<th align="left">RTCP Extension for Feedback Suppression Indication<th align="left">Qin Wu
<tr>
<td align="left">
<td align="left"><a href="http://tools.ietf.org/id/draft-ietf-avtcore-feedback-supression-rtp-08">draft-ietf-avtcore-feedback-supression-rtp-08</a>
<tr>
<th align="left">13:40
<th align="left">Monitoring Architecture for RTP<th align="left">Qin Wu
<tr>
<td align="left">
<td align="left"><a href="http://tools.ietf.org/id/draft-ietf-avtcore-monarch-05">draft-ietf-avtcore-monarch-05</a>
<tr>
<th align="left">13:50
<th align="left">RTCP for inter-destination media synchronization<th align="left">Ray van Brandenburg
<tr>
<td align="left">
<td align="left"><a href="http://tools.ietf.org/id/draft-ietf-avtcore-idms-02">draft-ietf-avtcore-idms-02</a>
<tr>
<th align="left">14:00
<th align="left">RTP Multiplexing Architecture<th align="left">Magnus Westerlund 
<tr>
<td align="left">
<td align="left"><a href="http://tools.ietf.org/id/draft-westerlund-avtcore-multiplex-architecture-00">draft-westerlund-avtcore-multiplex-architecture-00</a>
<tr>
<th align="left">14:25
<th align="left">Multiple RTP Session on a Single Lower-Layer Transport<th align="left">Magnus Westerlund 
<tr>
<td align="left">
<td align="left"><a href="http://tools.ietf.org/id/draft-westerlund-avtcore-transport-multiplexing-01">draft-westerlund-avtcore-transport-multiplexing-01</a>
<tr>
<th align="left">14:40
<th align="left">Duplicating RTP Streams<th align="left">Begen
<tr>
<td align="left">
<td align="left"><a href="http://tools.ietf.org/id/draft-begen-avtcore-rtp-duplication-00">draft-begen-avtcore-rtp-duplication-00</a>
<tr>
<th align="left">14:50
<th align="left">Multipath RTP <th align="left">Varun Singh
<tr>
<td align="left">
<td align="left"><a href="http://tools.ietf.org/id/draft-singh-avt-mprtp-03">draft-singh-avt-mprtp-03</a>
<tr>
<th align="left">15:00
<th align="left">End</table>

--Boundary_(ID_plDMVtu7DN4DCbDrU/aiBw)--

From rjsparks@nostrum.com  Tue Nov  1 08:50:40 2011
Return-Path: <rjsparks@nostrum.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65F491F0C44; Tue,  1 Nov 2011 08:50:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ow7nwSYAaBgb; Tue,  1 Nov 2011 08:50:39 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6288C11E80AB; Tue,  1 Nov 2011 08:50:30 -0700 (PDT)
Received: from [192.168.2.105] (pool-173-74-105-241.dllstx.fios.verizon.net [173.74.105.241]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id pA1FoSUL080731 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 1 Nov 2011 10:50:29 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <20111031132810.20293.12093.idtracker@ietfa.amsl.com>
Date: Tue, 1 Nov 2011 10:50:28 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <9AA22A68-6D9C-4709-964A-24693B7EE8DA@nostrum.com>
References: <20111031132810.20293.12093.idtracker@ietfa.amsl.com>
To: Pete Resnick <presnick@qualcomm.com>
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 173.74.105.241 is authenticated by a trusted mechanism)
Cc: draft-ietf-avtcore-srtp-vbr-audio@tools.ietf.org, avtcore-chairs@tools.ietf.org, IETF AVTCORE WG <avt@ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [AVTCORE] Pete Resnick's Discuss on draft-ietf-avtcore-srtp-vbr-audio-03: (with DISCUSS)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 01 Nov 2011 15:50:40 -0000

AVTCORE Working Group:

Pete is making an argument that the text in this document could be =
published as Standards Track. We've walked through the normative =
statements
in the document together and I see his argument. My only concern is =
whether there is any intent in the document to tell operators of =
existing deployments
to go change their configuration right away to avoid the security issues =
the document describes. Pete rightly points out that, as written, the =
document is=20
providing guidance to new implementers, not to current operators.

Does anyone believe moving this to the Standards Track is the wrong =
thing to do?
Do you think the document needs to say anything more strongly about =
current deployments?

RjS


On Oct 31, 2011, at 8:28 AM, Pete Resnick wrote:

> Pete Resnick has entered the following ballot position for
> draft-ietf-avtcore-srtp-vbr-audio-03: Discuss
>=20
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut =
this
> introductory paragraph, however.)
>=20
> Please refer to =
http://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>=20
>=20
>=20
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>=20
> I don't see how this is remotely a BCP. This should be on the =
standards track. It is specifying all sorts of implementation parameters =
that are clearly testable, may have interoperability implications, and =
may change over time as we get implementation experience. (E.g., the =
length of the overhang period may be something that we specify =
differently, whether VAD is used or not may have interoperability =
implications, etc.). This discussion would have normally happened in the =
context of a security considerations section of a base protocol document =
and would have gone along the standards track with the base protocol. =
The fact that it is being published separately shouldn't change its =
treatment.
>=20
>=20
>=20
>=20


From magnus.westerlund@ericsson.com  Wed Nov  2 02:55:52 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C1DE11E8163 for <avt@ietfa.amsl.com>; Wed,  2 Nov 2011 02:55:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.264
X-Spam-Level: 
X-Spam-Status: No, score=-106.264 tagged_above=-999 required=5 tests=[AWL=-0.265, BAYES_00=-2.599, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id azzbVKnPvYKV for <avt@ietfa.amsl.com>; Wed,  2 Nov 2011 02:55:51 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id A743B11E8142 for <avt@ietf.org>; Wed,  2 Nov 2011 02:55:50 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-3a-4eb113a58cd4
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id A2.09.13753.5A311BE4; Wed,  2 Nov 2011 10:55:49 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.3.137.0; Wed, 2 Nov 2011 10:55:48 +0100
Message-ID: <4EB113A4.4080606@ericsson.com>
Date: Wed, 2 Nov 2011 10:55:48 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: "fboronat@dcom.upv.es" <fboronat@dcom.upv.es>
References: <mailman.2165.1319035300.3002.avt@ietf.org> <4E9F1D69.2060703@dcom.upv.es>
In-Reply-To: <4E9F1D69.2060703@dcom.upv.es>
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] Possible Additional functionalities for draft-brandenburg-avt-rtcp-for-idms
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 02 Nov 2011 09:55:52 -0000

On 2011-10-19 20:56, Fernando Boronat Seguí wrote:
> Magnus,
> 
> Yes, you are right. That is our purpose.
> 
> What do you think about our proposal? Any suggestion will be much
> appreciated.

I do think the basic problem is a relevant one for any use cases where
having less than perfect playout sync at startup is not acceptable. For
example for the distributed loud speaker use case.

Then how common that use case is. And if the simplest way of resolving
this is simply to mandate the end-point to support the RTCP XR DLRR (RFC
3611) mechanism to enable them to determine all the transport delays
between the nodes.

Cheers

Magnus

> 
> Thank you for your response.
> 
> 
> El 19/10/2011 16:41, avt-request@ietf.org escribió:
>> Date: Wed, 19 Oct 2011 11:15:40 +0200
>> From: Magnus Westerlund <magnus.westerlund@ericsson.com>
>> To: avt@ietf.org
>> Subject: Re: [AVTCORE] Possible Additional functionalities for
>> 	draft-brandenburg-avt-rtcp-for-idms
>> Message-ID: <4E9E953C.507@ericsson.com>
>> Content-Type: text/plain; charset="windows-1252"
>>
>> Hi,
>>
>> If I understand the main issue you have is to determine the set of
>> transmission delays from a given media source to its population of
>> receivers so that an appropriate playout time can be selected by the
>> media source prior to actually having sent any media?
>>
>> Cheers
>>
>> Magnus
>>
>> On 2011-10-11 15:37, Fernando Boronat Segu? wrote:
>>> Dear Group members,
>>>
>>> As this is our first mail to the list, we introduce ourselves. We are 
>>> Fernando Boronat and Mario Montagud, co-authors of the Internet Draft 
>>> (I-D) ?RTCP for inter-destination media synchronization? 
>>> (draft-ietf-avtcore-idms-01.txt).
>>> As the I-D was accepted as a WG document, any changes will have to be 
>>> approved by the AVTCORE group. So, we would like to know if you consider 
>>> appropriate to introduce some additional functionalities to the proposed 
>>> IDMS approach in the I-D.
>>>
>>> In many distributed applications it is required that all the receivers 
>>> start the playout of the media stream almost simultaneously (we refer 
>>> this as Coarse Sync) and, after that, all of them play-out the media in 
>>> a synchronous way (we refer this as Fine Sync). Those processes are 
>>> essential for acquiring IDMS. A Global Initial Playout Instant for all 
>>> the geographically distributed receivers (SCs) in a media session could 
>>> prevent from an initial playout time discrepancy (asynchrony) at the 
>>> beginning of the playout of the media stream/s (if a fixed global 
>>> initial buffering delay is set) mainly due to the variable network 
>>> delays from the media server to each one of the SCs.
>>>
>>> Thus, we are thinking about including a new section in the I-D about 
>>> possible packets for Coarse Sync for both the initial playout instant 
>>> (at the begining of a media session) and the initial instant at each 
>>> stage in which the session can be divided (we consider that a stage ends 
>>> when no streams are transmitted during a fixed interval (it could be 
>>> defined depending on the applications), and that the next stage starts 
>>> when data is transmitted again).
>>>
>>> This technique has been considered in some previous IDMS works (see 
>>> reference [Boronat09] in the I-D), but using proprietary protocols. The 
>>> methods we propose here are based on the use of already defined and 
>>> standard RTCP packets, which would avoid the introduction of proprietary 
>>> closed solutions.
>>>
>>> Regarding the Initial Playout Instant, we have primarily thought about 
>>> the use of already proposed RTCP XR packets (RFC 3611):
>>>
>>> 1. Use of RTCP XR with RRTR and DLRR report blocks (defined RFC 3611) 
>>> for measuring the delay between MSAS and SCs, allowing MSAS to estimate 
>>> the RTT for all the SCs, then calculate a common initial playout instant 
>>> and then communicate it to all SCs by sending them an RTCP IDMS Packet 
>>> (defined in the I-D). The RTCP IDMS packet must include the RTP 
>>> Timestamp of the first MU to be sent by the source and its proper 
>>> playout instant, which will be common for all of them.
>>> MSAS may estimate its round trip time (RTT) to the SCs by sending them 
>>> an RTCP XR with the Receiver Reference Time Report Block and forcing 
>>> (according to RFC 3611) them to reply by sending an RTCP XR with a DLRR 
>>> Report Block. Notice that both XR blocks are defined in RFC 3611 to be 
>>> used in the opposite way we propose.
>>>
>>> If this solution is not considered appropriate we could think about 
>>> another solution based on the packets already defined in the I-D, but 
>>> maybe we would need to change the format adding new field/s.
>>>
>>> 2. Once joined the session, if it is not started yet, all the SCs could 
>>> start sending RTCP XR with IDMS block (until they receive the Initial 
>>> Playout Instant indication, sent using the RTCP IDMS Packet) as it is 
>>> defined in the I-D, but including only the essential timing information 
>>> (e.g. the wallclock time at which the packet is sent by the SC) to let 
>>> the MSAS estimate the one-way network delays (not round-trip as in the 
>>> previous case) for each SC (assuming symmetric delays as in TCP) and 
>>> calculate the Initial Playout Instant. For that purpose, some field of 
>>> the RTCP XR IDMS block should be used to indicate the XR IDMS block is 
>>> carrying out temporal information for Coarse Sync, and not for reporting 
>>> about arrival/playout timing of a specific RTP packet.
>>>  From the Initial Instant they will continue playing the streams and 
>>> sending the RTCP XR with IDMS complete block (as currently defined in 
>>> the I-D). It could be a possible solution.
>>>
>>> The process of the calculation of the optimum Initial Playout Instant 
>>> must take into consideration some factors such as the maximum and 
>>> minimum estimated delays, jitter values, expected duration of the 
>>> session, or probable clock deviations, in order to allow enough buffered 
>>> MUs to start the playout and to maintain it continuously, thus avoiding 
>>> underflow/overflow situations (playout discontinuities), during the 
>>> session. This process is out of the scope of the ID.
>>>
>>> With the introduction of the Coarse Sync functionality, the IDMS 
>>> proposal can counteract the effect of the delay variability at the 
>>> beginning of the playout of the media stream/s in each one of the stages 
>>> in which a media session can be divided.
>>>
>>> We prefer the first method because there is no need to define new IDMS 
>>> control messages (or to include some fields to already defined packets), 
>>> but the use of already defined RTCP reports (RFC 3611) can be adapted 
>>> for that purpose.
>>>
>>> Moreover, with the use of the first method, SCs do not have to send 
>>> control messages once they join the session, which may possibly result 
>>> on inefficient control traffic overhead. They will only have to send 
>>> RTCP XR DLRR messages in response to a new incoming RTRR message from 
>>> the source, which is who really knows the initial transmission time for 
>>> the RTP media stream. Moreover, the Initial Playout Instant can be sent 
>>> to the receivers by using the RTCP IDMS packet, already introduced in 
>>> the I-D.
>>>
>>> Feedback will be much appreciated.
>>>
>>> Regards
>>> ========================================================================
>>> Dr. Fernando Boronat Segu?
>>> IEEE Senior Member
>>> Profesor Titular / Lecturer
>>> Dept. Comunicaciones Tlf.-+34+962 849 300 Ext.-49341
>>> Tlf. directo -+34+962 849 341 Fax.-+34+962 849 309 (Compartido)
>>> UNIVERSIDAD POLIT?CNICA DE VALENCIA-CAMPUS DE GANDIA
>>> Calle Pararaninfo, 1, CP. 46730, Grao de Gandia (Valencia), SPAIN
>>> ========================================================================
>>> _______________________________________________
>>> Audio/Video Transport Core Maintenance
>>> avt@ietf.org
>>> https://www.ietf.org/mailman/listinfo/avt
>>>
>>
> 
> -- 
> Saludos/Regards
> ========================================================================
> Dr. Fernando Boronat Seguí
> Profesor Titular / Lecturer	
> Dept. Comunicaciones           Tlf.-+34+962 849 300 Ext.-49341
> Tlf. directo -+34+962 849 341  Fax.-+34+962 849 309 (Compartido)
> UNIVERSIDAD POLITÉCNICA DE VALENCIA-CAMPUS DE GANDIA
> Calle Pararaninfo, 1, CP. 46730, Grao de Gandia (Valencia), SPAIN
> ========================================================================
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From fboronat@dcom.upv.es  Wed Nov  2 03:46:11 2011
Return-Path: <fboronat@dcom.upv.es>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B672911E815E for <avt@ietfa.amsl.com>; Wed,  2 Nov 2011 03:46:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[AWL=0.418,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ibjA7DcY3StL for <avt@ietfa.amsl.com>; Wed,  2 Nov 2011 03:46:10 -0700 (PDT)
Received: from marfik.cc.upv.es (marfik.cc.upv.es [158.42.249.9]) by ietfa.amsl.com (Postfix) with ESMTP id C7C4111E8142 for <avt@ietf.org>; Wed,  2 Nov 2011 03:46:09 -0700 (PDT)
Received: from smtpx.upv.es (smtpxv.cc.upv.es [158.42.249.46]) by marfik.cc.upv.es (8.13.6/8.13.6) with ESMTP id pA2Ak6U4021260 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Nov 2011 11:46:06 +0100
Received: from smtp.upv.es (celaeno.cc.upv.es [158.42.249.55]) by smtpx.upv.es (8.14.3/8.14.3) with ESMTP id pA2Ak6Ok001990; Wed, 2 Nov 2011 11:46:06 +0100
Received: from [127.0.0.1] (fboronat2114.pc.upv.es [158.42.145.157]) by smtp.upv.es (8.13.6/8.13.6) with ESMTP id pA2Ak4ZI018044; Wed, 2 Nov 2011 11:46:05 +0100
Message-ID: <4EB11FAA.4070807@dcom.upv.es>
Date: Wed, 02 Nov 2011 11:47:06 +0100
From: =?ISO-8859-1?Q?Fernando_Boronat_Segu=ED?= <fboronat@dcom.upv.es>
Organization: UNIVERSIDAD =?ISO-8859-1?Q?POLIT=C9CNICA_DE_VALENCIA?=
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, avt@ietf.org
References: <mailman.2165.1319035300.3002.avt@ietf.org> <4E9F1D69.2060703@dcom.upv.es> <4EB113A4.4080606@ericsson.com>
In-Reply-To: <4EB113A4.4080606@ericsson.com>
Content-Type: multipart/alternative; boundary="------------050607080105090007060007"
Subject: Re: [AVTCORE] Possible Additional functionalities for draft-brandenburg-avt-rtcp-for-idms
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: fboronat@dcom.upv.es
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 02 Nov 2011 10:46:11 -0000

This is a multi-part message in MIME format.
--------------050607080105090007060007
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Dear Magnus,

Thank you for your answer.

After some discussion about it, in a recent post to the list we have 
suggested two possible valid methods to be discussed (one proposed by me 
and other proposed by Kevin Gross). Ray Brandenburg will present them in 
Taipei IETF meeting to get some feedback (if he has enough time).

We discarded the use of RTCP XR DLRR reports, as I proposed at first, 
because they will be useful to obtain RTT but no one-way delay we are 
interested in.

Regards
Fernando Boronat



El 02/11/2011 10:55, Magnus Westerlund escribió:
> On 2011-10-19 20:56, Fernando Boronat Seguí wrote:
>> Magnus,
>>
>> Yes, you are right. That is our purpose.
>>
>> What do you think about our proposal? Any suggestion will be much
>> appreciated.
> I do think the basic problem is a relevant one for any use cases where
> having less than perfect playout sync at startup is not acceptable. For
> example for the distributed loud speaker use case.
>
> Then how common that use case is. And if the simplest way of resolving
> this is simply to mandate the end-point to support the RTCP XR DLRR (RFC
> 3611) mechanism to enable them to determine all the transport delays
> between the nodes.
>
> Cheers
>
> Magnus
>
>> Thank you for your response.
>>
>>
>> El 19/10/2011 16:41, avt-request@ietf.org escribió:
>>> Date: Wed, 19 Oct 2011 11:15:40 +0200
>>> From: Magnus Westerlund<magnus.westerlund@ericsson.com>
>>> To: avt@ietf.org
>>> Subject: Re: [AVTCORE] Possible Additional functionalities for
>>> 	draft-brandenburg-avt-rtcp-for-idms
>>> Message-ID:<4E9E953C.507@ericsson.com>
>>> Content-Type: text/plain; charset="windows-1252"
>>>
>>> Hi,
>>>
>>> If I understand the main issue you have is to determine the set of
>>> transmission delays from a given media source to its population of
>>> receivers so that an appropriate playout time can be selected by the
>>> media source prior to actually having sent any media?
>>>
>>> Cheers
>>>
>>> Magnus
>>>
>>> On 2011-10-11 15:37, Fernando Boronat Segu? wrote:
>>>> Dear Group members,
>>>>
>>>> As this is our first mail to the list, we introduce ourselves. We are
>>>> Fernando Boronat and Mario Montagud, co-authors of the Internet Draft
>>>> (I-D) ?RTCP for inter-destination media synchronization?
>>>> (draft-ietf-avtcore-idms-01.txt).
>>>> As the I-D was accepted as a WG document, any changes will have to be
>>>> approved by the AVTCORE group. So, we would like to know if you consider
>>>> appropriate to introduce some additional functionalities to the proposed
>>>> IDMS approach in the I-D.
>>>>
>>>> In many distributed applications it is required that all the receivers
>>>> start the playout of the media stream almost simultaneously (we refer
>>>> this as Coarse Sync) and, after that, all of them play-out the media in
>>>> a synchronous way (we refer this as Fine Sync). Those processes are
>>>> essential for acquiring IDMS. A Global Initial Playout Instant for all
>>>> the geographically distributed receivers (SCs) in a media session could
>>>> prevent from an initial playout time discrepancy (asynchrony) at the
>>>> beginning of the playout of the media stream/s (if a fixed global
>>>> initial buffering delay is set) mainly due to the variable network
>>>> delays from the media server to each one of the SCs.
>>>>
>>>> Thus, we are thinking about including a new section in the I-D about
>>>> possible packets for Coarse Sync for both the initial playout instant
>>>> (at the begining of a media session) and the initial instant at each
>>>> stage in which the session can be divided (we consider that a stage ends
>>>> when no streams are transmitted during a fixed interval (it could be
>>>> defined depending on the applications), and that the next stage starts
>>>> when data is transmitted again).
>>>>
>>>> This technique has been considered in some previous IDMS works (see
>>>> reference [Boronat09] in the I-D), but using proprietary protocols. The
>>>> methods we propose here are based on the use of already defined and
>>>> standard RTCP packets, which would avoid the introduction of proprietary
>>>> closed solutions.
>>>>
>>>> Regarding the Initial Playout Instant, we have primarily thought about
>>>> the use of already proposed RTCP XR packets (RFC 3611):
>>>>
>>>> 1. Use of RTCP XR with RRTR and DLRR report blocks (defined RFC 3611)
>>>> for measuring the delay between MSAS and SCs, allowing MSAS to estimate
>>>> the RTT for all the SCs, then calculate a common initial playout instant
>>>> and then communicate it to all SCs by sending them an RTCP IDMS Packet
>>>> (defined in the I-D). The RTCP IDMS packet must include the RTP
>>>> Timestamp of the first MU to be sent by the source and its proper
>>>> playout instant, which will be common for all of them.
>>>> MSAS may estimate its round trip time (RTT) to the SCs by sending them
>>>> an RTCP XR with the Receiver Reference Time Report Block and forcing
>>>> (according to RFC 3611) them to reply by sending an RTCP XR with a DLRR
>>>> Report Block. Notice that both XR blocks are defined in RFC 3611 to be
>>>> used in the opposite way we propose.
>>>>
>>>> If this solution is not considered appropriate we could think about
>>>> another solution based on the packets already defined in the I-D, but
>>>> maybe we would need to change the format adding new field/s.
>>>>
>>>> 2. Once joined the session, if it is not started yet, all the SCs could
>>>> start sending RTCP XR with IDMS block (until they receive the Initial
>>>> Playout Instant indication, sent using the RTCP IDMS Packet) as it is
>>>> defined in the I-D, but including only the essential timing information
>>>> (e.g. the wallclock time at which the packet is sent by the SC) to let
>>>> the MSAS estimate the one-way network delays (not round-trip as in the
>>>> previous case) for each SC (assuming symmetric delays as in TCP) and
>>>> calculate the Initial Playout Instant. For that purpose, some field of
>>>> the RTCP XR IDMS block should be used to indicate the XR IDMS block is
>>>> carrying out temporal information for Coarse Sync, and not for reporting
>>>> about arrival/playout timing of a specific RTP packet.
>>>>   From the Initial Instant they will continue playing the streams and
>>>> sending the RTCP XR with IDMS complete block (as currently defined in
>>>> the I-D). It could be a possible solution.
>>>>
>>>> The process of the calculation of the optimum Initial Playout Instant
>>>> must take into consideration some factors such as the maximum and
>>>> minimum estimated delays, jitter values, expected duration of the
>>>> session, or probable clock deviations, in order to allow enough buffered
>>>> MUs to start the playout and to maintain it continuously, thus avoiding
>>>> underflow/overflow situations (playout discontinuities), during the
>>>> session. This process is out of the scope of the ID.
>>>>
>>>> With the introduction of the Coarse Sync functionality, the IDMS
>>>> proposal can counteract the effect of the delay variability at the
>>>> beginning of the playout of the media stream/s in each one of the stages
>>>> in which a media session can be divided.
>>>>
>>>> We prefer the first method because there is no need to define new IDMS
>>>> control messages (or to include some fields to already defined packets),
>>>> but the use of already defined RTCP reports (RFC 3611) can be adapted
>>>> for that purpose.
>>>>
>>>> Moreover, with the use of the first method, SCs do not have to send
>>>> control messages once they join the session, which may possibly result
>>>> on inefficient control traffic overhead. They will only have to send
>>>> RTCP XR DLRR messages in response to a new incoming RTRR message from
>>>> the source, which is who really knows the initial transmission time for
>>>> the RTP media stream. Moreover, the Initial Playout Instant can be sent
>>>> to the receivers by using the RTCP IDMS packet, already introduced in
>>>> the I-D.
>>>>
>>>> Feedback will be much appreciated.
>>>>
>>>> Regards
>>>>
>>>> _______________________________________________
>>>> Audio/Video Transport Core Maintenance
>>>> avt@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>


--------------050607080105090007060007
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Times New Roman, Times, serif">Dear Magnus,<br>
      <br>
      Thank you for your answer.<br>
      <br>
      After some discussion about it, in a recent post to the list we
      have suggested two possible valid methods to be discussed (one
      proposed by me and other proposed by Kevin Gross). Ray Brandenburg
      will present them in Taipei IETF meeting to get some feedback (if
      he has enough time).<br>
      <br>
      We discarded the use of RTCP XR DLRR reports, as I proposed at
      first, because they will be useful to obtain RTT but no one-way
      delay we are interested in.<br>
      <br>
      Regards<br>
      Fernando Boronat<br>
      <br>
      <br>
    </font><br>
    El 02/11/2011 10:55, Magnus Westerlund escribi&oacute;:
    <blockquote cite="mid:4EB113A4.4080606@ericsson.com" type="cite">
      <pre wrap="">On 2011-10-19 20:56, Fernando Boronat Segu&iacute; wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">Magnus,

Yes, you are right. That is our purpose.

What do you think about our proposal? Any suggestion will be much
appreciated.
</pre>
      </blockquote>
      <pre wrap="">
I do think the basic problem is a relevant one for any use cases where
having less than perfect playout sync at startup is not acceptable. For
example for the distributed loud speaker use case.

Then how common that use case is. And if the simplest way of resolving
this is simply to mandate the end-point to support the RTCP XR DLRR (RFC
3611) mechanism to enable them to determine all the transport delays
between the nodes.

Cheers

Magnus

</pre>
      <blockquote type="cite">
        <pre wrap="">
Thank you for your response.


El 19/10/2011 16:41, <a class="moz-txt-link-abbreviated" href="mailto:avt-request@ietf.org">avt-request@ietf.org</a> escribi&oacute;:
</pre>
        <blockquote type="cite">
          <pre wrap="">Date: Wed, 19 Oct 2011 11:15:40 +0200
From: Magnus Westerlund <a class="moz-txt-link-rfc2396E" href="mailto:magnus.westerlund@ericsson.com">&lt;magnus.westerlund@ericsson.com&gt;</a>
To: <a class="moz-txt-link-abbreviated" href="mailto:avt@ietf.org">avt@ietf.org</a>
Subject: Re: [AVTCORE] Possible Additional functionalities for
	draft-brandenburg-avt-rtcp-for-idms
Message-ID: <a class="moz-txt-link-rfc2396E" href="mailto:4E9E953C.507@ericsson.com">&lt;4E9E953C.507@ericsson.com&gt;</a>
Content-Type: text/plain; charset="windows-1252"

Hi,

If I understand the main issue you have is to determine the set of
transmission delays from a given media source to its population of
receivers so that an appropriate playout time can be selected by the
media source prior to actually having sent any media?

Cheers

Magnus

On 2011-10-11 15:37, Fernando Boronat Segu? wrote:
</pre>
          <blockquote type="cite">
            <pre wrap="">Dear Group members,

As this is our first mail to the list, we introduce ourselves. We are 
Fernando Boronat and Mario Montagud, co-authors of the Internet Draft 
(I-D) ?RTCP for inter-destination media synchronization? 
(draft-ietf-avtcore-idms-01.txt).
As the I-D was accepted as a WG document, any changes will have to be 
approved by the AVTCORE group. So, we would like to know if you consider 
appropriate to introduce some additional functionalities to the proposed 
IDMS approach in the I-D.

In many distributed applications it is required that all the receivers 
start the playout of the media stream almost simultaneously (we refer 
this as Coarse Sync) and, after that, all of them play-out the media in 
a synchronous way (we refer this as Fine Sync). Those processes are 
essential for acquiring IDMS. A Global Initial Playout Instant for all 
the geographically distributed receivers (SCs) in a media session could 
prevent from an initial playout time discrepancy (asynchrony) at the 
beginning of the playout of the media stream/s (if a fixed global 
initial buffering delay is set) mainly due to the variable network 
delays from the media server to each one of the SCs.

Thus, we are thinking about including a new section in the I-D about 
possible packets for Coarse Sync for both the initial playout instant 
(at the begining of a media session) and the initial instant at each 
stage in which the session can be divided (we consider that a stage ends 
when no streams are transmitted during a fixed interval (it could be 
defined depending on the applications), and that the next stage starts 
when data is transmitted again).

This technique has been considered in some previous IDMS works (see 
reference [Boronat09] in the I-D), but using proprietary protocols. The 
methods we propose here are based on the use of already defined and 
standard RTCP packets, which would avoid the introduction of proprietary 
closed solutions.

Regarding the Initial Playout Instant, we have primarily thought about 
the use of already proposed RTCP XR packets (RFC 3611):

1. Use of RTCP XR with RRTR and DLRR report blocks (defined RFC 3611) 
for measuring the delay between MSAS and SCs, allowing MSAS to estimate 
the RTT for all the SCs, then calculate a common initial playout instant 
and then communicate it to all SCs by sending them an RTCP IDMS Packet 
(defined in the I-D). The RTCP IDMS packet must include the RTP 
Timestamp of the first MU to be sent by the source and its proper 
playout instant, which will be common for all of them.
MSAS may estimate its round trip time (RTT) to the SCs by sending them 
an RTCP XR with the Receiver Reference Time Report Block and forcing 
(according to RFC 3611) them to reply by sending an RTCP XR with a DLRR 
Report Block. Notice that both XR blocks are defined in RFC 3611 to be 
used in the opposite way we propose.

If this solution is not considered appropriate we could think about 
another solution based on the packets already defined in the I-D, but 
maybe we would need to change the format adding new field/s.

2. Once joined the session, if it is not started yet, all the SCs could 
start sending RTCP XR with IDMS block (until they receive the Initial 
Playout Instant indication, sent using the RTCP IDMS Packet) as it is 
defined in the I-D, but including only the essential timing information 
(e.g. the wallclock time at which the packet is sent by the SC) to let 
the MSAS estimate the one-way network delays (not round-trip as in the 
previous case) for each SC (assuming symmetric delays as in TCP) and 
calculate the Initial Playout Instant. For that purpose, some field of 
the RTCP XR IDMS block should be used to indicate the XR IDMS block is 
carrying out temporal information for Coarse Sync, and not for reporting 
about arrival/playout timing of a specific RTP packet.
 From the Initial Instant they will continue playing the streams and 
sending the RTCP XR with IDMS complete block (as currently defined in 
the I-D). It could be a possible solution.

The process of the calculation of the optimum Initial Playout Instant 
must take into consideration some factors such as the maximum and 
minimum estimated delays, jitter values, expected duration of the 
session, or probable clock deviations, in order to allow enough buffered 
MUs to start the playout and to maintain it continuously, thus avoiding 
underflow/overflow situations (playout discontinuities), during the 
session. This process is out of the scope of the ID.

With the introduction of the Coarse Sync functionality, the IDMS 
proposal can counteract the effect of the delay variability at the 
beginning of the playout of the media stream/s in each one of the stages 
in which a media session can be divided.

We prefer the first method because there is no need to define new IDMS 
control messages (or to include some fields to already defined packets), 
but the use of already defined RTCP reports (RFC 3611) can be adapted 
for that purpose.

Moreover, with the use of the first method, SCs do not have to send 
control messages once they join the session, which may possibly result 
on inefficient control traffic overhead. They will only have to send 
RTCP XR DLRR messages in response to a new incoming RTRR message from 
the source, which is who really knows the initial transmission time for 
the RTP media stream. Moreover, the Initial Playout Instant can be sent 
to the receivers by using the RTCP IDMS packet, already introduced in 
the I-D.

Feedback will be much appreciated.

Regards

_______________________________________________
Audio/Video Transport Core Maintenance
<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>
          <pre wrap="">
</pre>
        </blockquote>
        <pre wrap="">
</pre>
      </blockquote>
    </blockquote>
    <br>
  </body>
</html>

--------------050607080105090007060007--

From magnus.westerlund@ericsson.com  Thu Nov  3 06:27:54 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADA811F0C70 for <avt@ietfa.amsl.com>; Thu,  3 Nov 2011 06:27:54 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yeg4yJhg8FH5 for <avt@ietfa.amsl.com>; Thu,  3 Nov 2011 06:27:53 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 4F3ED1F0C81 for <avt@ietf.org>; Thu,  3 Nov 2011 06:27:53 -0700 (PDT)
X-AuditID: c1b4fb39-b7cb2ae000001bd8-70-4eb296cc202c
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 54.74.07128.CC692BE4; Thu,  3 Nov 2011 14:27:40 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.137.0; Thu, 3 Nov 2011 14:27:38 +0100
Message-ID: <4EB296C9.7030800@ericsson.com>
Date: Thu, 3 Nov 2011 14:27:37 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Roni Even <Even.roni@huawei.com>
References: <4E8D76C1.5080508@ericsson.com> <BAC40485A1FA456CA771192D4F750C77@china.huawei.com> <4E9E93A0.10701@ericsson.com> <07aa01cc925b$2f351930$8d9f4b90$%roni@huawei.com>
In-Reply-To: <07aa01cc925b$2f351930$8d9f4b90$%roni@huawei.com>
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: "draft-ietf-avtcore-feedback-supression-rtp@tools.ietf.org" <draft-ietf-avtcore-feedback-supression-rtp@tools.ietf.org>, 'IETF AVTCore WG' <avt@ietf.org>
Subject: Re: [AVTCORE] Comments on draft-ietf-avtcore-feedback-supression-rtp-07
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 03 Nov 2011 13:27:54 -0000

On 2011-10-24 16:42, Roni Even wrote:
> Hi Magnus,
> Maybe we can add a recommendation for SSM to use the round trip sub report
> block specified in section 7.1.6 of RFC 5760
> (http://tools.ietf.org/html/rfc5760 ) to distribute the RTT from the
> distribution source to the receivers.

Well, that report is really the distribution for the whole session. If
one actually want that it can't be combined with only reporting the
distribution for a subset of the participants.

Cheers

Magnus

> 
> Roni
> 
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
>> Magnus Westerlund
>> Sent: Wednesday, October 19, 2011 11:09 AM
>> To: Qin Wu
>> Cc: IETF AVTCore WG; draft-ietf-avtcore-feedback-supression-
>> rtp@tools.ietf.org
>> Subject: Re: [AVTCORE] Comments on draft-ietf-avtcore-feedback-
>> supression-rtp-07
>>
>> Hi,
>>
>> Sorry for the delay in following up.
>>
>> I have removed the issues which don't need further discussion.
>>
>>
>> On 2011-10-11 03:40, Qin Wu wrote:
>>> Hi, Magnus,
>>> Thank for your valuable review, please see my replies belows.
>>> ----- Original Message -----
>>> From: "Magnus Westerlund" <magnus.westerlund@ericsson.com
>>
>>> 2. Section 3.
>>>   "The timer value shall be
>>>    based on the observed round-trip time.  A receiver should compute
>> an
>>>    estimate of the round-trip time (RTT) to the sender of TPLR from
>> RTCP
>>>    report round-trip time if available, or its reception time of the
>>>    reflected RTCP FB message (e.g.,NACK), or any other means."
>>>
>>> We hade the discussion before but now that you clarified which RTT to
>> be
>>> used, I think it is worth having a discussion if that RTT is the
>> right
>>> one. So you suggest that the RTT between the sender of the TPLR and
>> the
>>> receiver of the message is the most appropriate to use when
>> suppressing
>>> the message. I am not certain that is the case.
>>>
>>> Lets consider the use cases. In the case of an intermediary in a
>>> distribution tree sending the TPLR and at the same time sending a
>> NACK
>>> upstream. Then the time until the retransmission reaches the
>> suppressed
>>> receiver is the time from the sending of the NACK up to the
>>> retransmitting entity and all the way down past the TPLR sender to
>> the
>>> suppressed receiver. The receiver may not have a true RTT to the
>>> original media sender as that source appears to live at the TPLR
>> sender,
>>> not further upstream.
>>>
>>> Yes, the sender of the TPLR and the receiver might at least have
>> mutual
>>> knowledge of each other, thus the TPLR sender is able to determine
>> the
>>> lowest RTT in the set of receviers thus determining how often to
>> repeat
>>> it to cover additional time requried for the upstream part of the
>>> request. But I do note that these times aren't matching what appear
>> to
>>> be the delays in the systems.
>>>
>>> Can we find a better solution?
>>>
>>>
>>> [Qin]: It looks to me the round trip time between media source and
>>>
>>>  intermediary is trivial if we assume the intermediary is much
>>>
>>> closer to the source, that is why I put the last paragraph in the
>>>
>>> section 3 as follows:
>>>
>>> “
>>>
>>> In order not to incur a lot of NACK requests due to additional TPLR
>>>
>>> described above, it is recommended that the RTP system sending
>>>
>>> TPLR should be implemented more closer to the source. Also when
>>>
>>>  the loss was detected and repair initiated much closer to the
>> source,
>>>
>>> the delay for the receiver to recover from packet loss can be reduced
>>>
>>> through the combination of intermediary feedback to the source and
>>>
>>> Third Party Loss Report downstream.
>>>
>>> ”
>>>
>>>
>>>
>>> If we look for a better solution, I think we have two possible ways:
>>>
>>> The first way is to rely on sender report from media sender to
>>>
>>> calculate the more approximate RTT from media sender to the receiver.
>>>
>>> RTT measurement method follows the same way described in the
>>>
>>> figure 2 of RFC3550.
>>>
>>>
>>>
>>> The second way is to we can allow the intermediary tell the receiver
>> the
>>>
>>> RTT from media source to intermediary itself by sending a new message
>>>
>>> since the intermediary can measure such RTT based on past observation
>>>
>>> and estimation. However for the second way we need to define new
>>>
>>> message or extend TPLR message to carry such RTT.
>>>
>>>
>>>
>>> What do you think?
>>>
>>
>> From follow up email:
>>> Hi,Magnus: As regarding if there is better solution, I have some
>>> corrections and additional thoughts.
>>> I think If the media source is the repair server, the receiver should
>>> set timer to T1=max(the RTT from media source to middlebox sending
>>> TPLR, 1/2 of RTT from middlebox to receiver) when the receiver
>>> receives first TPLR. When the receiver receive addtional TPLR within
>>> T1, the receiver should reset the timer to the RTT from media source
>>> to middlebox sending TPLR.
>>>
>>> If the middlebox is the repair server, the receiver should set the
>>> timer to T2=1/2 of RTT from middlebox to receiver when the receiver
>>> receives first TPLR. When the receiver receive addtional TPLR within
>>> T2, the receiver should reset the timer to the T2.
>>>
>>
>> Can you express these rules for the receiver as something that is based
>> on what is observable from the RTP and RTCP traffic? Is when media
>> server being repair server equal to TPLR sender SSRC = Media SSRC the
>> TPLR applies on? And if they are not the same it is the second case?
>>
>>
>>
>>>
>>>
>>> 3. Section 3:
>>>   "To increase the robustness to the loss of a TPLR or of a
>> transmission
>>>    packet, a receiver is allowed to receive additional TPLR for the
>> same
>>>    packet.  In the case the first TPLR is lost and the additional
>> TPLR
>>>    arrives at the receiver, the receiver should immediately refresh
>> the
>>>    timer."
>>>
>>> In the second sentence I don't see how the receiver can know that it
>> is
>>> a retransmission. It is simply a TPLR from its perspective if that is
>> lost.
>>>
>>> Robustness reasons is only one reason for repeating them the other is
>>> clearly to renew the timer. Thus I think the formulation should be
>> more
>>> generic to make it clear that all receivers should upon reception of
>> a
>>> TPLR refresh the timer for the packets indicated.
>>>
>>>
>>>
>>> [Qin]: If the receiver does not keep state for the times the TPLR is
>>>
>>>  retransmitted, we can add repetition count field in each FCI entry
>>>
>>>  of TPLR feedback message to indicate the times TPLR is
>> retransmitted.
>>>
>>>  Particularly in PSLEI Feedback Message, we can reuse seq nr. Field
>> to
>>>
>>>  indicate if additional TPLR is retransmitted, which one you think
>> better?
>>>
>>>
>>
>> How, can the receiver keep state for something it has not seen due to
>> the initial packet not having been received?
>>
>> I don't think we need new packet extensions, just clarified rules that
>> correctly describe what the RTP end-point should do when it sees the
>> TPLR message.
>>
>>
>>>
>>> 7. Section 4.2:
>>>    Seq nr:8bits  Command sequence number.  It is used by the Command
>>>       receiver to check if the Command is repeated.  The sequence
>> number
>>>       space is unique for each pairing of the SSRC of command sender
>> and
>>>       the SSRC of the command receiver.  The sequence number SHALL
>>>       increase by 1 modulo 256 for each new Command.  A repetition
>> SHALL
>>>       NOT increase the sequence number.  The initial value is
>> arbitrary.
>>>
>>> Based on that it is defined that upon receiving one of the PSLEI
>>> request, one shouldn't send a FIR or PLI message for a time interval
>>> equal to the RTT between the receiver and the sender of the PSLEI
>>> message does the sequence number field have any meaning? From my
>>> perspective it doesn't matter if it is a new request or not. You are
>>> suppressed from the reception of the message, nothing else.
>>>
>>> [Qin]: I think we can use seq nr field to indicate the times the TPLR
>> is
>>> retransmitted, e.g.,
>>>
>>> If the additional TPLR with the same SSRC and different Seq Number is
>>> received, the
>>>
>>> receiver knows that it is a retransmission if the receiver keeps
>> state
>>> for the previous
>>>
>>> TPLR with the same SSRC.
>>>
>>> Also we can replace seq nr. Field with Repetition count field to
>>> indicate how many time
>>>
>>> the TPLR is retransmitted.
>>>
>>>
>>
>> That is possible, but is the repetition count really providing
>> anything?
>> What is the simplest most straight forward that can work? I think that
>> is that one simple suppress the source for X time after having receives
>> a TPLR message indicate that source. So, as long as you get repeat
>> messages more often than X you continue to be suppressed. Will the
>> receiver work better to know that it is now suppressed for Y times in a
>> go because of the same event?
>>
>> cheers
>>
>> Magnus Westerlund
>>
>> ----------------------------------------------------------------------
>> Multimedia Technologies, Ericsson Research EAB/TVM
>> ----------------------------------------------------------------------
>> Ericsson AB                | Phone  +46 10 7148287
>> Färögatan 6                | Mobile +46 73 0949079
>> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
>> ----------------------------------------------------------------------
>>
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
> 
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From magnus.westerlund@ericsson.com  Thu Nov  3 06:34:45 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8076D1F0C70 for <avt@ietfa.amsl.com>; Thu,  3 Nov 2011 06:34:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.579
X-Spam-Level: 
X-Spam-Status: No, score=-106.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tIo3Ps6BXU+d for <avt@ietfa.amsl.com>; Thu,  3 Nov 2011 06:34:44 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 452D111E8087 for <avt@ietf.org>; Thu,  3 Nov 2011 06:34:44 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-8d-4eb2987327cd
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.115.90]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id B4.1F.13753.37892BE4; Thu,  3 Nov 2011 14:34:43 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.3.137.0; Thu, 3 Nov 2011 14:34:40 +0100
Message-ID: <4EB2986F.2000301@ericsson.com>
Date: Thu, 3 Nov 2011 14:34:39 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Qin Wu <bill.wu@huawei.com>
References: <4E8D76C1.5080508@ericsson.com> <BAC40485A1FA456CA771192D4F750C77@china.huawei.com> <4E9E93A0.10701@ericsson.com> <06E9C1CF3B7D47B5A8FC8540EABA2FAF@china.huawei.com>
In-Reply-To: <06E9C1CF3B7D47B5A8FC8540EABA2FAF@china.huawei.com>
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: IETF AVTCore WG <avt@ietf.org>, "draft-ietf-avtcore-feedback-supression-rtp@tools.ietf.org" <draft-ietf-avtcore-feedback-supression-rtp@tools.ietf.org>
Subject: Re: [AVTCORE] Comments on draft-ietf-avtcore-feedback-supression-rtp-07
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 03 Nov 2011 13:34:45 -0000

On 2011-10-20 11:27, Qin Wu wrote:
> Hi, Magnus:
> Thank for your replies. please see inline.
> ----- Original Message ----- 
> From: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
> To: "Qin Wu" <bill.wu@huawei.com>
> Cc: "IETF AVTCore WG" <avt@ietf.org>; <draft-ietf-avtcore-feedback-supression-rtp@tools.ietf.org>
> Sent: Wednesday, October 19, 2011 5:08 PM
> Subject: Re: [AVTCORE] Comments on draft-ietf-avtcore-feedback-supression-rtp-07
> 
> 
>> Hi,
>>
>> Sorry for the delay in following up.
>>
>> I have removed the issues which don't need further discussion.
>>
>>
>> On 2011-10-11 03:40, Qin Wu wrote:
>>> Hi, Magnus,
>>> Thank for your valuable review, please see my replies belows.
>>> ----- Original Message -----
>>> From: "Magnus Westerlund" <magnus.westerlund@ericsson.com
>>
>>> 2. Section 3.
>>>   "The timer value shall be
>>>    based on the observed round-trip time.  A receiver should compute an
>>>    estimate of the round-trip time (RTT) to the sender of TPLR from RTCP
>>>    report round-trip time if available, or its reception time of the
>>>    reflected RTCP FB message (e.g.,NACK), or any other means."
>>>
>>> We hade the discussion before but now that you clarified which RTT to be
>>> used, I think it is worth having a discussion if that RTT is the right
>>> one. So you suggest that the RTT between the sender of the TPLR and the
>>> receiver of the message is the most appropriate to use when suppressing
>>> the message. I am not certain that is the case.
>>>
>>> Lets consider the use cases. In the case of an intermediary in a
>>> distribution tree sending the TPLR and at the same time sending a NACK
>>> upstream. Then the time until the retransmission reaches the suppressed
>>> receiver is the time from the sending of the NACK up to the
>>> retransmitting entity and all the way down past the TPLR sender to the
>>> suppressed receiver. The receiver may not have a true RTT to the
>>> original media sender as that source appears to live at the TPLR sender,
>>> not further upstream.
>>>
>>> Yes, the sender of the TPLR and the receiver might at least have mutual
>>> knowledge of each other, thus the TPLR sender is able to determine the
>>> lowest RTT in the set of receviers thus determining how often to repeat
>>> it to cover additional time requried for the upstream part of the
>>> request. But I do note that these times aren't matching what appear to
>>> be the delays in the systems.
>>>
>>> Can we find a better solution?
>>>  
>>>
>>> [Qin]: It looks to me the round trip time between media source and
>>>
>>>  intermediary is trivial if we assume the intermediary is much
>>>
>>> closer to the source, that is why I put the last paragraph in the
>>>
>>> section 3 as follows:
>>>
>>> “
>>>
>>> In order not to incur a lot of NACK requests due to additional TPLR
>>>
>>> described above, it is recommended that the RTP system sending
>>>
>>> TPLR should be implemented more closer to the source. Also when
>>>
>>>  the loss was detected and repair initiated much closer to the source,
>>>
>>> the delay for the receiver to recover from packet loss can be reduced
>>>
>>> through the combination of intermediary feedback to the source and
>>>
>>> Third Party Loss Report downstream.
>>>
>>> ”
>>>
>>>  
>>>
>>> If we look for a better solution, I think we have two possible ways:
>>>
>>> The first way is to rely on sender report from media sender to
>>>
>>> calculate the more approximate RTT from media sender to the receiver.
>>>
>>> RTT measurement method follows the same way described in the
>>>
>>> figure 2 of RFC3550.
>>>
>>>  
>>>
>>> The second way is to we can allow the intermediary tell the receiver the
>>>
>>> RTT from media source to intermediary itself by sending a new message
>>>
>>> since the intermediary can measure such RTT based on past observation
>>>
>>> and estimation. However for the second way we need to define new
>>>
>>> message or extend TPLR message to carry such RTT.
>>>
>>>  
>>>
>>> What do you think?
>>>
>>
>> From follow up email:
>>> Hi,Magnus: As regarding if there is better solution, I have some
>>> corrections and additional thoughts.
>>> I think If the media source is the repair server, the receiver should
>>> set timer to T1=max(the RTT from media source to middlebox sending
>>> TPLR, 1/2 of RTT from middlebox to receiver) when the receiver
>>> receives first TPLR. When the receiver receive addtional TPLR within
>>> T1, the receiver should reset the timer to the RTT from media source
>>> to middlebox sending TPLR.
>>>
>>> If the middlebox is the repair server, the receiver should set the
>>> timer to T2=1/2 of RTT from middlebox to receiver when the receiver
>>> receives first TPLR. When the receiver receive addtional TPLR within
>>> T2, the receiver should reset the timer to the T2.
>>>
>>
>> Can you express these rules for the receiver as something that is based
>> on what is observable from the RTP and RTCP traffic? Is when media
>> server being repair server equal to TPLR sender SSRC = Media SSRC the
>> TPLR applies on? And if they are not the same it is the second case?
>>
> 
> 
> [Qin]: Okay, I think the media source will not be the TPLR sender. 
> 
>  
> 
> The receiver should set the timer for the retransmitted data packet when it receive the first TPLR.
> 
> 
> 
> 
> If the sender of Retransmitted data packet is the media source, the timer value shall be
> 
> based on the observed time difference between the round-trip time from the receiver to 
> 
> the original media source and the round-trip time from the receiver to the sender of the TPLR.  

How does the receiver of a TPLR know that the sender of the
retransmitted data packet will be the media stream source?

And if this if statement is not true, what should the timer value be?

> 
> 
> 
> A receiver should compute an estimate of the round-trip time (RTT) to the original media source 
> 
> from Sender Report (SR) packets for the original stream, or any other means. The round-trip time 
> 
> from the receiver to the sender of the TPLR can be calculated from RTCP report round-trip time 
> 
> if available, or any other means.
> 

I think this needs to be more explicit on how that estimate actually can
be done and what precision we expect in it.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From magnus.westerlund@ericsson.com  Thu Nov  3 06:48:30 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 269E011E811F for <avt@ietfa.amsl.com>; Thu,  3 Nov 2011 06:48:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.579
X-Spam-Level: 
X-Spam-Status: No, score=-106.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id evdwhfqrVmPU for <avt@ietfa.amsl.com>; Thu,  3 Nov 2011 06:48:29 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 0106711E8087 for <avt@ietf.org>; Thu,  3 Nov 2011 06:48:28 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-a9-4eb29ba6f865
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 6D.C1.13753.6AB92BE4; Thu,  3 Nov 2011 14:48:23 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.137.0; Thu, 3 Nov 2011 14:48:22 +0100
Message-ID: <4EB29BA5.9080509@ericsson.com>
Date: Thu, 3 Nov 2011 14:48:21 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Qin Wu <bill.wu@huawei.com>
References: <4EA12119.4090900@ericsson.com> <0C80BD8E8293426DB3C50CC7F1ECB0F1@china.huawei.com> <F3153DC2249E4F83B5290A559BFC8B80@china.huawei.com>
In-Reply-To: <F3153DC2249E4F83B5290A559BFC8B80@china.huawei.com>
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: IETF AVTCore WG <avt@ietf.org>, "draft-ietf-avtcore-monarch@tools.ietf.org" <draft-ietf-avtcore-monarch@tools.ietf.org>
Subject: Re: [AVTCORE] Comments on draft-ietf-avtcore-monarch-04
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 03 Nov 2011 13:48:30 -0000

Hi,

Removing all issues that don't need additional discussion or commenting.



On 2011-10-25 07:45, Qin Wu wrote:
> 
> 9. Section 4:
> "It is also
>       fixed across multiple RTP sessions from the same source."
> 
> I interpret "source" in the above as an end-point or RTP node. Which
> causes me to have the following comment.
> 
> This is very commonly true, but not universally true. As CNAME
> identifies a synchronziation context, a given end-point could have media
> sources that belong to multiple synchronization contexts in the same
> session. For example have microphones and cameras from multiple rooms,
> where each room will be its own synchronization context.
> 
> 
> 
> [Qin]: Agree with your thinking, but here what we emphasize is "across multiple RTP session"
> 
> Does this really conflict with what you said?
> 
> Anyway I will reword this in the new vesion.
> 

No, as long as we consider source as media recording device(s) in a
given synchronization context they will be fixed across multiple sessions.


> 
> 12. Section 4. bullet 3:
> This issues does not have a recommendation in the next section. I think
> we should document the WG consensus on this issue. Even if it was that
> this issue wasn't significant enough to do something about. Or am I
> remembering the WG consensus wrong?
> 
> 
> 
> [Qin]: Yes, the issue wasn't significant and I remembered the consensus is 
> 
> to replace tag with the SSRC and use SSRC to identify and correlate and group
> 
>  participants between reports. The sequence numbering information and
> 
>  measurement interval can be defined in a new RTCP XR block if needed, 
> 
> but is not related to identity. Therefore I will add one section to talk about how to deal with this issue.
> 

Thanks, I think it is strange if we don't document the consensus
resolution when it is listed as an issue.

> 
> 21. Section 7.1:
> 
> Strictly the RTP end
>    system can only conclude that its RTP has been lost in the network,
>    though an RTP end system complying with the robustness principle of
>    [RFC1122] should survive with essential functions unimpaired.
> 
> What is the purpose with this sentence? And what is actually seen as
> "essential functions"?
> 
> 
> 
> [Qin]: I think essential functions are referred to as "media distribution"

So you mean that a robustly built end-point will still be able to send
its media despite the fact that media it should receive has been lost in
between the sender and this receiver?

> 
> 22. Section 7.2:
> For bidirectional unicast, an RTP system may usually detect RTCP XR
>    from a translator by noting that the sending SSRC is not present in
>    any RTP media packet.
> 
> So the assumption here is that the translator has its own SSRC to send
> these monitoring reports. But, how does an RTP node determine that an
> SSRC is associated with a translator rather than a receiver only
> end-point? From a session participant I don't think you can determine if
> a give SSRC is a receiver or just a monitor. They will not look
> different. One needs session configuration information, and in that case
> configuration information where the translator announces its node type
> to the management system.
> 
> 
> 
> [Qin]: That's what I want to said in part. And I agree that node type should also be announced.
> 
> I will reflect the draft to reflect this.

Ok, I think the new text is good enough.

> 
> 23. Section 8. I agree that this draft shouldn't have a IANA
> Consideration other to say that it is has no actions. However, I think
> the document should consider if it has some guidance on IANA actions for
> the monitoring architecture. Some part of this is clearly about the
> consumption of XR block code points that isn't a major issue. And if we
> do run out a second RTCP packet type for XR block 2 could be assigned.
> 
> 
> 
> [Qin]: The WG consensus is space depletion is not issue
> 
> if you really want space expansion, you can define one XR block type
> 
>  for vendor-specific extensions, with an enterprise number included 
> 
> to identify the vendor making the extension. So I prefer to say
> 
> "There is no IANA action in this document"

Yes, but if that is the conclusion, shouldn't we document it?


Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From magnus.westerlund@ericsson.com  Thu Nov  3 07:31:38 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA6E411E80EC for <avt@ietfa.amsl.com>; Thu,  3 Nov 2011 07:31:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.579
X-Spam-Level: 
X-Spam-Status: No, score=-106.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mS3LH0a98rl3 for <avt@ietfa.amsl.com>; Thu,  3 Nov 2011 07:31:37 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 5C38311E80B4 for <avt@ietf.org>; Thu,  3 Nov 2011 07:31:37 -0700 (PDT)
X-AuditID: c1b4fb39-b7cb2ae000001bd8-e3-4eb2a5c89fb6
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 49.B0.07128.8C5A2BE4; Thu,  3 Nov 2011 15:31:36 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.3.137.0; Thu, 3 Nov 2011 15:31:36 +0100
Message-ID: <4EB2A5C6.10004@ericsson.com>
Date: Thu, 3 Nov 2011 15:31:34 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
References: <FCC100FC8D6B034CB88CD8173B2DA158155893E1@EXC-MBX03.tsn.tno.nl>
In-Reply-To: <FCC100FC8D6B034CB88CD8173B2DA158155893E1@EXC-MBX03.tsn.tno.nl>
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] Comments on draft-westerlund-avtcore-rtp-simulcast-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 03 Nov 2011 14:31:38 -0000

Ray,

Thanks for the review. Some replies inline.

On 2011-10-26 09:27, Brandenburg, R. (Ray) van wrote:
> Hi Magnus,
> 
>  
> 
> I reviewed your draft draft-westerlund-avtcore-rtp-simulcast-00 and have
> some questions/comments:
> 
>  
> 
> -          Section 3: This section lacks a summary/conclusion. A number
> of different scenarios are introduced, some of which are explicitly
> stated to be out-of-scope (e.g. 3.5), and some are stated to be in-scope
> (e.g. 3.3). Some scenarios however (e.g. 3.2) are not specified to be
> either in- or out-of-scope.
> 

We consider Multicast in scope but with less importance that the mixer
based scenarios.

>  
> 
> -          Section 3: This section talks quite a bit about the relation
> between Simulcast and Scalable Coding and in which situations one of the
> two is more suitable. I’m not sure why this is relevant. Simulcast and
> Scalable Coding might be two techniques that in some cases can be used
> to solve the same problem, the layer on which they do this is completely
> different (codec-level versus transport level). The fact that Scalable
> Coding might, in some situations, be a better solution than Simulcast
> does not mean that Simulcast should not be standardized to handle those
> situations. I understand that you’ve written this mainly from a video
> conferencing perspective, in which Scalable Coding might be used more
> often, but in a lot of situations, such as IPTV, Scalable Coding is just
> not an option due to its inherent complexity. In these situations
> Simulcast might be able to solve some real issues, despite the fact that
> Scalable Coding might be able to solve these issues more efficiently.
> 

I think layered encoding is both a codec level and a transport level
thing. Just as in simulcast you need transport level methods for
selecting the media streams/layers that you want to receive.

I fully agree that there are use cases where one might be considered
much more appropriate than the other. And that is part of our arguments
for why it should be defined for usage also, even though we have layered
coding specified.


>  
> 
> -          Section 3.1.1 See comment above. Why is this section relevant
> to the rest of the document?
> 

See above. But will attempt to clarify this.

>  
> 
> -          Section 3.2.1: This scenario is the only one of the scenarios
> in section 3 to make a clear pro/con of SSRC versus Session based
> multiplexing. Furthermore, it does so before the actual discussion of
> SSRC vs. Session-based multiplexing is introduced in section 4.
> 

Ok, for consistency we should likely move the pro and cons to the
analysis section.

>  
> 
> -          Section 3.3: For the tiled streaming use case described
> below, this scenario is especially relevant. Is there any technical
> reason why it has less emphasis than the RTP-Mixer scenario?

If my understanding of tiled is correct, I don't see how this use case
maps onto tiling. Please elaborate.

> 
>  
> 
> -          Section 5.5: Your conclusion here is that Session Based
> Multiplexing is the best choice, since SSRC multiplexing seems to
> require a large amount of extensions in order to work. How does this
> conclusion relate to the draft-lennox-rtcweb-rtp-media-type-mux-00 which
> seems to suggest that SSRC multiplexing is not that difficult? (I should
> note that I have no experience with sending multiple streams inside a
> single RTP session, so it could be that I don’t understand the issues
> correctly)

If you review RTP Multiplexing architecture you are likely going realize
that there are a number of cases where I consider SSRC multiplexed media
streams to be the best and most appropriate choice. However, it is
important that one consider the use case. So this document argues that
for Simulcast the best choice is to have the simulcast version in
different RTP sessions. However, if one have multiple media streams one
should in fact use multiple SSRC in each of these sessions to carry the
different media sources.

And in sessions where all media streams going to be sent are of the same
type and same configuration then using SSRC multiplexing becomes easy.
The added twist in Lennox's draft is the multiple media types and that
do bring a few issues, but not that many.
https://datatracker.ietf.org/doc/draft-westerlund-avtcore-multiplex-architecture/
and
https://datatracker.ietf.org/doc/draft-westerlund-avtcore-transport-multiplexing/
has discussion on that proposal.

The main point of the multiplexing architecture document is to make
clear that one size fits all does not apply to using multiple SSRCs vs
using several RTP sessions.

> 
>  
> 
> -          Section 6.2: How do you suggest the sequence numbers and RTP
> timestamps are handled between multiple alternative streams? Would it
> make things easier if these were aligned across multiple streams?

No, I don't believe in alignment. first of all the sequence numbers
needs to progress with the packets actually sent for a media stream.
Encoding alternatives are quite likely to have different packet rates,
especially for video as soon as one comes to a media bit-rate where some
alternative requires multiple packets per video frame.

When it comes to timestamp I don't see any need either. For the best
robustness and simplicity one should simply skip using alignment and
instead use the mechanism for synchronizing media clocks with each other
that exist, i.e. RTCP SR and Rapid Synchronization of RTP flows (RFC 6051).


>  
> 
> And one more remark:
> 
>  
> 
> -          In the introduction session you describe three different ways
> in which the encoding of a media content can differ: bit-rate, codec and
> sampling. Recent work in the area of immersive media has proposed a
> fourth method: tiled video. With tiled video (or spatial segmentation),
> the video resulting from a single camera is split into a number of
> areas, each focusing on a particular spatial area of the video (e.g. a
> single video source could be tiled into four separate video streams, one
> describing the topleft quarter of the video and three more describing
> the topright, bottomleft and bottomright quarters respectively).
> 

If I understand this correct, what you really are talking about are
breaking up the output of one camer or several aligned cameras that can
be considered to produce a single video image is divided into several
separate streams. Then on the receiver side these are commonly one
device per media stream. So a practical example would be to split the
output of 4k camera into four 1080p media streams and on the receiver
side use 4 1080 projectors that are aligned so the right edges matches.

If I am correct in my understanding that isn't simulcast. There are no
two or more  different alternatives of the media source. From my
perspective it looks like your splitting your single media source into
multiple synchronized sources. However, it is clear that if you are
doing Tiled video then you would like to consider the transport options
for it. Because it depends if the receiver is actually a single
end-point with 4 displays connected to them or if one actually have four
different end-points and like to have each stream only being delivered
to each end-point, not all of the others.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From ray.vanbrandenburg@tno.nl  Thu Nov  3 08:27:52 2011
Return-Path: <ray.vanbrandenburg@tno.nl>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFFE91F0C72 for <avt@ietfa.amsl.com>; Thu,  3 Nov 2011 08:27:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.403
X-Spam-Level: 
X-Spam-Status: No, score=-0.403 tagged_above=-999 required=5 tests=[AWL=0.101,  BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fjt59+YHHnZU for <avt@ietfa.amsl.com>; Thu,  3 Nov 2011 08:27:50 -0700 (PDT)
Received: from mailouta.tno.nl (mailouta.tno.nl [134.221.1.16]) by ietfa.amsl.com (Postfix) with ESMTP id 572F211E80CD for <avt@ietf.org>; Thu,  3 Nov 2011 08:27:48 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.69,450,1315173600"; d="scan'208";a="59850394"
Received: from unknown (HELO mail.tno.nl) ([134.221.225.222]) by mailhost1a.tno.nl with ESMTP; 03 Nov 2011 16:27:44 +0100
Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.246]) by EXC-CASHUB03.tsn.tno.nl ([134.221.225.222]) with mapi id 14.01.0323.003; Thu, 3 Nov 2011 16:27:44 +0100
From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Thread-Topic: [AVTCORE] Comments on draft-westerlund-avtcore-rtp-simulcast-00
Thread-Index: AcyTIZ2iVQibSCxwScyjBkbRqff1xwHC0ncAAAMuygA=
Date: Thu, 3 Nov 2011 15:27:42 +0000
Message-ID: <FCC100FC8D6B034CB88CD8173B2DA1581558DD8A@EXC-MBX03.tsn.tno.nl>
References: <FCC100FC8D6B034CB88CD8173B2DA158155893E1@EXC-MBX03.tsn.tno.nl> <4EB2A5C6.10004@ericsson.com>
In-Reply-To: <4EB2A5C6.10004@ericsson.com>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [134.221.225.191]
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] Comments on draft-westerlund-avtcore-rtp-simulcast-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 03 Nov 2011 15:27:52 -0000

Hi Magnus,=20

See comments inline.=20

Ray

-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]=20
Sent: donderdag 3 november 2011 15:32
To: Brandenburg, R. (Ray) van
Cc: avt@ietf.org
Subject: Re: [AVTCORE] Comments on draft-westerlund-avtcore-rtp-simulcast-00

Ray,

Thanks for the review. Some replies inline.

On 2011-10-26 09:27, Brandenburg, R. (Ray) van wrote:
> Hi Magnus,
>=20
> =20
>=20
> I reviewed your draft draft-westerlund-avtcore-rtp-simulcast-00 and=20
> have some questions/comments:
>=20
> =20
>=20
> -          Section 3: This section lacks a summary/conclusion. A number
> of different scenarios are introduced, some of which are explicitly=20
> stated to be out-of-scope (e.g. 3.5), and some are stated to be=20
> in-scope (e.g. 3.3). Some scenarios however (e.g. 3.2) are not=20
> specified to be either in- or out-of-scope.
>=20

We consider Multicast in scope but with less importance that the mixer base=
d scenarios.

[RAY: Ok. Maybe you could add the reasoning to the document?]

> =20
>=20
> -          Section 3: This section talks quite a bit about the relation
> between Simulcast and Scalable Coding and in which situations one of=20
> the two is more suitable. I'm not sure why this is relevant. Simulcast=20
> and Scalable Coding might be two techniques that in some cases can be=20
> used to solve the same problem, the layer on which they do this is=20
> completely different (codec-level versus transport level). The fact=20
> that Scalable Coding might, in some situations, be a better solution=20
> than Simulcast does not mean that Simulcast should not be standardized=20
> to handle those situations. I understand that you've written this=20
> mainly from a video conferencing perspective, in which Scalable Coding=20
> might be used more often, but in a lot of situations, such as IPTV,=20
> Scalable Coding is just not an option due to its inherent complexity.=20
> In these situations Simulcast might be able to solve some real issues,=20
> despite the fact that Scalable Coding might be able to solve these issues=
 more efficiently.
>=20

I think layered encoding is both a codec level and a transport level thing.=
 Just as in simulcast you need transport level methods for selecting the me=
dia streams/layers that you want to receive.

I fully agree that there are use cases where one might be considered much m=
ore appropriate than the other. And that is part of our arguments for why i=
t should be defined for usage also, even though we have layered coding spec=
ified.

[RAY: I don't agree with you that layered coding is a transport-level thing=
 (or maybe I don't understand your definition of layered coding. With layer=
ed coding I mean e.g. SVC). It might be that layered-coding requires some s=
pecific transport-level properties (such as alignment), however these are n=
ot unique to layered coding. Your draft (or specifically section 3) seems t=
o imply that Simulcast can be considered an alternative to Scalable Coding =
and that you therefore have to argue why Simulcast is better in some situat=
ions. In my opinion, Scalable Coding is an alternative to creating multiple=
 bitrates/resolutions (i.e. Adaptive Streaming) and not to Simulcast. My un=
derstanding is that Simulcast is a method to deliver those multiple bitrate=
s, the same way it could be used to deliver Scalable Coding streams.]


> =20
>=20
> -          Section 3.1.1 See comment above. Why is this section relevant
> to the rest of the document?
>=20

See above. But will attempt to clarify this.

[RAY: OK]

> =20
>=20
> -          Section 3.2.1: This scenario is the only one of the scenarios
> in section 3 to make a clear pro/con of SSRC versus Session based=20
> multiplexing. Furthermore, it does so before the actual discussion of=20
> SSRC vs. Session-based multiplexing is introduced in section 4.
>=20

Ok, for consistency we should likely move the pro and cons to the analysis =
section.

[RAY: OK]

> =20
>=20
> -          Section 3.3: For the tiled streaming use case described
> below, this scenario is especially relevant. Is there any technical=20
> reason why it has less emphasis than the RTP-Mixer scenario?

If my understanding of tiled is correct, I don't see how this use case maps=
 onto tiling. Please elaborate.

[RAY: see my comment below]

>=20
> =20
>=20
> -          Section 5.5: Your conclusion here is that Session Based
> Multiplexing is the best choice, since SSRC multiplexing seems to=20
> require a large amount of extensions in order to work. How does this=20
> conclusion relate to the draft-lennox-rtcweb-rtp-media-type-mux-00=20
> which seems to suggest that SSRC multiplexing is not that difficult?=20
> (I should note that I have no experience with sending multiple streams=20
> inside a single RTP session, so it could be that I don't understand=20
> the issues
> correctly)

If you review RTP Multiplexing architecture you are likely going realize th=
at there are a number of cases where I consider SSRC multiplexed media stre=
ams to be the best and most appropriate choice. However, it is important th=
at one consider the use case. So this document argues that for Simulcast th=
e best choice is to have the simulcast version in different RTP sessions. H=
owever, if one have multiple media streams one should in fact use multiple =
SSRC in each of these sessions to carry the different media sources.

And in sessions where all media streams going to be sent are of the same ty=
pe and same configuration then using SSRC multiplexing becomes easy.
The added twist in Lennox's draft is the multiple media types and that do b=
ring a few issues, but not that many.
https://datatracker.ietf.org/doc/draft-westerlund-avtcore-multiplex-archite=
cture/
and
https://datatracker.ietf.org/doc/draft-westerlund-avtcore-transport-multipl=
exing/
has discussion on that proposal.

The main point of the multiplexing architecture document is to make clear t=
hat one size fits all does not apply to using multiple SSRCs vs using sever=
al RTP sessions.

[RAY: Thanks for clearing that up]

>=20
> =20
>=20
> -          Section 6.2: How do you suggest the sequence numbers and RTP
> timestamps are handled between multiple alternative streams? Would it=20
> make things easier if these were aligned across multiple streams?

No, I don't believe in alignment. first of all the sequence numbers needs t=
o progress with the packets actually sent for a media stream.
Encoding alternatives are quite likely to have different packet rates, espe=
cially for video as soon as one comes to a media bit-rate where some altern=
ative requires multiple packets per video frame.

When it comes to timestamp I don't see any need either. For the best robust=
ness and simplicity one should simply skip using alignment and instead use =
the mechanism for synchronizing media clocks with each other that exist, i.=
e. RTCP SR and Rapid Synchronization of RTP flows (RFC 6051).

[RAY: For the sequence numbers I agree, however about the timestamps I'm no=
t so sure. In some cases it might be particularly useful to align timestamp=
s. One example are areas where you need bit-level alignment (such as SVC an=
d spatially segmented streams). For these situations NTP-based solutions su=
ch as RTCP SR are not accurate enough]

> =20
>=20
> And one more remark:
>=20
> =20
>=20
> -          In the introduction session you describe three different ways
> in which the encoding of a media content can differ: bit-rate, codec=20
> and sampling. Recent work in the area of immersive media has proposed=20
> a fourth method: tiled video. With tiled video (or spatial=20
> segmentation), the video resulting from a single camera is split into=20
> a number of areas, each focusing on a particular spatial area of the=20
> video (e.g. a single video source could be tiled into four separate=20
> video streams, one describing the topleft quarter of the video and=20
> three more describing the topright, bottomleft and bottomright quarters r=
espectively).
>=20

If I understand this correct, what you really are talking about are breakin=
g up the output of one camer or several aligned cameras that can be conside=
red to produce a single video image is divided into several separate stream=
s. Then on the receiver side these are commonly one device per media stream=
. So a practical example would be to split the output of 4k camera into fou=
r 1080p media streams and on the receiver side use 4 1080 projectors that a=
re aligned so the right edges matches.

If I am correct in my understanding that isn't simulcast. There are no two =
or more  different alternatives of the media source. From my perspective it=
 looks like your splitting your single media source into multiple synchroni=
zed sources. However, it is clear that if you are doing Tiled video then yo=
u would like to consider the transport options for it. Because it depends i=
f the receiver is actually a single end-point with 4 displays connected to =
them or if one actually have four different end-points and like to have eac=
h stream only being delivered to each end-point, not all of the others.

[RAY: Sorry for not being any clearer. We have a different understanding of=
 tiled streaming (or spatial segmentation as is probably more descriptive).=
 The use case is not having four network-connected projectors. The use case=
 is having a mobile device with a relatively low resolution (e.g. 480x320 p=
ixels) being able to navigate through high resolution (4k/8k) content. By s=
plitting the output of a single 4k camera into 'tiles' of for example 240x1=
60 pixels, and storing each of these as a separate stream, a client can req=
uest multiple streams simultaneously and reconstruct part of the original v=
ideo (in this case it would request 4 'tiles'). When a user wants to naviga=
te through the content (e.g. pan/zoom) it requests a different subset of ti=
les. =09
As you can see, what we have here is a large number of tiles (streams), com=
ing from the same source, with different clients requesting different subse=
ts of these tiles. In that aspect, it is not that dissimilar from some of t=
he use cases you describe in your draft.]=20

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
F=E4r=F6gatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

This e-mail and its contents are subject to the DISCLAIMER at http://www.tn=
o.nl/emaildisclaimer


From bill.wu@huawei.com  Thu Nov  3 19:13:50 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 200CF1F0C3D for <avt@ietfa.amsl.com>; Thu,  3 Nov 2011 19:13:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.346
X-Spam-Level: 
X-Spam-Status: No, score=-4.346 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8aLY6v5fthFR for <avt@ietfa.amsl.com>; Thu,  3 Nov 2011 19:13:49 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 1F5B521F86A1 for <avt@ietf.org>; Thu,  3 Nov 2011 19:13:49 -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 <0LU400A8766T04@szxga03-in.huawei.com> for avt@ietf.org; Fri, 04 Nov 2011 10:13:42 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LU40003W66TSS@szxga03-in.huawei.com> for avt@ietf.org; Fri, 04 Nov 2011 10:13:41 +0800 (CST)
Received: from szxeml208-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEW18374; Fri, 04 Nov 2011 10:13:41 +0800
Received: from SZXEML401-HUB.china.huawei.com (10.82.67.31) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.270.1; Fri, 04 Nov 2011 10:13:35 +0800
Received: from w53375q (10.138.41.130) by szxeml401-hub.china.huawei.com (10.82.67.31) with Microsoft SMTP Server (TLS) id 14.1.270.1; Fri, 04 Nov 2011 10:13:33 +0800
Date: Fri, 04 Nov 2011 10:13:32 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-id: <060F172CB45D4D49A13B930494895B84@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: base64
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <4EA12119.4090900@ericsson.com> <0C80BD8E8293426DB3C50CC7F1ECB0F1@china.huawei.com> <F3153DC2249E4F83B5290A559BFC8B80@china.huawei.com> <4EB29BA5.9080509@ericsson.com>
Cc: IETF AVTCore WG <avt@ietf.org>, draft-ietf-avtcore-monarch@tools.ietf.org
Subject: Re: [AVTCORE] Comments on draft-ietf-avtcore-monarch-04
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 04 Nov 2011 02:13:50 -0000

LS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCkZyb206ICJNYWdudXMgV2VzdGVybHVuZCIg
PG1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29uLmNvbT4NClRvOiAiUWluIFd1IiA8YmlsbC53dUBo
dWF3ZWkuY29tPg0KQ2M6ICJJRVRGIEFWVENvcmUgV0ciIDxhdnRAaWV0Zi5vcmc+OyA8ZHJhZnQt
aWV0Zi1hdnRjb3JlLW1vbmFyY2hAdG9vbHMuaWV0Zi5vcmc+DQpTZW50OiBUaHVyc2RheSwgTm92
ZW1iZXIgMDMsIDIwMTEgOTo0OCBQTQ0KU3ViamVjdDogUmU6IFtBVlRDT1JFXSBDb21tZW50cyBv
biBkcmFmdC1pZXRmLWF2dGNvcmUtbW9uYXJjaC0wNA0KDQoNCj4gSGksDQo+IA0KPiBSZW1vdmlu
ZyBhbGwgaXNzdWVzIHRoYXQgZG9uJ3QgbmVlZCBhZGRpdGlvbmFsIGRpc2N1c3Npb24gb3IgY29t
bWVudGluZy4NCj4gDQo+IA0KPiANCj4gT24gMjAxMS0xMC0yNSAwNzo0NSwgUWluIFd1IHdyb3Rl
Og0KPj4gDQo+PiA5LiBTZWN0aW9uIDQ6DQo+PiAiSXQgaXMgYWxzbw0KPj4gICAgICAgZml4ZWQg
YWNyb3NzIG11bHRpcGxlIFJUUCBzZXNzaW9ucyBmcm9tIHRoZSBzYW1lIHNvdXJjZS4iDQo+PiAN
Cj4+IEkgaW50ZXJwcmV0ICJzb3VyY2UiIGluIHRoZSBhYm92ZSBhcyBhbiBlbmQtcG9pbnQgb3Ig
UlRQIG5vZGUuIFdoaWNoDQo+PiBjYXVzZXMgbWUgdG8gaGF2ZSB0aGUgZm9sbG93aW5nIGNvbW1l
bnQuDQo+PiANCj4+IFRoaXMgaXMgdmVyeSBjb21tb25seSB0cnVlLCBidXQgbm90IHVuaXZlcnNh
bGx5IHRydWUuIEFzIENOQU1FDQo+PiBpZGVudGlmaWVzIGEgc3luY2hyb256aWF0aW9uIGNvbnRl
eHQsIGEgZ2l2ZW4gZW5kLXBvaW50IGNvdWxkIGhhdmUgbWVkaWENCj4+IHNvdXJjZXMgdGhhdCBi
ZWxvbmcgdG8gbXVsdGlwbGUgc3luY2hyb25pemF0aW9uIGNvbnRleHRzIGluIHRoZSBzYW1lDQo+
PiBzZXNzaW9uLiBGb3IgZXhhbXBsZSBoYXZlIG1pY3JvcGhvbmVzIGFuZCBjYW1lcmFzIGZyb20g
bXVsdGlwbGUgcm9vbXMsDQo+PiB3aGVyZSBlYWNoIHJvb20gd2lsbCBiZSBpdHMgb3duIHN5bmNo
cm9uaXphdGlvbiBjb250ZXh0Lg0KPj4gDQo+PiANCj4+IA0KPj4gW1Fpbl06IEFncmVlIHdpdGgg
eW91ciB0aGlua2luZywgYnV0IGhlcmUgd2hhdCB3ZSBlbXBoYXNpemUgaXMgImFjcm9zcyBtdWx0
aXBsZSBSVFAgc2Vzc2lvbiINCj4+IA0KPj4gRG9lcyB0aGlzIHJlYWxseSBjb25mbGljdCB3aXRo
IHdoYXQgeW91IHNhaWQ/DQo+PiANCj4+IEFueXdheSBJIHdpbGwgcmV3b3JkIHRoaXMgaW4gdGhl
IG5ldyB2ZXNpb24uDQo+PiANCg0KPiBObywgYXMgbG9uZyBhcyB3ZSBjb25zaWRlciBzb3VyY2Ug
YXMgbWVkaWEgcmVjb3JkaW5nIGRldmljZShzKSBpbiBhDQo+IGdpdmVuIHN5bmNocm9uaXphdGlv
biBjb250ZXh0IHRoZXkgd2lsbCBiZSBmaXhlZCBhY3Jvc3MgbXVsdGlwbGUgc2Vzc2lvbnMuDQo+
IA0KDQoNCltRaW5dOiBPa2F5LCBkbyB3ZSBoYXZlIG90aGVyIHVzZSBjYXNlcyBiZXNpZGVzIHRo
ZSBhYm92ZSBvbmUgeW91IGdhdmU/DQoNCj4+IA0KPj4gMTIuIFNlY3Rpb24gNC4gYnVsbGV0IDM6
DQo+PiBUaGlzIGlzc3VlcyBkb2VzIG5vdCBoYXZlIGEgcmVjb21tZW5kYXRpb24gaW4gdGhlIG5l
eHQgc2VjdGlvbi4gSSB0aGluaw0KPj4gd2Ugc2hvdWxkIGRvY3VtZW50IHRoZSBXRyBjb25zZW5z
dXMgb24gdGhpcyBpc3N1ZS4gRXZlbiBpZiBpdCB3YXMgdGhhdA0KPj4gdGhpcyBpc3N1ZSB3YXNu
J3Qgc2lnbmlmaWNhbnQgZW5vdWdoIHRvIGRvIHNvbWV0aGluZyBhYm91dC4gT3IgYW0gSQ0KPj4g
cmVtZW1iZXJpbmcgdGhlIFdHIGNvbnNlbnN1cyB3cm9uZz8NCj4+IA0KPj4gDQo+PiANCj4+IFtR
aW5dOiBZZXMsIHRoZSBpc3N1ZSB3YXNuJ3Qgc2lnbmlmaWNhbnQgYW5kIEkgcmVtZW1iZXJlZCB0
aGUgY29uc2Vuc3VzIGlzIA0KPj4gDQo+PiB0byByZXBsYWNlIHRhZyB3aXRoIHRoZSBTU1JDIGFu
ZCB1c2UgU1NSQyB0byBpZGVudGlmeSBhbmQgY29ycmVsYXRlIGFuZCBncm91cA0KPj4gDQo+PiAg
cGFydGljaXBhbnRzIGJldHdlZW4gcmVwb3J0cy4gVGhlIHNlcXVlbmNlIG51bWJlcmluZyBpbmZv
cm1hdGlvbiBhbmQNCj4+IA0KPj4gIG1lYXN1cmVtZW50IGludGVydmFsIGNhbiBiZSBkZWZpbmVk
IGluIGEgbmV3IFJUQ1AgWFIgYmxvY2sgaWYgbmVlZGVkLCANCj4+IA0KPj4gYnV0IGlzIG5vdCBy
ZWxhdGVkIHRvIGlkZW50aXR5LiBUaGVyZWZvcmUgSSB3aWxsIGFkZCBvbmUgc2VjdGlvbiB0byB0
YWxrIGFib3V0IGhvdyB0byBkZWFsIHdpdGggdGhpcyBpc3N1ZS4NCj4+IA0KPiANCj4gVGhhbmtz
LCBJIHRoaW5rIGl0IGlzIHN0cmFuZ2UgaWYgd2UgZG9uJ3QgZG9jdW1lbnQgdGhlIGNvbnNlbnN1
cw0KPiByZXNvbHV0aW9uIHdoZW4gaXQgaXMgbGlzdGVkIGFzIGFuIGlzc3VlLg0KDQpbUWluXTog
WWVzLCBJIGhhdmUgZG9jdW1lbnRlZCB0aGVtIGluIHRoZSBuZXcgdmVyc2lvbiAwNSBJIHN1Ym1p
dHRlZCBiZWZvcmUgdGhlIGRlYWRsaW5lLg0KDQo+PiANCj4+IDIxLiBTZWN0aW9uIDcuMToNCj4+
IA0KPj4gU3RyaWN0bHkgdGhlIFJUUCBlbmQNCj4+ICAgIHN5c3RlbSBjYW4gb25seSBjb25jbHVk
ZSB0aGF0IGl0cyBSVFAgaGFzIGJlZW4gbG9zdCBpbiB0aGUgbmV0d29yaywNCj4+ICAgIHRob3Vn
aCBhbiBSVFAgZW5kIHN5c3RlbSBjb21wbHlpbmcgd2l0aCB0aGUgcm9idXN0bmVzcyBwcmluY2lw
bGUgb2YNCj4+ICAgIFtSRkMxMTIyXSBzaG91bGQgc3Vydml2ZSB3aXRoIGVzc2VudGlhbCBmdW5j
dGlvbnMgdW5pbXBhaXJlZC4NCj4+IA0KPj4gV2hhdCBpcyB0aGUgcHVycG9zZSB3aXRoIHRoaXMg
c2VudGVuY2U/IEFuZCB3aGF0IGlzIGFjdHVhbGx5IHNlZW4gYXMNCj4+ICJlc3NlbnRpYWwgZnVu
Y3Rpb25zIj8NCj4+IA0KPj4gDQo+PiANCj4+IFtRaW5dOiBJIHRoaW5rIGVzc2VudGlhbCBmdW5j
dGlvbnMgYXJlIHJlZmVycmVkIHRvIGFzICJtZWRpYSBkaXN0cmlidXRpb24iDQo+IA0KPiBTbyB5
b3UgbWVhbiB0aGF0IGEgcm9idXN0bHkgYnVpbHQgZW5kLXBvaW50IHdpbGwgc3RpbGwgYmUgYWJs
ZSB0byBzZW5kDQo+IGl0cyBtZWRpYSBkZXNwaXRlIHRoZSBmYWN0IHRoYXQgbWVkaWEgaXQgc2hv
dWxkIHJlY2VpdmUgaGFzIGJlZW4gbG9zdCBpbg0KPiBiZXR3ZWVuIHRoZSBzZW5kZXIgYW5kIHRo
aXMgcmVjZWl2ZXI/DQoNCltRaW5dOiBUaGF0J3MgbXkgdW5kZXJzdGFuZGluZywgaXMgdGhhdCBv
a2F5IHdpdGggeW91Pw0KDQo+PiANCj4+IDIyLiBTZWN0aW9uIDcuMjoNCj4+IEZvciBiaWRpcmVj
dGlvbmFsIHVuaWNhc3QsIGFuIFJUUCBzeXN0ZW0gbWF5IHVzdWFsbHkgZGV0ZWN0IFJUQ1AgWFIN
Cj4+ICAgIGZyb20gYSB0cmFuc2xhdG9yIGJ5IG5vdGluZyB0aGF0IHRoZSBzZW5kaW5nIFNTUkMg
aXMgbm90IHByZXNlbnQgaW4NCj4+ICAgIGFueSBSVFAgbWVkaWEgcGFja2V0Lg0KPj4gDQo+PiBT
byB0aGUgYXNzdW1wdGlvbiBoZXJlIGlzIHRoYXQgdGhlIHRyYW5zbGF0b3IgaGFzIGl0cyBvd24g
U1NSQyB0byBzZW5kDQo+PiB0aGVzZSBtb25pdG9yaW5nIHJlcG9ydHMuIEJ1dCwgaG93IGRvZXMg
YW4gUlRQIG5vZGUgZGV0ZXJtaW5lIHRoYXQgYW4NCj4+IFNTUkMgaXMgYXNzb2NpYXRlZCB3aXRo
IGEgdHJhbnNsYXRvciByYXRoZXIgdGhhbiBhIHJlY2VpdmVyIG9ubHkNCj4+IGVuZC1wb2ludD8g
RnJvbSBhIHNlc3Npb24gcGFydGljaXBhbnQgSSBkb24ndCB0aGluayB5b3UgY2FuIGRldGVybWlu
ZSBpZg0KPj4gYSBnaXZlIFNTUkMgaXMgYSByZWNlaXZlciBvciBqdXN0IGEgbW9uaXRvci4gVGhl
eSB3aWxsIG5vdCBsb29rDQo+PiBkaWZmZXJlbnQuIE9uZSBuZWVkcyBzZXNzaW9uIGNvbmZpZ3Vy
YXRpb24gaW5mb3JtYXRpb24sIGFuZCBpbiB0aGF0IGNhc2UNCj4+IGNvbmZpZ3VyYXRpb24gaW5m
b3JtYXRpb24gd2hlcmUgdGhlIHRyYW5zbGF0b3IgYW5ub3VuY2VzIGl0cyBub2RlIHR5cGUNCj4+
IHRvIHRoZSBtYW5hZ2VtZW50IHN5c3RlbS4NCj4+IA0KPj4gDQo+PiANCj4+IFtRaW5dOiBUaGF0
J3Mgd2hhdCBJIHdhbnQgdG8gc2FpZCBpbiBwYXJ0LiBBbmQgSSBhZ3JlZSB0aGF0IG5vZGUgdHlw
ZSBzaG91bGQgYWxzbyBiZSBhbm5vdW5jZWQuDQo+PiANCj4+IEkgd2lsbCByZXZpc2UgdGhlIGRy
YWZ0IHRvIHJlZmxlY3QgdGhpcy4NCj4gDQo+IE9rLCBJIHRoaW5rIHRoZSBuZXcgdGV4dCBpcyBn
b29kIGVub3VnaC4NCg0KW1Fpbl06IFRoYW5rcy4NCg0KPj4gDQo+PiAyMy4gU2VjdGlvbiA4LiBJ
IGFncmVlIHRoYXQgdGhpcyBkcmFmdCBzaG91bGRuJ3QgaGF2ZSBhIElBTkENCj4+IENvbnNpZGVy
YXRpb24gb3RoZXIgdG8gc2F5IHRoYXQgaXQgaXMgaGFzIG5vIGFjdGlvbnMuIEhvd2V2ZXIsIEkg
dGhpbmsNCj4+IHRoZSBkb2N1bWVudCBzaG91bGQgY29uc2lkZXIgaWYgaXQgaGFzIHNvbWUgZ3Vp
ZGFuY2Ugb24gSUFOQSBhY3Rpb25zIGZvcg0KPj4gdGhlIG1vbml0b3JpbmcgYXJjaGl0ZWN0dXJl
LiBTb21lIHBhcnQgb2YgdGhpcyBpcyBjbGVhcmx5IGFib3V0IHRoZQ0KPj4gY29uc3VtcHRpb24g
b2YgWFIgYmxvY2sgY29kZSBwb2ludHMgdGhhdCBpc24ndCBhIG1ham9yIGlzc3VlLiBBbmQgaWYg
d2UNCj4+IGRvIHJ1biBvdXQgYSBzZWNvbmQgUlRDUCBwYWNrZXQgdHlwZSBmb3IgWFIgYmxvY2sg
MiBjb3VsZCBiZSBhc3NpZ25lZC4NCj4+IA0KPj4gDQo+PiANCj4+IFtRaW5dOiBUaGUgV0cgY29u
c2Vuc3VzIGlzIHNwYWNlIGRlcGxldGlvbiBpcyBub3QgaXNzdWUNCj4+IA0KPj4gaWYgeW91IHJl
YWxseSB3YW50IHNwYWNlIGV4cGFuc2lvbiwgeW91IGNhbiBkZWZpbmUgb25lIFhSIGJsb2NrIHR5
cGUNCj4+IA0KPj4gIGZvciB2ZW5kb3Itc3BlY2lmaWMgZXh0ZW5zaW9ucywgd2l0aCBhbiBlbnRl
cnByaXNlIG51bWJlciBpbmNsdWRlZCANCj4+IA0KPj4gdG8gaWRlbnRpZnkgdGhlIHZlbmRvciBt
YWtpbmcgdGhlIGV4dGVuc2lvbi4gU28gSSBwcmVmZXIgdG8gc2F5DQo+PiANCj4+ICJUaGVyZSBp
cyBubyBJQU5BIGFjdGlvbiBpbiB0aGlzIGRvY3VtZW50Ig0KPiANCj4gWWVzLCBidXQgaWYgdGhh
dCBpcyB0aGUgY29uY2x1c2lvbiwgc2hvdWxkbid0IHdlIGRvY3VtZW50IGl0Pw0KDQpbUWluXTog
T2theSwgSSBjYW4gcHV0IHRoZW0gaW4gdGhlIG5ldyB2ZXJzaW9uLg0KDQo+IA0KPiBDaGVlcnMN
Cj4gDQo+IE1hZ251cyBXZXN0ZXJsdW5kDQo+IA0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+IE11bHRpbWVk
aWEgVGVjaG5vbG9naWVzLCBFcmljc3NvbiBSZXNlYXJjaCBFQUIvVFZNDQo+IC0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0NCj4gRXJpY3Nzb24gQUIgICAgICAgICAgICAgICAgfCBQaG9uZSAgKzQ2IDEwIDcxNDgyODcN
Cj4gRuRy9mdhdGFuIDYgICAgICAgICAgICAgICAgfCBNb2JpbGUgKzQ2IDczIDA5NDkwNzkNCj4g
U0UtMTY0IDgwIFN0b2NraG9sbSwgU3dlZGVufCBtYWlsdG86IG1hZ251cy53ZXN0ZXJsdW5kQGVy
aWNzc29uLmNvbQ0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+


From bill.wu@huawei.com  Thu Nov  3 20:46:29 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71B5911E8147 for <avt@ietfa.amsl.com>; Thu,  3 Nov 2011 20:46:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.338
X-Spam-Level: 
X-Spam-Status: No, score=-4.338 tagged_above=-999 required=5 tests=[AWL=0.508,  BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id THvKlMnfGPq4 for <avt@ietfa.amsl.com>; Thu,  3 Nov 2011 20:46:28 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 2120211E8146 for <avt@ietf.org>; Thu,  3 Nov 2011 20:46:28 -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 <0LU4008S5AH9JL@szxga04-in.huawei.com> for avt@ietf.org; Fri, 04 Nov 2011 11:46:21 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LU400LPEAGNSA@szxga04-in.huawei.com> for avt@ietf.org; Fri, 04 Nov 2011 11:46:21 +0800 (CST)
Received: from szxeml202-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AET32016; Fri, 04 Nov 2011 11:46:20 +0800
Received: from SZXEML412-HUB.china.huawei.com (10.82.67.91) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.270.1; Fri, 04 Nov 2011 11:46:08 +0800
Received: from w53375q (10.138.41.130) by szxeml412-hub.china.huawei.com (10.82.67.91) with Microsoft SMTP Server (TLS) id 14.1.270.1; Fri, 04 Nov 2011 11:46:12 +0800
Date: Fri, 04 Nov 2011 11:46:11 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-id: <85A232BE2B3647CB98401741A6DD9D91@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=windows-1252
Content-transfer-encoding: base64
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <4E8D76C1.5080508@ericsson.com> <BAC40485A1FA456CA771192D4F750C77@china.huawei.com> <4E9E93A0.10701@ericsson.com> <06E9C1CF3B7D47B5A8FC8540EABA2FAF@china.huawei.com> <4EB2986F.2000301@ericsson.com>
Cc: IETF AVTCore WG <avt@ietf.org>, draft-ietf-avtcore-feedback-supression-rtp@tools.ietf.org
Subject: Re: [AVTCORE] Comments on draft-ietf-avtcore-feedback-supression-rtp-07
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 04 Nov 2011 03:46:29 -0000

LS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCkZyb206ICJNYWdudXMgV2VzdGVybHVuZCIg
PG1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29uLmNvbT4NClRvOiAiUWluIFd1IiA8YmlsbC53dUBo
dWF3ZWkuY29tPg0KQ2M6ICJJRVRGIEFWVENvcmUgV0ciIDxhdnRAaWV0Zi5vcmc+OyA8ZHJhZnQt
aWV0Zi1hdnRjb3JlLWZlZWRiYWNrLXN1cHJlc3Npb24tcnRwQHRvb2xzLmlldGYub3JnPg0KU2Vu
dDogVGh1cnNkYXksIE5vdmVtYmVyIDAzLCAyMDExIDk6MzQgUE0NClN1YmplY3Q6IFJlOiBbQVZU
Q09SRV0gQ29tbWVudHMgb24gZHJhZnQtaWV0Zi1hdnRjb3JlLWZlZWRiYWNrLXN1cHJlc3Npb24t
cnRwLTA3DQoNCg0KT24gMjAxMS0xMC0yMCAxMToyNywgUWluIFd1IHdyb3RlOg0KPiBIaSwgTWFn
bnVzOg0KPiBUaGFuayBmb3IgeW91ciByZXBsaWVzLiBwbGVhc2Ugc2VlIGlubGluZS4NCj4gLS0t
LS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCj4gRnJvbTogIk1hZ251cyBXZXN0ZXJsdW5kIiA8
bWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tPg0KPiBUbzogIlFpbiBXdSIgPGJpbGwud3VA
aHVhd2VpLmNvbT4NCj4gQ2M6ICJJRVRGIEFWVENvcmUgV0ciIDxhdnRAaWV0Zi5vcmc+OyA8ZHJh
ZnQtaWV0Zi1hdnRjb3JlLWZlZWRiYWNrLXN1cHJlc3Npb24tcnRwQHRvb2xzLmlldGYub3JnPg0K
PiBTZW50OiBXZWRuZXNkYXksIE9jdG9iZXIgMTksIDIwMTEgNTowOCBQTQ0KPiBTdWJqZWN0OiBS
ZTogW0FWVENPUkVdIENvbW1lbnRzIG9uIGRyYWZ0LWlldGYtYXZ0Y29yZS1mZWVkYmFjay1zdXBy
ZXNzaW9uLXJ0cC0wNw0KPiANCj4gDQo+PiBIaSwNCj4+DQo+PiBTb3JyeSBmb3IgdGhlIGRlbGF5
IGluIGZvbGxvd2luZyB1cC4NCj4+DQo+PiBJIGhhdmUgcmVtb3ZlZCB0aGUgaXNzdWVzIHdoaWNo
IGRvbid0IG5lZWQgZnVydGhlciBkaXNjdXNzaW9uLg0KPj4NCj4+DQo+PiBPbiAyMDExLTEwLTEx
IDAzOjQwLCBRaW4gV3Ugd3JvdGU6DQo+Pj4gSGksIE1hZ251cywNCj4+PiBUaGFuayBmb3IgeW91
ciB2YWx1YWJsZSByZXZpZXcsIHBsZWFzZSBzZWUgbXkgcmVwbGllcyBiZWxvd3MuDQo+Pj4gLS0t
LS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLQ0KPj4+IEZyb206ICJNYWdudXMgV2VzdGVybHVuZCIg
PG1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29uLmNvbQ0KPj4NCj4+PiAyLiBTZWN0aW9uIDMuDQo+
Pj4gICAiVGhlIHRpbWVyIHZhbHVlIHNoYWxsIGJlDQo+Pj4gICAgYmFzZWQgb24gdGhlIG9ic2Vy
dmVkIHJvdW5kLXRyaXAgdGltZS4gIEEgcmVjZWl2ZXIgc2hvdWxkIGNvbXB1dGUgYW4NCj4+PiAg
ICBlc3RpbWF0ZSBvZiB0aGUgcm91bmQtdHJpcCB0aW1lIChSVFQpIHRvIHRoZSBzZW5kZXIgb2Yg
VFBMUiBmcm9tIFJUQ1ANCj4+PiAgICByZXBvcnQgcm91bmQtdHJpcCB0aW1lIGlmIGF2YWlsYWJs
ZSwgb3IgaXRzIHJlY2VwdGlvbiB0aW1lIG9mIHRoZQ0KPj4+ICAgIHJlZmxlY3RlZCBSVENQIEZC
IG1lc3NhZ2UgKGUuZy4sTkFDSyksIG9yIGFueSBvdGhlciBtZWFucy4iDQo+Pj4NCj4+PiBXZSBo
YWRlIHRoZSBkaXNjdXNzaW9uIGJlZm9yZSBidXQgbm93IHRoYXQgeW91IGNsYXJpZmllZCB3aGlj
aCBSVFQgdG8gYmUNCj4+PiB1c2VkLCBJIHRoaW5rIGl0IGlzIHdvcnRoIGhhdmluZyBhIGRpc2N1
c3Npb24gaWYgdGhhdCBSVFQgaXMgdGhlIHJpZ2h0DQo+Pj4gb25lLiBTbyB5b3Ugc3VnZ2VzdCB0
aGF0IHRoZSBSVFQgYmV0d2VlbiB0aGUgc2VuZGVyIG9mIHRoZSBUUExSIGFuZCB0aGUNCj4+PiBy
ZWNlaXZlciBvZiB0aGUgbWVzc2FnZSBpcyB0aGUgbW9zdCBhcHByb3ByaWF0ZSB0byB1c2Ugd2hl
biBzdXBwcmVzc2luZw0KPj4+IHRoZSBtZXNzYWdlLiBJIGFtIG5vdCBjZXJ0YWluIHRoYXQgaXMg
dGhlIGNhc2UuDQo+Pj4NCj4+PiBMZXRzIGNvbnNpZGVyIHRoZSB1c2UgY2FzZXMuIEluIHRoZSBj
YXNlIG9mIGFuIGludGVybWVkaWFyeSBpbiBhDQo+Pj4gZGlzdHJpYnV0aW9uIHRyZWUgc2VuZGlu
ZyB0aGUgVFBMUiBhbmQgYXQgdGhlIHNhbWUgdGltZSBzZW5kaW5nIGEgTkFDSw0KPj4+IHVwc3Ry
ZWFtLiBUaGVuIHRoZSB0aW1lIHVudGlsIHRoZSByZXRyYW5zbWlzc2lvbiByZWFjaGVzIHRoZSBz
dXBwcmVzc2VkDQo+Pj4gcmVjZWl2ZXIgaXMgdGhlIHRpbWUgZnJvbSB0aGUgc2VuZGluZyBvZiB0
aGUgTkFDSyB1cCB0byB0aGUNCj4+PiByZXRyYW5zbWl0dGluZyBlbnRpdHkgYW5kIGFsbCB0aGUg
d2F5IGRvd24gcGFzdCB0aGUgVFBMUiBzZW5kZXIgdG8gdGhlDQo+Pj4gc3VwcHJlc3NlZCByZWNl
aXZlci4gVGhlIHJlY2VpdmVyIG1heSBub3QgaGF2ZSBhIHRydWUgUlRUIHRvIHRoZQ0KPj4+IG9y
aWdpbmFsIG1lZGlhIHNlbmRlciBhcyB0aGF0IHNvdXJjZSBhcHBlYXJzIHRvIGxpdmUgYXQgdGhl
IFRQTFIgc2VuZGVyLA0KPj4+IG5vdCBmdXJ0aGVyIHVwc3RyZWFtLg0KPj4+DQo+Pj4gWWVzLCB0
aGUgc2VuZGVyIG9mIHRoZSBUUExSIGFuZCB0aGUgcmVjZWl2ZXIgbWlnaHQgYXQgbGVhc3QgaGF2
ZSBtdXR1YWwNCj4+PiBrbm93bGVkZ2Ugb2YgZWFjaCBvdGhlciwgdGh1cyB0aGUgVFBMUiBzZW5k
ZXIgaXMgYWJsZSB0byBkZXRlcm1pbmUgdGhlDQo+Pj4gbG93ZXN0IFJUVCBpbiB0aGUgc2V0IG9m
IHJlY2V2aWVycyB0aHVzIGRldGVybWluaW5nIGhvdyBvZnRlbiB0byByZXBlYXQNCj4+PiBpdCB0
byBjb3ZlciBhZGRpdGlvbmFsIHRpbWUgcmVxdXJpZWQgZm9yIHRoZSB1cHN0cmVhbSBwYXJ0IG9m
IHRoZQ0KPj4+IHJlcXVlc3QuIEJ1dCBJIGRvIG5vdGUgdGhhdCB0aGVzZSB0aW1lcyBhcmVuJ3Qg
bWF0Y2hpbmcgd2hhdCBhcHBlYXIgdG8NCj4+PiBiZSB0aGUgZGVsYXlzIGluIHRoZSBzeXN0ZW1z
Lg0KPj4+DQo+Pj4gQ2FuIHdlIGZpbmQgYSBiZXR0ZXIgc29sdXRpb24/DQo+Pj4gIA0KPj4+DQo+
Pj4gW1Fpbl06IEl0IGxvb2tzIHRvIG1lIHRoZSByb3VuZCB0cmlwIHRpbWUgYmV0d2VlbiBtZWRp
YSBzb3VyY2UgYW5kDQo+Pj4NCj4+PiAgaW50ZXJtZWRpYXJ5IGlzIHRyaXZpYWwgaWYgd2UgYXNz
dW1lIHRoZSBpbnRlcm1lZGlhcnkgaXMgbXVjaA0KPj4+DQo+Pj4gY2xvc2VyIHRvIHRoZSBzb3Vy
Y2UsIHRoYXQgaXMgd2h5IEkgcHV0IHRoZSBsYXN0IHBhcmFncmFwaCBpbiB0aGUNCj4+Pg0KPj4+
IHNlY3Rpb24gMyBhcyBmb2xsb3dzOg0KPj4+DQo+Pj4gkw0KPj4+DQo+Pj4gSW4gb3JkZXIgbm90
IHRvIGluY3VyIGEgbG90IG9mIE5BQ0sgcmVxdWVzdHMgZHVlIHRvIGFkZGl0aW9uYWwgVFBMUg0K
Pj4+DQo+Pj4gZGVzY3JpYmVkIGFib3ZlLCBpdCBpcyByZWNvbW1lbmRlZCB0aGF0IHRoZSBSVFAg
c3lzdGVtIHNlbmRpbmcNCj4+Pg0KPj4+IFRQTFIgc2hvdWxkIGJlIGltcGxlbWVudGVkIG1vcmUg
Y2xvc2VyIHRvIHRoZSBzb3VyY2UuIEFsc28gd2hlbg0KPj4+DQo+Pj4gIHRoZSBsb3NzIHdhcyBk
ZXRlY3RlZCBhbmQgcmVwYWlyIGluaXRpYXRlZCBtdWNoIGNsb3NlciB0byB0aGUgc291cmNlLA0K
Pj4+DQo+Pj4gdGhlIGRlbGF5IGZvciB0aGUgcmVjZWl2ZXIgdG8gcmVjb3ZlciBmcm9tIHBhY2tl
dCBsb3NzIGNhbiBiZSByZWR1Y2VkDQo+Pj4NCj4+PiB0aHJvdWdoIHRoZSBjb21iaW5hdGlvbiBv
ZiBpbnRlcm1lZGlhcnkgZmVlZGJhY2sgdG8gdGhlIHNvdXJjZSBhbmQNCj4+Pg0KPj4+IFRoaXJk
IFBhcnR5IExvc3MgUmVwb3J0IGRvd25zdHJlYW0uDQo+Pj4NCj4+PiCUDQo+Pj4NCj4+PiAgDQo+
Pj4NCj4+PiBJZiB3ZSBsb29rIGZvciBhIGJldHRlciBzb2x1dGlvbiwgSSB0aGluayB3ZSBoYXZl
IHR3byBwb3NzaWJsZSB3YXlzOg0KPj4+DQo+Pj4gVGhlIGZpcnN0IHdheSBpcyB0byByZWx5IG9u
IHNlbmRlciByZXBvcnQgZnJvbSBtZWRpYSBzZW5kZXIgdG8NCj4+Pg0KPj4+IGNhbGN1bGF0ZSB0
aGUgbW9yZSBhcHByb3hpbWF0ZSBSVFQgZnJvbSBtZWRpYSBzZW5kZXIgdG8gdGhlIHJlY2VpdmVy
Lg0KPj4+DQo+Pj4gUlRUIG1lYXN1cmVtZW50IG1ldGhvZCBmb2xsb3dzIHRoZSBzYW1lIHdheSBk
ZXNjcmliZWQgaW4gdGhlDQo+Pj4NCj4+PiBmaWd1cmUgMiBvZiBSRkMzNTUwLg0KPj4+DQo+Pj4g
IA0KPj4+DQo+Pj4gVGhlIHNlY29uZCB3YXkgaXMgdG8gd2UgY2FuIGFsbG93IHRoZSBpbnRlcm1l
ZGlhcnkgdGVsbCB0aGUgcmVjZWl2ZXIgdGhlDQo+Pj4NCj4+PiBSVFQgZnJvbSBtZWRpYSBzb3Vy
Y2UgdG8gaW50ZXJtZWRpYXJ5IGl0c2VsZiBieSBzZW5kaW5nIGEgbmV3IG1lc3NhZ2UNCj4+Pg0K
Pj4+IHNpbmNlIHRoZSBpbnRlcm1lZGlhcnkgY2FuIG1lYXN1cmUgc3VjaCBSVFQgYmFzZWQgb24g
cGFzdCBvYnNlcnZhdGlvbg0KPj4+DQo+Pj4gYW5kIGVzdGltYXRpb24uIEhvd2V2ZXIgZm9yIHRo
ZSBzZWNvbmQgd2F5IHdlIG5lZWQgdG8gZGVmaW5lIG5ldw0KPj4+DQo+Pj4gbWVzc2FnZSBvciBl
eHRlbmQgVFBMUiBtZXNzYWdlIHRvIGNhcnJ5IHN1Y2ggUlRULg0KPj4+DQo+Pj4gIA0KPj4+DQo+
Pj4gV2hhdCBkbyB5b3UgdGhpbms/DQo+Pj4NCj4+DQo+PiBGcm9tIGZvbGxvdyB1cCBlbWFpbDoN
Cj4+PiBIaSxNYWdudXM6IEFzIHJlZ2FyZGluZyBpZiB0aGVyZSBpcyBiZXR0ZXIgc29sdXRpb24s
IEkgaGF2ZSBzb21lDQo+Pj4gY29ycmVjdGlvbnMgYW5kIGFkZGl0aW9uYWwgdGhvdWdodHMuDQo+
Pj4gSSB0aGluayBJZiB0aGUgbWVkaWEgc291cmNlIGlzIHRoZSByZXBhaXIgc2VydmVyLCB0aGUg
cmVjZWl2ZXIgc2hvdWxkDQo+Pj4gc2V0IHRpbWVyIHRvIFQxPW1heCh0aGUgUlRUIGZyb20gbWVk
aWEgc291cmNlIHRvIG1pZGRsZWJveCBzZW5kaW5nDQo+Pj4gVFBMUiwgMS8yIG9mIFJUVCBmcm9t
IG1pZGRsZWJveCB0byByZWNlaXZlcikgd2hlbiB0aGUgcmVjZWl2ZXINCj4+PiByZWNlaXZlcyBm
aXJzdCBUUExSLiBXaGVuIHRoZSByZWNlaXZlciByZWNlaXZlIGFkZHRpb25hbCBUUExSIHdpdGhp
bg0KPj4+IFQxLCB0aGUgcmVjZWl2ZXIgc2hvdWxkIHJlc2V0IHRoZSB0aW1lciB0byB0aGUgUlRU
IGZyb20gbWVkaWEgc291cmNlDQo+Pj4gdG8gbWlkZGxlYm94IHNlbmRpbmcgVFBMUi4NCj4+Pg0K
Pj4+IElmIHRoZSBtaWRkbGVib3ggaXMgdGhlIHJlcGFpciBzZXJ2ZXIsIHRoZSByZWNlaXZlciBz
aG91bGQgc2V0IHRoZQ0KPj4+IHRpbWVyIHRvIFQyPTEvMiBvZiBSVFQgZnJvbSBtaWRkbGVib3gg
dG8gcmVjZWl2ZXIgd2hlbiB0aGUgcmVjZWl2ZXINCj4+PiByZWNlaXZlcyBmaXJzdCBUUExSLiBX
aGVuIHRoZSByZWNlaXZlciByZWNlaXZlIGFkZHRpb25hbCBUUExSIHdpdGhpbg0KPj4+IFQyLCB0
aGUgcmVjZWl2ZXIgc2hvdWxkIHJlc2V0IHRoZSB0aW1lciB0byB0aGUgVDIuDQo+Pj4NCj4+DQo+
PiBDYW4geW91IGV4cHJlc3MgdGhlc2UgcnVsZXMgZm9yIHRoZSByZWNlaXZlciBhcyBzb21ldGhp
bmcgdGhhdCBpcyBiYXNlZA0KPj4gb24gd2hhdCBpcyBvYnNlcnZhYmxlIGZyb20gdGhlIFJUUCBh
bmQgUlRDUCB0cmFmZmljPyBJcyB3aGVuIG1lZGlhDQo+PiBzZXJ2ZXIgYmVpbmcgcmVwYWlyIHNl
cnZlciBlcXVhbCB0byBUUExSIHNlbmRlciBTU1JDID0gTWVkaWEgU1NSQyB0aGUNCj4+IFRQTFIg
YXBwbGllcyBvbj8gQW5kIGlmIHRoZXkgYXJlIG5vdCB0aGUgc2FtZSBpdCBpcyB0aGUgc2Vjb25k
IGNhc2U/DQo+Pg0KPiANCj4gDQo+IFtRaW5dOiBPa2F5LCBJIHRoaW5rIHRoZSBtZWRpYSBzb3Vy
Y2Ugd2lsbCBub3QgYmUgdGhlIFRQTFIgc2VuZGVyLiANCj4gDQo+ICANCj4gDQo+IFRoZSByZWNl
aXZlciBzaG91bGQgc2V0IHRoZSB0aW1lciBmb3IgdGhlIHJldHJhbnNtaXR0ZWQgZGF0YSBwYWNr
ZXQgd2hlbiBpdCByZWNlaXZlIHRoZSBmaXJzdCBUUExSLg0KPiANCj4gDQo+IA0KPiANCj4gSWYg
dGhlIHNlbmRlciBvZiBSZXRyYW5zbWl0dGVkIGRhdGEgcGFja2V0IGlzIHRoZSBtZWRpYSBzb3Vy
Y2UsIHRoZSB0aW1lciB2YWx1ZSBzaGFsbCBiZQ0KPiANCj4gYmFzZWQgb24gdGhlIG9ic2VydmVk
IHRpbWUgZGlmZmVyZW5jZSBiZXR3ZWVuIHRoZSByb3VuZC10cmlwIHRpbWUgZnJvbSB0aGUgcmVj
ZWl2ZXIgdG8gDQo+IA0KPiB0aGUgb3JpZ2luYWwgbWVkaWEgc291cmNlIGFuZCB0aGUgcm91bmQt
dHJpcCB0aW1lIGZyb20gdGhlIHJlY2VpdmVyIHRvIHRoZSBzZW5kZXIgb2YgdGhlIFRQTFIuICAN
Cg0KSG93IGRvZXMgdGhlIHJlY2VpdmVyIG9mIGEgVFBMUiBrbm93IHRoYXQgdGhlIHNlbmRlciBv
ZiB0aGUNCnJldHJhbnNtaXR0ZWQgZGF0YSBwYWNrZXQgd2lsbCBiZSB0aGUgbWVkaWEgc3RyZWFt
IHNvdXJjZT8NCg0KQW5kIGlmIHRoaXMgaWYgc3RhdGVtZW50IGlzIG5vdCB0cnVlLCB3aGF0IHNo
b3VsZCB0aGUgdGltZXIgdmFsdWUgYmU/DQoNCltRaW5dOiBJc24ndCBieSB0aGUgU0RFUyBwYWNr
ZXQuIEFjY29yZGluZyB0byBSRkM0NTg4LCBzZWN0aW9uIDUuMiwgdGhlIG1lZGlhIHNvdXJjZSBN
VVNUDQp1c2UgdGhlIHNhbWUgQ05BTUUgZm9yIGFuIG9yaWdpbmFsIHN0cmVhbSBhbmQgaXRzIGFz
c29jaWF0ZWQgcmV0cmFuc21pc3Npb24gc3RyZWFtLg0KDQo+IA0KPiANCj4gDQo+IEEgcmVjZWl2
ZXIgc2hvdWxkIGNvbXB1dGUgYW4gZXN0aW1hdGUgb2YgdGhlIHJvdW5kLXRyaXAgdGltZSAoUlRU
KSB0byB0aGUgb3JpZ2luYWwgbWVkaWEgc291cmNlIA0KPiANCj4gZnJvbSBTZW5kZXIgUmVwb3J0
IChTUikgcGFja2V0cyBmb3IgdGhlIG9yaWdpbmFsIHN0cmVhbSwgb3IgYW55IG90aGVyIG1lYW5z
LiBUaGUgcm91bmQtdHJpcCB0aW1lIA0KPiANCj4gZnJvbSB0aGUgcmVjZWl2ZXIgdG8gdGhlIHNl
bmRlciBvZiB0aGUgVFBMUiBjYW4gYmUgY2FsY3VsYXRlZCBmcm9tIFJUQ1AgcmVwb3J0IHJvdW5k
LXRyaXAgdGltZSANCj4gDQo+IGlmIGF2YWlsYWJsZSwgb3IgYW55IG90aGVyIG1lYW5zLg0KPiAN
Cg0KSSB0aGluayB0aGlzIG5lZWRzIHRvIGJlIG1vcmUgZXhwbGljaXQgb24gaG93IHRoYXQgZXN0
aW1hdGUgYWN0dWFsbHkgY2FuDQpiZSBkb25lIGFuZCB3aGF0IHByZWNpc2lvbiB3ZSBleHBlY3Qg
aW4gaXQuDQoNCltRaW5dOiBBZ3JlZS4NCg0KQ2hlZXJzDQoNCk1hZ251cyBXZXN0ZXJsdW5kDQoN
Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0NCk11bHRpbWVkaWEgVGVjaG5vbG9naWVzLCBFcmljc3NvbiBSZXNlYXJj
aCBFQUIvVFZNDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpFcmljc3NvbiBBQiAgICAgICAgICAgICAgICB8IFBo
b25lICArNDYgMTAgNzE0ODI4Nw0KRuRy9mdhdGFuIDYgICAgICAgICAgICAgICAgfCBNb2JpbGUg
KzQ2IDczIDA5NDkwNzkNClNFLTE2NCA4MCBTdG9ja2hvbG0sIFN3ZWRlbnwgbWFpbHRvOiBtYWdu
dXMud2VzdGVybHVuZEBlcmljc3Nvbi5jb20NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg==


From magnus.westerlund@ericsson.com  Fri Nov  4 02:58:39 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36BCA21F8B71 for <avt@ietfa.amsl.com>; Fri,  4 Nov 2011 02:58:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.561
X-Spam-Level: 
X-Spam-Status: No, score=-106.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DJTCMkgE7SN6 for <avt@ietfa.amsl.com>; Fri,  4 Nov 2011 02:58:38 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id D133721F8B7B for <avt@ietf.org>; Fri,  4 Nov 2011 02:58:37 -0700 (PDT)
X-AuditID: c1b4fb39-b7b3eae00000252a-8a-4eb3b74c5a30
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 25.C4.09514.C47B3BE4; Fri,  4 Nov 2011 10:58:36 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.137.0; Fri, 4 Nov 2011 10:58:36 +0100
Message-ID: <4EB3B74A.4090909@ericsson.com>
Date: Fri, 4 Nov 2011 10:58:34 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
References: <FCC100FC8D6B034CB88CD8173B2DA158155893E1@EXC-MBX03.tsn.tno.nl> <4EB2A5C6.10004@ericsson.com> <FCC100FC8D6B034CB88CD8173B2DA1581558DD8A@EXC-MBX03.tsn.tno.nl>
In-Reply-To: <FCC100FC8D6B034CB88CD8173B2DA1581558DD8A@EXC-MBX03.tsn.tno.nl>
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] Comments on draft-westerlund-avtcore-rtp-simulcast-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 04 Nov 2011 09:58:39 -0000

Ray,

I have removed all points where the is nothing to follow up. We will
take your comments into account when preparing an update.

On 2011-11-03 16:27, Brandenburg, R. (Ray) van wrote:
> -----Original Message----- From: Magnus Westerlund
> [mailto:magnus.westerlund@ericsson.com] Sent: donderdag 3 november
> 2011 15:32 To: Brandenburg, R. (Ray) van Cc: avt@ietf.org Subject:
> Re: [AVTCORE] Comments on draft-westerlund-avtcore-rtp-simulcast-00
> 
>> 
>> -          Section 3: This section talks quite a bit about the
>> relation between Simulcast and Scalable Coding and in which
>> situations one of the two is more suitable. I'm not sure why this
>> is relevant. Simulcast and Scalable Coding might be two techniques
>> that in some cases can be used to solve the same problem, the layer
>> on which they do this is completely different (codec-level versus
>> transport level). The fact that Scalable Coding might, in some
>> situations, be a better solution than Simulcast does not mean that
>> Simulcast should not be standardized to handle those situations. I
>> understand that you've written this mainly from a video
>> conferencing perspective, in which Scalable Coding might be used
>> more often, but in a lot of situations, such as IPTV, Scalable
>> Coding is just not an option due to its inherent complexity. In
>> these situations Simulcast might be able to solve some real issues,
>>  despite the fact that Scalable Coding might be able to solve these
>> issues more efficiently.
>> 
> 
> I think layered encoding is both a codec level and a transport level
> thing. Just as in simulcast you need transport level methods for
> selecting the media streams/layers that you want to receive.
> 
> I fully agree that there are use cases where one might be considered
> much more appropriate than the other. And that is part of our
> arguments for why it should be defined for usage also, even though we
> have layered coding specified.
> 
> [RAY: I don't agree with you that layered coding is a transport-level
> thing (or maybe I don't understand your definition of layered coding.
> With layered coding I mean e.g. SVC). It might be that layered-coding
> requires some specific transport-level properties (such as
> alignment), however these are not unique to layered coding. Your
> draft (or specifically section 3) seems to imply that Simulcast can
> be considered an alternative to Scalable Coding and that you
> therefore have to argue why Simulcast is better in some situations.
> In my opinion, Scalable Coding is an alternative to creating multiple
> bitrates/resolutions (i.e. Adaptive Streaming) and not to Simulcast.
> My understanding is that Simulcast is a method to deliver those
> multiple bitrates, the same way it could be used to deliver Scalable
> Coding streams.]

Yes, SVC is one realization of layered encoding. And what I am getting
at is that SVC being a encoding technology do have specific transport
requirements to enable its functionality in some systems. For SVC this
is either a media aware network entity (MANE) that can remove layers
en-route. Or using multicast or other methods on the transport layers to
select the layers encoded.

I will not strongly disagree with your characterization in the second
half of the paragraph. I wouldn't use "adaptive streaming" as we are
interested in real-time conversational use cases, rather than content
delivery with somewhat relaxed source to receiver delay requirements.
But yes what we are discussing are methods for realization of adaptive
media delivery in point to multi-point scenarios.


>> 
>> 
>> 
>> -          Section 6.2: How do you suggest the sequence numbers and
>> RTP timestamps are handled between multiple alternative streams?
>> Would it make things easier if these were aligned across multiple
>> streams?
> 
> No, I don't believe in alignment. first of all the sequence numbers
> needs to progress with the packets actually sent for a media stream. 
> Encoding alternatives are quite likely to have different packet
> rates, especially for video as soon as one comes to a media bit-rate
> where some alternative requires multiple packets per video frame.
> 
> When it comes to timestamp I don't see any need either. For the best
> robustness and simplicity one should simply skip using alignment and
> instead use the mechanism for synchronizing media clocks with each
> other that exist, i.e. RTCP SR and Rapid Synchronization of RTP flows
> (RFC 6051).
> 
> [RAY: For the sequence numbers I agree, however about the timestamps
> I'm not so sure. In some cases it might be particularly useful to
> align timestamps. One example are areas where you need bit-level
> alignment (such as SVC and spatially segmented streams). For these
> situations NTP-based solutions such as RTCP SR are not accurate
> enough]

I would not completely dismiss timestamp alignment, however it has on
multiple times become clear that mechanism that attempts to rely on more
of the basic and well defined behaviors of RTP header fields have
encountered issues or resulted in limitations with which RTP extensions
they can interop. So it is more to caution people here.

I don't quite see what you mean with bit-level alignment in the
discussion of timestamps. To my knowledge the SVC payload format is so
defined that this isn't an issue. In SST all layers are sent under a
single SSRC in a single timestamp space in one single media stream. Thus
common timeline is used for all NALUs in all layers. When using MST the
layers will be in differnt media streams in different RTP sessions. Here
using the same timestamp values or not is still dependent on them
mapping to the common sender clock represented by the NTP time. I think
RTP has no issues mapping multiple SSRC timestamp value with random
offset to the same time base clock to a granularity that is equivalent
to the the precision of the NTP values provided in the RTCP SR packets.
Taking care I think a precision better than 1/2^30 of a second i
possible. That is more than sufficient to align frames.

If you with bit-alignment means that you need to indicate that the
content of the packet is starting at the 10th line from the top and 240
pixels in, then I think using the timestamp for that is the wrong
choice. Instead the payload formats should use the timestamp to
correctly id the frame, and then use other explicit indicators for
off-set or relation.


> 
> [RAY: Sorry for not being any clearer. We have a different
> understanding of tiled streaming (or spatial segmentation as is
> probably more descriptive). The use case is not having four
> network-connected projectors. The use case is having a mobile device
> with a relatively low resolution (e.g. 480x320 pixels) being able to
> navigate through high resolution (4k/8k) content. By splitting the
> output of a single 4k camera into 'tiles' of for example 240x160
> pixels, and storing each of these as a separate stream, a client can
> request multiple streams simultaneously and reconstruct part of the
> original video (in this case it would request 4 'tiles'). When a user
> wants to navigate through the content (e.g. pan/zoom) it requests a
> different subset of tiles. As you can see, what we have here is a
> large number of tiles (streams), coming from the same source, with
> different clients requesting different subsets of these tiles. In
> that aspect, it is not that dissimilar from some of the use cases you
> describe in your draft.]

Thanks for the explanation, it was needed. I haven't heard of that usage
of tiled in the context of video before.

First of all, I think this is something new and we should discuss the
most appropriate way or possible ways to transport this. I don't think
this belongs in the RTP simulcast draft as the use cases are currently
defined. The reason is that in all the cases of the simulcast we are
discussing are that the alternative media streams tries to represent the
full source, although at different quality levels when it comes to SNR,
resolution etc. While tiled video is dealing with the selection and
handling of multiple partial representations of a source.

I think one way of dealing with tiled video is to make each tile
separate media stream, where each tile will use its own SSRC. Thus one
could potentially on SSRC level control if a stream is being delivered
or not. Another way of viewing the problem is to only use as many SSRCs
as you need simultaneously delivered tiles. Then you use something other
than SSRCs to indicate which tile is currently delivered in each media
stream.

I think this is an interesting problem, if you are interested in
standardizing a recommended way of handling tiled video you should
create a separate internet draft to discuss this problem.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From magnus.westerlund@ericsson.com  Fri Nov  4 03:02:00 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E75B21F8B84 for <avt@ietfa.amsl.com>; Fri,  4 Nov 2011 03:02:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.562
X-Spam-Level: 
X-Spam-Status: No, score=-106.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id REbNWfPXUfSj for <avt@ietfa.amsl.com>; Fri,  4 Nov 2011 03:01:59 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 3F82F21F8B7D for <avt@ietf.org>; Fri,  4 Nov 2011 03:01:59 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-7c-4eb3b815f2cd
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id E4.C4.13753.518B3BE4; Fri,  4 Nov 2011 11:01:57 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.137.0; Fri, 4 Nov 2011 11:01:57 +0100
Message-ID: <4EB3B814.6000206@ericsson.com>
Date: Fri, 4 Nov 2011 11:01:56 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Qin Wu <bill.wu@huawei.com>
References: <4EA12119.4090900@ericsson.com> <0C80BD8E8293426DB3C50CC7F1ECB0F1@china.huawei.com> <F3153DC2249E4F83B5290A559BFC8B80@china.huawei.com> <4EB29BA5.9080509@ericsson.com> <060F172CB45D4D49A13B930494895B84@china.huawei.com>
In-Reply-To: <060F172CB45D4D49A13B930494895B84@china.huawei.com>
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: IETF AVTCore WG <avt@ietf.org>, "draft-ietf-avtcore-monarch@tools.ietf.org" <draft-ietf-avtcore-monarch@tools.ietf.org>
Subject: Re: [AVTCORE] Comments on draft-ietf-avtcore-monarch-04
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 04 Nov 2011 10:02:00 -0000

On 2011-11-04 03:13, Qin Wu wrote:
> ----- Original Message ----- 
> From: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
> To: "Qin Wu" <bill.wu@huawei.com>
> Cc: "IETF AVTCore WG" <avt@ietf.org>; <draft-ietf-avtcore-monarch@tools.ietf.org>
> Sent: Thursday, November 03, 2011 9:48 PM
> Subject: Re: [AVTCORE] Comments on draft-ietf-avtcore-monarch-04
> 
> 
>> Hi,
>>
>> Removing all issues that don't need additional discussion or commenting.
>>
>>
>>
>> On 2011-10-25 07:45, Qin Wu wrote:
>>>
>>> 9. Section 4:
>>> "It is also
>>>       fixed across multiple RTP sessions from the same source."
>>>
>>> I interpret "source" in the above as an end-point or RTP node. Which
>>> causes me to have the following comment.
>>>
>>> This is very commonly true, but not universally true. As CNAME
>>> identifies a synchronziation context, a given end-point could have media
>>> sources that belong to multiple synchronization contexts in the same
>>> session. For example have microphones and cameras from multiple rooms,
>>> where each room will be its own synchronization context.
>>>
>>>
>>>
>>> [Qin]: Agree with your thinking, but here what we emphasize is "across multiple RTP session"
>>>
>>> Does this really conflict with what you said?
>>>
>>> Anyway I will reword this in the new vesion.
>>>
> 
>> No, as long as we consider source as media recording device(s) in a
>> given synchronization context they will be fixed across multiple sessions.
>>
> 
> 
> [Qin]: Okay, do we have other use cases besides the above one you gave?

Not from the top of my head.


>>>
>>> 21. Section 7.1:
>>>
>>> Strictly the RTP end
>>>    system can only conclude that its RTP has been lost in the network,
>>>    though an RTP end system complying with the robustness principle of
>>>    [RFC1122] should survive with essential functions unimpaired.
>>>
>>> What is the purpose with this sentence? And what is actually seen as
>>> "essential functions"?
>>>
>>>
>>>
>>> [Qin]: I think essential functions are referred to as "media distribution"
>>
>> So you mean that a robustly built end-point will still be able to send
>> its media despite the fact that media it should receive has been lost in
>> between the sender and this receiver?
> 
> [Qin]: That's my understanding, is that okay with you?

Yes.


> 
>>>
>>> 23. Section 8. I agree that this draft shouldn't have a IANA
>>> Consideration other to say that it is has no actions. However, I think
>>> the document should consider if it has some guidance on IANA actions for
>>> the monitoring architecture. Some part of this is clearly about the
>>> consumption of XR block code points that isn't a major issue. And if we
>>> do run out a second RTCP packet type for XR block 2 could be assigned.
>>>
>>>
>>>
>>> [Qin]: The WG consensus is space depletion is not issue
>>>
>>> if you really want space expansion, you can define one XR block type
>>>
>>>  for vendor-specific extensions, with an enterprise number included 
>>>
>>> to identify the vendor making the extension. So I prefer to say
>>>
>>> "There is no IANA action in this document"
>>
>> Yes, but if that is the conclusion, shouldn't we document it?
> 
> [Qin]: Okay, I can put them in the new version.

Great

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From magnus.westerlund@ericsson.com  Fri Nov  4 03:40:27 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C382821F8C3C for <avt@ietfa.amsl.com>; Fri,  4 Nov 2011 03:40:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.564
X-Spam-Level: 
X-Spam-Status: No, score=-106.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kXdQFFAqDhJM for <avt@ietfa.amsl.com>; Fri,  4 Nov 2011 03:40:27 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id C903721F8BF6 for <avt@ietf.org>; Fri,  4 Nov 2011 03:40:24 -0700 (PDT)
X-AuditID: c1b4fb39-b7b3eae00000252a-0c-4eb3c10784b6
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 29.DC.09514.701C3BE4; Fri,  4 Nov 2011 11:40:07 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.137.0; Fri, 4 Nov 2011 11:39:32 +0100
Message-ID: <4EB3C0DC.7000906@ericsson.com>
Date: Fri, 4 Nov 2011 11:39:24 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: IETF AVTCore WG <avt@ietf.org>
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Subject: [AVTCORE] On the split of the RTP Multiple Stream Sessions and Simulcast draft
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 04 Nov 2011 10:40:27 -0000

Hi,

As Individual

In Quebec my colleagues and I had a draft named RTP Multiple Stream
Sessions and Simulcast
(https://datatracker.ietf.org/doc/draft-westerlund-avtcore-multistream-and-simulcast/)
which contained a number of RTP extensions and also general discussion
of how to do RTP simulcast.

The first think done was to split the discussion into two parts, one
common about RTP multiplexing in general. The goal here is to have
something that can aid when designing RTP extensions and application
designers in how to thing around the RTP multiplexing points and most
important what the pro and cons are of using SSRC multiplexing versus
Session multiplexing.

https://datatracker.ietf.org/doc/draft-westerlund-avtcore-multiplex-architecture/

As some of the extensions can be highly useful also outside of the
context of simulcast we have split them out as separate documents.

So in this WG we have the extension for explicit handling of multiple
SSRC in an RTP session. The extension is only a signaling one, but is
still kept in this WG due to that the underlying thinking needs
agreement we believe in this WG.
https://datatracker.ietf.org/doc/draft-westerlund-avtcore-max-ssrc/

In AVTEXT we have the RTCP SDES item SRCNAME that allows a single media
source to be identified over multiple media streams (SSRC) to enable
pairing of media streams that relate to each other, like retransmission,
FEC, duplication,  layered encoding, and simulcast.
https://datatracker.ietf.org/doc/draft-westerlund-avtext-rtcp-sdes-srcname/

In MMUSIC we have the proposal for a completely new SDP bandwidth
attribute.
https://datatracker.ietf.org/doc/draft-westerlund-mmusic-sdp-bw-attribute/

Finally we have the discussion of how to do RTP simulcast and the
session grouping extensions that we see as necessary for making RTP
simulcast work well which is in this WG.
https://datatracker.ietf.org/doc/draft-westerlund-avtcore-rtp-simulcast/

We have requested agenda time for the multiplexing architecture to start
with as that appears to be foundation for most of the other documents.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From magnus.westerlund@ericsson.com  Fri Nov  4 03:46:06 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38EB121F8BE9 for <avt@ietfa.amsl.com>; Fri,  4 Nov 2011 03:46:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.565
X-Spam-Level: 
X-Spam-Status: No, score=-106.565 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QrWcRbAIb4j0 for <avt@ietfa.amsl.com>; Fri,  4 Nov 2011 03:46:05 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 8A7B921F8B94 for <avt@ietf.org>; Fri,  4 Nov 2011 03:46:00 -0700 (PDT)
X-AuditID: c1b4fb39-b7b3eae00000252a-2a-4eb3c24ca7bc
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id BA.ED.09514.C42C3BE4; Fri,  4 Nov 2011 11:45:34 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.137.0; Fri, 4 Nov 2011 11:45:23 +0100
Message-ID: <4EB3C241.7030903@ericsson.com>
Date: Fri, 4 Nov 2011 11:45:21 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: IETF AVTCore WG <avt@ietf.org>
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Subject: [AVTCORE] Multiple RTP Session on a Single Lower-Layer Transport
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 04 Nov 2011 10:46:06 -0000

Hi,

As Individual

Colin Perkins and I have this draft regarding Multiple RTP Session on a
Single Lower-Layer Transport.

https://datatracker.ietf.org/doc/draft-westerlund-avtcore-transport-multiplexing/

We had discussion in the Quebec AVTCORE meeting regarding how to deal
with multiplexing of multiple RTP sessions over a single transport. In
Quebec a lot of focus was on the RTCWEB requirements. But the poll among
the present showed a strong interest in the generalized solution to this
problem. Therefore we have produced this document with a proposal

We plan to discuss this in the upcoming meeting. So please review the
document and any mailing list feedback is much appreciated.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From andrew.hutton@siemens-enterprise.com  Fri Nov  4 04:23:46 2011
Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 842FE21F8C3F; Fri,  4 Nov 2011 04:23:46 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6kHBjzMZ1VsF; Fri,  4 Nov 2011 04:23:45 -0700 (PDT)
Received: from senmx12-mx.siemens-enterprise.com (senmx12-mx.siemens-enterprise.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id 7255221F8C34; Fri,  4 Nov 2011 04:23:42 -0700 (PDT)
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx.siemens-enterprise.com (Server) with ESMTP id B38AB23F041E; Fri,  4 Nov 2011 12:23:40 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Fri, 4 Nov 2011 12:23:40 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: IETF AVTCore WG <avt@ietf.org>
Date: Fri, 4 Nov 2011 12:23:39 +0100
Thread-Topic: SIPREC draft relating to RTP
Thread-Index: Acx48cGG5DyouTPCThiVpxSEwYHLVgh7b2bA
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E311F809B130@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CA0BC11A84A0@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA0BC11A84A0@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: [AVTCORE] SIPREC draft relating to RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 04 Nov 2011 11:23:46 -0000

Hi AVTCORE,

The SIPREC (SIP Session Recording) WG are still looking for AVT experts who=
 can review draft http://datatracker.ietf.org/doc/draft-eckel-siprec-rtp-re=
c/. The draft provides recommendations and guidelines for RTP/RTCP in the c=
ontext of SIPREC.

If you are an expert and can help please consider reviewing the document an=
d attending the SIPREC session at IETF82 (See http://www.ietf.org/proceedin=
gs/82/agenda/siprec.html).


Regards
Andy (SIPREC co-chair).




> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Elwell, John
> Sent: 22 September 2011 07:35
> To: IETF AVTCore WG
> Cc: siprec@ietf.org
> Subject: [AVTCORE] SIPREC draft relating to RTP
>=20
> AVTCORE members,
>=20
> Please be aware that an updated I-D has been published:
> https://datatracker.ietf.org/doc/draft-eckel-siprec-rtp-rec/
>=20
> This discusses use of RTP in the context of SIPREC, and contains
> candidate normative material for inclusion in the SIPREC protocol
> document.
>=20
> SIPREC is holding a virtual interim meeting on Friday (13.00 GMT/UTC):
> http://www.timeanddate.com/worldclock/fixedtime.html?msg=3DSIPREC_interim
> _part2&iso=3D20110923T13&ah=3D2
>=20
> This draft will be the first agenda item. Slides are available in the
> official place:
> http://www.ietf.org/proceedings/interim/2011/09/19/siprec/proceedings.h
> tml
>=20
> Webex details are available here:
> http://www.ietf.org/mail-archive/web/siprec/current/msg02535.html
>=20
> It would be great to receive feedback on the draft from RTP experts
> and/or participation in Friday's discussions. Apologies for the short
> notice and for the inconvenient time for some of you (we have a number
> of Asian key participants).
>=20
> John (SIPREC co-chair)
>=20
> John Elwell
> Tel: +44 1908 817801 (office and mobile)
> Email: john.elwell@siemens-enterprise.com
> http://www.siemens-enterprise.com/uk/
>=20
> Siemens Enterprise Communications Limited.
> Registered office: Brickhill Street, Willen Lake, Milton Keynes, MK15
> 0DJ.
> Registered No: 5903714, England.
>=20
> Siemens Enterprise Communications Limited is a Trademark Licensee of
> Siemens AG.
>=20
>=20
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt

From magnus.westerlund@ericsson.com  Fri Nov  4 05:27:17 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E40D921F8BCB; Fri,  4 Nov 2011 05:27:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.565
X-Spam-Level: 
X-Spam-Status: No, score=-106.565 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yyUuhayvwVWm; Fri,  4 Nov 2011 05:27:17 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id DD83721F8BC5; Fri,  4 Nov 2011 05:27:16 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-f1-4eb3da239fda
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 0F.1B.13753.32AD3BE4; Fri,  4 Nov 2011 13:27:15 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.137.0; Fri, 4 Nov 2011 13:27:14 +0100
Message-ID: <4EB3DA1B.7040908@ericsson.com>
Date: Fri, 4 Nov 2011 13:27:07 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
References: <A444A0F8084434499206E78C106220CA0BC11A84A0@MCHP058A.global-ad.net> <101C6067BEC68246B0C3F6843BCCC1E311F809B130@MCHP058A.global-ad.net>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E311F809B130@MCHP058A.global-ad.net>
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: "siprec@ietf.org" <siprec@ietf.org>, IETF AVTCore WG <avt@ietf.org>
Subject: Re: [AVTCORE] SIPREC draft relating to RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 04 Nov 2011 12:27:18 -0000

On 2011-11-04 12:23, Hutton, Andrew wrote:
> Hi AVTCORE,
> 
> The SIPREC (SIP Session Recording) WG are still looking for AVT
> experts who can review draft
> http://datatracker.ietf.org/doc/draft-eckel-siprec-rtp-rec/. The
> draft provides recommendations and guidelines for RTP/RTCP in the
> context of SIPREC.
> 
> If you are an expert and can help please consider reviewing the
> document and attending the SIPREC session at IETF82 (See
> http://www.ietf.org/proceedings/82/agenda/siprec.html).
> 

WG Participants

Please help SIPREC with this. If you are doing a review, please drop us
AVTCORE chairs an email so we know that they get help.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From versteb@cisco.com  Fri Nov  4 08:29:42 2011
Return-Path: <versteb@cisco.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0499B21F8C00 for <avt@ietfa.amsl.com>; Fri,  4 Nov 2011 08:29:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.441
X-Spam-Level: 
X-Spam-Status: No, score=-4.441 tagged_above=-999 required=5 tests=[AWL=2.158,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u9hgmlZqLrwV for <avt@ietfa.amsl.com>; Fri,  4 Nov 2011 08:29:40 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 924B321F8BF7 for <avt@ietf.org>; Fri,  4 Nov 2011 08:29:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=versteb@cisco.com; l=9191; q=dns/txt; s=iport; t=1320420580; x=1321630180; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=tGjwjnG8d4XmNea26VkJozOvzNxj4iLOqgt7sHO8JVE=; b=WhoqhfTPgfhj3wUWS2Hs8QTrnUff2qQicuSZZNdunzesiTTDkgjl2cEE +Zh313ZiR71mp24Hi5LKsgowKxMmiM30l8JbwDQIOmCc0vqfVw0DK+are IV1Uja11EQOGN2ljpF3paGch3mQAG+SCn2LW4e2Ae+kFC/VHzqLcYpcqi 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AroAAA0EtE6tJXG8/2dsb2JhbABEmhCPc4EFgXIBAQEDAQwGAR1JDAICAgEIEQQBAQEKBhcBBgEaKwkIAQEEEwgah2CWfwGeYwKIRmMEh1kxkUyMSg
X-IronPort-AV: E=Sophos;i="4.69,456,1315180800"; d="scan'208";a="33431607"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-3.cisco.com with ESMTP; 04 Nov 2011 15:29:40 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core2-1.cisco.com (8.14.3/8.14.3) with ESMTP id pA4FTeM9024451;  Fri, 4 Nov 2011 15:29:40 GMT
Received: from xmb-rcd-312.cisco.com ([72.163.63.27]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 4 Nov 2011 10:29:40 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 4 Nov 2011 10:29:39 -0500
Message-ID: <117602CF2B17DB4F9001427FA6D90539B48E80@XMB-RCD-312.cisco.com>
In-Reply-To: <4E9EE184.4090606@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVTCORE] WGLC on draft-ietf-avtcore-ecn-for-rtp-04
Thread-Index: AcyObSZa+JtVmMKwR6+G0g43YpNo1gMlhq+g
References: <016101cc7f6c$9795e380$c6c1aa80$%roni@huawei.com> <117602CF2B17DB4F9001427FA6D9053996F6FF@XMB-RCD-312.cisco.com> <4E9EE184.4090606@ericsson.com>
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-OriginalArrivalTime: 04 Nov 2011 15:29:40.0094 (UTC) FILETIME=[918CE1E0:01CC9B06]
Cc: avt@ietf.org
Subject: Re: [AVTCORE] WGLC on draft-ietf-avtcore-ecn-for-rtp-04
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 04 Nov 2011 15:29:42 -0000

Magnus-

I am still thinking about the problems identified with receivers that =
have varying levels of capabilities reading the ECN related markings.=20

In my mind, there are 3 categories of devices - "ECN compliant" (follows =
the specification), "ECN blind (can't read/write the ECN markings, but =
does not otherwise mangle the stream)", and "ECN incapable"(barfs on the =
stream).=20

The analysis in the draft is spot-on for unicast flows.

For RTP multicast streams, it is pretty clear how to handle =
ECN-compliant and ECN-incapable devices. There are a few flavors of =
ECN-blind, and I am still getting educated - so I may be missing some =
subtlety here, but...... It seems that allowing an ECN blind receiver to =
join an ECN-enabled multicast stream is fairly innocuous, and will not =
provide an advantage to that receiver over other receivers of the same =
flow. If the path allows the device to receive the probe packet, the =
discovery method works. The RTCP feedback will be received from all of =
the devices, and the data can be analyzed by the sender. Some of the =
feedback reports will have the ECN information, and some not.=20

The alternative is to instantiate another flow that is not ECN marked. =
If we apply the same fairness test to these two flows, it is not clear =
that we have made an improvement. If we look at the BW consumption, it =
is clear that we have made congestion worse rather than better. In fact, =
we have doubled the BW. It seems to me that if we are trying to control =
congestion, a single flow is (almost always) better than two flows. This =
is particularly true of IPTV-style deployments.

These thoughts are not rock-solid, and I would like to understand the =
problem space a bit better.

So, can somebody enlighten me on the following

1- What Berkeley Sockets extension is used to read the ECN-related bits? =

2- What hosts in the wild are running operating systems that do not =
support a variant of these extensions?

bvs


-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]=20
Sent: Wednesday, October 19, 2011 10:41 AM
To: Bill Ver Steeg (versteb)
Cc: Roni Even; avt@ietf.org
Subject: Re: [AVTCORE] WGLC on draft-ietf-avtcore-ecn-for-rtp-04

Bill,

Thanks for the review. I here respond to the major issues. If needed I
will follow up on the minor issues, otherwise I will simply implement
them in the next update.

On 2011-10-12 14:57, Bill Ver Steeg (versteb) wrote:
>=20
> For the multicast case, we need to make it clear that feedback goes to
> the feedback target, which may be a different device than the source.
> This document consistently says "feedback goes to the source", which =
is
> misleading. See the detailed comments below for the places in which I
> found it to be most concerning. When viewed in the context of feedback
> going to a discrete feedback target at the network egress edge (like
> typical IPTV deployments), it makes sense for the feedback target to =
use
> these reports as diagnostic in nature. Perhaps the network has changed
> topology and caused a bottleneck link to appear, and the feedback is
> triggering action in the network to fix the congestion in a systematic
> manner. It is highly unlikely that RTCP feedback will be able to =
change
> the rate of a flow in such a system. It is more likely that the system
> would take other actions, but that is probably beyond the scope of =
this
> document.

I think we might not have been sufficient clear on the SSM case. But in
fact for this to work, the Feedback Targets will need to relay the
feedback, at least in aggregated form to the source (or at least the
entity marking the packets as ECN which might be the Distributuion
Source).

>=20
> =20
>=20
> If a host is unable to read the ECN bits, it can't join an ECN-enabled
> flow? This seems to be quite onerous, and will likely slow down the
> adoption of ECN for RTP - particularly in the IPTV multicast case. If =
an
> operator needs to dual carry hundreds of video channels (one ECN =
marked
> and one not ECN marked), he will simply not implement ECN. I need to
> think about this a bit more and see if there is a way to make this =
work.
> My first instinct was to add a field/bit pattern to the RTCP feedback
> that says " I joined the ECN enabled flow, but can't actually read the
> ECT/ECN markings". However, let's think about na=EFve receivers that =
do
> not understand the ECN SDP. They will ignore that SDP line, and join =
the
> flow. They will provide their normal feedback, without the ECT/ECN
> portions. How is this different from a receiver that knows about ECN,
> but is unable to actually read the ECN bits? Maybe we just treat it =
like
> a legacy receiver that does not know about the ECN SDP....... So, we
> need to think about three receiver populations - fully ECN capable (as
> currently described in this document), ECN aware in the application =
but
> unable to read ECN bits (either acts like a legacy receiver or sends a
> special RTCP feedback message), ECN unaware (ignores the SDP). I have
> thought about this in the context of the declarative SDP case using =
leap
> of faith, but need to think more about the offer/answer case and the
> STUN case. We need a way to have each type of receiver unambiguously
> join the same multicast flow. This would allow an operator to
> incrementally deploy ECN on multicast flows. If we do not fix this, =
the
> operator will be gated on the very last device in his deployment.
>=20

Lets start with commenting on the naive receivers, if they join an ECN
enabled RTP session they will cause the session to stop using ECN. That
is why we say the same to a receiver that knows about ECN but can't read
the session. If they join they will force the session into not-ECT
operations.

Yes, this is onerous. But we can't frankly figure out how we can allow
any other behavior in any best-effort network. Having receivers get
preferential treatment of their traffic compared to not-ECT marked in a
best effort seems problematic if they aren't reporting back on it and
telling the sender to adjust the bit-rate.

We know from that start that ECN and large scale multicast would be
problematic and that is not our main target. This as it will be
difficult to combine source rate modifications with large groups.

I think we authors are still of the opinion that we develop what is safe
but possibly overly conservative and get that published. If people want
to improve the ECN in multicast usage later they are free to do so. But
tackling the issues that arise from letting non ECN capable receivers
into a group that uses ECN is problematic. So my opinion is that we
shouldn't change anything in this behavior.

>=20
> It would be nice to have the RTCWEB folks take a courtesy look, as =
they
> are envisioning some very interesting use cases. I do not think that
> this presents any specific challenges, but it would be good to have
> those eyeballs. I see that at least a few of them have provided =
comments.........
>=20

Which RTCWEB folks do you want to have a look at this?

My personal view that I would love to have overturned is that ECN in
open Internet is so dysfunctional that it is barely worth trying. Thus
adding ECN support to RTCWEB nodes in the initial phase is lots of work
for the implementor with very little bang back.

>=20
> A few minor points and a bit more specificity on the major
> points------------
>=20
> =20
>=20
> There is a delicate balancing act between providing timely congestion
> notifications to the sender and sending feedback packets into a
> congested network. It is not clear that the this balancing act is
> discussed in enough detail in the document. An inexperienced =
implementer
> may "do the wrong thing" and send packets to freely, thus making the
> congestion worse. Perhaps a short paragraph in the introduction would
> make this clear? Perhaps a paragraph at the end of Page 11? Also in
> section 7.3.2, as congestion is not highly featured in RFC4585 or
> RFC3550. Congestion is mentioned in 7.3.2, as is feedback implosion, =
but
> there is no warning about how they can interact.

I think we can add more warnings and check that we are clear on that one
must follow the transmission rules for the session the end-point is
operating. I would note that congestion is in fact likely asymmetric.
Thus just because you receive CE marked packets doesn't mean that the
RTCP FB packets will go over path that is loaded into congestion and of
course the reverse.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
F=E4r=F6gatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From p.ohanlon@gmail.com  Fri Nov  4 09:56:27 2011
Return-Path: <p.ohanlon@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90BA121F899D for <avt@ietfa.amsl.com>; Fri,  4 Nov 2011 09:56:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.73
X-Spam-Level: 
X-Spam-Status: No, score=-0.73 tagged_above=-999 required=5 tests=[AWL=-1.119,  BAYES_00=-2.599, FRT_STOCK2=3.988, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 99kOtfgLlsB6 for <avt@ietfa.amsl.com>; Fri,  4 Nov 2011 09:56:26 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7AB6121F8922 for <avt@ietf.org>; Fri,  4 Nov 2011 09:56:26 -0700 (PDT)
Received: by iaeo4 with SMTP id o4so3585565iae.31 for <avt@ietf.org>; Fri, 04 Nov 2011 09:56:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=mLY9s24a8UDBOiEPOFC7IbUjRAClphK54m1sgE6Ue/I=; b=Z04Xj9hgnNGOqcx+P4oA8t1Lg1+09nxEQWbWbMErnK4bPn/sunmrjKqSgpFK/YMgpw wy7JqqFMvAxKXycQOUNyOol3cy/ES6HV/vviykbHvZiH0Wcu03SqF52D4He4Y8af/M03 uHPacrdh614RuF3VJjuAvtafI0KSNcBxfDZf0=
Received: by 10.42.151.196 with SMTP id f4mr17030421icw.17.1320425786087; Fri, 04 Nov 2011 09:56:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.179.70 with HTTP; Fri, 4 Nov 2011 09:56:05 -0700 (PDT)
In-Reply-To: <117602CF2B17DB4F9001427FA6D90539B48E80@XMB-RCD-312.cisco.com>
References: <016101cc7f6c$9795e380$c6c1aa80$%roni@huawei.com> <117602CF2B17DB4F9001427FA6D9053996F6FF@XMB-RCD-312.cisco.com> <4E9EE184.4090606@ericsson.com> <117602CF2B17DB4F9001427FA6D90539B48E80@XMB-RCD-312.cisco.com>
From: "Piers O'Hanlon" <p.ohanlon@gmail.com>
Date: Fri, 4 Nov 2011 16:56:05 +0000
Message-ID: <CAFWWCs4nvZumj5T4gbShjZNEK3GOyA2+joBMmkLz7x5MUkGQaw@mail.gmail.com>
To: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, avt@ietf.org
Subject: Re: [AVTCORE] WGLC on draft-ietf-avtcore-ecn-for-rtp-04
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 04 Nov 2011 16:56:27 -0000

Hi Bill,

On 4 November 2011 15:29, Bill Ver Steeg (versteb) <versteb@cisco.com> wrot=
e:
> Magnus-
>
> I am still thinking about the problems identified with receivers that hav=
e varying levels of capabilities reading the ECN related markings.
>
> In my mind, there are 3 categories of devices - "ECN compliant" (follows =
the specification), "ECN blind (can't read/write the ECN markings, but does=
 not otherwise mangle the stream)", and "ECN incapable"(barfs on the stream=
).
>
> The analysis in the draft is spot-on for unicast flows.
>
> For RTP multicast streams, it is pretty clear how to handle ECN-compliant=
 and ECN-incapable devices. There are a few flavors of ECN-blind, and I am =
still getting educated - so I may be missing some subtlety here, but...... =
It seems that allowing an ECN blind receiver to join an ECN-enabled multica=
st stream is fairly innocuous, and will not provide an advantage to that re=
ceiver over other receivers of the same flow. If the path allows the device=
 to receive the probe packet, the discovery method works. The RTCP feedback=
 will be received from all of the devices, and the data can be analyzed by =
the sender. Some of the feedback reports will have the ECN information, and=
 some not.
>
I guess one of the issues is that if misbehaving middlebox is on the
path an ECN marked flow may not be able to traverse it fully or at
all. It is also dependent on what type congestion control is in use -
if receiver driven control is in use then those receivers that are
ECN-blind would potentially enjoy higher rate flow potentially at the
expense of ECN-compliant nodes.

> The alternative is to instantiate another flow that is not ECN marked. If=
 we apply the same fairness test to these two flows, it is not clear that w=
e have made an improvement. If we look at the BW consumption, it is clear t=
hat we have made congestion worse rather than better. In fact, we have doub=
led the BW. It seems to me that if we are trying to control congestion, a s=
ingle flow is (almost always) better than two flows. This is particularly t=
rue of IPTV-style deployments.
>
Sure this is not optimal.

> These thoughts are not rock-solid, and I would like to understand the pro=
blem space a bit better.
>
> So, can somebody enlighten me on the following
>
> 1- What Berkeley Sockets extension is used to read the ECN-related bits?
> 2- What hosts in the wild are running operating systems that do not suppo=
rt a variant of these extensions?
>
On Linux, BSD and OSX one can use IP_TOS socket option, with the
setsockopt() call, to set the relevant ECN bits (as the root user on
Linux). On Windows XP one can use the same technique though firstly
one has to enable TOS byte setting by enabling a particular Registry
key ( DisableUserTOSSetting=3D0 (see
http://support.microsoft.com/kb/248611)}, but this no longer works
beyond Windows XP as they disabled this functionality so raw sockets
are the only option (which I understand are also problematic on later
versions of Windows). One could also probably use the libpcap write
functionality.

To obtain the ECN bits from a packet on Linux, one needs to firstly
set the IP_RECVTOS socket option on the receiving socket, and use the
recvmsg() call to receive a packet, and then retrieve the TOS byte
from the associated csmg structure returned by the recvmsg() call.
Whilst on Windows the only way to retrieve the ECN bits is via a raw
socket, or custom NDIS driver. On OSX/BSD there are no suitable socket
options and one cannot use raw sockets as they do not function for
UDP/TCP sockets (they do work with ICMP), so one has to use
alternatives such the bpf interface, or a REDIRECT socket.

It seems odd that OS manufacturers have ended up providing this
asymmetry in functionality...

Piers

> bvs
>
>
> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> Sent: Wednesday, October 19, 2011 10:41 AM
> To: Bill Ver Steeg (versteb)
> Cc: Roni Even; avt@ietf.org
> Subject: Re: [AVTCORE] WGLC on draft-ietf-avtcore-ecn-for-rtp-04
>
> Bill,
>
> Thanks for the review. I here respond to the major issues. If needed I
> will follow up on the minor issues, otherwise I will simply implement
> them in the next update.
>
> On 2011-10-12 14:57, Bill Ver Steeg (versteb) wrote:
>>
>> For the multicast case, we need to make it clear that feedback goes to
>> the feedback target, which may be a different device than the source.
>> This document consistently says "feedback goes to the source", which is
>> misleading. See the detailed comments below for the places in which I
>> found it to be most concerning. When viewed in the context of feedback
>> going to a discrete feedback target at the network egress edge (like
>> typical IPTV deployments), it makes sense for the feedback target to use
>> these reports as diagnostic in nature. Perhaps the network has changed
>> topology and caused a bottleneck link to appear, and the feedback is
>> triggering action in the network to fix the congestion in a systematic
>> manner. It is highly unlikely that RTCP feedback will be able to change
>> the rate of a flow in such a system. It is more likely that the system
>> would take other actions, but that is probably beyond the scope of this
>> document.
>
> I think we might not have been sufficient clear on the SSM case. But in
> fact for this to work, the Feedback Targets will need to relay the
> feedback, at least in aggregated form to the source (or at least the
> entity marking the packets as ECN which might be the Distributuion
> Source).
>
>>
>>
>>
>> If a host is unable to read the ECN bits, it can't join an ECN-enabled
>> flow? This seems to be quite onerous, and will likely slow down the
>> adoption of ECN for RTP - particularly in the IPTV multicast case. If an
>> operator needs to dual carry hundreds of video channels (one ECN marked
>> and one not ECN marked), he will simply not implement ECN. I need to
>> think about this a bit more and see if there is a way to make this work.
>> My first instinct was to add a field/bit pattern to the RTCP feedback
>> that says " I joined the ECN enabled flow, but can't actually read the
>> ECT/ECN markings". However, let's think about na=EFve receivers that do
>> not understand the ECN SDP. They will ignore that SDP line, and join the
>> flow. They will provide their normal feedback, without the ECT/ECN
>> portions. How is this different from a receiver that knows about ECN,
>> but is unable to actually read the ECN bits? Maybe we just treat it like
>> a legacy receiver that does not know about the ECN SDP....... So, we
>> need to think about three receiver populations - fully ECN capable (as
>> currently described in this document), ECN aware in the application but
>> unable to read ECN bits (either acts like a legacy receiver or sends a
>> special RTCP feedback message), ECN unaware (ignores the SDP). I have
>> thought about this in the context of the declarative SDP case using leap
>> of faith, but need to think more about the offer/answer case and the
>> STUN case. We need a way to have each type of receiver unambiguously
>> join the same multicast flow. This would allow an operator to
>> incrementally deploy ECN on multicast flows. If we do not fix this, the
>> operator will be gated on the very last device in his deployment.
>>
>
> Lets start with commenting on the naive receivers, if they join an ECN
> enabled RTP session they will cause the session to stop using ECN. That
> is why we say the same to a receiver that knows about ECN but can't read
> the session. If they join they will force the session into not-ECT
> operations.
>
> Yes, this is onerous. But we can't frankly figure out how we can allow
> any other behavior in any best-effort network. Having receivers get
> preferential treatment of their traffic compared to not-ECT marked in a
> best effort seems problematic if they aren't reporting back on it and
> telling the sender to adjust the bit-rate.
>
> We know from that start that ECN and large scale multicast would be
> problematic and that is not our main target. This as it will be
> difficult to combine source rate modifications with large groups.
>
> I think we authors are still of the opinion that we develop what is safe
> but possibly overly conservative and get that published. If people want
> to improve the ECN in multicast usage later they are free to do so. But
> tackling the issues that arise from letting non ECN capable receivers
> into a group that uses ECN is problematic. So my opinion is that we
> shouldn't change anything in this behavior.
>
>>
>> It would be nice to have the RTCWEB folks take a courtesy look, as they
>> are envisioning some very interesting use cases. I do not think that
>> this presents any specific challenges, but it would be good to have
>> those eyeballs. I see that at least a few of them have provided comments=
.........
>>
>
> Which RTCWEB folks do you want to have a look at this?
>
> My personal view that I would love to have overturned is that ECN in
> open Internet is so dysfunctional that it is barely worth trying. Thus
> adding ECN support to RTCWEB nodes in the initial phase is lots of work
> for the implementor with very little bang back.
>
>>
>> A few minor points and a bit more specificity on the major
>> points------------
>>
>>
>>
>> There is a delicate balancing act between providing timely congestion
>> notifications to the sender and sending feedback packets into a
>> congested network. It is not clear that the this balancing act is
>> discussed in enough detail in the document. An inexperienced implementer
>> may "do the wrong thing" and send packets to freely, thus making the
>> congestion worse. Perhaps a short paragraph in the introduction would
>> make this clear? Perhaps a paragraph at the end of Page 11? Also in
>> section 7.3.2, as congestion is not highly featured in RFC4585 or
>> RFC3550. Congestion is mentioned in 7.3.2, as is feedback implosion, but
>> there is no warning about how they can interact.
>
> I think we can add more warnings and check that we are clear on that one
> must follow the transmission rules for the session the end-point is
> operating. I would note that congestion is in fact likely asymmetric.
> Thus just because you receive CE marked packets doesn't mean that the
> RTCP FB packets will go over path that is loaded into congestion and of
> course the reverse.
>
> Cheers
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| Phone =A0+46 10 7148287
> F=E4r=F6gatan 6 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>

From versteb@cisco.com  Fri Nov  4 10:45:00 2011
Return-Path: <versteb@cisco.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ABAC21F8B7B for <avt@ietfa.amsl.com>; Fri,  4 Nov 2011 10:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.526
X-Spam-Level: 
X-Spam-Status: No, score=-3.526 tagged_above=-999 required=5 tests=[AWL=-0.915, BAYES_00=-2.599, FRT_STOCK2=3.988, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 50dZQwd3n2RK for <avt@ietfa.amsl.com>; Fri,  4 Nov 2011 10:44:58 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id A500821F8B7A for <avt@ietf.org>; Fri,  4 Nov 2011 10:44:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=versteb@cisco.com; l=12842; q=dns/txt; s=iport; t=1320428698; x=1321638298; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=wVxvGSkmKCtb1znCvNIP5kBDgxFeTFGC9RrwciAsszo=; b=BfF9X8+QVvrUwoU4ajLlxYIZOs6zBqMU5ftkU9Cb/AIk9zzU0nyiT1DR v+WfYJ0EOzx8wOMKPCxqHMJ68nNJ6/GlhwOSSfzJj2Din/VEJa5TzRmdM aztjVrOsMegFjlb133Q98B5irkm4KmVHaysoP8buvZjVW5V7wR4jRAnyM s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsYAAFYktE6tJXHB/2dsb2JhbABEmhCOKCuBIIEFgXIBAQEDAQEBAQkGAR1JBQcCAgIBCBEEAQEBCgYXAQYBGgYGHwMBBQgBAQQTCBqHYAiXKAGeUwKIRmMEh1kxkUyFAodI
X-IronPort-AV: E=Sophos;i="4.69,456,1315180800"; d="scan'208";a="33484123"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-7.cisco.com with ESMTP; 04 Nov 2011 17:44:58 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core2-6.cisco.com (8.14.3/8.14.3) with ESMTP id pA4Hivnl015660;  Fri, 4 Nov 2011 17:44:57 GMT
Received: from xmb-rcd-312.cisco.com ([72.163.63.27]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 4 Nov 2011 12:44:57 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 4 Nov 2011 12:44:56 -0500
Message-ID: <117602CF2B17DB4F9001427FA6D90539B48F0F@XMB-RCD-312.cisco.com>
In-Reply-To: <CAFWWCs4nvZumj5T4gbShjZNEK3GOyA2+joBMmkLz7x5MUkGQaw@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVTCORE] WGLC on draft-ietf-avtcore-ecn-for-rtp-04
Thread-Index: AcybErE8NSvjo37GTvKFbeqHQIYsPwABDFaQ
References: <016101cc7f6c$9795e380$c6c1aa80$%roni@huawei.com> <117602CF2B17DB4F9001427FA6D9053996F6FF@XMB-RCD-312.cisco.com> <4E9EE184.4090606@ericsson.com> <117602CF2B17DB4F9001427FA6D90539B48E80@XMB-RCD-312.cisco.com> <CAFWWCs4nvZumj5T4gbShjZNEK3GOyA2+joBMmkLz7x5MUkGQaw@mail.gmail.com>
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "Piers O'Hanlon" <p.ohanlon@gmail.com>
X-OriginalArrivalTime: 04 Nov 2011 17:44:57.0785 (UTC) FILETIME=[78123A90:01CC9B19]
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, avt@ietf.org
Subject: Re: [AVTCORE] WGLC on draft-ietf-avtcore-ecn-for-rtp-04
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 04 Nov 2011 17:45:00 -0000

Piers-

Thanks for the detailed note, particularly the details around Berkeley =
sockets. I am digesting the sockets information, and this response is =
regarding the ECN-blind portions of your note.=20

My concern is primarily about ECN-blind receivers. The topic of =
ECN-blind (or ECN-incapable) middleboxes is important, but orthogonal. =
If the middlebox is ECN-blind, the stream will get through. If it is =
ECN-incapable, it will not get through and the stream will fall back to =
a non-ECN stream. I think this is OK as stated in the draft.

So, on to the ECN-blind receiver case --- If an ECN-compliant receiver =
is sharing a given stream with an ECN-blind receiver, how can the =
ECN-blind receiver get a higher flow rate? If they are receiving =
different streams, one could make that case. But since they are =
receiving the same stream they are, by definition, receiving the same =
rate. In my mind, this is actually an argument for having them share the =
stream. The system gets feedback from all of the receivers. Some of the =
feedback has information about ECN and some does not.=20

bvs


-----Original Message-----
From: Piers O'Hanlon [mailto:p.ohanlon@gmail.com]=20
Sent: Friday, November 04, 2011 12:56 PM
To: Bill Ver Steeg (versteb)
Cc: Magnus Westerlund; avt@ietf.org
Subject: Re: [AVTCORE] WGLC on draft-ietf-avtcore-ecn-for-rtp-04

Hi Bill,

On 4 November 2011 15:29, Bill Ver Steeg (versteb) <versteb@cisco.com> =
wrote:
> Magnus-
>
> I am still thinking about the problems identified with receivers that =
have varying levels of capabilities reading the ECN related markings.
>
> In my mind, there are 3 categories of devices - "ECN compliant" =
(follows the specification), "ECN blind (can't read/write the ECN =
markings, but does not otherwise mangle the stream)", and "ECN =
incapable"(barfs on the stream).
>
> The analysis in the draft is spot-on for unicast flows.
>
> For RTP multicast streams, it is pretty clear how to handle =
ECN-compliant and ECN-incapable devices. There are a few flavors of =
ECN-blind, and I am still getting educated - so I may be missing some =
subtlety here, but...... It seems that allowing an ECN blind receiver to =
join an ECN-enabled multicast stream is fairly innocuous, and will not =
provide an advantage to that receiver over other receivers of the same =
flow. If the path allows the device to receive the probe packet, the =
discovery method works. The RTCP feedback will be received from all of =
the devices, and the data can be analyzed by the sender. Some of the =
feedback reports will have the ECN information, and some not.
>
I guess one of the issues is that if misbehaving middlebox is on the
path an ECN marked flow may not be able to traverse it fully or at
all. It is also dependent on what type congestion control is in use -
if receiver driven control is in use then those receivers that are
ECN-blind would potentially enjoy higher rate flow potentially at the
expense of ECN-compliant nodes.

> The alternative is to instantiate another flow that is not ECN marked. =
If we apply the same fairness test to these two flows, it is not clear =
that we have made an improvement. If we look at the BW consumption, it =
is clear that we have made congestion worse rather than better. In fact, =
we have doubled the BW. It seems to me that if we are trying to control =
congestion, a single flow is (almost always) better than two flows. This =
is particularly true of IPTV-style deployments.
>
Sure this is not optimal.

> These thoughts are not rock-solid, and I would like to understand the =
problem space a bit better.
>
> So, can somebody enlighten me on the following
>
> 1- What Berkeley Sockets extension is used to read the ECN-related =
bits?
> 2- What hosts in the wild are running operating systems that do not =
support a variant of these extensions?
>
On Linux, BSD and OSX one can use IP_TOS socket option, with the
setsockopt() call, to set the relevant ECN bits (as the root user on
Linux). On Windows XP one can use the same technique though firstly
one has to enable TOS byte setting by enabling a particular Registry
key ( DisableUserTOSSetting=3D0 (see
http://support.microsoft.com/kb/248611)}, but this no longer works
beyond Windows XP as they disabled this functionality so raw sockets
are the only option (which I understand are also problematic on later
versions of Windows). One could also probably use the libpcap write
functionality.

To obtain the ECN bits from a packet on Linux, one needs to firstly
set the IP_RECVTOS socket option on the receiving socket, and use the
recvmsg() call to receive a packet, and then retrieve the TOS byte
from the associated csmg structure returned by the recvmsg() call.
Whilst on Windows the only way to retrieve the ECN bits is via a raw
socket, or custom NDIS driver. On OSX/BSD there are no suitable socket
options and one cannot use raw sockets as they do not function for
UDP/TCP sockets (they do work with ICMP), so one has to use
alternatives such the bpf interface, or a REDIRECT socket.

It seems odd that OS manufacturers have ended up providing this
asymmetry in functionality...

Piers

> bvs
>
>
> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> Sent: Wednesday, October 19, 2011 10:41 AM
> To: Bill Ver Steeg (versteb)
> Cc: Roni Even; avt@ietf.org
> Subject: Re: [AVTCORE] WGLC on draft-ietf-avtcore-ecn-for-rtp-04
>
> Bill,
>
> Thanks for the review. I here respond to the major issues. If needed I
> will follow up on the minor issues, otherwise I will simply implement
> them in the next update.
>
> On 2011-10-12 14:57, Bill Ver Steeg (versteb) wrote:
>>
>> For the multicast case, we need to make it clear that feedback goes =
to
>> the feedback target, which may be a different device than the source.
>> This document consistently says "feedback goes to the source", which =
is
>> misleading. See the detailed comments below for the places in which I
>> found it to be most concerning. When viewed in the context of =
feedback
>> going to a discrete feedback target at the network egress edge (like
>> typical IPTV deployments), it makes sense for the feedback target to =
use
>> these reports as diagnostic in nature. Perhaps the network has =
changed
>> topology and caused a bottleneck link to appear, and the feedback is
>> triggering action in the network to fix the congestion in a =
systematic
>> manner. It is highly unlikely that RTCP feedback will be able to =
change
>> the rate of a flow in such a system. It is more likely that the =
system
>> would take other actions, but that is probably beyond the scope of =
this
>> document.
>
> I think we might not have been sufficient clear on the SSM case. But =
in
> fact for this to work, the Feedback Targets will need to relay the
> feedback, at least in aggregated form to the source (or at least the
> entity marking the packets as ECN which might be the Distributuion
> Source).
>
>>
>>
>>
>> If a host is unable to read the ECN bits, it can't join an =
ECN-enabled
>> flow? This seems to be quite onerous, and will likely slow down the
>> adoption of ECN for RTP - particularly in the IPTV multicast case. If =
an
>> operator needs to dual carry hundreds of video channels (one ECN =
marked
>> and one not ECN marked), he will simply not implement ECN. I need to
>> think about this a bit more and see if there is a way to make this =
work.
>> My first instinct was to add a field/bit pattern to the RTCP feedback
>> that says " I joined the ECN enabled flow, but can't actually read =
the
>> ECT/ECN markings". However, let's think about na=EFve receivers that =
do
>> not understand the ECN SDP. They will ignore that SDP line, and join =
the
>> flow. They will provide their normal feedback, without the ECT/ECN
>> portions. How is this different from a receiver that knows about ECN,
>> but is unable to actually read the ECN bits? Maybe we just treat it =
like
>> a legacy receiver that does not know about the ECN SDP....... So, we
>> need to think about three receiver populations - fully ECN capable =
(as
>> currently described in this document), ECN aware in the application =
but
>> unable to read ECN bits (either acts like a legacy receiver or sends =
a
>> special RTCP feedback message), ECN unaware (ignores the SDP). I have
>> thought about this in the context of the declarative SDP case using =
leap
>> of faith, but need to think more about the offer/answer case and the
>> STUN case. We need a way to have each type of receiver unambiguously
>> join the same multicast flow. This would allow an operator to
>> incrementally deploy ECN on multicast flows. If we do not fix this, =
the
>> operator will be gated on the very last device in his deployment.
>>
>
> Lets start with commenting on the naive receivers, if they join an ECN
> enabled RTP session they will cause the session to stop using ECN. =
That
> is why we say the same to a receiver that knows about ECN but can't =
read
> the session. If they join they will force the session into not-ECT
> operations.
>
> Yes, this is onerous. But we can't frankly figure out how we can allow
> any other behavior in any best-effort network. Having receivers get
> preferential treatment of their traffic compared to not-ECT marked in =
a
> best effort seems problematic if they aren't reporting back on it and
> telling the sender to adjust the bit-rate.
>
> We know from that start that ECN and large scale multicast would be
> problematic and that is not our main target. This as it will be
> difficult to combine source rate modifications with large groups.
>
> I think we authors are still of the opinion that we develop what is =
safe
> but possibly overly conservative and get that published. If people =
want
> to improve the ECN in multicast usage later they are free to do so. =
But
> tackling the issues that arise from letting non ECN capable receivers
> into a group that uses ECN is problematic. So my opinion is that we
> shouldn't change anything in this behavior.
>
>>
>> It would be nice to have the RTCWEB folks take a courtesy look, as =
they
>> are envisioning some very interesting use cases. I do not think that
>> this presents any specific challenges, but it would be good to have
>> those eyeballs. I see that at least a few of them have provided =
comments.........
>>
>
> Which RTCWEB folks do you want to have a look at this?
>
> My personal view that I would love to have overturned is that ECN in
> open Internet is so dysfunctional that it is barely worth trying. Thus
> adding ECN support to RTCWEB nodes in the initial phase is lots of =
work
> for the implementor with very little bang back.
>
>>
>> A few minor points and a bit more specificity on the major
>> points------------
>>
>>
>>
>> There is a delicate balancing act between providing timely congestion
>> notifications to the sender and sending feedback packets into a
>> congested network. It is not clear that the this balancing act is
>> discussed in enough detail in the document. An inexperienced =
implementer
>> may "do the wrong thing" and send packets to freely, thus making the
>> congestion worse. Perhaps a short paragraph in the introduction would
>> make this clear? Perhaps a paragraph at the end of Page 11? Also in
>> section 7.3.2, as congestion is not highly featured in RFC4585 or
>> RFC3550. Congestion is mentioned in 7.3.2, as is feedback implosion, =
but
>> there is no warning about how they can interact.
>
> I think we can add more warnings and check that we are clear on that =
one
> must follow the transmission rules for the session the end-point is
> operating. I would note that congestion is in fact likely asymmetric.
> Thus just because you receive CE marked packets doesn't mean that the
> RTCP FB packets will go over path that is loaded into congestion and =
of
> course the reverse.
>
> Cheers
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| Phone =A0+46 10 7148287
> F=E4r=F6gatan 6 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>

From p.ohanlon@gmail.com  Fri Nov  4 11:27:57 2011
Return-Path: <p.ohanlon@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05F3B21F8B50 for <avt@ietfa.amsl.com>; Fri,  4 Nov 2011 11:27:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[AWL=-0.746, BAYES_00=-2.599, FRT_STOCK2=3.988, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cj9vobyVG--X for <avt@ietfa.amsl.com>; Fri,  4 Nov 2011 11:27:55 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id A6F4C21F8B4E for <avt@ietf.org>; Fri,  4 Nov 2011 11:27:55 -0700 (PDT)
Received: by ywt2 with SMTP id 2so3186325ywt.31 for <avt@ietf.org>; Fri, 04 Nov 2011 11:27:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=4zUSOGQR5IUr+IGXKH+3Hi93UAgF5z479UfELCyUF9A=; b=GSnPv10DTSrbO52rpiHl4wpRUnXf1AqgWuKqlL4dqSOmQYGHOirHhb0pKzgX5wEAEz VIPxtrTJhM/W7UVP69AmCEqaWVzX+YMqQP+u8B8l3k0UNuwd9EiZaBToxa0eABEz8Zhz zPS3/kDEPMIIeXVJtZS0L/FgRS4diqH1ObeuQ=
Received: by 10.42.155.74 with SMTP id t10mr17401118icw.49.1320431275123; Fri, 04 Nov 2011 11:27:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.179.70 with HTTP; Fri, 4 Nov 2011 11:27:35 -0700 (PDT)
In-Reply-To: <117602CF2B17DB4F9001427FA6D90539B48F0F@XMB-RCD-312.cisco.com>
References: <016101cc7f6c$9795e380$c6c1aa80$%roni@huawei.com> <117602CF2B17DB4F9001427FA6D9053996F6FF@XMB-RCD-312.cisco.com> <4E9EE184.4090606@ericsson.com> <117602CF2B17DB4F9001427FA6D90539B48E80@XMB-RCD-312.cisco.com> <CAFWWCs4nvZumj5T4gbShjZNEK3GOyA2+joBMmkLz7x5MUkGQaw@mail.gmail.com> <117602CF2B17DB4F9001427FA6D90539B48F0F@XMB-RCD-312.cisco.com>
From: "Piers O'Hanlon" <p.ohanlon@gmail.com>
Date: Fri, 4 Nov 2011 18:27:35 +0000
Message-ID: <CAFWWCs6To=idVZ0hYB_30aacEUPC2qNx7q70q_5gNO38NuOeGw@mail.gmail.com>
To: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, avt@ietf.org
Subject: Re: [AVTCORE] WGLC on draft-ietf-avtcore-ecn-for-rtp-04
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 04 Nov 2011 18:27:57 -0000

Bill,

On 4 November 2011 17:44, Bill Ver Steeg (versteb) <versteb@cisco.com> wrot=
e:
> Piers-
>
> Thanks for the detailed note, particularly the details around Berkeley so=
ckets. I am digesting the sockets information, and this response is regardi=
ng the ECN-blind portions of your note.
>
> My concern is primarily about ECN-blind receivers. The topic of ECN-blind=
 (or ECN-incapable) middleboxes is important, but orthogonal. If the middle=
box is ECN-blind, the stream will get through. If it is ECN-incapable, it w=
ill not get through and the stream will fall back to a non-ECN stream. I th=
ink this is OK as stated in the draft.
>
Yes. Though the detection system in the draft does need to use
ECN-capable nodes to asses the situation. I guess in a 'managed
network' then one may be able to assume that things 'just work',
though there's still the small possibility of misconfiguration of
nodes resulting in the presence of ECN-incapable nodes.

> So, on to the ECN-blind receiver case --- If an ECN-compliant receiver is=
 sharing a given stream with an ECN-blind receiver, how can the ECN-blind r=
eceiver get a higher flow rate? If they are receiving different streams, on=
e could make that case. But since they are receiving the same stream they a=
re, by definition, receiving the same rate. In my mind, this is actually an=
 argument for having them share the stream. The system gets feedback from a=
ll of the receivers. Some of the feedback has information about ECN and som=
e does not.
>
I was thinking of the case where a congestion control algorithm counts
the number of ECN marks and the number of losses to calculate a total
loss rate. This would then potentially be utilised by the congestion
control algorithm to derive a suitable operating rate. With the
current prevalence of TCP like congestion control algorithms the rate
is proportional to one over the square root of the loss rate - so if
one omits to count the ECN marked packets the resulting rate would be
higher. So as you say in the case where everyone gets the same stream
there no problem, but if there's a layered transmission system or
variable subscription approach (multicast HTTP live streaming?) then
the ECN-blind receiver would end up requesting a higher rate stream
than an ECN-capable node.

Piers.

> bvs
>
>
> -----Original Message-----
> From: Piers O'Hanlon [mailto:p.ohanlon@gmail.com]
> Sent: Friday, November 04, 2011 12:56 PM
> To: Bill Ver Steeg (versteb)
> Cc: Magnus Westerlund; avt@ietf.org
> Subject: Re: [AVTCORE] WGLC on draft-ietf-avtcore-ecn-for-rtp-04
>
> Hi Bill,
>
> On 4 November 2011 15:29, Bill Ver Steeg (versteb) <versteb@cisco.com> wr=
ote:
>> Magnus-
>>
>> I am still thinking about the problems identified with receivers that ha=
ve varying levels of capabilities reading the ECN related markings.
>>
>> In my mind, there are 3 categories of devices - "ECN compliant" (follows=
 the specification), "ECN blind (can't read/write the ECN markings, but doe=
s not otherwise mangle the stream)", and "ECN incapable"(barfs on the strea=
m).
>>
>> The analysis in the draft is spot-on for unicast flows.
>>
>> For RTP multicast streams, it is pretty clear how to handle ECN-complian=
t and ECN-incapable devices. There are a few flavors of ECN-blind, and I am=
 still getting educated - so I may be missing some subtlety here, but......=
 It seems that allowing an ECN blind receiver to join an ECN-enabled multic=
ast stream is fairly innocuous, and will not provide an advantage to that r=
eceiver over other receivers of the same flow. If the path allows the devic=
e to receive the probe packet, the discovery method works. The RTCP feedbac=
k will be received from all of the devices, and the data can be analyzed by=
 the sender. Some of the feedback reports will have the ECN information, an=
d some not.
>>
> I guess one of the issues is that if misbehaving middlebox is on the
> path an ECN marked flow may not be able to traverse it fully or at
> all. It is also dependent on what type congestion control is in use -
> if receiver driven control is in use then those receivers that are
> ECN-blind would potentially enjoy higher rate flow potentially at the
> expense of ECN-compliant nodes.
>
>> The alternative is to instantiate another flow that is not ECN marked. I=
f we apply the same fairness test to these two flows, it is not clear that =
we have made an improvement. If we look at the BW consumption, it is clear =
that we have made congestion worse rather than better. In fact, we have dou=
bled the BW. It seems to me that if we are trying to control congestion, a =
single flow is (almost always) better than two flows. This is particularly =
true of IPTV-style deployments.
>>
> Sure this is not optimal.
>
>> These thoughts are not rock-solid, and I would like to understand the pr=
oblem space a bit better.
>>
>> So, can somebody enlighten me on the following
>>
>> 1- What Berkeley Sockets extension is used to read the ECN-related bits?
>> 2- What hosts in the wild are running operating systems that do not supp=
ort a variant of these extensions?
>>
> On Linux, BSD and OSX one can use IP_TOS socket option, with the
> setsockopt() call, to set the relevant ECN bits (as the root user on
> Linux). On Windows XP one can use the same technique though firstly
> one has to enable TOS byte setting by enabling a particular Registry
> key ( DisableUserTOSSetting=3D0 (see
> http://support.microsoft.com/kb/248611)}, but this no longer works
> beyond Windows XP as they disabled this functionality so raw sockets
> are the only option (which I understand are also problematic on later
> versions of Windows). One could also probably use the libpcap write
> functionality.
>
> To obtain the ECN bits from a packet on Linux, one needs to firstly
> set the IP_RECVTOS socket option on the receiving socket, and use the
> recvmsg() call to receive a packet, and then retrieve the TOS byte
> from the associated csmg structure returned by the recvmsg() call.
> Whilst on Windows the only way to retrieve the ECN bits is via a raw
> socket, or custom NDIS driver. On OSX/BSD there are no suitable socket
> options and one cannot use raw sockets as they do not function for
> UDP/TCP sockets (they do work with ICMP), so one has to use
> alternatives such the bpf interface, or a REDIRECT socket.
>
> It seems odd that OS manufacturers have ended up providing this
> asymmetry in functionality...
>
> Piers
>
>> bvs
>>
>>
>> -----Original Message-----
>> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
>> Sent: Wednesday, October 19, 2011 10:41 AM
>> To: Bill Ver Steeg (versteb)
>> Cc: Roni Even; avt@ietf.org
>> Subject: Re: [AVTCORE] WGLC on draft-ietf-avtcore-ecn-for-rtp-04
>>
>> Bill,
>>
>> Thanks for the review. I here respond to the major issues. If needed I
>> will follow up on the minor issues, otherwise I will simply implement
>> them in the next update.
>>
>> On 2011-10-12 14:57, Bill Ver Steeg (versteb) wrote:
>>>
>>> For the multicast case, we need to make it clear that feedback goes to
>>> the feedback target, which may be a different device than the source.
>>> This document consistently says "feedback goes to the source", which is
>>> misleading. See the detailed comments below for the places in which I
>>> found it to be most concerning. When viewed in the context of feedback
>>> going to a discrete feedback target at the network egress edge (like
>>> typical IPTV deployments), it makes sense for the feedback target to us=
e
>>> these reports as diagnostic in nature. Perhaps the network has changed
>>> topology and caused a bottleneck link to appear, and the feedback is
>>> triggering action in the network to fix the congestion in a systematic
>>> manner. It is highly unlikely that RTCP feedback will be able to change
>>> the rate of a flow in such a system. It is more likely that the system
>>> would take other actions, but that is probably beyond the scope of this
>>> document.
>>
>> I think we might not have been sufficient clear on the SSM case. But in
>> fact for this to work, the Feedback Targets will need to relay the
>> feedback, at least in aggregated form to the source (or at least the
>> entity marking the packets as ECN which might be the Distributuion
>> Source).
>>
>>>
>>>
>>>
>>> If a host is unable to read the ECN bits, it can't join an ECN-enabled
>>> flow? This seems to be quite onerous, and will likely slow down the
>>> adoption of ECN for RTP - particularly in the IPTV multicast case. If a=
n
>>> operator needs to dual carry hundreds of video channels (one ECN marked
>>> and one not ECN marked), he will simply not implement ECN. I need to
>>> think about this a bit more and see if there is a way to make this work=
.
>>> My first instinct was to add a field/bit pattern to the RTCP feedback
>>> that says " I joined the ECN enabled flow, but can't actually read the
>>> ECT/ECN markings". However, let's think about na=EFve receivers that do
>>> not understand the ECN SDP. They will ignore that SDP line, and join th=
e
>>> flow. They will provide their normal feedback, without the ECT/ECN
>>> portions. How is this different from a receiver that knows about ECN,
>>> but is unable to actually read the ECN bits? Maybe we just treat it lik=
e
>>> a legacy receiver that does not know about the ECN SDP....... So, we
>>> need to think about three receiver populations - fully ECN capable (as
>>> currently described in this document), ECN aware in the application but
>>> unable to read ECN bits (either acts like a legacy receiver or sends a
>>> special RTCP feedback message), ECN unaware (ignores the SDP). I have
>>> thought about this in the context of the declarative SDP case using lea=
p
>>> of faith, but need to think more about the offer/answer case and the
>>> STUN case. We need a way to have each type of receiver unambiguously
>>> join the same multicast flow. This would allow an operator to
>>> incrementally deploy ECN on multicast flows. If we do not fix this, the
>>> operator will be gated on the very last device in his deployment.
>>>
>>
>> Lets start with commenting on the naive receivers, if they join an ECN
>> enabled RTP session they will cause the session to stop using ECN. That
>> is why we say the same to a receiver that knows about ECN but can't read
>> the session. If they join they will force the session into not-ECT
>> operations.
>>
>> Yes, this is onerous. But we can't frankly figure out how we can allow
>> any other behavior in any best-effort network. Having receivers get
>> preferential treatment of their traffic compared to not-ECT marked in a
>> best effort seems problematic if they aren't reporting back on it and
>> telling the sender to adjust the bit-rate.
>>
>> We know from that start that ECN and large scale multicast would be
>> problematic and that is not our main target. This as it will be
>> difficult to combine source rate modifications with large groups.
>>
>> I think we authors are still of the opinion that we develop what is safe
>> but possibly overly conservative and get that published. If people want
>> to improve the ECN in multicast usage later they are free to do so. But
>> tackling the issues that arise from letting non ECN capable receivers
>> into a group that uses ECN is problematic. So my opinion is that we
>> shouldn't change anything in this behavior.
>>
>>>
>>> It would be nice to have the RTCWEB folks take a courtesy look, as they
>>> are envisioning some very interesting use cases. I do not think that
>>> this presents any specific challenges, but it would be good to have
>>> those eyeballs. I see that at least a few of them have provided comment=
s.........
>>>
>>
>> Which RTCWEB folks do you want to have a look at this?
>>
>> My personal view that I would love to have overturned is that ECN in
>> open Internet is so dysfunctional that it is barely worth trying. Thus
>> adding ECN support to RTCWEB nodes in the initial phase is lots of work
>> for the implementor with very little bang back.
>>
>>>
>>> A few minor points and a bit more specificity on the major
>>> points------------
>>>
>>>
>>>
>>> There is a delicate balancing act between providing timely congestion
>>> notifications to the sender and sending feedback packets into a
>>> congested network. It is not clear that the this balancing act is
>>> discussed in enough detail in the document. An inexperienced implemente=
r
>>> may "do the wrong thing" and send packets to freely, thus making the
>>> congestion worse. Perhaps a short paragraph in the introduction would
>>> make this clear? Perhaps a paragraph at the end of Page 11? Also in
>>> section 7.3.2, as congestion is not highly featured in RFC4585 or
>>> RFC3550. Congestion is mentioned in 7.3.2, as is feedback implosion, bu=
t
>>> there is no warning about how they can interact.
>>
>> I think we can add more warnings and check that we are clear on that one
>> must follow the transmission rules for the session the end-point is
>> operating. I would note that congestion is in fact likely asymmetric.
>> Thus just because you receive CE marked packets doesn't mean that the
>> RTCP FB packets will go over path that is loaded into congestion and of
>> course the reverse.
>>
>> Cheers
>>
>> Magnus Westerlund
>>
>> ----------------------------------------------------------------------
>> Multimedia Technologies, Ericsson Research EAB/TVM
>> ----------------------------------------------------------------------
>> Ericsson AB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| Phone =A0+46 10 7148287
>> F=E4r=F6gatan 6 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| Mobile +46 73 0949079
>> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
>> ----------------------------------------------------------------------
>>
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>>
>

From eckelcu@cisco.com  Fri Nov  4 15:30:24 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 720AB21F8564 for <avt@ietfa.amsl.com>; Fri,  4 Nov 2011 15:30:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.343
X-Spam-Level: 
X-Spam-Status: No, score=-6.343 tagged_above=-999 required=5 tests=[AWL=0.256,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NEY03Wcsx1R5 for <avt@ietfa.amsl.com>; Fri,  4 Nov 2011 15:30:23 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id C11DB21F853E for <avt@ietf.org>; Fri,  4 Nov 2011 15:30:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=1770; q=dns/txt; s=iport; t=1320445823; x=1321655423; h=mime-version:content-transfer-encoding:subject:date: message-id:from:to; bh=EGpDczdF/yfYsi2PPPAvnNEc6f+X1BT0h1QJx8tfVmA=; b=lJCyqohbaqQgfZL8cuR+ZQPXq/oPAH6LtKL+ij6UztDt4HlOeiL4bHxc Al7+TU+vqQXO9yuw0NM0cec/TXzhAc0DQRBKPoEsrbdIYMOef88y5lQUE jsCJvcVAGWsCRqFL1OOiwNst6f6G0Qvk2cMvLwhkuSZPCESKXepidu0VF g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiAHADtntE6rRDoI/2dsb2JhbABDmlePL4EFgXQBBBIBHQpRASoGGAdXAQQbGp4IgSYBnkWISGMEiAqRTIxM
X-IronPort-AV: E=Sophos;i="4.69,457,1315180800"; d="scan'208";a="12455115"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 04 Nov 2011 22:30:22 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pA4MUMVS009886 for <avt@ietf.org>; Fri, 4 Nov 2011 22:30:22 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 4 Nov 2011 15:30:22 -0700
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, 4 Nov 2011 15:30:21 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05B4B569@xmb-sjc-234.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: comments on draft-ietf-avtcore-monarch-05
Thread-Index: AcybQVaCnLsGTyLqRoalcf65qUAjqg==
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 04 Nov 2011 22:30:22.0931 (UTC) FILETIME=[57742230:01CC9B41]
Subject: [AVTCORE] comments on draft-ietf-avtcore-monarch-05
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 04 Nov 2011 22:30:24 -0000

I read the draft and have the following comments:

Section 2 and 3 contain some definitions. Should we add definitions
there for additional terms, including interval metric, cumulative
metric, and sampled metric. There has been some debate on the
definitions of these on xrblock alias, and it would be good to have a
consistent definition of these terms.

Section 3 reads, " The Metric Block exposes real time Application
Quality information". Section 2 defined transport level, application
level, and end system metrics. As such, the use of "application quality
information" seems too specific and limiting to me.

Section 5.2 read, There may be situation where more than one media
transport protocols are used by one application to interconnect to the
same session in the gateway.  For example, one RTCP XR Packet is sent to
the participating endpoints using non- RTP-based media transport (e.g.,
using SIP) in a VOIP session, one crucial factor lies in how to handle
their different identities that are corresponding to different media
transport."
Are we really expecting RTCP XR packets to be used outside of an RTP
session? Or are we trying to say there may be multiple RTP sessions for
a given VoIP session, and there is a need to be able to correlate the
RTCP XR packets from each of these RTP sessions with each other?

Nits:

Section 4:
- change " may have different monitoring requirements, design large
block ..." to " may have different monitoring requirements. Designing
large block ..."
- change " it is hardly to provide" to " it is hard to provide"
- change " block types For example" to " block types.  For example"
- change " consecutive metric interval" to " consecutive metric
intervals"

Thanks,
Charles

=20


From bill.wu@huawei.com  Sun Nov  6 22:21:31 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1595A21F848B for <avt@ietfa.amsl.com>; Sun,  6 Nov 2011 22:21:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.246
X-Spam-Level: 
X-Spam-Status: No, score=-5.246 tagged_above=-999 required=5 tests=[AWL=1.353,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z2Qc9FdhJGVM for <avt@ietfa.amsl.com>; Sun,  6 Nov 2011 22:21:30 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 1608921F8484 for <avt@ietf.org>; Sun,  6 Nov 2011 22:21:30 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUA00KU01NHM6@szxga04-in.huawei.com> for avt@ietf.org; Mon, 07 Nov 2011 14:21:17 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUA00K8K1ME5W@szxga04-in.huawei.com> for avt@ietf.org; Mon, 07 Nov 2011 14:21:17 +0800 (CST)
Received: from szxeml201-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEU34956; Mon, 07 Nov 2011 14:20:58 +0800
Received: from SZXEML405-HUB.china.huawei.com (10.82.67.60) by szxeml201-edg.china.huawei.com (172.24.2.39) with Microsoft SMTP Server (TLS) id 14.1.270.1; Mon, 07 Nov 2011 14:20:55 +0800
Received: from w53375q (10.138.41.130) by szxeml405-hub.china.huawei.com (10.82.67.60) with Microsoft SMTP Server (TLS) id 14.1.270.1; Mon, 07 Nov 2011 14:20:48 +0800
Date: Mon, 07 Nov 2011 14:20:47 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, avt@ietf.org
Message-id: <C7E873DD2F574ACCA02F6CCABE05B4E5@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05B4B569@xmb-sjc-234.amer.cisco.com>
Subject: Re: [AVTCORE] comments on draft-ietf-avtcore-monarch-05
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 07 Nov 2011 06:21:31 -0000

Hi, Charles:
Thank for your valuable comments, please see my reply below.

Regards!
-Qin
----- Original Message ----- 
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: <avt@ietf.org>
Sent: Saturday, November 05, 2011 6:30 AM
Subject: [AVTCORE] comments on draft-ietf-avtcore-monarch-05


>I read the draft and have the following comments:
> 
> Section 2 and 3 contain some definitions. Should we add definitions
> there for additional terms, including interval metric, cumulative
> metric, and sampled metric. There has been some debate on the
> definitions of these on xrblock alias, and it would be good to have a
> consistent definition of these terms.

[Qin]: Fair, will add them into the update.

> Section 3 reads, " The Metric Block exposes real time Application
> Quality information". Section 2 defined transport level, application
> level, and end system metrics. As such, the use of "application quality
> information" seems too specific and limiting to me.

[Qin]: Correct, how about change as "QoS/QoE metric information".

> 
> Section 5.2 read, There may be situation where more than one media
> transport protocols are used by one application to interconnect to the
> same session in the gateway.  For example, one RTCP XR Packet is sent to
> the participating endpoints using non- RTP-based media transport (e.g.,
> using SIP) in a VOIP session, one crucial factor lies in how to handle
> their different identities that are corresponding to different media
> transport."
> Are we really expecting RTCP XR packets to be used outside of an RTP
> session? Or are we trying to say there may be multiple RTP sessions for
> a given VoIP session, and there is a need to be able to correlate the
> RTCP XR packets from each of these RTP sessions with each other?


[Qin]: Yes, this section focuses on describing correlation of RTP session with Non-RTP 
session for monitoring purpose. You may read RFC5104 for an example but not limited 
to this.

> Nits:
> 
> Section 4:
> - change " may have different monitoring requirements, design large
> block ..." to " may have different monitoring requirements. Designing
> large block ..."
> - change " it is hardly to provide" to " it is hard to provide"
> - change " block types For example" to " block types.  For example"
> - change " consecutive metric interval" to " consecutive metric
> intervals"

[Qin]: Fixed, thanks very much.

> 
> Thanks,
> Charles
> 
> 
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>

From magnus.westerlund@ericsson.com  Mon Nov  7 02:18:00 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CEC521F8AC9; Mon,  7 Nov 2011 02:18:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.967
X-Spam-Level: 
X-Spam-Status: No, score=-105.967 tagged_above=-999 required=5 tests=[AWL=-0.568, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, J_CHICKENPOX_28=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lFY-W1lHchme; Mon,  7 Nov 2011 02:17:59 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id C241E21F8AD1; Mon,  7 Nov 2011 02:17:58 -0800 (PST)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-c3-4eb7b055fe63
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 8F.0A.13753.550B7BE4; Mon,  7 Nov 2011 11:17:57 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.137.0; Mon, 7 Nov 2011 11:17:57 +0100
Message-ID: <4EB7B054.3000706@ericsson.com>
Date: Mon, 7 Nov 2011 11:17:56 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: "rtcweb@ietf.org" <rtcweb@ietf.org>, IETF AVTCore WG <avt@ietf.org>,  Jonathan Lennox <jonathan@vidyo.com>, Jonathan Rosenberg <jonathan.rosenberg@skype.net>
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Subject: [AVTCORE] Comments on draft-lennox-rtcweb-rtp-media-type-mux-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: IETF AVTCore WG <avt@ietf.org>
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 07 Nov 2011 10:18:00 -0000

Hi,

(as individual)

I have reviewed draft-lennox-rtcweb-rtp-media-type-mux-00 and have some
comments.

I think this document is most appropriately discussed in AVTCORE as it
concerns RTP details. Therefore both lists are cc:ed and reply-to set to
AVTCORE WG mailing list. So if you are on RTCWEB and would like to
follow this discussion, please follow the AVTCORE mailing list also
(avt@ietf.org).

1. I think the biggest issue with multiple media type in a single RTP
session isn't discussed. I think it is very important that this issue is
brought up as it has to do with the applicability of this solution.

To start the discussion on this issue I think a quote from section 4.3
of draft-westerlund-avtcore-transport-multiplexing-01 is appropriate:

   Many transition scenarios use an RTP translator as a gateway between
   a single RTP session containing multiple media types multiplexed
   together, and several separate RTP sessions each using a single media
   type.  In this scenario, it is possible that a legacy device that
   uses one RTP session for each media type will use the same SSRC in
   each session.  When translating these into a single RTP session, it
   will be necessary to rewrite one of the SSRCs, so that each stream
   has a unique SSRC.  This SSRC translation process is straight-forward
   for RTP packets, but is very complex for RTCP packets.  It also
   hinders innovation, since such a gateway will not be able to
   translate new RTCP extensions that it is unaware of, even if they are
   supported by devices on both sides of the gateway.

The issue is that in any case where you have a desire to mix end-points
supporting this and where some don't you create a situation where you
will either get malfunctioning translators or translators that likely
are a barrier for deploying new RTP/RTCP extensions.

Even in WebRTC contexts the case combing the single session and multiple
sessions are likely to occur. One case is media plane gateways to legacy
that will negotiate the multiplexing between the WebRTC end-point and
the gateway and then attempt to perform basic splitting to two RTP
sessions on the legacy side based on the payload formats. Another
scenario is the centralized conferences where the RTP mixer or
translator can negotiate individual behavior to each end-point. Thus one
might start out fine with all being single session compliant. Then
someone joins who is not and the result is that one is in a situation
that either requires renegotiation (including NAT traversal) for the
already connected end-points or to do a translator. I am certain that
translator is going to be the approach rather than interrupting the
ongoing media streams.

So yes this would not be an issue if everyone supported it. But it is
clear that the world will be one of incremental deployment. So I am
quite worried on the future impact using a single RTP session creates. I
think RTCWEB needs to seriously consider if this really is the right way
to go or if another solution would be better.

2. Section 7.2.9 of draft-westerlund-avtcore-multiplex-architecture-00
discusses a number of aspects of this type of multiplexing. I think the
document covers most in a reasonable fashion. The ones that seems to be
missing are;

A) the number space limitation of the PT field. The 128 values should
after all cover all the RTP payload configurations one like to use/offer
+ the RTCP payload type overlap due to RTP/RTCP multiplexing. So the
fact that the real limitations in RTP payload types are in fact that all
media types need to share in 96+ available payload type values rather
than 128 per each media type.

B) I think the bit-rate issues could be improved but it is present.

C) Decomposited end-points are missing. This is not a big issue, only a
down side with this that increases the bit-rate to the actual functional
end-points and require them to have handling of the multiple media
types. So this is a limitation if one attempt to use this in a
Telepresence scenario with dedicated hardware, not an issue in a browser
context.

3. Section 3:
   For sessions using the RTP/AVPF [RFC4585] and RTP/SAVPF [RFC5124]
   profiles, however, endpoints SHOULD set the minimum RTCP regular
   reporting interval trr-int to 5000 (5 seconds), unless they
   explicitly need it to be lower.  This minimizes the excessive RTCP
   bandwidth consumption, as well as aiding compatibility with AVP
   endpoints.  Since this value only affects regular RTCP reports, not
   RTCP feedback, this does not prevent AVPF feedback messages from
   being sent as needed.

When AVP compatibility is the goal, I think 5 seconds is mostly ok. The
regular RTCP suppression algorithm has a bit of strange behavior in
cases where the Td value becomes similar to the T_rr_interval. That as
the scheduled transmission time of an regular RTCP packet might close to
the randomized value of the T_rr_interval but still smaller, that can in
worst case result in that the AVPF RTCP sender sends RTCP some cases
with close 2*T_rr_interval but no more often than 0.5*T_rr_interval.
Thus the median of the distribution gets skewed towards higher value
than T_rr_interval. I will send a separate email about this as it
requires a bit of graphs and more in detail discussion.

4. Section 3.1:

"An endpoint MAY choose to send multiple sources' RTCP messages in a
   single compound RTCP packet (though such compound packets SHOULD NOT
   exceed the path MTU, if avoidable and if it is known)."

I think this recommendation is appropriate but I think should likely
become a general recommendation for RTCP. However, that clearly requires
some feedback if it will fail with some implementations. And if it does,
I think that signalling support may be necessary. If that is the case,
this optimization can't be used when working in the separate RTP session
mode in WEBRTC, thus causing a situation where WebRTC end-points needs
to have a run-time switch to control if this is used or not.

5. Section 3.1:
   Regular (non-
   feedback) RTCP compound packets MUST still begin with an SR or RR
   packet, but otherwise may contain RTCP packets in any order.
   Receivers MUST be prepared to receive such compound packets.

I think this needs to make clear that for each SSRC include, both SR/RR
and the corresponding SDES CNAME items MUST be included.

6. Section 3.1:
  "An endpoint SHOULD NOT send reception reports from one of its own
   sources about another one ("cross-reports")."

This topic should also likely be discussed if it should be a general
clarifications to RFC3550. That includes how one determines what is the
considered the same end-point and what implications it provides. Is it
based on all SSRCs with the same CNAME in an end-point SHOULD NOT send
report blocks from more than one?

I do note that all SSRC still needs to send an SR or an RR(possibly
empty) just to announce there presence in the RTP session.

7. Section 3.1:
Similarly, an endpoint sending multiple sources SHOULD NOT send
   reception reports about a remote source from more than one of its
   local sources.

The same comments as for 6) applies to this.

8. Section 4:
   The more difficult case is if an offerer cannot reply on its
   potential peers supporting any features beyond baseline RTP (i.e.,
   neither ICE nor multiplexing).

I don't think this becomes a real issue if one assumes the offer
following the signalling as defined by
https://datatracker.ietf.org/doc/draft-holmberg-mmusic-sdp-bundle-negotiation/

9. Section 5:

So we do now have two proposals on the table for how to signal this. One
in
https://datatracker.ietf.org/doc/draft-holmberg-mmusic-sdp-bundle-negotiation/
(BUNDLE) and one in this document (Lennox).

A comparison is quite interesting.

BUNDLE will have very straightforward back-wards compatibility as that
can happen in the single offer/answer exchange. However, there exist no
way of forcing the usage of BUNDLE.

Lennox requires a new Offer if the peer doesn't support this. In
addition it creates a SDP media type that isn't supposed to be used with
MIME. That is likely going to be an interesting to execute. It does
allow for mandating support and refusing to establish a session not
compliant. In addition it reduces the risk of confusion around payload
types as they are only listed on a single media description.

I personally prefer the BUNDLE approach.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From harald@alvestrand.no  Mon Nov  7 02:37:24 2011
Return-Path: <harald@alvestrand.no>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 193D421F8AD6 for <avt@ietfa.amsl.com>; Mon,  7 Nov 2011 02:37:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.266
X-Spam-Level: 
X-Spam-Status: No, score=-110.266 tagged_above=-999 required=5 tests=[AWL=-0.267, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BZb-XGGf+r47 for <avt@ietfa.amsl.com>; Mon,  7 Nov 2011 02:37:23 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 217C921F8ABC for <avt@ietf.org>; Mon,  7 Nov 2011 02:37:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 438B239E119; Mon,  7 Nov 2011 11:37:14 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F6jzYbBr+PjR; Mon,  7 Nov 2011 11:37:13 +0100 (CET)
Received: from hta-dell.lul.corp.google.com (62-20-124-50.customer.telia.com [62.20.124.50]) by eikenes.alvestrand.no (Postfix) with ESMTPS id D002B39E112; Mon,  7 Nov 2011 11:37:12 +0100 (CET)
Message-ID: <4EB7B4D8.5050003@alvestrand.no>
Date: Mon, 07 Nov 2011 11:37:12 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15
MIME-Version: 1.0
To: IETF AVTCore WG <avt@ietf.org>
References: <4EB7B054.3000706@ericsson.com>
In-Reply-To: <4EB7B054.3000706@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, Jonathan Rosenberg <jonathan.rosenberg@skype.net>, Jonathan Lennox <jonathan@vidyo.com>
Subject: Re: [AVTCORE] Comments on draft-lennox-rtcweb-rtp-media-type-mux-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 07 Nov 2011 10:37:24 -0000

(RTCWEB deleted from CC list, as per request)

On 11/07/2011 11:17 AM, Magnus Westerlund wrote:
> Hi,
>
> (as individual)
>
> I have reviewed draft-lennox-rtcweb-rtp-media-type-mux-00 and have some
> comments.
>
> I think this document is most appropriately discussed in AVTCORE as it
> concerns RTP details. Therefore both lists are cc:ed and reply-to set to
> AVTCORE WG mailing list. So if you are on RTCWEB and would like to
> follow this discussion, please follow the AVTCORE mailing list also
> (avt@ietf.org).
>
> 1. I think the biggest issue with multiple media type in a single RTP
> session isn't discussed. I think it is very important that this issue is
> brought up as it has to do with the applicability of this solution.
>
> To start the discussion on this issue I think a quote from section 4.3
> of draft-westerlund-avtcore-transport-multiplexing-01 is appropriate:
>
>     Many transition scenarios use an RTP translator as a gateway between
>     a single RTP session containing multiple media types multiplexed
>     together, and several separate RTP sessions each using a single media
>     type.  In this scenario, it is possible that a legacy device that
>     uses one RTP session for each media type will use the same SSRC in
>     each session.  When translating these into a single RTP session, it
>     will be necessary to rewrite one of the SSRCs, so that each stream
>     has a unique SSRC.  This SSRC translation process is straight-forward
>     for RTP packets, but is very complex for RTCP packets.  It also
>     hinders innovation, since such a gateway will not be able to
>     translate new RTCP extensions that it is unaware of, even if they are
>     supported by devices on both sides of the gateway.
>
> The issue is that in any case where you have a desire to mix end-points
> supporting this and where some don't you create a situation where you
> will either get malfunctioning translators or translators that likely
> are a barrier for deploying new RTP/RTCP extensions.
Magnus,

why would such a gateway want to offer the BUNDLE extension in its SDP 
negotiation?
(I'm assuming support for draft-holmberg-mmusic-sdp-bundle-negotiation 
as the way to negotiate multiple media types in a single session here.)

An assumption in the deployment of extensions is that one is able to 
negotiate their non-use where some participant does not support the 
feature. I find your arguments compelling if (and only if) I accept the 
premises that:

1) Gateways between RTCWEB deployments and non-RTCWEB deployments will 
want to relay RTP sessions rather than terminate them (something which I 
do not believe, but that's another debate)

2) Gateways between RTCWEB deployments and non-RTCWEB deployments can't 
negotiatiate non-support for the BUNDLE extension with the RTCWEB deployment

Given that I believe 2) is false, I don't agree with your conclusion.

Some details below.
> Even in WebRTC contexts the case combing the single session and multiple
> sessions are likely to occur. One case is media plane gateways to legacy
> that will negotiate the multiplexing between the WebRTC end-point and
> the gateway and then attempt to perform basic splitting to two RTP
> sessions on the legacy side based on the payload formats. Another
> scenario is the centralized conferences where the RTP mixer or
> translator can negotiate individual behavior to each end-point. Thus one
> might start out fine with all being single session compliant. Then
> someone joins who is not and the result is that one is in a situation
> that either requires renegotiation (including NAT traversal) for the
> already connected end-points or to do a translator. I am certain that
> translator is going to be the approach rather than interrupting the
> ongoing media streams.
The 3 viable approaches I see for gateways are:

- The gateway refuses to negotiate BUNDLE with anyone
- The gateway terminates RTP sessions
- The gateway refuses to establish non-BUNDLE sessions at all

In neither of these 3 scenarios do I see the issue you posit.


From Even.roni@huawei.com  Mon Nov  7 08:45:10 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E4E521F8C41 for <avt@ietfa.amsl.com>; Mon,  7 Nov 2011 08:45:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.817
X-Spam-Level: 
X-Spam-Status: No, score=-105.817 tagged_above=-999 required=5 tests=[AWL=-0.782, BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_TAG_BALANCE_BODY=1.263, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jwc2l0MEb1nu for <avt@ietfa.amsl.com>; Mon,  7 Nov 2011 08:45:09 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 8603921F8C3D for <avt@ietf.org>; Mon,  7 Nov 2011 08:45:09 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUA00L5HUJ2I5@szxga05-in.huawei.com> for avt@ietf.org; Tue, 08 Nov 2011 00:45:02 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUA00E2YUJ0O2@szxga05-in.huawei.com> for avt@ietf.org; Tue, 08 Nov 2011 00:45:02 +0800 (CST)
Received: from szxeml201-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEU70353; Tue, 08 Nov 2011 00:45:01 +0800
Received: from SZXEML411-HUB.china.huawei.com (10.82.67.138) by szxeml201-edg.china.huawei.com (172.24.2.39) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 08 Nov 2011 00:44:57 +0800
Received: from SZXEML519-MBS.china.huawei.com ([169.254.7.4]) by szxeml411-hub.china.huawei.com ([10.82.67.138]) with mapi id 14.01.0270.001; Tue, 08 Nov 2011 00:44:52 +0800
Date: Mon, 07 Nov 2011 16:44:51 +0000
From: Roni even <Even.roni@huawei.com>
X-Originating-IP: [172.24.2.41]
To: =?windows-1256?Q?IETF_AVTCore_WG_=FD=5Bavt=40ietf=2Eorg=5D=FD?= <avt@ietf.org>
Message-id: <EADCEEE0AE4A7F46BD61061696794D98F73E2C@SZXEML519-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_tPRfMpnw/tA3WY0FvD2fSw)"
Content-language: en-US
Accept-Language: en-US, zh-CN
Thread-topic: Updated agenda for AVTcore IETF82 session
Thread-index: Acyda7813ZFMVo82RvKXfhHVGkeqDw==
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
Subject: [AVTCORE] Updated agenda for AVTcore IETF82 session
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 07 Nov 2011 16:45:10 -0000

--Boundary_(ID_tPRfMpnw/tA3WY0FvD2fSw)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_a3zGxUSCBi0QKMl1z4o9GA)"


--Boundary_(ID_a3zGxUSCBi0QKMl1z4o9GA)
Content-type: text/plain; charset=windows-1256
Content-transfer-encoding: 7BIT

Hi,

This is the updated agenda, the changes from the previous ones are shorter time for ECN and adding the time to the multiplex issue adding http://tools.ietf.org/html/draft-lennox-rtcweb-rtp-media-type-mux-00 to the documents that will be discussed.



This topic is relevant to other WGs like RTCWeb and CLUE, please read these drafts before the meeting and send any comments to the avtcore mailing list

The result of the multiplex discussion will be presented by Magnus in RTCWeb session.



Regards

Roni Even

--Boundary_(ID_a3zGxUSCBi0QKMl1z4o9GA)
Content-type: text/html; charset=windows-1256
Content-transfer-encoding: 7BIT

<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1256">
<style id="owaParaStyle">P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body fPStyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">
<p>Hi,</p>
<p>This is the updated agenda, the changes from the previous ones are shorter time for ECN and adding the time to the multiplex issue adding
<a href="http://tools.ietf.org/html/draft-lennox-rtcweb-rtp-media-type-mux-00">http://tools.ietf.org/html/draft-lennox-rtcweb-rtp-media-type-mux-00</a>&nbsp;to the documents that will be discussed.</p>
<p>&nbsp;</p>
<p>This topic is relevant to other WGs like&nbsp;RTCWeb<a></a><a></a> and CLUE, please read these drafts before the meeting and send any comments to the&nbsp;avtcore<a></a><a></a> mailing list</p>
<p>The result of the&nbsp;multiplex<a></a> discussion will be presented by Magnus in&nbsp;RTCWeb<a></a><a></a> session.</p>
<p>&nbsp;</p>
<p>Regards</p>
<p><a></a><a></a>Roni&nbsp;Even</p>
</div>
</body>
</html>

--Boundary_(ID_a3zGxUSCBi0QKMl1z4o9GA)--

--Boundary_(ID_tPRfMpnw/tA3WY0FvD2fSw)
Content-id: <0a46abdb-c7fa-42c4-acd6-28220b687fde>
Content-type: text/html; name=a1111.html
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=a1111.html; size=2931;
 creation-date="Mon, 07 Nov 2011 16:39:43 GMT";
 modification-date="Mon, 07 Nov 2011 16:39:43 GMT"
Content-description: a1111.html

<html>
<head>
<title>Audio/Video Transport Core Maintenance  (AVTCore) Working Group Agenda</title>
</head>
<body bgcolor="#ffffff"><h1>Audio/Video Transport Core Maintenance  (AVTCore) Working Group Agenda</h1>
<hr>
<p>
<h3>
Chairs: Magnus Westerlund       <magnus.westerlund@ericsson.com>, Roni Even         <even.roni@huawei.com>
</h3>
<p>
<h2>Monday, 14 November 2011 at 13:00-15:00 (101 C)</h2>
<p>
<table border="0" cellpadding="5">
<tr>
<th align="left">13:00
<th align="left">AVTCore Status Update<th align="left">Chairs
<tr>
<th align="left">13:10
<th align="left">ECN for RTP over UDP<th align="left">Magnus Westerlund
<tr>
<td align="left">
<td align="left"><a href="http://tools.ietf.org/id/draft-ietf-avtcore-ecn-for-rtp-05">draft-ietf-avtcore-ecn-for-rtp-05</a>
<tr>
<th align="left">13:20
<th align="left">RTCP Extension for Feedback Suppression Indication<th align="left">Qin Wu
<tr>
<td align="left">
<td align="left"><a href="http://tools.ietf.org/id/draft-ietf-avtcore-feedback-supression-rtp-08">draft-ietf-avtcore-feedback-supression-rtp-08</a>
<tr>
<th align="left">13:35
<th align="left">Monitoring Architecture for RTP<th align="left">Qin Wu
<tr>
<td align="left">
<td align="left"><a href="http://tools.ietf.org/id/draft-ietf-avtcore-monarch-05">draft-ietf-avtcore-monarch-05</a>
<tr>
<th align="left">13:45
<th align="left">RTCP for inter-destination media synchronization<th align="left">Ray van Brandenburg
<tr>
<td align="left">
<td align="left"><a href="http://tools.ietf.org/id/draft-ietf-avtcore-idms-02">draft-ietf-avtcore-idms-02</a>
<tr>
<th align="left">13:55
<th align="left">RTP Multiplexing Architecture<th align="left">Magnus Westerlund 
<tr>
<td align="left">
<td align="left"><a href="http://tools.ietf.org/id/draft-westerlund-avtcore-multiplex-architecture-00">draft-westerlund-avtcore-multiplex-architecture-00</a>
<tr>
<th align="left">14:20
<th align="left">Multiple RTP Session on a Single Lower-Layer Transport<th align="left">Magnus Westerlund 
<tr>
<td align="left">
<td align="left"><a href="http://tools.ietf.org/id/draft-westerlund-avtcore-transport-multiplexing-01">draft-westerlund-avtcore-transport-multiplexing-01</a>
<tr>
<td align="left">
<td align="left"><a href="http://tools.ietf.org/id/draft-lennox-rtcweb-rtp-media-type-mux-00">draft-lennox-rtcweb-rtp-media-type-mux-00</a>
<tr>
<th align="left">14:40
<th align="left">Duplicating RTP Streams<th align="left">Begen
<tr>
<td align="left">
<td align="left"><a href="http://tools.ietf.org/id/draft-begen-avtcore-rtp-duplication-00">draft-begen-avtcore-rtp-duplication-00</a>
<tr>
<th align="left">14:50
<th align="left">Multipath RTP <th align="left">Varun Singh
<tr>
<td align="left">
<td align="left"><a href="http://tools.ietf.org/id/draft-singh-avt-mprtp-03">draft-singh-avt-mprtp-03</a>
<tr>
<th align="left">15:00
<th align="left">End</table>

--Boundary_(ID_tPRfMpnw/tA3WY0FvD2fSw)
Content-id: <0eb43a86-ad66-4bdb-8db1-a186fc592eb5>
Content-type: text/plain; name=a1111.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=a1111.txt; size=1506;
 creation-date="Mon, 07 Nov 2011 16:39:43 GMT";
 modification-date="Mon, 07 Nov 2011 16:39:43 GMT"
Content-description: a1111.txt

Audio/Video Transport Core Maintenance  (AVTCore) Working Group
===============================================================

CHAIRS:  Magnus Westerlund       <magnus.westerlund@ericsson.com>
         Roni Even         <even.roni@huawei.com>

AGENDA

Monday, 14 November 2011 at 13:00-15:00 (101 C)
-----------------------------------------------
13:00   AVTCore Status Update                               (Chairs, 10)

13:10   ECN for RTP over UDP                     (Magnus Westerlund, 10)
        draft-ietf-avtcore-ecn-for-rtp-05

13:20   RTCP Extension for Feedback Suppression Indication  (Qin Wu, 15)
        draft-ietf-avtcore-feedback-supression-rtp-08

13:35   Monitoring Architecture for RTP                     (Qin Wu, 10)
        draft-ietf-avtcore-monarch-05

13:45   RTCP for inter-destination media synchronization(Ray van Brandenburg, 10)
        draft-ietf-avtcore-idms-02

13:55   RTP Multiplexing Architecture           (Magnus Westerlund , 25)
        draft-westerlund-avtcore-multiplex-architecture-00

14:20   Multiple RTP Session on a Single Lower-Layer Transport(Magnus Westerlund , 20)
        draft-westerlund-avtcore-transport-multiplexing-01
        draft-lennox-rtcweb-rtp-media-type-mux-00

14:40   Duplicating RTP Streams                              (Begen, 10)
        draft-begen-avtcore-rtp-duplication-00

14:50   Multipath RTP                                  (Varun Singh, 10)
        draft-singh-avt-mprtp-03

15:00   End

--Boundary_(ID_tPRfMpnw/tA3WY0FvD2fSw)--

From eckelcu@cisco.com  Mon Nov  7 09:21:59 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C44821F8C36 for <avt@ietfa.amsl.com>; Mon,  7 Nov 2011 09:21:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.353
X-Spam-Level: 
X-Spam-Status: No, score=-6.353 tagged_above=-999 required=5 tests=[AWL=0.246,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LMRxVEMBPv8D for <avt@ietfa.amsl.com>; Mon,  7 Nov 2011 09:21:58 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id E090E21F8BF8 for <avt@ietf.org>; Mon,  7 Nov 2011 09:21:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=3398; q=dns/txt; s=iport; t=1320686518; x=1321896118; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=B5Qtm4gPaDaKsXtVFhqeawV+bEG21lItDl7QohvSQzE=; b=JZhy5LaDH17lc8J3ezkRDrCid+dAQCwlujZ4Qs2rfuaEN9P9yvrELOw4 YeDLUqiJgR/1VbIcZVLZ6nc+PEdXowVo/smVTBFirqVwDLnpkguXl4NIT ycWy0xgmUor0fsNvwTSQcxaUHhneH1GHfnQ+Em9hfw2ZxIyEb+F+yeDn5 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AskAAGsTuE6rRDoG/2dsb2JhbABCmgeOR4EigQWBcgEBAQMBAQEBDwEdCksEAgEIDgMEAQELBhcBBgEmHwkIAQEEARIIGodgCJhJAZ5hBIhIYwSIC5FQjFM
X-IronPort-AV: E=Sophos;i="4.69,471,1315180800"; d="scan'208";a="11310659"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 07 Nov 2011 17:21:55 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pA7HLt74023237; Mon, 7 Nov 2011 17:21:55 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 7 Nov 2011 09:21:55 -0800
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, 7 Nov 2011 09:21:54 -0800
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05B4B798@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <C7E873DD2F574ACCA02F6CCABE05B4E5@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVTCORE] comments on draft-ietf-avtcore-monarch-05
Thread-Index: AcydFXmWXD8+/eLuSo6id6ZN+DSaewAWSPXQ
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05B4B569@xmb-sjc-234.amer.cisco.com> <C7E873DD2F574ACCA02F6CCABE05B4E5@china.huawei.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Qin Wu" <bill.wu@huawei.com>, <avt@ietf.org>
X-OriginalArrivalTime: 07 Nov 2011 17:21:55.0211 (UTC) FILETIME=[BF3B6DB0:01CC9D71]
Subject: Re: [AVTCORE] comments on draft-ietf-avtcore-monarch-05
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 07 Nov 2011 17:21:59 -0000

Hi Qin,

Please see inline.

> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]
> Sent: Sunday, November 06, 2011 10:21 PM
> To: Charles Eckel (eckelcu); avt@ietf.org
> Subject: Re: [AVTCORE] comments on draft-ietf-avtcore-monarch-05
>=20
> Hi, Charles:
> Thank for your valuable comments, please see my reply below.
>=20
> Regards!
> -Qin
> ----- Original Message -----
> From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
> To: <avt@ietf.org>
> Sent: Saturday, November 05, 2011 6:30 AM
> Subject: [AVTCORE] comments on draft-ietf-avtcore-monarch-05
>=20
>=20
> >I read the draft and have the following comments:
> >
> > Section 2 and 3 contain some definitions. Should we add definitions
> > there for additional terms, including interval metric, cumulative
> > metric, and sampled metric. There has been some debate on the
> > definitions of these on xrblock alias, and it would be good to have
a
> > consistent definition of these terms.
>=20
> [Qin]: Fair, will add them into the update.
>=20
> > Section 3 reads, " The Metric Block exposes real time Application
> > Quality information". Section 2 defined transport level, application
> > level, and end system metrics. As such, the use of "application
quality
> > information" seems too specific and limiting to me.
>=20
> [Qin]: Correct, how about change as "QoS/QoE metric information".

Works for me.

> >
> > Section 5.2 read, There may be situation where more than one media
> > transport protocols are used by one application to interconnect to
the
> > same session in the gateway.  For example, one RTCP XR Packet is
sent to
> > the participating endpoints using non- RTP-based media transport
(e.g.,
> > using SIP) in a VOIP session, one crucial factor lies in how to
handle
> > their different identities that are corresponding to different media
> > transport."
> > Are we really expecting RTCP XR packets to be used outside of an RTP
> > session? Or are we trying to say there may be multiple RTP sessions
for
> > a given VoIP session, and there is a need to be able to correlate
the
> > RTCP XR packets from each of these RTP sessions with each other?
>=20
>=20
> [Qin]: Yes, this section focuses on describing correlation of RTP
session with Non-RTP
> session for monitoring purpose. You may read RFC5104 for an example
but not limited
> to this.

I was not able to find any description of correlating RTP and non RTP
sessions in RFC 5104.
RFC 5576 defines the "ssrc" SDP attribute, but even in that case, it
usage is defined for RTP-based media only. So am I still not sure of the
use case you have in mind here.

Thanks,
Charles

=20
> > Nits:
> >
> > Section 4:
> > - change " may have different monitoring requirements, design large
> > block ..." to " may have different monitoring requirements.
Designing
> > large block ..."
> > - change " it is hardly to provide" to " it is hard to provide"
> > - change " block types For example" to " block types.  For example"
> > - change " consecutive metric interval" to " consecutive metric
> > intervals"
>=20
> [Qin]: Fixed, thanks very much.
>=20
> >
> > Thanks,
> > Charles
> >
> >
> >
> > _______________________________________________
> > Audio/Video Transport Core Maintenance
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
> >

From bill.wu@huawei.com  Mon Nov  7 18:00:57 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E463D11E80CB for <avt@ietfa.amsl.com>; Mon,  7 Nov 2011 18:00:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.239
X-Spam-Level: 
X-Spam-Status: No, score=-5.239 tagged_above=-999 required=5 tests=[AWL=1.360,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mNgv4IWbJSKI for <avt@ietfa.amsl.com>; Mon,  7 Nov 2011 18:00:57 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id A9BA211E8073 for <avt@ietf.org>; Mon,  7 Nov 2011 18:00:56 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUB00GXJK9J3Q@szxga05-in.huawei.com> for avt@ietf.org; Tue, 08 Nov 2011 10:00:55 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUB00C8VK8YJE@szxga05-in.huawei.com> for avt@ietf.org; Tue, 08 Nov 2011 10:00:55 +0800 (CST)
Received: from szxeml201-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEU80546; Tue, 08 Nov 2011 10:00:55 +0800
Received: from SZXEML411-HUB.china.huawei.com (10.82.67.138) by szxeml201-edg.china.huawei.com (172.24.2.39) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 08 Nov 2011 10:00:50 +0800
Received: from w53375q (10.138.41.130) by szxeml411-hub.china.huawei.com (10.82.67.138) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 08 Nov 2011 10:00:45 +0800
Date: Tue, 08 Nov 2011 10:00:44 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, avt@ietf.org
Message-id: <3FEED5DF800D44DEA994B421F053578B@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05B4B569@xmb-sjc-234.amer.cisco.com> <C7E873DD2F574ACCA02F6CCABE05B4E5@china.huawei.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05B4B798@xmb-sjc-234.amer.cisco.com>
Subject: Re: [AVTCORE] comments on draft-ietf-avtcore-monarch-05
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 08 Nov 2011 02:00:58 -0000

Hi, Charles:
----- Original Message ----- 
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
Sent: Tuesday, November 08, 2011 1:21 AM
Subject: RE: [AVTCORE] comments on draft-ietf-avtcore-monarch-05


Hi Qin,

Please see inline.

> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]
> Sent: Sunday, November 06, 2011 10:21 PM
> To: Charles Eckel (eckelcu); avt@ietf.org
> Subject: Re: [AVTCORE] comments on draft-ietf-avtcore-monarch-05
> 
> Hi, Charles:
> Thank for your valuable comments, please see my reply below.
> 
> Regards!
> -Qin
> ----- Original Message -----
> From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
> To: <avt@ietf.org>
> Sent: Saturday, November 05, 2011 6:30 AM
> Subject: [AVTCORE] comments on draft-ietf-avtcore-monarch-05
> 
> 
> >I read the draft and have the following comments:
> >
> > Section 2 and 3 contain some definitions. Should we add definitions
> > there for additional terms, including interval metric, cumulative
> > metric, and sampled metric. There has been some debate on the
> > definitions of these on xrblock alias, and it would be good to have
a
> > consistent definition of these terms.
> 
> [Qin]: Fair, will add them into the update.
> 
> > Section 3 reads, " The Metric Block exposes real time Application
> > Quality information". Section 2 defined transport level, application
> > level, and end system metrics. As such, the use of "application
quality
> > information" seems too specific and limiting to me.
> 
> [Qin]: Correct, how about change as "QoS/QoE metric information".

Works for me.

> >
> > Section 5.2 read, There may be situation where more than one media
> > transport protocols are used by one application to interconnect to
the
> > same session in the gateway.  For example, one RTCP XR Packet is
sent to
> > the participating endpoints using non- RTP-based media transport
(e.g.,
> > using SIP) in a VOIP session, one crucial factor lies in how to
handle
> > their different identities that are corresponding to different media
> > transport."
> > Are we really expecting RTCP XR packets to be used outside of an RTP
> > session? Or are we trying to say there may be multiple RTP sessions
for
> > a given VoIP session, and there is a need to be able to correlate
the
> > RTCP XR packets from each of these RTP sessions with each other?
> 
> 
> [Qin]: Yes, this section focuses on describing correlation of RTP
session with Non-RTP
> session for monitoring purpose. You may read RFC5104 for an example
but not limited
> to this.

I was not able to find any description of correlating RTP and non RTP
sessions in RFC 5104.
RFC 5576 defines the "ssrc" SDP attribute, but even in that case, it
usage is defined for RTP-based media only. So am I still not sure of the
use case you have in mind here.

[Qin]: Sorry, I give you a wrong reference, it should be RFC6035.
In that case, we may need to consider how to deal different identities that corresponding to
both RTP session and SIP session. e.g., In SIP session, we may use global call identifier,
In RTP session, we may use SSRC, how to correlate with each other is the issue we may
need to look at. The solution is to use SDES item to associate SSRC of RTP stream with
global call identifier.

Thanks,
Charles

 
> > Nits:
> >
> > Section 4:
> > - change " may have different monitoring requirements, design large
> > block ..." to " may have different monitoring requirements.
Designing
> > large block ..."
> > - change " it is hardly to provide" to " it is hard to provide"
> > - change " block types For example" to " block types.  For example"
> > - change " consecutive metric interval" to " consecutive metric
> > intervals"
> 
> [Qin]: Fixed, thanks very much.
> 
> >
> > Thanks,
> > Charles
> >
> >
> >
> > _______________________________________________
> > Audio/Video Transport Core Maintenance
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
> >

From eckelcu@cisco.com  Tue Nov  8 09:22:14 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66CFB21F8B50 for <avt@ietfa.amsl.com>; Tue,  8 Nov 2011 09:22:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.369
X-Spam-Level: 
X-Spam-Status: No, score=-6.369 tagged_above=-999 required=5 tests=[AWL=0.230,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id diIg-OO0BaSX for <avt@ietfa.amsl.com>; Tue,  8 Nov 2011 09:22:13 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id A8D6421F84D2 for <avt@ietf.org>; Tue,  8 Nov 2011 09:22:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=5081; q=dns/txt; s=iport; t=1320772933; x=1321982533; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=UsBxAH+929hzpaXBh/Ov4P4jnMHbcaqYowx2cY3Wc4o=; b=ah+UKQ6VhhPn677ttA5BW4/rRZ3V9T4I/oxH6hsyZF7H4w5RY4jU2GNu nqzUeu7MccmdTZm6Dk4pJIfMNb+/nifr0dIgsWvSXwWzB7fUKBs8mf6qZ scEuf38Aauommo0AnZ2+r+xxMQwRmcGSXDWrL7Q/Ez1MPJc3a8hj5W08B Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvMAALRkuU6rRDoI/2dsb2JhbABEmhqOR4EmgQWBcgEBAQMBAQEBDwEdCkQHBAIBCA4DBAEBCwYXAQYBJh8JCAEBBAESCBMHh2AImFkBnwwEiEpjBIgLkVCMVQ
X-IronPort-AV: E=Sophos;i="4.69,477,1315180800"; d="scan'208";a="12976316"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 08 Nov 2011 17:22:13 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pA8HMDZF004187; Tue, 8 Nov 2011 17:22:13 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 8 Nov 2011 09:22:13 -0800
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, 8 Nov 2011 09:22:12 -0800
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05B4BB1E@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <3FEED5DF800D44DEA994B421F053578B@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVTCORE] comments on draft-ietf-avtcore-monarch-05
Thread-Index: AcydukOJrZoCE3blStmlllEuCYcUBAAf1IoQ
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05B4B569@xmb-sjc-234.amer.cisco.com> <C7E873DD2F574ACCA02F6CCABE05B4E5@china.huawei.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05B4B798@xmb-sjc-234.amer.cisco.com> <3FEED5DF800D44DEA994B421F053578B@china.huawei.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Qin Wu" <bill.wu@huawei.com>, <avt@ietf.org>
X-OriginalArrivalTime: 08 Nov 2011 17:22:13.0337 (UTC) FILETIME=[F472FC90:01CC9E3A]
Subject: Re: [AVTCORE] comments on draft-ietf-avtcore-monarch-05
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 08 Nov 2011 17:22:14 -0000

More inline.

> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]
> Sent: Monday, November 07, 2011 6:01 PM
> To: Charles Eckel (eckelcu); avt@ietf.org
> Subject: Re: [AVTCORE] comments on draft-ietf-avtcore-monarch-05
>=20
> Hi, Charles:
> ----- Original Message -----
> From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Sent: Tuesday, November 08, 2011 1:21 AM
> Subject: RE: [AVTCORE] comments on draft-ietf-avtcore-monarch-05
>=20
>=20
> Hi Qin,
>=20
> Please see inline.
>=20
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com]
> > Sent: Sunday, November 06, 2011 10:21 PM
> > To: Charles Eckel (eckelcu); avt@ietf.org
> > Subject: Re: [AVTCORE] comments on draft-ietf-avtcore-monarch-05
> >
> > Hi, Charles:
> > Thank for your valuable comments, please see my reply below.
> >
> > Regards!
> > -Qin
> > ----- Original Message -----
> > From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
> > To: <avt@ietf.org>
> > Sent: Saturday, November 05, 2011 6:30 AM
> > Subject: [AVTCORE] comments on draft-ietf-avtcore-monarch-05
> >
> >
> > >I read the draft and have the following comments:
> > >
> > > Section 2 and 3 contain some definitions. Should we add
definitions
> > > there for additional terms, including interval metric, cumulative
> > > metric, and sampled metric. There has been some debate on the
> > > definitions of these on xrblock alias, and it would be good to
have
> a
> > > consistent definition of these terms.
> >
> > [Qin]: Fair, will add them into the update.
> >
> > > Section 3 reads, " The Metric Block exposes real time Application
> > > Quality information". Section 2 defined transport level,
application
> > > level, and end system metrics. As such, the use of "application
> quality
> > > information" seems too specific and limiting to me.
> >
> > [Qin]: Correct, how about change as "QoS/QoE metric information".
>=20
> Works for me.
>=20
> > >
> > > Section 5.2 read, There may be situation where more than one media
> > > transport protocols are used by one application to interconnect to
> the
> > > same session in the gateway.  For example, one RTCP XR Packet is
> sent to
> > > the participating endpoints using non- RTP-based media transport
> (e.g.,
> > > using SIP) in a VOIP session, one crucial factor lies in how to
> handle
> > > their different identities that are corresponding to different
media
> > > transport."
> > > Are we really expecting RTCP XR packets to be used outside of an
RTP
> > > session? Or are we trying to say there may be multiple RTP
sessions
> for
> > > a given VoIP session, and there is a need to be able to correlate
> the
> > > RTCP XR packets from each of these RTP sessions with each other?
> >
> >
> > [Qin]: Yes, this section focuses on describing correlation of RTP
> session with Non-RTP
> > session for monitoring purpose. You may read RFC5104 for an example
> but not limited
> > to this.
>=20
> I was not able to find any description of correlating RTP and non RTP
> sessions in RFC 5104.
> RFC 5576 defines the "ssrc" SDP attribute, but even in that case, it
> usage is defined for RTP-based media only. So am I still not sure of
the
> use case you have in mind here.
>=20
> [Qin]: Sorry, I give you a wrong reference, it should be RFC6035.
> In that case, we may need to consider how to deal different identities
that corresponding to
> both RTP session and SIP session. e.g., In SIP session, we may use
global call identifier,
> In RTP session, we may use SSRC, how to correlate with each other is
the issue we may
> need to look at. The solution is to use SDES item to associate SSRC of
RTP stream with
> global call identifier.

I see. I now understand how to interpret the text within
draft-ietf-avtcore-monarch. I have some concerns regarding the mechanism
in RFC 6035, as the SIP Call-ID is a globally unique ID whereas the SSRC
is unique per RTP session only. That is more of an issue/limitation for
RFC 6035 than a concern with draft-ietf-avtcore-monarch, and
draft-ietf-avtcore-monarch addresses this by mentioning the combination
of CNAME and SSRC as a potential solution.

Cheers,
Charles
=20
> Thanks,
> Charles
>=20
>=20
> > > Nits:
> > >
> > > Section 4:
> > > - change " may have different monitoring requirements, design
large
> > > block ..." to " may have different monitoring requirements.
> Designing
> > > large block ..."
> > > - change " it is hardly to provide" to " it is hard to provide"
> > > - change " block types For example" to " block types.  For
example"
> > > - change " consecutive metric interval" to " consecutive metric
> > > intervals"
> >
> > [Qin]: Fixed, thanks very much.
> >
> > >
> > > Thanks,
> > > Charles
> > >
> > >
> > >
> > > _______________________________________________
> > > Audio/Video Transport Core Maintenance
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
> > >

From bill.wu@huawei.com  Tue Nov  8 18:29:33 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0018221F8541 for <avt@ietfa.amsl.com>; Tue,  8 Nov 2011 18:29:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.26
X-Spam-Level: 
X-Spam-Status: No, score=-5.26 tagged_above=-999 required=5 tests=[AWL=1.339,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cpd0FRsf-H1F for <avt@ietfa.amsl.com>; Tue,  8 Nov 2011 18:29:32 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 978BD21F853E for <avt@ietf.org>; Tue,  8 Nov 2011 18:29:31 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUD00FE8G70VE@szxga04-in.huawei.com> for avt@ietf.org; Wed, 09 Nov 2011 10:28:12 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUD00E6UG6P7M@szxga04-in.huawei.com> for avt@ietf.org; Wed, 09 Nov 2011 10:28:12 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEX39948; Wed, 09 Nov 2011 10:28:10 +0800
Received: from SZXEML412-HUB.china.huawei.com (10.82.67.91) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.270.1; Wed, 09 Nov 2011 10:28:05 +0800
Received: from w53375q (10.138.41.130) by szxeml412-hub.china.huawei.com (10.82.67.91) with Microsoft SMTP Server (TLS) id 14.1.270.1; Wed, 09 Nov 2011 10:28:02 +0800
Date: Wed, 09 Nov 2011 10:28:01 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, avt@ietf.org
Message-id: <D4F9E6B3BC3745B88BEC14D88B9A4AD5@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05B4B569@xmb-sjc-234.amer.cisco.com> <C7E873DD2F574ACCA02F6CCABE05B4E5@china.huawei.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05B4B798@xmb-sjc-234.amer.cisco.com> <3FEED5DF800D44DEA994B421F053578B@china.huawei.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05B4BB1E@xmb-sjc-234.amer.cisco.com>
Subject: Re: [AVTCORE] comments on draft-ietf-avtcore-monarch-05
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 09 Nov 2011 02:29:33 -0000

Yes, I agree.
----- Original Message ----- 
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
Sent: Wednesday, November 09, 2011 1:22 AM
Subject: RE: [AVTCORE] comments on draft-ietf-avtcore-monarch-05


More inline.

> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]
> Sent: Monday, November 07, 2011 6:01 PM
> To: Charles Eckel (eckelcu); avt@ietf.org
> Subject: Re: [AVTCORE] comments on draft-ietf-avtcore-monarch-05
> 
> Hi, Charles:
> ----- Original Message -----
> From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
> To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
> Sent: Tuesday, November 08, 2011 1:21 AM
> Subject: RE: [AVTCORE] comments on draft-ietf-avtcore-monarch-05
> 
> 
> Hi Qin,
> 
> Please see inline.
> 
> > -----Original Message-----
> > From: Qin Wu [mailto:bill.wu@huawei.com]
> > Sent: Sunday, November 06, 2011 10:21 PM
> > To: Charles Eckel (eckelcu); avt@ietf.org
> > Subject: Re: [AVTCORE] comments on draft-ietf-avtcore-monarch-05
> >
> > Hi, Charles:
> > Thank for your valuable comments, please see my reply below.
> >
> > Regards!
> > -Qin
> > ----- Original Message -----
> > From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
> > To: <avt@ietf.org>
> > Sent: Saturday, November 05, 2011 6:30 AM
> > Subject: [AVTCORE] comments on draft-ietf-avtcore-monarch-05
> >
> >
> > >I read the draft and have the following comments:
> > >
> > > Section 2 and 3 contain some definitions. Should we add
definitions
> > > there for additional terms, including interval metric, cumulative
> > > metric, and sampled metric. There has been some debate on the
> > > definitions of these on xrblock alias, and it would be good to
have
> a
> > > consistent definition of these terms.
> >
> > [Qin]: Fair, will add them into the update.
> >
> > > Section 3 reads, " The Metric Block exposes real time Application
> > > Quality information". Section 2 defined transport level,
application
> > > level, and end system metrics. As such, the use of "application
> quality
> > > information" seems too specific and limiting to me.
> >
> > [Qin]: Correct, how about change as "QoS/QoE metric information".
> 
> Works for me.
> 
> > >
> > > Section 5.2 read, There may be situation where more than one media
> > > transport protocols are used by one application to interconnect to
> the
> > > same session in the gateway.  For example, one RTCP XR Packet is
> sent to
> > > the participating endpoints using non- RTP-based media transport
> (e.g.,
> > > using SIP) in a VOIP session, one crucial factor lies in how to
> handle
> > > their different identities that are corresponding to different
media
> > > transport."
> > > Are we really expecting RTCP XR packets to be used outside of an
RTP
> > > session? Or are we trying to say there may be multiple RTP
sessions
> for
> > > a given VoIP session, and there is a need to be able to correlate
> the
> > > RTCP XR packets from each of these RTP sessions with each other?
> >
> >
> > [Qin]: Yes, this section focuses on describing correlation of RTP
> session with Non-RTP
> > session for monitoring purpose. You may read RFC5104 for an example
> but not limited
> > to this.
> 
> I was not able to find any description of correlating RTP and non RTP
> sessions in RFC 5104.
> RFC 5576 defines the "ssrc" SDP attribute, but even in that case, it
> usage is defined for RTP-based media only. So am I still not sure of
the
> use case you have in mind here.
> 
> [Qin]: Sorry, I give you a wrong reference, it should be RFC6035.
> In that case, we may need to consider how to deal different identities
that corresponding to
> both RTP session and SIP session. e.g., In SIP session, we may use
global call identifier,
> In RTP session, we may use SSRC, how to correlate with each other is
the issue we may
> need to look at. The solution is to use SDES item to associate SSRC of
RTP stream with
> global call identifier.

I see. I now understand how to interpret the text within
draft-ietf-avtcore-monarch. I have some concerns regarding the mechanism
in RFC 6035, as the SIP Call-ID is a globally unique ID whereas the SSRC
is unique per RTP session only. That is more of an issue/limitation for
RFC 6035 than a concern with draft-ietf-avtcore-monarch, and
draft-ietf-avtcore-monarch addresses this by mentioning the combination
of CNAME and SSRC as a potential solution.

Cheers,
Charles
 
> Thanks,
> Charles
> 
> 
> > > Nits:
> > >
> > > Section 4:
> > > - change " may have different monitoring requirements, design
large
> > > block ..." to " may have different monitoring requirements.
> Designing
> > > large block ..."
> > > - change " it is hardly to provide" to " it is hard to provide"
> > > - change " block types For example" to " block types.  For
example"
> > > - change " consecutive metric interval" to " consecutive metric
> > > intervals"
> >
> > [Qin]: Fixed, thanks very much.
> >
> > >
> > > Thanks,
> > > Charles
> > >
> > >
> > >
> > > _______________________________________________
> > > Audio/Video Transport Core Maintenance
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
> > >

From Even.roni@huawei.com  Wed Nov  9 00:44:26 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 864BE21F8B8A for <avt@ietfa.amsl.com>; Wed,  9 Nov 2011 00:44:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.208
X-Spam-Level: 
X-Spam-Status: No, score=-106.208 tagged_above=-999 required=5 tests=[AWL=0.391, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jeuuCSrmLWtX for <avt@ietfa.amsl.com>; Wed,  9 Nov 2011 00:44:25 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 117D521F8B89 for <avt@ietf.org>; Wed,  9 Nov 2011 00:44:25 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUD00J7GXIHL1@szxga04-in.huawei.com> for avt@ietf.org; Wed, 09 Nov 2011 16:42:17 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUD008NGXHY0F@szxga04-in.huawei.com> for avt@ietf.org; Wed, 09 Nov 2011 16:42:17 +0800 (CST)
Received: from szxeml202-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEV88208; Wed, 09 Nov 2011 16:42:16 +0800
Received: from SZXEML409-HUB.china.huawei.com (10.82.67.136) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.270.1; Wed, 09 Nov 2011 16:42:03 +0800
Received: from SZXEML519-MBS.china.huawei.com ([169.254.7.4]) by szxeml409-hub.china.huawei.com ([10.82.67.136]) with mapi id 14.01.0270.001; Wed, 09 Nov 2011 16:42:02 +0800
Date: Wed, 09 Nov 2011 08:42:00 +0000
From: Roni even <Even.roni@huawei.com>
In-reply-to: <4EB296C9.7030800@ericsson.com>
X-Originating-IP: [172.24.2.41]
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-id: <EADCEEE0AE4A7F46BD61061696794D98F7468D@SZXEML519-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=Windows-1252
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US, zh-CN
Thread-topic: [AVTCORE] Comments on draft-ietf-avtcore-feedback-supression-rtp-07
Thread-index: AQHMmixjQL2jWwgiZE6Jq8ttzSkuDJWkQiGa
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <4E8D76C1.5080508@ericsson.com> <BAC40485A1FA456CA771192D4F750C77@china.huawei.com> <4E9E93A0.10701@ericsson.com> <07aa01cc925b$2f351930$8d9f4b90$%roni@huawei.com> <4EB296C9.7030800@ericsson.com>
Cc: "draft-ietf-avtcore-feedback-supression-rtp@tools.ietf.org" <draft-ietf-avtcore-feedback-supression-rtp@tools.ietf.org>, 'IETF AVTCore WG' <avt@ietf.org>
Subject: Re: [AVTCORE] Comments on draft-ietf-avtcore-feedback-supression-rtp-07
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 09 Nov 2011 08:44:26 -0000

Magnus,
The report has the maximum and minimum values, so the receiver can use the =
maximum value or estimate his RTT based on his position between the minimum=
 and maximum
Roni

________________________________________
From: Magnus Westerlund [magnus.westerlund@ericsson.com]
Sent: Thursday, November 03, 2011 15:27
To: Roni even
Cc: Qin Wu; 'IETF AVTCore WG'; draft-ietf-avtcore-feedback-supression-rtp@t=
ools.ietf.org
Subject: Re: [AVTCORE] Comments on draft-ietf-avtcore-feedback-supression-r=
tp-07

On 2011-10-24 16:42, Roni Even wrote:
> Hi Magnus,
> Maybe we can add a recommendation for SSM to use the round trip sub repor=
t
> block specified in section 7.1.6 of RFC 5760
> (http://tools.ietf.org/html/rfc5760 ) to distribute the RTT from the
> distribution source to the receivers.

Well, that report is really the distribution for the whole session. If
one actually want that it can't be combined with only reporting the
distribution for a subset of the participants.

Cheers

Magnus

>
> Roni
>
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
>> Magnus Westerlund
>> Sent: Wednesday, October 19, 2011 11:09 AM
>> To: Qin Wu
>> Cc: IETF AVTCore WG; draft-ietf-avtcore-feedback-supression-
>> rtp@tools.ietf.org
>> Subject: Re: [AVTCORE] Comments on draft-ietf-avtcore-feedback-
>> supression-rtp-07
>>
>> Hi,
>>
>> Sorry for the delay in following up.
>>
>> I have removed the issues which don't need further discussion.
>>
>>
>> On 2011-10-11 03:40, Qin Wu wrote:
>>> Hi, Magnus,
>>> Thank for your valuable review, please see my replies belows.
>>> ----- Original Message -----
>>> From: "Magnus Westerlund" <magnus.westerlund@ericsson.com
>>
>>> 2. Section 3.
>>>   "The timer value shall be
>>>    based on the observed round-trip time.  A receiver should compute
>> an
>>>    estimate of the round-trip time (RTT) to the sender of TPLR from
>> RTCP
>>>    report round-trip time if available, or its reception time of the
>>>    reflected RTCP FB message (e.g.,NACK), or any other means."
>>>
>>> We hade the discussion before but now that you clarified which RTT to
>> be
>>> used, I think it is worth having a discussion if that RTT is the
>> right
>>> one. So you suggest that the RTT between the sender of the TPLR and
>> the
>>> receiver of the message is the most appropriate to use when
>> suppressing
>>> the message. I am not certain that is the case.
>>>
>>> Lets consider the use cases. In the case of an intermediary in a
>>> distribution tree sending the TPLR and at the same time sending a
>> NACK
>>> upstream. Then the time until the retransmission reaches the
>> suppressed
>>> receiver is the time from the sending of the NACK up to the
>>> retransmitting entity and all the way down past the TPLR sender to
>> the
>>> suppressed receiver. The receiver may not have a true RTT to the
>>> original media sender as that source appears to live at the TPLR
>> sender,
>>> not further upstream.
>>>
>>> Yes, the sender of the TPLR and the receiver might at least have
>> mutual
>>> knowledge of each other, thus the TPLR sender is able to determine
>> the
>>> lowest RTT in the set of receviers thus determining how often to
>> repeat
>>> it to cover additional time requried for the upstream part of the
>>> request. But I do note that these times aren't matching what appear
>> to
>>> be the delays in the systems.
>>>
>>> Can we find a better solution?
>>>
>>>
>>> [Qin]: It looks to me the round trip time between media source and
>>>
>>>  intermediary is trivial if we assume the intermediary is much
>>>
>>> closer to the source, that is why I put the last paragraph in the
>>>
>>> section 3 as follows:
>>>
>>> =93
>>>
>>> In order not to incur a lot of NACK requests due to additional TPLR
>>>
>>> described above, it is recommended that the RTP system sending
>>>
>>> TPLR should be implemented more closer to the source. Also when
>>>
>>>  the loss was detected and repair initiated much closer to the
>> source,
>>>
>>> the delay for the receiver to recover from packet loss can be reduced
>>>
>>> through the combination of intermediary feedback to the source and
>>>
>>> Third Party Loss Report downstream.
>>>
>>> =94
>>>
>>>
>>>
>>> If we look for a better solution, I think we have two possible ways:
>>>
>>> The first way is to rely on sender report from media sender to
>>>
>>> calculate the more approximate RTT from media sender to the receiver.
>>>
>>> RTT measurement method follows the same way described in the
>>>
>>> figure 2 of RFC3550.
>>>
>>>
>>>
>>> The second way is to we can allow the intermediary tell the receiver
>> the
>>>
>>> RTT from media source to intermediary itself by sending a new message
>>>
>>> since the intermediary can measure such RTT based on past observation
>>>
>>> and estimation. However for the second way we need to define new
>>>
>>> message or extend TPLR message to carry such RTT.
>>>
>>>
>>>
>>> What do you think?
>>>
>>
>> From follow up email:
>>> Hi,Magnus: As regarding if there is better solution, I have some
>>> corrections and additional thoughts.
>>> I think If the media source is the repair server, the receiver should
>>> set timer to T1=3Dmax(the RTT from media source to middlebox sending
>>> TPLR, 1/2 of RTT from middlebox to receiver) when the receiver
>>> receives first TPLR. When the receiver receive addtional TPLR within
>>> T1, the receiver should reset the timer to the RTT from media source
>>> to middlebox sending TPLR.
>>>
>>> If the middlebox is the repair server, the receiver should set the
>>> timer to T2=3D1/2 of RTT from middlebox to receiver when the receiver
>>> receives first TPLR. When the receiver receive addtional TPLR within
>>> T2, the receiver should reset the timer to the T2.
>>>
>>
>> Can you express these rules for the receiver as something that is based
>> on what is observable from the RTP and RTCP traffic? Is when media
>> server being repair server equal to TPLR sender SSRC =3D Media SSRC the
>> TPLR applies on? And if they are not the same it is the second case?
>>
>>
>>
>>>
>>>
>>> 3. Section 3:
>>>   "To increase the robustness to the loss of a TPLR or of a
>> transmission
>>>    packet, a receiver is allowed to receive additional TPLR for the
>> same
>>>    packet.  In the case the first TPLR is lost and the additional
>> TPLR
>>>    arrives at the receiver, the receiver should immediately refresh
>> the
>>>    timer."
>>>
>>> In the second sentence I don't see how the receiver can know that it
>> is
>>> a retransmission. It is simply a TPLR from its perspective if that is
>> lost.
>>>
>>> Robustness reasons is only one reason for repeating them the other is
>>> clearly to renew the timer. Thus I think the formulation should be
>> more
>>> generic to make it clear that all receivers should upon reception of
>> a
>>> TPLR refresh the timer for the packets indicated.
>>>
>>>
>>>
>>> [Qin]: If the receiver does not keep state for the times the TPLR is
>>>
>>>  retransmitted, we can add repetition count field in each FCI entry
>>>
>>>  of TPLR feedback message to indicate the times TPLR is
>> retransmitted.
>>>
>>>  Particularly in PSLEI Feedback Message, we can reuse seq nr. Field
>> to
>>>
>>>  indicate if additional TPLR is retransmitted, which one you think
>> better?
>>>
>>>
>>
>> How, can the receiver keep state for something it has not seen due to
>> the initial packet not having been received?
>>
>> I don't think we need new packet extensions, just clarified rules that
>> correctly describe what the RTP end-point should do when it sees the
>> TPLR message.
>>
>>
>>>
>>> 7. Section 4.2:
>>>    Seq nr:8bits  Command sequence number.  It is used by the Command
>>>       receiver to check if the Command is repeated.  The sequence
>> number
>>>       space is unique for each pairing of the SSRC of command sender
>> and
>>>       the SSRC of the command receiver.  The sequence number SHALL
>>>       increase by 1 modulo 256 for each new Command.  A repetition
>> SHALL
>>>       NOT increase the sequence number.  The initial value is
>> arbitrary.
>>>
>>> Based on that it is defined that upon receiving one of the PSLEI
>>> request, one shouldn't send a FIR or PLI message for a time interval
>>> equal to the RTT between the receiver and the sender of the PSLEI
>>> message does the sequence number field have any meaning? From my
>>> perspective it doesn't matter if it is a new request or not. You are
>>> suppressed from the reception of the message, nothing else.
>>>
>>> [Qin]: I think we can use seq nr field to indicate the times the TPLR
>> is
>>> retransmitted, e.g.,
>>>
>>> If the additional TPLR with the same SSRC and different Seq Number is
>>> received, the
>>>
>>> receiver knows that it is a retransmission if the receiver keeps
>> state
>>> for the previous
>>>
>>> TPLR with the same SSRC.
>>>
>>> Also we can replace seq nr. Field with Repetition count field to
>>> indicate how many time
>>>
>>> the TPLR is retransmitted.
>>>
>>>
>>
>> That is possible, but is the repetition count really providing
>> anything?
>> What is the simplest most straight forward that can work? I think that
>> is that one simple suppress the source for X time after having receives
>> a TPLR message indicate that source. So, as long as you get repeat
>> messages more often than X you continue to be suppressed. Will the
>> receiver work better to know that it is now suppressed for Y times in a
>> go because of the same event?
>>
>> cheers
>>
>> Magnus Westerlund
>>
>> ----------------------------------------------------------------------
>> Multimedia Technologies, Ericsson Research EAB/TVM
>> ----------------------------------------------------------------------
>> Ericsson AB                | Phone  +46 10 7148287
>> F=E4r=F6gatan 6                | Mobile +46 73 0949079
>> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
>> ----------------------------------------------------------------------
>>
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>
>


--

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
F=E4r=F6gatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------=

From magnus.westerlund@ericsson.com  Wed Nov  9 05:41:55 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C450F21F8B2B for <avt@ietfa.amsl.com>; Wed,  9 Nov 2011 05:41:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.556
X-Spam-Level: 
X-Spam-Status: No, score=-106.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zuHhe6Od3+1t for <avt@ietfa.amsl.com>; Wed,  9 Nov 2011 05:41:55 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 173C321F8B1B for <avt@ietf.org>; Wed,  9 Nov 2011 05:41:54 -0800 (PST)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-ef-4eba8322692c
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 3C.BF.13753.2238ABE4; Wed,  9 Nov 2011 14:41:54 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.137.0; Wed, 9 Nov 2011 14:41:53 +0100
Message-ID: <4EBA831F.8020806@ericsson.com>
Date: Wed, 9 Nov 2011 14:41:51 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Roni even <Even.roni@huawei.com>
References: <4E8D76C1.5080508@ericsson.com> <BAC40485A1FA456CA771192D4F750C77@china.huawei.com> <4E9E93A0.10701@ericsson.com> <07aa01cc925b$2f351930$8d9f4b90$%roni@huawei.com> <4EB296C9.7030800@ericsson.com> <EADCEEE0AE4A7F46BD61061696794D98F7468D@SZXEML519-MBS.china.huawei.com>
In-Reply-To: <EADCEEE0AE4A7F46BD61061696794D98F7468D@SZXEML519-MBS.china.huawei.com>
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: "draft-ietf-avtcore-feedback-supression-rtp@tools.ietf.org" <draft-ietf-avtcore-feedback-supression-rtp@tools.ietf.org>, 'IETF AVTCore WG' <avt@ietf.org>
Subject: Re: [AVTCORE] Comments on draft-ietf-avtcore-feedback-supression-rtp-07
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 09 Nov 2011 13:41:55 -0000

On 2011-11-09 09:42, Roni even wrote:
> Magnus, The report has the maximum and minimum values, so the
> receiver can use the maximum value or estimate his RTT based on his
> position between the minimum and maximum

If the relevant RTT is the largest, then fine. But if one was after the
RTT to particular entity that doesn't provide anything. As you don't
know where that entity is within the distribution. And that Distribution
also provides RTTs in relation to a given media sender.

Thus I don't understand how the receiver can estimate its RTT to the
media sender.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From magnus.westerlund@ericsson.com  Thu Nov 10 02:56:26 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0951C21F84C9 for <avt@ietfa.amsl.com>; Thu, 10 Nov 2011 02:56:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.938
X-Spam-Level: 
X-Spam-Status: No, score=-105.938 tagged_above=-999 required=5 tests=[AWL=-0.579, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_LWSHORTT=1.24, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L0pceu1+S1D2 for <avt@ietfa.amsl.com>; Thu, 10 Nov 2011 02:56:25 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id D027921F849C for <avt@ietf.org>; Thu, 10 Nov 2011 02:56:24 -0800 (PST)
X-AuditID: c1b4fb39-b7b3eae00000252a-da-4ebbadd737a3
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 2D.7A.09514.7DDABBE4; Thu, 10 Nov 2011 11:56:23 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.137.0; Thu, 10 Nov 2011 11:56:23 +0100
Message-ID: <4EBBADD5.4020501@ericsson.com>
Date: Thu, 10 Nov 2011 11:56:21 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Harald Alvestrand <harald@alvestrand.no>
References: <4EB7B054.3000706@ericsson.com> <4EB7B4D8.5050003@alvestrand.no>
In-Reply-To: <4EB7B4D8.5050003@alvestrand.no>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: Jonathan Lennox <jonathan@vidyo.com>, Jonathan Rosenberg <jonathan.rosenberg@skype.net>, IETF AVTCore WG <avt@ietf.org>
Subject: Re: [AVTCORE] Comments on draft-lennox-rtcweb-rtp-media-type-mux-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 10 Nov 2011 10:56:26 -0000

Harald,

Inline

On 2011-11-07 11:37, Harald Alvestrand wrote:

>
> why would such a gateway want to offer the BUNDLE extension in its SDP
> negotiation?
> (I'm assuming support for draft-holmberg-mmusic-sdp-bundle-negotiation
> as the way to negotiate multiple media types in a single session here.)
>
> An assumption in the deployment of extensions is that one is able to
> negotiate their non-use where some participant does not support the
> feature. I find your arguments compelling if (and only if) I accept the
> premises that:
>
> 1) Gateways between RTCWEB deployments and non-RTCWEB deployments will
> want to relay RTP sessions rather than terminate them (something which I
> do not believe, but that's another debate)
>
> 2) Gateways between RTCWEB deployments and non-RTCWEB deployments can't
> negotiatiate non-support for the BUNDLE extension with the RTCWEB deployment
>
> Given that I believe 2) is false, I don't agree with your conclusion.

I will follow up one below. But regarding 2) that is not the reason. 
Even if one can negotiate that the one bundles multiple media types in a 
single RTP session, there is going to be gateways/conference nodes that 
are going to turn on this feature anyway.

The reason for that behavior is that they will think this issue is a 
non-issue. Short term thinking rather than long term implications. They 
will like to avoid the small but existing risk of establishing more NAT 
pinholes. Also, to be certain that this not occurs, you either have zero 
possibility to use the non bundled session to a central node, or you 
configure your central node to never use bundling to avoid this. I think 
more than one developer will look at this and ignore the issue. Because 
if you don't think it through it do look simple on the surface. You 
simply translate the SSRCs if you end up in a collision.

When it comes to using a common session. I agree that for media mixing 
central nodes (RTP mixer), the RTP session is anyway almost individual 
between each end-point and end-point. The only information you forward 
between the legs are the CSRC CNAMEs to ensure the possibility to bind 
the information to the right sources.

But, when looking at the cheapest central node solution, the transport 
relay (transport translator) the common RTP session becomes interesting 
as it limits the central nodes processing to bascially a packet 
forwarder. This gives you on the order of 1000 times higher capacity in 
the number of streams the central node can handle compared to one that 
performs media operations given the same general purpose hardware. Thus 
having a common RTP session and not having to change anything within the 
packets, not even having to perform decryption and encryption cycles in 
the relay is a big bonus.


> The 3 viable approaches I see for gateways are:
>
> - The gateway refuses to negotiate BUNDLE with anyone
> - The gateway terminates RTP sessions
> - The gateway refuses to establish non-BUNDLE sessions at all
>
> In neither of these 3 scenarios do I see the issue you posit.
>
>
Agreed, these do avoid the issue of having to translate. From my 
perspective, they should be documented and considered if they will be 
followed.

Raising this issue had two goals.

1) Ensure that the issue and the implications on what one need to do is 
clearly documented in the draft.

2) Raise discussion if those are acceptable

So I hope the authors at least will agree to perform 1). Regarding the 
outcome of 2) that is very much open.

When it comes to 2) I think we need to take into account the 
alternative. Is any of the evaluated alternatives in 
https://datatracker.ietf.org/doc/draft-westerlund-avtcore-transport-multiplexing/ 
actually less problematic?

And I think it is important we do consider what happens when WebRTC is 
successful. I fear the desire to interoperate will kill of the RTP 
session completely as a useful tool. Instead all RTP users will end up 
with a single RTP session and we have to re-invent mechanisms for 
separation when the short-coming of not having an layer of multiplexing 
for media stream purposes.

I know that the window for this is closing, but I think we should at 
least have some reconsideration if the direction proposed in Quebec 
really was the most appropriate.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From harald@alvestrand.no  Thu Nov 10 04:33:09 2011
Return-Path: <harald@alvestrand.no>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 911FE21F8B1D for <avt@ietfa.amsl.com>; Thu, 10 Nov 2011 04:33:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.938
X-Spam-Level: 
X-Spam-Status: No, score=-109.938 tagged_above=-999 required=5 tests=[AWL=-0.579, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_LWSHORTT=1.24, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eVfR-j7ZT0vT for <avt@ietfa.amsl.com>; Thu, 10 Nov 2011 04:33:08 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 4B88721F8B03 for <avt@ietf.org>; Thu, 10 Nov 2011 04:33:08 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 6C68639E0FC; Thu, 10 Nov 2011 13:33:07 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id be0ENOoN7Dud; Thu, 10 Nov 2011 13:33:06 +0100 (CET)
Received: from hta-dell.lul.corp.google.com (62-20-124-50.customer.telia.com [62.20.124.50]) by eikenes.alvestrand.no (Postfix) with ESMTPS id E64B739E089; Thu, 10 Nov 2011 13:33:05 +0100 (CET)
Message-ID: <4EBBC481.5010504@alvestrand.no>
Date: Thu, 10 Nov 2011 13:33:05 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <4EB7B054.3000706@ericsson.com> <4EB7B4D8.5050003@alvestrand.no> <4EBBADD5.4020501@ericsson.com>
In-Reply-To: <4EBBADD5.4020501@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Jonathan Lennox <jonathan@vidyo.com>, Jonathan Rosenberg <jonathan.rosenberg@skype.net>, IETF AVTCore WG <avt@ietf.org>
Subject: Re: [AVTCORE] Comments on draft-lennox-rtcweb-rtp-media-type-mux-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 10 Nov 2011 12:33:09 -0000

This response has two parts:

- One discussion about the scenarios Magnus is positing in his note 
(first half)
- One discussion about evaluating the approaches proposed (second half)

People who want to comment on just one of them may want to fork the 
discussion.

On 11/10/2011 11:56 AM, Magnus Westerlund wrote:
> Harald,
>
> Inline
>
> On 2011-11-07 11:37, Harald Alvestrand wrote:
>
>>
>> why would such a gateway want to offer the BUNDLE extension in its SDP
>> negotiation?
>> (I'm assuming support for draft-holmberg-mmusic-sdp-bundle-negotiation
>> as the way to negotiate multiple media types in a single session here.)
>>
>> An assumption in the deployment of extensions is that one is able to
>> negotiate their non-use where some participant does not support the
>> feature. I find your arguments compelling if (and only if) I accept the
>> premises that:
>>
>> 1) Gateways between RTCWEB deployments and non-RTCWEB deployments will
>> want to relay RTP sessions rather than terminate them (something which I
>> do not believe, but that's another debate)
>>
>> 2) Gateways between RTCWEB deployments and non-RTCWEB deployments can't
>> negotiatiate non-support for the BUNDLE extension with the RTCWEB 
>> deployment
>>
>> Given that I believe 2) is false, I don't agree with your conclusion.
>
> I will follow up one below. But regarding 2) that is not the reason. 
> Even if one can negotiate that the one bundles multiple media types in 
> a single RTP session, there is going to be gateways/conference nodes 
> that are going to turn on this feature anyway.
>
> The reason for that behavior is that they will think this issue is a 
> non-issue. Short term thinking rather than long term implications. 
> They will like to avoid the small but existing risk of establishing 
> more NAT pinholes. Also, to be certain that this not occurs, you 
> either have zero possibility to use the non bundled session to a 
> central node, or you configure your central node to never use bundling 
> to avoid this. I think more than one developer will look at this and 
> ignore the issue. Because if you don't think it through it do look 
> simple on the surface. You simply translate the SSRCs if you end up in 
> a collision.

I still don't get this argument. Can you describe in more detail a 
situation where you think trouble will occur, which does not involve a 
transport translator?

>
> When it comes to using a common session. I agree that for media mixing 
> central nodes (RTP mixer), the RTP session is anyway almost individual 
> between each end-point and end-point. The only information you forward 
> between the legs are the CSRC CNAMEs to ensure the possibility to bind 
> the information to the right sources.
Not even that, for the case of central nodes that don't do source mixing.
>
> But, when looking at the cheapest central node solution, the transport 
> relay (transport translator) the common RTP session becomes 
> interesting as it limits the central nodes processing to bascially a 
> packet forwarder. This gives you on the order of 1000 times higher 
> capacity in the number of streams the central node can handle compared 
> to one that performs media operations given the same general purpose 
> hardware. Thus having a common RTP session and not having to change 
> anything within the packets, not even having to perform decryption and 
> encryption cycles in the relay is a big bonus.
Can you give some reference for the claim of "1000 times higher capacity"?
In particular, there are 3 cases:

- Pure packet forwarder ("transport translator")
- RTP session terminator, non-media-mixing
- RTP session terminator, media-mixing

I think it's reasonable to assume that the RTP session terminator will 
always do decrypt/encrypt, since not doing so requires using key 
handling schemes that are no more secure than the transport translator case.

Still, I think we may be talking about CPU time per packet well below a 
millisecond for the middle case.
>
>
>> The 3 viable approaches I see for gateways are:
>>
>> - The gateway refuses to negotiate BUNDLE with anyone
>> - The gateway terminates RTP sessions
>> - The gateway refuses to establish non-BUNDLE sessions at all
>>
>> In neither of these 3 scenarios do I see the issue you posit.
>>
>>
> Agreed, these do avoid the issue of having to translate. From my 
> perspective, they should be documented and considered if they will be 
> followed.
>
> Raising this issue had two goals.
>
> 1) Ensure that the issue and the implications on what one need to do 
> is clearly documented in the draft.
>
> 2) Raise discussion if those are acceptable
>
> So I hope the authors at least will agree to perform 1). Regarding the 
> outcome of 2) that is very much open.
>
> When it comes to 2) I think we need to take into account the 
> alternative. Is any of the evaluated alternatives in 
> https://datatracker.ietf.org/doc/draft-westerlund-avtcore-transport-multiplexing/ 
> actually less problematic?

I have serious problems with evaluating 
draft-westerlund-avtcore-transport-multiplexing, because I still 
disagree with its problem description.

That problem description is described in section 3.1 as "allow 
separation of streams that have different purposes, for example 
different media types".

I agree fully with the part before the comma; I disagree fully with the 
part after the comma. The idea that the *infrastructure needs to 
dictate* that different media types have different purposes is very far 
from self-evident, and I believe it to be false.

I believe that the user of RTP functionality is the only one who's in a 
position to decide when "different purposes" are appropriate.

This means that I think the solutions described in section 4.2 
(multiplexing shim) and section 4.3 (single session) are *both* 
appropriate to pursue, because I believe that there are situations where 
differing RTP sessions that need differential treatment in some way is 
important. Thus, the dichtonomy is false.

> And I think it is important we do consider what happens when WebRTC is 
> successful. I fear the desire to interoperate will kill of the RTP 
> session completely as a useful tool. Instead all RTP users will end up 
> with a single RTP session and we have to re-invent mechanisms for 
> separation when the short-coming of not having an layer of 
> multiplexing for media stream purposes.
>
> I know that the window for this is closing, but I think we should at 
> least have some reconsideration if the direction proposed in Quebec 
> really was the most appropriate.

In summary: I believe that pursuing multiplexing of RTP sessions across 
a single transport connection is a worthwhile pursuit, and the 
multiplexing shim seems a reasonable approach to make this work.

I believe that the RTP users are capable of evaluting for themselves 
when using multiple RTP sessions is appropriate, and that the current 
shortcoming of SDP that forces them to use multiple RTP sessions when 
the media they are sending is classified under different top level MIME 
types should be addressed - and that 
draft-homberg-mmusic-sdp-bundle-negotiation addresses this in a fashion 
that does not do damage to the rest of the SDP/RTP ecosystem.

                         Harald




From magnus.westerlund@ericsson.com  Thu Nov 10 06:40:04 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A261B21F8B4D for <avt@ietfa.amsl.com>; Thu, 10 Nov 2011 06:40:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.93
X-Spam-Level: 
X-Spam-Status: No, score=-105.93 tagged_above=-999 required=5 tests=[AWL=-0.571, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_LWSHORTT=1.24, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rJJuWwz-q+qz for <avt@ietfa.amsl.com>; Thu, 10 Nov 2011 06:40:03 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 4449621F8B47 for <avt@ietf.org>; Thu, 10 Nov 2011 06:40:03 -0800 (PST)
X-AuditID: c1b4fb39-b7b3eae00000252a-f9-4ebbe24123df
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 6C.EF.09514.142EBBE4; Thu, 10 Nov 2011 15:40:01 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.137.0; Thu, 10 Nov 2011 15:40:00 +0100
Message-ID: <4EBBE238.20103@ericsson.com>
Date: Thu, 10 Nov 2011 15:39:52 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Harald Alvestrand <harald@alvestrand.no>
References: <4EB7B054.3000706@ericsson.com> <4EB7B4D8.5050003@alvestrand.no> <4EBBADD5.4020501@ericsson.com> <4EBBC481.5010504@alvestrand.no>
In-Reply-To: <4EBBC481.5010504@alvestrand.no>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: Jonathan Lennox <jonathan@vidyo.com>, Jonathan Rosenberg <jonathan.rosenberg@skype.net>, IETF AVTCore WG <avt@ietf.org>
Subject: Re: [AVTCORE] Comments on draft-lennox-rtcweb-rtp-media-type-mux-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 10 Nov 2011 14:40:04 -0000

Hi,

Inline with comments on both topics.

On 2011-11-10 13:33, Harald Alvestrand wrote:
> This response has two parts:
>
> - One discussion about the scenarios Magnus is positing in his note
> (first half)
> - One discussion about evaluating the approaches proposed (second half)
>
> People who want to comment on just one of them may want to fork the
> discussion.
>
> On 11/10/2011 11:56 AM, Magnus Westerlund wrote:
>> On 2011-11-07 11:37, Harald Alvestrand wrote:
>>
>> The reason for that behavior is that they will think this issue is a
>> non-issue. Short term thinking rather than long term implications.
>> They will like to avoid the small but existing risk of establishing
>> more NAT pinholes. Also, to be certain that this not occurs, you
>> either have zero possibility to use the non bundled session to a
>> central node, or you configure your central node to never use bundling
>> to avoid this. I think more than one developer will look at this and
>> ignore the issue. Because if you don't think it through it do look
>> simple on the surface. You simply translate the SSRCs if you end up in
>> a collision.
>
> I still don't get this argument. Can you describe in more detail a
> situation where you think trouble will occur, which does not involve a
> transport translator?

The most likely case I think is the legacy gateway. Yes, the purpose 
with the fallback is to avoid it. However, if you have a SIP SBG and you 
anyway need to do ICE termination, then the media separation into two 
RTP sessions might actually be that you decide that it looks simpler to 
have bundled media on the WebRTC side and only one instance of the ICE 
termination, than to have two ICE terminations and not do the session 
separation.

But, I do agree, there is nothing forcing an implementation to do this. 
I only fear that implementors in their search for features to 
differentiate themselves will put something on the spec sheet for an SBG 
to an SIP or IMS system that says:

- Support WebRTC Bundle of media types, improved NAT traversal performance!


>
>>
>> When it comes to using a common session. I agree that for media mixing
>> central nodes (RTP mixer), the RTP session is anyway almost individual
>> between each end-point and end-point. The only information you forward
>> between the legs are the CSRC CNAMEs to ensure the possibility to bind
>> the information to the right sources.
> Not even that, for the case of central nodes that don't do source mixing.
>>
>> But, when looking at the cheapest central node solution, the transport
>> relay (transport translator) the common RTP session becomes
>> interesting as it limits the central nodes processing to bascially a
>> packet forwarder. This gives you on the order of 1000 times higher
>> capacity in the number of streams the central node can handle compared
>> to one that performs media operations given the same general purpose
>> hardware. Thus having a common RTP session and not having to change
>> anything within the packets, not even having to perform decryption and
>> encryption cycles in the relay is a big bonus.

> Can you give some reference for the claim of "1000 times higher capacity"?

I can give you the motivation why I believe 1000 be the right ball park 
figure.

If you do a pure packet forwarder what you have to do is.
- Receive the packet from a given UDP flow, look up the corresponding 
outgoing UDP flows, forward it out one all of these flows.

- If you have a media mixing functionality then you will have to:
   - Receive the RTP packet
   - Decrypt the RTP packet
   - Decode the RTP packet
   - Perform up to one mix per destination with this media and others
   - Encode the mix
   - Encrypt the mix

That are at least 5 different steps, Decryption, Decoding, Mixing, 
Encoding, Encryption where the required CPU operations per byte of data 
is a number of CPU operations. G.719 for example has a complexity figure 
of roughly 18 MIPS, how many RTP packets can you forward using 18 MIPS. 
Quite a lot.

- If it is non mixing entity like an RTP mixer that switches media 
streams, i.e. sends them out using the Mixer's SSRCs. Then you still 
have the decryption and encryption cycle even if the media mixing, 
encoding and decoding goes away. So this is clearly less complex, but 
still more heavy than just forward the packet.

>
> Still, I think we may be talking about CPU time per packet well below a
> millisecond for the middle case.

Yes, but if your goal for how many streams a single media range server 
should handle is in the region of 100000 or more, then it does matter.

>
> I have serious problems with evaluating
> draft-westerlund-avtcore-transport-multiplexing, because I still
> disagree with its problem description.
>
> That problem description is described in section 3.1 as "allow
> separation of streams that have different purposes, for example
> different media types".
>
> I agree fully with the part before the comma; I disagree fully with the
> part after the comma. The idea that the *infrastructure needs to
> dictate* that different media types have different purposes is very far
> from self-evident, and I believe it to be false.

I agree that the application should have the freedom to choose. And the 
goal of the RTP Multiplexing architecture document is to provide 
guidance in those choice to the application.

And I think my guidance so far is that separate media type do have a 
advantage of using separate RTP session. However, it is clear in the 
trade-off between additional UDP flows and having to build more 
elaborate demultiplexing of the incomming RTP packets based on the 
payload type I would also have chosen a single RTP session.

But if we remove that consideration from the equation, isn't it still a 
reasonably good choice to separate media types from each other from the 
sole reason that the processing handling of the different media types 
simply are different.

>> And I think it is important we do consider what happens when WebRTC is
>> successful. I fear the desire to interoperate will kill of the RTP
>> session completely as a useful tool. Instead all RTP users will end up
>> with a single RTP session and we have to re-invent mechanisms for
>> separation when the short-coming of not having an layer of
>> multiplexing for media stream purposes.
>>
>> I know that the window for this is closing, but I think we should at
>> least have some reconsideration if the direction proposed in Quebec
>> really was the most appropriate.
>
> In summary: I believe that pursuing multiplexing of RTP sessions across
> a single transport connection is a worthwhile pursuit, and the
> multiplexing shim seems a reasonable approach to make this work.
>
> I believe that the RTP users are capable of evaluting for themselves
> when using multiple RTP sessions is appropriate, and that the current
> shortcoming of SDP that forces them to use multiple RTP sessions when
> the media they are sending is classified under different top level MIME
> types should be addressed - and that
> draft-homberg-mmusic-sdp-bundle-negotiation addresses this in a fashion
> that does not do damage to the rest of the SDP/RTP ecosystem.


Then my argument towards WebRTC is that it should chose the RTP shim 
based multiplexing as also a realization of the case when you have 
multiple media types in one RTP session. The shim based solution clearly 
can support that also, both in the media plane on the signaling.

The reason is that if WebRTC choices the single RTP session over a lower 
layer transport as the only implemented choice then the application 
developers in any case that could have use for multiple RTP sessions 
will still be locked into two choices if they want to have inter 
operation with WebRTC end-points

A) Using multiple media types in one RTP session over a single UDP flow

B) Using multiple RTP sessions over independent UDP flows.

While using SHIM would enable independent RTP sessions over a single UDP 
flow. Thus being capable of handling all the use cases, including 
towards gateways and transport translators where one leg doesn't have 
the same capabilities as the other when it comes to using multiple RTP 
sessions over a single transport. Thus preventing a lock in effect to a 
potentially problematic solution, even if one do want to run multiple 
media types in a single RTP session.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From jonathan@vidyo.com  Thu Nov 10 08:02:22 2011
Return-Path: <jonathan@vidyo.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC13021F8AB8 for <avt@ietfa.amsl.com>; Thu, 10 Nov 2011 08:02:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.429
X-Spam-Level: 
X-Spam-Status: No, score=-2.429 tagged_above=-999 required=5 tests=[AWL=0.170,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FIAcpfFFkva8 for <avt@ietfa.amsl.com>; Thu, 10 Nov 2011 08:02:22 -0800 (PST)
Received: from mxout.myoutlookonline.com (mxout.myoutlookonline.com [64.95.72.241]) by ietfa.amsl.com (Postfix) with ESMTP id 1188221F8A6F for <avt@ietf.org>; Thu, 10 Nov 2011 08:02:22 -0800 (PST)
Received: from mxout.myoutlookonline.com (localhost [127.0.0.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id 3BB167A2775; Thu, 10 Nov 2011 11:02:21 -0500 (EST)
X-Virus-Scanned: by SpamTitan at mail.lan
Received: from HUB028.mail.lan (unknown [10.110.2.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id 6E95D7A2AF7; Thu, 10 Nov 2011 11:02:04 -0500 (EST)
Received: from BE235.mail.lan ([10.110.32.235]) by HUB028.mail.lan ([10.110.17.28]) with mapi; Thu, 10 Nov 2011 11:01:41 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, Harald Alvestrand <harald@alvestrand.no>
Date: Thu, 10 Nov 2011 11:02:01 -0500
Thread-Topic: [AVTCORE] Comments on draft-lennox-rtcweb-rtp-media-type-mux-00
Thread-Index: AcyfuN/Fm+cjH8lJRPqslRw8xhmGrAAAqujQ
Message-ID: <C3759687E4991243A1A0BD44EAC823034C42D486BF@BE235.mail.lan>
References: <4EB7B054.3000706@ericsson.com> <4EB7B4D8.5050003@alvestrand.no> <4EBBADD5.4020501@ericsson.com> <4EBBC481.5010504@alvestrand.no> <4EBBE238.20103@ericsson.com>
In-Reply-To: <4EBBE238.20103@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Jonathan Rosenberg <jonathan.rosenberg@skype.net>, IETF AVTCore WG <avt@ietf.org>
Subject: Re: [AVTCORE] Comments on draft-lennox-rtcweb-rtp-media-type-mux-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 10 Nov 2011 16:02:23 -0000

(I'm cutting down this conversation heavily, to respond to just one point..=
.)

Magnus Westerlund wrote:

> - If it is non mixing entity like an RTP mixer that switches media stream=
s, i.e. sends them out using the Mixer's SSRCs. Then you still have the dec=
ryption and encryption cycle even if the media mixing, encoding and decodin=
g goes away. So this is clearly less complex, but still more heavy than jus=
t forward the packet.]

I think, in practice, that an RTP mixer *inevitably* has to have at least t=
his capability, and a pure transport translator is impossible for multipoin=
t conferences, assuming that the endpoints' sessions with the central point=
 are negotiated by SDP offer/answer.

The primary reason is that offer/answer allows each receiver to pick its ow=
n RTP payload type values.  This means the mixer has to re-write RTP header=
s, and also means it can't blindly forward unknown RTCP packets (since some=
 RTCP extensions refer to the session's payload types).=20

Additionally, both SDES and DTLS keying negotiate keys point-to-point, and =
offer/answer allows endpoints to pick their own b=3D receive bandwidth, whi=
ch means different RTCP timings.  Both of these can be worked around to som=
e extent (SRTP EKT is almost done, and having minorly-inconsistent RTCP tim=
ings is usually harmless), but it's not clear how much point there is to wo=
rking around these issues, given the first one.

In practice, though, decryption and re-encryption isn't that expensive, par=
ticularly on modern CPUs with built-in crypto accelerators.  It's certainly=
 tiny compared to the cost of media transcoding.


Thus, I think trying to design an architecture that makes pure-transport tr=
anslation possible is a lost cause, if your primary use cases are offer/ans=
wer based, and so there's no point in creating new mechanisms in an attempt=
 to support it.

Unless I'm missing something, SHIM falls in this category -- the benefits o=
f SHIM over single-session muxing are largely for transport translation.

--=20
Jonathan Lennox
jonathan@vidyo.com

From eckelcu@cisco.com  Thu Nov 10 10:29:30 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F420C21F8B70; Thu, 10 Nov 2011 10:29:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.998
X-Spam-Level: 
X-Spam-Status: No, score=-3.998 tagged_above=-999 required=5 tests=[AWL=-2.043, BAYES_00=-2.599, FRT_PENIS1=3.592, J_CHICKENPOX_73=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_UTF8=0.152]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L-utq3REGsUH; Thu, 10 Nov 2011 10:29:28 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 90FE821F8B63; Thu, 10 Nov 2011 10:29:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=26590; q=dns/txt; s=iport; t=1320949768; x=1322159368; h=mime-version:content-transfer-encoding:subject:date: message-id:from:to:cc; bh=+GMXAd5qG+XQSORlLQTYvsDsYECa/GTSs/lJSXoq23g=; b=CaFGdBIJmom8v2xGrNIyZv46wuvTFnD92f4Ad9VNG6/AEjVU4Y+zyFai AksIUitszXDvVA2RHa1TLbTuhDyL4T/fHsj9QSgs0J/jR2xOF3A8GBGUF gelkSkKUZ28k83caBL3bHos70ToOGu8fNdv1dtWCYfjvYwTamKOCl3RHS Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsIAANYWvE6rRDoG/2dsb2JhbABABIR9lTWOdYEFgQWBcgEBAQQBAQEPARANBDoLDAYBBgIRBAEBAQICBgYXAQICAwElHwYBAQEFBAEEEwgah2iZPwGMWZIHgTCFKYIPM2MEiA+RWoUBh1Q
X-IronPort-AV: E=Sophos;i="4.69,489,1315180800"; d="scan'208";a="13495755"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-4.cisco.com with ESMTP; 10 Nov 2011 18:29:27 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pAAITRtU029205; Thu, 10 Nov 2011 18:29:27 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 10 Nov 2011 10:29:27 -0800
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: Thu, 10 Nov 2011 10:29:24 -0800
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05C12E11@xmb-sjc-234.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: =?UTF-8?B?W3hyYmxvY2td562U5aSNOiBSZTog562U5aSNOiBHZW5lcmFsIGNvbQ==?= =?UTF-8?B?bWVudHMgb24geHJibG9jayBtZXRyaWNzIGRyYWZ0cw==?=
Thread-Index: AcyfQOikAGDHnzyVRnO4EJ69oXkSeQAlTGXg
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 10 Nov 2011 18:29:27.0075 (UTC) FILETIME=[AD920F30:01CC9FD6]
Cc: xrblock <xrblock@ietf.org>
Subject: [AVTCORE] =?utf-8?b?Rlc6IFt4cmJsb2NrXeetlOWkjTogUmU6IOetlOWkjTog?= =?utf-8?q?General_comments_on_xrblock_metrics_drafts?=
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 10 Nov 2011 18:29:30 -0000

KGFzIHhyYmxvY2sgY2hhaXIpDQoNCkZvcndhcmRpbmcgdG8gYXZ0Y29yZSBsaXN0IGFzIHRoZSBj
b21tZW50cyBhcmUgaW4gcmVnYXJkIHRvIGFuIGV4aXN0aW5nIEFWVENPUkUgd29ya2luZyBncm91
cCBkcmFmdC4NCkkgaGF2ZSBjYydkIHhyYmxvY2sgc3VjaCB0aGF0IGZvbGtzIG9uIHhyYmxvY2sg
a25vdyB0byBwb3N0IGFueSBmdXJ0aGVyIGNvbW1lbnRzIG9uIHRoaXMgdGhyZWFkIHRvIGF2dGNv
cmUuDQoNCkNoZWVycywNCkNoYXJsZXMNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZy
b206IFFpbiBXdSBbbWFpbHRvOmJpbGwud3VAaHVhd2VpLmNvbV0gDQpTZW50OiBXZWRuZXNkYXks
IE5vdmVtYmVyIDA5LCAyMDExIDQ6MzcgUE0NClRvOiBDaGFybGVzIEVja2VsIChlY2tlbGN1KTsg
QWxhbiBDbGFyazsgemhhb2ppbmdAc3R0cmkuY29tLmNuDQpDYzogeHJibG9jaw0KU3ViamVjdDog
UmU6IFt4cmJsb2NrXeetlOWkjTogUmU6IOetlOWkjTogR2VuZXJhbCBjb21tZW50cyBvbiB4cmJs
b2NrIG1ldHJpY3MgZHJhZnRzDQoNClllcywgdGhhdCdzIHdoYXQgSSB0aGluayB0byBhZGQgb25l
IHN1Y2ggZGVmaW5pdGlvbiB0byBkcmFmdC1pZXRmLWF2dGNvcmUtbW9uYXJjaC4NClRoYW5rIGZv
ciB5b3VyIHJlbWluZGluZy4NCg0KUmVnYXJkcyENCi1RaW4NCi0tLS0tIE9yaWdpbmFsIE1lc3Nh
Z2UgLS0tLS0gDQpGcm9tOiAiQ2hhcmxlcyBFY2tlbCAoZWNrZWxjdSkiIDxlY2tlbGN1QGNpc2Nv
LmNvbT4NClRvOiAiUWluIFd1IiA8YmlsbC53dUBodWF3ZWkuY29tPjsgIkFsYW4gQ2xhcmsiIDxh
bGFuLmQuY2xhcmtAdGVsY2hlbXkuY29tPjsgPHpoYW9qaW5nQHN0dHJpLmNvbS5jbj4NCkNjOiAi
eHJibG9jayIgPHhyYmxvY2tAaWV0Zi5vcmc+DQpTZW50OiBUaHVyc2RheSwgTm92ZW1iZXIgMTAs
IDIwMTEgNTo1NiBBTQ0KU3ViamVjdDogUmU6IFt4cmJsb2NrXeetlOWkjTogUmU6IOetlOWkjTog
R2VuZXJhbCBjb21tZW50cyBvbiB4cmJsb2NrIG1ldHJpY3MgZHJhZnRzDQoNCg0KPiAoQXMgYW4g
aW5kaXZpZHVhbCkNCj4gDQo+IEl0IGxvb2tzIGdvb2QgdG8gbWUgYXMgd2VsbC4gRnVydGhlcm1v
cmUsIGl0IHNlZW1zIHRoZXNlIGNvbW1lbnRzIGFyZSBhcHBsaWNhYmxlIHRvIG1vbml0b3Jpbmcg
bWV0cmljcyBpbiBnZW5lcmFsLCBub3QganVzdCB0aG9zZSBmb3IgUW9FLiBUaGF0IGJlaW5nIHRo
ZSBjYXNlLCBpcyB0aGUgaW50ZW50aW9uIHRvIGFkZCB0aGVzZSBkZWZpbml0aW9ucyBpbnRvIGRy
YWZ0LWlldGYtYXZ0Y29yZS1tb25hcmNoPw0KPiANCj4gQ2hlZXJzLA0KPiBDaGFybGVzDQo+IA0K
Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+IEZyb206IHhyYmxvY2stYm91bmNlc0Bp
ZXRmLm9yZyBbbWFpbHRvOnhyYmxvY2stYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFFp
biBXdQ0KPj4gU2VudDogVHVlc2RheSwgTm92ZW1iZXIgMDgsIDIwMTEgOTo1MSBQTQ0KPj4gVG86
IEFsYW4gQ2xhcms7IHpoYW9qaW5nQHN0dHJpLmNvbS5jbg0KPj4gQ2M6IHhyYmxvY2sNCj4+IFN1
YmplY3Q6IFJlOiBbeHJibG9ja13nrZTlpI06IFJlOiDnrZTlpI06IEdlbmVyYWwgY29tbWVudHMg
b24geHJibG9jayBtZXRyaWNzIGRyYWZ0cw0KPj4gDQo+PiBZb3VyIHByb3Bvc2FsIGxvb2tzIGdv
b2QgdG8gbWUuDQo+PiBUaGFua3MhDQo+PiANCj4+IFJlZ2FyZHMhDQo+PiAtUWluDQo+PiANCj4+
IC0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0NCj4+IEZyb206IEFsYW4gQ2xhcmsgPG1haWx0
bzphbGFuLmQuY2xhcmtAdGVsY2hlbXkuY29tPg0KPj4gVG86IFFpbiBXdSA8bWFpbHRvOmJpbGwu
d3VAaHVhd2VpLmNvbT4gIDsgemhhb2ppbmdAc3R0cmkuY29tLmNuDQo+PiBDYzogeHJibG9jayA8
bWFpbHRvOnhyYmxvY2tAaWV0Zi5vcmc+DQo+PiBTZW50OiBUdWVzZGF5LCBOb3ZlbWJlciAwOCwg
MjAxMSA5OjM2IFBNDQo+PiBTdWJqZWN0OiBSZTogW3hyYmxvY2tdIOetlOWkjTogUmU6IOetlOWk
jTogR2VuZXJhbCBjb21tZW50cyBvbiB4cmJsb2NrIG1ldHJpY3MgZHJhZnRzDQo+PiANCj4+IEhp
IFFpbg0KPj4gDQo+PiBUaGlzIGlzIGFuIGFsdGVybmF0aXZlIHRvIGludGVydmFsIG9yIHNhbXBs
ZSBhbmQgaGVuY2UgdGhlIHRocmVlIG9mIHRoZW0gbmVlZCB0byBiZSBlbnVtZXJhdGVkLg0KPj4g
DQo+PiBJbnRlcnZhbCBNZXRyaWMgZmxhZ3MgKEkpOiAyIGJpdHMNCj4+IA0KPj4gICAgICAgVGhp
cyBmaWVsZCBpcyB1c2VkIHRvIGluZGljYXRlIHdoZXRoZXIgdGhlID8/Pz8/Pz8/Pz8/Pw0KPj4g
ICAgICAgbWV0cmljcyBibG9jayBpcyBhbiBJbnRlcnZhbCwgQ3VtdWxhdGl2ZSBvciBTYW1wbGVk
IHJlcG9ydCwgdGhhdCBpcywNCj4+ICAgICAgIHdoZXRoZXIgdGhlIHJlcG9ydGVkIHZhbHVlcyBh
cHBseSB0byB0aGUgbW9zdCByZWNlbnQgbWVhc3VyZW1lbnQNCj4+ICAgICAgIGludGVydmFsIGR1
cmF0aW9uIGJldHdlZW4gc3VjY2Vzc2l2ZSBtZXRyaWNzIHJlcG9ydHMgKEk9MTApICh0aGUNCj4+
ICAgICAgIEludGVydmFsIER1cmF0aW9uKSBvciB0byB0aGUgYWNjdW11bGF0aW9uIHBlcmlvZCBj
aGFyYWN0ZXJpc3RpYyBvZg0KPj4gICAgICAgY3VtdWxhdGl2ZSBtZWFzdXJlbWVudHMgKEk9MDAp
ICh0aGUgQ3VtdWxhdGl2ZSBEdXJhdGlvbikgb3INCj4+ICAgICAgIHRvIHRoZSB2YWx1ZSBvZiBh
IGNvbnRpbnVvdXNseSBtZWFzdXJlZCBvciBjYWxjdWxhdGVkIHRoYXQgaGFzIGJlZW4NCj4+ICAg
ICAgIHNhbXBsZWQgYXQgZW5kIG9mIHRoZSBpbnRlcnZhbCAoST0wMSkgKFNhbXBsZWQgVmFsdWUp
Lg0KPj4gDQo+PiBCZXN0IFJlZ2FyZHMNCj4+IA0KPj4gQWxhbg0KPj4gDQo+PiANCj4+IE9uIDEx
LzcvMTEgODo0MyBQTSwgIlFpbiBXdSIgPGJpbGwud3VAaHVhd2VpLmNvbT4gd3JvdGU6DQo+PiAN
Cj4+IA0KPj4gDQo+PiBIaSwgQWxhbjoNCj4+IEJhc2VkIG9uIG91ciBkaXNjdXNzaW9uLCB3b3Vs
ZCB5b3UgbGlrZSB0byBwcm9wb3NlIHRoZSBjaGFuZ2UgdG8gdGhlIGRyYWZ0cyByZWdhcmRpbmcN
Cj4+IHNhbXBsZSBtZXRyaWM/DQo+PiBlLmcuLCB3aGF0J3MgeW91ciBwcm9wb3NlZCBjaGFuZ2Ug
dG8gdGhlIEludGVydmFsIG1ldHJpYyBmbGFnPyBvciBqdXN0IGFsbG9jYXRlIGFkZGl0aW9uYWwN
Cj4+IGZhbGcgdG8gc2FtcGxlPw0KPj4gQWxzbyBpdCB3aWxsIGJlIGdyZWF0IHlvdSBwcm92aWRl
IHRoZSBjbGVhciBkZWZpbml0aW9uIG9mIHNhbXBsZSBtZXRyaWMuDQo+PiBNeSB1bmRlcnN0YW5k
aW5nIHRvIHNhbXBsZSBtZXRyaWNzIGlzOg0KPj4gIg0KPj4gU2FtcGxlIG1ldHJpY3MNCj4+IA0K
Pj4gSXQgaXMgcmVmZXJyZWQgdG8gdGhlIG1ldHJpY3Mgb2Ygd2hpY2ggdGhlIHJlcG9ydGVkIHZh
bHVlcyBvbmx5DQo+PiBhcHBseSB0byB0aGUgc2FtcGxlIGluc3RhbnQgd2hpY2ggaXMgYW55IHRp
bWUgb2YgdGhlIG1lYXN1cmVtZW50IGR1cmF0aW9uLg0KPj4gIg0KPj4gSWYgdGhpcyBpcyBub3Qg
cHJlY2lzZSwgcGxlYXNlIGNvcnJlY3QgbWUuIFRoYW5rcyENCj4+IA0KPj4gUmVnYXJkcyENCj4+
IC1RaW4NCj4+IA0KPj4gDQo+PiANCj4+IC0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0NCj4+
IA0KPj4gRnJvbTogIEFsYW4gQ2xhcmsgPG1haWx0bzphbGFuLmQuY2xhcmtAdGVsY2hlbXkuY29t
Pg0KPj4gDQo+PiBUbzogUWluIFd1IDxtYWlsdG86YmlsbC53dUBodWF3ZWkuY29tPiAgOyB6aGFv
amluZ0BzdHRyaS5jb20uY24NCj4+IA0KPj4gQ2M6IHhyYmxvY2sgPG1haWx0bzp4cmJsb2NrQGll
dGYub3JnPg0KPj4gDQo+PiBTZW50OiBGcmlkYXksIE5vdmVtYmVyIDA0LCAyMDExIDEwOjA3IEFN
DQo+PiANCj4+IFN1YmplY3Q6IFJlOiBbeHJibG9ja10g562U5aSNOiBSZTog562U5aSNOiBHZW5l
cmFsICBjb21tZW50cyBvbiB4cmJsb2NrIG1ldHJpY3MgZHJhZnRzDQo+PiANCj4+IA0KPj4gSGkg
UWluDQo+PiANCj4+IFRoZSBnb2FsIGluIGVzdGFibGlzaGluZyBhIGZyYW1ld29yayAgc2hvdWxk
IGJlIHRvIG1ha2UgcHJvdmlzaW9uIGZvciB0aGluZ3MgdGhhdA0KPj4geW91IHdvdWxkIHJlYXNv
bmFibHkgZXhwZWN0LiAgIFRoZXJlIGFyZSBxdWl0ZSBhIGZldyBjb250aW51b3VzbHkgdmFyeWlu
ZyBwYXJhbWV0ZXJzIHRoYXQgY291bGQgYmUNCj4+IHJlcG9ydGVkIHVzaW5nIGEgc2FtcGxlZCBh
cHByb2FjaCAtIGF1ZGlvIHNpZ25hbCBsZXZlbCwgbm9pc2UgbGV2ZWwsIHZpZGVvICBiYW5kd2lk
dGggdG8gbmFtZSBhIGZldy4NCj4+IA0KPj4gVGhlIGZpcnN0IHBhcnQgb2YgdGhlIGhlYWRlciBj
b21wcmlzZXMNCj4+IC0gQmxvY2sgdHlwZSAoOCBiaXRzKQ0KPj4gLSBJbnRlcnZhbC9DdW11bGF0
aXZlICggMSBiaXQpDQo+PiAtIFRhZyAoMyAgYml0cykNCj4+IC0gUmVzZXJ2ZWQgKDQgYml0cykN
Cj4+IA0KPj4gRXhwYW5kaW5nIHRoZSBJbnRlcnZhbC9DdW11bGF0aXZlIHRvIDIgIGJpdHMgc3Rp
bGwgbGVhdmVzIDMgcmVzZXJ2ZWQgYml0cywgc28gdGhpcw0KPj4gd291bGQgbm90IGJyZWFrIHRo
ZSAgYnVkZ2V0Lg0KPj4gDQo+PiBCZXN0IFJlZ2FyZHMNCj4+IA0KPj4gQWxhbg0KPj4gDQo+PiAN
Cj4+IA0KPj4gDQo+PiBPbiAxMS8zLzExIDk6MjYgUE0sICAiUWluIFd1IiA8YmlsbC53dUBodWF3
ZWkuY29tPiAgd3JvdGU6DQo+PiANCj4+IA0KPj4gDQo+PiANCj4+IEhpLCBBbGFuOg0KPj4gSSB0
ZW5kIHRvIGFncmVlIHdpdGggeW91LiBCdXQgY3VycmVudGx5ICBJIGRvbid0IHNlZSB0aGUgc2Ft
cGxlZCBtZXRyaWMgaXMNCj4+IGFwcGxpZWQgdG8gYWxsIHRoZSBtZXRyaWNzIGV4Y2VwdCBQRFYg
IG1ldHJpYywNCj4+IFNvIG15IHByb3Bvc2FsIGlzIHRvIGFkZCBvbmUgYml0IGluIFBEViBtZXRy
aWMgYmxvY2sgaGVhZGVyIHRvICBpbmRpY2F0ZSBpZg0KPj4gc2FtcGxlIHdpbGwgYmUgdXNlZC4N
Cj4+IElmIHRoZXJlIGlzIGFueSBmdXR1cmUgbWV0cmljIHRoYXQgbmVlZCAgdG8gc3VwcG9ydCBz
YW1wbGUsIHdlIGNhbiBhZGQNCj4+IGluZGljYXRpb24gYml0ICBsYXRlci4NCj4+IA0KPj4gUmVn
YXJkcyENCj4+IC1RaW4NCj4+IA0KPj4gDQo+PiANCj4+IA0KPj4gLS0tLS0gT3JpZ2luYWwgTWVz
c2FnZSAtLS0tLQ0KPj4gDQo+PiBGcm9tOiAgQWxhbiBDbGFyayA8bWFpbHRvOmFsYW4uZC5jbGFy
a0B0ZWxjaGVteS5jb20+DQo+PiANCj4+IFRvOiBRaW4gV3UgPG1haWx0bzpiaWxsLnd1QGh1YXdl
aS5jb20+ICA7ICB6aGFvamluZ0BzdHRyaS5jb20uY24NCj4+IA0KPj4gQ2M6IHhyYmxvY2sgPG1h
aWx0bzp4cmJsb2NrQGlldGYub3JnPg0KPj4gDQo+PiBTZW50OiBUaHVyc2RheSwgTm92ZW1iZXIg
MDMsIDIwMTEgODoyNiAgIFBNDQo+PiANCj4+IFN1YmplY3Q6IFJlOiBbeHJibG9ja10g562U5aSN
OiBSZTog562U5aSNOiBHZW5lcmFsICAgY29tbWVudHMgb24geHJibG9jaw0KPj4gbWV0cmljcyBk
cmFmdHMNCj4+IA0KPj4gDQo+PiBRaW4NCj4+IA0KPj4gWW91ICBjYW5ub3QgZGVyaXZlIHRoZSB2
YWx1ZSBvZiBhIHNhbXBsZWQgIG1ldHJpYyBmcm9tIHR3byBpbnRlcnZhbA0KPj4gbWV0cmljcy4N
Cj4+IA0KPj4gQSBzYW1wbGVkIG1ldHJpYyBpcyB1c2VmdWwgZm9yICBtZWFzdXJpbmcgYW5kICBy
ZXBvcnRpbmcgb24gcGFyYW1ldGVycw0KPj4gdGhhdCB2YXJ5IGluIHRpbWUuIFNvbWV0aW1lcyBp
dCBpcyAgIGFjY2VwdGFibGUgdG8gcmVwb3J0IHRoZSBtaW4vbWF4L2F2ZXJhZ2Ugb2YgYSB0aW1l
IHZhcnlpbmcNCj4+IHBhcmFtZXRlciAgYW5kICBzb21ldGltZXMgeW91IG1heSB3YW50IHRvIHJl
cG9ydCB0aGUgdmFsdWUgYXQgcG9pbnRzIGluICB0aW1lLg0KPj4gDQo+PiBBdCByaXNrICBvZiBj
YXVzaW5nIGNvbXBsZXRlIGNvbmZ1c2lvbiAtIEnigJltIGdvaW5nIHRvICB1c2UgYSB0ZW1wZXJh
dHVyZQ0KPj4gZXhhbXBsZS4NCj4+IA0KPj4gKGkpIEJldHdlZW4gMnBtIGFuZCAzcG0gdGhlICBh
dmVyYWdlIHRlbXBlcmF0dXJlIHdhcyAxMCBkZWdyZWVzICBDLCBpcw0KPj4gYW4gaW50ZXJ2YWwg
bWV0cmljDQo+PiAoaWkpICBCZXR3ZWVuIDJwbSBhbmQgM3BtIHRoZSBtYXhpbXVtIHRlbXBlcmF0
dXJlICB3YXMgMTEgZGVncmVlcyBDLCBpcw0KPj4gYW4gIGludGVydmFsIG1ldHJpYw0KPj4gKGlp
KSBUaGUgdGVtcGVyYXR1cmUgYXQgM3BtIGlzIDIgIGRlZ3JlZXMgQyBpcyBhICBzYW1wbGVkIG1l
YXN1cmVtZW50DQo+PiANCj4+IEl0IGlzIHJlbWFya2FibHkgZWFzeSB0byBhZGQgb25lIGJpdCAg
dG8gIHRoZSBYUkJsb2NrIGhlYWQgYXQgdGhpcyB0aW1lDQo+PiB0byBhbGxvdyBmb3IgY3VycmVu
dCBvciBmdXR1cmUgbWV0cmljcyB0aGF0ICAgYXJlIHNhbXBsZWQuIEdpdmVuIHRoYXQgdGhlcmUg
YXJlIGV4aXN0aW5nIFJUUCBleGFtcGxlcw0KPj4gb2YgdGhpcyB0eXBlICBvZiBtZXRyaWMgIHRo
ZW4gd2Uga25vdyB0aGF0IGl0IGlzIGFscmVhZHkgdXNlZnVsIHRvIHJlcG9ydCBzYW1wbGVkICB2
YWx1ZXMuDQo+PiANCj4+IEJlc3QgIFJlZ2FyZHMNCj4+IA0KPj4gQWxhbg0KPj4gDQo+PiBPbiAx
MS8zLzExIDM6MTUgQU0sICAiUWluIFd1IiA8YmlsbC53dUBodWF3ZWkuY29tPiAgIHdyb3RlOg0K
Pj4gDQo+PiANCj4+IA0KPj4gDQo+PiANCj4+IEhpLCBBbGFuOg0KPj4gVGhhbmsgZm9yIHlvdXIg
Y2xhcmlmaWNhdGlvbiBvbiB0aGUgICBkaWZmZXJlbmNlIGJldHdlZW4gSW50ZXJ2YWwNCj4+IG1l
dHJpYywgQ3VtdWxhdGl2ZSBtZXRyaWMgdGhlIGV4aXN0aW5nICBkcmFmdCAgZGVzY3JpYmVkIGFu
ZCBzYW1wbGVkIG1ldHJpYyB5b3UgcHJvcG9zZWQuDQo+PiBJdCBsb29rcyAgU2FtcGxlIG1ldHJp
YyBpcyAgZXN0YWJsaXNoZWQgdXBvbiB0aGUgSW50ZXJ2YWwgbWV0cmljDQo+PiBhbmQgcHJlc2Vu
dCAgZGlmZmVyZW50IGZlYXR1cmVzIG9mIGFueSAgdHJhbnNwb3J0IGltcGFpcm1lbnRzIGZyb20g
Q3VsbXVsYXRpdmUgIG1ldHJpYy4NCj4+IGUuZy4sIHdlIGhhdmUgYSBsaXN0IG9mICBJbnRlcnZh
bCBtZXRyaWMNCj4+IHgxLCB4MiwgIHgzLHg0LHg1LHg2LHg3LHg4LHg5LHgxMA0KPj4gVGhlIHNh
bXBsZSBtZXRyaWMgaXMgIGFzICBmb2xsb3dzOg0KPj4gUzEsUzIsUzMsUzQsUzUsUzYsUzcsUzgs
UzksUzEwDQo+PiBTbyB0aGUgc2FtcGxlZCBtZXRpYyBjYW4gIGJlICBjYWxjdWxhdGVkIHVzaW5n
IHRoZSBmb2xsb3dpbmcNCj4+IGV4YW1wbGU6DQo+PiBTMT14MTsgUzI9ICBmdW5jKHgxLHgyKTsg
IFMzPWZ1bmMoeDIseDMpOyBTND1mdW5jKHgzLHg0KTsuLi4NCj4+IEluIHRoaXMgIGV4YW1wbGUs
IFNpIG9ubHkgcmVseSBvbiB0aGUgIHhpIGFuZCB4aS0xLg0KPj4gDQo+PiBTbyB0aGUgIHF1ZXN0
aW9uIGlzOg0KPj4gRG9lcyBzYW1wbGUgbWV0cmljIGZpeCB0aGUgIHByb2JsZW0geW91IHJhaXNl
ZCAgYmVsb3cgZm9yDQo+PiBDdW11bGF0aXZlIG1ldHJpYz8NCj4+IA0KPj4gQWxzbyB3aGF0J3Mg
dGhlICBzYW1wbGVkICBhbGdvcml0aG0gdXNlZCBmb3IgY2FsY3VsYXRpbmcgc3VjaA0KPj4gbWV0
cmljIGFuZCBwcmVzZW50ZWQgYXQgdGhlIGVuZCAgIG9mIGVhY2ggSW50ZXJ2YWw/IHRoZSBhbGdv
cml0aG0gc2ltaWxhciB0byBQUERWPyBvciBhbnkgYWxnb3JpdGhtDQo+PiB3ZSBjYW4gIGZpbmQ/
DQo+PiBEbyB5b3UgdGhpbmsgbWVhc3VyZW1lbnQgSW50ZXJ2YWwgZm9yIEludGVydmFsICBtZXRy
aWMgaXMgc2FtZSBhcw0KPj4gb25lIGZvciBTYW1wbGVkIG1ldHJpYz8NCj4+IA0KPj4gSXQgbG9v
a3MgdG8gIG1lIHRoYXQgaXQgaXMgbm90IHRoYXQgIHNpbXBsZSB0byBqdXN0IGFkZCBvbmUgbW9y
ZQ0KPj4gYml0IGluIHRoZSAgWFJCbG9jayBoZWFkZXIgdG8gaW5kaWNhdGUgU2FtcGxlZCAgbWV0
cmljIGlzIHVzZWQ/IFlvdSBzaG91bGQgbWFrZSAgc3VyZSB0aGUgbWVhc3VyZW1lbnQNCj4+IGlu
dGVydmFsIGFuZCBzcGVjaWZpYyAgc2FtcGxlZCAgYWxnb3JpdGhtPw0KPj4gQnV0IEludGVydmFs
IG1ldHJpYyBhbmQgQ3VtdWxhdGl2ZSBtZXRyaWMgZG9uJ3QgaGF2ZSAgIHN1Y2gNCj4+IGlzc3Vl
Lg0KPj4gDQo+PiANCj4+IFJlZ2FyZHMhDQo+PiAtUWluDQo+PiANCj4+IA0KPj4gDQo+PiANCj4+
IA0KPj4gLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLQ0KPj4gDQo+PiBGcm9tOiAgQWxhbiBD
bGFyayA8bWFpbHRvOmFsYW4uZC5jbGFya0B0ZWxjaGVteS5jb20+DQo+PiANCj4+IFRvOiBRaW4g
V3UgPG1haWx0bzpiaWxsLnd1QGh1YXdlaS5jb20+ICAgOw0KPj4gemhhb2ppbmdAc3R0cmkuY29t
LmNuDQo+PiANCj4+IENjOiB4cmJsb2NrIDxtYWlsdG86eHJibG9ja0BpZXRmLm9yZz4NCj4+IA0K
Pj4gU2VudDogVGh1cnNkYXksIE5vdmVtYmVyIDAzLCAyMDExICAxMDo0MSAgIEFNDQo+PiANCj4+
IFN1YmplY3Q6IFJlOiBbeHJibG9ja10g562U5aSNOiAgUmU6IOetlOWkjTogR2VuZXJhbCAgIGNv
bW1lbnRzIG9uDQo+PiB4cmJsb2NrIG1ldHJpY3MgIGRyYWZ0cw0KPj4gDQo+PiANCj4+IFFpbg0K
Pj4gDQo+PiBBbiAgaW50ZXJ2YWwgbWV0cmljIGlzICBtZWFzdXJlZCBvdmVyIGEgdGltZSAgaW50
ZXJ2YWwuICBBDQo+PiBjdW11bGF0aXZlICBtZXRyaWMgIGlzIHRoZSBzYW1lIGFzIGFuIGludGVy
dmFsIG1ldHJpYyBpZiB0aGVyZSAgaXMgb25seSBvbmUgICBpbnRlcnZhbC4NCj4+IA0KPj4gQSBt
ZXRyaWMgZm9yIGFuIGludGVydmFsIHNob3VsZCBub3QgYmUgYWZmZWN0ZWQgICBieQ0KPj4gcHJl
dmlvdXMgaW50ZXJ2YWxzLg0KPj4gDQo+PiBBIOKAnHNhbXBsZWTigJ0gbWV0cmljIGlzIHRoZSAg
dmFsdWUgb2YgYSBtZXRyaWMgYXQgICB0aGUNCj4+IGluc3RhbnQgb2Ygc2FtcGxpbmcuDQo+PiAN
Cj4+IChhKSAgU2ltcGxlIGNhc2UNCj4+IA0KPj4gSWYgd2UgIGNvbnNpZGVyIDEwICBpbnRlcnZh
bHMsIGVhY2ggd2l0aCAgMTAwMCBwYWNrZXRzDQo+PiBleHBlY3RlZC4gICBJbnRlcnZhbHMgMSBh
bmQgMyBoYXZlIDEwMCAgIHBhY2tldHMgbWlzc2luZy4NCj4+IA0KPj4gQ3VtdWxhdGl2ZSAgcGFj
a2V0IGxvc3MgcmF0ZSwgIHJlcG9ydGVkIGF0IHRoZSBlbmQgb2YgIGVhY2gNCj4+IGludGVydmFs
IHdvdWxkICBiZQ0KPj4gDQo+PiAxMCUsICA1JSwgNi43JSwgNSUsIDQlLCAzLjMlLCAyLjklLCAy
LjUlLCAyLjIlLCAgICAyLjAlDQo+PiANCj4+IEludGVydmFsIHBhY2tldCBsb3NzIHJhdGUgd291
bGQgYmUNCj4+IDEwJSwgMCUsICAxMCUsIDAlLCAgMCUsIDAlLCAgMCUsIDAlLCAwJSwgMCUNCj4+
IA0KPj4gQXZlcmFnaW5nICB0aGUgaW50ZXJ2YWwgbG9zcyAgcmF0ZXMgZ2l2ZXMgICgxMCsxMCkv
MTAgPQ0KPj4gMi4wJQ0KPj4gDQo+PiBjYWxjdWxhdGluZyB0aGUgcnVubmluZyBhdmVyYWdlICBs
b3NzIHJhdGUgYW5kICAgcmVwb3J0aW5nDQo+PiBzYW1wbGVkIHZhbHVlcyB3b3VsZCBnaXZlIHNv
bWV0aGluZyByb3VnaGx5ICAgbGlrZQ0KPj4gDQo+PiAxMCUsIDMlLCAgMTAlLCAzJSwgMSUsIDAu
MSUsIDAuMDElLCAwJSwgMCUsICAwJQ0KPj4gDQo+PiAoYikgIFNsaWdodGx5IGxlc3Mgc2ltcGxl
ICBjYXNlDQo+PiANCj4+IEFzc3VtZSB0aGUgIHNhbWUgaW50ZXJ2YWxzIGFuZCBsb3NzICByYXRl
cyBob3dldmVyIHNheSB0aGF0DQo+PiBzb21lIG9mICB0aGUgIHBhY2tldHMgZnJvbSBpbnRlcnZh
bCAxIHdlcmUgbm90ICBhY3R1YWxseSBsb3N0LCBidXQgYXJyaXZlIGluICBpbnRlcnZhbCAyLiAg
IFNvIGF0IHRoZQ0KPj4gdGltZSB0aGUgIHBhY2tldCBsb3NzIHJhdGUgd2FzICBjYWxjdWxhdGVk
IGZvciBpbnRlcnZhbCAxIGl0ICBhcHBlYXJlZCB0byBiZSA4JSAgaW5zdGVhZCBvZiAgMTAlLg0K
Pj4gDQo+PiBXZSBkb27igJl0IHR5cGljYWxseSByZXBvcnQgbmVnYXRpdmUgIGxvc3MgIHJhdGVz
LCAgc28gdGhlDQo+PiBpbnRlcnZhbCBsb3NzIHJhdGUgd291bGQgYmUgcmVwb3J0ZWQgYXMNCj4+
IA0KPj4gOCUsICAgIDAlLi4uLi4NCj4+IA0KPj4gSWYgd2UgY29tcHV0ZSBsb3NzIHJhdGUgY3Vt
dWxhdGl2ZWx5IHRoZW4gIHRoaXMgIHByb2JsZW0NCj4+IHdvdWxkICBvbmx5IG9jY3VyIGF0IHRo
ZSBlbmQgb2YgdGhlIGN1bXVsYXRpdmUgIHBlcmlvZCwgc28gdGhlICBsb3NzIHJhdGVzIHJlcG9y
dGVkICB3b3VsZCBiZQ0KPj4gDQo+PiA4JSwgNSUsICAuLi4NCj4+IA0KPj4gSW4gb3RoZXIgIHdv
cmRzIHRoZSBjdW11bGF0aXZlIG1ldHJpYyAgY29ycmVjdHMgIGl0c2VsZi4NCj4+IA0KPj4gVGhp
cyB3b3VsZCBtZWFuICB0aGF0IGlmIHdlIGFkZGVkIHRoZSBpbnRlcnZhbCAgcGFja2V0ICBsb3Nz
DQo+PiByYXRlcyB0b2dldGhlciB0aGUgc3VtIG1heSAgbm90IG1hdGNoIHRoZSAgY3VtdWxhdGl2
ZSB2YWx1ZS4NCj4+IA0KPj4gQmVzdCAgICBSZWdhcmRzDQo+PiANCj4+IEFsYW4NCj4+IA0KPj4g
DQo+PiBPbiAxMS8yLzExIDM6MTEgQU0sICJRaW4gIFd1IiA8YmlsbC53dUBodWF3ZWkuY29tPiAg
ICB3cm90ZToNCj4+IA0KPj4gDQo+PiANCj4+IA0KPj4gDQo+PiANCj4+IEkgICB0ZW5kIHRvIGFn
cmVlIHdpdGggeW91LiBCdXQgSXQgIGxvb2tzIHRvIG1lDQo+PiBJbnRlcnZhbCBtZXRyaWMgYWxz
byAgY2FuIGJlIHVzZWQgIHRvICBjYWxjdWxhdGUgY3VtdWxhdGl2ZSBjaGFyYXN0ZXJ0aXN0aWNz
LiBUaGUgb25seSAgZGlmZmVyZW5jZSB0bw0KPj4gdGhlICBDdW11bGF0aXZlIG1ldHJpYyBpcyBv
bmUgaGFzIHNob3J0IGludGVydmFsLCBvbmUgIGhhcyAgbG9uZ2VyICBpbnRlcnZhbC4NCj4+IA0K
Pj4gQW0gSSByaWdodD8NCj4+IA0KPj4gDQo+PiANCj4+IE9yICAgIHNob3VsZCB3ZSB2aWV3ICBJ
bnRlcnZhbCBtZXRyaWMgYXMgYSBtZXRyaWMgdGhhdA0KPj4gaXMgIHVzZWQgdG8gIHJlcG9ydCBp
bnN0YW50IHZhbHVlIGF0IHRoZSBlbmQgIG9mIHRoZSBpbnRlcnZhbCAgc2V0IGZvciB0aGUgIGlu
dGVydmFsIG1ldHJpYz8gaW4gdGhhdA0KPj4gY2FzZSwgdGhlcmUgd2lsbCBiZSBubyAgIGRpZmZl
cmVuY2UgYmV0d2VlbiAgSWludGV2YWwgbWV0cmljIGFuZCBTYW1wbGVkICAgbWV0cmljLA0KPj4g
DQo+PiANCj4+IA0KPj4gT3Igc2hvdWxkICB3ZSB2aWV3IEludGVydmFsICBtZXRyaWMgYXMgYSBi
YXNpYyAgbWV0cmljDQo+PiB0aGF0IGNhbiBiZSBkaXJlY3RseSAgbWVhc3VyZWQgIGFuZCBjYWxj
dWxhdGVkIGFuZCBkb2VzIG5vdCByZWx5IG9uICBvdGhlciAgIG1ldHJpYy4NCj4+IA0KPj4gd2hp
Y2ggb25lIGlzIGNvcnJlY3Q/DQo+PiANCj4+IA0KPj4gDQo+PiBCZWZvcmUgICBhbnN3ZXJpbmcg
dGhpcyBxdWVzdGlvbiwgICBJIHRoaW5rDQo+PiBpbnRyb2R1Y2luZyBuZXcgdGVybSAgInNhbXBs
ZWQgbWV0cmljIiAgaXMgIHZlcnkgICAgY29uZnVzZWQuDQo+PiANCj4+IA0KPj4gDQo+PiBSZWdh
cmRzIQ0KPj4gDQo+PiAtUWluDQo+PiANCj4+IA0KPj4gDQo+PiANCj4+IA0KPj4gX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCj4+IA0KPj4g5Y+R5Lu25Lq6OiAgemhhb2ppbmdAc3R0
cmkuY29tLmNuIFt6aGFvamluZ0BzdHRyaS5jb20uY25dDQo+PiDlj5HpgIHml7bpl7Q6ICAgIDIw
MTHlubQxMeaciDLml6UgMTQ6NTkNCj4+IOWIsDogQWxhbiBDbGFyazsgUWluICBXdQ0KPj4gQ2M6
ICAgeHJibG9jaw0KPj4g5Li76aKYOiBSZTogUmU6IOetlOWkjTogIFt4cmJsb2NrXSBHZW5lcmFs
IGNvbW1lbnRzIG9uDQo+PiB4cmJsb2NrICBtZXRyaWNzICBkcmFmdHMNCj4+IA0KPj4gSSBrbm93
IHlvdSAgaW50ZW5kIHRvIHNlcGVyYXRlICBTYW1wbGVkIG1ldHJpYyBmcm9tDQo+PiBJbnRlcnZh
bCBNZXRyaWMuIEhvd2V2ZXIgIGFjY29yZGluZyAgdG8gdGhlIGRlZmludGlvbiBvZiBJbnRlcnZh
bCBtZXRyaWMgIGRlZmluaXRpb246DQo+PiAiDQo+PiBUaGUgSW50ZXJ2YWwgbWV0cmljIGlzIHJl
ZmVyZWQgdG8gYXMgdGhlIHJlcG9ydGVkDQo+PiB2YWx1ZXMgYXBwbHkgIHRvIHRoZSBtb3N0IHJl
Y2VudCBtZWFzdXJlbWVudA0KPj4gaW50ZXJ2YWwgZHVyYXRpb24gIGJldHdlZW4gIHN1Y2Nlc3Np
dmUgbWV0cmljcw0KPj4gcmVwb3J0cw0KPj4gIg0KPj4gSW4geW91ciB1bmRlcnN0YW5kaW5nLCB0
aGUgICBzYW1lcGxlZCAgbWV0cmljIGlzDQo+PiByZWZlcnJlZCB0byBhcyB0aGUgbWVhc3VyZWQg
dmFsdWUgaXMgc2FtcGxlZCBhdCAgdGhlICBlbmQgIG9mIGludGVydmFsIG9yIGFwcGx5IHRvIHRo
ZSBlbmQgb2YNCj4+IGludGVydmFsLg0KPj4gSXMgdGhhdCAgIHdoYXQgeW91IHNheT8NCj4+IEJ1
dCBJIGFtIG5vdCBjb252aW5jZWQuIEl0IGxvb2tzIHRvIG1lICB0aGUgIHNhbXBsZWQNCj4+IG1l
dHJpYyBjYW4gYmUgIGNsYXNzaWZpZWQgaW50byBjdW11bGF0aXZlICBtZXRyaWMuDQo+PiBUYWtl
ICBQUERWIGFzIGV4YW1wbGUsIHRoZSBKKGkpPSAgSihpLTEpKysgICh8RChpLQ0KPj4gMSxpKXwg
LSBKKGktMSkpLzE2DQo+PiBJc24ndCBKKGkpIGEgY3VtdWxhdGl2ZSBtZXRyaWMgIHNpbmNlICB0
aGUgSihpKSBpcyB0aGUNCj4+IGFjY3VtdWxhdGlvbiBwZXJpb2QgY2hhcmFjdGVyaXN0aWMgIHRo
YXQgY29tYmluZSAgIEooaS0xKSxKKGktMiksLi5KKDApDQo+PiBkdXJpbmcgY3VtdWxhdGl2ZSAg
ZHVyYXRpb24/DQo+PiBDaGVlcnMhDQo+PiBKaW5nDQo+PiAtLS0tLS0tLS0tLS0tLS0tLS0gIOWO
n+Wni+mCruS7tiAtLS0tLS0tLS0tLS0tLS0tLS0NCj4+IA0KPj4g5Y+R5Lu25Lq677yaQWxhbiBD
bGFyaw0KPj4g5pe244CA6Ze077yaMjAxMS8xMS8wMiAwNToyNTowMSDmmJ/mnJ/kuIkNCj4+IOaU
tuS7tuS6uu+8mnpoYW9qaW5nQHN0dHJpLmNvbS5jbiwgUWluICBXdQ0KPj4g5oqE6YCB5Lq677ya
eHJibG9jaw0KPj4g5Li744CA6aKY77yaUmU6IOetlOWkjTogW3hyYmxvY2tdIEdlbmVyYWwgIGNv
bW1lbnRzIG9uDQo+PiB4cmJsb2NrICBtZXRyaWNzIGRyYWZ0cw0KPj4gDQo+PiBKaW5nDQo+PiAN
Cj4+IEFuIEludGVydmFsIG1ldHJpYyBpcyBjYWxjdWxhdGVkICAgb3ZlciAgdGhlIGludGVydmFs
DQo+PiAtIHNvIHBhY2tldCBsb3NzIGZvciBhbiBpbnRlcnZhbCB3b3VsZCAgYmUgdGhlICBwYWNr
ZXRzIGxvc3QgIGR1cmluZyB0aGUgaW50ZXJ2YWwgZGl2aWRlZCBieSB0aGUNCj4+IG51bWJlciBv
ZiBwYWNrZXRzICBleHBlY3RlZC4NCj4+IA0KPj4gSWYgIHRoZSBwYWNrZXQgbG9zcyAgcmF0ZSB3
YXMgY29udGludW91c2x5ICBjYWxjdWxhdGVkDQo+PiBhcyBhIHJ1bm5pbmcgYXZlcmFnZSAgICh1
cGRhdGVkIHBlciBwYWNrZXQpIGFuZCB0aGUgdmFsdWUgIG9mIHRoaXMgcGFja2V0IGxvc3MgIHJh
dGUgbWV0cmljIHdhcw0KPj4gc2FtcGxlZCBhdCB0aGUgZW5kIG9mIHRoZSAgaW50ZXJ2YWwsIGl0
ICB3b3VsZCBiZSBhIHNhbXBsZWQgdmFsdWUgb2YgdGhlICBtZXRyaWMgYW5kIG5vdCB0aGUNCj4+
IGludGVydmFsIHZhbHVlLg0KPj4gDQo+PiBIZW5jZSB0aGVyZSBpcyBhIGRpZmZlcmVuY2UgICBi
ZXR3ZWVuIGFuICBpbnRlcnZhbA0KPj4gbWV0cmljIGFuZCBhIHNhbXBsZWQgbWV0cmljLCB3aGlj
aCAgSU1ITyBtZWFucyB0aGF0IHdlICAgc2hvdWxkIGhhdmUgYSB3YXkgdG8gc3RhdGUgdGhhdCBh
ICBtZXRyaWMgaXMNCj4+IEN1bXVsYXRpdmUsIEludGVydmFsICBvciAgU2FtcGxlZC4NCj4+IA0K
Pj4gQmVzdCAgUmVnYXJkcw0KPj4gDQo+PiBBbGFuDQo+PiANCj4+IA0KPj4gT24gMTEvMS8xMSAg
NDoyMSBBTSwgInpoYW9qaW5nQHN0dHJpLmNvbS5jbg0KPj4gPGh0dHA6Ly9jb3JwdzYud2VibWFp
bC4yMWNuLmNvbS93ZWJtYWlsL2pzcC9wZW50c2ltcGxlL2h0bWxFZGl0b3Ivemhhb2ppbmdAc3R0
cmkuY29tLmNuPiAgICAiDQo+PiA8emhhb2ppbmdAc3R0cmkuY29tLmNuDQo+PiA8aHR0cDovL2Nv
cnB3Ni53ZWJtYWlsLjIxY24uY29tL3dlYm1haWwvanNwL3BlbnRzaW1wbGUvaHRtbEVkaXRvci96
aGFvamluZ0BzdHRyaS5jb20uY24+ICAgID4gd3JvdGU6DQo+PiANCj4+IA0KPj4gDQo+PiANCj4+
IA0KPj4gDQo+PiANCj4+IA0KPj4gDQo+PiBBcmUgeW91IHNheWluZyB0aGUgc2FtcGxlICAgc2Vt
YW50aWNzICBoYXMgYWxyZWFkeSBiZWVuIGluY29ycG9yYXRlIGludG8gIEludGVydmFsL0N1bXVs
YXRpdmUNCj4+IGluZGljYXRpb24/DQo+PiANCj4+IA0KPj4gDQo+PiBDaGVlcnMhDQo+PiANCj4+
IEppbmcNCj4+IA0KPj4gLS0tLS0tLS0tLS0tLS0tLS0tIOWOn+Wni+mCruS7tiAgLS0tLS0tLS0t
LS0tLS0tLS0tDQo+PiANCj4+IOWPkeS7tuS6uu+8mlFpbiBXdQ0KPj4g5pe244CA6Ze077yaMjAx
MS8xMS8wMSAxNToxOTo1NCDmmJ/mnJ/kuowNCj4+IOaUtuS7tuS6uu+8mkFsYW4gIENsYXJrICwg
emhhb2ppbmdAc3R0cmkuY29tLmNuDQo+PiA8aHR0cDovL2NvcnB3Ni53ZWJtYWlsLjIxY24uY29t
L3dlYm1haWwvanNwL3BlbnRzaW1wbGUvaHRtbEVkaXRvci96aGFvamluZ0BzdHRyaS5jb20uY24+
DQo+PiDmioTpgIHkurrvvJp4cmJsb2NrDQo+PiDkuLvjgIDpopjvvJrnrZTlpI06IFt4cmJsb2Nr
XSBHZW5lcmFsICBjb21tZW50cyBvbiAgeHJibG9jayAgbWV0cmljcyBkcmFmdHMNCj4+IA0KPj4g
DQo+PiANCj4+IA0KPj4gDQo+PiANCj4+IEhpLCBBbGFuOg0KPj4gDQo+PiANCj4+IFNvIHRoZSAg
SW50ZXJ2YWwgICBtZXRyaWMgeW91IHVuZGVyc3RhbmQgaXMgZm9yIHBlciBSVFAgcGFja2V0ICBt
b25pdG9yaW5nIG9yICBvYnNlcnZhdGlvbg0KPj4gd2hpbGUgdGhlIHNhbXBsZWQgbWV0cmljIGlz
ICBub3QuDQo+PiBJbiBvdGhlciAgd29yZHMsDQo+PiBhLiBUaGUgSW50ZXJ2YWwgIG1ldHJpYyBp
cyAgb2J0YWluZWQgYnkga2VlcGluZyB0cmFjZSBvZiAgZWFjaCBSVFAgcGFja2V0IGR1cmluZyBh
ICBzcGVjaWZpZWQNCj4+IEludGVydmFsIGFuZCB0cmVhdCBhbGwgdGhlICBzZXF1ZW5jZSBudW1i
ZXIgIHZhbGlkLg0KPj4gYi5UaGUgc2FtcGxlZCBtZXRyaWMgIGlzIG9idGFpbmVkIGJ5ICBzYW1w
bGluZyAgYSBzdWIgc2V0IG9mIFJUUCBwYWNrZXRzIGR1cmluZyBhIHNwZWNpZmllZA0KPj4gSW50
ZXJ2YWwuDQo+PiBJcyB0aGF0IHdoYXQgeW91IHNheT8NCj4+IA0KPj4gDQo+PiANCj4+IA0KPj4g
DQo+PiBIb3dldmVyICAgIGFjY29yZGluZyB0byBQRFYgZHJhZnRzIGFuZCBvdGhlciBzaW1pbGFy
IHhyYmxvY2sgIG1ldHJpY3MgIGRyYWZ0cywgIHBlci1wYWNrZXQNCj4+IHN0YXRpc3RpY3MgZG9l
c24ndCBhcHBseSB0byAgdGhlc2UgbWV0cmljcyhTZWUgIHNlY3VyaXR5ICBjb25zaWRlcmF0aW9u
ICBzZWN0aW9uKS4NCj4+IA0KPj4gDQo+PiBUaGF0IHNlZW1zIHRvICBpbXBsaWNhdGUgdGhhdCBi
b3RoICAgSW50ZXJ2YWwgbWV0cmljcyBhbmQgY3VtdWxhdGl2ZSBtZXRyaWMgYXJlICBub3QgdXNl
ZCAgZm9yDQo+PiBwZXItcGFja2V0ICBhY2NvdW50aW5nIGJ1dCBmb3Igc2FtcGxpbmcgICAgdXNl
Lg0KPj4gDQo+PiANCj4+IA0KPj4gDQo+PiANCj4+IFJlZ2FyZHMhDQo+PiANCj4+IA0KPj4gLVFp
bg0KPj4gDQo+PiANCj4+IA0KPj4gDQo+PiANCj4+IA0KPj4gX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX18NCj4+IA0KPj4gDQo+PiDlj5Hku7bkuro6ICB4cmJsb2NrLWJvdW5jZXNAaWV0
Zi5vcmcNCj4+IDxodHRwOi8vY29ycHc2LndlYm1haWwuMjFjbi5jb20vd2VibWFpbC9qc3AvcGVu
dHNpbXBsZS9odG1sRWRpdG9yL3hyYmxvY2stYm91bmNlc0BpZXRmLm9yZz4NCj4+IFt4cmJsb2Nr
LWJvdW5jZXNAaWV0Zi5vcmcNCj4+IDxodHRwOi8vY29ycHc2LndlYm1haWwuMjFjbi5jb20vd2Vi
bWFpbC9qc3AvcGVudHNpbXBsZS9odG1sRWRpdG9yL3hyYmxvY2stYm91bmNlc0BpZXRmLm9yZz4g
ICAgXSDku6PooagNCj4+IEFsYW4gQ2xhcmsgW2FsYW4uZC5jbGFya0B0ZWxjaGVteS5jb20NCj4+
IDxodHRwOi8vY29ycHc2LndlYm1haWwuMjFjbi5jb20vd2VibWFpbC9qc3AvcGVudHNpbXBsZS9o
dG1sRWRpdG9yL2FsYW4uZC5jbGFya0B0ZWxjaGVteS5jb20+ICAgIF0NCj4+IOWPkemAgeaXtumX
tDogMjAxMeW5tDEw5pyIMzHml6UgMjA6MDgNCj4+IOWIsDogemhhb2ppbmdAc3R0cmkuY29tLmNu
DQo+PiA8aHR0cDovL2NvcnB3Ni53ZWJtYWlsLjIxY24uY29tL3dlYm1haWwvanNwL3BlbnRzaW1w
bGUvaHRtbEVkaXRvci96aGFvamluZ0BzdHRyaS5jb20uY24+DQo+PiBDYzogeHJibG9jaw0KPj4g
5Li76aKYOiBSZTogW3hyYmxvY2tdICBHZW5lcmFsICBjb21tZW50cyBvbiAgeHJibG9jayBtZXRy
aWNzICBkcmFmdHMNCj4+IA0KPj4gDQo+PiANCj4+IA0KPj4gDQo+PiBIaSAgSmluZw0KPj4gDQo+
PiBBbiBpbnRlcnZhbCBtZXRyaWMgIHNob3VsZCAgYmUgbWVhc3VyZWQgdGhyb3VnaG91dCBhbiBp
bnRlcnZhbCAgaG93ZXZlciBhICBzYW1wbGVkIG1ldHJpYyBpcyAgYW4NCj4+IGluc3RhbnRhbmVv
dXMgdmFsdWUuDQo+PiANCj4+IFVzaW5nICAgSml0dGVyL1BEViBhcyBhbiAgZXhhbXBsZToNCj4+
IA0KPj4gLSBJbnRlcnZhbCBQRFYgc2hvdWxkICBiZSBjYWxjdWxhdGVkIGJ5ICBtZWFzdXJpbmcg
IHRoZSBkZWxheSB2YXJpYXRpb24gb2YgZWFjaCAgcGFja2V0IGFuZA0KPj4gYXZlcmFnaW5nIHRo
ZXNlIG92ZXIgdGhlICAgaW50ZXJ2YWwuIFRoaXMgIHJlcXVpcmVzIHRoZSBpbXBsZW1lbnRhdGlv
biB0byBzdW0gdGhlIGluZGl2aWR1YWwNCj4+IG1lYXN1cmVtZW50cyBhbmQgZGl2aWRlIGJ5IHRo
ZSBudW1iZXIgb2YgIG1lYXN1cmVtZW50cy4NCj4+IA0KPj4gLSAgUFBEViAgKFJGQzM1NTApIGlz
IGNhbGN1bGF0ZWQgYnkgIGtlZXBpbmcgYSBydW5uaW5nIGF2ZXJhZ2Ugb2YgdGhlICBpbmRpdmlk
dWFsICBkZWxheQ0KPj4gdmFyaWF0aW9uIG1lYXN1cmVtZW50cyB1c2luZyBhIHNjYWxpbmcgZmFj
dG9yICBvZiAxNiBhbmQgdGhlbiAgIHJlcG9ydGluZyB0aGUgdmFsdWUgb2YgdGhpcyBydW5uaW5n
DQo+PiBhdmVyYWdlIGF0ICB0aGUgZW5kICBvZiB0aGUgaW50ZXJ2YWwuICBXaXRoIGEgc2NhbGlu
ZyBmYWN0b3Igb2YgMTYgdGhlIFBQRFYgICBtZXRyaWMgaXMgbW9zdCBzdHJvbmdseQ0KPj4gYWZm
ZWN0ZWQgYnkgIHRoZSBkZWxheSAgdmFyaWF0aW9uIG9mIHRoZSAgbW9zdCByZWNlbnQgMTAtMjAg
cGFja2V0cyBhbmQgaGVuY2UgaXMgbm90ICAgcmVwcmVzZW50YXRpdmUNCj4+IG9mIHRoZSAgd2hv
bGUgaW50ZXJ2YWwuDQo+PiANCj4+IEludGVydmFsICBhdmVyYWdlcyBjYW4gYmUgIHF1aXRlIG1p
c2xlYWRpbmcgIGlmIHRoZSBtZWFzdXJlbWVudHMgIGFyZSBzdHJvbmdseSB0aW1lIHZhcnlpbmcs
DQo+PiB3aGljaCBQRFYgICB0eXBpY2FsbHkgIGlzLg0KPj4gDQo+PiBCZXN0IFJlZ2FyZHMNCj4+
IA0KPj4gQWxhbg0KPj4gDQo+PiANCj4+IE9uICAxMC8zMS8xMSAgNToyMyAgQU0sICJ6aGFvamlu
Z0BzdHRyaS5jb20uY24NCj4+IDxodHRwOi8vY29ycHc2LndlYm1haWwuMjFjbi5jb20vd2VibWFp
bC9qc3AvcGVudHNpbXBsZS9odG1sRWRpdG9yL3poYW9qaW5nQHN0dHJpLmNvbS5jbj4NCj4+IDxo
dHRwczovL2ltYWlsLmh1YXdlaS5jb20vT1dBL1VybEJsb2NrZWRFcnJvci5hc3B4PiAgICAiIDx6
aGFvamluZ0BzdHRyaS5jb20uY24NCj4+IDxodHRwOi8vY29ycHc2LndlYm1haWwuMjFjbi5jb20v
d2VibWFpbC9qc3AvcGVudHNpbXBsZS9odG1sRWRpdG9yL3poYW9qaW5nQHN0dHJpLmNvbS5jbj4N
Cj4+IDxodHRwczovL2ltYWlsLmh1YXdlaS5jb20vT1dBL1VybEJsb2NrZWRFcnJvci5hc3B4PiAg
ICA+IHdyb3RlOg0KPj4gDQo+PiANCj4+IA0KPj4gDQo+PiANCj4+IA0KPj4gSGksIEFsYW46DQo+
PiANCj4+IFF1ZXN0aW9uIGZvciAgIGNsYXJpZmljYXRpb24uDQo+PiANCj4+IElzbid0IHRoZSBz
YW1wbGVkIG1ldHJpYyBzYW1lICBhcyB0aGUgIEludGVydmFsIG1ldHJpYz8gSXMgdGhlICBzYW1w
bGVkIG1ldHJpYyBvbmx5ICBhcHBsaWVkIHRvDQo+PiBwZXItcGFja2V0IHJlcG9ydGluZyA/IHdo
YXQncyB0aGUgICBkaWZmZXJlbmNlIGJldHdlZW4gc2FtcGxlZCAgbWV0cmljIGFuZCBub24tc2Ft
cGxlZCAgbWV0cmljPw0KPj4gDQo+PiB3aGF0J3MgIHRoZSBkaWZmZXJlbmNlICBiZXR3ZWVuICBz
YW1wbGVkIG1ldHJpYyBhbmQgSW50ZXJ2YWwgbWV0cmljPyBXb3VsZCB5b3UgIGxpa2UgdG8NCj4+
IGNsYXJpZnkgbW9yZT8NCj4+IA0KPj4gDQo+PiANCj4+IENoZWVycyENCj4+IA0KPj4gSmluZw0K
Pj4gDQo+PiAtLS0tLS0tLS0tLS0tLS0tLS0g5Y6f5aeL6YKu5Lu2IC0tLS0tLS0tLS0tLS0tLS0t
LQ0KPj4gDQo+PiDlj5Hku7bkurrvvJpBbGFuICBDbGFyaw0KPj4g5pe244CA6Ze077yaMjAxMS8x
MC8zMSAwNjo1MTowMyAg5pif5pyf5LiADQo+PiDmlLbku7bkurrvvJp4cmJsb2NrQGlldGYub3Jn
DQo+PiA8aHR0cDovL2NvcnB3Ni53ZWJtYWlsLjIxY24uY29tL3dlYm1haWwvanNwL3BlbnRzaW1w
bGUvaHRtbEVkaXRvci/mlLbku7bkurrvvJp4cmJsb2NrQGlldGYub3JnPg0KPj4gPGh0dHBzOi8v
aW1haWwuaHVhd2VpLmNvbS9PV0EvVXJsQmxvY2tlZEVycm9yLmFzcHg+DQo+PiDmioTpgIHkurrv
vJoNCj4+IOS4u+OAgOmimO+8mlt4cmJsb2NrXSBHZW5lcmFsIGNvbW1lbnRzIG9uICB4cmJsb2Nr
IG1ldHJpY3MgIGRyYWZ0cw0KPj4gDQo+PiANCj4+IDEuIEN1bXVsYXRpdmUsICBJbnRlcnZhbCBh
bmQgU2FtcGxlICBtZXRyaWNzDQo+PiBUaGUgZHJhZnRzICBjdXJyZW50ICBoYXZlIG9uZSBiaXQg
YXNzaWduZWQgZm9yICBDdW11bGF0aXZlL0ludGVydmFsICBpbmRpY2F0aW9uLi4uLiAgU29tZQ0K
Pj4gbWV0cmljcyBhcmUgaG93ZXZlciAgc2FtcGxlZCBhbmQgIGRvbuKAmXQgaGF2ZSB2YWxpZGl0
eSBmb3IgYW4gaW50ZXJ2YWwgIG9yIGEgICBjYWxsL3Nlc3Npb247IGFuIGV4YW1wbGUNCj4+IG9m
IHRoaXMgaXMgUFBEViwgd2hpY2ggaXMgYSAgc2FtcGxlZCB2YWx1ZSAgIG9mIGEgcnVubmluZyBh
dmVyYWdlIGFuZCBvbmx5IGhhcyAgdmFsaWRpdHkgZm9yIHRoZSBsYXN0DQo+PiAyMDAtMzAwbXMg
YmVmb3JlICB0aGUgdmFsdWUgaXMgIHNhbXBsZWQuDQo+PiBQcm9wb3NhbCAtIGluY3JlYXNlICB0
aGlzIHRvIHR3byBiaXRzIHRvIGFsbG93ICAgZm9yIHRoZSBpbmRpY2F0aW9uIG9mIGEgU2FtcGxl
ZCAgdmFsdWUuDQo+PiANCj4+IA0KPj4gDQo+PiANCj4+IA0KPj4gDQo+PiANCj4+IA0KPj4gDQo+
PiANCj4+IA0KPj4gDQo+PiANCj4+IA0KPj4gDQo+PiANCj4+IA0KPj4gDQo+PiANCj4+IA0KPj4g
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+IA0KPj4gDQo+PiANCj4+IF9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PiB4cmJsb2NrICBt
YWlsaW5nICAgbGlzdA0KPj4geHJibG9ja0BpZXRmLm9yZw0KPj4gaHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby94cmJsb2NrDQo+PiANCj4+IA0KPj4gDQo+PiANCj4+IA0KPj4g
DQo+PiANCj4+IA0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCj4geHJibG9jayBtYWlsaW5nIGxpc3QNCj4geHJibG9ja0BpZXRmLm9yZw0KPiBo
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3hyYmxvY2sNCj4NCg==

From magnus.westerlund@ericsson.com  Fri Nov 11 01:10:48 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3767C21F8888 for <avt@ietfa.amsl.com>; Fri, 11 Nov 2011 01:10:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.542
X-Spam-Level: 
X-Spam-Status: No, score=-106.542 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xkeayGSBOZ6h for <avt@ietfa.amsl.com>; Fri, 11 Nov 2011 01:10:44 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id D5E6521F886A for <avt@ietf.org>; Fri, 11 Nov 2011 01:10:43 -0800 (PST)
X-AuditID: c1b4fb39-b7b3eae00000252a-87-4ebce68b4751
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id AB.2B.09514.B86ECBE4; Fri, 11 Nov 2011 10:10:36 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.137.0; Fri, 11 Nov 2011 10:10:35 +0100
Message-ID: <4EBCE686.5050606@ericsson.com>
Date: Fri, 11 Nov 2011 10:10:30 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: IETF AVTCore WG <avt@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Subject: [AVTCORE] AVPF Timer behaviors and draft-lennox-rtcweb-rtp-media-type-mux-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 11 Nov 2011 09:10:48 -0000

Hi,

As I said in a previous email on feedback on Lennox's draft I had some 
views around the choice of Trr-int as 5.0. The below linked slide set 
does contain material for why I think 4.0 is more suitable.

http://www.denstore.se/IETF/AVPF-RTCP-Intervals.pptx

In determining these values I also found what can be considered a 
general issues with the AVPF suppression algorithm. If you have feedback 
on that issue please comment on this email. We unfortunately have time 
to take it up in the AVTCORE WG meeting this time. But I gladly discuss 
it in the corridor.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------



From magnus.westerlund@ericsson.com  Fri Nov 11 01:20:10 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72B5C21F899D for <avt@ietfa.amsl.com>; Fri, 11 Nov 2011 01:20:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.543
X-Spam-Level: 
X-Spam-Status: No, score=-106.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LuqSOlraT88R for <avt@ietfa.amsl.com>; Fri, 11 Nov 2011 01:20:09 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 70CF721F84A5 for <avt@ietf.org>; Fri, 11 Nov 2011 01:20:09 -0800 (PST)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-54-4ebce8c86e74
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id C5.53.13753.8C8ECBE4; Fri, 11 Nov 2011 10:20:08 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.137.0; Fri, 11 Nov 2011 10:20:08 +0100
Message-ID: <4EBCE8C4.1060703@ericsson.com>
Date: Fri, 11 Nov 2011 10:20:04 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Jonathan Lennox <jonathan@vidyo.com>
References: <4EB7B054.3000706@ericsson.com> <4EB7B4D8.5050003@alvestrand.no> <4EBBADD5.4020501@ericsson.com> <4EBBC481.5010504@alvestrand.no> <4EBBE238.20103@ericsson.com> <C3759687E4991243A1A0BD44EAC823034C42D486BF@BE235.mail.lan>
In-Reply-To: <C3759687E4991243A1A0BD44EAC823034C42D486BF@BE235.mail.lan>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: Harald Alvestrand <harald@alvestrand.no>, Jonathan Rosenberg <jonathan.rosenberg@skype.net>, IETF AVTCore WG <avt@ietf.org>
Subject: [AVTCORE] Offer/Answer and Transport Translators was: Re: Comments on draft-lennox-rtcweb-rtp-media-type-mux-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 11 Nov 2011 09:20:10 -0000

On 2011-11-10 17:02, Jonathan Lennox wrote:
> (I'm cutting down this conversation heavily, to respond to just one
> point...)
>
> Magnus Westerlund wrote:
>
>> - If it is non mixing entity like an RTP mixer that switches media
>> streams, i.e. sends them out using the Mixer's SSRCs. Then you
>> still have the decryption and encryption cycle even if the media
>> mixing, encoding and decoding goes away. So this is clearly less
>> complex, but still more heavy than just forward the packet.]
>
> I think, in practice, that an RTP mixer *inevitably* has to have at
> least this capability, and a pure transport translator is impossible
> for multipoint conferences, assuming that the endpoints' sessions
> with the central point are negotiated by SDP offer/answer.

I would disagree with you here. I think it is very much possible. Yes 
the PT picking is an issue, but if the translator is the inviting party 
and the responder doesn't renumber it will work. Having the translator 
or application server start the media invite is actually easier in the 
WebRTC context, than it is in normal SIP, as there you likely need to 
accept an initial invite from the client and then re-offer from the 
server to get things correct.

The renumbering of payload is introduced because of something in the H. 
suite, is it really commonly happening?

> Additionally, both SDES and DTLS keying negotiate keys
> point-to-point, and offer/answer allows endpoints to pick their own
> b= receive bandwidth, which means different RTCP timings.  Both of
> these can be worked around to some extent (SRTP EKT is almost done,
> and having minorly-inconsistent RTCP timings is usually harmless),
> but it's not clear how much point there is to working around these
> issues, given the first one.

This I agree is the other hazzle, but with EKT we do resolve it. And the 
transport translators only task beyond forwarding media in such a 
session will be to inject keys from the other legs towards each end-point.

>
> In practice, though, decryption and re-encryption isn't that
> expensive, particularly on modern CPUs with built-in crypto
> accelerators.  It's certainly tiny compared to the cost of media
> transcoding.

I agree it is tiny to transcoding. But is not tiny in comparision to 
packet forwarding.

>
>
> Thus, I think trying to design an architecture that makes
> pure-transport translation possible is a lost cause, if your primary
> use cases are offer/answer based, and so there's no point in creating
> new mechanisms in an attempt to support it.

We are definitely disagreeing on this point.

>
> Unless I'm missing something, SHIM falls in this category -- the
> benefits of SHIM over single-session muxing are largely for transport
> translation.
>

Not at all. It benefits any usage where you want to have an additional 
demultiplexing point based on purpose. The alternative is to classify 
each and every SSRC into a role, then process them differently in any 
node. That is under the assumption you want to avoid multiple transport 
flows.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From harald@alvestrand.no  Fri Nov 11 01:32:47 2011
Return-Path: <harald@alvestrand.no>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0219221F8726 for <avt@ietfa.amsl.com>; Fri, 11 Nov 2011 01:32:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.543
X-Spam-Level: 
X-Spam-Status: No, score=-110.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iISdEZPArAec for <avt@ietfa.amsl.com>; Fri, 11 Nov 2011 01:32:43 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id C00EC21F86FF for <avt@ietf.org>; Fri, 11 Nov 2011 01:32:42 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 184B739E12F; Fri, 11 Nov 2011 10:32:42 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3bjrmEXcAl03; Fri, 11 Nov 2011 10:32:37 +0100 (CET)
Received: from hta-dell.lul.corp.google.com (62-20-124-50.customer.telia.com [62.20.124.50]) by eikenes.alvestrand.no (Postfix) with ESMTPS id C3BF139E048; Fri, 11 Nov 2011 10:32:37 +0100 (CET)
Message-ID: <4EBCEBB5.2040403@alvestrand.no>
Date: Fri, 11 Nov 2011 10:32:37 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <4EB7B054.3000706@ericsson.com> <4EB7B4D8.5050003@alvestrand.no> <4EBBADD5.4020501@ericsson.com> <4EBBC481.5010504@alvestrand.no> <4EBBE238.20103@ericsson.com>
In-Reply-To: <4EBBE238.20103@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Jonathan Lennox <jonathan@vidyo.com>, Jonathan Rosenberg <jonathan.rosenberg@skype.net>, IETF AVTCore WG <avt@ietf.org>
Subject: Re: [AVTCORE] Comments on draft-lennox-rtcweb-rtp-media-type-mux-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 11 Nov 2011 09:32:47 -0000

On 11/10/2011 03:39 PM, Magnus Westerlund wrote:
>>
>> Still, I think we may be talking about CPU time per packet well below a
>> millisecond for the middle case.
>
> Yes, but if your goal for how many streams a single media range server 
> should handle is in the region of 100000 or more, then it does matter.

Hm. 100.000 streams of audio at 50 pps is 5 Mpps.
At average packet size 128 bytes, this is 640 Mbytes/sec, or 5 Gbits/sec.

You need 6 cores equivalent to Eric Rescorla's Macbook Air (which 
encrypts on the order of 100 MB/s, no hardware encryption support) to 
handle encryption of those streams.

Or two Altera AES cores 
(http://www.altera.com/products/ip/dsp/encryption_decryption/m-dcr-aes_enc.html).

Yes, it does matter. Somewhat.


From csp@csperkins.org  Sun Nov 13 08:04:56 2011
Return-Path: <csp@csperkins.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BD3921F8B0D; Sun, 13 Nov 2011 08:04:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pl5pyTqUfgCE; Sun, 13 Nov 2011 08:04:55 -0800 (PST)
Received: from anchor-msapost-2.mail.demon.net (anchor-msapost-2.mail.demon.net [195.173.77.165]) by ietfa.amsl.com (Postfix) with ESMTP id 1C77A21F8B08; Sun, 13 Nov 2011 08:04:55 -0800 (PST)
Received: from dhcp-4355.meeting.ietf.org ([130.129.67.85]) by anchor-post-2.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1RPcYB-0005yP-jH; Sun, 13 Nov 2011 16:04:55 +0000
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=windows-1252
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <0B68D2E0-3480-47FB-8427-4032FD7B18F6@vidyo.com>
Date: Mon, 14 Nov 2011 00:04:48 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <C0CDA262-3B5E-4BD5-8B67-EA399136D98B@csperkins.org>
References: <20111024232740.11885.97235.idtracker@ietfa.amsl.com> <C66DE732-1C39-4AB6-A7E0-A4CF687BB0D8@vidyo.com> <462F77C3-8CAD-4699-9238-71B5C9EF7F9B@csperkins.org> <0B68D2E0-3480-47FB-8427-4032FD7B18F6@vidyo.com>
To: Jonathan Lennox <jonathan@vidyo.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, IETF AVTCore WG <avt@ietf.org>
Subject: Re: [AVTCORE] [rtcweb] I-D Action: draft-lennox-rtcweb-rtp-media-type-mux-00.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 13 Nov 2011 16:04:56 -0000

Jonathan,

A more compelling argument for reporting from all SSRCs may be that =
various AVPF and RTCP XR packets make no sense unless sent from the SSRC =
corresponding to the correct media type. Sending just those, but not =
regular RTCP reports, will cause havoc to the RTCP participant timeout =
rules, and SSRC collision detection, unless you signal and heavily =
special-case the code. This doesn't seem worth it, for tiny bandwidth =
savings.

Reporting on yourself is harder to defend, I agree, but the potential to =
confuse monitoring equipment (and given the activity in XRBLOCK, someone =
must care about that=85), and the additional signalling needed, again =
seem to outweigh the bandwidth cost.

Colin



On 27 Oct 2011, at 23:57, Jonathan Lennox wrote:
> Hi, Colin --
>=20
> Thanks for taking a look my draft!
>=20
> I saw this recommendation in the multiplex-architecture draft, after I =
finished my own (I didn't get a chance to read any other -00 drafts =
before finishing my own before the deadline).
>=20
> I think this is an AVTCore issue, so I'm following up there...further =
discussion should probably just be on AVTCore, unless there are =
WebRTC-specific issues.
>=20
>=20
> The multiplexing-architecture draft in general is a very good draft -- =
it's extremely thorough and useful -- but I admit to not being very =
convinced by that section of it.
>=20
> At small numbers of sources, self-reporting and cross-reporting does =
indeed use a fairly small amount of bandwidth, but the problem is that =
their bandwidth usage is quadratic in the number of sources, since every =
source must report on every other. So as the number of sources grows, =
they begin to consume all RTCP bandwidth sending redundant or trivial =
information.
>=20
> And this for the sake of third-party monitors, which (personally) I've =
never seen deployed outside a research environment, and seem =
architecturally dubious to me, at least for offer-answer negotiated =
streams. (IPTV and other declarative-SDP architectures are probably =
different.)
>=20
> On Oct 27, 2011, at 11:12 AM, Colin Perkins wrote:
>=20
>> Jonathan,
>>=20
>> Thanks for submitting. This is a good draft.
>>=20
>> One comment: Section 3.1 suggests that a source generating multiple =
RTP streams, with multiple SSRCs, should not send RTCP reports for its =
own media, and should pick a single SSRC to use when sending reports on =
other media. I agree that this would save a small amount of bandwidth, =
but I think the savings are negligible, it complicates the monitoring =
model, and so is a mistake. We talk about this in =
draft-westerlund-avtcore-multiplex-architecture-00 (Section 9, in =
particular).
>>=20
>> Cheers,
>> Colin
>=20
> --
> Jonathan Lennox
> jonathan@vidyo.com
>=20
>=20
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb



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




From jonathan@vidyo.com  Sun Nov 13 13:17:22 2011
Return-Path: <jonathan@vidyo.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54A5021F86AA; Sun, 13 Nov 2011 13:17:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level: 
X-Spam-Status: No, score=-2.439 tagged_above=-999 required=5 tests=[AWL=0.160,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ngfromaUYmvO; Sun, 13 Nov 2011 13:17:21 -0800 (PST)
Received: from mxout.myoutlookonline.com (mxout.myoutlookonline.com [64.95.72.241]) by ietfa.amsl.com (Postfix) with ESMTP id 738A321F86A6; Sun, 13 Nov 2011 13:17:21 -0800 (PST)
Received: from mxout.myoutlookonline.com (localhost [127.0.0.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id C09E27A2D0A; Sun, 13 Nov 2011 16:17:16 -0500 (EST)
X-Virus-Scanned: by SpamTitan at mail.lan
Received: from HUB016.mail.lan (unknown [10.110.2.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id 49E4E7A2D34; Sun, 13 Nov 2011 16:17:16 -0500 (EST)
Received: from BE235.mail.lan ([10.110.32.235]) by HUB016.mail.lan ([10.110.17.16]) with mapi; Sun, 13 Nov 2011 16:17:15 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: Colin Perkins <csp@csperkins.org>
Date: Sun, 13 Nov 2011 16:17:13 -0500
Thread-Topic: [rtcweb] I-D Action: draft-lennox-rtcweb-rtp-media-type-mux-00.txt
Thread-Index: AcyiHfyR6IKAmjCsQHKJtY3bzl7hTQAKqtYg
Message-ID: <C3759687E4991243A1A0BD44EAC823034C439A3493@BE235.mail.lan>
References: <20111024232740.11885.97235.idtracker@ietfa.amsl.com> <C66DE732-1C39-4AB6-A7E0-A4CF687BB0D8@vidyo.com> <462F77C3-8CAD-4699-9238-71B5C9EF7F9B@csperkins.org> <0B68D2E0-3480-47FB-8427-4032FD7B18F6@vidyo.com> <C0CDA262-3B5E-4BD5-8B67-EA399136D98B@csperkins.org>
In-Reply-To: <C0CDA262-3B5E-4BD5-8B67-EA399136D98B@csperkins.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, IETF AVTCore WG <avt@ietf.org>
Subject: Re: [AVTCORE] [rtcweb] I-D Action: draft-lennox-rtcweb-rtp-media-type-mux-00.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 13 Nov 2011 21:17:22 -0000

Colin,

I believe this would work under the logic I describe in media-type-mux: you=
 still send RR or SR packets for every source, you just treat your sources =
other than the reporting source as though they're "disconnected" receivers,=
 i.e. don't include redundant reports in their SRs/RRs.

The number of SR/RR packets is linear in the number of sources in a session=
 -- it's the number of reports that's quadratic, and thus problematic.

If there's a need for some XR reports to choose a reporting source that has=
 the same media type as the source being reported on, that should be fine.

-----Original Message-----
From: Colin Perkins [mailto:csp@csperkins.org]=20
Sent: Monday, November 14, 2011 12:05 AM
To: Jonathan Lennox
Cc: rtcweb@ietf.org; IETF AVTCore WG
Subject: Re: [rtcweb] I-D Action: draft-lennox-rtcweb-rtp-media-type-mux-00=
.txt

Jonathan,

A more compelling argument for reporting from all SSRCs may be that various=
 AVPF and RTCP XR packets make no sense unless sent from the SSRC correspon=
ding to the correct media type. Sending just those, but not regular RTCP re=
ports, will cause havoc to the RTCP participant timeout rules, and SSRC col=
lision detection, unless you signal and heavily special-case the code. This=
 doesn't seem worth it, for tiny bandwidth savings.

Reporting on yourself is harder to defend, I agree, but the potential to co=
nfuse monitoring equipment (and given the activity in XRBLOCK, someone must=
 care about that...), and the additional signalling needed, again seem to o=
utweigh the bandwidth cost.

Colin



On 27 Oct 2011, at 23:57, Jonathan Lennox wrote:
> Hi, Colin --
>=20
> Thanks for taking a look my draft!
>=20
> I saw this recommendation in the multiplex-architecture draft, after I fi=
nished my own (I didn't get a chance to read any other -00 drafts before fi=
nishing my own before the deadline).
>=20
> I think this is an AVTCore issue, so I'm following up there...further dis=
cussion should probably just be on AVTCore, unless there are WebRTC-specifi=
c issues.
>=20
>=20
> The multiplexing-architecture draft in general is a very good draft -- it=
's extremely thorough and useful -- but I admit to not being very convinced=
 by that section of it.
>=20
> At small numbers of sources, self-reporting and cross-reporting does inde=
ed use a fairly small amount of bandwidth, but the problem is that their ba=
ndwidth usage is quadratic in the number of sources, since every source mus=
t report on every other. So as the number of sources grows, they begin to c=
onsume all RTCP bandwidth sending redundant or trivial information.
>=20
> And this for the sake of third-party monitors, which (personally) I've ne=
ver seen deployed outside a research environment, and seem architecturally =
dubious to me, at least for offer-answer negotiated streams. (IPTV and othe=
r declarative-SDP architectures are probably different.)
>=20
> On Oct 27, 2011, at 11:12 AM, Colin Perkins wrote:
>=20
>> Jonathan,
>>=20
>> Thanks for submitting. This is a good draft.
>>=20
>> One comment: Section 3.1 suggests that a source generating multiple RTP =
streams, with multiple SSRCs, should not send RTCP reports for its own medi=
a, and should pick a single SSRC to use when sending reports on other media=
. I agree that this would save a small amount of bandwidth, but I think the=
 savings are negligible, it complicates the monitoring model, and so is a m=
istake. We talk about this in draft-westerlund-avtcore-multiplex-architectu=
re-00 (Section 9, in particular).
>>=20
>> Cheers,
>> Colin
>=20
> --
> Jonathan Lennox
> jonathan@vidyo.com
>=20
>=20
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb



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




From internet-drafts@ietf.org  Sun Nov 13 16:26:50 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F4BD21F8444; Sun, 13 Nov 2011 16:26:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.48
X-Spam-Level: 
X-Spam-Status: No, score=-102.48 tagged_above=-999 required=5 tests=[AWL=0.119, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s27r5AcJI3YN; Sun, 13 Nov 2011 16:26:49 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 217EB11E8073; Sun, 13 Nov 2011 16:26:47 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.63
Message-ID: <20111114002647.19680.14547.idtracker@ietfa.amsl.com>
Date: Sun, 13 Nov 2011 16:26:47 -0800
Cc: avt@ietf.org
Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-06.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 Nov 2011 00:26:50 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Audio/Video Transport Core Maintenanc=
e Working Group of the IETF.

	Title           : Monitoring Architectures for RTP
	Author(s)       : Qin Wu
                          Geoff Hunt
                          Philip Arden
	Filename        : draft-ietf-avtcore-monarch-06.txt
	Pages           : 25
	Date            : 2011-11-13

   This memo proposes an architecture for extending RTCP with a new RTCP
   XR (RFC3611) block type to report new metrics regarding media
   transmission or reception quality, following RTCP guideline
   established in RFC5968.  This memo suggests that a new block should
   contain a single metric or a small number of metrics relevant to a
   single parameter of interest or concern, rather than containing a
   number of metrics which attempt to provide full coverage of all those
   parameters of concern to a specific application.  Applications may
   then &quot;mix and match&quot; to create a set of blocks which covers th=
eir set
   of concerns.  Where possible, a specific block should be designed to
   be re-usable across more than one application, for example, for all
   of voice, streaming audio and video.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-06.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-06.txt

From bill.wu@huawei.com  Sun Nov 13 18:05:48 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C853711E8119 for <avt@ietfa.amsl.com>; Sun, 13 Nov 2011 18:05:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.616
X-Spam-Level: 
X-Spam-Status: No, score=-0.616 tagged_above=-999 required=5 tests=[AWL=-3.065, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fEs1GmHEdfLF for <avt@ietfa.amsl.com>; Sun, 13 Nov 2011 18:05:48 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id CACE311E808E for <avt@ietf.org>; Sun, 13 Nov 2011 18:05:47 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUM00NEZOHM0M@szxga04-in.huawei.com> for avt@ietf.org; Mon, 14 Nov 2011 10:05:46 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUM0049TOHMXK@szxga04-in.huawei.com> for avt@ietf.org; Mon, 14 Nov 2011 10:05:46 +0800 (CST)
Received: from szxeml208-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFA20136; Mon, 14 Nov 2011 10:05:46 +0800
Received: from SZXEML410-HUB.china.huawei.com (10.82.67.137) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 14 Nov 2011 10:05:44 +0800
Received: from SZXEML523-MBS.china.huawei.com ([169.254.6.67]) by szxeml410-hub.china.huawei.com ([10.82.67.137]) with mapi id 14.01.0323.003; Mon, 14 Nov 2011 10:05:37 +0800
Date: Mon, 14 Nov 2011 02:05:37 +0000
From: Qin Wu <bill.wu@huawei.com>
In-reply-to: <20111114002647.19680.14547.idtracker@ietfa.amsl.com>
X-Originating-IP: [172.24.2.41]
To: "avt@ietf.org" <avt@ietf.org>
Message-id: <B8F9A780D330094D99AF023C5877DABA3338A2@szxeml523-mbs.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=gb2312
Content-language: zh-CN
Content-transfer-encoding: base64
Accept-Language: zh-CN, en-US
Thread-topic: I-D Action: draft-ietf-avtcore-monarch-06.txt
Thread-index: AQHMomQlgYg5GwZpqEWyT0P+dDCZN5WrnRG+
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <20111114002647.19680.14547.idtracker@ietfa.amsl.com>
Subject: [AVTCORE] =?gb2312?b?tPC4tDogSS1EIEFjdGlvbjogZHJhZnQtaWV0Zi1hdnRj?= =?gb2312?b?b3JlLW1vbmFyY2gtMDYudHh0?=
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 Nov 2011 02:05:48 -0000

SGksIEZvbGtzOg0KV2UgaGF2ZSBqdXN0IHN1Ym1pdHRlZCBhIG5ldyB2ZXJzaW9uIG9mIG1vbmFy
Y2ggZG9jdW1lbnQuDQpodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1p
ZXRmLWF2dGNvcmUtbW9uYXJjaC0wNi50eHQNCg0KIFdlIHRhbGsgd2l0aCBjaGFpcnMgYW5kIHRo
aW5rIGl0IGhhcyBiZWVuIHJlYWR5IGZvciBXR0xDLg0KQ2hhaXJzLCB3b3VsZCB5b3UgbGlrZSB0
byB1c2UgdGhpcyB2ZXJzaW9uIGFzIGJhc2VsaW5lIHRvIHJhaXNlIFdHTEM/DQoNCg0KUmVnYXJk
cyENCi1RaW4NCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0Kt6K8/sjL
OiBpLWQtYW5ub3VuY2UtYm91bmNlc0BpZXRmLm9yZyBbaS1kLWFubm91bmNlLWJvdW5jZXNAaWV0
Zi5vcmddILT6se0gaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIFtpbnRlcm5ldC1kcmFmdHNAaWV0
Zi5vcmddDQq3osvNyrG85DogMjAxMcTqMTHUwjE0yNUgODoyNg0Ktb06IGktZC1hbm5vdW5jZUBp
ZXRmLm9yZw0KQ2M6IGF2dEBpZXRmLm9yZw0K1vfM4jogSS1EIEFjdGlvbjogZHJhZnQtaWV0Zi1h
dnRjb3JlLW1vbmFyY2gtMDYudHh0DQoNCkEgTmV3IEludGVybmV0LURyYWZ0IGlzIGF2YWlsYWJs
ZSBmcm9tIHRoZSBvbi1saW5lIEludGVybmV0LURyYWZ0cyBkaXJlY3Rvcmllcy4gVGhpcyBkcmFm
dCBpcyBhIHdvcmsgaXRlbSBvZiB0aGUgQXVkaW8vVmlkZW8gVHJhbnNwb3J0IENvcmUgTWFpbnRl
bmFuY2UgV29ya2luZyBHcm91cCBvZiB0aGUgSUVURi4NCg0KICAgICAgICBUaXRsZSAgICAgICAg
ICAgOiBNb25pdG9yaW5nIEFyY2hpdGVjdHVyZXMgZm9yIFJUUA0KICAgICAgICBBdXRob3Iocykg
ICAgICAgOiBRaW4gV3UNCiAgICAgICAgICAgICAgICAgICAgICAgICAgR2VvZmYgSHVudA0KICAg
ICAgICAgICAgICAgICAgICAgICAgICBQaGlsaXAgQXJkZW4NCiAgICAgICAgRmlsZW5hbWUgICAg
ICAgIDogZHJhZnQtaWV0Zi1hdnRjb3JlLW1vbmFyY2gtMDYudHh0DQogICAgICAgIFBhZ2VzICAg
ICAgICAgICA6IDI1DQogICAgICAgIERhdGUgICAgICAgICAgICA6IDIwMTEtMTEtMTMNCg0KICAg
VGhpcyBtZW1vIHByb3Bvc2VzIGFuIGFyY2hpdGVjdHVyZSBmb3IgZXh0ZW5kaW5nIFJUQ1Agd2l0
aCBhIG5ldyBSVENQDQogICBYUiAoUkZDMzYxMSkgYmxvY2sgdHlwZSB0byByZXBvcnQgbmV3IG1l
dHJpY3MgcmVnYXJkaW5nIG1lZGlhDQogICB0cmFuc21pc3Npb24gb3IgcmVjZXB0aW9uIHF1YWxp
dHksIGZvbGxvd2luZyBSVENQIGd1aWRlbGluZQ0KICAgZXN0YWJsaXNoZWQgaW4gUkZDNTk2OC4g
IFRoaXMgbWVtbyBzdWdnZXN0cyB0aGF0IGEgbmV3IGJsb2NrIHNob3VsZA0KICAgY29udGFpbiBh
IHNpbmdsZSBtZXRyaWMgb3IgYSBzbWFsbCBudW1iZXIgb2YgbWV0cmljcyByZWxldmFudCB0byBh
DQogICBzaW5nbGUgcGFyYW1ldGVyIG9mIGludGVyZXN0IG9yIGNvbmNlcm4sIHJhdGhlciB0aGFu
IGNvbnRhaW5pbmcgYQ0KICAgbnVtYmVyIG9mIG1ldHJpY3Mgd2hpY2ggYXR0ZW1wdCB0byBwcm92
aWRlIGZ1bGwgY292ZXJhZ2Ugb2YgYWxsIHRob3NlDQogICBwYXJhbWV0ZXJzIG9mIGNvbmNlcm4g
dG8gYSBzcGVjaWZpYyBhcHBsaWNhdGlvbi4gIEFwcGxpY2F0aW9ucyBtYXkNCiAgIHRoZW4gJnF1
b3Q7bWl4IGFuZCBtYXRjaCZxdW90OyB0byBjcmVhdGUgYSBzZXQgb2YgYmxvY2tzIHdoaWNoIGNv
dmVycyB0aGVpciBzZXQNCiAgIG9mIGNvbmNlcm5zLiAgV2hlcmUgcG9zc2libGUsIGEgc3BlY2lm
aWMgYmxvY2sgc2hvdWxkIGJlIGRlc2lnbmVkIHRvDQogICBiZSByZS11c2FibGUgYWNyb3NzIG1v
cmUgdGhhbiBvbmUgYXBwbGljYXRpb24sIGZvciBleGFtcGxlLCBmb3IgYWxsDQogICBvZiB2b2lj
ZSwgc3RyZWFtaW5nIGF1ZGlvIGFuZCB2aWRlby4NCg0KDQpBIFVSTCBmb3IgdGhpcyBJbnRlcm5l
dC1EcmFmdCBpczoNCmh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWll
dGYtYXZ0Y29yZS1tb25hcmNoLTA2LnR4dA0KDQpJbnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZh
aWxhYmxlIGJ5IGFub255bW91cyBGVFAgYXQ6DQpmdHA6Ly9mdHAuaWV0Zi5vcmcvaW50ZXJuZXQt
ZHJhZnRzLw0KDQpUaGlzIEludGVybmV0LURyYWZ0IGNhbiBiZSByZXRyaWV2ZWQgYXQ6DQpmdHA6
Ly9mdHAuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWlldGYtYXZ0Y29yZS1tb25hcmNo
LTA2LnR4dA0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
CkktRC1Bbm5vdW5jZSBtYWlsaW5nIGxpc3QNCkktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KaHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pLWQtYW5ub3VuY2UNCkludGVybmV0LURy
YWZ0IGRpcmVjdG9yaWVzOiBodHRwOi8vd3d3LmlldGYub3JnL3NoYWRvdy5odG1sDQpvciBmdHA6
Ly9mdHAuaWV0Zi5vcmcvaWV0Zi8xc2hhZG93LXNpdGVzLnR4dA==

From harald@alvestrand.no  Sun Nov 13 19:33:06 2011
Return-Path: <harald@alvestrand.no>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4BCD11E8160 for <avt@ietfa.amsl.com>; Sun, 13 Nov 2011 19:33:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.799
X-Spam-Level: 
X-Spam-Status: No, score=-109.799 tagged_above=-999 required=5 tests=[AWL=0.800, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JxD83RGhUvmb for <avt@ietfa.amsl.com>; Sun, 13 Nov 2011 19:33:06 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id CD20B11E80AE for <avt@ietf.org>; Sun, 13 Nov 2011 19:33:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 04F8B39E091; Mon, 14 Nov 2011 04:33:04 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lt+DmgS2ZPxJ; Mon, 14 Nov 2011 04:33:03 +0100 (CET)
Received: from [172.30.56.125] (unknown [72.14.229.161]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 72EC639E082; Mon, 14 Nov 2011 04:33:01 +0100 (CET)
Message-ID: <4EC08BEA.0@alvestrand.no>
Date: Mon, 14 Nov 2011 11:32:58 +0800
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <4EB7B054.3000706@ericsson.com> <4EB7B4D8.5050003@alvestrand.no> <4EBBADD5.4020501@ericsson.com> <4EBBC481.5010504@alvestrand.no> <4EBBE238.20103@ericsson.com> <C3759687E4991243A1A0BD44EAC823034C42D486BF@BE235.mail.lan> <4EBCE8C4.1060703@ericsson.com>
In-Reply-To: <4EBCE8C4.1060703@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Jonathan Lennox <jonathan@vidyo.com>, Jonathan Rosenberg <jonathan.rosenberg@skype.net>, IETF AVTCore WG <avt@ietf.org>
Subject: Re: [AVTCORE] Offer/Answer and Transport Translators was: Re: Comments on draft-lennox-rtcweb-rtp-media-type-mux-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 Nov 2011 03:33:06 -0000

I think this discussion shows pretty clearly that a pure RTP mixer (one 
that just forwards packets, and does not process any of them) is 
functionally equivalent to a multicast group.

I used to think that offer/answer was completely useless for negotiating 
media for multicast groups, but I think now that Magnus' comments seem 
to show how one can use offer/answer for that as long as a central node 
does all the offering.

On 11/11/2011 05:20 PM, Magnus Westerlund wrote:
> On 2011-11-10 17:02, Jonathan Lennox wrote:
>> (I'm cutting down this conversation heavily, to respond to just one
>> point...)
>>
>> Magnus Westerlund wrote:
>>
>>> - If it is non mixing entity like an RTP mixer that switches media
>>> streams, i.e. sends them out using the Mixer's SSRCs. Then you
>>> still have the decryption and encryption cycle even if the media
>>> mixing, encoding and decoding goes away. So this is clearly less
>>> complex, but still more heavy than just forward the packet.]
>>
>> I think, in practice, that an RTP mixer *inevitably* has to have at
>> least this capability, and a pure transport translator is impossible
>> for multipoint conferences, assuming that the endpoints' sessions
>> with the central point are negotiated by SDP offer/answer.
>
> I would disagree with you here. I think it is very much possible. Yes 
> the PT picking is an issue, but if the translator is the inviting 
> party and the responder doesn't renumber it will work. Having the 
> translator or application server start the media invite is actually 
> easier in the WebRTC context, than it is in normal SIP, as there you 
> likely need to accept an initial invite from the client and then 
> re-offer from the server to get things correct.
>
> The renumbering of payload is introduced because of something in the 
> H. suite, is it really commonly happening?
>
>> Additionally, both SDES and DTLS keying negotiate keys
>> point-to-point, and offer/answer allows endpoints to pick their own
>> b= receive bandwidth, which means different RTCP timings.  Both of
>> these can be worked around to some extent (SRTP EKT is almost done,
>> and having minorly-inconsistent RTCP timings is usually harmless),
>> but it's not clear how much point there is to working around these
>> issues, given the first one.
>
> This I agree is the other hazzle, but with EKT we do resolve it. And 
> the transport translators only task beyond forwarding media in such a 
> session will be to inject keys from the other legs towards each 
> end-point.
>
>>
>> In practice, though, decryption and re-encryption isn't that
>> expensive, particularly on modern CPUs with built-in crypto
>> accelerators.  It's certainly tiny compared to the cost of media
>> transcoding.
>
> I agree it is tiny to transcoding. But is not tiny in comparision to 
> packet forwarding.
>
>>
>>
>> Thus, I think trying to design an architecture that makes
>> pure-transport translation possible is a lost cause, if your primary
>> use cases are offer/answer based, and so there's no point in creating
>> new mechanisms in an attempt to support it.
>
> We are definitely disagreeing on this point.
>
>>
>> Unless I'm missing something, SHIM falls in this category -- the
>> benefits of SHIM over single-session muxing are largely for transport
>> translation.
>>
>
> Not at all. It benefits any usage where you want to have an additional 
> demultiplexing point based on purpose. The alternative is to classify 
> each and every SSRC into a role, then process them differently in any 
> node. That is under the assumption you want to avoid multiple 
> transport flows.
>
> Cheers
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> Färögatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
>


From fluffy@cisco.com  Sun Nov 13 21:48:06 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA8B221F8CE0 for <avt@ietfa.amsl.com>; Sun, 13 Nov 2011 21:48:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e1UTn3LT6VQm for <avt@ietfa.amsl.com>; Sun, 13 Nov 2011 21:48:04 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 999CA21F8CD0 for <avt@ietf.org>; Sun, 13 Nov 2011 21:48:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=766; q=dns/txt; s=iport; t=1321249684; x=1322459284; h=from:content-transfer-encoding:subject:date:message-id: to:mime-version; bh=6gQvA+YJyJxVymPG8GwSVREgvRoVRiM4EQcuGRWV/Ag=; b=HypGcHOaUIsDc/6HRqtnQ0juN+lVzk0FUVIqAUKpUJbQQEed406CUESd qbOIJLB5xo/Y8cw4gJ0seuGg2wXHGW6NXsTDTgahItABQGfqRDMtmPI1o Ex7nw2/OAWaEb8mbFgKnjqK1pyv3XBiW7AoeP52SfxUsM4ZVWslzpM/6a c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAJuqwE5Io8UQ/2dsb2JhbABCFqlngQWCCwGCJC4Hh2iYCYEmAZ1EiRxjBIgOjCCSBg
X-IronPort-AV: E=Sophos;i="4.69,506,1315180800"; d="scan'208";a="59766018"
Received: from bgl-core-1.cisco.com ([72.163.197.16]) by ams-iport-2.cisco.com with ESMTP; 14 Nov 2011 05:48:02 +0000
Received: from tky-vpn-client-230-189.cisco.com (tky-vpn-client-230-189.cisco.com [10.70.230.189]) by bgl-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pAE5m1gr017163 for <avt@ietf.org>; Mon, 14 Nov 2011 05:48:01 GMT
From: Cullen Jennings <fluffy@cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Date: Mon, 14 Nov 2011 13:48:00 +0800
Message-Id: <450F1DC0-1C0A-4037-8D44-64486E991C88@cisco.com>
To: IETF AVT WG <avt@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1251.1)
X-Mailer: Apple Mail (2.1251.1)
Subject: [AVTCORE] timing requirements for IDMS
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 Nov 2011 05:48:07 -0000

The list seems very inconclusive about what our requirements are for =
timing for a audio beam steering solution. At one level I am getting the =
answer of a single sample. I am also seeing 1 micro second. I tried to =
look at the list traffic and saw one link that did not work. Can someone =
give me the fundamentals of what we are trying to do. How accurate a =
beam do we want, what frequencies and sort of phase array. =46rom this =
seems like one can derive the required accuracy.=20

The one link I found on list =
(http://www.cs.ucc.ie/~ianp/CS2511/HAP.html) does not seem to work.=20

(BTW =85 glad to see the work on this. For my applications probably =
synchronization of 10 ms would be fine but I'm not trying to do beam =
steering). =20



From ron.even.tlv@gmail.com  Mon Nov 14 00:51:05 2011
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB51621F8E8F for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 00:51:05 -0800 (PST)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6wb9mvKVN5kB for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 00:51:05 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0313221F8E8A for <avt@ietf.org>; Mon, 14 Nov 2011 00:51:04 -0800 (PST)
Received: by ywt34 with SMTP id 34so4464256ywt.31 for <avt@ietf.org>; Mon, 14 Nov 2011 00:51:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=JhHdZt8+y7P/C1MiaTBBuOMJOWWuUPo887Dk0nbkETg=; b=cxdJjksMoBKMylUXyk2YZVS/0mtu6fSf8BlyjkT7hqUROIQC/zrdQDCd4JipM70CuK pBS9WMY6SN/DkjyNN/T41bvhDxejWtuBuiAc3o7XiVQarw03pLF8Kkb89L1qzH+vw9Y+ D7rsdB1XGcuqpS7Ku5GVV0FjDVhy+n7cDAHNU=
Received: by 10.236.176.201 with SMTP id b49mr12952353yhm.120.1321260660151; Mon, 14 Nov 2011 00:51:00 -0800 (PST)
Received: from windows8d787f9 (dhcp-17b3.meeting.ietf.org. [130.129.23.179]) by mx.google.com with ESMTPS id w68sm29996338yhe.14.2011.11.14.00.50.56 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 14 Nov 2011 00:50:58 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <avt@ietf.org>
Date: Mon, 14 Nov 2011 10:48:19 +0200
Message-ID: <4ec0d672.e856ec0a.763a.78fa@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcyioIjFY0bjMsh/RXWAOGONJcU2TwACZrFA
Content-Language: en-us
Subject: [AVTCORE] FW: [clue] CLUE/RTCWEB adhoc - RTP requirements/usages for multi-stream
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 Nov 2011 08:51:05 -0000

-----Original Message-----
From: clue-bounces@ietf.org [mailto:clue-bounces@ietf.org] On Behalf Of Mary
Barnes
Sent: Monday, November 14, 2011 9:39 AM
To: CLUE; rtcweb@ietf.org; avtcore@ietf.org
Subject: [clue] CLUE/RTCWEB adhoc - RTP requirements/usages for multi-stream

Hello CLUE, RTCWEB and AVTCORE WG members,

Per the discussion in the CLUE WG session this morning, an adhoc is planned
on Thursday, 11:40-12:50 (room TBA) to discuss requirements
and usages of RTP for multi-stream for CLUE and RTCWEB.   Note, this
also relates to the discussion today in AVTCORE around multiplexing.

A proposed agenda has been appended to the CLUE WG agenda for IETF-82:
http://www.ietf.org/proceedings/82/agenda/clue.html

Note since the meeting is during lunch, the secretariat is arranging for us
to have one of the rooms that allows food, although please consider the note
about outside food:
http://www.ietf.org/meeting/82/things-to-note.html

I will post a note with the room to the mailing list (and update the
agenda) as soon as I have the information.

Regards,
Mary and Ted
(as chairs for the adhoc)
_______________________________________________
clue mailing list
clue@ietf.org
https://www.ietf.org/mailman/listinfo/clue


From Even.roni@huawei.com  Mon Nov 14 00:57:00 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3FCB21F8BA0 for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 00:57:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.01
X-Spam-Level: 
X-Spam-Status: No, score=-105.01 tagged_above=-999 required=5 tests=[AWL=-0.165, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BaX9nQQ9vFuh for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 00:56:59 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id F2D9D21F8EEA for <avt@ietf.org>; Mon, 14 Nov 2011 00:56:58 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUN0083Q7IPCL@szxga05-in.huawei.com> for avt@ietf.org; Mon, 14 Nov 2011 16:56:50 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUN00B367GCDF@szxga05-in.huawei.com> for avt@ietf.org; Mon, 14 Nov 2011 16:56:49 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEZ01736; Mon, 14 Nov 2011 16:56:49 +0800
Received: from SZXEML406-HUB.china.huawei.com (10.82.67.93) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 14 Nov 2011 16:56:46 +0800
Received: from SZXEML519-MBS.china.huawei.com ([169.254.7.4]) by szxeml406-hub.china.huawei.com ([10.82.67.93]) with mapi id 14.01.0323.003; Mon, 14 Nov 2011 16:56:39 +0800
Date: Mon, 14 Nov 2011 08:56:38 +0000
From: Roni even <Even.roni@huawei.com>
In-reply-to: <EADCEEE0AE4A7F46BD61061696794D98F753FD@SZXEML519-MBS.china.huawei.com>
X-Originating-IP: [172.24.2.41]
To: "avt@ietf.org" <avt@ietf.org>
Message-id: <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_/ugkW/HfeEUA6BDZ3572RA)"
Content-language: en-US
Accept-Language: en-US, zh-CN
Thread-topic: Call for consensus on multiplexing multipe media streams.
Thread-index: AcyioJPRabCqeOiXQl2CbkZF1COPHQACpo9s
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <EADCEEE0AE4A7F46BD61061696794D98F753FD@SZXEML519-MBS.china.huawei.com>
Subject: [AVTCORE] Call for consensus on multiplexing multipe media streams.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 Nov 2011 08:57:01 -0000

--Boundary_(ID_/ugkW/HfeEUA6BDZ3572RA)
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: base64

SGkNCg0KQXQgdGhlIEFWVGNvcmUgc2Vzc2lvbiB3ZSBoYWQgdHdvIHByZXNlbnRhdGlvbnMuIE9u
ZSBmcm9tIE1hZ251cyBwcm9wb3NpbmcgdGhlIG11bHRpcGxleGluZyBvZiBtdWx0aXBsZSBSVFAg
c2Vzc2lvbnMgb3ZlciBhIHNpbmdsZSB0cmFuc3BvcnQgZmxvdyBhbmQgdGhlIHNlY29uZCBmcm9t
IEpvbmF0aGFuIExlbm5veCBwcm9wb3NpbmcgbXVsdGlwbGV4aW5nIG11bHRpcGxlIG1lZGlhIHR5
cGVzIGluIGEgc2luZ2xlIFJUUCBzZXNzaW9uLg0KDQoNCg0KTWFnbnVzIGFza2VkIGluIHRoZSBi
ZWdpbm5pbmcgb2YgaGlzIHByZXNlbnRhdGlvbiBpZiB0aGUgV0cgYmVsaWV2ZSB0aGF0IHRoZSBw
cm9ibGVtIG9mIHByb3ZpZGluZyBtdWx0aXBsZSBSVFAgc2Vzc2lvbnMgb3ZlciBhIHNpbmdsZSB0
cmFuc3BvcnQgZmxvdyBzaG91bGQgYmUgc29sdmVkLiBUaGUgcmVzcG9uc2UgZnJvbSB0aGUgcm9v
bSB3YXMgdGhhdCBpdCB3YXMgYWxyZWFkeSBkaXNjdXNzZWQgaW4gSUVURiA4MSBhbmQgdGhlcmUg
d2FzIGludGVyZXN0IGluIGRvaW5nIHRoaXMgd29yay4NCg0KSW4gSUVURjgxIHRoZXJlIHdhcyBh
biBpbnRlcmVzdCBpbiBkb2luZyBib3RoIG9wdGlvbnMuIER1cmluZyB0aGUgc2Vzc2lvbiB0b2Rh
eSB3ZSBkaWQgbm90IGhhdmUgdGltZSB0byBhc2sgZm9yIGNvbnNlbnN1cy4NCg0KDQoNCg0KDQpT
byB0aGUgV0cgY2hhaXJzIGFyZSBhc2tpbmcgd2hpY2ggZGlyZWN0aW9uIHRvIHRha2UNCg0KDQoN
ClRoZSBvcHRpb25zIHdlIGhhdmUgYXJlOg0KDQoNCg0KMS4gR28gZm9yd2FyZCB3aXRoIGJvdGgg
c29sdXRpb25zLg0KDQoyLiBPbmx5IGRlZmluZSBtdWx0aXBsZXhpbmcgb2YgbXVsdGlwbGUgUlRQ
IHNlc3Npb25zIGluIGEgc2luZ2xlIHRyYW5zcG9ydCBmbG93Lg0KDQozLiBPbmx5IGRlZmluZSBt
dWx0aXBsZXhpbmcgb2YgbXVsdGlwbGUgbWVkaWEgdHlwZXMgaW4gYSBzaW5nbGUgUlRQIHNlc3Np
b24uDQoNCjQuIE5vdCBlbm91Z2ggaW5mb3JtYXRpb24gaW4gb3JkZXIgdG8gZGVjaWRlLCBtb3Jl
IGRpc2N1c3Npb24gaXMgbmVlZGVkLg0KDQoNCg0KDQoNClRoZXJlIHdlcmUgYWJvdXQgMjAgcGVv
cGxlIGluIHRoZSBBVlRjb3JlIHNlc3Npb24gd2hvIHJhaXNlZCB0aGVyZSBoYW5kcyB3aGVuIGFz
a2VkIGlmIHRoZXkgaGF2ZSBvcGluaW9uDQoNCg0KDQpUaGFua3MNCg0KUm9uaSBFdmVuDQoNCkFW
VGNvcmUgY28tY2hhaXINCg0KDQoNCqGhDQoNCg0K

--Boundary_(ID_/ugkW/HfeEUA6BDZ3572RA)
Content-type: text/html; charset=gb2312
Content-transfer-encoding: quoted-printable

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312">
<style id=3D"owaParaStyle">P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body fPStyle=3D"1" ocsi=3D"0">
<div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: =
10pt;">
<p>Hi</p>
<div style=3D"FONT-FAMILY: Times New Roman; COLOR: #000000; FONT-SIZE: 16px=
">
<div>
<div style=3D"FONT-FAMILY: Tahoma; DIRECTION: ltr; COLOR: #000000; FONT-SIZ=
E: 10pt">
<p>At the&nbsp;AVTcore<a></a><a></a> session we had two presentations. One =
from Magnus proposing the multiplexing of multiple RTP sessions over a sing=
le transport flow and the second from Jonathan Lennox proposing multiplexin=
g multiple media types in a single RTP
 session.</p>
<p>&nbsp;</p>
<p>Magnus asked in the beginning of his presentation if the WG believe that=
 the problem of providing multiple RTP sessions over a single transport flo=
w should be solved. The response from the room was that it was already disc=
ussed in IETF 81 and there was interest
 in doing this work. </p>
<p>In IETF81 there was an interest in doing both options. During the sessio=
n today we did not have time to ask for consensus.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>So the WG chairs are asking which direction to take </p>
<p>&nbsp;</p>
<p>The options we have are:</p>
<p>&nbsp;</p>
<p>1. Go forward with both solutions.</p>
<p>2. Only define multiplexing of multiple RTP sessions in a single transpo=
rt flow.</p>
<p>3. Only define multiplexing of multiple media types in a single RTP sess=
ion.</p>
<p>4. Not enough information in order to decide, more discussion is needed.=
</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>There were about 20 people in the&nbsp;AVTcore<a></a><a></a> session who=
 raised there hands when asked if they have opinion</p>
<p>&nbsp;</p>
<p>Thanks</p>
<p><a></a><a></a>Roni&nbsp;Even</p>
<p><a></a><a></a>AVTcore&nbsp;co-chair</p>
<p>&nbsp;</p>
<p align=3D"left"></p>
<p>=A1=A1</p>
<font size=3D"2">
<p>&nbsp;</p>
</font></div>
</div>
</div>
</div>
</body>
</html>

--Boundary_(ID_/ugkW/HfeEUA6BDZ3572RA)--

From ray.vanbrandenburg@tno.nl  Mon Nov 14 01:10:59 2011
Return-Path: <ray.vanbrandenburg@tno.nl>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25ABC21F8F40 for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 01:10:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.411
X-Spam-Level: 
X-Spam-Status: No, score=-2.411 tagged_above=-999 required=5 tests=[AWL=2.093,  BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iKh6xQzbPMYZ for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 01:10:58 -0800 (PST)
Received: from mailouta.tno.nl (mailouta.tno.nl [134.221.1.16]) by ietfa.amsl.com (Postfix) with ESMTP id 1CF9021F8F3F for <avt@ietf.org>; Mon, 14 Nov 2011 01:10:55 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.69,507,1315173600"; d="scan'208";a="60309253"
Received: from unknown (HELO mail.tno.nl) ([134.221.225.220]) by mailhost1a.tno.nl with ESMTP; 14 Nov 2011 10:10:50 +0100
Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.242]) by EXC-CASHUB01.tsn.tno.nl ([134.221.225.220]) with mapi id 14.01.0323.003; Mon, 14 Nov 2011 10:10:50 +0100
From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
To: 'Cullen Jennings' <fluffy@cisco.com>, 'IETF AVT WG' <avt@ietf.org>
Thread-Topic: [AVTCORE] timing requirements for IDMS
Thread-Index: AQHMopECAiAnPMc+lESb0KweksRhcJWsExYA
Date: Mon, 14 Nov 2011 09:10:49 +0000
Message-ID: <FCC100FC8D6B034CB88CD8173B2DA158155AAAD1@EXC-MBX03.tsn.tno.nl>
References: <450F1DC0-1C0A-4037-8D44-64486E991C88@cisco.com>
In-Reply-To: <450F1DC0-1C0A-4037-8D44-64486E991C88@cisco.com>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [134.221.225.191]
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: Re: [AVTCORE] timing requirements for IDMS
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 Nov 2011 09:10:59 -0000

Hi Cullen,

Thanks for your mail and your interest in this topic.=20

For an in-depth answer, I'm afraid I will have to depend on Kevin or Aidan =
(CC).

For a more practical answer: I think the main issue here is whether we need=
 to be more accurate than 16 microseconds (as provided by a 32bit NTP-forma=
t timestamp) or not (in which case we would need to go for the 64bit timest=
amp). From what I understand from Kevin and Aidan, the level or accuracy yo=
u would need to have in these advanced use cases is right around the level =
of 1-8 microseconds.=20

Ray

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Culle=
n Jennings
Sent: maandag 14 november 2011 6:48
To: IETF AVT WG
Subject: [AVTCORE] timing requirements for IDMS


The list seems very inconclusive about what our requirements are for timing=
 for a audio beam steering solution. At one level I am getting the answer o=
f a single sample. I am also seeing 1 micro second. I tried to look at the =
list traffic and saw one link that did not work. Can someone give me the fu=
ndamentals of what we are trying to do. How accurate a beam do we want, wha=
t frequencies and sort of phase array. From this seems like one can derive =
the required accuracy.=20

The one link I found on list (http://www.cs.ucc.ie/~ianp/CS2511/HAP.html) d=
oes not seem to work.=20

(BTW ... glad to see the work on this. For my applications probably synchro=
nization of 10 ms would be fine but I'm not trying to do beam steering). =20


_______________________________________________
Audio/Video Transport Core Maintenance
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt
This e-mail and its contents are subject to the DISCLAIMER at http://www.tn=
o.nl/emaildisclaimer


From magnus.westerlund@ericsson.com  Mon Nov 14 02:04:00 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4090B21F8E1E for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 02:03:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.543
X-Spam-Level: 
X-Spam-Status: No, score=-106.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CVK3ZQYYAO+x for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 02:03:47 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 38C3411E80D4 for <avt@ietf.org>; Mon, 14 Nov 2011 02:00:50 -0800 (PST)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-82-4ec0e32c6516
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id F5.3E.13753.C23E0CE4; Mon, 14 Nov 2011 10:45:16 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.3.137.0; Mon, 14 Nov 2011 10:45:15 +0100
Message-ID: <4EC0E327.9080000@ericsson.com>
Date: Mon, 14 Nov 2011 17:45:11 +0800
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: avt@ietf.org
References: <EADCEEE0AE4A7F46BD61061696794D98F753FD@SZXEML519-MBS.china.huawei.com> <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com>
In-Reply-To: <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com>
X-Enigmail-Version: 1.3.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [AVTCORE] Call for consensus on multiplexing multipe media streams.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 Nov 2011 10:04:00 -0000

>  
> 
> 1. Go forward with both solutions.
> 
> 2. Only define multiplexing of multiple RTP sessions in a single
> transport flow.
> 
> 3. Only define multiplexing of multiple media types in a single RTP session.
> 
> 4. Not enough information in order to decide, more discussion is needed.

My personally view:
I don't think 3 is a viable option based on the the consensus that
appears to exist that the multiple RTP session solution should exist.

My preference is for 2 as I believe it can solve all the necessary
cases. But I will live with a consensus decision becoming 1 and shut up
and try to ensure both solutions are as quickly progressed as they can
individually.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
FÃ¤rÃ¶gatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From kevin.gross@avanw.com  Mon Nov 14 02:11:17 2011
Return-Path: <kevin.gross@avanw.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A937221F8CA9 for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 02:11:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.217
X-Spam-Level: 
X-Spam-Status: No, score=0.217 tagged_above=-999 required=5 tests=[AWL=0.089,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id frF5OLmB+Slq for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 02:11:16 -0800 (PST)
Received: from oproxy5-pub.bluehost.com (oproxy5.bluehost.com [IPv6:2605:dc00:100:2::a5]) by ietfa.amsl.com (Postfix) with SMTP id 9C38721F8EC0 for <avt@ietf.org>; Mon, 14 Nov 2011 02:08:09 -0800 (PST)
Received: (qmail 7384 invoked by uid 0); 14 Nov 2011 10:08:08 -0000
Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by cpoproxy2.bluehost.com with SMTP; 14 Nov 2011 10:08:08 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default;  h=Content-Type:Cc:To:From:Subject:Message-ID:Date:References:In-Reply-To:MIME-Version; bh=M6O8QjCoN5JsHb8vF2s6i+ZaUb848ftEIpEDdX8X6ms=;  b=hSW6fwcjhcDENH+D9MJS6pmIwAYLg1wC8RHG6guC4dgFBVpLH19nwbU0eHI+c0Q+oIkO8Z7t5HRpS30sXpdaLZLyze/aR3YGurll3B5yTKpC/BOI6gclwFItINyehGOQ;
Received: from mail-bw0-f44.google.com ([209.85.214.44]) by host291.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from <kevin.gross@avanw.com>) id 1RPtSR-0003aV-Rg for avt@ietf.org; Mon, 14 Nov 2011 03:08:08 -0700
Received: by bkbzv15 with SMTP id zv15so7056071bkb.31 for <avt@ietf.org>; Mon, 14 Nov 2011 02:08:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.204.154.69 with SMTP id n5mr18515444bkw.79.1321265286026; Mon, 14 Nov 2011 02:08:06 -0800 (PST)
Received: by 10.223.115.200 with HTTP; Mon, 14 Nov 2011 02:08:05 -0800 (PST)
In-Reply-To: <FCC100FC8D6B034CB88CD8173B2DA158155AAAD1@EXC-MBX03.tsn.tno.nl>
References: <450F1DC0-1C0A-4037-8D44-64486E991C88@cisco.com> <FCC100FC8D6B034CB88CD8173B2DA158155AAAD1@EXC-MBX03.tsn.tno.nl>
Date: Mon, 14 Nov 2011 03:08:05 -0700
Message-ID: <CALw1_Q3SFAKhA6LJ=8qVtkUGEG8YLACUk=JXJPiGfa2s1UdPiA@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
Content-Type: multipart/alternative; boundary=0015175cfbca0715a204b1af0cef
X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 209.85.214.44 authed with kevin.gross@avanw.com}
Cc: Cullen Jennings <fluffy@cisco.com>, IETF AVT WG <avt@ietf.org>
Subject: Re: [AVTCORE] timing requirements for IDMS
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 Nov 2011 10:11:18 -0000

--0015175cfbca0715a204b1af0cef
Content-Type: text/plain; charset=ISO-8859-1

Here's a fix for the broken link -
http://web.archive.org/web/20100410235208/http://www.cs.ucc.ie/~ianp/CS2511/HAP.html.
Look at the Localisation section.

knowing geometry of speaker and listener placement, the accuracy
requirements in terms of time can be readily derived from
requirements/capabilities in terms of angles.

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org


On Mon, Nov 14, 2011 at 2:10 AM, Brandenburg, R. (Ray) van <
ray.vanbrandenburg@tno.nl> wrote:

> Hi Cullen,
>
> Thanks for your mail and your interest in this topic.
>
> For an in-depth answer, I'm afraid I will have to depend on Kevin or Aidan
> (CC).
>
> For a more practical answer: I think the main issue here is whether we
> need to be more accurate than 16 microseconds (as provided by a 32bit
> NTP-format timestamp) or not (in which case we would need to go for the
> 64bit timestamp). From what I understand from Kevin and Aidan, the level or
> accuracy you would need to have in these advanced use cases is right around
> the level of 1-8 microseconds.
>
> Ray
>
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Cullen Jennings
> Sent: maandag 14 november 2011 6:48
> To: IETF AVT WG
> Subject: [AVTCORE] timing requirements for IDMS
>
>
> The list seems very inconclusive about what our requirements are for
> timing for a audio beam steering solution. At one level I am getting the
> answer of a single sample. I am also seeing 1 micro second. I tried to look
> at the list traffic and saw one link that did not work. Can someone give me
> the fundamentals of what we are trying to do. How accurate a beam do we
> want, what frequencies and sort of phase array. From this seems like one
> can derive the required accuracy.
>
> The one link I found on list (http://www.cs.ucc.ie/~ianp/CS2511/HAP.html)
> does not seem to work.
>
> (BTW ... glad to see the work on this. For my applications probably
> synchronization of 10 ms would be fine but I'm not trying to do beam
> steering).
>
>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
> This e-mail and its contents are subject to the DISCLAIMER at
> http://www.tno.nl/emaildisclaimer
>
>

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

Here&#39;s a fix for the broken link -=A0<a href=3D"http://web.archive.org/=
web/20100410235208/http://www.cs.ucc.ie/~ianp/CS2511/HAP.html">http://web.a=
rchive.org/web/20100410235208/http://www.cs.ucc.ie/~ianp/CS2511/HAP.html</a=
>. Look at the Localisation section.<div>
<br></div><div>knowing geometry of speaker and listener placement, the accu=
racy requirements in terms of time can be readily derived from requirements=
/capabilities in terms of angles.</div><div><br></div><div>Kevin Gross</div=
>
<div><div>+1-303-447-0517</div><div>Media Network Consultant<br><div>AVA Ne=
tworks -=A0<a href=3D"http://www.avanw.com/" target=3D"_blank">www.AVAnw.co=
m</a>,=A0<a href=3D"http://www.X192.org" target=3D"_blank">www.X192.org</a>=
</div><div>
<br></div></div><br><div class=3D"gmail_quote">On Mon, Nov 14, 2011 at 2:10=
 AM, Brandenburg, R. (Ray) van <span dir=3D"ltr">&lt;<a href=3D"mailto:ray.=
vanbrandenburg@tno.nl">ray.vanbrandenburg@tno.nl</a>&gt;</span> wrote:<br><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex;">
Hi Cullen,<br>
<br>
Thanks for your mail and your interest in this topic.<br>
<br>
For an in-depth answer, I&#39;m afraid I will have to depend on Kevin or Ai=
dan (CC).<br>
<br>
For a more practical answer: I think the main issue here is whether we need=
 to be more accurate than 16 microseconds (as provided by a 32bit NTP-forma=
t timestamp) or not (in which case we would need to go for the 64bit timest=
amp). From what I understand from Kevin and Aidan, the level or accuracy yo=
u would need to have in these advanced use cases is right around the level =
of 1-8 microseconds.<br>

<br>
Ray<br>
<div class=3D"im"><br>
-----Original Message-----<br>
From: <a href=3D"mailto:avt-bounces@ietf.org">avt-bounces@ietf.org</a> [mai=
lto:<a href=3D"mailto:avt-bounces@ietf.org">avt-bounces@ietf.org</a>] On Be=
half Of Cullen Jennings<br>
Sent: maandag 14 november 2011 6:48<br>
To: IETF AVT WG<br>
Subject: [AVTCORE] timing requirements for IDMS<br>
<br>
<br>
The list seems very inconclusive about what our requirements are for timing=
 for a audio beam steering solution. At one level I am getting the answer o=
f a single sample. I am also seeing 1 micro second. I tried to look at the =
list traffic and saw one link that did not work. Can someone give me the fu=
ndamentals of what we are trying to do. How accurate a beam do we want, wha=
t frequencies and sort of phase array. From this seems like one can derive =
the required accuracy.<br>

<br>
The one link I found on list (<a href=3D"http://www.cs.ucc.ie/~ianp/CS2511/=
HAP.html" target=3D"_blank">http://www.cs.ucc.ie/~ianp/CS2511/HAP.html</a>)=
 does not seem to work.<br>
<br>
</div>(BTW ... glad to see the work on this. For my applications probably s=
ynchronization of 10 ms would be fine but I&#39;m not trying to do beam ste=
ering).<br>
<div class=3D"im"><br>
<br>
_______________________________________________<br>
Audio/Video Transport Core Maintenance<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>
</div>This e-mail and its contents are subject to the DISCLAIMER at <a href=
=3D"http://www.tno.nl/emaildisclaimer" target=3D"_blank">http://www.tno.nl/=
emaildisclaimer</a><br>
<br>
</blockquote></div><br></div>

--0015175cfbca0715a204b1af0cef--

From magnus.westerlund@ericsson.com  Mon Nov 14 02:26:14 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34A9021F8AFF for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 02:26:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.544
X-Spam-Level: 
X-Spam-Status: No, score=-106.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sBW96Rgd899J for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 02:26:13 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 54A0121F8446 for <avt@ietf.org>; Mon, 14 Nov 2011 02:26:13 -0800 (PST)
X-AuditID: c1b4fb39-b7b3eae00000252a-83-4ec0ecc432b7
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 5D.79.09514.4CCE0CE4; Mon, 14 Nov 2011 11:26:12 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.137.0; Mon, 14 Nov 2011 11:26:11 +0100
Message-ID: <4EC0ECBD.7020604@ericsson.com>
Date: Mon, 14 Nov 2011 18:26:05 +0800
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Harald Alvestrand <harald@alvestrand.no>
References: <4EB7B054.3000706@ericsson.com> <4EB7B4D8.5050003@alvestrand.no> <4EBBADD5.4020501@ericsson.com> <4EBBC481.5010504@alvestrand.no> <4EBBE238.20103@ericsson.com> <C3759687E4991243A1A0BD44EAC823034C42D486BF@BE235.mail.lan> <4EBCE8C4.1060703@ericsson.com> <4EC08BEA.0@alvestrand.no>
In-Reply-To: <4EC08BEA.0@alvestrand.no>
X-Enigmail-Version: 1.3.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: Jonathan Lennox <jonathan@vidyo.com>, Jonathan Rosenberg <jonathan.rosenberg@skype.net>, IETF AVTCore WG <avt@ietf.org>
Subject: Re: [AVTCORE] Offer/Answer and Transport Translators was: Re: Comments on draft-lennox-rtcweb-rtp-media-type-mux-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 Nov 2011 10:26:14 -0000

On 2011-11-14 11:32, Harald Alvestrand wrote:
> I think this discussion shows pretty clearly that a pure RTP mixer (one 
> that just forwards packets, and does not process any of them) is 
> functionally equivalent to a multicast group.
> 

No, a pure RTP Transport Translator is equivalent to a multicast group.

An RTP mixer uses its own SSRC for delivering media to any session
participant why using the media streams from the other. And thus mostly
disconnecting the legs only selected information are passed.

> I used to think that offer/answer was completely useless for negotiating 
> media for multicast groups, but I think now that Magnus' comments seem 
> to show how one can use offer/answer for that as long as a central node 
> does all the offering.

Well, there is special rules for multicast also to avoid this issue if
you look at SDP O/A.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From harald@alvestrand.no  Mon Nov 14 02:33:53 2011
Return-Path: <harald@alvestrand.no>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A890711E80B4 for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 02:33:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.448
X-Spam-Level: 
X-Spam-Status: No, score=-110.448 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VecZHya9wxwX for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 02:33:53 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id C089111E8080 for <avt@ietf.org>; Mon, 14 Nov 2011 02:33:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 0B29639E0E7 for <avt@ietf.org>; Mon, 14 Nov 2011 11:33:52 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eb1ito3EEfvS for <avt@ietf.org>; Mon, 14 Nov 2011 11:33:51 +0100 (CET)
Received: from [130.129.22.244] (dhcp-16f4.meeting.ietf.org [130.129.22.244]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 6C8AB39E074 for <avt@ietf.org>; Mon, 14 Nov 2011 11:33:50 +0100 (CET)
Message-ID: <4EC0EE8B.1090108@alvestrand.no>
Date: Mon, 14 Nov 2011 18:33:47 +0800
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15
MIME-Version: 1.0
To: avt@ietf.org
References: <EADCEEE0AE4A7F46BD61061696794D98F753FD@SZXEML519-MBS.china.huawei.com> <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com>
In-Reply-To: <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------070202010708000806080203"
Subject: Re: [AVTCORE] Call for consensus on multiplexing multipe media streams.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 Nov 2011 10:33:53 -0000

This is a multi-part message in MIME format.
--------------070202010708000806080203
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 7bit

On 11/14/2011 04:56 PM, Roni even wrote:
>
> Hi
>
> At the AVTcore session we had two presentations. One from Magnus
> proposing the multiplexing of multiple RTP sessions over a single
> transport flow and the second from Jonathan Lennox proposing
> multiplexing multiple media types in a single RTP session.
>
> Magnus asked in the beginning of his presentation if the WG believe
> that the problem of providing multiple RTP sessions over a single
> transport flow should be solved. The response from the room was that
> it was already discussed in IETF 81 and there was interest in doing
> this work.
>
> In IETF81 there was an interest in doing both options. During the
> session today we did not have time to ask for consensus.
>
> So the WG chairs are asking which direction to take
>
> The options we have are:
>
> 1. Go forward with both solutions.
>
> 2. Only define multiplexing of multiple RTP sessions in a single
> transport flow.
>
> 3. Only define multiplexing of multiple media types in a single RTP
> session.
>
> 4. Not enough information in order to decide, more discussion is needed.
>

I don't see these 4 as a set from which it is reasonable to pick one and
only one choice...

My preferred option is 1.
I think that 3 is a viable option for my scenarios.
I am strongly opposed to 2.

(I am also strongly opposed to using the term "multiplexing" for the
activity described in 3. I would prefer
"sending", which I think is more descriptive and more clearly different
from the multiplexing option.)

I think this is not a surprise to anyone who was present in the meeting.

Harald



--------------070202010708000806080203
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=GB2312" http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    On 11/14/2011 04:56 PM, Roni even wrote:
    <blockquote
cite="mid:EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=GB2312">
      <style id="owaParaStyle">P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
      <div style="direction: ltr; font-family: Tahoma; color: rgb(0, 0,
        0); font-size: 10pt;">
        <p>Hi</p>
        <div style="font-family: Times New Roman; color: rgb(0, 0, 0);
          font-size: 16px;">
          <div>
            <div style="font-family: Tahoma; direction: ltr; color:
              rgb(0, 0, 0); font-size: 10pt;">
              <p>At the&nbsp;AVTcore session we had two presentations. One
                from Magnus proposing the multiplexing of multiple RTP
                sessions over a single transport flow and the second
                from Jonathan Lennox proposing multiplexing multiple
                media types in a single RTP session.</p>
              <p>&nbsp;</p>
              <p>Magnus asked in the beginning of his presentation if
                the WG believe that the problem of providing multiple
                RTP sessions over a single transport flow should be
                solved. The response from the room was that it was
                already discussed in IETF 81 and there was interest in
                doing this work. </p>
              <p>In IETF81 there was an interest in doing both options.
                During the session today we did not have time to ask for
                consensus.</p>
              <p>&nbsp;</p>
              <p>&nbsp;</p>
              <p>So the WG chairs are asking which direction to take </p>
              <p>&nbsp;</p>
              <p>The options we have are:</p>
              <p>&nbsp;</p>
              <p>1. Go forward with both solutions.</p>
              <p>2. Only define multiplexing of multiple RTP sessions in
                a single transport flow.</p>
              <p>3. Only define multiplexing of multiple media types in
                a single RTP session.</p>
              <p>4. Not enough information in order to decide, more
                discussion is needed.<br>
              </p>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    I don't see these 4 as a set from which it is reasonable to pick one
    and only one choice...<br>
    <br>
    My preferred option is 1.<br>
    I think that 3 is a viable option for my scenarios.<br>
    I am strongly opposed to 2.<br>
    <br>
    (I am also strongly opposed to using the term "multiplexing" for the
    activity described in 3. I would prefer<br>
    "sending", which I think is more descriptive and more clearly
    different from the multiplexing option.)<br>
    <br>
    I think this is not a surprise to anyone who was present in the
    meeting.<br>
    <br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Harald<br>
    <br>
    <br>
  </body>
</html>

--------------070202010708000806080203--

From fluffy@cisco.com  Mon Nov 14 02:36:59 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C85711E80EA for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 02:36:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.47
X-Spam-Level: 
X-Spam-Status: No, score=-106.47 tagged_above=-999 required=5 tests=[AWL=0.129, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cPb6Djk-sEE5 for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 02:36:58 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id A91E111E80D9 for <avt@ietf.org>; Mon, 14 Nov 2011 02:36:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=2419; q=dns/txt; s=iport; t=1321267018; x=1322476618; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=b/R0fIYsZkiuu1VmXvBiV/MZQkhvKTYZkQI1XdmTTEw=; b=h/wQZMgEDtHoYQ7BPnCNEAO2E1U5lPLycv4KN6lr/PSzUkB/KtqE2s6o gsfOhTuSsUpM+yPJgpdRBwj1p/ecpRZjmGM9zo9eQuafd+6WwvS2Ssb1M jbZYI5AlRqiC0RZgPmQYKxq1gdI9Ux4VrUwQi6HTQpFBQIG4Xl7vjsZQb 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EANXuwE6rRDoI/2dsb2JhbABCFqlmgQWBcgEBAQMBAQEBDwFaDAUHBAsRBAEBKAcnHwkIBhMbB4dgCJkAAZ1viRxjBIgOjCCSBg
X-IronPort-AV: E=Sophos;i="4.69,508,1315180800"; d="scan'208";a="14087974"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 14 Nov 2011 10:36:58 +0000
Received: from tky-vpn-client-230-100.cisco.com (tky-vpn-client-230-100.cisco.com [10.70.230.100]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pAEAatV6017510; Mon, 14 Nov 2011 10:36:56 GMT
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=iso-8859-1
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <FCC100FC8D6B034CB88CD8173B2DA158155AAAD1@EXC-MBX03.tsn.tno.nl>
Date: Mon, 14 Nov 2011 18:36:55 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <D208D8C0-0B12-4378-B0BD-67863D87F133@cisco.com>
References: <450F1DC0-1C0A-4037-8D44-64486E991C88@cisco.com> <FCC100FC8D6B034CB88CD8173B2DA158155AAAD1@EXC-MBX03.tsn.tno.nl>
To: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
X-Mailer: Apple Mail (2.1251.1)
Cc: IETF AVT WG <avt@ietf.org>
Subject: Re: [AVTCORE] timing requirements for IDMS
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 Nov 2011 10:36:59 -0000

On Nov 14, 2011, at 17:10 , Brandenburg, R. (Ray) van wrote:

> Hi Cullen,
>=20
> Thanks for your mail and your interest in this topic.
>=20
> For an in-depth answer, I'm afraid I will have to depend on Kevin or =
Aidan (CC).

Thank you guys - look forward to learning more.=20

>=20
> For a more practical answer: I think the main issue here is whether we =
need to be more accurate than 16 microseconds (as provided by a 32bit =
NTP-format timestamp) or not (in which case we would need to go for the =
64bit timestamp).

Fair enough. When I went to the mic today I was thinking about the use =
cases for synchronized playback which would not need resolution like =
this. Once people mentioned beam forming, I realized I had been thinking =
about the wrong level. That said, I think it would be good to provide a =
few sentences of text in the draft and explained what level was needed, =
and why.=20

> =46rom what I understand from Kevin and Aidan, the level or accuracy =
you would need to have in these advanced use cases is right around the =
level of 1-8 microseconds.
>=20
> Ray
>=20
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of =
Cullen Jennings
> Sent: maandag 14 november 2011 6:48
> To: IETF AVT WG
> Subject: [AVTCORE] timing requirements for IDMS
>=20
>=20
> The list seems very inconclusive about what our requirements are for =
timing for a audio beam steering solution. At one level I am getting the =
answer of a single sample. I am also seeing 1 micro second. I tried to =
look at the list traffic and saw one link that did not work. Can someone =
give me the fundamentals of what we are trying to do. How accurate a =
beam do we want, what frequencies and sort of phase array. =46rom this =
seems like one can derive the required accuracy.
>=20
> The one link I found on list =
(http://www.cs.ucc.ie/~ianp/CS2511/HAP.html) does not seem to work.
>=20
> (BTW ... glad to see the work on this. For my applications probably =
synchronization of 10 ms would be fine but I'm not trying to do beam =
steering).=20
>=20
>=20
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
> This e-mail and its contents are subject to the DISCLAIMER at =
http://www.tno.nl/emaildisclaimer
>=20
>=20


From harald@alvestrand.no  Mon Nov 14 02:55:15 2011
Return-Path: <harald@alvestrand.no>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDD211F0C56 for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 02:55:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.524
X-Spam-Level: 
X-Spam-Status: No, score=-110.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CeO+5YytjACI for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 02:55:14 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 139A61F0C43 for <avt@ietf.org>; Mon, 14 Nov 2011 02:55:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 620FD39E0CD; Mon, 14 Nov 2011 11:55:10 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jkTSGP10QU90; Mon, 14 Nov 2011 11:55:10 +0100 (CET)
Received: from [130.129.22.244] (dhcp-16f4.meeting.ietf.org [130.129.22.244]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 6EC1B39E074; Mon, 14 Nov 2011 11:55:08 +0100 (CET)
Message-ID: <4EC0F389.8040407@alvestrand.no>
Date: Mon, 14 Nov 2011 18:55:05 +0800
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <4EB7B054.3000706@ericsson.com> <4EB7B4D8.5050003@alvestrand.no> <4EBBADD5.4020501@ericsson.com> <4EBBC481.5010504@alvestrand.no> <4EBBE238.20103@ericsson.com> <C3759687E4991243A1A0BD44EAC823034C42D486BF@BE235.mail.lan> <4EBCE8C4.1060703@ericsson.com> <4EC08BEA.0@alvestrand.no> <4EC0ECBD.7020604@ericsson.com>
In-Reply-To: <4EC0ECBD.7020604@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Jonathan Lennox <jonathan@vidyo.com>, Jonathan Rosenberg <jonathan.rosenberg@skype.net>, IETF AVTCore WG <avt@ietf.org>
Subject: Re: [AVTCORE] Offer/Answer and Transport Translators was: Re: Comments on draft-lennox-rtcweb-rtp-media-type-mux-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 Nov 2011 10:55:15 -0000

On 11/14/2011 06:26 PM, Magnus Westerlund wrote:
> On 2011-11-14 11:32, Harald Alvestrand wrote:
>> I think this discussion shows pretty clearly that a pure RTP mixer (one
>> that just forwards packets, and does not process any of them) is
>> functionally equivalent to a multicast group.
>>
> No, a pure RTP Transport Translator is equivalent to a multicast group.
>
> An RTP mixer uses its own SSRC for delivering media to any session
> participant why using the media streams from the other. And thus mostly
> disconnecting the legs only selected information are passed.
Thanks. I keep swapping those terms.
>> I used to think that offer/answer was completely useless for negotiating
>> media for multicast groups, but I think now that Magnus' comments seem
>> to show how one can use offer/answer for that as long as a central node
>> does all the offering.
> Well, there is special rules for multicast also to avoid this issue if
> you look at SDP O/A.
Yes, I noticed that 3264 rules for multicast were incompatible with 
those for unicast.

Is anyone using the 3264 rules for multicast setup?


From eckelcu@cisco.com  Mon Nov 14 05:57:57 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A325221F8DD5 for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 05:57:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.228
X-Spam-Level: 
X-Spam-Status: No, score=-6.228 tagged_above=-999 required=5 tests=[AWL=0.371,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zJ1kpFPYDWz6 for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 05:57:56 -0800 (PST)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id E798621F8DCF for <avt@ietf.org>; Mon, 14 Nov 2011 05:57:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=2532; q=dns/txt; s=iport; t=1321279077; x=1322488677; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=Hfo/GXAD/p06nxUyLVRjliO0linBnZrUUkBl36Ln9Hc=; b=c64evxNgXDwtzzbG+CeSPMbM9U0DuA35YvQUeuV/MPtgMUqN7aAtkGQV nLwFA3Bgl6JvVt8P3l55N3asUc5MWOePZJ0mf03rX2dHRqD1ID4FSRRyc 0jadyNWUb9xSFfEiiv+523dWbDQ4Eb5c3qWCPdBi/8dHLZ0qG2X+Wh9RX 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApkAAMgdwU6rRDoI/2dsb2JhbABCmXqQBYEFgXIBAQEEEgEKEwpLBAIBCBEEAQELBhcBBgFFCQgBAQQBEggTB6BWAZ4ViRxjBIgQkWKMVg
X-IronPort-AV: E=Sophos;i="4.69,509,1315180800"; d="scan'208";a="14080557"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 14 Nov 2011 13:57:56 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pAEDvuhq029003; Mon, 14 Nov 2011 13:57:56 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 14 Nov 2011 05:57:56 -0800
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, 14 Nov 2011 05:57:54 -0800
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05C134C0@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVTCORE] Call for consensus on multiplexing multipe media streams.
Thread-Index: AcyioJPRabCqeOiXQl2CbkZF1COPHQACpo9sAAlqj9A=
References: <EADCEEE0AE4A7F46BD61061696794D98F753FD@SZXEML519-MBS.china.huawei.com> <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Roni even" <Even.roni@huawei.com>, <avt@ietf.org>
X-OriginalArrivalTime: 14 Nov 2011 13:57:56.0642 (UTC) FILETIME=[695E4020:01CCA2D5]
Subject: Re: [AVTCORE] Call for consensus on multiplexing multipe media streams.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 Nov 2011 13:57:57 -0000

In today's session, Magnus and Colin presented a set of requirements for
(2). During the session, it was argued by several people that the set of
requirements could and should be relaxed in their use cases. For such
use cases, I think (3) is the best solution and (2) is not necessary.
If you really need to multiplex multiple media types over a single port
for use cases matching the requirements listed by Magnus and Colin, then
I trust they are correct and really do need (2) as well.=20
However, if the only reason such uses cases exist is to build something
that does interworking between something that uses (3) and something
that requires (2), one would likely do so by demultiplexing the multiple
media types into multiple non-multiplexed RTP sessions, as we do today,
so I do not think (2) is necessary.

Cheers,
Charles

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Roni even
> Sent: Monday, November 14, 2011 4:57 PM
> To: avt@ietf.org
> Subject: [AVTCORE] Call for consensus on multiplexing multipe media
streams.
>=20
> Hi
>=20
> At the AVTcore session we had two presentations. One from Magnus
proposing the multiplexing of
> multiple RTP sessions over a single transport flow and the second from
Jonathan Lennox proposing
> multiplexing multiple media types in a single RTP session.
>=20
>=20
>=20
> Magnus asked in the beginning of his presentation if the WG believe
that the problem of providing
> multiple RTP sessions over a single transport flow should be solved.
The response from the room was
> that it was already discussed in IETF 81 and there was interest in
doing this work.
>=20
> In IETF81 there was an interest in doing both options. During the
session today we did not have time
> to ask for consensus.
>=20
>=20
>=20
>=20
>=20
> So the WG chairs are asking which direction to take
>=20
>=20
>=20
> The options we have are:
>=20
>=20
>=20
> 1. Go forward with both solutions.
>=20
> 2. Only define multiplexing of multiple RTP sessions in a single
transport flow.
>=20
> 3. Only define multiplexing of multiple media types in a single RTP
session.
>=20
> 4. Not enough information in order to decide, more discussion is
needed.
>=20
>=20
>=20
>=20
>=20
> There were about 20 people in the AVTcore session who raised there
hands when asked if they have
> opinion
>=20
>=20
>=20
> Thanks
>=20
> Roni Even
>=20
> AVTcore co-chair
>=20
>=20
>=20
>=20
>=20
>=20


From magnus.westerlund@ericsson.com  Mon Nov 14 07:56:39 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A00F11E82D7 for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 07:56:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.545
X-Spam-Level: 
X-Spam-Status: No, score=-106.545 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UdzzM5Fsg-Qn for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 07:56:39 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id C0AFE11E82D8 for <avt@ietf.org>; Mon, 14 Nov 2011 07:56:38 -0800 (PST)
X-AuditID: c1b4fb39-b7b3eae00000252a-7e-4ec13a357305
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 87.15.09514.53A31CE4; Mon, 14 Nov 2011 16:56:37 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.137.0; Mon, 14 Nov 2011 16:56:36 +0100
Message-ID: <4EC13A31.2060302@ericsson.com>
Date: Mon, 14 Nov 2011 23:56:33 +0800
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: avt@ietf.org
References: <EADCEEE0AE4A7F46BD61061696794D98F753FD@SZXEML519-MBS.china.huawei.com> <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05C134C0@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05C134C0@xmb-sjc-234.amer.cisco.com>
X-Enigmail-Version: 1.3.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [AVTCORE] Call for consensus on multiplexing multipe media streams.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 Nov 2011 15:56:39 -0000

On 2011-11-14 21:57, Charles Eckel (eckelcu) wrote:
> In today's session, Magnus and Colin presented a set of requirements for
> (2). During the session, it was argued by several people that the set of
> requirements could and should be relaxed in their use cases. For such
> use cases, I think (3) is the best solution and (2) is not necessary.
> If you really need to multiplex multiple media types over a single port
> for use cases matching the requirements listed by Magnus and Colin, then
> I trust they are correct and really do need (2) as well.

I think when those requirements doesn't apply do need to be written up
in the form of an applicability statement for when (3) do works.


> However, if the only reason such uses cases exist is to build something
> that does interworking between something that uses (3) and something
> that requires (2), one would likely do so by demultiplexing the multiple
> media types into multiple non-multiplexed RTP sessions, as we do today,
> so I do not think (2) is necessary.

No, that is not the only reason. We do see a need for multiple RTP
session over the single transport. Not simply to interwork 3 with legacy.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From HKaplan@acmepacket.com  Mon Nov 14 17:11:14 2011
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0293511E8139 for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 17:11:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.472
X-Spam-Level: 
X-Spam-Status: No, score=-2.472 tagged_above=-999 required=5 tests=[AWL=0.126,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X7O5XInkwOhL for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 17:11:13 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 1C3C611E8138 for <avt@ietf.org>; Mon, 14 Nov 2011 17:11:13 -0800 (PST)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Mon, 14 Nov 2011 20:11:11 -0500
Received: from MAIL1.acmepacket.com ([169.254.1.232]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Mon, 14 Nov 2011 20:11:11 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Harald Alvestrand <harald@alvestrand.no>
Thread-Topic: [AVTCORE] Call for consensus on multiplexing multipe media streams.
Thread-Index: AQHMozN2scdtifLnsk6GzupkhRsZig==
Date: Tue, 15 Nov 2011 01:11:11 +0000
Message-ID: <EB3E39E1-4671-4796-BC63-BF8E8E87CA0D@acmepacket.com>
References: <EADCEEE0AE4A7F46BD61061696794D98F753FD@SZXEML519-MBS.china.huawei.com> <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com> <4EC0EE8B.1090108@alvestrand.no>
In-Reply-To: <4EC0EE8B.1090108@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [216.41.24.34]
Content-Type: multipart/alternative; boundary="_000_EB3E39E146714796BC63BF8E8E87CA0Dacmepacketcom_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "<avt@ietf.org>" <avt@ietf.org>
Subject: Re: [AVTCORE] Call for consensus on multiplexing multipe media	streams.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 15 Nov 2011 01:11:14 -0000

--_000_EB3E39E146714796BC63BF8E8E87CA0Dacmepacketcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Harald,
Can you explain why you're strongly opposed to 2?  It would help me make a =
more informed decision myself.

I know the advantages of #2, some of which haven't been articulated yet I t=
hink... but what I don't know is what its disadvantages are that would make=
 us choose #3 instead.

-hadriel


On Nov 14, 2011, at 5:33 AM, Harald Alvestrand wrote:

On 11/14/2011 04:56 PM, Roni even wrote:

Hi

At the AVTcore session we had two presentations. One from Magnus proposing =
the multiplexing of multiple RTP sessions over a single transport flow and =
the second from Jonathan Lennox proposing multiplexing multiple media types=
 in a single RTP session.



Magnus asked in the beginning of his presentation if the WG believe that th=
e problem of providing multiple RTP sessions over a single transport flow s=
hould be solved. The response from the room was that it was already discuss=
ed in IETF 81 and there was interest in doing this work.

In IETF81 there was an interest in doing both options. During the session t=
oday we did not have time to ask for consensus.




So the WG chairs are asking which direction to take



The options we have are:



1. Go forward with both solutions.

2. Only define multiplexing of multiple RTP sessions in a single transport =
flow.

3. Only define multiplexing of multiple media types in a single RTP session=
.

4. Not enough information in order to decide, more discussion is needed.

I don't see these 4 as a set from which it is reasonable to pick one and on=
ly one choice...

My preferred option is 1.
I think that 3 is a viable option for my scenarios.
I am strongly opposed to 2.

(I am also strongly opposed to using the term "multiplexing" for the activi=
ty described in 3. I would prefer
"sending", which I think is more descriptive and more clearly different fro=
m the multiplexing option.)

I think this is not a surprise to anyone who was present in the meeting.

                    Harald


_______________________________________________
Audio/Video Transport Core Maintenance
avt@ietf.org<mailto:avt@ietf.org>
https://www.ietf.org/mailman/listinfo/avt


--_000_EB3E39E146714796BC63BF8E8E87CA0Dacmepacketcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <4D3B3F4D2CDA5442BDEE05ACD6E2053D@acmepacket.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div><br>
</div>
<div>Harald,</div>
<div>Can you explain why you're strongly opposed to 2? &nbsp;It would help =
me make a more informed decision myself.</div>
<div><br>
</div>
<div>I know the advantages of #2, some of which haven't been articulated ye=
t I think... but what I don't know is what its disadvantages are that would=
 make us choose #3 instead.</div>
<div><br>
</div>
<div>-hadriel</div>
<div><br>
</div>
<br>
<div>
<div>On Nov 14, 2011, at 5:33 AM, Harald Alvestrand wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div bgcolor=3D"#ffffff" text=3D"#000000">On 11/14/2011 04:56 PM, Roni even=
 wrote:
<blockquote cite=3D"mid:EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MB=
S.china.huawei.com" type=3D"cite">
<style id=3D"owaParaStyle">P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
<div style=3D"direction: ltr; font-family: Tahoma; color: rgb(0, 0,
        0); font-size: 10pt;">
<p>Hi</p>
<div style=3D"font-family: Times New Roman; color: rgb(0, 0, 0);
          font-size: 16px;">
<div>
<div style=3D"font-family: Tahoma; direction: ltr; color:
              rgb(0, 0, 0); font-size: 10pt;">
<p>At the&nbsp;AVTcore session we had two presentations. One from Magnus pr=
oposing the multiplexing of multiple RTP sessions over a single transport f=
low and the second from Jonathan Lennox proposing multiplexing multiple med=
ia types in a single RTP session.</p>
<div>&nbsp;<br class=3D"webkit-block-placeholder">
</div>
<p>Magnus asked in the beginning of his presentation if the WG believe that=
 the problem of providing multiple RTP sessions over a single transport flo=
w should be solved. The response from the room was that it was already disc=
ussed in IETF 81 and there was interest
 in doing this work. </p>
<p>In IETF81 there was an interest in doing both options. During the sessio=
n today we did not have time to ask for consensus.</p>
<div>&nbsp;<br class=3D"webkit-block-placeholder">
</div>
<div>&nbsp;<br class=3D"webkit-block-placeholder">
</div>
<p>So the WG chairs are asking which direction to take </p>
<div>&nbsp;<br class=3D"webkit-block-placeholder">
</div>
<p>The options we have are:</p>
<div>&nbsp;<br class=3D"webkit-block-placeholder">
</div>
<p>1. Go forward with both solutions.</p>
<p>2. Only define multiplexing of multiple RTP sessions in a single transpo=
rt flow.</p>
<p>3. Only define multiplexing of multiple media types in a single RTP sess=
ion.</p>
<p>4. Not enough information in order to decide, more discussion is needed.=
<br>
</p>
</div>
</div>
</div>
</div>
</blockquote>
<br>
I don't see these 4 as a set from which it is reasonable to pick one and on=
ly one choice...<br>
<br>
My preferred option is 1.<br>
I think that 3 is a viable option for my scenarios.<br>
I am strongly opposed to 2.<br>
<br>
(I am also strongly opposed to using the term &quot;multiplexing&quot; for =
the activity described in 3. I would prefer<br>
&quot;sending&quot;, which I think is more descriptive and more clearly dif=
ferent from the multiplexing option.)<br>
<br>
I think this is not a surprise to anyone who was present in the meeting.<br=
>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Harald<br>
<br>
<br>
</div>
_______________________________________________<br>
Audio/Video Transport Core Maintenance<br>
<a href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/avt<br>
</blockquote>
</div>
<br>
</body>
</html>

--_000_EB3E39E146714796BC63BF8E8E87CA0Dacmepacketcom_--

From mary.ietf.barnes@gmail.com  Mon Nov 14 17:20:55 2011
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5781A1F0C7D; Mon, 14 Nov 2011 17:20:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.185
X-Spam-Level: 
X-Spam-Status: No, score=-103.185 tagged_above=-999 required=5 tests=[AWL=0.414, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MJqd5MEcQLQy; Mon, 14 Nov 2011 17:20:54 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 783A31F0CF3; Mon, 14 Nov 2011 17:20:54 -0800 (PST)
Received: by vcbfk1 with SMTP id fk1so6705290vcb.31 for <multiple recipients>; Mon, 14 Nov 2011 17:20:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=qRvBGN5kqlmF6k6QuHoAqU9iKXqriymZ1vgAiY/BjBc=; b=UPn20g287WTvv9/ciyEwXA+69VL5excJT8Y0yZZvvGWU5+VNTiLogpF8zxgvlxp63s cHQq08FSR/15PXOuEa6SaEsLNG7x0bpPoXSqJ0qmlvawYgMDEaBLu8r06P95P6HiLsUo ww4a454Yt1nmqQ6ArEw8iS0QwFqNDvnTcU6Do=
MIME-Version: 1.0
Received: by 10.52.20.207 with SMTP id p15mr38607286vde.87.1321320053996; Mon, 14 Nov 2011 17:20:53 -0800 (PST)
Received: by 10.52.175.131 with HTTP; Mon, 14 Nov 2011 17:20:53 -0800 (PST)
Date: Mon, 14 Nov 2011 19:20:53 -0600
Message-ID: <CAHBDyN5CC9BaSi8iApfxBNhDQFXxrsio6gL=ZMh_BRU1RVL3LA@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: CLUE <clue@ietf.org>, rtcweb@ietf.org, avt@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [AVTCORE] CLUE/RTCWEB adhoc - RTP requirements/usages for multi-stream - Thurs. lunchtime in 3F Banquet
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 15 Nov 2011 01:20:55 -0000

The room has been assigned - 3F Banquet.

Also, please note that the agenda has been updated to be a bit broader
than the previous version.

Regards,
Mary.

On Mon, Nov 14, 2011 at 1:39 AM, Mary Barnes <mary.ietf.barnes@gmail.com> w=
rote:
> Hello CLUE, RTCWEB and AVTCORE WG members,
>
> Per the discussion in the CLUE WG session this morning, an adhoc is
> planned on Thursday, 11:40-12:50 (room 3F Banquet) to discuss requirement=
s
> and usages of RTP for multi-stream for CLUE and RTCWEB. =A0 Note, this
> also relates to the discussion today in AVTCORE around multiplexing.
>
> A proposed agenda has been appended to the CLUE WG agenda for IETF-82:
> http://www.ietf.org/proceedings/82/agenda/clue.html
>
> Note since the meeting is during lunch, the secretariat is arranging
> for us to have one of the rooms that allows food, although please
> consider the note about outside food:
> http://www.ietf.org/meeting/82/things-to-note.html
>
> I will post a note with the room to the mailing list (and update the
> agenda) as soon as I have the information.
>
> Regards,
> Mary and Ted
> (as chairs for the adhoc)
>

From harald@alvestrand.no  Mon Nov 14 17:31:20 2011
Return-Path: <harald@alvestrand.no>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBBD211E8244 for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 17:31:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.561
X-Spam-Level: 
X-Spam-Status: No, score=-110.561 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a-e5oPHqDga5 for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 17:31:20 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id DEED611E820F for <avt@ietf.org>; Mon, 14 Nov 2011 17:31:19 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 3945A39E0E7; Tue, 15 Nov 2011 02:31:19 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bnkGtoL4Y65H; Tue, 15 Nov 2011 02:31:18 +0100 (CET)
Received: from [130.129.22.244] (dhcp-16f4.meeting.ietf.org [130.129.22.244]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 258A539E074; Tue, 15 Nov 2011 02:31:16 +0100 (CET)
Message-ID: <4EC1C0E1.3000505@alvestrand.no>
Date: Tue, 15 Nov 2011 09:31:13 +0800
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15
MIME-Version: 1.0
To: Hadriel Kaplan <HKaplan@acmepacket.com>
References: <EADCEEE0AE4A7F46BD61061696794D98F753FD@SZXEML519-MBS.china.huawei.com> <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com> <4EC0EE8B.1090108@alvestrand.no> <EB3E39E1-4671-4796-BC63-BF8E8E87CA0D@acmepacket.com>
In-Reply-To: <EB3E39E1-4671-4796-BC63-BF8E8E87CA0D@acmepacket.com>
Content-Type: multipart/alternative; boundary="------------020709080902030407000809"
Cc: "<avt@ietf.org>" <avt@ietf.org>
Subject: [AVTCORE] Why HTA thinks #2 is bad (Re: Call for consensus on multiplexing multipe media	streams.)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 15 Nov 2011 01:31:20 -0000

This is a multi-part message in MIME format.
--------------020709080902030407000809
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Trying to make the chairs' job of tallying easier by changing the 
subject when we fork into discussion rather than the call for consensus 
itself....

On 11/15/2011 09:11 AM, Hadriel Kaplan wrote:
>
> Harald,
> Can you explain why you're strongly opposed to 2?  It would help me 
> make a more informed decision myself.
>
> I know the advantages of #2, some of which haven't been articulated 
> yet I think... but what I don't know is what its disadvantages are 
> that would make us choose #3 instead.
#2 implies that we would not have a standard way to negotiate sending 
media with different top-level content types (such as audio and video, 
or audio and text) in the same RTP session.

This is today a limitation of SDP, not RTP, although some language in 
RFC 3550 (section 2.2) indicates that this was an intentional limitation 
when designing the SDP/RTP protocol suite.

I believe this decision was a bad decision, and that the issue of how 
many sessions to use, and what to pass on each session, should be left 
strictly to the application.
This requires an extension to SDP; in RTP, all that I believe is 
required is that we stop stating the assumption; no wire protocol 
changes should be needed.

                          Harald






--------------020709080902030407000809
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!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">
    Trying to make the chairs' job of tallying easier by changing the
    subject when we fork into discussion rather than the call for
    consensus itself....<br>
    <br>
    On 11/15/2011 09:11 AM, Hadriel Kaplan wrote:
    <blockquote
      cite="mid:EB3E39E1-4671-4796-BC63-BF8E8E87CA0D@acmepacket.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div><br>
      </div>
      <div>Harald,</div>
      <div>Can you explain why you're strongly opposed to 2? &nbsp;It would
        help me make a more informed decision myself.</div>
      <div><br>
      </div>
      <div>I know the advantages of #2, some of which haven't been
        articulated yet I think... but what I don't know is what its
        disadvantages are that would make us choose #3 instead.</div>
    </blockquote>
    #2 implies that we would not have a standard way to negotiate
    sending media with different top-level content types (such as audio
    and video, or audio and text) in the same RTP session.<br>
    <br>
    This is today a limitation of SDP, not RTP, although some language
    in RFC 3550 (section 2.2) indicates that this was an intentional
    limitation when designing the SDP/RTP protocol suite.<br>
    <br>
    I believe this decision was a bad decision, and that the issue of
    how many sessions to use, and what to pass on each session, should
    be left strictly to the application.<br>
    This requires an extension to SDP; in RTP, all that I believe is
    required is that we stop stating the assumption; no wire protocol
    changes should be needed.<br>
    <br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Harald<br>
    <br>
    <br>
    <br>
    <br>
    <br>
  </body>
</html>

--------------020709080902030407000809--

From casner@acm.org  Mon Nov 14 17:37:34 2011
Return-Path: <casner@acm.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FD9521F8EA4 for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 17:37:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2j52gsB0HE6q for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 17:37:33 -0800 (PST)
Received: from mailman.packetdesign.com (firewall-gw-dirty-u.packetdesign.com [65.192.41.2]) by ietfa.amsl.com (Postfix) with ESMTP id B7E2A21F8EA2 for <avt@ietf.org>; Mon, 14 Nov 2011 17:37:33 -0800 (PST)
Received: from hsa.packetdesign.com (hsa.packetdesign.com [192.168.0.86]) by mailman.packetdesign.com (8.13.1/8.13.1) with ESMTP id pAF1bNlq005497; Mon, 14 Nov 2011 17:37:23 -0800
Date: Mon, 14 Nov 2011 17:37:23 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: Harald Alvestrand <harald@alvestrand.no>
In-Reply-To: <4EC1C0E1.3000505@alvestrand.no>
Message-ID: <alpine.BSF.2.00.1111141735530.269@hsa.packetdesign.com>
References: <EADCEEE0AE4A7F46BD61061696794D98F753FD@SZXEML519-MBS.china.huawei.com> <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com> <4EC0EE8B.1090108@alvestrand.no> <EB3E39E1-4671-4796-BC63-BF8E8E87CA0D@acmepacket.com> <4EC1C0E1.3000505@alvestrand.no>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: "<avt@ietf.org>" <avt@ietf.org>
Subject: Re: [AVTCORE] Why HTA thinks #2 is bad (Re: Call for consensus on multiplexing multipe media streams.)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 15 Nov 2011 01:37:34 -0000

On Tue, 15 Nov 2011, Harald Alvestrand wrote:

> Trying to make the chairs' job of tallying easier by changing the subject when
> we fork into discussion rather than the call for consensus itself....
>
> On 11/15/2011 09:11 AM, Hadriel Kaplan wrote:
> >
> > Harald,
> > Can you explain why you're strongly opposed to 2?  It would help me make a
> > more informed decision myself.
> >
> > I know the advantages of #2, some of which haven't been articulated yet I
> > think... but what I don't know is what its disadvantages are that would make
> > us choose #3 instead.
> #2 implies that we would not have a standard way to negotiate sending media
> with different top-level content types (such as audio and video, or audio and
> text) in the same RTP session.
>
> This is today a limitation of SDP, not RTP, although some language in RFC 3550
> (section 2.2) indicates that this was an intentional limitation when designing
> the SDP/RTP protocol suite.

See also RFC 3550 section 5.2 for a list of reasons why not to do this.

                                                        -- Steve

From harald@alvestrand.no  Mon Nov 14 17:52:37 2011
Return-Path: <harald@alvestrand.no>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87FB611E81F0 for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 17:52:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.569
X-Spam-Level: 
X-Spam-Status: No, score=-110.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xxU5qiiXuTBg for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 17:52:37 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id A703411E812C for <avt@ietf.org>; Mon, 14 Nov 2011 17:52:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id E8FAC39E0E7; Tue, 15 Nov 2011 02:52:35 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WVtFCydG6a+3; Tue, 15 Nov 2011 02:52:35 +0100 (CET)
Received: from [130.129.22.244] (dhcp-16f4.meeting.ietf.org [130.129.22.244]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 912EC39E074; Tue, 15 Nov 2011 02:52:34 +0100 (CET)
Message-ID: <4EC1C5DF.7040009@alvestrand.no>
Date: Tue, 15 Nov 2011 09:52:31 +0800
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15
MIME-Version: 1.0
To: Stephen Casner <casner@acm.org>
References: <EADCEEE0AE4A7F46BD61061696794D98F753FD@SZXEML519-MBS.china.huawei.com>	<EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com>	<4EC0EE8B.1090108@alvestrand.no>	<EB3E39E1-4671-4796-BC63-BF8E8E87CA0D@acmepacket.com>	<4EC1C0E1.3000505@alvestrand.no> <alpine.BSF.2.00.1111141735530.269@hsa.packetdesign.com>
In-Reply-To: <alpine.BSF.2.00.1111141735530.269@hsa.packetdesign.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "<avt@ietf.org>" <avt@ietf.org>
Subject: Re: [AVTCORE] Why HTA thinks #2 is bad (Re: Call for consensus on multiplexing multipe media streams.)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 15 Nov 2011 01:52:37 -0000

On 11/15/2011 09:37 AM, Stephen Casner wrote:
> On Tue, 15 Nov 2011, Harald Alvestrand wrote:
>
>> Trying to make the chairs' job of tallying easier by changing the subject when
>> we fork into discussion rather than the call for consensus itself....
>>
>> On 11/15/2011 09:11 AM, Hadriel Kaplan wrote:
>>> Harald,
>>> Can you explain why you're strongly opposed to 2?  It would help me make a
>>> more informed decision myself.
>>>
>>> I know the advantages of #2, some of which haven't been articulated yet I
>>> think... but what I don't know is what its disadvantages are that would make
>>> us choose #3 instead.
>> #2 implies that we would not have a standard way to negotiate sending media
>> with different top-level content types (such as audio and video, or audio and
>> text) in the same RTP session.
>>
>> This is today a limitation of SDP, not RTP, although some language in RFC 3550
>> (section 2.2) indicates that this was an intentional limitation when designing
>> the SDP/RTP protocol suite.
> See also RFC 3550 section 5.2 for a list of reasons why not to do this.
We've been over this several times. Didn't we do it on this list too?

1, 2 and 3 are only relevant to PT-based multiplex, which I think nobody 
argues for.
The ones that are left are:

    4. An RTP mixer would not be able to combine interleaved streams of
       incompatible media into one stream.

    5. Carrying multiple media in one RTP session precludes: the use of
       different network paths or network resource allocations if
       appropriate; reception of a subset of the media if desired, for
       example just audio if video would exceed the available bandwidth;
       and receiver implementations that use separate processes for the
       different media, whereas using separate RTP sessions permits
       either single- or multiple-process implementations.

4 is only relevant for applications that need to support blind mixing: 
where streams are mixed without knowing what their content is. A mixer 
that can tell the difference between an OPUS stream and a G.722 stream 
is also able to tell the difference between VP8 and G.722.

5 is a matter that I think should be left for the application developer 
to decide whether he cares about it or not, and how it balances against 
the real cost of supporting sessions over multiple network paths; I 
believe that making this decision at the RTP layer, which is, after all, 
a tool for applications, not an application in itself, is inappropriate.

(note: several of the points in bullet 5 also are functions that are 
lost in a session-multiplexing scenario, so they are irrelevant to the 
decision that is in front of us now.)

                             Harald





From marshall.eubanks@gmail.com  Mon Nov 14 17:58:44 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8709E11E82C0; Mon, 14 Nov 2011 17:58:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.489
X-Spam-Level: 
X-Spam-Status: No, score=-103.489 tagged_above=-999 required=5 tests=[AWL=0.110, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id odNW2BugKB-9; Mon, 14 Nov 2011 17:58:44 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6924C11E816C; Mon, 14 Nov 2011 17:58:43 -0800 (PST)
Received: by eyg24 with SMTP id 24so5998290eyg.31 for <multiple recipients>; Mon, 14 Nov 2011 17:58:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=45xS9ux2NqxeE5Gr3nH6Se1C3UMFtXJLtpfMllVHZbo=; b=xz6wB6smf3mdMuyu8ZkAV0ZqmWMs9hlPV1EJZcbcWjFspNSOVnVSpwPb4n9vbPQmRX niwv48wytSJAl7K2YGstHtRvQD98rPummUaa57SlPG+V0xzaGucwk4ui/Qn39Sq24VjS oiCOgFCCcYeNx3BttuNQfmAGzHKq+Vi3FuDX4=
MIME-Version: 1.0
Received: by 10.182.150.4 with SMTP id ue4mr4232391obb.74.1321322321940; Mon, 14 Nov 2011 17:58:41 -0800 (PST)
Received: by 10.182.159.73 with HTTP; Mon, 14 Nov 2011 17:58:41 -0800 (PST)
In-Reply-To: <CAHBDyN5CC9BaSi8iApfxBNhDQFXxrsio6gL=ZMh_BRU1RVL3LA@mail.gmail.com>
References: <CAHBDyN5CC9BaSi8iApfxBNhDQFXxrsio6gL=ZMh_BRU1RVL3LA@mail.gmail.com>
Date: Mon, 14 Nov 2011 20:58:41 -0500
Message-ID: <CAJNg7VKBn720yNadZj5aBA20mi2b=SeJqagXfmLnGM6Ve_xEkQ@mail.gmail.com>
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org, CLUE <clue@ietf.org>, avt@ietf.org
Subject: Re: [AVTCORE] CLUE/RTCWEB adhoc - RTP requirements/usages for multi-stream - Thurs. lunchtime in 3F Banquet
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 15 Nov 2011 01:58:44 -0000

To be clear, food is _allowed_ but not provided ?

Marshall

On Mon, Nov 14, 2011 at 8:20 PM, Mary Barnes <mary.ietf.barnes@gmail.com> w=
rote:
> The room has been assigned - 3F Banquet.
>
> Also, please note that the agenda has been updated to be a bit broader
> than the previous version.
>
> Regards,
> Mary.
>
> On Mon, Nov 14, 2011 at 1:39 AM, Mary Barnes <mary.ietf.barnes@gmail.com>=
 wrote:
>> Hello CLUE, RTCWEB and AVTCORE WG members,
>>
>> Per the discussion in the CLUE WG session this morning, an adhoc is
>> planned on Thursday, 11:40-12:50 (room 3F Banquet) to discuss requiremen=
ts
>> and usages of RTP for multi-stream for CLUE and RTCWEB. =A0 Note, this
>> also relates to the discussion today in AVTCORE around multiplexing.
>>
>> A proposed agenda has been appended to the CLUE WG agenda for IETF-82:
>> http://www.ietf.org/proceedings/82/agenda/clue.html
>>
>> Note since the meeting is during lunch, the secretariat is arranging
>> for us to have one of the rooms that allows food, although please
>> consider the note about outside food:
>> http://www.ietf.org/meeting/82/things-to-note.html
>>
>> I will post a note with the room to the mailing list (and update the
>> agenda) as soon as I have the information.
>>
>> Regards,
>> Mary and Ted
>> (as chairs for the adhoc)
>>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>

From mary.ietf.barnes@gmail.com  Mon Nov 14 18:08:22 2011
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11C8111E808B; Mon, 14 Nov 2011 18:08:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.196
X-Spam-Level: 
X-Spam-Status: No, score=-103.196 tagged_above=-999 required=5 tests=[AWL=0.403, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wuZhIO079xUp; Mon, 14 Nov 2011 18:08:21 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3EC011F0D36; Mon, 14 Nov 2011 18:08:21 -0800 (PST)
Received: by vws5 with SMTP id 5so6858909vws.31 for <multiple recipients>; Mon, 14 Nov 2011 18:08:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=WdunM7KmK0ImYsrrwRSsi2txgtJcpsBWM/bf2JfxLAo=; b=B/I/T47/PwHwszWFSL5vC9TKpNnrSmFBKLPpiNyk4+RSt0GAinl1tDYBTnPp0949pD X3o7F4ZNceC8SpREdE9idzJ0j8pRaqcVgV0RuN3A5MINlSDEzX1ejGspvzZ3VlyIPfMr whxcyWE93JNQe+509X8lQLvoa1WQD24QjZ7N0=
MIME-Version: 1.0
Received: by 10.52.20.207 with SMTP id p15mr38808145vde.87.1321322900810; Mon, 14 Nov 2011 18:08:20 -0800 (PST)
Received: by 10.52.175.131 with HTTP; Mon, 14 Nov 2011 18:08:20 -0800 (PST)
In-Reply-To: <CAJNg7VKBn720yNadZj5aBA20mi2b=SeJqagXfmLnGM6Ve_xEkQ@mail.gmail.com>
References: <CAHBDyN5CC9BaSi8iApfxBNhDQFXxrsio6gL=ZMh_BRU1RVL3LA@mail.gmail.com> <CAJNg7VKBn720yNadZj5aBA20mi2b=SeJqagXfmLnGM6Ve_xEkQ@mail.gmail.com>
Date: Mon, 14 Nov 2011 20:08:20 -0600
Message-ID: <CAHBDyN7cRW4DT-jm8ik7eZdKcTh=H76tzrhXiH2U=7BO9bsZZw@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org, CLUE <clue@ietf.org>, avt@ietf.org
Subject: Re: [AVTCORE] CLUE/RTCWEB adhoc - RTP requirements/usages for multi-stream - Thurs. lunchtime in 3F Banquet
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 15 Nov 2011 02:08:22 -0000

Correct - folks should bring their own lunch and again as a reminder,
please review the rules related to outside food:
http://www.ietf.org/meeting/82/things-to-note.html

Mary.

On Mon, Nov 14, 2011 at 7:58 PM, Marshall Eubanks
<marshall.eubanks@gmail.com> wrote:
> To be clear, food is _allowed_ but not provided ?
>
> Marshall
>
> On Mon, Nov 14, 2011 at 8:20 PM, Mary Barnes <mary.ietf.barnes@gmail.com>=
 wrote:
>> The room has been assigned - 3F Banquet.
>>
>> Also, please note that the agenda has been updated to be a bit broader
>> than the previous version.
>>
>> Regards,
>> Mary.
>>
>> On Mon, Nov 14, 2011 at 1:39 AM, Mary Barnes <mary.ietf.barnes@gmail.com=
> wrote:
>>> Hello CLUE, RTCWEB and AVTCORE WG members,
>>>
>>> Per the discussion in the CLUE WG session this morning, an adhoc is
>>> planned on Thursday, 11:40-12:50 (room 3F Banquet) to discuss requireme=
nts
>>> and usages of RTP for multi-stream for CLUE and RTCWEB. =A0 Note, this
>>> also relates to the discussion today in AVTCORE around multiplexing.
>>>
>>> A proposed agenda has been appended to the CLUE WG agenda for IETF-82:
>>> http://www.ietf.org/proceedings/82/agenda/clue.html
>>>
>>> Note since the meeting is during lunch, the secretariat is arranging
>>> for us to have one of the rooms that allows food, although please
>>> consider the note about outside food:
>>> http://www.ietf.org/meeting/82/things-to-note.html
>>>
>>> I will post a note with the room to the mailing list (and update the
>>> agenda) as soon as I have the information.
>>>
>>> Regards,
>>> Mary and Ted
>>> (as chairs for the adhoc)
>>>
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>>
>

From csp@csperkins.org  Mon Nov 14 18:11:30 2011
Return-Path: <csp@csperkins.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BEF121F8D00 for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 18:11:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H9ZIAJnlHmIa for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 18:11:29 -0800 (PST)
Received: from lon1-msapost-3.mail.demon.net (lon1-msapost-3.mail.demon.net [195.173.77.182]) by ietfa.amsl.com (Postfix) with ESMTP id 9C0D721F8CFE for <avt@ietf.org>; Mon, 14 Nov 2011 18:11:29 -0800 (PST)
Received: from dhcp-20d9.meeting.ietf.org ([130.129.32.217]) by lon1-post-3.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1RQ8Ud-0002ay-eX; Tue, 15 Nov 2011 02:11:28 +0000
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com>
Date: Tue, 15 Nov 2011 10:11:16 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <D4323622-5B09-47BD-BA8E-69791BCDBA7D@csperkins.org>
References: <EADCEEE0AE4A7F46BD61061696794D98F753FD@SZXEML519-MBS.china.huawei.com> <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com>
To: Roni even <Even.roni@huawei.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] Call for consensus on multiplexing multipe media streams.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 15 Nov 2011 02:11:30 -0000

On 14 Nov 2011, at 16:56, Roni even wrote:
> At the AVTcore session we had two presentations. One from Magnus =
proposing the multiplexing of multiple RTP sessions over a single =
transport flow and the second from Jonathan Lennox proposing =
multiplexing multiple media types in a single RTP session.
> =20
> Magnus asked in the beginning of his presentation if the WG believe =
that the problem of providing multiple RTP sessions over a single =
transport flow should be solved. The response from the room was that it =
was already discussed in IETF 81 and there was interest in doing this =
work.
> In IETF81 there was an interest in doing both options. During the =
session today we did not have time to ask for consensus.
> =20
> =20
> So the WG chairs are asking which direction to take
> =20
> The options we have are:
> =20
> 1. Go forward with both solutions.
> 2. Only define multiplexing of multiple RTP sessions in a single =
transport flow.
> 3. Only define multiplexing of multiple media types in a single RTP =
session.
> 4. Not enough information in order to decide, more discussion is =
needed.

I support option (2), and think option (3) is problematic for the =
reasons described in draft-perkins-rtcweb-rtp-usage-02.=20

I can live with option (1), provided the limitations of both approaches =
are clearly specified.=20

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




From kevin.gross@avanw.com  Mon Nov 14 19:27:39 2011
Return-Path: <kevin.gross@avanw.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26C1C1F0DA6 for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 19:27:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.713
X-Spam-Level: 
X-Spam-Status: No, score=0.713 tagged_above=-999 required=5 tests=[AWL=-0.415,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_BACKHAIR_52=1, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ofb+ThL4XSFJ for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 19:27:38 -0800 (PST)
Received: from oproxy5-pub.bluehost.com (oproxy5.bluehost.com [IPv6:2605:dc00:100:2::a5]) by ietfa.amsl.com (Postfix) with SMTP id 390A11F0DA2 for <avt@ietf.org>; Mon, 14 Nov 2011 19:27:38 -0800 (PST)
Received: (qmail 10119 invoked by uid 0); 15 Nov 2011 03:27:38 -0000
Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by cpoproxy2.bluehost.com with SMTP; 15 Nov 2011 03:27:37 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default;  h=Content-Type:Cc:To:From:Subject:Message-ID:Date:References:In-Reply-To:MIME-Version; bh=o8XP9DwZ/G8vF+SVHjPeC2IhPcbY2E3TTUEZKgXgxyM=;  b=FYQ2+rPXygH6/gPV4dJFPWd+7lz/C+eplTKDLF653j1n5vrUuIwvxB4ojs64FZeQ+oqcBsRy2dv2MZoO2M0cYViUHCdVXp3bt2/YzeOk68OC+p8kBgpzILI+T4jLNEM8;
Received: from mail-bw0-f44.google.com ([209.85.214.44]) by host291.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from <kevin.gross@avanw.com>) id 1RQ9gP-0004Oj-Eq for avt@ietf.org; Mon, 14 Nov 2011 20:27:37 -0700
Received: by bkbzv15 with SMTP id zv15so583964bkb.31 for <avt@ietf.org>; Mon, 14 Nov 2011 19:27:36 -0800 (PST)
MIME-Version: 1.0
Received: by 10.204.133.197 with SMTP id g5mr21867338bkt.43.1321327655945; Mon, 14 Nov 2011 19:27:35 -0800 (PST)
Received: by 10.223.115.200 with HTTP; Mon, 14 Nov 2011 19:27:35 -0800 (PST)
In-Reply-To: <D208D8C0-0B12-4378-B0BD-67863D87F133@cisco.com>
References: <450F1DC0-1C0A-4037-8D44-64486E991C88@cisco.com> <FCC100FC8D6B034CB88CD8173B2DA158155AAAD1@EXC-MBX03.tsn.tno.nl> <D208D8C0-0B12-4378-B0BD-67863D87F133@cisco.com>
Date: Mon, 14 Nov 2011 20:27:35 -0700
Message-ID: <CALw1_Q1xiesik4Tin8+B6OZ_oqQjYEW6WgxY8hAVH6r_C=Nwjw@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: Cullen Jennings <fluffy@cisco.com>
Content-Type: multipart/alternative; boundary=00151761c92a90866f04b1bd91dd
X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 209.85.214.44 authed with kevin.gross@avanw.com}
Cc: IETF AVT WG <avt@ietf.org>
Subject: Re: [AVTCORE] timing requirements for IDMS
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 15 Nov 2011 03:27:39 -0000

--00151761c92a90866f04b1bd91dd
Content-Type: text/plain; charset=ISO-8859-1

I published detailed use
cases<https://docs.google.com/document/d/1ANYd-MkQUtJi5_B8uwOwfazB0p1Qmr6X6r85dsmUTgo/edit>to
the reflector a couple months ago. We did not include this material in
the draft. It sounds like it would be be helpful if we included some of it.

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org


On Mon, Nov 14, 2011 at 3:36 AM, Cullen Jennings <fluffy@cisco.com> wrote:

>
> On Nov 14, 2011, at 17:10 , Brandenburg, R. (Ray) van wrote:
>
> > Hi Cullen,
> >
> > Thanks for your mail and your interest in this topic.
> >
> > For an in-depth answer, I'm afraid I will have to depend on Kevin or
> Aidan (CC).
>
> Thank you guys - look forward to learning more.
>
> >
> > For a more practical answer: I think the main issue here is whether we
> need to be more accurate than 16 microseconds (as provided by a 32bit
> NTP-format timestamp) or not (in which case we would need to go for the
> 64bit timestamp).
>
> Fair enough. When I went to the mic today I was thinking about the use
> cases for synchronized playback which would not need resolution like this.
> Once people mentioned beam forming, I realized I had been thinking about
> the wrong level. That said, I think it would be good to provide a few
> sentences of text in the draft and explained what level was needed, and why.
>
> > From what I understand from Kevin and Aidan, the level or accuracy you
> would need to have in these advanced use cases is right around the level of
> 1-8 microseconds.
> >
> > Ray
> >
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Cullen Jennings
> > Sent: maandag 14 november 2011 6:48
> > To: IETF AVT WG
> > Subject: [AVTCORE] timing requirements for IDMS
> >
> >
> > The list seems very inconclusive about what our requirements are for
> timing for a audio beam steering solution. At one level I am getting the
> answer of a single sample. I am also seeing 1 micro second. I tried to look
> at the list traffic and saw one link that did not work. Can someone give me
> the fundamentals of what we are trying to do. How accurate a beam do we
> want, what frequencies and sort of phase array. From this seems like one
> can derive the required accuracy.
> >
> > The one link I found on list (http://www.cs.ucc.ie/~ianp/CS2511/HAP.html)
> does not seem to work.
> >
> > (BTW ... glad to see the work on this. For my applications probably
> synchronization of 10 ms would be fine but I'm not trying to do beam
> steering).
> >
> >
> > _______________________________________________
> > Audio/Video Transport Core Maintenance
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
> > This e-mail and its contents are subject to the DISCLAIMER at
> http://www.tno.nl/emaildisclaimer
> >
> >
>
>

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

I published detailed=A0<a href=3D"https://docs.google.com/document/d/1ANYd-=
MkQUtJi5_B8uwOwfazB0p1Qmr6X6r85dsmUTgo/edit">use cases</a> to the=A0reflect=
or=A0a couple months ago. We did not include this material in the draft. It=
 sounds like it would be be helpful if we included some of it.<div>
<br clear=3D"all">Kevin Gross<br><div>+1-303-447-0517</div><div>Media Netwo=
rk Consultant<br><div>AVA Networks -=A0<a href=3D"http://www.avanw.com/" ta=
rget=3D"_blank">www.AVAnw.com</a>,=A0<a href=3D"http://www.X192.org" target=
=3D"_blank">www.X192.org</a></div>
<div><br></div></div>
<br><div class=3D"gmail_quote">On Mon, Nov 14, 2011 at 3:36 AM, Cullen Jenn=
ings <span dir=3D"ltr">&lt;<a href=3D"mailto:fluffy@cisco.com">fluffy@cisco=
.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im"><br>
On Nov 14, 2011, at 17:10 , Brandenburg, R. (Ray) van wrote:<br>
<br>
&gt; Hi Cullen,<br>
&gt;<br>
&gt; Thanks for your mail and your interest in this topic.<br>
&gt;<br>
&gt; For an in-depth answer, I&#39;m afraid I will have to depend on Kevin =
or Aidan (CC).<br>
<br>
</div>Thank you guys - look forward to learning more.<br>
<div class=3D"im"><br>
&gt;<br>
&gt; For a more practical answer: I think the main issue here is whether we=
 need to be more accurate than 16 microseconds (as provided by a 32bit NTP-=
format timestamp) or not (in which case we would need to go for the 64bit t=
imestamp).<br>

<br>
</div>Fair enough. When I went to the mic today I was thinking about the us=
e cases for synchronized playback which would not need resolution like this=
. Once people mentioned beam forming, I realized I had been thinking about =
the wrong level. That said, I think it would be good to provide a few sente=
nces of text in the draft and explained what level was needed, and why.<br>

<div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; From what I understand from Kevin and Aidan, the level or accuracy you=
 would need to have in these advanced use cases is right around the level o=
f 1-8 microseconds.<br>
&gt;<br>
&gt; Ray<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:avt-bounces@ietf.org">avt-bounces@ietf.org</a>=
 [mailto:<a href=3D"mailto:avt-bounces@ietf.org">avt-bounces@ietf.org</a>] =
On Behalf Of Cullen Jennings<br>
&gt; Sent: maandag 14 november 2011 6:48<br>
&gt; To: IETF AVT WG<br>
&gt; Subject: [AVTCORE] timing requirements for IDMS<br>
&gt;<br>
&gt;<br>
&gt; The list seems very inconclusive about what our requirements are for t=
iming for a audio beam steering solution. At one level I am getting the ans=
wer of a single sample. I am also seeing 1 micro second. I tried to look at=
 the list traffic and saw one link that did not work. Can someone give me t=
he fundamentals of what we are trying to do. How accurate a beam do we want=
, what frequencies and sort of phase array. From this seems like one can de=
rive the required accuracy.<br>

&gt;<br>
&gt; The one link I found on list (<a href=3D"http://www.cs.ucc.ie/~ianp/CS=
2511/HAP.html" target=3D"_blank">http://www.cs.ucc.ie/~ianp/CS2511/HAP.html=
</a>) does not seem to work.<br>
&gt;<br>
&gt; (BTW ... glad to see the work on this. For my applications probably sy=
nchronization of 10 ms would be fine but I&#39;m not trying to do beam stee=
ring).<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; Audio/Video Transport Core Maintenance<br>
&gt; <a href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/avt" target=3D"_blank=
">https://www.ietf.org/mailman/listinfo/avt</a><br>
&gt; This e-mail and its contents are subject to the DISCLAIMER at <a href=
=3D"http://www.tno.nl/emaildisclaimer" target=3D"_blank">http://www.tno.nl/=
emaildisclaimer</a><br>
&gt;<br>
&gt;<br>
<br>
</div></div></blockquote></div><br></div>

--00151761c92a90866f04b1bd91dd--

From csp@csperkins.org  Mon Nov 14 21:41:10 2011
Return-Path: <csp@csperkins.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81DFB11E80C4 for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 21:41:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7lUUKOdSUtFU for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 21:41:09 -0800 (PST)
Received: from lon1-msapost-3.mail.demon.net (lon1-msapost-3.mail.demon.net [195.173.77.182]) by ietfa.amsl.com (Postfix) with ESMTP id 9A05511E8073 for <avt@ietf.org>; Mon, 14 Nov 2011 21:41:09 -0800 (PST)
Received: from dhcp-20d9.meeting.ietf.org ([130.129.32.217]) by lon1-post-3.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1RQBl8-0005kN-fv; Tue, 15 Nov 2011 05:41:09 +0000
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=utf-8
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA3338A2@szxeml523-mbs.china.huawei.com>
Date: Tue, 15 Nov 2011 13:40:32 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <7D0E5A6C-5F70-42BF-B3AB-B405FC37A62E@csperkins.org>
References: <20111114002647.19680.14547.idtracker@ietfa.amsl.com> <B8F9A780D330094D99AF023C5877DABA3338A2@szxeml523-mbs.china.huawei.com>
To: Qin Wu <bill.wu@huawei.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-06.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 15 Nov 2011 05:41:10 -0000

I have two quick comments on this version.=20

This new IANA Considerations text says:

   At the time of writing, the consumption of XR block code points isn't
   a major issue.  However when XR block codes points is really close to
   run out of space, it might be desirable to define new fields encoded
   as TLV elements in the XR report block or define one XR block type
   for vendor-specific extensions, with an enterprise number included to
   identify the vendor making the extension.

This is not actionable by IANA, so I think it should be changed back to =
the previous wording of "There is no IANA action in this document".=20

Section 5.3 "proposes to define a new XR block". This would probably be =
better phrased as "draft-=E2=80=A6 defines a new XR block", since the =
definition has already happened.

Colin


On 14 Nov 2011, at 10:05, Qin Wu wrote:
> Hi, Folks:
> We have just submitted a new version of monarch document.
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-06.txt
>=20
> We talk with chairs and think it has been ready for WGLC.
> Chairs, would you like to use this version as baseline to raise WGLC?
>=20
>=20
> Regards!
> -Qin
> _______________________________________
> =E5=8F=91=E4=BB=B6=E4=BA=BA: i-d-announce-bounces@ietf.org =
[i-d-announce-bounces@ietf.org] =E4=BB=A3=E8=A1=A8 =
internet-drafts@ietf.org [internet-drafts@ietf.org]
> =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2011=E5=B9=B411=E6=9C=8814=E6=97=A5=
 8:26
> =E5=88=B0: i-d-announce@ietf.org
> Cc: avt@ietf.org
> =E4=B8=BB=E9=A2=98: I-D Action: draft-ietf-avtcore-monarch-06.txt
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories. This draft is a work item of the Audio/Video Transport Core =
Maintenance Working Group of the IETF.
>=20
>        Title           : Monitoring Architectures for RTP
>        Author(s)       : Qin Wu
>                          Geoff Hunt
>                          Philip Arden
>        Filename        : draft-ietf-avtcore-monarch-06.txt
>        Pages           : 25
>        Date            : 2011-11-13
>=20
>   This memo proposes an architecture for extending RTCP with a new =
RTCP
>   XR (RFC3611) block type to report new metrics regarding media
>   transmission or reception quality, following RTCP guideline
>   established in RFC5968.  This memo suggests that a new block should
>   contain a single metric or a small number of metrics relevant to a
>   single parameter of interest or concern, rather than containing a
>   number of metrics which attempt to provide full coverage of all =
those
>   parameters of concern to a specific application.  Applications may
>   then &quot;mix and match&quot; to create a set of blocks which =
covers their set
>   of concerns.  Where possible, a specific block should be designed to
>   be re-usable across more than one application, for example, for all
>   of voice, streaming audio and video.
>=20
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-06.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-06.txt
> _______________________________________________
> 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 Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From bill.wu@huawei.com  Mon Nov 14 22:23:20 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3DB011E821F for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 22:23:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.53
X-Spam-Level: 
X-Spam-Status: No, score=-0.53 tagged_above=-999 required=5 tests=[AWL=-2.979,  BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, MIME_8BIT_HEADER=0.3,  MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ywyGDLuKL-Z4 for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 22:23:20 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id F143F11E8291 for <avt@ietf.org>; Mon, 14 Nov 2011 22:23:19 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUO0006PV2V2Y@szxga03-in.huawei.com> for avt@ietf.org; Tue, 15 Nov 2011 14:23:19 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUO00DKMV2JL3@szxga03-in.huawei.com> for avt@ietf.org; Tue, 15 Nov 2011 14:23:19 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEZ58171; Tue, 15 Nov 2011 14:23:18 +0800
Received: from SZXEML401-HUB.china.huawei.com (10.82.67.31) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 15 Nov 2011 14:23:15 +0800
Received: from SZXEML523-MBS.china.huawei.com ([169.254.6.67]) by szxeml401-hub.china.huawei.com ([10.82.67.31]) with mapi id 14.01.0323.003; Tue, 15 Nov 2011 14:23:09 +0800
Date: Tue, 15 Nov 2011 06:23:09 +0000
From: Qin Wu <bill.wu@huawei.com>
In-reply-to: <7D0E5A6C-5F70-42BF-B3AB-B405FC37A62E@csperkins.org>
X-Originating-IP: [172.24.2.41]
To: Colin Perkins <csp@csperkins.org>
Message-id: <B8F9A780D330094D99AF023C5877DABA334193@szxeml523-mbs.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=gb2312
Content-language: zh-CN
Content-transfer-encoding: base64
Accept-Language: zh-CN, en-US
Thread-topic: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-06.txt
Thread-index: AQHMomQlgYg5GwZpqEWyT0P+dDCZN5WrnRG+gAFKOACAAJDvbw==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <20111114002647.19680.14547.idtracker@ietfa.amsl.com> <B8F9A780D330094D99AF023C5877DABA3338A2@szxeml523-mbs.china.huawei.com> <7D0E5A6C-5F70-42BF-B3AB-B405FC37A62E@csperkins.org>
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: [AVTCORE] =?gb2312?b?tPC4tDogIEktRCBBY3Rpb246IGRyYWZ0LWlldGYtYXZ0?= =?gb2312?b?Y29yZS1tb25hcmNoLTA2LnR4dA==?=
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 15 Nov 2011 06:23:20 -0000

VGhhbmtzIENvbGluIGZvciB5b3VyIHJldmlldyBhbmQgcXVpY2sgY29tbWVudHMuDQpBcyBmb3Ig
SUFOQSBzZWN0aW9uLCB0aGUgcHJvcG9zZWQgY2hhbmdlIGlzIGJhc2VkIG9uIE1hZ251cydzIHN1
Z2dlc3Rpb24uDQpJIGFtIG9rYXkgdG8gY2hhbmdlIGJhY2sgaWYgbm9ib2R5IGlzIGFnYWluc3Qg
aGF2aW5nIG5vIElBTkEgYWN0aW9uLg0KDQpGb3Igc2VjdGlvbiA1LjMsIHRoZSBhbnN3ZXIgaXMg
eWVzLiBUaGFuayBmb3IgeW91ciBzdWdnZXN0aW9uLg0KDQpSZWdhcmRzIQ0KLVFpbg0KX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0Kt6K8/sjLOiBDb2xpbiBQZXJraW5z
IFtjc3BAY3NwZXJraW5zLm9yZ10NCreiy83KsbzkOiAyMDExxOoxMdTCMTXI1SAxMzo0MA0Ktb06
IFFpbiBXdQ0KQ2M6IGF2dEBpZXRmLm9yZw0K1vfM4jogUmU6IFtBVlRDT1JFXSBJLUQgQWN0aW9u
OiBkcmFmdC1pZXRmLWF2dGNvcmUtbW9uYXJjaC0wNi50eHQNCg0KSSBoYXZlIHR3byBxdWljayBj
b21tZW50cyBvbiB0aGlzIHZlcnNpb24uDQoNClRoaXMgbmV3IElBTkEgQ29uc2lkZXJhdGlvbnMg
dGV4dCBzYXlzOg0KDQogICBBdCB0aGUgdGltZSBvZiB3cml0aW5nLCB0aGUgY29uc3VtcHRpb24g
b2YgWFIgYmxvY2sgY29kZSBwb2ludHMgaXNuJ3QNCiAgIGEgbWFqb3IgaXNzdWUuICBIb3dldmVy
IHdoZW4gWFIgYmxvY2sgY29kZXMgcG9pbnRzIGlzIHJlYWxseSBjbG9zZSB0bw0KICAgcnVuIG91
dCBvZiBzcGFjZSwgaXQgbWlnaHQgYmUgZGVzaXJhYmxlIHRvIGRlZmluZSBuZXcgZmllbGRzIGVu
Y29kZWQNCiAgIGFzIFRMViBlbGVtZW50cyBpbiB0aGUgWFIgcmVwb3J0IGJsb2NrIG9yIGRlZmlu
ZSBvbmUgWFIgYmxvY2sgdHlwZQ0KICAgZm9yIHZlbmRvci1zcGVjaWZpYyBleHRlbnNpb25zLCB3
aXRoIGFuIGVudGVycHJpc2UgbnVtYmVyIGluY2x1ZGVkIHRvDQogICBpZGVudGlmeSB0aGUgdmVu
ZG9yIG1ha2luZyB0aGUgZXh0ZW5zaW9uLg0KDQpUaGlzIGlzIG5vdCBhY3Rpb25hYmxlIGJ5IElB
TkEsIHNvIEkgdGhpbmsgaXQgc2hvdWxkIGJlIGNoYW5nZWQgYmFjayB0byB0aGUgcHJldmlvdXMg
d29yZGluZyBvZiAiVGhlcmUgaXMgbm8gSUFOQSBhY3Rpb24gaW4gdGhpcyBkb2N1bWVudCIuDQoN
ClNlY3Rpb24gNS4zICJwcm9wb3NlcyB0byBkZWZpbmUgYSBuZXcgWFIgYmxvY2siLiBUaGlzIHdv
dWxkIHByb2JhYmx5IGJlIGJldHRlciBwaHJhc2VkIGFzICJkcmFmdC2hrSBkZWZpbmVzIGEgbmV3
IFhSIGJsb2NrIiwgc2luY2UgdGhlIGRlZmluaXRpb24gaGFzIGFscmVhZHkgaGFwcGVuZWQuDQoN
CkNvbGluDQoNCg0KT24gMTQgTm92IDIwMTEsIGF0IDEwOjA1LCBRaW4gV3Ugd3JvdGU6DQo+IEhp
LCBGb2xrczoNCj4gV2UgaGF2ZSBqdXN0IHN1Ym1pdHRlZCBhIG5ldyB2ZXJzaW9uIG9mIG1vbmFy
Y2ggZG9jdW1lbnQuDQo+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0
LWlldGYtYXZ0Y29yZS1tb25hcmNoLTA2LnR4dA0KPg0KPiBXZSB0YWxrIHdpdGggY2hhaXJzIGFu
ZCB0aGluayBpdCBoYXMgYmVlbiByZWFkeSBmb3IgV0dMQy4NCj4gQ2hhaXJzLCB3b3VsZCB5b3Ug
bGlrZSB0byB1c2UgdGhpcyB2ZXJzaW9uIGFzIGJhc2VsaW5lIHRvIHJhaXNlIFdHTEM/DQo+DQo+
DQo+IFJlZ2FyZHMhDQo+IC1RaW4NCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fDQo+ILeivP7IyzogaS1kLWFubm91bmNlLWJvdW5jZXNAaWV0Zi5vcmcgW2ktZC1hbm5v
dW5jZS1ib3VuY2VzQGlldGYub3JnXSC0+rHtIGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyBbaW50
ZXJuZXQtZHJhZnRzQGlldGYub3JnXQ0KPiC3osvNyrG85DogMjAxMcTqMTHUwjE0yNUgODoyNg0K
PiC1vTogaS1kLWFubm91bmNlQGlldGYub3JnDQo+IENjOiBhdnRAaWV0Zi5vcmcNCj4g1vfM4jog
SS1EIEFjdGlvbjogZHJhZnQtaWV0Zi1hdnRjb3JlLW1vbmFyY2gtMDYudHh0DQo+DQo+IEEgTmV3
IEludGVybmV0LURyYWZ0IGlzIGF2YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIEludGVybmV0LURy
YWZ0cyBkaXJlY3Rvcmllcy4gVGhpcyBkcmFmdCBpcyBhIHdvcmsgaXRlbSBvZiB0aGUgQXVkaW8v
VmlkZW8gVHJhbnNwb3J0IENvcmUgTWFpbnRlbmFuY2UgV29ya2luZyBHcm91cCBvZiB0aGUgSUVU
Ri4NCj4NCj4gICAgICAgIFRpdGxlICAgICAgICAgICA6IE1vbml0b3JpbmcgQXJjaGl0ZWN0dXJl
cyBmb3IgUlRQDQo+ICAgICAgICBBdXRob3IocykgICAgICAgOiBRaW4gV3UNCj4gICAgICAgICAg
ICAgICAgICAgICAgICAgIEdlb2ZmIEh1bnQNCj4gICAgICAgICAgICAgICAgICAgICAgICAgIFBo
aWxpcCBBcmRlbg0KPiAgICAgICAgRmlsZW5hbWUgICAgICAgIDogZHJhZnQtaWV0Zi1hdnRjb3Jl
LW1vbmFyY2gtMDYudHh0DQo+ICAgICAgICBQYWdlcyAgICAgICAgICAgOiAyNQ0KPiAgICAgICAg
RGF0ZSAgICAgICAgICAgIDogMjAxMS0xMS0xMw0KPg0KPiAgIFRoaXMgbWVtbyBwcm9wb3NlcyBh
biBhcmNoaXRlY3R1cmUgZm9yIGV4dGVuZGluZyBSVENQIHdpdGggYSBuZXcgUlRDUA0KPiAgIFhS
IChSRkMzNjExKSBibG9jayB0eXBlIHRvIHJlcG9ydCBuZXcgbWV0cmljcyByZWdhcmRpbmcgbWVk
aWENCj4gICB0cmFuc21pc3Npb24gb3IgcmVjZXB0aW9uIHF1YWxpdHksIGZvbGxvd2luZyBSVENQ
IGd1aWRlbGluZQ0KPiAgIGVzdGFibGlzaGVkIGluIFJGQzU5NjguICBUaGlzIG1lbW8gc3VnZ2Vz
dHMgdGhhdCBhIG5ldyBibG9jayBzaG91bGQNCj4gICBjb250YWluIGEgc2luZ2xlIG1ldHJpYyBv
ciBhIHNtYWxsIG51bWJlciBvZiBtZXRyaWNzIHJlbGV2YW50IHRvIGENCj4gICBzaW5nbGUgcGFy
YW1ldGVyIG9mIGludGVyZXN0IG9yIGNvbmNlcm4sIHJhdGhlciB0aGFuIGNvbnRhaW5pbmcgYQ0K
PiAgIG51bWJlciBvZiBtZXRyaWNzIHdoaWNoIGF0dGVtcHQgdG8gcHJvdmlkZSBmdWxsIGNvdmVy
YWdlIG9mIGFsbCB0aG9zZQ0KPiAgIHBhcmFtZXRlcnMgb2YgY29uY2VybiB0byBhIHNwZWNpZmlj
IGFwcGxpY2F0aW9uLiAgQXBwbGljYXRpb25zIG1heQ0KPiAgIHRoZW4gJnF1b3Q7bWl4IGFuZCBt
YXRjaCZxdW90OyB0byBjcmVhdGUgYSBzZXQgb2YgYmxvY2tzIHdoaWNoIGNvdmVycyB0aGVpciBz
ZXQNCj4gICBvZiBjb25jZXJucy4gIFdoZXJlIHBvc3NpYmxlLCBhIHNwZWNpZmljIGJsb2NrIHNo
b3VsZCBiZSBkZXNpZ25lZCB0bw0KPiAgIGJlIHJlLXVzYWJsZSBhY3Jvc3MgbW9yZSB0aGFuIG9u
ZSBhcHBsaWNhdGlvbiwgZm9yIGV4YW1wbGUsIGZvciBhbGwNCj4gICBvZiB2b2ljZSwgc3RyZWFt
aW5nIGF1ZGlvIGFuZCB2aWRlby4NCj4NCj4NCj4gQSBVUkwgZm9yIHRoaXMgSW50ZXJuZXQtRHJh
ZnQgaXM6DQo+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWlldGYt
YXZ0Y29yZS1tb25hcmNoLTA2LnR4dA0KPg0KPiBJbnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZh
aWxhYmxlIGJ5IGFub255bW91cyBGVFAgYXQ6DQo+IGZ0cDovL2Z0cC5pZXRmLm9yZy9pbnRlcm5l
dC1kcmFmdHMvDQo+DQo+IFRoaXMgSW50ZXJuZXQtRHJhZnQgY2FuIGJlIHJldHJpZXZlZCBhdDoN
Cj4gZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRmLWF2dGNvcmUt
bW9uYXJjaC0wNi50eHQNCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCj4gSS1ELUFubm91bmNlIG1haWxpbmcgbGlzdA0KPiBJLUQtQW5ub3VuY2VAaWV0
Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pLWQtYW5ub3Vu
Y2UNCj4gSW50ZXJuZXQtRHJhZnQgZGlyZWN0b3JpZXM6IGh0dHA6Ly93d3cuaWV0Zi5vcmcvc2hh
ZG93Lmh0bWwNCj4gb3IgZnRwOi8vZnRwLmlldGYub3JnL2lldGYvMXNoYWRvdy1zaXRlcy50eHQN
Cj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gQXVk
aW8vVmlkZW8gVHJhbnNwb3J0IENvcmUgTWFpbnRlbmFuY2UNCj4gYXZ0QGlldGYub3JnDQo+IGh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vYXZ0

From csp@csperkins.org  Mon Nov 14 22:27:36 2011
Return-Path: <csp@csperkins.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 682CB11E81D5 for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 22:27:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.901
X-Spam-Level: 
X-Spam-Status: No, score=-102.901 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bYJxvPY6T4SM for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 22:27:33 -0800 (PST)
Received: from anchor-msapost-3.mail.demon.net (anchor-msapost-3.mail.demon.net [195.173.77.166]) by ietfa.amsl.com (Postfix) with ESMTP id 984F011E80AB for <avt@ietf.org>; Mon, 14 Nov 2011 22:27:33 -0800 (PST)
Received: from dhcp-20d9.meeting.ietf.org ([130.129.32.217]) by anchor-post-3.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1RQCUV-0004cU-pE; Tue, 15 Nov 2011 06:27:32 +0000
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=utf-8
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA334193@szxeml523-mbs.china.huawei.com>
Date: Tue, 15 Nov 2011 14:27:23 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C03A7F8-66DD-4903-AA8A-715748C3485A@csperkins.org>
References: <20111114002647.19680.14547.idtracker@ietfa.amsl.com> <B8F9A780D330094D99AF023C5877DABA3338A2@szxeml523-mbs.china.huawei.com> <7D0E5A6C-5F70-42BF-B3AB-B405FC37A62E@csperkins.org> <B8F9A780D330094D99AF023C5877DABA334193@szxeml523-mbs.china.huawei.com>
To: Qin Wu <bill.wu@huawei.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-06.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 15 Nov 2011 06:27:36 -0000

Qin,

I think the text added is unnecessary, but acceptable. The main problem =
is that it's in IANA considerations, but there's nothing there that the =
IANA can do. I have no objections if you want to move that text to some =
other section of the document.

Colin

On 15 Nov 2011, at 14:23, Qin Wu wrote:
> Thanks Colin for your review and quick comments.
> As for IANA section, the proposed change is based on Magnus's =
suggestion.
> I am okay to change back if nobody is against having no IANA action.
>=20
> For section 5.3, the answer is yes. Thank for your suggestion.
>=20
> Regards!
> -Qin
> ________________________________________
> =E5=8F=91=E4=BB=B6=E4=BA=BA: Colin Perkins [csp@csperkins.org]
> =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2011=E5=B9=B411=E6=9C=8815=E6=97=A5=
 13:40
> =E5=88=B0: Qin Wu
> Cc: avt@ietf.org
> =E4=B8=BB=E9=A2=98: Re: [AVTCORE] I-D Action: =
draft-ietf-avtcore-monarch-06.txt
>=20
> I have two quick comments on this version.
>=20
> This new IANA Considerations text says:
>=20
>   At the time of writing, the consumption of XR block code points =
isn't
>   a major issue.  However when XR block codes points is really close =
to
>   run out of space, it might be desirable to define new fields encoded
>   as TLV elements in the XR report block or define one XR block type
>   for vendor-specific extensions, with an enterprise number included =
to
>   identify the vendor making the extension.
>=20
> This is not actionable by IANA, so I think it should be changed back =
to the previous wording of "There is no IANA action in this document".
>=20
> Section 5.3 "proposes to define a new XR block". This would probably =
be better phrased as "draft-=E2=80=A6 defines a new XR block", since the =
definition has already happened.
>=20
> Colin
>=20
>=20
> On 14 Nov 2011, at 10:05, Qin Wu wrote:
>> Hi, Folks:
>> We have just submitted a new version of monarch document.
>> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-06.txt
>>=20
>> We talk with chairs and think it has been ready for WGLC.
>> Chairs, would you like to use this version as baseline to raise WGLC?
>>=20
>>=20
>> Regards!
>> -Qin
>> _______________________________________
>> =E5=8F=91=E4=BB=B6=E4=BA=BA: i-d-announce-bounces@ietf.org =
[i-d-announce-bounces@ietf.org] =E4=BB=A3=E8=A1=A8 =
internet-drafts@ietf.org [internet-drafts@ietf.org]
>> =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2011=E5=B9=B411=E6=9C=8814=E6=97=A5=
 8:26
>> =E5=88=B0: i-d-announce@ietf.org
>> Cc: avt@ietf.org
>> =E4=B8=BB=E9=A2=98: I-D Action: draft-ietf-avtcore-monarch-06.txt
>>=20
>> A New Internet-Draft is available from the on-line Internet-Drafts =
directories. This draft is a work item of the Audio/Video Transport Core =
Maintenance Working Group of the IETF.
>>=20
>>       Title           : Monitoring Architectures for RTP
>>       Author(s)       : Qin Wu
>>                         Geoff Hunt
>>                         Philip Arden
>>       Filename        : draft-ietf-avtcore-monarch-06.txt
>>       Pages           : 25
>>       Date            : 2011-11-13
>>=20
>>  This memo proposes an architecture for extending RTCP with a new =
RTCP
>>  XR (RFC3611) block type to report new metrics regarding media
>>  transmission or reception quality, following RTCP guideline
>>  established in RFC5968.  This memo suggests that a new block should
>>  contain a single metric or a small number of metrics relevant to a
>>  single parameter of interest or concern, rather than containing a
>>  number of metrics which attempt to provide full coverage of all =
those
>>  parameters of concern to a specific application.  Applications may
>>  then &quot;mix and match&quot; to create a set of blocks which =
covers their set
>>  of concerns.  Where possible, a specific block should be designed to
>>  be re-usable across more than one application, for example, for all
>>  of voice, streaming audio and video.
>>=20
>>=20
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-06.txt
>>=20
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>=20
>> This Internet-Draft can be retrieved at:
>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-06.txt
>> _______________________________________________
>> 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 Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt



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




From bill.wu@huawei.com  Mon Nov 14 22:37:41 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD3B71F0DCD for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 22:37:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.489
X-Spam-Level: 
X-Spam-Status: No, score=-0.489 tagged_above=-999 required=5 tests=[AWL=-2.938, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F2fbPOCZg0Jg for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 22:37:41 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 5D87B1F0DCA for <avt@ietf.org>; Mon, 14 Nov 2011 22:37:35 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUO007KEVPLWC@szxga04-in.huawei.com> for avt@ietf.org; Tue, 15 Nov 2011 14:36:58 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUO00BFYVPI3P@szxga04-in.huawei.com> for avt@ietf.org; Tue, 15 Nov 2011 14:36:57 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEZ59567; Tue, 15 Nov 2011 14:36:57 +0800
Received: from SZXEML409-HUB.china.huawei.com (10.82.67.136) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 15 Nov 2011 14:36:53 +0800
Received: from SZXEML523-MBS.china.huawei.com ([169.254.6.67]) by szxeml409-hub.china.huawei.com ([10.82.67.136]) with mapi id 14.01.0323.003; Tue, 15 Nov 2011 14:36:47 +0800
Date: Tue, 15 Nov 2011 06:36:46 +0000
From: Qin Wu <bill.wu@huawei.com>
In-reply-to: <6C03A7F8-66DD-4903-AA8A-715748C3485A@csperkins.org>
X-Originating-IP: [172.24.2.41]
To: Colin Perkins <csp@csperkins.org>
Message-id: <B8F9A780D330094D99AF023C5877DABA3341B6@szxeml523-mbs.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=gb2312
Content-language: zh-CN
Content-transfer-encoding: base64
Accept-Language: zh-CN, en-US
Thread-topic: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-06.txt
Thread-index: AQHMomQlgYg5GwZpqEWyT0P+dDCZN5WrnRG+gAFKOACAAJDvb///fCiAgACIaus=
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <20111114002647.19680.14547.idtracker@ietfa.amsl.com> <B8F9A780D330094D99AF023C5877DABA3338A2@szxeml523-mbs.china.huawei.com> <7D0E5A6C-5F70-42BF-B3AB-B405FC37A62E@csperkins.org> <B8F9A780D330094D99AF023C5877DABA334193@szxeml523-mbs.china.huawei.com> <6C03A7F8-66DD-4903-AA8A-715748C3485A@csperkins.org>
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: [AVTCORE] =?gb2312?b?tPC4tDogIEktRCBBY3Rpb246IGRyYWZ0LWlldGYtYXZ0?= =?gb2312?b?Y29yZS1tb25hcmNoLTA2LnR4dA==?=
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 15 Nov 2011 06:37:41 -0000

SSBzZWUgYW5kIGFncmVlLiBUaGFuayBmb3IgeW91ciBjbGFyaWZpY2F0aW9uLg0KDQpyZWdhcmRz
IQ0KLVFpbg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0Kt6K8/sjL
OiBhdnQtYm91bmNlc0BpZXRmLm9yZyBbYXZ0LWJvdW5jZXNAaWV0Zi5vcmddILT6se0gQ29saW4g
UGVya2lucyBbY3NwQGNzcGVya2lucy5vcmddDQq3osvNyrG85DogMjAxMcTqMTHUwjE1yNUgMTQ6
MjcNCrW9OiBRaW4gV3UNCkNjOiBhdnRAaWV0Zi5vcmcNCtb3zOI6IFJlOiBbQVZUQ09SRV0gSS1E
IEFjdGlvbjogZHJhZnQtaWV0Zi1hdnRjb3JlLW1vbmFyY2gtMDYudHh0DQoNClFpbiwNCg0KSSB0
aGluayB0aGUgdGV4dCBhZGRlZCBpcyB1bm5lY2Vzc2FyeSwgYnV0IGFjY2VwdGFibGUuIFRoZSBt
YWluIHByb2JsZW0gaXMgdGhhdCBpdCdzIGluIElBTkEgY29uc2lkZXJhdGlvbnMsIGJ1dCB0aGVy
ZSdzIG5vdGhpbmcgdGhlcmUgdGhhdCB0aGUgSUFOQSBjYW4gZG8uIEkgaGF2ZSBubyBvYmplY3Rp
b25zIGlmIHlvdSB3YW50IHRvIG1vdmUgdGhhdCB0ZXh0IHRvIHNvbWUgb3RoZXIgc2VjdGlvbiBv
ZiB0aGUgZG9jdW1lbnQuDQoNCkNvbGluDQoNCk9uIDE1IE5vdiAyMDExLCBhdCAxNDoyMywgUWlu
IFd1IHdyb3RlOg0KPiBUaGFua3MgQ29saW4gZm9yIHlvdXIgcmV2aWV3IGFuZCBxdWljayBjb21t
ZW50cy4NCj4gQXMgZm9yIElBTkEgc2VjdGlvbiwgdGhlIHByb3Bvc2VkIGNoYW5nZSBpcyBiYXNl
ZCBvbiBNYWdudXMncyBzdWdnZXN0aW9uLg0KPiBJIGFtIG9rYXkgdG8gY2hhbmdlIGJhY2sgaWYg
bm9ib2R5IGlzIGFnYWluc3QgaGF2aW5nIG5vIElBTkEgYWN0aW9uLg0KPg0KPiBGb3Igc2VjdGlv
biA1LjMsIHRoZSBhbnN3ZXIgaXMgeWVzLiBUaGFuayBmb3IgeW91ciBzdWdnZXN0aW9uLg0KPg0K
PiBSZWdhcmRzIQ0KPiAtUWluDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCj4gt6K8/sjLOiBDb2xpbiBQZXJraW5zIFtjc3BAY3NwZXJraW5zLm9yZ10NCj4gt6LL
zcqxvOQ6IDIwMTHE6jEx1MIxNcjVIDEzOjQwDQo+ILW9OiBRaW4gV3UNCj4gQ2M6IGF2dEBpZXRm
Lm9yZw0KPiDW98ziOiBSZTogW0FWVENPUkVdIEktRCBBY3Rpb246IGRyYWZ0LWlldGYtYXZ0Y29y
ZS1tb25hcmNoLTA2LnR4dA0KPg0KPiBJIGhhdmUgdHdvIHF1aWNrIGNvbW1lbnRzIG9uIHRoaXMg
dmVyc2lvbi4NCj4NCj4gVGhpcyBuZXcgSUFOQSBDb25zaWRlcmF0aW9ucyB0ZXh0IHNheXM6DQo+
DQo+ICAgQXQgdGhlIHRpbWUgb2Ygd3JpdGluZywgdGhlIGNvbnN1bXB0aW9uIG9mIFhSIGJsb2Nr
IGNvZGUgcG9pbnRzIGlzbid0DQo+ICAgYSBtYWpvciBpc3N1ZS4gIEhvd2V2ZXIgd2hlbiBYUiBi
bG9jayBjb2RlcyBwb2ludHMgaXMgcmVhbGx5IGNsb3NlIHRvDQo+ICAgcnVuIG91dCBvZiBzcGFj
ZSwgaXQgbWlnaHQgYmUgZGVzaXJhYmxlIHRvIGRlZmluZSBuZXcgZmllbGRzIGVuY29kZWQNCj4g
ICBhcyBUTFYgZWxlbWVudHMgaW4gdGhlIFhSIHJlcG9ydCBibG9jayBvciBkZWZpbmUgb25lIFhS
IGJsb2NrIHR5cGUNCj4gICBmb3IgdmVuZG9yLXNwZWNpZmljIGV4dGVuc2lvbnMsIHdpdGggYW4g
ZW50ZXJwcmlzZSBudW1iZXIgaW5jbHVkZWQgdG8NCj4gICBpZGVudGlmeSB0aGUgdmVuZG9yIG1h
a2luZyB0aGUgZXh0ZW5zaW9uLg0KPg0KPiBUaGlzIGlzIG5vdCBhY3Rpb25hYmxlIGJ5IElBTkEs
IHNvIEkgdGhpbmsgaXQgc2hvdWxkIGJlIGNoYW5nZWQgYmFjayB0byB0aGUgcHJldmlvdXMgd29y
ZGluZyBvZiAiVGhlcmUgaXMgbm8gSUFOQSBhY3Rpb24gaW4gdGhpcyBkb2N1bWVudCIuDQo+DQo+
IFNlY3Rpb24gNS4zICJwcm9wb3NlcyB0byBkZWZpbmUgYSBuZXcgWFIgYmxvY2siLiBUaGlzIHdv
dWxkIHByb2JhYmx5IGJlIGJldHRlciBwaHJhc2VkIGFzICJkcmFmdC2hrSBkZWZpbmVzIGEgbmV3
IFhSIGJsb2NrIiwgc2luY2UgdGhlIGRlZmluaXRpb24gaGFzIGFscmVhZHkgaGFwcGVuZWQuDQo+
DQo+IENvbGluDQo+DQo+DQo+IE9uIDE0IE5vdiAyMDExLCBhdCAxMDowNSwgUWluIFd1IHdyb3Rl
Og0KPj4gSGksIEZvbGtzOg0KPj4gV2UgaGF2ZSBqdXN0IHN1Ym1pdHRlZCBhIG5ldyB2ZXJzaW9u
IG9mIG1vbmFyY2ggZG9jdW1lbnQuDQo+PiBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRy
YWZ0cy9kcmFmdC1pZXRmLWF2dGNvcmUtbW9uYXJjaC0wNi50eHQNCj4+DQo+PiBXZSB0YWxrIHdp
dGggY2hhaXJzIGFuZCB0aGluayBpdCBoYXMgYmVlbiByZWFkeSBmb3IgV0dMQy4NCj4+IENoYWly
cywgd291bGQgeW91IGxpa2UgdG8gdXNlIHRoaXMgdmVyc2lvbiBhcyBiYXNlbGluZSB0byByYWlz
ZSBXR0xDPw0KPj4NCj4+DQo+PiBSZWdhcmRzIQ0KPj4gLVFpbg0KPj4gX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fDQo+PiC3orz+yMs6IGktZC1hbm5vdW5jZS1ib3VuY2Vz
QGlldGYub3JnIFtpLWQtYW5ub3VuY2UtYm91bmNlc0BpZXRmLm9yZ10gtPqx7SBpbnRlcm5ldC1k
cmFmdHNAaWV0Zi5vcmcgW2ludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10NCj4+ILeiy83KsbzkOiAy
MDExxOoxMdTCMTTI1SA4OjI2DQo+PiC1vTogaS1kLWFubm91bmNlQGlldGYub3JnDQo+PiBDYzog
YXZ0QGlldGYub3JnDQo+PiDW98ziOiBJLUQgQWN0aW9uOiBkcmFmdC1pZXRmLWF2dGNvcmUtbW9u
YXJjaC0wNi50eHQNCj4+DQo+PiBBIE5ldyBJbnRlcm5ldC1EcmFmdCBpcyBhdmFpbGFibGUgZnJv
bSB0aGUgb24tbGluZSBJbnRlcm5ldC1EcmFmdHMgZGlyZWN0b3JpZXMuIFRoaXMgZHJhZnQgaXMg
YSB3b3JrIGl0ZW0gb2YgdGhlIEF1ZGlvL1ZpZGVvIFRyYW5zcG9ydCBDb3JlIE1haW50ZW5hbmNl
IFdvcmtpbmcgR3JvdXAgb2YgdGhlIElFVEYuDQo+Pg0KPj4gICAgICAgVGl0bGUgICAgICAgICAg
IDogTW9uaXRvcmluZyBBcmNoaXRlY3R1cmVzIGZvciBSVFANCj4+ICAgICAgIEF1dGhvcihzKSAg
ICAgICA6IFFpbiBXdQ0KPj4gICAgICAgICAgICAgICAgICAgICAgICAgR2VvZmYgSHVudA0KPj4g
ICAgICAgICAgICAgICAgICAgICAgICAgUGhpbGlwIEFyZGVuDQo+PiAgICAgICBGaWxlbmFtZSAg
ICAgICAgOiBkcmFmdC1pZXRmLWF2dGNvcmUtbW9uYXJjaC0wNi50eHQNCj4+ICAgICAgIFBhZ2Vz
ICAgICAgICAgICA6IDI1DQo+PiAgICAgICBEYXRlICAgICAgICAgICAgOiAyMDExLTExLTEzDQo+
Pg0KPj4gIFRoaXMgbWVtbyBwcm9wb3NlcyBhbiBhcmNoaXRlY3R1cmUgZm9yIGV4dGVuZGluZyBS
VENQIHdpdGggYSBuZXcgUlRDUA0KPj4gIFhSIChSRkMzNjExKSBibG9jayB0eXBlIHRvIHJlcG9y
dCBuZXcgbWV0cmljcyByZWdhcmRpbmcgbWVkaWENCj4+ICB0cmFuc21pc3Npb24gb3IgcmVjZXB0
aW9uIHF1YWxpdHksIGZvbGxvd2luZyBSVENQIGd1aWRlbGluZQ0KPj4gIGVzdGFibGlzaGVkIGlu
IFJGQzU5NjguICBUaGlzIG1lbW8gc3VnZ2VzdHMgdGhhdCBhIG5ldyBibG9jayBzaG91bGQNCj4+
ICBjb250YWluIGEgc2luZ2xlIG1ldHJpYyBvciBhIHNtYWxsIG51bWJlciBvZiBtZXRyaWNzIHJl
bGV2YW50IHRvIGENCj4+ICBzaW5nbGUgcGFyYW1ldGVyIG9mIGludGVyZXN0IG9yIGNvbmNlcm4s
IHJhdGhlciB0aGFuIGNvbnRhaW5pbmcgYQ0KPj4gIG51bWJlciBvZiBtZXRyaWNzIHdoaWNoIGF0
dGVtcHQgdG8gcHJvdmlkZSBmdWxsIGNvdmVyYWdlIG9mIGFsbCB0aG9zZQ0KPj4gIHBhcmFtZXRl
cnMgb2YgY29uY2VybiB0byBhIHNwZWNpZmljIGFwcGxpY2F0aW9uLiAgQXBwbGljYXRpb25zIG1h
eQ0KPj4gIHRoZW4gJnF1b3Q7bWl4IGFuZCBtYXRjaCZxdW90OyB0byBjcmVhdGUgYSBzZXQgb2Yg
YmxvY2tzIHdoaWNoIGNvdmVycyB0aGVpciBzZXQNCj4+ICBvZiBjb25jZXJucy4gIFdoZXJlIHBv
c3NpYmxlLCBhIHNwZWNpZmljIGJsb2NrIHNob3VsZCBiZSBkZXNpZ25lZCB0bw0KPj4gIGJlIHJl
LXVzYWJsZSBhY3Jvc3MgbW9yZSB0aGFuIG9uZSBhcHBsaWNhdGlvbiwgZm9yIGV4YW1wbGUsIGZv
ciBhbGwNCj4+ICBvZiB2b2ljZSwgc3RyZWFtaW5nIGF1ZGlvIGFuZCB2aWRlby4NCj4+DQo+Pg0K
Pj4gQSBVUkwgZm9yIHRoaXMgSW50ZXJuZXQtRHJhZnQgaXM6DQo+PiBodHRwOi8vd3d3LmlldGYu
b3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRmLWF2dGNvcmUtbW9uYXJjaC0wNi50eHQNCj4+
DQo+PiBJbnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZhaWxhYmxlIGJ5IGFub255bW91cyBGVFAg
YXQ6DQo+PiBmdHA6Ly9mdHAuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzLw0KPj4NCj4+IFRoaXMg
SW50ZXJuZXQtRHJhZnQgY2FuIGJlIHJldHJpZXZlZCBhdDoNCj4+IGZ0cDovL2Z0cC5pZXRmLm9y
Zy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtaWV0Zi1hdnRjb3JlLW1vbmFyY2gtMDYudHh0DQo+PiBf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4gSS1ELUFu
bm91bmNlIG1haWxpbmcgbGlzdA0KPj4gSS1ELUFubm91bmNlQGlldGYub3JnDQo+PiBodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ktZC1hbm5vdW5jZQ0KPj4gSW50ZXJuZXQt
RHJhZnQgZGlyZWN0b3JpZXM6IGh0dHA6Ly93d3cuaWV0Zi5vcmcvc2hhZG93Lmh0bWwNCj4+IG9y
IGZ0cDovL2Z0cC5pZXRmLm9yZy9pZXRmLzFzaGFkb3ctc2l0ZXMudHh0DQo+PiBfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4gQXVkaW8vVmlkZW8gVHJh
bnNwb3J0IENvcmUgTWFpbnRlbmFuY2UNCj4+IGF2dEBpZXRmLm9yZw0KPj4gaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9hdnQNCg0KDQoNCi0tDQpDb2xpbiBQZXJraW5zDQpo
dHRwOi8vY3NwZXJraW5zLm9yZy8NCg0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fDQpBdWRpby9WaWRlbyBUcmFuc3BvcnQgQ29yZSBNYWludGVuYW5j
ZQ0KYXZ0QGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2F2
dA==

From bill.wu@huawei.com  Mon Nov 14 22:41:01 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E4B711E82FF for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 22:41:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.448
X-Spam-Level: 
X-Spam-Status: No, score=-0.448 tagged_above=-999 required=5 tests=[AWL=-2.897, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ldvVSSpw+XOs for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 22:41:00 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id D2E3211E82FC for <avt@ietf.org>; Mon, 14 Nov 2011 22:40:59 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUO00LB9VUUFP@szxga05-in.huawei.com> for avt@ietf.org; Tue, 15 Nov 2011 14:40:06 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUO00ANDVUQQC@szxga05-in.huawei.com> for avt@ietf.org; Tue, 15 Nov 2011 14:40:06 +0800 (CST)
Received: from szxeml205-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AEZ59825; Tue, 15 Nov 2011 14:39:47 +0800
Received: from SZXEML406-HUB.china.huawei.com (10.82.67.93) by szxeml205-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 15 Nov 2011 14:39:44 +0800
Received: from SZXEML523-MBS.china.huawei.com ([169.254.6.67]) by szxeml406-hub.china.huawei.com ([10.82.67.93]) with mapi id 14.01.0323.003; Tue, 15 Nov 2011 14:39:41 +0800
Date: Tue, 15 Nov 2011 06:39:42 +0000
From: Qin Wu <bill.wu@huawei.com>
In-reply-to: <6C03A7F8-66DD-4903-AA8A-715748C3485A@csperkins.org>
X-Originating-IP: [172.24.2.41]
To: Colin Perkins <csp@csperkins.org>
Message-id: <B8F9A780D330094D99AF023C5877DABA3341A2@szxeml523-mbs.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=gb2312
Content-language: zh-CN
Content-transfer-encoding: base64
Accept-Language: zh-CN, en-US
Thread-topic: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-06.txt
Thread-index: AQHMomQlgYg5GwZpqEWyT0P+dDCZN5WrnRG+gAFKOACAAJDvb///fCiAgACGX4Y=
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <20111114002647.19680.14547.idtracker@ietfa.amsl.com> <B8F9A780D330094D99AF023C5877DABA3338A2@szxeml523-mbs.china.huawei.com> <7D0E5A6C-5F70-42BF-B3AB-B405FC37A62E@csperkins.org> <B8F9A780D330094D99AF023C5877DABA334193@szxeml523-mbs.china.huawei.com> <6C03A7F8-66DD-4903-AA8A-715748C3485A@csperkins.org>
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: [AVTCORE] =?gb2312?b?tPC4tDogIEktRCBBY3Rpb246IGRyYWZ0LWlldGYtYXZ0?= =?gb2312?b?Y29yZS1tb25hcmNoLTA2LnR4dA==?=
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 15 Nov 2011 06:41:01 -0000

SSBzZWUgYW5kIEFncmVlLiBUaGFuayBmb3IgeW91ciBjbGFyaWZpY2F0aW9uLg0KX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0Kt6K8/sjLOiBhdnQtYm91bmNlc0BpZXRm
Lm9yZyBbYXZ0LWJvdW5jZXNAaWV0Zi5vcmddILT6se0gQ29saW4gUGVya2lucyBbY3NwQGNzcGVy
a2lucy5vcmddDQq3osvNyrG85DogMjAxMcTqMTHUwjE1yNUgMTQ6MjcNCrW9OiBRaW4gV3UNCkNj
OiBhdnRAaWV0Zi5vcmcNCtb3zOI6IFJlOiBbQVZUQ09SRV0gSS1EIEFjdGlvbjogZHJhZnQtaWV0
Zi1hdnRjb3JlLW1vbmFyY2gtMDYudHh0DQoNClFpbiwNCg0KSSB0aGluayB0aGUgdGV4dCBhZGRl
ZCBpcyB1bm5lY2Vzc2FyeSwgYnV0IGFjY2VwdGFibGUuIFRoZSBtYWluIHByb2JsZW0gaXMgdGhh
dCBpdCdzIGluIElBTkEgY29uc2lkZXJhdGlvbnMsIGJ1dCB0aGVyZSdzIG5vdGhpbmcgdGhlcmUg
dGhhdCB0aGUgSUFOQSBjYW4gZG8uIEkgaGF2ZSBubyBvYmplY3Rpb25zIGlmIHlvdSB3YW50IHRv
IG1vdmUgdGhhdCB0ZXh0IHRvIHNvbWUgb3RoZXIgc2VjdGlvbiBvZiB0aGUgZG9jdW1lbnQuDQoN
CkNvbGluDQoNCk9uIDE1IE5vdiAyMDExLCBhdCAxNDoyMywgUWluIFd1IHdyb3RlOg0KPiBUaGFu
a3MgQ29saW4gZm9yIHlvdXIgcmV2aWV3IGFuZCBxdWljayBjb21tZW50cy4NCj4gQXMgZm9yIElB
TkEgc2VjdGlvbiwgdGhlIHByb3Bvc2VkIGNoYW5nZSBpcyBiYXNlZCBvbiBNYWdudXMncyBzdWdn
ZXN0aW9uLg0KPiBJIGFtIG9rYXkgdG8gY2hhbmdlIGJhY2sgaWYgbm9ib2R5IGlzIGFnYWluc3Qg
aGF2aW5nIG5vIElBTkEgYWN0aW9uLg0KPg0KPiBGb3Igc2VjdGlvbiA1LjMsIHRoZSBhbnN3ZXIg
aXMgeWVzLiBUaGFuayBmb3IgeW91ciBzdWdnZXN0aW9uLg0KPg0KPiBSZWdhcmRzIQ0KPiAtUWlu
DQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gt6K8/sjLOiBD
b2xpbiBQZXJraW5zIFtjc3BAY3NwZXJraW5zLm9yZ10NCj4gt6LLzcqxvOQ6IDIwMTHE6jEx1MIx
NcjVIDEzOjQwDQo+ILW9OiBRaW4gV3UNCj4gQ2M6IGF2dEBpZXRmLm9yZw0KPiDW98ziOiBSZTog
W0FWVENPUkVdIEktRCBBY3Rpb246IGRyYWZ0LWlldGYtYXZ0Y29yZS1tb25hcmNoLTA2LnR4dA0K
Pg0KPiBJIGhhdmUgdHdvIHF1aWNrIGNvbW1lbnRzIG9uIHRoaXMgdmVyc2lvbi4NCj4NCj4gVGhp
cyBuZXcgSUFOQSBDb25zaWRlcmF0aW9ucyB0ZXh0IHNheXM6DQo+DQo+ICAgQXQgdGhlIHRpbWUg
b2Ygd3JpdGluZywgdGhlIGNvbnN1bXB0aW9uIG9mIFhSIGJsb2NrIGNvZGUgcG9pbnRzIGlzbid0
DQo+ICAgYSBtYWpvciBpc3N1ZS4gIEhvd2V2ZXIgd2hlbiBYUiBibG9jayBjb2RlcyBwb2ludHMg
aXMgcmVhbGx5IGNsb3NlIHRvDQo+ICAgcnVuIG91dCBvZiBzcGFjZSwgaXQgbWlnaHQgYmUgZGVz
aXJhYmxlIHRvIGRlZmluZSBuZXcgZmllbGRzIGVuY29kZWQNCj4gICBhcyBUTFYgZWxlbWVudHMg
aW4gdGhlIFhSIHJlcG9ydCBibG9jayBvciBkZWZpbmUgb25lIFhSIGJsb2NrIHR5cGUNCj4gICBm
b3IgdmVuZG9yLXNwZWNpZmljIGV4dGVuc2lvbnMsIHdpdGggYW4gZW50ZXJwcmlzZSBudW1iZXIg
aW5jbHVkZWQgdG8NCj4gICBpZGVudGlmeSB0aGUgdmVuZG9yIG1ha2luZyB0aGUgZXh0ZW5zaW9u
Lg0KPg0KPiBUaGlzIGlzIG5vdCBhY3Rpb25hYmxlIGJ5IElBTkEsIHNvIEkgdGhpbmsgaXQgc2hv
dWxkIGJlIGNoYW5nZWQgYmFjayB0byB0aGUgcHJldmlvdXMgd29yZGluZyBvZiAiVGhlcmUgaXMg
bm8gSUFOQSBhY3Rpb24gaW4gdGhpcyBkb2N1bWVudCIuDQo+DQo+IFNlY3Rpb24gNS4zICJwcm9w
b3NlcyB0byBkZWZpbmUgYSBuZXcgWFIgYmxvY2siLiBUaGlzIHdvdWxkIHByb2JhYmx5IGJlIGJl
dHRlciBwaHJhc2VkIGFzICJkcmFmdC2hrSBkZWZpbmVzIGEgbmV3IFhSIGJsb2NrIiwgc2luY2Ug
dGhlIGRlZmluaXRpb24gaGFzIGFscmVhZHkgaGFwcGVuZWQuDQo+DQo+IENvbGluDQo+DQo+DQo+
IE9uIDE0IE5vdiAyMDExLCBhdCAxMDowNSwgUWluIFd1IHdyb3RlOg0KPj4gSGksIEZvbGtzOg0K
Pj4gV2UgaGF2ZSBqdXN0IHN1Ym1pdHRlZCBhIG5ldyB2ZXJzaW9uIG9mIG1vbmFyY2ggZG9jdW1l
bnQuDQo+PiBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRmLWF2
dGNvcmUtbW9uYXJjaC0wNi50eHQNCj4+DQo+PiBXZSB0YWxrIHdpdGggY2hhaXJzIGFuZCB0aGlu
ayBpdCBoYXMgYmVlbiByZWFkeSBmb3IgV0dMQy4NCj4+IENoYWlycywgd291bGQgeW91IGxpa2Ug
dG8gdXNlIHRoaXMgdmVyc2lvbiBhcyBiYXNlbGluZSB0byByYWlzZSBXR0xDPw0KPj4NCj4+DQo+
PiBSZWdhcmRzIQ0KPj4gLVFpbg0KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fDQo+PiC3orz+yMs6IGktZC1hbm5vdW5jZS1ib3VuY2VzQGlldGYub3JnIFtpLWQtYW5u
b3VuY2UtYm91bmNlc0BpZXRmLm9yZ10gtPqx7SBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW2lu
dGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10NCj4+ILeiy83KsbzkOiAyMDExxOoxMdTCMTTI1SA4OjI2
DQo+PiC1vTogaS1kLWFubm91bmNlQGlldGYub3JnDQo+PiBDYzogYXZ0QGlldGYub3JnDQo+PiDW
98ziOiBJLUQgQWN0aW9uOiBkcmFmdC1pZXRmLWF2dGNvcmUtbW9uYXJjaC0wNi50eHQNCj4+DQo+
PiBBIE5ldyBJbnRlcm5ldC1EcmFmdCBpcyBhdmFpbGFibGUgZnJvbSB0aGUgb24tbGluZSBJbnRl
cm5ldC1EcmFmdHMgZGlyZWN0b3JpZXMuIFRoaXMgZHJhZnQgaXMgYSB3b3JrIGl0ZW0gb2YgdGhl
IEF1ZGlvL1ZpZGVvIFRyYW5zcG9ydCBDb3JlIE1haW50ZW5hbmNlIFdvcmtpbmcgR3JvdXAgb2Yg
dGhlIElFVEYuDQo+Pg0KPj4gICAgICAgVGl0bGUgICAgICAgICAgIDogTW9uaXRvcmluZyBBcmNo
aXRlY3R1cmVzIGZvciBSVFANCj4+ICAgICAgIEF1dGhvcihzKSAgICAgICA6IFFpbiBXdQ0KPj4g
ICAgICAgICAgICAgICAgICAgICAgICAgR2VvZmYgSHVudA0KPj4gICAgICAgICAgICAgICAgICAg
ICAgICAgUGhpbGlwIEFyZGVuDQo+PiAgICAgICBGaWxlbmFtZSAgICAgICAgOiBkcmFmdC1pZXRm
LWF2dGNvcmUtbW9uYXJjaC0wNi50eHQNCj4+ICAgICAgIFBhZ2VzICAgICAgICAgICA6IDI1DQo+
PiAgICAgICBEYXRlICAgICAgICAgICAgOiAyMDExLTExLTEzDQo+Pg0KPj4gIFRoaXMgbWVtbyBw
cm9wb3NlcyBhbiBhcmNoaXRlY3R1cmUgZm9yIGV4dGVuZGluZyBSVENQIHdpdGggYSBuZXcgUlRD
UA0KPj4gIFhSIChSRkMzNjExKSBibG9jayB0eXBlIHRvIHJlcG9ydCBuZXcgbWV0cmljcyByZWdh
cmRpbmcgbWVkaWENCj4+ICB0cmFuc21pc3Npb24gb3IgcmVjZXB0aW9uIHF1YWxpdHksIGZvbGxv
d2luZyBSVENQIGd1aWRlbGluZQ0KPj4gIGVzdGFibGlzaGVkIGluIFJGQzU5NjguICBUaGlzIG1l
bW8gc3VnZ2VzdHMgdGhhdCBhIG5ldyBibG9jayBzaG91bGQNCj4+ICBjb250YWluIGEgc2luZ2xl
IG1ldHJpYyBvciBhIHNtYWxsIG51bWJlciBvZiBtZXRyaWNzIHJlbGV2YW50IHRvIGENCj4+ICBz
aW5nbGUgcGFyYW1ldGVyIG9mIGludGVyZXN0IG9yIGNvbmNlcm4sIHJhdGhlciB0aGFuIGNvbnRh
aW5pbmcgYQ0KPj4gIG51bWJlciBvZiBtZXRyaWNzIHdoaWNoIGF0dGVtcHQgdG8gcHJvdmlkZSBm
dWxsIGNvdmVyYWdlIG9mIGFsbCB0aG9zZQ0KPj4gIHBhcmFtZXRlcnMgb2YgY29uY2VybiB0byBh
IHNwZWNpZmljIGFwcGxpY2F0aW9uLiAgQXBwbGljYXRpb25zIG1heQ0KPj4gIHRoZW4gJnF1b3Q7
bWl4IGFuZCBtYXRjaCZxdW90OyB0byBjcmVhdGUgYSBzZXQgb2YgYmxvY2tzIHdoaWNoIGNvdmVy
cyB0aGVpciBzZXQNCj4+ICBvZiBjb25jZXJucy4gIFdoZXJlIHBvc3NpYmxlLCBhIHNwZWNpZmlj
IGJsb2NrIHNob3VsZCBiZSBkZXNpZ25lZCB0bw0KPj4gIGJlIHJlLXVzYWJsZSBhY3Jvc3MgbW9y
ZSB0aGFuIG9uZSBhcHBsaWNhdGlvbiwgZm9yIGV4YW1wbGUsIGZvciBhbGwNCj4+ICBvZiB2b2lj
ZSwgc3RyZWFtaW5nIGF1ZGlvIGFuZCB2aWRlby4NCj4+DQo+Pg0KPj4gQSBVUkwgZm9yIHRoaXMg
SW50ZXJuZXQtRHJhZnQgaXM6DQo+PiBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0
cy9kcmFmdC1pZXRmLWF2dGNvcmUtbW9uYXJjaC0wNi50eHQNCj4+DQo+PiBJbnRlcm5ldC1EcmFm
dHMgYXJlIGFsc28gYXZhaWxhYmxlIGJ5IGFub255bW91cyBGVFAgYXQ6DQo+PiBmdHA6Ly9mdHAu
aWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzLw0KPj4NCj4+IFRoaXMgSW50ZXJuZXQtRHJhZnQgY2Fu
IGJlIHJldHJpZXZlZCBhdDoNCj4+IGZ0cDovL2Z0cC5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMv
ZHJhZnQtaWV0Zi1hdnRjb3JlLW1vbmFyY2gtMDYudHh0DQo+PiBfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4gSS1ELUFubm91bmNlIG1haWxpbmcgbGlz
dA0KPj4gSS1ELUFubm91bmNlQGlldGYub3JnDQo+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2ktZC1hbm5vdW5jZQ0KPj4gSW50ZXJuZXQtRHJhZnQgZGlyZWN0b3JpZXM6
IGh0dHA6Ly93d3cuaWV0Zi5vcmcvc2hhZG93Lmh0bWwNCj4+IG9yIGZ0cDovL2Z0cC5pZXRmLm9y
Zy9pZXRmLzFzaGFkb3ctc2l0ZXMudHh0DQo+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KPj4gQXVkaW8vVmlkZW8gVHJhbnNwb3J0IENvcmUgTWFpbnRl
bmFuY2UNCj4+IGF2dEBpZXRmLm9yZw0KPj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9hdnQNCg0KDQoNCi0tDQpDb2xpbiBQZXJraW5zDQpodHRwOi8vY3NwZXJraW5zLm9y
Zy8NCg0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
DQpBdWRpby9WaWRlbyBUcmFuc3BvcnQgQ29yZSBNYWludGVuYW5jZQ0KYXZ0QGlldGYub3JnDQpo
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2F2dA==

From allyn@cisco.com  Tue Nov 15 18:34:01 2011
Return-Path: <allyn@cisco.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4E9A1F0C60 for <avt@ietfa.amsl.com>; Tue, 15 Nov 2011 18:34:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.098
X-Spam-Level: 
X-Spam-Status: No, score=-6.098 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8nunlzHY2XqC for <avt@ietfa.amsl.com>; Tue, 15 Nov 2011 18:33:57 -0800 (PST)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id 4B7BB1F0C6F for <avt@ietf.org>; Tue, 15 Nov 2011 18:33:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=allyn@cisco.com; l=9784; q=dns/txt; s=iport; t=1321410837; x=1322620437; h=mime-version:subject:date:message-id:in-reply-to: references:from:to; bh=fvgl9pJbapswHvxngbgoArJ0Zd+Gdp029H7oQjXzu6s=; b=NbZg4OGOBMgGke2tXLFa7DLNSZX0tQJki8JVSrSpUZLn38EhUuFSHAak DZucVPIkJsvPjkNax1OmJtcg1v8EmI0kEe/MY4jbZc6cUy/l2r9+EGxW+ YCdtBaS0cT/KPs967+zz80QqTZmBJgzzm9UibLAx4lBjzBf8dVDJwkYeE 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnsAACQgw05Io8UT/2dsb2JhbABDgk2CNJRpkAiBBYFyAQEBBBIBCQEEAQsDWQIBCBEEAQELBQEXAQEDAgFFCQgBAQQBEggTB6I2AYxUAZIAiH42YwSIFJFkjFk
X-IronPort-AV: E=Sophos;i="4.69,518,1315180800"; d="scan'208,217";a="3162497"
Received: from bgl-core-4.cisco.com ([72.163.197.19]) by ams-iport-4.cisco.com with ESMTP; 16 Nov 2011 02:33:55 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by bgl-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pAG2WXJl014981; Wed, 16 Nov 2011 02:33:54 GMT
Received: from xmb-sjc-221.amer.cisco.com ([128.107.191.80]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 15 Nov 2011 18:33:04 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCA408.10A266FD"
Date: Tue, 15 Nov 2011 18:33:01 -0800
Message-ID: <9AC2C4348FD86B4BB1F8FA9C5E3A5EDC0625EA61@xmb-sjc-221.amer.cisco.com>
In-Reply-To: <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVTCORE] Call for consensus on multiplexing multipe media streams.
Thread-Index: AcyioJPRabCqeOiXQl2CbkZF1COPHQACpo9sAFWXJOA=
References: <EADCEEE0AE4A7F46BD61061696794D98F753FD@SZXEML519-MBS.china.huawei.com> <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com>
From: "Allyn Romanow (allyn)" <allyn@cisco.com>
To: "Roni even" <Even.roni@huawei.com>, <avt@ietf.org>
X-OriginalArrivalTime: 16 Nov 2011 02:33:04.0159 (UTC) FILETIME=[112A72F0:01CCA408]
Subject: Re: [AVTCORE] Call for consensus on multiplexing multipe media streams.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 16 Nov 2011 02:34:02 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CCA408.10A266FD
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit

I think more discussion  is needed- option 4. 

 

I don$B!G(Jt see any really clear analysis of the pros and cons of 2 and 3 (J-(J despite what is in Magnus$B!G(J draft.

 

Thanks,

Allyn

 

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Roni even
Sent: Monday, November 14, 2011 12:57 AM
To: avt@ietf.org
Subject: [AVTCORE] Call for consensus on multiplexing multipe media streams.

 

Hi

At the AVTcore session we had two presentations. One from Magnus proposing the multiplexing of multiple RTP sessions over a single transport flow and the second from Jonathan Lennox proposing multiplexing multiple media types in a single RTP session.

 

Magnus asked in the beginning of his presentation if the WG believe that the problem of providing multiple RTP sessions over a single transport flow should be solved. The response from the room was that it was already discussed in IETF 81 and there was interest in doing this work. 

In IETF81 there was an interest in doing both options. During the session today we did not have time to ask for consensus.

 

 

So the WG chairs are asking which direction to take 

 

The options we have are:

 

1. Go forward with both solutions.

2. Only define multiplexing of multiple RTP sessions in a single transport flow.

3. Only define multiplexing of multiple media types in a single RTP session.

4. Not enough information in order to decide, more discussion is needed.

 

 

There were about 20 people in the AVTcore session who raised there hands when asked if they have opinion

 

Thanks

Roni Even

AVTcore co-chair

 

$B!!(J

 


------_=_NextPart_001_01CCA408.10A266FD
Content-Type: text/html;
	charset="iso-2022-jp"
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=iso-2022-jp">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style id=owaParaStyle>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:SimSun;}
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;
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:SimSun;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
-->
</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=WordSection1>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I think more discussion &nbsp;is needed- option 4. <o:p></o:p></span></p>

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

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I don$B!G(Bt see any really clear analysis of the pros and cons of 2
and 3 &#8211; despite what is in Magnus$B!G(B draft.<o:p></o:p></span></p>

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

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

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

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

<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>

<div>

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

<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] <b>On Behalf Of </b>Roni
even<br>
<b>Sent:</b> Monday, November 14, 2011 12:57 AM<br>
<b>To:</b> avt@ietf.org<br>
<b>Subject:</b> [AVTCORE] Call for consensus on multiplexing multipe media
streams.<o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<div>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Hi<o:p></o:p></span></p>

<div>

<div>

<div>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>At
the&nbsp;AVTcore session we had two presentations. One from Magnus proposing
the multiplexing of multiple RTP sessions over a single transport flow and the
second from Jonathan Lennox proposing multiplexing multiple media types in a
single RTP session.<o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Magnus
asked in the beginning of his presentation if the WG believe that the problem
of providing multiple RTP sessions over a single transport flow should be
solved. The response from the room was that it was already discussed in IETF 81
and there was interest in doing this work. <o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>In
IETF81 there was an interest in doing both options. During the session today we
did not have time to ask for consensus.<o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>So
the WG chairs are asking which direction to take <o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>The
options we have are:<o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>1.
Go forward with both solutions.<o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>2.
Only define multiplexing of multiple RTP sessions in a single transport flow.<o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>3.
Only define multiplexing of multiple media types in a single RTP session.<o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>4.
Not enough information in order to decide, more discussion is needed.<o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>There
were about 20 people in the&nbsp;AVTcore session who raised there hands when asked
if they have opinion<o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Thanks<o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Roni&nbsp;Even<o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>AVTcore&nbsp;co-chair<o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p>

<p><span lang=ZH-CN style='font-size:10.0pt;color:black'>$B!!(B</span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p></o:p></span></p>

<p><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p>

</div>

</div>

</div>

</div>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01CCA408.10A266FD--

From abegen@cisco.com  Tue Nov 15 18:47:43 2011
Return-Path: <abegen@cisco.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CB5B1F0CBB for <avt@ietfa.amsl.com>; Tue, 15 Nov 2011 18:47:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.31
X-Spam-Level: 
X-Spam-Status: No, score=-5.31 tagged_above=-999 required=5 tests=[AWL=1.289,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8hUw1vxUJgSR for <avt@ietfa.amsl.com>; Tue, 15 Nov 2011 18:47:39 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 8D9881F0CBA for <avt@ietf.org>; Tue, 15 Nov 2011 18:47:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=abegen@cisco.com; l=520; q=dns/txt; s=iport; t=1321411659; x=1322621259; h=mime-version:content-transfer-encoding:subject:date: message-id:from:to; bh=2jL6/1TWx5xSn5cNbMPtiwfMuKKnH0Y62HnTfBc9V5k=; b=LTKzbUEjZJybrIhPLFA6snupa43GvIGcn0KlotjyblPUW/3R12LIUbCg yDr2urOXinOxInlfAoPiWbkvPTgG5zOzids38lomAuGP4foaLaafOYe/h ERwiT5ge/l0kRf4o66In220WtTaGnLtbXirdBSRPD26OxpAtF3zUl/knH o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EANgjw06rRDoG/2dsb2JhbABDhQGkcYEFgXIBAQEDARIBChNODQEIHAYGGAQDVwEEARoTB4dgmkwBjFMIkX6BLIdRN2MEiBSRZIxZ
X-IronPort-AV: E=Sophos;i="4.69,518,1315180800"; d="scan'208";a="14526186"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-4.cisco.com with ESMTP; 16 Nov 2011 02:47:39 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pAG2ld3Z026087; Wed, 16 Nov 2011 02:47:39 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.4675);  Tue, 15 Nov 2011 18:47:39 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 15 Nov 2011 18:47:35 -0800
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D54104F2031@xmb-sjc-215.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Call for consensus on multiplexing multipe media streams.
Thread-Index: AcyioJPRabCqeOiXQl2CbkZF1COPHQACpo9sAFers5A=
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Roni even" <Even.roni@huawei.com>, <avt@ietf.org>
X-OriginalArrivalTime: 16 Nov 2011 02:47:39.0309 (UTC) FILETIME=[1ACBBDD0:01CCA40A]
Subject: Re: [AVTCORE] Call for consensus on multiplexing multipe media streams.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 16 Nov 2011 02:47:43 -0000

> So the WG chairs are asking which direction to take
>=20
>=20
>=20
> The options we have are:
>=20
>=20
>=20
> 1. Go forward with both solutions.
>=20
> 2. Only define multiplexing of multiple RTP sessions in a single =
transport flow.
>=20
> 3. Only define multiplexing of multiple media types in a single RTP =
session.
>=20
> 4. Not enough information in order to decide, more discussion is =
needed.

My preference is (2) but I am also fine with (1) if that is the =
consensus.=20

-acbegen

From matthew@matthew.at  Tue Nov 15 18:52:32 2011
Return-Path: <matthew@matthew.at>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E6FC11E81DB for <avt@ietfa.amsl.com>; Tue, 15 Nov 2011 18:52:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.43
X-Spam-Level: 
X-Spam-Status: No, score=-1.43 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8x4pmnHOLv1U for <avt@ietfa.amsl.com>; Tue, 15 Nov 2011 18:52:31 -0800 (PST)
Received: from where.matthew.at (where.matthew.at [198.202.199.1]) by ietfa.amsl.com (Postfix) with ESMTP id D39AE11E81D2 for <avt@ietf.org>; Tue, 15 Nov 2011 18:52:31 -0800 (PST)
Received: from dhcp-4649.meeting.ietf.org (dhcp-4649.meeting.ietf.org [130.129.70.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by where.matthew.at (Postfix) with ESMTP id D1C96230002; Tue, 15 Nov 2011 18:52:30 -0800 (PST)
Message-ID: <4EC3256A.1030802@matthew.at>
Date: Wed, 16 Nov 2011 10:52:26 +0800
From: Matthew Kaufman <matthew@matthew.at>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: "Ali C. Begen (abegen)" <abegen@cisco.com>
References: <04CAD96D4C5A3D48B1919248A8FE0D54104F2031@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D54104F2031@xmb-sjc-215.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: avt@ietf.org
Subject: Re: [AVTCORE] Call for consensus on multiplexing multipe media streams.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 16 Nov 2011 02:52:32 -0000

On 11/16/11 10:47 AM, Ali C. Begen (abegen) wrote:
>> So the WG chairs are asking which direction to take
>>
>>
>>
>> The options we have are:
>>
>>
>>
>> 1. Go forward with both solutions.
>>
>> 2. Only define multiplexing of multiple RTP sessions in a single transport flow.
>>
>> 3. Only define multiplexing of multiple media types in a single RTP session.
>>
>> 4. Not enough information in order to decide, more discussion is needed.
> My preference is (2) but I am also fine with (1) if that is the consensus.
>
>

(Sorry about tagging on to this point in the thread, but I joined the 
list late)

I'm fine with either 2 or 3, but only because I think that 2 and 3 can 
look exactly the same on the wire and only differ in the semantics... 
and I don't really care which semantics we choose.

I'm not ok with a kind of 2 that isn't wire-equivalent to 3.

Matthew Kaufman

From mary.ietf.barnes@gmail.com  Tue Nov 15 20:48:25 2011
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 720BA11E80CC; Tue, 15 Nov 2011 20:48:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.99
X-Spam-Level: 
X-Spam-Status: No, score=-101.99 tagged_above=-999 required=5 tests=[AWL=-0.841, BAYES_00=-2.599, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XdkBB-PIv-5I; Tue, 15 Nov 2011 20:48:21 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id F058411E80AA; Tue, 15 Nov 2011 20:48:20 -0800 (PST)
Received: by vws16 with SMTP id 16so65746vws.31 for <multiple recipients>; Tue, 15 Nov 2011 20:48:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=ZYfH1+OJQNTrTQ/6HvZq5zkOBRgALINGA6XuGv4eTZ8=; b=pWXpTyjXJtY2SX845/Dy6IiIo+Z9F60L6hOmCUYDhVz6b3XrtWCnisiUo1YCZj1Z9c 7XK3CVLDOV2E9vRz8wD19/8dP+DQf++KHMy2JEjRHQwZz+iZYaJqS/Vp3jHLsV41AQ7x +Vvi5cAL3HzQW4NEd6V/ujKEuFQyzU8GhXLnA=
MIME-Version: 1.0
Received: by 10.52.34.207 with SMTP id b15mr48039916vdj.19.1321418893726; Tue, 15 Nov 2011 20:48:13 -0800 (PST)
Received: by 10.52.175.131 with HTTP; Tue, 15 Nov 2011 20:48:13 -0800 (PST)
Date: Tue, 15 Nov 2011 22:48:13 -0600
Message-ID: <CAHBDyN5Cs7ZuagGLUcYwTgD+mfBtkww19qKuum60f6OGD7ew4A@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: CLUE <clue@ietf.org>, rtcweb@ietf.org, avt@ietf.org
Content-Type: text/plain; charset=Big5
Content-Transfer-Encoding: quoted-printable
Subject: [AVTCORE] Room change for Thursday's adhoc (new room TBA)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 16 Nov 2011 04:48:25 -0000

They usurped our room for this speaker.  The room they offered in
replacement only seats 20.  I will let folks know as soon as I know if
they can get us a bigger room.

Regards,
Mary.

---------- Forwarded message ----------
From: Ray Pelletier <rpelletier@isoc.org>
Date: Tue, Nov 15, 2011 at 10:41 PM
Subject: [82all] Thursday Lunch Speaker: Cloud Computing - Dr.
Yu-Huang Chu (=A6=B6=B7=D4=B7=D7)
To: 82all@ietf.org


All;

Speaker:
Dr. Yu-Huang Chu (=A6=B6=B7=D4=B7=D7)
Senior Researcher of the Broadband Network Laboratory,
Telecommunication Laboratories Chunghwa Telecom Co., Ltd.

Logistics:
       Room:   3F Banquet
       Thursday        17 November
       Time:   12:00 - 12:45
       Note:   Lunch will -not- be served

Description of Topic:

Cloud Computing service is focus on flexibility and elasticity.
Tradition IP/Ethernet network is not easy to satisfy this
requirements. Software Defined Network (SDN) can provide dynamic
provision and modification for individual customer need. The smart
network must provide on demand self-service, secure, unified
management, and mobility. This talk covers SDN, OpenStack and LISP
(Location ID Separation Protocol). These technologies would solve most
of the smart network requirements. Besides, Open software will
dominate the future network development of management system.
OpenStack Software delivers a standard API between Application and
infrastructure. It simplifies Cloud Computing management efforts.

Speaker Bio:

Dr. Michele Mosca obtained his DPhil in 1999 from the University of
Oxford. He is co-founder and the Deputy Director of the Institute for
Quantum Computing at the University of Waterloo, a Professor in the
Department of Combinatorics & Optimization of the Faculty of
Mathematics, and a founding member of Waterloo's Perimeter Institute
for Theoretical Physics.

Dr. Mosca has made major contributions to the theory and practice of
quantum information processing.He has done pioneering work in quantum
algorithms, including the development and application of the phase
estimation approach to quantum algorithms. Together with collaborators
at Oxford, he realized several of the first implementations of quantum
algorithms using nuclear magnetic resonance. In the area of quantum
cryptography, he and his collaborators developed fundamental methods
for performing reliable computations with untrusted quantum apparatus,
defined the notion of private quantum channels, and developed optimal
methods for encrypting quantum information using classical keys. Dr.
Mosca's work is published widely in top journals, and he co-authored
the respected textbook "An Introduction to Quantum Computing" (OUP).

Dr. Mosca has won numerous academic awards and honours, including the
Premier's Research Excellence Award (2000-2005), Fellow of the
Canadian Institute for Advanced Research (CIFAR) since 2010, Canada
Research Chair in Quantum Computation (2002-present), and 2010
Canada's Top 40 Under 40.
_______________________________________________
82all mailing list
82all@ietf.org
https://www.ietf.org/mailman/listinfo/82all

From mary.ietf.barnes@gmail.com  Tue Nov 15 21:04:36 2011
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FDF71F0CEE; Tue, 15 Nov 2011 21:04:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.195
X-Spam-Level: 
X-Spam-Status: No, score=-103.195 tagged_above=-999 required=5 tests=[AWL=0.404, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yPMOBNbPBqRM; Tue, 15 Nov 2011 21:04:32 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id A9EB61F0CE8; Tue, 15 Nov 2011 21:04:20 -0800 (PST)
Received: by vws16 with SMTP id 16so76839vws.31 for <multiple recipients>; Tue, 15 Nov 2011 21:04:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=Mq4BKFaI+8Yzqygkomy2NXqBL48UaQPRNAdT4RX3IEc=; b=mcTYcgT+3+cStftUwTICdFquJGx1isfLy6cKyTMoq70YZvz7C0jEFhBArfTsyDj95a WnNQ9TqkvObt7GU1ykCK8Lkef2ZgE5iVKdeFHGxaWYhkkxqeVVyFoQXOpY6zKUid/HR+ o8Ts1rHlkhwkfT53FqqQtCVfgUOhBcOWCi9qo=
MIME-Version: 1.0
Received: by 10.52.33.140 with SMTP id r12mr48673628vdi.36.1321419859936; Tue, 15 Nov 2011 21:04:19 -0800 (PST)
Received: by 10.52.175.131 with HTTP; Tue, 15 Nov 2011 21:04:19 -0800 (PST)
Date: Tue, 15 Nov 2011 23:04:19 -0600
Message-ID: <CAHBDyN7FQ8iWUE_iDMBq=CY8ysSfhAhaz5eWYY+P1FQNq6VK0Q@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: CLUE <clue@ietf.org>, rtcweb@ietf.org, avt@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: [AVTCORE] Room change for Thursday's adhoc - 101D
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 16 Nov 2011 05:04:36 -0000

The meeting has been moved to 101D.  This room does not officially
allow food. People that eat lunch that might decide to discretely
bring lunch into the room should make sure that they take any
wrappings, containers, etc. back out of the room when they leave.

Thanks,
Mary.

2011/11/15 Mary Barnes <mary.ietf.barnes@gmail.com>:
> They usurped our room for this speaker. =C2=A0The room they offered in
> replacement only seats 20. =C2=A0I will let folks know as soon as I know =
if
> they can get us a bigger room.
>
> Regards,
> Mary.
>
> ---------- Forwarded message ----------
> From: Ray Pelletier <rpelletier@isoc.org>
> Date: Tue, Nov 15, 2011 at 10:41 PM
> Subject: [82all] Thursday Lunch Speaker: Cloud Computing - Dr.
> Yu-Huang Chu (=E6=9C=B1=E7=85=9C=E7=85=8C)
> To: 82all@ietf.org
>
>
> All;
>
> Speaker:
> Dr. Yu-Huang Chu (=E6=9C=B1=E7=85=9C=E7=85=8C)
> Senior Researcher of the Broadband Network Laboratory,
> Telecommunication Laboratories Chunghwa Telecom Co., Ltd.
>
> Logistics:
> =C2=A0 =C2=A0 =C2=A0 Room: =C2=A0 3F Banquet
> =C2=A0 =C2=A0 =C2=A0 Thursday =C2=A0 =C2=A0 =C2=A0 =C2=A017 November
> =C2=A0 =C2=A0 =C2=A0 Time: =C2=A0 12:00 - 12:45
> =C2=A0 =C2=A0 =C2=A0 Note: =C2=A0 Lunch will -not- be served
>
> Description of Topic:
>
> Cloud Computing service is focus on flexibility and elasticity.
> Tradition IP/Ethernet network is not easy to satisfy this
> requirements. Software Defined Network (SDN) can provide dynamic
> provision and modification for individual customer need. The smart
> network must provide on demand self-service, secure, unified
> management, and mobility. This talk covers SDN, OpenStack and LISP
> (Location ID Separation Protocol). These technologies would solve most
> of the smart network requirements. Besides, Open software will
> dominate the future network development of management system.
> OpenStack Software delivers a standard API between Application and
> infrastructure. It simplifies Cloud Computing management efforts.
>
> Speaker Bio:
>
> Dr. Michele Mosca obtained his DPhil in 1999 from the University of
> Oxford. He is co-founder and the Deputy Director of the Institute for
> Quantum Computing at the University of Waterloo, a Professor in the
> Department of Combinatorics & Optimization of the Faculty of
> Mathematics, and a founding member of Waterloo's Perimeter Institute
> for Theoretical Physics.
>
> Dr. Mosca has made major contributions to the theory and practice of
> quantum information processing.He has done pioneering work in quantum
> algorithms, including the development and application of the phase
> estimation approach to quantum algorithms. Together with collaborators
> at Oxford, he realized several of the first implementations of quantum
> algorithms using nuclear magnetic resonance. In the area of quantum
> cryptography, he and his collaborators developed fundamental methods
> for performing reliable computations with untrusted quantum apparatus,
> defined the notion of private quantum channels, and developed optimal
> methods for encrypting quantum information using classical keys. Dr.
> Mosca's work is published widely in top journals, and he co-authored
> the respected textbook "An Introduction to Quantum Computing" (OUP).
>
> Dr. Mosca has won numerous academic awards and honours, including the
> Premier's Research Excellence Award (2000-2005), Fellow of the
> Canadian Institute for Advanced Research (CIFAR) since 2010, Canada
> Research Chair in Quantum Computation (2002-present), and 2010
> Canada's Top 40 Under 40.
> _______________________________________________
> 82all mailing list
> 82all@ietf.org
> https://www.ietf.org/mailman/listinfo/82all
>

From HKaplan@acmepacket.com  Tue Nov 15 21:20:22 2011
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9AD41F0C47; Tue, 15 Nov 2011 21:20:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.474
X-Spam-Level: 
X-Spam-Status: No, score=-2.474 tagged_above=-999 required=5 tests=[AWL=0.125,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LBrHCvRaa-PU; Tue, 15 Nov 2011 21:20:14 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 644EC21F90FD; Tue, 15 Nov 2011 21:20:11 -0800 (PST)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 16 Nov 2011 00:20:08 -0500
Received: from MAIL1.acmepacket.com ([169.254.1.232]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Wed, 16 Nov 2011 00:20:07 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Thread-Topic: [AVTCORE] Room change for Thursday's adhoc - 101D
Thread-Index: AQHMpB9mksrLwJgXZk28a+V//XhybA==
Date: Wed, 16 Nov 2011 05:20:06 +0000
Message-ID: <3EF93494-EB9E-48A8-937E-0FAC7A44194B@acmepacket.com>
References: <CAHBDyN7FQ8iWUE_iDMBq=CY8ysSfhAhaz5eWYY+P1FQNq6VK0Q@mail.gmail.com>
In-Reply-To: <CAHBDyN7FQ8iWUE_iDMBq=CY8ysSfhAhaz5eWYY+P1FQNq6VK0Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="utf-8"
Content-ID: <11E87169561FAB439A4ACF6D7ADD6EB1@acmepacket.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>, CLUE <clue@ietf.org>, "<avt@ietf.org>" <avt@ietf.org>
Subject: Re: [AVTCORE] Room change for Thursday's adhoc - 101D
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 16 Nov 2011 05:20:22 -0000

DQpTbyBkb2VzIDEwMUQgb25seSBzaXQgMjAgcGVvcGxlPyAgSSBkb24ndCBoYXZlIGEgY3J5c3Rh
bCBiYWxsLCBidXQgbXkgZ3Vlc3MgaXMgdGhhdCdzIG5vdCBnb2luZyB0byB3b3JrIGlmIGl0J3Mg
b25seSAyMC4NCg0KLWhhZHJpZWwNCg0KDQpPbiBOb3YgMTYsIDIwMTEsIGF0IDEyOjA0IEFNLCBN
YXJ5IEJhcm5lcyB3cm90ZToNCg0KPiBUaGUgbWVldGluZyBoYXMgYmVlbiBtb3ZlZCB0byAxMDFE
LiAgVGhpcyByb29tIGRvZXMgbm90IG9mZmljaWFsbHkNCj4gYWxsb3cgZm9vZC4gUGVvcGxlIHRo
YXQgZWF0IGx1bmNoIHRoYXQgbWlnaHQgZGVjaWRlIHRvIGRpc2NyZXRlbHkNCj4gYnJpbmcgbHVu
Y2ggaW50byB0aGUgcm9vbSBzaG91bGQgbWFrZSBzdXJlIHRoYXQgdGhleSB0YWtlIGFueQ0KPiB3
cmFwcGluZ3MsIGNvbnRhaW5lcnMsIGV0Yy4gYmFjayBvdXQgb2YgdGhlIHJvb20gd2hlbiB0aGV5
IGxlYXZlLg0KPiANCj4gVGhhbmtzLA0KPiBNYXJ5Lg0KPiANCj4gMjAxMS8xMS8xNSBNYXJ5IEJh
cm5lcyA8bWFyeS5pZXRmLmJhcm5lc0BnbWFpbC5jb20+Og0KPj4gVGhleSB1c3VycGVkIG91ciBy
b29tIGZvciB0aGlzIHNwZWFrZXIuICBUaGUgcm9vbSB0aGV5IG9mZmVyZWQgaW4NCj4+IHJlcGxh
Y2VtZW50IG9ubHkgc2VhdHMgMjAuICBJIHdpbGwgbGV0IGZvbGtzIGtub3cgYXMgc29vbiBhcyBJ
IGtub3cgaWYNCj4+IHRoZXkgY2FuIGdldCB1cyBhIGJpZ2dlciByb29tLg0KPj4gDQo+PiBSZWdh
cmRzLA0KPj4gTWFyeS4NCj4+IA0KPj4gLS0tLS0tLS0tLSBGb3J3YXJkZWQgbWVzc2FnZSAtLS0t
LS0tLS0tDQo+PiBGcm9tOiBSYXkgUGVsbGV0aWVyIDxycGVsbGV0aWVyQGlzb2Mub3JnPg0KPj4g
RGF0ZTogVHVlLCBOb3YgMTUsIDIwMTEgYXQgMTA6NDEgUE0NCj4+IFN1YmplY3Q6IFs4MmFsbF0g
VGh1cnNkYXkgTHVuY2ggU3BlYWtlcjogQ2xvdWQgQ29tcHV0aW5nIC0gRHIuDQo+PiBZdS1IdWFu
ZyBDaHUgKOacseeFnOeFjCkNCj4+IFRvOiA4MmFsbEBpZXRmLm9yZw0KPj4gDQo+PiANCj4+IEFs
bDsNCj4+IA0KPj4gU3BlYWtlcjoNCj4+IERyLiBZdS1IdWFuZyBDaHUgKOacseeFnOeFjCkNCj4+
IFNlbmlvciBSZXNlYXJjaGVyIG9mIHRoZSBCcm9hZGJhbmQgTmV0d29yayBMYWJvcmF0b3J5LA0K
Pj4gVGVsZWNvbW11bmljYXRpb24gTGFib3JhdG9yaWVzIENodW5naHdhIFRlbGVjb20gQ28uLCBM
dGQuDQo+PiANCj4+IExvZ2lzdGljczoNCj4+ICAgICAgIFJvb206ICAgM0YgQmFucXVldA0KPj4g
ICAgICAgVGh1cnNkYXkgICAgICAgIDE3IE5vdmVtYmVyDQo+PiAgICAgICBUaW1lOiAgIDEyOjAw
IC0gMTI6NDUNCj4+ICAgICAgIE5vdGU6ICAgTHVuY2ggd2lsbCAtbm90LSBiZSBzZXJ2ZWQNCj4+
IA0KPj4gRGVzY3JpcHRpb24gb2YgVG9waWM6DQo+PiANCj4+IENsb3VkIENvbXB1dGluZyBzZXJ2
aWNlIGlzIGZvY3VzIG9uIGZsZXhpYmlsaXR5IGFuZCBlbGFzdGljaXR5Lg0KPj4gVHJhZGl0aW9u
IElQL0V0aGVybmV0IG5ldHdvcmsgaXMgbm90IGVhc3kgdG8gc2F0aXNmeSB0aGlzDQo+PiByZXF1
aXJlbWVudHMuIFNvZnR3YXJlIERlZmluZWQgTmV0d29yayAoU0ROKSBjYW4gcHJvdmlkZSBkeW5h
bWljDQo+PiBwcm92aXNpb24gYW5kIG1vZGlmaWNhdGlvbiBmb3IgaW5kaXZpZHVhbCBjdXN0b21l
ciBuZWVkLiBUaGUgc21hcnQNCj4+IG5ldHdvcmsgbXVzdCBwcm92aWRlIG9uIGRlbWFuZCBzZWxm
LXNlcnZpY2UsIHNlY3VyZSwgdW5pZmllZA0KPj4gbWFuYWdlbWVudCwgYW5kIG1vYmlsaXR5LiBU
aGlzIHRhbGsgY292ZXJzIFNETiwgT3BlblN0YWNrIGFuZCBMSVNQDQo+PiAoTG9jYXRpb24gSUQg
U2VwYXJhdGlvbiBQcm90b2NvbCkuIFRoZXNlIHRlY2hub2xvZ2llcyB3b3VsZCBzb2x2ZSBtb3N0
DQo+PiBvZiB0aGUgc21hcnQgbmV0d29yayByZXF1aXJlbWVudHMuIEJlc2lkZXMsIE9wZW4gc29m
dHdhcmUgd2lsbA0KPj4gZG9taW5hdGUgdGhlIGZ1dHVyZSBuZXR3b3JrIGRldmVsb3BtZW50IG9m
IG1hbmFnZW1lbnQgc3lzdGVtLg0KPj4gT3BlblN0YWNrIFNvZnR3YXJlIGRlbGl2ZXJzIGEgc3Rh
bmRhcmQgQVBJIGJldHdlZW4gQXBwbGljYXRpb24gYW5kDQo+PiBpbmZyYXN0cnVjdHVyZS4gSXQg
c2ltcGxpZmllcyBDbG91ZCBDb21wdXRpbmcgbWFuYWdlbWVudCBlZmZvcnRzLg0KPj4gDQo+PiBT
cGVha2VyIEJpbzoNCj4+IA0KPj4gRHIuIE1pY2hlbGUgTW9zY2Egb2J0YWluZWQgaGlzIERQaGls
IGluIDE5OTkgZnJvbSB0aGUgVW5pdmVyc2l0eSBvZg0KPj4gT3hmb3JkLiBIZSBpcyBjby1mb3Vu
ZGVyIGFuZCB0aGUgRGVwdXR5IERpcmVjdG9yIG9mIHRoZSBJbnN0aXR1dGUgZm9yDQo+PiBRdWFu
dHVtIENvbXB1dGluZyBhdCB0aGUgVW5pdmVyc2l0eSBvZiBXYXRlcmxvbywgYSBQcm9mZXNzb3Ig
aW4gdGhlDQo+PiBEZXBhcnRtZW50IG9mIENvbWJpbmF0b3JpY3MgJiBPcHRpbWl6YXRpb24gb2Yg
dGhlIEZhY3VsdHkgb2YNCj4+IE1hdGhlbWF0aWNzLCBhbmQgYSBmb3VuZGluZyBtZW1iZXIgb2Yg
V2F0ZXJsb28ncyBQZXJpbWV0ZXIgSW5zdGl0dXRlDQo+PiBmb3IgVGhlb3JldGljYWwgUGh5c2lj
cy4NCj4+IA0KPj4gRHIuIE1vc2NhIGhhcyBtYWRlIG1ham9yIGNvbnRyaWJ1dGlvbnMgdG8gdGhl
IHRoZW9yeSBhbmQgcHJhY3RpY2Ugb2YNCj4+IHF1YW50dW0gaW5mb3JtYXRpb24gcHJvY2Vzc2lu
Zy5IZSBoYXMgZG9uZSBwaW9uZWVyaW5nIHdvcmsgaW4gcXVhbnR1bQ0KPj4gYWxnb3JpdGhtcywg
aW5jbHVkaW5nIHRoZSBkZXZlbG9wbWVudCBhbmQgYXBwbGljYXRpb24gb2YgdGhlIHBoYXNlDQo+
PiBlc3RpbWF0aW9uIGFwcHJvYWNoIHRvIHF1YW50dW0gYWxnb3JpdGhtcy4gVG9nZXRoZXIgd2l0
aCBjb2xsYWJvcmF0b3JzDQo+PiBhdCBPeGZvcmQsIGhlIHJlYWxpemVkIHNldmVyYWwgb2YgdGhl
IGZpcnN0IGltcGxlbWVudGF0aW9ucyBvZiBxdWFudHVtDQo+PiBhbGdvcml0aG1zIHVzaW5nIG51
Y2xlYXIgbWFnbmV0aWMgcmVzb25hbmNlLiBJbiB0aGUgYXJlYSBvZiBxdWFudHVtDQo+PiBjcnlw
dG9ncmFwaHksIGhlIGFuZCBoaXMgY29sbGFib3JhdG9ycyBkZXZlbG9wZWQgZnVuZGFtZW50YWwg
bWV0aG9kcw0KPj4gZm9yIHBlcmZvcm1pbmcgcmVsaWFibGUgY29tcHV0YXRpb25zIHdpdGggdW50
cnVzdGVkIHF1YW50dW0gYXBwYXJhdHVzLA0KPj4gZGVmaW5lZCB0aGUgbm90aW9uIG9mIHByaXZh
dGUgcXVhbnR1bSBjaGFubmVscywgYW5kIGRldmVsb3BlZCBvcHRpbWFsDQo+PiBtZXRob2RzIGZv
ciBlbmNyeXB0aW5nIHF1YW50dW0gaW5mb3JtYXRpb24gdXNpbmcgY2xhc3NpY2FsIGtleXMuIERy
Lg0KPj4gTW9zY2EncyB3b3JrIGlzIHB1Ymxpc2hlZCB3aWRlbHkgaW4gdG9wIGpvdXJuYWxzLCBh
bmQgaGUgY28tYXV0aG9yZWQNCj4+IHRoZSByZXNwZWN0ZWQgdGV4dGJvb2sgIkFuIEludHJvZHVj
dGlvbiB0byBRdWFudHVtIENvbXB1dGluZyIgKE9VUCkuDQo+PiANCj4+IERyLiBNb3NjYSBoYXMg
d29uIG51bWVyb3VzIGFjYWRlbWljIGF3YXJkcyBhbmQgaG9ub3VycywgaW5jbHVkaW5nIHRoZQ0K
Pj4gUHJlbWllcidzIFJlc2VhcmNoIEV4Y2VsbGVuY2UgQXdhcmQgKDIwMDAtMjAwNSksIEZlbGxv
dyBvZiB0aGUNCj4+IENhbmFkaWFuIEluc3RpdHV0ZSBmb3IgQWR2YW5jZWQgUmVzZWFyY2ggKENJ
RkFSKSBzaW5jZSAyMDEwLCBDYW5hZGENCj4+IFJlc2VhcmNoIENoYWlyIGluIFF1YW50dW0gQ29t
cHV0YXRpb24gKDIwMDItcHJlc2VudCksIGFuZCAyMDEwDQo+PiBDYW5hZGEncyBUb3AgNDAgVW5k
ZXIgNDAuDQo+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KPj4gODJhbGwgbWFpbGluZyBsaXN0DQo+PiA4MmFsbEBpZXRmLm9yZw0KPj4gaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby84MmFsbA0KPj4gDQo+IF9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IEF1ZGlvL1ZpZGVvIFRyYW5zcG9y
dCBDb3JlIE1haW50ZW5hbmNlDQo+IGF2dEBpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL2F2dA0KDQo=

From HKaplan@acmepacket.com  Tue Nov 15 21:44:27 2011
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 329E611E80F5 for <avt@ietfa.amsl.com>; Tue, 15 Nov 2011 21:44:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.475
X-Spam-Level: 
X-Spam-Status: No, score=-2.475 tagged_above=-999 required=5 tests=[AWL=0.124,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oste9BOH-mhB for <avt@ietfa.amsl.com>; Tue, 15 Nov 2011 21:44:23 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 06FF211E80AC for <avt@ietf.org>; Tue, 15 Nov 2011 21:44:19 -0800 (PST)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 16 Nov 2011 00:44:15 -0500
Received: from MAIL1.acmepacket.com ([169.254.1.232]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Wed, 16 Nov 2011 00:44:15 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "avt@ietf.org" <avt@ietf.org>
Thread-Topic: [AVTCORE] Call for consensus on multiplexing multipe media streams.
Thread-Index: AQHMpCLGfEXn7itReEK3Hpfb/SQOWg==
Date: Wed, 16 Nov 2011 05:44:14 +0000
Message-ID: <5ABEAD38-E871-4CA6-8A3F-632FFD15369A@acmepacket.com>
References: <04CAD96D4C5A3D48B1919248A8FE0D54104F2031@xmb-sjc-215.amer.cisco.com> <4EC3256A.1030802@matthew.at>
In-Reply-To: <4EC3256A.1030802@matthew.at>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <EE8A4681DAE4A143A11DFE02EF4F48A0@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Subject: Re: [AVTCORE] Call for consensus on multiplexing multipe media	streams.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 16 Nov 2011 05:44:27 -0000

If what Matthew says is true, that 2 and 3 are on-the-wire equivalent, then=
 I'm totally confused by the choices now.

Can the chairs please clarifies what the consensus call options mean? =20

In particular, can you do so by indicating actual drafts, rather than using=
 high-level terminology?

-hadriel


On Nov 15, 2011, at 9:52 PM, Matthew Kaufman wrote:

> On 11/16/11 10:47 AM, Ali C. Begen (abegen) wrote:
>>> So the WG chairs are asking which direction to take
>>>=20
>>>=20
>>>=20
>>> The options we have are:
>>>=20
>>>=20
>>>=20
>>> 1. Go forward with both solutions.
>>>=20
>>> 2. Only define multiplexing of multiple RTP sessions in a single transp=
ort flow.
>>>=20
>>> 3. Only define multiplexing of multiple media types in a single RTP ses=
sion.
>>>=20
>>> 4. Not enough information in order to decide, more discussion is needed=
.
>> My preference is (2) but I am also fine with (1) if that is the consensu=
s.
>>=20
>>=20
>=20
> (Sorry about tagging on to this point in the thread, but I joined the lis=
t late)
>=20
> I'm fine with either 2 or 3, but only because I think that 2 and 3 can lo=
ok exactly the same on the wire and only differ in the semantics... and I d=
on't really care which semantics we choose.
>=20
> I'm not ok with a kind of 2 that isn't wire-equivalent to 3.
>=20
> Matthew Kaufman
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From mary.ietf.barnes@gmail.com  Tue Nov 15 21:48:49 2011
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B87CA21F91F3; Tue, 15 Nov 2011 21:48:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.205
X-Spam-Level: 
X-Spam-Status: No, score=-103.205 tagged_above=-999 required=5 tests=[AWL=0.394, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id isZdx+UYInq3; Tue, 15 Nov 2011 21:48:45 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id D67B021F9205; Tue, 15 Nov 2011 21:48:44 -0800 (PST)
Received: by vws16 with SMTP id 16so108746vws.31 for <multiple recipients>; Tue, 15 Nov 2011 21:48:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=pfUCKdKcK3kdZfIpQBKy/ixEWx2MU4PS4vKrD7R2XBY=; b=rKzm6Q+E33HPStEvS515LePk0hHZ7YqKQsB4LbgkfQGd0nqirWrgp6Cdilbys1EIhH NWYsxAjUxwNfXUXJ70ED6vNxTQ9SqCd1BhjKP9savSl7/pLb9pB82p0gXiK4taezECnI 4uxHFzoGtwFCC7TIw80GMbMciQrTMF+Egtklo=
MIME-Version: 1.0
Received: by 10.52.34.207 with SMTP id b15mr48326332vdj.19.1321422524153; Tue, 15 Nov 2011 21:48:44 -0800 (PST)
Received: by 10.52.175.131 with HTTP; Tue, 15 Nov 2011 21:48:44 -0800 (PST)
In-Reply-To: <3EF93494-EB9E-48A8-937E-0FAC7A44194B@acmepacket.com>
References: <CAHBDyN7FQ8iWUE_iDMBq=CY8ysSfhAhaz5eWYY+P1FQNq6VK0Q@mail.gmail.com> <3EF93494-EB9E-48A8-937E-0FAC7A44194B@acmepacket.com>
Date: Tue, 15 Nov 2011 23:48:44 -0600
Message-ID: <CAHBDyN5hVOLZbZ3CY2DKjkRoaOZCNb1=MaFmDw-oykTjqv8b4Q@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>, CLUE <clue@ietf.org>, "<avt@ietf.org>" <avt@ietf.org>
Subject: Re: [AVTCORE] Room change for Thursday's adhoc - 101D
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 16 Nov 2011 05:48:49 -0000

No, I rejected the 20 seat room. This room is purported to hold 80.

Mary.

On Tue, Nov 15, 2011 at 11:20 PM, Hadriel Kaplan <HKaplan@acmepacket.com> w=
rote:
>
> So does 101D only sit 20 people? =C2=A0I don't have a crystal ball, but m=
y guess is that's not going to work if it's only 20.
>
> -hadriel
>
>
> On Nov 16, 2011, at 12:04 AM, Mary Barnes wrote:
>
>> The meeting has been moved to 101D. =C2=A0This room does not officially
>> allow food. People that eat lunch that might decide to discretely
>> bring lunch into the room should make sure that they take any
>> wrappings, containers, etc. back out of the room when they leave.
>>
>> Thanks,
>> Mary.
>>
>> 2011/11/15 Mary Barnes <mary.ietf.barnes@gmail.com>:
>>> They usurped our room for this speaker. =C2=A0The room they offered in
>>> replacement only seats 20. =C2=A0I will let folks know as soon as I kno=
w if
>>> they can get us a bigger room.
>>>
>>> Regards,
>>> Mary.
>>>
>>> ---------- Forwarded message ----------
>>> From: Ray Pelletier <rpelletier@isoc.org>
>>> Date: Tue, Nov 15, 2011 at 10:41 PM
>>> Subject: [82all] Thursday Lunch Speaker: Cloud Computing - Dr.
>>> Yu-Huang Chu (=E6=9C=B1=E7=85=9C=E7=85=8C)
>>> To: 82all@ietf.org
>>>
>>>
>>> All;
>>>
>>> Speaker:
>>> Dr. Yu-Huang Chu (=E6=9C=B1=E7=85=9C=E7=85=8C)
>>> Senior Researcher of the Broadband Network Laboratory,
>>> Telecommunication Laboratories Chunghwa Telecom Co., Ltd.
>>>
>>> Logistics:
>>> =C2=A0 =C2=A0 =C2=A0 Room: =C2=A0 3F Banquet
>>> =C2=A0 =C2=A0 =C2=A0 Thursday =C2=A0 =C2=A0 =C2=A0 =C2=A017 November
>>> =C2=A0 =C2=A0 =C2=A0 Time: =C2=A0 12:00 - 12:45
>>> =C2=A0 =C2=A0 =C2=A0 Note: =C2=A0 Lunch will -not- be served
>>>
>>> Description of Topic:
>>>
>>> Cloud Computing service is focus on flexibility and elasticity.
>>> Tradition IP/Ethernet network is not easy to satisfy this
>>> requirements. Software Defined Network (SDN) can provide dynamic
>>> provision and modification for individual customer need. The smart
>>> network must provide on demand self-service, secure, unified
>>> management, and mobility. This talk covers SDN, OpenStack and LISP
>>> (Location ID Separation Protocol). These technologies would solve most
>>> of the smart network requirements. Besides, Open software will
>>> dominate the future network development of management system.
>>> OpenStack Software delivers a standard API between Application and
>>> infrastructure. It simplifies Cloud Computing management efforts.
>>>
>>> Speaker Bio:
>>>
>>> Dr. Michele Mosca obtained his DPhil in 1999 from the University of
>>> Oxford. He is co-founder and the Deputy Director of the Institute for
>>> Quantum Computing at the University of Waterloo, a Professor in the
>>> Department of Combinatorics & Optimization of the Faculty of
>>> Mathematics, and a founding member of Waterloo's Perimeter Institute
>>> for Theoretical Physics.
>>>
>>> Dr. Mosca has made major contributions to the theory and practice of
>>> quantum information processing.He has done pioneering work in quantum
>>> algorithms, including the development and application of the phase
>>> estimation approach to quantum algorithms. Together with collaborators
>>> at Oxford, he realized several of the first implementations of quantum
>>> algorithms using nuclear magnetic resonance. In the area of quantum
>>> cryptography, he and his collaborators developed fundamental methods
>>> for performing reliable computations with untrusted quantum apparatus,
>>> defined the notion of private quantum channels, and developed optimal
>>> methods for encrypting quantum information using classical keys. Dr.
>>> Mosca's work is published widely in top journals, and he co-authored
>>> the respected textbook "An Introduction to Quantum Computing" (OUP).
>>>
>>> Dr. Mosca has won numerous academic awards and honours, including the
>>> Premier's Research Excellence Award (2000-2005), Fellow of the
>>> Canadian Institute for Advanced Research (CIFAR) since 2010, Canada
>>> Research Chair in Quantum Computation (2002-present), and 2010
>>> Canada's Top 40 Under 40.
>>> _______________________________________________
>>> 82all mailing list
>>> 82all@ietf.org
>>> https://www.ietf.org/mailman/listinfo/82all
>>>
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>
>

From ron.even.tlv@gmail.com  Tue Nov 15 22:17:36 2011
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2036E11E80E0 for <avt@ietfa.amsl.com>; Tue, 15 Nov 2011 22:17:36 -0800 (PST)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fekYwsBdZxOa for <avt@ietfa.amsl.com>; Tue, 15 Nov 2011 22:17:32 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id F398011E812F for <avt@ietf.org>; Tue, 15 Nov 2011 22:17:31 -0800 (PST)
Received: by ggnr5 with SMTP id r5so3640756ggn.31 for <avt@ietf.org>; Tue, 15 Nov 2011 22:17:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :content-language; bh=8ZkFtjWjfQvK3r8h8QT0BFYRiiDFpsuEV9eHhWSZzXU=; b=wD10BxLIq9X5RO9GZ4O+jY/rjbnRyOTHEowUa2O6MckAsdPrWqjq3lDjs/uGrbiROT THpx40Xioktq+K+u6yK2p5ZMAgeG16BiA62OhFtlm+3Z44q7YZaOhJhfFr2ARoBxa4IG sDKYvtOb0wPs9VG2jBFadA0VaeNMLx40Voy6k=
Received: by 10.101.193.31 with SMTP id v31mr9769692anp.30.1321424251391; Tue, 15 Nov 2011 22:17:31 -0800 (PST)
Received: from windows8d787f9 (dhcp-17b3.meeting.ietf.org. [130.129.23.179]) by mx.google.com with ESMTPS id h28sm23616199ani.17.2011.11.15.22.17.29 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Nov 2011 22:17:30 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Hadriel Kaplan'" <HKaplan@acmepacket.com>, <avt@ietf.org>
References: <04CAD96D4C5A3D48B1919248A8FE0D54104F2031@xmb-sjc-215.amer.cisco.com>	<4EC3256A.1030802@matthew.at> <5ABEAD38-E871-4CA6-8A3F-632FFD15369A@acmepacket.com>
In-Reply-To: <5ABEAD38-E871-4CA6-8A3F-632FFD15369A@acmepacket.com>
Date: Wed, 16 Nov 2011 08:14:48 +0200
Message-ID: <4ec3557a.1c05650a.2f07.7d11@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHMpCLGfEXn7itReEK3Hpfb/SQOWpWvAt0g
Content-Language: en-us
Subject: Re: [AVTCORE] Call for consensus on multiplexing multipe	media	streams.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 16 Nov 2011 06:17:36 -0000

Hi Hadriel,
There is background information about the different multiplexing in
http://tools.ietf.org/html/draft-westerlund-avtcore-multiplex-architecture-0
0 
I would like to say that this is an individual draft does not reflect
consensus of the WG. Sections 3 till 6 provide the overview that may be
helpful for you.

As a WG chair I cannot comment on  sections 7-9 but they are relevant but
caused discussion.

The different proposals are in

http://tools.ietf.org/html/draft-westerlund-avtcore-transport-multiplexing-0
1 for option 2
 
and 

http://tools.ietf.org/id/draft-lennox-rtcweb-rtp-media-type-mux-00.txt for
option 3


All the documents were discussed in the AVTcore session.


Roni Even
AVT co-chair


> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Hadriel Kaplan
> Sent: Wednesday, November 16, 2011 7:44 AM
> To: avt@ietf.org
> Subject: Re: [AVTCORE] Call for consensus on multiplexing multipe media
> streams.
> 
> 
> If what Matthew says is true, that 2 and 3 are on-the-wire equivalent,
> then I'm totally confused by the choices now.
> 
> Can the chairs please clarifies what the consensus call options mean?
> 
> In particular, can you do so by indicating actual drafts, rather than
> using high-level terminology?
> 
> -hadriel
> 
> 
> On Nov 15, 2011, at 9:52 PM, Matthew Kaufman wrote:
> 
> > On 11/16/11 10:47 AM, Ali C. Begen (abegen) wrote:
> >>> So the WG chairs are asking which direction to take
> >>>
> >>>
> >>>
> >>> The options we have are:
> >>>
> >>>
> >>>
> >>> 1. Go forward with both solutions.
> >>>
> >>> 2. Only define multiplexing of multiple RTP sessions in a single
> transport flow.
> >>>
> >>> 3. Only define multiplexing of multiple media types in a single RTP
> session.
> >>>
> >>> 4. Not enough information in order to decide, more discussion is
> needed.
> >> My preference is (2) but I am also fine with (1) if that is the
> consensus.
> >>
> >>
> >
> > (Sorry about tagging on to this point in the thread, but I joined the
> > list late)
> >
> > I'm fine with either 2 or 3, but only because I think that 2 and 3
> can look exactly the same on the wire and only differ in the
> semantics... and I don't really care which semantics we choose.
> >
> > I'm not ok with a kind of 2 that isn't wire-equivalent to 3.
> >
> > Matthew Kaufman
> > _______________________________________________
> > Audio/Video Transport Core Maintenance avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From HKaplan@acmepacket.com  Tue Nov 15 22:42:17 2011
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CB471F0C4A for <avt@ietfa.amsl.com>; Tue, 15 Nov 2011 22:42:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.476
X-Spam-Level: 
X-Spam-Status: No, score=-2.476 tagged_above=-999 required=5 tests=[AWL=0.123,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eHjMJThuKF8E for <avt@ietfa.amsl.com>; Tue, 15 Nov 2011 22:42:13 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 67D101F0C5D for <avt@ietf.org>; Tue, 15 Nov 2011 22:42:13 -0800 (PST)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 16 Nov 2011 01:42:12 -0500
Received: from MAIL1.acmepacket.com ([169.254.1.232]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Wed, 16 Nov 2011 01:42:12 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Roni Even <ron.even.tlv@gmail.com>
Thread-Topic: [AVTCORE] Call for consensus on multiplexing multipe	media streams.
Thread-Index: AQHMpCrenylke9Cqx0KuKib+4n5omA==
Date: Wed, 16 Nov 2011 06:42:11 +0000
Message-ID: <4FECDC5A-6393-4D73-9965-C9AE60391A56@acmepacket.com>
References: <04CAD96D4C5A3D48B1919248A8FE0D54104F2031@xmb-sjc-215.amer.cisco.com> <4EC3256A.1030802@matthew.at> <5ABEAD38-E871-4CA6-8A3F-632FFD15369A@acmepacket.com> <4ec3557a.1c05650a.2f07.7d11@mx.google.com>
In-Reply-To: <4ec3557a.1c05650a.2f07.7d11@mx.google.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <367A61A557AD4B40979C14B3ACB691BE@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "<avt@ietf.org>" <avt@ietf.org>
Subject: Re: [AVTCORE] Call for consensus on multiplexing multipe	media	streams.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 16 Nov 2011 06:42:17 -0000

OK, so that's how I had also interpreted the original consensus-call email =
options.
Thank you for the clarification.

-hadriel


On Nov 16, 2011, at 1:14 AM, Roni Even wrote:

> Hi Hadriel,
> There is background information about the different multiplexing in
> http://tools.ietf.org/html/draft-westerlund-avtcore-multiplex-architectur=
e-0
> 0=20
> I would like to say that this is an individual draft does not reflect
> consensus of the WG. Sections 3 till 6 provide the overview that may be
> helpful for you.
>=20
> As a WG chair I cannot comment on  sections 7-9 but they are relevant but
> caused discussion.
>=20
> The different proposals are in
>=20
> http://tools.ietf.org/html/draft-westerlund-avtcore-transport-multiplexin=
g-0
> 1 for option 2
>=20
> and=20
>=20
> http://tools.ietf.org/id/draft-lennox-rtcweb-rtp-media-type-mux-00.txt fo=
r
> option 3
>=20
>=20
> All the documents were discussed in the AVTcore session.
>=20
>=20
> Roni Even
> AVT co-chair
>=20
>=20
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
>> Hadriel Kaplan
>> Sent: Wednesday, November 16, 2011 7:44 AM
>> To: avt@ietf.org
>> Subject: Re: [AVTCORE] Call for consensus on multiplexing multipe media
>> streams.
>>=20
>>=20
>> If what Matthew says is true, that 2 and 3 are on-the-wire equivalent,
>> then I'm totally confused by the choices now.
>>=20
>> Can the chairs please clarifies what the consensus call options mean?
>>=20
>> In particular, can you do so by indicating actual drafts, rather than
>> using high-level terminology?
>>=20
>> -hadriel
>>=20
>>=20
>> On Nov 15, 2011, at 9:52 PM, Matthew Kaufman wrote:
>>=20
>>> On 11/16/11 10:47 AM, Ali C. Begen (abegen) wrote:
>>>>> So the WG chairs are asking which direction to take
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> The options we have are:
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> 1. Go forward with both solutions.
>>>>>=20
>>>>> 2. Only define multiplexing of multiple RTP sessions in a single
>> transport flow.
>>>>>=20
>>>>> 3. Only define multiplexing of multiple media types in a single RTP
>> session.
>>>>>=20
>>>>> 4. Not enough information in order to decide, more discussion is
>> needed.
>>>> My preference is (2) but I am also fine with (1) if that is the
>> consensus.
>>>>=20
>>>>=20
>>>=20
>>> (Sorry about tagging on to this point in the thread, but I joined the
>>> list late)
>>>=20
>>> I'm fine with either 2 or 3, but only because I think that 2 and 3
>> can look exactly the same on the wire and only differ in the
>> semantics... and I don't really care which semantics we choose.
>>>=20
>>> I'm not ok with a kind of 2 that isn't wire-equivalent to 3.
>>>=20
>>> Matthew Kaufman
>>> _______________________________________________
>>> Audio/Video Transport Core Maintenance avt@ietf.org
>>> https://www.ietf.org/mailman/listinfo/avt
>>=20
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>=20


From HKaplan@acmepacket.com  Tue Nov 15 22:59:10 2011
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41DF311E81BC for <avt@ietfa.amsl.com>; Tue, 15 Nov 2011 22:59:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.477
X-Spam-Level: 
X-Spam-Status: No, score=-2.477 tagged_above=-999 required=5 tests=[AWL=0.122,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id maT+YGntwH2h for <avt@ietfa.amsl.com>; Tue, 15 Nov 2011 22:59:06 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 7BCE411E81B9 for <avt@ietf.org>; Tue, 15 Nov 2011 22:59:06 -0800 (PST)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 16 Nov 2011 01:59:05 -0500
Received: from MAIL1.acmepacket.com ([169.254.1.232]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Wed, 16 Nov 2011 01:59:05 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Roni even <Even.roni@huawei.com>
Thread-Topic: [AVTCORE] Call for consensus on multiplexing multipe media streams.
Thread-Index: AQHMpC06BTJ2uxlSo0+fZtgMThIydw==
Date: Wed, 16 Nov 2011 06:59:04 +0000
Message-ID: <C0D9F589-E8CE-4295-B027-EEA6C299506A@acmepacket.com>
References: <EADCEEE0AE4A7F46BD61061696794D98F753FD@SZXEML519-MBS.china.huawei.com> <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com>
In-Reply-To: <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="utf-8"
Content-ID: <5E28D81FF6C2C9468EDC37D0EBC7641F@acmepacket.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] Call for consensus on multiplexing multipe media streams.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 16 Nov 2011 06:59:10 -0000

DQpJIHRoaW5rIG9wdGlvbiA0IGlzIHJpZ2h0OiB0aGVyZSBoYXMgbm90IGJlZW4gZW5vdWdoIGRp
c2N1c3Npb24gdG8gZGVjaWRlLiAgVW5mb3J0dW5hdGVseSB0aGVyZSB3YXMgaW5zdWZmaWNpZW50
IHRpbWUgaW4gdGhlIFdHIG1lZXRpbmcgdG8gdHJ1bHkgY292ZXIvZGlzY3VzcyB0aGUgb25lIHNs
aWRlIHdoaWNoIGFjdHVhbGx5IGhhZCBhIGNvbXBhcmlzb24gdGFibGUuIA0KDQpJIGFtIHNsaWdo
dGx5IGFnYWluc3QgT3B0aW9uIDEsIGJlY2F1c2UgY2hvb3NpbmcgYm90aCBpcyByYXJlbHkgYSBn
b29kIHRoaW5nIGZvciBpbnRlcm9wZXJhYmlsaXR5IHVubGVzcyB0aGUgbWFya2V0IHdvdWxkIGVu
ZCB1cCBvbmx5IGNob29zaW5nIHRoZSBzYW1lIG9uZSBpbiB0aGUgZW5kIGFueXdheSBmb3Igc29t
ZSByZWFzb24sIG9yIHVubGVzcyB0aGVyZSBhcmUgYWN0dWFsIHBybydzL2NvbidzIHdoaWNoIG1h
a2UgcGlja2luZyBvbmUgYW5kIG9ubHkgb25lIGltcHJhY3RpY2FsLiAgDQoNCi1oYWRyaWVsDQoN
Cg0KT24gTm92IDE0LCAyMDExLCBhdCAzOjU2IEFNLCBSb25pIGV2ZW4gd3JvdGU6DQoNCj4gSGkN
Cj4gQXQgdGhlIEFWVGNvcmUgc2Vzc2lvbiB3ZSBoYWQgdHdvIHByZXNlbnRhdGlvbnMuIE9uZSBm
cm9tIE1hZ251cyBwcm9wb3NpbmcgdGhlIG11bHRpcGxleGluZyBvZiBtdWx0aXBsZSBSVFAgc2Vz
c2lvbnMgb3ZlciBhIHNpbmdsZSB0cmFuc3BvcnQgZmxvdyBhbmQgdGhlIHNlY29uZCBmcm9tIEpv
bmF0aGFuIExlbm5veCBwcm9wb3NpbmcgbXVsdGlwbGV4aW5nIG11bHRpcGxlIG1lZGlhIHR5cGVz
IGluIGEgc2luZ2xlIFJUUCBzZXNzaW9uLg0KPiAgDQo+IE1hZ251cyBhc2tlZCBpbiB0aGUgYmVn
aW5uaW5nIG9mIGhpcyBwcmVzZW50YXRpb24gaWYgdGhlIFdHIGJlbGlldmUgdGhhdCB0aGUgcHJv
YmxlbSBvZiBwcm92aWRpbmcgbXVsdGlwbGUgUlRQIHNlc3Npb25zIG92ZXIgYSBzaW5nbGUgdHJh
bnNwb3J0IGZsb3cgc2hvdWxkIGJlIHNvbHZlZC4gVGhlIHJlc3BvbnNlIGZyb20gdGhlIHJvb20g
d2FzIHRoYXQgaXQgd2FzIGFscmVhZHkgZGlzY3Vzc2VkIGluIElFVEYgODEgYW5kIHRoZXJlIHdh
cyBpbnRlcmVzdCBpbiBkb2luZyB0aGlzIHdvcmsuDQo+IEluIElFVEY4MSB0aGVyZSB3YXMgYW4g
aW50ZXJlc3QgaW4gZG9pbmcgYm90aCBvcHRpb25zLiBEdXJpbmcgdGhlIHNlc3Npb24gdG9kYXkg
d2UgZGlkIG5vdCBoYXZlIHRpbWUgdG8gYXNrIGZvciBjb25zZW5zdXMuDQo+ICANCj4gIA0KPiBT
byB0aGUgV0cgY2hhaXJzIGFyZSBhc2tpbmcgd2hpY2ggZGlyZWN0aW9uIHRvIHRha2UNCj4gIA0K
PiBUaGUgb3B0aW9ucyB3ZSBoYXZlIGFyZToNCj4gIA0KPiAxLiBHbyBmb3J3YXJkIHdpdGggYm90
aCBzb2x1dGlvbnMuDQo+IDIuIE9ubHkgZGVmaW5lIG11bHRpcGxleGluZyBvZiBtdWx0aXBsZSBS
VFAgc2Vzc2lvbnMgaW4gYSBzaW5nbGUgdHJhbnNwb3J0IGZsb3cuDQo+IDMuIE9ubHkgZGVmaW5l
IG11bHRpcGxleGluZyBvZiBtdWx0aXBsZSBtZWRpYSB0eXBlcyBpbiBhIHNpbmdsZSBSVFAgc2Vz
c2lvbi4NCj4gNC4gTm90IGVub3VnaCBpbmZvcm1hdGlvbiBpbiBvcmRlciB0byBkZWNpZGUsIG1v
cmUgZGlzY3Vzc2lvbiBpcyBuZWVkZWQuDQo+ICANCj4gIA0KPiBUaGVyZSB3ZXJlIGFib3V0IDIw
IHBlb3BsZSBpbiB0aGUgQVZUY29yZSBzZXNzaW9uIHdobyByYWlzZWQgdGhlcmUgaGFuZHMgd2hl
biBhc2tlZCBpZiB0aGV5IGhhdmUgb3Bpbmlvbg0KPiAgDQo+IFRoYW5rcw0KPiBSb25pIEV2ZW4N
Cj4gQVZUY29yZSBjby1jaGFpcg0KPiAgDQo+IOOAgA0KPiAgDQo+IF9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IEF1ZGlvL1ZpZGVvIFRyYW5zcG9ydCBD
b3JlIE1haW50ZW5hbmNlDQo+IGF2dEBpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL2F2dA0KDQo=

From HKaplan@acmepacket.com  Wed Nov 16 06:15:15 2011
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3AC021F96B8 for <avt@ietfa.amsl.com>; Wed, 16 Nov 2011 06:15:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.479
X-Spam-Level: 
X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[AWL=0.120,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aBuZfjjq1g13 for <avt@ietfa.amsl.com>; Wed, 16 Nov 2011 06:15:15 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 1FAAA21F96B7 for <avt@ietf.org>; Wed, 16 Nov 2011 06:15:14 -0800 (PST)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 16 Nov 2011 09:15:13 -0500
Received: from MAIL1.acmepacket.com ([169.254.1.232]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Wed, 16 Nov 2011 09:15:13 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Harald Alvestrand <harald@alvestrand.no>
Thread-Topic: Why HTA thinks #2 is bad (Re: [AVTCORE] Call for consensus on multiplexing multipe media	streams.)
Thread-Index: AQHMpGonUwgK69L1s0qupLgcWbe6RQ==
Date: Wed, 16 Nov 2011 14:15:12 +0000
Message-ID: <518FD958-6EF5-460F-826B-04EFE8766436@acmepacket.com>
References: <EADCEEE0AE4A7F46BD61061696794D98F753FD@SZXEML519-MBS.china.huawei.com> <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com> <4EC0EE8B.1090108@alvestrand.no> <EB3E39E1-4671-4796-BC63-BF8E8E87CA0D@acmepacket.com> <4EC1C0E1.3000505@alvestrand.no>
In-Reply-To: <4EC1C0E1.3000505@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <6C46BA28592E8D4282F4D58DF765077F@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "<avt@ietf.org>" <avt@ietf.org>
Subject: Re: [AVTCORE] Why HTA thinks #2 is bad (Re: Call for consensus on multiplexing multipe media	streams.)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 16 Nov 2011 14:15:15 -0000

On Nov 14, 2011, at 8:31 PM, Harald Alvestrand wrote:

> Trying to make the chairs' job of tallying easier by changing the subject=
 when we fork into discussion rather than the call for consensus itself....
>=20
> On 11/15/2011 09:11 AM, Hadriel Kaplan wrote:
>>=20
>>=20
>> Harald,
>> Can you explain why you're strongly opposed to 2?  It would help me make=
 a more informed decision myself.
>>=20
>> I know the advantages of #2, some of which haven't been articulated yet =
I think... but what I don't know is what its disadvantages are that would m=
ake us choose #3 instead.
> #2 implies that we would not have a standard way to negotiate sending med=
ia with different top-level content types (such as audio and video, or audi=
o and text) in the same RTP session.
>=20
> This is today a limitation of SDP, not RTP, although some language in RFC=
 3550 (section 2.2) indicates that this was an intentional limitation when =
designing the SDP/RTP protocol suite.
>=20
> I believe this decision was a bad decision, and that the issue of how man=
y sessions to use, and what to pass on each session, should be left strictl=
y to the application.
> This requires an extension to SDP; in RTP, all that I believe is required=
 is that we stop stating the assumption; no wire protocol changes should be=
 needed.

But if I understand what you're saying above, you're basically saying #2 is=
 bad because it doesn't enable you to do #3.  No?

But that doesn't answer the question - what's actually bad with sending dif=
ferent media types in separate RTP sessions in the same 5-tuple, using a mu=
x/demux header?  Or conversely, what's better about being able to send them=
 in the same RTP session?

I can see actual advantages for keeping them separate RTP sessions and usin=
g a shim header approach - what I don't see are negatives to doing so, nor =
positives for using a single RTP session.

-hadriel


From HKaplan@acmepacket.com  Wed Nov 16 15:39:30 2011
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCE0E11E8090 for <avt@ietfa.amsl.com>; Wed, 16 Nov 2011 15:39:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.481
X-Spam-Level: 
X-Spam-Status: No, score=-2.481 tagged_above=-999 required=5 tests=[AWL=0.118,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z4-UfS6TY4in for <avt@ietfa.amsl.com>; Wed, 16 Nov 2011 15:39:30 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 0EFDC11E808F for <avt@ietf.org>; Wed, 16 Nov 2011 15:39:29 -0800 (PST)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 16 Nov 2011 18:39:28 -0500
Received: from MAIL1.acmepacket.com ([169.254.1.232]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Wed, 16 Nov 2011 18:39:28 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Matthew Kaufman <matthew@matthew.at>
Thread-Topic: [AVTCORE] Call for consensus on multiplexing multipe media streams.
Thread-Index: AQHMpLj6/MIVTOUDSE2Z8Zzq2za8NQ==
Date: Wed, 16 Nov 2011 23:39:27 +0000
Message-ID: <380D4ABA-77D2-45F6-AF8C-DA675B177587@acmepacket.com>
References: <04CAD96D4C5A3D48B1919248A8FE0D54104F2031@xmb-sjc-215.amer.cisco.com> <4EC3256A.1030802@matthew.at>
In-Reply-To: <4EC3256A.1030802@matthew.at>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <598F8E8261BBC34292074FFA830E1492@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "<avt@ietf.org>" <avt@ietf.org>
Subject: Re: [AVTCORE] Call for consensus on multiplexing multipe media	streams.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 16 Nov 2011 23:39:30 -0000

On Nov 15, 2011, at 9:52 PM, Matthew Kaufman wrote:

> On 11/16/11 10:47 AM, Ali C. Begen (abegen) wrote:
>>> So the WG chairs are asking which direction to take
>>>=20
>>> The options we have are:
>>>=20
>>> 1. Go forward with both solutions.
>>>=20
>>> 2. Only define multiplexing of multiple RTP sessions in a single transp=
ort flow.
>>>=20
>>> 3. Only define multiplexing of multiple media types in a single RTP ses=
sion.
>>>=20
>>> 4. Not enough information in order to decide, more discussion is needed=
.
>> My preference is (2) but I am also fine with (1) if that is the consensu=
s.
>>=20
>>=20
>=20
> (Sorry about tagging on to this point in the thread, but I joined the lis=
t late)
>=20
> I'm fine with either 2 or 3, but only because I think that 2 and 3 can lo=
ok exactly the same on the wire and only differ in the semantics... and I d=
on't really care which semantics we choose.
>=20
> I'm not ok with a kind of 2 that isn't wire-equivalent to 3.

I don't believe the two can technically be on-the-wire equivalent.  Even if=
 you do #2 without a shim header, the nuances of being distinct multiple RT=
P sessions means:
1) With #2 each RTP session has its own RTCP, so there'll be separate RTCP =
packets on-the-wire for audio vs. video (for example); whereas #3 means the=
re's one RTCP and thus there's one RTCP packet on-the-wire carrying multipl=
e SSRCs.
2) With #2 each RTP session has its own SRTP key/context, and potentially y=
ou could even do SRTP for one media type and not the other at the same time=
; with #3 the SRTP fate is tied, since it's one RTP session.
3) With #2 one RTP session can use AVPF, such as the video one, while the o=
ther does not; with #3 I think they'd all be doing AVPF or all not.

-hadriel


From mary.ietf.barnes@gmail.com  Wed Nov 16 18:24:29 2011
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 604A51F0C5E; Wed, 16 Nov 2011 18:24:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.214
X-Spam-Level: 
X-Spam-Status: No, score=-103.214 tagged_above=-999 required=5 tests=[AWL=0.385, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id drhwJNFGisy9; Wed, 16 Nov 2011 18:24:25 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id F25101F0CA9; Wed, 16 Nov 2011 18:24:24 -0800 (PST)
Received: by vcbfl15 with SMTP id fl15so1486797vcb.31 for <multiple recipients>; Wed, 16 Nov 2011 18:24:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=djgMmFuINvdWOlslldLxJ2QBkZ+MIwObVoots/vFsRk=; b=NQijyU1cD7uzj+9iwCF+5f6VX6A/uYDqRs5lu9a27QwEfJIzWAVdBSaqCmC4e/N/Bq 0lHIR3x9/muFRNt7603vMv8jLD2Z7Nlr6DnEROsSa0HnCLJJuoBeFe2DWRkHk8fY85Ts SDW3ZYdZMqbVHVm48pWFU7evr5rvb9VPvWcWM=
MIME-Version: 1.0
Received: by 10.52.24.13 with SMTP id q13mr23899899vdf.104.1321496664184; Wed, 16 Nov 2011 18:24:24 -0800 (PST)
Received: by 10.52.175.131 with HTTP; Wed, 16 Nov 2011 18:24:24 -0800 (PST)
Date: Wed, 16 Nov 2011 20:24:24 -0600
Message-ID: <CAHBDyN6tEFS_rqX7ZRcatQRVeh0nQo0eN-5VgDAXp=Xnjz+pyg@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: CLUE <clue@ietf.org>, rtcweb@ietf.org, avt@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [AVTCORE] Reminder: CLUE/RTCWEB adhoc in room 101D during lunch today (Nov. 17th)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 17 Nov 2011 02:24:29 -0000

Hello CLUE, RTCWEB and AVTCORE WG members,

A reminder of the adhoc today (Thursday, Nov 18th) 11:40-12:50 in room
101D to discuss requirements and usages of RTP for multi-stream for
CLUE and RTCWEB.   This also relates to the discussion in AVTCORE
around multiplexing.

The agenda and meeting materials are (will be) available on the CLUE
WG wiki: http://trac.tools.ietf.org/wg/clue/trac/wiki/WikiStart

Unfortunately, we did not get a room that is listed as allowing food:
http://www.ietf.org/meeting/82/things-to-note.html

So, please consider that if you might consider bringing in food that
you might want to exercise caution and there should be nothing related
to that food left in the room after the meeting.

Regards,
Mary and Ted
(as chairs for the adhoc)

From marshall.eubanks@gmail.com  Wed Nov 16 18:36:25 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 951501F0C69; Wed, 16 Nov 2011 18:36:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.498
X-Spam-Level: 
X-Spam-Status: No, score=-103.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VklzFcYSq-6u; Wed, 16 Nov 2011 18:36:25 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 76C601F0C3D; Wed, 16 Nov 2011 18:36:24 -0800 (PST)
Received: by faap16 with SMTP id p16so3063898faa.31 for <multiple recipients>; Wed, 16 Nov 2011 18:36:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=vnddLQ5Afl416algYd9dqTvoiuVWEI1D/zaa3K5u0Wo=; b=q0fuR8AKv7iYBs73aF9rxZ7O/BvvnXuyoP9syOIX/hUrjMPYnMuTsiHyeBDHiwFSro yQDSmvJLyyOJFiWRtI+P4FtvJONuGemJbPaPsKV711EVzAbYlUTf+Fb6Em2nLBqybyF0 UgKzOYavp41pZkDJ9x+4ednfoyBFvCHUU/6q8=
MIME-Version: 1.0
Received: by 10.182.7.66 with SMTP id h2mr9604306oba.14.1321497383391; Wed, 16 Nov 2011 18:36:23 -0800 (PST)
Received: by 10.182.159.73 with HTTP; Wed, 16 Nov 2011 18:36:23 -0800 (PST)
In-Reply-To: <CAHBDyN6tEFS_rqX7ZRcatQRVeh0nQo0eN-5VgDAXp=Xnjz+pyg@mail.gmail.com>
References: <CAHBDyN6tEFS_rqX7ZRcatQRVeh0nQo0eN-5VgDAXp=Xnjz+pyg@mail.gmail.com>
Date: Wed, 16 Nov 2011 21:36:23 -0500
Message-ID: <CAJNg7VJxKvxYv-aiB6wid3OvkOhaTr5BMC8z9-DDe-Q8ZQKSUg@mail.gmail.com>
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org, CLUE <clue@ietf.org>, avt@ietf.org
Subject: Re: [AVTCORE] [clue] Reminder: CLUE/RTCWEB adhoc in room 101D during lunch today (Nov. 17th)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 17 Nov 2011 02:36:25 -0000

On Wed, Nov 16, 2011 at 9:24 PM, Mary Barnes <mary.ietf.barnes@gmail.com> w=
rote:
> Hello CLUE, RTCWEB and AVTCORE WG members,
>
> A reminder of the adhoc today (Thursday, Nov 18th) 11:40-12:50 in room
> 101D to discuss requirements and usages of RTP for multi-stream for
> CLUE and RTCWEB. =A0 This also relates to the discussion in AVTCORE
> around multiplexing.

Note that that is NOT the room in the agenda

http://www.ietf.org/proceedings/82/agenda/clue.html

The venue was moved.

Regards
Marshall
>
> The agenda and meeting materials are (will be) available on the CLUE
> WG wiki: http://trac.tools.ietf.org/wg/clue/trac/wiki/WikiStart
>
> Unfortunately, we did not get a room that is listed as allowing food:
> http://www.ietf.org/meeting/82/things-to-note.html
>
> So, please consider that if you might consider bringing in food that
> you might want to exercise caution and there should be nothing related
> to that food left in the room after the meeting.
>
> Regards,
> Mary and Ted
> (as chairs for the adhoc)
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>

From mary.ietf.barnes@gmail.com  Wed Nov 16 19:00:30 2011
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 779021F0CAE; Wed, 16 Nov 2011 19:00:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.222
X-Spam-Level: 
X-Spam-Status: No, score=-103.222 tagged_above=-999 required=5 tests=[AWL=0.377, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sNsYRNWdxEq5; Wed, 16 Nov 2011 19:00:30 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9E2F71F0CA1; Wed, 16 Nov 2011 19:00:29 -0800 (PST)
Received: by vcbfl15 with SMTP id fl15so1515736vcb.31 for <multiple recipients>; Wed, 16 Nov 2011 19:00:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=P3OFPmk5KcX/UkdYBAKKH4bcVagmkUKLOEG67hkkSus=; b=IevNQiKPeR3cBEOtZ15KqyLyrXzDuUk8Ri+FQqhvmu4Rh6fFYzKMARYIMTlFVLMaPm 4QeH6bdq81Ost9NiGJb5EBsS04Y2P74oNyrWVZwcAlfrgomyidTwleTcuJB16UJ3Cvd7 HHUXa3htMSuxQs6Vf3EjpfMrGjxrF++1Vrfzo=
MIME-Version: 1.0
Received: by 10.52.17.112 with SMTP id n16mr53442893vdd.70.1321498829057; Wed, 16 Nov 2011 19:00:29 -0800 (PST)
Received: by 10.52.175.131 with HTTP; Wed, 16 Nov 2011 19:00:29 -0800 (PST)
In-Reply-To: <CAJNg7VJxKvxYv-aiB6wid3OvkOhaTr5BMC8z9-DDe-Q8ZQKSUg@mail.gmail.com>
References: <CAHBDyN6tEFS_rqX7ZRcatQRVeh0nQo0eN-5VgDAXp=Xnjz+pyg@mail.gmail.com> <CAJNg7VJxKvxYv-aiB6wid3OvkOhaTr5BMC8z9-DDe-Q8ZQKSUg@mail.gmail.com>
Date: Wed, 16 Nov 2011 21:00:29 -0600
Message-ID: <CAHBDyN6DfZsquObFr0UjNPH7vZS=vW6xYeW6usdv9Dd9p8MQTw@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org, CLUE <clue@ietf.org>, avt@ietf.org
Subject: Re: [AVTCORE] [clue] Reminder: CLUE/RTCWEB adhoc in room 101D during lunch today (Nov. 17th)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 17 Nov 2011 03:00:30 -0000

I updated the agenda in the meeting materials so there should be no
confusion.  You may need to refresh your browser to see the update.

On Wed, Nov 16, 2011 at 8:36 PM, Marshall Eubanks
<marshall.eubanks@gmail.com> wrote:
> On Wed, Nov 16, 2011 at 9:24 PM, Mary Barnes <mary.ietf.barnes@gmail.com>=
 wrote:
>> Hello CLUE, RTCWEB and AVTCORE WG members,
>>
>> A reminder of the adhoc today (Thursday, Nov 18th) 11:40-12:50 in room
>> 101D to discuss requirements and usages of RTP for multi-stream for
>> CLUE and RTCWEB. =A0 This also relates to the discussion in AVTCORE
>> around multiplexing.
>
> Note that that is NOT the room in the agenda
>
> http://www.ietf.org/proceedings/82/agenda/clue.html
>
> The venue was moved.
>
> Regards
> Marshall
>>
>> The agenda and meeting materials are (will be) available on the CLUE
>> WG wiki: http://trac.tools.ietf.org/wg/clue/trac/wiki/WikiStart
>>
>> Unfortunately, we did not get a room that is listed as allowing food:
>> http://www.ietf.org/meeting/82/things-to-note.html
>>
>> So, please consider that if you might consider bringing in food that
>> you might want to exercise caution and there should be nothing related
>> to that food left in the room after the meeting.
>>
>> Regards,
>> Mary and Ted
>> (as chairs for the adhoc)
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>>
>

From stephen.botzko@gmail.com  Wed Nov 16 19:21:23 2011
Return-Path: <stephen.botzko@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3E8A1F0CBF; Wed, 16 Nov 2011 19:21:23 -0800 (PST)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZtGxCk-FovwN; Wed, 16 Nov 2011 19:21:23 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6FF761F0CBB; Wed, 16 Nov 2011 19:21:22 -0800 (PST)
Received: by wyf28 with SMTP id 28so1577979wyf.31 for <multiple recipients>; Wed, 16 Nov 2011 19:21:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mFM+GuDBs5WCb1HXfHUgLdQfu9HxzMY+fNgzhejKdK4=; b=CPixce+E4CA7beXwYbv5MFqxn3hNsXyRzJS9r9ngkn+AIYVdjcz1H0fsOBLrpnD1IM rKHRXKSH70EHQ+4xxVDiP3AxBpY/q/4Tm/331jp+SuDAH6n1vi7kR8BBW3ost0/7JkCD NGrN145HmqVj3LRIGPInBgqvWrjPnwcqEPFBA=
MIME-Version: 1.0
Received: by 10.52.116.237 with SMTP id jz13mr55127792vdb.90.1321500079858; Wed, 16 Nov 2011 19:21:19 -0800 (PST)
Received: by 10.52.183.33 with HTTP; Wed, 16 Nov 2011 19:21:19 -0800 (PST)
In-Reply-To: <CAHBDyN6DfZsquObFr0UjNPH7vZS=vW6xYeW6usdv9Dd9p8MQTw@mail.gmail.com>
References: <CAHBDyN6tEFS_rqX7ZRcatQRVeh0nQo0eN-5VgDAXp=Xnjz+pyg@mail.gmail.com> <CAJNg7VJxKvxYv-aiB6wid3OvkOhaTr5BMC8z9-DDe-Q8ZQKSUg@mail.gmail.com> <CAHBDyN6DfZsquObFr0UjNPH7vZS=vW6xYeW6usdv9Dd9p8MQTw@mail.gmail.com>
Date: Thu, 17 Nov 2011 11:21:19 +0800
Message-ID: <CAMC7SJ5xyUuimBuKtn2Lqv22WBQUCe9DQhijcwHwd5br26LxsQ@mail.gmail.com>
From: Stephen Botzko <stephen.botzko@gmail.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec5486432d4a50004b1e5b640
Cc: CLUE <clue@ietf.org>, rtcweb@ietf.org, avt@ietf.org, Marshall Eubanks <marshall.eubanks@gmail.com>
Subject: Re: [AVTCORE] [clue] Reminder: CLUE/RTCWEB adhoc in room 101D during lunch today (Nov. 17th)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 17 Nov 2011 03:21:23 -0000

--bcaec5486432d4a50004b1e5b640
Content-Type: text/plain; charset=ISO-8859-1

It would be nice if the Android/iPhone apps showed adhoc meetings...

Maybe something to forward to the appropriate tools folks.

Stephen Botzko

On Thu, Nov 17, 2011 at 11:00 AM, Mary Barnes <mary.ietf.barnes@gmail.com>wrote:

> I updated the agenda in the meeting materials so there should be no
> confusion.  You may need to refresh your browser to see the update.
>
> On Wed, Nov 16, 2011 at 8:36 PM, Marshall Eubanks
> <marshall.eubanks@gmail.com> wrote:
> > On Wed, Nov 16, 2011 at 9:24 PM, Mary Barnes <mary.ietf.barnes@gmail.com>
> wrote:
> >> Hello CLUE, RTCWEB and AVTCORE WG members,
> >>
> >> A reminder of the adhoc today (Thursday, Nov 18th) 11:40-12:50 in room
> >> 101D to discuss requirements and usages of RTP for multi-stream for
> >> CLUE and RTCWEB.   This also relates to the discussion in AVTCORE
> >> around multiplexing.
> >
> > Note that that is NOT the room in the agenda
> >
> > http://www.ietf.org/proceedings/82/agenda/clue.html
> >
> > The venue was moved.
> >
> > Regards
> > Marshall
> >>
> >> The agenda and meeting materials are (will be) available on the CLUE
> >> WG wiki: http://trac.tools.ietf.org/wg/clue/trac/wiki/WikiStart
> >>
> >> Unfortunately, we did not get a room that is listed as allowing food:
> >> http://www.ietf.org/meeting/82/things-to-note.html
> >>
> >> So, please consider that if you might consider bringing in food that
> >> you might want to exercise caution and there should be nothing related
> >> to that food left in the room after the meeting.
> >>
> >> Regards,
> >> Mary and Ted
> >> (as chairs for the adhoc)
> >> _______________________________________________
> >> clue mailing list
> >> clue@ietf.org
> >> https://www.ietf.org/mailman/listinfo/clue
> >>
> >
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>

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

It would be nice if the Android/iPhone apps showed adhoc meetings...<br><br=
>Maybe something to forward to the appropriate tools folks.<br><br>Stephen =
Botzko<br><br><div class=3D"gmail_quote">On Thu, Nov 17, 2011 at 11:00 AM, =
Mary Barnes <span dir=3D"ltr">&lt;<a href=3D"mailto:mary.ietf.barnes@gmail.=
com">mary.ietf.barnes@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">I updated the agenda in the meeting materia=
ls so there should be no<br>
confusion. =A0You may need to refresh your browser to see the update.<br>
<div><div></div><div class=3D"h5"><br>
On Wed, Nov 16, 2011 at 8:36 PM, Marshall Eubanks<br>
&lt;<a href=3D"mailto:marshall.eubanks@gmail.com">marshall.eubanks@gmail.co=
m</a>&gt; wrote:<br>
&gt; On Wed, Nov 16, 2011 at 9:24 PM, Mary Barnes &lt;<a href=3D"mailto:mar=
y.ietf.barnes@gmail.com">mary.ietf.barnes@gmail.com</a>&gt; wrote:<br>
&gt;&gt; Hello CLUE, RTCWEB and AVTCORE WG members,<br>
&gt;&gt;<br>
&gt;&gt; A reminder of the adhoc today (Thursday, Nov 18th) 11:40-12:50 in =
room<br>
&gt;&gt; 101D to discuss requirements and usages of RTP for multi-stream fo=
r<br>
&gt;&gt; CLUE and RTCWEB. =A0 This also relates to the discussion in AVTCOR=
E<br>
&gt;&gt; around multiplexing.<br>
&gt;<br>
&gt; Note that that is NOT the room in the agenda<br>
&gt;<br>
&gt; <a href=3D"http://www.ietf.org/proceedings/82/agenda/clue.html" target=
=3D"_blank">http://www.ietf.org/proceedings/82/agenda/clue.html</a><br>
&gt;<br>
&gt; The venue was moved.<br>
&gt;<br>
&gt; Regards<br>
&gt; Marshall<br>
&gt;&gt;<br>
&gt;&gt; The agenda and meeting materials are (will be) available on the CL=
UE<br>
&gt;&gt; WG wiki: <a href=3D"http://trac.tools.ietf.org/wg/clue/trac/wiki/W=
ikiStart" target=3D"_blank">http://trac.tools.ietf.org/wg/clue/trac/wiki/Wi=
kiStart</a><br>
&gt;&gt;<br>
&gt;&gt; Unfortunately, we did not get a room that is listed as allowing fo=
od:<br>
&gt;&gt; <a href=3D"http://www.ietf.org/meeting/82/things-to-note.html" tar=
get=3D"_blank">http://www.ietf.org/meeting/82/things-to-note.html</a><br>
&gt;&gt;<br>
&gt;&gt; So, please consider that if you might consider bringing in food th=
at<br>
&gt;&gt; you might want to exercise caution and there should be nothing rel=
ated<br>
&gt;&gt; to that food left in the room after the meeting.<br>
&gt;&gt;<br>
&gt;&gt; Regards,<br>
&gt;&gt; Mary and Ted<br>
&gt;&gt; (as chairs for the adhoc)<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; clue mailing list<br>
&gt;&gt; <a href=3D"mailto:clue@ietf.org">clue@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/clue" target=3D"_=
blank">https://www.ietf.org/mailman/listinfo/clue</a><br>
&gt;&gt;<br>
&gt;<br>
_______________________________________________<br>
clue mailing list<br>
<a href=3D"mailto:clue@ietf.org">clue@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/clue" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/clue</a><br>
</div></div></blockquote></div><br>

--bcaec5486432d4a50004b1e5b640--

From marshall.eubanks@gmail.com  Wed Nov 16 19:22:19 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 146E21F0CC0; Wed, 16 Nov 2011 19:22:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3tqlXkFFE1zs; Wed, 16 Nov 2011 19:22:18 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id F116B1F0CA5; Wed, 16 Nov 2011 19:22:17 -0800 (PST)
Received: by mail-ww0-f44.google.com with SMTP id 5so1718038wwe.13 for <multiple recipients>; Wed, 16 Nov 2011 19:22:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=VNBU3mYARCWHRM/oj57rmnKmL9JJPmgjPJcskZnJm18=; b=elzhLplWt1XbNtuQH92geHdlGBrm/DA2ayLQjx0Hdh4SSU1nFmTq1YHIS+ouyEFVK0 JtoAS5h1eF165RtjH2WNZROOSOHseUOH35W0j8GAF0/DiTNsuYIcuY7X5wOOosxrBaKf +fus2xlthp7yPL8vl7H83c8TGiaeaxfaX2i1k=
MIME-Version: 1.0
Received: by 10.182.7.66 with SMTP id h2mr9728745oba.14.1321500137336; Wed, 16 Nov 2011 19:22:17 -0800 (PST)
Received: by 10.182.159.73 with HTTP; Wed, 16 Nov 2011 19:22:17 -0800 (PST)
In-Reply-To: <CAMC7SJ5xyUuimBuKtn2Lqv22WBQUCe9DQhijcwHwd5br26LxsQ@mail.gmail.com>
References: <CAHBDyN6tEFS_rqX7ZRcatQRVeh0nQo0eN-5VgDAXp=Xnjz+pyg@mail.gmail.com> <CAJNg7VJxKvxYv-aiB6wid3OvkOhaTr5BMC8z9-DDe-Q8ZQKSUg@mail.gmail.com> <CAHBDyN6DfZsquObFr0UjNPH7vZS=vW6xYeW6usdv9Dd9p8MQTw@mail.gmail.com> <CAMC7SJ5xyUuimBuKtn2Lqv22WBQUCe9DQhijcwHwd5br26LxsQ@mail.gmail.com>
Date: Wed, 16 Nov 2011 22:22:17 -0500
Message-ID: <CAJNg7V+iWz=t0tEaY051atR0ctsxWsYe3zgga25uJM3YJJyMMQ@mail.gmail.com>
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Stephen Botzko <stephen.botzko@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: CLUE <clue@ietf.org>, rtcweb@ietf.org, avt@ietf.org
Subject: Re: [AVTCORE] [clue] Reminder: CLUE/RTCWEB adhoc in room 101D during lunch today (Nov. 17th)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 17 Nov 2011 03:22:19 -0000

OK,

On Wed, Nov 16, 2011 at 10:21 PM, Stephen Botzko
<stephen.botzko@gmail.com> wrote:
> It would be nice if the Android/iPhone apps showed adhoc meetings...
>
> Maybe something to forward to the appropriate tools folks.
>
> Stephen Botzko
>
> On Thu, Nov 17, 2011 at 11:00 AM, Mary Barnes <mary.ietf.barnes@gmail.com=
>
> wrote:
>>
>> I updated the agenda in the meeting materials so there should be no
>> confusion. =A0You may need to refresh your browser to see the update.
>>
>> On Wed, Nov 16, 2011 at 8:36 PM, Marshall Eubanks
>> <marshall.eubanks@gmail.com> wrote:
>> > On Wed, Nov 16, 2011 at 9:24 PM, Mary Barnes
>> > <mary.ietf.barnes@gmail.com> wrote:
>> >> Hello CLUE, RTCWEB and AVTCORE WG members,
>> >>
>> >> A reminder of the adhoc today (Thursday, Nov 18th) 11:40-12:50 in roo=
m
>> >> 101D to discuss requirements and usages of RTP for multi-stream for
>> >> CLUE and RTCWEB. =A0 This also relates to the discussion in AVTCORE
>> >> around multiplexing.
>> >
>> > Note that that is NOT the room in the agenda
>> >
>> > http://www.ietf.org/proceedings/82/agenda/clue.html
>> >
>> > The venue was moved.
>> >
>> > Regards
>> > Marshall
>> >>
>> >> The agenda and meeting materials are (will be) available on the CLUE
>> >> WG wiki: http://trac.tools.ietf.org/wg/clue/trac/wiki/WikiStart
>> >>
>> >> Unfortunately, we did not get a room that is listed as allowing food:
>> >> http://www.ietf.org/meeting/82/things-to-note.html
>> >>
>> >> So, please consider that if you might consider bringing in food that
>> >> you might want to exercise caution and there should be nothing relate=
d
>> >> to that food left in the room after the meeting.
>> >>
>> >> Regards,
>> >> Mary and Ted
>> >> (as chairs for the adhoc)
>> >> _______________________________________________
>> >> clue mailing list
>> >> clue@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/clue
>> >>
>> >
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>
>

From marshall.eubanks@gmail.com  Wed Nov 16 19:30:30 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E0C61F0CD3; Wed, 16 Nov 2011 19:30:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.5
X-Spam-Level: 
X-Spam-Status: No, score=-103.5 tagged_above=-999 required=5 tests=[AWL=0.099,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s4Nvti4ZnPbZ; Wed, 16 Nov 2011 19:30:29 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 49B191F0CD0; Wed, 16 Nov 2011 19:30:29 -0800 (PST)
Received: by mail-fx0-f44.google.com with SMTP id p16so3159931faa.31 for <multiple recipients>; Wed, 16 Nov 2011 19:30:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=pnS21PGuhbDrxCN+spr8W7tDuFUi3+1N+8b/qn+eNds=; b=jT5367rJFCJH+d0iKVis1uTyZzRnbusvV+FnR3EIZwndQepWmuTgo9Gk4ZdXMoQEST VecmAJnkqW5Zy2wo9cQ0JeKM2EPIcIULGeizMFwT6IdQm/OEwNgM7QheRQWo1Rgc3qvo aC13UjHG8vGhvWweXlFsC+jXiklmNQWXAXH1o=
MIME-Version: 1.0
Received: by 10.182.21.134 with SMTP id v6mr9769415obe.64.1321500628330; Wed, 16 Nov 2011 19:30:28 -0800 (PST)
Received: by 10.182.159.73 with HTTP; Wed, 16 Nov 2011 19:30:28 -0800 (PST)
In-Reply-To: <CAJNg7V+iWz=t0tEaY051atR0ctsxWsYe3zgga25uJM3YJJyMMQ@mail.gmail.com>
References: <CAHBDyN6tEFS_rqX7ZRcatQRVeh0nQo0eN-5VgDAXp=Xnjz+pyg@mail.gmail.com> <CAJNg7VJxKvxYv-aiB6wid3OvkOhaTr5BMC8z9-DDe-Q8ZQKSUg@mail.gmail.com> <CAHBDyN6DfZsquObFr0UjNPH7vZS=vW6xYeW6usdv9Dd9p8MQTw@mail.gmail.com> <CAMC7SJ5xyUuimBuKtn2Lqv22WBQUCe9DQhijcwHwd5br26LxsQ@mail.gmail.com> <CAJNg7V+iWz=t0tEaY051atR0ctsxWsYe3zgga25uJM3YJJyMMQ@mail.gmail.com>
Date: Wed, 16 Nov 2011 22:30:28 -0500
Message-ID: <CAJNg7VLbivMQqD23fFiWvnvdWqn_WeHdKPpDuMH6smnZonO=1w@mail.gmail.com>
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Stephen Botzko <stephen.botzko@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: CLUE <clue@ietf.org>, rtcweb@ietf.org, avt@ietf.org
Subject: Re: [AVTCORE] [clue] Reminder: CLUE/RTCWEB adhoc in room 101D during lunch today (Nov. 17th)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 17 Nov 2011 03:30:30 -0000

I made the request.

Marshall

On Wed, Nov 16, 2011 at 10:22 PM, Marshall Eubanks
<marshall.eubanks@gmail.com> wrote:
> OK,
>
> On Wed, Nov 16, 2011 at 10:21 PM, Stephen Botzko
> <stephen.botzko@gmail.com> wrote:
>> It would be nice if the Android/iPhone apps showed adhoc meetings...
>>
>> Maybe something to forward to the appropriate tools folks.
>>
>> Stephen Botzko
>>
>> On Thu, Nov 17, 2011 at 11:00 AM, Mary Barnes <mary.ietf.barnes@gmail.co=
m>
>> wrote:
>>>
>>> I updated the agenda in the meeting materials so there should be no
>>> confusion. =A0You may need to refresh your browser to see the update.
>>>
>>> On Wed, Nov 16, 2011 at 8:36 PM, Marshall Eubanks
>>> <marshall.eubanks@gmail.com> wrote:
>>> > On Wed, Nov 16, 2011 at 9:24 PM, Mary Barnes
>>> > <mary.ietf.barnes@gmail.com> wrote:
>>> >> Hello CLUE, RTCWEB and AVTCORE WG members,
>>> >>
>>> >> A reminder of the adhoc today (Thursday, Nov 18th) 11:40-12:50 in ro=
om
>>> >> 101D to discuss requirements and usages of RTP for multi-stream for
>>> >> CLUE and RTCWEB. =A0 This also relates to the discussion in AVTCORE
>>> >> around multiplexing.
>>> >
>>> > Note that that is NOT the room in the agenda
>>> >
>>> > http://www.ietf.org/proceedings/82/agenda/clue.html
>>> >
>>> > The venue was moved.
>>> >
>>> > Regards
>>> > Marshall
>>> >>
>>> >> The agenda and meeting materials are (will be) available on the CLUE
>>> >> WG wiki: http://trac.tools.ietf.org/wg/clue/trac/wiki/WikiStart
>>> >>
>>> >> Unfortunately, we did not get a room that is listed as allowing food=
:
>>> >> http://www.ietf.org/meeting/82/things-to-note.html
>>> >>
>>> >> So, please consider that if you might consider bringing in food that
>>> >> you might want to exercise caution and there should be nothing relat=
ed
>>> >> to that food left in the room after the meeting.
>>> >>
>>> >> Regards,
>>> >> Mary and Ted
>>> >> (as chairs for the adhoc)
>>> >> _______________________________________________
>>> >> clue mailing list
>>> >> clue@ietf.org
>>> >> https://www.ietf.org/mailman/listinfo/clue
>>> >>
>>> >
>>> _______________________________________________
>>> clue mailing list
>>> clue@ietf.org
>>> https://www.ietf.org/mailman/listinfo/clue
>>
>>
>

From magnus.westerlund@ericsson.com  Thu Nov 17 00:49:53 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C63E21F9A6B; Thu, 17 Nov 2011 00:49:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.548
X-Spam-Level: 
X-Spam-Status: No, score=-106.548 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HRFqmWaL3TEt; Thu, 17 Nov 2011 00:49:48 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 668D721F9A66; Thu, 17 Nov 2011 00:49:47 -0800 (PST)
X-AuditID: c1b4fb39-b7b3eae00000252a-a4-4ec4caa7ebbf
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 4D.FF.09514.7AAC4CE4; Thu, 17 Nov 2011 09:49:44 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.137.0; Thu, 17 Nov 2011 09:49:43 +0100
Message-ID: <4EC4CA9D.5020403@ericsson.com>
Date: Thu, 17 Nov 2011 16:49:33 +0800
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>
References: <20111031132810.20293.12093.idtracker@ietfa.amsl.com> <9AA22A68-6D9C-4709-964A-24693B7EE8DA@nostrum.com>
In-Reply-To: <9AA22A68-6D9C-4709-964A-24693B7EE8DA@nostrum.com>
X-Enigmail-Version: 1.3.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: Pete Resnick <presnick@qualcomm.com>, "draft-ietf-avtcore-srtp-vbr-audio@tools.ietf.org" <draft-ietf-avtcore-srtp-vbr-audio@tools.ietf.org>, "avtcore-chairs@tools.ietf.org" <avtcore-chairs@tools.ietf.org>, IETF AVTCORE WG <avt@ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [AVTCORE] Pete Resnick's Discuss on draft-ietf-avtcore-srtp-vbr-audio-03: (with DISCUSS)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 17 Nov 2011 08:49:53 -0000

WG,

There has been no responses to this topic. If you are fine with this, I
still would appreciate a few responses to indicate that you are fine
with going to standards track.

My individual view is that there are no issue and appear appropriate.
This is something the WG chairs should have considered before requesting
the publication.

Cheers

Magnus

On 2011-11-01 23:50, Robert Sparks wrote:
> AVTCORE Working Group:
> 
> Pete is making an argument that the text in this document could be
> published as Standards Track. We've walked through the normative
> statements in the document together and I see his argument. My only
> concern is whether there is any intent in the document to tell
> operators of existing deployments to go change their configuration
> right away to avoid the security issues the document describes. Pete
> rightly points out that, as written, the document is providing
> guidance to new implementers, not to current operators.
> 
> Does anyone believe moving this to the Standards Track is the wrong
> thing to do? Do you think the document needs to say anything more
> strongly about current deployments?
> 
> RjS
> 
> 
> On Oct 31, 2011, at 8:28 AM, Pete Resnick wrote:
> 
>> Pete Resnick has entered the following ballot position for 
>> draft-ietf-avtcore-srtp-vbr-audio-03: Discuss
>> 
>> When responding, please keep the subject line intact and reply to
>> all email addresses included in the To and CC lines. (Feel free to
>> cut this introductory paragraph, however.)
>> 
>> Please refer to
>> http://www.ietf.org/iesg/statement/discuss-criteria.html for more
>> information about IESG DISCUSS and COMMENT positions.
>> 
>> 
>> 
>> ----------------------------------------------------------------------
>>
>> 
DISCUSS:
>> ----------------------------------------------------------------------
>>
>>
>> 
I don't see how this is remotely a BCP. This should be on the standards
track. It is specifying all sorts of implementation parameters that are
clearly testable, may have interoperability implications, and may change
over time as we get implementation experience. (E.g., the length of the
overhang period may be something that we specify differently, whether
VAD is used or not may have interoperability implications, etc.). This
discussion would have normally happened in the context of a security
considerations section of a base protocol document and would have gone
along the standards track with the base protocol. The fact that it is
being published separately shouldn't change its treatment.
>> 
>> 
>> 
>> 
> 
> _______________________________________________ Audio/Video Transport
> Core Maintenance avt@ietf.org 
> https://www.ietf.org/mailman/listinfo/avt
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From HKaplan@acmepacket.com  Thu Nov 17 01:02:25 2011
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BA1021F9AF4; Thu, 17 Nov 2011 01:02:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.483
X-Spam-Level: 
X-Spam-Status: No, score=-2.483 tagged_above=-999 required=5 tests=[AWL=0.116,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZvqjRtVP5PUC; Thu, 17 Nov 2011 01:02:24 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 3977121F9AEF; Thu, 17 Nov 2011 01:02:21 -0800 (PST)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 17 Nov 2011 04:02:20 -0500
Received: from MAIL1.acmepacket.com ([169.254.1.232]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Thu, 17 Nov 2011 04:02:20 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Thread-Topic: [AVTCORE] Pete Resnick's Discuss on draft-ietf-avtcore-srtp-vbr-audio-03: (with DISCUSS)
Thread-Index: AQHMpQecT2W6MonbSEiUzzIHUvU6eQ==
Date: Thu, 17 Nov 2011 09:02:19 +0000
Message-ID: <BAA56D43-8972-4622-BD62-E71671AC9255@acmepacket.com>
References: <20111031132810.20293.12093.idtracker@ietfa.amsl.com> <9AA22A68-6D9C-4709-964A-24693B7EE8DA@nostrum.com> <4EC4CA9D.5020403@ericsson.com>
In-Reply-To: <4EC4CA9D.5020403@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <1B9A5C348EB18E4CACA478D5AAF574FA@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: IETF AVTCORE WG <avt@ietf.org>, "draft-ietf-avtcore-srtp-vbr-audio@tools.ietf.org" <draft-ietf-avtcore-srtp-vbr-audio@tools.ietf.org>, "avtcore-chairs@tools.ietf.org" <avtcore-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, Pete Resnick <presnick@qualcomm.com>
Subject: Re: [AVTCORE] Pete Resnick's Discuss on draft-ietf-avtcore-srtp-vbr-audio-03: (with DISCUSS)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 17 Nov 2011 09:02:25 -0000

Well you asked, so: I'm fine with making it standards-track, fwiw.
I'm not sure if "Guidelines" is an appropriate word in the document's title=
 for a standards-track doc, but I don't care - just noting it.=20

-hadriel


On Nov 17, 2011, at 3:49 AM, Magnus Westerlund wrote:

> WG,
>=20
> There has been no responses to this topic. If you are fine with this, I
> still would appreciate a few responses to indicate that you are fine
> with going to standards track.
>=20
> My individual view is that there are no issue and appear appropriate.
> This is something the WG chairs should have considered before requesting
> the publication.
>=20
> Cheers
>=20
> Magnus
>=20
> On 2011-11-01 23:50, Robert Sparks wrote:
>> AVTCORE Working Group:
>>=20
>> Pete is making an argument that the text in this document could be
>> published as Standards Track. We've walked through the normative
>> statements in the document together and I see his argument. My only
>> concern is whether there is any intent in the document to tell
>> operators of existing deployments to go change their configuration
>> right away to avoid the security issues the document describes. Pete
>> rightly points out that, as written, the document is providing
>> guidance to new implementers, not to current operators.
>>=20
>> Does anyone believe moving this to the Standards Track is the wrong
>> thing to do? Do you think the document needs to say anything more
>> strongly about current deployments?
>>=20
>> RjS
>>=20
>>=20
>> On Oct 31, 2011, at 8:28 AM, Pete Resnick wrote:
>>=20
>>> Pete Resnick has entered the following ballot position for=20
>>> draft-ietf-avtcore-srtp-vbr-audio-03: Discuss
>>>=20
>>> When responding, please keep the subject line intact and reply to
>>> all email addresses included in the To and CC lines. (Feel free to
>>> cut this introductory paragraph, however.)
>>>=20
>>> Please refer to
>>> http://www.ietf.org/iesg/statement/discuss-criteria.html for more
>>> information about IESG DISCUSS and COMMENT positions.
>>>=20
>>>=20
>>>=20
>>> ----------------------------------------------------------------------
>>>=20
>>>=20
> DISCUSS:
>>> ----------------------------------------------------------------------
>>>=20
>>>=20
>>>=20
> I don't see how this is remotely a BCP. This should be on the standards
> track. It is specifying all sorts of implementation parameters that are
> clearly testable, may have interoperability implications, and may change
> over time as we get implementation experience. (E.g., the length of the
> overhang period may be something that we specify differently, whether
> VAD is used or not may have interoperability implications, etc.). This
> discussion would have normally happened in the context of a security
> considerations section of a base protocol document and would have gone
> along the standards track with the base protocol. The fact that it is
> being published separately shouldn't change its treatment.
>>>=20
>>>=20
>>>=20
>>>=20
>>=20
>> _______________________________________________ Audio/Video Transport
>> Core Maintenance avt@ietf.org=20
>> https://www.ietf.org/mailman/listinfo/avt
>>=20
>=20
>=20
> --=20
>=20
> Magnus Westerlund
>=20
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> F=E4r=F6gatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>=20
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From abegen@cisco.com  Thu Nov 17 01:03:53 2011
Return-Path: <abegen@cisco.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44AF821F9B23; Thu, 17 Nov 2011 01:03:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.532
X-Spam-Level: 
X-Spam-Status: No, score=-4.532 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p5EXSjPUeh92; Thu, 17 Nov 2011 01:03:52 -0800 (PST)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 6D1B921F9B20; Thu, 17 Nov 2011 01:03:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=abegen@cisco.com; l=5170; q=dns/txt; s=iport; t=1321520632; x=1322730232; h=subject:references:content-transfer-encoding:from: in-reply-to:message-id:date:to:cc:mime-version; bh=qiR8+5R3y58eQBx1pzdDP4bunyUlPUC2eLn5oUGc9dg=; b=fwkfwbtRHZZlNVnAufaB//uZL5/dCEzBxm+hQi6rc3tJwyg1zt0wPlsl wfGxTU7j9VEUs2lmIHSU6kTX1G2l9qJ6JoElrblLgKT1Ay95YIAAWlmdX wTvdFM1SYAScTDEu3uzL2ESyojnFpvC2tbfgJod6y0BKHE79sIdXPOwXw M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoAHADTNxE6rRDoI/2dsb2JhbABChDFQo3aBBgKBBYFyAQEBAwEBAQEJBgEQEUUFCQICAQYCGAICIwMCAgIZDB8RAQEEEwkZh2AIlRUBjFmRYAKBLodRM2MEiBOMIoVEjEU
X-IronPort-AV: E=Sophos;i="4.69,525,1315180800"; d="scan'208";a="14740752"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 17 Nov 2011 09:03:52 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pAH93qIe020218; Thu, 17 Nov 2011 09:03:52 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.4675);  Thu, 17 Nov 2011 01:03:52 -0800
Received: from 72.163.63.13 ([72.163.63.13]) by xmb-sjc-215.amer.cisco.com ([171.70.151.169]) with Microsoft Exchange Server HTTP-DAV ;  Thu, 17 Nov 2011 09:03:51 +0000
References: <20111031132810.20293.12093.idtracker@ietfa.amsl.com> <9AA22A68-6D9C-4709-964A-24693B7EE8DA@nostrum.com> <4EC4CA9D.5020403@ericsson.com>
Content-Transfer-Encoding: base64
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
Content-Type: text/plain; charset="utf-8"
thread-topic: [AVTCORE] Pete Resnick's Discuss on draft-ietf-avtcore-srtp-vbr-audio-03: (with DISCUSS)
thread-index: AcylB9MLW9wfx+HPTT+6sdt7WjiLAQ==
In-Reply-To: <4EC4CA9D.5020403@ericsson.com>
Message-ID: <43831550-B681-4AFF-96DA-69EACEE66317@cisco.com>
Date: Thu, 17 Nov 2011 17:03:46 +0800
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
MIME-Version: 1.0 (1.0)
X-OriginalArrivalTime: 17 Nov 2011 09:03:52.0007 (UTC) FILETIME=[D395DD70:01CCA507]
Cc: IETF AVTCORE WG <avt@ietf.org>, draft-ietf-avtcore-srtp-vbr-audio@tools.ietf.org, avtcore-chairs@tools.ietf.org, The IESG <iesg@ietf.org>, Pete Resnick <presnick@qualcomm.com>
Subject: Re: [AVTCORE] Pete Resnick's Discuss on draft-ietf-avtcore-srtp-vbr-audio-03: (with DISCUSS)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 17 Nov 2011 09:03:53 -0000

SSBsb29rZWQgYXQgdGhlIGRvY3VtZW50IGJlZm9yZSB0aGUgbGFzdCBjYWxsIGFuZCBteSBpbXBy
ZXNzaW9uIGlzIHRoYXQgc3RhbmRhcmRzIHRyYWNrIGlzIG1vcmUgYXBwcm9wcmlhdGUgYXMgd2Vs
bC4gDQoNCi1hY2JlZ2VuDQoNCk9uIE5vdiAxNywgMjAxMSwgYXQgNDo0OSBQTSwgIk1hZ251cyBX
ZXN0ZXJsdW5kIiA8bWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tPiB3cm90ZToNCg0KPiBX
RywNCj4gDQo+IFRoZXJlIGhhcyBiZWVuIG5vIHJlc3BvbnNlcyB0byB0aGlzIHRvcGljLiBJZiB5
b3UgYXJlIGZpbmUgd2l0aCB0aGlzLCBJDQo+IHN0aWxsIHdvdWxkIGFwcHJlY2lhdGUgYSBmZXcg
cmVzcG9uc2VzIHRvIGluZGljYXRlIHRoYXQgeW91IGFyZSBmaW5lDQo+IHdpdGggZ29pbmcgdG8g
c3RhbmRhcmRzIHRyYWNrLg0KPiANCj4gTXkgaW5kaXZpZHVhbCB2aWV3IGlzIHRoYXQgdGhlcmUg
YXJlIG5vIGlzc3VlIGFuZCBhcHBlYXIgYXBwcm9wcmlhdGUuDQo+IFRoaXMgaXMgc29tZXRoaW5n
IHRoZSBXRyBjaGFpcnMgc2hvdWxkIGhhdmUgY29uc2lkZXJlZCBiZWZvcmUgcmVxdWVzdGluZw0K
PiB0aGUgcHVibGljYXRpb24uDQo+IA0KPiBDaGVlcnMNCj4gDQo+IE1hZ251cw0KPiANCj4gT24g
MjAxMS0xMS0wMSAyMzo1MCwgUm9iZXJ0IFNwYXJrcyB3cm90ZToNCj4+IEFWVENPUkUgV29ya2lu
ZyBHcm91cDoNCj4+IA0KPj4gUGV0ZSBpcyBtYWtpbmcgYW4gYXJndW1lbnQgdGhhdCB0aGUgdGV4
dCBpbiB0aGlzIGRvY3VtZW50IGNvdWxkIGJlDQo+PiBwdWJsaXNoZWQgYXMgU3RhbmRhcmRzIFRy
YWNrLiBXZSd2ZSB3YWxrZWQgdGhyb3VnaCB0aGUgbm9ybWF0aXZlDQo+PiBzdGF0ZW1lbnRzIGlu
IHRoZSBkb2N1bWVudCB0b2dldGhlciBhbmQgSSBzZWUgaGlzIGFyZ3VtZW50LiBNeSBvbmx5DQo+
PiBjb25jZXJuIGlzIHdoZXRoZXIgdGhlcmUgaXMgYW55IGludGVudCBpbiB0aGUgZG9jdW1lbnQg
dG8gdGVsbA0KPj4gb3BlcmF0b3JzIG9mIGV4aXN0aW5nIGRlcGxveW1lbnRzIHRvIGdvIGNoYW5n
ZSB0aGVpciBjb25maWd1cmF0aW9uDQo+PiByaWdodCBhd2F5IHRvIGF2b2lkIHRoZSBzZWN1cml0
eSBpc3N1ZXMgdGhlIGRvY3VtZW50IGRlc2NyaWJlcy4gUGV0ZQ0KPj4gcmlnaHRseSBwb2ludHMg
b3V0IHRoYXQsIGFzIHdyaXR0ZW4sIHRoZSBkb2N1bWVudCBpcyBwcm92aWRpbmcNCj4+IGd1aWRh
bmNlIHRvIG5ldyBpbXBsZW1lbnRlcnMsIG5vdCB0byBjdXJyZW50IG9wZXJhdG9ycy4NCj4+IA0K
Pj4gRG9lcyBhbnlvbmUgYmVsaWV2ZSBtb3ZpbmcgdGhpcyB0byB0aGUgU3RhbmRhcmRzIFRyYWNr
IGlzIHRoZSB3cm9uZw0KPj4gdGhpbmcgdG8gZG8/IERvIHlvdSB0aGluayB0aGUgZG9jdW1lbnQg
bmVlZHMgdG8gc2F5IGFueXRoaW5nIG1vcmUNCj4+IHN0cm9uZ2x5IGFib3V0IGN1cnJlbnQgZGVw
bG95bWVudHM/DQo+PiANCj4+IFJqUw0KPj4gDQo+PiANCj4+IE9uIE9jdCAzMSwgMjAxMSwgYXQg
ODoyOCBBTSwgUGV0ZSBSZXNuaWNrIHdyb3RlOg0KPj4gDQo+Pj4gUGV0ZSBSZXNuaWNrIGhhcyBl
bnRlcmVkIHRoZSBmb2xsb3dpbmcgYmFsbG90IHBvc2l0aW9uIGZvciANCj4+PiBkcmFmdC1pZXRm
LWF2dGNvcmUtc3J0cC12YnItYXVkaW8tMDM6IERpc2N1c3MNCj4+PiANCj4+PiBXaGVuIHJlc3Bv
bmRpbmcsIHBsZWFzZSBrZWVwIHRoZSBzdWJqZWN0IGxpbmUgaW50YWN0IGFuZCByZXBseSB0bw0K
Pj4+IGFsbCBlbWFpbCBhZGRyZXNzZXMgaW5jbHVkZWQgaW4gdGhlIFRvIGFuZCBDQyBsaW5lcy4g
KEZlZWwgZnJlZSB0bw0KPj4+IGN1dCB0aGlzIGludHJvZHVjdG9yeSBwYXJhZ3JhcGgsIGhvd2V2
ZXIuKQ0KPj4+IA0KPj4+IFBsZWFzZSByZWZlciB0bw0KPj4+IGh0dHA6Ly93d3cuaWV0Zi5vcmcv
aWVzZy9zdGF0ZW1lbnQvZGlzY3Vzcy1jcml0ZXJpYS5odG1sIGZvciBtb3JlDQo+Pj4gaW5mb3Jt
YXRpb24gYWJvdXQgSUVTRyBESVNDVVNTIGFuZCBDT01NRU5UIHBvc2l0aW9ucy4NCj4+PiANCj4+
PiANCj4+PiANCj4+PiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+Pj4gDQo+Pj4gDQo+IERJU0NVU1M6DQo+Pj4g
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLQ0KPj4+IA0KPj4+IA0KPj4+IA0KPiBJIGRvbid0IHNlZSBob3cgdGhpcyBp
cyByZW1vdGVseSBhIEJDUC4gVGhpcyBzaG91bGQgYmUgb24gdGhlIHN0YW5kYXJkcw0KPiB0cmFj
ay4gSXQgaXMgc3BlY2lmeWluZyBhbGwgc29ydHMgb2YgaW1wbGVtZW50YXRpb24gcGFyYW1ldGVy
cyB0aGF0IGFyZQ0KPiBjbGVhcmx5IHRlc3RhYmxlLCBtYXkgaGF2ZSBpbnRlcm9wZXJhYmlsaXR5
IGltcGxpY2F0aW9ucywgYW5kIG1heSBjaGFuZ2UNCj4gb3ZlciB0aW1lIGFzIHdlIGdldCBpbXBs
ZW1lbnRhdGlvbiBleHBlcmllbmNlLiAoRS5nLiwgdGhlIGxlbmd0aCBvZiB0aGUNCj4gb3Zlcmhh
bmcgcGVyaW9kIG1heSBiZSBzb21ldGhpbmcgdGhhdCB3ZSBzcGVjaWZ5IGRpZmZlcmVudGx5LCB3
aGV0aGVyDQo+IFZBRCBpcyB1c2VkIG9yIG5vdCBtYXkgaGF2ZSBpbnRlcm9wZXJhYmlsaXR5IGlt
cGxpY2F0aW9ucywgZXRjLikuIFRoaXMNCj4gZGlzY3Vzc2lvbiB3b3VsZCBoYXZlIG5vcm1hbGx5
IGhhcHBlbmVkIGluIHRoZSBjb250ZXh0IG9mIGEgc2VjdXJpdHkNCj4gY29uc2lkZXJhdGlvbnMg
c2VjdGlvbiBvZiBhIGJhc2UgcHJvdG9jb2wgZG9jdW1lbnQgYW5kIHdvdWxkIGhhdmUgZ29uZQ0K
PiBhbG9uZyB0aGUgc3RhbmRhcmRzIHRyYWNrIHdpdGggdGhlIGJhc2UgcHJvdG9jb2wuIFRoZSBm
YWN0IHRoYXQgaXQgaXMNCj4gYmVpbmcgcHVibGlzaGVkIHNlcGFyYXRlbHkgc2hvdWxkbid0IGNo
YW5nZSBpdHMgdHJlYXRtZW50Lg0KPj4+IA0KPj4+IA0KPj4+IA0KPj4+IA0KPj4gDQo+PiBfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXyBBdWRpby9WaWRlbyBU
cmFuc3BvcnQNCj4+IENvcmUgTWFpbnRlbmFuY2UgYXZ0QGlldGYub3JnIA0KPj4gaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9hdnQNCj4+IA0KPiANCj4gDQo+IC0tIA0KPiAN
Cj4gTWFnbnVzIFdlc3Rlcmx1bmQNCj4gDQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gTXVsdGltZWRpYSBU
ZWNobm9sb2dpZXMsIEVyaWNzc29uIFJlc2VhcmNoIEVBQi9UVk0NCj4gLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0K
PiBFcmljc3NvbiBBQiAgICAgICAgICAgICAgICB8IFBob25lICArNDYgMTAgNzE0ODI4Nw0KPiBG
w6Ryw7ZnYXRhbiA2ICAgICAgICAgICAgICAgIHwgTW9iaWxlICs0NiA3MyAwOTQ5MDc5DQo+IFNF
LTE2NCA4MCBTdG9ja2hvbG0sIFN3ZWRlbnwgbWFpbHRvOiBtYWdudXMud2VzdGVybHVuZEBlcmlj
c3Nvbi5jb20NCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCj4gQXVkaW8vVmlkZW8gVHJhbnNwb3J0IENvcmUgTWFp
bnRlbmFuY2UNCj4gYXZ0QGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vYXZ0DQo=

From csp@csperkins.org  Thu Nov 17 01:09:52 2011
Return-Path: <csp@csperkins.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9999B21F9991; Thu, 17 Nov 2011 01:09:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.425
X-Spam-Level: 
X-Spam-Status: No, score=-103.425 tagged_above=-999 required=5 tests=[AWL=0.175, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LgQV8CMWozSS; Thu, 17 Nov 2011 01:09:48 -0800 (PST)
Received: from anchor-msapost-2.mail.demon.net (anchor-msapost-2.mail.demon.net [195.173.77.165]) by ietfa.amsl.com (Postfix) with ESMTP id 94F1421F94B4; Thu, 17 Nov 2011 01:09:48 -0800 (PST)
Received: from dhcp-4355.meeting.ietf.org ([130.129.67.85]) by anchor-post-2.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1RQxyd-0004gI-k3; Thu, 17 Nov 2011 09:09:47 +0000
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=iso-8859-1
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <43831550-B681-4AFF-96DA-69EACEE66317@cisco.com>
Date: Thu, 17 Nov 2011 17:09:36 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <8131EE51-7A18-4105-A72D-96052704C671@csperkins.org>
References: <20111031132810.20293.12093.idtracker@ietfa.amsl.com> <9AA22A68-6D9C-4709-964A-24693B7EE8DA@nostrum.com> <4EC4CA9D.5020403@ericsson.com> <43831550-B681-4AFF-96DA-69EACEE66317@cisco.com>
To: "Ali C. Begen (abegen)" <abegen@cisco.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, IETF AVTCORE WG <avt@ietf.org>, draft-ietf-avtcore-srtp-vbr-audio@tools.ietf.org, avtcore-chairs@tools.ietf.org, The IESG <iesg@ietf.org>, Pete Resnick <presnick@qualcomm.com>
Subject: Re: [AVTCORE] Pete Resnick's Discuss on draft-ietf-avtcore-srtp-vbr-audio-03: (with DISCUSS)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 17 Nov 2011 09:09:52 -0000

I don't care either way. Standards track is fine.
Colin

On 17 Nov 2011, at 17:03, Ali C. Begen (abegen) wrote:

> I looked at the document before the last call and my impression is =
that standards track is more appropriate as well.=20
>=20
> -acbegen
>=20
> On Nov 17, 2011, at 4:49 PM, "Magnus Westerlund" =
<magnus.westerlund@ericsson.com> wrote:
>=20
>> WG,
>>=20
>> There has been no responses to this topic. If you are fine with this, =
I
>> still would appreciate a few responses to indicate that you are fine
>> with going to standards track.
>>=20
>> My individual view is that there are no issue and appear appropriate.
>> This is something the WG chairs should have considered before =
requesting
>> the publication.
>>=20
>> Cheers
>>=20
>> Magnus
>>=20
>> On 2011-11-01 23:50, Robert Sparks wrote:
>>> AVTCORE Working Group:
>>>=20
>>> Pete is making an argument that the text in this document could be
>>> published as Standards Track. We've walked through the normative
>>> statements in the document together and I see his argument. My only
>>> concern is whether there is any intent in the document to tell
>>> operators of existing deployments to go change their configuration
>>> right away to avoid the security issues the document describes. Pete
>>> rightly points out that, as written, the document is providing
>>> guidance to new implementers, not to current operators.
>>>=20
>>> Does anyone believe moving this to the Standards Track is the wrong
>>> thing to do? Do you think the document needs to say anything more
>>> strongly about current deployments?
>>>=20
>>> RjS
>>>=20
>>>=20
>>> On Oct 31, 2011, at 8:28 AM, Pete Resnick wrote:
>>>=20
>>>> Pete Resnick has entered the following ballot position for=20
>>>> draft-ietf-avtcore-srtp-vbr-audio-03: Discuss
>>>>=20
>>>> When responding, please keep the subject line intact and reply to
>>>> all email addresses included in the To and CC lines. (Feel free to
>>>> cut this introductory paragraph, however.)
>>>>=20
>>>> Please refer to
>>>> http://www.ietf.org/iesg/statement/discuss-criteria.html for more
>>>> information about IESG DISCUSS and COMMENT positions.
>>>>=20
>>>>=20
>>>>=20
>>>> =
----------------------------------------------------------------------
>>>>=20
>>>>=20
>> DISCUSS:
>>>> =
----------------------------------------------------------------------
>>>>=20
>>>>=20
>>>>=20
>> I don't see how this is remotely a BCP. This should be on the =
standards
>> track. It is specifying all sorts of implementation parameters that =
are
>> clearly testable, may have interoperability implications, and may =
change
>> over time as we get implementation experience. (E.g., the length of =
the
>> overhang period may be something that we specify differently, whether
>> VAD is used or not may have interoperability implications, etc.). =
This
>> discussion would have normally happened in the context of a security
>> considerations section of a base protocol document and would have =
gone
>> along the standards track with the base protocol. The fact that it is
>> being published separately shouldn't change its treatment.
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>=20
>>> _______________________________________________ Audio/Video =
Transport
>>> Core Maintenance avt@ietf.org=20
>>> https://www.ietf.org/mailman/listinfo/avt
>>>=20
>>=20
>>=20
>> --=20
>>=20
>> Magnus Westerlund
>>=20
>> =
----------------------------------------------------------------------
>> Multimedia Technologies, Ericsson Research EAB/TVM
>> =
----------------------------------------------------------------------
>> Ericsson AB                | Phone  +46 10 7148287
>> F=E4r=F6gatan 6                | Mobile +46 73 0949079
>> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
>> =
----------------------------------------------------------------------
>>=20
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt



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




From marshall.eubanks@gmail.com  Fri Nov 18 18:35:50 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB4711E8087 for <avt@ietfa.amsl.com>; Fri, 18 Nov 2011 18:35:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.512
X-Spam-Level: 
X-Spam-Status: No, score=-103.512 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KhIUVcvb+Mjn for <avt@ietfa.amsl.com>; Fri, 18 Nov 2011 18:35:49 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6EE1011E8080 for <avt@ietf.org>; Fri, 18 Nov 2011 18:35:49 -0800 (PST)
Received: by yenm7 with SMTP id m7so618453yen.31 for <avt@ietf.org>; Fri, 18 Nov 2011 18:35:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=aoETat1LIYfT50VJ5OQml/zdulAy5a5WTgf8Xc6TQxA=; b=lVS16tOIYY4iX6q152Xptty5A0PVnH2jbMFJA+2/VH24Ml8oqBrQVtmdpqAhjaZ6JN wqFev0kqr6K0L0uc4EH0tAZ2z/N2IqAv2cmLcw6fPO6M/XLDOUyDkpMBWSFogWmmxdu/ WNN0IGRcaGxdMC0WkqtP8Pvz5QstrkwSokOcc=
MIME-Version: 1.0
Received: by 10.182.150.4 with SMTP id ue4mr1259167obb.74.1321670149033; Fri, 18 Nov 2011 18:35:49 -0800 (PST)
Received: by 10.182.159.73 with HTTP; Fri, 18 Nov 2011 18:35:48 -0800 (PST)
In-Reply-To: <D208D8C0-0B12-4378-B0BD-67863D87F133@cisco.com>
References: <450F1DC0-1C0A-4037-8D44-64486E991C88@cisco.com> <FCC100FC8D6B034CB88CD8173B2DA158155AAAD1@EXC-MBX03.tsn.tno.nl> <D208D8C0-0B12-4378-B0BD-67863D87F133@cisco.com>
Date: Fri, 18 Nov 2011 21:35:48 -0500
Message-ID: <CAJNg7VLJ7WgfvmOCuc5xGzG9WSVzR-Z3p1sKcgxj5zq6s3qRRg@mail.gmail.com>
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Cullen Jennings <fluffy@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF AVT WG <avt@ietf.org>
Subject: Re: [AVTCORE] timing requirements for IDMS
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 19 Nov 2011 02:35:50 -0000

On Mon, Nov 14, 2011 at 5:36 AM, Cullen Jennings <fluffy@cisco.com> wrote:
>
> On Nov 14, 2011, at 17:10 , Brandenburg, R. (Ray) van wrote:
>
>> Hi Cullen,
>>
>> Thanks for your mail and your interest in this topic.
>>
>> For an in-depth answer, I'm afraid I will have to depend on Kevin or Aid=
an (CC).
>
> Thank you guys - look forward to learning more.
>
>>
>> For a more practical answer: I think the main issue here is whether we n=
eed to be more accurate than 16 microseconds (as provided by a 32bit NTP-fo=
rmat timestamp) or not (in which case we would need to go for the 64bit tim=
estamp).
>

Here is a physicist's answer. The human auditory system is good to
about 0.1 radians, maybe 0.02 radians for sounds from straight ahead.
At 1 KHz, this is based on phase. At much higher frequencies, this is
based on intensity. Intensity interferometers don't depend  on phase,
so they don't really depend much on timing. This requirements will
thus be dominated by the demands at 1 KHz, where our auditory system
forms a phase interferometer. (This upper frequency phase limit is set
by the speed of sound and the distance between our ears, i.e., the
size of our heads.)

1 KHz is ~ 6000 radians of phase per second, so 0.1 radian is 1/60,000
of a second, or ~ 17 microseconds, and 0.02 radians is ~ 3
microseconds. So, I would recommend you support 64bit timestamps.

Regards
Marshall


> Fair enough. When I went to the mic today I was thinking about the use ca=
ses for synchronized playback which would not need resolution like this. On=
ce people mentioned beam forming, I realized I had been thinking about the =
wrong level. That said, I think it would be good to provide a few sentences=
 of text in the draft and explained what level was needed, and why.
>
>> From what I understand from Kevin and Aidan, the level or accuracy you w=
ould need to have in these advanced use cases is right around the level of =
1-8 microseconds.
>>
>> Ray
>>
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Cu=
llen Jennings
>> Sent: maandag 14 november 2011 6:48
>> To: IETF AVT WG
>> Subject: [AVTCORE] timing requirements for IDMS
>>
>>
>> The list seems very inconclusive about what our requirements are for tim=
ing for a audio beam steering solution. At one level I am getting the answe=
r of a single sample. I am also seeing 1 micro second. I tried to look at t=
he list traffic and saw one link that did not work. Can someone give me the=
 fundamentals of what we are trying to do. How accurate a beam do we want, =
what frequencies and sort of phase array. From this seems like one can deri=
ve the required accuracy.
>>
>> The one link I found on list (http://www.cs.ucc.ie/~ianp/CS2511/HAP.html=
) does not seem to work.
>>
>> (BTW ... glad to see the work on this. For my applications probably sync=
hronization of 10 ms would be fine but I'm not trying to do beam steering).
>>
>>
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>> This e-mail and its contents are subject to the DISCLAIMER at http://www=
.tno.nl/emaildisclaimer
>>
>>
>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>

From stephen.botzko@gmail.com  Fri Nov 18 20:58:05 2011
Return-Path: <stephen.botzko@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FF2E21F8922 for <avt@ietfa.amsl.com>; Fri, 18 Nov 2011 20:58:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.42
X-Spam-Level: 
X-Spam-Status: No, score=-3.42 tagged_above=-999 required=5 tests=[AWL=0.178,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vg3-FUbfX8Rk for <avt@ietfa.amsl.com>; Fri, 18 Nov 2011 20:58:04 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id B69FE21F88B6 for <avt@ietf.org>; Fri, 18 Nov 2011 20:58:03 -0800 (PST)
Received: by vcbfy13 with SMTP id fy13so1013719vcb.31 for <avt@ietf.org>; Fri, 18 Nov 2011 20:58:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5p6NOuMKKYy7PkxL1ZNahIIGwsQ3kiP2qx+Gw+r/xuo=; b=vXlP/t4dNb5XzpL/2O9/frKgCNqZ1xdKsjUCIGaaJgy4azeTMIClEdTLrfVeygWYOT O6MYDuLlzwbWmXBpJXqKdx7j0Md+zwjRmbbHxixIgpQSLQphZ/X6NQUdpHMDvpghxwAC PXPCEbVhEwHYoGbfqd01dxHoU8f5+6RNjeU0o=
MIME-Version: 1.0
Received: by 10.52.174.193 with SMTP id bu1mr6443243vdc.71.1321678683116; Fri, 18 Nov 2011 20:58:03 -0800 (PST)
Received: by 10.52.183.33 with HTTP; Fri, 18 Nov 2011 20:58:03 -0800 (PST)
In-Reply-To: <CAJNg7VLJ7WgfvmOCuc5xGzG9WSVzR-Z3p1sKcgxj5zq6s3qRRg@mail.gmail.com>
References: <450F1DC0-1C0A-4037-8D44-64486E991C88@cisco.com> <FCC100FC8D6B034CB88CD8173B2DA158155AAAD1@EXC-MBX03.tsn.tno.nl> <D208D8C0-0B12-4378-B0BD-67863D87F133@cisco.com> <CAJNg7VLJ7WgfvmOCuc5xGzG9WSVzR-Z3p1sKcgxj5zq6s3qRRg@mail.gmail.com>
Date: Sat, 19 Nov 2011 12:58:03 +0800
Message-ID: <CAMC7SJ6t4e9YKDxKb21tQ_3s4b5xKjfcrMjbE0CZx_pL5LpUYQ@mail.gmail.com>
From: Stephen Botzko <stephen.botzko@gmail.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec51b197b6a135a04b20f4cbc
Cc: Cullen Jennings <fluffy@cisco.com>, IETF AVT WG <avt@ietf.org>
Subject: Re: [AVTCORE] timing requirements for IDMS
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 19 Nov 2011 04:58:05 -0000

--bcaec51b197b6a135a04b20f4cbc
Content-Type: text/plain; charset=ISO-8859-1

Not sure if this is physics or neurophysiology.

In any event, using a "just noticeable difference" test, humans can hear
interaural time differences (ITD) in the 10-20 microsecond range.  There
are several studies on the subject, some are referenced here:
http://www.jneurosci.org/content/23/2/716.full.pdf

17 microsecond granularity is of course near the upper end of this range.
So a 64 bit timestamp seems appropriate, in order to ensure that the
synchronization error between the channels is below the limits of human
perception.

Stephen Botzko


On Sat, Nov 19, 2011 at 10:35 AM, Marshall Eubanks <
marshall.eubanks@gmail.com> wrote:

> On Mon, Nov 14, 2011 at 5:36 AM, Cullen Jennings <fluffy@cisco.com> wrote:
> >
> > On Nov 14, 2011, at 17:10 , Brandenburg, R. (Ray) van wrote:
> >
> >> Hi Cullen,
> >>
> >> Thanks for your mail and your interest in this topic.
> >>
> >> For an in-depth answer, I'm afraid I will have to depend on Kevin or
> Aidan (CC).
> >
> > Thank you guys - look forward to learning more.
> >
> >>
> >> For a more practical answer: I think the main issue here is whether we
> need to be more accurate than 16 microseconds (as provided by a 32bit
> NTP-format timestamp) or not (in which case we would need to go for the
> 64bit timestamp).
> >
>
> Here is a physicist's answer. The human auditory system is good to
> about 0.1 radians, maybe 0.02 radians for sounds from straight ahead.
> At 1 KHz, this is based on phase. At much higher frequencies, this is
> based on intensity. Intensity interferometers don't depend  on phase,
> so they don't really depend much on timing. This requirements will
> thus be dominated by the demands at 1 KHz, where our auditory system
> forms a phase interferometer. (This upper frequency phase limit is set
> by the speed of sound and the distance between our ears, i.e., the
> size of our heads.)
>
> 1 KHz is ~ 6000 radians of phase per second, so 0.1 radian is 1/60,000
> of a second, or ~ 17 microseconds, and 0.02 radians is ~ 3
> microseconds. So, I would recommend you support 64bit timestamps.
>
> Regards
> Marshall
>
>
> > Fair enough. When I went to the mic today I was thinking about the use
> cases for synchronized playback which would not need resolution like this.
> Once people mentioned beam forming, I realized I had been thinking about
> the wrong level. That said, I think it would be good to provide a few
> sentences of text in the draft and explained what level was needed, and why.
> >
> >> From what I understand from Kevin and Aidan, the level or accuracy you
> would need to have in these advanced use cases is right around the level of
> 1-8 microseconds.
> >>
> >> Ray
> >>
> >> -----Original Message-----
> >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Cullen Jennings
> >> Sent: maandag 14 november 2011 6:48
> >> To: IETF AVT WG
> >> Subject: [AVTCORE] timing requirements for IDMS
> >>
> >>
> >> The list seems very inconclusive about what our requirements are for
> timing for a audio beam steering solution. At one level I am getting the
> answer of a single sample. I am also seeing 1 micro second. I tried to look
> at the list traffic and saw one link that did not work. Can someone give me
> the fundamentals of what we are trying to do. How accurate a beam do we
> want, what frequencies and sort of phase array. From this seems like one
> can derive the required accuracy.
> >>
> >> The one link I found on list (
> http://www.cs.ucc.ie/~ianp/CS2511/HAP.html) does not seem to work.
> >>
> >> (BTW ... glad to see the work on this. For my applications probably
> synchronization of 10 ms would be fine but I'm not trying to do beam
> steering).
> >>
> >>
> >> _______________________________________________
> >> Audio/Video Transport Core Maintenance
> >> avt@ietf.org
> >> https://www.ietf.org/mailman/listinfo/avt
> >> This e-mail and its contents are subject to the DISCLAIMER at
> http://www.tno.nl/emaildisclaimer
> >>
> >>
> >
> > _______________________________________________
> > Audio/Video Transport Core Maintenance
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
> >
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>

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

Not sure if this is physics or neurophysiology.=A0 <br><br>In any event, us=
ing a &quot;just noticeable difference&quot; test, humans can hear interaur=
al time differences (ITD) in the 10-20 microsecond range.=A0 There are seve=
ral studies on the subject, some are referenced here:=A0 <a href=3D"http://=
www.jneurosci.org/content/23/2/716.full.pdf">http://www.jneurosci.org/conte=
nt/23/2/716.full.pdf</a><br>
<br>17 microsecond granularity is of course near the upper end of this rang=
e.=A0 So a 64 bit timestamp seems appropriate, in order to ensure that the =
synchronization error between the channels is below the limits of human per=
ception.<br>
<br>Stephen Botzko<br><br><br><div class=3D"gmail_quote">On Sat, Nov 19, 20=
11 at 10:35 AM, Marshall Eubanks <span dir=3D"ltr">&lt;<a href=3D"mailto:ma=
rshall.eubanks@gmail.com">marshall.eubanks@gmail.com</a>&gt;</span> wrote:<=
br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><div class=3D"im">On Mon, Nov 14, 2011 at 5=
:36 AM, Cullen Jennings &lt;<a href=3D"mailto:fluffy@cisco.com">fluffy@cisc=
o.com</a>&gt; wrote:<br>

&gt;<br>
</div><div class=3D"im">&gt; On Nov 14, 2011, at 17:10 , Brandenburg, R. (R=
ay) van wrote:<br>
&gt;<br>
&gt;&gt; Hi Cullen,<br>
&gt;&gt;<br>
&gt;&gt; Thanks for your mail and your interest in this topic.<br>
&gt;&gt;<br>
&gt;&gt; For an in-depth answer, I&#39;m afraid I will have to depend on Ke=
vin or Aidan (CC).<br>
&gt;<br>
&gt; Thank you guys - look forward to learning more.<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; For a more practical answer: I think the main issue here is whethe=
r we need to be more accurate than 16 microseconds (as provided by a 32bit =
NTP-format timestamp) or not (in which case we would need to go for the 64b=
it timestamp).<br>

&gt;<br>
<br>
</div>Here is a physicist&#39;s answer. The human auditory system is good t=
o<br>
about 0.1 radians, maybe 0.02 radians for sounds from straight ahead.<br>
At 1 KHz, this is based on phase. At much higher frequencies, this is<br>
based on intensity. Intensity interferometers don&#39;t depend =A0on phase,=
<br>
so they don&#39;t really depend much on timing. This requirements will<br>
thus be dominated by the demands at 1 KHz, where our auditory system<br>
forms a phase interferometer. (This upper frequency phase limit is set<br>
by the speed of sound and the distance between our ears, i.e., the<br>
size of our heads.)<br>
<br>
1 KHz is ~ 6000 radians of phase per second, so 0.1 radian is 1/60,000<br>
of a second, or ~ 17 microseconds, and 0.02 radians is ~ 3<br>
microseconds. So, I would recommend you support 64bit timestamps.<br>
<br>
Regards<br>
<font color=3D"#888888">Marshall<br>
</font><div><div></div><div class=3D"h5"><br>
<br>
&gt; Fair enough. When I went to the mic today I was thinking about the use=
 cases for synchronized playback which would not need resolution like this.=
 Once people mentioned beam forming, I realized I had been thinking about t=
he wrong level. That said, I think it would be good to provide a few senten=
ces of text in the draft and explained what level was needed, and why.<br>

&gt;<br>
&gt;&gt; From what I understand from Kevin and Aidan, the level or accuracy=
 you would need to have in these advanced use cases is right around the lev=
el of 1-8 microseconds.<br>
&gt;&gt;<br>
&gt;&gt; Ray<br>
&gt;&gt;<br>
&gt;&gt; -----Original Message-----<br>
&gt;&gt; From: <a href=3D"mailto:avt-bounces@ietf.org">avt-bounces@ietf.org=
</a> [mailto:<a href=3D"mailto:avt-bounces@ietf.org">avt-bounces@ietf.org</=
a>] On Behalf Of Cullen Jennings<br>
&gt;&gt; Sent: maandag 14 november 2011 6:48<br>
&gt;&gt; To: IETF AVT WG<br>
&gt;&gt; Subject: [AVTCORE] timing requirements for IDMS<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; The list seems very inconclusive about what our requirements are f=
or timing for a audio beam steering solution. At one level I am getting the=
 answer of a single sample. I am also seeing 1 micro second. I tried to loo=
k at the list traffic and saw one link that did not work. Can someone give =
me the fundamentals of what we are trying to do. How accurate a beam do we =
want, what frequencies and sort of phase array. From this seems like one ca=
n derive the required accuracy.<br>

&gt;&gt;<br>
&gt;&gt; The one link I found on list (<a href=3D"http://www.cs.ucc.ie/%7Ei=
anp/CS2511/HAP.html" target=3D"_blank">http://www.cs.ucc.ie/~ianp/CS2511/HA=
P.html</a>) does not seem to work.<br>
&gt;&gt;<br>
&gt;&gt; (BTW ... glad to see the work on this. For my applications probabl=
y synchronization of 10 ms would be fine but I&#39;m not trying to do beam =
steering).<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; Audio/Video Transport Core Maintenance<br>
&gt;&gt; <a href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/avt" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/avt</a><br>
&gt;&gt; This e-mail and its contents are subject to the DISCLAIMER at <a h=
ref=3D"http://www.tno.nl/emaildisclaimer" target=3D"_blank">http://www.tno.=
nl/emaildisclaimer</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; Audio/Video Transport Core Maintenance<br>
&gt; <a href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/avt" target=3D"_blank=
">https://www.ietf.org/mailman/listinfo/avt</a><br>
&gt;<br>
_______________________________________________<br>
Audio/Video Transport Core Maintenance<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>
</div></div></blockquote></div><br>

--bcaec51b197b6a135a04b20f4cbc--

From harald@alvestrand.no  Tue Nov 22 06:08:34 2011
Return-Path: <harald@alvestrand.no>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EBFE21F8CE8 for <avt@ietfa.amsl.com>; Tue, 22 Nov 2011 06:08:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.545
X-Spam-Level: 
X-Spam-Status: No, score=-110.545 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B1wl6Zo9OXm6 for <avt@ietfa.amsl.com>; Tue, 22 Nov 2011 06:08:33 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id EEEB521F8CA9 for <avt@ietf.org>; Tue, 22 Nov 2011 06:08:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id CD5C739E074 for <avt@ietf.org>; Tue, 22 Nov 2011 15:08:20 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uG7mBr7BZ8IH for <avt@ietf.org>; Tue, 22 Nov 2011 15:08:19 +0100 (CET)
Received: from hta-dell.lul.corp.google.com (unknown [62.20.124.50]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 60A2D39E04C for <avt@ietf.org>; Tue, 22 Nov 2011 15:08:19 +0100 (CET)
Message-ID: <4ECBACD3.7090504@alvestrand.no>
Date: Tue, 22 Nov 2011 15:08:19 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15
MIME-Version: 1.0
To: avt@ietf.org
References: <EADCEEE0AE4A7F46BD61061696794D98F753FD@SZXEML519-MBS.china.huawei.com> <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com>
In-Reply-To: <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------090502010202030603040501"
Subject: Re: [AVTCORE] Call for consensus on multiplexing multipe media streams.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 22 Nov 2011 14:08:34 -0000

This is a multi-part message in MIME format.
--------------090502010202030603040501
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 8bit

Just a note - I count 8 people as having stated an opinion so far.

That's fewer than the number of people who had an opinion in AVTEXT.
Of course, people may have been convinced by the strong arguments of
those who said we can't decide yet.... in which case, it makes sense to
speak up for alternative 4.

On 11/14/2011 09:56 AM, Roni even wrote:
>
> Hi
>
> At the AVTcore session we had two presentations. One from Magnus
> proposing the multiplexing of multiple RTP sessions over a single
> transport flow and the second from Jonathan Lennox proposing
> multiplexing multiple media types in a single RTP session.
>
> Magnus asked in the beginning of his presentation if the WG believe
> that the problem of providing multiple RTP sessions over a single
> transport flow should be solved. The response from the room was that
> it was already discussed in IETF 81 and there was interest in doing
> this work.
>
> In IETF81 there was an interest in doing both options. During the
> session today we did not have time to ask for consensus.
>
> So the WG chairs are asking which direction to take
>
> The options we have are:
>
> 1. Go forward with both solutions.
>
> 2. Only define multiplexing of multiple RTP sessions in a single
> transport flow.
>
> 3. Only define multiplexing of multiple media types in a single RTP
> session.
>
> 4. Not enough information in order to decide, more discussion is needed.
>
> There were about 20 people in the AVTcore session who raised there
> hands when asked if they have opinion
>
> Thanks
>
> Roni Even
>
> AVTcore co-chair
>
> ¡¡
>
>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


--------------090502010202030603040501
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: 8bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=GB2312" http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Just a note - I count 8 people as having stated an opinion so far.<br>
    <br>
    That's fewer than the number of people who had an opinion in AVTEXT.<br>
    Of course, people may have been convinced by the strong arguments of
    those who said we can't decide yet.... in which case, it makes sense
    to speak up for alternative 4.<br>
    <br>
    On 11/14/2011 09:56 AM, Roni even wrote:
    <blockquote
cite="mid:EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=GB2312">
      <style id="owaParaStyle">P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
      <div style="direction: ltr; font-family: Tahoma; color: rgb(0, 0,
        0); font-size: 10pt;">
        <p>Hi</p>
        <div style="font-family: Times New Roman; color: rgb(0, 0, 0);
          font-size: 16px;">
          <div>
            <div style="font-family: Tahoma; direction: ltr; color:
              rgb(0, 0, 0); font-size: 10pt;">
              <p>At the&nbsp;AVTcore session we had two presentations. One
                from Magnus proposing the multiplexing of multiple RTP
                sessions over a single transport flow and the second
                from Jonathan Lennox proposing multiplexing multiple
                media types in a single RTP session.</p>
              <p>&nbsp;</p>
              <p>Magnus asked in the beginning of his presentation if
                the WG believe that the problem of providing multiple
                RTP sessions over a single transport flow should be
                solved. The response from the room was that it was
                already discussed in IETF 81 and there was interest in
                doing this work. </p>
              <p>In IETF81 there was an interest in doing both options.
                During the session today we did not have time to ask for
                consensus.</p>
              <p>&nbsp;</p>
              <p>&nbsp;</p>
              <p>So the WG chairs are asking which direction to take </p>
              <p>&nbsp;</p>
              <p>The options we have are:</p>
              <p>&nbsp;</p>
              <p>1. Go forward with both solutions.</p>
              <p>2. Only define multiplexing of multiple RTP sessions in
                a single transport flow.</p>
              <p>3. Only define multiplexing of multiple media types in
                a single RTP session.</p>
              <p>4. Not enough information in order to decide, more
                discussion is needed.</p>
              <p>&nbsp;</p>
              <p>&nbsp;</p>
              <p>There were about 20 people in the&nbsp;AVTcore session who
                raised there hands when asked if they have opinion</p>
              <p>&nbsp;</p>
              <p>Thanks</p>
              <p>Roni&nbsp;Even</p>
              <p>AVTcore&nbsp;co-chair</p>
              <p>&nbsp;</p>
              <p>¡¡</p>
              <font size="2">
                <p>&nbsp;</p>
              </font></div>
          </div>
        </div>
      </div>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Audio/Video Transport Core Maintenance
<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>
  </body>
</html>

--------------090502010202030603040501--

From mary.ietf.barnes@gmail.com  Tue Nov 22 08:00:47 2011
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D7C411E80A0 for <avt@ietfa.amsl.com>; Tue, 22 Nov 2011 08:00:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.257
X-Spam-Level: 
X-Spam-Status: No, score=-103.257 tagged_above=-999 required=5 tests=[AWL=0.342, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vOahTNqGjj3c for <avt@ietfa.amsl.com>; Tue, 22 Nov 2011 08:00:46 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 88ED511E8096 for <avt@ietf.org>; Tue, 22 Nov 2011 08:00:46 -0800 (PST)
Received: by vcbfy13 with SMTP id fy13so431017vcb.31 for <avt@ietf.org>; Tue, 22 Nov 2011 08:00:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=qFFDI9it752VJA3Rkr4mEfgU0g6g4Uvev67j2pTcDec=; b=U72HDy/TuUiAQ8jOx+mxHPt/5QMw2R7gIgIjCRBXonUqV7pQTkQZnes6dhY3VxRS/j 608XniO9lC5xImN8nQak/mVXIXwvmH5ydPNz5xj3SaKvIyGqbCz+XzXy+f8EPLdvFt+7 jCsRK+NIusc2odbFj3W5Zg+7Ajzb8i+0asZ0U=
MIME-Version: 1.0
Received: by 10.220.148.68 with SMTP id o4mr1224824vcv.123.1321977646044; Tue, 22 Nov 2011 08:00:46 -0800 (PST)
Received: by 10.52.175.131 with HTTP; Tue, 22 Nov 2011 08:00:45 -0800 (PST)
In-Reply-To: <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com>
References: <EADCEEE0AE4A7F46BD61061696794D98F753FD@SZXEML519-MBS.china.huawei.com> <EADCEEE0AE4A7F46BD61061696794D98F7543B@SZXEML519-MBS.china.huawei.com>
Date: Tue, 22 Nov 2011 10:00:45 -0600
Message-ID: <CAHBDyN5x_PW76dfXEPj__hDJwBFq_hkOkRxS8Q+RKDAQTKN7sQ@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Roni even <Even.roni@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] Call for consensus on multiplexing multipe media streams.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 22 Nov 2011 16:00:47 -0000

I think there is a 5th option:

5) Either 2) or 3) as I think some folks would like a single solution,
but it doesn't matter which of the two is selected.

Regards,
Mary.

2011/11/14 Roni even <Even.roni@huawei.com>:
> Hi
>
> At the=A0AVTcore session we had two presentations. One from Magnus propos=
ing
> the multiplexing of multiple RTP sessions over a single transport flow an=
d
> the second from Jonathan Lennox proposing multiplexing multiple media typ=
es
> in a single RTP session.
>
>
>
> Magnus asked in the beginning of his presentation if the WG believe that =
the
> problem of providing multiple RTP sessions over a single transport flow
> should be solved. The response from the room was that it was already
> discussed in IETF 81 and there was interest in doing this work.
>
> In IETF81 there was an interest in doing both options. During the session
> today we did not have time to ask for consensus.
>
>
>
>
>
> So the WG chairs are asking which direction to take
>
>
>
> The options we have are:
>
>
>
> 1. Go forward with both solutions.
>
> 2. Only define multiplexing of multiple RTP sessions in a single transpor=
t
> flow.
>
> 3. Only define multiplexing of multiple media types in a single RTP sessi=
on.
>
> 4. Not enough information in order to decide, more discussion is needed.
>
>
>
>
>
> There were about 20 people in the=A0AVTcore session who raised there hand=
s
> when asked if they have opinion
>
>
>
> Thanks
>
> Roni=A0Even
>
> AVTcore=A0co-chair
>
>
>
>
>
>
>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>
>

From csp@csperkins.org  Mon Nov 28 08:28:49 2011
Return-Path: <csp@csperkins.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4D3921F8876 for <avt@ietfa.amsl.com>; Mon, 28 Nov 2011 08:28:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VS+bc-Y8EVcd for <avt@ietfa.amsl.com>; Mon, 28 Nov 2011 08:28:49 -0800 (PST)
Received: from lon1-msapost-2.mail.demon.net (lon1-msapost-2.mail.demon.net [195.173.77.181]) by ietfa.amsl.com (Postfix) with ESMTP id 1255C21F8468 for <avt@ietf.org>; Mon, 28 Nov 2011 08:28:49 -0800 (PST)
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]) by lon1-post-2.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1RV44W-0001CX-Zb for avt@ietf.org; Mon, 28 Nov 2011 16:28:48 +0000
From: Colin Perkins <csp@csperkins.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 28 Nov 2011 16:28:47 +0000
Message-Id: <18BAEB91-E150-4DB2-B8ED-DB376E222E70@csperkins.org>
To: IETF AVTCORE WG <avt@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1251.1)
X-Mailer: Apple Mail (2.1251.1)
Subject: [AVTCORE] Open issues with draft-ietf-avtcore-ecn-for-rtp-05.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 28 Nov 2011 16:28:49 -0000

AVTCORE working group,

Following on from the presentation in AVTCORE at IETF 82, there are two =
remaining open issues with the ECN-for-RTP draft:

1) Interactions with ICE: Dan Wing noted that the rules for checking =
that a path is ECN capable using STUN/ICE can add additional call setup =
time, and proposed that the draft be modified to allow STUN check for =
ECN validation to be done in parallel with the media. The authors agree =
with this, and are working with Dan to draft appropriate text.

2) Support for Multicast: Bill Ver Steeg noted that the draft needs all =
receivers, and the paths to all receivers, of a multicast flow to =
support ECN, else it falls back to not using ECN. This is very =
conservative, and does not scale to large groups. The authors agree with =
the concern, but don't currently have an alternative that doesn't cause =
serious fairness problems. We propose to add a note to say that the =
multicast ECN rules are known to be conservative, and may be relaxed in =
a future version of the specification; and to encourage experimentation =
to determine a less conservative, but still relatively fair, response.

If there are comments or objections to these proposals, please raise =
them on the list. We expect to submit a revised draft before the =
Christmas holiday.

Colin


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




From fluffy@cisco.com  Mon Nov 28 12:44:46 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 511B41F0C94 for <avt@ietfa.amsl.com>; Mon, 28 Nov 2011 12:44:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cOgx6GAn5Yqh for <avt@ietfa.amsl.com>; Mon, 28 Nov 2011 12:44:45 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 64B9F1F0C93 for <avt@ietf.org>; Mon, 28 Nov 2011 12:44:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=3969; q=dns/txt; s=iport; t=1322513085; x=1323722685; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=VdyKtV4ghW2a+MMnpZNPNbPZEJWr+SMWorC2eDS/O8Q=; b=N0+ORnw0iNRkaub5EhMm2FVQKv18JE6cPh334V4AYJ7+tZIgfmhe6Cnl eaKniZ5hCbr4YtLAIOPTAhr0MWc7dBa6BoOJG+2qrrl+NE8Cj333p72Ur zTChfEteIO+T13JJDE7jrB4L3JgMk0XMn3SOE9s81mMaDXAjJ+eEQZy/w g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFADTy006rRDoG/2dsb2JhbABDFqpegQWBcgEBAQMBAQEBDwEnMwwFBwQLEQQBAQEnBycfCQgGExsHh2MImFEBnlmJf2MEiCGMKYVAjGs
X-IronPort-AV: E=Sophos;i="4.69,586,1315180800"; d="scan'208";a="16583245"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 28 Nov 2011 20:44:45 +0000
Received: from [192.168.4.100] (sjc-fluffy-8914.cisco.com [10.20.249.165]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pASKiiYu006136; Mon, 28 Nov 2011 20:44:44 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <CAJNg7VLJ7WgfvmOCuc5xGzG9WSVzR-Z3p1sKcgxj5zq6s3qRRg@mail.gmail.com>
Date: Mon, 28 Nov 2011 13:44:44 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7DAA38C3-B58D-4151-A39A-49D0881BBD65@cisco.com>
References: <450F1DC0-1C0A-4037-8D44-64486E991C88@cisco.com> <FCC100FC8D6B034CB88CD8173B2DA158155AAAD1@EXC-MBX03.tsn.tno.nl> <D208D8C0-0B12-4378-B0BD-67863D87F133@cisco.com> <CAJNg7VLJ7WgfvmOCuc5xGzG9WSVzR-Z3p1sKcgxj5zq6s3qRRg@mail.gmail.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF AVT WG <avt@ietf.org>
Subject: Re: [AVTCORE] timing requirements for IDMS
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 28 Nov 2011 20:44:46 -0000

Thanks Stephen, Marshall, and Kevin. Theses were the sort of answers I =
was looking for - I think it might be worth at least a sentence or two =
in the draft explaining beam forming with phrase arrayed speakers =
required accuracies approaching the low number of micro seconds. =20

On Nov 18, 2011, at 7:35 PM, Marshall Eubanks wrote:

> On Mon, Nov 14, 2011 at 5:36 AM, Cullen Jennings <fluffy@cisco.com> =
wrote:
>>=20
>> On Nov 14, 2011, at 17:10 , Brandenburg, R. (Ray) van wrote:
>>=20
>>> Hi Cullen,
>>>=20
>>> Thanks for your mail and your interest in this topic.
>>>=20
>>> For an in-depth answer, I'm afraid I will have to depend on Kevin or =
Aidan (CC).
>>=20
>> Thank you guys - look forward to learning more.
>>=20
>>>=20
>>> For a more practical answer: I think the main issue here is whether =
we need to be more accurate than 16 microseconds (as provided by a 32bit =
NTP-format timestamp) or not (in which case we would need to go for the =
64bit timestamp).
>>=20
>=20
> Here is a physicist's answer. The human auditory system is good to
> about 0.1 radians, maybe 0.02 radians for sounds from straight ahead.
> At 1 KHz, this is based on phase. At much higher frequencies, this is
> based on intensity. Intensity interferometers don't depend  on phase,
> so they don't really depend much on timing. This requirements will
> thus be dominated by the demands at 1 KHz, where our auditory system
> forms a phase interferometer. (This upper frequency phase limit is set
> by the speed of sound and the distance between our ears, i.e., the
> size of our heads.)
>=20
> 1 KHz is ~ 6000 radians of phase per second, so 0.1 radian is 1/60,000
> of a second, or ~ 17 microseconds, and 0.02 radians is ~ 3
> microseconds. So, I would recommend you support 64bit timestamps.
>=20
> Regards
> Marshall
>=20
>=20
>> Fair enough. When I went to the mic today I was thinking about the =
use cases for synchronized playback which would not need resolution like =
this. Once people mentioned beam forming, I realized I had been thinking =
about the wrong level. That said, I think it would be good to provide a =
few sentences of text in the draft and explained what level was needed, =
and why.
>>=20
>>> =46rom what I understand from Kevin and Aidan, the level or accuracy =
you would need to have in these advanced use cases is right around the =
level of 1-8 microseconds.
>>>=20
>>> Ray
>>>=20
>>> -----Original Message-----
>>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf =
Of Cullen Jennings
>>> Sent: maandag 14 november 2011 6:48
>>> To: IETF AVT WG
>>> Subject: [AVTCORE] timing requirements for IDMS
>>>=20
>>>=20
>>> The list seems very inconclusive about what our requirements are for =
timing for a audio beam steering solution. At one level I am getting the =
answer of a single sample. I am also seeing 1 micro second. I tried to =
look at the list traffic and saw one link that did not work. Can someone =
give me the fundamentals of what we are trying to do. How accurate a =
beam do we want, what frequencies and sort of phase array. =46rom this =
seems like one can derive the required accuracy.
>>>=20
>>> The one link I found on list =
(http://www.cs.ucc.ie/~ianp/CS2511/HAP.html) does not seem to work.
>>>=20
>>> (BTW ... glad to see the work on this. For my applications probably =
synchronization of 10 ms would be fine but I'm not trying to do beam =
steering).
>>>=20
>>>=20
>>> _______________________________________________
>>> Audio/Video Transport Core Maintenance
>>> avt@ietf.org
>>> https://www.ietf.org/mailman/listinfo/avt
>>> This e-mail and its contents are subject to the DISCLAIMER at =
http://www.tno.nl/emaildisclaimer
>>>=20
>>>=20
>>=20
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>>=20


From ietf-ipr@ietf.org  Mon Nov 28 14:00:01 2011
Return-Path: <ietf-ipr@ietf.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C82311E812C; Mon, 28 Nov 2011 14:00:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.227
X-Spam-Level: 
X-Spam-Status: No, score=-102.227 tagged_above=-999 required=5 tests=[AWL=0.372, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cqxrkTDalEnm; Mon, 28 Nov 2011 14:00:00 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E706D11E8128; Mon, 28 Nov 2011 14:00:00 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-ipr@ietf.org>
To: sva@kom.auc.dk, alan.duric@globalipsound.com,
X-Test-IDTracker: no
Message-ID: <20111128220000.28444.11215.idtracker@ietfa.amsl.com>
Date: Mon, 28 Nov 2011 14:00:00 -0800
Cc: avt@ietf.org, ipr-announce@ietf.org
Subject: [AVTCORE] IPR Disclosure: Google Inc.'s Statement about IPR related to RFC 3951	and RFC 3952
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 28 Nov 2011 22:00:01 -0000

Dear S Andersen, Alan Duric:

 An IPR disclosure that pertains to your RFC entitled "RTP Payload Format f=
or
iLBC Speech" (RFC3952) was submitted to the IETF Secretariat on 2011-11-08 =
and
has been posted on the "IETF Page of Intellectual Property Rights Disclosur=
es"
(https://datatracker.ietf.org/ipr/1649/). The title of the IPR disclosure is
"Google Inc.'s Statement about IPR related to RFC 3951 and RFC 3952."");

The IETF Secretariat


From ietf-ipr@ietf.org  Mon Nov 28 14:00:01 2011
Return-Path: <ietf-ipr@ietf.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AE0E11E8129; Mon, 28 Nov 2011 14:00:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.229
X-Spam-Level: 
X-Spam-Status: No, score=-102.229 tagged_above=-999 required=5 tests=[AWL=0.370, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XU3+Dvflu2Jf; Mon, 28 Nov 2011 14:00:00 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE03511E8125; Mon, 28 Nov 2011 14:00:00 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-ipr@ietf.org>
To: steven.c.andersen@lmco.com,
X-Test-IDTracker: no
Message-ID: <20111128220000.28444.17842.idtracker@ietfa.amsl.com>
Date: Mon, 28 Nov 2011 14:00:00 -0800
Cc: avt@ietf.org, ipr-announce@ietf.org
Subject: [AVTCORE] IPR Disclosure: Google Inc.'s Statement about IPR related to RFC 3951	and RFC 3952
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 28 Nov 2011 22:00:01 -0000

Dear Steven Andersen:

 An IPR disclosure that pertains to your RFC entitled "Internet Low Bit Rate
Codec" (RFC3951) was submitted to the IETF Secretariat on 2011-11-08 and has
been posted on the "IETF Page of Intellectual Property Rights Disclosures"
(https://datatracker.ietf.org/ipr/1649/). The title of the IPR disclosure is
"Google Inc.'s Statement about IPR related to RFC 3951 and RFC 3952."");

The IETF Secretariat


From internet-drafts@ietf.org  Mon Nov 28 23:39:28 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 683FB11E8089; Mon, 28 Nov 2011 23:39:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.561
X-Spam-Level: 
X-Spam-Status: No, score=-102.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9MtvCDQAgjFE; Mon, 28 Nov 2011 23:39:27 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 914C711E8082; Mon, 28 Nov 2011 23:39:27 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64
Message-ID: <20111129073927.6509.8889.idtracker@ietfa.amsl.com>
Date: Mon, 28 Nov 2011 23:39:27 -0800
Cc: avt@ietf.org
Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-07.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 29 Nov 2011 07:39:28 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Audio/Video Transport Core Maintenanc=
e Working Group of the IETF.

	Title           : Monitoring Architectures for RTP
	Author(s)       : Qin Wu
                          Geoff Hunt
                          Philip Arden
	Filename        : draft-ietf-avtcore-monarch-07.txt
	Pages           : 25
	Date            : 2011-11-28

   This memo proposes an architecture for extending RTCP with a new RTCP
   XR (RFC3611) block type to report new metrics regarding media
   transmission or reception quality, following RTCP guideline
   established in RFC5968.  This memo suggests that a new block should
   contain a single metric or a small number of metrics relevant to a
   single parameter of interest or concern, rather than containing a
   number of metrics which attempt to provide full coverage of all those
   parameters of concern to a specific application.  Applications may
   then "mix and match" to create a set of blocks which covers their set
   of concerns.  Where possible, a specific block should be designed to
   be re-usable across more than one application, for example, for all
   of voice, streaming audio and video.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-07.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-07.txt


From internet-drafts@ietf.org  Mon Nov 28 23:56:13 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A4C021F8B1D; Mon, 28 Nov 2011 23:56:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Zw9YBw66v0M; Mon, 28 Nov 2011 23:56:13 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39CC621F8B16; Mon, 28 Nov 2011 23:56:13 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64
Message-ID: <20111129075613.12419.4377.idtracker@ietfa.amsl.com>
Date: Mon, 28 Nov 2011 23:56:13 -0800
Cc: avt@ietf.org
Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 29 Nov 2011 07:56:13 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Audio/Video Transport Core Maintenanc=
e Working Group of the IETF.

	Title           : Monitoring Architectures for RTP
	Author(s)       : Qin Wu
                          Geoff Hunt
                          Philip Arden
	Filename        : draft-ietf-avtcore-monarch-08.txt
	Pages           : 25
	Date            : 2011-11-28

   This memo proposes an architecture for extending RTCP with a new RTCP
   XR (RFC3611) block type to report new metrics regarding media
   transmission or reception quality, following RTCP guideline
   established in RFC5968.  This memo suggests that a new block should
   contain a single metric or a small number of metrics relevant to a
   single parameter of interest or concern, rather than containing a
   number of metrics which attempt to provide full coverage of all those
   parameters of concern to a specific application.  Applications may
   then "mix and match" to create a set of blocks which covers their set
   of concerns.  Where possible, a specific block should be designed to
   be re-usable across more than one application, for example, for all
   of voice, streaming audio and video.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt


From bill.wu@huawei.com  Mon Nov 28 23:59:09 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CABC721F8B1D for <avt@ietfa.amsl.com>; Mon, 28 Nov 2011 23:59:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00nBBxsg5uJp for <avt@ietfa.amsl.com>; Mon, 28 Nov 2011 23:59:09 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 7D6221F0C36 for <avt@ietf.org>; Mon, 28 Nov 2011 23:59:08 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVE008QQWUD5A@szxga03-in.huawei.com> for avt@ietf.org; Tue, 29 Nov 2011 15:59:01 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVE00FZYWUCMR@szxga03-in.huawei.com> for avt@ietf.org; Tue, 29 Nov 2011 15:59:01 +0800 (CST)
Received: from szxeml207-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFK10627; Tue, 29 Nov 2011 15:59:00 +0800
Received: from SZXEML401-HUB.china.huawei.com (10.82.67.31) by szxeml207-edg.china.huawei.com (172.24.2.59) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 29 Nov 2011 15:58:57 +0800
Received: from w53375q (10.138.41.130) by szxeml401-hub.china.huawei.com (10.82.67.31) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 29 Nov 2011 15:58:49 +0800
Date: Tue, 29 Nov 2011 15:58:49 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: avt@ietf.org
Message-id: <82D7A2A79913454F98689DCF72F66852@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: [AVTCORE] Fw:  I-D Action: draft-ietf-avtcore-monarch-07.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 29 Nov 2011 07:59:09 -0000

Hi, all:
This has just address minor issue pointed out by Colin pointed out during the meeting. We are not aware of any remaining open issue and the draft should be ready for the chair's review
and move forward.

Diff:
http://tools.ietf.org/rfcdiff?difftype=--hwdiff&url2=draft-ietf-avtcore-monarch-08.txt

-Qin
----- Original Message ----- 
From: <internet-drafts@ietf.org>
To: <i-d-announce@ietf.org>
Cc: <avt@ietf.org>
Sent: Tuesday, November 29, 2011 3:39 PM
Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-07.txt


> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Audio/Video Transport Core Maintenance Working Group of the IETF.
> 
> Title           : Monitoring Architectures for RTP
> Author(s)       : Qin Wu
>                          Geoff Hunt
>                          Philip Arden
> Filename        : draft-ietf-avtcore-monarch-08.txt
> Pages           : 25
> Date            : 2011-11-28
> 
>   This memo proposes an architecture for extending RTCP with a new RTCP
>   XR (RFC3611) block type to report new metrics regarding media
>   transmission or reception quality, following RTCP guideline
>   established in RFC5968.  This memo suggests that a new block should
>   contain a single metric or a small number of metrics relevant to a
>   single parameter of interest or concern, rather than containing a
>   number of metrics which attempt to provide full coverage of all those
>   parameters of concern to a specific application.  Applications may
>   then "mix and match" to create a set of blocks which covers their set
>   of concerns.  Where possible, a specific block should be designed to
>   be re-usable across more than one application, for example, for all
>   of voice, streaming audio and video.
> 
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt

From internet-drafts@ietf.org  Tue Nov 29 00:32:47 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAA3E21F8B16; Tue, 29 Nov 2011 00:32:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level: 
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x1bXZ-I15mHK; Tue, 29 Nov 2011 00:32:47 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55DEF21F8672; Tue, 29 Nov 2011 00:32:47 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64
Message-ID: <20111129083247.32308.83766.idtracker@ietfa.amsl.com>
Date: Tue, 29 Nov 2011 00:32:47 -0800
Cc: avt@ietf.org
Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-feedback-supression-rtp-09.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 29 Nov 2011 08:32:47 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Audio/Video Transport Core Maintenanc=
e Working Group of the IETF.

	Title           : RTCP Extension for Third-party Loss Report
	Author(s)       : Qin Wu
                          Frank Xia
                          Roni Even
	Filename        : draft-ietf-avtcore-feedback-supression-rtp-09.txt
	Pages           : 17
	Date            : 2011-11-29

   In a large RTP session using the RTCP feedback mechanism defined in
   RFC 4585, a feedback target may experience transient overload if some
   event causes a large number of receivers to send feedback at once.
   This overload is usually avoided by ensuring that feedback reports
   are forwarded to all receivers, allowing them to avoid sending
   duplicate feedback reports.  However, there are cases where it is not
   recommended to forward feedback reports, and this may allow feedback
   implosion.  This memo discusses these cases and defines a new RTCP
   third-party loss report that can be used to inform receivers that the
   feedback target is aware of some loss event, allowing them to
   suppress feedback.  Associated SDP signalling is also defined.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avtcore-feedback-supression-=
rtp-09.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-feedback-supression-r=
tp-09.txt


From bill.wu@huawei.com  Tue Nov 29 00:53:49 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AFDF21F8C06 for <avt@ietfa.amsl.com>; Tue, 29 Nov 2011 00:53:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.766
X-Spam-Level: 
X-Spam-Status: No, score=-5.766 tagged_above=-999 required=5 tests=[AWL=-0.833, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_OBFU_BELIEVE=1.666]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Jsbed5KYgDd for <avt@ietfa.amsl.com>; Tue, 29 Nov 2011 00:53:48 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id D30B321F8C00 for <avt@ietf.org>; Tue, 29 Nov 2011 00:53:47 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVE00KICZBQEP@szxga04-in.huawei.com> for avt@ietf.org; Tue, 29 Nov 2011 16:52:38 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVE00GCCZAZNH@szxga04-in.huawei.com> for avt@ietf.org; Tue, 29 Nov 2011 16:52:38 +0800 (CST)
Received: from szxeml205-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFK16712; Tue, 29 Nov 2011 16:52:37 +0800
Received: from SZXEML418-HUB.china.huawei.com (10.82.67.157) by szxeml205-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 29 Nov 2011 16:52:35 +0800
Received: from w53375q (10.138.41.130) by szxeml418-hub.china.huawei.com (10.82.67.157) with Microsoft SMTP Server (TLS) id 14.1.218.12; Tue, 29 Nov 2011 16:52:12 +0800
Date: Tue, 29 Nov 2011 16:52:11 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: avt@ietf.org
Message-id: <3785C80A53BA4322A17FB64EBE1B2F94@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: multipart/alternative; boundary="Boundary_(ID_6UjPZ2JPAeiZM7KqNsYAGQ)"
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: [AVTCORE] Updated Feedback Suppression daft based on IETF 82 meeting discussion
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 29 Nov 2011 08:53:49 -0000

--Boundary_(ID_6UjPZ2JPAeiZM7KqNsYAGQ)
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT

Hi, folks:
This revision is used to address the only remaining issue with draft-ietf-avtcore-feedback-suppression-rtp draft  discussed in IETF Taipei meeting.

It was noted that calculating Suppression Interval based on the RTT values measured between original media source, middle-box that sends the TPLR, and the receiver of the is complex,
Therefore it was agreed in the meeting to take simple and staightforward way to address this issue:
 i.e.,deal with TPLR in the same way as reciving NACK and follow the rules for NACK suppression in RFC 4585 when a TPLR is received. 
No additional reciever behavior is required. 

We are not aware any other open issues remained in this document and belileve this version is ready for chair review and  move forward. 

Diff is:
http://tools.ietf.org/rfcdiff?url2=draft-ietf-avtcore-feedback-supression-rtp-09

Regards!
-Qin

--Boundary_(ID_6UjPZ2JPAeiZM7KqNsYAGQ)
Content-type: text/html; charset=gb2312
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=gb2312" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19154">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face="Times New Roman">Hi, folks:<BR>This revision is used to address 
the only remaining issue with draft-ietf-avtcore-feedback-suppression-rtp 
draft&nbsp; discussed in IETF Taipei meeting.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face="Times New Roman">It was noted that calculating Suppression 
Interval based on the RTT values measured between original media source, 
middle-box that sends the TPLR, and the receiver of the is complex,<BR>Therefore 
it was agreed in the meeting to take simple and staightforward way to address 
this issue:<BR>&nbsp;i.e.,deal with TPLR in the same way as reciving NACK and 
follow the rules for NACK suppression in RFC 4585 when a TPLR is received. 
<BR>No additional reciever behavior is required. </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face="Times New Roman">We are not aware any other open issues 
remained in this document and belileve this version is ready for chair review 
and&nbsp; move forward. </FONT></DIV>
<DIV><FONT size=2></FONT>&nbsp;</DIV>
<DIV><FONT face="Times New Roman">Diff is:<BR><A 
href="http://tools.ietf.org/rfcdiff?url2=draft-ietf-avtcore-feedback-supression-rtp-09">http://tools.ietf.org/rfcdiff?url2=draft-ietf-avtcore-feedback-supression-rtp-09</A></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face="Times New Roman">Regards!<BR>-Qin</FONT></DIV>
<DIV><FONT face="Times New Roman"></FONT>&nbsp;</DIV></BODY></HTML>

--Boundary_(ID_6UjPZ2JPAeiZM7KqNsYAGQ)--

From albrecht.schwarz@alcatel-lucent.com  Tue Nov 29 03:32:24 2011
Return-Path: <albrecht.schwarz@alcatel-lucent.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33FF921F8B3A; Tue, 29 Nov 2011 03:32:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0cuhG3Wr0M6y; Tue, 29 Nov 2011 03:32:23 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id 4AC1E21F8B30; Tue, 29 Nov 2011 03:32:22 -0800 (PST)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pATBWIte002676 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 29 Nov 2011 12:32:21 +0100
Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.52]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Tue, 29 Nov 2011 12:31:56 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: "avt@ietf.org" <avt@ietf.org>
Date: Tue, 29 Nov 2011 12:32:46 +0100
Thread-Topic: Types of monitoring architectures; RE: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-08.txt
Thread-Index: AcyubGYHPa88O0vWQYK5qbTx0sZ/ngAF1k3A
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com>
In-Reply-To: <20111129075613.12419.4377.idtracker@ietfa.amsl.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Cc: "megaco@ietf.org" <megaco@ietf.org>
Subject: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 29 Nov 2011 11:32:24 -0000

Dear All,

there are different types of monitoring architectures, particularily from p=
erspective of QoE related performance parameters.=20
Let's recall QoE (e.g., ITU-T P.10 Amendment 2):

Quality of Experience (QoE):=20
	The overall acceptability of an application or service, as perceived subje=
ctively by the end-user. =20
	NOTE 1 - Quality of experience includes the complete end-to-end system eff=
ects (client, terminal, network, services infrastructure, etc.).=20
	NOTE 2 - Overall acceptability may be influenced by user expectations and =
context.=20
=20
Important for MONARCH:
1st ... perceived by end-user
2nd QoE includes the complete end-to-end sytem effects ...

That said, present RTP monitoring architecture in MONARCH according clause =
3 is not specific on the type of monitoring architecture. For instance, Fig=
. 1, it is possibly supposed that the "RTP Sender" and "RTP Receiver" entit=
ies are equal to a terminal/user equipment (UE). This would be an end-to-en=
d IP network scenario.

However, the "RTP Sender" and "RTP Receiver" entities may be also located a=
t the edge of an IP network, e.g. in a gateway for IP-to-non-IP interworkin=
g, i.e. an UE located in the non-IP network part.=20
Note: such scenarios are considered by MEGACO gateways (I've Cc'd megaco li=
st).

An RTP Sender/Receiver located NOT in the UE would question the value of RT=
P/RTCP QoE related performance measurements (because the UE is located outs=
ide the RTP domain).=20

Conclusions:
- the set of meaningful performance metrics may be dependent on the locatio=
n of the RTP Sender/Receiver, e.g. whether in a UE, gateway, ...
- don't see any impact on transport level metrics
- ... but the set of meaningful application level metrics

Proposal for MONARCH:
#1: insert sub-clause title "3.1 End-to-end IP network architecture" below =
clause 3

#2: add a sub-clause 3.2 at the end of clause 3, sth like

"3.2 RTP Sender/Receiver entities located in network nodes
The location of the RTP Sender/Receiver entity may impact the set of meanin=
gful metrics.
For instance: application level metrics for QoE related performance metrics=
 are questionable (or doesn't really make sense at all) when measured in a =
network node (terminating the RTP) instead of the user equipment."

Something like this would help to avoid confusion.
I even believe that a QoE measurement in a network node would violate the Q=
oE definition. Would be rather something like QoE* ("remote QoE"):-(

Such information would improve the MONARCH doc in my opinion.
Sorry for that late comment.
Any views?

Regards,
Albrecht

=20


> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On=20
> Behalf Of internet-drafts@ietf.org
> Sent: Dienstag, 29. November 2011 08:56
> To: i-d-announce@ietf.org
> Cc: avt@ietf.org
> Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-08.txt
>=20
>=20
> A New Internet-Draft is available from the on-line=20
> Internet-Drafts directories. This draft is a work item of the=20
> Audio/Video Transport Core Maintenance Working Group of the IETF.
>=20
> 	Title           : Monitoring Architectures for RTP
> 	Author(s)       : Qin Wu
>                           Geoff Hunt
>                           Philip Arden
> 	Filename        : draft-ietf-avtcore-monarch-08.txt
> 	Pages           : 25
> 	Date            : 2011-11-28
>=20
>    This memo proposes an architecture for extending RTCP with=20
> a new RTCP
>    XR (RFC3611) block type to report new metrics regarding media
>    transmission or reception quality, following RTCP guideline
>    established in RFC5968.  This memo suggests that a new block should
>    contain a single metric or a small number of metrics relevant to a
>    single parameter of interest or concern, rather than containing a
>    number of metrics which attempt to provide full coverage=20
> of all those
>    parameters of concern to a specific application.  Applications may
>    then "mix and match" to create a set of blocks which=20
> covers their set
>    of concerns.  Where possible, a specific block should be=20
> designed to
>    be re-usable across more than one application, for example, for all
>    of voice, streaming audio and video.
>=20
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
>=20
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
> =

From kevin.gross@avanw.com  Tue Nov 29 14:07:21 2011
Return-Path: <kevin.gross@avanw.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5701311E8121 for <avt@ietfa.amsl.com>; Tue, 29 Nov 2011 14:07:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.128
X-Spam-Level: 
X-Spam-Status: No, score=0.128 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kvBsqrDo1S9j for <avt@ietfa.amsl.com>; Tue, 29 Nov 2011 14:07:17 -0800 (PST)
Received: from oproxy5-pub.bluehost.com (oproxy5.bluehost.com [IPv6:2605:dc00:100:2::a5]) by ietfa.amsl.com (Postfix) with SMTP id D776D11E8112 for <avt@ietf.org>; Tue, 29 Nov 2011 14:07:12 -0800 (PST)
Received: (qmail 9474 invoked by uid 0); 29 Nov 2011 22:07:12 -0000
Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by cpoproxy2.bluehost.com with SMTP; 29 Nov 2011 22:07:12 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default;  h=Content-Type:To:From:Subject:Message-ID:Date:References:In-Reply-To:MIME-Version; bh=BF2yXQdrQqBh3YBNdqMZHxp/nfAmyinoKVT8QfetzKY=;  b=Fx0IpWIFId0SjGc1c41zZzszQ8+nVlfNn9EhUlo5Mcg3XCZM7NT5vzTXiQpSUhXuzs/3Ipk2U6Do80SlukwoCa+JqpSMcG+oQT58x6KYZnwPWS9AzcdhII07hhuhgcaw;
Received: from mail-fx0-f44.google.com ([209.85.161.44]) by host291.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from <kevin.gross@avanw.com>) id 1RVVpY-0006hK-5D; Tue, 29 Nov 2011 15:07:12 -0700
Received: by faap14 with SMTP id p14so187145faa.31 for <multiple recipients>; Tue, 29 Nov 2011 14:07:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.204.154.151 with SMTP id o23mr51484464bkw.62.1322604430485; Tue, 29 Nov 2011 14:07:10 -0800 (PST)
Received: by 10.223.93.197 with HTTP; Tue, 29 Nov 2011 14:07:10 -0800 (PST)
In-Reply-To: <CALw1_Q1GygiRv=hz5dhTgEcvVzuj8-ft6swahh16ny3ha__jEQ@mail.gmail.com>
References: <4EAF4255.8010909@audinate.com> <CALw1_Q1GygiRv=hz5dhTgEcvVzuj8-ft6swahh16ny3ha__jEQ@mail.gmail.com>
Date: Tue, 29 Nov 2011 15:07:10 -0700
Message-ID: <CALw1_Q2XOmJNjjfgh1mOp-Q-_tvYf0dWoFA=ZWr0SQMeWZOezQ@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: Aidan Williams <aidan.williams@audinate.com>, avtext@ietf.org, avt@ietf.org
Content-Type: multipart/alternative; boundary=0015175d039441e9bc04b2e6d76a
X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 209.85.161.44 authed with kevin.gross@avanw.com}
Subject: Re: [AVTCORE] [avtext] draft-williams-avtext-avbsync updated
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 29 Nov 2011 22:07:21 -0000

--0015175d039441e9bc04b2e6d76a
Content-Type: text/plain; charset=ISO-8859-1

Aidan and I ended up at the same conference in San Diego last weekend and
found time to discuss clock domain identification. We believe it
is desirable to use the same clock identification scheme for IDMS and
Aidan's work. Here's a proposal I've fleshed out based on our discussion.

The "clocksource" parameter should be improved to allow optional
specification of clock identifiers. Clock identifiers are derived from an
EUI-48 or EUI-64 as specified by IEEE 1588 (IEEE 1588-2008 7.5.2.2.2, IEEE
1588-2002 D.2). The listed identifiers would be for the current grandmaster
and other high-quality clocks on the IEEE 1288 domain, members of a
grandmaster cluster (IEEE 1588-2008 17.3) or an alternate master (IEEE
1588-2008 17.4).

If no clock identifiers are supplied, implementations may assume that a
match of the supplied attributes (e.g. PTP, version and domain identifier)
specifies the same clock. If one or more clock identifiers are supplied,
these should be compared to the available clock identifiers for the
specified domain. If there is at least one match, there is assumed to be a
clock match.

We both believe a traceability indication should be included in the
"clocksource" attribute for IEEE 1588-2002, IEEE 1588-2008, IEEE 802.1AS
and NTP. Galileo and GPS are implied traceable and local is presumably
never traceable. Aidan argues that  you shouldn't have to second guess
a traceable clock and therefore, no domain or clock identifiers are
required for traceable clocks.

>
Kevin Gross



> On Sun, Nov 6, 2011 at 9:12 PM, Kevin Gross <kevin.gross@avanw.com> wrote:

>
> IDMS defines a "clocksource" SDP attribute to identify the clock
> domain. The following clock distribution methods are supported by IDMS:
> NTP, GPS, Galileo, IEEE 1588-2002, IEEE 1588-2008 and IEEE 802.1AS. When
> IEEE 1588-2002 or IEEE 1588-2008 are used, a domain identifier is also
> specified. The IEEE 802.1AS PTP profile allows use of the default domain
> (0) only. You are proposing using the EUI-64 of the grandmaster instead. I
> also considered this possibility for IDMS but was confounded by the
> following scenario...
>
> For fault tolerance, mission-critical media systems are configured with at
> least two potential grandmasters all receiving time from a common reference
> (e.g. house sync reference, GPS). Upon failure of the primary grandmaster,
> another takes over and, although nothing has functionally changed about the
> clock domain, the EUI-64 of the grandmaster in the network does change.
> Until updated SDP advertisements reflecting the new grandmaster are
> received, senders and receivers will believe they are operating on
> different time domains and streams will presumably be interrupted.
>
> It would be very useful to have a unique identifier for a clock domain. My
> conclusion after considering the above scenario was that the grandmaster ID
> was not that identifier and clock distribution protocol, protocol version
> and domain identifier is currently the best identifier we have. I think
> there is definitely room for improvement in this. It does not strike me as
> an easy problem, however.
>
> I like your idea of using a traceability indicator to help determine clock
> compatibility. I am concerned however that while traceable clocks can be
> assumed to be frequency synchronized (syntonized) I am not aware of any way
> to gauge the accuracy of their phase synchronization. Nevertheless, adding
> a traceability indicator to the SDP clock attribute would seem to be a
> useful improvement.
>
>

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

Aidan and I ended up at the same conference in San Diego last weekend and f=
ound time to discuss clock domain identification. We=A0believe=A0it is=A0de=
sirable=A0to use the same clock identification scheme for IDMS and Aidan&#3=
9;s work. Here&#39;s a proposal I&#39;ve fleshed out based on our discussio=
n.<br>





<br><div>The &quot;clocksource&quot; parameter should be improved to allow =
optional specification of clock identifiers. Clock identifiers are derived =
from an EUI-48 or EUI-64 as specified by IEEE 1588 (IEEE 1588-2008 7.5.2.2.=
2, IEEE 1588-2002 D.2). The listed identifiers would be for the current gra=
ndmaster and other high-quality clocks on the IEEE 1288 domain, members of =
a grandmaster cluster (IEEE 1588-2008 17.3) or an alternate master (IEEE 15=
88-2008 17.4).</div>




<div><br></div><div>If no clock identifiers are supplied, implementations m=
ay assume that a match of the supplied attributes (e.g. PTP, version and do=
main identifier) specifies the same clock. If one or more clock identifiers=
 are supplied, these should be compared to the available clock identifiers =
for the specified domain. If there is at least one match, there is assumed =
to be a clock match.</div>





<div><br></div><div><div>We both=A0believe=A0a traceability indication shou=
ld be included in the &quot;clocksource&quot; attribute for IEEE 1588-2002,=
 IEEE 1588-2008, IEEE 802.1AS and NTP. Galileo=A0and GPS are implied=A0trac=
eable=A0and local is presumably never traceable.=A0Aidan argues that =A0you=
 shouldn&#39;t have to second guess a=A0traceable=A0clock and=A0therefore, =
no domain or clock identifiers are required for traceable clocks.</div>



</div><div>

<blockquote class=3D"gmail_quote" style=3D"margin-top:0px;margin-right:0px;=
margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color=
:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
</blockquote></div><div><br></div><div>Kevin Gross</div><div><br></div><div=
>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin-top:0px;margin-=
right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-=
left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">





</blockquote><div class=3D"gmail_quote">On Sun, Nov 6, 2011 at 9:12 PM, Kev=
in Gross <span dir=3D"ltr">&lt;<a href=3D"mailto:kevin.gross@avanw.com" tar=
get=3D"_blank">kevin.gross@avanw.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div><br></div><div>IDMS defines a &quot;clo=
cksource&quot; SDP attribute to identify the clock domain.=A0The following =
clock distribution methods are supported by IDMS: NTP, GPS,=A0Galileo, IEEE=
 1588-2002, IEEE 1588-2008 and IEEE 802.1AS.=A0When IEEE 1588-2002 or IEEE =
1588-2008 are used, a domain identifier is also specified. The IEEE 802.1AS=
 PTP profile allows use of the default domain (0) only.=A0You are proposing=
 using the EUI-64 of the grandmaster=A0instead. I also considered this poss=
ibility for IDMS but was confounded by the following scenario...</div>








<div><br></div><div>For fault tolerance, mission-critical media systems are=
 configured with at least two potential grandmasters all receiving time fro=
m a common reference (e.g. house sync reference, GPS). Upon failure of the =
primary grandmaster, another takes over and, although nothing has functiona=
lly changed about the clock domain, the EUI-64 of the grandmaster in the ne=
twork does change. Until updated SDP advertisements reflecting the new gran=
dmaster are received, senders and receivers will believe they are operating=
 on different time domains and streams will presumably be interrupted.</div=
>








<div><br></div><div>It would be very useful to have a unique identifier for=
 a clock domain. My conclusion after considering the above scenario was tha=
t the grandmaster ID was not that identifier and clock distribution protoco=
l, protocol version and domain identifier is currently the best identifier =
we have. I think there is definitely room for improvement in this. It does =
not strike me as an easy problem, however.</div>








<div><br></div></blockquote><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>I like your=
 idea of using a traceability=A0indicator to help determine clock compatibi=
lity. I am concerned however that while traceable clocks can be assumed to =
be frequency synchronized (syntonized) I am not aware of any way to gauge t=
he accuracy of their phase synchronization. Nevertheless, adding a traceabi=
lity indicator to the SDP clock attribute would seem to be a useful improve=
ment.</div>








<div><br></div></blockquote><div>=A0</div></div>

--0015175d039441e9bc04b2e6d76a--

From bill.wu@huawei.com  Tue Nov 29 19:51:50 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D783B21F86A5; Tue, 29 Nov 2011 19:51:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.182
X-Spam-Level: 
X-Spam-Status: No, score=-6.182 tagged_above=-999 required=5 tests=[AWL=0.417,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PpVfRKvVj791; Tue, 29 Nov 2011 19:51:49 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id B0EFC21F86A4; Tue, 29 Nov 2011 19:51:48 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVG003AHG0VSB@szxga03-in.huawei.com>; Wed, 30 Nov 2011 11:50:55 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVG0017WG0UHZ@szxga03-in.huawei.com>; Wed, 30 Nov 2011 11:50:54 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFI56187; Wed, 30 Nov 2011 11:50:54 +0800
Received: from SZXEML401-HUB.china.huawei.com (10.82.67.31) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 30 Nov 2011 11:50:48 +0800
Received: from w53375q (10.138.41.130) by szxeml401-hub.china.huawei.com (10.82.67.31) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 30 Nov 2011 11:50:42 +0800
Date: Wed, 30 Nov 2011 11:50:41 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>, avt@ietf.org
Message-id: <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
Cc: megaco@ietf.org
Subject: Re: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 30 Nov 2011 03:51:50 -0000

Hi,
----- Original Message ----- 
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: <avt@ietf.org>
Cc: <megaco@ietf.org>
Sent: Tuesday, November 29, 2011 7:32 PM
Subject: [AVTCORE] Types of monitoring architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt


> Dear All,
> 
> there are different types of monitoring architectures, particularily from perspective of QoE related performance parameters. 
> Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> 
> Quality of Experience (QoE): 
> The overall acceptability of an application or service, as perceived subjectively by the end-user.  
> NOTE 1 - Quality of experience includes the complete end-to-end system effects (client, terminal, network, services infrastructure, etc.). 
> NOTE 2 - Overall acceptability may be influenced by user expectations and context. 
> 
> Important for MONARCH:
> 1st ... perceived by end-user
> 2nd QoE includes the complete end-to-end sytem effects ...
> 
> That said, present RTP monitoring architecture in MONARCH according clause 3 is not specific on the type of monitoring architecture. For instance, Fig. 1, it is possibly supposed that the "RTP Sender" and "RTP Receiver" entities are equal to a terminal/user equipment (UE). This would be an end-to-end IP network scenario.
> 
> However, the "RTP Sender" and "RTP Receiver" entities may be also located at the edge of an IP network, e.g. in a gateway for IP-to-non-IP interworking, i.e. an UE located in the non-IP network part. 
> Note: such scenarios are considered by MEGACO gateways (I've Cc'd megaco list).
> 
> An RTP Sender/Receiver located NOT in the UE would question the value of RTP/RTCP QoE related performance measurements (because the UE is located outside the RTP domain). 
> 
> Conclusions:
> - the set of meaningful performance metrics may be dependent on the location of the RTP Sender/Receiver, e.g. whether in a UE, gateway, ...
> - don't see any impact on transport level metrics
> - ... but the set of meaningful application level metrics
> 
> Proposal for MONARCH:
> #1: insert sub-clause title "3.1 End-to-end IP network architecture" below clause 3
> 
> #2: add a sub-clause 3.2 at the end of clause 3, sth like
> 
> "3.2 RTP Sender/Receiver entities located in network nodes
> The location of the RTP Sender/Receiver entity may impact the set of meaningful metrics.
> For instance: application level metrics for QoE related performance metrics are questionable (or doesn't really make sense at all) when measured in a network node (terminating the RTP) instead of the user equipment."
> 
> Something like this would help to avoid confusion.
> I even believe that a QoE measurement in a network node would violate the QoE definition. Would be rather something like QoE* ("remote QoE"):-(
> 
> Such information would improve the MONARCH doc in my opinion.
> Sorry for that late comment.
> Any views?

[Qin]: 
Albrrecht, if you follow ealry list discussion on draft-hunt-avt-monarch-01, you will see the rough consensus to position this document was 
this daft should focus on guidelines for defining reporting blocks. That is to say the main purpose of MONARCH draft is how to 
provide guidelines for the development of new RTCP XR block types in XRBlock working group.

Therefore how and where to collect the metric from RTP endpoint is not scope of this document, in my opinion. since you may have many ways to do this and different vendors have their different appoaches. It will be better to leave this beyond the scope. But you are right, it will be more reasonable to measure QoE related performance metric at the RTP receiver.
 
Another point is it is not clear to me how RTP monitoring has to do with architectureend to end IP network architecture .
this draft mostly focus on discussing RTP level stuff. Therefore I am quite doubt that we should describe anything in this document like how
RTP entties is mapped into network entities/nodes at the IP layer.

But as the author of this document, I am interested and open to other opinions.:-)

> Regards,
> Albrecht
> 
> 
> 
> 
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On 
>> Behalf Of internet-drafts@ietf.org
>> Sent: Dienstag, 29. November 2011 08:56
>> To: i-d-announce@ietf.org
>> Cc: avt@ietf.org
>> Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-08.txt
>> 
>> 
>> A New Internet-Draft is available from the on-line 
>> Internet-Drafts directories. This draft is a work item of the 
>> Audio/Video Transport Core Maintenance Working Group of the IETF.
>> 
>> Title           : Monitoring Architectures for RTP
>> Author(s)       : Qin Wu
>>                           Geoff Hunt
>>                           Philip Arden
>> Filename        : draft-ietf-avtcore-monarch-08.txt
>> Pages           : 25
>> Date            : 2011-11-28
>> 
>>    This memo proposes an architecture for extending RTCP with 
>> a new RTCP
>>    XR (RFC3611) block type to report new metrics regarding media
>>    transmission or reception quality, following RTCP guideline
>>    established in RFC5968.  This memo suggests that a new block should
>>    contain a single metric or a small number of metrics relevant to a
>>    single parameter of interest or concern, rather than containing a
>>    number of metrics which attempt to provide full coverage 
>> of all those
>>    parameters of concern to a specific application.  Applications may
>>    then "mix and match" to create a set of blocks which 
>> covers their set
>>    of concerns.  Where possible, a specific block should be 
>> designed to
>>    be re-usable across more than one application, for example, for all
>>    of voice, streaming audio and video.
>> 
>> 
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
>> 
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>> 
>> This Internet-Draft can be retrieved at:
>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
>> 
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt

From cris.pascual.gonzalez@gmail.com  Tue Nov 29 11:15:39 2011
Return-Path: <cris.pascual.gonzalez@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 316D521F8AFF for <avt@ietfa.amsl.com>; Tue, 29 Nov 2011 11:15:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.013
X-Spam-Level: 
X-Spam-Status: No, score=-4.013 tagged_above=-999 required=5 tests=[AWL=0.586,  BAYES_00=-2.599, GB_I_INVITATION=-2]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HqNxRa7UEROT for <avt@ietfa.amsl.com>; Tue, 29 Nov 2011 11:15:39 -0800 (PST)
Received: from marfik.cc.upv.es (marfik.cc.upv.es [158.42.249.9]) by ietfa.amsl.com (Postfix) with ESMTP id 6770921F8B16 for <avt@ietf.org>; Tue, 29 Nov 2011 11:15:35 -0800 (PST)
Received: from smtpx.upv.es (smtpxv.cc.upv.es [158.42.249.46]) by marfik.cc.upv.es (8.13.6/8.13.6) with ESMTP id pATJFYC9022246 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <avt@ietf.org>; Tue, 29 Nov 2011 20:15:34 +0100
Received: from smtp.upv.es (celaeno.cc.upv.es [158.42.249.55]) by smtpx.upv.es (8.14.3/8.14.3) with ESMTP id pATJFj9m021673 for <avt@ietf.org>; Tue, 29 Nov 2011 20:15:45 +0100
Received: from JLLORET (vpn245-22.vpns.upv.es [158.42.245.22]) by smtp.upv.es (8.13.6/8.13.6) with SMTP id pATJFXGu012921 for <avt@ietf.org>; Tue, 29 Nov 2011 20:15:33 +0100
Date: Tue, 29 Nov 2011 20:15:33 +0100
Message-Id: <201111291915.pATJFXGu012921@smtp.upv.es>
From: Cristina Pascual<cris.pascual.gonzalez@gmail.com>
To: avt@ietf.org
CC: 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailman-Approved-At: Wed, 30 Nov 2011 08:28:42 -0800
Subject: [AVTCORE] Deadline extension, December 16: MMEDIA 2012 || April 29 - May 4, 2012 - Chamonix / Mont Blanc, France
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 29 Nov 2011 19:15:39 -0000

INVITATION:

=================
Please, consider to contribute to and/or forward to the appropriate groups the following opportunity to submit and publish original scientific results to MMEDIA 2012.
The submission deadline is extended to December 16, 2011.
In addition, authors of selected papers will be invited to submit extended article versions to one of the IARIA Journals: http://www.iariajournals.org
=================


============== MMEDIA 2012 | Call for Papers ===============

CALL FOR PAPERS, TUTORIALS, PANELS

MMEDIA 2012: The Fourth International Conferences on Advances in Multimedia
April 29 - May 4, 2012 - Chamonix / Mont Blanc, France

General page: http://www.iaria.org/conferences2012/MMEDIA12.html

Call for Papers: http://www.iaria.org/conferences2012/CfPMMEDIA12.html

- regular papers
- short papers (work in progress)
- posters

- ideas

Submission page: hhttp://www.iaria.org/conferences2012/SubmitMMEDIA12.html

Submission deadline: December 16, 2011

Sponsored by IARIA, www.iaria.org

Extended versions of selected papers will be published in IARIA Journals: http://www.iariajournals.org

Please note the Poster and Work in Progress options.

The topics suggested by the conference can be discussed in term of concepts, state of the art, research, standards, implementations, running experiments, applications, and industrial case studies. Authors are invited to submit complete unpublished papers, which are not under review in any other conference or journal in the following, but not limited to, topic areas.

All tracks are open to both research and industry contributions, in terms of Regular papers, Posters, Work in progress, Technical/marketing/business presentations, Demos, Tutorials, and Panels.

Before submission, please check and conform with the Editorial rules: http://www.iaria.org/editorialrules.html

MMEDIA 2012 Topics (topics and submission details: see CfP on the site)

Fundamentals in multimedia
Multimedia systems, architecture, and applications; New multimedia platforms; Multimedia architectural specification languages; Theoretical aspects and algorithms for multimedia; Multimedia content delivery networks; Network support for multimedia data; Multimedia data storage; Multimedia meta-modeling techniques and operating systems; Multimedia signal coding and processing (audio, video, image); Multimedia applications (telepresence, triple-play, quadruple-play, …); Multimedia tools (authoring, analyzing, editing, browsing, …); Computational multimedia intelligence (fuzzy logic, neural networks, genetic algorithms, …); Intelligent agents for multimedia content creation, distribution, and analysis; Multimedia networking; Wired and wireless multimedia systems; Distributed multimedia systems; Multisensor data integration and fusion; Multimedia and P2P; Multimedia standards

Multimedia content and modeling
Interfaces for multimedia creation; Multimedia streaming and services; Image modeling and editing; Audio modeling and transformation; Video modeling and transformation; Image recognition; Multimedia databases; Multimedia coding and encryption; Multimedia modeling for learning content; Multimedia description languages; Image clustering; Media fusion for communication and presentation

Self-organizing multimedia architectures
Self-organization in multimedia systems; Self-organization in multimedia communities; Self-organized multimedia networks; Multimedia content distribution and consumption; Adaptive multimedia interfaces; Multimedia retrieval

Multimedia content-based retrieval and analysis
Multimodal data analysis; Multimedia databases; Semi-automatic and automatic methods for multimedia annotation; Image/video/audio databases; Content-based image retrieval; Semantics-based search and integration of multimedia and digital content; Multimedia data modeling, indexing, and mining; Statistical modeling of multimedia data; Multimedia extraction and annotation; Content search/browsing/retrieval; Internet imaging and multimedia; Multimodal content analysis; Multimedia abstraction and summarization; Semantic analysis of multimedia data; Media assimilation and fusion

Perception and cognition for multimedia users
Quality of experience; Relevance feedback; Human-computer interaction; Multimodal interaction; Multimodal user interfaces; Mobile user-centered interfaces; Peer-to-peer multimedia systems and streaming; Pervasive and interactive multimedia systems (digital TV, mobile systems, gaming,…); Multimedia in personal, sensor and ad-hoc networks; Visualization and virtual reality; Intelligent browsing and visualization; Perception and cognition; Perception and modeling of the environment; Multimedia collaboration; Social networking

Multimedia ontology
Multimedia semantics; Emergent semantics; Media ontology learning; Ontology for media web mining; Multimedia ontologies; Multimedia information management; Approaches using metadata standards; Conceptual clustering; Modeling and recognition of visual objects and actions

Mobile and ubiquitous multimedia
Architectures, protocols, and algorithms for multimedia mobility; Middleware and distributed computing support for mobile and ubiquitous multimedia; Mobile and ubiquitous multimedia in intelligent transportation systems; Enabling platforms for mobile multimedia; Roaming and limited bandwidth; Intermittent connectivity; Streaming mobile multimedia; Mobile multimedia software architectures; Mobile multimedia applications and services; Communication and cooperation via mobile multimedia; Business models for mobile multimedia; Provisioning of mobile multimedia services; Context-aware mobile and ubiquitous multimedia; Mobile computer graphics, games and entertainment; Mobile and ubiquitous multimedia in ad hoc networks; Personalization, privacy and security in mobile multimedia; Social and regulatory aspects of mobile multimedia; Multimedia in the Extended Home; Ubiquitous/Seamless content sharing

Multimedia services
Reliability, availability, serviceability of multimedia services; Multimedia content distribution services; Real-time multimedia services; Audio-visual multimedia services; Multimedia signal processing and communications; Media representation and algorithms; Audio, image, video processing, coding and compression; Multimedia database, content delivery and transport; Multimedia service protocols; Mobility of multimedia services; Internet telephony and hypermedia technologies and systems; Media enabled eCommerce service; Case studies, field trials and evaluation of new multimedia services

Multimedia applications
Real-time interactive multimedia applications Adaptive and context-aware multimedia applications; Ambiance multimedia applications; Media applications on mobile devices; Multi-modal interaction; Virtual environments; Personalization; Collaboration, contextual metadata, collaborative tagging; Web applications; Multimedia authoring; Multimedia-enabled new applications (eLearning, entertainment,…..); Cooperative networks and applications; Mobile multimedia applications & services; Semantic metadata for mobile applications; Semantics enabled multimedia applications; Semantics enabled networks and middleware for multimedia applications; Wireless ad-hoc and sensor networks/RFID applications Industrial use-cases and applications

Multimedia security and content protection
Multimedia security (watermark, encryption,… ); Mobile multimedia systems and services; Security, privacy, and cryptographic protocols; Network security issues and protocols; Key management and authentication; Authentication and access control; Intrusion detection and prevention; Content protection and digital rights management; Trusted computing; Information hiding; Protection of user-generated content

Multimedia control and management
Wireless and mobile multimedia network management; Multimedia measurement, control, and management; Content management and delivery; IP multimedia system operations and management; Managing the quality of experience and quality of service; Measuring the quality of performance in multimedia systems; Mobile multimedia network traffic engineering and optimization; Monitoring and managing mobile multimedia; Resource reservation for multimedia services; Multicast and broadcast multimedia service management; Management of service oriented architectures; Pricing, accounting and billing for multimedia services


Committee: http://www.iaria.org/conferences2012/ComMMEDIA12.html
====================

From albrecht.schwarz@alcatel-lucent.com  Wed Nov 30 09:23:35 2011
Return-Path: <albrecht.schwarz@alcatel-lucent.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3268921F8C0F; Wed, 30 Nov 2011 09:23:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.874
X-Spam-Level: 
X-Spam-Status: No, score=-5.874 tagged_above=-999 required=5 tests=[AWL=0.375,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QsLxkmovJtox; Wed, 30 Nov 2011 09:23:34 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id F189A21F8C06; Wed, 30 Nov 2011 09:23:33 -0800 (PST)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id pAUHNPi4007339 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 30 Nov 2011 18:23:25 +0100
Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.52]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Wed, 30 Nov 2011 18:23:25 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: Qin Wu <bill.wu@huawei.com>, "avt@ietf.org" <avt@ietf.org>
Date: Wed, 30 Nov 2011 18:24:16 +0100
Thread-Topic: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
Thread-Index: AcyvE2HylSLOa+J4RfiROAbrd6oriAAbsNGQ
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com>
In-Reply-To: <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Cc: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 30 Nov 2011 17:23:35 -0000

My replies below inline,
Albrecht=20

> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com]=20
> Sent: Mittwoch, 30. November 2011 04:51
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE:=20
> I-D Action: draft-ietf-avtcore-monarch-08.txt
>=20
> Hi,
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)"=20
> <albrecht.schwarz@alcatel-lucent.com>
> To: <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Tuesday, November 29, 2011 7:32 PM
> Subject: [AVTCORE] Types of monitoring architectures; RE: I-D=20
> Action: draft-ietf-avtcore-monarch-08.txt
>=20
>=20
> > Dear All,
> >=20
> > there are different types of monitoring architectures,=20
> particularily from perspective of QoE related performance parameters.=20
> > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> >=20
> > Quality of Experience (QoE):=20
> > The overall acceptability of an application or service, as=20
> perceived subjectively by the end-user. =20
> > NOTE 1 - Quality of experience includes the complete=20
> end-to-end system effects (client, terminal, network,=20
> services infrastructure, etc.).=20
> > NOTE 2 - Overall acceptability may be influenced by user=20
> expectations and context.=20
> >=20
> > Important for MONARCH:
> > 1st ... perceived by end-user
> > 2nd QoE includes the complete end-to-end sytem effects ...
> >=20
> > That said, present RTP monitoring architecture in MONARCH=20
> according clause 3 is not specific on the type of monitoring=20
> architecture. For instance, Fig. 1, it is possibly supposed=20
> that the "RTP Sender" and "RTP Receiver" entities are equal=20
> to a terminal/user equipment (UE). This would be an=20
> end-to-end IP network scenario.
> >=20
> > However, the "RTP Sender" and "RTP Receiver" entities may=20
> be also located at the edge of an IP network, e.g. in a=20
> gateway for IP-to-non-IP interworking, i.e. an UE located in=20
> the non-IP network part.=20
> > Note: such scenarios are considered by MEGACO gateways=20
> (I've Cc'd megaco list).
> >=20
> > An RTP Sender/Receiver located NOT in the UE would question=20
> the value of RTP/RTCP QoE related performance measurements=20
> (because the UE is located outside the RTP domain).=20
> >=20
> > Conclusions:
> > - the set of meaningful performance metrics may be=20
> dependent on the location of the RTP Sender/Receiver, e.g.=20
> whether in a UE, gateway, ...
> > - don't see any impact on transport level metrics
> > - ... but the set of meaningful application level metrics
> >=20
> > Proposal for MONARCH:
> > #1: insert sub-clause title "3.1 End-to-end IP network=20
> architecture" below clause 3
> >=20
> > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> >=20
> > "3.2 RTP Sender/Receiver entities located in network nodes
> > The location of the RTP Sender/Receiver entity may impact=20
> the set of meaningful metrics.
> > For instance: application level metrics for QoE related=20
> performance metrics are questionable (or doesn't really make=20
> sense at all) when measured in a network node (terminating=20
> the RTP) instead of the user equipment."
> >=20
> > Something like this would help to avoid confusion.
> > I even believe that a QoE measurement in a network node=20
> would violate the QoE definition. Would be rather something=20
> like QoE* ("remote QoE"):-(
> >=20
> > Such information would improve the MONARCH doc in my opinion.
> > Sorry for that late comment.
> > Any views?
>=20
> [Qin]:=20
> Albrrecht, if you follow ealry list discussion on=20
> draft-hunt-avt-monarch-01, you will see the rough consensus=20
> to position this document was=20
> this daft should focus on guidelines for defining reporting=20
> blocks. That is to say the main purpose of MONARCH draft is how to=20
> provide guidelines for the development of new RTCP XR block=20
> types in XRBlock working group.

[ABS] ... then the title "monitoring architectures" is misleading.
Proposal: keep title, revise scope section on focus

>=20
> Therefore how and where to collect the metric from RTP=20
> endpoint is not scope of this document, in my opinion. since=20
> you may have many ways to do this and different vendors have=20
> their different appoaches. It will be better to leave this=20
> beyond the scope. But you are right, it will be more=20
> reasonable to measure QoE related performance metric at the=20
> RTP receiver.

[ABS] I would disagree. At least your statement should be conditional, sth =
like=20
"QoE related performance metrics may be measured in a RTP receiver, IF the =
RTP receiver function is located in user equipment (e.g. IP terminal), beca=
use QoE performance metrics are tightly coupled to the point of view of a '=
user'.
... IF NOT, then ..."

> =20
> Another point is it is not clear to me how RTP monitoring has=20
> to do with architectureend to end IP network architecture .
> this draft mostly focus on discussing RTP level stuff.=20
> Therefore I am quite doubt that we should describe anything=20
> in this document like how
> RTP entties is mapped into network entities/nodes at the IP layer.

[ABS] I don't got any problems to talk about architectural framework for mo=
nitoring in this document. Such information is required and this is the onl=
y IETF AVT doc about it.
The solution to this issue is rather simple to me:
- split the MONARCH "monitoring architecture" in
	1) a functional monitoring architecture (let's call it 'FMA') and
	2) a physical monitoring architecture (... 'PMA').

- the present MONARCH doc would describe the FMA at the level of RTP entiti=
es (i.e., Fig. 1 entities, incl. all the RTP topology components according =
RFC 5117)

- there are many options of functional-to-physical mappings, i.e. how a FMA=
 would be mapped on a PMA
- the mapping is typically dependent on considered network architecture (li=
ke SIP, H.323, MGCP, IMS, wireless, etc networks)

- the present MONARCH doc would describe the FMA-to-PMA mapping IF all RTP =
receiver/sender entities would be located in physical IP terminals (UEs)
- etc


>=20
> But as the author of this document, I am interested and open=20
> to other opinions.:-)

[ABS] Like to add a further aspect: a "functional monitoring architecture" =
may be considered as a network overlay, something which adds additional cap=
abilities (here: measurement services, reporting services on top of basic R=
TP services).
Such an overlay concept is nothing new: e.g., the MultiService Forum did de=
fine a "Performance Measurement & Monitoring (PMM)" overlay network, or IET=
F RMON may be also considered as such.

>=20
> > Regards,
> > Albrecht
> >=20
> >=20
> >=20
> >=20
> >> -----Original Message-----
> >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On=20
> >> Behalf Of internet-drafts@ietf.org
> >> Sent: Dienstag, 29. November 2011 08:56
> >> To: i-d-announce@ietf.org
> >> Cc: avt@ietf.org
> >> Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-08.txt
> >>=20
> >>=20
> >> A New Internet-Draft is available from the on-line=20
> >> Internet-Drafts directories. This draft is a work item of the=20
> >> Audio/Video Transport Core Maintenance Working Group of the IETF.
> >>=20
> >> Title           : Monitoring Architectures for RTP
> >> Author(s)       : Qin Wu
> >>                           Geoff Hunt
> >>                           Philip Arden
> >> Filename        : draft-ietf-avtcore-monarch-08.txt
> >> Pages           : 25
> >> Date            : 2011-11-28
> >>=20
> >>    This memo proposes an architecture for extending RTCP with=20
> >> a new RTCP
> >>    XR (RFC3611) block type to report new metrics regarding media
> >>    transmission or reception quality, following RTCP guideline
> >>    established in RFC5968.  This memo suggests that a new=20
> block should
> >>    contain a single metric or a small number of metrics=20
> relevant to a
> >>    single parameter of interest or concern, rather than=20
> containing a
> >>    number of metrics which attempt to provide full coverage=20
> >> of all those
> >>    parameters of concern to a specific application. =20
> Applications may
> >>    then "mix and match" to create a set of blocks which=20
> >> covers their set
> >>    of concerns.  Where possible, a specific block should be=20
> >> designed to
> >>    be re-usable across more than one application, for=20
> example, for all
> >>    of voice, streaming audio and video.
> >>=20
> >>=20
> >> A URL for this Internet-Draft is:
> >>=20
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> >>=20
> >> Internet-Drafts are also available by anonymous FTP at:
> >> ftp://ftp.ietf.org/internet-drafts/
> >>=20
> >> This Internet-Draft can be retrieved at:
> >>=20
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> >>=20
> >> _______________________________________________
> >> Audio/Video Transport Core Maintenance
> >> avt@ietf.org
> >> https://www.ietf.org/mailman/listinfo/avt
> >>=20
> > _______________________________________________
> > Audio/Video Transport Core Maintenance
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
> =

From bill.wu@huawei.com  Wed Nov 30 17:42:54 2011
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FDC711E809D; Wed, 30 Nov 2011 17:42:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.091
X-Spam-Level: 
X-Spam-Status: No, score=-6.091 tagged_above=-999 required=5 tests=[AWL=-0.092, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J3aYhqlYIMLA; Wed, 30 Nov 2011 17:42:53 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id C58B411E8099; Wed, 30 Nov 2011 17:42:52 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVI00GIU4R8AB@szxga05-in.huawei.com>; Thu, 01 Dec 2011 09:42:44 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVI005MK4R6Z6@szxga05-in.huawei.com>; Thu, 01 Dec 2011 09:42:44 +0800 (CST)
Received: from szxeml208-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFL62318; Thu, 01 Dec 2011 09:42:10 +0800
Received: from SZXEML403-HUB.china.huawei.com (10.82.67.35) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 01 Dec 2011 09:42:05 +0800
Received: from w53375q (10.138.41.130) by szxeml403-hub.china.huawei.com (10.82.67.35) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 01 Dec 2011 09:42:01 +0800
Date: Thu, 01 Dec 2011 09:42:00 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>, avt@ietf.org
Message-id: <B527BAFA038842A8939A8C2D558074CD@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <20111129075613.12419.4377.idtracker@ietfa.amsl.com> <5F7BCCF5541B7444830A2288ABBEBC96216190051A@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <EAC481B4D8034C38AC54E1217F8D875D@china.huawei.com> <5F7BCCF5541B7444830A2288ABBEBC96216190077F@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
Cc: megaco@ietf.org
Subject: Re: [AVTCORE] Types of monitoring architectures; RE:  I-D Action: draft-ietf-avtcore-monarch-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 01 Dec 2011 01:42:54 -0000

Hi,
----- Original Message ----- 
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: "Qin Wu" <bill.wu@huawei.com>; <avt@ietf.org>
Cc: <megaco@ietf.org>
Sent: Thursday, December 01, 2011 1:24 AM
Subject: RE: [AVTCORE] Types of monitoring architectures; RE: I-D Action: draft-ietf-avtcore-monarch-08.txt


My replies below inline,
Albrecht 

> -----Original Message-----
> From: Qin Wu [mailto:bill.wu@huawei.com] 
> Sent: Mittwoch, 30. November 2011 04:51
> To: Schwarz, Albrecht (Albrecht); avt@ietf.org
> Cc: megaco@ietf.org
> Subject: Re: [AVTCORE] Types of monitoring architectures; RE: 
> I-D Action: draft-ietf-avtcore-monarch-08.txt
> 
> Hi,
> ----- Original Message -----
> From: "Schwarz, Albrecht (Albrecht)" 
> <albrecht.schwarz@alcatel-lucent.com>
> To: <avt@ietf.org>
> Cc: <megaco@ietf.org>
> Sent: Tuesday, November 29, 2011 7:32 PM
> Subject: [AVTCORE] Types of monitoring architectures; RE: I-D 
> Action: draft-ietf-avtcore-monarch-08.txt
> 
> 
> > Dear All,
> > 
> > there are different types of monitoring architectures, 
> particularily from perspective of QoE related performance parameters. 
> > Let's recall QoE (e.g., ITU-T P.10 Amendment 2):
> > 
> > Quality of Experience (QoE): 
> > The overall acceptability of an application or service, as 
> perceived subjectively by the end-user.  
> > NOTE 1 - Quality of experience includes the complete 
> end-to-end system effects (client, terminal, network, 
> services infrastructure, etc.). 
> > NOTE 2 - Overall acceptability may be influenced by user 
> expectations and context. 
> > 
> > Important for MONARCH:
> > 1st ... perceived by end-user
> > 2nd QoE includes the complete end-to-end sytem effects ...
> > 
> > That said, present RTP monitoring architecture in MONARCH 
> according clause 3 is not specific on the type of monitoring 
> architecture. For instance, Fig. 1, it is possibly supposed 
> that the "RTP Sender" and "RTP Receiver" entities are equal 
> to a terminal/user equipment (UE). This would be an 
> end-to-end IP network scenario.
> > 
> > However, the "RTP Sender" and "RTP Receiver" entities may 
> be also located at the edge of an IP network, e.g. in a 
> gateway for IP-to-non-IP interworking, i.e. an UE located in 
> the non-IP network part. 
> > Note: such scenarios are considered by MEGACO gateways 
> (I've Cc'd megaco list).
> > 
> > An RTP Sender/Receiver located NOT in the UE would question 
> the value of RTP/RTCP QoE related performance measurements 
> (because the UE is located outside the RTP domain). 
> > 
> > Conclusions:
> > - the set of meaningful performance metrics may be 
> dependent on the location of the RTP Sender/Receiver, e.g. 
> whether in a UE, gateway, ...
> > - don't see any impact on transport level metrics
> > - ... but the set of meaningful application level metrics
> > 
> > Proposal for MONARCH:
> > #1: insert sub-clause title "3.1 End-to-end IP network 
> architecture" below clause 3
> > 
> > #2: add a sub-clause 3.2 at the end of clause 3, sth like
> > 
> > "3.2 RTP Sender/Receiver entities located in network nodes
> > The location of the RTP Sender/Receiver entity may impact 
> the set of meaningful metrics.
> > For instance: application level metrics for QoE related 
> performance metrics are questionable (or doesn't really make 
> sense at all) when measured in a network node (terminating 
> the RTP) instead of the user equipment."
> > 
> > Something like this would help to avoid confusion.
> > I even believe that a QoE measurement in a network node 
> would violate the QoE definition. Would be rather something 
> like QoE* ("remote QoE"):-(
> > 
> > Such information would improve the MONARCH doc in my opinion.
> > Sorry for that late comment.
> > Any views?
> 
> [Qin]: 
> Albrrecht, if you follow ealry list discussion on 
> draft-hunt-avt-monarch-01, you will see the rough consensus 
> to position this document was 
> this daft should focus on guidelines for defining reporting 
> blocks. That is to say the main purpose of MONARCH draft is how to 
> provide guidelines for the development of new RTCP XR block 
> types in XRBlock working group.

[ABS] ... then the title "monitoring architectures" is misleading.
Proposal: keep title, revise scope section on focus

[Qin]: No, the title is *RTP* monitoring architecture, we can not expand scope into IP monitoring architecture.

> 
> Therefore how and where to collect the metric from RTP 
> endpoint is not scope of this document, in my opinion. since 
> you may have many ways to do this and different vendors have 
> their different appoaches. It will be better to leave this 
> beyond the scope. But you are right, it will be more 
> reasonable to measure QoE related performance metric at the 
> RTP receiver.

[ABS] I would disagree. At least your statement should be conditional, sth like 
"QoE related performance metrics may be measured in a RTP receiver, IF the RTP receiver function is located in user equipment (e.g. IP terminal), because QoE performance metrics are tightly coupled to the point of view of a 'user'.
... IF NOT, then ..."

[Qin]: I am not sure user equipment or IP terminal is the right term from RTP perspective.

Also if you read P.NAMS, P.NAMS model for calculating QoE related metric can be placed either at the network or at the client.
So I disagree with what you said.

Also as I said, how and where to collect the metric from RTP 
 endpoint is not scope of this document. It depends on the model you are choosing, e.g., four operation modes specified in P.NAMS.
Apparently this should not be specified again in RTP monitoring architecture document.

>  
> Another point is it is not clear to me how RTP monitoring has 
> to do with architectureend to end IP network architecture .
> this draft mostly focus on discussing RTP level stuff. 
> Therefore I am quite doubt that we should describe anything 
> in this document like how
> RTP entties is mapped into network entities/nodes at the IP layer.

[ABS] I don't got any problems to talk about architectural framework for monitoring in this document. Such information is required and this is the only IETF AVT doc about it.
The solution to this issue is rather simple to me:
- split the MONARCH "monitoring architecture" in
1) a functional monitoring architecture (let's call it 'FMA') and
2) a physical monitoring architecture (... 'PMA').

- the present MONARCH doc would describe the FMA at the level of RTP entities (i.e., Fig. 1 entities, incl. all the RTP topology components according RFC 5117)

- there are many options of functional-to-physical mappings, i.e. how a FMA would be mapped on a PMA
- the mapping is typically dependent on considered network architecture (like SIP, H.323, MGCP, IMS, wireless, etc networks)

- the present MONARCH doc would describe the FMA-to-PMA mapping IF all RTP receiver/sender entities would be located in physical IP terminals (UEs)
- etc

[Qin]: I can understand your point, but you can not do that. Since this document is only focus on *RTP* monitoring architecture, that is what it said in AVTCore milestone:
"

Goals and Milestones:

  Feb 2011 - Submit Monitoring Architecture for RTP for Informational

"
Also if you really don't see how to map FMA to PMA, you may look at the P.NAMS models specifed in ITU-T P.NAMS. 
As for how to use RTP monitoring architecture or RTP XR Report in the IMS network architecture, you may look at:
http://tools.ietf.org/html/rfc6035
ITU-T H.248.48.
But I haven't check the current status of H.248.48.

> 
> But as the author of this document, I am interested and open 
> to other opinions.:-)

[ABS] Like to add a further aspect: a "functional monitoring architecture" may be considered as a network overlay, something which adds additional capabilities (here: measurement services, reporting services on top of basic RTP services).
Such an overlay concept is nothing new: e.g., the MultiService Forum did define a "Performance Measurement & Monitoring (PMM)" overlay network, or IETF RMON may be also considered as such.

> 
> > Regards,
> > Albrecht
> > 
> > 
> > 
> > 
> >> -----Original Message-----
> >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On 
> >> Behalf Of internet-drafts@ietf.org
> >> Sent: Dienstag, 29. November 2011 08:56
> >> To: i-d-announce@ietf.org
> >> Cc: avt@ietf.org
> >> Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-08.txt
> >> 
> >> 
> >> A New Internet-Draft is available from the on-line 
> >> Internet-Drafts directories. This draft is a work item of the 
> >> Audio/Video Transport Core Maintenance Working Group of the IETF.
> >> 
> >> Title           : Monitoring Architectures for RTP
> >> Author(s)       : Qin Wu
> >>                           Geoff Hunt
> >>                           Philip Arden
> >> Filename        : draft-ietf-avtcore-monarch-08.txt
> >> Pages           : 25
> >> Date            : 2011-11-28
> >> 
> >>    This memo proposes an architecture for extending RTCP with 
> >> a new RTCP
> >>    XR (RFC3611) block type to report new metrics regarding media
> >>    transmission or reception quality, following RTCP guideline
> >>    established in RFC5968.  This memo suggests that a new 
> block should
> >>    contain a single metric or a small number of metrics 
> relevant to a
> >>    single parameter of interest or concern, rather than 
> containing a
> >>    number of metrics which attempt to provide full coverage 
> >> of all those
> >>    parameters of concern to a specific application.  
> Applications may
> >>    then "mix and match" to create a set of blocks which 
> >> covers their set
> >>    of concerns.  Where possible, a specific block should be 
> >> designed to
> >>    be re-usable across more than one application, for 
> example, for all
> >>    of voice, streaming audio and video.
> >> 
> >> 
> >> A URL for this Internet-Draft is:
> >> 
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> >> 
> >> Internet-Drafts are also available by anonymous FTP at:
> >> ftp://ftp.ietf.org/internet-drafts/
> >> 
> >> This Internet-Draft can be retrieved at:
> >> 
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-08.txt
> >> 
> >> _______________________________________________
> >> Audio/Video Transport Core Maintenance
> >> avt@ietf.org
> >> https://www.ietf.org/mailman/listinfo/avt
> >> 
> > _______________________________________________
> > Audio/Video Transport Core Maintenance
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
>
