From avt-bounces@ietf.org Tue Feb 06 08:06:59 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HEQ0m-0005Ac-Nj; Tue, 06 Feb 2007 08:05:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HEB2K-00087r-Lk
	for avt@ietf.org; Mon, 05 Feb 2007 16:06:04 -0500
Received: from smtp101.vzn.mail.dcn.yahoo.com ([209.73.179.139])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HEB2F-0000yi-D4
	for avt@ietf.org; Mon, 05 Feb 2007 16:06:04 -0500
Received: (qmail 6918 invoked from network); 5 Feb 2007 21:05:59 -0000
Received: from unknown (HELO AMALIS.verizon.net)
	(agmalis@verizon.net@84.233.132.68 with login)
	by smtp101.vzn.mail.dcn.yahoo.com with SMTP; 5 Feb 2007 21:05:58 -0000
X-YMail-OSG: S2E6m_AVM1nkBw4dWSWMpGt0R79UhnqjzXCd7wiaGWddEALIAX7kWfnYsEEjlVI9S2lOeMrGvprrDgKXTHyg8EnuHmOnmhzO.PGxoeF3ccZuvUN9dkbWTUNkVEuxV3rH9dOPS2rcD09e2DLBL6yoN0QI5Xbop5w4frVEc1unK75rZIb2essj6IQVNhd5sA--
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 05 Feb 2007 16:05:45 -0500
To: iesg@ietf.org
From: "Andrew G. Malis" <amalis@gmail.com>
In-Reply-To: <E1HE5t1-0005s0-KN@stiedprstage1.ietf.org>
References: <E1HE5t1-0005s0-KN@stiedprstage1.ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
X-Mailman-Approved-At: Tue, 06 Feb 2007 08:05:27 -0500
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>, amalis@gmail.com,
	avt@ietf.org
Subject: [AVT] Re: Last Call: draft-ietf-avt-hc-over-mpls-protocol (Protocol
 Extensions for Header Compression over MPLS) to Proposed Standard 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org
Message-Id: <E1HEQ0m-0005Ac-Nj@megatron.ietf.org>

As one of the co-authors, I just wanted to point out that the 
downreference mentioned below really isn't necessary in the normative 
text, as RFC 3985 was already referenced (twice!) in the informative 
introductory text, and thus can easily be removed from the normative 
text. The only reason we included the reference in the normative 
section is that RFC 3985 is a good resource for people who really 
aren't familiar with the relationship between pseudowires and the 
MPLS tunnels that carry them. As far as I'm concerned, the reference 
can be removed if it is a problem.

Thanks,
Andy

-----------

At 2/5/2007 10:36 AM -0500, The IESG wrote:
>The IESG has received a request from the Audio/Video Transport WG (avt)
>to consider the following document:
>
>- 'Protocol Extensions for Header Compression over MPLS '
>    <draft-ietf-avt-hc-over-mpls-protocol-07.txt> as a Proposed Standard
>
>The original Last Call failed to note that there is a normative
>downreference in the document to RFC 3985, which is an Informational RFC.
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action.  Please send substantive comments to the
>ietf@ietf.org mailing lists by 2007-02-19. Exceptionally,
>comments may be sent to iesg@ietf.org instead. In either case, please
>retain the beginning of the Subject line to allow automated sorting.
>
>The file can be obtained via
>http://www.ietf.org/internet-drafts/draft-ietf-avt-hc-over-mpls-protocol-07.txt
>
>
>IESG discussion can be tracked via
>https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=13573&rfc_flag=0


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



From avt-bounces@ietf.org Wed Feb 07 04:08:10 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HEil8-0006Su-Nx; Wed, 07 Feb 2007 04:06:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HEil7-0006Rz-GS
	for avt@ietf.org; Wed, 07 Feb 2007 04:06:33 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HEil0-0000EG-TB
	for avt@ietf.org; Wed, 07 Feb 2007 04:06:33 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	5B73920B45 for <avt@ietf.org>; Wed,  7 Feb 2007 10:05:05 +0100 (CET)
X-AuditID: c1b4fb3c-af7c7bb0000007de-ad-45c99641f1a7 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	4A3A3205B8 for <avt@ietf.org>; Wed,  7 Feb 2007 10:05:05 +0100 (CET)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Feb 2007 10:05:05 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 7 Feb 2007 10:05:04 +0100
Message-ID: <026F8EEDAD2C4342A993203088C1FC05045D073F@esealmw109.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Non-compound RTCP
Thread-Index: AcdKlw4w8rgWIpLVQRy2f7aOtTTteg==
From: "Ingemar Johansson S \(LU/EAB\)" <ingemar.s.johansson@ericsson.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 07 Feb 2007 09:05:05.0124 (UTC)
	FILETIME=[0EBEA240:01C74A97]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: "Ingemar Johansson S \(LU/EAB\)" <ingemar.s.johansson@ericsson.com>
Subject: [AVT] Non-compound RTCP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi

A little before the new years party I posted an announcement of a new =
draft with the title=20
"Support for non-compund RTCP in RTCP AVPF profile, opportunities and =
consequences", see abstract and link to draft below

Support for non-compound RTCP has since then been been presented for =
inclusion in a 3GPP specification (TS26.114). It was however delayed, =
the argument was mainly that this issue has not been discussed openly in =
IETF at all. So therefore opinons around this issue are very welcome, =
especially regarding:=20

1) Examples where "middle boxes" in a network might discard non-compound =
RTCP. What kind of middle boxes are these.
2) Non-compound RTCP is specified in OMA-PoC (Push to talk). Are there =
any other standards or proprietary solutions or defacto standards that =
already today use non-compund RTCP and thus violate the rules outlined =
in RFC3550? Are there any problems ?

Regards
Ingemar

Abstract:
This memo discusses benefits and issues that arise when allowing RTCP =
packets to be transmitted as non-compound packets, i.e. not follow the =
rules of RFC 3550.  Based on that analysis this memo proposes changes to =
the rules to allow feedback messages to be sent as non-compound RTCP =
packets when using the RTP AVPF profile (RFC 4585)under certain =
conditions.
http://tools.ietf.org/wg/avt/draft-johansson-avt-rtcp-avpf-non-compound-0=
0.txt

*******************************************
Ingemar Johansson
Senior Research Engineer
EAB/TVP - Multimedia Technologies Ericsson Research
Ericsson AB
Box 920
S-971 28 Lule=E5, Sweden
Tel: +46 (0)8 4043042
ECN: 850-43042
Mobile: +46 (0)730 783289
*******************************************
=20

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



From avt-bounces@ietf.org Wed Feb 07 04:46:15 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HEjMV-00071e-2R; Wed, 07 Feb 2007 04:45:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HEjMU-00071Z-CE
	for avt@ietf.org; Wed, 07 Feb 2007 04:45:10 -0500
Received: from mxs2.siemens.at ([194.138.12.133] helo=atvies1zrx.siemens.at)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HEjMH-0000NB-96
	for avt@ietf.org; Wed, 07 Feb 2007 04:45:10 -0500
Received: from vies1kbx.sie.siemens.at ([158.226.129.82])
	by atvies1zrx.siemens.at  with ESMTP id l179hqxi000375;
	Wed, 7 Feb 2007 10:43:52 +0100
Received: from nets139a.ww300.siemens.net ([158.226.129.98])
	by vies1kbx.sie.siemens.at (8.12.11.20060308/8.12.1) with ESMTP id
	l179ihZq010522; Wed, 7 Feb 2007 10:44:43 +0100
Received: from nets13ka.ww300.siemens.net ([158.226.250.80]) by
	nets139a.ww300.siemens.net with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Feb 2007 10:44:43 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: AW: [AVT] Non-compound RTCP
Date: Wed, 7 Feb 2007 10:44:42 +0100
Message-ID: <AE99B7B733E1BB49B019CAA0F806D7A704C390C2@nets13ka.ww300.siemens.net>
In-Reply-To: <026F8EEDAD2C4342A993203088C1FC05045D073F@esealmw109.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Non-compound RTCP
Thread-Index: AcdKlw4w8rgWIpLVQRy2f7aOtTTtegAA3J/g
From: "Kalleitner, Franz" <franz.kalleitner@siemens.com>
To: "Ingemar Johansson S \(LU/EAB\)" <ingemar.s.johansson@ericsson.com>
X-OriginalArrivalTime: 07 Feb 2007 09:44:43.0735 (UTC)
	FILETIME=[9881DE70:01C74A9C]
X-purgate: clean
X-purgate: This mail is considered clean
X-purgate-type: clean
X-purgate-Ad: Checked for Spam by eleven - eXpurgate www.eXpurgate.net
X-purgate-ID: 149917::070207104352-0AAACBB0-1339ABE9/0-0/0-15
X-purgate-size: 2453/999999
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

hi ingemar,

concerning MTSI:=20
wouldn't it be sufficient to follow the 3GPP recommendation to keep the =
size of RTCP packets as small=20
as possible. only to include SR or RR and SDES CNAME item (considering a =
short CNAME). Or do you refer to=20
application dependent RTCP (RTCP-APP)?=20

cheers,
franz

-----Urspr=FCngliche Nachricht-----
Von: Ingemar Johansson S (LU/EAB) =
[mailto:ingemar.s.johansson@ericsson.com]=20
Gesendet: Mittwoch, 07. Februar 2007 10:05
An: avt@ietf.org
Cc: Ingemar Johansson S (LU/EAB)
Betreff: [AVT] Non-compound RTCP

Hi

A little before the new years party I posted an announcement of a new =
draft with the title=20
"Support for non-compund RTCP in RTCP AVPF profile, opportunities and =
consequences", see abstract and link to draft below

Support for non-compound RTCP has since then been been presented for =
inclusion in a 3GPP specification (TS26.114). It was however delayed, =
the argument was mainly that this issue has not been discussed openly in =
IETF at all. So therefore opinons around this issue are very welcome, =
especially regarding:=20

1) Examples where "middle boxes" in a network might discard non-compound =
RTCP. What kind of middle boxes are these.
2) Non-compound RTCP is specified in OMA-PoC (Push to talk). Are there =
any other standards or proprietary solutions or defacto standards that =
already today use non-compund RTCP and thus violate the rules outlined =
in RFC3550? Are there any problems ?

Regards
Ingemar

Abstract:
This memo discusses benefits and issues that arise when allowing RTCP =
packets to be transmitted as non-compound packets, i.e. not follow the =
rules of RFC 3550.  Based on that analysis this memo proposes changes to =
the rules to allow feedback messages to be sent as non-compound RTCP =
packets when using the RTP AVPF profile (RFC 4585)under certain =
conditions.
http://tools.ietf.org/wg/avt/draft-johansson-avt-rtcp-avpf-non-compound-0=
0.txt

*******************************************
Ingemar Johansson
Senior Research Engineer
EAB/TVP - Multimedia Technologies Ericsson Research
Ericsson AB
Box 920
S-971 28 Lule=E5, Sweden
Tel: +46 (0)8 4043042
ECN: 850-43042
Mobile: +46 (0)730 783289
*******************************************
=20

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

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



From avt-bounces@ietf.org Wed Feb 07 09:08:10 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HEnRW-00016l-KS; Wed, 07 Feb 2007 09:06:38 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HEnRV-00016f-K6
	for avt@ietf.org; Wed, 07 Feb 2007 09:06:37 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HEnRL-0003RO-QB
	for avt@ietf.org; Wed, 07 Feb 2007 09:06:37 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	A4D9E21687; Wed,  7 Feb 2007 15:04:53 +0100 (CET)
X-AuditID: c1b4fb3e-b06d4bb0000007e1-ca-45c9dc85d21a 
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	8B29D20F93; Wed,  7 Feb 2007 15:04:53 +0100 (CET)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Feb 2007 15:04:53 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] Non-compound RTCP
Date: Wed, 7 Feb 2007 15:04:52 +0100
Message-ID: <026F8EEDAD2C4342A993203088C1FC050460FFA1@esealmw109.eemea.ericsson.se>
In-Reply-To: <AE99B7B733E1BB49B019CAA0F806D7A704C390C2@nets13ka.ww300.siemens.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Non-compound RTCP
Thread-Index: AcdKlw4w8rgWIpLVQRy2f7aOtTTtegAA3J/gAAfiCWA=
From: "Ingemar Johansson S \(LU/EAB\)" <ingemar.s.johansson@ericsson.com>
To: "Kalleitner, Franz" <franz.kalleitner@siemens.com>
X-OriginalArrivalTime: 07 Feb 2007 14:04:53.0425 (UTC)
	FILETIME=[F09B8A10:01C74AC0]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi

This issue is debated to some extent in the draft=20
http://tools.ietf.org/wg/avt/draft-johansson-avt-rtcp-avpf-non-compound-0=
0.txt
Minimum compound RTCP will typically have a size in the order 80-90 =
bytes + IP/UDP header. This is with the SR and SDES CNAME items. If one =
wish to add adaptation signaling like described in 3GPP TS26.114 another =
extra 16 bytes is needed.=20
In a 3GPP VoIP service these large RTCP packets are likely to face =
severe problems in terms of lost RTCP packets in bad coverage =
situations. This means that adaptation feedback runs a high risk of =
being nonfunctional in the cases where it is needed the most (namely bad =
channel conditions). The simple reason is that large packets will be =
segmented and therefore the loss probablity is increased.

The purpose of non-compound RTCP is to be able to transmit adaptation =
feedback like the one described in 3GPP TS26.114 more reliably. In the =
VoIP example these non-compound feedback packets are of the size 16bytes =
+ IP/UDP which is considerably smaller than the ~100byte figure above.

Note 1: I have deliberately chosen to quote the figures without IP/UDP =
header, the simple reason is that header compression almost completely =
removes this overhead.

Note 2: The TS26.114 is available at=20
http://www.3gpp.org/ftp/Specs/archive/26_series/26.114/26114-120.zip
The adaptation feedback is described in section 10.2

Regards
Ingemar=20





> -----Original Message-----
> From: Kalleitner, Franz [mailto:franz.kalleitner@siemens.com]=20
> Sent: den 7 februari 2007 10:45
> To: Ingemar Johansson S (LU/EAB)
> Cc: avt@ietf.org
> Subject: AW: [AVT] Non-compound RTCP
>=20
> hi ingemar,
>=20
> concerning MTSI:=20
> wouldn't it be sufficient to follow the 3GPP recommendation=20
> to keep the size of RTCP packets as small as possible. only=20
> to include SR or RR and SDES CNAME item (considering a short=20
> CNAME). Or do you refer to application dependent RTCP (RTCP-APP)?=20
>=20
> cheers,
> franz
>=20
> -----Urspr=FCngliche Nachricht-----
> Von: Ingemar Johansson S (LU/EAB)=20
> [mailto:ingemar.s.johansson@ericsson.com]
> Gesendet: Mittwoch, 07. Februar 2007 10:05
> An: avt@ietf.org
> Cc: Ingemar Johansson S (LU/EAB)
> Betreff: [AVT] Non-compound RTCP
>=20
> Hi
>=20
> A little before the new years party I posted an announcement=20
> of a new draft with the title "Support for non-compund RTCP=20
> in RTCP AVPF profile, opportunities and consequences", see=20
> abstract and link to draft below
>=20
> Support for non-compound RTCP has since then been been=20
> presented for inclusion in a 3GPP specification (TS26.114).=20
> It was however delayed, the argument was mainly that this=20
> issue has not been discussed openly in IETF at all. So=20
> therefore opinons around this issue are very welcome,=20
> especially regarding:=20
>=20
> 1) Examples where "middle boxes" in a network might discard=20
> non-compound RTCP. What kind of middle boxes are these.
> 2) Non-compound RTCP is specified in OMA-PoC (Push to talk).=20
> Are there any other standards or proprietary solutions or=20
> defacto standards that already today use non-compund RTCP and=20
> thus violate the rules outlined in RFC3550? Are there any problems ?
>=20
> Regards
> Ingemar
>=20
> Abstract:
> This memo discusses benefits and issues that arise when=20
> allowing RTCP packets to be transmitted as non-compound=20
> packets, i.e. not follow the rules of RFC 3550.  Based on=20
> that analysis this memo proposes changes to the rules to=20
> allow feedback messages to be sent as non-compound RTCP=20
> packets when using the RTP AVPF profile (RFC 4585)under=20
> certain conditions.
> http://tools.ietf.org/wg/avt/draft-johansson-avt-rtcp-avpf-non
> -compound-00.txt
>=20
> *******************************************
> Ingemar Johansson
> Senior Research Engineer
> EAB/TVP - Multimedia Technologies Ericsson Research Ericsson=20
> AB Box 920
> S-971 28 Lule=E5, Sweden
> Tel: +46 (0)8 4043042
> ECN: 850-43042
> Mobile: +46 (0)730 783289
> *******************************************
> =20
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>=20

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



From avt-bounces@ietf.org Wed Feb 07 09:44:20 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HEo1K-0001TK-LP; Wed, 07 Feb 2007 09:43:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HEX50-0005jd-QV
	for avt@ietf.org; Tue, 06 Feb 2007 15:38:18 -0500
Received: from grid.lrg.ufsc.br ([150.162.63.19])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HEX4Y-0004OU-Oc
	for avt@ietf.org; Tue, 06 Feb 2007 15:37:52 -0500
Received: from localhost.grid.lrg.ufsc.br (localhost [127.0.0.1])
	by grid.lrg.ufsc.br (Postfix) with ESMTP id AF43812B0F2;
	Tue,  6 Feb 2007 17:46:18 -0200 (BRST)
X-Original-To: mycolleagues@grid.lrg.ufsc.br
Delivered-To: mycolleagues@grid.lrg.ufsc.br
Received: from jupiter.ece.ac.ae (unknown [194.170.15.36])
	by grid.lrg.ufsc.br (Postfix) with ESMTP id 8D2437F621B
	for <mycolleagues@grid.lrg.ufsc.br>;
	Fri,  2 Feb 2007 19:48:17 -0200 (BRST)
Received: from ACER36906.ece.ac.ae ([194.170.15.100])
	by jupiter.ece.ac.ae (8.12.7/8.12.7) with ESMTP id l12MTXl2000659
	for <mycolleagues@grid.lrg.ufsc.br>;
	Sat, 3 Feb 2007 02:29:33 +0400 (GMT)
Message-Id: <7.0.1.0.0.20070203022943.038c6148@ece.ac.ae>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Sat, 03 Feb 2007 02:34:41 +0400
To: mycolleagues@grid.lrg.ufsc.br
From: Mohammed Al-Mualla <almualla@ece.ac.ae>
Mime-Version: 1.0
X-Mailman-Approved-At: Tue, 06 Feb 2007 17:16:07 -0200
X-BeenThere: mycolleagues@grid.lrg.ufsc.br
X-Mailman-Version: 2.1.8
Precedence: list
Content-Type: multipart/mixed; boundary="===============1670637502=="
X-Spam-Score: 1.2 (+)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
X-Mailman-Approved-At: Wed, 07 Feb 2007 09:43:37 -0500
Cc: 
Subject: [AVT] [mycolleagues] IEEE ICSPC07 Call-for-Papers
X-BeenThere: avt@ietf.org
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--===============1670637502==
Content-Type: text/html; charset="us-ascii"

<html>
<body>
Dear Colleagues,<br><br>
PLEASE ACCEPT OUR APOLOGIES IF YOU RECEIVE MULTIPLE COPIES OF THIS
CFP<br><br>
The <font color="#FF0000"><b>2007 IEEE International Conference on Signal
Processing and Communication (ICSPC07)</b></font> will be held
<font color="#0000FF"><b>24-27 November 2007 in Dubai, United Arab
Emirates</b></font>.<br><br>
The conference will include keynote addresses, tutorials, special,
regular and poster sessions. All papers will be peer reviewed. Acceptance
will be based on quality, relevance and originality. Accepted papers will
be published in the conference proceedings and will be included in IEEE
Explore.<br><br>
<font color="#0000FF"><b>SCOPE<br><br>
</b></font>Topics will include, but are not limited to, the
following:<br><br>
Digital Signal Processing<br>
DSP Implementation and Embedded Systems<br>
Audio/Speech Processing and Coding<br>
Image/Video Processing and Coding<br>
Watermarking and Information Hiding<br>
Multimedia Communications<br>
Sensor Array and Multi-channel Processing<br>
Time-Frequency/Time-Scale Analysis<br>
Analog and Mixed Signal Processing<br>
Parallel and Distributed Processing<br>
Internet Signal Processing<br>
Signal Processing for Communications<br>
Modulation and Channel Coding<br>
Next Generation Mobile Communications<br>
Ad-Hoc and Sensor Networks<br>
RF and Wireless Communications<br>
Optical Communications<br>
Communication and Broadband Networks<br>
Cryptography and Network Security<br>
Soft Computing and Machine learning for Signal Processing and<br>
Communications<br>
Applications (Biomedical, Bioinformatics, Genomic, Seismic, Radar,
Sonar,<br>
Remote Sensing, Positioning, etc.)<br>
Signal Processing and Communications Education<br><br>
<br>
<font color="#0000FF"><b>SUBMISSION<br><br>
</b></font>Prospective authors are invited to submit full-length (4
pages) paper proposals for review. Proposals for tutorials and special
sessions are also welcome. The submission procedures can be found on the
conference web site:<br><br>
<a href="http://www.icspc07.org/" eudora="autourl">
http://www.icspc07.org<br>
</a>OR<br>
<a href="http://www.icspc.info/" eudora="autourl">
http://www.icspc.info<br><br>
</a>All submissions must be made on-line and must follow the guidelines
given on the web site.<br><br>
<br>
<font color="#0000FF"><b>SCHEDULE<br><br>
</b></font>Submission of proposals for tutorials and special
sessions&nbsp;&nbsp; March 5th, 2007<br><br>
<font color="#FF0000"><b>Submission of full-paper
proposals<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>April 2nd,
2007<br><br>
</b></font>Notification of
acceptance<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>June 4th,
2007<br><br>
Submission of final version of
paper<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>October 1st,
2007<br><br>
<br><br>
<br>
<font color="#0000FF"><b>ICSPC 2007 Conference Secretariat,<br>
P. O. Box: 573, Sharjah, United Arab Emirates (U.A.E.),<br>
Fax: +971 6 5611789<br>
secretariat@icspc07.org <br><br>
</font></b></body>
</html>


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

_______________________________________________
mycolleagues mailing list
mycolleagues@grid.lrg.ufsc.br
http://grid.lrg.ufsc.br/mailman/listinfo/mycolleagues

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

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

--===============1670637502==--




From avt-bounces@ietf.org Wed Feb 07 13:06:25 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HErAK-0007zt-3q; Wed, 07 Feb 2007 13:05:08 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HErAI-0007zl-KG
	for avt@ietf.org; Wed, 07 Feb 2007 13:05:06 -0500
Received: from ihemail1.lucent.com ([135.245.0.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HErAG-0001pO-6D
	for avt@ietf.org; Wed, 07 Feb 2007 13:05:06 -0500
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l17I4lvY012878
	for <avt@ietf.org>; Wed, 7 Feb 2007 12:05:01 -0600 (CST)
Received: from inexp02.in.lucent.com ([135.254.223.66]) by
	ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Feb 2007 12:04:53 -0600
Received: from INEXC1U01.in.lucent.com ([135.254.223.20]) by
	inexp02.in.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Feb 2007 23:34:32 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 7 Feb 2007 23:34:29 +0530
Message-ID: <AC93587F24F9734C90394F68B39B670637FA23@INEXC1U01.in.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Possible issues in RTP/RTCP (RFC 3550)
thread-index: AcdKydv/COpraUhGTAuZ9FtaDgrXaAAGGEPA
From: "Bhattacharya, Abhijit \(Abhijit\)" <abhattacharya@alcatel-lucent.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 07 Feb 2007 18:04:32.0892 (UTC)
	FILETIME=[6B7013C0:01C74AE2]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8
Subject: [AVT] Possible issues in RTP/RTCP (RFC 3550)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0049542272=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0049542272==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C74AE2.6B5C0F66"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C74AE2.6B5C0F66
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20
Hi all,

I feel the following issues exist in RFC 3550 (RFC for RTP and RTCP).

Problem 1:
If an RTP packet arrives after the jitter tolerance period of that
network node on which the packet is received, the packet becomes useless
because the frame which was supposed to contain this packet has already
been played out to avoid delay. So this packet, which arrived after the
stipulated jitter tolearnce period, is as good as lost for the receiving
node, although it has arrived at its destination. At present this packet
is not considered as a lost packet.

Example:

If an RTP packet of sequence number n arrives at time t1 at a network
node N with ptime of p and jitter tolerance of J, then the expected time
e of arrival of RTP packet of sequence number n-1 at the same node is
(t1 - p). Hence the RTP packet with sequence number n-1 is a delayed
packet if it arrived at t2 and (t2 - e) > J. This is because, if the RTP
packet of sequence number n-1 comes after that, its likely that the next
RTP packet would have been played out thus making the RTP packet with
sequence number n-1 useless.

Effect:
It gives a wrong impression of loss of packets as the quality of the
media (audio/video) played out is definitely reduced due to the absence
of the packet which arrived late. If this happens more frequently, the
quality of the media will be significantly degraded although it will not
be reflected in the report showing loss of packets.

=20

Problem 2:=20

Now if a duplicate RTP packet is received, it is not handled separately.
It is considered for all the feedback report generation. Since loss of
packets is equal to expected packets - the received number of packets,
let us consider the following example.

Example:=20

Let us consider the expected packet count to be c and received packets
to be r which includes d number of duplicate packets.  Now lost packet
count p is equal to c-r, but actually the count MUST be c-r-d.  Thus the
lost packet count gives a wrong impression.


I need some advice how to go about with this issue.=20

Thanks and regards,

Abhijit Bhattacharya

=20


------_=_NextPart_001_01C74AE2.6B5C0F66
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3020" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>Hi =
all,<BR><BR>I=20
feel the following issues exist in RFC 3550 (RFC for RTP and =
RTCP).<BR><BR><FONT=20
color=3D#0000ff>Problem 1:</FONT><FONT color=3D#0000ff><BR>If an =
RTP&nbsp;packet=20
arrives after the jitter tolerance period of that network node on which =
the=20
packet is received, the packet becomes useless because the frame which =
was=20
supposed to contain this packet has already been played out to avoid =
delay. So=20
this packet, which arrived after the stipulated jitter tolearnce period, =
is as=20
good as lost for the receiving node, although it has arrived at its =
destination.=20
At present this packet is not considered as a lost=20
packet.<BR><BR>Example:<BR><BR>If an RTP packet of sequence number n =
arrives at=20
time t1 at a network node N with ptime of p and jitter tolerance of J, =
then the=20
expected time e of arrival of RTP packet of sequence number n-1 at the =
same node=20
is (t1 - p). Hence the RTP packet with sequence number n-1 is a delayed =
packet=20
if it arrived at t2 and&nbsp;(t2 - e) &gt; J. This is because, if the =
RTP packet=20
of sequence number n-1 comes after that, its likely that the next RTP =
packet=20
would have been played out thus making the RTP packet with sequence =
number n-1=20
useless.<BR><BR>Effect:<BR>It gives a wrong impression of loss of =
packets as the=20
quality of the media (audio/video) played out is definitely reduced due =
to the=20
absence of the packet which arrived late. If this happens more =
frequently, the=20
quality of the media will be significantly degraded although it will not =
be=20
reflected in the&nbsp;report showing loss of packets</FONT>.</DIV>
<P><FONT face=3DArial size=3D2></FONT>&nbsp;</P>
<P><FONT color=3D#0000ff>Problem 2:&nbsp;</FONT></P>
<P><FONT color=3D#0000ff>Now if a duplicate RTP packet is received, it =
is not=20
handled&nbsp;separately.&nbsp; It is considered for all the feedback =
report=20
generation.&nbsp;Since loss of packets is equal to expected packets - =
the=20
received&nbsp;number of packets, let us consider the following=20
example.</FONT></P><FONT face=3DArial size=3D2></FONT>
<P><FONT color=3D#0000ff>Example: </FONT></P>
<P><FONT color=3D#0000ff>Let us consider the expected packet count to be =
c=20
and&nbsp;received packets to be r which includes d number of=20
duplicate&nbsp;packets.&nbsp; Now lost packet count p is equal to c-r, =
but=20
actually the&nbsp;count MUST be c-r-d.&nbsp; Thus the lost packet count =
gives a=20
wrong&nbsp;impression</FONT>.<BR></P>
<P>I need some advice how to go about with this issue. </P>
<P>Thanks and regards,</P>
<P>Abhijit Bhattacharya</P>
<P>&nbsp;</P></BODY></HTML>

------_=_NextPart_001_01C74AE2.6B5C0F66--


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

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

--===============0049542272==--




From avt-bounces@ietf.org Wed Feb 07 17:14:00 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HEv1e-0006j9-DC; Wed, 07 Feb 2007 17:12:26 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HEv1d-0006ig-8s
	for avt@ietf.org; Wed, 07 Feb 2007 17:12:25 -0500
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HEv1c-0007Ic-0T for avt@ietf.org; Wed, 07 Feb 2007 17:12:25 -0500
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Feb 2007 17:12:19 -0500
To: "Bhattacharya, Abhijit \(Abhijit\)" <abhattacharya@alcatel-lucent.com>
Subject: Re: [AVT] Possible issues in RTP/RTCP (RFC 3550)
References: <AC93587F24F9734C90394F68B39B670637FA23@INEXC1U01.in.lucent.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Wed, 07 Feb 2007 17:12:18 -0500
In-Reply-To: <AC93587F24F9734C90394F68B39B670637FA23@INEXC1U01.in.lucent.com>
	(Abhijit
	Bhattacharya's message of "Wed, 7 Feb 2007 23:34:29 +0530")
Message-ID: <ybuy7n91ut9.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 07 Feb 2007 22:12:19.0377 (UTC)
	FILETIME=[088DAA10:01C74B05]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

"Bhattacharya, Abhijit \(Abhijit\)" <abhattacharya@alcatel-lucent.com> writes:
>I feel the following issues exist in RFC 3550 (RFC for RTP and RTCP).
>
>Problem 1:
>If an RTP packet arrives after the jitter tolerance period of that
>network node on which the packet is received, the packet becomes useless
>because the frame which was supposed to contain this packet has already
>been played out to avoid delay. So this packet, which arrived after the
>stipulated jitter tolearnce period, is as good as lost for the receiving
>node, although it has arrived at its destination. At present this packet
>is not considered as a lost packet.

>Effect:
>It gives a wrong impression of loss of packets as the quality of the
>media (audio/video) played out is definitely reduced due to the absence
>of the packet which arrived late. If this happens more frequently, the
>quality of the media will be significantly degraded although it will not
>be reflected in the report showing loss of packets.

Correct, though RTCP stats are not a measure of media quality, so the
use you're assuming isn't the use that RTCP SR/RR were designed for.  For
media quality RTCP, see some of the other specs/drafts (RTCP-XR, video, etc).

>Problem 2: 
>
>Now if a duplicate RTP packet is received, it is not handled separately.
>It is considered for all the feedback report generation. Since loss of
>packets is equal to expected packets - the received number of packets,

Correct.

Again, SR/RR RTCP are not media-quality reports (or even very good
link-quality reports).  Don't try to use them for that.  SR/RR are
(apparently) designed to be simple to calculate and not require any
significant amount of state to generate (like a list of recent missing
packets). 

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


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



From avt-bounces@ietf.org Wed Feb 07 17:42:24 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HEvU6-0003XO-Vq; Wed, 07 Feb 2007 17:41:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HEvU5-0003Mi-EY
	for avt@ietf.org; Wed, 07 Feb 2007 17:41:49 -0500
Received: from mx.cbeyond.com ([66.180.96.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HEvU3-0003hU-SQ
	for avt@ietf.org; Wed, 07 Feb 2007 17:41:49 -0500
Received: from [69.15.238.196] (port=1314 helo=TELCHADCPC)
	by mx.cbeyond.com with asmtp (Exim 4.34)
	id 1HEvU2-0000ur-PC; Wed, 07 Feb 2007 17:41:47 -0500
From: "Alan Clark" <alan.d.clark@telchemy.com>
To: "'Bhattacharya, Abhijit \(Abhijit\)'" <abhattacharya@alcatel-lucent.com>, 
	<avt@ietf.org>
Subject: RE: [AVT] Possible issues in RTP/RTCP (RFC 3550)
Date: Wed, 7 Feb 2007 17:41:45 -0500
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcdKydv/COpraUhGTAuZ9FtaDgrXaAAGGEPAAAmIY2A=
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
In-Reply-To: <AC93587F24F9734C90394F68B39B670637FA23@INEXC1U01.in.lucent.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 850245b51c39701e2700a112f3032caa
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1904854896=="
Errors-To: avt-bounces@ietf.org
Message-Id: <E1HEvU6-0003XO-Vq@megatron.ietf.org>

This is a multi-part message in MIME format.

--===============1904854896==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0033_01C74ADF.3DA0CFA0"

This is a multi-part message in MIME format.

------=_NextPart_000_0033_01C74ADF.3DA0CFA0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

As Randell stated in his reply - you should consider using RTCP XR (RFC3611)
for multimedia applications.
 
The RFC3611 VoIP metrics block has
- packet loss rate (which is defined as NOT including duplicate packets)
- packet discard rate (packets that arrived too late were discarded)
 
- burst/gap metrics - which report separately on periods of high and low
loss/discard.  Using the default value for Gmin of 16
 .....a burst would be a period of 5% or higher packet loss/discard
 .....during gaps, any lost or discarded packets would be preceded and
followed by at least 16 good packets
 
- etc
 
Regards
 
Alan Clark
Telchemy
 
 

  _____  

From: Bhattacharya, Abhijit (Abhijit)
[mailto:abhattacharya@alcatel-lucent.com] 
Sent: Wednesday, February 07, 2007 1:04 PM
To: avt@ietf.org
Subject: [AVT] Possible issues in RTP/RTCP (RFC 3550)


 
Hi all,

I feel the following issues exist in RFC 3550 (RFC for RTP and RTCP).

Problem 1:
If an RTP packet arrives after the jitter tolerance period of that network
node on which the packet is received, the packet becomes useless because the
frame which was supposed to contain this packet has already been played out
to avoid delay. So this packet, which arrived after the stipulated jitter
tolearnce period, is as good as lost for the receiving node, although it has
arrived at its destination. At present this packet is not considered as a
lost packet.

Example:

If an RTP packet of sequence number n arrives at time t1 at a network node N
with ptime of p and jitter tolerance of J, then the expected time e of
arrival of RTP packet of sequence number n-1 at the same node is (t1 - p).
Hence the RTP packet with sequence number n-1 is a delayed packet if it
arrived at t2 and (t2 - e) > J. This is because, if the RTP packet of
sequence number n-1 comes after that, its likely that the next RTP packet
would have been played out thus making the RTP packet with sequence number
n-1 useless.

Effect:
It gives a wrong impression of loss of packets as the quality of the media
(audio/video) played out is definitely reduced due to the absence of the
packet which arrived late. If this happens more frequently, the quality of
the media will be significantly degraded although it will not be reflected
in the report showing loss of packets.

 

Problem 2: 

Now if a duplicate RTP packet is received, it is not handled separately.  It
is considered for all the feedback report generation. Since loss of packets
is equal to expected packets - the received number of packets, let us
consider the following example.

Example: 

Let us consider the expected packet count to be c and received packets to be
r which includes d number of duplicate packets.  Now lost packet count p is
equal to c-r, but actually the count MUST be c-r-d.  Thus the lost packet
count gives a wrong impression.


I need some advice how to go about with this issue. 

Thanks and regards,

Abhijit Bhattacharya

 


------=_NextPart_000_0033_01C74ADF.3DA0CFA0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D220123622-07022007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>As Randell stated in his reply - you should =
consider using=20
RTCP XR (RFC3611) for multimedia applications.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D220123622-07022007><FONT =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D220123622-07022007><FONT =
color=3D#0000ff=20
size=3D2>The RFC3611 VoIP metrics block has</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D220123622-07022007><FONT =
color=3D#0000ff=20
size=3D2>- packet loss rate (which is defined as NOT including duplicate =

packets)</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D220123622-07022007><FONT =
color=3D#0000ff=20
size=3D2>- packet discard rate (packets that arrived too late&nbsp;were=20
discarded)</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D220123622-07022007><FONT =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D220123622-07022007><FONT =
color=3D#0000ff=20
size=3D2>- burst/gap metrics - which report separately on periods of =
high and low=20
loss/discard.&nbsp; Using the default value for Gmin of =
16</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D220123622-07022007><FONT =
color=3D#0000ff=20
size=3D2>&nbsp;.....a burst would be a period of 5% or higher packet=20
loss/discard</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D220123622-07022007><FONT =
color=3D#0000ff=20
size=3D2>&nbsp;.....during gaps, any lost or discarded packets would be =
preceded=20
and followed by at least 16 good packets</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D220123622-07022007><FONT =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D220123622-07022007><FONT =
color=3D#0000ff=20
size=3D2>- etc</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D220123622-07022007><FONT =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D220123622-07022007><FONT =
color=3D#0000ff=20
size=3D2>Regards</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D220123622-07022007><FONT =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D220123622-07022007><FONT =
color=3D#0000ff=20
size=3D2>Alan Clark</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D220123622-07022007><FONT =
color=3D#0000ff=20
size=3D2>Telchemy</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D220123622-07022007></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D220123622-07022007><FONT =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Bhattacharya, Abhijit =
(Abhijit)=20
[mailto:abhattacharya@alcatel-lucent.com] <BR><B>Sent:</B> Wednesday, =
February=20
07, 2007 1:04 PM<BR><B>To:</B> avt@ietf.org<BR><B>Subject:</B> [AVT] =
Possible=20
issues in RTP/RTCP (RFC 3550)<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>Hi =
all,<BR><BR>I=20
feel the following issues exist in RFC 3550 (RFC for RTP and =
RTCP).<BR><BR><FONT=20
color=3D#0000ff>Problem 1:</FONT><FONT color=3D#0000ff><BR>If an =
RTP&nbsp;packet=20
arrives after the jitter tolerance period of that network node on which =
the=20
packet is received, the packet becomes useless because the frame which =
was=20
supposed to contain this packet has already been played out to avoid =
delay. So=20
this packet, which arrived after the stipulated jitter tolearnce period, =
is as=20
good as lost for the receiving node, although it has arrived at its =
destination.=20
At present this packet is not considered as a lost=20
packet.<BR><BR>Example:<BR><BR>If an RTP packet of sequence number n =
arrives at=20
time t1 at a network node N with ptime of p and jitter tolerance of J, =
then the=20
expected time e of arrival of RTP packet of sequence number n-1 at the =
same node=20
is (t1 - p). Hence the RTP packet with sequence number n-1 is a delayed =
packet=20
if it arrived at t2 and&nbsp;(t2 - e) &gt; J. This is because, if the =
RTP packet=20
of sequence number n-1 comes after that, its likely that the next RTP =
packet=20
would have been played out thus making the RTP packet with sequence =
number n-1=20
useless.<BR><BR>Effect:<BR>It gives a wrong impression of loss of =
packets as the=20
quality of the media (audio/video) played out is definitely reduced due =
to the=20
absence of the packet which arrived late. If this happens more =
frequently, the=20
quality of the media will be significantly degraded although it will not =
be=20
reflected in the&nbsp;report showing loss of packets</FONT>.</DIV>
<P><FONT face=3DArial size=3D2></FONT>&nbsp;</P>
<P><FONT color=3D#0000ff>Problem 2:&nbsp;</FONT></P>
<P><FONT color=3D#0000ff>Now if a duplicate RTP packet is received, it =
is not=20
handled&nbsp;separately.&nbsp; It is considered for all the feedback =
report=20
generation.&nbsp;Since loss of packets is equal to expected packets - =
the=20
received&nbsp;number of packets, let us consider the following=20
example.</FONT></P><FONT face=3DArial size=3D2></FONT>
<P><FONT color=3D#0000ff>Example: </FONT></P>
<P><FONT color=3D#0000ff>Let us consider the expected packet count to be =
c=20
and&nbsp;received packets to be r which includes d number of=20
duplicate&nbsp;packets.&nbsp; Now lost packet count p is equal to c-r, =
but=20
actually the&nbsp;count MUST be c-r-d.&nbsp; Thus the lost packet count =
gives a=20
wrong&nbsp;impression</FONT>.<BR></P>
<P>I need some advice how to go about with this issue. </P>
<P>Thanks and regards,</P>
<P>Abhijit Bhattacharya</P>
<P>&nbsp;</P></BODY></HTML>

------=_NextPart_000_0033_01C74ADF.3DA0CFA0--



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

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

--===============1904854896==--





From avt-bounces@ietf.org Thu Feb 08 06:26:08 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HF7OE-0000RT-4F; Thu, 08 Feb 2007 06:24:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HEoPl-0004l4-Lp
	for avt@ietf.org; Wed, 07 Feb 2007 10:08:53 -0500
Received: from ihemail1.lucent.com ([135.245.0.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HEoPi-0000iY-4G
	for avt@ietf.org; Wed, 07 Feb 2007 10:08:53 -0500
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l17F8mfU004920
	for <avt@ietf.org>; Wed, 7 Feb 2007 09:08:49 -0600 (CST)
Received: from inexp01.in.lucent.com ([135.254.223.65]) by
	ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Feb 2007 09:08:49 -0600
Received: from INEXC1U01.in.lucent.com ([135.254.223.20]) by
	inexp01.in.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Feb 2007 20:38:45 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 7 Feb 2007 20:38:44 +0530
Message-ID: <AC93587F24F9734C90394F68B39B670637FA01@INEXC1U01.in.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Possible issues in RTP/RTCP (RFC 3550)
thread-index: AcdKydv/COpraUhGTAuZ9FtaDgrXaA==
From: "Bhattacharya, Abhijit \(Abhijit\)" <abhattacharya@alcatel-lucent.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 07 Feb 2007 15:08:45.0132 (UTC)
	FILETIME=[DC7BA0C0:01C74AC9]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 93e7fb8fef2e780414389440f367c879
X-Mailman-Approved-At: Thu, 08 Feb 2007 06:24:32 -0500
Subject: [AVT] Possible issues in RTP/RTCP (RFC 3550)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2098138811=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2098138811==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C74AC9.DC8CC73E"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C74AC9.DC8CC73E
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

I feel the following issues exist in RFC 3550 (RFC for RTP and RTCP).

Problem 1:
If an RTP packet arrives after the jitter tolerance period of that
network node on which the packet is received, the packet becomes useless
because the frame which was supposed to contain this packet has already
been played out to avoid delay. So this packet, which arrived after the
stipulated jitter tolearnce period, is as good as lost for the receiving
node, although it has arrived at its destination. At present this packet
is not considered as a lost packet.

Example:

If an RTP packet of sequence number n arrives at time t1 at a network
node N with ptime of p and jitter tolerance of J, then the expected time
e of arrival of RTP packet of sequence number n-1 at the same node is
(t1 - p). Hence the RTP packet with sequence number n-1 is a delayed
packet if it arrived at t2 and (t2 - e) > J. This is because, if the RTP
packet of sequence number n-1 comes after that, its likely that the next
RTP packet would have been played out thus making the RTP packet with
sequence number n-1 useless.

Effect:
It gives a wrong impression of loss of packets as the quality of the
media (audio/video) played out is definitely reduced due to the absence
of the packet which arrived late. If this happens more frequently, the
quality of the media will be significantly degraded although it will not
be reflected in the report showing loss of packets.

=20

Problem 2:=20

Now if a duplicate RTP packet is received, it is not handled separately.
It is considered for all the feedback report generation. Since loss of
packets is equal to expected packets - the received number of packets,
let us consider the following example.

Example:=20

Let us consider the expected packet count to be c and received packets
to be r which includes d number of duplicate packets.  Now lost packet
count p is equal to c-r, but actually the count MUST be c-r-d.  Thus the
lost packet count gives a wrong impression.


I need some advice how to go about with this issue.=20

Thanks and regards,

Abhijit Bhattacharya

=20


------_=_NextPart_001_01C74AC9.DC8CC73E
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3020" name=3DGENERATOR></HEAD>
<BODY><!-- Converted from text/plain format -->
<P>Hi all,<BR><BR>I feel the following issues exist in RFC 3550 (RFC for =
RTP and=20
RTCP).<BR><BR><FONT color=3D#0000ff>Problem 1:</FONT><FONT =
color=3D#0000ff><BR>If an=20
RTP&nbsp;packet arrives after the jitter tolerance period of that =
network node=20
on which the packet is received, the packet becomes useless because the =
frame=20
which was supposed to contain this packet has already been played out to =
avoid=20
delay. So this packet, which arrived after the stipulated jitter =
tolearnce=20
period, is as good as lost for the receiving node, although it has =
arrived at=20
its destination. At present this packet is not considered as a lost=20
packet.<BR><BR>Example:<BR><BR>If an RTP packet of sequence number n =
arrives at=20
time t1 at a network node N with ptime of p and jitter tolerance of J, =
then the=20
expected time e of arrival of RTP packet of sequence number n-1 at the =
same node=20
is (t1 - p). Hence the RTP packet with sequence number n-1 is a delayed =
packet=20
if it arrived at t2 and&nbsp;(t2 - e) &gt; J. This is because, if the =
RTP packet=20
of sequence number n-1 comes after that, its likely that the next RTP =
packet=20
would have been played out thus making the RTP packet with sequence =
number n-1=20
useless.<BR><BR>Effect:<BR>It gives a wrong impression of loss of =
packets as the=20
quality of the media (audio/video) played out is definitely reduced due =
to the=20
absence of the packet which arrived late. If this happens more =
frequently, the=20
quality of the media will be significantly degraded although it will not =
be=20
reflected in the&nbsp;report showing loss of packets</FONT>.</P>
<P><FONT face=3DArial size=3D2></FONT>&nbsp;</P>
<P><FONT color=3D#0000ff>Problem 2:&nbsp;</FONT></P>
<P><FONT color=3D#0000ff>Now if a duplicate RTP packet is received, it =
is not=20
handled&nbsp;separately.&nbsp; It is considered for all the feedback =
report=20
generation.&nbsp;Since loss of packets is equal to expected packets - =
the=20
received&nbsp;number of packets, let us consider the following=20
example.</FONT></P><FONT face=3DArial size=3D2></FONT>
<P><FONT color=3D#0000ff>Example: </FONT></P>
<P><FONT color=3D#0000ff>Let us consider the expected packet count to be =
c=20
and&nbsp;received packets to be r which includes d number of=20
duplicate&nbsp;packets.&nbsp; Now lost packet count p is equal to c-r, =
but=20
actually the&nbsp;count MUST be c-r-d.&nbsp; Thus the lost packet count =
gives a=20
wrong&nbsp;impression</FONT>.<BR></P>
<P>I need some advice how to go about with this issue. </P>
<P>Thanks and regards,</P>
<P>Abhijit Bhattacharya</P>
<P>&nbsp;</P></BODY></HTML>

------_=_NextPart_001_01C74AC9.DC8CC73E--


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

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

--===============2098138811==--




From avt-bounces@ietf.org Thu Feb 08 11:39:00 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HFCHN-0000bM-Gj; Thu, 08 Feb 2007 11:37:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HFCHL-0000aL-QM
	for avt@ietf.org; Thu, 08 Feb 2007 11:37:47 -0500
Received: from zcars04e.nortel.com ([47.129.242.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HFCCE-0003ZH-Iw
	for avt@ietf.org; Thu, 08 Feb 2007 11:32:36 -0500
Received: from zcarhxs1.corp.nortel.com (zcarhxs1.corp.nortel.com
	[47.129.230.89])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	l18GOVG12802; Thu, 8 Feb 2007 11:24:32 -0500 (EST)
Received: from [47.130.19.101] ([47.130.19.101] RDNS failed) by
	zcarhxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 8 Feb 2007 11:32:25 -0500
Message-ID: <45CB5084.4070509@nortel.com>
Date: Thu, 08 Feb 2007 11:32:04 -0500
From: "Tom-PT Taylor" <taylor@nortel.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: avt@ietf.org
References: <45A317A3.8020703@nortel.com>
In-Reply-To: <45A317A3.8020703@nortel.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Feb 2007 16:32:25.0489 (UTC)
	FILETIME=[B7431010:01C74B9E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Cc: Ladan Gharai <ladan@ISI.EDU>, Dave Singer <singer@apple.com>
Subject: [AVT] Re: Review requested: draft-ietf-avt-smpte-rtp-07.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Ladan Gharai, a member of our AVT Review Team, has reviewed 
draft-ietf-avt-smpte-rtp-07.txt and has generated these comments. 
Thanks, Ladan.

---------------------------------------
Ladan wrote:


Hi:

I have reviewed  draft-ietf-avt-smpte-rtp-07. Overall the draft is in
good shape, most of the comment below are minor or are requests for
more clarification in the text:

cheers,
ladan



page 3: in the introduction there is mention of the SMPTE time code
in a simple counter format, but then there is no discussion of how
such a counter would be represented in RTP/RTCP - does the draft
foresee that there will never be interest in using the counter form
of the time-code with RTP/RTCP? it seems to me that discussing the
counter form in the draft would make it more complete,

page 8: this is more of a question: are the same dropped frames
applied to NSTC, PAL and also HDTV video formats?

page 8: an additional example with dropped frames would be helpful to
understanding the example

page 9:  the draft would be more complete with a breakdown of what
the full SMPTE 12M time code looks like - i.e.  in the example of
full time code SMPTETC packets in section 5.3.    Also does the SMPTE
time code use BCD or is it binary? (section 5.1 says "A full
binary ....")

page 9: section 5.3: are RTCP minimum time intervals sufficient to
send the time-codes when needed? or will the sender need to over ride
the RTCP intervals to send the time-codes at particular times?

page 11: why is only the long form of the extension associated with
an offset? would the short form not benefit from an offset (perhaps
even an 8 bit one?)  -- also an drawing of how the RTP packets would
look like in both cases would be beneficial here.

page 13: section 7 says: "The RTCP packets (or the in-band codes)
need not use the same RTP timestamp as the sender report (or
transmission time) in the same RTCP packet."

           In the case of the RTCP packets, this makes sense. However
for the in-band mode, the short form relies on the RTP timestamp of
the RTP packet (and it has no offset) so it not clear how it could be
sent "ahead of need."


page 14: " ... it is hard to see" -> "... there are no".  If, indeed,
there are no security considerations, or else they should be listed.


nits and organizational changes:
----
- make first character in section heading all caps (or not). in the
text and the Table of contents. Right now its inconsistent across the
draft:
      page 2: Requirements notation -> Requirements Notation
      page 7: Signaling (setup) information -> Signaling Setup
Information
      page 9: In-stream information -> In-stream Information

page 3: "This specification enables ..." -> "This memo specifies ..."
or "This document defines how ..."

page 5: referencing sections 5.3 and 5.4 from "The first can be ..."
and "The second ..." would make the draft easier to understand.

page 7: "time-code-second" -> "time-code second"

page 8:  in:
                      extensionattributes = frameduration "/"
framesperscecond drop
does frameduration refer to frame_duration in 1. on page 7? why is
the same syntax not used? (same thing with framespersecond)

page 10: "... defined above." -> "... defined in Section 5.1"


On Jan 8, 2007, at 11:18 PM, Tom-PT Taylor wrote:

> Hi, folks.
>
> draft-ietf-avt-smpte-rtp-07.txt is in WGLC but has so far drawn no  
> comments. Would you care to have a look at it?
>
> Thanks,
> Tom
>



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



From avt-bounces@ietf.org Thu Feb 08 16:51:04 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HFH8z-0000Zb-BY; Thu, 08 Feb 2007 16:49:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HFH8x-0000ZW-F8
	for avt@ietf.org; Thu, 08 Feb 2007 16:49:27 -0500
Received: from zcars04e.nortel.com ([47.129.242.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HFH8w-000774-5Y
	for avt@ietf.org; Thu, 08 Feb 2007 16:49:27 -0500
Received: from zcarhxs1.corp.nortel.com (zcarhxs1.corp.nortel.com
	[47.129.230.89])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	l18LfSG24966 for <avt@ietf.org>; Thu, 8 Feb 2007 16:41:28 -0500 (EST)
Received: from [47.130.19.101] ([47.130.19.101] RDNS failed) by
	zcarhxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 8 Feb 2007 16:49:21 -0500
Message-ID: <45CB9ACF.6010201@nortel.com>
Date: Thu, 08 Feb 2007 16:49:03 -0500
From: "Tom-PT Taylor" <taylor@nortel.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: avt@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Feb 2007 21:49:21.0973 (UTC)
	FILETIME=[FDF83E50:01C74BCA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Subject: [AVT] [Fwd: Re: Review requested: draft-ietf-avt-rtp-toffset-04.txt]
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Qiaobing was asked as a member of the AVT Review Team to comment on the 
toffset draft. I am assuming Qiaobing's consent to publish this to the 
list. There was some behind-the scenes discussion of these points that I 
will also forward. From now on, we will ensure a more efficient 
procedure by asking the review team to publish directly to the authors 
and the list.

Many thanks for your review, Qiaobing.

Qiaobing Xie wrote:
> Tom,
> 
> Here are my comments on the draft:
> 
> 1. I agree with the use case analysis in the draft and agree in general 
> this may be a useful extension.
> 
> 2. I would like to see a more crisp definition of the "transmission 
> timestamp" - what is it? Is it the time instance the first (or the last) 
> octet of the packet is put on the wire by the physical interface at the 
> RTP sender? Or is it the time instance the sending RTP stack passes the 
> fully assembled packet into the out-going buffer? Or, is it the time 
> instance the last media octet in the packet was assembled at the RTP 
> stack? and so on.
> 
> 3. The following statement in the draft:
> 
>    "In the RTP specification [RFC3550] it is implied that packets are
>     transmitted essentially in accordance with their RTP timestamps."
> 
> is a little misleading since RFC3550 only says:
> 
>    "The timestamp reflects the sampling instant of the first octet in
>     the RTP data packet."
> 
> I'd therefore suggest to say something like: "RFC 3550 does not specify 
> a transmission timestamp."
> 
> 4. The sentence:
> 
>    "When added to the RTP timestamp of the packet, it represents the
>     "effective" RTP transmission time of the packet, on the RTP
>     timescale."
> 
> seems to say that
> 
>    Adjusted RTP timestamp = RTP timestamp in RTP header +
>                             transmission offset
> 
> If so, it probably is helpful to spell this out clearly.
> 
> 5. If my understanding above (point 4) is correct, then I am confused 
> about the following statement:
> 
>     "The sign of the offset value depends greatly on the choice of the
>     initial mapping of RTP to NTP times.  In general, without scanning a
>     stream entirely it is not possible to ensure that this mapping would
>     keep all the offsets positive; therefore this specification allows
>     negative values."
> 
> Some more explanation would help.
> 
> 6. In section 4, it would help if more detail can be given on how to 
> "indicate the actual network jitter, excluding the source-introduced 
> jitter". An example calculation would help too.
> 
> regards,
> -Qiaobing
> 


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



From avt-bounces@ietf.org Thu Feb 08 16:51:52 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HFHAc-0001E4-Oa; Thu, 08 Feb 2007 16:51:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HFHAa-0001Cc-Ra
	for avt@ietf.org; Thu, 08 Feb 2007 16:51:08 -0500
Received: from zcars04e.nortel.com ([47.129.242.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HFHAZ-0007Nm-JX
	for avt@ietf.org; Thu, 08 Feb 2007 16:51:08 -0500
Received: from zcarhxs1.corp.nortel.com (zcarhxs1.corp.nortel.com
	[47.129.230.89])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	l18LhBG25114 for <avt@ietf.org>; Thu, 8 Feb 2007 16:43:12 -0500 (EST)
Received: from [47.130.19.101] ([47.130.19.101] RDNS failed) by
	zcarhxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 8 Feb 2007 16:51:05 -0500
Message-ID: <45CB9B37.4060902@nortel.com>
Date: Thu, 08 Feb 2007 16:50:47 -0500
From: "Tom-PT Taylor" <taylor@nortel.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: avt@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Feb 2007 21:51:05.0551 (UTC)
	FILETIME=[3BB4FDF0:01C74BCB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: [AVT] [Fwd: Re: Review requested: draft-ietf-avt-rtp-toffset-04.txt]
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Ron Frederick was also asked to review the toffset draft. Here was his 
response. Thank you, Ron.

Ron Frederick wrote:
> Hi Tom...
> 
> Tom-PT Taylor wrote:
>> draft-ietf-avt-rtp-toffset-04.txt is in WGLC but has not drawn any 
>> comments. Could you look it over?
> 
> Sorry for not getting to this sooner. I've just looked over the latest 
> version of the draft, and I'm happy with it as is. I like that we're now 
> using the 'urn' namespace for registering the extension, and my comments 
> on earlier drafts appear to be addressed. My only suggestion at this 
> point would be to possibly include an example of the calculations shown 
> in section 3 to add further clarity, but I'm happy to see the draft move 
> forward even without that.


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



From avt-bounces@ietf.org Thu Feb 08 18:40:31 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HFIrV-0003lN-3n; Thu, 08 Feb 2007 18:39:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HFIrU-0003l7-HT
	for avt@ietf.org; Thu, 08 Feb 2007 18:39:32 -0500
Received: from zrtps0kp.nortel.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HFIrS-0007yf-6r
	for avt@ietf.org; Thu, 08 Feb 2007 18:39:32 -0500
Received: from zcarhxs1.corp.nortel.com (zcarhxs1.corp.nortel.com
	[47.129.230.89])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l18NdPW16253 for <avt@ietf.org>; Thu, 8 Feb 2007 18:39:26 -0500 (EST)
Received: from [47.130.19.101] ([47.130.19.101] RDNS failed) by
	zcarhxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 8 Feb 2007 18:39:25 -0500
Message-ID: <45CBB49A.4010104@nortel.com>
Date: Thu, 08 Feb 2007 18:39:06 -0500
From: "Tom-PT Taylor" <taylor@nortel.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: avt@ietf.org
References: <4586E60E.20408@nortel.com> <4586E8D6.2070903@nortel.com>
	<4586E73C.50901@nortel.com> <p06230912c1d2511793b0@[10.0.1.33]>
	<45ACF914.8040700@nortel.com> <p062309a0c1dcda6fe8ca@[10.0.1.33]>
	<E319D2A3-2E44-4795-86D8-63465DDC300B@csperkins.org>
In-Reply-To: <E319D2A3-2E44-4795-86D8-63465DDC300B@csperkins.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Feb 2007 23:39:25.0239 (UTC)
	FILETIME=[5DD2AC70:01C74BDA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 200d029292fbb60d25b263122ced50fc
Subject: [AVT] Re: Review requested: draft-ietf-avt-rtp-toffset-04.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Here was Dave's response to Qiaobing's review. I've changed the subject 
line (above) to correlate with the reviews.

Dave Singer wrote:
--------------------


At 11:41  +0000 26/01/07, Colin Perkins wrote:
>
>Qiaobing Xie sent the following comments on the toffset draft:

Thanks, I missed this one.  Here are some proposed responses...

>
>1. I agree with the use case analysis in the draft and agree in 
>general this may be a useful extension.
>
>2. I would like to see a more crisp definition of the "transmission 
>timestamp" - what is it? Is it the time instance the first (or the 
>last) octet of the packet is put on the wire by the physical 
>interface at the RTP sender? Or is it the time instance the sending 
>RTP stack passes the fully assembled packet into the out-going 
>buffer? Or, is it the time instance the last media octet in the 
>packet was assembled at the RTP stack? and so on.

I really don't want to define it any more than the RTP specification
defines it.  This draft merely provides information about it;  its
definition is in 3550.

>
>3. The following statement in the draft:
>
>   "In the RTP specification [RFC3550] it is implied that packets are
>    transmitted essentially in accordance with their RTP timestamps."
>
>is a little misleading since RFC3550 only says:
>
>   "The timestamp reflects the sampling instant of the first octet in
>    the RTP data packet."
>
>I'd therefore suggest to say something like: "RFC 3550 does not 
>specify a transmission timestamp."

But this is missing the point.  It's true that 3550 does not have a
'transmission timestamp' that is different from the media timestamp;
but jitter calculations etc. are all based on the assumption that
they are in 1-1 relationship.

>
>4. The sentence:
>
>   "When added to the RTP timestamp of the packet, it represents the
>    "effective" RTP transmission time of the packet, on the RTP
>    timescale."
>
>seems to say that
>
>   Adjusted RTP timestamp = RTP timestamp in RTP header +
>                            transmission offset
>
>If so, it probably is helpful to spell this out clearly.

More accurately:
RelativeTransmissionTimeinRTPUnits = RTPTimestamp + transmission_offset


>
>5. If my understanding above (point 4) is correct, then I am 
>confused about the following statement:
>
>    "The sign of the offset value depends greatly on the choice of the
>    initial mapping of RTP to NTP times.  In general, without scanning a
>    stream entirely it is not possible to ensure that this mapping would
>    keep all the offsets positive; therefore this specification allows
>    negative values."
>
>Some more explanation would help.

Imagine a stream with the following timestamps and sizes in bytes

200   2kb
300   4kb
400   2kb
500   12kb
600   ...effective end of stream

This has 20KB spread over 400 time units, i.e. on average 1 kb per 20
time-units.  We traffic-smooth this, and establish that given a
transmission time of x for the first packet, we would transmit the
following packets at the given intervals later:

x + 000  2kb
x + 040  4kb
x + 120  2kb
x + 160  12kb
x + 400 ...effective end of stream

The choice of x is esssentially arbitrary:  only relative values of
timestamps matter.  Now, let's say I claim on the first packet that
it went out *at* its RTP timestamp, i.e. with an offset of 0, i.e. x
is 200.   Then the offset values are

0
-60
-80
-140

This is because in this case, I traffic-smooth this because
conceptually I think of sending the small packets 'early'.  But it is
just as valid to say x is 400, whereupon the offset values are

200
140
120
60



>
>6. In section 4, it would help if more detail can be given on how to 
>"indicate the actual network jitter, excluding the source-introduced 
>jitter". An example calculation would help too.

Simply perform the jitter calculation on the 'RTP time of
transmission' defined above...

>
>
>>>>I think we have passed the indicated date without comment, right? 
>>>>So, what happens now?
>>>>
>>>>Thanks, gang
>>
>>
>>--
>>David Singer
>>Apple Computer/QuickTime
>
>--
>Colin Perkins
>http://csperkins.org/


-- 
David Singer
Apple Computer/QuickTime


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



From avt-bounces@ietf.org Thu Feb 08 18:44:05 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HFIvE-00053j-MR; Thu, 08 Feb 2007 18:43:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HFIvD-00053c-IF
	for avt@ietf.org; Thu, 08 Feb 2007 18:43:23 -0500
Received: from zcars04e.nortel.com ([47.129.242.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HFIvC-000218-1s
	for avt@ietf.org; Thu, 08 Feb 2007 18:43:23 -0500
Received: from zcarhxs1.corp.nortel.com (zcarhxs1.corp.nortel.com
	[47.129.230.89])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	l18NZQG16281 for <avt@ietf.org>; Thu, 8 Feb 2007 18:35:26 -0500 (EST)
Received: from [47.130.19.101] ([47.130.19.101] RDNS failed) by
	zcarhxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 8 Feb 2007 18:43:19 -0500
Message-ID: <45CBB585.5070504@nortel.com>
Date: Thu, 08 Feb 2007 18:43:01 -0500
From: "Tom-PT Taylor" <taylor@nortel.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: avt@ietf.org
References: <4586E60E.20408@nortel.com> <4586E8D6.2070903@nortel.com>
	<4586E73C.50901@nortel.com> <p06230912c1d2511793b0@[10.0.1.33]>
	<45ACF914.8040700@nortel.com> <p062309a0c1dcda6fe8ca@[10.0.1.33]>
	<E319D2A3-2E44-4795-86D8-63465DDC300B@csperkins.org>
	<p062309c2c1e37868bb4e@[10.0.1.33]>
In-Reply-To: <p062309c2c1e37868bb4e@[10.0.1.33]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Feb 2007 23:43:19.0817 (UTC)
	FILETIME=[E9A46F90:01C74BDA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Subject: [AVT] Re: Review requested: draft-ietf-avt-rtp-toffset-04.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Here is Colin's response to Dave's note. Again, the subject line was 
changed to correlate with the previous messages I sent on.

I do apologize for the inefficiency of all this. I've learned a few 
lessons for the next set of documents I shepherd through Last Call.

Tom

Colin Perkins wrote:
-----------------------


On 29 Jan 2007, at 10:28, Dave Singer wrote:
> At 11:41  +0000 26/01/07, Colin Perkins wrote:
>>
>> Qiaobing Xie sent the following comments on the toffset draft:
>
> Thanks, I missed this one.  Here are some proposed responses...
>
>>
>> 1. I agree with the use case analysis in the draft and agree in  
>> general this may be a useful extension.
>>
>> 2. I would like to see a more crisp definition of the  
>> "transmission timestamp" - what is it? Is it the time instance the  
>> first (or the last) octet of the packet is put on the wire by the  
>> physical interface at the RTP sender? Or is it the time instance  
>> the sending RTP stack passes the fully assembled packet into the  
>> out-going buffer? Or, is it the time instance the last media octet  
>> in the packet was assembled at the RTP stack? and so on.
>
> I really don't want to define it any more than the RTP  
> specification defines it.  This draft merely provides information  
> about it;  its definition is in 3550.

Agreed.

>> 3. The following statement in the draft:
>>
>>   "In the RTP specification [RFC3550] it is implied that packets are
>>    transmitted essentially in accordance with their RTP timestamps."
>>
>> is a little misleading since RFC3550 only says:
>>
>>   "The timestamp reflects the sampling instant of the first octet in
>>    the RTP data packet."
>>
>> I'd therefore suggest to say something like: "RFC 3550 does not  
>> specify a transmission timestamp."
>
> But this is missing the point.  It's true that 3550 does not have a  
> 'transmission timestamp' that is different from the media  
> timestamp; but jitter calculations etc. are all based on the  
> assumption that they are in 1-1 relationship.

Kind-of... The jitter calculation breaks if the transmission time
doesn't have a one-to-one mapping onto the sampling instant, but I
don't think 3550 mandates such a mapping.

...snip the rest, which seems reasonable...

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




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



From avt-bounces@ietf.org Thu Feb 08 18:52:26 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HFJ39-0003eh-Vp; Thu, 08 Feb 2007 18:51:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HFIyb-0007Dk-TO
	for avt@ietf.org; Thu, 08 Feb 2007 18:46:53 -0500
Received: from zrtps0kp.nortel.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HFIya-0004Jw-JJ
	for avt@ietf.org; Thu, 08 Feb 2007 18:46:53 -0500
Received: from zcarhxs1.corp.nortel.com (zcarhxs1.corp.nortel.com
	[47.129.230.89])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l18NkoW16701 for <avt@ietf.org>; Thu, 8 Feb 2007 18:46:50 -0500 (EST)
Received: from [47.130.19.101] ([47.130.19.101] RDNS failed) by
	zcarhxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 8 Feb 2007 18:46:50 -0500
Message-ID: <45CBB657.4010200@nortel.com>
Date: Thu, 08 Feb 2007 18:46:31 -0500
From: "Tom-PT Taylor" <taylor@nortel.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: avt@ietf.org
References: <4586E60E.20408@nortel.com> <4586E8D6.2070903@nortel.com>
	<4586E73C.50901@nortel.com> <p06230912c1d2511793b0@[10.0.1.33]>
	<45ACF914.8040700@nortel.com> <p062309a0c1dcda6fe8ca@[10.0.1.33]>
	<E319D2A3-2E44-4795-86D8-63465DDC300B@csperkins.org>
	<p062309c2c1e37868bb4e@[10.0.1.33]>
	<4A9A2D76-48B4-4C8A-8D29-3B2497C055F1@csperkins.org>
In-Reply-To: <4A9A2D76-48B4-4C8A-8D29-3B2497C055F1@csperkins.org>
Content-Type: multipart/mixed; boundary="------------040804010703040701020409"
X-OriginalArrivalTime: 08 Feb 2007 23:46:50.0051 (UTC)
	FILETIME=[66F39930:01C74BDB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 85e99493ec37f9acef29c7843dbf2e68
X-Mailman-Approved-At: Thu, 08 Feb 2007 18:51:33 -0500
Subject: [AVT] Re: Review requested: draft-ietf-avt-rtp-toffset-04.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

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

Here is what I hope is the last word on the topic: Dave's actions.

Dave Singer wrote:
-------------------

OK, changed the first sentence:

In the RTP specification <xref target="RFC3550"/> network jitter
calculations are based on the presumption that packets are
transmitted essentially in accordance with their RTP timestamps.

and added

The RTP specification does not define a transmission timestamp, and
nor does this specification.  This specification merely provides
information on the relationship between the relative transmission
times and relative RTP timestamps.

and

The reported transmission time T1 of a packet with timestamp R1 and
an offset of O1, from the above equations, is T1 = R1+O1 (though of
course the transmission time values only have meaning when two or
more are compared).

and

The content is exactly that number of interarrival jitter
calculations, calculated using the same formula as for sender and
receiver reports, but taking into account the transmission offsets
for the streams (if any);  that is, using the values T1=R1+O1, T2
etc. as defined above, instead of R1, R2 etc..

I then re-named the symbols to be in accord with the RTP spec (i.e.
using Si for RTP timestamp, not Ri).


-- 
David Singer
Apple Computer/QuickTime

--------------040804010703040701020409
Content-Type: application/octet-stream;
	name="draft-ietf-avt-rtp-toffset-05.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="draft-ietf-avt-rtp-toffset-05.txt"

CgoKQVZUICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgRC4gU2luZ2VyCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgQXBwbGUgQ29tcHV0ZXIgSW5jLgpFeHBpcmVzOiBBdWd1
c3QgMywgMjAwNyAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgSC4gRGVz
aW5lbmkKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIFF1YWxjb21tCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgSmFudWFyeSAzMCwgMjAwNwoKCiAgICAgICAg
ICAgICAgICBUcmFuc21pc3Npb24gVGltZSBvZmZzZXRzIGluIFJUUCBzdHJlYW1zCiAgICAg
ICAgICAgICAgICAgICBkcmFmdC1pZXRmLWF2dC1ydHAtdG9mZnNldC0wNS50eHQKClN0YXR1
cyBvZiB0aGlzIE1lbW8KCiAgIEJ5IHN1Ym1pdHRpbmcgdGhpcyBJbnRlcm5ldC1EcmFmdCwg
ZWFjaCBhdXRob3IgcmVwcmVzZW50cyB0aGF0IGFueQogICBhcHBsaWNhYmxlIHBhdGVudCBv
ciBvdGhlciBJUFIgY2xhaW1zIG9mIHdoaWNoIGhlIG9yIHNoZSBpcyBhd2FyZQogICBoYXZl
IGJlZW4gb3Igd2lsbCBiZSBkaXNjbG9zZWQsIGFuZCBhbnkgb2Ygd2hpY2ggaGUgb3Igc2hl
IGJlY29tZXMKICAgYXdhcmUgd2lsbCBiZSBkaXNjbG9zZWQsIGluIGFjY29yZGFuY2Ugd2l0
aCBTZWN0aW9uIDYgb2YgQkNQIDc5LgoKICAgSW50ZXJuZXQtRHJhZnRzIGFyZSB3b3JraW5n
IGRvY3VtZW50cyBvZiB0aGUgSW50ZXJuZXQgRW5naW5lZXJpbmcKICAgVGFzayBGb3JjZSAo
SUVURiksIGl0cyBhcmVhcywgYW5kIGl0cyB3b3JraW5nIGdyb3Vwcy4gIE5vdGUgdGhhdAog
ICBvdGhlciBncm91cHMgbWF5IGFsc28gZGlzdHJpYnV0ZSB3b3JraW5nIGRvY3VtZW50cyBh
cyBJbnRlcm5ldC0KICAgRHJhZnRzLgoKICAgSW50ZXJuZXQtRHJhZnRzIGFyZSBkcmFmdCBk
b2N1bWVudHMgdmFsaWQgZm9yIGEgbWF4aW11bSBvZiBzaXggbW9udGhzCiAgIGFuZCBtYXkg
YmUgdXBkYXRlZCwgcmVwbGFjZWQsIG9yIG9ic29sZXRlZCBieSBvdGhlciBkb2N1bWVudHMg
YXQgYW55CiAgIHRpbWUuICBJdCBpcyBpbmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1E
cmFmdHMgYXMgcmVmZXJlbmNlCiAgIG1hdGVyaWFsIG9yIHRvIGNpdGUgdGhlbSBvdGhlciB0
aGFuIGFzICJ3b3JrIGluIHByb2dyZXNzLiIKCiAgIFRoZSBsaXN0IG9mIGN1cnJlbnQgSW50
ZXJuZXQtRHJhZnRzIGNhbiBiZSBhY2Nlc3NlZCBhdAogICBodHRwOi8vd3d3LmlldGYub3Jn
L2lldGYvMWlkLWFic3RyYWN0cy50eHQuCgogICBUaGUgbGlzdCBvZiBJbnRlcm5ldC1EcmFm
dCBTaGFkb3cgRGlyZWN0b3JpZXMgY2FuIGJlIGFjY2Vzc2VkIGF0CiAgIGh0dHA6Ly93d3cu
aWV0Zi5vcmcvc2hhZG93Lmh0bWwuCgogICBUaGlzIEludGVybmV0LURyYWZ0IHdpbGwgZXhw
aXJlIG9uIEF1Z3VzdCAzLCAyMDA3LgoKQ29weXJpZ2h0IE5vdGljZQoKICAgQ29weXJpZ2h0
IChDKSBUaGUgSW50ZXJuZXQgU29jaWV0eSAoMjAwNykuCgpBYnN0cmFjdAoKICAgVGhpcyBk
b2N1bWVudCBkZXNjcmliZXMgYSBtZXRob2QgdG8gaW5mb3JtIFJUUCBjbGllbnRzIHdoZW4g
UlRQCiAgIHBhY2tldHMgYXJlIHRyYW5zbWl0dGVkIGF0IGEgdGltZSBvdGhlciB0aGFuIHRo
ZWlyICdub21pbmFsJwogICB0cmFuc21pc3Npb24gdGltZS4gIEl0IGFsc28gcHJvdmlkZXMg
YSBtZWNoYW5pc20gdG8gcHJvdmlkZSBpbXByb3ZlZAogICBpbnRlci1hcnJpdmFsIGppdHRl
ciByZXBvcnRzIGZyb20gdGhlIGNsaWVudHMsIHRoYXQgdGFrZSBpbnRvIGFjY291bnQKICAg
dGhlIHJlcG9ydGVkIHRyYW5zbWlzc2lvbiB0aW1lcy4KCgoKCgpTaW5nZXIgJiBEZXNpbmVu
aSAgICAgICAgRXhwaXJlcyBBdWd1c3QgMywgMjAwNyAgICAgICAgICAgICAgICAgW1BhZ2Ug
MV0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICBSVFAgVHJhbnNtaXNzaW9uIE9mZnNldHMg
ICAgICAgICAgICBKYW51YXJ5IDIwMDcKCgpUYWJsZSBvZiBDb250ZW50cwoKICAgMS4gIElu
dHJvZHVjdGlvbiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuICAzCiAgIDIuICBSZXF1aXJlbWVudHMgbm90YXRpb24gIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgNAogICAzLiAgVHJhbnNtaXNzaW9uIG9mZnNl
dCAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDUKICAgNC4g
IEV4dGVuZGVkIEppdHRlciBSZXBvcnRzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuICA4CiAgIDUuICBTaWduYWxpbmcgKHNldHVwKSBpbmZvcm1hdGlvbiAgLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgOQogICA2LiAgU2VjdXJpdHkgQ29uc2lk
ZXJhdGlvbnMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTAKICAg
Ny4gIElBTkEgQ29uc2lkZXJhdGlvbnMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIDExCiAgIDguICBSRkMgRWRpdG9yIENvbnNpZGVyYXRpb25zICAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxMgogICA5LiAgQWNrbm93bGVkZ21l
bnRzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTMK
ICAgMTAuIE5vcm1hdGl2ZSBSZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIDEzCiAgIEF1dGhvcnMnIEFkZHJlc3NlcyAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxNAogICBJbnRlbGxlY3R1YWwg
UHJvcGVydHkgYW5kIENvcHlyaWdodCBTdGF0ZW1lbnRzIC4gLiAuIC4gLiAuIC4gLiAuIC4g
MTUKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKClNpbmdlciAmIERlc2lu
ZW5pICAgICAgICBFeHBpcmVzIEF1Z3VzdCAzLCAyMDA3ICAgICAgICAgICAgICAgICBbUGFn
ZSAyXQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgIFJUUCBUcmFuc21pc3Npb24gT2Zmc2V0
cyAgICAgICAgICAgIEphbnVhcnkgMjAwNwoKCjEuICBJbnRyb2R1Y3Rpb24KCiAgIEluIHRo
ZSBSVFAgc3BlY2lmaWNhdGlvbiBbUkZDMzU1MF0gbmV0d29yayBqaXR0ZXIgY2FsY3VsYXRp
b25zIGFyZQogICBiYXNlZCBvbiB0aGUgcHJlc3VtcHRpb24gdGhhdCBwYWNrZXRzIGFyZSB0
cmFuc21pdHRlZCBlc3NlbnRpYWxseSBpbgogICBhY2NvcmRhbmNlIHdpdGggdGhlaXIgUlRQ
IHRpbWVzdGFtcHMuICBUaGlzIG11c3QgYmUgdHJ1ZSwgb2YgY291cnNlLAogICBvbiBhdmVy
YWdlIG92ZXIgbG9uZ2VyIHRpbWUgaW50ZXJ2YWxzLCBhcyB0aGUgY2xpZW50IGlzIHBsYXlp
bmcgdGhlCiAgIHBhY2tldHMgb3V0IGFjY29yZGluZyB0byB0aG9zZSB0aW1lc3RhbXBzLiAg
SG93ZXZlciwgZm9yIGluZGl2aWR1YWwKICAgcGFja2V0cywgdGhpcyBtYXkgdW5kZXIgc29t
ZSBjaXJjdW1zdGFuY2VzIG5vdCBiZSB0cnVlOgoKICAgbyAgV2hlbiB0aGUgZGF0YSByYXRl
IG9mIHRoZSBzdHJlYW0gaXMgYnVyc3R5LCBzdWNoIGFzIHdpdGggdmlkZW8KICAgICAgd2hl
cmUgSS1mcmFtZXMgbWF5IGJlIHNpZ25pZmljYW50bHkgbGFyZ2VyIHRoYW4gUCBvciBCIGZy
YW1lcywKICAgICAgdHJhZmZpYyBzbW9vdGhpbmcgbWF5IG5lZWQgdG8gYmUgYXBwbGllZCB0
byBtYWludGFpbiBhbgogICAgICBhcHByb3ByaWF0ZSBkYXRhIHJhdGUuCgogICBvICBJbiB2
aWRlbyB3aGljaCBoYXMgZm9yd2FyZCBkZWNvZGUgZGVwZW5kZW5jaWVzLCBmcmFtZXMgbWF5
IG5lZWQgdG8KICAgICAgYmUgdHJhbnNtaXR0ZWQgaW4gZGVjb2Rpbmcgb3JkZXIgKHRoZSBz
ZXF1ZW5jZSBudW1iZXIgb3JkZXIpIGJ1dAogICAgICB3aXRoLCBvZiBjb3Vyc2UsIHByZXNl
bnRhdGlvbiB0aW1lc3RhbXBzLiAgVW5kZXIgdGhlc2UKICAgICAgY2lyY3Vtc3RhbmNlcyB0
aGUgdHJhbnNtaXNzaW9uIHRpbWUgb2YgYSBmcmFtZSBzZW50IGVhcmx5IGluCiAgICAgIHNl
cXVlbmNlIGRvZXMgbm90IGNvcnJlc3BvbmQgdG8gaXRzIFJUUCB0aW1lc3RhbXAuCgogICBv
ICBXaGVuIHJlLXRyYW5zbWlzc2lvbnMgYXJlIHNlbnQsIHRoZSByZS10cmFuc21pdHRlZCBw
YWNrZXQgY2xlYXJseQogICAgICBoYXMgYSBkaWZmZXJlbnQgYWN0dWFsIHRyYW5zbWlzc2lv
biB0aW1lIGZyb20gdGhlIG9yaWdpbmFsLCBldmVuCiAgICAgIHRob3VnaCB0aGV5IHNoYXJl
IHRoZSBzYW1lIHRpbWVzdGFtcC4KCiAgIFVuZGVyIHNvbWUgY2lyY3Vtc3RhbmNlcyBpdCBj
YW4gaGVscCB0aGUgcmVjZWl2ZXIsIG9yIGludGVybWVkaWF0ZQogICBuZXR3b3JrIGVsZW1l
bnRzLCB0byBrbm93IHRoZSBhY3R1YWwgdHJhbnNtaXNzaW9uIHRpbWUgb2YgdGhlIHBhY2tl
dC4KICAgVGhpcyBSVFAgaGVhZGVyIGV4dGVuc2lvbiBlbGVtZW50IGFsbG93cyB0aGUgY29t
bXVuaWNhdGlvbiBvZiB0aGlzCiAgIGluZm9ybWF0aW9uLgoKICAgVGhlIFJUUCBzcGVjaWZp
Y2F0aW9uIGRvZXMgbm90IGRlZmluZSBhIHRyYW5zbWlzc2lvbiB0aW1lc3RhbXAsIGFuZAog
ICBub3IgZG9lcyB0aGlzIHNwZWNpZmljYXRpb24uICBUaGlzIHNwZWNpZmljYXRpb24gbWVy
ZWx5IHByb3ZpZGVzCiAgIGluZm9ybWF0aW9uIG9uIHRoZSByZWxhdGlvbnNoaXAgYmV0d2Vl
biB0aGUgcmVsYXRpdmUgdHJhbnNtaXNzaW9uCiAgIHRpbWVzIGFuZCByZWxhdGl2ZSBSVFAg
dGltZXN0YW1wcy4KCiAgIEl0IGNhbiBhbHNvIGJlIG9mIHVzZSB0byByZXBvcnQgdGhlIGlu
dGVyLWFycml2YWwgaml0dGVyIGNhdXNlZCBieQogICB0aGUgbmV0d29yaywgZXhjbHVkaW5n
IHRoYXQgaW50cm9kdWNlZCBieSB0aGUgc291cmNlLiAgQSBuZXcgUlRDUAogICBwYWNrZXQg
aXMgZGVmaW5lZCB0byBlbmFibGUgdGhpcyByZXBvcnRpbmcuCgoKCgoKCgoKCgoKCgoKU2lu
Z2VyICYgRGVzaW5lbmkgICAgICAgIEV4cGlyZXMgQXVndXN0IDMsIDIwMDcgICAgICAgICAg
ICAgICAgIFtQYWdlIDNdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgUlRQIFRyYW5zbWlz
c2lvbiBPZmZzZXRzICAgICAgICAgICAgSmFudWFyeSAyMDA3CgoKMi4gIFJlcXVpcmVtZW50
cyBub3RhdGlvbgoKICAgVGhlIGtleSB3b3JkcyAiTVVTVCIsICJNVVNUIE5PVCIsICJSRVFV
SVJFRCIsICJTSEFMTCIsICJTSEFMTCBOT1QiLAogICAiU0hPVUxEIiwgIlNIT1VMRCBOT1Qi
LCAiUkVDT01NRU5ERUQiLCAiTUFZIiwgYW5kICJPUFRJT05BTCIgaW4gdGhpcwogICBkb2N1
bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgYXMgZGVzY3JpYmVkIGluIFtSRkMyMTE5XS4K
CgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKClNpbmdlciAm
IERlc2luZW5pICAgICAgICBFeHBpcmVzIEF1Z3VzdCAzLCAyMDA3ICAgICAgICAgICAgICAg
ICBbUGFnZSA0XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgIFJUUCBUcmFuc21pc3Npb24g
T2Zmc2V0cyAgICAgICAgICAgIEphbnVhcnkgMjAwNwoKCjMuICBUcmFuc21pc3Npb24gb2Zm
c2V0CgogICBDbGFzc2ljYWxseSBhIHBhaXIgb2YgUlRQIHBhY2tldHMgd2l0aCB0aW1lc3Rh
bXBzIFMyIGFuZCBTMSBhcmUKICAgdHJhbnNtaXR0ZWQgd2l0aCBhIHRpbWUgaW50ZXJ2YWwg
YmV0d2VlbiB0aGVtIG9mIChTMiAtIFMxKS4gIFRoaXMKICAgc3BlY2lmaWNhdGlvbiBwZXJt
aXRzIHNlbmRpbmcgYW4gb2Zmc2V0IHZhbHVlIE8gaW4gZWFjaCBwYWNrZXQsIE8xCiAgIGFu
ZCBPMi4gIE9uZSBjaGFyYWN0ZXJpc3RpYyBvZiB0aGVzZSBvZmZzZXRzIGlzIHRoYXQgdGhl
IG9yaWdpbmFsCiAgIHRyYW5zbWlzc2lvbiBpbnRlcnZhbCBjYW4gYmUgZGVkdWNlZCB0byBi
ZSAoUzIgKyBPMikgLSAoUzEgKyBPMSkuCgogICBNb3JlIHByZWNpc2VseSwgdGhlIG9mZnNl
dCBpcyBkZWZpbmVkIGFzIGZvbGxvd3MgKHdpdGggdGhlIGZ1bmN0aW9uCiAgIFJ0b04gY29u
dmVydGluZyBmcm9tIFJUUCB0byBOVFAgdGltZXMsIGFuZCBOdG9SIGRvaW5nIHRoZSByZXZl
cnNlKToKCiAgIG8gIFRha2UgYW4gUlRQIHN0cmVhbSB0aGF0IGhhcyBhIHJlY2VudCBSVENQ
IHNlbmRlciByZXBvcnQgcmVsYXRpbmcKICAgICAgUlRQIHRpbWVzdGFtcCBTMCB0byBOVFAg
dGltZXN0YW1wIE4wOwoKICAgbyAgY29uc2lkZXIgYSBwYWNrZXQgc2VudCBhZnRlciB0aGF0
IHdpdGggUlRQIHRpbWVzdGFtcCBTMS4KICAgICAgTm9taW5hbGx5IHRoaXMgaXMgc2VudCBh
dCBOMSA9IChOMCArIFJ0b04oUzEgLSBTMCkpOwoKICAgbyAgSWYgaXQgd2FzIGFjdHVhbGx5
IHNlbnQgYXQgYSBkaWZmZXJlbnQgdGltZSwgTmEsIHRoZW4gdGhlIG9mZnNldAogICAgICB2
YWx1ZSBPMSBpcyBPMSA9IE50b1IoTmEgLSBOMSkuCgogICBUaGUgdHJhbnNtaXNzaW9uIHRp
bWUgaXMgc2lnbmFsbGVkIHRvIHRoZSByZWNlaXZlciBpbi1iYW5kIHVzaW5nIFRoZQogICBJ
RVRGIEdlbmVyaWMgUlRQIGhlYWRlciBleHRlbnNpb24gW2hkcmV4dF0uICBUaGUgcGF5bG9h
ZCBvZiB0aGlzCiAgIGV4dGVuc2lvbiAodGhlIHRyYW5zbWl0dGVkIHZhbHVlKSBpcyBhIDI0
LWJpdCBzaWduZWQgaW50ZWdlci4gIFdoZW4KICAgYWRkZWQgdG8gdGhlIFJUUCB0aW1lc3Rh
bXAgb2YgdGhlIHBhY2tldCwgaXQgcmVwcmVzZW50cyB0aGUKICAgImVmZmVjdGl2ZSIgUlRQ
IHRyYW5zbWlzc2lvbiB0aW1lIG9mIHRoZSBwYWNrZXQsIG9uIHRoZSBSVFAKICAgdGltZXNj
YWxlLiAgVGhlIHJlcG9ydGVkIHRyYW5zbWlzc2lvbiB0aW1lIFQxIG9mIGEgcGFja2V0IHdp
dGgKICAgdGltZXN0YW1wIFMxIGFuZCBhbiBvZmZzZXQgb2YgTzEsIGZyb20gdGhlIGFib3Zl
IGVxdWF0aW9ucywgaXMgVDEgPQogICBTMStPMSAodGhvdWdoIG9mIGNvdXJzZSB0aGUgdHJh
bnNtaXNzaW9uIHRpbWUgdmFsdWVzIG9ubHkgaGF2ZQogICBtZWFuaW5nIHdoZW4gdHdvIG9y
IG1vcmUgYXJlIGNvbXBhcmVkKS4KCiAgIFRoZSBmb3JtIG9mIHRoZSB0cmFuc21pc3Npb24g
b2Zmc2V0IGV4dGVuc2lvbiBibG9jayBpcyBhcyBmb2xsb3dzOgoKICAgICAgIDAgICAgICAg
ICAgICAgICAgICAgMSAgICAgICAgICAgICAgICAgICAyICAgICAgICAgICAgICAgICAgIDMK
ICAgICAgIDAgMSAyIDMgNCA1IDYgNyA4IDkgMCAxIDIgMyA0IDUgNiA3IDggOSAwIDEgMiAz
IDQgNSA2IDcgOCA5IDAgMQogICAgICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKwogICAgICB8ICBJRCAgIHwgbGVu
PTIgfCAgICAgICAgICAgICAgdHJhbnNtaXNzaW9uIG9mZnNldCAgICAgICAgICAgICAgfAog
ICAgICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKwoKCiAgIFRoZSBsZW5ndGggZmllbGQgdGFrZXMgdGhlIHZhbHVl
IDIgdG8gaW5kaWNhdGUgdGhhdCAzIGJ5dGVzIGZvbGxvdy4KCiAgIFRoZSBzaWduIG9mIHRo
ZSBvZmZzZXQgdmFsdWUgZGVwZW5kcyBncmVhdGx5IG9uIHRoZSBjaG9pY2Ugb2YgdGhlCiAg
IGluaXRpYWwgbWFwcGluZyBvZiBSVFAgdG8gTlRQIHRpbWVzLiAgSW4gZ2VuZXJhbCwgd2l0
aG91dCBzY2FubmluZyBhCiAgIHN0cmVhbSBlbnRpcmVseSBpdCBpcyBub3QgcG9zc2libGUg
dG8gZW5zdXJlIHRoYXQgdGhpcyBtYXBwaW5nIHdvdWxkCiAgIGtlZXAgYWxsIHRoZSBvZmZz
ZXRzIHBvc2l0aXZlOyB0aGVyZWZvcmUgdGhpcyBzcGVjaWZpY2F0aW9uIGFsbG93cwogICBu
ZWdhdGl2ZSB2YWx1ZXMuCgogICBJbWFnaW5lIGEgc3RyZWFtIHdpdGggdGhlIGZvbGxvd2lu
ZyB0aW1lc3RhbXBzIGFuZCBzaXplcyBpbiBieXRlczoKCgoKU2luZ2VyICYgRGVzaW5lbmkg
ICAgICAgIEV4cGlyZXMgQXVndXN0IDMsIDIwMDcgICAgICAgICAgICAgICAgIFtQYWdlIDVd
CgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgUlRQIFRyYW5zbWlzc2lvbiBPZmZzZXRzICAg
ICAgICAgICAgSmFudWFyeSAyMDA3CgoKICAgMjAwICAgMmtiCiAgIDMwMCAgIDRrYgogICA0
MDAgICAya2IKICAgNTAwICAgMTJrYgogICA2MDAgICAuLi5lZmZlY3RpdmUgZW5kIG9mIHN0
cmVhbQoKICAgVGhpcyBoYXMgMjBLQiBzcHJlYWQgb3ZlciA0MDAgdGltZSB1bml0cywgaS5l
LiBvbiBhdmVyYWdlIDEga2IgcGVyIDIwCiAgIHRpbWUtdW5pdHMuICBXZSB0cmFmZmljLXNt
b290aCB0aGlzLCBhbmQgZXN0YWJsaXNoIHRoYXQgZ2l2ZW4gYQogICB0cmFuc21pc3Npb24g
dGltZSBvZiB4IGZvciB0aGUgZmlyc3QgcGFja2V0LCB3ZSB3b3VsZCB0cmFuc21pdCB0aGUK
ICAgZm9sbG93aW5nIHBhY2tldHMgYXQgdGhlIGdpdmVuIGludGVydmFscyBsYXRlcjoKCiAg
IHggKyAwMDAgIDJrYgogICB4ICsgMDQwICA0a2IKICAgeCArIDEyMCAgMmtiCiAgIHggKyAx
NjAgIDEya2IKICAgeCArIDQwMCAuLi5lZmZlY3RpdmUgZW5kIG9mIHN0cmVhbQoKICAgVGhl
IGNob2ljZSBvZiB4IGlzIGVzc3NlbnRpYWxseSBhcmJpdHJhcnk6IG9ubHkgcmVsYXRpdmUg
dmFsdWVzIG9mCiAgIHRpbWVzdGFtcHMgbWF0dGVyLiAgTm93LCBsZXQncyBzYXkgSSBjbGFp
bSBvbiB0aGUgZmlyc3QgcGFja2V0IHRoYXQKICAgaXQgd2VudCBvdXQgKmF0KiBpdHMgUlRQ
IHRpbWVzdGFtcCwgaS5lLiB3aXRoIGFuIG9mZnNldCBvZiAwLCBpLmUuIHgKICAgaXMgMjAw
LiAgVGhlbiB0aGUgb2Zmc2V0IHZhbHVlcyBhcmUKCiAgIDAKICAgLTYwCiAgIC04MAogICAt
MTQwCgogICBUaGlzIGlzIGJlY2F1c2UgaW4gdGhpcyBjYXNlLCBJIHRyYWZmaWMtc21vb3Ro
IHRoaXMgYmVjYXVzZQogICBjb25jZXB0dWFsbHkgSSB0aGluayBvZiBzZW5kaW5nIHRoZSBz
bWFsbCBwYWNrZXRzICdlYXJseScuICBCdXQgc2luY2UKICAgb25seSB0aGUgcmVsYXRpdmUg
dmFsdWVzIGFyZSBzaWduaWZpY2FudCwgaXQgaXMganVzdCBhcyB2YWxpZCB0byBzYXkKICAg
eCBpcyA0MDAsIHdoZXJldXBvbiB0aGUgb2Zmc2V0IHZhbHVlcyBhcmUKCiAgIDIwMAogICAx
NDAKICAgMTIwCiAgIDYwCgogICBJbiBhIHN0cmVhbSB3aGVyZSB0aGlzIGV4dGVuc2lvbiBp
cyBub3QgaW4gZWZmZWN0IChpLmUuIG5vdCBkZWNsYXJlZAogICBvciBuZWdvdGlhdGVkKSwg
dGhlIGFjdHVhbCB0cmFuc21pc3Npb24gb2Zmc2V0IGlzIHRoZXJlZm9yZSB1bmtub3duLgog
ICBIb3dldmVyLCB3aGVuIHRoZSBleHRlbnNpb24gaXMgaW4gZWZmZWN0IGZvciB0aGUgc3Ry
ZWFtLCBpdCBtYXkgYmUKICAgb21pdHRlZCBpbiB0aG9zZSBwYWNrZXRzIGZvciB3aGljaCB0
aGUgb2Zmc2V0IGlzIDAgKHplcm8pOyB0aGF0IGlzLAogICBwYWNrZXRzIHNlbnQgYXQgdGhl
aXIgbm9taW5hbCB0aW1lIGRvIG5vdCBuZWVkIHRoaXMgZXh0ZW5zaW9uCiAgIHRhZ2dpbmcu
ICBUaGVyZWZvcmUgdGhlIGltcGxpZWQgdHJhbnNtaXNzaW9uIHRpbWUgb2YgYW4gdW4tdGFn
Z2VkIFJUUAogICBwYWNrZXQgZGVwZW5kcyBvbiB3aGV0aGVyIHRoZSBleHRlbnNpb24gaXMg
aW4gZWZmZWN0IGZvciB0aGUgc3RyZWFtCiAgIChhbmQgdGhlcmVmb3JlIHRoZSB0cmFuc21p
c3Npb24gb2Zmc2V0IGlzIDApIG9yIG5vdCAod2hlcmV1cG9uIHRoZQogICB0cmFuc21pc3Np
b24gb2Zmc2V0IGlzIHVua25vd24pLgoKICAgVGhlIGppdHRlciBjYWxjdWxhdGlvbnMgcGVy
Zm9ybWVkIGJ5IGFuIFJUUCBjbGllbnQgTVVTVCBOT1QgdXNlIHRoZXNlCgoKClNpbmdlciAm
IERlc2luZW5pICAgICAgICBFeHBpcmVzIEF1Z3VzdCAzLCAyMDA3ICAgICAgICAgICAgICAg
ICBbUGFnZSA2XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgIFJUUCBUcmFuc21pc3Npb24g
T2Zmc2V0cyAgICAgICAgICAgIEphbnVhcnkgMjAwNwoKCiAgIHRyYW5zbWlzc2lvbiBvZmZz
ZXRzLiAgSW4gZ2VuZXJhbCwgdGhlIHNlbmRlciAob3IgaW50ZXJtZWRpYXRlCiAgIG5ldHdv
cmsgZWxlbWVudHMgZG9pbmcgUlRQIGFuYWx5c2lzKSBjYW5ub3QgYWx3YXlzIGtub3cgd2hl
dGhlciB0aGUKICAgb2Zmc2V0cyBoYXZlIGJlZW4gdGFrZW4gaW50byBhY2NvdW50IG9yIG5v
dCwgYW5kIGZvciBjb25zaXN0ZW5jeQogICB0aGVyZWZvcmUsIHRoZSBqaXR0ZXIgY2FsY3Vs
YXRpb24gc2hvdWxkIGNvbnRpbnVlIHRvIG9wZXJhdGUgb24gdGhlCiAgICdyYXcnIHJlY2Vw
dGlvbiB0aW1lcy4gIEhvd2V2ZXIsIHNlZSB0aGUgc2VjdGlvbiBvbiBleHRlbmRlZCBqaXR0
ZXIKICAgcmVwb3J0cywgYmVsb3cuCgogICBUaGVyZSBhcmUgbm8gZXh0ZW5zaW9uIGF0dHJp
YnV0ZXMgZGVmaW5lZCBmb3IgdGhpcyBleHRlbnNpb24uCgogICBJdCBpcyBzdHJ1Y3R1cmFs
bHkgcG9zc2libGUgdG8gaGF2ZSBtb3JlIHRoYW4gb25lIGV4dGVuc2lvbiBvZiB0aGUKICAg
c2FtZSB0eXBlIGluIGEgcGFja2V0LiAgSG93ZXZlciwgdGhpcyBleHRlbnNpb24gaXMgb25s
eSBkZWZpbmVkIGZvcgogICB0aGUgc291cmNlIHRvIHJlcG9ydCwgYW5kIGludGVybWVkaWF0
ZSBuZXR3b3JrIG5vZGVzIHRoYXQgYXJlIG5vdCB0aGUKICAgc291cmNlIG9mIHRoZSBSVFAg
c2Vzc2lvbiBNVVNUIE5PVCBhZGQgdGhpcyBleHRlbnNpb24gKHdoZXRoZXIgb3Igbm90CiAg
IGl0IHdhcyBwcmV2aW91c2x5IHByZXNlbnQpIGFuZCBNVVNUIE5PVCBhbHRlciB0aGUgZXhp
c3RpbmcKICAgdHJhbnNtaXNzaW9uIG9mZnNldCB2YWx1ZSBpbiBhIHBhY2tldCwgaWYgdGhl
IGV4dGVuc2lvbiBpcyBhbHJlYWR5CiAgIHByZXNlbnQuCgogICAoT2YgY291cnNlLCBpdCBp
cyBjbGVhciB0aGF0IG5ldHdvcmsgZWxlbWVudHMgdGhhdCB0ZXJtaW5hdGUgYW4gUlRQCiAg
IGZsb3csIGFuZCBhcmUgdGhlIHNvdXJjZSBmb3IgYSBuZXcgUlRQIGZsb3csIGNhbiBhZGQg
YSB0cmFuc21pc3Npb24KICAgb2Zmc2V0IGV4dGVuc2lvbiBoZWFkZXIgdG8gdGhlIFJUUCBw
YWNrZXRzIG9mIHRoZSBuZXcgZmxvdywgaWYKICAgZGVzaXJlZC4pCgoKCgoKCgoKCgoKCgoK
CgoKCgoKCgoKCgoKCgoKClNpbmdlciAmIERlc2luZW5pICAgICAgICBFeHBpcmVzIEF1Z3Vz
dCAzLCAyMDA3ICAgICAgICAgICAgICAgICBbUGFnZSA3XQoMCkludGVybmV0LURyYWZ0ICAg
ICAgICAgIFJUUCBUcmFuc21pc3Npb24gT2Zmc2V0cyAgICAgICAgICAgIEphbnVhcnkgMjAw
NwoKCjQuICBFeHRlbmRlZCBKaXR0ZXIgUmVwb3J0cwoKICAgVGhlIGludGVyIGFycml2YWwg
aml0dGVyIGNvbXB1dGVkIGFzIGRlZmluZWQgaW4gU2VjIDYuNC4xIG9mIFJGQzM1NTAKICAg
cHJvdmlkZXMgaW50ZXItYXJyaXZhbCBqaXR0ZXIgcmVwb3J0cyB3aGljaCBpbmNsdWRlIGFu
eSBzb3VyY2UtCiAgIGludHJvZHVjZWQgaml0dGVyICh0cmFuc21pc3Npb24gdGltZSBvZmZz
ZXRzKS4gIElmIGl0IGlzIGRlc2lyZWQgdG8KICAgaW5kaWNhdGUgdGhlIGFjdHVhbCBuZXR3
b3JrIGppdHRlciwgZXhjbHVkaW5nIHRoZSBzb3VyY2UtaW50cm9kdWNlZAogICBqaXR0ZXIs
IHRoZSBuZXcgUlRDUCBwYWNrZXQgdHlwZSBkZWZpbmVkIGhlcmUgbWF5IGJlIHVzZWQuICBU
aGlzIG5ldwogICBSVENQIHBhY2tldCBtYXkgYmUgcGxhY2VkIGFmdGVyIHRoZSByZWNlcHRp
b24gcmVwb3J0IGluc2lkZSBhCiAgIGNvbXBvdW5kIFJUQ1AgcGFja2V0LgoKICAgSXQgaGFz
IHRoZSBmb2xsb3dpbmcgZm9ybToKCiAgICAgICAgMCAgICAgICAgICAgICAgICAgICAxICAg
ICAgICAgICAgICAgICAgIDIgICAgICAgICAgICAgICAgICAgMwogICAgICAgIDAgMSAyIDMg
NCA1IDYgNyA4IDkgMCAxIDIgMyA0IDUgNiA3IDggOSAwIDEgMiAzIDQgNSA2IDcgOCA5IDAg
MQogICAgICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSsKICAgaGRyIHxWPTJ8UHwgICAgUkMgICB8ICAgUFQ9SUo9
MTk1ICAgfCAgICAgICAgICAgICBsZW5ndGggICAgICAgICAgICB8CiAgICAgICArLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKwogICAgICAgfCAgICAgICAgICAgICAgICAgICAgICBpbnRlcmFycml2YWwgaml0dGVy
ICAgICAgICAgICAgICAgICAgICAgIHwKICAgICAgICstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rCiAgICAgICAuICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgLgogICAgICAgLiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIC4KICAgICAgIC4gICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAuCiAgICAgICB8
ICAgICAgICAgICAgICAgICAgICAgIGludGVyYXJyaXZhbCBqaXR0ZXIgICAgICAgICAgICAg
ICAgICAgICAgfAogICAgICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsKCiAgIFRoaXMgUlRDUCBwYWNrZXQgbXVz
dCBiZSBwbGFjZWQgYWZ0ZXIgYSByZWNlaXZlciByZXBvcnQgKGluc2lkZSBhCiAgIGNvbXBv
dW5kIFJUQ1AgcGFja2V0KSwgYW5kIE1VU1QgaGF2ZSB0aGUgc2FtZSB2YWx1ZSBhcyB0aGUg
cmVjZWl2ZXIKICAgcmVwb3J0IGZvciBSQy4gIFRoZSBjb250ZW50IGlzIGV4YWN0bHkgdGhh
dCBudW1iZXIgb2YgaW50ZXJhcnJpdmFsCiAgIGppdHRlciBjYWxjdWxhdGlvbnMsIGNhbGN1
bGF0ZWQgdXNpbmcgdGhlIHNhbWUgZm9ybXVsYSBhcyBmb3Igc2VuZGVyCiAgIGFuZCByZWNl
aXZlciByZXBvcnRzLCBidXQgdGFraW5nIGludG8gYWNjb3VudCB0aGUgdHJhbnNtaXNzaW9u
CiAgIG9mZnNldHMgZm9yIHRoZSBzdHJlYW1zIChpZiBhbnkpOyB0aGF0IGlzLCB1c2luZyB0
aGUgdmFsdWVzIFQxPVMxK08xLAogICBUMiBldGMuIGFzIGRlZmluZWQgYWJvdmUsIGluc3Rl
YWQgb2YgUzEsIFMyIGV0Yy4uICAoSWYgbm8KICAgdHJhbnNtaXNzaW9uIG9mZnNldCBpbmZv
cm1hdGlvbiBpcyBnaXZlbiBmb3IgYSBzdHJlYW0sIHRoZW4gdGhlIHZhbHVlCiAgIG9mIGlu
dGVyYXJyaXZhbCBqaXR0ZXIgaW4gdGhpcyBwYWNrZXQgYW5kIGluIHRoZSByZWNlaXZlciBy
ZXBvcnQgd2lsbAogICBiZSBpZGVudGljYWwpLgoKICAgUHJlY2lzZWx5LCB0aGUgcmVwbGFj
ZW1lbnQgZXF1YXRpb24gZm9yIHRoZSBlcXVhdGlvbiBpbiB0aGUgUlRQCiAgIHNwZWNpZmlj
YXRpb24gaXMsIHdoZXJlIFJpIGlzIHRoZSBhcnJpdmFsIHRpbWU6CgogICBEKGksaikgPSAo
UmogLSBSaSkgLSAoKFNqICsgT2opIC0gKFNpICsgT2kpKQogICAgICAgICAgPSAoUmogLSAo
U2ogKyBPaikpIC0gKFJpIC0gKFNpICsgT2kpKQoKCgoKCgoKCgoKU2luZ2VyICYgRGVzaW5l
bmkgICAgICAgIEV4cGlyZXMgQXVndXN0IDMsIDIwMDcgICAgICAgICAgICAgICAgIFtQYWdl
IDhdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgUlRQIFRyYW5zbWlzc2lvbiBPZmZzZXRz
ICAgICAgICAgICAgSmFudWFyeSAyMDA3CgoKNS4gIFNpZ25hbGluZyAoc2V0dXApIGluZm9y
bWF0aW9uCgogICBUaGUgVVJJIGZvciBkZWNsYXJpbmcgdGhpcyBoZWFkZXIgZXh0ZW5zaW9u
IGluIGFuIGV4dG1hcCBhdHRyaWJ1dGUgaXMKICAgInVybjppZXRmOnBhcmFtczpydHAtaGRy
ZXh0OnRvZmZzZXQiLiAgVGhlcmUgaXMgbm8gYWRkaXRpb25hbCBzZXR1cAogICBpbmZvcm1h
dGlvbiBuZWVkZWQgZm9yIHRoaXMgZXh0ZW5zaW9uIChubyBleHRlbnNpb25hdHRyaWJ1dGVz
KS4KCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKClNpbmdl
ciAmIERlc2luZW5pICAgICAgICBFeHBpcmVzIEF1Z3VzdCAzLCAyMDA3ICAgICAgICAgICAg
ICAgICBbUGFnZSA5XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgIFJUUCBUcmFuc21pc3Np
b24gT2Zmc2V0cyAgICAgICAgICAgIEphbnVhcnkgMjAwNwoKCjYuICBTZWN1cml0eSBDb25z
aWRlcmF0aW9ucwoKICAgVGhlIGdpdmVuIHRyYW5zbWlzc2lvbiBvZmZzZXRzIGFyZSBvbmx5
IGluZm9ybWF0aXZlIGFuZCBpdCBpcyBoYXJkIHRvCiAgIHNlZSBzZWN1cml0eSBjb25zaWRl
cmF0aW9ucyBmcm9tIGFzc29jaWF0aW5nIHRoZW0gd2l0aCBtZWRpYSBzdHJlYW1zLgoKCgoK
CgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKClNpbmdlciAmIERl
c2luZW5pICAgICAgICBFeHBpcmVzIEF1Z3VzdCAzLCAyMDA3ICAgICAgICAgICAgICAgIFtQ
YWdlIDEwXQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgIFJUUCBUcmFuc21pc3Npb24gT2Zm
c2V0cyAgICAgICAgICAgIEphbnVhcnkgMjAwNwoKCjcuICBJQU5BIENvbnNpZGVyYXRpb25z
CgogICBUaGUgUlRDUCBwYWNrZXQgdHlwZSB1c2VkIGZvciB0aGUgYWRqdXN0ZWQgaW50ZXJh
cnJpdmFsIGppdHRlciBuZWVkcwogICB0byBiZSByZWdpc3RlcmVkLCBpbiBhY2NvcmRhbmNl
IHdpdGggc2VjdGlvbiAxNSBvZiBbUkZDMzU1MF0uICBUaGUKICAgYWJicmV2aWF0aW9uIGlz
ICJJSiIsIHRoZSBmdWxsIG5hbWUgaXMgIkV4dGVuZGVkIGludGVyLWFycml2YWwgaml0dGVy
CiAgIHJlcG9ydCIsIHRoZSBzdWdnZXN0ZWQgdmFsdWUgaXMgMTk1LCBhbmQgdGhlIHNwZWNp
ZmljYXRpb24gaXMgdGhpcwogICBkb2N1bWVudC4KCiAgIFRoZSBuYW1lIHRvZmZzZXQgbmVl
ZHMgdG8gYmUgcmVnaXN0ZXJlZCBpbnRvIHRoZSBydHAtaGRyZXh0IHNlY3Rpb24KICAgb2Yg
dGhlIHVybjppZXRmOiBuYW1lc3BhY2UsIHJlZmVycmluZyB0byBSRkN4eHh4LgoKCgoKCgoK
CgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKClNpbmdlciAmIERlc2luZW5pICAg
ICAgICBFeHBpcmVzIEF1Z3VzdCAzLCAyMDA3ICAgICAgICAgICAgICAgIFtQYWdlIDExXQoM
CkludGVybmV0LURyYWZ0ICAgICAgICAgIFJUUCBUcmFuc21pc3Npb24gT2Zmc2V0cyAgICAg
ICAgICAgIEphbnVhcnkgMjAwNwoKCjguICBSRkMgRWRpdG9yIENvbnNpZGVyYXRpb25zCgog
ICBUaGUgcmVmZXJlbmNlIHRvIGFuIEludGVybmV0IERyYWZ0IG5lZWRzIHRvIGJlIHVwZGF0
ZWQgdG8gdGhlIFJGQwogICB3aGVuIGl0IGlzIHB1Ymxpc2hlZCAod2hpY2ggc2hvdWxkIGJl
IGJlZm9yZSB0aGlzIGRyYWZ0KS4KCiAgIFJGQ3h4eHggaW4gdGhlIElBTkEgY29uc2lkZXJh
dGlvbnMgbmVlZHMgdG8gYmUgdXBkYXRlZCB3aXRoIHRoZQogICBudW1iZXIgb2YgdGhpcyBS
RkMuCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKU2luZ2Vy
ICYgRGVzaW5lbmkgICAgICAgIEV4cGlyZXMgQXVndXN0IDMsIDIwMDcgICAgICAgICAgICAg
ICAgW1BhZ2UgMTJdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgUlRQIFRyYW5zbWlzc2lv
biBPZmZzZXRzICAgICAgICAgICAgSmFudWFyeSAyMDA3CgoKOS4gIEFja25vd2xlZGdtZW50
cwoKICAgUm9uIEZyZWRlcmljaywgQ29saW4gUGVya2lucywgYW5kIFN0ZXZlIENhc25lciBh
bGwgY29udHJpYnV0ZWQKICAgc3Vic3RhbnRpYWxseSB0byB0aGlzIGRvY3VtZW50LCBhbmQg
dGhlaXIgaGVscCBhbmQgY29udHJpYnV0aW9ucwogICBoZWxwZWQgdHVybiBhbiBpZGVhIGlu
dG8gYSBzcGVjaWZpY2F0aW9uLgoKMTAuICBOb3JtYXRpdmUgUmVmZXJlbmNlcwoKICAgW1JG
QzIxMTldICBCcmFkbmVyLCBTLiwgIktleSB3b3JkcyBmb3IgdXNlIGluIFJGQ3MgdG8gSW5k
aWNhdGUKICAgICAgICAgICAgICBSZXF1aXJlbWVudCBMZXZlbHMiLCBCQ1AgMTQsIFJGQyAy
MTE5LCBNYXJjaCAxOTk3LgoKICAgW1JGQzM1NTBdICBTY2h1bHpyaW5uZSwgSC4sIENhc25l
ciwgUy4sIEZyZWRlcmljaywgUi4sIGFuZCBWLgogICAgICAgICAgICAgIEphY29ic29uLCAi
UlRQOiBBIFRyYW5zcG9ydCBQcm90b2NvbCBmb3IgUmVhbC1UaW1lCiAgICAgICAgICAgICAg
QXBwbGljYXRpb25zIiwgUkZDIDM1NTAsIFNURCAwMDY0LCBKdWx5IDIwMDMuCgogICBbaGRy
ZXh0XSAgIFNpbmdlciwgRC4sICJBIGdlbmVyYWwgbWVjaGFuaXNtIGZvciBSVFAgSGVhZGVy
CiAgICAgICAgICAgICAgRXh0ZW5zaW9ucyIsIElEIGRyYWZ0LWlldGYtYXZ0LXJ0cC1oZHJl
eHQtMDgsCiAgICAgICAgICAgICAgT2N0b2JlciAyMDA2LgoKCgoKCgoKCgoKCgoKCgoKCgoK
CgoKCgoKCgoKCgoKCgpTaW5nZXIgJiBEZXNpbmVuaSAgICAgICAgRXhwaXJlcyBBdWd1c3Qg
MywgMjAwNyAgICAgICAgICAgICAgICBbUGFnZSAxM10KDApJbnRlcm5ldC1EcmFmdCAgICAg
ICAgICBSVFAgVHJhbnNtaXNzaW9uIE9mZnNldHMgICAgICAgICAgICBKYW51YXJ5IDIwMDcK
CgpBdXRob3JzJyBBZGRyZXNzZXMKCiAgIERhdmlkIFNpbmdlcgogICBBcHBsZSBDb21wdXRl
ciBJbmMuCiAgIDEgSW5maW5pdGUgTG9vcAogICBDdXBlcnRpbm8sIENBICA5NTAxNAogICBV
UwoKICAgUGhvbmU6ICsxIDQwOCA5OTYgMTAxMAogICBFbWFpbDogc2luZ2VyQGFwcGxlLmNv
bQoKCiAgIEhhcmlraXNoYW4gRGVzaW5lbmkKICAgUXVhbGNvbW0KICAgNTc3NSBNb3JlaG91
c2UgRHJpdmUKICAgU2FuIERpZWdvLCBDQSAgOTIxMjEKICAgVVMKCiAgIFBob25lOiArMSA4
NTggODQ1IDg5OTYKICAgRW1haWw6IGhkQHF1YWxjb21tLmNvbQoKCgoKCgoKCgoKCgoKCgoK
CgoKCgoKCgoKCgoKCgoKU2luZ2VyICYgRGVzaW5lbmkgICAgICAgIEV4cGlyZXMgQXVndXN0
IDMsIDIwMDcgICAgICAgICAgICAgICAgW1BhZ2UgMTRdCgwKSW50ZXJuZXQtRHJhZnQgICAg
ICAgICAgUlRQIFRyYW5zbWlzc2lvbiBPZmZzZXRzICAgICAgICAgICAgSmFudWFyeSAyMDA3
CgoKSW50ZWxsZWN0dWFsIFByb3BlcnR5IFN0YXRlbWVudAoKICAgVGhlIElFVEYgdGFrZXMg
bm8gcG9zaXRpb24gcmVnYXJkaW5nIHRoZSB2YWxpZGl0eSBvciBzY29wZSBvZiBhbnkKICAg
SW50ZWxsZWN0dWFsIFByb3BlcnR5IFJpZ2h0cyBvciBvdGhlciByaWdodHMgdGhhdCBtaWdo
dCBiZSBjbGFpbWVkIHRvCiAgIHBlcnRhaW4gdG8gdGhlIGltcGxlbWVudGF0aW9uIG9yIHVz
ZSBvZiB0aGUgdGVjaG5vbG9neSBkZXNjcmliZWQgaW4KICAgdGhpcyBkb2N1bWVudCBvciB0
aGUgZXh0ZW50IHRvIHdoaWNoIGFueSBsaWNlbnNlIHVuZGVyIHN1Y2ggcmlnaHRzCiAgIG1p
Z2h0IG9yIG1pZ2h0IG5vdCBiZSBhdmFpbGFibGU7IG5vciBkb2VzIGl0IHJlcHJlc2VudCB0
aGF0IGl0IGhhcwogICBtYWRlIGFueSBpbmRlcGVuZGVudCBlZmZvcnQgdG8gaWRlbnRpZnkg
YW55IHN1Y2ggcmlnaHRzLiAgSW5mb3JtYXRpb24KICAgb24gdGhlIHByb2NlZHVyZXMgd2l0
aCByZXNwZWN0IHRvIHJpZ2h0cyBpbiBSRkMgZG9jdW1lbnRzIGNhbiBiZQogICBmb3VuZCBp
biBCQ1AgNzggYW5kIEJDUCA3OS4KCiAgIENvcGllcyBvZiBJUFIgZGlzY2xvc3VyZXMgbWFk
ZSB0byB0aGUgSUVURiBTZWNyZXRhcmlhdCBhbmQgYW55CiAgIGFzc3VyYW5jZXMgb2YgbGlj
ZW5zZXMgdG8gYmUgbWFkZSBhdmFpbGFibGUsIG9yIHRoZSByZXN1bHQgb2YgYW4KICAgYXR0
ZW1wdCBtYWRlIHRvIG9idGFpbiBhIGdlbmVyYWwgbGljZW5zZSBvciBwZXJtaXNzaW9uIGZv
ciB0aGUgdXNlIG9mCiAgIHN1Y2ggcHJvcHJpZXRhcnkgcmlnaHRzIGJ5IGltcGxlbWVudGVy
cyBvciB1c2VycyBvZiB0aGlzCiAgIHNwZWNpZmljYXRpb24gY2FuIGJlIG9idGFpbmVkIGZy
b20gdGhlIElFVEYgb24tbGluZSBJUFIgcmVwb3NpdG9yeSBhdAogICBodHRwOi8vd3d3Lmll
dGYub3JnL2lwci4KCiAgIFRoZSBJRVRGIGludml0ZXMgYW55IGludGVyZXN0ZWQgcGFydHkg
dG8gYnJpbmcgdG8gaXRzIGF0dGVudGlvbiBhbnkKICAgY29weXJpZ2h0cywgcGF0ZW50cyBv
ciBwYXRlbnQgYXBwbGljYXRpb25zLCBvciBvdGhlciBwcm9wcmlldGFyeQogICByaWdodHMg
dGhhdCBtYXkgY292ZXIgdGVjaG5vbG9neSB0aGF0IG1heSBiZSByZXF1aXJlZCB0byBpbXBs
ZW1lbnQKICAgdGhpcyBzdGFuZGFyZC4gIFBsZWFzZSBhZGRyZXNzIHRoZSBpbmZvcm1hdGlv
biB0byB0aGUgSUVURiBhdAogICBpZXRmLWlwckBpZXRmLm9yZy4KCgpEaXNjbGFpbWVyIG9m
IFZhbGlkaXR5CgogICBUaGlzIGRvY3VtZW50IGFuZCB0aGUgaW5mb3JtYXRpb24gY29udGFp
bmVkIGhlcmVpbiBhcmUgcHJvdmlkZWQgb24gYW4KICAgIkFTIElTIiBiYXNpcyBhbmQgVEhF
IENPTlRSSUJVVE9SLCBUSEUgT1JHQU5JWkFUSU9OIEhFL1NIRSBSRVBSRVNFTlRTCiAgIE9S
IElTIFNQT05TT1JFRCBCWSAoSUYgQU5ZKSwgVEhFIElOVEVSTkVUIFNPQ0lFVFkgQU5EIFRI
RSBJTlRFUk5FVAogICBFTkdJTkVFUklORyBUQVNLIEZPUkNFIERJU0NMQUlNIEFMTCBXQVJS
QU5USUVTLCBFWFBSRVNTIE9SIElNUExJRUQsCiAgIElOQ0xVRElORyBCVVQgTk9UIExJTUlU
RUQgVE8gQU5ZIFdBUlJBTlRZIFRIQVQgVEhFIFVTRSBPRiBUSEUKICAgSU5GT1JNQVRJT04g
SEVSRUlOIFdJTEwgTk9UIElORlJJTkdFIEFOWSBSSUdIVFMgT1IgQU5ZIElNUExJRUQKICAg
V0FSUkFOVElFUyBPRiBNRVJDSEFOVEFCSUxJVFkgT1IgRklUTkVTUyBGT1IgQSBQQVJUSUNV
TEFSIFBVUlBPU0UuCgoKQ29weXJpZ2h0IFN0YXRlbWVudAoKICAgQ29weXJpZ2h0IChDKSBU
aGUgSW50ZXJuZXQgU29jaWV0eSAoMjAwNykuICBUaGlzIGRvY3VtZW50IGlzIHN1YmplY3QK
ICAgdG8gdGhlIHJpZ2h0cywgbGljZW5zZXMgYW5kIHJlc3RyaWN0aW9ucyBjb250YWluZWQg
aW4gQkNQIDc4LCBhbmQKICAgZXhjZXB0IGFzIHNldCBmb3J0aCB0aGVyZWluLCB0aGUgYXV0
aG9ycyByZXRhaW4gYWxsIHRoZWlyIHJpZ2h0cy4KCgpBY2tub3dsZWRnbWVudAoKICAgRnVu
ZGluZyBmb3IgdGhlIFJGQyBFZGl0b3IgZnVuY3Rpb24gaXMgY3VycmVudGx5IHByb3ZpZGVk
IGJ5IHRoZQogICBJbnRlcm5ldCBTb2NpZXR5LgoKCgoKU2luZ2VyICYgRGVzaW5lbmkgICAg
ICAgIEV4cGlyZXMgQXVndXN0IDMsIDIwMDcgICAgICAgICAgICAgICAgW1BhZ2UgMTVdCgwK

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

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

--------------040804010703040701020409--




From avt-bounces@ietf.org Sun Feb 11 07:21:42 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGDfw-0000gs-B6; Sun, 11 Feb 2007 07:19:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGDfu-0000VO-Vs
	for avt@ietf.org; Sun, 11 Feb 2007 07:19:22 -0500
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGDft-00088p-JC
	for avt@ietf.org; Sun, 11 Feb 2007 07:19:22 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 11 Feb 2007 14:19:40 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C044ED28C@IsrExch01.israel.polycom.com>
In-Reply-To: <45AF87D3.9090200@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: status of  draft-ietf-avt-topologies-03
Thread-Index: Acc7GdL/AqeeeaJgRhaiSp9b6izlaQSu/6PA
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>,
	<avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: stewe@stewe.org
Subject: [AVT] status of  draft-ietf-avt-topologies-03
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi,
The document has finished the WG last call some time ago.=20
I suggest that you will prepare an updated version that will incorporate =
the comments from David Mcgrew that Magnus accepted and talking out the =
reference to what is common architecture. There werer also some nits =
from Keith Lantz.


Also please clear the nits (3 errors and 4 warnings) from the tools.

I believe that we would be ready for publication afterwards.

Roni =20

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



From avt-bounces@ietf.org Sun Feb 11 08:23:40 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGEes-0000Go-5y; Sun, 11 Feb 2007 08:22:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGEer-0000Gh-GH
	for avt@ietf.org; Sun, 11 Feb 2007 08:22:21 -0500
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGEep-000279-1M
	for avt@ietf.org; Sun, 11 Feb 2007 08:22:21 -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
Subject: RE: [AVT] CCM draft review -- should "bandwidth" include the
	headeroverhead
Date: Sun, 11 Feb 2007 15:22:11 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C044ED2BB@IsrExch01.israel.polycom.com>
In-Reply-To: <45AF89C0.6090007@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] CCM draft review -- should "bandwidth" include the
	headeroverhead
Thread-Index: Acc7ELDN1vxcM046Ty+gzIOWwbQ7SQSzndIA
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>,
	"Stephan Wenger" <stewe@stewe.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Cc: Randell Jesup <rjesup@wgate.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Magnus,
This is our view about why to use the codec bit rate and not any =
overhead. We have to remember that this is mostly for video who does not =
have a fixed frame size and that packets can be larger than MTU size and =
thus may be broken differently based on implementations.

For one thing, the amount of data in the headers depends on whether =
header compression is in use.  Since header compression can be applied =
(or removed) anywhere along the path, the amount of overhead seen by the =
receiver might be different than the overhead seen by the transmitter.

Another reason is that an intermediate device (gateways, proxies, or =
other RTP media engine) might be re-packetizing the data.  This would =
also create a mismatch between the source and the receiver.  All of this =
is avoided if we define the bit rate to be the media rate.

A third way a mismatch can be created is by encryption, where an =
encryption pad is added (or possibly removed) at the campus edge.  So =
I'd also want that RTP padding to be excluded from the definition (not =
just the headers).=20

Of course, we'd also prefer to keep it as media because that is what =
both H.323 and H.320 do and part of the usage of this command is to =
adapt rates between different transport channels.

Thanks
Roni Even
> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> Sent: Thursday, January 18, 2007 4:53 PM
> To: Stephan Wenger
> Cc: Randell Jesup; avt@ietf.org
> Subject: Re: [AVT] CCM draft review -- should "bandwidth" include the
> headeroverhead
>=20
> Hi,
>=20
> I have just read through the whole debate around what the TMMBR =
bitrate
> value should contain. I below attempt to summarize this and provide my
> view in relation to the arguments that has been made.
>=20
> 1. Bandwidth vs Bitrate
> Yes, we should change to bitrate as this is clearer. We should also
> document the assumption that the value indicated is a smoothed value.
> The only way of only indicating a single bit-rate value is to assume
> that these bits are sent in constant rate instead of bursty fashion. =
If
> we where trying to capture the bursty reality of most links then we
> would need to indicate a token bucket. Due to token buckets having two
> parameters then the owner comparison would be difficult. In addition =
it
> is not easy to determine the token bucket parameters. Thus I propose =
we
> don't go there, instead the receiver will face the jitter he will
> subjected to by the path.
>=20
> 2. What header overhead should be included.
>=20
> To me it seemed that most people was in favor of using a media rate,
> like RTP payload, or even media codec rate to be signaled. I disagree
> due to the following reasons:
>=20
> The receiver can only indicate a gross bit-rate which is available to
> receive with. He can not guess what packet rate or packetization the
> media sender will use. Thus the media sender must be the one =
responsible
> for making the sum of media rate and packetization overhead fit the
> indicated TMMBR. If not the receiver has no idea how much of his
> available bit-rate that actually will be consumed.
>=20
> When talking about gross bit-rate and packetization overhead it should
> include all headers down to and including the common layer. In the
> context of Internet applications we would then be talking about IP.
>=20
> I also would like to say that I agree with Guido Franceschini that =
TIAS
> is flawed in this regard. TIAS only works for declarative usages of =
SDP.
> TIAS is a media sender property. It doesn't work with SDP offer/answer
> as that requires one to describe the bitrate available to receive =
with.
> Thus RFC 3890 should be updated to address these issues.
>=20
> This leads to the main issue with using a bitrate value that include =
all
> overhead down to IP level. Which is the one that TIAS tried to =
address,
> the variable overhead for different parts of the transport topology.
> Lets try to understand when this becomes an issue. If one uses a total
> bitrate in the signalling the receiver may receive larger than TMMBR
> value in the case that the headers get expanded. This may occur in a =
NAT
> doing IPv4 to IPv6 translation on the path. I actually have a hard =
time
> thinking of another device doing changes without being an RTP
> translator. I think this is important as an RTP translator could be =
made
> responsible to translate the TMMBR request also. However that would =
not
> be possible to do perfect without the packet rate. Thus the question
> arise how well this should work.
>=20
> Guido's idea of including the average packet overhead might actually =
not
> be a bad one. As that would allow the sender to take into =
consideration
> the per packet overhead seen by the TMMBR sending receiver. I would
> define that overhead as the number of bytes in addition to RTP =
payload.
> The reason to include the RTP header itself is that if there are some
> translator or mixer doing something to expand the RTP header.
>=20
> Comments on this?
>=20
> Cheers
>=20
> Magnus Westerlund
>=20
> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

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



From avt-bounces@ietf.org Sun Feb 11 11:27:54 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGHX1-0002iq-Dl; Sun, 11 Feb 2007 11:26:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGHX0-0002il-JP
	for avt@ietf.org; Sun, 11 Feb 2007 11:26:26 -0500
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HGHWz-0002Bm-9Z for avt@ietf.org; Sun, 11 Feb 2007 11:26:26 -0500
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Sun, 11 Feb 2007 11:26:20 -0500
To: "Even, Roni" <roni.even@polycom.co.il>
Subject: Re: [AVT] CCM draft review -- should "bandwidth" include the
	headeroverhead
References: <144ED8561CE90C41A3E5908EDECE315C044ED2BB@IsrExch01.israel.polycom.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Sun, 11 Feb 2007 11:26:19 -0500
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C044ED2BB@IsrExch01.israel.polycom.com>
	(Roni Even's message of "Sun, 11 Feb 2007 15:22:11 +0200")
Message-ID: <ybu4ppsaces.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 11 Feb 2007 16:26:20.0943 (UTC)
	FILETIME=[5D3701F0:01C74DF9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Stephan Wenger <stewe@stewe.org>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

"Even, Roni" <roni.even@polycom.co.il> writes:
>This is our view about why to use the codec bit rate and not any
>overhead. We have to remember that this is mostly for video who does not
>have a fixed frame size and that packets can be larger than MTU size and
>thus may be broken differently based on implementations.

Which is why TIAS (especially with TMMBR) is fundamentally broken for
offer/answer.  TIAS allows setting the max packet rate - fine for a
declarative use, but for offer/answer, it means that the receiver knows the
actual bandwidth (typically configured - "I have a 1Mbps downstream",
perhaps measured/probed, but usually NOT probed end-to-end to the sender),
it must (to send TIAS) follow RFC 3890 #6.4 in reverse, using a (high)
guess at maxprate.  When done, you basically have 
TIAS = BW - (maxprate*hsize).  

So the sender limits their codec to TIAS, and probably uses a lot less than
maxprate packets, wasting that bandwidth.  If maxprate was chosen too low,
the sender might have to (for video) reduce frame rate, especially if (as
you mention) the sender wants to send more packets than the receiver
anticipates.  If the sender goes over maxprate, it might work, and might
not, and there's no way for the sender to estimate how much to reduce the
TIAS amount by other than guessing.

I think b=AS (etc) make more sense; the sender knows the actual prate, size
of any headers it sends, and so can make best use of of the available bits.
If we need to know any additional header/etc modifications inbetween the
sender and receiver, then we should find a mechanism to discover and/or
signal that directly.

>For one thing, the amount of data in the headers depends on whether header
>compression is in use.  Since header compression can be applied (or
>removed) anywhere along the path, the amount of overhead seen by the
>receiver might be different than the overhead seen by the transmitter.

And how does the receiver making an offer or answer determine this?  The
receiver typically only knows the last-link settings.

>Another reason is that an intermediate device (gateways, proxies, or other
>RTP media engine) might be re-packetizing the data.  This would also
>create a mismatch between the source and the receiver.  All of this is
>avoided if we define the bit rate to be the media rate.

Avoided: not really.  I'd say pushed off into some undefined mechanism.
Or, if not handled, you're not really solving the problem.

>A third way a mismatch can be created is by encryption, where an
>encryption pad is added (or possibly removed) at the campus edge.  So I'd
>also want that RTP padding to be excluded from the definition (not just
>the headers).

And again, how does the receiver know this to include it in the TIAS
calculation?  If this is an RTP/RTCP-aware midbox, it could adjust BW
values - if *everything* that can modify bandwidth is aware and handles
TIAS in offers and TMMBR, you could adjust TIAS by (maxprate *
packet_delta), but in reality I don't see this happening.  BTW, any
end-to-end signalling or media encryption will cause a major headache here
- the midbox can't see/modify these values.  At best it could in some cases
signal the modification separately or in a separate tag at call setup, but
that's not an option with current protocols.

>Of course, we'd also prefer to keep it as media because that is what both
>H.323 and H.320 do and part of the usage of this command is to adapt rates
>between different transport channels.

I'd say then push the burden of converting to bandwidth into media rate
onto the converter, not into every endpoint (especially since using these
conversions seems to require either a lot of assumptions or potentially
wastes bandwidth).

I think I'm pretty much in agreement with Magnus here.

Magnus also writes:
>> Guido's idea of including the average packet overhead might actually not
>> be a bad one. As that would allow the sender to take into consideration
>> the per packet overhead seen by the TMMBR sending receiver. I would
>> define that overhead as the number of bytes in addition to RTP payload.
>> The reason to include the RTP header itself is that if there are some
>> translator or mixer doing something to expand the RTP header.

This speaks to my comment above about finding a way to signal overhead
separate from link bandwidth.

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


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



From avt-bounces@ietf.org Sun Feb 11 14:00:36 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGJul-0002S8-IL; Sun, 11 Feb 2007 13:59:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGJuk-0002S1-Bt
	for avt@ietf.org; Sun, 11 Feb 2007 13:59:06 -0500
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGJug-0007N5-Kt
	for avt@ietf.org; Sun, 11 Feb 2007 13:59:06 -0500
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:61459
	helo=[192.168.0.3])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HGJuf-00075x-3j; Sun, 11 Feb 2007 18:59:01 +0000
In-Reply-To: <FDA45A7874021C40897203FA3554940002E197B8@xmb-sjc-216.amer.cisco.com>
References: <FDA45A7874021C40897203FA3554940002E197B8@xmb-sjc-216.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <90B66CE8-45E9-4897-8211-3076FDC19FA1@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Re: I-D ACTION:draft-xu-avt-subrtcp-00.txt 
Date: Sun, 11 Feb 2007 18:59:06 +0000
To: Xiaode Xu ((xdxu)) <xdxu@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 140baa79ca42e6b0e2b4504291346186
Cc: hd-yamada@kddilabs.jp, AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On 2 Feb 2007, at 18:39, Xiaode Xu ((xdxu)) wrote:
> Hi Colin, Thanks for your comments. Please see my points inlined.
> //Xiaode
>
> -----Original Message-----
> From: Colin Perkins [mailto:csp@csperkins.org]
> Sent: Friday, February 02, 2007 12:08 AM
> To: Xiaode Xu (xdxu)
> Cc: hd-yamada@kddilabs.jp; AVT WG
> Subject: Re: [AVT] Re: I-D ACTION:draft-xu-avt-subrtcp-00.txt
>
> On 2 Feb 2007, at 00:30, Xiaode Xu ((xdxu)) wrote:
>> I think I did not catch the points presented in the existing rfc docs
>> (3550 & 3611) correctly in my last email. Thanks for correcting me.
>>
>> But I feel the existing system bears the following issues:
>>
>> - For an 1-way RTP session:  E1-->T1-->T2-->E2, where E and T stands
>> for
>>   Endpoint and Translator.
>>
>>   According to 3550, E1 can send a sender info in SR to E2 which
>> returns
>>   LSR and DLSR to E1. E1 can thus estimate the RTT between E1 and E2.
>> But
>>   E2 does not have a view of the RTT.
>>
>>   With help of 3611, E2 is capable of estimating the RTT with E1 by
>>   exchanging "Receiver Reference Time Report Blocks and DLRR" via the
>> XRs.
>>
>>   In an one speaker only multicast or broadcast session, from the
>>   speaker to any receiver of the session will be an instance of the
>>   such an 1-way rtp session. Another example could be resulted
>>   from some voice mute feature.
>>
>> - According to 3550, a translater can not send sender info i.e. SR.
>> But
>>   assuming T1 can send a XR with time reference report blocks to T1
>> and
>>   receive DLRR from T2 in order to measure RTT between them. So does
>> T2.
>>   In this case, T1 and T2 needs to create their own SSRC and  
>> spread to
>>   E1 and E2 for calculating rtp report interval.
>>
>>   In this case, T1 and T2 are totally confined to the infrastructure.
>> To
>>   have their SSRC in the same SSRC space as that for endpoints E1 and
>> E2
>>   may not be too forceful.
>
> Creating an SSRC is trivial, so I don't see it as a problem.
> [XU]: In order to have all the participants sync up their report
> interval,
>       every ssrc (as rtcp speaker) needs to be maintained by each
> participant,
>       even the effort is just to measure RTT between T1 and T2.
> Creating
>       an SSRC itself is not an issue but its management and sync  
> across
> all
>       participants is not trivial.

So? All participants must implement this code anyway.

>> - How about a rtp sessiong riding over more than two Ts, this can
>> happen
>>   when a call crossing mulitple service providers' network domain.
>>   Meaturing the RTT between any two of the middle boxes based on the
>>   existing 3611 and 3550 protocols could be burdensome.
>
> This is no different for standard RTCP than for your proposal.
> [XU] This is a big difference between SubRTCP and regular RTCP.  
> SubRTCP
>      carrying its own message type, a middle box can immediately  
> forward
>      it further out and simultaneously digest it, if configured to do
> so.
>      This can ensure better accuracy of the RTT estimation. A  
> SubRTCP SR
>      message is capable of soliciting response from all the middle
> boxes,
>      not just one.

I simply do not believe the complexity of looking at RTCP packet  
types is significant compared to checking the subRTCP packet type.

> In order to limit how far a SubRTCP message can reach, a hop limit  
> field may help.

IP has such a field, independent of RTCP or subRTCP.

>      Coming back to the regular RTCP, the intended middle box for its
>      messages is not clear or explicit. Either each middle box parses
>      a received RTCP message to look for the portion of interest to
>      digest or terminate it and create a new RTCP message as a mixer
>      does. If a middle box terminates a received RTCP and creates a
>      new RTCP, the true sender and receiver (listener) will lose the
>      true judgement of the RTP media quality. In principle, I prefer
>      regular RTCP maintains its native observation of its accompanying
>      RTP stream.
>
>      Please think about the advantage of separation of end2end rtcp
>      and internal rtcp for their respective monitoring purpose in
> comparision
>      with one rtcp lumping two things in one participant group. Yes,
>      we can treat all middle boxes as regular RTCP speaker, but the
>      cost and complexity and efficiency in implementation will differ.

I see the complexity as coming from introducing an additional  
protocol where none is needed: subRTCP is more complex than regular  
RTCP.

>> - Also when an RTCP packet traverses through all the middle boxes, if
>>   each box needs to look into a compound RTCP packet for XR packet's
>>   reference time blocks to act, it will delay the passing-through of
>>   the RTCP packet and cause the inaccuracy of the RTT estimation in
>> the
>>   end.
>
> Those boxes have to examine every packet to tell if they are RTCP or
> subRTCP in your proposal. Checking the RTCP packet type values instead
> turns a single "if" statement in the code into a "for" loop containing
> an "if" statement. In almost all cases, that loop will iterate over  
> two
> values (and SR/RR packet, followed by an SDES packet). This adds one
> extra comparison per packet, and will not cause significant delay.
> [XU] The reason being stated above: a middle box only needs to know if
> it's a subRTCP packet or regular RTCP packet. It
>      has its choice whether it needs to dig into a SubRTCP message.
> Regardlessly, it can forward the SubRTCP message
>      further up or down immediately. But for a regular RTCP message, a
> middle box needs to parse the message to know
>      what is being carried to process them accordingly. For  
> example, the
> SDES needs to be made known all the others.
>      SubRTCP can get rid of this burden by simplifying uneccessary
> elements.

As I said previously, who cares? The "burden" of parsing RTCP is  
negligible.

>      On the other hand, per-session observation of an RTP stream at a
> middle box is mostly for debugging purpose. But
>      even so, internal monitoring of a media path may be more  
> important
> than the end2end monitoring from a service
>      provider's purspective.
>      With SubRTCP separation from the regular RTCP, another cent is
> SubRTCP can be turned off when not needed. It should
>      be turned off after the network is tuned well.

This is no different to regular RTCP.

>> Coming back to SubRTCP, it uses its own message type, middle boxes  
>> can
>
>> act upon them right way. Also it is functioning on a different SSRC
>> space which can make the group of endpoints easier in performing
>> regular RTCP jobs.
>
> Why do you think this makes the endpoints job easier? The RTCP packets
> from the infrastructure nodes don't need to reach the end systems, and
> even if they do, I don't see that it will cause any additional
> complexity.
>
> [XU] With endpoints and middle boxes in the same SSRC space, they are
> equal RTCP speaker and should be make known to all
>      participants in order to get the dynamically synced report
> interval.

This has to be done for subRTCP too, if you wish to scale the  
reporting interval. If no, simply send regular RTCP internal to the  
infrastructure.

>> Even Translator can send RR and Mixer can do both SR and RR, they are
>> still not true endpoints.
>> In principle, the true meaningful sense of the RTCP will be more
>> obvious when it accompanys the its RTP session. In field, complaints
>> are usually from RTP endpoints, the true sender and receiver.
>
> I think you misunderstand the definition of RTP session. The  
> association
> of RTP systems that includes the middleboxes and end point is a single
> RTP session, with associated RTCP. RTCP is explicitly intended to  
> allow
> the type of monitoring you desire as part of its "true meaningful
> sense".
>
> [XU] I understood. Treat all RTP nodes involved in one RTP session
> including all endpoints and middle points in one SSRC
>      space is arguable to me. Think about the good aspect of partition
> endpoints and middle nodes into two SSRC-space
>      groups as we do to differ host nodes and transport nodes
> (router/switch) in networking.

What good aspect? It is *intentional* in the design of RTCP that  
middleboxes use the same SSRC space, since it allows endpoints to  
monitor the quality to those middleboxes.

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



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



From avt-bounces@ietf.org Sun Feb 11 14:23:20 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGKHS-0006Aa-SL; Sun, 11 Feb 2007 14:22:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGK7H-0007gi-CW
	for avt@ietf.org; Sun, 11 Feb 2007 14:12:03 -0500
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGK7E-0000d4-BM
	for avt@ietf.org; Sun, 11 Feb 2007 14:12:03 -0500
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:61529
	helo=[192.168.0.3])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HGK7C-0000DP-7d for avt@ietf.org; Sun, 11 Feb 2007 19:11:59 +0000
Mime-Version: 1.0 (Apple Message framework v752.2)
To: AVT WG <avt@ietf.org>
Message-Id: <E3ECD0C5-153B-4AC6-8BDF-A7F16BFD7755@csperkins.org>
Content-Type: multipart/mixed; boundary=Apple-Mail-6--359604656
From: Colin Perkins <csp@csperkins.org>
Date: Sun, 11 Feb 2007 19:12:03 +0000
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52005c17383d4e3f609075a067e11971
X-Mailman-Approved-At: Sun, 11 Feb 2007 14:22:33 -0500
Subject: [AVT] =?utf-8?q?Liaison_Statement_from_3rd_FG_IPTV_meeting_=28Mo?=
 =?utf-8?q?untain_View=2C_22-26_Jan=2E_2007=29__=EF=BF=BC?=
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org


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

AVT working group,

Please find attached a liaison statement from the 3rd ITU FG IPTV  
meeting held in Mountain View, California, USA, from 22-26 January  
2007. Those interested in this work should respond directly to the  
ITU-T, cc'ing the AVT group as appropriate.

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






--Apple-Mail-6--359604656
Content-Transfer-Encoding: base64
Content-Type: application/msword; x-unix-mode=0644; name=FG IPTV-OL-0021e.doc
Content-Disposition: attachment;
	filename="FG IPTV-OL-0021e.doc"

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAXgAAAAAAAAAA
EAAAYAAAAAEAAAD+////AAAAAF8AAAD/////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////s
pcEAA2AJBAAA+BK/AAAAAAAAMAAAAAAABgAAphIAAA4AYmpiastzy3MAAAAAAAAAAAAAAAAAAAAA
AAAJBBYAOzQAAKkZAQCpGQEAWwgAAAAAAABKAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAD//w8AAAAA
AAAAAAD//w8AAAAAAAAAAAD//w8AAAAAAAAAAAAAAAAAAAAAAKQAAAAAAEYfAAAAAAAARh8AAEYf
AAAAAAAARh8AAAAAAABGHwAAAAAAAEYfAAAAAAAARh8AABQAAAAAAAAAAAAAAFofAAAAAAAAhjEA
AAAAAACGMQAAAAAAAIYxAAA4AAAAvjEAACQAAADiMQAAXAAAAFofAAAAAAAAST8AAGgBAABKMgAA
KAAAAHIyAAAWAAAAiDIAAAAAAACIMgAAAAAAAIgyAAAAAAAAvDMAAKgAAABkNAAAVAAAALg0AAAs
AAAAyD4AAAIAAADKPgAAAAAAAMo+AAAAAAAAyj4AAAAAAADKPgAAAAAAAMo+AAAAAAAAyj4AACQA
AACxQAAAaAIAABlDAAA6AQAA7j4AABUAAAAAAAAAAAAAAAAAAAAAAAAARh8AAAAAAAClNgAAAAAA
AAAAAAAAAAAAAAAAAAAAAAC8MwAAAAAAALwzAAAAAAAApTYAAAAAAAClNgAAAAAAAO4+AAAAAAAA
AAAAAAAAAABGHwAAAAAAAEYfAAAAAAAAiDIAAAAAAAAAAAAAAAAAAIgyAAA0AQAAAz8AABYAAAC/
OAAAAAAAAL84AAAAAAAAvzgAAAAAAAClNgAAoAAAAEYfAAAAAAAAiDIAAAAAAABGHwAAAAAAAIgy
AAAAAAAAyD4AAAAAAAAAAAAAAAAAAL84AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAApTYAAAAAAADIPgAAAAAAAAAAAAAAAAAAvzgAAAAAAAC/OAAA
HgAAAIA7AABoAAAARh8AAAAAAABGHwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA+DsAAAwAAACIMgAAAAAAAD4yAAAMAAAAIANsNcNA
xwEAAAAAAAAAAIYxAAAAAAAARTcAAGQAAADoOwAACAAAAAAAAAAAAAAAPD0AAIwBAAAZPwAAMAAA
AEk/AAAAAAAA8DsAAAgAAABTRAAAAAAAAKk3AAC+AAAAU0QAABAAAAAEPAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAFNEAAAAAAAAAAAAAAAAAABGHwAAAAAAAAQ8AAA4AQAA5DQAAFoAAAA+NQAAQAAAAL84
AAAAAAAAfjUAADQAAACyNQAA8wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA5DQA
AAAAAADkNAAAAAAAAOQ0AAAAAAAA7j4AAAAAAADuPgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAZzgAAFgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAOQ0AAAA
AAAA5DQAAAAAAADkNAAAAAAAAEk/AAAAAAAApTYAAAAAAAClNgAAAAAAAKU2AAAAAAAApTYAAAAA
AAAAAAAAAAAAAFofAAAAAAAAWh8AAGQAAAC+HwAAJAkAAOIoAACkCAAAWh8AAAAAAABaHwAAAAAA
AL4fAAAAAAAA4igAAAAAAABaHwAAAAAAAFofAAAAAAAAWh8AAAAAAABGHwAAAAAAAEYfAAAAAAAA
Rh8AAAAAAABGHwAAAAAAAEYfAAAAAAAARh8AAAAAAAD/////AAAAAAIADAEAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAENB0lO
VEVSTkFUSU9OQUwgVEVMRUNPTU1VTklDQVRJT04gVU5JT04HRm9jdXMgR3JvdXAgT24gSVBUVgcH
B1RFTEVDT01NVU5JQ0FUSU9OC1NUQU5EQVJESVpBVElPTiBTRUNUT1INU1RVRFkgUEVSSU9EIDIw
MDUtMjAwOAdGRyBJUFRWLU9MLTAwMjEHBwcHRW5nbGlzaCBvbmx5BwdXRyhzKTogUEwHBzNyZCBG
RyBJUFRWIG1lZXRpbmc6C01vdW50YWluIFZpZXcsIDIyLTI2IEphbnVhcnkgMjAwNwcHT1VUR09J
TkcgTElBSVNPTiBTVEFURU1FTlQHB1NvdXJjZToHQ2hhaXJtYW4sIElUVS1UIEZHIElQVFYHB1Rp
dGxlOgdQZXJmb3JtYW5jZSBNb25pdG9yaW5nIGZvciBJUFRWBwcHB1RvOgdJRVRGIElQUE0sIElF
VEYgQVZUBwdBcHByb3ZhbDoHRkcgSVBUVgcHRm9yOgdpbmZvcm1hdGlvbiBhbmQgYWN0aW9uBwdE
ZWFkbGluZToHMzB0aCBBcHJpbCAyMDA3BwdDb250YWN0OgdHaGFzc2VtIEtvbGV5bmkLTm9ydGVs
IE5ldHdvcmtzIChDYW5hZGEpC0NhbmFkYQ0HVGVsOiArMSAoNjEzKSA3NjMgNDE1NA1FbWFpbDog
EyBIWVBFUkxJTksgIm1haWx0bzpnaGFzc2VtQG5vcnRlbC5jb20iIAEUZ2hhc3NlbUBub3J0ZWwu
Y29tFQcHUGxlYXNlIGRvbpJ0IGNoYW5nZSB0aGUgc3RydWN0dXJlIG9mIHRoaXMgdGFibGUsIGp1
c3QgaW5zZXJ0IHRoZSBuZWNlc3NhcnkgaW5mb3JtYXRpb24uBwdJVFUtVCBGb2N1cyBHcm91cCBJ
UFRWIFdvcmtpbmcgR3JvdXAgMiBpcyB3b3JraW5nIG9uIFFvUyBhbmQgUGVyZm9ybWFuY2UgYXNw
ZWN0cyBmb3IgSVBUVi4gQXMgb25lIG9mIG91ciB3b3JrIGl0ZW1zIHdlIGFyZSBkZWZpbmluZyBQ
ZXJmb3JtYW5jZSBNb25pdG9yaW5nIGZvciBJUFRWLiBXZSBhcmUgY29uc2lkZXJpbmcgcGVyZm9y
bWFuY2UgbW9uaXRvcmluZyBmb3IgdGhlIElQVFYgc2VydmljZXMgYW5kIHRoZSB1bmRlcmx5aW5n
IG5ldHdvcmsgaW5mcmFzdHJ1Y3R1cmUuDUF0IHRoZSBKYW51YXJ5IDIwMDcgbWVldGluZyBXRzIg
d2FzIGluZm9ybWVkIGJ5IGNvbnRyaWJ1dGlvbnMgYW5kIGEgbGlhaXNvbiBmcm9tIElUVS1UIFNH
MTIgYWJvdXQgb25nb2luZyB3b3JrIHJlbGF0ZWQgdG8gbmV0d29yayBjYXBhY2l0eSBtZXRyaWNz
IGFuZCB2aWRlbyBtZXRyaWNzIGluIElFVEYgV29ya2luZyBHcm91cHMgSVBQTSBhbmQgQVZULiBB
cyBib3RoIGFjdGl2aXRpZXMgYXJlIG9mIGludGVyZXN0IHRvIHRoZSB3b3JrIG9mIFdHMiB3ZSB3
b3VsZCBsaWtlIHRvIGluaXRpYXRlIGxpYWlzb24gd2l0aCBJRVRGIElQUE0gYW5kIEFWVCBmb3Ig
ZXhjaGFuZ2Ugb2YgaW5mb3JtYXRpb24uIEZvciB5b3VyIGluZm9ybWF0aW9uIGFuZCByZXZpZXcg
cGxlYXNlIGZpbmQgbGF0ZXN0IHZlcnNpb24gb2Ygb3VyIHdvcmtpbmcgZG9jdW1lbnQgRkcgSVBU
Vi1ET0MtMDA2NiCTUGVyZm9ybWFuY2UgTW9uaXRvcmluZyBmb3IgSVBUVpQgYXQgdGhlIFVSTCBn
aXZlbiBiZWxvdy4gV2UgYXJlIGludGVyZXN0ZWQgaW4geW91ciBmZWVkYmFjayB0byB0aGlzIGRv
Y3VtZW50LiBGdXJ0aGVybW9yZSwgd2Uga2luZGx5IGFzayB0byByZWNlaXZlIGluZm9ybWF0aW9u
IGFib3V0IHlvdXIgd29yayBpdGVtcyByZWxhdGVkIHRvIHRoaXMgZG9jdW1lbnQuIA1GRyBJUFRW
IHdvdWxkIGFsc28gbGlrZSB0byByZW1pbmQgeW91IHRoYXQgYWxsIGl0cyBkb2N1bWVudHMgKElu
cHV0cywgT3V0cHV0cywgUmVwb3J0cyBhbmQgTGlhaXNvbiBTdGF0ZW1lbnRzKSBhcmUgcHVibGlj
bHkgYXZhaWxhYmxlLiAgDU91ciByZWNlbnQgbWVldGluZyBwcm9kdWNlZCBhIG51bWJlciBvZiBv
dXRwdXQgZG9jdW1lbnRzIHdoaWNoIG1heSBiZSBvZiBpbnRlcmVzdCB0byB5b3VyIG1lbWJlcnMu
IEFsbCBGRyBJUFRWIGRvY3VtZW50cyBjYW4gYmUgb2J0YWluZWQgZnJvbSANEyBIWVBFUkxJTksg
Imh0dHA6Ly93d3cuaXR1LmludC9JVFUtVC9JUFRWIiABFHd3dy5pdHUuaW50L0lUVS1UL0lQVFYV
DQ1GRyBJUFRWIGlzIGxvb2tpbmcgZm9yd2FyZCB0byBvdXIgY29udGludWluZyBjb29wZXJhdGlv
biB3aXRoIElFVEYgb24gdG9waWNzIG9mIG11dHVhbCBpbnRlcmVzdC4gDVRoZSBuZXh0IG1lZXRp
bmcgb2YgRkcgSVBUViB3aWxsIGJlIGhlbGQgZnJvbSA3IHRvIDExIE1heSAyMDA3IGluIEJsZWQs
IFNsb3ZlbmlhLiANX19fX19fX19fX19fDQMNDQQNDQMNDQQNDS0gEyBQQUdFICBcKiBNRVJHRUZP
Uk1BVCAUMhUgLQ1GRyBJUFRWIJYgT0wgIJYgRQ0NQXR0ZW50aW9uOiBUaGlzIGlzIGEgZG9jdW1l
bnQgc3VibWl0dGVkIHRvIHRoZSB3b3JrIG9mIElUVS1UIGFuZCBpcyBpbnRlbmRlZCBmb3IgdXNl
IGJ5IHRoZaBwYXJ0aWNpcGFudHMgdG8gdGhlIGFjdGl2aXRpZXMgb2YgSVRVLVQncyBGb2N1cyBH
cm91cCBvbiBJUFRWLCBhbmQgdGhlaXIgcmVzcGVjdGl2ZSBzdGFmZiBhbmQgY29sbGFib3JhdG9y
cyBpbiB0aGVpciBJVFUtcmVsYXRlZCB3b3JrLqAgSXQgaXMgbWFkZSBwdWJsaWNseSBhdmFpbGFi
bGUgZm9yIGluZm9ybWF0aW9uIHB1cnBvc2VzIGJ1dCBzaGFsbCBub3QgYmUgcmVkaXN0cmlidXRl
ZCB3aXRob3V0IHRoZSBwcmlvciB3cml0dGVuIGNvbnNlbnQgb2YgSVRVLqAgQ29weXJpZ2h0IG9u
IHRoaXMgZG9jdW1lbnQgaXMgb3duZWQgYnkgdGhlIGF1dGhvciwgdW5sZXNzIG90aGVyd2lzZSBt
ZW50aW9uZWQuoCBUaGlzIGRvY3VtZW50IGlzIG5vdCBhbiBJVFUtVCBSZWNvbW1lbmRhdGlvbiwg
YW4gSVRVIHB1YmxpY2F0aW9uLCBvciBwYXJ0IHRoZXJlb2YuBwcNDQ0NAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGAAABCAAAAwgA
ACkIAAA8CAAAPQgAAD8IAABoCAAAfggAAH8IAACCCAAAhwgAAIgIAACJCAAAiggAAI4IAACPCAAA
kQgAAJIIAACZCAAAnggAAJ8IAACgCAAAqQgAAKoIAACrCAAArAgAAPHq4dTL6r/htaqckYace2/q
v2Nab+pTSepFAAAAAAYWaAZnHwAAEhVoV37GABZoV37GADUIgVwIgQAMFmiqNAYANQiBXAiBABAW
aJkX5QA1CIFDShwAXAiBABYVaBUttwAWaFd+xgA1CIFDShwAXAiBABYVaFd+xgAWaFd+xgA1CIFD
ShwAXAiBABQWaKo0BgA1CIFDSiIAXAiBYUoiAAAUFmgIKLUANQiBQ0oiAFwIgWFKIgAAFBZoFTm2
ADUIgUNKIgBcCIFhSiIAABoVaEd9bQAWaCpkPwA1CIFDSiIAXAiBYUoiAAAUFmj8P/cANQiBQ0oi
AFwIgWFKIgAAExVoV37GABZoV37GADoIgUNKFAAWFWhXfsYAFmhXfsYANQiBQ0oaAFwIgQAQFWhX
fsYAFmhXfsYAQ0ocAAAZFWh0aWcAFmgqZD8ANQiBOgiBQ0ocAFwIgRAVaFd+xgAWaFd+xgBDShQA
AAwVaFd+xgAWaFd+xgAAHANqAAAAABVoV37GABZoV37GADUIgUNKJABVCAEaAAYAAAIIAAADCAAA
KQgAAD0IAAA+CAAAPwgAAGgIAAB/CAAAjwgAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAA
AAAAAAAAAAAAAOoAAAAAAAAAAAAAAACJAAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAA
AAAAAAD2AAAAAAAAAAAAAAAA6gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABgAABrZB8LAAAWJAEXJAFJZgEAAAAC
ljkAAzQBCNZGAAPH/1AFeRmKJmAGiQUAAAAAAAAAAAAAAAAAAAAAAAYpFAAAAAAAAAAAAAAAAAAA
AAAABhENAAAAAAAAAAAAAAAAAAAAABT2A8MmF/YDAAAY9gMAABrWDAAAAP8AAAD/AAAA/xvWDAAA
AP8AAAD/AAAA/xzWDAAAAP8AAAD/AAAA/x3WDAAAAP8AAAD/AAAA/zTWBgABCgM5AGH2AwAAZjQB
DAAAAyQCFiQBSWYBAAAAYSQCZ2RXfsYACQAAFiQBSWYBAAAAZ2RXfsYAAAkABgAAWxAAAKUSAAD+
/gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgEBAo8IAACQCAAAkQgAAJII
AACfCAAAnAAAAAAAAAAAAAAAAJMAAAAAAAAAAAAAAACTAAAAAAAAAAAAAAAAhQAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADgAAAyQCE6QAABYkAUlmAQAAAGEkAmdkV37GAAkAABYk
AUlmAQAAAGdkV37GAABiAABrZKgLAAAWJAEXJAFJZgEAAAACljkAAzQBB5RjAQjWRgADx/9QBRgV
iiYgBokFAAAAAAAAAAAAAAAAAAAAAGAGyA8AAAAAAAAAAAAAAAAAAAAAAAZyEQAAAAAAAAAAAAAA
AAAAAAAU9gPDJhf2AwAAGPYDAAAa1gwAAAD/AAAA/wAAAP8b1gwAAAD/AAAA/wAAAP8c1gwAAAD/
AAAA/wAAAP8d1gwAAAD/AAAA/wAAAP801gYAAQoDOQBh9gMAAGY0AQAEnwgAAKAIAACqCAAAqwgA
AOIIAACcAAAAAAAAAAAAAAAAkwAAAAAAAAAAAAAAAJMAAAAAAAAAAAAAAACHAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADAAAAyQCFiQBSWYBAAAAYSQCZ2RXfsYACQAAFiQB
SWYBAAAAZ2RXfsYAAGIAAGtkOgwAABYkARckAUlmAQAAAAKWOQADNAEHlAwDCNZGAAPH/1AFGBWK
JiAGiQUAAAAAAAAAAAwBAAAAAAAAIAbIDwAAAAAAAAAADAEAAAAAAACABnIRAAAAAAAAAAAMAQAA
AAAAABT2A8MmF/YDAAAY9gMAABrWDAAAAP8AAAD/AAAA/xvWDAAAAP8AAAD/AAAA/xzWDAAAAP8A
AAD/AAAA/x3WDAAAAP8AAAD/AAAA/zTWBgABCgM5AGH2AwAAZjQBAASsCAAArggAAOEIAADjCAAA
7AgAAP0IAAD+CAAABwkAABEJAAAUCQAAGQkAAB4JAAAgCQAAJgkAACcJAABGCQAASAkAAEoJAABO
CQAAYQkAAG0JAAB0CQAAewkAAJEJAACdCQAAnwkAAKEJAACiCQAArAkAAK4JAAC3CQAAxgkAAOAJ
AADmCQAA6AkAAP8JAAAGCgAA9/Ps59/Vy8fDx8Psy+y77Lavq6+kr52vlouWna+EfHF8cWZeAAAA
AA4WaKo0BgBtSAwQc0gMEAAUFWigONgAFmiqNAYAbUgMBHNIDAQAFBVoIwtEABZoqjQGAG1ICgRz
SAoEAA4WaKo0BgBtSAoEc0gKBAAMFmiqNAYANQiBXAiBABUVaKQVowAWaKQVowA1CIFIKgFcCIEM
FmikFaMANQiBXAiBAAwWaM83KAA1CIFcCIEADBZoD0BSADUIgVwIgQAGFmgPQFIAAAwWaKJSlgA1
CIFcCIEACRZoolKWADUIgQ4WaA9AUgBtSAkEc0gJBAAGFmjPNygAAAYWaKo0BgAAEhVoV37GABZo
V37GADUIgVwIgQASFWhXfsYAFmjqWh8ANQiBXAiBAA8VaKobvwAWaOpaHwA1CIEJFmjqWh8ANQiB
DBVoV37GABZoV37GAAAGFmgGZx8AAA8VaEAdzQAWaAZnHwBIKgEAJOIIAADjCAAA/ggAAP8IAAAH
CQAAHwkAAJwAAAAAAAAAAAAAAACQAAAAAAAAAAAAAAAAUwAAAAAAAAAAAAAAAEoAAAAAAAAAAAAA
AABKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAJAAAWJAFJZgEAAABnZFd+xgAAPAAAa2RoDQAAFiQBFyQBSWYBAAAA
ApY5AAM0AQeUZQEI1hoAAcf/iiYABsMmAAAAAAAAAAAAAAAAAAAAABT2A8MmF/YDAAAY9gMAABrW
BAAAAP8b1gQAAAD/HNYEAAAA/x3WBAAAAP801gYAAQoDOQBh9gMAAGY0AQwAAAMkARYkAUlmAQAA
AGEkAWdkV37GAABiAABrZOAMAAAWJAEXJAFJZgEAAAACljkAAzQBB5RlAQjWRgADx/8YBjgTiiYA
BlEGAAAAAAAAAAAAAAAAAAAAAAAGIA0AAAAAAAAAAAAAAAAAAAAAAAZSEwAAAAAAAAAAAAAAAAAA
AAAU9gPDJhf2AwAAGPYDAAAa1gwAAAD/AAAA/wAAAP8b1gwAAAD/AAAA/wAAAP8c1gwAAAD/AAAA
/wAAAP8d1gwAAAD/AAAA/wAAAP801gYAAQoDOQBh9gMAAGY0AQAFHwkAACAJAAAnCQAARwkAAEgJ
AABJCQAArwAAAAAAAAAAAAAAAKQAAAAAAAAAAAAAAACkAAAAAAAAAAAAAAAAVAAAAAAAAAAAAAAA
AEsAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAACQAAAyQBFiQBSWYBAAAAYSQBAE8AAGtkNg4AABYkARckAUlmAQAA
AAKWOQADNAEHlGUBCNYwAALH/xgGiiYABlEGAAAAAAAAAAAMAQAAAAAAAAAGciAAAAAAAAAAAAwB
AAAAAAAAFPYDwyYX9gMAABj2AwAAGtYIAAAA/wAAAP8b1ggAAAD/AAAA/xzWCAAAAP8AAAD/HdYI
AAAA/wAAAP801gYAAQoDOQBh9gMAAGY0AQsAABSkeAAWJAFJZgEAAABnZFd+xgAATwAAa2TEDQAA
FiQBFyQBSWYBAAAAApY5AAM0AQeUZQEI1jAAAsf/GAaKJgAGUQYAAAAAAAAAAAAAAAAAAAAAAAZy
IAAAAAAAAAAAAAAAAAAAAAAU9gPDJhf2AwAAGPYDAAAa1ggAAAD/AAAA/xvWCAAAAP8AAAD/HNYI
AAAA/wAAAP8d1ggAAAD/AAAA/zTWBgABCgM5AGH2AwAAZjQBAAVJCQAASgkAAE4JAABiCQAAYwkA
AG0JAAB1CQAAwgAAAAAAAAAAAAAAALwAAAAAAAAAAAAAAAC8AAAAAAAAAAAAAAAAbAAAAAAAAAAA
AAAAALwAAAAAAAAAAAAAAAC8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAATwAAa2QgDwAAFiQBFyQBSWYBAAAAApY5AAM0AQeU
ZQEI1jAAAsf/GAaKJgAGUQYAAAAAAAAAAAAAAAAAAAAAAAZyIAAAAAAAAAAAAAAAAAAAAAAU9gPD
Jhf2AwAAGPYDAAAa1ggAAAD/AAAA/xvWCAAAAP8AAAD/HNYIAAAA/wAAAP8d1ggAAAD/AAAA/zTW
BgABCgM5AGH2AwAAZjQBBgAAFiQBSWYBAAAAADwAAGtktg4AABYkARckAUlmAQAAAAKWOQADNAEH
lGUBCNYaAAHH/4omAAbDJgwBAAAAAAAAAAAAAAAAAAAU9gPDJhf2AwAAGPYDAAAa1gQAAAD/G9YE
AAAA/xzWBAAAAP8d1gQAAAD/NNYGAAEKAzkAYfYDAABmNAEABnUJAAB2CQAAewkAAJIJAACTCQAA
nQkAAK0JAACvAAAAAAAAAAAAAAAAqQAAAAAAAAAAAAAAAKkAAAAAAAAAAAAAAABZAAAAAAAAAAAA
AAAAqQAAAAAAAAAAAAAAAKkAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAATwAAa2QEEAAAFiQB
FyQBSWYBAAAAApY5AAM0AQeUZQEI1jAAAsf/GAaKJgAGUQYAAAAAAAAAAAAAAAAAAAAAAAZyIAAA
AAAAAAAAAAAAAAAAAAAU9gPDJhf2AwAAGPYDAAAa1ggAAAD/AAAA/xvWCAAAAP8AAAD/HNYIAAAA
/wAAAP8d1ggAAAD/AAAA/zTWBgABCgM5AGH2AwAAZjQBBgAAFiQBSWYBAAAAAE8AAGtkkg8AABYk
ARckAUlmAQAAAAKWOQADNAEHlGUBCNYwAALH/xgGiiYABlEGAAAAAAAAAAAAAAAAAAAAAAAGciAA
AAAAAAAAAAAAAAAAAAAAFPYDwyYX9gMAABj2AwAAGtYIAAAA/wAAAP8b1ggAAAD/AAAA/xzWCAAA
AP8AAAD/HdYIAAAA/wAAAP801gYAAQoDOQBh9gMAAGY0AQAGrQkAAK4JAAC3CQAA5wkAAOgJAAD/
CQAARAoAAK8AAAAAAAAAAAAAAACpAAAAAAAAAAAAAAAAoAAAAAAAAAAAAAAAAKAAAAAAAAAAAAAA
AACgAAAAAAAAAAAAAAAAoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAJAAAWJAFJZgEAAABnZBti9gAGAAAWJAFJZgEAAAAATwAAa2R2EAAAFiQB
FyQBSWYBAAAAApY5AAM0AQeUZQEI1jAAAsf/GAaKJgAGUQYAAAAAAAAAAAwBAAAAAAAAAAZyIAAA
AAAAAAAADAEAAAAAAAAU9gPDJhf2AwAAGPYDAAAa1ggAAAD/AAAA/xvWCAAAAP8AAAD/HNYIAAAA
/wAAAP8d1ggAAAD/AAAA/zTWBgABCgM5AGH2AwAAZjQBAAYGCgAABwoAABoKAAAsCgAALgoAAC8K
AAAwCgAAQgoAAEMKAABECgAARQoAAJ4KAAChCgAAwwoAAMUKAACuCwAAtAsAANELAACBDAAAoQwA
AKcMAACuDAAAyAwAAAgNAAAvDQAAVw0AAGcNAABoDQAAiQ0AAKANAADVDQAA4g0AAOMNAADxDQAA
GQ4AAB8OAAA5DgAAOg4AAFIPAABTDwAAfg8AAPPr4OvO88Hz67awrKikqKCcqJyonJiolKiYkKiU
qIyYjKCcoKiIfHUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMFWg5I8oAFmjYaqwAABcD
agAAAAAWaNhqrABVCAFtSAwEc0gMBAYWaNhqrAAABhZoKCKTAAAGFmjTZpAAAAYWaJIUWQAABhZo
qjQGAAAGFmhQKHIAAAYWaBJG0QAABhZoIBNqAAAGFmgPQFIAAAYWaLUgBwAAChZoolKWAENKEgAA
FBZoqjQGADUIgVwIgW1IDBBzSAwQABgVaFgsyQAWaKo0BgAwSm0AbUgMEHNIDBAAIwIIgQNq9hAA
AAYIARVoWCzJABZoqjQGAFUIAW1IDBBzSAwQFBVoZGuhABZoqjQGAG1IDBBzSAwQAA4WaKo0BgBt
SAwQc0gMEAAXA2oAAAAAFmiqNAYAVQgBbUgMEHNIDBAAKEQKAABFCgAAnQoAAJ4KAACuCwAAOg4A
AMMOAABSDwAAnAAAAAAAAAAAAAAAAJQAAAAAAAAAAAAAAABXAAAAAAAAAAAAAAAAUgAAAAAAAAAA
AAAAAFIAAAAAAAAAAAAAAABNAAAAAAAAAAAAAAAATQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAABAAAZ2TYaqwAAAQAAGdkaWXQAAA8AABrZFsSAAAWJAEXJAFJZgEA
AAACljkAAzQBB5TMAAjWGgABx/+KJgAGwyYMAQAAAAAAAAAAAAAAAAAAFPYDwyYX9gMAABj2AwAA
GtYEAAAA/xvWBAAAAP8c1gQAAAD/HdYEAAAA/zTWBgABCgM5AGH2AwAAZjQBCAAAE6QAABYkAUlm
AQAAAABiAABrZMURAAAWJAEXJAFJZgEAAAACljkAAzQBB5TMAAjWRgADx/8YBkIXiiYABlEGDAEA
AAAAAAAAAAAAAAAAAAAGKhEMAQAAAAAAAAAAAAAAAAAAAAZIDwwBAAAAAAAAAAAAAAAAAAAU9gPD
Jhf2AwAAGPYDAAAa1gwAAAD/AAAA/wAAAP8b1gwAAAD/AAAA/wAAAP8c1gwAAAD/AAAA/wAAAP8d
1gwAAAD/AAAA/wAAAP801gYAAQoDOQBh9gMAAGY0AQAHfg8AAH8PAACADwAAlg8AAJcPAACYDwAA
ThAAAFoQAABbEAAAXBAAAF4QAABfEAAAYRAAAGIQAABkEAAAZRAAAGcQAABpEAAAahAAAIAQAACB
EAAAghAAAIMQAACGEAAAjRAAAJAQAACUEAAAmBAAAJkQAACiEAAA+xAAABcRAAAaEQAAHBEAACoR
AAAuEQAAnxIAAKASAACiEgAAoxIAAKQSAAClEgAAphIAAO3h2OHRzcnFvbm9ub25vbmyp7Knnqey
mrKaspqMgXmBeYF5gXmBspq5xQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAOFmhQKHIAQ0oS
AGFKEgAAFBVow0pFABZoUChyAENKEgBhShIAABoVaD4gSwAWaFAocgA1CIFDShIAXAiBYUoSAAAG
FmhQKHIAABEWaKo0BgBtSAAEbkgABHUIARUDagAAAAAVaFd+xgAWaFAocgBVCAEMFWhXfsYAFmhQ
KHIAAAYWaBti9gAADwNqAAAAABZoG2L2AFUIAQYWaA9AUgAABhZoqjQGAAAGFmjYaqwAAAwVaDkj
ygAWaNhqrAAAEBVoOSPKABZo2GqsADBKbQAAFwNqAAAAABZo2GqsAFUIAW1IDARzSAwEIwIIgQNq
xRIAAAYIARVoB3qhABZo2GqsAFUIAW1IDARzSAwEACpSDwAAmA8AAJkPAAD7DwAAThAAAFsQAABd
EAAAXhAAAGAQAABhEAAAYxAAAGQQAABmEAAAZxAAAIYQAACYEAAAmRAAAKESAAD3AAAAAAAAAAAA
AAAA4gAAAAAAAAAAAAAAAOIAAAAAAAAAAAAAAADdAAAAAAAAAAAAAAAA1QAAAAAAAAAAAAAAANMA
AAAAAAAAAAAAAADTAAAAAAAAAAAAAAAA0wAAAAAAAAAAAAAAANMAAAAAAAAAAAAAAADTAAAAAAAA
AAAAAAAA0wAAAAAAAAAAAAAAANMAAAAAAAAAAAAAAADTAAAAAAAAAAAAAAAAzgAAAAAAAAAAAAAA
AMcAAAAAAAAAAAAAAADTAAAAAAAAAAAAAAAAvAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAACwAAE6QAABYkAUlmAQAAAGdkyxMcAAAGMAAUpPAAZ2RpZdAAAAQwAGdkV37GAAAB
AAAABwAAAyQBYSQBZ2SqNAYAAAQAAGdk2GqsABUAAA3GCgQaA6cENAbBBwATpAAANSQBNyQBOCQB
OUQEAEgkAWdk2GqsAAAHAAADJAFhJAFnZNhqrAAAEaESAACiEgAAoxIAAKQSAAClEgAAphIAAL4A
AAAAAAAAAAAAAAC3AAAAAAAAAAAAAAAAsgAAAAAAAAAAAAAAALAAAAAAAAAAAAAAAACoAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHAAADJAFhJAFnZKo0BgAAAQAAAAQpAGdkV37GAAAG
AAATpAAAZ2QgJesAAEAAAGtkpBMAABYkARckAUlmAQAAAABUAQAClmwAAzQBCNYaAAHH/70mAAbD
JgQBAAAEAQAABAEAAAQBAAAU9gP2Jhj2AwAAGtYEAAAA/xvWBAAAAP8c1gQAAAD/HdYEAAAA/zLW
BgABCgM5ADTWBgABCgNsAGH2AwAAZjQBilQBAAAFOQAKMAExkEYBL1IgADpwV37GAB+wgy4gsMhB
IbBuBCKwbgQjkIkFJJCJBSWwAAAXsDcCGLA3AgyQ0AIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAfCwAARABkAAAAAAAAAAgAAAAAAAAAAAAAAAAA
VgS/BOgD6AMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA8ABPBKAAAAsgQK8AgAAAAB
BAAAAAoAAEMAC/AmAAAABEEBAAAABcEOAAAABgECAAAA/wEAAAgA7QB0AHUAdwBlAGIAAAAAABDw
BAAAAAAAAIBiAAfwgQoAAAYG5jX1KGGXgAY/9tQIKnZIh/8AXQoAAAEAAABEAAAAAAAdDgBuHvBV
CgAA5jX1KGGXgAY/9tQIKnZIh/+JUE5HDQoaCgAAAA1JSERSAAAASgAAAFEIAwAAAEIfwBsAAADA
UExUReIdIQgsZHm36ImZtrbk+HKStJCtyNvy/IXD7MPo+ZnX9OX1/TdjlttgaO+aoP///3mlx0d4
qtDt+qexx7XA0lOFs0VtnKbe98/Z5fzJzIC968B9jlmQw4zJ7rza7PL5/Wyp3maez6VfeNjh67je
85LP8RY6b+73/OI9ROHl7sXP3ebs8qbG3qvV77bN4G+t5PO2uJy71JJDYPv9/jZWhmSEqZ3O7e7x
9Vd4oPrf4bQrPvf7/ff3+f739nKx5v78/HXSCwIAAAABYktHRACIBR1IAAAADGNtUFBKQ21wMDcx
MgAAAANIAHO8AAAJGklEQVRYR62Ye3eiPBDGuQVFo9yjtYhS762X8kpadtu13/9bvTNJuGjb3T92
c06PQuXH80yGmQTN/WdDq0jPH3/LbFDP/wz1Mfjxl6xalTsc/DOUu/3K4us4ikLbDsNo/PqHWzWq
3Oftr+sf7yKTl2WcEM/LCHzjZrT7Da6FcrdtiztS8uwy7fV6Izksa5QXJTEfv6O1Uc9abTFia78L
GAWy1HgprT1h9tewNsrdqqOQl3S+EiTUpDiH3M4ZsawlKe23L2hXqDsNLUY867I4i6vBiWcfnD1+
2DZlJHccrww/s65Q7kAbuhwohe9duhAnjNHhsLc9QtfEwbFnqcc8xyHl4hZ2jbrTtJLGScyEOxls
ywLCge09Tuw0CMg+AIcHJy+jG9Y1yv2p/fSmq9hoRUmI8ewgCFKb8zwl8G3JbRBG3q9g1yi/0LT7
6cpHUY0kB7QcARB0OinhLA3SvV0wQgp2brPaqFfKugNNC6dxIwolAYTkHTkcrwCKnaecO5ZdtlO2
hXqnSbeba9rWzmpREhQEOUfOnpckD0rOUSPf4yQ8Nboa1JkBqTu917SfgJL2FAkoPE1NDhz4mnsO
h4ClPHAg+E28GhSLJ4iabiFcn0gdUph75bHDg05e5jiXjmOXtawaZVJJWpkahKstqtMJ8tIkdkXq
IDQoyd4LgEXMilWhHtdzhVqBLG3f2Ot0bG6CMW721TgSpNoMXEIEeJX4CvVe0AmgQNRqFQJqK1GY
AHnp4ZX9vs3HilWmYhLWObKWTOW9QhGa1KgeRF4bqJg7vHQECEbOIskyhVnbhoCBrJxLixL16LOs
8gfpiRYHQhSEV4RIIp5MHj7B55j0YSI5BMwGlsWPLRTL2KWFQovaPaB4ibOvSBsYO7vk9njB07yE
eewE+AA5L3IWharIN5hRoTA90aI2dGIRpRYJaUeTmJSbR/GfoISSY5WiGApUOTeoREHURabD86Np
D0epSdhDSjX6eQ4OBcphuWMdhCxEjZlhFGgQJzAc3N/fhwKlPTf22qTN5hESQ6KCJYO5jjFaiCKZ
0fUv0xcYh94eKNtqPDeKZrPZBv7E2CzMDqAEDh5PeBZxEgH1WhiB+1Hl7FmU0i/Gh7tx3+sn7gyY
6vDDPVDILUDZ1AiIrq9xwMcRUEtxcDPOM5fJX611IlBMXKUX7pJ5AsUzUOWWuhjwRA21YSoProc7
O7uhPBW6AuWO4d46FOZlzBD1xi6GYQSmuKEeLXu9QY1SGsTla3cze9tJ9TvzKMLuFnjeIbZXvAFq
7N+ieogqfMYK6adgjK4RtalQCzNso6w4oWNA5TGIulLlRY+6/ev52bUland3d34r9AalP4X2Fcor
shxQJLlBGSyN1tCptbsKNXzuz0L9XKvSnyJTpJUyaL3QLgEULDKuVdFeEPrPkF0/BErXn+AR3oz1
981mJmP1CeUVHqLYvI16HHlxL3gKhlAbXiVqvTvCg+NGYPA7lO/FiKKnNmqcQ2e2OohSBgFl8mMf
krzf/xq19L1RHAOquFypIqpzQXGQsdL1105ASlTWoEJRMwIZK+KNRglDVRdkVXn1SFRtsAY1agez
tTAZGfc3rzJWOxMrYqBQNjQVr/iM2ivUaLmtVC1kEbA5Cd+rFMWmU6Gs0ahnrNHgqa0qWgoUlCwr
vUYhLqpQJIVSdcxdigYRNUXUOkOHtcG8qn4jqy8eJl2XqkQNfFKqYI1bloxUqF5vhQbX8XWs4krW
6AtU9QxiC4QOIcNujQBFMVYi7rWql9ivWBVqJxdEqEqhFiacgQahUBCQqY/ZXsyBVVeGw9QXyyuI
lkKtF0OxmgFajcKmVaNAVK+LeWVT/xo1zdhEsCrUbrsdS5hC6YsjgixLqkJ/F8z2vU9BVkvVdOrR
ObIalKZFUpcMux72BSl4xbILqNUqswG18BOQ1aCg70ynfgwmO3IG1zvs1tBhoVuDDHFqMYO02rzD
kc7OQFr5R0Cd/TnIaqFED0uYd43SBinAZrLu6HoZRhEBJtTjAEhduhG1PUnoxakK8kGuslZdli1C
VfpkV9xGGGjVGmSNBxJ/E6JEbXdzevL2Mi5Q24PlC1pcrQ7RR5WiT0O0CCYhPC5XzUmIg7YyApKx
lh1nU5ycMcfzeB+yAF3I6oxVE9LXJnQhKexoOecFCFODLTaoacoK2QehJDuP3LZNOzRNUo7RIsA6
UWnCgF2labqpWNygsNGoc16YZVEUpTk+OwCCWMSqO7sLOklT+3A4hksYzlSuaZYyC1M73C+d0ShS
rO2+l1iBqIQBelutTuwS7+uVTHI6+f5lXmDDMCa4/pMmcfQ8WIVDlr3IeGnaf7bc3qE1MBfDIsjH
bYVYFB3pCVkZrVBXrFXPSPz40qs8atuwBhkxrvb9Zn3lshhZVPRpIUuwamF484efSpQIP5ai6SWm
LIOfzeVeR65FxyjrxGSZv2YJl+F95a7iPcDG00+MKd7Rx0hVKJf4gJoXTHSfa5h9LzP0dmzNqQB1
s6sVsvtGIfInlhTJrbCuWJd+NUwB6l4Ktf2qdxN0DqhTRkVNVbpkxMxbc4L7IP85mbBcrevqPY7N
IPDZ6QIlR3oU0Zfx/+zwvgJNfFKtEJudV+mfYnB5QZNtFl50bXJ7L63hnWJWvydobS3hlQkG/zL3
qVjcNMomXbsWtpUhkpInCZvVy9YW6o0xREFbzGjtUtmcTHBvJ59CRREk2nrn0947z/wCYo+sS0L9
7EaZ8Z9iDSQe/p1Um652XkmVZ47zqGCM1TbFHPhJ7dJEjmH4ZeOuSdHKMKFZxUKbSTWbhsFwnVnl
xQN8P1GVmp9nUJ45UhEv4fIyjxm8nMH5zKqZULCt6dMqn75DuTPYZTawyzzxmR83yWYY3oOI2c/x
7Y7j5kWKFMakSyntconXlMLsxnGSJPgUMzkBt9uXL1C4P2RKGcAS5kPLPWUZgpIEPv04En3j5uXg
lyhQVkI2oK4EJEptcpxiWoqacodJu71rufwG5bo7s2Q+LVpeT6CHlaSO0Q+U1nqb+i0KbvcUkTL2
mwEvZG7eQKK0GvY7lBD/uhs/RtHjePf1a9EPkKZgf0TdTvnn4x/Dwf3dR12Q/3zBb3/xYzj8pdrE
X5Lk5f8DSeDInu2IOn0AAAAASUVORK5CYIKHABYkARckAUlmAQAAAAGWAAAhdgADaAE11gUAAQOJ
BTXWBQECAykUNdYFAgMDEQ0jdgABiQUjdgECKRQjdgIDEQ06VgsAApY5AAM0ART2A8MmGPYDAAAr
1gIAAzXWBQABA4kFNdYFAQIDKRQ11gUCAwMRDTTWBgABBQAAADTWBgABCgM5AGY0AZAAFiQBFyQB
SWYBAAAAAZYAACF2AANoATXWBQABA4kFNdYFAQIDyA811gUCAwNyESN2AAGJBSN2AQLIDyN2AgNy
ETpWCwACljkAAzQBB5RjART2A8MmGPYDAAAr1gIAASvWAgEDNdYFAAEDiQU11gUBAgPIDzXWBQID
A3IRNNYGAAEFAAAANNYGAAEKAzkAZjQBpAAWJAEXJAFJZgEAAAABlgAAIXYAA2gBNdYFAAEDiQU1
1gUBAgPIDzXWBQIDA3IRI3YAAYkFI3YBAsgPI3YCA3IROlYLAAKWOQADNAEHlAwDFPYDwyYY9gMA
ACvWAgABK9YCAQEs1gMCAwE11gUAAQOJBTXWBQECA8gPNdYFAgMDchEv1gsAAwQAAAD/DAEAADTW
BgABBQAAADTWBgABCgM5AGY0AYYAFiQBFyQBSWYBAAAAAZYAACF2AANoATXWBQABA1EGNdYFAQID
IA011gUCAwNSEyN2AAFRBiN2AQIgDSN2AgNSEzpWCwACljkAAzQBB5RlART2A8MmGPYDAAA11gUA
AQNRBjXWBQECAyANNdYFAgMDUhM01gYAAQUAAAA01gYAAQoDOQBmNAFaABYkARckAUlmAQAAAAGW
AAAhdgABaAE11gUAAQPDJiN2AAHDJjpWCwACljkAAzQBB5RlART2A8MmGPYDAAA11gUAAQPDJjTW
BgABBQAAADTWBgABCgM5AGY0AXAAFiQBFyQBSWYBAAAAAZYAACF2AAJoATXWBQABA1EGNdYFAQID
ciAjdgABUQYjdgECciA6VgsAApY5AAM0AQeUZQEU9gPDJhj2AwAANdYFAAEDUQY11gUBAgNyIDTW
BgABBQAAADTWBgABCgM5AGY0AX4AFiQBFyQBSWYBAAAAAZYAACF2AAJoATXWBQABA1EGNdYFAQID
ciAjdgABUQYjdgECciA6VgsAApY5AAM0AQeUZQEU9gPDJhj2AwAANdYFAAEDUQY11gUBAgNyIC/W
CwACBAAAAP8MAQAANNYGAAEFAAAANNYGAAEKAzkAZjQBaAAWJAEXJAFJZgEAAAABlgAAIXYAAWgB
NdYFAAEDwyYjdgABwyY6VgsAApY5AAM0AQeUZQEU9gPDJhj2AwAANdYFAAEDwyYv1gsAAQEAAAD/
DAEAADTWBgABBQAAADTWBgABCgM5AGY0AXAAFiQBFyQBSWYBAAAAAZYAACF2AAJoATXWBQABA1EG
NdYFAQIDciAjdgABUQYjdgECciA6VgsAApY5AAM0AQeUZQEU9gPDJhj2AwAANdYFAAEDUQY11gUB
AgNyIDTWBgABBQAAADTWBgABCgM5AGY0AXAAFiQBFyQBSWYBAAAAAZYAACF2AAJoATXWBQABA1EG
NdYFAQIDciAjdgABUQYjdgECciA6VgsAApY5AAM0AQeUZQEU9gPDJhj2AwAANdYFAAEDUQY11gUB
AgNyIDTWBgABBQAAADTWBgABCgM5AGY0AXAAFiQBFyQBSWYBAAAAAZYAACF2AAJoATXWBQABA1EG
NdYFAQIDciAjdgABUQYjdgECciA6VgsAApY5AAM0AQeUZQEU9gPDJhj2AwAANdYFAAEDUQY11gUB
AgNyIDTWBgABBQAAADTWBgABCgM5AGY0AX4AFiQBFyQBSWYBAAAAAZYAACF2AAJoATXWBQABA1EG
NdYFAQIDciAjdgABUQYjdgECciA6VgsAApY5AAM0AQeUZQEU9gPDJhj2AwAANdYFAAEDUQY11gUB
AgNyIC/WCwACBAAAAP8MAQAANNYGAAEFAAAANNYGAAEKAzkAZjQBzwAAAEQAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA0Mnqefm6
zhGMggCqAEupCwIAAAAXAAAAEwAAAGcAaABhAHMAcwBlAG0AQABuAG8AcgB0AGUAbAAuAGMAbwBt
AAAA4Mnqefm6zhGMggCqAEupCzQAAABtAGEAaQBsAHQAbwA6AGcAaABhAHMAcwBlAG0AQABuAG8A
cgB0AGUAbAAuAGMAbwBtAAAAlAAWJAEXJAFJZgEAAAABlgAAIXYAA2gBNdYFAAEDUQY11gUBAgMq
ETXWBQIDA0gPI3YAAVEGI3YBAioRI3YCA0gPOlYLAAKWOQADNAEHlMwAFPYDwyYY9gMAADXWBQAB
A1EGNdYFAQIDKhE11gUCAwNIDy/WCwADAQAAAP8MAQAANNYGAAEFAAAANNYGAAEKAzkAZjQBaAAW
JAEXJAFJZgEAAAABlgAAIXYAAWgBNdYFAAEDwyYjdgABwyY6VgsAApY5AAM0AQeUzAAU9gPDJhj2
AwAANdYFAAEDwyYv1gsAAQEAAAD/DAEAADTWBgABBQAAADTWBgABCgM5AGY0Ad8AAABEAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
ANDJ6nn5us4RjIIAqgBLqQsCAAAAFwAAABcAAAB3AHcAdwAuAGkAdAB1AC4AaQBuAHQALwBJAFQA
VQAtAFQALwBJAFAAVABWAAAA4Mnqefm6zhGMggCqAEupCzwAAABoAHQAdABwADoALwAvAHcAdwB3
AC4AaQB0AHUALgBpAG4AdAAvAEkAVABVAC0AVAAvAEkAUABUAFYAAABtABYkARckAUlmAQAAAAGW
MwAhdgABaAE11gUAAQP2JiN2AAH2JjpWCwAClmwAAzQBFPYD9iYX9gAAABj2AwAANdYFAAEDwyYv
1gsAAQ8AAAD/BAEAADLWBgABCgM5ADTWBgABBQAAAGY0AYpUAQAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAhgJwABIAAQCcAA8ABAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAYgAAQPH/AgBiAAwAAAAAAAAA
AAAGAE4AbwByAG0AYQBsAAAAJwAAAA3GDgAEGgOnBDQGwQfAwMDAE6R4ADUkADckADgkADlEAgBI
JAAAFABDShgAX0gBBG1ICQhzSAkIdEgJBFAAAUABAAIAUAAMAAAAAAAAAAAACQBIAGUAYQBkAGkA
bgBnACAAMQAAAB8AAQAFJAEGJAEPhBoDEYTm/BOkaAFAJgBehBoDYITm/AADADUIgQA2AAJAEQAC
ADYADAAAAAAAAAAAAAkASABlAGEAZABpAG4AZwAgADIAAAAJAAIAE6TwAEAmAQAAADYAA0ARAAIA
NgAMAAAAAAAAAAAACQBIAGUAYQBkAGkAbgBnACAAMwAAAAkAAwATpKAAQCYCAAAATAAEQDEAAgBM
AAwAAAAAAAAAAAAJAEgAZQBhAGQAaQBuAGcAIAA0AAAAHwAEAA3GBwEaAwH9A8APhP0DEYQD/EAm
A16E/QNghAP8AAAAMgAFQEEAAgAyAAwAAAAAAAAAAAAJAEgAZQBhAGQAaQBuAGcAIAA1AAAABQAF
AEAmBAAAAEoABkBBAAIASgAMAAAAAAAAAAAACQBIAGUAYQBkAGkAbgBnACAANgAAAB4ABgANxgYC
/QOnBAAPhDQGEYTM+UAmBV6ENAZghMz5AAAyAAdAYQACADIADAAAAAAAAAAAAAkASABlAGEAZABp
AG4AZwAgADcAAAAFAAcAQCYGAAAAMgAIQGEAAgAyAAwAAAAAAAAAAAAJAEgAZQBhAGQAaQBuAGcA
IAA4AAAABQAIAEAmBwAAADIACUBhAAIAMgAMAAAAAAAAAAAACQBIAGUAYQBkAGkAbgBnACAAOQAA
AAUACQBAJggAAABEAEFA8v+hAEQADAFvAAAAAAAAABYARABlAGYAYQB1AGwAdAAgAFAAYQByAGEA
ZwByAGEAcABoACAARgBvAG4AdAAAAAAAVgBpQPP/swBWAAwFAAAAAAAAAAAMAFQAYQBiAGwAZQAg
AE4AbwByAG0AYQBsAAAAIAA6VgsAF/YDAAA01gYAAQUDAAA01gYAAQoDbABh9gMAAAIACwAAACgA
awD0/8EAKAAABQAAAAAAAAAABwBOAG8AIABMAGkAcwB0AAAAAgAMAAAAAABUAP5PAQACAFQADAAA
AAAAAAAAABAAQQBuAG4AZQB4AF8ATgBvACAAJgAgAHQAaQB0AGwAZQAAABIADwADJAEFJAEGJAET
pOABYSQBBwA1CIFDShwAADYA/k+iAAEBNgAMAAAAAAAAAAAABwBBAHAAcABfAGQAZQBmAAAADwA1
CIFPSgAAUUoAAGtI5AQAJgD+T6IAEQEmAAwAAAAAAAAAAAAHAEEAcABwAF8AcgBlAGYAAAAAAEIA
/k/xAAIAQgAMAAAAAAAAAAAAEwBBAHAAcABlAG4AZABpAHgAXwBOAG8AIAAmACAAdABpAHQAbABl
AAAAAgASAAAANgD+T6IAMQE2AAwAAAAAAAAAAAAHAEEAcgB0AF8AZABlAGYAAAAPADUIgU9KAABR
SgAAa0jkBABEAP5PAQACAEQADAAAAAAAAAAAAAsAQQByAHQAXwBoAGUAYQBkAGkAbgBnAAAADAAU
AAMkAROk4AFhJAEHADUIgUNKHAAAQAD+TwEAAgBAAAwAAAAAAAAAAAAGAEEAcgB0AF8ATgBvAAAA
EgAVAAMkAQUkAQYkAROk4AFhJAEHADsIgUNKHAAAJgD+T6IAYQEmAAwAAAAAAAAAAAAHAEEAcgB0
AF8AcgBlAGYAAAAAAEYA/k8BAAIARgAMAAAAAAAAAAAACQBBAHIAdABfAHQAaQB0AGwAZQAAABIA
FwADJAEFJAEGJAETpPAAYSQBBwA1CIFDShwAAHAA/k8BAIIBcAAEAAAAAAAAAAAABQBBAFMATgAu
ADEAAAAxABgADcYoBBoDpwQ0BsEHCjcCbgSlBtwIEwtKDYEPuBHvEyYWAAAAAAAAAAAAABOkAAAA
GgA1CIFDShQAT0oDAFFKAwBtSAAEbkgABHUIAToA/k8BAAIAOgAMAAAAAAAAAAAABABDAGEAbABs
AAAAFAAZAAUkAQYkAQ+EGgMTpKAAXoQaAwMANgiBAFYA/k8BAAIAVgAMAAAAAAAAAAAABwBDAGgA
YQBwAF8ATgBvAAAAIwAaAAMkAQUkAQYkAQ3GDgAEGgOnBDQGwQcAAAAAE6TgAWEkAQAKADUIgTsI
gUNKHABIAP5PAQACAEgADAAAAAAAAAAAAAoAQwBoAGEAcABfAHQAaQB0AGwAZQAAABIAGwADJAEF
JAEGJAETpPAAYSQBBwA1CIFDShwAAD4AKgCiAMEBPgAMAQAAAAAAAAAAEQBFAG4AZABuAG8AdABl
ACAAUgBlAGYAZQByAGUAbgBjAGUAAAADAEgqAQBAAP5PAQDSAUAADAAAAAAAAAAAAAgAZQBuAHUA
bQBsAGUAdgAxAAAAFgAdAA+EGgMRhOb8E6RQAF6EGgNghOb8AAA8AP5P0QHiATwADAAAAAAAAAAA
AAgAZQBuAHUAbQBsAGUAdgAyAAAAEgAeAA+EpwQRhHP+XoSnBGCEc/4AADQA/k/hAfIBNAAMAAAA
AAAAAAAACABlAG4AdQBtAGwAZQB2ADMAAAAKAB8AD4Q0Bl6ENAYAAD4A/k8BAAICPgAMAAAAAAAA
AAAACABFAHEAdQBhAHQAaQBvAG4AAAATACAADcYOA6cENAbBBwLUEqclwcIAAABcAP5PAQASAlwA
DAAAAAAAAAAAAA8ARQBxAHUAYQB0AGkAbwBuAF8AbABlAGcAZQBuAGQAAAAkACEADcYLAxoDpwQ0
BgEWB8IPhMEHEYQ/+BOkUABehMEHYIQ/+AAAPAD+TwEAAgA8AAwAAAAAAAAAAAAGAEYAaQBnAHUA
cgBlAAAAFgAiAAMkAQUkAQYkAROk8AAUpHgAYSQBAABWAP5PAQAyAlYADAAAAAAAAAAAAA0ARgBp
AGcAdQByAGUAXwBsAGUAZwBlAG4AZAAAAB0AIwAFJAEGJAENxgoEGgOnBDQGwQcAE6QUABSkFAAA
BABDShIAVAD+TwEAAgBUAAwAAAAAAAAAAAARAEYAaQBnAHUAcgBlAF8ATgBvACAAJgAgAHQAaQB0
AGwAZQAAABMAJAADJAEFJAETpPAAFKR4AGEkAQADADUIgQBMAP5PAQACAEwADAAAAAAAAAAAAAwA
RgBpAGcAdQByAGUAXwBOAG8AXwBCAFIAAAAWACUAAyQBBSQBBiQBE6TgARSkeABhJAEDADsIgQBQ
AP5PAQACAFAADAAAAAAAAAAAAA4AVABhAGIAbABlAF8AdABpAHQAbABlAF8AQgBSAAAAFgAmAAMk
AQUkAQYkAROkAAAUpHgAYSQBAwA1CIEAQgD+T2ECAgBCAAwAAAAAAAAAAAAPAEYAaQBnAHUAcgBl
AF8AdABpAHQAbABlAF8AQgBSAAAACQAnAAYkABSk4AEAAABWAP5PAQACAFYADAAAAAAAAAAAABQA
RgBpAGcAdQByAGUAXwB3AGkAdABoAG8AdQB0AF8AdABpAHQAbABlAAAAEwAoAAMkAQUkAROk8AAU
pHgAYSQBAAAAUgAgQAEAkgJSAAQAAAAAAAAAAAAGAEYAbwBvAHQAZQByAAAAGQApAA3GEAQaA6cE
NAbBBwJCF6clAAITpAAAABIAOwiBQ0oQAG1IAARuSAAEdQgBVgD+T5ECogJWAAwAAAAAAAAAAAAL
AEYAaQByAHMAdABGAG8AbwB0AGUAcgAAAB8AKgANxgYCQhenJQATpCgANSQBNyQBOCQBOUQEAEgk
AQAGADsIgXUIAFAA/k8BALICUAAMAAAAAAAAAAAACQBGAG8AbwB0AGUAcgBfAFEAUAAAABwAKwAN
xhMEGgOnBDQGwQcDiwNVIqclwMLCE6QAAAcANQiBQ0oWAABEACYAogDBAkQADAEAAAAAAAAAABIA
RgBvAG8AdABuAG8AdABlACAAUgBlAGYAZQByAGUAbgBjAGUAAAAIAENKEgBFSAYAOgD+TwEA0gI6
AAwAAAAAAAAAAAAEAE4AbwB0AGUAAAAXAC0ADcYOAAQaA6cENAbBBwAAAAATpFAAAAAAUgAdANEC
4gJSAAwBAAAAAAAAAAANAEYAbwBvAHQAbgBvAHQAZQAgAFQAZQB4AHQAAAAdAC4ABSQBDcYFAAH/
AAAPhP8AEYQB/16E/wBghAH/AAAAUAD+T4EB8gJQAAQAAAAAAAAAAAAGAEYAbwByAG0AYQBsAAAA
JQAvAA3GIAAKNwJuBKUG3AgTC0oNgQ+4Ee8TJhbAwMDAwMDAwMDAAAMANQiBAEQAH0ABAAIDRAAM
AAAAAAAAAAAABgBIAGUAYQBkAGUAcgAAABkAMAADJAENxgoEGgOnBDQGwQcAE6QAAGEkAQAEAENK
EgA6AP5PAQACADoADAAAAAAAAAAAAAkASABlAGEAZABpAG4AZwBfAGIAAAAJADEABiQBE6SgAAAD
ADUIgQA6AP5PAQACADoADAAAAAAAAAAAAAkASABlAGEAZABpAG4AZwBfAGkAAAAJADIABiQBE6Sg
AAADADYIgQAqAAoAAQACACoADAEAAAAAAAAAAAcASQBuAGQAZQB4ACAAMQAAAAIAMwAAADIACwAB
AAIAMgAMAQAAAAAAAAAABwBJAG4AZABlAHgAIAAyAAAACgA0AA+EGwFehBsBAAAyAAwAAQACADIA
DAEAAAAAAAAAAAcASQBuAGQAZQB4ACAAMwAAAAoANQAPhDYCXoQ2AgAARAD+TwEAAgBEAAwAAAAA
AAAAAAASAE4AbwByAG0AYQBsAF8AYQBmAHQAZQByAF8AdABpAHQAbABlAAAABgA2ABOkaAEAAC4A
KUCiAHEDLgAMAAAAAAAAAAAACwBQAGEAZwBlACAATgB1AG0AYgBlAHIAAAAAAEYA/k8BAAIARgAM
AAAAAAAAAAAABwBQAGEAcgB0AF8ATgBvAAAAFgA4AAMkAQUkAQYkAROk4AEUpFAAYSQBBwA7CIFD
ShwAADwA/k8BAAIAPAAMAAAAAAAAAAAACABQAGEAcgB0AF8AcgBlAGYAAAASADkAAyQBBSQBBiQB
E6QYAWEkAQAATAD+TwEAYgNMAAwAAAAAAAAAAAAKAFAAYQByAHQAXwB0AGkAdABsAGUAAAAWADoA
AyQBBSQBBiQBE6TwABSkGAFhJAEHADUIgUNKHAAATgD+TwEAYgNOAAwAAAAAAAAAAAAIAFIAZQBj
AF8AZABhAHQAZQAAABsAOwADJAIFJAEGJAENxgoEGgOnBDQGwQcAYSQCAAcANgiBQ0oWAAA2AP5P
sQNiAzYADAAAAAAAAAAAAA0AUQB1AGUAcwB0AGkAbwBuAF8AZABhAHQAZQAAAAIAPAAAADoA/k8B
AAIAOgAMAAAAAAAAAAAABgBSAGUAYwBfAE4AbwAAAAwAPQAFJAEGJAETpAAABwA1CIFDShwAADIA
/k/RAwIAMgAMAAAAAAAAAAAACwBRAHUAZQBzAHQAaQBvAG4AXwBOAG8AAAACAD4AAABGAP5PAQAC
AEYADAAAAAAAAAAAAAkAUgBlAGMAXwBOAG8AXwBCAFIAAAASAD8AAyQBBSQBBiQBE6TgAWEkAQcA
OwiBQ0ocAAA4AP5P8QMCADgADAAAAAAAAAAAAA4AUQB1AGUAcwB0AGkAbwBuAF8ATgBvAF8AQgBS
AAAAAgBAAAAASAD+TwEAsgNIAAwAAAAAAAAAAAAHAFIAZQBjAF8AcgBlAGYAAAAbAEEAAyQBBSQB
BiQBDcYKBBoDpwQ0BsEHAGEkAQADADYIgQA0AP5PEQTCAzQADAAAAAAAAAAAAAwAUQB1AGUAcwB0
AGkAbwBuAF8AcgBlAGYAAAACAEIAAABGAP5PAQBiA0YADAAAAAAAAAAAAAkAUgBlAGMAXwB0AGkA
dABsAGUAAAASAEMAAyQBBSQBBiQBE6RoAWEkAQcANQiBQ0ocAAA4AP5PMQQiBDgADAAAAAAAAAAA
AA4AUQB1AGUAcwB0AGkAbwBuAF8AdABpAHQAbABlAAAAAgBEAAAAKgD+T6IAUQQqAAwAAAAAAAAA
AAAHAFIAZQBjAF8AZABlAGYAAAADADUIgQA8AP5PAQBiBDwADAAAAAAAAAAAAAgAUgBlAGYAXwB0
AGUAeAB0AAAAEgBGAA+EGgMRhOb8XoQaA2CE5vwAADwA/k8BAGIEPAAMAAAAAAAAAAAACQBSAGUA
ZgBfAHQAaQB0AGwAZQAAAAwARwADJAETpOABYSQBAwA1CIEALAD+T7EDYgMsAAwAAAAAAAAAAAAI
AFIAZQBwAF8AZABhAHQAZQAAAAIASAAAACgA/k/RAwIAKAAMAAAAAAAAAAAABgBSAGUAcABfAE4A
bwAAAAIASQAAAC4A/k/xAwIALgAMAAAAAAAAAAAACQBSAGUAcABfAE4AbwBfAEIAUgAAAAIASgAA
ACoA/k8RBIIEKgAMAAAAAAAAAAAABwBSAGUAcABfAHIAZQBmAAAAAgBLAAAALgD+TzEEsgQuAAwA
AAAAAAAAAAAJAFIAZQBwAF8AdABpAHQAbABlAAAAAgBMAAAALAD+T7EDYgMsAAwAAAAAAAAAAAAI
AFIAZQBzAF8AZABhAHQAZQAAAAIATQAAADYA/k+iAOEENgAMAAAAAAAAAAAABwBSAGUAcwBfAGQA
ZQBmAAAADwA1CIFPSgAAUUoAAGtI5AQAKAD+T9EDAgAoAAwAAAAAAAAAAAAGAFIAZQBzAF8ATgBv
AAAAAgBPAAAALgD+T/EDAgAuAAwAAAAAAAAAAAAJAFIAZQBzAF8ATgBvAF8AQgBSAAAAAgBQAAAA
KgD+TxEE0gQqAAwAAAAAAAAAAAAHAFIAZQBzAF8AcgBlAGYAAAACAFEAAAAuAP5PMQQSBS4ADAAA
AAAAAAAAAAkAUgBlAHMAXwB0AGkAdABsAGUAAAACAFIAAABKAP5PAQACAEoADAAAAAAAAAAAAAkA
UwBlAGMAdABpAG8AbgBfADEAAAAZAFMAAyQBDcYKBBoDpwQ0BsEHABOkcAJhJAEAAwA1CIEASgD+
TwEAAgBKAAwAAAAAAAAAAAAJAFMAZQBjAHQAaQBvAG4AXwAyAAAAGQBUAAMkAQ3GCgQaA6cENAbB
BwATpPAAYSQBAAMANgiBAEwA/k8BAAIATAAMAAAAAAAAAAAACgBTAGUAYwB0AGkAbwBuAF8ATgBv
AAAAFgBVAAMkAQUkAQYkAROk4AEUpFAAYSQBBwA7CIFDShwAAFIA/k8BAGIDUgAMAAAAAAAAAAAA
DQBTAGUAYwB0AGkAbwBuAF8AdABpAHQAbABlAAAAFgBWAAMkAQUkAQYkAROk4AEUpBgBYSQBBwA1
CIFDShwAAD4A/k8BAGIDPgAMAAAAAAAAAAAABgBTAG8AdQByAGMAZQAAABAAVwADJAETpEgDFKTI
AGEkAQcANQiBQ0ocAABYAP5PkQKCBVgADAAAAAAAAAAAAA4AUwBwAGUAYwBpAGEAbAAgAEYAbwBv
AHQAZQByAAAAHABYAAMkAw3GEQAFNwJuBKUG3AgTC8DAwMDAYSQDBgA7CIF1CAA4AP5PogCRBTgA
DAAAAAAAAAAAAAoAVABhAGIAbABlAF8AZgByAGUAcQAAAAwANQiBQioAcGgAAAD/fAD+TwEAAgB8
AAwAAAAAAAAAAAAKAFQAYQBiAGwAZQBfAGgAZQBhAGQAAABFAFoAAyQBBiQBDcYvAxoDpwQ0Bg0c
ATcCUwNuBIoFpQbcCPgJEwsvDEoNZg6BD8DAwMDAwMDAwMDAwMATpFAAFKRQAGEkAQAHADUIgUNK
FgAAbgD+TwEAsgVuAAwAAAAAAAAAAAAMAFQAYQBiAGwAZQBfAGwAZQBnAGUAbgBkAAAAOABbAA3G
LwMaA6cENAYNHAE3AlMDbgSKBaUG3Aj4CRMLLwxKDWYOgQ/AwMDAwMDAwMDAwMDAFKQoAAQAQ0oW
AFQA/k8BAKIFVAAMAAAAAAAAAAAAEABUAGEAYgBsAGUAXwBOAG8AIAAmACAAdABpAHQAbABlAAAA
FgBcAAMkAQUkAQYkAROkaAEUpHgAYSQBAwA1CIEASAD+TwEAYgJIAAwAAAAAAAAAAAALAFQAYQBi
AGwAZQBfAE4AbwBfAEIAUgAAABMAXQADJAEGJAETpDACFKR4AGEkAQADADsIgQBAAP5PAQBiAkAA
DAAAAAAAAAAAAAkAVABhAGIAbABlAF8AcgBlAGYAAAATAF4AAyQBBiQBE6QAABSkeABhJAEAAABy
AP5PAQDyBXIADAAAAAAAAAAAAAoAVABhAGIAbABlAF8AdABlAHgAdAAAAD8AXwANxjIDGgOnBDQG
DhwBNwJTA24EigWlBsEH3Aj4CRMLLwxKDWYOgQ9AQEBAQEBAQEBAQEBAQBOkKAAUpCgAAAQAQ0oW
AFQA/k9xBQIAVAAMAAAAAAAAAAAABwBUAGkAdABsAGUAIAAxAAAAJgBgAA3GGQQaA6cENAbBBwU3
Am4EpQbcCBMLwMDAwMATpPAAFKQAAAYANQiBOwiBKgD+TwEGAgAqAAwAAAAAAAAAAAAHAFQAaQB0
AGwAZQAgADIAAAACAGEAAAAuAP5PEQYCAC4ADAAAAAAAAAAAAAcAVABpAHQAbABlACAAMwAAAAIA
YgADADsIgQAuAP5PIQYSAC4ADAAAAAAAAAAAAAcAVABpAHQAbABlACAANAAAAAIAYwADADUIgQA6
AP5PAQBSBjoADAAAAAAAAAAAAAUAdABvAGMAIAAwAAAAEgBkAA3GDQQaA6cENAbBBwGnJQIDADUI
gQBcABMAAQBSBlwADAEAAAAAAAAAAAUAVABPAEMAIAAxAAAANwBlAAUkAQ3GEwQaA6cENAbBBwPE
A1UipyUACAIOhFMDD4SoAhGEWP0TpPAAXYRTA16EqAJghFj9AAAAOgAUAFEGYgY6AAwBAAAAAAAA
AAAFAFQATwBDACAAMgAAABYAZgAPhPsFEYSt/BOkUABehPsFYISt/AAAJgAVAGEGcgYmAAwBAAAA
AAAAAAAFAFQATwBDACAAMwAAAAIAZwAAACYAFgBxBoIGJgAMAQAAAAAAAAAABQBUAE8AQwAgADQA
AAACAGgAAAAmABcAgQaSBiYADAEAAAAAAAAAAAUAVABPAEMAIAA1AAAAAgBpAAAAJgAYAIEGogYm
AAwBAAAAAAAAAAAFAFQATwBDACAANgAAAAIAagAAACYAGQCBBrIGJgAMAQAAAAAAAAAABQBUAE8A
QwAgADcAAAACAGsAAAAmABoAgQbCBiYADAEAAAAAAAAAAAUAVABPAEMAIAA4AAAAAgBsAAAANgBV
QKIA0QY2AAwAAAC1IAcAAAAJAEgAeQBwAGUAcgBsAGkAbgBrAAAADAA+KgFCKgJwaAAA/wB+AP5P
AQDiBn4ADQAAAAZnHwAAABQAIABaAGMAaABuACAAWgBjAGgAbgAgAEMAaABhAHIAIABDAGgAYQBy
AAAAHABuAAMkAwUkAQYkAQckAQ3GBQABaAEGMSQAYSQDIABLSAIAT0oEAFBKBQBRSgQAbUgJBG5I
BAhzSAkEdEgECJIA/m8BAPIGkgANAAoAqjQGAAAAHgAgAFoAYwBoAG4AIABaAGMAaABuACAAQwBo
AGEAcgAgAEMAaABhAHIAIABaAGMAaABuACAAWgBjAGgAbgAAABwAbwADJAMFJAEGJAEHJAENxgUA
AWgBBjEkAGEkAyAAS0gCAE9KBABQSgUAUUoEAG1ICQRuSAQIc0gJBHRIBAgAAAAApgoAAAgAADQA
AAAA/////wAAAABJAQAASgEAAKcKAAB7iQAwADAAAAAAAAACAAAAAQAAAAEAAACIkJUH/////wAw
AADGmAEAxpgBAAAAAAAAAAAAQwAgB5oAAAAAMAAAAAAAAACAAAAAgAAAAAAAAAAAAAcAAAAAAgAA
AAMAAAApAAAAPQAAAD4AAAA/AAAAaAAAAH8AAACPAAAAkAAAAJEAAACSAAAAnwAAAKAAAACqAAAA
qwAAAOIAAADjAAAA/gAAAP8AAAAHAQAAHwEAACABAAAnAQAARwEAAEgBAABJAQAASgEAAE4BAABi
AQAAYwEAAG0BAAB1AQAAdgEAAHsBAACSAQAAkwEAAJ0BAACtAQAArgEAALcBAADnAQAA6AEAAP8B
AABEAgAARQIAAJ0CAACeAgAArgMAADoGAADDBgAAUgcAAJgHAACZBwAA+wcAAE4IAABbCAAAXQgA
AF4IAABgCAAAYQgAAGMIAABkCAAAZggAAGcIAACGCAAAmAgAAJkIAAChCgAAogoAAKMKAACkCgAA
pwoAAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAAACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAA
ACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAA
IACZAAAAADAAAAAAAAAAgAAAAIABAADUAAAAACAAqSAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAg
AKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAAACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAA
qQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAJkAAAAAMAAAAAAAAACAAAAAgAEAANQAAAAAIACp
IAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAqSAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkA
AAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACZAAAAADAAAAAAAAAAgAAAAIABAADUAAAAACAAqQAA
AAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACpAAAA
ADAAAAAAAAAAgAAAAIABAADQAAAAACAAmQAAAAAwAAAAAAAAAIAAAACAAQAA1AAAAAAgAKkAAAAA
MAAAAAAAAACAAAAAgAEAANAAAAAAIACZAAAAADAAAAAAAAAAgAAAAIABAADUAAAAACAAqQAAAAAw
AAAAAAAAAIAAAACAAQAA0AAAAAAgAKkAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIACZAAAAADAA
AAAAAAAAgAAAAIABAADUAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAKkAAAAAMAAA
AAAAAACAAAAAgAEAANAAAAAAIACZAAAAADAAAAAAAAAAgAAAAIABAADUAAAAACAAqQAAAAAwAAAA
AAAAAIAAAACAAQAA0AAAAAAgAJkAAAAAMAAAAAAAAACAAAAAgAEAANQAAAAAIACpAAAAADAAAAAA
AAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAJkAAAAAMAAAAAAA
AACAAAAAgAEAANQAAAAAIACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAA
AIAAAACAAQAA0AAAAAAgAJkAAAAAMAAAAAAAAACAAAAAgAEAANQAAAAAIACpAAAAADAAAAAAAAAA
gAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAJkAAAAAMAAAAAAAAACA
AAAAgAEAANQAAAAAIACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAA
AACAAQAA0AAAAAAgAJkAAAAAMAAAAAAAAACAAAAAgAEAANQAAAAAIACpAAAAADAAAAAAAAAAgAAA
AIABAADQAAAAACAAqQAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAAAKkAAAAAMAAAAAAAAACAAAAA
gAEAANAAAAAAIACpAAAAADAAAAAAAAAAgAAAAIABAADQAAAAAAAAqQAAAAAwAAAAAAAAAIAAAACA
AQAA0AAAAAAgAJkAAAAAMAAAAAAAAACAAAAAgAEAANQAAAAAIACpAAAAADAAAAAAAAAAgAAAAIAB
AADQAAAAACAAmQAAAAAwAAAAAAAAAIAAAACAAQAA1AAAAAAgAJgAAAAAMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYAAAAADAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAAAAwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJgAAAAAMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAADAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmAAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAAMAAAAAAAAACAAAAAgAAAAAAA
AAAAAACYAAAAADAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAAAAwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAZhAAAAAMAAAAAAAAACAAAAAgAAAAAAAAAAAgAdoiwAwADAAAAAAAAABAAAAAAAAAAAAAAAA
ALgHmEAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAACAB2iLADAAMAAAAAAAAAEAAAAAAAAAAAAAAAAA
uAeYQAAAADAAAAAAAAAAgAAAAIAAAAAAAAAAAIAHaIsAMAAwAAAAAAAAAQAAAAAAAAAAAAAAAAC4
B5hAAAAAMAAAAAAAAACAAAAAgAAAAAAAAAAAgAdoiwAwADAAAAAAAAABAAAAAAAAAAAAAAAAALgH
mEAAADAwAAAAAAAAAIAAAACAAAAAAAAAAAAAB5hAAAAwMAAAAAAAAACAAAAAgAAAAAAAAAAAAACY
QAAAADAAAAAAAAAAgAAAAIAAAAAAAAAAAIAHqUAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAJlA
AAAAMAAAAAAAAACAAAAAgAEAANQAAAAAIACYQAAAADAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmEAA
ACkwAAAAAAAAAIAAAACAAAAAAAAAAAAAB2iLADAAMAAAAAAAAAEAAAAAAAAAAAAAANgXuAcAAAAA
AgAAAAMAAAApAAAAPQAAAD4AAAA/AAAAaAAAAH8AAACPAAAAkAAAAJEAAACSAAAAnwAAAKAAAACq
AAAAqwAAAOIAAADjAAAA/gAAAP8AAAAHAQAAHwEAACABAAAnAQAARwEAAEgBAABJAQAASgEAAE4B
AABiAQAAYwEAAG0BAAB1AQAAdgEAAHsBAACSAQAAkwEAAJ0BAACtAQAArgEAALcBAADnAQAA6AEA
AP8BAABEAgAARQIAAJ0CAACeAgAArgMAADoGAADDBgAAUgcAAJgHAACZBwAA+wcAAE4IAABbCAAA
XQgAAGAIAABjCAAAZggAAIYIAACYCAAAmQgAAKEKAACiCgAAowoAAKQKAACnCgAAqQAAAAAwAAAA
AAAAAIAAAACAAQAAqAAAAAAAAakAAAAAMAAAAAAAAACAAAAAgAEAAKgAAAAAIAGpAAAAADAAAAAA
AAAAgAAAAIABAACoAAAAACABqQAAAAAwAAAAAAAAAIAAAACAAQAAqAAAAAAgAZkAAAAAMAAAAAAA
AACAAAAAgAEAAKwAAAAAIAGpIAAAADAAAAAAAAAAgAAAAIABAACoAAAAACABqQAAAAAwAAAAAAAA
AIAAAACAAQAAqAAAAAAAAakAAAAAMAAAAAAAAACAAAAAgAEAAKgAAAAAIAGpAAAAADAAAAAAAAAA
gAAAAIABAACoAAAAACABmQAAAAAwAAAAAAAAAIAAAACAAQAArAAAAAAgAakgAAAAMAAAAAAAAACA
AAAAgAEAAKgAAAAAIAGpIAAAADAAAAAAAAAAgAAAAIABAACoAAAAACABqQAAAAAwAAAAAAAAAIAA
AACAAQAAqAAAAAAgAZkAAAAAMAAAAAAAAACAAAAAgAEAAKwAAAAAIAGpAAAAADAAAAAAAAAAgAAA
AIABAACoAAAAACABqQAAAAAwAAAAAAAAAIAAAACAAQAAqAAAAAAgAakAAAAAMAAAAAAAAACAAAAA
gAEAAKgAAAAAIAGZAAAAADAAAAAAAAAAgAAAAIABAACsAAAAACABqwAAAAAwAAAAAAAAAIAAAACA
AQAAqAAAAAAgB5kAAAAAMAAAAAAAAACAAAAAgAEAAKwAAAAAIAGpAAAAADAAAAAAAAAAgAAAAIAB
AACoAAAAACABqQAAAAAwAAAAAAAAAIAAAACAAQAAqAAAAAAgAZkAAAAAMAAAAAAAAACAAAAAgAEA
AKwAAAAAIAGpAAAAADAAAAAAAAAAgAAAAIABAACoAAAAACABqQAAAAAwAAAAAAAAAIAAAACAAQAA
qAAAAAAgAZkAAAAAMAAAAAAAAACAAAAAgAEAAKwAAAAAIAGpAAAAADAAAAAAAAAAgAAAAIABAACo
AAAAACABmQAAAAAwAAAAAAAAAIAAAACAAQAArAAAAAAgAakAAAAAMAAAAAAAAACAAAAAgAEAAKgA
AAAAIAGpAAAAADAAAAAAAAAAgAAAAIABAACoAAAAACABmQAAAAAwAAAAAAAAAIAAAACAAQAArAAA
AAAgAakAAAAAMAAAAAAAAACAAAAAgAEAAKgAAAAAIAGpAAAAADAAAAAAAAAAgAAAAIABAACoAAAA
ACABmQAAAAAwAAAAAAAAAIAAAACAAQAArAAAAAAgAakAAAAAMAAAAAAAAACAAAAAgAEAAKgAAAAA
IAGpAAAAADAAAAAAAAAAgAAAAIABAACoAAAAACABmQAAAAAwAAAAAAAAAIAAAACAAQAArAAAAAAg
AakAAAAAMAAAAAAAAACAAAAAgAEAAKgAAAAAIAGpAAAAADAAAAAAAAAAgAAAAIABAACoAAAAACAB
mQAAAAAwAAAAAAAAAIAAAACAAQAArAAAAAAgAalAAAAAMAAAAAAAAACAAAAAgAEAAKgAAAAAIAGp
QAAAADAAAAAAAAAAgAAAAIABAADQAAAAAAABqUAAAAAwAAAAAAAAAIAAAACAAQAA0AAAAAAgAalA
AAAAMAAAAAAAAACAAAAAgAEAANAAAAAAAAGpQAAAADAAAAAAAAAAgAAAAIABAADQAAAAACABmUAA
AAAwAAAAAAAAAIAAAACAAQAArAAAAAAgAasAAAAAMAAAAAAAAACAAAAAgAEAAKgAAAAAIAeZAAAA
ADAAAAAAAAAAgAAAAIABAACsAAAAACABmgAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAB5oAAAAA
MAAAAAAAAACAAAAAgAAAAAAAAAAAAAeYQAAAADAAAAAAAAAAgAAAAIAAAAAAAAAAAAABmEAAAAAw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAZgAAAAAMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAADAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAAMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACaAAAAADAAAAAAAAAAgAAAAIAAAAAAAAAAAAAHmkAAAAAwAAAA
AAAAAIAAAACAAAAAAAAAAAAAB5pAAAAAMAAAAAAAAACAAAAAgAAAAAAAAAAAAAeaQAAAADAAAAAA
AAAAgAAAAIAAAAAAAAAAAIAHmkAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAACAB5pAAAAwMAAAAAAA
AACAAAAAgAAAAAAAAAAAAAeaQAAAMDAAAAAAAAAAgAAAAIAAAAAAAAAAAAAHmkAAAAAwAAAAAAAA
AIAAAACAAAAAAAAAAACAB6tAAAAAMAAAAAAAAACAAAAAgAEAANAAAAAAIAebQAAAADAAAAAAAAAA
gAAAAIABAAAEAAAAACAHmkAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAB5pAAAApMAAAAAAAAACA
AAAAgAAAAAAAAAAAAAcKAAAAADAAAAAAAAAAAAAAAAAGMAIAAAAAAAAHAAAAAAMAAAAGAAAABgAA
AAkAAAAMAAAADAAAAAwAAAA+AAAAPgAAAD4AAAA+AAAASQIAAEwCAAAABgAArAgAAAYKAAB+DwAA
phIAAAoAAAAPAAAAFQAAABcAAAAABgAAjwgAAJ8IAADiCAAAHwkAAEkJAAB1CQAArQkAAEQKAABS
DwAAoRIAAKYSAAALAAAADQAAAA4AAAAQAAAAEQAAABIAAAATAAAAFAAAABYAAAAYAAAAGQAAAAAG
AAClEgAADAAAAAYCAAAvAgAAQgIAAFIHAAB/BwAAlgcAAKYKAAATWBT/FYQTWBT/FYQOAAAAJQAA
ACcAAABMAgAAEyEU/5WADwAA8EAAAAAAAAbwIAAAAAIMAAADAAAAAgAAAAIAAAACAAAAAgAAAAEA
AAABAAAAQAAe8RAAAAD//wAAAAD/AICAgAD3AAAQAA8AAvCSAAAAIAAI8AgAAAABAAAAAQQAAA8A
A/AwAAAADwAE8CgAAAABAAnwEAAAAAAAAAAAAAAAAAAAAAAAAAACAArwCAAAAAAEAAAFAAAADwAE
8EIAAAASAArwCAAAAAEEAAAADgAAUwAL8B4AAAC/AQAAEADLAQAAAAD/AQAACAAEAwkAAAA/AwEA
AQAAABHwBAAAAAEAAAABDwAC8EgAAAAQAAjwCAAAAAEAAAAACAAADwAD8DAAAAAPAATwKAAAAAEA
CfAQAAAAAAAAAAAAAAAAAAAAAAAAAAIACvAIAAAAAAgAAAUAAAD//woAAAAIAGQAdABhAGIAbABl
AGEAdQAKAEkAbgBzAGUAcgB0AEwAbwBnAG8ABABkAG4AdQBtAAUAZABkAGEAdABlAAcAZABvAHIA
bABhAG4AZwAIAGQAbQBlAGUAdABpAG4AZwAJAGQAYgBsAHUAZQBwAGkAbgBrAAYAZAB0AGkAdABs
AGUABwBkAHMAbwB1AHIAYwBlAAcAZAB0AGkAdABsAGUAMQAAAAAAAAAAAAAAAAA+AAAAkAAAAKAA
AACgAAAA4wAAAP8AAAAgAQAApwoAAAgAAAAAAAAAAQACgwIAAoMDAAKDBAACgwUAAYIGAACBBwAB
ggkAAYIAAAAAPgAAAJAAAACgAAAA4wAAAOMAAAD/AAAAIAEAAEgBAABIAQAApwoAAP//BgAAAAYA
YGslABAAAQB0pRgABgBhayUAEQABAPSVGAAGAGJrJQAQAAEA9KIYAAYAY2slABAAAQC0qxgABgBk
ayUAEQABAOxlZQoGAGVrJQARAAEAbK5mCiMAAADAAAAAwAAAAD0IAAA9CAAAQwgAAKcKAAAAAAAA
AQABAAAAAgACAAAAAgAEAAAAAgADAAAAAgAFAAAAAgAoAAAAzQAAAM0AAABBCAAASwgAAEsIAACn
CgAAAAAAAAEAAAACAAAABAABAAMAAAAFAAAAAwAAADkAAAAGAAAAKoB1cm46c2NoZW1hcy1taWNy
b3NvZnQtY29tOm9mZmljZTpzbWFydHRhZ3MFgHBsYWNlAIBCAAAAAQAAACqAdXJuOnNjaGVtYXMt
bWljcm9zb2Z0LWNvbTpvZmZpY2U6c21hcnR0YWdzDoBjb3VudHJ5LXJlZ2lvbgCAOAAAAAUAAAAq
gHVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOnNtYXJ0dGFncwSAQ2l0eQCADAAAATR3
tQ0AAAAABgAAAAAABQAAAAAABgAAAAAABgAAAAAABQAAAAAAAQAAAAAAAAAAALcBAAC+AQAAvwEA
AMYBAADHAQAAzQEAAM4BAADWAQAA2AEAAN4BAADgAQAA5gEAAFsIAABbCAAAXQgAAF0IAABeCAAA
XggAAGAIAABhCAAAYwgAAGQIAABmCAAAZwgAAKQKAACnCgAABwAcAAcAHAAHABwABwAcAAcAHAAH
ABwABwAEAAcABAACAAQABwAEAAcABAAHAAQABwACAAAAAABbCAAAWwgAAF0IAABdCAAAXggAAF4I
AABgCAAAYQgAAGMIAABkCAAAZggAAGcIAACQCAAAlQgAAKQKAACnCgAABwAEAAcABAACAAQABwAE
AAcABAAHAAQABwAzAAcAAgAAAAAAAwAAAD8AAAB/AAAAqwAAAOMAAAD9AAAA/wAAAAcBAAAgAQAA
twEAAOgBAABFAgAATggAAFoIAABbCAAAWwgAAF0IAABdCAAAXggAAF4IAABgCAAAYQgAAGMIAABk
CAAAZggAAGcIAABpCAAAgwgAAJcIAACkCgAApwoAAAcABQAHAAUABwAFAAcABQAHAAUABwAFAAcA
BQAHAAQABwAEAAIABAAHAAQABwAEAAcABAAFAAcABQAHAAIAAAAAAFsIAABbCAAAXQgAAF0IAABe
CAAAXggAAGAIAABhCAAAYwgAAGQIAABmCAAAZwgAAKQKAACnCgAABwAEAAcABAACAAQABwAEAAcA
BAAHAAQABwACAAEA+////y7AbOr/D/8P/w//DwUABgAHAAgACQAAAAEAAAAAAAEAAAAAAAAAAAAA
AAAAAAAAAAMYAAAPhLABEYRQ/hXGBQABsAEGXoSwAWCEUP5vKAABAAAAAQAAAAAAAQMAAAAAAAAA
AAAAAAAAAAAAAxgBAA+EQAIRhMD9FcYFAAFAAgZehEACYITA/W8oAAMAAAAuAAEAAQAAAAAAAQMF
AAAAAAAAAAAAAAAAAAAAAxgCAA+E0AIRhDD9FcYFAAHQAgZehNACYIQw/W8oAAUAAAAuAAEALgAC
AAEAAAAAAAEDBQcAAAAAAAAAAAAAAAAAAAMYAwAPhGADEYSg/BXGBQABYAMGXoRgA2CEoPxvKAAH
AAAALgABAC4AAgAuAAMAAQAAAAAAAQMFBwkAAAAAAAAAAAAAAAAAAxgEAA+E8AMRhBD8FcYFAAHw
AwZehPADYIQQ/G8oAAkAAAAuAAEALgACAC4AAwAuAAQAAQAAAAAAAQMFBwkLAAAAAAAAAAAAAAAA
AxgFAA+EgAQRhID7FcYFAAGABAZehIAEYISA+28oAAsAAAAuAAEALgACAC4AAwAuAAQALgAFAAEA
AAAAAAEDBQcJCw0AAAAAAAAAAAAAAAMYBgAPhBAFEYTw+hXGBQABEAUGXoQQBWCE8PpvKAANAAAA
LgABAC4AAgAuAAMALgAEAC4ABQAuAAYAAQAAAAAAAQMFBwkLDQ8AAAAAAAAAAAAAAxgHAA+EoAUR
hGD6FcYFAAGgBQZehKAFYIRg+m8oAA8AAAAuAAEALgACAC4AAwAuAAQALgAFAC4ABgAuAAcAAQAA
AAAAAQMFBwkLDQ8RAAAAAAAAAAAAAxgIAA+EMAYRhND5FcYFAAEwBgZehDAGYITQ+W8oABEAAAAu
AAEALgACAC4AAwAuAAQALgAFAC4ABgAuAAcALgAIAAUAAAD7////AAAAAAAAAAAAAAAA+////wAA
AAAAAAAAAAAAAPv///8AAAAAAAAAAAAAAAD7////AAAAAAAAAAAAAAAA+////wAAAAAAAAAAAAAA
AP////////////////////////////8BAAAAAAD//wEAAAAAAAEAAAAAAAcEAAIJAEgAAAAEAAAA
CAAAAOUAAAAAAAAARwAAAOU4AgC5YQMAXQ8GAKo0BgC1IAcAkjUOAFh+DgDLExwA6lofAAZnHwD0
LCMAf38lABguJwDPNygACmspANEnKgD3AC0AbUsyANwEPACfPz4AKmQ/AAARRAAPQFIAUH9WANFl
VwCSFFkAIBNqAEd9bQCTKW8AAHZwAA5XcQBQKHIA+Cp4AMkzeQDcanwAunR/ABN8fwAWf4YA2FmP
ANNmkAAoIpMAolKWAPVhlgBfQZcAuHygAKQVowDNdqUAwhGoADhCqADYaqwACCi1AJ0YtgAVObYA
22+9AKobvwAQIMEAV37GAOxGzABpZdAAEkbRAB080wCkVtkAz1/bAEVC3QA0OeEAmRflACJ86AAg
JesAkCLtABti9gD8P/cAwQ78AAAAAAADAAAAKQAAAD0AAAA+AAAAPwAAAH8AAACPAAAAkAAAAJEA
AACSAAAAnwAAAKAAAACqAAAAqwAAAOIAAADjAAAA/gAAAP8AAAAHAQAAHwEAACABAAAnAQAARwEA
AEgBAABJAQAASgEAAE4BAABiAQAAYwEAAG0BAAB1AQAAdgEAAHsBAACSAQAAkwEAAJ0BAACtAQAA
rgEAALcBAADoAQAARAIAAEUCAACdAgAAngIAAFsIAACZCAAAoQoAAKIKAACnCgAAAAAAAAIBAAAC
AQAAAgEAAJ4BAAQCAQAAAgEAAAIBAACeAQAEAgEAAAIBAAACAQAAngEABAIBAAACAQAAAgEAAJ4B
AAQCAQAAngEABAIBAAACAQAAngEABAIBAAACAQAAngEABAIBAACeAQAEAgEAAAIBAACeAQAEAgEA
AAIBAACeAQAEAgEAAAIBAACeAQAEAgEAAAIBAACeAQAEAgEAAAIBAAACAQAAngEABAIBAACWAQAE
AAAAAAgAAAACAQAAlgEABP9ADYABAAAAAAAAAAAAWDm1DQEAAQAAAAAAAAAAAAAAAADH/4omAhAA
AAAAAAAApgoAAIAAABAAQAAA//8BAAAABwBVAG4AawBuAG8AdwBuAP//AQAIAAAAAAAAAAAAAAD/
/wEAAAAAAP//AAACAP//AAAAAP//AAACAP//AAAAAAYAAABHFpABAAACAgYDBQQFAgMEh3oAIAAA
AIAIAAAAAAAAAP8BAAAAAAAAVABpAG0AZQBzACAATgBlAHcAIABSAG8AbQBhAG4AAAA1FpABAgAF
BQECAQcGAgUHAAAAAAAAABAAAAAAAAAAAAAAAIAAAAAAUwB5AG0AYgBvAGwAAAAzJpABAAACCwYE
AgICAgIEh3oAIAAAAIAIAAAAAAAAAP8BAAAAAAAAQQByAGkAYQBsAAAAPzWQAQAAAgcDCQICBQIE
BId6ACAAAACACAAAAAAAAAD/AQAAAAAAAEMAbwB1AHIAaQBlAHIAIABOAGUAdwAAADUmAAAAAAIL
BgQDBQQEAgSHegBhAAAAgAgAAAAAAAAA/wEBAAAAAABUAGEAaABvAG0AYQAAADsGkAGGBwIBBgAD
AQEBAQEDAAAAAAAOCBAAAAAAAAAAAQAEAAAAAABTAGkAbQBTAHUAbgAAAItbU08AACIABAADAAgY
Vvw3AgAAqQEAAAAAd82xhnfNsYbomqlGAgAEAAAAPwEAABwHAAABAAQAAAAEAIMADwAAAD8BAAAc
BwAAAQAEAAAADwAAAAAAAAAJJFb8EAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABuBIkFeAC0
AICAEjQAABAAGQBkAAAAGQAAAFcIAABXCAAAAAAAAE0z/CQAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAgzg3FW/BAE398DAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAASFAAAAAACfD/DwEAAT8AAOQEAAD///9/////f////3////9/
////f////3////9/olKWAAAAAAAyAAAAAAAAAAAAAAAAAAEAAAD//xIAAAAAAF0AQwA6AFwARABv
AGMAdQBtAGUAbgB0AHMAIABhAG4AZAAgAFMAZQB0AHQAaQBuAGcAcwBcAHEAdQBpAHMAdABcAEEA
cABwAGwAaQBjAGEAdABpAG8AbgAgAEQAYQB0AGEAXABNAGkAYwByAG8AcwBvAGYAdABcAFQAZQBt
AHAAbABhAHQAZQBzAFwASQB0AHUAdABMAGkAYQBpAHMAbwBuAC0AVABlAG0AcABsAGEAdABlAC4A
ZABvAHQAGgBPAFUAVABHAE8ASQBOAEcAIABMAEkAQQBJAFMATwBOACAAUwBUAEEAVABFAE0ARQBO
AFQAAAAAAAAABQBJAFQAVQAtAFQADABKAHUAZABpAHQAaAAgAFEAdQBpAHMAdAAAAAAAAAAAAAAA
AAAAAAAAAAAAABAAAAAGAAAAAQAAAAAADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP7/AAAFAQIAAAAAAAAAAAAA
AAAAAAAAAAEAAADghZ/y+U9oEKuRCAArJ7PZMAAAAKwBAAASAAAAAQAAAJgAAAACAAAAoAAAAAMA
AADEAAAABAAAANAAAAAFAAAA4AAAAAYAAADsAAAABwAAAPgAAAAIAAAAGAEAAAkAAAAwAQAAEgAA
ADwBAAAKAAAAXAEAAAsAAABoAQAADAAAAHQBAAANAAAAgAEAAA4AAACMAQAADwAAAJQBAAAQAAAA
nAEAABMAAACkAQAAAgAAAOQEAAAeAAAAHAAAAE9VVEdPSU5HIExJQUlTT04gU1RBVEVNRU5UAAAe
AAAABAAAAAAAAAAeAAAACAAAAElUVS1UAAAAHgAAAAQAAAAAAAAAHgAAAAQAAAAAAAAAHgAAABgA
AABJdHV0TGlhaXNvbi1UZW1wbGF0ZQAAAAAeAAAAEAAAAEp1ZGl0aCBRdWlzdAAAAAAeAAAABAAA
ADIAAAAeAAAAGAAAAE1pY3Jvc29mdCBPZmZpY2UgV29yZAAAAEAAAAAAGA2PAAAAAEAAAAAAAOn0
19vGAUAAAAAAKuYTw0DHAUAAAAAAKuYTw0DHAQMAAAABAAAAAwAAAD8BAAADAAAAHAcAAAMAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD+/wAABQECAAAAAAAAAAAAAAAAAAAAAAAC
AAAAAtXN1ZwuGxCTlwgAKyz5rkQAAAAF1c3VnC4bEJOXCAArLPmuqAEAAGQBAAAPAAAAAQAAAIAA
AAACAAAAiAAAAA4AAACUAAAADwAAAKAAAAAEAAAA1AAAAAUAAADcAAAABgAAAOQAAAARAAAA7AAA
ABcAAAD0AAAACwAAAPwAAAAQAAAABAEAABMAAAAMAQAAFgAAABQBAAANAAAAHAEAAAwAAABDAQAA
AgAAAOQEAAAeAAAABAAAAAAAAAAeAAAABAAAAAAAAAAeAAAALAAAAEludGVybmF0aW9uYWwgVGVs
ZWNvbW11bmljYXRpb24gVW5pb24gKElUVSkAAwAAAG4tAAADAAAADwAAAAMAAAAEAAAAAwAAAFcI
AAADAAAAqBkLAAsAAAAAAAAACwAAAAAAAAALAAAAAAAAAAsAAAAAAAAAHhAAAAEAAAAbAAAAT1VU
R09JTkcgTElBSVNPTiBTVEFURU1FTlQADBAAAAIAAAAeAAAABgAAAFRpdGxlAAMAAAABAAAAAAAA
RAIAAAkAAAAAAAAAUAAAAAEAAADPAAAAAgAAANcAAAADAAAAuwEAAAQAAADXAQAABQAAAOMBAAAG
AAAACwIAAAcAAAAXAgAACAAAADcCAAAHAAAAAgAAAAwAAABfUElEX0hMSU5LUwADAAAABwAAAERv
Y251bQAEAAAACAAAAERvY2RhdGUABQAAAAoAAABEb2NvcmxhbmcABgAAAAwAAABEb2NibHVlcGlu
awAHAAAACAAAAERvY2Rlc3QACAAAAAoAAABEb2NhdXRob3IAAgAAAOQEAABBAAAA3AAAAAwAAAAD
AAAATQBfAAMAAAADAAAAAwAAAAAAAAADAAAABQAAAB8AAAAeAAAAaAB0AHQAcAA6AC8ALwB3AHcA
dwAuAGkAdAB1AC4AaQBuAHQALwBJAFQAVQAtAFQALwBJAFAAVABWAAAAHwAAAAEAAAAAAPQOAwAA
AGAAQgADAAAAAAAAAAMAAAAAAAAAAwAAAAUAAAAfAAAAGgAAAG0AYQBpAGwAdABvADoAZwBoAGEA
cwBzAGUAbQBAAG4AbwByAHQAZQBsAC4AYwBvAG0AAAAfAAAAAQAAAAAA9A4eAAAAFAAAAFRTQUcg
liBMUyB4eHh4eCCWIEUAHgAAAAQAAAAAAAAAHgAAACAAAABFbmdsaXNoIG9ubHkgT3JpZ2luYWw6
IEVuZ2xpc2gAAB4AAAAEAAAAAAAAAB4AAAAYAAAAR2VuZXZhLCAzLTcgSnVseSAyMDA2AAAAHgAA
AAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAIAAAADAAAABAAAAAUAAAAGAAAABwAAAAgAAAAJ
AAAACgAAAAsAAAAMAAAADQAAAA4AAAAPAAAAEAAAABEAAAASAAAAEwAAABQAAAAVAAAAFgAAABcA
AAAYAAAAGQAAABoAAAD+////HAAAAB0AAAAeAAAAHwAAACAAAAAhAAAAIgAAACMAAAAkAAAAJQAA
AP7///8nAAAAKAAAACkAAAAqAAAAKwAAACwAAAAtAAAALgAAAC8AAAAwAAAAMQAAADIAAAAzAAAA
NAAAADUAAAA2AAAANwAAADgAAAA5AAAAOgAAADsAAAA8AAAAPQAAAD4AAAA/AAAAQAAAAEEAAABC
AAAAQwAAAEQAAABFAAAARgAAAEcAAABIAAAA/v///0oAAABLAAAATAAAAE0AAABOAAAATwAAAFAA
AAD+////UgAAAFMAAABUAAAAVQAAAFYAAABXAAAAWAAAAP7////9////WwAAAP7////+/////v//
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
//////////////////////////////9SAG8AbwB0ACAARQBuAHQAcgB5AAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFgAFAf//////////AwAAAAYJAgAAAAAAwAAA
AAAAAEYAAAAAAAAAAAAAAAAQdQg3w0DHAV0AAACAAAAAAAAAAEQAYQB0AGEAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKAAIB////////////
////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGwAAABMUAAAAAAAAMQBUAGEA
YgBsAGUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AA4AAgEBAAAABgAAAP////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAmAAAA
Y0QAAAAAAABXAG8AcgBkAEQAbwBjAHUAbQBlAG4AdAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAGgACAQIAAAAFAAAA/////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAA7NAAAAAAAAAUAUwB1AG0AbQBhAHIAeQBJAG4AZgBvAHIAbQBhAHQAaQBv
AG4AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoAAIB////////////////AAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAASQAAAAAQAAAAAAAABQBEAG8AYwB1AG0AZQBuAHQAUwB1
AG0AbQBhAHIAeQBJAG4AZgBvAHIAbQBhAHQAaQBvAG4AAAAAAAAAAAAAADgAAgEEAAAA////////
//8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABRAAAAABAAAAAAAAABAEMAbwBt
AHAATwBiAGoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
EgACAP///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABx
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAA////////////////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAP7/////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
//////////////////////////8BAP7/AwoAAP////8GCQIAAAAAAMAAAAAAAABGHwAAAE1pY3Jv
c29mdCBPZmZpY2UgV29yZCBEb2N1bWVudAAKAAAATVNXb3JkRG9jABAAAABXb3JkLkRvY3VtZW50
LjgA9DmycQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAFIAbwBvAHQAIABFAG4AdAByAHkAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAWAAUB//////////8DAAAABgkCAAAAAADAAAAAAAAA
RgAAAAAAAAAAAAAAADCoViwtRccBZAAAAIAEAAAAAAAARABhAHQAYQAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoAAgH///////////////8A
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAbAAAAExQAAAAAAAAxAFQAYQBiAGwA
ZQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADgAC
AQEAAAAGAAAA/////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACYAAABjRAAA
AAAAAFcAbwByAGQARABvAGMAdQBtAGUAbgB0AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAaAAIBAgAAAAUAAAD/////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAADs0AAAAAAAAAQAAAAIAAAADAAAABAAAAAUAAAAGAAAABwAAAAgAAAAJAAAACgAA
AAsAAAAMAAAADQAAAA4AAAAPAAAAEAAAABEAAAASAAAAEwAAABQAAAAVAAAAFgAAABcAAAAYAAAA
GQAAABoAAAD+////HAAAAB0AAAAeAAAAHwAAACAAAAAhAAAAIgAAACMAAAAkAAAAJQAAAP7///8n
AAAAKAAAACkAAAAqAAAAKwAAACwAAAAtAAAALgAAAC8AAAAwAAAAMQAAADIAAAAzAAAANAAAADUA
AAA2AAAANwAAADgAAAA5AAAAOgAAADsAAAA8AAAAPQAAAD4AAAA/AAAAQAAAAEEAAABCAAAAQwAA
AEQAAABFAAAARgAAAEcAAABIAAAA/v///0oAAABLAAAATAAAAE0AAABOAAAATwAAAFAAAAD+////
/////////////////////////////////////////////////////////////////////2MAAAD9
/////v///2IAAAD+/////v///2EAAAD/////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
//////////////////////8BAAAA/v///wMAAAAEAAAABQAAAAYAAAAHAAAACAAAAAkAAAAKAAAA
CwAAAAwAAAANAAAADgAAAA8AAAAQAAAAEQAAAP7/////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
/////////////////////1RFTUVOVAAMEAAAAgAAAB4AAAAGAAAAVGl0bGUAAwAAAAEAAAAAAABE
AgAACQAAAAAAAABQAAAAAQAAANAAAAACAAAA2AAAAAMAAAC8AQAABAAAANgBAAAFAAAA5AEAAAYA
AAAMAgAABwAAABgCAAAIAAAAOAIAAAcAAAACAAAADAAAAF9QSURfSExJTktTAAMAAAAHAAAARG9j
bnVtAAQAAAAIAAAARG9jZGF0ZQAFAAAACgAAAERvY29ybGFuZwAGAAAADAAAAERvY2JsdWVwaW5r
AAcAAAAIAAAARG9jZGVzdAAIAAAACgAAAERvY2F1dGhvcgACAgAAAOQEAABBAAAA3AAAAAwAAAAD
AAAATQBfAAMAAAADAAAAAwAAAAAAAAADAAAABQAAAB8AAAAeAAAAaAB0AHQAcAA6AC8ALwB3AHcA
dwAuAGkAdAB1AC4AaQBuAHQALwBJAFQAVQAtAFQALwBJAFAAVABWAAAAHwAAAAEAAAAAAPQOAwAA
AGAAQgADAAAAAAAAAAMAAAAAAAAAAwAAAAUAAAAfAAAAGgAAAG0AYQBpAGwAdABvADoAZwBoAGEA
cwBzAGUAbQBAAG4AbwByAHQAZQBsAC4AYwBvAG0AAAAfAAAAAQAAAAAA9A4eAAAAFAAAAFRTQUcg
liBMUyB4eHh4eCCWIEUAHgAAAAQAAAAAAAAAHgAAACAAAABFbmdsaXNoIG9ubHkgT3JpZ2luYWw6
IEVuZ2xpc2gAAB4AAAAEAAAAAAAAAB4AAAAYAAAAR2VuZXZhLCAzLTcgSnVseSAyMDA2AAAAHgAA
AAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAFAFMAdQBtAG0AYQByAHkASQBuAGYAbwByAG0AYQB0AGkAbwBuAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAKAACAf///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAEkAAAAAEAAAAAAAAAUARABvAGMAdQBtAGUAbgB0AFMAdQBtAG0AYQBy
AHkASQBuAGYAbwByAG0AYQB0AGkAbwBuAAAAAAAAAAAAAAA4AAIBBAAAAP//////////AAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAOwDAAAAAAAAAQBDAG8AbQBwAE8AYgBq
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABIAAgD/////
//////////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAcQAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAP///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAEA/v8DCgAA/////wYJAgAAAAAAwAAAAAAAAEYfAAAATWljcm9zb2Z0IE9m
ZmljZSBXb3JkIERvY3VtZW50AAoAAABNU1dvcmREb2MAEAAAAFdvcmQuRG9jdW1lbnQuOAD0ObJx
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/v8AAAUBAgAAAAAAAAAAAAAAAAAAAAAAAgAAAALV
zdWcLhsQk5cIACss+a5EAAAABdXN1ZwuGxCTlwgAKyz5rqgBAABkAQAADwAAAAEAAACAAAAAAgAA
AIgAAAAOAAAAlAAAAA8AAACgAAAABAAAANQAAAAFAAAA3AAAAAYAAADkAAAAEQAAAOwAAAAXAAAA
9AAAAAsAAAD8AAAAEAAAAAQBAAATAAAADAEAABYAAAAUAQAADQAAABwBAAAMAAAAQwEAAAIAAADk
BAAAHgAAAAQAAAAAAAAAHgAAAAQAAAAAAAAAHgAAACwAAABJbnRlcm5hdGlvbmFsIFRlbGVjb21t
dW5pY2F0aW9uIFVuaW9uIChJVFUpAAMAAABuLQAAAwAAAA8AAAADAAAABAAAAAMAAABXCAAAAwAA
AKgZCwALAAAAAAAAAAsAAAAAAAAACwAAAAAAAAALAAAAAAAAAB4QAAABAAAAGwAAAE9VVEdPSU5H
IExJQUlTT04gU1RB

--Apple-Mail-6--359604656
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed



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

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

--Apple-Mail-6--359604656--




From avt-bounces@ietf.org Sun Feb 11 16:13:30 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGLzT-0004ty-FT; Sun, 11 Feb 2007 16:12:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGLzS-0004tQ-6E
	for avt@ietf.org; Sun, 11 Feb 2007 16:12:06 -0500
Received: from mail153.messagelabs.com ([216.82.253.51])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HGLzQ-0008OR-Qe
	for avt@ietf.org; Sun, 11 Feb 2007 16:12:06 -0500
X-VirusChecked: Checked
X-Env-Sender: Qiaobing.Xie@motorola.com
X-Msg-Ref: server-13.tower-153.messagelabs.com!1171228321!1981859!1
X-StarScan-Version: 5.5.10.7.1; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 14287 invoked from network); 11 Feb 2007 21:12:01 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-13.tower-153.messagelabs.com with SMTP;
	11 Feb 2007 21:12:01 -0000
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l1BLBv5g023233;
	Sun, 11 Feb 2007 14:11:57 -0700 (MST)
Received: from [192.168.15.2] (mvp-10-31-8-238.am.mot.com [10.31.8.238])
	by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id l1BLBtCZ021082;
	Sun, 11 Feb 2007 15:11:56 -0600 (CST)
Message-ID: <45CF869D.2030405@motorola.com>
Date: Sun, 11 Feb 2007 15:11:57 -0600
From: Qiaobing Xie <Qiaobing.Xie@motorola.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortel.com>
Subject: Re: [AVT] Re: Review requested: draft-ietf-avt-rtp-toffset-04.txt
References: <4586E60E.20408@nortel.com>
	<4586E8D6.2070903@nortel.com>	<4586E73C.50901@nortel.com>
	<p06230912c1d2511793b0@[10.0.1.33]>	<45ACF914.8040700@nortel.com>
	<p062309a0c1dcda6fe8ca@[10.0.1.33]>	<E319D2A3-2E44-4795-86D8-63465DDC300B@csperkins.org>	<p062309c2c1e37868bb4e@[10.0.1.33]>	<4A9A2D76-48B4-4C8A-8D29-3B2497C055F1@csperkins.org>
	<45CBB657.4010200@nortel.com>
In-Reply-To: <45CBB657.4010200@nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

I agree. The proposed changes address my comments sufficiently.

regards,
-Qiaobing

Tom-PT Taylor wrote:
> Here is what I hope is the last word on the topic: Dave's actions.
> 
> Dave Singer wrote:
> -------------------
> 
> OK, changed the first sentence:
> 
> In the RTP specification <xref target="RFC3550"/> network jitter
> calculations are based on the presumption that packets are
> transmitted essentially in accordance with their RTP timestamps.
> 
> and added
> 
> The RTP specification does not define a transmission timestamp, and
> nor does this specification.  This specification merely provides
> information on the relationship between the relative transmission
> times and relative RTP timestamps.
> 
> and
> 
> The reported transmission time T1 of a packet with timestamp R1 and
> an offset of O1, from the above equations, is T1 = R1+O1 (though of
> course the transmission time values only have meaning when two or
> more are compared).
> 
> and
> 
> The content is exactly that number of interarrival jitter
> calculations, calculated using the same formula as for sender and
> receiver reports, but taking into account the transmission offsets
> for the streams (if any);  that is, using the values T1=R1+O1, T2
> etc. as defined above, instead of R1, R2 etc..
> 
> I then re-named the symbols to be in accord with the RTP spec (i.e.
> using Si for RTP timestamp, not Ri).
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

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



From avt-bounces@ietf.org Mon Feb 12 04:34:10 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGXYP-0001Z8-PW; Mon, 12 Feb 2007 04:32:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGXYO-0001Z3-9A
	for avt@ietf.org; Mon, 12 Feb 2007 04:32:56 -0500
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGXYN-0007Ih-MO
	for avt@ietf.org; Mon, 12 Feb 2007 04:32: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="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] CCM draft review -- should "bandwidth" include the
	headeroverhead
Date: Mon, 12 Feb 2007 11:32:53 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com>
In-Reply-To: <ybu4ppsaces.fsf@jesup.eng.wgate.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] CCM draft review -- should "bandwidth" include the
	headeroverhead
Thread-Index: AcdN+XzRC4PlNiH5RQ6eEKzZsw7jKgAjvqug
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Randell Jesup" <rjesup@wgate.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 29dc808194f5fb921c09d0040806d6eb
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Stephan Wenger <stewe@stewe.org>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Randell,
I think part of the discussion is because there is a lack of application
usage.
For example, on a gateway between H.320 and SIP you need to limit the
codec BW bellow the circuit switch rate. Same for a mixed conference
that has ISDN as well as SIP or H.323 parties.
This is why in H.323 and H.320 the rate is the codec rate
Roni Even

> -----Original Message-----
> From: Randell Jesup [mailto:rjesup@wgate.com]
> Sent: Sunday, February 11, 2007 6:26 PM
> To: Even, Roni
> Cc: Magnus Westerlund; Stephan Wenger; avt@ietf.org
> Subject: Re: [AVT] CCM draft review -- should "bandwidth" include the
> headeroverhead
>=20
> "Even, Roni" <roni.even@polycom.co.il> writes:
> >This is our view about why to use the codec bit rate and not any
> >overhead. We have to remember that this is mostly for video who does
not
> >have a fixed frame size and that packets can be larger than MTU size
and
> >thus may be broken differently based on implementations.
>=20
> Which is why TIAS (especially with TMMBR) is fundamentally broken for
> offer/answer.  TIAS allows setting the max packet rate - fine for a
> declarative use, but for offer/answer, it means that the receiver
knows
> the
> actual bandwidth (typically configured - "I have a 1Mbps downstream",
> perhaps measured/probed, but usually NOT probed end-to-end to the
sender),
> it must (to send TIAS) follow RFC 3890 #6.4 in reverse, using a (high)
> guess at maxprate.  When done, you basically have
> TIAS =3D BW - (maxprate*hsize).
>=20
> So the sender limits their codec to TIAS, and probably uses a lot less
> than
> maxprate packets, wasting that bandwidth.  If maxprate was chosen too
low,
> the sender might have to (for video) reduce frame rate, especially if
(as
> you mention) the sender wants to send more packets than the receiver
> anticipates.  If the sender goes over maxprate, it might work, and
might
> not, and there's no way for the sender to estimate how much to reduce
the
> TIAS amount by other than guessing.
>=20
> I think b=3DAS (etc) make more sense; the sender knows the actual =
prate,
> size
> of any headers it sends, and so can make best use of of the available
> bits.
> If we need to know any additional header/etc modifications inbetween
the
> sender and receiver, then we should find a mechanism to discover
and/or
> signal that directly.
>=20
> >For one thing, the amount of data in the headers depends on whether
> header
> >compression is in use.  Since header compression can be applied (or
> >removed) anywhere along the path, the amount of overhead seen by the
> >receiver might be different than the overhead seen by the
transmitter.
>=20
> And how does the receiver making an offer or answer determine this?
The
> receiver typically only knows the last-link settings.
>=20
> >Another reason is that an intermediate device (gateways, proxies, or
> other
> >RTP media engine) might be re-packetizing the data.  This would also
> >create a mismatch between the source and the receiver.  All of this
is
> >avoided if we define the bit rate to be the media rate.
>=20
> Avoided: not really.  I'd say pushed off into some undefined
mechanism.
> Or, if not handled, you're not really solving the problem.
>=20
> >A third way a mismatch can be created is by encryption, where an
> >encryption pad is added (or possibly removed) at the campus edge.  So
I'd
> >also want that RTP padding to be excluded from the definition (not
just
> >the headers).
>=20
> And again, how does the receiver know this to include it in the TIAS
> calculation?  If this is an RTP/RTCP-aware midbox, it could adjust BW
> values - if *everything* that can modify bandwidth is aware and
handles
> TIAS in offers and TMMBR, you could adjust TIAS by (maxprate *
> packet_delta), but in reality I don't see this happening.  BTW, any
> end-to-end signalling or media encryption will cause a major headache
here
> - the midbox can't see/modify these values.  At best it could in some
> cases
> signal the modification separately or in a separate tag at call setup,
but
> that's not an option with current protocols.
>=20
> >Of course, we'd also prefer to keep it as media because that is what
both
> >H.323 and H.320 do and part of the usage of this command is to adapt
> rates
> >between different transport channels.
>=20
> I'd say then push the burden of converting to bandwidth into media
rate
> onto the converter, not into every endpoint (especially since using
these
> conversions seems to require either a lot of assumptions or
potentially
> wastes bandwidth).
>=20
> I think I'm pretty much in agreement with Magnus here.
>=20
> Magnus also writes:
> >> Guido's idea of including the average packet overhead might
actually
> not
> >> be a bad one. As that would allow the sender to take into
consideration
> >> the per packet overhead seen by the TMMBR sending receiver. I would
> >> define that overhead as the number of bytes in addition to RTP
payload.
> >> The reason to include the RTP header itself is that if there are
some
> >> translator or mixer doing something to expand the RTP header.
>=20
> This speaks to my comment above about finding a way to signal overhead
> separate from link bandwidth.
>=20
> --
> Randell Jesup, Worldgate (developers of the Ojo videophone), ex-Amiga
OS
> team
> rjesup@wgate.com
> "The fetters imposed on liberty at home have ever been forged out of
the
> weapons
> provided for defence against real, pretended, or imaginary dangers
from
> abroad."
> 		- James Madison, 4th US president (1751-1836)


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



From avt-bounces@ietf.org Mon Feb 12 08:08:58 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGauQ-0007i9-OU; Mon, 12 Feb 2007 08:07:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGauP-0007hn-Co
	for avt@ietf.org; Mon, 12 Feb 2007 08:07:53 -0500
Received: from stewe.org ([85.214.23.117] helo=h665227.serverkompetenz.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGauN-0007c2-MK
	for avt@ietf.org; Mon, 12 Feb 2007 08:07:53 -0500
Received: (qmail 3437 invoked by uid 60000); 12 Feb 2007 12:02:09 -0000
Received: from 91.153.2.168 by h665227 (envelope-from <stewe@stewe.org>,
	uid 60004) with qmail-scanner-1.24st visas (spamassassin: 2.64.  
	Clear:RC:0(91.153.2.168):SA:0(0.0/20.0):. 
	Processed in 0.34616 secs); 12 Feb 2007 12:02:09 -0000
X-Spam-Status: No, hits=0.0 required=20.0
X-Envelope-From: stewe@stewe.org
Received: from a91-153-2-168.elisa-laajakaista.fi (HELO ?192.168.1.5?)
	(stewe@stewe.org@91.153.2.168)
	by stewe.org with SMTP; 12 Feb 2007 12:02:09 -0000
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com>
References: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <10E7D146-0080-420A-BEF4-44C22DD7BAE0@stewe.org>
Content-Transfer-Encoding: 7bit
From: Stephan Wenger <stewe@stewe.org>
Subject: Re: [AVT] CCM draft review -- should "bandwidth" include the
	headeroverhead
Date: Mon, 12 Feb 2007 15:07:27 +0200
To: "Even, Roni" <roni.even@polycom.co.il>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on 
	h665227.serverkompetenz.net
X-Spam-Level: 
X-Qmail-Scanner-MOVED-X-Spam-Status: No, hits=0.0 required=20.0 tests=none
	autolearn=no version=2.64
X-Spam-Score: 0.1 (/)
X-Scan-Signature: bf422c85703d3d847fb014987125ac48
Cc: Randell Jesup <rjesup@wgate.com>,
	Magnus Westerlund <magnus.westerlund@ericsson.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Folks,

I have a proposal in the best tradition of ITU-T standardization :-):  
let's do it both.

Roni has compelling arguments, I believe, for the interpretation of  
the TMMBR bitrate as the codec bitrate only.  I agree with him that  
using the codec bitrate opens cross-protocol application spaces that  
would otherwise be closed.  And, the codec bitrate is not affected by  
ROHC, IPv4/v6 issues, and so on.

Magnus and others have suggested that including the header overhead  
makes sense as well, almost certainly for all-IP scenarios.  It's  
also what most folks assume in 3GPP SA4, which is going to be the  
first "customer" for TMMBR.

So let's do it both.  We can signal the interpretation by a bit in  
the header (sliced off from the bitrate---there are enough bits), or  
we can make this dependent on signaling.  I have a slight preference  
for the latter.

How does this sound?

Regards,
Stepha


On Feb 12, 2007, at 11:32 AM, Even, Roni wrote:

> Randell,
> I think part of the discussion is because there is a lack of  
> application
> usage.
> For example, on a gateway between H.320 and SIP you need to limit the
> codec BW bellow the circuit switch rate. Same for a mixed conference
> that has ISDN as well as SIP or H.323 parties.
> This is why in H.323 and H.320 the rate is the codec rate
> Roni Even
>
>> -----Original Message-----
>> From: Randell Jesup [mailto:rjesup@wgate.com]
>> Sent: Sunday, February 11, 2007 6:26 PM
>> To: Even, Roni
>> Cc: Magnus Westerlund; Stephan Wenger; avt@ietf.org
>> Subject: Re: [AVT] CCM draft review -- should "bandwidth" include the
>> headeroverhead
>>
>> "Even, Roni" <roni.even@polycom.co.il> writes:
>>> This is our view about why to use the codec bit rate and not any
>>> overhead. We have to remember that this is mostly for video who does
> not
>>> have a fixed frame size and that packets can be larger than MTU size
> and
>>> thus may be broken differently based on implementations.
>>
>> Which is why TIAS (especially with TMMBR) is fundamentally broken for
>> offer/answer.  TIAS allows setting the max packet rate - fine for a
>> declarative use, but for offer/answer, it means that the receiver
> knows
>> the
>> actual bandwidth (typically configured - "I have a 1Mbps downstream",
>> perhaps measured/probed, but usually NOT probed end-to-end to the
> sender),
>> it must (to send TIAS) follow RFC 3890 #6.4 in reverse, using a  
>> (high)
>> guess at maxprate.  When done, you basically have
>> TIAS = BW - (maxprate*hsize).
>>
>> So the sender limits their codec to TIAS, and probably uses a lot  
>> less
>> than
>> maxprate packets, wasting that bandwidth.  If maxprate was chosen too
> low,
>> the sender might have to (for video) reduce frame rate, especially if
> (as
>> you mention) the sender wants to send more packets than the receiver
>> anticipates.  If the sender goes over maxprate, it might work, and
> might
>> not, and there's no way for the sender to estimate how much to reduce
> the
>> TIAS amount by other than guessing.
>>
>> I think b=AS (etc) make more sense; the sender knows the actual  
>> prate,
>> size
>> of any headers it sends, and so can make best use of of the available
>> bits.
>> If we need to know any additional header/etc modifications inbetween
> the
>> sender and receiver, then we should find a mechanism to discover
> and/or
>> signal that directly.
>>
>>> For one thing, the amount of data in the headers depends on whether
>> header
>>> compression is in use.  Since header compression can be applied (or
>>> removed) anywhere along the path, the amount of overhead seen by the
>>> receiver might be different than the overhead seen by the
> transmitter.
>>
>> And how does the receiver making an offer or answer determine this?
> The
>> receiver typically only knows the last-link settings.
>>
>>> Another reason is that an intermediate device (gateways, proxies, or
>> other
>>> RTP media engine) might be re-packetizing the data.  This would also
>>> create a mismatch between the source and the receiver.  All of this
> is
>>> avoided if we define the bit rate to be the media rate.
>>
>> Avoided: not really.  I'd say pushed off into some undefined
> mechanism.
>> Or, if not handled, you're not really solving the problem.
>>
>>> A third way a mismatch can be created is by encryption, where an
>>> encryption pad is added (or possibly removed) at the campus  
>>> edge.  So
> I'd
>>> also want that RTP padding to be excluded from the definition (not
> just
>>> the headers).
>>
>> And again, how does the receiver know this to include it in the TIAS
>> calculation?  If this is an RTP/RTCP-aware midbox, it could adjust BW
>> values - if *everything* that can modify bandwidth is aware and
> handles
>> TIAS in offers and TMMBR, you could adjust TIAS by (maxprate *
>> packet_delta), but in reality I don't see this happening.  BTW, any
>> end-to-end signalling or media encryption will cause a major headache
> here
>> - the midbox can't see/modify these values.  At best it could in some
>> cases
>> signal the modification separately or in a separate tag at call  
>> setup,
> but
>> that's not an option with current protocols.
>>
>>> Of course, we'd also prefer to keep it as media because that is what
> both
>>> H.323 and H.320 do and part of the usage of this command is to adapt
>> rates
>>> between different transport channels.
>>
>> I'd say then push the burden of converting to bandwidth into media
> rate
>> onto the converter, not into every endpoint (especially since using
> these
>> conversions seems to require either a lot of assumptions or
> potentially
>> wastes bandwidth).
>>
>> I think I'm pretty much in agreement with Magnus here.
>>
>> Magnus also writes:
>>>> Guido's idea of including the average packet overhead might
> actually
>> not
>>>> be a bad one. As that would allow the sender to take into
> consideration
>>>> the per packet overhead seen by the TMMBR sending receiver. I would
>>>> define that overhead as the number of bytes in addition to RTP
> payload.
>>>> The reason to include the RTP header itself is that if there are
> some
>>>> translator or mixer doing something to expand the RTP header.
>>
>> This speaks to my comment above about finding a way to signal  
>> overhead
>> separate from link bandwidth.
>>
>> --
>> Randell Jesup, Worldgate (developers of the Ojo videophone), ex-Amiga
> OS
>> team
>> rjesup@wgate.com
>> "The fetters imposed on liberty at home have ever been forged out of
> the
>> weapons
>> provided for defence against real, pretended, or imaginary dangers
> from
>> abroad."
>> 		- James Madison, 4th US president (1751-1836)
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt


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



From avt-bounces@ietf.org Mon Feb 12 12:53:08 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGfKw-0000yJ-O8; Mon, 12 Feb 2007 12:51:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGfKv-0000y3-4h
	for avt@ietf.org; Mon, 12 Feb 2007 12:51:33 -0500
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGfKu-0003It-Dj
	for avt@ietf.org; Mon, 12 Feb 2007 12:51:33 -0500
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
Subject: RE: [AVT] CCM draft review -- should "bandwidth" include the
	headeroverhead
Date: Mon, 12 Feb 2007 19:51:28 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C044ED4BE@IsrExch01.israel.polycom.com>
In-Reply-To: <10E7D146-0080-420A-BEF4-44C22DD7BAE0@stewe.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] CCM draft review -- should "bandwidth" include the
	headeroverhead
Thread-Index: AcdOptq0q4iqL9SsRwOTRC6J+uz/qgAI5a9w
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Stephan Wenger" <stewe@stewe.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 17bdfcaea25d1444baef0e24abc38874
Cc: Randell Jesup <rjesup@wgate.com>,
	Magnus Westerlund <magnus.westerlund@ericsson.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Stephan,
I can agree with your suggestion in principal depending on the
mechanism. I just want to mention that the video conferencing products
are waiting for this and may implement it before 3GPP. Those are
shipping products that use today INFO based fast update and use b=3DTIAS
for bw.
Since I am not a participant in SA4 but comes from an industry that
ships video conferencing products for quiet some time I would like to
ask you to think about the input from this industry about using codec
rate for flow control in the RTCP feedback. I am not talking here about
the SDP parameter
Thanks

Roni Even
=20

> -----Original Message-----
> From: Stephan Wenger [mailto:stewe@stewe.org]
> Sent: Monday, February 12, 2007 3:07 PM
> To: Even, Roni
> Cc: Randell Jesup; Magnus Westerlund; avt@ietf.org
> Subject: Re: [AVT] CCM draft review -- should "bandwidth" include the
> headeroverhead
>=20
> Folks,
>=20
> I have a proposal in the best tradition of ITU-T standardization :-):
> let's do it both.
>=20
> Roni has compelling arguments, I believe, for the interpretation of
> the TMMBR bitrate as the codec bitrate only.  I agree with him that
> using the codec bitrate opens cross-protocol application spaces that
> would otherwise be closed.  And, the codec bitrate is not affected by
> ROHC, IPv4/v6 issues, and so on.
>=20
> Magnus and others have suggested that including the header overhead
> makes sense as well, almost certainly for all-IP scenarios.  It's
> also what most folks assume in 3GPP SA4, which is going to be the
> first "customer" for TMMBR.
>=20
> So let's do it both.  We can signal the interpretation by a bit in
> the header (sliced off from the bitrate---there are enough bits), or
> we can make this dependent on signaling.  I have a slight preference
> for the latter.
>=20
> How does this sound?
>=20
> Regards,
> Stepha
>=20
>=20
> On Feb 12, 2007, at 11:32 AM, Even, Roni wrote:
>=20
> > Randell,
> > I think part of the discussion is because there is a lack of
> > application
> > usage.
> > For example, on a gateway between H.320 and SIP you need to limit
the
> > codec BW bellow the circuit switch rate. Same for a mixed conference
> > that has ISDN as well as SIP or H.323 parties.
> > This is why in H.323 and H.320 the rate is the codec rate
> > Roni Even
> >
> >> -----Original Message-----
> >> From: Randell Jesup [mailto:rjesup@wgate.com]
> >> Sent: Sunday, February 11, 2007 6:26 PM
> >> To: Even, Roni
> >> Cc: Magnus Westerlund; Stephan Wenger; avt@ietf.org
> >> Subject: Re: [AVT] CCM draft review -- should "bandwidth" include
the
> >> headeroverhead
> >>
> >> "Even, Roni" <roni.even@polycom.co.il> writes:
> >>> This is our view about why to use the codec bit rate and not any
> >>> overhead. We have to remember that this is mostly for video who
does
> > not
> >>> have a fixed frame size and that packets can be larger than MTU
size
> > and
> >>> thus may be broken differently based on implementations.
> >>
> >> Which is why TIAS (especially with TMMBR) is fundamentally broken
for
> >> offer/answer.  TIAS allows setting the max packet rate - fine for a
> >> declarative use, but for offer/answer, it means that the receiver
> > knows
> >> the
> >> actual bandwidth (typically configured - "I have a 1Mbps
downstream",
> >> perhaps measured/probed, but usually NOT probed end-to-end to the
> > sender),
> >> it must (to send TIAS) follow RFC 3890 #6.4 in reverse, using a
> >> (high)
> >> guess at maxprate.  When done, you basically have
> >> TIAS =3D BW - (maxprate*hsize).
> >>
> >> So the sender limits their codec to TIAS, and probably uses a lot
> >> less
> >> than
> >> maxprate packets, wasting that bandwidth.  If maxprate was chosen
too
> > low,
> >> the sender might have to (for video) reduce frame rate, especially
if
> > (as
> >> you mention) the sender wants to send more packets than the
receiver
> >> anticipates.  If the sender goes over maxprate, it might work, and
> > might
> >> not, and there's no way for the sender to estimate how much to
reduce
> > the
> >> TIAS amount by other than guessing.
> >>
> >> I think b=3DAS (etc) make more sense; the sender knows the actual
> >> prate,
> >> size
> >> of any headers it sends, and so can make best use of of the
available
> >> bits.
> >> If we need to know any additional header/etc modifications
inbetween
> > the
> >> sender and receiver, then we should find a mechanism to discover
> > and/or
> >> signal that directly.
> >>
> >>> For one thing, the amount of data in the headers depends on
whether
> >> header
> >>> compression is in use.  Since header compression can be applied
(or
> >>> removed) anywhere along the path, the amount of overhead seen by
the
> >>> receiver might be different than the overhead seen by the
> > transmitter.
> >>
> >> And how does the receiver making an offer or answer determine this?
> > The
> >> receiver typically only knows the last-link settings.
> >>
> >>> Another reason is that an intermediate device (gateways, proxies,
or
> >> other
> >>> RTP media engine) might be re-packetizing the data.  This would
also
> >>> create a mismatch between the source and the receiver.  All of
this
> > is
> >>> avoided if we define the bit rate to be the media rate.
> >>
> >> Avoided: not really.  I'd say pushed off into some undefined
> > mechanism.
> >> Or, if not handled, you're not really solving the problem.
> >>
> >>> A third way a mismatch can be created is by encryption, where an
> >>> encryption pad is added (or possibly removed) at the campus
> >>> edge.  So
> > I'd
> >>> also want that RTP padding to be excluded from the definition (not
> > just
> >>> the headers).
> >>
> >> And again, how does the receiver know this to include it in the
TIAS
> >> calculation?  If this is an RTP/RTCP-aware midbox, it could adjust
BW
> >> values - if *everything* that can modify bandwidth is aware and
> > handles
> >> TIAS in offers and TMMBR, you could adjust TIAS by (maxprate *
> >> packet_delta), but in reality I don't see this happening.  BTW, any
> >> end-to-end signalling or media encryption will cause a major
headache
> > here
> >> - the midbox can't see/modify these values.  At best it could in
some
> >> cases
> >> signal the modification separately or in a separate tag at call
> >> setup,
> > but
> >> that's not an option with current protocols.
> >>
> >>> Of course, we'd also prefer to keep it as media because that is
what
> > both
> >>> H.323 and H.320 do and part of the usage of this command is to
adapt
> >> rates
> >>> between different transport channels.
> >>
> >> I'd say then push the burden of converting to bandwidth into media
> > rate
> >> onto the converter, not into every endpoint (especially since using
> > these
> >> conversions seems to require either a lot of assumptions or
> > potentially
> >> wastes bandwidth).
> >>
> >> I think I'm pretty much in agreement with Magnus here.
> >>
> >> Magnus also writes:
> >>>> Guido's idea of including the average packet overhead might
> > actually
> >> not
> >>>> be a bad one. As that would allow the sender to take into
> > consideration
> >>>> the per packet overhead seen by the TMMBR sending receiver. I
would
> >>>> define that overhead as the number of bytes in addition to RTP
> > payload.
> >>>> The reason to include the RTP header itself is that if there are
> > some
> >>>> translator or mixer doing something to expand the RTP header.
> >>
> >> This speaks to my comment above about finding a way to signal
> >> overhead
> >> separate from link bandwidth.
> >>
> >> --
> >> Randell Jesup, Worldgate (developers of the Ojo videophone),
ex-Amiga
> > OS
> >> team
> >> rjesup@wgate.com
> >> "The fetters imposed on liberty at home have ever been forged out
of
> > the
> >> weapons
> >> provided for defence against real, pretended, or imaginary dangers
> > from
> >> abroad."
> >> 		- James Madison, 4th US president (1751-1836)
> >
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www1.ietf.org/mailman/listinfo/avt


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



From avt-bounces@ietf.org Mon Feb 12 15:27:24 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGhks-0004Cu-F1; Mon, 12 Feb 2007 15:26:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGhkq-0004CT-SJ
	for avt@ietf.org; Mon, 12 Feb 2007 15:26:28 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGhkp-0003c5-5e
	for avt@ietf.org; Mon, 12 Feb 2007 15:26:28 -0500
Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l1CKQLhN022277
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 12 Feb 2007 12:26:21 -0800
Received: from sanexcas01.na.qualcomm.com (sanexcas01.qualcomm.com
	[172.30.36.175])
	by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l1CKQJQB029896;
	Mon, 12 Feb 2007 12:26:19 -0800 (PST)
Received: from NAEX01.qualcomm.com ([129.46.51.60]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Feb 2007 12:26:19 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] CCM draft review -- should "bandwidth" include
	theheaderoverhead
Date: Mon, 12 Feb 2007 12:26:18 -0800
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B028B05AB@NAEX01.na.qualcomm.com>
In-Reply-To: <10E7D146-0080-420A-BEF4-44C22DD7BAE0@stewe.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] CCM draft review -- should "bandwidth" include
	theheaderoverhead
Thread-Index: AcdOqKXT/ObPRsGgTsy0VdLKT8qOUQAOfR1g
References: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com>
	<10E7D146-0080-420A-BEF4-44C22DD7BAE0@stewe.org>
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: "Stephan Wenger" <stewe@stewe.org>, "Even, Roni" <roni.even@polycom.co.il>
X-OriginalArrivalTime: 12 Feb 2007 20:26:19.0051 (UTC)
	FILETIME=[0D91AFB0:01C74EE4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f0b5a4216bfa030ed8a6f68d1833f8ae
Cc: Randell Jesup <rjesup@wgate.com>,
	Magnus Westerlund <magnus.westerlund@ericsson.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

That doesn't sound good to me. It complicates the definition and
confuses the implementers on what to use and when.=20

Just one definition for TMMBR would be cleaner. Majority is towards
using it as pure media bitrate.=20

I don't think 3GPP SA4 understand transport details that well as it is
not their core area. They depend on IETF to decide what is good in
general.

Thanks,
Hari

> -----Original Message-----
> From: Stephan Wenger [mailto:stewe@stewe.org]
> Sent: Monday, February 12, 2007 5:07 AM
> To: Even, Roni
> Cc: Randell Jesup; Magnus Westerlund; avt@ietf.org
> Subject: Re: [AVT] CCM draft review -- should "bandwidth" include
> theheaderoverhead
>=20
> Folks,
>=20
> I have a proposal in the best tradition of ITU-T standardization :-):
> let's do it both.
>=20
> Roni has compelling arguments, I believe, for the interpretation of
> the TMMBR bitrate as the codec bitrate only.  I agree with him that
> using the codec bitrate opens cross-protocol application spaces that
> would otherwise be closed.  And, the codec bitrate is not affected by
> ROHC, IPv4/v6 issues, and so on.
>=20
> Magnus and others have suggested that including the header overhead
> makes sense as well, almost certainly for all-IP scenarios.  It's
> also what most folks assume in 3GPP SA4, which is going to be the
> first "customer" for TMMBR.
>=20
> So let's do it both.  We can signal the interpretation by a bit in
> the header (sliced off from the bitrate---there are enough bits), or
> we can make this dependent on signaling.  I have a slight preference
> for the latter.
>=20
> How does this sound?
>=20
> Regards,
> Stepha
>=20
>=20
> On Feb 12, 2007, at 11:32 AM, Even, Roni wrote:
>=20
> > Randell,
> > I think part of the discussion is because there is a lack of
> > application
> > usage.
> > For example, on a gateway between H.320 and SIP you need to limit
the
> > codec BW bellow the circuit switch rate. Same for a mixed conference
> > that has ISDN as well as SIP or H.323 parties.
> > This is why in H.323 and H.320 the rate is the codec rate
> > Roni Even
> >
> >> -----Original Message-----
> >> From: Randell Jesup [mailto:rjesup@wgate.com]
> >> Sent: Sunday, February 11, 2007 6:26 PM
> >> To: Even, Roni
> >> Cc: Magnus Westerlund; Stephan Wenger; avt@ietf.org
> >> Subject: Re: [AVT] CCM draft review -- should "bandwidth" include
the
> >> headeroverhead
> >>
> >> "Even, Roni" <roni.even@polycom.co.il> writes:
> >>> This is our view about why to use the codec bit rate and not any
> >>> overhead. We have to remember that this is mostly for video who
does
> > not
> >>> have a fixed frame size and that packets can be larger than MTU
size
> > and
> >>> thus may be broken differently based on implementations.
> >>
> >> Which is why TIAS (especially with TMMBR) is fundamentally broken
for
> >> offer/answer.  TIAS allows setting the max packet rate - fine for a
> >> declarative use, but for offer/answer, it means that the receiver
> > knows
> >> the
> >> actual bandwidth (typically configured - "I have a 1Mbps
downstream",
> >> perhaps measured/probed, but usually NOT probed end-to-end to the
> > sender),
> >> it must (to send TIAS) follow RFC 3890 #6.4 in reverse, using a
> >> (high)
> >> guess at maxprate.  When done, you basically have
> >> TIAS =3D BW - (maxprate*hsize).
> >>
> >> So the sender limits their codec to TIAS, and probably uses a lot
> >> less
> >> than
> >> maxprate packets, wasting that bandwidth.  If maxprate was chosen
too
> > low,
> >> the sender might have to (for video) reduce frame rate, especially
if
> > (as
> >> you mention) the sender wants to send more packets than the
receiver
> >> anticipates.  If the sender goes over maxprate, it might work, and
> > might
> >> not, and there's no way for the sender to estimate how much to
reduce
> > the
> >> TIAS amount by other than guessing.
> >>
> >> I think b=3DAS (etc) make more sense; the sender knows the actual
> >> prate,
> >> size
> >> of any headers it sends, and so can make best use of of the
available
> >> bits.
> >> If we need to know any additional header/etc modifications
inbetween
> > the
> >> sender and receiver, then we should find a mechanism to discover
> > and/or
> >> signal that directly.
> >>
> >>> For one thing, the amount of data in the headers depends on
whether
> >> header
> >>> compression is in use.  Since header compression can be applied
(or
> >>> removed) anywhere along the path, the amount of overhead seen by
the
> >>> receiver might be different than the overhead seen by the
> > transmitter.
> >>
> >> And how does the receiver making an offer or answer determine this?
> > The
> >> receiver typically only knows the last-link settings.
> >>
> >>> Another reason is that an intermediate device (gateways, proxies,
or
> >> other
> >>> RTP media engine) might be re-packetizing the data.  This would
also
> >>> create a mismatch between the source and the receiver.  All of
this
> > is
> >>> avoided if we define the bit rate to be the media rate.
> >>
> >> Avoided: not really.  I'd say pushed off into some undefined
> > mechanism.
> >> Or, if not handled, you're not really solving the problem.
> >>
> >>> A third way a mismatch can be created is by encryption, where an
> >>> encryption pad is added (or possibly removed) at the campus
> >>> edge.  So
> > I'd
> >>> also want that RTP padding to be excluded from the definition (not
> > just
> >>> the headers).
> >>
> >> And again, how does the receiver know this to include it in the
TIAS
> >> calculation?  If this is an RTP/RTCP-aware midbox, it could adjust
BW
> >> values - if *everything* that can modify bandwidth is aware and
> > handles
> >> TIAS in offers and TMMBR, you could adjust TIAS by (maxprate *
> >> packet_delta), but in reality I don't see this happening.  BTW, any
> >> end-to-end signalling or media encryption will cause a major
headache
> > here
> >> - the midbox can't see/modify these values.  At best it could in
some
> >> cases
> >> signal the modification separately or in a separate tag at call
> >> setup,
> > but
> >> that's not an option with current protocols.
> >>
> >>> Of course, we'd also prefer to keep it as media because that is
what
> > both
> >>> H.323 and H.320 do and part of the usage of this command is to
adapt
> >> rates
> >>> between different transport channels.
> >>
> >> I'd say then push the burden of converting to bandwidth into media
> > rate
> >> onto the converter, not into every endpoint (especially since using
> > these
> >> conversions seems to require either a lot of assumptions or
> > potentially
> >> wastes bandwidth).
> >>
> >> I think I'm pretty much in agreement with Magnus here.
> >>
> >> Magnus also writes:
> >>>> Guido's idea of including the average packet overhead might
> > actually
> >> not
> >>>> be a bad one. As that would allow the sender to take into
> > consideration
> >>>> the per packet overhead seen by the TMMBR sending receiver. I
would
> >>>> define that overhead as the number of bytes in addition to RTP
> > payload.
> >>>> The reason to include the RTP header itself is that if there are
> > some
> >>>> translator or mixer doing something to expand the RTP header.
> >>
> >> This speaks to my comment above about finding a way to signal
> >> overhead
> >> separate from link bandwidth.
> >>
> >> --
> >> Randell Jesup, Worldgate (developers of the Ojo videophone),
ex-Amiga
> > OS
> >> team
> >> rjesup@wgate.com
> >> "The fetters imposed on liberty at home have ever been forged out
of
> > the
> >> weapons
> >> provided for defence against real, pretended, or imaginary dangers
> > from
> >> abroad."
> >> 		- James Madison, 4th US president (1751-1836)
> >
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www1.ietf.org/mailman/listinfo/avt
>=20
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

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



From avt-bounces@ietf.org Mon Feb 12 15:46:55 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGi3z-0005sk-D8; Mon, 12 Feb 2007 15:46:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGi3y-0005qr-3H
	for avt@ietf.org; Mon, 12 Feb 2007 15:46:14 -0500
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HGi3w-0008NH-SO for avt@ietf.org; Mon, 12 Feb 2007 15:46:14 -0500
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 12 Feb 2007 15:46:08 -0500
To: "Even, Roni" <roni.even@polycom.co.il>
Subject: Re: [AVT] CCM draft review -- should "bandwidth" include the
	headeroverhead
References: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Mon, 12 Feb 2007 15:46:06 -0500
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com>
	(Roni Even's message of "Mon, 12 Feb 2007 11:32:53 +0200")
Message-ID: <ybumz3jumsx.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 12 Feb 2007 20:46:08.0566 (UTC)
	FILETIME=[D2934560:01C74EE6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Stephan Wenger <stewe@stewe.org>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

"Even, Roni" <roni.even@polycom.co.il> writes:

>Randell,
>I think part of the discussion is because there is a lack of application
>usage.
>For example, on a gateway between H.320 and SIP you need to limit the
>codec BW bellow the circuit switch rate. Same for a mixed conference
>that has ISDN as well as SIP or H.323 parties.
>This is why in H.323 and H.320 the rate is the codec rate

Ok; H.320<->SIP gateway use has a reason for having TIAS for reception, but
not in place of (or used for) link bandwidth specifications.  In this case,
TIAS is specifying an aspect of the decoder or a link on the far side of
the device negotiating; it's not attempting to convey anything about the
link between the H320 gateway and the SIP device.  Normally (to my mind at
least), b=AS (etc) apply to telling the sender the configured or probed
link bandwidth available.  So I could see providing TIAS _and_ AS or CT.

This may be an aspect of the fact that I (and a lot of others) are focused
on pure SIP UA-to-UA unicast (i.e. phone call) scenarios, while you may
well be much more focused on H.323/etc interop and conferencing.

TMMBR (the original point of discusson here) is speaking to a link
restriction, and so I still feel that there should not be an assumption
that TMMBR should be applied to (implied) TIAS values, it should be applied
to link-bandwidth.  The argument being made is that TMMBR should be in
terms of TIAS, even if TIAS was not the original negotiation.

If there are multiple b=*'s of different types, which one takes precedence?
My assertion (assuming multiple b='s are valid) is that TMMBR should apply
to link bandwidth values if present (b=AS or b=CT), and to TIAS only if
b=TIAS is the only bandwidth value specified.  If no b= value is specified,
then I'm not sure and I'd have to review the spec.

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


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



From avt-bounces@ietf.org Mon Feb 12 16:10:40 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGiQU-0002h2-3K; Mon, 12 Feb 2007 16:09:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGiQS-0002ed-FO; Mon, 12 Feb 2007 16:09:28 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HGiQL-0003qu-V2; Mon, 12 Feb 2007 16:09:28 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	717A2204F8; Mon, 12 Feb 2007 22:09:19 +0100 (CET)
X-AuditID: c1b4fb3e-afed3bb0000007e1-1d-45d0d77fa27e 
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	54D71200DB; Mon, 12 Feb 2007 22:09:19 +0100 (CET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Feb 2007 22:09:19 +0100
Received: from [138.85.12.13] ([138.85.12.13]) by esealmw128.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Feb 2007 22:09:18 +0100
Message-ID: <45D0D77F.8030705@ericsson.com>
Date: Mon, 12 Feb 2007 22:09:19 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>,  behave@ietf.org
Content-Type: multipart/mixed; boundary="------------020108020609070503020100"
X-OriginalArrivalTime: 12 Feb 2007 21:09:18.0823 (UTC)
	FILETIME=[0F3BA770:01C74EEA]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Cc: 
Subject: [AVT] [Fwd: Last Call: draft-wing-behave-symmetric-rtprtcp (Common
 Local
 Transmit and Receive Ports (Symmetric RTP)) to Informational RFC]
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

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

Hi,

This document has been raised before in both AVT and BEHAVE WG. I have 
chosen to AD sponsor this document for publication as informational 
status because it seems to be of general interest. You have 4 weeks to 
provide any comments on the document.

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

--------------020108020609070503020100
Content-Type: message/rfc822;
	name*0="Last Call: draft-wing-behave-symmetric-rtprtcp (Common Local
	Tr"; 
	name*1="ansmit and Receive Ports (Symmetric RTP)) to Informational RFC"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
	filename*0="Last Call: draft-wing-behave-symmetric-rtprtcp (Common
	Local"; 
	filename*1=" Transmit and Receive Ports (Symmetric RTP)) to
	Information"; filename*2="al RFC"

Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw103.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Feb 2007 21:49:27 +0100
Received: from mailgw1.ericsson.se ([193.180.251.45]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Feb 2007 21:49:27 +0100
Received: from mailgw1.ericsson.se (unknown [127.0.0.1])
	by mailgw1.ericsson.se (Symantec Mail Security) with ESMTP id
	50A0C402E5; Mon, 12 Feb 2007 21:49:27 +0100 (CET)
X-AuditID: c1b4fb2d-b05a6bb000003506-68-45d0d2d68629 
Received: from megatron.ietf.org (lists.ietf.ORG [156.154.16.145])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mailgw1.ericsson.se (Symantec Mail Security) with ESMTP id
	CD9914033F; Mon, 12 Feb 2007 21:49:26 +0100 (CET)
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGi39-00057P-Ug; Mon, 12 Feb 2007 15:45:23 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGi38-00057D-6Q
	for ietf-announce@ietf.org; Mon, 12 Feb 2007 15:45:22 -0500
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HGi37-0001WH-UO
	for ietf-announce@ietf.org; Mon, 12 Feb 2007 15:45:22 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id DD1AB2AD13
	for <ietf-announce@ietf.org>; Mon, 12 Feb 2007 20:44:51 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HGi2d-0006lu-Lc
	for ietf-announce@ietf.org; Mon, 12 Feb 2007 15:44:51 -0500
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1HGi2d-0006lu-Lc@stiedprstage1.ietf.org>
Date: Mon, 12 Feb 2007 15:44:51 -0500
X-Spam-Score: -2.8 (--)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Subject: Last Call: draft-wing-behave-symmetric-rtprtcp (Common Local 
	Transmit and Receive Ports (Symmetric RTP)) to Informational RFC
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ietf@ietf.org
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>,
	<mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>,
	<mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org
X-Brightmail-Tracker: AAAAAA==
Return-Path: ietf-announce-bounces@ietf.org
X-OriginalArrivalTime: 12 Feb 2007 20:49:27.0392 (UTC)
	FILETIME=[4915B600:01C74EE7]

The IESG has received a request from an individual submitter to consider
the following document:

- 'Common Local Transmit and Receive Ports (Symmetric RTP) '
   <draft-wing-behave-symmetric-rtprtcp-01.txt> as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2007-03-12. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-wing-behave-symmetric-rtprtcp-01.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=13165&rfc_flag=0


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce


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

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

--------------020108020609070503020100--




From avt-bounces@ietf.org Mon Feb 12 16:13:02 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGiTF-0005Jz-Iz; Mon, 12 Feb 2007 16:12:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGiTE-0005JA-9S
	for avt@ietf.org; Mon, 12 Feb 2007 16:12:20 -0500
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HGiTD-0004AP-2h for avt@ietf.org; Mon, 12 Feb 2007 16:12:20 -0500
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 12 Feb 2007 16:12:19 -0500
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>
Subject: Re: [AVT] CCM draft review -- should "bandwidth" include
	theheaderoverhead
References: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com>
	<10E7D146-0080-420A-BEF4-44C22DD7BAE0@stewe.org>
	<2CA3E1B6CEC064449CAA7D0FAB46079B028B05AB@NAEX01.na.qualcomm.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Mon, 12 Feb 2007 16:12:17 -0500
In-Reply-To: <2CA3E1B6CEC064449CAA7D0FAB46079B028B05AB@NAEX01.na.qualcomm.com>
	(Harikishan
	Desineni's message of "Mon, 12 Feb 2007 12:26:18 -0800")
Message-ID: <ybud54fulla.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 12 Feb 2007 21:12:19.0024 (UTC)
	FILETIME=[7AA42500:01C74EEA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: "Even, Roni" <roni.even@polycom.co.il>, Stephan Wenger <stewe@stewe.org>,
	avt@ietf.org, Magnus Westerlund <magnus.westerlund@ericsson.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

"Desineni, Harikishan" <hdesinen@qualcomm.com> writes:
>That doesn't sound good to me. It complicates the definition and
>confuses the implementers on what to use and when. 
>
>Just one definition for TMMBR would be cleaner. Majority is towards
>using it as pure media bitrate. 

I don't consider it cleaner if I have to convert my b=AS/CT (somehow...)
into b=TIAS, apply TMMBR, and re-convert, and end up wasting bits because
of assumptions about maxprate/etc.  And I'd dispute the "majority"
assertion.  :-) But I'm a SIP "phone" guy, not a conferencing/H.* interop
guy.

>I don't think 3GPP SA4 understand transport details that well as it is
>not their core area. They depend on IETF to decide what is good in
>general.

I'd be a little cautious - I'm not sure that if we define it in a way they
don't like (not useful to them, or too hard to use), they may decide to
ignore the IETF.  Perhaps not, I don't have any visibility beyond the
message's I've read here.  I wouldn't *assume* they'll happily implement
things if it doesn't fit into their needs - I certainly wouldn't; I'd say
screw it and implement what I need using APP or some such.  And that
fragmentation doesn't help anyone.

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


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



From avt-bounces@ietf.org Mon Feb 12 16:39:21 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGisb-0003Ww-BU; Mon, 12 Feb 2007 16:38:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGisa-0003WV-Fw
	for avt@ietf.org; Mon, 12 Feb 2007 16:38:32 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGisQ-0001x7-Sw
	for avt@ietf.org; Mon, 12 Feb 2007 16:38:32 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	48C2120F21; Mon, 12 Feb 2007 22:38:18 +0100 (CET)
X-AuditID: c1b4fb3e-ae6d0bb0000007e1-f1-45d0de4a784c 
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	2F50B2056B; Mon, 12 Feb 2007 22:38:18 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Feb 2007 22:38:17 +0100
Received: from [138.85.12.13] ([138.85.12.13]) by esealmw129.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Feb 2007 22:38:17 +0100
Message-ID: <45D0DE49.4060105@ericsson.com>
Date: Mon, 12 Feb 2007 22:38:17 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Stephan Wenger <stewe@stewe.org>
Subject: Re: [AVT] CCM draft review -- should "bandwidth" include the
	headeroverhead
References: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com>
	<10E7D146-0080-420A-BEF4-44C22DD7BAE0@stewe.org>
In-Reply-To: <10E7D146-0080-420A-BEF4-44C22DD7BAE0@stewe.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Feb 2007 21:38:17.0331 (UTC)
	FILETIME=[1B76EC30:01C74EEE]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: Randell Jesup <rjesup@wgate.com>, "Even, Roni" <roni.even@polycom.co.il>,
	avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Stephan Wenger skrev:
> Folks,
> 
> I have a proposal in the best tradition of ITU-T standardization :-): 
> let's do it both.
> 
> Roni has compelling arguments, I believe, for the interpretation of the 
> TMMBR bitrate as the codec bitrate only.  I agree with him that using 
> the codec bitrate opens cross-protocol application spaces that would 
> otherwise be closed.  And, the codec bitrate is not affected by ROHC, 
> IPv4/v6 issues, and so on.
> 
> Magnus and others have suggested that including the header overhead 
> makes sense as well, almost certainly for all-IP scenarios.  It's also 
> what most folks assume in 3GPP SA4, which is going to be the first 
> "customer" for TMMBR.
> 
> So let's do it both.  We can signal the interpretation by a bit in the 
> header (sliced off from the bitrate---there are enough bits), or we can 
> make this dependent on signaling.  I have a slight preference for the 
> latter.
> 
> How does this sound?
> 

Not, good at all. This will only be confusing. Lets sort this discussion 
out and determine what we actually want to signal.

Roni, a media bit-rate without any indication of the amount of header 
overhead you be worse than a gross bit-rate value. The reason is that 
what you as a receiver know something about is the gross bit-rate. The 
receiver has no knowledge about how much overhead the sender will put on 
each packet. Thus a media bit-rate is hard to calculate for the receiver 
as it varies in two dimensions, packet rate and per packet overhead. 
Both can be changed by the sender.

Regarding the MTU reasoning. You really should avoid IP fragmentation. 
And therefore PMTUD should be run. As I see it one could run 
draft-ietf-pmtud-method over RTP simply by selecting to use the RTCP XR 
packet loss vector to inform the sender about which packets gets 
through. Also the NACK format would work. As RTP is designed to aim for 
the working point that doesn't fragment using fragmentation as an 
argument why media bit-rate is better is strange. If you have 
fragmentation problems, deal with that.

When it comes to repacketization or transcoding, then the TMMBR will 
need to be rewritten or absorbed by that entity. Due to the reason that 
it is that middelbox that determines the bit-rate forwarded to the 
receiver. We intend to include clearer guidance on this into the CCM 
draft, instead of what was present in the topologies.

I will try to write an analysis for the three proposals on the table.

TMMBR report:
a) Media Bit-rate
b) Gross bit-rate on IP-level
c) Gross bit-rate on IP-level and the amount of overhead seen in the 
received packets.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



From avt-bounces@ietf.org Mon Feb 12 16:50:32 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGj33-0000lR-VV; Mon, 12 Feb 2007 16:49:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGj32-0000lB-IX
	for avt@ietf.org; Mon, 12 Feb 2007 16:49:20 -0500
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGj2z-0003Zu-Up
	for avt@ietf.org; Mon, 12 Feb 2007 16:49:20 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [AVT] CCM draft review -- should "bandwidth" include
	theheaderoverhead
Date: Mon, 12 Feb 2007 23:49:16 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C730CD4@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] CCM draft review -- should "bandwidth" include
	theheaderoverhead
Thread-Index: AcdO6o210FEwyaRwQyuaVcolBHts1AABFfQ/
References: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com><10E7D146-0080-420A-BEF4-44C22DD7BAE0@stewe.org><2CA3E1B6CEC064449CAA7D0FAB46079B028B05AB@NAEX01.na.qualcomm.com>
	<ybud54fulla.fsf@jesup.eng.wgate.com>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Randell Jesup" <rjesup@wgate.com>,
	"Desineni, Harikishan" <hdesinen@qualcomm.com>
X-Spam-Score: 0.6 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Stephan Wenger <stewe@stewe.org>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1570789611=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1570789611==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C74EEF.A456F868"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C74EEF.A456F868
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Hi,
I think you have to know ow to convert from b=3D to the codec rate =
anyhow, otherwise how can you know how much to allow the encoder to use =
in term of bit rate.
On the receiver side, the way I see it is that once you establish the =
connection and want to use TMMBR you already know the codec rate you =
receive, if you decode so you can reduce the rate based on this =
information.
Roni

________________________________

=EE=E0=FA: Randell Jesup [mailto:rjesup@wgate.com]
=F0=F9=EC=E7: =E1 12/02/2007 23:12
=E0=EC: Desineni, Harikishan
=F2=E5=FA=F7 =EC=E9=E3=E9=F2=E4: Stephan Wenger; Even, Roni; Magnus =
Westerlund; avt@ietf.org
=F0=E5=F9=E0: Re: [AVT] CCM draft review -- should "bandwidth" include =
theheaderoverhead



"Desineni, Harikishan" <hdesinen@qualcomm.com> writes:
>That doesn't sound good to me. It complicates the definition and
>confuses the implementers on what to use and when.
>
>Just one definition for TMMBR would be cleaner. Majority is towards
>using it as pure media bitrate.

I don't consider it cleaner if I have to convert my b=3DAS/CT =
(somehow...)
into b=3DTIAS, apply TMMBR, and re-convert, and end up wasting bits =
because
of assumptions about maxprate/etc.  And I'd dispute the "majority"
assertion.  :-) But I'm a SIP "phone" guy, not a conferencing/H.* =
interop
guy.

>I don't think 3GPP SA4 understand transport details that well as it is
>not their core area. They depend on IETF to decide what is good in
>general.

I'd be a little cautious - I'm not sure that if we define it in a way =
they
don't like (not useful to them, or too hard to use), they may decide to
ignore the IETF.  Perhaps not, I don't have any visibility beyond the
message's I've read here.  I wouldn't *assume* they'll happily implement
things if it doesn't fit into their needs - I certainly wouldn't; I'd =
say
screw it and implement what I need using APP or some such.  And that
fragmentation doesn't help anyone.

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




------_=_NextPart_001_01C74EEF.A456F868
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Drtl><HEAD><TITLE>Re: [AVT] CCM draft review -- should =
"bandwidth" include theheaderoverhead</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.3020" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 =
size=3D2>Hi,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>I think you have to know ow =
to convert from b=3D to the codec rate anyhow, otherwise how can you =
know how much to allow the encoder to use&nbsp;in term of bit =
rate.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>On the receiver side, the way =
I see it is that once you establish the connection and want to use TMMBR =
you already know the codec rate you receive, if you decode so you can =
reduce the rate based on this information.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Roni</FONT></DIV>=0A=
<DIV dir=3Drtl><BR></DIV>=0A=
<DIV dir=3Drtl>=0A=
<HR tabIndex=3D-1>=0A=
</DIV>=0A=
<DIV dir=3Drtl><FONT face=3DTahoma size=3D2><B>=EE=E0=FA:</B> Randell =
Jesup [mailto:rjesup@wgate.com]<BR><B>=F0=F9=EC=E7:</B> =E1 12/02/2007 =
23:12<BR><B>=E0=EC:</B> Desineni, Harikishan<BR><B>=F2=E5=FA=F7 =
=EC=E9=E3=E9=F2=E4:</B> Stephan Wenger; Even, Roni; Magnus Westerlund; =
avt@ietf.org<BR><B>=F0=E5=F9=E0:</B> Re: [AVT] CCM draft review -- =
should "bandwidth" include theheaderoverhead<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>"Desineni, Harikishan" &lt;hdesinen@qualcomm.com&gt; =
writes:<BR>&gt;That doesn't sound good to me. It complicates the =
definition and<BR>&gt;confuses the implementers on what to use and =
when.<BR>&gt;<BR>&gt;Just one definition for TMMBR would be cleaner. =
Majority is towards<BR>&gt;using it as pure media bitrate.<BR><BR>I =
don't consider it cleaner if I have to convert my b=3DAS/CT =
(somehow...)<BR>into b=3DTIAS, apply TMMBR, and re-convert, and end up =
wasting bits because<BR>of assumptions about maxprate/etc.&nbsp; And I'd =
dispute the "majority"<BR>assertion.&nbsp; :-) But I'm a SIP "phone" =
guy, not a conferencing/H.* interop<BR>guy.<BR><BR>&gt;I don't think =
3GPP SA4 understand transport details that well as it is<BR>&gt;not =
their core area. They depend on IETF to decide what is good =
in<BR>&gt;general.<BR><BR>I'd be a little cautious - I'm not sure that =
if we define it in a way they<BR>don't like (not useful to them, or too =
hard to use), they may decide to<BR>ignore the IETF.&nbsp; Perhaps not, =
I don't have any visibility beyond the<BR>message's I've read =
here.&nbsp; I wouldn't *assume* they'll happily implement<BR>things if =
it doesn't fit into their needs - I certainly wouldn't; I'd say<BR>screw =
it and implement what I need using APP or some such.&nbsp; And =
that<BR>fragmentation doesn't help anyone.<BR><BR>--<BR>Randell Jesup, =
Worldgate (developers of the Ojo videophone), ex-Amiga OS =
team<BR>rjesup@wgate.com<BR>"The fetters imposed on liberty at home have =
ever been forged out of the weapons<BR>provided for defence against =
real, pretended, or imaginary dangers from =
abroad."<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - James Madison, 4th US =
president (1751-1836)<BR><BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C74EEF.A456F868--


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

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

--===============1570789611==--




From avt-bounces@ietf.org Mon Feb 12 16:53:12 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGj69-0002kb-Kx; Mon, 12 Feb 2007 16:52:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGj68-0002kW-9Q
	for avt@ietf.org; Mon, 12 Feb 2007 16:52:32 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGj66-000439-NU
	for avt@ietf.org; Mon, 12 Feb 2007 16:52:32 -0500
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l1CLqP6r022332
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 12 Feb 2007 13:52:26 -0800
Received: from SANEXCAS02.na.qualcomm.com (sanexcas02.qualcomm.com
	[172.30.36.176])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l1CLqPPI031930; Mon, 12 Feb 2007 13:52:25 -0800
Received: from NAEX01.qualcomm.com ([129.46.51.60]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Feb 2007 13:52:25 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] CCM draft review -- should "bandwidth" include
	theheaderoverhead
Date: Mon, 12 Feb 2007 13:52:22 -0800
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B028B05E2@NAEX01.na.qualcomm.com>
In-Reply-To: <ybumz3jumsx.fsf@jesup.eng.wgate.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] CCM draft review -- should "bandwidth" include
	theheaderoverhead
Thread-Index: AcdO54gF25FtknBQS5WwvArZhXDUdQAA9D7A
References: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com>
	<ybumz3jumsx.fsf@jesup.eng.wgate.com>
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: "Randell Jesup" <rjesup@wgate.com>, "Even, Roni" <roni.even@polycom.co.il>
X-OriginalArrivalTime: 12 Feb 2007 21:52:25.0370 (UTC)
	FILETIME=[14EF67A0:01C74EF0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Stephan Wenger <stewe@stewe.org>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org



> -----Original Message-----
> From: Randell Jesup [mailto:rjesup@wgate.com]
> Sent: Monday, February 12, 2007 12:46 PM
> To: Even, Roni
> Cc: Magnus Westerlund; Stephan Wenger; avt@ietf.org
> Subject: Re: [AVT] CCM draft review -- should "bandwidth" include
> theheaderoverhead
>=20
> "Even, Roni" <roni.even@polycom.co.il> writes:
>=20
> >Randell,
> >I think part of the discussion is because there is a lack of
application
> >usage.
> >For example, on a gateway between H.320 and SIP you need to limit the
> >codec BW bellow the circuit switch rate. Same for a mixed conference
> >that has ISDN as well as SIP or H.323 parties.
> >This is why in H.323 and H.320 the rate is the codec rate
>=20
> Ok; H.320<->SIP gateway use has a reason for having TIAS for
reception,
> but
> not in place of (or used for) link bandwidth specifications.  In this
case,
> TIAS is specifying an aspect of the decoder or a link on the far side
of
> the device negotiating; it's not attempting to convey anything about
the
> link between the H320 gateway and the SIP device.  Normally (to my
mind at
> least), b=3DAS (etc) apply to telling the sender the configured or
probed
> link bandwidth available.  So I could see providing TIAS _and_ AS or
CT.

Your point on "AS" is just your assumption and it is not defined that
way in RFC3550/3890. Following is the description of "AS" from 3890.

Sec 1.1.2, RFC 3890
"Application Specific Maximum: The Application Specific maximum
bandwidth is
indicated by the modifier "AS". The session bandwidth includes the
bandwidth that the RTP data traffic will consume, including the lower
layers, down to the IP layer. Therefore, the bandwidth is in most cases
calculated over RTP payload, RTP header, UDP, and IP, defined in RFC
2327 [1]."

It is bandwidth at IP level. IMO, "AS" inherently assumes some packet
rate. From the above text in RFC3890 AS is nothing but TIAS + BW for
packet overhead. BW for packet overhead should be assuming some packet
rate. Specifying bandwidth below IP (link bandwidth) may not be
architecturally pure. Usually SDP does not specify anything below IP.


>=20
> This may be an aspect of the fact that I (and a lot of others) are
focused
> on pure SIP UA-to-UA unicast (i.e. phone call) scenarios, while you
may
> well be much more focused on H.323/etc interop and conferencing.
>=20
> TMMBR (the original point of discusson here) is speaking to a link
> restriction, and so I still feel that there should not be an
assumption
> that TMMBR should be applied to (implied) TIAS values, it should be
> applied
> to link-bandwidth.

It is actually link restriction mapped to media restriction. As far as I
know, link bandwidth (below IP) does not fall in the scope of SDP or
RTCP.
One has to translate the link restriction (below IP) to media
restriction (above IP) and use it in RTCP/SDP. TIAS and maxprate gives
some estimation which is better than nothing. (TIAS,maxprate) is better
than AS. The reason being AS is hiding the max packet rate and actual
media rate.

[The following mostly applies to point to point topology]
(High value of) maxprate may result in bandwidth overallocation to some
extent but it is better than nothing. In fact, even if maxprate is
accurate it can still result in overallocation because the sender may
send at much lower media bit rate (than TIAS) while still using the
signaled maxprate. What the sender is actually planning to send at
(media send rate) is not captured in any SDP attribute. In a point to
point session, one has to note that link bandwidth limitation applies to
'send' direction as well and it is not limited to 'receive' direction.
Link bandwidth limitation in 'send' direction is possible for the same
reasons it is possible for link bandwidth limitation in 'receive'
direction (QoS changes forced by the cellular network in 'send'
direction of a stream)

Correct bandwidth needed for a stream:

(Actual max media bit rate + max header overhead bit rate)

Actual max media bit rate <=3D TIAS

Actual max media bit rate can be signaled in a new SDP attribute
('sendrate').=20


>  The argument being made is that TMMBR should be in
> terms of TIAS, even if TIAS was not the original negotiation.
>=20
> If there are multiple b=3D*'s of different types, which one takes
> precedence?
> My assertion (assuming multiple b=3D's are valid) is that TMMBR should
apply
> to link bandwidth values if present (b=3DAS or b=3DCT), and to TIAS =
only
if
> b=3DTIAS is the only bandwidth value specified.  If no b=3D value is
specified,
> then I'm not sure and I'd have to review the spec.
>=20
> --
> Randell Jesup, Worldgate (developers of the Ojo videophone), ex-Amiga
OS
> team
> rjesup@wgate.com
> "The fetters imposed on liberty at home have ever been forged out of
the
> weapons
> provided for defence against real, pretended, or imaginary dangers
from
> abroad."
> 		- James Madison, 4th US president (1751-1836)
>=20
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

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



From avt-bounces@ietf.org Mon Feb 12 17:07:49 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGjK1-0002Rs-Bi; Mon, 12 Feb 2007 17:06:53 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGjK0-0002Qs-1z
	for avt@ietf.org; Mon, 12 Feb 2007 17:06:52 -0500
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGjJz-0005ut-AS
	for avt@ietf.org; Mon, 12 Feb 2007 17:06:52 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [AVT] CCM draft review -- should "bandwidth" include the
	headeroverhead
Date: Tue, 13 Feb 2007 00:06:48 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C730CD5@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] CCM draft review -- should "bandwidth" include the
	headeroverhead
Thread-Index: AcdO7i+14cEEN8MtQVq/2x9dLLEl7AAAcOrp
References: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com>
	<10E7D146-0080-420A-BEF4-44C22DD7BAE0@stewe.org>
	<45D0DE49.4060105@ericsson.com>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>,
	"Stephan Wenger" <stewe@stewe.org>
X-Spam-Score: 0.6 (/)
X-Scan-Signature: a492040269d440726bfd84680622cee7
Cc: Randell Jesup <rjesup@wgate.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1478888381=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1478888381==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C74EF2.17A65758"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C74EF2.17A65758
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Magnus,
We are talking about TMMBR which happens after the receiver has already =
received media and can know what is the payload bit rate.
=20
As for fragmentation you should know that knowing the path MTU do not =
make each sender break a frame to the same sizes. Example MTU=3D500 =
frame =3D 800. can be broken to 400 and 400 or 300, 300 and 200 based on =
policy for breaking on macro block or GOB boundary or any other =
algorithm as long as smaller than MTU.
=20
=20
Repacketization in a middlebox can happen between two networks with =
different MTUs and the middle box cannot reduce the rate (it does not =
transcode). RTCP may flow end to end (this is a viable topology in the =
topolgy draft).
=20
=20
Roni

________________________________

=EE=E0=FA: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
=F0=F9=EC=E7: =E1 12/02/2007 23:38
=E0=EC: Stephan Wenger
=F2=E5=FA=F7 =EC=E9=E3=E9=F2=E4: Even, Roni; Randell Jesup; avt@ietf.org
=F0=E5=F9=E0: Re: [AVT] CCM draft review -- should "bandwidth" include =
the headeroverhead



Stephan Wenger skrev:
> Folks,
>
> I have a proposal in the best tradition of ITU-T standardization :-):
> let's do it both.
>
> Roni has compelling arguments, I believe, for the interpretation of =
the
> TMMBR bitrate as the codec bitrate only.  I agree with him that using
> the codec bitrate opens cross-protocol application spaces that would
> otherwise be closed.  And, the codec bitrate is not affected by ROHC,
> IPv4/v6 issues, and so on.
>
> Magnus and others have suggested that including the header overhead
> makes sense as well, almost certainly for all-IP scenarios.  It's also
> what most folks assume in 3GPP SA4, which is going to be the first
> "customer" for TMMBR.
>
> So let's do it both.  We can signal the interpretation by a bit in the
> header (sliced off from the bitrate---there are enough bits), or we =
can
> make this dependent on signaling.  I have a slight preference for the
> latter.
>
> How does this sound?
>

Not, good at all. This will only be confusing. Lets sort this discussion
out and determine what we actually want to signal.

Roni, a media bit-rate without any indication of the amount of header
overhead you be worse than a gross bit-rate value. The reason is that
what you as a receiver know something about is the gross bit-rate. The
receiver has no knowledge about how much overhead the sender will put on
each packet. Thus a media bit-rate is hard to calculate for the receiver
as it varies in two dimensions, packet rate and per packet overhead.
Both can be changed by the sender.

Regarding the MTU reasoning. You really should avoid IP fragmentation.
And therefore PMTUD should be run. As I see it one could run
draft-ietf-pmtud-method over RTP simply by selecting to use the RTCP XR
packet loss vector to inform the sender about which packets gets
through. Also the NACK format would work. As RTP is designed to aim for
the working point that doesn't fragment using fragmentation as an
argument why media bit-rate is better is strange. If you have
fragmentation problems, deal with that.

When it comes to repacketization or transcoding, then the TMMBR will
need to be rewritten or absorbed by that entity. Due to the reason that
it is that middelbox that determines the bit-rate forwarded to the
receiver. We intend to include clearer guidance on this into the CCM
draft, instead of what was present in the topologies.

I will try to write an analysis for the three proposals on the table.

TMMBR report:
a) Media Bit-rate
b) Gross bit-rate on IP-level
c) Gross bit-rate on IP-level and the amount of overhead seen in the
received packets.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------



------_=_NextPart_001_01C74EF2.17A65758
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Drtl><HEAD><TITLE>Re: [AVT] CCM draft review -- should =
"bandwidth" include the headeroverhead</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.3020" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 =
size=3D2>Magnus,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>We are talking about TMMBR =
which happens after the receiver has already received media and can know =
what is the payload bit rate.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>As for fragmentation you =
should know that knowing the path MTU do not make each sender break a =
frame to the same sizes. Example MTU=3D500 frame =3D 800. can be broken =
to 400 and 400 or 300, 300 and 200 based on policy for breaking on macro =
block or GOB boundary or any other algorithm as long as smaller than =
MTU.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Repacketization in a =
middlebox can happen between two networks with different MTUs and the =
middle box cannot reduce the rate (it does not transcode). RTCP may flow =
end to end (this is a viable topology in the topolgy draft).</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Roni</FONT></DIV>=0A=
<DIV dir=3Drtl><BR></DIV>=0A=
<DIV dir=3Drtl>=0A=
<HR tabIndex=3D-1>=0A=
</DIV>=0A=
<DIV dir=3Drtl><FONT face=3DTahoma size=3D2><B>=EE=E0=FA:</B> Magnus =
Westerlund =
[mailto:magnus.westerlund@ericsson.com]<BR><B>=F0=F9=EC=E7:</B> =E1 =
12/02/2007 23:38<BR><B>=E0=EC:</B> Stephan Wenger<BR><B>=F2=E5=FA=F7 =
=EC=E9=E3=E9=F2=E4:</B> Even, Roni; Randell Jesup; =
avt@ietf.org<BR><B>=F0=E5=F9=E0:</B> Re: [AVT] CCM draft review -- =
should "bandwidth" include the headeroverhead<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Stephan Wenger skrev:<BR>&gt; Folks,<BR>&gt;<BR>&gt; I =
have a proposal in the best tradition of ITU-T standardization =
:-):<BR>&gt; let's do it both.<BR>&gt;<BR>&gt; Roni has compelling =
arguments, I believe, for the interpretation of the<BR>&gt; TMMBR =
bitrate as the codec bitrate only.&nbsp; I agree with him that =
using<BR>&gt; the codec bitrate opens cross-protocol application spaces =
that would<BR>&gt; otherwise be closed.&nbsp; And, the codec bitrate is =
not affected by ROHC,<BR>&gt; IPv4/v6 issues, and so on.<BR>&gt;<BR>&gt; =
Magnus and others have suggested that including the header =
overhead<BR>&gt; makes sense as well, almost certainly for all-IP =
scenarios.&nbsp; It's also<BR>&gt; what most folks assume in 3GPP SA4, =
which is going to be the first<BR>&gt; "customer" for =
TMMBR.<BR>&gt;<BR>&gt; So let's do it both.&nbsp; We can signal the =
interpretation by a bit in the<BR>&gt; header (sliced off from the =
bitrate---there are enough bits), or we can<BR>&gt; make this dependent =
on signaling.&nbsp; I have a slight preference for the<BR>&gt; =
latter.<BR>&gt;<BR>&gt; How does this sound?<BR>&gt;<BR><BR>Not, good at =
all. This will only be confusing. Lets sort this discussion<BR>out and =
determine what we actually want to signal.<BR><BR>Roni, a media bit-rate =
without any indication of the amount of header<BR>overhead you be worse =
than a gross bit-rate value. The reason is that<BR>what you as a =
receiver know something about is the gross bit-rate. The<BR>receiver has =
no knowledge about how much overhead the sender will put on<BR>each =
packet. Thus a media bit-rate is hard to calculate for the =
receiver<BR>as it varies in two dimensions, packet rate and per packet =
overhead.<BR>Both can be changed by the sender.<BR><BR>Regarding the MTU =
reasoning. You really should avoid IP fragmentation.<BR>And therefore =
PMTUD should be run. As I see it one could =
run<BR>draft-ietf-pmtud-method over RTP simply by selecting to use the =
RTCP XR<BR>packet loss vector to inform the sender about which packets =
gets<BR>through. Also the NACK format would work. As RTP is designed to =
aim for<BR>the working point that doesn't fragment using fragmentation =
as an<BR>argument why media bit-rate is better is strange. If you =
have<BR>fragmentation problems, deal with that.<BR><BR>When it comes to =
repacketization or transcoding, then the TMMBR will<BR>need to be =
rewritten or absorbed by that entity. Due to the reason that<BR>it is =
that middelbox that determines the bit-rate forwarded to =
the<BR>receiver. We intend to include clearer guidance on this into the =
CCM<BR>draft, instead of what was present in the topologies.<BR><BR>I =
will try to write an analysis for the three proposals on the =
table.<BR><BR>TMMBR report:<BR>a) Media Bit-rate<BR>b) Gross bit-rate on =
IP-level<BR>c) Gross bit-rate on IP-level and the amount of overhead =
seen in the<BR>received packets.<BR><BR>Cheers<BR><BR>Magnus =
Westerlund<BR><BR>IETF Transport Area Director &amp; TSVWG =
Chair<BR>----------------------------------------------------------------=
------<BR>Multimedia Technologies, Ericsson Research =
EAB/TVA/A<BR>------------------------------------------------------------=
----------<BR>Ericsson =
AB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; | Phone +46 8 4048287<BR>Torshamsgatan =
23&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
Fax&nbsp;&nbsp; +46 8 7575550<BR>S-164 80 Stockholm, Sweden | mailto: =
magnus.westerlund@ericsson.com<BR>---------------------------------------=
-------------------------------<BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C74EF2.17A65758--


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

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

--===============1478888381==--




From avt-bounces@ietf.org Mon Feb 12 17:09:32 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGjLz-00038i-HA; Mon, 12 Feb 2007 17:08:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGjLy-00038c-Ba
	for avt@ietf.org; Mon, 12 Feb 2007 17:08:54 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGjLw-0006Pz-UI
	for avt@ietf.org; Mon, 12 Feb 2007 17:08:54 -0500
Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l1CM8nYI025076
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 12 Feb 2007 14:08:49 -0800
Received: from SANEXCAS02.na.qualcomm.com (sanexcas02.qualcomm.com
	[172.30.36.176])
	by hamtaro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l1CM8mn3000887; Mon, 12 Feb 2007 14:08:48 -0800 (PST)
Received: from NAEX01.qualcomm.com ([129.46.51.60]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Feb 2007 14:08:48 -0800
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
Subject: RE: [AVT] Non-compound RTCP
Date: Mon, 12 Feb 2007 14:08:53 -0800
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B028B05EE@NAEX01.na.qualcomm.com>
In-Reply-To: <026F8EEDAD2C4342A993203088C1FC05045D073F@esealmw109.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Non-compound RTCP
Thread-Index: AcdKlw4w8rgWIpLVQRy2f7aOtTTtegEWtOHQ
References: <026F8EEDAD2C4342A993203088C1FC05045D073F@esealmw109.eemea.ericsson.se>
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: "Ingemar Johansson S \(LU/EAB\)" <ingemar.s.johansson@ericsson.com>,
	<avt@ietf.org>
X-OriginalArrivalTime: 12 Feb 2007 22:08:48.0114 (UTC)
	FILETIME=[5EB23D20:01C74EF2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Based on the meeting report:
Non-compound RTCP feature is *not* delayed in MTSI. It was not agreed =
for inclusion into the MTSI TS26.114. TS26.114 has already been approved =
without the non-compound RTCP feature.

Regards,
Hari
> -----Original Message-----
> From: Ingemar Johansson S (LU/EAB)
> [mailto:ingemar.s.johansson@ericsson.com]
> Sent: Wednesday, February 07, 2007 1:05 AM
> To: avt@ietf.org
> Cc: Ingemar Johansson S (LU/EAB)
> Subject: [AVT] Non-compound RTCP
>=20
> Hi
>=20
> A little before the new years party I posted an announcement of a new
> draft with the title
> "Support for non-compund RTCP in RTCP AVPF profile, opportunities and
> consequences", see abstract and link to draft below
>=20
> Support for non-compound RTCP has since then been been presented for
> inclusion in a 3GPP specification (TS26.114). It was however delayed, =
the
> argument was mainly that this issue has not been discussed openly in =
IETF
> at all. So therefore opinons around this issue are very welcome,
> especially regarding:
>=20
> 1) Examples where "middle boxes" in a network might discard =
non-compound
> RTCP. What kind of middle boxes are these.
> 2) Non-compound RTCP is specified in OMA-PoC (Push to talk). Are there =
any
> other standards or proprietary solutions or defacto standards that =
already
> today use non-compund RTCP and thus violate the rules outlined in =
RFC3550?
> Are there any problems ?
>=20
> Regards
> Ingemar
>=20
> Abstract:
> This memo discusses benefits and issues that arise when allowing RTCP
> packets to be transmitted as non-compound packets, i.e. not follow the
> rules of RFC 3550.  Based on that analysis this memo proposes changes =
to
> the rules to allow feedback messages to be sent as non-compound RTCP
> packets when using the RTP AVPF profile (RFC 4585)under certain =
conditions.
> =
http://tools.ietf.org/wg/avt/draft-johansson-avt-rtcp-avpf-non-compound-
> 00.txt
>=20
> *******************************************
> Ingemar Johansson
> Senior Research Engineer
> EAB/TVP - Multimedia Technologies Ericsson Research
> Ericsson AB
> Box 920
> S-971 28 Lule=E5, Sweden
> Tel: +46 (0)8 4043042
> ECN: 850-43042
> Mobile: +46 (0)730 783289
> *******************************************
>=20
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

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



From avt-bounces@ietf.org Mon Feb 12 18:09:37 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGkHh-0000pL-3y; Mon, 12 Feb 2007 18:08:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGkHg-0000pG-FB
	for avt@ietf.org; Mon, 12 Feb 2007 18:08:32 -0500
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGkHf-0004oB-4e
	for avt@ietf.org; Mon, 12 Feb 2007 18:08:32 -0500
Received: from relay7.apple.com (a17-128-113-37.apple.com [17.128.113.37])
	by mail-out4.apple.com (8.13.8/8.13.8) with ESMTP id l1CN8U0M010004
	for <avt@ietf.org>; Mon, 12 Feb 2007 15:08:30 -0800 (PST)
Received: from relay7.apple.com (unknown [127.0.0.1])
	by relay7.apple.com (Symantec Mail Security) with ESMTP id 5A9293007C
	for <avt@ietf.org>; Mon, 12 Feb 2007 15:08:30 -0800 (PST)
X-AuditID: 11807125-a3308bb0000007df-c3-45d0f36ea3d1 
Mime-Version: 1.0
Message-Id: <p06230914c1f6a200bde6@[17.202.35.52]>
In-Reply-To: <2CA3E1B6CEC064449CAA7D0FAB46079B028B05E2@NAEX01.na.qualcomm.com>
References: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com>
	<ybumz3jumsx.fsf@jesup.eng.wgate.com>
	<2CA3E1B6CEC064449CAA7D0FAB46079B028B05E2@NAEX01.na.qualcomm.com>
Date: Mon, 12 Feb 2007 15:07:32 -0800
To: avt@ietf.org
From: Dave Singer <singer@apple.com>
Subject: RE: [AVT] CCM draft review -- should "bandwidth" include 
	theheaderoverhead
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On the question of what bitrate to send, it depends on who knows what:

"Please send me a stream that fits through a constriction of x kb/s. And
a) I know that ROHC is in use through that constriction;
b) I know it is not;
c) I don't know;  if you do, then you can do the partitioning;
d) I don't know, and if you don't either, assume the worst (i.e. that 
it is not)."

My suspicion is that we have to signal (c, d), and that (d) is the 
most likely outcome.  That is, we include headers unless the sender 
knows to the contrary.


On the question of "what is bitrate", I'd suggest that we say that 
the source was traffic-smoothed to not exceed x.  By that I mean, if 
I send a packet of Y kbits, then the next packet is sent no earlier 
than Y/x seconds later.  Alternatively, the bitrate is the max over 
all consecutive pairs of packets [i,i+1] of
(timestamp(i+1) - timestamp(i))/size(i)

which is harsh, but otherwise we'll have to define a leaky bucket 
model, or an averaging interval.  Both of these either require 
signalling the size of the ingest buffer to the constriction, or 
assuming it, neither of which are pleasant.
-- 
David Singer
Apple Computer/QuickTime

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



From avt-bounces@ietf.org Mon Feb 12 18:45:40 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGkqi-0001Jn-Lh; Mon, 12 Feb 2007 18:44:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGkqg-0001JX-Tl
	for avt@ietf.org; Mon, 12 Feb 2007 18:44:42 -0500
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HGkqf-00051Q-Kb for avt@ietf.org; Mon, 12 Feb 2007 18:44:42 -0500
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 12 Feb 2007 18:44:37 -0500
To: "Even, Roni" <roni.even@polycom.co.il>
Subject: Re: [AVT] CCM draft review -- should "bandwidth" include
	theheaderoverhead
References: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com>
	<10E7D146-0080-420A-BEF4-44C22DD7BAE0@stewe.org>
	<2CA3E1B6CEC064449CAA7D0FAB46079B028B05AB@NAEX01.na.qualcomm.com>
	<ybud54fulla.fsf@jesup.eng.wgate.com>
	<144ED8561CE90C41A3E5908EDECE315C730CD4@IsrExch01.israel.polycom.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Mon, 12 Feb 2007 18:44:35 -0500
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C730CD4@IsrExch01.israel.polycom.com>
	(Roni Even's message of "Mon, 12 Feb 2007 16:49:16 -0500")
Message-ID: <ybuire7szz0.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 12 Feb 2007 23:44:37.0453 (UTC)
	FILETIME=[C191BFD0:01C74EFF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: Stephan Wenger <stewe@stewe.org>, avt@ietf.org,
	Magnus Westerlund <magnus.westerlund@ericsson.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

"Even, Roni" <roni.even@polycom.co.il> writes:
>I think you have to know ow to convert from b= to the codec rate anyhow,
>otherwise how can you know how much to allow the encoder to use in term of
>bit rate.  On the receiver side, the way I see it is that once you
>establish the connection and want to use TMMBR you already know the codec
>rate you receive, if you decode so you can reduce the rate based on this
>information.  Roni

a) At the sender side, the codec and the RTP could interact on a
   packet-by-packet (second-by-second, etc) basis to adjust bitrate
   (i.e. the RTP layer knows what overhead exists (at the sending end), and
   RTP header extensions added (for example by ZRTP), etc).  The codec does
   not have to be given a fixed bitrate to encode at.  Most devices are set
   up that way currently, but they don't need to be.

b) The receiver does not know (and in many cases cannot know) the sender's
   bitrate.  At most you know the rate you suggested to the sender.  Many
   codec/rate-controller implementations use "bitrate" settings as a
   maximum, so a receiver can't monitor the incoming rate to get anything
   useful.  Similarly, the packet rate could vary by 2x or more easily.

c) Only the sender needs to convert link bandwidth to codec bandwidth.
   This makes sense, since only the sender knows if he'll be including (for
   example) header extensions, and if so how often.  You don't want to have
   the receiver have to assume worst-case use of header extensions, you
   want the sender to account for actual use by adjusting codec bandwidth.
   For example, if an extension in use could use 50 bytes per packet, the
   receiver may have to use "link - (normal_overhead+50)*maxprate", while
   the sender can use (if it wants to)
   "link - ((actual_overhead)*actual_prate + actual_hdrext_use)" 

   The sender needs to know how to calculate codec BW anyways, if the
   sender accepts b=AS or b=CT.

I'm not saying b=AS/etc is perfect.  I am saying that for link bandwidth
signalling and adaption it's better than codec bandwidth (TIAS), and much
better than having TMMBR *always* use TIAS values (even if not signaled).

Perhaps in addition to being conference/interop focused, your usages also
leave a lot of headroom, and so a little wasted bandwidth isn't a big deal.
For lower-bandwidth devices trying to squeeze every bit out of a tight link
(home users, 3GPP, etc), link efficiency is much more important than ease
of codec control or ease of calculations for codec BW.

IMHO.

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


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



From avt-bounces@ietf.org Mon Feb 12 21:16:25 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGnC3-0002Na-P5; Mon, 12 Feb 2007 21:14:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGiiY-0006Jx-MS; Mon, 12 Feb 2007 16:28:10 -0500
Received: from zcars04e.nortel.com ([47.129.242.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HGiiX-0007FW-Di; Mon, 12 Feb 2007 16:28:10 -0500
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	l1CLK6Z11821; Mon, 12 Feb 2007 16:20:06 -0500 (EST)
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, 12 Feb 2007 15:27:55 -0600
Message-ID: <1ECE0EB50388174790F9694F77522CCF0F21D703@zrc2hxm0.corp.nortel.com>
In-Reply-To: <45D0D77F.8030705@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] [Fwd: Last Call: draft-wing-behave-symmetric-rtprtcp
	(Common Local Transmit and Receive Ports (Symmetric RTP)) to
	Informational RFC]
Thread-Index: AcdO6l3gxbbx0BwMRx2CLZguomeVFQAAZFCg
From: "Francois Audet" <audet@nortel.com>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>,
	"IETF AVT WG" <avt@ietf.org>, <behave@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
X-Mailman-Approved-At: Mon, 12 Feb 2007 21:14:55 -0500
Cc: Dan Wing <dwing@cisco.com>
Subject: [AVT] RE: [BEHAVE] [Fwd: Last Call:
	draft-wing-behave-symmetric-rtprtcp (Common Local Transmit
	and Receive Ports (Symmetric RTP)) to Informational RFC]
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Thanks for doing this Magnus.

I have one comment. I think we should add as a last statement at the end
of=20
section 3 "Recommended usage" that says something like:

"It is therefore RECOMMENDED that symmetric RTP and symmetric RTCP
always=20
be used for bi-directional RTP media streams."

Otherwise, the draft doesn't specifically recommend anything.

> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]=20
> Sent: Monday, February 12, 2007 13:09
> To: IETF AVT WG; behave@ietf.org
> Subject: [BEHAVE] [Fwd: Last Call:=20
> draft-wing-behave-symmetric-rtprtcp (Common Local Transmit=20
> and Receive Ports (Symmetric RTP)) to Informational RFC]
>=20
> Hi,
>=20
> This document has been raised before in both AVT and BEHAVE=20
> WG. I have chosen to AD sponsor this document for publication=20
> as informational status because it seems to be of general=20
> interest. You have 4 weeks to provide any comments on the document.
>=20
> Magnus Westerlund
>=20
> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>=20

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



From avt-bounces@ietf.org Tue Feb 13 02:02:05 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGreh-0002Ye-BV; Tue, 13 Feb 2007 02:00:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGreg-0002XV-9u
	for avt@ietf.org; Tue, 13 Feb 2007 02:00:46 -0500
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGref-0002Ve-9p
	for avt@ietf.org; Tue, 13 Feb 2007 02:00:46 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [AVT] CCM draft review -- should "bandwidth" include
	theheaderoverhead
Date: Tue, 13 Feb 2007 09:00:39 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C730CD9@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] CCM draft review -- should "bandwidth" include
	theheaderoverhead
Thread-Index: AcdO+zojcSowGOugTemU5PT1PRNlDQAQEq9Y
References: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com><ybumz3jumsx.fsf@jesup.eng.wgate.com><2CA3E1B6CEC064449CAA7D0FAB46079B028B05E2@NAEX01.na.qualcomm.com>
	<p06230914c1f6a200bde6@[17.202.35.52]>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Dave Singer" <singer@apple.com>,
	<avt@ietf.org>
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0972442428=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0972442428==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C74F3C.AB6CB594"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C74F3C.AB6CB594
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Hi,
I think that looking at it from the perspective of the link is not the =
right direction.
The first question to ask is why does the receiver wants to send a TMMBR =
which is a temporary change. I gave a couple of examples in previous =
emails. (speed between IP and circuit switch, dividing the bit rate =
between two video streams, processing issues on codec)
Once you know why the receiver wants to do it than you can try to =
analyze what the receiver knows at that stage in order to ask the =
correct speed.
My point that in most cases when the receiver wants to reduce the speed =
it has to do with the coder on the receiver side which knows the media =
bit rate and not the link overhead.
Congestion is a case but it does not require an exact number but rather =
takes some percentage bellow the current speed.
=20
Roni

________________________________

=EE=E0=FA: Dave Singer [mailto:singer@apple.com]
=F0=F9=EC=E7: =E2 13/02/2007 01:07
=E0=EC: avt@ietf.org
=F0=E5=F9=E0: RE: [AVT] CCM draft review -- should "bandwidth" include =
theheaderoverhead



On the question of what bitrate to send, it depends on who knows what:

"Please send me a stream that fits through a constriction of x kb/s. And
a) I know that ROHC is in use through that constriction;
b) I know it is not;
c) I don't know;  if you do, then you can do the partitioning;
d) I don't know, and if you don't either, assume the worst (i.e. that
it is not)."

My suspicion is that we have to signal (c, d), and that (d) is the
most likely outcome.  That is, we include headers unless the sender
knows to the contrary.


On the question of "what is bitrate", I'd suggest that we say that
the source was traffic-smoothed to not exceed x.  By that I mean, if
I send a packet of Y kbits, then the next packet is sent no earlier
than Y/x seconds later.  Alternatively, the bitrate is the max over
all consecutive pairs of packets [i,i+1] of
(timestamp(i+1) - timestamp(i))/size(i)

which is harsh, but otherwise we'll have to define a leaky bucket
model, or an averaging interval.  Both of these either require
signalling the size of the ingest buffer to the constriction, or
assuming it, neither of which are pleasant.
--
David Singer
Apple Computer/QuickTime

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



------_=_NextPart_001_01C74F3C.AB6CB594
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Drtl><HEAD><TITLE>RE: [AVT] CCM draft review -- should =
"bandwidth" include theheaderoverhead</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2800.1515" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 =
size=3D2>Hi,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>I think that looking at it =
from the perspective of the link is not the right direction.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>The first question to ask is =
why does the receiver wants to send a TMMBR which is a temporary change. =
I gave a couple of examples in previous emails. (speed between IP and =
circuit switch, dividing the bit rate between two video streams, =
processing issues on codec)</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Once you know why the =
receiver wants to do it than you can try to analyze what the receiver =
knows at that stage in order to ask the correct speed.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>My point that in most cases =
when the receiver wants to reduce the speed it has to do with the coder =
on the receiver side which knows the media bit rate and not the link =
overhead.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Congestion is a case but it =
does not require an exact number but rather takes some percentage bellow =
the current speed.</FONT></DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Roni</FONT></DIV>=0A=
<DIV dir=3Drtl><BR></DIV>=0A=
<DIV dir=3Drtl>=0A=
<HR tabIndex=3D-1>=0A=
</DIV>=0A=
<DIV dir=3Drtl><FONT face=3DTahoma size=3D2><B>=EE=E0=FA:</B> Dave =
Singer [mailto:singer@apple.com]<BR><B>=F0=F9=EC=E7:</B> =E2 13/02/2007 =
01:07<BR><B>=E0=EC:</B> avt@ietf.org<BR><B>=F0=E5=F9=E0:</B> RE: [AVT] =
CCM draft review -- should "bandwidth" include =
theheaderoverhead<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>On the question of what bitrate to send, it depends on =
who knows what:<BR><BR>"Please send me a stream that fits through a =
constriction of x kb/s. And<BR>a) I know that ROHC is in use through =
that constriction;<BR>b) I know it is not;<BR>c) I don't know;&nbsp; if =
you do, then you can do the partitioning;<BR>d) I don't know, and if you =
don't either, assume the worst (i.e. that<BR>it is not)."<BR><BR>My =
suspicion is that we have to signal (c, d), and that (d) is the<BR>most =
likely outcome.&nbsp; That is, we include headers unless the =
sender<BR>knows to the contrary.<BR><BR><BR>On the question of "what is =
bitrate", I'd suggest that we say that<BR>the source was =
traffic-smoothed to not exceed x.&nbsp; By that I mean, if<BR>I send a =
packet of Y kbits, then the next packet is sent no earlier<BR>than Y/x =
seconds later.&nbsp; Alternatively, the bitrate is the max over<BR>all =
consecutive pairs of packets [i,i+1] of<BR>(timestamp(i+1) - =
timestamp(i))/size(i)<BR><BR>which is harsh, but otherwise we'll have to =
define a leaky bucket<BR>model, or an averaging interval.&nbsp; Both of =
these either require<BR>signalling the size of the ingest buffer to the =
constriction, or<BR>assuming it, neither of which are =
pleasant.<BR>--<BR>David Singer<BR>Apple =
Computer/QuickTime<BR><BR>_______________________________________________=
<BR>Audio/Video Transport Working Group<BR>avt@ietf.org<BR><A =
href=3D"https://www1.ietf.org/mailman/listinfo/avt">https://www1.ietf.org=
/mailman/listinfo/avt</A><BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C74F3C.AB6CB594--


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

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

--===============0972442428==--




From avt-bounces@ietf.org Tue Feb 13 04:23:56 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGts6-0000ZW-PB; Tue, 13 Feb 2007 04:22:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGts5-0000ZH-Gj
	for avt@ietf.org; Tue, 13 Feb 2007 04:22:45 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGtrt-0001Qa-OJ
	for avt@ietf.org; Tue, 13 Feb 2007 04:22:43 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	1F833207C2; Tue, 13 Feb 2007 10:22:31 +0100 (CET)
X-AuditID: c1b4fb3c-ae7c5bb0000007de-c7-45d183574662 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	03296205DB; Tue, 13 Feb 2007 10:22:31 +0100 (CET)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 13 Feb 2007 10:22:30 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] Non-compound RTCP
Date: Tue, 13 Feb 2007 10:22:29 +0100
Message-ID: <026F8EEDAD2C4342A993203088C1FC0504692090@esealmw109.eemea.ericsson.se>
In-Reply-To: <2CA3E1B6CEC064449CAA7D0FAB46079B028B05EE@NAEX01.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Non-compound RTCP
Thread-Index: AcdKlw4w8rgWIpLVQRy2f7aOtTTtegEWtOHQABUVDQA=
From: "Ingemar Johansson S \(LU/EAB\)" <ingemar.s.johansson@ericsson.com>
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>,
	<avt@ietf.org>
X-OriginalArrivalTime: 13 Feb 2007 09:22:30.0652 (UTC)
	FILETIME=[7C680BC0:01C74F50]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi

I was perhaps a little unclear in my selection of words (sorry)

The exact wording is found in section 9.9 of
http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/TSGS4_42/Docs/S4-070177.zip=20
See full text below.=20

The main point was that it was not justified to delay the entire =
TS26.114 specification just because of the Non-compound RTCP feature. =
Instead Ericsson will submit a change request for next SA-4 meeting =
(Rennes April 23-27) containing more thorough argumentation for =
Non-compound RTCP.

Again the main argument against Non-compound RTCP was that it has been =
very little discussion about this topic in IETF. Therefore any comments =
on the draft=20
http://tools.ietf.org/wg/avt/draft-johansson-avt-rtcp-avpf-non-compound-0=
0.txt
are appreciated.

Regards
Ingemar

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Text from the meeting notes =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Mr. Tomas Frankkila presented TD S4-070084 Non-compound RTCP, from =
Ericsson.
This document contained a proposal to recommend support for the use of =
non-compound RTCP in TS 26.114. The use of non-compound RTCP makes =
transmission of critical feedback messages more robust in severe radio =
conditions where small packet sizes are crucial for successful =
transmission, another advantage is that non-compound RTCP packets can be =
transmitted more frequently (since they are smaller). This means that =
adaptation requests can be transmitted more frequently with the given =
bandwidth, this enables faster adaptation.=20
The concept is not new to the mobile industry; it is also used in =
OMA-PoC.=20
The proposed change assumes an additional SDP attribute "ncp" =
interpreted as non-compound. Additionally the use of the parameter =
"trr-int" differs from what is described in ch. 7.3.2 in TS26.114.
The proposal to 3GPP-SA4 from Ericsson was to adopt these additions to =
the MTSI-TS.

Comments / Questions : Nokia expressed reservation on the proposed =
changes, despite OMA already accepted the concept proposed in the =
document. Also Siemens Networks was not in favour of the proposed =
changes. Ericsson proposed to continue eventually the discussion at next =
meeting, but felt more important that TS 26.114 is approved at SA#35.

Conclusion : the document was noted.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=




> -----Original Message-----
> From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]=20
> Sent: den 12 februari 2007 23:09
> To: Ingemar Johansson S (LU/EAB); avt@ietf.org
> Subject: RE: [AVT] Non-compound RTCP
>=20
> Based on the meeting report:
> Non-compound RTCP feature is *not* delayed in MTSI. It was=20
> not agreed for inclusion into the MTSI TS26.114. TS26.114 has=20
> already been approved without the non-compound RTCP feature.
>=20
> Regards,
> Hari
> > -----Original Message-----
> > From: Ingemar Johansson S (LU/EAB)
> > [mailto:ingemar.s.johansson@ericsson.com]
> > Sent: Wednesday, February 07, 2007 1:05 AM
> > To: avt@ietf.org
> > Cc: Ingemar Johansson S (LU/EAB)
> > Subject: [AVT] Non-compound RTCP
> >=20
> > Hi
> >=20
> > A little before the new years party I posted an=20
> announcement of a new=20
> > draft with the title "Support for non-compund RTCP in RTCP AVPF=20
> > profile, opportunities and consequences", see abstract and link to=20
> > draft below
> >=20
> > Support for non-compound RTCP has since then been been=20
> presented for=20
> > inclusion in a 3GPP specification (TS26.114). It was=20
> however delayed,=20
> > the argument was mainly that this issue has not been=20
> discussed openly=20
> > in IETF at all. So therefore opinons around this issue are very=20
> > welcome, especially regarding:
> >=20
> > 1) Examples where "middle boxes" in a network might discard=20
> > non-compound RTCP. What kind of middle boxes are these.
> > 2) Non-compound RTCP is specified in OMA-PoC (Push to=20
> talk). Are there=20
> > any other standards or proprietary solutions or defacto=20
> standards that=20
> > already today use non-compund RTCP and thus violate the=20
> rules outlined in RFC3550?
> > Are there any problems ?
> >=20
> > Regards
> > Ingemar
> >=20
> > Abstract:
> > This memo discusses benefits and issues that arise when=20
> allowing RTCP=20
> > packets to be transmitted as non-compound packets, i.e. not=20
> follow the=20
> > rules of RFC 3550.  Based on that analysis this memo=20
> proposes changes=20
> > to the rules to allow feedback messages to be sent as non-compound=20
> > RTCP packets when using the RTP AVPF profile (RFC=20
> 4585)under certain conditions.
> >=20
> http://tools.ietf.org/wg/avt/draft-johansson-avt-rtcp-avpf-non-compoun
> > d-
> > 00.txt
> >=20
> > *******************************************
> > Ingemar Johansson
> > Senior Research Engineer
> > EAB/TVP - Multimedia Technologies Ericsson Research Ericsson AB Box=20
> > 920
> > S-971 28 Lule=E5, Sweden
> > Tel: +46 (0)8 4043042
> > ECN: 850-43042
> > Mobile: +46 (0)730 783289
> > *******************************************
> >=20
> >=20
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www1.ietf.org/mailman/listinfo/avt
>=20

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



From avt-bounces@ietf.org Tue Feb 13 05:01:44 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGuSl-0003Sy-FX; Tue, 13 Feb 2007 05:00:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGuSk-0003Sq-EY
	for avt@ietf.org; Tue, 13 Feb 2007 05:00:38 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGuSd-00069e-Rt
	for avt@ietf.org; Tue, 13 Feb 2007 05:00:38 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	3CA50207B9 for <avt@ietf.org>; Tue, 13 Feb 2007 11:00:27 +0100 (CET)
X-AuditID: c1b4fb3c-b07c9bb0000007de-d6-45d18c3b9f45 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	2C35C2065C for <avt@ietf.org>; Tue, 13 Feb 2007 11:00:27 +0100 (CET)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 13 Feb 2007 11:00:26 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] CCM draft review -- should "bandwidth" include
	theheaderoverhead
Date: Tue, 13 Feb 2007 11:00:25 +0100
Message-ID: <026F8EEDAD2C4342A993203088C1FC0504692138@esealmw109.eemea.ericsson.se>
In-Reply-To: <E1HGts8-0000bL-Fp@megatron.ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] CCM draft review -- should "bandwidth" include
	theheaderoverhead
Thread-Index: AcdPULCco+bKJ3hYSrebSuuEep780QAAp2Sg
From: "Ingemar Johansson S \(LU/EAB\)" <ingemar.s.johansson@ericsson.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 13 Feb 2007 10:00:26.0765 (UTC)
	FILETIME=[C91353D0:01C74F55]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi

My humble opinion is that it is unrealistic to assume that the
application has any knowledge whatsoever about the use of header
compression, this applies esp. to RoHC. One could perhaps argue that
RoHC will be used in 3GPP rel 7 but here the implementor/operator have
full freedom to choose to use-or-not-to-use RoHC, it is more or less a
"coffee with cream" issue. That said RoHC is highly recommended to use.

There is some possibility that the application could get know the use of
header compression in a terminal but this knowledge only applies to the
radio interface closest to the terminal. Moreover this is to be regarded
as a vendor specific (dreadful crosslayer) feature and I don't belive
that one should rely on such things in a proposed standard.

I bet my "5 kronor" on alternative d)

Ingemar

> Message: 2
> Date: Mon, 12 Feb 2007 15:07:32 -0800
> From: Dave Singer <singer@apple.com>
> Subject: RE: [AVT] CCM draft review -- should "bandwidth" include
> 	theheaderoverhead
> To: avt@ietf.org
> Message-ID: <p06230914c1f6a200bde6@[17.202.35.52]>
> Content-Type: text/plain; charset=3D"us-ascii" ; format=3D"flowed"
>=20
> On the question of what bitrate to send, it depends on who knows what:
>=20
> "Please send me a stream that fits through a constriction of=20
> x kb/s. And
> a) I know that ROHC is in use through that constriction;
> b) I know it is not;
> c) I don't know;  if you do, then you can do the partitioning;
> d) I don't know, and if you don't either, assume the worst=20
> (i.e. that it is not)."
>=20
> My suspicion is that we have to signal (c, d), and that (d)=20
> is the most likely outcome.  That is, we include headers=20
> unless the sender knows to the contrary.
>=20
>=20
> On the question of "what is bitrate", I'd suggest that we say=20
> that the source was traffic-smoothed to not exceed x.  By=20
> that I mean, if I send a packet of Y kbits, then the next=20
> packet is sent no earlier than Y/x seconds later. =20
> Alternatively, the bitrate is the max over all consecutive=20
> pairs of packets [i,i+1] of
> (timestamp(i+1) - timestamp(i))/size(i)
>=20
> which is harsh, but otherwise we'll have to define a leaky=20
> bucket model, or an averaging interval.  Both of these either=20
> require signalling the size of the ingest buffer to the=20
> constriction, or assuming it, neither of which are pleasant.
> --
> David Singer
> Apple Computer/QuickTime

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



From avt-bounces@ietf.org Tue Feb 13 07:20:04 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGwch-0002LW-Ec; Tue, 13 Feb 2007 07:19:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGwcg-0002IG-Cv
	for avt@ietf.org; Tue, 13 Feb 2007 07:19:02 -0500
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HGwcf-0001XP-5y for avt@ietf.org; Tue, 13 Feb 2007 07:19:02 -0500
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 Feb 2007 07:19:01 -0500
To: "Even, Roni" <roni.even@polycom.co.il>
Subject: Re: [AVT] CCM draft review -- should "bandwidth" include
	theheaderoverhead
References: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com>
	<ybumz3jumsx.fsf@jesup.eng.wgate.com>
	<2CA3E1B6CEC064449CAA7D0FAB46079B028B05E2@NAEX01.na.qualcomm.com>
	<p06230914c1f6a200bde6@[17.202.35.52]>
	<144ED8561CE90C41A3E5908EDECE315C730CD9@IsrExch01.israel.polycom.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Tue, 13 Feb 2007 07:18:59 -0500
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C730CD9@IsrExch01.israel.polycom.com>
	(Roni Even's message of "Tue, 13 Feb 2007 09:00:39 +0200")
Message-ID: <ybusldajln0.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 13 Feb 2007 12:19:01.0196 (UTC)
	FILETIME=[24DCD0C0:01C74F69]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: Dave Singer <singer@apple.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

"Even, Roni" <roni.even@polycom.co.il> writes:
>I think that looking at it from the perspective of the link is not the
>right direction.  The first question to ask is why does the receiver wants
>to send a TMMBR which is a temporary change. I gave a couple of examples
>in previous emails. (speed between IP and circuit switch, dividing the bit
>rate between two video streams, processing issues on codec) Once you know
>why the receiver wants to do it than you can try to analyze what the
>receiver knows at that stage in order to ask the correct speed.  My point
>that in most cases when the receiver wants to reduce the speed it has to
>do with the coder on the receiver side which knows the media bit rate and
>not the link overhead.

Aha.  This explains some of the disconnect occuring here.  Those are uses
that haven't even crossed my mind for TMMBR.

I (and I assume the 3G people, and David Singer and Magnus I think) are
looking to TMMBR for link status changes, while you are looking to it for a
very different (more codec-oriented) purpose.

>Congestion is a case but it does not require an
>exact number but rather takes some percentage bellow the current speed.

Yes, probably, though you can easily do that with TMMBR.

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


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



From avt-bounces@ietf.org Tue Feb 13 12:39:31 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH1bM-0006Ly-Tm; Tue, 13 Feb 2007 12:38:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HH1bL-0006Lo-MY
	for avt@ietf.org; Tue, 13 Feb 2007 12:37:59 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HH1bJ-0003YX-Ai
	for avt@ietf.org; Tue, 13 Feb 2007 12:37:59 -0500
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l1DHbqvC032188
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 13 Feb 2007 09:37:53 -0800
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com
	[172.30.32.65])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l1DHbpYM021472; Tue, 13 Feb 2007 09:37:51 -0800
Received: from NAEX01.qualcomm.com ([129.46.51.60]) by
	SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 13 Feb 2007 09:37:51 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] CCM draft review -- should "bandwidth"
	includetheheaderoverhead
Date: Tue, 13 Feb 2007 09:37:49 -0800
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B028B06D7@NAEX01.na.qualcomm.com>
In-Reply-To: <ybusldajln0.fsf@jesup.eng.wgate.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] CCM draft review -- should "bandwidth"
	includetheheaderoverhead
Thread-Index: AcdPata3K58y9RVnTlu9EMo/M26teQAKeE3g
References: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com><ybumz3jumsx.fsf@jesup.eng.wgate.com><2CA3E1B6CEC064449CAA7D0FAB46079B028B05E2@NAEX01.na.qualcomm.com><p06230914c1f6a200bde6@[17.202.35.52]><144ED8561CE90C41A3E5908EDECE315C730CD9@IsrExch01.israel.polycom.com>
	<ybusldajln0.fsf@jesup.eng.wgate.com>
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: "Randell Jesup" <rjesup@wgate.com>, "Even, Roni" <roni.even@polycom.co.il>
X-OriginalArrivalTime: 13 Feb 2007 17:37:51.0211 (UTC)
	FILETIME=[AF3D73B0:01C74F95]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: Dave Singer <singer@apple.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org



> -----Original Message-----
> From: Randell Jesup [mailto:rjesup@wgate.com]
>=20
> "Even, Roni" <roni.even@polycom.co.il> writes:
> >I think that looking at it from the perspective of the link is not
the
> >right direction.  The first question to ask is why does the receiver
> wants
> >to send a TMMBR which is a temporary change. I gave a couple of
examples
> >in previous emails. (speed between IP and circuit switch, dividing
the
> bit
> >rate between two video streams, processing issues on codec) Once you
know
> >why the receiver wants to do it than you can try to analyze what the
> >receiver knows at that stage in order to ask the correct speed.  My
point
> >that in most cases when the receiver wants to reduce the speed it has
to
> >do with the coder on the receiver side which knows the media bit rate
and
> >not the link overhead.
>=20
> Aha.  This explains some of the disconnect occuring here.  Those are
uses
> that haven't even crossed my mind for TMMBR.
>=20
> I (and I assume the 3G people, and David Singer and Magnus I think)
are
> looking to TMMBR for link status changes, while you are looking to it
for
> a
> very different (more codec-oriented) purpose.
>=20

If TMMBR is not codec oriented then it should not be treated as a codec
control message and it has to be taken out from "codec control messages"
draft.


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



From avt-bounces@ietf.org Tue Feb 13 13:21:05 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH2GH-0002qr-N8; Tue, 13 Feb 2007 13:20:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HH2GG-0002pV-6b
	for avt@ietf.org; Tue, 13 Feb 2007 13:20:16 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HH2GC-0007nO-O0
	for avt@ietf.org; Tue, 13 Feb 2007 13:20:16 -0500
Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l1DIK0Fw007754
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 13 Feb 2007 10:20:01 -0800
Received: from SANEXCAS02.na.qualcomm.com (sanexcas02.qualcomm.com
	[172.30.36.176])
	by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l1DIJxCV022352;
	Tue, 13 Feb 2007 10:20:00 -0800 (PST)
Received: from NAEX01.qualcomm.com ([129.46.51.60]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 13 Feb 2007 10:19:59 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] CCM draft review -- should "bandwidth" include
	theheaderoverhead
Date: Tue, 13 Feb 2007 10:19:59 -0800
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B028B06FE@NAEX01.na.qualcomm.com>
In-Reply-To: <p06230914c1f6a200bde6@[17.202.35.52]>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] CCM draft review -- should "bandwidth" include
	theheaderoverhead
Thread-Index: AcdO/HyjlQyhvK3cRlWGlPWGbu9pWgAnexAw
References: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com><ybumz3jumsx.fsf@jesup.eng.wgate.com><2CA3E1B6CEC064449CAA7D0FAB46079B028B05E2@NAEX01.na.qualcomm.com>
	<p06230914c1f6a200bde6@[17.202.35.52]>
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: "Dave Singer" <singer@apple.com>, <avt@ietf.org>
X-OriginalArrivalTime: 13 Feb 2007 18:19:59.0869 (UTC)
	FILETIME=[92700AD0:01C74F9B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org



> -----Original Message-----
> From: Dave Singer [mailto:singer@apple.com]
> Sent: Monday, February 12, 2007 3:08 PM
> To: avt@ietf.org
> Subject: RE: [AVT] CCM draft review -- should "bandwidth" include
> theheaderoverhead
>=20
> On the question of what bitrate to send, it depends on who knows what:
>=20
> "Please send me a stream that fits through a constriction of x kb/s.
And
> a) I know that ROHC is in use through that constriction;
> b) I know it is not;
> c) I don't know;  if you do, then you can do the partitioning;
> d) I don't know, and if you don't either, assume the worst (i.e. that
> it is not)."
>=20
> My suspicion is that we have to signal (c, d), and that (d) is the
> most likely outcome.  That is, we include headers unless the sender
> knows to the contrary.
>=20

With option d), it is possible for the sender to signal what its worst
assumption is. I.e., Sender can tell details like what (max/avg) bitrate
it will send at. In theory, packet overhead is out of sender's control
as RTP header extensions can be added by RTP nodes in the middle.
Whatever the sender/receiver does w.r.to packet overhead is just a worst
case guess over end to end path. One thing that will at least remain
valid (assumption free) end to end is the (max/avg) media bit-rate of
the sender.

I have a draft which captures the SDP bandwidth attribute that can be
used to signal a sender's max media bitrate in offer/answer model. Until
it appears on the IETF server, it can be accessed from
http://people.qualcomm.com/hdesinen/draft-hdesinen-mmusic-oa-send-bw-att
r-00.txt



>=20
> On the question of "what is bitrate", I'd suggest that we say that
> the source was traffic-smoothed to not exceed x.  By that I mean, if
> I send a packet of Y kbits, then the next packet is sent no earlier
> than Y/x seconds later.  Alternatively, the bitrate is the max over
> all consecutive pairs of packets [i,i+1] of
> (timestamp(i+1) - timestamp(i))/size(i)
>=20
> which is harsh, but otherwise we'll have to define a leaky bucket
> model, or an averaging interval.  Both of these either require
> signalling the size of the ingest buffer to the constriction, or
> assuming it, neither of which are pleasant.
> --
> David Singer
> Apple Computer/QuickTime
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

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



From avt-bounces@ietf.org Tue Feb 13 15:18:49 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH45i-000538-Uf; Tue, 13 Feb 2007 15:17:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH45h-000530-7R; Tue, 13 Feb 2007 15:17:29 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HH45Y-0003Pu-Go; Tue, 13 Feb 2007 15:17:29 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	ACBF820415; Tue, 13 Feb 2007 21:17:11 +0100 (CET)
X-AuditID: c1b4fb3c-aefc6bb0000007de-56-45d21cc753c9 
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	8C96720414; Tue, 13 Feb 2007 21:17:11 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 13 Feb 2007 21:17:10 +0100
Received: from [138.85.12.222] ([138.85.12.222]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 13 Feb 2007 21:17:10 +0100
Message-ID: <45D21CC4.10909@ericsson.com>
Date: Tue, 13 Feb 2007 21:17:08 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <45D0D77F.8030705@ericsson.com>
In-Reply-To: <45D0D77F.8030705@ericsson.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
X-OriginalArrivalTime: 13 Feb 2007 20:17:10.0388 (UTC)
	FILETIME=[F0F41B40:01C74FAB]
X-Brightmail-Tracker: AAAAAA==
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: behave@ietf.org, IETF AVT WG <avt@ietf.org>
Subject: [AVT] Re: [BEHAVE] [Fwd: Last Call:
 draft-wing-behave-symmetric-rtprtcp
 (Common Local Transmit and Receive Ports (Symmetric RTP)) to Informational
 RFC]
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

There has been raised a comment that this document should contain a=20
normative recommendation on using symmetric ports. However to make this=20
happen the document would need to be a BCP. I am willing to consider=20
this but would like to have AVT and Behave WG participant's view on=20
doing this before progressing down that road and updating the IETF last=20
call. So please provide comments by Tuesday 20th of Feb on this issue.

Best Regards

Magnus

Magnus Westerlund skrev:
> Hi,
>=20
> This document has been raised before in both AVT and BEHAVE WG. I have=20
> chosen to AD sponsor this document for publication as informational=20
> status because it seems to be of general interest. You have 4 weeks to=20
> provide any comments on the document.
>=20
> Magnus Westerlund
>=20
> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>=20
> -----------------------------------------------------------------------=
-
>=20
> =C3=84mne:
> Last Call: draft-wing-behave-symmetric-rtprtcp (Common Local Transmit=20
> and Receive Ports (Symmetric RTP)) to Informational RFC
> Fr=C3=A5n:
> The IESG <iesg-secretary@ietf.org>
> Datum:
> Mon, 12 Feb 2007 15:44:51 -0500
> Till:
> IETF-Announce <ietf-announce@ietf.org>
>=20
> Till:
> IETF-Announce <ietf-announce@ietf.org>
>=20
>=20
> The IESG has received a request from an individual submitter to conside=
r
> the following document:
>=20
> - 'Common Local Transmit and Receive Ports (Symmetric RTP) '
>    <draft-wing-behave-symmetric-rtprtcp-01.txt> as an Informational RFC
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send substantive comments to the
> ietf@ietf.org mailing lists by 2007-03-12. Exceptionally,=20
> comments may be sent to iesg@ietf.org instead. In either case, please=20
> retain the beginning of the Subject line to allow automated sorting.
>=20
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-wing-behave-symmetric-rtprtcp=
-01.txt
>=20
>=20
> IESG discussion can be tracked via
> https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dview_id&dT=
ag=3D13165&rfc_flag=3D0
>=20
>=20
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce
>=20
>=20
>=20
> -----------------------------------------------------------------------=
-
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www1.ietf.org/mailman/listinfo/behave


--=20

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



From avt-bounces@ietf.org Tue Feb 13 15:23:03 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH4AD-0006Jj-9a; Tue, 13 Feb 2007 15:22:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HH4AC-0006JZ-9Y
	for avt@ietf.org; Tue, 13 Feb 2007 15:22:08 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HH4AA-0004LB-SB
	for avt@ietf.org; Tue, 13 Feb 2007 15:22:08 -0500
Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l1DKM5Sk015401
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 13 Feb 2007 12:22:05 -0800
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com
	[172.30.32.65])
	by hamtaro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l1DKM3xa027146; Tue, 13 Feb 2007 12:22:04 -0800 (PST)
Received: from NAEX01.qualcomm.com ([129.46.51.60]) by
	SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 13 Feb 2007 12:22:04 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] CCM draft review -- should
	"bandwidth"includetheheaderoverhead
Date: Tue, 13 Feb 2007 12:22:00 -0800
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B028B0731@NAEX01.na.qualcomm.com>
In-Reply-To: <2CA3E1B6CEC064449CAA7D0FAB46079B028B06D7@NAEX01.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] CCM draft review -- should
	"bandwidth"includetheheaderoverhead
Thread-Index: AcdPata3K58y9RVnTlu9EMo/M26teQAKeE3gAATWBiA=
References: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com><ybumz3jumsx.fsf@jesup.eng.wgate.com><2CA3E1B6CEC064449CAA7D0FAB46079B028B05E2@NAEX01.na.qualcomm.com><p06230914c1f6a200bde6@[17.202.35.52]><144ED8561CE90C41A3E5908EDECE315C730CD9@IsrExch01.israel.polycom.com><ybusldajln0.fsf@jesup.eng.wgate.com>
	<2CA3E1B6CEC064449CAA7D0FAB46079B028B06D7@NAEX01.na.qualcomm.com>
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>,
	"Randell Jesup" <rjesup@wgate.com>, "Even, Roni" <roni.even@polycom.co.il>
X-OriginalArrivalTime: 13 Feb 2007 20:22:04.0039 (UTC)
	FILETIME=[9FFBB170:01C74FAC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: Dave Singer <singer@apple.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org


Codec control message should be independent of transport. Roni's view
makes it a true codec control message. (Re)Using it for signaling
transport/link status/bandwidth changes will make it less obvious for
codec control usage.

A message that captures transport/link status/bitrate changes alone does
not well qualify for being a true codec control message. If there is a
use case for such a message, it is better to define it as a separate
RTCP report message (not call it a codec control message) and solve the
header overhead problem with the help of the new message (and any
additional signaling). Let's keep things simple by not introducing
transport specific issues in TMMBR.

> -----Original Message-----
> From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> Sent: Tuesday, February 13, 2007 9:38 AM
> To: Randell Jesup; Even, Roni
> Cc: Dave Singer; avt@ietf.org
> Subject: RE: [AVT] CCM draft review -- should
> "bandwidth"includetheheaderoverhead
>=20
>=20
>=20
> > -----Original Message-----
> > From: Randell Jesup [mailto:rjesup@wgate.com]
> >
> > "Even, Roni" <roni.even@polycom.co.il> writes:
> > >I think that looking at it from the perspective of the link is not
> the
> > >right direction.  The first question to ask is why does the
receiver
> > wants
> > >to send a TMMBR which is a temporary change. I gave a couple of
> examples
> > >in previous emails. (speed between IP and circuit switch, dividing
> the
> > bit
> > >rate between two video streams, processing issues on codec) Once
you
> know
> > >why the receiver wants to do it than you can try to analyze what
the
> > >receiver knows at that stage in order to ask the correct speed.  My
> point
> > >that in most cases when the receiver wants to reduce the speed it
has
> to
> > >do with the coder on the receiver side which knows the media bit
rate
> and
> > >not the link overhead.
> >
> > Aha.  This explains some of the disconnect occuring here.  Those are
> uses
> > that haven't even crossed my mind for TMMBR.
> >
> > I (and I assume the 3G people, and David Singer and Magnus I think)
> are
> > looking to TMMBR for link status changes, while you are looking to
it
> for
> > a
> > very different (more codec-oriented) purpose.
> >
>=20
> If TMMBR is not codec oriented then it should not be treated as a
codec
> control message and it has to be taken out from "codec control
messages"
> draft.
>=20
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

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



From avt-bounces@ietf.org Tue Feb 13 15:43:10 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH4TY-00014e-BV; Tue, 13 Feb 2007 15:42:08 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HH4TX-00013v-D4
	for avt@ietf.org; Tue, 13 Feb 2007 15:42:07 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HH4TV-0006KJ-SD
	for avt@ietf.org; Tue, 13 Feb 2007 15:42:07 -0500
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l1DKg36E032396
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 13 Feb 2007 12:42:04 -0800
Received: from SANEXCAS02.na.qualcomm.com (sanexcas02.qualcomm.com
	[172.30.36.176])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l1DKg2b6016716; Tue, 13 Feb 2007 12:42:03 -0800
Received: from NAEX01.qualcomm.com ([129.46.51.60]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 13 Feb 2007 12:42:02 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] CCM draft review -- should
	"bandwidth"includetheheaderoverhead
Date: Tue, 13 Feb 2007 12:42:01 -0800
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B028B073B@NAEX01.na.qualcomm.com>
In-Reply-To: <2CA3E1B6CEC064449CAA7D0FAB46079B028B0731@NAEX01.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] CCM draft review -- should
	"bandwidth"includetheheaderoverhead
Thread-Index: AcdPata3K58y9RVnTlu9EMo/M26teQAKeE3gAATWBiAAAXdkQA==
References: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com><ybumz3jumsx.fsf@jesup.eng.wgate.com><2CA3E1B6CEC064449CAA7D0FAB46079B028B05E2@NAEX01.na.qualcomm.com><p06230914c1f6a200bde6@[17.202.35.52]><144ED8561CE90C41A3E5908EDECE315C730CD9@IsrExch01.israel.polycom.com><ybusldajln0.fsf@jesup.eng.wgate.com>
	<2CA3E1B6CEC064449CAA7D0FAB46079B028B06D7@NAEX01.na.qualcomm.com>
	<2CA3E1B6CEC064449CAA7D0FAB46079B028B0731@NAEX01.na.qualcomm.com>
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>,
	"Randell Jesup" <rjesup@wgate.com>, "Even, Roni" <roni.even@polycom.co.il>
X-OriginalArrivalTime: 13 Feb 2007 20:42:02.0994 (UTC)
	FILETIME=[6A9DB520:01C74FAF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Cc: Dave Singer <singer@apple.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org


Few more points after carefully reading the draft version-03

* Section 4.3 captures "Payload Specific Feedback Messages". IMHO, these
are the true codec control messages which are independent of transport
and can be directly signaled to a codec.

Payload specific feedback messages from Sec 4.3:
     0:     unassigned
     1:     Picture Loss Indication (PLI)
     2:     Slice Lost Indication (SLI)
     3:     Reference Picture Selection Indication (RPSI)
     4:     Full Intra Request Command (FIR)
     5:     Temporal-Spatial Trade-off Request (TSTR)
     6:     Temporal-Spatial Trade-off Announcement (TSTA)
     7:     Video Back Channel Message (VBCM)
     8-14:  unassigned


* Section 4.2 captures "Transport Layer Feedback Messages". TMMBR and
TMMBN are listed here along with Generic NACK. These are transport
specific feedback messages and do not purely fall in codec control
category. Ideally, transport specific messages do not qualify for being
codec control messages and hence TMMBR/TMMBN should be taken out from
this ("codec control messages") draft. If TMMBR is needed for pure codec
media control then it has to be in "payload specific" section (4.3).


Transport layer feedback messages from Sec 4.2:
      0:    unassigned
      1:    Generic NACK (as per AVPF)
      2:    Temporary Maximum Media Bit-rate Request
      3:    Temporary Maximum Media Bit-rate Notification

Thanks,
Hari

> -----Original Message-----
> From: Desineni, Harikishan
> Sent: Tuesday, February 13, 2007 12:22 PM
> To: Desineni, Harikishan; Randell Jesup; Even, Roni
> Cc: Dave Singer; avt@ietf.org
> Subject: RE: [AVT] CCM draft review -- should
> "bandwidth"includetheheaderoverhead
>=20
>=20
> Codec control message should be independent of transport. Roni's view
> makes it a true codec control message. (Re)Using it for signaling
> transport/link status/bandwidth changes will make it less obvious for
> codec control usage.
>=20
> A message that captures transport/link status/bitrate changes alone
does
> not well qualify for being a true codec control message. If there is a
use
> case for such a message, it is better to define it as a separate RTCP
> report message (not call it a codec control message) and solve the
header
> overhead problem with the help of the new message (and any additional
> signaling). Let's keep things simple by not introducing transport
specific
> issues in TMMBR.
>=20
> > -----Original Message-----
> > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > Sent: Tuesday, February 13, 2007 9:38 AM
> > To: Randell Jesup; Even, Roni
> > Cc: Dave Singer; avt@ietf.org
> > Subject: RE: [AVT] CCM draft review -- should
> > "bandwidth"includetheheaderoverhead
> >
> >
> >
> > > -----Original Message-----
> > > From: Randell Jesup [mailto:rjesup@wgate.com]
> > >
> > > "Even, Roni" <roni.even@polycom.co.il> writes:
> > > >I think that looking at it from the perspective of the link is
not
> > the
> > > >right direction.  The first question to ask is why does the
receiver
> > > wants
> > > >to send a TMMBR which is a temporary change. I gave a couple of
> > examples
> > > >in previous emails. (speed between IP and circuit switch,
dividing
> > the
> > > bit
> > > >rate between two video streams, processing issues on codec) Once
you
> > know
> > > >why the receiver wants to do it than you can try to analyze what
the
> > > >receiver knows at that stage in order to ask the correct speed.
My
> > point
> > > >that in most cases when the receiver wants to reduce the speed it
has
> > to
> > > >do with the coder on the receiver side which knows the media bit
rate
> > and
> > > >not the link overhead.
> > >
> > > Aha.  This explains some of the disconnect occuring here.  Those
are
> > uses
> > > that haven't even crossed my mind for TMMBR.
> > >
> > > I (and I assume the 3G people, and David Singer and Magnus I
think)
> > are
> > > looking to TMMBR for link status changes, while you are looking to
it
> > for
> > > a
> > > very different (more codec-oriented) purpose.
> > >
> >
> > If TMMBR is not codec oriented then it should not be treated as a
codec
> > control message and it has to be taken out from "codec control
messages"
> > draft.
> >
> >
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www1.ietf.org/mailman/listinfo/avt

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



From avt-bounces@ietf.org Tue Feb 13 15:44:52 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH4Vc-000220-EX; Tue, 13 Feb 2007 15:44:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH4Va-00021F-Bk; Tue, 13 Feb 2007 15:44:14 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HH4VY-0006Uk-Si; Tue, 13 Feb 2007 15:44:14 -0500
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-5.cisco.com with ESMTP; 13 Feb 2007 12:44:10 -0800
X-IronPort-AV: i="4.14,164,1170662400"; 
	d="scan'208"; a="388748234:sNHT2246296632"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id l1DKi8Q8006695; 
	Tue, 13 Feb 2007 12:44:08 -0800
Received: from dwingwxp ([10.32.240.194])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l1DKi8nF017281;
	Tue, 13 Feb 2007 12:44:08 -0800 (PST)
From: "Dan Wing" <dwing@cisco.com>
To: "'Magnus Westerlund'" <magnus.westerlund@ericsson.com>
Date: Tue, 13 Feb 2007 12:44:07 -0800
Message-ID: <083301c74faf$b570fb20$c2f0200a@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <45D21CC4.10909@ericsson.com>
Thread-Index: AcdPrEX0YWQ8YVSgQSOznluD8gQH6wAAUhWg
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4713; t=1171399448;
	x=1172263448; c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20[Fwd=3A=20Last=20Call=3A=20draft-wing-beha
	ve-symmetric-rtprtcp(Common=20Local=20Transmit=20and=20Receive=20Ports=20(
	Symmetric=20RTP))=20toInformational=20RFC] |Sender:=20;
	bh=tZd7LPX57cS/LVqivnXV2fL3WlekF1a2avh0JfXJREw=;
	b=H807YU3/c5ffdpDvSXMZ+zQZ/sXg/h+hMQP+88SO2stAG96AflsfvVWAMFrWpVAE5KlJr2Mx
	l2xKg/9V2nkEqkn7gLKgj9ZSEfkIkhgiYJzLj7eaTd8FhwfVagMLVhAE;
Authentication-Results: sj-dkim-7; header.From=dwing@cisco.com; dkim=pass (s
	ig from cisco.com/sjdkim7002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93e7fb8fef2e780414389440f367c879
Cc: behave@ietf.org, 'IETF AVT WG' <avt@ietf.org>
Subject: [AVT] RE: [BEHAVE] [Fwd: Last Call:
	draft-wing-behave-symmetric-rtprtcp(Common Local Transmit and
	Receive Ports (Symmetric RTP)) toInformational RFC]
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Per Francois's suggestion, the following new text would be placed at the =
end
of section 3 of draft-wing-behave-symmetric-rtprtcp:

  "For these reasons it is RECOMMENDED that symmetric RTP and=20
   symmetric RTCP always be used for bi-directional RTP media=20
   streams."=20

-d

> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]=20
> Sent: Tuesday, February 13, 2007 12:17 PM
> To: Magnus Westerlund
> Cc: behave@ietf.org; IETF AVT WG
> Subject: Re: [BEHAVE] [Fwd: Last Call:=20
> draft-wing-behave-symmetric-rtprtcp(Common Local Transmit and=20
> Receive Ports (Symmetric RTP)) toInformational RFC]
>=20
> There has been raised a comment that this document should contain a=20
> normative recommendation on using symmetric ports. However to=20
> make this=20
> happen the document would need to be a BCP. I am willing to consider=20
> this but would like to have AVT and Behave WG participant's view on=20
> doing this before progressing down that road and updating the=20
> IETF last=20
> call. So please provide comments by Tuesday 20th of Feb on this issue.
>=20
> Best Regards
>=20
> Magnus
>=20
> Magnus Westerlund skrev:
> > Hi,
> >=20
> > This document has been raised before in both AVT and BEHAVE=20
> WG. I have=20
> > chosen to AD sponsor this document for publication as informational=20
> > status because it seems to be of general interest. You have=20
> 4 weeks to=20
> > provide any comments on the document.
> >=20
> > Magnus Westerlund
> >=20
> > IETF Transport Area Director & TSVWG Chair
> >=20
> ----------------------------------------------------------------------
> > Multimedia Technologies, Ericsson Research EAB/TVA/A
> >=20
> ----------------------------------------------------------------------
> > Ericsson AB                | Phone +46 8 4048287
> > Torshamsgatan 23           | Fax   +46 8 7575550
> > S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> >=20
> ----------------------------------------------------------------------
> >=20
> >=20
> --------------------------------------------------------------
> ----------
> >=20
> > =C4mne:
> > Last Call: draft-wing-behave-symmetric-rtprtcp (Common=20
> Local Transmit=20
> > and Receive Ports (Symmetric RTP)) to Informational RFC
> > Fr=E5n:
> > The IESG <iesg-secretary@ietf.org>
> > Datum:
> > Mon, 12 Feb 2007 15:44:51 -0500
> > Till:
> > IETF-Announce <ietf-announce@ietf.org>
> >=20
> > Till:
> > IETF-Announce <ietf-announce@ietf.org>
> >=20
> >=20
> > The IESG has received a request from an individual=20
> submitter to consider
> > the following document:
> >=20
> > - 'Common Local Transmit and Receive Ports (Symmetric RTP) '
> >    <draft-wing-behave-symmetric-rtprtcp-01.txt> as an=20
> Informational RFC
> >=20
> > The IESG plans to make a decision in the next few weeks,=20
> and solicits
> > final comments on this action.  Please send substantive=20
> comments to the
> > ietf@ietf.org mailing lists by 2007-03-12. Exceptionally,=20
> > comments may be sent to iesg@ietf.org instead. In either=20
> case, please=20
> > retain the beginning of the Subject line to allow automated sorting.
> >=20
> > The file can be obtained via
> >=20
> http://www.ietf.org/internet-drafts/draft-wing-behave-symmetri
> c-rtprtcp-01.txt
> >=20
> >=20
> > IESG discussion can be tracked via
> >=20
> https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dvie
> w_id&dTag=3D13165&rfc_flag=3D0
> >=20
> >=20
> > _______________________________________________
> > IETF-Announce mailing list
> > IETF-Announce@ietf.org
> > https://www1.ietf.org/mailman/listinfo/ietf-announce
> >=20
> >=20
> >=20
> >=20
> --------------------------------------------------------------
> ----------
> >=20
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www1.ietf.org/mailman/listinfo/behave
>=20
>=20
> --=20
>=20
> Magnus Westerlund
>=20
> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www1.ietf.org/mailman/listinfo/behave

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



From avt-bounces@ietf.org Tue Feb 13 16:27:49 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH5Ac-0005UA-DX; Tue, 13 Feb 2007 16:26:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH5Aa-0005Tj-FQ; Tue, 13 Feb 2007 16:26:36 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HH5AU-0006gF-QD; Tue, 13 Feb 2007 16:26:36 -0500
Received: from sj-dkim-8.cisco.com ([171.68.10.93])
	by sj-iport-4.cisco.com with ESMTP; 13 Feb 2007 13:26:30 -0800
X-IronPort-AV: i="4.14,164,1170662400"; 
	d="scan'208"; a="39283429:sNHT147035007"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-8.cisco.com (8.12.11/8.12.11) with ESMTP id l1DLQUWP022987; 
	Tue, 13 Feb 2007 13:26:30 -0800
Received: from dwingwxp ([10.32.240.194])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l1DLQNho000703;
	Tue, 13 Feb 2007 13:26:23 -0800 (PST)
From: "Dan Wing" <dwing@cisco.com>
To: "'David Barrett'" <dbarrett@quinthar.com>,
	"'Magnus Westerlund'" <magnus.westerlund@ericsson.com>
Date: Tue, 13 Feb 2007 13:26:22 -0800
Message-ID: <0a3401c74fb5$a01f9e10$c2f0200a@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <07fa01c74fb1$2fc20a80$6b02a8c0@Quinthar>
Thread-Index: AcdPrEX0YWQ8YVSgQSOznluD8gQH6wAAUhWgAAC0ykAAASKhMA==
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7399; t=1171401990;
	x=1172265990; c=relaxed/simple; s=sjdkim8002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20[Fwd=3A=20Last=20Call=3Adraft-wing-behave-
	symmetric-rtprtcp(Common=20Local=20Transmit=20andReceive=20Ports=20(Symmet
	ric=20RTP))=20toInformational=20RFC] |Sender:=20;
	bh=zMaMynsO7amXjWUWyjBctdM3QIryeiiK3V6jH3HU1es=;
	b=Yo5B1ddiyOpS6nBUkjtjkh3UUEF6fdC3RANFlgmQdP35Aja6SjB6goE0oVmSicb2ZcLdfEnC
	FcTjTwv7uD2A07KcKYbdnI+IibHVfuLc14t1TkE1pJUUt89Tl76ilRxh;
Authentication-Results: sj-dkim-8; header.From=dwing@cisco.com; dkim=pass (s
	ig from cisco.com/sjdkim8002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d008c19e97860b8641c1851f84665a75
Cc: behave@ietf.org, 'IETF AVT WG' <avt@ietf.org>
Subject: [AVT] RE: [BEHAVE] [Fwd: Last
	Call:draft-wing-behave-symmetric-rtprtcp(Common Local
	Transmit andReceive Ports (Symmetric RTP)) toInformational RFC]
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Some NATs will close down NAT bindings after some number of seconds if =
there
is only outside->inside traffic and no inside->outside traffic on that =
same
5-tuple.  If you were to encounter such a NAT with the optimization you
describe below, the RTP traffic from the TURN server would stop after
awhile.  I suppose you could work around that NAT behavior, and still do
this optimization technique, if you were to send some sort of outgoing
traffic (inside->outside) to your own TURN server.

-d
=20

> -----Original Message-----
> From: David Barrett [mailto:dbarrett@quinthar.com]=20
> Sent: Tuesday, February 13, 2007 12:55 PM
> To: 'Dan Wing'; 'Magnus Westerlund'
> Cc: behave@ietf.org; 'IETF AVT WG'
> Subject: RE: [BEHAVE] [Fwd: Last=20
> Call:draft-wing-behave-symmetric-rtprtcp(Common Local=20
> Transmit andReceive Ports (Symmetric RTP)) toInformational RFC]
>=20
> Though I think it's still a good recommendation, one thing I=20
> found when
> working on iGlance was the case where two users were each=20
> behind a different
> TURN relay server.
>=20
> With symmetric RTP (if I understand correctly), for me to=20
> send a packet to
> you I need to send it up to my TURN server, which forwards it=20
> to your TURN
> server, which sends it to you.  Ideally I'd send it to your=20
> TURN server
> direct, and cut out one relay.
>=20
> The problem with this is it means our RTP isn't strictly=20
> symmetric -- I
> receive from one place (my TURN server), but send to another=20
> (your TURN
> server).
>=20
> Am I misunderstanding how symmetric RTP works?  Perhaps this=20
> is too minor a
> point to discuss here, however.
>=20
> -david
>=20
> > -----Original Message-----
> > From: Dan Wing [mailto:dwing@cisco.com]
> > Sent: Tuesday, February 13, 2007 12:44 PM
> > To: 'Magnus Westerlund'
> > Cc: behave@ietf.org; 'IETF AVT WG'
> > Subject: RE: [BEHAVE] [Fwd: Last Call:draft-wing-behave-symmetric-
> > rtprtcp(Common Local Transmit andReceive Ports (Symmetric RTP))
> > toInformational RFC]
> >=20
> > Per Francois's suggestion, the following new text would be=20
> placed at the
> > end
> > of section 3 of draft-wing-behave-symmetric-rtprtcp:
> >=20
> >   "For these reasons it is RECOMMENDED that symmetric RTP and
> >    symmetric RTCP always be used for bi-directional RTP media
> >    streams."
> >=20
> > -d
> >=20
> > > -----Original Message-----
> > > From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> > > Sent: Tuesday, February 13, 2007 12:17 PM
> > > To: Magnus Westerlund
> > > Cc: behave@ietf.org; IETF AVT WG
> > > Subject: Re: [BEHAVE] [Fwd: Last Call:
> > > draft-wing-behave-symmetric-rtprtcp(Common Local Transmit and
> > > Receive Ports (Symmetric RTP)) toInformational RFC]
> > >
> > > There has been raised a comment that this document should=20
> contain a
> > > normative recommendation on using symmetric ports. However to
> > > make this
> > > happen the document would need to be a BCP. I am willing=20
> to consider
> > > this but would like to have AVT and Behave WG=20
> participant's view on
> > > doing this before progressing down that road and updating the
> > > IETF last
> > > call. So please provide comments by Tuesday 20th of Feb=20
> on this issue.
> > >
> > > Best Regards
> > >
> > > Magnus
> > >
> > > Magnus Westerlund skrev:
> > > > Hi,
> > > >
> > > > This document has been raised before in both AVT and BEHAVE
> > > WG. I have
> > > > chosen to AD sponsor this document for publication as=20
> informational
> > > > status because it seems to be of general interest. You have
> > > 4 weeks to
> > > > provide any comments on the document.
> > > >
> > > > Magnus Westerlund
> > > >
> > > > IETF Transport Area Director & TSVWG Chair
> > > >
> > >=20
> ----------------------------------------------------------------------
> > > > Multimedia Technologies, Ericsson Research EAB/TVA/A
> > > >
> > >=20
> ----------------------------------------------------------------------
> > > > Ericsson AB                | Phone +46 8 4048287
> > > > Torshamsgatan 23           | Fax   +46 8 7575550
> > > > S-164 80 Stockholm, Sweden | mailto:=20
> magnus.westerlund@ericsson.com
> > > >
> > >=20
> ----------------------------------------------------------------------
> > > >
> > > >
> > > --------------------------------------------------------------
> > > ----------
> > > >
> > > > =C4mne:
> > > > Last Call: draft-wing-behave-symmetric-rtprtcp (Common
> > > Local Transmit
> > > > and Receive Ports (Symmetric RTP)) to Informational RFC
> > > > Fr=E5n:
> > > > The IESG <iesg-secretary@ietf.org>
> > > > Datum:
> > > > Mon, 12 Feb 2007 15:44:51 -0500
> > > > Till:
> > > > IETF-Announce <ietf-announce@ietf.org>
> > > >
> > > > Till:
> > > > IETF-Announce <ietf-announce@ietf.org>
> > > >
> > > >
> > > > The IESG has received a request from an individual
> > > submitter to consider
> > > > the following document:
> > > >
> > > > - 'Common Local Transmit and Receive Ports (Symmetric RTP) '
> > > >    <draft-wing-behave-symmetric-rtprtcp-01.txt> as an
> > > Informational RFC
> > > >
> > > > The IESG plans to make a decision in the next few weeks,
> > > and solicits
> > > > final comments on this action.  Please send substantive
> > > comments to the
> > > > ietf@ietf.org mailing lists by 2007-03-12. Exceptionally,
> > > > comments may be sent to iesg@ietf.org instead. In either
> > > case, please
> > > > retain the beginning of the Subject line to allow=20
> automated sorting.
> > > >
> > > > The file can be obtained via
> > > >
> > > http://www.ietf.org/internet-drafts/draft-wing-behave-symmetri
> > > c-rtprtcp-01.txt
> > > >
> > > >
> > > > IESG discussion can be tracked via
> > > >
> > > https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dvie
> > > w_id&dTag=3D13165&rfc_flag=3D0
> > > >
> > > >
> > > > _______________________________________________
> > > > IETF-Announce mailing list
> > > > IETF-Announce@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/ietf-announce
> > > >
> > > >
> > > >
> > > >
> > > --------------------------------------------------------------
> > > ----------
> > > >
> > > > _______________________________________________
> > > > Behave mailing list
> > > > Behave@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/behave
> > >
> > >
> > > --
> > >
> > > Magnus Westerlund
> > >
> > > IETF Transport Area Director & TSVWG Chair
> > >=20
> ----------------------------------------------------------------------
> > > Multimedia Technologies, Ericsson Research EAB/TVA/A
> > >=20
> ----------------------------------------------------------------------
> > > Ericsson AB                | Phone +46 8 4048287
> > > Torshamsgatan 23           | Fax   +46 8 7575550
> > > S-164 80 Stockholm, Sweden | mailto:=20
> magnus.westerlund@ericsson.com
> > >=20
> ----------------------------------------------------------------------
> > >
> > > _______________________________________________
> > > Behave mailing list
> > > Behave@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/behave
> >=20
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www1.ietf.org/mailman/listinfo/behave

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



From avt-bounces@ietf.org Tue Feb 13 16:44:09 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH5QS-0004nC-LA; Tue, 13 Feb 2007 16:43:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HH5QR-0004mM-6h
	for avt@ietf.org; Tue, 13 Feb 2007 16:42:59 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HH5QP-0000tK-O8
	for avt@ietf.org; Tue, 13 Feb 2007 16:42:59 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	3A373204F4; Tue, 13 Feb 2007 22:42:55 +0100 (CET)
X-AuditID: c1b4fb3e-b06d4bb0000007e1-2f-45d230df738a 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	1A729201F5; Tue, 13 Feb 2007 22:42:55 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 13 Feb 2007 22:42:54 +0100
Received: from [138.85.12.222] ([138.85.12.222]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 13 Feb 2007 22:42:53 +0100
Message-ID: <45D230DA.7040101@ericsson.com>
Date: Tue, 13 Feb 2007 22:42:50 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: "Even, Roni" <roni.even@polycom.co.il>
Subject: Re: [AVT] CCM draft review -- should "bandwidth" include the
	headeroverhead
References: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com>
	<10E7D146-0080-420A-BEF4-44C22DD7BAE0@stewe.org>
	<45D0DE49.4060105@ericsson.com>
	<144ED8561CE90C41A3E5908EDECE315C730CD5@IsrExch01.israel.polycom.com>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C730CD5@IsrExch01.israel.polycom.com>
Content-Type: text/plain; charset=windows-1255; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Feb 2007 21:42:54.0223 (UTC)
	FILETIME=[EAEB09F0:01C74FB7]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: Randell Jesup <rjesup@wgate.com>, Stephan Wenger <stewe@stewe.org>,
	avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Even, Roni skrev:
> 
> Magnus,
> We are talking about TMMBR which happens after the receiver has already 
> received media and can know what is the payload bit rate.

I see this as being problematic for several reasons. The first one is 
that the sender may not at all send at rates close to the TMMBR rate you 
request. For example due to congestion. Remember that TMMBR is not for 
real congestion control. Thus the receiver has no data on which 
combination of packet rates and packetization it will use for any 
maximum packet rate. Thus the actual bit-rate consumed may be 
significantly different from what the receiver requested. Also this 
implies that the sender are restricted in there of change packet rate 
and packetization parameters. To me this seems to yield much larger 
discrepancies than your actual gross rate and seen overhead.

>  
> As for fragmentation you should know that knowing the path MTU do not 
> make each sender break a frame to the same sizes. Example MTU=500 frame 
> = 800. can be broken to 400 and 400 or 300, 300 and 200 based on policy 
> for breaking on macro block or GOB boundary or any other algorithm as 
> long as smaller than MTU.

No, this is another argument why the sender should know gross bit-rate 
and can take into account what changing the packetization will result 
in. Using a media bit-rate will not provide any restrictions at all on 
the fragmentation, while gross-bitrate will have impact on how you break 
up packets.

>  
>  
> Repacketization in a middlebox can happen between two networks with 
> different MTUs and the middle box cannot reduce the rate (it does not 
> transcode). RTCP may flow end to end (this is a viable topology in the 
> topolgy draft).
>  
>  

And as the new version of topologies and CCM drafts will be clearer on 
is that a mixer or translator doing this will need to rewrite the RTCP 
messages to provide the correct image over the box. Thus this is not an 
argument against using a gross bit-rate and that media bit-rate is better.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



From avt-bounces@ietf.org Tue Feb 13 17:03:42 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH5ji-0002o5-Fv; Tue, 13 Feb 2007 17:02:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HH5jh-0002nZ-OE
	for avt@ietf.org; Tue, 13 Feb 2007 17:02:53 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HH5jc-0003Qv-94
	for avt@ietf.org; Tue, 13 Feb 2007 17:02:53 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	BCB7920263; Tue, 13 Feb 2007 23:02:45 +0100 (CET)
X-AuditID: c1b4fb3e-b1ed7bb0000007e1-45-45d235855fba 
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	A26F42009C; Tue, 13 Feb 2007 23:02:45 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 13 Feb 2007 23:02:45 +0100
Received: from [138.85.12.222] ([138.85.12.222]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 13 Feb 2007 23:02:44 +0100
Message-ID: <45D23581.1030006@ericsson.com>
Date: Tue, 13 Feb 2007 23:02:41 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Dave Singer <singer@apple.com>
Subject: Re: [AVT] CCM draft review -- should "bandwidth" include
	theheaderoverhead
References: <144ED8561CE90C41A3E5908EDECE315C044ED3B2@IsrExch01.israel.polycom.com>	<ybumz3jumsx.fsf@jesup.eng.wgate.com>	<2CA3E1B6CEC064449CAA7D0FAB46079B028B05E2@NAEX01.na.qualcomm.com>
	<p06230914c1f6a200bde6@[17.202.35.52]>
In-Reply-To: <p06230914c1f6a200bde6@[17.202.35.52]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Feb 2007 22:02:44.0963 (UTC)
	FILETIME=[B0A78B30:01C74FBA]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi,

Dave Singer skrev:
> On the question of what bitrate to send, it depends on who knows what:
> 
> "Please send me a stream that fits through a constriction of x kb/s. And
> a) I know that ROHC is in use through that constriction;
> b) I know it is not;
> c) I don't know;  if you do, then you can do the partitioning;
> d) I don't know, and if you don't either, assume the worst (i.e. that it 
> is not)."
> 
> My suspicion is that we have to signal (c, d), and that (d) is the most 
> likely outcome.  That is, we include headers unless the sender knows to 
> the contrary.

Yes, I also think so. Do also notice that there is a requirement to 
combine TMMBR with congestion control. That way the sender will be 
anyway react in the cases where the real overhead in a bottleneck is 
larger than the overhead seen by a receiver.

> 
> 
> On the question of "what is bitrate", I'd suggest that we say that the 
> source was traffic-smoothed to not exceed x.  By that I mean, if I send 
> a packet of Y kbits, then the next packet is sent no earlier than Y/x 
> seconds later.  Alternatively, the bitrate is the max over all 
> consecutive pairs of packets [i,i+1] of
> (timestamp(i+1) - timestamp(i))/size(i)
> 
> which is harsh, but otherwise we'll have to define a leaky bucket model, 
> or an averaging interval.  Both of these either require signalling the 
> size of the ingest buffer to the constriction, or assuming it, neither 
> of which are pleasant.

As I see it the traffic smoothing case is the correct one. There are 
some buffering in the network that will help with this. The issue is 
that one don't know how much, thus one has to be careful. If one defines 
a token bucket then one needs to find a level of buffering that is 
available. I don't see how that will be possible.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



From avt-bounces@ietf.org Tue Feb 13 17:28:45 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH67f-0005nE-8P; Tue, 13 Feb 2007 17:27:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HH4gQ-0006JC-Li
	for avt@ietf.org; Tue, 13 Feb 2007 15:55:26 -0500
Received: from quinthar.com ([64.62.221.66])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HH4fw-000067-II
	for avt@ietf.org; Tue, 13 Feb 2007 15:55:26 -0500
Received: from Quinthar ([67.169.180.240]) by quinthar.com for <avt@ietf.org>;
	Tue, 13 Feb 2007 12:54:42 -0800
From: "David Barrett" <dbarrett@quinthar.com>
To: "'Dan Wing'" <dwing@cisco.com>,
	"'Magnus Westerlund'" <magnus.westerlund@ericsson.com>
Date: Tue, 13 Feb 2007 12:54:40 -0800
Message-ID: <07fa01c74fb1$2fc20a80$6b02a8c0@Quinthar>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <083301c74faf$b570fb20$c2f0200a@amer.cisco.com>
Thread-Index: AcdPrEX0YWQ8YVSgQSOznluD8gQH6wAAUhWgAAC0ykA=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ccfb4541e989aa743998098cd315d0fd
X-Mailman-Approved-At: Tue, 13 Feb 2007 17:27:37 -0500
Cc: behave@ietf.org, 'IETF AVT WG' <avt@ietf.org>
Subject: [AVT] RE: [BEHAVE] [Fwd: Last
	Call:draft-wing-behave-symmetric-rtprtcp(Common Local
	Transmit andReceive Ports (Symmetric RTP)) toInformational RFC]
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Though I think it's still a good recommendation, one thing I found when
working on iGlance was the case where two users were each behind a =
different
TURN relay server.

With symmetric RTP (if I understand correctly), for me to send a packet =
to
you I need to send it up to my TURN server, which forwards it to your =
TURN
server, which sends it to you.  Ideally I'd send it to your TURN server
direct, and cut out one relay.

The problem with this is it means our RTP isn't strictly symmetric -- I
receive from one place (my TURN server), but send to another (your TURN
server).

Am I misunderstanding how symmetric RTP works?  Perhaps this is too =
minor a
point to discuss here, however.

-david

> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com]
> Sent: Tuesday, February 13, 2007 12:44 PM
> To: 'Magnus Westerlund'
> Cc: behave@ietf.org; 'IETF AVT WG'
> Subject: RE: [BEHAVE] [Fwd: Last Call:draft-wing-behave-symmetric-
> rtprtcp(Common Local Transmit andReceive Ports (Symmetric RTP))
> toInformational RFC]
>=20
> Per Francois's suggestion, the following new text would be placed at =
the
> end
> of section 3 of draft-wing-behave-symmetric-rtprtcp:
>=20
>   "For these reasons it is RECOMMENDED that symmetric RTP and
>    symmetric RTCP always be used for bi-directional RTP media
>    streams."
>=20
> -d
>=20
> > -----Original Message-----
> > From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> > Sent: Tuesday, February 13, 2007 12:17 PM
> > To: Magnus Westerlund
> > Cc: behave@ietf.org; IETF AVT WG
> > Subject: Re: [BEHAVE] [Fwd: Last Call:
> > draft-wing-behave-symmetric-rtprtcp(Common Local Transmit and
> > Receive Ports (Symmetric RTP)) toInformational RFC]
> >
> > There has been raised a comment that this document should contain a
> > normative recommendation on using symmetric ports. However to
> > make this
> > happen the document would need to be a BCP. I am willing to consider
> > this but would like to have AVT and Behave WG participant's view on
> > doing this before progressing down that road and updating the
> > IETF last
> > call. So please provide comments by Tuesday 20th of Feb on this =
issue.
> >
> > Best Regards
> >
> > Magnus
> >
> > Magnus Westerlund skrev:
> > > Hi,
> > >
> > > This document has been raised before in both AVT and BEHAVE
> > WG. I have
> > > chosen to AD sponsor this document for publication as =
informational
> > > status because it seems to be of general interest. You have
> > 4 weeks to
> > > provide any comments on the document.
> > >
> > > Magnus Westerlund
> > >
> > > IETF Transport Area Director & TSVWG Chair
> > >
> > =
----------------------------------------------------------------------
> > > Multimedia Technologies, Ericsson Research EAB/TVA/A
> > >
> > =
----------------------------------------------------------------------
> > > Ericsson AB                | Phone +46 8 4048287
> > > Torshamsgatan 23           | Fax   +46 8 7575550
> > > S-164 80 Stockholm, Sweden | mailto: =
magnus.westerlund@ericsson.com
> > >
> > =
----------------------------------------------------------------------
> > >
> > >
> > --------------------------------------------------------------
> > ----------
> > >
> > > =C4mne:
> > > Last Call: draft-wing-behave-symmetric-rtprtcp (Common
> > Local Transmit
> > > and Receive Ports (Symmetric RTP)) to Informational RFC
> > > Fr=E5n:
> > > The IESG <iesg-secretary@ietf.org>
> > > Datum:
> > > Mon, 12 Feb 2007 15:44:51 -0500
> > > Till:
> > > IETF-Announce <ietf-announce@ietf.org>
> > >
> > > Till:
> > > IETF-Announce <ietf-announce@ietf.org>
> > >
> > >
> > > The IESG has received a request from an individual
> > submitter to consider
> > > the following document:
> > >
> > > - 'Common Local Transmit and Receive Ports (Symmetric RTP) '
> > >    <draft-wing-behave-symmetric-rtprtcp-01.txt> as an
> > Informational RFC
> > >
> > > The IESG plans to make a decision in the next few weeks,
> > and solicits
> > > final comments on this action.  Please send substantive
> > comments to the
> > > ietf@ietf.org mailing lists by 2007-03-12. Exceptionally,
> > > comments may be sent to iesg@ietf.org instead. In either
> > case, please
> > > retain the beginning of the Subject line to allow automated =
sorting.
> > >
> > > The file can be obtained via
> > >
> > http://www.ietf.org/internet-drafts/draft-wing-behave-symmetri
> > c-rtprtcp-01.txt
> > >
> > >
> > > IESG discussion can be tracked via
> > >
> > https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dvie
> > w_id&dTag=3D13165&rfc_flag=3D0
> > >
> > >
> > > _______________________________________________
> > > IETF-Announce mailing list
> > > IETF-Announce@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/ietf-announce
> > >
> > >
> > >
> > >
> > --------------------------------------------------------------
> > ----------
> > >
> > > _______________________________________________
> > > Behave mailing list
> > > Behave@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/behave
> >
> >
> > --
> >
> > Magnus Westerlund
> >
> > IETF Transport Area Director & TSVWG Chair
> > =
----------------------------------------------------------------------
> > Multimedia Technologies, Ericsson Research EAB/TVA/A
> > =
----------------------------------------------------------------------
> > Ericsson AB                | Phone +46 8 4048287
> > Torshamsgatan 23           | Fax   +46 8 7575550
> > S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> > =
----------------------------------------------------------------------
> >
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www1.ietf.org/mailman/listinfo/behave
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www1.ietf.org/mailman/listinfo/behave


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

From avt-bounces@ietf.org Tue Feb 13 17:28:45 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH67f-0005nJ-IO; Tue, 13 Feb 2007 17:27:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH4sl-0008Be-Ap; Tue, 13 Feb 2007 16:08:11 -0500
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HH4sK-0002Nz-Uk; Tue, 13 Feb 2007 16:08:10 -0500
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l1DL4AA6020347; Tue, 13 Feb 2007 23:04:18 +0200
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 13 Feb 2007 23:07:00 +0200
Received: from esebe108.NOE.Nokia.com ([172.21.138.114]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 13 Feb 2007 23:07:28 +0200
Received: from 172.21.143.123 ([172.21.143.123]) by esebe108.NOE.Nokia.com
	([172.21.138.114]) with Microsoft Exchange Server HTTP-DAV ; 
	Tue, 13 Feb 2007 21:07:27 +0000
From: "Denis-Courmont Remi \(Nokia-TP-MSW/Helsinki\)"
	<Remi.Denis-Courmont@nokia.com>
To: "ext David Barrett" <dbarrett@quinthar.com>,
	"'Dan Wing'" <dwing@cisco.com>,
	"'Magnus Westerlund'" <magnus.westerlund@ericsson.com>
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 13 Feb 2007 21:07:24 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Thread-Topic: [BEHAVE] [Fwd: LastCall:draft-wing-behave-symmetric-rtprtcp(Co
	mmon Local TransmitandReceive Ports (Symmetric RTP))
	toInformational RFC]
Thread-Index: AcdPrEX0YWQ8YVSgQSOznluD8gQH6wAAUhWgAAC0ykAAAKFKQw==
Message-ID: <1a6401c74fb2$e69b1860$7b8f15ac@NOE.Nokia.com>
X-Mailer: EAS Version 1.00
MIME-Version: 1.0
Content-Language: i-default
X-OriginalArrivalTime: 13 Feb 2007 21:07:28.0571 (UTC)
	FILETIME=[F7EE48B0:01C74FB2]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::070213230418-4EC45BB0-2E3A68A2/1541828286-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 140baa79ca42e6b0e2b4504291346186
X-Mailman-Approved-At: Tue, 13 Feb 2007 17:27:37 -0500
Cc: behave@ietf.org, 'IETF AVT WG' <avt@ietf.org>
Subject: [AVT] RE: [BEHAVE] [Fwd:
	LastCall:draft-wing-behave-symmetric-rtprtcp(Co mmon Local
	TransmitandReceive Ports (Symmetric RTP)) toInformational RFC]
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hmm... Bypassing TURN relays might be tempting but IMHO you should stick =
to whatever ICE yield. If only one TURN relay is needed, ICE ought to =
find it out. Otherwise, it could that policy mandates TURN or whatever =
requires relays on both sides...

R=C3=A9mi Denis-Courmont

--- message original ---
De : "ext David Barrett" <dbarrett@quinthar.com>
Objet : RE: [BEHAVE] [Fwd: =
LastCall:draft-wing-behave-symmetric-rtprtcp(Common Local =
TransmitandReceive Ports (Symmetric RTP)) toInformational RFC]
Date : 13 f=C3=A9vrier 2007
Heure : 22:56:18

Though I think it's still a good recommendation, one thing I found when
working on iGlance was the case where two users were each behind a =
different
TURN relay server.

With symmetric RTP (if I understand correctly), for me to send a packet =
to
you I need to send it up to my TURN server, which forwards it to your =
TURN
server, which sends it to you.  Ideally I'd send it to your TURN server
direct, and cut out one relay.

The problem with this is it means our RTP isn't strictly symmetric -- I
receive from one place (my TURN server), but send to another (your TURN
server).

Am I misunderstanding how symmetric RTP works?  Perhaps this is too =
minor a
point to discuss here, however.

-david

> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com]
> Sent: Tuesday, February 13, 2007 12:44 PM
> To: 'Magnus Westerlund'
> Cc: behave@ietf.org; 'IETF AVT WG'
> Subject: RE: [BEHAVE] [Fwd: Last Call:draft-wing-behave-symmetric-
> rtprtcp(Common Local Transmit andReceive Ports (Symmetric RTP))
> toInformational RFC]
>=20
> Per Francois's suggestion, the following new text would be placed at =
the
> end
> of section 3 of draft-wing-behave-symmetric-rtprtcp:
>=20
>   "For these reasons it is RECOMMENDED that symmetric RTP and
>    symmetric RTCP always be used for bi-directional RTP media
>    streams."
>=20
> -d
>=20
> > -----Original Message-----
> > From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> > Sent: Tuesday, February 13, 2007 12:17 PM
> > To: Magnus Westerlund
> > Cc: behave@ietf.org; IETF AVT WG
> > Subject: Re: [BEHAVE] [Fwd: Last Call:
> > draft-wing-behave-symmetric-rtprtcp(Common Local Transmit and
> > Receive Ports (Symmetric RTP)) toInformational RFC]
> >
> > There has been raised a comment that this document should contain a
> > normative recommendation on using symmetric ports. However to
> > make this
> > happen the document would need to be a BCP. I am willing to consider
> > this but would like to have AVT and Behave WG participant's view on
> > doing this before progressing down that road and updating the
> > IETF last
> > call. So please provide comments by Tuesday 20th of Feb on this =
issue.
> >
> > Best Regards
> >
> > Magnus
> >
> > Magnus Westerlund skrev:
> > > Hi,
> > >
> > > This document has been raised before in both AVT and BEHAVE
> > WG. I have
> > > chosen to AD sponsor this document for publication as =
informational
> > > status because it seems to be of general interest. You have
> > 4 weeks to
> > > provide any comments on the document.
> > >
> > > Magnus Westerlund
> > >
> > > IETF Transport Area Director & TSVWG Chair
> > >
> > =
----------------------------------------------------------------------
> > > Multimedia Technologies, Ericsson Research EAB/TVA/A
> > >
> > =
----------------------------------------------------------------------
> > > Ericsson AB                | Phone +46 8 4048287
> > > Torshamsgatan 23           | Fax   +46 8 7575550
> > > S-164 80 Stockholm, Sweden | mailto: =
magnus.westerlund@ericsson.com
> > >
> > =
----------------------------------------------------------------------
> > >
> > >
> > --------------------------------------------------------------
> > ----------
> > >
> > > =C3=84mne:
> > > Last Call: draft-wing-behave-symmetric-rtprtcp (Common
> > Local Transmit
> > > and Receive Ports (Symmetric RTP)) to Informational RFC
> > > Fr=C3=A5n:
> > > The IESG <iesg-secretary@ietf.org>
> > > Datum:
> > > Mon, 12 Feb 2007 15:44:51 -0500
> > > Till:
> > > IETF-Announce <ietf-announce@ietf.org>
> > >
> > > Till:
> > > IETF-Announce <ietf-announce@ietf.org>
> > >
> > >
> > > The IESG has received a request from an individual
> > submitter to consider
> > > the following document:
> > >
> > > - 'Common Local Transmit and Receive Ports (Symmetric RTP) '
> > >    <draft-wing-behave-symmetric-rtprtcp-01.txt> as an
> > Informational RFC
> > >
> > > The IESG plans to make a decision in the next few weeks,
> > and solicits
> > > final comments on this action.  Please send substantive
> > comments to the
> > > ietf@ietf.org mailing lists by 2007-03-12. Exceptionally,
> > > comments may be sent to iesg@ietf.org instead. In either
> > case, please
> > > retain the beginning of the Subject line to allow automated =
sorting.
> > >
> > > The file can be obtained via
> > >
> > http://www.ietf.org/internet-drafts/draft-wing-behave-symmetri
> > c-rtprtcp-01.txt
> > >
> > >
> > > IESG discussion can be tracked via
> > >
> > https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dvie
> > w_id&dTag=3D13165&rfc_flag=3D0
> > >
> > >
> > > _______________________________________________
> > > IETF-Announce mailing list
> > > IETF-Announce@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/ietf-announce
> > >
> > >
> > >
> > >
> > -----------------------------From avt-bounces@ietf.org Tue Feb 13 17:28:45 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH67f-0005nE-8P; Tue, 13 Feb 2007 17:27:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HH4gQ-0006JC-Li
	for avt@ietf.org; Tue, 13 Feb 2007 15:55:26 -0500
Received: from quinthar.com ([64.62.221.66])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HH4fw-000067-II
	for avt@ietf.org; Tue, 13 Feb 2007 15:55:26 -0500
Received: from Quinthar ([67.169.180.240]) by quinthar.com for <avt@ietf.org>;
	Tue, 13 Feb 2007 12:54:42 -0800
From: "David Barrett" <dbarrett@quinthar.com>
To: "'Dan Wing'" <dwing@cisco.com>,
	"'Magnus Westerlund'" <magnus.westerlund@ericsson.com>
Date: Tue, 13 Feb 2007 12:54:40 -0800
Message-ID: <07fa01c74fb1$2fc20a80$6b02a8c0@Quinthar>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <083301c74faf$b570fb20$c2f0200a@amer.cisco.com>
Thread-Index: AcdPrEX0YWQ8YVSgQSOznluD8gQH6wAAUhWgAAC0ykA=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ccfb4541e989aa743998098cd315d0fd
X-Mailman-Approved-At: Tue, 13 Feb 2007 17:27:37 -0500
Cc: behave@ietf.org, 'IETF AVT WG' <avt@ietf.org>
Subject: [AVT] RE: [BEHAVE] [Fwd: Last
	Call:draft-wing-behave-symmetric-rtprtcp(Common Local
	Transmit andReceive Ports (Symmetric RTP)) toInformational RFC]
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Though I think it's still a good recommendation, one thing I found when
working on iGlance was the case where two users were each behind a =
different
TURN relay server.

With symmetric RTP (if I understand correctly), for me to send a packet =
to
you I need to send it up to my TURN server, which forwards it to your =
TURN
server, which sends it to you.  Ideally I'd send it to your TURN server
direct, and cut out one relay.

The problem with this is it means our RTP isn't strictly symmetric -- I
receive from one place (my TURN server), but send to another (your TURN
server).

Am I misunderstanding how symmetric RTP works?  Perhaps this is too =
minor a
point to discuss here, however.

-david

> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com]
> Sent: Tuesday, February 13, 2007 12:44 PM
> To: 'Magnus Westerlund'
> Cc: behave@ietf.org; 'IETF AVT WG'
> Subject: RE: [BEHAVE] [Fwd: Last Call:draft-wing-behave-symmetric-
> rtprtcp(Common Local Transmit andReceive Ports (Symmetric RTP))
> toInformational RFC]
>=20
> Per Francois's suggestion, the following new text would be placed at =
the
> end
> of section 3 of draft-wing-behave-symmetric-rtprtcp:
>=20
>   "For these reasons it is RECOMMENDED that symmetric RTP and
>    symmetric RTCP always be used for bi-directional RTP media
>    streams."
>=20
> -d
>=20
> > -----Original Message-----
> > From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> > Sent: Tuesday, February 13, 2007 12:17 PM
> > To: Magnus Westerlund
> > Cc: behave@ietf.org; IETF AVT WG
> > Subject: Re: [BEHAVE] [Fwd: Last Call:
> > draft-wing-behave-symmetric-rtprtcp(Common Local Transmit and
> > Receive Ports (Symmetric RTP)) toInformational RFC]
> >
> > There has been raised a comment that this document should contain a
> > normative recommendation on using symmetric ports. However to
> > make this
> > happen the document would need to be a BCP. I am willing to consider
> > this but would like to have AVT and Behave WG participant's view on
> > doing this before progressing down that road and updatin---------------------------------
> > ----------
> > >
> > > _______________________________________________
> > > Behave mailing list
> > > Behave@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/behave
> >
> >
> > --
> >
> > Magnus Westerlund
> >
> > IETF Transport Area Director & TSVWG Chair
> > =
----------------------------------------------------------------------
> > Multimedia Technologies, Ericsson Research EAB/TVA/A
> > =
----------------------------------------------------------------------
> > Ericsson AB                | Phone +46 8 4048287
> > Torshamsgatan 23           | Fax   +46 8 7575550
> > S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> > =
----------------------------------------------------------------------
> >
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www1.ietf.org/mailman/listinfo/behave
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www1.ietf.org/mailman/listinfo/behave


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www1.ietf.org/mailman/listinfo/behave

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





g the
> > IETF last
> > call. So please provide comments by Tuesday 20th of Feb on this =
issue.
> >
> > Best Regards
> >
> > Magnus
> >
> > Magnus Westerlund skrev:
> > > Hi,
> > >
> > > This document has been raised before in both AVT and BEHAVE
> > WG. I have
> > > chosen to AD sponsor this document for publication as =
informational
> > > status because it seems to be of general interest. You have
> > 4 weeks to
> > > provide any comments on the document.
> > >
> > > Magnus Westerlund
> > >
> > > IETF Transport Area Director & TSVWG Chair
> > >
> > =
----------------------------------------------------------------------
> > > Multimedia Technologies, Ericsson Research EAB/TVA/A
> > >
> > =
----------------------------------------------------------------------
> > > Ericsson AB                | Phone +46 8 4048287
> > > Torshamsgatan 23           | Fax   +46 8 7575550
> > > S-164 80 Stockholm, Sweden | mailto: =
magnus.westerlund@ericsson.com
> > >
> > =
----------------------------------------------------------------------
> > >
> > >
> > --------------------------------------------------------------
> > ----------
> > >
> > > =C4mne:
> > > Last Call: draft-wing-behave-symmetric-rtprtcp (Common
> > Local Transmit
> > > and Receive Ports (Symmetric RTP)) to Informational RFC
> > > Fr=E5n:
> > > The IESG <iesg-secretary@ietf.org>
> > > Datum:
> > > Mon, 12 Feb 2007 15:44:51 -0500
> > > Till:
> > > IETF-Announce <ietf-announce@ietf.org>
> > >
> > > Till:
> > > IETF-Announce <ietf-announce@ietf.org>
> > >
> > >
> > > The IESG has received a request from an individual
> > submitter to consider
> > > the following document:
> > >
> > > - 'Common Local Transmit and Receive Ports (Symmetric RTP) '
> > >    <draft-wing-behave-symmetric-rtprtcp-01.txt> as an
> > Informational RFC
> > >
> > > The IESG plans to make a decision in the next few weeks,
> > and solicits
> > > final comments on this action.  Please send substantive
> > comments to the
> > > ietf@ietf.org mailing lists by 2007-03-12. Exceptionally,
> > > comments may be sent to iesg@ietf.org instead. In either
> > case, please
> > > retain the beginning of the Subject line to allow automated =
sorting.
> > >
> > > The file can be obtained via
> > >
> > http://www.ietf.org/internet-drafts/draft-wing-behave-symmetri
> > c-rtprtcp-01.txt
> > >
> > >
> > > IESG discussion can be tracked via
> > >
> > https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dvie
> > w_id&dTag=3D13165&rfc_flag=3D0
> > >
> > >
> > > _______________________________________________
> > > IETF-Announce mailing list
> > > IETF-Announce@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/ietf-announce
> > >
> > >
> > >
> > >
> > --------------------------------------------------------------
> > ----------
> > >
> > > _______________________________________________
> > > Behave mailing list
> > > Behave@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/behave
> >
> >
> > --
> >
> > Magnus Westerlund
> >
> > IETF Transport Area Director & TSVWG Chair
> > =
----------------------------------------------------------------------
> > Multimedia Technologies, Ericsson Research EAB/TVA/A
> > =
----------------------------------------------------------------------
> > Ericsson AB                | Phone +46 8 4048287
> > Torshamsgatan 23           | Fax   +46 8 7575550
> > S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> > =
----------------------------------------------------------------------
> >
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www1.ietf.org/mailman/listinfo/behave
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www1.ietf.org/mailman/listinfo/behave


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

From avt-bounces@ietf.org Tue Feb 13 17:28:45 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH67f-0005nJ-IO; Tue, 13 Feb 2007 17:27:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH4sl-0008Be-Ap; Tue, 13 Feb 2007 16:08:11 -0500
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HH4sK-0002Nz-Uk; Tue, 13 Feb 2007 16:08:10 -0500
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l1DL4AA6020347; Tue, 13 Feb 2007 23:04:18 +0200
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 13 Feb 2007 23:07:00 +0200
Received: from esebe108.NOE.Nokia.com ([172.21.138.114]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 13 Feb 2007 23:07:28 +0200
Received: from 172.21.143.123 ([172.21.143.123]) by esebe108.NOE.Nokia.com
	([172.21.138.114]) with Microsoft Exchange Server HTTP-DAV ; 
	Tue, 13 Feb 2007 21:07:27 +0000
From: "Denis-Courmont Remi \(Nokia-TP-MSW/Helsinki\)"
	<Remi.Denis-Courmont@nokia.com>
To: "ext David Barrett" <dbarrett@quinthar.com>,
	"'Dan Wing'" <dwing@cisco.com>,
	"'Magnus Westerlund'" <magnus.westerlund@ericsson.com>
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 13 Feb 2007 21:07:24 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Thread-Topic: [BEHAVE] [Fwd: LastCall:draft-wing-behave-symmetric-rtprtcp(Co
	mmon Local TransmitandReceive Ports (Symmetric RTP))
	toInformational RFC]
Thread-Index: AcdPrEX0YWQ8YVSgQSOznluD8gQH6wAAUhWgAAC0ykAAAKFKQw==
Message-ID: <1a6401c74fb2$e69b1860$7b8f15ac@NOE.Nokia.com>
X-Mailer: EAS Version 1.00
MIME-Version: 1.0
Content-Language: i-default
X-OriginalArrivalTime: 13 Feb 2007 21:07:28.0571 (UTC)
	FILETIME=[F7EE48B0:01C74FB2]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::070213230418-4EC45BB0-2E3A68A2/1541828286-0/0-1
X-Nokia-AV: Clean
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 140baa79ca42e6b0e2b4504291346186
X-Mailman-Approved-At: Tue, 13 Feb 2007 17:27:37 -0500
Cc: behave@ietf.org, 'IETF AVT WG' <avt@ietf.org>
Subject: [AVT] RE: [BEHAVE] [Fwd:
	LastCall:draft-wing-behave-symmetric-rtprtcp(Co mmon Local
	TransmitandReceive Ports (Symmetric RTP)) toInformational RFC]
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hmm... Bypassing TURN relays might be tempting but IMHO you should stick =
to whatever ICE yield. If only one TURN relay is needed, ICE ought to =
find it out. Otherwise, it could that policy mandates TURN or whatever =
requires relays on both sides...

R=C3=A9mi Denis-Courmont

--- message original ---
De : "ext David Barrett" <dbarrett@quinthar.com>
Objet : RE: [BEHAVE] [Fwd: =
LastCall:draft-wing-behave-symmetric-rtprtcp(Common Local =
TransmitandReceive Ports (Symmetric RTP)) toInformational RFC]
Date : 13 f=C3=A9vrier 2007
Heure : 22:56:18

Though I think it's still a good recommendation, one thing I found when
working on iGlance was the case where two users were each behind a =
different
TURN relay server.

With symmetric RTP (if I understand correctly), for me to send a packet =
to
you I need to send it up to my TURN server, which forwards it to your =
TURN
server, which sends it to you.  Ideally I'd send it to your TURN server
direct, and cut out one relay.

The problem with this is it means our RTP isn't strictly symmetric -- I
receive from one place (my TURN server), but send to another (your TURN
server).

Am I misunderstanding how symmetric RTP works?  Perhaps this is too =
minor a
point to discuss here, however.

-david

> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com]
> Sent: Tuesday, February 13, 2007 12:44 PM
> To: 'Magnus Westerlund'
> Cc: behave@ietf.org; 'IETF AVT WG'
> Subject: RE: [BEHAVE] [Fwd: Last Call:draft-wing-behave-symmetric-
> rtprtcp(Common Local Transmit andReceive Ports (Symmetric RTP))
> toInformational RFC]
>=20
> Per Francois's suggestion, the following new text would be placed at =
the
> end
> of section 3 of draft-wing-behave-symmetric-rtprtcp:
>=20
>   "For these reasons it is RECOMMENDED that symmetric RTP and
>    symmetric RTCP always be used for bi-directional RTP media
>    streams."
>=20
> -d
>=20
> > -----Original Message-----
> > From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> > Sent: Tuesday, February 13, 2007 12:17 PM
> > To: Magnus Westerlund
> > Cc: behave@ietf.org; IETF AVT WG
> > Subject: Re: [BEHAVE] [Fwd: Last Call:
> > draft-wing-behave-symmetric-rtprtcp(Common Local Transmit and
> > Receive Ports (Symmetric RTP)) toInformational RFC]
> >
> > There has been raised a comment that this document should contain a
> > normative recommendation on using symmetric ports. However to
> > make this
> > happen the document would need to be a BCP. I am willing to consider
> > this but would like to have AVT and Behave WG participant's view on
> > doing this before progressing down that road and updating the
> > IETF last
> > call. So please provide comments by Tuesday 20th of Feb on this =
issue.
> >
> > Best Regards
> >
> > Magnus
> >
> > Magnus Westerlund skrev:
> > > Hi,
> > >
> > > This document has been raised before in both AVT and BEHAVE
> > WG. I have
> > > chosen to AD sponsor this document for publication as =
informational
> > > status because it seems to be of general interest. You have
> > 4 weeks to
> > > provide any comments on the document.
> > >
> > > Magnus Westerlund
> > >
> > > IETF Transport Area Director & TSVWG Chair
> > >
> > =
----------------------------------------------------------------------
> > > Multimedia Technologies, Ericsson Research EAB/TVA/A
> > >
> > =
----------------------------------------------------------------------
> > > Ericsson AB                | Phone +46 8 4048287
> > > Torshamsgatan 23           | Fax   +46 8 7575550
> > > S-164 80 Stockholm, Sweden | mailto: =
magnus.westerlund@ericsson.com
> > >
> > =
----------------------------------------------------------------------
> > >
> > >
> > --------------------------------------------------------------
> > ----------
> > >
> > > =C3=84mne:
> > > Last Call: draft-wing-behave-symmetric-rtprtcp (Common
> > Local Transmit
> > > and Receive Ports (Symmetric RTP)) to Informational RFC
> > > Fr=C3=A5n:
> > > The IESG <iesg-secretary@ietf.org>
> > > Datum:
> > > Mon, 12 Feb 2007 15:44:51 -0500
> > > Till:
> > > IETF-Announce <ietf-announce@ietf.org>
> > >
> > > Till:
> > > IETF-Announce <ietf-announce@ietf.org>
> > >
> > >
> > > The IESG has received a request from an individual
> > submitter to consider
> > > the following document:
> > >
> > > - 'Common Local Transmit and Receive Ports (Symmetric RTP) '
> > >    <draft-wing-behave-symmetric-rtprtcp-01.txt> as an
> > Informational RFC
> > >
> > > The IESG plans to make a decision in the next few weeks,
> > and solicits
> > > final comments on this action.  Please send substantive
> > comments to the
> > > ietf@ietf.org mailing lists by 2007-03-12. Exceptionally,
> > > comments may be sent to iesg@ietf.org instead. In either
> > case, please
> > > retain the beginning of the Subject line to allow automated =
sorting.
> > >
> > > The file can be obtained via
> > >
> > http://www.ietf.org/internet-drafts/draft-wing-behave-symmetri
> > c-rtprtcp-01.txt
> > >
> > >
> > > IESG discussion can be tracked via
> > >
> > https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dvie
> > w_id&dTag=3D13165&rfc_flag=3D0
> > >
> > >
> > > _______________________________________________
> > > IETF-Announce mailing list
> > > IETF-Announce@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/ietf-announce
> > >
> > >
> > >
> > >
> > --------------------------------------------------------------
> > ----------
> > >
> > > _______________________________________________
> > > Behave mailing list
> > > Behave@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/behave
> >
> >
> > --
> >
> > Magnus Westerlund
> >
> > IETF Transport Area Director & TSVWG Chair
> > =
----------------------------------------------------------------------
> > Multimedia Technologies, Ericsson Research EAB/TVA/A
> > =
----------------------------------------------------------------------
> > Ericsson AB                | Phone +46 8 4048287
> > Torshamsgatan 23           | Fax   +46 8 7575550
> > S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> > =
----------------------------------------------------------------------
> >
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www1.ietf.org/mailman/listinfo/behave
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www1.ietf.org/mailman/listinfo/behave


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www1.ietf.org/mailman/listinfo/behave

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





From avt-bounces@ietf.org Tue Feb 13 17:37:56 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH6Go-0005t4-Qa; Tue, 13 Feb 2007 17:37:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH6Gm-0005oh-Ca; Tue, 13 Feb 2007 17:37:04 -0500
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HH6Gk-0007x7-Q7; Tue, 13 Feb 2007 17:37:04 -0500
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:63347
	helo=[192.168.0.3])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HH6Gj-0003c1-MR; Tue, 13 Feb 2007 22:37:02 +0000
In-Reply-To: <083301c74faf$b570fb20$c2f0200a@amer.cisco.com>
References: <083301c74faf$b570fb20$c2f0200a@amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <5937EACD-F25C-442E-B407-5564D7955AF0@csperkins.org>
Content-Transfer-Encoding: quoted-printable
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] RE: [BEHAVE] [Fwd: Last Call:
	draft-wing-behave-symmetric-rtprtcp(Common Local Transmit and
	Receive Ports (Symmetric RTP)) toInformational RFC]
Date: Tue, 13 Feb 2007 22:37:09 +0000
To: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0e9ebc0cbd700a87c0637ad0e2c91610
Cc: behave@ietf.org, IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Magnus, Dan,

The draft is good, and adding this text will improve it. Go ahead any =20=

publish it...

Colin




On 13 Feb 2007, at 20:44, Dan Wing wrote:
> Per Francois's suggestion, the following new text would be placed =20
> at the end
> of section 3 of draft-wing-behave-symmetric-rtprtcp:
>
>   "For these reasons it is RECOMMENDED that symmetric RTP and
>    symmetric RTCP always be used for bi-directional RTP media
>    streams."
>
> -d
>
>> -----Original Message-----
>> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
>> Sent: Tuesday, February 13, 2007 12:17 PM
>> To: Magnus Westerlund
>> Cc: behave@ietf.org; IETF AVT WG
>> Subject: Re: [BEHAVE] [Fwd: Last Call:
>> draft-wing-behave-symmetric-rtprtcp(Common Local Transmit and
>> Receive Ports (Symmetric RTP)) toInformational RFC]
>>
>> There has been raised a comment that this document should contain a
>> normative recommendation on using symmetric ports. However to
>> make this
>> happen the document would need to be a BCP. I am willing to consider
>> this but would like to have AVT and Behave WG participant's view on
>> doing this before progressing down that road and updating the
>> IETF last
>> call. So please provide comments by Tuesday 20th of Feb on this =20
>> issue.
>>
>> Best Regards
>>
>> Magnus
>>
>> Magnus Westerlund skrev:
>>> Hi,
>>>
>>> This document has been raised before in both AVT and BEHAVE
>> WG. I have
>>> chosen to AD sponsor this document for publication as informational
>>> status because it seems to be of general interest. You have
>> 4 weeks to
>>> provide any comments on the document.
>>>
>>> Magnus Westerlund
>>>
>>> IETF Transport Area Director & TSVWG Chair
>>>
>> ---------------------------------------------------------------------=20=

>> -
>>> Multimedia Technologies, Ericsson Research EAB/TVA/A
>>>
>> ---------------------------------------------------------------------=20=

>> -
>>> Ericsson AB                | Phone +46 8 4048287
>>> Torshamsgatan 23           | Fax   +46 8 7575550
>>> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>>>
>> ---------------------------------------------------------------------=20=

>> -
>>>
>>>
>> --------------------------------------------------------------
>> ----------
>>>
>>> =C4mne:
>>> Last Call: draft-wing-behave-symmetric-rtprtcp (Common
>> Local Transmit
>>> and Receive Ports (Symmetric RTP)) to Informational RFC
>>> Fr=E5n:
>>> The IESG <iesg-secretary@ietf.org>
>>> Datum:
>>> Mon, 12 Feb 2007 15:44:51 -0500
>>> Till:
>>> IETF-Announce <ietf-announce@ietf.org>
>>>
>>> Till:
>>> IETF-Announce <ietf-announce@ietf.org>
>>>
>>>
>>> The IESG has received a request from an individual
>> submitter to consider
>>> the following document:
>>>
>>> - 'Common Local Transmit and Receive Ports (Symmetric RTP) '
>>>    <draft-wing-behave-symmetric-rtprtcp-01.txt> as an
>> Informational RFC
>>>
>>> The IESG plans to make a decision in the next few weeks,
>> and solicits
>>> final comments on this action.  Please send substantive
>> comments to the
>>> ietf@ietf.org mailing lists by 2007-03-12. Exceptionally,
>>> comments may be sent to iesg@ietf.org instead. In either
>> case, please
>>> retain the beginning of the Subject line to allow automated sorting.
>>>
>>> The file can be obtained via
>>>
>> http://www.ietf.org/internet-drafts/draft-wing-behave-symmetri
>> c-rtprtcp-01.txt
>>>
>>>
>>> IESG discussion can be tracked via
>>>
>> https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dvie
>> w_id&dTag=3D13165&rfc_flag=3D0
>>>
>>>
>>> _______________________________________________
>>> IETF-Announce mailing list
>>> IETF-Announce@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/ietf-announce
>>>
>>>
>>>
>>>
>> --------------------------------------------------------------
>> ----------
>>>
>>> _______________________________________________
>>> Behave mailing list
>>> Behave@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/behave
>>
>>
>> --=20
>>
>> Magnus Westerlund
>>
>> IETF Transport Area Director & TSVWG Chair
>> ---------------------------------------------------------------------=20=

>> -
>> Multimedia Technologies, Ericsson Research EAB/TVA/A
>> ---------------------------------------------------------------------=20=

>> -
>> Ericsson AB                | Phone +46 8 4048287
>> Torshamsgatan 23           | Fax   +46 8 7575550
>> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>> ---------------------------------------------------------------------=20=

>> -
>>
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www1.ietf.org/mailman/listinfo/behave
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt



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



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



From avt-bounces@ietf.org Wed Feb 14 03:18:17 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHFJz-00029T-LT; Wed, 14 Feb 2007 03:16:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HHFJx-00029I-MQ
	for avt@ietf.org; Wed, 14 Feb 2007 03:16:57 -0500
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HHFJw-00048m-C4
	for avt@ietf.org; Wed, 14 Feb 2007 03:16:57 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 14 Feb 2007 10:16:50 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C044ED6E1@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AVT WG meeting in Prague
Thread-Index: AcbyuHqIrG/a6QMiRE+AaN3CgJ2CbA==
From: "Even, Roni" <roni.even@polycom.co.il>
To: "IETF AVT WG" <avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: "Even, Roni" <roni.even@polycom.co.il>, Colin Perkins <csp@csperkins.org>,
	Tom-PT Taylor <taylor@nortel.com>
Subject: [AVT] AVT WG meeting in Prague
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi,

If you wish to have agenda time at the upcoming meeting in Prague, =
please send an agenda request to the chairs, but no later than March =
1st.

We have requested two time slots:
1. Monday March 19th 15:20-17:20
2. Wednesday March 21st 15.10-16.10=20

Please note that those times are not final and may change. The final =
agenda for the meeting will; be published on February 26th.



This meeting time is intended for the following:

- Discussion of important drafts fundamental for the complete RTP =
framework.
- Discussion of issues that hasn't been possible to resolve on the =
mailing list.
- Discussion of new work that falls outside of our current charter.
- Discussion of important AVT relevant work in other WGs

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

A. Presentation Title:

B. Name of presenter:

C. Draft Reference(s):

D. Requested amount of time in minutes:




Thanks
Roni Even

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



From avt-bounces@ietf.org Wed Feb 14 06:40:53 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHITp-0006vJ-Q9; Wed, 14 Feb 2007 06:39:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HHITo-0006uZ-Oh
	for avt@ietf.org; Wed, 14 Feb 2007 06:39:20 -0500
Received: from prix.tandberg.no ([194.196.35.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HHITn-0007nK-8g
	for avt@ietf.org; Wed, 14 Feb 2007 06:39:20 -0500
Received: from 47mail.eu.tandberg.int (47mail.eu.tandberg.int [10.0.0.25])
	by prix.tandberg.no (8.12.11.20060308/8.12.10) with ESMTP id
	l1EBdE2M024640 for <avt@ietf.org>; Wed, 14 Feb 2007 12:39:18 +0100
Received: from 10.0.6.165 ([10.0.6.165]) by 47mail.eu.tandberg.int
	([10.0.0.25]) with Microsoft Exchange Server HTTP-DAV ; 
	Wed, 14 Feb 2007 11:39:16 +0000
Received: from TKristensenLpt by 47MAIL; 14 Feb 2007 12:39:16 +0100
From: Tom Kristensen <tom.kristensen@tandberg.net>
To: avt@ietf.org
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Organization: TANDBERG
Date: Wed, 14 Feb 2007 12:39:16 +0100
Message-Id: <1171453156.4018.15.camel@TKristensenLpt>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1 (2.4.2.1-1.1.fc4.nr) 
X-Scanned-By: MIMEDefang 2.45
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Subject: [AVT] draft-kristensen-avt-rtp-h264-extension-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org


I'd like to draw your attention to a new Internet Draft:
http://www.ietf.org/internet-drafts/draft-kristensen-avt-rtp-h264-extension-00.txt

----------------------
Abstract
  This document proposes extensions to the RTP payload format
  specification for H.264 video defined in RFC 3984.  

  It addresses two separate issues: 
   (i)  The signalling of the framerate of static macroblocks a 
        decoder is able to process in order to sustain high 
        framerates with high resolutions. 
   (ii) The signalling of a reduced-complexity decoding operation 
        (RCDO) for H.264 Baseline profile bitstreams.
----------------------

Feedback and comments on both technical content/concept and 
the style/shape of the document itself are much appreciated. 

-- Tom

-- 
Tom Kristensen, Senior Software Developer - TANDBERG asa, R&D
+47 6711 2922 / +47 9516 1107 (mob) / http://www.tandberg.net


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



From avt-bounces@ietf.org Wed Feb 14 15:51:38 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHR4n-0006H0-Al; Wed, 14 Feb 2007 15:50:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHR4k-0006Ee-LN; Wed, 14 Feb 2007 15:50:02 -0500
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HHR4k-0000lH-DB; Wed, 14 Feb 2007 15:50:02 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 5AE663292D;
	Wed, 14 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HHR4k-0004KB-7t; Wed, 14 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HHR4k-0004KB-7t@stiedprstage1.ietf.org>
Date: Wed, 14 Feb 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-smpte-rtp-08.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: Associating Time-codes with RTP streams
	Author(s)	: D. Singer
	Filename	: draft-ietf-avt-smpte-rtp-08.txt
	Pages		: 21
	Date		: 2007-2-14
	
This document describes a mechanism for associating time-codes, as
   defined by the Society of Motion Picture and Television Engineers
   (SMPTE), with media streams, in a way that is independent of the RTP
   payload format of the media stream itself.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-avt-smpte-rtp-08.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-avt-smpte-rtp-08.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-smpte-rtp-08.txt

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

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


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org Wed Feb 14 15:51:45 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHR4t-0006IM-Oj; Wed, 14 Feb 2007 15:50:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHR4l-0006F1-3Y; Wed, 14 Feb 2007 15:50:03 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HHR4k-0000lO-OW; Wed, 14 Feb 2007 15:50:03 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 87A2426F14;
	Wed, 14 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HHR4k-0004KE-8V; Wed, 14 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HHR4k-0004KE-8V@stiedprstage1.ietf.org>
Date: Wed, 14 Feb 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-hdrext-09.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: A general mechanism for RTP Header Extensions
	Author(s)	: H. Desineni, D. Singer
	Filename	: draft-ietf-avt-rtp-hdrext-09.txt
	Pages		: 21
	Date		: 2007-2-14
	
This document provides a general mechanism to use the header-
   extension feature of RTP (the Real Time Transport Protocol).  It
   provides the option to use a small number of small extensions in each
   RTP packet, where the universe of possible extensions is large and
   unregistered.  The actual extensions in use in a session are signaled
   in the setup information for that session.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-avt-rtp-hdrext-09.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-avt-rtp-hdrext-09.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-hdrext-09.txt

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

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


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org Wed Feb 14 15:53:21 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHR7K-0008VR-HN; Wed, 14 Feb 2007 15:52:42 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHR5j-00077Z-Vr; Wed, 14 Feb 2007 15:51:04 -0500
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HHR5j-0008PL-H7; Wed, 14 Feb 2007 15:51:03 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id EB1201761E;
	Wed, 14 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HHR4k-0004KH-98; Wed, 14 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HHR4k-0004KH-98@stiedprstage1.ietf.org>
Date: Wed, 14 Feb 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-toffset-05.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: Transmission Time offsets in RTP streams
	Author(s)	: H. Desineni, D. Singer
	Filename	: draft-ietf-avt-rtp-toffset-05.txt
	Pages		: 16
	Date		: 2007-2-14
	
This document describes a method to inform RTP clients when RTP
   packets are transmitted at a time other than their 'nominal'
   transmission time.  It also provides a mechanism to provide improved
   inter-arrival jitter reports from the clients, that take into account
   the reported transmission times.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-avt-rtp-toffset-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-avt-rtp-toffset-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-toffset-05.txt

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

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


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org Wed Feb 14 17:42:58 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHSp8-0002Fi-7H; Wed, 14 Feb 2007 17:42:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HHSp6-0002DT-Dk
	for avt@ietf.org; Wed, 14 Feb 2007 17:42:00 -0500
Received: from gateway0.eecs.berkeley.edu ([169.229.60.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HHSp5-0007DN-0o
	for avt@ietf.org; Wed, 14 Feb 2007 17:42:00 -0500
Received: from [128.32.34.73] (dhcp-34-73.CS.Berkeley.EDU [128.32.34.73])
	(authenticated bits=0)
	by gateway0.EECS.Berkeley.EDU (8.14.0/8.13.5) with ESMTP id
	l1EMflkB012842
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Wed, 14 Feb 2007 14:41:49 -0800 (PST)
In-Reply-To: <45D3155E.4040301@nortel.com>
References: <45D3155E.4040301@nortel.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <DD273948-EA2F-48EE-8B12-E8EE4C609859@eecs.berkeley.edu>
Content-Transfer-Encoding: 7bit
From: lazzaro <lazzaro@eecs.berkeley.edu>
Date: Wed, 14 Feb 2007 14:41:46 -0800
To: avt@ietf.org
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	lazzaro <lazzaro@eecs.berkeley.edu>, Roni Even <roni.even@polycom.co.il>,
	Joerg Ott <jo@netlab.tkk.fi>, ingemar.s.johansson@ericsson.com,
	Tom-PT Taylor <taylor@nortel.com>, Colin Perkins <csp@csperkins.org>
Subject: [AVT] Review of draft-johansson-avt-rtcp-avpf-non-compound-00.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi everyone,

	One of our co-chairs asked me to evaluate
draft-johansson-avt-rtcp-avpf-non-compound-00.txt
for WG item status.  This is my review.

	This I-D wishes to legitimize sending RTCP
AVPF packets that are not compound-packets --
these RTCP packets would not begin with an SR/RR
and would not include SDES w/ a CNAME.  At the
moment RTCP packets of this nature are forbidden
by RFC 3550.  Cellular push-to-talk, a fielded service,
breaks this RFC 3550 already (OMA-PoC as mentioned
in the I-D).

	This goals of the I-D seem reasonable to me,
so I'm in favor of making it a WG item.  Some
other comments follow:

o   The current I-D is limited in scope to AVPF.  If
we have reason to believe that users of the other
profiles will also want to legitimize non-compound RTCP
at some later date, I believe we should expand the scope
of this I-D to all profiles, in anticipation.  That sort of
anticipation is one way we can keep AVT's workload
manageable.

o  I'm under the impression that many fielded applications
multiplex RTP and RTCP on the same port; Colin has an
I-D in progress trying to legitimize that practice.  It
doesn't take much imagination to see how non-compound
RTCP packets would break fielded code that does the
demultiplex by looking for magic numbers in the PT field.

o  If we can either (1) write this I-D to conform to the
rules OMA-PoC uses for sending RTCP, or (2) get
buy-in from the OMA-PoC folks to issue a revision
that matches this I-D, it would be best.  Otherwise,
we are "closing the barn door after the horse has
run away".

o  The I-D needs an English grammar rewrite -- key
problems are singular/plural noun/verb matching,
a/an problems, to/too problems ... while normally
"just let the RFC editor handle it" is OK, I think there
are so many errors that a grammar pass should be
done sooner, so that we can concentrate on the
content.

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



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



From avt-bounces@ietf.org Wed Feb 14 20:03:11 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHV0e-0000AU-Ta; Wed, 14 Feb 2007 20:02:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HHV0e-0008V5-2P
	for avt@ietf.org; Wed, 14 Feb 2007 20:02:04 -0500
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HHV0b-0003y3-Rw for avt@ietf.org; Wed, 14 Feb 2007 20:02:04 -0500
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 14 Feb 2007 20:02:01 -0500
To: lazzaro <lazzaro@eecs.berkeley.edu>
Subject: Re: [AVT] Review of draft-johansson-avt-rtcp-avpf-non-compound-00.txt
References: <45D3155E.4040301@nortel.com>
	<DD273948-EA2F-48EE-8B12-E8EE4C609859@eecs.berkeley.edu>
From: Randell Jesup <rjesup@wgate.com>
Date: Wed, 14 Feb 2007 20:01:59 -0500
In-Reply-To: <DD273948-EA2F-48EE-8B12-E8EE4C609859@eecs.berkeley.edu>
	(lazzaro@eecs.berkeley.edu's
	message of "Wed, 14 Feb 2007 14:41:46 -0800")
Message-ID: <ybud54cmdx4.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 15 Feb 2007 01:02:01.0806 (UTC)
	FILETIME=[E6A546E0:01C7509C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Roni Even <roni.even@polycom.co.il>, avt@ietf.org,
	Joerg Ott <jo@netlab.tkk.fi>, ingemar.s.johansson@ericsson.com,
	Tom-PT Taylor <taylor@nortel.com>, Colin Perkins <csp@csperkins.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Overall sounds good.

lazzaro <lazzaro@eecs.berkeley.edu> writes:
>o  I'm under the impression that many fielded applications
>multiplex RTP and RTCP on the same port; Colin has an
>I-D in progress trying to legitimize that practice.  It
>doesn't take much imagination to see how non-compound
>RTCP packets would break fielded code that does the
>demultiplex by looking for magic numbers in the PT field.

Are there such fielded applications?  Anyone know of any?  List? I haven't
seen or heard of any, but I'm not a good judge.  If there are, do they
signal this?  How?  (Note: a=rtcp with the same port number can cause
problems with SBCs that don't understand it; see Colins draft.)

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


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



From avt-bounces@ietf.org Wed Feb 14 20:40:01 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHVad-0006ph-8O; Wed, 14 Feb 2007 20:39:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HHVac-0006pY-Mt
	for avt@ietf.org; Wed, 14 Feb 2007 20:39:14 -0500
Received: from gateway0.eecs.berkeley.edu ([169.229.60.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HHVab-00039o-BJ
	for avt@ietf.org; Wed, 14 Feb 2007 20:39:14 -0500
Received: from [128.32.34.73] (dhcp-34-73.CS.Berkeley.EDU [128.32.34.73])
	(authenticated bits=0)
	by gateway0.EECS.Berkeley.EDU (8.14.0/8.13.5) with ESMTP id
	l1F1d50e016217
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Wed, 14 Feb 2007 17:39:06 -0800 (PST)
In-Reply-To: <ybud54cmdx4.fsf@jesup.eng.wgate.com>
References: <45D3155E.4040301@nortel.com>
	<DD273948-EA2F-48EE-8B12-E8EE4C609859@eecs.berkeley.edu>
	<ybud54cmdx4.fsf@jesup.eng.wgate.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F3643590-0A61-4DAE-BD70-330AD0046DC0@eecs.berkeley.edu>
Content-Transfer-Encoding: 7bit
From: lazzaro <lazzaro@eecs.berkeley.edu>
Subject: Re: [AVT] Review of draft-johansson-avt-rtcp-avpf-non-compound-00.txt
Date: Wed, 14 Feb 2007 17:39:03 -0800
To: Randell Jesup <rjesup@wgate.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	lazzaro <lazzaro@eecs.berkeley.edu>,
	Roni Even <roni.even@polycom.co.il>, avt@ietf.org,
	Joerg Ott <jo@netlab.tkk.fi>, ingemar.s.johansson@ericsson.com,
	Tom-PT Taylor <taylor@nortel.com>, Colin Perkins <csp@csperkins.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On Feb 14, 2007, at 5:01 PM, Randell Jesup wrote:
>
> lazzaro <lazzaro@eecs.berkeley.edu> writes:
>> o  I'm under the impression that many fielded applications
>> multiplex RTP and RTCP on the same port; Colin has an
>> I-D in progress trying to legitimize that practice.  It
>> doesn't take much imagination to see how non-compound
>> RTCP packets would break fielded code that does the
>> demultiplex by looking for magic numbers in the PT field.
>
> Are there such fielded applications?  Anyone know of any?  List? I  
> haven't
> seen or heard of any, but I'm not a good judge.  If there are, do they
> signal this?  How?  (Note: a=rtcp with the same port number can cause
> problems with SBCs that don't understand it; see Colins draft.)



My level of certainty is summed up by my choice of
"I'm under the impression" in the quoted sentence :-).
Hopefully someone reading the list can chime in with
real information ...

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



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



From avt-bounces@ietf.org Thu Feb 15 05:15:27 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHdcx-0004Zq-Av; Thu, 15 Feb 2007 05:14:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HHdcw-0004Zk-P6
	for avt@ietf.org; Thu, 15 Feb 2007 05:14:10 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HHdcq-0000vF-4A
	for avt@ietf.org; Thu, 15 Feb 2007 05:14:10 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	290D1211C1; Thu, 15 Feb 2007 11:12:56 +0100 (CET)
X-AuditID: c1b4fb3e-b0ed5bb0000007e1-22-45d4322876ca 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	0D9DA210B5; Thu, 15 Feb 2007 11:12:56 +0100 (CET)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 15 Feb 2007 11:12:55 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 15 Feb 2007 11:12:54 +0100
Message-ID: <026F8EEDAD2C4342A993203088C1FC05046D24C9@esealmw109.eemea.ericsson.se>
In-Reply-To: <DD273948-EA2F-48EE-8B12-E8EE4C609859@eecs.berkeley.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Review of draft-johansson-avt-rtcp-avpf-non-compound-00.txt
Thread-Index: AcdQiVTtGpFpYd96RJGfKkqq6vkYmQAXVwHg
From: "Ingemar Johansson S \(LU/EAB\)" <ingemar.s.johansson@ericsson.com>
To: "lazzaro" <lazzaro@eecs.berkeley.edu>,
	<avt@ietf.org>
X-OriginalArrivalTime: 15 Feb 2007 10:12:55.0900 (UTC)
	FILETIME=[DC6BC1C0:01C750E9]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: "Magnus Westerlund \(KI/EAB\)" <magnus.westerlund@ericsson.com>,
	Roni Even <roni.even@polycom.co.il>,
	Colin Perkins <csp@csperkins.org>, Joerg Ott <jo@netlab.tkk.fi>,
	Tom-PT Taylor <taylor@nortel.com>
Subject: [AVT] RE: Review of
	draft-johansson-avt-rtcp-avpf-non-compound-00.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi

Thanks for the comments, my comments inline with text below

> -----Original Message-----
> From: lazzaro [mailto:lazzaro@eecs.berkeley.edu]=20
> Sent: den 14 februari 2007 23:42
> To: avt@ietf.org
> Cc: lazzaro; Joerg Ott; Colin Perkins; Roni Even; Tom-PT=20
> Taylor; Ingemar Johansson S (LU/EAB); Magnus Westerlund (KI/EAB)
> Subject: Review of draft-johansson-avt-rtcp-avpf-non-compound-00.txt
>=20
> Hi everyone,
>=20
> 	One of our co-chairs asked me to evaluate=20
> draft-johansson-avt-rtcp-avpf-non-compound-00.txt
> for WG item status.  This is my review.
>=20
> 	This I-D wishes to legitimize sending RTCP AVPF packets=20
> that are not compound-packets -- these RTCP packets would not=20
> begin with an SR/RR and would not include SDES w/ a CNAME. =20
> At the moment RTCP packets of this nature are forbidden by=20
> RFC 3550.  Cellular push-to-talk, a fielded service, breaks=20
> this RFC 3550 already (OMA-PoC as mentioned in the I-D).
>=20
> 	This goals of the I-D seem reasonable to me, so I'm in=20
> favor of making it a WG item.  Some other comments follow:
>=20
> o   The current I-D is limited in scope to AVPF.  If
> we have reason to believe that users of the other profiles=20
> will also want to legitimize non-compound RTCP at some later=20
> date, I believe we should expand the scope of this I-D to all=20
> profiles, in anticipation.  That sort of anticipation is one=20
> way we can keep AVT's workload manageable.
I have no particular comment to this except that it is some sense tied
to the=20
immediate and early modes in AVPF as the non-compound RTCP feature is
(by me) primarily expected to be used with adaptation feedback.

> o  I'm under the impression that many fielded applications=20
> multiplex RTP and RTCP on the same port; Colin has an I-D in=20
> progress trying to legitimize that practice.  It doesn't take=20
> much imagination to see how non-compound RTCP packets would=20
> break fielded code that does the demultiplex by looking for=20
> magic numbers in the PT field.
Could be true, one could however argue that the text in section 4 of=20
http://tools.ietf.org/id/draft-ietf-avt-rtp-and-rtcp-mux-03.txt
should make this a lesser problem as.
=20
> o  If we can either (1) write this I-D to conform to the=20
> rules OMA-PoC uses for sending RTCP, or (2) get buy-in from=20
> the OMA-PoC folks to issue a revision that matches this I-D,=20
> it would be best.  Otherwise, we are "closing the barn door=20
> after the horse has run away".
The writing in the OMA-PoC spec is quite simple. Below is a snippet from
section 6.5
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
The Talk Burst Control Protocol (TBCP) is based on the RTCP Application
Packets (RTCP: APP), as defined in [RFC3550], but TBCP messages do not
conform to the rules for compound RTCP packets or RTCP packet
transmission. Each TBCP message SHALL be one RTCP: APP packet. These
RTCP: APP packets SHALL not be sent in compound RTCP packets, but more
than one TBCP Talk Burst Control message MAY be sent in a single IP
packet. The structure of each TBCP message is defined below.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

> o  The I-D needs an English grammar rewrite -- key problems=20
> are singular/plural noun/verb matching, a/an problems, to/too=20
> problems ... while normally "just let the RFC editor handle=20
> it" is OK, I think there are so many errors that a grammar=20
> pass should be done sooner, so that we can concentrate on the content.
Sounds fair. I could possibly issue an updated (grammar corrected) draft
before march 5 but it would of course feel better to do more than a
grammar update.=20

Regards
Ingemar

=20

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



From avt-bounces@ietf.org Thu Feb 15 14:26:28 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHmDz-0000UK-P7; Thu, 15 Feb 2007 14:24:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HHmDy-0000U8-J0
	for avt@ietf.org; Thu, 15 Feb 2007 14:24:58 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HHmDu-0001IS-Q5
	for avt@ietf.org; Thu, 15 Feb 2007 14:24:58 -0500
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-5.cisco.com with ESMTP; 15 Feb 2007 11:24:55 -0800
X-IronPort-AV: i="4.14,177,1170662400"; 
	d="scan'208"; a="389513878:sNHT274430764"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l1FJOrgH016623; 
	Thu, 15 Feb 2007 11:24:53 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l1FJOjDm013820;
	Thu, 15 Feb 2007 11:24:45 -0800 (PST)
Received: from xmb-sjc-216.amer.cisco.com ([171.70.151.184]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 15 Feb 2007 11:24:41 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] Re: I-D ACTION:draft-xu-avt-subrtcp-00.txt 
Date: Thu, 15 Feb 2007 11:24:40 -0800
Message-ID: <FDA45A7874021C40897203FA3554940002F77B75@xmb-sjc-216.amer.cisco.com>
In-Reply-To: <90B66CE8-45E9-4897-8211-3076FDC19FA1@csperkins.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Re: I-D ACTION:draft-xu-avt-subrtcp-00.txt 
Thread-Index: AcdODreZaPV9FoBISl6zAcRpBk5KtADI0Mgg
From: "Xiaode Xu \(xdxu\)" <xdxu@cisco.com>
To: "Colin Perkins" <csp@csperkins.org>
X-OriginalArrivalTime: 15 Feb 2007 19:24:41.0137 (UTC)
	FILETIME=[F0AE0A10:01C75136]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=10876; t=1171567493;
	x=1172431493; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=xdxu@cisco.com;
	z=From:=20=22Xiaode=20Xu=20\(xdxu\)=22=20<xdxu@cisco.com>
	|Subject:=20RE=3A=20[AVT]=20Re=3A=20I-D=20ACTION=3Adraft-xu-avt-subrtcp-0
	0.txt=20 |Sender:=20;
	bh=X9czGmHHsk3LmWBwdFRIhASb83Hmj3NZOzwtD+XpSMw=;
	b=RCAIjmYKysBfYG5CDEEqw4gdC+9LDNwBx/zTPyoIPDGRFLPZZs195fBgNiqNPAlctRIRfFzX
	hYKCGcdSqvg2nBUKU5jxEqnquglq2NVu/q2hpDDkgSSR4p12Mh/4uEGM;
Authentication-Results: sj-dkim-3; header.From=xdxu@cisco.com; dkim=pass (si
	g from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 578c2c9d0cb01ffe6e1ca36540edd070
Cc: hd-yamada@kddilabs.jp, AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi Colin,

Unfortunately the world has too many owners. As a result, a service
provider
does not have visibility to a customer's network, and have no interest
in it,
either. A service provider network is more like a transport at VoIP
plane
with respect to media traffic.

On the other hand, a service provider network would be self-enclosed and
does not solicit any external probing.=20

Also parsing a packet on traffic path in particular deep looking into
its
body to digest certain information elements is not a good idea for the
transport function provided by a service provider network. In lab test,
you will see the performance drop resulted from implementation of the
idea.=20

But a service provider would not be blind certainly on how its transport
goes. It needs some good measurements within its domain for the purpose
of ensuring the SLA. SubRTCP is just one way of achieving this goal. We
are also drafting something more powerful from this perspective.

To have a middlebox continuously digest something unecessary is not
preferred and performance economic.=20

I understand the beauty of having the whole thing under on governor but
the fact is the world will have many presidents regardlessly.

Regarding the hop limit I mentioned in my last email, I did not mean=20
the TTL (IPv4) or Hop Limit (IPv6) fields in IP header. I do not know
what you meant in one of your comments. The hop limit on my mind is
for the RTP plane specifically.

Just share some general thoughts which might be better than digging to
details at this moment. But no matter what, the goal is to solve=20
issues facing owners of RTP transport networks. A RTP path can originate
from one enterprise through multiple service providers to another
enterprise.

Separation of SSRC spaces between internal (transport) and true
endpoints
can solve the problem better.

Thanks,
Xiaode


-----Original Message-----
From: Colin Perkins [mailto:csp@csperkins.org]=20
Sent: Sunday, February 11, 2007 10:59 AM
To: Xiaode Xu (xdxu)
Cc: hd-yamada@kddilabs.jp; AVT WG
Subject: Re: [AVT] Re: I-D ACTION:draft-xu-avt-subrtcp-00.txt=20

On 2 Feb 2007, at 18:39, Xiaode Xu ((xdxu)) wrote:
> Hi Colin, Thanks for your comments. Please see my points inlined.
> //Xiaode
>
> -----Original Message-----
> From: Colin Perkins [mailto:csp@csperkins.org]
> Sent: Friday, February 02, 2007 12:08 AM
> To: Xiaode Xu (xdxu)
> Cc: hd-yamada@kddilabs.jp; AVT WG
> Subject: Re: [AVT] Re: I-D ACTION:draft-xu-avt-subrtcp-00.txt
>
> On 2 Feb 2007, at 00:30, Xiaode Xu ((xdxu)) wrote:
>> I think I did not catch the points presented in the existing rfc docs

>> (3550 & 3611) correctly in my last email. Thanks for correcting me.
>>
>> But I feel the existing system bears the following issues:
>>
>> - For an 1-way RTP session:  E1-->T1-->T2-->E2, where E and T stands=20
>> for
>>   Endpoint and Translator.
>>
>>   According to 3550, E1 can send a sender info in SR to E2 which=20
>> returns
>>   LSR and DLSR to E1. E1 can thus estimate the RTT between E1 and E2.
>> But
>>   E2 does not have a view of the RTT.
>>
>>   With help of 3611, E2 is capable of estimating the RTT with E1 by
>>   exchanging "Receiver Reference Time Report Blocks and DLRR" via the

>> XRs.
>>
>>   In an one speaker only multicast or broadcast session, from the
>>   speaker to any receiver of the session will be an instance of the
>>   such an 1-way rtp session. Another example could be resulted
>>   from some voice mute feature.
>>
>> - According to 3550, a translater can not send sender info i.e. SR.
>> But
>>   assuming T1 can send a XR with time reference report blocks to T1=20
>> and
>>   receive DLRR from T2 in order to measure RTT between them. So does=20
>> T2.
>>   In this case, T1 and T2 needs to create their own SSRC and spread=20
>> to
>>   E1 and E2 for calculating rtp report interval.
>>
>>   In this case, T1 and T2 are totally confined to the infrastructure.
>> To
>>   have their SSRC in the same SSRC space as that for endpoints E1 and
>> E2
>>   may not be too forceful.
>
> Creating an SSRC is trivial, so I don't see it as a problem.
> [XU]: In order to have all the participants sync up their report=20
> interval,
>       every ssrc (as rtcp speaker) needs to be maintained by each=20
> participant,
>       even the effort is just to measure RTT between T1 and T2.
> Creating
>       an SSRC itself is not an issue but its management and sync=20
> across all
>       participants is not trivial.

So? All participants must implement this code anyway.

>> - How about a rtp sessiong riding over more than two Ts, this can=20
>> happen
>>   when a call crossing mulitple service providers' network domain.
>>   Meaturing the RTT between any two of the middle boxes based on the
>>   existing 3611 and 3550 protocols could be burdensome.
>
> This is no different for standard RTCP than for your proposal.
> [XU] This is a big difference between SubRTCP and regular RTCP. =20
> SubRTCP
>      carrying its own message type, a middle box can immediately=20
> forward
>      it further out and simultaneously digest it, if configured to do=20
> so.
>      This can ensure better accuracy of the RTT estimation. A SubRTCP=20
> SR
>      message is capable of soliciting response from all the middle=20
> boxes,
>      not just one.

I simply do not believe the complexity of looking at RTCP packet types
is significant compared to checking the subRTCP packet type.

> In order to limit how far a SubRTCP message can reach, a hop limit=20
> field may help.

IP has such a field, independent of RTCP or subRTCP.

>      Coming back to the regular RTCP, the intended middle box for its
>      messages is not clear or explicit. Either each middle box parses
>      a received RTCP message to look for the portion of interest to
>      digest or terminate it and create a new RTCP message as a mixer
>      does. If a middle box terminates a received RTCP and creates a
>      new RTCP, the true sender and receiver (listener) will lose the
>      true judgement of the RTP media quality. In principle, I prefer
>      regular RTCP maintains its native observation of its accompanying
>      RTP stream.
>
>      Please think about the advantage of separation of end2end rtcp
>      and internal rtcp for their respective monitoring purpose in=20
> comparision
>      with one rtcp lumping two things in one participant group. Yes,
>      we can treat all middle boxes as regular RTCP speaker, but the
>      cost and complexity and efficiency in implementation will differ.

I see the complexity as coming from introducing an additional protocol
where none is needed: subRTCP is more complex than regular RTCP.

>> - Also when an RTCP packet traverses through all the middle boxes, if
>>   each box needs to look into a compound RTCP packet for XR packet's
>>   reference time blocks to act, it will delay the passing-through of
>>   the RTCP packet and cause the inaccuracy of the RTT estimation in=20
>> the
>>   end.
>
> Those boxes have to examine every packet to tell if they are RTCP or=20
> subRTCP in your proposal. Checking the RTCP packet type values instead

> turns a single "if" statement in the code into a "for" loop containing

> an "if" statement. In almost all cases, that loop will iterate over=20
> two values (and SR/RR packet, followed by an SDES packet). This adds=20
> one extra comparison per packet, and will not cause significant delay.
> [XU] The reason being stated above: a middle box only needs to know if

> it's a subRTCP packet or regular RTCP packet. It
>      has its choice whether it needs to dig into a SubRTCP message.
> Regardlessly, it can forward the SubRTCP message
>      further up or down immediately. But for a regular RTCP message, a

> middle box needs to parse the message to know
>      what is being carried to process them accordingly. For example,=20
> the SDES needs to be made known all the others.
>      SubRTCP can get rid of this burden by simplifying uneccessary=20
> elements.

As I said previously, who cares? The "burden" of parsing RTCP is
negligible.

>      On the other hand, per-session observation of an RTP stream at a=20
> middle box is mostly for debugging purpose. But
>      even so, internal monitoring of a media path may be more=20
> important than the end2end monitoring from a service
>      provider's purspective.
>      With SubRTCP separation from the regular RTCP, another cent is=20
> SubRTCP can be turned off when not needed. It should
>      be turned off after the network is tuned well.

This is no different to regular RTCP.

>> Coming back to SubRTCP, it uses its own message type, middle boxes=20
>> can
>
>> act upon them right way. Also it is functioning on a different SSRC=20
>> space which can make the group of endpoints easier in performing=20
>> regular RTCP jobs.
>
> Why do you think this makes the endpoints job easier? The RTCP packets

> from the infrastructure nodes don't need to reach the end systems, and

> even if they do, I don't see that it will cause any additional=20
> complexity.
>
> [XU] With endpoints and middle boxes in the same SSRC space, they are=20
> equal RTCP speaker and should be make known to all
>      participants in order to get the dynamically synced report=20
> interval.

This has to be done for subRTCP too, if you wish to scale the reporting
interval. If no, simply send regular RTCP internal to the
infrastructure.

>> Even Translator can send RR and Mixer can do both SR and RR, they are

>> still not true endpoints.
>> In principle, the true meaningful sense of the RTCP will be more=20
>> obvious when it accompanys the its RTP session. In field, complaints=20
>> are usually from RTP endpoints, the true sender and receiver.
>
> I think you misunderstand the definition of RTP session. The=20
> association of RTP systems that includes the middleboxes and end point

> is a single RTP session, with associated RTCP. RTCP is explicitly=20
> intended to allow the type of monitoring you desire as part of its=20
> "true meaningful sense".
>
> [XU] I understood. Treat all RTP nodes involved in one RTP session=20
> including all endpoints and middle points in one SSRC
>      space is arguable to me. Think about the good aspect of partition

> endpoints and middle nodes into two SSRC-space
>      groups as we do to differ host nodes and transport nodes
> (router/switch) in networking.

What good aspect? It is *intentional* in the design of RTCP that
middleboxes use the same SSRC space, since it allows endpoints to
monitor the quality to those middleboxes.

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

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



From avt-bounces@ietf.org Fri Feb 16 02:43:08 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHxiv-000753-65; Fri, 16 Feb 2007 02:41:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHxit-00074r-Ug; Fri, 16 Feb 2007 02:41:39 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HHxis-0003OI-Fo; Fri, 16 Feb 2007 02:41:39 -0500
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l1G7faF2007255
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 15 Feb 2007 23:41:37 -0800
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com
	[172.30.32.65])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l1G7faIw028741; Thu, 15 Feb 2007 23:41:36 -0800
Received: from NAEX01.qualcomm.com ([129.46.51.60]) by
	SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 15 Feb 2007 23:41:36 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 15 Feb 2007 23:41:36 -0800
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B028B0ACC@NAEX01.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Draft on SDP BW attribute for media bitrate in 'send' direction
	( draft-hdesinen-mmusic-oa-send-bw-attr-00.txt )
Thread-Index: AcdRneNSWBGfPE2eQB2K8M4MrfgUlw==
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: <avt@ietf.org>, <mmusic@ietf.org>
X-OriginalArrivalTime: 16 Feb 2007 07:41:36.0100 (UTC)
	FILETIME=[E2D9FA40:01C7519D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: 
Subject: [AVT] Draft on SDP BW attribute for media bitrate in 'send'
	direction ( draft-hdesinen-mmusic-oa-send-bw-attr-00.txt )
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

AVT & MMUSIC,

Here is a draft which defines a new bandwidth attribute for SDP
Offer/Answer model.

=3D=3D=3D=3D=3D=3D=3D
Abstract:
"This document defines a new SDP bandwidth attribute that can be used to
signal the maximum media bitrate in 'send' direction of a stream in SDP
offer/answer model."
=3D=3D=3D=3D=3D=3D=3D=3D=3D

-01 version of the draft is not yet available on IETF server. Until then
it can be viewed at
http://people.qualcomm.com/hdesinen/draft-hdesinen-mmusic-oa-send-bw-att
r-01.txt

-00 is available on IETF server at
http://www.ietf.org/internet-drafts/draft-hdesinen-mmusic-oa-send-bw-att
r-00.txt

Please review the latest version (-01) of the draft and post your
comments.

Thanks,
Hari

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



From avt-bounces@ietf.org Fri Feb 16 12:35:49 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HI6yg-00053v-8g; Fri, 16 Feb 2007 12:34:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HI6ye-00053p-Uf
	for avt@ietf.org; Fri, 16 Feb 2007 12:34:32 -0500
Received: from maile.telecomitalia.it ([156.54.233.31])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HI6yY-0006OS-Tl
	for avt@ietf.org; Fri, 16 Feb 2007 12:34:32 -0500
Received: from ptpxch007ba020.idc.cww.telecomitalia.it ([156.54.240.50]) by
	maile.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830);
	Fri, 16 Feb 2007 18:34:25 +0100
Received: from PTPEVS108BA020.idc.cww.telecomitalia.it ([156.54.241.227]) by
	ptpxch007ba020.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 16 Feb 2007 18:34:24 +0100
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Importance: normal
Priority: normal
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] CCM draft review --
	should"bandwidth"includetheheaderoverhead
Date: Fri, 16 Feb 2007 18:34:24 +0100
Message-ID: <E9D1028EC5C22B418B5D54CA6EA27C579A5E76@PTPEVS108BA020.idc.cww.telecomitalia.it>
In-Reply-To: <2CA3E1B6CEC064449CAA7D0FAB46079B028B0731@NAEX01.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] CCM draft review --
	should"bandwidth"includetheheaderoverhead
thread-index: AcdPata3K58y9RVnTlu9EMo/M26teQAKeE3gAATWBiAAT4g+4A==
From: "Franceschini Guido" <guido.franceschini@telecomitalia.it>
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>,
	"Randell Jesup" <rjesup@wgate.com>, "Even, Roni" <roni.even@polycom.co.il>
X-OriginalArrivalTime: 16 Feb 2007 17:34:24.0689 (UTC)
	FILETIME=[B361F210:01C751F0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f884eb1d4ec5a230688d7edc526ea665
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

I think that the semantic we are looking for is best represented by =
Randell's mail, i.e. a transport/link status/bitrate change. Hari is =
thus right in stating that this is not exactly a Codec Control Message.

But apart from the nomenclature, I have seen so far discussion looping =
around a couple of concepts:
- at what level should we measure the bandwidth?
- do we have to indicate something in addition to the bandwidth (packet =
rate, average overhead)?

None of the existing bandwidth metrics (CT, AS, TIAS) fits well with the =
problem of describing how to saturate (or avoid congesting) the path =
capacity.
IMHO this problem, raised in the context of TMMBR, i.e. in the context =
of providing updates, applies equally well in the SETUP phase. Again, =
none of the existing tools has been designed to describe how to saturate =
(or avoid congesting) the path capacity.

I have just written a draft that addresses the above requirement =
(available at: =
http://www.ietf.org/internet-drafts/draft-franceschini-avt-bwmetrics-00.t=
xt), and I already mentioned in a past mail the essential conclusion of =
my analysis, i.e.:
- signaling from RX to TX a tuple made of
-- a bandwidth parameter (TIDC), that represents the bandwidth available =
in the downlink at a certain protocol stack layer X;
-- an overhead parameter (MPO), that measures the average overhead of a =
packet in the downlink at that same layer X.

In the draft I show that the maximum accuracy in the downlink =
characterization is obtained when the layer X is selected as the point =
where the packet oriented protocol stack portion (e.g. RTP, UDP, IP, =
PPP, ETH...) interfaces the byte-oriented protocol stack portion (e.g. =
LAPM or various other link layers).
For such a choice, the packet rate is irrilevant.
If instead a different 'layer X' is considered, the packet rate impacts =
on the accuracy of characterization.=20

In the discussion seen on this thread, the two major candidates =
considered as layer X have been IP and Application (codec bitrate). The =
model I propose could accomodate both, but as I said, the packetrate =
shall also be known to provide an accurate characterization when we =
select a reference layer other than the ideal one.

I think the packetrate is not a precise parameter, and in general cannot =
be known by the receiver -just approximatively guessed-, and anyway, if =
the receiver assumes a specific packetrate, it should better signal this =
as well.

I am in favor of defining a mechanism that allows for accurate =
characterization of a link capacity, and to depart from the maximum =
accuracy not by design, but because of reasonable implementation =
impediments. Therefore, my proposal for a layer X at which to measure =
bandwidth and overhead, that does not necessarily corresponds to =
Application (codec bitrate) or IP layers, and that could avoid the =
uncertainty due to a badly guessed packetrate.

Also, I have read in this e-mail thread that it is not practical to =
determine whether ROHC is applied or not on the local link. Maybe this =
is true, today, but I disagree with what has been derived from this =
statement. The availability of this information to the application is =
indeed a terminal implementation issue: the terminal _has_ this info, =
it's just a matter for the application to gather this info from the O.S.
I would therefore disagree with the principle that we should not =
consider the presence of ROHC _by design_, simply because it is felt =
that today's devices do not expose this information to applications.
Of course, as far as presence of ROHC cannot be granted, a terminal =
should assume that no header compression is achieved. But if it knows =
more, why not exploiting this knowledge to more accurately characterize =
the link capacity?

Furthermore, an issue that has had no attention in this thread but that =
I feel relevant for this context, is that of cross-media relations. By =
this I mean:
- the jitter induced in the audio stream by the presence of big video =
packets on the same physical link (in case an entire packet is =
serialized without interleaving of audio data)
- the bandwidth eroded to the video stream by the packetization overhead =
of the audio stream

Apparently, no mechanism has been defined so far to allow a transmitter =
terminal to determine how to organize the audio and video traffic and =
partition the available bandwidth between the two. When the goal is to =
saturate a path capacity, these problems shall be addressed.
My draft describes a possible approach to this problem, with a detailed =
real-life example and figures.
The cons of my approach is that the bandwidth parameter (TIDC) in this =
context has session-level meaning, thus updates (through TMMBR or =
whatever RTCP feedback message) should convey session-level, and not =
just media-level parameters. This is certainly not a big hurdle from a =
syntax point of view, but maybe there are architectural CONS that I =
haven't seen.

Best regards
Guido Franceschini=20
Telecom Italia - Technology=20
Innovation & Engineering Services - Service Creation & Application=20
Multimedia Technology Innovation=20
Via G. Reiss Romoli, 274=20
10148 Torino - ITALY=20
Phone +39 011 2286137=20
Fax     +39 011 2287185=20
guido.franceschini@telecomitalia.it =
<mailto:guido.franceschini@telecomitalia.it> =20


> -----Original Message-----
> From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> Sent: marted=EC 13 febbraio 2007 21.22
> To: Desineni, Harikishan; Randell Jesup; Even, Roni
> Cc: Dave Singer; avt@ietf.org
> Subject: RE: [AVT] CCM draft review --
> should"bandwidth"includetheheaderoverhead
>=20
>=20
>=20
> Codec control message should be independent of transport. Roni's view
> makes it a true codec control message. (Re)Using it for signaling
> transport/link status/bandwidth changes will make it less obvious for
> codec control usage.
>=20
> A message that captures transport/link status/bitrate changes=20
> alone does
> not well qualify for being a true codec control message. If there is a
> use case for such a message, it is better to define it as a separate
> RTCP report message (not call it a codec control message) and=20
> solve the
> header overhead problem with the help of the new message (and any
> additional signaling). Let's keep things simple by not introducing
> transport specific issues in TMMBR.
>=20
> > -----Original Message-----
> > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > Sent: Tuesday, February 13, 2007 9:38 AM
> > To: Randell Jesup; Even, Roni
> > Cc: Dave Singer; avt@ietf.org
> > Subject: RE: [AVT] CCM draft review -- should
> > "bandwidth"includetheheaderoverhead
> >=20
> >=20
> >=20
> > > -----Original Message-----
> > > From: Randell Jesup [mailto:rjesup@wgate.com]
> > >
> > > "Even, Roni" <roni.even@polycom.co.il> writes:
> > > >I think that looking at it from the perspective of the=20
> link is not
> > the
> > > >right direction.  The first question to ask is why does the
> receiver
> > > wants
> > > >to send a TMMBR which is a temporary change. I gave a couple of
> > examples
> > > >in previous emails. (speed between IP and circuit=20
> switch, dividing
> > the
> > > bit
> > > >rate between two video streams, processing issues on codec) Once
> you
> > know
> > > >why the receiver wants to do it than you can try to analyze what
> the
> > > >receiver knows at that stage in order to ask the correct=20
> speed.  My
> > point
> > > >that in most cases when the receiver wants to reduce the speed it
> has
> > to
> > > >do with the coder on the receiver side which knows the media bit
> rate
> > and
> > > >not the link overhead.
> > >
> > > Aha.  This explains some of the disconnect occuring here.=20
>  Those are
> > uses
> > > that haven't even crossed my mind for TMMBR.
> > >
> > > I (and I assume the 3G people, and David Singer and=20
> Magnus I think)
> > are
> > > looking to TMMBR for link status changes, while you are looking to
> it
> > for
> > > a
> > > very different (more codec-oriented) purpose.
> > >
> >=20
> > If TMMBR is not codec oriented then it should not be treated as a
> codec
> > control message and it has to be taken out from "codec control
> messages"
> > draft.
> >=20
> >=20
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www1.ietf.org/mailman/listinfo/avt
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>=20
--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons =
above and may contain confidential information. If you have received the =
message in error, be informed that any use of the content hereof is =
prohibited. Please return it immediately to the sender and delete the =
message. Should you have any questions, please contact us by replying to =
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                       =20

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



From avt-bounces@ietf.org Fri Feb 16 15:51:20 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HIA2M-0001n0-CT; Fri, 16 Feb 2007 15:50:34 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HIA2L-0001mG-Gd; Fri, 16 Feb 2007 15:50:33 -0500
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HIA2L-0000Uf-6D; Fri, 16 Feb 2007 15:50:33 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 7A5362AD38;
	Fri, 16 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HIA1q-0000cJ-70; Fri, 16 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HIA1q-0000cJ-70@stiedprstage1.ietf.org>
Date: Fri, 16 Feb 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-hc-over-mpls-protocol-08.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: Protocol Extensions for Header Compression over MPLS
	Author(s)	: J. Ash, et al.
	Filename	: draft-ietf-avt-hc-over-mpls-protocol-08.txt
	Pages		: 32
	Date		: 2007-2-16
	
This specification defines how to use Multi-Protocol Label Switching
   (MPLS) to route Header-Compressed (HC) packets over an MPLS label
   switched path.  HC can significantly reduce packet-header overhead
   and, in combination with MPLS, can also increases bandwidth
   efficiency and processing scalability in terms of the maximum number
   of simultaneous compressed flows that use HC at each router).  Here
   we define how MPLS pseudowires are used to transport the HC context
   and control messages between the ingress and egress MPLS label
   switching routers.  This is defined for a specific set of existing HC
   mechanisms that might be used, for example, to support voice over IP.
   This specification also describes extension mechanisms to allow
   support for future, as yet to be defined, HC protocols.  In this
   specification, each HC protocol operates independently over a single
   pseudowire instance very much as it would over a single
   point-to-point link.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-hc-over-mpls-protocol-08.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-avt-hc-over-mpls-protocol-08.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-avt-hc-over-mpls-protocol-08.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert theFrom avt-bounces@ietf.org Fri Feb 16 15:51:20 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HIA2M-0001n0-CT; Fri, 16 Feb 2007 15:50:34 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HIA2L-0001mG-Gd; Fri, 16 Feb 2007 15:50:33 -0500
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HIA2L-0000Uf-6D; Fri, 16 Feb 2007 15:50:33 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 7A5362AD38;
	Fri, 16 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HIA1q-0000cJ-70; Fri, 16 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HIA1q-0000cJ-70@stiedprstage1.ietf.org>
Date: Fri, 16 Feb 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-hc-over-mpls-protocol-08.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: Protocol Extensions for Header Compression over MPLS
	Author(s)	: J. Ash, et al.
	Filename	: draft-ietf-avt-hc-over-mpls-protocol-08.txt
	Pages		: 32
	Date		: 2007-2-16
	
This specification defines how to use Multi-Protocol Label Switching
   (MPLS) to route Header-Compressed (HC) packets over an MPLS label
   switched path.  HC can significantly reduce packet-header overhead
   and, in combination with MPLS, can also increases bandwidth
   efficiency and processing scalability in terms of the maximum number
   of simultaneous compressed flows that use HC at each router).  Here
   we define how MPLS pseudowires are used to transport the HC context
   and control messages between the ingress and egress MPLS label
   switching routers.  This is defined for a specific set of existing HC
   mechanisms that might be used, for example, to support voice over IP.
   This specification also describes extension mechanisms to allow
   support for future, as yet to be defined, HC protocols.  In this
   specification, each HC protocol operates independently over a single
   pseudowire instance very much as it would over a single
   point-to-point link.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-hc-over-mpls-protocol-08.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-avt-hc-over-mpls-protocol-08.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-avt-hc-over-mpls-protocol-08.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-hc-over-mpls-protocol-08.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-avt-hc-over-mpls-protocol-08.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

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

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

--NextPart--


From avt-bounces@ietf.org Fri Feb 16 15:51:20 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HIA23-0001So-Ir; Fri, 16 Feb 2007 15:50:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HIA1r-0001Ps-HH; Fri, 16 Feb 2007 15:50:03 -0500
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HIA1q-0006vc-Rc; Fri, 16 Feb 2007 15:50:03 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id C2D90328FA;
	Fri, 16 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HIA1q-0000dH-K0; Fri, 16 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HIA1q-0000dH-K0@stiedprstage1.ietf.org>
Date: Fri, 16 Feb 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtcphr-00.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: RTCP HR - High Resolution VoIP Metrics Report Blocks
	Author(s)	: A. Clark, et al.
	Filename	: draft-ietf-avt-rtcphr-00.txt
	Pages		: 
	Date		: 2007-2-16
	
   This document defines extensions to the RTCP XR extended report
   packet type blocks to support Voice over IP (VoIP) monitoring
   for services that require higher resolution or more detailed
   metrics than those supported by RFC3611 [3].


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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous F command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-hc-over-mpls-protocol-08.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-avt-hc-over-mpls-protocol-08.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

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

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

--NextPart--


From avt-bounces@ietf.org Fri Feb 16 15:51:20 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HIA23-0001So-Ir; Fri, 16 Feb 2007 15:50:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HIA1r-0001Ps-HH; Fri, 16 Feb 2007 15:50:03 -0500
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HIA1q-0006vc-Rc; Fri, 16 Feb 2007 15:50:03 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id C2D90328FA;
	Fri, 16 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HIA1q-0000dH-K0; Fri, 16 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HIA1q-0000dH-K0@stiedprstage1.ietf.org>
Date: Fri, 16 Feb 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtcphr-00.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: RTCP HR - High Resolution VoIP Metrics Report Blocks
	Author(s)	: A. Clark, et al.
	Filename	: draft-ietf-avt-rtcphr-00.txt
	Pages		: 
	Date		: 2007-2-16
	
   This document defines extensions to the RTCP XR extended report
   packet type blocks to support Voice over IP (VoIP) monitoring
   for services that require higher resolution or more detailed
   metrics than those supported by RFC3611 [3].


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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-avt-rtcphr-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-avt-rtcphr-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtcphr-00.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-avt-rtcphr-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

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

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

--NextPart--






TP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-avt-rtcphr-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-avt-rtcphr-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtcphr-00.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-avt-rtcphr-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

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

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

--NextPart--






From avt-bounces@ietf.org Sat Feb 17 13:06:46 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HITvW-00058k-C4; Sat, 17 Feb 2007 13:04:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HITvU-00058f-Ou
	for avt@ietf.org; Sat, 17 Feb 2007 13:04:48 -0500
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HITvT-0001tq-DW
	for avt@ietf.org; Sat, 17 Feb 2007 13:04:48 -0500
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:60564
	helo=[192.168.0.3])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HITvS-0002OA-Nc for avt@ietf.org; Sat, 17 Feb 2007 18:04:46 +0000
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <E1HIA1q-0000cJ-70@stiedprstage1.ietf.org>
References: <E1HIA1q-0000cJ-70@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <BE4FC908-52BF-4ECE-A62C-38D87D7E4176@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-hc-over-mpls-protocol-08.txt 
Date: Sat, 17 Feb 2007 18:04:57 +0000
To: IETF AVT WG <avt@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On 16 Feb 2007, at 20:50, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Audio/Video Transport Working  
> Group of the IETF.
>
> 	Title		: Protocol Extensions for Header Compression over MPLS
> 	Author(s)	: J. Ash, et al.
> 	Filename	: draft-ietf-avt-hc-over-mpls-protocol-08.txt
> 	Pages		: 32
> 	Date		: 2007-2-16
> 	
> This specification defines how to use Multi-Protocol Label Switching
>    (MPLS) to route Header-Compressed (HC) packets over an MPLS label
>    switched path.  HC can significantly reduce packet-header overhead
>    and, in combination with MPLS, can also increases bandwidth
>    efficiency and processing scalability in terms of the maximum  
> number
>    of simultaneous compressed flows that use HC at each router).  Here
>    we define how MPLS pseudowires are used to transport the HC context
>    and control messages between the ingress and egress MPLS label
>    switching routers.  This is defined for a specific set of  
> existing HC
>    mechanisms that might be used, for example, to support voice  
> over IP.
>    This specification also describes extension mechanisms to allow
>    support for future, as yet to be defined, HC protocols.  In this
>    specification, each HC protocol operates independently over a  
> single
>    pseudowire instance very much as it would over a single
>    point-to-point link.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-hc-over-mpls- 
> protocol-08.txt

To update the working group: there were some comments received during  
IETF last call, which this version of the draft is intended to  
address. For details, see: https://datatracker.ietf.org/public/ 
pidtracker.cgi?command=view_id&dTag=13573

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



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



From avt-bounces@ietf.org Sun Feb 18 08:45:33 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HImKJ-0008Cp-Iw; Sun, 18 Feb 2007 08:43:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HImKI-0008Cf-6r
	for avt@ietf.org; Sun, 18 Feb 2007 08:43:38 -0500
Received: from [212.25.125.1] (helo=aclmsg.corp.audiocodes.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HImKG-0001pt-Hy
	for avt@ietf.org; Sun, 18 Feb 2007 08:43:38 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 18 Feb 2007 15:43:31 +0200
Message-ID: <79B4F738DDD4EF4F85A4641A0FE5EFD602CA8B7E@aclmsg.corp.audiocodes.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Concatenation of RTP streams
Thread-Index: AcdTYsfYSJ5A7VSgSky7p6aMZ8aO9w==
From: "Yuval Nissan" <Yuval.Nissan@audiocodes.com>
To: <avt@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a3f7094ccc62748c06b21fcf44c073ee
Cc: Eli  Shoval <Eli.Shoval@audiocodes.com>
Subject: [AVT] Concatenation of RTP streams
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0341575171=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0341575171==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C75362.C6F7410B"

This is a multi-part message in MIME format.

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

Hi,=20

=20

There can be different scenarios in a unicast session that the incoming
stream is changed\restart without signaling it to the receiver.

=20

Examples:

1.	The remote side is reset because of some problem - In this case
the remote side usually keeps the same SSRC, but the sequence number and
timestamp usually start from new random value.=20
2.	When few RTP streams from different sources are aggregated (in
real time) one after another to create one stream (for example: adding
announcements, advertising, etc).
3.	Video Conference Server that does only RTP switching.

=20

RFC 3550 appendix A describes algorithm to handle these cases, and the
tradeoff between fast transit and validity check. As I understand from
the code there (update_seq() function) - at least 1 packet is dropped
during the stream transit. This can be problematic in video application
where the first packet is Intra and can cause freeze of long duration.

=20

I would like to get your feedback how this issue is implemented today in
RTP stacks (In devices such as video conferencing endpoints and
streaming clients)?

=20

I think it would be better to define a standard way to notify the
receiver (should be inband) before the RTP switch, so no packet is
getting lost. What do you think?

=20

Regards,

Yuval=20

=20

=20


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

<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@Batang";
	panose-1:2 3 6 0 0 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi, </span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>There can be different scenarios in a unicast session =
that the
incoming stream is changed\restart without signaling it to the =
receiver.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Examples:</span></font></p>

<ol style=3D'margin-top:0in' start=3D1 type=3D1>
 <li class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
     font-family:Arial'>The remote side is reset because of some problem =
- In
     this case the remote side usually keeps the same SSRC, but the =
sequence
     number and timestamp usually start from new random value. =
</span></font></li>
 <li class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
     font-family:Arial'>When few RTP streams from different sources are =
aggregated
     (in real time) one after another to create one stream (for example: =
adding
     announcements, advertising, etc).</span></font></li>
 <li class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
     font-family:Arial'>Video Conference Server that does only RTP =
switching.</span></font></li>
</ol>

<p class=3DMsoNormal style=3D'margin-left:.25in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>RFC 3550 appendix A describes algorithm to handle =
these
cases, and the tradeoff between fast transit and validity check. As I
understand from the code there (update_seq() function) &#8211; at least =
1
packet is dropped during the stream transit. This can be problematic in =
video
application where the first packet is Intra and can cause freeze of long
duration.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I would like to get your feedback how this issue is
implemented today in RTP stacks (In devices such as video conferencing
endpoints and streaming clients)?</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I think it would be better to define a standard way =
to notify
the receiver (should be inband) before the RTP switch, so no packet is =
getting
lost. What do you think?</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Regards,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Yuval </span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

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

</div>

</body>

</html>

------_=_NextPart_001_01C75362.C6F7410B--


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

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

--===============0341575171==--




From avt-bounces@ietf.org Sun Feb 18 09:35:41 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HIn7M-0007Qx-U7; Sun, 18 Feb 2007 09:34:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HIn7L-0007Qk-L8
	for avt@ietf.org; Sun, 18 Feb 2007 09:34:19 -0500
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HIn7K-0000RT-6j
	for avt@ietf.org; Sun, 18 Feb 2007 09:34:19 -0500
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:63117
	helo=[192.168.0.3])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HIn7J-0004d6-DH; Sun, 18 Feb 2007 14:34:17 +0000
In-Reply-To: <79B4F738DDD4EF4F85A4641A0FE5EFD602CA8B7E@aclmsg.corp.audiocodes.com>
References: <79B4F738DDD4EF4F85A4641A0FE5EFD602CA8B7E@aclmsg.corp.audiocodes.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed
Message-Id: <C9F23E39-C7C4-4B8F-840E-DC0F5D37941D@csperkins.org>
Content-Transfer-Encoding: quoted-printable
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Concatenation of RTP streams
Date: Sun, 18 Feb 2007 14:34:28 +0000
To: Yuval Nissan <Yuval.Nissan@audiocodes.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: Eli Shoval <Eli.Shoval@audiocodes.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On 18 Feb 2007, at 13:43, Yuval Nissan wrote:
> There can be different scenarios in a unicast session that the =20
> incoming stream is changed\restart without signaling it to the =20
> receiver.
>
>
> Examples:
>
> The remote side is reset because of some problem - In this case the =20=

> remote side usually keeps the same SSRC, but the sequence number =20
> and timestamp usually start from new random value.

The SSRC should change in this case.

> When few RTP streams from different sources are aggregated (in real =20=

> time) one after another to create one stream (for example: adding =20
> announcements, advertising, etc).

In this case, the aggregator is supposed to ensure the sequence =20
numbers and timestamps are maintained. Alternatively, the inserts =20
should use different SSRC values.

> Video Conference Server that does only RTP switching.

Again, the SSRC should change when the switch occurs.

> RFC 3550 appendix A describes algorithm to handle these cases, and =20
> the tradeoff between fast transit and validity check. As I =20
> understand from the code there (update_seq() function) =96 at least 1 =20=

> packet is dropped during the stream transit. This can be =20
> problematic in video application where the first packet is Intra =20
> and can cause freeze of long duration.

An implementation can buffer packets with unexpected RTP sequence =20
numbers, if it suspects those packets will shortly be shown to be =20
valid, which would avoid the problems you highlight.

> I would like to get your feedback how this issue is implemented =20
> today in RTP stacks (In devices such as video conferencing =20
> endpoints and streaming clients)?
>
>
> I think it would be better to define a standard way to notify the =20
> receiver (should be inband) before the RTP switch, so no packet is =20
> getting lost. What do you think?

I'm not sure any such notification is needed, beyond the expected =20
SSRC change. This seems to be a quality of implementation issue, =20
rather than a standards problem.

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



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



From avt-bounces@ietf.org Mon Feb 19 11:46:44 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJBdf-0001T8-HJ; Mon, 19 Feb 2007 11:45:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJBde-0001Ss-1E
	for avt@ietf.org; Mon, 19 Feb 2007 11:45:18 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJBdU-0003Io-76
	for avt@ietf.org; Mon, 19 Feb 2007 11:45:18 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	A51CA20602; Mon, 19 Feb 2007 17:45:05 +0100 (CET)
X-AuditID: c1b4fb3c-b0fcabb0000007de-16-45d9d411d123 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	83DA0204B6; Mon, 19 Feb 2007 17:45:05 +0100 (CET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 19 Feb 2007 17:45:05 +0100
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 19 Feb 2007 17:45:04 +0100
Message-ID: <45D9D410.2070506@ericsson.com>
Date: Mon, 19 Feb 2007 17:45:04 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Franceschini Guido <guido.franceschini@telecomitalia.it>
Subject: Re: [AVT] CCM draft review
	--	should"bandwidth"includetheheaderoverhead
References: <E9D1028EC5C22B418B5D54CA6EA27C579A5E76@PTPEVS108BA020.idc.cww.telecomitalia.it>
In-Reply-To: <E9D1028EC5C22B418B5D54CA6EA27C579A5E76@PTPEVS108BA020.idc.cww.telecomitalia.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Feb 2007 16:45:04.0563 (UTC)
	FILETIME=[4E3FD030:01C75445]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48
Cc: Randell Jesup <rjesup@wgate.com>, "Even, Roni" <roni.even@polycom.co.il>,
	avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi,

Guido, I think your draft is very interesting when it comes to work on 
updating RFC 3890 and the TIAS concept to something that works. However 
for the moment I would like to focus on solving the issue around CCM. 
Thus I will below remind you all of the purpose of TMMBR, the topologies 
and their impact and then discuss the alternatives that has been raised. 
  Looking at the advantages and disadvantages.

TMMBR as currently written in CCM has the following usages:

1. A mixer requests a media sender to reduce its bit-rate to have the 
mixer avoid doing transcoding for some or all session participants.

2. Put an upper limit for the congestion control to probe when known 
path limitations exist. Such signals that a receiver could know is 
changes in the link layer, for example a wireless that effect the 
maximum bit-rate the link will be able to transfer.

For the first case the topology one discuss to use TMMBR in is the 
following:

    +---+      +------------+      +---+
    | A |<---->|            |<---->| B |
    +---+      |            |      +---+
               |   Mixer    |
    +---+      |            |      +---+
    | C |<---->|            |<---->| D |
    +---+      +------------+      +---+

A. Mixer sending TMMBR

In this case the mixer may request that A reduces it transmission 
bit-rate, due to a limitation on any of the paths to B-D. The bit-rate 
has been learned by the mixer as a result of congestion control between 
a itself and the receiver, or from a TMMBR message from receiver.

For the second usage this occurs in the following topologies.

    +---+         +---+
    | A |<------->| B |
    +---+         +---+

B. Point to Point where receiver send TMMBR directly

               +-----+
    +---+     /       \    +---+
    | A |----/         \---| B |
    +---+   /   Multi-  \  +---+
           +    Cast     +
    +---+   \  Network  /  +---+
    | C |----\         /---| D |
    +---+     \       /    +---+
               +-----+
C. Point to Multipoint using Multicast where any receiver may send TMMBR 
to any sender.

In these case the receiver sending the TMMBR knows a limitation on the 
path between the sender and itself.

So what method of reporting the known bit-rate is the best. Lets start 
looking at the comparison when all links have homogeneous overhead, i.e. 
there are no transparent translators, like NATs present within the 
topologies.

The two main ways of reporting the available bit-rate restriction that 
has been proposed are:

X. IP layer Gross Bit-rate, i.e. all bit-rate consumed by all the 
packets from the IP header and above.

Y. Media layer bit-rate, i.e. the bit-rate that may be consumed by the 
media encoding only. Thus excluding any bit-rate consumed by the headers 
used to packetize the media, e.g. IP, UDP, RTP, RTP Payload headers.

Considering these two proposals in regards to the usages above.

For usage A the mixer can easily provide a IP-gross bit-rate from its 
congestion control. If the mixer would have to provide a media bit-rate 
  to the sender then the following uncertainties creep in.

R1. The IP layer congestion control does not equal the media bit-rate, 
thus requiring the mixer to continuously measure the media bit-rate vs 
IP layer bit-rate to determine how much the media bit-rate should be 
reduced.

R2. In cases a reduced media bit-rate results in a change of the 
packetization scheme from the sender the resulting IP bit-rate will not 
change. Thus reducing the possibility to maximize the utilization as a 
certain marginal would be needed.

R3. Any changes in the packetization scheme as a result of other reasons 
than available bit-rate may result in the need to send a new TMMBR 
message to have the sender adjust its total bit-rate due to the changed 
overhead. Thus increasing the signalling churn needed.

Looking at usage B, it is highly dependent on the type of bit-rate 
restriction. For cases when the restriction is easy to measure in IP 
layer bit-rate then that is advantageous. In cases when a packet rate 
would be need to derive either the IP layer or media bit-rate available 
then they are from complexity point of view similar. Assuming that one 
has measured the packet rate prior to needing to send the TMMBR request 
one can use that rate to estimate the amount of overhead also introduced 
in the future. Thus resulting in the same error situations raised in R2 
and R3. This error is dependent on two factors, the error in the packet 
rate estimation and the amount of per packet overhead need to reach a 
value for the reported layer. So in case one knows the link layer 
bit-rate available, the IP layer error is only the overhead of the 
link-layer headers, while a media bit-rate may be link-layer, IP, UDP 
and RTP overhead multiplied by the error in estimating the packet rate.

Usage C, is no different from B.

One advantage of the media bit-rate is when it interfaces through 
gateways to other technologies that are based on circuit switched 
technologies and uses media bit-rate, such as H.323.

So far the sender has used the assumption that the overhead per packet 
the receiver sees equals what the sender see, i.e. the protocol stacks 
are identical for both sender and receiver. This is the reasonable 
assumption unless information is provide on the contrary.

Lets introduce a transparent translator, for example NAPT that changes 
the IP version from 4 to 6 and vice versa when packets flow through it. 
This change of per packet overhead results only in a different value for 
the overhead to be used in calculation to estimate what media rate can 
be supported. Thus the size of error can be effected by this. For a IP 
layer bit-rate value this results in bit-rate flowing through the 
restriction may be larger than the requested maximum value in cases the 
overhead at the restriction is larger than at the sender. In these case 
the restricting entity would end up being the congestion control and 
TMMBR looses its meaning. In cases where the overhead is reduced this 
results in a under-utilization. Similar cases occurs in the media 
bit-rate solution when the packet-rate estimate is off and the resulting 
transmission bit-rate results in congestion or under-utilization. 
Independent of what the value represents the receiver can updated its 
TMMBR value, however it would be to late and simply be a correction 
after the issue has arisen.

If one would be to refine the IP layer bit-rate value with an overhead 
measurement. I would propose the simple filtration of keeping 15/16 of 
the old value and add 1/16 of the last packets value for each packet 
received. That way a sender can compare the overhead seen by the 
receiver with what it is sending. By the filtering on both sides this 
should provide a rather stable number to determining any differences in 
overhead. By doing this the sender can take the per packet overhead 
directly into account when transmitting media avoiding overshooting the 
TMMBR bit-rate value. It even lets a receiver take header compression 
into account if the restriction and header compression is happening over 
the same link.

As I see it a IP layer bit-rate value with a filtered value for the per 
packet overhead, IP up to and including the RTP packet header has the 
least downsides. It reports the actual restriction bit-rate value for 
the common networking layer. It allows the sender to directly take the 
effect on packetization on the total bit-rate into account. It also 
avoids running the bit-rate value as a relative value that are adjusted 
based on measurements on the arriving packets.

Comments

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



From avt-bounces@ietf.org Mon Feb 19 22:18:37 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJLUm-00086U-S4; Mon, 19 Feb 2007 22:16:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJLUl-00086K-Ra
	for avt@ietf.org; Mon, 19 Feb 2007 22:16:47 -0500
Received: from zcars04e.nortel.com ([47.129.242.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJLUk-0007Wj-GO
	for avt@ietf.org; Mon, 19 Feb 2007 22:16:47 -0500
Received: from zcarhxs1.corp.nortel.com (zcarhxs1.corp.nortel.com
	[47.129.230.89])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	l1K38ON29755; Mon, 19 Feb 2007 22:08:24 -0500 (EST)
Received: from [47.130.17.37] ([47.130.17.37] RDNS failed) by
	zcarhxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 19 Feb 2007 22:16:26 -0500
Message-ID: <45DA67F7.5090108@nortel.com>
Date: Mon, 19 Feb 2007 22:16:07 -0500
From: "Tom-PT Taylor" <taylor@nortel.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Dave Singer <singer@apple.com>, Hari Desineni <hd@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Feb 2007 03:16:26.0336 (UTC)
	FILETIME=[818BA600:01C7549D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: avt@ietf.org
Subject: [AVT] draft-ietf-avt-rtp-hdrext-09.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

I write this in some embarrassment for the lateness of the day.

I was reviewing draft-ietf-avt-rtp-hdrext-09.txt one last time for the 
PROTO write-up and noted several places where I might have said things 
differently. No show stoppers until I came to the formal ABNF (section 
7), which I believe has two errors due to the use of parentheses rather 
than square brackets (which denote optionality in ABNF).

First: the direction attribute is supposed to be optional. That means 
("/" direction) should be ["/" direction], as it is in section 5.

Second: the existing specification of mapattrs makes a space mandatory 
at the end of the a=extmap line if there are no extension attributes. 
This is because the expression

   (space extensionattributes)

evaluates to (space) if extensionattributes is a null string. You get 
what you want by using square brackets around the above expression 
instead of parentheses.

Now that the draft needs fixing anyway, here are my nits. These can be 
ignored if you don't have time to follow up.

1. The abstract mildly contradicts the IANA considerations, in that it 
says flatly that extensions are unregistered. May I suggest saying 
instead: "in general unregistered" or "unregistered except for those 
defined by the IETF", with the latter perhaps preferred?

2. Drop "to" at the end of the first line of the Introduction.

3. I don't understand the one-sentence paragraph at the end of the 
Introduction. What "value"? Are you really saying:

"This specification applies to extensions of the RTP/AVP profile."

or is the sentence misplaced?

4. In section 4, I would rephrase:

"The 4-bit length is the length minus one of the data bytes of this
    header extension element (excluding this one-byte header)."

to read instead:

"The 4-bit length is the number minus one of data bytes of this
    header extension element following the one-byte header."

5. In section 6, second paragraph (immediately after the bullets), I 
think the first occurrence of the word "may" should be an RFC 2119 
"MAY", and the second occurrence should be an RFC 2119 "MUST":

"A direction attribute MAY be included in an extmap ..." and

"The direction MUST be one of ...".

6. The last paragraph on page 10 before the example reads:

"Note that either party may include extensions in the stream other
    than those negotiated, or those negotiated as "inactive", for example
    for the benefit of intermediate nodes.  Only extensions with an
    identifier in the range 1-14, and with a declaration, can be sent."

In that last line, "and with a declaration" seems to contradict "other 
than those negotiated" in the preceding lines. What is meant here? I 
also think that "may" in the first line should be an RFC 2119 "MAY".

Again, apologies for being so last-minute.

Tom Taylor

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



From avt-bounces@ietf.org Tue Feb 20 06:06:00 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJSnN-00074W-QF; Tue, 20 Feb 2007 06:04:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJSnM-0006xf-E8
	for avt@ietf.org; Tue, 20 Feb 2007 06:04:28 -0500
Received: from maile.telecomitalia.it ([156.54.233.31])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJSnF-0004sM-Se
	for avt@ietf.org; Tue, 20 Feb 2007 06:04:28 -0500
Received: from ptpxch007ba020.idc.cww.telecomitalia.it ([156.54.240.50]) by
	maile.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830);
	Tue, 20 Feb 2007 12:04:17 +0100
Received: from PTPEVS108BA020.idc.cww.telecomitalia.it ([156.54.241.227]) by
	ptpxch007ba020.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 20 Feb 2007 12:04:17 +0100
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Importance: normal
Content-Transfer-Encoding: quoted-printable
Priority: normal
Subject: R: [AVT] CCM draft review --	should"bandwidth"includetheheaderoverhead
Date: Tue, 20 Feb 2007 12:04:16 +0100
Message-ID: <E9D1028EC5C22B418B5D54CA6EA27C579A5E86@PTPEVS108BA020.idc.cww.telecomitalia.it>
In-Reply-To: <45D9D410.2070506@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] CCM draft review
	--	should"bandwidth"includetheheaderoverhead
thread-index: AcdURVJ5bGrcyMW9Q0ev7yVgKR3JjgAhgSGQ
References: <E9D1028EC5C22B418B5D54CA6EA27C579A5E76@PTPEVS108BA020.idc.cww.telecomitalia.it>
	<45D9D410.2070506@ericsson.com>
From: "Franceschini Guido" <guido.franceschini@telecomitalia.it>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-OriginalArrivalTime: 20 Feb 2007 11:04:17.0053 (UTC)
	FILETIME=[DCFF24D0:01C754DE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: abda3837e791065a13ac6f11cf8e625a
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Dear Magnus, all,

IMHO all the issues being described so far can be reduced to the problem =
of making the sender aware of the bottlenecks it shall respect. Thus, if =
we identify a suitable characterization of the bottleneck(s), then we =
are done (in terms of signalling).
Depending on the different cases, as you show, bottlenecks can be more =
effectively characterized by the media bitrate, or by the IP gross =
bitrate. Plus possibly additional params such as average overhead and/or =
packet rate.

Then the problem I see you are debating is: which choice is better? or, =
which choice has the least downsides? This derives from the assumption =
(which has become a constraint) that either one or the other metric =
should be used. I think this can be relaxed.

If we define metrics that are generic and neutral, and that can =
represent either the media bitrate or the IP gross rate or even the =
bandwidth as measured at some other layer, than what would be the cons?

To be more practical, I try to review your Mixer scenario, and to show =
how my proposal would adapt to it.
My proposal, in essence, consists in always providing a tuple made of =
<available bandwidth measured at layer X, average per packet overhead =
measured at the same layer X>, and having the sender collect all the =
information about bottlenecks so as to determine how to generate traffic =
that fits all constraints.


Scenario A, the mixer

Suppose the mixer received information about the bottleneck towards =
receiver D (BottD =3D <TIDC_D, MPO_D>): it could simply propagate that =
same bottleneck info to the A, B and C senders. Then the traffic =
generated by each of them would comply with the constraints in the path =
to D, although A, B and C might have chosen different encoding and =
transmission parameters.

With numbers:
BottD =3D <21000, 40>
A chooses to generate AMR at 4750, with 20 ms per packet (50 pkt/sec)
=3D=3D> with respect to D metrics A generates 50*40*8=3D16000 bit/s of =
overhead + 4750 of payload (total of 20750 < 21000)

B chooses to generate AMR at 12200, with 40 ms per packet (25 pkt/sec)
=3D=3D> with respect to D metrics B generates 25*40*8=3D8000 bit/s of =
overhead + 12200 of payload (total of 20200 < 21000)

C chooses ....

Suppose than that receiver C as well has a bottleneck, but has a =
different stack (e.g. a VPN that duplicates the IP layer)

Then C could notify such bottleneck BottC to the Mixer, and this could =
be again propagated to the A, B and D senders.

With numbers:
BottD =3D <21000, 40>
BottC =3D <25000, 60>
If the same choices as before were kept:
A would generate AMR at 4750, with 20 ms per packet (50 pkt/sec)
=3D=3D> with respect to D metrics A generates 50*40*8=3D16000 bit/s of =
overhead + 4750 of payload (total of 20750 < 21000)
=3D=3D> with respect to C metrics A generates 50*60*8=3D24000 bit/s of =
overhead + 4750 of payload (total of 28750 > 25000) NOT OK

B would generate AMR at 12200, with 40 ms per packet (25 pkt/sec)
=3D=3D> with respect to D metrics B generates 25*40*8=3D8000 bit/s of =
overhead + 12200 of payload (total of 20200 < 21000)
=3D=3D> with respect to C metrics B generates 25*60*8=3D12000 bit/s of =
overhead + 12200 of payload (total of 24200 < 25000) STILL OK

By means of collecting the bottleneck info, in such a case the sender A =
will decide to change its encoding/transmitter parameters, while sender =
B would take no action.

Now suppose receiver A has a bottleneck too, but its stack is of a yet =
different nature, since it resides in a H323 branch. Here the media =
bitrate is more meaningful than any other measurement, thus it would =
communicate its bottleneck characterization providing the media codec =
layer measurements:
BottA =3D <8000,0>

I.e., it tells the Mixer that it can receive up to 8000 bit/sec of =
audio, irrespective of the packetization scheme in use (the overhead is =
0 at this layer).
The Mixer would once again propagate this information to the B, C and D =
sender which in turn will determine their encoding and transmission =
parameters matching all bottleneck constraints. Etc, etc etc.

Now also receiver B communicates a bottleneck. B is behind a NAPT that =
maps IPV4 to IPV6, i.e. B runs an IPV6 stack.
Once again, B will communicate its BottB tuple, which will contain yet =
another overhead figure. And the Mixer will propagate the BottB =
information to senders A, C and D, which in turn will determine their =
encoding and transmission parameters matching all bottleneck =
constraints. Etc, etc etc.

Comments?

Guido



-----Messaggio originale-----
Da: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]=20
Inviato: luned=EC 19 febbraio 2007 17.45
A: Franceschini Guido
Cc: Desineni, Harikishan; Randell Jesup; Even, Roni; avt@ietf.org
Oggetto: Re: [AVT] CCM draft review -- =
should"bandwidth"includetheheaderoverhead

Hi,

Guido, I think your draft is very interesting when it comes to work on=20
updating RFC 3890 and the TIAS concept to something that works. However=20
for the moment I would like to focus on solving the issue around CCM.=20
Thus I will below remind you all of the purpose of TMMBR, the topologies =

and their impact and then discuss the alternatives that has been raised. =

  Looking at the advantages and disadvantages.

TMMBR as currently written in CCM has the following usages:

1. A mixer requests a media sender to reduce its bit-rate to have the=20
mixer avoid doing transcoding for some or all session participants.

2. Put an upper limit for the congestion control to probe when known=20
path limitations exist. Such signals that a receiver could know is=20
changes in the link layer, for example a wireless that effect the=20
maximum bit-rate the link will be able to transfer.

For the first case the topology one discuss to use TMMBR in is the=20
following:

    +---+      +------------+      +---+
    | A |<---->|            |<---->| B |
    +---+      |            |      +---+
               |   Mixer    |
    +---+      |            |      +---+
    | C |<---->|            |<---->| D |
    +---+      +------------+      +---+

A. Mixer sending TMMBR

In this case the mixer may request that A reduces it transmission=20
bit-rate, due to a limitation on any of the paths to B-D. The bit-rate=20
has been learned by the mixer as a result of congestion control between=20
a itself and the receiver, or from a TMMBR message from receiver.

For the second usage this occurs in the following topologies.

    +---+         +---+
    | A |<------->| B |
    +---+         +---+

B. Point to Point where receiver send TMMBR directly

               +-----+
    +---+     /       \    +---+
    | A |----/         \---| B |
    +---+   /   Multi-  \  +---+
           +    Cast     +
    +---+   \  Network  /  +---+
    | C |----\         /---| D |
    +---+     \       /    +---+
               +-----+
C. Point to Multipoint using Multicast where any receiver may send TMMBR =

to any sender.

In these case the receiver sending the TMMBR knows a limitation on the=20
path between the sender and itself.

So what method of reporting the known bit-rate is the best. Lets start=20
looking at the comparison when all links have homogeneous overhead, i.e. =

there are no transparent translators, like NATs present within the=20
topologies.

The two main ways of reporting the available bit-rate restriction that=20
has been proposed are:

X. IP layer Gross Bit-rate, i.e. all bit-rate consumed by all the=20
packets from the IP header and above.

Y. Media layer bit-rate, i.e. the bit-rate that may be consumed by the=20
media encoding only. Thus excluding any bit-rate consumed by the headers =

used to packetize the media, e.g. IP, UDP, RTP, RTP Payload headers.

Considering these two proposals in regards to the usages above.

For usage A the mixer can easily provide a IP-gross bit-rate from its=20
congestion control. If the mixer would have to provide a media bit-rate=20
  to the sender then the following uncertainties creep in.

R1. The IP layer congestion control does not equal the media bit-rate,=20
thus requiring the mixer to continuously measure the media bit-rate vs=20
IP layer bit-rate to determine how much the media bit-rate should be=20
reduced.

R2. In cases a reduced media bit-rate results in a change of the=20
packetization scheme from the sender the resulting IP bit-rate will not=20
change. Thus reducing the possibility to maximize the utilization as a=20
certain marginal would be needed.

R3. Any changes in the packetization scheme as a result of other reasons =

than available bit-rate may result in the need to send a new TMMBR=20
message to have the sender adjust its total bit-rate due to the changed=20
overhead. Thus increasing the signalling churn needed.

Looking at usage B, it is highly dependent on the type of bit-rate=20
restriction. For cases when the restriction is easy to measure in IP=20
layer bit-rate then that is advantageous. In cases when a packet rate=20
would be need to derive either the IP layer or media bit-rate available=20
then they are from complexity point of view similar. Assuming that one=20
has measured the packet rate prior to needing to send the TMMBR request=20
one can use that rate to estimate the amount of overhead also introduced =

in the future. Thus resulting in the same error situations raised in R2=20
and R3. This error is dependent on two factors, the error in the packet=20
rate estimation and the amount of per packet overhead need to reach a=20
value for the reported layer. So in case one knows the link layer=20
bit-rate available, the IP layer error is only the overhead of the=20
link-layer headers, while a media bit-rate may be link-layer, IP, UDP=20
and RTP overhead multiplied by the error in estimating the packet rate.

Usage C, is no different from B.

One advantage of the media bit-rate is when it interfaces through=20
gateways to other technologies that are based on circuit switched=20
technologies and uses media bit-rate, such as H.323.

So far the sender has used the assumption that the overhead per packet=20
the receiver sees equals what the sender see, i.e. the protocol stacks=20
are identical for both sender and receiver. This is the reasonable=20
assumption unless information is provide on the contrary.

Lets introduce a transparent translator, for example NAPT that changes=20
the IP version from 4 to 6 and vice versa when packets flow through it.=20
This change of per packet overhead results only in a different value for =

the overhead to be used in calculation to estimate what media rate can=20
be supported. Thus the size of error can be effected by this. For a IP=20
layer bit-rate value this results in bit-rate flowing through the=20
restriction may be larger than the requested maximum value in cases the=20
overhead at the restriction is larger than at the sender. In these case=20
the restricting entity would end up being the congestion control and=20
TMMBR looses its meaning. In cases where the overhead is reduced this=20
results in a under-utilization. Similar cases occurs in the media=20
bit-rate solution when the packet-rate estimate is off and the resulting =

transmission bit-rate results in congestion or under-utilization.=20
Independent of what the value represents the receiver can updated its=20
TMMBR value, however it would be to late and simply be a correction=20
after the issue has arisen.

If one would be to refine the IP layer bit-rate value with an overhead=20
measurement. I would propose the simple filtration of keeping 15/16 of=20
the old value and add 1/16 of the last packets value for each packet=20
received. That way a sender can compare the overhead seen by the=20
receiver with what it is sending. By the filtering on both sides this=20
should provide a rather stable number to determining any differences in=20
overhead. By doing this the sender can take the per packet overhead=20
directly into account when transmitting media avoiding overshooting the=20
TMMBR bit-rate value. It even lets a receiver take header compression=20
into account if the restriction and header compression is happening over =

the same link.

As I see it a IP layer bit-rate value with a filtered value for the per=20
packet overhead, IP up to and including the RTP packet header has the=20
least downsides. It reports the actual restriction bit-rate value for=20
the common networking layer. It allows the sender to directly take the=20
effect on packetization on the total bit-rate into account. It also=20
avoids running the bit-rate value as a relative value that are adjusted=20
based on measurements on the arriving packets.

Comments

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------
--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons =
above and may contain confidential information. If you have received the =
message in error, be informed that any use of the content hereof is =
prohibited. Please return it immediately to the sender and delete the =
message. Should you have any questions, please contact us by replying to =
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                       =20

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



From avt-bounces@ietf.org Tue Feb 20 07:34:34 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJUBd-0002GI-A6; Tue, 20 Feb 2007 07:33:37 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJUBc-0002GB-71
	for avt@ietf.org; Tue, 20 Feb 2007 07:33:36 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJUBU-0001iM-ND
	for avt@ietf.org; Tue, 20 Feb 2007 07:33:36 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	0C08F20FA6; Tue, 20 Feb 2007 13:33:24 +0100 (CET)
X-AuditID: c1b4fb3e-aeed1bb0000007e1-ec-45daea93b624 
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	DAA8C20485; Tue, 20 Feb 2007 13:33:23 +0100 (CET)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 20 Feb 2007 13:33:23 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 20 Feb 2007 13:33:22 +0100
Message-ID: <026F8EEDAD2C4342A993203088C1FC050474B0C8@esealmw109.eemea.ericsson.se>
In-Reply-To: <45DAB333.9000806@netlab.hut.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Review of draft-johansson-avt-rtcp-avpf-non-compound-00.txt
Thread-Index: AcdUyl3TiFsXeGKTRWyEsndR5AnBlAADeTSw
From: "Ingemar Johansson S \(LU/EAB\)" <ingemar.s.johansson@ericsson.com>
To: "Joerg Ott" <jo@netlab.tkk.fi>,
	"Tom-PT Taylor" <taylor@nortel.com>
X-OriginalArrivalTime: 20 Feb 2007 12:33:23.0473 (UTC)
	FILETIME=[4FB61810:01C754EB]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Cc: "Magnus Westerlund \(KI/EAB\)" <magnus.westerlund@ericsson.com>,
	John Lazzaro <lazzaro@eecs.berkeley.edu>,
	Roni Even <roni.even@polycom.co.il>, IETF AVT WG <avt@ietf.org>,
	"Ingemar Johansson S \(LU/EAB\)" <ingemar.s.johansson@ericsson.com>,
	Colin Perkins <csp@csperkins.org>
Subject: [AVT] RE: Review of
	draft-johansson-avt-rtcp-avpf-non-compound-00.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi

Comments inline with text below.=20

> -----Original Message-----
> From: Joerg Ott [mailto:jo@netlab.tkk.fi]=20
> Sent: den 20 februari 2007 09:37
> To: Tom-PT Taylor
> Cc: Joerg Ott; John Lazzaro; Colin Perkins; Roni Even;=20
> Ingemar Johansson S (LU/EAB); Magnus Westerlund (KI/EAB); IETF AVT WG
> Subject: Re: Review of=20
> draft-johansson-avt-rtcp-avpf-non-compound-00.txt
>=20
> I have been asked to provide a review of=20
> draft-johansson-avt-rtcp-avpf-non-compound-00.txt
>=20
> I won't repeat John's points in my review (some of which I share).
>=20
> I also understand the motivation for the work (which we have=20
> taken into close consideration when doing AVPF in the first=20
> place, where we decided to keep the basic packet structure,=20
> even though wireless environments were one of our concerns). =20
> To this end, the motivation is still fairly abstract (packet=20
> loss increasing with size, sure, but you still got link layer=20
> units) concerning what it is to be signalled.
>=20
> Most importantly, however, I am opposed to making this a WG=20
> item, primarily on an architectural basis (other than that,=20
> you can engineer anything and make it kind of work).
>=20
> Given the considerations in section 4, I do not see how the=20
> first sentence of section 5 immediately follows:
> "Based on the above analysis it seems feasible to allow=20
> transmission in RTCP under some restrictions."
>=20
> Technically:
>=20
> We have plenty of RTP deployment out there and RTP has been=20
> the constant in the change of signaling protocols, primary=20
> usages, and the like.  We have seen uses for stream quality=20
> monitoring and the like that are dependent on the general=20
> availability of RTCP information.
The intention is not to exclude compound RTCP, rather the intention is
to ensure that eg. adaptation feedback is transmitted with a low
probability  if packet loss even under bad channel conditions and this
is to be achieved by means of non-compound RTCP

> I believe that it is an important and desirable property for=20
> RTCP packets to be detectable and interpretable independent=20
> of the signaling channel.  This is what section
> 4 of the draft describes.  Signaling which types of RTCP=20
> packets will be used, will not reach such devices and will=20
> not help old receivers as the authors point out.
The signaling is intended for endpoints, it is true the devices in the
network cannot be assumed to understand such signaling, therefore
section 5 states that implicit verification of the delivery  of
non-compound RTCP should be performed. If this verification fails
compound RTCP should be transmitted instead. Also I must admit that I am
a bit puzzled by the rule that an RTCP packet must look in a specific
way and contain a specified number of mandatory blocks, in my opinion it
should suffice that the payload type is valid, but I guess I need to be
enlightened. Also one must remember that non-compound RTCP is already
employed in OMA-PoC.
=20
> Architecturally:
>=20
> We are looking at an optimization problem here.  We are=20
> trying to optimizing behavior across a single wireless link=20
> (or two wireless links connected via some core).  While=20
> saving bits on a wireless link is a desirable goal, it is=20
> specific to this link layer technology -- and those come and=20
> go.  It is not obvious why any other device in the Internet=20
> should be bothered by this very problem to motivate a change=20
> at the RTCP level.
>=20
> Remember: it is already sufficiently hard to get people=20
> implement RTCP to begin with.  We should not make it harder=20
> by suddenly allowing multiple flavors of it (one specific use=20
> of which defeats the general usefulness of RTCP).
>=20
> So, if we have two devices communicating in a specific=20
> wireless environment, where all kinds of optimizations are=20
> already carried out between a base station and the mobile=20
> equipment, why not treat this problem at this very place=20
> where it belongs?  This feels like another specific=20
> optimization useful on one particular link and should not=20
> impact the rest of the Internet.
One could always argue in this direction. Problem is however that in
order to achieve a maximum throughput in terms of Mbits/Hz/s some
optimizations are needed and large RTCP packets impose a problem in that
aspect. If the systems are made less optimized this problem is lesser
but this comes at a cost of reduced coverage/capacity and eventually
less revenue for operator or higher cost for the user. I don't believe
that this is a 3GPP problem as the law of physics applies to all
wireless access technologies. Some access technologies might not
experience this problem are they may be hidden by e.g large
packetization overhead.
=20
> Summary:
>=20
> Assuming some more sound motivation (and pointing out=20
> applications usages that are in line with the scope of AVPF),=20
> I buy into the basic problem.  Yet, I believe AVT is the=20
> wrong place to solve it as this is link-specific and hence=20
> should be done elsewhere.
I understand the "above the wire, below the application" argument, still
I believe that we must see the link-layer problems to some extent.

Regards
Ingemar


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



From avt-bounces@ietf.org Tue Feb 20 08:22:57 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJUwY-00016t-4z; Tue, 20 Feb 2007 08:22:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJQVA-0006rY-Co
	for avt@ietf.org; Tue, 20 Feb 2007 03:37:32 -0500
Received: from keskus.netlab.hut.fi ([130.233.154.176] helo=smtp.netlab.hut.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJQV9-0002i2-1Q
	for avt@ietf.org; Tue, 20 Feb 2007 03:37:32 -0500
Received: from [127.0.0.1] (keskus.netlab.hut.fi [130.233.154.176])
	by smtp.netlab.hut.fi (Postfix) with ESMTP id B154E4FF10;
	Tue, 20 Feb 2007 10:37:24 +0200 (EET)
Message-ID: <45DAB333.9000806@netlab.hut.fi>
Date: Tue, 20 Feb 2007 10:37:07 +0200
From: Joerg Ott <jo@netlab.tkk.fi>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortel.com>
References: <45D3155E.4040301@nortel.com>
In-Reply-To: <45D3155E.4040301@nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
X-Mailman-Approved-At: Tue, 20 Feb 2007 08:22:04 -0500
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	John Lazzaro <lazzaro@eecs.berkeley.edu>,
	Roni Even <roni.even@polycom.co.il>, IETF AVT WG <avt@ietf.org>,
	Joerg Ott <jo@netlab.tkk.fi>, ingemar.s.johansson@ericsson.com,
	Colin Perkins <csp@csperkins.org>
Subject: [AVT] Re: Review of
	draft-johansson-avt-rtcp-avpf-non-compound-00.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

I have been asked to provide a review of
draft-johansson-avt-rtcp-avpf-non-compound-00.txt

I won't repeat John's points in my review (some of which I
share).

I also understand the motivation for the work (which we
have taken into close consideration when doing AVPF in
the first place, where we decided to keep the basic packet
structure, even though wireless environments were one
of our concerns).  To this end, the motivation is still
fairly abstract (packet loss increasing with size, sure,
but you still got link layer units) concerning what it
is to be signalled.

Most importantly, however, I am opposed to making this a
WG item, primarily on an architectural basis (other than
that, you can engineer anything and make it kind of work).

Given the considerations in section 4, I do not see how the
first sentence of section 5 immediately follows:
"Based on the above analysis it seems feasible to allow
transmission in RTCP under some restrictions."

Technically:

We have plenty of RTP deployment out there and RTP has been
the constant in the change of signaling protocols, primary
usages, and the like.  We have seen uses for stream quality
monitoring and the like that are dependent on the general
availability of RTCP information.

I believe that it is an important and desirable property
for RTCP packets to be detectable and interpretable
independent of the signaling channel.  This is what section
4 of the draft describes.  Signaling which types of RTCP
packets will be used, will not reach such devices and will
not help old receivers as the authors point out.

Architecturally:

We are looking at an optimization problem here.  We are trying
to optimizing behavior across a single wireless link (or two
wireless links connected via some core).  While saving bits
on a wireless link is a desirable goal, it is specific to this
link layer technology -- and those come and go.  It is not
obvious why any other device in the Internet should be bothered
by this very problem to motivate a change at the RTCP level.

Remember: it is already sufficiently hard to get people implement
RTCP to begin with.  We should not make it harder by suddenly
allowing multiple flavors of it (one specific use of which defeats
the general usefulness of RTCP).

So, if we have two devices communicating in a specific wireless
environment, where all kinds of optimizations are already carried
out between a base station and the mobile equipment, why not treat
this problem at this very place where it belongs?  This feels like
another specific optimization useful on one particular link and
should not impact the rest of the Internet.

Summary:

Assuming some more sound motivation (and pointing out applications
usages that are in line with the scope of AVPF), I buy into the
basic problem.  Yet, I believe AVT is the wrong place to solve it
as this is link-specific and hence should be done elsewhere.

Regards,
Joerg



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



From avt-bounces@ietf.org Tue Feb 20 10:54:55 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJXJ7-0008Nk-IJ; Tue, 20 Feb 2007 10:53:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJXJ6-0008Nf-Jp
	for avt@ietf.org; Tue, 20 Feb 2007 10:53:32 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJXIv-0001mV-Os
	for avt@ietf.org; Tue, 20 Feb 2007 10:53:32 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	0FCC820751; Tue, 20 Feb 2007 16:53:17 +0100 (CET)
X-AuditID: c1b4fb3c-affc8bb0000007de-73-45db196c518a 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	E3943204A4; Tue, 20 Feb 2007 16:53:16 +0100 (CET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 20 Feb 2007 16:53:16 +0100
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 20 Feb 2007 16:53:16 +0100
Message-ID: <45DB196C.3010908@ericsson.com>
Date: Tue, 20 Feb 2007 16:53:16 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Franceschini Guido <guido.franceschini@telecomitalia.it>
Subject: Re: R: [AVT] CCM draft review
	--	should"bandwidth"includetheheaderoverhead
References: <E9D1028EC5C22B418B5D54CA6EA27C579A5E76@PTPEVS108BA020.idc.cww.telecomitalia.it>
	<45D9D410.2070506@ericsson.com>
	<E9D1028EC5C22B418B5D54CA6EA27C579A5E86@PTPEVS108BA020.idc.cww.telecomitalia.it>
In-Reply-To: <E9D1028EC5C22B418B5D54CA6EA27C579A5E86@PTPEVS108BA020.idc.cww.telecomitalia.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Feb 2007 15:53:16.0261 (UTC)
	FILETIME=[3BF85150:01C75507]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Franceschini Guido skrev:
> Dear Magnus, all,
> 
> IMHO all the issues being described so far can be reduced to the problem of making the sender aware of the bottlenecks it shall respect. Thus, if we identify a suitable characterization of the bottleneck(s), then we are done (in terms of signalling).
> Depending on the different cases, as you show, bottlenecks can be more effectively characterized by the media bitrate, or by the IP gross bitrate. Plus possibly additional params such as average overhead and/or packet rate.
> 
> Then the problem I see you are debating is: which choice is better? or, which choice has the least downsides? This derives from the assumption (which has become a constraint) that either one or the other metric should be used. I think this can be relaxed.

Yes, I would like us (the WG) to determine which choice is the best, or 
at least has the least downsides. And yes, I would like to have one 
defined format to avoid combinatorial explosion within the 
implementations if one would allow to measure things at various layers 
and then have the receiver of the request work things out.

I would also like to come to a conclusion on this prior to the IETF 
meeting, preferably before the draft cut-off date in two weeks time.

> 
> If we define metrics that are generic and neutral, and that can represent either the media bitrate or the IP gross rate or even the bandwidth as measured at some other layer, than what would be the cons?
> 
> To be more practical, I try to review your Mixer scenario, and to show how my proposal would adapt to it.
> My proposal, in essence, consists in always providing a tuple made of <available bandwidth measured at layer X, average per packet overhead measured at the same layer X>, and having the sender collect all the information about bottlenecks so as to determine how to generate traffic that fits all constraints.

I think you are unclear about how one define overhead in your proposal. 
 From what layer to what layer are considered overhead. Looking at the 
below example your overhead seem to be from the lowest IP layer up to 
the RTP payload.

> 
> 
> Scenario A, the mixer
> 
> Suppose the mixer received information about the bottleneck towards receiver D (BottD = <TIDC_D, MPO_D>): it could simply propagate that same bottleneck info to the A, B and C senders. Then the traffic generated by each of them would comply with the constraints in the path to D, although A, B and C might have chosen different encoding and transmission parameters.
> 
> With numbers:
> BottD = <21000, 40>
> A chooses to generate AMR at 4750, with 20 ms per packet (50 pkt/sec)
> ==> with respect to D metrics A generates 50*40*8=16000 bit/s of overhead + 4750 of payload (total of 20750 < 21000)
> 
> B chooses to generate AMR at 12200, with 40 ms per packet (25 pkt/sec)
> ==> with respect to D metrics B generates 25*40*8=8000 bit/s of overhead + 12200 of payload (total of 20200 < 21000)
> 
> C chooses ....
> 
> Suppose than that receiver C as well has a bottleneck, but has a different stack (e.g. a VPN that duplicates the IP layer)
> 
> Then C could notify such bottleneck BottC to the Mixer, and this could be again propagated to the A, B and D senders.
> 
> With numbers:
> BottD = <21000, 40>
> BottC = <25000, 60>
> If the same choices as before were kept:
> A would generate AMR at 4750, with 20 ms per packet (50 pkt/sec)
> ==> with respect to D metrics A generates 50*40*8=16000 bit/s of overhead + 4750 of payload (total of 20750 < 21000)
> ==> with respect to C metrics A generates 50*60*8=24000 bit/s of overhead + 4750 of payload (total of 28750 > 25000) NOT OK
> 
> B would generate AMR at 12200, with 40 ms per packet (25 pkt/sec)
> ==> with respect to D metrics B generates 25*40*8=8000 bit/s of overhead + 12200 of payload (total of 20200 < 21000)
> ==> with respect to C metrics B generates 25*60*8=12000 bit/s of overhead + 12200 of payload (total of 24200 < 25000) STILL OK
> 
> By means of collecting the bottleneck info, in such a case the sender A will decide to change its encoding/transmitter parameters, while sender B would take no action.
> 
> Now suppose receiver A has a bottleneck too, but its stack is of a yet different nature, since it resides in a H323 branch. Here the media bitrate is more meaningful than any other measurement, thus it would communicate its bottleneck characterization providing the media codec layer measurements:
> BottA = <8000,0>
> 
> I.e., it tells the Mixer that it can receive up to 8000 bit/sec of audio, irrespective of the packetization scheme in use (the overhead is 0 at this layer).
> The Mixer would once again propagate this information to the B, C and D sender which in turn will determine their encoding and transmission parameters matching all bottleneck constraints. Etc, etc etc.
> 
> Now also receiver B communicates a bottleneck. B is behind a NAPT that maps IPV4 to IPV6, i.e. B runs an IPV6 stack.
> Once again, B will communicate its BottB tuple, which will contain yet another overhead figure. And the Mixer will propagate the BottB information to senders A, C and D, which in turn will determine their encoding and transmission parameters matching all bottleneck constraints. Etc, etc etc.
> 
> Comments?
> 

Assuming I interpret this correct, you would support a TMMBR proposal 
that encodes the following information:

1. The maximum bit-rate as seen on lowest common networking layer. In 
the case of IP, the maximum bit-rate available at the lowest visible IP 
layer, i.e. excluding link layer headers.

2. The average measurement of the number of bytes present in each packet 
from the start of the first IP header until the start of the RTP 
payload. Which represents the header overhead in bytes for each packet 
from the lowest visible IP header to the RTP payload. This value is 
measured for each received packet and the value reported is filtered by 
for each packet doing the following calculation:
avg_packet_overhead = 15/16*avg_packet_overhead + 1/16 * packet_overhead

As Guido present above there is an issue with using a tuple. Only 
allowing a mixer to forward a single tuple for TMMBR can result in that 
some combinations will not be okay depending on the packet rate 
selected. Thus there may be need to include multiple tuple to correctly 
restrict the space of possible combinations. I need to think more about 
what the relations are between selecting a packet rate and provided 
values of bit-rate and overhead.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



From avt-bounces@ietf.org Tue Feb 20 12:40:57 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJYxh-0006H1-OQ; Tue, 20 Feb 2007 12:39:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJYxg-0006Gj-4Z
	for avt@ietf.org; Tue, 20 Feb 2007 12:39:32 -0500
Received: from maild.telecomitalia.it ([156.54.233.30])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJYxa-0003yg-6j
	for avt@ietf.org; Tue, 20 Feb 2007 12:39:32 -0500
Received: from ptpxch009ba020.idc.cww.telecomitalia.it ([156.54.240.52]) by
	maild.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830);
	Tue, 20 Feb 2007 18:39:25 +0100
Received: from PTPEVS108BA020.idc.cww.telecomitalia.it ([156.54.241.227]) by
	ptpxch009ba020.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 20 Feb 2007 18:39:24 +0100
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Importance: normal
Priority: normal
Content-Transfer-Encoding: quoted-printable
Subject: RE: R: [AVT] CCM draft review
	--	should"bandwidth"includetheheaderoverhead
Date: Tue, 20 Feb 2007 18:39:22 +0100
Message-ID: <E9D1028EC5C22B418B5D54CA6EA27C579A5E90@PTPEVS108BA020.idc.cww.telecomitalia.it>
In-Reply-To: <45DB196C.3010908@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: R: [AVT] CCM draft review
	--	should"bandwidth"includetheheaderoverhead
thread-index: AcdVBz3Ox32/cs1CRn6PnWKZtOREUgAA7LOw
From: "Franceschini Guido" <guido.franceschini@telecomitalia.it>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-OriginalArrivalTime: 20 Feb 2007 17:39:24.0642 (UTC)
	FILETIME=[0FD22420:01C75516]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2b2ad76aced9b1d558e34a970a85c027
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Dear Magnus, all,

some more comment inline.

Best regards
Guido

<snip>
=20
> > To be more practical, I try to review your Mixer scenario,=20
> and to show how my proposal would adapt to it.
> > My proposal, in essence, consists in always providing a=20
> tuple made of <available bandwidth measured at layer X,=20
> average per packet overhead measured at the same layer X>,=20
> and having the sender collect all the information about=20
> bottlenecks so as to determine how to generate traffic that=20
> fits all constraints.
>=20
> I think you are unclear about how one define overhead in your=20
> proposal.=20
>  From what layer to what layer are considered overhead.=20
> Looking at the=20
> below example your overhead seem to be from the lowest IP layer up to=20
> the RTP payload.

You are correct in saying that in my analysis of the Mixer scenario I =
was not fully precise.
Indeed, I computed the overhead exactly as you described (from the =
lowest IP up to RTP included): I did so to avoid adding too many details =
in the analisys. My calculation was therefore non perfectly accurate, =
depending on the stack protocol below the IP layer. Actually, my =
intention was mostly to show the concept that a sender should collect =
all bottlenecks information, and that the metrics I propose are =
compatible with a variety of different stacks. Which is the key =
advantage over picking up the media-bitrate or the IP-gross rate. I =
tried to provide a convincing example that 4 different protocol stacks =
can be managed uniformely by means of tuples that -although each =
potentially referring to a different layer X- are neutral in practice, =
something that cannot be achieved if either the media-bitrate or the =
IP-gross rate is signaled.

>=20
> >=20
> >=20
> > Scenario A, the mixer
> >=20
> > Suppose the mixer received information about the bottleneck=20
> towards receiver D (BottD =3D <TIDC_D, MPO_D>): it could simply=20
> propagate that same bottleneck info to the A, B and C=20
> senders. Then the traffic generated by each of them would=20
> comply with the constraints in the path to D, although A, B=20
> and C might have chosen different encoding and transmission=20
> parameters.
> >=20
> > With numbers:
> > BottD =3D <21000, 40>
> > A chooses to generate AMR at 4750, with 20 ms per packet=20
> (50 pkt/sec)
> > =3D=3D> with respect to D metrics A generates 50*40*8=3D16000=20
> bit/s of overhead + 4750 of payload (total of 20750 < 21000)
> >=20
> > B chooses to generate AMR at 12200, with 40 ms per packet=20
> (25 pkt/sec)
> > =3D=3D> with respect to D metrics B generates 25*40*8=3D8000=20
> bit/s of overhead + 12200 of payload (total of 20200 < 21000)
> >=20
> > C chooses ....
> >=20
> > Suppose than that receiver C as well has a bottleneck, but=20
> has a different stack (e.g. a VPN that duplicates the IP layer)
> >=20
> > Then C could notify such bottleneck BottC to the Mixer, and=20
> this could be again propagated to the A, B and D senders.
> >=20
> > With numbers:
> > BottD =3D <21000, 40>
> > BottC =3D <25000, 60>
> > If the same choices as before were kept:
> > A would generate AMR at 4750, with 20 ms per packet (50 pkt/sec)
> > =3D=3D> with respect to D metrics A generates 50*40*8=3D16000=20
> bit/s of overhead + 4750 of payload (total of 20750 < 21000)
> > =3D=3D> with respect to C metrics A generates 50*60*8=3D24000=20
> bit/s of overhead + 4750 of payload (total of 28750 > 25000) NOT OK
> >=20
> > B would generate AMR at 12200, with 40 ms per packet (25 pkt/sec)
> > =3D=3D> with respect to D metrics B generates 25*40*8=3D8000=20
> bit/s of overhead + 12200 of payload (total of 20200 < 21000)
> > =3D=3D> with respect to C metrics B generates 25*60*8=3D12000=20
> bit/s of overhead + 12200 of payload (total of 24200 < 25000) STILL OK
> >=20
> > By means of collecting the bottleneck info, in such a case=20
> the sender A will decide to change its encoding/transmitter=20
> parameters, while sender B would take no action.
> >=20
> > Now suppose receiver A has a bottleneck too, but its stack=20
> is of a yet different nature, since it resides in a H323=20
> branch. Here the media bitrate is more meaningful than any=20
> other measurement, thus it would communicate its bottleneck=20
> characterization providing the media codec layer measurements:
> > BottA =3D <8000,0>
> >=20
> > I.e., it tells the Mixer that it can receive up to 8000=20
> bit/sec of audio, irrespective of the packetization scheme in=20
> use (the overhead is 0 at this layer).
> > The Mixer would once again propagate this information to=20
> the B, C and D sender which in turn will determine their=20
> encoding and transmission parameters matching all bottleneck=20
> constraints. Etc, etc etc.
> >=20
> > Now also receiver B communicates a bottleneck. B is behind=20
> a NAPT that maps IPV4 to IPV6, i.e. B runs an IPV6 stack.
> > Once again, B will communicate its BottB tuple, which will=20
> contain yet another overhead figure. And the Mixer will=20
> propagate the BottB information to senders A, C and D, which=20
> in turn will determine their encoding and transmission=20
> parameters matching all bottleneck constraints. Etc, etc etc.
> >=20
> > Comments?
> >=20
>=20
> Assuming I interpret this correct, you would support a TMMBR proposal=20
> that encodes the following information:
>=20
> 1. The maximum bit-rate as seen on lowest common networking layer. In=20
> the case of IP, the maximum bit-rate available at the lowest=20
> visible IP=20
> layer, i.e. excluding link layer headers.

Mmmm, your definition does not really matches my intention.

I try to explain: suppose we have a stack (at a receiver) including =
RTP/UDP/IP/PPP/LAPM. Suppose the physical gross bandwidth is 40 Kbit/s =
(in downlink).
The RTP, UDP, IP and PPP layers are packet-oriented, and add a =
per-packet overhead (12, 8, 20, 8 bytes respectively), whereas the LAPM =
layer is byte-oriented and adds a per-byte overhead (say a 10% =
overhead).
If we measure bandwidth and overhead at the point at which the protocol =
stack portion providing per-packet overhead interfaces with the protocol =
stack portion providing per-byte overhead, we have a precise =
characterization.

   TIDC(PPP) =3D 36 (=3D 40 - 10%)
   MPOD(PPP) =3D 48 (=3D 12(RTP)+8(UDP)+20(IP)+8(PPP))
   =20
If we measure bandwidth and overhead in other points of the stack, we =
also need to make a guess about the packet rate. Here are various other =
possible tuples, for other layers and under the hypothesys of 50 and 25 =
packets/sec:=20
   =20
   TIDC(IP,50) =3D 33  (=3D 36 Kbit/s - 8*8*50 bit/sec)
   MPOD(IP) =3D 40     (=3D 12+8+20)
   =20
   TIDC(UDP,50) =3D 25 (=3D 36 Kbit/s - 28*8*50 bit/sec)
   MPOD(UDP) =3D 20    (=3D 12+8)
   =20
   TIDC(RTP,50) =3D 22 (=3D 36 Kbit/s - 36*8*50 bit/sec)
   MPOD(RTP) =3D 12    (=3D 12)
   =20
   TIDC(APP,50) =3D 17 (=3D 36 Kbit/s - 48*8*50 bit/sec)
   MPOD(APP) =3D 0=20
   =20
   TIDC(IP,25) =3D 34  (=3D 36 Kbit/s - 8*8*25 bit/sec)
   MPOD(IP) =3D 40=20
   =20
   TIDC(UDP,25) =3D 30 (=3D 36 Kbit/s - 28*8*25 bit/sec)
   MPOD(UDP) =3D 20=20
   =20
   TIDC(RTP,25) =3D 29 (=3D 36 Kbit/s - 36*8*25 bit/sec)
   MPOD(RTP) =3D 12=20
   =20
   TIDC(APP,25) =3D 26 (=3D 36 Kbit/s - 48*8*25 bit/sec)
   MPOD(APP) =3D 0=20

It is clear that inaccurate packet-rate guesses determine inaccurate =
TIDC values, and that this effect is huge at the APP level, but reduced =
at the IP level, for such a stack example.
Nevertheless, if the receiver communicates the tuple computed at the PPP =
layer, it does the best job.

Thus, my definition would better be:

1. The maximum bit-rate as seen on lowest packet-oriented layer (said =
layer X).

2. The average measurement of the number of bytes present in each packet =
from the start of the first layer X header until the start of the RTP =
payload, plus the number of bytes present in each packet from the end of =
the RTP payload to the end of the layer X trailer (if any). Etc etc etc. =
I am fine with your overhead measurement criteria, that -I understand- =
is meant to determine the average performance of a possible compression =
scheme.
=20
> 2. The average measurement of the number of bytes present in=20
> each packet=20
> from the start of the first IP header until the start of the RTP=20
> payload. Which represents the header overhead in bytes for=20
> each packet=20
> from the lowest visible IP header to the RTP payload. This value is=20
> measured for each received packet and the value reported is=20
> filtered by=20
> for each packet doing the following calculation:
> avg_packet_overhead =3D 15/16*avg_packet_overhead + 1/16 *=20
> packet_overhead
>=20
> As Guido present above there is an issue with using a tuple. Only=20
> allowing a mixer to forward a single tuple for TMMBR can=20
> result in that=20
> some combinations will not be okay depending on the packet rate=20
> selected. Thus there may be need to include multiple tuple to=20
> correctly=20
> restrict the space of possible combinations. I need to think=20
> more about=20
> what the relations are between selecting a packet rate and provided=20
> values of bit-rate and overhead.
>=20
> Cheers
>=20
> Magnus Westerlund
>=20
> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>=20
--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons =
above and may contain confidential information. If you have received the =
message in error, be informed that any use of the content hereof is =
prohibited. Please return it immediately to the sender and delete the =
message. Should you have any questions, please contact us by replying to =
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                       =20

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



From avt-bounces@ietf.org Tue Feb 20 13:58:56 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJaB9-0006JJ-3B; Tue, 20 Feb 2007 13:57:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJaB7-0006J6-Ss
	for avt@ietf.org; Tue, 20 Feb 2007 13:57:29 -0500
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJaB6-0002wG-Cj
	for avt@ietf.org; Tue, 20 Feb 2007 13:57:29 -0500
Received: from relay8.apple.com (a17-128-113-38.apple.com [17.128.113.38])
	by mail-out3.apple.com (8.13.8/8.13.8) with ESMTP id l1KIvPHG028314;
	Tue, 20 Feb 2007 10:57:25 -0800 (PST)
Received: from relay8.apple.com (unknown [127.0.0.1])
	by relay8.apple.com (Symantec Mail Security) with ESMTP id 8A70F404E3; 
	Tue, 20 Feb 2007 10:57:25 -0800 (PST)
X-AuditID: 11807126-9dfcabb00000685d-c4-45db449579c4 
Received: from [17.202.35.52] (unknown [17.219.215.32])
	by relay8.apple.com (Apple SCV relay) with ESMTP id 2AD5A40477;
	Tue, 20 Feb 2007 10:57:25 -0800 (PST)
Mime-Version: 1.0
Message-Id: <p06230963c200e927c7fc@[17.202.35.52]>
In-Reply-To: <45DA67F7.5090108@nortel.com>
References: <45DA67F7.5090108@nortel.com>
Date: Tue, 20 Feb 2007 10:56:30 -0800
To: Tom-PT Taylor <taylor@nortel.com>, Hari Desineni <hd@qualcomm.com>
From: Dave Singer <singer@apple.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: avt@ietf.org
Subject: [AVT] Re: draft-ietf-avt-rtp-hdrext-09.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

At 22:16  -0500 19/02/07, Tom-PT Taylor wrote:
>I write this in some embarrassment for the lateness of the day.
>First: the direction attribute is supposed to be optional. That 
>means ("/" direction) should be ["/" direction], as it is in section 
>5.
>
>Second: the existing specification of mapattrs makes a space 
>mandatory at the end of the a=extmap line if there are no extension 
>attributes. This is because the expression
>
>   (space extensionattributes)
>
>evaluates to (space) if extensionattributes is a null string. You 
>get what you want by using square brackets around the above 
>expression instead of parentheses.

thanks.  not an abnf expert, myself...

>
>Now that the draft needs fixing anyway, here are my nits. These can 
>be ignored if you don't have time to follow up.
>
>1. The abstract mildly contradicts the IANA considerations, in that 
>it says flatly that extensions are unregistered. May I suggest 
>saying instead: "in general unregistered" or "unregistered except 
>for those defined by the IETF", with the latter perhaps preferred?

actually, any body could make a registration authority for their URN 
space, so I said "registration is de-centralized".

>
>2. Drop "to" at the end of the first line of the Introduction.

done

>
>3. I don't understand the one-sentence paragraph at the end of the 
>Introduction. What "value"? Are you really saying:
>
>"This specification applies to extensions of the RTP/AVP profile."
>
>or is the sentence misplaced?

the word "value" seems mis-placed.  deleted.

>
>4. In section 4, I would rephrase:
>
>"The 4-bit length is the length minus one of the data bytes of this
>    header extension element (excluding this one-byte header)."
>
>to read instead:
>
>"The 4-bit length is the number minus one of data bytes of this
>    header extension element following the one-byte header."

ok

>5. In section 6, second paragraph (immediately after the bullets), I 
>think the first occurrence of the word "may" should be an RFC 2119 
>"MAY", and the second occurrence should be an RFC 2119 "MUST":
>
>"A direction attribute MAY be included in an extmap ..." and
>
>"The direction MUST be one of ...".

done

>
>6. The last paragraph on page 10 before the example reads:
>
>"Note that either party may include extensions in the stream other
>    than those negotiated, or those negotiated as "inactive", for example
>    for the benefit of intermediate nodes.  Only extensions with an
>    identifier in the range 1-14, and with a declaration, can be sent."
>
>In that last line, "and with a declaration" seems to contradict 
>"other than those negotiated" in the preceding lines. What is meant 
>here? I also think that "may" in the first line should be an RFC 
>2119 "MAY".

Ok, "MAY" changed.  The point of the last sentence is that even if 
you don't offer to receive an extension, I might send it;  but if I 
send it, I have to include its declaration.

How about

<t>Either party MAY include extensions in the stream other than those 
offered, for example for the benefit of intermediate nodes.  For the 
RTP packets to include the extension, it must have been declared with 
an identifier in the range 1-14.</t>

?


-- 
David Singer
Apple Computer/QuickTime

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



From avt-bounces@ietf.org Tue Feb 20 14:48:58 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJay2-0006nu-Pz; Tue, 20 Feb 2007 14:48:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJay1-0006nj-Sw
	for avt@ietf.org; Tue, 20 Feb 2007 14:48:01 -0500
Received: from zrtps0kp.nortel.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJaxz-0006OU-JQ
	for avt@ietf.org; Tue, 20 Feb 2007 14:48:01 -0500
Received: from zcarhxs1.corp.nortel.com (zcarhxs1.corp.nortel.com
	[47.129.230.89])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l1KJlip27373; Tue, 20 Feb 2007 14:47:44 -0500 (EST)
Received: from [47.130.16.66] ([47.130.16.66] RDNS failed) by
	zcarhxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 20 Feb 2007 14:47:40 -0500
Message-ID: <45DB5048.7020003@nortel.com>
Date: Tue, 20 Feb 2007 14:47:20 -0500
From: "Tom-PT Taylor" <taylor@nortel.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Dave Singer <singer@apple.com>
References: <45DA67F7.5090108@nortel.com>
	<p06230963c200e927c7fc@[17.202.35.52]>
In-Reply-To: <p06230963c200e927c7fc@[17.202.35.52]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Feb 2007 19:47:40.0923 (UTC)
	FILETIME=[FB296CB0:01C75527]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: avt@ietf.org, Hari Desineni <hd@qualcomm.com>
Subject: [AVT] Re: draft-ietf-avt-rtp-hdrext-09.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Just one open item at the end.

Dave Singer wrote:
> At 22:16  -0500 19/02/07, Tom-PT Taylor wrote:
...
> 
>> 6. The last paragraph on page 10 before the example reads:
>>
>> "Note that either party may include extensions in the stream other
>>    than those negotiated, or those negotiated as "inactive", for example
>>    for the benefit of intermediate nodes.  Only extensions with an
>>    identifier in the range 1-14, and with a declaration, can be sent."
>>
>> In that last line, "and with a declaration" seems to contradict 
>> "other than those negotiated" in the preceding lines. What is meant 
>> here? I also think that "may" in the first line should be an RFC 
>> 2119 "MAY".
> 
> Ok, "MAY" changed.  The point of the last sentence is that even if 
> you don't offer to receive an extension, I might send it;  but if I 
> send it, I have to include its declaration.
> 
> How about
> 
> <t>Either party MAY include extensions in the stream other than those 
> offered, for example for the benefit of intermediate nodes.  For the 
> RTP packets to include the extension, it must have been declared with 
> an identifier in the range 1-14.</t>
> 
> ?
> 
> 
[PTT] I'm left to infer from this that the declaration happens in the 
answer, since the first sentence says it wasn't in the offer. Is this 
what you intended?

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



From avt-bounces@ietf.org Tue Feb 20 17:36:41 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJdaG-0007hg-Iq; Tue, 20 Feb 2007 17:35:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJdaF-0007gk-E4
	for avt@ietf.org; Tue, 20 Feb 2007 17:35:39 -0500
Received: from whisker.bluecoat.com ([216.52.23.28])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJdaC-0001eg-Ob
	for avt@ietf.org; Tue, 20 Feb 2007 17:35:39 -0500
Received: from bcs-mail2.internal.cacheflow.com
	(bcs-mail2.internal.cacheflow.com [10.2.2.59])
	by whisker.bluecoat.com (8.13.8/8.13.8) with ESMTP id l1KMZYPM001598;
	Tue, 20 Feb 2007 14:35:34 -0800 (PST)
Received: from webmail.internal.cacheflow.com ([216.52.23.20]) by
	bcs-mail2.internal.cacheflow.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 20 Feb 2007 14:35:30 -0800
Received: from [10.2.4.50] ([10.2.4.50]) by webmail.internal.cacheflow.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 20 Feb 2007 14:35:29 -0800
Message-ID: <45DB77B0.5010700@bluecoat.com>
Date: Tue, 20 Feb 2007 14:35:28 -0800
From: Ron Frederick <ronf@bluecoat.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Dave Singer <singer@apple.com>
Subject: Re: [AVT] Re: draft-ietf-avt-rtp-hdrext-09.txt
References: <45DA67F7.5090108@nortel.com>
	<p06230963c200e927c7fc@[17.202.35.52]>
In-Reply-To: <p06230963c200e927c7fc@[17.202.35.52]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Feb 2007 22:35:29.0797 (UTC)
	FILETIME=[6CADAB50:01C7553F]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Dave Singer wrote:
> At 22:16  -0500 19/02/07, Tom-PT Taylor wrote:
>> 4. In section 4, I would rephrase:
>>
>> "The 4-bit length is the length minus one of the data bytes of this
>>    header extension element (excluding this one-byte header)."
>>
>> to read instead:
>>
>> "The 4-bit length is the number minus one of data bytes of this
>>    header extension element following the one-byte header."
> 
> ok

Since the discussion got reopened, was there ever a reply to the review 
comment that we should allow for zero-length elements here, as 
effectively "boolean" value where their presence was enough to indicate 
something? I actually like that idea, and think that's useful enough to 
justify reducing the maximum length to 15 bytes (from 16). It also 
happens to clean up something that I suspect a lot of people will likely 
implement wrong, by eliminating the need to remember to subtract one 
from the length before encoding it.
-- 
Ron Frederick
ronf@bluecoat.com

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



From avt-bounces@ietf.org Tue Feb 20 17:45:25 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJdip-0003X2-Hh; Tue, 20 Feb 2007 17:44:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJdio-0003Wx-E6
	for avt@ietf.org; Tue, 20 Feb 2007 17:44:30 -0500
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJdin-00034K-2Y
	for avt@ietf.org; Tue, 20 Feb 2007 17:44:30 -0500
Received: from relay8.apple.com (relay8.apple.com [17.128.113.38])
	by mail-out4.apple.com (8.13.8/8.13.8) with ESMTP id l1KMiRjs018413;
	Tue, 20 Feb 2007 14:44:27 -0800 (PST)
Received: from relay8.apple.com (unknown [127.0.0.1])
	by relay8.apple.com (Symantec Mail Security) with ESMTP id 61E66404EF; 
	Tue, 20 Feb 2007 14:44:27 -0800 (PST)
X-AuditID: 11807126-9bfc6bb00000685d-93-45db79cae354 
Received: from [17.202.35.52] (Vpn2priv-152.apple.com [17.219.204.152])
	by relay8.apple.com (Apple SCV relay) with ESMTP id B92C840477;
	Tue, 20 Feb 2007 14:44:26 -0800 (PST)
Mime-Version: 1.0
Message-Id: <p0623096fc2012981a148@[17.202.35.52]>
In-Reply-To: <45DB77B0.5010700@bluecoat.com>
References: <45DA67F7.5090108@nortel.com>
	<p06230963c200e927c7fc@[17.202.35.52]> <45DB77B0.5010700@bluecoat.com>
Date: Tue, 20 Feb 2007 14:43:56 -0800
To: Ron Frederick <ronf@bluecoat.com>
From: Dave Singer <singer@apple.com>
Subject: Re: [AVT] Re: draft-ietf-avt-rtp-hdrext-09.txt
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

At 14:35  -0800 20/02/07, Ron Frederick wrote:
>Dave Singer wrote:
>>At 22:16  -0500 19/02/07, Tom-PT Taylor wrote:
>>>4. In section 4, I would rephrase:
>>>
>>>"The 4-bit length is the length minus one of the data bytes of this
>>>    header extension element (excluding this one-byte header)."
>>>
>>>to read instead:
>>>
>>>"The 4-bit length is the number minus one of data bytes of this
>>>    header extension element following the one-byte header."
>>
>>ok
>
>Since the discussion got reopened, was there ever a reply to the 
>review comment that we should allow for zero-length elements here, 
>as effectively "boolean" value where their presence was enough to 
>indicate something? I actually like that idea, and think that's 
>useful enough to justify reducing the maximum length to 15 bytes 
>(from 16). It also happens to clean up something that I suspect a 
>lot of people will likely implement wrong, by eliminating the need 
>to remember to subtract one from the length before encoding it.

Yes, I was keen to allow the storage of 16-byte elements, such as 
UUIDs, SMPTE standard labels, and SMPTE universal material IDs 
(UMIDs).  Since a zero-byte element by itself would take 3 bytes of 
padding, unless there were multiple it wouldn't gain any space, 
anyway, because of the need to pad.  So, given that it probably 
wouldn't often change the packet size, but would awkwardly remove the 
possibility of 16-byte values, I felt that the current design of 
length-1 was the right balance...

-- 
David Singer
Apple Computer/QuickTime

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



From avt-bounces@ietf.org Tue Feb 20 18:12:08 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJe8S-0002Uj-Vc; Tue, 20 Feb 2007 18:11:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJe8S-0002Ue-3V
	for avt@ietf.org; Tue, 20 Feb 2007 18:11:00 -0500
Received: from whisker.bluecoat.com ([216.52.23.28])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJe8Q-000825-ND
	for avt@ietf.org; Tue, 20 Feb 2007 18:11:00 -0500
Received: from bcs-mail2.internal.cacheflow.com
	(bcs-mail2.internal.cacheflow.com [10.2.2.59])
	by whisker.bluecoat.com (8.13.8/8.13.8) with ESMTP id l1KNAv2o005150;
	Tue, 20 Feb 2007 15:10:57 -0800 (PST)
Received: from webmail.internal.cacheflow.com ([216.52.23.20]) by
	bcs-mail2.internal.cacheflow.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 20 Feb 2007 15:10:53 -0800
Received: from [10.2.4.50] ([10.2.4.50]) by webmail.internal.cacheflow.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 20 Feb 2007 15:10:53 -0800
Message-ID: <45DB7FFB.6010504@bluecoat.com>
Date: Tue, 20 Feb 2007 15:10:51 -0800
From: Ron Frederick <ronf@bluecoat.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Dave Singer <singer@apple.com>
Subject: Re: [AVT] Re: draft-ietf-avt-rtp-hdrext-09.txt
References: <45DA67F7.5090108@nortel.com>
	<p06230963c200e927c7fc@[17.202.35.52]>
	<45DB77B0.5010700@bluecoat.com>
	<p0623096fc2012981a148@[17.202.35.52]>
In-Reply-To: <p0623096fc2012981a148@[17.202.35.52]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Feb 2007 23:10:53.0033 (UTC)
	FILETIME=[5E39C590:01C75544]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Dave Singer wrote:
> At 14:35  -0800 20/02/07, Ron Frederick wrote:
>> Dave Singer wrote:
>>> At 22:16  -0500 19/02/07, Tom-PT Taylor wrote:
>>>> 4. In section 4, I would rephrase:
>>>>
>>>> "The 4-bit length is the length minus one of the data bytes of this
>>>>    header extension element (excluding this one-byte header)."
>>>>
>>>> to read instead:
>>>>
>>>> "The 4-bit length is the number minus one of data bytes of this
>>>>    header extension element following the one-byte header."
>>>
>>> ok
>>
>> Since the discussion got reopened, was there ever a reply to the 
>> review comment that we should allow for zero-length elements here, as 
>> effectively "boolean" value where their presence was enough to 
>> indicate something? I actually like that idea, and think that's useful 
>> enough to justify reducing the maximum length to 15 bytes (from 16). 
>> It also happens to clean up something that I suspect a lot of people 
>> will likely implement wrong, by eliminating the need to remember to 
>> subtract one from the length before encoding it.
> 
> Yes, I was keen to allow the storage of 16-byte elements, such as UUIDs, 
> SMPTE standard labels, and SMPTE universal material IDs (UMIDs).  Since 
> a zero-byte element by itself would take 3 bytes of padding, unless 
> there were multiple it wouldn't gain any space, anyway, because of the 
> need to pad.  So, given that it probably wouldn't often change the 
> packet size, but would awkwardly remove the possibility of 16-byte 
> values, I felt that the current design of length-1 was the right balance...

Do we think we'd ever need anything longer? Should we be considering a 
non-linear mapping of the length field? For instance, values 0-7 could 
represent lengths 0-7 as-is, but values 8-15 could be a length of 
(value-4)*2 (allowing lengths of 8, 10, 12, 14, 16, 18, 20, or 22), or 
we could even divide things further and support even longer values, 
mapping 12-15 as (value-8)*4 (making the last four values correspond to 
lengths of 16, 20, 24, and 28). This would be easy to implement either 
as logic or a simple lookup table.

I'm still ok with the current proposal to support lengths of 1-16 and 
just say that these boolean elements should be encoded as 1-byte values, 
but it seems like we have enough bits here to allow both zero-length and 
longer items if that's the only issue. I could imagine getting a lot of 
benefit out of multiple of these zero-length values being packed 
together. Even if you have a mixture of zero-length and non-zero length 
values, not all over those non-zero length values will insist on 
alignment, so you could still get an overall space benefit.
-- 
Ron Frederick
ronf@bluecoat.com

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



From avt-bounces@ietf.org Wed Feb 21 03:51:24 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJnB0-0004me-6z; Wed, 21 Feb 2007 03:50:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJnAz-0004mU-Gi
	for avt@ietf.org; Wed, 21 Feb 2007 03:50:13 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJnAy-0000D7-0H
	for avt@ietf.org; Wed, 21 Feb 2007 03:50:13 -0500
Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l1L8o8o5008382
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 21 Feb 2007 00:50:08 -0800
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com
	[172.30.32.65])
	by hamtaro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l1L8o7dH021741; Wed, 21 Feb 2007 00:50:07 -0800 (PST)
Received: from NAEX01.qualcomm.com ([129.46.51.61]) by
	SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 21 Feb 2007 00:50:07 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: R: [AVT] CCM draft
	review--	should"bandwidth"includetheheaderoverhead
Date: Wed, 21 Feb 2007 00:50:01 -0800
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B0297C7B1@NAEX01.na.qualcomm.com>
In-Reply-To: <E9D1028EC5C22B418B5D54CA6EA27C579A5E90@PTPEVS108BA020.idc.cww.telecomitalia.it>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: R: [AVT] CCM draft
	review--	should"bandwidth"includetheheaderoverhead
Thread-Index: AcdVBz3Ox32/cs1CRn6PnWKZtOREUgAA7LOwACEgzsA=
References: <45DB196C.3010908@ericsson.com>
	<E9D1028EC5C22B418B5D54CA6EA27C579A5E90@PTPEVS108BA020.idc.cww.telecomitalia.it>
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: "Franceschini Guido" <guido.franceschini@telecomitalia.it>,
	"Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-OriginalArrivalTime: 21 Feb 2007 08:50:07.0442 (UTC)
	FILETIME=[4977BB20:01C75595]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org


> >
> > Assuming I interpret this correct, you would support a TMMBR
proposal
> > that encodes the following information:
> >
> > 1. The maximum bit-rate as seen on lowest common networking layer.
In
> > the case of IP, the maximum bit-rate available at the lowest
> > visible IP
> > layer, i.e. excluding link layer headers.
>=20
> Mmmm, your definition does not really matches my intention.
>=20
> I try to explain: suppose we have a stack (at a receiver) including
> RTP/UDP/IP/PPP/LAPM. Suppose the physical gross bandwidth is 40 Kbit/s
(in
> downlink).
> The RTP, UDP, IP and PPP layers are packet-oriented, and add a
per-packet
> overhead (12, 8, 20, 8 bytes respectively), whereas the LAPM layer is
> byte-oriented and adds a per-byte overhead (say a 10% overhead).
> If we measure bandwidth and overhead at the point at which the
protocol
> stack portion providing per-packet overhead interfaces with the
protocol
> stack portion providing per-byte overhead, we have a precise
> characterization.
>=20
>    TIDC(PPP) =3D 36 (=3D 40 - 10%)
>    MPOD(PPP) =3D 48 (=3D 12(RTP)+8(UDP)+20(IP)+8(PPP))
>=20
> If we measure bandwidth and overhead in other points of the stack, we
also
> need to make a guess about the packet rate. Here are various other
> possible tuples, for other layers and under the hypothesys of 50 and
25
> packets/sec:
>=20
>    TIDC(IP,50) =3D 33  (=3D 36 Kbit/s - 8*8*50 bit/sec)
>    MPOD(IP) =3D 40     (=3D 12+8+20)
>=20
>    TIDC(UDP,50) =3D 25 (=3D 36 Kbit/s - 28*8*50 bit/sec)
>    MPOD(UDP) =3D 20    (=3D 12+8)
>=20
>    TIDC(RTP,50) =3D 22 (=3D 36 Kbit/s - 36*8*50 bit/sec)
>    MPOD(RTP) =3D 12    (=3D 12)
>=20
>    TIDC(APP,50) =3D 17 (=3D 36 Kbit/s - 48*8*50 bit/sec)
>    MPOD(APP) =3D 0
>=20
>    TIDC(IP,25) =3D 34  (=3D 36 Kbit/s - 8*8*25 bit/sec)
>    MPOD(IP) =3D 40
>=20
>    TIDC(UDP,25) =3D 30 (=3D 36 Kbit/s - 28*8*25 bit/sec)
>    MPOD(UDP) =3D 20
>=20
>    TIDC(RTP,25) =3D 29 (=3D 36 Kbit/s - 36*8*25 bit/sec)
>    MPOD(RTP) =3D 12
>=20
>    TIDC(APP,25) =3D 26 (=3D 36 Kbit/s - 48*8*25 bit/sec)
>    MPOD(APP) =3D 0
>=20
> It is clear that inaccurate packet-rate guesses determine inaccurate
TIDC
> values, and that this effect is huge at the APP level, but reduced at
the
> IP level, for such a stack example.

If we have to work at a common layer (IP) (which results in not so
inaccurate TIDC values), estimating (max) packet rate is anyways
necessary for other media types like video. In your example, the header
overhead looks huge due to the fact that it is applied over a speech
stream. The header overhead bit-rate of a video stream may not be
significant when compared to actual video (RTP Payload) bit-rate alone.
I.e., header overhead due to inaccurate video packet rate may not be
significant. In some topologies like point 2 point, it might even be
possible for the sender to signal its actual packet rate. Average
measurement of header overhead can be used to correct/signal/detect
header overhead inaccuracies.

In my opinion this discussion on "bandwidth" control/usage is nothing
but signaling for RTP stream control (which is more than just codec
control). I would name such messages as SCMs (Stream Control Messages in
RTCP) and clear the confusion that resulted by incorrectly naming them
as "codec" control messages. IMO, SCMs should be captured in a new draft
(like Guido's) and described in a better way. RTCP TMMBR (or a flavor of
it) which includes header overhead should be called a "stream" control
message.

> Nevertheless, if the receiver communicates the tuple computed at the
PPP
> layer, it does the best job.
>=20
> Thus, my definition would better be:
>=20
> 1. The maximum bit-rate as seen on lowest packet-oriented layer (said
> layer X).
>=20
> 2. The average measurement of the number of bytes present in each
packet
> from the start of the first layer X header until the start of the RTP
> payload, plus the number of bytes present in each packet from the end
of
> the RTP payload to the end of the layer X trailer (if any). Etc etc
etc. I
> am fine with your overhead measurement criteria, that -I understand-
is
> meant to determine the average performance of a possible compression
> scheme.
>=20
> > 2. The average measurement of the number of bytes present in
> > each packet
> > from the start of the first IP header until the start of the RTP
> > payload. Which represents the header overhead in bytes for
> > each packet
> > from the lowest visible IP header to the RTP payload. This value is
> > measured for each received packet and the value reported is
> > filtered by
> > for each packet doing the following calculation:
> > avg_packet_overhead =3D 15/16*avg_packet_overhead + 1/16 *
> > packet_overhead
> >

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



From avt-bounces@ietf.org Wed Feb 21 05:57:54 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJp9K-0003Zq-8H; Wed, 21 Feb 2007 05:56:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJp9J-0003Zh-2N
	for avt@ietf.org; Wed, 21 Feb 2007 05:56:37 -0500
Received: from [212.25.125.1] (helo=aclmsg.corp.audiocodes.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJp9H-0006L3-FV
	for avt@ietf.org; Wed, 21 Feb 2007 05:56:37 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 21 Feb 2007 12:56:36 +0200
Message-ID: <79B4F738DDD4EF4F85A4641A0FE5EFD602CA8B9B@aclmsg.corp.audiocodes.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RFC 4733 flash event
Thread-Index: AcdVpvZWZNAYU8uJTR2/K9tgWjEHGQ==
From: "Yuval Nissan" <Yuval.Nissan@audiocodes.com>
To: <avt@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ec7c6dab5a62df223002ae71b5179d41
Cc: Nachum Frid <Nachum.Frid@audiocodes.com>
Subject: [AVT] RFC 4733 flash event
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0029653129=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0029653129==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C755A6.F505D94B"

This is a multi-part message in MIME format.

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

Hi,

=20

We have noticed that the line flash event (code 16) defined in RFC 2833
is now deprecated in the new RFC 4733.=20

=20

+-------------+---------------------------------------+-------------+
| Event Codes | RFC 2833 Description                  | Disposition |
+-------------+---------------------------------------+-------------+
|        0-15 | DTMF digits                           | RFC 4733    |
|          16 | Line flash (deprecated)               | Reserved    |

=20

=20

Audiocodes and other vendors already use this event in products in the
field (and will continue to use it in the future).

=20

What is the reason for this change (not keeping backward compatible)?

How this issue can be resolved, so no interop problems start to rise? =20

=20

Regards,

Yuval=20

=20


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

<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@Batang";
	panose-1:2 3 6 0 0 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>We have noticed that the line <b><span =
style=3D'font-weight:
bold'>flash</span></b> event (code 16) defined in RFC 2833 is now =
deprecated in
the new RFC 4733. </span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<pre><font size=3D2 face=3D"Courier New"><span lang=3DFR =
style=3D'font-size:10.0pt'>+-------------+-------------------------------=
--------+-------------+</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span lang=3DFR =
style=3D'font-size:10.0pt'>| Event Codes | RFC 2833 =
Description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Disposition =
|</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>+-------------+-------------------------------=
--------+-------------+</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
0-15 | DTMF digits&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| RFC =
4733&nbsp;&nbsp;&nbsp; |</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; 16 | Line flash =
(deprecated)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; | Reserved&nbsp;&nbsp;&nbsp; =
|</span></font></pre>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Audiocodes and other vendors already use this event =
in products
in the field (and will continue to use it in the =
future).</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>What is the reason for this change (not keeping =
backward
compatible)?</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>How this issue can be resolved, so no interop =
problems start
to rise? &nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Regards,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Yuval </span></font></p>

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

</div>

</body>

</html>

------_=_NextPart_001_01C755A6.F505D94B--


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

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

--===============0029653129==--




From avt-bounces@ietf.org Wed Feb 21 09:04:44 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJs4M-00062T-SB; Wed, 21 Feb 2007 09:03:42 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJs4L-00062N-NV
	for avt@ietf.org; Wed, 21 Feb 2007 09:03:41 -0500
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJs4K-00088l-Bl
	for avt@ietf.org; Wed, 21 Feb 2007 09:03:41 -0500
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:55204)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HJs4J-0004Jm-Ot for avt@ietf.org; Wed, 21 Feb 2007 14:03:39 +0000
Mime-Version: 1.0 (Apple Message framework v752.2)
References: <E1HHvCT-0001Mx-S9@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <4A520F89-1B49-41D1-9F19-1846AC60084C@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Wed, 21 Feb 2007 14:03:39 +0000
To: IETF AVT WG <avt@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Subject: [AVT] Fwd: Internet-Drafts Submission Cutoff Dates for the 68th
	IETF Meeting in Prague, Czech Republic 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

A reminder that the internet-draft submission deadlines for the  
Prague IETF meeting are rapidly approaching.

Colin



Begin forwarded message:
> From: ietf-secretariat@ietf.org
> Date: 16 February 2007 05:00:01 GMT
> To: ietf-announce@ietf.org
> Subject: Internet-Drafts Submission Cutoff Dates for the 68th IETF   
> Meeting in Prague, Czech Republic
>
>
> There are two (2) Internet-Draft cutoff dates for the 68th
> IETF Meeting in Prague, Czech Republic:
>
> February 26th: Cutoff Date for Initial (i.e., version -00)
> Internet-Draft Submissions
>
> All initial Internet-Drafts (version -00) must be submitted by Monday,
> February 26th at 9:00 AM ET. As always, all initial submissions with a
> filename beginning with "draft-ietf" must be approved by the
> appropriate WG Chair before they can be processed or announced.  The
> Secretariat would appreciate receiving WG Chair approval by Monday,
> February 19th at 9:00 AM ET.
>
> March 5th: Cutoff Date for Revised (i.e., version -01 and higher)
> Internet-Draft Submissions
>
> All revised Internet-Drafts (version -01 and higher) must be submitted
> by Monday, March 5th at 9:00 AM ET.
>
> Initial and revised Internet-Drafts received after their respective
> cutoff dates will not be made available in the Internet-Drafts
> directory or announced until on or after Monday, March 19th at 9:00
> AM ET, when Internet-Draft posting resumes.  Please do not wait until
> the last minute to submit.
>
> Thank you for your understanding and cooperation. If you have any
> questions or concerns, then please send a message to
> internet-drafts@ietf.org.
>
> The IETF Secretariat
>
> FYI: The Internet-Draft cutoff dates as well as other significant  
> dates
> for the 68th IETF Meeting can be found at http://www.ietf.org/ 
> meetings/cutoff_dates_68.html.
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce



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



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



From avt-bounces@ietf.org Wed Feb 21 09:23:08 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJsMQ-0007nV-EN; Wed, 21 Feb 2007 09:22:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJsMP-0007nP-Ge
	for avt@ietf.org; Wed, 21 Feb 2007 09:22:21 -0500
Received: from zrtps0kn.nortel.com ([47.140.192.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJsMO-0003EN-5N
	for avt@ietf.org; Wed, 21 Feb 2007 09:22:21 -0500
Received: from zcarhxs1.corp.nortel.com (zcarhxs1.corp.nortel.com
	[47.129.230.89])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l1LEMHm09218; Wed, 21 Feb 2007 09:22:17 -0500 (EST)
Received: from [47.130.16.147] ([47.130.16.147] RDNS failed) by
	zcarhxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 21 Feb 2007 09:22:17 -0500
Message-ID: <45DC5584.2040801@nortel.com>
Date: Wed, 21 Feb 2007 09:21:56 -0500
From: "Tom-PT Taylor" <taylor@nortel.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Yuval Nissan <Yuval.Nissan@audiocodes.com>
Subject: Re: [AVT] RFC 4733 flash event
References: <79B4F738DDD4EF4F85A4641A0FE5EFD602CA8B9B@aclmsg.corp.audiocodes.com>
In-Reply-To: <79B4F738DDD4EF4F85A4641A0FE5EFD602CA8B9B@aclmsg.corp.audiocodes.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Feb 2007 14:22:17.0180 (UTC)
	FILETIME=[B08469C0:01C755C3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: Nachum Frid <Nachum.Frid@audiocodes.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Someone has to write an I-D re-standardizing the line events they want 
to preserve. When I worked on 2833bis, 2833biscas and 2833bisdata, no 
one indicated any interest in the line-related events. Now, it seems 
like there is some interest. I wouldn't think it would be a big job to 
write the draft, but I feel I've done my part.

BTW we did make sure the codepoints remain available for allocation.

Yuval Nissan wrote:
> Hi,
> 
>  
> 
> We have noticed that the line flash event (code 16) defined in RFC 2833
> is now deprecated in the new RFC 4733. 
> 
>  
> 
> +-------------+---------------------------------------+-------------+
> | Event Codes | RFC 2833 Description                  | Disposition |
> +-------------+---------------------------------------+-------------+
> |        0-15 | DTMF digits                           | RFC 4733    |
> |          16 | Line flash (deprecated)               | Reserved    |
> 
>  
> 
>  
> 
> Audiocodes and other vendors already use this event in products in the
> field (and will continue to use it in the future).
> 
>  
> 
> What is the reason for this change (not keeping backward compatible)?
> 
> How this issue can be resolved, so no interop problems start to rise?  
> 
>  
> 
> Regards,
> 
> Yuval 
> 
>  
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

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



From avt-bounces@ietf.org Wed Feb 21 09:46:51 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJsiy-0002kb-O7; Wed, 21 Feb 2007 09:45:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJsix-0002kW-Qd
	for avt@ietf.org; Wed, 21 Feb 2007 09:45:39 -0500
Received: from zrtps0kn.nortel.com ([47.140.192.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJsiw-0008MX-HO
	for avt@ietf.org; Wed, 21 Feb 2007 09:45:39 -0500
Received: from zcarhxs1.corp.nortel.com (zcarhxs1.corp.nortel.com
	[47.129.230.89])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l1LEjEm14390; Wed, 21 Feb 2007 09:45:15 -0500 (EST)
Received: from [47.130.16.147] ([47.130.16.147] RDNS failed) by
	zcarhxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 21 Feb 2007 09:45:03 -0500
Message-ID: <45DC5ADB.9010703@nortel.com>
Date: Wed, 21 Feb 2007 09:44:43 -0500
From: "Tom-PT Taylor" <taylor@nortel.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Dave Singer <singer@apple.com>
Subject: Re: [AVT] Re: draft-ietf-avt-rtp-hdrext-09.txt
References: <45DA67F7.5090108@nortel.com>
	<p06230963c200e927c7fc@[17.202.35.52]>
	<45DB5048.7020003@nortel.com>
In-Reply-To: <45DB5048.7020003@nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Feb 2007 14:45:03.0430 (UTC)
	FILETIME=[DEDD9E60:01C755C6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: avt@ietf.org, Hari Desineni <hd@qualcomm.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

I am wondering if what you really meant for this paragraph was:

  "Note that either party may include extensions in the stream other
   than those negotiated, or those negotiated as "inactive", for example
   for the benefit of intermediate nodes.  Only extensions that appeared
   with an identifier in the range 1-14 in SDP originated by the sender
   can be sent."


Taylor, Tom-PT (CAR:AR00) wrote:
> Just one open item at the end.
> 
> Dave Singer wrote:
>> At 22:16  -0500 19/02/07, Tom-PT Taylor wrote:
> ...
>>> 6. The last paragraph on page 10 before the example reads:
>>>
>>> "Note that either party may include extensions in the stream other
>>>    than those negotiated, or those negotiated as "inactive", for example
>>>    for the benefit of intermediate nodes.  Only extensions with an
>>>    identifier in the range 1-14, and with a declaration, can be sent."
>>>
>>> In that last line, "and with a declaration" seems to contradict 
>>> "other than those negotiated" in the preceding lines. What is meant 
>>> here? I also think that "may" in the first line should be an RFC 
>>> 2119 "MAY".
>> Ok, "MAY" changed.  The point of the last sentence is that even if 
>> you don't offer to receive an extension, I might send it;  but if I 
>> send it, I have to include its declaration.
>>
>> How about
>>
>> <t>Either party MAY include extensions in the stream other than those 
>> offered, for example for the benefit of intermediate nodes.  For the 
>> RTP packets to include the extension, it must have been declared with 
>> an identifier in the range 1-14.</t>
>>
>> ?
>>
>>
> [PTT] I'm left to infer from this that the declaration happens in the 
> answer, since the first sentence says it wasn't in the offer. Is this 
> what you intended?
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
> 

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



From avt-bounces@ietf.org Wed Feb 21 11:22:49 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJuE1-0006NR-Ig; Wed, 21 Feb 2007 11:21:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJuDy-0006Lx-9n
	for avt@ietf.org; Wed, 21 Feb 2007 11:21:46 -0500
Received: from zcars04f.nortel.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJuDu-0005hk-2S
	for avt@ietf.org; Wed, 21 Feb 2007 11:21:46 -0500
Received: from zcarhxs1.corp.nortel.com (zcarhxs1.corp.nortel.com
	[47.129.230.89])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l1LGLbZ25397; Wed, 21 Feb 2007 11:21:37 -0500 (EST)
Received: from [47.130.16.147] ([47.130.16.147] RDNS failed) by
	zcarhxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 21 Feb 2007 11:21:21 -0500
Message-ID: <45DC716D.3060409@nortel.com>
Date: Wed, 21 Feb 2007 11:21:01 -0500
From: "Tom-PT Taylor" <taylor@nortel.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Dave Singer <singer@apple.com>, avt@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Feb 2007 16:21:21.0883 (UTC)
	FILETIME=[531792B0:01C755D4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: 
Subject: [AVT] ABNF in draft-ietf-avt-smpte-rtp-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

The ABNF in section 4 of draft-ietf-avt-smpte-rtp-08.txt needs fixing. 
Per RFC 4234, alternatives are expressed by forward slash rather than 
vertical bar. Thus your first line should be:

digit = "0"/"1"/"2"/"3"/"4"/"5"/"6"/"7"/"8"/"9"

I also note a discrepancy (legal, but undesirable) between the complete 
extensionattributes string and its definition as a series of 
space-separated parameters in [hdrext]. Would you consider replacing the 
"/" separator by space as defined in [hdrext]? Or is [hdrext] wrong in 
specifying space as a separator?

Finally, to get what you want for drop, use the square brackets:

drop = "/drop"
or
drop = space "drop"

and

extensionattributes = frame_duration "/" frames_per_tc_second [drop]
or
extensionattributes = frame_duration space frames_per_tc_second [drop]






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



From avt-bounces@ietf.org Wed Feb 21 12:29:30 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJvGI-0002G5-CI; Wed, 21 Feb 2007 12:28:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJvGH-0002Fz-IW
	for avt@ietf.org; Wed, 21 Feb 2007 12:28:13 -0500
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJvGF-0006vV-3j
	for avt@ietf.org; Wed, 21 Feb 2007 12:28:13 -0500
Received: from relay5.apple.com (relay5.apple.com [17.128.113.35])
	by mail-out3.apple.com (8.13.8/8.13.8) with ESMTP id l1LHSAiU004091;
	Wed, 21 Feb 2007 09:28:10 -0800 (PST)
Received: from relay5.apple.com (unknown [127.0.0.1])
	by relay5.apple.com (Symantec Mail Security) with ESMTP id 8039329C005; 
	Wed, 21 Feb 2007 09:28:10 -0800 (PST)
X-AuditID: 11807123-a13bbbb000000a1d-eb-45dc812ae995 
Received: from [10.101.201.85] (Vpn2priv-61.apple.com [17.219.204.61])
	by relay5.apple.com (Apple SCV relay) with ESMTP id 91B6930400D;
	Wed, 21 Feb 2007 09:28:09 -0800 (PST)
Mime-Version: 1.0
Message-Id: <p06230901c202313be682@[10.101.201.85]>
In-Reply-To: <45DC5ADB.9010703@nortel.com>
References: <45DA67F7.5090108@nortel.com>
	<p06230963c200e927c7fc@[17.202.35.52]> <45DB5048.7020003@nortel.com>
	<45DC5ADB.9010703@nortel.com>
Date: Wed, 21 Feb 2007 09:26:33 -0800
To: Tom-PT Taylor <taylor@nortel.com>
From: Dave Singer <singer@apple.com>
Subject: Re: [AVT] Re: draft-ietf-avt-rtp-hdrext-09.txt
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: avt@ietf.org, Hari Desineni <hd@qualcomm.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

At 9:44  -0500 21/02/07, Tom-PT Taylor wrote:
>I am wondering if what you really meant for this paragraph was:
>
>  "Note that either party may include extensions in the stream other
>   than those negotiated, or those negotiated as "inactive", for example
>   for the benefit of intermediate nodes.  Only extensions that appeared
>   with an identifier in the range 1-14 in SDP originated by the sender
>   can be sent."

that would also be fine.

>
>Taylor, Tom-PT (CAR:AR00) wrote:
>>Just one open item at the end.
>>
>>Dave Singer wrote:
>>>At 22:16  -0500 19/02/07, Tom-PT Taylor wrote:
>>...
>>>>6. The last paragraph on page 10 before the example reads:
>>>>
>>>>"Note that either party may include extensions in the stream other
>>>>    than those negotiated, or those negotiated as "inactive", for example
>>>>    for the benefit of intermediate nodes.  Only extensions with an
>>>>    identifier in the range 1-14, and with a declaration, can be sent."
>>>>
>>>>In that last line, "and with a declaration" seems to contradict 
>>>>"other than those negotiated" in the preceding lines. What is 
>>>>meant here? I also think that "may" in the first line should be 
>>>>an RFC 2119 "MAY".
>>>Ok, "MAY" changed.  The point of the last sentence is that even if 
>>>you don't offer to receive an extension, I might send it;  but if 
>>>I send it, I have to include its declaration.
>>>
>>>How about
>>>
>>><t>Either party MAY include extensions in the stream other than 
>>>those offered, for example for the benefit of intermediate nodes. 
>>>For the RTP packets to include the extension, it must have been 
>>>declared with an identifier in the range 1-14.</t>
>>>
>>>?
>>>
>>[PTT] I'm left to infer from this that the declaration happens in 
>>the answer, since the first sentence says it wasn't in the offer. 
>>Is this what you intended?
>>
>>_______________________________________________
>>Audio/Video Transport Working Group
>>avt@ietf.org
>>https://www1.ietf.org/mailman/listinfo/avt


-- 
David Singer
Apple Computer/QuickTime

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



From avt-bounces@ietf.org Wed Feb 21 12:36:05 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJvNB-0003Oi-H6; Wed, 21 Feb 2007 12:35:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJvNB-0003Oc-0Y
	for avt@ietf.org; Wed, 21 Feb 2007 12:35:21 -0500
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HJvN8-0008Uz-P2 for avt@ietf.org; Wed, 21 Feb 2007 12:35:20 -0500
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 Feb 2007 12:35:18 -0500
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>
Subject: Re: R: [AVT] CCM draft review--
	should"bandwidth"includetheheaderoverhead
References: <45DB196C.3010908@ericsson.com>
	<E9D1028EC5C22B418B5D54CA6EA27C579A5E90@PTPEVS108BA020.idc.cww.telecomitalia.it>
	<2CA3E1B6CEC064449CAA7D0FAB46079B0297C7B1@NAEX01.na.qualcomm.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Wed, 21 Feb 2007 12:35:17 -0500
In-Reply-To: <2CA3E1B6CEC064449CAA7D0FAB46079B0297C7B1@NAEX01.na.qualcomm.com>
	(Harikishan
	Desineni's message of "Wed, 21 Feb 2007 00:50:01 -0800")
Message-ID: <ybuejojo1m2.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 21 Feb 2007 17:35:18.0718 (UTC)
	FILETIME=[A7A6DDE0:01C755DE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, avt@ietf.org,
	Franceschini Guido <guido.franceschini@telecomitalia.it>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

"Desineni, Harikishan" <hdesinen@qualcomm.com> writes:
>> It is clear that inaccurate packet-rate guesses determine inaccurate
>> TIDC values, and that this effect is huge at the APP level, but reduced
>> at the IP level, for such a stack example.
>
>If we have to work at a common layer (IP) (which results in not so
>inaccurate TIDC values), estimating (max) packet rate is anyways
>necessary for other media types like video. In your example, the header
>overhead looks huge due to the fact that it is applied over a speech
>stream. The header overhead bit-rate of a video stream may not be
>significant when compared to actual video (RTP Payload) bit-rate alone.
>I.e., header overhead due to inaccurate video packet rate may not be
>significant. In some topologies like point 2 point, it might even be
>possible for the sender to signal its actual packet rate. Average
>measurement of header overhead can be used to correct/signal/detect
>header overhead inaccuracies.

Note that video links might vary wildly in packets per second, due to
a) motion, b) packetization, c) jitter (for example, using codec bitrates
of circa 384K/30FPS on a 1500-byte MTU link - a frame could easily be one
or two packets, causing big swings in rate), d) iframe pacing and/or error
recovery (iframes use a bunch of packets compared to pframes typically), 
etc, etc.  The sender may vary framerate in response to
bitrate/congestion as well.

This is part of why I argue for letting the sender apportion the available
bits (as best as possible), including as much of the packet overhead as
possible.

Averages for header overhead may or may not help, depending on the type of
header overhead.  For example, if a header extension uses 500 bytes once
every 3 seconds (say for security/ZRTP/etc), on a link with nominal 50 pps
of 50 bytes, the "15/16 plus 1/16" will show serious spikes, and make TMMBR
very sensitive to exactly where in the decay of the spike it's sent.  On
the other hand, the sender should know about any header extensions it is
and has sent.

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


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



From avt-bounces@ietf.org Wed Feb 21 13:06:31 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJvqL-0006ym-A4; Wed, 21 Feb 2007 13:05:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJtuw-0004xZ-E9; Wed, 21 Feb 2007 11:02:07 -0500
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HJtus-0008LZ-JB; Wed, 21 Feb 2007 11:02:06 -0500
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:55362)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HJtur-0005Wd-1s; Wed, 21 Feb 2007 16:02:01 +0000
In-Reply-To: <2CA3E1B6CEC064449CAA7D0FAB46079B028B0ACC@NAEX01.na.qualcomm.com>
References: <2CA3E1B6CEC064449CAA7D0FAB46079B028B0ACC@NAEX01.na.qualcomm.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <6345BEB5-1C1D-4B99-9662-8E75C3CA87EC@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Wed, 21 Feb 2007 16:01:59 +0000
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
X-Mailman-Approved-At: Wed, 21 Feb 2007 13:05:27 -0500
Cc: mmusic WG <mmusic@ietf.org>
Subject: [AVT] Re: [MMUSIC] Draft on SDP BW attribute for media bitrate in
	'send' direction ( draft-hdesinen-mmusic-oa-send-bw-attr-00.txt )
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On 16 Feb 2007, at 07:41, Desineni, Harikishan wrote:
> AVT & MMUSIC,

I've bcc'd the AVT list on this message. Future discussion on the  
MMUSIC list, please.

> Here is a draft which defines a new bandwidth attribute for SDP
> Offer/Answer model.
>
> =======
> Abstract:
> "This document defines a new SDP bandwidth attribute that can be  
> used to
> signal the maximum media bitrate in 'send' direction of a stream in  
> SDP
> offer/answer model."
> =========
>
> -01 version of the draft is not yet available on IETF server. Until  
> then
> it can be viewed at
> http://people.qualcomm.com/hdesinen/draft-hdesinen-mmusic-oa-send- 
> bw-att
> r-01.txt
>
> -00 is available on IETF server at
> http://www.ietf.org/internet-drafts/draft-hdesinen-mmusic-oa-send- 
> bw-att
> r-00.txt
>
> Please review the latest version (-01) of the draft and post your
> comments.

The terminology in Section 5 is misleading and incorrect, and should  
be changed. This is not an SDP attribute ("a=" line), but rather a  
Bandwidth Specifier (for the "b=" line). Please update the draft to  
use the correct terminology.

Also, RFC 4566, notes that "although no length limit is given, it is  
recommended that they be short" when discussing bandwidth specifier  
names. Following this, and existing practice, it might be better to  
name this "MSR" rather than "maxsendrate"?

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



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



From avt-bounces@ietf.org Wed Feb 21 13:08:49 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJvsy-0007Fs-Uw; Wed, 21 Feb 2007 13:08:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJvsx-0007Fg-A0
	for avt@ietf.org; Wed, 21 Feb 2007 13:08:11 -0500
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJvsv-0008Uq-W0
	for avt@ietf.org; Wed, 21 Feb 2007 13:08:11 -0500
Received: from relay6.apple.com (relay6.apple.com [17.128.113.36])
	by mail-out4.apple.com (8.13.8/8.13.8) with ESMTP id l1LI89Bk027068;
	Wed, 21 Feb 2007 10:08:09 -0800 (PST)
Received: from relay6.apple.com (unknown [127.0.0.1])
	by relay6.apple.com (Symantec Mail Security) with ESMTP id 6F55D10CC4; 
	Wed, 21 Feb 2007 10:08:09 -0800 (PST)
X-AuditID: 11807124-9f753bb0000035e0-8f-45dc8a8982b7 
Received: from [10.101.201.85] (Vpn2priv-61.apple.com [17.219.204.61])
	by relay6.apple.com (Apple SCV relay) with ESMTP id EBCFB1012D;
	Wed, 21 Feb 2007 10:08:08 -0800 (PST)
Mime-Version: 1.0
Message-Id: <p06230905c202362c0f1d@[10.101.201.85]>
In-Reply-To: <45DC716D.3060409@nortel.com>
References: <45DC716D.3060409@nortel.com>
Date: Wed, 21 Feb 2007 10:07:03 -0800
To: Tom-PT Taylor <taylor@nortel.com>, avt@ietf.org
From: Dave Singer <singer@apple.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: 
Subject: [AVT] Re: ABNF in draft-ietf-avt-smpte-rtp-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

At 11:21  -0500 21/02/07, Tom-PT Taylor wrote:
>The ABNF in section 4 of draft-ietf-avt-smpte-rtp-08.txt needs 
>fixing. Per RFC 4234, alternatives are expressed by forward slash 
>rather than vertical bar. Thus your first line should be:
>
>digit = "0"/"1"/"2"/"3"/"4"/"5"/"6"/"7"/"8"/"9"

I'm sure I copied this string from another RFC, but I don't mind changing it...

>I also note a discrepancy (legal, but undesirable) between the 
>complete extensionattributes string and its definition as a series 
>of space-separated parameters in [hdrext].

No, hdrext merely says that it is separated from the URI by a space. 
Or did I write something I didn't intend?

>Would you consider replacing the "/" separator by space as defined 
>in [hdrext]? Or is [hdrext] wrong in specifying space as a separator?

as I say, unless I missed something, I don't think it necessary.

>
>Finally, to get what you want for drop, use the square brackets:
>
>drop = "/drop"
>or
>drop = space "drop"
>
>and
>
>extensionattributes = frame_duration "/" frames_per_tc_second [drop]
>or
>extensionattributes = frame_duration space frames_per_tc_second [drop]

ok

-- 
David Singer
Apple Computer/QuickTime

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



From avt-bounces@ietf.org Wed Feb 21 13:24:09 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJw7g-0002Ia-CO; Wed, 21 Feb 2007 13:23:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJvdJ-0004mF-BV
	for avt@ietf.org; Wed, 21 Feb 2007 12:52:01 -0500
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HJvZ8-0002x0-0R for avt@ietf.org; Wed, 21 Feb 2007 12:47:43 -0500
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 Feb 2007 12:47:42 -0500
To: "Ingemar Johansson S \(LU/EAB\)" <ingemar.s.johansson@ericsson.com>
Subject: Re: [AVT] RE: Review of
	draft-johansson-avt-rtcp-avpf-non-compound-00.txt
References: <026F8EEDAD2C4342A993203088C1FC050474B0C8@esealmw109.eemea.ericsson.se>
From: Randell Jesup <rjesup@wgate.com>
Date: Wed, 21 Feb 2007 12:47:39 -0500
In-Reply-To: <026F8EEDAD2C4342A993203088C1FC050474B0C8@esealmw109.eemea.ericsson.se>
	(Ingemar
	Johansson S.'s message of "Tue, 20 Feb 2007 13:33:22 +0100")
Message-ID: <ybuabz7o11g.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 21 Feb 2007 17:47:42.0040 (UTC)
	FILETIME=[62B4CD80:01C755E0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: "Magnus Westerlund \(KI/EAB\)" <magnus.westerlund@ericsson.com>,
	John Lazzaro <lazzaro@eecs.berkeley.edu>,
	Roni Even <roni.even@polycom.co.il>, IETF AVT WG <avt@ietf.org>,
	Joerg Ott <jo@netlab.tkk.fi>, Tom-PT Taylor <taylor@nortel.com>,
	Colin Perkins <csp@csperkins.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

"Ingemar Johansson S \(LU/EAB\)" <ingemar.s.johansson@ericsson.com> writes:
>> So, if we have two devices communicating in a specific 
>> wireless environment, where all kinds of optimizations are 
>> already carried out between a base station and the mobile 
>> equipment, why not treat this problem at this very place 
>> where it belongs?  This feels like another specific 
>> optimization useful on one particular link and should not 
>> impact the rest of the Internet.

>One could always argue in this direction. Problem is however that in
>order to achieve a maximum throughput in terms of Mbits/Hz/s some
>optimizations are needed and large RTCP packets impose a problem in that
>aspect. If the systems are made less optimized this problem is lesser
>but this comes at a cost of reduced coverage/capacity and eventually
>less revenue for operator or higher cost for the user. I don't believe
>that this is a 3GPP problem as the law of physics applies to all
>wireless access technologies. Some access technologies might not
>experience this problem are they may be hidden by e.g large
>packetization overhead.

>From the point of a non-wireless RTP/RTCP user, I also see noticable
advantage to non-compound RTCP, at least in an AVPF framework.  If you're
only sending RTCP every 5 seconds, layering another sub-packet in isn't a
big deal; if you're sending them for real-time events under AVPF, you may
consume noticable extra bandwidth, enough to impact the available bits for
other data in the channel.  (And remember that even a 5% hit could be a
noticable reduction in quality, and RTCP may be allowed a higher
percentage - and if the SR's bump you up against the 5% limit, under AVPF
rules you may need to delay or throw away attempts to use RTCP for a while.)

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


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



From avt-bounces@ietf.org Wed Feb 21 13:38:04 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJwKw-0000Sz-07; Wed, 21 Feb 2007 13:37:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJwKu-0000Sr-UH
	for avt@ietf.org; Wed, 21 Feb 2007 13:37:04 -0500
Received: from zcars04e.nortel.com ([47.129.242.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJwKs-0007YE-W7
	for avt@ietf.org; Wed, 21 Feb 2007 13:37:04 -0500
Received: from zcarhxs1.corp.nortel.com (zcarhxs1.corp.nortel.com
	[47.129.230.89])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	l1LISm529846; Wed, 21 Feb 2007 13:28:49 -0500 (EST)
Received: from [47.130.16.147] ([47.130.16.147] RDNS failed) by
	zcarhxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 21 Feb 2007 13:36:52 -0500
Message-ID: <45DC9130.4070101@nortel.com>
Date: Wed, 21 Feb 2007 13:36:32 -0500
From: "Tom-PT Taylor" <taylor@nortel.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Dave Singer <singer@apple.com>
References: <45DC716D.3060409@nortel.com>
	<p06230905c202362c0f1d@[10.101.201.85]>
In-Reply-To: <p06230905c202362c0f1d@[10.101.201.85]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Feb 2007 18:36:52.0226 (UTC)
	FILETIME=[41277620:01C755E7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: avt@ietf.org
Subject: [AVT] Re: ABNF in draft-ietf-avt-smpte-rtp-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Look at the first paragraph, last line, of section 7 of [hdrext]. Then 
decide how you want to go -- change [hdrext], change [smpte], or do 
nothing (though as I say, this last is undesirable).

Dave Singer wrote:
> At 11:21  -0500 21/02/07, Tom-PT Taylor wrote:
...

> 
>> I also note a discrepancy (legal, but undesirable) between the 
>> complete extensionattributes string and its definition as a series 
>> of space-separated parameters in [hdrext].
> 
> No, hdrext merely says that it is separated from the URI by a space. 
> Or did I write something I didn't intend?
> 
>> Would you consider replacing the "/" separator by space as defined 
>> in [hdrext]? Or is [hdrext] wrong in specifying space as a separator?
> 
> as I say, unless I missed something, I don't think it necessary.
> 
...

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



From avt-bounces@ietf.org Wed Feb 21 13:43:08 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJwPx-0001NZ-UZ; Wed, 21 Feb 2007 13:42:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJwPw-0001NR-G3
	for avt@ietf.org; Wed, 21 Feb 2007 13:42:16 -0500
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJwPv-0008KU-5I
	for avt@ietf.org; Wed, 21 Feb 2007 13:42:16 -0500
Received: from relay8.apple.com (relay8.apple.com [17.128.113.38])
	by mail-out3.apple.com (8.13.8/8.13.8) with ESMTP id l1LIgEmQ016608;
	Wed, 21 Feb 2007 10:42:14 -0800 (PST)
Received: from relay8.apple.com (unknown [127.0.0.1])
	by relay8.apple.com (Symantec Mail Security) with ESMTP id 9532840054; 
	Wed, 21 Feb 2007 10:42:14 -0800 (PST)
X-AuditID: 11807126-9cfc8bb00000685d-64-45dc92834dbc 
Received: from [10.101.201.85] (Vpn2priv-61.apple.com [17.219.204.61])
	by relay8.apple.com (Apple SCV relay) with ESMTP id 862BB40492;
	Wed, 21 Feb 2007 10:42:10 -0800 (PST)
Mime-Version: 1.0
Message-Id: <p0623090ac20242b4fef6@[10.101.201.85]>
In-Reply-To: <45DC9130.4070101@nortel.com>
References: <45DC716D.3060409@nortel.com>
	<p06230905c202362c0f1d@[10.101.201.85]> <45DC9130.4070101@nortel.com>
Date: Wed, 21 Feb 2007 10:41:16 -0800
To: Tom-PT Taylor <taylor@nortel.com>
From: Dave Singer <singer@apple.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: avt@ietf.org
Subject: [AVT] Re: ABNF in draft-ietf-avt-smpte-rtp-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

At 13:36  -0500 21/02/07, Tom-PT Taylor wrote:
>Look at the first paragraph, last line, of section 7 of [hdrext]. 
>Then decide how you want to go -- change [hdrext], change [smpte], 
>or do nothing (though as I say, this last is undesirable).

I'll remove "separated by spaces", thanks.  It's gratuitous.

>
>Dave Singer wrote:
>>At 11:21  -0500 21/02/07, Tom-PT Taylor wrote:
>...
>
>>
>>>I also note a discrepancy (legal, but undesirable) between the 
>>>complete extensionattributes string and its definition as a series 
>>>of space-separated parameters in [hdrext].
>>
>>No, hdrext merely says that it is separated from the URI by a 
>>space. Or did I write something I didn't intend?
>>
>>>Would you consider replacing the "/" separator by space as defined 
>>>in [hdrext]? Or is [hdrext] wrong in specifying space as a 
>>>separator?
>>
>>as I say, unless I missed something, I don't think it necessary.
>>
>...


-- 
David Singer
Apple Computer/QuickTime

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



From avt-bounces@ietf.org Thu Feb 22 01:22:03 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HK7Jf-0000uf-Ob; Thu, 22 Feb 2007 01:20:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HK7Jd-0000tW-Vx
	for avt@ietf.org; Thu, 22 Feb 2007 01:20:29 -0500
Received: from jaguar.hughesbpo.net ([61.246.186.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HK7Ja-0003CB-SD
	for avt@ietf.org; Thu, 22 Feb 2007 01:20:29 -0500
Received: from jaguar.hughesbpo.net (localhost.localdomain [127.0.0.1])
	by jaguar.hughesbpo.net (8.13.8/8.13.8) with ESMTP id l1M6K5Y6009015
	for <avt@ietf.org>; Thu, 22 Feb 2007 11:50:05 +0530
Received: from sandesh.hss.hns.com (sandesh [10.203.142.21])
	by jaguar.hughesbpo.net (8.13.8/8.13.8) with ESMTP id l1M6K5Im008992
	for <avt@ietf.org>; Thu, 22 Feb 2007 11:50:05 +0530
To: avt@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V655_10312005 October 31, 2005
Message-ID: <OFFCF11754.ABFEE9F4-ON6525728A.00208995-6525728A.002309F2@flextronicssoftware.com>
From: Sunil Mahajan <sunil.mahajan@aricent.com>
Date: Thu, 22 Feb 2007 11:54:44 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.5.5|November 30,
	2005) at 22/02/2007 11:53:45 AM,
	Serialize complete at 22/02/2007 11:53:45 AM
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: Shyam SBK Gupta Pallapothu <Shyam.Pallapothu@aricent.com>
Subject: [AVT] Revised IETF Draft - Support for Selective Encryption in SRTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0384067011=="
Errors-To: avt-bounces@ietf.org

This is a multipart message in MIME format.
--===============0384067011==
Content-Type: multipart/alternative;
	boundary="=_alternative 002309E76525728A_="

This is a multipart message in MIME format.
--=_alternative 002309E76525728A_=
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: base64

SGkgQWxsLA0KDQpXZSBoYXZlIHJlLXN1Ym1pdHRlZCBpZXRmIGRyYWZ0IG9uIHN1cHBvcnQgZm9y
IHNlbGVjdGl2ZSBlbmNyeXB0aW9uIGluIA0KU1JUUCAtIHRoaXMgZHJhZnQNCmlzIGVuaGFuY2Vk
IGJhc2VkIG9uIHRoZSBmZWVkYmFjayByZWNlaXZlZCBmcm9tIHRoZSBtYWlsaW5nIGxpc3QuIEl0
cyANCmF2YWlsYWJsZSBhdDoNCiANCmh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRz
L2RyYWZ0LXNtYWhhamFuLXNydHAtc2VsZWN0aXZlLWVuY3J5cHRpb24tMDEudHh0DQoNCldvdWxk
IHJlcXVlc3QgdGhlIG1lbWJlcnMgb24gdGhlIGxpc3QgdG8gZ28gdGhyb3VnaCB0aGUgZHJhZnQg
YW5kIHByb3ZpZGUgDQp0aGVpciB2YWx1YWJsZSBmZWVkYmFjay4NCg0KU3VtbWFyeSBvZiBjaGFu
Z2VzOg0KMSkgSW5jbHVkZWQgc29tZSBkZXRhaWxlZCBkZXNjcmlwdGlvbiBvZiAiU2VsZWN0aXZl
IEVuY3J5cHRpb24iIHdpdGggDQpleGFtcGxlcyBvZiBib3RoIGtpbmQgb2Ygc2VsZWN0aXZlDQog
ICAgIGVuY3J5cHRpb24gLSBiYXNlZCBvbiBjb250ZW50IHR5cGUgYW5kIGZyYW1lIHR5cGUNCjIp
IFJlYWwgbGlmZSBleGFtcGxlcyBvZiB1c2FnZSBvZiBzZWxlY3RpdmUgZW5jcnlwdGlvbg0KMykg
MiBtZXRob2RzIHRvIHN1cHBvcnQgU2VsZWN0aXZlIEVuY3J5cHRpb24gaW4gU1JUUCAtIG92ZXJs
b2FkZWQgTUtJIGJpdCANCmFuZCBhZGRpdGlvbmFsIHBhcmFtZXRlcg0KICAgICBpbiBTUlRQIHRv
IGluZGljYXRlIHNlbGVjdGl2ZSBlbmNyeXB0aW9uDQo0KSBFbmhhbmNlZCAiU2VjdXJpdHkgQ29u
c2lkZXJhdGlvbiIgc2VjdGlvbiB0byB3YXJuIG1pc3VzZSBvZiBzZWxlY3RpdmUgDQplbmNyeXB0
aW9uDQoNClJlZ2FyZHMsDQpTdW5pbCBNYWhhamFuDQpBUklDRU5ULCBJTkRJQQ0KDQoNCg0KKioq
KioqKioqKioqKioqKioqKioqKiogIEFyaWNlbnQtVW5jbGFzc2lmaWVkICAgKioqKioqKioqKioq
KioqKioqKioqKioNCg0KKioqKioqKioqKioqKioqKioqKioqKiogIEFyaWNlbnQtVW5jbGFzc2lm
aWVkICAgKioqKioqKioqKioqKioqKioqKioqKioNCiJESVNDTEFJTUVSOiBUaGlzIG1lc3NhZ2Ug
aXMgcHJvcHJpZXRhcnkgdG8gQXJpY2VudCAgYW5kIGlzIGludGVuZGVkIHNvbGVseSBmb3IgdGhl
IHVzZSBvZiAKdGhlIGluZGl2aWR1YWwgdG8gd2hvbSBpdCBpcyBhZGRyZXNzZWQuIEl0IG1heSBj
b250YWluIHByaXZpbGVnZWQgb3IgY29uZmlkZW50aWFsIGluZm9ybWF0aW9uIGFuZCBzaG91bGQg
bm90IGJlIApjaXJjdWxhdGVkIG9yIHVzZWQgZm9yIGFueSBwdXJwb3NlIG90aGVyIHRoYW4gZm9y
IHdoYXQgaXQgaXMgaW50ZW5kZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgbWVzc2FnZSBp
biBlcnJvciwgCnBsZWFzZSBub3RpZnkgdGhlIG9yaWdpbmF0b3IgaW1tZWRpYXRlbHkuIElmIHlv
dSBhcmUgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQsIHlvdSBhcmUgbm90aWZpZWQgdGhhdCB5
b3UgYXJlIHN0cmljdGx5CnByb2hpYml0ZWQgZnJvbSB1c2luZywgY29weWluZywgYWx0ZXJpbmcs
IG9yIGRpc2Nsb3NpbmcgdGhlIGNvbnRlbnRzIG9mIHRoaXMgbWVzc2FnZS4gQXJpY2VudCBhY2Nl
cHRzIG5vIHJlc3BvbnNpYmlsaXR5IGZvciAKbG9zcyBvciBkYW1hZ2UgYXJpc2luZyBmcm9tIHRo
ZSB1c2Ugb2YgdGhlIGluZm9ybWF0aW9uIHRyYW5zbWl0dGVkIGJ5IHRoaXMgZW1haWwgaW5jbHVk
aW5nIGRhbWFnZSBmcm9tIHZpcnVzLiIK
--=_alternative 002309E76525728A_=
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkhpIEFsbCw8L2ZvbnQ+DQo8YnI+
DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPldlIGhhdmUgcmUtc3VibWl0dGVk
IGlldGYgZHJhZnQgb24gc3VwcG9ydA0KZm9yIHNlbGVjdGl2ZSBlbmNyeXB0aW9uIGluIFNSVFAg
LSB0aGlzIGRyYWZ0PC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5p
cyBlbmhhbmNlZCBiYXNlZCBvbiB0aGUgZmVlZGJhY2sgcmVjZWl2ZWQNCmZyb20gdGhlIG1haWxp
bmcgbGlzdC4gSXRzIGF2YWlsYWJsZSBhdDo8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9
InNhbnMtc2VyaWYiPiZuYnNwOzwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1z
ZXJpZiI+aHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtc21haGFqYW4t
c3J0cC1zZWxlY3RpdmUtZW5jcnlwdGlvbi0wMS50eHQ8L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQg
c2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPldvdWxkIHJlcXVlc3QgdGhlIG1lbWJlcnMgb24gdGhl
IGxpc3QNCnRvIGdvIHRocm91Z2ggdGhlIGRyYWZ0IGFuZCBwcm92aWRlIHRoZWlyIHZhbHVhYmxl
IGZlZWRiYWNrLjwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJp
ZiI+U3VtbWFyeSBvZiBjaGFuZ2VzOjwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fu
cy1zZXJpZiI+MSkgSW5jbHVkZWQgc29tZSBkZXRhaWxlZCBkZXNjcmlwdGlvbg0Kb2YgJnF1b3Q7
U2VsZWN0aXZlIEVuY3J5cHRpb24mcXVvdDsgd2l0aCBleGFtcGxlcyBvZiBib3RoIGtpbmQgb2Yg
c2VsZWN0aXZlPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJz
cDsgJm5ic3A7ICZuYnNwO2VuY3J5cHRpb24gLSBiYXNlZA0Kb24gY29udGVudCB0eXBlIGFuZCBm
cmFtZSB0eXBlPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4yKSBS
ZWFsIGxpZmUgZXhhbXBsZXMgb2YgdXNhZ2Ugb2Ygc2VsZWN0aXZlDQplbmNyeXB0aW9uPC9mb250
Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4zKSAyIG1ldGhvZHMgdG8gc3Vw
cG9ydCBTZWxlY3RpdmUgRW5jcnlwdGlvbg0KaW4gU1JUUCAtIG92ZXJsb2FkZWQgTUtJIGJpdCBh
bmQgYWRkaXRpb25hbCBwYXJhbWV0ZXI8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNh
bnMtc2VyaWYiPiZuYnNwOyAmbmJzcDsgJm5ic3A7aW4gU1JUUCB0byBpbmRpY2F0ZQ0Kc2VsZWN0
aXZlIGVuY3J5cHRpb248L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYi
PjQpIEVuaGFuY2VkICZxdW90O1NlY3VyaXR5IENvbnNpZGVyYXRpb24mcXVvdDsNCnNlY3Rpb24g
dG8gd2FybiBtaXN1c2Ugb2Ygc2VsZWN0aXZlIGVuY3J5cHRpb248L2ZvbnQ+DQo8YnI+DQo8YnI+
PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlJlZ2FyZHMsPC9mb250Pg0KPGJyPjxmb250
IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5TdW5pbCBNYWhhamFuPC9mb250Pg0KPGJyPjxmb250
IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5BUklDRU5ULCBJTkRJQTxicj4NCjxicj4NCjxicj4N
Cjxicj4NCioqKioqKioqKioqKioqKioqKioqKioqICZuYnNwO0FyaWNlbnQtVW5jbGFzc2lmaWVk
ICZuYnNwOyAqKioqKioqKioqKioqKioqKioqKioqKjxicj4NCjxicj4NCioqKioqKioqKioqKioq
KioqKioqKioqICZuYnNwO0FyaWNlbnQtVW5jbGFzc2lmaWVkICZuYnNwOyAqKioqKioqKioqKioq
KioqKioqKioqKjwvZm9udD4NCjx0YWJsZT48dHI+PHRkIGJnY29sb3I9I2ZmZmZmZj48Zm9udCBj
b2xvcj0jMDAwMDAwPjxwcmU+IkRJU0NMQUlNRVI6IFRoaXMgbWVzc2FnZSBpcyBwcm9wcmlldGFy
eSB0byBBcmljZW50ICBhbmQgaXMgaW50ZW5kZWQgc29sZWx5IGZvciB0aGUgdXNlIG9mIAp0aGUg
aW5kaXZpZHVhbCB0byB3aG9tIGl0IGlzIGFkZHJlc3NlZC4gSXQgbWF5IGNvbnRhaW4gcHJpdmls
ZWdlZCBvciBjb25maWRlbnRpYWwgaW5mb3JtYXRpb24gYW5kIHNob3VsZCBub3QgYmUgCmNpcmN1
bGF0ZWQgb3IgdXNlZCBmb3IgYW55IHB1cnBvc2Ugb3RoZXIgdGhhbiBmb3Igd2hhdCBpdCBpcyBp
bnRlbmRlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBtZXNzYWdlIGluIGVycm9yLCAKcGxl
YXNlIG5vdGlmeSB0aGUgb3JpZ2luYXRvciBpbW1lZGlhdGVseS4gSWYgeW91IGFyZSBub3QgdGhl
IGludGVuZGVkIHJlY2lwaWVudCwgeW91IGFyZSBub3RpZmllZCB0aGF0IHlvdSBhcmUgc3RyaWN0
bHkKcHJvaGliaXRlZCBmcm9tIHVzaW5nLCBjb3B5aW5nLCBhbHRlcmluZywgb3IgZGlzY2xvc2lu
ZyB0aGUgY29udGVudHMgb2YgdGhpcyBtZXNzYWdlLiBBcmljZW50IGFjY2VwdHMgbm8gcmVzcG9u
c2liaWxpdHkgZm9yIApsb3NzIG9yIGRhbWFnZSBhcmlzaW5nIGZyb20gdGhlIHVzZSBvZiB0aGUg
aW5mb3JtYXRpb24gdHJhbnNtaXR0ZWQgYnkgdGhpcyBlbWFpbCBpbmNsdWRpbmcgZGFtYWdlIGZy
b20gdmlydXMuIgo8L3ByZT48L2ZvbnQ+PC90ZD48L3RyPjwvdGFibGU+
--=_alternative 002309E76525728A_=--


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

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

--===============0384067011==--




From avt-bounces@ietf.org Thu Feb 22 03:49:58 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HK9d9-0007yj-F6; Thu, 22 Feb 2007 03:48:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HK9d8-0007yb-Q3
	for avt@ietf.org; Thu, 22 Feb 2007 03:48:46 -0500
Received: from mailf.telecomitalia.it ([156.54.233.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HK9d2-00035p-RT
	for avt@ietf.org; Thu, 22 Feb 2007 03:48:46 -0500
Received: from ptpxch008ba020.idc.cww.telecomitalia.it ([156.54.240.51]) by
	mailf.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830);
	Thu, 22 Feb 2007 09:48:36 +0100
Received: from PTPEVS108BA020.idc.cww.telecomitalia.it ([156.54.241.227]) by
	ptpxch008ba020.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 22 Feb 2007 09:48:35 +0100
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Importance: normal
Priority: normal
Content-Transfer-Encoding: quoted-printable
Subject: RE: R: [AVT] CCM draft
	review--	should"bandwidth"includetheheaderoverhead
Date: Thu, 22 Feb 2007 09:48:35 +0100
Message-ID: <E9D1028EC5C22B418B5D54CA6EA27C579A5EA5@PTPEVS108BA020.idc.cww.telecomitalia.it>
In-Reply-To: <2CA3E1B6CEC064449CAA7D0FAB46079B0297C7B1@NAEX01.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: R: [AVT] CCM draft
	review--	should"bandwidth"includetheheaderoverhead
thread-index: AcdVBz3Ox32/cs1CRn6PnWKZtOREUgAA7LOwACEgzsAAAgd9sA==
From: "Franceschini Guido" <guido.franceschini@telecomitalia.it>
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>,
	"Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-OriginalArrivalTime: 22 Feb 2007 08:48:35.0592 (UTC)
	FILETIME=[3D224880:01C7565E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hari, Magnus,

> > It is clear that inaccurate packet-rate guesses determine inaccurate
> TIDC
> > values, and that this effect is huge at the APP level, but=20
> reduced at
> the
> > IP level, for such a stack example.
>=20
> If we have to work at a common layer (IP) (which results in not so
> inaccurate TIDC values), estimating (max) packet rate is anyways
> necessary for other media types like video. In your example,=20
> the header
> overhead looks huge due to the fact that it is applied over a speech
> stream. The header overhead bit-rate of a video stream may not be
> significant when compared to actual video (RTP Payload)=20
> bit-rate alone.
> I.e., header overhead due to inaccurate video packet rate may not be
> significant. In some topologies like point 2 point, it might even be
> possible for the sender to signal its actual packet rate. Average
> measurement of header overhead can be used to correct/signal/detect
> header overhead inaccuracies.

It is true that in my example, as well as in most practical cases =
related to video, the inaccuracy due to the selection of the IP layer =
combined with a badly-guessed packetrate is negligible.
In my draft I outlined another real-life example, with a much more =
complex (and unefficient) stack, where below the IP layer there was =
still plenty of stuff, making that inaccuracy more significant. However, =
in that case the bandwidth was higher, thus a conservative approach =
would not be too much of a penalty.
Indeed, in order to prevent congestion, the terminal providing the =
bottleneck characterization is required to provide a conservative =
description, thus to assume the highest packetrate that is potentially =
possible.

The message I am trying to convey is anyway the following: when =
characterizing a bottleneck, there could be many causes that lead to an =
inaccurate description. By means of the metrics I am proposing, at least =
one of such reason (the metrics used) can be controlled.
This would apply to a large variety of protocol stacks (I am hesitant to =
say 'all' protocol stacks, but certainly many more examples that would =
be reasonably covered by picking either the media-bitrate or the =
IP-gross bitrate).
Since, in order to prevent congestion, every bottlenck description =
should stay on the safe side, the consequence of an inaccurate =
measurement is that the measurement data that is signaled would =
potentially lead to a sub-utilization of the available resources at the =
bottleneck.

If a receiver makes the perfect choice for the measurement point (e.g.: =
the PPP layer in the PSTN example) the accuracy is optimal, and the =
tuple provided allows the sender to maximally exploit the bottleneck =
resources; if the receiver makes a different choice (e.g. the IP layer) =
the accuracy is less than optimal, but the tuple it would provide is =
still neutral, i.e. transport stack protocol independent.
The sender will probably exploit a bit less of the bottleneck resources. =
The practical impact could be negligible in many cases. Thus, referring =
again to the PSTN stack example, if I have an implementation that knows =
well about its protocol stack, and provides the perfect tuple:
TIDC(PPP)=3D36
MPO(PPP)=3D48
very good.
If instead I have a more generic software that only accounts for the IP =
impact and provides the tuple <33, 40> (with an implied packetrate of =
50), then this is a bit less accurate; if my implementation finally =
provides a tuple measured at the codec level such as <17, 0> (again with =
an implied packetrate of 50), then this is quite less accurate.
The recipient of this tuple will manage the information contained in the =
tuple in a neutral manner, i.e. it does not need to know the exact stack =
at the bottleneck: its computation will be more or less optimized =
depending on the accuracy of the tuple provided, i.e. optimal if the =
tuple referred to the PPP layer, a bit less perfect if the tuple =
referred to the IP layer, potentially bad if the tuple referred to the =
media layer.

To conclude: I do not see a need for specifying the measurement point to =
be used, just an explanation showing how to obtain the maximum =
precision, how much inaccuracy would be introduced otherwise and how =
this would lead to a sub-utilization of the available resources at the =
bottleneck.

Cheers
Guido
--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons =
above and may contain confidential information. If you have received the =
message in error, be informed that any use of the content hereof is =
prohibited. Please return it immediately to the sender and delete the =
message. Should you have any questions, please contact us by replying to =
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                       =20

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



From avt-bounces@ietf.org Thu Feb 22 09:27:25 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKEt2-0002Nt-Lj; Thu, 22 Feb 2007 09:25:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKEt1-0002Ni-BE
	for avt@ietf.org; Thu, 22 Feb 2007 09:25:31 -0500
Received: from foxtrot.nab.org ([209.116.240.194] helo=nab.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKEsx-0007RN-U0
	for avt@ietf.org; Thu, 22 Feb 2007 09:25:31 -0500
Received: from ([199.29.3.25])
	by maildc2.nab.org with ESMTP  id 4028857.18075640;
	Thu, 22 Feb 2007 09:25:04 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: R: [AVT] CCM
	draftreview--	should"bandwidth"includetheheaderoverhead
Date: Thu, 22 Feb 2007 09:25:15 -0500
Message-ID: <33CB4DEADE8C734CAF59FA0B47E14C17031F329E@morse.NAB.ORG>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: R: [AVT] CCM
	draftreview--	should"bandwidth"includetheheaderoverhead
thread-index: AcdVBz3Ox32/cs1CRn6PnWKZtOREUgAA7LOwACEgzsAAAgd9sAA8n/zw
From: "Allison, Art" <AAllison@nab.org>
To: <avt@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org


When considering content flow rate control, it seems to me that the
additional complexity of adjusting the audio flow rate needs to be
considered and has not been brought up on list.
In order to enable retention of lip-synch within acceptable tolerances
the content packets (that are inside  the IP packets) need to arrive
within the buffer model design constraints.  The buffers can deal with
temporary variations, but a systemic differential change in the rate for
video and not audio could lead to, for example, audio frames arriving
early compared to video and being forced to be rendered (or dropped) due
to the need to empty the buffer. One would expect  jumps in the amount
of audio offset with respect to the video when the flow was
differentially adjusted. Experts in the tolerance allowable differ in
the allowed amount, but whatever the amount, it can be exceeded in this
scenario.

This need to keep the program elements 'close enough' in time is a total
content requirement that seems to me to indicate the signaling of one
element may introduce an additional complexity requirement in the end
receiver. If each element is controlled the receiver would seem to need
to compute how close to its buffer limits it is operating and then
signal changes in rate of the program elements differentially to retain
lip-synch. =20

Sorry, but I do not know how to translate this meta-issue into the flow
control means being discussed here; and merely suggest that those that
are expert in such consider the need for lip-synch for consumer
acceptance. =20

Art
_____________
Art Allison
Director, Advanced Engineering
Science & Technology
National Association of Broadcasters
1771 N Street, NW
Washington, D.C. 20036
Phone: 202.429.5418
Fax: 202.777.4981
aallison@nab.org

The National Association of Broadcasters is a trade association that
advocates on behalf of more than 8,300 free, local radio and television
stations and also broadcast networks before Congress, the Federal
Communications Commission and the Courts.

-----Original Message-----
From: Franceschini Guido [mailto:guido.franceschini@telecomitalia.it]=20
Sent: Thursday, February 22, 2007 3:49 AM
To: Desineni, Harikishan; Magnus Westerlund
Cc: avt@ietf.org
Subject: RE: R: [AVT] CCM draftreview--
should"bandwidth"includetheheaderoverhead

Hari, Magnus,

> > It is clear that inaccurate packet-rate guesses determine inaccurate
> TIDC
> > values, and that this effect is huge at the APP level, but
> reduced at
> the
> > IP level, for such a stack example.
>=20
> If we have to work at a common layer (IP) (which results in not so=20
> inaccurate TIDC values), estimating (max) packet rate is anyways=20
> necessary for other media types like video. In your example, the=20
> header overhead looks huge due to the fact that it is applied over a=20
> speech stream. The header overhead bit-rate of a video stream may not=20
> be significant when compared to actual video (RTP Payload) bit-rate=20
> alone.
> I.e., header overhead due to inaccurate video packet rate may not be=20
> significant. In some topologies like point 2 point, it might even be=20
> possible for the sender to signal its actual packet rate. Average=20
> measurement of header overhead can be used to correct/signal/detect=20
> header overhead inaccuracies.

It is true that in my example, as well as in most practical cases
related to video, the inaccuracy due to the selection of the IP layer
combined with a badly-guessed packetrate is negligible.
In my draft I outlined another real-life example, with a much more
complex (and unefficient) stack, where below the IP layer there was
still plenty of stuff, making that inaccuracy more significant. However,
in that case the bandwidth was higher, thus a conservative approach
would not be too much of a penalty.
Indeed, in order to prevent congestion, the terminal providing the
bottleneck characterization is required to provide a conservative
description, thus to assume the highest packetrate that is potentially
possible.

The message I am trying to convey is anyway the following: when
characterizing a bottleneck, there could be many causes that lead to an
inaccurate description. By means of the metrics I am proposing, at least
one of such reason (the metrics used) can be controlled.
This would apply to a large variety of protocol stacks (I am hesitant to
say 'all' protocol stacks, but certainly many more examples that would
be reasonably covered by picking either the media-bitrate or the
IP-gross bitrate).
Since, in order to prevent congestion, every bottlenck description
should stay on the safe side, the consequence of an inaccurate
measurement is that the measurement data that is signaled would
potentially lead to a sub-utilization of the available resources at the
bottleneck.

If a receiver makes the perfect choice for the measurement point (e.g.:
the PPP layer in the PSTN example) the accuracy is optimal, and the
tuple provided allows the sender to maximally exploit the bottleneck
resources; if the receiver makes a different choice (e.g. the IP layer)
the accuracy is less than optimal, but the tuple it would provide is
still neutral, i.e. transport stack protocol independent.
The sender will probably exploit a bit less of the bottleneck resources.
The practical impact could be negligible in many cases. Thus, referring
again to the PSTN stack example, if I have an implementation that knows
well about its protocol stack, and provides the perfect tuple:
TIDC(PPP)=3D36
MPO(PPP)=3D48
very good.
If instead I have a more generic software that only accounts for the IP
impact and provides the tuple <33, 40> (with an implied packetrate of
50), then this is a bit less accurate; if my implementation finally
provides a tuple measured at the codec level such as <17, 0> (again with
an implied packetrate of 50), then this is quite less accurate.
The recipient of this tuple will manage the information contained in the
tuple in a neutral manner, i.e. it does not need to know the exact stack
at the bottleneck: its computation will be more or less optimized
depending on the accuracy of the tuple provided, i.e. optimal if the
tuple referred to the PPP layer, a bit less perfect if the tuple
referred to the IP layer, potentially bad if the tuple referred to the
media layer.

To conclude: I do not see a need for specifying the measurement point to
be used, just an explanation showing how to obtain the maximum
precision, how much inaccuracy would be introduced otherwise and how
this would lead to a sub-utilization of the available resources at the
bottleneck.

Cheers
Guido
--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received the
message in error, be informed that any use of the content hereof is
prohibited. Please return it immediately to the sender and delete the
message. Should you have any questions, please contact us by replying to
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                       =20

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

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



From avt-bounces@ietf.org Thu Feb 22 10:37:33 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKG00-00072z-J9; Thu, 22 Feb 2007 10:36:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKFzy-00072t-JY
	for avt@ietf.org; Thu, 22 Feb 2007 10:36:46 -0500
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKFzw-00043u-8g
	for avt@ietf.org; Thu, 22 Feb 2007 10:36:46 -0500
Received: from postgrad1.arts.gla.ac.uk ([130.209.98.104]:59544
	helo=[192.168.3.121])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HKFzu-0005DG-8Y; Thu, 22 Feb 2007 15:36:42 +0000
Mime-Version: 1.0 (Apple Message framework v752.2)
References: <E1HJtjG-0008Sb-2b@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <32889E24-D6F0-4EED-8C1E-D1E8B4675FF2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Thu, 22 Feb 2007 15:33:28 +0000
To: yusuke hiwasaki <hiwasaki.yusuke@lab.ntt.co.jp>,
	ohmuro.hitoshi@lab.ntt.co.jp
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: IETF AVT WG <avt@ietf.org>
Subject: [AVT] Fwd: I-D ACTION:draft-hiwasaki-avt-rtp-uemclip-01.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Begin forwarded message:
> From: Internet-Drafts@ietf.org
> Date: 21 February 2007 15:50:02 GMT
> To: i-d-announce@ietf.org
> Subject: I-D ACTION:draft-hiwasaki-avt-rtp-uemclip-01.txt
> Reply-To: internet-drafts@ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
> 	Title		: RTP payload format for UEMCLIP speech codec
> 	Author(s)	: Y. Hiwasaki, H. Ohmuro
> 	Filename	: draft-hiwasaki-avt-rtp-uemclip-01.txt
> 	Pages		: 25
> 	Date		: 2007-2-21
> 	
> This document describes the RTP payload format of an ITU-T G.711
>    enhanced speech codec, UEMCLIP.  The bitstream has a scalable
>    structure with an embedded u-Law bitstream, also known as PCMU,  
> thus
>    providing a handy transcoding operation between narrowband and
>    wideband speech.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-hiwasaki-avt-rtp- 
> uemclip-01.txt

I have two RTP-usage questions relating to this draft:

1) The RTP timestamp rate is specified as being 50 kHz, yet the audio  
sampling rate for this codec is either 8 or 16 kHz (with 32 kHz as a  
possible extension). Given this, would it not make more sense for the  
RTP timestamp rate to be 32 kHz?

2) Does the codec not support silence suppression? The draft mandates  
the marker bit not be used, which is surprising.

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



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



From avt-bounces@ietf.org Thu Feb 22 11:11:58 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKGX8-0002uH-8v; Thu, 22 Feb 2007 11:11:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKGX6-0002u9-Pb
	for avt@ietf.org; Thu, 22 Feb 2007 11:11:00 -0500
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HKGX5-0001Ex-H6 for avt@ietf.org; Thu, 22 Feb 2007 11:11:00 -0500
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 Feb 2007 11:10:59 -0500
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Fwd: I-D ACTION:draft-hiwasaki-avt-rtp-uemclip-01.txt
References: <E1HJtjG-0008Sb-2b@stiedprstage1.ietf.org>
	<32889E24-D6F0-4EED-8C1E-D1E8B4675FF2@csperkins.org>
From: Randell Jesup <rjesup@wgate.com>
Date: Thu, 22 Feb 2007 11:10:57 -0500
In-Reply-To: <32889E24-D6F0-4EED-8C1E-D1E8B4675FF2@csperkins.org> (Colin
	Perkins's message of "Thu, 22 Feb 2007 15:33:28 +0000")
Message-ID: <ybu4ppemaum.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 22 Feb 2007 16:10:59.0256 (UTC)
	FILETIME=[0A63FB80:01C7569C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: IETF AVT WG <avt@ietf.org>, yusuke hiwasaki <hiwasaki.yusuke@lab.ntt.co.jp>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Colin Perkins <csp@csperkins.org> writes:
>> 	Title		: RTP payload format for UEMCLIP speech codec
>> 	Author(s)	: Y. Hiwasaki, H. Ohmuro
>> 	Filename	: draft-hiwasaki-avt-rtp-uemclip-01.txt
>> 	Pages		: 25
>> 	Date		: 2007-2-21
>> 	
>> This document describes the RTP payload format of an ITU-T G.711
>>    enhanced speech codec, UEMCLIP.  The bitstream has a scalable
>>    structure with an embedded u-Law bitstream, also known as PCMU,  thus
>>    providing a handy transcoding operation between narrowband and
>>    wideband speech.

>I have two RTP-usage questions relating to this draft:
>
>1) The RTP timestamp rate is specified as being 50 kHz, yet the audio
>sampling rate for this codec is either 8 or 16 kHz (with 32 kHz as a
>possible extension). Given this, would it not make more sense for the  RTP
>timestamp rate to be 32 kHz?

If all the scalable rates are multiples of 8KHz, I would expect the
timestamp rate to also be a multiple of that to avoid rounding errors and
jitter.  Perhaps 32000, or 64000, would be more appropriate?  (Are there
other possible sampling rates beyond 8/16/32?)

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


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



From avt-bounces@ietf.org Thu Feb 22 12:17:53 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKHYX-0006IO-MU; Thu, 22 Feb 2007 12:16:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKHYW-0006Hd-6Y
	for avt@ietf.org; Thu, 22 Feb 2007 12:16:32 -0500
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKHYU-0002sC-SR
	for avt@ietf.org; Thu, 22 Feb 2007 12:16:32 -0500
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:59798)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HKHYJ-0003Cr-He; Thu, 22 Feb 2007 17:16:19 +0000
In-Reply-To: <ybu4ppemaum.fsf@jesup.eng.wgate.com>
References: <E1HJtjG-0008Sb-2b@stiedprstage1.ietf.org>
	<32889E24-D6F0-4EED-8C1E-D1E8B4675FF2@csperkins.org>
	<ybu4ppemaum.fsf@jesup.eng.wgate.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B09EA99B-5B7E-4F66-9969-6C4ADC368BBF@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Fwd: I-D ACTION:draft-hiwasaki-avt-rtp-uemclip-01.txt
Date: Thu, 22 Feb 2007 17:16:18 +0000
To: Randell Jesup <rjesup@wgate.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: IETF AVT WG <avt@ietf.org>, yusuke hiwasaki <hiwasaki.yusuke@lab.ntt.co.jp>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On 22 Feb 2007, at 16:10, Randell Jesup wrote:
> Colin Perkins <csp@csperkins.org> writes:
>>> 	Title		: RTP payload format for UEMCLIP speech codec
>>> 	Author(s)	: Y. Hiwasaki, H. Ohmuro
>>> 	Filename	: draft-hiwasaki-avt-rtp-uemclip-01.txt
>>> 	Pages		: 25
>>> 	Date		: 2007-2-21
>>> 	
>>> This document describes the RTP payload format of an ITU-T G.711
>>>    enhanced speech codec, UEMCLIP.  The bitstream has a scalable
>>>    structure with an embedded u-Law bitstream, also known as  
>>> PCMU,  thus
>>>    providing a handy transcoding operation between narrowband and
>>>    wideband speech.
>
>> I have two RTP-usage questions relating to this draft:
>>
>> 1) The RTP timestamp rate is specified as being 50 kHz, yet the audio
>> sampling rate for this codec is either 8 or 16 kHz (with 32 kHz as a
>> possible extension). Given this, would it not make more sense for  
>> the  RTP
>> timestamp rate to be 32 kHz?
>
> If all the scalable rates are multiples of 8KHz, I would expect the
> timestamp rate to also be a multiple of that to avoid rounding  
> errors and
> jitter.  Perhaps 32000, or 64000, would be more appropriate?  (Are  
> there
> other possible sampling rates beyond 8/16/32?)

Right - that was my point.

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



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



From avt-bounces@ietf.org Thu Feb 22 13:31:16 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKIhe-0001Y7-3O; Thu, 22 Feb 2007 13:30:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKIhc-0001Xd-KJ
	for avt@ietf.org; Thu, 22 Feb 2007 13:30:00 -0500
Received: from bay0-omc1-s9.bay0.hotmail.com ([65.54.246.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKIhU-0007H5-9K
	for avt@ietf.org; Thu, 22 Feb 2007 13:30:00 -0500
Received: from hotmail.com ([64.4.56.48]) by bay0-omc1-s9.bay0.hotmail.com
	with Microsoft SMTPSVC(6.0.3790.2668); 
	Thu, 22 Feb 2007 10:29:52 -0800
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Thu, 22 Feb 2007 10:29:51 -0800
Message-ID: <BAY101-F389E28EE72B7EE9B381353D98F0@phx.gbl>
Received: from 64.4.56.244 by by101fd.bay101.hotmail.msn.com with HTTP;
	Thu, 22 Feb 2007 18:29:47 GMT
X-Originating-IP: [199.171.212.100]
X-Originating-Email: [jcanas2000@hotmail.com]
X-Sender: jcanas2000@hotmail.com
From: "Jorge Canas" <jcanas2000@hotmail.com>
To: avt@ietf.org
Bcc: 
Date: Thu, 22 Feb 2007 13:29:47 -0500
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
X-OriginalArrivalTime: 22 Feb 2007 18:29:51.0385 (UTC)
	FILETIME=[70B9F890:01C756AF]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Subject: [AVT] Duplicate RTP packets
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hello,

I have searched RFC 3550, but can't find an answer to the following 
questions:

Are RTP stacks required to drop received RTP packets with the same RTP 
sequence number (duplicate RTP packets)?  If so, how much history (in number 
of packets) does the RTP stack need to maintain in order to detect 
duplicates? Or is it only required to detect duplicates arriving piggy 
backed?

If the RTP stack is not required to drop those packets, I guess the 
application is expected to deal with duplicates?

Regards,

Jorge

_________________________________________________________________
The average US Credit Score is 675. The cost to see yours: $0 by Experian. 
http://www.freecreditreport.com/pm/default.aspx?sc=660600&bcd=EMAILFOOTERAVERAGE


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



From avt-bounces@ietf.org Thu Feb 22 22:24:49 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKR1l-0001VM-1h; Thu, 22 Feb 2007 22:23:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKR1j-0001VH-IM
	for avt@ietf.org; Thu, 22 Feb 2007 22:23:19 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKR1h-0007x0-MO
	for avt@ietf.org; Thu, 22 Feb 2007 22:23:19 -0500
Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l1N3NFdK014886
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 22 Feb 2007 19:23:16 -0800
Received: from SANEXCAS02.na.qualcomm.com (sanexcas02.qualcomm.com
	[172.30.36.176])
	by hamtaro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l1N3NFwt006875; Thu, 22 Feb 2007 19:23:15 -0800 (PST)
Received: from NAEX01.qualcomm.com ([129.46.51.60]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 22 Feb 2007 19:23:15 -0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: R: [AVT]
	CCMdraftreview--	should"bandwidth"includetheheaderoverhead
Date: Thu, 22 Feb 2007 19:23:20 -0800
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B0297CA3F@NAEX01.na.qualcomm.com>
In-Reply-To: <33CB4DEADE8C734CAF59FA0B47E14C17031F329E@morse.NAB.ORG>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: R: [AVT]
	CCMdraftreview--	should"bandwidth"includetheheaderoverhead
Thread-Index: AcdVBz3Ox32/cs1CRn6PnWKZtOREUgAA7LOwACEgzsAAAgd9sAA8n/zwABmoANA=
References: <33CB4DEADE8C734CAF59FA0B47E14C17031F329E@morse.NAB.ORG>
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: "Allison, Art" <AAllison@nab.org>, <avt@ietf.org>
X-OriginalArrivalTime: 23 Feb 2007 03:23:15.0080 (UTC)
	FILETIME=[F46A4880:01C756F9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ba0d4c5f57f7c289496fce758bbf4798
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org



> -----Original Message-----
> From: Allison, Art [mailto:AAllison@nab.org]
> Sent: Thursday, February 22, 2007 6:25 AM
> To: avt@ietf.org
> Subject: RE: R: [AVT] CCMdraftreview--
> should"bandwidth"includetheheaderoverhead
>=20
>=20
> When considering content flow rate control, it seems to me that the
> additional complexity of adjusting the audio flow rate needs to be
> considered and has not been brought up on list.

This is an important point which usually gets ignored while
concentrating on rate control for just one type of media.

> In order to enable retention of lip-synch within acceptable tolerances
> the content packets (that are inside  the IP packets) need to arrive
> within the buffer model design constraints.  The buffers can deal with
> temporary variations, but a systemic differential change in the rate
for
> video and not audio could lead to, for example, audio frames arriving
> early compared to video and being forced to be rendered (or dropped)
due
> to the need to empty the buffer. One would expect  jumps in the amount
> of audio offset with respect to the video when the flow was
> differentially adjusted. Experts in the tolerance allowable differ in
> the allowed amount, but whatever the amount, it can be exceeded in
this
> scenario.
>=20

I agree with this. This problem can easily show up if a sender is
attempting to adjust only one type of media rate without considering the
overall impact on other streams. Adjusting the rate does not guarantee
that packet arrive on time for proper synchronized play-out at the
receiver. I believed this is partly addressed in Guido's draft(Guido,
can you comment?) and totally ignored by codec control messages and
TMMBR.

When one of the media streams to be synchronized is arriving late and
some of it is not rendered due to lip-sync constraints, it can have a
huge impact on user experience. A sender will not know this unless the
receiver can inform it back to the sender in some way.

*This cannot be reported as packet loss. Also, packet loss does not mean
that packets of a given stream are not arriving on time for proper
synchronization. There can be occasional packet loss even when all
others packets arrive before the target time and get synchronized
properly.

*Existing RTCP messages like Inter-arrival jitter do not capture such
problems. Inter-arrival jitter takes time to converge and it is not
reliable to quickly detect late arrival of media packets. Packets can be
late and still result in *not to worry* values of inter-arrival jitter.
This is fundamentally due to the fact the inter-arrival jitter is just
relative spacing between consecutive packets and not the overall delay
experienced by the media packets. The inter-arrival formula in RFC3550
runs over the life time of the session and values of it are sampled just
at the time of reporting. Assuming that media packets are delayed based
on inter-arrival jitter (IJ) can be too wild a guess. From IJ, it is not
possible to estimate the extent to which the packets are getting delayed
at the receiver. A receiver would want to report this late arrival
problem to a sender as and when the experienced delay is approaching
unacceptable boundaries. This can let a sender take quick action get the
overall user experience at the receiver under control.

*Another point is some implementations use elastic buffers which will
dynamically change their depth in order to adapt to changing packet
arrival patterns. This could in-turn have impact on synchronization
target that a receiver is attempting to maintain

* Many details (changing depth, synchronization target) in media
de-jitter buffers are implementation specific. It is not practical to
expect a sender to know all these details about a receiver's de-jitter
buffer.


> This need to keep the program elements 'close enough' in time is a
total
> content requirement that seems to me to indicate the signaling of one
> element may introduce an additional complexity requirement in the end
> receiver.
> If each element is controlled the receiver would seem to need
> to compute how close to its buffer limits it is operating and then
> signal changes in rate of the program elements differentially to
retain
> lip-synch.

This is another important point. Making a receiver report how close the
program elements are seems like a good approach to let a sender know
about the overall experience at the receiver's media buffers. Receiver
can even operate at finer level and report how delayed or early a
particular program element has arrived into its buffers. As an
optimization, receiver can tell the sender only when particular program
elements over a period of time are slowly approaching unacceptable
delay. A sender can take some actions until receiver starts complaining
or until the receiver says it is receiving everything on time.

> Sorry, but I do not know how to translate this meta-issue into the
flow
> control means being discussed here; and merely suggest that those that
> are expert in such consider the need for lip-synch for consumer
> acceptance.

I think you have an important here which is not captured by TMMBR and I
believe it is addressed to some extent in Guido's draft (Guido, can you
comment?). I'll try to capture the above discussion into a draft and
make sure that your point gets discussed.

>=20
> Art
> _____________
> Art Allison
> Director, Advanced Engineering
> Science & Technology
> National Association of Broadcasters
> 1771 N Street, NW
> Washington, D.C. 20036
> Phone: 202.429.5418
> Fax: 202.777.4981
> aallison@nab.org
>=20
> The National Association of Broadcasters is a trade association that
> advocates on behalf of more than 8,300 free, local radio and
television
> stations and also broadcast networks before Congress, the Federal
> Communications Commission and the Courts.
>=20
> -----Original Message-----
> From: Franceschini Guido [mailto:guido.franceschini@telecomitalia.it]
> Sent: Thursday, February 22, 2007 3:49 AM
> To: Desineni, Harikishan; Magnus Westerlund
> Cc: avt@ietf.org
> Subject: RE: R: [AVT] CCM draftreview--
> should"bandwidth"includetheheaderoverhead
>=20
> Hari, Magnus,
>=20
> > > It is clear that inaccurate packet-rate guesses determine
inaccurate
> > TIDC
> > > values, and that this effect is huge at the APP level, but
> > reduced at
> > the
> > > IP level, for such a stack example.
> >
> > If we have to work at a common layer (IP) (which results in not so
> > inaccurate TIDC values), estimating (max) packet rate is anyways
> > necessary for other media types like video. In your example, the
> > header overhead looks huge due to the fact that it is applied over a
> > speech stream. The header overhead bit-rate of a video stream may
not
> > be significant when compared to actual video (RTP Payload) bit-rate
> > alone.
> > I.e., header overhead due to inaccurate video packet rate may not be
> > significant. In some topologies like point 2 point, it might even be
> > possible for the sender to signal its actual packet rate. Average
> > measurement of header overhead can be used to correct/signal/detect
> > header overhead inaccuracies.
>=20
> It is true that in my example, as well as in most practical cases
> related to video, the inaccuracy due to the selection of the IP layer
> combined with a badly-guessed packetrate is negligible.
> In my draft I outlined another real-life example, with a much more
> complex (and unefficient) stack, where below the IP layer there was
> still plenty of stuff, making that inaccuracy more significant.
However,
> in that case the bandwidth was higher, thus a conservative approach
> would not be too much of a penalty.
> Indeed, in order to prevent congestion, the terminal providing the
> bottleneck characterization is required to provide a conservative
> description, thus to assume the highest packetrate that is potentially
> possible.
>=20
> The message I am trying to convey is anyway the following: when
> characterizing a bottleneck, there could be many causes that lead to
an
> inaccurate description. By means of the metrics I am proposing, at
least
> one of such reason (the metrics used) can be controlled.
> This would apply to a large variety of protocol stacks (I am hesitant
to
> say 'all' protocol stacks, but certainly many more examples that would
> be reasonably covered by picking either the media-bitrate or the
> IP-gross bitrate).
> Since, in order to prevent congestion, every bottlenck description
> should stay on the safe side, the consequence of an inaccurate
> measurement is that the measurement data that is signaled would
> potentially lead to a sub-utilization of the available resources at
the
> bottleneck.
>=20
> If a receiver makes the perfect choice for the measurement point
(e.g.:
> the PPP layer in the PSTN example) the accuracy is optimal, and the
> tuple provided allows the sender to maximally exploit the bottleneck
> resources; if the receiver makes a different choice (e.g. the IP
layer)
> the accuracy is less than optimal, but the tuple it would provide is
> still neutral, i.e. transport stack protocol independent.
> The sender will probably exploit a bit less of the bottleneck
resources.
> The practical impact could be negligible in many cases. Thus,
referring
> again to the PSTN stack example, if I have an implementation that
knows
> well about its protocol stack, and provides the perfect tuple:
> TIDC(PPP)=3D36
> MPO(PPP)=3D48
> very good.
> If instead I have a more generic software that only accounts for the
IP
> impact and provides the tuple <33, 40> (with an implied packetrate of
> 50), then this is a bit less accurate; if my implementation finally
> provides a tuple measured at the codec level such as <17, 0> (again
with
> an implied packetrate of 50), then this is quite less accurate.
> The recipient of this tuple will manage the information contained in
the
> tuple in a neutral manner, i.e. it does not need to know the exact
stack
> at the bottleneck: its computation will be more or less optimized
> depending on the accuracy of the tuple provided, i.e. optimal if the
> tuple referred to the PPP layer, a bit less perfect if the tuple
> referred to the IP layer, potentially bad if the tuple referred to the
> media layer.
>=20
> To conclude: I do not see a need for specifying the measurement point
to
> be used, just an explanation showing how to obtain the maximum
> precision, how much inaccuracy would be introduced otherwise and how
> this would lead to a sub-utilization of the available resources at the
> bottleneck.
>=20
> Cheers
> Guido
> --------------------------------------------------------------------
>=20
> CONFIDENTIALITY NOTICE
>=20
> This message and its attachments are addressed solely to the persons
> above and may contain confidential information. If you have received
the
> message in error, be informed that any use of the content hereof is
> prohibited. Please return it immediately to the sender and delete the
> message. Should you have any questions, please contact us by replying
to
> webmaster@telecomitalia.it.
>=20
>         Thank you
>=20
>                                         www.telecomitalia.it
>=20
> --------------------------------------------------------------------
>=20
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

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



From avt-bounces@ietf.org Fri Feb 23 03:17:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKVaa-0006Wl-4M; Fri, 23 Feb 2007 03:15:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKVaY-0006VQ-Lc
	for avt@ietf.org; Fri, 23 Feb 2007 03:15:34 -0500
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKVaV-00061o-VJ
	for avt@ietf.org; Fri, 23 Feb 2007 03:15:34 -0500
Received: from mfs34.rdh.ecl.ntt.co.jp (mfs34.rdh.ecl.ntt.co.jp
	[129.60.39.114])
	by tama5.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l1N8FLl0025508;
	Fri, 23 Feb 2007 17:15:24 +0900 (JST)
Received: from mfs34.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by mfs34.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id B3A0120AE3A;
	Fri, 23 Feb 2007 17:15:23 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp (nttmail3.ecl.ntt.co.jp [129.60.39.100])
	by mfs34.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id CE50120AE2F;
	Fri, 23 Feb 2007 17:15:22 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp
	[129.60.5.69])
	by nttmail3.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l1N8FMuU000922; 
	Fri, 23 Feb 2007 17:15:22 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	l1N8FM13004997; Fri, 23 Feb 2007 17:15:22 +0900 (JST)
Received: from imi.m.ecl.ntt.co.jp (imi0.m.ecl.ntt.co.jp [129.60.5.147])
	by eclscan3.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	l1N8FLfH004986; Fri, 23 Feb 2007 17:15:21 +0900 (JST)
Received: from sp-abarth.splab.ecl.ntt.co.jp.lab.ntt.co.jp
	(sp-abarth.splab.ecl.ntt.co.jp [129.60.2.79])
	by imi.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l1N8FLcZ008452;
	Fri, 23 Feb 2007 17:15:21 +0900 (JST)
Date: Fri, 23 Feb 2007 17:14:29 +0900
Message-ID: <m33b4x8f4q.wl%hiwasaki.yusuke@lab.ntt.co.jp>
From: yusuke hiwasaki <hiwasaki.yusuke@lab.ntt.co.jp>
To: IETF AVT WG <avt@ietf.org>, Colin Perkins <csp@csperkins.org>,
	Randell Jesup <rjesup@wgate.com>
Subject: Re: [AVT] Fwd: I-D ACTION:draft-hiwasaki-avt-rtp-uemclip-01.txt
In-Reply-To: <B09EA99B-5B7E-4F66-9969-6C4ADC368BBF@csperkins.org>
References: <E1HJtjG-0008Sb-2b@stiedprstage1.ietf.org>
	<32889E24-D6F0-4EED-8C1E-D1E8B4675FF2@csperkins.org>
	<ybu4ppemaum.fsf@jesup.eng.wgate.com>
	<B09EA99B-5B7E-4F66-9969-6C4ADC368BBF@csperkins.org>
User-Agent: User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: NTT Cyber Space Laboratories
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: yusuke hiwasaki <hiwasaki.yusuke@lab.ntt.co.jp>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi Colin, Randell, and all,

Thank you very much for prompt feed back, and pointing out the faults.

Regarding the questions raised by Colin:

(1) Time-stamp rate: It should be multiples of 8 kHz. The figure
    should change depending on the modes described in Table 2 (or is
    it better be fixed?). This will be fixed in the next version.

(2) Marker bit: Initially, we were not thinking of using DTXs, because
    it sometimes (and only sometimes) introduces degradation, but of
    couse one should not prohibit using it (besides, DTXs are one of
    the advantages of using RTP). Perhaps description on this item in
    Section 3.1 should read something like:

      If the codec is used for applications with discontinuous
      transmission (DTX, or silence compression), the first packet
      after a silence period during which packets have not been
      transmitted contiguously SHOULD have the marker bit in the RTP
      data header set to one. The marker bit in all other packets MUST
      be zero. Applications without DTX MUST set the marker bit to
      zero.

By the way, reading through my draft again, I noticed that there are
no descriptions on when one or more frames are fitted in an RTP
packet. In the next version, I will add another section on this, too.

Cheers,
yusuke
============
Yusuke Hiwasaki, NTT Cyber Space Labs.
hiwasaki.yusuke@lab.ntt.co.jp
Tel: +81-422-59-4815 (Fax: +81-422-60-7811)

At Thu, 22 Feb 2007 17:16:18 +0000,
Colin Perkins wrote:
> 
> On 22 Feb 2007, at 16:10, Randell Jesup wrote:
> > Colin Perkins <csp@csperkins.org> writes:
> >>> 	Title		: RTP payload format for UEMCLIP speech codec
> >>> 	Author(s)	: Y. Hiwasaki, H. Ohmuro
> >>> 	Filename	: draft-hiwasaki-avt-rtp-uemclip-01.txt
> >>> 	Pages		: 25
> >>> 	Date		: 2007-2-21
> >>> 	
> >>> This document describes the RTP payload format of an ITU-T G.711
> >>>    enhanced speech codec, UEMCLIP.  The bitstream has a scalable
> >>>    structure with an embedded u-Law bitstream, also known as  
> >>> PCMU,  thus
> >>>    providing a handy transcoding operation between narrowband and
> >>>    wideband speech.
> >
> >> I have two RTP-usage questions relating to this draft:
> >>
> >> 1) The RTP timestamp rate is specified as being 50 kHz, yet the audio
> >> sampling rate for this codec is either 8 or 16 kHz (with 32 kHz as a
> >> possible extension). Given this, would it not make more sense for  
> >> the  RTP
> >> timestamp rate to be 32 kHz?
> >
> > If all the scalable rates are multiples of 8KHz, I would expect the
> > timestamp rate to also be a multiple of that to avoid rounding  
> > errors and
> > jitter.  Perhaps 32000, or 64000, would be more appropriate?  (Are  
> > there
> > other possible sampling rates beyond 8/16/32?)
> 
> Right - that was my point.
> 
> -- 
> Colin Perkins
> http://csperkins.org/
> 
> 
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

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



From avt-bounces@ietf.org Fri Feb 23 03:23:51 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKVhf-00048j-SF; Fri, 23 Feb 2007 03:22:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKVhe-00043B-C3
	for avt@ietf.org; Fri, 23 Feb 2007 03:22:54 -0500
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKVhd-00083q-2Q
	for avt@ietf.org; Fri, 23 Feb 2007 03:22:54 -0500
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:63659
	helo=[192.168.0.3])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HKVha-0003as-U5; Fri, 23 Feb 2007 08:22:51 +0000
In-Reply-To: <m33b4x8f4q.wl%hiwasaki.yusuke@lab.ntt.co.jp>
References: <E1HJtjG-0008Sb-2b@stiedprstage1.ietf.org>
	<32889E24-D6F0-4EED-8C1E-D1E8B4675FF2@csperkins.org>
	<ybu4ppemaum.fsf@jesup.eng.wgate.com>
	<B09EA99B-5B7E-4F66-9969-6C4ADC368BBF@csperkins.org>
	<m33b4x8f4q.wl%hiwasaki.yusuke@lab.ntt.co.jp>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <540848BB-2C68-4CC4-BB88-8CA48ECCCA01@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Fwd: I-D ACTION:draft-hiwasaki-avt-rtp-uemclip-01.txt
Date: Fri, 23 Feb 2007 08:22:48 +0000
To: yusuke hiwasaki <hiwasaki.yusuke@lab.ntt.co.jp>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: Randell Jesup <rjesup@wgate.com>, IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On 23 Feb 2007, at 08:14, yusuke hiwasaki wrote:
> Regarding the questions raised by Colin:
>
> (1) Time-stamp rate: It should be multiples of 8 kHz. The figure
>     should change depending on the modes described in Table 2 (or is
>     it better be fixed?). This will be fixed in the next version.

If the sampling rate can change during a session, the RTP timestamp  
rate should be equal to the maximum rate. Otherwise, it should equal  
the actual rate.

> (2) Marker bit: Initially, we were not thinking of using DTXs, because
>     it sometimes (and only sometimes) introduces degradation, but of
>     couse one should not prohibit using it (besides, DTXs are one of
>     the advantages of using RTP). Perhaps description on this item in
>     Section 3.1 should read something like:
>
>       If the codec is used for applications with discontinuous
>       transmission (DTX, or silence compression), the first packet
>       after a silence period during which packets have not been
>       transmitted contiguously SHOULD have the marker bit in the RTP
>       data header set to one. The marker bit in all other packets MUST
>       be zero. Applications without DTX MUST set the marker bit to
>       zero.

These changes would address my concerns. Thanks!

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



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



From avt-bounces@ietf.org Fri Feb 23 03:29:08 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKVmk-0006O9-G5; Fri, 23 Feb 2007 03:28:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKVmi-0006NP-Pj
	for avt@ietf.org; Fri, 23 Feb 2007 03:28:08 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKVmY-0000yf-4O
	for avt@ietf.org; Fri, 23 Feb 2007 03:28:08 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	566D12092D; Fri, 23 Feb 2007 09:27:51 +0100 (CET)
X-AuditID: c1b4fb3c-b17cbbb0000007de-92-45dea5876418 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	440E32092A; Fri, 23 Feb 2007 09:27:51 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 23 Feb 2007 09:27:50 +0100
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 23 Feb 2007 09:27:50 +0100
Message-ID: <45DEA585.4050808@ericsson.com>
Date: Fri, 23 Feb 2007 09:27:49 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Dave Singer <singer@apple.com>
Subject: Re: [AVT] Re: ABNF in draft-ietf-avt-smpte-rtp-08.txt
References: <45DC716D.3060409@nortel.com>	<p06230905c202362c0f1d@[10.101.201.85]>
	<45DC9130.4070101@nortel.com>
	<p0623090ac20242b4fef6@[10.101.201.85]>
In-Reply-To: <p0623090ac20242b4fef6@[10.101.201.85]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Feb 2007 08:27:50.0367 (UTC)
	FILETIME=[8155C6F0:01C75724]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: avt@ietf.org, Tom-PT Taylor <taylor@nortel.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Regarding ABNF. There are a lot of different variants to ABNF/BNF. One 
should use only one, and that one is the one documented in RFC 4234. It 
is also highly recommended that one checks the ABNF one has created in 
for example Bill Fenner's online syntax check. It is linked from the 
very useful verification tool webpage:

http://tools.ietf.org/inventory/verif-tools

Cheers

Magnus

Dave Singer skrev:
> At 13:36  -0500 21/02/07, Tom-PT Taylor wrote:
>> Look at the first paragraph, last line, of section 7 of [hdrext]. Then 
>> decide how you want to go -- change [hdrext], change [smpte], or do 
>> nothing (though as I say, this last is undesirable).
> 
> I'll remove "separated by spaces", thanks.  It's gratuitous.
> 
>>
>> Dave Singer wrote:
>>> At 11:21  -0500 21/02/07, Tom-PT Taylor wrote:
>> ...
>>
>>>
>>>> I also note a discrepancy (legal, but undesirable) between the 
>>>> complete extensionattributes string and its definition as a series 
>>>> of space-separated parameters in [hdrext].
>>>
>>> No, hdrext merely says that it is separated from the URI by a space. 
>>> Or did I write something I didn't intend?
>>>
>>>> Would you consider replacing the "/" separator by space as defined 
>>>> in [hdrext]? Or is [hdrext] wrong in specifying space as a separator?
>>>
>>> as I say, unless I missed something, I don't think it necessary.
>>>
>> ...
> 
> 


-- 

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



From avt-bounces@ietf.org Fri Feb 23 03:45:30 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKW2t-0002Vu-Ro; Fri, 23 Feb 2007 03:44:51 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKW2s-0002Ul-7l
	for avt@ietf.org; Fri, 23 Feb 2007 03:44:50 -0500
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKW2k-0004lm-QO
	for avt@ietf.org; Fri, 23 Feb 2007 03:44:50 -0500
Received: from mfs4.rdh.ecl.ntt.co.jp (mfs4.rdh.ecl.ntt.co.jp [129.60.39.113])
	by tama5.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l1N8iZak014548; 
	Fri, 23 Feb 2007 17:44:35 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp (nttmail3.ecl.ntt.co.jp [129.60.39.100])
	by mfs4.rdh.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	l1N8iYKN012152; Fri, 23 Feb 2007 17:44:34 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp
	[129.60.5.69])
	by nttmail3.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l1N8iYY6014527; 
	Fri, 23 Feb 2007 17:44:34 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	l1N8iY3P020333; Fri, 23 Feb 2007 17:44:34 +0900 (JST)
Received: from imi.m.ecl.ntt.co.jp (imi0.m.ecl.ntt.co.jp [129.60.5.147])
	by eclscan3.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	l1N8iYQQ020330; Fri, 23 Feb 2007 17:44:34 +0900 (JST)
Received: from sp-abarth.splab.ecl.ntt.co.jp.lab.ntt.co.jp
	(sp-abarth.splab.ecl.ntt.co.jp [129.60.2.79])
	by imi.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l1N8iXwR011889;
	Fri, 23 Feb 2007 17:44:33 +0900 (JST)
Date: Fri, 23 Feb 2007 17:43:41 +0900
Message-ID: <m31wkh8ds2.wl%hiwasaki.yusuke@lab.ntt.co.jp>
From: yusuke hiwasaki <hiwasaki.yusuke@lab.ntt.co.jp>
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Fwd: I-D ACTION:draft-hiwasaki-avt-rtp-uemclip-01.txt
In-Reply-To: <540848BB-2C68-4CC4-BB88-8CA48ECCCA01@csperkins.org>
References: <E1HJtjG-0008Sb-2b@stiedprstage1.ietf.org>
	<32889E24-D6F0-4EED-8C1E-D1E8B4675FF2@csperkins.org>
	<ybu4ppemaum.fsf@jesup.eng.wgate.com>
	<B09EA99B-5B7E-4F66-9969-6C4ADC368BBF@csperkins.org>
	<m33b4x8f4q.wl%hiwasaki.yusuke@lab.ntt.co.jp>
	<540848BB-2C68-4CC4-BB88-8CA48ECCCA01@csperkins.org>
User-Agent: User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: NTT Cyber Space Laboratories
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: Randell Jesup <rjesup@wgate.com>, IETF AVT WG <avt@ietf.org>,
	yusuke hiwasaki <hiwasaki.yusuke@lab.ntt.co.jp>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Dear Colin,

At Fri, 23 Feb 2007 08:22:48 +0000,
Colin Perkins wrote:
> 
> On 23 Feb 2007, at 08:14, yusuke hiwasaki wrote:
> > Regarding the questions raised by Colin:
> >
> > (1) Time-stamp rate: It should be multiples of 8 kHz. The figure
> >     should change depending on the modes described in Table 2 (or is
> >     it better be fixed?). This will be fixed in the next version.
> 
> If the sampling rate can change during a session, the RTP timestamp  
> rate should be equal to the maximum rate. Otherwise, it should equal  
> the actual rate.

Thanks for clarifications. It will be reflected in the next version.

Regards,
yusuke
--
============
Yusuke Hiwasaki, NTT Cyber Space Labs.
hiwasaki.yusuke@lab.ntt.co.jp
Tel: +81-422-59-4815 (Fax: +81-422-60-7811)

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



From avt-bounces@ietf.org Fri Feb 23 04:12:45 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKWTF-0004KD-Qt; Fri, 23 Feb 2007 04:12:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKWTE-0004ID-Ku
	for avt@ietf.org; Fri, 23 Feb 2007 04:12:04 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKWT8-0003Ob-1M
	for avt@ietf.org; Fri, 23 Feb 2007 04:12:04 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	67DDA2074D; Fri, 23 Feb 2007 10:11:51 +0100 (CET)
X-AuditID: c1b4fb3c-ae7c5bb0000007de-f5-45deafd7c97d 
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	4F813206B5; Fri, 23 Feb 2007 10:11:51 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 23 Feb 2007 10:11:51 +0100
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 23 Feb 2007 10:11:50 +0100
Message-ID: <45DEAFD6.2030501@ericsson.com>
Date: Fri, 23 Feb 2007 10:11:50 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>
Subject: Re: R:
	[AVT]	CCMdraftreview--	should"bandwidth"includetheheaderoverhead
References: <33CB4DEADE8C734CAF59FA0B47E14C17031F329E@morse.NAB.ORG>
	<2CA3E1B6CEC064449CAA7D0FAB46079B0297CA3F@NAEX01.na.qualcomm.com>
In-Reply-To: <2CA3E1B6CEC064449CAA7D0FAB46079B0297CA3F@NAEX01.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Feb 2007 09:11:50.0764 (UTC)
	FILETIME=[A72262C0:01C7572A]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: avt@ietf.org, "Allison, Art" <AAllison@nab.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi,

I don't think this topic is really relevant for the TMMBR discussion. 
The issue you talk about arise independently of the existance of TMMBR 
or not. Beyond how a media sender packetize data it can't make much to 
affect the lip-synch (assuming a good implementation). RTP was designed 
with a model that it is the receiver that needs to buffer and delay its 
playout to ensure best possible synchronization and smooth playout. And 
as I see it there are good reasons for this model. First any sender 
adjusting model breaks down in multi-party sessions. Also the feedback 
loop issues are eliminated by having the receiver deal with it.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



From avt-bounces@ietf.org Fri Feb 23 04:50:57 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKX4B-0003FT-Qn; Fri, 23 Feb 2007 04:50:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKX4A-0003FE-Ef
	for avt@ietf.org; Fri, 23 Feb 2007 04:50:14 -0500
Received: from mailf.telecomitalia.it ([156.54.233.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKX3y-0003Iq-EF
	for avt@ietf.org; Fri, 23 Feb 2007 04:50:14 -0500
Received: from ptpxch007ba020.idc.cww.telecomitalia.it ([156.54.240.50]) by
	mailf.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830);
	Fri, 23 Feb 2007 10:49:59 +0100
Received: from PTPEVS108BA020.idc.cww.telecomitalia.it ([156.54.241.227]) by
	ptpxch007ba020.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 23 Feb 2007 10:49:59 +0100
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Importance: normal
Priority: normal
Content-Transfer-Encoding: quoted-printable
Subject: RE: R: [AVT]
	CCMdraftreview--	should"bandwidth"includetheheaderoverhead
Date: Fri, 23 Feb 2007 10:49:58 +0100
Message-ID: <E9D1028EC5C22B418B5D54CA6EA27C579A5EBB@PTPEVS108BA020.idc.cww.telecomitalia.it>
In-Reply-To: <33CB4DEADE8C734CAF59FA0B47E14C17031F329E@morse.NAB.ORG>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: R: [AVT]
	CCMdraftreview--	should"bandwidth"includetheheaderoverhead
thread-index: AcdVBz3Ox32/cs1CRn6PnWKZtOREUgAA7LOwACEgzsAAAgd9sAA8n/zwAAOXdFA=
From: "Franceschini Guido" <guido.franceschini@telecomitalia.it>
To: "Allison, Art" <AAllison@nab.org>,
	<avt@ietf.org>
X-OriginalArrivalTime: 23 Feb 2007 09:49:59.0377 (UTC)
	FILETIME=[FB410410:01C7572F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7e267523e0685e5aa2dbbdde4b659686
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Allison,

I somehow addressed this type of issue in my draft.
In my view, this is part of what I called "cross-media relations". I =
specifically addressed:
   o  the impact of video packet sizes on audio jitter, in case audio=20
      and video RTP packets get serialized on the physical link;=20
   o  the impact of audio packet rate (and thus overhead) on the=20
      bandwidth that remains available for the video.=20

The key aspect of this "cross-media relations", at least in my view, is =
that they require the bottleneck characterization to be expressed at =
session level and not at media level.

Let me make a bit of history:

The main discussion in this thread is around the TMMBR feedback message =
(or whatever it will be re-named).

Initially, two proposals were made for TMMBR: to signal the codec =
bitrate, or the IP gross bitrate.
IMO, both solutions are more or less inaccurate, depending on the =
protocol stack running in the bottleneck.

I made than the proposal of using a tuple (TIDC, MPO), measuring the =
bottleneck capacity at a layer X, where such layer X need not be know at =
the recipient of the signalling message, and may be choosen by the =
generator of the bottleneck description.
My proposal (in my opinion of course), is no worse than previous ones, =
since the generator of the bottleneck description can still measure the =
capacity at the media level, or at the IP level. However, the generator =
of the bottleneck description has also the opportunity to provide a more =
accurate description by carefully selecting the layer X: this makes my =
proposed metrics preferable with respect to the other solutions.

So far, we are still talking about media level parameters.

The usage of media level parameters avoids jeopardizing the =
specification efforts, since it is just a matter of specifying the =
metrics to be used, and adopting them in both SDP and an RTCP feedback =
message. No architectural impact.

The kind of problem you raise, is however NOT addressed by this kind of =
solution, since the entity that generates the bottleneck info somehow =
decides how to subdivide the total bottleneck capacity into a portion =
dedicated to the audio and a portion dedicated to the video.=20
This reduces the ability of the sender to make the best decision about =
how to encode and deliver audio and video: indeed, the sender will not =
receive the genuine information, but pieces of information filtered by =
outside logics. Hence its decisions will be less then optimal.

In my draft I showed how, in a real-life use case, the signalling of the =
bottleneck capacity (actually: the TIDC parameter) at session level =
instead of media level, allows the sender to keep control of the audio =
jitter induced by the video packetization, to accurately calculate the =
portion of bottleneck capacity consumed by the audio flow, and assign =
the remaining to the video flow, thus optimizing the video quality.

Unfortunately, signaling session-level parameters through RTCP feedback =
is, as far as I know, new.

More feedback inline.
Guido


> -----Original Message-----
> From: Allison, Art [mailto:AAllison@nab.org]
> Sent: gioved=EC 22 febbraio 2007 15.25
> To: avt@ietf.org
> Subject: RE: R: [AVT] CCMdraftreview--
> should"bandwidth"includetheheaderoverhead
>=20
>=20
>=20
> When considering content flow rate control, it seems to me that the
> additional complexity of adjusting the audio flow rate needs to be
> considered and has not been brought up on list.

Actually I tried, but with no feedback so far. Maybe your message is =
more clear.

> In order to enable retention of lip-synch within acceptable tolerances
> the content packets (that are inside  the IP packets) need to arrive
> within the buffer model design constraints.  The buffers can deal with
> temporary variations, but a systemic differential change in=20
> the rate for
> video and not audio could lead to, for example, audio frames arriving
> early compared to video and being forced to be rendered (or=20
> dropped) due
> to the need to empty the buffer. One would expect  jumps in the amount
> of audio offset with respect to the video when the flow was
> differentially adjusted. Experts in the tolerance allowable differ in
> the allowed amount, but whatever the amount, it can be=20
> exceeded in this
> scenario.

I am not sure whether a differential-delay problem really exists, as far =
as congestion is succesfully prevented. But there is a somehow similar =
issue (and maybe we are stating the same): an RTP packet requires time =
to go through a bottleneck, and this time changes when the bottleneck =
capacity changes. Suppose you have audio+video, with video packets of, =
say, up to 1500 bytes (12000 bits). If you started with a bandwidth of =
40000 bit/s, your video packet would take 300ms to go through the =
bottleneck. If RTP packets flow serialized through that bottleneck, this =
means that if an audio packet arrives just before that video packet, it =
would enter immediately the bottleneck; if instead it arrives just =
after, it will wait 300 ms before entering immediately the bottleneck. =
This is jitter!
And when the bottleneck capacity changes, also that jitter figure =
changes: this in turn would impact on the receiver.
The sender should try to keep that jitter figure constant across =
variations in the bottleneck capacity, but this work would be more =
precise if the bottleneck description it gets relates to the link in =
general, and not to the portion of the link capacity that some other =
entity decided to assign to the video.

> This need to keep the program elements 'close enough' in time=20
> is a total
> content requirement that seems to me to indicate the signaling of one
> element may introduce an additional complexity requirement in the end
> receiver. If each element is controlled the receiver would=20
> seem to need
> to compute how close to its buffer limits it is operating and then
> signal changes in rate of the program elements differentially=20
> to retain
> lip-synch. =20
>=20
> Sorry, but I do not know how to translate this meta-issue=20
> into the flow
> control means being discussed here; and merely suggest that those that
> are expert in such consider the need for lip-synch for consumer
> acceptance. =20
>=20
> Art
> _____________
> Art Allison
> Director, Advanced Engineering
> Science & Technology
> National Association of Broadcasters
> 1771 N Street, NW
> Washington, D.C. 20036
> Phone: 202.429.5418
> Fax: 202.777.4981
> aallison@nab.org
>=20
> The National Association of Broadcasters is a trade association that
> advocates on behalf of more than 8,300 free, local radio and=20
> television
> stations and also broadcast networks before Congress, the Federal
> Communications Commission and the Courts.
>=20
> -----Original Message-----
> From: Franceschini Guido [mailto:guido.franceschini@telecomitalia.it]=20
> Sent: Thursday, February 22, 2007 3:49 AM
> To: Desineni, Harikishan; Magnus Westerlund
> Cc: avt@ietf.org
> Subject: RE: R: [AVT] CCM draftreview--
> should"bandwidth"includetheheaderoverhead
>=20
> Hari, Magnus,
>=20
> > > It is clear that inaccurate packet-rate guesses determine=20
> inaccurate
> > TIDC
> > > values, and that this effect is huge at the APP level, but
> > reduced at
> > the
> > > IP level, for such a stack example.
> >=20
> > If we have to work at a common layer (IP) (which results in not so=20
> > inaccurate TIDC values), estimating (max) packet rate is anyways=20
> > necessary for other media types like video. In your example, the=20
> > header overhead looks huge due to the fact that it is=20
> applied over a=20
> > speech stream. The header overhead bit-rate of a video=20
> stream may not=20
> > be significant when compared to actual video (RTP Payload) bit-rate=20
> > alone.
> > I.e., header overhead due to inaccurate video packet rate=20
> may not be=20
> > significant. In some topologies like point 2 point, it=20
> might even be=20
> > possible for the sender to signal its actual packet rate. Average=20
> > measurement of header overhead can be used to correct/signal/detect=20
> > header overhead inaccuracies.
>=20
> It is true that in my example, as well as in most practical cases
> related to video, the inaccuracy due to the selection of the IP layer
> combined with a badly-guessed packetrate is negligible.
> In my draft I outlined another real-life example, with a much more
> complex (and unefficient) stack, where below the IP layer there was
> still plenty of stuff, making that inaccuracy more=20
> significant. However,
> in that case the bandwidth was higher, thus a conservative approach
> would not be too much of a penalty.
> Indeed, in order to prevent congestion, the terminal providing the
> bottleneck characterization is required to provide a conservative
> description, thus to assume the highest packetrate that is potentially
> possible.
>=20
> The message I am trying to convey is anyway the following: when
> characterizing a bottleneck, there could be many causes that=20
> lead to an
> inaccurate description. By means of the metrics I am=20
> proposing, at least
> one of such reason (the metrics used) can be controlled.
> This would apply to a large variety of protocol stacks (I am=20
> hesitant to
> say 'all' protocol stacks, but certainly many more examples that would
> be reasonably covered by picking either the media-bitrate or the
> IP-gross bitrate).
> Since, in order to prevent congestion, every bottlenck description
> should stay on the safe side, the consequence of an inaccurate
> measurement is that the measurement data that is signaled would
> potentially lead to a sub-utilization of the available=20
> resources at the
> bottleneck.
>=20
> If a receiver makes the perfect choice for the measurement=20
> point (e.g.:
> the PPP layer in the PSTN example) the accuracy is optimal, and the
> tuple provided allows the sender to maximally exploit the bottleneck
> resources; if the receiver makes a different choice (e.g. the=20
> IP layer)
> the accuracy is less than optimal, but the tuple it would provide is
> still neutral, i.e. transport stack protocol independent.
> The sender will probably exploit a bit less of the bottleneck=20
> resources.
> The practical impact could be negligible in many cases. Thus,=20
> referring
> again to the PSTN stack example, if I have an implementation=20
> that knows
> well about its protocol stack, and provides the perfect tuple:
> TIDC(PPP)=3D36
> MPO(PPP)=3D48
> very good.
> If instead I have a more generic software that only accounts=20
> for the IP
> impact and provides the tuple <33, 40> (with an implied packetrate of
> 50), then this is a bit less accurate; if my implementation finally
> provides a tuple measured at the codec level such as <17, 0>=20
> (again with
> an implied packetrate of 50), then this is quite less accurate.
> The recipient of this tuple will manage the information=20
> contained in the
> tuple in a neutral manner, i.e. it does not need to know the=20
> exact stack
> at the bottleneck: its computation will be more or less optimized
> depending on the accuracy of the tuple provided, i.e. optimal if the
> tuple referred to the PPP layer, a bit less perfect if the tuple
> referred to the IP layer, potentially bad if the tuple referred to the
> media layer.
>=20
> To conclude: I do not see a need for specifying the=20
> measurement point to
> be used, just an explanation showing how to obtain the maximum
> precision, how much inaccuracy would be introduced otherwise and how
> this would lead to a sub-utilization of the available resources at the
> bottleneck.
>=20
> Cheers
> Guido
> --------------------------------------------------------------------
>=20
> CONFIDENTIALITY NOTICE
>=20
> This message and its attachments are addressed solely to the persons
> above and may contain confidential information. If you have=20
> received the
> message in error, be informed that any use of the content hereof is
> prohibited. Please return it immediately to the sender and delete the
> message. Should you have any questions, please contact us by=20
> replying to
> webmaster@telecomitalia.it.
>=20
>         Thank you
>=20
>                                         www.telecomitalia.it
>=20
> --------------------------------------------------------------------
>                        =20
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>=20
--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons =
above and may contain confidential information. If you have received the =
message in error, be informed that any use of the content hereof is =
prohibited. Please return it immediately to the sender and delete the =
message. Should you have any questions, please contact us by replying to =
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                       =20

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



From avt-bounces@ietf.org Fri Feb 23 05:06:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKXJ5-0008C2-3c; Fri, 23 Feb 2007 05:05:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKXJ3-00087j-HG
	for avt@ietf.org; Fri, 23 Feb 2007 05:05:37 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKXJ2-0007fh-0L
	for avt@ietf.org; Fri, 23 Feb 2007 05:05:37 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	7CE33208E5; Fri, 23 Feb 2007 11:05:33 +0100 (CET)
X-AuditID: c1b4fb3c-affc8bb0000007de-3e-45debc6d76e3 
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	62609208CE; Fri, 23 Feb 2007 11:05:33 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 23 Feb 2007 11:05:33 +0100
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 23 Feb 2007 11:05:32 +0100
Message-ID: <45DEBC6C.2060805@ericsson.com>
Date: Fri, 23 Feb 2007 11:05:32 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Randell Jesup <rjesup@wgate.com>
Subject: Re: R: [AVT] CCM draft
	review--	should"bandwidth"includetheheaderoverhead
References: <45DB196C.3010908@ericsson.com>	<E9D1028EC5C22B418B5D54CA6EA27C579A5E90@PTPEVS108BA020.idc.cww.telecomitalia.it>	<2CA3E1B6CEC064449CAA7D0FAB46079B0297C7B1@NAEX01.na.qualcomm.com>
	<ybuejojo1m2.fsf@jesup.eng.wgate.com>
In-Reply-To: <ybuejojo1m2.fsf@jesup.eng.wgate.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Feb 2007 10:05:32.0905 (UTC)
	FILETIME=[27AE1590:01C75732]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: avt@ietf.org, Franceschini Guido <guido.franceschini@telecomitalia.it>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Randell Jesup skrev:
> "Desineni, Harikishan" <hdesinen@qualcomm.com> writes:
>>> It is clear that inaccurate packet-rate guesses determine inaccurate
>>> TIDC values, and that this effect is huge at the APP level, but reduced
>>> at the IP level, for such a stack example.
>> If we have to work at a common layer (IP) (which results in not so
>> inaccurate TIDC values), estimating (max) packet rate is anyways
>> necessary for other media types like video. In your example, the header
>> overhead looks huge due to the fact that it is applied over a speech
>> stream. The header overhead bit-rate of a video stream may not be
>> significant when compared to actual video (RTP Payload) bit-rate alone.
>> I.e., header overhead due to inaccurate video packet rate may not be
>> significant. In some topologies like point 2 point, it might even be
>> possible for the sender to signal its actual packet rate. Average
>> measurement of header overhead can be used to correct/signal/detect
>> header overhead inaccuracies.
> 
> Note that video links might vary wildly in packets per second, due to
> a) motion, b) packetization, c) jitter (for example, using codec bitrates
> of circa 384K/30FPS on a 1500-byte MTU link - a frame could easily be one
> or two packets, causing big swings in rate), d) iframe pacing and/or error
> recovery (iframes use a bunch of packets compared to pframes typically), 
> etc, etc.  The sender may vary framerate in response to
> bitrate/congestion as well.
> 
> This is part of why I argue for letting the sender apportion the available
> bits (as best as possible), including as much of the packet overhead as
> possible.

Harikishan, are your point that it is hard for the media sender to 
correctly take the overhead into account when transmitting video? In 
most cases it shouldn't be. The rate-control simply need to be told the 
TMMBR tuple, thus taking the overhead applicable per packet and the 
bit-rate and use that in its control loop. For any non-real-time streams 
sent in a session using TMMBR, would still need to be available in 
multiple rates and then the sender can use a look ahead in the stream to 
determine what actual rate the different versions would use. So I don't 
think there is a problem here.

I would also like to point out that TMMBR needs to work for all media, 
from T.140 chat text at less than 1kbps and beyond uncompressed HDTV 
conferencing at gigabit speed.

I finally understood what Guido was going with his proposal. Allowing 
the TMMBR sender to select which layer it reports on does work in the 
common case. The TMMBR tuple definition for his proposal would then be:

Bit-rate: The maximum available bit-rate at the layer reported on.

Overhead: A measured value between the start of the layer reported on 
and up to the RTP payload's start within the packet.

> 
> Averages for header overhead may or may not help, depending on the type of
> header overhead.  For example, if a header extension uses 500 bytes once
> every 3 seconds (say for security/ZRTP/etc), on a link with nominal 50 pps
> of 50 bytes, the "15/16 plus 1/16" will show serious spikes, and make TMMBR
> very sensitive to exactly where in the decay of the spike it's sent.  On
> the other hand, the sender should know about any header extensions it is
> and has sent.
> 

The idea with the filtered measurement was that the media sender can 
compare its local version of this filtering with what it receives in the 
TMMBR request. In a packet loss free environment that would provide a 
perfect measurement in the differences in overhead between what the 
media sender uses and what the TMMBR reporting node sees. When you 
include packet loss you get some noise in the measurement. How much is 
highly dependent on the overhead variations. If you have a distribution 
for the used overhead with a few extreme outlyers then you will get into 
problems if these are dropped. However to my knowledge these type of 
variations of overhead will not be that common and usually not be that 
extreme. Looking at possible reasons in the normal IP and RTP context:

- CSRC list changes
- Header extensions for intermittent sent data
- Header compression (requiring one to measure on layer 2).
- IP extension headers / options

As I see it as long as the overhead measurement is done over a 
reasonable number of packets and for reasonable amounts of packet loss 
this shouldn't be a major problem. If any would like to verify this by 
simulation that would be appreciated.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



From avt-bounces@ietf.org Fri Feb 23 05:23:38 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKXZk-0006LL-2l; Fri, 23 Feb 2007 05:22:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKXZh-0006JP-SP
	for avt@ietf.org; Fri, 23 Feb 2007 05:22:49 -0500
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKXZg-0004tf-Hv
	for avt@ietf.org; Fri, 23 Feb 2007 05:22:49 -0500
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:61528)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HKXZg-0004H6-4w; Fri, 23 Feb 2007 10:22:48 +0000
In-Reply-To: <BAY101-F389E28EE72B7EE9B381353D98F0@phx.gbl>
References: <BAY101-F389E28EE72B7EE9B381353D98F0@phx.gbl>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <DA7FB42D-7340-4101-B635-EDEAB1A373B7@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Duplicate RTP packets
Date: Fri, 23 Feb 2007 10:22:47 +0000
To: Jorge Canas <jcanas2000@hotmail.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On 22 Feb 2007, at 18:29, Jorge Canas wrote:
> I have searched RFC 3550, but can't find an answer to the following  
> questions:
>
> Are RTP stacks required to drop received RTP packets with the same  
> RTP sequence number (duplicate RTP packets)?  If so, how much  
> history (in number of packets) does the RTP stack need to maintain  
> in order to detect duplicates? Or is it only required to detect  
> duplicates arriving piggy backed?
>
> If the RTP stack is not required to drop those packets, I guess the  
> application is expected to deal with duplicates?

The standards don't specify implementation details such as these. My  
RTP library passes duplicates to the application, but there are other  
implementations which suppress duplicates in the RTP layer. The  
boundary between the RTP layer and the application is intentionally  
fussy (see http://portal.acm.org/citation.cfm?doid=99508.99553)

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



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



From avt-bounces@ietf.org Fri Feb 23 05:24:45 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKXbB-0006xM-6U; Fri, 23 Feb 2007 05:24:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKXb9-0006x9-2t
	for avt@ietf.org; Fri, 23 Feb 2007 05:24:19 -0500
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKXb7-0005LZ-Nt
	for avt@ietf.org; Fri, 23 Feb 2007 05:24:19 -0500
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 23 Feb 2007 11:24:16 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: R: [AVT]CCMdraftreview--should"bandwidth"includetheheaderoverhead
Date: Fri, 23 Feb 2007 11:24:15 +0100
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD1033B4E24@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <E9D1028EC5C22B418B5D54CA6EA27C579A5EBB@PTPEVS108BA020.idc.cww.telecomitalia.it>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: R: [AVT]CCMdraftreview--should"bandwidth"includetheheaderoverhead
Thread-Index: AcdVBz3Ox32/cs1CRn6PnWKZtOREUgAA7LOwACEgzsAAAgd9sAA8n/zwAAOXdFAAJmvosA==
From: "SOLLAUD Aurelien RD-TECH-LAN" <aurelien.sollaud@orange-ftgroup.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 23 Feb 2007 10:24:16.0071 (UTC)
	FILETIME=[C5239D70:01C75734]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

>=20
> Let me make a bit of history:
>=20
> The main discussion in this thread is around the TMMBR=20
> feedback message (or whatever it will be re-named).
>=20
> Initially, two proposals were made for TMMBR: to signal the=20
> codec bitrate, or the IP gross bitrate.
> IMO, both solutions are more or less inaccurate, depending on=20
> the protocol stack running in the bottleneck.
>=20

Anyway, I would find useful to have a standard feedback message to
signal a desired codec bitrate back to the media sender. It would avoid
a per codec definition like the codec mode requests embedded in the RTP
payload header we have in RFC 3267 (AMR), RFC 3558 (SMV, EVRC), RFC 4348
(VMR-WB), RFC 4749 (G.729.1), ...

I initially thought it was the goal of TMMBR. But the current discussion
shows that it is likely to be something else.

Most modern audio codecs will be multi-bitrate, it is desirable to have
a standard RTCP message to signal codec bitrate change requests, instead
of incorrectly using the RTP media path to perform this. And it would be
interesting no to reduce it to AVPF profile.

Regards,
Aurelien

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



From avt-bounces@ietf.org Fri Feb 23 05:34:47 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKXkZ-0003rT-BX; Fri, 23 Feb 2007 05:34:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKXkX-0003q7-Lq
	for avt@ietf.org; Fri, 23 Feb 2007 05:34:01 -0500
Received: from mailf.telecomitalia.it ([156.54.233.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKXkW-0007hR-76
	for avt@ietf.org; Fri, 23 Feb 2007 05:34:01 -0500
Received: from ptpxch007ba020.idc.cww.telecomitalia.it ([156.54.240.50]) by
	mailf.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830);
	Fri, 23 Feb 2007 11:33:59 +0100
Received: from PTPEVS108BA020.idc.cww.telecomitalia.it ([156.54.241.227]) by
	ptpxch007ba020.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 23 Feb 2007 11:33:58 +0100
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Importance: normal
Priority: normal
Content-Transfer-Encoding: quoted-printable
Subject: RE: R: [AVT] CCM draft
	review--	should"bandwidth"includetheheaderoverhead
Date: Fri, 23 Feb 2007 11:33:58 +0100
Message-ID: <E9D1028EC5C22B418B5D54CA6EA27C579A5EBC@PTPEVS108BA020.idc.cww.telecomitalia.it>
In-Reply-To: <45DEBC6C.2060805@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: R: [AVT] CCM draft
	review--	should"bandwidth"includetheheaderoverhead
thread-index: AcdXMij/zu0bfqvtSP29XN9flrhXJAAA/CAQ
From: "Franceschini Guido" <guido.franceschini@telecomitalia.it>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>,
	"Randell Jesup" <rjesup@wgate.com>
X-OriginalArrivalTime: 23 Feb 2007 10:33:58.0546 (UTC)
	FILETIME=[20523F20:01C75736]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

> I finally understood what Guido was going with his proposal. Allowing=20
> the TMMBR sender to select which layer it reports on does work in the=20
> common case. The TMMBR tuple definition for his proposal=20
> would then be:
>=20
> Bit-rate: The maximum available bit-rate at the layer reported on.
>=20
> Overhead: A measured value between the start of the layer reported on=20
> and up to the RTP payload's start within the packet.

OK, but don't forget trailer bytes too

Guido
--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons =
above and may contain confidential information. If you have received the =
message in error, be informed that any use of the content hereof is =
prohibited. Please return it immediately to the sender and delete the =
message. Should you have any questions, please contact us by replying to =
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                       =20

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



From avt-bounces@ietf.org Fri Feb 23 05:39:13 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKXou-0005la-5D; Fri, 23 Feb 2007 05:38:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKXot-0005jT-0k
	for avt@ietf.org; Fri, 23 Feb 2007 05:38:31 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKXom-0000wc-AG
	for avt@ietf.org; Fri, 23 Feb 2007 05:38:31 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	B5685211E2; Fri, 23 Feb 2007 11:38:19 +0100 (CET)
X-AuditID: c1b4fb3e-ae6d0bb0000007e1-05-45dec41bc493 
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	9F34F212EE; Fri, 23 Feb 2007 11:38:19 +0100 (CET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 23 Feb 2007 11:38:19 +0100
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 23 Feb 2007 11:38:19 +0100
Message-ID: <45DEC41A.1010101@ericsson.com>
Date: Fri, 23 Feb 2007 11:38:18 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Issues with using tuples in TMMBR was:Re: R: [AVT] CCM draft review
	--	should"bandwidth"includetheheaderoverhead
References: <E9D1028EC5C22B418B5D54CA6EA27C579A5E76@PTPEVS108BA020.idc.cww.telecomitalia.it>	<45D9D410.2070506@ericsson.com>	<E9D1028EC5C22B418B5D54CA6EA27C579A5E86@PTPEVS108BA020.idc.cww.telecomitalia.it>
	<45DB196C.3010908@ericsson.com>
In-Reply-To: <45DB196C.3010908@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Feb 2007 10:38:19.0197 (UTC)
	FILETIME=[BBAE6ED0:01C75736]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Cc: avt@ietf.org, Franceschini Guido <guido.franceschini@telecomitalia.it>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Bo and me has spent some time thinking about what we see as one of the 
major real problems with using tuples in TMMBR. As one changed TMMBR 
from a one-dimensional problem to a two dimensional problem, the concept 
of a single owner of the restriction took a hike. Thus we end up with a 
need to indicate multiple tuples that are the active restrictions. This 
will create extra complexities. There will also be more data to transmit.

We are working on this, and haven't yet verified and simulated it to 
understand the full implications. However we do like to share this with 
you to provide you the opportunity to think about the same problem and 
possibly find any issues we have forgotten about. Our current proposal 
for how this would work is the following:

Lets start assuming that there is a session with a number of 
participants. They can all have restriction tuples (bit-rate, overhead). 
So if a media receiver has some change he first checks if the new values 
are an actually restriction compared to the current set of restrictions 
in the session. If that is the case it sends a TMMBR message to the 
media sender. The media sender checks the restriction compared to its 
current set and see if that is an actual restriction given its sets 
(remember the asynchronous behavior in a multi-party session) and if 
that allows it to drop some of the previous restriction as being less 
restrictive then the new one. Then it sends out the TMMBN with the 
current set.

So how does on determine which is the current set of restrictions. Me 
and Bo have been kicking around an algorithm that might result in this. 
However we need to spend some time on verification.

1. First sort the set X of restriction tuples according to bit-rate 
creating a vector of tuples, X1 to Xn with the X1 carrying the lowest 
bit-rate and Xn the highest value.

2. Eleminate all tuples in X with a overhead value smaller than the 
value in X1.

3. Repeat step 2 for all elements in X from the lowest to the next highest.

4. A reduced set X has been created.

The above algorithm eliminates all the tuples that doesn't provide a 
restriction because they allow a higher bit-rate and their bit-rate 
grows slower than the previous one when packet-rate increases.

A second step would be to eliminate all tuples where they although have 
higher bit-rate, the overhead value is only slightly larger so that the 
first restriction does not allow a packet rate that is large enough, 
even when all the allowed bit-rate is spent on headers. An example to 
illustrate this:

Lets say that you have a tuple of (35kbps, 40 bytes) and a second one 
that is (45 kbps, 50 bytes).  The maximum packet rate the first one 
allows are 35000 /(40*8) = 109.375 packets / s. Performing the same 
calculation for the second tuple yields 45000/(50*8) = 112.5 packets/s. 
Thus the second tuple does not provide a restriction that is applicable 
given that the first one is included in the set.

5. For each tuple in X calculate the largest possible packet-rate 
yielding no useful work, i.e. bit-rate / overhead and store in vector Y.

6. For each element in X, index by i, in case Yi+1 is larger than Yi 
remove Yi+1 and Xi+1 from the sets and repeat comparison for i.

However looking at the above there is evident that one could do more 
here with some additional information. The comparison using packet rates 
that means no useful data is transported is easy to do but doesn't 
restrict as well as is possible. There exist two parameters that could 
be introduced into this to provide restrictions that exist in real 
usage. However these values needs to be the same and known to all 
session participants to be possible to utilize.

The first one would to explicit declare the maximum packet rate the 
application has any usage of at all for this media. For example this 
could be restricted by codec, or by the codec in combination with the 
session maximum bit-rate. This maximum packet rate value would allow one 
to eliminate from the set of restriction all tuples whose bit-rate 
divided by overhead is larger than the session maximum packet-rate.

A second possible restriction would to declare a minimum of useful 
rtp-payload bit-rate. In many cases the media codec or application has 
knowledge about what the smallest bit-rate that would provide any 
utility from the media at all. For example for an audio session using 
the AMR speech codec packetized in RTP (RFC 3267), that bit-rate would 
be 4.75kbps. I ignore the per frame and RTP payload overhead in this 
case, but those could be considered to be included also. This minimal 
overhead could then be subtracted from all the tuples bit-rate values 
prior to running the above presented algorithm. Note that this second 
restriction needs to be applied prior to the first one if both where to 
be present.

What these restrictions provides are some application sanity 
restrictions on what possible combination of useful bit-rate and maximum 
packet rate it can produce and still do some good. However these would 
need to be signaled and could also result in some dispute during session 
establishment if the applications aren't agreeing on a value.

So the big question to you is: Is solving the inaccuracy problem that 
introducing a tuple solves worth the extra complexities and overhead?

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



From avt-bounces@ietf.org Fri Feb 23 05:41:12 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKXr6-0006mS-2C; Fri, 23 Feb 2007 05:40:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKXr4-0006jA-Hp
	for avt@ietf.org; Fri, 23 Feb 2007 05:40:46 -0500
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKXr1-0001Yz-7k
	for avt@ietf.org; Fri, 23 Feb 2007 05:40:46 -0500
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:61549)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HKXr0-00069I-MP; Fri, 23 Feb 2007 10:40:42 +0000
In-Reply-To: <E9D1028EC5C22B418B5D54CA6EA27C579A5EBB@PTPEVS108BA020.idc.cww.telecomitalia.it>
References: <E9D1028EC5C22B418B5D54CA6EA27C579A5EBB@PTPEVS108BA020.idc.cww.telecomitalia.it>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <04F0882F-5159-4675-9B3D-7D4A17058B8D@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: R: [AVT]
	CCMdraftreview--	should"bandwidth"includetheheaderoverhead
Date: Fri, 23 Feb 2007 10:40:42 +0000
To: "Franceschini Guido" <guido.franceschini@telecomitalia.it>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: avt@ietf.org, "Allison, Art" <AAllison@nab.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On 23 Feb 2007, at 09:49, Franceschini Guido wrote:
...
> In my draft I showed how, in a real-life use case, the signalling  
> of the bottleneck capacity (actually: the TIDC parameter) at  
> session level instead of media level, allows the sender to keep  
> control of the audio jitter induced by the video packetization, to  
> accurately calculate the portion of bottleneck capacity consumed by  
> the audio flow, and assign the remaining to the video flow, thus  
> optimizing the video quality.

What about cross traffic, RTP or non-RTP? You can't assume the two  
RTP flows are the only ones sharing the bottleneck link. Indeed, this  
discussion seems to be focussing on congestion control, for which  
something like DCCP is likely better suited, than on coarse  
application-layer rate limiting, which was the intent of TMMBR.

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



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



From avt-bounces@ietf.org Fri Feb 23 05:48:02 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKXxb-0001ND-LX; Fri, 23 Feb 2007 05:47:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKXxb-0001N8-0f
	for avt@ietf.org; Fri, 23 Feb 2007 05:47:31 -0500
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKXxZ-00034r-N2
	for avt@ietf.org; Fri, 23 Feb 2007 05:47:30 -0500
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:61558)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HKXxZ-0007TZ-BU; Fri, 23 Feb 2007 10:47:29 +0000
In-Reply-To: <E9D1028EC5C22B418B5D54CA6EA27C579A5EBC@PTPEVS108BA020.idc.cww.telecomitalia.it>
References: <E9D1028EC5C22B418B5D54CA6EA27C579A5EBC@PTPEVS108BA020.idc.cww.telecomitalia.it>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <9C7093C8-B5DD-4082-BE95-2A7AD7E31DD3@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: IETF IPR policy (was Re: R: [AVT] CCM draft
	review--	should"bandwidth"includetheheaderoverhead)
Date: Fri, 23 Feb 2007 10:47:29 +0000
To: "Franceschini Guido" <guido.franceschini@telecomitalia.it>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On 23 Feb 2007, at 10:33, Franceschini Guido wrote:
> CONFIDENTIALITY NOTICE
>
> This message and its attachments are addressed solely to the  
> persons above and may contain confidential information. If you have  
> received the message in error, be informed that any use of the  
> content hereof is prohibited. Please return it immediately to the  
> sender and delete the message. Should you have any questions,  
> please contact us by replying to webmaster@telecomitalia.it.
>
>         Thank you
>
>                                         www.telecomitalia.it
>
> --------------------------------------------------------------------

A reminder that the IETF IPR policy [RFC 3978 section 3.2] states:

    No information or document that is subject to any requirement of
    confidentiality or any restriction on its dissemination may be
    submitted as a Contribution or otherwise considered in any part of
    the IETF Standards Process, and there must be no assumption of any
    confidentiality obligation with respect to any Contribution.  Each
    Contributor agrees that any statement in a Contribution, whether
    generated automatically or otherwise, that states or implies that  
the
    Contribution is confidential or subject to any privilege, can be
    disregarded for all purposes, and will be of no force or effect.

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



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



From avt-bounces@ietf.org Fri Feb 23 08:32:55 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKaWN-0003l8-Vt; Fri, 23 Feb 2007 08:31:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKaWN-0003kv-E0
	for avt@ietf.org; Fri, 23 Feb 2007 08:31:35 -0500
Received: from maild.telecomitalia.it ([156.54.233.30])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKaWF-0003io-L1
	for avt@ietf.org; Fri, 23 Feb 2007 08:31:33 -0500
Received: from ptpxch009ba020.idc.cww.telecomitalia.it ([156.54.240.52]) by
	maild.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830);
	Fri, 23 Feb 2007 14:31:22 +0100
Received: from PTPEVS108BA020.idc.cww.telecomitalia.it ([156.54.241.227]) by
	ptpxch009ba020.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 23 Feb 2007 14:31:21 +0100
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Importance: normal
Content-Type: text/plain;
	charset="iso-8859-1"
Priority: normal
Content-Transfer-Encoding: quoted-printable
Subject: RE: Issues with using tuples in TMMBR was:Re: R: [AVT] CCM draft
	review --	should"bandwidth"includetheheaderoverhead
Date: Fri, 23 Feb 2007 14:31:21 +0100
Message-ID: <E9D1028EC5C22B418B5D54CA6EA27C579A5EBF@PTPEVS108BA020.idc.cww.telecomitalia.it>
In-Reply-To: <45DEC41A.1010101@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Issues with using tuples in TMMBR was:Re: R: [AVT] CCM draft
	review --	should"bandwidth"includetheheaderoverhead
thread-index: AcdXNr0l71oyisQ+TnacUBEyq9I83wAD2lPg
From: "Franceschini Guido" <guido.franceschini@telecomitalia.it>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-OriginalArrivalTime: 23 Feb 2007 13:31:21.0401 (UTC)
	FILETIME=[E7F50A90:01C7574E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5fb88b8381f3896aeacc5a021513237b
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Magnus,

let me first check if I have understood your scenario. Then I'll give my =
view on your mail: just disregard it if I missed to understand the =
scenario in the first place.


Scanario: a sender S and multiple receivers R1, R2 ... RN

The sender is notified of a number of bottlneck tuples B1, B2 ... BN, =
each expressed for a potentially different stack.
Based on some internal logic, the sender decides how to encode and =
packetize its traffic, and also acknowledges with TMMBN to let each =
receiver aware of the currently valid limits.

If the above is correct, then let's go on.

There is a set of challenges in this scenario:

1) identification of the most restrictive bottleneck among the B1 ... BN =

2) generation of the TMMBN to let receiver know about the current =
restriction
3) reduction of useless TMMBR traffic
4) accuracy of the Bx data

Concerning 1) identification of the most restrictive bottleneck among =
the B1 ... BN

The usage of a tuple instead of a single value allows for a more =
accurate description, but it is easy to derive from an accurate =
description a less accurate one ;-)
More specifically, if you indicated in the TMMBR the IP gross bitrate, =
or the media bitrate, you were actually impling some packetrate =
(actually, the generator of the TMMBR implied a maxpacketrate). You can =
now apply as well a maxpacketrate, with the advantage that you are now =
the sender, and can therefore apply a more close-to-reality =
maxpacketrate.
Suppose you apply a maxpacketrate of 50; you would obtain from:
(35 kbps, 40 bytes) =3D=3D> 35000-(40*50*8)=3D19000
(45 kbps, 50 bytes) =3D=3D> 45000-(50*50*8)=3D25000

Thus, you go back to the same complexity that you have to deal with =
anyway, with just a better accuracy (the sender applied a uniform and =
credible maxpacketrate, instead of having each receiver applying his own =
guess). Also, the sender knows that it must not exceed 50 pkt/sec.


Concerning 2) generation of the TMMBN to let receiver know about the =
current restriction

Here the goal is to let each receiver aware of the current limits, so =
that it will generate new TMMBR only if they have an impact on the =
sender.
It is definitely undesirable that the sender generates a TMMBN listing =
all tuples that it is currently taking into account.
But if the TMMBN contains a different tuple, made of:
<media bitrate, maxpacketrate>
then each receiver is again able to determine whether it should send a =
TMMBR or not.
Let's use the figures above:

at time t0:
- receiver R1 sends TMMBR(35 kbps, 40 bytes)
- receiver R2 sends TMMBR(35 kbps, 40 bytes)
=3D=3D> sender sends TMMBN(19000, 50 pkt/sec, R1)

at time t1:
- R2 changes from (45 kbps, 50 bytes) to (40 kbps, 50 bytes)
=3D=3D> R2 computes that 19000 + (50*50*8) =3D 39000, thus does not send =
TMMBR

at time t2:
- R2 changes to (38 kbps, 50 bytes)
=3D=3D> R2 sends TMMBR
- Sender computes (38 kbps, 50 bytes) =3D=3D> 38000-(50*50*8)=3D18000
=3D=3D> sender sends TMMBN(18000, 50 pkt/sec, R2)


Concerning 3) reduction of useless TMMBR traffic

The above algorithm shows how the usage of tuples instead of single =
values can be managed with the same efficiency


Concerning 4) accuracy of the Bx data

The usage of tuples instead of single values allows, even in such p2mp =
scenario, to compute more accurate limits.


To conclude: IMHO the usage of tuples have no CONS with respect to =
picking up a single value, while providing benefits instead.

Cheers
Guido


> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> Sent: venerd=EC 23 febbraio 2007 11.38
> To: Magnus Westerlund
> Cc: Franceschini Guido; avt@ietf.org
> Subject: Issues with using tuples in TMMBR was:Re: R: [AVT] CCM draft
> review -- should"bandwidth"includetheheaderoverhead
>=20
>=20
> Bo and me has spent some time thinking about what we see as=20
> one of the=20
> major real problems with using tuples in TMMBR. As one changed TMMBR=20
> from a one-dimensional problem to a two dimensional problem,=20
> the concept=20
> of a single owner of the restriction took a hike. Thus we end=20
> up with a=20
> need to indicate multiple tuples that are the active=20
> restrictions. This=20
> will create extra complexities. There will also be more data=20
> to transmit.
>=20
> We are working on this, and haven't yet verified and simulated it to=20
> understand the full implications. However we do like to share=20
> this with=20
> you to provide you the opportunity to think about the same=20
> problem and=20
> possibly find any issues we have forgotten about. Our current=20
> proposal=20
> for how this would work is the following:
>=20
> Lets start assuming that there is a session with a number of=20
> participants. They can all have restriction tuples (bit-rate,=20
> overhead).=20
> So if a media receiver has some change he first checks if the=20
> new values=20
> are an actually restriction compared to the current set of=20
> restrictions=20
> in the session. If that is the case it sends a TMMBR message to the=20
> media sender. The media sender checks the restriction compared to its=20
> current set and see if that is an actual restriction given its sets=20
> (remember the asynchronous behavior in a multi-party session) and if=20
> that allows it to drop some of the previous restriction as being less=20
> restrictive then the new one. Then it sends out the TMMBN with the=20
> current set.
>=20
> So how does on determine which is the current set of restrictions. Me=20
> and Bo have been kicking around an algorithm that might=20
> result in this.=20
> However we need to spend some time on verification.
>=20
> 1. First sort the set X of restriction tuples according to bit-rate=20
> creating a vector of tuples, X1 to Xn with the X1 carrying the lowest=20
> bit-rate and Xn the highest value.
>=20
> 2. Eleminate all tuples in X with a overhead value smaller than the=20
> value in X1.
>=20
> 3. Repeat step 2 for all elements in X from the lowest to the=20
> next highest.
>=20
> 4. A reduced set X has been created.
>=20
> The above algorithm eliminates all the tuples that doesn't provide a=20
> restriction because they allow a higher bit-rate and their bit-rate=20
> grows slower than the previous one when packet-rate increases.
>=20
> A second step would be to eliminate all tuples where they=20
> although have=20
> higher bit-rate, the overhead value is only slightly larger=20
> so that the=20
> first restriction does not allow a packet rate that is large enough,=20
> even when all the allowed bit-rate is spent on headers. An example to=20
> illustrate this:
>=20
> Lets say that you have a tuple of (35kbps, 40 bytes) and a second one=20
> that is (45 kbps, 50 bytes).  The maximum packet rate the first one=20
> allows are 35000 /(40*8) =3D 109.375 packets / s. Performing the same=20
> calculation for the second tuple yields 45000/(50*8) =3D 112.5=20
> packets/s.=20
> Thus the second tuple does not provide a restriction that is=20
> applicable=20
> given that the first one is included in the set.
>=20
> 5. For each tuple in X calculate the largest possible packet-rate=20
> yielding no useful work, i.e. bit-rate / overhead and store=20
> in vector Y.
>=20
> 6. For each element in X, index by i, in case Yi+1 is larger than Yi=20
> remove Yi+1 and Xi+1 from the sets and repeat comparison for i.
>=20
> However looking at the above there is evident that one could do more=20
> here with some additional information. The comparison using=20
> packet rates=20
> that means no useful data is transported is easy to do but doesn't=20
> restrict as well as is possible. There exist two parameters=20
> that could=20
> be introduced into this to provide restrictions that exist in real=20
> usage. However these values needs to be the same and known to all=20
> session participants to be possible to utilize.
>=20
> The first one would to explicit declare the maximum packet rate the=20
> application has any usage of at all for this media. For example this=20
> could be restricted by codec, or by the codec in combination with the=20
> session maximum bit-rate. This maximum packet rate value=20
> would allow one=20
> to eliminate from the set of restriction all tuples whose bit-rate=20
> divided by overhead is larger than the session maximum packet-rate.
>=20
> A second possible restriction would to declare a minimum of useful=20
> rtp-payload bit-rate. In many cases the media codec or=20
> application has=20
> knowledge about what the smallest bit-rate that would provide any=20
> utility from the media at all. For example for an audio session using=20
> the AMR speech codec packetized in RTP (RFC 3267), that=20
> bit-rate would=20
> be 4.75kbps. I ignore the per frame and RTP payload overhead in this=20
> case, but those could be considered to be included also. This minimal=20
> overhead could then be subtracted from all the tuples bit-rate values=20
> prior to running the above presented algorithm. Note that this second=20
> restriction needs to be applied prior to the first one if=20
> both where to=20
> be present.
>=20
> What these restrictions provides are some application sanity=20
> restrictions on what possible combination of useful bit-rate=20
> and maximum=20
> packet rate it can produce and still do some good. However=20
> these would=20
> need to be signaled and could also result in some dispute=20
> during session=20
> establishment if the applications aren't agreeing on a value.
>=20
> So the big question to you is: Is solving the inaccuracy problem that=20
> introducing a tuple solves worth the extra complexities and overhead?
>=20
> Cheers
>=20
> Magnus Westerlund
>=20
> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>=20
--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons =
above and may contain confidential information. If you have received the =
message in error, be informed that any use of the content hereof is =
prohibited. Please return it immediately to the sender and delete the =
message. Should you have any questions, please contact us by replying to =
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                       =20

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



From avt-bounces@ietf.org Fri Feb 23 08:56:47 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKatp-0003IW-LL; Fri, 23 Feb 2007 08:55:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKato-0003Gq-42
	for avt@ietf.org; Fri, 23 Feb 2007 08:55:48 -0500
Received: from maild.telecomitalia.it ([156.54.233.30])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKatm-0003Sn-NL
	for avt@ietf.org; Fri, 23 Feb 2007 08:55:48 -0500
Received: from ptpxch009ba020.idc.cww.telecomitalia.it ([156.54.240.52]) by
	maild.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830);
	Fri, 23 Feb 2007 14:55:45 +0100
Received: from PTPEVS108BA020.idc.cww.telecomitalia.it ([156.54.241.227]) by
	ptpxch009ba020.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 23 Feb 2007 14:55:45 +0100
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Importance: normal
Content-Type: text/plain;
	charset="iso-8859-1"
Priority: normal
Content-Transfer-Encoding: quoted-printable
Subject: RE: R: [AVT]
	CCMdraftreview--	should"bandwidth"includetheheaderoverhead
Date: Fri, 23 Feb 2007 14:55:44 +0100
Message-ID: <E9D1028EC5C22B418B5D54CA6EA27C579A5EC1@PTPEVS108BA020.idc.cww.telecomitalia.it>
In-Reply-To: <04F0882F-5159-4675-9B3D-7D4A17058B8D@csperkins.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: R: [AVT]
	CCMdraftreview--	should"bandwidth"includetheheaderoverhead
thread-index: AcdXNxQW9caMNf2SSnKsleHEF0JLhAAGQlmw
From: "Franceschini Guido" <guido.franceschini@telecomitalia.it>
To: "Colin Perkins" <csp@csperkins.org>
X-OriginalArrivalTime: 23 Feb 2007 13:55:45.0044 (UTC)
	FILETIME=[505B3D40:01C75752]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: avt@ietf.org, "Allison, Art" <AAllison@nab.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

> -----Original Message-----
> From: Colin Perkins [mailto:csp@csperkins.org]
> Sent: venerd=EC 23 febbraio 2007 11.41
> To: Franceschini Guido
> Cc: Allison, Art; avt@ietf.org
> Subject: Re: R: [AVT] CCMdraftreview--
> should"bandwidth"includetheheaderoverhead
>=20
>=20
> On 23 Feb 2007, at 09:49, Franceschini Guido wrote:
> ...
> > In my draft I showed how, in a real-life use case, the signalling =20
> > of the bottleneck capacity (actually: the TIDC parameter) at =20
> > session level instead of media level, allows the sender to keep =20
> > control of the audio jitter induced by the video packetization, to =20
> > accurately calculate the portion of bottleneck capacity=20
> consumed by =20
> > the audio flow, and assign the remaining to the video flow, thus =20
> > optimizing the video quality.
>=20
> What about cross traffic, RTP or non-RTP? You can't assume the two =20
> RTP flows are the only ones sharing the bottleneck link.=20

True. And indeed this should be better taken into account when =
describing the bottleneck. But this applies to any of the proposals on =
the table, not just mine.
Also, I definitely acknowledge that there are many elements that make =
the bottleneck description inaccurate:
- competing traffic
- error rate
- inappropriate metrics
...

Each vagueness in the information leads to a decision that in order to =
almost guarantee to prevent congestion, under-utilizes the available =
resources.
My proposal addresses of course just the metrics, and by doing so aims =
at reducing the vagueness of the information, and thus improving the =
resource utilization.
By no means my proposal affects any of the other factors of uncertainty.

> Indeed, this =20
> discussion seems to be focussing on congestion control, for which =20
> something like DCCP is likely better suited, than on coarse =20
> application-layer rate limiting, which was the intent of TMMBR.

Guido
--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons =
above and may contain confidential information. If you have received the =
message in error, be informed that any use of the content hereof is =
prohibited. Please return it immediately to the sender and delete the =
message. Should you have any questions, please contact us by replying to =
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                       =20

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



From avt-bounces@ietf.org Fri Feb 23 09:26:37 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKbMk-0003Ii-3f; Fri, 23 Feb 2007 09:25:42 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKbMi-0003IP-Do
	for avt@ietf.org; Fri, 23 Feb 2007 09:25:40 -0500
Received: from foxtrot.nab.org ([209.116.240.194] helo=nab.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKbMc-0000v4-LK
	for avt@ietf.org; Fri, 23 Feb 2007 09:25:40 -0500
Received: from ([199.29.3.25])
	by maildc2.nab.org with ESMTP  id 4028857.18109727;
	Fri, 23 Feb 2007 09:25:06 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: R: [AVT]
	CCMdraftreview--	should"bandwidth"includetheheaderoverhead
Date: Fri, 23 Feb 2007 09:25:06 -0500
Message-ID: <33CB4DEADE8C734CAF59FA0B47E14C17031F32B3@morse.NAB.ORG>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: R: [AVT]
	CCMdraftreview--	should"bandwidth"includetheheaderoverhead
thread-index: AcdVBz3Ox32/cs1CRn6PnWKZtOREUgAA7LOwACEgzsAAAgd9sAA8n/zwAAOXdFAALg8XYA==
From: "Allison, Art" <AAllison@nab.org>
To: <avt@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 872695ea777a517bf5717e5acc69f8be
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Guido,
Thanks for the response, especially the equates_of_termonology (AhHa!).

It seems to me that signaling the individual codec bit-rates is less =
desirable than signaling the IP gross bitrate in "TMMBR"  with respect =
to the goal of managing lip sync .=20

If codec level signaling were chosen, then a means to /somehow/ =
determine that the components have gotten out of synch would seem to be =
needed in order to avoid the unintended result of unpredictable and =
uncontrolled lip-sync variance.=20

A IP gross bitrate approach would also seem to better accommodate adding =
new time sensitive elements without having to go back to the =
fundamentals because the added element interfered with the main stream =
flow through a constriction. Examples: Teletext, Closed Captions, web =
references to overlay (vs pop up) during advertisements, etc.

<acknowledge this is only a factor to consider, not a trade-off of all =
system needs>
::{)
Art

_____________
Art Allison
Director, Advanced Engineering
Science & Technology
National Association of Broadcasters
1771 N Street, NW
Washington, D.C. 20036
Phone: 202.429.5418
Fax: 202.777.4981
aallison@nab.org

The National Association of Broadcasters is a trade association that =
advocates on behalf of more than 8,300 free, local radio and television =
stations and also broadcast networks before Congress, the Federal =
Communications Commission and the Courts.

-----Original Message-----
From: Franceschini Guido [mailto:guido.franceschini@telecomitalia.it]=20
Sent: Friday, February 23, 2007 4:50 AM
To: Allison, Art; avt@ietf.org
Subject: RE: R: [AVT] CCMdraftreview-- =
should"bandwidth"includetheheaderoverhead

Allison,

I somehow addressed this type of issue in my draft.
In my view, this is part of what I called "cross-media relations". I =
specifically addressed:
   o  the impact of video packet sizes on audio jitter, in case audio=20
      and video RTP packets get serialized on the physical link;=20
   o  the impact of audio packet rate (and thus overhead) on the=20
      bandwidth that remains available for the video.=20

The key aspect of this "cross-media relations", at least in my view, is =
that they require the bottleneck characterization to be expressed at =
session level and not at media level.

Let me make a bit of history:

The main discussion in this thread is around the TMMBR feedback message =
(or whatever it will be re-named).

Initially, two proposals were made for TMMBR: to signal the codec =
bitrate, or the IP gross bitrate.
IMO, both solutions are more or less inaccurate, depending on the =
protocol stack running in the bottleneck.

I made than the proposal of using a tuple (TIDC, MPO), measuring the =
bottleneck capacity at a layer X, where such layer X need not be know at =
the recipient of the signalling message, and may be choosen by the =
generator of the bottleneck description.
My proposal (in my opinion of course), is no worse than previous ones, =
since the generator of the bottleneck description can still measure the =
capacity at the media level, or at the IP level. However, the generator =
of the bottleneck description has also the opportunity to provide a more =
accurate description by carefully selecting the layer X: this makes my =
proposed metrics preferable with respect to the other solutions.

So far, we are still talking about media level parameters.

The usage of media level parameters avoids jeopardizing the =
specification efforts, since it is just a matter of specifying the =
metrics to be used, and adopting them in both SDP and an RTCP feedback =
message. No architectural impact.

The kind of problem you raise, is however NOT addressed by this kind of =
solution, since the entity that generates the bottleneck info somehow =
decides how to subdivide the total bottleneck capacity into a portion =
dedicated to the audio and a portion dedicated to the video.=20
This reduces the ability of the sender to make the best decision about =
how to encode and deliver audio and video: indeed, the sender will not =
receive the genuine information, but pieces of information filtered by =
outside logics. Hence its decisions will be less then optimal.

In my draft I showed how, in a real-life use case, the signalling of the =
bottleneck capacity (actually: the TIDC parameter) at session level =
instead of media level, allows the sender to keep control of the audio =
jitter induced by the video packetization, to accurately calculate the =
portion of bottleneck capacity consumed by the audio flow, and assign =
the remaining to the video flow, thus optimizing the video quality.

Unfortunately, signaling session-level parameters through RTCP feedback =
is, as far as I know, new.

More feedback inline.
Guido


> -----Original Message-----
> From: Allison, Art [mailto:AAllison@nab.org]
> Sent: gioved=EC 22 febbraio 2007 15.25
> To: avt@ietf.org
> Subject: RE: R: [AVT] CCMdraftreview--=20
> should"bandwidth"includetheheaderoverhead
>=20
>=20
>=20
> When considering content flow rate control, it seems to me that the=20
> additional complexity of adjusting the audio flow rate needs to be=20
> considered and has not been brought up on list.

Actually I tried, but with no feedback so far. Maybe your message is =
more clear.

> In order to enable retention of lip-synch within acceptable tolerances =

> the content packets (that are inside  the IP packets) need to arrive=20
> within the buffer model design constraints.  The buffers can deal with =

> temporary variations, but a systemic differential change in the rate=20
> for video and not audio could lead to, for example, audio frames=20
> arriving early compared to video and being forced to be rendered (or
> dropped) due
> to the need to empty the buffer. One would expect  jumps in the amount =

> of audio offset with respect to the video when the flow was=20
> differentially adjusted. Experts in the tolerance allowable differ in=20
> the allowed amount, but whatever the amount, it can be exceeded in=20
> this scenario.

I am not sure whether a differential-delay problem really exists, as far =
as congestion is succesfully prevented. But there is a somehow similar =
issue (and maybe we are stating the same): an RTP packet requires time =
to go through a bottleneck, and this time changes when the bottleneck =
capacity changes. Suppose you have audio+video, with video packets of, =
say, up to 1500 bytes (12000 bits). If you started with a bandwidth of =
40000 bit/s, your video packet would take 300ms to go through the =
bottleneck. If RTP packets flow serialized through that bottleneck, this =
means that if an audio packet arrives just before that video packet, it =
would enter immediately the bottleneck; if instead it arrives just =
after, it will wait 300 ms before entering immediately the bottleneck. =
This is jitter!
And when the bottleneck capacity changes, also that jitter figure =
changes: this in turn would impact on the receiver.
The sender should try to keep that jitter figure constant across =
variations in the bottleneck capacity, but this work would be more =
precise if the bottleneck description it gets relates to the link in =
general, and not to the portion of the link capacity that some other =
entity decided to assign to the video.

> This need to keep the program elements 'close enough' in time is a=20
> total content requirement that seems to me to indicate the signaling=20
> of one element may introduce an additional complexity requirement in=20
> the end receiver. If each element is controlled the receiver would=20
> seem to need to compute how close to its buffer limits it is operating =

> and then signal changes in rate of the program elements differentially =

> to retain lip-synch.
>=20
> Sorry, but I do not know how to translate this meta-issue into the=20
> flow control means being discussed here; and merely suggest that those =

> that are expert in such consider the need for lip-synch for consumer=20
> acceptance.
>=20
> Art
> _____________
> Art Allison
> Director, Advanced Engineering
> Science & Technology
> National Association of Broadcasters
> 1771 N Street, NW
> Washington, D.C. 20036
> Phone: 202.429.5418
> Fax: 202.777.4981
> aallison@nab.org
>=20
> The National Association of Broadcasters is a trade association that=20
> advocates on behalf of more than 8,300 free, local radio and=20
> television stations and also broadcast networks before Congress, the=20
> Federal Communications Commission and the Courts.
>=20
> -----Original Message-----
> From: Franceschini Guido [mailto:guido.franceschini@telecomitalia.it]
> Sent: Thursday, February 22, 2007 3:49 AM
> To: Desineni, Harikishan; Magnus Westerlund
> Cc: avt@ietf.org
> Subject: RE: R: [AVT] CCM draftreview--=20
> should"bandwidth"includetheheaderoverhead
>=20
> Hari, Magnus,
>=20
> > > It is clear that inaccurate packet-rate guesses determine
> inaccurate
> > TIDC
> > > values, and that this effect is huge at the APP level, but
> > reduced at
> > the
> > > IP level, for such a stack example.
> >=20
> > If we have to work at a common layer (IP) (which results in not so=20
> > inaccurate TIDC values), estimating (max) packet rate is anyways=20
> > necessary for other media types like video. In your example, the=20
> > header overhead looks huge due to the fact that it is
> applied over a
> > speech stream. The header overhead bit-rate of a video
> stream may not
> > be significant when compared to actual video (RTP Payload) bit-rate=20
> > alone.
> > I.e., header overhead due to inaccurate video packet rate
> may not be
> > significant. In some topologies like point 2 point, it
> might even be
> > possible for the sender to signal its actual packet rate. Average=20
> > measurement of header overhead can be used to correct/signal/detect=20
> > header overhead inaccuracies.
>=20
> It is true that in my example, as well as in most practical cases=20
> related to video, the inaccuracy due to the selection of the IP layer=20
> combined with a badly-guessed packetrate is negligible.
> In my draft I outlined another real-life example, with a much more=20
> complex (and unefficient) stack, where below the IP layer there was=20
> still plenty of stuff, making that inaccuracy more significant.=20
> However, in that case the bandwidth was higher, thus a conservative=20
> approach would not be too much of a penalty.
> Indeed, in order to prevent congestion, the terminal providing the=20
> bottleneck characterization is required to provide a conservative=20
> description, thus to assume the highest packetrate that is potentially =

> possible.
>=20
> The message I am trying to convey is anyway the following: when=20
> characterizing a bottleneck, there could be many causes that lead to=20
> an inaccurate description. By means of the metrics I am proposing, at=20
> least one of such reason (the metrics used) can be controlled.
> This would apply to a large variety of protocol stacks (I am hesitant=20
> to say 'all' protocol stacks, but certainly many more examples that=20
> would be reasonably covered by picking either the media-bitrate or the =

> IP-gross bitrate).
> Since, in order to prevent congestion, every bottlenck description=20
> should stay on the safe side, the consequence of an inaccurate=20
> measurement is that the measurement data that is signaled would=20
> potentially lead to a sub-utilization of the available resources at=20
> the bottleneck.
>=20
> If a receiver makes the perfect choice for the measurement point=20
> (e.g.:
> the PPP layer in the PSTN example) the accuracy is optimal, and the=20
> tuple provided allows the sender to maximally exploit the bottleneck=20
> resources; if the receiver makes a different choice (e.g. the IP=20
> layer) the accuracy is less than optimal, but the tuple it would=20
> provide is still neutral, i.e. transport stack protocol independent.
> The sender will probably exploit a bit less of the bottleneck=20
> resources.
> The practical impact could be negligible in many cases. Thus,=20
> referring again to the PSTN stack example, if I have an implementation =

> that knows well about its protocol stack, and provides the perfect=20
> tuple:
> TIDC(PPP)=3D36
> MPO(PPP)=3D48
> very good.
> If instead I have a more generic software that only accounts for the=20
> IP impact and provides the tuple <33, 40> (with an implied packetrate=20
> of 50), then this is a bit less accurate; if my implementation finally =

> provides a tuple measured at the codec level such as <17, 0> (again=20
> with an implied packetrate of 50), then this is quite less accurate.
> The recipient of this tuple will manage the information contained in=20
> the tuple in a neutral manner, i.e. it does not need to know the exact =

> stack at the bottleneck: its computation will be more or less=20
> optimized depending on the accuracy of the tuple provided, i.e.=20
> optimal if the tuple referred to the PPP layer, a bit less perfect if=20
> the tuple referred to the IP layer, potentially bad if the tuple=20
> referred to the media layer.
>=20
> To conclude: I do not see a need for specifying the measurement point=20
> to be used, just an explanation showing how to obtain the maximum=20
> precision, how much inaccuracy would be introduced otherwise and how=20
> this would lead to a sub-utilization of the available resources at the =

> bottleneck.
>=20
> Cheers
> Guido
> --------------------------------------------------------------------
>=20
> CONFIDENTIALITY NOTICE
>=20
> This message and its attachments are addressed solely to the persons=20
> above and may contain confidential information. If you have received=20
> the message in error, be informed that any use of the content hereof=20
> is prohibited. Please return it immediately to the sender and delete=20
> the message. Should you have any questions, please contact us by=20
> replying to webmaster@telecomitalia.it.
>=20
>         Thank you
>=20
>                                         www.telecomitalia.it
>=20
> --------------------------------------------------------------------
>                        =20
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>=20
--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons =
above and may contain confidential information. If you have received the =
message in error, be informed that any use of the content hereof is =
prohibited. Please return it immediately to the sender and delete the =
message. Should you have any questions, please contact us by replying to =
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                       =20

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



From avt-bounces@ietf.org Fri Feb 23 09:53:14 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKbmg-0002sJ-Rk; Fri, 23 Feb 2007 09:52:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKbmg-0002ro-1K
	for avt@ietf.org; Fri, 23 Feb 2007 09:52:30 -0500
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HKbmb-0007bM-Ti for avt@ietf.org; Fri, 23 Feb 2007 09:52:30 -0500
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Fri, 23 Feb 2007 09:52:25 -0500
To: "SOLLAUD Aurelien RD-TECH-LAN" <aurelien.sollaud@orange-ftgroup.com>
Subject: Re: R: [AVT]CCMdraftreview--should"bandwidth"includetheheaderoverhead
References: <DD8B8FEBBFAF9E488F63FF0F1A69EDD1033B4E24@ftrdmel1.rd.francetelecom.fr>
From: Randell Jesup <rjesup@wgate.com>
Date: Fri, 23 Feb 2007 09:52:23 -0500
In-Reply-To: <DD8B8FEBBFAF9E488F63FF0F1A69EDD1033B4E24@ftrdmel1.rd.francetelecom.fr>
	(SOLLAUD Aurelien's message of "Fri, 23 Feb 2007 11:24:15 +0100")
Message-ID: <ybuejohkjtk.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 23 Feb 2007 14:52:25.0296 (UTC)
	FILETIME=[3B108500:01C7575A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

"SOLLAUD Aurelien RD-TECH-LAN" <aurelien.sollaud@orange-ftgroup.com> writes:
>> The main discussion in this thread is around the TMMBR 
>> feedback message (or whatever it will be re-named).
>> 
>> Initially, two proposals were made for TMMBR: to signal the 
>> codec bitrate, or the IP gross bitrate.
>> IMO, both solutions are more or less inaccurate, depending on 
>> the protocol stack running in the bottleneck.
>
>Anyway, I would find useful to have a standard feedback message to
>signal a desired codec bitrate back to the media sender. It would avoid
>a per codec definition like the codec mode requests embedded in the RTP
>payload header we have in RFC 3267 (AMR), RFC 3558 (SMV, EVRC), RFC 4348
>(VMR-WB), RFC 4749 (G.729.1), ...
>
>I initially thought it was the goal of TMMBR. But the current discussion
>shows that it is likely to be something else.

Correct; TMMBR was not designed as a codec-bitrate-switch-request tool
(witness the name).  It could result in a sender deciding to switch
bitrates in a multi-bitrate codec, but counting on specific values to mean
specific things (like "switch from 16Kbps mode to 8Kbps mode" by indicating
8000 bps) is dangerous with TMMBR.  For example, a midbox might modify a
TMMBR request by subtracting some amount for overhead it knows about,
causing your 8000 to become 7500.

>Most modern audio codecs will be multi-bitrate, it is desirable to have
>a standard RTCP message to signal codec bitrate change requests, instead
>of incorrectly using the RTP media path to perform this. And it would be
>interesting no to reduce it to AVPF profile.

I'm not sure I understand "interesting no to reduce it to AVPF profile".
I think it may make sense to consider a draft for something other than
TMMBR to provide the ability to request/suggest (pure) codec rate shifts,
for reasons other than restriction.  The two items don't work well together
in one model (as evidenced by the discussions/disagreements here over TIAS
vs AS vs tuples), but may work well when separated into two mechanisms with
different goals and uses.

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


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



From avt-bounces@ietf.org Fri Feb 23 09:56:08 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKbp6-0004Wi-Oj; Fri, 23 Feb 2007 09:55:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKbp5-0004Ti-BB
	for avt@ietf.org; Fri, 23 Feb 2007 09:54:59 -0500
Received: from foxtrot.nab.org ([209.116.240.194] helo=nab.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKbou-0008AN-Pk
	for avt@ietf.org; Fri, 23 Feb 2007 09:54:59 -0500
Received: from ([199.29.3.25])
	by maildc2.nab.org with ESMTP  id 4028857.18110697;
	Fri, 23 Feb 2007 09:54:23 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: R:
	[AVT]	CCMdraftreview--	should"bandwidth"includetheheaderoverhead
Date: Fri, 23 Feb 2007 09:54:23 -0500
Message-ID: <33CB4DEADE8C734CAF59FA0B47E14C17031F32B8@morse.NAB.ORG>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: R: [AVT]	CCMdraftreview--	should"bandwidth"includetheheaderoverhead
thread-index: AcdXKsseMffwm9K1Su65PDhH6W0I/wALs6lA
From: "Allison, Art" <AAllison@nab.org>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>,
	"Desineni, Harikishan" <hdesinen@qualcomm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

How to control lip-sync or lack thereof is clearly out of scope here.

However, I respectively disagree with the AD that it is out of scope as
a factor in the decision between selection of a total bit rate control
vs. a partial bit rate control. =20

It is only one factor, but declaring it out of scope as a consideration
can be expected to impact the technical choice. =20

I request reconsideration and clarification, as surly the AD did not
intend to force the group to ignore a technical factor that is material
to the RFC content.

_____________
Art Allison
Director, Advanced Engineering
Science & Technology
National Association of Broadcasters
1771 N Street, NW
Washington, D.C. 20036
Phone: 202.429.5418
Fax: 202.777.4981
aallison@nab.org

The National Association of Broadcasters is a trade association that
advocates on behalf of more than 8,300 free, local radio and television
stations and also broadcast networks before Congress, the Federal
Communications Commission and the Courts.

-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]=20
Sent: Friday, February 23, 2007 4:12 AM
To: Desineni, Harikishan
Cc: Allison, Art; avt@ietf.org
Subject: Re: R: [AVT] CCMdraftreview--
should"bandwidth"includetheheaderoverhead

Hi,

I don't think this topic is really relevant for the TMMBR discussion.=20
The issue you talk about arise independently of the existance of TMMBR
or not. Beyond how a media sender packetize data it can't make much to
affect the lip-synch (assuming a good implementation). RTP was designed
with a model that it is the receiver that needs to buffer and delay its
playout to ensure best possible synchronization and smooth playout. And
as I see it there are good reasons for this model. First any sender
adjusting model breaks down in multi-party sessions. Also the feedback
loop issues are eliminated by having the receiver deal with it.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



From avt-bounces@ietf.org Fri Feb 23 10:27:27 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKcJ3-00017O-CW; Fri, 23 Feb 2007 10:25:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKcIq-00011h-Rv
	for avt@ietf.org; Fri, 23 Feb 2007 10:25:44 -0500
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKcFb-0005ps-Gf
	for avt@ietf.org; Fri, 23 Feb 2007 10:22:25 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: R:[AVT]	CCMdraftreview--	should"bandwidth"includetheheaderoverhead
Date: Fri, 23 Feb 2007 17:22:14 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C730CE5@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: R: [AVT]	CCMdraftreview--	should"bandwidth"includetheheaderoverhead
Thread-Index: AcdXKsseMffwm9K1Su65PDhH6W0I/wALs6lAAAD+RGw=
References: <33CB4DEADE8C734CAF59FA0B47E14C17031F32B8@morse.NAB.ORG>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Allison, Art" <AAllison@nab.org>,
	"Magnus Westerlund" <magnus.westerlund@ericsson.com>,
	"Desineni, Harikishan" <hdesinen@qualcomm.com>
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 31b28e25e9d13a22020d8b7aedc9832c
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2048540172=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2048540172==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7575E.657700C7"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7575E.657700C7
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Hi,
I think what Magnus is saying is that TMMBR address the bit rate of a =
specific stream, for example the video.
Now as for lip-synch problem. The assumption is that the sender will put =
the audio and video in its output buffer synchronizes enableing the =
receiver to adjuct based on time. The sender do not have any control on =
the way the medai handled by the network.
When a receiver aks for a TMMBR to reduce the bit rate, in some cases =
due to application constrains it is typicaly for the video. The sender =
can reduce the bit rate and keep the frame rate and this will keep the =
lip synch or it may reduce the frame rate and re-adjuct is internal =
synchronization between the audio and video keeping them synchronized on =
its output buffers.
So my view, for TMMBR, lip-synch is not related
Roni Even

________________________________

=EE=E0=FA: Allison, Art [mailto:AAllison@nab.org]
=F0=F9=EC=E7: =E5 23/02/2007 16:54
=E0=EC: Magnus Westerlund; Desineni, Harikishan
=F2=E5=FA=F7 =EC=E9=E3=E9=F2=E4: avt@ietf.org
=F0=E5=F9=E0: RE: R:[AVT] CCMdraftreview-- =
should"bandwidth"includetheheaderoverhead



How to control lip-sync or lack thereof is clearly out of scope here.

However, I respectively disagree with the AD that it is out of scope as
a factor in the decision between selection of a total bit rate control
vs. a partial bit rate control.=20

It is only one factor, but declaring it out of scope as a consideration
can be expected to impact the technical choice.=20

I request reconsideration and clarification, as surly the AD did not
intend to force the group to ignore a technical factor that is material
to the RFC content.

_____________
Art Allison
Director, Advanced Engineering
Science & Technology
National Association of Broadcasters
1771 N Street, NW
Washington, D.C. 20036
Phone: 202.429.5418
Fax: 202.777.4981
aallison@nab.org

The National Association of Broadcasters is a trade association that
advocates on behalf of more than 8,300 free, local radio and television
stations and also broadcast networks before Congress, the Federal
Communications Commission and the Courts.

-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
Sent: Friday, February 23, 2007 4:12 AM
To: Desineni, Harikishan
Cc: Allison, Art; avt@ietf.org
Subject: Re: R: [AVT] CCMdraftreview--
should"bandwidth"includetheheaderoverhead

Hi,

I don't think this topic is really relevant for the TMMBR discussion.
The issue you talk about arise independently of the existance of TMMBR
or not. Beyond how a media sender packetize data it can't make much to
affect the lip-synch (assuming a good implementation). RTP was designed
with a model that it is the receiver that needs to buffer and delay its
playout to ensure best possible synchronization and smooth playout. And
as I see it there are good reasons for this model. First any sender
adjusting model breaks down in multi-party sessions. Also the feedback
loop issues are eliminated by having the receiver deal with it.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



------_=_NextPart_001_01C7575E.657700C7
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Drtl><HEAD><TITLE>RE: R:[AVT] CCMdraftreview-- =
should"bandwidth"includetheheaderoverhead</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2800.1515" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 =
size=3D2>Hi,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>I think what Magnus is saying =
is that TMMBR address the bit rate of a specific stream, for example the =
video.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Now as for lip-synch problem. =
The assumption is that the sender will put the audio and video in its =
output buffer synchronizes enableing the receiver to adjuct based on =
time. The sender do not have any control on the way the medai handled by =
the network.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>When a receiver aks for a =
TMMBR to reduce the bit rate, in some cases due to application =
constrains it is typicaly for the video. The sender can reduce the bit =
rate and keep the frame rate and this will keep the lip synch or it may =
reduce the frame rate and re-adjuct is internal synchronization between =
the audio and video keeping them synchronized on its output =
buffers.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>So my view, for TMMBR, =
lip-synch is not related</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Roni Even</FONT></DIV>=0A=
<DIV dir=3Drtl><BR></DIV>=0A=
<DIV dir=3Drtl>=0A=
<HR tabIndex=3D-1>=0A=
</DIV>=0A=
<DIV dir=3Drtl><FONT face=3DTahoma size=3D2><B>=EE=E0=FA:</B> Allison, =
Art [mailto:AAllison@nab.org]<BR><B>=F0=F9=EC=E7:</B> =E5 23/02/2007 =
16:54<BR><B>=E0=EC:</B> Magnus Westerlund; Desineni, =
Harikishan<BR><B>=F2=E5=FA=F7 =EC=E9=E3=E9=F2=E4:</B> =
avt@ietf.org<BR><B>=F0=E5=F9=E0:</B> RE: R:[AVT] CCMdraftreview-- =
should"bandwidth"includetheheaderoverhead<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>How to control lip-sync or lack thereof is clearly out =
of scope here.<BR><BR>However, I respectively disagree with the AD that =
it is out of scope as<BR>a factor in the decision between selection of a =
total bit rate control<BR>vs. a partial bit rate =
control.&nbsp;<BR><BR>It is only one factor, but declaring it out of =
scope as a consideration<BR>can be expected to impact the technical =
choice.&nbsp;<BR><BR>I request reconsideration and clarification, as =
surly the AD did not<BR>intend to force the group to ignore a technical =
factor that is material<BR>to the RFC =
content.<BR><BR>_____________<BR>Art Allison<BR>Director, Advanced =
Engineering<BR>Science &amp; Technology<BR>National Association of =
Broadcasters<BR>1771 N Street, NW<BR>Washington, D.C. 20036<BR>Phone: =
202.429.5418<BR>Fax: 202.777.4981<BR>aallison@nab.org<BR><BR>The =
National Association of Broadcasters is a trade association =
that<BR>advocates on behalf of more than 8,300 free, local radio and =
television<BR>stations and also broadcast networks before Congress, the =
Federal<BR>Communications Commission and the =
Courts.<BR><BR>-----Original Message-----<BR>From: Magnus Westerlund [<A =
href=3D"mailto:magnus.westerlund@ericsson.com">mailto:magnus.westerlund@e=
ricsson.com</A>]<BR>Sent: Friday, February 23, 2007 4:12 AM<BR>To: =
Desineni, Harikishan<BR>Cc: Allison, Art; avt@ietf.org<BR>Subject: Re: =
R: [AVT] =
CCMdraftreview--<BR>should"bandwidth"includetheheaderoverhead<BR><BR>Hi,<=
BR><BR>I don't think this topic is really relevant for the TMMBR =
discussion.<BR>The issue you talk about arise independently of the =
existance of TMMBR<BR>or not. Beyond how a media sender packetize data =
it can't make much to<BR>affect the lip-synch (assuming a good =
implementation). RTP was designed<BR>with a model that it is the =
receiver that needs to buffer and delay its<BR>playout to ensure best =
possible synchronization and smooth playout. And<BR>as I see it there =
are good reasons for this model. First any sender<BR>adjusting model =
breaks down in multi-party sessions. Also the feedback<BR>loop issues =
are eliminated by having the receiver deal with =
it.<BR><BR>Cheers<BR><BR>Magnus Westerlund<BR><BR>IETF Transport Area =
Director &amp; TSVWG =
Chair<BR>----------------------------------------------------------------=
------<BR>Multimedia Technologies, Ericsson Research =
EAB/TVA/A<BR>------------------------------------------------------------=
----------<BR>Ericsson =
AB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; | Phone +46 8 4048287<BR>Torshamsgatan =
23&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
Fax&nbsp;&nbsp; +46 8 7575550<BR>S-164 80 Stockholm, Sweden | mailto: =
magnus.westerlund@ericsson.com<BR>---------------------------------------=
-------------------------------<BR><BR>__________________________________=
_____________<BR>Audio/Video Transport Working =
Group<BR>avt@ietf.org<BR><A =
href=3D"https://www1.ietf.org/mailman/listinfo/avt">https://www1.ietf.org=
/mailman/listinfo/avt</A><BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C7575E.657700C7--


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

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

--===============2048540172==--




From avt-bounces@ietf.org Fri Feb 23 10:46:35 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKcc5-0002Ke-Kh; Fri, 23 Feb 2007 10:45:37 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKcc4-0002Jp-9U
	for avt@ietf.org; Fri, 23 Feb 2007 10:45:36 -0500
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKcbz-00034r-QR
	for avt@ietf.org; Fri, 23 Feb 2007 10:45:36 -0500
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 23 Feb 2007 16:45:12 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: R:[AVT]CCMdraftreview--should"bandwidth"includetheheaderoverhead
Date: Fri, 23 Feb 2007 16:45:28 +0100
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD1033EB076@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <ybuejohkjtk.fsf@jesup.eng.wgate.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: R:[AVT]CCMdraftreview--should"bandwidth"includetheheaderoverhead
Thread-Index: AcdXWjyl1mCz6nMtQMqfDTZ+ZyRGLgABiWfg
From: "SOLLAUD Aurelien RD-TECH-LAN" <aurelien.sollaud@orange-ftgroup.com>
To: "Randell Jesup" <rjesup@wgate.com>
X-OriginalArrivalTime: 23 Feb 2007 15:45:12.0600 (UTC)
	FILETIME=[9AECC180:01C75761]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org


> >Anyway, I would find useful to have a standard feedback message to=20
> >signal a desired codec bitrate back to the media sender. It=20
> would avoid=20
> >a per codec definition like the codec mode requests embedded=20
> in the RTP=20
> >payload header we have in RFC 3267 (AMR), RFC 3558 (SMV, EVRC), RFC=20
> >4348 (VMR-WB), RFC 4749 (G.729.1), ...
> >
> >I initially thought it was the goal of TMMBR. But the current=20
> >discussion shows that it is likely to be something else.
>=20
> Correct; TMMBR was not designed as a=20
> codec-bitrate-switch-request tool (witness the name).  It=20
> could result in a sender deciding to switch bitrates in a=20
> multi-bitrate codec, but counting on specific values to mean=20
> specific things (like "switch from 16Kbps mode to 8Kbps mode"=20
> by indicating 8000 bps) is dangerous with TMMBR.  For=20
> example, a midbox might modify a TMMBR request by subtracting=20
> some amount for overhead it knows about, causing your 8000 to=20
> become 7500.

OK
=20
> >Most modern audio codecs will be multi-bitrate, it is=20
> desirable to have=20
> >a standard RTCP message to signal codec bitrate change requests,=20
> >instead of incorrectly using the RTP media path to perform=20
> this. And it=20
> >would be interesting no to reduce it to AVPF profile.
>=20
> I'm not sure I understand "interesting no to reduce it to=20
> AVPF profile".

I mean that a codec bitrate change request mechanism would be useful
with the usual AVP profile too. (and SAVP etc...)
Most endpoints are now using AVP.

> I think it may make sense to consider a draft for something=20
> other than TMMBR to provide the ability to request/suggest=20
> (pure) codec rate shifts, for reasons other than restriction.=20
>  The two items don't work well together in one model (as=20
> evidenced by the discussions/disagreements here over TIAS vs=20
> AS vs tuples), but may work well when separated into two=20
> mechanisms with different goals and uses.
>=20

Yes, for me, a pure codec bit rate CCM is useful and would help VoIP
developpers to take advantage of the modern codecs features (multi-rate,
scalable encodings...).

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



From avt-bounces@ietf.org Fri Feb 23 12:32:36 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKeGj-0000Rc-4v; Fri, 23 Feb 2007 12:31:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKeGi-0000RW-83
	for avt@ietf.org; Fri, 23 Feb 2007 12:31:40 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKeGf-00026Z-Cz
	for avt@ietf.org; Fri, 23 Feb 2007 12:31:40 -0500
Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l1NHVUHv006968
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 23 Feb 2007 09:31:30 -0800
Received: from sanexcas01.na.qualcomm.com (sanexcas01.qualcomm.com
	[172.30.36.175])
	by hamtaro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l1NHVR0w028590; Fri, 23 Feb 2007 09:31:29 -0800 (PST)
Received: from NAEX01.qualcomm.com ([129.46.51.60]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 23 Feb 2007 09:31:28 -0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: R:[AVT]	CCMdraftreview--	should"bandwidth"includetheheaderoverhead
Date: Fri, 23 Feb 2007 09:31:29 -0800
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B0297CA90@NAEX01.na.qualcomm.com>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C730CE5@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: R:[AVT]	CCMdraftreview--	should"bandwidth"includetheheaderoverhead
Thread-Index: AcdXKsseMffwm9K1Su65PDhH6W0I/wALs6lAAAD+RGwABKVNMA==
References: <33CB4DEADE8C734CAF59FA0B47E14C17031F32B8@morse.NAB.ORG>
	<144ED8561CE90C41A3E5908EDECE315C730CE5@IsrExch01.israel.polycom.com>
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: "Even, Roni" <roni.even@polycom.co.il>, "Allison, Art" <AAllison@nab.org>, 
	"Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-OriginalArrivalTime: 23 Feb 2007 17:31:28.0819 (UTC)
	FILETIME=[73729030:01C75770]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d67762704726a1bed57e7f4595960d34
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1807625200=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1807625200==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C75770.73275D71"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C75770.73275D71
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

I am addressing Art=92s point on a point to point topology. A sender can =
react to TMMBR several ways as you pointed (changing frame rate, packet =
sizes etc,). The end result could be that packets are getting delayed or =
arriving too early at the receiver. This could happen due to variable =
size of video packets. Some video packets may experience longer delay =
than the corresponding audio packets or audio packets may experience =
more delay when they stay behind video over serial links (Guido=92s =
draft).

=20

My point is that a receiver could inform the sender about delayed or too =
early arrival of packets if it chooses to. This can be done with the =
help of a new RTCP message. A sender can (if it chooses to) make use of =
the delay/earliness information while adjusting its rate for each media. =


=20

Regarding the feedback loop issue:=20

What I am considering is another RTCP message for reporting delay when a =
receiver detects problem with packet arrivals. The performance of =
feedback is anyways dictated by the RTCP timing rules allowed by the RTP =
profile under use. This is applicable to any RTCP message.

=20

Thanks,

Hari

=20

________________________________

From: Even, Roni [mailto:roni.even@polycom.co.il]=20
Sent: Friday, February 23, 2007 7:22 AM
To: Allison, Art; Magnus Westerlund; Desineni, Harikishan
Cc: avt@ietf.org
Subject: RE: R:[AVT] CCMdraftreview-- =
should"bandwidth"includetheheaderoverhead

=20

Hi,

I think what Magnus is saying is that TMMBR address the bit rate of a =
specific stream, for example the video.

Now as for lip-synch problem. The assumption is that the sender will put =
the audio and video in its output buffer synchronizes enableing the =
receiver to adjuct based on time. The sender do not have any control on =
the way the medai handled by the network.

When a receiver aks for a TMMBR to reduce the bit rate, in some cases =
due to application constrains it is typicaly for the video. The sender =
can reduce the bit rate and keep the frame rate and this will keep the =
lip synch or it may reduce the frame rate and re-adjuct is internal =
synchronization between the audio and video keeping them synchronized on =
its output buffers.

So my view, for TMMBR, lip-synch is not related

Roni Even

=20

________________________________

=EE=E0=FA: Allison, Art [mailto:AAllison@nab.org]
=F0=F9=EC=E7: =E5 23/02/2007 16:54
=E0=EC: Magnus Westerlund; Desineni, Harikishan
=F2=E5=FA=F7 =EC=E9=E3=E9=F2=E4: avt@ietf.org
=F0=E5=F9=E0: RE: R:[AVT] CCMdraftreview-- =
should"bandwidth"includetheheaderoverhead

How to control lip-sync or lack thereof is clearly out of scope here.

However, I respectively disagree with the AD that it is out of scope as
a factor in the decision between selection of a total bit rate control
vs. a partial bit rate control.=20

It is only one factor, but declaring it out of scope as a consideration
can be expected to impact the technical choice.=20

I request reconsideration and clarification, as surly the AD did not
intend to force the group to ignore a technical factor that is material
to the RFC content.

_____________
Art Allison
Director, Advanced Engineering
Science & Technology
National Association of Broadcasters
1771 N Street, NW
Washington, D.C. 20036
Phone: 202.429.5418
Fax: 202.777.4981
aallison@nab.org

The National Association of Broadcasters is a trade association that
advocates on behalf of more than 8,300 free, local radio and television
stations and also broadcast networks before Congress, the Federal
Communications Commission and the Courts.

-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
Sent: Friday, February 23, 2007 4:12 AM
To: Desineni, Harikishan
Cc: Allison, Art; avt@ietf.org
Subject: Re: R: [AVT] CCMdraftreview--
should"bandwidth"includetheheaderoverhead

Hi,

I don't think this topic is really relevant for the TMMBR discussion.
The issue you talk about arise independently of the existance of TMMBR
or not. Beyond how a media sender packetize data it can't make much to
affect the lip-synch (assuming a good implementation). RTP was designed
with a model that it is the receiver that needs to buffer and delay its
playout to ensure best possible synchronization and smooth playout. And
as I see it there are good reasons for this model. First any sender
adjusting model breaks down in multi-party sessions. Also the feedback
loop issues are eliminated by having the receiver deal with it.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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


------_=_NextPart_001_01C75770.73275D71
Content-Type: text/html;
	charset="windows-1255"
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=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1255">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>RE: R:[AVT] CCMdraftreview--
should&quot;bandwidth&quot;includetheheaderoverhead</title>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{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";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I am addressing Art=92s point on a =
point to
point topology. A sender can react to TMMBR several ways as you pointed
(changing frame rate, packet sizes etc,). The end result could be that =
packets
are getting delayed or arriving too early at the receiver. This could =
happen
due to variable size of video packets. Some video packets may experience =
longer
delay than the corresponding audio packets or audio packets may =
experience more
delay when they stay behind video over serial links (Guido=92s =
draft).<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>My point is that a receiver could =
inform
the sender about delayed or too early arrival of packets if it chooses =
to. This
can be done with the help of a new RTCP message. A sender can (if it =
chooses
to) make use of the delay/earliness information while adjusting its rate =
for
each media. <o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Regarding the feedback loop issue: =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>What I am considering is another =
RTCP
message for reporting delay when a receiver detects problem with packet
arrivals. The performance of feedback is anyways dictated by the RTCP =
timing
rules allowed by the RTP profile under use. This is applicable to any =
RTCP
message.<o:p></o:p></span></font></p>

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

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


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

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

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

<div>

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

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

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

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Even, =
Roni
[mailto:roni.even@polycom.co.il] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, February =
23, 2007
7:22 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Allison, Art; Magnus
Westerlund; Desineni, Harikishan<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> avt@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: R:[AVT]
CCMdraftreview-- =
should&quot;bandwidth&quot;includetheheaderoverhead</span></font><o:p></o=
:p></p>

</div>

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

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Hi,</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I think what Magnus is saying is that TMMBR address =
the bit
rate of a specific stream, for example the =
video.</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Now as for lip-synch problem. The assumption is that =
the
sender will put the audio and video in its output buffer synchronizes =
enableing
the receiver to adjuct based on time. The sender do not have any control =
on the
way the medai handled by the network.</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>When a receiver aks for a TMMBR to reduce the bit =
rate, in
some cases due to application constrains it is typicaly for the video. =
The
sender can reduce the bit rate and keep the frame rate and this will =
keep the
lip synch or it may reduce the frame rate and re-adjuct is internal
synchronization between the audio and video keeping them synchronized on =
its
output buffers.</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>So my view, for TMMBR, lip-synch is not =
related</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Roni Even</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal dir=3DRTL =
style=3D'text-align:right;direction:rtl;unicode-bidi:
embed'><font size=3D3 face=3D"Times New Roman"><span dir=3DLTR =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<div class=3DMsoNormal align=3Dcenter dir=3DRTL =
style=3D'text-align:center;direction:
rtl;unicode-bidi:embed'><font size=3D3 face=3D"Times New Roman"><span =
dir=3DLTR
style=3D'font-size:12.0pt'>

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

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

</div>

<div>

<p class=3DMsoNormal dir=3DRTL =
style=3D'margin-bottom:12.0pt;text-align:right;
direction:rtl;unicode-bidi:embed'><b><font size=3D2 face=3DTahoma><span =
lang=3DHE
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>=EE=E0=FA:=
</span></font></b><font
size=3D2 face=3DTahoma><span lang=3DHE =
style=3D'font-size:10.0pt;font-family:Tahoma'>
Allison, Art [mailto:AAllison@nab.org]<br>
<b><span style=3D'font-weight:bold'>=F0=F9=EC=E7:</span></b> =E5 =
23/02/2007 16:54<br>
<b><span style=3D'font-weight:bold'>=E0=EC:</span></b> Magnus =
Westerlund; Desineni,
Harikishan<br>
<b><span style=3D'font-weight:bold'>=F2=E5=FA=F7 =
=EC=E9=E3=E9=F2=E4:</span></b> avt@ietf.org<br>
<b><span style=3D'font-weight:bold'>=F0=E5=F9=E0:</span></b> RE: R:[AVT] =
CCMdraftreview--
should&quot;bandwidth&quot;includetheheaderoverhead</span></font><span =
lang=3DHE><o:p></o:p></span></p>

</div>

<div>

<p dir=3DRTL =
style=3D'text-align:right;direction:rtl;unicode-bidi:embed'><font
size=3D2 face=3D"Times New Roman"><span lang=3DHE =
style=3D'font-size:10.0pt'>How to
control lip-sync or lack thereof is clearly out of scope here.<br>
<br>
However, I respectively disagree with the AD that it is out of scope =
as<br>
a factor in the decision between selection of a total bit rate =
control<br>
vs. a partial bit rate control.&nbsp;<br>
<br>
It is only one factor, but declaring it out of scope as a =
consideration<br>
can be expected to impact the technical choice.&nbsp;<br>
<br>
I request reconsideration and clarification, as surly the AD did not<br>
intend to force the group to ignore a technical factor that is =
material<br>
to the RFC content.<br>
<br>
_____________<br>
Art Allison<br>
Director, Advanced Engineering<br>
Science &amp; Technology<br>
National Association of Broadcasters<br>
1771 N Street, NW<br>
Washington, D.C. 20036<br>
Phone: 202.429.5418<br>
Fax: 202.777.4981<br>
aallison@nab.org<br>
<br>
The National Association of Broadcasters is a trade association that<br>
advocates on behalf of more than 8,300 free, local radio and =
television<br>
stations and also broadcast networks before Congress, the Federal<br>
Communications Commission and the Courts.<br>
<br>
-----Original Message-----<br>
From: Magnus Westerlund [<a =
href=3D"mailto:magnus.westerlund@ericsson.com">mailto:magnus.westerlund@e=
ricsson.com</a>]<br>
Sent: Friday, February 23, 2007 4:12 AM<br>
To: Desineni, Harikishan<br>
Cc: Allison, Art; avt@ietf.org<br>
Subject: Re: R: [AVT] CCMdraftreview--<br>
should&quot;bandwidth&quot;includetheheaderoverhead<br>
<br>
Hi,<br>
<br>
I don't think this topic is really relevant for the TMMBR =
discussion.<br>
The issue you talk about arise independently of the existance of =
TMMBR<br>
or not. Beyond how a media sender packetize data it can't make much =
to<br>
affect the lip-synch (assuming a good implementation). RTP was =
designed<br>
with a model that it is the receiver that needs to buffer and delay =
its<br>
playout to ensure best possible synchronization and smooth playout. =
And<br>
as I see it there are good reasons for this model. First any sender<br>
adjusting model breaks down in multi-party sessions. Also the =
feedback<br>
loop issues are eliminated by having the receiver deal with it.<br>
<br>
Cheers<br>
<br>
Magnus Westerlund<br>
<br>
IETF Transport Area Director &amp; TSVWG Chair<br>
----------------------------------------------------------------------<br=
>
Multimedia Technologies, Ericsson Research EAB/TVA/A<br>
----------------------------------------------------------------------<br=
>
Ericsson
AB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;
| Phone +46 8 4048287<br>
Torshamsgatan =
23&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
Fax&nbsp;&nbsp; +46 8 7575550<br>
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com<br>
----------------------------------------------------------------------<br=
>
<br>
_______________________________________________<br>
Audio/Video Transport Working Group<br>
avt@ietf.org<br>
<a =
href=3D"https://www1.ietf.org/mailman/listinfo/avt">https://www1.ietf.org=
/mailman/listinfo/avt</a></span></font><span
lang=3DHE><o:p></o:p></span></p>

</div>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C75770.73275D71--


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

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

--===============1807625200==--




From avt-bounces@ietf.org Fri Feb 23 13:54:33 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKfXH-000799-PJ; Fri, 23 Feb 2007 13:52:51 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKfXF-00078r-U3
	for avt@ietf.org; Fri, 23 Feb 2007 13:52:49 -0500
Received: from zcars04f.nortel.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKfXE-0000jY-Bq
	for avt@ietf.org; Fri, 23 Feb 2007 13:52:49 -0500
Received: from zcarhxs1.corp.nortel.com (zcarhxs1.corp.nortel.com
	[47.129.230.89])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l1NIqH317901; Fri, 23 Feb 2007 13:52:17 -0500 (EST)
Received: from [47.130.18.16] ([47.130.18.16] RDNS failed) by
	zcarhxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 23 Feb 2007 13:52:02 -0500
Message-ID: <45DF37BA.9020604@nortel.com>
Date: Fri, 23 Feb 2007 13:51:38 -0500
From: "Tom-PT Taylor" <taylor@nortel.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>
Subject: Re: R:[AVT]	CCMdraftreview--	should"bandwidth"includetheheaderoverhead
References: <33CB4DEADE8C734CAF59FA0B47E14C17031F32B8@morse.NAB.ORG>
	<144ED8561CE90C41A3E5908EDECE315C730CE5@IsrExch01.israel.polycom.com>
	<2CA3E1B6CEC064449CAA7D0FAB46079B0297CA90@NAEX01.na.qualcomm.com>
In-Reply-To: <2CA3E1B6CEC064449CAA7D0FAB46079B0297CA90@NAEX01.na.qualcomm.com>
Content-Type: text/plain; charset=windows-1255; format=flowed
X-OriginalArrivalTime: 23 Feb 2007 18:52:02.0794 (UTC)
	FILETIME=[B4B89CA0:01C7577B]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by zcars04f.nortel.com id
	l1NIqH317901
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "Even,
	Roni" <roni.even@polycom.co.il>, avt@ietf.org, "Allison,
	Art" <AAllison@nab.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Maybe the time adjustment draft, draft-taylor-avt-time-align-00.txt,=20
would be an useful mechanism here. I plan to reissue it shortly.

Desineni, Harikishan wrote:
> I am addressing Art=92s point on a point to point topology. A sender
> can react to TMMBR several ways as you pointed (changing frame rate,
> packet sizes etc,). The end result could be that packets are getting
> delayed or arriving too early at the receiver. This could happen due
> to variable size of video packets. Some video packets may experience
> longer delay than the corresponding audio packets or audio packets
> may experience more delay when they stay behind video over serial
> links (Guido=92s draft).
>=20
>=20
>=20
> My point is that a receiver could inform the sender about delayed or
> too early arrival of packets if it chooses to. This can be done with
> the help of a new RTCP message. A sender can (if it chooses to) make
> use of the delay/earliness information while adjusting its rate for
> each media.
>=20
>=20
>=20
> Regarding the feedback loop issue:
>=20
> What I am considering is another RTCP message for reporting delay
> when a receiver detects problem with packet arrivals. The performance
> of feedback is anyways dictated by the RTCP timing rules allowed by
> the RTP profile under use. This is applicable to any RTCP message.
>=20
>=20
>=20
> Thanks,
>=20
> Hari
>=20
>=20
>=20
> ________________________________
>=20
> From: Even, Roni [mailto:roni.even@polycom.co.il] Sent: Friday,
> February 23, 2007 7:22 AM To: Allison, Art; Magnus Westerlund;
> Desineni, Harikishan Cc: avt@ietf.org Subject: RE: R:[AVT]
> CCMdraftreview-- should"bandwidth"includetheheaderoverhead
>=20
>=20
>=20
> Hi,
>=20
> I think what Magnus is saying is that TMMBR address the bit rate of a
> specific stream, for example the video.
>=20
> Now as for lip-synch problem. The assumption is that the sender will
> put the audio and video in its output buffer synchronizes enableing
> the receiver to adjuct based on time. The sender do not have any
> control on the way the medai handled by the network.
>=20
> When a receiver aks for a TMMBR to reduce the bit rate, in some cases
> due to application constrains it is typicaly for the video. The
> sender can reduce the bit rate and keep the frame rate and this will
> keep the lip synch or it may reduce the frame rate and re-adjuct is
> internal synchronization between the audio and video keeping them
> synchronized on its output buffers.
>=20
> So my view, for TMMBR, lip-synch is not related
>=20
> Roni Even
>=20
>=20
>=20
> ________________________________
>=20
> =EE=E0=FA: Allison, Art [mailto:AAllison@nab.org] =F0=F9=EC=E7: =E5 23/=
02/2007 16:54=20
> =E0=EC: Magnus Westerlund; Desineni, Harikishan =F2=E5=FA=F7 =EC=E9=E3=E9=
=F2=E4: avt@ietf.org
>  =F0=E5=F9=E0: RE: R:[AVT] CCMdraftreview--
> should"bandwidth"includetheheaderoverhead
>=20
> How to control lip-sync or lack thereof is clearly out of scope here.
>=20
>=20
> However, I respectively disagree with the AD that it is out of scope
> as a factor in the decision between selection of a total bit rate
> control vs. a partial bit rate control.
>=20
> It is only one factor, but declaring it out of scope as a
> consideration can be expected to impact the technical choice.
>=20
> I request reconsideration and clarification, as surly the AD did not=20
> intend to force the group to ignore a technical factor that is
> material to the RFC content.
>=20
> _____________ Art Allison Director, Advanced Engineering Science &
> Technology National Association of Broadcasters 1771 N Street, NW=20
> Washington, D.C. 20036 Phone: 202.429.5418 Fax: 202.777.4981=20
> aallison@nab.org
>=20
> The National Association of Broadcasters is a trade association that=20
> advocates on behalf of more than 8,300 free, local radio and
> television stations and also broadcast networks before Congress, the
> Federal Communications Commission and the Courts.
>=20
> -----Original Message----- From: Magnus Westerlund
> [mailto:magnus.westerlund@ericsson.com] Sent: Friday, February 23,
> 2007 4:12 AM To: Desineni, Harikishan Cc: Allison, Art; avt@ietf.org=20
> Subject: Re: R: [AVT] CCMdraftreview--=20
> should"bandwidth"includetheheaderoverhead
>=20
> Hi,
>=20
> I don't think this topic is really relevant for the TMMBR discussion.
>  The issue you talk about arise independently of the existance of
> TMMBR or not. Beyond how a media sender packetize data it can't make
> much to affect the lip-synch (assuming a good implementation). RTP
> was designed with a model that it is the receiver that needs to
> buffer and delay its playout to ensure best possible synchronization
> and smooth playout. And as I see it there are good reasons for this
> model. First any sender adjusting model breaks down in multi-party
> sessions. Also the feedback loop issues are eliminated by having the
> receiver deal with it.
>=20
> Cheers
>=20
> Magnus Westerlund
>=20
> IETF Transport Area Director & TSVWG Chair=20
> ----------------------------------------------------------------------
>  Multimedia Technologies, Ericsson Research EAB/TVA/A=20
> ----------------------------------------------------------------------
>  Ericsson AB                | Phone +46 8 4048287 Torshamsgatan 23
> | Fax   +46 8 7575550 S-164 80 Stockholm, Sweden | mailto:
> magnus.westerlund@ericsson.com=20
> ----------------------------------------------------------------------
>=20
>=20
> _______________________________________________ Audio/Video Transport
> Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
>=20
>=20
>=20

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



From avt-bounces@ietf.org Fri Feb 23 15:51:23 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKhN8-00084o-Ec; Fri, 23 Feb 2007 15:50:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKhMi-0006bx-0P; Fri, 23 Feb 2007 15:50:04 -0500
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HKhMh-0006Qr-9P; Fri, 23 Feb 2007 15:50:03 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 2DE6732981;
	Fri, 23 Feb 2007 20:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HKhMh-00071C-1W; Fri, 23 Feb 2007 15:50:03 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HKhMh-00071C-1W@stiedprstage1.ietf.org>
Date: Fri, 23 Feb 2007 15:50:03 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-hdrext-10.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: A general mechanism for RTP Header Extensions
	Author(s)	: H. Desineni, D. Singer
	Filename	: draft-ietf-avt-rtp-hdrext-10.txt
	Pages		: 21
	Date		: 2007-2-23
	
This document provides a general mechanism to use the header-
   extension feature of RTP (the Real Time Transport Protocol).  It
   provides the option to use a small number of small extensions in each
   RTP packet, where the universe of possible extensions is large and
   registration is de-centralized.  The actual extensions in use in a
   session are signaled in the setup information for that session.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-avt-rtp-hdrext-10.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-avt-rtp-hdrext-10.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-hdrext-10.txt

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

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


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org Fri Feb 23 15:51:30 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKhNT-0000Nr-T9; Fri, 23 Feb 2007 15:50:51 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKhNB-0008F0-BD; Fri, 23 Feb 2007 15:50:33 -0500
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HKhNA-0005Y8-VL; Fri, 23 Feb 2007 15:50:33 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id DEBB81760B;
	Fri, 23 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HKhMg-00070L-KT; Fri, 23 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HKhMg-00070L-KT@stiedprstage1.ietf.org>
Date: Fri, 23 Feb 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-topologies-04.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: RTP Topologies
	Author(s)	: M. Westerlund, S. Wenger
	Filename	: draft-ietf-avt-topologies-04.txt
	Pages		: 20
	Date		: 2007-2-23
	
This document discucsses multi-endpoint topologies used in RTP
   based environments.  In particular, centralized topologies commonly
   employed in the video conferencing industry are mapped to the RTP
   terminology.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-avt-topologies-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-avt-topologies-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-topologies-04.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-avt-topologies-04.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org Fri Feb 23 15:51:35 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKhNA-0008Do-H5; Fri, 23 Feb 2007 15:50:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKhMi-0006ca-9V; Fri, 23 Feb 2007 15:50:04 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HKhMh-0006RX-Rw; Fri, 23 Feb 2007 15:50:04 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 5E25626ECA;
	Fri, 23 Feb 2007 20:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HKhMh-000719-0q; Fri, 23 Feb 2007 15:50:03 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HKhMh-000719-0q@stiedprstage1.ietf.org>
Date: Fri, 23 Feb 2007 15:50:03 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-smpte-rtp-09.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: Associating Time-codes with RTP streams
	Author(s)	: D. Singer
	Filename	: draft-ietf-avt-smpte-rtp-09.txt
	Pages		: 21
	Date		: 2007-2-23
	
This document describes a mechanism for associating time-codes, as
   defined by the Society of Motion Picture and Television Engineers
   (SMPTE), with media streams, in a way that is independent of the RTP
   payload format of the media stream itself.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-avt-smpte-rtp-09.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-avt-smpte-rtp-09.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-smpte-rtp-09.txt

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

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


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org Fri Feb 23 16:35:34 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKi3y-0006Cv-Qe; Fri, 23 Feb 2007 16:34:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKi3x-0006Br-Fr
	for avt@ietf.org; Fri, 23 Feb 2007 16:34:45 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKi3u-0007ya-AZ
	for avt@ietf.org; Fri, 23 Feb 2007 16:34:45 -0500
Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l1NLYepf014599
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 23 Feb 2007 13:34:40 -0800
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com
	[172.30.32.65])
	by hamtaro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l1NLYcmk006892; Fri, 23 Feb 2007 13:34:39 -0800 (PST)
Received: from NAEX01.qualcomm.com ([129.46.51.60]) by
	SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 23 Feb 2007 13:34:38 -0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: R: [AVT]CCMdraftreview--should"bandwidth"includetheheaderoverhead
Date: Fri, 23 Feb 2007 13:34:38 -0800
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B0297CB18@NAEX01.na.qualcomm.com>
In-Reply-To: <ybuejohkjtk.fsf@jesup.eng.wgate.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: R: [AVT]CCMdraftreview--should"bandwidth"includetheheaderoverhead
Thread-Index: AcdXXNXrEYCAJcHBRvq05phqeSb3rQAMZHsQ
References: <DD8B8FEBBFAF9E488F63FF0F1A69EDD1033B4E24@ftrdmel1.rd.francetelecom.fr>
	<ybuejohkjtk.fsf@jesup.eng.wgate.com>
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: "Randell Jesup" <rjesup@wgate.com>,
	"SOLLAUD Aurelien RD-TECH-LAN" <aurelien.sollaud@orange-ftgroup.com>
X-OriginalArrivalTime: 23 Feb 2007 21:34:38.0437 (UTC)
	FILETIME=[6B899950:01C75792]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org



> -----Original Message-----
> From: Randell Jesup [mailto:rjesup@wgate.com]
> Sent: Friday, February 23, 2007 6:52 AM
> To: SOLLAUD Aurelien RD-TECH-LAN
> Cc: avt@ietf.org
> Subject: Re: R: [AVT]CCMdraftreview--
> should"bandwidth"includetheheaderoverhead
>=20
> "SOLLAUD Aurelien RD-TECH-LAN" <aurelien.sollaud@orange-ftgroup.com>
> writes:
> >> The main discussion in this thread is around the TMMBR
> >> feedback message (or whatever it will be re-named).
> >>
> >> Initially, two proposals were made for TMMBR: to signal the
> >> codec bitrate, or the IP gross bitrate.
> >> IMO, both solutions are more or less inaccurate, depending on
> >> the protocol stack running in the bottleneck.
> >
> >Anyway, I would find useful to have a standard feedback message to
> >signal a desired codec bitrate back to the media sender. It would
avoid
> >a per codec definition like the codec mode requests embedded in the
RTP
> >payload header we have in RFC 3267 (AMR), RFC 3558 (SMV, EVRC), RFC
4348
> >(VMR-WB), RFC 4749 (G.729.1), ...
> >
> >I initially thought it was the goal of TMMBR. But the current
discussion
> >shows that it is likely to be something else.
>=20

The discussion exists because some people think it is something else
than what you understood. The authors did not specify which definition
was meant out of the two options and the discussion is to clarify that.

> Correct; TMMBR was not designed as a codec-bitrate-switch-request tool
> (witness the name).

The name is misleading if it is not meant for just codec control.
If TMMBR was not designed as codec-bitrate-switch-request then the name
of the draft is misleading ""Codec Control Messages in the RTP
Audio-Visual Profile with Feedback (AVPF)"

If TMMBR is not pure codec-bitrate-switch-request tool, why is it
present in a draft with title "Codec Control Messages in the RTP
Audio-Visual Profile with Feedback (AVPF)"? This is what really puzzles
me. I've posted this question many times and it never got answered.

>  It could result in a sender deciding to switch
> bitrates in a multi-bitrate codec, but counting on specific values to
mean
> specific things (like "switch from 16Kbps mode to 8Kbps mode" by
> indicating
> 8000 bps) is dangerous with TMMBR.  For example, a midbox might modify
a
> TMMBR request by subtracting some amount for overhead it knows about,
> causing your 8000 to become 7500.

Middle box in the media path can be either RTP mixer or RTP translator
RTP mixer is an RTP end point and RTP translator is not.

If it is a pure codec control RTCP message then the RTP middle box
(mixer/translator) must not modify it unless there is codec media
transcoding or thinning taking place in the RTP media path.

>=20
> >Most modern audio codecs will be multi-bitrate, it is desirable to
have
> >a standard RTCP message to signal codec bitrate change requests,
instead
> >of incorrectly using the RTP media path to perform this. And it would
be
> >interesting no to reduce it to AVPF profile.
>=20
> I'm not sure I understand "interesting no to reduce it to AVPF
profile".
> I think it may make sense to consider a draft for something other than
> TMMBR to provide the ability to request/suggest (pure) codec rate
shifts,
> for reasons other than restriction.=20

RTCP message related to codec rate shifts should be in CCM and the
message which is not purely codec rate should NOT be in CCM. If TMMBR is
pure codec bitrate then it should stay (with an appropriate name - MCBR
MaxCodecBitRate) in CCM draft. If TMMBR includes header overhead then it
is not a pure codec command and has to go into a new draft.

SOLLAUD's point was that a true/generic codec rate switch message is
useful for all RTP profiles and not just AVPF (based on the codecs
listed by him that currently use codec commands in RTP payload field).=20


> The two items don't work well
> together
> in one model (as evidenced by the discussions/disagreements here over
TIAS
> vs AS vs tuples), but may work well when separated into two mechanisms
> with
> different goals and uses.
>=20
> --
> Randell Jesup, Worldgate (developers of the Ojo videophone), ex-Amiga
OS
> team
> rjesup@wgate.com
> "The fetters imposed on liberty at home have ever been forged out of
the
> weapons
> provided for defence against real, pretended, or imaginary dangers
from
> abroad."
> 		- James Madison, 4th US president (1751-1836)
>=20
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

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



From avt-bounces@ietf.org Fri Feb 23 17:01:55 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKiSi-0003MM-LX; Fri, 23 Feb 2007 17:00:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKiSh-0003Lu-0q
	for avt@ietf.org; Fri, 23 Feb 2007 17:00:19 -0500
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKiSf-0004RG-NX
	for avt@ietf.org; Fri, 23 Feb 2007 17:00:19 -0500
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:61603
	helo=[192.168.0.3])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HKiSf-00053m-0q; Fri, 23 Feb 2007 22:00:17 +0000
In-Reply-To: <DA7FB42D-7340-4101-B635-EDEAB1A373B7@csperkins.org>
References: <BAY101-F389E28EE72B7EE9B381353D98F0@phx.gbl>
	<DA7FB42D-7340-4101-B635-EDEAB1A373B7@csperkins.org>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <704C49A7-D6D5-43E0-9F35-D57138DE00C6@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Duplicate RTP packets
Date: Fri, 23 Feb 2007 22:00:16 +0000
To: Jorge Canas <jcanas2000@hotmail.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On 23 Feb 2007, at 10:22, Colin Perkins wrote:
> On 22 Feb 2007, at 18:29, Jorge Canas wrote:
>> I have searched RFC 3550, but can't find an answer to the  
>> following questions:
>>
>> Are RTP stacks required to drop received RTP packets with the same  
>> RTP sequence number (duplicate RTP packets)?  If so, how much  
>> history (in number of packets) does the RTP stack need to maintain  
>> in order to detect duplicates? Or is it only required to detect  
>> duplicates arriving piggy backed?
>>
>> If the RTP stack is not required to drop those packets, I guess  
>> the application is expected to deal with duplicates?
>
> The standards don't specify implementation details such as these.  
> My RTP library passes duplicates to the application, but there are  
> other implementations which suppress duplicates in the RTP layer.  
> The boundary between the RTP layer and the application is  
> intentionally fussy (see http://portal.acm.org/citation.cfm? 
> doid=99508.99553)

s/fussy/fuzzy/ of course... *sigh*

Colin

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



From avt-bounces@ietf.org Sat Feb 24 11:38:26 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKzru-0007yw-F6; Sat, 24 Feb 2007 11:35:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKzrt-0007yk-BN
	for avt@ietf.org; Sat, 24 Feb 2007 11:35:29 -0500
Received: from zcars04e.nortel.com ([47.129.242.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKzrr-0001Nf-Ue
	for avt@ietf.org; Sat, 24 Feb 2007 11:35:29 -0500
Received: from zcarhxs1.corp.nortel.com (zcarhxs1.corp.nortel.com
	[47.129.230.89])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	l1OGQwT03875; Sat, 24 Feb 2007 11:26:59 -0500 (EST)
Received: from [47.130.25.52] ([47.130.25.52] RDNS failed) by
	zcarhxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 24 Feb 2007 11:35:03 -0500
Message-ID: <45E0691F.1070702@nortel.com>
Date: Sat, 24 Feb 2007 11:34:39 -0500
From: "Tom-PT Taylor" <taylor@nortel.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Duplicate RTP packets
References: <BAY101-F389E28EE72B7EE9B381353D98F0@phx.gbl>
	<DA7FB42D-7340-4101-B635-EDEAB1A373B7@csperkins.org>
	<704C49A7-D6D5-43E0-9F35-D57138DE00C6@csperkins.org>
In-Reply-To: <704C49A7-D6D5-43E0-9F35-D57138DE00C6@csperkins.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Feb 2007 16:35:04.0003 (UTC)
	FILETIME=[BC5A6130:01C75831]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

I just figured it was your Scottish accent on paper :-)

Colin Perkins wrote:
> On 23 Feb 2007, at 10:22, Colin Perkins wrote:
>> On 22 Feb 2007, at 18:29, Jorge Canas wrote:
>>> I have searched RFC 3550, but can't find an answer to the  
>>> following questions:
>>>
>>> Are RTP stacks required to drop received RTP packets with the same  
>>> RTP sequence number (duplicate RTP packets)?  If so, how much  
>>> history (in number of packets) does the RTP stack need to maintain  
>>> in order to detect duplicates? Or is it only required to detect  
>>> duplicates arriving piggy backed?
>>>
>>> If the RTP stack is not required to drop those packets, I guess  
>>> the application is expected to deal with duplicates?
>> The standards don't specify implementation details such as these.  
>> My RTP library passes duplicates to the application, but there are  
>> other implementations which suppress duplicates in the RTP layer.  
>> The boundary between the RTP layer and the application is  
>> intentionally fussy (see http://portal.acm.org/citation.cfm? 
>> doid=99508.99553)
> 
> s/fussy/fuzzy/ of course... *sigh*
> 
> Colin
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
> 

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



From avt-bounces@ietf.org Sun Feb 25 23:32:49 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLXVR-0001W3-8y; Sun, 25 Feb 2007 23:30:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HLXVP-0001Vq-JB
	for avt@ietf.org; Sun, 25 Feb 2007 23:30:31 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLXVM-0004AO-Nz
	for avt@ietf.org; Sun, 25 Feb 2007 23:30:31 -0500
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l1Q4UOmp024419
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Sun, 25 Feb 2007 20:30:24 -0800
Received: from SANEXCAS02.na.qualcomm.com (sanexcas02.qualcomm.com
	[172.30.36.176])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l1Q4UNmu014284; Sun, 25 Feb 2007 20:30:24 -0800
Received: from NAEX01.qualcomm.com ([129.46.51.60]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 25 Feb 2007 20:30:23 -0800
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
Subject: RE: Issues with using tuples in TMMBR was:Re: R: [AVT] CCM
	draftreview --	should"bandwidth"includetheheaderoverhead
Date: Sun, 25 Feb 2007 20:30:17 -0800
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B0297CBA8@NAEX01.na.qualcomm.com>
In-Reply-To: <E9D1028EC5C22B418B5D54CA6EA27C579A5EBF@PTPEVS108BA020.idc.cww.telecomitalia.it>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Issues with using tuples in TMMBR was:Re: R: [AVT] CCM
	draftreview --	should"bandwidth"includetheheaderoverhead
Thread-Index: AcdXNr0l71oyisQ+TnacUBEyq9I83wAD2lPgAIVaIhA=
References: <45DEC41A.1010101@ericsson.com>
	<E9D1028EC5C22B418B5D54CA6EA27C579A5EBF@PTPEVS108BA020.idc.cww.telecomitalia.it>
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: "Franceschini Guido" <guido.franceschini@telecomitalia.it>
X-OriginalArrivalTime: 26 Feb 2007 04:30:23.0574 (UTC)
	FILETIME=[D4D2EF60:01C7595E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2c12be3f3a8d57895fb9c003e1517c01
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org


Guido, I think you meant

At time t0:
"-receiver R2 sends TMMBR(45 kbps, 50 bytes)" instead of "-receiver R2 =
sends TMMBR(35 kbps, 40 bytes)"=20

Your explanation looks straight forward to me.=20

A sender need not maintain a list of tmmbr tuples all the time. Only the =
active limitation needs to be stored. Whenever a new TMMBR tuple is =
received, it needs to do just one comparison to determine whether a =
TMMBN with new limitation is necessary. No complexity involved there.

I see one difference when I compared your example with the example from =
Magnus. Magnus interpreted the first element in the tuple as pure header =
overhead. Your example interpreted it as total bit-rate up to particular =
protocol layer including codec media bit-rate.

If I map your example to a simple p2p session:
SDP offer includes the TMMBR tuple (Max 'receive' rate, 'recv' per =
packet overhead) and SDP answer includes TMMBN tuple (Max 'send' codec =
media bit-rate, max 'send' packet rate). Max receive rate in TMMBR tuple =
includes both codec media rate and header overhead due to protocol =
layers.=20

--Hari

> -----Original Message-----
> From: Franceschini Guido [mailto:guido.franceschini@telecomitalia.it]
> Sent: Friday, February 23, 2007 5:31 AM
> To: Magnus Westerlund
> Cc: avt@ietf.org
> Subject: RE: Issues with using tuples in TMMBR was:Re: R: [AVT] CCM
> draftreview -- should"bandwidth"includetheheaderoverhead
>=20
> Magnus,
>=20
> let me first check if I have understood your scenario. Then I'll give =
my
> view on your mail: just disregard it if I missed to understand the
> scenario in the first place.
>=20
>=20
> Scanario: a sender S and multiple receivers R1, R2 ... RN
>=20
> The sender is notified of a number of bottlneck tuples B1, B2 ... BN, =
each
> expressed for a potentially different stack.
> Based on some internal logic, the sender decides how to encode and
> packetize its traffic, and also acknowledges with TMMBN to let each
> receiver aware of the currently valid limits.
>=20
> If the above is correct, then let's go on.
>=20
> There is a set of challenges in this scenario:
>=20
> 1) identification of the most restrictive bottleneck among the B1 ... =
BN
> 2) generation of the TMMBN to let receiver know about the current
> restriction
> 3) reduction of useless TMMBR traffic
> 4) accuracy of the Bx data
>=20
> Concerning 1) identification of the most restrictive bottleneck among =
the
> B1 ... BN
>=20
> The usage of a tuple instead of a single value allows for a more =
accurate
> description, but it is easy to derive from an accurate description a =
less
> accurate one ;-)
> More specifically, if you indicated in the TMMBR the IP gross bitrate, =
or
> the media bitrate, you were actually impling some packetrate =
(actually,
> the generator of the TMMBR implied a maxpacketrate). You can now apply =
as
> well a maxpacketrate, with the advantage that you are now the sender, =
and
> can therefore apply a more close-to-reality maxpacketrate.
> Suppose you apply a maxpacketrate of 50; you would obtain from:
> (35 kbps, 40 bytes) =3D=3D> 35000-(40*50*8)=3D19000
> (45 kbps, 50 bytes) =3D=3D> 45000-(50*50*8)=3D25000
>=20
> Thus, you go back to the same complexity that you have to deal with =
anyway,
> with just a better accuracy (the sender applied a uniform and credible
> maxpacketrate, instead of having each receiver applying his own =
guess).
> Also, the sender knows that it must not exceed 50 pkt/sec.
>=20
>=20
> Concerning 2) generation of the TMMBN to let receiver know about the
> current restriction
>=20
> Here the goal is to let each receiver aware of the current limits, so =
that
> it will generate new TMMBR only if they have an impact on the sender.
> It is definitely undesirable that the sender generates a TMMBN listing =
all
> tuples that it is currently taking into account.
> But if the TMMBN contains a different tuple, made of:
> <media bitrate, maxpacketrate>
> then each receiver is again able to determine whether it should send a
> TMMBR or not.
> Let's use the figures above:
>=20
> at time t0:
> - receiver R1 sends TMMBR(35 kbps, 40 bytes)
> - receiver R2 sends TMMBR(35 kbps, 40 bytes)
> =3D=3D> sender sends TMMBN(19000, 50 pkt/sec, R1)
>=20
> at time t1:
> - R2 changes from (45 kbps, 50 bytes) to (40 kbps, 50 bytes)
> =3D=3D> R2 computes that 19000 + (50*50*8) =3D 39000, thus does not =
send TMMBR
>=20
> at time t2:
> - R2 changes to (38 kbps, 50 bytes)
> =3D=3D> R2 sends TMMBR
> - Sender computes (38 kbps, 50 bytes) =3D=3D> 38000-(50*50*8)=3D18000
> =3D=3D> sender sends TMMBN(18000, 50 pkt/sec, R2)
>=20
>=20
> Concerning 3) reduction of useless TMMBR traffic
>=20
> The above algorithm shows how the usage of tuples instead of single =
values
> can be managed with the same efficiency
>=20
>=20
> Concerning 4) accuracy of the Bx data
>=20
> The usage of tuples instead of single values allows, even in such p2mp
> scenario, to compute more accurate limits.
>=20
>=20
> To conclude: IMHO the usage of tuples have no CONS with respect to =
picking
> up a single value, while providing benefits instead.
>=20
> Cheers
> Guido
>=20
>=20
> > -----Original Message-----
> > From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> > Sent: venerd=EC 23 febbraio 2007 11.38
> > To: Magnus Westerlund
> > Cc: Franceschini Guido; avt@ietf.org
> > Subject: Issues with using tuples in TMMBR was:Re: R: [AVT] CCM =
draft
> > review -- should"bandwidth"includetheheaderoverhead
> >
> >
> > Bo and me has spent some time thinking about what we see as
> > one of the
> > major real problems with using tuples in TMMBR. As one changed TMMBR
> > from a one-dimensional problem to a two dimensional problem,
> > the concept
> > of a single owner of the restriction took a hike. Thus we end
> > up with a
> > need to indicate multiple tuples that are the active
> > restrictions. This
> > will create extra complexities. There will also be more data
> > to transmit.
> >
> > We are working on this, and haven't yet verified and simulated it to
> > understand the full implications. However we do like to share
> > this with
> > you to provide you the opportunity to think about the same
> > problem and
> > possibly find any issues we have forgotten about. Our current
> > proposal
> > for how this would work is the following:
> >
> > Lets start assuming that there is a session with a number of
> > participants. They can all have restriction tuples (bit-rate,
> > overhead).
> > So if a media receiver has some change he first checks if the
> > new values
> > are an actually restriction compared to the current set of
> > restrictions
> > in the session. If that is the case it sends a TMMBR message to the
> > media sender. The media sender checks the restriction compared to =
its
> > current set and see if that is an actual restriction given its sets
> > (remember the asynchronous behavior in a multi-party session) and if
> > that allows it to drop some of the previous restriction as being =
less
> > restrictive then the new one. Then it sends out the TMMBN with the
> > current set.
> >
> > So how does on determine which is the current set of restrictions. =
Me
> > and Bo have been kicking around an algorithm that might
> > result in this.
> > However we need to spend some time on verification.
> >
> > 1. First sort the set X of restriction tuples according to bit-rate
> > creating a vector of tuples, X1 to Xn with the X1 carrying the =
lowest
> > bit-rate and Xn the highest value.
> >
> > 2. Eleminate all tuples in X with a overhead value smaller than the
> > value in X1.
> >
> > 3. Repeat step 2 for all elements in X from the lowest to the
> > next highest.
> >
> > 4. A reduced set X has been created.
> >
> > The above algorithm eliminates all the tuples that doesn't provide a
> > restriction because they allow a higher bit-rate and their bit-rate
> > grows slower than the previous one when packet-rate increases.
> >
> > A second step would be to eliminate all tuples where they
> > although have
> > higher bit-rate, the overhead value is only slightly larger
> > so that the
> > first restriction does not allow a packet rate that is large enough,
> > even when all the allowed bit-rate is spent on headers. An example =
to
> > illustrate this:
> >
> > Lets say that you have a tuple of (35kbps, 40 bytes) and a second =
one
> > that is (45 kbps, 50 bytes).  The maximum packet rate the first one
> > allows are 35000 /(40*8) =3D 109.375 packets / s. Performing the =
same
> > calculation for the second tuple yields 45000/(50*8) =3D 112.5
> > packets/s.
> > Thus the second tuple does not provide a restriction that is
> > applicable
> > given that the first one is included in the set.
> >
> > 5. For each tuple in X calculate the largest possible packet-rate
> > yielding no useful work, i.e. bit-rate / overhead and store
> > in vector Y.
> >
> > 6. For each element in X, index by i, in case Yi+1 is larger than Yi
> > remove Yi+1 and Xi+1 from the sets and repeat comparison for i.
> >
> > However looking at the above there is evident that one could do more
> > here with some additional information. The comparison using
> > packet rates
> > that means no useful data is transported is easy to do but doesn't
> > restrict as well as is possible. There exist two parameters
> > that could
> > be introduced into this to provide restrictions that exist in real
> > usage. However these values needs to be the same and known to all
> > session participants to be possible to utilize.
> >
> > The first one would to explicit declare the maximum packet rate the
> > application has any usage of at all for this media. For example this
> > could be restricted by codec, or by the codec in combination with =
the
> > session maximum bit-rate. This maximum packet rate value
> > would allow one
> > to eliminate from the set of restriction all tuples whose bit-rate
> > divided by overhead is larger than the session maximum packet-rate.
> >
> > A second possible restriction would to declare a minimum of useful
> > rtp-payload bit-rate. In many cases the media codec or
> > application has
> > knowledge about what the smallest bit-rate that would provide any
> > utility from the media at all. For example for an audio session =
using
> > the AMR speech codec packetized in RTP (RFC 3267), that
> > bit-rate would
> > be 4.75kbps. I ignore the per frame and RTP payload overhead in this
> > case, but those could be considered to be included also. This =
minimal
> > overhead could then be subtracted from all the tuples bit-rate =
values
> > prior to running the above presented algorithm. Note that this =
second
> > restriction needs to be applied prior to the first one if
> > both where to
> > be present.
> >
> > What these restrictions provides are some application sanity
> > restrictions on what possible combination of useful bit-rate
> > and maximum
> > packet rate it can produce and still do some good. However
> > these would
> > need to be signaled and could also result in some dispute
> > during session
> > establishment if the applications aren't agreeing on a value.
> >
> > So the big question to you is: Is solving the inaccuracy problem =
that
> > introducing a tuple solves worth the extra complexities and =
overhead?
> >
> > Cheers
> >
> > Magnus Westerlund
> >
> > IETF Transport Area Director & TSVWG Chair
> > =
----------------------------------------------------------------------
> > Multimedia Technologies, Ericsson Research EAB/TVA/A
> > =
----------------------------------------------------------------------
> > Ericsson AB                | Phone +46 8 4048287
> > Torshamsgatan 23           | Fax   +46 8 7575550
> > S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> > =
----------------------------------------------------------------------
> >
> --------------------------------------------------------------------
>=20
> CONFIDENTIALITY NOTICE
>=20
> This message and its attachments are addressed solely to the persons =
above
> and may contain confidential information. If you have received the =
message
> in error, be informed that any use of the content hereof is =
prohibited.
> Please return it immediately to the sender and delete the message. =
Should
> you have any questions, please contact us by replying to
> webmaster@telecomitalia.it.
>=20
>         Thank you
>=20
>                                         www.telecomitalia.it
>=20
> --------------------------------------------------------------------
>=20
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

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



From avt-bounces@ietf.org Mon Feb 26 01:53:44 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLZiH-0007N7-Uq; Mon, 26 Feb 2007 01:51:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HLZiG-0007HL-8X
	for avt@ietf.org; Mon, 26 Feb 2007 01:51:56 -0500
Received: from [212.25.125.1] (helo=aclmsg.corp.audiocodes.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLZiE-0005z0-S2
	for avt@ietf.org; Mon, 26 Feb 2007 01:51:56 -0500
Content-class: urn:content-classes:message
Subject: RE: [AVT] RFC 4733 flash event
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 26 Feb 2007 08:51:22 +0200
Message-ID: <79B4F738DDD4EF4F85A4641A0FE5EFD602CA8BAF@aclmsg.corp.audiocodes.com>
X-MIMEOLE: Produced By Microsoft Exchange V6.5
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] RFC 4733 flash event
Thread-Index: AcdVw9eBHNuzFjNgQmyOYly/iym6gwDrD2MQ
From: "Yuval Nissan" <Yuval.Nissan@audiocodes.com>
To: "Tom-PT Taylor" <taylor@nortel.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: Nachum Frid <Nachum.Frid@audiocodes.com>,
	Eli  Shoval <Eli.Shoval@audiocodes.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Is it possible to add the line-related events to the 2833biscas draft as
another type of signaling (instead of creating new I-D only for this
type)?

Regards,
Yuval=20

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortel.com]=20
Sent: Wednesday, February 21, 2007 4:22 PM
To: Yuval Nissan
Cc: avt@ietf.org; Nachum Frid
Subject: Re: [AVT] RFC 4733 flash event

Someone has to write an I-D re-standardizing the line events they want=20
to preserve. When I worked on 2833bis, 2833biscas and 2833bisdata, no=20
one indicated any interest in the line-related events. Now, it seems=20
like there is some interest. I wouldn't think it would be a big job to=20
write the draft, but I feel I've done my part.

BTW we did make sure the codepoints remain available for allocation.

Yuval Nissan wrote:
> Hi,
>=20
> =20
>=20
> We have noticed that the line flash event (code 16) defined in RFC
2833
> is now deprecated in the new RFC 4733.=20
>=20
> =20
>=20
> +-------------+---------------------------------------+-------------+
> | Event Codes | RFC 2833 Description                  | Disposition |
> +-------------+---------------------------------------+-------------+
> |        0-15 | DTMF digits                           | RFC 4733    |
> |          16 | Line flash (deprecated)               | Reserved    |
>=20
> =20
>=20
> =20
>=20
> Audiocodes and other vendors already use this event in products in the
> field (and will continue to use it in the future).
>=20
> =20
>=20
> What is the reason for this change (not keeping backward compatible)?
>=20
> How this issue can be resolved, so no interop problems start to rise?

>=20
> =20
>=20
> Regards,
>=20
> Yuval=20
>=20
> =20
>=20
>=20
>=20
>=20
>
------------------------------------------------------------------------
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

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



From avt-bounces@ietf.org Mon Feb 26 03:08:44 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLat3-00073I-O9; Mon, 26 Feb 2007 03:07:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HLat1-0006w4-Pz
	for avt@ietf.org; Mon, 26 Feb 2007 03:07:07 -0500
Received: from mailf.telecomitalia.it ([156.54.233.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLasv-0007JM-IK
	for avt@ietf.org; Mon, 26 Feb 2007 03:07:07 -0500
Received: from ptpxch010ba020.idc.cww.telecomitalia.it ([156.54.240.53]) by
	mailf.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830);
	Mon, 26 Feb 2007 09:07:00 +0100
Received: from PTPEVS108BA020.idc.cww.telecomitalia.it ([156.54.241.227]) by
	ptpxch010ba020.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 26 Feb 2007 09:06:59 +0100
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Importance: normal
Priority: normal
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Issues with using tuples in TMMBR was:Re: R: [AVT] CCM
	draftreview --	should"bandwidth"includetheheaderoverhead
Date: Mon, 26 Feb 2007 09:06:59 +0100
Message-ID: <E9D1028EC5C22B418B5D54CA6EA27C579A5ECB@PTPEVS108BA020.idc.cww.telecomitalia.it>
In-Reply-To: <2CA3E1B6CEC064449CAA7D0FAB46079B0297CBA8@NAEX01.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Issues with using tuples in TMMBR was:Re: R: [AVT] CCM
	draftreview --	should"bandwidth"includetheheaderoverhead
thread-index: AcdXNr0l71oyisQ+TnacUBEyq9I83wAD2lPgAIVaIhAAB6oSQA==
From: "Franceschini Guido" <guido.franceschini@telecomitalia.it>
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>
X-OriginalArrivalTime: 26 Feb 2007 08:06:59.0691 (UTC)
	FILETIME=[171D03B0:01C7597D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 354d6627469d0be959806e15912c47f1
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

> Guido, I think you meant
>=20
> At time t0:
> "-receiver R2 sends TMMBR(45 kbps, 50 bytes)" instead of=20
> "-receiver R2 sends TMMBR(35 kbps, 40 bytes)"=20

Yes, thanks!
>=20
> Your explanation looks straight forward to me.=20
>=20
> A sender need not maintain a list of tmmbr tuples all the=20
> time. Only the active limitation needs to be stored. Whenever=20
> a new TMMBR tuple is received, it needs to do just one=20
> comparison to determine whether a TMMBN with new limitation=20
> is necessary. No complexity involved there.

A downside of your algorithm is that if the current limitation (and only =
stored limitation in the server) is due to Rn, and Rn now communicates =
an higher limit, your server does not know to what higher limit to move.
IMO we should not over-specify here: the complex algorithm from Magnus =
and Bo is one, mine is another, your yet another one =3D=3D> it's an =
implementation matter, that balances complexity and effectiveness.
=20
> I see one difference when I compared your example with the=20
> example from Magnus. Magnus interpreted the first element in=20
> the tuple as pure header overhead. Your example interpreted=20
> it as total bit-rate up to particular protocol layer=20
> including codec media bit-rate.

The key aspect of my suggestion here, is that each peer communicates =
accurate data, no guesses.
The accurate data that a receiver can communicate relates to the <TIDC, =
MPO> tuple (hopefully measured at the most precise layer of its stack); =
it has no control on the packet rate, thus it should better not imply =
any.
The accurate data that a sender can communicate relates to <media =
bitrate, maxpacketrate>, which are both under its control.
This works nicely in p2p as well as in p2mp.
Note that the metrics generated by the sender correspond to the <TIAS, =
maxprate> tuple already defined in RFC3890 !
=20
> If I map your example to a simple p2p session:
> SDP offer includes the TMMBR tuple (Max 'receive' rate,=20
> 'recv' per packet overhead) and SDP answer includes TMMBN=20
> tuple (Max 'send' codec media bit-rate, max 'send' packet=20
> rate). Max receive rate in TMMBR tuple includes both codec=20
> media rate and header overhead due to protocol layers.=20

Exactly (we only need to find good definitions for such semantics, so =
that we get uniform on this)
Guido

PS: the computation of the RTP Header extension is somehow disputable. =
Should it be part of the media bitrate figure (TIAS) provided by the =
sender (it should not, per RFC3890)? Should it be part of the mean =
packet overhead (MPO) figure provided by the receiver (it should, since =
it is overhead, but it should not, since it is not under the control of =
the receiver)?
IMO this is a detail that we could disregard for the time being: maybe =
the solution could be to identify a bw portion that can be assigned to =
RTP Header Extension, similarly to RTCP.

=20
> --Hari
>=20
> > -----Original Message-----
> > From: Franceschini Guido=20
> [mailto:guido.franceschini@telecomitalia.it]
> > Sent: Friday, February 23, 2007 5:31 AM
> > To: Magnus Westerlund
> > Cc: avt@ietf.org
> > Subject: RE: Issues with using tuples in TMMBR was:Re: R: [AVT] CCM
> > draftreview -- should"bandwidth"includetheheaderoverhead
> >=20
> > Magnus,
> >=20
> > let me first check if I have understood your scenario. Then=20
> I'll give my
> > view on your mail: just disregard it if I missed to understand the
> > scenario in the first place.
> >=20
> >=20
> > Scanario: a sender S and multiple receivers R1, R2 ... RN
> >=20
> > The sender is notified of a number of bottlneck tuples B1,=20
> B2 ... BN, each
> > expressed for a potentially different stack.
> > Based on some internal logic, the sender decides how to encode and
> > packetize its traffic, and also acknowledges with TMMBN to let each
> > receiver aware of the currently valid limits.
> >=20
> > If the above is correct, then let's go on.
> >=20
> > There is a set of challenges in this scenario:
> >=20
> > 1) identification of the most restrictive bottleneck among=20
> the B1 ... BN
> > 2) generation of the TMMBN to let receiver know about the current
> > restriction
> > 3) reduction of useless TMMBR traffic
> > 4) accuracy of the Bx data
> >=20
> > Concerning 1) identification of the most restrictive=20
> bottleneck among the
> > B1 ... BN
> >=20
> > The usage of a tuple instead of a single value allows for a=20
> more accurate
> > description, but it is easy to derive from an accurate=20
> description a less
> > accurate one ;-)
> > More specifically, if you indicated in the TMMBR the IP=20
> gross bitrate, or
> > the media bitrate, you were actually impling some=20
> packetrate (actually,
> > the generator of the TMMBR implied a maxpacketrate). You=20
> can now apply as
> > well a maxpacketrate, with the advantage that you are now=20
> the sender, and
> > can therefore apply a more close-to-reality maxpacketrate.
> > Suppose you apply a maxpacketrate of 50; you would obtain from:
> > (35 kbps, 40 bytes) =3D=3D> 35000-(40*50*8)=3D19000
> > (45 kbps, 50 bytes) =3D=3D> 45000-(50*50*8)=3D25000
> >=20
> > Thus, you go back to the same complexity that you have to=20
> deal with anyway,
> > with just a better accuracy (the sender applied a uniform=20
> and credible
> > maxpacketrate, instead of having each receiver applying his=20
> own guess).
> > Also, the sender knows that it must not exceed 50 pkt/sec.
> >=20
> >=20
> > Concerning 2) generation of the TMMBN to let receiver know about the
> > current restriction
> >=20
> > Here the goal is to let each receiver aware of the current=20
> limits, so that
> > it will generate new TMMBR only if they have an impact on=20
> the sender.
> > It is definitely undesirable that the sender generates a=20
> TMMBN listing all
> > tuples that it is currently taking into account.
> > But if the TMMBN contains a different tuple, made of:
> > <media bitrate, maxpacketrate>
> > then each receiver is again able to determine whether it=20
> should send a
> > TMMBR or not.
> > Let's use the figures above:
> >=20
> > at time t0:
> > - receiver R1 sends TMMBR(35 kbps, 40 bytes)
> > - receiver R2 sends TMMBR(35 kbps, 40 bytes)
> > =3D=3D> sender sends TMMBN(19000, 50 pkt/sec, R1)
> >=20
> > at time t1:
> > - R2 changes from (45 kbps, 50 bytes) to (40 kbps, 50 bytes)
> > =3D=3D> R2 computes that 19000 + (50*50*8) =3D 39000, thus does=20
> not send TMMBR
> >=20
> > at time t2:
> > - R2 changes to (38 kbps, 50 bytes)
> > =3D=3D> R2 sends TMMBR
> > - Sender computes (38 kbps, 50 bytes) =3D=3D> =
38000-(50*50*8)=3D18000
> > =3D=3D> sender sends TMMBN(18000, 50 pkt/sec, R2)
> >=20
> >=20
> > Concerning 3) reduction of useless TMMBR traffic
> >=20
> > The above algorithm shows how the usage of tuples instead=20
> of single values
> > can be managed with the same efficiency
> >=20
> >=20
> > Concerning 4) accuracy of the Bx data
> >=20
> > The usage of tuples instead of single values allows, even=20
> in such p2mp
> > scenario, to compute more accurate limits.
> >=20
> >=20
> > To conclude: IMHO the usage of tuples have no CONS with=20
> respect to picking
> > up a single value, while providing benefits instead.
> >=20
> > Cheers
> > Guido
> >=20
> >=20
> > > -----Original Message-----
> > > From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> > > Sent: venerd=EC 23 febbraio 2007 11.38
> > > To: Magnus Westerlund
> > > Cc: Franceschini Guido; avt@ietf.org
> > > Subject: Issues with using tuples in TMMBR was:Re: R:=20
> [AVT] CCM draft
> > > review -- should"bandwidth"includetheheaderoverhead
> > >
> > >
> > > Bo and me has spent some time thinking about what we see as
> > > one of the
> > > major real problems with using tuples in TMMBR. As one=20
> changed TMMBR
> > > from a one-dimensional problem to a two dimensional problem,
> > > the concept
> > > of a single owner of the restriction took a hike. Thus we end
> > > up with a
> > > need to indicate multiple tuples that are the active
> > > restrictions. This
> > > will create extra complexities. There will also be more data
> > > to transmit.
> > >
> > > We are working on this, and haven't yet verified and=20
> simulated it to
> > > understand the full implications. However we do like to share
> > > this with
> > > you to provide you the opportunity to think about the same
> > > problem and
> > > possibly find any issues we have forgotten about. Our current
> > > proposal
> > > for how this would work is the following:
> > >
> > > Lets start assuming that there is a session with a number of
> > > participants. They can all have restriction tuples (bit-rate,
> > > overhead).
> > > So if a media receiver has some change he first checks if the
> > > new values
> > > are an actually restriction compared to the current set of
> > > restrictions
> > > in the session. If that is the case it sends a TMMBR=20
> message to the
> > > media sender. The media sender checks the restriction=20
> compared to its
> > > current set and see if that is an actual restriction=20
> given its sets
> > > (remember the asynchronous behavior in a multi-party=20
> session) and if
> > > that allows it to drop some of the previous restriction=20
> as being less
> > > restrictive then the new one. Then it sends out the TMMBN with the
> > > current set.
> > >
> > > So how does on determine which is the current set of=20
> restrictions. Me
> > > and Bo have been kicking around an algorithm that might
> > > result in this.
> > > However we need to spend some time on verification.
> > >
> > > 1. First sort the set X of restriction tuples according=20
> to bit-rate
> > > creating a vector of tuples, X1 to Xn with the X1=20
> carrying the lowest
> > > bit-rate and Xn the highest value.
> > >
> > > 2. Eleminate all tuples in X with a overhead value=20
> smaller than the
> > > value in X1.
> > >
> > > 3. Repeat step 2 for all elements in X from the lowest to the
> > > next highest.
> > >
> > > 4. A reduced set X has been created.
> > >
> > > The above algorithm eliminates all the tuples that=20
> doesn't provide a
> > > restriction because they allow a higher bit-rate and=20
> their bit-rate
> > > grows slower than the previous one when packet-rate increases.
> > >
> > > A second step would be to eliminate all tuples where they
> > > although have
> > > higher bit-rate, the overhead value is only slightly larger
> > > so that the
> > > first restriction does not allow a packet rate that is=20
> large enough,
> > > even when all the allowed bit-rate is spent on headers.=20
> An example to
> > > illustrate this:
> > >
> > > Lets say that you have a tuple of (35kbps, 40 bytes) and=20
> a second one
> > > that is (45 kbps, 50 bytes).  The maximum packet rate the=20
> first one
> > > allows are 35000 /(40*8) =3D 109.375 packets / s.=20
> Performing the same
> > > calculation for the second tuple yields 45000/(50*8) =3D 112.5
> > > packets/s.
> > > Thus the second tuple does not provide a restriction that is
> > > applicable
> > > given that the first one is included in the set.
> > >
> > > 5. For each tuple in X calculate the largest possible packet-rate
> > > yielding no useful work, i.e. bit-rate / overhead and store
> > > in vector Y.
> > >
> > > 6. For each element in X, index by i, in case Yi+1 is=20
> larger than Yi
> > > remove Yi+1 and Xi+1 from the sets and repeat comparison for i.
> > >
> > > However looking at the above there is evident that one=20
> could do more
> > > here with some additional information. The comparison using
> > > packet rates
> > > that means no useful data is transported is easy to do but doesn't
> > > restrict as well as is possible. There exist two parameters
> > > that could
> > > be introduced into this to provide restrictions that exist in real
> > > usage. However these values needs to be the same and known to all
> > > session participants to be possible to utilize.
> > >
> > > The first one would to explicit declare the maximum=20
> packet rate the
> > > application has any usage of at all for this media. For=20
> example this
> > > could be restricted by codec, or by the codec in=20
> combination with the
> > > session maximum bit-rate. This maximum packet rate value
> > > would allow one
> > > to eliminate from the set of restriction all tuples whose bit-rate
> > > divided by overhead is larger than the session maximum=20
> packet-rate.
> > >
> > > A second possible restriction would to declare a minimum of useful
> > > rtp-payload bit-rate. In many cases the media codec or
> > > application has
> > > knowledge about what the smallest bit-rate that would provide any
> > > utility from the media at all. For example for an audio=20
> session using
> > > the AMR speech codec packetized in RTP (RFC 3267), that
> > > bit-rate would
> > > be 4.75kbps. I ignore the per frame and RTP payload=20
> overhead in this
> > > case, but those could be considered to be included also.=20
> This minimal
> > > overhead could then be subtracted from all the tuples=20
> bit-rate values
> > > prior to running the above presented algorithm. Note that=20
> this second
> > > restriction needs to be applied prior to the first one if
> > > both where to
> > > be present.
> > >
> > > What these restrictions provides are some application sanity
> > > restrictions on what possible combination of useful bit-rate
> > > and maximum
> > > packet rate it can produce and still do some good. However
> > > these would
> > > need to be signaled and could also result in some dispute
> > > during session
> > > establishment if the applications aren't agreeing on a value.
> > >
> > > So the big question to you is: Is solving the inaccuracy=20
> problem that
> > > introducing a tuple solves worth the extra complexities=20
> and overhead?
> > >
> > > Cheers
> > >
> > > Magnus Westerlund
> > >
> > > IETF Transport Area Director & TSVWG Chair
> > >=20
> ----------------------------------------------------------------------
> > > Multimedia Technologies, Ericsson Research EAB/TVA/A
> > >=20
> ----------------------------------------------------------------------
> > > Ericsson AB                | Phone +46 8 4048287
> > > Torshamsgatan 23           | Fax   +46 8 7575550
> > > S-164 80 Stockholm, Sweden | mailto:=20
> magnus.westerlund@ericsson.com
> > >=20
> ----------------------------------------------------------------------
> > >
> > --------------------------------------------------------------------
> >=20
> > CONFIDENTIALITY NOTICE
> >=20
> > This message and its attachments are addressed solely to=20
> the persons above
> > and may contain confidential information. If you have=20
> received the message
> > in error, be informed that any use of the content hereof is=20
> prohibited.
> > Please return it immediately to the sender and delete the=20
> message. Should
> > you have any questions, please contact us by replying to
> > webmaster@telecomitalia.it.
> >=20
> >         Thank you
> >=20
> >                                         www.telecomitalia.it
> >=20
> > --------------------------------------------------------------------
> >=20
> >=20
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www1.ietf.org/mailman/listinfo/avt
>=20
--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons =
above and may contain confidential information. If you have received the =
message in error, be informed that any use of the content hereof is =
prohibited. Please return it immediately to the sender and delete the =
message. Should you have any questions, please contact us by replying to =
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                       =20

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



From avt-bounces@ietf.org Mon Feb 26 04:19:33 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLbzI-0005Sd-D8; Mon, 26 Feb 2007 04:17:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HLbzG-0005MB-FV
	for avt@ietf.org; Mon, 26 Feb 2007 04:17:38 -0500
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLbzE-0001Br-VI
	for avt@ietf.org; Mon, 26 Feb 2007 04:17:38 -0500
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Feb 2007 10:17:30 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: R: [AVT]CCMdraftreview--should"bandwidth"includetheheaderoverhead
Date: Mon, 26 Feb 2007 10:17:27 +0100
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD1033EB231@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <2CA3E1B6CEC064449CAA7D0FAB46079B0297CB18@NAEX01.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: R: [AVT]CCMdraftreview--should"bandwidth"includetheheaderoverhead
Thread-Index: AcdXXNXrEYCAJcHBRvq05phqeSb3rQAMZHsQAH3kHkA=
From: "SOLLAUD Aurelien RD-TECH-LAN" <aurelien.sollaud@orange-ftgroup.com>
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>,
	"Randell Jesup" <rjesup@wgate.com>
X-OriginalArrivalTime: 26 Feb 2007 09:17:30.0633 (UTC)
	FILETIME=[F0F38790:01C75986]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi=20

> -----Message d'origine-----
> De : Desineni, Harikishan [mailto:hdesinen@qualcomm.com]=20
> Envoy=E9 : vendredi 23 f=E9vrier 2007 22:35
> =C0 : Randell Jesup; SOLLAUD Aurelien RD-TECH-LAN
> Cc : avt@ietf.org
> Objet : RE: R:=20
> [AVT]CCMdraftreview--should"bandwidth"includetheheaderoverhead
> > -----Original Message-----
> > From: Randell Jesup [mailto:rjesup@wgate.com]
> > Sent: Friday, February 23, 2007 6:52 AM
> > To: SOLLAUD Aurelien RD-TECH-LAN
> > Cc: avt@ietf.org
> > Subject: Re: R: [AVT]CCMdraftreview--
> > should"bandwidth"includetheheaderoverhead
> >=20
> > "SOLLAUD Aurelien RD-TECH-LAN" <aurelien.sollaud@orange-ftgroup.com>
> > writes:
> > >> The main discussion in this thread is around the TMMBR feedback=20
> > >> message (or whatever it will be re-named).
> > >>
> > >> Initially, two proposals were made for TMMBR: to signal=20
> the codec=20
> > >> bitrate, or the IP gross bitrate.
> > >> IMO, both solutions are more or less inaccurate,=20
> depending on the=20
> > >> protocol stack running in the bottleneck.
> > >
> > >Anyway, I would find useful to have a standard feedback message to=20
> > >signal a desired codec bitrate back to the media sender. It would
> avoid
> > >a per codec definition like the codec mode requests embedded in the
> RTP
> > >payload header we have in RFC 3267 (AMR), RFC 3558 (SMV, EVRC), RFC
> 4348
> > >(VMR-WB), RFC 4749 (G.729.1), ...
> > >
> > >I initially thought it was the goal of TMMBR. But the current
> discussion
> > >shows that it is likely to be something else.
> >=20
>=20
> The discussion exists because some people think it is=20
> something else than what you understood. The authors did not=20
> specify which definition was meant out of the two options and=20
> the discussion is to clarify that.
>=20
> > Correct; TMMBR was not designed as a=20
> codec-bitrate-switch-request tool=20
> > (witness the name).
>=20
> The name is misleading if it is not meant for just codec control.
> If TMMBR was not designed as codec-bitrate-switch-request=20
> then the name of the draft is misleading ""Codec Control=20
> Messages in the RTP Audio-Visual Profile with Feedback (AVPF)"
>=20
> If TMMBR is not pure codec-bitrate-switch-request tool, why=20
> is it present in a draft with title "Codec Control Messages=20
> in the RTP Audio-Visual Profile with Feedback (AVPF)"? This=20
> is what really puzzles me. I've posted this question many=20
> times and it never got answered.

Yes, I have the same question.
If TMMBR deals with network layers, it is network congestion control, =
not Codec Control Message. And this kind of TMMBR does not address the =
"Codec Mode Request" thing we (unfortunately) find in the RTP payload =
formats I listed above.


> >  It could result in a sender deciding to switch bitrates in a=20
> > multi-bitrate codec, but counting on specific values to
> mean
> > specific things (like "switch from 16Kbps mode to 8Kbps mode" by=20
> > indicating 8000 bps) is dangerous with TMMBR.  For example,=20
> a midbox=20
> > might modify
> a
> > TMMBR request by subtracting some amount for overhead it=20
> knows about,=20
> > causing your 8000 to become 7500.
>=20
> Middle box in the media path can be either RTP mixer or RTP=20
> translator RTP mixer is an RTP end point and RTP translator is not.
>=20
> If it is a pure codec control RTCP message then the RTP middle box
> (mixer/translator) must not modify it unless there is codec=20
> media transcoding or thinning taking place in the RTP media path.
>=20
> >=20
> > >Most modern audio codecs will be multi-bitrate, it is desirable to
> have
> > >a standard RTCP message to signal codec bitrate change requests,
> instead
> > >of incorrectly using the RTP media path to perform this.=20
> And it would
> be
> > >interesting no to reduce it to AVPF profile.
> >=20
> > I'm not sure I understand "interesting no to reduce it to AVPF
> profile".
> > I think it may make sense to consider a draft for something=20
> other than=20
> > TMMBR to provide the ability to request/suggest (pure) codec rate
> shifts,
> > for reasons other than restriction.=20
>=20
> RTCP message related to codec rate shifts should be in CCM=20
> and the message which is not purely codec rate should NOT be=20
> in CCM. If TMMBR is pure codec bitrate then it should stay=20
> (with an appropriate name - MCBR
> MaxCodecBitRate) in CCM draft. If TMMBR includes header=20
> overhead then it is not a pure codec command and has to go=20
> into a new draft.
>=20
> SOLLAUD's point was that a true/generic codec rate switch=20
> message is useful for all RTP profiles and not just AVPF=20
> (based on the codecs listed by him that currently use codec=20
> commands in RTP payload field).=20

Exactly.
=20
>=20
> > The two items don't work well
> > together
> > in one model (as evidenced by the discussions/disagreements=20
> here over
> TIAS
> > vs AS vs tuples), but may work well when separated into two=20
> mechanisms=20
> > with different goals and uses.
> >=20
> > --
> > Randell Jesup, Worldgate (developers of the Ojo=20
> videophone), ex-Amiga
> OS
> > team
> > rjesup@wgate.com
> > "The fetters imposed on liberty at home have ever been forged out of
> the
> > weapons
> > provided for defence against real, pretended, or imaginary dangers
> from
> > abroad."
> > 		- James Madison, 4th US president (1751-1836)
> >=20
> >=20
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www1.ietf.org/mailman/listinfo/avt
>=20

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



From avt-bounces@ietf.org Mon Feb 26 04:54:01 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLcXb-0007C9-JS; Mon, 26 Feb 2007 04:53:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HLcQW-0001K3-LO
	for avt@ietf.org; Mon, 26 Feb 2007 04:45:48 -0500
Received: from ik-out-1112.google.com ([66.249.90.178])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLcQV-0004wJ-4q
	for avt@ietf.org; Mon, 26 Feb 2007 04:45:48 -0500
Received: by ik-out-1112.google.com with SMTP id c21so312856ika
	for <avt@ietf.org>; Mon, 26 Feb 2007 01:45:44 -0800 (PST)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type;
	b=Ke32P0EU+0XQMS7kZIEJfIMiwS3SJbfr5zKFvs0QUAOEuC79WEztu/jbd2/Sj2YtNxfwVx/zOoXVgR4nVySLf+oPp8oycLoLkqdnY58zGSEZ+p7s8pmR8XkX8lSGRFtqm/m+cxVPncI5l/XxvUms2n2JFtpJB2MINYkqWiFt36I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:mime-version:content-type;
	b=uBiLe27KBxA2T1Mt30OnW+xV2hQ3t5i7jy3W8L8rTkB/qnjBACUcRP283hT49HllFUIiNx89W3Z2e/pm2bMsMd/hhf2LUmM8RRxHXiBJIh9I+qaZkGydU2aZO/nRiEenWuWh9WBoCaa8oL0LBhX+mfg6Oxg3/j2yVxqIrcSi4NU=
Received: by 10.114.12.9 with SMTP id 9mr2030418wal.1172483141806;
	Mon, 26 Feb 2007 01:45:41 -0800 (PST)
Received: by 10.114.180.13 with HTTP; Mon, 26 Feb 2007 01:45:41 -0800 (PST)
Message-ID: <bd8277fd0702260145kb443b71ub2fcb3f83783f42d@mail.gmail.com>
Date: Mon, 26 Feb 2007 11:45:41 +0200
From: "Roni Even" <even.roni@gmail.com>
To: avt@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
X-Mailman-Approved-At: Mon, 26 Feb 2007 04:53:06 -0500
Cc: csp@csperkins.org, taylor@nortel.com
Subject: [AVT] AVT WG agenda time in Prague - reminder
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0622788866=="
Errors-To: avt-bounces@ietf.org

--===============0622788866==
Content-Type: multipart/alternative; 
	boundary="----=_Part_2449_5310842.1172483141766"

------=_Part_2449_5310842.1172483141766
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,



If you wish to have agenda time at the upcoming meeting in Prague, please
send an agenda request to the chairs, but no later than March 1st.



We have requested two time slots:

1. Monday March 19th 13:00-15:00

2. Wednesday March 21st 15:10-16:10



Please note that those times are not final and may change. The final agenda
for the meeting will; be published on February 26th.







This meeting time is intended for the following:



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

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

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

- Discussion of important AVT relevant work in other WGs



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



A. Presentation Title:



B. Name of presenter:



C. Draft Reference(s):



D. Requested amount of time in minutes:









Thanks

Roni Even

------=_Part_2449_5310842.1172483141766
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div class="Section1">
<div class="Section1">
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">Hi,</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">&nbsp;</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">If you wish to have agenda time at the upcoming meeting in Prague, please send an agenda request to the chairs, but no later than March 1st.
</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">&nbsp;</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">We have requested two time slots:</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">1. Monday March 19th 13:00-15:00</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">2. Wednesday March 21st 15:10-16:10 </span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">&nbsp;</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">Please note that those times are not final and may change. The final agenda for the meeting will; be published on February 26th.
</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">&nbsp;</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">&nbsp;</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">&nbsp;</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">This meeting time is intended for the following:</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">&nbsp;</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">- Discussion of important drafts fundamental for the complete RTP framework.</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">- Discussion of issues that hasn&#39;t been possible to resolve on the mailing list.</span></font></p>

<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">- Discussion of new work that falls outside of our current charter.</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">- Discussion of important AVT relevant work in other WGs</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">&nbsp;</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">So if you want time for discussing your issues in AVT. Then you are required to request time. These request shall contain the below information. 
</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">&nbsp;</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">A. Presentation Title:</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">&nbsp;</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">B. Name of presenter:</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">&nbsp;</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">C. Draft Reference(s):</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">&nbsp;</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">D. Requested amount of time in minutes:</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">&nbsp;</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">&nbsp;</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">&nbsp;</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">&nbsp;</span></font></p>
<p class="MsoNormal"><font face="Courier New" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: &#39;Courier New&#39;">Thanks</span></font></p>
<p class="MsoNormal"><font face="Arial" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Roni Even</span></font></p></div></div>

------=_Part_2449_5310842.1172483141766--


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

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

--===============0622788866==--




From avt-bounces@ietf.org Mon Feb 26 05:19:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLcvt-0000Gt-Vu; Mon, 26 Feb 2007 05:18:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HLcvs-0000CQ-4u
	for avt@ietf.org; Mon, 26 Feb 2007 05:18:12 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLcvl-0002I9-BE
	for avt@ietf.org; Mon, 26 Feb 2007 05:18:12 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	AE3B62014F; Mon, 26 Feb 2007 11:17:58 +0100 (CET)
X-AuditID: c1b4fb3e-af6d2bb0000007e1-e3-45e2b3d61ce8 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	9911320FE3; Mon, 26 Feb 2007 11:17:58 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Feb 2007 11:17:58 +0100
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Feb 2007 11:17:58 +0100
Message-ID: <45E2B3D5.5060403@ericsson.com>
Date: Mon, 26 Feb 2007 11:17:57 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Franceschini Guido <guido.franceschini@telecomitalia.it>
Subject: Re: Issues with using tuples in TMMBR was:Re: R: [AVT] CCM draft
	review --	should"bandwidth"includetheheaderoverhead
References: <E9D1028EC5C22B418B5D54CA6EA27C579A5EBF@PTPEVS108BA020.idc.cww.telecomitalia.it>
In-Reply-To: <E9D1028EC5C22B418B5D54CA6EA27C579A5EBF@PTPEVS108BA020.idc.cww.telecomitalia.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Feb 2007 10:17:58.0434 (UTC)
	FILETIME=[634A0820:01C7598F]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Franceschini Guido skrev:
> Magnus,
> 
> let me first check if I have understood your scenario. Then I'll give my view on your mail: just disregard it if I missed to understand the scenario in the first place.
> 
> 
> Scanario: a sender S and multiple receivers R1, R2 ... RN
> 
> The sender is notified of a number of bottlneck tuples B1, B2 ... BN, each expressed for a potentially different stack.
> Based on some internal logic, the sender decides how to encode and packetize its traffic, and also acknowledges with TMMBN to let each receiver aware of the currently valid limits.
> 
> If the above is correct, then let's go on.

Yes.

> 
> There is a set of challenges in this scenario:
> 
> 1) identification of the most restrictive bottleneck among the B1 ... BN 
> 2) generation of the TMMBN to let receiver know about the current restriction
> 3) reduction of useless TMMBR traffic
> 4) accuracy of the Bx data
> 
> Concerning 1) identification of the most restrictive bottleneck among the B1 ... BN
> 
> The usage of a tuple instead of a single value allows for a more accurate description, but it is easy to derive from an accurate description a less accurate one ;-)
> More specifically, if you indicated in the TMMBR the IP gross bitrate, or the media bitrate, you were actually impling some packetrate (actually, the generator of the TMMBR implied a maxpacketrate). You can now apply as well a maxpacketrate, with the advantage that you are now the sender, and can therefore apply a more close-to-reality maxpacketrate.
> Suppose you apply a maxpacketrate of 50; you would obtain from:
> (35 kbps, 40 bytes) ==> 35000-(40*50*8)=19000
> (45 kbps, 50 bytes) ==> 45000-(50*50*8)=25000
> 
> Thus, you go back to the same complexity that you have to deal with anyway, with just a better accuracy (the sender applied a uniform and credible maxpacketrate, instead of having each receiver applying his own guess). Also, the sender knows that it must not exceed 50 pkt/sec.

For a sender to determine which tuple is the currently most restrictive 
one is not a problem. The issue arise if the sender likes to change for 
example the packetization and the packet rate. Without any differences 
in how the receiver would be affected by this, there was no need update 
your TMMBR value as result of a sender change. However with a change of 
packet rate you can actually end up with different tuples being the 
restriction. The maximum packet rate only helps reduce the number of 
possible tuples as it cuts of the outer extremes.

> 
> 
> Concerning 2) generation of the TMMBN to let receiver know about the current restriction
> 
> Here the goal is to let each receiver aware of the current limits, so that it will generate new TMMBR only if they have an impact on the sender.
> It is definitely undesirable that the sender generates a TMMBN listing all tuples that it is currently taking into account.
> But if the TMMBN contains a different tuple, made of:
> <media bitrate, maxpacketrate>
> then each receiver is again able to determine whether it should send a TMMBR or not.
> Let's use the figures above:
> 
> at time t0:
> - receiver R1 sends TMMBR(35 kbps, 40 bytes)
> - receiver R2 sends TMMBR(35 kbps, 40 bytes)
> ==> sender sends TMMBN(19000, 50 pkt/sec, R1)
> 
> at time t1:
> - R2 changes from (45 kbps, 50 bytes) to (40 kbps, 50 bytes)
> ==> R2 computes that 19000 + (50*50*8) = 39000, thus does not send TMMBR
> 
> at time t2:
> - R2 changes to (38 kbps, 50 bytes)
> ==> R2 sends TMMBR
> - Sender computes (38 kbps, 50 bytes) ==> 38000-(50*50*8)=18000
> ==> sender sends TMMBN(18000, 50 pkt/sec, R2)
> 

I think there might be benefits from including a maximum packet rate 
also in the TMMBN. But I need to think a bit more about this. However 
including the max_prate in SDP does to me still seem to be a good 
solution. Otherwise in highly dynamic multi-party session the new 
participants may end up creating unnecessary request traffic due to it 
not knowing any restriction on the maximum packet rate.

> 
> Concerning 3) reduction of useless TMMBR traffic
> 
> The above algorithm shows how the usage of tuples instead of single values can be managed with the same efficiency
> 
> 

I am not agreeing that one always can restrict oneself to a single 
value. As stated before, if one does that any change in the actual 
packet rate would result in that one moves from one tuple to another if 
they are giving certain values. The only way the TMMBR mechanism could 
work in this case is for a TMMBN to be sent with a new max packet rate 
every time one makes changes to the packetization and how often it 
produces packet. This also ends up being complicated when one has 
content that changes its packet rate continuously. Allowing for multiple 
restriction tuples to be valid at the same time do ensure that senders 
can take those effects into account also.

> Concerning 4) accuracy of the Bx data
> 
> The usage of tuples instead of single values allows, even in such p2mp scenario, to compute more accurate limits.
> 

Agreed. I do think that the usage of tuples will help solve an real 
problem. However I do need to raise a discussion if the added complexity 
is worth it to solve the problem. I think it is.

> 
> To conclude: IMHO the usage of tuples have no CONS with respect to picking up a single value, while providing benefits instead.

Well, here I do disagree. There are CONS.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



From avt-bounces@ietf.org Mon Feb 26 05:32:40 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLd8e-0004tv-48; Mon, 26 Feb 2007 05:31:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HLd8d-0004tp-7W
	for avt@ietf.org; Mon, 26 Feb 2007 05:31:23 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLd8V-0003Vy-KA
	for avt@ietf.org; Mon, 26 Feb 2007 05:31:23 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	6EB1E20469; Mon, 26 Feb 2007 11:31:01 +0100 (CET)
X-AuditID: c1b4fb3c-ae7c5bb0000007de-c7-45e2b6e50a4c 
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	536F0206F9; Mon, 26 Feb 2007 11:31:01 +0100 (CET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Feb 2007 11:31:01 +0100
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Feb 2007 11:31:00 +0100
Message-ID: <45E2B6E4.3060301@ericsson.com>
Date: Mon, 26 Feb 2007 11:31:00 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: SOLLAUD Aurelien RD-TECH-LAN <aurelien.sollaud@orange-ftgroup.com>
Subject: Separation of Transport layer and Payload specific messages in CCM;
	was Re: R:
	[AVT]CCMdraftreview--should"bandwidth"includetheheaderoverhead
References: <DD8B8FEBBFAF9E488F63FF0F1A69EDD1033EB231@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <DD8B8FEBBFAF9E488F63FF0F1A69EDD1033EB231@ftrdmel1.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Feb 2007 10:31:00.0813 (UTC)
	FILETIME=[359F97D0:01C75991]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: Randell Jesup <rjesup@wgate.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

SOLLAUD Aurelien RD-TECH-LAN skrev:
>>
>> If TMMBR is not pure codec-bitrate-switch-request tool, why 
>> is it present in a draft with title "Codec Control Messages 
>> in the RTP Audio-Visual Profile with Feedback (AVPF)"? This 
>> is what really puzzles me. I've posted this question many 
>> times and it never got answered.
> 
> Yes, I have the same question.
> If TMMBR deals with network layers, it is network congestion control, not Codec Control Message. And this kind of TMMBR does not address the "Codec Mode Request" thing we (unfortunately) find in the RTP payload formats I listed above.
> 

I agree that TMMBR is not directly a "CODEC" control message. However it 
is also not a purely transport related thing dealing with congestion 
control. The main motivation for TMMBR is to deal with RTP layer 
transport issues related RTP topologies including mixers and 
translators. If you don't understand this from the motivation text for 
TMMBR present in the CMM draft. Can you please explain what is lacking.

If you look at AVPF you can see that it does make the distinction 
between Transport Layer feedback and Payload Specific Feedback messages. 
The FIR and TSTR are clearly payload specific in the way that they only 
apply to certain codecs. TMMBR is transport related because it isn't 
restricted to any specific codec.

It was not split out into a separate draft because the issue TMMBR deals 
with are closely related to the one dealing with video. It has been part 
of the discussion. It is true that splitting it out to a separate draft 
would make this separation of different types of feedback messages 
clearer. However I don't the gain in clarity from this is worth the 
effort it will place on us authors.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



From avt-bounces@ietf.org Mon Feb 26 05:41:01 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLdHF-0001OE-L9; Mon, 26 Feb 2007 05:40:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HLdHD-0001O5-EY
	for avt@ietf.org; Mon, 26 Feb 2007 05:40:15 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLdHA-0004ow-W9
	for avt@ietf.org; Mon, 26 Feb 2007 05:40:15 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	7586A20786; Mon, 26 Feb 2007 11:40:10 +0100 (CET)
X-AuditID: c1b4fb3c-ae7c5bb0000007de-86-45e2b90a2e82 
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	60C5F20501; Mon, 26 Feb 2007 11:40:10 +0100 (CET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Feb 2007 11:40:10 +0100
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Feb 2007 11:40:09 +0100
Message-ID: <45E2B909.5060406@ericsson.com>
Date: Mon, 26 Feb 2007 11:40:09 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: "Allison, Art" <AAllison@nab.org>
Subject: LIP synch and TMMBR; was Re: R:
	[AVT]	CCMdraftreview--	should"bandwidth"includetheheaderoverhead
References: <33CB4DEADE8C734CAF59FA0B47E14C17031F32B8@morse.NAB.ORG>
In-Reply-To: <33CB4DEADE8C734CAF59FA0B47E14C17031F32B8@morse.NAB.ORG>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Feb 2007 10:40:09.0762 (UTC)
	FILETIME=[7CD29020:01C75992]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Allison, Art skrev:
> How to control lip-sync or lack thereof is clearly out of scope here.
> 
> However, I respectively disagree with the AD that it is out of scope as
> a factor in the decision between selection of a total bit rate control
> vs. a partial bit rate control.  

Can you please clarify what you mean with total vs partial bit-rate control.

> 
> It is only one factor, but declaring it out of scope as a consideration
> can be expected to impact the technical choice.  
> 
> I request reconsideration and clarification, as surly the AD did not
> intend to force the group to ignore a technical factor that is material
> to the RFC content.
> 

To be clear, in AVT I am only another technical contributor. Cullen 
Jennings is the responsible AD for this WG. I am not trying to force 
something out. However I have so far failed to see how the issue you are 
discussing do affect TMMBR. Looking at the fundamental synchronization 
model RTP has, TMMBRs impact on lip-synch is purely implementation 
specific. Sure there are things that in the implementation that controls 
what is actually sent that could affect when packets get sent in such a 
way that it has some impact on the lip-synch. Are there any special part 
of the problem that you would like to have note about to help improve 
implementations?

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



From avt-bounces@ietf.org Mon Feb 26 05:52:04 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLdRu-0000tP-RN; Mon, 26 Feb 2007 05:51:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HLdRt-0000ot-V5
	for avt@ietf.org; Mon, 26 Feb 2007 05:51:17 -0500
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLdRr-0006RY-F3
	for avt@ietf.org; Mon, 26 Feb 2007 05:51:17 -0500
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Feb 2007 11:50:41 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Separation of Transport layer and Payload specific messages in
	CCM; was Re: R:
	[AVT]CCMdraftreview--should"bandwidth"includetheheaderoverhead
Date: Mon, 26 Feb 2007 11:50:59 +0100
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD1033EB354@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <45E2B6E4.3060301@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Separation of Transport layer and Payload specific messages in
	CCM; was Re: R:
	[AVT]CCMdraftreview--should"bandwidth"includetheheaderoverhead
Thread-Index: AcdZkTxjTfKRCLM2QXKNG98S73ivuAAAaHCQ
From: "SOLLAUD Aurelien RD-TECH-LAN" <aurelien.sollaud@orange-ftgroup.com>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-OriginalArrivalTime: 26 Feb 2007 10:50:41.0663 (UTC)
	FILETIME=[F57700F0:01C75993]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: Randell Jesup <rjesup@wgate.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

> De : Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]=20
> >>
> >> If TMMBR is not pure codec-bitrate-switch-request tool, why is it=20
> >> present in a draft with title "Codec Control Messages in the RTP=20
> >> Audio-Visual Profile with Feedback (AVPF)"? This is what really=20
> >> puzzles me. I've posted this question many times and it never got=20
> >> answered.
> >=20
> > Yes, I have the same question.
> > If TMMBR deals with network layers, it is network=20
> congestion control, not Codec Control Message. And this kind=20
> of TMMBR does not address the "Codec Mode Request" thing we=20
> (unfortunately) find in the RTP payload formats I listed above.
> >=20
>=20
> I agree that TMMBR is not directly a "CODEC" control message.=20
> However it is also not a purely transport related thing=20
> dealing with congestion control. The main motivation for=20
> TMMBR is to deal with RTP layer transport issues related RTP=20
> topologies including mixers and translators. If you don't=20
> understand this from the motivation text for TMMBR present in=20
> the CMM draft. Can you please explain what is lacking.
>=20
> If you look at AVPF you can see that it does make the=20
> distinction between Transport Layer feedback and Payload=20
> Specific Feedback messages.=20
> The FIR and TSTR are clearly payload specific in the way that=20
> they only apply to certain codecs. TMMBR is transport related=20
> because it isn't restricted to any specific codec.
>=20
> It was not split out into a separate draft because the issue=20
> TMMBR deals with are closely related to the one dealing with=20
> video. It has been part of the discussion. It is true that=20
> splitting it out to a separate draft would make this=20
> separation of different types of feedback messages clearer.=20
> However I don't the gain in clarity from this is worth the=20
> effort it will place on us authors.
>=20

I'm OK with that. The motivations for TMMBR are clear.

The conclusion could be that there is a need for another kind of CCM, to
perform codec bitrate requests in RTCP, in a profile-independant, and
codec-independant way. It means a new draft for this, not for the
current TMMBR.

Regards,
Aurelien

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



From avt-bounces@ietf.org Mon Feb 26 06:02:04 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLdb7-0007x4-2v; Mon, 26 Feb 2007 06:00:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HLdb4-0007ww-VT
	for avt@ietf.org; Mon, 26 Feb 2007 06:00:46 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLdb3-0007hp-LG
	for avt@ietf.org; Mon, 26 Feb 2007 06:00:46 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	0A7F32109C; Mon, 26 Feb 2007 12:00:43 +0100 (CET)
X-AuditID: c1b4fb3e-af6d2bb0000007e1-bc-45e2bdda79ec 
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	DE57420244; Mon, 26 Feb 2007 12:00:42 +0100 (CET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Feb 2007 12:00:43 +0100
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Feb 2007 12:00:42 +0100
Message-ID: <45E2BDDA.20601@ericsson.com>
Date: Mon, 26 Feb 2007 12:00:42 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: SOLLAUD Aurelien RD-TECH-LAN <aurelien.sollaud@orange-ftgroup.com>
Subject: Re: Separation of Transport layer and Payload specific messages in
	CCM; was Re: R:
	[AVT]CCMdraftreview--should"bandwidth"includetheheaderoverhead
References: <DD8B8FEBBFAF9E488F63FF0F1A69EDD1033EB354@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <DD8B8FEBBFAF9E488F63FF0F1A69EDD1033EB354@ftrdmel1.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Feb 2007 11:00:42.0489 (UTC)
	FILETIME=[5B95C690:01C75995]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: Randell Jesup <rjesup@wgate.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

SOLLAUD Aurelien RD-TECH-LAN skrev:
> 
> The conclusion could be that there is a need for another kind of CCM, to
> perform codec bitrate requests in RTCP, in a profile-independant, and
> codec-independant way. It means a new draft for this, not for the
> current TMMBR.
> 

Yes, if one thinks that there are cases where AMR Codec-mode-request 
like behavior is needed in a more generic fashion then that is a 
separate type of message. It is a different problem than from TMMBR and 
for different reasons. I currently don't have any real opinion how good 
or bad such a thing would be.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



From avt-bounces@ietf.org Mon Feb 26 07:34:09 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLf2Y-00088t-S4; Mon, 26 Feb 2007 07:33:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HLf2X-00088n-3f
	for avt@ietf.org; Mon, 26 Feb 2007 07:33:13 -0500
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLf2U-0002ma-NU
	for avt@ietf.org; Mon, 26 Feb 2007 07:33:13 -0500
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 25 Feb 2007 17:56:31 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C0457BFB1@IsrExch01.israel.polycom.com>
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AVT WG agenda time in Prague - reminder
Thread-Index: AcdY9YQzPx62HBi7Q0WDNk3etaV8Og==
From: "Even, Roni" <roni.even@polycom.co.il>
To: <avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e654cfa5e44bd623be3eb2c720858b05
Cc: Colin Perkins <csp@csperkins.org>, Tom-PT Taylor <taylor@nortel.com>
Subject: [AVT] AVT WG agenda time in Prague - reminder
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0584386773=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0584386773==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C758F5.858A02D2"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C758F5.858A02D2
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

=20

If you wish to have agenda time at the upcoming meeting in Prague,
please send an agenda request to the chairs, but no later than March
1st.

=20

We have requested two time slots:

1. Monday March 19th 13:00-15:00

2. Wednesday March 21st 15:10-16:10=20

=20

Please note that those times are not final and may change. The final
agenda for the meeting will; be published on February 26th.

=20

=20

=20

This meeting time is intended for the following:

=20

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

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

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

- Discussion of important AVT relevant work in other WGs

=20

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

=20

A. Presentation Title:

=20

B. Name of presenter:

=20

C. Draft Reference(s):

=20

D. Requested amount of time in minutes:

=20

=20

=20

=20

Thanks

Roni Even


------_=_NextPart_001_01C758F5.858A02D2
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:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
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 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Hi,<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>If you wish to have =
agenda
time at the upcoming meeting in <st1:City w:st=3D"on"><st1:place =
w:st=3D"on">Prague</st1:place></st1:City>,
please send an agenda request to the chairs, but no later than March =
1st.<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>We have requested =
two time
slots:<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>1. Monday March =
19th
13:00-15:00<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>2. Wednesday March =
21st
15:10-16:10 <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>Please note that =
those times
are not final and may change. The final agenda for the meeting will; be
published on February 26th.<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>This meeting time =
is
intended for the following:<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

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

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

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

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

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

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

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>A. Presentation =
Title:<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>B. Name of =
presenter:<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

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

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

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

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Thanks<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Roni Even<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C758F5.858A02D2--


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

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

--===============0584386773==--




From avt-bounces@ietf.org Mon Feb 26 10:12:48 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLhVo-00069i-Tw; Mon, 26 Feb 2007 10:11:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLhVo-00068a-9R; Mon, 26 Feb 2007 10:11:36 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HLhVm-0006Az-VA; Mon, 26 Feb 2007 10:11:36 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	80CD020880; Mon, 26 Feb 2007 16:10:25 +0100 (CET)
X-AuditID: c1b4fb3c-ae7c5bb0000007de-ba-45e2f861f8fd 
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	70F6220549; Mon, 26 Feb 2007 16:10:25 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Feb 2007 16:10:25 +0100
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Feb 2007 16:10:24 +0100
Message-ID: <45E2F860.1000407@ericsson.com>
Date: Mon, 26 Feb 2007 16:10:24 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <45D0D77F.8030705@ericsson.com> <45D21CC4.10909@ericsson.com>
In-Reply-To: <45D21CC4.10909@ericsson.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Feb 2007 15:10:24.0898 (UTC)
	FILETIME=[3DCBF620:01C759B8]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: behave@ietf.org, IETF AVT WG <avt@ietf.org>
Subject: [AVT] Re: [BEHAVE] [Fwd: Last Call:
 draft-wing-behave-symmetric-rtprtcp
 (Common Local Transmit and Receive Ports (Symmetric RTP)) to Informational
 RFC]
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Magnus Westerlund skrev:
> There has been raised a comment that this document should contain a 
> normative recommendation on using symmetric ports. However to make this 
> happen the document would need to be a BCP. I am willing to consider 
> this but would like to have AVT and Behave WG participant's view on 
> doing this before progressing down that road and updating the IETF last 
> call. So please provide comments by Tuesday 20th of Feb on this issue.
> 

There has been no objections against making this into a BCP.

Dan can you please update your draft with the proposed requirement text.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



From avt-bounces@ietf.org Mon Feb 26 14:25:59 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLlSw-0002MJ-3n; Mon, 26 Feb 2007 14:24:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLlSu-0002M8-9i; Mon, 26 Feb 2007 14:24:52 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HLlSo-0000iF-LJ; Mon, 26 Feb 2007 14:24:52 -0500
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-6.cisco.com with ESMTP; 26 Feb 2007 11:24:46 -0800
X-IronPort-AV: i="4.14,221,1170662400"; 
	d="scan'208"; a="116265847:sNHT50773662"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id l1QJOjBK013457; 
	Mon, 26 Feb 2007 11:24:45 -0800
Received: from dwingwxp ([128.107.114.231])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l1QJOjnF011388;
	Mon, 26 Feb 2007 11:24:45 -0800 (PST)
From: "Dan Wing" <dwing@cisco.com>
To: "'Magnus Westerlund'" <magnus.westerlund@ericsson.com>
Date: Mon, 26 Feb 2007 11:24:45 -0800
Message-ID: <00bb01c759db$c5e81660$e7726b80@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AcdZuIX6vyomh2jUQFuV62AG9Ty1ugAItgLw
In-Reply-To: <45E2F860.1000407@ericsson.com>
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2032; t=1172517885;
	x=1173381885; c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20[Fwd=3A=20Last=20Call=3A=20draft-wing-beha
	ve-symmetric-rtprtcp(Common=20Local=20Transmit=20and=20Receive=20Ports=20(
	Symmetric=20RTP))=20toInformational=20RFC] |Sender:=20;
	bh=Hwkz3VnXINXMi7U/FRCUorB8BXK2BF2gNqo0Zjsc+RU=;
	b=VBvZ+9L2KW4MmfAwFGk+VLpjHRxqJ554gEBRz/AypH6/gcwqtW8w4IFDFbFny3N3zDE5Cy/I
	PGK8whNtgoObGrn+H3FQTXuuSgN5kAvDWg/Lk4sFROPzX5fdhBu+q0eZ;
Authentication-Results: sj-dkim-7; header.From=dwing@cisco.com; dkim=pass (s
	ig from cisco.com/sjdkim7002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: behave@ietf.org, 'IETF AVT WG' <avt@ietf.org>
Subject: [AVT] RE: [BEHAVE] [Fwd: Last Call:
	draft-wing-behave-symmetric-rtprtcp(Common Local Transmit and
	Receive Ports (Symmetric RTP)) toInformational RFC]
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Submitted.  

In the meantime, it is available here:
http://svn.resiprocate.org/rep/ietf-drafts/dwing/draft-wing-behave-symmetric
-rtprtcp-02.html
http://svn.resiprocate.org/rep/ietf-drafts/dwing/draft-wing-behave-symmetric
-rtprtcp-02.txt

Rfcdiff between -02 and -01 is:
http://tinyurl.com/33a3d8

-d

> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com] 
> Sent: Monday, February 26, 2007 7:10 AM
> To: Magnus Westerlund
> Cc: behave@ietf.org; IETF AVT WG
> Subject: Re: [BEHAVE] [Fwd: Last Call: 
> draft-wing-behave-symmetric-rtprtcp(Common Local Transmit and 
> Receive Ports (Symmetric RTP)) toInformational RFC]
> 
> Magnus Westerlund skrev:
> > There has been raised a comment that this document should contain a 
> > normative recommendation on using symmetric ports. However 
> to make this 
> > happen the document would need to be a BCP. I am willing to 
> consider 
> > this but would like to have AVT and Behave WG participant's view on 
> > doing this before progressing down that road and updating 
> the IETF last 
> > call. So please provide comments by Tuesday 20th of Feb on 
> this issue.
> > 
> 
> There has been no objections against making this into a BCP.
> 
> Dan can you please update your draft with the proposed 
> requirement text.
> 
> Cheers
> 
> Magnus Westerlund
> 
> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www1.ietf.org/mailman/listinfo/behave

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



From avt-bounces@ietf.org Mon Feb 26 15:51:23 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLmnj-00046q-4W; Mon, 26 Feb 2007 15:50:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLmnY-0003vO-ND; Mon, 26 Feb 2007 15:50:16 -0500
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HLmnK-0005ts-S4; Mon, 26 Feb 2007 15:50:16 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id CC9FE3297F;
	Mon, 26 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HLmnK-0004z6-Mm; Mon, 26 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HLmnK-0004z6-Mm@stiedprstage1.ietf.org>
Date: Mon, 26 Feb 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-smpte-rtp-10.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: Associating Time-codes with RTP streams
	Author(s)	: D. Singer
	Filename	: draft-ietf-avt-smpte-rtp-10.txt
	Pages		: 21
	Date		: 2007-2-26
	
This document describes a mechanism for associating time-codes, as
   defined by the Society of Motion Picture and Television Engineers
   (SMPTE), with media streams, in a way that is independent of the RTP
   payload format of the media stream itself.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-avt-smpte-rtp-10.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-avt-smpte-rtp-10.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-smpte-rtp-10.txt

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

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


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org Mon Feb 26 15:53:08 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLmpi-0000cs-10; Mon, 26 Feb 2007 15:52:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLmno-0004BA-BC; Mon, 26 Feb 2007 15:50:32 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HLmnc-00060B-1M; Mon, 26 Feb 2007 15:50:32 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 4509926EEB;
	Mon, 26 Feb 2007 20:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HLmnK-0004z3-M4; Mon, 26 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HLmnK-0004z3-M4@stiedprstage1.ietf.org>
Date: Mon, 26 Feb 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-hdrext-11.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: A general mechanism for RTP Header Extensions
	Author(s)	: H. Desineni, D. Singer
	Filename	: draft-ietf-avt-rtp-hdrext-11.txt
	Pages		: 21
	Date		: 2007-2-26
	
This document provides a general mechanism to use the header-
   extension feature of RTP (the Real Time Transport Protocol).  It
   provides the option to use a small number of small extensions in each
   RTP packet, where the universe of possible extensions is large and
   registration is de-centralized.  The actual extensions in use in a
   session are signaled in the setup information for that session.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-avt-rtp-hdrext-11.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-avt-rtp-hdrext-11.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-hdrext-11.txt

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

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


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org Mon Feb 26 17:36:33 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLoRM-0003oq-Gh; Mon, 26 Feb 2007 17:35:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HLoQh-0003DZ-0D
	for avt@ietf.org; Mon, 26 Feb 2007 17:34:47 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLoQf-0003S4-Fd
	for avt@ietf.org; Mon, 26 Feb 2007 17:34:46 -0500
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l1QMYd2v032341
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 26 Feb 2007 14:34:40 -0800
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com
	[172.30.32.65])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l1QMYcP5013237; Mon, 26 Feb 2007 14:34:38 -0800
Received: from NAEX01.qualcomm.com ([129.46.51.60]) by
	SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Feb 2007 14:34:38 -0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Separation of Transport layer and Payload specific messages in
	CCM; was Re: R:
	[AVT]CCMdraftreview--should"bandwidth"includetheheaderoverhead
Date: Mon, 26 Feb 2007 14:34:41 -0800
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B0297CC6A@NAEX01.na.qualcomm.com>
In-Reply-To: <DD8B8FEBBFAF9E488F63FF0F1A69EDD1033EB354@ftrdmel1.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Separation of Transport layer and Payload specific messages in
	CCM; was Re: R:
	[AVT]CCMdraftreview--should"bandwidth"includetheheaderoverhead
Thread-Index: AcdZkTxjTfKRCLM2QXKNG98S73ivuAAAaHCQABa3uRA=
References: <45E2B6E4.3060301@ericsson.com>
	<DD8B8FEBBFAF9E488F63FF0F1A69EDD1033EB354@ftrdmel1.rd.francetelecom.fr>
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: "SOLLAUD Aurelien RD-TECH-LAN" <aurelien.sollaud@orange-ftgroup.com>,
	"Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-OriginalArrivalTime: 26 Feb 2007 22:34:38.0596 (UTC)
	FILETIME=[4CA38440:01C759F6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: Randell Jesup <rjesup@wgate.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

> > >> If TMMBR is not pure codec-bitrate-switch-request tool, why is it
> > >> present in a draft with title "Codec Control Messages in the RTP
> > >> Audio-Visual Profile with Feedback (AVPF)"? This is what really
> > >> puzzles me. I've posted this question many times and it never got
> > >> answered.
> > >
> > > Yes, I have the same question.
> > > If TMMBR deals with network layers, it is network
> > congestion control, not Codec Control Message. And this kind
> > of TMMBR does not address the "Codec Mode Request" thing we
> > (unfortunately) find in the RTP payload formats I listed above.
> > >
> >
> > I agree that TMMBR is not directly a "CODEC" control message.
> > However it is also not a purely transport related thing
> > dealing with congestion control.=20

It is a pure transport layer feedback message as stated in Section 4.2
of the draft.

>>The main motivation for
> > TMMBR is to deal with RTP layer transport issues related RTP
> > topologies including mixers and translators. If you don't
> > understand this from the motivation text for TMMBR present in
> > the CMM draft. Can you please explain what is lacking.

The justification for making the reader think that it is a "codec"
control message is lacking. It is a codec control if it does not include
header overhead and can be directly signaled to a codec
> >
> > If you look at AVPF you can see that it does make the
> > distinction between Transport Layer feedback and Payload
> > Specific Feedback messages.
> > The FIR and TSTR are clearly payload specific in the way that
> > they only apply to certain codecs.
> TMMBR is transport related
> > because it isn't restricted to any specific codec.

It is not restricted to certain (video/audio/text) codec and that's why
I think TMMBR (with header overhead) should not be called a codec
control message and just be called a transport layer feedback message.

> >
> > It was not split out into a separate draft because the issue
> > TMMBR deals with are closely related to the one dealing with
> > video. It has been part of the discussion. It is true that
> > splitting it out to a separate draft would make this
> > separation of different types of feedback messages clearer.

Many folks assumed that TMMBR carries just codec media bit-rate only and
the question was "should header overhead bandwidth be included" (as
written in the subject of e-mail thread)? IMO, The source of confusion
is the fact that it is attempting far more beyond than just codec
control. It resulted in 2 months+ discussion which is still going and
that itself speaks that such a definition (TMMBR includes header
overhead) in CCM draft is highly confusing to many.

> > However I don't the gain in clarity from this is worth the
> > effort it will place on us authors.
> >

I don't think it is a huge task to define it (TMMBR with header
overhead) and clearly describe it in a generic (codec independent)
manner a new draft. The text from CCM draft can be easily reused.  If
done in a new draft, it can be easily referred in video related use
cases in CCM draft as well any other non-video (scalable speech) related
or more video related codec control use cases in future drafts. Also, a
new draft gives the freedom to explain it in detail and clarify why it
is far beyond codec control.


>=20
> I'm OK with that. The motivations for TMMBR are clear.
>=20
> The conclusion could be that there is a need for another kind of CCM,
to
> perform codec bitrate requests in RTCP,=20
>in a profile-independant, and
> codec-independant way.
> It means a new draft for this, not for the
> current TMMBR.
>=20
Given that it (TMMBR with header overhead) is independent of codec, one
can even play with this message without even interacting with codecs. I
mean one can just use it to control overhead above codec layers without
interacting with codecs.

> Regards,
> Aurelien

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



From avt-bounces@ietf.org Mon Feb 26 22:44:27 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLtDf-0004mu-42; Mon, 26 Feb 2007 22:41:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HLtDd-0004mo-QW
	for avt@ietf.org; Mon, 26 Feb 2007 22:41:37 -0500
Received: from brixmail.brixnet.com ([63.122.27.37]
	helo=brixmail.ma.brixnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLtDY-0005W3-H0
	for avt@ietf.org; Mon, 26 Feb 2007 22:41:37 -0500
Received: from mail pickup service by brixmail.ma.brixnet.com with Microsoft
	SMTPSVC; Mon, 26 Feb 2007 22:41:32 -0500
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
Importance: normal
Priority: normal
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 26 Feb 2007 22:41:31 -0500
Message-ID: <DA7323DD48676E4CAF5C4450D442254123DC74@brixmail.ma.brixnet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RTCP XR Report Block for IPTV Metrics...
thread-index: AcdaISuj+MGeBlgRRpGHX2Y9wJPkHw==
From: "Venna, Nagarjuna" <nvenna@Brixnet.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 27 Feb 2007 03:41:32.0356 (UTC)
	FILETIME=[2C185040:01C75A21]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: 
Subject: [AVT] RTCP XR Report Block for IPTV Metrics...
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0684740740=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0684740740==
Content-Transfer-Encoding: 7bit
Content-Class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C75A21.2BB8FDCC"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C75A21.2BB8FDCC
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


I have posted an individual draft =
(http://www.ietf.org/internet-drafts/draft-venna-avt-rtcpxr-iptv-00.txt) =
that proposes a new RTCP-XR block for IPTV applications that use RFC =
2250.

Comments and feedback are appreciated.

Thanks,
Nagarjuna


-------------------------------------------------------------------------=
----------------------------------------------------------------------
Service Quality Matters. Test the performance and quality of your VoIP =
or IP video service at:=20
http://www.TestYourVoIP.com
http://www.TestYourIPVideo.com
------_=_NextPart_001_01C75A21.2BB8FDCC
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7651.59">
<TITLE>RTCP XR Report Block for IPTV Metrics...</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>

<P><FONT SIZE=3D2>I have posted an individual draft (<A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-venna-avt-rtcpxr-iptv-0=
0.txt">http://www.ietf.org/internet-drafts/draft-venna-avt-rtcpxr-iptv-00=
txt</A>) that proposes a new RTCP-XR block for IPTV applications that =
use RFC 2250.<BR>
<BR>
Comments and feedback are appreciated.<BR>
<BR>
Thanks,<BR>
Nagarjuna</FONT>
</P>

<BR><BR><P><FONT face=3DArial =
size=3D2>----------------------------------------------------------------=
--------------------------------------------------------------</FONT></P>=
<P><FONT face=3DArial size=3D2>Service Quality Matters. Test the =
performance and quality of your VoIP or IP video service =
at:</FONT></P><FONT color=3D#0000ff></FONT><P><FONT =
color=3D#0000ff><FONT face=3DArial size=3D2><A =
href=3D"http://www.testyourvoip.com/">http://www.TestYourVoIP.com</A></FO=
NT></FONT></P><P><FONT color=3D#0000ff><FONT face=3DArial size=3D2><A =
href=3D"http://www.testyouripvideo.com/">http://www.TestYourIPVideo.com</=
A></FONT></FONT></P></BODY>
</HTML>
------_=_NextPart_001_01C75A21.2BB8FDCC--


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

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

--===============0684740740==--




From avt-bounces@ietf.org Tue Feb 27 14:05:07 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HM7br-0006fy-95; Tue, 27 Feb 2007 14:03:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HM7bp-0006fe-NL; Tue, 27 Feb 2007 14:03:33 -0500
Received: from mta3.srv.hcvlny.cv.net ([167.206.4.198])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HM7bn-00072W-Ag; Tue, 27 Feb 2007 14:03:33 -0500
Received: from jonathanlmi (ool-44c5ee3a.dyn.optonline.net [68.197.238.58])
	by mta3.srv.hcvlny.cv.net
	(Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
	with ESMTP id <0JE4002R4Y9U5880@mta3.srv.hcvlny.cv.net>; Tue,
	27 Feb 2007 14:03:31 -0500 (EST)
Date: Tue, 27 Feb 2007 14:03:28 -0500
From: Jonathan Lennox <jonathan@layeredmedia.com>
To: avt@ietf.org, mmusic@ietf.org
Message-id: <00d201c75aa1$f7671170$ad01a8c0@jonathanlmi>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/mixed; boundary="Boundary_(ID_9Z/s8S3yGbLdx67nJjNTkA)"
Thread-index: Acdaofbv3adEN29SSjO1+ZgRPK2rLg==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176
Cc: 'Joerg Ott' <jo@netlab.tkk.fi>
Subject: [AVT] Draft on source-specific SDP attributes:
 draft-lennox-mmusic-sdp-source-attributes-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

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

Joerg Ott, Thomas Schierl, and I have written an Internet-Draft on
source-specific SDP attributes,
draft-lennox-mmusic-sdp-source-attributes-00, now available from the I-D
repository.

The draft allows individual RTP sources to be described in SDP session
descriptions, generalizing the mechanism used by the draft on RTCP
extensions for single-source multicast (draft-ietf-avt-rtcpssm).  It was
also originally motivated by the desire to support ssrc-multiplexing of
H.264 SVC, as originally used by draft-wenger-avt-rtp-svc-02 and
draft-schierl-mmusic-layered-codec-01, though the latest revisions of those
drafts have dropped support for ssrc-multiplexing for other reasons.

Comments are welcome.

I'm sending this annoucement to the AVT group as well as MMUSIC, as the
draft's mechanisms have non-trivial interactions with RTP collision
detection.   Please direct followups to only one of the working group
mailing lists, depending on the topic being discussed.

-- 
Jonathan Lennox -- Layered Media
jonathan@layeredmedia.com

--Boundary_(ID_9Z/s8S3yGbLdx67nJjNTkA)
Content-type: message/rfc822
Content-disposition: attachment

Return-path: <lennox@cs.columbia.edu>
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by spf6-5.us4.outblaze.com (Postfix) with ESMTP id 921FE1070E7	for
	<jonathan@layeredmedia.com>; Mon, 26 Feb 2007 21:51:51 +0000 (GMT)
Received: from av1-4.us4.outblaze.com (av1-4.us4.outblaze.com [127.0.0.1])
	by av1-4.us4.outblaze.com (Postfix) with SMTP id 8E31517C12B	for
	<"jonathan:layeredmedia.com"@register.com.avs.int>; Mon,
	26 Feb 2007 21:51:52 +0000 (GMT)
Received: from metro-north.cs.columbia.edu
	(metro-north.cs.columbia.edu [128.59.19.61])
	by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id l1QLpm3h003615
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 26 Feb 2007 16:51:48 -0500 (EST)
Received: (from lennox@localhost)	by metro-north.cs.columbia.edu
	(8.12.10/8.12.10/Submit) id l1QLpa8R017141	for
	jonathan@layeredmedia.com; Mon, 26 Feb 2007 16:51:36 -0500 (EST)
Received: from metro-north.cs.columbia.edu (localhost [127.0.0.1])
	by metro-north.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id
	l1QLpaxn017144; Mon, 26 Feb 2007 16:51:44 -0500 (EST)
Received: (qmail 6219 invoked by uid 1001); Mon, 26 Feb 2007 21:51:54 +0000
Date: Mon, 26 Feb 2007 15:50:02 -0500
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-lennox-mmusic-sdp-source-attributes-00.txt
To: i-d-announce@ietf.org
Reply-to: internet-drafts@ietf.org
Message-id: <E1HLmnK-0004zI-Pe@stiedprstage1.ietf.org>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/mixed; boundary="Boundary_(ID_Q3ubY9R1oFGlPODsKK5ohw)"
Thread-index: AcdZ8FQFYx56SsMpSBK5tScFld1QGw==
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>

This is a multi-part message in MIME format.

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

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.


	Title		: Source-Specific Media Attributes in the Session
Description Protocol (SDP)
	Author(s)	: J. Lennox, et al.
	Filename	: draft-lennox-mmusic-sdp-source-attributes-00.txt
	Pages		: 20
	Date		: 2007-2-26
	
   The Session Description Protocol provides mechanisms to describe
   attributes of multimedia sessions and of individual media streams
   (e.g., Real-time Transport Protocol (RTP) sessions) within a
   multimedia session, but does not provide any mechanism to describe
   individual media sources within a media stream.  This document
   defines a mechanism to describe RTP media sources, identified by
   their Synchronization Source Identifiers (SSRCs), in SDP, associate
   attributes with these sources, and express relationships among
   sources.  It also defines a number of source-level attributes which
   can be used to describe properties of media sources.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-lennox-mmusic-sdp-source-attribute
s-00.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-lennox-mmusic-sdp-source-attributes-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE
/internet-drafts/draft-lennox-mmusic-sdp-source-attributes-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

--Boundary_(ID_Q3ubY9R1oFGlPODsKK5ohw)
Content-type: Message/External-body; name=ATT00173.dat
Content-transfer-encoding: 7bit
Content-disposition: attachment; filename=ATT00173.dat

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

ENCODING mime
FILE /internet-drafts/draft-lennox-mmusic-sdp-source-attributes-00.txt

--Boundary_(ID_Q3ubY9R1oFGlPODsKK5ohw)
Content-type: Message/External-body;
	name=draft-lennox-mmusic-sdp-source-attributes-00.txt
Content-transfer-encoding: 7bit
Content-disposition: attachment;
	filename=draft-lennox-mmusic-sdp-source-attributes-00.txt

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


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

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

--Boundary_(ID_Q3ubY9R1oFGlPODsKK5ohw)--

--Boundary_(ID_9Z/s8S3yGbLdx67nJjNTkA)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--Boundary_(ID_9Z/s8S3yGbLdx67nJjNTkA)--




From avt-bounces@ietf.org Wed Feb 28 04:15:59 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMKtL-0007xg-GI; Wed, 28 Feb 2007 04:14:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMKtK-0007xT-Is
	for avt@ietf.org; Wed, 28 Feb 2007 04:14:30 -0500
Received: from maild.telecomitalia.it ([156.54.233.30])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMKtD-0004VK-QX
	for avt@ietf.org; Wed, 28 Feb 2007 04:14:30 -0500
Received: from ptpxch008ba020.idc.cww.telecomitalia.it ([156.54.240.51]) by
	maild.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830);
	Wed, 28 Feb 2007 10:14:14 +0100
Received: from PTPEVS108BA020.idc.cww.telecomitalia.it ([156.54.241.227]) by
	ptpxch008ba020.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 28 Feb 2007 10:14:14 +0100
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Importance: normal
Priority: normal
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: IETF IPR policy (was Re: R: [AVT] CCM draft
	review--	should"bandwidth"includetheheaderoverhead)
Date: Wed, 28 Feb 2007 10:14:13 +0100
Message-ID: <E9D1028EC5C22B418B5D54CA6EA27C579A5EEA@PTPEVS108BA020.idc.cww.telecomitalia.it>
In-Reply-To: <9C7093C8-B5DD-4082-BE95-2A7AD7E31DD3@csperkins.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IETF IPR policy (was Re: R: [AVT] CCM draft
	review--	should"bandwidth"includetheheaderoverhead)
thread-index: AcdXOASR8SNEaTaSQuG7g1c4R4nfTQD4J2gQ
From: "Franceschini Guido" <guido.franceschini@telecomitalia.it>
To: "Colin Perkins" <csp@csperkins.org>
X-OriginalArrivalTime: 28 Feb 2007 09:14:14.0121 (UTC)
	FILETIME=[D0A5AD90:01C75B18]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Colin, all,

The automatically inserted notice only states that if you received my =
mail by mistake you should not make any use of it.
But if you are an intended recipient, no problem.
I got confirmation about this from the legal dept.

Guido

> -----Original Message-----
> From: Colin Perkins [mailto:csp@csperkins.org]
> Sent: venerd=EC 23 febbraio 2007 11.47
> To: Franceschini Guido
> Cc: IETF AVT WG
> Subject: IETF IPR policy (was Re: R: [AVT] CCM draft review--
> should"bandwidth"includetheheaderoverhead)
>=20
>=20
> On 23 Feb 2007, at 10:33, Franceschini Guido wrote:
> > CONFIDENTIALITY NOTICE
> >
> > This message and its attachments are addressed solely to the =20
> > persons above and may contain confidential information. If=20
> you have =20
> > received the message in error, be informed that any use of the =20
> > content hereof is prohibited. Please return it immediately to the =20
> > sender and delete the message. Should you have any questions, =20
> > please contact us by replying to webmaster@telecomitalia.it.
> >
> >         Thank you
> >
> >                                         www.telecomitalia.it
> >
> > --------------------------------------------------------------------
>=20
> A reminder that the IETF IPR policy [RFC 3978 section 3.2] states:
>=20
>     No information or document that is subject to any requirement of
>     confidentiality or any restriction on its dissemination may be
>     submitted as a Contribution or otherwise considered in any part of
>     the IETF Standards Process, and there must be no assumption of any
>     confidentiality obligation with respect to any Contribution.  Each
>     Contributor agrees that any statement in a Contribution, whether
>     generated automatically or otherwise, that states or=20
> implies that =20
> the
>     Contribution is confidential or subject to any privilege, can be
>     disregarded for all purposes, and will be of no force or effect.
>=20
> --=20
> Colin Perkins
> http://csperkins.org/
>=20
>=20
>=20
--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons =
above and may contain confidential information. If you have received the =
message in error, be informed that any use of the content hereof is =
prohibited. Please return it immediately to the sender and delete the =
message. Should you have any questions, please contact us by replying to =
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                       =20

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



From avt-bounces@ietf.org Wed Feb 28 05:17:17 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMLqV-0004EW-PZ; Wed, 28 Feb 2007 05:15:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMLqU-0004Di-At
	for avt@ietf.org; Wed, 28 Feb 2007 05:15:38 -0500
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMLqS-0004Sw-So
	for avt@ietf.org; Wed, 28 Feb 2007 05:15:38 -0500
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:56763)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HMLqS-0004XM-8Q; Wed, 28 Feb 2007 10:15:36 +0000
In-Reply-To: <E9D1028EC5C22B418B5D54CA6EA27C579A5EEA@PTPEVS108BA020.idc.cww.telecomitalia.it>
References: <E9D1028EC5C22B418B5D54CA6EA27C579A5EEA@PTPEVS108BA020.idc.cww.telecomitalia.it>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <FC8E262C-2E34-4F9F-80E9-D3ACB67303C6@csperkins.org>
Content-Transfer-Encoding: quoted-printable
From: Colin Perkins <csp@csperkins.org>
Subject: Re: IETF IPR policy (was Re: R: [AVT] CCM draft
	review--	should"bandwidth"includetheheaderoverhead)
Date: Wed, 28 Feb 2007 10:15:35 +0000
To: Franceschini Guido <guido.franceschini@telecomitalia.it>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Guido,

My point was to remind you, and the working group, that the IETF IPR =20
policy disallows such confidentiality notices [RFC 3978 section 3.2].

Colin




On 28 Feb 2007, at 09:14, Franceschini Guido wrote:
> Colin, all,
>
> The automatically inserted notice only states that if you received =20
> my mail by mistake you should not make any use of it.
> But if you are an intended recipient, no problem.
> I got confirmation about this from the legal dept.
>
> Guido
>
>> -----Original Message-----
>> From: Colin Perkins [mailto:csp@csperkins.org]
>> Sent: venerd=EC 23 febbraio 2007 11.47
>> To: Franceschini Guido
>> Cc: IETF AVT WG
>> Subject: IETF IPR policy (was Re: R: [AVT] CCM draft review--
>> should"bandwidth"includetheheaderoverhead)
>>
>>
>> On 23 Feb 2007, at 10:33, Franceschini Guido wrote:
>>> CONFIDENTIALITY NOTICE
>>>
>>> This message and its attachments are addressed solely to the
>>> persons above and may contain confidential information. If
>> you have
>>> received the message in error, be informed that any use of the
>>> content hereof is prohibited. Please return it immediately to the
>>> sender and delete the message. Should you have any questions,
>>> please contact us by replying to webmaster@telecomitalia.it.
>>>
>>>         Thank you
>>>
>>>                                         www.telecomitalia.it
>>>
>>> --------------------------------------------------------------------
>>
>> A reminder that the IETF IPR policy [RFC 3978 section 3.2] states:
>>
>>     No information or document that is subject to any requirement of
>>     confidentiality or any restriction on its dissemination may be
>>     submitted as a Contribution or otherwise considered in any =20
>> part of
>>     the IETF Standards Process, and there must be no assumption of =20=

>> any
>>     confidentiality obligation with respect to any Contribution.  =20
>> Each
>>     Contributor agrees that any statement in a Contribution, whether
>>     generated automatically or otherwise, that states or
>> implies that
>> the
>>     Contribution is confidential or subject to any privilege, can be
>>     disregarded for all purposes, and will be of no force or effect.
>>
>> --=20
>> Colin Perkins
>> http://csperkins.org/


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



From avt-bounces@ietf.org Wed Feb 28 10:10:55 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMQQo-0004eN-Ij; Wed, 28 Feb 2007 10:09:26 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMQQZ-0004Kd-H2; Wed, 28 Feb 2007 10:09:12 -0500
Received: from expint.psytechnics.com ([217.33.106.234])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HMQKJ-0008Jy-1D; Wed, 28 Feb 2007 10:02:44 -0500
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
Date: Wed, 28 Feb 2007 15:03:26 -0000
Message-ID: <257B18BFF522214E92EB52F3478B014E094688@psy01exch.intra.psytechnics.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Perceptual objective media quality reporting
thread-index: AcdbSZlLw9qRfvsQSU61gayfTs285Q==
From: "Ravi Raviraj" <ravi.raviraj@psytechnics.com>
To: <sipping@ietf.org>,
	<sip@ietf.org>,
	<avt@ietf.org>
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 8b6657e60309a1317174c9db2ae5f227
Cc: 
Subject: [AVT] Perceptual objective media quality reporting
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1419409037=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1419409037==
Content-Class: urn:content-classes:message
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C75B49.9952ED7C"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C75B49.9952ED7C
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

Over the last few years, a number of perceptual media quality objective
measures and assessment techniques have been standardized by ITU-T. For
example, MOS-LQO, MOS-CQO, etc. Each one of these parameters could have
number of variations like narrow-band/wide-band, electrical/acoustical,
full reference/no-reference, audio/video, etc. When applied within a
network end-point, each media direction (ingress/egress) could have one
or more of these values associated with it. We need a way to report
these values efficiently without any ambiguity. These MOS values could
be sent/distributed as perceptual objective quality SIP events. In this
way, all the advantages of SIP like mobility, etc. will be pulled in.

=20

I would like to propose a work/discussion item on an event package for
this purpose. Even define/specify a quality reporting framework. Is
there any interest out there?

=20

I presume that, an event package work will be within SIPPING WG, where
should we do the framework work? SIP/AVT?

=20

Thanks.

=20

Ravi.

=20





This email and attachment are confidential. If you have received this =
message in error, please notify the sender immediately and delete the =
message from your computer. Psytechnics Ltd has taken steps to ensure =
that this email is virus free but the recipient should take necessary =
steps to make certain.




------_=_NextPart_001_01C75B49.9952ED7C
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
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 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>Hi all,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>Over the last few years, a number of =
perceptual media
quality objective measures and assessment techniques have been =
standardized by
ITU-T. For example, MOS-LQO, MOS-CQO, etc. Each one of these parameters =
could
have number of variations like narrow-band/wide-band, =
electrical/acoustical,
full reference/no-reference, audio/video, etc. When applied within a =
network
end-point, each media direction (ingress/egress) could have one or more =
of
these values associated with it. We need a way to report these values
efficiently without any ambiguity. These MOS values could be =
sent/distributed as
perceptual objective quality SIP events. In this way, all the advantages =
of SIP
like mobility, etc. will be pulled in.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>I would like to propose a work/discussion item =
on an
event package for this purpose. Even define/specify a quality reporting
framework. Is there any interest out there?<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>I presume that, an event package work will be =
within
SIPPING WG, where should we do the framework work? =
SIP/AVT?<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>Thanks.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><st1:place w:st=3D"on"><font size=3D2 =
face=3DArial><span
 lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Arial'>Ravi</span></font></st1:plac=
e><font
size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Arial'>.<o:p></o:p></span></font></=
p>

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

</div>

</body>

</html>




This email and attachment are confidential. If you have received this =
message in error, please notify the sender immediately and delete the =
message from your computer. Psytechnics Ltd has taken steps to ensure =
that this email is virus free but the recipient should take necessary =
steps to make certain.




------_=_NextPart_001_01C75B49.9952ED7C--


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

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

--===============1419409037==--




From avt-bounces@ietf.org Wed Feb 28 10:43:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMQwt-0004Um-Mm; Wed, 28 Feb 2007 10:42:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMQwr-0004Tt-P5
	for avt@ietf.org; Wed, 28 Feb 2007 10:42:33 -0500
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMQwq-0005g9-99
	for avt@ietf.org; Wed, 28 Feb 2007 10:42:33 -0500
Received: from [172.17.1.65] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l1SFex9F042482
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Wed, 28 Feb 2007 09:42:31 -0600 (CST)
	(envelope-from rjsparks@nostrum.com)
In-Reply-To: <257B18BFF522214E92EB52F3478B014E094688@psy01exch.intra.psytechnics.com>
References: <257B18BFF522214E92EB52F3478B014E094688@psy01exch.intra.psytechnics.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <44BC83F3-34FA-42C8-ADB4-804915F2931E@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
Date: Wed, 28 Feb 2007 09:42:30 -0600
To: "Ravi Raviraj" <ravi.raviraj@psytechnics.com>
X-Mailer: Apple Mail (2.752.3)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: avt@ietf.org
Subject: [AVT] Re: [Sipping] Perceptual objective media quality reporting
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0350086991=="
Errors-To: avt-bounces@ietf.org


--===============0350086991==
Content-Type: multipart/alternative; boundary=Apple-Mail-33--1050861021


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

I've replied to this on the SIPPING list and suggest that subsequent  
conversation take place there.

On Feb 28, 2007, at 9:03 AM, Ravi Raviraj wrote:

> Hi all,
>
> Over the last few years, a number of perceptual media quality  
> objective measures and assessment techniques have been standardized  
> by ITU-T. For example, MOS-LQO, MOS-CQO, etc. Each one of these  
> parameters could have number of variations like narrow-band/wide- 
> band, electrical/acoustical, full reference/no-reference, audio/ 
> video, etc. When applied within a network end-point, each media  
> direction (ingress/egress) could have one or more of these values  
> associated with it. We need a way to report these values  
> efficiently without any ambiguity. These MOS values could be sent/ 
> distributed as perceptual objective quality SIP events. In this  
> way, all the advantages of SIP like mobility, etc. will be pulled in.
>
>
>
> I would like to propose a work/discussion item on an event package  
> for this purpose. Even define/specify a quality reporting  
> framework. Is there any interest out there?
>
>
>
> I presume that, an event package work will be within SIPPING WG,  
> where should we do the framework work? SIP/AVT?
>
>
>
> Thanks.
>
>
>
> Ravi.
>
>
>
> This email and attachment are confidential. If you have received  
> this message in error, please notify the sender immediately and  
> delete the message from your computer. Psytechnics Ltd has taken  
> steps to ensure that this email is virus free but the recipient  
> should take necessary steps to make certain.
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


--Apple-Mail-33--1050861021
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">I've replied to this on the =
SIPPING list and suggest that subsequent conversation take place =
there.<DIV><BR><DIV><DIV>On Feb 28, 2007, at 9:03 AM, Ravi Raviraj =
wrote:</DIV><BR class=3D"Apple-interchange-newline"><BLOCKQUOTE =
type=3D"cite"><O:SMARTTAGTYPE =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"place"> <DIV class=3D"Section1"><P class=3D"MsoNormal"><FONT =
size=3D"2" face=3D"Arial"><SPAN lang=3D"EN-GB" style=3D"font-size: =
10.0pt;font-family:Arial">Hi all,<O:P></O:P></SPAN></FONT></P><P =
class=3D"MsoNormal"><FONT size=3D"2" face=3D"Arial"><SPAN lang=3D"EN-GB" =
style=3D"font-size: 10.0pt;font-family:Arial">Over the last few years, a =
number of perceptual media quality objective measures and assessment =
techniques have been standardized by ITU-T. For example, MOS-LQO, =
MOS-CQO, etc. Each one of these parameters could have number of =
variations like narrow-band/wide-band, electrical/acoustical, full =
reference/no-reference, audio/video, etc. When applied within a network =
end-point, each media direction (ingress/egress) could have one or more =
of these values associated with it. We need a way to report these values =
efficiently without any ambiguity. These MOS values could be =
sent/distributed as perceptual objective quality SIP events. In this =
way, all the advantages of SIP like mobility, etc. will be pulled =
in.<O:P></O:P></SPAN></FONT></P><P class=3D"MsoNormal"><FONT size=3D"2" =
face=3D"Arial"><SPAN lang=3D"EN-GB" style=3D"font-size: =
10.0pt;font-family:Arial"><O:P>=A0</O:P></SPAN></FONT></P><P =
class=3D"MsoNormal"><FONT size=3D"2" face=3D"Arial"><SPAN lang=3D"EN-GB" =
style=3D"font-size: 10.0pt;font-family:Arial">I would like to propose a =
work/discussion item on an event package for this purpose. Even =
define/specify a quality reporting framework. Is there any interest out =
there?<O:P></O:P></SPAN></FONT></P><P class=3D"MsoNormal"><FONT size=3D"2"=
 face=3D"Arial"><SPAN lang=3D"EN-GB" style=3D"font-size: =
10.0pt;font-family:Arial"><O:P>=A0</O:P></SPAN></FONT></P><P =
class=3D"MsoNormal"><FONT size=3D"2" face=3D"Arial"><SPAN lang=3D"EN-GB" =
style=3D"font-size: 10.0pt;font-family:Arial">I presume that, an event =
package work will be within SIPPING WG, where should we do the framework =
work? SIP/AVT?<O:P></O:P></SPAN></FONT></P><P class=3D"MsoNormal"><FONT =
size=3D"2" face=3D"Arial"><SPAN lang=3D"EN-GB" style=3D"font-size: =
10.0pt;font-family:Arial"><O:P>=A0</O:P></SPAN></FONT></P><P =
class=3D"MsoNormal"><FONT size=3D"2" face=3D"Arial"><SPAN lang=3D"EN-GB" =
style=3D"font-size: =
10.0pt;font-family:Arial">Thanks.<O:P></O:P></SPAN></FONT></P><P =
class=3D"MsoNormal"><FONT size=3D"2" face=3D"Arial"><SPAN lang=3D"EN-GB" =
style=3D"font-size: =
10.0pt;font-family:Arial"><O:P>=A0</O:P></SPAN></FONT></P><P =
class=3D"MsoNormal"><ST1:PLACE w:st=3D"on"><FONT size=3D"2" =
face=3D"Arial"><SPAN lang=3D"EN-GB" =
style=3D"font-size:10.0pt;font-family:Arial">Ravi</SPAN></FONT></ST1:PLACE=
><FONT size=3D"2" face=3D"Arial"><SPAN lang=3D"EN-GB" =
style=3D"font-size:10.0pt;font-family:Arial">.<O:P></O:P></SPAN></FONT></P=
><P class=3D"MsoNormal"><FONT size=3D"3" face=3D"Times New Roman"><SPAN =
style=3D"font-size: 12.0pt"><O:P>=A0</O:P></SPAN></FONT></P> </DIV> This =
email and attachment are confidential. If you have received this message =
in error, please notify the sender immediately and delete the message =
from your computer. Psytechnics Ltd has taken steps to ensure that this =
email is virus free but the recipient should take necessary steps to =
make certain. </O:SMARTTAGTYPE><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">_______________________________________________</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Sipping mailing list<SPAN =
class=3D"Apple-converted-space">=A0 </SPAN><A =
href=3D"https://www1.ietf.org/mailman/listinfo/sipping">https://www1.ietf.=
org/mailman/listinfo/sipping</A></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">This list is =
for NEW development of the application of SIP</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Use <A =
href=3D"mailto:sip-implementors@cs.columbia.edu">sip-implementors@cs.colum=
bia.edu</A> for questions on current sip</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Use <A =
href=3D"mailto:sip@ietf.org">sip@ietf.org</A> for new developments of =
core SIP</DIV> </BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>=

--Apple-Mail-33--1050861021--


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

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

--===============0350086991==--




From avt-bounces@ietf.org Wed Feb 28 10:53:00 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMR6O-00018j-0J; Wed, 28 Feb 2007 10:52:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMR6L-00017W-C7; Wed, 28 Feb 2007 10:52:21 -0500
Received: from mx.cbeyond.com ([66.180.96.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HMR6J-0006eM-RC; Wed, 28 Feb 2007 10:52:21 -0500
Received: from [69.15.238.196] (port=3427 helo=TELCHADCPC)
	by mx.cbeyond.com with esmtpa (Exim 4.62)
	(envelope-from <alan.d.clark@telchemy.com>)
	id 1HMS3S-0000M7-AQ; Wed, 28 Feb 2007 11:53:26 -0500
From: "Alan Clark" <alan.d.clark@telchemy.com>
To: "'Ravi Raviraj'" <ravi.raviraj@psytechnics.com>, <sipping@ietf.org>,
	<sip@ietf.org>, <avt@ietf.org>
Subject: RE: [AVT] Perceptual objective media quality reporting
Date: Wed, 28 Feb 2007 10:52:13 -0500
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcdbSZlLw9qRfvsQSU61gayfTs285QABkZRA
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
In-Reply-To: <257B18BFF522214E92EB52F3478B014E094688@psy01exch.intra.psytechnics.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f0b5a4216bfa030ed8a6f68d1833f8ae
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1791330016=="
Errors-To: avt-bounces@ietf.org
Message-Id: <E1HMR6O-00018j-0J@megatron.ietf.org>

This is a multi-part message in MIME format.

--===============1791330016==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0039_01C75B26.819B6C40"

This is a multi-part message in MIME format.

------=_NextPart_000_0039_01C75B26.819B6C40
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi Ravi
 
The industry has been doing this for some time - there is an existing draft
in SIPPING - for the SIP RTCP Summary Report that does exactly what you are
asking for, also RTCP XR (RFC3611), RTCP HR (current AVT WG draft), and a
laundry list of other protocols for MGCP, Megaco.......  In some cases (e.g.
RTCP HR, SIP) you can indicate the algorithm used to estimate quality, and
hence if you wanted to use PESQ in an active test then you could report
using the SIP RTCP Summary Report and indicate that the MOS estimation
algorithm was P.862.n
 
Regards
 
Alan
 

  _____  

From: Ravi Raviraj [mailto:ravi.raviraj@psytechnics.com] 
Sent: Wednesday, February 28, 2007 10:03 AM
To: sipping@ietf.org; sip@ietf.org; avt@ietf.org
Subject: [AVT] Perceptual objective media quality reporting



Hi all,

Over the last few years, a number of perceptual media quality objective
measures and assessment techniques have been standardized by ITU-T. For
example, MOS-LQO, MOS-CQO, etc. Each one of these parameters could have
number of variations like narrow-band/wide-band, electrical/acoustical, full
reference/no-reference, audio/video, etc. When applied within a network
end-point, each media direction (ingress/egress) could have one or more of
these values associated with it. We need a way to report these values
efficiently without any ambiguity. These MOS values could be
sent/distributed as perceptual objective quality SIP events. In this way,
all the advantages of SIP like mobility, etc. will be pulled in.

 

I would like to propose a work/discussion item on an event package for this
purpose. Even define/specify a quality reporting framework. Is there any
interest out there?

 

I presume that, an event package work will be within SIPPING WG, where
should we do the framework work? SIP/AVT?

 

Thanks.

 

Ravi.

 

This email and attachment are confidential. If you have received this
message in error, please notify the sender immediately and delete the
message from your computer. Psytechnics Ltd has taken steps to ensure that
this email is virus free but the recipient should take necessary steps to
make certain. 

------=_NextPart_000_0039_01C75B26.819B6C40
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:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR><o:SmartTagType =
name=3D"place"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@page Section1 {size: 612.0pt 792.0pt; margin: 72.0pt 90.0pt =
72.0pt 90.0pt; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D546214815-28022007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Ravi</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D546214815-28022007><FONT =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D546214815-28022007><FONT =
color=3D#0000ff=20
size=3D2>The industry&nbsp;has been doing this for some time - there is =
an=20
existing draft in SIPPING - for the SIP RTCP Summary Report that does =
exactly=20
what you are asking for, also RTCP XR (RFC3611), RTCP HR (current AVT WG =
draft),=20
and a laundry list of other protocols for MGCP, Megaco.......&nbsp; In =
some=20
cases (e.g. RTCP HR, SIP) you can indicate the algorithm used to =
estimate=20
quality, and hence if you wanted to use PESQ in an active test then you =
could=20
report using the SIP RTCP Summary Report and indicate that the MOS =
estimation=20
algorithm was P.862.n</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D546214815-28022007><FONT =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D546214815-28022007><FONT =
color=3D#0000ff=20
size=3D2>Regards</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D546214815-28022007><FONT =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D546214815-28022007><FONT =
color=3D#0000ff=20
size=3D2>Alan</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D546214815-28022007><FONT =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Ravi Raviraj=20
[mailto:ravi.raviraj@psytechnics.com] <BR><B>Sent:</B> Wednesday, =
February 28,=20
2007 10:03 AM<BR><B>To:</B> sipping@ietf.org; sip@ietf.org;=20
avt@ietf.org<BR><B>Subject:</B> [AVT] Perceptual objective media quality =

reporting<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi =
all,<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Over the last few years, a =
number of=20
perceptual media quality objective measures and assessment techniques =
have been=20
standardized by ITU-T. For example, MOS-LQO, MOS-CQO, etc. Each one of =
these=20
parameters could have number of variations like narrow-band/wide-band,=20
electrical/acoustical, full reference/no-reference, audio/video, etc. =
When=20
applied within a network end-point, each media direction =
(ingress/egress) could=20
have one or more of these values associated with it. We need a way to =
report=20
these values efficiently without any ambiguity. These MOS values could =
be=20
sent/distributed as perceptual objective quality SIP events. In this =
way, all=20
the advantages of SIP like mobility, etc. will be pulled=20
in.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I would like to propose a=20
work/discussion item on an event package for this purpose. Even =
define/specify a=20
quality reporting framework. Is there any interest out=20
there?<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I presume that, an event =
package=20
work will be within SIPPING WG, where should we do the framework work?=20
SIP/AVT?<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Thanks.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><st1:place w:st=3D"on"><FONT face=3DArial =
size=3D2><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Ravi</SPAN></FONT></st1:place><FONT=20
face=3DArial size=3D2><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV>This =
email and=20
attachment are confidential. If you have received this message in error, =
please=20
notify the sender immediately and delete the message from your computer. =

Psytechnics Ltd has taken steps to ensure that this email is virus free =
but the=20
recipient should take necessary steps to make certain. </BODY></HTML>

------=_NextPart_000_0039_01C75B26.819B6C40--



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

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

--===============1791330016==--





From avt-bounces@ietf.org Wed Feb 28 11:59:50 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMS8v-0004tl-MV; Wed, 28 Feb 2007 11:59:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMS8u-0004rM-2h; Wed, 28 Feb 2007 11:59:04 -0500
Received: from expint.psytechnics.com ([217.33.106.234])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HMS8s-0006Hb-Qu; Wed, 28 Feb 2007 11:59:04 -0500
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
Date: Wed, 28 Feb 2007 16:59:46 -0000
Message-ID: <257B18BFF522214E92EB52F3478B014E09468D@psy01exch.intra.psytechnics.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Perceptual objective media quality reporting
thread-index: AcdbUjlX/MqWBMo7RMOgxZNziI+gSwABuw9g
From: "Ravi Raviraj" <ravi.raviraj@psytechnics.com>
To: <sip@ietf.org>,
	<avt@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: 
Subject: [AVT] Perceptual objective media quality reporting
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi all,
Number of people asked me to discuss this in the SIPPING list.
So, let's discuss it over there.

If you are interested in this topic, please have a look over there.

Thanks.

Ravi.






This email and attachment are confidential. If you have received this =
message in error, please notify the sender immediately and delete the =
message from your computer. Psytechnics Ltd has taken steps to ensure =
that this email is virus free but the recipient should take necessary =
steps to make certain.




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



From avt-bounces@ietf.org Wed Feb 28 18:12:00 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMXwk-00015g-FN; Wed, 28 Feb 2007 18:10:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMXwj-00013n-6E; Wed, 28 Feb 2007 18:10:53 -0500
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HMXwh-0007NW-S6; Wed, 28 Feb 2007 18:10:53 -0500
Received: from relay6.apple.com (relay6.apple.com [17.128.113.36])
	by mail-out4.apple.com (8.13.8/8.13.8) with ESMTP id l1SNAoZZ008652;
	Wed, 28 Feb 2007 15:10:50 -0800 (PST)
Received: from relay6.apple.com (unknown [127.0.0.1])
	by relay6.apple.com (Symantec Mail Security) with ESMTP id A4C0C10C73; 
	Wed, 28 Feb 2007 15:10:50 -0800 (PST)
X-AuditID: 11807124-a0f56bb0000035e0-a9-45e60bfac6cc 
Received: from [17.202.35.52] (singda.apple.com [17.202.35.52])
	by relay6.apple.com (Apple SCV relay) with ESMTP id 529DE10C3A;
	Wed, 28 Feb 2007 15:10:50 -0800 (PST)
Mime-Version: 1.0
Message-Id: <p06230929c20bbb8356e9@[17.202.35.52]>
In-Reply-To: <0a2801c75b81$3bd56ca0$70a36b80@amer.cisco.com>
References: <0a2801c75b81$3bd56ca0$70a36b80@amer.cisco.com>
Date: Wed, 28 Feb 2007 15:09:50 -0800
To: mmusic@ietf.org
From: Dave Singer <singer@apple.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: avt@ietf.org
Subject: [AVT] linking two streams in SDP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

If I have one stream which carries optional 'repair' data for another 
stream, and I want to send them on two separate multicast groups, or 
two separate streams to an RTSP client, how would I indicate that 
'this media stream' is the repair data for 'that media stream' in SDP?

I guess this is somewhat like scalable coding, in which I would need 
to say 'this stream' is an enhancement, and builds on 'that stream'.

I have no idea how to write a stream reference in SDP, i.e. how to 
say 'that stream'.  The techniques for scalable coding seem to be 
confined to assigning consecutive port numbers or multicast 
addresses, neither of which seem to apply when RTSP/SDP is used.

Help?
-- 
David Singer
Apple Computer/QuickTime

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



From avt-bounces@ietf.org Wed Feb 28 19:13:16 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMYtF-0000Sc-Fb; Wed, 28 Feb 2007 19:11:21 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMYt5-0000Lq-JB; Wed, 28 Feb 2007 19:11:11 -0500
Received: from 206-225-85-160.dedicated.abac.net ([206.225.85.160]
	helo=server.zchannels.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HMYsQ-0002Xe-QF; Wed, 28 Feb 2007 19:11:11 -0500
Received: from [192.168.142.102] (rrcs-67-52-150-122.west.biz.rr.com
	[67.52.150.122]) (authenticated bits=0)
	by server.zchannels.com (8.13.6/8.13.4) with ESMTP id l21083BM060836
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 28 Feb 2007 16:08:07 -0800 (PST)
	(envelope-from adamli@hyervision.com)
Message-ID: <45E619EA.9060907@hyervision.com>
Date: Wed, 28 Feb 2007 16:10:18 -0800
From: Adam Li <adamli@hyervision.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Dave Singer <singer@apple.com>
References: <0a2801c75b81$3bd56ca0$70a36b80@amer.cisco.com>
	<p06230929c20bbb8356e9@[17.202.35.52]>
In-Reply-To: <p06230929c20bbb8356e9@[17.202.35.52]>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: mmusic@ietf.org, avt@ietf.org
Subject: [AVT] Re: [MMUSIC] linking two streams in SDP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

David,

For forward error correction, I think you can use RFC 4756 (FEC
Semantics)  with RFC 3388 (Media Line Grouping). There might be similar
semantics for scalable coding.

Adam


Dave Singer wrote:
> If I have one stream which carries optional 'repair' data for another
> stream, and I want to send them on two separate multicast groups, or
> two separate streams to an RTSP client, how would I indicate that
> 'this media stream' is the repair data for 'that media stream' in SDP?
>
> I guess this is somewhat like scalable coding, in which I would need
> to say 'this stream' is an enhancement, and builds on 'that stream'.
>
> I have no idea how to write a stream reference in SDP, i.e. how to say
> 'that stream'.  The techniques for scalable coding seem to be confined
> to assigning consecutive port numbers or multicast addresses, neither
> of which seem to apply when RTSP/SDP is used.
>
> Help?

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



