
From Internet-Drafts@ietf.org  Fri Mar  4 00:45:02 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8CF383A6972; Fri,  4 Mar 2011 00:45:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z1T2V3TOeffV; Fri,  4 Mar 2011 00:45:01 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7E3843A6968; Fri,  4 Mar 2011 00:45:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110304084501.2917.19313.idtracker@localhost>
Date: Fri, 04 Mar 2011 00:45:01 -0800
Cc: avt@ietf.org
Subject: [AVTCORE] I-D Action:draft-ietf-avt-app-rtp-keepalive-10.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2011 08:45:02 -0000

--NextPart

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


	Title           : Application Mechanism for keeping alive the Network Address Translator (NAT) mappings associated to RTP/RTCP flows.
	Author(s)       : X. Marjou, A. Sollaud
	Filename        : draft-ietf-avt-app-rtp-keepalive-10.txt
	Pages           : 11
	Date            : 2011-03-04

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

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

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

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

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

Content-Type: text/plain
Content-ID: <2011-03-04003252.I-D@ietf.org>


--NextPart--

From sunseawq@huawei.com  Fri Mar  4 01:34:18 2011
Return-Path: <sunseawq@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1489E3A68B3 for <avt@core3.amsl.com>; Fri,  4 Mar 2011 01:34:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.504
X-Spam-Level: 
X-Spam-Status: No, score=-3.504 tagged_above=-999 required=5 tests=[AWL=0.991,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nhCbUAnbd6A7 for <avt@core3.amsl.com>; Fri,  4 Mar 2011 01:34:16 -0800 (PST)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 2EEEF3A6889 for <avt@ietf.org>; Fri,  4 Mar 2011 01:34:16 -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 <0LHJ00MUA175QP@szxga04-in.huawei.com> for avt@ietf.org; Fri, 04 Mar 2011 17:33:05 +0800 (CST)
Received: from 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 <0LHJ00EIO175QG@szxga04-in.huawei.com> for avt@ietf.org; Fri, 04 Mar 2011 17:33:05 +0800 (CST)
Received: from w53375 ([10.138.41.48]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LHJ00HWH17592@szxml04-in.huawei.com> for avt@ietf.org; Fri, 04 Mar 2011 17:33:05 +0800 (CST)
Date: Fri, 04 Mar 2011 17:33:05 +0800
From: Qin Wu <sunseawq@huawei.com>
To: avt@ietf.org
Message-id: <049701cbda4f$2a38fb00$30298a0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Outlook Express 6.00.2900.3664
Content-type: multipart/mixed; boundary="Boundary_(ID_FABh5vCfVpaQYR+478BOvw)"
X-Priority: 3
X-MSMail-priority: Normal
Subject: [AVTCORE] Fw: I-D Action:draft-hunt-avtcore-monarch-00.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2011 09:34:18 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_FABh5vCfVpaQYR+478BOvw)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

Hi, folks:
The new version of draft-hunt-avtcore-monarch-00 updated from draft-hunt-avt-monarch-01
is ready at:
http://www.ietf.org/internet-drafts/draft-hunt-avtcore-monarch-00.txt

The major changes compared to previous version 00 are:
   o  Provide some background texts and related work into Introduction
      section.

   o  Add a new section 3 to describe RTP monitoring architecture.

   o  Add a new section 4 to describe RTCP Metric Block Report and
      associated parameters.

   o  Move section 3.1, 3.2,3.3 and 3.4 in draft-hunt-avt-monarch-00 to
      this version as section 5 to describe Monitoring Methodology.

   o  Add a new section 6 to describe Issues with RTCP XR extension.

   o  Merge section 3,4, 8 in previous version into one new section 9 to
      describe Guideline for reporting block format using RTCP XR.

   o  Merge section 6,7 in previous version into one new section 9 to
      describe Application to RFC 5117 topologies.

Right now, we haven't cleaned up the editor notes in the document and will do another revision before the deadline of 01 version.
I will appreciate your review if you can provide your early comments.

Regards!
-Qin 
----- Original Message ----- 
From: <Internet-Drafts@ietf.org>
To: <i-d-announce@ietf.org>
Sent: Friday, March 04, 2011 4:00 PM
Subject: I-D Action:draft-hunt-avtcore-monarch-00.txt


>A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> Title           : Monitoring Architectures for RTP
> Author(s)       : G. Hunt, et al.
> Filename        : draft-hunt-avtcore-monarch-00.txt
> Pages           : 26
> Date            : 2011-03-03
> 
> 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, as proposed 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-hunt-avtcore-monarch-00.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>


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


> _______________________________________________
> 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
>

--Boundary_(ID_FABh5vCfVpaQYR+478BOvw)
Content-type: text/plain; name=draft-hunt-avtcore-monarch-00.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=draft-hunt-avtcore-monarch-00.txt

Content-Type: text/plain
Content-ID: <2011-03-03235510.I-D@ietf.org>


--Boundary_(ID_FABh5vCfVpaQYR+478BOvw)--

From ray.vanbrandenburg@tno.nl  Fri Mar  4 04:30:20 2011
Return-Path: <ray.vanbrandenburg@tno.nl>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 47C573A6994 for <avt@core3.amsl.com>; Fri,  4 Mar 2011 04:30:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.503
X-Spam-Level: 
X-Spam-Status: No, score=-0.503 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545,  HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iI3TXawuoAk3 for <avt@core3.amsl.com>; Fri,  4 Mar 2011 04:30:19 -0800 (PST)
Received: from mailouta.tno.nl (mailouta.tno.nl [134.221.1.16]) by core3.amsl.com (Postfix) with ESMTP id E5B893A69C0 for <avt@ietf.org>; Fri,  4 Mar 2011 04:30:18 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.62,263,1297033200"; d="scan'208,217";a="48225236"
Received: from unknown (HELO mail.tno.nl) ([134.221.225.220]) by mailhost1a.tno.nl with ESMTP; 04 Mar 2011 13:31:27 +0100
Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.81]) by EXC-CASHUB01.tsn.tno.nl ([134.221.225.220]) with mapi id 14.01.0270.001; Fri, 4 Mar 2011 13:31:27 +0100
From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
To: "avt@ietf.org" <avt@ietf.org>
Thread-Topic: New revision for I-D on RTCP for IDMS
Thread-Index: AcvaaBMHJZ8GP6vMRX+LZcmYf1pUSg==
Date: Fri, 4 Mar 2011 12:31:26 +0000
Message-ID: <FCC100FC8D6B034CB88CD8173B2DA1585E3963@EXC-MBX03.tsn.tno.nl>
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: multipart/alternative; boundary="_000_FCC100FC8D6B034CB88CD8173B2DA1585E3963EXCMBX03tsntnonl_"
MIME-Version: 1.0
Subject: [AVTCORE] New revision for I-D on RTCP for IDMS
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2011 12:30:20 -0000

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

Hi all,

We have just uploaded the new version for our Internet-Draft on RTCP for ID=
MS.

http://tools.ietf.org/html/draft-brandenburg-avt-rtcp-for-idms-04

As you can see on the diff, this update has been a major revision where we =
have tried to include a solution to all of the comments and issues that we =
have discussed here on the AVT list over the past few weeks/months.

Most importantly, we have split the IDMS signalling into a XR block type fo=
r the SC->MSAS part and a seperate RTCP Packet Type for the MSAS->SC part.

Furthermore, as some people have suggested, NTP might not always be accurat=
e enough for the level of synchronization that is required for some use cas=
es. In order to solve this potential issue, we have defined an SDP clocksou=
rce parameter with which it is possible to negiotate on both the type of ti=
me synchronization that is used (NTP, GPS etc.) as well as the specific sou=
rce of this time information (e.g. which NTP server to use).

We look forward to your comments and hope to see you at IETF 80.

Best regards,

Ray van Brandenburg

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

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Arial" size=3D"2"><span style=3D"font-size:10pt;">
<div>Hi all,</div>
<div>&nbsp;</div>
<div>We have just uploaded the new version for our Internet-Draft on RTCP f=
or IDMS. </div>
<div>&nbsp;</div>
<div><font size=3D"3"><span style=3D"font-size:12pt;"><a href=3D"http://too=
ls.ietf.org/html/draft-brandenburg-avt-rtcp-for-idms-04"><font color=3D"blu=
e"><u>http://tools.ietf.org/html/draft-brandenburg-avt-rtcp-for-idms-04</u>=
</font></a> </span></font></div>
<div><font size=3D"3"><span style=3D"font-size:12pt;">&nbsp;</span></font><=
/div>
<div>As you can see on the diff, this update has been a major revision wher=
e we have tried to include a solution to all of the comments and issues tha=
t we have discussed here on the AVT list over the past few weeks/months. </=
div>
<div>&nbsp;</div>
<div>Most importantly, we have split the IDMS signalling into a XR block ty=
pe for the SC-&gt;MSAS part and a seperate RTCP Packet Type for the MSAS-&g=
t;SC part. </div>
<div>&nbsp;</div>
<div>Furthermore, as some people have suggested, NTP might not always be ac=
curate enough for the level of synchronization that is required for some us=
e cases. In order to solve this potential issue, we have defined an SDP clo=
cksource parameter with which it
is possible to negiotate on both the type of time synchronization that is u=
sed (NTP, GPS etc.) as well as the specific source of this time information=
 (e.g. which NTP server to use). </div>
<div>&nbsp;</div>
<div>We look forward to your comments and hope to see you at IETF 80. </div>
<div>&nbsp;</div>
<div>Best regards,</div>
<div>&nbsp;</div>
<div>Ray van Brandenburg</div>
<div>&nbsp;</div>
</span></font>
<font face=3D"monospace">This e-mail and its contents are subject to the DI=
SCLAIMER at http://www.tno.nl/emaildisclaimer</font></body>
</html>

--_000_FCC100FC8D6B034CB88CD8173B2DA1585E3963EXCMBX03tsntnonl_--


From fluffy@cisco.com  Fri Mar  4 09:11:47 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D59B03A687E for <avt@core3.amsl.com>; Fri,  4 Mar 2011 09:11:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.275
X-Spam-Level: 
X-Spam-Status: No, score=-110.275 tagged_above=-999 required=5 tests=[AWL=0.324, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HgWYKWTpuqhn for <avt@core3.amsl.com>; Fri,  4 Mar 2011 09:11:46 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 002BB3A6866 for <avt@ietf.org>; Fri,  4 Mar 2011 09:11:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=1797; q=dns/txt; s=iport; t=1299258775; x=1300468375; h=mime-version:subject:from:in-reply-to:date: content-transfer-encoding:message-id:references:to; bh=ztdrEavKswP0zjC5nyT8gVY2XGiFBI/gfEuRXiDPmWI=; b=mtKRjsJIbHIEbwPsb5mp0/nZoW7fNY0EEN6CHhUNuGE2aLlMG67l1eED X1CdFlOB1OK0f7kYKcgmKkSQNyEgtR0J4TqXOJpmQnDTerUJBQZYeRHT6 k7QBxuz5zTAqoRLR0rkwTAur24fumbbLggPseN3UQ73uqifGcp9gSMI2w g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAPOrcE2rR7H+/2dsb2JhbACmY3SjQ5tqhWEEhRyHE4ND
X-IronPort-AV: E=Sophos;i="4.62,264,1297036800"; d="scan'208";a="339458576"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-5.cisco.com with ESMTP; 04 Mar 2011 17:12:55 +0000
Received: from [192.168.4.100] (rcdn-fluffy-8712.cisco.com [10.99.9.19]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p24HCsrt012372; Fri, 4 Mar 2011 17:12:54 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <20110304084501.2917.19313.idtracker@localhost>
Date: Fri, 4 Mar 2011 10:15:29 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <EEEFFB03-CC13-438F-B934-3FA67EC1BE68@cisco.com>
References: <20110304084501.2917.19313.idtracker@localhost>
To: IETF AVT WG <avt@ietf.org>, Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.1082)
Subject: [AVTCORE] New RTCP section in draft-ietf-avt-app-rtp-keepalive-10.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2011 17:11:48 -0000

I read this and it looked good to me.=20

Cullen

On Mar 4, 2011, at 1:45 AM, <Internet-Drafts@ietf.org> =
<Internet-Drafts@ietf.org> wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the Audio/Video Transport Core =
Maintenance Working Group of the IETF.
>=20
>=20
>         Title           : Application Mechanism for keeping alive the =
Network Address Translator (NAT) mappings associated to RTP/RTCP flows.
>         Author(s)       : X. Marjou, A. Sollaud
>         Filename        : draft-ietf-avt-app-rtp-keepalive-10.txt
>         Pages           : 11
>         Date            : 2011-03-04
>=20
> This document lists the different mechanisms that enable applications
> using Real-time Transport Protocol (RTP) and RTP control protocol
> (RTCP) to maintain their RTP Network Address Translator (NAT)
> mappings alive.  It also makes a recommendation for a preferred
> mechanism.  This document is not applicable to Interactive
> Connectivity Establishment (ICE) agents.
>=20
> A URL for this Internet-Draft is:
> =
http://www.ietf.org/internet-drafts/draft-ietf-avt-app-rtp-keepalive-10.tx=
t
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>=20
> =
<draft-ietf-avt-app-rtp-keepalive-10.URL>_________________________________=
______________
> 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


From Even.roni@huawei.com  Fri Mar  4 09:56:32 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 171063A6856 for <avt@core3.amsl.com>; Fri,  4 Mar 2011 09:56:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.495
X-Spam-Level: 
X-Spam-Status: No, score=-101.495 tagged_above=-999 required=5 tests=[AWL=-1.001, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PGi7viBdLj-p for <avt@core3.amsl.com>; Fri,  4 Mar 2011 09:56:30 -0800 (PST)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 28C933A6830 for <avt@ietf.org>; Fri,  4 Mar 2011 09:56:30 -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 <0LHJ0055SOJTPC@szxga05-in.huawei.com> for avt@ietf.org; Sat, 05 Mar 2011 01:57:29 +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 <0LHJ00M1MOJS18@szxga05-in.huawei.com> for avt@ietf.org; Sat, 05 Mar 2011 01:57:29 +0800 (CST)
Received: from windows8d787f9 ([109.67.15.131]) by szxml11-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LHJ00JQJOJHX5@szxml11-in.huawei.com>; Sat, 05 Mar 2011 01:57:28 +0800 (CST)
Date: Fri, 04 Mar 2011 19:57:18 +0200
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <FCC100FC8D6B034CB88CD8173B2DA1585E3963@EXC-MBX03.tsn.tno.nl>
To: "'Brandenburg, R. (Ray) van'" <ray.vanbrandenburg@tno.nl>
Message-id: <00b201cbda95$a0c37f20$e24a7d60$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_3oneeckXaIiqm4OBYsX5vQ)"
Content-language: en-us
Thread-index: AcvaaBMHJZ8GP6vMRX+LZcmYf1pUSgALQZuw
References: <FCC100FC8D6B034CB88CD8173B2DA1585E3963@EXC-MBX03.tsn.tno.nl>
Cc: avt@ietf.org
Subject: Re: [AVTCORE] New revision for I-D on RTCP for IDMS
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2011 17:56:32 -0000

This is a multi-part message in MIME format.

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

Hi Ray,

AVT was restructured to four new working group. You document will be
discussed in avtcore ( <http://tools.ietf.org/wg/avtcore/charters>
http://tools.ietf.org/wg/avtcore/charters ).

It will be good if you resubmit the draft as
draft-brandenburg-avtcore-rtcp-for-idms-00

Thanks

Roni Even

 

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Brandenburg, R. (Ray) van
Sent: Friday, March 04, 2011 2:31 PM
To: avt@ietf.org
Subject: [AVTCORE] New revision for I-D on RTCP for IDMS

 

Hi all,

 

We have just uploaded the new version for our Internet-Draft on RTCP for
IDMS. 

 

http://tools.ietf.org/html/draft-brandenburg-avt-rtcp-for-idms-04 

 

As you can see on the diff, this update has been a major revision where we
have tried to include a solution to all of the comments and issues that we
have discussed here on the AVT list over the past few weeks/months. 

 

Most importantly, we have split the IDMS signalling into a XR block type for
the SC->MSAS part and a seperate RTCP Packet Type for the MSAS->SC part. 

 

Furthermore, as some people have suggested, NTP might not always be accurate
enough for the level of synchronization that is required for some use cases.
In order to solve this potential issue, we have defined an SDP clocksource
parameter with which it is possible to negiotate on both the type of time
synchronization that is used (NTP, GPS etc.) as well as the specific source
of this time information (e.g. which NTP server to use). 

 

We look forward to your comments and hope to see you at IETF 80. 

 

Best regards,

 

Ray van Brandenburg

 

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


--Boundary_(ID_3oneeckXaIiqm4OBYsX5vQ)
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:x="urn:schemas-microsoft-com:office:excel" 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;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.emailquote, li.emailquote, div.emailquote
	{mso-style-name:emailquote;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	border:none;
	padding:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.h11
	{mso-style-name:h11;
	font-family:"Courier New";
	font-weight:bold;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@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><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Hi Ray,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>AVT was restructured to four new working group. You document will be discussed in avtcore (<a href="http://tools.ietf.org/wg/avtcore/charters"><span style='color:windowtext'>http://tools.ietf.org/wg/avtcore/charters</span></a> ).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>It will be good if you resubmit the draft as </span><span class=h11><span lang=EN style='font-size:11.0pt;font-family:"Calibri","sans-serif";font-weight:normal'>draft-brandenburg-avtcore-rtcp-for-idms-00<o:p></o:p></span></span></p><p class=MsoNormal><span class=h11><span lang=EN style='font-size:11.0pt;font-family:"Calibri","sans-serif";font-weigh
 t:normal
></span></p><p class=MsoNormal><span class=h11><span lang=EN style='font-size:11.0pt;font-family:"Calibri","sans-serif";font-weight:normal'>Roni Even</span></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><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>Brandenburg, R. (Ray) van<br><b>Sent:</b> Friday, March 04, 2011 2:31 PM<br><b>To:</b> avt@ietf.org<br><b>Subject:</b> [AVTCORE] New revision for I-D on RTCP for IDMS<o:p></o:p></span></p></div></div><p cl
 ass=MsoN
p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Hi all,<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>&nbsp;<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>We have just uploaded the new version for our Internet-Draft on RTCP for IDMS. <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>&nbsp;<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif"'><a href="http://tools.ietf.org/html/draft-brandenburg-avt-rtcp-for-idms-04">http://tools.ietf.org/html/draft-brandenburg-avt-rtcp-for-idms-04</a> </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif"'>&nbsp;</span><span style='font-size:10.
 0pt;font
if"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>As you can see on the diff, this update has been a major revision where we have tried to include a solution to all of the comments and issues that we have discussed here on the AVT list over the past few weeks/months. <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>&nbsp;<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Most importantly, we have split the IDMS signalling into a XR block type for the SC-&gt;MSAS part and a seperate RTCP Packet Type for the MSAS-&gt;SC part. <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>&nbsp;<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Furthermore, as som
 e people
t not always be accurate enough for the level of synchronization that is required for some use cases. In order to solve this potential issue, we have defined an SDP clocksource parameter with which it is possible to negiotate on both the type of time synchronization that is used (NTP, GPS etc.) as well as the specific source of this time information (e.g. which NTP server to use). <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>&nbsp;<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>We look forward to your comments and hope to see you at IETF 80. <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>&nbsp;<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Best regards,<o:p></o:p></span></p></div><div><p class=MsoNormal>
 <span st
t-family:"Arial","sans-serif"'>&nbsp;<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Ray van Brandenburg<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>&nbsp;<o:p></o:p></span></p></div><p class=MsoNormal><span style='font-family:"Courier New"'>This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/emaildisclaimer</span><o:p></o:p></p></div></div></body></html>

--Boundary_(ID_3oneeckXaIiqm4OBYsX5vQ)--

From vsingh.ietf@gmail.com  Sat Mar  5 05:00:03 2011
Return-Path: <vsingh.ietf@gmail.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C66FB3A69A6 for <avt@core3.amsl.com>; Sat,  5 Mar 2011 05:00:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.569
X-Spam-Level: 
X-Spam-Status: No, score=-3.569 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y7288eMnou9O for <avt@core3.amsl.com>; Sat,  5 Mar 2011 05:00:01 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 35F073A69F2 for <avt@ietf.org>; Sat,  5 Mar 2011 05:00:01 -0800 (PST)
Received: by fxm15 with SMTP id 15so3132752fxm.31 for <avt@ietf.org>; Sat, 05 Mar 2011 05:01:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=OsHUvW7tEkwCuLiAZ5CPw9CXo38ijf63twjBRHLOLdQ=; b=Bp/10pD+Bec8tvLI6aq6kZRivxHjWvYTGnLR000Ra8cii2zDOYOOILSod9/XVA4EZv bnQeOejfnXBsgi5zGv5LCOfAc+hzrtffwpMAt4tG18LDnHqEQYPRPX223G+q/Q3+I0sp njLf8lH2wJvTsYFKhe5zCN7BeSOUfb9VX9Cx4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=bg32UmqAseBQggSZYM1aBz0G4wBykrB4mBhIciZs4xUiadj5M779WiWmzb5afXyXRB 8yClVecl3BrvOyEYDUerqiUy6ybIpW/yCeLwg8EezAPBEjm08AnAkxgR7xooyxF0PvrS rywxV9kZQ2xyQs+rZtyYNeRCJmUCMwpaA07l4=
Received: by 10.223.160.80 with SMTP id m16mr2209679fax.72.1299330071162; Sat, 05 Mar 2011 05:01:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.104.211 with HTTP; Sat, 5 Mar 2011 05:00:51 -0800 (PST)
In-Reply-To: <B99DECD58A94E143BA6F1508CC688351AEF524@DFWEML501-MBX.china.huawei.com>
References: <01fc01cbc44d$194ddc10$4be99430$%roni@huawei.com> <B99DECD58A94E143BA6F1508CC688351AC84BD@DFWEML501-MBX.china.huawei.com> <AANLkTikxwp0rrTq=RGe=HeCbwWtMXba5AyQxW6pWqo3M@mail.gmail.com> <B99DECD58A94E143BA6F1508CC688351AEF524@DFWEML501-MBX.china.huawei.com>
From: varun singh <vsingh.ietf@gmail.com>
Date: Sat, 5 Mar 2011 15:00:51 +0200
Message-ID: <AANLkTinF3JaF7L6RAxMjrSnGzJTrn+N8MF6xiVDnFpPw@mail.gmail.com>
To: Ye-Kui Wang <yekui.wang@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: varun <varun@comnet.tkk.fi>, "avt-at-ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] Comments on draft-singh-avt-mprtp-01
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Mar 2011 13:00:04 -0000

Hi Ye-kui,

Thanks for the response, responses inline.

On Thu, Feb 24, 2011 at 19:52, Ye-Kui Wang <yekui.wang@huawei.com> wrote:
> Hi Varun,
> From: varun singh [mailto:vsingh.ietf@gmail.com]
> Sent: Friday, February 11, 2011 9:16 AM

snip!

> On Tue, Feb 8, 2011 at 02:15, Wangyekui <yekui.wang@huawei.com> wrote:
>> -=A0=A0=A0=A0=A0=A0=A0=A0=A0 First of all, I think this draft initiated =
a very useful work. For example, today, many mobile operators have deployed=
 dual-plane IP bearer networks, wherein a multipath version of RTP can be u=
sed for real-time communications such as voice- and video-over-IP services.=
 BTW, you may want to mention this in the introduction section.
>
> Can you elaborate on what is a dual-plane IP bearer.
>
> YK: This is basically an IP bearer network with two planes, between which=
 there can be communications. When there is problem is one plane, services =
would be all switched to the other plane. Mobile operators deploy such netw=
orks for robust service provisioning. In the multi-path context, two planes=
 provide at least two paths for data transfer.


VS: Like mentioned elsewhere, that this specification is supposed to
be generic and agnostic to specific architectures. To reiterate, the
draft aims to use multiple interface at one or both end-points to
achieve its goals. If the mobile operator is one of the end-point then
it could advertise its multiple paths and use MPRTP as currently
defined.

However, if the mobile operator is an intermediate component (hop)
then this is a bit more complex use-case and is currently out of scope
for the current document. It also opens up new issues like route
labeling, route advertisement etc. So that endpoints can schedule
packets to take a specific route.

>
>> -=A0=A0=A0=A0=A0=A0=A0=A0=A0 The draft specifies the negotiation of mult=
iple paths is through upgrading from a single-path session and using in-ban=
d signaling (i.e. RTP header extension) for indication of additional paths.=
 Would it be better to negotiate the use of one or more of the available pa=
ths out-of-band (i.e. using SDP)? One problem with in-band negotiation is t=
hat, if the initial path happens to be broken, then even the session setup =
would fail. Another problem is that in-band information may get lost (and w=
hen it happens the negotiation would fail).
>
> If the initial path is broken then it would also fail for the case of
> single path RTP.
>
> YK: Right, that's the point. If initially multiple possible paths are off=
ered, then the other side may check and choose the best one or at least a w=
orking one.
>

VS: The in-band negotiation is a mechanism to quickly start a basic
RTP session and then upgrade it without running combinatorial number
of connectivity checks before the first frame of audio/video is sent.

> In the spec we allow for ICE and SDP. SDP is too slow
> to always negotiate.
>
> YK: What do you mean by "allow for SDP"? Allow for offering multiple path=
s using SDP?
>

VS: This is an open questions: do we want to use ICE for MPRTP? or is
it possible to use subset of its features and adapt them for MPRTP. To
that end, we have kept the draft open ended and think that this is
something we need to clarify within at the meeting in Prague.

>> -=A0=A0=A0=A0=A0=A0=A0=A0=A0 In some cases, it may be useful to use mult=
iple paths concurrently, for improved throughput. In some other cases, it m=
ay be more desirable to use only a subset of available paths at any time in=
stance. For example, in mobile networks using dual-plane IP bearer, typical=
ly the better-performing path is used, while the other path is kept there f=
or fast fallback when the path being used has problem. Therefore, it would =
be desirable if signaling of such a capability/preference is possible.
>>
>
> This is a good point and the draft aims to have basic mechanisms
> first. Profiles to be added later, may be to the same document or as a
> different draft. We'll add this inside as an editor's note.
>
> YK: Good.
>
>> -=A0=A0=A0=A0=A0=A0=A0=A0=A0 Finally, it would be useful if it is possib=
le to indicate more path specific information when advertising paths (or "i=
nterfaces" as used in the draft), e.g., which of the two planes in a networ=
k using dual-plane IP bearer. It might be sufficient if there is a hook spe=
cified to enable backwards compatible extensions when the potential multipa=
th RTP standard is used in the future by application system standards.
>
> We need to stay independent of network architecture or infrastructure.
>
> YK: Agreed.
>
> However, can you elaborate on the extension that can signal a path's
> characteristic?
>
> YK: Actually I found that the "mprtp-optional-parameter" in the current d=
raft is already sufficient for this. We just need to keep in mind that in t=
he final spec there should be such an openly specified parameter.
>
>

VS: Yes, the intention is to keep it open ended.

From ray.vanbrandenburg@tno.nl  Mon Mar  7 00:35:00 2011
Return-Path: <ray.vanbrandenburg@tno.nl>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6675D3A6827 for <avt@core3.amsl.com>; Mon,  7 Mar 2011 00:35:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.503
X-Spam-Level: 
X-Spam-Status: No, score=-0.503 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545,  HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PbO+Mob5Cyec for <avt@core3.amsl.com>; Mon,  7 Mar 2011 00:34:59 -0800 (PST)
Received: from mailoutb.tno.nl (mailoutb.tno.nl [134.221.1.17]) by core3.amsl.com (Postfix) with ESMTP id 6F6E83A6800 for <avt@ietf.org>; Mon,  7 Mar 2011 00:34:58 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.62,276,1297033200"; d="scan'208,217";a="11630982"
Received: from unknown (HELO mail.tno.nl) ([134.221.225.221]) by mailhost1b.tno.nl with ESMTP; 07 Mar 2011 09:36:06 +0100
Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.81]) by EXC-CASHUB02.tsn.tno.nl ([134.221.225.221]) with mapi id 14.01.0270.001; Mon, 7 Mar 2011 09:36:05 +0100
From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
To: 'Roni Even' <Even.roni@huawei.com>
Thread-Topic: [AVTCORE] New revision for I-D on RTCP for IDMS
Thread-Index: AcvaaBMHJZ8GP6vMRX+LZcmYf1pUSgALQZuwAIM7FFA=
Date: Mon, 7 Mar 2011 08:36:05 +0000
Message-ID: <FCC100FC8D6B034CB88CD8173B2DA1580ADFEA3B@EXC-MBX03.tsn.tno.nl>
References: <FCC100FC8D6B034CB88CD8173B2DA1585E3963@EXC-MBX03.tsn.tno.nl> <00b201cbda95$a0c37f20$e24a7d60$%roni@huawei.com>
In-Reply-To: <00b201cbda95$a0c37f20$e24a7d60$%roni@huawei.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: multipart/alternative; boundary="_000_FCC100FC8D6B034CB88CD8173B2DA1580ADFEA3BEXCMBX03tsntnon_"
MIME-Version: 1.0
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] New revision for I-D on RTCP for IDMS
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Mar 2011 08:35:00 -0000

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

Hi Roni,

Thanks. You can find the new avtcore version here:
http://tools.ietf.org/html/draft-brandenburg-avtcore-rtcp-for-idms-00

Do you perhaps know if it is possible to link this new avtcore version to t=
he old set of drafts marked under avt in some way? (I believe a similar lin=
k is used when a document becomes a WG item) This way it would be immediate=
ly visible that this is in fact the fourth version of this document instead=
 of the first and people would be able to find the mailing list discussions=
 related to this draft more easily.

Regards,

Ray

________________________________
From: Roni Even [mailto:Even.roni@huawei.com]
Sent: vrijdag 4 maart 2011 18:57
To: Brandenburg, R. (Ray) van
Cc: avt@ietf.org
Subject: RE: [AVTCORE] New revision for I-D on RTCP for IDMS

Hi Ray,
AVT was restructured to four new working group. You document will be discus=
sed in avtcore (http://tools.ietf.org/wg/avtcore/charters ).
It will be good if you resubmit the draft as draft-brandenburg-avtcore-rtcp=
-for-idms-00
Roni Even

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Brand=
enburg, R. (Ray) van
Sent: Friday, March 04, 2011 2:31 PM
To: avt@ietf.org
Subject: [AVTCORE] New revision for I-D on RTCP for IDMS
Hi all,

We have just uploaded the new version for our Internet-Draft on RTCP for ID=
MS.

http://tools.ietf.org/html/draft-brandenburg-avt-rtcp-for-idms-04

As you can see on the diff, this update has been a major revision where we =
have tried to include a solution to all of the comments and issues that we =
have discussed here on the AVT list over the past few weeks/months.

Most importantly, we have split the IDMS signalling into a XR block type fo=
r the SC->MSAS part and a seperate RTCP Packet Type for the MSAS->SC part.

Furthermore, as some people t not always be accurate enough for the level o=
f synchronization that is required for some use cases. In order to solve th=
is potential issue, we have defined an SDP clocksource parameter with which=
 it is possible to negiotate on both the type of time synchronization that =
is used (NTP, GPS etc.) as well as the specific source of this time informa=
tion (e.g. which NTP server to use).

We look forward to your comments and hope to see you at IETF 80.

Best regards,

Ray van Brandenburg

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

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v=3D"urn:schemas-micr=
osoft-com:vml" xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=
=3D"urn:schemas-microsoft-com:office:word" xmlns:x=3D"urn:schemas-microsoft=
-com:office:excel" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/o=
mml">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta content=3D"MSHTML 6.00.6000.17095" name=3D"GENERATOR">
<style>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","seri=
f"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","seri=
f"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","seri=
f"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.emailquote {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PA=
DDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN-LEFT: 1pt; BO=
RDER-LEFT: medium none; MARGIN-RIGHT: 0in; PADDING-TOP: 0in; BORDER-BOTTOM:=
 medium none; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: email=
quote; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
LI.emailquote {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PA=
DDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN-LEFT: 1pt; BO=
RDER-LEFT: medium none; MARGIN-RIGHT: 0in; PADDING-TOP: 0in; BORDER-BOTTOM:=
 medium none; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: email=
quote; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
DIV.emailquote {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PA=
DDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN-LEFT: 1pt; BO=
RDER-LEFT: medium none; MARGIN-RIGHT: 0in; PADDING-TOP: 0in; BORDER-BOTTOM:=
 medium none; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: email=
quote; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: perso=
nal-reply
}
SPAN.h11 {
	FONT-WEIGHT: bold; FONT-FAMILY: "Courier New"; mso-style-name: h11
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.WordSection1 {
	page: WordSection1
}
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" vlink=3D"purple" link=3D"blue">
<div dir=3D"ltr" align=3D"left"><span class=3D"218153108-07032011"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2">Hi Roni,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"218153108-07032011"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"218153108-07032011"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2">Thanks. You can find the new avtc=
ore version here:</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"218153108-07032011"><a href=
=3D"http://tools.ietf.org/html/draft-brandenburg-avtcore-rtcp-for-idms-00">=
http://tools.ietf.org/html/draft-brandenburg-avtcore-rtcp-for-idms-00</a></=
span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"218153108-07032011"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"218153108-07032011"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2">Do you perhaps know if it is poss=
ible to link this new&nbsp;avtcore version&nbsp;to the old set of drafts&nb=
sp;marked under&nbsp;avt in some way? (I believe a similar link
 is used when a document becomes a WG item) This way it would be immediatel=
y visible that this is in fact the fourth version of this document instead =
of the first and people would be able to find the mailing list discussions =
related to this draft more easily.
</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"218153108-07032011"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"218153108-07032011"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2">Regards,</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"218153108-07032011"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"218153108-07032011"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2">Ray</font></span></div>
<br>
<div class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"lef=
t">
<hr tabindex=3D"-1">
<font face=3D"Tahoma" size=3D"2"><b>From:</b> Roni Even [mailto:Even.roni@h=
uawei.com]
<br>
<b>Sent:</b> vrijdag 4 maart 2011 18:57<br>
<b>To:</b> Brandenburg, R. (Ray) van<br>
<b>Cc:</b> avt@ietf.org<br>
<b>Subject:</b> RE: [AVTCORE] New revision for I-D on RTCP for IDMS<br>
</font><br>
</div>
<div></div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibr=
i','sans-serif'">Hi Ray,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibr=
i','sans-serif'">AVT was restructured to four new working group. You docume=
nt will be discussed in avtcore (<a href=3D"http://tools.ietf.org/wg/avtcor=
e/charters"><span style=3D"COLOR: windowtext">http://tools.ietf.org/wg/avtc=
ore/charters</span></a>
 ).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibr=
i','sans-serif'">It will be good if you resubmit the draft as
</span><span class=3D"h11"><span lang=3D"EN" style=3D"FONT-WEIGHT: normal; =
FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">draft-brandenburg-avt=
core-rtcp-for-idms-00<o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><span class=3D"h11"><span lang=3D"EN" style=3D"FONT-=
SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'" font-size:11.0pt;font-fami=
ly:?Calibri?,?sans-serif?;font-weight:normal?=3D"">Roni Even</span></span><=
span style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT=
-FAMILY: 'Calibri','sans-serif'"><o:p>&nbsp;</o:p></span></p>
<div style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: me=
dium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue 1.5pt =
solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<div>
<div style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b=
5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: mediu=
m none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<p class=3D"MsoNormal"><b><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tah=
oma','sans-serif'">From:</span></b><span style=3D"FONT-SIZE: 10pt; FONT-FAM=
ILY: 'Tahoma','sans-serif'"> avt-bounces@ietf.org [mailto:avt-bounces@ietf.=
org]
<b>On Behalf Of </b>Brandenburg, R. (Ray) van<br>
<b>Sent:</b> Friday, March 04, 2011 2:31 PM<br>
<b>To:</b> avt@ietf.org<br>
<b>Subject:</b> [AVTCORE] New revision for I-D on RTCP for IDMS<o:p></o:p><=
/span></p>
</div>
</div>
<p class=3D"MsoN" p=3D""></p>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">Hi all,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">We have just uploaded the new version for our Internet-Draft=
 on RTCP for IDMS.
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Arial','sans-serif'"><a=
 href=3D"http://tools.ietf.org/html/draft-brandenburg-avt-rtcp-for-idms-04"=
>http://tools.ietf.org/html/draft-brandenburg-avt-rtcp-for-idms-04</a>
</span><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><=
o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Arial','sans-serif'">&n=
bsp;</span><span style=3D"FONT-SIZE: 10pt"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">As you can see on the diff, this update has been a major rev=
ision where we have tried to include a solution to all of the comments and =
issues that we have discussed here on
 the AVT list over the past few weeks/months. <o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">Most importantly, we have split the IDMS signalling into a X=
R block type for the SC-&gt;MSAS part and a seperate RTCP Packet Type for t=
he MSAS-&gt;SC part.
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">Furthermore, as some people t not always be accurate enough =
for the level of synchronization that is required for some use cases. In or=
der to solve this potential issue, we
 have defined an SDP clocksource parameter with which it is possible to neg=
iotate on both the type of time synchronization that is used (NTP, GPS etc.=
) as well as the specific source of this time information (e.g. which NTP s=
erver to use).
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">We look forward to your comments and hope to see you at IETF=
 80.
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">Best regards,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span stt-family:?Arial?,?sans-serif??=3D"">&nbsp;<o=
:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">Ray van Brandenburg<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'=
,'sans-serif'">&nbsp;<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'">This e-ma=
il and its contents are subject to the DISCLAIMER at http://www.tno.nl/emai=
ldisclaimer</span><o:p></o:p></p>
</div>
</div>
<font face=3D"monospace">This e-mail and its contents are subject to the DI=
SCLAIMER at http://www.tno.nl/emaildisclaimer</font></body>
</html>

--_000_FCC100FC8D6B034CB88CD8173B2DA1580ADFEA3BEXCMBX03tsntnon_--


From magnus.westerlund@ericsson.com  Mon Mar  7 07:58:33 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 800523A6906 for <avt@core3.amsl.com>; Mon,  7 Mar 2011 07:58:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.437
X-Spam-Level: 
X-Spam-Status: No, score=-106.437 tagged_above=-999 required=5 tests=[AWL=0.162, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t8EVSbQDAZG6 for <avt@core3.amsl.com>; Mon,  7 Mar 2011 07:58:32 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 774FA3A686E for <avt@ietf.org>; Mon,  7 Mar 2011 07:58:31 -0800 (PST)
X-AuditID: c1b4fb39-b7c6dae0000023f2-40-4d7500f05686
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id D6.4A.09202.0F0057D4; Mon,  7 Mar 2011 16:59:45 +0100 (CET)
Received: from [147.214.183.8] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.2.234.1; Mon, 7 Mar 2011 16:59:44 +0100
Message-ID: <4D7500F0.5000109@ericsson.com>
Date: Mon, 7 Mar 2011 16:59:44 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: IETF AVTCore WG <avt@ietf.org>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Subject: [AVTCORE] WG last call: draft-ietf-avtcore-srtp-vbr-audio-00 to BCP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Mar 2011 15:58:33 -0000

WG,

This starts a 3 week Working Group Last Call for "Guidelines for the use
of Variable Bit Rate Audio with Secure RTP"
draft-ietf-avtcore-srtp-vbr-audio-00 with the intended status of BCP.
The WG last call ends Sunday the 27th of March.

https://datatracker.ietf.org/doc/draft-ietf-avtcore-srtp-vbr-audio/

Please send any comments to the AVTCore mailing list.

Regards

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 csp@csperkins.org  Tue Mar  8 15:03:40 2011
Return-Path: <csp@csperkins.org>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E40483A67AB for <avt@core3.amsl.com>; Tue,  8 Mar 2011 15:03:40 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id La7dNtBX7-Yn for <avt@core3.amsl.com>; Tue,  8 Mar 2011 15:03:40 -0800 (PST)
Received: from lon1-msapost-3.mail.demon.net (lon1-msapost-3.mail.demon.net [195.173.77.182]) by core3.amsl.com (Postfix) with ESMTP id A51F23A659B for <avt@ietf.org>; Tue,  8 Mar 2011 15:03:36 -0800 (PST)
Received: from starkperkins.demon.co.uk ([80.176.158.71] helo=[192.168.0.5]) by lon1-post-3.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1Px5xT-0003fY-dw; Tue, 08 Mar 2011 23:04:51 +0000
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <EEEFFB03-CC13-438F-B934-3FA67EC1BE68@cisco.com>
Date: Tue, 8 Mar 2011 23:04:49 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <1B0E492F-90B3-4820-B1F9-32F4FB3F72CD@csperkins.org>
References: <20110304084501.2917.19313.idtracker@localhost> <EEEFFB03-CC13-438F-B934-3FA67EC1BE68@cisco.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.1082)
Cc: Cullen Jennings <fluffy@cisco.com>, IETF AVT WG <avt@ietf.org>
Subject: Re: [AVTCORE] New RTCP section in draft-ietf-avt-app-rtp-keepalive-10.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2011 23:03:41 -0000

Looks good to me too.
Colin


On 4 Mar 2011, at 17:15, Cullen Jennings wrote:
> I read this and it looked good to me.=20
>=20
> Cullen
>=20
> On Mar 4, 2011, at 1:45 AM, <Internet-Drafts@ietf.org> =
<Internet-Drafts@ietf.org> wrote:
>=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
>>=20
>>        Title           : Application Mechanism for keeping alive the =
Network Address Translator (NAT) mappings associated to RTP/RTCP flows.
>>        Author(s)       : X. Marjou, A. Sollaud
>>        Filename        : draft-ietf-avt-app-rtp-keepalive-10.txt
>>        Pages           : 11
>>        Date            : 2011-03-04
>>=20
>> This document lists the different mechanisms that enable applications
>> using Real-time Transport Protocol (RTP) and RTP control protocol
>> (RTCP) to maintain their RTP Network Address Translator (NAT)
>> mappings alive.  It also makes a recommendation for a preferred
>> mechanism.  This document is not applicable to Interactive
>> Connectivity Establishment (ICE) agents.
>>=20
>> A URL for this Internet-Draft is:
>> =
http://www.ietf.org/internet-drafts/draft-ietf-avt-app-rtp-keepalive-10.tx=
t
>>=20
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>=20
>> Below is the data which will enable a MIME compliant mail reader
>> implementation to automatically retrieve the ASCII version of the
>> Internet-Draft.
>>=20
>> =
<draft-ietf-avt-app-rtp-keepalive-10.URL>_________________________________=
______________
>> 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
>=20
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt



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




From fluffy@cisco.com  Tue Mar  8 15:30:17 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 938073A67C2 for <avt@core3.amsl.com>; Tue,  8 Mar 2011 15:30:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.557
X-Spam-Level: 
X-Spam-Status: No, score=-110.557 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yWyFHzCbppBm for <avt@core3.amsl.com>; Tue,  8 Mar 2011 15:30:12 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 7F9C73A67B8 for <avt@ietf.org>; Tue,  8 Mar 2011 15:30:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=642; q=dns/txt; s=iport; t=1299627087; x=1300836687; h=from:content-transfer-encoding:subject:date:message-id: to:mime-version; bh=6MbfOvNhh3qyokqW/SnwzN52ePMfwLbmhKQmOpwBO64=; b=g3oNxah82sEa2noOjmPXUEfZ2o+66TslfAeww0bP8YkIrydthKDVC4iE RXRLrG0SMtsaIUSVCE4BoC4or4foLayMhVxEEN6oPt1J1JZyFU7LQmSPa 2924TGaILNgXdbxF1jvLSZ2pC8QTHxhqyWPlc2PT9AgEKcgyo1dlPCw7P I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAANLdk2rRN+J/2dsb2JhbACmZ3SlDZw5hWMEhR2HFYNH
X-IronPort-AV: E=Sophos;i="4.62,286,1297036800"; d="scan'208";a="272828407"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-4.cisco.com with ESMTP; 08 Mar 2011 23:31:27 +0000
Received: from [192.168.4.100] (rcdn-fluffy-8712.cisco.com [10.99.9.19]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id p28NVQ8b028215 for <avt@ietf.org>; Tue, 8 Mar 2011 23:31:26 GMT
From: Cullen Jennings <fluffy@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 8 Mar 2011 16:34:02 -0700
Message-Id: <11120238-4159-4BA7-B150-0B28E86651B3@cisco.com>
To: IETF AVT WG <avt@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
Subject: [AVTCORE] SSRC multiplexing of RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2011 23:30:17 -0000

I've been geeing a lot of questions lately about ways to multiplex RTP =
onto one UDP port. This would be for an environment using point to point =
media flows set up with SIP between endpoints or between an endpoint and =
centralized conferring unit. There is no multicast involved in these use =
cases. For example the SSRC based approach in=20

=
http://www.jdrosen.net/papers/draft-peterson-rosenberg-avt-rtp-ssrc-demux-=
00.txt

Now, I do recall that people felt there were problems with this type of =
approach but I forget what they were. Can someone help remind me what =
the issues are with this.=20

Thanks, Cullen


From magnus.westerlund@ericsson.com  Tue Mar  8 23:41:16 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6CF2A3A685D for <avt@core3.amsl.com>; Tue,  8 Mar 2011 23:41:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.453
X-Spam-Level: 
X-Spam-Status: No, score=-106.453 tagged_above=-999 required=5 tests=[AWL=0.146, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hBhBRzvTJ3Gk for <avt@core3.amsl.com>; Tue,  8 Mar 2011 23:41:15 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 371483A67ED for <avt@ietf.org>; Tue,  8 Mar 2011 23:41:14 -0800 (PST)
X-AuditID: c1b4fb3d-b7bbbae000005311-f4-4d772f665972
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id DC.F9.21265.66F277D4; Wed,  9 Mar 2011 08:42:30 +0100 (CET)
Received: from [147.214.183.8] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.2.234.1; Wed, 9 Mar 2011 08:42:30 +0100
Message-ID: <4D772F66.7000105@ericsson.com>
Date: Wed, 9 Mar 2011 08:42:30 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: avt@ietf.org
References: <11120238-4159-4BA7-B150-0B28E86651B3@cisco.com>
In-Reply-To: <11120238-4159-4BA7-B150-0B28E86651B3@cisco.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [AVTCORE] SSRC multiplexing of RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Mar 2011 07:41:16 -0000

Cullen Jennings skrev 2011-03-09 00:34:
> 
> I've been geeing a lot of questions lately about ways to multiplex
> RTP onto one UDP port. This would be for an environment using point
> to point media flows set up with SIP between endpoints or between an
> endpoint and centralized conferring unit. There is no multicast
> involved in these use cases. For example the SSRC based approach in
> 
> http://www.jdrosen.net/papers/draft-peterson-rosenberg-avt-rtp-ssrc-demux-00.txt
>
>  Now, I do recall that people felt there were problems with this type
> of approach but I forget what they were. Can someone help remind me
> what the issues are with this.
> 

I have written a summary of the issues in Section 2.1 of
http://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/

But, that has actually not considered the actual feedback when this
document was discussed. Should do some digging and see if there is
anything in that discussion that should be added to our document.

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 gunnar.hellstrom@omnitor.se  Wed Mar  9 07:10:26 2011
Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6019B3A69DC for <avt@core3.amsl.com>; Wed,  9 Mar 2011 07:10:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wlTyh0cmX08v for <avt@core3.amsl.com>; Wed,  9 Mar 2011 07:10:25 -0800 (PST)
Received: from vsp-outgoing1.binero.net (vsp-outgoing1.binero.net [193.17.218.160]) by core3.amsl.com (Postfix) with SMTP id CC1AD3A6881 for <avt@ietf.org>; Wed,  9 Mar 2011 07:10:24 -0800 (PST)
Received: from smtp01.binero.se (unknown [195.74.39.229]) by vsp-outgoing1.binero.net (Halon Mail Gateway) with ESMTP for <avt@ietf.org>; Wed,  9 Mar 2011 16:11:32 +0100 (CET)
Received: from [192.168.0.210] (136.240.13.217.in-addr.dgcsystems.net [217.13.240.136]) by smtp-04-01.atm.binero.net (Postfix) with ESMTPA id 04B6D3A170 for <avt@ietf.org>; Wed,  9 Mar 2011 16:11:32 +0100 (CET)
Message-ID: <4D7798A9.7080006@omnitor.se>
Date: Wed, 09 Mar 2011 16:11:37 +0100
From: =?ISO-8859-1?Q?Gunnar_Hellstr=F6m?= <gunnar.hellstrom@omnitor.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; sv-SE; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: avt@ietf.org
References: <11120238-4159-4BA7-B150-0B28E86651B3@cisco.com>
In-Reply-To: <11120238-4159-4BA7-B150-0B28E86651B3@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [AVTCORE] SSRC multiplexing of RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Mar 2011 15:10:26 -0000

Cullen

I agree. I have also got negative feedback on SSRC multiplexing.

I had it described in the draft for multi-party handling of real-time 
text in draft-hellstrom-text-conference-02.txt
in order to easily separate the streams from different sources and 
display them in a way that the receiver decides.

But the feedback was that many RTP implementations would just regard it 
to be an error if a new SSRC appeared in the session and it would cause 
problems.

SSRC multiplexing also has some trickiness in that when a new SSRC 
appears in the session, it can either be an old stream that changed SSRC 
or a new multiplexed stream. RFC 3550 mentions ways to handle that but 
there is a risk for losing initial packets before it is sorted out. 
Losing initial packets in e.g. a video stream can be fatal for the 
possibility to start proper decoding rapidly.

Taking the consequences of this, I am just about to submit a modified 
draft for the real-time text case using one stream and marking the 
source by CSRC per packet.
It will survive through most existing RTP implementations.

/Gunnar


Cullen Jennings skrev 2011-03-09 00:34:
> I've been geeing a lot of questions lately about ways to multiplex RTP onto one UDP port. This would be for an environment using point to point media flows set up with SIP between endpoints or between an endpoint and centralized conferring unit. There is no multicast involved in these use cases. For example the SSRC based approach in
>
> http://www.jdrosen.net/papers/draft-peterson-rosenberg-avt-rtp-ssrc-demux-00.txt
>
> Now, I do recall that people felt there were problems with this type of approach but I forget what they were. Can someone help remind me what the issues are with this.
>
> Thanks, Cullen
>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt

From magnus.westerlund@ericsson.com  Wed Mar  9 07:39:27 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC7F03A689F for <avt@core3.amsl.com>; Wed,  9 Mar 2011 07:39:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.471
X-Spam-Level: 
X-Spam-Status: No, score=-106.471 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KMZTV+Ig4Uin for <avt@core3.amsl.com>; Wed,  9 Mar 2011 07:39:26 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 6E8AA3A6866 for <avt@ietf.org>; Wed,  9 Mar 2011 07:39:26 -0800 (PST)
X-AuditID: c1b4fb39-b7c6dae0000023f2-21-4d779f7a523d
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id DD.2D.09202.A7F977D4; Wed,  9 Mar 2011 16:40:42 +0100 (CET)
Received: from [147.214.183.8] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.2.234.1; Wed, 9 Mar 2011 16:40:42 +0100
Message-ID: <4D779F79.8090001@ericsson.com>
Date: Wed, 9 Mar 2011 16:40:41 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: avt@ietf.org
References: <11120238-4159-4BA7-B150-0B28E86651B3@cisco.com> <4D7798A9.7080006@omnitor.se>
In-Reply-To: <4D7798A9.7080006@omnitor.se>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [AVTCORE] SSRC multiplexing of RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Mar 2011 15:39:27 -0000

Hi Gunnar,

Gunnar Hellström skrev 2011-03-09 16:11:
> Cullen
> 
> I agree. I have also got negative feedback on SSRC multiplexing.
> 
> I had it described in the draft for multi-party handling of real-time 
> text in draft-hellstrom-text-conference-02.txt
> in order to easily separate the streams from different sources and 
> display them in a way that the receiver decides.
> 
> But the feedback was that many RTP implementations would just regard it 
> to be an error if a new SSRC appeared in the session and it would cause 
> problems.

Well, this is how you are supposed to use cases when you have multiple
sources. And text chat is case when implementations can't really say
that they don't have the rendering capabilities for it. But I do
understand that most implementations sucks at handling multiple SSRCs
which is very bad.

My hope is that we will see a bit of signalling support for handling
multiple SSRCs as part of the CLUE work. But, we do need to push that
support for multiple SSRCs, it needs to be in the stacks.

> 
> SSRC multiplexing also has some trickiness in that when a new SSRC 
> appears in the session, it can either be an old stream that changed SSRC 
> or a new multiplexed stream. RFC 3550 mentions ways to handle that but 
> there is a risk for losing initial packets before it is sorted out. 
> Losing initial packets in e.g. a video stream can be fatal for the 
> possibility to start proper decoding rapidly.

I guess clarifications should be in place here. And your strategy for
handling it will depend a lot of what application it is and which media
one talks about.

> 
> Taking the consequences of this, I am just about to submit a modified 
> draft for the real-time text case using one stream and marking the 
> source by CSRC per packet.
> It will survive through most existing RTP implementations.
> 

So your going with a mixer design, despite that for text it isn't really
needed. I think it is unfortunate, but I guess pragmatic due to poor
implementation support.

A question to implementors:

Have you tried running the tests documented in RTP testing strategies?
http://www.rfc-editor.org/rfc/rfc3158.txt

These are excellent tests to check that ones implementation handles what
it needs to.

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 Mar 10 07:20:53 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 632293A6A00 for <avt@core3.amsl.com>; Thu, 10 Mar 2011 07:20:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.176
X-Spam-Level: 
X-Spam-Status: No, score=-106.176 tagged_above=-999 required=5 tests=[AWL=-0.177, BAYES_00=-2.599, J_CHICKENPOX_42=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YhPgYdnwCVEC for <avt@core3.amsl.com>; Thu, 10 Mar 2011 07:20:52 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id E27263A69A9 for <avt@ietf.org>; Thu, 10 Mar 2011 07:20:51 -0800 (PST)
X-AuditID: c1b4fb3d-b7bbbae000005311-3e-4d78eca00648
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id DC.A8.21265.0ACE87D4; Thu, 10 Mar 2011 16:22:08 +0100 (CET)
Received: from [147.214.183.8] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.2.234.1; Thu, 10 Mar 2011 16:22:07 +0100
Message-ID: <4D78EC9F.2070508@ericsson.com>
Date: Thu, 10 Mar 2011 16:22:07 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: "Belling, Thomas (NSN - DE/Munich)" <thomas.belling@nsn.com>
References: <744A66DF31B5B34EA8B08BBD8187A72203597EAD@DEMUEXC014.nsn-intra.net>	<4D5A4456.8070000@ericsson.com>	<744A66DF31B5B34EA8B08BBD8187A722035E48E5@DEMUEXC014.nsn-intra.net>	<92AF6A87-D0C7-4F74-B9EF-C61B66BC9854@g11.org.uk>	<744A66DF31B5B34EA8B08BBD8187A722035E499F@DEMUEXC014.nsn-intra.net>	<4D5E3949.30804@ericsson.com>	<744A66DF31B5B34EA8B08BBD8187A72203664A86@DEMUEXC014.nsn-intra.net>	<4D62404C.5080807@ericsson.com>	<744A66DF31B5B34EA8B08BBD8187A722036E8D17@DEMUEXC014.nsn-intra.net> <4D64C166.2020902@ericsson.com>
In-Reply-To: <4D64C166.2020902@ericsson.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: IETF AVT WG <avt@ietf.org>
Subject: Re: [AVTCORE] draft-ietf-avtcore-ecn-for-rtp-00.txt: What to do if "ecn-fb" has not been negotiated via rtcp.fb attribute?
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Mar 2011 15:20:53 -0000

Magnus Westerlund skrev 2011-02-23 09:12:
> Belling, Thomas (NSN - DE/Munich) skrev 2011-02-23 03:07:
>> Hi Magnus,
>>
>> please note that the agreed procedures in TS 26.114 currently do not assume the behaviour discussed in this thread from peers, as we deemed it safer not to take any such assumptions.
>>
>> Although the question poped up when we were preparing the procedures.
>>
>> So you believe such a recommendation is not appropriate?
> 
> I think there can be an informative pointer to that in advanced use case
> beyond what is defined in here, it is important to watch the RTCP-FB
> attribute for what messages really should be used in a session.
> 

Hi I wanted to follow up on the above.

I have looked on what is written and would like to point at Section 7.1:

The "ecn-capable-rtp" SDP attribute MUST always be used when employing
ECN for RTP according to this specification. As the XR ECN summary
report is required independently of the initialization method, or
congestion control scheme the "rtcp-xr" attribute with the "ecn-sum"
parameter MUST also be used. The "rtcp-fb" attribute with the "nack"
parameter "ecn" MUST be used whenever the initialization method or a
congestion control algorithm requiring timely sender side knowledge of
received CE markings. If the congestion control scheme uses additional
signalling they should be indicated as appropriate for those signalling
methods.

All except the last sentence was present in the 00 version. I suggest
that we add the last sentence to make it clear that there may be
additional signalling requirements for some congestion control schemes.

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 Mar 10 07:31:29 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A2CDE3A6A11 for <avt@core3.amsl.com>; Thu, 10 Mar 2011 07:31:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.469
X-Spam-Level: 
X-Spam-Status: No, score=-106.469 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IPAqVDcCeCTc for <avt@core3.amsl.com>; Thu, 10 Mar 2011 07:31:28 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 03B073A69E2 for <avt@ietf.org>; Thu, 10 Mar 2011 07:31:27 -0800 (PST)
X-AuditID: c1b4fb3d-b7bbbae000005311-95-4d78ef1d8e55
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 15.8A.21265.D1FE87D4; Thu, 10 Mar 2011 16:32:45 +0100 (CET)
Received: from [147.214.183.8] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.2.234.1; Thu, 10 Mar 2011 16:32:45 +0100
Message-ID: <4D78EF1D.5050104@ericsson.com>
Date: Thu, 10 Mar 2011 16:32:45 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: IETF AVTCore WG <avt@ietf.org>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Subject: [AVTCORE] Proposed changes to draft-ietf-avtcore-ecn-for-rtp
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Mar 2011 15:31:29 -0000

Hi,

This email contains a number of suggested changes that are the result of
various comments on list and also off it. I appreciate rapid feedback as
the plan is to include it in an update submitted on Monday unless people
have suggestions for improvement or gripe with what is suggested.


Section 2:
I have received a comment that it not all clear what is meant with
Sender and Receiver. As this intended to be the RTP packet sender that
originates the data and the RTP packet receiver that sinks the media.
The complication are any media level middlebox such as a mixer or
translator that splits the ECN control loop. In these cases the mixer or
translator will also be senders and receivers due to that they sinks and
originates the RTP media packets. Thus I propose the following
definition to be added to section 2 after the abbreviation:

This document uses the terms sender and receiver according to the
following definition:

Sender: Sender of RTP packets carrying an encoded media stream. The
sender has the possibility to effect how this transmission is performed.
It is one end-point of the ECN control loop.

Receiver: A receiver of RTP packets with the intention to consume the
media stream in some form. It sends RTCP feedback on the received
stream. It is the other end-point of the ECN control loop.

Note: RTP mixers or translators that operate in such a manner that they
terminate or split the ECN control loop will take on the role of
receivers or senders. This is further discussed in Section 3.2.


Section 3.2:
I gotten a comment that it was unclear what was meant with "all known
receivers" in the following text:

>From Topo-Multicast:

      Accordingly, we allow ECN to be used
      by an RTP sender using multicast UDP provided the sender has
      verified that the paths to all its known receivers support ECN,
      and irrespective of whether the paths from other senders to their
      receivers support ECN.

The proposal to clarify this is to add after the above sentence:

"all its known receivers" are all the SSRCs that the RTP sender has
received RTP or RTCP from the last five reporting intervals, i.e. they
are not timed out.

Related to the above I have realized that we need to forbid the usage of
Group memebership sampling process as described by RFC2762. Thus I
suggest to add this to 3.2 as a second paragraph:

Due to the need for each RTP sender that intended to use ECN with RTP to
track all participants in the RTP session the sub-sampling of the group
membership as specified by "Sampling of the Group Membership in RTP"
[RFC2762] MUST NOT be used.
	

Section 6.1:
The ecn-capable-rtp attribute is defined as media level attribute.
However the previous text explicitly forbid it to be on session level.
But that blocks the default behavior specified in the SDP RFC 4566:

   The connection ("c=") and attribute ("a=") information in the
   session-level section applies to all the media of that session unless
   overridden by connection information or an attribute of the same name
   in the media description.  For instance, in the example below, each
   media behaves as if it were given a "recvonly" attribute.

OLD text:
 This is a
   media level attribute, which MUST NOT be used at the session level.


NEW text:
This is a media level attribute, thus it is normally included as part of
the media description, but if present at session level the same
configuration applies to all media descriptions.

Section 6.1:
Roni raised this:
1.       In section 6.1 there are these two sentences: "If the
participant lack the functionality they SHALL refuse the media streams
using multicast." and " Participants MUST NOT join such a session unless
they have the capability to receive ECN-marked UDP packets," I am not
sure h ow that o do not understand the ecn-capable-rtp attribute. I
think that they will ignore the attribute and join the session and will
not use ECN.

I propose that we change the text to:

In an RTP session using multicast all participants intending to send RTP
packets needs support setting ECT in the RTP packets, and all
participants receiving needs to have the capability to read ECN values
on incoming packets. Especially the later is important, otherwise no
sender in the multicast session will be able to enable ECN. If a session
is negotiated using offer/answer it is preferable that intended session
participant would be aware of the signalling attributes and if not
capable but ECN for RTP aware SHOULD refuse to join the session. For
intended session participants that are not aware of the ECN for RTP
signalling and simple ignore the signalling attribute the other party in
the offer/answer exchange SHOULD terminate the SIP dialog so that the
participant leaves the session.


Section 6.4:
I have received a comment that it was uncleared when the inclusion of
the ICE option for ECN checks was needed. The proposal is to mandate
both signal when including ICE initiation method.


NEW text:
Section 6.4
This ICE option SHALL be included when the ICE initiation method is
offered or declared in the SDP.


I have also fixed these typos, omissions:

Roni 2: Split the sentence and clarified it:
   Thus, the use of the Extended RTP Profile for RTCP-Based Feedback
   (RTP/AVPF) [RFC4585] or other profile that inherits AVPF's signalling
   rules, MUST be signalled unless timely feedback is not required.  If
   timely feedback is not required it is still RECOMMENDED to used AVPF.

Roni 3: Added a=ice-options:rtp+ecn to both offer and answer

Roni 4A: Section 6.1: "However, using "mode=readonly" also in ASM
sessions is reasonable, unless all senders are required to attempt to
use ECN for the RTP packets they send, in which case the mode needs to
be set to "setread"."

Roni 4B: Section 7.4: The number of ECT packets received plus the number
of CE marked and lost packets should correspond to the number of sent
ECT marked packets unless there is duplication in the network.

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 iesg-secretary@ietf.org  Thu Mar 10 13:20:48 2011
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 93A5F3A691F; Thu, 10 Mar 2011 13:20:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.54
X-Spam-Level: 
X-Spam-Status: No, score=-102.54 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id npV8VdX5YvcF; Thu, 10 Mar 2011 13:20:47 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 30FA03A6ABA; Thu, 10 Mar 2011 13:20:47 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110310212047.16397.87886.idtracker@localhost>
Date: Thu, 10 Mar 2011 13:20:47 -0800
Cc: avtcore chair <avtcore-chairs@tools.ietf.org>, Internet Architecture Board <iab@iab.org>, avtcore mailing list <avt@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [AVTCORE] Protocol Action: 'Application Mechanism for keeping alive the Network	Address Translator (NAT) mappings associated to RTP/RTCP	flows.' to Proposed Standard (draft-ietf-avt-app-rtp-keepalive-10.txt)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Mar 2011 21:20:48 -0000

The IESG has approved the following document:
- 'Application Mechanism for keeping alive the Network Address Translator
   (NAT) mappings associated to RTP/RTCP flows.'
  (draft-ietf-avt-app-rtp-keepalive-10.txt) as a Proposed Standard

This document is the product of the Audio/Video Transport Core
Maintenance Working Group.

The IESG contact persons are Robert Sparks and Gonzalo Camarillo.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-avt-app-rtp-keepalive/




Technical Summary

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


Working Group Summary

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


Document Quality

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


Personnel

  Tom Taylor is Document Shepherd.

From carlberg@g11.org.uk  Thu Mar 10 16:22:22 2011
Return-Path: <carlberg@g11.org.uk>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 188EF3A69B6 for <avt@core3.amsl.com>; Thu, 10 Mar 2011 16:22:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y6OnSilATCuG for <avt@core3.amsl.com>; Thu, 10 Mar 2011 16:22:20 -0800 (PST)
Received: from portland.eukhosting.net (portland.eukhosting.net [92.48.97.5]) by core3.amsl.com (Postfix) with ESMTP id 59B493A6ADF for <avt@ietf.org>; Thu, 10 Mar 2011 16:22:20 -0800 (PST)
Received: from c-76-111-69-4.hsd1.va.comcast.net ([76.111.69.4]:60361 helo=[192.168.0.20]) by portland.eukhosting.net with esmtpa (Exim 4.69) (envelope-from <carlberg@g11.org.uk>) id 1Pxq8Z-0004gr-Me for avt@ietf.org; Fri, 11 Mar 2011 00:23:23 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
From: ken carlberg <carlberg@g11.org.uk>
In-Reply-To: <4D78EF1D.5050104@ericsson.com>
Date: Thu, 10 Mar 2011 19:23:36 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <A006DC10-BADA-4E3B-94AF-B7C6E9700219@g11.org.uk>
References: <4D78EF1D.5050104@ericsson.com>
To: IETF AVTCore WG <avt@ietf.org>
X-Mailer: Apple Mail (2.1082)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - portland.eukhosting.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - g11.org.uk
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: Re: [AVTCORE] Proposed changes to draft-ietf-avtcore-ecn-for-rtp
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 00:22:22 -0000

Hi,

Along these lines, we had an internal discussion concerning a suggested =
change in the first paragraph of Section 7.3.3.  The original text was =
the following:

7.3.3 Response to Congestion Notifications:

    When RTP packets are received with ECN-CE marks, the sender and/or
    receivers MUST react with congestion control as-if those packets had
    been lost.  Depending on the media format, type of session, and RTP
    topology used, there are several different types of congestion
    control that can be used.

the suggested new text is...

    The reception of RTP packets with ECN-CE marks in the IP header are =
a
    notification that congestion is being experience. The default =
reaction
    on the reception of these ECN-CE marked packets MUST be to provide =
the
    congestion control algorithm with notification and that it is =
treated as
    a packet loss would when it comes to indicating congestion.

    We note that there MAY be other reactions to ECN-CE specified in the
    future. Such an alternative reaction MUST be specified and analyzed =
to
    be safe for deployment under any restrictions specified. A potential
    example for an alternative reaction could be emergency =
communications
    (such as that generated by first responders, as opposed to the =
general
    public) in networks where the user has been authorized. A more =
detailed
    description of these other reactions, as well as the types of =
congestion
    control algorithms used by end-nodes, is outside of the scope of =
this
    document.

    Depending on the media format, type of session, and RTP
    topology used, there are several different types of congestion
    control that can be used.

The purpose of the suggested change is two fold.  One is to *explicitly* =
state that the congestion control algorithms are out of scope of the AVT =
draft.  The second suggested change was to continue reinforcing that =
congestion control algorithms MUST be the default action, but also =
recognize that there may be cases where other reactions may exist.  And =
taking this into account, we wanted to constrain and confine this =
possibility.

-ken


From chandu73@gmail.com  Thu Mar 10 23:40:14 2011
Return-Path: <chandu73@gmail.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 219843A6BBC for <avt@core3.amsl.com>; Thu, 10 Mar 2011 23:40:14 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5MaS6zfdd+ZJ for <avt@core3.amsl.com>; Thu, 10 Mar 2011 23:40:11 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 34CB63A6BB0 for <avt@ietf.org>; Thu, 10 Mar 2011 23:40:11 -0800 (PST)
Received: by qwh6 with SMTP id 6so2268131qwh.31 for <avt@ietf.org>; Thu, 10 Mar 2011 23:41:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=0v2xGIAIbLOuFgXq7jYzfN6df5/mib/rZmAwglY6kMM=; b=chm70U+zk3MOjdiFEdG6eFx2Qi7rVMQZv7uYGdaLIKeB/XSbvczVWnJf7W/i5rXBAm G3RD3SHvM36l9VIYZWZ/FlD7U382ozOTHl65ERfXZR2mlGYibZ7E5ceFUIzxln9UC3TH prz8Mi08y01iiuLnaftgb2KeRwyq9XSlWR2MU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=DB+g243C1SLJkhYLgQ3Hqki44IRJYCuhhsXO42tP1f4OiILfRjTVh0RYRkKMi6tgRI Sv+UYofzRZes7Tyf0Q+EP/9lSVWHWMCBXdhLedLALhSkTzNGJe802JXT44ej1Rd+lmp6 H3EZDKEyrN/UCHNeUQq1wTSxDlfBWIyCnZr5s=
MIME-Version: 1.0
Received: by 10.229.40.139 with SMTP id k11mr7294353qce.135.1299829289875; Thu, 10 Mar 2011 23:41:29 -0800 (PST)
Received: by 10.229.236.21 with HTTP; Thu, 10 Mar 2011 23:41:29 -0800 (PST)
Date: Fri, 11 Mar 2011 15:41:29 +0800
Message-ID: <AANLkTinWE7Ojw0cUFeg6UWnCYZg5LUeab3i0C8o+P1OJ@mail.gmail.com>
From: chandu <chandu73@gmail.com>
To: avt@ietf.org
Content-Type: multipart/alternative; boundary=001636834014177a63049e3017d5
Subject: [AVTCORE] Compilation error / UCL Common Library
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 07:53:37 -0000

--001636834014177a63049e3017d5
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

 <avt@ietf.org>Hello Everyone.

I have downloaded UCL Common library (common-1.2.14 Unix) and trying to
compile it on Ubuntu (2.6 kernel) in following way

 $> ./configure
 $> make
 $> su -c =92make install=92


while compiling am coming across some errors, Could any one help me to
solve the issues.


for s in src tests examples  ; do (cd $s && make) || exit 1 ; done
make[1]: Entering directory `/home/official/chandu/common-1.2.14/src'
gcc -g -O2 -W -Wall -Wwrite-strings -Wbad-function-cast
-Wmissing-prototypes -Wcast-qual -Wmissing-declarations -Werror
-DHAVE_CONFIG_H  -c rtp.c
cc1: warnings being treated as errors
rtp.c: In function =91rtp_recv_data=92:
rtp.c:1356: error: pointer targets in passing argument 2 of =91udp_recv=92
differ in signedness
net_udp.h:50: note: expected =91char *=92 but argument is of type =91uint8_=
t *=92
rtp.c:1385: error: pointer targets in assignment differ in signedness
rtp.c: In function =91rtp_recv=92:
rtp.c:1876: error: pointer targets in passing argument 2 of =91udp_recv=92
differ in signedness
net_udp.h:50: note: expected =91char *=92 but argument is of type =91uint8_=
t *=92
rtp.c: In function =91rtp_send_data=92:
rtp.c:2192: error: pointer targets in assignment differ in signedness
rtp.c:2236: error: pointer targets in passing argument 2 of =91udp_send=92
differ in signedness
net_udp.h:51: note: expected =91char *=92 but argument is of type =91uint8_=
t *=92
rtp.c: In function =91rtp_send_data_iov=92:
rtp.c:2277: error: pointer targets in assignment differ in signedness
rtp.c: In function =91send_rtcp=92:
rtp.c:2671: error: pointer targets in passing argument 2 of =91udp_send=92
differ in signedness
net_udp.h:51: note: expected =91char *=92 but argument is of type =91uint8_=
t *=92
rtp.c: In function =91rtp_send_bye_now=92:
rtp.c:2859: error: pointer targets in passing argument 2 of =91udp_send=92
differ in signedness
net_udp.h:51: note: expected =91char *=92 but argument is of type =91uint8_=
t *=92
rtp.c: In function =91rtp_send_bye=92:
rtp.c:2922: error: pointer targets in passing argument 2 of =91udp_recv=92
differ in signedness
net_udp.h:50: note: expected =91char *=92 but argument is of type =91uint8_=
t *=92
rtp.c: In function =91des_encrypt=92:
rtp.c:3146: error: pointer targets in passing argument 1 of =91qfDES=92
differ in signedness
qfDES.h:31: note: expected =91unsigned char *=92 but argument is of type =
=91char *=92
rtp.c: In function =91des_decrypt=92:
rtp.c:3154: error: pointer targets in passing argument 1 of =91qfDES=92
differ in signedness
qfDES.h:31: note: expected =91unsigned char *=92 but argument is of type =
=91char *=92
make[1]: *** [rtp.o] Error 1
make[1]: Leaving directory `/home/official/chandu/common-1.2.14/src'
make: *** [all-recursive] Error 1


2) Is UCL common library RTP stack compatable  with ATMEL (EVK 1105).
because I want to add the RTP feature to LWIP TCP/IP stack.



--=20
Thanks & Regards
Chandu

--001636834014177a63049e3017d5
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div><font class=3D"Apple-style-span" face=3D"arial, helvetica, clean, sans=
-serif"><span class=3D"Apple-style-span" style=3D"line-height: 16px;"><br><=
/span></font></div>
<div><a href=3D"mailto:avt@ietf.org" target=3D"_blank"></a><font face=3D"ar=
ial, helvetica, clean, sans-serif"><span style=3D"line-height:16px">Hello E=
veryone.</span></font></div><div><font face=3D"arial, helvetica, clean, san=
s-serif"><span style=3D"line-height:16px"><br>


</span></font></div><div><font face=3D"arial, helvetica, clean, sans-serif"=
><span style=3D"line-height:16px">I have downloaded UCL Common library (com=
mon-1.2.14 Unix) and trying to compile it on Ubuntu (2.6 kernel) in followi=
ng way</span></font></div>

<div><font face=3D"arial, helvetica, clean, sans-serif"><span style=3D"line=
-height:16px"><br></span></font></div><div><font face=3D"arial, helvetica, =
clean, sans-serif"><span style=3D"line-height:16px"><span style=3D"color:rg=
b(51, 51, 51);font-family:&#39;Ubuntu Beta&#39;, &#39;Bitstream Vera Sans&#=
39;, &#39;DejaVu Sans&#39;, Tahoma, sans-serif;font-size:12px;line-height:1=
2px"><pre style=3D"margin-top:0px;margin-right:0px;margin-bottom:0px;margin=
-left:0px;padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left=
:0px;border-top-width:0px;border-right-width:0px;border-bottom-width:0px;bo=
rder-left-width:0px;border-style:initial;border-color:initial;font-weight:i=
nherit;font-style:inherit;font-size:12px;line-height:16px;font-family:inher=
it;text-align:left;vertical-align:baseline">
 $&gt; ./configure
 $&gt; make
 $&gt; su -c =92make install=92</pre><pre style=3D"margin-top:0px;margin-ri=
ght:0px;margin-bottom:0px;margin-left:0px;padding-top:0px;padding-right:0px=
;padding-bottom:0px;padding-left:0px;border-top-width:0px;border-right-widt=
h:0px;border-bottom-width:0px;border-left-width:0px;border-style:initial;bo=
rder-color:initial;font-weight:inherit;font-style:inherit;font-size:12px;li=
ne-height:16px;font-family:inherit;text-align:left;vertical-align:baseline"=
>
<span style=3D"line-height:12px;white-space:normal"><pre style=3D"margin-to=
p:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;padding-top:0px;pa=
dding-right:0px;padding-bottom:0px;padding-left:0px;border-top-width:0px;bo=
rder-right-width:0px;border-bottom-width:0px;border-left-width:0px;border-s=
tyle:initial;border-color:initial;font-weight:inherit;font-style:inherit;fo=
nt-size:12px;line-height:16px;font-family:inherit;text-align:left;vertical-=
align:baseline">
 <br></pre><pre style=3D"margin-top:0px;margin-right:0px;margin-bottom:0px;=
margin-left:0px;padding-top:0px;padding-right:0px;padding-bottom:0px;paddin=
g-left:0px;border-top-width:0px;border-right-width:0px;border-bottom-width:=
0px;border-left-width:0px;border-style:initial;border-color:initial;font-we=
ight:inherit;font-style:inherit;font-size:12px;line-height:16px;font-family=
:inherit;text-align:left;vertical-align:baseline">
while compiling am coming across some errors, Could any one help me to solv=
e the issues.</pre><pre style=3D"margin-top:0px;margin-right:0px;margin-bot=
tom:0px;margin-left:0px;padding-top:0px;padding-right:0px;padding-bottom:0p=
x;padding-left:0px;border-top-width:0px;border-right-width:0px;border-botto=
m-width:0px;border-left-width:0px;border-style:initial;border-color:initial=
;font-weight:inherit;font-style:inherit;font-size:12px;line-height:16px;fon=
t-family:inherit;text-align:left;vertical-align:baseline">
<br></pre><pre style=3D"margin-top:0px;margin-right:0px;margin-bottom:0px;m=
argin-left:0px;padding-top:0px;padding-right:0px;padding-bottom:0px;padding=
-left:0px;border-top-width:0px;border-right-width:0px;border-bottom-width:0=
px;border-left-width:0px;border-style:initial;border-color:initial;font-wei=
ght:inherit;font-style:inherit;font-size:12px;line-height:16px;font-family:=
inherit;text-align:left;vertical-align:baseline">
<span class=3D"Apple-style-span" style=3D"border-collapse: collapse; font-f=
amily: arial, sans-serif; font-size: 13px; color: rgb(0, 0, 0); line-height=
: normal; white-space: normal; ">for s in src tests examples=A0 ; do (cd $s=
 &amp;&amp; make) || exit 1 ; done<br>
make[1]: Entering directory `/home/official/chandu/common-1.2.14/src&#39;<b=
r>gcc -g -O2 -W -Wall -Wwrite-strings -Wbad-function-cast -Wmissing-prototy=
pes -Wcast-qual -Wmissing-declarations -Werror -DHAVE_CONFIG_H=A0 -c rtp.c<=
br>
cc1: warnings being treated as errors<br>rtp.c: In function =91rtp_recv_dat=
a=92:<br>rtp.c:1356: error: pointer targets in passing argument 2 of =91udp=
_recv=92 differ in signedness<br>net_udp.h:50: note: expected =91char *=92 =
but argument is of type =91uint8_t *=92<br>
rtp.c:1385: error: pointer targets in assignment differ in signedness<br>rt=
p.c: In function =91rtp_recv=92:<br>rtp.c:1876: error: pointer targets in p=
assing argument 2 of =91udp_recv=92 differ in signedness<br>net_udp.h:50: n=
ote: expected =91char *=92 but argument is of type =91uint8_t *=92<br>
rtp.c: In function =91rtp_send_data=92:<br>rtp.c:2192: error: pointer targe=
ts in assignment differ in signedness<br>rtp.c:2236: error: pointer targets=
 in passing argument 2 of =91udp_send=92 differ in signedness<br>net_udp.h:=
51: note: expected =91char *=92 but argument is of type =91uint8_t *=92<br>
rtp.c: In function =91rtp_send_data_iov=92:<br>rtp.c:2277: error: pointer t=
argets in assignment differ in signedness<br>rtp.c: In function =91send_rtc=
p=92:<br>rtp.c:2671: error: pointer targets in passing argument 2 of =91udp=
_send=92 differ in signedness<br>
net_udp.h:51: note: expected =91char *=92 but argument is of type =91uint8_=
t *=92<br>rtp.c: In function =91rtp_send_bye_now=92:<br>rtp.c:2859: error: =
pointer targets in passing argument 2 of =91udp_send=92 differ in signednes=
s<br>net_udp.h:51: note: expected =91char *=92 but argument is of type =91u=
int8_t *=92<br>
rtp.c: In function =91rtp_send_bye=92:<br>rtp.c:2922: error: pointer target=
s in passing argument 2 of =91udp_recv=92 differ in signedness<br>net_udp.h=
:50: note: expected =91char *=92 but argument is of type =91uint8_t *=92<br=
>rtp.c: In function =91des_encrypt=92:<br>
rtp.c:3146: error: pointer targets in passing argument 1 of =91qfDES=92 dif=
fer in signedness<br>qfDES.h:31: note: expected =91unsigned char *=92 but a=
rgument is of type =91char *=92<br>rtp.c: In function =91des_decrypt=92:<br=
>rtp.c:3154: error: pointer targets in passing argument 1 of =91qfDES=92 di=
ffer in signedness<br>
qfDES.h:31: note: expected =91unsigned char *=92 but argument is of type =
=91char *=92<br>make[1]: *** [rtp.o] Error 1<br>make[1]: Leaving directory =
`/home/official/chandu/common-1.2.14/src&#39;<br>make: *** [all-recursive] =
Error 1<br>
</span></pre></span></pre></span></span></font></div>
<div><font face=3D"arial, helvetica, clean, sans-serif"><span style=3D"line=
-height:16px"><br></span></font></div><div><font face=3D"arial, helvetica, =
clean, sans-serif"><span style=3D"line-height:16px">2) Is UCL common librar=
y RTP stack compatable =A0with ATMEL (EVK 1105).
</span></font></div><div><font face=3D"arial, helvetica, clean, sans-serif"=
><span style=3D"line-height:16px">because I want to add the RTP feature to =
LWIP TCP/IP stack.</span></font></div>
<div><font face=3D"arial, helvetica, clean, sans-serif"><span style=3D"line=
-height:16px"><br></span></font></div>
<div><font face=3D"arial, helvetica, clean, sans-serif"><span style=3D"line=
-height:16px"><br></span></font></div>
<div><br>-- <br><div>Thanks &amp; Regards</div>
<div>Chandu</div><br>
</div>

--001636834014177a63049e3017d5--

From harald@alvestrand.no  Fri Mar 11 02:50:34 2011
Return-Path: <harald@alvestrand.no>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CF8823A6989 for <avt@core3.amsl.com>; Fri, 11 Mar 2011 02:50: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=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sW6v3UFrCqLX for <avt@core3.amsl.com>; Fri, 11 Mar 2011 02:50:33 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by core3.amsl.com (Postfix) with ESMTP id E159C3A68AA for <avt@ietf.org>; Fri, 11 Mar 2011 02:50:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id C276139E0D4; Fri, 11 Mar 2011 11:51:13 +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 pspqjj-4jMcd; Fri, 11 Mar 2011 11:51: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 F318B39E082; Fri, 11 Mar 2011 11:51:12 +0100 (CET)
Message-ID: <4D79FEC3.9060204@alvestrand.no>
Date: Fri, 11 Mar 2011 11:51:47 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <11120238-4159-4BA7-B150-0B28E86651B3@cisco.com>	<4D7798A9.7080006@omnitor.se> <4D779F79.8090001@ericsson.com>
In-Reply-To: <4D779F79.8090001@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: avt@ietf.org
Subject: Re: [AVTCORE] SSRC multiplexing of RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 10:50:34 -0000

On 03/09/11 16:40, Magnus Westerlund wrote:
> Hi Gunnar,
>
> Gunnar Hellstr=F6m skrev 2011-03-09 16:11:
>> Cullen
>>
>> I agree. I have also got negative feedback on SSRC multiplexing.
>>
>> I had it described in the draft for multi-party handling of real-time
>> text in draft-hellstrom-text-conference-02.txt
>> in order to easily separate the streams from different sources and
>> display them in a way that the receiver decides.
>>
>> But the feedback was that many RTP implementations would just regard i=
t
>> to be an error if a new SSRC appeared in the session and it would caus=
e
>> problems.
> Well, this is how you are supposed to use cases when you have multiple
> sources. And text chat is case when implementations can't really say
> that they don't have the rendering capabilities for it. But I do
> understand that most implementations sucks at handling multiple SSRCs
> which is very bad.
>
> My hope is that we will see a bit of signalling support for handling
> multiple SSRCs as part of the CLUE work. But, we do need to push that
> support for multiple SSRCs, it needs to be in the stacks.
Seems to me that since this isn't clear from current specs, there needs=20
to be a specification of what a new SSRC appearing in a session means,=20
possibly agreed to at call setup time, and if both renumbering and=20
multiple streams are to be supported:

- if it is a new stream, how to tell that it's a new stream
- if it is an old stream, renumbered, how to tell what the old stream was=


This will certainly be an RTCWEB discussion item, so I'm happy to see=20
AVTCORE pick it up to be worked on.
>> SSRC multiplexing also has some trickiness in that when a new SSRC
>> appears in the session, it can either be an old stream that changed SS=
RC
>> or a new multiplexed stream. RFC 3550 mentions ways to handle that but=

>> there is a risk for losing initial packets before it is sorted out.
>> Losing initial packets in e.g. a video stream can be fatal for the
>> possibility to start proper decoding rapidly.
> I guess clarifications should be in place here. And your strategy for
> handling it will depend a lot of what application it is and which media=

> one talks about.
>
>> Taking the consequences of this, I am just about to submit a modified
>> draft for the real-time text case using one stream and marking the
>> source by CSRC per packet.
>> It will survive through most existing RTP implementations.
>>
> So your going with a mixer design, despite that for text it isn't reall=
y
> needed. I think it is unfortunate, but I guess pragmatic due to poor
> implementation support.
>
> A question to implementors:
>
> Have you tried running the tests documented in RTP testing strategies?
> http://www.rfc-editor.org/rfc/rfc3158.txt
>
> These are excellent tests to check that ones implementation handles wha=
t
> it needs to.
>
> 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
>



From Internet-Drafts@ietf.org  Sun Mar 13 16:00:05 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C5A53A6B98; Sun, 13 Mar 2011 16:00:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.565
X-Spam-Level: 
X-Spam-Status: No, score=-102.565 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G9XiNLbyVEcf; Sun, 13 Mar 2011 16:00:02 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 850DA3A68AB; Sun, 13 Mar 2011 16:00:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110313230002.23225.98535.idtracker@localhost>
Date: Sun, 13 Mar 2011 16:00:02 -0700
Cc: avt@ietf.org
Subject: [AVTCORE] I-D Action:draft-ietf-avtcore-ports-for-ucast-mcast-rtp-01.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Mar 2011 23:00:06 -0000

--NextPart

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


	Title           : Port Mapping Between Unicast and Multicast RTP Sessions
	Author(s)       : A. Begen, et al.
	Filename        : draft-ietf-avtcore-ports-for-ucast-mcast-rtp-01.txt
	Pages           : 36
	Date            : 2011-03-13

This document presents a port mapping solution that allows RTP
receivers to choose their own ports for an auxiliary unicast session
in RTP applications using both unicast and multicast services.  The
solution provides protection against denial-of-service or packet
amplification attacks that could be used to cause one or more RTP
packets to be sent to a victim client.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avtcore-ports-for-ucast-mcast-rtp-01.txt

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

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

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

Content-Type: text/plain
Content-ID: <2011-03-13155210.I-D@ietf.org>


--NextPart--

From Internet-Drafts@ietf.org  Mon Mar 14 09:15:05 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 64E5B3A6DF4; Mon, 14 Mar 2011 09:15:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1lmvA1qVKS23; Mon, 14 Mar 2011 09:15:03 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B76133A6DF5; Mon, 14 Mar 2011 09:15:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110314161501.21193.44542.idtracker@localhost>
Date: Mon, 14 Mar 2011 09:15:01 -0700
Cc: avt@ietf.org
Subject: [AVTCORE] I-D Action:draft-ietf-avtcore-ecn-for-rtp-01.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2011 16:15:05 -0000

--NextPart

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


	Title           : Explicit Congestion Notification (ECN) for RTP over UDP
	Author(s)       : M. Westerlund, et al.
	Filename        : draft-ietf-avtcore-ecn-for-rtp-01.txt
	Pages           : 54
	Date            : 2011-03-14

This document specifies how explicit congestion notification (ECN)
can be used with Real-time Transport Protocol (RTP) over UDP flows
that use RTP Control Protocol (RTCP) as feedback mechanism.  It
defines one RTP Control Protocol Extended Reports (RTCP XR) extension
for ECN summary, a RTCP transport feedback format for timely
reporting of congestion events, and an Session Traversal Utilities
for NAT (STUN) extension used in the optional initilization method
using Interactive Connectivity Establishment (ICE).  Signalling and
procedures for negotiation of capabilities and initilization methods
are also defined.

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

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

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

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

Content-Type: text/plain
Content-ID: <2011-03-14090559.I-D@ietf.org>


--NextPart--

From magnus.westerlund@ericsson.com  Mon Mar 14 09:16:11 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2362A3A6DB8 for <avt@core3.amsl.com>; Mon, 14 Mar 2011 09:16:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.49
X-Spam-Level: 
X-Spam-Status: No, score=-106.49 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l9Oe4psTN+yQ for <avt@core3.amsl.com>; Mon, 14 Mar 2011 09:16:10 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 0E9703A6972 for <avt@ietf.org>; Mon, 14 Mar 2011 09:16:09 -0700 (PDT)
X-AuditID: c1b4fb3d-b7bbbae000005311-ef-4d7e3f9cc0c2
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 19.DE.21265.C9F3E7D4; Mon, 14 Mar 2011 17:17:33 +0100 (CET)
Received: from [147.214.183.8] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.2.234.1; Mon, 14 Mar 2011 17:17:32 +0100
Message-ID: <4D7E3F9C.4010505@ericsson.com>
Date: Mon, 14 Mar 2011 17:17:32 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Harald Alvestrand <harald@alvestrand.no>
References: <11120238-4159-4BA7-B150-0B28E86651B3@cisco.com>	<4D7798A9.7080006@omnitor.se> <4D779F79.8090001@ericsson.com> <4D79FEC3.9060204@alvestrand.no>
In-Reply-To: <4D79FEC3.9060204@alvestrand.no>
X-Enigmail-Version: 1.1.1
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] SSRC multiplexing of RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2011 16:16:11 -0000

Harald Alvestrand skrev 2011-03-11 11:51:
> On 03/09/11 16:40, Magnus Westerlund wrote:
>> Hi Gunnar,
>>
>> Gunnar Hellström skrev 2011-03-09 16:11:
>>> Cullen
>>>
>>> I agree. I have also got negative feedback on SSRC multiplexing.
>>>
>>> I had it described in the draft for multi-party handling of real-time
>>> text in draft-hellstrom-text-conference-02.txt
>>> in order to easily separate the streams from different sources and
>>> display them in a way that the receiver decides.
>>>
>>> But the feedback was that many RTP implementations would just regard it
>>> to be an error if a new SSRC appeared in the session and it would cause
>>> problems.
>> Well, this is how you are supposed to use cases when you have multiple
>> sources. And text chat is case when implementations can't really say
>> that they don't have the rendering capabilities for it. But I do
>> understand that most implementations sucks at handling multiple SSRCs
>> which is very bad.
>>
>> My hope is that we will see a bit of signalling support for handling
>> multiple SSRCs as part of the CLUE work. But, we do need to push that
>> support for multiple SSRCs, it needs to be in the stacks.

> Seems to me that since this isn't clear from current specs, there needs 
> to be a specification of what a new SSRC appearing in a session means, 
> possibly agreed to at call setup time, and if both renumbering and 
> multiple streams are to be supported:
> 
> - if it is a new stream, how to tell that it's a new stream
> - if it is an old stream, renumbered, how to tell what the old stream was

I don't think the specs are that unclear on what is what. You do need
the CNAME to determine which case it is. Sure it can be clarified. I
mostly think the issue is with the state of the implementations. They
haven't considered the implications and need for multiple SSRC support.

> 
> This will certainly be an RTCWEB discussion item, so I'm happy to see 
> AVTCORE pick it up to be worked on.

Lets figure out what is considered the issues here.

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  Mon Mar 14 09:42:28 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 49AA33A69F9 for <avt@core3.amsl.com>; Mon, 14 Mar 2011 09:42:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.494
X-Spam-Level: 
X-Spam-Status: No, score=-106.494 tagged_above=-999 required=5 tests=[AWL=0.105, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RGA1N6e7dpwr for <avt@core3.amsl.com>; Mon, 14 Mar 2011 09:42:26 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 58A8D3A69BC for <avt@ietf.org>; Mon, 14 Mar 2011 09:42:25 -0700 (PDT)
X-AuditID: c1b4fb3d-b7bbbae000005311-1b-4d7e45c48bfa
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 69.A1.21265.4C54E7D4; Mon, 14 Mar 2011 17:43:48 +0100 (CET)
Received: from [147.214.183.8] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.2.234.1; Mon, 14 Mar 2011 17:43:48 +0100
Message-ID: <4D7E45C4.2010400@ericsson.com>
Date: Mon, 14 Mar 2011 17:43:48 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: IETF AVTCore WG <avt@ietf.org>
References: <20110314161501.21193.44542.idtracker@localhost>
In-Reply-To: <20110314161501.21193.44542.idtracker@localhost>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [AVTCORE] I-D Action:draft-ietf-avtcore-ecn-for-rtp-01.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2011 16:42:28 -0000

This implements the changes discussed last week. It also includes Ken's
proposal.

Diff:
http://tools.ietf.org/rfcdiff?url2=draft-ietf-avtcore-ecn-for-rtp-01

Cheers

Magnus

Internet-Drafts@ietf.org skrev 2011-03-14 17:15:
> 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           : Explicit Congestion Notification (ECN) for RTP over UDP
> 	Author(s)       : M. Westerlund, et al.
> 	Filename        : draft-ietf-avtcore-ecn-for-rtp-01.txt
> 	Pages           : 54
> 	Date            : 2011-03-14
> 
> This document specifies how explicit congestion notification (ECN)
> can be used with Real-time Transport Protocol (RTP) over UDP flows
> that use RTP Control Protocol (RTCP) as feedback mechanism.  It
> defines one RTP Control Protocol Extended Reports (RTCP XR) extension
> for ECN summary, a RTCP transport feedback format for timely
> reporting of congestion events, and an Session Traversal Utilities
> for NAT (STUN) extension used in the optional initilization method
> using Interactive Connectivity Establishment (ICE).  Signalling and
> procedures for negotiation of capabilities and initilization methods
> are also defined.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-ecn-for-rtp-01.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.


-- 

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 lennox@cs.columbia.edu  Mon Mar 14 10:13:36 2011
Return-Path: <lennox@cs.columbia.edu>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 000673A6D78 for <avt@core3.amsl.com>; Mon, 14 Mar 2011 10:13:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gjT96gDFAGKp for <avt@core3.amsl.com>; Mon, 14 Mar 2011 10:13:34 -0700 (PDT)
Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by core3.amsl.com (Postfix) with ESMTP id 6D82B3A6973 for <avt@ietf.org>; Mon, 14 Mar 2011 10:13:34 -0700 (PDT)
Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) by mail1.panix.com (Postfix) with ESMTP id ECA051F08B; Mon, 14 Mar 2011 13:14:57 -0400 (EDT)
Received: from amman.clic.cs.columbia.edu (amman.clic.cs.columbia.edu [128.59.15.55]) by mailbackend.panix.com (Postfix) with ESMTP id 81B00328D3; Mon, 14 Mar 2011 13:14:57 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <19838.19728.906691.771074@amman.clic.cs.columbia.edu>
Date: Mon, 14 Mar 2011 13:14:56 -0400
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
In-Reply-To: <4D7E3F9C.4010505@ericsson.com>
References: <11120238-4159-4BA7-B150-0B28E86651B3@cisco.com> <4D7798A9.7080006@omnitor.se> <4D779F79.8090001@ericsson.com> <4D79FEC3.9060204@alvestrand.no> <4D7E3F9C.4010505@ericsson.com>
X-Mailer: VM 7.19 under Emacs 22.2.1
From: lennox@cs.columbia.edu
Cc: Harald Alvestrand <harald@alvestrand.no>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] SSRC multiplexing of RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2011 17:13:36 -0000

On Monday, March 14 2011, "Magnus Westerlund" wrote to "Harald Alvestrand, avt@ietf.org" saying:

> > - if it is a new stream, how to tell that it's a new stream
> > - if it is an old stream, renumbered, how to tell what the old stream was
> 
> I don't think the specs are that unclear on what is what. You do need
> the CNAME to determine which case it is. Sure it can be clarified. I
> mostly think the issue is with the state of the implementations. They
> haven't considered the implications and need for multiple SSRC support.

There are valid cases where multiple independent streams will have the same
CNAME -- if they're multiple sources from the same participant.  Multiple
video streams in the Telepresence/CLUE environment are probably the current
most prominent example of this, but generally, this will be the case if you
have multiple streams that all need to be synchronized together.

-- 
Jonathan Lennox
lennox@cs.columbia.edu

From abegen@cisco.com  Mon Mar 14 10:29:40 2011
Return-Path: <abegen@cisco.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8991A3A6D9D for <avt@core3.amsl.com>; Mon, 14 Mar 2011 10:29:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.551
X-Spam-Level: 
X-Spam-Status: No, score=-10.551 tagged_above=-999 required=5 tests=[AWL=0.048, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Or-HUlQhpchS for <avt@core3.amsl.com>; Mon, 14 Mar 2011 10:29:38 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 213A93A6D6C for <avt@ietf.org>; Mon, 14 Mar 2011 10:29:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=abegen@cisco.com; l=1677; q=dns/txt; s=iport; t=1300123862; x=1301333462; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=njZbNleHkq/O2MJRS6ygGnpINLBr2za+MFFYKiONv6Y=; b=KwYOp1xlIA/Q4QxWZtqHZ1qGzA0WaIIjC3B95NUZNztZB5nyQvL51s+6 u28K63Q4gCiLnsxCbhD7zwsMjGV43gIDmCpcAVbH8RaEaU5oC6ky7vVmm TAAonHqVj5dlfevnys/RuMxjrnwCGsysUKkLjaS4A99FmToCnJk8HqMBF o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvEAAO7tfU2tJXG//2dsb2JhbACYRI1Gd6QTnBmFYgSFK4p7iGs
X-IronPort-AV: E=Sophos;i="4.62,316,1297036800"; d="scan'208";a="276280646"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by sj-iport-4.cisco.com with ESMTP; 14 Mar 2011 17:31:00 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by rcdn-core2-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2EHUnCB010732;  Mon, 14 Mar 2011 17:31:00 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);  Mon, 14 Mar 2011 10:31:00 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 14 Mar 2011 10:30:15 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540E8ABC69@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <19838.19728.906691.771074@amman.clic.cs.columbia.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVTCORE] SSRC multiplexing of RTP
Thread-Index: Acvia2JwdIeHzSkvRqSTMP12iiJvRwAAVeIw
References: <11120238-4159-4BA7-B150-0B28E86651B3@cisco.com><4D7798A9.7080006@omnitor.se> <4D779F79.8090001@ericsson.com><4D79FEC3.9060204@alvestrand.no> <4D7E3F9C.4010505@ericsson.com> <19838.19728.906691.771074@amman.clic.cs.columbia.edu>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: <lennox@cs.columbia.edu>, "Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-OriginalArrivalTime: 14 Mar 2011 17:31:00.0074 (UTC) FILETIME=[95AE6CA0:01CBE26D]
Cc: Harald Alvestrand <harald@alvestrand.no>, avt@ietf.org
Subject: Re: [AVTCORE] SSRC multiplexing of RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2011 17:29:40 -0000

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of =
lennox@cs.columbia.edu
> Sent: Monday, March 14, 2011 1:15 PM
> To: Magnus Westerlund
> Cc: Harald Alvestrand; avt@ietf.org
> Subject: Re: [AVTCORE] SSRC multiplexing of RTP
>=20
> On Monday, March 14 2011, "Magnus Westerlund" wrote to "Harald =
Alvestrand, avt@ietf.org" saying:
>=20
> > > - if it is a new stream, how to tell that it's a new stream
> > > - if it is an old stream, renumbered, how to tell what the old =
stream was
> >
> > I don't think the specs are that unclear on what is what. You do =
need
> > the CNAME to determine which case it is. Sure it can be clarified. I
> > mostly think the issue is with the state of the implementations. =
They
> > haven't considered the implications and need for multiple SSRC =
support.
>=20
> There are valid cases where multiple independent streams will have the =
same
> CNAME -- if they're multiple sources from the same participant.  =
Multiple
> video streams in the Telepresence/CLUE environment are probably the =
current
> most prominent example of this, but generally, this will be the case =
if you
> have multiple streams that all need to be synchronized together.

CNAME would be used to relate a source stream with its FEC stream as =
well. The cname guidelines document is a useful read:
http://tools.ietf.org/html/draft-ietf-avt-rtp-cnames-05

-acbegen
=20
> --
> Jonathan Lennox
> lennox@cs.columbia.edu
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt

From Internet-Drafts@ietf.org  Mon Mar 14 13:15:06 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A246A3A6EA0; Mon, 14 Mar 2011 13:15:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o2UH5Mo9trWw; Mon, 14 Mar 2011 13:15:05 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C33053A6E86; Mon, 14 Mar 2011 13:15:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110314201502.20551.81627.idtracker@localhost>
Date: Mon, 14 Mar 2011 13:15:02 -0700
Cc: avt@ietf.org
Subject: [AVTCORE] I-D Action:draft-ietf-avt-srtp-ekt-02.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2011 20:15:07 -0000

--NextPart

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


	Title           : Encrypted Key Transport for Secure RTP
	Author(s)       : D. McGrew, et al.
	Filename        : draft-ietf-avt-srtp-ekt-02.txt
	Pages           : 52
	Date            : 2011-03-14

SRTP Encrypted Key Transport (EKT) is an extension to SRTP that
provides for the secure transport of SRTP master keys, Rollover
Counters, and other information, within SRTP or SRTCP.  This facility
enables SRTP to work for decentralized conferences with minimal
control, and to handle situations caused by early media.

This note defines EKT, and also describes how to use it with SDP
Security Descriptions, DTLS-SRTP, and MIKEY.  These other key
management protocols provide an EKT key to everyone in a session, and
EKT coordinates the keys within the session.

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

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

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

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

Content-Type: text/plain
Content-ID: <2011-03-14131405.I-D@ietf.org>


--NextPart--

From vsingh.ietf@gmail.com  Mon Mar 14 14:56:08 2011
Return-Path: <vsingh.ietf@gmail.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C7DAD3A6BCD for <avt@core3.amsl.com>; Mon, 14 Mar 2011 14:56:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.574
X-Spam-Level: 
X-Spam-Status: No, score=-3.574 tagged_above=-999 required=5 tests=[AWL=0.025,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fHvGwbnp8iPy for <avt@core3.amsl.com>; Mon, 14 Mar 2011 14:56:06 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 911943A6BBA for <avt@ietf.org>; Mon, 14 Mar 2011 14:56:06 -0700 (PDT)
Received: by fxm15 with SMTP id 15so3742188fxm.31 for <avt@ietf.org>; Mon, 14 Mar 2011 14:57:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:from:date:message-id:subject:to :content-type; bh=ZO7HuV7fbBd6E4reLSLgo6MaSgSqXvZUfZJzAuQ31aU=; b=MPlOVWFw61pGy2Ka86O5fmeHXqf6Un3S5h+4aBsciUEihshJUcnuMvNiW3RnackEDt wqzCLuuEeq/J3R9plixf2/wQvfn5e278Cfci6KIi8LMMcNF+0qXCuTs+BSgMUiTn+XY+ jeejGwb5d10ZrqAAEKXOmXH86rvYfA1pQBKrI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=H4iEMHRJiNYeQ85D8ci3LCOJP73nQ9Q377AI3ySWq3AHbuobSPNl/w/nPOhWwK5b+s vnBRIkrS09jqWJBmlGIHsEh5IauGIElDjnEdl1Q8K6KJCFHGtjfrUoLkJsPOxTkepvSw LjVrskpBPie/sfKQ1xTId3yyi+iSkh8B/6siQ=
Received: by 10.223.58.80 with SMTP id f16mr1403009fah.148.1300139850065; Mon, 14 Mar 2011 14:57:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.104.211 with HTTP; Mon, 14 Mar 2011 14:57:10 -0700 (PDT)
From: varun singh <vsingh.ietf@gmail.com>
Date: Mon, 14 Mar 2011 23:57:10 +0200
Message-ID: <AANLkTimiOb29PRXVfDjVp5=Bt2L4hQ_FXychLbCdboaT@mail.gmail.com>
To: avt@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [AVTCORE] New Packet formats section in Multipath RTP (draft-singh-avtcore-mprtp-01)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2011 21:56:08 -0000

Greetings,

We have updated the draft and the latest iteration contains an updated
section on Packet Formats (Section 9). In Section 9.3.1, we define a
generic mechanism to reuse the session level reports (e.g., SR, RR,
XR) for subflow-specific reports. An example non-compound subflow
MPRTCP is shown in Figure 12.

For exact changes see
http://tools.ietf.org/rfcdiff?url2=draft-singh-avtcore-mprtp-01.txt.

The draft contains some open issues (and some recommendations) that
should be discussed here on the mailing so that we can move ahead and
close them.

Regards,
Varun

Begin forwarded message:

A new version of I-D, draft-singh-avtcore-mprtp-01.txt has been
successfully submitted by Varun Singh and posted to the IETF
repository.

Filename:	 draft-singh-avtcore-mprtp
Revision:	 01
Title:		 Multipath RTP (MPRTP)
Creation_date:	 2011-03-14
WG ID:		 Independent Submission
Number_of_pages: 29

Abstract:
The Real-time Transport Protocol (RTP) is used to deliver real-time
content and, along with the RTP Control Protocol (RTCP), forms the
control channel between the sender and receiver.  However, RTP and
RTCP assume a single delivery path between the sender and receiver
and make decisions based on the measured characteristics of this
single path.  Increasingly, endpoints are becoming multi-homed, which
means that they are connected via multiple Internet paths.  Network
utilization can be improved when endpoints use multiple parallel
paths for communication.  The resulting increase in reliability and
throughput can also enhance the user experience.  This document
extends the Real-time Transport Protocol (RTP) so that a single
session can take advantage of the availability of multiple paths
between two endpoints.



The IETF Secretariat.


Varun Singh
http://www.netlab.tkk.fi/~varun

From gunnar.hellstrom@omnitor.se  Mon Mar 14 16:13:06 2011
Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AE0933A6BAE for <avt@core3.amsl.com>; Mon, 14 Mar 2011 16:13:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.728
X-Spam-Level: 
X-Spam-Status: No, score=-2.728 tagged_above=-999 required=5 tests=[AWL=-0.429, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id muHB4fPf1iIC for <avt@core3.amsl.com>; Mon, 14 Mar 2011 16:13:06 -0700 (PDT)
Received: from vsp-outgoing1.binero.net (vsp-outgoing1.binero.net [193.17.218.160]) by core3.amsl.com (Postfix) with SMTP id 796873A697A for <avt@ietf.org>; Mon, 14 Mar 2011 16:13:05 -0700 (PDT)
Received: from smtp01.binero.se (unknown [195.74.39.229]) by vsp-outgoing1.binero.net (Halon Mail Gateway) with ESMTP for <avt@ietf.org>; Tue, 15 Mar 2011 00:14:19 +0100 (CET)
Received: from [192.168.50.31] (h225n1fls32o933.telia.com [213.67.165.225]) by smtp-08-01.atm.binero.net (Postfix) with ESMTPA id EE4243A276 for <avt@ietf.org>; Tue, 15 Mar 2011 00:14:17 +0100 (CET)
Message-ID: <4D7EA149.50005@omnitor.se>
Date: Tue, 15 Mar 2011 00:14:17 +0100
From: =?ISO-8859-1?Q?Gunnar_Hellstr=F6m?= <gunnar.hellstrom@omnitor.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; sv-SE; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: avt@ietf.org
References: <11120238-4159-4BA7-B150-0B28E86651B3@cisco.com><4D7798A9.7080006@omnitor.se>	<4D779F79.8090001@ericsson.com><4D79FEC3.9060204@alvestrand.no>	<4D7E3F9C.4010505@ericsson.com>	<19838.19728.906691.771074@amman.clic.cs.columbia.edu> <04CAD96D4C5A3D48B1919248A8FE0D540E8ABC69@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D540E8ABC69@xmb-sjc-215.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [AVTCORE] SSRC multiplexing of RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2011 23:13:06 -0000

The rtp-cnames document seems to give good advice.

Statements that make me want to stay away from SSRC multiplexing is for 
example what is stated in RFC 3550 RTP
in 6.2.1
  "New sites are added to the count when they are heard, and an entry 
for each SHOULD be created in a table indexed by the SSRC or CSRC 
identifier (see Section 8.2) to keep track of them. New entries MAY be 
considered not valid until multiple packets carrying the new SSRC have 
been received "

If a source is regarded not valid, I see a risk that RTP implementations 
ignore packets from that source.

/Gunnar

Ali C. Begen (abegen) skrev 2011-03-14 18:30:
>
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of lennox@cs.columbia.edu
>> Sent: Monday, March 14, 2011 1:15 PM
>> To: Magnus Westerlund
>> Cc: Harald Alvestrand; avt@ietf.org
>> Subject: Re: [AVTCORE] SSRC multiplexing of RTP
>>
>> On Monday, March 14 2011, "Magnus Westerlund" wrote to "Harald Alvestrand, avt@ietf.org" saying:
>>
>>>> - if it is a new stream, how to tell that it's a new stream
>>>> - if it is an old stream, renumbered, how to tell what the old stream was
>>> I don't think the specs are that unclear on what is what. You do need
>>> the CNAME to determine which case it is. Sure it can be clarified. I
>>> mostly think the issue is with the state of the implementations. They
>>> haven't considered the implications and need for multiple SSRC support.
>> There are valid cases where multiple independent streams will have the same
>> CNAME -- if they're multiple sources from the same participant.  Multiple
>> video streams in the Telepresence/CLUE environment are probably the current
>> most prominent example of this, but generally, this will be the case if you
>> have multiple streams that all need to be synchronized together.
> CNAME would be used to relate a source stream with its FEC stream as well. The cname guidelines document is a useful read:
> http://tools.ietf.org/html/draft-ietf-avt-rtp-cnames-05
>
> -acbegen
>
>> --
>> Jonathan Lennox
>> lennox@cs.columbia.edu
>> _______________________________________________
>> 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 paromitaz@gmail.com  Mon Mar 14 22:37:35 2011
Return-Path: <paromitaz@gmail.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EBCBC3A6A66 for <avt@core3.amsl.com>; Mon, 14 Mar 2011 22:37:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.298
X-Spam-Level: 
X-Spam-Status: No, score=-3.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tTjC7BZN8JHa for <avt@core3.amsl.com>; Mon, 14 Mar 2011 22:37:33 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 2CDF13A68AB for <avt@ietf.org>; Mon, 14 Mar 2011 22:37:33 -0700 (PDT)
Received: by bwz13 with SMTP id 13so277024bwz.31 for <avt@ietf.org>; Mon, 14 Mar 2011 22:38:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=xGBLl4jYgyMkLns87IJP/X1aSO9WXS2odsMg/q1dQEM=; b=sZol+yddyjZKKeUAI+l5hw1QbFZsRyIpMSdCU4B6XnR4/8qsm/k8Z42kwcYxmXrcmK j4UvAN4y+zr5WNYu8T3V9SA+WsQARR6lBgH66EcvTNUhNnIuc7ZujPPj+PeH3FsVYE8P ZWZMcc8MGIehSpqlUSq15R89JOmvlKWviUddE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=IZT30vaPBfKZqVTxeKLhtfeUjKPAnNSaOXLLZyjD/lDnt/+47RnluY+u4ePiqKIg4e sh7iTXVEf9PRRbbKM+7tFNm/AuQLN9AgFebamktaY9T9Hr59+vqFdylcwwZjl6nsJut7 a1GDtDpm/FmOOwkO/vksvlEXo21RVCBo4xpo0=
MIME-Version: 1.0
Received: by 10.204.187.194 with SMTP id cx2mr3202908bkb.167.1300167536841; Mon, 14 Mar 2011 22:38:56 -0700 (PDT)
Received: by 10.204.52.19 with HTTP; Mon, 14 Mar 2011 22:38:56 -0700 (PDT)
In-Reply-To: <4D7EA149.50005@omnitor.se>
References: <11120238-4159-4BA7-B150-0B28E86651B3@cisco.com> <4D7798A9.7080006@omnitor.se> <4D779F79.8090001@ericsson.com> <4D79FEC3.9060204@alvestrand.no> <4D7E3F9C.4010505@ericsson.com> <19838.19728.906691.771074@amman.clic.cs.columbia.edu> <04CAD96D4C5A3D48B1919248A8FE0D540E8ABC69@xmb-sjc-215.amer.cisco.com> <4D7EA149.50005@omnitor.se>
Date: Tue, 15 Mar 2011 11:08:56 +0530
Message-ID: <AANLkTin2gG1eEQfdEvSTXOzjDTNg4_mgGNaDuGqAWCvK@mail.gmail.com>
From: paromita chowdhury <paromitaz@gmail.com>
To: =?ISO-8859-1?Q?Gunnar_Hellstr=F6m?= <gunnar.hellstrom@omnitor.se>
Content-Type: multipart/alternative; boundary=20cf302666a62e9501049e7ed895
Cc: avt@ietf.org
Subject: Re: [AVTCORE] SSRC multiplexing of RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 05:37:36 -0000

--20cf302666a62e9501049e7ed895
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I have a doubt with SSRC multiplexing. When two multiplexed SSRC sessions
appear in a RTP session, do have two separate sequence number series or
share the same. Also in unicast sessions when the receiver receives two suc=
h
sessions what does it considers the two streams as?

-PC

2011/3/15 Gunnar Hellstr=F6m <gunnar.hellstrom@omnitor.se>

> The rtp-cnames document seems to give good advice.
>
> Statements that make me want to stay away from SSRC multiplexing is for
> example what is stated in RFC 3550 RTP
> in 6.2.1
>  "New sites are added to the count when they are heard, and an entry for
> each SHOULD be created in a table indexed by the SSRC or CSRC identifier
> (see Section 8.2) to keep track of them. New entries MAY be considered no=
t
> valid until multiple packets carrying the new SSRC have been received "
>
> If a source is regarded not valid, I see a risk that RTP implementations
> ignore packets from that source.
>
> /Gunnar
>
> Ali C. Begen (abegen) skrev 2011-03-14 18:30:
>
>
>>  -----Original Message-----
>>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
>>> lennox@cs.columbia.edu
>>> Sent: Monday, March 14, 2011 1:15 PM
>>> To: Magnus Westerlund
>>> Cc: Harald Alvestrand; avt@ietf.org
>>> Subject: Re: [AVTCORE] SSRC multiplexing of RTP
>>>
>>> On Monday, March 14 2011, "Magnus Westerlund" wrote to "Harald
>>> Alvestrand, avt@ietf.org" saying:
>>>
>>>  - if it is a new stream, how to tell that it's a new stream
>>>>> - if it is an old stream, renumbered, how to tell what the old stream
>>>>> was
>>>>>
>>>> I don't think the specs are that unclear on what is what. You do need
>>>> the CNAME to determine which case it is. Sure it can be clarified. I
>>>> mostly think the issue is with the state of the implementations. They
>>>> haven't considered the implications and need for multiple SSRC support=
.
>>>>
>>> There are valid cases where multiple independent streams will have the
>>> same
>>> CNAME -- if they're multiple sources from the same participant.  Multip=
le
>>> video streams in the Telepresence/CLUE environment are probably the
>>> current
>>> most prominent example of this, but generally, this will be the case if
>>> you
>>> have multiple streams that all need to be synchronized together.
>>>
>> CNAME would be used to relate a source stream with its FEC stream as wel=
l.
>> The cname guidelines document is a useful read:
>> http://tools.ietf.org/html/draft-ietf-avt-rtp-cnames-05
>>
>> -acbegen
>>
>>  --
>>> Jonathan Lennox
>>> lennox@cs.columbia.edu
>>> _______________________________________________
>>> 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
>>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>

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

I have a doubt with SSRC multiplexing. When two multiplexed SSRC sessions a=
ppear in a RTP session, do have two separate sequence number series or shar=
e the same. Also in unicast sessions when the receiver receives two such se=
ssions what does it considers the two streams as?<br>
<br>-PC<br><br><div class=3D"gmail_quote">2011/3/15 Gunnar Hellstr=F6m <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:gunnar.hellstrom@omnitor.se">gunnar.hel=
lstrom@omnitor.se</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=
=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); p=
adding-left: 1ex;">
The rtp-cnames document seems to give good advice.<br>
<br>
Statements that make me want to stay away from SSRC multiplexing is for exa=
mple what is stated in RFC 3550 RTP<br>
in 6.2.1<br>
=A0&quot;New sites are added to the count when they are heard, and an entry=
 for each SHOULD be created in a table indexed by the SSRC or CSRC identifi=
er (see Section 8.2) to keep track of them. New entries MAY be considered n=
ot valid until multiple packets carrying the new SSRC have been received &q=
uot;<br>

<br>
If a source is regarded not valid, I see a risk that RTP implementations ig=
nore packets from that source.<br>
<br>
/Gunnar<br>
<br>
Ali C. Begen (abegen) skrev 2011-03-14 18:30:<div><div></div><div class=3D"=
h5"><br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
-----Original Message-----<br>
From: <a href=3D"mailto:avt-bounces@ietf.org" target=3D"_blank">avt-bounces=
@ietf.org</a> [mailto:<a href=3D"mailto:avt-bounces@ietf.org" target=3D"_bl=
ank">avt-bounces@ietf.org</a>] On Behalf Of <a href=3D"mailto:lennox@cs.col=
umbia.edu" target=3D"_blank">lennox@cs.columbia.edu</a><br>

Sent: Monday, March 14, 2011 1:15 PM<br>
To: Magnus Westerlund<br>
Cc: Harald Alvestrand; <a href=3D"mailto:avt@ietf.org" target=3D"_blank">av=
t@ietf.org</a><br>
Subject: Re: [AVTCORE] SSRC multiplexing of RTP<br>
<br>
On Monday, March 14 2011, &quot;Magnus Westerlund&quot; wrote to &quot;Hara=
ld Alvestrand, <a href=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.o=
rg</a>&quot; saying:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><blockquote class=
=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid=
 rgb(204, 204, 204); padding-left: 1ex;">

- if it is a new stream, how to tell that it&#39;s a new stream<br>
- if it is an old stream, renumbered, how to tell what the old stream was<b=
r>
</blockquote>
I don&#39;t think the specs are that unclear on what is what. You do need<b=
r>
the CNAME to determine which case it is. Sure it can be clarified. I<br>
mostly think the issue is with the state of the implementations. They<br>
haven&#39;t considered the implications and need for multiple SSRC support.=
<br>
</blockquote>
There are valid cases where multiple independent streams will have the same=
<br>
CNAME -- if they&#39;re multiple sources from the same participant. =A0Mult=
iple<br>
video streams in the Telepresence/CLUE environment are probably the current=
<br>
most prominent example of this, but generally, this will be the case if you=
<br>
have multiple streams that all need to be synchronized together.<br>
</blockquote>
CNAME would be used to relate a source stream with its FEC stream as well. =
The cname guidelines document is a useful read:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-avt-rtp-cnames-05" target=
=3D"_blank">http://tools.ietf.org/html/draft-ietf-avt-rtp-cnames-05</a><br>
<br>
-acbegen<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
--<br>
Jonathan Lennox<br>
<a href=3D"mailto:lennox@cs.columbia.edu" target=3D"_blank">lennox@cs.colum=
bia.edu</a><br>
_______________________________________________<br>
Audio/Video Transport Core Maintenance<br>
<a href=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/avt</a><br>
</blockquote>
_______________________________________________<br>
Audio/Video Transport Core Maintenance<br>
<a href=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/avt</a><br>
</blockquote>
_______________________________________________<br>
Audio/Video Transport Core Maintenance<br>
<a href=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/avt</a><br>
</div></div></blockquote></div><br>

--20cf302666a62e9501049e7ed895--

From gunnar.hellstrom@omnitor.se  Mon Mar 14 23:23:00 2011
Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 71E3E3A6A80 for <avt@core3.amsl.com>; Mon, 14 Mar 2011 23:23:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SIIIrzpXMUJa for <avt@core3.amsl.com>; Mon, 14 Mar 2011 23:22:59 -0700 (PDT)
Received: from vsp-outgoing1.binero.net (vsp-outgoing1.binero.net [193.17.218.160]) by core3.amsl.com (Postfix) with SMTP id 3D96C3A697C for <avt@ietf.org>; Mon, 14 Mar 2011 23:22:57 -0700 (PDT)
Received: from smtp01.binero.se (unknown [195.74.39.229]) by vsp-outgoing1.binero.net (Halon Mail Gateway) with ESMTP for <avt@ietf.org>; Tue, 15 Mar 2011 07:24:12 +0100 (CET)
Received: from [192.168.50.31] (h225n1fls32o933.telia.com [213.67.165.225]) by smtp-03-01.atm.binero.net (Postfix) with ESMTPA id 3B5D53A279; Tue, 15 Mar 2011 07:24:12 +0100 (CET)
Message-ID: <4D7F060E.7090908@omnitor.se>
Date: Tue, 15 Mar 2011 07:24:14 +0100
From: =?ISO-8859-1?Q?Gunnar_Hellstr=F6m?= <gunnar.hellstrom@omnitor.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; sv-SE; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: avt@ietf.org
References: <11120238-4159-4BA7-B150-0B28E86651B3@cisco.com>	<4D7798A9.7080006@omnitor.se>	<4D779F79.8090001@ericsson.com>	<4D79FEC3.9060204@alvestrand.no>	<4D7E3F9C.4010505@ericsson.com>	<19838.19728.906691.771074@amman.clic.cs.columbia.edu>	<04CAD96D4C5A3D48B1919248A8FE0D540E8ABC69@xmb-sjc-215.amer.cisco.com>	<4D7EA149.50005@omnitor.se> <AANLkTin2gG1eEQfdEvSTXOzjDTNg4_mgGNaDuGqAWCvK@mail.gmail.com>
In-Reply-To: <AANLkTin2gG1eEQfdEvSTXOzjDTNg4_mgGNaDuGqAWCvK@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------010905050406020407070507"
Subject: Re: [AVTCORE] SSRC multiplexing of RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 06:23:00 -0000

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

The use is described in RFC 3550 RTP, section 7.1, about RTP Translator, 
that can be used in a conference focus to multiplex media originating 
from a number of sources into one session. We had used it in a draft for 
multi-party conference application of real-time text, because of two 
reasons.
1. Text from different sources can be separated by the receiver and 
displayed in a layout that the receiver controls.
2. RTP Sequence numbers are maintained per SSRC stream, so it is easy to 
detect what stream has been suffering from packet loss and recover that 
stream.

However, because of reactions from implementors, the draft for real-time 
text conferencing has now changed to use an RTP mixer (also see RTP 
section 7.1). It has the same SSRC, but different CSRCs. The mixer only 
has text from one source per packet and mark the packet with the 
contributing CSRC. The final result is that we achieve the same results 
as for the translator with a more widely accepted mechanism.

Gunnar

-----------

paromita chowdhury skrev 2011-03-15 06:38:
> I have a doubt with SSRC multiplexing. When two multiplexed SSRC 
> sessions appear in a RTP session, do have two separate sequence number 
> series or share the same. Also in unicast sessions when the receiver 
> receives two such sessions what does it considers the two streams as?
>
> -PC
>
> 2011/3/15 Gunnar Hellström <gunnar.hellstrom@omnitor.se 
> <mailto:gunnar.hellstrom@omnitor.se>>
>
>     The rtp-cnames document seems to give good advice.
>
>     Statements that make me want to stay away from SSRC multiplexing
>     is for example what is stated in RFC 3550 RTP
>     in 6.2.1
>      "New sites are added to the count when they are heard, and an
>     entry for each SHOULD be created in a table indexed by the SSRC or
>     CSRC identifier (see Section 8.2) to keep track of them. New
>     entries MAY be considered not valid until multiple packets
>     carrying the new SSRC have been received "
>
>     If a source is regarded not valid, I see a risk that RTP
>     implementations ignore packets from that source.
>
>     /Gunnar
>
>     Ali C. Begen (abegen) skrev 2011-03-14 18:30:
>
>
>             -----Original Message-----
>             From: avt-bounces@ietf.org <mailto:avt-bounces@ietf.org>
>             [mailto:avt-bounces@ietf.org
>             <mailto:avt-bounces@ietf.org>] On Behalf Of
>             lennox@cs.columbia.edu <mailto:lennox@cs.columbia.edu>
>             Sent: Monday, March 14, 2011 1:15 PM
>             To: Magnus Westerlund
>             Cc: Harald Alvestrand; avt@ietf.org <mailto:avt@ietf.org>
>             Subject: Re: [AVTCORE] SSRC multiplexing of RTP
>
>             On Monday, March 14 2011, "Magnus Westerlund" wrote to
>             "Harald Alvestrand, avt@ietf.org <mailto:avt@ietf.org>"
>             saying:
>
>                     - if it is a new stream, how to tell that it's a
>                     new stream
>                     - if it is an old stream, renumbered, how to tell
>                     what the old stream was
>
>                 I don't think the specs are that unclear on what is
>                 what. You do need
>                 the CNAME to determine which case it is. Sure it can
>                 be clarified. I
>                 mostly think the issue is with the state of the
>                 implementations. They
>                 haven't considered the implications and need for
>                 multiple SSRC support.
>
>             There are valid cases where multiple independent streams
>             will have the same
>             CNAME -- if they're multiple sources from the same
>             participant.  Multiple
>             video streams in the Telepresence/CLUE environment are
>             probably the current
>             most prominent example of this, but generally, this will
>             be the case if you
>             have multiple streams that all need to be synchronized
>             together.
>
>         CNAME would be used to relate a source stream with its FEC
>         stream as well. The cname guidelines document is a useful read:
>         http://tools.ietf.org/html/draft-ietf-avt-rtp-cnames-05
>
>         -acbegen
>
>             --
>             Jonathan Lennox
>             lennox@cs.columbia.edu <mailto:lennox@cs.columbia.edu>
>             _______________________________________________
>             Audio/Video Transport Core Maintenance
>             avt@ietf.org <mailto:avt@ietf.org>
>             https://www.ietf.org/mailman/listinfo/avt
>
>         _______________________________________________
>         Audio/Video Transport Core Maintenance
>         avt@ietf.org <mailto:avt@ietf.org>
>         https://www.ietf.org/mailman/listinfo/avt
>
>     _______________________________________________
>     Audio/Video Transport Core Maintenance
>     avt@ietf.org <mailto:avt@ietf.org>
>     https://www.ietf.org/mailman/listinfo/avt
>
>

--------------010905050406020407070507
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">
    <title></title>
  </head>
  <body bgcolor="#ffffff" text="#000000">
    The use is described in RFC 3550 RTP, section 7.1, about RTP
    Translator, that can be used in a conference focus to multiplex
    media originating from a number of sources into one session. We had
    used it in a draft for multi-party conference application of
    real-time text, because of two reasons. <br>
    1. Text from different sources can be separated by the receiver and
    displayed in a layout that the receiver controls. <br>
    2. RTP Sequence numbers are maintained per SSRC stream, so it is
    easy to detect what stream has been suffering from packet loss and
    recover that stream. <br>
    <br>
    However, because of reactions from implementors, the draft for
    real-time text conferencing has now changed to use an RTP mixer
    (also see RTP section 7.1). It has the same SSRC, but different
    CSRCs. The mixer only has text from one source per packet and mark
    the packet with the contributing CSRC. The final result is that we
    achieve the same results as for the translator with a more widely
    accepted mechanism.<br>
    <br>
    Gunnar <br>
    &nbsp;<br>
    -----------<br>
    <br>
    paromita chowdhury skrev 2011-03-15 06:38:
    <blockquote
      cite="mid:AANLkTin2gG1eEQfdEvSTXOzjDTNg4_mgGNaDuGqAWCvK@mail.gmail.com"
      type="cite">I have a doubt with SSRC multiplexing. When two
      multiplexed SSRC sessions appear in a RTP session, do have two
      separate sequence number series or share the same. Also in unicast
      sessions when the receiver receives two such sessions what does it
      considers the two streams as?<br>
      <br>
      -PC<br>
      <br>
      <div class="gmail_quote">2011/3/15 Gunnar Hellstr&ouml;m <span
          dir="ltr">&lt;<a moz-do-not-send="true"
            href="mailto:gunnar.hellstrom@omnitor.se">gunnar.hellstrom@omnitor.se</a>&gt;</span><br>
        <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
          0.8ex; border-left: 1px solid rgb(204, 204, 204);
          padding-left: 1ex;">
          The rtp-cnames document seems to give good advice.<br>
          <br>
          Statements that make me want to stay away from SSRC
          multiplexing is for example what is stated in RFC 3550 RTP<br>
          in 6.2.1<br>
          &nbsp;"New sites are added to the count when they are heard, and an
          entry for each SHOULD be created in a table indexed by the
          SSRC or CSRC identifier (see Section 8.2) to keep track of
          them. New entries MAY be considered not valid until multiple
          packets carrying the new SSRC have been received "<br>
          <br>
          If a source is regarded not valid, I see a risk that RTP
          implementations ignore packets from that source.<br>
          <br>
          /Gunnar<br>
          <br>
          Ali C. Begen (abegen) skrev 2011-03-14 18:30:
          <div>
            <div class="h5"><br>
              <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
                0.8ex; border-left: 1px solid rgb(204, 204, 204);
                padding-left: 1ex;">
                <br>
                <blockquote class="gmail_quote" style="margin: 0pt 0pt
                  0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);
                  padding-left: 1ex;">
                  -----Original Message-----<br>
                  From: <a moz-do-not-send="true"
                    href="mailto:avt-bounces@ietf.org" target="_blank">avt-bounces@ietf.org</a>
                  [mailto:<a moz-do-not-send="true"
                    href="mailto:avt-bounces@ietf.org" target="_blank">avt-bounces@ietf.org</a>]
                  On Behalf Of <a moz-do-not-send="true"
                    href="mailto:lennox@cs.columbia.edu" target="_blank">lennox@cs.columbia.edu</a><br>
                  Sent: Monday, March 14, 2011 1:15 PM<br>
                  To: Magnus Westerlund<br>
                  Cc: Harald Alvestrand; <a moz-do-not-send="true"
                    href="mailto:avt@ietf.org" target="_blank">avt@ietf.org</a><br>
                  Subject: Re: [AVTCORE] SSRC multiplexing of RTP<br>
                  <br>
                  On Monday, March 14 2011, "Magnus Westerlund" wrote to
                  "Harald Alvestrand, <a moz-do-not-send="true"
                    href="mailto:avt@ietf.org" target="_blank">avt@ietf.org</a>"
                  saying:<br>
                  <br>
                  <blockquote class="gmail_quote" style="margin: 0pt 0pt
                    0pt 0.8ex; border-left: 1px solid rgb(204, 204,
                    204); padding-left: 1ex;">
                    <blockquote class="gmail_quote" style="margin: 0pt
                      0pt 0pt 0.8ex; border-left: 1px solid rgb(204,
                      204, 204); padding-left: 1ex;">
                      - if it is a new stream, how to tell that it's a
                      new stream<br>
                      - if it is an old stream, renumbered, how to tell
                      what the old stream was<br>
                    </blockquote>
                    I don't think the specs are that unclear on what is
                    what. You do need<br>
                    the CNAME to determine which case it is. Sure it can
                    be clarified. I<br>
                    mostly think the issue is with the state of the
                    implementations. They<br>
                    haven't considered the implications and need for
                    multiple SSRC support.<br>
                  </blockquote>
                  There are valid cases where multiple independent
                  streams will have the same<br>
                  CNAME -- if they're multiple sources from the same
                  participant. &nbsp;Multiple<br>
                  video streams in the Telepresence/CLUE environment are
                  probably the current<br>
                  most prominent example of this, but generally, this
                  will be the case if you<br>
                  have multiple streams that all need to be synchronized
                  together.<br>
                </blockquote>
                CNAME would be used to relate a source stream with its
                FEC stream as well. The cname guidelines document is a
                useful read:<br>
                <a moz-do-not-send="true"
                  href="http://tools.ietf.org/html/draft-ietf-avt-rtp-cnames-05"
                  target="_blank">http://tools.ietf.org/html/draft-ietf-avt-rtp-cnames-05</a><br>
                <br>
                -acbegen<br>
                <br>
                <blockquote class="gmail_quote" style="margin: 0pt 0pt
                  0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);
                  padding-left: 1ex;">
                  --<br>
                  Jonathan Lennox<br>
                  <a moz-do-not-send="true"
                    href="mailto:lennox@cs.columbia.edu" target="_blank">lennox@cs.columbia.edu</a><br>
                  _______________________________________________<br>
                  Audio/Video Transport Core Maintenance<br>
                  <a moz-do-not-send="true" href="mailto:avt@ietf.org"
                    target="_blank">avt@ietf.org</a><br>
                  <a moz-do-not-send="true"
                    href="https://www.ietf.org/mailman/listinfo/avt"
                    target="_blank">https://www.ietf.org/mailman/listinfo/avt</a><br>
                </blockquote>
                _______________________________________________<br>
                Audio/Video Transport Core Maintenance<br>
                <a moz-do-not-send="true" href="mailto:avt@ietf.org"
                  target="_blank">avt@ietf.org</a><br>
                <a moz-do-not-send="true"
                  href="https://www.ietf.org/mailman/listinfo/avt"
                  target="_blank">https://www.ietf.org/mailman/listinfo/avt</a><br>
              </blockquote>
              _______________________________________________<br>
              Audio/Video Transport Core Maintenance<br>
              <a moz-do-not-send="true" href="mailto:avt@ietf.org"
                target="_blank">avt@ietf.org</a><br>
              <a moz-do-not-send="true"
                href="https://www.ietf.org/mailman/listinfo/avt"
                target="_blank">https://www.ietf.org/mailman/listinfo/avt</a><br>
            </div>
          </div>
        </blockquote>
      </div>
      <br>
    </blockquote>
  </body>
</html>

--------------010905050406020407070507--

From harald@alvestrand.no  Mon Mar 14 23:23:31 2011
Return-Path: <harald@alvestrand.no>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 05B3F3A6A80 for <avt@core3.amsl.com>; Mon, 14 Mar 2011 23:23:31 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tsnlzewaM2Uj for <avt@core3.amsl.com>; Mon, 14 Mar 2011 23:23:30 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by core3.amsl.com (Postfix) with ESMTP id D777A3A6B3A for <avt@ietf.org>; Mon, 14 Mar 2011 23:23:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 9CF3C39E162; Tue, 15 Mar 2011 07:24:17 +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 VNRYaAbr83vf; Tue, 15 Mar 2011 07:24:17 +0100 (CET)
Received: from [192.168.0.200] (126.80-202-241.nextgentel.com [80.202.241.126]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 183F039E089; Tue, 15 Mar 2011 07:24:17 +0100 (CET)
Message-ID: <4D7F0636.1070707@alvestrand.no>
Date: Tue, 15 Mar 2011 07:24:54 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: lennox@cs.columbia.edu
References: <11120238-4159-4BA7-B150-0B28E86651B3@cisco.com>	<4D7798A9.7080006@omnitor.se> <4D779F79.8090001@ericsson.com>	<4D79FEC3.9060204@alvestrand.no> <4D7E3F9C.4010505@ericsson.com> <19838.19728.906691.771074@amman.clic.cs.columbia.edu>
In-Reply-To: <19838.19728.906691.771074@amman.clic.cs.columbia.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] SSRC multiplexing of RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 06:23:31 -0000

On 03/14/11 18:14, lennox@cs.columbia.edu wrote:
> On Monday, March 14 2011, "Magnus Westerlund" wrote to "Harald Alvestrand, avt@ietf.org" saying:
>
>>> - if it is a new stream, how to tell that it's a new stream
>>> - if it is an old stream, renumbered, how to tell what the old stream was
>> I don't think the specs are that unclear on what is what. You do need
>> the CNAME to determine which case it is. Sure it can be clarified. I
>> mostly think the issue is with the state of the implementations. They
>> haven't considered the implications and need for multiple SSRC support.
> There are valid cases where multiple independent streams will have the same
> CNAME -- if they're multiple sources from the same participant.  Multiple
> video streams in the Telepresence/CLUE environment are probably the current
> most prominent example of this, but generally, this will be the case if you
> have multiple streams that all need to be synchronized together.
Hm. CNAME seems like it's not a stream identifier.

RFC 3550 section 6.5.1 contains lots of language saying that it is the 
user@host, which would mean that if I send two video streams and two 
audio streams, I have four streams with the same CNAME.

No matter whether these are in one RTP session or multiple RTP sessions, 
this seems problematic - in the case of layered encodings using multiple 
RTP sessions, it seems to me that if I send two video streams over four 
sessions, I will have a hard time matching each base layer with its 
corresponding higher layer if CNAME is my only correlator.

                       Harald









From Even.roni@huawei.com  Tue Mar 15 06:27:13 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 835C43A6D75 for <avt@core3.amsl.com>; Tue, 15 Mar 2011 06:27:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.863
X-Spam-Level: 
X-Spam-Status: No, score=-101.863 tagged_above=-999 required=5 tests=[AWL=-1.368, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WSE+Lb-SKBho for <avt@core3.amsl.com>; Tue, 15 Mar 2011 06:27:12 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id A8B5A3A6D19 for <avt@ietf.org>; Tue, 15 Mar 2011 06:27:12 -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 <0LI3005BPPFFXN@szxga05-in.huawei.com> for avt@ietf.org; Tue, 15 Mar 2011 21:28:27 +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 <0LI300DEEPFEET@szxga05-in.huawei.com> for avt@ietf.org; Tue, 15 Mar 2011 21:28:27 +0800 (CST)
Received: from windows8d787f9 (bzq-109-65-13-217.red.bezeqint.net [109.65.13.217]) by szxml11-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LI300FPNPF62M@szxml11-in.huawei.com>; Tue, 15 Mar 2011 21:28:26 +0800 (CST)
Date: Tue, 15 Mar 2011 15:28:05 +0200
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <4D78EF1D.5050104@ericsson.com>
To: 'Magnus Westerlund' <magnus.westerlund@ericsson.com>, 'IETF AVTCore WG' <avt@ietf.org>
Message-id: <00c101cbe314$d69178a0$83b469e0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcvfOIag8rySqca5RPSWt3+gTN2XfAD23sQQ
References: <4D78EF1D.5050104@ericsson.com>
Subject: Re: [AVTCORE] Proposed changes to draft-ietf-avtcore-ecn-for-rtp
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 13:27:13 -0000

Hi Magnus,
Sorry for not looking at it before the version came out. I have one comment.

> 
> 
> Section 6.1:
> The ecn-capable-rtp attribute is defined as media level attribute.
> However the previous text explicitly forbid it to be on session level.
> But that blocks the default behavior specified in the SDP RFC 4566:
> 
>    The connection ("c=") and attribute ("a=") information in the
>    session-level section applies to all the media of that session
> unless
>    overridden by connection information or an attribute of the same
> name
>    in the media description.  For instance, in the example below, each
>    media behaves as if it were given a "recvonly" attribute.
> 
> OLD text:
>  This is a
>    media level attribute, which MUST NOT be used at the session level.
> 
> 
> NEW text:
> This is a media level attribute, thus it is normally included as part
> of
> the media description, but if present at session level the same
> configuration applies to all media descriptions.


There is no such requirement in RFC 4566. See section 5.13 "Attributes are
the primary means for extending SDP.  Attributes may
   be defined to be used as "session-level" attributes, "media-level"
attributes, or both."
So it can be a media level attribute. If you want it to be a session level
attribute also than you will need to define it later in section 6.1 and in
the IANA registration section. My view is this is only a media level
attribute.



Roni Even


From magnus.westerlund@ericsson.com  Tue Mar 15 07:06:34 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7996E3A6DAC for <avt@core3.amsl.com>; Tue, 15 Mar 2011 07:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.497
X-Spam-Level: 
X-Spam-Status: No, score=-106.497 tagged_above=-999 required=5 tests=[AWL=0.102, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rI8WQVsU5MqK for <avt@core3.amsl.com>; Tue, 15 Mar 2011 07:06:33 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 64F413A6DB6 for <avt@ietf.org>; Tue, 15 Mar 2011 07:06:31 -0700 (PDT)
X-AuditID: c1b4fb3d-b7bbbae000005311-dc-4d7f72bb02f1
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id BD.06.21265.BB27F7D4; Tue, 15 Mar 2011 15:07:55 +0100 (CET)
Received: from [147.214.183.8] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.2.234.1; Tue, 15 Mar 2011 15:07:55 +0100
Message-ID: <4D7F72BB.2060605@ericsson.com>
Date: Tue, 15 Mar 2011 15:07:55 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Roni Even <Even.roni@huawei.com>
References: <4D78EF1D.5050104@ericsson.com> <00c101cbe314$d69178a0$83b469e0$%roni@huawei.com>
In-Reply-To: <00c101cbe314$d69178a0$83b469e0$%roni@huawei.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: 'IETF AVTCore WG' <avt@ietf.org>
Subject: Re: [AVTCORE] Proposed changes to draft-ietf-avtcore-ecn-for-rtp
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 14:06:34 -0000

Roni Even skrev 2011-03-15 14:28:
> Hi Magnus,
> Sorry for not looking at it before the version came out. I have one comment.
> 
>>
>>
>> Section 6.1:
>> The ecn-capable-rtp attribute is defined as media level attribute.
>> However the previous text explicitly forbid it to be on session level.
>> But that blocks the default behavior specified in the SDP RFC 4566:
>>
>>    The connection ("c=") and attribute ("a=") information in the
>>    session-level section applies to all the media of that session
>> unless
>>    overridden by connection information or an attribute of the same
>> name
>>    in the media description.  For instance, in the example below, each
>>    media behaves as if it were given a "recvonly" attribute.
>>
>> OLD text:
>>  This is a
>>    media level attribute, which MUST NOT be used at the session level.
>>
>>
>> NEW text:
>> This is a media level attribute, thus it is normally included as part
>> of
>> the media description, but if present at session level the same
>> configuration applies to all media descriptions.
> 
> 
> There is no such requirement in RFC 4566. See section 5.13 "Attributes are
> the primary means for extending SDP.  Attributes may
>    be defined to be used as "session-level" attributes, "media-level"
> attributes, or both."
> So it can be a media level attribute. If you want it to be a session level
> attribute also than you will need to define it later in section 6.1 and in
> the IANA registration section. My view is this is only a media level
> attribute.

Yes,

I have to agree after re-reading this. I can't understand how I came to
the conclusion that a media level only attribute can be at session level
also. I will ask my commentor about what supports his view.


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  Tue Mar 15 07:16:16 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 78B303A6D25 for <avt@core3.amsl.com>; Tue, 15 Mar 2011 07:16:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.5
X-Spam-Level: 
X-Spam-Status: No, score=-106.5 tagged_above=-999 required=5 tests=[AWL=0.099,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b2oH2-wlbfO1 for <avt@core3.amsl.com>; Tue, 15 Mar 2011 07:16:15 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 55E863A6B5B for <avt@ietf.org>; Tue, 15 Mar 2011 07:16:15 -0700 (PDT)
X-AuditID: c1b4fb39-b7c6dae0000023f2-c7-4d7f75037f88
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 48.34.09202.3057F7D4; Tue, 15 Mar 2011 15:17:39 +0100 (CET)
Received: from [147.214.183.8] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.2.234.1; Tue, 15 Mar 2011 15:17:39 +0100
Message-ID: <4D7F7503.70907@ericsson.com>
Date: Tue, 15 Mar 2011 15:17:39 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Harald Alvestrand <harald@alvestrand.no>
References: <11120238-4159-4BA7-B150-0B28E86651B3@cisco.com>	<4D7798A9.7080006@omnitor.se> <4D779F79.8090001@ericsson.com>	<4D79FEC3.9060204@alvestrand.no> <4D7E3F9C.4010505@ericsson.com> <19838.19728.906691.771074@amman.clic.cs.columbia.edu> <4D7F0636.1070707@alvestrand.no>
In-Reply-To: <4D7F0636.1070707@alvestrand.no>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: "lennox@cs.columbia.edu" <lennox@cs.columbia.edu>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] SSRC multiplexing of RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 14:16:16 -0000

Harald Alvestrand skrev 2011-03-15 07:24:
> On 03/14/11 18:14, lennox@cs.columbia.edu wrote:
>> On Monday, March 14 2011, "Magnus Westerlund" wrote to "Harald Alvestrand, avt@ietf.org" saying:
>>
>>>> - if it is a new stream, how to tell that it's a new stream
>>>> - if it is an old stream, renumbered, how to tell what the old stream was
>>> I don't think the specs are that unclear on what is what. You do need
>>> the CNAME to determine which case it is. Sure it can be clarified. I
>>> mostly think the issue is with the state of the implementations. They
>>> haven't considered the implications and need for multiple SSRC support.
>> There are valid cases where multiple independent streams will have the same
>> CNAME -- if they're multiple sources from the same participant.  Multiple
>> video streams in the Telepresence/CLUE environment are probably the current
>> most prominent example of this, but generally, this will be the case if you
>> have multiple streams that all need to be synchronized together.
> Hm. CNAME seems like it's not a stream identifier.
> 
> RFC 3550 section 6.5.1 contains lots of language saying that it is the 
> user@host, which would mean that if I send two video streams and two 
> audio streams, I have four streams with the same CNAME.

Well, generating good quality cnames are one question and that is solved by:
https://datatracker.ietf.org/doc/draft-ietf-avt-rtp-cnames/

The other question is how you use the CNAME to bind together streams. I
do agree that we do have cases today where you can't both get synch and
SSRC multiplexing of certain functionalities. It is definitely something
that should be included in the
https://datatracker.ietf.org/doc/draft-perkins-rtcweb-rtp-usage/

> 
> No matter whether these are in one RTP session or multiple RTP sessions, 
> this seems problematic - in the case of layered encodings using multiple 
> RTP sessions, it seems to me that if I send two video streams over four 
> sessions, I will have a hard time matching each base layer with its 
> corresponding higher layer if CNAME is my only correlator.

Well, you can use the same SSRC over multiple RTP streams to achieve
quicker and clearer synchronization. I still need to read SVC payload
format, but I know that Session multiplexing of RTP retransmissions (RFC
4588) does use that method for correlation.

I am not certain that we haven't forgotten any case, but when
introducing certain type of RTP functionalities you also at the same
time restrict the possibilities in how these mechanisms can be used.

I think AVT groups should work with CLUE and RTCWEB here to address the
issues found due to the use cases these WGs have.

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 lennox@cs.columbia.edu  Tue Mar 15 07:26:11 2011
Return-Path: <lennox@cs.columbia.edu>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24C533A6D27 for <avt@core3.amsl.com>; Tue, 15 Mar 2011 07:26:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id noPzyJ-tVSr5 for <avt@core3.amsl.com>; Tue, 15 Mar 2011 07:26:10 -0700 (PDT)
Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by core3.amsl.com (Postfix) with ESMTP id 75EF13A6D11 for <avt@ietf.org>; Tue, 15 Mar 2011 07:26:07 -0700 (PDT)
Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) by mail1.panix.com (Postfix) with ESMTP id 049EE1F091; Tue, 15 Mar 2011 10:27:31 -0400 (EDT)
Received: from amman.clic.cs.columbia.edu (amman.clic.cs.columbia.edu [128.59.15.55]) by mailbackend.panix.com (Postfix) with ESMTP id A068D32470; Tue, 15 Mar 2011 10:27:31 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Message-ID: <19839.30546.858197.282793@amman.clic.cs.columbia.edu>
Date: Tue, 15 Mar 2011 10:27:30 -0400
To: =?ISO-8859-1?Q?Gunnar_Hellstr=F6m?= <gunnar.hellstrom@omnitor.se>
In-Reply-To: <4D7EA149.50005@omnitor.se>
References: <11120238-4159-4BA7-B150-0B28E86651B3@cisco.com> <4D7798A9.7080006@omnitor.se> <4D779F79.8090001@ericsson.com> <4D79FEC3.9060204@alvestrand.no> <4D7E3F9C.4010505@ericsson.com> <19838.19728.906691.771074@amman.clic.cs.columbia.edu> <04CAD96D4C5A3D48B1919248A8FE0D540E8ABC69@xmb-sjc-215.amer.cisco.com> <4D7EA149.50005@omnitor.se>
X-Mailer: VM 7.19 under Emacs 22.2.1
From: lennox@cs.columbia.edu
Cc: avt@ietf.org
Subject: Re: [AVTCORE] SSRC multiplexing of RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 14:26:11 -0000

On Tuesday, March 15 2011, "Gunnar Hellstr=F6m" wrote to "avt@ietf.org"=
 saying:

> The rtp-cnames document seems to give good advice.
>=20
> Statements that make me want to stay away from SSRC multiplexing is f=
or=20
> example what is stated in RFC 3550 RTP
> in 6.2.1
>   "New sites are added to the count when they are heard, and an entry=
=20
> for each SHOULD be created in a table indexed by the SSRC or CSRC=20
> identifier (see Section 8.2) to keep track of them. New entries MAY b=
e=20
> considered not valid until multiple packets carrying the new SSRC hav=
e=20
> been received "
>
> If a source is regarded not valid, I see a risk that RTP implementati=
ons=20
> ignore packets from that source.

This recommendation made sense in the context RTP was originally writte=
n
for, i.e. Any-Source Multicast with no authentication.

It doesn't make much sense for SSRC multiplixing over unicast or
single-source multicast, or for SRTP-based authentication.

A document giving recommendations about how best to handle SSRC multipl=
exing
should probably mention that this recommendation should be altered in
environments when it's inappropriate.  (Particularly for video, disrega=
rding
initial packets is a very bad idea.)

--=20
Jonathan Lennox
lennox@cs.columbia.edu

From lennox@cs.columbia.edu  Tue Mar 15 07:36:31 2011
Return-Path: <lennox@cs.columbia.edu>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C1F763A6DEC for <avt@core3.amsl.com>; Tue, 15 Mar 2011 07:36:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level: 
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QHUf9DeTEjSQ for <avt@core3.amsl.com>; Tue, 15 Mar 2011 07:36:30 -0700 (PDT)
Received: from mail2.panix.com (mail2.panix.com [166.84.1.73]) by core3.amsl.com (Postfix) with ESMTP id A39B13A6DEA for <avt@ietf.org>; Tue, 15 Mar 2011 07:36:30 -0700 (PDT)
Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) by mail2.panix.com (Postfix) with ESMTP id 8F36838E4A; Tue, 15 Mar 2011 10:37:55 -0400 (EDT)
Received: from amman.clic.cs.columbia.edu (amman.clic.cs.columbia.edu [128.59.15.55]) by mailbackend.panix.com (Postfix) with ESMTP id 0900A32059; Tue, 15 Mar 2011 10:37:54 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <19839.31170.408326.656106@amman.clic.cs.columbia.edu>
Date: Tue, 15 Mar 2011 10:37:54 -0400
To: Harald Alvestrand <harald@alvestrand.no>
In-Reply-To: <4D7F0636.1070707@alvestrand.no>
References: <11120238-4159-4BA7-B150-0B28E86651B3@cisco.com> <4D7798A9.7080006@omnitor.se> <4D779F79.8090001@ericsson.com> <4D79FEC3.9060204@alvestrand.no> <4D7E3F9C.4010505@ericsson.com> <19838.19728.906691.771074@amman.clic.cs.columbia.edu> <4D7F0636.1070707@alvestrand.no>
X-Mailer: VM 7.19 under Emacs 22.2.1
From: lennox@cs.columbia.edu
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] SSRC multiplexing of RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 14:36:31 -0000

On Tuesday, March 15 2011, "Harald Alvestrand" wrote to "lennox@cs.columbia.edu, Magnus Westerlund, avt@ietf.org" saying:

> On 03/14/11 18:14, lennox@cs.columbia.edu wrote:
> > On Monday, March 14 2011, "Magnus Westerlund" wrote to "Harald Alvestrand, avt@ietf.org" saying:
> >
> >>> - if it is a new stream, how to tell that it's a new stream
> >>> - if it is an old stream, renumbered, how to tell what the old stream was
> >> I don't think the specs are that unclear on what is what. You do need
> >> the CNAME to determine which case it is. Sure it can be clarified. I
> >> mostly think the issue is with the state of the implementations. They
> >> haven't considered the implications and need for multiple SSRC support.
> > There are valid cases where multiple independent streams will have the same
> > CNAME -- if they're multiple sources from the same participant.  Multiple
> > video streams in the Telepresence/CLUE environment are probably the current
> > most prominent example of this, but generally, this will be the case if you
> > have multiple streams that all need to be synchronized together.
> Hm. CNAME seems like it's not a stream identifier.

No -- RFC 3550 pretty clearly defines CNAME as a participant/endpoint
identifier, not a stream identifier.  The rule of thumb I use is that all
streams that need to be synchronized with each other need to have the same
CNAME.

RFC 5576 provides an SDP-based mechanism to uniquely identify streams and
their properties, and to bind streams together following an SSRC collision,
even when multiple streams have the same CNAME.

It's not clear that RTCWeb necessarily wants to use SDP, and it's also not
clear that SDP scales to all the cases that CLUE needs.  However, I think
that starting from RFC 5576 semantics, even if not necessarily its syntax,
for these other use cases would probably be a good idea.

-- 
Jonathan Lennox
lennox@cs.columbia.edu

From magnus.westerlund@ericsson.com  Tue Mar 15 07:41:43 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9929C3A6D8D for <avt@core3.amsl.com>; Tue, 15 Mar 2011 07:41:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.503
X-Spam-Level: 
X-Spam-Status: No, score=-106.503 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w0AWkKhQL2m8 for <avt@core3.amsl.com>; Tue, 15 Mar 2011 07:41:42 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 74F0F3A6D85 for <avt@ietf.org>; Tue, 15 Mar 2011 07:41:42 -0700 (PDT)
X-AuditID: c1b4fb39-b7c6dae0000023f2-f6-4d7f7afaa442
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 88.E7.09202.AFA7F7D4; Tue, 15 Mar 2011 15:43:06 +0100 (CET)
Received: from [147.214.183.8] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.2.234.1; Tue, 15 Mar 2011 15:43:06 +0100
Message-ID: <4D7F7AFA.2000206@ericsson.com>
Date: Tue, 15 Mar 2011 15:43:06 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: "lennox@cs.columbia.edu" <lennox@cs.columbia.edu>
References: <11120238-4159-4BA7-B150-0B28E86651B3@cisco.com>	<4D7798A9.7080006@omnitor.se> <4D779F79.8090001@ericsson.com>	<4D79FEC3.9060204@alvestrand.no> <4D7E3F9C.4010505@ericsson.com>	<19838.19728.906691.771074@amman.clic.cs.columbia.edu>	<04CAD96D4C5A3D48B1919248A8FE0D540E8ABC69@xmb-sjc-215.amer.cisco.com>	<4D7EA149.50005@omnitor.se> <19839.30546.858197.282793@amman.clic.cs.columbia.edu>
In-Reply-To: <19839.30546.858197.282793@amman.clic.cs.columbia.edu>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: =?ISO-8859-1?Q?Gunnar_Hellstr=F6m?= <gunnar.hellstrom@omnitor.se>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] SSRC multiplexing of RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 14:41:43 -0000

lennox@cs.columbia.edu skrev 2011-03-15 15:27:
> On Tuesday, March 15 2011, "Gunnar Hellström" wrote to "avt@ietf.org" saying:
> 
>> The rtp-cnames document seems to give good advice.
>>
>> Statements that make me want to stay away from SSRC multiplexing is for 
>> example what is stated in RFC 3550 RTP
>> in 6.2.1
>>   "New sites are added to the count when they are heard, and an entry 
>> for each SHOULD be created in a table indexed by the SSRC or CSRC 
>> identifier (see Section 8.2) to keep track of them. New entries MAY be 
>> considered not valid until multiple packets carrying the new SSRC have 
>> been received "
>>
>> If a source is regarded not valid, I see a risk that RTP implementations 
>> ignore packets from that source.
> 
> This recommendation made sense in the context RTP was originally written
> for, i.e. Any-Source Multicast with no authentication.
> 
> It doesn't make much sense for SSRC multiplixing over unicast or
> single-source multicast, or for SRTP-based authentication.
> 
> A document giving recommendations about how best to handle SSRC multiplexing
> should probably mention that this recommendation should be altered in
> environments when it's inappropriate.  (Particularly for video, disregarding
> initial packets is a very bad idea.)
> 

Fully agree, and please note the "MAY" in the RFC 3550 text. An
implementation can do so when appropriate. I think in a context where
one knows source addresses of one peer etc, those are better protection
than RTP and RTCP packet based validation before accepting an SSRC. In
the implementations I have done of RTP/RTCP we have set the number of
packets needed before adding SSRC to 0. Because dropping the initial
packets are degrading quality to much.

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 thomas.schierl@hhi.fraunhofer.de  Tue Mar 15 08:09:08 2011
Return-Path: <thomas.schierl@hhi.fraunhofer.de>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D1153A6D77 for <avt@core3.amsl.com>; Tue, 15 Mar 2011 08:09:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.8
X-Spam-Level: 
X-Spam-Status: No, score=-4.8 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y3wqH-r9jCCI for <avt@core3.amsl.com>; Tue, 15 Mar 2011 08:09:07 -0700 (PDT)
Received: from mailgw.hhi.fraunhofer.de (mail.HHI.FRAUNHOFER.DE [193.174.67.45]) by core3.amsl.com (Postfix) with ESMTP id 226293A6D7F for <avt@ietf.org>; Tue, 15 Mar 2011 08:09:06 -0700 (PDT)
X-IMSS-DKIM-Authentication-Result: mailgw.hhi.fraunhofer.de; sigcount=0
Received: from [130.149.228.79] (ic638001.ic.tu-berlin.de [130.149.228.79]) by mailgw.hhi.fraunhofer.de (Postfix) with ESMTP id 2052B1C90005; Tue, 15 Mar 2011 16:11:49 +0100 (CET)
Message-ID: <4D7F8166.3070409@hhi.fraunhofer.de>
Date: Tue, 15 Mar 2011 16:10:30 +0100
From: Thomas Schierl <thomas.schierl@hhi.fraunhofer.de>
Organization: Fraunhofer-Institut fuer Nachrichtentechnik Heinrich-Hertz-Institut
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <11120238-4159-4BA7-B150-0B28E86651B3@cisco.com>	<4D7798A9.7080006@omnitor.se>	<4D779F79.8090001@ericsson.com>	<4D79FEC3.9060204@alvestrand.no>	<4D7E3F9C.4010505@ericsson.com>	<19838.19728.906691.771074@amman.clic.cs.columbia.edu>	<4D7F0636.1070707@alvestrand.no> <4D7F7503.70907@ericsson.com>
In-Reply-To: <4D7F7503.70907@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-alterMIME: Yes
Cc: "lennox@cs.columbia.edu" <lennox@cs.columbia.edu>, Harald Alvestrand <harald@alvestrand.no>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] SSRC multiplexing of RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 15:09:08 -0000

Hi Magnus,

On 15.03.2011 15:17, Magnus Westerlund wrote:
>> >  
>> >  No matter whether these are in one RTP session or multiple RTP sessions,
>> >  this seems problematic - in the case of layered encodings using multiple
>> >  RTP sessions, it seems to me that if I send two video streams over four
>> >  sessions, I will have a hard time matching each base layer with its
>> >  corresponding higher layer if CNAME is my only correlator.
> Well, you can use the same SSRC over multiple RTP streams to achieve
> quicker and clearer synchronization. I still need to read SVC payload
> format, but I know that Session multiplexing of RTP retransmissions (RFC
> 4588) does use that method for correlation.
>
> I am not certain that we haven't forgotten any case, but when
> introducing certain type of RTP functionalities you also at the same
> time restrict the possibilities in how these mechanisms can be used.
>
> I think AVT groups should work with CLUE and RTCWEB here to address the
> issues found due to the use cases these WGs have.


In the RTP payload format for SVC, we assumed Session Multiplexing plus 
using the same SSRC for the layers of the same source.
















-- 
Visit us at

Web 2.0 / March 28-31 / San Francisco, Moscone West, USA / booth 824
www.web2expo.com/webexsf2011

NAB Show 2011/ April 11-14 / Las Vegas, Nevada, USA / booth C8444 (Bavarian Pavillon)
www.hhi.fraunhofer.de/nab

From tom.van_caenegem@alcatel-lucent.com  Wed Mar 16 02:15:20 2011
Return-Path: <tom.van_caenegem@alcatel-lucent.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6F5423A68CB for <avt@core3.amsl.com>; Wed, 16 Mar 2011 02:15:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.915
X-Spam-Level: 
X-Spam-Status: No, score=-5.915 tagged_above=-999 required=5 tests=[AWL=0.333,  BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YeeFLrEF9jua for <avt@core3.amsl.com>; Wed, 16 Mar 2011 02:15:19 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by core3.amsl.com (Postfix) with ESMTP id 72D813A68B1 for <avt@ietf.org>; Wed, 16 Mar 2011 02:15:18 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p2G9FgYJ009843 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <avt@ietf.org>; Wed, 16 Mar 2011 10:16:43 +0100
Received: from FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com ([135.120.45.43]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Wed, 16 Mar 2011 10:16:35 +0100
From: "Van Caenegem, Tom (Tom)" <tom.van_caenegem@alcatel-lucent.com>
To: IETF AVT WG <avt@ietf.org>
Date: Wed, 16 Mar 2011 10:16:33 +0100
Thread-Topic: Submission of new draft: "draft-vancaenegem-avtcore-fb-supp-and-retransm-00"
Thread-Index: Acvjutf259GXqGBpQ++1/wizS6FnWA==
Message-ID: <EC3FD58E75D43A4F8807FDE074917546170B13EA@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
Accept-Language: nl-NL, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: nl-NL, en-US
Content-Type: multipart/alternative; boundary="_000_EC3FD58E75D43A4F8807FDE074917546170B13EAFRMRSSXCHMBSB1d_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.83
Subject: [AVTCORE] Submission of new draft: "draft-vancaenegem-avtcore-fb-supp-and-retransm-00"
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Mar 2011 09:15:20 -0000

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

Hi,

a new draft is submitted for your review and comments on the topic of RTCP =
FB suppression and retransmission, entitled: "RTCP FB NACK storm suppressio=
n and its impact on retransmission in RTP"
It can be found here:

https://datatracker.ietf.org/doc/draft-vancaenegem-avtcore-fb-supp-and-retr=
ansm/


Abstract

   This document discusses how RTCP Feedback storm suppression
   negatively affects retransmission efficacy for Source Specific
   Multicast sessions with unicast feedback architectures and proposes
   some recommendations by means of additional signaling (e.g.  RSI
   message and new attribute parameters) and a small AVPF FB suppression
   rule modification resulting in a overall better system where the FB
   suppression can be maintained but with a optimised retransmission
   efficacy.



Kind Regards

Tom

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.6058" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D348521009-16032011>Hi,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D348521009-16032011></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D348521009-16032011>a new dra=
ft is=20
submitted for your review and comments on the topic of RTCP FB suppression =
and=20
retransmission, entitled: "</SPAN></FONT><FONT face=3DArial size=3D2><SPAN=
=20
class=3D348521009-16032011>RTCP FB NACK storm suppression and its impact on=
=20
retransmission in RTP"<BR></DIV></SPAN></FONT>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D348521009-16032011>It&nbsp;c=
an be found=20
here:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D348521009-16032011></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D348521009-16032011><A=20
href=3D"https://datatracker.ietf.org/doc/draft-vancaenegem-avtcore-fb-supp-=
and-retransm/">https://datatracker.ietf.org/doc/draft-vancaenegem-avtcore-f=
b-supp-and-retransm/</A></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV><!-- Converted from tex=
t/rtf format -->
<DIV><PRE><SPAN class=3Dm_h>Abstract</SPAN>

   This document discusses how RTCP Feedback storm suppression
   negatively affects retransmission efficacy for Source Specific
   Multicast sessions with unicast feedback architectures and proposes
   some recommendations by means of additional signaling (e.g.  RSI
   message and new attribute parameters) and a small AVPF FB suppression
   rule modification resulting in a overall better system where the FB
   suppression can be maintained but with a optimised retransmission
   efficacy.

<SPAN class=3D348521009-16032011></SPAN></PRE><PRE><SPAN class=3D348521009-=
16032011>Kind Regards</SPAN></PRE><PRE><SPAN class=3D348521009-16032011></S=
PAN><SPAN class=3D348521009-16032011>Tom</SPAN></PRE></DIV></BODY></HTML>

--_000_EC3FD58E75D43A4F8807FDE074917546170B13EAFRMRSSXCHMBSB1d_--

From mcgrew@cisco.com  Wed Mar 16 06:32:13 2011
Return-Path: <mcgrew@cisco.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 417513A6954 for <avt@core3.amsl.com>; Wed, 16 Mar 2011 06:32:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.411
X-Spam-Level: 
X-Spam-Status: No, score=-110.411 tagged_above=-999 required=5 tests=[AWL=0.188, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RMesrD9PmTdu for <avt@core3.amsl.com>; Wed, 16 Mar 2011 06:32:12 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 18C933A6999 for <avt@ietf.org>; Wed, 16 Mar 2011 06:32:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mcgrew@cisco.com; l=3233; q=dns/txt; s=iport; t=1300282418; x=1301492018; h=message-id:from:to:in-reply-to:mime-version:subject:date: references; bh=3nRfBum+ac/s1jgiuJhG4mXVVFfsmHVvn2oI8tx4bPQ=; b=MY//MXD+9oZ5OtMRVwwl0SZqOue3I8UpCM7HpAzszl/R3zyjC6LMo6GD /i4qDB44bGFkC+7/cdfhyUraKQZ6MSt9EW2xOfsAeSg2TSrHhN4r5td3M Tdb8ozMW3wtmjF2cJFxtTX6PBjYwx44NBvSJWMEIiHqSjBzkEzXdt06Ao Q=;
X-Files: smime.p7s : 1760
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAOtYgE2tJV2a/2dsb2JhbACmCHelM5xRhWIEhS+HL4NN
X-IronPort-AV: E=Sophos;i="4.63,194,1299456000";  d="p7s'?scan'208";a="347691560"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by sj-iport-5.cisco.com with ESMTP; 16 Mar 2011 13:33:38 +0000
Received: from [10.32.254.210] ([10.32.254.210]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2GDXbbY002270;  Wed, 16 Mar 2011 13:33:37 GMT
Message-Id: <BBCED4EC-69BF-4E41-9BC1-2CFA39807524@cisco.com>
From: David McGrew <mcgrew@cisco.com>
To: AVT WG <avt@ietf.org>, draft-ietf-avtcore-srtp-vbr-audio@tools.ietf.org
In-Reply-To: <2B418AC4-F470-4A18-BB98-48191DA2B6DE@cisco.com>
Content-Type: multipart/signed; boundary=Apple-Mail-497--147330907; micalg=sha1; protocol="application/pkcs7-signature"
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 16 Mar 2011 06:33:36 -0700
References: <2B418AC4-F470-4A18-BB98-48191DA2B6DE@cisco.com>
X-Mailer: Apple Mail (2.936)
Subject: Re: [AVTCORE] comments on draft-ietf-avtcore-srtp-vbr-audio
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Mar 2011 13:32:13 -0000

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

Hi,

this draft treats an important topic and is well written.  I would  
definitely like to see it advance.

I suggest that Section 5 include a more concrete recommendation on  
padding, such as: the payload SHOULD be padded so that its length is a  
multiple of 16 octets, which has been shown to greatly reduce the leak  
of speech characteristics [spot-me, Section 4].

CBR should be defined (I assumed "constant bit rate")

regards,

David



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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIDnjCCA5ow
ggKCoAMCAQICAWQwCwYJKoZIhvcNAQEFMG0xFTATBgNVBAMMDERhdmlkIE1jR3JldzETMBEGA1UE
CAwKQ2FsaWZvcm5pYTELMAkGA1UEBhMCVVMxETAPBgNVBAcMCFNhbiBKb3NlMR8wHQYJKoZIhvcN
AQkBFhBtY2dyZXdAY2lzY28uY29tMB4XDTA4MTIwOTIyMDMzMFoXDTA5MTIwOTIyMDMzMFowbTEV
MBMGA1UEAwwMRGF2aWQgTWNHcmV3MRMwEQYDVQQIDApDYWxpZm9ybmlhMQswCQYDVQQGEwJVUzER
MA8GA1UEBwwIU2FuIEpvc2UxHzAdBgkqhkiG9w0BCQEWEG1jZ3Jld0BjaXNjby5jb20wggEiMA0G
CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDh5WR1gATRK4ubbWwmG2T/XTUeVc2FAxnmtoYy00fM
5jp3DYFXHkWj4Cl8RVVfAJxP/2PhKsTl0qx2b7N9pIZZa6BaODEyJ8yVMRHloHrpzHeU8DIrst/H
SFVkcJvl3p9LFD42BCvznzQ48VxnWX68OCk7GAwg6XoKMY8Z1F70PVvcZ0JcbnDuKx0efQ+P74uY
UdpjRYSXb2xJUziGs5k6b1kTr5754B3tnYCGkum49YAbONpsOL4R+e4HNNrkVTx254ggrcDb1GDr
IpZYCSPh6lZWwOp0XBoJiLYEKXuBf/jSNEv15/Kt/Uu5Oh8jUBxkBHGAVZuaVu25s3Zk9waLAgMB
AAGjRzBFMA4GA1UdDwEB/wQEAwIEsDAWBgNVHSUBAf8EDDAKBggrBgEFBQcDBDAbBgNVHREEFDAS
gRBtY2dyZXdAY2lzY28uY29tMA0GCSqGSIb3DQEBBQUAA4IBAQCbD+Y6Yu0d5FZHSGd7WTP7vlo+
SE2rF0YzqvcMYrEuu6VBbkOFGfq3leu2WVJinXYQwAgaZ7vJpH43/bjDIK4YuOqAUv57ZQjtCJ6W
6b0rdG8/A2cWcGoDjqmjAGJ4TC8oMIc0h33QPEjsGdon0nsV0QCxrgWcWEjFSzlE6kbR4pT3yA2V
zo7byNoDoYpH5otGH0/cRQM9i6ENTytxzczPeNTt2uaMp/3s8MZ5W/0Yz8U/yy5bcS5TGrqgTvN7
mI+nngoJ4TNKapSpdSqCyEK86z51VWtRRFyBosLQsNhMYb7HWzW/mIQCG0SygOVjUcRPKxhYUokR
gCmxsHqcL1uMMYIDBDCCAwACAQEwcjBtMRUwEwYDVQQDDAxEYXZpZCBNY0dyZXcxEzARBgNVBAgM
CkNhbGlmb3JuaWExCzAJBgNVBAYTAlVTMREwDwYDVQQHDAhTYW4gSm9zZTEfMB0GCSqGSIb3DQEJ
ARYQbWNncmV3QGNpc2NvLmNvbQIBZDAJBgUrDgMCGgUAoIIBZzAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTAzMTYxMzMzMzZaMCMGCSqGSIb3DQEJBDEWBBSsKbMk
8hlHp7XNSVCtP0hTAEXYvDCBgQYJKwYBBAGCNxAEMXQwcjBtMRUwEwYDVQQDDAxEYXZpZCBNY0dy
ZXcxEzARBgNVBAgMCkNhbGlmb3JuaWExCzAJBgNVBAYTAlVTMREwDwYDVQQHDAhTYW4gSm9zZTEf
MB0GCSqGSIb3DQEJARYQbWNncmV3QGNpc2NvLmNvbQIBZDCBgwYLKoZIhvcNAQkQAgsxdKByMG0x
FTATBgNVBAMMDERhdmlkIE1jR3JldzETMBEGA1UECAwKQ2FsaWZvcm5pYTELMAkGA1UEBhMCVVMx
ETAPBgNVBAcMCFNhbiBKb3NlMR8wHQYJKoZIhvcNAQkBFhBtY2dyZXdAY2lzY28uY29tAgFkMA0G
CSqGSIb3DQEBAQUABIIBAHyFAfv3Vz56fmvu/QF8aPMnjDduLH3v8tKVFaGJHUTlqyRzH7dVhMGw
8sq0ltvMO/5MNL5eSYUkDIKO1fL1mnabaCKqOx5mSetnb89FYPZh521jHmdhZMAnSOgAPiESuxYh
hSFpSf7aUHziZYbKBoc1KG/nv2hPY7sK2uqzPubyRPjTMMVWfM7dTBHdcRXElU3tob5Ijy4HyPw6
TuZ/T5g8YePJX+MqL1NMtX7Hoxd4KlCqxaBT48c3WydUmGaHb2PXgjJQo407VHGbYmZmbVUziCCh
o3gdbCRMbAMmJgSHGeQ1Ek9CRDAOWX8DxTsnecKHYL/WceK999T19L3n1ScAAAAAAAA=

--Apple-Mail-497--147330907--

From Even.roni@huawei.com  Wed Mar 16 07:35:45 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 617F33A6920 for <avt@core3.amsl.com>; Wed, 16 Mar 2011 07:35:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.179
X-Spam-Level: 
X-Spam-Status: No, score=-103.179 tagged_above=-999 required=5 tests=[AWL=1.316, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HC7YyTCGNynj for <avt@core3.amsl.com>; Wed, 16 Mar 2011 07:35:44 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id C679A3A6911 for <avt@ietf.org>; Wed, 16 Mar 2011 07:35:43 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LI500AC3N5RRM@szxga04-in.huawei.com> for avt@ietf.org; Wed, 16 Mar 2011 22:34:39 +0800 (CST)
Received: from 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 <0LI5003FEN5RRG@szxga04-in.huawei.com> for avt@ietf.org; Wed, 16 Mar 2011 22:34:39 +0800 (CST)
Received: from windows8d787f9 ([109.65.13.217]) by szxml12-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LI500LUMN5KFS@szxml12-in.huawei.com>; Wed, 16 Mar 2011 22:34:39 +0800 (CST)
Date: Wed, 16 Mar 2011 16:34:20 +0200
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <AANLkTimiOb29PRXVfDjVp5=Bt2L4hQ_FXychLbCdboaT@mail.gmail.com>
To: 'varun singh' <vsingh.ietf@gmail.com>, avt@ietf.org
Message-id: <005e01cbe3e7$4142abb0$c3c80310$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcvikujbowjMvyEVSD6SPFyBpshDPgBU+YYw
References: <AANLkTimiOb29PRXVfDjVp5=Bt2L4hQ_FXychLbCdboaT@mail.gmail.com>
Subject: Re: [AVTCORE] New Packet formats section in Multipath RTP	(draft-singh-avtcore-mprtp-01)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Mar 2011 14:35:45 -0000

Hi,
I noticed that in the document you talk about RTCP header extension (section
8.1, 9.1) yet it looks to me like you define a new RTCP packet type and not
an extension to RTCP SR or RR. Please clarify and if you define new packets
it will be better to use one RTCP packet type.

Regards
Roni Even

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> varun singh
> Sent: Monday, March 14, 2011 11:57 PM
> To: avt@ietf.org
> Subject: [AVTCORE] New Packet formats section in Multipath RTP (draft-
> singh-avtcore-mprtp-01)
> 
> Greetings,
> 
> We have updated the draft and the latest iteration contains an updated
> section on Packet Formats (Section 9). In Section 9.3.1, we define a
> generic mechanism to reuse the session level reports (e.g., SR, RR,
> XR) for subflow-specific reports. An example non-compound subflow
> MPRTCP is shown in Figure 12.
> 
> For exact changes see
> http://tools.ietf.org/rfcdiff?url2=draft-singh-avtcore-mprtp-01.txt.
> 
> The draft contains some open issues (and some recommendations) that
> should be discussed here on the mailing so that we can move ahead and
> close them.
> 
> Regards,
> Varun
> 
> Begin forwarded message:
> 
> A new version of I-D, draft-singh-avtcore-mprtp-01.txt has been
> successfully submitted by Varun Singh and posted to the IETF
> repository.
> 
> Filename:	 draft-singh-avtcore-mprtp
> Revision:	 01
> Title:		 Multipath RTP (MPRTP)
> Creation_date:	 2011-03-14
> WG ID:		 Independent Submission
> Number_of_pages: 29
> 
> Abstract:
> The Real-time Transport Protocol (RTP) is used to deliver real-time
> content and, along with the RTP Control Protocol (RTCP), forms the
> control channel between the sender and receiver.  However, RTP and
> RTCP assume a single delivery path between the sender and receiver
> and make decisions based on the measured characteristics of this
> single path.  Increasingly, endpoints are becoming multi-homed, which
> means that they are connected via multiple Internet paths.  Network
> utilization can be improved when endpoints use multiple parallel
> paths for communication.  The resulting increase in reliability and
> throughput can also enhance the user experience.  This document
> extends the Real-time Transport Protocol (RTP) so that a single
> session can take advantage of the availability of multiple paths
> between two endpoints.
> 
> 
> 
> The IETF Secretariat.
> 
> 
> Varun Singh
> http://www.netlab.tkk.fi/~varun
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From vsingh.ietf@gmail.com  Fri Mar 18 04:42:19 2011
Return-Path: <vsingh.ietf@gmail.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D92E33A6800 for <avt@core3.amsl.com>; Fri, 18 Mar 2011 04:42:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.578
X-Spam-Level: 
X-Spam-Status: No, score=-3.578 tagged_above=-999 required=5 tests=[AWL=0.021,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6VNhUfcmx-4R for <avt@core3.amsl.com>; Fri, 18 Mar 2011 04:42:17 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 65A283A6869 for <avt@ietf.org>; Fri, 18 Mar 2011 04:42:17 -0700 (PDT)
Received: by fxm15 with SMTP id 15so3864676fxm.31 for <avt@ietf.org>; Fri, 18 Mar 2011 04:43:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=v5CSKii0uuuUoHbsX028DDrje+MhqY3esAXozvGpQD8=; b=OWf+wAkVrAeNrVxbdmnpcnFOwJraobiwndaEgI/P4wqrhTXdWtETBOvo17a8iGwbyE W/xLj83TPSElZF5krHSPYyX1Ao4fra9pe43Rnw/e7tL6n5ohxTWejTKEDTuqtBWlWyUc cuP5XpxPbKs/M0QCILAd+b09Y8D5ZO1rgxrmo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=UQ83lE5Jk4zE9a6ZlfnQWweBhjZmGMcsC42YSWDb8MeKFTwg5TCgZ5cdUy1Y1M8KJe EzB8DBD09zGG5HOpZml53Qb14NiMpzS0iRu7UprNUIix+QrUz6+rGL8k/QpDNB4osB54 lrK/Oienp/pf0hV4pFjYVfb0ns2w/xk0NEfio=
Received: by 10.223.27.14 with SMTP id g14mr1090321fac.129.1300448626130; Fri, 18 Mar 2011 04:43:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.104.211 with HTTP; Fri, 18 Mar 2011 04:43:26 -0700 (PDT)
In-Reply-To: <005e01cbe3e7$4142abb0$c3c80310$%roni@huawei.com>
References: <AANLkTimiOb29PRXVfDjVp5=Bt2L4hQ_FXychLbCdboaT@mail.gmail.com> <005e01cbe3e7$4142abb0$c3c80310$%roni@huawei.com>
From: varun singh <vsingh.ietf@gmail.com>
Date: Fri, 18 Mar 2011 13:43:26 +0200
Message-ID: <AANLkTimv+_mKb76hJ7wfTQDDXegLBFENwkHcciyZRKsQ@mail.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
Subject: Re: [AVTCORE] New Packet formats section in Multipath RTP (draft-singh-avtcore-mprtp-01)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Mar 2011 11:42:20 -0000

Hi Roni,


On Wed, Mar 16, 2011 at 16:34, Roni Even <Even.roni@huawei.com> wrote:
> Hi,
> I noticed that in the document you talk about RTCP header extension (sect=
ion
> 8.1, 9.1) yet it looks to me like you define a new RTCP packet type and n=
ot

We mean the latter, MPRTP requires new RTCP packet types.

> an extension to RTCP SR or RR. Please clarify and if you define new packe=
ts
> it will be better to use one RTCP packet type.

We will make alterations to the packet formats to reduce it to using
one RTCP packet type.
An alternative to a new RTCP packet type would be to define these RTCP
packets as App Packets (PT=3D204). However, I don't think MPRTP fits the
definition of Application defined packet.


Additionally, I'm also looking for comments on the packet format
defined in 9.3 (if reusing and re-encapsulating other RTCP packet
types) is a good idea or not.




>
> Regards
> Roni Even
>
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
>> varun singh
>> Sent: Monday, March 14, 2011 11:57 PM
>> To: avt@ietf.org
>> Subject: [AVTCORE] New Packet formats section in Multipath RTP (draft-
>> singh-avtcore-mprtp-01)
>>
>> Greetings,
>>
>> We have updated the draft and the latest iteration contains an updated
>> section on Packet Formats (Section 9). In Section 9.3.1, we define a
>> generic mechanism to reuse the session level reports (e.g., SR, RR,
>> XR) for subflow-specific reports. An example non-compound subflow
>> MPRTCP is shown in Figure 12.
>>
>> For exact changes see
>> http://tools.ietf.org/rfcdiff?url2=3Ddraft-singh-avtcore-mprtp-01.txt.
>>
>> The draft contains some open issues (and some recommendations) that
>> should be discussed here on the mailing so that we can move ahead and
>> close them.
>>
>> Regards,
>> Varun
>>
>> Begin forwarded message:
>>
>> A new version of I-D, draft-singh-avtcore-mprtp-01.txt has been
>> successfully submitted by Varun Singh and posted to the IETF
>> repository.
>>
>> Filename: =A0 =A0 =A0draft-singh-avtcore-mprtp
>> Revision: =A0 =A0 =A001
>> Title: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Multipath RTP (MPRTP)
>> Creation_date: =A0 =A0 =A0 =A0 2011-03-14
>> WG ID: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Independent Submission
>> Number_of_pages: 29
>>
>> Abstract:
>> The Real-time Transport Protocol (RTP) is used to deliver real-time
>> content and, along with the RTP Control Protocol (RTCP), forms the
>> control channel between the sender and receiver. =A0However, RTP and
>> RTCP assume a single delivery path between the sender and receiver
>> and make decisions based on the measured characteristics of this
>> single path. =A0Increasingly, endpoints are becoming multi-homed, which
>> means that they are connected via multiple Internet paths. =A0Network
>> utilization can be improved when endpoints use multiple parallel
>> paths for communication. =A0The resulting increase in reliability and
>> throughput can also enhance the user experience. =A0This document
>> extends the Real-time Transport Protocol (RTP) so that a single
>> session can take advantage of the availability of multiple paths
>> between two endpoints.
>>
>>
>>
>> The IETF Secretariat.
>>
>>
>> Varun Singh
>> http://www.netlab.tkk.fi/~varun
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>
>

From wwwrun@core3.amsl.com  Fri Mar 18 16:35:44 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 292CF3A6A83; Fri, 18 Mar 2011 16:35:43 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110318233544.292CF3A6A83@core3.amsl.com>
Date: Fri, 18 Mar 2011 16:35:44 -0700 (PDT)
Cc: keith.drage@alcatel-lucent.com, avt@ietf.org
Subject: [AVTCORE] WG Action: Conclusion of Audio/Video Transport (AVT)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Mar 2011 23:35:44 -0000

The Audio/Video Transport (AVT) working group in the Real-time
Applications and Infrastructure Area has concluded. Its work has been
distributed to the AVTCORE, AVTEXT, PAYLOAD, or XRBLOCK working groups. 
The IESG contact persons are Robert Sparks and Gonzalo Camarillo.

The mailing list will remain active as the list for the AVTCORE working
group.

From Even.roni@huawei.com  Sat Mar 19 01:34:35 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A343E3A6A0E for <avt@core3.amsl.com>; Sat, 19 Mar 2011 01:34:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.494
X-Spam-Level: 
X-Spam-Status: No, score=-102.494 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id npx6M4pnpKIR for <avt@core3.amsl.com>; Sat, 19 Mar 2011 01:34:34 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id C13B03A6A0D for <avt@ietf.org>; Sat, 19 Mar 2011 01:34:34 -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 <0LIA008MKQJT6Y@szxga05-in.huawei.com> for avt@ietf.org; Sat, 19 Mar 2011 16:35:53 +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 <0LIA00405QJSH8@szxga05-in.huawei.com> for avt@ietf.org; Sat, 19 Mar 2011 16:35:53 +0800 (CST)
Received: from windows8d787f9 (bzq-79-183-24-207.red.bezeqint.net [79.183.24.207]) by szxml11-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LIA00MVPQJLE2@szxml11-in.huawei.com> for avt@ietf.org; Sat, 19 Mar 2011 16:35:52 +0800 (CST)
Date: Sat, 19 Mar 2011 10:35:30 +0200
From: Roni Even <Even.roni@huawei.com>
To: avt@ietf.org
Message-id: <004101cbe610$9fcbf440$df63dcc0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_dG/EF1oKNzg8rlHPB0TEFA)"
Content-language: en-us
Thread-index: AcvmEJrOXNLSgxu4QjG5iDkuBoHm/g==
Subject: [AVTCORE] Question about draft-gharai-avtcore-rtp-tfrc-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Mar 2011 08:34:35 -0000

This is a multi-part message in MIME format.

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

Hi,

If I understand correctly there will be a new RTP header extension that must
be sent in every RTP packet. Will it not prevent the sender from using other
RTP header extensions.

Thank

Roni Even


--Boundary_(ID_dG/EF1oKNzg8rlHPB0TEFA)
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>If I understand correctly there will be a new RTP header extension that must be sent in every RTP packet. Will it not prevent the sender from using other RTP header extensions.<o:p></o:p></p><p class=MsoNormal>Thank<o:p></o:p></p><p class=MsoNormal>Roni Even<o:p></o:p></p></div></body></html>

--Boundary_(ID_dG/EF1oKNzg8rlHPB0TEFA)--

From csp@csperkins.org  Sat Mar 19 02:03:16 2011
Return-Path: <csp@csperkins.org>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3AA183A6A20 for <avt@core3.amsl.com>; Sat, 19 Mar 2011 02:03:16 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4RruzB8MnrSv for <avt@core3.amsl.com>; Sat, 19 Mar 2011 02:03:15 -0700 (PDT)
Received: from lon1-msapost-2.mail.demon.net (lon1-msapost-2.mail.demon.net [195.173.77.181]) by core3.amsl.com (Postfix) with ESMTP id E01923A6A0E for <avt@ietf.org>; Sat, 19 Mar 2011 02:03:14 -0700 (PDT)
Received: from starkperkins.demon.co.uk ([80.176.158.71] helo=[192.168.0.5]) by lon1-post-2.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1Q0s5U-00054f-ca; Sat, 19 Mar 2011 09:04:45 +0000
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <004101cbe610$9fcbf440$df63dcc0$%roni@huawei.com>
Date: Sat, 19 Mar 2011 09:04:42 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF587947-3A42-42D0-B808-E4F4CB7B0FF1@csperkins.org>
References: <004101cbe610$9fcbf440$df63dcc0$%roni@huawei.com>
To: Roni Even <Even.roni@huawei.com>
X-Mailer: Apple Mail (2.1082)
Cc: avt@ietf.org
Subject: Re: [AVTCORE] Question about draft-gharai-avtcore-rtp-tfrc-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Mar 2011 09:03:16 -0000

On 19 Mar 2011, at 08:35, Roni Even wrote:
> If I understand correctly there will be a new RTP header extension =
that must be sent in every RTP packet. Will it not prevent the sender =
from using other RTP header extensions.

It uses the RFC 5285 generic header extension mechanism, which allows =
stacking.

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




From Even.roni@huawei.com  Sat Mar 19 05:00:59 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF8933A6A9D for <avt@core3.amsl.com>; Sat, 19 Mar 2011 05:00:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.828
X-Spam-Level: 
X-Spam-Status: No, score=-103.828 tagged_above=-999 required=5 tests=[AWL=0.667, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LvXBMM7YRbDc for <avt@core3.amsl.com>; Sat, 19 Mar 2011 05:00:59 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id D5FBF3A6A97 for <avt@ietf.org>; Sat, 19 Mar 2011 05:00:58 -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 <0LIB00B4U03SY9@szxga04-in.huawei.com> for avt@ietf.org; Sat, 19 Mar 2011 20:02:16 +0800 (CST)
Received: from 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 <0LIB00E2503S9X@szxga04-in.huawei.com> for avt@ietf.org; Sat, 19 Mar 2011 20:02:16 +0800 (CST)
Received: from windows8d787f9 (bzq-79-183-24-207.red.bezeqint.net [79.183.24.207]) by szxml11-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LIB00MWH03JE2@szxml11-in.huawei.com>; Sat, 19 Mar 2011 20:02:16 +0800 (CST)
Date: Sat, 19 Mar 2011 14:01:51 +0200
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <DF587947-3A42-42D0-B808-E4F4CB7B0FF1@csperkins.org>
To: 'Colin Perkins' <csp@csperkins.org>
Message-id: <007e01cbe62d$7427bff0$5c773fd0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcvmFLWPI+9tJ+NkTsWX9jV/qMqxfAAGAcIg
References: <004101cbe610$9fcbf440$df63dcc0$%roni@huawei.com> <DF587947-3A42-42D0-B808-E4F4CB7B0FF1@csperkins.org>
Cc: avt@ietf.org
Subject: Re: [AVTCORE] Question about draft-gharai-avtcore-rtp-tfrc-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Mar 2011 12:01:00 -0000

Hi Colin,
Thanks for reminding me. I assume that you intend to update the draft if
there is an interest in the work.
I think that addressing mixers and translators may be good. Also address the
issues mentioned in RFC5968 about using it with TFRC (comment in figure 1)
and the limitations mentioned in section 3.2.

BTW: TFRC is now RFC5348
Thanks
Roni

> -----Original Message-----
> From: Colin Perkins [mailto:csp@csperkins.org]
> Sent: Saturday, March 19, 2011 11:05 AM
> To: Roni Even
> Cc: avt@ietf.org
> Subject: Re: [AVTCORE] Question about draft-gharai-avtcore-rtp-tfrc-00
> 
> On 19 Mar 2011, at 08:35, Roni Even wrote:
> > If I understand correctly there will be a new RTP header extension
> that must be sent in every RTP packet. Will it not prevent the sender
> from using other RTP header extensions.
> 
> It uses the RFC 5285 generic header extension mechanism, which allows
> stacking.
> 
> --
> Colin Perkins
> http://csperkins.org/
> 



From yekui.wang@huawei.com  Sun Mar 20 01:19:59 2011
Return-Path: <yekui.wang@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A6453A69ED; Sun, 20 Mar 2011 01:19:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5JmsHkOA3y1n; Sun, 20 Mar 2011 01:19:47 -0700 (PDT)
Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180]) by core3.amsl.com (Postfix) with ESMTP id 7E68D3A69D5; Sun, 20 Mar 2011 01:19:47 -0700 (PDT)
Received: from huawei.com (usaga04-in [172.18.4.101]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LIC00G0XKJIUU@usaga04-in.huawei.com>; Sun, 20 Mar 2011 03:21:18 -0500 (CDT)
Received: from dfweml201-edg.china.huawei.com ([172.18.9.107]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPS id <0LIC00M1ZKJHQP@usaga04-in.huawei.com>; Sun, 20 Mar 2011 03:21:17 -0500 (CDT)
Received: from DFWEML401-HUB.china.huawei.com (10.193.5.101) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.270.1; Sun, 20 Mar 2011 01:21:17 -0700
Received: from DFWEML504-MBX.china.huawei.com ([169.254.4.84]) by DFWEML401-HUB.china.huawei.com ([fe80::f07f:889f:78ef:8df3%13]) with mapi id 14.01.0270.001; Sun, 20 Mar 2011 01:20:46 -0700
Date: Sun, 20 Mar 2011 08:20:45 +0000
From: Ye-Kui Wang <yekui.wang@huawei.com>
X-Originating-IP: [10.47.82.122]
To: "payload@ietf.org" <payload@ietf.org>, "avt@ietf.org" <avt@ietf.org>
Message-id: <B99DECD58A94E143BA6F1508CC688351B417FB@dfweml504-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_1FJOVytJLbUE7c12TfBduA)"
Content-language: en-US
Accept-Language: en-US
Thread-topic: Some changes to rfc3984bis, SVC, and RCDO payload drafts
Thread-index: Acvm161AAF2A6AC0R/ODLEMZyh1Icg==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Subject: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Mar 2011 08:19:59 -0000

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

Folks,

The three H.264/AVC related payload formats, namely, draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-rtp-svc-27, and draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48 stage.

The RFC-Editor has found the following problem: In draft-ietf-avt-rtp-rfc3984bis-12, the definition of the max-dpb media parameter refers to the MaxDPB that was defined the first version of the H.264/AVC spec, but not any more in the latest version (the 2010 version). The parameter in the latest H.264/AVC version corresponding to MaxDPB is MaxDpbMbs, and the unit of the new parameter (i.e., macroblocks) is different from the original one (i.e. 1024 bytes).

The problem applies also to the SVC payload format, the RCDO payload format, and H.241.

A solution has been found and agreed, involving rfc3984bis authors and some key people related to H.264/AVC (e.g., Gary Sullivan and Heiko Schwarz) and H.241 (e.g., Stephen Botzko and Patrick Luthi). Furthermore, we have found that there are also a couple of places that need fixes due to similar changes from the initial version of H.264/AVC to the latest version.

Per Roni's suggestion, I am sending in below the changes to draft-ietf-avt-rtp-rfc3984bis-12 for review by the Payload and AVTcore WGs. It seems that exactly the same changes are needed to draft-ietf-avt-rtp-h264-rcdo-08 (co-authors of this draft may confirm), and similar but slightly different changes are needed to draft-ietf-avt-rtp-svc-27.

Since the drafts are at the AUTH48 stage, please provide comments by Monday, March 21, if any. Many thanks!

BR, YK



------------------------------------Start of suggested changes --------------------------------------

Section 8.1:
OLD:

      profile-level-id:

         A base16 [7] (hexadecimal) representation of the following

         three bytes in the sequence parameter set NAL unit is specified

         in [1]: 1) profile_idc, 2) a byte herein referred to as

         profile-iop, composed of the values of constraint_set0_flag,

         constraint_set1_flag,constraint_set2_flag,

         constraint_set3_flag, and reserved_zero_4bits in bit-

         significance order, starting from the most-significant bit, and

         3) level_idc.  Note that reserved_zero_4bits is required to be

         equal to 0 in [1], but other values for it may be specified in

         the future by ITU-T or ISO/IEC.
 NEW:
      profile-level-id:
         A base16 [7] (hexadecimal) representation of the following
         three bytes in the sequence parameter set NAL unit is specified
         in [1]: 1) profile_idc, 2) a byte herein referred to as
         profile-iop, composed of the values of constraint_set0_flag,
         constraint_set1_flag,constraint_set2_flag,
         constraint_set3_flag, constraint_set4_flag, constraint_set5_flag,
 and reserved_zero_2bits in bit-significance order, starting from the most-significant bit, and
         3) level_idc.  Note that reserved_zero_2bits is required to be
         equal to 0 in [1], but other values for it may be specified in
         the future by ITU-T or ISO/IEC.

OLD:

         For example, in the table above, profile_idc equal to 58

         (Extended) with profile-iop equal to 11xx0000 indicates the

         same sub-profile corresponding to profile_idc equal to 42

         (Baseline) with profile-iop equal to x1xx0000.  Note that other

         combinations of profile_idc and profile-iop (not listed in

         Table 5) may represent a sub-profile equivalent to the common

         subset of coding tools for more than one profile.  Note also

         that a decoder conforming to a certain profile may be able to

         decode bitstreams conforming to other profiles.  For example, a

         decoder conforming to the High 4:4:4 profile, at a certain

         level, must be able to decode bitstreams conforming to the

         Constrained Baseline, Main, High, High 10, or High 4:2:2

         profile at the same or a lower level.
 NEW:
         For example, in the table above, profile_idc equal to 58
         (Extended) with profile-iop equal to 11xx0000 indicates the
         same sub-profile corresponding to profile_idc equal to 42
         (Baseline) with profile-iop equal to x1xx0000.  Note that other
         combinations of profile_idc and profile-iop (not listed in
         Table 5) may represent a sub-profile equivalent to the common
         subset of coding tools for more than one profile.  Note also
         that a decoder conforming to a certain profile may be able to
         decode bitstreams conforming to other profiles.

OLD:

         If the profile-level-id parameter is used for capability

         exchange or session setup procedure, it indicates the subset of

         coding tools, which is equal to the default sub-profile, that

         the codec supports for both receiving and sending.
 NEW:
         If the profile-level-id parameter is used for capability
         exchange or session setup, it indicates the subset of
         coding tools, which is equal to the default sub-profile, that
         the codec supports for both receiving and sending.

OLD:
      max-cpb: The value of max-cpb is an integer indicating the maximum
         coded picture buffer size in units of 1000 bits for the VCL HRD
         parameters (see A.3.1, item i of [1]) and in units of 1200 bits
         for the NAL HRD parameters (see A.3.1, item j of [1]).
NEW:
      max-cpb: The value of max-cpb is an integer indicating the maximum
         coded picture buffer size. For Constrained Baseline, Baseline, Main
and Extended profiles, the unit is 1000 bits for the VCL HRD
         parameters and 1200 bits for the NAL HRD parameters. For High, High 10,
High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra,
High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles, the unit is cpbBrVclFactor
bits for the VCL HRD and cpbBrNalFactor bits for the NAL HRD parameters.

OLD:
      max-dpb: The value of max-dpb is an integer indicating the maximum
         decoded picture buffer size in units of 1024 bytes.  The max-
         dpb parameter signals that the receiver has more memory than
         the minimum amount of decoded picture buffer memory required by
         the signaled highest level conveyed in the value of the
         profile-level-id parameter or the max-recv-level parameter.
         When max-dpb is signaled, the receiver MUST be able to decode
         NAL unit streams that conform to the signaled highest level,
         with the exception that the MaxDPB value in Table A-1 of [1]
         for the signaled highest level is replaced with the value of
         max-dpb.  Consequently, a receiver that signals max-dpb MUST be
         capable of storing the following number of decoded frames,
         complementary field pairs, and non-paired fields in its decoded
         picture buffer:

            Min(1024 * max-dpb / ( PicWidthInMbs * FrameHeightInMbs *
            256 * ChromaFormatFactor ), 16)

         PicWidthInMbs, FrameHeightInMbs, and ChromaFormatFactor are
         defined in [1].

         The value of max-dpb MUST be greater than or equal to the value
         of MaxDPB given in Table A-1 of [1] for the highest level.
         Senders MAY use this knowledge to construct coded video streams
         with improved compression.
NEW:
      max-dpb: The value of max-dpb is an integer indicating the maximum
         decoded picture buffer size in units of 8/3 macroblocks.  The max-
         dpb parameter signals that the receiver has more memory than
         the minimum amount of decoded picture buffer memory required by
         the signaled highest level conveyed in the value of the
         profile-level-id parameter or the max-recv-level parameter.
         When max-dpb is signaled, the receiver MUST be able to decode
         NAL unit streams that conform to the signaled highest level,
         with the exception that the MaxDpbMbs value in Table A-1 of [1]
         for the signaled highest level is replaced with the value of
         max-dpb * 3 / 8.  Consequently, a receiver that signals max-dpb MUST be
         capable of storing the following number of decoded frames,
         complementary field pairs, and non-paired fields in its decoded
         picture buffer:

            Min(max-dpb * 3 / 8 / ( PicWidthInMbs * FrameHeightInMbs), 16)

         Wherein PicWidthInMbs and FrameHeightInMbs are defined in [1].

         The value of max-dpb MUST be greater than or equal to the value
         of MaxDpbMbs * 3 / 8, wherein the value of MaxDpbMbs is given in
Table A-1 of [1] for the highest level.
         Senders MAY use this knowledge to construct coded video streams
         with improved compression.

OLD:

      max-br: The value of max-br is an integer indicating the maximum

         video bitrate in units of 1000 bits per second for the VCL HRD

         parameters (see A.3.1, item i of [1]) and in units of 1200 bits

         per second for the NAL HRD parameters (see A.3.1, item j of

         [1]).

         ...
         For example, if a receiver signals capability for Level 1.2
         with max-br equal to 1550, this indicates a maximum video
         bitrate of 1550 kbits/sec for VCL HRD parameters, a maximum
         video bitrate of 1860 kbits/sec for NAL HRD parameters, and a
         CPB size of 4036458 bits (1550000 / 384000 * 1000 * 1000).
NEW:

      max-br: The value of max-br is an integer indicating the maximum
         video bitrate.  For Constrained Baseline, Baseline, Main
and Extended profiles, the unit is 1000 bits per second for the VCL HRD
         parameters and 1200 bits per second for the NAL HRD parameters. For High, High 10,
High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra,
High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles, the unit is cpbBrVclFactor
bits per second for the VCL HRD and cpbBrNalFactor bits per second for the NAL HRD parameters.

         ...
         For example, if a receiver signals capability for Main profile Level 1.2
         with max-br equal to 1550, this indicates a maximum video
         bitrate of 1550 kbits/sec for VCL HRD parameters, a maximum
         video bitrate of 1860 kbits/sec for NAL HRD parameters, and a
         CPB size of 4036458 bits (1550000 / 384000 * 1000 * 1000).


------------------------------------End of suggested changes --------------------------------------


--Boundary_(ID_1FJOVytJLbUE7c12TfBduA)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* 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:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:SimSun;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:SimSun;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
 /* Page Definitions */
 @page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple" style=3D"text-justify-t=
rim:punctuation">
<div class=3D"Section1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Folks,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The three H.264/AVC related pay=
load formats, namely, draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-rtp-=
svc-27, and draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48 stage.<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The RFC-Editor has found the fo=
llowing problem: In draft-ietf-avt-rtp-rfc3984bis-12, the definition of the=
 max-dpb media parameter refers to the MaxDPB that was defined the first ve=
rsion of the H.264/AVC spec, but not
 any more in the latest version (the 2010 version). The parameter in the la=
test H.264/AVC version corresponding to MaxDPB is MaxDpbMbs, and the unit o=
f the new parameter (i.e., macroblocks) is different from the original one =
(i.e. 1024 bytes).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The problem applies also to the=
 SVC payload format, the RCDO payload format, and H.241.<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">A solution has been found and a=
greed, involving rfc3984bis authors and some key people related to H.264/AV=
C (e.g., Gary Sullivan and Heiko Schwarz) and H.241 (e.g., Stephen Botzko a=
nd Patrick Luthi). Furthermore, we have
 found that there are also a couple of places that need fixes due to simila=
r changes from the initial version of H.264/AVC to the latest version.<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Per Roni&#8217;s suggestion, I =
am sending in below the changes to draft-ietf-avt-rtp-rfc3984bis-12 for rev=
iew by the Payload and AVTcore WGs. It seems that exactly the same changes =
are needed to draft-ietf-avt-rtp-h264-rcdo-08
 (co-authors of this draft may confirm), and similar but slightly different=
 changes are needed to draft-ietf-avt-rtp-svc-27.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Since the drafts are at the AUT=
H48 stage, please provide comments by Monday, March 21, if any. Many thanks=
!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">BR, YK<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">----------------------------=
--------Start of suggested changes --------------------------------------<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Section=
 8.1:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">OLD:<o:=
p></o:p></span></p>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; profile-level-id:<=
o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
A base16 [7] (hexadecimal) representation of the following<o:p></o:p></span=
></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
three bytes in the sequence parameter set NAL unit is specified<o:p></o:p><=
/span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
in [1]: 1) profile_idc, 2) a byte herein referred to as<o:p></o:p></span></=
pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;=
profile-iop, composed of the values of constraint_set0_flag,<o:p></o:p></sp=
an></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
constraint_set1_flag,constraint_set2_flag,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
constraint_set3_flag, and reserved_zero_4bits in bit-<o:p></o:p></span></pr=
e>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
significance order, starting from the most-significant bit, and<o:p></o:p><=
/span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;=
3) level_idc.&nbsp; Note that reserved_zero_4bits is required to be<o:p></o=
:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
equal to 0 in [1], but other values for it may be specified in<o:p></o:p></=
span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
the future by ITU-T or ISO/IEC.<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;N=
EW:<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; profile-level-id:<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A base16 [7] (hexadecimal) representation of=
 the following<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; three bytes in the sequence parameter set NA=
L unit is specified<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in [1]: 1) profile_idc, 2) a byte herein ref=
erred to as<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; profile-iop, composed of the values of const=
raint_set0_flag,<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; constraint_set1_flag,constraint_set2_flag,<o=
:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; constraint_set3_flag, constraint_set4_flag, =
constraint_set5_flag,<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-indent:=
48.0pt"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">=
&nbsp;and reserved_zero_2bits in bit-significance order, starting from the =
most-significant bit, and<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3) level_idc.&nbsp; Note that reserved_zero_=
2bits is required to be<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; equal to 0 in [1], but other values for it m=
ay be specified in<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the future by ITU-T or ISO/IEC.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">OLD:<o:=
p></o:p></span></p>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
For example, in the table above, profile_idc equal to 58<o:p></o:p></span><=
/pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
(Extended) with profile-iop equal to 11xx0000 indicates the<o:p></o:p></spa=
n></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
same sub-profile corresponding to profile_idc equal to 42<o:p></o:p></span>=
</pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
(Baseline) with profile-iop equal to x1xx0000.&nbsp; Note that other<o:p></=
o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
combinations of profile_idc and profile-iop (not listed in<o:p></o:p></span=
></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Table 5) may represent a sub-profile equivalent to the common<o:p></o:p></s=
pan></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
subset of coding tools for more than one profile.&nbsp; Note also<o:p></o:p=
></span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
that a decoder conforming to a certain profile may be able to<o:p></o:p></s=
pan></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
decode bitstreams conforming to other profiles.&nbsp; For example, a<o:p></=
o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=
decoder conforming to the High 4:4:4 profile, at a certain<o:p></o:p></span=
></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
level, must be able to decode bitstreams conforming to the<o:p></o:p></span=
></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Constrained Baseline, Main, High, High 10, or High 4:2:2<o:p></o:p></span><=
/pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
profile at the same or a lower level.<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;N=
EW:<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;For example, in the table above, profile_idc=
 equal to 58<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (Extended) with profile-iop equal to 11xx000=
0 indicates the<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; same sub-profile corresponding to profile_id=
c equal to 42<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (Baseline) with profile-iop equal to x1xx000=
0.&nbsp; Note that other<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; combinations of profile_idc and profile-iop =
(not listed in<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Table 5) may represent a sub-profile equival=
ent to the common<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; subset of coding tools for more than one pro=
file.&nbsp; Note also<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that a decoder conforming to a certain profi=
le may be able to<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; decode bitstreams conforming to other profil=
es.<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">OLD:<o:=
p></o:p></span></p>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
If the profile-level-id parameter is used for capability<o:p></o:p></span><=
/pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
exchange or session setup procedure, it indicates the subset of<o:p></o:p><=
/span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
coding tools, which is equal to the default sub-profile, that<o:p></o:p></s=
pan></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
the codec supports for both receiving and sending.<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;N=
EW:<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If the profile-level-id parameter is used fo=
r capability<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; exchange or session setup, it indicates the =
subset of<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;coding tools, which is equal to the default =
sub-profile, that<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the codec supports for both receiving and se=
nding.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">OLD:<o:=
p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; max-cpb: The value of max-cpb is an integer indicating the max=
imum<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; coded picture buffer size in units of 1000 b=
its for the VCL HRD<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; parameters (see A.3.1, item i of [1]) and in=
 units of 1200 bits<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the NAL HRD parameters (see A.3.1, item =
j of [1]).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">NEW:<o:=
p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; max-cpb: The value of max-cpb is an integer indicating the max=
imum<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; coded picture buffer size. For Constrained B=
aseline, Baseline, Main
<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-indent:=
54.0pt"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">=
and Extended profiles, the unit is 1000 bits for the VCL HRD<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; parameters and 1200 bits for the NAL HRD par=
ameters. For High, High 10,<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-indent:=
54.0pt"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">=
High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra,
<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-indent:=
54.0pt"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">=
High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles, the unit is cpbBrVclFactor=
<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-indent:=
54.0pt"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">=
bits for the VCL HRD and cpbBrNalFactor bits for the NAL HRD parameters.<o:=
p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">OLD:<o:=
p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; max-dpb: The value of max-dpb is an integer indicating the max=
imum<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; decoded picture buffer size in units of 1024=
 bytes.&nbsp; The max-<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dpb parameter signals that the receiver has =
more memory than<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the minimum amount of decoded picture buffer=
 memory required by<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the signaled highest level conveyed in the v=
alue of the<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; profile-level-id parameter or the max-recv-l=
evel parameter.<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When max-dpb is signaled, the receiver MUST =
be able to decode<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAL unit streams that conform to the signale=
d highest level,<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with the exception that the MaxDPB value in =
Table A-1 of [1]<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the signaled highest level is replaced w=
ith the value of<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-dpb.&nbsp; Consequently, a receiver that=
 signals max-dpb MUST be<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; capable of storing the following number of d=
ecoded frames,<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;complementary field pairs, and non-paired fi=
elds in its decoded<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; picture buffer:<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p><=
/span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Min(1024 * max-dpb / ( Pic=
WidthInMbs * FrameHeightInMbs *<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 256 * ChromaFormatFactor )=
, 16)<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p><=
/span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PicWidthInMbs, FrameHeightInMbs, and ChromaF=
ormatFactor are<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; defined in [1].<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p><=
/span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The value of max-dpb MUST be greater than or=
 equal to the value<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of MaxDPB given in Table A-1 of [1] for the =
highest level.<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Senders MAY use this knowledge to construct =
coded video streams<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with improved compression.<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">NEW:<o:=
p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; max-dpb: The value of max-dpb is an integer indicating the max=
imum<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; decoded picture buffer size in units of 8/3 =
macroblocks.&nbsp; The max-<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dpb parameter signals that the receiver has =
more memory than<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the minimum amount of decoded picture buffer=
 memory required by<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the signaled highest level conveyed in the v=
alue of the<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; profile-level-id parameter or the max-recv-l=
evel parameter.<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When max-dpb is signaled, the receiver MUST =
be able to decode<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAL unit streams that conform to the signale=
d highest level,<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with the exception that the MaxDpbMbs value =
in Table A-1 of [1]<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the signaled highest level is replaced w=
ith the value of<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-dpb * 3 / 8.&nbsp; Consequently, a recei=
ver that signals max-dpb MUST be<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; capable of storing the following number of d=
ecoded frames,<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; complementary field pairs, and non-paired fi=
elds in its decoded<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; picture buffer:<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p><=
/span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Min(max-dpb * 3 / 8 / ( Pi=
cWidthInMbs * FrameHeightInMbs), 16)<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p><=
/span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Wherein PicWidthInMbs and FrameHeightInMbs a=
re defined in [1].<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p><=
/span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The value of max-dpb MUST be greater than or=
 equal to the value<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of MaxDpbMbs * 3 / 8, wherein the value of M=
axDpbMbs is given in
<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-indent:=
54.0pt"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">=
Table A-1 of [1] for the highest level.<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Senders MAY use this knowledge to construct =
coded video streams<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with improved compression.<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">OLD:<o:=
p></o:p></span></p>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-br: The value =
of max-br is an integer indicating the maximum<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
video bitrate in units of 1000 bits per second for the VCL HRD<o:p></o:p></=
span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
parameters (see A.3.1, item i of [1]) and in units of 1200 bits<o:p></o:p><=
/span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
per second for the NAL HRD parameters (see A.3.1, item j of<o:p></o:p></spa=
n></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[1]).<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>&#8230;<span lang=3D"EN-US"><o:p></o:p></span></pre>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; For example, if a receiver signals capabilit=
y for Level 1.2<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with max-br equal to 1550, this indicates a =
maximum video<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bitrate of 1550 kbits/sec for VCL HRD parame=
ters, a maximum<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; video bitrate of 1860 kbits/sec for NAL HRD =
parameters, and a<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CPB size of 4036458 bits (1550000 / 384000 *=
 1000 * 1000).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">NEW: <o=
:p></o:p></span></p>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-br: The value =
of max-br is an integer indicating the maximum<o:p></o:p></span></pre>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; video bitrate.&nbsp; For Constrained Baselin=
e, Baseline, Main
<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-indent:=
54.0pt"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">=
and Extended profiles, the unit is 1000 bits per second for the VCL HRD<o:p=
></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; parameters and 1200 bits per second for the =
NAL HRD parameters. For High, High 10,<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-indent:=
54.0pt"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">=
High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra,
<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-indent:=
54.0pt"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">=
High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles, the unit is cpbBrVclFactor=
<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-indent:=
54.0pt"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">=
bits per second for the VCL HRD and cpbBrNalFactor bits per second for the =
NAL HRD parameters.<o:p></o:p></span></p>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>&#8230;<span lang=3D"EN-US"><o:p></o:p></span></pre>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; For example, if a receiver signals capabilit=
y for Main profile Level 1.2<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with max-br equal to 1550, this indicates a =
maximum video<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bitrate of 1550 kbits/sec for VCL HRD parame=
ters, a maximum<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; video bitrate of 1860 kbits/sec for NAL HRD =
parameters, and a<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CPB size of 4036458 bits (1550000 / 384000 *=
 1000 * 1000).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">----------------------------=
--------End of suggested changes --------------------------------------<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--Boundary_(ID_1FJOVytJLbUE7c12TfBduA)--

From yekui.wang@huawei.com  Sun Mar 20 01:22:56 2011
Return-Path: <yekui.wang@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 782DD3A69ED; Sun, 20 Mar 2011 01:22:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NvwMqiMg6-kq; Sun, 20 Mar 2011 01:22:55 -0700 (PDT)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id EF46B3A69D5; Sun, 20 Mar 2011 01:22:54 -0700 (PDT)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LIC00CR8KOP46@usaga02-in.huawei.com>; Sun, 20 Mar 2011 01:24:26 -0700 (PDT)
Received: from dfweml202-edg.china.huawei.com ([172.18.9.108]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPS id <0LIC00FJ7KOPWR@usaga02-in.huawei.com>; Sun, 20 Mar 2011 01:24:25 -0700 (PDT)
Received: from DFWEML402-HUB.china.huawei.com (10.193.5.102) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.270.1; Sun, 20 Mar 2011 01:24:25 -0700
Received: from DFWEML504-MBX.china.huawei.com ([169.254.4.84]) by DFWEML402-HUB.china.huawei.com ([::1]) with mapi id 14.01.0270.001; Sun, 20 Mar 2011 01:24:24 -0700
Date: Sun, 20 Mar 2011 08:24:24 +0000
From: Ye-Kui Wang <yekui.wang@huawei.com>
X-Originating-IP: [10.47.82.122]
To: "payload@ietf.org" <payload@ietf.org>, "avt@ietf.org" <avt@ietf.org>
Message-id: <B99DECD58A94E143BA6F1508CC688351B41818@dfweml504-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: en-US
Content-transfer-encoding: base64
Accept-Language: en-US
Thread-topic: Some changes to rfc3984bis, SVC, and RCDO payload drafts
Thread-index: Acvm161AAF2A6AC0R/ODLEMZyh1IcgAAG9Hg
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Mar 2011 08:22:56 -0000

Rm9sa3MsDQoNClRoZSB0aHJlZSBILjI2NC9BVkMgcmVsYXRlZCBwYXlsb2FkIGZvcm1hdHMsIG5h
bWVseSwgZHJhZnQtaWV0Zi1hdnQtcnRwLXJmYzM5ODRiaXMtMTIsIGRyYWZ0LWlldGYtYXZ0LXJ0
cC1zdmMtMjcsIGFuZCBkcmFmdC1pZXRmLWF2dC1ydHAtaDI2NC1yY2RvLTA4LCBhcmUgYWxsIGF0
IHRoZSBBVVRINDggc3RhZ2UuDQoNClRoZSBSRkMtRWRpdG9yIGhhcyBmb3VuZCB0aGUgZm9sbG93
aW5nIHByb2JsZW06IEluIGRyYWZ0LWlldGYtYXZ0LXJ0cC1yZmMzOTg0YmlzLTEyLCB0aGUgZGVm
aW5pdGlvbiBvZiB0aGUgbWF4LWRwYiBtZWRpYSBwYXJhbWV0ZXIgcmVmZXJzIHRvIHRoZSBNYXhE
UEIgdGhhdCB3YXMgZGVmaW5lZCB0aGUgZmlyc3QgdmVyc2lvbiBvZiB0aGUgSC4yNjQvQVZDIHNw
ZWMsIGJ1dCBub3QgYW55IG1vcmUgaW4gdGhlIGxhdGVzdCB2ZXJzaW9uICh0aGUgMjAxMCB2ZXJz
aW9uKS4gVGhlIHBhcmFtZXRlciBpbiB0aGUgbGF0ZXN0IEguMjY0L0FWQyB2ZXJzaW9uIGNvcnJl
c3BvbmRpbmcgdG8gTWF4RFBCIGlzIE1heERwYk1icywgYW5kIHRoZSB1bml0IG9mIHRoZSBuZXcg
cGFyYW1ldGVyIChpLmUuLCBtYWNyb2Jsb2NrcykgaXMgZGlmZmVyZW50IGZyb20gdGhlIG9yaWdp
bmFsIG9uZSAoaS5lLiAxMDI0IGJ5dGVzKS4NCg0KVGhlIHByb2JsZW0gYXBwbGllcyBhbHNvIHRv
IHRoZSBTVkMgcGF5bG9hZCBmb3JtYXQsIHRoZSBSQ0RPIHBheWxvYWQgZm9ybWF0LCBhbmQgSC4y
NDEuDQoNCkEgc29sdXRpb24gaGFzIGJlZW4gZm91bmQgYW5kIGFncmVlZCwgaW52b2x2aW5nIHJm
YzM5ODRiaXMgYXV0aG9ycyBhbmQgc29tZSBrZXkgcGVvcGxlIHJlbGF0ZWQgdG8gSC4yNjQvQVZD
IChlLmcuLCBHYXJ5IFN1bGxpdmFuIGFuZCBIZWlrbyBTY2h3YXJ6KSBhbmQgSC4yNDEgKGUuZy4s
IFN0ZXBoZW4gQm90emtvIGFuZCBQYXRyaWNrIEx1dGhpKS4gRnVydGhlcm1vcmUsIHdlIGhhdmUg
Zm91bmQgdGhhdCB0aGVyZSBhcmUgYWxzbyBhIGNvdXBsZSBvZiBwbGFjZXMgdGhhdCBuZWVkIGZp
eGVzIGR1ZSB0byBzaW1pbGFyIGNoYW5nZXMgZnJvbSB0aGUgaW5pdGlhbCB2ZXJzaW9uIG9mIEgu
MjY0L0FWQyB0byB0aGUgbGF0ZXN0IHZlcnNpb24uDQoNClBlciBSb25p4oCZcyBzdWdnZXN0aW9u
LCBJIGFtIHNlbmRpbmcgaW4gYmVsb3cgdGhlIGNoYW5nZXMgdG8gZHJhZnQtaWV0Zi1hdnQtcnRw
LXJmYzM5ODRiaXMtMTIgZm9yIHJldmlldyBieSB0aGUgUGF5bG9hZCBhbmQgQVZUY29yZSBXR3Mu
IEl0IHNlZW1zIHRoYXQgZXhhY3RseSB0aGUgc2FtZSBjaGFuZ2VzIGFyZSBuZWVkZWQgdG8gZHJh
ZnQtaWV0Zi1hdnQtcnRwLWgyNjQtcmNkby0wOCAoY28tYXV0aG9ycyBvZiB0aGlzIGRyYWZ0IG1h
eSBjb25maXJtKSwgYW5kIHNpbWlsYXIgYnV0IHNsaWdodGx5IGRpZmZlcmVudCBjaGFuZ2VzIGFy
ZSBuZWVkZWQgdG8gZHJhZnQtaWV0Zi1hdnQtcnRwLXN2Yy0yNy4NCg0KU2luY2UgdGhlIGRyYWZ0
cyBhcmUgYXQgdGhlIEFVVEg0OCBzdGFnZSwgcGxlYXNlIHByb3ZpZGUgY29tbWVudHMgYnkgTW9u
ZGF5LCBNYXJjaCAyMSwgaWYgYW55LiBNYW55IHRoYW5rcyENCg0KQlIsIFlLDQoNCg0KLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tU3RhcnQgb2Ygc3VnZ2VzdGVkIGNoYW5nZXMg
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KU2VjdGlvbiA4LjE6DQpP
TEQ6DQrCoMKgwqDCoMKgIHByb2ZpbGUtbGV2ZWwtaWQ6DQrCoMKgwqDCoMKgwqDCoMKgIEEgYmFz
ZTE2IFs3XSAoaGV4YWRlY2ltYWwpIHJlcHJlc2VudGF0aW9uIG9mIHRoZSBmb2xsb3dpbmcNCsKg
wqDCoMKgwqDCoMKgwqAgdGhyZWUgYnl0ZXMgaW4gdGhlIHNlcXVlbmNlIHBhcmFtZXRlciBzZXQg
TkFMIHVuaXQgaXMgc3BlY2lmaWVkDQrCoMKgwqDCoMKgwqDCoMKgIGluIFsxXTogMSkgcHJvZmls
ZV9pZGMsIDIpIGEgYnl0ZSBoZXJlaW4gcmVmZXJyZWQgdG8gYXMNCsKgwqDCoMKgwqDCoCDCoMKg
cHJvZmlsZS1pb3AsIGNvbXBvc2VkIG9mIHRoZSB2YWx1ZXMgb2YgY29uc3RyYWludF9zZXQwX2Zs
YWcsDQrCoMKgwqDCoMKgwqDCoMKgIGNvbnN0cmFpbnRfc2V0MV9mbGFnLGNvbnN0cmFpbnRfc2V0
Ml9mbGFnLA0KwqDCoMKgwqDCoMKgwqDCoCBjb25zdHJhaW50X3NldDNfZmxhZywgYW5kIHJlc2Vy
dmVkX3plcm9fNGJpdHMgaW4gYml0LQ0KwqDCoMKgwqDCoMKgwqDCoCBzaWduaWZpY2FuY2Ugb3Jk
ZXIsIHN0YXJ0aW5nIGZyb20gdGhlIG1vc3Qtc2lnbmlmaWNhbnQgYml0LCBhbmQNCsKgwqDCoMKg
IMKgwqDCoMKgMykgbGV2ZWxfaWRjLsKgIE5vdGUgdGhhdCByZXNlcnZlZF96ZXJvXzRiaXRzIGlz
IHJlcXVpcmVkIHRvIGJlDQrCoMKgwqDCoMKgwqDCoMKgIGVxdWFsIHRvIDAgaW4gWzFdLCBidXQg
b3RoZXIgdmFsdWVzIGZvciBpdCBtYXkgYmUgc3BlY2lmaWVkIGluDQrCoMKgwqDCoMKgwqDCoMKg
IHRoZSBmdXR1cmUgYnkgSVRVLVQgb3IgSVNPL0lFQy4NCsKgTkVXOg0KwqDCoMKgwqDCoCBwcm9m
aWxlLWxldmVsLWlkOg0KwqDCoMKgwqDCoMKgwqDCoCBBIGJhc2UxNiBbN10gKGhleGFkZWNpbWFs
KSByZXByZXNlbnRhdGlvbiBvZiB0aGUgZm9sbG93aW5nDQrCoMKgwqDCoMKgwqDCoMKgIHRocmVl
IGJ5dGVzIGluIHRoZSBzZXF1ZW5jZSBwYXJhbWV0ZXIgc2V0IE5BTCB1bml0IGlzIHNwZWNpZmll
ZA0KwqDCoMKgwqDCoMKgwqDCoCBpbiBbMV06IDEpIHByb2ZpbGVfaWRjLCAyKSBhIGJ5dGUgaGVy
ZWluIHJlZmVycmVkIHRvIGFzDQrCoMKgwqDCoMKgwqDCoMKgIHByb2ZpbGUtaW9wLCBjb21wb3Nl
ZCBvZiB0aGUgdmFsdWVzIG9mIGNvbnN0cmFpbnRfc2V0MF9mbGFnLA0KwqDCoMKgwqDCoMKgwqDC
oCBjb25zdHJhaW50X3NldDFfZmxhZyxjb25zdHJhaW50X3NldDJfZmxhZywNCsKgwqDCoMKgwqDC
oMKgwqAgY29uc3RyYWludF9zZXQzX2ZsYWcsIGNvbnN0cmFpbnRfc2V0NF9mbGFnLCBjb25zdHJh
aW50X3NldDVfZmxhZywNCuOAgOOAgOOAgOOAgMKgYW5kIHJlc2VydmVkX3plcm9fMmJpdHMgaW4g
Yml0LXNpZ25pZmljYW5jZSBvcmRlciwgc3RhcnRpbmcgZnJvbSB0aGUgbW9zdC1zaWduaWZpY2Fu
dCBiaXQsIGFuZA0KwqDCoMKgwqDCoMKgwqDCoCAzKSBsZXZlbF9pZGMuwqAgTm90ZSB0aGF0IHJl
c2VydmVkX3plcm9fMmJpdHMgaXMgcmVxdWlyZWQgdG8gYmUNCsKgwqDCoMKgwqDCoMKgwqAgZXF1
YWwgdG8gMCBpbiBbMV0sIGJ1dCBvdGhlciB2YWx1ZXMgZm9yIGl0IG1heSBiZSBzcGVjaWZpZWQg
aW4NCsKgwqDCoMKgwqDCoMKgwqAgdGhlIGZ1dHVyZSBieSBJVFUtVCBvciBJU08vSUVDLg0KDQpP
TEQ6DQrCoMKgwqDCoMKgwqDCoMKgIEZvciBleGFtcGxlLCBpbiB0aGUgdGFibGUgYWJvdmUsIHBy
b2ZpbGVfaWRjIGVxdWFsIHRvIDU4DQrCoMKgwqDCoMKgwqDCoMKgIChFeHRlbmRlZCkgd2l0aCBw
cm9maWxlLWlvcCBlcXVhbCB0byAxMXh4MDAwMCBpbmRpY2F0ZXMgdGhlDQrCoMKgwqDCoMKgwqDC
oMKgIHNhbWUgc3ViLXByb2ZpbGUgY29ycmVzcG9uZGluZyB0byBwcm9maWxlX2lkYyBlcXVhbCB0
byA0Mg0KwqDCoMKgwqDCoMKgwqDCoCAoQmFzZWxpbmUpIHdpdGggcHJvZmlsZS1pb3AgZXF1YWwg
dG8geDF4eDAwMDAuwqAgTm90ZSB0aGF0IG90aGVyDQrCoMKgwqDCoMKgwqDCoMKgIGNvbWJpbmF0
aW9ucyBvZiBwcm9maWxlX2lkYyBhbmQgcHJvZmlsZS1pb3AgKG5vdCBsaXN0ZWQgaW4NCsKgwqDC
oMKgwqDCoMKgwqAgVGFibGUgNSkgbWF5IHJlcHJlc2VudCBhIHN1Yi1wcm9maWxlIGVxdWl2YWxl
bnQgdG8gdGhlIGNvbW1vbg0KwqDCoMKgwqDCoMKgwqDCoCBzdWJzZXQgb2YgY29kaW5nIHRvb2xz
IGZvciBtb3JlIHRoYW4gb25lIHByb2ZpbGUuwqAgTm90ZSBhbHNvDQrCoMKgwqDCoMKgwqDCoMKg
IHRoYXQgYSBkZWNvZGVyIGNvbmZvcm1pbmcgdG8gYSBjZXJ0YWluIHByb2ZpbGUgbWF5IGJlIGFi
bGUgdG8NCsKgwqDCoMKgwqDCoMKgwqAgZGVjb2RlIGJpdHN0cmVhbXMgY29uZm9ybWluZyB0byBv
dGhlciBwcm9maWxlcy7CoCBGb3IgZXhhbXBsZSwgYQ0KwqDCoMKgwqDCoCDCoMKgwqBkZWNvZGVy
IGNvbmZvcm1pbmcgdG8gdGhlIEhpZ2ggNDo0OjQgcHJvZmlsZSwgYXQgYSBjZXJ0YWluDQrCoMKg
wqDCoMKgwqDCoMKgIGxldmVsLCBtdXN0IGJlIGFibGUgdG8gZGVjb2RlIGJpdHN0cmVhbXMgY29u
Zm9ybWluZyB0byB0aGUNCsKgwqDCoMKgwqDCoMKgwqAgQ29uc3RyYWluZWQgQmFzZWxpbmUsIE1h
aW4sIEhpZ2gsIEhpZ2ggMTAsIG9yIEhpZ2ggNDoyOjINCsKgwqDCoMKgwqDCoMKgwqAgcHJvZmls
ZSBhdCB0aGUgc2FtZSBvciBhIGxvd2VyIGxldmVsLg0KwqBORVc6DQrCoMKgwqDCoMKgwqAgwqDC
oEZvciBleGFtcGxlLCBpbiB0aGUgdGFibGUgYWJvdmUsIHByb2ZpbGVfaWRjIGVxdWFsIHRvIDU4
DQrCoMKgwqDCoMKgwqDCoMKgIChFeHRlbmRlZCkgd2l0aCBwcm9maWxlLWlvcCBlcXVhbCB0byAx
MXh4MDAwMCBpbmRpY2F0ZXMgdGhlDQrCoMKgwqDCoMKgwqDCoMKgIHNhbWUgc3ViLXByb2ZpbGUg
Y29ycmVzcG9uZGluZyB0byBwcm9maWxlX2lkYyBlcXVhbCB0byA0Mg0KwqDCoMKgwqDCoMKgwqDC
oCAoQmFzZWxpbmUpIHdpdGggcHJvZmlsZS1pb3AgZXF1YWwgdG8geDF4eDAwMDAuwqAgTm90ZSB0
aGF0IG90aGVyDQrCoMKgwqDCoMKgwqDCoMKgIGNvbWJpbmF0aW9ucyBvZiBwcm9maWxlX2lkYyBh
bmQgcHJvZmlsZS1pb3AgKG5vdCBsaXN0ZWQgaW4NCsKgwqDCoMKgwqDCoMKgwqAgVGFibGUgNSkg
bWF5IHJlcHJlc2VudCBhIHN1Yi1wcm9maWxlIGVxdWl2YWxlbnQgdG8gdGhlIGNvbW1vbg0KwqDC
oMKgwqDCoMKgwqDCoCBzdWJzZXQgb2YgY29kaW5nIHRvb2xzIGZvciBtb3JlIHRoYW4gb25lIHBy
b2ZpbGUuwqAgTm90ZSBhbHNvDQrCoMKgwqDCoMKgwqDCoMKgIHRoYXQgYSBkZWNvZGVyIGNvbmZv
cm1pbmcgdG8gYSBjZXJ0YWluIHByb2ZpbGUgbWF5IGJlIGFibGUgdG8NCsKgwqDCoMKgwqDCoMKg
wqAgZGVjb2RlIGJpdHN0cmVhbXMgY29uZm9ybWluZyB0byBvdGhlciBwcm9maWxlcy4NCg0KT0xE
Og0KwqDCoMKgwqDCoMKgwqDCoCBJZiB0aGUgcHJvZmlsZS1sZXZlbC1pZCBwYXJhbWV0ZXIgaXMg
dXNlZCBmb3IgY2FwYWJpbGl0eQ0KwqDCoMKgwqDCoMKgwqDCoCBleGNoYW5nZSBvciBzZXNzaW9u
IHNldHVwIHByb2NlZHVyZSwgaXQgaW5kaWNhdGVzIHRoZSBzdWJzZXQgb2YNCsKgwqDCoMKgwqDC
oMKgwqAgY29kaW5nIHRvb2xzLCB3aGljaCBpcyBlcXVhbCB0byB0aGUgZGVmYXVsdCBzdWItcHJv
ZmlsZSwgdGhhdA0KwqDCoMKgwqDCoMKgwqDCoCB0aGUgY29kZWMgc3VwcG9ydHMgZm9yIGJvdGgg
cmVjZWl2aW5nIGFuZCBzZW5kaW5nLg0KwqBORVc6DQrCoMKgwqDCoMKgwqDCoMKgIElmIHRoZSBw
cm9maWxlLWxldmVsLWlkIHBhcmFtZXRlciBpcyB1c2VkIGZvciBjYXBhYmlsaXR5DQrCoMKgwqDC
oMKgwqDCoMKgIGV4Y2hhbmdlIG9yIHNlc3Npb24gc2V0dXAsIGl0IGluZGljYXRlcyB0aGUgc3Vi
c2V0IG9mDQrCoMKgwqAgwqDCoMKgwqDCoGNvZGluZyB0b29scywgd2hpY2ggaXMgZXF1YWwgdG8g
dGhlIGRlZmF1bHQgc3ViLXByb2ZpbGUsIHRoYXQNCsKgwqDCoMKgwqDCoMKgwqAgdGhlIGNvZGVj
IHN1cHBvcnRzIGZvciBib3RoIHJlY2VpdmluZyBhbmQgc2VuZGluZy4NCg0KT0xEOg0KwqDCoMKg
wqDCoCBtYXgtY3BiOiBUaGUgdmFsdWUgb2YgbWF4LWNwYiBpcyBhbiBpbnRlZ2VyIGluZGljYXRp
bmcgdGhlIG1heGltdW0NCsKgwqDCoMKgwqDCoMKgwqAgY29kZWQgcGljdHVyZSBidWZmZXIgc2l6
ZSBpbiB1bml0cyBvZiAxMDAwIGJpdHMgZm9yIHRoZSBWQ0wgSFJEDQrCoMKgwqDCoMKgwqDCoMKg
IHBhcmFtZXRlcnMgKHNlZSBBLjMuMSwgaXRlbSBpIG9mIFsxXSkgYW5kIGluIHVuaXRzIG9mIDEy
MDAgYml0cw0KwqDCoMKgwqDCoMKgwqDCoCBmb3IgdGhlIE5BTCBIUkQgcGFyYW1ldGVycyAoc2Vl
IEEuMy4xLCBpdGVtIGogb2YgWzFdKS4NCk5FVzoNCsKgwqDCoMKgwqAgbWF4LWNwYjogVGhlIHZh
bHVlIG9mIG1heC1jcGIgaXMgYW4gaW50ZWdlciBpbmRpY2F0aW5nIHRoZSBtYXhpbXVtDQrCoMKg
wqDCoMKgwqDCoMKgIGNvZGVkIHBpY3R1cmUgYnVmZmVyIHNpemUuIEZvciBDb25zdHJhaW5lZCBC
YXNlbGluZSwgQmFzZWxpbmUsIE1haW4gDQogICAgICAgICBhbmQgRXh0ZW5kZWQgcHJvZmlsZXMs
IHRoZSB1bml0IGlzIDEwMDAgYml0cyBmb3IgdGhlIFZDTCBIUkQNCsKgwqDCoMKgwqDCoMKgwqAg
cGFyYW1ldGVycyBhbmQgMTIwMCBiaXRzIGZvciB0aGUgTkFMIEhSRCBwYXJhbWV0ZXJzLiBGb3Ig
SGlnaCwgSGlnaCAxMCwNCiAgICAgICAgIEhpZ2ggNDoyOjIsIEhpZ2ggNDo0OjQgUHJlZGljdGl2
ZSwgSGlnaCAxMCBJbnRyYSwgSGlnaCA0OjI6MiBJbnRyYSwgDQogICAgICAgICBIaWdoIDQ6NDo0
IEludHJhIGFuZCBDQVZMQyA0OjQ6NCBJbnRyYSBwcm9maWxlcywgdGhlIHVuaXQgaXMgY3BiQnJW
Y2xGYWN0b3INCiAgICAgICAgIGJpdHMgZm9yIHRoZSBWQ0wgSFJEIGFuZCBjcGJCck5hbEZhY3Rv
ciBiaXRzIGZvciB0aGUgTkFMIEhSRCBwYXJhbWV0ZXJzLg0KDQpPTEQ6DQrCoMKgwqDCoMKgIG1h
eC1kcGI6IFRoZSB2YWx1ZSBvZiBtYXgtZHBiIGlzIGFuIGludGVnZXIgaW5kaWNhdGluZyB0aGUg
bWF4aW11bQ0KwqDCoMKgwqDCoMKgwqDCoCBkZWNvZGVkIHBpY3R1cmUgYnVmZmVyIHNpemUgaW4g
dW5pdHMgb2YgMTAyNCBieXRlcy7CoCBUaGUgbWF4LQ0KwqDCoMKgwqDCoMKgwqDCoCBkcGIgcGFy
YW1ldGVyIHNpZ25hbHMgdGhhdCB0aGUgcmVjZWl2ZXIgaGFzIG1vcmUgbWVtb3J5IHRoYW4NCsKg
wqDCoMKgwqDCoMKgwqAgdGhlIG1pbmltdW0gYW1vdW50IG9mIGRlY29kZWQgcGljdHVyZSBidWZm
ZXIgbWVtb3J5IHJlcXVpcmVkIGJ5DQrCoMKgwqDCoMKgwqDCoMKgIHRoZSBzaWduYWxlZCBoaWdo
ZXN0IGxldmVsIGNvbnZleWVkIGluIHRoZSB2YWx1ZSBvZiB0aGUNCsKgwqDCoMKgwqDCoMKgwqAg
cHJvZmlsZS1sZXZlbC1pZCBwYXJhbWV0ZXIgb3IgdGhlIG1heC1yZWN2LWxldmVsIHBhcmFtZXRl
ci4NCsKgwqDCoMKgwqDCoMKgwqAgV2hlbiBtYXgtZHBiIGlzIHNpZ25hbGVkLCB0aGUgcmVjZWl2
ZXIgTVVTVCBiZSBhYmxlIHRvIGRlY29kZQ0KwqDCoMKgwqDCoMKgwqDCoCBOQUwgdW5pdCBzdHJl
YW1zIHRoYXQgY29uZm9ybSB0byB0aGUgc2lnbmFsZWQgaGlnaGVzdCBsZXZlbCwNCsKgwqDCoMKg
wqDCoMKgwqAgd2l0aCB0aGUgZXhjZXB0aW9uIHRoYXQgdGhlIE1heERQQiB2YWx1ZSBpbiBUYWJs
ZSBBLTEgb2YgWzFdDQrCoMKgwqDCoMKgwqDCoMKgIGZvciB0aGUgc2lnbmFsZWQgaGlnaGVzdCBs
ZXZlbCBpcyByZXBsYWNlZCB3aXRoIHRoZSB2YWx1ZSBvZg0KwqDCoMKgwqDCoMKgwqDCoCBtYXgt
ZHBiLsKgIENvbnNlcXVlbnRseSwgYSByZWNlaXZlciB0aGF0IHNpZ25hbHMgbWF4LWRwYiBNVVNU
IGJlDQrCoMKgwqDCoMKgwqDCoMKgIGNhcGFibGUgb2Ygc3RvcmluZyB0aGUgZm9sbG93aW5nIG51
bWJlciBvZiBkZWNvZGVkIGZyYW1lcywNCsKgwqDCoMKgwqDCoMKgIMKgY29tcGxlbWVudGFyeSBm
aWVsZCBwYWlycywgYW5kIG5vbi1wYWlyZWQgZmllbGRzIGluIGl0cyBkZWNvZGVkDQrCoMKgwqDC
oMKgwqDCoMKgIHBpY3R1cmUgYnVmZmVyOg0KDQrCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIE1pbigx
MDI0ICogbWF4LWRwYiAvICggUGljV2lkdGhJbk1icyAqIEZyYW1lSGVpZ2h0SW5NYnMgKg0KwqDC
oMKgwqDCoMKgwqDCoMKgwqDCoCAyNTYgKiBDaHJvbWFGb3JtYXRGYWN0b3IgKSwgMTYpDQoNCsKg
wqDCoMKgwqDCoMKgwqAgUGljV2lkdGhJbk1icywgRnJhbWVIZWlnaHRJbk1icywgYW5kIENocm9t
YUZvcm1hdEZhY3RvciBhcmUNCsKgwqDCoMKgwqDCoMKgwqAgZGVmaW5lZCBpbiBbMV0uDQoNCsKg
wqDCoMKgwqDCoMKgwqAgVGhlIHZhbHVlIG9mIG1heC1kcGIgTVVTVCBiZSBncmVhdGVyIHRoYW4g
b3IgZXF1YWwgdG8gdGhlIHZhbHVlDQrCoMKgwqDCoMKgwqDCoMKgIG9mIE1heERQQiBnaXZlbiBp
biBUYWJsZSBBLTEgb2YgWzFdIGZvciB0aGUgaGlnaGVzdCBsZXZlbC4NCsKgwqDCoMKgwqDCoMKg
wqAgU2VuZGVycyBNQVkgdXNlIHRoaXMga25vd2xlZGdlIHRvIGNvbnN0cnVjdCBjb2RlZCB2aWRl
byBzdHJlYW1zDQrCoMKgwqDCoMKgwqDCoMKgIHdpdGggaW1wcm92ZWQgY29tcHJlc3Npb24uDQpO
RVc6DQrCoMKgwqDCoMKgIG1heC1kcGI6IFRoZSB2YWx1ZSBvZiBtYXgtZHBiIGlzIGFuIGludGVn
ZXIgaW5kaWNhdGluZyB0aGUgbWF4aW11bQ0KwqDCoMKgwqDCoMKgwqDCoCBkZWNvZGVkIHBpY3R1
cmUgYnVmZmVyIHNpemUgaW4gdW5pdHMgb2YgOC8zIG1hY3JvYmxvY2tzLsKgIFRoZSBtYXgtDQrC
oMKgwqDCoMKgwqDCoMKgIGRwYiBwYXJhbWV0ZXIgc2lnbmFscyB0aGF0IHRoZSByZWNlaXZlciBo
YXMgbW9yZSBtZW1vcnkgdGhhbg0KwqDCoMKgwqDCoMKgwqDCoCB0aGUgbWluaW11bSBhbW91bnQg
b2YgZGVjb2RlZCBwaWN0dXJlIGJ1ZmZlciBtZW1vcnkgcmVxdWlyZWQgYnkNCsKgwqDCoMKgwqDC
oMKgwqAgdGhlIHNpZ25hbGVkIGhpZ2hlc3QgbGV2ZWwgY29udmV5ZWQgaW4gdGhlIHZhbHVlIG9m
IHRoZQ0KwqDCoMKgwqDCoMKgwqDCoCBwcm9maWxlLWxldmVsLWlkIHBhcmFtZXRlciBvciB0aGUg
bWF4LXJlY3YtbGV2ZWwgcGFyYW1ldGVyLg0KwqDCoMKgwqDCoMKgwqDCoCBXaGVuIG1heC1kcGIg
aXMgc2lnbmFsZWQsIHRoZSByZWNlaXZlciBNVVNUIGJlIGFibGUgdG8gZGVjb2RlDQrCoMKgwqDC
oMKgwqDCoMKgIE5BTCB1bml0IHN0cmVhbXMgdGhhdCBjb25mb3JtIHRvIHRoZSBzaWduYWxlZCBo
aWdoZXN0IGxldmVsLA0KwqDCoMKgwqDCoMKgwqDCoCB3aXRoIHRoZSBleGNlcHRpb24gdGhhdCB0
aGUgTWF4RHBiTWJzIHZhbHVlIGluIFRhYmxlIEEtMSBvZiBbMV0NCsKgwqDCoMKgwqDCoMKgwqAg
Zm9yIHRoZSBzaWduYWxlZCBoaWdoZXN0IGxldmVsIGlzIHJlcGxhY2VkIHdpdGggdGhlIHZhbHVl
IG9mDQrCoMKgwqDCoMKgwqDCoMKgIG1heC1kcGIgKiAzIC8gOC7CoCBDb25zZXF1ZW50bHksIGEg
cmVjZWl2ZXIgdGhhdCBzaWduYWxzIG1heC1kcGIgTVVTVCBiZQ0KwqDCoMKgwqDCoMKgwqDCoCBj
YXBhYmxlIG9mIHN0b3JpbmcgdGhlIGZvbGxvd2luZyBudW1iZXIgb2YgZGVjb2RlZCBmcmFtZXMs
DQrCoMKgwqDCoMKgwqDCoMKgIGNvbXBsZW1lbnRhcnkgZmllbGQgcGFpcnMsIGFuZCBub24tcGFp
cmVkIGZpZWxkcyBpbiBpdHMgZGVjb2RlZA0KwqDCoMKgwqDCoMKgwqDCoCBwaWN0dXJlIGJ1ZmZl
cjoNCg0KwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCBNaW4obWF4LWRwYiAqIDMgLyA4IC8gKCBQaWNX
aWR0aEluTWJzICogRnJhbWVIZWlnaHRJbk1icyksIDE2KQ0KDQrCoMKgwqDCoMKgwqDCoMKgIFdo
ZXJlaW4gUGljV2lkdGhJbk1icyBhbmQgRnJhbWVIZWlnaHRJbk1icyBhcmUgZGVmaW5lZCBpbiBb
MV0uDQoNCsKgwqDCoMKgwqDCoMKgwqAgVGhlIHZhbHVlIG9mIG1heC1kcGIgTVVTVCBiZSBncmVh
dGVyIHRoYW4gb3IgZXF1YWwgdG8gdGhlIHZhbHVlDQrCoMKgwqDCoMKgwqDCoMKgIG9mIE1heERw
Yk1icyAqIDMgLyA4LCB3aGVyZWluIHRoZSB2YWx1ZSBvZiBNYXhEcGJNYnMgaXMgZ2l2ZW4gaW4g
DQogICAgICAgICBUYWJsZSBBLTEgb2YgWzFdIGZvciB0aGUgaGlnaGVzdCBsZXZlbC4NCsKgwqDC
oMKgwqDCoMKgwqAgU2VuZGVycyBNQVkgdXNlIHRoaXMga25vd2xlZGdlIHRvIGNvbnN0cnVjdCBj
b2RlZCB2aWRlbyBzdHJlYW1zDQrCoMKgwqDCoMKgwqDCoMKgIHdpdGggaW1wcm92ZWQgY29tcHJl
c3Npb24uDQoNCk9MRDoNCsKgwqDCoMKgwqAgbWF4LWJyOiBUaGUgdmFsdWUgb2YgbWF4LWJyIGlz
IGFuIGludGVnZXIgaW5kaWNhdGluZyB0aGUgbWF4aW11bQ0KwqDCoMKgwqDCoMKgwqDCoCB2aWRl
byBiaXRyYXRlIGluIHVuaXRzIG9mIDEwMDAgYml0cyBwZXIgc2Vjb25kIGZvciB0aGUgVkNMIEhS
RA0KwqDCoMKgwqDCoMKgwqDCoCBwYXJhbWV0ZXJzIChzZWUgQS4zLjEsIGl0ZW0gaSBvZiBbMV0p
IGFuZCBpbiB1bml0cyBvZiAxMjAwIGJpdHMNCsKgwqDCoMKgwqDCoMKgwqAgcGVyIHNlY29uZCBm
b3IgdGhlIE5BTCBIUkQgcGFyYW1ldGVycyAoc2VlIEEuMy4xLCBpdGVtIGogb2YNCsKgwqDCoMKg
wqDCoMKgwqAgWzFdKS4NCsKgwqDCoMKgwqDCoMKgwqAg4oCmDQrCoMKgwqDCoMKgwqDCoMKgIEZv
ciBleGFtcGxlLCBpZiBhIHJlY2VpdmVyIHNpZ25hbHMgY2FwYWJpbGl0eSBmb3IgTGV2ZWwgMS4y
DQrCoMKgwqDCoMKgwqDCoMKgIHdpdGggbWF4LWJyIGVxdWFsIHRvIDE1NTAsIHRoaXMgaW5kaWNh
dGVzIGEgbWF4aW11bSB2aWRlbw0KwqDCoMKgwqDCoMKgwqDCoCBiaXRyYXRlIG9mIDE1NTAga2Jp
dHMvc2VjIGZvciBWQ0wgSFJEIHBhcmFtZXRlcnMsIGEgbWF4aW11bQ0KwqDCoMKgwqDCoMKgwqDC
oCB2aWRlbyBiaXRyYXRlIG9mIDE4NjAga2JpdHMvc2VjIGZvciBOQUwgSFJEIHBhcmFtZXRlcnMs
IGFuZCBhDQrCoMKgwqDCoMKgwqDCoMKgIENQQiBzaXplIG9mIDQwMzY0NTggYml0cyAoMTU1MDAw
MCAvIDM4NDAwMCAqIDEwMDAgKiAxMDAwKS4NCk5FVzogDQrCoMKgwqDCoMKgIG1heC1icjogVGhl
IHZhbHVlIG9mIG1heC1iciBpcyBhbiBpbnRlZ2VyIGluZGljYXRpbmcgdGhlIG1heGltdW0NCsKg
wqDCoMKgwqDCoMKgwqAgdmlkZW8gYml0cmF0ZS7CoCBGb3IgQ29uc3RyYWluZWQgQmFzZWxpbmUs
IEJhc2VsaW5lLCBNYWluIA0KICAgICAgICAgYW5kIEV4dGVuZGVkIHByb2ZpbGVzLCB0aGUgdW5p
dCBpcyAxMDAwIGJpdHMgcGVyIHNlY29uZCBmb3IgdGhlIFZDTCBIUkQNCsKgwqDCoMKgwqDCoMKg
wqAgcGFyYW1ldGVycyBhbmQgMTIwMCBiaXRzIHBlciBzZWNvbmQgZm9yIHRoZSBOQUwgSFJEIHBh
cmFtZXRlcnMuIEZvciBIaWdoLCBIaWdoIDEwLA0KICAgICAgICAgSGlnaCA0OjI6MiwgSGlnaCA0
OjQ6NCBQcmVkaWN0aXZlLCBIaWdoIDEwIEludHJhLCBIaWdoIDQ6MjoyIEludHJhLCANCiAgICAg
ICAgIEhpZ2ggNDo0OjQgSW50cmEgYW5kIENBVkxDIDQ6NDo0IEludHJhIHByb2ZpbGVzLCB0aGUg
dW5pdCBpcyBjcGJCclZjbEZhY3Rvcg0KICAgICAgICAgYml0cyBwZXIgc2Vjb25kIGZvciB0aGUg
VkNMIEhSRCBhbmQgY3BiQnJOYWxGYWN0b3IgYml0cyBwZXIgc2Vjb25kIGZvciB0aGUgTkFMIEhS
RCBwYXJhbWV0ZXJzLg0KwqDCoMKgwqDCoMKgwqDCoCDigKYNCsKgwqDCoMKgwqDCoMKgwqAgRm9y
IGV4YW1wbGUsIGlmIGEgcmVjZWl2ZXIgc2lnbmFscyBjYXBhYmlsaXR5IGZvciBNYWluIHByb2Zp
bGUgTGV2ZWwgMS4yDQrCoMKgwqDCoMKgwqDCoMKgIHdpdGggbWF4LWJyIGVxdWFsIHRvIDE1NTAs
IHRoaXMgaW5kaWNhdGVzIGEgbWF4aW11bSB2aWRlbw0KwqDCoMKgwqDCoMKgwqDCoCBiaXRyYXRl
IG9mIDE1NTAga2JpdHMvc2VjIGZvciBWQ0wgSFJEIHBhcmFtZXRlcnMsIGEgbWF4aW11bQ0KwqDC
oMKgwqDCoMKgwqDCoCB2aWRlbyBiaXRyYXRlIG9mIDE4NjAga2JpdHMvc2VjIGZvciBOQUwgSFJE
IHBhcmFtZXRlcnMsIGFuZCBhDQrCoMKgwqDCoMKgwqDCoMKgIENQQiBzaXplIG9mIDQwMzY0NTgg
Yml0cyAoMTU1MDAwMCAvIDM4NDAwMCAqIDEwMDAgKiAxMDAwKS4NCg0KLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tRW5kIG9mIHN1Z2dlc3RlZCBjaGFuZ2VzIC0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCg==

From gwz@net-zen.net  Sun Mar 20 02:15:19 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 720E73A69D5 for <avt@core3.amsl.com>; Sun, 20 Mar 2011 02:15:19 -0700 (PDT)
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=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Wtl08QFvvHM for <avt@core3.amsl.com>; Sun, 20 Mar 2011 02:15:18 -0700 (PDT)
Received: from smtpauth20.prod.mesa1.secureserver.net (smtpauth20.prod.mesa1.secureserver.net [64.202.165.36]) by core3.amsl.com (Postfix) with SMTP id 91C013A6A38 for <avt@ietf.org>; Sun, 20 Mar 2011 02:15:18 -0700 (PDT)
Received: (qmail 8186 invoked from network); 20 Mar 2011 09:16:49 -0000
Received: from unknown (124.120.73.139) by smtpauth20.prod.mesa1.secureserver.net (64.202.165.36) with ESMTP; 20 Mar 2011 09:16:48 -0000
Message-ID: <4D85C5FA.4010407@net-zen.net>
Date: Sun, 20 Mar 2011 16:16:42 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9 ThunderBrowse/3.3.5
MIME-Version: 1.0
To: Ye-Kui Wang <yekui.wang@huawei.com>
References: <B99DECD58A94E143BA6F1508CC688351B417FB@dfweml504-mbx.china.huawei.com>
In-Reply-To: <B99DECD58A94E143BA6F1508CC688351B417FB@dfweml504-mbx.china.huawei.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "avt@ietf.org" <avt@ietf.org>, "payload@ietf.org" <payload@ietf.org>
Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Mar 2011 09:15:19 -0000

On 3/20/2011 3:20 PM, Ye-Kui Wang wrote:
> Folks,
> 
>  
> 
> The three H.264/AVC related payload formats, namely,
> draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-rtp-svc-27, and
> draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48 stage.
> 
>  
> 
> The RFC-Editor has found the following problem: In
> draft-ietf-avt-rtp-rfc3984bis-12, the definition of the max-dpb media
> parameter refers to the MaxDPB that was defined the first version of the
> H.264/AVC spec, but not any more in the latest version (the 2010
> version). The parameter in the latest H.264/AVC version corresponding to
> MaxDPB is MaxDpbMbs, and the unit of the new parameter (i.e.,
> macroblocks) is different from the original one (i.e. 1024 bytes).

...

> Since the drafts are at the AUTH48 stage, please provide comments by
> Monday, March 21, if any. Many thanks!

Just my opinion but these seem like technical changes that can't really
be dealt with in AUTH48.

...

From abegen@cisco.com  Sun Mar 20 03:45:19 2011
Return-Path: <abegen@cisco.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF9363A6BA6 for <avt@core3.amsl.com>; Sun, 20 Mar 2011 03:45:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.553
X-Spam-Level: 
X-Spam-Status: No, score=-10.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 79n--Fa01VSe for <avt@core3.amsl.com>; Sun, 20 Mar 2011 03:45:18 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id BF8233A6BA5 for <avt@ietf.org>; Sun, 20 Mar 2011 03:45:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=abegen@cisco.com; l=964; q=dns/txt; s=iport; t=1300618010; x=1301827610; h=mime-version:content-transfer-encoding:subject:date: message-id:from:to; bh=npPtl/KWTGd7K29MK0yogT6CgAGTT0yp1R8UGnLx2Rs=; b=lzLjj5NQgKVjwBO9pkMCk9/0TxsZV7UA47539lVbH4ehpwymFOFte8eW fNSAdJtvhfEwWdU/CVPbMRs6NrufOdIWpWdriEMXHaZPzMUwqGjNBhJmR Akl/Sn8th7E+cktsiMYLUXEAq9xde9Xp5flKN/YrNLXaU+owOae47fafK A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai8BAAJ4hU2tJV2Y/2dsb2JhbACYPT+Me3ekd5sQhWMEhTOLCw
X-IronPort-AV: E=Sophos;i="4.63,214,1299456000"; d="scan'208";a="416223704"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by sj-iport-1.cisco.com with ESMTP; 20 Mar 2011 10:46:50 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by rcdn-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p2KAkosf011835 for <avt@ietf.org>; Sun, 20 Mar 2011 10:46:50 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 20 Mar 2011 03:46:49 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 20 Mar 2011 03:46:48 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540E955E09@xmb-sjc-215.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Two new drafts on redundant media streams
Thread-Index: AcvdCFV4SdefuVX9QCum97sIXr7IBAJ4321g
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 20 Mar 2011 10:46:49.0560 (UTC) FILETIME=[1DBA2580:01CBE6EC]
Subject: [AVTCORE] FW: [MMUSIC] Two new drafts on redundant media streams
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Mar 2011 10:45:19 -0000

FYI. These two drafts will be presented in MMUSIC. There are AVT-related =
issues so we would welcome feedback from this list as well.

-acbegen

-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf =
Of Ali C. Begen (abegen)
Sent: Monday, March 07, 2011 9:45 PM
To: mmusic@ietf.org
Cc: Heidi Ou (hou); Yiqun Cai (ycai)
Subject: [MMUSIC] Two new drafts on redundant media streams

We have submitted two new drafts for describing redundant media streams =
in SDP.

https://datatracker.ietf.org/doc/draft-begen-mmusic-temporal-interleaving=
/=20
https://datatracker.ietf.org/doc/draft-begen-mmusic-redundancy-grouping/ =


Comments and feedback are welcome. We will request a presentation slot =
for these two drafts in the upcoming meeting.

Thanks.
-acbegen
_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic

From Even.roni@huawei.com  Sun Mar 20 05:24:49 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 826CF3A6BB8; Sun, 20 Mar 2011 05:24:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.495
X-Spam-Level: 
X-Spam-Status: No, score=-100.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8M2p+gy1NtdM; Sun, 20 Mar 2011 05:24:48 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 9371E3A6BB7; Sun, 20 Mar 2011 05:24:48 -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 <0LIC00KM3VVLMQ@szxga05-in.huawei.com>; Sun, 20 Mar 2011 20:26: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 <0LIC00439VVKE5@szxga05-in.huawei.com>; Sun, 20 Mar 2011 20:26:09 +0800 (CST)
Received: from windows8d787f9 (cust.static.109-164-246-172.swisscomdata.ch [109.164.246.172]) by szxml12-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LIC00AD4VUJT7@szxml12-in.huawei.com>; Sun, 20 Mar 2011 20:26:08 +0800 (CST)
Date: Sun, 20 Mar 2011 14:25:10 +0200
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <4D85C5FA.4010407@net-zen.net>
To: 'Glen Zorn' <gwz@net-zen.net>, 'Ye-Kui Wang' <yekui.wang@huawei.com>, 'Robert Sparks' <rjsparks@nostrum.com>
Message-id: <000701cbe6f9$f44b1e80$dce15b80$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: Acvm35YRpzpCX3JQSOWXj1OvEp108gADr0Sg
References: <B99DECD58A94E143BA6F1508CC688351B417FB@dfweml504-mbx.china.huawei.com> <4D85C5FA.4010407@net-zen.net>
Cc: avt@ietf.org, payload@ietf.org
Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Mar 2011 12:24:49 -0000

Hi Glen,
The technical change is more in H.264/AVC specification. In the payload
specifications (3984bis/ RCDO and SVC) the change is to specify the
conversion between the old and new parameter and to explain the change in
H.264.
It can be looked as a technical and I will leave it to the AD to help here.

As for the quality of the change it was done by YK with the help of Steve
Botzko (H.241 editor) and Gary Sullivan the Rapportuer of Q6 SG16 that does
the video codec in a f2f meeting. It was also reviewed by me and by some
other experts on video coding and I feel good about the solution,

This change involves also an update to H.241 that has the same issue and the
objective is to approve the H.241 change this week at the ongoing ITU Study
Group 16 meeting. The solution for the IETF draft and ITU draft should be
the same to address interoperability.

Thanks
Roni Even
As individual.


> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Glen Zorn
> Sent: Sunday, March 20, 2011 11:17 AM
> To: Ye-Kui Wang
> Cc: avt@ietf.org; payload@ietf.org
> Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO
> payload drafts
> 
> On 3/20/2011 3:20 PM, Ye-Kui Wang wrote:
> > Folks,
> >
> >
> >
> > The three H.264/AVC related payload formats, namely,
> > draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-rtp-svc-27, and
> > draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48 stage.
> >
> >
> >
> > The RFC-Editor has found the following problem: In
> > draft-ietf-avt-rtp-rfc3984bis-12, the definition of the max-dpb media
> > parameter refers to the MaxDPB that was defined the first version of
> the
> > H.264/AVC spec, but not any more in the latest version (the 2010
> > version). The parameter in the latest H.264/AVC version corresponding
> to
> > MaxDPB is MaxDpbMbs, and the unit of the new parameter (i.e.,
> > macroblocks) is different from the original one (i.e. 1024 bytes).
> 
> ...
> 
> > Since the drafts are at the AUTH48 stage, please provide comments by
> > Monday, March 21, if any. Many thanks!
> 
> Just my opinion but these seem like technical changes that can't really
> be dealt with in AUTH48.
> 
> ...
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From stewe@stewe.org  Sun Mar 20 07:19:28 2011
Return-Path: <stewe@stewe.org>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F04A73A6BC5; Sun, 20 Mar 2011 07:19:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2XmZ-fG+1sZU; Sun, 20 Mar 2011 07:19:27 -0700 (PDT)
Received: from stewe.org (stewe.org [85.214.122.234]) by core3.amsl.com (Postfix) with ESMTP id AB8863A6A03; Sun, 20 Mar 2011 07:19:26 -0700 (PDT)
Received: from [156.106.237.64] (unverified [156.106.237.64])  by stewe.org (SurgeMail 3.9e) with ESMTP id 14264-1743317  for multiple; Sun, 20 Mar 2011 15:20:52 +0100
References: <B99DECD58A94E143BA6F1508CC688351B417FB@dfweml504-mbx.china.huawei.com> <4D85C5FA.4010407@net-zen.net> <000701cbe6f9$f44b1e80$dce15b80$%roni@huawei.com>
In-Reply-To: <000701cbe6f9$f44b1e80$dce15b80$%roni@huawei.com>
Mime-Version: 1.0 (iPhone Mail 8C148)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <594FCF5C-180C-423E-A96B-E0BEB399A529@stewe.org>
X-Mailer: iPhone Mail (8C148)
From: Stephan Wenger <stewe@stewe.org>
Date: Sun, 20 Mar 2011 15:20:41 +0100
To: Roni Even <Even.roni@huawei.com>
X-Originating-IP: 156.106.237.64
X-Authenticated-User: stewe@stewe.org 
Cc: "payload@ietf.org" <payload@ietf.org>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] [payload]  Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Mar 2011 14:19:28 -0000

+1
Stephan (also in Geneve)


Sent from my iPhone

On Mar 20, 2011, at 13:25, Roni Even <Even.roni@huawei.com> wrote:

> Hi Glen,
> The technical change is more in H.264/AVC specification. In the payload
> specifications (3984bis/ RCDO and SVC) the change is to specify the
> conversion between the old and new parameter and to explain the change in
> H.264.
> It can be looked as a technical and I will leave it to the AD to help here=
.
>=20
> As for the quality of the change it was done by YK with the help of Steve
> Botzko (H.241 editor) and Gary Sullivan the Rapportuer of Q6 SG16 that doe=
s
> the video codec in a f2f meeting. It was also reviewed by me and by some
> other experts on video coding and I feel good about the solution,
>=20
> This change involves also an update to H.241 that has the same issue and t=
he
> objective is to approve the H.241 change this week at the ongoing ITU Stud=
y
> Group 16 meeting. The solution for the IETF draft and ITU draft should be
> the same to address interoperability.
>=20
> Thanks
> Roni Even
> As individual.
>=20
>=20
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
>> Glen Zorn
>> Sent: Sunday, March 20, 2011 11:17 AM
>> To: Ye-Kui Wang
>> Cc: avt@ietf.org; payload@ietf.org
>> Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO
>> payload drafts
>>=20
>> On 3/20/2011 3:20 PM, Ye-Kui Wang wrote:
>>> Folks,
>>>=20
>>>=20
>>>=20
>>> The three H.264/AVC related payload formats, namely,
>>> draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-rtp-svc-27, and
>>> draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48 stage.
>>>=20
>>>=20
>>>=20
>>> The RFC-Editor has found the following problem: In
>>> draft-ietf-avt-rtp-rfc3984bis-12, the definition of the max-dpb media
>>> parameter refers to the MaxDPB that was defined the first version of
>> the
>>> H.264/AVC spec, but not any more in the latest version (the 2010
>>> version). The parameter in the latest H.264/AVC version corresponding
>> to
>>> MaxDPB is MaxDpbMbs, and the unit of the new parameter (i.e.,
>>> macroblocks) is different from the original one (i.e. 1024 bytes).
>>=20
>> ...
>>=20
>>> Since the drafts are at the AUTH48 stage, please provide comments by
>>> Monday, March 21, if any. Many thanks!
>>=20
>> Just my opinion but these seem like technical changes that can't really
>> be dealt with in AUTH48.
>>=20
>> ...
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>=20
> _______________________________________________
> payload mailing list
> payload@ietf.org
> https://www.ietf.org/mailman/listinfo/payload

From gwz@net-zen.net  Sun Mar 20 23:10:01 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 392103A67B6 for <avt@core3.amsl.com>; Sun, 20 Mar 2011 23:10:01 -0700 (PDT)
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=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hk0Z2PG32mex for <avt@core3.amsl.com>; Sun, 20 Mar 2011 23:09:56 -0700 (PDT)
Received: from smtpauth20.prod.mesa1.secureserver.net (smtpauth20.prod.mesa1.secureserver.net [64.202.165.36]) by core3.amsl.com (Postfix) with SMTP id 21A753A67B1 for <avt@ietf.org>; Sun, 20 Mar 2011 23:09:55 -0700 (PDT)
Received: (qmail 12301 invoked from network); 21 Mar 2011 06:11:28 -0000
Received: from unknown (124.122.150.171) by smtpauth20.prod.mesa1.secureserver.net (64.202.165.36) with ESMTP; 21 Mar 2011 06:11:27 -0000
Message-ID: <4D86EC09.2020304@net-zen.net>
Date: Mon, 21 Mar 2011 13:11:21 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9 ThunderBrowse/3.3.5
MIME-Version: 1.0
To: Roni Even <Even.roni@huawei.com>
References: <B99DECD58A94E143BA6F1508CC688351B417FB@dfweml504-mbx.china.huawei.com> <4D85C5FA.4010407@net-zen.net> <000701cbe6f9$f44b1e80$dce15b80$%roni@huawei.com>
In-Reply-To: <000701cbe6f9$f44b1e80$dce15b80$%roni@huawei.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: payload@ietf.org, avt@ietf.org
Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2011 06:10:01 -0000

On 3/20/2011 7:25 PM, Roni Even wrote:

> Hi Glen,
> The technical change is more in H.264/AVC specification. In the payload
> specifications (3984bis/ RCDO and SVC) the change is to specify the
> conversion between the old and new parameter and to explain the change in
> H.264.
> It can be looked as a technical and I will leave it to the AD to help here.
> 
> As for the quality of the change it was done by YK with the help of Steve
> Botzko (H.241 editor) and Gary Sullivan the Rapportuer of Q6 SG16 that does
> the video codec in a f2f meeting. It was also reviewed by me and by some
> other experts on video coding and I feel good about the solution,

I'm admittedly not an expert on H.264, so I can't quibble about the
quality of the proposed solution.  My comment is a procedural one: I
don't believe that technical changes are allowed after the completion of
IETF review, nor should they be.  My understanding is that the AUTH48
review is provided only as a last-minute opportunity to catch typos or
make small editorial changes, not to modify the technical content of a
document.  BTW, I'm in the same boat myself right now: one of my
co-authors has fairly significant technical changes (and has proposed
even bigger ones) to a draft now in AUTH48 & I'm saying the same thing
about that one.  I'm _not_ looking forward to restarting the whole
process, but OTOH my co-author (& for that matter, I) should have had
our act together before requesting publication.

> 
> This change involves also an update to H.241 that has the same issue and the
> objective is to approve the H.241 change this week at the ongoing ITU Study
> Group 16 meeting. The solution for the IETF draft and ITU draft should be
> the same to address interoperability.
> 
> Thanks
> Roni Even
> As individual.
> 
> 
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
>> Glen Zorn
>> Sent: Sunday, March 20, 2011 11:17 AM
>> To: Ye-Kui Wang
>> Cc: avt@ietf.org; payload@ietf.org
>> Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO
>> payload drafts
>>
>> On 3/20/2011 3:20 PM, Ye-Kui Wang wrote:
>>> Folks,
>>>
>>>
>>>
>>> The three H.264/AVC related payload formats, namely,
>>> draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-rtp-svc-27, and
>>> draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48 stage.
>>>
>>>
>>>
>>> The RFC-Editor has found the following problem: In
>>> draft-ietf-avt-rtp-rfc3984bis-12, the definition of the max-dpb media
>>> parameter refers to the MaxDPB that was defined the first version of
>> the
>>> H.264/AVC spec, but not any more in the latest version (the 2010
>>> version). The parameter in the latest H.264/AVC version corresponding
>> to
>>> MaxDPB is MaxDpbMbs, and the unit of the new parameter (i.e.,
>>> macroblocks) is different from the original one (i.e. 1024 bytes).
>>
>> ...
>>
>>> Since the drafts are at the AUTH48 stage, please provide comments by
>>> Monday, March 21, if any. Many thanks!
>>
>> Just my opinion but these seem like technical changes that can't really
>> be dealt with in AUTH48.
>>
>> ...
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
> 
> 
> 

From yekui.wang@huawei.com  Mon Mar 21 01:10:10 2011
Return-Path: <yekui.wang@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C3273A67F0; Mon, 21 Mar 2011 01:10:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PCCx2gwtM0Bw; Mon, 21 Mar 2011 01:09:57 -0700 (PDT)
Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180]) by core3.amsl.com (Postfix) with ESMTP id 3BE3E28C111; Mon, 21 Mar 2011 01:09:57 -0700 (PDT)
Received: from huawei.com (usaga04-in [172.18.4.101]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LIE00B81ER271@usaga04-in.huawei.com>; Mon, 21 Mar 2011 03:11:27 -0500 (CDT)
Received: from dfweml202-edg.china.huawei.com ([172.18.9.108]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPS id <0LIE00FIJER143@usaga04-in.huawei.com>; Mon, 21 Mar 2011 03:11:26 -0500 (CDT)
Received: from DFWEML401-HUB.china.huawei.com (10.193.5.101) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.270.1; Mon, 21 Mar 2011 01:11:25 -0700
Received: from DFWEML504-MBX.china.huawei.com ([169.254.4.84]) by DFWEML401-HUB.china.huawei.com ([fe80::f07f:889f:78ef:8df3%13]) with mapi id 14.01.0270.001; Mon, 21 Mar 2011 01:11:24 -0700
Date: Mon, 21 Mar 2011 08:11:23 +0000
From: Ye-Kui Wang <yekui.wang@huawei.com>
In-reply-to: <B99DECD58A94E143BA6F1508CC688351B417FB@dfweml504-mbx.china.huawei.com>
X-Originating-IP: [10.47.86.236]
To: "payload@ietf.org" <payload@ietf.org>, "avt@ietf.org" <avt@ietf.org>
Message-id: <B99DECD58A94E143BA6F1508CC688351B445DE@dfweml504-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_hcR2NkBpOkdtxtm59hGaDw)"
Content-language: en-US
Accept-Language: en-US
Thread-topic: Some changes to rfc3984bis, SVC, and RCDO payload drafts
Thread-index: Acvm161AAF2A6AC0R/ODLEMZyh1IcgAwzyEA
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <B99DECD58A94E143BA6F1508CC688351B417FB@dfweml504-mbx.china.huawei.com>
Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2011 08:10:10 -0000

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

Further discussions with the same group of persons led to a decision to stay with the unscaled units for max-br and max-cpb, thus fewer changes are needed to the three payload formats listed in the title and H.241. With this, the changes needed are listed below (the originally suggested changes are dropped from this email). This time I have highlighted the changes, and I have also described the nature the changes below. Hope these may help understand better what have been changed, and can lead to a quicker decision by the group, including WG chairs, and our AD.

BR, YK


------------------------------------Start of suggested changes --------------------------------------


Section 8.1:
OLD:

      profile-level-id:

         A base16 [7] (hexadecimal) representation of the following

         three bytes in the sequence parameter set NAL unit is specified

         in [1]: 1) profile_idc, 2) a byte herein referred to as

         profile-iop, composed of the values of constraint_set0_flag,

         constraint_set1_flag,constraint_set2_flag,

         constraint_set3_flag, and reserved_zero_4bits in bit-

         significance order, starting from the most-significant bit, and

         3) level_idc.  Note that reserved_zero_4bits is required to be

         equal to 0 in [1], but other values for it may be specified in

         the future by ITU-T or ISO/IEC.
 NEW: (note that the change here is purely editorial)
      profile-level-id:
         A base16 [7] (hexadecimal) representation of the following
         three bytes in the sequence parameter set NAL unit is specified
         in [1]: 1) profile_idc, 2) a byte herein referred to as
         profile-iop, composed of the values of constraint_set0_flag,
         constraint_set1_flag,constraint_set2_flag,
         constraint_set3_flag, constraint_set4_flag, constraint_set5_flag,
 and reserved_zero_2bits in bit-significance order, starting from the most-significant bit, and
         3) level_idc.  Note that reserved_zero_2bits is required to be
         equal to 0 in [1], but other values for it may be specified in
         the future by ITU-T or ISO/IEC.

OLD:

         For example, in the table above, profile_idc equal to 58

         (Extended) with profile-iop equal to 11xx0000 indicates the

         same sub-profile corresponding to profile_idc equal to 42

         (Baseline) with profile-iop equal to x1xx0000.  Note that other

         combinations of profile_idc and profile-iop (not listed in

         Table 5) may represent a sub-profile equivalent to the common

         subset of coding tools for more than one profile.  Note also

         that a decoder conforming to a certain profile may be able to

         decode bitstreams conforming to other profiles.  For example, a

         decoder conforming to the High 4:4:4 profile, at a certain

         level, must be able to decode bitstreams conforming to the

         Constrained Baseline, Main, High, High 10, or High 4:2:2

         profile at the same or a lower level.
 NEW: (note that the change here is purely editorial)
         For example, in the table above, profile_idc equal to 58
         (Extended) with profile-iop equal to 11xx0000 indicates the
         same sub-profile corresponding to profile_idc equal to 42
         (Baseline) with profile-iop equal to x1xx0000.  Note that other
         combinations of profile_idc and profile-iop (not listed in
         Table 5) may represent a sub-profile equivalent to the common
         subset of coding tools for more than one profile.  Note also
         that a decoder conforming to a certain profile may be able to
         decode bitstreams conforming to other profiles.

OLD:

         If the profile-level-id parameter is used for capability

         exchange or session setup procedure, it indicates the subset of

         coding tools, which is equal to the default sub-profile, that

         the codec supports for both receiving and sending.
 NEW: (note that the change here is purely editorial)
         If the profile-level-id parameter is used for capability
         exchange or session setup, it indicates the subset of
         coding tools, which is equal to the default sub-profile, that
         the codec supports for both receiving and sending.

OLD:
      max-cpb: The value of max-cpb is an integer indicating the maximum
         coded picture buffer size in units of 1000 bits for the VCL HRD
         parameters (see A.3.1, item i of [1]) and in units of 1200 bits
         for the NAL HRD parameters (see A.3.1, item j of [1]).
NEW: (note that the change here is purely editorial)
      max-cpb: The value of max-cpb is an integer indicating the maximum
         coded picture buffer size in units of 1000 bits for the VCL HRD
         parameters and in units of 1200 bits
         for the NAL HRD parameters.

OLD:
      max-dpb: The value of max-dpb is an integer indicating the maximum
         decoded picture buffer size in units of 1024 bytes.  The max-
         dpb parameter signals that the receiver has more memory than
         the minimum amount of decoded picture buffer memory required by
         the signaled highest level conveyed in the value of the
         profile-level-id parameter or the max-recv-level parameter.
         When max-dpb is signaled, the receiver MUST be able to decode
         NAL unit streams that conform to the signaled highest level,
         with the exception that the MaxDPB value in Table A-1 of [1]
         for the signaled highest level is replaced with the value of
         max-dpb.  Consequently, a receiver that signals max-dpb MUST be
         capable of storing the following number of decoded frames,
         complementary field pairs, and non-paired fields in its decoded
         picture buffer:

            Min(1024 * max-dpb / ( PicWidthInMbs * FrameHeightInMbs *
            256 * ChromaFormatFactor ), 16)

         PicWidthInMbs, FrameHeightInMbs, and ChromaFormatFactor are
         defined in [1].

         The value of max-dpb MUST be greater than or equal to the value
         of MaxDPB given in Table A-1 of [1] for the highest level.
         Senders MAY use this knowledge to construct coded video streams
         with improved compression.
NEW: (When this change can be considered as editorial can be discussed, but the nature of this change as follows. On the other hand, if not changed, then the semantics of max-dpb is simply equivalent to unspecified, as MaxDPB and ChromaFormatFactor are not found in the latest H.264 spec any more. Note that compared to RFC 3984, the bits on the wire do not change.)
      max-dpb: The value of max-dpb is an integer indicating the maximum
         decoded picture buffer size in units of 8/3 macroblocks.  The max-
         dpb parameter signals that the receiver has more memory than
         the minimum amount of decoded picture buffer memory required by
         the signaled highest level conveyed in the value of the
         profile-level-id parameter or the max-recv-level parameter.
         When max-dpb is signaled, the receiver MUST be able to decode
         NAL unit streams that conform to the signaled highest level,
         with the exception that the MaxDpbMbs value in Table A-1 of [1]
         for the signaled highest level is replaced with the value of
         max-dpb * 3 / 8.  Consequently, a receiver that signals max-dpb MUST be
         capable of storing the following number of decoded frames,
         complementary field pairs, and non-paired fields in its decoded
         picture buffer:

            Min(max-dpb * 3 / 8 / ( PicWidthInMbs * FrameHeightInMbs), 16)

         Wherein PicWidthInMbs and FrameHeightInMbs are defined in [1].

         The value of max-dpb MUST be greater than or equal to the value
         of MaxDpbMbs * 3 / 8, wherein the value of MaxDpbMbs is given in
Table A-1 of [1] for the highest level.
         Senders MAY use this knowledge to construct coded video streams
         with improved compression.

OLD:

      max-br: The value of max-br is an integer indicating the maximum

         video bitrate in units of 1000 bits per second for the VCL HRD

         parameters (see A.3.1, item i of [1]) and in units of 1200 bits

         per second for the NAL HRD parameters (see A.3.1, item j of

         [1]).

         ...
         For example, if a receiver signals capability for Level 1.2
         with max-br equal to 1550, this indicates a maximum video
         bitrate of 1550 kbits/sec for VCL HRD parameters, a maximum
         video bitrate of 1860 kbits/sec for NAL HRD parameters, and a
         CPB size of 4036458 bits (1550000 / 384000 * 1000 * 1000).
NEW: (note that the change here is purely editorial)

      max-br: The value of max-br is an integer indicating the maximum

         video bitrate in units of 1000 bits per second for the VCL HRD

         parameters and in units of 1200 bits

         per second for the NAL HRD parameters.

         ...
         For example, if a receiver signals capability for Main profile Level 1.2
         with max-br equal to 1550, this indicates a maximum video
         bitrate of 1550 kbits/sec for VCL HRD parameters, a maximum
         video bitrate of 1860 kbits/sec for NAL HRD parameters, and a
         CPB size of 4036458 bits (1550000 / 384000 * 1000 * 1000).


------------------------------------End of suggested changes --------------------------------------

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Ye-Kui Wang
Sent: Sunday, March 20, 2011 4:21 AM
To: payload@ietf.org; avt@ietf.org
Subject: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload drafts

Folks,

The three H.264/AVC related payload formats, namely, draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-rtp-svc-27, and draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48 stage.

The RFC-Editor has found the following problem: In draft-ietf-avt-rtp-rfc3984bis-12, the definition of the max-dpb media parameter refers to the MaxDPB that was defined the first version of the H.264/AVC spec, but not any more in the latest version (the 2010 version). The parameter in the latest H.264/AVC version corresponding to MaxDPB is MaxDpbMbs, and the unit of the new parameter (i.e., macroblocks) is different from the original one (i.e. 1024 bytes).

The problem applies also to the SVC payload format, the RCDO payload format, and H.241.

A solution has been found and agreed, involving rfc3984bis authors and some key people related to H.264/AVC (e.g., Gary Sullivan and Heiko Schwarz) and H.241 (e.g., Stephen Botzko and Patrick Luthi). Furthermore, we have found that there are also a couple of places that need fixes due to similar changes from the initial version of H.264/AVC to the latest version.

Per Roni's suggestion, I am sending in below the changes to draft-ietf-avt-rtp-rfc3984bis-12 for review by the Payload and AVTcore WGs. It seems that exactly the same changes are needed to draft-ietf-avt-rtp-h264-rcdo-08 (co-authors of this draft may confirm), and similar but slightly different changes are needed to draft-ietf-avt-rtp-svc-27.

Since the drafts are at the AUTH48 stage, please provide comments by Monday, March 21, if any. Many thanks!

BR, YK


--Boundary_(ID_hcR2NkBpOkdtxtm59hGaDw)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* 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:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:SimSun;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:SimSun;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple" style=3D"text-justify-t=
rim:punctuation">
<div class=3D"Section1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">Furt=
her discussions with the same group of persons led to a decision to stay wi=
th the unscaled units for max-br and max-cpb, thus fewer changes are needed=
 to the three payload formats listed in
 the title and H.241. With this, the changes needed are listed below (the o=
riginally suggested changes are dropped from this email). This time I have =
highlighted the changes, and I have also described the nature the changes b=
elow. Hope these may help understand
 better what have been changed, and can lead to a quicker decision by the g=
roup, including WG chairs, and our AD.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt"><o:p=
>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">BR, =
YK<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt"><o:p=
>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">----------------------------=
--------Start of suggested changes --------------------------------------<o=
:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Section=
 8.1:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">OLD:<o:=
p></o:p></span></p>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; profile-level-id:<=
o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
A base16 [7] (hexadecimal) representation of the following<o:p></o:p></span=
></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
three bytes in the sequence parameter set NAL unit is specified<o:p></o:p><=
/span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
in [1]: 1) profile_idc, 2) a byte herein referred to as<o:p></o:p></span></=
pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
profile-iop, composed of the values of constraint_set0_flag,<o:p></o:p></sp=
an></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
constraint_set1_flag,constraint_set2_flag,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
constraint_set3_flag, and reserved_zero_4bits in bit-<o:p></o:p></span></pr=
e>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
significance order, starting from the most-significant bit, and<o:p></o:p><=
/span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
3) level_idc.&nbsp; Note that reserved_zero_4bits is required to be<o:p></o=
:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
equal to 0 in [1], but other values for it may be specified in<o:p></o:p></=
span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
the future by ITU-T or ISO/IEC.<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;N=
EW: <span style=3D"background:aqua;mso-highlight:aqua">
(note that the change here is purely editorial)</span><o:p></o:p></span></p=
>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; profile-level-id:<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A base16 [7] (hexadecimal) representation of=
 the following<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; three bytes in the sequence parameter set NA=
L unit is specified<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in [1]: 1) profile_idc, 2) a byte herein ref=
erred to as<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; profile-iop, composed of the values of const=
raint_set0_flag,<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; constraint_set1_flag,constraint_set2_flag,<o=
:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; constraint_set3_flag,
<span style=3D"background:yellow;mso-highlight:yellow">constraint_set4_flag=
, constraint_set5_flag,<o:p></o:p></span></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-indent:=
48.0pt"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun;b=
ackground:yellow;
mso-highlight:yellow">&nbsp;and reserved_zero_2bits</span><span lang=3D"EN-=
US" style=3D"font-size:12.0pt;font-family:SimSun">
 in bit-significance order, starting from the most-significant bit, and<o:p=
></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3) level_idc.&nbsp; Note that reserved_zero_=
2bits is required to be<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; equal to 0 in [1], but other values for it m=
ay be specified in<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;the future by ITU-T or ISO/IEC.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">OLD:<o:=
p></o:p></span></p>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
For example, in the table above, profile_idc equal to 58<o:p></o:p></span><=
/pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
(Extended) with profile-iop equal to 11xx0000 indicates the<o:p></o:p></spa=
n></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
same sub-profile corresponding to profile_idc equal to 42<o:p></o:p></span>=
</pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
(Baseline) with profile-iop equal to x1xx0000.&nbsp; Note that other<o:p></=
o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
combinations of profile_idc and profile-iop (not listed in<o:p></o:p></span=
></pre>
<pre><span lang=3D"EN-US"> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
Table 5) may represent a sub-profile equivalent to the common<o:p></o:p></s=
pan></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
subset of coding tools for more than one profile.&nbsp; Note also<o:p></o:p=
></span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
that a decoder conforming to a certain profile may be able to<o:p></o:p></s=
pan></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
decode bitstreams conforming to other profiles.&nbsp; <span style=3D"backgr=
ound:red;mso-highlight:red">For example, a<o:p></o:p></span></span></pre>
<pre><span lang=3D"EN-US" style=3D"background:red;mso-highlight:red">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; decoder conforming to the High 4=
:4:4 profile, at a certain<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"background:red;mso-highlight:red">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; level, must be able to decode bi=
tstreams conforming to the<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"background:red;mso-highlight:red">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Constrained Baseline, Main, High=
, High 10, or High 4:2:2<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"background:red;mso-highlight:red">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; profile at the same or a lower l=
evel.</span><span lang=3D"EN-US"><o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;N=
EW: <span style=3D"background:aqua;mso-highlight:aqua">
(note that the change here is purely editorial)</span><o:p></o:p></span></p=
>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; For example, in the table above, profile_idc=
 equal to 58<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (Extended) with profile-iop equal to 11xx000=
0 indicates the<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; same sub-profile corresponding to profile_id=
c equal to 42<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (Baseline) with profile-iop equal to x1xx000=
0.&nbsp; Note that other<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; combinations of profile_idc and profile-iop =
(not listed in<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Table 5) may represent a sub-profile equival=
ent to the common<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; subset of coding tools for more than one pro=
file.&nbsp; Note also<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;that a decoder conforming to a certain profi=
le may be able to<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; decode bitstreams conforming to other profil=
es.<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">OLD:<o:=
p></o:p></span></p>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
If the profile-level-id parameter is used for capability<o:p></o:p></span><=
/pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
exchange or session setup <span style=3D"background:red;mso-highlight:red">=
procedure</span>, it indicates the subset of<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
coding tools, which is equal to the default sub-profile, that<o:p></o:p></s=
pan></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
the codec supports for both receiving and sending.<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;N=
EW: <span style=3D"background:aqua;mso-highlight:aqua">
(note that the change here is purely editorial)</span><o:p></o:p></span></p=
>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If the profile-level-id parameter is used fo=
r capability<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; exchange or session setup, it indicates the =
subset of<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; coding tools, which is equal to the default =
sub-profile, that<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the codec supports for both receiving and se=
nding.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">OLD: <o=
:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; max-cpb: The value of max-cpb is an integer indicating the max=
imum<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; coded picture buffer size in units of 1000 b=
its for the VCL HRD<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; parameters
<span style=3D"background:red;mso-highlight:red">(see A.3.1, item i of [1])=
</span> and in units of 1200 bits<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the NAL HRD parameters
<span style=3D"background:red;mso-highlight:red">(see A.3.1, item j of [1])=
</span>.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">NEW: <s=
pan style=3D"background:aqua;mso-highlight:aqua">
(note that the change here is purely editorial)</span><o:p></o:p></span></p=
>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; max-cpb: The value of max-cpb is an integer indicating the max=
imum<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; coded picture buffer size in units of 1000 b=
its for the VCL HRD<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; parameters and in units of 1200 bits<o:p></o=
:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the NAL HRD parameters.<o:p></o:p></span=
></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">OLD:<o:=
p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; max-dpb: The value of max-dpb is an integer indicating the max=
imum<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; decoded picture buffer size in units of 1024=
 bytes.&nbsp; The max-<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dpb parameter signals that the receiver has =
more memory than<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the minimum amount of decoded picture buffer=
 memory required by<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the signaled highest level conveyed in the v=
alue of the<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; profile-level-id parameter or the max-recv-l=
evel parameter.<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When max-dpb is signaled, the receiver MUST =
be able to decode<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAL unit streams that conform to the signale=
d highest level,<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with the exception that the MaxDPB value in =
Table A-1 of [1]<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the signaled highest level is replaced w=
ith the value of<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-dpb.&nbsp; Consequently, a receiver that=
 signals max-dpb MUST be<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; capable of storing the following number of d=
ecoded frames,<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; complementary field pairs, and non-paired fi=
elds in its decoded<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; picture buffer:<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p><=
/span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Min(1024 * max-dpb / ( Pic=
WidthInMbs * FrameHeightInMbs *<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 256 * ChromaFormatFactor )=
, 16)<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p><=
/span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PicWidthInMbs, FrameHeightInMbs, and ChromaF=
ormatFactor are<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp; &nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;defined in [1].<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p><=
/span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The value of max-dpb MUST be greater than or=
 equal to the value<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of MaxDPB given in Table A-1 of [1] for the =
highest level.<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Senders MAY use this knowledge to construct =
coded video streams<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with improved compression.<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">NEW: <s=
pan style=3D"background:aqua;mso-highlight:aqua">
(When this change can be considered as editorial can be discussed, but the =
nature of this change as follows. On the other hand, if not changed, then t=
he semantics of max-dpb is simply equivalent to unspecified, as MaxDPB and =
ChromaFormatFactor are not found
 in the latest H.264 spec any more. Note that compared to RFC 3984, the bit=
s on the wire do not change.)</span><o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; max-dpb: The value of max-dpb is an integer indicating the max=
imum<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; decoded picture buffer size in units of 8/3 =
macroblocks.&nbsp; The max-<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dpb parameter signals that the receiver has =
more memory than<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the minimum amount of decoded picture buffer=
 memory required by<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the signaled highest level conveyed in the v=
alue of the<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; profile-level-id parameter or the max-recv-l=
evel parameter.<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When max-dpb is signaled, the receiver MUST =
be able to decode<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAL unit streams that conform to the signale=
d highest level,<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with the exception that
<span style=3D"background:yellow;mso-highlight:yellow">the MaxDpbMbs value =
in Table A-1 of [1]<o:p></o:p></span></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun;background:yellow;m=
so-highlight:
yellow">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the signaled h=
ighest level is replaced with the value of<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun;background:yellow;m=
so-highlight:
yellow">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-dpb * 3 / 8</s=
pan><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">.&nb=
sp;
 Consequently, a receiver that signals max-dpb MUST be<o:p></o:p></span></p=
>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; capable of storing the following number of d=
ecoded frames,<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; complementary field pairs, and non-paired fi=
elds in its decoded<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; picture buffer:<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p><=
/span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<span style=3D"background:yellow;mso-highlight:yellow">Min(max-dpb * 3 / 8 =
/ ( PicWidthInMbs * FrameHeightInMbs), 16)<o:p></o:p></span></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun;background:yellow;m=
so-highlight:
yellow"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun;background:yellow;m=
so-highlight:
yellow">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Wherein PicWidthIn=
Mbs and FrameHeightInMbs are defined in [1].</span><span lang=3D"EN-US" sty=
le=3D"font-size:12.0pt;font-family:SimSun"><o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p><=
/span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The value of max-dpb MUST be greater than or=
 equal to the value<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of
<span style=3D"background:yellow;mso-highlight:yellow">MaxDpbMbs * 3 / 8, w=
herein the value of MaxDpbMbs is given in
<o:p></o:p></span></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left;text-indent:=
54.0pt"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun;b=
ackground:yellow;
mso-highlight:yellow">Table A-1 of [1] for the highest level.</span><span l=
ang=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun"><o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Senders MAY use this knowledge to construct =
coded video streams<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with improved compression.<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">OLD:<o:=
p></o:p></span></p>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-br: The value =
of max-br is an integer indicating the maximum<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
video bitrate in units of 1000 bits per second for the VCL HRD<o:p></o:p></=
span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
parameters <span style=3D"background:red;mso-highlight:red">(see A.3.1, ite=
m i of [1])</span> and in units of 1200 bits<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
per second for the NAL HRD parameters <span style=3D"background:red;mso-hig=
hlight:red">(see A.3.1, item j of</span><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<span style=3D"background:red;mso-highlight:red">[1])</span>.<o:p></o:p></s=
pan></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>&#8230;<span lang=3D"EN-US"><o:p></o:p></span></pre>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; For example, if a receiver signals capabilit=
y for Level 1.2<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with max-br equal to 1550, this indicates a =
maximum video<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bitrate of 1550 kbits/sec for VCL HRD parame=
ters, a maximum<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; video bitrate of 1860 kbits/sec for NAL HRD =
parameters, and a<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp; &nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPB size of 4036458 bits (1550000 / 384000 *=
 1000 * 1000).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">NEW: <s=
pan style=3D"background:aqua;mso-highlight:aqua">
(note that the change here is purely editorial)</span> <o:p></o:p></span></=
p>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-br: The value =
of max-br is an integer indicating the maximum<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
video bitrate in units of 1000 bits per second for the VCL HRD<o:p></o:p></=
span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
parameters and in units of 1200 bits<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
per second for the NAL HRD parameters.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>&#8230;<span lang=3D"EN-US"><o:p></o:p></span></pre>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; For example, if a receiver signals capabilit=
y for
<span style=3D"background:yellow;
mso-highlight:yellow">Main profile</span> Level 1.2<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with max-br equal to 1550, this indicates a =
maximum video<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bitrate of 1550 kbits/sec for VCL HRD parame=
ters, a maximum<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; video bitrate of 1860 kbits/sec for NAL HRD =
parameters, and a<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:SimSun">&nbsp; &nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPB size of 4036458 bits (1550000 / 384000 *=
 1000 * 1000).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">----------------------------=
--------End of suggested changes --------------------------------------<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><b><span la=
ng=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot=
;sans-serif&quot;">From:</span></b><span lang=3D"EN-US" style=3D"font-size:=
10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> avt-bounces@=
ietf.org [mailto:avt-bounces@ietf.org]
<b>On Behalf Of </b>Ye-Kui Wang<br>
<b>Sent:</b> Sunday, March 20, 2011 4:21 AM<br>
<b>To:</b> payload@ietf.org; avt@ietf.org<br>
<b>Subject:</b> [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload=
 drafts<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Folks,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The three H.264/AVC related pay=
load formats, namely, draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-rtp-=
svc-27, and draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48 stage.<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The RFC-Editor has found the fo=
llowing problem: In draft-ietf-avt-rtp-rfc3984bis-12, the definition of the=
 max-dpb media parameter refers to the MaxDPB that was defined the first ve=
rsion of the H.264/AVC spec, but not
 any more in the latest version (the 2010 version). The parameter in the la=
test H.264/AVC version corresponding to MaxDPB is MaxDpbMbs, and the unit o=
f the new parameter (i.e., macroblocks) is different from the original one =
(i.e. 1024 bytes).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The problem applies also to the=
 SVC payload format, the RCDO payload format, and H.241.<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">A solution has been found and a=
greed, involving rfc3984bis authors and some key people related to H.264/AV=
C (e.g., Gary Sullivan and Heiko Schwarz) and H.241 (e.g., Stephen Botzko a=
nd Patrick Luthi). Furthermore, we have
 found that there are also a couple of places that need fixes due to simila=
r changes from the initial version of H.264/AVC to the latest version.<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Per Roni&#8217;s suggestion, I =
am sending in below the changes to draft-ietf-avt-rtp-rfc3984bis-12 for rev=
iew by the Payload and AVTcore WGs. It seems that exactly the same changes =
are needed to draft-ietf-avt-rtp-h264-rcdo-08
 (co-authors of this draft may confirm), and similar but slightly different=
 changes are needed to draft-ietf-avt-rtp-svc-27.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Since the drafts are at the AUT=
H48 stage, please provide comments by Monday, March 21, if any. Many thanks=
!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">BR, YK<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--Boundary_(ID_hcR2NkBpOkdtxtm59hGaDw)--

From keith.drage@alcatel-lucent.com  Mon Mar 21 03:28:52 2011
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 27D013A681C; Mon, 21 Mar 2011 03:28:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.777
X-Spam-Level: 
X-Spam-Status: No, score=-105.777 tagged_above=-999 required=5 tests=[AWL=0.472, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2l12GTmsjSzk; Mon, 21 Mar 2011 03:28:51 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [62.23.212.57]) by core3.amsl.com (Postfix) with ESMTP id C894B3A6818; Mon, 21 Mar 2011 03:28:50 -0700 (PDT)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p2LATHDE031448 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 21 Mar 2011 11:30:16 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Mon, 21 Mar 2011 11:29:55 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Glen Zorn <gwz@net-zen.net>, Roni Even <Even.roni@huawei.com>
Date: Mon, 21 Mar 2011 11:29:54 +0100
Thread-Topic: [AVTCORE] Some changes to rfc3984bis, SVC,	and RCDO payload drafts
Thread-Index: Acvnjt6mHYE390w2T4akPFUwjAYpLQAI8Gtw
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE21EAC6B5F@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <B99DECD58A94E143BA6F1508CC688351B417FB@dfweml504-mbx.china.huawei.com> <4D85C5FA.4010407@net-zen.net> <000701cbe6f9$f44b1e80$dce15b80$%roni@huawei.com> <4D86EC09.2020304@net-zen.net>
In-Reply-To: <4D86EC09.2020304@net-zen.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
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Cc: "avt@ietf.org" <avt@ietf.org>, "payload@ietf.org" <payload@ietf.org>
Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2011 10:28:52 -0000

Technical changes can be made, but they require the approval of the area di=
rector, who has the right to either ask for consensus of the mailing list f=
irst or indeed send it back to the working group.

I would suggest we allow significantly longer than over the weekend for WG =
comment before accepting the change, e.g. until Monday 28th March.

Regards

Keith

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Gle=
n
> Zorn
> Sent: 21 March 2011 06:11
> To: Roni Even
> Cc: payload@ietf.org; avt@ietf.org
> Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload
> drafts
>=20
> On 3/20/2011 7:25 PM, Roni Even wrote:
>=20
> > Hi Glen,
> > The technical change is more in H.264/AVC specification. In the payload
> > specifications (3984bis/ RCDO and SVC) the change is to specify the
> > conversion between the old and new parameter and to explain the change
> in
> > H.264.
> > It can be looked as a technical and I will leave it to the AD to help
> here.
> >
> > As for the quality of the change it was done by YK with the help of
> Steve
> > Botzko (H.241 editor) and Gary Sullivan the Rapportuer of Q6 SG16 that
> does
> > the video codec in a f2f meeting. It was also reviewed by me and by som=
e
> > other experts on video coding and I feel good about the solution,
>=20
> I'm admittedly not an expert on H.264, so I can't quibble about the
> quality of the proposed solution.  My comment is a procedural one: I
> don't believe that technical changes are allowed after the completion of
> IETF review, nor should they be.  My understanding is that the AUTH48
> review is provided only as a last-minute opportunity to catch typos or
> make small editorial changes, not to modify the technical content of a
> document.  BTW, I'm in the same boat myself right now: one of my
> co-authors has fairly significant technical changes (and has proposed
> even bigger ones) to a draft now in AUTH48 & I'm saying the same thing
> about that one.  I'm _not_ looking forward to restarting the whole
> process, but OTOH my co-author (& for that matter, I) should have had
> our act together before requesting publication.
>=20
> >
> > This change involves also an update to H.241 that has the same issue an=
d
> the
> > objective is to approve the H.241 change this week at the ongoing ITU
> Study
> > Group 16 meeting. The solution for the IETF draft and ITU draft should
> be
> > the same to address interoperability.
> >
> > Thanks
> > Roni Even
> > As individual.
> >
> >
> >> -----Original Message-----
> >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> >> Glen Zorn
> >> Sent: Sunday, March 20, 2011 11:17 AM
> >> To: Ye-Kui Wang
> >> Cc: avt@ietf.org; payload@ietf.org
> >> Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO
> >> payload drafts
> >>
> >> On 3/20/2011 3:20 PM, Ye-Kui Wang wrote:
> >>> Folks,
> >>>
> >>>
> >>>
> >>> The three H.264/AVC related payload formats, namely,
> >>> draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-rtp-svc-27, and
> >>> draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48 stage.
> >>>
> >>>
> >>>
> >>> The RFC-Editor has found the following problem: In
> >>> draft-ietf-avt-rtp-rfc3984bis-12, the definition of the max-dpb media
> >>> parameter refers to the MaxDPB that was defined the first version of
> >> the
> >>> H.264/AVC spec, but not any more in the latest version (the 2010
> >>> version). The parameter in the latest H.264/AVC version corresponding
> >> to
> >>> MaxDPB is MaxDpbMbs, and the unit of the new parameter (i.e.,
> >>> macroblocks) is different from the original one (i.e. 1024 bytes).
> >>
> >> ...
> >>
> >>> Since the drafts are at the AUTH48 stage, please provide comments by
> >>> Monday, March 21, if any. Many thanks!
> >>
> >> Just my opinion but these seem like technical changes that can't reall=
y
> >> be dealt with in AUTH48.
> >>
> >> ...
> >> _______________________________________________
> >> 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 stephen.botzko@gmail.com  Mon Mar 21 03:44:35 2011
Return-Path: <stephen.botzko@gmail.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A4C3428C10A; Mon, 21 Mar 2011 03:44:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.181
X-Spam-Level: 
X-Spam-Status: No, score=-3.181 tagged_above=-999 required=5 tests=[AWL=0.417,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NWzrweSy9IWi; Mon, 21 Mar 2011 03:44:34 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id D9CE328C119; Mon, 21 Mar 2011 03:44:33 -0700 (PDT)
Received: by vws12 with SMTP id 12so5938168vws.31 for <multiple recipients>; Mon, 21 Mar 2011 03:46:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=G15x4nuSZoqr2QLIQJV14kapCFKu3EET3t6EXVfhoDw=; b=DGPRJb2G8J9Bk9rUpT0kWJxDMW3Azz9YW6kFyVD0tmNojLu30y6S4QfAXmJc6p09Qz orjM6yAZkMj8i911IVqwamRb2qftS+rjXHYDM4eMtBgiSkxo/FEV2Ideg3sxzt+SW1O1 9Zzp3PYcToCh5DHYK1+cm5uGSkx4AtduBRjuE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Q7Cq/cUB1nqHDWJ1AZ/LfOYUQO5glcpU2jM7IgczVcQ/HJFCZK207qam5r5iz7pOUG 1qV8aPqrQS5IfcP+/V5/C8Mr4zZ1JQe5b57Ecf5O/Py0OTQ6ci/CaBbiPjARG3J7xo6E 7in4JiQEbWdaqDUoZU/tRL6ZhusSR7MOU77YU=
MIME-Version: 1.0
Received: by 10.220.199.141 with SMTP id es13mr1112044vcb.73.1300704365849; Mon, 21 Mar 2011 03:46:05 -0700 (PDT)
Received: by 10.220.170.196 with HTTP; Mon, 21 Mar 2011 03:46:05 -0700 (PDT)
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE21EAC6B5F@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <B99DECD58A94E143BA6F1508CC688351B417FB@dfweml504-mbx.china.huawei.com> <4D85C5FA.4010407@net-zen.net> <000701cbe6f9$f44b1e80$dce15b80$%roni@huawei.com> <4D86EC09.2020304@net-zen.net> <EDC0A1AE77C57744B664A310A0B23AE21EAC6B5F@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Date: Mon, 21 Mar 2011 11:46:05 +0100
Message-ID: <AANLkTin1EKGtPba2Z8fvsYUMOiDyQPvb1_RMpWsQeF7i@mail.gmail.com>
From: Stephen Botzko <stephen.botzko@gmail.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=90e6ba53a014af2eb1049efbd5e5
Cc: "payload@ietf.org" <payload@ietf.org>, Roni Even <Even.roni@huawei.com>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] [payload]  Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2011 10:44:35 -0000

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

Delaying until 28 March makes sense for several reasons.

The related change to H.241 should be submitted for consent on 25 March.
Since the max-dbp parameter is intended to provide an equivalent codepoint
to the one in H.241, it is sensible to wait for the H.241 outcome before
locking this down.

On the text itself, I am fine with it (presuming H.241 progresses as
expected).  It makes little sense for these new RFCs to refer to a
superseded version of H.264, so there needs to be some change to the current
text.  In the end, the proposed change simply adjusts the units to be
consistent with the current H.264.  Since the units are scaled so the actual
value on the wire is unchanged, it provides backwards compatibility.

I don't personally see the need to send it back to the Working Group, but
allowing time for WG comment is prudent.

Stephen Botzko

On Mon, Mar 21, 2011 at 11:29 AM, DRAGE, Keith (Keith) <
keith.drage@alcatel-lucent.com> wrote:

> Technical changes can be made, but they require the approval of the area
> director, who has the right to either ask for consensus of the mailing list
> first or indeed send it back to the working group.
>
> I would suggest we allow significantly longer than over the weekend for WG
> comment before accepting the change, e.g. until Monday 28th March.
>
> Regards
>
> Keith
>
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Glen
> > Zorn
> > Sent: 21 March 2011 06:11
> > To: Roni Even
> > Cc: payload@ietf.org; avt@ietf.org
> > Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload
> > drafts
> >
> > On 3/20/2011 7:25 PM, Roni Even wrote:
> >
> > > Hi Glen,
> > > The technical change is more in H.264/AVC specification. In the payload
> > > specifications (3984bis/ RCDO and SVC) the change is to specify the
> > > conversion between the old and new parameter and to explain the change
> > in
> > > H.264.
> > > It can be looked as a technical and I will leave it to the AD to help
> > here.
> > >
> > > As for the quality of the change it was done by YK with the help of
> > Steve
> > > Botzko (H.241 editor) and Gary Sullivan the Rapportuer of Q6 SG16 that
> > does
> > > the video codec in a f2f meeting. It was also reviewed by me and by
> some
> > > other experts on video coding and I feel good about the solution,
> >
> > I'm admittedly not an expert on H.264, so I can't quibble about the
> > quality of the proposed solution.  My comment is a procedural one: I
> > don't believe that technical changes are allowed after the completion of
> > IETF review, nor should they be.  My understanding is that the AUTH48
> > review is provided only as a last-minute opportunity to catch typos or
> > make small editorial changes, not to modify the technical content of a
> > document.  BTW, I'm in the same boat myself right now: one of my
> > co-authors has fairly significant technical changes (and has proposed
> > even bigger ones) to a draft now in AUTH48 & I'm saying the same thing
> > about that one.  I'm _not_ looking forward to restarting the whole
> > process, but OTOH my co-author (& for that matter, I) should have had
> > our act together before requesting publication.
> >
> > >
> > > This change involves also an update to H.241 that has the same issue
> and
> > the
> > > objective is to approve the H.241 change this week at the ongoing ITU
> > Study
> > > Group 16 meeting. The solution for the IETF draft and ITU draft should
> > be
> > > the same to address interoperability.
> > >
> > > Thanks
> > > Roni Even
> > > As individual.
> > >
> > >
> > >> -----Original Message-----
> > >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> > >> Glen Zorn
> > >> Sent: Sunday, March 20, 2011 11:17 AM
> > >> To: Ye-Kui Wang
> > >> Cc: avt@ietf.org; payload@ietf.org
> > >> Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO
> > >> payload drafts
> > >>
> > >> On 3/20/2011 3:20 PM, Ye-Kui Wang wrote:
> > >>> Folks,
> > >>>
> > >>>
> > >>>
> > >>> The three H.264/AVC related payload formats, namely,
> > >>> draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-rtp-svc-27, and
> > >>> draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48 stage.
> > >>>
> > >>>
> > >>>
> > >>> The RFC-Editor has found the following problem: In
> > >>> draft-ietf-avt-rtp-rfc3984bis-12, the definition of the max-dpb media
> > >>> parameter refers to the MaxDPB that was defined the first version of
> > >> the
> > >>> H.264/AVC spec, but not any more in the latest version (the 2010
> > >>> version). The parameter in the latest H.264/AVC version corresponding
> > >> to
> > >>> MaxDPB is MaxDpbMbs, and the unit of the new parameter (i.e.,
> > >>> macroblocks) is different from the original one (i.e. 1024 bytes).
> > >>
> > >> ...
> > >>
> > >>> Since the drafts are at the AUTH48 stage, please provide comments by
> > >>> Monday, March 21, if any. Many thanks!
> > >>
> > >> Just my opinion but these seem like technical changes that can't
> really
> > >> be dealt with in AUTH48.
> > >>
> > >> ...
> > >> _______________________________________________
> > >> 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
> _______________________________________________
> payload mailing list
> payload@ietf.org
> https://www.ietf.org/mailman/listinfo/payload
>

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

Delaying until 28 March makes sense for several reasons.<br><br>The related=
 change to H.241 should be submitted for consent on 25 March.=A0 Since the =
max-dbp parameter is intended to provide an equivalent codepoint to the one=
 in H.241, it is sensible to wait for the H.241 outcome before locking this=
 down.<br>
<br>On the text itself, I am fine with it (presuming H.241 progresses as ex=
pected).=A0 It makes little sense for these new RFCs to refer to a supersed=
ed version of H.264, so there needs to be some change to the current text.=
=A0 In the end, the proposed change simply adjusts the units to be consiste=
nt with the current H.264.=A0 Since the units are scaled so the actual valu=
e on the wire is unchanged, it provides backwards compatibility.=A0 <br>
<br>I don&#39;t personally see the need to send it back to the Working Grou=
p, but allowing time for WG comment is prudent.<br><br>Stephen Botzko<br><b=
r><div class=3D"gmail_quote">On Mon, Mar 21, 2011 at 11:29 AM, DRAGE, Keith=
 (Keith) <span dir=3D"ltr">&lt;<a href=3D"mailto:keith.drage@alcatel-lucent=
.com">keith.drage@alcatel-lucent.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Technical changes=
 can be made, but they require the approval of the area director, who has t=
he right to either ask for consensus of the mailing list first or indeed se=
nd it back to the working group.<br>

<br>
I would suggest we allow significantly longer than over the weekend for WG =
comment before accepting the change, e.g. until Monday 28th March.<br>
<br>
Regards<br>
<br>
Keith<br>
<div class=3D"im"><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 Glen<br>
&gt; Zorn<br>
</div><div><div></div><div class=3D"h5">&gt; Sent: 21 March 2011 06:11<br>
&gt; To: Roni Even<br>
&gt; Cc: <a href=3D"mailto:payload@ietf.org">payload@ietf.org</a>; <a href=
=3D"mailto:avt@ietf.org">avt@ietf.org</a><br>
&gt; Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO paylo=
ad<br>
&gt; drafts<br>
&gt;<br>
&gt; On 3/20/2011 7:25 PM, Roni Even wrote:<br>
&gt;<br>
&gt; &gt; Hi Glen,<br>
&gt; &gt; The technical change is more in H.264/AVC specification. In the p=
ayload<br>
&gt; &gt; specifications (3984bis/ RCDO and SVC) the change is to specify t=
he<br>
&gt; &gt; conversion between the old and new parameter and to explain the c=
hange<br>
&gt; in<br>
&gt; &gt; H.264.<br>
&gt; &gt; It can be looked as a technical and I will leave it to the AD to =
help<br>
&gt; here.<br>
&gt; &gt;<br>
&gt; &gt; As for the quality of the change it was done by YK with the help =
of<br>
&gt; Steve<br>
&gt; &gt; Botzko (H.241 editor) and Gary Sullivan the Rapportuer of Q6 SG16=
 that<br>
&gt; does<br>
&gt; &gt; the video codec in a f2f meeting. It was also reviewed by me and =
by some<br>
&gt; &gt; other experts on video coding and I feel good about the solution,=
<br>
&gt;<br>
&gt; I&#39;m admittedly not an expert on H.264, so I can&#39;t quibble abou=
t the<br>
&gt; quality of the proposed solution. =A0My comment is a procedural one: I=
<br>
&gt; don&#39;t believe that technical changes are allowed after the complet=
ion of<br>
&gt; IETF review, nor should they be. =A0My understanding is that the AUTH4=
8<br>
&gt; review is provided only as a last-minute opportunity to catch typos or=
<br>
&gt; make small editorial changes, not to modify the technical content of a=
<br>
&gt; document. =A0BTW, I&#39;m in the same boat myself right now: one of my=
<br>
&gt; co-authors has fairly significant technical changes (and has proposed<=
br>
&gt; even bigger ones) to a draft now in AUTH48 &amp; I&#39;m saying the sa=
me thing<br>
&gt; about that one. =A0I&#39;m _not_ looking forward to restarting the who=
le<br>
&gt; process, but OTOH my co-author (&amp; for that matter, I) should have =
had<br>
&gt; our act together before requesting publication.<br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt; This change involves also an update to H.241 that has the same is=
sue and<br>
&gt; the<br>
&gt; &gt; objective is to approve the H.241 change this week at the ongoing=
 ITU<br>
&gt; Study<br>
&gt; &gt; Group 16 meeting. The solution for the IETF draft and ITU draft s=
hould<br>
&gt; be<br>
&gt; &gt; the same to address interoperability.<br>
&gt; &gt;<br>
&gt; &gt; Thanks<br>
&gt; &gt; Roni Even<br>
&gt; &gt; As individual.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt; From: <a href=3D"mailto:avt-bounces@ietf.org">avt-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:avt-bounces@ietf.org">avt-bounces@ietf.=
org</a>] On Behalf Of<br>
&gt; &gt;&gt; Glen Zorn<br>
&gt; &gt;&gt; Sent: Sunday, March 20, 2011 11:17 AM<br>
&gt; &gt;&gt; To: Ye-Kui Wang<br>
&gt; &gt;&gt; Cc: <a href=3D"mailto:avt@ietf.org">avt@ietf.org</a>; <a href=
=3D"mailto:payload@ietf.org">payload@ietf.org</a><br>
&gt; &gt;&gt; Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC, and R=
CDO<br>
&gt; &gt;&gt; payload drafts<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; On 3/20/2011 3:20 PM, Ye-Kui Wang wrote:<br>
&gt; &gt;&gt;&gt; Folks,<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; The three H.264/AVC related payload formats, namely,<br>
&gt; &gt;&gt;&gt; draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-rtp-svc-=
27, and<br>
&gt; &gt;&gt;&gt; draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48 st=
age.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; The RFC-Editor has found the following problem: In<br>
&gt; &gt;&gt;&gt; draft-ietf-avt-rtp-rfc3984bis-12, the definition of the m=
ax-dpb media<br>
&gt; &gt;&gt;&gt; parameter refers to the MaxDPB that was defined the first=
 version of<br>
&gt; &gt;&gt; the<br>
&gt; &gt;&gt;&gt; H.264/AVC spec, but not any more in the latest version (t=
he 2010<br>
&gt; &gt;&gt;&gt; version). The parameter in the latest H.264/AVC version c=
orresponding<br>
&gt; &gt;&gt; to<br>
&gt; &gt;&gt;&gt; MaxDPB is MaxDpbMbs, and the unit of the new parameter (i=
.e.,<br>
&gt; &gt;&gt;&gt; macroblocks) is different from the original one (i.e. 102=
4 bytes).<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; ...<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt; Since the drafts are at the AUTH48 stage, please provide =
comments by<br>
&gt; &gt;&gt;&gt; Monday, March 21, if any. Many thanks!<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Just my opinion but these seem like technical changes that ca=
n&#39;t really<br>
&gt; &gt;&gt; be dealt with in AUTH48.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; ...<br>
&gt; &gt;&gt; _______________________________________________<br>
&gt; &gt;&gt; Audio/Video Transport Core Maintenance<br>
&gt; &gt;&gt; <a href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br>
&gt; &gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/avt" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/avt</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &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>
</div></div>_______________________________________________<br>
payload mailing list<br>
<a href=3D"mailto:payload@ietf.org">payload@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/payload" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/payload</a><br>
</blockquote></div><br>

--90e6ba53a014af2eb1049efbd5e5--

From eckelcu@cisco.com  Mon Mar 21 10:50:34 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 93E843A687B; Mon, 21 Mar 2011 10:50:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.276
X-Spam-Level: 
X-Spam-Status: No, score=-10.276 tagged_above=-999 required=5 tests=[AWL=-0.277, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZeL6dLuPw2YQ; Mon, 21 Mar 2011 10:50:32 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id D13FB28C0D8; Mon, 21 Mar 2011 10:50:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=13224; q=dns/txt; s=iport; t=1300729925; x=1301939525; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=5BtxtgH0NJfmCEECpQdYBkGQdLaPo8SVXzU/c+VVpMQ=; b=hszzpLgTDCVeQOp8JcOm8DkuNtDkdHPn/VMnZ0RoO8dRG7K4Y9Cd/WKA 01DFFtGhtrL8p/Ls8CE2dcuH5gfVku7qmu0y9MUCniJlit64uTYXMtMpW a3X2k+HHrMOT55LSfXiye0Rw15uIGQlLpQSfmAKG4T4fqoCUgo/UHaE5P I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4BAJcth02rRDoI/2dsb2JhbACXfY1Cd6YOnBaFYwSFM4sL
X-IronPort-AV: E=Sophos;i="4.63,220,1299456000"; d="scan'208";a="349937835"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-5.cisco.com with ESMTP; 21 Mar 2011 17:51:45 +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 p2LHpj0D016491; Mon, 21 Mar 2011 17:51:45 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 21 Mar 2011 10:51:45 -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: Mon, 21 Mar 2011 10:51:43 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE39AD@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <B99DECD58A94E143BA6F1508CC688351B445DE@dfweml504-mbx.china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [payload] Some changes to rfc3984bis, SVC, and RCDO payload drafts
Thread-Index: Acvm161AAF2A6AC0R/ODLEMZyh1IcgAwzyEAABVfHoA=
References: <B99DECD58A94E143BA6F1508CC688351B417FB@dfweml504-mbx.china.huawei.com> <B99DECD58A94E143BA6F1508CC688351B445DE@dfweml504-mbx.china.huawei.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Ye-Kui Wang" <yekui.wang@huawei.com>, <payload@ietf.org>, <avt@ietf.org>
X-OriginalArrivalTime: 21 Mar 2011 17:51:45.0267 (UTC) FILETIME=[A4C40C30:01CBE7F0]
Subject: Re: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2011 17:50:34 -0000

Hi YK,

Thank you for providing this clear description of the proposed changes.
The changes look good to me.

Cheers,
Charles

> -----Original Message-----
> From: payload-bounces@ietf.org [mailto:payload-bounces@ietf.org] On
Behalf Of Ye-Kui Wang
> Sent: Monday, March 21, 2011 1:11 AM
> To: payload@ietf.org; avt@ietf.org
> Subject: Re: [payload] Some changes to rfc3984bis, SVC,and RCDO
payload drafts
>=20
> Further discussions with the same group of persons led to a decision
to stay with the unscaled units
> for max-br and max-cpb, thus fewer changes are needed to the three
payload formats listed in the title
> and H.241. With this, the changes needed are listed below (the
originally suggested changes are
> dropped from this email). This time I have highlighted the changes,
and I have also described the
> nature the changes below. Hope these may help understand better what
have been changed, and can lead
> to a quicker decision by the group, including WG chairs, and our AD.
>=20
>=20
>=20
> BR, YK
>=20
>=20
>=20
> ------------------------------------Start of suggested changes
--------------------------------------
>=20
>=20
>=20
> Section 8.1:
>=20
> OLD:
>=20
>       profile-level-id:
>          A base16 [7] (hexadecimal) representation of the following
>          three bytes in the sequence parameter set NAL unit is
specified
>          in [1]: 1) profile_idc, 2) a byte herein referred to as
>          profile-iop, composed of the values of constraint_set0_flag,
>          constraint_set1_flag,constraint_set2_flag,
>          constraint_set3_flag, and reserved_zero_4bits in bit-
>          significance order, starting from the most-significant bit,
and
>          3) level_idc.  Note that reserved_zero_4bits is required to
be
>          equal to 0 in [1], but other values for it may be specified
in
>          the future by ITU-T or ISO/IEC.
>=20
>  NEW: (note that the change here is purely editorial)
>=20
>       profile-level-id:
>=20
>          A base16 [7] (hexadecimal) representation of the following
>=20
>          three bytes in the sequence parameter set NAL unit is
specified
>=20
>          in [1]: 1) profile_idc, 2) a byte herein referred to as
>=20
>          profile-iop, composed of the values of constraint_set0_flag,
>=20
>          constraint_set1_flag,constraint_set2_flag,
>=20
>          constraint_set3_flag, constraint_set4_flag,
constraint_set5_flag,
>=20
>  and reserved_zero_2bits in bit-significance order, starting from the
most-significant bit, and
>=20
>          3) level_idc.  Note that reserved_zero_2bits is required to
be
>=20
>          equal to 0 in [1], but other values for it may be specified
in
>=20
>          the future by ITU-T or ISO/IEC.
>=20
>=20
>=20
> OLD:
>=20
>          For example, in the table above, profile_idc equal to 58
>          (Extended) with profile-iop equal to 11xx0000 indicates the
>          same sub-profile corresponding to profile_idc equal to 42
>          (Baseline) with profile-iop equal to x1xx0000.  Note that
other
>          combinations of profile_idc and profile-iop (not listed in
>          Table 5) may represent a sub-profile equivalent to the common
>          subset of coding tools for more than one profile.  Note also
>          that a decoder conforming to a certain profile may be able to
>          decode bitstreams conforming to other profiles.  For example,
a
>          decoder conforming to the High 4:4:4 profile, at a certain
>          level, must be able to decode bitstreams conforming to the
>          Constrained Baseline, Main, High, High 10, or High 4:2:2
>          profile at the same or a lower level.
>=20
>  NEW: (note that the change here is purely editorial)
>=20
>          For example, in the table above, profile_idc equal to 58
>=20
>          (Extended) with profile-iop equal to 11xx0000 indicates the
>=20
>          same sub-profile corresponding to profile_idc equal to 42
>=20
>          (Baseline) with profile-iop equal to x1xx0000.  Note that
other
>=20
>          combinations of profile_idc and profile-iop (not listed in
>=20
>          Table 5) may represent a sub-profile equivalent to the common
>=20
>          subset of coding tools for more than one profile.  Note also
>=20
>          that a decoder conforming to a certain profile may be able to
>=20
>          decode bitstreams conforming to other profiles.
>=20
>=20
>=20
> OLD:
>=20
>          If the profile-level-id parameter is used for capability
>          exchange or session setup procedure, it indicates the subset
of
>          coding tools, which is equal to the default sub-profile, that
>          the codec supports for both receiving and sending.
>=20
>  NEW: (note that the change here is purely editorial)
>=20
>          If the profile-level-id parameter is used for capability
>=20
>          exchange or session setup, it indicates the subset of
>=20
>          coding tools, which is equal to the default sub-profile, that
>=20
>          the codec supports for both receiving and sending.
>=20
>=20
>=20
> OLD:
>=20
>       max-cpb: The value of max-cpb is an integer indicating the
maximum
>=20
>          coded picture buffer size in units of 1000 bits for the VCL
HRD
>=20
>          parameters (see A.3.1, item i of [1]) and in units of 1200
bits
>=20
>          for the NAL HRD parameters (see A.3.1, item j of [1]).
>=20
> NEW: (note that the change here is purely editorial)
>=20
>       max-cpb: The value of max-cpb is an integer indicating the
maximum
>=20
>          coded picture buffer size in units of 1000 bits for the VCL
HRD
>=20
>          parameters and in units of 1200 bits
>=20
>          for the NAL HRD parameters.
>=20
>=20
>=20
> OLD:
>=20
>       max-dpb: The value of max-dpb is an integer indicating the
maximum
>=20
>          decoded picture buffer size in units of 1024 bytes.  The max-
>=20
>          dpb parameter signals that the receiver has more memory than
>=20
>          the minimum amount of decoded picture buffer memory required
by
>=20
>          the signaled highest level conveyed in the value of the
>=20
>          profile-level-id parameter or the max-recv-level parameter.
>=20
>          When max-dpb is signaled, the receiver MUST be able to decode
>=20
>          NAL unit streams that conform to the signaled highest level,
>=20
>          with the exception that the MaxDPB value in Table A-1 of [1]
>=20
>          for the signaled highest level is replaced with the value of
>=20
>          max-dpb.  Consequently, a receiver that signals max-dpb MUST
be
>=20
>          capable of storing the following number of decoded frames,
>=20
>          complementary field pairs, and non-paired fields in its
decoded
>=20
>          picture buffer:
>=20
>=20
>=20
>             Min(1024 * max-dpb / ( PicWidthInMbs * FrameHeightInMbs *
>=20
>             256 * ChromaFormatFactor ), 16)
>=20
>=20
>=20
>          PicWidthInMbs, FrameHeightInMbs, and ChromaFormatFactor are
>=20
>          defined in [1].
>=20
>=20
>=20
>          The value of max-dpb MUST be greater than or equal to the
value
>=20
>          of MaxDPB given in Table A-1 of [1] for the highest level.
>=20
>          Senders MAY use this knowledge to construct coded video
streams
>=20
>          with improved compression.
>=20
> NEW: (When this change can be considered as editorial can be
discussed, but the nature of this change
> as follows. On the other hand, if not changed, then the semantics of
max-dpb is simply equivalent to
> unspecified, as MaxDPB and ChromaFormatFactor are not found in the
latest H.264 spec any more. Note
> that compared to RFC 3984, the bits on the wire do not change.)
>=20
>       max-dpb: The value of max-dpb is an integer indicating the
maximum
>=20
>          decoded picture buffer size in units of 8/3 macroblocks.  The
max-
>=20
>          dpb parameter signals that the receiver has more memory than
>=20
>          the minimum amount of decoded picture buffer memory required
by
>=20
>          the signaled highest level conveyed in the value of the
>=20
>          profile-level-id parameter or the max-recv-level parameter.
>=20
>          When max-dpb is signaled, the receiver MUST be able to decode
>=20
>          NAL unit streams that conform to the signaled highest level,
>=20
>          with the exception that the MaxDpbMbs value in Table A-1 of
[1]
>=20
>          for the signaled highest level is replaced with the value of
>=20
>          max-dpb * 3 / 8.  Consequently, a receiver that signals
max-dpb MUST be
>=20
>          capable of storing the following number of decoded frames,
>=20
>          complementary field pairs, and non-paired fields in its
decoded
>=20
>          picture buffer:
>=20
>=20
>=20
>             Min(max-dpb * 3 / 8 / ( PicWidthInMbs * FrameHeightInMbs),
16)
>=20
>=20
>=20
>          Wherein PicWidthInMbs and FrameHeightInMbs are defined in
[1].
>=20
>=20
>=20
>          The value of max-dpb MUST be greater than or equal to the
value
>=20
>          of MaxDpbMbs * 3 / 8, wherein the value of MaxDpbMbs is given
in
>=20
> Table A-1 of [1] for the highest level.
>=20
>          Senders MAY use this knowledge to construct coded video
streams
>=20
>          with improved compression.
>=20
>=20
>=20
> OLD:
>=20
>       max-br: The value of max-br is an integer indicating the maximum
>          video bitrate in units of 1000 bits per second for the VCL
HRD
>          parameters (see A.3.1, item i of [1]) and in units of 1200
bits
>          per second for the NAL HRD parameters (see A.3.1, item j of
>          [1]).
>          ...
>=20
>          For example, if a receiver signals capability for Level 1.2
>=20
>          with max-br equal to 1550, this indicates a maximum video
>=20
>          bitrate of 1550 kbits/sec for VCL HRD parameters, a maximum
>=20
>          video bitrate of 1860 kbits/sec for NAL HRD parameters, and a
>=20
>          CPB size of 4036458 bits (1550000 / 384000 * 1000 * 1000).
>=20
> NEW: (note that the change here is purely editorial)
>=20
>       max-br: The value of max-br is an integer indicating the maximum
>          video bitrate in units of 1000 bits per second for the VCL
HRD
>          parameters and in units of 1200 bits
>          per second for the NAL HRD parameters.
>          ...
>=20
>          For example, if a receiver signals capability for Main
profile Level 1.2
>=20
>          with max-br equal to 1550, this indicates a maximum video
>=20
>          bitrate of 1550 kbits/sec for VCL HRD parameters, a maximum
>=20
>          video bitrate of 1860 kbits/sec for NAL HRD parameters, and a
>=20
>          CPB size of 4036458 bits (1550000 / 384000 * 1000 * 1000).
>=20
>=20
>=20
> ------------------------------------End of suggested changes
--------------------------------------
>=20
>=20
>=20
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Ye-Kui Wang
> Sent: Sunday, March 20, 2011 4:21 AM
> To: payload@ietf.org; avt@ietf.org
> Subject: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload
drafts
>=20
>=20
>=20
> Folks,
>=20
>=20
>=20
> The three H.264/AVC related payload formats, namely,
draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-
> rtp-svc-27, and draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48
stage.
>=20
>=20
>=20
> The RFC-Editor has found the following problem: In
draft-ietf-avt-rtp-rfc3984bis-12, the definition of
> the max-dpb media parameter refers to the MaxDPB that was defined the
first version of the H.264/AVC
> spec, but not any more in the latest version (the 2010 version). The
parameter in the latest H.264/AVC
> version corresponding to MaxDPB is MaxDpbMbs, and the unit of the new
parameter (i.e., macroblocks) is
> different from the original one (i.e. 1024 bytes).
>=20
>=20
>=20
> The problem applies also to the SVC payload format, the RCDO payload
format, and H.241.
>=20
>=20
>=20
> A solution has been found and agreed, involving rfc3984bis authors and
some key people related to
> H.264/AVC (e.g., Gary Sullivan and Heiko Schwarz) and H.241 (e.g.,
Stephen Botzko and Patrick Luthi).
> Furthermore, we have found that there are also a couple of places that
need fixes due to similar
> changes from the initial version of H.264/AVC to the latest version.
>=20
>=20
>=20
> Per Roni's suggestion, I am sending in below the changes to
draft-ietf-avt-rtp-rfc3984bis-12 for
> review by the Payload and AVTcore WGs. It seems that exactly the same
changes are needed to draft-
> ietf-avt-rtp-h264-rcdo-08 (co-authors of this draft may confirm), and
similar but slightly different
> changes are needed to draft-ietf-avt-rtp-svc-27.
>=20
>=20
>=20
> Since the drafts are at the AUTH48 stage, please provide comments by
Monday, March 21, if any. Many
> thanks!
>=20
>=20
>=20
> BR, YK
>=20
>=20


From aallison@nab.org  Mon Mar 21 13:45:57 2011
Return-Path: <aallison@nab.org>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 13EAF3A688F; Mon, 21 Mar 2011 13:45:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mqBIz01PwD0A; Mon, 21 Mar 2011 13:45:49 -0700 (PDT)
Received: from p01c12o149.mxlogic.net (p01c12o149.mxlogic.net [208.65.145.72]) by core3.amsl.com (Postfix) with ESMTP id 7BE643A6889; Mon, 21 Mar 2011 13:45:48 -0700 (PDT)
Received: from unknown [208.97.234.91] (EHLO NABSREX027324.NAB.ORG) by p01c12o149.mxlogic.net(mxl_mta-6.9.0-2) with ESMTP id 859b78d4.0.063.00-370.98.p01c12o149.mxlogic.net (envelope-from <aallison@nab.org>);  Mon, 21 Mar 2011 14:47:21 -0600 (MDT)
X-MXL-Hash: 4d87b9592aac0919-20935f5bfeb238f839e64c397ccd13bcd67fd7de
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: Mon, 21 Mar 2011 16:47:20 -0400
Message-ID: <71C9EC0544D1F64D8B7D91EDCC62202006890479@NABSREX027324.NAB.ORG>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE39AD@xmb-sjc-234.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and RCDO payload drafts
Thread-Index: Acvm161AAF2A6AC0R/ODLEMZyh1IcgAwzyEAABVfHoAABchBIA==
References: <B99DECD58A94E143BA6F1508CC688351B445DE@dfweml504-mbx.china.huawei.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE39AD@xmb-sjc-234.amer.cisco.com>
From: "Allison, Art" <AAllison@nab.org>
To: <payload@ietf.org>, <avt@ietf.org>
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <aallison@nab.org>
X-SOURCE-IP: [208.97.234.91]
X-AnalysisOut: [v=1.0 c=1 a=DzHdTxL-66EA:10 a=BLceEmwcHowA:10 a=8nJEP1OIZ-]
X-AnalysisOut: [IA:10 a=tFGTPFZixTZ3yCXJchW01Q==:17 a=g0FpLpFZAAAA:8 a=48v]
X-AnalysisOut: [gC7mUAAAA:8 a=3DFX1qKQIBNiGt9bwzEA:9 a=crRPvF3YIfjp4rOSsNA]
X-AnalysisOut: [A:7 a=J0UfUdaXDh-KRANSfXOz36xHNnwA:4 a=wPNLvfGTeEIA:10 a=8]
X-AnalysisOut: [SgyfJxrfqYA:10 a=-9UqKSle32gA:10 a=Qd0007q6B0YA:10 a=lZB81]
X-AnalysisOut: [5dzVvQA:10 a=bnotN7MkczWK5nCo:21 a=ubWaTVfSfK86nHZf:21]
Subject: Re: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2011 20:45:57 -0000

It has been by experience that discovery of a significant technical =
issue that is 'patched' in a draft standard in a hurry to get it =
published is always risky and often results in an internal =
inconsistency.

Seems to me that is a few weeks delay for the formulating body to review =
is prudent - even if such change can be done.=20

Just reading for consistency, as I am no expert in the codec; I see the =
1000 and 1200 values expressed as pure multipliers and bits per second? =
Is that a coincidence, error or a magic number effect? And the High =
Profile factor of 1.25 (to these values) that is in the AVC standard =
seems to be relevant, but is not being discussed. Is that covered =
elsewhere in a clear fashion and independent?

I think this should be sent back for correction...and thanks go to the =
sharp eye who caught the discrepancy.

Art

Art Allison
Senior Director Advanced Engineering, Science and Technology
National Association of Broadcasters
1771 N Street NW
Washington, DC 20036
Phone=A0 202 429 5418=20
Fax=A0 202 775 4981
www.nab.org
Advocacy =A0Education=A0 Innovation


-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of =
Charles Eckel (eckelcu)
Sent: Monday, March 21, 2011 1:52 PM
To: Ye-Kui Wang; payload@ietf.org; avt@ietf.org
Subject: Re: [AVTCORE] [payload] Some changes to rfc3984bis, SVC,and =
RCDO payload drafts

Hi YK,

Thank you for providing this clear description of the proposed changes.
The changes look good to me.

Cheers,
Charles

> -----Original Message-----
> From: payload-bounces@ietf.org [mailto:payload-bounces@ietf.org] On
Behalf Of Ye-Kui Wang
> Sent: Monday, March 21, 2011 1:11 AM
> To: payload@ietf.org; avt@ietf.org
> Subject: Re: [payload] Some changes to rfc3984bis, SVC,and RCDO
payload drafts
>=20
> Further discussions with the same group of persons led to a decision
to stay with the unscaled units
> for max-br and max-cpb, thus fewer changes are needed to the three
payload formats listed in the title
> and H.241. With this, the changes needed are listed below (the
originally suggested changes are
> dropped from this email). This time I have highlighted the changes,
and I have also described the
> nature the changes below. Hope these may help understand better what
have been changed, and can lead
> to a quicker decision by the group, including WG chairs, and our AD.
>=20
>=20
>=20
> BR, YK
>=20
>=20
>=20
> ------------------------------------Start of suggested changes
--------------------------------------
>=20
>=20
>=20
> Section 8.1:
>=20
> OLD:
>=20
>       profile-level-id:
>          A base16 [7] (hexadecimal) representation of the following
>          three bytes in the sequence parameter set NAL unit is
specified
>          in [1]: 1) profile_idc, 2) a byte herein referred to as
>          profile-iop, composed of the values of constraint_set0_flag,
>          constraint_set1_flag,constraint_set2_flag,
>          constraint_set3_flag, and reserved_zero_4bits in bit-
>          significance order, starting from the most-significant bit,
and
>          3) level_idc.  Note that reserved_zero_4bits is required to
be
>          equal to 0 in [1], but other values for it may be specified
in
>          the future by ITU-T or ISO/IEC.
>=20
>  NEW: (note that the change here is purely editorial)
>=20
>       profile-level-id:
>=20
>          A base16 [7] (hexadecimal) representation of the following
>=20
>          three bytes in the sequence parameter set NAL unit is
specified
>=20
>          in [1]: 1) profile_idc, 2) a byte herein referred to as
>=20
>          profile-iop, composed of the values of constraint_set0_flag,
>=20
>          constraint_set1_flag,constraint_set2_flag,
>=20
>          constraint_set3_flag, constraint_set4_flag,
constraint_set5_flag,
>=20
>  and reserved_zero_2bits in bit-significance order, starting from the
most-significant bit, and
>=20
>          3) level_idc.  Note that reserved_zero_2bits is required to
be
>=20
>          equal to 0 in [1], but other values for it may be specified
in
>=20
>          the future by ITU-T or ISO/IEC.
>=20
>=20
>=20
> OLD:
>=20
>          For example, in the table above, profile_idc equal to 58
>          (Extended) with profile-iop equal to 11xx0000 indicates the
>          same sub-profile corresponding to profile_idc equal to 42
>          (Baseline) with profile-iop equal to x1xx0000.  Note that
other
>          combinations of profile_idc and profile-iop (not listed in
>          Table 5) may represent a sub-profile equivalent to the common
>          subset of coding tools for more than one profile.  Note also
>          that a decoder conforming to a certain profile may be able to
>          decode bitstreams conforming to other profiles.  For example,
a
>          decoder conforming to the High 4:4:4 profile, at a certain
>          level, must be able to decode bitstreams conforming to the
>          Constrained Baseline, Main, High, High 10, or High 4:2:2
>          profile at the same or a lower level.
>=20
>  NEW: (note that the change here is purely editorial)
>=20
>          For example, in the table above, profile_idc equal to 58
>=20
>          (Extended) with profile-iop equal to 11xx0000 indicates the
>=20
>          same sub-profile corresponding to profile_idc equal to 42
>=20
>          (Baseline) with profile-iop equal to x1xx0000.  Note that
other
>=20
>          combinations of profile_idc and profile-iop (not listed in
>=20
>          Table 5) may represent a sub-profile equivalent to the common
>=20
>          subset of coding tools for more than one profile.  Note also
>=20
>          that a decoder conforming to a certain profile may be able to
>=20
>          decode bitstreams conforming to other profiles.
>=20
>=20
>=20
> OLD:
>=20
>          If the profile-level-id parameter is used for capability
>          exchange or session setup procedure, it indicates the subset
of
>          coding tools, which is equal to the default sub-profile, that
>          the codec supports for both receiving and sending.
>=20
>  NEW: (note that the change here is purely editorial)
>=20
>          If the profile-level-id parameter is used for capability
>=20
>          exchange or session setup, it indicates the subset of
>=20
>          coding tools, which is equal to the default sub-profile, that
>=20
>          the codec supports for both receiving and sending.
>=20
>=20
>=20
> OLD:
>=20
>       max-cpb: The value of max-cpb is an integer indicating the
maximum
>=20
>          coded picture buffer size in units of 1000 bits for the VCL
HRD
>=20
>          parameters (see A.3.1, item i of [1]) and in units of 1200
bits
>=20
>          for the NAL HRD parameters (see A.3.1, item j of [1]).
>=20
> NEW: (note that the change here is purely editorial)
>=20
>       max-cpb: The value of max-cpb is an integer indicating the
maximum
>=20
>          coded picture buffer size in units of 1000 bits for the VCL
HRD
>=20
>          parameters and in units of 1200 bits
>=20
>          for the NAL HRD parameters.
>=20
>=20
>=20
> OLD:
>=20
>       max-dpb: The value of max-dpb is an integer indicating the
maximum
>=20
>          decoded picture buffer size in units of 1024 bytes.  The max-
>=20
>          dpb parameter signals that the receiver has more memory than
>=20
>          the minimum amount of decoded picture buffer memory required
by
>=20
>          the signaled highest level conveyed in the value of the
>=20
>          profile-level-id parameter or the max-recv-level parameter.
>=20
>          When max-dpb is signaled, the receiver MUST be able to decode
>=20
>          NAL unit streams that conform to the signaled highest level,
>=20
>          with the exception that the MaxDPB value in Table A-1 of [1]
>=20
>          for the signaled highest level is replaced with the value of
>=20
>          max-dpb.  Consequently, a receiver that signals max-dpb MUST
be
>=20
>          capable of storing the following number of decoded frames,
>=20
>          complementary field pairs, and non-paired fields in its
decoded
>=20
>          picture buffer:
>=20
>=20
>=20
>             Min(1024 * max-dpb / ( PicWidthInMbs * FrameHeightInMbs *
>=20
>             256 * ChromaFormatFactor ), 16)
>=20
>=20
>=20
>          PicWidthInMbs, FrameHeightInMbs, and ChromaFormatFactor are
>=20
>          defined in [1].
>=20
>=20
>=20
>          The value of max-dpb MUST be greater than or equal to the
value
>=20
>          of MaxDPB given in Table A-1 of [1] for the highest level.
>=20
>          Senders MAY use this knowledge to construct coded video
streams
>=20
>          with improved compression.
>=20
> NEW: (When this change can be considered as editorial can be
discussed, but the nature of this change
> as follows. On the other hand, if not changed, then the semantics of
max-dpb is simply equivalent to
> unspecified, as MaxDPB and ChromaFormatFactor are not found in the
latest H.264 spec any more. Note
> that compared to RFC 3984, the bits on the wire do not change.)
>=20
>       max-dpb: The value of max-dpb is an integer indicating the
maximum
>=20
>          decoded picture buffer size in units of 8/3 macroblocks.  The
max-
>=20
>          dpb parameter signals that the receiver has more memory than
>=20
>          the minimum amount of decoded picture buffer memory required
by
>=20
>          the signaled highest level conveyed in the value of the
>=20
>          profile-level-id parameter or the max-recv-level parameter.
>=20
>          When max-dpb is signaled, the receiver MUST be able to decode
>=20
>          NAL unit streams that conform to the signaled highest level,
>=20
>          with the exception that the MaxDpbMbs value in Table A-1 of
[1]
>=20
>          for the signaled highest level is replaced with the value of
>=20
>          max-dpb * 3 / 8.  Consequently, a receiver that signals
max-dpb MUST be
>=20
>          capable of storing the following number of decoded frames,
>=20
>          complementary field pairs, and non-paired fields in its
decoded
>=20
>          picture buffer:
>=20
>=20
>=20
>             Min(max-dpb * 3 / 8 / ( PicWidthInMbs * FrameHeightInMbs),
16)
>=20
>=20
>=20
>          Wherein PicWidthInMbs and FrameHeightInMbs are defined in
[1].
>=20
>=20
>=20
>          The value of max-dpb MUST be greater than or equal to the
value
>=20
>          of MaxDpbMbs * 3 / 8, wherein the value of MaxDpbMbs is given
in
>=20
> Table A-1 of [1] for the highest level.
>=20
>          Senders MAY use this knowledge to construct coded video
streams
>=20
>          with improved compression.
>=20
>=20
>=20
> OLD:
>=20
>       max-br: The value of max-br is an integer indicating the maximum
>          video bitrate in units of 1000 bits per second for the VCL
HRD
>          parameters (see A.3.1, item i of [1]) and in units of 1200
bits
>          per second for the NAL HRD parameters (see A.3.1, item j of
>          [1]).
>          ...
>=20
>          For example, if a receiver signals capability for Level 1.2
>=20
>          with max-br equal to 1550, this indicates a maximum video
>=20
>          bitrate of 1550 kbits/sec for VCL HRD parameters, a maximum
>=20
>          video bitrate of 1860 kbits/sec for NAL HRD parameters, and a
>=20
>          CPB size of 4036458 bits (1550000 / 384000 * 1000 * 1000).
>=20
> NEW: (note that the change here is purely editorial)
>=20
>       max-br: The value of max-br is an integer indicating the maximum
>          video bitrate in units of 1000 bits per second for the VCL
HRD
>          parameters and in units of 1200 bits
>          per second for the NAL HRD parameters.
>          ...
>=20
>          For example, if a receiver signals capability for Main
profile Level 1.2
>=20
>          with max-br equal to 1550, this indicates a maximum video
>=20
>          bitrate of 1550 kbits/sec for VCL HRD parameters, a maximum
>=20
>          video bitrate of 1860 kbits/sec for NAL HRD parameters, and a
>=20
>          CPB size of 4036458 bits (1550000 / 384000 * 1000 * 1000).
>=20
>=20
>=20
> ------------------------------------End of suggested changes
--------------------------------------
>=20
>=20
>=20
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Ye-Kui Wang
> Sent: Sunday, March 20, 2011 4:21 AM
> To: payload@ietf.org; avt@ietf.org
> Subject: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload
drafts
>=20
>=20
>=20
> Folks,
>=20
>=20
>=20
> The three H.264/AVC related payload formats, namely,
draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-
> rtp-svc-27, and draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48
stage.
>=20
>=20
>=20
> The RFC-Editor has found the following problem: In
draft-ietf-avt-rtp-rfc3984bis-12, the definition of
> the max-dpb media parameter refers to the MaxDPB that was defined the
first version of the H.264/AVC
> spec, but not any more in the latest version (the 2010 version). The
parameter in the latest H.264/AVC
> version corresponding to MaxDPB is MaxDpbMbs, and the unit of the new
parameter (i.e., macroblocks) is
> different from the original one (i.e. 1024 bytes).
>=20
>=20
>=20
> The problem applies also to the SVC payload format, the RCDO payload
format, and H.241.
>=20
>=20
>=20
> A solution has been found and agreed, involving rfc3984bis authors and
some key people related to
> H.264/AVC (e.g., Gary Sullivan and Heiko Schwarz) and H.241 (e.g.,
Stephen Botzko and Patrick Luthi).
> Furthermore, we have found that there are also a couple of places that
need fixes due to similar
> changes from the initial version of H.264/AVC to the latest version.
>=20
>=20
>=20
> Per Roni's suggestion, I am sending in below the changes to
draft-ietf-avt-rtp-rfc3984bis-12 for
> review by the Payload and AVTcore WGs. It seems that exactly the same
changes are needed to draft-
> ietf-avt-rtp-h264-rcdo-08 (co-authors of this draft may confirm), and
similar but slightly different
> changes are needed to draft-ietf-avt-rtp-svc-27.
>=20
>=20
>=20
> Since the drafts are at the AUTH48 stage, please provide comments by
Monday, March 21, if any. Many
> thanks!
>=20
>=20
>=20
> BR, YK
>=20
>=20

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

From Even.roni@huawei.com  Mon Mar 21 14:58:05 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9AC9728C1A3; Mon, 21 Mar 2011 14:58:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.863
X-Spam-Level: 
X-Spam-Status: No, score=-99.863 tagged_above=-999 required=5 tests=[AWL=-0.632, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, HTML_TAG_BALANCE_BODY=1.263, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dV+1R3C2FoFn; Mon, 21 Mar 2011 14:57:58 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 7CDE33A68E4; Mon, 21 Mar 2011 14:57:58 -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 <0LIF00FV4H2WSK@szxga05-in.huawei.com>; Tue, 22 Mar 2011 05:59:21 +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 <0LIF00MEQH2WNG@szxga05-in.huawei.com>; Tue, 22 Mar 2011 05:59:20 +0800 (CST)
Received: from windows8d787f9 (cust.static.109-164-246-172.swisscomdata.ch [109.164.246.172]) by szxml11-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LIF00EQ7H2RF7@szxml11-in.huawei.com>; Tue, 22 Mar 2011 05:59:20 +0800 (CST)
Date: Mon, 21 Mar 2011 23:58:58 +0200
From: Roni Even <Even.roni@huawei.com>
To: avt@ietf.org
Message-id: <000001cbe813$31ed2980$95c77c80$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/mixed; boundary="Boundary_(ID_GiuN6RPIJ8UjGZWShI216A)"
Content-language: en-us
Thread-index: Acvn3nQPbW3aKf6aSP68ZQys8bVHXw==
Cc: payload@ietf.org, xrblock@ietf.org
Subject: [AVTCORE] Latest agenda for AVTcore at IETF80
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2011 21:58:05 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_GiuN6RPIJ8UjGZWShI216A)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_l+c8aYCd9eVq+QUJDX0f2w)"


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

Hi,

Attached is the agenda for the AVTcore session. Hopefully the final one

See you in Prague 

Roni Even


--Boundary_(ID_l+c8aYCd9eVq+QUJDX0f2w)
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>Attached is the agenda for the AVTcore session. Hopefully the final one<o:p></o:p></p><p class=MsoNormal>See you in Prague <o:p></o:p></p><p class=MsoNormal>Roni Even<o:p></o:p></p></div></body></html>

--Boundary_(ID_l+c8aYCd9eVq+QUJDX0f2w)--

--Boundary_(ID_GiuN6RPIJ8UjGZWShI216A)
Content-type: text/html; name=a1103.html
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=a1103.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, 28 March 2011 at 13:00-15:00 (Congress Hall I)</h2>
<p>
<table border="0" cellpadding="5">
<tr>
<th align="left">13:00
<th align="left">AVTCore Introduction and Status Update<th align="left">Chairs
<tr>
<th align="left">13:15
<th align="left">Payload Introduction and Status Update<th align="left">Payload Chairs
<tr>
<th align="left">13:30
<th align="left">XRBlock Introduction and Status Update<th align="left">XRblock Chairs
<tr>
<th align="left">13:45
<th align="left">Explicit Congestion Notification for RTP over UDP<th align="left">Perkins
<tr>
<td align="left">
<td align="left"><a href="http://tools.ietf.org/id/draft-ietf-avtcore-ecn-for-rtp-01">draft-ietf-avtcore-ecn-for-rtp-01</a>
<tr>
<th align="left">13:55
<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-00">draft-ietf-avtcore-feedback-supression-rtp-00</a>
<tr>
<th align="left">14:05
<th align="left">RTCP Feedbak Suppression and Retransmission<th align="left">Tom VanCaenegem
<tr>
<td align="left">
<td align="left"><a href="http://tools.ietf.org/id/draft-vancaenegem-avtcore-fb-supp-and-retransm-00">draft-vancaenegem-avtcore-fb-supp-and-retransm-00</a>
<tr>
<th align="left">14:10
<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-brandenburg-avtcore-rtcp-for-idms-00">draft-brandenburg-avtcore-rtcp-for-idms-00</a>
<tr>
<th align="left">14:25
<th align="left">Monitoring Architectures for RTP<th align="left">Qin Wu
<tr>
<td align="left">
<td align="left"><a href="http://tools.ietf.org/id/draft-hunt-avtcore-monarch-01">draft-hunt-avtcore-monarch-01</a>
<tr>
<th align="left">14:40
<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-avtcore-mprtp-01">draft-singh-avtcore-mprtp-01</a>
<tr>
<th align="left">14:50
<th align="left">End</table>

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

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

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

AGENDA

Monday, 28 March 2011 at 13:00-15:00 (Congress Hall I)
------------------------------------------------------
13:00   AVTCore Introduction and Status Update              (Chairs, 15)

13:15   Payload Introduction and Status Update      (Payload Chairs, 15)

13:30   XRBlock Introduction and Status Update      (XRblock Chairs, 15)

13:45   Explicit Congestion Notification for RTP over UDP  (Perkins, 10)
        draft-ietf-avtcore-ecn-for-rtp-01

13:55   RTCP Extension for Feedback Suppression Indication  (Qin Wu, 10)
        draft-ietf-avtcore-feedback-supression-rtp-00

14:05   RTCP Feedbak Suppression and Retransmission (Tom VanCaenegem, 5)
        draft-vancaenegem-avtcore-fb-supp-and-retransm-00

14:10   RTCP for inter-destination media synchronization(Ray van Brandenburg , 15)
        draft-brandenburg-avtcore-rtcp-for-idms-00

14:25   Monitoring Architectures for RTP                    (Qin Wu, 15)
        draft-hunt-avtcore-monarch-01

14:40   Multipath RTP                                  (Varun Singh, 10)
        draft-singh-avtcore-mprtp-01

14:50   End

--Boundary_(ID_GiuN6RPIJ8UjGZWShI216A)--

From wwwrun@rfc-editor.org  Mon Mar 21 22:23:05 2011
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F9833A65A5; Mon, 21 Mar 2011 22:23:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.117
X-Spam-Level: 
X-Spam-Status: No, score=-102.117 tagged_above=-999 required=5 tests=[AWL=-0.117, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oTEc3eLdynb4; Mon, 21 Mar 2011 22:23:04 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 74B6D3A672F; Mon, 21 Mar 2011 22:22:48 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C11EFE0767; Mon, 21 Mar 2011 22:24:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110322052421.C11EFE0767@rfc-editor.org>
Date: Mon, 21 Mar 2011 22:24:21 -0700 (PDT)
Cc: avt@ietf.org, rfc-editor@rfc-editor.org
Subject: [AVTCORE] RFC 6188 on The Use of AES-192 and AES-256 in Secure RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Mar 2011 05:23:05 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6188

        Title:      The Use of AES-192 and 
                    AES-256 in Secure RTP 
        Author:     D. McGrew
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2011
        Mailbox:    mcgrew@cisco.com
        Pages:      16
        Characters: 35973
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avt-srtp-big-aes-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6188.txt

This memo describes the use of the Advanced Encryption Standard (AES)
with 192- and 256-bit keys within the Secure RTP (SRTP) protocol.  It
details counter mode encryption for SRTP and Secure Realtime
Transport Control Protocol (SRTCP) and a new SRTP Key Derivation
Function (KDF) for AES-192 and AES-256.  [STANDARDS-TRACK]

This document is a product of the Audio/Video Transport Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From yekui.wang@huawei.com  Wed Mar 23 01:52:48 2011
Return-Path: <yekui.wang@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B7CD53A67A8; Wed, 23 Mar 2011 01:52:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rE032Xa5PXto; Wed, 23 Mar 2011 01:52:46 -0700 (PDT)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id A1E223A679C; Wed, 23 Mar 2011 01:52:46 -0700 (PDT)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LII0095W62J0Q@usaga02-in.huawei.com>; Wed, 23 Mar 2011 01:54:20 -0700 (PDT)
Received: from dfweml201-edg.china.huawei.com ([172.18.9.107]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPS id <0LII00DGE62JQL@usaga02-in.huawei.com>; Wed, 23 Mar 2011 01:54:19 -0700 (PDT)
Received: from DFWEML402-HUB.china.huawei.com (10.193.5.102) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.270.1; Wed, 23 Mar 2011 01:54:18 -0700
Received: from DFWEML503-MBX.china.huawei.com ([169.254.3.47]) by DFWEML402-HUB.china.huawei.com ([::1]) with mapi id 14.01.0270.001; Wed, 23 Mar 2011 01:54:18 -0700
Date: Wed, 23 Mar 2011 08:54:17 +0000
From: Ye-Kui Wang <yekui.wang@huawei.com>
In-reply-to: <71C9EC0544D1F64D8B7D91EDCC62202006890479@NABSREX027324.NAB.ORG>
X-Originating-IP: [10.47.86.192]
To: "Allison, Art" <AAllison@nab.org>, "payload@ietf.org" <payload@ietf.org>,  "avt@ietf.org" <avt@ietf.org>
Message-id: <B99DECD58A94E143BA6F1508CC688351051CAE50@dfweml503-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US
Thread-topic: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and RCDO payload drafts
Thread-index: AQHL6TfkNG8bu5QUBkWtpBAtPXzvbg==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <B99DECD58A94E143BA6F1508CC688351B445DE@dfweml504-mbx.china.huawei.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE39AD@xmb-sjc-234.amer.cisco.com> <71C9EC0544D1F64D8B7D91EDCC62202006890479@NABSREX027324.NAB.ORG>
Subject: Re: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Mar 2011 08:52:48 -0000

The units of the values of 1000 and 1200 are clearly specified. Where is no=
t clear, could you clarify?=20

What is "that" in "Is that a coincidence, error or a magic number effect?"?

If you read carefully the previous two emails on this subject I sent out, y=
ou would have noticed that the factor you mentioned, which is not only for =
High profile, but for many other profiles, and the factor can be different =
for different profiles, has been addressed. Please let us know if you found=
 any place that is not well addressed.

Finally, what is "this" in "I think this should be sent back for correction=
..."? I guess you meant for the entire draft. But if you don't point out th=
e place that needs to be corrected, what we can do?

BR, YK

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Allis=
on, Art
Sent: Monday, March 21, 2011 4:47 PM
To: payload@ietf.org; avt@ietf.org
Subject: Re: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and RCDO =
payload drafts

It has been by experience that discovery of a significant technical issue t=
hat is 'patched' in a draft standard in a hurry to get it published is alwa=
ys risky and often results in an internal inconsistency.

Seems to me that is a few weeks delay for the formulating body to review is=
 prudent - even if such change can be done.=20

Just reading for consistency, as I am no expert in the codec; I see the 100=
0 and 1200 values expressed as pure multipliers and bits per second? Is tha=
t a coincidence, error or a magic number effect? And the High Profile facto=
r of 1.25 (to these values) that is in the AVC standard seems to be relevan=
t, but is not being discussed. Is that covered elsewhere in a clear fashion=
 and independent?

I think this should be sent back for correction...and thanks go to the shar=
p eye who caught the discrepancy.

Art

Art Allison
Senior Director Advanced Engineering, Science and Technology
National Association of Broadcasters
1771 N Street NW
Washington, DC 20036
Phone=A0 202 429 5418=20
Fax=A0 202 775 4981
www.nab.org
Advocacy =A0Education=A0 Innovation


-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Charl=
es Eckel (eckelcu)
Sent: Monday, March 21, 2011 1:52 PM
To: Ye-Kui Wang; payload@ietf.org; avt@ietf.org
Subject: Re: [AVTCORE] [payload] Some changes to rfc3984bis, SVC,and RCDO p=
ayload drafts

Hi YK,

Thank you for providing this clear description of the proposed changes.
The changes look good to me.

Cheers,
Charles

> -----Original Message-----
> From: payload-bounces@ietf.org [mailto:payload-bounces@ietf.org] On
Behalf Of Ye-Kui Wang
> Sent: Monday, March 21, 2011 1:11 AM
> To: payload@ietf.org; avt@ietf.org
> Subject: Re: [payload] Some changes to rfc3984bis, SVC,and RCDO
payload drafts
>=20
> Further discussions with the same group of persons led to a decision
to stay with the unscaled units
> for max-br and max-cpb, thus fewer changes are needed to the three
payload formats listed in the title
> and H.241. With this, the changes needed are listed below (the
originally suggested changes are
> dropped from this email). This time I have highlighted the changes,
and I have also described the
> nature the changes below. Hope these may help understand better what
have been changed, and can lead
> to a quicker decision by the group, including WG chairs, and our AD.
>=20
>=20
>=20
> BR, YK
>=20
>=20
>=20
> ------------------------------------Start of suggested changes
--------------------------------------
>=20
>=20
>=20
> Section 8.1:
>=20
> OLD:
>=20
>       profile-level-id:
>          A base16 [7] (hexadecimal) representation of the following
>          three bytes in the sequence parameter set NAL unit is
specified
>          in [1]: 1) profile_idc, 2) a byte herein referred to as
>          profile-iop, composed of the values of constraint_set0_flag,
>          constraint_set1_flag,constraint_set2_flag,
>          constraint_set3_flag, and reserved_zero_4bits in bit-
>          significance order, starting from the most-significant bit,
and
>          3) level_idc.  Note that reserved_zero_4bits is required to
be
>          equal to 0 in [1], but other values for it may be specified
in
>          the future by ITU-T or ISO/IEC.
>=20
>  NEW: (note that the change here is purely editorial)
>=20
>       profile-level-id:
>=20
>          A base16 [7] (hexadecimal) representation of the following
>=20
>          three bytes in the sequence parameter set NAL unit is
specified
>=20
>          in [1]: 1) profile_idc, 2) a byte herein referred to as
>=20
>          profile-iop, composed of the values of constraint_set0_flag,
>=20
>          constraint_set1_flag,constraint_set2_flag,
>=20
>          constraint_set3_flag, constraint_set4_flag,
constraint_set5_flag,
>=20
>  and reserved_zero_2bits in bit-significance order, starting from the
most-significant bit, and
>=20
>          3) level_idc.  Note that reserved_zero_2bits is required to
be
>=20
>          equal to 0 in [1], but other values for it may be specified
in
>=20
>          the future by ITU-T or ISO/IEC.
>=20
>=20
>=20
> OLD:
>=20
>          For example, in the table above, profile_idc equal to 58
>          (Extended) with profile-iop equal to 11xx0000 indicates the
>          same sub-profile corresponding to profile_idc equal to 42
>          (Baseline) with profile-iop equal to x1xx0000.  Note that
other
>          combinations of profile_idc and profile-iop (not listed in
>          Table 5) may represent a sub-profile equivalent to the common
>          subset of coding tools for more than one profile.  Note also
>          that a decoder conforming to a certain profile may be able to
>          decode bitstreams conforming to other profiles.  For example,
a
>          decoder conforming to the High 4:4:4 profile, at a certain
>          level, must be able to decode bitstreams conforming to the
>          Constrained Baseline, Main, High, High 10, or High 4:2:2
>          profile at the same or a lower level.
>=20
>  NEW: (note that the change here is purely editorial)
>=20
>          For example, in the table above, profile_idc equal to 58
>=20
>          (Extended) with profile-iop equal to 11xx0000 indicates the
>=20
>          same sub-profile corresponding to profile_idc equal to 42
>=20
>          (Baseline) with profile-iop equal to x1xx0000.  Note that
other
>=20
>          combinations of profile_idc and profile-iop (not listed in
>=20
>          Table 5) may represent a sub-profile equivalent to the common
>=20
>          subset of coding tools for more than one profile.  Note also
>=20
>          that a decoder conforming to a certain profile may be able to
>=20
>          decode bitstreams conforming to other profiles.
>=20
>=20
>=20
> OLD:
>=20
>          If the profile-level-id parameter is used for capability
>          exchange or session setup procedure, it indicates the subset
of
>          coding tools, which is equal to the default sub-profile, that
>          the codec supports for both receiving and sending.
>=20
>  NEW: (note that the change here is purely editorial)
>=20
>          If the profile-level-id parameter is used for capability
>=20
>          exchange or session setup, it indicates the subset of
>=20
>          coding tools, which is equal to the default sub-profile, that
>=20
>          the codec supports for both receiving and sending.
>=20
>=20
>=20
> OLD:
>=20
>       max-cpb: The value of max-cpb is an integer indicating the
maximum
>=20
>          coded picture buffer size in units of 1000 bits for the VCL
HRD
>=20
>          parameters (see A.3.1, item i of [1]) and in units of 1200
bits
>=20
>          for the NAL HRD parameters (see A.3.1, item j of [1]).
>=20
> NEW: (note that the change here is purely editorial)
>=20
>       max-cpb: The value of max-cpb is an integer indicating the
maximum
>=20
>          coded picture buffer size in units of 1000 bits for the VCL
HRD
>=20
>          parameters and in units of 1200 bits
>=20
>          for the NAL HRD parameters.
>=20
>=20
>=20
> OLD:
>=20
>       max-dpb: The value of max-dpb is an integer indicating the
maximum
>=20
>          decoded picture buffer size in units of 1024 bytes.  The max-
>=20
>          dpb parameter signals that the receiver has more memory than
>=20
>          the minimum amount of decoded picture buffer memory required
by
>=20
>          the signaled highest level conveyed in the value of the
>=20
>          profile-level-id parameter or the max-recv-level parameter.
>=20
>          When max-dpb is signaled, the receiver MUST be able to decode
>=20
>          NAL unit streams that conform to the signaled highest level,
>=20
>          with the exception that the MaxDPB value in Table A-1 of [1]
>=20
>          for the signaled highest level is replaced with the value of
>=20
>          max-dpb.  Consequently, a receiver that signals max-dpb MUST
be
>=20
>          capable of storing the following number of decoded frames,
>=20
>          complementary field pairs, and non-paired fields in its
decoded
>=20
>          picture buffer:
>=20
>=20
>=20
>             Min(1024 * max-dpb / ( PicWidthInMbs * FrameHeightInMbs *
>=20
>             256 * ChromaFormatFactor ), 16)
>=20
>=20
>=20
>          PicWidthInMbs, FrameHeightInMbs, and ChromaFormatFactor are
>=20
>          defined in [1].
>=20
>=20
>=20
>          The value of max-dpb MUST be greater than or equal to the
value
>=20
>          of MaxDPB given in Table A-1 of [1] for the highest level.
>=20
>          Senders MAY use this knowledge to construct coded video
streams
>=20
>          with improved compression.
>=20
> NEW: (When this change can be considered as editorial can be
discussed, but the nature of this change
> as follows. On the other hand, if not changed, then the semantics of
max-dpb is simply equivalent to
> unspecified, as MaxDPB and ChromaFormatFactor are not found in the
latest H.264 spec any more. Note
> that compared to RFC 3984, the bits on the wire do not change.)
>=20
>       max-dpb: The value of max-dpb is an integer indicating the
maximum
>=20
>          decoded picture buffer size in units of 8/3 macroblocks.  The
max-
>=20
>          dpb parameter signals that the receiver has more memory than
>=20
>          the minimum amount of decoded picture buffer memory required
by
>=20
>          the signaled highest level conveyed in the value of the
>=20
>          profile-level-id parameter or the max-recv-level parameter.
>=20
>          When max-dpb is signaled, the receiver MUST be able to decode
>=20
>          NAL unit streams that conform to the signaled highest level,
>=20
>          with the exception that the MaxDpbMbs value in Table A-1 of
[1]
>=20
>          for the signaled highest level is replaced with the value of
>=20
>          max-dpb * 3 / 8.  Consequently, a receiver that signals
max-dpb MUST be
>=20
>          capable of storing the following number of decoded frames,
>=20
>          complementary field pairs, and non-paired fields in its
decoded
>=20
>          picture buffer:
>=20
>=20
>=20
>             Min(max-dpb * 3 / 8 / ( PicWidthInMbs * FrameHeightInMbs),
16)
>=20
>=20
>=20
>          Wherein PicWidthInMbs and FrameHeightInMbs are defined in
[1].
>=20
>=20
>=20
>          The value of max-dpb MUST be greater than or equal to the
value
>=20
>          of MaxDpbMbs * 3 / 8, wherein the value of MaxDpbMbs is given
in
>=20
> Table A-1 of [1] for the highest level.
>=20
>          Senders MAY use this knowledge to construct coded video
streams
>=20
>          with improved compression.
>=20
>=20
>=20
> OLD:
>=20
>       max-br: The value of max-br is an integer indicating the maximum
>          video bitrate in units of 1000 bits per second for the VCL
HRD
>          parameters (see A.3.1, item i of [1]) and in units of 1200
bits
>          per second for the NAL HRD parameters (see A.3.1, item j of
>          [1]).
>          ...
>=20
>          For example, if a receiver signals capability for Level 1.2
>=20
>          with max-br equal to 1550, this indicates a maximum video
>=20
>          bitrate of 1550 kbits/sec for VCL HRD parameters, a maximum
>=20
>          video bitrate of 1860 kbits/sec for NAL HRD parameters, and a
>=20
>          CPB size of 4036458 bits (1550000 / 384000 * 1000 * 1000).
>=20
> NEW: (note that the change here is purely editorial)
>=20
>       max-br: The value of max-br is an integer indicating the maximum
>          video bitrate in units of 1000 bits per second for the VCL
HRD
>          parameters and in units of 1200 bits
>          per second for the NAL HRD parameters.
>          ...
>=20
>          For example, if a receiver signals capability for Main
profile Level 1.2
>=20
>          with max-br equal to 1550, this indicates a maximum video
>=20
>          bitrate of 1550 kbits/sec for VCL HRD parameters, a maximum
>=20
>          video bitrate of 1860 kbits/sec for NAL HRD parameters, and a
>=20
>          CPB size of 4036458 bits (1550000 / 384000 * 1000 * 1000).
>=20
>=20
>=20
> ------------------------------------End of suggested changes
--------------------------------------
>=20
>=20
>=20
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Ye-Kui Wang
> Sent: Sunday, March 20, 2011 4:21 AM
> To: payload@ietf.org; avt@ietf.org
> Subject: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload
drafts
>=20
>=20
>=20
> Folks,
>=20
>=20
>=20
> The three H.264/AVC related payload formats, namely,
draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-
> rtp-svc-27, and draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48
stage.
>=20
>=20
>=20
> The RFC-Editor has found the following problem: In
draft-ietf-avt-rtp-rfc3984bis-12, the definition of
> the max-dpb media parameter refers to the MaxDPB that was defined the
first version of the H.264/AVC
> spec, but not any more in the latest version (the 2010 version). The
parameter in the latest H.264/AVC
> version corresponding to MaxDPB is MaxDpbMbs, and the unit of the new
parameter (i.e., macroblocks) is
> different from the original one (i.e. 1024 bytes).
>=20
>=20
>=20
> The problem applies also to the SVC payload format, the RCDO payload
format, and H.241.
>=20
>=20
>=20
> A solution has been found and agreed, involving rfc3984bis authors and
some key people related to
> H.264/AVC (e.g., Gary Sullivan and Heiko Schwarz) and H.241 (e.g.,
Stephen Botzko and Patrick Luthi).
> Furthermore, we have found that there are also a couple of places that
need fixes due to similar
> changes from the initial version of H.264/AVC to the latest version.
>=20
>=20
>=20
> Per Roni's suggestion, I am sending in below the changes to
draft-ietf-avt-rtp-rfc3984bis-12 for
> review by the Payload and AVTcore WGs. It seems that exactly the same
changes are needed to draft-
> ietf-avt-rtp-h264-rcdo-08 (co-authors of this draft may confirm), and
similar but slightly different
> changes are needed to draft-ietf-avt-rtp-svc-27.
>=20
>=20
>=20
> Since the drafts are at the AUTH48 stage, please provide comments by
Monday, March 21, if any. Many
> thanks!
>=20
>=20
>=20
> BR, YK
>=20
>=20

_______________________________________________
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 aallison@nab.org  Wed Mar 23 07:35:59 2011
Return-Path: <aallison@nab.org>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 690C33A691F; Wed, 23 Mar 2011 07:35:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qzs8Id-pEHFx; Wed, 23 Mar 2011 07:35:56 -0700 (PDT)
Received: from p01c11o144.mxlogic.net (p01c11o144.mxlogic.net [208.65.144.67]) by core3.amsl.com (Postfix) with ESMTP id CF7F43A6919; Wed, 23 Mar 2011 07:35:55 -0700 (PDT)
Received: from unknown [208.97.234.91] (EHLO NABSREX027324.NAB.ORG) by p01c11o144.mxlogic.net(mxl_mta-6.9.0-2) with ESMTP id 9a50a8d4.0.4901.00-359.11364.p01c11o144.mxlogic.net (envelope-from <aallison@nab.org>);  Wed, 23 Mar 2011 08:37:30 -0600 (MDT)
X-MXL-Hash: 4d8a05aa7aa51c8b-773f1af9b788741c36c04e14422ae7a08c8a1333
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: Wed, 23 Mar 2011 10:37:26 -0400
Message-ID: <71C9EC0544D1F64D8B7D91EDCC62202006890498@NABSREX027324.NAB.ORG>
In-Reply-To: <B99DECD58A94E143BA6F1508CC688351051CAE50@dfweml503-mbx.china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and RCDO payload drafts
Thread-Index: AQHL6TfkNG8bu5QUBkWtpBAtPXzvbpQ6866Q
References: <B99DECD58A94E143BA6F1508CC688351B445DE@dfweml504-mbx.china.huawei.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE39AD@xmb-sjc-234.amer.cisco.com> <71C9EC0544D1F64D8B7D91EDCC62202006890479@NABSREX027324.NAB.ORG> <B99DECD58A94E143BA6F1508CC688351051CAE50@dfweml503-mbx.china.huawei.com>
From: "Allison, Art" <AAllison@nab.org>
To: "Ye-Kui Wang" <yekui.wang@huawei.com>, <payload@ietf.org>, <avt@ietf.org>
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <aallison@nab.org>
X-SOURCE-IP: [208.97.234.91]
X-AnalysisOut: [v=1.0 c=1 a=DzHdTxL-66EA:10 a=BLceEmwcHowA:10 a=8nJEP1OIZ-]
X-AnalysisOut: [IA:10 a=tFGTPFZixTZ3yCXJchW01Q==:17 a=g0FpLpFZAAAA:8 a=i0E]
X-AnalysisOut: [eH86SAAAA:8 a=48vgC7mUAAAA:8 a=KFtVM71Ojwk9vxD59x0A:9 a=4s]
X-AnalysisOut: [WVP4qkbm72IdYnaWEA:7 a=h_9P7y10rm6nB48iuRaEXH9nOWgA:4 a=wP]
X-AnalysisOut: [NLvfGTeEIA:10 a=8SgyfJxrfqYA:10 a=-9UqKSle32gA:10 a=Qd0007]
X-AnalysisOut: [q6B0YA:10 a=hPjdaMEvmhQA:10 a=lZB815dzVvQA:10 a=XbQgGpvnme]
X-AnalysisOut: [2S4Gwb:21 a=VOCzThdEtGMs-80J:21]
Subject: Re: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Mar 2011 14:35:59 -0000

I admit significant ignorance of the technical details. =20

My main point, based on decades of standards development experience, was =
that last minute changes such as these often result in failure to fix =
the issue precisely and that the due process group should be given time =
to assure the correct fix has been made.  Rushing can work, but often =
has a bad outcome.=20

As to specifics; I saw that the values of 1000 and 1200 as the correct =
unit sizes for NAL stream overhead (in some cases).  In one place these =
are asserted to be bits (no rate units) as a multiplier and in another =
place these are described as bits-per-second. These are clearly =
different usages. Perhaps both usages are correct - I do not know - but =
it appeared to be inconsistent.  (And this type of inconsistency is =
exactly the kind of thing that I have seen happen when last minute =
patches are made to a standard.)

By magic number, I meant was it correct that these values have two =
different uses, perhaps due to their fundamental nature.

I do not assert anything is wrong, I suggest that unless there is a =
vital need to push this out fast, that the draft be referred back to the =
drafting group. Maybe all those folks have had time to carefully =
consider and respond before the deadline...and this is specious.

I believe that you <process managers> can make better decisions when =
more information is provided. I commented to so assist.
=20

Art Allison
Senior Director Advanced Engineering, Science and Technology
National Association of Broadcasters
1771 N Street NW
Washington, DC 20036
Phone=A0 202 429 5418=20
Fax=A0 202 775 4981
www.nab.org
Advocacy =A0Education=A0 Innovation


-----Original Message-----
From: Ye-Kui Wang [mailto:yekui.wang@huawei.com]=20
Sent: Wednesday, March 23, 2011 4:54 AM
To: Allison, Art; payload@ietf.org; avt@ietf.org
Subject: RE: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and =
RCDO payload drafts

The units of the values of 1000 and 1200 are clearly specified. Where is =
not clear, could you clarify?=20

What is "that" in "Is that a coincidence, error or a magic number =
effect?"?

If you read carefully the previous two emails on this subject I sent =
out, you would have noticed that the factor you mentioned, which is not =
only for High profile, but for many other profiles, and the factor can =
be different for different profiles, has been addressed. Please let us =
know if you found any place that is not well addressed.

Finally, what is "this" in "I think this should be sent back for =
correction..."? I guess you meant for the entire draft. But if you don't =
point out the place that needs to be corrected, what we can do?

BR, YK

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of =
Allison, Art
Sent: Monday, March 21, 2011 4:47 PM
To: payload@ietf.org; avt@ietf.org
Subject: Re: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and =
RCDO payload drafts

It has been by experience that discovery of a significant technical =
issue that is 'patched' in a draft standard in a hurry to get it =
published is always risky and often results in an internal =
inconsistency.

Seems to me that is a few weeks delay for the formulating body to review =
is prudent - even if such change can be done.=20

Just reading for consistency, as I am no expert in the codec; I see the =
1000 and 1200 values expressed as pure multipliers and bits per second? =
Is that a coincidence, error or a magic number effect? And the High =
Profile factor of 1.25 (to these values) that is in the AVC standard =
seems to be relevant, but is not being discussed. Is that covered =
elsewhere in a clear fashion and independent?

I think this should be sent back for correction...and thanks go to the =
sharp eye who caught the discrepancy.

Art

Art Allison
Senior Director Advanced Engineering, Science and Technology
National Association of Broadcasters
1771 N Street NW
Washington, DC 20036
Phone=A0 202 429 5418=20
Fax=A0 202 775 4981
www.nab.org
Advocacy =A0Education=A0 Innovation


-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of =
Charles Eckel (eckelcu)
Sent: Monday, March 21, 2011 1:52 PM
To: Ye-Kui Wang; payload@ietf.org; avt@ietf.org
Subject: Re: [AVTCORE] [payload] Some changes to rfc3984bis, SVC,and =
RCDO payload drafts

Hi YK,

Thank you for providing this clear description of the proposed changes.
The changes look good to me.

Cheers,
Charles

> -----Original Message-----
> From: payload-bounces@ietf.org [mailto:payload-bounces@ietf.org] On
Behalf Of Ye-Kui Wang
> Sent: Monday, March 21, 2011 1:11 AM
> To: payload@ietf.org; avt@ietf.org
> Subject: Re: [payload] Some changes to rfc3984bis, SVC,and RCDO
payload drafts
>=20
> Further discussions with the same group of persons led to a decision
to stay with the unscaled units
> for max-br and max-cpb, thus fewer changes are needed to the three
payload formats listed in the title
> and H.241. With this, the changes needed are listed below (the
originally suggested changes are
> dropped from this email). This time I have highlighted the changes,
and I have also described the
> nature the changes below. Hope these may help understand better what
have been changed, and can lead
> to a quicker decision by the group, including WG chairs, and our AD.
>=20
>=20
>=20
> BR, YK
>=20
>=20
>=20
> ------------------------------------Start of suggested changes
--------------------------------------
>=20
>=20
>=20
> Section 8.1:
>=20
> OLD:
>=20
>       profile-level-id:
>          A base16 [7] (hexadecimal) representation of the following
>          three bytes in the sequence parameter set NAL unit is
specified
>          in [1]: 1) profile_idc, 2) a byte herein referred to as
>          profile-iop, composed of the values of constraint_set0_flag,
>          constraint_set1_flag,constraint_set2_flag,
>          constraint_set3_flag, and reserved_zero_4bits in bit-
>          significance order, starting from the most-significant bit,
and
>          3) level_idc.  Note that reserved_zero_4bits is required to
be
>          equal to 0 in [1], but other values for it may be specified
in
>          the future by ITU-T or ISO/IEC.
>=20
>  NEW: (note that the change here is purely editorial)
>=20
>       profile-level-id:
>=20
>          A base16 [7] (hexadecimal) representation of the following
>=20
>          three bytes in the sequence parameter set NAL unit is
specified
>=20
>          in [1]: 1) profile_idc, 2) a byte herein referred to as
>=20
>          profile-iop, composed of the values of constraint_set0_flag,
>=20
>          constraint_set1_flag,constraint_set2_flag,
>=20
>          constraint_set3_flag, constraint_set4_flag,
constraint_set5_flag,
>=20
>  and reserved_zero_2bits in bit-significance order, starting from the
most-significant bit, and
>=20
>          3) level_idc.  Note that reserved_zero_2bits is required to
be
>=20
>          equal to 0 in [1], but other values for it may be specified
in
>=20
>          the future by ITU-T or ISO/IEC.
>=20
>=20
>=20
> OLD:
>=20
>          For example, in the table above, profile_idc equal to 58
>          (Extended) with profile-iop equal to 11xx0000 indicates the
>          same sub-profile corresponding to profile_idc equal to 42
>          (Baseline) with profile-iop equal to x1xx0000.  Note that
other
>          combinations of profile_idc and profile-iop (not listed in
>          Table 5) may represent a sub-profile equivalent to the common
>          subset of coding tools for more than one profile.  Note also
>          that a decoder conforming to a certain profile may be able to
>          decode bitstreams conforming to other profiles.  For example,
a
>          decoder conforming to the High 4:4:4 profile, at a certain
>          level, must be able to decode bitstreams conforming to the
>          Constrained Baseline, Main, High, High 10, or High 4:2:2
>          profile at the same or a lower level.
>=20
>  NEW: (note that the change here is purely editorial)
>=20
>          For example, in the table above, profile_idc equal to 58
>=20
>          (Extended) with profile-iop equal to 11xx0000 indicates the
>=20
>          same sub-profile corresponding to profile_idc equal to 42
>=20
>          (Baseline) with profile-iop equal to x1xx0000.  Note that
other
>=20
>          combinations of profile_idc and profile-iop (not listed in
>=20
>          Table 5) may represent a sub-profile equivalent to the common
>=20
>          subset of coding tools for more than one profile.  Note also
>=20
>          that a decoder conforming to a certain profile may be able to
>=20
>          decode bitstreams conforming to other profiles.
>=20
>=20
>=20
> OLD:
>=20
>          If the profile-level-id parameter is used for capability
>          exchange or session setup procedure, it indicates the subset
of
>          coding tools, which is equal to the default sub-profile, that
>          the codec supports for both receiving and sending.
>=20
>  NEW: (note that the change here is purely editorial)
>=20
>          If the profile-level-id parameter is used for capability
>=20
>          exchange or session setup, it indicates the subset of
>=20
>          coding tools, which is equal to the default sub-profile, that
>=20
>          the codec supports for both receiving and sending.
>=20
>=20
>=20
> OLD:
>=20
>       max-cpb: The value of max-cpb is an integer indicating the
maximum
>=20
>          coded picture buffer size in units of 1000 bits for the VCL
HRD
>=20
>          parameters (see A.3.1, item i of [1]) and in units of 1200
bits
>=20
>          for the NAL HRD parameters (see A.3.1, item j of [1]).
>=20
> NEW: (note that the change here is purely editorial)
>=20
>       max-cpb: The value of max-cpb is an integer indicating the
maximum
>=20
>          coded picture buffer size in units of 1000 bits for the VCL
HRD
>=20
>          parameters and in units of 1200 bits
>=20
>          for the NAL HRD parameters.
>=20
>=20
>=20
> OLD:
>=20
>       max-dpb: The value of max-dpb is an integer indicating the
maximum
>=20
>          decoded picture buffer size in units of 1024 bytes.  The max-
>=20
>          dpb parameter signals that the receiver has more memory than
>=20
>          the minimum amount of decoded picture buffer memory required
by
>=20
>          the signaled highest level conveyed in the value of the
>=20
>          profile-level-id parameter or the max-recv-level parameter.
>=20
>          When max-dpb is signaled, the receiver MUST be able to decode
>=20
>          NAL unit streams that conform to the signaled highest level,
>=20
>          with the exception that the MaxDPB value in Table A-1 of [1]
>=20
>          for the signaled highest level is replaced with the value of
>=20
>          max-dpb.  Consequently, a receiver that signals max-dpb MUST
be
>=20
>          capable of storing the following number of decoded frames,
>=20
>          complementary field pairs, and non-paired fields in its
decoded
>=20
>          picture buffer:
>=20
>=20
>=20
>             Min(1024 * max-dpb / ( PicWidthInMbs * FrameHeightInMbs *
>=20
>             256 * ChromaFormatFactor ), 16)
>=20
>=20
>=20
>          PicWidthInMbs, FrameHeightInMbs, and ChromaFormatFactor are
>=20
>          defined in [1].
>=20
>=20
>=20
>          The value of max-dpb MUST be greater than or equal to the
value
>=20
>          of MaxDPB given in Table A-1 of [1] for the highest level.
>=20
>          Senders MAY use this knowledge to construct coded video
streams
>=20
>          with improved compression.
>=20
> NEW: (When this change can be considered as editorial can be
discussed, but the nature of this change
> as follows. On the other hand, if not changed, then the semantics of
max-dpb is simply equivalent to
> unspecified, as MaxDPB and ChromaFormatFactor are not found in the
latest H.264 spec any more. Note
> that compared to RFC 3984, the bits on the wire do not change.)
>=20
>       max-dpb: The value of max-dpb is an integer indicating the
maximum
>=20
>          decoded picture buffer size in units of 8/3 macroblocks.  The
max-
>=20
>          dpb parameter signals that the receiver has more memory than
>=20
>          the minimum amount of decoded picture buffer memory required
by
>=20
>          the signaled highest level conveyed in the value of the
>=20
>          profile-level-id parameter or the max-recv-level parameter.
>=20
>          When max-dpb is signaled, the receiver MUST be able to decode
>=20
>          NAL unit streams that conform to the signaled highest level,
>=20
>          with the exception that the MaxDpbMbs value in Table A-1 of
[1]
>=20
>          for the signaled highest level is replaced with the value of
>=20
>          max-dpb * 3 / 8.  Consequently, a receiver that signals
max-dpb MUST be
>=20
>          capable of storing the following number of decoded frames,
>=20
>          complementary field pairs, and non-paired fields in its
decoded
>=20
>          picture buffer:
>=20
>=20
>=20
>             Min(max-dpb * 3 / 8 / ( PicWidthInMbs * FrameHeightInMbs),
16)
>=20
>=20
>=20
>          Wherein PicWidthInMbs and FrameHeightInMbs are defined in
[1].
>=20
>=20
>=20
>          The value of max-dpb MUST be greater than or equal to the
value
>=20
>          of MaxDpbMbs * 3 / 8, wherein the value of MaxDpbMbs is given
in
>=20
> Table A-1 of [1] for the highest level.
>=20
>          Senders MAY use this knowledge to construct coded video
streams
>=20
>          with improved compression.
>=20
>=20
>=20
> OLD:
>=20
>       max-br: The value of max-br is an integer indicating the maximum
>          video bitrate in units of 1000 bits per second for the VCL
HRD
>          parameters (see A.3.1, item i of [1]) and in units of 1200
bits
>          per second for the NAL HRD parameters (see A.3.1, item j of
>          [1]).
>          ...
>=20
>          For example, if a receiver signals capability for Level 1.2
>=20
>          with max-br equal to 1550, this indicates a maximum video
>=20
>          bitrate of 1550 kbits/sec for VCL HRD parameters, a maximum
>=20
>          video bitrate of 1860 kbits/sec for NAL HRD parameters, and a
>=20
>          CPB size of 4036458 bits (1550000 / 384000 * 1000 * 1000).
>=20
> NEW: (note that the change here is purely editorial)
>=20
>       max-br: The value of max-br is an integer indicating the maximum
>          video bitrate in units of 1000 bits per second for the VCL
HRD
>          parameters and in units of 1200 bits
>          per second for the NAL HRD parameters.
>          ...
>=20
>          For example, if a receiver signals capability for Main
profile Level 1.2
>=20
>          with max-br equal to 1550, this indicates a maximum video
>=20
>          bitrate of 1550 kbits/sec for VCL HRD parameters, a maximum
>=20
>          video bitrate of 1860 kbits/sec for NAL HRD parameters, and a
>=20
>          CPB size of 4036458 bits (1550000 / 384000 * 1000 * 1000).
>=20
>=20
>=20
> ------------------------------------End of suggested changes
--------------------------------------
>=20
>=20
>=20
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Ye-Kui Wang
> Sent: Sunday, March 20, 2011 4:21 AM
> To: payload@ietf.org; avt@ietf.org
> Subject: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload
drafts
>=20
>=20
>=20
> Folks,
>=20
>=20
>=20
> The three H.264/AVC related payload formats, namely,
draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-
> rtp-svc-27, and draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48
stage.
>=20
>=20
>=20
> The RFC-Editor has found the following problem: In
draft-ietf-avt-rtp-rfc3984bis-12, the definition of
> the max-dpb media parameter refers to the MaxDPB that was defined the
first version of the H.264/AVC
> spec, but not any more in the latest version (the 2010 version). The
parameter in the latest H.264/AVC
> version corresponding to MaxDPB is MaxDpbMbs, and the unit of the new
parameter (i.e., macroblocks) is
> different from the original one (i.e. 1024 bytes).
>=20
>=20
>=20
> The problem applies also to the SVC payload format, the RCDO payload
format, and H.241.
>=20
>=20
>=20
> A solution has been found and agreed, involving rfc3984bis authors and
some key people related to
> H.264/AVC (e.g., Gary Sullivan and Heiko Schwarz) and H.241 (e.g.,
Stephen Botzko and Patrick Luthi).
> Furthermore, we have found that there are also a couple of places that
need fixes due to similar
> changes from the initial version of H.264/AVC to the latest version.
>=20
>=20
>=20
> Per Roni's suggestion, I am sending in below the changes to
draft-ietf-avt-rtp-rfc3984bis-12 for
> review by the Payload and AVTcore WGs. It seems that exactly the same
changes are needed to draft-
> ietf-avt-rtp-h264-rcdo-08 (co-authors of this draft may confirm), and
similar but slightly different
> changes are needed to draft-ietf-avt-rtp-svc-27.
>=20
>=20
>=20
> Since the drafts are at the AUTH48 stage, please provide comments by
Monday, March 21, if any. Many
> thanks!
>=20
>=20
>=20
> BR, YK
>=20
>=20

_______________________________________________
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 yekui.wang@huawei.com  Wed Mar 23 07:54:29 2011
Return-Path: <yekui.wang@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B0B983A685A; Wed, 23 Mar 2011 07:54:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.261
X-Spam-Level: 
X-Spam-Status: No, score=-6.261 tagged_above=-999 required=5 tests=[AWL=-0.262, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W4Qaqm1uvNst; Wed, 23 Mar 2011 07:54:27 -0700 (PDT)
Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180]) by core3.amsl.com (Postfix) with ESMTP id 5D9973A684B; Wed, 23 Mar 2011 07:54:27 -0700 (PDT)
Received: from huawei.com (usaga04-in [172.18.4.101]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LII00E6ZMTC1A@usaga04-in.huawei.com>; Wed, 23 Mar 2011 09:56:00 -0500 (CDT)
Received: from dfweml201-edg.china.huawei.com ([172.18.9.107]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPS id <0LII00LJ6MT053@usaga04-in.huawei.com>; Wed, 23 Mar 2011 09:56:00 -0500 (CDT)
Received: from DFWEML402-HUB.china.huawei.com (10.193.5.102) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.270.1; Wed, 23 Mar 2011 07:55:52 -0700
Received: from DFWEML503-MBX.china.huawei.com ([169.254.3.47]) by DFWEML402-HUB.china.huawei.com ([::1]) with mapi id 14.01.0270.001; Wed, 23 Mar 2011 07:55:47 -0700
Date: Wed, 23 Mar 2011 14:55:46 +0000
From: Ye-Kui Wang <yekui.wang@huawei.com>
In-reply-to: <71C9EC0544D1F64D8B7D91EDCC62202006890498@NABSREX027324.NAB.ORG>
X-Originating-IP: [10.200.218.160]
To: "Allison, Art" <AAllison@nab.org>, "payload@ietf.org" <payload@ietf.org>,  "avt@ietf.org" <avt@ietf.org>
Message-id: <B99DECD58A94E143BA6F1508CC688351051D4163@dfweml503-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US
Thread-topic: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and RCDO payload drafts
Thread-index: AQHL6TfkNG8bu5QUBkWtpBAtPXzvbpQ6866QgAAMmMA=
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <B99DECD58A94E143BA6F1508CC688351B445DE@dfweml504-mbx.china.huawei.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE39AD@xmb-sjc-234.amer.cisco.com> <71C9EC0544D1F64D8B7D91EDCC62202006890479@NABSREX027324.NAB.ORG> <B99DECD58A94E143BA6F1508CC688351051CAE50@dfweml503-mbx.china.huawei.com> <71C9EC0544D1F64D8B7D91EDCC62202006890498@NABSREX027324.NAB.ORG>
Subject: Re: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Mar 2011 14:54:29 -0000

The 1000 and 1200 are for Video Coding Layer (VCL) and Network Abstraction =
Layer (NAL), respectively, and the numbers (magic or not) were from the H.2=
64/AVC spec. The unit of bits is for buffer size, and the unit of bits per =
second is for bitrate (which are clear from the text), they have to be diff=
erent (which you call inconsistency). Many times you have to be inconsisten=
t to be correct :-)

The changes are now sent to the (two) lists for review, and we authors welc=
ome any comments, and particularly those that point out concrete further ch=
anges that are needed.

BR, YK

-----Original Message-----
From: Allison, Art [mailto:AAllison@nab.org]=20
Sent: Wednesday, March 23, 2011 10:37 AM
To: Ye-Kui Wang; payload@ietf.org; avt@ietf.org
Subject: RE: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and RCDO =
payload drafts

I admit significant ignorance of the technical details. =20

My main point, based on decades of standards development experience, was th=
at last minute changes such as these often result in failure to fix the iss=
ue precisely and that the due process group should be given time to assure =
the correct fix has been made.  Rushing can work, but often has a bad outco=
me.=20

As to specifics; I saw that the values of 1000 and 1200 as the correct unit=
 sizes for NAL stream overhead (in some cases).  In one place these are ass=
erted to be bits (no rate units) as a multiplier and in another place these=
 are described as bits-per-second. These are clearly different usages. Perh=
aps both usages are correct - I do not know - but it appeared to be inconsi=
stent.  (And this type of inconsistency is exactly the kind of thing that I=
 have seen happen when last minute patches are made to a standard.)

By magic number, I meant was it correct that these values have two differen=
t uses, perhaps due to their fundamental nature.

I do not assert anything is wrong, I suggest that unless there is a vital n=
eed to push this out fast, that the draft be referred back to the drafting =
group. Maybe all those folks have had time to carefully consider and respon=
d before the deadline...and this is specious.

I believe that you <process managers> can make better decisions when more i=
nformation is provided. I commented to so assist.
=20

Art Allison
Senior Director Advanced Engineering, Science and Technology
National Association of Broadcasters
1771 N Street NW
Washington, DC 20036
Phone=A0 202 429 5418=20
Fax=A0 202 775 4981
www.nab.org
Advocacy =A0Education=A0 Innovation


-----Original Message-----
From: Ye-Kui Wang [mailto:yekui.wang@huawei.com]=20
Sent: Wednesday, March 23, 2011 4:54 AM
To: Allison, Art; payload@ietf.org; avt@ietf.org
Subject: RE: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and RCDO =
payload drafts

The units of the values of 1000 and 1200 are clearly specified. Where is no=
t clear, could you clarify?=20

What is "that" in "Is that a coincidence, error or a magic number effect?"?

If you read carefully the previous two emails on this subject I sent out, y=
ou would have noticed that the factor you mentioned, which is not only for =
High profile, but for many other profiles, and the factor can be different =
for different profiles, has been addressed. Please let us know if you found=
 any place that is not well addressed.

Finally, what is "this" in "I think this should be sent back for correction=
..."? I guess you meant for the entire draft. But if you don't point out th=
e place that needs to be corrected, what we can do?

BR, YK

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Allis=
on, Art
Sent: Monday, March 21, 2011 4:47 PM
To: payload@ietf.org; avt@ietf.org
Subject: Re: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and RCDO =
payload drafts

It has been by experience that discovery of a significant technical issue t=
hat is 'patched' in a draft standard in a hurry to get it published is alwa=
ys risky and often results in an internal inconsistency.

Seems to me that is a few weeks delay for the formulating body to review is=
 prudent - even if such change can be done.=20

Just reading for consistency, as I am no expert in the codec; I see the 100=
0 and 1200 values expressed as pure multipliers and bits per second? Is tha=
t a coincidence, error or a magic number effect? And the High Profile facto=
r of 1.25 (to these values) that is in the AVC standard seems to be relevan=
t, but is not being discussed. Is that covered elsewhere in a clear fashion=
 and independent?

I think this should be sent back for correction...and thanks go to the shar=
p eye who caught the discrepancy.

Art

Art Allison
Senior Director Advanced Engineering, Science and Technology
National Association of Broadcasters
1771 N Street NW
Washington, DC 20036
Phone=A0 202 429 5418=20
Fax=A0 202 775 4981
www.nab.org
Advocacy =A0Education=A0 Innovation


-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Charl=
es Eckel (eckelcu)
Sent: Monday, March 21, 2011 1:52 PM
To: Ye-Kui Wang; payload@ietf.org; avt@ietf.org
Subject: Re: [AVTCORE] [payload] Some changes to rfc3984bis, SVC,and RCDO p=
ayload drafts

Hi YK,

Thank you for providing this clear description of the proposed changes.
The changes look good to me.

Cheers,
Charles

> -----Original Message-----
> From: payload-bounces@ietf.org [mailto:payload-bounces@ietf.org] On
Behalf Of Ye-Kui Wang
> Sent: Monday, March 21, 2011 1:11 AM
> To: payload@ietf.org; avt@ietf.org
> Subject: Re: [payload] Some changes to rfc3984bis, SVC,and RCDO
payload drafts
>=20
> Further discussions with the same group of persons led to a decision
to stay with the unscaled units
> for max-br and max-cpb, thus fewer changes are needed to the three
payload formats listed in the title
> and H.241. With this, the changes needed are listed below (the
originally suggested changes are
> dropped from this email). This time I have highlighted the changes,
and I have also described the
> nature the changes below. Hope these may help understand better what
have been changed, and can lead
> to a quicker decision by the group, including WG chairs, and our AD.
>=20
>=20
>=20
> BR, YK
>=20
>=20
>=20
> ------------------------------------Start of suggested changes
--------------------------------------
>=20
>=20
>=20
> Section 8.1:
>=20
> OLD:
>=20
>       profile-level-id:
>          A base16 [7] (hexadecimal) representation of the following
>          three bytes in the sequence parameter set NAL unit is
specified
>          in [1]: 1) profile_idc, 2) a byte herein referred to as
>          profile-iop, composed of the values of constraint_set0_flag,
>          constraint_set1_flag,constraint_set2_flag,
>          constraint_set3_flag, and reserved_zero_4bits in bit-
>          significance order, starting from the most-significant bit,
and
>          3) level_idc.  Note that reserved_zero_4bits is required to
be
>          equal to 0 in [1], but other values for it may be specified
in
>          the future by ITU-T or ISO/IEC.
>=20
>  NEW: (note that the change here is purely editorial)
>=20
>       profile-level-id:
>=20
>          A base16 [7] (hexadecimal) representation of the following
>=20
>          three bytes in the sequence parameter set NAL unit is
specified
>=20
>          in [1]: 1) profile_idc, 2) a byte herein referred to as
>=20
>          profile-iop, composed of the values of constraint_set0_flag,
>=20
>          constraint_set1_flag,constraint_set2_flag,
>=20
>          constraint_set3_flag, constraint_set4_flag,
constraint_set5_flag,
>=20
>  and reserved_zero_2bits in bit-significance order, starting from the
most-significant bit, and
>=20
>          3) level_idc.  Note that reserved_zero_2bits is required to
be
>=20
>          equal to 0 in [1], but other values for it may be specified
in
>=20
>          the future by ITU-T or ISO/IEC.
>=20
>=20
>=20
> OLD:
>=20
>          For example, in the table above, profile_idc equal to 58
>          (Extended) with profile-iop equal to 11xx0000 indicates the
>          same sub-profile corresponding to profile_idc equal to 42
>          (Baseline) with profile-iop equal to x1xx0000.  Note that
other
>          combinations of profile_idc and profile-iop (not listed in
>          Table 5) may represent a sub-profile equivalent to the common
>          subset of coding tools for more than one profile.  Note also
>          that a decoder conforming to a certain profile may be able to
>          decode bitstreams conforming to other profiles.  For example,
a
>          decoder conforming to the High 4:4:4 profile, at a certain
>          level, must be able to decode bitstreams conforming to the
>          Constrained Baseline, Main, High, High 10, or High 4:2:2
>          profile at the same or a lower level.
>=20
>  NEW: (note that the change here is purely editorial)
>=20
>          For example, in the table above, profile_idc equal to 58
>=20
>          (Extended) with profile-iop equal to 11xx0000 indicates the
>=20
>          same sub-profile corresponding to profile_idc equal to 42
>=20
>          (Baseline) with profile-iop equal to x1xx0000.  Note that
other
>=20
>          combinations of profile_idc and profile-iop (not listed in
>=20
>          Table 5) may represent a sub-profile equivalent to the common
>=20
>          subset of coding tools for more than one profile.  Note also
>=20
>          that a decoder conforming to a certain profile may be able to
>=20
>          decode bitstreams conforming to other profiles.
>=20
>=20
>=20
> OLD:
>=20
>          If the profile-level-id parameter is used for capability
>          exchange or session setup procedure, it indicates the subset
of
>          coding tools, which is equal to the default sub-profile, that
>          the codec supports for both receiving and sending.
>=20
>  NEW: (note that the change here is purely editorial)
>=20
>          If the profile-level-id parameter is used for capability
>=20
>          exchange or session setup, it indicates the subset of
>=20
>          coding tools, which is equal to the default sub-profile, that
>=20
>          the codec supports for both receiving and sending.
>=20
>=20
>=20
> OLD:
>=20
>       max-cpb: The value of max-cpb is an integer indicating the
maximum
>=20
>          coded picture buffer size in units of 1000 bits for the VCL
HRD
>=20
>          parameters (see A.3.1, item i of [1]) and in units of 1200
bits
>=20
>          for the NAL HRD parameters (see A.3.1, item j of [1]).
>=20
> NEW: (note that the change here is purely editorial)
>=20
>       max-cpb: The value of max-cpb is an integer indicating the
maximum
>=20
>          coded picture buffer size in units of 1000 bits for the VCL
HRD
>=20
>          parameters and in units of 1200 bits
>=20
>          for the NAL HRD parameters.
>=20
>=20
>=20
> OLD:
>=20
>       max-dpb: The value of max-dpb is an integer indicating the
maximum
>=20
>          decoded picture buffer size in units of 1024 bytes.  The max-
>=20
>          dpb parameter signals that the receiver has more memory than
>=20
>          the minimum amount of decoded picture buffer memory required
by
>=20
>          the signaled highest level conveyed in the value of the
>=20
>          profile-level-id parameter or the max-recv-level parameter.
>=20
>          When max-dpb is signaled, the receiver MUST be able to decode
>=20
>          NAL unit streams that conform to the signaled highest level,
>=20
>          with the exception that the MaxDPB value in Table A-1 of [1]
>=20
>          for the signaled highest level is replaced with the value of
>=20
>          max-dpb.  Consequently, a receiver that signals max-dpb MUST
be
>=20
>          capable of storing the following number of decoded frames,
>=20
>          complementary field pairs, and non-paired fields in its
decoded
>=20
>          picture buffer:
>=20
>=20
>=20
>             Min(1024 * max-dpb / ( PicWidthInMbs * FrameHeightInMbs *
>=20
>             256 * ChromaFormatFactor ), 16)
>=20
>=20
>=20
>          PicWidthInMbs, FrameHeightInMbs, and ChromaFormatFactor are
>=20
>          defined in [1].
>=20
>=20
>=20
>          The value of max-dpb MUST be greater than or equal to the
value
>=20
>          of MaxDPB given in Table A-1 of [1] for the highest level.
>=20
>          Senders MAY use this knowledge to construct coded video
streams
>=20
>          with improved compression.
>=20
> NEW: (When this change can be considered as editorial can be
discussed, but the nature of this change
> as follows. On the other hand, if not changed, then the semantics of
max-dpb is simply equivalent to
> unspecified, as MaxDPB and ChromaFormatFactor are not found in the
latest H.264 spec any more. Note
> that compared to RFC 3984, the bits on the wire do not change.)
>=20
>       max-dpb: The value of max-dpb is an integer indicating the
maximum
>=20
>          decoded picture buffer size in units of 8/3 macroblocks.  The
max-
>=20
>          dpb parameter signals that the receiver has more memory than
>=20
>          the minimum amount of decoded picture buffer memory required
by
>=20
>          the signaled highest level conveyed in the value of the
>=20
>          profile-level-id parameter or the max-recv-level parameter.
>=20
>          When max-dpb is signaled, the receiver MUST be able to decode
>=20
>          NAL unit streams that conform to the signaled highest level,
>=20
>          with the exception that the MaxDpbMbs value in Table A-1 of
[1]
>=20
>          for the signaled highest level is replaced with the value of
>=20
>          max-dpb * 3 / 8.  Consequently, a receiver that signals
max-dpb MUST be
>=20
>          capable of storing the following number of decoded frames,
>=20
>          complementary field pairs, and non-paired fields in its
decoded
>=20
>          picture buffer:
>=20
>=20
>=20
>             Min(max-dpb * 3 / 8 / ( PicWidthInMbs * FrameHeightInMbs),
16)
>=20
>=20
>=20
>          Wherein PicWidthInMbs and FrameHeightInMbs are defined in
[1].
>=20
>=20
>=20
>          The value of max-dpb MUST be greater than or equal to the
value
>=20
>          of MaxDpbMbs * 3 / 8, wherein the value of MaxDpbMbs is given
in
>=20
> Table A-1 of [1] for the highest level.
>=20
>          Senders MAY use this knowledge to construct coded video
streams
>=20
>          with improved compression.
>=20
>=20
>=20
> OLD:
>=20
>       max-br: The value of max-br is an integer indicating the maximum
>          video bitrate in units of 1000 bits per second for the VCL
HRD
>          parameters (see A.3.1, item i of [1]) and in units of 1200
bits
>          per second for the NAL HRD parameters (see A.3.1, item j of
>          [1]).
>          ...
>=20
>          For example, if a receiver signals capability for Level 1.2
>=20
>          with max-br equal to 1550, this indicates a maximum video
>=20
>          bitrate of 1550 kbits/sec for VCL HRD parameters, a maximum
>=20
>          video bitrate of 1860 kbits/sec for NAL HRD parameters, and a
>=20
>          CPB size of 4036458 bits (1550000 / 384000 * 1000 * 1000).
>=20
> NEW: (note that the change here is purely editorial)
>=20
>       max-br: The value of max-br is an integer indicating the maximum
>          video bitrate in units of 1000 bits per second for the VCL
HRD
>          parameters and in units of 1200 bits
>          per second for the NAL HRD parameters.
>          ...
>=20
>          For example, if a receiver signals capability for Main
profile Level 1.2
>=20
>          with max-br equal to 1550, this indicates a maximum video
>=20
>          bitrate of 1550 kbits/sec for VCL HRD parameters, a maximum
>=20
>          video bitrate of 1860 kbits/sec for NAL HRD parameters, and a
>=20
>          CPB size of 4036458 bits (1550000 / 384000 * 1000 * 1000).
>=20
>=20
>=20
> ------------------------------------End of suggested changes
--------------------------------------
>=20
>=20
>=20
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Ye-Kui Wang
> Sent: Sunday, March 20, 2011 4:21 AM
> To: payload@ietf.org; avt@ietf.org
> Subject: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload
drafts
>=20
>=20
>=20
> Folks,
>=20
>=20
>=20
> The three H.264/AVC related payload formats, namely,
draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-
> rtp-svc-27, and draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48
stage.
>=20
>=20
>=20
> The RFC-Editor has found the following problem: In
draft-ietf-avt-rtp-rfc3984bis-12, the definition of
> the max-dpb media parameter refers to the MaxDPB that was defined the
first version of the H.264/AVC
> spec, but not any more in the latest version (the 2010 version). The
parameter in the latest H.264/AVC
> version corresponding to MaxDPB is MaxDpbMbs, and the unit of the new
parameter (i.e., macroblocks) is
> different from the original one (i.e. 1024 bytes).
>=20
>=20
>=20
> The problem applies also to the SVC payload format, the RCDO payload
format, and H.241.
>=20
>=20
>=20
> A solution has been found and agreed, involving rfc3984bis authors and
some key people related to
> H.264/AVC (e.g., Gary Sullivan and Heiko Schwarz) and H.241 (e.g.,
Stephen Botzko and Patrick Luthi).
> Furthermore, we have found that there are also a couple of places that
need fixes due to similar
> changes from the initial version of H.264/AVC to the latest version.
>=20
>=20
>=20
> Per Roni's suggestion, I am sending in below the changes to
draft-ietf-avt-rtp-rfc3984bis-12 for
> review by the Payload and AVTcore WGs. It seems that exactly the same
changes are needed to draft-
> ietf-avt-rtp-h264-rcdo-08 (co-authors of this draft may confirm), and
similar but slightly different
> changes are needed to draft-ietf-avt-rtp-svc-27.
>=20
>=20
>=20
> Since the drafts are at the AUTH48 stage, please provide comments by
Monday, March 21, if any. Many
> thanks!
>=20
>=20
>=20
> BR, YK
>=20
>=20

_______________________________________________
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 Even.roni@huawei.com  Wed Mar 23 11:18:25 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 45E9E28C116; Wed, 23 Mar 2011 11:18:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.984
X-Spam-Level: 
X-Spam-Status: No, score=-99.984 tagged_above=-999 required=5 tests=[AWL=-0.089, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_33=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FyS775tqhOii; Wed, 23 Mar 2011 11:18:23 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 0075528C110; Wed, 23 Mar 2011 11:18:23 -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 <0LII002T8W93IP@szxga05-in.huawei.com>; Thu, 24 Mar 2011 02:19:51 +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 <0LII00IQ2W92R8@szxga05-in.huawei.com>; Thu, 24 Mar 2011 02:19:51 +0800 (CST)
Received: from windows8d787f9 (cust.static.109-164-246-172.swisscomdata.ch [109.164.246.172]) by szxml12-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LII00LYVW8Q2Z@szxml12-in.huawei.com>; Thu, 24 Mar 2011 02:19:50 +0800 (CST)
Date: Wed, 23 Mar 2011 20:19:20 +0200
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <71C9EC0544D1F64D8B7D91EDCC62202006890498@NABSREX027324.NAB.ORG>
To: "'Allison, Art'" <AAllison@nab.org>, 'Ye-Kui Wang' <yekui.wang@huawei.com>, payload@ietf.org, avt@ietf.org
Message-id: <000501cbe986$db1902d0$914b0870$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=windows-1255
Content-language: en-us
Content-transfer-encoding: quoted-printable
Thread-index: AQHL6TfkNG8bu5QUBkWtpBAtPXzvbpQ6866QgAAOfWA=
References: <B99DECD58A94E143BA6F1508CC688351B445DE@dfweml504-mbx.china.huawei.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C03CE39AD@xmb-sjc-234.amer.cisco.com> <71C9EC0544D1F64D8B7D91EDCC62202006890479@NABSREX027324.NAB.ORG> <B99DECD58A94E143BA6F1508CC688351051CAE50@dfweml503-mbx.china.huawei.com> <71C9EC0544D1F64D8B7D91EDCC62202006890498@NABSREX027324.NAB.ORG>
Subject: Re: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Mar 2011 18:18:25 -0000

Hi,
The changes were done taking advantage of the fact that all relevant =
experts
were in Geneva to ITU-T SG16 meeting (both the H.264 guys and the
signaling). After a couple of days of email exchange everybody met face =
to
face to iron up the issue. I was part of the email exchange and asked =
them
to post to the avtcore and payload mailing list. Since it has been =
posted
the only feedback on the list was about procedure and not technical.=20
My assumption is that we will not see any technical comments but will =
wait
till next week.
As for the timeline- this changes are also relevant to H.241 which is =
the
H.323 signaling for H.323. The changes were incorporated there as well =
and
reviewed and will be approved this week since we are all now in the =
ITU-T
study group 16 meeting
Regards
Roni Even

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Allison, Art
> Sent: Wednesday, March 23, 2011 4:37 PM
> To: Ye-Kui Wang; payload@ietf.org; avt@ietf.org
> Subject: Re: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and
> RCDO payload drafts
>=20
> I admit significant ignorance of the technical details.
>=20
> My main point, based on decades of standards development experience,
> was that last minute changes such as these often result in failure to
> fix the issue precisely and that the due process group should be given
> time to assure the correct fix has been made.  Rushing can work, but
> often has a bad outcome.
>=20
> As to specifics; I saw that the values of 1000 and 1200 as the correct
> unit sizes for NAL stream overhead (in some cases).  In one place =
these
> are asserted to be bits (no rate units) as a multiplier and in another
> place these are described as bits-per-second. These are clearly
> different usages. Perhaps both usages are correct - I do not know - =
but
> it appeared to be inconsistent.  (And this type of inconsistency is
> exactly the kind of thing that I have seen happen when last minute
> patches are made to a standard.)
>=20
> By magic number, I meant was it correct that these values have two
> different uses, perhaps due to their fundamental nature.
>=20
> I do not assert anything is wrong, I suggest that unless there is a
> vital need to push this out fast, that the draft be referred back to
> the drafting group. Maybe all those folks have had time to carefully
> consider and respond before the deadline...and this is specious.
>=20
> I believe that you <process managers> can make better decisions when
> more information is provided. I commented to so assist.
>=20
>=20
> Art Allison
> Senior Director Advanced Engineering, Science and Technology
> National Association of Broadcasters
> 1771 N Street NW
> Washington, DC 20036
> Phone=A0 202 429 5418
> Fax=A0 202 775 4981
> www.nab.org
> Advocacy =A0Education=A0 Innovation
>=20
>=20
> -----Original Message-----
> From: Ye-Kui Wang [mailto:yekui.wang@huawei.com]
> Sent: Wednesday, March 23, 2011 4:54 AM
> To: Allison, Art; payload@ietf.org; avt@ietf.org
> Subject: RE: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and
> RCDO payload drafts
>=20
> The units of the values of 1000 and 1200 are clearly specified. Where
> is not clear, could you clarify?
>=20
> What is "that" in "Is that a coincidence, error or a magic number
> effect?"?
>=20
> If you read carefully the previous two emails on this subject I sent
> out, you would have noticed that the factor you mentioned, which is =
not
> only for High profile, but for many other profiles, and the factor can
> be different for different profiles, has been addressed. Please let us
> know if you found any place that is not well addressed.
>=20
> Finally, what is "this" in "I think this should be sent back for
> correction..."? I guess you meant for the entire draft. But if you
> don't point out the place that needs to be corrected, what we can do?
>=20
> BR, YK
>=20
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Allison, Art
> Sent: Monday, March 21, 2011 4:47 PM
> To: payload@ietf.org; avt@ietf.org
> Subject: Re: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and
> RCDO payload drafts
>=20
> It has been by experience that discovery of a significant technical
> issue that is 'patched' in a draft standard in a hurry to get it
> published is always risky and often results in an internal
> inconsistency.
>=20
> Seems to me that is a few weeks delay for the formulating body to
> review is prudent - even if such change can be done.
>=20
> Just reading for consistency, as I am no expert in the codec; I see =
the
> 1000 and 1200 values expressed as pure multipliers and bits per =
second?
> Is that a coincidence, error or a magic number effect? And the High
> Profile factor of 1.25 (to these values) that is in the AVC standard
> seems to be relevant, but is not being discussed. Is that covered
> elsewhere in a clear fashion and independent?
>=20
> I think this should be sent back for correction...and thanks go to the
> sharp eye who caught the discrepancy.
>=20
> Art
>=20
> Art Allison
> Senior Director Advanced Engineering, Science and Technology
> National Association of Broadcasters
> 1771 N Street NW
> Washington, DC 20036
> Phone=A0 202 429 5418
> Fax=A0 202 775 4981
> www.nab.org
> Advocacy =A0Education=A0 Innovation
>=20
>=20
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Charles Eckel (eckelcu)
> Sent: Monday, March 21, 2011 1:52 PM
> To: Ye-Kui Wang; payload@ietf.org; avt@ietf.org
> Subject: Re: [AVTCORE] [payload] Some changes to rfc3984bis, SVC,and
> RCDO payload drafts
>=20
> Hi YK,
>=20
> Thank you for providing this clear description of the proposed =
changes.
> The changes look good to me.
>=20
> Cheers,
> Charles
>=20
> > -----Original Message-----
> > From: payload-bounces@ietf.org [mailto:payload-bounces@ietf.org] On
> Behalf Of Ye-Kui Wang
> > Sent: Monday, March 21, 2011 1:11 AM
> > To: payload@ietf.org; avt@ietf.org
> > Subject: Re: [payload] Some changes to rfc3984bis, SVC,and RCDO
> payload drafts
> >
> > Further discussions with the same group of persons led to a decision
> to stay with the unscaled units
> > for max-br and max-cpb, thus fewer changes are needed to the three
> payload formats listed in the title
> > and H.241. With this, the changes needed are listed below (the
> originally suggested changes are
> > dropped from this email). This time I have highlighted the changes,
> and I have also described the
> > nature the changes below. Hope these may help understand better what
> have been changed, and can lead
> > to a quicker decision by the group, including WG chairs, and our AD.
> >
> >
> >
> > BR, YK
> >
> >
> >
> > ------------------------------------Start of suggested changes
> --------------------------------------
> >
> >
> >
> > Section 8.1:
> >
> > OLD:
> >
> >       profile-level-id:
> >          A base16 [7] (hexadecimal) representation of the following
> >          three bytes in the sequence parameter set NAL unit is
> specified
> >          in [1]: 1) profile_idc, 2) a byte herein referred to as
> >          profile-iop, composed of the values of =
constraint_set0_flag,
> >          constraint_set1_flag,constraint_set2_flag,
> >          constraint_set3_flag, and reserved_zero_4bits in bit-
> >          significance order, starting from the most-significant bit,
> and
> >          3) level_idc.  Note that reserved_zero_4bits is required to
> be
> >          equal to 0 in [1], but other values for it may be specified
> in
> >          the future by ITU-T or ISO/IEC.
> >
> >  NEW: (note that the change here is purely editorial)
> >
> >       profile-level-id:
> >
> >          A base16 [7] (hexadecimal) representation of the following
> >
> >          three bytes in the sequence parameter set NAL unit is
> specified
> >
> >          in [1]: 1) profile_idc, 2) a byte herein referred to as
> >
> >          profile-iop, composed of the values of =
constraint_set0_flag,
> >
> >          constraint_set1_flag,constraint_set2_flag,
> >
> >          constraint_set3_flag, constraint_set4_flag,
> constraint_set5_flag,
> >
> >  and reserved_zero_2bits in bit-significance order, starting from =
the
> most-significant bit, and
> >
> >          3) level_idc.  Note that reserved_zero_2bits is required to
> be
> >
> >          equal to 0 in [1], but other values for it may be specified
> in
> >
> >          the future by ITU-T or ISO/IEC.
> >
> >
> >
> > OLD:
> >
> >          For example, in the table above, profile_idc equal to 58
> >          (Extended) with profile-iop equal to 11xx0000 indicates the
> >          same sub-profile corresponding to profile_idc equal to 42
> >          (Baseline) with profile-iop equal to x1xx0000.  Note that
> other
> >          combinations of profile_idc and profile-iop (not listed in
> >          Table 5) may represent a sub-profile equivalent to the
> common
> >          subset of coding tools for more than one profile.  Note =
also
> >          that a decoder conforming to a certain profile may be able
> to
> >          decode bitstreams conforming to other profiles.  For
> example,
> a
> >          decoder conforming to the High 4:4:4 profile, at a certain
> >          level, must be able to decode bitstreams conforming to the
> >          Constrained Baseline, Main, High, High 10, or High 4:2:2
> >          profile at the same or a lower level.
> >
> >  NEW: (note that the change here is purely editorial)
> >
> >          For example, in the table above, profile_idc equal to 58
> >
> >          (Extended) with profile-iop equal to 11xx0000 indicates the
> >
> >          same sub-profile corresponding to profile_idc equal to 42
> >
> >          (Baseline) with profile-iop equal to x1xx0000.  Note that
> other
> >
> >          combinations of profile_idc and profile-iop (not listed in
> >
> >          Table 5) may represent a sub-profile equivalent to the
> common
> >
> >          subset of coding tools for more than one profile.  Note =
also
> >
> >          that a decoder conforming to a certain profile may be able
> to
> >
> >          decode bitstreams conforming to other profiles.
> >
> >
> >
> > OLD:
> >
> >          If the profile-level-id parameter is used for capability
> >          exchange or session setup procedure, it indicates the =
subset
> of
> >          coding tools, which is equal to the default sub-profile,
> that
> >          the codec supports for both receiving and sending.
> >
> >  NEW: (note that the change here is purely editorial)
> >
> >          If the profile-level-id parameter is used for capability
> >
> >          exchange or session setup, it indicates the subset of
> >
> >          coding tools, which is equal to the default sub-profile,
> that
> >
> >          the codec supports for both receiving and sending.
> >
> >
> >
> > OLD:
> >
> >       max-cpb: The value of max-cpb is an integer indicating the
> maximum
> >
> >          coded picture buffer size in units of 1000 bits for the VCL
> HRD
> >
> >          parameters (see A.3.1, item i of [1]) and in units of 1200
> bits
> >
> >          for the NAL HRD parameters (see A.3.1, item j of [1]).
> >
> > NEW: (note that the change here is purely editorial)
> >
> >       max-cpb: The value of max-cpb is an integer indicating the
> maximum
> >
> >          coded picture buffer size in units of 1000 bits for the VCL
> HRD
> >
> >          parameters and in units of 1200 bits
> >
> >          for the NAL HRD parameters.
> >
> >
> >
> > OLD:
> >
> >       max-dpb: The value of max-dpb is an integer indicating the
> maximum
> >
> >          decoded picture buffer size in units of 1024 bytes.  The
> max-
> >
> >          dpb parameter signals that the receiver has more memory =
than
> >
> >          the minimum amount of decoded picture buffer memory =
required
> by
> >
> >          the signaled highest level conveyed in the value of the
> >
> >          profile-level-id parameter or the max-recv-level parameter.
> >
> >          When max-dpb is signaled, the receiver MUST be able to
> decode
> >
> >          NAL unit streams that conform to the signaled highest =
level,
> >
> >          with the exception that the MaxDPB value in Table A-1 of =
[1]
> >
> >          for the signaled highest level is replaced with the value =
of
> >
> >          max-dpb.  Consequently, a receiver that signals max-dpb =
MUST
> be
> >
> >          capable of storing the following number of decoded frames,
> >
> >          complementary field pairs, and non-paired fields in its
> decoded
> >
> >          picture buffer:
> >
> >
> >
> >             Min(1024 * max-dpb / ( PicWidthInMbs * FrameHeightInMbs =
*
> >
> >             256 * ChromaFormatFactor ), 16)
> >
> >
> >
> >          PicWidthInMbs, FrameHeightInMbs, and ChromaFormatFactor are
> >
> >          defined in [1].
> >
> >
> >
> >          The value of max-dpb MUST be greater than or equal to the
> value
> >
> >          of MaxDPB given in Table A-1 of [1] for the highest level.
> >
> >          Senders MAY use this knowledge to construct coded video
> streams
> >
> >          with improved compression.
> >
> > NEW: (When this change can be considered as editorial can be
> discussed, but the nature of this change
> > as follows. On the other hand, if not changed, then the semantics of
> max-dpb is simply equivalent to
> > unspecified, as MaxDPB and ChromaFormatFactor are not found in the
> latest H.264 spec any more. Note
> > that compared to RFC 3984, the bits on the wire do not change.)
> >
> >       max-dpb: The value of max-dpb is an integer indicating the
> maximum
> >
> >          decoded picture buffer size in units of 8/3 macroblocks.
> The
> max-
> >
> >          dpb parameter signals that the receiver has more memory =
than
> >
> >          the minimum amount of decoded picture buffer memory =
required
> by
> >
> >          the signaled highest level conveyed in the value of the
> >
> >          profile-level-id parameter or the max-recv-level parameter.
> >
> >          When max-dpb is signaled, the receiver MUST be able to
> decode
> >
> >          NAL unit streams that conform to the signaled highest =
level,
> >
> >          with the exception that the MaxDpbMbs value in Table A-1 of
> [1]
> >
> >          for the signaled highest level is replaced with the value =
of
> >
> >          max-dpb * 3 / 8.  Consequently, a receiver that signals
> max-dpb MUST be
> >
> >          capable of storing the following number of decoded frames,
> >
> >          complementary field pairs, and non-paired fields in its
> decoded
> >
> >          picture buffer:
> >
> >
> >
> >             Min(max-dpb * 3 / 8 / ( PicWidthInMbs *
> FrameHeightInMbs),
> 16)
> >
> >
> >
> >          Wherein PicWidthInMbs and FrameHeightInMbs are defined in
> [1].
> >
> >
> >
> >          The value of max-dpb MUST be greater than or equal to the
> value
> >
> >          of MaxDpbMbs * 3 / 8, wherein the value of MaxDpbMbs is
> given
> in
> >
> > Table A-1 of [1] for the highest level.
> >
> >          Senders MAY use this knowledge to construct coded video
> streams
> >
> >          with improved compression.
> >
> >
> >
> > OLD:
> >
> >       max-br: The value of max-br is an integer indicating the
> maximum
> >          video bitrate in units of 1000 bits per second for the VCL
> HRD
> >          parameters (see A.3.1, item i of [1]) and in units of 1200
> bits
> >          per second for the NAL HRD parameters (see A.3.1, item j of
> >          [1]).
> >          ...
> >
> >          For example, if a receiver signals capability for Level 1.2
> >
> >          with max-br equal to 1550, this indicates a maximum video
> >
> >          bitrate of 1550 kbits/sec for VCL HRD parameters, a maximum
> >
> >          video bitrate of 1860 kbits/sec for NAL HRD parameters, and
> a
> >
> >          CPB size of 4036458 bits (1550000 / 384000 * 1000 * 1000).
> >
> > NEW: (note that the change here is purely editorial)
> >
> >       max-br: The value of max-br is an integer indicating the
> maximum
> >          video bitrate in units of 1000 bits per second for the VCL
> HRD
> >          parameters and in units of 1200 bits
> >          per second for the NAL HRD parameters.
> >          ...
> >
> >          For example, if a receiver signals capability for Main
> profile Level 1.2
> >
> >          with max-br equal to 1550, this indicates a maximum video
> >
> >          bitrate of 1550 kbits/sec for VCL HRD parameters, a maximum
> >
> >          video bitrate of 1860 kbits/sec for NAL HRD parameters, and
> a
> >
> >          CPB size of 4036458 bits (1550000 / 384000 * 1000 * 1000).
> >
> >
> >
> > ------------------------------------End of suggested changes
> --------------------------------------
> >
> >
> >
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf =
Of
> Ye-Kui Wang
> > Sent: Sunday, March 20, 2011 4:21 AM
> > To: payload@ietf.org; avt@ietf.org
> > Subject: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload
> drafts
> >
> >
> >
> > Folks,
> >
> >
> >
> > The three H.264/AVC related payload formats, namely,
> draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-
> > rtp-svc-27, and draft-ietf-avt-rtp-h264-rcdo-08, are all at the
> AUTH48
> stage.
> >
> >
> >
> > The RFC-Editor has found the following problem: In
> draft-ietf-avt-rtp-rfc3984bis-12, the definition of
> > the max-dpb media parameter refers to the MaxDPB that was defined =
the
> first version of the H.264/AVC
> > spec, but not any more in the latest version (the 2010 version). The
> parameter in the latest H.264/AVC
> > version corresponding to MaxDPB is MaxDpbMbs, and the unit of the =
new
> parameter (i.e., macroblocks) is
> > different from the original one (i.e. 1024 bytes).
> >
> >
> >
> > The problem applies also to the SVC payload format, the RCDO payload
> format, and H.241.
> >
> >
> >
> > A solution has been found and agreed, involving rfc3984bis authors
> and
> some key people related to
> > H.264/AVC (e.g., Gary Sullivan and Heiko Schwarz) and H.241 (e.g.,
> Stephen Botzko and Patrick Luthi).
> > Furthermore, we have found that there are also a couple of places
> that
> need fixes due to similar
> > changes from the initial version of H.264/AVC to the latest version.
> >
> >
> >
> > Per Roni's suggestion, I am sending in below the changes to
> draft-ietf-avt-rtp-rfc3984bis-12 for
> > review by the Payload and AVTcore WGs. It seems that exactly the =
same
> changes are needed to draft-
> > ietf-avt-rtp-h264-rcdo-08 (co-authors of this draft may confirm), =
and
> similar but slightly different
> > changes are needed to draft-ietf-avt-rtp-svc-27.
> >
> >
> >
> > Since the drafts are at the AUTH48 stage, please provide comments by
> Monday, March 21, if any. Many
> > thanks!
> >
> >
> >
> > BR, YK
> >
> >
>=20
> _______________________________________________
> 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
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From stewe@stewe.org  Sat Mar 26 01:55:40 2011
Return-Path: <stewe@stewe.org>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 404B53A6900; Sat, 26 Mar 2011 01:55:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.202
X-Spam-Level: 
X-Spam-Status: No, score=-1.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qkyKyzZxmQol; Sat, 26 Mar 2011 01:55:39 -0700 (PDT)
Received: from stewe.org (stewe.org [85.214.122.234]) by core3.amsl.com (Postfix) with ESMTP id 190C13A68FD; Sat, 26 Mar 2011 01:55:38 -0700 (PDT)
Received: from [192.168.0.4] (unverified [84.187.126.113])  by stewe.org (SurgeMail 3.9e) with ESMTP id 2138-1743317  for multiple; Sat, 26 Mar 2011 09:57:13 +0100
User-Agent: Microsoft-MacOutlook/14.2.0.101115
Date: Sat, 26 Mar 2011 09:56:41 +0100
From: Stephan Wenger <stewe@stewe.org>
To: IETF AVT WG <avt@ietf.org>, <payload@ietf.org>
Message-ID: <C9B368D9.29080%stewe@stewe.org>
Thread-Topic: VP8 payload format
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3383978221_4045035"
X-Originating-IP: 84.187.126.113
X-Authenticated-User: stewe@stewe.org 
X-ORBS-Stamp: Your IP (84.187.126.113) was found in the spamhaus database. http://www.spamhaus.net
Subject: [AVTCORE] VP8 payload format
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Mar 2011 08:55:40 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3383978221_4045035
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Hi all,
I had a brief look at the payload format specification as well as the VP8
codec specification.  I support the adoption of the payload format as a
PAYLOAD work item.  However, we Vidyo people (Alex, Jonathan, and myself)
would like to suggest adding a few mechanisms to efficiently support
temporal scalability, so to at least partially enable the use of VP8 in
applications like ours.  We believe that the VP8 codec does support temporal
scalability, but only when those mechanisms are present in the payload (or
in the VP8 bitstream).  These mechanisms are based on lessons learned during
the implementation of more subtle parts of the SVC payload.  Let's get
together in Prague and see how far we can get with this.
Thanks,
Stephan





--B_3383978221_4045035
Content-type: text/html;
	charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:=
 14px; font-family: Calibri, sans-serif; "><div>Hi all,</div><div>I had a br=
ief look at the payload format specification as well as the VP8 codec specif=
ication. &nbsp;I support the adoption of the payload format as a PAYLOAD wor=
k item. &nbsp;However, we Vidyo people (Alex, Jonathan, and myself) would li=
ke to suggest adding a few mechanisms to efficiently support temporal scalab=
ility, so to at least partially enable the use of VP8 in applications like o=
urs. &nbsp;We believe that the VP8 codec does support temporal scalability, =
but only when those mechanisms are present in the payload (or in the VP8 bit=
stream). &nbsp;These mechanisms are based on lessons learned during the impl=
ementation of more subtle parts of the SVC payload. &nbsp;Let's get together=
 in Prague and see how far we can get with this.</div><div>Thanks,</div><div=
>Stephan</div><div><br></div><div><br></div></body></html>

--B_3383978221_4045035--



From magnus.westerlund@ericsson.com  Sat Mar 26 03:22:57 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B59F23A6920 for <avt@core3.amsl.com>; Sat, 26 Mar 2011 03:22:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.524
X-Spam-Level: 
X-Spam-Status: No, score=-106.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3YV28pPoA4qK for <avt@core3.amsl.com>; Sat, 26 Mar 2011 03:22:57 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 0B0043A691F for <avt@ietf.org>; Sat, 26 Mar 2011 03:22:53 -0700 (PDT)
X-AuditID: c1b4fb39-b7c6dae0000023f2-b8-4d8dbedcea4f
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id BA.C6.09202.CDEBD8D4; Sat, 26 Mar 2011 11:24:28 +0100 (CET)
Received: from [153.88.50.152] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.137.0; Sat, 26 Mar 2011 11:24:28 +0100
Message-ID: <4D8DBEDB.4090406@ericsson.com>
Date: Sat, 26 Mar 2011 11:24:27 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: IETF AVTCore WG <avt@ietf.org>,  VAN CAENEGEM Tom <Tom.Van_Caenegem@alcatel-lucent.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Subject: [AVTCORE] Comments on draft-vancaenegem-avtcore-fb-supp-and-retransm-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Mar 2011 10:22:57 -0000

Tom, AVTCORE,

I have reviewed this draft and have the following comment.

To me it appears that one big reason for the issues is actually that we
haven't specified how RTP retransmission in SSM with unicast delivery is
supposed to work. Because if that was well defined we would likely have
concluded that one should not forward NACK request to the DS from a FT
for any request it service locally.

Thus as I raised before in relation to the RAMS work that there appeared
to be a need for defining this properly, including this aspect. Do we
have anyone that is interested in defining this?

Secondly I think there clearly are some improvements needed of the WG
document based on what you comment. One thing is clearly to clarify the
WG document on its usages, and then map those usages of suppression to
different topologies.

My personal opinion on how to handle your comments are to include your
concerns in the WG document.

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 abegen@cisco.com  Sat Mar 26 05:35:17 2011
Return-Path: <abegen@cisco.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 23A7F3A685D for <avt@core3.amsl.com>; Sat, 26 Mar 2011 05:35:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.532
X-Spam-Level: 
X-Spam-Status: No, score=-8.532 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eJ4PW-rCWr0V for <avt@core3.amsl.com>; Sat, 26 Mar 2011 05:35:14 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 4BD9C3A680F for <avt@ietf.org>; Sat, 26 Mar 2011 05:35:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=abegen@cisco.com; l=2612; q=dns/txt; s=iport; t=1301143010; x=1302352610; h=subject:references:content-transfer-encoding:from: in-reply-to:message-id:date:to:cc:mime-version; bh=/6vpa1UKTI1Qy/jSfvQh2bwE+kqoUfwyMya/YDJe2b4=; b=SPq8ZR1sgvxPLEvTqCKCNCZfLNDUzfAENJPuJVGdV1OFwofNfSaanMVp nkpMAu+SfA47vYp5g1Ns+0lmYUbq8tCeV3tUs3NnBHQQxUgENJrRCfRGL mMjFPs58djShpWGC2oHrLV9SaDcYMKYLCcR8FsTc7dy8UzQTe6M/WRtrm c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhsGAI7djU2rRDoG/2dsb2JhbACDf0agOGQCd4hrnWCLO5BRAoElg0t3BIx1g1qFTg
X-IronPort-AV: E=Sophos;i="4.63,247,1299456000"; d="scan'208";a="418696220"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-1.cisco.com with ESMTP; 26 Mar 2011 12:36:50 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p2QCao8G025092; Sat, 26 Mar 2011 12:36:50 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);  Sat, 26 Mar 2011 05:36:50 -0700
Received: from 128.107.191.32 ([128.107.191.32]) by xmb-sjc-215.amer.cisco.com ([171.70.151.169]) with Microsoft Exchange Server HTTP-DAV ;  Sat, 26 Mar 2011 12:36:49 +0000
References: <4D8DBEDB.4090406@ericsson.com>
Content-Transfer-Encoding: base64
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
Content-Type: text/plain; charset="utf-8"
In-Reply-To: <4D8DBEDB.4090406@ericsson.com>
Thread-Topic: [AVTCORE] Comments ondraft-vancaenegem-avtcore-fb-supp-and-retransm-00
Thread-Index: AcvrsnpKwM+YoGedQ+WAMmbOk5yy2Q==
Message-ID: <DD7F45DE-A43D-40B3-8B6D-DCF5C3C5E539@cisco.com>
Date: Sat, 26 Mar 2011 13:36:45 +0100
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
MIME-Version: 1.0 (iPhone Mail 8F190)
X-OriginalArrivalTime: 26 Mar 2011 12:36:50.0371 (UTC) FILETIME=[7A987930:01CBEBB2]
Cc: VAN CAENEGEM Tom <Tom.Van_Caenegem@alcatel-lucent.com>, IETF AVTCore WG <avt@ietf.org>
Subject: Re: [AVTCORE] Comments ondraft-vancaenegem-avtcore-fb-supp-and-retransm-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Mar 2011 12:35:17 -0000

DQoNCk9uIE1hciAyNiwgMjAxMSwgYXQgMTE6MjUgQU0sICJNYWdudXMgV2VzdGVybHVuZCIgPG1h
Z251cy53ZXN0ZXJsdW5kQGVyaWNzc29uLmNvbT4gd3JvdGU6DQoNCj4gVG9tLCBBVlRDT1JFLA0K
PiANCj4gSSBoYXZlIHJldmlld2VkIHRoaXMgZHJhZnQgYW5kIGhhdmUgdGhlIGZvbGxvd2luZyBj
b21tZW50Lg0KPiANCj4gVG8gbWUgaXQgYXBwZWFycyB0aGF0IG9uZSBiaWcgcmVhc29uIGZvciB0
aGUgaXNzdWVzIGlzIGFjdHVhbGx5IHRoYXQgd2UNCj4gaGF2ZW4ndCBzcGVjaWZpZWQgaG93IFJU
UCByZXRyYW5zbWlzc2lvbiBpbiBTU00gd2l0aCB1bmljYXN0IGRlbGl2ZXJ5IGlzDQo+IHN1cHBv
c2VkIHRvIHdvcmsuIEJlY2F1c2UgaWYgdGhhdCB3YXMgd2VsbCBkZWZpbmVkIHdlIHdvdWxkIGxp
a2VseSBoYXZlDQo+IGNvbmNsdWRlZCB0aGF0IG9uZSBzaG91bGQgbm90IGZvcndhcmQgTkFDSyBy
ZXF1ZXN0IHRvIHRoZSBEUyBmcm9tIGEgRlQNCj4gZm9yIGFueSByZXF1ZXN0IGl0IHNlcnZpY2Ug
bG9jYWxseS4NCj4gDQo+IFRodXMgYXMgSSByYWlzZWQgYmVmb3JlIGluIHJlbGF0aW9uIHRvIHRo
ZSBSQU1TIHdvcmsgdGhhdCB0aGVyZSBhcHBlYXJlZA0KPiB0byBiZSBhIG5lZWQgZm9yIGRlZmlu
aW5nIHRoaXMgcHJvcGVybHksIGluY2x1ZGluZyB0aGlzIGFzcGVjdC4gRG8gd2UNCj4gaGF2ZSBh
bnlvbmUgdGhhdCBpcyBpbnRlcmVzdGVkIGluIGRlZmluaW5nIHRoaXM/DQo+IA0KUHJldmlvdXNs
eSBJIG9mZmVyZWQgbXkgbmFtZSBmb3IgdGhpcy4gQW5kIGlmIHdlIHRoaW5rIHdlIHNob3VsZCBk
byB0aGlzLCBJIGNhbiAgaGVscCBkcmFmdGluZyBpdC4gV2UgaGFkIHF1aXRlIGEgYml0IGV4cGVy
aWVuY2UgaW4gdGhpcyB3aXRoIHJhbXMuIA0KDQotYWNiZWdlbg0KDQo+IFNlY29uZGx5IEkgdGhp
bmsgdGhlcmUgY2xlYXJseSBhcmUgc29tZSBpbXByb3ZlbWVudHMgbmVlZGVkIG9mIHRoZSBXRw0K
PiBkb2N1bWVudCBiYXNlZCBvbiB3aGF0IHlvdSBjb21tZW50LiBPbmUgdGhpbmcgaXMgY2xlYXJs
eSB0byBjbGFyaWZ5IHRoZQ0KPiBXRyBkb2N1bWVudCBvbiBpdHMgdXNhZ2VzLCBhbmQgdGhlbiBt
YXAgdGhvc2UgdXNhZ2VzIG9mIHN1cHByZXNzaW9uIHRvDQo+IGRpZmZlcmVudCB0b3BvbG9naWVz
Lg0KPiANCj4gTXkgcGVyc29uYWwgb3BpbmlvbiBvbiBob3cgdG8gaGFuZGxlIHlvdXIgY29tbWVu
dHMgYXJlIHRvIGluY2x1ZGUgeW91cg0KPiBjb25jZXJucyBpbiB0aGUgV0cgZG9jdW1lbnQuDQo+
IA0KPiBDaGVlcnMNCj4gDQo+IE1hZ251cyBXZXN0ZXJsdW5kDQo+IA0KPiAtLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
DQo+IE11bHRpbWVkaWEgVGVjaG5vbG9naWVzLCBFcmljc3NvbiBSZXNlYXJjaCBFQUIvVFZNDQo+
IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0NCj4gRXJpY3Nzb24gQUIgICAgICAgICAgICAgICAgfCBQaG9uZSAgKzQ2
IDEwIDcxNDgyODcNCj4gRsOkcsO2Z2F0YW4gNiAgICAgICAgICAgICAgICB8IE1vYmlsZSArNDYg
NzMgMDk0OTA3OQ0KPiBTRS0xNjQgODAgU3RvY2tob2xtLCBTd2VkZW58IG1haWx0bzogbWFnbnVz
Lndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tDQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gQXVkaW8vVmlkZW8gVHJhbnNw
b3J0IENvcmUgTWFpbnRlbmFuY2UNCj4gYXZ0QGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vYXZ0DQo=

From sunseawq@huawei.com  Sat Mar 26 07:17:31 2011
Return-Path: <sunseawq@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9EF1728C0D8 for <avt@core3.amsl.com>; Sat, 26 Mar 2011 07:17:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  MIME_BASE64_BLANKS=0.041, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QWn7MPy5-FMk for <avt@core3.amsl.com>; Sat, 26 Mar 2011 07:17:30 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 42A1328C0D7 for <avt@ietf.org>; Sat, 26 Mar 2011 07:17:26 -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 <0LIO0069853FYG@szxga03-in.huawei.com> for avt@ietf.org; Sat, 26 Mar 2011 22:18:51 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LIO009LZ53F42@szxga03-in.huawei.com> for avt@ietf.org; Sat, 26 Mar 2011 22:18:51 +0800 (CST)
Received: from jys1037575 (19.218.broadband.iol.cz [80.188.218.19]) by szxml11-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LIO000BW52W35@szxml11-in.huawei.com>; Sat, 26 Mar 2011 22:18:51 +0800 (CST)
Date: Sat, 26 Mar 2011 15:18:30 +0100
From: Qin Wu <sunseawq@huawei.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, IETF AVTCore WG <avt@ietf.org>, VAN CAENEGEM Tom <Tom.Van_Caenegem@alcatel-lucent.com>
Message-id: <5F141A015792424CA17CE056377BF64D@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
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
References: <4D8DBEDB.4090406@ericsson.com>
Subject: Re: [AVTCORE] Comments on	draft-vancaenegem-avtcore-fb-supp-and-retransm-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Mar 2011 14:17:31 -0000

SGksTWFnbnVzLCBhbGw6DQpUaGFuayBmb3IgcmFpc2luZyBkaXNjdXNzaW9uIG9uIHNvbWUgb2Yg
dGhlc2UgaXNzdWVzLg0KUGxlYXNlIHNlZSBjb21tZW50cyBpbmxpbmUuDQoNClJlZ2FyZHMhDQot
UWluDQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIk1hZ251cyBXZXN0ZXJs
dW5kIiA8bWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tPg0KVG86ICJJRVRGIEFWVENvcmUg
V0ciIDxhdnRAaWV0Zi5vcmc+OyAiVkFOIENBRU5FR0VNIFRvbSIgPFRvbS5WYW5fQ2FlbmVnZW1A
YWxjYXRlbC1sdWNlbnQuY29tPg0KU2VudDogU2F0dXJkYXksIE1hcmNoIDI2LCAyMDExIDExOjI0
IEFNDQpTdWJqZWN0OiBbQVZUQ09SRV0gQ29tbWVudHMgb24gZHJhZnQtdmFuY2FlbmVnZW0tYXZ0
Y29yZS1mYi1zdXBwLWFuZC1yZXRyYW5zbS0wMA0KDQoNClRvbSwgQVZUQ09SRSwNCg0KSSBoYXZl
IHJldmlld2VkIHRoaXMgZHJhZnQgYW5kIGhhdmUgdGhlIGZvbGxvd2luZyBjb21tZW50Lg0KDQpU
byBtZSBpdCBhcHBlYXJzIHRoYXQgb25lIGJpZyByZWFzb24gZm9yIHRoZSBpc3N1ZXMgaXMgYWN0
dWFsbHkgdGhhdCB3ZQ0KaGF2ZW4ndCBzcGVjaWZpZWQgaG93IFJUUCByZXRyYW5zbWlzc2lvbiBp
biBTU00gd2l0aCB1bmljYXN0IGRlbGl2ZXJ5IGlzDQpzdXBwb3NlZCB0byB3b3JrLiBCZWNhdXNl
IGlmIHRoYXQgd2FzIHdlbGwgZGVmaW5lZCB3ZSB3b3VsZCBsaWtlbHkgaGF2ZQ0KY29uY2x1ZGVk
IHRoYXQgb25lIHNob3VsZCBub3QgZm9yd2FyZCBOQUNLIHJlcXVlc3QgdG8gdGhlIERTIGZyb20g
YSBGVA0KZm9yIGFueSByZXF1ZXN0IGl0IHNlcnZpY2UgbG9jYWxseS4NCg0KW1Fpbl06IEFncmVl
Lg0KDQpUaHVzIGFzIEkgcmFpc2VkIGJlZm9yZSBpbiByZWxhdGlvbiB0byB0aGUgUkFNUyB3b3Jr
IHRoYXQgdGhlcmUgYXBwZWFyZWQNCnRvIGJlIGEgbmVlZCBmb3IgZGVmaW5pbmcgdGhpcyBwcm9w
ZXJseSwgaW5jbHVkaW5nIHRoaXMgYXNwZWN0LiBEbyB3ZQ0KaGF2ZSBhbnlvbmUgdGhhdCBpcyBp
bnRlcmVzdGVkIGluIGRlZmluaW5nIHRoaXM/DQoNCltRaW5dOiBZZXMsIEkgY2FuIGhlbHAgd2l0
aCB0aGlzIGlmIGl0IGRvZXMgd29ydGggYmVpbmcgZGVmaW5lZC4NCldlIGhhdmUgb25lIFJBTVMg
dXNlIGNhc2UgaW4gZHJhZnQtaWV0Zi1hdnRjb3JlLWZlZWRiYWNrLXN1cHByZXNzaW9uIHdoaWNo
IGJyaWVmbHkgZGlzY3VzcyBob3cNCnRvIGRlYWwgd2l0aCB0aGUgc2Vjb25kIGxvc3MgZHVlIHRv
IHJldHJhbWlzc2lvbi4gSSBiZWxpZXZlIGl0IGlzIHJlbGV2YW50IGFuZCB3b3VsZCBsaWtlIHRv
IGRyYXcgeW91ciBhdHRlbnRpb24uDQoNCg0KU2Vjb25kbHkgSSB0aGluayB0aGVyZSBjbGVhcmx5
IGFyZSBzb21lIGltcHJvdmVtZW50cyBuZWVkZWQgb2YgdGhlIFdHDQpkb2N1bWVudCBiYXNlZCBv
biB3aGF0IHlvdSBjb21tZW50LiBPbmUgdGhpbmcgaXMgY2xlYXJseSB0byBjbGFyaWZ5IHRoZQ0K
V0cgZG9jdW1lbnQgb24gaXRzIHVzYWdlcywgYW5kIHRoZW4gbWFwIHRob3NlIHVzYWdlcyBvZiBz
dXBwcmVzc2lvbiB0bw0KZGlmZmVyZW50IHRvcG9sb2dpZXMuDQoNCltRaW5dOiBBcyBmb3IgU1NN
IHVzZSBjYXNlLCB0aGUgaW50ZXJlc3RpbmcgcGFydCBJIGNhbiBzZWUgaXMgc2VsZWN0aXZlIHJl
ZmxlY3Rpb24NCmFuZCBzZWxlY3RpdmUgZm9yd2FyZCBkZXNjcmliZWQgaW4gdGhpcyBkcmFmdC4g
SXQgbG9va3MgbGlrZSBzb21lIGltcHJvdmVtZW50IHRoYXQgbmVlZHMgV0cgZG9jdW1lbnQNCnRv
IHRha2UgYSBsb29rIGF0LiBJIHdvdWxkIGxpa2UgdG8gZHJhdyBXRyB0byBwYXkgYXR0ZW50aW9u
IHRvIHRoZXNlLg0KdG8gc2VlIGFueSB0cmFkZW9mZiBuZWVkZWQgZm9yIHRoZSBXRyBkb2N1bWVu
dD8NCg0KTXkgcGVyc29uYWwgb3BpbmlvbiBvbiBob3cgdG8gaGFuZGxlIHlvdXIgY29tbWVudHMg
YXJlIHRvIGluY2x1ZGUgeW91cg0KY29uY2VybnMgaW4gdGhlIFdHIGRvY3VtZW50Lg0KDQpDaGVl
cnMNCg0KTWFnbnVzIFdlc3Rlcmx1bmQNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KTXVsdGltZWRpYSBUZWNo
bm9sb2dpZXMsIEVyaWNzc29uIFJlc2VhcmNoIEVBQi9UVk0NCi0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCkVyaWNz
c29uIEFCICAgICAgICAgICAgICAgIHwgUGhvbmUgICs0NiAxMCA3MTQ4Mjg3DQpG5HL2Z2F0YW4g
NiAgICAgICAgICAgICAgICB8IE1vYmlsZSArNDYgNzMgMDk0OTA3OQ0KU0UtMTY0IDgwIFN0b2Nr
aG9sbSwgU3dlZGVufCBtYWlsdG86IG1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29uLmNvbQ0KLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLQ0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18NCkF1ZGlvL1ZpZGVvIFRyYW5zcG9ydCBDb3JlIE1haW50ZW5hbmNlDQphdnRAaWV0Zi5vcmcN
Cmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vYXZ0DQo=



From tom.van_caenegem@alcatel-lucent.com  Sat Mar 26 10:14:53 2011
Return-Path: <tom.van_caenegem@alcatel-lucent.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A52EF3A67D7 for <avt@core3.amsl.com>; Sat, 26 Mar 2011 10:14:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.963
X-Spam-Level: 
X-Spam-Status: No, score=-5.963 tagged_above=-999 required=5 tests=[AWL=0.286,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wLYjecTUrf47 for <avt@core3.amsl.com>; Sat, 26 Mar 2011 10:14:52 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id 7969B3A67D0 for <avt@ietf.org>; Sat, 26 Mar 2011 10:14:52 -0700 (PDT)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p2QHGOSs021931 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sat, 26 Mar 2011 18:16:25 +0100
Received: from FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com ([135.120.45.43]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Sat, 26 Mar 2011 18:16:24 +0100
From: "Van Caenegem, Tom (Tom)" <tom.van_caenegem@alcatel-lucent.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, IETF AVTCore WG <avt@ietf.org>
Date: Sat, 26 Mar 2011 18:16:23 +0100
Thread-Topic: Comments on draft-vancaenegem-avtcore-fb-supp-and-retransm-00
Thread-Index: AcvroAAE/GyomVmjSPC8hsv8rHmwaAAN32pQ
Message-ID: <EC3FD58E75D43A4F8807FDE074917546171962C4@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
References: <4D8DBEDB.4090406@ericsson.com>
In-Reply-To: <4D8DBEDB.4090406@ericsson.com>
Accept-Language: nl-NL, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: nl-NL, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Subject: Re: [AVTCORE] Comments on draft-vancaenegem-avtcore-fb-supp-and-retransm-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Mar 2011 17:14:53 -0000

Hi Magnus,

Thanks you for reviewing the draft and the comments.

The main initial reason I submitted this draft was to provide some structur=
ed feedback on the existing WG draft document http://tools.ietf.org/html/dr=
aft-wu-avt-retransmission-supression-rtp-08 . I must say  I am still quite =
puzzled how a WG item can address FB suppression for multiparty session wit=
hout even mentioning the existing AVTF suppression rule of RFC 4585.=20
But as I tackled the topic with focus on SSM, it became apparent to me that=
 FB suppression and the actions triggered or system knowledge gathered on t=
he basis of RTCP FB messages need to be addressed together. In this draft I=
 focus on the impact of FB supression on the retransmission action/service =
(but this could be easily made more generic).=20
So, I agree with you that this draft has material that should be addressed =
in the scope of the FB suppression/3rd party loss WG item, and it could als=
o be fed into a WG item addresssing "retransmission" in SSM. But it is a fa=
ct that RAMS does cover some retransmission aspects as well. We need to see=
 how we address this.

Tom =20
=20

-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]=20
Sent: zaterdag 26 maart 2011 11:24
To: IETF AVTCore WG; Van Caenegem, Tom (Tom)
Subject: Comments on draft-vancaenegem-avtcore-fb-supp-and-retransm-00

Tom, AVTCORE,

I have reviewed this draft and have the following comment.

To me it appears that one big reason for the issues is actually that we hav=
en't specified how RTP retransmission in SSM with unicast delivery is suppo=
sed to work. Because if that was well defined we would likely have conclude=
d that one should not forward NACK request to the DS from a FT for any requ=
est it service locally.

Thus as I raised before in relation to the RAMS work that there appeared to=
 be a need for defining this properly, including this aspect. Do we have an=
yone that is interested in defining this?

Secondly I think there clearly are some improvements needed of the WG docum=
ent based on what you comment. One thing is clearly to clarify the WG docum=
ent on its usages, and then map those usages of suppression to different to=
pologies.

My personal opinion on how to handle your comments are to include your conc=
erns in the WG document.

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 mzanaty@cisco.com  Sat Mar 26 21:21:21 2011
Return-Path: <mzanaty@cisco.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A77003A689A; Sat, 26 Mar 2011 21:21:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.998
X-Spam-Level: 
X-Spam-Status: No, score=-9.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z-O37E7-IJRb; Sat, 26 Mar 2011 21:21:08 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 90B093A68B0; Sat, 26 Mar 2011 21:21:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mzanaty@cisco.com; l=47621; q=dns/txt; s=iport; t=1301199765; x=1302409365; h=mime-version:subject:date:message-id:from:to:cc; bh=smy0kyrYbGLzdKsutnzXoXbv/Egyj3Nkb5pozoZVReQ=; b=CNHN4+m3mgdjYBSlPUzNsBi0eENyO93aPrn8M4/Rz8fDbJYvRGyORVAd O113mx/aoVSDjYKmWk+pIdKC5rPt98JBjrbQTF9b/KGs2+7Tc4g3oWX1U vPOKK642Hi1VvaFByEeQf8yaGCldfvCuus3tSxGTk5MOowcEOuOlXuANw 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AusAAAi7jk2tJXHB/2dsb2JhbACCYJVJjTx3p1+ae4VpBIU6ixc
X-IronPort-AV: E=Sophos;i="4.63,249,1299456000";  d="scan'208,217";a="281506558"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by sj-iport-4.cisco.com with ESMTP; 27 Mar 2011 04:22:44 +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 p2R4Mhuo024360;  Sun, 27 Mar 2011 04:22:43 GMT
Received: from xmb-rcd-201.cisco.com ([72.163.62.208]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 26 Mar 2011 23:22:44 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBEC36.9E4B4891"
Date: Sat, 26 Mar 2011 23:22:42 -0500
Message-ID: <B2DE0AFA86565C47BD3A8435550F9553030CFF66@XMB-RCD-201.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Some changes to rfc3984bis, SVC, and RCDO payload drafts
Thread-Index: Acvm161AAF2A6AC0R/ODLEMZyh1IcgAwzyEAAIkXUFAAnXzNcA==
From: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
To: "Ye-Kui Wang" <yekui.wang@huawei.com>, <payload@ietf.org>, <avt@ietf.org>
X-OriginalArrivalTime: 27 Mar 2011 04:22:44.0030 (UTC) FILETIME=[9E6995E0:01CBEC36]
Cc: Gary Sullivan <garysull@microsoft.com>, Stephen Botzko <stephen.botzko@gmail.com>, Roni Even <Even.roni@huawei.com>
Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Mar 2011 04:21:21 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBEC36.9E4B4891
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The proposed changes to max-dpb, max-cpb and max-br sacrifice some
backward compatibility with RFC 3984 and forward compatibility with
H.264. The latter seems intentional but the former seems unintentional.
Further changes are needed to fix or clearly convey these
incompatibilities.

=20

What was discussed and decided regarding max-dpb, max-cpb and max-br in
the ITU/IETF F2F meetings? Based on the original suggested changes (at
the end without color coding), forward compatibility with H.264 appears
to be the focus. But after "further discussions", the newest suggested
changes (with color coding) appear focused on backward compatibility
with RFC 3984, but don't fully achieve this.

=20

The problem with RFC 3984 backward compatibility is that changing the
units of max-dpb (from 1024 bytes to 8/3 macroblocks) only works for the
4:2:0 chroma format, which is the primary format used in most profiles
and applications. However, the high profiles support other chroma
formats, and this change breaks backward compatibility for them.

=20

For example, consider an RFC 3984 implementation that declares
max-dpb=3D8100 (KB) to support 3 reference frames of 720p at 4:4:4. The
proposed change would misinterpret this declaration to mean 6 reference
frames of 720p at any chroma format including 4:4:4, hence potentially
overflowing the old RFC 3984 receiver's DPB by a factor of 2.

=20

(Note that H.264 got away with changing MaxDPB since the original 2003
version only supported 4:2:0. When the high profiles which support other
chroma formats were added in 2005, MaxDPB was explicitly redefined in
terms of 4:2:0 so it remains constant across all chroma formats. For
further clarity, MaxDpbMbs later replaced MaxDPB. But RFC 3984 never
kept up with these changes, so implementations are stuck with the 2003
definitions even for later features such as the high profiles and other
chroma formats.)

=20

The problem with H.264 forward compatibility is that NOT changing the
units of max-cpb and max-br for the high profiles (to include the
scaling factors 1.25/3/4) obviously creates confusion and
incompatibility between H.264 and this bis draft. This seems like an
intentional change after "further discussions" decided to focus on RFC
3984 backward compatibility at the expense of H.264 forward
compatibility.

=20

Before deciding on specific new text, the WG should decide on whether
the focus of this draft should be backward compatibility with RFC 3984
or forward compatibility with H.264. Or if the intent is to strike some
balance between the two, then clearly convey the intentional
incompatibilities in the text.

=20

Regards,

Mo Zanaty

=20

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Ye-Kui Wang
Sent: Monday, March 21, 2011 4:11 AM
To: payload@ietf.org; avt@ietf.org
Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC,and RCDO payload
drafts

=20

Further discussions with the same group of persons led to a decision to
stay with the unscaled units for max-br and max-cpb, thus fewer changes
are needed to the three payload formats listed in the title and H.241.
With this, the changes needed are listed below (the originally suggested
changes are dropped from this email). This time I have highlighted the
changes, and I have also described the nature the changes below. Hope
these may help understand better what have been changed, and can lead to
a quicker decision by the group, including WG chairs, and our AD.

=20

BR, YK

=20

------------------------------------Start of suggested changes
--------------------------------------

=20

Section 8.1:

OLD:

      max-dpb: The value of max-dpb is an integer indicating the maximum

         decoded picture buffer size in units of 1024 bytes.  The max-

         dpb parameter signals that the receiver has more memory than

         the minimum amount of decoded picture buffer memory required by

         the signaled highest level conveyed in the value of the

         profile-level-id parameter or the max-recv-level parameter.

         When max-dpb is signaled, the receiver MUST be able to decode

         NAL unit streams that conform to the signaled highest level,

         with the exception that the MaxDPB value in Table A-1 of [1]

         for the signaled highest level is replaced with the value of

         max-dpb.  Consequently, a receiver that signals max-dpb MUST be

         capable of storing the following number of decoded frames,

         complementary field pairs, and non-paired fields in its decoded

         picture buffer:

=20

            Min(1024 * max-dpb / ( PicWidthInMbs * FrameHeightInMbs *

            256 * ChromaFormatFactor ), 16)

=20

         PicWidthInMbs, FrameHeightInMbs, and ChromaFormatFactor are

         defined in [1].

=20

         The value of max-dpb MUST be greater than or equal to the value

         of MaxDPB given in Table A-1 of [1] for the highest level.

         Senders MAY use this knowledge to construct coded video streams

         with improved compression.

NEW: (When this change can be considered as editorial can be discussed,
but the nature of this change as follows. On the other hand, if not
changed, then the semantics of max-dpb is simply equivalent to
unspecified, as MaxDPB and ChromaFormatFactor are not found in the
latest H.264 spec any more. Note that compared to RFC 3984, the bits on
the wire do not change.)

      max-dpb: The value of max-dpb is an integer indicating the maximum

         decoded picture buffer size in units of 8/3 macroblocks.  The
max-

         dpb parameter signals that the receiver has more memory than

         the minimum amount of decoded picture buffer memory required by

         the signaled highest level conveyed in the value of the

         profile-level-id parameter or the max-recv-level parameter.

         When max-dpb is signaled, the receiver MUST be able to decode

         NAL unit streams that conform to the signaled highest level,

         with the exception that the MaxDpbMbs value in Table A-1 of [1]

         for the signaled highest level is replaced with the value of

         max-dpb * 3 / 8.  Consequently, a receiver that signals max-dpb
MUST be

         capable of storing the following number of decoded frames,

         complementary field pairs, and non-paired fields in its decoded

         picture buffer:

=20

            Min(max-dpb * 3 / 8 / ( PicWidthInMbs * FrameHeightInMbs),
16)

=20

         Wherein PicWidthInMbs and FrameHeightInMbs are defined in [1].

=20

         The value of max-dpb MUST be greater than or equal to the value

         of MaxDpbMbs * 3 / 8, wherein the value of MaxDpbMbs is given
in=20

Table A-1 of [1] for the highest level.

         Senders MAY use this knowledge to construct coded video streams

         with improved compression.

=20

=20

------------------------------------End of suggested changes
--------------------------------------

=20

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Ye-Kui Wang
Sent: Sunday, March 20, 2011 4:21 AM
To: payload@ietf.org; avt@ietf.org
Subject: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload
drafts

=20

Folks,

=20

The three H.264/AVC related payload formats, namely,
draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-rtp-svc-27, and
draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48 stage.

=20

The RFC-Editor has found the following problem: In
draft-ietf-avt-rtp-rfc3984bis-12, the definition of the max-dpb media
parameter refers to the MaxDPB that was defined the first version of the
H.264/AVC spec, but not any more in the latest version (the 2010
version). The parameter in the latest H.264/AVC version corresponding to
MaxDPB is MaxDpbMbs, and the unit of the new parameter (i.e.,
macroblocks) is different from the original one (i.e. 1024 bytes).

=20

The problem applies also to the SVC payload format, the RCDO payload
format, and H.241.

=20

A solution has been found and agreed, involving rfc3984bis authors and
some key people related to H.264/AVC (e.g., Gary Sullivan and Heiko
Schwarz) and H.241 (e.g., Stephen Botzko and Patrick Luthi).
Furthermore, we have found that there are also a couple of places that
need fixes due to similar changes from the initial version of H.264/AVC
to the latest version.

=20

Per Roni's suggestion, I am sending in below the changes to
draft-ietf-avt-rtp-rfc3984bis-12 for review by the Payload and AVTcore
WGs. It seems that exactly the same changes are needed to
draft-ietf-avt-rtp-h264-rcdo-08 (co-authors of this draft may confirm),
and similar but slightly different changes are needed to
draft-ietf-avt-rtp-svc-27.

=20

Since the drafts are at the AUTH48 stage, please provide comments by
Monday, March 21, if any. Many thanks!

=20

BR, YK

=20

=20

------------------------------------Start of suggested changes
--------------------------------------

=20

Section 8.1:

OLD:

      max-cpb: The value of max-cpb is an integer indicating the maximum

         coded picture buffer size in units of 1000 bits for the VCL HRD

         parameters (see A.3.1, item i of [1]) and in units of 1200 bits

         for the NAL HRD parameters (see A.3.1, item j of [1]).

NEW:

      max-cpb: The value of max-cpb is an integer indicating the maximum

         coded picture buffer size. For Constrained Baseline, Baseline,
Main=20

and Extended profiles, the unit is 1000 bits for the VCL HRD

         parameters and 1200 bits for the NAL HRD parameters. For High,
High 10,

High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra,=20

High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles, the unit is
cpbBrVclFactor

bits for the VCL HRD and cpbBrNalFactor bits for the NAL HRD parameters.

=20

OLD:

      max-br: The value of max-br is an integer indicating the maximum
         video bitrate in units of 1000 bits per second for the VCL HRD
         parameters (see A.3.1, item i of [1]) and in units of 1200 bits
         per second for the NAL HRD parameters (see A.3.1, item j of
         [1]).

NEW:=20

      max-br: The value of max-br is an integer indicating the maximum

         video bitrate.  For Constrained Baseline, Baseline, Main=20

and Extended profiles, the unit is 1000 bits per second for the VCL HRD

         parameters and 1200 bits per second for the NAL HRD parameters.
For High, High 10,

High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra,=20

High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles, the unit is
cpbBrVclFactor

bits per second for the VCL HRD and cpbBrNalFactor bits per second for
the NAL HRD parameters.

=20

------------------------------------End of suggested changes
--------------------------------------

=20

=20


------_=_NextPart_001_01CBEC36.9E4B4891
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;
	text-align:justify;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:SimSun;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:SimSun;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle27
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@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=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple style=3D'text-justify-trim:punctuation'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt'>The proposed changes to max-dpb, max-cpb and =
max-br sacrifice some backward compatibility with RFC 3984 and forward =
compatibility with H.264. The latter seems intentional but the former =
seems unintentional. Further changes are needed to fix or clearly convey =
these incompatibilities.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:11.0pt'>What was discussed =
and decided regarding max-dpb, max-cpb and max-br in the ITU/IETF F2F =
meetings? Based on the original suggested changes (at the end without =
color coding), forward compatibility with H.264 appears to be the focus. =
But after &#8220;further discussions&#8221;, the newest suggested =
changes (with color coding) appear focused on backward compatibility =
with RFC 3984, but don&#8217;t fully achieve =
this.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:11.0pt'>The problem with RFC =
3984 backward compatibility is that changing the units of max-dpb (from =
1024 bytes to 8/3 macroblocks) only works for the 4:2:0 chroma format, =
which is the primary format used in most profiles and applications. =
However, the high profiles support other chroma formats, and this change =
breaks backward compatibility for them.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:11.0pt'>For example, consider =
an RFC 3984 implementation that declares max-dpb=3D8100 (KB) to support =
3 reference frames of 720p at 4:4:4. The proposed change would =
misinterpret this declaration to mean 6 reference frames of 720p at any =
chroma format including 4:4:4, hence potentially overflowing the old RFC =
3984 receiver&#8217;s DPB by a factor of 2.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:11.0pt'>(Note that H.264 got =
away with changing MaxDPB since the original 2003 version only supported =
4:2:0. When the high profiles which support other chroma formats were =
added in 2005, MaxDPB was explicitly redefined in terms of 4:2:0 so it =
remains constant across all chroma formats. For further clarity, =
MaxDpbMbs later replaced MaxDPB. But RFC 3984 never kept up with these =
changes, so implementations are stuck with the 2003 definitions even for =
later features such as the high profiles and other chroma =
formats.)<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:11.0pt'>The problem with =
H.264 forward compatibility is that NOT changing the units of max-cpb =
and max-br for the high profiles (to include the scaling factors =
1.25/3/4) obviously creates confusion and incompatibility between H.264 =
and this bis draft. This seems like an intentional change after =
&#8220;further discussions&#8221; decided to focus on RFC 3984 backward =
compatibility at the expense of H.264 forward =
compatibility.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:11.0pt'>Before deciding on =
specific new text, the WG should decide on whether the focus of this =
draft should be backward compatibility with RFC 3984 or forward =
compatibility with H.264. Or if the intent is to strike some balance =
between the two, then clearly convey the intentional incompatibilities =
in the text.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt'>Regards,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:11.0pt'>Mo =
Zanaty<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] <b>On Behalf Of =
</b>Ye-Kui Wang<br><b>Sent:</b> Monday, March 21, 2011 4:11 =
AM<br><b>To:</b> payload@ietf.org; avt@ietf.org<br><b>Subject:</b> Re: =
[AVTCORE] Some changes to rfc3984bis, SVC,and RCDO payload =
drafts<o:p></o:p></span></p></div></div><p class=3DMsoNormal =
align=3Dleft style=3D'text-align:left'><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;mso-fareast-language:ZH-CN'>Further =
discussions with the same group of persons led to a decision to stay =
with the unscaled units for max-br and max-cpb, thus fewer changes are =
needed to the three payload formats listed in the title and H.241. With =
this, the changes needed are listed below (the originally suggested =
changes are dropped from this email). This time I have highlighted the =
changes, and I have also described the nature the changes below. Hope =
these may help understand better what have been changed, and can lead to =
a quicker decision by the group, including WG chairs, and our =
AD.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;mso-fareast-language:ZH-CN'><o:p>&nbsp;</o:p></=
span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;mso-fareast-language:ZH-CN'>BR, =
YK<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;mso-fareast-language:ZH-CN'><o:p>&nbsp;</o:p></=
span></p><p class=3DMsoPlainText><span =
style=3D'mso-fareast-language:ZH-CN'>------------------------------------=
Start of suggested changes =
--------------------------------------<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'mso-fareast-language:ZH-CN'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D;mso-fareast-language:ZH-CN'>Section =
8.1:<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D;mso-fareast-language:ZH-CN'>OLD:<o:p></o:p></span>=
</p><p class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-dpb: The value of max-dpb is an =
integer indicating the maximum<o:p></o:p></span></p><p class=3DMsoNormal =
align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; decoded picture buffer =
size in units of 1024 bytes.&nbsp; The max-<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dpb parameter signals =
that the receiver has more memory than<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the minimum amount of =
decoded picture buffer memory required by<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the signaled highest =
level conveyed in the value of the<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; profile-level-id =
parameter or the max-recv-level parameter.<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When max-dpb is =
signaled, the receiver MUST be able to decode<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAL unit streams that =
conform to the signaled highest level,<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with the exception that =
the MaxDPB value in Table A-1 of [1]<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the signaled =
highest level is replaced with the value of<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-dpb.&nbsp; =
Consequently, a receiver that signals max-dpb MUST =
be<o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; capable of storing the =
following number of decoded frames,<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; complementary field =
pairs, and non-paired fields in its decoded<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; picture =
buffer:<o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Min(1024 * max-dpb / ( PicWidthInMbs * FrameHeightInMbs =
*<o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 256 * =
ChromaFormatFactor ), 16)<o:p></o:p></span></p><p class=3DMsoNormal =
align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PicWidthInMbs, =
FrameHeightInMbs, and ChromaFormatFactor are<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;defined in =
[1].<o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The value of max-dpb =
MUST be greater than or equal to the value<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of MaxDPB given in =
Table A-1 of [1] for the highest level.<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Senders MAY use this =
knowledge to construct coded video streams<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with improved =
compression.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D;mso-fareast-language:ZH-CN'>NEW: <span =
style=3D'background:aqua;mso-highlight:aqua'>(When this change can be =
considered as editorial can be discussed, but the nature of this change =
as follows. On the other hand, if not changed, then the semantics of =
max-dpb is simply equivalent to unspecified, as MaxDPB and =
ChromaFormatFactor are not found in the latest H.264 spec any more. Note =
that compared to RFC 3984, the bits on the wire do not =
change.)</span><o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-dpb: The value of max-dpb is an =
integer indicating the maximum<o:p></o:p></span></p><p class=3DMsoNormal =
align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; decoded picture buffer =
size in units of 8/3 macroblocks.&nbsp; The max-<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dpb parameter signals =
that the receiver has more memory than<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the minimum amount of =
decoded picture buffer memory required by<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the signaled highest =
level conveyed in the value of the<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; profile-level-id =
parameter or the max-recv-level parameter.<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When max-dpb is =
signaled, the receiver MUST be able to decode<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAL unit streams that =
conform to the signaled highest level,<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with the exception that =
<span style=3D'background:yellow;mso-highlight:yellow'>the MaxDpbMbs =
value in Table A-1 of [1]<o:p></o:p></span></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;background:yellow;mso-highli=
ght:yellow;mso-fareast-language:ZH-CN'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; for the signaled highest level is replaced with the value =
of<o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;background:yellow;mso-highli=
ght:yellow;mso-fareast-language:ZH-CN'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; max-dpb * 3 / 8</span><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
.&nbsp; Consequently, a receiver that signals max-dpb MUST =
be<o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; capable of storing the =
following number of decoded frames,<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; complementary field =
pairs, and non-paired fields in its decoded<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; picture =
buffer:<o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span =
style=3D'background:yellow;mso-highlight:yellow'>Min(max-dpb * 3 / 8 / ( =
PicWidthInMbs * FrameHeightInMbs), 16)<o:p></o:p></span></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;background:yellow;mso-highli=
ght:yellow;mso-fareast-language:ZH-CN'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;background:yellow;mso-highli=
ght:yellow;mso-fareast-language:ZH-CN'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; Wherein PicWidthInMbs and FrameHeightInMbs are defined in =
[1].</span><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
<o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The value of max-dpb =
MUST be greater than or equal to the value<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of <span =
style=3D'background:yellow;mso-highlight:yellow'>MaxDpbMbs * 3 / 8, =
wherein the value of MaxDpbMbs is given in =
<o:p></o:p></span></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;text-indent:.75in'><span =
style=3D'font-size:12.0pt;font-family:SimSun;background:yellow;mso-highli=
ght:yellow;mso-fareast-language:ZH-CN'>Table A-1 of [1] for the highest =
level.</span><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
<o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Senders MAY use this =
knowledge to construct coded video streams<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with improved =
compression.<o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D;mso-fareast-language:ZH-CN'><o:p>&nbsp;</o:p></spa=
n></p><p class=3DMsoPlainText><span =
style=3D'mso-fareast-language:ZH-CN'>------------------------------------=
End of suggested changes =
--------------------------------------<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D;mso-fareast-language:ZH-CN'><o:p>&nbsp;</o:p></spa=
n></p><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ZH-CN'>From:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ZH-CN'> avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] <b>On =
Behalf Of </b>Ye-Kui Wang<br><b>Sent:</b> Sunday, March 20, 2011 4:21 =
AM<br><b>To:</b> payload@ietf.org; avt@ietf.org<br><b>Subject:</b> =
[AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload =
drafts<o:p></o:p></span></p></div></div><p class=3DMsoNormal =
align=3Dleft style=3D'text-align:left'><span =
style=3D'mso-fareast-language:ZH-CN'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-fareast-language:ZH-CN'>Folks,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-fareast-language:ZH-CN'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'mso-fareast-language:ZH-CN'>The three =
H.264/AVC related payload formats, namely, =
draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-rtp-svc-27, and =
draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48 =
stage.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'mso-fareast-language:ZH-CN'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'mso-fareast-language:ZH-CN'>The =
RFC-Editor has found the following problem: In =
draft-ietf-avt-rtp-rfc3984bis-12, the definition of the max-dpb media =
parameter refers to the MaxDPB that was defined the first version of the =
H.264/AVC spec, but not any more in the latest version (the 2010 =
version). The parameter in the latest H.264/AVC version corresponding to =
MaxDPB is MaxDpbMbs, and the unit of the new parameter (i.e., =
macroblocks) is different from the original one (i.e. 1024 =
bytes).<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'mso-fareast-language:ZH-CN'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'mso-fareast-language:ZH-CN'>The problem =
applies also to the SVC payload format, the RCDO payload format, and =
H.241.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'mso-fareast-language:ZH-CN'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'mso-fareast-language:ZH-CN'>A solution =
has been found and agreed, involving rfc3984bis authors and some key =
people related to H.264/AVC (e.g., Gary Sullivan and Heiko Schwarz) and =
H.241 (e.g., Stephen Botzko and Patrick Luthi). Furthermore, we have =
found that there are also a couple of places that need fixes due to =
similar changes from the initial version of H.264/AVC to the latest =
version.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'mso-fareast-language:ZH-CN'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'mso-fareast-language:ZH-CN'>Per =
Roni&#8217;s suggestion, I am sending in below the changes to =
draft-ietf-avt-rtp-rfc3984bis-12 for review by the Payload and AVTcore =
WGs. It seems that exactly the same changes are needed to =
draft-ietf-avt-rtp-h264-rcdo-08 (co-authors of this draft may confirm), =
and similar but slightly different changes are needed to =
draft-ietf-avt-rtp-svc-27.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-fareast-language:ZH-CN'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'mso-fareast-language:ZH-CN'>Since the =
drafts are at the AUTH48 stage, please provide comments by Monday, March =
21, if any. Many thanks!<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'mso-fareast-language:ZH-CN'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'mso-fareast-language:ZH-CN'>BR, =
YK<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'mso-fareast-language:ZH-CN'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-fareast-language:ZH-CN'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'mso-fareast-language:ZH-CN'>------------------------------------=
Start of suggested changes =
--------------------------------------<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-fareast-language:ZH-CN'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D;mso-fareast-language:ZH-CN'>Section =
8.1:<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D;mso-fareast-language:ZH-CN'>OLD:<o:p></o:p></span>=
</p><p class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-cpb: The value of max-cpb is an =
integer indicating the maximum<o:p></o:p></span></p><p class=3DMsoNormal =
align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; coded picture buffer =
size in units of 1000 bits for the VCL HRD<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; parameters (see A.3.1, =
item i of [1]) and in units of 1200 bits<o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the NAL HRD =
parameters (see A.3.1, item j of [1]).<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D;mso-fareast-language:ZH-CN'>NEW:<o:p></o:p></span>=
</p><p class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-cpb: The value of max-cpb is an =
integer indicating the maximum<o:p></o:p></span></p><p class=3DMsoNormal =
align=3Dleft style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; coded picture buffer =
size. For Constrained Baseline, Baseline, Main <o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;text-indent:.75in'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
and Extended profiles, the unit is 1000 bits for the VCL =
HRD<o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; parameters and 1200 =
bits for the NAL HRD parameters. For High, High =
10,<o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;text-indent:.75in'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, =
<o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;text-indent:.75in'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles, the unit is =
cpbBrVclFactor<o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;text-indent:.75in'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
bits for the VCL HRD and cpbBrNalFactor bits for the NAL HRD =
parameters.<o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D;mso-fareast-language:ZH-CN'>OLD:<o:p></o:p></span>=
</p><pre><span =
style=3D'mso-fareast-language:ZH-CN'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
max-br: The value of max-br is an integer indicating the =
maximum<o:p></o:p></span></pre><pre><span =
style=3D'mso-fareast-language:ZH-CN'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; video bitrate in units of 1000 bits per second for the VCL =
HRD<o:p></o:p></span></pre><pre><span =
style=3D'mso-fareast-language:ZH-CN'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; parameters (see A.3.1, item i of [1]) and in units of 1200 =
bits<o:p></o:p></span></pre><pre><span =
style=3D'mso-fareast-language:ZH-CN'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; per second for the NAL HRD parameters (see A.3.1, item j =
of<o:p></o:p></span></pre><pre><span =
style=3D'mso-fareast-language:ZH-CN'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; [1]).<o:p></o:p></span></pre><p class=3DMsoNormal><span =
style=3D'color:#1F497D;mso-fareast-language:ZH-CN'>NEW: =
<o:p></o:p></span></p><pre><span =
style=3D'mso-fareast-language:ZH-CN'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
max-br: The value of max-br is an integer indicating the =
maximum<o:p></o:p></span></pre><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; video bitrate.&nbsp; =
For Constrained Baseline, Baseline, Main <o:p></o:p></span></p><p =
class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;text-indent:.75in'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
and Extended profiles, the unit is 1000 bits per second for the VCL =
HRD<o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; parameters and 1200 =
bits per second for the NAL HRD parameters. For High, High =
10,<o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;text-indent:.75in'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, =
<o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;text-indent:.75in'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles, the unit is =
cpbBrVclFactor<o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;text-indent:.75in'><span =
style=3D'font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN'>=
bits per second for the VCL HRD and cpbBrNalFactor bits per second for =
the NAL HRD parameters.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'mso-fareast-language:ZH-CN'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'mso-fareast-language:ZH-CN'>------------------------------------=
End of suggested changes =
--------------------------------------<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-fareast-language:ZH-CN'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;mso-fareast-language:ZH-CN'><o:p>&nbsp;</o:p></=
span></p></div></body></html>
------_=_NextPart_001_01CBEC36.9E4B4891--

From Even.roni@huawei.com  Sat Mar 26 22:23:18 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B5D243A6991; Sat, 26 Mar 2011 22:23:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.339
X-Spam-Level: 
X-Spam-Status: No, score=-97.339 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FRT_PROFILE1=2.555, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WhlhkNzp4E7L; Sat, 26 Mar 2011 22:23:03 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 6402E3A698E; Sat, 26 Mar 2011 22:23:02 -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 <0LIP00HTQB0Q82@szxga05-in.huawei.com>; Sun, 27 Mar 2011 13:24:26 +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 <0LIP0091LB0PSW@szxga05-in.huawei.com>; Sun, 27 Mar 2011 13:24:26 +0800 (CST)
Received: from windows8d787f9 (dhcp-4795.meeting.ietf.org [130.129.71.149]) by szxml12-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LIP000AKB092N@szxml12-in.huawei.com>; Sun, 27 Mar 2011 13:24:25 +0800 (CST)
Date: Sun, 27 Mar 2011 07:23:50 +0200
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <B2DE0AFA86565C47BD3A8435550F9553030CFF66@XMB-RCD-201.cisco.com>
To: "'Mo Zanaty (mzanaty)'" <mzanaty@cisco.com>, 'Ye-Kui Wang' <yekui.wang@huawei.com>, payload@ietf.org, avt@ietf.org
Message-id: <003501cbec3f$2d8448d0$888cda70$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_Y4Tbp7ToHbsmjs6ecv17SA)"
Content-language: en-us
Thread-index: Acvm161AAF2A6AC0R/ODLEMZyh1IcgAwzyEAAIkXUFAAnXzNcAACDXKA
iPlanet-SMTP-Warning: Lines longer than SMTP allows found and truncated.
References: <B2DE0AFA86565C47BD3A8435550F9553030CFF66@XMB-RCD-201.cisco.com>
Cc: 'Gary Sullivan' <garysull@microsoft.com>
Subject: Re: [AVTCORE] [payload]  Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Mar 2011 05:23:19 -0000

This is a multi-part message in MIME format.

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

HI Mo,

When the solution was discussed there are two assumptions

1.        Old implementations (RFC3984) expecting the maxdpb parameter in
kbyes only supported 4:2:0 8-bit and no other color because otherwise using
only Kbytes and not macro blocks will not work for them. 

2.       New implementation(RFC6184 - the assigned RFC number to 3984bis)
expects a value in macroblocks and will interpret the value in maxdpb as
macroblocks.

So see my comments inline

Roni Even

As individual

 

From: payload-bounces@ietf.org [mailto:payload-bounces@ietf.org] On Behalf
Of Mo Zanaty (mzanaty)
Sent: Sunday, March 27, 2011 6:23 AM
To: Ye-Kui Wang; payload@ietf.org; avt@ietf.org
Cc: Gary Sullivan; Roni Even
Subject: Re: [payload] [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO
payload drafts

 

The proposed changes to max-dpb, max-cpb and max-br sacrifice some backward
compatibility with RFC 3984 and forward compatibility with H.264. The latter
seems intentional but the former seems unintentional. Further changes are
needed to fix or clearly convey these incompatibilities.

 

What was discussed and decided regarding max-dpb, max-cpb and max-br in the
ITU/IETF F2F meetings? Based on the original suggested changes (at the end
without color coding), forward compatibility with H.264 appears to be the
focus. But after "further discussions", the newest suggested changes (with
color coding) appear focused on backward compatibility with RFC 3984, but
don't fully achieve this.

 

The problem with RFC 3984 backward compatibility is that changing the units
of max-dpb (from 1024 bytes to 8/3 macroblocks) only works for the 4:2:0
chroma format, which is the primary format used in most profiles and
applications. However, the high profiles support other chroma formats, and
this change breaks backward compatibility for them.

 

RE: See assumption 1

 

For example, consider an RFC 3984 implementation that declares max-dpb=8100
(KB) to support 3 reference frames of 720p at 4:4:4. The proposed change
would misinterpret this declaration to mean 6 reference frames of 720p at
any chroma format including 4:4:4, hence potentially overflowing the old RFC
3984 receiver's DPB by a factor of 2.

 

RE: if the system is old it will calculate the KB and will not start from
MBs and convert. Also we have assumption 1.

 

(Note that H.264 got away with changing MaxDPB since the original 2003
version only supported 4:2:0. When the high profiles which support other
chroma formats were added in 2005, MaxDPB was explicitly redefined in terms
of 4:2:0 so it remains constant across all chroma formats. For further
clarity, MaxDpbMbs later replaced MaxDPB. But RFC 3984 never kept up with
these changes, so implementations are stuck with the 2003 definitions even
for later features such as the high profiles and other chroma formats.)

 

RE: so this is why the two assumption are there.

 

The problem with H.264 forward compatibility is that NOT changing the units
of max-cpb and max-br for the high profiles (to include the scaling factors
1.25/3/4) obviously creates confusion and incompatibility between H.264 and
this bis draft. This seems like an intentional change after "further
discussions" decided to focus on RFC 3984 backward compatibility at the
expense of H.264 forward compatibility.

 

 

Before deciding on specific new text, the WG should decide on whether the
focus of this draft should be backward compatibility with RFC 3984 or
forward compatibility with H.264. Or if the intent is to strike some balance
between the two, then clearly convey the intentional incompatibilities in
the text.

 

Regards,

Mo Zanaty

 

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Ye-Kui
Wang
Sent: Monday, March 21, 2011 4:11 AM
To: payload@ietf.org; avt@ietf.org
Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC,and RCDO payload
drafts

 

Further discussions with the same group of persons led to a decision to stay
with the unscaled units for max-br and max-cpb, thus fewer changes are
needed to the three payload formats listed in the title and H.241. With
this, the changes needed are listed below (the originally suggested changes
are dropped from this email). This time I have highlighted the changes, and
I have also described the nature the changes below. Hope these may help
understand better what have been changed, and can lead to a quicker decision
by the group, including WG chairs, and our AD.

 

BR, YK

 

------------------------------------Start of suggested changes
--------------------------------------

 

Section 8.1:

OLD:

      max-dpb: The value of max-dpb is an integer indicating the maximum

         decoded picture buffer size in units of 1024 bytes.  The max-

         dpb parameter signals that the receiver has more memory than

         the minimum amount of decoded picture buffer memory required by

         the signaled highest level conveyed in the value of the

         profile-level-id parameter or the max-recv-level parameter.

         When max-dpb is signaled, the receiver MUST be able to decode

         NAL unit streams that conform to the signaled highest level,

         with the exception that the MaxDPB value in Table A-1 of [1]

         for the signaled highest level is replaced with the value of

         max-dpb.  Consequently, a receiver that signals max-dpb MUST be

         capable of storing the following number of decoded frames,

         complementary field pairs, and non-paired fields in its decoded

         picture buffer:

 

            Min(1024 * max-dpb / ( PicWidthInMbs * FrameHeightInMbs *

            256 * ChromaFormatFactor ), 16)

 

         PicWidthInMbs, FrameHeightInMbs, and ChromaFormatFactor are

         defined in [1].

 

         The value of max-dpb MUST be greater than or equal to the value

         of MaxDPB given in Table A-1 of [1] for the highest level.

         Senders MAY use this knowledge to construct coded video streams

         with improved compression.

NEW: (When this change can be considered as editorial can be discussed, but
the nature of this change as follows. On the other hand, if not changed,
then the semantics of max-dpb is simply equivalent to unspecified, as MaxDPB
and ChromaFormatFactor are not found in the latest H.264 spec any more. Note
that compared to RFC 3984, the bits on the wire do not change.)

      max-dpb: The value of max-dpb is an integer indicating the maximum

         decoded picture buffer size in units of 8/3 macroblocks.  The max-

         dpb parameter signals that the receiver has more memory than

         the minimum amount of decoded picture buffer memory required by

         the signaled highest level conveyed in the value of the

         profile-level-id parameter or the max-recv-level parameter.

         When max-dpb is signaled, the receiver MUST be able to decode

         NAL unit streams that conform to the signaled highest level,

         with the exception that the MaxDpbMbs value in Table A-1 of [1]

         for the signaled highest level is replaced with the value of

         max-dpb * 3 / 8.  Consequently, a receiver that signals max-dpb
MUST be

         capable of storing the following number of decoded frames,

         complementary field pairs, and non-paired fields in its decoded

         picture buffer:

 

            Min(max-dpb * 3 / 8 / ( PicWidthInMbs * FrameHeightInMbs), 16)

 

         Wherein PicWidthInMbs and FrameHeightInMbs are defined in [1].

 

         The value of max-dpb MUST be greater than or equal to the value

         of MaxDpbMbs * 3 / 8, wherein the value of MaxDpbMbs is given in 

Table A-1 of [1] for the highest level.

         Senders MAY use this knowledge to construct coded video streams

         with improved compression.

 

 

------------------------------------End of suggested changes
--------------------------------------

 

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Ye-Kui
Wang
Sent: Sunday, March 20, 2011 4:21 AM
To: payload@ietf.org; avt@ietf.org
Subject: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload drafts

 

Folks,

 

The three H.264/AVC related payload formats, namely,
draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-rtp-svc-27, and
draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48 stage.

 

The RFC-Editor has found the following problem: In
draft-ietf-avt-rtp-rfc3984bis-12, the definition of the max-dpb media
parameter refers to the MaxDPB that was defined the first version of the
H.264/AVC spec, but not any more in the latest version (the 2010 version).
The parameter in the latest H.264/AVC version corresponding to MaxDPB is
MaxDpbMbs, and the unit of the new parameter (i.e., macroblocks) is
different from the original one (i.e. 1024 bytes).

 

The problem applies also to the SVC payload format, the RCDO payload format,
and H.241.

 

A solution has been found and agreed, involving rfc3984bis authors and some
key people related to H.264/AVC (e.g., Gary Sullivan and Heiko Schwarz) and
H.241 (e.g., Stephen Botzko and Patrick Luthi). Furthermore, we have found
that there are also a couple of places that need fixes due to similar
changes from the initial version of H.264/AVC to the latest version.

 

Per Roni's suggestion, I am sending in below the changes to
draft-ietf-avt-rtp-rfc3984bis-12 for review by the Payload and AVTcore WGs.
It seems that exactly the same changes are needed to
draft-ietf-avt-rtp-h264-rcdo-08 (co-authors of this draft may confirm), and
similar but slightly different changes are needed to
draft-ietf-avt-rtp-svc-27.

 

Since the drafts are at the AUTH48 stage, please provide comments by Monday,
March 21, if any. Many thanks!

 

BR, YK

 

 

------------------------------------Start of suggested changes
--------------------------------------

 

Section 8.1:

OLD:

      max-cpb: The value of max-cpb is an integer indicating the maximum

         coded picture buffer size in units of 1000 bits for the VCL HRD

         parameters (see A.3.1, item i of [1]) and in units of 1200 bits

         for the NAL HRD parameters (see A.3.1, item j of [1]).

NEW:

      max-cpb: The value of max-cpb is an integer indicating the maximum

         coded picture buffer size. For Constrained Baseline, Baseline, Main


and Extended profiles, the unit is 1000 bits for the VCL HRD

         parameters and 1200 bits for the NAL HRD parameters. For High, High
10,

High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, 

High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles, the unit is cpbBrVclFactor

bits for the VCL HRD and cpbBrNalFactor bits for the NAL HRD parameters.

 

OLD:

      max-br: The value of max-br is an integer indicating the maximum
         video bitrate in units of 1000 bits per second for the VCL HRD
         parameters (see A.3.1, item i of [1]) and in units of 1200 bits
         per second for the NAL HRD parameters (see A.3.1, item j of
         [1]).

NEW: 

      max-br: The value of max-br is an integer indicating the maximum

         video bitrate.  For Constrained Baseline, Baseline, Main 

and Extended profiles, the unit is 1000 bits per second for the VCL HRD

         parameters and 1200 bits per second for the NAL HRD parameters. For
High, High 10,

High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, 

High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles, the unit is cpbBrVclFactor

bits per second for the VCL HRD and cpbBrNalFactor bits per second for the
NAL HRD parameters.

 

------------------------------------End of suggested changes
--------------------------------------

 

 


--Boundary_(ID_Y4Tbp7ToHbsmjs6ecv17SA)
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: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";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:SimSun;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:SimSun;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle28
	{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.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:484593867;
	mso-list-type:hybrid;
	mso-list-template-ids:-354640490 -1632847936 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Times New Roman","serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:Arial;
	color:#1F497D;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple style='text-justify-trim:punctuation'><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>HI Mo,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>When the solution was discussed there are two assumptions<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;color:#1F497D'><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span dir=LTR></span><span style='font-size:11.0pt;color:#1F497D'>&nbsp;Old implementations (RFC3984) expecting the maxdpb parameter in kbyes only supported </span><span style='font-size:11.0pt;color:#1F497D'>4:2:0 8-bit and no other color because otherwise using only Kbytes and not macro blocks will not work for them. <o:p>
 </o:p></
Paragraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;color:#1F497D'><span style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span dir=LTR></span><span style='font-size:11.0pt;color:#1F497D'>New implementation(RFC6184 &#8211; the assigned RFC number to 3984bis) expects a value in macroblocks and will interpret the value in maxdpb as macroblocks.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>So see my comments inline<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Roni Even<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>As individual<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;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><d
der-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal align=left style='text-align:left'><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"'> payload-bounces@ietf.org [mailto:payload-bounces@ietf.org] <b>On Behalf Of </b>Mo Zanaty (mzanaty)<br><b>Sent:</b> Sunday, March 27, 2011 6:23 AM<br><b>To:</b> Ye-Kui Wang; payload@ietf.org; avt@ietf.org<br><b>Cc:</b> Gary Sullivan; Roni Even<br><b>Subject:</b> Re: [payload] [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload drafts<o:p></o:p></span></p></div></div><p class=MsoNormal align=left style='text-align:left'><o:p>&nbsp;</o:p></p><p class=MsoNormal><span style='font-size:11.0pt'>The proposed changes to max-dpb, max-cpb and max-br sacrifice some backward compatibility with RFC 3984 and forward compatibility with H.264. The latter seems intentional but the former seems unintentional. Further changes are nee
 ded to f
e incompatibilities.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>What was discussed and decided regarding max-dpb, max-cpb and max-br in the ITU/IETF F2F meetings? Based on the original suggested changes (at the end without color coding), forward compatibility with H.264 appears to be the focus. But after &#8220;further discussions&#8221;, the newest suggested changes (with color coding) appear focused on backward compatibility with RFC 3984, but don&#8217;t fully achieve this.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>The problem with RFC 3984 backward compatibility is that changing the units of max-dpb (from 1024 bytes to 8/3 macroblocks) only works for the 4:2:0 chroma format, which is the primary format used in most profiles and applications. However, the high pro
 files su
s, and this change breaks backward compatibility for them.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>RE: See assumption 1<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>For example, consider an RFC 3984 implementation that declares max-dpb=8100 (KB) to support 3 reference frames of 720p at 4:4:4. The proposed change would misinterpret this declaration to mean 6 reference frames of 720p at any chroma format including 4:4:4, hence potentially overflowing the old RFC 3984 receiver&#8217;s DPB by a factor of 2.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>RE: if the system is old it will calculate the KB and will not 
 start fr
we have assumption 1.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>(Note that H.264 got away with changing MaxDPB since the original 2003 version only supported 4:2:0. When the high profiles which support other chroma formats were added in 2005, MaxDPB was explicitly redefined in terms of 4:2:0 so it remains constant across all chroma formats. For further clarity, MaxDpbMbs later replaced MaxDPB. But RFC 3984 never kept up with these changes, so implementations are stuck with the 2003 definitions even for later features such as the high profiles and other chroma formats.)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>RE: so this is why the two assumption are there.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p>&nbsp
 ;</o:p><
mal><span style='font-size:11.0pt'>The problem with H.264 forward compatibility is that NOT changing the units of max-cpb and max-br for the high profiles (to include the scaling factors 1.25/3/4) obviously creates confusion and incompatibility between H.264 and this bis draft. This seems like an intentional change after &#8220;further discussions&#8221; decided to focus on RFC 3984 backward compatibility at the expense of H.264 forward compatibility.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Before deciding on specific new text, the WG should decide on whether the focus of this draft should be backward compatibility with RFC 3984 or forward compatibility with H.264. Or if the intent is to strike some balance between the two, then clearly convey the intentional incompatibilities i
 n the te
<p class=MsoNormal><span style='font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Mo Zanaty<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal align=left style='text-align:left'><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>Ye-Kui Wang<br><b>Sent:</b> Monday, March 21, 2011 4:11 AM<br><b>To:</b> payload@ietf.org; avt@ietf.org<br><b>Subject:</b> Re: [AVTCORE] Some changes to rfc3984bis, SVC,and RCDO payload drafts<o:p></o:p></span></p></div></div><p class=MsoNormal align=left style='text-align:left'><o:p>&nbsp;</o:p></p><p class=M
 soNormal
1.0pt'>Further discussions with the same group of persons led to a decision to stay with the unscaled units for max-br and max-cpb, thus fewer changes are needed to the three payload formats listed in the title and H.241. With this, the changes needed are listed below (the originally suggested changes are dropped from this email). This time I have highlighted the changes, and I have also described the nature the changes below. Hope these may help understand better what have been changed, and can lead to a quicker decision by the group, including WG chairs, and our AD.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>BR, YK<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText>------------------------------------Start of suggested changes --------------------------------------<o:p></o:p></p><p class=MsoPlainText>
 <o:p>&nb
Normal><span style='color:#1F497D'>Section 8.1:<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>OLD:<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> max-dpb: The value of max-dpb is an integer indicating the maximum<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> decoded picture buffer size in units of 1024 bytes.</span><span style='font-size:12.0pt'>&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> The max-<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> dpb parameter signals 
 that the
 than<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> the minimum amount of decoded picture buffer memory required by<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> the signaled highest level conveyed in the value of the<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> profile-level-id parameter or the max-recv-level parameter.<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span s
 tyle='fo
y:SimSun'> When max-dpb is signaled, the receiver MUST be able to decode<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> NAL unit streams that conform to the signaled highest level,<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> with the exception that the MaxDPB value in Table A-1 of [1]<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> for the signaled highest level is replaced with the value of<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:
 12.0pt'>
nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> max-dpb.</span><span style='font-size:12.0pt'>&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> Consequently, a receiver that signals max-dpb MUST be<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> capable of storing the following number of decoded frames,<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> complementary field pairs, and non-paired fields in its decoded<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-fa
 mily:Sim
></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt;font-family:SimSun'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> Min(1024 * max-dpb / ( PicWidthInMbs * FrameHeightInMbs *<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> 256 * ChromaFormatFactor ), 16)<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt;font-family:SimSun'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-
 size:12.
PicWidthInMbs, FrameHeightInMbs, and ChromaFormatFactor are<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> </span><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'>defined in [1].<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt;font-family:SimSun'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> The value of max-dpb MUST be greater than or equal to the value<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-fam
 ily:SimS
able A-1 of [1] for the highest level.<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> Senders MAY use this knowledge to construct coded video streams<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> with improved compression.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>NEW: <span style='background:aqua;mso-highlight:aqua'>(When this change can be considered as editorial can be discussed, but the nature of this change as follows. On the other hand, if not changed, then the semantics of max-dpb is simply equivalent to unspecified, as MaxDPB and ChromaFormatFactor are not found in the latest H.264 spec any more. Note that compared to
  RFC 398
o not change.)</span><o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> max-dpb: The value of max-dpb is an integer indicating the maximum<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> decoded picture buffer size in units of 8/3 macroblocks.</span><span style='font-size:12.0pt'>&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> The max-<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> dpb parameter signals that the receiver has more memory than<o:p></o:p></span></p><p class=MsoNormal align=left styl
 e='text-
font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> the minimum amount of decoded picture buffer memory required by<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> the signaled highest level conveyed in the value of the<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> profile-level-id parameter or the max-recv-level parameter.<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> When max-dpb is signaled, the receiver MUST be abl
 e to dec
<p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> NAL unit streams that conform to the signaled highest level,<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> with the exception that <span style='background:yellow;mso-highlight:yellow'>the MaxDpbMbs value in Table A-1 of [1]<o:p></o:p></span></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt;background:yellow;mso-highlight:yellow'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun;background:yellow;mso-highlight:yellow'> for the signaled highest level is replaced with the value of<o:p></o:p></span></p><p class=MsoNormal align=left 
 style='t
le='font-size:12.0pt;background:yellow;mso-highlight:yellow'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun;background:yellow;mso-highlight:yellow'> max-dpb * 3 / 8</span><span style='font-size:12.0pt;font-family:SimSun'>.</span><span style='font-size:12.0pt'>&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> Consequently, a receiver that signals max-dpb MUST be<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> capable of storing the following number of decoded frames,<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> complementary field pairs, and non-paired fields in its decoded<o:p></o:
 p></span
lign=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> picture buffer:<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt;font-family:SimSun'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> <span style='background:yellow;mso-highlight:yellow'>Min(max-dpb * 3 / 8 / ( PicWidthInMbs * FrameHeightInMbs), 16)<o:p></o:p></span></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt;font-family:SimSun;background:yellow;mso-highlight:yellow'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt;background:yellow;mso-highlight:yellow'>&n
 bsp;&nbs
;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun;background:yellow;mso-highlight:yellow'> Wherein PicWidthInMbs and FrameHeightInMbs are defined in [1].</span><span style='font-size:12.0pt;font-family:SimSun'><o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt;font-family:SimSun'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> The value of max-dpb MUST be greater than or equal to the value<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> of <span style='background:yellow;mso-highlight:yellow'>MaxDpbMbs * 3 / 8, wherein the value of MaxDpbMbs is given in <o:p></o:p></span></sp
 an></p><
eft style='text-align:left;text-indent:.75in'><span style='font-size:12.0pt;font-family:SimSun;background:yellow;mso-highlight:yellow'>Table A-1 of [1] for the highest level.</span><span style='font-size:12.0pt;font-family:SimSun'><o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> Senders MAY use this knowledge to construct coded video streams<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> with improved compression.<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt;font-family:SimSun'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoPla
 inText>-
----------End of suggested changes --------------------------------------<o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal align=left style='text-align:left'><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>Ye-Kui Wang<br><b>Sent:</b> Sunday, March 20, 2011 4:21 AM<br><b>To:</b> payload@ietf.org; avt@ietf.org<br><b>Subject:</b> [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload drafts<o:p></o:p></span></p></div></div><p class=MsoNormal align=left style='text-align:left'><o:p>&nbsp;</o:p></p><p class=MsoNormal>Folks,<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>The three H.264/AVC related payload formats, namely, draft-ietf-avt-
 rtp-rfc3
-rtp-svc-27, and draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48 stage.<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>The RFC-Editor has found the following problem: In draft-ietf-avt-rtp-rfc3984bis-12, the definition of the max-dpb media parameter refers to the MaxDPB that was defined the first version of the H.264/AVC spec, but not any more in the latest version (the 2010 version). The parameter in the latest H.264/AVC version corresponding to MaxDPB is MaxDpbMbs, and the unit of the new parameter (i.e., macroblocks) is different from the original one (i.e. 1024 bytes).<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>The problem applies also to the SVC payload format, the RCDO payload format, and H.241.<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>A solution has been found and agreed, involving rfc3984bis authors and some key people related to H.264/AVC (e.g., Gary Sullivan and Heiko Schw
 arz) and
zko and Patrick Luthi). Furthermore, we have found that there are also a couple of places that need fixes due to similar changes from the initial version of H.264/AVC to the latest version.<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Per Roni&#8217;s suggestion, I am sending in below the changes to draft-ietf-avt-rtp-rfc3984bis-12 for review by the Payload and AVTcore WGs. It seems that exactly the same changes are needed to draft-ietf-avt-rtp-h264-rcdo-08 (co-authors of this draft may confirm), and similar but slightly different changes are needed to draft-ietf-avt-rtp-svc-27.<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Since the drafts are at the AUTH48 stage, please provide comments by Monday, March 21, if any. Many thanks!<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>BR, YK<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=MsoPlainText
 >-------
----Start of suggested changes --------------------------------------<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal><span style='color:#1F497D'>Section 8.1:<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>OLD:<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> max-cpb: The value of max-cpb is an integer indicating the maximum<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> coded picture buffer size in units of 1000 bits for the VCL HRD<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-
 family:S
.3.1, item i of [1]) and in units of 1200 bits<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> for the NAL HRD parameters (see A.3.1, item j of [1]).<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>NEW:<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> max-cpb: The value of max-cpb is an integer indicating the maximum<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> coded picture buffer size. For Constrained Baseline, Baseline, Main <o:p></o:p></span></p><p class=MsoNormal align=left style='tex
 t-align:
   ft;text-indent:.75in'>
span style='font-size:12.0pt;font-family:SimSun'>and Extended profiles, the unit is 1000 bits for the VCL HRD<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> parameters and 1200 bits for the NAL HRD parameters. For High, High 10,<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left;text-indent:.75in'><span style='font-size:12.0pt;font-family:SimSun'>High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, <o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left;text-indent:.75in'><span style='font-size:12.0pt;font-family:SimSun'>High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles, the unit is cpbBrVclFactor<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left;text-indent:.75in'><span style='font-size:12.0pt;font-family:SimSun'>bits for the VCL HRD a
 nd cpbBr
L HRD parameters.<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt;font-family:SimSun'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>OLD:<o:p></o:p></span></p><pre><span style='font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span> max-br: The value of max-br is an integer indicating the maximum<o:p></o:p></pre><pre><span style='font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span> video bitrate in units of 1000 bits per second for the VCL HRD<o:p></o:p></pre><pre><span style='font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span> parameters (see A.3.1, item i of [1]) and in units of 1200 bits<o:p></o:p></pre><pre><span style='font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span> per second for the NAL HRD parameters (see A.3.1, item j of<o:p></o:p></pre><pre><span style='font-family:"Courier New"'
 >&nbsp;&
bsp;&nbsp;&nbsp;</span> [1]).<o:p></o:p></pre><p class=MsoNormal><span style='color:#1F497D'>NEW: <o:p></o:p></span></p><pre><span style='font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span> max-br: The value of max-br is an integer indicating the maximum<o:p></o:p></pre><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> video bitrate.</span><span style='font-size:12.0pt'>&nbsp;</span><span style='font-size:12.0pt;font-family:SimSun'> For Constrained Baseline, Baseline, Main <o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left;text-indent:.75in'><span style='font-size:12.0pt;font-family:SimSun'>and Extended profiles, the unit is 1000 bits per second for the VCL HRD<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left'><span style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 &nbsp;&n
ont-size:12.0pt;font-family:SimSun'> parameters and 1200 bits per second for the NAL HRD parameters. For High, High 10,<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left;text-indent:.75in'><span style='font-size:12.0pt;font-family:SimSun'>High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra, <o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left;text-indent:.75in'><span style='font-size:12.0pt;font-family:SimSun'>High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles, the unit is cpbBrVclFactor<o:p></o:p></span></p><p class=MsoNormal align=left style='text-align:left;text-indent:.75in'><span style='font-size:12.0pt;font-family:SimSun'>bits per second for the VCL HRD and cpbBrNalFactor bits per second for the NAL HRD parameters.<o:p></o:p></span></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoPlainText>------------------------------------End of suggested changes --------------------------------------<o:p></o:p></p><p c
 lass=Mso
/p><p class=MsoNormal><span style='font-size:11.0pt'><o:p>&nbsp;</o:p></span></p></div></div></body></html>

--Boundary_(ID_Y4Tbp7ToHbsmjs6ecv17SA)--

From sunseawq@huawei.com  Sun Mar 27 04:44:44 2011
Return-Path: <sunseawq@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3207D3A67C3 for <avt@core3.amsl.com>; Sun, 27 Mar 2011 04:44:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.697
X-Spam-Level: 
X-Spam-Status: No, score=-2.697 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_23=0.6, J_CHICKENPOX_24=0.6, J_CHICKENPOX_53=0.6, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t2m13ZCLOcoI for <avt@core3.amsl.com>; Sun, 27 Mar 2011 04:44:40 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id BF97E3A67B4 for <avt@ietf.org>; Sun, 27 Mar 2011 04:44:38 -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 <0LIP00M5LSOSAR@szxga03-in.huawei.com> for avt@ietf.org; Sun, 27 Mar 2011 19:46:04 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LIP008B5SOSN3@szxga03-in.huawei.com> for avt@ietf.org; Sun, 27 Mar 2011 19:46:04 +0800 (CST)
Received: from jys1037575 (19.218.broadband.iol.cz [80.188.218.19]) by szxml12-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LIP00JLXSOD1Q@szxml12-in.huawei.com> for avt@ietf.org; Sun, 27 Mar 2011 19:46:04 +0800 (CST)
Date: Sun, 27 Mar 2011 13:43:35 +0200
From: Qin Wu <sunseawq@huawei.com>
To: IETF AVTCore WG <avt@ietf.org>
Message-id: <A20837070A10403A9CBEE46DB9EA6369@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: multipart/mixed; boundary="Boundary_(ID_IK1hVsUN/xXsrh/OZpPyIg)"
X-Priority: 3
X-MSMail-priority: Normal
Subject: [AVTCORE] New revision to draft-hunt-avtcore-monarch
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Mar 2011 11:44:44 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_IK1hVsUN/xXsrh/OZpPyIg)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_EaIKDVnI1KQlsU/wD8opHw)"


--Boundary_(ID_EaIKDVnI1KQlsU/wD8opHw)
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT

Hi,

In case you didn't receive this email, I send it again.

There is a new revision of the monarch draft that was late for the draft submission deadline. It will be uploaded once submission is re-opened. Meanwhile I attached the latest draft since part of my presentation is based on it.

Regards

Qin

--Boundary_(ID_EaIKDVnI1KQlsU/wD8opHw)
Content-type: text/html; charset=gb2312
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:o = "urn:schemas-microsoft-com:office:office"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=gb2312">
<META content="MSHTML 6.00.2900.6058" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>
<DIV class=WordSection1>
<P class=MsoNormal>Hi,<o:p></o:p></P>
<P class=MsoNormal>In case you didn't receive this email, I send it again.</P>
<P class=MsoNormal>There is a new revision of the monarch draft that was late 
for the draft submission deadline. It will be uploaded once submission is 
re-opened. Meanwhile I attached the latest draft since part of my presentation 
is based on it.<o:p></o:p></P>
<P class=MsoNormal>Regards<o:p></o:p></P>
<P class=MsoNormal>Qin<o:p></o:p></P></DIV></DIV></FONT></BODY></HTML>

--Boundary_(ID_EaIKDVnI1KQlsU/wD8opHw)--

--Boundary_(ID_IK1hVsUN/xXsrh/OZpPyIg)
Content-type: text/plain; name=draft-hunt-avtcore-monarch-02.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=draft-hunt-avtcore-monarch-02.txt




Audio/Video Transport Working                                    G. Hunt
Group                                                           P. Arden
Internet-Draft                                                        BT
Intended status: Informational                                Q. Wu, Ed.
Expires: September 25, 2011                                       Huawei
                                                          March 24, 2011


                    Monitoring Architectures for RTP
                   draft-hunt-avtcore-monarch-02.txt

Abstract

   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, as proposed 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.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 25, 2011.

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors.  All rights reserved.




Hunt, et al.           Expires September 25, 2011               [Page 1]

Internet-Draft        RTP Monitoring Architectures            March 2011


   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Requirements notation  . . . . . . . . . . . . . . . . . . . .  4
   3.  RTP monitoring architecture  . . . . . . . . . . . . . . . . .  5
   4.  RTCP Metric Block Report and associated parameters . . . . . .  8
     4.1.  Classification of RTCP Metric Block parameters . . . . . .  9
       4.1.1.  Application level parameters . . . . . . . . . . . . .  9
       4.1.2.  Transport level parameters . . . . . . . . . . . . . .  9
       4.1.3.  End system parameters  . . . . . . . . . . . . . . . . 10
   5.  Monitoring Methodology . . . . . . . . . . . . . . . . . . . . 11
     5.1.  Option 1 - Monitoring every packet . . . . . . . . . . . . 11
     5.2.  Option 2 - Real-time histogram methods . . . . . . . . . . 11
     5.3.  Option 3 - Monitoring by exception . . . . . . . . . . . . 11
     5.4.  Option 4 - Application-specific monitoring . . . . . . . . 12
   6.  Issues with RTCP XR extension  . . . . . . . . . . . . . . . . 13
   7.  Guideline for reporting block format using RTCP XR . . . . . . 14
     7.1.  Using small blocks . . . . . . . . . . . . . . . . . . . . 14
     7.2.  Sharing the identity block . . . . . . . . . . . . . . . . 14
     7.3.  Expanding the RTCP XR block namespace  . . . . . . . . . . 18
   8.  An example of a metric block . . . . . . . . . . . . . . . . . 19
   9.  Application to RFC 5117 topologies . . . . . . . . . . . . . . 20
     9.1.  Applicability to MCU . . . . . . . . . . . . . . . . . . . 20
     9.2.  Application to translators . . . . . . . . . . . . . . . . 20
   10. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 22
   11. Security Considerations  . . . . . . . . . . . . . . . . . . . 23
   12. Acknowledgement  . . . . . . . . . . . . . . . . . . . . . . . 24
   13. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 25
     13.1. draft-hunt-avtcore-monarch-00  . . . . . . . . . . . . . . 25
     13.2. draft-hunt-avtcore-monarch-01  . . . . . . . . . . . . . . 25
     13.3. draft-hunt-avtcore-monarch-02  . . . . . . . . . . . . . . 25
   14. Informative References . . . . . . . . . . . . . . . . . . . . 27
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 28







Hunt, et al.           Expires September 25, 2011               [Page 2]

Internet-Draft        RTP Monitoring Architectures            March 2011


1.  Introduction

   Service providers and network providers today suffer from lack of
   good service that can monitor the performance at the user's home,
   handset or remote office.  Without service performance metrics, it is
   difficult for network operators to properly locate the problem and
   solve service issues before problems impact subscriber/end user.  The
   resolution generally involves deploying costly field network
   technician to conduct on-site troubleshooting and diagnostics.  By
   reducing the expensive deployments with more automated remote
   monitoring capabilities, network operators can save significant
   costs, reduce mean time to repair and provider a better service
   offering.

   As more users and subscribers rely on real time application services,
   uncertainties in the performance and availability of these services
   are driving the need to support new standard methods for gathering
   performance metrics from RTP applications.  These rapidly emerging
   standards, such as RTCP XR [RFC3611]and other RTCP extension to
   Sender Reports(SR), Receiver Reports (RR) [RFC3550]are being
   developed for the purpose of collecting and reporting performance
   metrics from endpoint devices that can be used to correlate the
   metrics, provide end to end service visibility and measure and
   monitor QoE.

   However the proliferation of RTP/RTCP specific metrics for transport
   and application quality monitoring has been identified as a potential
   problem for RTP/RTCP interoperability, which attempt to provide full
   coverage of all those parameters of concern to a specific
   application.  Since different applications layered on RTP may have
   some monitoring requirements in common, therefore these metrics
   should be satisfied by a common design.

   The objective of this document is to define an extensible RTP
   monitoring framework to provide a small number of re-usable QoS/QoE
   metrics which facilitate reduced implementation costs and help
   maximize inter-operability.  [RFC5968] has stated that, where RTCP is
   to be extended with a new metric, the preferred mechanism is by the
   addition of a new RTCP XR [RFC3611] block.  This memo assumes that
   any requirement for a new metric to be transported in RTCP will use a
   new RTCP XR block.










Hunt, et al.           Expires September 25, 2011               [Page 3]

Internet-Draft        RTP Monitoring Architectures            March 2011


2.  Requirements notation

   This memo is informative and as such contains no normative
   requirements.















































Hunt, et al.           Expires September 25, 2011               [Page 4]

Internet-Draft        RTP Monitoring Architectures            March 2011


3.  RTP monitoring architecture

   The RTP monitoring architecture comprises the following two
   functional components shown below:

   o  Monitor

   o  Metric Block Structure

   Monitor is a functional component that acts as a source of
   information gathered for monitoring purposes.  It may also collects
   statistics from multiple source, stores such information reported by
   RTCP XR or other RTCP extension appropriately as base metric or
   calculates composite metric.  The end system that source RTP streams,
   or an intermediate-system that forwards RTP packets to End-devices
   that send or receive metric block can be envisioned to act as Monitor
   within the RTP monitoring architecture.

   The Metric Block exposes real time Application Quality information in
   the report block format to monitor within the Network Management
   System.  The RTCP or RTCP XR can be extended to convey such
   information.





























Hunt, et al.           Expires September 25, 2011               [Page 5]

Internet-Draft        RTP Monitoring Architectures            March 2011


       +-------------------+
       | RTP Sender        |
       |   +-----------+   |
       |   |  Monitor  | --- --------|
       |   |           |   |         |
       |   +-----------+   |         |
       |+-----------------+|         |        +--------------+
       ||Application      ||         |        |Management    |
       ||-streaming video ||         |        |  System      |
    |---|-VOIP            ||         |        |              |
    |  ||-video conference||      5  |        | +----------+ |
    |  ||-telepresence    ||          --------->|          | |
    |  ||-ad insertion    ||                  | |  Monitor | |
    |  |+-----------------+|         |--------->|          | |
    |  +-------------------+         |        | +-------\--+ |
    |               Report Block     |        +---------|----+
    |               transported over |  Report Block    |
    |               RTCP extension   |  transported over|5
    | 1                              |  RTCP XR         |
    | +------ -----------------+     |   +--------------|---- ----+
    | | RTP System             |     |   | RTP Receiver >--4-|--- |
    | |      +----------+      |  5  |   |    +-----------+  |    |
    | |      |          |------------|   |    |  Monitor  |<--    |
    | |      |  Monitor |      |         |    |           |<------|
    | |      |          |      |         |    +----/------+      ||
    | |      +----------+      |         |         |             ||
    | |                        |         |         |2            ||
    | | +-----------------+    |         | +-------/---------+   ||
    | | |Application      |    |         | |Application      |   ||
    | | |-streaming video |    |         | |-streaming video |   ||
    | | |-VOIP            |    |    1    | |-VOIP            |   3|
    ---->-Video conference|--------------->|-Video conference    ||
      | |-Telepresence    |    |         | |-Telepresence    |   ||
      | |-Ad insertion    |    |         | |-Ad insertion    |   ||
      | +-----------------+    |         | +-----------------+   ||
      | +-----------------+    |         | +-----------------+   ||
      | |Transport        |    |         | |Transport        |   ||
      | |-IP/UDP/RTP      |    |         | |-IP/UDP/RTP      >---||
      | |-IP/TCP/RTP      |    |         | | -IP/TCP/RTP     |    |
      | |-IP/TCP/RTSP/RTP |    |         | |-IP/TCP/RTSP/RTP |    |
      | +-----------------+    |         | +-----------------+    |
      +------------------------+         +------------------------+


                   Figure 1: RTP Monitoring Architecture






Hunt, et al.           Expires September 25, 2011               [Page 6]

Internet-Draft        RTP Monitoring Architectures            March 2011


   1.  RTP communication between real time applications

   2.  Application layer metrics

   3.  Transport layer metrics

   4.  End System metrics

   5.  Reporting Session- metrics transmitted over specified interfaces

   6.  Management application- monitor interaction using northbound
       interface. - Monitor outputs reports to the management
       application.  The management application collects raw data from
       monitor, organizes database, conducts data analysis and creates
       alerts to the users.  Note that Management application
       interaction with Monitor is out of scope of this document.



































Hunt, et al.           Expires September 25, 2011               [Page 7]

Internet-Draft        RTP Monitoring Architectures            March 2011


4.  RTCP Metric Block Report and associated parameters

   The basic RTCP Reception Report (RR) conveys reception statistics in
   metric block report format for multiple RTP media streams including

   o  transport level statistics

   o  the fraction of packet lost since the last report

   o  the cumulative number of packets lost

   o  the highest sequence number received

   o  an estimate of the inter-arrival jitter

   o  and information to allow senders to calculate the network round
      trip time.

   The RTCP XRs [RFC3611] supplement the existing RTCP packets and
   provide more detailed feedback on reception quality in several
   categories:

   o  Loss and duplicate RLE reports

   o  Packet-receipt times reports

   o  Round-trip time reports

   o  Statistics Summary Reports

   There are also various other scenarios in which it is desirable to
   send RTCP Metric reports more frequently.  The Audio/Video Profile
   with Feedback [RFC4585]extends the standard A/V Profile[RFC3551] to
   allow RTCP reports to be sent early provided RTCP bandwidth
   allocation is respected.  There are four use cases but are not
   limited to:

   o  RTCP NACK is used to provide feedback on the RTP sequence number
      of the lost packets.

   o  RTCP XR is extended to provide feedback on multicast acquisition
      statistics information and parameters.

   o  RTCP is extended to convey requests for full intra-coded frames or
      select the reference picture, and signalchanges in the desired
      temporal/spatial trade-off and maximum media bit rate.





Hunt, et al.           Expires September 25, 2011               [Page 8]

Internet-Draft        RTP Monitoring Architectures            March 2011


   o  RTCP or RTCP XR is extended to provide feedback on ECN statistics
      information.

4.1.  Classification of RTCP Metric Block parameters

4.1.1.  Application level parameters

   Measured data at the application level, i.e., QoE related parameters
   which focus on quality of content rather than network parameters.
   These include but are not limited to:

   o  Sound/Noise Level

   o  Echo return lost

   o  Statistics Summary Info, e.g.,key frame lost key frame lost rate/
      discard rate, key frame burst severity

   o  Codec Control

   o  Estimated Mean Opinion Score (MOS)

4.1.2.  Transport level parameters

   Measured data at the transport level.  These include but are not
   limited to:

   o  Lost packets

   o  Round trip delay

   o  Jitter

   o  Congestion info

   o  FEC

   o  Codec Control

   o  Media Synchronization info

   o  Retransmission Info

   o  RAMS info







Hunt, et al.           Expires September 25, 2011               [Page 9]

Internet-Draft        RTP Monitoring Architectures            March 2011


4.1.3.  End system parameters

   Measured data from application residing in that device.  These
   include but are not limited to:

   o  Error Concealment

   o  FEC

   o  Media Synchronization info

   o  Jitter Buffer Lost

   o  Jitter Buffer Delay





































Hunt, et al.           Expires September 25, 2011              [Page 10]

Internet-Draft        RTP Monitoring Architectures            March 2011


5.  Monitoring Methodology

5.1.  Option 1 - Monitoring every packet

   The aim of "monitoring every packet" is to ensure that the
   information reported is not dependent on the application.  In this
   scheme, RTP systems will report arrival data for each individual RTP
   packet.  RTP (or other) systems receiving this "raw" data may use it
   to calculate any preferred heuristic metrics, but such calculations
   and the reporting of the results (e.g. to a session control layer or
   a management layer) are outside the scope of RTP and RTCP.

5.2.  Option 2 - Real-time histogram methods

   There are several potentially useful metrics which rely on the
   accumulation of a histogram in real time, so that a packet arrival
   results in a counter being incremented rather than in the creation of
   a new data item.  These metrics may be gathered with a low and
   predictable storage requirement.  Each counter corresponds to a
   single class interval or "bin" of the histogram.  Examples of metrics
   which may be accumulated in this way include the observed
   distribution of packet delay variation, and the number of packets
   lost per unit time interval.

   Different networks may have very different expected and achieved
   levels of performance, but it may be useful to fix the number of
   class intervals in the reported histogram to give a predictable
   volume of data.  This can be achieved by starting with small class
   intervals ("bin widths") and automatically increasing the width (e.g.
   by factors of two) if outliers are seen beyond the current upper
   limit of the histogram.  Data already accumulated may be assigned
   unambiguously to the new set of bins, given some simple conditions on
   the relationship between the old and new origins and bin widths.

   A significant disadvantage of the histogram method is the loss of any
   information about time-domain correlations between the samples which
   build the histogram.  For example, a histogram of packet delay
   variation provides no indication of whether successive samples of
   packet delay variation were uncorrelated, or alternatively that the
   packet delay variation showed a highly-correlated low-frequency
   wander.

5.3.  Option 3 - Monitoring by exception

   An entity which both monitors the packet stream, and has sufficient
   knowledge of the application to know when transport impairments may
   have degraded the application's performance, may choose to send
   exception reports containing details of the transport impairments to



Hunt, et al.           Expires September 25, 2011              [Page 11]

Internet-Draft        RTP Monitoring Architectures            March 2011


   a receiving system.  The crossing of a transport impairment
   threshold, or some application-layer event, would trigger such
   reports.  RTP end systems and mixers are likely to contain
   application implementations which may, in principle, identify this
   type of exception.

   It is likely that RTP translators will not contain suitable
   implementations which could identify such exceptions.

   On-path devices such as routers and switches are not likely to be
   aware of RTP at all.  Even if they are aware of RTP, they are
   unlikely to be aware of the RTP-level performance required by
   specific applications, and hence they are unlikely to be able to
   identify the level of impairment at which exceptional transport
   conditions may start to affect application performance.

   This type of monitoring typically requires the storage of recent data
   in a FIFO (e.g. a circular buffer) so that data relevant to the
   period just before and just after the exception may be reported.  It
   is not usually helpful to report transport data only from the period
   following an exception event detected by an application.  This
   imposes some storage requirement (though less than needed for Option
   1).  It also implies the existence of additional cross-layer
   primitives or APIs to trigger the transport layer to generate and
   send its exception report.  Such a capability might be considered
   architecturally undesirable, in that it complicates one or more
   interfaces above the RTP layer.

5.4.  Option 4 - Application-specific monitoring

   This is a business-as-usual option which suggests that the current
   approach should not be changed, based on the idea that previous
   application-specific approaches such as that of [RFC3611] were valid.
   If a large category of RTP applications (such as VoIP) has a
   requirement for a unique set of transport metrics, arising from its
   different requirements of the transport, then it seems reasonable for
   each application category to define its preferred set of metrics to
   describe transport impairments.  We expect that there will be few
   such categories, probably less than 10.

   It may be easier to achieve interworking for a well-defined set of
   application-specific metrics than it would be in the case that
   applications select a profile from a palette of many independent re-
   usable metrics.







Hunt, et al.           Expires September 25, 2011              [Page 12]

Internet-Draft        RTP Monitoring Architectures            March 2011


6.  Issues with RTCP XR extension

   Issues that have come up in the past with extensions to RTCP or RTCP
   XR include (but are probably not limited to) the following:

   o  Repeating this information in a number of metrics blocks within
      the same RTCP packet may bring inefficiency when multiple small
      blocks in the same RTCP XR packet contain measurement data for the
      same stream and period.

   o  RFC 3611 [RFC3611] defines seven report block formats for network
      management and quality monitoring.  However some of these block
      types defined in [RFC3611]are only specifically designed for
      conveying multicast inference of network characteristics(MINC) or
      voice over IP (VoIP) monitoring.

   o  Designing a single report block or metric containing a large
      number of parameters in different classes for a specific
      application may increase implementation cost and minimize
      interoperability.

   o  The RTCP XR block namespace is limited by the 8-bit block type
      field in the RTCP XR header Under current allocation pressure, we
      expect that the RTCP XR Block Type space will be exhausted soon.
      We therefore need a way to extend the block type space, so that
      new specifications may continue to be developed.

























Hunt, et al.           Expires September 25, 2011              [Page 13]

Internet-Draft        RTP Monitoring Architectures            March 2011


7.   Guideline for reporting block format using RTCP XR

7.1.  Using small blocks

   Different applications using RTP for media transport certainly have
   differing requirements for metrics transported in RTCP to support
   their operation.  For many applications, the basic metrics for
   transport impairments provided in RTCP SR and RR packets [RFC3550]
   (together with source identification provided in RTCP SDES packets)
   are sufficient.  For other applications additional metrics may be
   required or at least sufficiently useful to justify the overheads,
   both of processing in endpoints and of increased session bandwidth.
   For example an IPTV application using Forward Error Correction (FEC)
   might use either a metric of post-repair loss or a metric giving
   detailed information about pre-repair loss bursts to optimise payload
   bandwidth and the strength of FEC required for changing network
   conditions.  However there are many metrics available.  It is likely
   that different applications or classes of applications will wish to
   use different metrics.  Any one application is likely to require
   metrics for more than one parameter but if this is the case,
   different applications will almost certainly require different
   combinations of metrics.  If larger blocks are defined containing
   multiple metrics to address the needs of each application, it becomes
   likely that many different such larger blocks are defined, which
   becomes a danger to interoperability.

   To avoid this pitfall, this memo proposes the use of small RTCP XR
   metrics blocks each containing a very small number of individual
   metrics characterising only one parameter of interest to an
   application running over RTP.  For example, at the RTP transport
   layer, the parameter of interest might be packet delay variation, and
   specifically the metric "IPDV" defined by [Y1540].  See Section 8 for
   architectural considerations for a metrics block, using as an example
   a metrics block to report packet delay variation.

7.2.  Sharing the identity block

   Any measurement must be identified.  However if metrics are delivered
   in small blocks there is a danger of inefficiency arising from
   repeating this information in a number of metrics blocks within the
   same RTCP packet, in cases where the same identification information
   applies to multiple metrics blocks.

   An instance of a metric must be identified using information which is
   likely to include most of the following:






Hunt, et al.           Expires September 25, 2011              [Page 14]

Internet-Draft        RTP Monitoring Architectures            March 2011


   o  the node at which it was measured,

   o  the source of the measured stream (for example, its CNAME),

   o  the SSRC of the measured stream,

   o  the sequence number of the first packet of the RTP session,

   o  the extended sequence numbers of the first packet of the current
      measurement interval, and the last packet included in the
      measurement,

   o  the duration of the most recent measurement interval and

   o  the duration of the interval applicable to cumulative measurements
      (which may be the duration of the RTP session to date).

   Note that this set of information may overlap with, but is more
   extensive than, that in the union of similar information in RTCP RR
   packets.  However we can not assume that RR information is always
   present when XR is sent, since they may have different measurement
   intervals.  Also the reason for the additional information carried in
   the XR is the perceived difficulty of "locating" the *start* of the
   RTP session (sequence number of 1st packet, duration of interval
   applicable to cumulative measurements) using only RR.  However when
   an RTCP XR packet containing more than two metrics blocks, reporting
   on the same streams from the same source, each metric block should
   have the same measurement identify, if each metric block carry the
   duplicated data for the measurement identity ,it leads to redundant
   information in this design since equivalent information is provided
   multiple times, once in *every* identification packet.  Though this
   ensures immunity to packet loss, the design bring more complexity and
   the overhead is not completely trivial.

   This section proposes an approach to minimise the inefficiency of
   providing this identification information, assuming that an
   architecture based on small blocks means that a typical RTCP packet
   will contain more than one metrics block needing the same
   identification.  The choice of identification information to be
   provided is discussed in [IDENTITY] (work in progress).

   The approach is to define a stand-alone block containing only
   identification information, and to tag this identification block with
   a number which is unique within the scope of the containing RTCP XR
   packet.  The "containing RTCP XR packet" is defined here as the RTCP
   XR header with PT=XR=207 defined in Section 2 of [RFC3611] and the
   associated payload defined by the length field of this RTCP XR
   header.  The RTCP XR header itself includes the SSRC of the node at



Hunt, et al.           Expires September 25, 2011              [Page 15]

Internet-Draft        RTP Monitoring Architectures            March 2011


   which all of the contained metrics were measured, hence this SSRC
   need not be repeated in the stand-alone identification block.  A
   single containing RTCP XR packet may contain multiple identification
   blocks limited by the range of the tag field.  Typically there will
   be one identification block per monitored source SSRC, but the use of
   more than one identification block for a single monitored source SSRC
   within a single containing RTCP XR packet is not ruled out.

   There will be zero or more metrics blocks dependent on each
   identification block.  The dependence of an instance of a metrics
   block on an identification block is established by the metrics
   block's having the same numeric value of the tag field as its
   identification block (in the same containing RTCP XR packet).

   Figure 2 below illustrates this principle using as an example an RTCP
   XR packet containing four metrics blocks, reporting on streams from
   two sources.  The measurement identity information is provided in two
   blocks with Block Type NMI, and tag values 0 and 1 respectively.

   Note: in this example, RTCP XR block type values for four proposed
   new block types (work in progress) are given as NMI, NPDV, NBGL and
   NDEL.  These represent numeric block type codepoints to be allocated
   by IANA at the conclusion of the work.

   Each of these two identity blocks will specify the SSRC of one of the
   monitored streams, as well as information about the span of the
   measurement.  There are two metrics blocks with tag=0 indicating
   their association with the measurement identity block which also has
   tag=0.  These are the two blocks following the identity block with
   tag=0, though this positioning is not mandatory.  There are also two
   metrics blocks with tag=1 indicating their association with the
   measurement identity block which also has tag=1, and these are the
   two blocks following the identity block with tag=1.

   Note that if metrics blocks associated with an identity block must
   always follow the identity block, we could save the tag field and
   possibly simplify processing.  However depending on ordering of
   metric block and identity block may bring inefficiency since you do
   not know which block is the last metric block associated with
   identity block.  Hence it is more desirable to to cross-referencing
   with a numeric tag,i.e., using tag field to associated metric block
   with identity block.

   In the example, the block types of the metrics blocks associated with
   tag=0 are BT=NPDV (a PDV metrics block) and BT=NBGL (a burst and gap
   loss metrics block).  The block types of the metrics blocks
   associated with tag=1 are BT=NPDV (a second PDV metrics block) and
   BT=NDEL (a delay metrics block).  This illustrates that:



Hunt, et al.           Expires September 25, 2011              [Page 16]

Internet-Draft        RTP Monitoring Architectures            March 2011


   o  multiple instances of the same metrics block may occur within a
      containing RTCP XR packet, associated with different
      identification information, and

   o  differing measurements may be made, and reported, for the
      different streams arriving at an RTP system.


       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |V=2|P|reserved |   PT=XR=207   |             length            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                  SSRC of RTCP XR packet sender                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |     BT=NMI    |0|tag=0| resv  |        block length           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                  SSRC of stream source 1                      |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      .      ...measurement identity information, source 1...         .
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |     BT=NPDV   |I|tag=0|pdvtyp |        block length           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      .               ...PDV information for source 1...              .
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |    BT=NBGL    |I|tag=0| resv  |        block length           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      .            ...burst-gap-loss information for source 1...      .
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |     BT=NMI    |0|tag=1| resv  |        block length           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                  SSRC of stream source 2                      |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      .      ...measurement identity information, source 2...         .
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |     BT=NPDV   |I|tag=1|pdvtyp |        block length           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      .              ...PDV information for source 2...               .
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |    BT=NDEL    |I|tag=1| resv  |        block length           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      .             ...delay information for source 2...              .
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

               Figure 2: RTCP XR block with identity blocks

   This approach of separating the identification information is more
   costly than providing identification in each metrics block if only a



Hunt, et al.           Expires September 25, 2011              [Page 17]

Internet-Draft        RTP Monitoring Architectures            March 2011


   single metrics block is sent in an RTCP packet, but becomes
   beneficial as soon as more than one metrics block shares common
   identification.

7.3.  Expanding the RTCP XR block namespace

   The RTCP XR block namespace is limited by the 8-bit block type field
   in the RTCP XR header (Section 3 of [RFC3611]).  IESG have noted that
   this is potentially restrictive.  It would be possible to standardize
   an expansion mechanism, probably based on use of a new field near the
   start of the variable-length "type-specific block contents" field.
   Clearly this could apply only to new block types, so might be
   standardized to apply to some subrange of the current 8-bit range,
   for example the range 128 through 191 might be used.  At time of
   writing, block types 12 to 254 are unassigned and 255 is reserved for
   future expansion.  One potential use is through hierarchical control,
   where one or a few codepoints at the top level are given to other
   SDOs who may then define a number of metrics distinguished by values
   in the (so far hypothetical) new field.
































Hunt, et al.           Expires September 25, 2011              [Page 18]

Internet-Draft        RTP Monitoring Architectures            March 2011


8.  An example of a metric block

   This section uses the example of an existing proposed metrics block
   to illustrate the application of the principles set out in
   Section 7.1.

   The example [PDV] (work in progress) is a block to convey information
   about packet delay variation (PDV) only, consistent with the
   principle that a metrics block should address only one parameter of
   interest.  One simple metric of PDV is available in the RTCP RR
   packet as the "jit" field.  There are other PDV metrics which may be
   more useful to certain applications.  Two such metrics are the IPDV
   metric ([Y1540], [RFC3393]) and the MAPDV2 metric [G1020].  Use of
   these metrics is consistent with the principle in Section 5 of
   [RFC5968] that metrics should usually be defined elsewhere, so that
   RTCP standards define only the transport of the metric rather than
   its nature.  The purpose of this section is to illustrate the
   architecure using the example of [PDV] (work in progress) rather than
   to document the design of the PDV metrics block or to provide a
   tutorial on PDV in general.

   Given the availability of at least three metrics for PDV, there are
   design options for the allocation of metrics to RTCP XR blocks:

   o  provide an RTCP XR block per metric

   o  provide a single RTCP XR block which contains all three metrics

   o  provide a single RTCP block to convey any one of the three
      metrics, together with a identifier to inform the receiving RTP
      system of the specific metric being conveyed

   In choosing between these options, extensibility is important,
   because additional metrics of PDV may well be standardised and
   require inclusion in this framework.  The first option is extensible
   but only by use of additional RTCP XR blocks, which may consume the
   limited namespace for RTCP XR blocks at an unacceptable rate.  The
   second option is not extensible, so could be rejected on that basis,
   but in any case a single application is quite unlikely to require
   transport of more than one metric for PDV.  Hence the third option
   was chosen.  This implies the creation of a subsidiary namespace to
   enumerate the PDV metrics which may be transported by this block, as
   discussed further in [PDV] (work in progress).








Hunt, et al.           Expires September 25, 2011              [Page 19]

Internet-Draft        RTP Monitoring Architectures            March 2011


9.  Application to RFC 5117 topologies

   An RTP system (end system, mixer or translator) which originates,
   terminates or forwards RTCP XR blocks is expected to handle RTCP,
   including RTCP XR, as specified in [RFC3550] for that class of RTP
   systems.  Provided this expectation is met, an RTP system using RTCP
   XR is architecturally no different from an RTP system of the same
   class (end system, mixer, or translator) which does not use RTCP XR.
   This statement applies to the topologies investigated in [RFC5117],
   where they use RTP end systems, RTP mixers and RTP translators as
   these classes are defined in [RFC3550].

   These topologies are specifically Topo-Point-to-Point, Topo-
   Multicast, Topo-Translator (both variants, Topo-Trn-Translator and
   Topo-Media-Translator, and combinations of the two), and Topo-Mixer.

9.1.  Applicability to MCU

   The topologies based on systems which do not behave according to
   [RFC3550], that is Topo-Video-Switch-MCU and Topo-RTCP-terminating-
   MCU, suffer from the difficulties described in [RFC5117].  These
   difficulties apply to systems sending, and expecting to receive, RTCP
   XR blocks as much as to systems using other RTCP packet types.  For
   example, a participant RTP end system may send media to a video
   switch MCU.  If the media stream is not selected for forwarding by
   the switch, neither RTCP RR packets nor RTCP XR blocks referring to
   the end system's generated stream will be received at the RTP end
   system.  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.

9.2.  Application to translators

   Section 7.2 of [RFC3550] describes processing of RTCP by translators.
   RTCP XR is within the scope of the recommendations of [RFC3550].
   Some RTCP XR metrics blocks may usefully be measured at, and reported
   by, translators.  As described in [RFC3550] this creates a
   requirement for the translator to allocate an SSRC for itself so that
   it may populate the SSRC in the RTCP XR packet header (although the
   translator is not a Synchronisation Source in the sense of
   originating RTP media packets).  It must also supply this SSRC and
   the corresponding CNAME in RTCP SDES packets.

   In RTP sessions where one or more translators generate any RTCP
   traffic towards their next-neighbour RTP system, other translators in
   the session have a choice as to whether they forward a translator's
   RTCP packets.  Forwarding may provide additional information to other



Hunt, et al.           Expires September 25, 2011              [Page 20]

Internet-Draft        RTP Monitoring Architectures            March 2011


   RTP systems in the connection but increases RTCP bandwidth and may in
   some cases present a security risk.  RTP translators may have
   forwarding behaviour based on local policy, which might differ
   between different interfaces of the same translator.

   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.  However even for bidirectional unicast there
   is a possibility of a source sending RTCP XR before it has sent any
   RTP media (leading to transient mis-categorisation of an RTP end
   system or RTP mixer as a translator), and for multicast sessions - or
   unidirectional/streaming unicast - there is a possibility of a
   receive-only end system being permanently mis-categorised as a
   translator.  Hence it is desirable for a translator that send XR to
   have a way to declare itself explicitly.




































Hunt, et al.           Expires September 25, 2011              [Page 21]

Internet-Draft        RTP Monitoring Architectures            March 2011


10.  IANA Considerations

   None.
















































Hunt, et al.           Expires September 25, 2011              [Page 22]

Internet-Draft        RTP Monitoring Architectures            March 2011


11.  Security Considerations

   This document itself contains no normative text and hence should not
   give rise to any new security considerations, to be confirmed.















































Hunt, et al.           Expires September 25, 2011              [Page 23]

Internet-Draft        RTP Monitoring Architectures            March 2011


12.  Acknowledgement

   The authors would like to thank Colin Perkins, Graeme Gibbs, Debbie
   Greenstreet, Keith Drage,Dan Romascanu, Ali C. Begen, Roni Even for
   their valuable comments and suggestions on the early version of this
   document.













































Hunt, et al.           Expires September 25, 2011              [Page 24]

Internet-Draft        RTP Monitoring Architectures            March 2011


13.  Change Log

13.1.  draft-hunt-avtcore-monarch-00

   The following are the major changes compared to previous version:

   o  Provide some background texts and related work into Introduction
      section.

   o  Add a new section 3 to describe RTP monitoring architecture.

   o  Add a new section 4 to describe RTCP Metric Block Report and
      associated parameters.

   o  Move section 3.1, 3.2,3.3 and 3.4 in draft-hunt-avt-monarch-00 to
      this version as section 5 to describe Monitoring Methodology.

   o  Add a new section 6 to describe Issues with RTCP XR extension.

   o  Merge section 3,4, 8 in previous version into one new section 9 to
      describe Guideline for reporting block format using RTCP XR.

   o  Merge section 6,7 in previous version into one new section 9 to
      describe Application to RFC 5117 topologies.

13.2.  draft-hunt-avtcore-monarch-01

   The following are the major changes compared to previous version:

   o  Update figure 1 to describe the interface between RTP Sender and
      Report Collector in precise granularity.

   o  Add some texts to define the role of RRW and RRC.

   o  Correct the order of the second figure in the document.

   o  Other editorial changes.

13.3.  draft-hunt-avtcore-monarch-02

   The following are the major changes compared to previous version:

   o  Substitute the two components in the monitoring archtiecture with
      monitor functionality to get alignment with RFC3550 terminology.

   o  Clear up all the Editor Notes in the document.





Hunt, et al.           Expires September 25, 2011              [Page 25]

Internet-Draft        RTP Monitoring Architectures            March 2011


   o  Add one more issue with RTCP XR extension.

   o  Add some texts to clarify the RRC interface with Network Mangement
      Application.















































Hunt, et al.           Expires September 25, 2011              [Page 26]

Internet-Draft        RTP Monitoring Architectures            March 2011


14.  Informative References

   [G1020]    ITU-T, "ITU-T Rec. G.1020, Performance parameter
              definitions for quality of speech and other voiceband
              applications utilizing IP networks", July 2006.

   [IDENTITY]
              Hunt, G., "RTCP XR Report Block for Measurement Identity",
              ID draft-ietf-avt-rtcp-xr-meas-identity-02, May 2009.

   [PDV]      Hunt, G., "RTCP XR Report Block for Packet Delay Variation
              Metric Reporting", ID draft-ietf-avt-rtcp-xr-pdv-03,
              May 2009.

   [RFC1122]  Braden, R., "Requirements for Internet Hosts --
              Communication Layers", RFC 1122, October 1989.

   [RFC3393]  Demichelis, C., "IP Packet Delay Variation Metric for IP
              Performance Metrics (IPPM)", RFC 3393, November 2002.

   [RFC3550]  Schulzrinne, H., "RTP: A Transport Protocol for Real-Time
              Applications", RFC 3550, July 2003.

   [RFC3551]  Schulzrinne , H. and S. Casner, "Extended RTP Profile for
              Real-time Transport Control Protocol (RTCP)-Based Feedback
              (RTP/AVPF)", RFC 3551, July 2003.

   [RFC3611]  Friedman, T., "RTP Control Protocol Extended Reports (RTCP
              XR)", RFC 3611, November 2003.

   [RFC4585]  Ott, J. and S. Wenger, "Extended RTP Profile for Real-time
              Transport Control Protocol (RTCP)-Based Feedback (RTP/
              AVPF)", RFC 4585, July 2006.

   [RFC5117]  Westerlund, M., "RTP Topologies", RFC 5117, January 2008.

   [RFC5968]  Ott, J. and C. Perkins, "Guidelines for Extending the RTP
              Control Protocol (RTCP)", RFC 5968, September 2010.

   [Y1540]    ITU-T, "ITU-T Rec. Y.1540, IP packet transfer and
              availability performance parameters", November 2007.










Hunt, et al.           Expires September 25, 2011              [Page 27]

Internet-Draft        RTP Monitoring Architectures            March 2011


Authors' Addresses

   Geoff Hunt
   BT
   Orion 1 PP2
   Adastral Park
   Martlesham Heath
   Ipswich, Suffolk  IP5 3RE
   United Kingdom

   Phone: +44 1473 651704
   Email: geoff.hunt@bt.com


   Philip Arden
   BT
   Orion 3/7 PP4
   Adastral Park
   Martlesham Heath
   Ipswich, Suffolk  IP5 3RE
   United Kingdom

   Phone: +44 1473 644192
   Email: philip.arden@bt.com


   Qin Wu (editor)
   Huawei
   101 Software Avenue, Yuhua District
   Nanjing, Jiangsu  210012
   China

   Email: sunseawq@huawei.com


















Hunt, et al.           Expires September 25, 2011              [Page 28]



--Boundary_(ID_IK1hVsUN/xXsrh/OZpPyIg)--

From yekui.wang@huawei.com  Sun Mar 27 06:00:44 2011
Return-Path: <yekui.wang@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 69DF43A6822; Sun, 27 Mar 2011 06:00:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.232
X-Spam-Level: 
X-Spam-Status: No, score=-6.232 tagged_above=-999 required=5 tests=[AWL=-0.234, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aB3dgBFEt-JS; Sun, 27 Mar 2011 06:00:29 -0700 (PDT)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id 5B7993A6823; Sun, 27 Mar 2011 06:00:29 -0700 (PDT)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LIP00L6ZW7HJU@usaga02-in.huawei.com>; Sun, 27 Mar 2011 06:02:05 -0700 (PDT)
Received: from dfweml201-edg.china.huawei.com ([172.18.9.107]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPS id <0LIP00B3LW7G4G@usaga02-in.huawei.com>; Sun, 27 Mar 2011 06:02:04 -0700 (PDT)
Received: from DFWEML402-HUB.china.huawei.com (10.193.5.102) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.270.1; Sun, 27 Mar 2011 06:02:04 -0700
Received: from DFWEML503-MBX.china.huawei.com ([169.254.3.54]) by DFWEML402-HUB.china.huawei.com ([::1]) with mapi id 14.01.0270.001; Sun, 27 Mar 2011 06:01:31 -0700
Date: Sun, 27 Mar 2011 13:01:30 +0000
From: Ye-Kui Wang <yekui.wang@huawei.com>
In-reply-to: <B2DE0AFA86565C47BD3A8435550F9553030CFF66@XMB-RCD-201.cisco.com>
X-Originating-IP: [10.47.138.6]
To: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>, "payload@ietf.org" <payload@ietf.org>, "avt@ietf.org" <avt@ietf.org>
Message-id: <B99DECD58A94E143BA6F1508CC688351051E9159@dfweml503-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_S2WDxSbD8uh4J8yJq+CNww)"
Content-language: en-US
Accept-Language: en-US
Thread-topic: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload drafts
Thread-index: Acvm161AAF2A6AC0R/ODLEMZyh1IcgAwzyEAAIkXUFAAnXzNcAAR3LnQ
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <B2DE0AFA86565C47BD3A8435550F9553030CFF66@XMB-RCD-201.cisco.com>
Cc: Gary Sullivan <garysull@microsoft.com>, Stephen Botzko <stephen.botzko@gmail.com>, Roni Even <Even.roni@huawei.com>
Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Mar 2011 13:00:44 -0000

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

I think the statement "The proposed changes to max-dpb, max-cpb and max-br sacrifice some backward compatibility with RFC 3984 and forward compatibility with H.264." is incorrect.

On backward compatibility with RFC 3984: The semantics in RFC 3984 does not work with color formats other than YUV 4:2:0 and bit depth other than 8 bits, and the new profiles defined in H.264 after RFC 3984's publication. The proposed changes fix this bug in a way that is backward compatible to RFC 3984, i.e., the fix now covers all color formats and bit depths, while for the video formats and profiles supported in RFC 3984, the bits on the wire remain unchanged. Therefore, I don't think the changes sacrifice backward compatibility with RFC 3984.

On the so-called forward compatibility with H.264: "NOT changing the units of max-cpb and max-br for the high profiles (to include the scaling factors 1.25/3/4)" means that the numbers in the referred H.264 spec must be scaled before they are put into the payload format signaling as specified in the new RFC. Note that whether the scaling factor is considered or not, there is no problem with RFC 3984 backward compatibility. Are you saying you prefer to have the scaled units for the semantics of max-cpb and max-br? If yes, could you please explain why that is better?

BR, YK

From: Mo Zanaty (mzanaty) [mailto:mzanaty@cisco.com]
Sent: Sunday, March 27, 2011 12:23 AM
To: Ye-Kui Wang; payload@ietf.org; avt@ietf.org
Cc: Roni Even; Stephen Botzko; Gary Sullivan
Subject: RE: [AVTCORE] Some changes to rfc3984bis, SVC,and RCDO payload drafts

The proposed changes to max-dpb, max-cpb and max-br sacrifice some backward compatibility with RFC 3984 and forward compatibility with H.264. The latter seems intentional but the former seems unintentional. Further changes are needed to fix or clearly convey these incompatibilities.

What was discussed and decided regarding max-dpb, max-cpb and max-br in the ITU/IETF F2F meetings? Based on the original suggested changes (at the end without color coding), forward compatibility with H.264 appears to be the focus. But after "further discussions", the newest suggested changes (with color coding) appear focused on backward compatibility with RFC 3984, but don't fully achieve this.

The problem with RFC 3984 backward compatibility is that changing the units of max-dpb (from 1024 bytes to 8/3 macroblocks) only works for the 4:2:0 chroma format, which is the primary format used in most profiles and applications. However, the high profiles support other chroma formats, and this change breaks backward compatibility for them.

For example, consider an RFC 3984 implementation that declares max-dpb=8100 (KB) to support 3 reference frames of 720p at 4:4:4. The proposed change would misinterpret this declaration to mean 6 reference frames of 720p at any chroma format including 4:4:4, hence potentially overflowing the old RFC 3984 receiver's DPB by a factor of 2.

(Note that H.264 got away with changing MaxDPB since the original 2003 version only supported 4:2:0. When the high profiles which support other chroma formats were added in 2005, MaxDPB was explicitly redefined in terms of 4:2:0 so it remains constant across all chroma formats. For further clarity, MaxDpbMbs later replaced MaxDPB. But RFC 3984 never kept up with these changes, so implementations are stuck with the 2003 definitions even for later features such as the high profiles and other chroma formats.)

The problem with H.264 forward compatibility is that NOT changing the units of max-cpb and max-br for the high profiles (to include the scaling factors 1.25/3/4) obviously creates confusion and incompatibility between H.264 and this bis draft. This seems like an intentional change after "further discussions" decided to focus on RFC 3984 backward compatibility at the expense of H.264 forward compatibility.

Before deciding on specific new text, the WG should decide on whether the focus of this draft should be backward compatibility with RFC 3984 or forward compatibility with H.264. Or if the intent is to strike some balance between the two, then clearly convey the intentional incompatibilities in the text.

Regards,
Mo Zanaty

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Ye-Kui Wang
Sent: Monday, March 21, 2011 4:11 AM
To: payload@ietf.org; avt@ietf.org
Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC,and RCDO payload drafts

Further discussions with the same group of persons led to a decision to stay with the unscaled units for max-br and max-cpb, thus fewer changes are needed to the three payload formats listed in the title and H.241. With this, the changes needed are listed below (the originally suggested changes are dropped from this email). This time I have highlighted the changes, and I have also described the nature the changes below. Hope these may help understand better what have been changed, and can lead to a quicker decision by the group, including WG chairs, and our AD.

BR, YK


------------------------------------Start of suggested changes --------------------------------------


Section 8.1:
OLD:
      max-dpb: The value of max-dpb is an integer indicating the maximum
         decoded picture buffer size in units of 1024 bytes.  The max-
         dpb parameter signals that the receiver has more memory than
         the minimum amount of decoded picture buffer memory required by
         the signaled highest level conveyed in the value of the
         profile-level-id parameter or the max-recv-level parameter.
         When max-dpb is signaled, the receiver MUST be able to decode
         NAL unit streams that conform to the signaled highest level,
         with the exception that the MaxDPB value in Table A-1 of [1]
         for the signaled highest level is replaced with the value of
         max-dpb.  Consequently, a receiver that signals max-dpb MUST be
         capable of storing the following number of decoded frames,
         complementary field pairs, and non-paired fields in its decoded
         picture buffer:

            Min(1024 * max-dpb / ( PicWidthInMbs * FrameHeightInMbs *
            256 * ChromaFormatFactor ), 16)

         PicWidthInMbs, FrameHeightInMbs, and ChromaFormatFactor are
         defined in [1].

         The value of max-dpb MUST be greater than or equal to the value
         of MaxDPB given in Table A-1 of [1] for the highest level.
         Senders MAY use this knowledge to construct coded video streams
         with improved compression.
NEW: (When this change can be considered as editorial can be discussed, but the nature of this change as follows. On the other hand, if not changed, then the semantics of max-dpb is simply equivalent to unspecified, as MaxDPB and ChromaFormatFactor are not found in the latest H.264 spec any more. Note that compared to RFC 3984, the bits on the wire do not change.)
      max-dpb: The value of max-dpb is an integer indicating the maximum
         decoded picture buffer size in units of 8/3 macroblocks.  The max-
         dpb parameter signals that the receiver has more memory than
         the minimum amount of decoded picture buffer memory required by
         the signaled highest level conveyed in the value of the
         profile-level-id parameter or the max-recv-level parameter.
         When max-dpb is signaled, the receiver MUST be able to decode
         NAL unit streams that conform to the signaled highest level,
         with the exception that the MaxDpbMbs value in Table A-1 of [1]
         for the signaled highest level is replaced with the value of
         max-dpb * 3 / 8.  Consequently, a receiver that signals max-dpb MUST be
         capable of storing the following number of decoded frames,
         complementary field pairs, and non-paired fields in its decoded
         picture buffer:

            Min(max-dpb * 3 / 8 / ( PicWidthInMbs * FrameHeightInMbs), 16)

         Wherein PicWidthInMbs and FrameHeightInMbs are defined in [1].

         The value of max-dpb MUST be greater than or equal to the value
         of MaxDpbMbs * 3 / 8, wherein the value of MaxDpbMbs is given in
Table A-1 of [1] for the highest level.
         Senders MAY use this knowledge to construct coded video streams
         with improved compression.



------------------------------------End of suggested changes --------------------------------------

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Ye-Kui Wang
Sent: Sunday, March 20, 2011 4:21 AM
To: payload@ietf.org; avt@ietf.org
Subject: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload drafts

Folks,

The three H.264/AVC related payload formats, namely, draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-rtp-svc-27, and draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48 stage.

The RFC-Editor has found the following problem: In draft-ietf-avt-rtp-rfc3984bis-12, the definition of the max-dpb media parameter refers to the MaxDPB that was defined the first version of the H.264/AVC spec, but not any more in the latest version (the 2010 version). The parameter in the latest H.264/AVC version corresponding to MaxDPB is MaxDpbMbs, and the unit of the new parameter (i.e., macroblocks) is different from the original one (i.e. 1024 bytes).

The problem applies also to the SVC payload format, the RCDO payload format, and H.241.

A solution has been found and agreed, involving rfc3984bis authors and some key people related to H.264/AVC (e.g., Gary Sullivan and Heiko Schwarz) and H.241 (e.g., Stephen Botzko and Patrick Luthi). Furthermore, we have found that there are also a couple of places that need fixes due to similar changes from the initial version of H.264/AVC to the latest version.

Per Roni's suggestion, I am sending in below the changes to draft-ietf-avt-rtp-rfc3984bis-12 for review by the Payload and AVTcore WGs. It seems that exactly the same changes are needed to draft-ietf-avt-rtp-h264-rcdo-08 (co-authors of this draft may confirm), and similar but slightly different changes are needed to draft-ietf-avt-rtp-svc-27.

Since the drafts are at the AUTH48 stage, please provide comments by Monday, March 21, if any. Many thanks!

BR, YK



------------------------------------Start of suggested changes --------------------------------------

Section 8.1:
OLD:
      max-cpb: The value of max-cpb is an integer indicating the maximum
         coded picture buffer size in units of 1000 bits for the VCL HRD
         parameters (see A.3.1, item i of [1]) and in units of 1200 bits
         for the NAL HRD parameters (see A.3.1, item j of [1]).
NEW:
      max-cpb: The value of max-cpb is an integer indicating the maximum
         coded picture buffer size. For Constrained Baseline, Baseline, Main
and Extended profiles, the unit is 1000 bits for the VCL HRD
         parameters and 1200 bits for the NAL HRD parameters. For High, High 10,
High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra,
High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles, the unit is cpbBrVclFactor
bits for the VCL HRD and cpbBrNalFactor bits for the NAL HRD parameters.

OLD:

      max-br: The value of max-br is an integer indicating the maximum

         video bitrate in units of 1000 bits per second for the VCL HRD

         parameters (see A.3.1, item i of [1]) and in units of 1200 bits

         per second for the NAL HRD parameters (see A.3.1, item j of

         [1]).
NEW:

      max-br: The value of max-br is an integer indicating the maximum
         video bitrate.  For Constrained Baseline, Baseline, Main
and Extended profiles, the unit is 1000 bits per second for the VCL HRD
         parameters and 1200 bits per second for the NAL HRD parameters. For High, High 10,
High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra,
High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles, the unit is cpbBrVclFactor
bits per second for the VCL HRD and cpbBrNalFactor bits per second for the NAL HRD parameters.


------------------------------------End of suggested changes --------------------------------------



--Boundary_(ID_S2WDxSbD8uh4J8yJq+CNww)
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: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:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:SimSun;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:SimSun;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle28
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
</head>
<body lang="ZH-CN" link="blue" vlink="purple" style="text-justify-trim:punctuation">
<div class="Section1">
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">I think the statement &#8220;</span><span lang="EN-US" style="font-size:11.0pt">The proposed changes to max-dpb, max-cpb and max-br sacrifice some backward compatibility with RFC 3984 and forward compatibility
 with H.264.</span><span lang="EN-US" style="color:#1F497D">&#8221; is incorrect. <o:p>
</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">On backward compatibility with RFC 3984: The semantics in RFC 3984 does not work with color formats other than YUV 4:2:0 and bit depth other than 8 bits, and the new profiles defined in H.264 after
 RFC 3984&#8217;s publication. The proposed changes fix this bug in a way that is backward compatible to RFC 3984, i.e., the fix now covers all color formats and bit depths, while for the video formats and profiles supported in RFC 3984, the bits on the wire remain
 unchanged. Therefore, I don&#8217;t think the changes sacrifice backward compatibility with RFC 3984.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">On the so-called forward compatibility with H.264: &#8220;NOT changing the units of max-cpb and max-br for the high profiles (to include the scaling factors 1.25/3/4)&#8221; means that the numbers in the referred
 H.264 spec must be scaled before they are put into the payload format signaling as specified in the new RFC. Note that whether the scaling factor is considered or not, there is no problem with RFC 3984 backward compatibility. Are you saying you prefer to have
 the scaled units for the semantics of max-cpb and max-br? If yes, could you please explain why that is better?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">BR, YK<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" align="left" style="text-align:left"><b><span lang="EN-US" style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Mo Zanaty (mzanaty) [mailto:mzanaty@cisco.com]
<br>
<b>Sent:</b> Sunday, March 27, 2011 12:23 AM<br>
<b>To:</b> Ye-Kui Wang; payload@ietf.org; avt@ietf.org<br>
<b>Cc:</b> Roni Even; Stephen Botzko; Gary Sullivan<br>
<b>Subject:</b> RE: [AVTCORE] Some changes to rfc3984bis, SVC,and RCDO payload drafts<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">The proposed changes to max-dpb, max-cpb and max-br sacrifice some backward compatibility with RFC 3984 and forward compatibility with H.264. The latter seems intentional but the former seems
 unintentional. Further changes are needed to fix or clearly convey these incompatibilities.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">What was discussed and decided regarding max-dpb, max-cpb and max-br in the ITU/IETF F2F meetings? Based on the original suggested changes (at the end without color coding), forward compatibility
 with H.264 appears to be the focus. But after &#8220;further discussions&#8221;, the newest suggested changes (with color coding) appear focused on backward compatibility with RFC 3984, but don&#8217;t fully achieve this.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">The problem with RFC 3984 backward compatibility is that changing the units of max-dpb (from 1024 bytes to 8/3 macroblocks) only works for the 4:2:0 chroma format, which is the primary format
 used in most profiles and applications. However, the high profiles support other chroma formats, and this change breaks backward compatibility for them.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">For example, consider an RFC 3984 implementation that declares max-dpb=8100 (KB) to support 3 reference frames of 720p at 4:4:4. The proposed change would misinterpret this declaration to mean
 6 reference frames of 720p at any chroma format including 4:4:4, hence potentially overflowing the old RFC 3984 receiver&#8217;s DPB by a factor of 2.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">(Note that H.264 got away with changing MaxDPB since the original 2003 version only supported 4:2:0. When the high profiles which support other chroma formats were added in 2005, MaxDPB was explicitly
 redefined in terms of 4:2:0 so it remains constant across all chroma formats. For further clarity, MaxDpbMbs later replaced MaxDPB. But RFC 3984 never kept up with these changes, so implementations are stuck with the 2003 definitions even for later features
 such as the high profiles and other chroma formats.)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">The problem with H.264 forward compatibility is that NOT changing the units of max-cpb and max-br for the high profiles (to include the scaling factors 1.25/3/4) obviously creates confusion and
 incompatibility between H.264 and this bis draft. This seems like an intentional change after &#8220;further discussions&#8221; decided to focus on RFC 3984 backward compatibility at the expense of H.264 forward compatibility.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Before deciding on specific new text, the WG should decide on whether the focus of this draft should be backward compatibility with RFC 3984 or forward compatibility with H.264. Or if the intent
 is to strike some balance between the two, then clearly convey the intentional incompatibilities in the text.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Mo Zanaty<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p>&nbsp;</o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" align="left" style="text-align:left"><b><span lang="EN-US" style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]
<b>On Behalf Of </b>Ye-Kui Wang<br>
<b>Sent:</b> Monday, March 21, 2011 4:11 AM<br>
<b>To:</b> payload@ietf.org; avt@ietf.org<br>
<b>Subject:</b> Re: [AVTCORE] Some changes to rfc3984bis, SVC,and RCDO payload drafts<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Further discussions with the same group of persons led to a decision to stay with the unscaled units for max-br and max-cpb, thus fewer changes are needed to the three payload formats listed in
 the title and H.241. With this, the changes needed are listed below (the originally suggested changes are dropped from this email). This time I have highlighted the changes, and I have also described the nature the changes below. Hope these may help understand
 better what have been changed, and can lead to a quicker decision by the group, including WG chairs, and our AD.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">BR, YK<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">------------------------------------Start of suggested changes --------------------------------------<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Section 8.1:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">OLD:<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-dpb: The value of max-dpb is an integer indicating the maximum<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; decoded picture buffer size in units of 1024 bytes.&nbsp; The max-<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dpb parameter signals that the receiver has more memory than<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the minimum amount of decoded picture buffer memory required by<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the signaled highest level conveyed in the value of the<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; profile-level-id parameter or the max-recv-level parameter.<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When max-dpb is signaled, the receiver MUST be able to decode<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAL unit streams that conform to the signaled highest level,<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with the exception that the MaxDPB value in Table A-1 of [1]<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the signaled highest level is replaced with the value of<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-dpb.&nbsp; Consequently, a receiver that signals max-dpb MUST be<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; capable of storing the following number of decoded frames,<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; complementary field pairs, and non-paired fields in its decoded<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; picture buffer:<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Min(1024 * max-dpb / ( PicWidthInMbs * FrameHeightInMbs *<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 256 * ChromaFormatFactor ), 16)<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PicWidthInMbs, FrameHeightInMbs, and ChromaFormatFactor are<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;defined in [1].<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The value of max-dpb MUST be greater than or equal to the value<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of MaxDPB given in Table A-1 of [1] for the highest level.<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Senders MAY use this knowledge to construct coded video streams<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with improved compression.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">NEW: <span style="background:aqua;mso-highlight:aqua">
(When this change can be considered as editorial can be discussed, but the nature of this change as follows. On the other hand, if not changed, then the semantics of max-dpb is simply equivalent to unspecified, as MaxDPB and ChromaFormatFactor are not found
 in the latest H.264 spec any more. Note that compared to RFC 3984, the bits on the wire do not change.)</span><o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-dpb: The value of max-dpb is an integer indicating the maximum<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; decoded picture buffer size in units of 8/3 macroblocks.&nbsp; The max-<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dpb parameter signals that the receiver has more memory than<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the minimum amount of decoded picture buffer memory required by<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the signaled highest level conveyed in the value of the<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; profile-level-id parameter or the max-recv-level parameter.<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When max-dpb is signaled, the receiver MUST be able to decode<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAL unit streams that conform to the signaled highest level,<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with the exception that
<span style="background:yellow;mso-highlight:yellow">the MaxDpbMbs value in Table A-1 of [1]<o:p></o:p></span></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun;background:yellow;mso-highlight:
yellow">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the signaled highest level is replaced with the value of<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun;background:yellow;mso-highlight:
yellow">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-dpb * 3 / 8</span><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">.&nbsp;
 Consequently, a receiver that signals max-dpb MUST be<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; capable of storing the following number of decoded frames,<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; complementary field pairs, and non-paired fields in its decoded<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; picture buffer:<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<span style="background:yellow;mso-highlight:yellow">Min(max-dpb * 3 / 8 / ( PicWidthInMbs * FrameHeightInMbs), 16)<o:p></o:p></span></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun;background:yellow;mso-highlight:
yellow"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun;background:yellow;mso-highlight:
yellow">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Wherein PicWidthInMbs and FrameHeightInMbs are defined in [1].</span><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun"><o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The value of max-dpb MUST be greater than or equal to the value<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of
<span style="background:yellow;mso-highlight:yellow">MaxDpbMbs * 3 / 8, wherein the value of MaxDpbMbs is given in
<o:p></o:p></span></span></p>
<p class="MsoNormal" align="left" style="text-align:left;text-indent:54.0pt"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun;background:yellow;
mso-highlight:yellow">Table A-1 of [1] for the highest level.</span><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun"><o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Senders MAY use this knowledge to construct coded video streams<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with improved compression.<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">------------------------------------End of suggested changes --------------------------------------<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" align="left" style="text-align:left"><b><span lang="EN-US" style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]
<b>On Behalf Of </b>Ye-Kui Wang<br>
<b>Sent:</b> Sunday, March 20, 2011 4:21 AM<br>
<b>To:</b> payload@ietf.org; avt@ietf.org<br>
<b>Subject:</b> [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload drafts<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Folks,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">The three H.264/AVC related payload formats, namely, draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-rtp-svc-27, and draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48 stage.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">The RFC-Editor has found the following problem: In draft-ietf-avt-rtp-rfc3984bis-12, the definition of the max-dpb media parameter refers to the MaxDPB that was defined the first version of the H.264/AVC spec, but not
 any more in the latest version (the 2010 version). The parameter in the latest H.264/AVC version corresponding to MaxDPB is MaxDpbMbs, and the unit of the new parameter (i.e., macroblocks) is different from the original one (i.e. 1024 bytes).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">The problem applies also to the SVC payload format, the RCDO payload format, and H.241.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">A solution has been found and agreed, involving rfc3984bis authors and some key people related to H.264/AVC (e.g., Gary Sullivan and Heiko Schwarz) and H.241 (e.g., Stephen Botzko and Patrick Luthi). Furthermore, we have
 found that there are also a couple of places that need fixes due to similar changes from the initial version of H.264/AVC to the latest version.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Per Roni&#8217;s suggestion, I am sending in below the changes to draft-ietf-avt-rtp-rfc3984bis-12 for review by the Payload and AVTcore WGs. It seems that exactly the same changes are needed to draft-ietf-avt-rtp-h264-rcdo-08
 (co-authors of this draft may confirm), and similar but slightly different changes are needed to draft-ietf-avt-rtp-svc-27.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Since the drafts are at the AUTH48 stage, please provide comments by Monday, March 21, if any. Many thanks!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">BR, YK<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">------------------------------------Start of suggested changes --------------------------------------<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Section 8.1:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">OLD:<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-cpb: The value of max-cpb is an integer indicating the maximum<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; coded picture buffer size in units of 1000 bits for the VCL HRD<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; parameters (see A.3.1, item i of [1]) and in units of 1200 bits<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the NAL HRD parameters (see A.3.1, item j of [1]).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">NEW:<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-cpb: The value of max-cpb is an integer indicating the maximum<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; coded picture buffer size. For Constrained Baseline, Baseline, Main
<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left;text-indent:54.0pt"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">and Extended profiles, the unit is 1000 bits for the VCL HRD<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; parameters and 1200 bits for the NAL HRD parameters. For High, High 10,<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left;text-indent:54.0pt"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra,
<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left;text-indent:54.0pt"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles, the unit is cpbBrVclFactor<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left;text-indent:54.0pt"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">bits for the VCL HRD and cpbBrNalFactor bits for the NAL HRD parameters.<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">OLD:<o:p></o:p></span></p>
<pre><span lang="EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-br: The value of max-br is an integer indicating the maximum<o:p></o:p></span></pre>
<pre><span lang="EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; video bitrate in units of 1000 bits per second for the VCL HRD<o:p></o:p></span></pre>
<pre><span lang="EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; parameters (see A.3.1, item i of [1]) and in units of 1200 bits<o:p></o:p></span></pre>
<pre><span lang="EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; per second for the NAL HRD parameters (see A.3.1, item j of<o:p></o:p></span></pre>
<pre><span lang="EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [1]).<o:p></o:p></span></pre>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">NEW: <o:p></o:p></span></p>
<pre><span lang="EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; max-br: The value of max-br is an integer indicating the maximum<o:p></o:p></span></pre>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; video bitrate.&nbsp; For Constrained Baseline, Baseline, Main
<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left;text-indent:54.0pt"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">and Extended profiles, the unit is 1000 bits per second for the VCL HRD<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; parameters and 1200 bits per second for the NAL HRD parameters. For High, High 10,<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left;text-indent:54.0pt"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">High 4:2:2, High 4:4:4 Predictive, High 10 Intra, High 4:2:2 Intra,
<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left;text-indent:54.0pt"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">High 4:4:4 Intra and CAVLC 4:4:4 Intra profiles, the unit is cpbBrVclFactor<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left;text-indent:54.0pt"><span lang="EN-US" style="font-size:12.0pt;font-family:SimSun">bits per second for the VCL HRD and cpbBrNalFactor bits per second for the NAL HRD parameters.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">------------------------------------End of suggested changes --------------------------------------<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--Boundary_(ID_S2WDxSbD8uh4J8yJq+CNww)--

From sunseawq@huawei.com  Mon Mar 28 00:58:32 2011
Return-Path: <sunseawq@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 297313A6903 for <avt@core3.amsl.com>; Mon, 28 Mar 2011 00:58:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.494
X-Spam-Level: 
X-Spam-Status: No, score=-4.494 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4BeC5pZweCvZ for <avt@core3.amsl.com>; Mon, 28 Mar 2011 00:58:31 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id F36413A68F1 for <avt@ietf.org>; Mon, 28 Mar 2011 00:58:30 -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 <0LIR000EPCULYU@szxga03-in.huawei.com> for avt@ietf.org; Mon, 28 Mar 2011 15:59:09 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LIR0006BCULQX@szxga03-in.huawei.com> for avt@ietf.org; Mon, 28 Mar 2011 15:59:09 +0800 (CST)
Received: from jys1037575 (dhcp-104a.meeting.ietf.org [130.129.16.74]) by szxml12-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LIR00NH3CUA01@szxml12-in.huawei.com> for avt@ietf.org; Mon, 28 Mar 2011 15:59:09 +0800 (CST)
Date: Mon, 28 Mar 2011 09:58:52 +0200
From: Qin Wu <sunseawq@huawei.com>
To: IETF AVTCore WG <avt@ietf.org>
Message-id: <9567E54DB2554037992DBBFFC8C57E67@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: multipart/alternative; boundary="Boundary_(ID_L69TFpHusi8G1wfM4UysPQ)"
X-Priority: 3
X-MSMail-priority: Normal
Subject: [AVTCORE] The new version of draft-hunt-avtcore-monarch-02
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 07:58:32 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_L69TFpHusi8G1wfM4UysPQ)
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT

Hi,folks:
Just let you know, the new versionn has just been submitted. It is available at:
http://www.ietf.org/id/draft-hunt-avtcore-monarch-02.txt

Regard!
-Qin

--Boundary_(ID_L69TFpHusi8G1wfM4UysPQ)
Content-type: text/html; charset=gb2312
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=gb2312">
<META content="MSHTML 6.00.2900.6058" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face="Times New Roman">Hi,folks:</FONT></DIV>
<DIV><FONT face="Times New Roman">Just let you know, the new versionn has just 
been submitted. It is available at:</FONT></DIV>
<DIV><FONT face="Times New Roman"><A 
href="http://www.ietf.org/id/draft-hunt-avtcore-monarch-02.txt">http://www.ietf.org/id/draft-hunt-avtcore-monarch-02.txt</A></FONT></DIV>
<DIV><FONT face="Times New Roman"></FONT>&nbsp;</DIV>
<DIV><FONT face="Times New Roman">Regard!</FONT></DIV>
<DIV><FONT face="Times New Roman">-Qin</FONT></DIV></BODY></HTML>

--Boundary_(ID_L69TFpHusi8G1wfM4UysPQ)--

From jonathan@vidyo.com  Mon Mar 28 02:06:42 2011
Return-Path: <jonathan@vidyo.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 40E633A6953 for <avt@core3.amsl.com>; Mon, 28 Mar 2011 02:06:42 -0700 (PDT)
X-Quarantine-ID: <izl1DKtpztjb>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, MIME error: error: illegal encoding [base64] for MIME type message/external-body
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id izl1DKtpztjb for <avt@core3.amsl.com>; Mon, 28 Mar 2011 02:06:41 -0700 (PDT)
Received: from mx1.myoutlookonline.com (mx1.myoutlookonline.com [64.95.72.238]) by core3.amsl.com (Postfix) with ESMTP id AC48F3A68BB for <avt@ietf.org>; Mon, 28 Mar 2011 02:06:40 -0700 (PDT)
Received: from st23.mx1.myoutlookonline.com (localhost [127.0.0.1]) by mx1.myoutlookonline.com (Postfix) with ESMTP id E5007416D50 for <avt@ietf.org>; Mon, 28 Mar 2011 05:08:17 -0400 (EDT)
X-Virus-Scanned: by SpamTitan at mail.lan
Received: from HUB025.mail.lan (unknown [10.110.2.1]) by mx1.myoutlookonline.com (Postfix) with ESMTP id 8122A416D7B for <avt@ietf.org>; Mon, 28 Mar 2011 05:08:17 -0400 (EDT)
Received: from BE235.mail.lan ([10.110.32.235]) by HUB025.mail.lan ([10.110.17.25]) with mapi; Mon, 28 Mar 2011 05:07:23 -0400
From: Jonathan Lennox <jonathan@vidyo.com>
To: "avt@ietf.org" <avt@ietf.org>
Date: Mon, 28 Mar 2011 05:08:15 -0400
Thread-Topic: I-D Action:draft-lennox-avtcore-srtp-encrypted-header-ext-00.txt
Thread-Index: AcvtJ5Sfs6qb7M/0TQy7wg8IIjslhg==
Message-ID: <17CE6EA0-074D-43BD-990F-467F0A8708BD@vidyo.com>
References: <20110328090001.18465.38410.idtracker@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/mixed; boundary="_003_17CE6EA0074D43BD990F467F0A8708BDvidyocom_"
MIME-Version: 1.0
Subject: [AVTCORE] Fwd: I-D Action:draft-lennox-avtcore-srtp-encrypted-header-ext-00.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 09:06:42 -0000

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

Hello, all --

I've updated my draft on encrypting RTP header extensions, targeting the dr=
aft at the AVTCore WG, in the hope that the group will find it a suitable s=
tarting point for the WG milestone.

This version of the draft has no substantial changes from draft-lennox-avt-=
srtp-encrypted-extension-headers-02, only the name change and some referenc=
e updates.

Begin forwarded message:

> From: "Internet-Drafts@ietf.org" <Internet-Drafts@ietf.org>
> Date: March 28, 2011 11:00:01 AM GMT+02:00
> To: "i-d-announce@ietf.org" <i-d-announce@ietf.org>
> Subject: I-D Action:draft-lennox-avtcore-srtp-encrypted-header-ext-00.txt
> Reply-To: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>=20
> 	Title           : Encryption of Header Extensions in the Secure Real-Tim=
e Transport Protocol (SRTP)
> 	Author(s)       : J. Lennox
> 	Filename        : draft-lennox-avtcore-srtp-encrypted-header-ext-00.txt
> 	Pages           : 8
> 	Date            : 2011-03-28
>=20
> The Secure Real-Time Transport Protocol (SRTP) provides
> authentication, but not encryption, of the headers of Real-Time
> Transport Protocol (RTP) packets.  However, RTP header extensions may
> carry sensitive information for which participants in multimedia
> sessions want confidentiality.  This document provides a mechanism,
> extending the mechanisms of SRTP, to selectively encrypt RTP header
> extensions in SRTP.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-lennox-avtcore-srtp-encrypted-h=
eader-ext-00.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.

--_003_17CE6EA0074D43BD990F467F0A8708BDvidyocom_
Content-Type: message/external-body;
	name="draft-lennox-avtcore-srtp-encrypted-header-ext-00.url"
Content-Description: draft-lennox-avtcore-srtp-encrypted-header-ext-00.url
Content-Disposition: attachment;
	filename="draft-lennox-avtcore-srtp-encrypted-header-ext-00.url"; size=357;
	creation-date="Mon, 28 Mar 2011 05:07:36 GMT";
	modification-date="Mon, 28 Mar 2011 05:07:36 GMT"
Content-Transfer-Encoding: base64


Q29udGVudC1EaXNwb3NpdGlvbjogYXR0YWNobWVudDsNCglmaWxlbmFtZT0iZHJhZnQtbGVubm94
LWF2dGNvcmUtc3J0cC1lbmNyeXB0ZWQtaGVhZGVyLWV4dC0wMC51cmwiDQpDb250ZW50LVR5cGU6
IG1lc3NhZ2UvZXh0ZXJuYWwtYm9keTsNCgluYW1lPSJkcmFmdC1sZW5ub3gtYXZ0Y29yZS1zcnRw
LWVuY3J5cHRlZC1oZWFkZXItZXh0LTAwLnVybCINCkNvbnRlbnQtVHJhbnNmZXItRW5jb2Rpbmc6
IDdiaXQNCg0KW0ludGVybmV0U2hvcnRjdXRdPEJSPlVSTD1mdHA6Ly9mdHAuaWV0Zi5vcmcvaW50
ZXJuZXQtZHJhZnRzL2RyYWZ0LWxlbm5veC1hdnRjb3JlLXNydHAtZW5jcnlwdGVkLWhlYWRlci1l
eHQtMDAudHh0PEJSPg0K

--_003_17CE6EA0074D43BD990F467F0A8708BDvidyocom_
Content-Type: text/plain; name="ATT00001.txt"
Content-Description: ATT00001.txt
Content-Disposition: attachment; filename="ATT00001.txt"; size=317;
	creation-date="Mon, 28 Mar 2011 05:07:36 GMT";
	modification-date="Mon, 28 Mar 2011 05:07:36 GMT"
Content-Transfer-Encoding: base64

PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBJLUQt
QW5ub3VuY2UgbWFpbGluZyBsaXN0DQo+IEktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KPiBodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ktZC1hbm5vdW5jZQ0KPiBJbnRlcm5ldC1E
cmFmdCBkaXJlY3RvcmllczogaHR0cDovL3d3dy5pZXRmLm9yZy9zaGFkb3cuaHRtbA0KPiBvciBm
dHA6Ly9mdHAuaWV0Zi5vcmcvaWV0Zi8xc2hhZG93LXNpdGVzLnR4dA0KDQotLQ0KSm9uYXRoYW4g
TGVubm94DQpqb25hdGhhbkB2aWR5by5jb20NCg0KDQo=

--_003_17CE6EA0074D43BD990F467F0A8708BDvidyocom_--

From versteb@cisco.com  Mon Mar 28 02:08:19 2011
Return-Path: <versteb@cisco.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EFAD63A6878 for <avt@core3.amsl.com>; Mon, 28 Mar 2011 02:08:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VYaP3WgdR9j5 for <avt@core3.amsl.com>; Mon, 28 Mar 2011 02:08:18 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id DDD0F3A68B1 for <avt@ietf.org>; Mon, 28 Mar 2011 02:08:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=versteb@cisco.com; l=2858; q=dns/txt; s=iport; t=1301303396; x=1302512996; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=sTiWwm/czHw4M0mHbRTdHXFMk0Ps3mMz34m9aN/+K9w=; b=kv0tyQeQWwavhRWTrEF0fseQED76hrKIKO1fkvDwneT9gqprcTGmNFhf m1SLIKntw/tHHL8CuTmlSOaCz/kIVxIlZLtzWcycTd/ghiGiox4eTgmwS s55GxCL7xoDMQMrdACPlJZhb+DI6czBHCRY/fvPvbhiCVEDpzARtywlJh Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvwAAFhPkE2tJV2d/2dsb2JhbACYDY09d6YwmzUChWcEhTqLFw
X-IronPort-AV: E=Sophos;i="4.63,253,1299456000"; d="scan'208";a="281568042"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by sj-iport-4.cisco.com with ESMTP; 28 Mar 2011 09:09:56 +0000
Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core-6.cisco.com (8.14.3/8.14.3) with ESMTP id p2S99tkK019904;  Mon, 28 Mar 2011 09:09:55 GMT
Received: from xmb-rcd-213.cisco.com ([72.163.62.220]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 28 Mar 2011 04:09:56 -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: Mon, 28 Mar 2011 04:09:53 -0500
Message-ID: <EE933D92D054D14089A336CC71A5CCA603CDEFBE@XMB-RCD-213.cisco.com>
In-Reply-To: <4D8DBEDB.4090406@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVTCORE] Comments ondraft-vancaenegem-avtcore-fb-supp-and-retransm-00
Thread-Index: AcvroBEwlJa4ELehTSSAK8PcA32LWQBhixTw
References: <4D8DBEDB.4090406@ericsson.com>
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>, "IETF AVTCore WG" <avt@ietf.org>, "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.com>
X-OriginalArrivalTime: 28 Mar 2011 09:09:56.0312 (UTC) FILETIME=[E810E580:01CBED27]
Subject: Re: [AVTCORE] Comments ondraft-vancaenegem-avtcore-fb-supp-and-retransm-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 09:08:20 -0000

Correlated loss in a multicast RTP system is a real problem, =
particularly in commercial IPTV systems. Tom's draft begins the =
discussion of this important area, and the small section on distributed =
repair is particularly important. We need to continue to think about =
standard mechanisms to have the FT/RS device handle loss to large =
populations of receivers.=20

The topology that is most interesting to me is when there is a =
well-defined mapping from a set of SSM receivers to combined FT/RS =
devices. In other words, IPTV systems often use SSM and put a =
repair/RAMS device at the edge of the service provider network. The FT =
and RS devices are co-resident in a single physical device. This device =
is the focus point for error recovery and thus NACK suppression. This is =
not the only topology that we should consider, but it should be strongly =
considered.

I have some experience in this area and would like to help with this =
analysis.

Bill VerSteeg

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of =
Magnus Westerlund
Sent: Saturday, March 26, 2011 11:24 AM
To: IETF AVTCore WG; VAN CAENEGEM Tom
Subject: [AVTCORE] Comments =
ondraft-vancaenegem-avtcore-fb-supp-and-retransm-00

Tom, AVTCORE,

I have reviewed this draft and have the following comment.

To me it appears that one big reason for the issues is actually that we
haven't specified how RTP retransmission in SSM with unicast delivery is
supposed to work. Because if that was well defined we would likely have
concluded that one should not forward NACK request to the DS from a FT
for any request it service locally.

Thus as I raised before in relation to the RAMS work that there appeared
to be a need for defining this properly, including this aspect. Do we
have anyone that is interested in defining this?

Secondly I think there clearly are some improvements needed of the WG
document based on what you comment. One thing is clearly to clarify the
WG document on its usages, and then map those usages of suppression to
different topologies.

My personal opinion on how to handle your comments are to include your
concerns in the WG document.

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

From Even.roni@huawei.com  Mon Mar 28 08:20:01 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 46AE93A6820; Mon, 28 Mar 2011 08:20:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.917
X-Spam-Level: 
X-Spam-Status: No, score=-100.917 tagged_above=-999 required=5 tests=[AWL=3.577, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DxlYRwMHCnvf; Mon, 28 Mar 2011 08:19:56 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id DDAA73A67D6; Mon, 28 Mar 2011 08:19:45 -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 <0LIR000AKXB8YU@szxga03-in.huawei.com>; Mon, 28 Mar 2011 23:21:08 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LIR007DHXB8TK@szxga03-in.huawei.com>; Mon, 28 Mar 2011 23:21:08 +0800 (CST)
Received: from windows8d787f9 (dhcp-1164.meeting.ietf.org [130.129.17.100]) by szxml12-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LIR00FFOXASMM@szxml12-in.huawei.com>; Mon, 28 Mar 2011 23:21:08 +0800 (CST)
Date: Mon, 28 Mar 2011 17:20:32 +0200
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <003501cbec3f$2d8448d0$888cda70$%roni@huawei.com>
To: 'Ye-Kui Wang' <yekui.wang@huawei.com>, payload@ietf.org, avt@ietf.org
Message-id: <001b01cbed5b$b7162600$25427200$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_z1bTfMJCnOpvzTDtOO/49w)"
Content-language: en-us
Thread-index: Acvm161AAF2A6AC0R/ODLEMZyh1IcgAwzyEAAIkXUFAAnXzNcAACDXKAAEZuowA=
References: <B2DE0AFA86565C47BD3A8435550F9553030CFF66@XMB-RCD-201.cisco.com> <003501cbec3f$2d8448d0$888cda70$%roni@huawei.com>
Cc: 'Gary Sullivan' <garysull@microsoft.com>, 'Roni Even' <Even.roni@huawei.com>
Subject: Re: [AVTCORE] [payload]  Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 15:20:01 -0000

This is a multi-part message in MIME format.

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

YK,

Maybe it will be helpful to add the assumption about 4:2:0 8-bit support in
RFC3984 systems to the new 3984bis draft to clarify that you need to support
the new parameter if you are using other color schemes

Roni

 

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Roni
Even
Sent: Sunday, March 27, 2011 7:24 AM
To: 'Mo Zanaty (mzanaty)'; 'Ye-Kui Wang'; payload@ietf.org; avt@ietf.org
Cc: 'Gary Sullivan'
Subject: Re: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and RCDO
payload drafts

 

HI Mo,

When the solution was discussed there are two assumptions

1.        Old implementations (RFC3984) expecting the maxdpb parameter in
kbyes only supported 4:2:0 8-bit and no other color because otherwise using
only Kbytes and not macro blocks will not work for them. New
implementation(RFC6184 - the assigned RFC number to 3984bis) expects a value
in macroblocks and will interpret the value in maxdpb as macroblocks.

So see my comments inline

Roni Even

As individual

 

Further discussions with the same group of persons led to a decision to stay
with the unscaled units for max-br and max-cpb, thus fewer changes are
needed to the three payload formats listed in the title and H.241. With
this, the changes needed are listed below (the originally suggested changes
are dropped from this email). This time I have highlighted the changes, and
I have also described the nature the changes below. Hope these may help
understand better what have been changed, and can lead to a quicker decision
by the group, including WG chairs, and our AD.

 

BR, YK

 

------------------------------------Start of suggested changes
--------------------------------------


--Boundary_(ID_z1bTfMJCnOpvzTDtOO/49w)
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: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";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:SimSun;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:SimSun;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle28
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
p.msopla, li.msopla, div.msopla
	{mso-style-name:msopla;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle31
	{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.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:484593867;
	mso-list-type:hybrid;
	mso-list-template-ids:-354640490 -1632847936 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-bidi-font-family:Arial;
	color:#1F497D;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple style='text-justify-trim:punctuation'><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>YK,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Maybe it will be helpful to add the assumption about </span><span style='font-size:11.0pt;color:#1F497D'>4:2:0 8-bit support in RFC3984 systems to the new 3984bis draft to clarify that you need to support the new parameter if you are using other color schemes<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Roni</span><span style='font-size:11.0pt;color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;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=Mso
 Normal a
gn:left'><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> Sunday, March 27, 2011 7:24 AM<br><b>To:</b> 'Mo Zanaty (mzanaty)'; 'Ye-Kui Wang'; payload@ietf.org; avt@ietf.org<br><b>Cc:</b> 'Gary Sullivan'<br><b>Subject:</b> Re: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and RCDO payload drafts<o:p></o:p></span></p></div></div><p class=MsoNormal align=left style='text-align:left'><o:p>&nbsp;</o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>HI Mo,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>When the solution was discussed there are two assumptions<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='font-size:11.0pt;color:#1F497D'><spa
 n style=
 style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span dir=LTR></span><span style='font-size:11.0pt;color:#1F497D'>&nbsp;Old implementations (RFC3984) expecting the maxdpb parameter in kbyes only supported 4:2:0 8-bit and no other color because otherwise using only Kbytes and not macro blocks will not work for them. New implementation(RFC6184 &#8211; the assigned RFC number to 3984bis) expects a value in macroblocks and will interpret the value in maxdpb as macroblocks.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>So see my comments inline<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Roni Even<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>As individual<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><div style='border:none;border-left:soli
 d blue 1
4.0pt'><div><p class=MsoNormal align=left style='text-align:left'><span style='font-size:11.0pt;font-family:"Times New Roman","serif";color:#1F497D'>Further discussions with the same group of persons led to a decision to stay with the unscaled units for max-br and max-cpb, thus fewer changes are needed to the three payload formats listed in the title and H.241. With this, the changes needed are listed below (the originally suggested changes are dropped from this email). This time I have highlighted the changes, and I have also described the nature the changes below. Hope these may help understand better what have been changed, and can lead to a quicker decision by the group, including WG chairs, and our AD.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>BR, YK<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainT
 ext>----
-------Start of suggested changes --------------------------------------<o:p></o:p></p></div></div></div></div></body></html>

--Boundary_(ID_z1bTfMJCnOpvzTDtOO/49w)--

From yekui.wang@huawei.com  Mon Mar 28 12:01:27 2011
Return-Path: <yekui.wang@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A4CEB3A691D; Mon, 28 Mar 2011 12:01:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.508
X-Spam-Level: 
X-Spam-Status: No, score=-6.508 tagged_above=-999 required=5 tests=[AWL=0.090,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0mZ1YVjii8ZB; Mon, 28 Mar 2011 12:01:22 -0700 (PDT)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id BB9F43A6A6B; Mon, 28 Mar 2011 12:01:06 -0700 (PDT)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LIS00G6Y7KIG2@usaga02-in.huawei.com>; Mon, 28 Mar 2011 12:02:43 -0700 (PDT)
Received: from dfweml201-edg.china.huawei.com ([172.18.9.107]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPS id <0LIS00LJH7KIND@usaga02-in.huawei.com>; Mon, 28 Mar 2011 12:02:42 -0700 (PDT)
Received: from DFWEML402-HUB.china.huawei.com (10.193.5.102) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.270.1; Mon, 28 Mar 2011 12:02:40 -0700
Received: from DFWEML503-MBX.china.huawei.com ([169.254.3.54]) by DFWEML402-HUB.china.huawei.com ([::1]) with mapi id 14.01.0270.001; Mon, 28 Mar 2011 12:02:40 -0700
Date: Mon, 28 Mar 2011 19:02:40 +0000
From: Ye-Kui Wang <yekui.wang@huawei.com>
In-reply-to: <001b01cbed5b$b7162600$25427200$%roni@huawei.com>
X-Originating-IP: [10.193.125.214]
To: Roni Even <Even.roni@huawei.com>, "payload@ietf.org" <payload@ietf.org>, "avt@ietf.org" <avt@ietf.org>
Message-id: <B99DECD58A94E143BA6F1508CC688351051F95C4@dfweml503-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_wtkyw5gZZqpWBpUp+0gzEA)"
Content-language: en-US
Accept-Language: en-US
Thread-topic: [AVTCORE] [payload]  Some changes to rfc3984bis, SVC, and RCDO payload drafts
Thread-index: AQHL7Xq13hWH9Vft5kKbNdH/qp/OIg==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <B2DE0AFA86565C47BD3A8435550F9553030CFF66@XMB-RCD-201.cisco.com> <003501cbec3f$2d8448d0$888cda70$%roni@huawei.com> <001b01cbed5b$b7162600$25427200$%roni@huawei.com>
Cc: 'Gary Sullivan' <garysull@microsoft.com>
Subject: Re: [AVTCORE] [payload]  Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 19:01:27 -0000

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

Hi Roni,

Yes, we can add some notes to clarify the reason for the changes and that the changes are backward compatible to RFC 3984. If people feel that other notes would be helpful too, please propose, I think we are open to all such additions as long as they would be helpful for readers and implementers.

BR, YK

From: Roni Even [mailto:even.roni@huawei.com]
Sent: Monday, March 28, 2011 11:21 AM
To: Ye-Kui Wang; payload@ietf.org; avt@ietf.org
Cc: 'Gary Sullivan'; 'Roni Even'; 'Mo Zanaty (mzanaty)'
Subject: RE: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and RCDO payload drafts

YK,
Maybe it will be helpful to add the assumption about 4:2:0 8-bit support in RFC3984 systems to the new 3984bis draft to clarify that you need to support the new parameter if you are using other color schemes
Roni

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Roni Even
Sent: Sunday, March 27, 2011 7:24 AM
To: 'Mo Zanaty (mzanaty)'; 'Ye-Kui Wang'; payload@ietf.org; avt@ietf.org
Cc: 'Gary Sullivan'
Subject: Re: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and RCDO payload drafts

HI Mo,
When the solution was discussed there are two assumptions

1.        Old implementations (RFC3984) expecting the maxdpb parameter in kbyes only supported 4:2:0 8-bit and no other color because otherwise using only Kbytes and not macro blocks will not work for them. New implementation(RFC6184 - the assigned RFC number to 3984bis) expects a value in macroblocks and will interpret the value in maxdpb as macroblocks.
So see my comments inline
Roni Even
As individual

Further discussions with the same group of persons led to a decision to stay with the unscaled units for max-br and max-cpb, thus fewer changes are needed to the three payload formats listed in the title and H.241. With this, the changes needed are listed below (the originally suggested changes are dropped from this email). This time I have highlighted the changes, and I have also described the nature the changes below. Hope these may help understand better what have been changed, and can lead to a quicker decision by the group, including WG chairs, and our AD.

BR, YK


------------------------------------Start of suggested changes --------------------------------------

--Boundary_(ID_wtkyw5gZZqpWBpUp+0gzEA)
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: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:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:SimSun;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:SimSun;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
p.msopla, li.msopla, div.msopla
	{mso-style-name:msopla;
	mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle28
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle29
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle30
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle31
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle32
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:484593867;
	mso-list-type:hybrid;
	mso-list-template-ids:-354640490 -1632847936 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-bidi-font-family:Arial;
	color:#1F497D;}
@list l0:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="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="ZH-CN" link="blue" vlink="purple" style="text-justify-trim:punctuation">
<div class="Section1">
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Hi Roni,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Yes, we can add some notes to clarify the reason for the changes and that the changes are backward compatible to RFC 3984. If people feel that other notes would be helpful too, please propose, I
 think we are open to all such additions as long as they would be helpful for readers and implementers.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">BR, YK<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" align="left" style="text-align:left"><b><span lang="EN-US" style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Roni Even [mailto:even.roni@huawei.com]
<br>
<b>Sent:</b> Monday, March 28, 2011 11:21 AM<br>
<b>To:</b> Ye-Kui Wang; payload@ietf.org; avt@ietf.org<br>
<b>Cc:</b> 'Gary Sullivan'; 'Roni Even'; 'Mo Zanaty (mzanaty)'<br>
<b>Subject:</b> RE: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and RCDO payload drafts<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">YK,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">Maybe it will be helpful to add the assumption about 4:2:0 8-bit support in RFC3984 systems to the new 3984bis draft to clarify that you need to support the new parameter if you
 are using other color schemes<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">Roni<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" align="left" style="text-align:left"><b><span lang="EN-US" style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]
<b>On Behalf Of </b>Roni Even<br>
<b>Sent:</b> Sunday, March 27, 2011 7:24 AM<br>
<b>To:</b> 'Mo Zanaty (mzanaty)'; 'Ye-Kui Wang'; payload@ietf.org; avt@ietf.org<br>
<b>Cc:</b> 'Gary Sullivan'<br>
<b>Subject:</b> Re: [AVTCORE] [payload] Some changes to rfc3984bis, SVC, and RCDO payload drafts<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">HI Mo,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">When the solution was discussed there are two assumptions<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo2"><![if !supportLists]><span lang="EN-US" style="font-size:11.0pt;color:#1F497D"><span style="mso-list:Ignore">1.<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">&nbsp;Old implementations (RFC3984) expecting the maxdpb parameter in kbyes only supported 4:2:0 8-bit and no other color because otherwise using only Kbytes and not macro blocks
 will not work for them. New implementation(RFC6184 &#8211; the assigned RFC number to 3984bis) expects a value in macroblocks and will interpret the value in maxdpb as macroblocks.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">So see my comments inline<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">Roni Even<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">As individual<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<p class="MsoNormal" align="left" style="text-align:left"><span lang="EN-US" style="font-size:11.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;color:#1F497D">Further discussions with the same group of persons led to a decision to stay with the unscaled units for
 max-br and max-cpb, thus fewer changes are needed to the three payload formats listed in the title and H.241. With this, the changes needed are listed below (the originally suggested changes are dropped from this email). This time I have highlighted the changes,
 and I have also described the nature the changes below. Hope these may help understand better what have been changed, and can lead to a quicker decision by the group, including WG chairs, and our AD.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">BR, YK<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p>&nbsp;</o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">------------------------------------Start of suggested changes --------------------------------------<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>

--Boundary_(ID_wtkyw5gZZqpWBpUp+0gzEA)--

From petithug@acm.org  Tue Mar 29 03:26:37 2011
Return-Path: <petithug@acm.org>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A6F9F28C0F5 for <avt@core3.amsl.com>; Tue, 29 Mar 2011 03:26:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.146
X-Spam-Level: 
X-Spam-Status: No, score=-102.146 tagged_above=-999 required=5 tests=[AWL=0.119, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BzbHrBDU5nB1 for <avt@core3.amsl.com>; Tue, 29 Mar 2011 03:26:36 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91]) by core3.amsl.com (Postfix) with ESMTP id C50393A6947 for <avt@ietf.org>; Tue, 29 Mar 2011 03:26:36 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001) id 49A21DBCC046; Tue, 29 Mar 2011 10:28:14 +0000 (UTC)
Received: from [130.129.70.114] (server.implementers.org [127.0.0.1]) by server.implementers.org (Postfix) with ESMTPA id AF06CDBCC044 for <avt@ietf.org>; Tue, 29 Mar 2011 10:28:13 +0000 (UTC)
Message-ID: <4D91B43B.1090807@acm.org>
Date: Tue, 29 Mar 2011 12:28:11 +0200
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.4) Gecko/20100718 Icedove/3.1
MIME-Version: 1.0
To: AVT WG <avt@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [AVTCORE] RTCP in Overlay Multicast
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Mar 2011 10:26:37 -0000

We talked briefly yesterday in the AVT session about this milestone:

Dec 2011 Submit Real-Time Transport Control Protocol (RTCP) in Overlay Multicast
for Proposed Standard

The general subject of Overlay Multicast is something I am interested in, but is 
there any pointer to what that milestone would be about (paper, i-d, email 
exchange, etc...)

Thanks.

-- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org

From keith.drage@alcatel-lucent.com  Tue Mar 29 03:46:18 2011
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2A3D828C152 for <avt@core3.amsl.com>; Tue, 29 Mar 2011 03:46:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.992
X-Spam-Level: 
X-Spam-Status: No, score=-105.992 tagged_above=-999 required=5 tests=[AWL=0.257, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SjSGnZ8FbCSo for <avt@core3.amsl.com>; Tue, 29 Mar 2011 03:46:17 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by core3.amsl.com (Postfix) with ESMTP id C9AD928C108 for <avt@ietf.org>; Tue, 29 Mar 2011 03:46:16 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p2TAld0d007490 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 29 Mar 2011 12:47:49 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Tue, 29 Mar 2011 12:47:43 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Marc Petit-Huguenin <petithug@acm.org>, AVT WG <avt@ietf.org>
Date: Tue, 29 Mar 2011 12:47:42 +0200
Thread-Topic: [AVTCORE] RTCP in Overlay Multicast
Thread-Index: Acvt/AqHU72RgjO/Ra2/Of0NYzZNgwAAo6lg
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE21EB2B237@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <4D91B43B.1090807@acm.org>
In-Reply-To: <4D91B43B.1090807@acm.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
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.83
Subject: Re: [AVTCORE] RTCP in Overlay Multicast
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Mar 2011 10:46:18 -0000

The document that formed the basis for the milestone existing was:

http://tools.ietf.org/id/draft-ott-avt-rtcp-overlay-multicast-02.txt

Jorg Ott is certainly at this meeting. I'm sure he could fill you in on mor=
e details.

Regards

Keith

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Mar=
c
> Petit-Huguenin
> Sent: 29 March 2011 11:28
> To: AVT WG
> Subject: [AVTCORE] RTCP in Overlay Multicast
>=20
> We talked briefly yesterday in the AVT session about this milestone:
>=20
> Dec 2011 Submit Real-Time Transport Control Protocol (RTCP) in Overlay
> Multicast
> for Proposed Standard
>=20
> The general subject of Overlay Multicast is something I am interested in,
> but is
> there any pointer to what that milestone would be about (paper, i-d, emai=
l
> exchange, etc...)
>=20
> Thanks.
>=20
> --
> Marc Petit-Huguenin
> Personal email: marc@petit-huguenin.org
> Professional email: petithug@acm.org
> Blog: http://blog.marc.petit-huguenin.org
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt

From jo@netlab.tkk.fi  Tue Mar 29 05:04:38 2011
Return-Path: <jo@netlab.tkk.fi>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 48C973A67B0 for <avt@core3.amsl.com>; Tue, 29 Mar 2011 05:04:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mo6gJUPUbs3F for <avt@core3.amsl.com>; Tue, 29 Mar 2011 05:04:37 -0700 (PDT)
Received: from smtp.netlab.hut.fi (luuri.netlab.hut.fi [130.233.154.177]) by core3.amsl.com (Postfix) with ESMTP id 10D853A6784 for <avt@ietf.org>; Tue, 29 Mar 2011 05:04:36 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.netlab.hut.fi (Postfix) with ESMTP id 4E3F11E27B; Tue, 29 Mar 2011 15:06:14 +0300 (EEST)
X-Virus-Scanned: by amavisd-new at luuri.netlab.hut.fi
Received: from smtp.netlab.hut.fi ([127.0.0.1]) by localhost (luuri.netlab.hut.fi [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 4xgN2EmwJbf8; Tue, 29 Mar 2011 15:06:09 +0300 (EEST)
Received: from dhcp-50f5.meeting.ietf.org (unknown [130.129.80.245]) by smtp.netlab.hut.fi (Postfix) with ESMTPSA id 8D1AF1E278; Tue, 29 Mar 2011 15:06:09 +0300 (EEST)
Message-ID: <4D91CB02.9010309@netlab.tkk.fi>
Date: Tue, 29 Mar 2011 15:05:22 +0300
From: Joerg Ott <jo@netlab.tkk.fi>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
References: <4D91B43B.1090807@acm.org> <EDC0A1AE77C57744B664A310A0B23AE21EB2B237@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE21EB2B237@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Marc Petit-Huguenin <petithug@acm.org>, AVT WG <avt@ietf.org>
Subject: Re: [AVTCORE] RTCP in Overlay Multicast
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Mar 2011 12:04:38 -0000

I am at the meeting (and so is Varun) and we would be happy to fill you
in.

Joerg

On 29.03.2011 13:47, DRAGE, Keith (Keith) wrote:
> The document that formed the basis for the milestone existing was:
>
> http://tools.ietf.org/id/draft-ott-avt-rtcp-overlay-multicast-02.txt
>
> Jorg Ott is certainly at this meeting. I'm sure he could fill you in on more details.
>
> Regards
>
> Keith
>
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Marc
>> Petit-Huguenin
>> Sent: 29 March 2011 11:28
>> To: AVT WG
>> Subject: [AVTCORE] RTCP in Overlay Multicast
>>
>> We talked briefly yesterday in the AVT session about this milestone:
>>
>> Dec 2011 Submit Real-Time Transport Control Protocol (RTCP) in Overlay
>> Multicast
>> for Proposed Standard
>>
>> The general subject of Overlay Multicast is something I am interested in,
>> but is
>> there any pointer to what that milestone would be about (paper, i-d, email
>> exchange, etc...)
>>
>> Thanks.
>>
>> --
>> Marc Petit-Huguenin
>> Personal email: marc@petit-huguenin.org
>> Professional email: petithug@acm.org
>> Blog: http://blog.marc.petit-huguenin.org
>> _______________________________________________
>> 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 vikramb11@gmail.com  Tue Mar 29 22:32:42 2011
Return-Path: <vikramb11@gmail.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7E6533A6AA0 for <avt@core3.amsl.com>; Tue, 29 Mar 2011 22:32:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IorSrV00T3t8 for <avt@core3.amsl.com>; Tue, 29 Mar 2011 22:32:41 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id 8655A3A6AF8 for <avt@ietf.org>; Tue, 29 Mar 2011 22:32:40 -0700 (PDT)
Received: by gyf3 with SMTP id 3so434127gyf.31 for <avt@ietf.org>; Tue, 29 Mar 2011 22:34:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=W40CVGUX3ILzEJhTqERg/SrupdwQb10Kw7i6yZ1pxoU=; b=HRdYb0+/SKirtVCrjuha9r4v7IaI+uZmdBc/2c91VLNP2sWkhsEC1sppsRbjsbgd4u PBersDmIco9arxA7M0llLDsHMHz4a1aAcaXb/rsx5rh71XlF1rYUMUK9CJK/pCyd4ELr JxYwGTubfi9cNGI7QMX4pYeuWZXNF3rssEdZg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=NXwCsBBPU4rXBig1MAujn/8PONo+BfaPXNi6kyK7DI4TlhnBJt4MmUGtQMF6s3uKe8 L6sLt+Te08N0fhItsagyb2qqJGGlJHlGcbXpIprUvh8vPbvTi5LPyh5vBjqH3h0i9P0o 41kvuPt0OXrvWGIOJarOEmncBvvg6p8J4MAEU=
MIME-Version: 1.0
Received: by 10.91.141.19 with SMTP id t19mr1062723agn.182.1301463258921; Tue, 29 Mar 2011 22:34:18 -0700 (PDT)
Received: by 10.90.67.3 with HTTP; Tue, 29 Mar 2011 22:34:18 -0700 (PDT)
Date: Wed, 30 Mar 2011 11:04:18 +0530
Message-ID: <AANLkTinBJKF=ezAiz3xwU7RJnNVgNkFDwkHywawd9cd9@mail.gmail.com>
From: Vikram Bhuskute <vikramb11@gmail.com>
To: avt@ietf.org
Content-Type: multipart/alternative; boundary=0016e646076e3c7c33049fac8733
Subject: [AVTCORE] G729 RTP Min. interval between Voice and SID packet
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 05:33:49 -0000

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

Hi ,

I would like to know if standard puts a barrier on minimum interval required
between a silence (SID) packet and a
voice packet.

Our application is streaming  RTP pakcets(G.729 ab coded) ,where voice
packet is followed by SID packets.
As I know G.729 is a frame based codec, here packetization time is 20ms that
means voice is played out at the rate
of 20ms.

The last voice packet before SID packet has less voice data i.e the payload
is less than 20ms,so our application
ships out SID packet at the almost same time, because there is still some
space after the last voice packet to
fill in the 20ms frame.

*If we observe packets in wireshark, the time difference between last voice
packet and SID packet is in micro seconds.
**And that is creating problem at our customer place.*

Is microsecond interval unacceptable ? .
I guess this is expected behavior Please comment.

I saw RFC 3551 section on G.729, it talks about 10 and 20 ms frames but dose
not talk about minimum interval.

Thanks & Regards,

Vikram

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

Hi ,<br><br>I would like to know if standard puts a barrier on minimum inte=
rval required between a silence (SID) packet and a <br>voice packet.<br><br=
>Our application is streaming=A0 RTP pakcets(G.729 ab coded) ,where voice p=
acket is followed by SID packets.<br>
As I know G.729 is a frame based codec, here packetization time is 20ms tha=
t means voice is played out at the rate<br>of 20ms.<br><br>The last voice p=
acket before SID packet has less voice data i.e the payload is less than 20=
ms,so our application<br>
ships out SID packet at the almost same time, because there is still some s=
pace after the last voice packet to<br>fill in the 20ms frame.<br><br><b>If=
 we observe packets in wireshark, the time difference between last voice pa=
cket and SID packet is in micro seconds.<br>
</b><b>And that is creating problem at our customer place.</b><br><br>Is mi=
crosecond interval unacceptable ? .<br> I guess this is expected behavior P=
lease comment.<br><br>I saw RFC 3551 section on G.729, it talks about 10 an=
d 20 ms frames but dose not talk about minimum interval.<br>
<br>Thanks &amp; Regards,<br><br>Vikram<br>

--0016e646076e3c7c33049fac8733--

From Even.roni@huawei.com  Wed Mar 30 00:25:41 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8DFE33A682C for <avt@core3.amsl.com>; Wed, 30 Mar 2011 00:25:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.705
X-Spam-Level: 
X-Spam-Status: No, score=-102.705 tagged_above=-999 required=5 tests=[AWL=1.789, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BNf6fs-dRg8x for <avt@core3.amsl.com>; Wed, 30 Mar 2011 00:25:40 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 360563A6802 for <avt@ietf.org>; Wed, 30 Mar 2011 00:25:40 -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 <0LIV00JMZ0P7YV@szxga04-in.huawei.com> for avt@ietf.org; Wed, 30 Mar 2011 15:27:08 +0800 (CST)
Received: from 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 <0LIV00L620P78C@szxga04-in.huawei.com> for avt@ietf.org; Wed, 30 Mar 2011 15:27:07 +0800 (CST)
Received: from windows8d787f9 (dhcp-44e0.meeting.ietf.org [130.129.68.224]) by szxml11-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LIV0097B0OY0Z@szxml11-in.huawei.com>; Wed, 30 Mar 2011 15:27:07 +0800 (CST)
Date: Wed, 30 Mar 2011 09:26:36 +0200
From: Roni Even <Even.roni@huawei.com>
To: avt@ietf.org
Message-id: <009801cbeeab$d3110f40$79332dc0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_Wi1Bp/Cqh2jnvZFffBtjsA)"
Content-language: en-us
Thread-index: Acvuq81DNVUOLxmIRQ2jwD/mnhVoQw==
Cc: 'Magnus Westerlund' <magnus.westerlund@ericsson.com>
Subject: [AVTCORE] Call for adoption of encryption header extensionsin SRTP document
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 07:25:41 -0000

This is a multi-part message in MIME format.

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

 

 

Hi,

AVTCore has a mile stone for September 2011 for Encryption of Header
Extensions in the Secure Real-Time Transport Protocol (SRTP) for Proposed
Standard

 

There is an individual draft Encryption of Header Extensions in the Secure
Real-Time Transport   Protocol (SRTP)
http://tools.ietf.org/html/draft-lennox-avtcore-srtp-encrypted-header-ext-00


 

 

Based on the feedback in the AVTcore session in Prague this is a WG call  to
adopt the above text as baseline text for this milestone. This is an initial
text and can be updated based on feedback once it is a WG document.

 

 

Please respond by Thursday April 14th  2011 with your positions. 

 

Roni Even

AVTCORE WG co-chair

 


--Boundary_(ID_Wi1Bp/Cqh2jnvZFffBtjsA)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.h11
	{mso-style-name:h11;
	font-family:"Courier New";
	font-weight:bold;}
.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=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Hi,<o:p></o=
:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>AVTCore =
has a mile stone for September 2011 for</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> =
Encryption of Header Extensions in the Secure Real-Time Transport =
Protocol (SRTP) for Proposed Standard<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>There is =
an individual draft </span><span lang=3DEN =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Encryption =
of Header Extensions in the Secure&nbsp; Real-Time Transport&nbsp;&nbsp; =
Protocol (SRTP) </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><a =
href=3D"http://tools.ietf.org/html/draft-lennox-avtcore-srtp-encrypted-he=
ader-ext-00">http://tools.ietf.org/html/draft-lennox-avtcore-srtp-encrypt=
ed-header-ext-00</a> <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Based on =
the feedback in the AVTcore session in Prague this is a WG call &nbsp;to =
adopt the above text as baseline text for this milestone. This is an =
initial text and can be updated based on feedback once it is a WG =
document.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Please =
respond by Thursday April 14<sup>th</sup> &nbsp;2011 with your =
positions. <o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Roni =
Even<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>AVTCORE WG =
co-chair<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>=

--Boundary_(ID_Wi1Bp/Cqh2jnvZFffBtjsA)--

From Even.roni@huawei.com  Wed Mar 30 22:16:03 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 240A23A6C03 for <avt@core3.amsl.com>; Wed, 30 Mar 2011 22:16:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.1
X-Spam-Level: 
X-Spam-Status: No, score=-103.1 tagged_above=-999 required=5 tests=[AWL=1.394,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6z72L1YWKjo1 for <avt@core3.amsl.com>; Wed, 30 Mar 2011 22:16:02 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id A99F43A6BFA for <avt@ietf.org>; Wed, 30 Mar 2011 22:16:01 -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 <0LIW005MHPD6QK@szxga04-in.huawei.com> for avt@ietf.org; Thu, 31 Mar 2011 13:17:30 +0800 (CST)
Received: from 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 <0LIW007N2PD62F@szxga04-in.huawei.com> for avt@ietf.org; Thu, 31 Mar 2011 13:17:30 +0800 (CST)
Received: from windows8d787f9 (dhcp-44e0.meeting.ietf.org [130.129.68.224]) by szxml12-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LIW007HIPCYK5@szxml12-in.huawei.com>; Thu, 31 Mar 2011 13:17:30 +0800 (CST)
Date: Thu, 31 Mar 2011 07:16:58 +0200
From: Roni Even <Even.roni@huawei.com>
To: avt@ietf.org
Message-id: <009001cbef62$e1814510$a483cf30$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_m1TbtcOzFs9p1Yyx3omjCw)"
Content-language: en-us
Thread-index: AcvvYttZq95ohdRBTkqX9CwqlfqxBQ==
Cc: 'Magnus Westerlund' <magnus.westerlund@ericsson.com>
Subject: [AVTCORE] Call for adoption of Monitoring Architectures for RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 05:16:03 -0000

This is a multi-part message in MIME format.

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

Hi,

AVTCore has a mile stone for February 2011 for Monitoring Architectures for
RTP as Informational. 

 

There is an individual draft Monitoring Architectures for RTP
http://tools.ietf.org/id/draft-hunt-avtcore-monarch-02.txt 

 

 

Based on the feedback in the AVTcore session in Prague this is a WG call  to
adopt the above text as baseline text for this milestone. This is an initial
text and can be updated based on feedback once it is a WG document.

 

 

Please respond by Thursday April 14th  2011 with your positions. 

 

Roni Even

AVTCORE WG co-chair

 

 


--Boundary_(ID_m1TbtcOzFs9p1Yyx3omjCw)
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;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.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=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Hi,<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>AVTCore has a mile stone for February 2011 for </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Monitoring Architectures for RTP</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> as Informational. <o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><pre><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>There is an individual draft </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Monitoring Architectures for RTP</span> <span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</span><span styl
 e='font-
Calibri","sans-serif"'><a href="http://tools.ietf.org/id/draft-hunt-avtcore-monarch-02.txt">http://tools.ietf.org/id/draft-hunt-avtcore-monarch-02.txt</a> <o:p></o:p></span></pre><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Based on the feedback in the AVTcore session in Prague this is a WG call &nbsp;to adopt the above text as baseline text for this milestone. This is an initial text and can be updated based on feedback once it is a WG document.<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=Ms
 oPlainTe
:11.0pt;font-family:"Calibri","sans-serif"'>Please respond by Thursday April 14<sup>th</sup> &nbsp;2011 with your positions. <o:p></o:p></span></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Roni Even<o:p></o:p></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>AVTCORE WG co-chair<o:p></o:p></span></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p></div></body></html>

--Boundary_(ID_m1TbtcOzFs9p1Yyx3omjCw)--

From peter.musgrave@magorcorp.com  Wed Mar 30 22:29:36 2011
Return-Path: <peter.musgrave@magorcorp.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AAF9E3A6C09 for <avt@core3.amsl.com>; Wed, 30 Mar 2011 22:29:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5PG0DTV4Hyhm for <avt@core3.amsl.com>; Wed, 30 Mar 2011 22:29:33 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 340063A6C03 for <avt@ietf.org>; Wed, 30 Mar 2011 22:29:32 -0700 (PDT)
Received: by wwa36 with SMTP id 36so1665642wwa.13 for <avt@ietf.org>; Wed, 30 Mar 2011 22:31:11 -0700 (PDT)
Received: by 10.217.6.202 with SMTP id y52mr1698920wes.42.1301549471820; Wed, 30 Mar 2011 22:31:11 -0700 (PDT)
Received: from dhcp-471c.meeting.ietf.org (dhcp-471c.meeting.ietf.org [130.129.71.28]) by mx.google.com with ESMTPS id z50sm327607weq.47.2011.03.30.22.31.10 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 30 Mar 2011 22:31:10 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-12--1027760973
From: Peter Musgrave <peter.musgrave@magorcorp.com>
In-Reply-To: <009001cbef62$e1814510$a483cf30$%roni@huawei.com>
Date: Thu, 31 Mar 2011 07:31:09 +0200
Message-Id: <26F0805A-CEC8-4A52-A9AE-89DF73BC1F05@magorcorp.com>
References: <009001cbef62$e1814510$a483cf30$%roni@huawei.com>
To: Roni Even <Even.roni@huawei.com>
X-Mailer: Apple Mail (2.1082)
Cc: 'Magnus Westerlund' <magnus.westerlund@ericsson.com>, avt@ietf.org
Subject: Re: [AVTCORE] Call for adoption of Monitoring Architectures for RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 05:29:36 -0000

--Apple-Mail-12--1027760973
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I support adopting this document.=20

Peter Musgrave

On 2011-03-31, at 7:16 AM, Roni Even wrote:

> Hi,
> AVTCore has a mile stone for February 2011 for Monitoring =
Architectures for RTP as Informational.
> =20
> There is an individual draft Monitoring Architectures for RTP  =
http://tools.ietf.org/id/draft-hunt-avtcore-monarch-02.txt=20
> =20
> =20
> Based on the feedback in the AVTcore session in Prague this is a WG =
call  to adopt the above text as baseline text for this milestone. This =
is an initial text and can be updated based on feedback once it is a WG =
document.
> =20
> =20
> Please respond by Thursday April 14th  2011 with your positions.
>=20
> =20
> Roni Even
> AVTCORE WG co-chair
> =20
> =20
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


--Apple-Mail-12--1027760973
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><base href=3D"x-msg://199/"></head><body style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; ">I support adopting this =
document.&nbsp;<div><br></div><div>Peter =
Musgrave</div><div><br><div><div>On 2011-03-31, at 7:16 AM, Roni Even =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; ">Hi,<o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10.5pt; font-family: Consolas; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">AVTCore =
has a mile stone for February 2011 for<span =
class=3D"Apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">Monitoring =
Architectures for RTP</span><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; "><span =
class=3D"Apple-converted-space">&nbsp;</span>as =
Informational.<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></div><pre =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10pt; font-family: 'Courier New'; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">There is =
an individual draft </span><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; ">Monitoring Architectures for RTP</span> <span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
">&nbsp;</span><span styl=3D"" e=3D"font-
Calibri&quot;,&quot;sans-serif&quot;"><a =
href=3D"http://tools.ietf.org/id/draft-hunt-avtcore-monarch-02.txt" =
style=3D"color: blue; text-decoration: underline; =
">http://tools.ietf.org/id/draft-hunt-avtcore-monarch-02.txt</a> =
<o:p></o:p></span></pre><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10.5pt; =
font-family: Consolas; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10.5pt; font-family: Consolas; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; ">Based on the feedback in the AVTcore =
session in Prague this is a WG call &nbsp;to adopt the above text as =
baseline text for this milestone. This is an initial text and can be =
updated based on feedback once it is a WG =
document.<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10.5pt; font-family: Consolas; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></span></div><p class=3D"Ms" oplainte=3D"" =
:11.0pt;font-family:"calibri","sans-serif"'=3D"">Please respond by =
Thursday April 14<sup>th</sup><span =
class=3D"Apple-converted-space">&nbsp;</span>&nbsp;2011 with your =
positions.<o:p></o:p></p><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; =
">Roni Even<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10.5pt; =
font-family: Consolas; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; ">AVTCORE WG co-chair<o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div></div>___________________________________________=
____<br>Audio/Video Transport Core Maintenance<br><a =
href=3D"mailto:avt@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">avt@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/avt" style=3D"color: blue; =
text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/avt</a><br></div></span></blockquo=
te></div><br></div></body></html>=

--Apple-Mail-12--1027760973--

From ray.vanbrandenburg@tno.nl  Thu Mar 31 03:37:20 2011
Return-Path: <ray.vanbrandenburg@tno.nl>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 19E5928C113 for <avt@core3.amsl.com>; Thu, 31 Mar 2011 03:37:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.356
X-Spam-Level: 
X-Spam-Status: No, score=-0.356 tagged_above=-999 required=5 tests=[AWL=0.147,  BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IdSz1NNmM0UG for <avt@core3.amsl.com>; Thu, 31 Mar 2011 03:37:18 -0700 (PDT)
Received: from mailouta.tno.nl (mailouta.tno.nl [134.221.1.16]) by core3.amsl.com (Postfix) with ESMTP id 494B728C112 for <avt@ietf.org>; Thu, 31 Mar 2011 03:37:18 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.63,274,1299452400"; d="scan'208,217";a="49600876"
Received: from unknown (HELO mail.tno.nl) ([134.221.225.221]) by mailhost1a.tno.nl with ESMTP; 31 Mar 2011 12:38:56 +0200
Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.81]) by EXC-CASHUB02.tsn.tno.nl ([134.221.225.221]) with mapi id 14.01.0270.001; Thu, 31 Mar 2011 12:38:56 +0200
From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
To: 'Roni Even' <Even.roni@huawei.com>, "avt@ietf.org" <avt@ietf.org>
Thread-Topic: [AVTCORE] Call for adoption of Monitoring Architectures for RTP
Thread-Index: AcvvYttZq95ohdRBTkqX9CwqlfqxBQALOGUQ
Date: Thu, 31 Mar 2011 10:38:55 +0000
Message-ID: <FCC100FC8D6B034CB88CD8173B2DA1580AE229C5@EXC-MBX03.tsn.tno.nl>
References: <009001cbef62$e1814510$a483cf30$%roni@huawei.com>
In-Reply-To: <009001cbef62$e1814510$a483cf30$%roni@huawei.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: multipart/alternative; boundary="_000_FCC100FC8D6B034CB88CD8173B2DA1580AE229C5EXCMBX03tsntnon_"
MIME-Version: 1.0
Cc: 'Magnus Westerlund' <magnus.westerlund@ericsson.com>
Subject: Re: [AVTCORE] Call for adoption of Monitoring Architectures for RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 10:37:20 -0000

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

I support adopting this document as a baseline document.

Ray van Brandenburg

________________________________
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Roni =
Even
Sent: donderdag 31 maart 2011 7:17
To: avt@ietf.org
Cc: 'Magnus Westerlund'
Subject: [AVTCORE] Call for adoption of Monitoring Architectures for RTP


Hi,

AVTCore has a mile stone for February 2011 for Monitoring Architectures for=
 RTP as Informational.



There is an individual draft Monitoring Architectures for RTP  http://tools=
.ietf.org/id/draft-hunt-avtcore-monarch-02.txt





Based on the feedback in the AVTcore session in Prague this is a WG call  t=
o adopt the above text as baseline text for this milestone. This is an init=
ial text and can be updated based on feedback once it is a WG document.





Please respond by Thursday April 14th  2011 with your positions.

Roni Even

AVTCORE WG co-chair


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

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v=3D"urn:schemas-micr=
osoft-com:vml" xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=
=3D"urn:schemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.micros=
oft.com/office/2004/12/omml">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta content=3D"MSHTML 6.00.6000.17095" name=3D"GENERATOR">
<style>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Consolas;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoPlainText {
	FONT-SIZE: 10.5pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Consolas; mso-style-p=
riority: 99; mso-style-link: "Plain Text Char"
}
LI.MsoPlainText {
	FONT-SIZE: 10.5pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Consolas; mso-style-p=
riority: 99; mso-style-link: "Plain Text Char"
}
DIV.MsoPlainText {
	FONT-SIZE: 10.5pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Consolas; mso-style-p=
riority: 99; mso-style-link: "Plain Text Char"
}
PRE {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"; mso-styl=
e-priority: 99; mso-style-link: "HTML Preformatted Char"
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: pe=
rsonal-compose
}
SPAN.PlainTextChar {
	FONT-FAMILY: Consolas; mso-style-priority: 99; mso-style-link: "Plain Text=
"; mso-style-name: "Plain Text Char"
}
SPAN.HTMLPreformattedChar {
	FONT-FAMILY: "Courier New"; mso-style-priority: 99; mso-style-link: "HTML =
Preformatted"; mso-style-name: "HTML Preformatted Char"
}
.MsoChpDefault {
	mso-style-type: export-only
}
DIV.WordSection1 {
	page: WordSection1
}
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" vlink=3D"purple" link=3D"blue">
<div dir=3D"ltr" align=3D"left"><span class=3D"140143810-31032011"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2">I support adopting this document =
as a baseline document.
</font></span></div>
<div dir=3D"ltr" align=3D"left"><span class=3D"140143810-31032011"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div>
<div dir=3D"ltr" align=3D"left"><span class=3D"140143810-31032011"><font fa=
ce=3D"Arial" color=3D"#0000ff" size=3D"2">Ray van Brandenburg</font></span>=
</div>
<br>
<div class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"lef=
t">
<hr tabindex=3D"-1">
<font face=3D"Tahoma" size=3D"2"><b>From:</b> avt-bounces@ietf.org [mailto:=
avt-bounces@ietf.org]
<b>On Behalf Of </b>Roni Even<br>
<b>Sent:</b> donderdag 31 maart 2011 7:17<br>
<b>To:</b> avt@ietf.org<br>
<b>Cc:</b> 'Magnus Westerlund'<br>
<b>Subject:</b> [AVTCORE] Call for adoption of Monitoring Architectures for=
 RTP<br>
</font><br>
</div>
<div></div>
<div class=3D"WordSection1">
<p class=3D"MsoPlainText"><span style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Cal=
ibri','sans-serif'">Hi,<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Cal=
ibri','sans-serif'">AVTCore has a mile stone for February 2011 for
</span><span style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'"=
>Monitoring Architectures for RTP</span><span style=3D"FONT-SIZE: 11pt; FON=
T-FAMILY: 'Calibri','sans-serif'"> as Informational.
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Cal=
ibri','sans-serif'"><o:p>&nbsp;</o:p></span></p>
<pre><span style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">T=
here is an individual draft </span><span style=3D"FONT-SIZE: 11pt; FONT-FAM=
ILY: 'Calibri','sans-serif'">Monitoring Architectures for RTP</span> <span =
style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Calibri','sans-serif'">&nbsp;</span=
><span><a href=3D"http://tools.ietf.org/id/draft-hunt-avtcore-monarch-02.tx=
t">http://tools.ietf.org/id/draft-hunt-avtcore-monarch-02.txt</a> <o:p></o:=
p></span></pre>
<p class=3D"MsoPlainText"><span style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Cal=
ibri','sans-serif'"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Cal=
ibri','sans-serif'"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Cal=
ibri','sans-serif'">Based on the feedback in the AVTcore session in Prague =
this is a WG call &nbsp;to adopt the above text as baseline text for this m=
ilestone. This is an initial text and can
 be updated based on feedback once it is a WG document.<o:p></o:p></span></=
p>
<p class=3D"MsoPlainText"><span style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Cal=
ibri','sans-serif'"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Cal=
ibri','sans-serif'"><o:p>&nbsp;</o:p></span></p>
<p class=3D"Ms" oPlainTe:11.0pt;font-family:?Calibri?,?sans-serif??=3D"">Pl=
ease respond by Thursday April 14<sup>th</sup> &nbsp;2011 with your positio=
ns.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Roni Even<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"FONT-SIZE: 11pt; FONT-FAMILY: 'Cal=
ibri','sans-serif'">AVTCORE WG co-chair<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<font face=3D"monospace">This e-mail and its contents are subject to the DI=
SCLAIMER at http://www.tno.nl/emaildisclaimer</font></body>
</html>

--_000_FCC100FC8D6B034CB88CD8173B2DA1580AE229C5EXCMBX03tsntnon_--


From csp@csperkins.org  Thu Mar 31 07:18:52 2011
Return-Path: <csp@csperkins.org>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C0833A6B33 for <avt@core3.amsl.com>; Thu, 31 Mar 2011 07:18:52 -0700 (PDT)
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=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ExQYk+792rGm for <avt@core3.amsl.com>; Thu, 31 Mar 2011 07:18:51 -0700 (PDT)
Received: from lon1-msapost-2.mail.demon.net (lon1-msapost-2.mail.demon.net [195.173.77.181]) by core3.amsl.com (Postfix) with ESMTP id 07E163A6AD7 for <avt@ietf.org>; Thu, 31 Mar 2011 07:18:44 -0700 (PDT)
Received: from dhcp-9238.meeting.ietf.org ([130.129.10.56]) by lon1-post-2.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1Q5IjX-0004u6-a6; Thu, 31 Mar 2011 14:20:23 +0000
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-1--996008701
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <009001cbef62$e1814510$a483cf30$%roni@huawei.com>
Date: Thu, 31 Mar 2011 16:20:21 +0200
Message-Id: <5803904C-7287-4837-ACB2-3B74B52B93F9@csperkins.org>
References: <009001cbef62$e1814510$a483cf30$%roni@huawei.com>
To: Roni Even <Even.roni@huawei.com>
X-Mailer: Apple Mail (2.1084)
Cc: 'Magnus Westerlund' <magnus.westerlund@ericsson.com>, avt@ietf.org
Subject: Re: [AVTCORE] Call for adoption of Monitoring Architectures for RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 14:18:52 -0000

--Apple-Mail-1--996008701
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I support adopting this document as a starting point for this milestone.

Colin


On 31 Mar 2011, at 07:16, Roni Even wrote:
> Hi,
> AVTCore has a mile stone for February 2011 for Monitoring =
Architectures for RTP as Informational.
> =20
> There is an individual draft Monitoring Architectures for RTP  =
http://tools.ietf.org/id/draft-hunt-avtcore-monarch-02.txt=20
> =20
> =20
> Based on the feedback in the AVTcore session in Prague this is a WG =
call  to adopt the above text as baseline text for this milestone. This =
is an initial text and can be updated based on feedback once it is a WG =
document.
> =20
> =20
> Please respond by Thursday April 14th  2011 with your positions.
>=20
> =20
> Roni Even
> AVTCORE WG co-chair
> =20
> =20
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt



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




--Apple-Mail-1--996008701
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I =
support adopting this document as a starting point for this =
milestone.<div><br></div><div>Colin</div><div><br></div><div><br><div><div=
>On 31 Mar 2011, at 07:16, Roni Even wrote:</div><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: 'Lucida Sans Typewriter'; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; ">Hi,<o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10.5pt; font-family: Consolas; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">AVTCore =
has a mile stone for February 2011 for<span =
class=3D"Apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">Monitoring =
Architectures for RTP</span><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; "><span =
class=3D"Apple-converted-space">&nbsp;</span>as =
Informational.<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></div><pre =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10pt; font-family: 'Courier New'; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">There is =
an individual draft </span><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; ">Monitoring Architectures for RTP</span> <span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
">&nbsp;</span><span styl=3D"" e=3D"font-
Calibri&quot;,&quot;sans-serif&quot;"><a =
href=3D"http://tools.ietf.org/id/draft-hunt-avtcore-monarch-02.txt" =
style=3D"color: blue; text-decoration: underline; =
">http://tools.ietf.org/id/draft-hunt-avtcore-monarch-02.txt</a> =
<o:p></o:p></span></pre><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10.5pt; =
font-family: Consolas; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10.5pt; font-family: Consolas; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; ">Based on the feedback in the AVTcore =
session in Prague this is a WG call &nbsp;to adopt the above text as =
baseline text for this milestone. This is an initial text and can be =
updated based on feedback once it is a WG =
document.<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10.5pt; font-family: Consolas; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></span></div><p class=3D"Ms" oplainte=3D"" =
:11.0pt;font-family:"calibri","sans-serif"'=3D"">Please respond by =
Thursday April 14<sup>th</sup><span =
class=3D"Apple-converted-space">&nbsp;</span>&nbsp;2011 with your =
positions.<o:p></o:p></p><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; =
">Roni Even<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10.5pt; =
font-family: Consolas; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; ">AVTCORE WG co-chair<o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div></div>___________________________________________=
____<br>Audio/Video Transport Core Maintenance<br><a =
href=3D"mailto:avt@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">avt@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/avt" style=3D"color: blue; =
text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/avt</a><br></div></span></blockquo=
te></div><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Arial; font-size: 9px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Lucida Sans Typewriter'; font-size: 9px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; color: rgb(0, 0, 0); =
font-family: 'Lucida Sans Typewriter'; font-size: 9px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; -webkit-text-decorations-in-effect: none; =
text-indent: 0px; -webkit-text-size-adjust: auto; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; color: rgb(0, 0, 0); font-family: 'Lucida Sans Typewriter'; =
font-size: 9px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; =
-webkit-text-decorations-in-effect: none; text-indent: 0px; =
-webkit-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; color: rgb(0, 0, 0); font-family: 'Lucida Sans Typewriter'; =
font-size: 9px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; =
-webkit-text-decorations-in-effect: none; text-indent: 0px; =
-webkit-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"khtml-block-placeholder"></div><div>--&nbsp;</div><div></div><div=
>Colin Perkins</div><div><a =
href=3D"http://csperkins.org/">http://csperkins.org/</a></div></span></spa=
n></span><br class=3D"Apple-interchange-newline"></span><br =
class=3D"Apple-interchange-newline"></span>
</div>
<br></div></body></html>=

--Apple-Mail-1--996008701--

From oran@cisco.com  Thu Mar 31 07:26:26 2011
Return-Path: <oran@cisco.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BDF7B28C0F2 for <avt@core3.amsl.com>; Thu, 31 Mar 2011 07:26:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.499
X-Spam-Level: 
X-Spam-Status: No, score=-110.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cw2oLwd3sf8t for <avt@core3.amsl.com>; Thu, 31 Mar 2011 07:26:25 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id A01A728C0F7 for <avt@ietf.org>; Thu, 31 Mar 2011 07:26:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=oran@cisco.com; l=1864; q=dns/txt; s=iport; t=1301581685; x=1302791285; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=B2jNPxytNaxaKkAwQj/uw7VQRRvy7PfZLlVHiAhsuFM=; b=MpsgL6bzLbtSS17lgQSENktTKAouZd8V+m7j69q7pHUBpGCgwfoUnDtR o5dSihSL2/KQYCvYFWtnGwIXLPrIAzfmmRAzVUBJZsYZ47RPhjijtMT5g PdSTCqAG9k8d0H8m02hroKQD1+HsK+E0mZybp5yXeVRaEF+NFkRfTAzwF Q=;
X-Files: PGP.sig : 193
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAJuOlE2rRDoH/2dsb2JhbAClTXeIeZoLnBGFawSNEYNV
X-IronPort-AV: E=Sophos;i="4.63,275,1299456000";  d="sig'?scan'208";a="328222402"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-2.cisco.com with ESMTP; 31 Mar 2011 14:28:05 +0000
Received: from OranMBP.local ([10.21.118.238]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2VERX6D004433 for <avt@ietf.org>; Thu, 31 Mar 2011 14:28:04 GMT
Received: from [127.0.0.1] by OranMBP.local (PGP Universal service); Thu, 31 Mar 2011 10:28:04 -0400
X-PGP-Universal: processed; by OranMBP.local on Thu, 31 Mar 2011 10:28:04 -0400
Mime-Version: 1.0 (Apple Message framework v1084)
From: David R Oran <oran@cisco.com>
In-Reply-To: <5803904C-7287-4837-ACB2-3B74B52B93F9@csperkins.org>
Date: Thu, 31 Mar 2011 10:27:26 -0400
Message-Id: <A8F6970A-E772-4504-8288-80521E1E19DB@cisco.com>
References: <009001cbef62$e1814510$a483cf30$%roni@huawei.com> <5803904C-7287-4837-ACB2-3B74B52B93F9@csperkins.org>
To: Colin Perkins <csp@csperkins.org>
X-Mailer: Apple Mail (2.1084)
X-PGP-Encoding-Format: MIME
X-PGP-Encoding-Version: 2.0.2
Content-Type: multipart/signed; boundary="PGP_Universal_60135E91_535538A9_EE6E3290_08A1FA8C"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Cc: 'Magnus Westerlund' <magnus.westerlund@ericsson.com>, avt@ietf.org, Roni Even <Even.roni@huawei.com>
Subject: Re: [AVTCORE] Call for adoption of Monitoring Architectures for RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 14:26:26 -0000

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


On Mar 31, 2011, at 10:20 AM, Colin Perkins wrote:

> I support adopting this document as a starting point for this =
milestone.
>=20
+1

> Colin
>=20
>=20
> On 31 Mar 2011, at 07:16, Roni Even wrote:
>> Hi,
>> AVTCore has a mile stone for February 2011 for Monitoring =
Architectures for RTP as Informational.
>> =20
>> There is an individual draft Monitoring Architectures for RTP  =
http://tools.ietf.org/id/draft-hunt-avtcore-monarch-02.txt=20
>> =20
>> =20
>> Based on the feedback in the AVTcore session in Prague this is a WG =
call  to adopt the above text as baseline text for this milestone. This =
is an initial text and can be updated based on feedback once it is a WG =
document.
>> =20
>> =20
>> Please respond by Thursday April 14th  2011 with your positions.
>>=20
>> =20
>> Roni Even
>> AVTCORE WG co-chair
>> =20
>> =20
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>=20
>=20
>=20
> --=20
> Colin Perkins
> http://csperkins.org/
>=20
>=20
>=20
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


--PGP_Universal_60135E91_535538A9_EE6E3290_08A1FA8C
Content-Type: application/pgp-signature;
	x-mac-type=70674453;
	name=PGP.sig
Content-Disposition: attachment; filename=PGP.sig

-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 10.0.3 (Build 1)

iQA/AwUBTZSPZo1mhLZU3SrmEQKiFgCg5VbLA/cQhb4qPRL8CGkEhfBDLMwAoJE6
GnYHf3bfLwNLKWQGsb+02RjF
=FXmU
-----END PGP SIGNATURE-----

--PGP_Universal_60135E91_535538A9_EE6E3290_08A1FA8C--

From dromasca@avaya.com  Thu Mar 31 07:29:00 2011
Return-Path: <dromasca@avaya.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8253E28C0EA for <avt@core3.amsl.com>; Thu, 31 Mar 2011 07:29:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.172
X-Spam-Level: 
X-Spam-Status: No, score=-103.172 tagged_above=-999 required=5 tests=[AWL=0.427, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S1NxHI-+jdAq for <avt@core3.amsl.com>; Thu, 31 Mar 2011 07:28:59 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 6CDA328C0F4 for <avt@ietf.org>; Thu, 31 Mar 2011 07:28:59 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvYAAFMtcU3GmAcF/2dsb2JhbACYKo47dKR5ApkWhWEEkAw
X-IronPort-AV: E=Sophos;i="4.63,275,1299474000"; d="scan'208";a="272361822"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 31 Mar 2011 10:30:38 -0400
X-IronPort-AV: E=Sophos;i="4.63,275,1299474000"; d="scan'208";a="603625847"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 31 Mar 2011 10:30:37 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 31 Mar 2011 16:30:24 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0402EF103A@307622ANEX5.global.avaya.com>
In-Reply-To: <A8F6970A-E772-4504-8288-80521E1E19DB@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVTCORE] Call for adoption of Monitoring Architectures for RTP
Thread-Index: Acvvr+XsFPvRa1zzQsqvUpjxoDgasgAAEAOg
References: <009001cbef62$e1814510$a483cf30$%roni@huawei.com><5803904C-7287-4837-ACB2-3B74B52B93F9@csperkins.org> <A8F6970A-E772-4504-8288-80521E1E19DB@cisco.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "David R Oran" <oran@cisco.com>, "Colin Perkins" <csp@csperkins.org>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, avt@ietf.org, Roni Even <Even.roni@huawei.com>
Subject: Re: [AVTCORE] Call for adoption of Monitoring Architectures for RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 14:29:00 -0000

+1

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On=20
> Behalf Of David R Oran
> Sent: Thursday, March 31, 2011 4:27 PM
> To: Colin Perkins
> Cc: 'Magnus Westerlund'; avt@ietf.org; Roni Even
> Subject: Re: [AVTCORE] Call for adoption of Monitoring=20
> Architectures for RTP
>=20
>=20
> On Mar 31, 2011, at 10:20 AM, Colin Perkins wrote:
>=20
> > I support adopting this document as a starting point for=20
> this milestone.
> >=20
> +1
>=20
> > Colin
> >=20
> >=20
> > On 31 Mar 2011, at 07:16, Roni Even wrote:
> >> Hi,
> >> AVTCore has a mile stone for February 2011 for Monitoring=20
> Architectures for RTP as Informational.
> >> =20
> >> There is an individual draft Monitoring Architectures for RTP =20
> >> http://tools.ietf.org/id/draft-hunt-avtcore-monarch-02.txt
> >> =20
> >> =20
> >> Based on the feedback in the AVTcore session in Prague=20
> this is a WG call  to adopt the above text as baseline text=20
> for this milestone. This is an initial text and can be=20
> updated based on feedback once it is a WG document.
> >> =20
> >> =20
> >> Please respond by Thursday April 14th  2011 with your positions.
> >>=20
> >> =20
> >> Roni Even
> >> AVTCORE WG co-chair
> >> =20
> >> =20
> >> _______________________________________________
> >> Audio/Video Transport Core Maintenance avt@ietf.org=20
> >> https://www.ietf.org/mailman/listinfo/avt
> >=20
> >=20
> >=20
> > --
> > Colin Perkins
> > http://csperkins.org/
> >=20
> >=20
> >=20
> > _______________________________________________
> > Audio/Video Transport Core Maintenance avt@ietf.org=20
> > https://www.ietf.org/mailman/listinfo/avt
>=20
>=20

From emil@sip-communicator.org  Thu Mar 31 07:32:15 2011
Return-Path: <emil@sip-communicator.org>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 081D428C0F2 for <avt@core3.amsl.com>; Thu, 31 Mar 2011 07:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ucEik54OkdpV for <avt@core3.amsl.com>; Thu, 31 Mar 2011 07:32:13 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 36F0D28C0EA for <avt@ietf.org>; Thu, 31 Mar 2011 07:32:13 -0700 (PDT)
Received: by wyb29 with SMTP id 29so2337071wyb.31 for <avt@ietf.org>; Thu, 31 Mar 2011 07:33:52 -0700 (PDT)
Received: by 10.216.141.206 with SMTP id g56mr1656898wej.5.1301582031941; Thu, 31 Mar 2011 07:33:51 -0700 (PDT)
Received: from porcinet.local ([78.90.181.123]) by mx.google.com with ESMTPS id s40sm542694weq.4.2011.03.31.07.33.49 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 31 Mar 2011 07:33:50 -0700 (PDT)
Message-ID: <4D9490CC.9050108@jitsi.org>
Date: Thu, 31 Mar 2011 17:33:48 +0300
From: Emil Ivov <emcho@jitsi.org>
Organization: Jitsi
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; bg; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Roni Even <Even.roni@huawei.com>
References: <009801cbeeab$d3110f40$79332dc0$%roni@huawei.com>
In-Reply-To: <009801cbeeab$d3110f40$79332dc0$%roni@huawei.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: 'Magnus Westerlund' <magnus.westerlund@ericsson.com>, avt@ietf.org
Subject: Re: [AVTCORE] Call for adoption of encryption header extensionsin SRTP	document
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 14:32:15 -0000

+1

Emil

=D0=9D=D0=B0 30.03.11 10:26, Roni Even =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=
:
> AVTCore has a mile stone for September 2011 forEncryption of Header
> Extensions in the Secure Real-Time Transport Protocol (SRTP) for
> Proposed Standard
>=20
> =20
>=20
> There is an individual draft Encryption of Header Extensions in the
> Secure  Real-Time Transport   Protocol (SRTP)
> http://tools.ietf.org/html/draft-lennox-avtcore-srtp-encrypted-header-e=
xt-00
>=20
>=20
> =20
>=20
> =20
>=20
> Based on the feedback in the AVTcore session in Prague this is a WG cal=
l
>  to adopt the above text as baseline text for this milestone. This is a=
n
> initial text and can be updated based on feedback once it is a WG docum=
ent.
>=20
> =20
>=20
> =20
>=20
> Please respond by Thursday April 14^th  2011 with your positions.
>=20
> =20
>=20
> Roni Even
>=20
> AVTCORE WG co-chair
>=20
> =20
>=20
>=20
>=20
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt

--=20
Emil Ivov, Ph.D.                       67000 Strasbourg,
Project Lead                           France
Jitsi
emcho@jitsi.org                        PHONE: +33.1.77.62.43.30
http://jitsi.org                       FAX:   +33.1.77.62.47.31


From skillzero@gmail.com  Thu Mar 31 09:20:06 2011
Return-Path: <skillzero@gmail.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8035128C167 for <avt@core3.amsl.com>; Thu, 31 Mar 2011 09:20:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.367
X-Spam-Level: 
X-Spam-Status: No, score=-3.367 tagged_above=-999 required=5 tests=[AWL=0.232,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R7Bv87qUcZfm for <avt@core3.amsl.com>; Thu, 31 Mar 2011 09:20:05 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 5DF0428C155 for <avt@ietf.org>; Thu, 31 Mar 2011 09:20:05 -0700 (PDT)
Received: by wwa36 with SMTP id 36so2122841wwa.13 for <avt@ietf.org>; Thu, 31 Mar 2011 09:21:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=fJdlogRmQX0OCj7vyfuYOqHRm4DWltu77q73VIic8z8=; b=WacuETMjUqZAgAHKivYZPy5Z6RK+Nqn1o9WsmUd8PntwaoMzZyJcPqWDUUPTBrlC4q 5cZ4QEbcxOelG9lGNafT09g5VF/5wAMQpn+Q/yfy0dt2gOjNi+dnFfCR3Bgd14k8S9nB pjQDe4uLANv6I0qI6sW8kpTYnTmztil6SePfU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=t2O0OCUEo4BABGvrtrul3rEWNI7y9hIT8Ckhh5HbWRN+JP7Yey90A+6urJSJjT1qCA 0beu8G/Eq6ISW3RJOLTYbEujNzJXYwjoo8Sde+ekNjbIFIBz5RTinmu6RBQaKmI1NZeG 5bYVniCLJjSK6BhHxzbTsR5MXWjDiHKGTD5LQ=
MIME-Version: 1.0
Received: by 10.216.141.94 with SMTP id f72mr2836787wej.38.1301588504538; Thu, 31 Mar 2011 09:21:44 -0700 (PDT)
Received: by 10.216.17.138 with HTTP; Thu, 31 Mar 2011 09:21:44 -0700 (PDT)
Date: Thu, 31 Mar 2011 09:21:44 -0700
Message-ID: <AANLkTi=OkJEwf28K+vfG3ddifmGZUy8Li30v9Ai5DaXz@mail.gmail.com>
From: skillzero@gmail.com
To: avt@ietf.org
Content-Type: text/plain; charset=UTF-8
Subject: [AVTCORE] Synchronization source for synchronizing stream changes?
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 16:20:06 -0000

Is it acceptable, from an RTP protocol perspective, to use the
synchronization source ID in the RTP header to synchronize changes in
the RTP stream, such as encoding, display characteristics (e.g.
rotation, scaling), etc.? Or are there better ways to handle this?

When I'm sending video frames via RTP, changes that happen on the
source, such as the encoder config, transforms for display, etc. may
change on a frame-by-frame basis, such as when the user rotates a
source camera or the quality is reduced based on network conditions.
Normally, this is sent via static SDP during session setup, but here
it changes in the middle of a session. When it happens, I send the new
data via a separate channel (e.g. RTCP/RTSP), but this also means it's
possible for RTP video frames to arrive before the updated
configuration info arrives. I need to know to defer trying to decode
or display the frame until the new configuration comes in via the
other channel.

It seemed reasonable to use the synchronization source ID in the RTP
header to indicate this. Whenever something changes, the ssrc could be
incremented so the receiver knows it needs to wait until out-of-band
information about the new ssrc arrives before it processes the RTP
packet. Packets may also be lost so I didn't want to rely on a
one-time thing like the marker bit. Payload type has a pretty small
usable range and I can see it wrapping too quickly for this usage.

Does this break any rules of RTP? Or is there a recommended way to
handle these situations?

From Even.roni@huawei.com  Thu Mar 31 09:48:46 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 780BF3A699E for <avt@core3.amsl.com>; Thu, 31 Mar 2011 09:48:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.732
X-Spam-Level: 
X-Spam-Status: No, score=-103.732 tagged_above=-999 required=5 tests=[AWL=0.763, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CEmmWwiZDgTT for <avt@core3.amsl.com>; Thu, 31 Mar 2011 09:48:45 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id C4B983A69BE for <avt@ietf.org>; Thu, 31 Mar 2011 09:48:44 -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 <0LIX00B89LFQGX@szxga04-in.huawei.com> for avt@ietf.org; Fri, 01 Apr 2011 00:50:14 +0800 (CST)
Received: from 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 <0LIX00KVYLFQUT@szxga04-in.huawei.com> for avt@ietf.org; Fri, 01 Apr 2011 00:50:14 +0800 (CST)
Received: from windows8d787f9 (dhcp-44e0.meeting.ietf.org [130.129.68.224]) by szxml11-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LIX003MKLFIAY@szxml11-in.huawei.com>; Fri, 01 Apr 2011 00:50:14 +0800 (CST)
Date: Thu, 31 Mar 2011 18:49:43 +0200
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <AANLkTi=OkJEwf28K+vfG3ddifmGZUy8Li30v9Ai5DaXz@mail.gmail.com>
To: skillzero@gmail.com, avt@ietf.org
Message-id: <021201cbefc3$a753f6b0$f5fbe410$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: Acvvv8tfU0HajQtcQYiwbpUCFTJkZQAAzSQA
References: <AANLkTi=OkJEwf28K+vfG3ddifmGZUy8Li30v9Ai5DaXz@mail.gmail.com>
Subject: Re: [AVTCORE] Synchronization source for synchronizing stream changes?
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 16:48:46 -0000

Hi,
Using SSRC is not the right way. It will be better to have this information
as part of the RTP payload specification of the specific codec and send it
with the payload. Example is parameter sets in H.264


In RFC3984 and RFC3984bis (H.264 payload) even if parameter sets are sent
out of band in SDP they have an ID that is used in the payload or payload
header and not part of the RTP header.

I am not sure why you do it out of band and if it is for a specific codec or
a general mechanism.

Roni Even

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> skillzero@gmail.com
> Sent: Thursday, March 31, 2011 6:22 PM
> To: avt@ietf.org
> Subject: [AVTCORE] Synchronization source for synchronizing stream
> changes?
> 
> Is it acceptable, from an RTP protocol perspective, to use the
> synchronization source ID in the RTP header to synchronize changes in
> the RTP stream, such as encoding, display characteristics (e.g.
> rotation, scaling), etc.? Or are there better ways to handle this?
> 
> When I'm sending video frames via RTP, changes that happen on the
> source, such as the encoder config, transforms for display, etc. may
> change on a frame-by-frame basis, such as when the user rotates a
> source camera or the quality is reduced based on network conditions.
> Normally, this is sent via static SDP during session setup, but here
> it changes in the middle of a session. When it happens, I send the new
> data via a separate channel (e.g. RTCP/RTSP), but this also means it's
> possible for RTP video frames to arrive before the updated
> configuration info arrives. I need to know to defer trying to decode
> or display the frame until the new configuration comes in via the
> other channel.
> 
> It seemed reasonable to use the synchronization source ID in the RTP
> header to indicate this. Whenever something changes, the ssrc could be
> incremented so the receiver knows it needs to wait until out-of-band
> information about the new ssrc arrives before it processes the RTP
> packet. Packets may also be lost so I didn't want to rely on a
> one-time thing like the marker bit. Payload type has a pretty small
> usable range and I can see it wrapping too quickly for this usage.
> 
> Does this break any rules of RTP? Or is there a recommended way to
> handle these situations?
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From versteb@cisco.com  Thu Mar 31 13:28:07 2011
Return-Path: <versteb@cisco.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B03F28C0E1 for <avt@core3.amsl.com>; Thu, 31 Mar 2011 13:28:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.448
X-Spam-Level: 
X-Spam-Status: No, score=-10.448 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Sbgf4aYbLcE for <avt@core3.amsl.com>; Thu, 31 Mar 2011 13:28:05 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id BC6873A6BAB for <avt@ietf.org>; Thu, 31 Mar 2011 13:28:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=versteb@cisco.com; l=14044; q=dns/txt; s=iport; t=1301603385; x=1302812985; h=mime-version:subject:date:message-id:in-reply-to: references:from:to:cc; bh=9f+2gYMeCSxbimIJv7zOgzT6XmAbIkhXVKrDpxmM8kQ=; b=Hvidv7mEFGX+sd+B3iBKxJx5fdGW+RL6dra+KlKoEeBMdwSZJWhP4sVB 0q/gY2XuHBpCnbmORuY0C7TZO63DYtmUvnhFZvOvhT2kThfX6FvIDRAro JrLreNr8OtRUoNuJhKTnU++Yi6CtLx8s0aNMPXAPxHOiM2255e9XOyha9 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvkAAPbilE2tJV2Y/2dsb2JhbACCXpU5QIYGhnl3o3WcOoVrBIVBiys
X-IronPort-AV: E=Sophos;i="4.63,278,1299456000";  d="scan'208,217";a="286841990"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by sj-iport-3.cisco.com with ESMTP; 31 Mar 2011 20:29:45 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p2VKTjsk006204;  Thu, 31 Mar 2011 20:29:45 GMT
Received: from xmb-rcd-213.cisco.com ([72.163.62.220]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 31 Mar 2011 15:29:45 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBEFE2.5EA339F4"
Date: Thu, 31 Mar 2011 15:29:42 -0500
Message-ID: <EE933D92D054D14089A336CC71A5CCA603D9BC94@XMB-RCD-213.cisco.com>
In-Reply-To: <5803904C-7287-4837-ACB2-3B74B52B93F9@csperkins.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVTCORE] Call for adoption of Monitoring Architectures for RTP
Thread-Index: AcvvrtUJ76iIa4RoQVagGiMimOHzKAAM4FKQ
References: <009001cbef62$e1814510$a483cf30$%roni@huawei.com> <5803904C-7287-4837-ACB2-3B74B52B93F9@csperkins.org>
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "Colin Perkins" <csp@csperkins.org>, "Roni Even" <Even.roni@huawei.com>
X-OriginalArrivalTime: 31 Mar 2011 20:29:45.0543 (UTC) FILETIME=[5F94DD70:01CBEFE2]
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, avt@ietf.org
Subject: Re: [AVTCORE] Call for adoption of Monitoring Architectures for RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 20:28:07 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBEFE2.5EA339F4
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

+1

=20

Bill VerSteeg

=20

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
Colin Perkins
Sent: Thursday, March 31, 2011 10:20 AM
To: Roni Even
Cc: 'Magnus Westerlund'; avt@ietf.org
Subject: Re: [AVTCORE] Call for adoption of Monitoring Architectures for
RTP

=20

I support adopting this document as a starting point for this milestone.

=20

Colin

=20

=20

On 31 Mar 2011, at 07:16, Roni Even wrote:

	Hi,

	AVTCore has a mile stone for February 2011 for Monitoring
Architectures for RTP as Informational.

	=20

	There is an individual draft Monitoring Architectures for RTP
http://tools.ietf.org/id/draft-hunt-avtcore-monarch-02.txt=20

	=20

	=20

	Based on the feedback in the AVTcore session in Prague this is a
WG call  to adopt the above text as baseline text for this milestone.
This is an initial text and can be updated based on feedback once it is
a WG document.

	=20

	=20

	Please respond by Thursday April 14th  2011 with your positions.

	=20

	Roni Even

	AVTCORE WG co-chair

	=20

	=20

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

=20

=20

--=20

Colin Perkins

http://csperkins.org/






=20


------_=_NextPart_001_01CBEFE2.5EA339F4
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Lucida Sans Typewriter";
	panose-1:2 11 5 9 3 5 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
p.ms, li.ms, div.ms
	{mso-style-name:ms;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple style=3D'word-wrap: =
break-word;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space'>

<div class=3DSection1>

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

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

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

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

<div>

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

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] <b>On Behalf Of =
</b>Colin
Perkins<br>
<b>Sent:</b> Thursday, March 31, 2011 10:20 AM<br>
<b>To:</b> Roni Even<br>
<b>Cc:</b> 'Magnus Westerlund'; avt@ietf.org<br>
<b>Subject:</b> Re: [AVTCORE] Call for adoption of Monitoring =
Architectures for
RTP<o:p></o:p></span></p>

</div>

</div>

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

<p class=3DMsoNormal>I support adopting this document as a starting =
point for
this milestone.<o:p></o:p></p>

<div>

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

</div>

<div>

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

</div>

<div>

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

</div>

<div>

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

<div>

<div>

<p class=3DMsoNormal>On 31 Mar 2011, at 07:16, Roni Even =
wrote:<o:p></o:p></p>

</div>

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

<div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>AVTCore
has a mile stone for February 2011 for<span =
class=3Dapple-converted-space>&nbsp;</span>Monitoring
Architectures for RTP<span class=3Dapple-converted-space>&nbsp;</span>as
Informational.</span><span =
style=3D'font-size:10.5pt;font-family:Consolas'><o:p></o:p></span></p>

</div>

<div>

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

</div>

<pre><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>There is =
an individual draft Monitoring Architectures for RTP</span> <span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><a
href=3D"http://tools.ietf.org/id/draft-hunt-avtcore-monarch-02.txt">http:=
//tools.ietf.org/id/draft-hunt-avtcore-monarch-02.txt</a> =
<o:p></o:p></pre>

<div>

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

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Based
on the feedback in the AVTcore session in Prague this is a WG call =
&nbsp;to
adopt the above text as baseline text for this milestone. This is an =
initial
text and can be updated based on feedback once it is a WG =
document.</span><span
style=3D'font-size:10.5pt;font-family:Consolas'><o:p></o:p></span></p>

</div>

<div>

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

</div>

<div>

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

</div>

<p class=3Dms><span style=3D'font-size:13.5pt;font-family:"Lucida Sans =
Typewriter","sans-serif"'>Please
respond by Thursday April 14<sup>th</sup><span =
class=3Dapple-converted-space>&nbsp;</span>&nbsp;2011
with your positions.<o:p></o:p></span></p>

<div>

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

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>AVTCORE
WG co-chair</span><span =
style=3D'font-size:10.5pt;font-family:Consolas'><o:p></o:p></span></p>

</div>

<div>

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

</div>

<div>

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

</div>

<p class=3DMsoNormal><span style=3D'font-size:13.5pt;font-family:"Lucida =
Sans =
Typewriter","sans-serif"'>_______________________________________________=
<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">https://www.ietf.org/m=
ailman/listinfo/avt</a><o:p></o:p></span></p>

</div>

</blockquote>

</div>

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

<div>

<div>

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

</div>

<div>

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

</div>

<div>

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

</div>

<div>

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

</div>

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

</div>

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

</div>

</div>

</body>

</html>

------_=_NextPart_001_01CBEFE2.5EA339F4--

From skillzero@gmail.com  Thu Mar 31 19:41:10 2011
Return-Path: <skillzero@gmail.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 205E83A6AE9 for <avt@core3.amsl.com>; Thu, 31 Mar 2011 19:41:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.413
X-Spam-Level: 
X-Spam-Status: No, score=-3.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xsYCDCuA4oot for <avt@core3.amsl.com>; Thu, 31 Mar 2011 19:41:08 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 218793A6ADE for <avt@ietf.org>; Thu, 31 Mar 2011 19:41:07 -0700 (PDT)
Received: by wyb29 with SMTP id 29so2891132wyb.31 for <avt@ietf.org>; Thu, 31 Mar 2011 19:42:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=cehT5Vxeg5qaq2AIRN1w1xjTIf8gh8qrIgF2q84jets=; b=K9aAtRUATvehla16ew2RBEGEBBzligIp1GgbAJdYVhjZLNdNCU6cDZAvpAQ+vWQTGB Bf0Yhc0EQibZch2y/IV/n0nAs/rISuSoj4oDZ6mO+DJj0o/rFbqldEc3JcWXzz90BQiz 5EItlENV4rEKGbarRfQNeuwawjLZ/nZXB//9M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ewBTiPtqyiGiSXIdtJPSFhCh1ma9pdVoHMFsxltmZws7JKIsJ85WWFsqjGCEc3yN1Z jb51yHkzFD51EboS27jzZlHDcqcAvOVsYvoMe0EpwN3zuFh5XbkkgZSBQuVXyBfbtGxN ZU8SdnW2dminRNu0dKK/h6R3smuH/S0QVnZpc=
MIME-Version: 1.0
Received: by 10.216.145.135 with SMTP id p7mr257136wej.38.1301625767305; Thu, 31 Mar 2011 19:42:47 -0700 (PDT)
Received: by 10.216.17.138 with HTTP; Thu, 31 Mar 2011 19:42:47 -0700 (PDT)
In-Reply-To: <021201cbefc3$a753f6b0$f5fbe410$%roni@huawei.com>
References: <AANLkTi=OkJEwf28K+vfG3ddifmGZUy8Li30v9Ai5DaXz@mail.gmail.com> <021201cbefc3$a753f6b0$f5fbe410$%roni@huawei.com>
Date: Thu, 31 Mar 2011 19:42:47 -0700
Message-ID: <AANLkTiny3yrBq-6WR4F4G-2gAvOz7c3VqoJOTUSLShp-@mail.gmail.com>
From: skillzero@gmail.com
To: Roni Even <Even.roni@huawei.com>
Content-Type: text/plain; charset=UTF-8
Cc: avt@ietf.org
Subject: Re: [AVTCORE] Synchronization source for synchronizing stream changes?
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2011 02:41:10 -0000

Thanks, I'll check out H.264 parameter sets.

The main reason I planned to do it out-of-band is that I have a
reliable TCP-based RTSP channel and RTP data goes over unreliable UDP.
I use an FEC scheme for RTP video data, but if there is more loss than
FEC can recover from, I just move on. But for this data, it's critical
for it to not be dropped so I would need to re-implement a TCP-like
scheme for loss recovery.

One thing that also complicates this is that the codec can change
dynamically (it adapts to network conditions, type of content, etc.).
I can use the payload type to some extent, but that usually assumes
some level of pre-configuration when the RTP stream is setup (e.g. SDP
rtpmap lines) and there's a pretty limited number of dynamic payload
types (and I have multiple concurrent RTP streams of differing types,
which reduces the payload type range further).

A separate ID in the payload can work. I was just thinking to reuse
the SSRC since I'm not using it for anything else (and it seemed like
this could be viewed as another synchronizing source becoming active).
Using an ID in the payload also means I won't be able to use standard
payload formats, unless they already have a ID in their specification.

On Thu, Mar 31, 2011 at 9:49 AM, Roni Even <Even.roni@huawei.com> wrote:
> Hi,
> Using SSRC is not the right way. It will be better to have this information
> as part of the RTP payload specification of the specific codec and send it
> with the payload. Example is parameter sets in H.264
>
>
> In RFC3984 and RFC3984bis (H.264 payload) even if parameter sets are sent
> out of band in SDP they have an ID that is used in the payload or payload
> header and not part of the RTP header.
>
> I am not sure why you do it out of band and if it is for a specific codec or
> a general mechanism.
>
> Roni Even
>
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
>> skillzero@gmail.com
>> Sent: Thursday, March 31, 2011 6:22 PM
>> To: avt@ietf.org
>> Subject: [AVTCORE] Synchronization source for synchronizing stream
>> changes?
>>
>> Is it acceptable, from an RTP protocol perspective, to use the
>> synchronization source ID in the RTP header to synchronize changes in
>> the RTP stream, such as encoding, display characteristics (e.g.
>> rotation, scaling), etc.? Or are there better ways to handle this?
>>
>> When I'm sending video frames via RTP, changes that happen on the
>> source, such as the encoder config, transforms for display, etc. may
>> change on a frame-by-frame basis, such as when the user rotates a
>> source camera or the quality is reduced based on network conditions.
>> Normally, this is sent via static SDP during session setup, but here
>> it changes in the middle of a session. When it happens, I send the new
>> data via a separate channel (e.g. RTCP/RTSP), but this also means it's
>> possible for RTP video frames to arrive before the updated
>> configuration info arrives. I need to know to defer trying to decode
>> or display the frame until the new configuration comes in via the
>> other channel.
>>
>> It seemed reasonable to use the synchronization source ID in the RTP
>> header to indicate this. Whenever something changes, the ssrc could be
>> incremented so the receiver knows it needs to wait until out-of-band
>> information about the new ssrc arrives before it processes the RTP
>> packet. Packets may also be lost so I didn't want to rely on a
>> one-time thing like the marker bit. Payload type has a pretty small
>> usable range and I can see it wrapping too quickly for this usage.
>>
>> Does this break any rules of RTP? Or is there a recommended way to
>> handle these situations?
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>
>

From Even.roni@huawei.com  Thu Mar 31 22:08:57 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 812823A67F1 for <avt@core3.amsl.com>; Thu, 31 Mar 2011 22:08:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.841
X-Spam-Level: 
X-Spam-Status: No, score=-101.841 tagged_above=-999 required=5 tests=[AWL=-1.346, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 423JOiaqXFRB for <avt@core3.amsl.com>; Thu, 31 Mar 2011 22:08:56 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 1AB973A67E1 for <avt@ietf.org>; Thu, 31 Mar 2011 22:08:56 -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 <0LIY00JMSJPDSS@szxga05-in.huawei.com> for avt@ietf.org; Fri, 01 Apr 2011 13:10:25 +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 <0LIY00JBMJPDZ8@szxga05-in.huawei.com> for avt@ietf.org; Fri, 01 Apr 2011 13:10:25 +0800 (CST)
Received: from windows8d787f9 (dhcp-44e0.meeting.ietf.org [130.129.68.224]) by szxml12-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LIY0091JJP0GA@szxml12-in.huawei.com>; Fri, 01 Apr 2011 13:10:25 +0800 (CST)
Date: Fri, 01 Apr 2011 08:09:47 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <AANLkTiny3yrBq-6WR4F4G-2gAvOz7c3VqoJOTUSLShp-@mail.gmail.com>
To: skillzero@gmail.com
Message-id: <006f01cbf02b$0de65550$29b2fff0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=utf-8
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcvwFqd7h3iPgtx7TY2mvbhe1AuoeQAE++mw
References: <AANLkTi=OkJEwf28K+vfG3ddifmGZUy8Li30v9Ai5DaXz@mail.gmail.com> <021201cbefc3$a753f6b0$f5fbe410$%roni@huawei.com> <AANLkTiny3yrBq-6WR4F4G-2gAvOz7c3VqoJOTUSLShp-@mail.gmail.com>
Cc: avt@ietf.org
Subject: Re: [AVTCORE] Synchronization source for synchronizing stream changes?
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2011 05:08:57 -0000

Hi,
If it is a specific payload then the information can be in the payload headers or in some payload specific structure.
For general case look at rtp header extensions in rfc3550 and rfc5285
Roni


> -----Original Message-----
> From: skillzero@gmail.com [mailto:skillzero@gmail.com]
> Sent: Friday, April 01, 2011 5:43 AM
> To: Roni Even
> Cc: avt@ietf.org
> Subject: Re: [AVTCORE] Synchronization source for synchronizing stream
> changes?
> 
> Thanks, I'll check out H.264 parameter sets.
> 
> The main reason I planned to do it out-of-band is that I have a
> reliable TCP-based RTSP channel and RTP data goes over unreliable UDP.
> I use an FEC scheme for RTP video data, but if there is more loss than
> FEC can recover from, I just move on. But for this data, it's critical
> for it to not be dropped so I would need to re-implement a TCP-like
> scheme for loss recovery.
> 
> One thing that also complicates this is that the codec can change
> dynamically (it adapts to network conditions, type of content, etc.).
> I can use the payload type to some extent, but that usually assumes
> some level of pre-configuration when the RTP stream is setup (e.g. SDP
> rtpmap lines) and there's a pretty limited number of dynamic payload
> types (and I have multiple concurrent RTP streams of differing types,
> which reduces the payload type range further).
> 
> A separate ID in the payload can work. I was just thinking to reuse
> the SSRC since I'm not using it for anything else (and it seemed like
> this could be viewed as another synchronizing source becoming active).
> Using an ID in the payload also means I won't be able to use standard
> payload formats, unless they already have a ID in their specification.
> 
> On Thu, Mar 31, 2011 at 9:49 AM, Roni Even <Even.roni@huawei.com>
> wrote:
> > Hi,
> > Using SSRC is not the right way. It will be better to have this
> information
> > as part of the RTP payload specification of the specific codec and
> send it
> > with the payload. Example is parameter sets in H.264
> >
> >
> > In RFC3984 and RFC3984bis (H.264 payload) even if parameter sets are
> sent
> > out of band in SDP they have an ID that is used in the payload or
> payload
> > header and not part of the RTP header.
> >
> > I am not sure why you do it out of band and if it is for a specific
> codec or
> > a general mechanism.
> >
> > Roni Even
> >
> >> -----Original Message-----
> >> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
> Of
> >> skillzero@gmail.com
> >> Sent: Thursday, March 31, 2011 6:22 PM
> >> To: avt@ietf.org
> >> Subject: [AVTCORE] Synchronization source for synchronizing stream
> >> changes?
> >>
> >> Is it acceptable, from an RTP protocol perspective, to use the
> >> synchronization source ID in the RTP header to synchronize changes
> in
> >> the RTP stream, such as encoding, display characteristics (e.g.
> >> rotation, scaling), etc.? Or are there better ways to handle this?
> >>
> >> When I'm sending video frames via RTP, changes that happen on the
> >> source, such as the encoder config, transforms for display, etc. may
> >> change on a frame-by-frame basis, such as when the user rotates a
> >> source camera or the quality is reduced based on network conditions.
> >> Normally, this is sent via static SDP during session setup, but here
> >> it changes in the middle of a session. When it happens, I send the
> new
> >> data via a separate channel (e.g. RTCP/RTSP), but this also means
> it's
> >> possible for RTP video frames to arrive before the updated
> >> configuration info arrives. I need to know to defer trying to decode
> >> or display the frame until the new configuration comes in via the
> >> other channel.
> >>
> >> It seemed reasonable to use the synchronization source ID in the RTP
> >> header to indicate this. Whenever something changes, the ssrc could
> be
> >> incremented so the receiver knows it needs to wait until out-of-band
> >> information about the new ssrc arrives before it processes the RTP
> >> packet. Packets may also be lost so I didn't want to rely on a
> >> one-time thing like the marker bit. Payload type has a pretty small
> >> usable range and I can see it wrapping too quickly for this usage.
> >>
> >> Does this break any rules of RTP? Or is there a recommended way to
> >> handle these situations?
> >> _______________________________________________
> >> Audio/Video Transport Core Maintenance
> >> avt@ietf.org
> >> https://www.ietf.org/mailman/listinfo/avt
> >
> >

