From mailman-bounces@ietf.org  Wed Dec  1 08:58:13 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29649
	for <avt-archive@ietf.org>; Wed, 1 Dec 2004 08:58:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZV58-0000c0-PF
	for avt-archive@ietf.org; Wed, 01 Dec 2004 09:03:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZSf1-0001ek-2N
	for avt-archive@ietf.org; Wed, 01 Dec 2004 06:28:39 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: avt-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.22011.1101898102.3553.mailman@lists.ietf.org>
Date: Wed, 01 Dec 2004 05:48:22 -0500
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

**********************************************************************

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for avt-archive@ietf.org:

List                                     Password // URL
----                                     --------  
avt@ietf.org                             afvueh    
https://www1.ietf.org/mailman/options/avt/avt-archive%40ietf.org


From avt-bounces@ietf.org  Wed Dec  1 12:29:24 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00276
	for <avt-archive@ietf.org>; Wed, 1 Dec 2004 12:29:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZYNW-0005fQ-CR
	for avt-archive@ietf.org; Wed, 01 Dec 2004 12:34:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZXOA-0003MC-RP; Wed, 01 Dec 2004 11:31:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZVXx-0004JE-Fr
	for avt@megatron.ietf.org; Wed, 01 Dec 2004 09:33:33 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03167
	for <avt@ietf.org>; Wed, 1 Dec 2004 09:33:32 -0500 (EST)
Received: from mailrelay.pel.panasonic.de ([194.162.191.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZVdI-0001Gf-6d
	for avt@ietf.org; Wed, 01 Dec 2004 09:39:04 -0500
Received: from localhost ([127.0.0.1]) by MailRelay.PEL.Panasonic.de
	for avt@ietf.org; Wed, 1 Dec 2004 15:36:29 +0100
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
Date: Wed, 1 Dec 2004 15:32:59 +0100
Message-ID: <9D277E44D6EF0942B928C6F0DE99BB3146FC0C@lan-ex-01.panasonic.de>
Thread-Topic: Re: Request for WG Last-Call for
	draft-ietf-avt-rtp-3gpp-timed-text-07.txt 
Thread-Index: AcTXsqguv+0WsQjIQTCZ6ufSlvkf5w==
From: "Rey Jose" <Rey@panasonic.de>
To: "Magnus Westerlund \(KI/EAB\)" <magnus.westerlund@ericsson.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: quoted-printable
Cc: avt@ietf.org
Subject: [AVT] Re: Request for WG Last-Call for
	draft-ietf-avt-rtp-3gpp-timed-text-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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: quoted-printable


Magnus,

Thanks for the comments.  Below, I don't understand the last part,
between "**": is it meant that a wraparound for the timestamp is needed?

"
19. Section 12.3:


        o the Decoding Time to Sample Box (stts): the 24 least
          significant bits of the "sample_delta" are mapped to the
          field SDUR (Text Sample Duration),

I think this is incorrectly stated, I think one should use as many bits
as existing in the mapping to the SDUR value. Please consider that if
one strictly takes the lower 24, values one can't scale in the mapping,
or do ceiling value with the bits one have. Lets assume that one can
only represent number with 3 digits, and SDUR would be 1023, **then one
could send this sample as one with SDUR=3D999 and another with
TS=3DTS_org+999 and SDUR=3D24.**
"

Thanks,

---------------------------------------------
Jose Rey              mailto:rey@panasonic.de
P R D C G - Panasonic R&D Center Germany GmbH
Phone/Fax: +49(0)6103766-134/166
---------------------------------------------=20


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


From avt-bounces@ietf.org  Wed Dec  1 12:39:46 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02081
	for <avt-archive@ietf.org>; Wed, 1 Dec 2004 12:39:46 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZYXN-0006Eq-PH
	for avt-archive@ietf.org; Wed, 01 Dec 2004 12:45:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZXcy-0003es-Oq; Wed, 01 Dec 2004 11:46:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZWQI-0007yB-2K
	for avt@megatron.ietf.org; Wed, 01 Dec 2004 10:29:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11767
	for <avt@ietf.org>; Wed, 1 Dec 2004 10:29:40 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZWVc-0002Qf-3K
	for avt@ietf.org; Wed, 01 Dec 2004 10:35:13 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iB1FTavD009609
	for <avt@ietf.org>; Wed, 1 Dec 2004 16:29:36 +0100 (MET)
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 1 Dec 2004 16:29:34 +0100
Received: from [147.214.34.68] (research-1fd0e1.ki.sw.ericsson.se
	[147.214.34.68]) by esealnt611.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id WHL4DK1A; Wed, 1 Dec 2004 16:29:34 +0100
Message-ID: <41ADE35E.1020709@ericsson.com>
Date: Wed, 01 Dec 2004 16:29:34 +0100
X-Sybari-Trust: 655f92c3 a5e9b67f c9eea391 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: Rey Jose <Rey@panasonic.de>
References: <9D277E44D6EF0942B928C6F0DE99BB3146FC0C@lan-ex-01.panasonic.de>
In-Reply-To: <9D277E44D6EF0942B928C6F0DE99BB3146FC0C@lan-ex-01.panasonic.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Dec 2004 15:29:34.0672 (UTC)
	FILETIME=[8F9FCD00:01C4D7BA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit
Cc: avt@ietf.org
Subject: [AVT] Re: Request for WG Last-Call for
	draft-ietf-avt-rtp-3gpp-timed-text-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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit

Hi Jose,

The comment, is that it is not simply allowed to mask out the lower 24 
bits. Doing a simple masking operation on a 32 bit value that has any 
bits set above would 24 bits would result in that the potentially much 
smaller value is used, rather the complete number. That was what I was 
trying to adress with my example.

Please consider the value 1023, if you have a storage that fits only 3 
digits, any you do a simple masking, then you get the number 23. Which 
is much longer from the real number, than storing 999 would. However to 
get the correct number in this case you would need to use multiple SDUR 
fields that are added together. The for me obvious case of how to solve 
the problem is that one uses multiple copies of the same sample, and 
make the display after each other until the complete time has been 
reached. Thus my example between the "**".

Have I managed to explain the issue sufficiently?

Cheers

Magnus

Rey Jose wrote:

> Magnus,
> 
> Thanks for the comments.  Below, I don't understand the last part, between "**": is it meant that a wraparound for the timestamp is needed?
> 
> "
> 19. Section 12.3:
> 
> 
>         o the Decoding Time to Sample Box (stts): the 24 least
>           significant bits of the "sample_delta" are mapped to the
>           field SDUR (Text Sample Duration),
> 
> I think this is incorrectly stated, I think one should use as many bits as existing in the mapping to the SDUR value. Please consider that if one strictly takes the lower 24, values one can't scale in the mapping, or do ceiling value with the bits one have. Lets assume that one can only represent number with 3 digits, and SDUR would be 1023, **then one could send this sample as one with SDUR=999 and another with TS=TS_org+999 and SDUR=24.**
> "
> 
> Thanks,
> 
> ---------------------------------------------
> Jose Rey              mailto:rey@panasonic.de
> P R D C G - Panasonic R&D Center Germany GmbH
> Phone/Fax: +49(0)6103766-134/166
> --------------------------------------------- 


-- 

Magnus Westerlund

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  Wed Dec  1 12:40:14 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02207
	for <avt-archive@ietf.org>; Wed, 1 Dec 2004 12:40:14 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZYY1-0006HR-Jb
	for avt-archive@ietf.org; Wed, 01 Dec 2004 12:45:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZXiY-0005GE-36; Wed, 01 Dec 2004 11:52:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZWZm-0003QU-7g
	for avt@megatron.ietf.org; Wed, 01 Dec 2004 10:39:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12991
	for <avt@ietf.org>; Wed, 1 Dec 2004 10:39:28 -0500 (EST)
Received: from mailrelay.pel.panasonic.de ([194.162.191.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZWf6-0002ar-Lu
	for avt@ietf.org; Wed, 01 Dec 2004 10:45:01 -0500
Received: from localhost ([127.0.0.1]) by MailRelay.PEL.Panasonic.de;
	Wed, 1 Dec 2004 16:42:24 +0100
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
Date: Wed, 1 Dec 2004 16:38:51 +0100
Message-ID: <9D277E44D6EF0942B928C6F0DE99BB3146FC21@lan-ex-01.panasonic.de>
Thread-Topic: Request for WG Last-Call for
	draft-ietf-avt-rtp-3gpp-timed-text-07.txt
Thread-Index: AcTXupBslMowiY0ESSGIKGXraYXu4gAATaJA
From: "Rey Jose" <Rey@panasonic.de>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Content-Transfer-Encoding: quoted-printable
Cc: avt@ietf.org
Subject: [AVT] RE: Request for WG Last-Call for
	draft-ietf-avt-rtp-3gpp-timed-text-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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: quoted-printable


> Have I managed to explain the issue sufficiently?

Yes, thanks!

Cheers,
Jos=E9=20


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


From avt-bounces@ietf.org  Wed Dec  1 17:54:45 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05702
	for <avt-archive@ietf.org>; Wed, 1 Dec 2004 17:54:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZdSP-0007b2-FO
	for avt-archive@ietf.org; Wed, 01 Dec 2004 18:00:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZcTB-0005qS-2g; Wed, 01 Dec 2004 16:57:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZbt1-0004hl-Oi
	for avt@megatron.ietf.org; Wed, 01 Dec 2004 16:19:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25620
	for <avt@ietf.org>; Wed, 1 Dec 2004 16:19:42 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZbyQ-0004ig-50 for avt@ietf.org; Wed, 01 Dec 2004 16:25:18 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-1.cisco.com with ESMTP; 01 Dec 2004 13:25:35 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iB1LJ72O013470;
	Wed, 1 Dec 2004 13:19:08 -0800 (PST)
Received: from [10.32.254.212] (stealth-10-32-254-212.cisco.com
	[10.32.254.212]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR)
	with SMTP id AZL14779; Wed, 1 Dec 2004 13:26:38 -0800 (PST)
In-Reply-To: <772BCEF88A1DD91191F80011856715F3245B36@zin24exm01.ap.mot.com>
References: <772BCEF88A1DD91191F80011856715F3245B36@zin24exm01.ap.mot.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <9AD3C390-43DE-11D9-BD71-0003935495EC@cisco.com>
Content-Transfer-Encoding: 7bit
From: "David A. McGrew" <mcgrew@cisco.com>
Date: Wed, 1 Dec 2004 13:18:54 -0800
To: Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Content-Transfer-Encoding: 7bit
Cc: karl.norrman@ericsson.com, elisabetta.carrara@ericsson.com,
        milo diurn <srtpdev@hotmail.com>, mbaugher@cisco.com, avt@ietf.org
Subject: [AVT] Re: SRTP_PREFIX_LENGTH
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Content-Transfer-Encoding: 7bit

Srikanth,

On Nov 22, 2004, at 5:01 AM, Vavilapalli Srikanth-A19563 wrote:

> Hi
>
> Another question from my side:
>
> RFC 3711: Section 4.1: Page 19: SRTP_PREFIX_LENGTH is the octet length 
> of
> the key-stream prefix, a non-negative integer, specified by the message
> authentication code in use.
>
> RFC 3711: Section 4.1: Page 20: SRTP_PREFIX_LENGTH, the key-stream 
> prefix is
> indicated by a positive, non-zero value of SRTP_PREFIX_LENGTH.
>
> It looks like the second bullet is restricting zero value for
> SRTP_PREFIX_LENGTH.

No, that was not the intent.  The full quote is:

    The number of octets in the keystream prefix is denoted as
    SRTP_PREFIX_LENGTH.  The keystream prefix is indicated by a positive,
    non-zero value of SRTP_PREFIX_LENGTH.

It should have read something like this:

    The number of octets in the keystream prefix is denoted as
    SRTP_PREFIX_LENGTH.  The *presence of the* keystream prefix is 
indicated
    by a positive, non-zero value of SRTP_PREFIX_LENGTH.


> In that case, how can HMAC-SHA1 use a zero length
> key-stream prefix?
>
> 	RFC 3711: Section 4.2.1: Page 25: With HMAC-SHA1, the
> SRTP_PREFIX_LENGTH SHALL be 0.
>
> Am missing something here? Please clarify this point.

Zero values of the SRTP_PREFIX_LENGTH are permitted.

David

>
> Thanks & Regards
> Srikanth Vavilapalli
>
>
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of 
> David
> A. McGrew
> Sent: Friday, November 19, 2004 9:25 PM
> To: milo diurn
> Cc: karl.norrman@ericsson.com; elisabetta.carrara@ericsson.com;
> mbaugher@cisco.com; avt@ietf.org
> Subject: Re: [AVT] RFC3711: Srtp Parameters for Rx/Tx ?
>
> Hi Milo,
>
> On Nov 19, 2004, at 7:10 AM, milo diurn wrote:
>
>> Karl, and Srtp community,
>>
>> In RFC3711, I do not see any clear way of setting the Srtp parameters
>> (chap 8.2)
>> for both ways of the session:
>> - Transmit : need the Srtp parameters for Encryption (to be sent to
>> the network)
>> - Receive: need the Srtp parameters for Decryption (to be received
>> from the network).
>
> essentially, the parameters are established out-of-band for SRTP.  The
> transmit/receive issue doesn't affect this point; either SRTP endpoint,
> or a third-party device (e.g. a call controller) could set the
> parameters.  In this respect, SRTP is like RTP: it relies on another
> protocol to signal the context information needed to get it going.
> MIKEY and the SDP Security Descriptions are two standards-track ways of
> signaling SRTP.
>
> David
>
>>
>> Could you, please, clarify this point ?
>>
>> Thanks
>>
>> Regards
>>
>> _________________________________________________________________
>> FREE pop-up blocking with the new MSN Toolbar - get it now!
>> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
>>
>
>
> _______________________________________________
> 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 Dec  1 18:27:01 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09817
	for <avt-archive@ietf.org>; Wed, 1 Dec 2004 18:27:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZdxe-00005b-V0
	for avt-archive@ietf.org; Wed, 01 Dec 2004 18:32:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZdnX-0001PD-Fi; Wed, 01 Dec 2004 18:22:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZdkb-0005O1-Iu; Wed, 01 Dec 2004 18:19:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08831;
	Wed, 1 Dec 2004 18:19:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZdq1-0008K5-8C; Wed, 01 Dec 2004 18:24:45 -0500
Received: from apache by megatron.ietf.org with local (Exim 4.32)
	id 1CZdas-0002cb-96; Wed, 01 Dec 2004 18:09:06 -0500
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1CZdas-0002cb-96@megatron.ietf.org>
Date: Wed, 01 Dec 2004 18:09:06 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: avt@ietf.org
Subject: [AVT] Last Call: 'RTP payload Format for H.264 Video' to Proposed
	Standard 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f

The IESG has received a request from the Audio/Video Transport WG to consider 
the following document:

- 'RTP payload Format for H.264 Video '
   <draft-ietf-avt-rtp-h264-11.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2004-12-15.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-h264-11.txt


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


From avt-bounces@ietf.org  Wed Dec  1 23:37:14 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14692
	for <avt-archive@ietf.org>; Wed, 1 Dec 2004 23:37:14 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZinu-0006c3-HM
	for avt-archive@ietf.org; Wed, 01 Dec 2004 23:42:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZi0u-0000sQ-4e; Wed, 01 Dec 2004 22:52:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZhhk-0000tn-Dh
	for avt@megatron.ietf.org; Wed, 01 Dec 2004 22:32:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10649
	for <avt@ietf.org>; Wed, 1 Dec 2004 22:32:26 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZhnB-0005Qf-Gu
	for avt@ietf.org; Wed, 01 Dec 2004 22:38:06 -0500
Received: from zcard303.ca.nortel.com (zcard303.ca.nortel.com [47.129.242.59])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iB23Ved19215; Wed, 1 Dec 2004 22:31:40 -0500 (EST)
Received: from [47.130.17.25] (acart128.ca.nortel.com [47.130.17.25]) by
	zcard303.ca.nortel.com with SMTP (Microsoft Exchange Internet
	Mail Service Version 5.5.2653.13)
	id W14FSWK9; Wed, 1 Dec 2004 22:31:40 -0500
Message-ID: <41AE8C9B.9070807@nortelnetworks.com>
Date: Wed, 01 Dec 2004 22:31:39 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Mundra, Satish" <smundra@ti.com>
Subject: Re: [AVT] comments on draft-ietf-avt-rfc2833bis-06.txt
References: <953541C3AD5E7F4B9A9ED03338BD50435DEB83@dlee2k03.ent.ti.com>
In-Reply-To: <953541C3AD5E7F4B9A9ED03338BD50435DEB83@dlee2k03.ent.ti.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd3fc8e909678b38737fc606dec187f0
Content-Transfer-Encoding: 7bit
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21be852dc93f0971708678c18d38c096
Content-Transfer-Encoding: 7bit

Thank you very much for taking the trouble to review this document.  My responses
are inline, marked with [PTT].

Mundra, Satish wrote:
> 
> I have following comments on this draft:
> 
> 
> 1. Section 2.5.1.2 states: "Timing information is contained in the RTP
> timestamp, allowing precise recovery of inter-event times.  Thus, the sender
> does not need to maintain precise or consistent time intervals between event 
> packets."
> 
> The section refers to "event packets" as those belonging to same event. I think
> a sender needs to maintain consistent interval between event packets as a
> receiver relies on the inter-arrival times to decide how long to extend the
> tone when there are no event packets received. For e.g. if the interval is 
> changed from 10ms to 50ms then a receiver could timeout before the event packet
>  sent at new interval arrives.
> 
[PTT begin]
Good point.  How about if I add the following text to that paragraph:

"However, depending on the playout algorithm used, any increase in time interval 
between sending of event packets may result in gaps in or premature termination of 
tone playout.  As a result, a new event packet for a continuing event SHOULD be 
sent before the receiving end might be expected to complete playout of the 
duration indicated by the packets already sent.  Moreover, the duration reported 
in the initial event packet SHOULD be larger than the expected inter-event packet 
interval, to provide a buffer against packet delays at the receiving end."
[PTT end]

> 
> 2. Section 2.5.1.4 states: "A sender MAY delay setting the "E" bit until
> retransmitting the last 
> packet for a tone, rather than setting the bit on its first transmission. This
> avoids having to wait to detect whether the tone has indeed ended.  Once the
> sender has set the "E" bit for a packet, it MUST continue to set the "E" bit
> for any further retransmissions of that packet."
> 
> How is above different from a sender that does not re-transmit packets with 
> E-bit set? Assuming that receiver is using section2.5.2.2 alogorithm-2 for 
> playout, isn't delaying the setting of E-bit going to cause tone extension by
> 5*inter-arrival periods if the packet with E-bit set was lost ?

[PTT] I think that's just 3*inter-arrival periods, based on the advice in 2.5.2.2. 
  Don't forget that the final packet and its retransmissions will all indicate the 
same total event duration, regardless of the setting of the E-bit.  I agree that 
if the E-bit appears in the first packet reflecting the end of the event and that 
packet is not lost, there will be NO tone extension.  How about if I modify the 
text above to say that:

"A sender MAY delay setting the "E" bit until the first retransmission of the 
final packet of a tone, ..."

This is slightly more precise, and results in the E-bit being set for both 
retransmissions.  If one packet is lost, the worst-case extension is now just 
2xinter-arrival interval.

> 
> 3. Section 2.6.2 states: "This approach allows dumb gateways that do not
> understand this format to function. See also the discussion in section 1."
> 
> This statement should be removed, as gateways first need to negotiate the 
> payloads via out-of-band means, hence the situation where dumb gateway receives
>  payload format that it does not understand should not arise.
> 
[PTT] OK with me.  This is original RFC 2833 text, but perhaps these days we have 
a clearer idea of our architecture.


> 4. Section 2.6.2 states: "The audio redundancy mechanism described in RFC 2198
> [N-2] MAY be used to recover from packet loss across events. For the suggested
>  packet gap of 50 ms, the effective data rate is r times 64 bits (32 bits for
> the redundancy header and 32 bits for the telephone-event payload) plus 8 bits
> for the primary encoding every 50 ms or (r times 
> 1280 + 160) bits/second, where r is the number of redundant events carried in
> each packet. The value of r is an implementation trade- off, with a value of 5
> suggested."
> 
> I think calculations are for "effective increase in data rate" when redundancy 
> is used and not effective data rate. The primary payload of 4 bytes is not 
> included in the above data rate.

[PTT] Agreed.

> 
> 5. Section 5.1 states: "Gateways which send signalling events via RTP MAY send
> both named signals (section named) and the tone representation (section tones)
>  as a single RTP session, using the redundancy mechanism defined in RFC 2198
> [N-2] to interleave the two representations. It is generally
> 
> a good idea to send both, since it allows the receiver to choose the 
> appropriate rendering."
> 
> I think "a single RTP session" above should be changed to "in a single RTP
> packet".

[PTT] Agreed.

> 
> 6. Section 5.2 states: "Events and Audio "The source sends events and encoded
> audio packets (e.g., PCMU or the codec used for speech signals) for the same
> time instant. In that mode, events are treated as redundant encodings for the 
> encoded audio stream."
> 
> As noted in section 2.5.2.2, encoded audio packets preceding the encoded 
> events can cause spurious digits/events and this mode allows the encoded 
> audio packets after the recognition of events and is probably going to increase
> the probability of spurious digits. Section 5.2 also recommends 
> using encoded tones rather than encoded audio for rendering tones. Why not
> disallow this mode?

[PTT] The apparently contradictory advice at the end of 5.2 actually refers to 
receiver behaviour, where the earlier part refers to sender strategy.  I would 
expect the type of situation where you would send both tones and events would be a 
data transmission case such as transmission of V.21 bits, where the receiver is 
going to have to make a transition to audio anyway and the combined encoding 
allows it to pick the point at which it does that.  Another point to consider: by 
an argument you made earlier, combinations like this will occur only with the 
receiver's consent (as a result of out-of-band negotiation).

I'd suggest that maybe I should add a few words to say that where the RTP packet 
contains both audio and event data, the receiver must decide when to transition to 
event playout and when to audio based on consideration of the type of events being 
reported.

> 
> 7. Section 2.6 states: "Section 2.6.2 describes how a summary of earlier events
> MAY be carried in RFC 2198 redundancy payloads.  This is particularly useful
> for sequences of short events, e.g., digits dialed by a modem or autodialer or
> in-band tone signaling sequences (section 3.2 or 3.5)."
> 
> There is no section 3.5 in the new draft. What about redundancy when the 
> digits are not dialed by auto-dialer or modem and inter-digit interval and 
> dialing duration are not small, for e.g., calling card calls ?
> 
[PTT] Thanks for the catch -- the 3.5 reference goes out.  To justify the 
reference to section 3.2 I'll add some mention of data signals.  As to your main 
point, I'm not sure how much extra information redundancy gives you when most of 
it is just earlier reports of the same event.  This does let you catch 'M' and 'E' 
bits that might otherwise be lost, but in between, the latest event report pretty 
well tells you all you need to know.  So redundancy is less useful in the case of 
spread-out events than when they have short duration and follow one another at 
short intervals.
> 
> Regards,
> 
> Satish Mundra
> 
> 
> _______________________________________________ Audio/Video Transport Working
> Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
> 
> 

-- 
Tom Taylor
Carrier VoIP Standards Development
Nortel Networks
Phone +1 613 763 1496  (ESN 393-1496)
E-mail: taylor@nortelnetworks.com

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


From avt-bounces@ietf.org  Thu Dec  2 03:43:29 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20231
	for <avt-archive@ietf.org>; Thu, 2 Dec 2004 03:43:29 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZmeG-0003rf-4E
	for avt-archive@ietf.org; Thu, 02 Dec 2004 03:49:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZmCQ-0008AV-Ft; Thu, 02 Dec 2004 03:20:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZE4s-000162-SL
	for avt@megatron.ietf.org; Tue, 30 Nov 2004 14:54:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26880
	for <avt@ietf.org>; Tue, 30 Nov 2004 14:54:20 -0500 (EST)
Received: from news.ti.com ([192.94.94.33] helo=dragon.ti.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZEA2-0005cK-UI
	for avt@ietf.org; Tue, 30 Nov 2004 14:59:43 -0500
Received: from dlep90.itg.ti.com ([157.170.152.54])
	by dragon.ti.com (8.13.1/8.13.1) with ESMTP id iAUJrkJ5022317
	for <avt@ietf.org>; Tue, 30 Nov 2004 13:53:46 -0600 (CST)
Received: from dlee2k70.ent.ti.com (localhost [127.0.0.1])
	by dlep90.itg.ti.com (8.12.11/8.12.11) with ESMTP id iAUJrjr6000274
	for <avt@ietf.org>; Tue, 30 Nov 2004 13:53:45 -0600 (CST)
Received: from dlee2k03.ent.ti.com ([157.170.152.86]) by dlee2k70.ent.ti.com
	with Microsoft SMTPSVC(5.0.2195.6713); 
	Tue, 30 Nov 2004 13:53:42 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: [AVT] comments on draft-ietf-avt-rfc2833bis-06.txt
Date: Tue, 30 Nov 2004 13:53:42 -0600
Message-ID: <953541C3AD5E7F4B9A9ED03338BD50435DEAC2@dlee2k03.ent.ti.com>
Thread-Topic: [AVT] comments on draft-ietf-avt-rfc2833bis-06.txt
Thread-Index: AcTXFkrVbEZVb5sgSjiQAABi1JxybA==
From: "Mundra, Satish" <smundra@ti.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 30 Nov 2004 19:53:42.0687 (UTC)
	FILETIME=[4B5D3AF0:01C4D716]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 02 Dec 2004 03:20:23 -0500
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Content-Transfer-Encoding: quoted-printable

I have following comments on this draft:


1. Section 2.5.1.2 states:
   "Timing information is contained in the RTP timestamp, allowing=20
   precise recovery of inter-event times.  Thus, the sender does not=20
   need to maintain precise or consistent time intervals between event=20
   packets."=20

The section refers to "event packets" as those belonging to same event.
I=20
think a sender needs to maintain consistent interval between event
packets=20
as a receiver relies on the inter-arrival times to decide how long to
extend=20
the tone when there are no event packets received. For e.g. if the
interval is=20
changed from 10ms to 50ms then a receiver could timeout before the event
packet=20
sent at new interval arrives.=20


2. Section 2.5.1.4 states:
   "A sender MAY delay setting the "E" bit until retransmitting the last

   packet for a tone, rather than setting the bit on its first=20
   transmission. This avoids having to wait to detect whether the tone=20
   has indeed ended.  Once the sender has set the "E" bit for a packet,=20
   it MUST continue to set the "E" bit for any further retransmissions=20
   of that packet."

How is above different from a sender that does not re-transmit packets
with=20
E-bit set? Assuming that receiver is using section2.5.2.2 alogorithm-2
for=20
playout, isn't delaying the setting of E-bit going to cause tone
extension=20
by 5*inter-arrival periods if the packet with E-bit set was lost ?=20

3. Section 2.6.2 states: =20
      "This approach allows dumb gateways that do not understand this

      format to function. See also the discussion in section 1."

This statement should be removed, as gateways first need to negotiate
the=20
payloads via out-of-band means, hence the situation where dumb gateway
receives=20
payload format that it does not understand should not arise.

4. Section 2.6.2 states:
   "The audio redundancy mechanism described in RFC 2198 [N-2] MAY be=20
   used to recover from packet loss across events. For the suggested=20
   packet gap of 50 ms, the effective data rate is r times 64 bits (32=20
   bits for the redundancy header and 32 bits for the telephone-event=20
   payload) plus 8 bits for the primary encoding every 50 ms or (r times

   1280 + 160) bits/second, where r is the number of redundant events=20
   carried in each packet. The value of r is an implementation trade-
   off, with a value of 5 suggested."

I think calculations are for "effective increase in data rate" when
redundancy
is used and not effective data rate. The primary payload of 4 bytes is
not=20
included in the above data rate.

5. Section 5.1 states:
   "Gateways which send signalling events via RTP MAY send both named=20
   signals (section named) and the tone representation (section tones)=20
   as a single RTP session, using the redundancy mechanism defined in=20
   RFC 2198 [N-2] to interleave the two representations. It is generally

   a good idea to send both, since it allows the receiver to choose the=20
   appropriate rendering."=20
  =20
I think "a single RTP session" above should be changed to "in a single
RTP packet".

6. Section 5.2 states:
  "Events and Audio
      "The source sends events and encoded audio packets (e.g., PCMU or=20
      the codec used for speech signals) for the same time instant. In=20
      that mode, events are treated as redundant encodings for the=20
      encoded audio stream."

 =20
As noted in section 2.5.2.2, encoded audio packets preceding the encoded

events can cause spurious digits/events and this mode allows the encoded

audio packets after the recognition of events and is probably going to=20
increase the probability of spurious digits. Section 5.2 also recommends

using encoded tones rather than encoded audio for rendering tones.=20
Why not disallow this mode?

7. Section 2.6 states:=20
      "Section 2.6.2 describes how a summary of earlier events MAY be=20
      carried in RFC 2198 redundancy payloads.  This is particularly=20
      useful for sequences of short events, e.g., digits dialed by a=20
      modem or autodialer or in-band tone signaling sequences (section=20
      3.2 or 3.5)."

There is no section 3.5 in the new draft. What about redundancy when the

digits are not dialed by auto-dialer or modem and inter-digit interval
and=20
dialing duration are not small, for e.g., calling card calls ?=20


Regards,

Satish Mundra


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


From avt-bounces@ietf.org  Thu Dec  2 06:57:40 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05599
	for <avt-archive@ietf.org>; Thu, 2 Dec 2004 06:57:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZpgD-0008Ps-Ss
	for avt-archive@ietf.org; Thu, 02 Dec 2004 07:03:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZpV4-0006tO-5a; Thu, 02 Dec 2004 06:51:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZpFU-0008Ov-77
	for avt@megatron.ietf.org; Thu, 02 Dec 2004 06:35:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03614
	for <avt@ietf.org>; Thu, 2 Dec 2004 06:35:45 -0500 (EST)
Received: from mailrelay.pel.panasonic.de ([194.162.191.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZpL0-0007rQ-4L
	for avt@ietf.org; Thu, 02 Dec 2004 06:41:30 -0500
Received: from localhost ([127.0.0.1]) by MailRelay.PEL.Panasonic.de;
	Thu, 2 Dec 2004 12:38:39 +0100
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
Date: Thu, 2 Dec 2004 12:35:10 +0100
Message-ID: <9D277E44D6EF0942B928C6F0DE99BB3146FC82@lan-ex-01.panasonic.de>
Thread-Topic: Comments on  draft-ietf-avt-rtp-3gpp-timed-text-07.txt
Thread-Index: AcTBDRM7m56bYuLhQ9iTUjkGeUMiPAXSuoaA
From: "Rey Jose" <Rey@panasonic.de>
To: "Colin Perkins" <csp@csperkins.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: quoted-printable
Cc: Jan van der Meer <jan.vandermeer@philips.com>,
        Magnus Westerlund <magnus.westerlund@ericsson.com>, avt@ietf.org,
        Dave Singer <singer@apple.com>
Subject: [AVT] Comments on  draft-ietf-avt-rtp-3gpp-timed-text-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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: quoted-printable

Colin,

Thanks for the comments!

I have a question. You say:

>=20
> "Section 3 notes that the RTP timestamp rate is the value of=20
> the "timescale" parameter in the Media Header Box. Because=20
> the timestamp rate affects the synchronisation accuracy and=20
> RTCP statistics, I think this draft needs to give guidance on=20
> how that parameter is chosen when the file is constructed."
>=20

Part of this concern is addressed in the text describing live-streaming =
with a quote from RTP:

"The resolution of the clock MUST be sufficient for the desired =
synchronization accuracy and for measuring packet arrival jitter (one =
tick per video frame is typically not sufficient)"=20

Now, I want to understand better what's being asked:=20

1.- Regarding the synchronisation of different RTP streams: is this =
actually a matter to be dealt with in the payload format? Isn't this =
rather a matter of the creator of the 3GP file?? I.e. in a 3GP file =
containing several tracks, these should be synchronised anyway so no =
special care is taken for RTP. For the case of a text track sent =
together with other RTP streams (not coming from the same 3GP file), =
would the quote above be enough?=20

2.- Regarding RTCP statistics, for all cases, why is the quote above not =
enough?=20

If this is not sufficient, I'll be glad to add more text on this. Can =
you or someone point me to a document that deals with the same/similar =
problem for getting a better idea of what's asked?=20

Thanks,

---------------------------------------------
Jose Rey              mailto:rey@panasonic.de
P R D C G - Panasonic R&D Center Germany GmbH
Phone/Fax: +49(0)6103766-134/166
---------------------------------------------=20


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


From avt-bounces@ietf.org  Thu Dec  2 07:34:45 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08743
	for <avt-archive@ietf.org>; Thu, 2 Dec 2004 07:34:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZqG4-0000jk-Qn
	for avt-archive@ietf.org; Thu, 02 Dec 2004 07:40:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZpXF-0000i6-3Z; Thu, 02 Dec 2004 06:54:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZpP2-0003nk-EM; Thu, 02 Dec 2004 06:45:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04722;
	Thu, 2 Dec 2004 06:45:37 -0500 (EST)
Received: from tierw.net.avaya.com ([198.152.13.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZpUX-00089c-OX; Thu, 02 Dec 2004 06:51:22 -0500
Received: from tierw.net.avaya.com (localhost [127.0.0.1])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	iB2Bb085023632; Thu, 2 Dec 2004 06:37:00 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	iB2Bav85023592; Thu, 2 Dec 2004 06:36:58 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.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: [MMUSIC] RE: [AVT] RFC 3711 and RTCP
Date: Thu, 2 Dec 2004 13:45:34 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F06E305DA@is0004avexu1.global.avaya.com>
Thread-Topic: [MMUSIC] RE: [AVT] RFC 3711 and RTCP
Thread-Index: AcTX8uJBpR0iZEA+R5KHvoJeoHZTHQAcJywA
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Alan Clark" <alan.d.clark@telchemy.com>,
        "Mark Baugher" <mbaugher@cisco.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: c021adebe99b05433d94f84a85f41df2
Content-Transfer-Encoding: quoted-printable
Cc: rmonmib@ietf.org, mmusic@ietf.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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 81ca0cebdb446e1ff4e2b634791f24a9
Content-Transfer-Encoding: quoted-printable

I would be cautious in saying that in no circumstances the contents of =
an XR payload would be remotely useful to an eavesdropper. We may =
encounter some very security aware environments where even the fact that =
a call happens between two IP phones, its duration, or QoS parameters =
need to be kept confidential. For this reason, while working to provide =
a strong recommendation for RTCP XR packets not to be encrypted, I do =
not believe that we can make this a MUST requirements. As an =
alternative, I suggest to use  RAQMON extensions to report the RTCP XR =
metrics to RAQMON collectors without the security risks that may be of =
concern in some environments.=20

Regards,

Dan



> -----Original Message-----
> From: mmusic-bounces@ietf.org=20
> [mailto:mmusic-bounces@ietf.org]On Behalf Of Alan Clark
> Sent: 01 December, 2004 2:08 PM
> To: Mark Baugher
> Cc: mmusic@ietf.org
> Subject: [MMUSIC] RE: [AVT] RFC 3711 and RTCP
>=20
>=20
> Mark
>=20
> To provide some background to the list - RFC3611 states the=20
> following:-
>=20
>    "Any encryption or filtering of XR report blocks entails a loss of
>    monitoring information to third parties.  For example, a=20
> network that
>    establishes a tunnel to encrypt VoIP Report Blocks denies that
>    information to the service providers traversed by the tunnel.  The
>    service providers cannot then monitor or respond to the quality of
>    the VoIP calls that they carry, potentially creating=20
> problems for the
>    network's users.  As a default, XR packets should not be=20
> encrypted or
>    filtered."
>=20
> I can't conceive of any circumstance in which the contents of=20
> an XR payload
> would be remotely useful to an eavesdropper and hence stating that XR
> payloads should always be left unencrypted would be (at least=20
> in my opinion)
> ok.  If we wanted to make this even more specific we could narrow this
> requirement down to only XR VoIP Metrics payloads to avoid=20
> the situation in
> which some future XR payload may be problematic.
>=20
> The availability of VoIP metrics payloads will be a huge=20
> issue for service
> providers - as we move through 2005 RTCP XR will be a mainstay of VoIP
> performance management and is already a mandatory requirement=20
> within certain
> sectors of the industry.  Making the VoIP metrics payload=20
> unencrypted by
> default may seem a small issue today however it will have=20
> major consequences
> to the industry as SRTP starts to roll out.
>=20
> Regards
>=20
> Alan
>=20
>=20
>=20
> -----Original Message-----
> From: Mark Baugher [mailto:mbaugher@cisco.com]
> Sent: Tuesday, November 30, 2004 6:45 PM
> To: Alan Clark
> Cc: mmusic@ietf.org
> Subject: Re: [AVT] RFC 3711 and RTCP
>=20
>=20
> Alan
>    I am copying MMUSIC (and not cross-posting to AVT) to=20
> further discuss
> a possible change to SDP security descriptions, which has completed WG
> last call.  The change is needed for RFC 3611, and we also discovered
> that
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions
> -07.txt does not address the SRTCP E bit properly. I offered the
> following text in a posting to AVT:
> "As the default behavior when UNENCRYPTED_SRTCP is signaled, all SRTCP
> packets MUST have the E bit set to zero and MUST NOT be encrypted.
> Otherwise, all SRTP packets MUST have the E bit set to one and MUST be
> encrypted by default.  Individual applications MAY override these
> default behaviors in their specifications.  In a session where SRTCP
> packets are encrypted, therefore, applications that use RFC 3611 MAY
> set the E bit to 0 for XR packets as recommended by RFC 3611."
>=20
> One of my co-authors pointed out that the last sentence is=20
> more than an
> editorial change.  We also don't like the fact that an offerer or
> answerer cannot explicitly signal when it wants the XR packet to be
> encrypted or unencrypted.  In other words, if ENCRYPTED_SRTCP is the
> default setting and RFC 3611 is also signaled, it is ambiguous as to
> whether the SRTCP sender will encrypt the XR packet or not.  It's
> solely up to the sender.  If the offerer or answerer want the=20
> XR packet
> to always be encrypted, there is no way to signal that.  Ditto for the
> unencrypted case.
>=20
> I think we need to put the first three sentences of the above-quoted
> paragraph into SDP security descriptions as an editorial change.  I'm
> proposing this to the working group.  I also propose not to=20
> include the
> last sentence.  Instead, we could add a new signaling parameter,
> UNENCRYPTED_XR, which implies that all SRTCP messages are to be
> encrypted except for the XR packets, which will have their E=20
> bit clear,
> of course.
>=20
> This new parameter could be placed in an RFC 3611bis or in a revision
> of draft-ietf-mmusic-sdescriptions-07.txt, which will then need to
> undergo another WG last call.  What do you (all) think about this?
>=20
> Mark
>=20
> On Nov 24, 2004, at 4:18 PM, Mark Baugher wrote:
>=20
> > Alan
> >   As Dave Oran has pointed out, the definition that you want is not
> > supported in the signaling, at present.  The current definition of
> > http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions
> > -07.txt treats SRTCP encryption as either on or off and does not
> > address the problem of setting the E bit in SRTCP packets. =20
> This is a
> > bug that we need to fix.
> >
> >   MMUSIC has finished last call on
> > draft-ietf-mmusic-sdescriptions-07.txt, and the transport ADs have
> > reviewed it.  We'll be making some changes at Jon Peterson's request
> > and post another version in about a week.  This is an opportunity to
> > address the E bit, but the MMUSIC chairs or transport ADs may want
> > another WG last call.  Off the top of my head, I would=20
> offer something
> > like the following.
> >
> > "As the default behavior when UNENCRYPTED_SRTCP is=20
> signaled, all SRTCP
> > packets MUST have the E bit set to zero and MUST NOT be encrypted.
> > Otherwise, all SRTP packets MUST have the E bit set to one=20
> and MUST be
> > encrypted by default.  Individual applications MAY override these
> > default behaviors in their specifications.  In a session where SRTCP
> > packets are encrypted, therefore, applications that use RFC 3611 MAY
> > set the E bit to 0 for XR packets as recommended by RFC 3611."
> >
> > Mark
> >
> > On Nov 24, 2004, at 2:33 PM, Alan Clark wrote:
> >
> >>
> >>
> >> Mark
> >>
> >> We tried to flag this in RFC3611 with the following text in the
> >> "security
> >> considerations" section
> >>
> >>    Any encryption or filtering of XR report blocks entails=20
> a loss of
> >>    monitoring information to third parties.  For example, a network
> >> that
> >>    establishes a tunnel to encrypt VoIP Report Blocks denies that
> >>    information to the service providers traversed by the=20
> tunnel.  The
> >>    service providers cannot then monitor or respond to the=20
> quality of
> >>    the VoIP calls that they carry, potentially creating=20
> problems for
> >> the
> >>    network's users.  As a default, XR packets should not=20
> be encrypted
> >> or
> >>    filtered.
> >>
> >> Could we potentially interpret this as being the=20
> definition of what to
> >> selectively encrypt in the case of the RFC3611 specification?
> >>
> >> Regards
> >>
> >> Alan
> >>
> >>
> >> -----Original Message-----
> >> From: Mark Baugher [mailto:mbaugher@cisco.com]
> >> Sent: Wednesday, November 24, 2004 2:42 PM
> >> To: Alan Clark
> >> Cc: Oren Peleg; Cullen Jennings; avt@ietf.org; David R=20
> Oran; Michael
> >> A.
> >> Ramalho
> >> Subject: Re: [AVT] RFC 3711 and RTCP
> >>
> >>
> >> So, when the sender and receiver agree to encrypt SRTCP, this would
> >> mean
> >> only that some SRTCP messages would be encrypted and the=20
> sender would
> >> decide which ones to encrypt?  My personal opinion is that=20
> this is not
> >> secure because it is unpredictable to the receiver, which=20
> may have a
> >> policy that all messages related to its session be encrypted.
> >>
> >> I can think of a few potential approaches to this problem.
> >>
> >> 1. Let individual SRTCP messages or a bundle of SRTCP messages
> >> be signaled to be unencrypted when SRTCP encryption is used.
> >>
> >> 2. Make a blanket policy that the sender determine what
> >> to selectively encrypt, as you suggest.
> >>
> >> 3. Define the policy of what to selectively encrypt in
> >> the particular specification.  In other words, a document could
> >> re-define the signaling of SRTCP encryption according to its
> >> needs.  The specification of foo, therefore, could define a new
> >> parameter such as foo_ENCRYPTED_SRTCP to be used in place of
> >> ENCRYPTED_SRTCP.  The foo document would define what gets
> >> encrypted and what does not get encrypted as per its needs.
> >>
> >> I commented on #2 already.  I don't like #1 because of its=20
> signaling
> >> complexity.  I like #3 because it limits the complexity to the
> >> specific needs of an application.  #1 would be more efficient than
> >> #3 if lots of applications had their own specific needs for
> >> selective encryption of SRTCP message.  But I don't think this is
> >> the case.
> >>
> >> Mark
> >>
> >> On Nov 24, 2004, at 10:58 AM, Alan Clark wrote:
> >>
> >>>
> >>> If the use of encryption in SRTCP is signalled by an=20
> explicit (E) bit
> >>> in the
> >>> SRTCP header then perhaps the sender could autonomously decide
> >>> whether
> >>> it
> >>> wants to encrypt?  Presumably since the sender is in the best
> >>> position
> >>> to
> >>> decide if the data is sensitive then this would be ok - and the
> >>> receiver is
> >>> able to just look at the E bit and hence recognize that=20
> decryption is
> >>> needed.
> >>>
> >>> Alan
> >>>
> >>> -----Original Message-----
> >>> From: avt-bounces@ietf.org=20
> [mailto:avt-bounces@ietf.org]On Behalf Of
> >>> Mark Baugher
> >>> Sent: Wednesday, November 24, 2004 1:33 PM
> >>> To: David R Oran
> >>> Cc: Cullen Jennings; Oren Peleg; Michael A. Ramalho; Alan Clark;
> >>> avt@ietf.org
> >>> Subject: Re: [AVT] RFC 3711 and RTCP
> >>>
> >>>
> >>>
> >>> On Nov 24, 2004, at 10:05 AM, David R Oran wrote:
> >>>
> >>>>
> >>>> On Nov 24, 2004, at 12:23 PM, Alan Clark wrote:
> >>>>
> >>>>>
> >>>>> Michael
> >>>>>
> >>>>> I don't see why this would be a problem unless you included SDES
> >>>>> and
> >>>>> (SR or
> >>>>> RR or XR) in the same RTCP packet.  SRTP (at least the=20
> protocol) is
> >>>>> apparently able to decided on a packet by packet basis=20
> whether to
> >>>>> encrypt
> >>>>> RTCP - hopefully SRTP implementations also permit this.
> >>>>>
> >>>> Sure, they can do this. But remember offer-answer. How does a
> >>>> receiver
> >>>> communicate such a granular policy to the transmitter?=20
> Right now if
> >>>> can say whether to auth or auth+encrypt RTP, and auth or
> >>>> auth+encrypt
> >>>> RTCP. There's no way to say auth+encrypt SDES but only auth SR/XR
> >>>> etc.
> >>>
> >>> Seems to me that this is a problem with SDP security descriptions.
> >>> That problem might be there because we forgot about the E=20
> bit.  This
> >>> seems very messy for the reason you mention above -=20
> granularity.  I
> >>> don't think that we want to negotiate the encryption=20
> policy for each
> >>> type SDP message, which is a problem with something like=20
> the E bit.
> >>>
> >>> Mark
> >>>>
> >>>>
> >>>>> Logically I'd send SDES on its own at the start of a call to
> >>>>> provide
> >>>>> some
> >>>>> user info, but would not send SR/RR/XR until at least=20
> 8-10 seconds
> >>>>> into the
> >>>>> call as I need some time to gather statistics to report.
> >>>> That's not exactly what the RTP specs say. RTCP timers don't have
> >>>> this
> >>>> kind of policy today. In fact, there are porposals on=20
> the table to
> >>>> use
> >>>> RTCP for early feedback to assess reception quality on=20
> some initial
> >>>> packets - e.g. the RTP-noop proposal. In any event that has no
> >>>> bearing
> >>>> on the present discussion.
> >>>>
> >>>>> After the
> >>>>> start-of-call exchange there would appear to be minimal need to
> >>>>> include
> >>>>> SDES. I'm sure we could construct some scenarios in=20
> which you "may"
> >>>>> need to
> >>>>> include SDES with SR/RR/XR however the vast majority of=20
> cases would
> >>>>> either
> >>>>> need only a single initial exchange or may not need SDES at all.
> >>>>>
> >>>> Any time you change SSRC you potentially need to send SDES.
> >>>> That said, I still don't see what bearing this has on=20
> the discussion
> >>>> about whether we need the complexity of encrypting some=20
> RTCP packets
> >>>> and not others for a single session.
> >>>>
> >>>> It's a tradeoff between extra complexity+less privacy versus
> >>>> allowing
> >>>> snoopers to gather RTCP stats.
> >>>>
> >>>> Dave.
> >>>>
> >>>>> Regards
> >>>>>
> >>>>> Alan
> >>>>>
> >>>>>
> >>>>>
> >>>>> -----Original Message-----
> >>>>> From: Michael A. Ramalho [mailto:mramalho@cisco.com]
> >>>>> Sent: Wednesday, November 24, 2004 9:39 AM
> >>>>> To: Alan Clark
> >>>>> Cc: Oren Peleg; avt@ietf.org
> >>>>> Subject: RE: [AVT] RFC 3711 and RTCP
> >>>>>
> >>>>>
> >>>>> At 07:54 AM 11/24/2004 -0500, Alan Clark wrote:
> >>>>>> Hi Oren
> >>>>>>
> >>>>>> Yes - encryption is intended to provide privacy however this
> >>>>>> relates
> >>>>>> primarily to the voice payloads and to information within RTCP
> >>>>>> that
> >>>>>> may be
> >>>>>> associated with individual users (e.g. SDES).
> >>>>>>
> >>>>>> SR, RR and XR contain only peformance statistics and=20
> there is no
> >>>>>> privacy
> >>>>>> consideration that I can think of related to this type of data.
> >>>>>>
> >>>>>> The message is - encrypt RTP, optionally encrypt RTCP SDES but
> >>>>>> don't
> >>>>> encrypt
> >>>>>> RTCP SR/RR/XR
> >>>>>
> >>>>> Hi Alan,
> >>>>>
> >>>>> I am wondering about implementations utilizing your advise
> >>>>> "optionally
> >>>>> encrypt
> >>>>> RTCP SDES but don't encrypt RTCP SR/RR/XR".
> >>>>>
> >>>>> Is there an easy way to tell SRTP to encrypt RTCP SDES, but not
> >>>>> RTCP
> >>>>> SR/RR/XR? It seems that all the RTCP blocks would otherwise be
> >>>>> highly
> >>>>> related to each other. For example (quote out of RFC 3611):
> >>>>>
> >>>>> "XR packets supplement the existing RTCP packets, and may be
> >>>>> stacked
> >>>>> with
> >>>>> other RTCP packets to form compound RTCP packets [9,=20
> Section 6]."
> >>>>>
> >>>>> Thus, RFC3611 explicitly admits the possibility of (but does not
> >>>>> mandate)
> >>>>> the piggybacking all the RTCP-XR block types.
> >>>>>
> >>>>> RTCP implementations would have to know the SRTP=20
> encryption rules
> >>>>> to
> >>>>> make sure they don't perform piggybacking with SDES ...=20
> but could
> >>>>> allow
> >>>>> (the more bandwidth efficient) piggybacking on the other RTCP-XR
> >>>>> blocks.
> >>>>>
> >>>>> This RTCP/SRTP interaction/dependency seems to add a=20
> burden to both
> >>>>> RTCP and SRTP implementations ... let alone the expressiveness
> >>>>> required
> >>>>> to signal your advise in existing SDP/SRTP mechanisms.
> >>>>>
> >>>>> Are you aware of any implementations that have actually followed
> >>>>> your
> >>>>> advise above? I rather go into this one with our eyes open ...
> >>>>> developers
> >>>>> highly dislike this cross-functional entity dependency=20
> (RTCP & SRTP
> >>>>> along
> >>>>> with expressing it in SDP/SRTP mechanisms).
> >>>>>
> >>>>> Regards,
> >>>>>
> >>>>> Michael Ramalho
> >>>>>
> >>>>>
> >>>>>
> >>>>>> Regards
> >>>>>>
> >>>>>> Alan
> >>>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: Oren Peleg [mailto:OrenP@audiocodes.com]
> >>>>>> Sent: Wednesday, November 24, 2004 7:50 AM
> >>>>>> To: Alan Clark; avt@ietf.org
> >>>>>> Subject: RE: [AVT] RFC 3711 and RTCP
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Isnt encryption is to prevent monitoring from the first place?
> >>>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: avt-bounces@ietf.org=20
> [mailto:avt-bounces@ietf.org] On Behalf
> >>>>>> Of
> >>>>>> Alan Clark
> >>>>>> Sent: Tuesday, November 23, 2004 5:42 PM
> >>>>>> To: avt@ietf.org
> >>>>>> Subject: [AVT] RFC 3711 and RTCP
> >>>>>>
> >>>>>>
> >>>>>>> From the flurry of discussion on RFC3711 it looks as=20
> if there is
> >>>>>> considerable interest in SRTP implementation.  I'd=20
> like to add a
> >>>>>> request
> >>>>>> to
> >>>>>> SRTP implementors with regard to manageability.
> >>>>>>
> >>>>>> RTCP SR, RR and more particularly XR (e.g. VoIP Metrics report
> >>>>>> block)
> >>>>>> contain useful information for network monitoring, and=20
> are often
> >>>>>> used by
> >>>>>> probes and analyzers to support problem diagnosis. =20
> RFC3711 allows
> >>>>>> the
> >>>>>> selective encryption of RTCP payloads and hence I=20
> would strongly
> >>>>>> recomment
> >>>>>> that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR
> >>>>>> payloads
> >>>>>> as
> >>>>>> this
> >>>>>> adversely impacts manageability.
> >>>>>>
> >>>>>> Regards
> >>>>>>
> >>>>>> Alan Clark
> >>>>>> Telchemy
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> Audio/Video Transport Working Group
> >>>>>> avt@ietf.org
> >>>>>> https://www1.ietf.org/mailman/listinfo/avt
> >>>>>>
> >>>>>>=20
> ******************************************************************
> >>>>>> **
> >>>>>> *
> >>>>>> ******
> >>>>> *
> >>>>>> ********************************
> >>>>>> This email and any files transmitted with it are confidential
> >>>>>> material.
> >>>>>> They are intended solely for the use of the designated=20
> individual
> >>>>>> or
> >>>>>> entity
> >>>>>> to whom they are addressed.
> >>>>>> If the reader of this message is not the intended recipient,
> >>>>>> you are hereby notified that any dissemination,use,
> >>>>>> distribution or copying of this communication is strictly
> >>>>>> prohibited
> >>>>>> and
> >>>>> may
> >>>>>> be unlawful.
> >>>>>>
> >>>>>> If you have received this email in error please notify
> >>>>>> postmaster@audiocodes.com and permanently delete the e-mail and
> >>>>>> files.
> >>>>>>
> >>>>>>
> >>>>>>=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
> >>>>>
> >>>> David R. Oran
> >>>> Cisco Fellow
> >>>> Cisco Systems
> >>>> 7 Ladyslipper Lane
> >>>> Acton, MA 01720 USA
> >>>> Tel: +1 978 264 2048
> >>>> Email: oran@cisco.com
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> 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
> >>>
> >>
> >
>=20
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
>=20

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


From avt-bounces@ietf.org  Thu Dec  2 08:22:07 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13695
	for <avt-archive@ietf.org>; Thu, 2 Dec 2004 08:22:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZqzv-0002AR-UV
	for avt-archive@ietf.org; Thu, 02 Dec 2004 08:27:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZqEh-0005o9-84; Thu, 02 Dec 2004 07:39:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZqB1-0001Gs-7y; Thu, 02 Dec 2004 07:35:15 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08832;
	Thu, 2 Dec 2004 07:35:14 -0500 (EST)
Message-Id: <200412021235.HAA08832@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 02 Dec 2004 07:35:13 -0500
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-vmr-wb-06.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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f

--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		: Real-Time Transport Protocol (RTP) Payload Formats for
                          the Variable-Rate Multimode Wideband (VMR-WB) Audio 
                          Codec
	Author(s)	: S. Ahmadi
	Filename	: draft-ietf-avt-rtp-vmr-wb-06.txt
	Pages		: 29
	Date		: 2004-12-1
	
This document specifies a real-time transport protocol (RTP) payload
   format to be used for the Variable-Rate Multimode Wideband (VMR-WB)
   speech codec. The payload format is designed to be able to
   interoperate with existing VMR-WB transport formats on non-IP
   networks. A MIME type registration is included for VMR-WB RTP 
   payload formats.

   VMR-WB is a variable-rate multimode wideband speech codec that has a
   number of operating modes, one of which is interoperable with AMR-WB
   (i.e., RFC 3267) audio codec at certain rates. Therefore, provisions
   have been made in this draft to facilitate and simplify data packet
   exchange between VMR-WB and AMR-WB in the interoperable mode with no
   transcoding function involved.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-vmr-wb-06.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-vmr-wb-06.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-vmr-wb-06.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: <2004-12-2080110.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-vmr-wb-06.txt

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

Content-Type: text/plain
Content-ID: <2004-12-2080110.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org  Thu Dec  2 15:48:51 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28342
	for <avt-archive@ietf.org>; Thu, 2 Dec 2004 15:48:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZxyK-0006gM-6a
	for avt-archive@ietf.org; Thu, 02 Dec 2004 15:54:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZuwU-0005EN-DC; Thu, 02 Dec 2004 12:40:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZrFU-0005Y2-KH
	for avt@megatron.ietf.org; Thu, 02 Dec 2004 08:43:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17882
	for <avt@ietf.org>; Thu, 2 Dec 2004 08:43:54 -0500 (EST)
Received: from mailrelay.pel.panasonic.de ([194.162.191.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZrKz-0003aG-MZ
	for avt@ietf.org; Thu, 02 Dec 2004 08:49:40 -0500
Received: from localhost ([127.0.0.1]) by MailRelay.PEL.Panasonic.de;
	Thu, 2 Dec 2004 14:46:47 +0100
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: [AVT] Request for WG Last-Call for
	draft-ietf-avt-rtp-3gpp-timed-text-07.txt
Date: Thu, 2 Dec 2004 14:43:18 +0100
Message-ID: <9D277E44D6EF0942B928C6F0DE99BB3146FCAF@lan-ex-01.panasonic.de>
Thread-Topic: [AVT] Request for WG Last-Call for
	draft-ietf-avt-rtp-3gpp-timed-text-07.txt
Thread-Index: AcTBDRM7m56bYuLhQ9iTUjkGeUMiPAXZdZfg
From: "Rey Jose" <Rey@panasonic.de>
To: "Colin Perkins" <csp@csperkins.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: quoted-printable
Cc: "Magnus Westerlund \(KI/EAB\)" <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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: quoted-printable

=20
Colin,

> Section 3.1.2 (first paragraph on page 21) states that a=20
> maximum of 64 dynamic SIDX are allowed at any moment, but=20
> allows a range of 0-127. =20
> Suggest either allowing 127 active values, or reducing the=20
> allowable range, or adding an explanatory note to clarify.

This has the following reason: If you allow 127 values, then when a =
reordered packet with a new sample description arrives, it is discarded. =
 E.g. last packet received is SIDX=3D5, thus the only invalid value =
would be SIDX=3D6, e.g. Now a reordered packet arrives with a new =
description, SIDX=3D9. It will be mistakingly discarded, because the =
SIDX=3D9 is marked "valid" at that moment and the valid sample =
descriptions shall not be re-written.  Therefore, a "guard interval" is =
introduced. Agreed it should be rare to use so many sample descriptions =
but nevertheless, a mechanism is provided for that case. As for the =
"guard interval" value, we found 64 as 128/2 simple enough while still =
meeting the expected maximum number of sample descriptions. Besides =
that, there's no other motivation for choosing 64 or other value. I'll =
add a similar explanation if that's fine with you into the Annex.  =
Comments?

Thanks,

Jos=E9





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


From avt-bounces@ietf.org  Thu Dec  2 18:28:38 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14180
	for <avt-archive@ietf.org>; Thu, 2 Dec 2004 18:28:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ca0Sz-0002Pg-I0
	for avt-archive@ietf.org; Thu, 02 Dec 2004 18:34:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZwHx-00089S-6G; Thu, 02 Dec 2004 14:06:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZuMN-00015d-Nv; Thu, 02 Dec 2004 12:03:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09120;
	Thu, 2 Dec 2004 12:03:12 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZuRu-0001A3-11; Thu, 02 Dec 2004 12:09:00 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 02 Dec 2004 09:07:38 -0800
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iB2H2K2O024786;
	Thu, 2 Dec 2004 09:02:21 -0800 (PST)
Received: from [192.168.0.11] (sjc-vpn1-546.cisco.com [10.21.98.34])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id iB2H21Xv018796;
	Thu, 2 Dec 2004 09:02:01 -0800
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F06E305DA@is0004avexu1.global.avaya.com>
References: <AAB4B3D3CF0F454F98272CBE187FDE2F06E305DA@is0004avexu1.global.avaya.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F5A8611E-4483-11D9-8729-000A95DC10F2@cisco.com>
Content-Transfer-Encoding: 7bit
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [MMUSIC] RE: [AVT] RFC 3711 and RTCP
Date: Thu, 2 Dec 2004 09:02:33 -0800
To: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1102006922.172912"; x:"432200"; a:"rsa-sha1"; b:"nofws:20871";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"FKYAMQH+Yu9kofBZSxUSrsv+Ndpb8ztHL5uP38QaHjUXl0UucJ+nzZt4R8t0E"
	"+CvR9/C7sWatboAX0EK8Cno0yJz9Danqehum819o/9I1+bCKTxJis29QZnK6j"
	"56oSAxANlQwu6lSgYTMFchoG8Nr/tAkr2K6meAZJRQ/aVILT8=";
	c:"From: Mark Baugher <mbaugher@cisco.com>";
	c:"Subject: Re: [MMUSIC] RE: [AVT] RFC 3711 and RTCP";
	c:"Date: Thu, 2 Dec 2004 09:02:33 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 6ce9c9805f9fd7f2a8e6eb8268c6b0fc
Content-Transfer-Encoding: 7bit
Cc: rmonmib@ietf.org, avt@ietf.org, Alan Clark <alan.d.clark@telchemy.com>,
        mmusic@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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: fc231bf912a450f71747fa7a4e3e2f5a
Content-Transfer-Encoding: 7bit

Dan
   I think use of the E bit needs to be explicitly signaled the SDP 
security descriptions.  That way, an offerer or answerer can express 
whether it wants to have all SRTCP messages encrypted or allow some to 
be in the clear.  I don't know if we need to call out the specific 
SRTCP messages that may be left in the clear or do make it "general 
purpose."  A general-purpose approach would be to signal that 
ENCRYPTED_SRTP can be overridden for any packet for which the sender 
chooses to clear the E bit.  The general-purpose mechanism might be 
suitable for going into draft-ietf-mmusic-sdescriptions-08.txt.  If we 
want to explicitly signal that the E bit can be clear just for XR 
packets when UNENCRYPTED_SRTCP is set, then I think that belongs in RFC 
3611bis.

Mark
On Dec 2, 2004, at 3:45 AM, Romascanu, Dan ((Dan)) wrote:

> I would be cautious in saying that in no circumstances the contents of 
> an XR payload would be remotely useful to an eavesdropper. We may 
> encounter some very security aware environments where even the fact 
> that a call happens between two IP phones, its duration, or QoS 
> parameters need to be kept confidential. For this reason, while 
> working to provide a strong recommendation for RTCP XR packets not to 
> be encrypted, I do not believe that we can make this a MUST 
> requirements. As an alternative, I suggest to use  RAQMON extensions 
> to report the RTCP XR metrics to RAQMON collectors without the 
> security risks that may be of concern in some environments.
>
> Regards,
>
> Dan
>
>
>
>> -----Original Message-----
>> From: mmusic-bounces@ietf.org
>> [mailto:mmusic-bounces@ietf.org]On Behalf Of Alan Clark
>> Sent: 01 December, 2004 2:08 PM
>> To: Mark Baugher
>> Cc: mmusic@ietf.org
>> Subject: [MMUSIC] RE: [AVT] RFC 3711 and RTCP
>>
>>
>> Mark
>>
>> To provide some background to the list - RFC3611 states the
>> following:-
>>
>>    "Any encryption or filtering of XR report blocks entails a loss of
>>    monitoring information to third parties.  For example, a
>> network that
>>    establishes a tunnel to encrypt VoIP Report Blocks denies that
>>    information to the service providers traversed by the tunnel.  The
>>    service providers cannot then monitor or respond to the quality of
>>    the VoIP calls that they carry, potentially creating
>> problems for the
>>    network's users.  As a default, XR packets should not be
>> encrypted or
>>    filtered."
>>
>> I can't conceive of any circumstance in which the contents of
>> an XR payload
>> would be remotely useful to an eavesdropper and hence stating that XR
>> payloads should always be left unencrypted would be (at least
>> in my opinion)
>> ok.  If we wanted to make this even more specific we could narrow this
>> requirement down to only XR VoIP Metrics payloads to avoid
>> the situation in
>> which some future XR payload may be problematic.
>>
>> The availability of VoIP metrics payloads will be a huge
>> issue for service
>> providers - as we move through 2005 RTCP XR will be a mainstay of VoIP
>> performance management and is already a mandatory requirement
>> within certain
>> sectors of the industry.  Making the VoIP metrics payload
>> unencrypted by
>> default may seem a small issue today however it will have
>> major consequences
>> to the industry as SRTP starts to roll out.
>>
>> Regards
>>
>> Alan
>>
>>
>>
>> -----Original Message-----
>> From: Mark Baugher [mailto:mbaugher@cisco.com]
>> Sent: Tuesday, November 30, 2004 6:45 PM
>> To: Alan Clark
>> Cc: mmusic@ietf.org
>> Subject: Re: [AVT] RFC 3711 and RTCP
>>
>>
>> Alan
>>    I am copying MMUSIC (and not cross-posting to AVT) to
>> further discuss
>> a possible change to SDP security descriptions, which has completed WG
>> last call.  The change is needed for RFC 3611, and we also discovered
>> that
>> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions
>> -07.txt does not address the SRTCP E bit properly. I offered the
>> following text in a posting to AVT:
>> "As the default behavior when UNENCRYPTED_SRTCP is signaled, all SRTCP
>> packets MUST have the E bit set to zero and MUST NOT be encrypted.
>> Otherwise, all SRTP packets MUST have the E bit set to one and MUST be
>> encrypted by default.  Individual applications MAY override these
>> default behaviors in their specifications.  In a session where SRTCP
>> packets are encrypted, therefore, applications that use RFC 3611 MAY
>> set the E bit to 0 for XR packets as recommended by RFC 3611."
>>
>> One of my co-authors pointed out that the last sentence is
>> more than an
>> editorial change.  We also don't like the fact that an offerer or
>> answerer cannot explicitly signal when it wants the XR packet to be
>> encrypted or unencrypted.  In other words, if ENCRYPTED_SRTCP is the
>> default setting and RFC 3611 is also signaled, it is ambiguous as to
>> whether the SRTCP sender will encrypt the XR packet or not.  It's
>> solely up to the sender.  If the offerer or answerer want the
>> XR packet
>> to always be encrypted, there is no way to signal that.  Ditto for the
>> unencrypted case.
>>
>> I think we need to put the first three sentences of the above-quoted
>> paragraph into SDP security descriptions as an editorial change.  I'm
>> proposing this to the working group.  I also propose not to
>> include the
>> last sentence.  Instead, we could add a new signaling parameter,
>> UNENCRYPTED_XR, which implies that all SRTCP messages are to be
>> encrypted except for the XR packets, which will have their E
>> bit clear,
>> of course.
>>
>> This new parameter could be placed in an RFC 3611bis or in a revision
>> of draft-ietf-mmusic-sdescriptions-07.txt, which will then need to
>> undergo another WG last call.  What do you (all) think about this?
>>
>> Mark
>>
>> On Nov 24, 2004, at 4:18 PM, Mark Baugher wrote:
>>
>>> Alan
>>>   As Dave Oran has pointed out, the definition that you want is not
>>> supported in the signaling, at present.  The current definition of
>>> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions
>>> -07.txt treats SRTCP encryption as either on or off and does not
>>> address the problem of setting the E bit in SRTCP packets.
>> This is a
>>> bug that we need to fix.
>>>
>>>   MMUSIC has finished last call on
>>> draft-ietf-mmusic-sdescriptions-07.txt, and the transport ADs have
>>> reviewed it.  We'll be making some changes at Jon Peterson's request
>>> and post another version in about a week.  This is an opportunity to
>>> address the E bit, but the MMUSIC chairs or transport ADs may want
>>> another WG last call.  Off the top of my head, I would
>> offer something
>>> like the following.
>>>
>>> "As the default behavior when UNENCRYPTED_SRTCP is
>> signaled, all SRTCP
>>> packets MUST have the E bit set to zero and MUST NOT be encrypted.
>>> Otherwise, all SRTP packets MUST have the E bit set to one
>> and MUST be
>>> encrypted by default.  Individual applications MAY override these
>>> default behaviors in their specifications.  In a session where SRTCP
>>> packets are encrypted, therefore, applications that use RFC 3611 MAY
>>> set the E bit to 0 for XR packets as recommended by RFC 3611."
>>>
>>> Mark
>>>
>>> On Nov 24, 2004, at 2:33 PM, Alan Clark wrote:
>>>
>>>>
>>>>
>>>> Mark
>>>>
>>>> We tried to flag this in RFC3611 with the following text in the
>>>> "security
>>>> considerations" section
>>>>
>>>>    Any encryption or filtering of XR report blocks entails
>> a loss of
>>>>    monitoring information to third parties.  For example, a network
>>>> that
>>>>    establishes a tunnel to encrypt VoIP Report Blocks denies that
>>>>    information to the service providers traversed by the
>> tunnel.  The
>>>>    service providers cannot then monitor or respond to the
>> quality of
>>>>    the VoIP calls that they carry, potentially creating
>> problems for
>>>> the
>>>>    network's users.  As a default, XR packets should not
>> be encrypted
>>>> or
>>>>    filtered.
>>>>
>>>> Could we potentially interpret this as being the
>> definition of what to
>>>> selectively encrypt in the case of the RFC3611 specification?
>>>>
>>>> Regards
>>>>
>>>> Alan
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Mark Baugher [mailto:mbaugher@cisco.com]
>>>> Sent: Wednesday, November 24, 2004 2:42 PM
>>>> To: Alan Clark
>>>> Cc: Oren Peleg; Cullen Jennings; avt@ietf.org; David R
>> Oran; Michael
>>>> A.
>>>> Ramalho
>>>> Subject: Re: [AVT] RFC 3711 and RTCP
>>>>
>>>>
>>>> So, when the sender and receiver agree to encrypt SRTCP, this would
>>>> mean
>>>> only that some SRTCP messages would be encrypted and the
>> sender would
>>>> decide which ones to encrypt?  My personal opinion is that
>> this is not
>>>> secure because it is unpredictable to the receiver, which
>> may have a
>>>> policy that all messages related to its session be encrypted.
>>>>
>>>> I can think of a few potential approaches to this problem.
>>>>
>>>> 1. Let individual SRTCP messages or a bundle of SRTCP messages
>>>> be signaled to be unencrypted when SRTCP encryption is used.
>>>>
>>>> 2. Make a blanket policy that the sender determine what
>>>> to selectively encrypt, as you suggest.
>>>>
>>>> 3. Define the policy of what to selectively encrypt in
>>>> the particular specification.  In other words, a document could
>>>> re-define the signaling of SRTCP encryption according to its
>>>> needs.  The specification of foo, therefore, could define a new
>>>> parameter such as foo_ENCRYPTED_SRTCP to be used in place of
>>>> ENCRYPTED_SRTCP.  The foo document would define what gets
>>>> encrypted and what does not get encrypted as per its needs.
>>>>
>>>> I commented on #2 already.  I don't like #1 because of its
>> signaling
>>>> complexity.  I like #3 because it limits the complexity to the
>>>> specific needs of an application.  #1 would be more efficient than
>>>> #3 if lots of applications had their own specific needs for
>>>> selective encryption of SRTCP message.  But I don't think this is
>>>> the case.
>>>>
>>>> Mark
>>>>
>>>> On Nov 24, 2004, at 10:58 AM, Alan Clark wrote:
>>>>
>>>>>
>>>>> If the use of encryption in SRTCP is signalled by an
>> explicit (E) bit
>>>>> in the
>>>>> SRTCP header then perhaps the sender could autonomously decide
>>>>> whether
>>>>> it
>>>>> wants to encrypt?  Presumably since the sender is in the best
>>>>> position
>>>>> to
>>>>> decide if the data is sensitive then this would be ok - and the
>>>>> receiver is
>>>>> able to just look at the E bit and hence recognize that
>> decryption is
>>>>> needed.
>>>>>
>>>>> Alan
>>>>>
>>>>> -----Original Message-----
>>>>> From: avt-bounces@ietf.org
>> [mailto:avt-bounces@ietf.org]On Behalf Of
>>>>> Mark Baugher
>>>>> Sent: Wednesday, November 24, 2004 1:33 PM
>>>>> To: David R Oran
>>>>> Cc: Cullen Jennings; Oren Peleg; Michael A. Ramalho; Alan Clark;
>>>>> avt@ietf.org
>>>>> Subject: Re: [AVT] RFC 3711 and RTCP
>>>>>
>>>>>
>>>>>
>>>>> On Nov 24, 2004, at 10:05 AM, David R Oran wrote:
>>>>>
>>>>>>
>>>>>> On Nov 24, 2004, at 12:23 PM, Alan Clark wrote:
>>>>>>
>>>>>>>
>>>>>>> Michael
>>>>>>>
>>>>>>> I don't see why this would be a problem unless you included SDES
>>>>>>> and
>>>>>>> (SR or
>>>>>>> RR or XR) in the same RTCP packet.  SRTP (at least the
>> protocol) is
>>>>>>> apparently able to decided on a packet by packet basis
>> whether to
>>>>>>> encrypt
>>>>>>> RTCP - hopefully SRTP implementations also permit this.
>>>>>>>
>>>>>> Sure, they can do this. But remember offer-answer. How does a
>>>>>> receiver
>>>>>> communicate such a granular policy to the transmitter?
>> Right now if
>>>>>> can say whether to auth or auth+encrypt RTP, and auth or
>>>>>> auth+encrypt
>>>>>> RTCP. There's no way to say auth+encrypt SDES but only auth SR/XR
>>>>>> etc.
>>>>>
>>>>> Seems to me that this is a problem with SDP security descriptions.
>>>>> That problem might be there because we forgot about the E
>> bit.  This
>>>>> seems very messy for the reason you mention above -
>> granularity.  I
>>>>> don't think that we want to negotiate the encryption
>> policy for each
>>>>> type SDP message, which is a problem with something like
>> the E bit.
>>>>>
>>>>> Mark
>>>>>>
>>>>>>
>>>>>>> Logically I'd send SDES on its own at the start of a call to
>>>>>>> provide
>>>>>>> some
>>>>>>> user info, but would not send SR/RR/XR until at least
>> 8-10 seconds
>>>>>>> into the
>>>>>>> call as I need some time to gather statistics to report.
>>>>>> That's not exactly what the RTP specs say. RTCP timers don't have
>>>>>> this
>>>>>> kind of policy today. In fact, there are porposals on
>> the table to
>>>>>> use
>>>>>> RTCP for early feedback to assess reception quality on
>> some initial
>>>>>> packets - e.g. the RTP-noop proposal. In any event that has no
>>>>>> bearing
>>>>>> on the present discussion.
>>>>>>
>>>>>>> After the
>>>>>>> start-of-call exchange there would appear to be minimal need to
>>>>>>> include
>>>>>>> SDES. I'm sure we could construct some scenarios in
>> which you "may"
>>>>>>> need to
>>>>>>> include SDES with SR/RR/XR however the vast majority of
>> cases would
>>>>>>> either
>>>>>>> need only a single initial exchange or may not need SDES at all.
>>>>>>>
>>>>>> Any time you change SSRC you potentially need to send SDES.
>>>>>> That said, I still don't see what bearing this has on
>> the discussion
>>>>>> about whether we need the complexity of encrypting some
>> RTCP packets
>>>>>> and not others for a single session.
>>>>>>
>>>>>> It's a tradeoff between extra complexity+less privacy versus
>>>>>> allowing
>>>>>> snoopers to gather RTCP stats.
>>>>>>
>>>>>> Dave.
>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> Alan
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Michael A. Ramalho [mailto:mramalho@cisco.com]
>>>>>>> Sent: Wednesday, November 24, 2004 9:39 AM
>>>>>>> To: Alan Clark
>>>>>>> Cc: Oren Peleg; avt@ietf.org
>>>>>>> Subject: RE: [AVT] RFC 3711 and RTCP
>>>>>>>
>>>>>>>
>>>>>>> At 07:54 AM 11/24/2004 -0500, Alan Clark wrote:
>>>>>>>> Hi Oren
>>>>>>>>
>>>>>>>> Yes - encryption is intended to provide privacy however this
>>>>>>>> relates
>>>>>>>> primarily to the voice payloads and to information within RTCP
>>>>>>>> that
>>>>>>>> may be
>>>>>>>> associated with individual users (e.g. SDES).
>>>>>>>>
>>>>>>>> SR, RR and XR contain only peformance statistics and
>> there is no
>>>>>>>> privacy
>>>>>>>> consideration that I can think of related to this type of data.
>>>>>>>>
>>>>>>>> The message is - encrypt RTP, optionally encrypt RTCP SDES but
>>>>>>>> don't
>>>>>>> encrypt
>>>>>>>> RTCP SR/RR/XR
>>>>>>>
>>>>>>> Hi Alan,
>>>>>>>
>>>>>>> I am wondering about implementations utilizing your advise
>>>>>>> "optionally
>>>>>>> encrypt
>>>>>>> RTCP SDES but don't encrypt RTCP SR/RR/XR".
>>>>>>>
>>>>>>> Is there an easy way to tell SRTP to encrypt RTCP SDES, but not
>>>>>>> RTCP
>>>>>>> SR/RR/XR? It seems that all the RTCP blocks would otherwise be
>>>>>>> highly
>>>>>>> related to each other. For example (quote out of RFC 3611):
>>>>>>>
>>>>>>> "XR packets supplement the existing RTCP packets, and may be
>>>>>>> stacked
>>>>>>> with
>>>>>>> other RTCP packets to form compound RTCP packets [9,
>> Section 6]."
>>>>>>>
>>>>>>> Thus, RFC3611 explicitly admits the possibility of (but does not
>>>>>>> mandate)
>>>>>>> the piggybacking all the RTCP-XR block types.
>>>>>>>
>>>>>>> RTCP implementations would have to know the SRTP
>> encryption rules
>>>>>>> to
>>>>>>> make sure they don't perform piggybacking with SDES ...
>> but could
>>>>>>> allow
>>>>>>> (the more bandwidth efficient) piggybacking on the other RTCP-XR
>>>>>>> blocks.
>>>>>>>
>>>>>>> This RTCP/SRTP interaction/dependency seems to add a
>> burden to both
>>>>>>> RTCP and SRTP implementations ... let alone the expressiveness
>>>>>>> required
>>>>>>> to signal your advise in existing SDP/SRTP mechanisms.
>>>>>>>
>>>>>>> Are you aware of any implementations that have actually followed
>>>>>>> your
>>>>>>> advise above? I rather go into this one with our eyes open ...
>>>>>>> developers
>>>>>>> highly dislike this cross-functional entity dependency
>> (RTCP & SRTP
>>>>>>> along
>>>>>>> with expressing it in SDP/SRTP mechanisms).
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Michael Ramalho
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Regards
>>>>>>>>
>>>>>>>> Alan
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Oren Peleg [mailto:OrenP@audiocodes.com]
>>>>>>>> Sent: Wednesday, November 24, 2004 7:50 AM
>>>>>>>> To: Alan Clark; avt@ietf.org
>>>>>>>> Subject: RE: [AVT] RFC 3711 and RTCP
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Isnt encryption is to prevent monitoring from the first place?
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: avt-bounces@ietf.org
>> [mailto:avt-bounces@ietf.org] On Behalf
>>>>>>>> Of
>>>>>>>> Alan Clark
>>>>>>>> Sent: Tuesday, November 23, 2004 5:42 PM
>>>>>>>> To: avt@ietf.org
>>>>>>>> Subject: [AVT] RFC 3711 and RTCP
>>>>>>>>
>>>>>>>>
>>>>>>>>> From the flurry of discussion on RFC3711 it looks as
>> if there is
>>>>>>>> considerable interest in SRTP implementation.  I'd
>> like to add a
>>>>>>>> request
>>>>>>>> to
>>>>>>>> SRTP implementors with regard to manageability.
>>>>>>>>
>>>>>>>> RTCP SR, RR and more particularly XR (e.g. VoIP Metrics report
>>>>>>>> block)
>>>>>>>> contain useful information for network monitoring, and
>> are often
>>>>>>>> used by
>>>>>>>> probes and analyzers to support problem diagnosis.
>> RFC3711 allows
>>>>>>>> the
>>>>>>>> selective encryption of RTCP payloads and hence I
>> would strongly
>>>>>>>> recomment
>>>>>>>> that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR
>>>>>>>> payloads
>>>>>>>> as
>>>>>>>> this
>>>>>>>> adversely impacts manageability.
>>>>>>>>
>>>>>>>> Regards
>>>>>>>>
>>>>>>>> Alan Clark
>>>>>>>> Telchemy
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Audio/Video Transport Working Group
>>>>>>>> avt@ietf.org
>>>>>>>> https://www1.ietf.org/mailman/listinfo/avt
>>>>>>>>
>>>>>>>>
>> ******************************************************************
>>>>>>>> **
>>>>>>>> *
>>>>>>>> ******
>>>>>>> *
>>>>>>>> ********************************
>>>>>>>> This email and any files transmitted with it are confidential
>>>>>>>> material.
>>>>>>>> They are intended solely for the use of the designated
>> individual
>>>>>>>> or
>>>>>>>> entity
>>>>>>>> to whom they are addressed.
>>>>>>>> If the reader of this message is not the intended recipient,
>>>>>>>> you are hereby notified that any dissemination,use,
>>>>>>>> distribution or copying of this communication is strictly
>>>>>>>> prohibited
>>>>>>>> and
>>>>>>> may
>>>>>>>> be unlawful.
>>>>>>>>
>>>>>>>> If you have received this email in error please notify
>>>>>>>> postmaster@audiocodes.com and permanently delete the e-mail and
>>>>>>>> files.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>> ******************************************************************
>>>>>>>> **
>>>>>>>> *
>>>>>>>> ******
>>>>>>> *
>>>>>>>> *******************************
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>>>
>>>>>> David R. Oran
>>>>>> Cisco Fellow
>>>>>> Cisco Systems
>>>>>> 7 Ladyslipper Lane
>>>>>> Acton, MA 01720 USA
>>>>>> Tel: +1 978 264 2048
>>>>>> Email: oran@cisco.com
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>>
>>>>
>>>
>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>
> _______________________________________________
> 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 Dec  2 18:35:08 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14888
	for <avt-archive@ietf.org>; Thu, 2 Dec 2004 18:35:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ca0ZG-0002bc-O8
	for avt-archive@ietf.org; Thu, 02 Dec 2004 18:40:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZzv8-00007U-SB; Thu, 02 Dec 2004 17:59:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZv10-00008T-CH; Thu, 02 Dec 2004 12:45:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14382;
	Thu, 2 Dec 2004 12:45:10 -0500 (EST)
Received: from mx.cbeyond.net ([66.180.96.58] helo=mx.cbeyond.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZv6V-0002mA-Vb; Thu, 02 Dec 2004 12:50:58 -0500
Received: from [64.238.103.215] (port=1036 helo=telws116)
	by mx.cbeyond.com with asmtp (Exim 4.34)
	id 1CZv0u-0003iL-FV; Thu, 02 Dec 2004 12:45:08 -0500
From: "Alan Clark" <alan.d.clark@telchemy.com>
To: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>,
        "Mark Baugher" <mbaugher@cisco.com>
Subject: RE: [MMUSIC] RE: [AVT] RFC 3711 and RTCP
Date: Thu, 2 Dec 2004 12:45:07 -0500
Message-ID: <BGEKJNNFCPJKLLMMDMELIEPFFMAA.alan.d.clark@telchemy.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F06E305DA@is0004avexu1.global.avaya.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 778b456acd32f555185589e04d062871
Content-Transfer-Encoding: 7bit
Cc: rmonmib@ietf.org, mmusic@ietf.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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: aec2475b197ed9c8908117d8fbf9ee2e
Content-Transfer-Encoding: 7bit

Dan

I can understand your desire to create a RAQMON-centric reporting system
however the industry needs to keep its options open.  The RTCP XR based VoIP
performance management framework allows metrics to be reported via the media
path, signaling protocols or SNMP, and we need to give the implementor as
much flexibility as possible.  Reporting RTCP XR metrics to a RAQMON
collector is one option that should be available however this would not
address many practical scenarios.

Service providers and network managers make extensive use of probes and
analyzers to monitor key demarc points in the network and diagnose problems.
Encrypting everything can severely limit the functionality of these
mid-network systems and hence make it harder for the network manager to
manage the network.

If we had to trade the number of circumstances in which knowledge of packet
loss/ discard rates etc. were a security concern vs the number of
circumstances under which network managers needed improved tools to diagnose
problems then I'd be surprised if the former was even a minute fraction of
the latter.
It is also distinctly possible that if issues such as the duration of a call
was of concern then the IP endpoints would probably simply use an encrypted
IP tunnel - otherwise a mid-stream observer could examine the RTP stream.

Regards

Alan




-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]On Behalf Of
Romascanu, Dan (Dan)
Sent: Thursday, December 02, 2004 6:46 AM
To: Alan Clark; Mark Baugher
Cc: rmonmib@ietf.org; mmusic@ietf.org; avt@ietf.org
Subject: RE: [MMUSIC] RE: [AVT] RFC 3711 and RTCP


I would be cautious in saying that in no circumstances the contents of an XR
payload would be remotely useful to an eavesdropper. We may encounter some
very security aware environments where even the fact that a call happens
between two IP phones, its duration, or QoS parameters need to be kept
confidential. For this reason, while working to provide a strong
recommendation for RTCP XR packets not to be encrypted, I do not believe
that we can make this a MUST requirements. As an alternative, I suggest to
use  RAQMON extensions to report the RTCP XR metrics to RAQMON collectors
without the security risks that may be of concern in some environments.

Regards,

Dan



> -----Original Message-----
> From: mmusic-bounces@ietf.org
> [mailto:mmusic-bounces@ietf.org]On Behalf Of Alan Clark
> Sent: 01 December, 2004 2:08 PM
> To: Mark Baugher
> Cc: mmusic@ietf.org
> Subject: [MMUSIC] RE: [AVT] RFC 3711 and RTCP
>
>
> Mark
>
> To provide some background to the list - RFC3611 states the
> following:-
>
>    "Any encryption or filtering of XR report blocks entails a loss of
>    monitoring information to third parties.  For example, a
> network that
>    establishes a tunnel to encrypt VoIP Report Blocks denies that
>    information to the service providers traversed by the tunnel.  The
>    service providers cannot then monitor or respond to the quality of
>    the VoIP calls that they carry, potentially creating
> problems for the
>    network's users.  As a default, XR packets should not be
> encrypted or
>    filtered."
>
> I can't conceive of any circumstance in which the contents of
> an XR payload
> would be remotely useful to an eavesdropper and hence stating that XR
> payloads should always be left unencrypted would be (at least
> in my opinion)
> ok.  If we wanted to make this even more specific we could narrow this
> requirement down to only XR VoIP Metrics payloads to avoid
> the situation in
> which some future XR payload may be problematic.
>
> The availability of VoIP metrics payloads will be a huge
> issue for service
> providers - as we move through 2005 RTCP XR will be a mainstay of VoIP
> performance management and is already a mandatory requirement
> within certain
> sectors of the industry.  Making the VoIP metrics payload
> unencrypted by
> default may seem a small issue today however it will have
> major consequences
> to the industry as SRTP starts to roll out.
>
> Regards
>
> Alan
>
>
>
> -----Original Message-----
> From: Mark Baugher [mailto:mbaugher@cisco.com]
> Sent: Tuesday, November 30, 2004 6:45 PM
> To: Alan Clark
> Cc: mmusic@ietf.org
> Subject: Re: [AVT] RFC 3711 and RTCP
>
>
> Alan
>    I am copying MMUSIC (and not cross-posting to AVT) to
> further discuss
> a possible change to SDP security descriptions, which has completed WG
> last call.  The change is needed for RFC 3611, and we also discovered
> that
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions
> -07.txt does not address the SRTCP E bit properly. I offered the
> following text in a posting to AVT:
> "As the default behavior when UNENCRYPTED_SRTCP is signaled, all SRTCP
> packets MUST have the E bit set to zero and MUST NOT be encrypted.
> Otherwise, all SRTP packets MUST have the E bit set to one and MUST be
> encrypted by default.  Individual applications MAY override these
> default behaviors in their specifications.  In a session where SRTCP
> packets are encrypted, therefore, applications that use RFC 3611 MAY
> set the E bit to 0 for XR packets as recommended by RFC 3611."
>
> One of my co-authors pointed out that the last sentence is
> more than an
> editorial change.  We also don't like the fact that an offerer or
> answerer cannot explicitly signal when it wants the XR packet to be
> encrypted or unencrypted.  In other words, if ENCRYPTED_SRTCP is the
> default setting and RFC 3611 is also signaled, it is ambiguous as to
> whether the SRTCP sender will encrypt the XR packet or not.  It's
> solely up to the sender.  If the offerer or answerer want the
> XR packet
> to always be encrypted, there is no way to signal that.  Ditto for the
> unencrypted case.
>
> I think we need to put the first three sentences of the above-quoted
> paragraph into SDP security descriptions as an editorial change.  I'm
> proposing this to the working group.  I also propose not to
> include the
> last sentence.  Instead, we could add a new signaling parameter,
> UNENCRYPTED_XR, which implies that all SRTCP messages are to be
> encrypted except for the XR packets, which will have their E
> bit clear,
> of course.
>
> This new parameter could be placed in an RFC 3611bis or in a revision
> of draft-ietf-mmusic-sdescriptions-07.txt, which will then need to
> undergo another WG last call.  What do you (all) think about this?
>
> Mark
>
> On Nov 24, 2004, at 4:18 PM, Mark Baugher wrote:
>
> > Alan
> >   As Dave Oran has pointed out, the definition that you want is not
> > supported in the signaling, at present.  The current definition of
> > http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions
> > -07.txt treats SRTCP encryption as either on or off and does not
> > address the problem of setting the E bit in SRTCP packets.
> This is a
> > bug that we need to fix.
> >
> >   MMUSIC has finished last call on
> > draft-ietf-mmusic-sdescriptions-07.txt, and the transport ADs have
> > reviewed it.  We'll be making some changes at Jon Peterson's request
> > and post another version in about a week.  This is an opportunity to
> > address the E bit, but the MMUSIC chairs or transport ADs may want
> > another WG last call.  Off the top of my head, I would
> offer something
> > like the following.
> >
> > "As the default behavior when UNENCRYPTED_SRTCP is
> signaled, all SRTCP
> > packets MUST have the E bit set to zero and MUST NOT be encrypted.
> > Otherwise, all SRTP packets MUST have the E bit set to one
> and MUST be
> > encrypted by default.  Individual applications MAY override these
> > default behaviors in their specifications.  In a session where SRTCP
> > packets are encrypted, therefore, applications that use RFC 3611 MAY
> > set the E bit to 0 for XR packets as recommended by RFC 3611."
> >
> > Mark
> >
> > On Nov 24, 2004, at 2:33 PM, Alan Clark wrote:
> >
> >>
> >>
> >> Mark
> >>
> >> We tried to flag this in RFC3611 with the following text in the
> >> "security
> >> considerations" section
> >>
> >>    Any encryption or filtering of XR report blocks entails
> a loss of
> >>    monitoring information to third parties.  For example, a network
> >> that
> >>    establishes a tunnel to encrypt VoIP Report Blocks denies that
> >>    information to the service providers traversed by the
> tunnel.  The
> >>    service providers cannot then monitor or respond to the
> quality of
> >>    the VoIP calls that they carry, potentially creating
> problems for
> >> the
> >>    network's users.  As a default, XR packets should not
> be encrypted
> >> or
> >>    filtered.
> >>
> >> Could we potentially interpret this as being the
> definition of what to
> >> selectively encrypt in the case of the RFC3611 specification?
> >>
> >> Regards
> >>
> >> Alan
> >>
> >>
> >> -----Original Message-----
> >> From: Mark Baugher [mailto:mbaugher@cisco.com]
> >> Sent: Wednesday, November 24, 2004 2:42 PM
> >> To: Alan Clark
> >> Cc: Oren Peleg; Cullen Jennings; avt@ietf.org; David R
> Oran; Michael
> >> A.
> >> Ramalho
> >> Subject: Re: [AVT] RFC 3711 and RTCP
> >>
> >>
> >> So, when the sender and receiver agree to encrypt SRTCP, this would
> >> mean
> >> only that some SRTCP messages would be encrypted and the
> sender would
> >> decide which ones to encrypt?  My personal opinion is that
> this is not
> >> secure because it is unpredictable to the receiver, which
> may have a
> >> policy that all messages related to its session be encrypted.
> >>
> >> I can think of a few potential approaches to this problem.
> >>
> >> 1. Let individual SRTCP messages or a bundle of SRTCP messages
> >> be signaled to be unencrypted when SRTCP encryption is used.
> >>
> >> 2. Make a blanket policy that the sender determine what
> >> to selectively encrypt, as you suggest.
> >>
> >> 3. Define the policy of what to selectively encrypt in
> >> the particular specification.  In other words, a document could
> >> re-define the signaling of SRTCP encryption according to its
> >> needs.  The specification of foo, therefore, could define a new
> >> parameter such as foo_ENCRYPTED_SRTCP to be used in place of
> >> ENCRYPTED_SRTCP.  The foo document would define what gets
> >> encrypted and what does not get encrypted as per its needs.
> >>
> >> I commented on #2 already.  I don't like #1 because of its
> signaling
> >> complexity.  I like #3 because it limits the complexity to the
> >> specific needs of an application.  #1 would be more efficient than
> >> #3 if lots of applications had their own specific needs for
> >> selective encryption of SRTCP message.  But I don't think this is
> >> the case.
> >>
> >> Mark
> >>
> >> On Nov 24, 2004, at 10:58 AM, Alan Clark wrote:
> >>
> >>>
> >>> If the use of encryption in SRTCP is signalled by an
> explicit (E) bit
> >>> in the
> >>> SRTCP header then perhaps the sender could autonomously decide
> >>> whether
> >>> it
> >>> wants to encrypt?  Presumably since the sender is in the best
> >>> position
> >>> to
> >>> decide if the data is sensitive then this would be ok - and the
> >>> receiver is
> >>> able to just look at the E bit and hence recognize that
> decryption is
> >>> needed.
> >>>
> >>> Alan
> >>>
> >>> -----Original Message-----
> >>> From: avt-bounces@ietf.org
> [mailto:avt-bounces@ietf.org]On Behalf Of
> >>> Mark Baugher
> >>> Sent: Wednesday, November 24, 2004 1:33 PM
> >>> To: David R Oran
> >>> Cc: Cullen Jennings; Oren Peleg; Michael A. Ramalho; Alan Clark;
> >>> avt@ietf.org
> >>> Subject: Re: [AVT] RFC 3711 and RTCP
> >>>
> >>>
> >>>
> >>> On Nov 24, 2004, at 10:05 AM, David R Oran wrote:
> >>>
> >>>>
> >>>> On Nov 24, 2004, at 12:23 PM, Alan Clark wrote:
> >>>>
> >>>>>
> >>>>> Michael
> >>>>>
> >>>>> I don't see why this would be a problem unless you included SDES
> >>>>> and
> >>>>> (SR or
> >>>>> RR or XR) in the same RTCP packet.  SRTP (at least the
> protocol) is
> >>>>> apparently able to decided on a packet by packet basis
> whether to
> >>>>> encrypt
> >>>>> RTCP - hopefully SRTP implementations also permit this.
> >>>>>
> >>>> Sure, they can do this. But remember offer-answer. How does a
> >>>> receiver
> >>>> communicate such a granular policy to the transmitter?
> Right now if
> >>>> can say whether to auth or auth+encrypt RTP, and auth or
> >>>> auth+encrypt
> >>>> RTCP. There's no way to say auth+encrypt SDES but only auth SR/XR
> >>>> etc.
> >>>
> >>> Seems to me that this is a problem with SDP security descriptions.
> >>> That problem might be there because we forgot about the E
> bit.  This
> >>> seems very messy for the reason you mention above -
> granularity.  I
> >>> don't think that we want to negotiate the encryption
> policy for each
> >>> type SDP message, which is a problem with something like
> the E bit.
> >>>
> >>> Mark
> >>>>
> >>>>
> >>>>> Logically I'd send SDES on its own at the start of a call to
> >>>>> provide
> >>>>> some
> >>>>> user info, but would not send SR/RR/XR until at least
> 8-10 seconds
> >>>>> into the
> >>>>> call as I need some time to gather statistics to report.
> >>>> That's not exactly what the RTP specs say. RTCP timers don't have
> >>>> this
> >>>> kind of policy today. In fact, there are porposals on
> the table to
> >>>> use
> >>>> RTCP for early feedback to assess reception quality on
> some initial
> >>>> packets - e.g. the RTP-noop proposal. In any event that has no
> >>>> bearing
> >>>> on the present discussion.
> >>>>
> >>>>> After the
> >>>>> start-of-call exchange there would appear to be minimal need to
> >>>>> include
> >>>>> SDES. I'm sure we could construct some scenarios in
> which you "may"
> >>>>> need to
> >>>>> include SDES with SR/RR/XR however the vast majority of
> cases would
> >>>>> either
> >>>>> need only a single initial exchange or may not need SDES at all.
> >>>>>
> >>>> Any time you change SSRC you potentially need to send SDES.
> >>>> That said, I still don't see what bearing this has on
> the discussion
> >>>> about whether we need the complexity of encrypting some
> RTCP packets
> >>>> and not others for a single session.
> >>>>
> >>>> It's a tradeoff between extra complexity+less privacy versus
> >>>> allowing
> >>>> snoopers to gather RTCP stats.
> >>>>
> >>>> Dave.
> >>>>
> >>>>> Regards
> >>>>>
> >>>>> Alan
> >>>>>
> >>>>>
> >>>>>
> >>>>> -----Original Message-----
> >>>>> From: Michael A. Ramalho [mailto:mramalho@cisco.com]
> >>>>> Sent: Wednesday, November 24, 2004 9:39 AM
> >>>>> To: Alan Clark
> >>>>> Cc: Oren Peleg; avt@ietf.org
> >>>>> Subject: RE: [AVT] RFC 3711 and RTCP
> >>>>>
> >>>>>
> >>>>> At 07:54 AM 11/24/2004 -0500, Alan Clark wrote:
> >>>>>> Hi Oren
> >>>>>>
> >>>>>> Yes - encryption is intended to provide privacy however this
> >>>>>> relates
> >>>>>> primarily to the voice payloads and to information within RTCP
> >>>>>> that
> >>>>>> may be
> >>>>>> associated with individual users (e.g. SDES).
> >>>>>>
> >>>>>> SR, RR and XR contain only peformance statistics and
> there is no
> >>>>>> privacy
> >>>>>> consideration that I can think of related to this type of data.
> >>>>>>
> >>>>>> The message is - encrypt RTP, optionally encrypt RTCP SDES but
> >>>>>> don't
> >>>>> encrypt
> >>>>>> RTCP SR/RR/XR
> >>>>>
> >>>>> Hi Alan,
> >>>>>
> >>>>> I am wondering about implementations utilizing your advise
> >>>>> "optionally
> >>>>> encrypt
> >>>>> RTCP SDES but don't encrypt RTCP SR/RR/XR".
> >>>>>
> >>>>> Is there an easy way to tell SRTP to encrypt RTCP SDES, but not
> >>>>> RTCP
> >>>>> SR/RR/XR? It seems that all the RTCP blocks would otherwise be
> >>>>> highly
> >>>>> related to each other. For example (quote out of RFC 3611):
> >>>>>
> >>>>> "XR packets supplement the existing RTCP packets, and may be
> >>>>> stacked
> >>>>> with
> >>>>> other RTCP packets to form compound RTCP packets [9,
> Section 6]."
> >>>>>
> >>>>> Thus, RFC3611 explicitly admits the possibility of (but does not
> >>>>> mandate)
> >>>>> the piggybacking all the RTCP-XR block types.
> >>>>>
> >>>>> RTCP implementations would have to know the SRTP
> encryption rules
> >>>>> to
> >>>>> make sure they don't perform piggybacking with SDES ...
> but could
> >>>>> allow
> >>>>> (the more bandwidth efficient) piggybacking on the other RTCP-XR
> >>>>> blocks.
> >>>>>
> >>>>> This RTCP/SRTP interaction/dependency seems to add a
> burden to both
> >>>>> RTCP and SRTP implementations ... let alone the expressiveness
> >>>>> required
> >>>>> to signal your advise in existing SDP/SRTP mechanisms.
> >>>>>
> >>>>> Are you aware of any implementations that have actually followed
> >>>>> your
> >>>>> advise above? I rather go into this one with our eyes open ...
> >>>>> developers
> >>>>> highly dislike this cross-functional entity dependency
> (RTCP & SRTP
> >>>>> along
> >>>>> with expressing it in SDP/SRTP mechanisms).
> >>>>>
> >>>>> Regards,
> >>>>>
> >>>>> Michael Ramalho
> >>>>>
> >>>>>
> >>>>>
> >>>>>> Regards
> >>>>>>
> >>>>>> Alan
> >>>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: Oren Peleg [mailto:OrenP@audiocodes.com]
> >>>>>> Sent: Wednesday, November 24, 2004 7:50 AM
> >>>>>> To: Alan Clark; avt@ietf.org
> >>>>>> Subject: RE: [AVT] RFC 3711 and RTCP
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Isnt encryption is to prevent monitoring from the first place?
> >>>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: avt-bounces@ietf.org
> [mailto:avt-bounces@ietf.org] On Behalf
> >>>>>> Of
> >>>>>> Alan Clark
> >>>>>> Sent: Tuesday, November 23, 2004 5:42 PM
> >>>>>> To: avt@ietf.org
> >>>>>> Subject: [AVT] RFC 3711 and RTCP
> >>>>>>
> >>>>>>
> >>>>>>> From the flurry of discussion on RFC3711 it looks as
> if there is
> >>>>>> considerable interest in SRTP implementation.  I'd
> like to add a
> >>>>>> request
> >>>>>> to
> >>>>>> SRTP implementors with regard to manageability.
> >>>>>>
> >>>>>> RTCP SR, RR and more particularly XR (e.g. VoIP Metrics report
> >>>>>> block)
> >>>>>> contain useful information for network monitoring, and
> are often
> >>>>>> used by
> >>>>>> probes and analyzers to support problem diagnosis.
> RFC3711 allows
> >>>>>> the
> >>>>>> selective encryption of RTCP payloads and hence I
> would strongly
> >>>>>> recomment
> >>>>>> that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR
> >>>>>> payloads
> >>>>>> as
> >>>>>> this
> >>>>>> adversely impacts manageability.
> >>>>>>
> >>>>>> Regards
> >>>>>>
> >>>>>> Alan Clark
> >>>>>> Telchemy
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> Audio/Video Transport Working Group
> >>>>>> avt@ietf.org
> >>>>>> https://www1.ietf.org/mailman/listinfo/avt
> >>>>>>
> >>>>>>
> ******************************************************************
> >>>>>> **
> >>>>>> *
> >>>>>> ******
> >>>>> *
> >>>>>> ********************************
> >>>>>> This email and any files transmitted with it are confidential
> >>>>>> material.
> >>>>>> They are intended solely for the use of the designated
> individual
> >>>>>> or
> >>>>>> entity
> >>>>>> to whom they are addressed.
> >>>>>> If the reader of this message is not the intended recipient,
> >>>>>> you are hereby notified that any dissemination,use,
> >>>>>> distribution or copying of this communication is strictly
> >>>>>> prohibited
> >>>>>> and
> >>>>> may
> >>>>>> be unlawful.
> >>>>>>
> >>>>>> If you have received this email in error please notify
> >>>>>> postmaster@audiocodes.com and permanently delete the e-mail and
> >>>>>> files.
> >>>>>>
> >>>>>>
> >>>>>>
> ******************************************************************
> >>>>>> **
> >>>>>> *
> >>>>>> ******
> >>>>> *
> >>>>>> *******************************
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> 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
> >>>>>
> >>>> David R. Oran
> >>>> Cisco Fellow
> >>>> Cisco Systems
> >>>> 7 Ladyslipper Lane
> >>>> Acton, MA 01720 USA
> >>>> Tel: +1 978 264 2048
> >>>> Email: oran@cisco.com
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> 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
> >>>
> >>
> >
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
>

_______________________________________________
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 Dec  2 21:15:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27426
	for <avt-archive@ietf.org>; Thu, 2 Dec 2004 21:15:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ca34Y-00064T-Pc
	for avt-archive@ietf.org; Thu, 02 Dec 2004 21:21:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ca0Pi-00044l-2v; Thu, 02 Dec 2004 18:31:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZx7u-0000IR-5F; Thu, 02 Dec 2004 15:00:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22359;
	Thu, 2 Dec 2004 15:00:28 -0500 (EST)
Received: from tiere.net.avaya.com ([198.152.12.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZxDT-0005Ux-Lf; Thu, 02 Dec 2004 15:06:16 -0500
Received: from tiere.net.avaya.com (localhost [127.0.0.1])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	iB2JwQZ4007206; Thu, 2 Dec 2004 14:58:26 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	iB2JukZ4004911; Thu, 2 Dec 2004 14:57:11 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.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: [MMUSIC] RE: [AVT] RFC 3711 and RTCP
Date: Thu, 2 Dec 2004 21:56:53 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F038A9F80@is0004avexu1.global.avaya.com>
Thread-Topic: [MMUSIC] RE: [AVT] RFC 3711 and RTCP
Thread-Index: AcTYmFkvpFEyWw7kRhOYFl5G8vPeJwAD0i9g
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Alan Clark" <alan.d.clark@telchemy.com>,
        "Mark Baugher" <mbaugher@cisco.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7b4956e5f2f9c5fe16a8fbd4ddb538bc
Content-Transfer-Encoding: quoted-printable
Cc: rmonmib@ietf.org, mmusic@ietf.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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 18100d5cbd6ebe12591b0282c337464d
Content-Transfer-Encoding: quoted-printable

Alan,

I believe that we are not in disagreement from a technical perspective. =
I am just suggesting that reporting RTCP XR metrics to a RAQMON =
collector be one of the options that should be available=20

This is not about pushing a RAQMON-centric technology to the industry or =
closing other options. This is about providing another way of =
transporting RTCP XR reports for these situations where the RTCP XR =
probes cannot be deployed . As the need for RTCP encryption will not run =
away completely, at least in some environments, and even the information =
carried by  RTCP XR may be considered confidential in some deployments, =
RAQMON reports carrying RTCP XR information can provide the missing =
functionality.=20

RAQMON Reports will also support the case of the encrypted IP tunnels, =
as well as any combination of media and signaling encryption.

Regards,

Dan



> -----Original Message-----
> From: Alan Clark [mailto:alan.d.clark@telchemy.com]
> Sent: 02 December, 2004 7:45 PM
> To: Romascanu, Dan (Dan); Mark Baugher
> Cc: rmonmib@ietf.org; mmusic@ietf.org; avt@ietf.org
> Subject: RE: [MMUSIC] RE: [AVT] RFC 3711 and RTCP
>=20
>=20
> Dan
>=20
> I can understand your desire to create a RAQMON-centric=20
> reporting system
> however the industry needs to keep its options open.  The=20
> RTCP XR based VoIP
> performance management framework allows metrics to be=20
> reported via the media
> path, signaling protocols or SNMP, and we need to give the=20
> implementor as
> much flexibility as possible.  Reporting RTCP XR metrics to a RAQMON
> collector is one option that should be available however this=20
> would not
> address many practical scenarios.
>=20
> Service providers and network managers make extensive use of=20
> probes and
> analyzers to monitor key demarc points in the network and=20
> diagnose problems.
> Encrypting everything can severely limit the functionality of these
> mid-network systems and hence make it harder for the network=20
> manager to
> manage the network.
>=20
> If we had to trade the number of circumstances in which=20
> knowledge of packet
> loss/ discard rates etc. were a security concern vs the number of
> circumstances under which network managers needed improved=20
> tools to diagnose
> problems then I'd be surprised if the former was even a=20
> minute fraction of
> the latter.
> It is also distinctly possible that if issues such as the=20
> duration of a call
> was of concern then the IP endpoints would probably simply=20
> use an encrypted
> IP tunnel - otherwise a mid-stream observer could examine the=20
> RTP stream.
>=20
> Regards
>=20
> Alan
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]On Behalf Of
> Romascanu, Dan (Dan)
> Sent: Thursday, December 02, 2004 6:46 AM
> To: Alan Clark; Mark Baugher
> Cc: rmonmib@ietf.org; mmusic@ietf.org; avt@ietf.org
> Subject: RE: [MMUSIC] RE: [AVT] RFC 3711 and RTCP
>=20
>=20
> I would be cautious in saying that in no circumstances the=20
> contents of an XR
> payload would be remotely useful to an eavesdropper. We may=20
> encounter some
> very security aware environments where even the fact that a=20
> call happens
> between two IP phones, its duration, or QoS parameters need to be kept
> confidential. For this reason, while working to provide a strong
> recommendation for RTCP XR packets not to be encrypted, I do=20
> not believe
> that we can make this a MUST requirements. As an alternative,=20
> I suggest to
> use  RAQMON extensions to report the RTCP XR metrics to=20
> RAQMON collectors
> without the security risks that may be of concern in some=20
> environments.
>=20
> Regards,
>=20
> Dan
>=20
>=20
>=20
> > -----Original Message-----
> > From: mmusic-bounces@ietf.org
> > [mailto:mmusic-bounces@ietf.org]On Behalf Of Alan Clark
> > Sent: 01 December, 2004 2:08 PM
> > To: Mark Baugher
> > Cc: mmusic@ietf.org
> > Subject: [MMUSIC] RE: [AVT] RFC 3711 and RTCP
> >
> >
> > Mark
> >
> > To provide some background to the list - RFC3611 states the
> > following:-
> >
> >    "Any encryption or filtering of XR report blocks entails=20
> a loss of
> >    monitoring information to third parties.  For example, a
> > network that
> >    establishes a tunnel to encrypt VoIP Report Blocks denies that
> >    information to the service providers traversed by the=20
> tunnel.  The
> >    service providers cannot then monitor or respond to the=20
> quality of
> >    the VoIP calls that they carry, potentially creating
> > problems for the
> >    network's users.  As a default, XR packets should not be
> > encrypted or
> >    filtered."
> >
> > I can't conceive of any circumstance in which the contents of
> > an XR payload
> > would be remotely useful to an eavesdropper and hence=20
> stating that XR
> > payloads should always be left unencrypted would be (at least
> > in my opinion)
> > ok.  If we wanted to make this even more specific we could=20
> narrow this
> > requirement down to only XR VoIP Metrics payloads to avoid
> > the situation in
> > which some future XR payload may be problematic.
> >
> > The availability of VoIP metrics payloads will be a huge
> > issue for service
> > providers - as we move through 2005 RTCP XR will be a=20
> mainstay of VoIP
> > performance management and is already a mandatory requirement
> > within certain
> > sectors of the industry.  Making the VoIP metrics payload
> > unencrypted by
> > default may seem a small issue today however it will have
> > major consequences
> > to the industry as SRTP starts to roll out.
> >
> > Regards
> >
> > Alan
> >
> >
> >
> > -----Original Message-----
> > From: Mark Baugher [mailto:mbaugher@cisco.com]
> > Sent: Tuesday, November 30, 2004 6:45 PM
> > To: Alan Clark
> > Cc: mmusic@ietf.org
> > Subject: Re: [AVT] RFC 3711 and RTCP
> >
> >
> > Alan
> >    I am copying MMUSIC (and not cross-posting to AVT) to
> > further discuss
> > a possible change to SDP security descriptions, which has=20
> completed WG
> > last call.  The change is needed for RFC 3611, and we also=20
> discovered
> > that
> > http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions
> > -07.txt does not address the SRTCP E bit properly. I offered the
> > following text in a posting to AVT:
> > "As the default behavior when UNENCRYPTED_SRTCP is=20
> signaled, all SRTCP
> > packets MUST have the E bit set to zero and MUST NOT be encrypted.
> > Otherwise, all SRTP packets MUST have the E bit set to one=20
> and MUST be
> > encrypted by default.  Individual applications MAY override these
> > default behaviors in their specifications.  In a session where SRTCP
> > packets are encrypted, therefore, applications that use RFC 3611 MAY
> > set the E bit to 0 for XR packets as recommended by RFC 3611."
> >
> > One of my co-authors pointed out that the last sentence is
> > more than an
> > editorial change.  We also don't like the fact that an offerer or
> > answerer cannot explicitly signal when it wants the XR packet to be
> > encrypted or unencrypted.  In other words, if ENCRYPTED_SRTCP is the
> > default setting and RFC 3611 is also signaled, it is ambiguous as to
> > whether the SRTCP sender will encrypt the XR packet or not.  It's
> > solely up to the sender.  If the offerer or answerer want the
> > XR packet
> > to always be encrypted, there is no way to signal that. =20
> Ditto for the
> > unencrypted case.
> >
> > I think we need to put the first three sentences of the above-quoted
> > paragraph into SDP security descriptions as an editorial=20
> change.  I'm
> > proposing this to the working group.  I also propose not to
> > include the
> > last sentence.  Instead, we could add a new signaling parameter,
> > UNENCRYPTED_XR, which implies that all SRTCP messages are to be
> > encrypted except for the XR packets, which will have their E
> > bit clear,
> > of course.
> >
> > This new parameter could be placed in an RFC 3611bis or in=20
> a revision
> > of draft-ietf-mmusic-sdescriptions-07.txt, which will then need to
> > undergo another WG last call.  What do you (all) think about this?
> >
> > Mark
> >
> > On Nov 24, 2004, at 4:18 PM, Mark Baugher wrote:
> >
> > > Alan
> > >   As Dave Oran has pointed out, the definition that you=20
> want is not
> > > supported in the signaling, at present.  The current definition of
> > >=20
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions
> > > -07.txt treats SRTCP encryption as either on or off and does not
> > > address the problem of setting the E bit in SRTCP packets.
> > This is a
> > > bug that we need to fix.
> > >
> > >   MMUSIC has finished last call on
> > > draft-ietf-mmusic-sdescriptions-07.txt, and the transport ADs have
> > > reviewed it.  We'll be making some changes at Jon=20
> Peterson's request
> > > and post another version in about a week.  This is an=20
> opportunity to
> > > address the E bit, but the MMUSIC chairs or transport ADs may want
> > > another WG last call.  Off the top of my head, I would
> > offer something
> > > like the following.
> > >
> > > "As the default behavior when UNENCRYPTED_SRTCP is
> > signaled, all SRTCP
> > > packets MUST have the E bit set to zero and MUST NOT be encrypted.
> > > Otherwise, all SRTP packets MUST have the E bit set to one
> > and MUST be
> > > encrypted by default.  Individual applications MAY override these
> > > default behaviors in their specifications.  In a session=20
> where SRTCP
> > > packets are encrypted, therefore, applications that use=20
> RFC 3611 MAY
> > > set the E bit to 0 for XR packets as recommended by RFC 3611."
> > >
> > > Mark
> > >
> > > On Nov 24, 2004, at 2:33 PM, Alan Clark wrote:
> > >
> > >>
> > >>
> > >> Mark
> > >>
> > >> We tried to flag this in RFC3611 with the following text in the
> > >> "security
> > >> considerations" section
> > >>
> > >>    Any encryption or filtering of XR report blocks entails
> > a loss of
> > >>    monitoring information to third parties.  For=20
> example, a network
> > >> that
> > >>    establishes a tunnel to encrypt VoIP Report Blocks denies that
> > >>    information to the service providers traversed by the
> > tunnel.  The
> > >>    service providers cannot then monitor or respond to the
> > quality of
> > >>    the VoIP calls that they carry, potentially creating
> > problems for
> > >> the
> > >>    network's users.  As a default, XR packets should not
> > be encrypted
> > >> or
> > >>    filtered.
> > >>
> > >> Could we potentially interpret this as being the
> > definition of what to
> > >> selectively encrypt in the case of the RFC3611 specification?
> > >>
> > >> Regards
> > >>
> > >> Alan
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: Mark Baugher [mailto:mbaugher@cisco.com]
> > >> Sent: Wednesday, November 24, 2004 2:42 PM
> > >> To: Alan Clark
> > >> Cc: Oren Peleg; Cullen Jennings; avt@ietf.org; David R
> > Oran; Michael
> > >> A.
> > >> Ramalho
> > >> Subject: Re: [AVT] RFC 3711 and RTCP
> > >>
> > >>
> > >> So, when the sender and receiver agree to encrypt SRTCP,=20
> this would
> > >> mean
> > >> only that some SRTCP messages would be encrypted and the
> > sender would
> > >> decide which ones to encrypt?  My personal opinion is that
> > this is not
> > >> secure because it is unpredictable to the receiver, which
> > may have a
> > >> policy that all messages related to its session be encrypted.
> > >>
> > >> I can think of a few potential approaches to this problem.
> > >>
> > >> 1. Let individual SRTCP messages or a bundle of SRTCP messages
> > >> be signaled to be unencrypted when SRTCP encryption is used.
> > >>
> > >> 2. Make a blanket policy that the sender determine what
> > >> to selectively encrypt, as you suggest.
> > >>
> > >> 3. Define the policy of what to selectively encrypt in
> > >> the particular specification.  In other words, a document could
> > >> re-define the signaling of SRTCP encryption according to its
> > >> needs.  The specification of foo, therefore, could define a new
> > >> parameter such as foo_ENCRYPTED_SRTCP to be used in place of
> > >> ENCRYPTED_SRTCP.  The foo document would define what gets
> > >> encrypted and what does not get encrypted as per its needs.
> > >>
> > >> I commented on #2 already.  I don't like #1 because of its
> > signaling
> > >> complexity.  I like #3 because it limits the complexity to the
> > >> specific needs of an application.  #1 would be more=20
> efficient than
> > >> #3 if lots of applications had their own specific needs for
> > >> selective encryption of SRTCP message.  But I don't think this is
> > >> the case.
> > >>
> > >> Mark
> > >>
> > >> On Nov 24, 2004, at 10:58 AM, Alan Clark wrote:
> > >>
> > >>>
> > >>> If the use of encryption in SRTCP is signalled by an
> > explicit (E) bit
> > >>> in the
> > >>> SRTCP header then perhaps the sender could autonomously decide
> > >>> whether
> > >>> it
> > >>> wants to encrypt?  Presumably since the sender is in the best
> > >>> position
> > >>> to
> > >>> decide if the data is sensitive then this would be ok - and the
> > >>> receiver is
> > >>> able to just look at the E bit and hence recognize that
> > decryption is
> > >>> needed.
> > >>>
> > >>> Alan
> > >>>
> > >>> -----Original Message-----
> > >>> From: avt-bounces@ietf.org
> > [mailto:avt-bounces@ietf.org]On Behalf Of
> > >>> Mark Baugher
> > >>> Sent: Wednesday, November 24, 2004 1:33 PM
> > >>> To: David R Oran
> > >>> Cc: Cullen Jennings; Oren Peleg; Michael A. Ramalho; Alan Clark;
> > >>> avt@ietf.org
> > >>> Subject: Re: [AVT] RFC 3711 and RTCP
> > >>>
> > >>>
> > >>>
> > >>> On Nov 24, 2004, at 10:05 AM, David R Oran wrote:
> > >>>
> > >>>>
> > >>>> On Nov 24, 2004, at 12:23 PM, Alan Clark wrote:
> > >>>>
> > >>>>>
> > >>>>> Michael
> > >>>>>
> > >>>>> I don't see why this would be a problem unless you=20
> included SDES
> > >>>>> and
> > >>>>> (SR or
> > >>>>> RR or XR) in the same RTCP packet.  SRTP (at least the
> > protocol) is
> > >>>>> apparently able to decided on a packet by packet basis
> > whether to
> > >>>>> encrypt
> > >>>>> RTCP - hopefully SRTP implementations also permit this.
> > >>>>>
> > >>>> Sure, they can do this. But remember offer-answer. How does a
> > >>>> receiver
> > >>>> communicate such a granular policy to the transmitter?
> > Right now if
> > >>>> can say whether to auth or auth+encrypt RTP, and auth or
> > >>>> auth+encrypt
> > >>>> RTCP. There's no way to say auth+encrypt SDES but only=20
> auth SR/XR
> > >>>> etc.
> > >>>
> > >>> Seems to me that this is a problem with SDP security=20
> descriptions.
> > >>> That problem might be there because we forgot about the E
> > bit.  This
> > >>> seems very messy for the reason you mention above -
> > granularity.  I
> > >>> don't think that we want to negotiate the encryption
> > policy for each
> > >>> type SDP message, which is a problem with something like
> > the E bit.
> > >>>
> > >>> Mark
> > >>>>
> > >>>>
> > >>>>> Logically I'd send SDES on its own at the start of a call to
> > >>>>> provide
> > >>>>> some
> > >>>>> user info, but would not send SR/RR/XR until at least
> > 8-10 seconds
> > >>>>> into the
> > >>>>> call as I need some time to gather statistics to report.
> > >>>> That's not exactly what the RTP specs say. RTCP timers=20
> don't have
> > >>>> this
> > >>>> kind of policy today. In fact, there are porposals on
> > the table to
> > >>>> use
> > >>>> RTCP for early feedback to assess reception quality on
> > some initial
> > >>>> packets - e.g. the RTP-noop proposal. In any event that has no
> > >>>> bearing
> > >>>> on the present discussion.
> > >>>>
> > >>>>> After the
> > >>>>> start-of-call exchange there would appear to be=20
> minimal need to
> > >>>>> include
> > >>>>> SDES. I'm sure we could construct some scenarios in
> > which you "may"
> > >>>>> need to
> > >>>>> include SDES with SR/RR/XR however the vast majority of
> > cases would
> > >>>>> either
> > >>>>> need only a single initial exchange or may not need=20
> SDES at all.
> > >>>>>
> > >>>> Any time you change SSRC you potentially need to send SDES.
> > >>>> That said, I still don't see what bearing this has on
> > the discussion
> > >>>> about whether we need the complexity of encrypting some
> > RTCP packets
> > >>>> and not others for a single session.
> > >>>>
> > >>>> It's a tradeoff between extra complexity+less privacy versus
> > >>>> allowing
> > >>>> snoopers to gather RTCP stats.
> > >>>>
> > >>>> Dave.
> > >>>>
> > >>>>> Regards
> > >>>>>
> > >>>>> Alan
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> -----Original Message-----
> > >>>>> From: Michael A. Ramalho [mailto:mramalho@cisco.com]
> > >>>>> Sent: Wednesday, November 24, 2004 9:39 AM
> > >>>>> To: Alan Clark
> > >>>>> Cc: Oren Peleg; avt@ietf.org
> > >>>>> Subject: RE: [AVT] RFC 3711 and RTCP
> > >>>>>
> > >>>>>
> > >>>>> At 07:54 AM 11/24/2004 -0500, Alan Clark wrote:
> > >>>>>> Hi Oren
> > >>>>>>
> > >>>>>> Yes - encryption is intended to provide privacy however this
> > >>>>>> relates
> > >>>>>> primarily to the voice payloads and to information=20
> within RTCP
> > >>>>>> that
> > >>>>>> may be
> > >>>>>> associated with individual users (e.g. SDES).
> > >>>>>>
> > >>>>>> SR, RR and XR contain only peformance statistics and
> > there is no
> > >>>>>> privacy
> > >>>>>> consideration that I can think of related to this=20
> type of data.
> > >>>>>>
> > >>>>>> The message is - encrypt RTP, optionally encrypt=20
> RTCP SDES but
> > >>>>>> don't
> > >>>>> encrypt
> > >>>>>> RTCP SR/RR/XR
> > >>>>>
> > >>>>> Hi Alan,
> > >>>>>
> > >>>>> I am wondering about implementations utilizing your advise
> > >>>>> "optionally
> > >>>>> encrypt
> > >>>>> RTCP SDES but don't encrypt RTCP SR/RR/XR".
> > >>>>>
> > >>>>> Is there an easy way to tell SRTP to encrypt RTCP=20
> SDES, but not
> > >>>>> RTCP
> > >>>>> SR/RR/XR? It seems that all the RTCP blocks would otherwise be
> > >>>>> highly
> > >>>>> related to each other. For example (quote out of RFC 3611):
> > >>>>>
> > >>>>> "XR packets supplement the existing RTCP packets, and may be
> > >>>>> stacked
> > >>>>> with
> > >>>>> other RTCP packets to form compound RTCP packets [9,
> > Section 6]."
> > >>>>>
> > >>>>> Thus, RFC3611 explicitly admits the possibility of=20
> (but does not
> > >>>>> mandate)
> > >>>>> the piggybacking all the RTCP-XR block types.
> > >>>>>
> > >>>>> RTCP implementations would have to know the SRTP
> > encryption rules
> > >>>>> to
> > >>>>> make sure they don't perform piggybacking with SDES ...
> > but could
> > >>>>> allow
> > >>>>> (the more bandwidth efficient) piggybacking on the=20
> other RTCP-XR
> > >>>>> blocks.
> > >>>>>
> > >>>>> This RTCP/SRTP interaction/dependency seems to add a
> > burden to both
> > >>>>> RTCP and SRTP implementations ... let alone the expressiveness
> > >>>>> required
> > >>>>> to signal your advise in existing SDP/SRTP mechanisms.
> > >>>>>
> > >>>>> Are you aware of any implementations that have=20
> actually followed
> > >>>>> your
> > >>>>> advise above? I rather go into this one with our eyes open ...
> > >>>>> developers
> > >>>>> highly dislike this cross-functional entity dependency
> > (RTCP & SRTP
> > >>>>> along
> > >>>>> with expressing it in SDP/SRTP mechanisms).
> > >>>>>
> > >>>>> Regards,
> > >>>>>
> > >>>>> Michael Ramalho
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>> Regards
> > >>>>>>
> > >>>>>> Alan
> > >>>>>>
> > >>>>>> -----Original Message-----
> > >>>>>> From: Oren Peleg [mailto:OrenP@audiocodes.com]
> > >>>>>> Sent: Wednesday, November 24, 2004 7:50 AM
> > >>>>>> To: Alan Clark; avt@ietf.org
> > >>>>>> Subject: RE: [AVT] RFC 3711 and RTCP
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> Isnt encryption is to prevent monitoring from the=20
> first place?
> > >>>>>>
> > >>>>>> -----Original Message-----
> > >>>>>> From: avt-bounces@ietf.org
> > [mailto:avt-bounces@ietf.org] On Behalf
> > >>>>>> Of
> > >>>>>> Alan Clark
> > >>>>>> Sent: Tuesday, November 23, 2004 5:42 PM
> > >>>>>> To: avt@ietf.org
> > >>>>>> Subject: [AVT] RFC 3711 and RTCP
> > >>>>>>
> > >>>>>>
> > >>>>>>> From the flurry of discussion on RFC3711 it looks as
> > if there is
> > >>>>>> considerable interest in SRTP implementation.  I'd
> > like to add a
> > >>>>>> request
> > >>>>>> to
> > >>>>>> SRTP implementors with regard to manageability.
> > >>>>>>
> > >>>>>> RTCP SR, RR and more particularly XR (e.g. VoIP=20
> Metrics report
> > >>>>>> block)
> > >>>>>> contain useful information for network monitoring, and
> > are often
> > >>>>>> used by
> > >>>>>> probes and analyzers to support problem diagnosis.
> > RFC3711 allows
> > >>>>>> the
> > >>>>>> selective encryption of RTCP payloads and hence I
> > would strongly
> > >>>>>> recomment
> > >>>>>> that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR
> > >>>>>> payloads
> > >>>>>> as
> > >>>>>> this
> > >>>>>> adversely impacts manageability.
> > >>>>>>
> > >>>>>> Regards
> > >>>>>>
> > >>>>>> Alan Clark
> > >>>>>> Telchemy
> > >>>>>>
> > >>>>>>
> > >>>>>> _______________________________________________
> > >>>>>> Audio/Video Transport Working Group
> > >>>>>> avt@ietf.org
> > >>>>>> https://www1.ietf.org/mailman/listinfo/avt
> > >>>>>>
> > >>>>>>
> > ******************************************************************
> > >>>>>> **
> > >>>>>> *
> > >>>>>> ******
> > >>>>> *
> > >>>>>> ********************************
> > >>>>>> This email and any files transmitted with it are confidential
> > >>>>>> material.
> > >>>>>> They are intended solely for the use of the designated
> > individual
> > >>>>>> or
> > >>>>>> entity
> > >>>>>> to whom they are addressed.
> > >>>>>> If the reader of this message is not the intended recipient,
> > >>>>>> you are hereby notified that any dissemination,use,
> > >>>>>> distribution or copying of this communication is strictly
> > >>>>>> prohibited
> > >>>>>> and
> > >>>>> may
> > >>>>>> be unlawful.
> > >>>>>>
> > >>>>>> If you have received this email in error please notify
> > >>>>>> postmaster@audiocodes.com and permanently delete the=20
> e-mail and
> > >>>>>> files.
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > ******************************************************************
> > >>>>>> **
> > >>>>>> *
> > >>>>>> ******
> > >>>>> *
> > >>>>>> *******************************
> > >>>>>>
> > >>>>>>
> > >>>>>> _______________________________________________
> > >>>>>> 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
> > >>>>>
> > >>>> David R. Oran
> > >>>> Cisco Fellow
> > >>>> Cisco Systems
> > >>>> 7 Ladyslipper Lane
> > >>>> Acton, MA 01720 USA
> > >>>> Tel: +1 978 264 2048
> > >>>> Email: oran@cisco.com
> > >>>>
> > >>>>
> > >>>> _______________________________________________
> > >>>> 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
> > >>>
> > >>
> > >
> >
> >
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mmusic
> >
>=20
> _______________________________________________
> 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


From avt-bounces@ietf.org  Fri Dec  3 08:20:51 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02253
	for <avt-archive@ietf.org>; Fri, 3 Dec 2004 08:20:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaDSH-0002zD-2K
	for avt-archive@ietf.org; Fri, 03 Dec 2004 08:26:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaAqu-00085S-Gs; Fri, 03 Dec 2004 05:39:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ca9Wf-00050z-7T
	for avt@megatron.ietf.org; Fri, 03 Dec 2004 04:14:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14380
	for <avt@ietf.org>; Fri, 3 Dec 2004 04:14:51 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ca9cC-0006d5-S1
	for avt@ietf.org; Fri, 03 Dec 2004 04:20:47 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iB39EfvD018170
	for <avt@ietf.org>; Fri, 3 Dec 2004 10:14:41 +0100 (MET)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 3 Dec 2004 10:14:39 +0100
Received: from [147.214.34.68] (research-1fd0e1.ki.sw.ericsson.se
	[147.214.34.68]) by esealnt612.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id XVCVNGTX; Fri, 3 Dec 2004 10:14:39 +0100
Message-ID: <41B02E7F.8030802@ericsson.com>
Date: Fri, 03 Dec 2004 10:14:39 +0100
X-Sybari-Trust: 8814690c a5e9b67f eeb34d91 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>, John Lazzaro <lazzaro@eecs.berkeley.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Dec 2004 09:14:39.0714 (UTC)
	FILETIME=[84691C20:01C4D918]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
Subject: [AVT] Comment on draft-ietf-avt-rtp-framing-contrans-03.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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit

Hi,

I just glancing at the RTP framing for TCP due to ongoing SIPPING 
discussion. Thus I noticed that the protocol identifier registration 
needs to be extended. I think it would be good to register also 
"TCP/RTP/AVPF".

I know that we have discussed SAVP, but I don't think we discussed AVPF. 
To my understanding using AVPF does not require any extra considerations 
such as would be required for SAVP. What does the WG say?

Cheers

Magnus Westerlund

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 Dec  3 10:01:43 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12454
	for <avt-archive@ietf.org>; Fri, 3 Dec 2004 10:01:43 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaF24-0005Ss-JX
	for avt-archive@ietf.org; Fri, 03 Dec 2004 10:07:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaEac-0004nJ-E6; Fri, 03 Dec 2004 09:39:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaDoV-0006LQ-9q
	for avt@megatron.ietf.org; Fri, 03 Dec 2004 08:49:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04298
	for <avt@ietf.org>; Fri, 3 Dec 2004 08:49:34 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaDuE-0003fz-IL for avt@ietf.org; Fri, 03 Dec 2004 08:55:31 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-3.cisco.com with ESMTP; 03 Dec 2004 06:56:43 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iB3Dmqbt006783;
	Fri, 3 Dec 2004 05:48:52 -0800 (PST)
Received: from [10.32.245.156] (stealth-10-32-245-156.cisco.com
	[10.32.245.156])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id iB3Dm9LT025625;
	Fri, 3 Dec 2004 05:48:12 -0800
In-Reply-To: <41B02E7F.8030802@ericsson.com>
References: <41B02E7F.8030802@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <066B2BF3-4532-11D9-B1B5-000A95C73842@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [AVT] Comment on draft-ietf-avt-rtp-framing-contrans-03.txt
Date: Fri, 3 Dec 2004 08:48:34 -0500
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1102081695.18945"; x:"432200"; a:"rsa-sha1"; b:"nofws:1464";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"asSRzALNmL1L8P4elLE+QhK0cA2Ifgwoijm0wcBsbaFRZ0z4ayZ1dfLFHClHq"
	"b6oyEaZBeFzBwkl22Oj+HkzvJ1wr3hdCgMdZevmh6ZIhPljrl7kY+ev6wSW30"
	"QAEWTyULT16GdVhIVlf5NRppiAVyE130vhz8Ulvtklw1oPy/k=";
	c:"From: David R Oran <oran@cisco.com>";
	c:"Subject: Re: [AVT] Comment on
	draft-ietf-avt-rtp-framing-contrans-03.t" "xt";
	c:"Date: Fri, 3 Dec 2004 08:48:34 -0500"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit


On Dec 3, 2004, at 4:14 AM, Magnus Westerlund wrote:

> Hi,
>
> I just glancing at the RTP framing for TCP due to ongoing SIPPING 
> discussion. Thus I noticed that the protocol identifier registration 
> needs to be extended. I think it would be good to register also 
> "TCP/RTP/AVPF".
>
Works for me.

> I know that we have discussed SAVP, but I don't think we discussed 
> AVPF. To my understanding using AVPF does not require any extra 
> considerations such as would be required for SAVP. What does the WG 
> say?
>
Seems reasonable. While having SAVP registered for TCP would also be 
useful, there's no reason to hold things up. I wonder though, exactly 
what considerations do you think are different for TCP/RTP/SAVP than 
UDP/RTP/SAVP? Interactions of SRTP integrity with attacks on TCP?

Dave.

> Cheers
>
> Magnus Westerlund
>
> 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
>
David R. Oran
Cisco Fellow
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720 USA
Tel: +1 978 264 2048
Email: oran@cisco.com


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


From avt-bounces@ietf.org  Fri Dec  3 10:25:40 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15618
	for <avt-archive@ietf.org>; Fri, 3 Dec 2004 10:25:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaFPG-0005yx-9v
	for avt-archive@ietf.org; Fri, 03 Dec 2004 10:31:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaEuo-0000xA-L7; Fri, 03 Dec 2004 10:00:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaELH-0002VH-5e
	for avt@megatron.ietf.org; Fri, 03 Dec 2004 09:23:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08330
	for <avt@ietf.org>; Fri, 3 Dec 2004 09:23:25 -0500 (EST)
Received: from news.ti.com ([192.94.94.33] helo=dragon.ti.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaER1-0004bn-Fv
	for avt@ietf.org; Fri, 03 Dec 2004 09:29:24 -0500
Received: from dlep90.itg.ti.com ([157.170.152.54])
	by dragon.ti.com (8.13.1/8.13.1) with ESMTP id iB3EMmrY016866;
	Fri, 3 Dec 2004 08:22:49 -0600 (CST)
Received: from dlee2k70.ent.ti.com (localhost [127.0.0.1])
	by dlep90.itg.ti.com (8.12.11/8.12.11) with ESMTP id iB3EMmXu010805;
	Fri, 3 Dec 2004 08:22:48 -0600 (CST)
Received: from dlee2k03.ent.ti.com ([157.170.152.86]) by dlee2k70.ent.ti.com
	with Microsoft SMTPSVC(5.0.2195.6713); 
	Fri, 3 Dec 2004 08:22:48 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.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: [AVT] comments on draft-ietf-avt-rfc2833bis-06.txt
Date: Fri, 3 Dec 2004 08:22:48 -0600
Message-ID: <953541C3AD5E7F4B9A9ED03338BD50435DF3E3@dlee2k03.ent.ti.com>
Thread-Topic: [AVT] comments on draft-ietf-avt-rfc2833bis-06.txt
Thread-Index: AcTYKMAnLF5Bsm67RLKRl6tnVAobiwAfFQew
From: "Mundra, Satish" <smundra@ti.com>
To: "Tom Taylor" <taylor@nortelnetworks.com>
X-OriginalArrivalTime: 03 Dec 2004 14:22:48.0685 (UTC)
	FILETIME=[90B231D0:01C4D943]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48
Content-Transfer-Encoding: quoted-printable
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0e9ebc0cbd700a87c0637ad0e2c91610
Content-Transfer-Encoding: quoted-printable

=20
Hi Tom,

Thanks your for your response to my previous comments/questions.=20
[Sorry about double posting of earlier mail, my subscription id did not
mtach=20
 the id I used for first posting and I forgot to withdraw that when I
did a repost.]

Please see below for some follow up comments/questions.=20


> > 1. Section 2.5.1.2 states: "Timing information is contained=20
.......
> [PTT begin]
> Good point.  How about if I add the following text to that paragraph:
>=20
> "However, depending on the playout algorithm used, any=20
> increase in time interval between sending of event packets=20
> may result in gaps in or premature termination of tone=20
> playout.  As a result, a new event packet for a continuing=20
> event SHOULD be sent before the receiving end might be=20
> expected to complete playout of the duration indicated by the=20
> packets already sent.  Moreover, the duration reported in the=20
> initial event packet SHOULD be larger than the expected=20
> inter-event packet interval, to provide a buffer against=20
> packet delays at the receiving end."
> [PTT end]
>=20
Ok.

> > 2. Section 2.5.1.4 states: "A sender MAY delay setting the "E" bit=20
......
> [PTT] I think that's just 3*inter-arrival periods, based on=20
> the advice in 2.5.2.2.=20
>   Don't forget that the final packet and its retransmissions=20
> will all indicate the same total event duration, regardless=20
> of the setting of the E-bit.  I agree that if the E-bit=20
> appears in the first packet reflecting the end of the event=20
> and that packet is not lost, there will be NO tone extension.=20
>  How about if I modify the text above to say that:
>=20
> "A sender MAY delay setting the "E" bit until the first=20
> retransmission of the final packet of a tone, ..."
>=20
> This is slightly more precise, and results in the E-bit being=20
> set for both retransmissions.  If one packet is lost, the=20
> worst-case extension is now just 2xinter-arrival interval.
>=20

I see that motivation for this change is to avoid sender having to wait
to see=20
if the tone has indeed ended. Does this mean that a sender can send
consecutive=20
packets with same duration "X" and then find out that tone has not
really ended=20
and start incrementing the duration ?=20
If this is the case then, the receiver still has to rely on E-bit, the
above change=20
effectively reduced the number of E-bit retransmissions to two ? I don't
see benefit
of this change. =20

> >=20
> > 3. Section 2.6.2 states: "This approach allows dumb=20
.....=20
> [PTT] OK with me.  This is original RFC 2833 text, but=20
> perhaps these days we have a clearer idea of our architecture.
>=20
Agreed.

> > 4. Section 2.6.2 states: "The audio redundancy mechanism=20
>=20
> [PTT] Agreed.
>=20
OK.

> >=20
> > 5. Section 5.1 states: "Gateways which send signalling=20
>=20
> [PTT] Agreed.
>=20
OK.

> >=20
> > 6. Section 5.2 states: "Events and Audio "The source sends=20
....
> [PTT] The apparently contradictory advice at the end of 5.2=20
> actually refers to=20
> receiver behaviour, where the earlier part refers to sender=20
> strategy.  I would=20
> expect the type of situation where you would send both tones=20
> and events would be a=20
> data transmission case such as transmission of V.21 bits,=20
> where the receiver is=20
> going to have to make a transition to audio anyway and the=20
> combined encoding=20
> allows it to pick the point at which it does that.  Another=20
> point to consider: by=20
> an argument you made earlier, combinations like this will=20
> occur only with the=20
> receiver's consent (as a result of out-of-band negotiation).
>=20
It was not clear that this mode is to be used only if negotiated.
May be some examples of negotiation mechanism to be used or reference=20
to same or an Offer/Answer section in the draft would really help.

> I'd suggest that maybe I should add a few words to say that=20
> where the RTP packet=20
> contains both audio and event data, the receiver must decide=20
[You mean when sender transmits both event data and audio data for=20
same time instant ?]=20

> when to transition to=20
> event playout and when to audio based on consideration of the=20
> type of events being=20
> reported.
>=20

I have another related question on above. Assuming that this mode was
not negotaited, can a receiver use of recetion of audio packets (with
higher seq#)
to conclude that event has ended ? This way a sender can choose between
re-transmissions
Of E-bit packets or switching to audio endcoding and either behavior
would=20
terminate the event.  =20

> >=20
> > 7. Section 2.6 states: "Section 2.6.2 describes how a=20
......
> [PTT] Thanks for the catch -- the 3.5 reference goes out.  To=20
> justify the=20
> reference to section 3.2 I'll add some mention of data=20
> signals.  As to your main=20
> point, I'm not sure how much extra information redundancy=20
> gives you when most of=20
> it is just earlier reports of the same event.  This does let=20
> you catch 'M' and 'E'=20
> bits that might otherwise be lost, but in between, the latest=20
> event report pretty=20
> well tells you all you need to know.  So redundancy is less=20
> useful in the case of=20
> spread-out events than when they have short duration and=20
> follow one another at=20
> short intervals.
> >=20
Consider an example of calling card calls. You would first reach a
IP-IVR host, and=20
then there may be password and 10-12 digit destination number that you
want to reach.=20
I think the manual dialing typically would have inter-digit times that
could be 3-4=20
seconds.=20

Another comment on Section 5.4.2:

The example uses 16383 as offset to represent a named event that started
7.5 seconds earlier.
I believe this topic came up earlier and as per Colin Perkins "I don't
think this is appropriate,=20
since it overloads the semantics of the RTP timestamp.".
The new draft does not define named event code for ringback, so I am not
sure if the=20
example should use that. =20


Thanks and regards,

Satish Mundra =20


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


From avt-bounces@ietf.org  Fri Dec  3 14:21:39 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24172
	for <avt-archive@ietf.org>; Fri, 3 Dec 2004 14:21:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaJ5e-00011h-N7
	for avt-archive@ietf.org; Fri, 03 Dec 2004 14:27:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaIMO-0002K0-57; Fri, 03 Dec 2004 13:40:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaFz1-0005Je-5b
	for avt@megatron.ietf.org; Fri, 03 Dec 2004 11:08:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20302
	for <avt@ietf.org>; Fri, 3 Dec 2004 11:08:33 -0500 (EST)
Received: from dns.packetdesign.com ([65.192.41.10]
	helo=mailman.packetdesign.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaG4l-0007AN-I2
	for avt@ietf.org; Fri, 03 Dec 2004 11:14:32 -0500
Received: from packetdesign.com (main-fw-eth1.packetdesign.com [192.168.0.254])
	by mailman.packetdesign.com (8.12.8/8.12.8) with ESMTP id
	iB3G7ICJ007332; Fri, 3 Dec 2004 08:07:18 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Fri, 3 Dec 2004 08:07:17 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Re: [AVT] Comment on draft-ietf-avt-rtp-framing-contrans-03.txt
In-Reply-To: <41B02E7F.8030802@ericsson.com>
Message-ID: <20041203080421.S11590@oak.packetdesign.com>
References: <41B02E7F.8030802@ericsson.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: John Lazzaro <lazzaro@eecs.berkeley.edu>, 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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906

On Fri, 3 Dec 2004, Magnus Westerlund wrote:

> I just glancing at the RTP framing for TCP due to ongoing SIPPING
> discussion. Thus I noticed that the protocol identifier registration
> needs to be extended. I think it would be good to register also
> "TCP/RTP/AVPF".

How would AVPF be used with TCP?  One of the primary applications for
AVPF with UDP is retransmission, but that is not applicable to TCP.

> I know that we have discussed SAVP, but I don't think we discussed AVPF.
> To my understanding using AVPF does not require any extra considerations
> such as would be required for SAVP. What does the WG say?

AVPF is about timing rules for sending RTCP.  When transmitting over
TCP, one cannot strictly control when packets are sent.

                                                        -- Steve

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


From avt-bounces@ietf.org  Fri Dec  3 14:27:21 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24783
	for <avt-archive@ietf.org>; Fri, 3 Dec 2004 14:27:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaJAw-0001CH-8F
	for avt-archive@ietf.org; Fri, 03 Dec 2004 14:33:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaIMZ-0002Zo-TK; Fri, 03 Dec 2004 13:41:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaG96-0006m9-RO
	for avt@megatron.ietf.org; Fri, 03 Dec 2004 11:19:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21274
	for <avt@ietf.org>; Fri, 3 Dec 2004 11:18:58 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaGEh-0007Uv-Eg
	for avt@ietf.org; Fri, 03 Dec 2004 11:24:58 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iB3GImvD006429
	for <avt@ietf.org>; Fri, 3 Dec 2004 17:18:48 +0100 (MET)
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 3 Dec 2004 17:18:46 +0100
Received: from [147.214.34.68] (research-1fd0e1.ki.sw.ericsson.se
	[147.214.34.68]) by esealnt611.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id WHL449B1; Fri, 3 Dec 2004 17:18:46 +0100
Message-ID: <41B091E6.7070901@ericsson.com>
Date: Fri, 03 Dec 2004 17:18:46 +0100
X-Sybari-Trust: 89a62fa5 a5e9b67f eeb34d91 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: Stephen Casner <casner@acm.org>
Subject: Re: [AVT] Comment on draft-ietf-avt-rtp-framing-contrans-03.txt
References: <20041203080421.S11590@oak.packetdesign.com>
In-Reply-To: <20041203080421.S11590@oak.packetdesign.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Dec 2004 16:18:46.0887 (UTC)
	FILETIME=[C41B8F70:01C4D953]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
Cc: John Lazzaro <lazzaro@eecs.berkeley.edu>, 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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit

Hi Steve,

Stephen Casner wrote:
> On Fri, 3 Dec 2004, Magnus Westerlund wrote:
> 
>  > I just glancing at the RTP framing for TCP due to ongoing SIPPING
>  > discussion. Thus I noticed that the protocol identifier registration
>  > needs to be extended. I think it would be good to register also
>  > "TCP/RTP/AVPF".
> 
> How would AVPF be used with TCP?  One of the primary applications for
> AVPF with UDP is retransmission, but that is not applicable to TCP.

There are also other feedback reports that can be included in RTCP. The 
reason I think that one should be able to indicate AVPF, is the case of 
a media relay, like the XCON focus. In that case, one participants may 
be required to join a session using TCP, for example due to NAT 
traversal. In that case the other participants will use AVPF get 
advantages of it. Thus there are cases where the usage of AVPF feedback 
and timing may be forwarded over the TCP/RTP connection.
> 
>  > I know that we have discussed SAVP, but I don't think we discussed AVPF.
>  > To my understanding using AVPF does not require any extra considerations
>  > such as would be required for SAVP. What does the WG say?
> 
> AVPF is about timing rules for sending RTCP.  When transmitting over
> TCP, one cannot strictly control when packets are sent.
> 

Assuming that you have sufficient bandwidth for sending packets 
immediately the rules are still useful in scenarios like the above one I 
  described.

Cheers

Magnus Westerlund

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 Dec  3 17:16:21 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10860
	for <avt-archive@ietf.org>; Fri, 3 Dec 2004 17:16:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaLol-0006Sv-AM
	for avt-archive@ietf.org; Fri, 03 Dec 2004 17:22:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaKx6-0002tO-Kz; Fri, 03 Dec 2004 16:26:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaKYW-0003UR-Hn
	for avt@megatron.ietf.org; Fri, 03 Dec 2004 16:01:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06273
	for <avt@ietf.org>; Fri, 3 Dec 2004 16:01:30 -0500 (EST)
Received: from relay0.eecs.berkeley.edu ([169.229.60.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaKeJ-0004rp-IX
	for avt@ietf.org; Fri, 03 Dec 2004 16:07:33 -0500
Received: from gateway2.EECS (gateway2.EECS.Berkeley.EDU [169.229.60.39])
	by relay0.EECS.Berkeley.EDU (8.13.1/8.12.10) with ESMTP id
	iB3L1TcF011989
	for <avt@ietf.org>; Fri, 3 Dec 2004 13:01:29 -0800 (PST)
Received: from [128.32.34.73] (dhcp-34-73.CS.Berkeley.EDU [128.32.34.73])
	by gateway2.EECS.Berkeley.EDU
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTPSA id <0I85007YCZQHCL@gateway2.EECS.Berkeley.EDU> for
	avt@ietf.org; Fri, 03 Dec 2004 13:01:29 -0800 (PST)
Date: Fri, 03 Dec 2004 13:01:28 -0800
From: lazzaro <lazzaro@eecs.berkeley.edu>
In-reply-to: <41B02E7F.8030802@ericsson.com>
To: IETF AVT WG <avt@ietf.org>
Message-id: <80362B0E-456E-11D9-AE6A-00039372C384@eecs.berkeley.edu>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; charset=US-ASCII; format=flowed
Content-transfer-encoding: 7BIT
References: <41B02E7F.8030802@ericsson.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7BIT
Subject: [AVT] Re: Comment on draft-ietf-avt-rtp-framing-contrans-03.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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7BIT


On Dec 3, 2004, at 1:14 AM, Magnus Westerlund wrote:
> I just glancing at the RTP framing for TCP due to ongoing SIPPING 
> discussion. Thus I noticed that the protocol identifier registration 
> needs to be extended. I think it would be good to register also 
> "TCP/RTP/AVPF".

> I know that we have discussed SAVP, but I don't think we discussed 
> AVPF. To my understanding using AVPF does not require any extra 
> considerations such as would be required for SAVP. What does the WG 
> say?

I'm happy to add whatever the consensus is to the next revision
of the document, which I'm hoping to do before its expiration ...
so, I'll be tracking the discussion ...

---
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  Fri Dec  3 17:29:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12133
	for <avt-archive@ietf.org>; Fri, 3 Dec 2004 17:29:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaM1a-0006nO-Gs
	for avt-archive@ietf.org; Fri, 03 Dec 2004 17:35:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaLis-00087b-DR; Fri, 03 Dec 2004 17:16:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaKyt-0003Cp-D4; Fri, 03 Dec 2004 16:28:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08322;
	Fri, 3 Dec 2004 16:28:45 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaL4f-0005Yh-JW; Fri, 03 Dec 2004 16:34:48 -0500
Received: from ISI.EDU (adma.isi.edu [128.9.160.239])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id iB3LRMQ11272;
	Fri, 3 Dec 2004 13:27:22 -0800 (PST)
Message-Id: <200412032127.iB3LRMQ11272@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Fri, 03 Dec 2004 13:27:22 -0800
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: avt@ietf.org, rfc-editor@rfc-editor.org
Subject: [AVT] RFC 3952 on Real-time Transport Protocol (RTP) Payload Format
	for internet Low Bit Rate Codec (iLBC) Speech
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f


--NextPart


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


        RFC 3952

        Title:      Real-time Transport Protocol (RTP) Payload Format
                    for internet Low Bit Rate Codec (iLBC) Speech
        Author(s):  A. Duric, S. Andersen
        Status:     Experimental
        Date:       December 2004
        Mailbox:    alan.duric@telio.no, sva@kom.auc.dk
        Pages:      13
        Characters: 28655
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-avt-rtp-ilbc-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3952.txt


This document describes the Real-time Transport Protocol (RTP) payload
format for the internet Low Bit Rate Codec (iLBC) Speech developed by
Global IP Sound (GIPS).  Also, within the document there are included
necessary details for the use of iLBC with MIME and Session
Description Protocol (SDP).

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

This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind.  Discussion and
suggestions for improvement are requested.  Distribution of this memo
is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <041203132548.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3952

--OtherAccess
Content-Type: Message/External-body; name="rfc3952.txt"; site="ftp.isi.edu";
	access-type="anon-ftp"; directory="in-notes"

Content-Type: text/plain
Content-ID: <041203132548.RFC@RFC-EDITOR.ORG>


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

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

--NextPart--



From avt-bounces@ietf.org  Fri Dec  3 17:35:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13029
	for <avt-archive@ietf.org>; Fri, 3 Dec 2004 17:35:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaM75-000762-Cg
	for avt-archive@ietf.org; Fri, 03 Dec 2004 17:41:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaLiw-0008A9-LH; Fri, 03 Dec 2004 17:16:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaKyv-0003Ct-45; Fri, 03 Dec 2004 16:28:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08328;
	Fri, 3 Dec 2004 16:28:47 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaL4j-0005Yh-AI; Fri, 03 Dec 2004 16:34:49 -0500
Received: from ISI.EDU (adma.isi.edu [128.9.160.239])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id iB3LPVQ11060;
	Fri, 3 Dec 2004 13:25:31 -0800 (PST)
Message-Id: <200412032125.iB3LPVQ11060@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Fri, 03 Dec 2004 13:25:31 -0800
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Cc: avt@ietf.org, rfc-editor@rfc-editor.org
Subject: [AVT] RFC 3951 on Internet Low Bit Rate Codec (iLBC)
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027


--NextPart


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


        RFC 3951

        Title:      Internet Low Bit Rate Codec (iLBC)
        Author(s):  S. Andersen, A. Duric, H. Astrom, R. Hagen,
                    W. Kleijn, J. Linden
        Status:     Experimental
        Date:       December 2004
        Mailbox:    sva@kom.auc.dk, alan.duric@telio.no,
                    henrik.astrom@globalipsound.com,
                    roar.hagen@globalipsound.com,
                    bastiaan.kleijn@globalipsound.com,
                    jan.linden@globalipsound.com
        Pages:      194
        Characters: 373442
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-avt-ilbc-codec-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3951.txt


This document specifies a speech codec suitable for robust voice
communication over IP.  The codec is developed by Global IP Sound
(GIPS).  It is designed for narrow band speech and results in a
payload bit rate of 13.33 kbit/s for 30 ms frames and 15.20 kbit/s
for 20 ms frames.  The codec enables graceful speech quality
degradation in the case of lost frames, which occurs in connection
with lost or delayed IP packets.

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

This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind.  Discussion and
suggestions for improvement are requested.  Distribution of this memo
is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <041203132106.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3951

--OtherAccess
Content-Type: Message/External-body; name="rfc3951.txt"; site="ftp.isi.edu";
	access-type="anon-ftp"; directory="in-notes"

Content-Type: text/plain
Content-ID: <041203132106.RFC@RFC-EDITOR.ORG>


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

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

--NextPart--



From avt-bounces@ietf.org  Fri Dec  3 19:38:02 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24326
	for <avt-archive@ietf.org>; Fri, 3 Dec 2004 19:38:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaO1u-0001vf-FZ
	for avt-archive@ietf.org; Fri, 03 Dec 2004 19:44:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaNhC-0002N8-Rm; Fri, 03 Dec 2004 19:22:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaNWa-0007cO-10
	for avt@megatron.ietf.org; Fri, 03 Dec 2004 19:11:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22614
	for <avt@ietf.org>; Fri, 3 Dec 2004 19:11:40 -0500 (EST)
Received: from dns.packetdesign.com ([65.192.41.10]
	helo=mailman.packetdesign.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaNcP-0001RP-4F
	for avt@ietf.org; Fri, 03 Dec 2004 19:17:45 -0500
Received: from ash.packetdesign.com (ash.packetdesign.com [192.168.0.243])
	by mailman.packetdesign.com (8.12.8/8.12.8) with ESMTP id
	iB40AuCJ040024; Fri, 3 Dec 2004 16:10:57 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Fri, 3 Dec 2004 16:10:56 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Re: [AVT] Comment on draft-ietf-avt-rtp-framing-contrans-03.txt
In-Reply-To: <41B091E6.7070901@ericsson.com>
Message-ID: <20041203160456.I91532@ash.packetdesign.com>
References: <20041203080421.S11590@oak.packetdesign.com>
	<41B091E6.7070901@ericsson.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: John Lazzaro <lazzaro@eecs.berkeley.edu>, 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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5

On Fri, 3 Dec 2004, Magnus Westerlund wrote:
> Stephen Casner wrote:
> > How would AVPF be used with TCP?  One of the primary applications for
> > AVPF with UDP is retransmission, but that is not applicable to TCP.
>
> There are also other feedback reports that can be included in RTCP. The
> reason I think that one should be able to indicate AVPF, is the case of
> a media relay, like the XCON focus. In that case, one participants may
> be required to join a session using TCP, for example due to NAT
> traversal. In that case the other participants will use AVPF get
> advantages of it. Thus there are cases where the usage of AVPF feedback
> and timing may be forwarded over the TCP/RTP connection.

Hmmm.  XCON is centralized conferencing.  I would think that the
TCP/RTP connection would be a separate RTP session from the ones using
AVPF.  That is, the MCU is an RTP mixer rather than an RTP translator.

> > AVPF is about timing rules for sending RTCP.  When transmitting over
> > TCP, one cannot strictly control when packets are sent.
>
> Assuming that you have sufficient bandwidth for sending packets
> immediately the rules are still useful in scenarios like the above
> one I described.

But it may not be easy or possible for the application to tell whether
or not it has sufficient bandwidth.  I don't think this makes sense.
At least, I don't think that TCP/RTP/AVPF can be defined without
giving some thought to the problems that might arise with that
combination.  It is not a slam dunk.

                                                        -- Steve

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


From avt-bounces@ietf.org  Sun Dec  5 01:46:13 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA26802
	for <avt-archive@ietf.org>; Sun, 5 Dec 2004 01:46:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaqFw-0002ff-Hh
	for avt-archive@ietf.org; Sun, 05 Dec 2004 01:52:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CapmX-0005ml-8o; Sun, 05 Dec 2004 01:22:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CapLu-0006oO-N6
	for avt@megatron.ietf.org; Sun, 05 Dec 2004 00:54:34 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20172
	for <avt@ietf.org>; Sun, 5 Dec 2004 00:54:31 -0500 (EST)
Received: from relay0.eecs.berkeley.edu ([169.229.60.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CapRz-0001EM-Dg
	for avt@ietf.org; Sun, 05 Dec 2004 01:00:52 -0500
Received: from gateway2.EECS (gateway2.EECS.Berkeley.EDU [169.229.60.39])
	by relay0.EECS.Berkeley.EDU (8.13.1/8.12.10) with ESMTP id
	iB55sWbq008483
	for <avt@ietf.org>; Sat, 4 Dec 2004 21:54:32 -0800 (PST)
Received: from [128.32.34.73] (dhcp-34-73.CS.Berkeley.EDU [128.32.34.73])
	by gateway2.EECS.Berkeley.EDU
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTPSA id <0I88009MJJ2VM8@gateway2.EECS.Berkeley.EDU> for
	avt@ietf.org; Sat, 04 Dec 2004 21:54:32 -0800 (PST)
Date: Sat, 04 Dec 2004 21:54:31 -0800
From: lazzaro <lazzaro@eecs.berkeley.edu>
To: avt@ietf.org
Message-id: <21EC2664-4682-11D9-85BE-00039372C384@eecs.berkeley.edu>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; charset=US-ASCII; format=flowed
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7BIT
Subject: [AVT] RTP MIDI: new I-Ds available, ready for Last Call
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7BIT

Hi everyone,

	Just sent updated RTP MIDI I-Ds off to
internet-drafts:

draft-ietf-avt-rtp-midi-format-07.txt
draft-ietf-avt-rtp-midi-guidelines-07.txt

	Download advance copies here:

http://www.cs.berkeley.edu/~lazzaro/sa/pubs/txt/current-rtp-midi.txt
http://www.cs.berkeley.edu/~lazzaro/sa/pubs/txt/current-guide.txt

	I believe these two I-Ds are ready for Last Call.

	This update incorporates comments from MIDI
Manufacturers Association (MMA) expert Jim Wright,
which were advanced by the MMA Transport Level Working
Group (TLWG).  At this point, I believe the MMA is happy
with the I-Ds going forward.

	This update also incorporates changes requested
by Magnus in MMUSIC concerning media time.

	See the change log for more details.

---
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  Mon Dec  6 03:48:38 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14202
	for <avt-archive@ietf.org>; Mon, 6 Dec 2004 03:48:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbEeG-0004sk-AP
	for avt-archive@ietf.org; Mon, 06 Dec 2004 03:55:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbEUV-0003bB-SC; Mon, 06 Dec 2004 03:45:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CagMI-0008K3-Rq
	for avt@megatron.ietf.org; Sat, 04 Dec 2004 15:18:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20975
	for <avt@ietf.org>; Sat, 4 Dec 2004 15:18:20 -0500 (EST)
Received: from mail1.microsoft.com ([131.107.3.125])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CagSH-0007jN-Va
	for avt@ietf.org; Sat, 04 Dec 2004 15:24:35 -0500
Received: from mailout2.microsoft.com ([157.54.1.120]) by mail1.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.1277); 
	Sat, 4 Dec 2004 12:17:50 -0800
Received: from red-hub-04.redmond.corp.microsoft.com ([157.54.3.6]) by
	mailout2.microsoft.com with Microsoft SMTPSVC(6.0.3790.211); 
	Sat, 4 Dec 2004 12:17:49 -0800
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com
	([157.54.0.39]) by red-hub-04.redmond.corp.microsoft.com with
	Microsoft SMTPSVC(6.0.3790.211); Sat, 4 Dec 2004 12:17:49 -0800
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com
	([157.54.12.81]) by
	win-imc-01.wingroup.windeploy.ntdev.microsoft.com with
	Microsoft SMTPSVC(6.0.3790.1277); Sat, 4 Dec 2004 12:17:49 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 4 Dec 2004 12:14:46 -0800
Message-ID: <9ED672B9D1A64C489291BE0FB822217D0851EF5B@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: Does RTCP_MIN_TIME still apply when b=RR is specified?
thread-index: AcTaPeZa1dLwEXzkTmqM/035VdRU9A==
From: "Anders Klemets" <anderskl@windows.microsoft.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 04 Dec 2004 20:17:49.0590 (UTC)
	FILETIME=[53701B60:01C4DA3E]
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 3f3e54d3c03ed638c06aa9fa6861237e
X-Mailman-Approved-At: Mon, 06 Dec 2004 03:45:04 -0500
Subject: [AVT] Does RTCP_MIN_TIME still apply when b=RR is specified?
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="===============1730339124=="
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 8d89ee9312a95de8ee48d1c94511f1bb

This is a multi-part message in MIME format.

--===============1730339124==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4DA3E.535AFB18"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4DA3E.535AFB18
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The algorithm for computing the RTCP reporting interval in RFC-3550 has
a constant called RTCP_MIN_TIME.  The purpose of this constant (its
value is 5 seconds) is to limit the RTCP reporting interval.  It has the
effect of limiting the actual RTCP bandwidth used by any single RTP
session participant. =20

RFC-3556 defines the SDP attributes "b=3DRR" and "b=3DRS".  These =
attributes
can be used to increase, or decrease, the bandwidth available for RTCP
reports.  But when I read RFC-3556, it is not clear if the RTCP_MIN_TIME
parameter still applies, or not.  This seems to be left entirely to the
reader's imagination. =20

=20

When I started reading RFC-3556, I imagined that RTCP_MIN_TIME would not
apply.  RFC-3556 says that some applications may want to increase the
RTCP bandwidth beyond 5% of the session bandwidth, and that the solution
to that problem is provided by "b=3DRR" and "b=3DRS".  But RTCP_MIN_TIME =
is
effectively imposing a hard upper limit on the actual RTCP bandwidth
that anyone is allowed to use. =20

=20

So, because RTCP_MIN_TIME seems to work against the goal of being able
to increase the RTCP bandwidth, I thought that it would not apply in
this case.  I asked some other knowledgeable people, and they said the
same thing.

=20

But after reading the "Security Considerations" section at the end of
RFC-3556, I now have a different impression.  It says that although
"b=3DRR" and "b=3DRS" can be used to increase the RTCP bandwidth, this =
is
not a new security problem, because the same thing can happen using
RFC-3550, if someone just specifies an artificially large session
bandwidth using "b=3DAS". =20

=20

But in a RFC 3550-only implementation, if someone specifies a large
session bandwidth using "b=3DAS", RTCP_MIN_TIME will still limit the
actual RTCP bandwidth used, preventing it from becoming "excessive".
And the "Security Considerations" section in RFC-3556 says that "b=3DRR"
and "b=3DRS" do not make this problem any worse.  So, I must conclude =
that
RTCP_MIN_TIME will still limit the actual RTCP bandwidth that can be
used, even when "b=3DRR" and "b=3DRS" are used to specify a larger
bandwidth.

=20

Did I understand this correctly?

=20

(Luckily, I read the Security Considerations section, or I might have
missed this important implicit information.)

=20

Anders

=20


------_=_NextPart_001_01C4DA3E.535AFB18
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=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)">
<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>

</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'>The algorithm for computing the RTCP reporting =
interval in
RFC-3550 has a constant called RTCP_MIN_TIME. &nbsp;The purpose of this
constant (its value is 5 seconds) is to limit the RTCP reporting =
interval. &nbsp;It
has the effect of limiting the actual RTCP bandwidth used by any single =
RTP
session participant. &nbsp;<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'>RFC-3556 defines the SDP attributes =
&#8220;b=3DRR&#8221; and &#8220;b=3DRS&#8221;.&nbsp;
These attributes can be used to increase, or decrease, the bandwidth =
available
for RTCP reports.&nbsp; But when I read RFC-3556, it is not clear if the =
RTCP_MIN_TIME
parameter still applies, or not. &nbsp;This seems to be left entirely to =
the
reader&#8217;s imagination.&nbsp; <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'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>When I started reading RFC-3556, I imagined that =
RTCP_MIN_TIME
would not apply. &nbsp;RFC-3556 says that some applications may want to
increase the RTCP bandwidth beyond 5% of the session bandwidth, and that =
the
solution to that problem is provided by &#8220;b=3DRR&#8221; and =
&#8220;b=3DRS&#8221;.
&nbsp;But RTCP_MIN_TIME is effectively imposing a hard upper limit on =
the
actual RTCP bandwidth that anyone is allowed to use.&nbsp; =
<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'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>So, because RTCP_MIN_TIME seems to work against the =
goal of
being able to increase the RTCP bandwidth, I thought that it would not =
apply in
this case.&nbsp; I asked some other knowledgeable people, and they said =
the
same thing.<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'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>But after reading the &#8220;Security =
Considerations&#8221;
section at the end of RFC-3556, I now have a different impression. =
&nbsp;It
says that although &#8220;b=3DRR&#8221; and &#8220;b=3DRS&#8221; can be =
used to
increase the RTCP bandwidth, this is not a new security problem, because =
the
same thing can happen using RFC-3550, if someone just specifies an =
artificially
large session bandwidth using &#8220;b=3DAS&#8221;. =
&nbsp;<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'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>But in a RFC 3550-only implementation, if someone =
specifies
a large session bandwidth using &#8220;b=3DAS&#8221;, RTCP_MIN_TIME will =
still
limit the actual RTCP bandwidth used, preventing it from becoming =
&#8220;excessive&#8221;.&nbsp;
And the &#8220;Security Considerations&#8221; section in RFC-3556 says =
that &#8220;b=3DRR&#8221;
and &#8220;b=3DRS&#8221; do not make this problem any worse. &nbsp;So, I =
must conclude
that RTCP_MIN_TIME will still limit the actual RTCP bandwidth that can =
be used,
even when &#8220;b=3DRR&#8221; and &#8220;b=3DRS&#8221; are used to =
specify a
larger bandwidth.<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'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Did I understand this =
correctly?<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'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>(Luckily, I read the Security Considerations section, =
or I
might have missed this important implicit =
information.)<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'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Anders<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'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C4DA3E.535AFB18--


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

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

--===============1730339124==--



From avt-bounces@ietf.org  Mon Dec  6 14:14:06 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13365
	for <avt-archive@ietf.org>; Mon, 6 Dec 2004 14:14:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbOPd-0004Up-Te
	for avt-archive@ietf.org; Mon, 06 Dec 2004 14:20:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbOCr-0004AR-FB; Mon, 06 Dec 2004 14:07:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbOAt-0003vC-A7; Mon, 06 Dec 2004 14:05:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12842;
	Mon, 6 Dec 2004 14:05:29 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbOHI-0004LX-Tm; Mon, 06 Dec 2004 14:12:09 -0500
Received: from apache by megatron.ietf.org with local (Exim 4.32)
	id 1CbO9U-0003X6-6K; Mon, 06 Dec 2004 14:04:04 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1CbO9U-0003X6-6K@megatron.ietf.org>
Date: Mon, 06 Dec 2004 14:04:04 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: avt chair <magnus.westerlund@ericsson.com>, avt chair <csp@csperkins.org>,
        Internet Architecture Board <iab@iab.org>,
        avt mailing list <avt@ietf.org>,
        RFC Editor <rfc-editor@rfc-editor.org>
Subject: [AVT] Protocol Action: 'RTP Payload for Text Conversation' 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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135

The IESG has approved the following document:

- 'RTP Payload for Text Conversation '
   <draft-ietf-avt-rfc2793bis-09.txt> as a Proposed Standard

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

The IESG contact persons are Allison Mankin and Jon Peterson.

Technical Summary
 
   This specification describes how to carry real time text conversation 
   session contents in RTP packets. Text conversation session contents 
   are specified in ITU-T Recommendation T.140. 
    
   One payload format is described for transmitting text on a separate 
   RTP session dedicated for the transmission of text.  

   This RTP payload description also recommends a method to include 
   redundant text from already transmitted packets in order to reduce 
   the risk of text loss caused by packet loss.   It uses the payload format
   format specified in RFC 2198, and updated in draft-ietf-avt-text-red, in
   current IETF review.   

   The document obsoletes RFC 2793.  The text clarifies 
   ambiguities in RFC 2793, improves on the specific implementation 
   requirements learned through development experience, and gives 
   explicit usage examples.     
 
Working Group Summary
 
 The material in  this document was strongly supported by the AVT
 working group.  There has been considerable IETF review of the
 text/red media type; in this document, the RTP domain usage is clearly
 indicated, as was carefully discussed as the context for that text mediatype.
   
Protocol Quality
 
The document was reviewed for the IESG by Allison Mankin and the AVT
 Working Group chairs.

RFC Editor Notes

Abstract

OLD:
This memo describes how to carry real time text conversation 
   session contents in RTP packets. Text conversation session contents 
   are specified in ITU-T Recommendation T.140.
NEW:
 This memo obsoletes RFC 2793; it describes how to carry real time text
 conversation session contents in RTP packets.  Text conversation session
 contents are specified in ITU-T Recommendation T.140.

IANA Considerations

OLD:
   This document defines one RTP payload format named "t140" and an 
   associated MIME type "text/t140", to be registered by IANA.
NEW:
  This document updates the RTP payload format named "t140" and the
   associated MIME type "text/t140", in the IANA RTP and Media Type registries.


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


From avt-bounces@ietf.org  Tue Dec  7 08:03:11 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24983
	for <avt-archive@ietf.org>; Tue, 7 Dec 2004 08:03:11 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cbf6N-0002WY-Rr
	for avt-archive@ietf.org; Tue, 07 Dec 2004 08:10:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CberF-0004g8-Dk; Tue, 07 Dec 2004 07:54:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbekH-0003lo-V1
	for avt@megatron.ietf.org; Tue, 07 Dec 2004 07:47:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23408
	for <avt@ietf.org>; Tue, 7 Dec 2004 07:47:08 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cbeqq-0001yK-3l
	for avt@ietf.org; Tue, 07 Dec 2004 07:53:57 -0500
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:65446)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1Cbejl-0000eM-C7; Tue, 07 Dec 2004 12:46:37 +0000
In-Reply-To: <9D277E44D6EF0942B928C6F0DE99BB3146FCAF@lan-ex-01.panasonic.de>
References: <9D277E44D6EF0942B928C6F0DE99BB3146FCAF@lan-ex-01.panasonic.de>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <05D32DBC-484E-11D9-9AFB-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Request for WG Last-Call for
	draft-ietf-avt-rtp-3gpp-timed-text-07.txt
Date: Tue, 7 Dec 2004 12:46:32 +0000
To: "Rey Jose" <Rey@panasonic.de>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit
Cc: "Magnus Westerlund \(KI/EAB\)" <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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit

Jose,

On 2 Dec 2004, at 13:43, Rey Jose wrote:
>> Section 3.1.2 (first paragraph on page 21) states that a
>> maximum of 64 dynamic SIDX are allowed at any moment, but
>> allows a range of 0-127.
>> Suggest either allowing 127 active values, or reducing the
>> allowable range, or adding an explanatory note to clarify.
>
> This has the following reason: If you allow 127 values, then when a 
> reordered packet with a new sample description arrives, it is 
> discarded.  E.g. last packet received is SIDX=5, thus the only invalid 
> value would be SIDX=6, e.g. Now a reordered packet arrives with a new 
> description, SIDX=9. It will be mistakingly discarded, because the 
> SIDX=9 is marked "valid" at that moment and the valid sample 
> descriptions shall not be re-written.  Therefore, a "guard interval" 
> is introduced. Agreed it should be rare to use so many sample 
> descriptions but nevertheless, a mechanism is provided for that case. 
> As for the "guard interval" value, we found 64 as 128/2 simple enough 
> while still meeting the expected maximum number of sample 
> descriptions. Besides that, there's no other motivation for choosing 
> 64 or other value. I'll add a similar explanation if that's fine with 
> you into the Annex.  Comments?

Adding this would be helpful.

Thanks,
Colin


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


From avt-bounces@ietf.org  Tue Dec  7 08:06:30 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25303
	for <avt-archive@ietf.org>; Tue, 7 Dec 2004 08:06:30 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cbf9a-0002cP-Us
	for avt-archive@ietf.org; Tue, 07 Dec 2004 08:13:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cbevn-0005kc-Hf; Tue, 07 Dec 2004 07:59:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cbeq6-0004Oy-SD
	for avt@megatron.ietf.org; Tue, 07 Dec 2004 07:53:11 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23900
	for <avt@ietf.org>; Tue, 7 Dec 2004 07:53:09 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cbewg-00025Z-4h
	for avt@ietf.org; Tue, 07 Dec 2004 07:59:58 -0500
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:65495)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1Cbepb-0001cn-Lv; Tue, 07 Dec 2004 12:52:39 +0000
In-Reply-To: <9D277E44D6EF0942B928C6F0DE99BB3146FC82@lan-ex-01.panasonic.de>
References: <9D277E44D6EF0942B928C6F0DE99BB3146FC82@lan-ex-01.panasonic.de>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <DE004F17-484E-11D9-9AFB-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Comments on  draft-ietf-avt-rtp-3gpp-timed-text-07.txt
Date: Tue, 7 Dec 2004 12:52:35 +0000
To: "Rey Jose" <Rey@panasonic.de>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
Cc: Jan van der Meer <jan.vandermeer@philips.com>,
        Magnus Westerlund <magnus.westerlund@ericsson.com>, avt@ietf.org,
        Dave Singer <singer@apple.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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit

Jose,

On 2 Dec 2004, at 11:35, Rey Jose wrote:
> I have a question. You say:
>>
>> "Section 3 notes that the RTP timestamp rate is the value of
>> the "timescale" parameter in the Media Header Box. Because
>> the timestamp rate affects the synchronisation accuracy and
>> RTCP statistics, I think this draft needs to give guidance on
>> how that parameter is chosen when the file is constructed."
>
> Part of this concern is addressed in the text describing 
> live-streaming with a quote from RTP:
>
> "The resolution of the clock MUST be sufficient for the desired 
> synchronization accuracy and for measuring packet arrival jitter (one 
> tick per video frame is typically not sufficient)"
>
> Now, I want to understand better what's being asked:
>
> 1.- Regarding the synchronisation of different RTP streams: is this 
> actually a matter to be dealt with in the payload format? Isn't this 
> rather a matter of the creator of the 3GP file?? I.e. in a 3GP file 
> containing several tracks, these should be synchronised anyway so no 
> special care is taken for RTP. For the case of a text track sent 
> together with other RTP streams (not coming from the same 3GP file), 
> would the quote above be enough?
>
> 2.- Regarding RTCP statistics, for all cases, why is the quote above 
> not enough?

The quote is enough, but your draft states that it applies only to live 
streaming. You need to restructure the text to make it clear that the 
talk about synchronisation accuracy applies both when choosing a clock 
rate for live streaming, and when creating a 3GPP timed text file.

Colin


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


From avt-bounces@ietf.org  Wed Dec  8 14:14:15 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25369
	for <avt-archive@ietf.org>; Wed, 8 Dec 2004 14:14:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cc7NH-0005Mw-IU
	for avt-archive@ietf.org; Wed, 08 Dec 2004 14:21:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cc78t-0007B9-8C; Wed, 08 Dec 2004 14:06:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cc74s-0006Bt-OF; Wed, 08 Dec 2004 14:02:19 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24230;
	Wed, 8 Dec 2004 14:02:17 -0500 (EST)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cc7Bd-000564-9y; Wed, 08 Dec 2004 14:09:22 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-1.cisco.com with ESMTP; 08 Dec 2004 14:08:21 -0500
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mramalho-w2k.cisco.com (dhcp-64-100-135-181.cisco.com
	[64.100.135.181])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iB8I1cA7017672; 
	Wed, 8 Dec 2004 13:01:38 -0500 (EST)
Message-Id: <4.3.2.7.2.20041208134458.02880aa0@mira-sjc5-e.cisco.com>
X-Sender: mramalho@mira-sjc5-e.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 08 Dec 2004 14:01:37 -0500
To: Mark Baugher <mbaugher@cisco.com>
From: "Michael A. Ramalho" <mramalho@cisco.com>
Subject: Re: [MMUSIC] RE: [AVT] RFC 3711 and RTCP
In-Reply-To: <F5A8611E-4483-11D9-8729-000A95DC10F2@cisco.com>
References: <AAB4B3D3CF0F454F98272CBE187FDE2F06E305DA@is0004avexu1.global.avaya.com>
	<AAB4B3D3CF0F454F98272CBE187FDE2F06E305DA@is0004avexu1.global.avaya.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 0c3d807a9e67fb2ae2b97f891ffd2e4e
Cc: rmonmib@ietf.org, "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>,
        avt@ietf.org, Alan Clark <alan.d.clark@telchemy.com>, mmusic@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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 0f3de74e534ea82d41273d2b8504db1c

At 09:02 AM 12/2/2004 -0800, Mark Baugher wrote:
>Dan
>   I think use of the E bit needs to be explicitly signaled the SDP 
> security descriptions.  That way, an offerer or answerer can express 
> whether it wants to have all SRTCP messages encrypted or allow some to be 
> in the clear.  I don't know if we need to call out the specific SRTCP 
> messages that may be left in the clear or do make it "general purpose."

Mark,

I was looking into this last week. I think it would be unwise to leave
UNencrypted any RTCP block type that has RTP Sequence Numbers
in it (as they would be in the clear).

For example, the Loss RLE block (a RTCP-XR block) has information
on the base RTP sequence numbers the Loss RLE block reports on.
There are many such RTCP-XR block types (but the VoIP Metrics
Block is not one of these :-)).

This would expose a "guess-able range" for *part of* the packet index
used in SRTP (as I remember it, the SRTP packet index uses the
RTP sequence number for low order portion of the packet index).
I think this would be a no-no for the cryptographic experts.

>A general-purpose approach would be to signal that ENCRYPTED_SRTP can be 
>overridden for any packet for which the sender chooses to clear the E 
>bit.  The general-purpose mechanism might be suitable for going into 
>draft-ietf-mmusic-sdescriptions-08.txt.  If we want to explicitly signal 
>that the E bit can be clear just for XR packets when UNENCRYPTED_SRTCP is 
>set, then I think that belongs in RFC 3611bis.

If my assertion/guess above is correct, then I'd only recommend the
option to leave in the clear only those RTCP-XR packets that do not
expose information sensitive to the SRTP context. This would be a trivial
exercise (to look at the blocks and decide which ones you do not want
sent in the clear) but does complicate the permutations/combinations of
what would need to be signaled in SDP.

And then, since RTPC blocks may be piggybacked, one must take
care not to have*potentially unencrptable* blocks piggybacked with
other "normally encrypted" blocks. I still don't like the potential interaction
between the "encryption" and "RTCP" layers here.

Michael Ramalho


>Mark
>On Dec 2, 2004, at 3:45 AM, Romascanu, Dan ((Dan)) wrote:
>
>>I would be cautious in saying that in no circumstances the contents of an 
>>XR payload would be remotely useful to an eavesdropper. We may encounter 
>>some very security aware environments where even the fact that a call 
>>happens between two IP phones, its duration, or QoS parameters need to be 
>>kept confidential. For this reason, while working to provide a strong 
>>recommendation for RTCP XR packets not to be encrypted, I do not believe 
>>that we can make this a MUST requirements. As an alternative, I suggest 
>>to use  RAQMON extensions to report the RTCP XR metrics to RAQMON 
>>collectors without the security risks that may be of concern in some 
>>environments.
>>
>>Regards,
>>
>>Dan
>>
>>
>>
>>>-----Original Message-----
>>>From: mmusic-bounces@ietf.org
>>>[mailto:mmusic-bounces@ietf.org]On Behalf Of Alan Clark
>>>Sent: 01 December, 2004 2:08 PM
>>>To: Mark Baugher
>>>Cc: mmusic@ietf.org
>>>Subject: [MMUSIC] RE: [AVT] RFC 3711 and RTCP
>>>
>>>
>>>Mark
>>>
>>>To provide some background to the list - RFC3611 states the
>>>following:-
>>>
>>>    "Any encryption or filtering of XR report blocks entails a loss of
>>>    monitoring information to third parties.  For example, a
>>>network that
>>>    establishes a tunnel to encrypt VoIP Report Blocks denies that
>>>    information to the service providers traversed by the tunnel.  The
>>>    service providers cannot then monitor or respond to the quality of
>>>    the VoIP calls that they carry, potentially creating
>>>problems for the
>>>    network's users.  As a default, XR packets should not be
>>>encrypted or
>>>    filtered."
>>>
>>>I can't conceive of any circumstance in which the contents of
>>>an XR payload
>>>would be remotely useful to an eavesdropper and hence stating that XR
>>>payloads should always be left unencrypted would be (at least
>>>in my opinion)
>>>ok.  If we wanted to make this even more specific we could narrow this
>>>requirement down to only XR VoIP Metrics payloads to avoid
>>>the situation in
>>>which some future XR payload may be problematic.
>>>
>>>The availability of VoIP metrics payloads will be a huge
>>>issue for service
>>>providers - as we move through 2005 RTCP XR will be a mainstay of VoIP
>>>performance management and is already a mandatory requirement
>>>within certain
>>>sectors of the industry.  Making the VoIP metrics payload
>>>unencrypted by
>>>default may seem a small issue today however it will have
>>>major consequences
>>>to the industry as SRTP starts to roll out.
>>>
>>>Regards
>>>
>>>Alan
>>>
>>>
>>>
>>>-----Original Message-----
>>>From: Mark Baugher [mailto:mbaugher@cisco.com]
>>>Sent: Tuesday, November 30, 2004 6:45 PM
>>>To: Alan Clark
>>>Cc: mmusic@ietf.org
>>>Subject: Re: [AVT] RFC 3711 and RTCP
>>>
>>>
>>>Alan
>>>    I am copying MMUSIC (and not cross-posting to AVT) to
>>>further discuss
>>>a possible change to SDP security descriptions, which has completed WG
>>>last call.  The change is needed for RFC 3611, and we also discovered
>>>that
>>>http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions
>>>-07.txt does not address the SRTCP E bit properly. I offered the
>>>following text in a posting to AVT:
>>>"As the default behavior when UNENCRYPTED_SRTCP is signaled, all SRTCP
>>>packets MUST have the E bit set to zero and MUST NOT be encrypted.
>>>Otherwise, all SRTP packets MUST have the E bit set to one and MUST be
>>>encrypted by default.  Individual applications MAY override these
>>>default behaviors in their specifications.  In a session where SRTCP
>>>packets are encrypted, therefore, applications that use RFC 3611 MAY
>>>set the E bit to 0 for XR packets as recommended by RFC 3611."
>>>
>>>One of my co-authors pointed out that the last sentence is
>>>more than an
>>>editorial change.  We also don't like the fact that an offerer or
>>>answerer cannot explicitly signal when it wants the XR packet to be
>>>encrypted or unencrypted.  In other words, if ENCRYPTED_SRTCP is the
>>>default setting and RFC 3611 is also signaled, it is ambiguous as to
>>>whether the SRTCP sender will encrypt the XR packet or not.  It's
>>>solely up to the sender.  If the offerer or answerer want the
>>>XR packet
>>>to always be encrypted, there is no way to signal that.  Ditto for the
>>>unencrypted case.
>>>
>>>I think we need to put the first three sentences of the above-quoted
>>>paragraph into SDP security descriptions as an editorial change.  I'm
>>>proposing this to the working group.  I also propose not to
>>>include the
>>>last sentence.  Instead, we could add a new signaling parameter,
>>>UNENCRYPTED_XR, which implies that all SRTCP messages are to be
>>>encrypted except for the XR packets, which will have their E
>>>bit clear,
>>>of course.
>>>
>>>This new parameter could be placed in an RFC 3611bis or in a revision
>>>of draft-ietf-mmusic-sdescriptions-07.txt, which will then need to
>>>undergo another WG last call.  What do you (all) think about this?
>>>
>>>Mark
>>>
>>>On Nov 24, 2004, at 4:18 PM, Mark Baugher wrote:
>>>
>>>>Alan
>>>>   As Dave Oran has pointed out, the definition that you want is not
>>>>supported in the signaling, at present.  The current definition of
>>>>http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions
>>>>-07.txt treats SRTCP encryption as either on or off and does not
>>>>address the problem of setting the E bit in SRTCP packets.
>>>This is a
>>>>bug that we need to fix.
>>>>
>>>>   MMUSIC has finished last call on
>>>>draft-ietf-mmusic-sdescriptions-07.txt, and the transport ADs have
>>>>reviewed it.  We'll be making some changes at Jon Peterson's request
>>>>and post another version in about a week.  This is an opportunity to
>>>>address the E bit, but the MMUSIC chairs or transport ADs may want
>>>>another WG last call.  Off the top of my head, I would
>>>offer something
>>>>like the following.
>>>>
>>>>"As the default behavior when UNENCRYPTED_SRTCP is
>>>signaled, all SRTCP
>>>>packets MUST have the E bit set to zero and MUST NOT be encrypted.
>>>>Otherwise, all SRTP packets MUST have the E bit set to one
>>>and MUST be
>>>>encrypted by default.  Individual applications MAY override these
>>>>default behaviors in their specifications.  In a session where SRTCP
>>>>packets are encrypted, therefore, applications that use RFC 3611 MAY
>>>>set the E bit to 0 for XR packets as recommended by RFC 3611."
>>>>
>>>>Mark
>>>>
>>>>On Nov 24, 2004, at 2:33 PM, Alan Clark wrote:
>>>>
>>>>>
>>>>>
>>>>>Mark
>>>>>
>>>>>We tried to flag this in RFC3611 with the following text in the
>>>>>"security
>>>>>considerations" section
>>>>>
>>>>>    Any encryption or filtering of XR report blocks entails
>>>a loss of
>>>>>    monitoring information to third parties.  For example, a network
>>>>>that
>>>>>    establishes a tunnel to encrypt VoIP Report Blocks denies that
>>>>>    information to the service providers traversed by the
>>>tunnel.  The
>>>>>    service providers cannot then monitor or respond to the
>>>quality of
>>>>>    the VoIP calls that they carry, potentially creating
>>>problems for
>>>>>the
>>>>>    network's users.  As a default, XR packets should not
>>>be encrypted
>>>>>or
>>>>>    filtered.
>>>>>
>>>>>Could we potentially interpret this as being the
>>>definition of what to
>>>>>selectively encrypt in the case of the RFC3611 specification?
>>>>>
>>>>>Regards
>>>>>
>>>>>Alan
>>>>>
>>>>>
>>>>>-----Original Message-----
>>>>>From: Mark Baugher [mailto:mbaugher@cisco.com]
>>>>>Sent: Wednesday, November 24, 2004 2:42 PM
>>>>>To: Alan Clark
>>>>>Cc: Oren Peleg; Cullen Jennings; avt@ietf.org; David R
>>>Oran; Michael
>>>>>A.
>>>>>Ramalho
>>>>>Subject: Re: [AVT] RFC 3711 and RTCP
>>>>>
>>>>>
>>>>>So, when the sender and receiver agree to encrypt SRTCP, this would
>>>>>mean
>>>>>only that some SRTCP messages would be encrypted and the
>>>sender would
>>>>>decide which ones to encrypt?  My personal opinion is that
>>>this is not
>>>>>secure because it is unpredictable to the receiver, which
>>>may have a
>>>>>policy that all messages related to its session be encrypted.
>>>>>
>>>>>I can think of a few potential approaches to this problem.
>>>>>
>>>>>1. Let individual SRTCP messages or a bundle of SRTCP messages
>>>>>be signaled to be unencrypted when SRTCP encryption is used.
>>>>>
>>>>>2. Make a blanket policy that the sender determine what
>>>>>to selectively encrypt, as you suggest.
>>>>>
>>>>>3. Define the policy of what to selectively encrypt in
>>>>>the particular specification.  In other words, a document could
>>>>>re-define the signaling of SRTCP encryption according to its
>>>>>needs.  The specification of foo, therefore, could define a new
>>>>>parameter such as foo_ENCRYPTED_SRTCP to be used in place of
>>>>>ENCRYPTED_SRTCP.  The foo document would define what gets
>>>>>encrypted and what does not get encrypted as per its needs.
>>>>>
>>>>>I commented on #2 already.  I don't like #1 because of its
>>>signaling
>>>>>complexity.  I like #3 because it limits the complexity to the
>>>>>specific needs of an application.  #1 would be more efficient than
>>>>>#3 if lots of applications had their own specific needs for
>>>>>selective encryption of SRTCP message.  But I don't think this is
>>>>>the case.
>>>>>
>>>>>Mark
>>>>>
>>>>>On Nov 24, 2004, at 10:58 AM, Alan Clark wrote:
>>>>>
>>>>>>
>>>>>>If the use of encryption in SRTCP is signalled by an
>>>explicit (E) bit
>>>>>>in the
>>>>>>SRTCP header then perhaps the sender could autonomously decide
>>>>>>whether
>>>>>>it
>>>>>>wants to encrypt?  Presumably since the sender is in the best
>>>>>>position
>>>>>>to
>>>>>>decide if the data is sensitive then this would be ok - and the
>>>>>>receiver is
>>>>>>able to just look at the E bit and hence recognize that
>>>decryption is
>>>>>>needed.
>>>>>>
>>>>>>Alan
>>>>>>
>>>>>>-----Original Message-----
>>>>>>From: avt-bounces@ietf.org
>>>[mailto:avt-bounces@ietf.org]On Behalf Of
>>>>>>Mark Baugher
>>>>>>Sent: Wednesday, November 24, 2004 1:33 PM
>>>>>>To: David R Oran
>>>>>>Cc: Cullen Jennings; Oren Peleg; Michael A. Ramalho; Alan Clark;
>>>>>>avt@ietf.org
>>>>>>Subject: Re: [AVT] RFC 3711 and RTCP
>>>>>>
>>>>>>
>>>>>>
>>>>>>On Nov 24, 2004, at 10:05 AM, David R Oran wrote:
>>>>>>
>>>>>>>
>>>>>>>On Nov 24, 2004, at 12:23 PM, Alan Clark wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>Michael
>>>>>>>>
>>>>>>>>I don't see why this would be a problem unless you included SDES
>>>>>>>>and
>>>>>>>>(SR or
>>>>>>>>RR or XR) in the same RTCP packet.  SRTP (at least the
>>>protocol) is
>>>>>>>>apparently able to decided on a packet by packet basis
>>>whether to
>>>>>>>>encrypt
>>>>>>>>RTCP - hopefully SRTP implementations also permit this.
>>>>>>>Sure, they can do this. But remember offer-answer. How does a
>>>>>>>receiver
>>>>>>>communicate such a granular policy to the transmitter?
>>>Right now if
>>>>>>>can say whether to auth or auth+encrypt RTP, and auth or
>>>>>>>auth+encrypt
>>>>>>>RTCP. There's no way to say auth+encrypt SDES but only auth SR/XR
>>>>>>>etc.
>>>>>>
>>>>>>Seems to me that this is a problem with SDP security descriptions.
>>>>>>That problem might be there because we forgot about the E
>>>bit.  This
>>>>>>seems very messy for the reason you mention above -
>>>granularity.  I
>>>>>>don't think that we want to negotiate the encryption
>>>policy for each
>>>>>>type SDP message, which is a problem with something like
>>>the E bit.
>>>>>>
>>>>>>Mark
>>>>>>>
>>>>>>>
>>>>>>>>Logically I'd send SDES on its own at the start of a call to
>>>>>>>>provide
>>>>>>>>some
>>>>>>>>user info, but would not send SR/RR/XR until at least
>>>8-10 seconds
>>>>>>>>into the
>>>>>>>>call as I need some time to gather statistics to report.
>>>>>>>That's not exactly what the RTP specs say. RTCP timers don't have
>>>>>>>this
>>>>>>>kind of policy today. In fact, there are porposals on
>>>the table to
>>>>>>>use
>>>>>>>RTCP for early feedback to assess reception quality on
>>>some initial
>>>>>>>packets - e.g. the RTP-noop proposal. In any event that has no
>>>>>>>bearing
>>>>>>>on the present discussion.
>>>>>>>
>>>>>>>>After the
>>>>>>>>start-of-call exchange there would appear to be minimal need to
>>>>>>>>include
>>>>>>>>SDES. I'm sure we could construct some scenarios in
>>>which you "may"
>>>>>>>>need to
>>>>>>>>include SDES with SR/RR/XR however the vast majority of
>>>cases would
>>>>>>>>either
>>>>>>>>need only a single initial exchange or may not need SDES at all.
>>>>>>>Any time you change SSRC you potentially need to send SDES.
>>>>>>>That said, I still don't see what bearing this has on
>>>the discussion
>>>>>>>about whether we need the complexity of encrypting some
>>>RTCP packets
>>>>>>>and not others for a single session.
>>>>>>>
>>>>>>>It's a tradeoff between extra complexity+less privacy versus
>>>>>>>allowing
>>>>>>>snoopers to gather RTCP stats.
>>>>>>>
>>>>>>>Dave.
>>>>>>>
>>>>>>>>Regards
>>>>>>>>
>>>>>>>>Alan
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>-----Original Message-----
>>>>>>>>From: Michael A. Ramalho [mailto:mramalho@cisco.com]
>>>>>>>>Sent: Wednesday, November 24, 2004 9:39 AM
>>>>>>>>To: Alan Clark
>>>>>>>>Cc: Oren Peleg; avt@ietf.org
>>>>>>>>Subject: RE: [AVT] RFC 3711 and RTCP
>>>>>>>>
>>>>>>>>
>>>>>>>>At 07:54 AM 11/24/2004 -0500, Alan Clark wrote:
>>>>>>>>>Hi Oren
>>>>>>>>>
>>>>>>>>>Yes - encryption is intended to provide privacy however this
>>>>>>>>>relates
>>>>>>>>>primarily to the voice payloads and to information within RTCP
>>>>>>>>>that
>>>>>>>>>may be
>>>>>>>>>associated with individual users (e.g. SDES).
>>>>>>>>>
>>>>>>>>>SR, RR and XR contain only peformance statistics and
>>>there is no
>>>>>>>>>privacy
>>>>>>>>>consideration that I can think of related to this type of data.
>>>>>>>>>
>>>>>>>>>The message is - encrypt RTP, optionally encrypt RTCP SDES but
>>>>>>>>>don't
>>>>>>>>encrypt
>>>>>>>>>RTCP SR/RR/XR
>>>>>>>>
>>>>>>>>Hi Alan,
>>>>>>>>
>>>>>>>>I am wondering about implementations utilizing your advise
>>>>>>>>"optionally
>>>>>>>>encrypt
>>>>>>>>RTCP SDES but don't encrypt RTCP SR/RR/XR".
>>>>>>>>
>>>>>>>>Is there an easy way to tell SRTP to encrypt RTCP SDES, but not
>>>>>>>>RTCP
>>>>>>>>SR/RR/XR? It seems that all the RTCP blocks would otherwise be
>>>>>>>>highly
>>>>>>>>related to each other. For example (quote out of RFC 3611):
>>>>>>>>
>>>>>>>>"XR packets supplement the existing RTCP packets, and may be
>>>>>>>>stacked
>>>>>>>>with
>>>>>>>>other RTCP packets to form compound RTCP packets [9,
>>>Section 6]."
>>>>>>>>
>>>>>>>>Thus, RFC3611 explicitly admits the possibility of (but does not
>>>>>>>>mandate)
>>>>>>>>the piggybacking all the RTCP-XR block types.
>>>>>>>>
>>>>>>>>RTCP implementations would have to know the SRTP
>>>encryption rules
>>>>>>>>to
>>>>>>>>make sure they don't perform piggybacking with SDES ...
>>>but could
>>>>>>>>allow
>>>>>>>>(the more bandwidth efficient) piggybacking on the other RTCP-XR
>>>>>>>>blocks.
>>>>>>>>
>>>>>>>>This RTCP/SRTP interaction/dependency seems to add a
>>>burden to both
>>>>>>>>RTCP and SRTP implementations ... let alone the expressiveness
>>>>>>>>required
>>>>>>>>to signal your advise in existing SDP/SRTP mechanisms.
>>>>>>>>
>>>>>>>>Are you aware of any implementations that have actually followed
>>>>>>>>your
>>>>>>>>advise above? I rather go into this one with our eyes open ...
>>>>>>>>developers
>>>>>>>>highly dislike this cross-functional entity dependency
>>>(RTCP & SRTP
>>>>>>>>along
>>>>>>>>with expressing it in SDP/SRTP mechanisms).
>>>>>>>>
>>>>>>>>Regards,
>>>>>>>>
>>>>>>>>Michael Ramalho
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>Regards
>>>>>>>>>
>>>>>>>>>Alan
>>>>>>>>>
>>>>>>>>>-----Original Message-----
>>>>>>>>>From: Oren Peleg [mailto:OrenP@audiocodes.com]
>>>>>>>>>Sent: Wednesday, November 24, 2004 7:50 AM
>>>>>>>>>To: Alan Clark; avt@ietf.org
>>>>>>>>>Subject: RE: [AVT] RFC 3711 and RTCP
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>Isnt encryption is to prevent monitoring from the first place?
>>>>>>>>>
>>>>>>>>>-----Original Message-----
>>>>>>>>>From: avt-bounces@ietf.org
>>>[mailto:avt-bounces@ietf.org] On Behalf
>>>>>>>>>Of
>>>>>>>>>Alan Clark
>>>>>>>>>Sent: Tuesday, November 23, 2004 5:42 PM
>>>>>>>>>To: avt@ietf.org
>>>>>>>>>Subject: [AVT] RFC 3711 and RTCP
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> From the flurry of discussion on RFC3711 it looks as
>>>if there is
>>>>>>>>>considerable interest in SRTP implementation.  I'd
>>>like to add a
>>>>>>>>>request
>>>>>>>>>to
>>>>>>>>>SRTP implementors with regard to manageability.
>>>>>>>>>
>>>>>>>>>RTCP SR, RR and more particularly XR (e.g. VoIP Metrics report
>>>>>>>>>block)
>>>>>>>>>contain useful information for network monitoring, and
>>>are often
>>>>>>>>>used by
>>>>>>>>>probes and analyzers to support problem diagnosis.
>>>RFC3711 allows
>>>>>>>>>the
>>>>>>>>>selective encryption of RTCP payloads and hence I
>>>would strongly
>>>>>>>>>recomment
>>>>>>>>>that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR
>>>>>>>>>payloads
>>>>>>>>>as
>>>>>>>>>this
>>>>>>>>>adversely impacts manageability.
>>>>>>>>>
>>>>>>>>>Regards
>>>>>>>>>
>>>>>>>>>Alan Clark
>>>>>>>>>Telchemy
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>_______________________________________________
>>>>>>>>>Audio/Video Transport Working Group
>>>>>>>>>avt@ietf.org
>>>>>>>>>https://www1.ietf.org/mailman/listinfo/avt
>>>>>>>>>
>>>******************************************************************
>>>>>>>>>**
>>>>>>>>>*
>>>>>>>>>******
>>>>>>>>*
>>>>>>>>>********************************
>>>>>>>>>This email and any files transmitted with it are confidential
>>>>>>>>>material.
>>>>>>>>>They are intended solely for the use of the designated
>>>individual
>>>>>>>>>or
>>>>>>>>>entity
>>>>>>>>>to whom they are addressed.
>>>>>>>>>If the reader of this message is not the intended recipient,
>>>>>>>>>you are hereby notified that any dissemination,use,
>>>>>>>>>distribution or copying of this communication is strictly
>>>>>>>>>prohibited
>>>>>>>>>and
>>>>>>>>may
>>>>>>>>>be unlawful.
>>>>>>>>>
>>>>>>>>>If you have received this email in error please notify
>>>>>>>>>postmaster@audiocodes.com and permanently delete the e-mail and
>>>>>>>>>files.
>>>>>>>>>
>>>>>>>>>
>>>******************************************************************
>>>>>>>>>**
>>>>>>>>>*
>>>>>>>>>******
>>>>>>>>*
>>>>>>>>>*******************************
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>_______________________________________________
>>>>>>>>>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
>>>>>>>David R. Oran
>>>>>>>Cisco Fellow
>>>>>>>Cisco Systems
>>>>>>>7 Ladyslipper Lane
>>>>>>>Acton, MA 01720 USA
>>>>>>>Tel: +1 978 264 2048
>>>>>>>Email: oran@cisco.com
>>>>>>>
>>>>>>>
>>>>>>>_______________________________________________
>>>>>>>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
>>>
>>>
>>>_______________________________________________
>>>mmusic mailing list
>>>mmusic@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>_______________________________________________
>>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

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


From avt-bounces@ietf.org  Wed Dec  8 15:44:39 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02493
	for <avt-archive@ietf.org>; Wed, 8 Dec 2004 15:44:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cc8mm-000776-K5
	for avt-archive@ietf.org; Wed, 08 Dec 2004 15:51:45 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cc8Zi-00017y-4z; Wed, 08 Dec 2004 15:38:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cc8Qa-0005Pq-Dv
	for avt@megatron.ietf.org; Wed, 08 Dec 2004 15:28:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01512
	for <avt@ietf.org>; Wed, 8 Dec 2004 15:28:46 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cc8XN-0006q8-EP
	for avt@ietf.org; Wed, 08 Dec 2004 15:35:52 -0500
Received: from sj-core-4.cisco.com (171.68.223.138)
	by sj-iport-4.cisco.com with ESMTP; 08 Dec 2004 12:28:24 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from [192.168.1.101] (rtp-vpn1-365.cisco.com [10.82.225.109])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id iB8KS96v013516;
	Wed, 8 Dec 2004 12:28:10 -0800 (PST)
Message-ID: <41B763D9.3060901@cisco.com>
Date: Wed, 08 Dec 2004 15:28:09 -0500
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@NORTELNETWORKS.COM>, "avt@ietf.org" <avt@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Subject: [AVT] Additional events for 2833bis-06
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit

Greetings

I've taken a look at the events in 2833bis-06, and it turns out that 
some of the events that were removed from the -05 version are actually 
being used:

1. ABCD events (144-159), which are used by some GR-303 implementations 
(incl. PacketCable GR-303 specification)
2. The trunk unavailable event (175) , which is used for some PSTN 
trunking applications.

I'd like to ask that we add these events back into 2833bis again.

Thanks

       Flemming

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


From avt-bounces@ietf.org  Wed Dec  8 15:45:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02545
	for <avt-archive@ietf.org>; Wed, 8 Dec 2004 15:45:10 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cc8nI-00077j-Cz
	for avt-archive@ietf.org; Wed, 08 Dec 2004 15:52:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cc8Zy-0001F5-Vf; Wed, 08 Dec 2004 15:38:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cc8TM-0006XI-7B; Wed, 08 Dec 2004 15:31:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01629;
	Wed, 8 Dec 2004 15:31:38 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cc8aB-0006tA-7n; Wed, 08 Dec 2004 15:38:44 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-3.cisco.com with ESMTP; 08 Dec 2004 13:36:30 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iB8KV4Pv002868;
	Wed, 8 Dec 2004 12:31:04 -0800 (PST)
Received: from [192.168.0.11] (sjc-vpn1-223.cisco.com [10.21.96.223])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id iB8KU5On001124;
	Wed, 8 Dec 2004 12:30:05 -0800
In-Reply-To: <4.3.2.7.2.20041208134458.02880aa0@mira-sjc5-e.cisco.com>
References: <AAB4B3D3CF0F454F98272CBE187FDE2F06E305DA@is0004avexu1.global.avaya.com>
	<AAB4B3D3CF0F454F98272CBE187FDE2F06E305DA@is0004avexu1.global.avaya.com>
	<4.3.2.7.2.20041208134458.02880aa0@mira-sjc5-e.cisco.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <119F387A-4958-11D9-8183-000A95DC10F2@cisco.com>
Content-Transfer-Encoding: 7bit
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [MMUSIC] RE: [AVT] RFC 3711 and RTCP
Date: Wed, 8 Dec 2004 12:30:58 -0800
To: "Michael A. Ramalho" <mramalho@cisco.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1102537807.865418"; x:"432200"; a:"rsa-sha1"; b:"nofws:24769";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"RsDtDPKbGs8PEp5GvvW1SAqiP7scCMvdNXKdky73PgIXsCwQwfOuKSsYXA54n"
	"2f1FZE8mUGWqm1RCJ/WVIgRJplCRL+KbnuHqYuikU2KK8H+FTCRAhxuHkfSha"
	"78SirdJB15tBXIaRhPDJADHTriWBpJDTpD9CLwNgwEmRM0qkk=";
	c:"From: Mark Baugher <mbaugher@cisco.com>";
	c:"Subject: Re: [MMUSIC] RE: [AVT] RFC 3711 and RTCP";
	c:"Date: Wed, 8 Dec 2004 12:30:58 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.2 (/)
X-Scan-Signature: fe6e20eef2d8927c50910823cd0d1c84
Content-Transfer-Encoding: 7bit
Cc: rmonmib@ietf.org, "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>,
        mmusic@ietf.org, Alan Clark <alan.d.clark@telchemy.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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 04ebe73024b6be81174765e91aced811
Content-Transfer-Encoding: 7bit

Michael
   Here's my take on the security of all of this:  Endpoints can choose 
to negotiate UNENCRYPTED_SRTCP or refuse such an offer, but the goal is 
to not force use of UNENCRYPTED_SRTCP when only the XR packet needs to 
be in the clear.  If we enabled the E bit for XR packets, that would 
not prevent an endpoint from rejecting the offer or any offer in which 
the SRTCP is not encrypted.

   If one does not want to expose information in the XR packets, then 
reject UNENCRYPTED_SRTCP or any offer that allows use of the E bit (in 
the future).  I don't see any security problem apart from having no 
recourse except to offer UNENCRYPTED_SRTCP when all that is desired is 
to leave one SRTCP packet type in the clear.

   Besides that, all sequence numbers are always in the clear in SRTP.

Mark
On Dec 8, 2004, at 11:01 AM, Michael A. Ramalho wrote:

> At 09:02 AM 12/2/2004 -0800, Mark Baugher wrote:
>> Dan
>>   I think use of the E bit needs to be explicitly signaled the SDP 
>> security descriptions.  That way, an offerer or answerer can express 
>> whether it wants to have all SRTCP messages encrypted or allow some 
>> to be in the clear.  I don't know if we need to call out the specific 
>> SRTCP messages that may be left in the clear or do make it "general 
>> purpose."
>
> Mark,
>
> I was looking into this last week. I think it would be unwise to leave
> UNencrypted any RTCP block type that has RTP Sequence Numbers
> in it (as they would be in the clear).
>
> For example, the Loss RLE block (a RTCP-XR block) has information
> on the base RTP sequence numbers the Loss RLE block reports on.
> There are many such RTCP-XR block types (but the VoIP Metrics
> Block is not one of these :-)).
>
> This would expose a "guess-able range" for *part of* the packet index
> used in SRTP (as I remember it, the SRTP packet index uses the
> RTP sequence number for low order portion of the packet index).
> I think this would be a no-no for the cryptographic experts.
>
>> A general-purpose approach would be to signal that ENCRYPTED_SRTP can 
>> be overridden for any packet for which the sender chooses to clear 
>> the E bit.  The general-purpose mechanism might be suitable for going 
>> into draft-ietf-mmusic-sdescriptions-08.txt.  If we want to 
>> explicitly signal that the E bit can be clear just for XR packets 
>> when UNENCRYPTED_SRTCP is set, then I think that belongs in RFC 
>> 3611bis.
>
> If my assertion/guess above is correct, then I'd only recommend the
> option to leave in the clear only those RTCP-XR packets that do not
> expose information sensitive to the SRTP context. This would be a 
> trivial
> exercise (to look at the blocks and decide which ones you do not want
> sent in the clear) but does complicate the permutations/combinations of
> what would need to be signaled in SDP.
>
> And then, since RTPC blocks may be piggybacked, one must take
> care not to have*potentially unencrptable* blocks piggybacked with
> other "normally encrypted" blocks. I still don't like the potential 
> interaction
> between the "encryption" and "RTCP" layers here.
>
> Michael Ramalho
>
>
>> Mark
>> On Dec 2, 2004, at 3:45 AM, Romascanu, Dan ((Dan)) wrote:
>>
>>> I would be cautious in saying that in no circumstances the contents 
>>> of an XR payload would be remotely useful to an eavesdropper. We may 
>>> encounter some very security aware environments where even the fact 
>>> that a call happens between two IP phones, its duration, or QoS 
>>> parameters need to be kept confidential. For this reason, while 
>>> working to provide a strong recommendation for RTCP XR packets not 
>>> to be encrypted, I do not believe that we can make this a MUST 
>>> requirements. As an alternative, I suggest to use  RAQMON extensions 
>>> to report the RTCP XR metrics to RAQMON collectors without the 
>>> security risks that may be of concern in some environments.
>>>
>>> Regards,
>>>
>>> Dan
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: mmusic-bounces@ietf.org
>>>> [mailto:mmusic-bounces@ietf.org]On Behalf Of Alan Clark
>>>> Sent: 01 December, 2004 2:08 PM
>>>> To: Mark Baugher
>>>> Cc: mmusic@ietf.org
>>>> Subject: [MMUSIC] RE: [AVT] RFC 3711 and RTCP
>>>>
>>>>
>>>> Mark
>>>>
>>>> To provide some background to the list - RFC3611 states the
>>>> following:-
>>>>
>>>>    "Any encryption or filtering of XR report blocks entails a loss 
>>>> of
>>>>    monitoring information to third parties.  For example, a
>>>> network that
>>>>    establishes a tunnel to encrypt VoIP Report Blocks denies that
>>>>    information to the service providers traversed by the tunnel.  
>>>> The
>>>>    service providers cannot then monitor or respond to the quality 
>>>> of
>>>>    the VoIP calls that they carry, potentially creating
>>>> problems for the
>>>>    network's users.  As a default, XR packets should not be
>>>> encrypted or
>>>>    filtered."
>>>>
>>>> I can't conceive of any circumstance in which the contents of
>>>> an XR payload
>>>> would be remotely useful to an eavesdropper and hence stating that 
>>>> XR
>>>> payloads should always be left unencrypted would be (at least
>>>> in my opinion)
>>>> ok.  If we wanted to make this even more specific we could narrow 
>>>> this
>>>> requirement down to only XR VoIP Metrics payloads to avoid
>>>> the situation in
>>>> which some future XR payload may be problematic.
>>>>
>>>> The availability of VoIP metrics payloads will be a huge
>>>> issue for service
>>>> providers - as we move through 2005 RTCP XR will be a mainstay of 
>>>> VoIP
>>>> performance management and is already a mandatory requirement
>>>> within certain
>>>> sectors of the industry.  Making the VoIP metrics payload
>>>> unencrypted by
>>>> default may seem a small issue today however it will have
>>>> major consequences
>>>> to the industry as SRTP starts to roll out.
>>>>
>>>> Regards
>>>>
>>>> Alan
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Mark Baugher [mailto:mbaugher@cisco.com]
>>>> Sent: Tuesday, November 30, 2004 6:45 PM
>>>> To: Alan Clark
>>>> Cc: mmusic@ietf.org
>>>> Subject: Re: [AVT] RFC 3711 and RTCP
>>>>
>>>>
>>>> Alan
>>>>    I am copying MMUSIC (and not cross-posting to AVT) to
>>>> further discuss
>>>> a possible change to SDP security descriptions, which has completed 
>>>> WG
>>>> last call.  The change is needed for RFC 3611, and we also 
>>>> discovered
>>>> that
>>>> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions
>>>> -07.txt does not address the SRTCP E bit properly. I offered the
>>>> following text in a posting to AVT:
>>>> "As the default behavior when UNENCRYPTED_SRTCP is signaled, all 
>>>> SRTCP
>>>> packets MUST have the E bit set to zero and MUST NOT be encrypted.
>>>> Otherwise, all SRTP packets MUST have the E bit set to one and MUST 
>>>> be
>>>> encrypted by default.  Individual applications MAY override these
>>>> default behaviors in their specifications.  In a session where SRTCP
>>>> packets are encrypted, therefore, applications that use RFC 3611 MAY
>>>> set the E bit to 0 for XR packets as recommended by RFC 3611."
>>>>
>>>> One of my co-authors pointed out that the last sentence is
>>>> more than an
>>>> editorial change.  We also don't like the fact that an offerer or
>>>> answerer cannot explicitly signal when it wants the XR packet to be
>>>> encrypted or unencrypted.  In other words, if ENCRYPTED_SRTCP is the
>>>> default setting and RFC 3611 is also signaled, it is ambiguous as to
>>>> whether the SRTCP sender will encrypt the XR packet or not.  It's
>>>> solely up to the sender.  If the offerer or answerer want the
>>>> XR packet
>>>> to always be encrypted, there is no way to signal that.  Ditto for 
>>>> the
>>>> unencrypted case.
>>>>
>>>> I think we need to put the first three sentences of the above-quoted
>>>> paragraph into SDP security descriptions as an editorial change.  
>>>> I'm
>>>> proposing this to the working group.  I also propose not to
>>>> include the
>>>> last sentence.  Instead, we could add a new signaling parameter,
>>>> UNENCRYPTED_XR, which implies that all SRTCP messages are to be
>>>> encrypted except for the XR packets, which will have their E
>>>> bit clear,
>>>> of course.
>>>>
>>>> This new parameter could be placed in an RFC 3611bis or in a 
>>>> revision
>>>> of draft-ietf-mmusic-sdescriptions-07.txt, which will then need to
>>>> undergo another WG last call.  What do you (all) think about this?
>>>>
>>>> Mark
>>>>
>>>> On Nov 24, 2004, at 4:18 PM, Mark Baugher wrote:
>>>>
>>>>> Alan
>>>>>   As Dave Oran has pointed out, the definition that you want is not
>>>>> supported in the signaling, at present.  The current definition of
>>>>> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions
>>>>> -07.txt treats SRTCP encryption as either on or off and does not
>>>>> address the problem of setting the E bit in SRTCP packets.
>>>> This is a
>>>>> bug that we need to fix.
>>>>>
>>>>>   MMUSIC has finished last call on
>>>>> draft-ietf-mmusic-sdescriptions-07.txt, and the transport ADs have
>>>>> reviewed it.  We'll be making some changes at Jon Peterson's 
>>>>> request
>>>>> and post another version in about a week.  This is an opportunity 
>>>>> to
>>>>> address the E bit, but the MMUSIC chairs or transport ADs may want
>>>>> another WG last call.  Off the top of my head, I would
>>>> offer something
>>>>> like the following.
>>>>>
>>>>> "As the default behavior when UNENCRYPTED_SRTCP is
>>>> signaled, all SRTCP
>>>>> packets MUST have the E bit set to zero and MUST NOT be encrypted.
>>>>> Otherwise, all SRTP packets MUST have the E bit set to one
>>>> and MUST be
>>>>> encrypted by default.  Individual applications MAY override these
>>>>> default behaviors in their specifications.  In a session where 
>>>>> SRTCP
>>>>> packets are encrypted, therefore, applications that use RFC 3611 
>>>>> MAY
>>>>> set the E bit to 0 for XR packets as recommended by RFC 3611."
>>>>>
>>>>> Mark
>>>>>
>>>>> On Nov 24, 2004, at 2:33 PM, Alan Clark wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> Mark
>>>>>>
>>>>>> We tried to flag this in RFC3611 with the following text in the
>>>>>> "security
>>>>>> considerations" section
>>>>>>
>>>>>>    Any encryption or filtering of XR report blocks entails
>>>> a loss of
>>>>>>    monitoring information to third parties.  For example, a 
>>>>>> network
>>>>>> that
>>>>>>    establishes a tunnel to encrypt VoIP Report Blocks denies that
>>>>>>    information to the service providers traversed by the
>>>> tunnel.  The
>>>>>>    service providers cannot then monitor or respond to the
>>>> quality of
>>>>>>    the VoIP calls that they carry, potentially creating
>>>> problems for
>>>>>> the
>>>>>>    network's users.  As a default, XR packets should not
>>>> be encrypted
>>>>>> or
>>>>>>    filtered.
>>>>>>
>>>>>> Could we potentially interpret this as being the
>>>> definition of what to
>>>>>> selectively encrypt in the case of the RFC3611 specification?
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> Alan
>>>>>>
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Mark Baugher [mailto:mbaugher@cisco.com]
>>>>>> Sent: Wednesday, November 24, 2004 2:42 PM
>>>>>> To: Alan Clark
>>>>>> Cc: Oren Peleg; Cullen Jennings; avt@ietf.org; David R
>>>> Oran; Michael
>>>>>> A.
>>>>>> Ramalho
>>>>>> Subject: Re: [AVT] RFC 3711 and RTCP
>>>>>>
>>>>>>
>>>>>> So, when the sender and receiver agree to encrypt SRTCP, this 
>>>>>> would
>>>>>> mean
>>>>>> only that some SRTCP messages would be encrypted and the
>>>> sender would
>>>>>> decide which ones to encrypt?  My personal opinion is that
>>>> this is not
>>>>>> secure because it is unpredictable to the receiver, which
>>>> may have a
>>>>>> policy that all messages related to its session be encrypted.
>>>>>>
>>>>>> I can think of a few potential approaches to this problem.
>>>>>>
>>>>>> 1. Let individual SRTCP messages or a bundle of SRTCP messages
>>>>>> be signaled to be unencrypted when SRTCP encryption is used.
>>>>>>
>>>>>> 2. Make a blanket policy that the sender determine what
>>>>>> to selectively encrypt, as you suggest.
>>>>>>
>>>>>> 3. Define the policy of what to selectively encrypt in
>>>>>> the particular specification.  In other words, a document could
>>>>>> re-define the signaling of SRTCP encryption according to its
>>>>>> needs.  The specification of foo, therefore, could define a new
>>>>>> parameter such as foo_ENCRYPTED_SRTCP to be used in place of
>>>>>> ENCRYPTED_SRTCP.  The foo document would define what gets
>>>>>> encrypted and what does not get encrypted as per its needs.
>>>>>>
>>>>>> I commented on #2 already.  I don't like #1 because of its
>>>> signaling
>>>>>> complexity.  I like #3 because it limits the complexity to the
>>>>>> specific needs of an application.  #1 would be more efficient than
>>>>>> #3 if lots of applications had their own specific needs for
>>>>>> selective encryption of SRTCP message.  But I don't think this is
>>>>>> the case.
>>>>>>
>>>>>> Mark
>>>>>>
>>>>>> On Nov 24, 2004, at 10:58 AM, Alan Clark wrote:
>>>>>>
>>>>>>>
>>>>>>> If the use of encryption in SRTCP is signalled by an
>>>> explicit (E) bit
>>>>>>> in the
>>>>>>> SRTCP header then perhaps the sender could autonomously decide
>>>>>>> whether
>>>>>>> it
>>>>>>> wants to encrypt?  Presumably since the sender is in the best
>>>>>>> position
>>>>>>> to
>>>>>>> decide if the data is sensitive then this would be ok - and the
>>>>>>> receiver is
>>>>>>> able to just look at the E bit and hence recognize that
>>>> decryption is
>>>>>>> needed.
>>>>>>>
>>>>>>> Alan
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: avt-bounces@ietf.org
>>>> [mailto:avt-bounces@ietf.org]On Behalf Of
>>>>>>> Mark Baugher
>>>>>>> Sent: Wednesday, November 24, 2004 1:33 PM
>>>>>>> To: David R Oran
>>>>>>> Cc: Cullen Jennings; Oren Peleg; Michael A. Ramalho; Alan Clark;
>>>>>>> avt@ietf.org
>>>>>>> Subject: Re: [AVT] RFC 3711 and RTCP
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Nov 24, 2004, at 10:05 AM, David R Oran wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> On Nov 24, 2004, at 12:23 PM, Alan Clark wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Michael
>>>>>>>>>
>>>>>>>>> I don't see why this would be a problem unless you included 
>>>>>>>>> SDES
>>>>>>>>> and
>>>>>>>>> (SR or
>>>>>>>>> RR or XR) in the same RTCP packet.  SRTP (at least the
>>>> protocol) is
>>>>>>>>> apparently able to decided on a packet by packet basis
>>>> whether to
>>>>>>>>> encrypt
>>>>>>>>> RTCP - hopefully SRTP implementations also permit this.
>>>>>>>> Sure, they can do this. But remember offer-answer. How does a
>>>>>>>> receiver
>>>>>>>> communicate such a granular policy to the transmitter?
>>>> Right now if
>>>>>>>> can say whether to auth or auth+encrypt RTP, and auth or
>>>>>>>> auth+encrypt
>>>>>>>> RTCP. There's no way to say auth+encrypt SDES but only auth 
>>>>>>>> SR/XR
>>>>>>>> etc.
>>>>>>>
>>>>>>> Seems to me that this is a problem with SDP security 
>>>>>>> descriptions.
>>>>>>> That problem might be there because we forgot about the E
>>>> bit.  This
>>>>>>> seems very messy for the reason you mention above -
>>>> granularity.  I
>>>>>>> don't think that we want to negotiate the encryption
>>>> policy for each
>>>>>>> type SDP message, which is a problem with something like
>>>> the E bit.
>>>>>>>
>>>>>>> Mark
>>>>>>>>
>>>>>>>>
>>>>>>>>> Logically I'd send SDES on its own at the start of a call to
>>>>>>>>> provide
>>>>>>>>> some
>>>>>>>>> user info, but would not send SR/RR/XR until at least
>>>> 8-10 seconds
>>>>>>>>> into the
>>>>>>>>> call as I need some time to gather statistics to report.
>>>>>>>> That's not exactly what the RTP specs say. RTCP timers don't 
>>>>>>>> have
>>>>>>>> this
>>>>>>>> kind of policy today. In fact, there are porposals on
>>>> the table to
>>>>>>>> use
>>>>>>>> RTCP for early feedback to assess reception quality on
>>>> some initial
>>>>>>>> packets - e.g. the RTP-noop proposal. In any event that has no
>>>>>>>> bearing
>>>>>>>> on the present discussion.
>>>>>>>>
>>>>>>>>> After the
>>>>>>>>> start-of-call exchange there would appear to be minimal need to
>>>>>>>>> include
>>>>>>>>> SDES. I'm sure we could construct some scenarios in
>>>> which you "may"
>>>>>>>>> need to
>>>>>>>>> include SDES with SR/RR/XR however the vast majority of
>>>> cases would
>>>>>>>>> either
>>>>>>>>> need only a single initial exchange or may not need SDES at 
>>>>>>>>> all.
>>>>>>>> Any time you change SSRC you potentially need to send SDES.
>>>>>>>> That said, I still don't see what bearing this has on
>>>> the discussion
>>>>>>>> about whether we need the complexity of encrypting some
>>>> RTCP packets
>>>>>>>> and not others for a single session.
>>>>>>>>
>>>>>>>> It's a tradeoff between extra complexity+less privacy versus
>>>>>>>> allowing
>>>>>>>> snoopers to gather RTCP stats.
>>>>>>>>
>>>>>>>> Dave.
>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>>
>>>>>>>>> Alan
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: Michael A. Ramalho [mailto:mramalho@cisco.com]
>>>>>>>>> Sent: Wednesday, November 24, 2004 9:39 AM
>>>>>>>>> To: Alan Clark
>>>>>>>>> Cc: Oren Peleg; avt@ietf.org
>>>>>>>>> Subject: RE: [AVT] RFC 3711 and RTCP
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> At 07:54 AM 11/24/2004 -0500, Alan Clark wrote:
>>>>>>>>>> Hi Oren
>>>>>>>>>>
>>>>>>>>>> Yes - encryption is intended to provide privacy however this
>>>>>>>>>> relates
>>>>>>>>>> primarily to the voice payloads and to information within RTCP
>>>>>>>>>> that
>>>>>>>>>> may be
>>>>>>>>>> associated with individual users (e.g. SDES).
>>>>>>>>>>
>>>>>>>>>> SR, RR and XR contain only peformance statistics and
>>>> there is no
>>>>>>>>>> privacy
>>>>>>>>>> consideration that I can think of related to this type of 
>>>>>>>>>> data.
>>>>>>>>>>
>>>>>>>>>> The message is - encrypt RTP, optionally encrypt RTCP SDES but
>>>>>>>>>> don't
>>>>>>>>> encrypt
>>>>>>>>>> RTCP SR/RR/XR
>>>>>>>>>
>>>>>>>>> Hi Alan,
>>>>>>>>>
>>>>>>>>> I am wondering about implementations utilizing your advise
>>>>>>>>> "optionally
>>>>>>>>> encrypt
>>>>>>>>> RTCP SDES but don't encrypt RTCP SR/RR/XR".
>>>>>>>>>
>>>>>>>>> Is there an easy way to tell SRTP to encrypt RTCP SDES, but not
>>>>>>>>> RTCP
>>>>>>>>> SR/RR/XR? It seems that all the RTCP blocks would otherwise be
>>>>>>>>> highly
>>>>>>>>> related to each other. For example (quote out of RFC 3611):
>>>>>>>>>
>>>>>>>>> "XR packets supplement the existing RTCP packets, and may be
>>>>>>>>> stacked
>>>>>>>>> with
>>>>>>>>> other RTCP packets to form compound RTCP packets [9,
>>>> Section 6]."
>>>>>>>>>
>>>>>>>>> Thus, RFC3611 explicitly admits the possibility of (but does 
>>>>>>>>> not
>>>>>>>>> mandate)
>>>>>>>>> the piggybacking all the RTCP-XR block types.
>>>>>>>>>
>>>>>>>>> RTCP implementations would have to know the SRTP
>>>> encryption rules
>>>>>>>>> to
>>>>>>>>> make sure they don't perform piggybacking with SDES ...
>>>> but could
>>>>>>>>> allow
>>>>>>>>> (the more bandwidth efficient) piggybacking on the other 
>>>>>>>>> RTCP-XR
>>>>>>>>> blocks.
>>>>>>>>>
>>>>>>>>> This RTCP/SRTP interaction/dependency seems to add a
>>>> burden to both
>>>>>>>>> RTCP and SRTP implementations ... let alone the expressiveness
>>>>>>>>> required
>>>>>>>>> to signal your advise in existing SDP/SRTP mechanisms.
>>>>>>>>>
>>>>>>>>> Are you aware of any implementations that have actually 
>>>>>>>>> followed
>>>>>>>>> your
>>>>>>>>> advise above? I rather go into this one with our eyes open ...
>>>>>>>>> developers
>>>>>>>>> highly dislike this cross-functional entity dependency
>>>> (RTCP & SRTP
>>>>>>>>> along
>>>>>>>>> with expressing it in SDP/SRTP mechanisms).
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Michael Ramalho
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Regards
>>>>>>>>>>
>>>>>>>>>> Alan
>>>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: Oren Peleg [mailto:OrenP@audiocodes.com]
>>>>>>>>>> Sent: Wednesday, November 24, 2004 7:50 AM
>>>>>>>>>> To: Alan Clark; avt@ietf.org
>>>>>>>>>> Subject: RE: [AVT] RFC 3711 and RTCP
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Isnt encryption is to prevent monitoring from the first place?
>>>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: avt-bounces@ietf.org
>>>> [mailto:avt-bounces@ietf.org] On Behalf
>>>>>>>>>> Of
>>>>>>>>>> Alan Clark
>>>>>>>>>> Sent: Tuesday, November 23, 2004 5:42 PM
>>>>>>>>>> To: avt@ietf.org
>>>>>>>>>> Subject: [AVT] RFC 3711 and RTCP
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> From the flurry of discussion on RFC3711 it looks as
>>>> if there is
>>>>>>>>>> considerable interest in SRTP implementation.  I'd
>>>> like to add a
>>>>>>>>>> request
>>>>>>>>>> to
>>>>>>>>>> SRTP implementors with regard to manageability.
>>>>>>>>>>
>>>>>>>>>> RTCP SR, RR and more particularly XR (e.g. VoIP Metrics report
>>>>>>>>>> block)
>>>>>>>>>> contain useful information for network monitoring, and
>>>> are often
>>>>>>>>>> used by
>>>>>>>>>> probes and analyzers to support problem diagnosis.
>>>> RFC3711 allows
>>>>>>>>>> the
>>>>>>>>>> selective encryption of RTCP payloads and hence I
>>>> would strongly
>>>>>>>>>> recomment
>>>>>>>>>> that RFC3711 implementors DO NOT encrypt RTCP SR, RR and XR
>>>>>>>>>> payloads
>>>>>>>>>> as
>>>>>>>>>> this
>>>>>>>>>> adversely impacts manageability.
>>>>>>>>>>
>>>>>>>>>> Regards
>>>>>>>>>>
>>>>>>>>>> Alan Clark
>>>>>>>>>> Telchemy
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Audio/Video Transport Working Group
>>>>>>>>>> avt@ietf.org
>>>>>>>>>> https://www1.ietf.org/mailman/listinfo/avt
>>>>>>>>>>
>>>> ******************************************************************
>>>>>>>>>> **
>>>>>>>>>> *
>>>>>>>>>> ******
>>>>>>>>> *
>>>>>>>>>> ********************************
>>>>>>>>>> This email and any files transmitted with it are confidential
>>>>>>>>>> material.
>>>>>>>>>> They are intended solely for the use of the designated
>>>> individual
>>>>>>>>>> or
>>>>>>>>>> entity
>>>>>>>>>> to whom they are addressed.
>>>>>>>>>> If the reader of this message is not the intended recipient,
>>>>>>>>>> you are hereby notified that any dissemination,use,
>>>>>>>>>> distribution or copying of this communication is strictly
>>>>>>>>>> prohibited
>>>>>>>>>> and
>>>>>>>>> may
>>>>>>>>>> be unlawful.
>>>>>>>>>>
>>>>>>>>>> If you have received this email in error please notify
>>>>>>>>>> postmaster@audiocodes.com and permanently delete the e-mail 
>>>>>>>>>> and
>>>>>>>>>> files.
>>>>>>>>>>
>>>>>>>>>>
>>>> ******************************************************************
>>>>>>>>>> **
>>>>>>>>>> *
>>>>>>>>>> ******
>>>>>>>>> *
>>>>>>>>>> *******************************
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> 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
>>>>>>>> David R. Oran
>>>>>>>> Cisco Fellow
>>>>>>>> Cisco Systems
>>>>>>>> 7 Ladyslipper Lane
>>>>>>>> Acton, MA 01720 USA
>>>>>>>> Tel: +1 978 264 2048
>>>>>>>> Email: oran@cisco.com
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>
>>>>
>>>> _______________________________________________
>>>> mmusic mailing list
>>>> mmusic@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/mmusic
>>>
>>> _______________________________________________
>>> 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
>

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


From avt-bounces@ietf.org  Wed Dec  8 16:32:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04997
	for <avt-archive@ietf.org>; Wed, 8 Dec 2004 16:32:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cc9Wt-00082u-OH
	for avt-archive@ietf.org; Wed, 08 Dec 2004 16:39:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cc9D6-0007en-O4; Wed, 08 Dec 2004 16:18:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cc9BK-0006qu-9K; Wed, 08 Dec 2004 16:17:06 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04207;
	Wed, 8 Dec 2004 16:17:04 -0500 (EST)
Message-Id: <200412082117.QAA04207@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 08 Dec 2004 16:17:04 -0500
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-midi-guidelines-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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632

--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		: An Implementation Guide for RTP MIDI
	Author(s)	: J. Lazzaro, J. Wawrzynek
	Filename	: draft-ietf-avt-rtp-midi-guidelines-07.txt
	Pages		: 38
	Date		: 2004-12-8
	
This memo offers non-normative implementation guidance for the RTP
     MIDI payload format.  The memo presents its advice in the context
     of a network musical performance application.  In this application
     two musicians, located in different physical locations, interact
     over a network to perform as they would if located in the same
     room.  Underlying the performances are RTP MIDI sessions over
     unicast UDP.  Algorithms for sending and receiving recovery
     journals (the resiliency structure for the payload format) are
     described in detail.  Although the memo focuses on network musical
     performance, the presented implementation advice is relevant to
     other RTP MIDI applications.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-midi-guidelines-07.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-midi-guidelines-07.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-midi-guidelines-07.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: <2004-12-8164702.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-midi-guidelines-07.txt

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

Content-Type: text/plain
Content-ID: <2004-12-8164702.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org  Wed Dec  8 16:34:45 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05193
	for <avt-archive@ietf.org>; Wed, 8 Dec 2004 16:34:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cc9ZI-000864-Iu
	for avt-archive@ietf.org; Wed, 08 Dec 2004 16:41:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cc9DA-0007gI-5n; Wed, 08 Dec 2004 16:19:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cc9BS-0006sV-QE; Wed, 08 Dec 2004 16:17:14 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04215;
	Wed, 8 Dec 2004 16:17:12 -0500 (EST)
Message-Id: <200412082117.QAA04215@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 08 Dec 2004 16:17:12 -0500
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-midi-format-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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632

--NextPart

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

	Title		: RTP Payload Format for MIDI
	Author(s)	: J. Lazzaro, J. Wawrzynek
	Filename	: draft-ietf-avt-rtp-midi-format-07.txt
	Pages		: 158
	Date		: 2004-12-8
	
This memo describes an RTP payload format for the MIDI command
language.  The format encodes all commands that may legally appear
on a MIDI 1.0 DIN cable.  The format is suitable for interactive
applications (such as the remote operation of musical instruments)
and content-delivery applications (such as file streaming).  The
format may be used over unicast and multicast UDP as well as TCP,
and defines tools for graceful recovery from packet loss.  Stream
behavior, including the MIDI rendering method, may be customized
during session setup.  The format also serves as a mode for the
mpeg4-generic format, to support the MPEG 4 Audio Object Types for
General MIDI, Downloadable Sounds Level 2, and Structured Audio.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-midi-format-07.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-midi-format-07.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-midi-format-07.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: <2004-12-8164720.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-midi-format-07.txt

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

Content-Type: text/plain
Content-ID: <2004-12-8164720.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org  Wed Dec  8 18:30:36 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25059
	for <avt-archive@ietf.org>; Wed, 8 Dec 2004 18:30:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcBNN-0005WI-K5
	for avt-archive@ietf.org; Wed, 08 Dec 2004 18:37:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcB80-0002kx-M5; Wed, 08 Dec 2004 18:21:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcAqo-0000nn-7N
	for avt@megatron.ietf.org; Wed, 08 Dec 2004 18:04:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21160
	for <avt@ietf.org>; Wed, 8 Dec 2004 18:03:59 -0500 (EST)
Received: from relay0.eecs.berkeley.edu ([169.229.60.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcAxf-0004c4-NI
	for avt@ietf.org; Wed, 08 Dec 2004 18:11:08 -0500
Received: from gateway2.EECS (gateway2.EECS.Berkeley.EDU [169.229.60.39])
	by relay0.EECS.Berkeley.EDU (8.13.1/8.12.10) with ESMTP id
	iB8N40to020008
	for <avt@ietf.org>; Wed, 8 Dec 2004 15:04:00 -0800 (PST)
Received: from [128.32.34.73] (dhcp-34-73.CS.Berkeley.EDU [128.32.34.73])
	by gateway2.EECS.Berkeley.EDU
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTPSA id <0I8F00BYEEQOID@gateway2.EECS.Berkeley.EDU> for
	avt@ietf.org; Wed, 08 Dec 2004 15:04:00 -0800 (PST)
Date: Wed, 08 Dec 2004 15:03:59 -0800
From: lazzaro <lazzaro@eecs.berkeley.edu>
To: avt@ietf.org
Message-id: <722782CE-496D-11D9-9AD9-00039372C384@eecs.berkeley.edu>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; charset=US-ASCII; format=flowed
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7BIT
Subject: [AVT] Refresh of contrans I-D ...
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7BIT

Hi everyone,

	Just sent off draft-ietf-avt-rtp-framing-contrans-04.txt
to Internet-Drafts.  See a mirror copy here:

http://www.cs.berkeley.edu/~lazzaro/files/ietf/contrans-04.txt

	This version updates SDP syntax in the examples to
match the latest comedia syntax, and also brings it inline with
the idnits web service.

	There didn't appear to be consensus on TCP/RTP/AVPF,
so it is not defined in the document.

	From the RTP MIDI perspective, I'm happy with contrans
as is and think we're ready for Last Call, but there may be other
reasons why its best to wait (synchronization with comedia in
the standardization process, etc).

---
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 Dec  9 04:05:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03894
	for <avt-archive@ietf.org>; Thu, 9 Dec 2004 04:05:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcKLc-0008OL-Gu
	for avt-archive@ietf.org; Thu, 09 Dec 2004 04:12:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcK7p-0005sn-Qf; Thu, 09 Dec 2004 03:58:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cc7Ei-0008LN-Uh
	for avt@megatron.ietf.org; Wed, 08 Dec 2004 14:12:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25319
	for <avt@ietf.org>; Wed, 8 Dec 2004 14:12:27 -0500 (EST)
Received: from mavis.erg.abdn.ac.uk ([139.133.204.77] helo=erg.abdn.ac.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cc7LV-0005KI-W8
	for avt@ietf.org; Wed, 08 Dec 2004 14:19:32 -0500
Received: from erg.abdn.ac.uk (gresley.erg.abdn.ac.uk [139.133.207.106])
	(authenticated bits=0)
	by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id iB8JAnrI026026
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Wed, 8 Dec 2004 19:10:50 GMT
Message-ID: <41B751BA.3010102@erg.abdn.ac.uk>
Date: Wed, 08 Dec 2004 19:10:50 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: Univesrity of Aberdeen
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: avt@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
X-ERG-MailScanner-To: avt@ietf.org, johan.sjoberg@ericsson.com, mankin@psg.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 09 Dec 2004 03:58:11 -0500
Cc: Johan.Sjoberg@ericsson.com
Subject: [AVT] draft-ietf-avt-rtp-amr-bis-00.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 7bit


I've just been doing a little reading of drafts from other WGs and had some 
questions about the design rationale of the above ID:


I notice that in section 4.4.2.1, it says:

    "The frame CRC, when used, MUST be calculated only over all class A
     bits in the frame.  Class B and C bits in the frame MUST NOT be
     included in the CRC calculation and SHOULD NOT be covered by the
     transport checksum."

I wonder if this could be justified?

At first read, this seems to go exactly the opposite way to what was written 
in UDP-Lite [RFC3828], section 4.

    ...."For a link that supports
    partial error detection, the Checksum Coverage field in the UDP-Lite
    header MAY be used as a hint of where errors do not need to be
    detected.  Lower layers MUST use a strong error detection mechanism
    [RFC-3819] to detect at least errors that occur in the sensitive part
    of the packet, and discard damaged packets."

So my take on this was, UDP-Lite says you MUST perform a check on the IP 
headers, and any fields covered by the Checksum coverage, but that you MAY 
relax this to only cover the Checksum coverage for UDP-Lite frames. If we're 
changing the recommendation, then this introduces new issues that really need 
to be discussed.

Later, the ID also says:

    "Packets SHOULD be discarded if the transport layer checksum detects
     errors."

- Is there any justification why that is not a MUST be discarded, since the 
check indicates the header IS mangled, and therefore there is little 
confidence in using the packet header? Again it seems the opposite to 
envisaged with UDP-Lite. Where UDP-Lite says, section 6:

    ..."Corruption of any bit within
    the protected area will then result in the IP receiver discarding the
    UDP-Lite packet."

I'm not sure if this was a mistake or a design strategy. Can you tell me?

Best wishes,

Gorry Fairhurst

(please cc me directly as well as via the list - so I can pick up the thread).




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


From avt-bounces@ietf.org  Thu Dec  9 05:34:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09900
	for <avt-archive@ietf.org>; Thu, 9 Dec 2004 05:34:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcLjv-0001jd-1J
	for avt-archive@ietf.org; Thu, 09 Dec 2004 05:41:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcLVs-0004Cc-2X; Thu, 09 Dec 2004 05:27:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcLNU-0002ST-Hs
	for avt@megatron.ietf.org; Thu, 09 Dec 2004 05:18:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08595
	for <avt@ietf.org>; Thu, 9 Dec 2004 05:18:26 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcLUH-0001O7-Nd
	for avt@ietf.org; Thu, 09 Dec 2004 05:25:40 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iB9AIGO6010781 for <avt@ietf.org>; Thu, 9 Dec 2004 11:18:16 +0100
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by
	esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 9 Dec 2004 11:18:16 +0100
Received: from [147.214.34.68] (research-1fd0e1.ki.sw.ericsson.se
	[147.214.34.68]) by esealnt613.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id YLNK61Z9; Thu, 9 Dec 2004 11:18:16 +0100
Message-ID: <41B82668.30602@ericsson.com>
Date: Thu, 09 Dec 2004 11:18:16 +0100
X-Sybari-Trust: 449a36ef 96d33411 2a63e42e 00000138
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: gorry@erg.abdn.ac.uk
Subject: Re: [AVT] draft-ietf-avt-rtp-amr-bis-00.txt
References: <41B751BA.3010102@erg.abdn.ac.uk>
In-Reply-To: <41B751BA.3010102@erg.abdn.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Dec 2004 10:18:16.0447 (UTC)
	FILETIME=[65D6D8F0:01C4DDD8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Content-Transfer-Encoding: 7bit
Cc: =?ISO-8859-1?Q?=22Johan_Sj=F6berg_=28KI/EAB=29=22?=
	<Johan.Sjoberg@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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Content-Transfer-Encoding: 7bit

Hi Gorry,

I hope that you are aware that this draft is an update of RFC 3267, 
which mainly intends to fixes the lack of an offer-answer section. 
However if we conclude that any of these normative text is wrong we 
should definitely consider changing it. But any backwards compatibility 
issues must be considered. The payload format is rather well deployed, 
however I think the CRC mode is very seldom or may be not at all used. 
Both the robust sorting and the CRC mode are specifically designed for 
UDP-Lite type of partial checksums.

I would also note that this format was finished long before UDP-Lite was 
approved and went through the last round of changes.

See further below.

Gorry Fairhurst wrote:
> 
> I've just been doing a little reading of drafts from other WGs and had some
> questions about the design rationale of the above ID:
> 
> 
> I notice that in section 4.4.2.1, it says:
> 
>     "The frame CRC, when used, MUST be calculated only over all class A
>      bits in the frame.  Class B and C bits in the frame MUST NOT be
>      included in the CRC calculation and SHOULD NOT be covered by the
>      transport checksum."
> 
> I wonder if this could be justified?
> 
> At first read, this seems to go exactly the opposite way to what was 
> written
> in UDP-Lite [RFC3828], section 4.
> 
>     ...."For a link that supports
>     partial error detection, the Checksum Coverage field in the UDP-Lite
>     header MAY be used as a hint of where errors do not need to be
>     detected.  Lower layers MUST use a strong error detection mechanism
>     [RFC-3819] to detect at least errors that occur in the sensitive part
>     of the packet, and discard damaged packets."
> 
> So my take on this was, UDP-Lite says you MUST perform a check on the IP
> headers, and any fields covered by the Checksum coverage, but that you MAY
> relax this to only cover the Checksum coverage for UDP-Lite frames. If 
> we're
> changing the recommendation, then this introduces new issues that really 
> need
> to be discussed.
> 

I don't the text in section 4.4.2.1 that you quote is contradicting 
UDP-Lite at all. The CRC mode is specifically designed for partial 
checksums from the beginning. The bits in a AMR audio frame is sorted in 
sensitivity order, with the most sensitive bits first and the least 
last. This is utilized in circuit switched channel coding to provide 
three levels of protection A, which are so sensitive that any errors 
results in those bits not being used. A class B that has less protection 
but still needs lower bit-error rates than the class C bits that use the 
channel as is. The channel error rates are of course tuned to what the 
codec can accept in both bit-errors and frame erasures. Also if the 
class A bits are damaged as detected by the CRC (present also in the CS 
transport) some of the class B and C bits are used.

Due to this characteristics of the codec, the CRC was included to 
provide maximum performance for RTP payload with multiple AMR frames. 
The per frame CRC allows the complete section of data frames to be 
unprotected by UDP-Lite. Bit-errors in the sensitive class A bits are 
detected by the CRC, and in that case the frame is marked as damaged and 
some of the B and C bits for that frame are used in concealment.

The intention of the CRC mode compared to Robust sorting was to reduce 
the part that needs strong protection when aggregating multiple frames 
into a packet compared to the Robust Sorting mode. In the robust sorting 
mode, the complete payload data part is sorted byte-wise into decreasing 
order of sensitivity to bit-errors. In Robust sorting mode the intention 
is to cover the class A bits with the UDP-Lite checksum instead.

In conclusion I think this can be motivated.


> Later, the ID also says:
> 
>     "Packets SHOULD be discarded if the transport layer checksum detects
>      errors."
> 
> - Is there any justification why that is not a MUST be discarded, since the
> check indicates the header IS mangled, and therefore there is little
> confidence in using the packet header? Again it seems the opposite to
> envisaged with UDP-Lite. Where UDP-Lite says, section 6:
> 
>     ..."Corruption of any bit within
>     the protected area will then result in the IP receiver discarding the
>     UDP-Lite packet."
> 
> I'm not sure if this was a mistake or a design strategy. Can you tell me?
> 

I am not certain why it says SHOULD rather than MUST. It was probably a 
case of given a little to much freedom to the implementors. In fact 
there are basically no fields where a bit-error could be present without 
resulting in serious problems for the playing application. Some 
bit-errors would result in inconsistent payload forcing one to discard 
it anyway. Others would result in misinterpretation of the result. For 
example a timestamp error would place the frame wrongly in time, which I 
consider quite serious. The backwards compatibility issues with changing 
this seem to be almost non-existent. If someone actually has taken on 
all the hassle to make an implementation that accept UDP-Lite packets 
with failed checksum and handles it correctly, fine they can keep it 
without affecting some else. The effect of the change would also only 
give the implementors a clearer implementation statement.

A better proposal may be to rewrite that sentence to simple note that 
any packets with errors detected by the UDP-Lite checksum or lower layer 
in that part will be discarded and never delivered.

Please provide more feedback if such a change is appropriate.


Cheers


Magnus Westerlund

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  Thu Dec  9 11:59:39 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10274
	for <avt-archive@ietf.org>; Thu, 9 Dec 2004 11:59:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcRkm-0001Mi-39
	for avt-archive@ietf.org; Thu, 09 Dec 2004 12:06:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcRVv-0007es-TH; Thu, 09 Dec 2004 11:51:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcROc-0005qQ-EB
	for avt@megatron.ietf.org; Thu, 09 Dec 2004 11:44:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09348
	for <avt@ietf.org>; Thu, 9 Dec 2004 11:44:00 -0500 (EST)
Received: from wproxy.gmail.com ([64.233.184.200])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcRVc-000143-5E
	for avt@ietf.org; Thu, 09 Dec 2004 11:51:17 -0500
Received: by wproxy.gmail.com with SMTP id 37so861261wra
	for <avt@ietf.org>; Thu, 09 Dec 2004 08:43:29 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding;
	b=dZ+2lwvwnEFgDRSbU7O3BjD2uDGcMW8bJKcNYus/94KNBQPJFmG/JvV89+sr5ppVaDOLf1yxqDU44WO8UnhBRgRZeHlyUBh3ShBpOfqj3n8c6n3bkKRkv6EqWJU7cvDhxpU2SL25gIDA1kEF3DzFhIIHKimo2uwWrkctwKBUX0c=
Received: by 10.54.39.9 with SMTP id m9mr878985wrm;
	Thu, 09 Dec 2004 08:43:27 -0800 (PST)
Received: by 10.54.46.69 with HTTP; Thu, 9 Dec 2004 08:43:27 -0800 (PST)
Message-ID: <6e5aff67041209084317d461ad@mail.gmail.com>
Date: Thu, 9 Dec 2004 13:43:27 -0300
From: Alejandro Cabrera Obed <aco1967@gmail.com>
To: AVT Lista <avt@ietf.org>, DCCP Lista <dccp@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit
Subject: [AVT] TFRC applied to HDTV uncompressed 1.5 Gbps
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Alejandro Cabrera Obed <aco1967@gmail.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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit

Dear people,

I'm from Argentina, developing a survey about HDTV uncompressed live
streaming over IP. I'm contacting you in order to know what you think
about applying TFRC to HDTV uncompressed live streaming (aprox. 1.5
Gbps), in order to get congestion control.

1) Do you think there is any limitation in applying the TFRC mechanism
to my scenario ???

2) Is it correct the use of RTCP like a feedback mechanism for TFRC,
taking the RTCP throughput at about 5% of 1.5 Gbps ???

Maybe, if TRFC is OK to HDTV uncompressed, I'm interesting in studying
into account the use of LSR and DLSR fields of RR in order to
calculate the RTT.

Thanks a lot, I appreciate your opinion.

 
Alejandro Cabrera Obed

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


From avt-bounces@ietf.org  Thu Dec  9 13:05:05 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16535
	for <avt-archive@ietf.org>; Thu, 9 Dec 2004 13:05:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcSm7-0002rP-IQ
	for avt-archive@ietf.org; Thu, 09 Dec 2004 13:12:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcSYL-0004ga-MR; Thu, 09 Dec 2004 12:58:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcSV4-0003Jw-4C
	for avt@megatron.ietf.org; Thu, 09 Dec 2004 12:54:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15429
	for <avt@ietf.org>; Thu, 9 Dec 2004 12:54:43 -0500 (EST)
Received: from mavis.erg.abdn.ac.uk ([139.133.204.77] helo=erg.abdn.ac.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcSc3-0002cu-6A
	for avt@ietf.org; Thu, 09 Dec 2004 13:02:02 -0500
Received: from [10.0.1.109] (maxp15.abdn.ac.uk [139.133.7.174])
	(authenticated bits=0)
	by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id iB9HqQdm025871
	(version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT);
	Thu, 9 Dec 2004 17:52:35 GMT
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Thu, 09 Dec 2004 16:50:38 +0000
Subject: Re: [AVT] draft-ietf-avt-rtp-amr-bis-00.txt
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <BDDE32DE.1ADC%gorry@erg.abdn.ac.uk>
In-Reply-To: <41B82668.30602@ericsson.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
X-ERG-MailScanner-To: avt@ietf.org, johan.sjoberg@ericsson.com,
	magnus.westerlund@ericsson.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ed68cc91cc637fea89623888898579ba
Content-Transfer-Encoding: 7bit
Cc: "Johan Sj=?ISO-8859-1?B?9g==?=berg \(KI/EAB\)"
	<Johan.Sjoberg@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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ce732c7d36989a1bd55104ba259c40a1
Content-Transfer-Encoding: 7bit

I've numbered the issues, to try to help us quickly agree on what the
problem is/was.

On 9/12/04 10:18 am, "Magnus Westerlund" <magnus.westerlund@ericsson.com>
wrote:

> Hi Gorry,
> 
> I hope that you are aware that this draft is an update of RFC 3267,
> which mainly intends to fixes the lack of an offer-answer section.

Yes - and it seems a good application for UDP-Lite, which was what
interested me.

> However if we conclude that any of these normative text is wrong we
> should definitely consider changing it. But any backwards compatibility
> issues must be considered. The payload format is rather well deployed,
> however I think the CRC mode is very seldom or may be not at all used.
> Both the robust sorting and the CRC mode are specifically designed for
> UDP-Lite type of partial checksums.
> 
> I would also note that this format was finished long before UDP-Lite was
> approved and went through the last round of changes.

Yes - and if so, then it explains the differences.

On looking through your response, I wonder how much of my response is due to
there being two types of "frames" link-frame and payload-codec-frames, each
with their own CRC's. Normally I'd not expect RTP documents to mention link
frames, but use of UDP-Lite naturally leads to comments on link frames. If
this differentiation can be clearer, then the issues can be localised to
section 3.6.1 (which seems perhaps to be the correct place to discuss IP,
Link and UDP-Lite).

> See further below.
> 
> Gorry Fairhurst wrote:
>> 
>> I've just been doing a little reading of drafts from other WGs and had some
>> questions about the design rationale of the above ID:
>> 
>> 
>> I notice that in section 4.4.2.1, it says:
>> 
>>     "The frame CRC, when used, MUST be calculated only over all class A
>>      bits in the frame.  Class B and C bits in the frame MUST NOT be
>>      included in the CRC calculation and SHOULD NOT be covered by the
>>      transport checksum."
>> 
>> I wonder if this could be justified?
>> 
>> At first read, this seems to go exactly the opposite way to what was
>> written
>> in UDP-Lite [RFC3828], section 4.
>> 
>>     ...."For a link that supports
>>     partial error detection, the Checksum Coverage field in the UDP-Lite
>>     header MAY be used as a hint of where errors do not need to be
>>     detected.  Lower layers MUST use a strong error detection mechanism
>>     [RFC-3819] to detect at least errors that occur in the sensitive part
>>     of the packet, and discard damaged packets."
>> 
>> So my take on this was, UDP-Lite says you MUST perform a check on the IP
>> headers, and any fields covered by the Checksum coverage, but that you MAY
>> relax this to only cover the Checksum coverage for UDP-Lite frames. If
>> we're
>> changing the recommendation, then this introduces new issues that really
>> need
>> to be discussed.
>> 
> 
> I don't the text in section 4.4.2.1 that you quote is contradicting
> UDP-Lite at all.

OK - if that's the case, we can agree.

1) There's a subtle difference between what is expected Link behaviour as
described by UDP-Lite, and what this ID seems to suggest at the moment. This
lies in whether the Link-Layer does full frame protection; unequal
protection; or NO protection.

Experience with SLIP, etc, showed that NO protection of IP and transport
headers was bad - I would expect the concerns to be greater with IPv6 (where
there is no IP checksum), cite RFC3819 on use of link CRCs?

One thing I'd propose is to recommend a mode were all protocol headers up to
and including the class A bits in the frame are protected by a link-frame
CRC; you could cite UDP-Lite as clarification?

Would this impact any known usage? - Or is it only a clarification?

Of course, it is in practice hard for the IETF to mandate use of partial
(unequal) CRC protection at the link layer, never-the-less in my opinion, it
would be very wrong to encourage use of links with NO protection for IP.


2) Looking back, the current text in 3.6.1 seems to have a focus on RTP
issues (it is an AVT draft), but also touches on the implications for IP
networks. Perhaps a little more clarity here would prevent confusion (at
least for me). 

Suggestions are: Be clear which types of frame is being mentioned. It would
be good  to mention  the network and transport (i.e. UDP/UDP-Lite) headers
explicitly in your discussion. For example:

   "  1) Utilizing a partial checksum to cover headers and the most
       important speech bits of the payload."

Could become:
   "  1) Utilizing a partial checksum to cover protocol headers (i.e., IP
network headers, UDP/UDP-Lite transport headers; RTP headers; and RTP
payload headers) together with the most important speech bits of the
payload."

Etc.

Is this what was meant?


> The CRC mode is specifically designed for partial
> checksums from the beginning. The bits in a AMR audio frame is sorted in
> sensitivity order, with the most sensitive bits first and the least
> last. This is utilized in circuit switched channel coding to provide
> three levels of protection A, which are so sensitive that any errors
> results in those bits not being used. A class B that has less protection
> but still needs lower bit-error rates than the class C bits that use the
> channel as is. The channel error rates are of course tuned to what the
> codec can accept in both bit-errors and frame erasures. Also if the
> class A bits are damaged as detected by the CRC (present also in the CS
> transport) some of the class B and C bits are used.
> 
This was what I thought, so that is good.

> Due to this characteristics of the codec, the CRC was included to
> provide maximum performance for RTP payload with multiple AMR frames.
> The per frame CRC allows the complete section of data frames to be
> unprotected by UDP-Lite. Bit-errors in the sensitive class A bits are
> detected by the CRC, and in that case the frame is marked as damaged and
> some of the B and C bits for that frame are used in concealment.
> 
Yes.
> The intention of the CRC mode compared to Robust sorting was to reduce
> the part that needs strong protection when aggregating multiple frames
> into a packet compared to the Robust Sorting mode. In the robust sorting
> mode, the complete payload data part is sorted byte-wise into decreasing
> order of sensitivity to bit-errors. In Robust sorting mode the intention
> is to cover the class A bits with the UDP-Lite checksum instead.
> 
> In conclusion I think this can be motivated.
> 
This sounds like the correct thing to do.
> 
>> Later, the ID also says:
>> 
>>     "Packets SHOULD be discarded if the transport layer checksum detects
>>      errors."
>> 
>> - Is there any justification why that is not a MUST be discarded, since the
>> check indicates the header IS mangled, and therefore there is little
>> confidence in using the packet header? Again it seems the opposite to
>> envisaged with UDP-Lite. Where UDP-Lite says, section 6:
>> 
>>     ..."Corruption of any bit within
>>     the protected area will then result in the IP receiver discarding the
>>     UDP-Lite packet."
>> 
>> I'm not sure if this was a mistake or a design strategy. Can you tell me?
>> 
> 
> I am not certain why it says SHOULD rather than MUST. It was probably a
> case of given a little to much freedom to the implementors. In fact
> there are basically no fields where a bit-error could be present without
> resulting in serious problems for the playing application. Some
> bit-errors would result in inconsistent payload forcing one to discard
> it anyway. Others would result in misinterpretation of the result. For
> example a timestamp error would place the frame wrongly in time, which I
> consider quite serious. The backwards compatibility issues with changing
> this seem to be almost non-existent. If someone actually has taken on
> all the hassle to make an implementation that accept UDP-Lite packets
> with failed checksum and handles it correctly, fine they can keep it
> without affecting some else. The effect of the change would also only
> give the implementors a clearer implementation statement.
> 

3) Looking at the ID, I think the problem I had actually was in section 3.6
which speaks (I think) about Link-layer frames. If this was to be made
clear, then this section could refer back to it (and remove the potential
for confusion).

 " The frame CRC, when used, MUST be calculated only over all class A
    bits in the frame."

- Which "frame" is this about? - I think this is the payload-codec-frame of
RTP?

4)  A correct UDP-Lite implementation MUST discard these packets (this is
also the way DCCP is expected to behave when using partial checksum
coverage).  Of course AMR can also be used over non-IP transports, and then
you rely on their multiplexing and control functions to supply the bit
stream that AMR uses.

The rationale for IP transport was that allowing these packets to pass up
the stack with no verification of the IP header (in IPv6) or UDP-Lite header
(IPv4,IPv6), could result in cases of mis-delivery of arbitary corrupted
packets to *any* port, and applications do not generally have an ability to
handle such events robustly (with serious implications). So, unless there is
a strong argument, I'd recommend that if you use an IP network, you MUST use
a transport layer checksum.

> A better proposal may be to rewrite that sentence to simple note that
> any packets with errors detected by the UDP-Lite checksum or lower layer
> in that part will be discarded and never delivered.
> 

Exactly:-)

> Please provide more feedback if such a change is appropriate.
> 
> 
> Cheers
> 
> 
> Magnus Westerlund
> 
> 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
> 

I'm relieved we were closer than I thought... Are there still points of
disagreement?

Gorry



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


From avt-bounces@ietf.org  Thu Dec  9 13:58:11 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21313
	for <avt-archive@ietf.org>; Thu, 9 Dec 2004 13:58:11 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcTbU-00041u-Ga
	for avt-archive@ietf.org; Thu, 09 Dec 2004 14:05:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcTMI-0000MR-Qi; Thu, 09 Dec 2004 13:49:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcTEX-0006Hz-T2; Thu, 09 Dec 2004 13:41:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19900;
	Thu, 9 Dec 2004 13:41:45 -0500 (EST)
Received: from mail.sonusnet.com ([208.45.178.33] helo=revere.sonusnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcTLZ-0003cd-TL; Thu, 09 Dec 2004 13:49:02 -0500
Received: from sonusms1.sonusnet.com (sonusms1 [10.128.32.93])
	by revere.sonusnet.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	iB9IfCKX029993; Thu, 9 Dec 2004 13:41:12 -0500 (EST)
Received: from sonusmail03.sonusnet.com (unverified) by sonusms1.sonusnet.com
	(Content Technologies SMTPRS 4.3.12) with ESMTP id
	<T6dc478958e0a80205d3a4@sonusms1.sonusnet.com>; 
	Thu, 9 Dec 2004 13:41:12 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 9 Dec 2004 13:41:11 -0500
Message-ID: <A3863F3136CBC546A40A61BA9CBA9D93079C30@sonusmail03.sonusnet.com>
Thread-Topic: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps
Thread-Index: AcTeEKCgCWo68JWNRiGPbly3r/+jwQAC0r2g
From: "Phelan, Tom" <tphelan@sonusnet.com>
To: "Alejandro Cabrera Obed" <aco1967@gmail.com>, "AVT Lista" <avt@ietf.org>,
        "DCCP Lista" <dccp@ietf.org>
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: quoted-printable
Subject: [AVT] RE: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: quoted-printable

Hi Alejandro,

See inline ...

Tom Phelan

> -----Original Message-----
> From: Alejandro Cabrera Obed [mailto:aco1967@gmail.com]
> Sent: Thursday, December 09, 2004 11:43 AM
> To: AVT Lista; DCCP Lista
> Subject: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps
>=20
>=20
> Dear people,
>=20
> I'm from Argentina, developing a survey about HDTV uncompressed live
> streaming over IP. I'm contacting you in order to know what you think
> about applying TFRC to HDTV uncompressed live streaming (aprox. 1.5
> Gbps), in order to get congestion control.
>=20
> 1) Do you think there is any limitation in applying the TFRC mechanism
> to my scenario ???

I think there's two issues you'll need to deal with.  One is slow start =
- it'll take a good number of round trip times to get up to 1.5G bps.  =
The other is, what will you do when there is congestion and you must =
reduce the transmit rate?  I assume you'll be using large packets to get =
that high a transmit rate, so the small packet issues shown in =
http://www.phelan-4.com/dccp/tfrc-self-limit.pdf won't be a problem.

> 2) Is it correct the use of RTCP like a feedback mechanism for TFRC,
> taking the RTCP throughput at about 5% of 1.5 Gbps ???

Normally TFRC requires one feedback packet per RTT.  So the RTCP 5% =
limit is a bit problematic.  The feedback is greater or less than 5% =
depending on the RTT.  I know this has been raised as a problem the RTP =
profile for TFRC - I'm not sure how Ladan has dealt with it.  For DCCP, =
there's no such restriction.  The DCCP feedback packets are fairly small =
- I don't remember the exact size, but using 40 bytes, you'd need an RTT =
of less than 5 microseconds to use up 5% of 1.5G on the feedback.

>=20
> Maybe, if TRFC is OK to HDTV uncompressed, I'm interesting in studying
> into account the use of LSR and DLSR fields of RR in order to
> calculate the RTT.
>=20
> Thanks a lot, I appreciate your opinion.
>=20
> =20
> Alejandro Cabrera Obed
>=20
> _______________________________________________
> dccp IETF mailing list: dccp@ietf.org
> list info:  https://www1.ietf.org/mailman/listinfo/dccp
> wg charter: http://www.ietf.org/html.charters/dccp-charter.html
>=20

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


From avt-bounces@ietf.org  Thu Dec  9 14:31:30 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24632
	for <avt-archive@ietf.org>; Thu, 9 Dec 2004 14:31:30 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcU7j-0004vc-Rt
	for avt-archive@ietf.org; Thu, 09 Dec 2004 14:38:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcTuT-0001tN-Rw; Thu, 09 Dec 2004 14:25:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcTmo-0007zD-Or; Thu, 09 Dec 2004 14:17:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23319;
	Thu, 9 Dec 2004 14:17:09 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcTtq-0004Y9-Sy; Thu, 09 Dec 2004 14:24:27 -0500
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:58835)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1CcTm9-0001o3-No; Thu, 09 Dec 2004 19:16:29 +0000
In-Reply-To: <A3863F3136CBC546A40A61BA9CBA9D93079C30@sonusmail03.sonusnet.com>
References: <A3863F3136CBC546A40A61BA9CBA9D93079C30@sonusmail03.sonusnet.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <D019C382-4A16-11D9-99D3-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Thu, 9 Dec 2004 19:16:22 +0000
To: "Phelan, Tom" <tphelan@sonusnet.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: 7bit
Cc: DCCP Lista <dccp@ietf.org>, AVT Lista <avt@ietf.org>
Subject: [AVT] Re: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 1.1 (+)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Content-Transfer-Encoding: 7bit

You would also have the issue of how to maintain acceptable viewing 
quality whilst varying the transmission rate. That problem is at least 
as difficult as the practicalities of making the TFRC mechanisms work 
(and note that you must either compress or discard data to do this in 
real-time, so using TFRC for "uncompressed" HDTV isn't practical if 
there might be congestion).

Colin



On 9 Dec 2004, at 18:41, Phelan, Tom wrote:

> Hi Alejandro,
>
> See inline ...
>
> Tom Phelan
>
>> -----Original Message-----
>> From: Alejandro Cabrera Obed [mailto:aco1967@gmail.com]
>> Sent: Thursday, December 09, 2004 11:43 AM
>> To: AVT Lista; DCCP Lista
>> Subject: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps
>>
>>
>> Dear people,
>>
>> I'm from Argentina, developing a survey about HDTV uncompressed live
>> streaming over IP. I'm contacting you in order to know what you think
>> about applying TFRC to HDTV uncompressed live streaming (aprox. 1.5
>> Gbps), in order to get congestion control.
>>
>> 1) Do you think there is any limitation in applying the TFRC mechanism
>> to my scenario ???
>
> I think there's two issues you'll need to deal with.  One is slow 
> start - it'll take a good number of round trip times to get up to 1.5G 
> bps.  The other is, what will you do when there is congestion and you 
> must reduce the transmit rate?  I assume you'll be using large packets 
> to get that high a transmit rate, so the small packet issues shown in 
> http://www.phelan-4.com/dccp/tfrc-self-limit.pdf won't be a problem.
>
>> 2) Is it correct the use of RTCP like a feedback mechanism for TFRC,
>> taking the RTCP throughput at about 5% of 1.5 Gbps ???
>
> Normally TFRC requires one feedback packet per RTT.  So the RTCP 5% 
> limit is a bit problematic.  The feedback is greater or less than 5% 
> depending on the RTT.  I know this has been raised as a problem the 
> RTP profile for TFRC - I'm not sure how Ladan has dealt with it.  For 
> DCCP, there's no such restriction.  The DCCP feedback packets are 
> fairly small - I don't remember the exact size, but using 40 bytes, 
> you'd need an RTT of less than 5 microseconds to use up 5% of 1.5G on 
> the feedback.
>
>>
>> Maybe, if TRFC is OK to HDTV uncompressed, I'm interesting in studying
>> into account the use of LSR and DLSR fields of RR in order to
>> calculate the RTT.
>>
>> Thanks a lot, I appreciate your opinion.
>>
>>
>> Alejandro Cabrera Obed
>>
>> _______________________________________________
>> dccp IETF mailing list: dccp@ietf.org
>> list info:  https://www1.ietf.org/mailman/listinfo/dccp
>> wg charter: http://www.ietf.org/html.charters/dccp-charter.html


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


From avt-bounces@ietf.org  Thu Dec  9 16:02:19 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03716
	for <avt-archive@ietf.org>; Thu, 9 Dec 2004 16:02:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcVXe-0006z3-MZ
	for avt-archive@ietf.org; Thu, 09 Dec 2004 16:09:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcVKw-0003q7-JV; Thu, 09 Dec 2004 15:56:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcV8o-0006XP-WC; Thu, 09 Dec 2004 15:43:59 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02399;
	Thu, 9 Dec 2004 15:43:57 -0500 (EST)
Message-Id: <200412092043.PAA02399@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 09 Dec 2004 15:43:57 -0500
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-amrwbplus-03.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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87

--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		: Real-Time Transport Protocol (RTP) Payload Format for 
			  Extended AMR Wideband (AMR-WB+) Audio Codec
	Author(s)	: J. Sjoberg, et al.
	Filename	: draft-ietf-avt-rtp-amrwbplus-03.txt
	Pages		: 35
	Date		: 2004-12-9
	
This document specifies a real-time transport protocol (RTP) payload
format to be used for Extended AMR Wideband (AMR-WB+) encoded audio
signals. The AMR-WB+ codec is an audio extension of the AMR-WB codec
providing additional modes designed to give higher quality of music
and speech than the original modes.  A MIME type registration is
included for AMR-WB+.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-amrwbplus-03.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-amrwbplus-03.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-amrwbplus-03.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: <2004-12-9155809.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-amrwbplus-03.txt

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

Content-Type: text/plain
Content-ID: <2004-12-9155809.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org  Thu Dec  9 16:12:42 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04782
	for <avt-archive@ietf.org>; Thu, 9 Dec 2004 16:12:41 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcVhh-0007Fn-4O
	for avt-archive@ietf.org; Thu, 09 Dec 2004 16:20:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcVKz-0003t5-Tj; Thu, 09 Dec 2004 15:56:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcV8u-0006Xv-6Z; Thu, 09 Dec 2004 15:44:04 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02408;
	Thu, 9 Dec 2004 15:44:02 -0500 (EST)
Message-Id: <200412092044.PAA02408@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 09 Dec 2004 15:44:02 -0500
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-bv-02.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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8

--NextPart

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

	Title		: RTP Payload and Storage Format for BroadVoice Speech Codecs
	Author(s)	: J. Chen, et al.
	Filename	: draft-ietf-avt-rtp-bv-02.txt
	Pages		: 14
	Date		: 2004-12-9
	
This document describes the RTP payload format for the 
   BroadVoice(TM) narrowband and wideband speech codecs developed by 
   Broadcom Corporation.  The document also provides specifications for 
   the use of BroadVoice with MIME and SDP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-bv-02.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-bv-02.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-bv-02.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: <2004-12-9155821.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-bv-02.txt

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

Content-Type: text/plain
Content-ID: <2004-12-9155821.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org  Thu Dec  9 17:36:24 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23225
	for <avt-archive@ietf.org>; Thu, 9 Dec 2004 17:36:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcX0i-0004Xm-OV
	for avt-archive@ietf.org; Thu, 09 Dec 2004 17:43:45 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcWns-00079j-R7; Thu, 09 Dec 2004 17:30:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcVRy-0008Ii-95; Thu, 09 Dec 2004 16:03:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03934;
	Thu, 9 Dec 2004 16:03:44 -0500 (EST)
Received: from insite-mail.datafast.net.au ([203.123.67.13])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcVYq-00071J-NM; Thu, 09 Dec 2004 16:11:03 -0500
Received: from barqto (udsl-5-095.NSW.dft.com.au [202.168.104.95])
	by insite-mail.datafast.net.au (Postfix) with ESMTP id BF2AA231C1;
	Fri, 10 Dec 2004 08:03:27 +1100 (EST)
From: "Ernesto Exposito" <ernesto@gsn.net.au>
To: "'Colin Perkins'" <csp@csperkins.org>,
        "'Phelan, Tom'" <tphelan@sonusnet.com>
Subject: RE: [AVT] Re: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps
Date: Fri, 10 Dec 2004 08:03:25 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTeHX+iN7I59ev+Rb+GUMujr+mSwQAFFDIA
In-Reply-To: <D019C382-4A16-11D9-99D3-000A957FC5F2@csperkins.org>
Message-Id: <20041209210327.BF2AA231C1@insite-mail.datafast.net.au>
X-Spam-Score: 1.1 (+)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 09 Dec 2004 17:30:25 -0500
Cc: "'DCCP Lista'" <dccp@ietf.org>, "'AVT Lista'" <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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 1.1 (+)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Content-Transfer-Encoding: 7bit

Dear all,

However, remember that if for HDTV we have a buffer of some seconds
(following ITU G.1010 standards, we are talking of 5-10 seconds for VoD),
then the results will not be so catastrophic. Indeed, this buffer at the
receiving side could help to hide to the application the effects of
slow-start and transmission variation. TFRC effects are more important for
"interactive" streams.

Best regards,

Ernesto Exposito
NPC Program National ICT Australia Ltd.
Sydney, Australia
Tel: +61 2 8374 5541
Email: ernesto.exposito@nicta.com.au
Web: www.nicta.com.au

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Colin
Perkins
Sent: Friday, 10 December 2004 6:16 AM
To: Phelan, Tom
Cc: DCCP Lista; AVT Lista
Subject: [AVT] Re: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps

You would also have the issue of how to maintain acceptable viewing 
quality whilst varying the transmission rate. That problem is at least 
as difficult as the practicalities of making the TFRC mechanisms work 
(and note that you must either compress or discard data to do this in 
real-time, so using TFRC for "uncompressed" HDTV isn't practical if 
there might be congestion).

Colin



On 9 Dec 2004, at 18:41, Phelan, Tom wrote:

> Hi Alejandro,
>
> See inline ...
>
> Tom Phelan
>
>> -----Original Message-----
>> From: Alejandro Cabrera Obed [mailto:aco1967@gmail.com]
>> Sent: Thursday, December 09, 2004 11:43 AM
>> To: AVT Lista; DCCP Lista
>> Subject: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps
>>
>>
>> Dear people,
>>
>> I'm from Argentina, developing a survey about HDTV uncompressed live
>> streaming over IP. I'm contacting you in order to know what you think
>> about applying TFRC to HDTV uncompressed live streaming (aprox. 1.5
>> Gbps), in order to get congestion control.
>>
>> 1) Do you think there is any limitation in applying the TFRC mechanism
>> to my scenario ???
>
> I think there's two issues you'll need to deal with.  One is slow 
> start - it'll take a good number of round trip times to get up to 1.5G 
> bps.  The other is, what will you do when there is congestion and you 
> must reduce the transmit rate?  I assume you'll be using large packets 
> to get that high a transmit rate, so the small packet issues shown in 
> http://www.phelan-4.com/dccp/tfrc-self-limit.pdf won't be a problem.
>
>> 2) Is it correct the use of RTCP like a feedback mechanism for TFRC,
>> taking the RTCP throughput at about 5% of 1.5 Gbps ???
>
> Normally TFRC requires one feedback packet per RTT.  So the RTCP 5% 
> limit is a bit problematic.  The feedback is greater or less than 5% 
> depending on the RTT.  I know this has been raised as a problem the 
> RTP profile for TFRC - I'm not sure how Ladan has dealt with it.  For 
> DCCP, there's no such restriction.  The DCCP feedback packets are 
> fairly small - I don't remember the exact size, but using 40 bytes, 
> you'd need an RTT of less than 5 microseconds to use up 5% of 1.5G on 
> the feedback.
>
>>
>> Maybe, if TRFC is OK to HDTV uncompressed, I'm interesting in studying
>> into account the use of LSR and DLSR fields of RR in order to
>> calculate the RTT.
>>
>> Thanks a lot, I appreciate your opinion.
>>
>>
>> Alejandro Cabrera Obed
>>
>> _______________________________________________
>> dccp IETF mailing list: dccp@ietf.org
>> list info:  https://www1.ietf.org/mailman/listinfo/dccp
>> wg charter: http://www.ietf.org/html.charters/dccp-charter.html


_______________________________________________
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 Dec  9 19:42:17 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03597
	for <avt-archive@ietf.org>; Thu, 9 Dec 2004 19:42:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcYyQ-00076b-4r
	for avt-archive@ietf.org; Thu, 09 Dec 2004 19:49:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcYlT-00069Y-3Y; Thu, 09 Dec 2004 19:36:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcYgN-0004ul-Kv
	for avt@megatron.ietf.org; Thu, 09 Dec 2004 19:30:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02774
	for <avt@ietf.org>; Thu, 9 Dec 2004 19:30:48 -0500 (EST)
Received: from [192.84.19.225] (helo=mail.8x8.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcYnI-0006tx-QI
	for avt@ietf.org; Thu, 09 Dec 2004 19:38:11 -0500
Received: from [127.0.0.1] (bouncer.8x8.com [192.168.85.12])
	by mail.8x8.com (Postfix) with ESMTP
	id 882F01E1AB; Thu,  9 Dec 2004 16:29:58 -0800 (PST)
Message-ID: <41B8EE06.4060709@8x8.com>
Date: Thu, 09 Dec 2004 16:29:58 -0800
From: James Kleck <jimk@8x8.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: avt@ietf.org, alan.johnston@mci.com, henry.sinnreich@mci.com,
        alan@telchemy.com, aspen@nortelnetworks.com
Subject: [AVT] video in draft-johnston-sipping-rtcp-summary-04
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit

To add support for Video-over-IP applications, all that may
be needed is to include another field for the StreamInfo:

   StreamInfo  = ("StreamInfo") EQUAL source-info SP dest-info SP pt-info
   pt-info     = ("pt") COLON 1*DIGIT

to identify the RTP payload type in the metrics.

Jim Kleck
8x8, Inc
jimk@8x8.com


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


From avt-bounces@ietf.org  Fri Dec 10 03:48:26 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24157
	for <avt-archive@ietf.org>; Fri, 10 Dec 2004 03:48:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcgZ5-0007kU-Ah
	for avt-archive@ietf.org; Fri, 10 Dec 2004 03:55:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcgMP-0006rJ-Sd; Fri, 10 Dec 2004 03:42:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcgLo-0006j3-T8
	for avt@megatron.ietf.org; Fri, 10 Dec 2004 03:42:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23897;
	Fri, 10 Dec 2004 03:41:57 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcgSn-0007dR-KF; Fri, 10 Dec 2004 03:49:22 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:63155
	helo=[192.168.0.5])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1CcgL7-0000Ey-GR; Fri, 10 Dec 2004 08:41:26 +0000
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <411D53C0-4A87-11D9-99D3-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Fri, 10 Dec 2004 08:41:15 +0000
To: IETF AVT working group <avt@ietf.org>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 312bb437839230b5894c6b1686dbca1d
Content-Transfer-Encoding: 7bit
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, proceedings@ietf.org
Subject: [AVT] IETF 61 AVT minutes
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0634ec58aad05a6aa9ac7d4670be9c6c
Content-Transfer-Encoding: 7bit

Audio/Video Transport Working Group Minutes

Reported by Colin Perkins from notes by Marshall Eubanks


Introduction and Status Update

     The Audio/Video Transport working group met twice at the 61st IETF
     meeting (Washington DC, 10th and 11th November 2004). Topics under
     discussion included the RTCP XR MIB, the new RTP Profile for TCP
     Friendly Rate Control, an RTP header extension for anti-shadow
     redundancy, and RTP payload formats for telephony tones and events,
     JPEG 2000, H.224, VMR-WB audio, and several variants of AMR audio.
     The group also discussed the issue of how the RTP timestamp should 
be
     interpreted for audio codecs where the input and output sampling 
rates
     are decoupled. The meeting was chaired by Colin Perkins and Magnus
     Westerlund.

     The meeting started with a working group status update presented by 
the
     chairs. The group has had no new RFCs published since the previous 
IETF
     meeting, but 4 drafts are with the RFC editor awaiting publication. 
In
     addition, we have requested publication for 11 more drafts which are
     currently awaiting review by our area director or the full IESG. The
     RTCP feedback draft is expected to go to the IESG for review 
shortly.
     The chairs briefly outlined the status of the drafts that were not 
to
     be discussed in detail, and solicited feedback via the mailing list.

     Colin Perkins noted that the grqup is slightly behind on some of its
     milestones, and that some of them will need to be updated. The group
     also needs to update its charter to include new work. The most 
pressing
     milestone to which no effort has been allocated is the updated RTP 
MIB;
     Alan Clark volunteered to work on this, but solicited help.


RTP Payload Format for MIDI
draft-ietf-avt-rtp-midi-format-06.txt
draft-ietf-avt-rtp-midi-guidelines-06.txt

     John Lazzaro couldn't be at the meeting to discuss the MIDI drafts, 
but
     sent a slide outlining the status of the work.  The draft has 
received
     an expert review from Dominique Fober from the MIDI community. This
     found no significant issues, and we expect the draft will be 
completed
     soon. Comments from the group were solicited.


RTCP XR MIB
draft-ietf-avt-rtcp-xr-mib-00.txt

     Alan Clark and Amy Pendleton discussed the RTCP XR MIB. This has 
been
     updated since the previous meeting, and is now a working group 
draft.
     Recent changes include a section on the relation between the RTCP XR
     MIB and RAQMON that will incorporate wording suggested by the RAQMON
     authors, plus a number of technical changes to the MIB to address
     comments by Magnus Westerlund and Dan Romascanu.

     After Alan introduced the work and gave the status update, Amy gave 
a
     detailed response to the comments received. Discussion centered 
around
     three areas: use of the SSRC as a session identifier, the complexity
     of the MIB, and the need for new parameters to be signalled.

     The issue with using the SSRC as a session identifier is that it is
     unique only within a session, not necessarily across sessions. There
     was much discussion, but no real conclusions were drawn: it is clear
     that using the SSRC isn't sufficient to correlate across sessions,
     but it's not clear what would be an appropriate session identifier.

     Regarding the complexity of the MIB, Dan Romascanu noted that the 
MIB
     is large and may not all be implemented by everyone. It might be a 
good
     idea to split the MIB, to allow implementations to claim conformance
     to subsets of the MIB with different tables? Jean Francois Mule also
     expressed interest in such a split.

     There was a lot of discussion regarding the calculation of the R 
factor
     and how the MOS-LQ is to be calculated. Jean Francois Mule was keen 
to
     see information added to the MIB to specify how particular 
parameters,
     that can be calculated in various ways, were defined. Alan Clark 
noted
     that RFC3611 does recommend a minimum algorithm (G.107), however, 
this
     is an evolving area: the state-of-the-art a year ago has been 
extended
     by now. It would be very useful to be able to specify enhanced 
methods
     in the future. It seems clear that something may need to be added to
     the MIB to address this: Colin Perkins suggested Jean Francois 
write-up
     a proposal for changes to send to the mailing list, and that 
discussion
     continue there.


Open Issues in RFC 2833bis
draft-ietf-avt-rfc2833bis-05.txt

     Tom Taylor discussed the open issues in RFC 2833bis, starting with a
     review of the changes in the -04 and -05 drafts. There are a lot of
     changes (listed in the -05 draft) a number of which cause backwards
     compatibility issues: compliance no longer requires support of DTMF
     events, a number of trunk events have been discarded and alternative
     means of signalling them defined, and event codes 138 and 139 have 
been
     reassigned. Feedback was solicited on these changes, and Jean 
Francois
     Mule expressed concern over backwards compatibility of the 
signalling
     for DTMF, suggesting that the default be to assume DTMF is supported
     unless signalled otherwise. Jean Francois and Flemming Andreasen 
noted
     that DTMF is widely supported, but other events are not. Colin 
Perkins
     suggested splitting the draft, progressing the DTMF parts quickly. 
The
     idea of a split was well received.

     The E bit is usually set to indicate the end of an event, but there 
is
     an exception for events defined as states, when the E bit doesn't 
have
     to be set when moving between mutually exclusive states. This rarely
     happens, but complicates the code and has little real benefit. It 
was
     asked if this is worth the complication? Colin Perkins suggested to
     remove this feature, unless there were objections. No one spoke up 
for
     the continued presence of this feature.

     There are a number of tone events listed that are not well defined.
     Tom suggested to remove these? Stephan Wenger and others supported
     their removal.

     Tom noted that the draft is very long, and it's not clear that all 
the
     events are needed. The decision to split out DTMF into a separate 
draft
     will help with this problem, but we may also consider other events 
for
     removal.

     Tom asked if we should establish an IANA registry for the code 
points,
     or if it should be done when the draft was published as an RFC. 
Colin
     Perkins suggested this should go into the IANA considerations 
section
     now, rather than waiting for publication.


RTP Payload Format for JPEG 2000
draft-ietf-avt-jpeg2000-06.txt

     Andrew Leung discussed the RTP payload format for JPEG2000. Since 
the
     last meeting, an IPR statement has been published listing the patent
     applications that cover this draft, the non-intelligent mode has 
been
     removed, the MIME types and SDP parameters have been improved, and 
the
     payload header has been slightly reordered.

     After off-line discussion with the chairs at the meeting, it has 
been
     agreed to split this draft into two parts. The patent applications 
do
     not apply to the basic protocol, but to various enhanced features. 
It
     looks to be possible to split the draft into an unencumbered base 
and
     an encumbered extension draft. This will be done by the next 
meeting.
     Stephan Wenger applauded this split, and encouraged other companies
     with encumbered payload formats to consider similar moves.

     The non-intelligent packetization has been removed. There is only 
one
     branch in the code, making better use of the payload header and 
using
     the Main Header Flag Field.

     Regarding the MIME types, Colin Perkins noted that the uncompressed
     video draft has similar parameters to identify the colour space. It
     would be good if the two drafts could be made consistant.

     Revised drafts addressing these issues should be available by the 
end
     of the year.


Far End Camera Control/H.224
draft-even-avt-h224-00.txt

     Roni Even discussed the MIME type registration for the RTP payload
     format for H.224. ITU has defined, amongst other things, an 
approach to
     far end camera control in H.281 and H.224. H.323 annex Q defines 
how to
     transport this within RTP, however it does not register an 
appropriate
     MIME subtype. This draft registers the "application/h224" MIME 
subtype,
     referencing H.323 annex Q, allowing SIP applications to interwork 
with
     existing H.323 systems that use the format.

     Roni asked for feedback, Steve Casner noted that it looked fine in 
his
     view. Alan Johnston (the XCON co-chair) agreed, and noted that far 
end
     camera control is out of scope for XCON. Colin Perkins concluded 
with
     an acceptance of this as an AVT working group draft, unless there 
were
     objections via the mailing list.


RTP Payload for Anti-Shadow Redundancy
draft-xie-avt-rtp-anti-shadow-00.txt

     Qiaobing Xie discussed a new draft on anti-shadow redundancy for 
RTP.
     There may be IPR issues with Motorola: the IETF has been notified 
and
     an IPR statement will be forthcoming.

     This draft attempts to address the problem of shadowing in mobile 
radio
     communications, where blockage on signals can range from fractions 
of a
     second to a couple of minutes, and where traditional RTP-style FEC 
is
     not effective. The draft defines an RTP header extension, where the
     sender generates a base media stream and a forward-shifted 
anti-shadow
     stream sent at the same time. The amount of forward shift determines
     the maximum length of blockage that can be recovered without service
     interruption, and the amount of data that must be received before 
the
     first interruption. The anti-shadow stream may be lower quality than
     the original.

     There was a lot of discussion, with Lorenzo Vicisano, Joerg Ott, 
Steve
     Casner, Stephan Wenger, Colin Perkins, Magnus Westerlund, Anders 
Klemets
     and Marshall Eubanks noting that this is a simple but inefficient 
form
     of FEC, which has a long buffering delay and problems with startup, 
is
     not likely to work well with single packet losses, and is difficult 
to
     deploy when the lower-quality encoding has different timing 
properties
     to the primary. It was noted that the RMT working group, and others,
     have effective FEC schemes that can solve this problem. It was also
     noted that it may be more appropriate to solve this at the link 
layer,
     or via layer/parallel transmission.

     Colin Perkins concluded by stating that there is clear pushback 
against
     this draft as it stands. If there is a desire to proceed with the 
work,
     the authors need to define the problem and explain why it's 
something
     we need to solve within AVT, before working on solutions.


RTP Jitter Calculation

     At the end of the first session, Steve Casner noted that there has 
been
     recent discussion on the list about jitter calculation. This is 
defined
     very specifically and a particular algorithm is required so 
calculations
     are comparable both over time and between streams, if not 
necessarily
     between, say, a video and an audio codec. People should pay more 
attention
     to the receiver reports section of RFC 3550, which describes how to 
make
     use of this.


RTP Profile for TCP friendly rate control
draft-ietf-avt-tfrc-profile-03.txt

     The second session started with a presentation of the RTP Profile 
for
     TFRC (RTP/AVPCC) by Ladan Gharai. After summarising the operation of
     the profile, Ladan discussed the changes since the -02 draft. The 
RTP
     header previously included a 16 bit quad-RTT counter as a profile
     specific extension. This has been changed to a 32 bit send timestamp
     with a 32 bit RTT sent only when the RTT estimate changes 
significantly.
     The presence of the RTT is indicated by an "R" bit, taken from the 7
     bit payload type field (as extra marker bit, as a profile specific
     change to the RTP header). The RTP/AVPCC profile uses dynamic 
payload
     types only, and does not share the static payload type space with
     RTP/AVP. Joerg Ott noted that the presence of the R and M bits could
     cause the RTP payload type to alias the RTCP payload type values -
     could there be confusion? Colin Perkins noted that standard RTP has
     the same issue, and reserves some payload types. This should also be
     done for RTP/AVPCC.

     RTCP RR packets are extended with 4 32-bit fields, describing the
     timestamp of the last data packet received (t_i), the delay between
     receipt of the last data packet and the generation of this feedback
     packet (t_delay), the rate at which the receiver estimates that data
     was received since the last feedback report was sent (x_recv), and 
the
     loss event rate (p). Colin Perkins asked if the field p and t_delay
     could be reduced in size? Possibly, but it may be possible to use 
the
     data in sender reports to deduce the RTT in interactive sessions,
     saving more bandwidth.

     Another open issue is the RTCP minimum timing interval. TFRC says to
     send feedback once per RTT or once per packet, whichever is longer.
     However for flows with small round-trip time and data rate, this can
     require sending feedback packets more often than allowed by the RTCP
     timing rules, and consuming large amount of bandwidth. It was asked
     if the RTCP timing rules can be relaxed in these cases? Steve Casner
     agreed that they probably could be, since this is specifically for
     unicast and so will not have flash joins or leaves, however this 
does
     not change the excessive bandwidth usage for the feedback in these
     cases. An alternative might be to send less than one packet of 
feedback
     per round-trip time; this is a regime where TFRC hasn't been tested
     and, as noted by Tom Phelan, it is not clear that TFRC is 
TCP-friendly.
     More research will be needed to determine if TFRC can operate well 
at
     that rate.

     The draft adopts the SRTP specification (RFC 3711) for security.  
There
     can be a NULL security operation, if there is no desire for 
privacy. It
     was pointed out that SRTP requires RTCP packets to be authenticated,
     which may not be desirable. Anders Klemets expressed concern about 
this
     additional requirement, wanting secure RTP/AVPCC to be a separate
     profile to standard RTP/AVPCC. The sense of the room was to agree 
with
     Anders, rather than forcing authentication on all implementations.

     Finally, Ladan asked if the group thought it appropriate to include
     more introductory text on TFRC into the draft. Colin replied that 
this
     never hurts, but there are perhaps more pressing design issues to
     resolve with the draft.


RTP Timestamps for Variable Frequency Codecs.
draft-ietf-avt-variable-rate-audio-00.txt

     An issue which has generated a lot of traffic on the mailing list is
     how to handle the RTP timestamp for audio codecs that use different
     input and output sampling rates. Colin Perkins summarised the issues
     and presented options on how to proceed.

     The RTP timestamp reflects the sampling instance of the first octet 
in
     the RTP data packet, and MUST be derived from a clock that 
increments
     monotonically and linearly in time [RFC 3550, section 5.1]. This 
means
     that we cannot vary the RTP timestamp rate within a session.

     There are different conventions for use of the timestamp between 
audio
     and video formats. For audio, the RTP clock rate used for generating
     the RTP timestamp is independent of the number of channels and the
     encoding; it usually equals the number of sampling periods per 
second
     [RFC 3551, section 4.1]. There are two exceptions to this: G.722 
uses
     an 8kHz RTP timestamp clock for a 16kHz sampling rate codec, for
     compatibility with a mistake in RFC 1890; and MPEG audio uses a 
90kHz
     clock for compatibility with other MPEG systems [RFC 3551 sections
     4.5.2 and 4.5.13, RFC 3119]. The implication is that using RTP clock
     rate other than the sampling rate is allowed, but one must consider
     how it will affect the overall system design.

     For audio, the convention is that the sampling frequency SHOULD be 
drawn
     from the set 8000, 11025, 16000, 22050, 24000, 32000, 4400 and 
48000 Hz.
     However, most audio encodings are defined for a more restricted set 
of
     sampling frequencies [RFC 3551, section 4.1].

     Two new audio formats violate these conventions. VMR-WB accepts 
8kHz or
     16kHz input and produces 16kHz output by default, irrespective of 
the
     input sampling rate. It is desired to use a fixed 16kHz clock for 
the
     VMR-WB payload format. AMR-WB+ can accept a range of input sampling
     rates, re-samples within the codec to one of 12 internal sampling
     frequencies, and can produce output at one of 8, 16, 24, 32 or 
48kHz.
     The draft RTP payload format for AMR-WB+ uses a fixed 72kHz clock. 
The
     key points for both new codecs are that the input and output 
sampling
     rates are decoupled and that the decoder is agnostic of the input
     sampling rate (and that the rate can vary within a session).

     These codecs raise two issues: 1) the number of sampling periods per
     second varies in different parts of the system: the usual 
definition of
     the RTP clock rate for audio it not sufficient; and 2) is it 
necessary
     to separately signal the input and output rates, and, if so, how? 
Colin
     suggested that consistency across codecs is desirable, to simplify 
the
     protocol and implementations that support multiple codecs.

     There are four options going forward:

      1) Only support codecs with one sample rate. This makes for easy
         backwards compatibility, but won't support certain codecs.

      2) Mandate a common clock rate for all RTP codecs as described in
         draft-ietf-avt-variable-rate-audio-00.txt. Stephan Wenger gave
	an outline of this (the "uRTR" approach).

      3) Allow each codec to specify its own definition for the RTP
	timestamp and signaling

      4) Do something else?

     Finally, it was asked if we need a set of guidelines for developers
     of new audio codecs which might need transport in RTP?

     After presenting option 2, Stephan noted that his experience is that
     once Pandora's box is opened, the issue does not go away.  We'll see
     this with more and more codecs in the future - probably most future
     audio codecs. But this is good, as the ability to change sample 
rates
     means that bandwidth requirements will decline and efficiency will
     increase.

     Stephan noted several issues with option 2: Should this apply to all
     future audio codecs, or just the variable clock frequency ones? What
     about codecs that don't fit the subset sampling rates (e.g. Magnus
     Westerlund noted that DVD audio uses an 88.2kHz sampling rate). How
     do we cope with non-sample-exact mixing and synchronisation?

     Qiabing Xie would support the uRTR, but wondered what if we pick not
     one but two uRTRs? Is that so bad? Colin Perkins wondered what would
     we would gain from using two uRTRs? Stephan Casner replied that we'd
     gain exactness in calculations during synchronisation.

     Magnus Westerlund noted that the problem he sees with uRTR is with
     codecs that don't fit the rate.  You will wind up with frames with
     fractional lengths.  That is a real complication. This will cause
     error. There was a lot of discussion of the details of this, between
     Magnus and Stephan.

     Steve Casner asked what is the strong gain that comes from mandating
     one number? We know that there are some downsides, what is the gain?
     Colin replied that the strong gain comes from if the uRTR time rate 
is
     an integer multiple of all possible time rates. Doubt was expressed
     that this is possible for a realistic common rate.

     The group took a "hum" on the preferred outcome. Option 3 got the
     majority. Options 1 and 4 got nothing, option 2 very little. Colin
     Perkins wrapped up the session by stating that it was clear option
     3 was the consensus, and we just have to accept the complexity it
     causes for implementations.


RTP Payload Format and File Format for VMR-WB
draft-ietf-avt-vmr-wb-file-format-00.txt
draft-ietf-avt-rtp-vmr-wb-05.txt

     Sassan Ahmadi presented the open issues with the VMR-WB payload 
format,
     now that the previous discussion has given the go-ahead to its use 
of a
     fixed 16kHz timestamp.

     Since the last meeting, the draft has been split into two: one for 
the
     payload format, one for the file format. Currently there is one MIME
     subtype with four magic numbers for the file format, but it has been
     suggested that four MIME subtypes should be defined with appropriate
     headers and parameters (to match typical MIME usage). Colin Perkins
     also noted that the AMR file format was origianlly defined in a very
     similar manner to this VMR-WB file format, but that 3GPP is moving 
away
     from this towards using an ISO-based file format. It may be 
appropriate
     to consider using an ISO-based file format for VMR-WB+, defined 
within
     3GPP2, rather than repeating a design choice that didn't work well 
for
     3GPP. There are concerns that this is not an appropriate file 
format,
     based on experience with AMR, and the group would like for 3GPP2 to
     look at this again and think about what their requirements are. Once
     they do that, we can move forward.

RTP Payload Format for AMR and AMR-WB
draft-ietf-avt-rtp-amr-bis-00.txt

     Magnus Westerlund presented an update to RFC 3267, intended to 
address
     its shortcomings and to move the AMR and AMR-WB payload formats to
     draft standard. In addition to a number of clarifications, the big
     change in this draft is a new offer/answer section.

     After private discussion during the week, the authors have decided 
that
     this new offer/answer section needs revision: there are issues with 
the
     gateway-related paramters (mode-set, mode-change-period, and 
mode-change
     neighbour) which may result in a new parameter 
(mode-change-capabilities)
     being defined. In addition, the mode-change-neighbour parameter may 
be
     changed to be only a hint, rather than a strict requirement on 
possible
     mode changes (as it will usually work changing between arbitrary 
modes).
     A new draft will be produced to include these changes before the 
end of
     the year.

     Magnus noted that Ericsson and Nokia have performed tests of about 
50%
     of the various parameter combinations. However, help with conducting
     the reminder of the interoperability tests was solicited.


RTP Payload Format for AMR-WB+
draft-ietf-avt-rtp-amrwbplus-02.txt

     Magnus Westerlund also presented the AMR-WB+ payload format. He 
noted
     that Nokia believes there is an unpublished Nokia patent application
     that may be relevant to this draft (an IPR statement is available on
     the IETF website). AMR-WB+ is one of the recommended codecs for 3GPP
     PSS and MMS, and the technical specifications of the codec are ready
     and published now. It is aslo likely be become a mandatory codec in
     3GPP MBMS.

     The payload format as written has a problem with overhead, with its
     flexibility coming with an unacceptable price. It turns out that 
this
     flexibility isn't always needed, since the internal sampling 
frequency
     and frame type are rarely switched. By making assumptions that these
     will be constant for certain frame grouping, it's possible to reduce
     the overhead significantly. An outline new proposal was presented
     (see slides) that makes this change. A revised version of the draft,
     including this proposal, will be published shortly. Steve Casner
     expressed approval for the new proposal, noting that this is a 
change
     in the direction that he generally favours.

				  -- + --


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


From avt-bounces@ietf.org  Fri Dec 10 03:56:18 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24714
	for <avt-archive@ietf.org>; Fri, 10 Dec 2004 03:56:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcggX-00081U-6V
	for avt-archive@ietf.org; Fri, 10 Dec 2004 04:03:43 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcgVg-00089H-M5; Fri, 10 Dec 2004 03:52:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcgTq-0007ct-Gx
	for avt@megatron.ietf.org; Fri, 10 Dec 2004 03:50:26 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24302
	for <avt@ietf.org>; Fri, 10 Dec 2004 03:50:24 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ccgap-0007mI-RP
	for avt@ietf.org; Fri, 10 Dec 2004 03:57:50 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBA8oEh5024612
	for <avt@ietf.org>; Fri, 10 Dec 2004 09:50:14 +0100 (MET)
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by
	esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 10 Dec 2004 09:50:14 +0100
Received: from [147.214.97.152] (RESEARCH-1FD0E1 [147.214.97.152]) by
	esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id WHLV6BWN; Fri, 10 Dec 2004 09:50:14 +0100
Message-ID: <41B943FF.6070209@ericsson.com>
Date: Fri, 10 Dec 2004 07:36:47 +0100
X-Sybari-Trust: 85a46082 a5e9b67f e22d96ec 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Subject: Re: [AVT] draft-ietf-avt-rtp-amr-bis-00.txt
References: <BDDE32DE.1ADC%gorry@erg.abdn.ac.uk>
In-Reply-To: <BDDE32DE.1ADC%gorry@erg.abdn.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 Dec 2004 08:50:14.0724 (UTC)
	FILETIME=[4419A040:01C4DE95]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
Content-Transfer-Encoding: 7bit
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd3fc8e909678b38737fc606dec187f0
Content-Transfer-Encoding: 7bit

Hi Gorry,

Thanks for this review and discussion. Comments inline.

Gorry Fairhurst wrote:
> On 9/12/04 10:18 am, "Magnus Westerlund" <magnus.westerlund@ericsson.com>
> wrote:

[snip]

> On looking through your response, I wonder how much of my response is 
> due to
> there being two types of "frames" link-frame and payload-codec-frames, each
> with their own CRC's. Normally I'd not expect RTP documents to mention link
> frames, but use of UDP-Lite naturally leads to comments on link frames. If
> this differentiation can be clearer, then the issues can be localised to
> section 3.6.1 (which seems perhaps to be the correct place to discuss IP,
> Link and UDP-Lite).
> 

Yes, all talk about the frames apply to the AMR audio data frame I 
think. We never intended to discuss link layer frames. From AVT's 
perspective this is all packets. However in relevant section where we 
discuss checksum, I could try to clarify the language.

[snip]
>  >
>  > I don't the text in section 4.4.2.1 that you quote is contradicting
>  > UDP-Lite at all.
> 
> OK - if that's the case, we can agree.
> 
> 1) There's a subtle difference between what is expected Link behaviour as
> described by UDP-Lite, and what this ID seems to suggest at the moment. 
> This
> lies in whether the Link-Layer does full frame protection; unequal
> protection; or NO protection.
> 
> Experience with SLIP, etc, showed that NO protection of IP and transport
> headers was bad - I would expect the concerns to be greater with IPv6 
> (where
> there is no IP checksum), cite RFC3819 on use of link CRCs?
> 
> One thing I'd propose is to recommend a mode were all protocol headers 
> up to
> and including the class A bits in the frame are protected by a link-frame
> CRC; you could cite UDP-Lite as clarification?
> 
> Would this impact any known usage? - Or is it only a clarification?

If this applies to the statement for robust mode, I would agree. However 
I would like to avoid to put normative requirement on link-layer design 
here. I think we should limit ourselves to talk about the transport 
protocols partial coverage length. Possibly with a suggestion that this 
preferable applies also to link-layer checksums.

> 
> Of course, it is in practice hard for the IETF to mandate use of partial
> (unequal) CRC protection at the link layer, never-the-less in my 
> opinion, it
> would be very wrong to encourage use of links with NO protection for IP.
> 
> 
> 2) Looking back, the current text in 3.6.1 seems to have a focus on RTP
> issues (it is an AVT draft), but also touches on the implications for IP
> networks. Perhaps a little more clarity here would prevent confusion (at
> least for me).
> 
> Suggestions are: Be clear which types of frame is being mentioned. It would
> be good  to mention  the network and transport (i.e. UDP/UDP-Lite) headers
> explicitly in your discussion. For example:
> 
>    "  1) Utilizing a partial checksum to cover headers and the most
>        important speech bits of the payload."
> 
> Could become:
>    "  1) Utilizing a partial checksum to cover protocol headers (i.e., IP
> network headers, UDP/UDP-Lite transport headers; RTP headers; and RTP
> payload headers) together with the most important speech bits of the
> payload."
> 
> Etc.
> 
> Is this what was meant?
> 

Yes.

[snip]
> 
> 3) Looking at the ID, I think the problem I had actually was in section 3.6
> which speaks (I think) about Link-layer frames. If this was to be made
> clear, then this section could refer back to it (and remove the potential
> for confusion).
> 
>  " The frame CRC, when used, MUST be calculated only over all class A
>     bits in the frame."
> 
> - Which "frame" is this about? - I think this is the payload-codec-frame of
> RTP?

Yes, it is the audio codec's frame.

> 
> 4)  A correct UDP-Lite implementation MUST discard these packets (this is
> also the way DCCP is expected to behave when using partial checksum
> coverage).  Of course AMR can also be used over non-IP transports, and then
> you rely on their multiplexing and control functions to supply the bit
> stream that AMR uses.
> 
> The rationale for IP transport was that allowing these packets to pass up
> the stack with no verification of the IP header (in IPv6) or UDP-Lite 
> header
> (IPv4,IPv6), could result in cases of mis-delivery of arbitary corrupted
> packets to *any* port, and applications do not generally have an ability to
> handle such events robustly (with serious implications). So, unless 
> there is
> a strong argument, I'd recommend that if you use an IP network, you MUST 
> use
> a transport layer checksum.
> 
>  > A better proposal may be to rewrite that sentence to simple note that
>  > any packets with errors detected by the UDP-Lite checksum or lower layer
>  > in that part will be discarded and never delivered.
>  >
> 
> Exactly:-)

Then I propose that the next version of the draft will try to address this.

Conclusion:

This discussion suggest that the following changes should be applied to 
draft-ietf-avt-rtp-amr-bis-00.txt

- Clarify in the unequal protection chapters that we are talking about 
audio frames (sections 3.6 and 4.4.2.1).
- Change the "Packet with errors in protected headerparts SHOULD be 
discarded" to a more inforamtive text that this is assumed to happen.
- Expand in Section 3.6.1, bullet 1 that we also IP and transport 
protocol headers are assumed to be protected by transport level checksum.

I think these are all clarifications and alignments with the published 
specifications. I do not see any backwards compatibility issues.

Does anyone protest against the outline changes?

Cheers

Magnus Westerlund

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 Dec 10 09:53:21 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19431
	for <avt-archive@ietf.org>; Fri, 10 Dec 2004 09:53:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcmGG-0006Te-GO
	for avt-archive@ietf.org; Fri, 10 Dec 2004 10:00:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ccm7V-0007Oq-DY; Fri, 10 Dec 2004 09:51:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ccm13-000681-Vr
	for avt@megatron.ietf.org; Fri, 10 Dec 2004 09:45:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18628
	for <avt@ietf.org>; Fri, 10 Dec 2004 09:45:04 -0500 (EST)
Received: from wproxy.gmail.com ([64.233.184.198])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ccm8F-0006Hk-3p
	for avt@ietf.org; Fri, 10 Dec 2004 09:52:32 -0500
Received: by wproxy.gmail.com with SMTP id 37so1050655wra
	for <avt@ietf.org>; Fri, 10 Dec 2004 06:44:31 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
	b=Tbqaev6L9uFeJBgA29i3bj3LDB57+VFMuXL7FTip6XBPFWeJrj4eglqmdTh1NlhqxJfuy2xri+2j+gKdvy4/MFk5T/jRGRMVofELeLZrjqs34bToislNdlutFip4cWxMMy15pMlfuK8Sb40JeE1RVbu8g4uzYNK8Ywss2LAhdEU=
Received: by 10.54.28.75 with SMTP id b75mr716711wrb;
	Fri, 10 Dec 2004 06:44:31 -0800 (PST)
Received: by 10.54.46.69 with HTTP; Fri, 10 Dec 2004 06:44:31 -0800 (PST)
Message-ID: <6e5aff6704121006442e815d51@mail.gmail.com>
Date: Fri, 10 Dec 2004 11:44:31 -0300
From: Alejandro Cabrera Obed <aco1967@gmail.com>
To: Ernesto Exposito <ernesto@gsn.net.au>, Colin Perkins <csp@csperkins.org>,
        "Phelan, Tom" <tphelan@sonusnet.com>
Subject: Re: [AVT] Re: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps
In-Reply-To: <20041209210327.BF2AA231C1@insite-mail.datafast.net.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: <D019C382-4A16-11D9-99D3-000A957FC5F2@csperkins.org>
	<20041209210327.BF2AA231C1@insite-mail.datafast.net.au>
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f
Content-Transfer-Encoding: quoted-printable
Cc: DCCP Lista <dccp@ietf.org>, AVT Lista <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Alejandro Cabrera Obed <aco1967@gmail.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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 3fbd9b434023f8abfcb1532abaec7a21
Content-Transfer-Encoding: quoted-printable

Dear people,

In accordance with your right comments about TFRC applied to HDTV
uncompressed streaming, I was thinking in a new point of view in order
to transmit this type of video taking into account the congestion
control. My technical situation is not good enough because I have not
contact with new generation Internet networks, just reading as much
information I can and the support of people like you. So maybe I could
have erroneous concepts=E2=80=A6sorry.

I have the following idea:=20

- There is an under-emphasized aspect of QoS, which is to provide
better ways for the application to discover the current state of the
network, so that it will not undertake to do the impossible. For
example, the HDTV streaming software could be able to tell the end
user: "Sorry, now you can get only EDTV resolution". And then the end
user can decide whether to playout or not the video streaming.
- I suppose stable congestion conditions and low loss on the network.
- I use jumbograms 9 KB.
- RTP/UDP/IP with RTP payload format for uncompressed video.
- I always run an Iperf session between server and user in order to
get an updated packet loss value. I choose a loss threshold. Before
the user run the streaming application, if loss is less than threshold
I could apply TFRC to the streaming because throughput variation will
be minimum; if loss is equal or greater than threshold I could
dowsampling the color samples from 12 to 10 or 8 bits for example.
- Conclusion: the HDTV is transmitted from sender to user with either
TFRC or color downsampling along a unique streaming session (no mixed
mechanism applied to a same streaming session) in order to adjust the
congestion control.

I really appreciate your comments again because I'm getting my thesis
conclusions.

Thanks a lot, greetings !!!

Alejandro

On Fri, 10 Dec 2004 08:03:25 +1100, Ernesto Exposito <ernesto@gsn.net.au> w=
rote:
> Dear all,
>=20
> However, remember that if for HDTV we have a buffer of some seconds
> (following ITU G.1010 standards, we are talking of 5-10 seconds for VoD),
> then the results will not be so catastrophic. Indeed, this buffer at the
> receiving side could help to hide to the application the effects of
> slow-start and transmission variation. TFRC effects are more important fo=
r
> "interactive" streams.
>=20
> Best regards,
>=20
> Ernesto Exposito
> NPC Program National ICT Australia Ltd.
> Sydney, Australia
> Tel: +61 2 8374 5541
> Email: ernesto.exposito@nicta.com.au
> Web: www.nicta.com.au
>=20
>=20
>=20
> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Col=
in
> Perkins
> Sent: Friday, 10 December 2004 6:16 AM
> To: Phelan, Tom
> Cc: DCCP Lista; AVT Lista
> Subject: [AVT] Re: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps
>=20
> You would also have the issue of how to maintain acceptable viewing
> quality whilst varying the transmission rate. That problem is at least
> as difficult as the practicalities of making the TFRC mechanisms work
> (and note that you must either compress or discard data to do this in
> real-time, so using TFRC for "uncompressed" HDTV isn't practical if
> there might be congestion).
>=20
> Colin
>=20
> On 9 Dec 2004, at 18:41, Phelan, Tom wrote:
>=20
> > Hi Alejandro,
> >
> > See inline ...
> >
> > Tom Phelan
> >
> >> -----Original Message-----
> >> From: Alejandro Cabrera Obed [mailto:aco1967@gmail.com]
> >> Sent: Thursday, December 09, 2004 11:43 AM
> >> To: AVT Lista; DCCP Lista
> >> Subject: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps
> >>
> >>
> >> Dear people,
> >>
> >> I'm from Argentina, developing a survey about HDTV uncompressed live
> >> streaming over IP. I'm contacting you in order to know what you think
> >> about applying TFRC to HDTV uncompressed live streaming (aprox. 1.5
> >> Gbps), in order to get congestion control.
> >>
> >> 1) Do you think there is any limitation in applying the TFRC mechanism
> >> to my scenario ???
> >
> > I think there's two issues you'll need to deal with.  One is slow
> > start - it'll take a good number of round trip times to get up to 1.5G
> > bps.  The other is, what will you do when there is congestion and you
> > must reduce the transmit rate?  I assume you'll be using large packets
> > to get that high a transmit rate, so the small packet issues shown in
> > http://www.phelan-4.com/dccp/tfrc-self-limit.pdf won't be a problem.
> >
> >> 2) Is it correct the use of RTCP like a feedback mechanism for TFRC,
> >> taking the RTCP throughput at about 5% of 1.5 Gbps ???
> >
> > Normally TFRC requires one feedback packet per RTT.  So the RTCP 5%
> > limit is a bit problematic.  The feedback is greater or less than 5%
> > depending on the RTT.  I know this has been raised as a problem the
> > RTP profile for TFRC - I'm not sure how Ladan has dealt with it.  For
> > DCCP, there's no such restriction.  The DCCP feedback packets are
> > fairly small - I don't remember the exact size, but using 40 bytes,
> > you'd need an RTT of less than 5 microseconds to use up 5% of 1.5G on
> > the feedback.
> >
> >>
> >> Maybe, if TRFC is OK to HDTV uncompressed, I'm interesting in studying
> >> into account the use of LSR and DLSR fields of RR in order to
> >> calculate the RTT.
> >>
> >> Thanks a lot, I appreciate your opinion.
> >>
> >>
> >> Alejandro Cabrera Obed
> >>
> >> _______________________________________________
> >> dccp IETF mailing list: dccp@ietf.org
> >> list info:  https://www1.ietf.org/mailman/listinfo/dccp
> >> wg charter: http://www.ietf.org/html.charters/dccp-charter.html
>=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


--=20
Alejandro Cabrera Obed
aco1967@gmail.com

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


From avt-bounces@ietf.org  Fri Dec 10 09:59:50 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19820
	for <avt-archive@ietf.org>; Fri, 10 Dec 2004 09:59:50 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcmMY-0006bH-IB
	for avt-archive@ietf.org; Fri, 10 Dec 2004 10:07:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ccm8M-0007dk-80; Fri, 10 Dec 2004 09:52:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ccm6b-0007AW-Mx
	for avt@megatron.ietf.org; Fri, 10 Dec 2004 09:50:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19094
	for <avt@ietf.org>; Fri, 10 Dec 2004 09:50:48 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcmDd-0006Oa-Dp
	for avt@ietf.org; Fri, 10 Dec 2004 09:58:17 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBAEoZh5021994
	for <avt@ietf.org>; Fri, 10 Dec 2004 15:50:36 +0100 (MET)
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 10 Dec 2004 15:50:35 +0100
Received: from [136.225.248.176] (RESEARCH-1FD0E1 [136.225.248.176]) by
	esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id YDRHWSA5; Fri, 10 Dec 2004 15:50:35 +0100
Message-ID: <41B9694E.7070000@ericsson.com>
Date: Fri, 10 Dec 2004 10:15:58 +0100
X-Sybari-Trust: 7485326f 87bd62f0 4a0b6d13 00000979
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: avt@ietf.org
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-amrwbplus-03.txt
References: <200412092043.PAA02399@ietf.org>
In-Reply-To: <200412092043.PAA02399@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 Dec 2004 14:50:35.0879 (UTC)
	FILETIME=[9B500F70:01C4DEC7]
X-Spam-Score: 0.7 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit

Hi,

This new version contains a major update to the payload formats 
structure as outlined by the presentation in Washington. We authors are 
planning to progress as quickly as possible due to the pressure from 
3GPP to deliver this format. Therefore, we solicit feedback within the 
next week. We authors are planning to make any updates directly after 
Christmas and go to WG last call. So please provide your feedback as 
quickly as possible.

Cheers

Magnus

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		: Real-Time Transport Protocol (RTP) Payload Format for 
> 			  Extended AMR Wideband (AMR-WB+) Audio Codec
> 	Author(s)	: J. Sjoberg, et al.
> 	Filename	: draft-ietf-avt-rtp-amrwbplus-03.txt
> 	Pages		: 35
> 	Date		: 2004-12-9
> 	
> This document specifies a real-time transport protocol (RTP) payload
> format to be used for Extended AMR Wideband (AMR-WB+) encoded audio
> signals. The AMR-WB+ codec is an audio extension of the AMR-WB codec
> providing additional modes designed to give higher quality of music
> and speech than the original modes.  A MIME type registration is
> included for AMR-WB+.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-amrwbplus-03.txt
> 
-- 

Magnus Westerlund

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 Dec 10 15:37:20 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15852
	for <avt-archive@ietf.org>; Fri, 10 Dec 2004 15:37:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcrdE-0004xM-93
	for avt-archive@ietf.org; Fri, 10 Dec 2004 15:44:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcrPN-0004xo-Gi; Fri, 10 Dec 2004 15:30:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcrLn-0002hk-4d; Fri, 10 Dec 2004 15:26:51 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15073;
	Fri, 10 Dec 2004 15:26:49 -0500 (EST)
Message-Id: <200412102026.PAA15073@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 10 Dec 2004 15:26:49 -0500
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-framing-contrans-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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db

--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		: Framing RTP and RTCP Packets over Connection-Oriented Transport
	Author(s)	: J. Lazzaro
	Filename	: draft-ietf-avt-rtp-framing-contrans-04.txt
	Pages		: 10
	Date		: 2004-12-10
	
This memo defines a method for framing Real Time Protocol (RTP) and
Real Time Control Protocol (RTCP) packets onto connection-oriented
transport (such as TCP and TLS).  The memo also defines how to
specify the framing method in a session description.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-framing-contrans-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-rtp-framing-contrans-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-rtp-framing-contrans-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: <2004-12-10155618.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-framing-contrans-04.txt

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

Content-Type: text/plain
Content-ID: <2004-12-10155618.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org  Fri Dec 10 17:16:27 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03379
	for <avt-archive@ietf.org>; Fri, 10 Dec 2004 17:16:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CctBA-0001vX-Dh
	for avt-archive@ietf.org; Fri, 10 Dec 2004 17:24:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cct2o-0003yT-Qq; Fri, 10 Dec 2004 17:15:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcszL-000353-KB
	for avt@megatron.ietf.org; Fri, 10 Dec 2004 17:11:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02987;
	Fri, 10 Dec 2004 17:11:45 -0500 (EST)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cct6c-0001pq-6e; Fri, 10 Dec 2004 17:19:18 -0500
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id iBAMDJHu020462;
	Fri, 10 Dec 2004 15:13:20 -0700 (MST)
Received: from motorola.com (d1421-0a1071e2.cig.mot.com [10.16.113.226])
	by az33exr01.mot.com (Motorola/az33exr01) with ESMTP id iBAMAIHG010585; 
	Fri, 10 Dec 2004 16:10:18 -0600
Message-ID: <41BA1FAD.4020302@motorola.com>
Date: Fri, 10 Dec 2004 16:14:05 -0600
From: Qiaobing Xie <Qiaobing.Xie@motorola.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] IETF 61 AVT minutes
References: <411D53C0-4A87-11D9-99D3-000A957FC5F2@csperkins.org>
In-Reply-To: <411D53C0-4A87-11D9-99D3-000A957FC5F2@csperkins.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Content-Transfer-Encoding: 7bit
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, proceedings@ietf.org,
        IETF AVT working group <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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Content-Transfer-Encoding: 7bit

Some comments on the comments made to draft-xie-avt-rtp-anti-shadow-00.txt at IETF 61

....
> RTP Payload for Anti-Shadow Redundancy
> draft-xie-avt-rtp-anti-shadow-00.txt
....
>     There was a lot of discussion, with Lorenzo Vicisano, Joerg Ott, Steve
>     Casner, Stephan Wenger, Colin Perkins, Magnus Westerlund, Anders Klemets
>     and Marshall Eubanks noting that this is a simple but inefficient form
>     of FEC, which has a long buffering delay 

This is not true (and may be due to a misread of the draft). One of the motivations of this 
proposal is to remove the buffer delay at the start of a session - a problem other schemes 
(including FEC and normal jitter buffer) suffer from. As clearly stated in the draft, it 
achieves this objective, i.e., no buffer delay at the start under any situation.

>     and problems with startup, is

It is made clear in the draft that there will be no anti-shadow (AS) protection at the 
beginning of a session for the duration equal to the amount of the forward-shift. But in a 
sense this is a tradeoff between "being forced to wait for x sec before the play can start" 
(e.g., FEC or jitter buffer) and "playing start instantly but no AS for the first x sec" 
(this approach). For one, I would prefer the latter without a doubt.

>     not likely to work well with single packet losses, 

How come? Please give more specifics of this comment since I think it will work well under 
this situation.

 >     and is difficult to
>     deploy when the lower-quality encoding has different timing properties
>     to the primary. 

Sure, if one chooses to use different timing properties between the two streams, it simply 
creates a harder problem for him/herself. But why one would want to do that? Normally, this 
is not an issue since both streams are originated from the same source and it is not hard to 
keep the timing properties the same.

In addition, this AS scheme does not require tight timing sync between the two streams at 
all. This is important IMO because it will make things easier to deploy.

>     It was noted that the RMT working group, and others,
>     have effective FEC schemes that can solve this problem. 

That would be good and I'd like to see proposals based on those methods. The FEC solutions 
that I am aware of so far do not provide *effective* anti-shadow protection.

>     It was also
>     noted that it may be more appropriate to solve this at the link layer,
>     or via layer/parallel transmission.

I am not sure of solving this at the link layer, but probably parallel trans is an alternate 
way to do it.

> 
>     Colin Perkins concluded by stating that there is clear pushback against
>     this draft as it stands. If there is a desire to proceed with the work,
>     the authors need to define the problem and explain why it's something
>     we need to solve within AVT, before working on solutions.

This (whether to solve it within AVT) is a valid question. The proposed AS scheme itself can 
be deployed without avt doing any additional spec or payload work (e.g., one could use two 
separate RTP streams to accomplish the AS algorithm since there is no tight coupling needed 
for the timing). However, I think a payload format from avt could improve the delivery 
efficiency (less traffic overhead).

regards,
-Qiaobing


> 



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


From avt-bounces@ietf.org  Fri Dec 10 23:06:03 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28942
	for <avt-archive@ietf.org>; Fri, 10 Dec 2004 23:06:03 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcydY-0000B9-6J
	for avt-archive@ietf.org; Fri, 10 Dec 2004 23:13:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcyQA-0005Dy-Go; Fri, 10 Dec 2004 22:59:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcyNP-0004g5-2y
	for avt@megatron.ietf.org; Fri, 10 Dec 2004 22:56:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA28476
	for <avt@ietf.org>; Fri, 10 Dec 2004 22:56:56 -0500 (EST)
Received: from rproxy.gmail.com ([64.233.170.198])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcyUi-0008SK-Gs
	for avt@ietf.org; Fri, 10 Dec 2004 23:04:32 -0500
Received: by rproxy.gmail.com with SMTP id z35so497154rne
	for <avt@ietf.org>; Fri, 10 Dec 2004 19:56:57 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
	b=RgukGu9EKh7JrwaxSW314C7grFI/fKL3O9jvjF4XWKLcy4dg8oEoyQj0Xs3Mor2x0QDx3JSBl65vkc89jMTn/0HlXOluSvj+ISGLEBLGbBtpFbUIXdcg8a3wwMowAs9uboDJtZxOEiGLyWTFmA51zH3OLQfLCm5j/eKgxDV1oUA=
Received: by 10.38.181.65 with SMTP id d65mr686863rnf;
	Fri, 10 Dec 2004 19:56:57 -0800 (PST)
Received: by 10.38.208.48 with HTTP; Fri, 10 Dec 2004 19:56:57 -0800 (PST)
Message-ID: <dcad22d804121019564c741931@mail.gmail.com>
Date: Fri, 10 Dec 2004 22:56:57 -0500
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Qiaobing Xie <Qiaobing.Xie@motorola.com>
Subject: Re: [AVT] IETF 61 AVT minutes
In-Reply-To: <41BA1FAD.4020302@motorola.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <411D53C0-4A87-11D9-99D3-000A957FC5F2@csperkins.org>
	<41BA1FAD.4020302@motorola.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Content-Transfer-Encoding: 7bit
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, proceedings@ietf.org,
        Colin Perkins <csp@csperkins.org>,
        IETF AVT working group <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Marshall Eubanks <marshall.eubanks@gmail.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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Content-Transfer-Encoding: 7bit

Hello;


On Fri, 10 Dec 2004 16:14:05 -0600, Qiaobing Xie
<Qiaobing.Xie@motorola.com> wrote:
> Some comments on the comments made to draft-xie-avt-rtp-anti-shadow-00.txt at IETF 61
> 
> ....
> > RTP Payload for Anti-Shadow Redundancy
> > draft-xie-avt-rtp-anti-shadow-00.txt
> ....
> >     There was a lot of discussion, with Lorenzo Vicisano, Joerg Ott, Steve
> >     Casner, Stephan Wenger, Colin Perkins, Magnus Westerlund, Anders Klemets
> >     and Marshall Eubanks noting that this is a simple but inefficient form
> >     of FEC, which has a long buffering delay
> 
> This is not true (and may be due to a misread of the draft). One of the motivations of this
> proposal is to remove the buffer delay at the start of a session - a problem other schemes
> (including FEC and normal jitter buffer) suffer from. As clearly stated in the draft, it
> achieves this objective, i.e., no buffer delay at the start under any situation.
> 

This is to me very similar to the SLAP protection of multicast audio
that OnTheI has
broadcast for years. I do regard this as logically a form of FEC, but
it is different enough
to warrent separate treatment.

The reason why we never pursued this as a RFC is that we could not think of an
elegant way to make different streams at different bit rates match in
general. (Different bit rate
streams in general will have different frame durations for most
codecs, so they will not
line up evenly in time, which is nasty at playback time.) I do not see
that this has been solved in this
proposal; it might be sufficient just to point out the problem and
require its avoidance.

This in practice works very well if you have control over what the
codec does, which is one reason why XM uses it.

> >     and problems with startup, is
> 
> It is made clear in the draft that there will be no anti-shadow (AS) protection at the
> beginning of a session for the duration equal to the amount of the forward-shift. But in a
> sense this is a tradeoff between "being forced to wait for x sec before the play can start"
> (e.g., FEC or jitter buffer) and "playing start instantly but no AS for the first x sec"
> (this approach). For one, I would prefer the latter without a doubt.
> 

Which is what we did too - making the first few seconds unprotected is
a reasonable tradeoff
to making the startup buffering very short.

> >     not likely to work well with single packet losses,
> 
> How come? Please give more specifics of this comment since I think it will work well under
> this situation.

I don't see this either. Generally single packet losses are
undetectable even if the backup
stream has a much lower quality.

> 
>  >     and is difficult to
> >     deploy when the lower-quality encoding has different timing properties
> >     to the primary.
> 
> Sure, if one chooses to use different timing properties between the two streams, it simply
> creates a harder problem for him/herself. But why one would want to do that? Normally, this
> is not an issue since both streams are originated from the same source and it is not hard to
> keep the timing properties the same.
> 

Not so trival for many codecs. For MP3's, for example, you have to
keep the same sampling rate
to keep the same audio frame duration (it's a fixed number of
samples). The default for many MP3
encoding packages is to lower the sample rate as the quality / bit
rate declines, which is not what
you want. This can be fixed, but it requires control of the codec.

Ogg Vorbis is even messier and I don't think this would work without
control of the codec code.

Video can be even more messy as many codecs drop video frames, etc.,
depending on quality.

> In addition, this AS scheme does not require tight timing sync between the two streams at
> all. This is important IMO because it will make things easier to deploy.
> 
> >     It was noted that the RMT working group, and others,
> >     have effective FEC schemes that can solve this problem.
> 

They do not in my opinion for streaming. What RFCs are you referring to ?

> That would be good and I'd like to see proposals based on those methods. The FEC solutions
> that I am aware of so far do not provide *effective* anti-shadow protection.
> 
> >     It was also
> >     noted that it may be more appropriate to solve this at the link layer,
> >     or via layer/parallel transmission.
> 
> I am not sure of solving this at the link layer, but probably parallel trans is an alternate
> way to do it.
> 
> >
> >     Colin Perkins concluded by stating that there is clear pushback against
> >     this draft as it stands. If there is a desire to proceed with the work,
> >     the authors need to define the problem and explain why it's something
> >     we need to solve within AVT, before working on solutions.
> 
> This (whether to solve it within AVT) is a valid question. The proposed AS scheme itself can
> be deployed without avt doing any additional spec or payload work (e.g., one could use two
> separate RTP streams to accomplish the AS algorithm since there is no tight coupling needed
> for the timing). However, I think a payload format from avt could improve the delivery
> efficiency (less traffic overhead).
> 
> regards,
> -Qiaobing
> 

Regards
Marshall

> 
> 
> 
> >
> 
> _______________________________________________
> 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  Sat Dec 11 07:18:00 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17815
	for <avt-archive@ietf.org>; Sat, 11 Dec 2004 07:18:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cd6Ji-0001EB-Cn
	for avt-archive@ietf.org; Sat, 11 Dec 2004 07:25:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cd6A8-0005B8-K5; Sat, 11 Dec 2004 07:15:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cd66s-0003t3-7H
	for avt@megatron.ietf.org; Sat, 11 Dec 2004 07:12:26 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17415
	for <avt@ietf.org>; Sat, 11 Dec 2004 07:12:22 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cd6EG-00014Q-BT
	for avt@ietf.org; Sat, 11 Dec 2004 07:20:04 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:60323
	helo=[192.168.0.5])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1Cd66H-0007Yt-8i for avt@ietf.org; Sat, 11 Dec 2004 12:11:49 +0000
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <dcad22d804121019564c741931@mail.gmail.com>
References: <411D53C0-4A87-11D9-99D3-000A957FC5F2@csperkins.org>
	<41BA1FAD.4020302@motorola.com>
	<dcad22d804121019564c741931@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <CF8081BA-4B6D-11D9-8877-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] IETF 61 AVT minutes
Date: Sat, 11 Dec 2004 12:11:38 +0000
To: IETF AVT working group <avt@ietf.org>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Content-Transfer-Encoding: 7bit
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Content-Transfer-Encoding: 7bit

[cc line trimmed]

On 11 Dec 2004, at 03:56, Marshall Eubanks wrote:
> On Fri, 10 Dec 2004 16:14:05 -0600, Qiaobing Xie
> <Qiaobing.Xie@motorola.com> wrote:
>> Some comments on the comments made to 
>> draft-xie-avt-rtp-anti-shadow-00.txt at IETF 61
>> ....
>>> RTP Payload for Anti-Shadow Redundancy
>>> draft-xie-avt-rtp-anti-shadow-00.txt
>> ....
>>>     and problems with startup, is
>>
>> It is made clear in the draft that there will be no anti-shadow (AS) 
>> protection at the beginning of a session for the duration equal to 
>> the amount of the forward-shift. But in a sense this is a tradeoff 
>> between "being forced to wait for x sec before the play can start" 
>> (e.g., FEC or jitter buffer) and "playing start instantly but no AS 
>> for the first x sec"
>> (this approach). For one, I would prefer the latter without a doubt.
>
> Which is what we did too - making the first few seconds unprotected is
> a reasonable tradeoff to making the startup buffering very short.

I agree that it's likely a reasonable trade-off; however it was 
highlighted as a potential issue during the discussion.

>>>     not likely to work well with single packet losses,
>>
>> How come? Please give more specifics of this comment since I think it 
>> will work well under this situation.
>
> I don't see this either. Generally single packet losses are
> undetectable even if the backup stream has a much lower quality.

The notes I took during the meeting say:

- [Lorenzo Vicisano]: this is a form of simple, inefficient, fec. good
   at covering big gaps, but not at single packet losses (if there's a
   correlation between time shift and gaps). might be useful when sending
   lower quality redundant stream

I think the point was that other FEC schemes may be more robust than a 
single delayed transmission, since there are several ways to recover 
each loss.

...
>>>     It was noted that the RMT working group, and others,
>>>     have effective FEC schemes that can solve this problem.
>
> They do not in my opinion for streaming. What RFCs are you referring 
> to ?

Lorenzo and Stephan Wenger both pointed to the FEC building block work 
going on in RMT and in 3GPP; Joerg Ott mentioned FLUTE. I don't know if 
they can solve your problem, but I think the conclusion of the 
discussion was that the anti-shadow draft needs to explain why the 
existing FEC work in IETF doesn't work.

>> That would be good and I'd like to see proposals based on those 
>> methods. The FEC solutions that I am aware of so far do not provide 
>> *effective* anti-shadow protection.
>>
>>>     It was also noted that it may be more appropriate to solve this 
>>> at the link layer, or via layer/parallel transmission.
>>
>> I am not sure of solving this at the link layer, but probably 
>> parallel trans is an alternate way to do it.

Discussion of the effectiveness of the alternatives would be valuable.

...
>> This (whether to solve it within AVT) is a valid question. The 
>> proposed AS scheme itself can be deployed without avt doing any 
>> additional spec or payload work (e.g., one could use two separate RTP 
>> streams to accomplish the AS algorithm since there is no tight 
>> coupling needed for the timing). However, I think a payload format 
>> from avt could improve the delivery
>> efficiency (less traffic overhead).

A standard technique is clearly desirable. My overarching impression 
from the discussion, though, is that the group was not convinced that 
the approach you have chosen is the best solution to the problem: it 
might be, but you need to justify your design choices and explain why 
the alternatives aren't suitable.

Cheers,
Colin


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


From avt-bounces@ietf.org  Sat Dec 11 11:28:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03215
	for <avt-archive@ietf.org>; Sat, 11 Dec 2004 11:28:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CdAEZ-0005kX-RQ
	for avt-archive@ietf.org; Sat, 11 Dec 2004 11:36:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CdA5G-0004pb-0f; Sat, 11 Dec 2004 11:27:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CdA32-0004JT-2T
	for avt@megatron.ietf.org; Sat, 11 Dec 2004 11:24:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02961
	for <avt@ietf.org>; Sat, 11 Dec 2004 11:24:41 -0500 (EST)
Received: from rproxy.gmail.com ([64.233.170.197])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdAAR-0005fg-Ca
	for avt@ietf.org; Sat, 11 Dec 2004 11:32:24 -0500
Received: by rproxy.gmail.com with SMTP id z35so519975rne
	for <avt@ietf.org>; Sat, 11 Dec 2004 08:24:41 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
	b=dqnrOKKfLwF6WIGgynw99fVerIkV5EN2eViJDoBMrmGZ3SDQRa3NdiCueHEh2MxKcaK5WSxBIdtHbhn19G2m5TIei3NCDeASHQQmxug9Tlju5Abuay3TiRaCGJXdrzu628JockyN+ScuN77G4g/jYtqfmQCBjTJ+39+5EBn2CjY=
Received: by 10.38.208.43 with SMTP id f43mr2040714rng;
	Sat, 11 Dec 2004 08:24:41 -0800 (PST)
Received: by 10.38.208.48 with HTTP; Sat, 11 Dec 2004 08:24:40 -0800 (PST)
Message-ID: <dcad22d804121108244b1e5c67@mail.gmail.com>
Date: Sat, 11 Dec 2004 11:24:40 -0500
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] IETF 61 AVT minutes
In-Reply-To: <CF8081BA-4B6D-11D9-8877-000A957FC5F2@csperkins.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <411D53C0-4A87-11D9-99D3-000A957FC5F2@csperkins.org>
	<41BA1FAD.4020302@motorola.com>
	<dcad22d804121019564c741931@mail.gmail.com>
	<CF8081BA-4B6D-11D9-8877-000A957FC5F2@csperkins.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f
Content-Transfer-Encoding: 7bit
Cc: IETF AVT working group <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Marshall Eubanks <marshall.eubanks@gmail.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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93e7fb8fef2e780414389440f367c879
Content-Transfer-Encoding: 7bit

Hello;

On Sat, 11 Dec 2004 12:11:38 +0000, Colin Perkins <csp@csperkins.org> wrote:
> [cc line trimmed]
> 
> 
> 
> On 11 Dec 2004, at 03:56, Marshall Eubanks wrote:
> > On Fri, 10 Dec 2004 16:14:05 -0600, Qiaobing Xie
> > <Qiaobing.Xie@motorola.com> wrote:
> >> Some comments on the comments made to
> >> draft-xie-avt-rtp-anti-shadow-00.txt at IETF 61
> >> ....
> >>> RTP Payload for Anti-Shadow Redundancy
> >>> draft-xie-avt-rtp-anti-shadow-00.txt
> >> ....
> >>>     and problems with startup, is
> >>
> >> It is made clear in the draft that there will be no anti-shadow (AS)
> >> protection at the beginning of a session for the duration equal to
> >> the amount of the forward-shift. But in a sense this is a tradeoff
> >> between "being forced to wait for x sec before the play can start"
> >> (e.g., FEC or jitter buffer) and "playing start instantly but no AS
> >> for the first x sec"
> >> (this approach). For one, I would prefer the latter without a doubt.
> >
> > Which is what we did too - making the first few seconds unprotected is
> > a reasonable tradeoff to making the startup buffering very short.
> 
> I agree that it's likely a reasonable trade-off; however it was
> highlighted as a potential issue during the discussion.
> 
> >>>     not likely to work well with single packet losses,
> >>
> >> How come? Please give more specifics of this comment since I think it
> >> will work well under this situation.
> >
> > I don't see this either. Generally single packet losses are
> > undetectable even if the backup stream has a much lower quality.
> 
> The notes I took during the meeting say:
> 
> - [Lorenzo Vicisano]: this is a form of simple, inefficient, fec. good
>    at covering big gaps, but not at single packet losses (if there's a
>    correlation between time shift and gaps). might be useful when sending
>    lower quality redundant stream
>

Lorenzo is correct - this is not particularly efficient at correcting
for single packet losses. However,
the psycho acoustics and psycho visual aspects are interesting, as
replacing a single dropped frame
(either a small set of audio samples or even an entire video frame in
a reasonably high motion video) with a lower quality backup is
typically very hard for a human to detect, as obvious as it may be on
a spectrum analyzer. Since actual packet losses tend to be bursty,
this technique works very well in conjunction with interleaving (to
convert contiguous loss bursts in real time to isolated single packet
bursts at  playback time).


> I think the point was that other FEC schemes may be more robust than a
> single delayed transmission, since there are several ways to recover
> each loss.
> 

Like always in engineering, there are different tradeoffs depending on
what path you take and
what you are actually trying to do. Clearly, this is not as simple and
may not be as efficient as XOR FEC for repairing Poisson packet
losses. On the  other hand, I don't see much that's Poisson about
packet losses on the Internet.

We used 3 separate transmissions with interleaving, and therefore had
200% redundancy, could support layering and could repair quite long
packet dropouts (up to 5+ seconds) without loss of signal, all for a
bit rate increase of about 60%. Its hard for me to see how FEC could
meet those goals without basically being driven to a very similar
solution.

Regards
Marshall

> ...
> >>>     It was noted that the RMT working group, and others,
> >>>     have effective FEC schemes that can solve this problem.
> >
> > They do not in my opinion for streaming. What RFCs are you referring
> > to ?
> 
> Lorenzo and Stephan Wenger both pointed to the FEC building block work
> going on in RMT and in 3GPP; Joerg Ott mentioned FLUTE. I don't know if
> they can solve your problem, but I think the conclusion of the
> discussion was that the anti-shadow draft needs to explain why the
> existing FEC work in IETF doesn't work.
> 
> >> That would be good and I'd like to see proposals based on those
> >> methods. The FEC solutions that I am aware of so far do not provide
> >> *effective* anti-shadow protection.
> >>
> >>>     It was also noted that it may be more appropriate to solve this
> >>> at the link layer, or via layer/parallel transmission.
> >>
> >> I am not sure of solving this at the link layer, but probably
> >> parallel trans is an alternate way to do it.
> 
> Discussion of the effectiveness of the alternatives would be valuable.
> 
> ...
> >> This (whether to solve it within AVT) is a valid question. The
> >> proposed AS scheme itself can be deployed without avt doing any
> >> additional spec or payload work (e.g., one could use two separate RTP
> >> streams to accomplish the AS algorithm since there is no tight
> >> coupling needed for the timing). However, I think a payload format
> >> from avt could improve the delivery
> >> efficiency (less traffic overhead).
> 
> A standard technique is clearly desirable. My overarching impression
> from the discussion, though, is that the group was not convinced that
> the approach you have chosen is the best solution to the problem: it
> might be, but you need to justify your design choices and explain why
> the alternatives aren't suitable.
> 
> Cheers,
> 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  Mon Dec 13 03:33:08 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10425
	for <avt-archive@ietf.org>; Mon, 13 Dec 2004 03:33:08 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CdllW-000740-JG
	for avt-archive@ietf.org; Mon, 13 Dec 2004 03:41:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cdlb6-0007b5-Fm; Mon, 13 Dec 2004 03:30:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CdABn-0006sQ-K7; Sat, 11 Dec 2004 11:33:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03444;
	Sat, 11 Dec 2004 11:33:43 -0500 (EST)
Received: from host60a.simplicato.com ([207.99.47.60]
	helo=host52a.simplicato.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CdAJD-0005pN-IR; Sat, 11 Dec 2004 11:41:27 -0500
Received: from localhost (localhost.simplicato.com [127.0.0.1])
	by host52a.simplicato.com (Postfix) with ESMTP id 5DF2611E2C7;
	Sat, 11 Dec 2004 11:33:38 -0500 (EST)
Received: from host52a.simplicato.com ([127.0.0.1])
	by localhost (host52a.simplicato.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 13648-04; Sat, 11 Dec 2004 11:33:37 -0500 (EST)
Received: from [192.168.1.2] (c-24-6-177-99.client.comcast.net [24.6.177.99])
	by host52a.simplicato.com (Postfix) with ESMTP id 328C111E28E;
	Sat, 11 Dec 2004 11:33:37 -0500 (EST)
Message-ID: <41BB2162.9050307@asomi.com>
Date: Sat, 11 Dec 2004 08:33:38 -0800
From: Caitlin Bester <cait@asomi.com>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ernesto Exposito <ernesto@gsn.net.au>
Subject: Re: [AVT] Re: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps
References: <20041209210327.BF2AA231C1@insite-mail.datafast.net.au>
In-Reply-To: <20041209210327.BF2AA231C1@insite-mail.datafast.net.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at simplicato.com
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 13 Dec 2004 03:30:22 -0500
Cc: "'DCCP Lista'" <dccp@ietf.org>, "'AVT Lista'" <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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit

Ernesto Exposito wrote:
> Dear all,
> 
> However, remember that if for HDTV we have a buffer of some seconds
> (following ITU G.1010 standards, we are talking of 5-10 seconds for VoD),
> then the results will not be so catastrophic. Indeed, this buffer at the
> receiving side could help to hide to the application the effects of
> slow-start and transmission variation. TFRC effects are more important for
> "interactive" streams.
> 
> Best regards,
> 

Which is also true if you were streaming MPEG-2 or some other form
of compressed HDTV.

If you are sending uncompressed HDTV over a short essentially private
network then a bandwidth reservation scheme is more critical than TFRC.
If you are sending 1.5 Gbits over an unknown network that doesn't have
known reservation capabilities then you really need to ask yourself
why you aren't using compression.

As soon as you hit any form of public network the cost of the bandwidth
has to be higher than the cost of the compression. And HDTV 
decompression is designed for consumer products.

The only reason I can think of for sending it uncompressed is to
support editing. Are your video editors really that far from the
signal source?

Congestion control is not my primary area of focuse, but I doubt
that any current algorithms are intended to deal with a sustained
flow that consumes a subtantial portion of each network segment
that it passes through.

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


From avt-bounces@ietf.org  Mon Dec 13 11:46:46 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27202
	for <avt-archive@ietf.org>; Mon, 13 Dec 2004 11:46:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CdtTI-0002sn-Ic
	for avt-archive@ietf.org; Mon, 13 Dec 2004 11:54:53 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cdt9p-0007G9-7B; Mon, 13 Dec 2004 11:34:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CdszI-0003pu-LO
	for avt@megatron.ietf.org; Mon, 13 Dec 2004 11:23:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24568
	for <avt@ietf.org>; Mon, 13 Dec 2004 11:23:50 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cdt77-00026X-J1
	for avt@ietf.org; Mon, 13 Dec 2004 11:31:58 -0500
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:57533)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1Cdsyl-0007Xw-Mb for avt@ietf.org; Mon, 13 Dec 2004 16:23:19 +0000
Mime-Version: 1.0 (Apple Message framework v619)
Content-Transfer-Encoding: 7bit
Message-Id: <492A0214-4D23-11D9-A87D-000A957FC5F2@csperkins.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: IETF AVT working group <avt@ietf.org>
From: Colin Perkins <csp@csperkins.org>
Date: Mon, 13 Dec 2004 16:23:13 +0000
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit
Subject: [AVT] Working group last call: draft-ietf-avt-rtp-bv-02.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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit

This is to announce a working group last call on the RTP Payload and 
Storage Format for BroadVoice Speech Codecs:

	http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-bv-02.txt

Please send any final comments on this draft to the <avt@ietf.org> 
mailing list by 5th January 2005. If no substantive technical issues 
are raised by that time, we will submit the draft for publication as a 
Proposed Standard RFC.

Colin


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


From avt-bounces@ietf.org  Mon Dec 13 12:17:52 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29496
	for <avt-archive@ietf.org>; Mon, 13 Dec 2004 12:17:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CdtxQ-0003iv-67
	for avt-archive@ietf.org; Mon, 13 Dec 2004 12:26:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CdtYR-0007f2-DY; Mon, 13 Dec 2004 12:00:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CdtMI-0003i1-Dc
	for avt@megatron.ietf.org; Mon, 13 Dec 2004 11:47:38 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27301
	for <avt@ietf.org>; Mon, 13 Dec 2004 11:47:34 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdtU6-0002tc-1C
	for avt@ietf.org; Mon, 13 Dec 2004 11:55:43 -0500
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:57775)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1CdtLk-0001lB-4j for avt@ietf.org; Mon, 13 Dec 2004 16:47:04 +0000
Mime-Version: 1.0 (Apple Message framework v619)
Content-Transfer-Encoding: 7bit
Message-Id: <9AFE3492-4D26-11D9-A87D-000A957FC5F2@csperkins.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: IETF AVT working group <avt@ietf.org>
From: Colin Perkins <csp@csperkins.org>
Date: Mon, 13 Dec 2004 16:46:58 +0000
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Subject: [AVT] Working group last call: MIDI Payload Format and
	Implementation Guide
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit

This is to announce a working group last call on the RTP Payload Format  
for MIDI and the associated implementation guide:

http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-midi-format 
-07.txt
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-midi-guidelines 
-07.txt

Please send any final comments on these drafts to the <avt@ietf.org>  
mailing list by 10th January 2005. If no substantive issues are  
received by then, we will request that the payload format be published  
as a Proposed Standard RFC and the implementation guide be published as  
an informational RFC.

Colin


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


From avt-bounces@ietf.org  Mon Dec 13 12:24:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00265
	for <avt-archive@ietf.org>; Mon, 13 Dec 2004 12:24:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cdu3w-0003tS-OS
	for avt-archive@ietf.org; Mon, 13 Dec 2004 12:32:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CdtYn-0007oC-Eg; Mon, 13 Dec 2004 12:00:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CdtMg-0004KR-Na
	for avt@megatron.ietf.org; Mon, 13 Dec 2004 11:48:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27352
	for <avt@ietf.org>; Mon, 13 Dec 2004 11:48:00 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdtUV-0002ua-As
	for avt@ietf.org; Mon, 13 Dec 2004 11:56:08 -0500
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:57775)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1CdtM9-0001lB-QH for avt@ietf.org; Mon, 13 Dec 2004 16:47:29 +0000
Mime-Version: 1.0 (Apple Message framework v619)
Content-Transfer-Encoding: 7bit
Message-Id: <AA6869E6-4D26-11D9-A87D-000A957FC5F2@csperkins.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: IETF AVT working group <avt@ietf.org>
From: Colin Perkins <csp@csperkins.org>
Date: Mon, 13 Dec 2004 16:47:24 +0000
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit
Subject: [AVT] Working group last call:
	draft-ietf-avt-rtp-framing-contrans-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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit

This is to announce a working group last call on the method for Framing  
RTP and RTCP Packets over Connection-Oriented Transport:

http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-framing- 
contrans-04.txt

Please send any final comments on this draft to the <avt@ietf.org>  
mailing list by 5th January 2005. If no substantive technical issues  
are raised by that time, we will submit the draft for publication as a  
Proposed Standard RFC.

Colin


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


From avt-bounces@ietf.org  Mon Dec 13 15:41:03 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16749
	for <avt-archive@ietf.org>; Mon, 13 Dec 2004 15:41:03 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cdx85-00006h-Di
	for avt-archive@ietf.org; Mon, 13 Dec 2004 15:49:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cdwwz-0004GT-Tc; Mon, 13 Dec 2004 15:37:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cdwsy-0001Y7-RU; Mon, 13 Dec 2004 15:33:36 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16310;
	Mon, 13 Dec 2004 15:33:35 -0500 (EST)
Message-Id: <200412132033.PAA16310@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Mon, 13 Dec 2004 15:33:35 -0500
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-mime-h224-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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2

--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		: MIME type registration for RTP Payload format for H.224
	Author(s)	: R. Even
	Filename	: draft-ietf-avt-mime-h224-00.txt
	Pages		: 10
	Date		: 2004-12-13
	
In conversional video applications far end camera control protocol is
   used by participants to control the remote camera.  The protocol that
   is commonly used is ITU H.281 over H.224.  The document registers the
   H224 MIME type.  It defines the syntax and the semantics of the SDP
   parameters needed to support far end camera control protocol using
   H.281.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-mime-h224-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-mime-h224-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-mime-h224-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: <2004-12-13145459.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2004-12-13145459.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org  Mon Dec 13 17:19:13 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02355
	for <avt-archive@ietf.org>; Mon, 13 Dec 2004 17:19:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cdyf7-0004Xa-7y
	for avt-archive@ietf.org; Mon, 13 Dec 2004 17:27:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CdyPy-0007XL-LG; Mon, 13 Dec 2004 17:11:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CdyHp-0005RR-9F
	for avt@megatron.ietf.org; Mon, 13 Dec 2004 17:03:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01452
	for <avt@ietf.org>; Mon, 13 Dec 2004 17:03:19 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdyPi-0004AG-3o
	for avt@ietf.org; Mon, 13 Dec 2004 17:11:30 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iBDM2dP00364; Mon, 13 Dec 2004 17:02:40 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YZAG82GT>; Mon, 13 Dec 2004 17:02:40 -0500
Message-ID: <7A3E36B3528ED04A880178D337F30C9A0237A415@zrc2hxm1.corp.nortel.com>
From: "Amy Pendleton" <aspen@nortelnetworks.com>
To: James Kleck <jimk@8x8.com>, avt@ietf.org, alan.johnston@mci.com,
        henry.sinnreich@mci.com, alan@telchemy.com
Subject: RE: [AVT] video in draft-johnston-sipping-rtcp-summary-04
Date: Mon, 13 Dec 2004 17:02:23 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.7 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
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="===============0838562655=="
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8

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

--===============0838562655==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4E15F.6D8B1D93"

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

------_=_NextPart_001_01C4E15F.6D8B1D93
Content-Type: text/plain

Hi James,

The RTP payload type should already be covered in the CodecInfo line.  The
reason we are not using RTP payload type specifically is to allow permit
reporting for codecs that have not obtained officially IANA assignments.
Also, I realize more parameters are potentially needed to fully describe a
video codec; these are out of scope for the draft.
  
The intention of the draft is remain flexible enough to permit service
quality reporting for applications other than voice but at the same time
report enough useful information.  Some of the parameters, all of which are
optional, should be omitted if using the event for video.  A couple of
examples are echo return loss and the quality scores.

Thanks,
Amy

-----Original Message-----
From: James Kleck [mailto:jimk@8x8.com] 
Sent: Thursday, December 09, 2004 6:30 PM
To: avt@ietf.org; alan.johnston@mci.com; henry.sinnreich@mci.com;
alan@telchemy.com; Pendleton, Amy [NGC:B601:EXCH]
Subject: [AVT] video in draft-johnston-sipping-rtcp-summary-04


To add support for Video-over-IP applications, all that may
be needed is to include another field for the StreamInfo:

   StreamInfo  = ("StreamInfo") EQUAL source-info SP dest-info SP pt-info
   pt-info     = ("pt") COLON 1*DIGIT

to identify the RTP payload type in the metrics.

Jim Kleck
8x8, Inc
jimk@8x8.com



------_=_NextPart_001_01C4E15F.6D8B1D93
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: [AVT] video in =
draft-johnston-sipping-rtcp-summary-04</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hi James,</FONT>
</P>

<P><FONT SIZE=3D2>The RTP payload type should already be covered in the =
CodecInfo line.&nbsp; The reason we are not using RTP payload type =
specifically is to allow permit reporting for codecs that have not =
obtained officially IANA assignments.&nbsp; Also, I realize more =
parameters are potentially needed to fully describe a video codec; =
these are out of scope for the draft.</FONT></P>

<P><FONT SIZE=3D2>&nbsp; </FONT>
<BR><FONT SIZE=3D2>The intention of the draft is remain flexible enough =
to permit service quality reporting for applications other than voice =
but at the same time report enough useful information.&nbsp; Some of =
the parameters, all of which are optional, should be omitted if using =
the event for video.&nbsp; A couple of examples are echo return loss =
and the quality scores.</FONT></P>

<P><FONT SIZE=3D2>Thanks,</FONT>
<BR><FONT SIZE=3D2>Amy</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: James Kleck [<A =
HREF=3D"mailto:jimk@8x8.com">mailto:jimk@8x8.com</A>] </FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, December 09, 2004 6:30 PM</FONT>
<BR><FONT SIZE=3D2>To: avt@ietf.org; alan.johnston@mci.com; =
henry.sinnreich@mci.com; alan@telchemy.com; Pendleton, Amy =
[NGC:B601:EXCH]</FONT>
<BR><FONT SIZE=3D2>Subject: [AVT] video in =
draft-johnston-sipping-rtcp-summary-04</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>To add support for Video-over-IP applications, all =
that may</FONT>
<BR><FONT SIZE=3D2>be needed is to include another field for the =
StreamInfo:</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; StreamInfo&nbsp; =3D =
(&quot;StreamInfo&quot;) EQUAL source-info SP dest-info SP =
pt-info</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; pt-info&nbsp;&nbsp;&nbsp;&nbsp; =3D =
(&quot;pt&quot;) COLON 1*DIGIT</FONT>
</P>

<P><FONT SIZE=3D2>to identify the RTP payload type in the =
metrics.</FONT>
</P>

<P><FONT SIZE=3D2>Jim Kleck</FONT>
<BR><FONT SIZE=3D2>8x8, Inc</FONT>
<BR><FONT SIZE=3D2>jimk@8x8.com</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C4E15F.6D8B1D93--


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

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

--===============0838562655==--



From avt-bounces@ietf.org  Tue Dec 14 10:36:08 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09978
	for <avt-archive@ietf.org>; Tue, 14 Dec 2004 10:36:08 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeEqi-0004ZD-7W
	for avt-archive@ietf.org; Tue, 14 Dec 2004 10:44:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeERv-0001Bz-PQ; Tue, 14 Dec 2004 10:18:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeEHN-0003tO-7u
	for avt@megatron.ietf.org; Tue, 14 Dec 2004 10:07:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05402
	for <avt@ietf.org>; Tue, 14 Dec 2004 10:07:55 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeEPN-0003e2-ED for avt@ietf.org; Tue, 14 Dec 2004 10:16:15 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 14 Dec 2004 07:11:13 -0800
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iBEF7Ksv029376;
	Tue, 14 Dec 2004 07:07:21 -0800 (PST)
Received: from [10.32.245.152] (stealth-10-32-245-152.cisco.com
	[10.32.245.152])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id iBEF61ur009687;
	Tue, 14 Dec 2004 07:06:02 -0800
In-Reply-To: <7A3E36B3528ED04A880178D337F30C9A0237A415@zrc2hxm1.corp.nortel.com>
References: <7A3E36B3528ED04A880178D337F30C9A0237A415@zrc2hxm1.corp.nortel.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <D04D9964-4DE1-11D9-9D93-000A95C73842@cisco.com>
Content-Transfer-Encoding: quoted-printable
From: David R Oran <oran@cisco.com>
Subject: Re: [AVT] video in draft-johnston-sipping-rtcp-summary-04
Date: Tue, 14 Dec 2004 10:07:04 -0500
To: "Amy Pendleton" <aspen@nortelnetworks.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1103036763.602207"; x:"432200"; a:"rsa-sha1"; b:"nofws:2673";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"gZ31WMQe6+6DOtDNuY5YzG9lyRZYv7zJ6ZdUa1bij8GhSglAreio0BHrgnP2I"
	"yejD/BfFgXihAiyhc8i+9J7zdEeD02H9YCTtbzbLrPGIlF9H4aFI8xraD3Vtv"
	"IuK7eVaLB5YIayDuPICXjrnXCySzwA6u3HBlzz115yx3QR6tQ=";
	c:"From: David R Oran <oran@cisco.com>";
	c:"Subject: Re: [AVT] video in draft-johnston-sipping-rtcp-summary-04"; 
	c:"Date: Tue, 14 Dec 2004 10:07:04 -0500"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.2 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Content-Transfer-Encoding: quoted-printable
Cc: alan.johnston@mci.com, avt@ietf.org, henry.sinnreich@mci.com,
        alan@telchemy.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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Content-Transfer-Encoding: quoted-printable


On Dec 13, 2004, at 5:02 PM, Amy Pendleton wrote:

> Hi James,
>
> The RTP payload type should already be covered in the CodecInfo line.=A0=
=20
> The reason we are not using RTP payload type specifically is to allow=20=

> permit reporting for codecs that have not obtained officially IANA=20
> assignments.=A0 Also, I realize more parameters are potentially needed=20=

> to fully describe a video codec; these are out of scope for the draft.
>
One thing we could do is instead of continuing to add stuff to the=20
report format is to explicitly include the contents of the media and=20
associated "a=3D" lines that were used in SDP to establish the stream.=20=

That allows this to simply piggyback on registrations done for codecs=20
through AVT to IANA.

Just wrap up the SDP stuff in an "SDPInfo=3D" parameter; then anything=20=

which is media-type or codec specific gets included without having to=20
extend this draft for every weird-ass situation.

This deals with the static descriptor stuff; I agree that including all=20=

the measurement parameters to characterize the performance of the video=20=

coder is much more work and should be deferred unless somebody has all=20=

of it ready and laid out in their back-pockets.

> =A0
> The intention of the draft is remain flexible enough to permit service=20=

> quality reporting for applications other than voice but at the same=20
> time report enough useful information.=A0 Some of the parameters, all =
of=20
> which are optional, should be omitted if using the event for video.=A0 =
A=20
> couple of examples are echo return loss and the quality scores.
>
> Thanks,
> Amy
>
> -----Original Message-----
> From: James Kleck [mailto:jimk@8x8.com]
> Sent: Thursday, December 09, 2004 6:30 PM
> To: avt@ietf.org; alan.johnston@mci.com; henry.sinnreich@mci.com;=20
> alan@telchemy.com; Pendleton, Amy [NGC:B601:EXCH]
> Subject: [AVT] video in draft-johnston-sipping-rtcp-summary-04
>
>
>
> To add support for Video-over-IP applications, all that may
> be needed is to include another field for the StreamInfo:
>
> =A0=A0 StreamInfo=A0 =3D ("StreamInfo") EQUAL source-info SP dest-info =
SP=20
> pt-info
> =A0=A0 pt-info=A0=A0=A0=A0 =3D ("pt") COLON 1*DIGIT
>
> to identify the RTP payload type in the metrics.
>
> Jim Kleck
> 8x8, Inc
> jimk@8x8.com
>
>  _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>
David R. Oran
Cisco Fellow
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720 USA
Tel: +1 978 264 2048
Email: oran@cisco.com

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


From avt-bounces@ietf.org  Tue Dec 14 13:07:13 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28172
	for <avt-archive@ietf.org>; Tue, 14 Dec 2004 13:07:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeHCx-0000rn-4z
	for avt-archive@ietf.org; Tue, 14 Dec 2004 13:15:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeGwH-0007uv-Og; Tue, 14 Dec 2004 12:58:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeGNL-0006qT-3i
	for avt@megatron.ietf.org; Tue, 14 Dec 2004 12:22:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23052
	for <avt@ietf.org>; Tue, 14 Dec 2004 12:22:12 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeGVM-0007rA-Jk
	for avt@ietf.org; Tue, 14 Dec 2004 12:30:34 -0500
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:50044)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1CeGMk-0004Sc-HK for avt@ietf.org; Tue, 14 Dec 2004 17:21:38 +0000
Mime-Version: 1.0 (Apple Message framework v619)
To: IETF AVT working group <avt@ietf.org>
Message-Id: <99E65266-4DF4-11D9-94D3-000A957FC5F2@csperkins.org>
Content-Type: multipart/mixed; boundary=Apple-Mail-3-183641828
From: Colin Perkins <csp@csperkins.org>
Date: Tue, 14 Dec 2004 17:21:33 +0000
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 76fee95f697ac1bd4d0bfe58b40699d9
X-Mailman-Approved-At: Tue, 14 Dec 2004 12:58:19 -0500
Subject: [AVT] ISO/IEC JTC 1 Special Working Group on Accessibility
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 85fe3afc5d9560be77aa81420052017a


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

Folks,

The attached memo provides details on a new ISO/IEC effort on 
Accessibility which may be of interest to some working group 
participants. Please contact Jennifer Garner directly if you wish to 
participate.

Colin

--Apple-Mail-3-183641828
Content-Type: application/msword;
	x-unix-mode=0444;
	name="SWG_memo.doc"
Content-Disposition: attachment;
	filename=SWG_memo.doc
Content-Transfer-Encoding: base64

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAQQAAAAAAAAAA
EAAAQwAAAAEAAAD+////AAAAAEIAAAD/////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////s
pcEAdUAJBAAA+BK/AAAAAAAAEAAAAAAABgAAqhkAAA4AYmpiah3mHeYAAAAAAAAAAAAAAAAAAAAA
AAAJBBYAZigAAH+MAQB/jAEA5hAAAAAAAAAJAAAAAAAAAAAAAAAAAAAAAAAAALoAAAD//w8AAAAA
AAAAAAD//w8AAAAAAAAAAAD//w8AAAAAAAAAAAAAAAAAAAAAAIgAAAAAAPQCAAAAAAAA9AIAAPQC
AAAAAAAA9AIAAAAAAABEAwAAAAAAAEQDAAAAAAAARAMAACQAAAAAAAAAAAAAAGgDAAAAAAAAEA0A
AAAAAAAQDQAAAAAAABANAABQAAAAYA0AABQAAAB0DQAAJAAAAGgDAAAAAAAAFRsAADIBAACkDQAA
KAAAAMwNAAAAAAAAzA0AAAAAAADMDQAAAAAAAMwNAAAAAAAAeA8AAAAAAAB4DwAAAAAAAHgPAAAA
AAAAlBoAAAIAAACWGgAAAAAAAJYaAAAAAAAAlhoAAAAAAACWGgAAAAAAAJYaAAAAAAAAlhoAACQA
AABHHAAAUgIAAJkeAACOAAAAuhoAABUAAAAAAAAAAAAAAAAAAAAAAAAARAMAAAAAAABSEgAAAAAA
AAAAAAAAAAAAAAAAAAAAAABWDwAAAAAAAFYPAAAiAAAAUhIAAAAAAABSEgAAAAAAALoaAAAAAAAA
AAAAAAAAAAD0AgAAAAAAAPQCAAAAAAAAzA0AAAAAAAAAAAAAAAAAAMwNAACKAQAAzxoAABYAAAAK
EwAAAAAAAAoTAAAAAAAAChMAAAAAAABSEgAAWAAAAPQCAAAAAAAAzA0AAAAAAAD0AgAAOAAAAMwN
AAAAAAAAlBoAAAAAAAAAAAAAAAAAAAoTAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAUhIAAAAAAACUGgAAAAAAAAoTAACOAAAAChMAAAAAAACYEwAA
OgAAAFQZAAAsAAAA9AIAAAAAAAAsAwAAGAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA3BkAAAAAAADMDQAAAAAAAJgNAAAMAAAAgNpIVobc
xAEAAAAAAAAAABANAAAAAAAAqhIAABwAAACAGQAACgAAAAAAAAAAAAAAlBoAAAAAAADlGgAAMAAA
ABUbAAAAAAAAihkAAFIAAAAnHwAAAAAAAMYSAAAoAAAAJx8AABQAAADcGQAAAAAAAAAAAAAAAAAA
aAMAAAAAAABoAwAAAAAAAPQCAAAAAAAA9AIAAAAAAAD0AgAAAAAAAPQCAAAAAAAAAAAAAAAAAADc
GQAAOAAAACcfAAAAAAAAAAAAAAAAAABEAwAAAAAAABQaAACAAAAAeA8AAHYAAADuDwAAVAAAAAoT
AAAAAAAAQhAAAEQAAACGEAAAzAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAeA8A
AAAAAAB4DwAAAAAAAHgPAAAAAAAAuhoAAAAAAAC6GgAAAAAAAGgDAAAAAAAAaAMAAIQJAADsDAAA
JAAAAAAAAAAAAAAA7hIAABwAAABoAwAAAAAAAGgDAAAAAAAA7AwAAAAAAAACAAEBAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA0NDQ0N
DU1lbW8gdG8gSWRlbnRpZmllZCBQb3RlbnRpYWwgUGFydGljaXBhbnRzIG9uIHRoZSBJU08vSUVD
IEpUQyAxIFNwZWNpYWwgV29ya2luZyBHcm91cCBvbiBBY2Nlc3NpYmlsaXR5DaANoA2gDaANRGVh
ciBQb3RlbnRpYWwgUGFydGljaXBhbnQ6DaANoA1BdCB0aGUgT2N0b2JlciAyMDA0IHBsZW5hcnkg
bWVldGluZyBvZiBJU08vSUVDIEpvaW50IFRlY2huaWNhbCBDb21taXR0ZWUgMSAoSlRDIDEpLCBh
IG5ldyBKVEMgMSBTcGVjaWFsIFdvcmtpbmcgR3JvdXAgb24gQWNjZXNzaWJpbGl0eSB3YXMgZXN0
YWJsaXNoZWQgYnkgYSB1bmFuaW1vdXMgdm90ZS6gVGhlIHJlc29sdXRpb24gZXN0YWJsaXNoaW5n
IHRoZSBTcGVjaWFsIFdvcmtpbmcgR3JvdXAgKFNXRykgaXMgaW5jbHVkZWQgZm9yIHlvdXIgaW5m
b3JtYXRpb24uICBLYXJlbiBIaWdnaW5ib3R0b20gKEhld2xldHQtUGFja2FyZCkgaGFzIGJlZW4g
YXBwb2ludGVkIGFzIHRoZSBjb252ZW5lciBmb3IgdGhlIFNXRywgYW5kIHRoZSBJbnRlck5hdGlv
bmFsIENvbW1pdHRlZSBmb3IgSW5mb3JtYXRpb24gVGVjaG5vbG9neSBTdGFuZGFyZHMgKElOQ0lU
Uykgd2lsbCBzZXJ2ZSBhcyB0aGUgU2VjcmV0YXJpYXQuDQ1BcyBkZXRhaWxlZCBpbiB0aGUgcmVz
b2x1dGlvbiwgb3JnYW5pemF0aW9ucyBzdWNoIGFzIHlvdXJzIHdlcmUgaWRlbnRpZmllZCBhcyBw
b3RlbnRpYWwgcGFydGljaXBhbnRzIG9uIHRoaXMgbmV3IGFjdGl2aXR5LCBhbmQgSSBhbSB3cml0
aW5nIHRvIGRldGVybWluZSB5b3VyIGludGVyZXN0IGluIHRoaXMgbmV3IGFjdGl2aXR5Lg2gDUFz
IHdlIGFyZSBpbiB0aGUgcHJvY2VzcyBvZiBlc3RhYmxpc2hpbmcgdGhlIGluaXRpYWwgbWVldGlu
ZyBvZiB0aGUgU1dHLCBwbGVhc2UgbGV0IG1lIGtub3cgKGJ5IEphbnVhcnkgMzEsIDIwMDUpIHdo
ZXRoZXIgb3Igbm90IHlvdXIgb3JnYW5pemF0aW9uIG1heSBoYXZlIGFuIGludGVyZXN0IGluIHBh
cnRpY2lwYXRpbmcgb24gdGhlIEpUQyAxIFNXRyBvbiBBY2Nlc3NpYmlsaXR5LiAgDQ1QbGVhc2Ug
Y29udGFjdCBKZW5uaWZlciBHYXJuZXIgb2YgSU5DSVRTICgTIEhZUEVSTElOSyAibWFpbHRvOmpn
YXJuZXJAaXRpYy5vcmciIAEUamdhcm5lckBpdGljLm9yZxUpIG9yIDIwMi42MjYuNTczNyBpZiB5
b3UgaGF2ZSBxdWVzdGlvbnMgb3Igd291bGQgbGlrZSBhZGRpdGlvbmFsIGluZm9ybWF0aW9uLiAg
VGhhbmtzIGluIGFkdmFuY2UgZm9yIHlvdXIgY29uc2lkZXJhdGlvbiBvZiB0aGlzIHJlcXVlc3Qs
IGFuZCB3ZSBsb29rIGZvcndhcmQgdG8gd29ya2luZyB3aXRoIHlvdSBvbiB0aGlzIGltcG9ydGFu
dCBpc3N1ZS4NoA1CZXN0IHJlZ2FyZHMuDQ1QYXRyaWNrIE1vcnJpcw1FeGVjdXRpdmUgRGlyZWN0
b3INSW50ZXJOYXRpb25hbCBDb21taXR0ZWUgZm9yIEluZm9ybWF0aW9uIFRlY2hub2xvZ3kgU3Rh
bmRhcmRzIChJTkNJVFMpDUluZm9ybWF0aW9uIFRlY2hub2xvZ3kgSW5kdXN0cnkgQ291bmNpbA1X
YXNoaW5ndG9uLCBEQw0yMDIuNjI2LjU3NDINEyBIWVBFUkxJTksgIm1haWx0bzpwbW9ycmlzQGl0
aWMub3JnIiABFHBtb3JyaXNAaXRpYy5vcmcVDQ2gDQwNDVJlc29sdXRpb24gMjQgliBFc3RhYmxp
c2htZW50IG9mIGEgU3BlY2lhbCBXb3JraW5nIEdyb3VwIG9uIEFjY2Vzc2liaWxpdHkNoA1KVEMg
MSBiZWxpZXZlcyB0aGF0IHRoZSB3b3JrIGluIHRoZSBhcmVhIG9mIGluZm9ybWF0aW9uIGNvbW11
bmljYXRpb24gYW5kIHRlY2hub2xvZ3kgc3RhbmRhcmRpemF0aW9uIGZvciBhY2Nlc3NpYmlsaXR5
IGlzIGEgbWFqb3IgdW5kZXJ0YWtpbmcsIGVuY29tcGFzc2luZyBtYW55IGludGVybmF0aW9uYWws
IHJlZ2lvbmFsIGFuZCBsb2NhbCBpbnRlcmVzdHMuIEFkZGl0aW9uYWxseSwgdGhlcmUgYXJlIHNp
Z25pZmljYW50IHN0YW5kYXJkcyBlZmZvcnRzIHRha2luZyBwbGFjZSBpbiBJU08sIElFQywgSVRV
IGFuZCB0aGUgbmF0aW9uYWwgYW5kIHJlZ2lvbmFsIHN0YW5kYXJkcyBib2RpZXMgYXMgd2VsbCBh
cyB2YXJpb3VzIGNvbnNvcnRpYS9mb3JhIGFuZCB1c2VyIGdyb3Vwcy4NoA1BcyBpZGVudGlmaWVk
IGluIGl0cyBsb25nIHRlcm0gYnVzaW5lc3MgcGxhbiBhbmQgdG8gYmUgcmVzcG9uc2l2ZSB0byBp
bnRlcm5hdGlvbmFsLCByZWdpb25hbCwgbmF0aW9uYWwsIGFuZCBlbmQgdXNlciByZXF1aXJlbWVu
dHMgaW4gdGhlIGFyZWEgb2YgYWNjZXNzaWJpbGl0eSwgSlRDIDEgZXN0YWJsaXNoZXMgYSBTcGVj
aWFsIFdvcmtpbmcgR3JvdXAgb24gQWNjZXNzaWJpbGl0eSB3aXRoIHRoZSBmb2xsb3dpbmcgVGVy
bXMgb2YgUmVmZXJlbmNlOg2gDVRoZSBTV0cgd2lsbDoNoA0xKaCgoKBkZXRlcm1pbmUgYW4gYXBw
cm9hY2gsIGFuZCBpbXBsZW1lbnQsIHRoZSBnYXRoZXJpbmcgb2YgdXNlciByZXF1aXJlbWVudHMs
IGJlaW5nIG1pbmRmdWwgb2YgdGhlIHZhcmllZCBhbmQgdW5pcXVlIG9wcG9ydHVuaXRpZXMgKGRp
cmVjdCBwYXJ0aWNpcGF0aW9uIG9mIHVzZXIgb3JnYW5pemF0aW9ucywgd29ya3Nob3BzLCBsaWFp
c29ucykNMimgoKCgaWRlbnRpZnkgYSBtZWNoYW5pc20gdG8gd29yayBwcm9hY3RpdmVseSBiZXR3
ZWVuIG1lZXRpbmdzIHRvIG1ha2UgZm9yd2FyZCBwcm9ncmVzcw0zKaCgoKBnYXRoZXIgYW5kIHB1
Ymxpc2ggYW4gaW52ZW50b3J5IG9mIGFsbCBrbm93biBhY2Nlc3NpYmlsaXR5IHN0YW5kYXJkcyBl
ZmZvcnRzDTQpoKCgoGlkZW50aWZ5IGFyZWFzL3RlY2hub2xvZ2llcyB3aGVyZSB2b2x1bnRhcnkg
c3RhbmRhcmRzIGFyZSBub3QgYmVpbmcgYWRkcmVzc2VkIGFuZCBzdWdnZXN0IGFuIGFwcHJvcHJp
YXRlIGJvZHkgdG8gY29uc2lkZXIgdGhlIG5ldyB3b3JrDTUpoKCgoHRyYWNrIHB1YmxpYyBsYXdz
LCBwb2xpY2llcy9tZWFzdXJlcyBhbmQgZ3VpZGVsaW5lcyB0byBlbnN1cmUgdGhlIG5lY2Vzc2Fy
eSBzdGFuZGFyZHMgYXJlIGF2YWlsYWJsZQ02KaCgoKB0aHJvdWdoIHdpZGUgZGlzc2VtaW5hdGlv
biBvZiB0aGUgU1dHIG1hdGVyaWFscywgZW5jb3VyYWdlIHRoZSB1c2Ugb2YgZ2xvYmFsbHkgcmVs
ZXZhbnQgdm9sdW50YXJ5IHN0YW5kYXJkcw03KaCgoKBhc3Npc3QgY29uc29ydGlhL2ZvcmEsIGlm
IGRlc2lyZWQsIGluIHN1Ym1pdHRpbmcgdGhlaXIgc3BlY2lmaWNhdGlvbnMgdG8gdGhlIGZvcm1h
bCBzdGFuZGFyZHMgcHJvY2Vzcw2gDU1lbWJlcnNoaXAgaW4gdGhlIFNXRyB3aWxsIGJlIG9wZW4g
dG86DaANSVNPL0lFQyBKVEMgMSBOYXRpb25hbCBCb2RpZXMgYW5kIENhdGVnb3J5IEEgTGlhaXNv
bnMNSVNPL0lFQyBKVEMgMSBTQ3Mgd2l0aCBhY2Nlc3NpYmlsaXR5IGVmZm9ydHMgb3IgY29uY2Vy
bnMgKHN1Y2ggYXMgU0MgMzUsIFNDIDM2LCBTQyAzNykNSVNPIG9yIElFQyBUQ3Mgd2l0aCBhY2Nl
c3NpYmlsaXR5IGVmZm9ydHMgb3IgY29uY2VybnMgKHN1Y2ggYXMgSVNPIFRDIDE1OSkNSVRVLVQg
U0dzIHdpdGggaW50ZXJlc3RzL2VmZm9ydHMgaW4gYWNjZXNzaWJpbGl0eQ1SZWdpb25hbCBzdGFu
ZGFyZCBkZXZlbG9wbWVudCBhbmQgc3VwcG9ydCBvcmdhbml6YXRpb25zIHdpdGggYWNjZXNzaWJp
bGl0eSBlZmZvcnRzL2NvbmNlcm5zIChzdWNoIGFzIElDVCBTQiBEQVRTQ0csIEVUU0kgSEYsIElU
SSwgQU5FQywgQ0VOIFRDIDIyNCkNUmVwcmVzZW50YXRpdmVzIG9mIGNvbnNvcnRpYS9mb3JhIChm
b3IgZXhhbXBsZSwgYnV0IG5vdCBsaW1pdGVkIHRvKSBXM0OScyBXQUksIEZTRyBBY2Nlc3NpYmls
aXR5IFdvcmtncm91cCwgdGhlIEludGVybmF0aW9uYWwgRXJnb25vbWljcyBBc3NvY2lhdGlvbg1D
b25zdW1lciBPcmdhbml6YXRpb25zIGFuZCBVc2VyIFJlcHJlc2VudGF0aXZlcyAodGhlIFNXRyB3
aWxsIGJlIHJlc3BvbnNpYmxlIGZvciBkZXRlcm1pbmluZyB0aGUgbW9zdCBhcHByb3ByaWF0ZSBt
ZXRob2QgdG8gaWRlbnRpZnkgYW5kIGVuZ2FnZSBzdWNoIHJlY29nbml6ZWQgYWN0aXZpdGllcykN
oA1UaGUgU1dHIG9uIEFjY2Vzc2liaWxpdHkgd2lsbCBtZWV0IHR3aWNlIGEgeWVhci4gVG8gZGVt
b25zdHJhdGUgdGhlIGFjaGlldmVtZW50cyBvZiB0aGUgZ3JvdXAsIGEgc3RhdHVzIHJlcG9ydCB3
aWxsIGJlIHN1Ym1pdHRlZCB0byBKVEMgMSBhZnRlciBlYWNoIFNXRyBtZWV0aW5nIGFzIHdlbGwg
YXMgYXQgZWFjaCBKVEMgMSBQbGVuYXJ5LiBUaGUgVVMgd2lsbCBzZXJ2ZSBhcyBTZWNyZXRhcmlh
dCBhbmQgS2FyZW4gSGlnZ2luYm90dG9tIGlzIGFwcG9pbnRlZCBhcyBDb252ZW5lci4NoA1KVEMg
MSBpbnZpdGVzIHRoZSBTV0cgdG8gcmV2aWV3LCBtb2RpZnkgYW5kIGNvbmZpcm0gdGhlc2UgVGVy
bXMgb2YgUmVmZXJlbmNlIGR1cmluZyBpdHMgaW5pdGlhbCBtZWV0aW5nLg0NDQ0BDQ0IAQ0NDUlO
Q0lUUyBpcyBzcG9uc29yZWQgYnkgdGhlIEluZm9ybWF0aW9uIFRlY2hub2xvZ3kgSW5kdXN0cnkg
Q291bmNpbCAoSVRJKSwgYSB0cmFkZSBhc3NvY2lhdGlvbiByZXByZXNlbnRpbmcgdGhlIGxlYWRp
bmcgVS5TLiBwcm92aWRlcnMgb2YgaW5mb3JtYXRpb24gdGVjaG5vbG9neSBwcm9kdWN0cyBhbmQg
c2VydmljZXMuIA0NDQ0AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGAAABCAAAAwgAAAUI
AAAGCAAAawgAAGwIAAB5CAAAjwgAACoMAAArDAAAUAwAAFEMAABSDAAAYgwAAGMMAADqDQAA6w0A
ABAOAAARDgAAEg4AACIOAAAjDgAAJA4AACcOAAAoDgAAKg4AAHMOAAD38ejdzsLds92k3ZKkhaTd
pN1zpIWk3ehtYFIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGhVormeHABZoWmzmADUIgUNKGABc
CIFeSgIAABgWaFps5gA1CIFDShYAXAiBXkoCAGFKFgAAChZoWmzmAF5KAgAAIwIIgQNqxwAAAAYI
ARVormeHABZo9i2cAENKGABVCAFeSgIAGBVormeHABZo9i2cADBKEgBDShgAXkoCAAAjAgiBA2oA
AAAABggBFWiuZ4cAFmj2LZwAQ0oYAFUIAV5KAgAdA2oAAAAAFWiuZ4cAFmj2LZwAQ0oYAFUIAV5K
AgAdFWiuZ4cAFmj2LZwAQioBQ0oYAF5KAgBwaAAAAAAXFWiuZ4cAFmj2LZwANQiBQ0oYAF5KAgAd
FWiuZ4cAFmj2LZwANQiBNgiBQ0oYAF0IgV5KAgAUFWiuZ4cAFmj2LZwAQ0oYAF5KAgAAEBVo9i2c
ABZo9i2cAF5KAgAAChZo9i2cAF5KAgAAEBVo9i2cABZo2hA6AF5KAgAbAAYAAAEIAAACCAAAAwgA
AAQIAAAFCAAABggAAGwIAABuCAAAcAgAAHIIAAB0CAAAkAgAAJIIAACUCAAAYQoAAGIKAAAfCwAA
IQsAAP8LAAAADAAALQ0AAC8NAAA9DQAAPg0AAE0NAABgDQAApg0AAPYAAAAAAAAAAAAAAAD2AAAA
AAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAA
AAAAAOoAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2
AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAA
AAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAA
AAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAA
AAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAAAAAAAAAAsA
AAMkAQ+EaAFehGgBYSQBZ2T2LZwAAAgAAA+EaAFehGgBZ2T2LZwAABsABgAA5hgAAO8YAACpGQAA
/v7+AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgEBA6YNAADODQAA3Q0AAOoNAAAk
DgAAJQ4AACcOAAAoDgAAKQ4AACoOAAB0DgAAdg4AAPoPAAD8DwAA/hAAAAARAAAOEQAAEBEAANcR
AAAwEgAAgxIAABATAAB6EwAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA
9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA7QAAAAAAAAAAAAAAAN0AAAAA
AAAAAAAAAADUAAAAAAAAAAAAAAAA3QAAAAAAAAAAAAAAAMsAAAAAAAAAAAAAAADLAAAAAAAAAAAA
AAAAywAAAAAAAAAAAAAAAMsAAAAAAAAAAAAAAADLAAAAAAAAAAAAAAAAywAAAAAAAAAAAAAAAMsA
AAAAAAAAAAAAAAC+AAAAAAAAAAAAAAAAvgAAAAAAAAAAAAAAAL4AAAAAAAAAAAAAAAC+AAAAAAAA
AAAAAAAAvgAAAAAAAAAAAAAAAAAAAAwAAA+EOAQRhJj+XoQ4BGCEmP5nZFps5gAACAAAD4RoAV6E
aAFnZFps5gAACAAADcYFAAG0AABnZK5nhwAADwAAAyQBDcYFAAG0AAAPhGgBXoRoAWEkAWdkWmzm
AAAIAAANxgUAAbQAAGdkWmzmAAAIAAAPhGgBXoRoAWdk9i2cAAAWcw4AAHQOAAB1DgAA5BgAAOUY
AADmGAAA5xgAAOgYAADpGAAA6hgAAOsYAADsGAAA7hgAAO8YAABqGQAAdxkAAKcZAACpGQAAqhkA
APXn9d7Vz8XPwbOrwaefl5/B1QAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAO
FmjUQ5gAQ0oQAF5KAgAADhZoG1oLAENKEABeSgIAAAYWaK5nhwAADwNqvRgAABZoG1oLAFUIARoD
agAAAAAWaBtaCwBVCAFtSAAEbkgABHUIAQAGFmgbWgsAABMDao4BAAAWaBtaCwBDShAAVQgBChZo
G1oLAENKEAAAEBVo9i2cABZo2hA6AF5KAgAAEBVo9i2cABZo9i2cAF5KAgAAGhVormeHABZoWmzm
ADUIgUNKGABcCIFeSgIAABQVaK5nhwAWaFps5gBDShgAXkoCABJ6EwAA7BMAAFgUAABaFAAAgRQA
AIMUAAC5FAAAEBUAAFsVAACNFQAAIRYAALYWAABiFwAAZBcAAHkYAAB7GAAA5BgAAOUYAADmGAAA
5xgAAOkYAADqGAAA7RgAAO4YAADyAAAAAAAAAAAAAAAA8gAAAAAAAAAAAAAAAOkAAAAAAAAAAAAA
AADpAAAAAAAAAAAAAAAA6QAAAAAAAAAAAAAAAOEAAAAAAAAAAAAAAADhAAAAAAAAAAAAAAAA4QAA
AAAAAAAAAAAAAOEAAAAAAAAAAAAAAADhAAAAAAAAAAAAAAAA4QAAAAAAAAAAAAAAAOEAAAAAAAAA
AAAAAADpAAAAAAAAAAAAAAAA6QAAAAAAAAAAAAAAAOkAAAAAAAAAAAAAAADpAAAAAAAAAAAAAAAA
2AAAAAAAAAAAAAAAANMAAAAAAAAAAAAAAADRAAAAAAAAAAAAAAAA0QAAAAAAAAAAAAAAAM8AAAAA
AAAAAAAAAADNAAAAAAAAAAAAAAAAzwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABEAAAAQAA
AAEPAAAEAABnZK5nhwAACAAADcYFAAG0AABnZFps5gAIAAAKJgALRgIAZ2RabOYAAAgAAA+EaAFe
hGgBZ2RabOYAAAwAAA+EOAQRhJj+XoQ4BGCEmP5nZFps5gAAF+4YAADvGAAApxkAAKgZAACpGQAA
qhkAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD4
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAZ2SuZ4cAAAEAAAAFMQAJMAAmUAEAMZBoATpw9i2cAB+w
0C8gsOA9IbD4ASKwhAMjkKEEJJBoASWwAAAYsGYDMQAKMAEmUAEAMZBoATpwWmzmAB+w0C8gsOA9
IbD4ASKwiwMjkJ0EJJBoASWwAAAYsGADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADHAAAARAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADQyep5+brOEYyC
AKoAS6kLAgAAABcAAAARAAAAagBnAGEAcgBuAGUAcgBAAGkAdABpAGMALgBvAHIAZwAAAODJ6nn5
us4RjIIAqgBLqQswAAAAbQBhAGkAbAB0AG8AOgBqAGcAYQByAG4AZQByAEAAaQB0AGkAYwAuAG8A
cgBnAAAAxwAAAEQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAA0Mnqefm6zhGMggCqAEupCwIAAAAXAAAAEQAAAHAAbQBvAHIAcgBp
AHMAQABpAHQAaQBjAC4AbwByAGcAAADgyep5+brOEYyCAKoAS6kLMAAAAG0AYQBpAGwAdABvADoA
cABtAG8AcgByAGkAcwBAAGkAdABpAGMALgBvAHIAZwAAAC8XAABEAGQAAAAAAAAACAAAAAAAAAAA
AAAAAABbHPsE6APoAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADwAE8GYAAACyBArw
CAAAAAEEAAAACgAAQwAL8EIAAAAEQQEAAAAFwSoAAAAGAQIAAAD/AQAACABpAG4AYwBpAHQAcwBf
AGIAYQBuAG4AZQByAC0AcwBsAG8AZwBhAG4AAAAAABDwBAAAAAAAAIJiAAfwdRYAAAYG7ErfIpSG
+vtOJ3nKB0B+Lf8AURYAAAEAAADSAQAAAAAZBwBuHvBJFgAA7ErfIpSG+vtOJ3nKB0B+Lf+JUE5H
DQoaCgAAAA1JSERSAAAB5AAAAFUIAwAAAK+RZ68AAAABc1JHQgCuzhzpAAADAFBMVEX/////zMz/
mZnMzMzMmZnMZmbMMzOZmZlmZmYzMzMAAAD///8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAADz15nTAAAACXBIWXMAAA7EAAAOxAGVKw4bAAAAEnRFWHRTb2Z0
d2FyZQBJcmZhblZpZXfJJgcXAAASs0lEQVR4Xu1dh3LjOgyU29lO/v9/H3ZRCJFUi0v8JuLM5VRI
kMKikYTk4ftzyuFwOJ8vl397eTIHhrdjfLp/fX3dZvsVsHesnwj0C0AWhWQ5nrUc/QL7ugrEUu7L
wiUEdq1+CtTbQL7evu63U4MP7awo3zIm52/oMcptGWXUEJ1+ynP+aSKbQL4pPo7yAF1bgWxi8OFk
GIsqC3qXy/l8OCyN4XDcgX5ISJcYnPUtABqGkdMUoGmX3Sx3dDQsdtD4+j6XgQuB42FWtXeNfgDm
LSCbIn99XQ/So2rhPDQtbkmT21D6IgSnod5x/inOW0B2dyr+dCu2Ad3g5jp8ch1KzyF9SNr/0yf+
g+3WgizuN2KmtUFTVyk9uq46FgeQQ6zLpPU+7P55s5iuApkKdPHZT4m81gXIVa0rDMI9+j1FQSyd
TfLl2B/ccJx/yjWhoNdZU7fpbdRIvNaPiCwgtTGgnae2CPKA0FZMqEDgpnbl7GdSBATWci8cfbHf
x+Ca9tuWOXW+DMOiUT8MKinnYWgNw3FJiFKj48CCGGVNOa+sKM8wDGsIrquzADIRjjkOF6sWVqu2
anc4+tH0G+G7PUAf52mYhUGLFl1AZqUeyIvtSwVigbIoVfYsK2uC7mGlPKyBeQ5kMPIyVqXT7dqu
hWzFdVTfA7GvZiRletzFeQrmCjjBs+WDa191U/V7ib3SQWA2cBSr7fVBRMssjdmSLkalhzUQLteZ
BlmUuEL4ITAnGke0/dW3y6Yj3ZH0YSZwcGlnRhIHw0HjOrl+kcuufnITLMI0X55W2E/LRUMg18g9
OROvq4es9i8kQ2x1Ure6gbb35ulM1FlGoX1FN9FJO2bQeGzdbwJkGKDzor9+Aupp3jxBzaHsDafn
PYmBmdF/6jMv+r/UFlRxLujQ6RElkQNW0v9gwuWatcOZUohqoKHKk/2mNiDX9Ii02jOtp10NRhPE
9ZxFKVx0PDJmO19W2MkaFZBchJY/PSWOMHj4HnJI/D1cb7f7vWvIT7wlN+1uaqgkStyl5470ie1u
ulBuOHdg7nhDAgdGCpMuEqEPxzP4dKYZJ/+O8KpyepBTeVKve5YGojHAkNfIdfl7kKrHUk0aqWxB
VJyv3kB0zhA+SM9nCheu6BnkR3qReCP6GnBEUhyQGgycxSMoyA956ARymr6IOWnD2hQi5ZC44FSH
ZOmO70kkxQ0a4ZVjc2q4RV8S5wFnWwU5dwLtWn7BEBhD/KEHFEUBqwE0VZfMJt68BFlQ9VU7DJDV
5OtdigwvWTWPntiJFcHQvG00oARNnekNYoumEAGi7dLDruhXtOfVXr+rzQFy2QRwF1QrTg/k6xjI
vIHI+fCoyCQpSUcXZM6jNIgv5U51Voa2slfF0oSm4JuML/RUg2rHEFZRTbZwWeEFX1UWFGRjtV0y
rbPoPemXNwUklAqOIUCuz6wvM+3uKVxdOUqFXEF+SI1BRXWjxDCXFFwe+3Hwd1r7anHUNjVQtrtY
lr8LjUziiqa1cPjms01tG20eTWDIW0Jr2qlwWeiUQAYbA+SAxqFVX4j4yETGXXohBgIaXBkQIRW5
leHLIQQxFQMdIUV3hONo4Eet+lBRkIOKWOkczFySNc8hUqOkgYs5VVu8HMMlCCZr0EBpu5gtxmUZ
leNslTlLOk1xsb5Y9gCfDhJVi6VWrqoKMtihWgNLtcqyd2pqBPNOZ2kmHyTonAMZddOyfSb1YG9x
qjLCVqjXPzuISnlfsvAjgTebX1zTaFbgmEFR5eyxQhRj8UD4NyaYUM4gdwHiRahipH9U1UQACsgd
LKW6tO2Y8bLERj6MDQwNUWFCMbxUD0Y9Frwe1Co7yLxXAmDCTdftwa5Li9sFCAV9uPdGMdGoyCL0
wDdA5kE6Y+xHa2xxmTkElbik10rRJOZxkGNtSRCvhaagHMp56xjUgJNeuavHX1juiHr9OtK6B75K
jhYMcA5lmRtIBQRqmCQIhtAbsaiSjiSsPsBOyYk+ctQolUSfKDGSs2RVWV8Jsdo5b4Vhs1WjGTnS
5UFOyiBe8iefSSRIOvJXKGNAUh3tyXIcOA7m6+1SjPbnQCdcYQbbiefFuZvc6QiIu6yBFVQBcl9J
oabJGsgcSUrZveSpoJlI3f3uaJENjJrV5Z8z40NaPm6fqwcZ3NRRZXthnE9bkjvNmqqmtNhY2ccY
eWzJCeN8+I7wqVn6iKrh/IMSbcKJMfp4JRWDbP3ywq7Ch+C3ZhgRJq6pvKrOYA5ZFba7sm/8782g
3Acn/Rs71ZT1d8pq6l7WzXeZe0U3fkkmaclauwduV+MWdyVW8eMDKr0AZFtlIR/72mCqXNxpmv24
jqXUrbIaHSIQICWTz2udRc1iE6Z3NDH7qIAXA/IB+HzoEGympyzTFfNaJVTJuzOosKOB7D1HVM2G
Vb2vmII5By25gukMfBliA3ITM34ox39hWLpKYMYPzo4BvmCdxsK73RlUcLq7XJmDYq1Zg1xrdu4H
i5xT25qYs+yqvFpcaOQsWNW1IVspSCiTn70ZVPGk6e54NjWGIpn8Lui4OJont3KiBHv2uokomhXf
B5eAE1OxZclSM3q2i1Ur0KsGOUWpf50gGxK2dmALBmX4lIG06jznSW/FO7cATQfXWRZGKE84Zpmu
tva6DinSsgUfRhcgNpTWdVlj2yrs0JtbaF4TUemW01IQWVbd6slS9wEBsvNLl+d1b+WS9IL3g/Vp
VlwQKHa3gNza2hrk5Mk3otzV5HoCWG3QYY9/OTMoc20SsQJyDcccyJPQlD5ty2JJFG3lrpHXiSVQ
bq4VTcY2NhUig0xNnthotKa95cpW1eo4K0Cv9HVZl38C8pZNWVvkmlH8KX7ONKktS8emaESEpbOy
ANapNiVKE7YCIAcaidxB3J4XCkFyp0mpvWlZ1EiTqQblOjOzzdS0JqN10U701Q286qUchQH5N/BU
2F3wDCBKMW7YbZ7q06qjxQav3vSqVqX4PK5IG51oyR0JdaokU4iiiicbjfry2tq9L2DHaG1A8RhK
2eTVogLviSkS6VkCQIw0wCi2Z7QZheg6W9ZOgmURgTlzXUtHJ7i2seSdys5brt0pVBdks3+WE8J9
KOWQ7iwg8QOe1S56bdsboJTQNGsLHLpPUJCZo6Mr0txhAPvVU5MEb6UuPeqJy6ie90J9cuONdUDc
YTG6lqUUiUb2SEx18SHUoQfGEyB75CLpAsm/cZ68egZVVH55BhXS0lbNa6ONKmMLonUG9UTZd3/A
HtnxxV9ygqcKAjiGG5orpFtWqMbLUBhuF+FmShNSBVHbKze5/2j7UU5Bs8yUKEIBORDe2r6TnqEZ
+9JOjN8+u+GYuC+uw63GbXTLPQ5D5YFyO3bqoB780kUj8C/HMORncqedcCk712ZdssAxOYPqxdBl
BbwGGVu8HYy7IJPP5GHJxAE+tHjcaNZD29T3TBG19LHTbC0scaiADKuOfFDLH7BtRautCUhqWu1S
OrNUMkKfXSng1YxDlSGVDQosiCBnLdG1vU/ZlIbIshUPxvEg1q7LuoLuelUbFeTn2hlUnueOoTuN
TD6JVvIwXK/fJa27LI/WICMs6YFcRbrUtQwtoVQ7p1oaeTqaGKDXyh4uomG1yiDlu8rm6Rw7qo+0
tOwkFyfSwh8lgMbjMwyMJI9U9PCftsvteZo2oBBT3yTXgfF5ksE3eajnEJJ5maec5JNwME05lZ9r
Z1CjjcayPSG7SfeZPShJAZSUT2w3yWbVVdffJkGewrhevC4pPeYkfQM+IKtywZxvllnCFAOd9oCU
ZSN4L65vuibiXjBkKkRiLCXlTA282ovwocp+dOnSaLlLKZ8QvsoHZvbHrI7JMAgWmWE4h/yuohZq
pnHRq9kkeu0MKusnFiYlFRdZuTjMJl97bJJADFlJxU1bzeOdRipWT4+bfVKzwpZk5Sl59MuWj1ny
dMg3QsW4Gg7zSGhhbZlMmWw+WKOwapKmBO2wkUjbD3EKkXACR++C5OiTbZbEcMkcPbJ13YXw0LJJ
M90jHYTfK8jyyfD+HV1ULtCaHMQouMJF890uACtnULCsEzkDt2zyFaU6gyQpe84cypDKYtDUex2V
tSYMYTX1SCPdEuqYvSxmnXc9/StZZLpG/jEbpyrp8ZYdKMgllKL+aX6/BwVxhsBKR0wR0qKjU6eB
q3aecsVK1J7ugY4S9iC70eSxWijKDL7wFHYzv80yO4PqKigRSyC3G5SKaaqSQM6unYapq8eNIjNt
xv/Eu23QAn3hyXKDkHnjuUK8qbk+1HYuLzIbni1gQ3zF0ZJyGIfjLg+QO2R9kr534gS0Sz1TUEg4
WVckX+vrVVINpETdNY3I6CIxSauke4RMpwSo2iyLthxTlFVdwi6un0FNogx/ayUiqSrr89rL4ktv
wpHNfYjb7LSxMKcky+rG75zCziCQdsP/0lF01MIM+ii3vjeDKgkbzcZDL3H+lBfNDKnKsic5KJoc
EkHxnXw/aylnYG5R+aUc7hPn6jG9xSi0fs1IukyzqCvBPD+Davf+O/maKVwuyjiqJ0tbrXQ4xp33
aEc6XXnkhlsfBrIFB5zzvjw9ra8ZHgnEi8FpAbKTzdFZnhzayLn7AmNav2QiyDB+u8aTQ5Yg7qYg
joBetU37GkXqUpWvojCHlynELy5T5s9hvmjoLdMgLadvzaXloZd0N2nX1RNu7Y3HaDhexMT8GHOt
8kKjNZTpl47OIpspZ4zrS8b6xVz8cPLT7yCHFXnDq+gz+OlEY+ld6SVj/eEovHh4sy+aR4ZC+WzI
nDo9/54ivCxlO8azYjILspjBeKN16kM8z0fWKNrrJ4GwuHTx1xKatVtWO8bzpmABZLi7/Oby4sdO
n4O5LQaNBOsmuZuCc+crYjvGC+Z+GWQNfYKReAX0OUhOLFx5X/VH+SRev37JJybq9ym2pW292Pt9
Jvl1IFOhU9Y9kH461Okjmz1Bul2/5DMi8m8sHIuZjZ/J97eOajXInKiMP1Sr38l9XK1HPz0xKT74
tszpeq2+I/byhYS3ovGizjaBrLPW5pPEAFum9htJ2c+KFIf6E/MgL+rvZZEDG5EJteVH6xvBQ3ej
75v7x8z1f97qvHfwE3gfNyB/h8JPQVYO4SMbP/9ILCXiGfb+78D1syd9DOSi2PrjMb23g+oVZKr6
9k/e/+zx9lbUxRexYWynd0xfxOZ1ZF8F8rre91pv4cAO8lvY/Lud7CD/Lv/f0vsO8lvY/Lud7CD/
Lv/f0vsO8lvY/Lud7CD/Lv/f0vsO8lvY/Lud7CD/Lv/f0vsqkPmJ4qeUG75dLRvDTqyXzJM6Osm7
kHt5mAMNyAYo3yOVIuk2w2nN75brSOSdKYGl8/qDDfSODK2E7L36OGr1PJIK8vAT7gTatWsFF4nw
BFlSMbLmLXFMZGL0Oey6PqkmZBdshPzW2FKP+/1lDjSarAgg4R38hSJ3EyQnKEu7G39QSF5lk0SO
+hsBahMKshtsxPKj7DWmONAHWawuvacoHX84Qt5puOsbK/Lhaj063XCYLrAHwVaB1Z8asMLmuE5v
nJCVTvxWoaxH31DiG8YgaT+8gPb4ragdzK0c6IMszCce6hP5GgtUlBouR/hhXH25xS94t46tmPvk
TdkI6FNyVHxYQAS3lB4oUxJ4JMcia/ZOu3bPOruX3opx65MJgSBywv9UZAAmr0CB4cx6lq8v6e/C
6FfK/QL13LGlb/ZywjtNpEtfMIq7hDLpFUJIoieeCAYEUZAa8BeYS/OpL+dufvS/06DRZIABLQbI
qsj0y+pJCS/xEobjUK1z6GZgKxhVIRONNCmVuEtRY3OtjyMlxlum+NRd6V7h38tmDnRBBgwA2TEF
a2E6oagolAH7SRG/4OZXYQjfTP3W1xutEW2wFpswC5aJsiEJefCIgDZC+jOfsfkh/3qDBmRhPBVY
QLZZqmoeuOxQ3PHdB+gb3CeLaZhji0+MBGdRCR/zgU0OP28yQZvOCCAIacshFF/tCJvipec97tou
sg3IAqZ5YsEF6JrmAdVRXKwzrHEY1I27qJpmfultAyeYBClSIREqoLI769McubmO7c/5p1t0QNbg
SZirCCYuiyZ7fVfv0Q+YR9w10jgPns0bqw9g0Z6kMmxEoazBXig+BcEcuXnxPw3Z9odvQIalBQqx
5mWaRy4L7viMmsXa5L1dYM857ipBMOvYcieR9T7RhZBjf4UQLTdnXBZ3USYgCDT6+wzqCSD7MkbS
SsMcplu/yVQWNOICe46YWqe+VviRkbD2yeSLn+Vsm3GdU8aKB6ozlo81ULQincnfHtn+6H+nxapd
qMSO/GvlvNxc6PDudJrspix9jgh11zuxXPp3kHnik24F+Yld90kNDPYsJHt5b3+jg48DWeJsevCP
G9j/WB4+jpf8jpfthvyP+fpRQ/8PY0Ash8xkbtAAAAAASUVORK5CYILiDgAARABkAAAAAAAAAAgA
AAAAAAAAAAAAAAAAghTuAvIC6AMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA8ABPBS
AAAAsgQK8AgAAAACBAAAAAoAAEMAC/AuAAAABEECAAAABcEWAAAABgECAAAA/wEAAAgASQBUAEkA
bABvAGcAbwAtAFYARwAAAAAAEPAEAAAAAQAAgmIAB/A8DgAABgYHV+JNcPXN5PPUChN2m9+d/wAY
DgAAAQAAAAEZAAAAABkHAG4e8BAOAAAHV+JNcPXN5PPUChN2m9+d/4lQTkcNChoKAAAADUlIRFIA
AAFeAAAAMggDAAAAI7RDvQAAAwBQTFRF////EBAQISEhMTExQkJCUlJSY2Njc3Nze3t7jIyMnJyc
ra2tvb29zs7O3t7e7+/v7+fn9+/v//f33tbW597e/+/v/+fn/97e/9bW987O/87O9729962t96Wl
95yc73Nz72tr5zkx5zEp5ykh3iEY73tz73Nr72tj52Na72Na51pS51JK50pC50I575yU95yU75SM
95SM74R797Wt96Wc972173tr52ta3mNS1jkh1jEY/9bO987G98a975yM962c76WU53tj53Na3mtS
52tS51Ix3kop1kIh3kIh1jkY1jEQ/97W97Wl762c95yE95R774xz74Rr51o53lIx/8a1972t/62U
96WM53ta51ox3lIp3koh/869/7Wc/5x795Rz74xr94xr54Rj74Rj73NK52tC72tC52M5/+fe/9bG
/72l97Wc762U/6WE95x775Rz94xj94Ra73tS972l/62M96WE95Rr74RaxrWt/97O/8at/7WU962M
/6V795xz/+/nva2l/86198at/72c/62EtaWc/8al/7WM/9a9lHtr/+fW/97G/86te2NSxr21rZyM
pZSE//fv1s7GvbWt/+/enIx7lIRzzsa9///33t7W5+feAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAALEEq9gAA
AAFiS0dEAIgFHUgAAAAMY21QUEpDbXAwNzEyAAAAA0gAc7wAAAqVSURBVHhe7Zr9VxNXGsfvz3sK
CZNJSI50rV3Q3ZClFGG7tllX7R6ta7Equqfl6JEt7REBEStv4gsBGtfU7kwgJnH61/b7fZ6ZJITK
y3KMdjvPxGHm5t5n7v3c7zz3JRoTWkggJBASCAmEBEICIYEDEDieqVkSbpIZno9nPjSmM5NJZru7
Myvp7u4sLna2tGG2we7utOnJfGiZ5J+OxY2JH/sA7g711p7Rc4Cq/hqLAkhgWdS/82gnzoPdR425
oFQziX3gHSbedPdRy2SPZBLGbPQfh7uuz2rPSP8aGR2gzgDSiNds0FciC8hWNmslBoePW/vAmxwe
HDJJKZ1KvoQni+663v/N4v19E96tPWVFEwnTmUxaVvaDnYLDHw8lzQSzJRIICc3W9YcmvG2uu2lw
coxZct2ocWlLKFZ1C4UiUk1UUjb9K9vEcCtuc66bk1KwTS1tLKdYKLhVfIvEDpalL72FRcWZ+mdG
zSAn1EG94UlWrlyouDHkUq9IWWJ2VkIuK3l8afMRrI3k2NWa1JvoxyttUv1DiJv9/Ylkb7onfuzI
kdQeYu97yDbU2ztguvqHLJPoexcvgjV4CO7ebVavUyg4BqdC1YBnu8EVm80bWsUytl6BdBV/SqaM
cwSuNpka8TM6WtqqaGY4kDPKaleo30K7F3ydlwvNICfWQbw4xva94JHiFZWv+7XAmZaXL9mbpV3J
Soam2JvtZgQe7D5cj73RfQSHLbEX/ZvIDMDd8Wb11vBWOlBbjxjyTpuwK7HFOQMi5RJAGyFQ7GDb
bLiSZlZNiR3htrGtnsmRETIXNoVnDGWL2ngX2StulHgd33/eqdB5UU90LnVw2IFlh25t9YoXpe6X
l3hmvs2YCEog697omib1dg5waBtK92GUS6dTyXT6L/GeTCaVyvx5p+DwfqYHE4ZMaiidHjAD6T7M
HN7rQZiw+vAabI+9NbwFF02xSSXneGwW5AHISqBN8Iqi2TxKGW1j+FBhKm0pjRcYysyrXKF3X72m
XS6Jl+8/suSM6WCqmKq34CLdieKiwxByXr3KIwK/AOpE7E3bQxYpw+/3YjvHXvGwkoi+NImhnfAe
7uww8QTk+ou2LfYGeNEuNEXUW3tJpfENwYGqwoF8QANy72jjFW+gfSTAp4vUIjPX8MZqeOv+FXcN
L2RPvEzT/nID9SpF328hJljRxQwUQfftSrh55lAvYHV1xaHew/GBdDqZ7O3dCe8RirY3nRT1/q0r
tfWxw6+KvY5UOabBwTZLIGmxcWWfAF9BEEN6AaAgWrSsiH9Ib8ArzbUAtcRUyjAIDuwllGIgj9kR
A5LliKnyvuKwa8nOYXAvOJawY+ESa1C1PUWtfnHpeKwsRz4Rxx6tSb1B7G2Y9+4n9sKbzHs3OO9d
CWLvtolZoF5HYqm83gx2ePXVYsJFRxy0kenCU0IwLVLHi1nF1lRSCNTlNajXDYqz7+pDm9bBIXsx
dJ2OsI1+2QUuQGPQ3R/eJvUq3uFurK4OtqxIybJiRYa2VwYHlYsEBwlmPihMsfhWM0rE0LAc2ptj
VIzgpui146rq45XQYhwd4qEsUiGdrXjVLdJk3iHcXGUs/cw6OMZSvkVEOPKmI00pU7G52pf7w5vI
1ow9Y2V5DpYV8Xg2m3yZzGbjWGPsbEmsJrJxeOMFhscNWVZYKc7zVlK1slxyY3TxYh08YaoVjXmW
8XgS8zDCSz289iiSbS9iI1dHu2WitmdFpUjE9vgd9c5E5m5zHE6l/FQbZdWsGC8tO4bskoaMHu+j
eAJOfh3ErYlUnSqd0mvM4xX9Sope+l4jrH1oIYH/ewJ2uW57a2y+ocTepn/VegnMa39T5v23bntr
eLmhhB+YdilYqpfQ1U6HbSP28mSins24atsa2CQRd4yotlNFIm54b/HMkCd/kK3WszHH8bM7EhOR
M4r4XH+CerM26U78S47WWOxAeDmo7m7b8AYTM8xCZWEgM6GKAwryjcwmOmT8lqks73WlVY4yR5GT
UX/qqdk8Y+twj9RgM0F2NXQeDRXI7NafKtQ3JXav+wFzHEy9e8Oba1ZvbVEsKyRZ5MukqI7X5uyo
lNf1A/l5+rdsyaJJuInaudcDFw1TZuTU9UJ9wyaYG/t4JUdr7GDq/R+DQ33PgTuEsj6qck4aa1Av
bvNVvOzeO4DRbhEJRdtuIjLL9TuWAvVM1dMFGbuJOX2MuiYMnuBalhB3dMrbGmuFel8dHAoVzNdF
vTFO4v3mU46+ohFhFQbOFSpVAwj3H8RkZVf7y9WvvQUvtnDlCfhCJsaCt4XBoRXqfWVwcOTVltjr
ccehjhfiFO3hJa7vG4hCYUgPtCf7ZBi39C/fgJ8kf23ZLbHDM1A8d8xr6m1VcHij6nUkZAreHLe6
owRU5D5vh1mqCuAG9ZbBKNqEl0Bdp2zzL7ZySZYbstzw3hSWsg7WPeFSqR57Ky52i1tgrVDvK4OD
bqTIMEaD/rhxBcMLr/sIuNBNRZ4ZaCnfBvX6McSffMgGcTBQ+lLVJ+jQV8errl+/tUK924LDplvc
NHIy+SI2URy3WHRLut7HxhR/bdPfz6iwqFvEz2T4aaxk5Yryi1nRbXi32xBguA/DIayYl/kEipbz
SNIn/I5PMJESwvCSJsGj/FLXAnsj6m1Bu96SR7RCvduCw1vS9hZUoxXq3RYcWtCut+QRoXpfa0e0
Qr3bgsPJmvWd7Dt5qu9Uo02fmp4enh6m/Z3H1PAU7fOpz8Xu86Bdu3+NtnZtbW1teW15aHlodWj1
6tCq2PXV62rPYLfr9vyT5w8Cu/Dghws4aBM/TNBeTLx4sfJiRS2+shHfoFkbFuyl9ZL/7Wif1gr1
bgsO//yYdv7EeXzOnTjHD+2s2ujI2ZGRkdGvcPpq5NatKzhufXvrW35o36h9xwO2eA/H4r3xxfF7
47Pjswv/xrFwc+HmE9iM2PzMnfn57+fn5ub+M/dw7iHtxvqN9fXJ9cmnk0+XYVd/1C5BT1xnV2gX
CHowV94bhA3K+2P8RtRLtjxOnD8BtID72bmzgIvP6NnR0dGRUSGLz5UrQAsD2hpc4fsPQUu63y3C
QHd2nHTHZhcI98lNHE9myPfOY6VLvo9Ad5p0AdenK3h/vHrVF/xtav3BbaELvlD1i4kEAUPLImP9
X3N7tlaod1twIN2Pwfb8CQImXR8wtEvpEq9Kd4TShYIDug3qDfhSvIuzwAvAC6RLI13wfYyDdO/M
z83PPYJ6Rbw3HkK8kwD8dHJ5UuiuUr5BJHmu6r3wQNXry1ciBUPEntEyYyvU+0vBQbVLuBIZoFyN
DZCv0oV6b+FDtipeke83fmyohQZqV8W7OD47O7swRrg3b5LuDNX7eP7x/Ay1+73EBg0OUw+p3sl1
xgbI9yr4Smy4/uw2A/XzT4TuD4gOpLuSkOBA+SI47Iuu+elN/Bj06ad/5ecjHmc+OqP25ekzp788
LfY1bezry2OXYWNjl8cujV2C3b109+4X/HyhQXXmIo+L8xfnYY8Cm57+FwhOg+HU1PrU+vrU5OT9
SfwDxzVIdW15ddkf/q4/o2CFaBBvSTUQLclOaNwV5Urktcw+Ae+vO8LcIYGQQEggJBASCAmEBEIC
IYGQQEggJPDaCPwMvRYZKnuuLb4AAAAASUVORK5CYIIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAFAAUABIAAQCcAA8AAwAAAAAAAAAAAEQAAEDx/wIARAAMAAAAqDcOAAAA
BgBOAG8AcgBtAGEAbAAAAAIAAAAcAE9KAgBRSgIAX0gBBGFKGABtSAkEc0gJBHRICQRGAAFAAQAC
AEYADAAAAAAAAAAAAAkASABlAGEAZABpAG4AZwAgADEAAAAIAAEABiQBQCYAEgA1CIFDShQAT0oC
AFFKAgBcCIFQAAJAAQACAFAADAAAAAAAAAAAAAkASABlAGEAZABpAG4AZwAgADIAAAAOAAIAAyQB
BiQBQCYBYSQBFgA1CIFDShAAT0oCAFFKAgBcCIFeSgIAAAAAAAAAAAAAAAAAAABEAEFA8v+hAEQA
DAEAAAAAAAAAABYARABlAGYAYQB1AGwAdAAgAFAAYQByAGEAZwByAGEAcABoACAARgBvAG4AdAAA
AAAAVgBpAPP/swBWAAwBAAAAAAAAAAAMAFQAYQBiAGwAZQAgAE4AbwByAG0AYQBsAAAAIAA6VgsA
F/YDAAA01gYAAQUDAAA01gYAAQoDbABh9gMAAAIACwAAACgAawD0/8EAKAAAAQAAAAAAAAAABwBO
AG8AIABMAGkAcwB0AAAAAgAMAAAAAAA0AB9AAQDyADQADAAAAAAAAAAAAAYASABlAGEAZABlAHIA
AAANAA8ADcYIAALgEMAhAQIAAAA0ACBAAQACATQADAAAAAAAAAAAAAYARgBvAG8AdABlAHIAAAAN
ABAADcYIAALgEMAhAQIAAABCAF5AAQASAUIADAAAAAAAAAAAAAwATgBvAHIAbQBhAGwAIAAoAFcA
ZQBiACkAAAAQABEAE6RkABSkZABbJAFcJAEAADYAVUCiACEBNgAMAAAAAAAAAAAACQBIAHkAcABl
AHIAbABpAG4AawAAAAwAPioBQioCcGgAAP8AOgBCQAEAMgE6AAwAAAAAAAAAAAAJAEIAbwBkAHkA
IABUAGUAeAB0AAAAAgATAAwAQ0oSAE9KAgBRSgIAAAAAALkAAACqEQAAAQAAAAAAAAAAAP////8B
BAAAAAAAAP////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAuQAAALwAAAAAAAAAAAD//wAAAAAAAAAA
KAYAAKoRAAAIAAAoAAAAAP////8IADMoAAAAAP////8AAAAAAQAAAAIAAAADAAAABAAAAAUAAAAG
AAAAbAAAAG4AAABwAAAAcgAAAHQAAACQAAAAkgAAAJQAAABhAgAAYgIAAB8DAAAhAwAA/wMAAAAE
AAAtBQAALwUAAD0FAAA+BQAATQUAAGAFAACmBQAAzgUAAN0FAADqBQAAJAYAACUGAAAnBgAAKAYA
ACkGAAAqBgAAdAYAAHYGAAD6BwAA/AcAAP4IAAAACQAADgkAABAJAADXCQAAMAoAAIMKAAAQCwAA
egsAAOwLAABYDAAAWgwAAIEMAACDDAAAuQwAABANAABbDQAAjQ0AACEOAAC2DgAAYg8AAGQPAAB5
EAAAexAAAOQQAADlEAAA5hAAAOcQAADpEAAA6hAAAO0QAADuEAAA7xAAAKcRAACoEQAAqxEAAJgA
AAAAMAAAAAAAAACAAAAAgAAAADAAAAAAAACYAAAAADAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAA
AAAwAAAAAAAAAIAAAACAAAAAeAAAAAAAAJgAAAAAMAAAAAAAAACAAAAAgAAAAHgAAAAAAACYAAAA
ADAAAAAAAAAAgAAAAIAAAAB4AAAAAAAAmAAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAA
MAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAADAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAAAAw
AAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAAMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAADAA
AAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAAMAAA
AAAAAACAAAAAgAAAAAAAAAAAAACYAAAAADAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAAAAwAAAA
AAAAAIAAAACAAAAAAAAAAAAAAJgAAAAAMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAADAAAAAA
AAAAgAAAAIAAAAAAAAAAAAAAmAAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAAMAAAAAAA
AACAAAAAgAAAAAAAAAAAAACYAAAAADAAAAAAAAAAgAAAAIAAAAB4AAAAAAAAmAAAAAAwAAAAAAAA
AIAAAACAAAAAAAAAAAAAAJgAAAAAMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAADAAAAAAAAAA
gAAAAIAAAAAAAAAAAAAAmAAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAAMAAAAAAAAACA
AAAAgAAAAAAAAAAAAACYAAAAADAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAAAAwAAAAAAAAAIAA
AACAAAAAAAAAAAAAAJgAAAAAMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYAAAAADAAAAAAAAAAgAAA
AIAAAAAAAAAAAAAAmAAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAAMAAAAAAAAACAAAAA
gAAAAAAAAAAAAACYAAAAADAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmAAAAAAwAAAAAAAAAIAAAACA
AAAAAAAAAAAAAJgAAAAAMAAAAAAAAACAAAAAgAAAAHgAAAAAAAGYAAAAADAAAAAAAAAAgAAAAIAA
AAD4AAAAAAAAmAAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJgAAAAAMAAAAAAAAACAAAAAgAAA
AAAAAAAAAACYQAAAADAAAAAAAAAAgAAAAIAAAAB4AAAAAAAAmEAAAAAwAAAAAAAAAIAAAACAAAAA
AAAAAAAAAJhAAAAAMAAAAAAAAACAAAAAgAAAAAAAAAAAAACYQAAAADAAAAAAAAAAgAAAAIAAAAAA
AAAAAAAAmEAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJhAAAAAMAAAAAAAAACAAAAAgAAAAAgA
AAAAAACYQAAAADAAAAAAAAAAgAAAAIAAAAAIAAAAAAAAmEAAAAAwAAAAAAAAAIAAAACAAAAAAAAA
AAAAAJhAAAAAMAAAAAAAAACAAAAAgAAAAAgAAAAAAACYQAAAADAAAAAAAAAAgAAAAIAAAAAIAAAA
AAAAmEAAAAAwAAAAAAAAAIAAAACAAAAACAAAAAAAAJhAAAAAMAAAAAAAAACAAAAAgAAAAAgAAAAA
AACYQAAAADAAAAAAAAAAgAAAAIAAAAAIAAAAAAAAmEAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAAAA
AJhAAAAAMAAAAAAAAACAAAAAgAAAAAgAAAAAAACYQAAAADAAAAAAAAAAgAAAAIAAAAAIAAAAAAAA
mEAAAAAwAAAAAAAAAIAAAACAAAAACAAAAAAAAJhAAiAAMAAAAAAAAACAAAAAgAAAAAgAAAAAAACY
QAIgADAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmEACIAAwAAAAAAAAAIAAAACAAAAAeAAAAAAAAJhA
AiAAMAAAAAAAAACAAAAAgAAAAHgAAAAAAACYQAIgADAAAAAAAAAAgAAAAIAAAAAAAAAAAAAAmEAC
IAAwAAAAAAAAAIAAAACAAAAAeAAAAAAAAJhAAiAAMAAAAAAAAACAAAAAgAAAAHgAAAAAAACYQAAA
ADAAAAAAAAAAgAAAAIAAAAAQAAAAAAAAmEAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAAAAAJhAAAAA
MAAAAAAAAACAAAAAgAAAABAAAAAAAACYQAAAADAAAAAAAAAAgAAAAIAAAAAQAAAAAAAAmAAAAAAw
AAAAAAAAAIAAAACAAAAAEAAAAAAAAJgAAAAAMAAAAAAAAACAAAAAgAAAABAAAAAAAACYQAAADzAA
AAAAAAAAgAAAAIAAAAD4AAAAAIAHmEAAAA8wAAAAAAAAAIAAAACAAAAAAAAAAAAAAJhAAAAAMAAA
AAAAAACAAAAAgAAAAAAAAAAAgACYQAAAEDAAAAAAAAAAgAAAAIAAAAD4AAAAAIAAmEAAAAAwAAAA
AAAAAIAAAACAAAAAAAAAAACAAAgAAAAAMAAAAAAAAAAAAAAAAAAA0GJmBAcAAAeYAAAAADAAAAAA
AAAAgAAAAIAAAABIAAAAAAAAmAAAAAAwAAAAAAAAAIAAAACAAAAAAAAAAACAB4k8ATACEAAAAAAA
AAEAAAABAAAAAAAAAAAAZgMAAAAAqxEAAK46ATAAMAAAAAAAAAEAAAABAAAAAAAAACALnAcAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAEAAAACAAAAAgAAAAIAAAACAAAAAgAAAAI
AAAACAAAAAgAAAAIAAAACwAAAAAGAABzDgAAqhkAAA0AAAARAAAAAAYAAKYNAAB6EwAA7hgAAKoZ
AAAOAAAAEAAAABIAAAATAAAAAAYAAKkZAAAPAAAAKgQAAFEEAABiBAAA6gUAABEGAAAiBgAAqhEA
ABNYFP8VhBNYFP8VhA8AAPBAAAAAAAAG8CAAAAACDAAAAwAAAAMAAAACAAAAAgAAAAIAAAABAAAA
AgAAAEAAHvEQAAAA//8AAAAA/wCAgIAA9wAAEAEPAALwngAAACAACPAIAAAAAgAAAAEEAAAPAAPw
hgAAAA8ABPAoAAAAAQAJ8BAAAAAAAAAAAAAAAAAAAAAAAAAAAgAK8AgAAAAABAAABQAAAA8ABPBO
AAAAogwK8AgAAAABBAAAAAoAADMAC/ASAAAAgAAAAAEAigABBAAA/wEAAAgAAAAQ8AQAAAAAAAAA
AAAR8AQAAAAdAAAAAAAN8AQAAAAAAAEAAA8AAvCSAAAAEAAI8AgAAAABAAAAAQgAAA8AA/AwAAAA
DwAE8CgAAAABAAnwEAAAAAAAAAAAAAAAAAAAAAAAAAACAArwCAAAAAAIAAAFAAAADwAE8EIAAAAS
AArwCAAAAAEIAAAADgAAUwAL8B4AAAC/AQAAEADLAQAAAAD/AQAACAAEAwkAAAA/AwEAAQAAABHw
BAAAAAEAAAAEAAAACwAAAAEEAADEDgAAHgAAAEwsAABqAgAAdQABAAAA//8IAAAABgDXAB8AAAAB
ACTEGwAGANgAHwAAAAEAzMYbAAYA2QAfAAEAAQD8M+QBBgDaAB8AAQABALwz5AEGANsAHwAAAAEA
rJ0gAAYA3AAfAAEAAQA8XxcABgDdAB8AAAABAMwi5AEGAN4AHwABAAEA7PbwAYEDAADOBQAAzgUA
ANoFAAArEAAAKxAAAGYRAABmEQAAqxEAAAAAAAABAAIAAAACAAEAAAACAAMAAAACAAQAAAACAAUA
AAACAAYAAAACAAcAAAACAJEDAADYBQAA3AUAANwFAAAtEAAALRAAAGoRAABqEQAAqxEAAAAAAAAC
AAEAAQAAAAMAAAAEAAAABQAAAAYAAAAHAAAABQAAADkAAAAFAAAAKoB1cm46c2NoZW1hcy1taWNy
b3NvZnQtY29tOm9mZmljZTpzbWFydHRhZ3MFgFN0YXRlAIA4AAAABgAAACqAdXJuOnNjaGVtYXMt
bWljcm9zb2Z0LWNvbTpvZmZpY2U6c21hcnR0YWdzBIBDaXR5AIBCAAAAAwAAACqAdXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6c21hcnR0YWdzDoBjb3VudHJ5LXJlZ2lvbgCAVgAAAAcA
AAAqgHVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOnNtYXJ0dGFncwWAcGxhY2UdgGh0
dHA6Ly93d3cuNWlhbnRsYXZhbGFtcC5jb20vOAAAAAgAAAAqgHVybjpzY2hlbWFzLW1pY3Jvc29m
dC1jb206b2ZmaWNlOnNtYXJ0dGFncwSAZGF0ZQCADAAAAQEAAAAGAAAAAYAxBIAyMDA1AoAzMQOA
RGF5BYBNb250aASAWWVhcggAAwAAAAUAAAABAAAAAwAAAAIAAAAEAAAAAAAAAAcAAAAAAAYAAAAA
AAUAAAAAAAcAAAAAAAMAAAAAAAcAAAAAAAMAAAAAAAAAAADlEAAA5hAAAOYQAADnEAAA5xAAAOgQ
AADoEAAA7hAAAO8QAADvEAAApxEAAKcRAACoEQAAqxEAAAQABwAEAAcABAAHAAQABwACAAQABwAE
AAcABwAAAAAA5hAAAO4QAADvEAAAqxEAAAcABwACAAcAAAAAAN0FAAAnBgAA5hAAAO4QAADvEAAA
qxEAAAcABQAHAAcAAgAHAAAAAADmEAAA7hAAAO8QAACrEQAABwAHAAIABwD//wwAAAAKAEwAeQBu
AG4AIABCAGEAcgByAGEAAAAKAEwAeQBuAG4AIABCAGEAcgByAGEAAAAKAEwAeQBuAG4AIABCAGEA
cgByAGEAAAAKAEwAeQBuAG4AIABCAGEAcgByAGEAAAABACAAAAAPAEoAZQBuAG4AaQBmAGUAcgAg
AEcAYQByAG4AZQByAAAAAgC9Ly4ZxmGCZP8P/w//D/8P/w//D/8P/w//DxAANjapadbBcsn/D/8P
/w//D/8P/w//D/8P/w8QAAEAAAAXEAAAAAAAAAAAAABoAQAAAAAAABUYAAAPhDgEEYSY/hXGBQAB
OAQGXoQ4BGCEmP5PSgMAUUoDAG8oAIdoAAAAAIhIAAABAKfwAQAAABeQAAAAAAAAAAAAAGgBAAAA
AAAAGRgAAA+ECAcRhJj+FcYFAAEIBwZehAgHYISY/k9KBABRSgQAXkoEAG8oAIdoAAAAAIhIAAAB
AG8AAQAAABeQAAAAAAAAAAAAAGgBAAAAAAAAFRgAAA+E2AkRhJj+FcYFAAHYCQZehNgJYISY/k9K
AwBRSgMAbygAh2gAAAAAiEgAAAEAp/ABAAAAF5AAAAAAAAAAAAAAaAEAAAAAAAAVGAAAD4SoDBGE
mP4VxgUAAagMBl6EqAxghJj+T0oBAFFKAQBvKACHaAAAAACISAAAAQC38AEAAAAXkAAAAAAAAAAA
AABoAQAAAAAAABkYAAAPhHgPEYSY/hXGBQABeA8GXoR4D2CEmP5PSgQAUUoEAF5KBABvKACHaAAA
AACISAAAAQBvAAEAAAAXkAAAAAAAAAAAAABoAQAAAAAAABUYAAAPhEgSEYSY/hXGBQABSBIGXoRI
EmCEmP5PSgMAUUoDAG8oAIdoAAAAAIhIAAABAKfwAQAAABeQAAAAAAAAAAAAAGgBAAAAAAAAFRgA
AA+EGBURhJj+FcYFAAEYFQZehBgVYISY/k9KAQBRSgEAbygAh2gAAAAAiEgAAAEAt/ABAAAAF5AA
AAAAAAAAAAAAaAEAAAAAAAAZGAAAD4ToFxGEmP4VxgUAAegXBl6E6BdghJj+T0oEAFFKBABeSgQA
bygAh2gAAAAAiEgAAAEAbwABAAAAF5AAAAAAAAAAAAAAaAEAAAAAAAAVGAAAD4S4GhGEmP4VxgUA
AbgaBl6EuBpghJj+T0oDAFFKAwBvKACHaAAAAACISAAAAQCn8AEAAAAXEAAAAAAAAAAAAABoAQAA
AAAAABUYAAAPhDgEEYSY/hXGBQABOAQGXoQ4BGCEmP5PSgEAUUoBAG8oAIdoAAAAAIhIAAABALfw
AQAAABeQAAAAAAAAAAAAAGgBAAAAAAAAGRgAAA+ECAcRhJj+FcYFAAEIBwZehAgHYISY/k9KBABR
SgQAXkoEAG8oAIdoAAAAAIhIAAABAG8AAQAAABeQAAAAAAAAAAAAAGgBAAAAAAAAFRgAAA+E2AkR
hJj+FcYFAAHYCQZehNgJYISY/k9KAwBRSgMAbygAh2gAAAAAiEgAAAEAp/ABAAAAF5AAAAAAAAAA
AAAAaAEAAAAAAAAVGAAAD4SoDBGEmP4VxgUAAagMBl6EqAxghJj+T0oBAFFKAQBvKACHaAAAAACI
SAAAAQC38AEAAAAXkAAAAAAAAAAAAABoAQAAAAAAABkYAAAPhHgPEYSY/hXGBQABeA8GXoR4D2CE
mP5PSgQAUUoEAF5KBABvKACHaAAAAACISAAAAQBvAAEAAAAXkAAAAAAAAAAAAABoAQAAAAAAABUY
AAAPhEgSEYSY/hXGBQABSBIGXoRIEmCEmP5PSgMAUUoDAG8oAIdoAAAAAIhIAAABAKfwAQAAABeQ
AAAAAAAAAAAAAGgBAAAAAAAAFRgAAA+EGBURhJj+FcYFAAEYFQZehBgVYISY/k9KAQBRSgEAbygA
h2gAAAAAiEgAAAEAt/ABAAAAF5AAAAAAAAAAAAAAaAEAAAAAAAAZGAAAD4ToFxGEmP4VxgUAAegX
Bl6E6BdghJj+T0oEAFFKBABeSgQAbygAh2gAAAAAiEgAAAEAbwABAAAAF5AAAAAAAAAAAAAAaAEA
AAAAAAAVGAAAD4S4GhGEmP4VxgUAAbgaBl6EuBpghJj+T0oDAFFKAwBvKACHaAAAAACISAAAAQCn
8AIAAAC9Ly4ZAAAAAAAAAAAAAAAANjapaQAAAAAAAAAAAAAAAP////////////8CAAAAAAAAAP//
AgAAABIABQAJBAMACQQFAAkEAQAJBAMACQQFAAkEAQAJBAMACQQFAAkEEgABAAkEAwAJBAUACQQB
AAkEAwAJBAUACQQBAAkEAwAJBAUACQQDABJ0mSoAAAAAAAAAAAABAgACAG5wllMAAAAAAAAAAAAB
AgACAK4TB2UAAAAAAAAAAAABAgACABoAAAAEAAAACAAAAOUAAAAAAAAAGQAAANh3AwDSGgcAG1oL
AFkTDgCoNw4AI0AjABcHKQDaEDoAlnJDAGYgTAAVOU0AhX51AK5nhwCbbYwA1EOYAPYtnAAHe6MA
ITiwAHN0tAAgZcYAelDMAEYJ1gBJTeUAWmzmAOou9QASbPUA/0ADgAEA5RAAAOUQAACQgn0EAQAB
AOUQAAAAAAAA5RAAAAAAAAACEAAAAAAAAACqEQAAgAAAEABAAAD//wEAAAAHAFUAbgBrAG4AbwB3
AG4A//8BAAgAAAAAAAAAAAAAAP//AQAAAAAA//8AAAIA//8AAAAA//8AAAIA//8AAAAABQAAAEcW
kAEAAAICBgMFBAUCAwSHegAgAAAAgAgAAAAAAAAA/wEAAAAAAABUAGkAbQBlAHMAIABOAGUAdwAg
AFIAbwBtAGEAbgAAADUWkAECAAUFAQIBBwYCBQcAAAAAAAAAEAAAAAAAAAAAAAAAgAAAAABTAHkA
bQBiAG8AbAAAADMmkAEAAAILBgQCAgICAgSHegAgAAAAgAgAAAAAAAAA/wEAAAAAAABBAHIAaQBh
AGwAAAA7BpABAgAFAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAIAAAAAAVwBpAG4AZwBkAGkA
bgBnAHMAAAA/NZABAAACBwMJAgIFAgQEh3oAIAAAAIAIAAAAAAAAAP8BAAAAAAAAQwBvAHUAcgBp
AGUAcgAgAE4AZQB3AAAAIgAEADEIiBgA8NACAABoAQAAAAAyO4xGOjuMRjY7jEYFAAgAAACFAgAA
YQ4AAAEACAAAAAQAAxAeAAAAhQIAAGEOAAABAAgAAAAeAAAAAAAAACEDAPAQAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAPgBnQS0ALQAgYFyNAAAEAAZAGQAAAAZAAAA3hAAAN4QAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAA
AAAAAAAADTODUQDwEAAI3AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABIAAAAAAAo8P8PAQAB
PwAA5AQAAP///3////9/////f////3////9/////f////3+oNw4A//8SAAAAAAAAABkASQBuAHYA
bwBpAGMAZQAgAE4AdQBtAGIAZQByADoAIAAgADIAMAAwADQAMAAwADEAOAAAAAAAAAAKAEwAeQBu
AG4AIABCAGEAcgByAGEADwBKAGUAbgBuAGkAZgBlAHIAIABHAGEAcgBuAGUAcgAAAAAAAAAAAAAA
AAAAAAAAAAAAABQAAAAGAAAAAgAAAAAADAABAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD+
/wAABQECAAAAAAAAAAAAAAAAAAAAAAABAAAA4IWf8vlPaBCrkQgAKyez2TAAAACgAQAAEgAAAAEA
AACYAAAAAgAAAKAAAAADAAAAxAAAAAQAAADQAAAABQAAAOQAAAAGAAAA8AAAAAcAAAD8AAAACAAA
ABABAAAJAAAAKAEAABIAAAA0AQAACgAAAFABAAALAAAAXAEAAAwAAABoAQAADQAAAHQBAAAOAAAA
gAEAAA8AAACIAQAAEAAAAJABAAATAAAAmAEAAAIAAADkBAAAHgAAABoAAABJbnZvaWNlIE51bWJl
cjogIDIwMDQwMDE4AC4AHgAAAAEAAAAAbnZvHgAAAAsAAABMeW5uIEJhcnJhAGIeAAAAAQAAAAB5
bm4eAAAAAQAAAAB5bm4eAAAACwAAAE5vcm1hbC5kb3QAYh4AAAAQAAAASmVubmlmZXIgR2FybmVy
AB4AAAACAAAANQBubh4AAAAUAAAATWljcm9zb2Z0IFdvcmQgMTAuMABAAAAAADAaHgEAAABAAAAA
AGwKu4XcxAFAAAAAAFT9K4XcxAFAAAAAAIQXSobcxAEDAAAAAQAAAAMAAACFAgAAAwAAAGEOAAAD
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
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAUgBvAG8AdAAg
AEUAbgB0AHIAeQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABYA
BQH//////////wMAAAAGCQIAAAAAAMAAAAAAAABGAAAAAAAAAAAAAAAA0DC/kv/hxAFFAAAAwAMA
AAAAAABEAGEAdABhAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAACgACAf///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAABUAAACfJwAAAAAAADEAVABhAGIAbABlAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAOAAIBAQAAAAYAAAD/////AAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAKQAAADsfAAAAAAAAVwBvAHIAZABEAG8AYwB1AG0AZQBuAHQA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABoAAgECAAAABQAAAP////8A
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAZigAAAAAAAABAAAAAgAAAAMA
AAAEAAAABQAAAAYAAAAHAAAACAAAAAkAAAAKAAAACwAAAAwAAAANAAAADgAAAA8AAAAQAAAAEQAA
ABIAAAATAAAAFAAAAP7///8WAAAAFwAAABgAAAAZAAAAGgAAABsAAAAcAAAAHQAAAB4AAAAfAAAA
IAAAACEAAAAiAAAAIwAAACQAAAAlAAAAJgAAACcAAAAoAAAA/v///yoAAAArAAAALAAAAC0AAAAu
AAAALwAAADAAAAAxAAAAMgAAADMAAAA0AAAANQAAADYAAAA3AAAAOAAAAP7///86AAAAOwAAADwA
AAA9AAAAPgAAAD8AAABAAAAA/v///0QAAAD9/////v////7///9GAAAA/v//////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
/////////////////////////////////////////////////////////////wEAAAD+////AwAA
AAQAAAAFAAAABgAAAAcAAAAIAAAACQAAAAoAAAALAAAADAAAAA0AAAAOAAAA/v//////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////BQBTAHUAbQBtAGEA
cgB5AEkAbgBmAG8AcgBtAGEAdABpAG8AbgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACgAAgH/
//////////////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA5AAAAABAAAAAA
AAAFAEQAbwBjAHUAbQBlAG4AdABTAHUAbQBtAGEAcgB5AEkAbgBmAG8AcgBtAGEAdABpAG8AbgAA
AAAAAAAAAAAAOAACAQQAAAD//////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAIAAAAIAwAAAAAAAAEAQwBvAG0AcABPAGIAagAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAASAAIA////////////////AAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAGoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD///////////////8AAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAP7/AwoAAP////8G
CQIAAAAAAMAAAAAAAABGGAAAAE1pY3Jvc29mdCBXb3JkIERvY3VtZW50AAoAAABNU1dvcmREb2MA
EAAAAFdvcmQuRG9jdW1lbnQuOAD0ObJxAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AP7/AAAFAQIAAAAAAAAAAAAAAAAAAAAAAAIAAAAC1c3VnC4bEJOXCAArLPmuRAAAAAXVzdWcLhsQ
k5cIACss+a5IAQAABAEAAAwAAAABAAAAaAAAAA8AAABwAAAABQAAAIAAAAAGAAAAiAAAABEAAACQ
AAAAFwAAAJgAAAALAAAAoAAAABAAAACoAAAAEwAAALAAAAAWAAAAuAAAAA0AAADAAAAADAAAAOYA
AAACAAAA5AQAAB4AAAAFAAAASVRJQwAAaQADAAAAHgAAAAMAAAAIAAAAAwAAAN4QAAADAAAAexAK
AAsAAAAAAAAACwAAAAAAAAALAAAAAAAAAAsAAAAAAAAAHhAAAAEAAAAaAAAASW52b2ljZSBOdW1i
ZXI6ICAyMDA0MDAxOAAMEAAAAgAAAB4AAAAGAAAAVGl0bGUAAwAAAAEAAADAAQAAAwAAAAAAAAAg
AAAAAQAAAOQAAAACAAAA7AAAAAcAAAACAAAADAAAAF9QSURfSExJTktTAAMAAAAUAAAAX0FkSG9j
UmV2aWV3Q3ljbGVJRAAEAAAADgAAAF9FbWFpbFN1YmplY3QABQAAAA0AAABfQXV0aG9yRW1haWwA
BgAAABgAAABfQXV0aG9yRW1haWxEaXNwbGF5TmFtZQAHAAAAGQAAAF9SZXZpZXdpbmdUb29sc1No
b3duT25jZQAIAAAAHAAAAF9QcmV2aW91c0FkSG9jUmV2aWV3Q3ljbGVJRAACAAAA5AQAAEEAAADM
AAAADAAAAAMAAAAEACAAAwAAAAMAAAADAAAAAAAAAAMAAAAFAAAAHwAAABgAAABtAGEAaQBsAHQA
bwA6AHAAbQBvAHIAcgBpAHMAQABpAHQAaQBjAC4AbwByAGcAAAAfAAAAAQAAAAAAAAADAAAAAgAp
AAMAAAAAAAAAAwAAAAAAAAADAAAABQAAAB8AAAAYAAAAbQBhAGkAbAB0AG8AOgBqAGcAYQByAG4A
ZQByAEAAaQB0AGkAYwAuAG8AcgBnAAAAHwAAAAEAAAAAAAAAcgBuAGUAcgBAAGkAdABpAGMALgBv
AHIAZwAAAB8AAAABAAAAAAAAAAMAAABQ18LBHwAAAFUAAABKAFQAQwAgADEAIABTAFcARwAgAG8A
bgAgAEEAYwBjAGUAcwBzAGkAYgBpAGwAaQB0AHkAIAAtACAASQBuAHQA

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

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

--Apple-Mail-3-183641828--




From avt-bounces@ietf.org  Wed Dec 15 15:16:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05703
	for <avt-archive@ietf.org>; Wed, 15 Dec 2004 15:16:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cefht-0000FU-F0
	for avt-archive@ietf.org; Wed, 15 Dec 2004 15:25:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CefRu-00087m-Jj; Wed, 15 Dec 2004 15:08:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CefOU-0004Iw-B2
	for avt@megatron.ietf.org; Wed, 15 Dec 2004 15:05:07 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03766
	for <avt@ietf.org>; Wed, 15 Dec 2004 15:05:04 -0500 (EST)
Received: from wproxy.gmail.com ([64.233.184.194])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CefWi-0008LN-Jr
	for avt@ietf.org; Wed, 15 Dec 2004 15:13:40 -0500
Received: by wproxy.gmail.com with SMTP id 69so258087wri
	for <avt@ietf.org>; Wed, 15 Dec 2004 12:04:30 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding;
	b=jyyErH+pSTAgWgE2qv1af13BLLebVoYkmarcFNQeDbGZKhbqB28sGcflWuyzsumLJLCRquQuESINd7JqfFOfRzLO42AeqozOgQZ/oqeozHwa0JbkpM6GaVl6LnacwMfGgYNFy4jd+NSqLk0wy026V44xh0jNgUKQ/Pz/ipWWif0=
Received: by 10.54.47.65 with SMTP id u65mr575571wru;
	Wed, 15 Dec 2004 12:04:30 -0800 (PST)
Received: by 10.54.46.2 with HTTP; Wed, 15 Dec 2004 12:04:30 -0800 (PST)
Message-ID: <6e5aff6704121512046950e57@mail.gmail.com>
Date: Wed, 15 Dec 2004 17:04:30 -0300
From: Alejandro Cabrera Obed <aco1967@gmail.com>
To: AVT Lista <avt@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
Subject: [AVT] Using two or more RTP payload formats
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Alejandro Cabrera Obed <aco1967@gmail.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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit

Dear people,

Sorry for my newbie's question but I'm entering the streaming media world.

Just one short question: suppose I want to apply the RTP Payload
format for Uncompressed Video and also I'd want to apply the RTP
Paylod format for FEC to my RTP transport packets....Is it possible to
apply 2 or more RTP payloads format at the same time and to the same
RTP flow/session ???

Because I often saw one RTP payload format applied at a time....

(In the negative case what can I do then to transport uncompressed
video and FEC on a RTP flow ???)

Thanks a lot,

Alejandro Cabrera Obed

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


From avt-bounces@ietf.org  Thu Dec 16 07:09:09 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16786
	for <avt-archive@ietf.org>; Thu, 16 Dec 2004 07:09:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeuZv-0007Ks-7f
	for avt-archive@ietf.org; Thu, 16 Dec 2004 07:17:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeuLR-0002mM-W8; Thu, 16 Dec 2004 07:02:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeuKH-0002F4-8Y
	for avt@megatron.ietf.org; Thu, 16 Dec 2004 07:01:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15953
	for <avt@ietf.org>; Thu, 16 Dec 2004 07:01:41 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeuSW-00079B-7D
	for avt@ietf.org; Thu, 16 Dec 2004 07:10:28 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBGC1TO6004041 for <avt@ietf.org>; Thu, 16 Dec 2004 13:01:29 +0100
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 16 Dec 2004 13:01:29 +0100
Received: from [147.214.97.154] (permit154.er.ki.sw.ericsson.se
	[147.214.97.154]) by esealnt613.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id Y0BJJQ6G; Thu, 16 Dec 2004 13:01:29 +0100
Message-ID: <41C17918.3020001@ericsson.com>
Date: Thu, 16 Dec 2004 13:01:28 +0100
X-Sybari-Trust: 56db9b00 96d33411 ed1d98ce 00000138
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alejandro Cabrera Obed <aco1967@gmail.com>
Subject: Re: [AVT] Using two or more RTP payload formats
References: <6e5aff6704121512046950e57@mail.gmail.com>
In-Reply-To: <6e5aff6704121512046950e57@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 Dec 2004 12:01:29.0736 (UTC)
	FILETIME=[FA380080:01C4E366]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: 7bit
Cc: AVT Lista <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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: 7bit

Hi Alejandro,

RTP is designed to enable the usage of multiple payload types in the 
same RTP session. The usage of multiple payload types, is for example an 
result of desiring to use multiple payload formats or use multiple 
configurations of a payload format. The reason you usually see only a 
single payload format is that most applications is happy with a single 
one per RTP session.

This should be rather obvious from the SDP examples that are present in 
many RTP payload formats, especially the more generic ones. For example 
RFC 2733 has in section 11.2 the following SDP example:

    m=audio 12345 RTP/AVP 121 0 5 100
    a=rtpmap:121 red/8000/1
    a=rtpmap:100 parityfec/8000
    a=fmtp:121 0/5/100

However do please note that for example RFC 2733 provides two different 
choices of multiplexing, either in separate RTP sessions or as in the 
above example using RFC 2198.

Cheers

Magnus



Alejandro Cabrera Obed wrote:
> Dear people,
> 
> Sorry for my newbie's question but I'm entering the streaming media world.
> 
> Just one short question: suppose I want to apply the RTP Payload
> format for Uncompressed Video and also I'd want to apply the RTP
> Paylod format for FEC to my RTP transport packets....Is it possible to
> apply 2 or more RTP payloads format at the same time and to the same
> RTP flow/session ???
> 
> Because I often saw one RTP payload format applied at a time....
> 
> (In the negative case what can I do then to transport uncompressed
> video and FEC on a RTP flow ???)
> 
> Thanks a lot,
> 
> Alejandro Cabrera Obed
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
> 


-- 

Magnus Westerlund

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  Thu Dec 16 08:40:30 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22551
	for <avt-archive@ietf.org>; Thu, 16 Dec 2004 08:40:30 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cew0J-0001AK-US
	for avt-archive@ietf.org; Thu, 16 Dec 2004 08:49:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cevgp-0003Cj-MA; Thu, 16 Dec 2004 08:29:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeYkq-0002AI-Ic; Wed, 15 Dec 2004 07:59:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27910;
	Wed, 15 Dec 2004 07:59:42 -0500 (EST)
Received: from sophia.inria.fr ([138.96.64.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeYt4-0004sA-3S; Wed, 15 Dec 2004 08:08:14 -0500
Received: from localhost (localhost [127.0.0.1])
	by sophia.inria.fr (8.12.10/8.12.9) with ESMTP id iBFCgb7n004750;
	Wed, 15 Dec 2004 13:42:37 +0100
Received: from sophia.inria.fr (vesubie.inria.fr [138.96.112.27])
	by sophia.inria.fr (8.12.10/8.12.9) with ESMTP id iBFCcUko003419;
	Wed, 15 Dec 2004 13:38:30 +0100
Message-ID: <41C03046.DC65B8A1@sophia.inria.fr>
Date: Wed, 15 Dec 2004 13:38:30 +0100
From: Sara Alouf <Sara.Alouf@sophia.inria.fr>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.22 i686)
X-Accept-Language: en, fr, pt
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
To: undisclosed-recipients:;
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.4
	(sophia.inria.fr [138.96.64.20]);
	Wed, 15 Dec 2004 13:42:09 +0100 (MET)
X-Virus-Scanned: by amavisd-new at sophia.inria.fr
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by sophia.inria.fr id
	iBFCgb7n004750
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 827a2a57ca7ab0837847220f447e8d56
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 16 Dec 2004 08:29:07 -0500
Subject: [AVT] Performance 2005: Call for Papers
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e472ca43d56132790a46d9eefd95f0a5
Content-Transfer-Encoding: quoted-printable

  ** Apologies for multiple copies of this message **

                   ***************
                   CALL FOR PAPERS
                   ***************

                   PERFORMANCE 2005

The 24th IFIP WG 7.3 International Symposium on Computer=20
Performance Modeling, Measurement and Evaluation

                   October 3-7, 2005
                 Juan-les-Pins, France
       http://www-sop.inria.fr/maestro/performance2005/

Sponsored by IFIP WG 7.3, the Computer Performance Foundation=20
and INRIA


The PERFORMANCE 2005 conference solicits papers on the=20
development and application of state-of-the-art analytic,=20
simulation, and measurement-based performance evaluation=20
techniques. Topics of interest include, but are not=20
limited to:

* Performance-oriented design and evaluation of:
  communication networks, mobile and wireless systems,
  Internet servers and E-commerce systems, Web services,
  Web architectures, peer-to-peer systems, grid computing,
  computer architectures, database systems, operating
  systems, software systems, distributed systems,=20
  multimedia systems, file and I/O systems, memory
  systems, real-time systems, and fault-tolerant systems.

* Techniques and algorithms: analytic modeling, performance
  optimization, queueing analysis, stochastic scheduling,
  model verification and validation, power analysis, hybrid
  models, experimental design, system or network measurement
  and monitoring, workload characterization, simulation,=20
  and statistical analysis.

** SUBMISSION GUIDELINES **

PAPERS: Papers should not exceed 20 double-spaced pages=20
including figures, tables and references. A limited number=20
of submitted papers will be accepted for a poster session.=20
Submissions must be made electronically as Postscript or=20
Adobe PDF files through the Conference Web site=20
(http://www-sop.inria.fr/maestro/performance2005/).
In case of problems, please send papers by email to=20
papers.perf2005@sophia.inria.fr
Papers will be selected on the basis of their originality,=20
technical standards, relevance and clarity.=20

Full papers will be published in a special issue of the Journal=20
Performance Evaluation (Elsevier) available at the conference.

TUTORIAL SESSIONS: Tutorial proposals, not exceeding 3 pages,=20
have to include title, abstract, duration (1H30 or 3H),=20
intended audience, assumed background of attendees, name,=20
affiliation and a biographical sketch of the instructors.=20
Proposals should be sent to the tutorials co-chairs
(tutorials.perf2005@sophia.inria.fr).

HOT/CONTROVERSIAL TOPIC SESSIONS: Proposals are solicited for=20
a hot topic session, in which a group of speakers will present=20
and discuss their recent results in an area. Send proposals to=20
the program co-chairs, identifying the organizer of the session,=20
the session title, three to five speakers, the titles of their=20
talks, and a short abstract of each talk.

** IMPORTANT DATES **

FEBRUARY 22, 2005  Title, abstract and author affiliation due.
MARCH 1, 2005      Submission of papers, hot topic proposals
                   and tutorial proposals.=20
JUNE 1, 2005       Notification of acceptance.
JULY 1, 2005       Camera ready copy due.

For Further Information:
    info.perf2005@sophia.inria.fr
    http://www-sop.inria.fr/maestro/performance2005/

** ORGANIZING COMMITTEE **

GENERAL CHAIR:=20
       Philippe Nain, INRIA, France=20

PROGRAM COMMITTEE CO-CHAIRS:=20
       Cheng-Shang Chang, National Tsing Hua U., Taiwan=20
       Daniel A. Menasce, George Mason U., USA

TUTORIALS CO-CHAIRS:=20
       Eitan Altman, INRIA, France
       Zhen Liu, IBM T. J.Watson Reseach Center, USA

LOCAL ARRANGEMENTS CO-CHAIRS:=20
       Konstantin Avrachenkov, INRIA, France
       Ephie Deriche, INRIA, France
      =20
FINANCE CHAIR: Dany Sergeant, INRIA, France

PUBLICITY CHAIR: Sara Alouf, INRIA, France

PROCEEDINGS CHAIR:=20
       Rudesindo N=FA=F1ez Queija, CWI, The Netherlands

** PROGRAM COMMITTEE **

Almeida, Virgilio               UFMG, Brazil
Baccelli, Francois              ENS, France
Bonald, Thomas                  France Telecom, France
Borst, Sem                      CWI, the Netherlands
Calzarossa, Mariacarla          U. Pavia, Italy
de Souza e Silva, Edmundo       UFRJ, Brazil
Duffield, Nick                  AT&T Research, USA
Eager, Derek                    U. Saskatchewan, Canada
Gelenbe, Erol                   Imperial College, UK=20
Golubchik, Leana                USC, USA
Harchol-Balter, Mor             Carnegie Mellon U., USA
Haring, Guenter                 U. Wien, Austria
Harrison, Pete                  Imperial College, UK
Haverkort, Boudewijn            U. Twente, the Netherlands
Herzog, Ulrich                  Friedrich Alexander U., Germany
Hou, Jennifer                   U. Illinois Urbana Champaign, USA
Hsu, Yarsun                     National Tsing Hua U., Taiwan
Iazeolla, Giuseppe              U. Roma "Tor Vergata", Italy
Jean-Marie, Alain               U. Montpellier & INRIA, France
Kumar, Anurag                   IISc, India
Kurose, Jim                     U. Massachusetts, USA
Le Boudec, Jean-Yves            EPFL, Switzerland
Lee, Duan-Shin                  National Tsing Hua U., Taiwan
Liebeherr, Jorg                 U. Virginia, USA
Lindemann, Christoph            U. Dortmund, Germany
Lui, John                       Chinese U. of Hong Kong, China
Marsan, Marco A.                Politecnico di Torino, Italy
Mazumdar, Ravi                  U. Waterloo, Canada
Merchant, Arif                  HP Labs, USA
Misra, Vishal                   Columbia U., USA
Mitra, Debasis                  Bell Laboratories, USA
Muntz, Richard R.               UCLA, USA
Nicol, David                    U. Illinois Urbana-Champaign, USA
Perros, Harry                   North Carolina State U., USA
Sanders, William                U. Illinois Urbana-Champaign, USA
Serazzi, Giuseppe               Politecnico di Milano, Italy
Setia, Sanjeev                  George Mason University, USA
Smirni, Evgenia                 College of William and Mary, USA
Squillante, Mark                IBM Research, USA
Stewart, William                North Carolina State U., USA
Thomasian, Alexander            NJIT, USA
Trivedi, Kishor                 Duke U., USA
Tucci, Salvatore                U. Roma "Tor Vergata", Italy
Vernon, Mary                    U. Wisconsin-Madison, USA
Verscheure, Olivier             IBM Research, USA
Williamson, Carey               U. Calgary, Canada
Woodside, C. Murray             Carleton U., Canada
Xia, Cathy                      IBM Research, USA
Yao, David                      Columbia U., USA
Zhang, Zhi-Li                   U. Minnesota, USA

--
Sara Alouf
Publicity Chair

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


From avt-bounces@ietf.org  Thu Dec 16 10:25:03 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04765
	for <avt-archive@ietf.org>; Thu, 16 Dec 2004 10:25:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CexPC-0004M0-1l
	for avt-archive@ietf.org; Thu, 16 Dec 2004 10:19:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CexFS-0008NG-6B; Thu, 16 Dec 2004 10:08:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CexEy-00089b-OS
	for avt@megatron.ietf.org; Thu, 16 Dec 2004 10:08:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02823
	for <avt@ietf.org>; Thu, 16 Dec 2004 10:08:25 -0500 (EST)
Received: from mailrelay.pel.panasonic.de ([194.162.191.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CexNP-00047p-1O
	for avt@ietf.org; Thu, 16 Dec 2004 10:17:12 -0500
Received: from localhost ([127.0.0.1]) by MailRelay.PEL.Panasonic.de;
	Thu, 16 Dec 2004 16:07:49 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Thu, 16 Dec 2004 16:07:50 +0100
Message-ID: <9D277E44D6EF0942B928C6F0DE99BB3164B2DF@lan-ex-01.panasonic.de>
Thread-Topic: Update (-08) Timed Text draft 
Thread-Index: AcTjgQKEvyesqsXfSZeXBzjBwfvEFg==
From: "Rey Jose" <Rey@panasonic.de>
To: <avt@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 57b3d456dc4730784e7070d5c6b7d14f
Content-Transfer-Encoding: quoted-printable
Cc: "Magnus Westerlund \(KI/EAB\)" <magnus.westerlund@ericsson.com>,
        Colin Perkins <csp@csperkins.org>
Subject: [AVT] Update (-08) Timed Text draft 
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8e140a89d08e89747ee196e282ac2228
Content-Transfer-Encoding: quoted-printable

Hi Magnus, Colin, All,

I've just sent an update to the ID manager.  You can get it here until
is published
http://www.prdcg.panasonic.de/ietf/docs/draft-ietf-avt-rtp-3gpp-timed-te
xt-08.txt

Below are the comments and actions taken in the draft -08. The first
part is the issues pending (until the "Non-issues" mark); the second one
is the the non-issues; this part is just there for quick checking of
each comment. Not necessarily to be read, if one reads the draft anyway.


I have introduced many figures, 2 new sections on relation to RFC2793
and RFC3640. Also re-arranged into introduction, motivation, basics of
the format, requirements and limitations at the beginning.  I hope it is
easier to read now.


------
[CP]
In Section 3.1.2, SDUR has 3 bytes, since two bytes gives limited
maximum duration. This will be true no matter what: is it appropriate to
place a fixed maximum? Or to define a way in which event duration can be
extended by a following packet to allow unlimited duration events?
[JR]
"o	SDUR (24 bits) "Text Sample Duration": indicates the sample
duration in RTP timestamp units of the text sample.  For this field, a
length of 3 bytes is preferred to 2 bytes.  This is because, for a
typical clockrate of 1000 Hz, 16 bits would allow for a maximum duration
of just 65 seconds, which might be too short for some streams.  On the
other hand, 24 bits at 1000 Hz allow for a maximum duration of about 4.6
hours, while for 90 KHz, this value is about 3 minutes.  These values
should be enough for streaming applications.  However, if a larger
duration is needed, the extension mechanism specified in Section 4.2
SHALL be used."

An extension mechanism has been defined. Thereby a copy of the sample
with adjusted timestamp and duration is sent:
"I.e., a sample with timestamp TS and duration SDUR can be sent as two
samples having timestamps TS1 and TS2 and durations SDUR1 and SDUR2,
such that TS1=3DTS, TS2=3DTS1+SDUR1 and SDUR=3D SDUR1+SDUR2."

Comments?
--
[JR]
Also the draft states now explicitly that a limitation is not being able
to convey packet sizes larger than a 16 bits integer.  This is a design
choice and it is considered enough for streaming apps. There is no
extension mechanism defined for this reason. Comments?
--
[MW]
> 14. Section 8.2.2: Last bullet: The usage of "sver" in multicast? Is
it really possible to offer more=20
> than one version that all uses? Especially if the version result in
that different parsing of the samples  > must be used, then one can=20
>really only offer one. Otherwise one needs to agree on the version
used.

[JR]
I think so: as "sver" is defined currently if a newer extension to the
3GPP TS26245 is done which is not backwards-compatible with previous
versions or cannot be discarded, then this version will not be listed in
the "sver" param list (per definition). So this case cannot happen in
the first place.=20

Thus, if alternative non-compatible versions are offered, then this
should be done using different payload types. Is this acceptable?

On the other hand, it is the question whether the "sver" may be
obviated. We say that parameters that are not understood by the SDP
consumer are ignored and the timed text format itself is
backwards-compatible.  then there's no need, correct?=20

--
[JR]

I've been asked by some MPEG people whether it would be possible to
introduce a header that uses char counter to allow the number of chars
lost to be known. Obviously I have no time to do this.  But, could a new
header be added later? There are three types remaining "TYPE 0, 6 and 7
are reserved." Could the number be used in a later complementary draft?
---
[JR]

I've done some more emphasis on packet repetition as a means for
resilient transport, in particular on carousel data transmission in
section about resilient transport.  Since one of the main applications
will be for multicast and timed text has low bitrates, I think RTP
carousel should be a good trade-off, instead of choosing more complex
redundancy methods such as rfc2733 or reliable multicast.  Comments?
--
[MW]
11. Section 8.2.1, bullet 1, a, i: Should it also be added, that unless
special=20
preference exist the offered value should be used?

[JR]

Hhmmm... a) if not used then the answerer MUST ensure that the
preference of the offerer are compatible with the values offered, how
makes this sense?? and b) what should be done if this is not so?? A
behaviour for error case shall be defined...no?

Accordingly, in the second bullet the second MUST changed to SHOULD.

This is what I wrote:

"
a.	"tx", "ty" and "layer": these are parameters describing where
the received text track is placed.  Depending on the directionality:
i.	MUST appear in all sendrecv offers and answers and in all
recvonly offers and answers(thus applying to the incoming stream).  In
the case of sendrecv offers and answers and in recvonly offers, these
values SHOULD be used by the sender of the stream unless it has a
particular preference, in which case, it MUST make sure that these
different values do not corrupt the presentation.  For recvonly answers,
the answerer MAY accept the proposed values for the incoming stream (in
a sendonly offer, see bullet below) or respond with different ones.  The
offerer MUST use the returned values. =20

ii.	MAY appear in sendonly offers and MUST appear in sendonly
answers.  In sendonly offers they specify the values that the offerer
proposes for sending (see example in Section 9.3).  In sendonly answers
these values SHOULD be copied from the corresponding recvonly offer upon
accepting the stream, unless a particular preference by the receiver if
the stream exists, as explained in the previous bullet "
---

[MW]
7. Section 7.1: I think that a number of parameters are misclassified.
Any=20
parameter that do not need to be included in all messages belongs under
Optional=20
parameters. I think that include: max-w, max-h, width, and height. This
also has=20
effect in 8.1.
[JR]
What means are "all" messages? Sendrecv or recvonly O & A? I thought
about all possibilities and created a new table:

+..---------------------------+----------+----------+----------+
|   ``--..__  Directionality/ | sendrecv | recvonly | sendonly |
+ Type of   ``--..__   O or A +----------+----------+----------+
|    Parameter      ``--..__  |   O/A    |   O/A    |   O/A    |
+--------------+------------``+----------+----------+----------+
| Declarative  |tx, ty, layer |   M/M    |   M/M    |   m/M    |
|              |              |          |          |          |
+--------------+--------------+----------+----------+----------+
| Display      |max-h, max-w  |   M/M    |   M/M    |   -/-    |
| Capabilities |              |          |          |          |
+--------------+--------------+----------+----------+----------+
| Stream       |height, width |   M/M    |   -/(M)  |   M/M    |
| properties   |tx3g          |   m/m    |   -/-    |   m/m    |
|              |              |          |          |          |
+--------------+--------------+----------+----------+----------+
|  Negotiable  |sver          |   M/M    |   M/M    |   M/M    |
|              |              |          |          |          |
+--------------+--------------+----------+----------+----------+
|  Symmetric   |rate          |   M/M    |   M/M    |   M/M    |
+--------------+--------------+----------+----------+----------+
Table 1. Parameter usage in Unicast Offer /Answer.

Key:
o M means MUST be present
o m means MAY be present (such as proposed values)
o (m) or (M) means MUST or MAY, when applicable
o means MUST NOT be present.
---

[MW]
15. Section 8.3:
"In this case the answerer's "max-h" and
   "max-w" are compatible with the offerer's "height" and "width".
   Otherwise, the answerer would have to remove this stream and the
   answerer issue a new offer taking the answerer's capabilities into
   account."

I would like to make you aware that the offerer will not receive a
payload type=20
at all if the answerer has to refuse the stream due to that height and
width are=20
larger then the supported max-w and max-h. The only way to ensure that
this=20
would happened would be do define multiple payload types, with at least
one that=20
is guaranteed to be acceptable, thus allowing the answerer to give his
max-w and=20
max-h parameters. Then the offerer can re-issue the offerer with the
knowledge=20
about the answerers capability.

[JR]
I added the following:=20
"In this case the answerer's "max-h" and "max-w" are compatible with the
offerer's "height" and "width".  Otherwise, the answerer would have to
remove this stream and the offerer would have to issue a new offer
taking the answerer's capabilities into account.  This is possible only
if multiple payload types are present in the initial offer so that at
least one of them matches the answerer's capabilities as expressed by
"max-h" and "max-w" in the negative answer.  Note also that the
answerer's text box dimensions fit within the within the maximum values
signalled in the offer.  Finally, the answerer chooses to use version 60
of the timed text format."
---

----------
----------
Non-issues
----------
----------

[JR]
I've introduced a section (after Colin's comment) on relation to RFC3640
and RFC2793.  AS well as example payloads.
---
[CP]
"Section 2.3.3 (last bullet point on page 9) mentions that "it does not
seem reasonable to include such additional headers". What headers are
these? The text preceding talks about intelligent fragmentation, but
it's not clear that this needs extra headers."

Added:

Informative note: ensuring that partially received modifiers can be
applied to text strings in all cases (for all modifier types and for all
fragment loss constellations) would place additional requirements on the
payload format.  In particular this would require that: a) senders
understand the semantics of the modifier boxes (where does it field of
the modifier start and end, what the fields indicate,...) and b)
specific fragment headers for each of the modifier boxes are defined (in
addition to the payload formats defined below.)  This would be necessary
to apply each piece of the modifiers received independent of previous
packet losses.  This requires complex headers.  Given the low
probability of fragmentation and the desire to keep the requirements
low, it does not seem reasonable to specify such modifier box specific
headers.

[CP]
"In section 2.2, requirement 1 is to keep the 3GP text sample structure.

This is justified by stating that a receiver SHALL be able to rebuild
the text samples from the received RTP packets. I agree that rebuilding
the text samples is an appropriate goal, but don't see why this requires
the payload format to keep the 3GP text sample structure? We have other
payload formats that modify the data format to optimise media transport,
but allow reconstruction of the original data."

[JR]
It should rather be new reqs 1&2. It should rather be new reqs 1&2:

"1.	It SHALL enable both live streaming and streaming from a 3GP
file. =20

..

2.	Furthermore, it SHALL be possible for an RTP receiver using this
payload format, and capable of storing in 3GP format, to obtain all
necessary information from the RTP packets for storing the received text
contents according to the 3GP file format.  This file MAY or MAY NOT be
the same as the original file."

[CP]
"In section 2.2, requirement 3 states that it may be more appropriate to
send large sample descriptions in-band. What is the justification for
this? In-band transmission would seem inappropriate for large
descriptions, since they're more likely to be affected by packet loss
than smaller descriptions that fit into a single packet."

[JR]
Fixed:
3.	It SHALL enable efficient and resilient transport of timed text
contents over RTP.  The following measures are taken:

a.	Enable the transmission of the sample descriptions both by
out-of-band and in-band means.  Sample descriptions are important
information, which potentially apply to several text samples.  These
default formatting settings are typically transmitted out-of-band
(reliably) once at the initialization phase.  If sample descriptions are
needed in the course of a session, these may be sent also out-of-band or
in-band.  In-band transmission, although unreliable, may be more
appropriate for sending sample descriptions if these should be sent
frequently, as opposed to establishing an additional communication
channel for SDP, for example.  It is also useful in cases where an
out-of-band channel may not be available and for live streaming, where
contents are not known a priori.  In order to cover this wide range of
scenarios, the payload format SHALL enable both in-band and out-of-band
transmission of sample descriptions.  Section 4.1.6 specifies a payload
header for transmitting sample descriptions in-band.  Section 9
specifies how sample descriptions are mapped to SDP.

[MW]

"18. Section 12.1: The algorithm description. I have some problem with
the current description. Bullet 3, has an IF without an clear argument.
Also I think it fails to properly describe if the new X must be the next
value or values above the current active set. Or if one is allowed to
send an X=3D127 in a session that had the inactive set to be "

[JR]
Better:   Let X be the SIDX of the last received sample description.
Let Y=20
  be a value within the allowed range for dynamic SIDX: [0,127], and=20
  different from X.

1.	Initialize all dynamic SIDX values as inactive.  For stored
content, read the sample description index in the Sample to Chunk box
("stsc") for that sample.  For live streaming, the first value MAY be
zero or any other value in the interval above.  The initial value is
SIDX=3DX.  Go to step 2.
2.	First in-band sample description with SIDX=3DX is received. Go to
step 3.
3.	Set SIDX=3DY inactive if Y inside the (inclusive) interval [X+1
modulo(128), X+64 modulo(128)].  Otherwise, set SIDX=3DY as active.  Go =
to
step 4.
4.	Wait for next sample description.  Upon reception of a sample
description with SIDX=3DX do:=20
a.	If X is currently active, then wait for next SIDX (do nothing).

b.	Else go to step 3.

Informative note: note that it is allowed to send any value of SIDX=3DX =
in
the interval [0,127].  E.g. if [64..127] is the current active set and
65 is sent a new sample description is defined and an old one deleted
(64).  Similarly one could send X=3D127, thus inverting the active and
inactive sets.

[CP]
"Section 2.3.4 specifies how packets are formed from samples and
modifiers. The rules listed in the numbered list at the start of the
sections allow empty packets, but the preceding text specifies that at
least one unit of data must be included. Which is correct?"

-A small sentence has been added "At least one unit of either type MUST
be present.  "

[CP]
"The first observation in section 2.3.4 (near the end of page 10) states
that type 5 units may be placed anywhere in the aggregate, and SHALL NOT
be regarded for calculating the timestamp (indeed, they MUST be ignored
when calculating the timestamp). The numbered rules for aggregate
payload earlier in the section allow a packet that comprises only a type
5 unit. What is the RTP timestamp for such a packet, given that type 5
units MUST be ignored when calculating timestamps?"

[JR]
Yes, good point.

The text now is:

o	TYPE 5 units MAY be placed anywhere in the aggregate and they
SHALL NOT be regarded for calculating the timestamp of the subsequent
units.  This is because they usually do not belong to any text sample in
particular, but may apply to several.  For timestamp calculations, TYPE
5 units MUST simply be ignored, i.e. by jumping to the next unit.  For
setting the timestamp in packets containing TYPE 5 units refer to
Section 3, timestamp definition.


[CP][MW]
Section 3 again notes that TYPE 5 units do not make use of the
timestamp. All RTP packets need a valid timestamp; if only TYPE 5 units
are included, what value does it take?

Secondly, I think some clarification on when Type 5 packets shall be
assumed to become active. From the point they are received, when they
are unpacked, i.e. order in the RTP packet may have some meaning, or
when other packets type the type 5 was attached to is utilized. I think
this has some impact, although the guard band for dynamic types normally
would prevent it."

[JR]
Now:
"Note that TYPE 5 units do not make use of the timestamp and therefore
the above does not apply to them.  TYPE 5 units become active upon
reception and not at the time instant indicated by the timestamp.  In
RTP packets containing only TYPE 5 unit(s), the RTP timestamp SHALL be
set to the current value of RTP timestamp."=20


[CP]
Section 3.1.2 has an "example that illustrates how units of unknown
duration MUST be presented". If there's a rule, it need to be defined
explicitly, not by a single example.
[JR]
Text samples have generally a known duration at the time of
transmission.  However, in some cases like live streaming, the time for
which a text piece shall be presented might not be known a priori.  For
this case, the value zero SDUR=3D0 (0x000000) is reserved to signal
unknown duration.  The amount of time that a sample of unknown duration
is presented is determined by the timestamp of the next sample that
shall be displayed at the receiver.  Text samples of unknown duration
SHALL be displayed until the next text sample becomes active, as
indicated by its timestamp.  Note that only text samples to be actually
displayed SHALL replace them, while discarded samples (e.g. because of
missing fragments) or sample descriptions alone SHALL NOT terminate
display of a sample of unknown duration.

[CP]
Section 3.1.2 (top of page 22) says that only TYPE 5 units can follow
units of unknown duration otherwise it's not possible to calculate the
timestamp. Which timestamp does that refer to? The RTP timestamp of the
packet or that (implied) for the following unit? Please clarify.
[JR]
Note that samples of unknown duration SHALL NOT use features, which
require knowledge of the duration of the sample up front.  Such features
are scrolling and karaoke in [1].  Furthermore, only sample descriptions
(TYPE 5) MAY follow units of unknown duration in the same aggregate
payload.  Otherwise, it would not be possible to calculate the timestamp
of these other units. =20

[CP]
Section 3.1.2 (last two bullets) explains that the TLEN is needed by the
decoder to know where the modifiers in the payload start. It's not clear
what this means: does the text string include modifier boxes? I thought
TYPE 1 units transported text samples only, and that any modifiers would
be part of a TYPE 5 unit later?
[JR]
No, TYPE 1 units carry text samples (defined in Terminology). Text
samples carry text strings + zero or more modifiers.  TYPE 5 OTH carry
sample descriptions, which specify default settings that may be modified
by modifiers.  I added minimum changes to the text:
"o	Finally, the actual text sample follows the TLEN field.  As
defined in Section 3, a text sample consists of a string of characters
encoded using either UTF-8 or UTF-16, followed by zero or more
modifiers.  Note also, that no BOM and no byte count are included in the
strings carried in the payload (as opposed to text samples stored in 3GP
files [1])."

[CP]
Similar comment for section 3.1.3, where SLEN indicates the size of the
text string plus any modifier boxes. From the description earlier, it
can be read that there are no modifiers and only text here?
[JR]
I included also a reference to the terminology section.

[CP]
Section 3.1.3 states that LEN MUST be greater than 9. What is the
response to a packet where LEN <=3D 9? (similar comments apply for =
section
3.1.4, 3.1.5 and 3.1.6)
[JR]
Done. Units should be discarded.

[CP]
Section 3.1.3 what should a receiver do if it receives fragments with
differing SLEN values?
[JR]
Discard. Added:
"If a receiver receives fragments of the same text sample (identified by
the timestamp) with differing SLEN, these should be discarded.  Either
the SLEN is known at the moment of sending the packet or it is unknown
but it SHALL NOT change for different fragments."

[CP]
Sections 3.1.3, 3.1.4 and 3.1.5, what should a receiver do if it
receives units where THIS > TOTAL? Or if TOTAL =3D 0?
[JR]
Discard.Added:
"In all cases (TYPEs 2, 3 and 4), if THIS > TOTAL or if TOTAL =3D 0, the
fragment SHALL be discarded."

[CP]
Section 7.1 states that a receiver MUST ignore any "unspecified" =20
parameter. Can you clarify what this means? Did you intend to write
"unrecognised"?
[JR]
Yes.

[CP]
Section 7.1 defines a number of parameters as "16 bit integers" or as
"16 bit unsigned integers". Does this mean that the parameters are in
binary format? Or do you intend (as in the examples in section 8) that
the decimal representation is used?
[JR]
Decimal representation.

[CP]
Section 8.1, last bullet point says that unknown parameters SHALL be
ignored. Does this mean that they're not copied into the SDP (i.e. =20
ignored by the device generating the SDP)? Or are they copied, but
ignored by the device that later uses the SDP? Please clarify.
[JR]
Added:

"o	Any unknown parameter to the device that uses the SDP SHALL be
ignored.  E.g. parameters added in later media format specifications MAY
be copied into the SDP and SHALL be ignored by receivers that do not
understand them."
"
[CP]
Please add some examples of complete RTP packets and their contents, for
several combinations of unit types, including all the headers and data.
[JR]
Added.

[CP]
These lead to a bigger question: lease clarify the contents of the
payload. Is it a single logical block, with the headers giving pointers
to sub-parts of the block? Or is it multiple logical blocks (some text,
some modifiers) stacked after the headers in order?
[JR]
Hopefully (!) clarified with  examples.



---------------------------------------------
Jose Rey              mailto:rey@panasonic.de
P R D C G - Panasonic R&D Center Germany GmbH
Phone/Fax: +49(0)6103766-134/166
---------------------------------------------=20


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


From avt-bounces@ietf.org  Thu Dec 16 16:10:19 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09528
	for <avt-archive@ietf.org>; Thu, 16 Dec 2004 16:10:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cf31h-0000Dv-Pu
	for avt-archive@ietf.org; Thu, 16 Dec 2004 16:19:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cf2mc-0005vF-Rm; Thu, 16 Dec 2004 16:03:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cf2eB-0001X1-4N; Thu, 16 Dec 2004 15:54:51 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08071;
	Thu, 16 Dec 2004 15:54:48 -0500 (EST)
Message-Id: <200412162054.PAA08071@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 16 Dec 2004 15:54:48 -0500
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-vmr-wb-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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5

--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		: Real-Time Transport Protocol (RTP) Payload Formats for 
			  the Variable-Rate Multimode Wideband (VMR-WB) Audio Codec
	Author(s)	: S. Ahmadi
	Filename	: draft-ietf-avt-rtp-vmr-wb-07.txt
	Pages		: 29
	Date		: 2004-12-16
	
This document specifies a real-time transport protocol (RTP) payload
   format to be used for the Variable-Rate Multimode Wideband (VMR-WB)
   speech codec. The payload format is designed to be able to
   interoperate with existing VMR-WB transport formats on non-IP
   networks. A MIME type registration is included for VMR-WB RTP 
   payload formats.

   VMR-WB is a variable-rate multimode wideband speech codec that has a
   number of operating modes, one of which is interoperable with AMR-WB
   (i.e., RFC 3267) audio codec at certain rates. Therefore, provisions
   have been made in this draft to facilitate and simplify data packet
   exchange between VMR-WB and AMR-WB in the interoperable mode with no
   transcoding function involved.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-vmr-wb-07.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-vmr-wb-07.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-vmr-wb-07.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: <2004-12-16162600.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-vmr-wb-07.txt

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

Content-Type: text/plain
Content-ID: <2004-12-16162600.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org  Fri Dec 17 15:40:48 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01802
	for <avt-archive@ietf.org>; Fri, 17 Dec 2004 15:40:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CfP2r-0002RO-J0
	for avt-archive@ietf.org; Fri, 17 Dec 2004 15:49:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfOno-000757-Ak; Fri, 17 Dec 2004 15:34:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfOkA-0004Bb-FQ; Fri, 17 Dec 2004 15:30:30 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00516;
	Fri, 17 Dec 2004 15:30:28 -0500 (EST)
Message-Id: <200412172030.PAA00516@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 17 Dec 2004 15:30:28 -0500
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-amrwbplus-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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87

--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		: Real-Time Transport Protocol (RTP) Payload Format 
			  for Extended AMR Wideband (AMR-WB+) Audio Codec
	Author(s)	: J. Sjoberg, et al.
	Filename	: draft-ietf-avt-rtp-amrwbplus-04.txt
	Pages		: 35
	Date		: 2004-12-17
	
This document specifies a real-time transport protocol (RTP) payload
    format to be used for Extended AMR Wideband (AMR-WB+) encoded audio
    signals.  The AMR-WB+ codec is an audio extension of the AMR-WB
    codec providing additional frame types designed to give higher
    quality of music and speech than the original frame types.  A media
    type registration is included for AMR-WB+.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-amrwbplus-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-rtp-amrwbplus-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-rtp-amrwbplus-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: <2004-12-17151606.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-amrwbplus-04.txt

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

Content-Type: text/plain
Content-ID: <2004-12-17151606.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org  Fri Dec 17 17:45:47 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22986
	for <avt-archive@ietf.org>; Fri, 17 Dec 2004 17:45:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CfQzR-0001dj-I9
	for avt-archive@ietf.org; Fri, 17 Dec 2004 17:54:50 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfQWD-0000rc-Jv; Fri, 17 Dec 2004 17:24:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfQRz-0007AP-BN
	for avt@megatron.ietf.org; Fri, 17 Dec 2004 17:19:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19396
	for <avt@ietf.org>; Fri, 17 Dec 2004 17:19:49 -0500 (EST)
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfQae-0000MU-0D
	for avt@ietf.org; Fri, 17 Dec 2004 17:28:52 -0500
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id
	iBHMJChP010812
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 17 Dec 2004 14:19:13 -0800 (PST)
Received: from HGARUDAD.qualcomm.com (hgarudad.qualcomm.com [129.46.75.112])
	by magus.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id iBHMJAIj009934;
	Fri, 17 Dec 2004 14:19:10 -0800 (PST)
Message-Id: <6.0.0.20.2.20041217132929.04dc03d0@qcmail1.qualcomm.com>
X-Sender: hgarudad@qcmail1.qualcomm.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.20 (Beta)
Date: Fri, 17 Dec 2004 14:19:04 -0800
To: <avt@ietf.org>, "TSG-C Working Group 1" <tsgcwg1@3gpp2.org>
From: Harinath Garudadri <hgarudad@qualcomm.com>
Subject: [AVT] Updated 3GPP2 MIME ID:
  draft-garudadri-avt-3gpp2-mime-01.txt
Mime-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
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="===============1148786058=="
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be

--===============1148786058==
Content-Type: multipart/alternative;
	boundary="=====================_172638861==.ALT"

--=====================_172638861==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

Hello All,

An updated version of the ID registering 3gpp2 MIME types is now available 
at 
http://www.ietf.org/internet-drafts/draft-garudadri-avt-3gpp2-mime-01.txt. 
This version uses the correct template and incorporates some editorial 
changes. It is based on RFC 3839 -

MIME Type Registrations for 3rd Generation Partnership Project (3GPP) 
Multimedia files.

Filename: draft-garudadri-avt-3gpp2-mime-01.txt
Date:     December, 2004
Pages:    8
Editor:   H. Garudadri

Abstract:
     This document serves to register and document the standard MIME types
     associated with the 3GPP2 multimedia file format, which is part of the
     family based on the ISO Media File Format.

Thanks,
hari


Dr. Hari Garudadri
Qualcomm Inc.
work    : +1 858 651 6383
mobile : +1 858 229 2801

--=====================_172638861==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
<font size=3>Hello All,<br><br>
An updated version of the ID registering 3gpp2 MIME types is now
available at
</font><a href="http://www.ietf.org/internet-drafts/draft-garudadri-avt-3gpp2-mime-01.txt" eudora="autourl">http://www.ietf.org/internet-drafts/draft-garudadri-avt-3gpp2-mime-01.txt</a><font size=3>.
This version uses the correct template and incorporates some editorial
changes. It is based on </font><pre>RFC 383<font size=3>9 -
</font></pre><h3>MIME Type Registrations for 3rd Generation Partnership
Project (3GPP) Multimedia files. </h3><font size=3>Filename:
draft-garudadri-avt-3gpp2-mime-01.txt<br>
Date:&nbsp;&nbsp;&nbsp;&nbsp; December, 2004<br>
Pages:&nbsp;&nbsp;&nbsp; 8<br>
Editor:&nbsp;&nbsp; H. Garudadri<br><br>
Abstract:<br>
</font><font size=2>&nbsp;&nbsp;&nbsp; This document serves to register
and document the standard MIME types<br>
&nbsp;&nbsp;&nbsp; associated with the 3GPP2 multimedia file format,
which is part of the<br>
&nbsp;&nbsp;&nbsp; family based on the ISO Media File Format.<br><br>
</font><font size=3>Thanks,<br>
hari<br><br>
</font><x-sigsep><p></x-sigsep>
Dr. Hari Garudadri<br>
Qualcomm Inc.<br>
work&nbsp;&nbsp;&nbsp; : +1 858 651 6383 <br>
mobile : +1 858 229 2801<br>
</body>
</html>

--=====================_172638861==.ALT--



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

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

--===============1148786058==--




From avt-bounces@ietf.org  Sat Dec 18 08:20:23 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16661
	for <avt-archive@ietf.org>; Sat, 18 Dec 2004 08:20:23 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CfeeL-0002Pg-NR
	for avt-archive@ietf.org; Sat, 18 Dec 2004 08:29:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfeTW-0003mA-Jv; Sat, 18 Dec 2004 08:18:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfeSr-0003ZA-Nd
	for avt@megatron.ietf.org; Sat, 18 Dec 2004 08:17:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16480
	for <avt@ietf.org>; Sat, 18 Dec 2004 08:17:40 -0500 (EST)
Received: from web8406.mail.in.yahoo.com ([202.43.219.154])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Cfebh-0002KV-Bj
	for avt@ietf.org; Sat, 18 Dec 2004 08:26:50 -0500
Received: (qmail 28625 invoked by uid 60001); 18 Dec 2004 13:17:08 -0000
Message-ID: <20041218131707.28620.qmail@web8406.mail.in.yahoo.com>
Received: from [203.129.220.115] by web8406.mail.in.yahoo.com via HTTP;
	Sat, 18 Dec 2004 13:17:07 GMT
Date: Sat, 18 Dec 2004 13:17:07 +0000 (GMT)
From: rahul agrawal <voipthesis@yahoo.co.in>
To: avt@ietf.org
MIME-Version: 1.0
X-Spam-Score: 1.8 (+)
X-Scan-Signature: c54bc2f42d02429833c0ca4b8725abd7
Subject: [AVT] need help @sourcecodec(iLBC)
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="===============0657983939=="
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1

--===============0657983939==
Content-Type: multipart/alternative; boundary="0-946178371-1103375827=:28272"

--0-946178371-1103375827=:28272
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Please, help me.
                         i  get source codec (iLBC) from IETE site, but when i go to run it then some problem occur. it having many modules, so pls tell me that how should i run it, give me method to run this program.
 
 
one more query is that how coeffiecients vary in CELP, that is what is main criteria to change reflection coeffiecients of code book .
 
 
rahul agrawal
M.Tech (ELECTRONICS)


avt-request@ietf.org wrote:
Send avt mailing list submissions to
avt@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
https://www1.ietf.org/mailman/listinfo/avt
or, via email, send a message with subject or body 'help' to
avt-request@ietf.org

You can reach the person managing the list at
avt-owner@ietf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of avt digest..."


Today's Topics:

1. I-D ACTION:draft-ietf-avt-rtp-vmr-wb-07.txt
(Internet-Drafts@ietf.org)


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

Message: 1
Date: Thu, 16 Dec 2004 15:54:48 -0500
From: Internet-Drafts@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-vmr-wb-07.txt
To: i-d-announce@ietf.org
Cc: avt@ietf.org
Message-ID: <200412162054.PAA08071@ietf.org>
Content-Type: text/plain; charset="us-ascii"

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 : Real-Time Transport Protocol (RTP) Payload Formats for 
the Variable-Rate Multimode Wideband (VMR-WB) Audio Codec
Author(s) : S. Ahmadi
Filename : draft-ietf-avt-rtp-vmr-wb-07.txt
Pages : 29
Date : 2004-12-16

This document specifies a real-time transport protocol (RTP) payload
format to be used for the Variable-Rate Multimode Wideband (VMR-WB)
speech codec. The payload format is designed to be able to
interoperate with existing VMR-WB transport formats on non-IP
networks. A MIME type registration is included for VMR-WB RTP 
payload formats.

VMR-WB is a variable-rate multimode wideband speech codec that has a
number of operating modes, one of which is interoperable with AMR-WB
(i.e., RFC 3267) audio codec at certain rates. Therefore, provisions
have been made in this draft to facilitate and simplify data packet
exchange between VMR-WB and AMR-WB in the interoperable mode with no
transcoding function involved.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-vmr-wb-07.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-vmr-wb-07.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-vmr-wb-07.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.
-------------- next part --------------
Skipped content of type multipart/alternative

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

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


End of avt Digest, Vol 8, Issue 21
**********************************


Yahoo! India Matrimony: Find your life partneronline.
--0-946178371-1103375827=:28272
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<DIV>
<DIV>Please, help me.</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; i&nbsp; get source codec (iLBC)&nbsp;from IETE site, but when i go to run it then some problem occur. it having many modules, so pls tell me that how should i run it, give me method to run this program.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>one more query is that how coeffiecients vary in CELP,&nbsp;that is what is main criteria to change reflection coeffiecients of code book .</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>rahul agrawal</DIV>
<DIV>M.Tech (ELECTRONICS)<BR><BR><BR><B><I>avt-request@ietf.org</I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Send avt mailing list submissions to<BR>avt@ietf.org<BR><BR>To subscribe or unsubscribe via the World Wide Web, visit<BR>https://www1.ietf.org/mailman/listinfo/avt<BR>or, via email, send a message with subject or body 'help' to<BR>avt-request@ietf.org<BR><BR>You can reach the person managing the list at<BR>avt-owner@ietf.org<BR><BR>When replying, please edit your Subject line so it is more specific<BR>than "Re: Contents of avt digest..."<BR><BR><BR>Today's Topics:<BR><BR>1. I-D ACTION:draft-ietf-avt-rtp-vmr-wb-07.txt<BR>(Internet-Drafts@ietf.org)<BR><BR><BR>----------------------------------------------------------------------<BR><BR>Message: 1<BR>Date: Thu, 16 Dec 2004 15:54:48 -0500<BR>From: Internet-Drafts@ietf.org<BR>Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-vmr-wb-07.txt<BR>To: i-d-announce@ietf.org<BR>Cc: avt@ietf.org<BR>Message-ID:
 &lt;200412162054.PAA08071@ietf.org&gt;<BR>Content-Type: text/plain; charset="us-ascii"<BR><BR>A New Internet-Draft is available from the on-line Internet-Drafts directories.<BR>This draft is a work item of the Audio/Video Transport Working Group of the IETF.<BR><BR>Title : Real-Time Transport Protocol (RTP) Payload Formats for <BR>the Variable-Rate Multimode Wideband (VMR-WB) Audio Codec<BR>Author(s) : S. Ahmadi<BR>Filename : draft-ietf-avt-rtp-vmr-wb-07.txt<BR>Pages : 29<BR>Date : 2004-12-16<BR><BR>This document specifies a real-time transport protocol (RTP) payload<BR>format to be used for the Variable-Rate Multimode Wideband (VMR-WB)<BR>speech codec. The payload format is designed to be able to<BR>interoperate with existing VMR-WB transport formats on non-IP<BR>networks. A MIME type registration is included for VMR-WB RTP <BR>payload formats.<BR><BR>VMR-WB is a variable-rate multimode wideband speech codec that has a<BR>number of operating modes, one of which is interope!
 rable
 with AMR-WB<BR>(i.e., RFC 3267) audio codec at certain rates. Therefore, provisions<BR>have been made in this draft to facilitate and simplify data packet<BR>exchange between VMR-WB and AMR-WB in the interoperable mode with no<BR>transcoding function involved.<BR><BR>A URL for this Internet-Draft is:<BR>http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-vmr-wb-07.txt<BR><BR>To remove yourself from the I-D Announcement list, send a message to <BR>i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. <BR>You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce <BR>to change your subscription settings.<BR><BR><BR>Internet-Drafts are also available by anonymous FTP. Login with the username<BR>"anonymous" and a password of your e-mail address. After logging in,<BR>type "cd internet-drafts" and then<BR>"get draft-ietf-avt-rtp-vmr-wb-07.txt".<BR><BR>A list of Internet-Drafts directories can be found in<BR>http://www.ietf.org/shadow.h!
 tml
 <BR>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt<BR><BR><BR>Internet-Drafts can also be obtained by e-mail.<BR><BR>Send a message to:<BR>mailserv@ietf.org.<BR>In the body type:<BR>"FILE /internet-drafts/draft-ietf-avt-rtp-vmr-wb-07.txt".<BR><BR>NOTE: The mail server at ietf.org can return the document in<BR>MIME-encoded form by using the "mpack" utility. To use this<BR>feature, insert the command "ENCODING mime" before the "FILE"<BR>command. To decode the response(s), you will need "munpack" or<BR>a MIME-compliant mail reader. Different MIME-compliant mail readers<BR>exhibit different behavior, especially when dealing with<BR>"multipart" MIME messages (i.e. documents which have been split<BR>up into multiple messages), so check your local documentation on<BR>how to manipulate these messages.<BR><BR><BR>Below is the data which will enable a MIME compliant mail reader<BR>implementation to automatically retrieve the ASCII version of the<BR>Internet-Draft.<BR>-------------- nex!
 t part
 --------------<BR>Skipped content of type multipart/alternative<BR><BR>------------------------------<BR><BR>_______________________________________________<BR>Audio/Video Transport Working Group<BR>avt@ietf.org<BR>https://www1.ietf.org/mailman/listinfo/avt<BR><BR><BR>End of avt Digest, Vol 8, Issue 21<BR>**********************************<BR></BLOCKQUOTE></DIV><p><font face=arial size=-1>
<a href="http://in.rd.yahoo.com/specials/mailtg/*http://yahoo.shaadi.com/india-matrimony/" target="_blank">
<b>Yahoo! India Matrimony</a>:</b> Find your life partner
<a href="http://in.rd.yahoo.com/specials/mailtg2/*http://yahoo.shaadi.com/india-matrimony/" target="_blank">online</a>.</font>
--0-946178371-1103375827=:28272--


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

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

--===============0657983939==--



From avt-bounces@ietf.org  Sat Dec 18 09:24:47 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20792
	for <avt-archive@ietf.org>; Sat, 18 Dec 2004 09:24:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cffee-000455-Cr
	for avt-archive@ietf.org; Sat, 18 Dec 2004 09:33:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CffUY-0005mD-Fj; Sat, 18 Dec 2004 09:23:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfHAj-00074t-Eq
	for avt@megatron.ietf.org; Fri, 17 Dec 2004 07:25:26 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11124
	for <avt@ietf.org>; Fri, 17 Dec 2004 07:25:24 -0500 (EST)
Received: from web8401.mail.in.yahoo.com ([202.43.219.149])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CfHJJ-0002QQ-DO
	for avt@ietf.org; Fri, 17 Dec 2004 07:34:20 -0500
Received: (qmail 50668 invoked by uid 60001); 17 Dec 2004 12:24:48 -0000
Message-ID: <20041217122448.50666.qmail@web8401.mail.in.yahoo.com>
Received: from [203.129.220.115] by web8401.mail.in.yahoo.com via HTTP;
	Fri, 17 Dec 2004 12:24:48 GMT
Date: Fri, 17 Dec 2004 12:24:48 +0000 (GMT)
From: rahul agrawal <voipthesis@yahoo.co.in>
To: avt@ietf.org
MIME-Version: 1.0
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 559439f19b20fd64c5cd872aef84c6f3
X-Mailman-Approved-At: Sat, 18 Dec 2004 09:23:29 -0500
Subject: [AVT] help about source codec(iLBC)
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="===============0411212725=="
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 3b3673afe71d94a7551c8fbc5adb8948

--===============0411212725==
Content-Type: multipart/alternative; boundary="0-1893106423-1103286288=:50649"

--0-1893106423-1103286288=:50649
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Please, help me.
                         i  get source codec (iLBC) from IETE site, but when i go to run it then some problem occur. it having many modules, so pls tell me that how should i run it, give me method to run this program.
 
 
one more query is that how coeffiecients vary in CELP, that is what is main criteria to change reflection coeffiecients of code book .
 
 
rahul agrawal
M.Tech (ELECTRONICS)

avt-request@ietf.org wrote:
Send avt mailing list submissions to
avt@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
https://www1.ietf.org/mailman/listinfo/avt
or, via email, send a message with subject or body 'help' to
avt-request@ietf.org

You can reach the person managing the list at
avt-owner@ietf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of avt digest..."


Today's Topics:

1. Re: draft-ietf-avt-rtp-amr-bis-00.txt (Gorry Fairhurst)
2. RE: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps
(Phelan, Tom)
3. Re: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps
(Colin Perkins)
4. I-D ACTION:draft-ietf-avt-rtp-amrwbplus-03.txt
(Internet-Drafts@ietf.org)
5. I-D ACTION:draft-ietf-avt-rtp-bv-02.txt (Internet-Drafts@ietf.org)
6. RE: Re: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps
(Ernesto Exposito)


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

Message: 1
Date: Thu, 09 Dec 2004 16:50:38 +0000
From: Gorry Fairhurst 
Subject: Re: [AVT] draft-ietf-avt-rtp-amr-bis-00.txt
To: Magnus Westerlund 
Cc: "Johan Sj ? berg \(KI/EAB\)" ,
avt@ietf.org
Message-ID: 
Content-Type: text/plain; charset="US-ASCII"

I've numbered the issues, to try to help us quickly agree on what the
problem is/was.

On 9/12/04 10:18 am, "Magnus Westerlund" 
wrote:

> Hi Gorry,
> 
> I hope that you are aware that this draft is an update of RFC 3267,
> which mainly intends to fixes the lack of an offer-answer section.

Yes - and it seems a good application for UDP-Lite, which was what
interested me.

> However if we conclude that any of these normative text is wrong we
> should definitely consider changing it. But any backwards compatibility
> issues must be considered. The payload format is rather well deployed,
> however I think the CRC mode is very seldom or may be not at all used.
> Both the robust sorting and the CRC mode are specifically designed for
> UDP-Lite type of partial checksums.
> 
> I would also note that this format was finished long before UDP-Lite was
> approved and went through the last round of changes.

Yes - and if so, then it explains the differences.

On looking through your response, I wonder how much of my response is due to
there being two types of "frames" link-frame and payload-codec-frames, each
with their own CRC's. Normally I'd not expect RTP documents to mention link
frames, but use of UDP-Lite naturally leads to comments on link frames. If
this differentiation can be clearer, then the issues can be localised to
section 3.6.1 (which seems perhaps to be the correct place to discuss IP,
Link and UDP-Lite).

> See further below.
> 
> Gorry Fairhurst wrote:
>> 
>> I've just been doing a little reading of drafts from other WGs and had some
>> questions about the design rationale of the above ID:
>> 
>> 
>> I notice that in section 4.4.2.1, it says:
>> 
>> "The frame CRC, when used, MUST be calculated only over all class A
>> bits in the frame. Class B and C bits in the frame MUST NOT be
>> included in the CRC calculation and SHOULD NOT be covered by the
>> transport checksum."
>> 
>> I wonder if this could be justified?
>> 
>> At first read, this seems to go exactly the opposite way to what was
>> written
>> in UDP-Lite [RFC3828], section 4.
>> 
>> ...."For a link that supports
>> partial error detection, the Checksum Coverage field in the UDP-Lite
>> header MAY be used as a hint of where errors do not need to be
>> detected. Lower layers MUST use a strong error detection mechanism
>> [RFC-3819] to detect at least errors that occur in the sensitive part
>> of the packet, and discard damaged packets."
>> 
>> So my take on this was, UDP-Lite says you MUST perform a check on the IP
>> headers, and any fields covered by the Checksum coverage, but that you MAY
>> relax this to only cover the Checksum coverage for UDP-Lite frames. If
>> we're
>> changing the recommendation, then this introduces new issues that really
>> need
>> to be discussed.
>> 
> 
> I don't the text in section 4.4.2.1 that you quote is contradicting
> UDP-Lite at all.

OK - if that's the case, we can agree.

1) There's a subtle difference between what is expected Link behaviour as
described by UDP-Lite, and what this ID seems to suggest at the moment. This
lies in whether the Link-Layer does full frame protection; unequal
protection; or NO protection.

Experience with SLIP, etc, showed that NO protection of IP and transport
headers was bad - I would expect the concerns to be greater with IPv6 (where
there is no IP checksum), cite RFC3819 on use of link CRCs?

One thing I'd propose is to recommend a mode were all protocol headers up to
and including the class A bits in the frame are protected by a link-frame
CRC; you could cite UDP-Lite as clarification?

Would this impact any known usage? - Or is it only a clarification?

Of course, it is in practice hard for the IETF to mandate use of partial
(unequal) CRC protection at the link layer, never-the-less in my opinion, it
would be very wrong to encourage use of links with NO protection for IP.


2) Looking back, the current text in 3.6.1 seems to have a focus on RTP
issues (it is an AVT draft), but also touches on the implications for IP
networks. Perhaps a little more clarity here would prevent confusion (at
least for me). 

Suggestions are: Be clear which types of frame is being mentioned. It would
be good to mention the network and transport (i.e. UDP/UDP-Lite) headers
explicitly in your discussion. For example:

" 1) Utilizing a partial checksum to cover headers and the most
important speech bits of the payload."

Could become:
" 1) Utilizing a partial checksum to cover protocol headers (i.e., IP
network headers, UDP/UDP-Lite transport headers; RTP headers; and RTP
payload headers) together with the most important speech bits of the
payload."

Etc.

Is this what was meant?


> The CRC mode is specifically designed for partial
> checksums from the beginning. The bits in a AMR audio frame is sorted in
> sensitivity order, with the most sensitive bits first and the least
> last. This is utilized in circuit switched channel coding to provide
> three levels of protection A, which are so sensitive that any errors
> results in those bits not being used. A class B that has less protection
> but still needs lower bit-error rates than the class C bits that use the
> channel as is. The channel error rates are of course tuned to what the
> codec can accept in both bit-errors and frame erasures. Also if the
> class A bits are damaged as detected by the CRC (present also in the CS
> transport) some of the class B and C bits are used.
> 
This was what I thought, so that is good.

> Due to this characteristics of the codec, the CRC was included to
> provide maximum performance for RTP payload with multiple AMR frames.
> The per frame CRC allows the complete section of data frames to be
> unprotected by UDP-Lite. Bit-errors in the sensitive class A bits are
> detected by the CRC, and in that case the frame is marked as damaged and
> some of the B and C bits for that frame are used in concealment.
> 
Yes.
> The intention of the CRC mode compared to Robust sorting was to reduce
> the part that needs strong protection when aggregating multiple frames
> into a packet compared to the Robust Sorting mode. In the robust sorting
> mode, the complete payload data part is sorted byte-wise into decreasing
> order of sensitivity to bit-errors. In Robust sorting mode the intention
> is to cover the class A bits with the UDP-Lite checksum instead.
> 
> In conclusion I think this can be motivated.
> 
This sounds like the correct thing to do.
> 
>> Later, the ID also says:
>> 
>> "Packets SHOULD be discarded if the transport layer checksum detects
>> errors."
>> 
>> - Is there any justification why that is not a MUST be discarded, since the
>> check indicates the header IS mangled, and therefore there is little
>> confidence in using the packet header? Again it seems the opposite to
>> envisaged with UDP-Lite. Where UDP-Lite says, section 6:
>> 
>> ..."Corruption of any bit within
>> the protected area will then result in the IP receiver discarding the
>> UDP-Lite packet."
>> 
>> I'm not sure if this was a mistake or a design strategy. Can you tell me?
>> 
> 
> I am not certain why it says SHOULD rather than MUST. It was probably a
> case of given a little to much freedom to the implementors. In fact
> there are basically no fields where a bit-error could be present without
> resulting in serious problems for the playing application. Some
> bit-errors would result in inconsistent payload forcing one to discard
> it anyway. Others would result in misinterpretation of the result. For
> example a timestamp error would place the frame wrongly in time, which I
> consider quite serious. The backwards compatibility issues with changing
> this seem to be almost non-existent. If someone actually has taken on
> all the hassle to make an implementation that accept UDP-Lite packets
> with failed checksum and handles it correctly, fine they can keep it
> without affecting some else. The effect of the change would also only
> give the implementors a clearer implementation statement.
> 

3) Looking at the ID, I think the problem I had actually was in section 3.6
which speaks (I think) about Link-layer frames. If this was to be made
clear, then this section could refer back to it (and remove the potential
for confusion).

" The frame CRC, when used, MUST be calculated only over all class A
bits in the frame."

- Which "frame" is this about? - I think this is the payload-codec-frame of
RTP?

4) A correct UDP-Lite implementation MUST discard these packets (this is
also the way DCCP is expected to behave when using partial checksum
coverage). Of course AMR can also be used over non-IP transports, and then
you rely on their multiplexing and control functions to supply the bit
stream that AMR uses.

The rationale for IP transport was that allowing these packets to pass up
the stack with no verification of the IP header (in IPv6) or UDP-Lite header
(IPv4,IPv6), could result in cases of mis-delivery of arbitary corrupted
packets to *any* port, and applications do not generally have an ability to
handle such events robustly (with serious implications). So, unless there is
a strong argument, I'd recommend that if you use an IP network, you MUST use
a transport layer checksum.

> A better proposal may be to rewrite that sentence to simple note that
> any packets with errors detected by the UDP-Lite checksum or lower layer
> in that part will be discarded and never delivered.
> 

Exactly:-)

> Please provide more feedback if such a change is appropriate.
> 
> 
> Cheers
> 
> 
> Magnus Westerlund
> 
> 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
> 

I'm relieved we were closer than I thought... Are there still points of
disagreement?

Gorry





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

Message: 2
Date: Thu, 9 Dec 2004 13:41:11 -0500
From: "Phelan, Tom" 
Subject: [AVT] RE: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps
To: "Alejandro Cabrera Obed" , "AVT Lista"
, "DCCP Lista" 
Message-ID:

Content-Type: text/plain; charset="iso-8859-1"

Hi Alejandro,

See inline ...

Tom Phelan

> -----Original Message-----
> From: Alejandro Cabrera Obed [mailto:aco1967@gmail.com]
> Sent: Thursday, December 09, 2004 11:43 AM
> To: AVT Lista; DCCP Lista
> Subject: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps
> 
> 
> Dear people,
> 
> I'm from Argentina, developing a survey about HDTV uncompressed live
> streaming over IP. I'm contacting you in order to know what you think
> about applying TFRC to HDTV uncompressed live streaming (aprox. 1.5
> Gbps), in order to get congestion control.
> 
> 1) Do you think there is any limitation in applying the TFRC mechanism
> to my scenario ???

I think there's two issues you'll need to deal with. One is slow start - it'll take a good number of round trip times to get up to 1.5G bps. The other is, what will you do when there is congestion and you must reduce the transmit rate? I assume you'll be using large packets to get that high a transmit rate, so the small packet issues shown in http://www.phelan-4.com/dccp/tfrc-self-limit.pdf won't be a problem.

> 2) Is it correct the use of RTCP like a feedback mechanism for TFRC,
> taking the RTCP throughput at about 5% of 1.5 Gbps ???

Normally TFRC requires one feedback packet per RTT. So the RTCP 5% limit is a bit problematic. The feedback is greater or less than 5% depending on the RTT. I know this has been raised as a problem the RTP profile for TFRC - I'm not sure how Ladan has dealt with it. For DCCP, there's no such restriction. The DCCP feedback packets are fairly small - I don't remember the exact size, but using 40 bytes, you'd need an RTT of less than 5 microseconds to use up 5% of 1.5G on the feedback.

> 
> Maybe, if TRFC is OK to HDTV uncompressed, I'm interesting in studying
> into account the use of LSR and DLSR fields of RR in order to
> calculate the RTT.
> 
> Thanks a lot, I appreciate your opinion.
> 
> 
> Alejandro Cabrera Obed
> 
> _______________________________________________
> dccp IETF mailing list: dccp@ietf.org
> list info: https://www1.ietf.org/mailman/listinfo/dccp
> wg charter: http://www.ietf.org/html.charters/dccp-charter.html
> 



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

Message: 3
Date: Thu, 9 Dec 2004 19:16:22 +0000
From: Colin Perkins 
Subject: [AVT] Re: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps
To: "Phelan, Tom" 
Cc: DCCP Lista , AVT Lista 
Message-ID: 
Content-Type: text/plain; charset=US-ASCII; format=flowed

You would also have the issue of how to maintain acceptable viewing 
quality whilst varying the transmission rate. That problem is at least 
as difficult as the practicalities of making the TFRC mechanisms work 
(and note that you must either compress or discard data to do this in 
real-time, so using TFRC for "uncompressed" HDTV isn't practical if 
there might be congestion).

Colin



On 9 Dec 2004, at 18:41, Phelan, Tom wrote:

> Hi Alejandro,
>
> See inline ...
>
> Tom Phelan
>
>> -----Original Message-----
>> From: Alejandro Cabrera Obed [mailto:aco1967@gmail.com]
>> Sent: Thursday, December 09, 2004 11:43 AM
>> To: AVT Lista; DCCP Lista
>> Subject: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps
>>
>>
>> Dear people,
>>
>> I'm from Argentina, developing a survey about HDTV uncompressed live
>> streaming over IP. I'm contacting you in order to know what you think
>> about applying TFRC to HDTV uncompressed live streaming (aprox. 1.5
>> Gbps), in order to get congestion control.
>>
>> 1) Do you think there is any limitation in applying the TFRC mechanism
>> to my scenario ???
>
> I think there's two issues you'll need to deal with. One is slow 
> start - it'll take a good number of round trip times to get up to 1.5G 
> bps. The other is, what will you do when there is congestion and you 
> must reduce the transmit rate? I assume you'll be using large packets 
> to get that high a transmit rate, so the small packet issues shown in 
> http://www.phelan-4.com/dccp/tfrc-self-limit.pdf won't be a problem.
>
>> 2) Is it correct the use of RTCP like a feedback mechanism for TFRC,
>> taking the RTCP throughput at about 5% of 1.5 Gbps ???
>
> Normally TFRC requires one feedback packet per RTT. So the RTCP 5% 
> limit is a bit problematic. The feedback is greater or less than 5% 
> depending on the RTT. I know this has been raised as a problem the 
> RTP profile for TFRC - I'm not sure how Ladan has dealt with it. For 
> DCCP, there's no such restriction. The DCCP feedback packets are 
> fairly small - I don't remember the exact size, but using 40 bytes, 
> you'd need an RTT of less than 5 microseconds to use up 5% of 1.5G on 
> the feedback.
>
>>
>> Maybe, if TRFC is OK to HDTV uncompressed, I'm interesting in studying
>> into account the use of LSR and DLSR fields of RR in order to
>> calculate the RTT.
>>
>> Thanks a lot, I appreciate your opinion.
>>
>>
>> Alejandro Cabrera Obed
>>
>> _______________________________________________
>> dccp IETF mailing list: dccp@ietf.org
>> list info: https://www1.ietf.org/mailman/listinfo/dccp
>> wg charter: http://www.ietf.org/html.charters/dccp-charter.html




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

Message: 4
Date: Thu, 09 Dec 2004 15:43:57 -0500
From: Internet-Drafts@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-amrwbplus-03.txt
To: i-d-announce@ietf.org
Cc: avt@ietf.org
Message-ID: <200412092043.PAA02399@ietf.org>
Content-Type: text/plain; charset="us-ascii"

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 : Real-Time Transport Protocol (RTP) Payload Format for 
Extended AMR Wideband (AMR-WB+) Audio Codec
Author(s) : J. Sjoberg, et al.
Filename : draft-ietf-avt-rtp-amrwbplus-03.txt
Pages : 35
Date : 2004-12-9

This document specifies a real-time transport protocol (RTP) payload
format to be used for Extended AMR Wideband (AMR-WB+) encoded audio
signals. The AMR-WB+ codec is an audio extension of the AMR-WB codec
providing additional modes designed to give higher quality of music
and speech than the original modes. A MIME type registration is
included for AMR-WB+.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-amrwbplus-03.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-amrwbplus-03.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-amrwbplus-03.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.
-------------- next part --------------
Skipped content of type multipart/alternative

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

Message: 5
Date: Thu, 09 Dec 2004 15:44:02 -0500
From: Internet-Drafts@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-bv-02.txt
To: i-d-announce@ietf.org
Cc: avt@ietf.org
Message-ID: <200412092044.PAA02408@ietf.org>
Content-Type: text/plain; charset="us-ascii"

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

Title : RTP Payload and Storage Format for BroadVoice Speech Codecs

=== message truncated ===
		
---------------------------------
Do you Yahoo!?
 Yahoo! Mail - 250MB free storage. Do more. Manage less.
--0-1893106423-1103286288=:50649
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<DIV>Please, help me.</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; i&nbsp; get source codec (iLBC)&nbsp;from IETE site, but when i go to run it then some problem occur. it having many modules, so pls tell me that how should i run it, give me method to run this program.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>one more query is that how coeffiecients vary in CELP,&nbsp;that is what is main criteria to change reflection coeffiecients of code book .</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>rahul agrawal</DIV>
<DIV>M.Tech (ELECTRONICS)<BR><BR><B><I>avt-request@ietf.org</I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Send avt mailing list submissions to<BR>avt@ietf.org<BR><BR>To subscribe or unsubscribe via the World Wide Web, visit<BR>https://www1.ietf.org/mailman/listinfo/avt<BR>or, via email, send a message with subject or body 'help' to<BR>avt-request@ietf.org<BR><BR>You can reach the person managing the list at<BR>avt-owner@ietf.org<BR><BR>When replying, please edit your Subject line so it is more specific<BR>than "Re: Contents of avt digest..."<BR><BR><BR>Today's Topics:<BR><BR>1. Re: draft-ietf-avt-rtp-amr-bis-00.txt (Gorry Fairhurst)<BR>2. RE: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps<BR>(Phelan, Tom)<BR>3. Re: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps<BR>(Colin Perkins)<BR>4. I-D ACTION:draft-ietf-avt-rtp-amrwbplus-03.txt<BR>(Internet-Drafts@ietf.org)<BR>5. I-D ACTION:draft-ietf-avt-rtp-bv-02.txt (Internet-Drafts@ietf.org)<BR>6. RE: Re: [dccp] TFRC applied to HDTV
 uncompressed 1.5 Gbps<BR>(Ernesto Exposito)<BR><BR><BR>----------------------------------------------------------------------<BR><BR>Message: 1<BR>Date: Thu, 09 Dec 2004 16:50:38 +0000<BR>From: Gorry Fairhurst <GORRY@ERG.ABDN.AC.UK><BR>Subject: Re: [AVT] draft-ietf-avt-rtp-amr-bis-00.txt<BR>To: Magnus Westerlund <MAGNUS.WESTERLUND@ERICSSON.COM><BR>Cc: "Johan Sj ? berg \(KI/EAB\)" <JOHAN.SJOBERG@ERICSSON.COM>,<BR>avt@ietf.org<BR>Message-ID: <BDDE32DE.1ADC%GORRY@ERG.ABDN.AC.UK><BR>Content-Type: text/plain; charset="US-ASCII"<BR><BR>I've numbered the issues, to try to help us quickly agree on what the<BR>problem is/was.<BR><BR>On 9/12/04 10:18 am, "Magnus Westerlund" <MAGNUS.WESTERLUND@ERICSSON.COM><BR>wrote:<BR><BR>&gt; Hi Gorry,<BR>&gt; <BR>&gt; I hope that you are aware that this draft is an update of RFC 3267,<BR>&gt; which mainly intends to fixes the lack of an offer-answer section.<BR><BR>Yes - and it seems a good application for UDP-Lite, which was what<BR>interested
 me.<BR><BR>&gt; However if we conclude that any of these normative text is wrong we<BR>&gt; should definitely consider changing it. But any backwards compatibility<BR>&gt; issues must be considered. The payload format is rather well deployed,<BR>&gt; however I think the CRC mode is very seldom or may be not at all used.<BR>&gt; Both the robust sorting and the CRC mode are specifically designed for<BR>&gt; UDP-Lite type of partial checksums.<BR>&gt; <BR>&gt; I would also note that this format was finished long before UDP-Lite was<BR>&gt; approved and went through the last round of changes.<BR><BR>Yes - and if so, then it explains the differences.<BR><BR>On looking through your response, I wonder how much of my response is due to<BR>there being two types of "frames" link-frame and payload-codec-frames, each<BR>with their own CRC's. Normally I'd not expect RTP documents to mention link<BR>frames, but use of UDP-Lite naturally leads to comments on link frames. If<BR>this differ!
 entiation
 can be clearer, then the issues can be localised to<BR>section 3.6.1 (which seems perhaps to be the correct place to discuss IP,<BR>Link and UDP-Lite).<BR><BR>&gt; See further below.<BR>&gt; <BR>&gt; Gorry Fairhurst wrote:<BR>&gt;&gt; <BR>&gt;&gt; I've just been doing a little reading of drafts from other WGs and had some<BR>&gt;&gt; questions about the design rationale of the above ID:<BR>&gt;&gt; <BR>&gt;&gt; <BR>&gt;&gt; I notice that in section 4.4.2.1, it says:<BR>&gt;&gt; <BR>&gt;&gt; "The frame CRC, when used, MUST be calculated only over all class A<BR>&gt;&gt; bits in the frame. Class B and C bits in the frame MUST NOT be<BR>&gt;&gt; included in the CRC calculation and SHOULD NOT be covered by the<BR>&gt;&gt; transport checksum."<BR>&gt;&gt; <BR>&gt;&gt; I wonder if this could be justified?<BR>&gt;&gt; <BR>&gt;&gt; At first read, this seems to go exactly the opposite way to what was<BR>&gt;&gt; written<BR>&gt;&gt; in UDP-Lite [RFC3828], section 4.<BR>&gt;&gt; <BR>&!
 gt;&gt;
 ...."For a link that supports<BR>&gt;&gt; partial error detection, the Checksum Coverage field in the UDP-Lite<BR>&gt;&gt; header MAY be used as a hint of where errors do not need to be<BR>&gt;&gt; detected. Lower layers MUST use a strong error detection mechanism<BR>&gt;&gt; [RFC-3819] to detect at least errors that occur in the sensitive part<BR>&gt;&gt; of the packet, and discard damaged packets."<BR>&gt;&gt; <BR>&gt;&gt; So my take on this was, UDP-Lite says you MUST perform a check on the IP<BR>&gt;&gt; headers, and any fields covered by the Checksum coverage, but that you MAY<BR>&gt;&gt; relax this to only cover the Checksum coverage for UDP-Lite frames. If<BR>&gt;&gt; we're<BR>&gt;&gt; changing the recommendation, then this introduces new issues that really<BR>&gt;&gt; need<BR>&gt;&gt; to be discussed.<BR>&gt;&gt; <BR>&gt; <BR>&gt; I don't the text in section 4.4.2.1 that you quote is contradicting<BR>&gt; UDP-Lite at all.<BR><BR>OK - if that's the case, we can
 agree.<BR><BR>1) There's a subtle difference between what is expected Link behaviour as<BR>described by UDP-Lite, and what this ID seems to suggest at the moment. This<BR>lies in whether the Link-Layer does full frame protection; unequal<BR>protection; or NO protection.<BR><BR>Experience with SLIP, etc, showed that NO protection of IP and transport<BR>headers was bad - I would expect the concerns to be greater with IPv6 (where<BR>there is no IP checksum), cite RFC3819 on use of link CRCs?<BR><BR>One thing I'd propose is to recommend a mode were all protocol headers up to<BR>and including the class A bits in the frame are protected by a link-frame<BR>CRC; you could cite UDP-Lite as clarification?<BR><BR>Would this impact any known usage? - Or is it only a clarification?<BR><BR>Of course, it is in practice hard for the IETF to mandate use of partial<BR>(unequal) CRC protection at the link layer, never-the-less in my opinion, it<BR>would be very wrong to encourage use of links!
  with NO
 protection for IP.<BR><BR><BR>2) Looking back, the current text in 3.6.1 seems to have a focus on RTP<BR>issues (it is an AVT draft), but also touches on the implications for IP<BR>networks. Perhaps a little more clarity here would prevent confusion (at<BR>least for me). <BR><BR>Suggestions are: Be clear which types of frame is being mentioned. It would<BR>be good to mention the network and transport (i.e. UDP/UDP-Lite) headers<BR>explicitly in your discussion. For example:<BR><BR>" 1) Utilizing a partial checksum to cover headers and the most<BR>important speech bits of the payload."<BR><BR>Could become:<BR>" 1) Utilizing a partial checksum to cover protocol headers (i.e., IP<BR>network headers, UDP/UDP-Lite transport headers; RTP headers; and RTP<BR>payload headers) together with the most important speech bits of the<BR>payload."<BR><BR>Etc.<BR><BR>Is this what was meant?<BR><BR><BR>&gt; The CRC mode is specifically designed for partial<BR>&gt; checksums from the beginnin!
 g. The
 bits in a AMR audio frame is sorted in<BR>&gt; sensitivity order, with the most sensitive bits first and the least<BR>&gt; last. This is utilized in circuit switched channel coding to provide<BR>&gt; three levels of protection A, which are so sensitive that any errors<BR>&gt; results in those bits not being used. A class B that has less protection<BR>&gt; but still needs lower bit-error rates than the class C bits that use the<BR>&gt; channel as is. The channel error rates are of course tuned to what the<BR>&gt; codec can accept in both bit-errors and frame erasures. Also if the<BR>&gt; class A bits are damaged as detected by the CRC (present also in the CS<BR>&gt; transport) some of the class B and C bits are used.<BR>&gt; <BR>This was what I thought, so that is good.<BR><BR>&gt; Due to this characteristics of the codec, the CRC was included to<BR>&gt; provide maximum performance for RTP payload with multiple AMR frames.<BR>&gt; The per frame CRC allows the complete sectio!
 n of data
 frames to be<BR>&gt; unprotected by UDP-Lite. Bit-errors in the sensitive class A bits are<BR>&gt; detected by the CRC, and in that case the frame is marked as damaged and<BR>&gt; some of the B and C bits for that frame are used in concealment.<BR>&gt; <BR>Yes.<BR>&gt; The intention of the CRC mode compared to Robust sorting was to reduce<BR>&gt; the part that needs strong protection when aggregating multiple frames<BR>&gt; into a packet compared to the Robust Sorting mode. In the robust sorting<BR>&gt; mode, the complete payload data part is sorted byte-wise into decreasing<BR>&gt; order of sensitivity to bit-errors. In Robust sorting mode the intention<BR>&gt; is to cover the class A bits with the UDP-Lite checksum instead.<BR>&gt; <BR>&gt; In conclusion I think this can be motivated.<BR>&gt; <BR>This sounds like the correct thing to do.<BR>&gt; <BR>&gt;&gt; Later, the ID also says:<BR>&gt;&gt; <BR>&gt;&gt; "Packets SHOULD be discarded if the transport layer checksum
 detects<BR>&gt;&gt; errors."<BR>&gt;&gt; <BR>&gt;&gt; - Is there any justification why that is not a MUST be discarded, since the<BR>&gt;&gt; check indicates the header IS mangled, and therefore there is little<BR>&gt;&gt; confidence in using the packet header? Again it seems the opposite to<BR>&gt;&gt; envisaged with UDP-Lite. Where UDP-Lite says, section 6:<BR>&gt;&gt; <BR>&gt;&gt; ..."Corruption of any bit within<BR>&gt;&gt; the protected area will then result in the IP receiver discarding the<BR>&gt;&gt; UDP-Lite packet."<BR>&gt;&gt; <BR>&gt;&gt; I'm not sure if this was a mistake or a design strategy. Can you tell me?<BR>&gt;&gt; <BR>&gt; <BR>&gt; I am not certain why it says SHOULD rather than MUST. It was probably a<BR>&gt; case of given a little to much freedom to the implementors. In fact<BR>&gt; there are basically no fields where a bit-error could be present without<BR>&gt; resulting in serious problems for the playing application. Some<BR>&gt; bit-errors would r!
 esult in
 inconsistent payload forcing one to discard<BR>&gt; it anyway. Others would result in misinterpretation of the result. For<BR>&gt; example a timestamp error would place the frame wrongly in time, which I<BR>&gt; consider quite serious. The backwards compatibility issues with changing<BR>&gt; this seem to be almost non-existent. If someone actually has taken on<BR>&gt; all the hassle to make an implementation that accept UDP-Lite packets<BR>&gt; with failed checksum and handles it correctly, fine they can keep it<BR>&gt; without affecting some else. The effect of the change would also only<BR>&gt; give the implementors a clearer implementation statement.<BR>&gt; <BR><BR>3) Looking at the ID, I think the problem I had actually was in section 3.6<BR>which speaks (I think) about Link-layer frames. If this was to be made<BR>clear, then this section could refer back to it (and remove the potential<BR>for confusion).<BR><BR>" The frame CRC, when used, MUST be calculated only over !
 all class
 A<BR>bits in the frame."<BR><BR>- Which "frame" is this about? - I think this is the payload-codec-frame of<BR>RTP?<BR><BR>4) A correct UDP-Lite implementation MUST discard these packets (this is<BR>also the way DCCP is expected to behave when using partial checksum<BR>coverage). Of course AMR can also be used over non-IP transports, and then<BR>you rely on their multiplexing and control functions to supply the bit<BR>stream that AMR uses.<BR><BR>The rationale for IP transport was that allowing these packets to pass up<BR>the stack with no verification of the IP header (in IPv6) or UDP-Lite header<BR>(IPv4,IPv6), could result in cases of mis-delivery of arbitary corrupted<BR>packets to *any* port, and applications do not generally have an ability to<BR>handle such events robustly (with serious implications). So, unless there is<BR>a strong argument, I'd recommend that if you use an IP network, you MUST use<BR>a transport layer checksum.<BR><BR>&gt; A better proposal may be !
 to
 rewrite that sentence to simple note that<BR>&gt; any packets with errors detected by the UDP-Lite checksum or lower layer<BR>&gt; in that part will be discarded and never delivered.<BR>&gt; <BR><BR>Exactly:-)<BR><BR>&gt; Please provide more feedback if such a change is appropriate.<BR>&gt; <BR>&gt; <BR>&gt; Cheers<BR>&gt; <BR>&gt; <BR>&gt; Magnus Westerlund<BR>&gt; <BR>&gt; Multimedia Technologies, Ericsson Research EAB/TVA/A<BR>&gt; ----------------------------------------------------------------------<BR>&gt; Ericsson AB | Phone +46 8 4048287<BR>&gt; Torshamsgatan 23 | Fax +46 8 7575550<BR>&gt; S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com<BR>&gt; <BR><BR>I'm relieved we were closer than I thought... Are there still points of<BR>disagreement?<BR><BR>Gorry<BR><BR><BR><BR><BR><BR>------------------------------<BR><BR>Message: 2<BR>Date: Thu, 9 Dec 2004 13:41:11 -0500<BR>From: "Phelan, Tom" <TPHELAN@SONUSNET.COM><BR>Subject: [AVT] RE: [dccp] TFRC appli!
 ed to
 HDTV uncompressed 1.5 Gbps<BR>To: "Alejandro Cabrera Obed" <ACO1967@GMAIL.COM>, "AVT Lista"<BR><AVT@IETF.ORG>, "DCCP Lista" <DCCP@IETF.ORG><BR>Message-ID:<BR><A3863F3136CBC546A40A61BA9CBA9D93079C30@SONUSMAIL03.SONUSNET.COM><BR>Content-Type: text/plain; charset="iso-8859-1"<BR><BR>Hi Alejandro,<BR><BR>See inline ...<BR><BR>Tom Phelan<BR><BR>&gt; -----Original Message-----<BR>&gt; From: Alejandro Cabrera Obed [mailto:aco1967@gmail.com]<BR>&gt; Sent: Thursday, December 09, 2004 11:43 AM<BR>&gt; To: AVT Lista; DCCP Lista<BR>&gt; Subject: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps<BR>&gt; <BR>&gt; <BR>&gt; Dear people,<BR>&gt; <BR>&gt; I'm from Argentina, developing a survey about HDTV uncompressed live<BR>&gt; streaming over IP. I'm contacting you in order to know what you think<BR>&gt; about applying TFRC to HDTV uncompressed live streaming (aprox. 1.5<BR>&gt; Gbps), in order to get congestion control.<BR>&gt; <BR>&gt; 1) Do you think there is any limitation in applying!
  the TFRC
 mechanism<BR>&gt; to my scenario ???<BR><BR>I think there's two issues you'll need to deal with. One is slow start - it'll take a good number of round trip times to get up to 1.5G bps. The other is, what will you do when there is congestion and you must reduce the transmit rate? I assume you'll be using large packets to get that high a transmit rate, so the small packet issues shown in http://www.phelan-4.com/dccp/tfrc-self-limit.pdf won't be a problem.<BR><BR>&gt; 2) Is it correct the use of RTCP like a feedback mechanism for TFRC,<BR>&gt; taking the RTCP throughput at about 5% of 1.5 Gbps ???<BR><BR>Normally TFRC requires one feedback packet per RTT. So the RTCP 5% limit is a bit problematic. The feedback is greater or less than 5% depending on the RTT. I know this has been raised as a problem the RTP profile for TFRC - I'm not sure how Ladan has dealt with it. For DCCP, there's no such restriction. The DCCP feedback packets are fairly small - I don't remember the exact s!
 ize, but
 using 40 bytes, you'd need an RTT of less than 5 microseconds to use up 5% of 1.5G on the feedback.<BR><BR>&gt; <BR>&gt; Maybe, if TRFC is OK to HDTV uncompressed, I'm interesting in studying<BR>&gt; into account the use of LSR and DLSR fields of RR in order to<BR>&gt; calculate the RTT.<BR>&gt; <BR>&gt; Thanks a lot, I appreciate your opinion.<BR>&gt; <BR>&gt; <BR>&gt; Alejandro Cabrera Obed<BR>&gt; <BR>&gt; _______________________________________________<BR>&gt; dccp IETF mailing list: dccp@ietf.org<BR>&gt; list info: https://www1.ietf.org/mailman/listinfo/dccp<BR>&gt; wg charter: http://www.ietf.org/html.charters/dccp-charter.html<BR>&gt; <BR><BR><BR><BR>------------------------------<BR><BR>Message: 3<BR>Date: Thu, 9 Dec 2004 19:16:22 +0000<BR>From: Colin Perkins <CSP@CSPERKINS.ORG><BR>Subject: [AVT] Re: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps<BR>To: "Phelan, Tom" <TPHELAN@SONUSNET.COM><BR>Cc: DCCP Lista <DCCP@IETF.ORG>, AVT Lista <AVT@IETF.ORG><BR>Message-ID:
 <D019C382-4A16-11D9-99D3-000A957FC5F2@CSPERKINS.ORG><BR>Content-Type: text/plain; charset=US-ASCII; format=flowed<BR><BR>You would also have the issue of how to maintain acceptable viewing <BR>quality whilst varying the transmission rate. That problem is at least <BR>as difficult as the practicalities of making the TFRC mechanisms work <BR>(and note that you must either compress or discard data to do this in <BR>real-time, so using TFRC for "uncompressed" HDTV isn't practical if <BR>there might be congestion).<BR><BR>Colin<BR><BR><BR><BR>On 9 Dec 2004, at 18:41, Phelan, Tom wrote:<BR><BR>&gt; Hi Alejandro,<BR>&gt;<BR>&gt; See inline ...<BR>&gt;<BR>&gt; Tom Phelan<BR>&gt;<BR>&gt;&gt; -----Original Message-----<BR>&gt;&gt; From: Alejandro Cabrera Obed [mailto:aco1967@gmail.com]<BR>&gt;&gt; Sent: Thursday, December 09, 2004 11:43 AM<BR>&gt;&gt; To: AVT Lista; DCCP Lista<BR>&gt;&gt; Subject: [dccp] TFRC applied to HDTV uncompressed 1.5 Gbps<BR>&gt;&gt;<BR>&gt;&gt;<BR>&gt;&gt; D!
 ear
 people,<BR>&gt;&gt;<BR>&gt;&gt; I'm from Argentina, developing a survey about HDTV uncompressed live<BR>&gt;&gt; streaming over IP. I'm contacting you in order to know what you think<BR>&gt;&gt; about applying TFRC to HDTV uncompressed live streaming (aprox. 1.5<BR>&gt;&gt; Gbps), in order to get congestion control.<BR>&gt;&gt;<BR>&gt;&gt; 1) Do you think there is any limitation in applying the TFRC mechanism<BR>&gt;&gt; to my scenario ???<BR>&gt;<BR>&gt; I think there's two issues you'll need to deal with. One is slow <BR>&gt; start - it'll take a good number of round trip times to get up to 1.5G <BR>&gt; bps. The other is, what will you do when there is congestion and you <BR>&gt; must reduce the transmit rate? I assume you'll be using large packets <BR>&gt; to get that high a transmit rate, so the small packet issues shown in <BR>&gt; http://www.phelan-4.com/dccp/tfrc-self-limit.pdf won't be a problem.<BR>&gt;<BR>&gt;&gt; 2) Is it correct the use of RTCP like a feedback !
 mechanism
 for TFRC,<BR>&gt;&gt; taking the RTCP throughput at about 5% of 1.5 Gbps ???<BR>&gt;<BR>&gt; Normally TFRC requires one feedback packet per RTT. So the RTCP 5% <BR>&gt; limit is a bit problematic. The feedback is greater or less than 5% <BR>&gt; depending on the RTT. I know this has been raised as a problem the <BR>&gt; RTP profile for TFRC - I'm not sure how Ladan has dealt with it. For <BR>&gt; DCCP, there's no such restriction. The DCCP feedback packets are <BR>&gt; fairly small - I don't remember the exact size, but using 40 bytes, <BR>&gt; you'd need an RTT of less than 5 microseconds to use up 5% of 1.5G on <BR>&gt; the feedback.<BR>&gt;<BR>&gt;&gt;<BR>&gt;&gt; Maybe, if TRFC is OK to HDTV uncompressed, I'm interesting in studying<BR>&gt;&gt; into account the use of LSR and DLSR fields of RR in order to<BR>&gt;&gt; calculate the RTT.<BR>&gt;&gt;<BR>&gt;&gt; Thanks a lot, I appreciate your opinion.<BR>&gt;&gt;<BR>&gt;&gt;<BR>&gt;&gt; Alejandro Cabrera
 Obed<BR>&gt;&gt;<BR>&gt;&gt; _______________________________________________<BR>&gt;&gt; dccp IETF mailing list: dccp@ietf.org<BR>&gt;&gt; list info: https://www1.ietf.org/mailman/listinfo/dccp<BR>&gt;&gt; wg charter: http://www.ietf.org/html.charters/dccp-charter.html<BR><BR><BR><BR><BR>------------------------------<BR><BR>Message: 4<BR>Date: Thu, 09 Dec 2004 15:43:57 -0500<BR>From: Internet-Drafts@ietf.org<BR>Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-amrwbplus-03.txt<BR>To: i-d-announce@ietf.org<BR>Cc: avt@ietf.org<BR>Message-ID: &lt;200412092043.PAA02399@ietf.org&gt;<BR>Content-Type: text/plain; charset="us-ascii"<BR><BR>A New Internet-Draft is available from the on-line Internet-Drafts directories.<BR>This draft is a work item of the Audio/Video Transport Working Group of the IETF.<BR><BR>Title : Real-Time Transport Protocol (RTP) Payload Format for <BR>Extended AMR Wideband (AMR-WB+) Audio Codec<BR>Author(s) : J. Sjoberg, et al.<BR>Filename :
 draft-ietf-avt-rtp-amrwbplus-03.txt<BR>Pages : 35<BR>Date : 2004-12-9<BR><BR>This document specifies a real-time transport protocol (RTP) payload<BR>format to be used for Extended AMR Wideband (AMR-WB+) encoded audio<BR>signals. The AMR-WB+ codec is an audio extension of the AMR-WB codec<BR>providing additional modes designed to give higher quality of music<BR>and speech than the original modes. A MIME type registration is<BR>included for AMR-WB+.<BR><BR>A URL for this Internet-Draft is:<BR>http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-amrwbplus-03.txt<BR><BR>To remove yourself from the I-D Announcement list, send a message to <BR>i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. <BR>You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce <BR>to change your subscription settings.<BR><BR><BR>Internet-Drafts are also available by anonymous FTP. Login with the username<BR>"anonymous" and a password of your e-mail addres!
 s. After
 logging in,<BR>type "cd internet-drafts" and then<BR>"get draft-ietf-avt-rtp-amrwbplus-03.txt".<BR><BR>A list of Internet-Drafts directories can be found in<BR>http://www.ietf.org/shadow.html <BR>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt<BR><BR><BR>Internet-Drafts can also be obtained by e-mail.<BR><BR>Send a message to:<BR>mailserv@ietf.org.<BR>In the body type:<BR>"FILE /internet-drafts/draft-ietf-avt-rtp-amrwbplus-03.txt".<BR><BR>NOTE: The mail server at ietf.org can return the document in<BR>MIME-encoded form by using the "mpack" utility. To use this<BR>feature, insert the command "ENCODING mime" before the "FILE"<BR>command. To decode the response(s), you will need "munpack" or<BR>a MIME-compliant mail reader. Different MIME-compliant mail readers<BR>exhibit different behavior, especially when dealing with<BR>"multipart" MIME messages (i.e. documents which have been split<BR>up into multiple messages), so check your local documentation on<BR>how to manipulate these
 messages.<BR><BR><BR>Below is the data which will enable a MIME compliant mail reader<BR>implementation to automatically retrieve the ASCII version of the<BR>Internet-Draft.<BR>-------------- next part --------------<BR>Skipped content of type multipart/alternative<BR><BR>------------------------------<BR><BR>Message: 5<BR>Date: Thu, 09 Dec 2004 15:44:02 -0500<BR>From: Internet-Drafts@ietf.org<BR>Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-bv-02.txt<BR>To: i-d-announce@ietf.org<BR>Cc: avt@ietf.org<BR>Message-ID: &lt;200412092044.PAA02408@ietf.org&gt;<BR>Content-Type: text/plain; charset="us-ascii"<BR><BR>A New Internet-Draft is available from the on-line Internet-Drafts directories.<BR>This draft is a work item of the Audio/Video Transport Working Group of the IETF.<BR><BR>Title : RTP Payload and Storage Format for BroadVoice Speech Codecs<BR><BR>=== message truncated ===</BLOCKQUOTE><p>
		<hr size=1>Do you Yahoo!?<br> 
Yahoo! Mail - 250MB free storage. <a href="http://us.rd.yahoo.com/evt=29915/*http://info.mail.yahoo.com/mail_250">Do more. Manage less.</a>
--0-1893106423-1103286288=:50649--


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

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

--===============0411212725==--



From avt-bounces@ietf.org  Sun Dec 19 19:57:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27203
	for <avt-archive@ietf.org>; Sun, 19 Dec 2004 19:57:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgC0w-0000D8-WE
	for avt-archive@ietf.org; Sun, 19 Dec 2004 20:07:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgBnM-00052a-Et; Sun, 19 Dec 2004 19:53:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgBmT-0004r4-NA; Sun, 19 Dec 2004 19:52:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26824;
	Sun, 19 Dec 2004 19:52:05 -0500 (EST)
Received: from cs.columbia.edu ([128.59.16.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgBvc-00005A-HL; Sun, 19 Dec 2004 20:01:37 -0500
Received: from razor.cs.columbia.edu
	(IDENT:l59pBPtYDVv9VpBx8lxed6W9cGXQDz/3@razor.cs.columbia.edu
	[128.59.16.8])
	by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id iBK0q5e9003931
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); 
	Sun, 19 Dec 2004 19:52:05 -0500 (EST)
Received: from [127.0.0.1] (IDENT:6ixMjLMhlTNMDEER1LRwoBQUPKmr7ISW@localhost
	[127.0.0.1])
	by razor.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id iBK0q4U3007110;
	Sun, 19 Dec 2004 19:52:04 -0500
Message-ID: <41C62240.5070202@cs.columbia.edu>
Date: Sun, 19 Dec 2004 19:52:16 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: avt@ietf.org, mmusic@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.2.0,
	Antispam-Data: 2004.12.18.1
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0,
	__CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0,
	__PORN_PHRASE_15_0 0, __SANE_MSGID 0'
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit
Subject: [AVT] Maximum non-scaled image size
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit

Do any video payload formats specify, as SDP format attributes or 
otherwise, the maximum image size supported natively (i.e., without 
downscaling)?

For a draft we're working on, I'd like to re-use any existing 
conventions. In general, it would seem useful to know this since there 
isn't much point in sending at a higher resolution than the screen 
resolution or the maximum size that an application can handle. This 
seems like a natural extension to a=framerate in SDP.

Henning


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


From avt-bounces@ietf.org  Sun Dec 19 20:40:21 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00159
	for <avt-archive@ietf.org>; Sun, 19 Dec 2004 20:40:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgCgJ-0001Bc-TI
	for avt-archive@ietf.org; Sun, 19 Dec 2004 20:49:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgCVj-0001ZQ-VV; Sun, 19 Dec 2004 20:38:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgCQm-00014f-Qj; Sun, 19 Dec 2004 20:33:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29739;
	Sun, 19 Dec 2004 20:33:46 -0500 (EST)
Received: from mail3.microsoft.com ([131.107.3.123])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgCZv-00011A-BW; Sun, 19 Dec 2004 20:43:16 -0500
Received: from mailout1.microsoft.com ([157.54.1.117]) by mail3.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Sun, 19 Dec 2004 17:32:05 -0800
Received: from red-hub-01.redmond.corp.microsoft.com ([157.54.7.71]) by
	mailout1.microsoft.com with Microsoft SMTPSVC(6.0.3790.1264); 
	Sun, 19 Dec 2004 17:32:06 -0800
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com
	([157.54.0.39]) by red-hub-01.redmond.corp.microsoft.com with
	Microsoft SMTPSVC(6.0.3790.1264); Sun, 19 Dec 2004 17:32:05 -0800
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com
	([157.54.12.81]) by
	win-imc-01.wingroup.windeploy.ntdev.microsoft.com with
	Microsoft SMTPSVC(6.0.3790.1289); Sun, 19 Dec 2004 17:32:05 -0800
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: [AVT] Maximum non-scaled image size
Date: Sun, 19 Dec 2004 17:32:01 -0800
Message-ID: <91D7F2CEE3425A4A9D11311D09FCE2460C5B1F71@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: [AVT] Maximum non-scaled image size
thread-index: AcTmLtSTU4zTsv0oSk6UHzZYvGVuOAAAWePg
From: "Gary Sullivan" <garysull@windows.microsoft.com>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>, <avt@ietf.org>,
        <mmusic@ietf.org>
X-OriginalArrivalTime: 20 Dec 2004 01:32:05.0321 (UTC)
	FILETIME=[B6869390:01C4E633]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: quoted-printable
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: quoted-printable


There are ways to declare an image size as part of a decoder capability
or a decoder preference indication in both H.245 and SDP (and perhaps
other places too, most likely including H.241 and what H.320 uses) -- I
would suggest checking the design in regards to H.263 as that has
probably been the most commonly used video codec in two-way
communication scenarios.

When specified as part of a declaration of decoder capability, an image
size would ordinarily be interpreted as the maximum that the decoder
could decode, rather than as the maximum it can display.  But if
specified as a decoder preference, its interpretation would be more akin
to what you mention.  That would be a declaration of what image size the
decoder would most like to receive, although perhaps not necessarily an
indication of exactly why.  In some sense, that might be a better thing
to design than what you seek.  (Why pick only one specific reason for
the decoder to indicate its preference for something?)

A decoder might also, of course, use censorship of its decoder
capability declaration to simply not declare capabilities beyond its
native display resolutions.

>From draft-ietf-avt-rfc2429-bis-03.txt (September 2004, section 8.1),
there is a way in SDP for an H.263 decoder to indicate an ordered list
of preferences for picture resolution and frame rate.  (That stuff is
also probably in the original RFC 2429 as well -- I just happen to have
checked the "bis" draft).

Best Regards,

Gary Sullivan


+> -----Original Message-----
+> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On=20
+> Behalf Of Henning Schulzrinne
+> Sent: Sunday, December 19, 2004 4:52 PM
+> To: avt@ietf.org; mmusic@ietf.org
+> Subject: [AVT] Maximum non-scaled image size
+>=20
+> Do any video payload formats specify, as SDP format attributes or=20
+> otherwise, the maximum image size supported natively (i.e., without=20
+> downscaling)?
+>=20
+> For a draft we're working on, I'd like to re-use any existing=20
+> conventions. In general, it would seem useful to know this=20
+> since there=20
+> isn't much point in sending at a higher resolution than the screen=20
+> resolution or the maximum size that an application can handle. This=20
+> seems like a natural extension to a=3Dframerate in SDP.
+>=20
+> Henning
+>=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 Dec 20 02:43:47 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07852
	for <avt-archive@ietf.org>; Mon, 20 Dec 2004 02:43:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgIM4-0000qO-HJ
	for avt-archive@ietf.org; Mon, 20 Dec 2004 02:53:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgI96-0007P4-Fd; Mon, 20 Dec 2004 02:39:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgI86-0007E7-8R; Mon, 20 Dec 2004 02:38:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07589;
	Mon, 20 Dec 2004 02:38:52 -0500 (EST)
Received: from fep15.012.net.il ([212.117.129.240])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgIHI-0000kI-KM; Mon, 20 Dec 2004 02:48:25 -0500
Received: from isrexch01.israel.polycom.com ([212.199.61.2])
	by fep15.012.net.il with ESMTP
	id <20041220073611.ZLO5205.fep15@isrexch01.israel.polycom.com>;
	Mon, 20 Dec 2004 09:36:11 +0200
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
Date: Mon, 20 Dec 2004 09:32:21 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C921901@IsrExch01.israel.polycom.com>
Thread-Topic: [MMUSIC] Maximum non-scaled image size
Thread-Index: AcTmLtRxkdMT/ytaQ8+WhE+BIblXUwANKIQA
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>, <avt@ietf.org>,
        <mmusic@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: quoted-printable
Subject: [AVT] RE: [MMUSIC] Maximum non-scaled image size
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: quoted-printable

Henning,
In the bis drafts for the H.263 and H.261 I added the support for
specifying the image size that the decoder can receive per frame rate.
For H.261 the support is for fixed resolutions for H.263 the support is
also for custom formats. See draft-ietf-avt-rfc2429-bis-03.txt and
draft-ietf-avt-rfc2032-bis-03.txt
In the H.264, see draft-ietf-avt-rtp-h264-11, the concept was that the
decoder, using the level parameter, specifies the number of macro blocks
per second it can process; The level as specified in H.264 gives a
maximum on the frame rate and resolution. The level parameters can be
overridden by the optional parameters specified in the draft.

The transformation from the decoder to the display is up to the
implementer. =20

As can be seen in H.261 and H.263 the SDP from the receiver can specify
an exact picture size(resolution)it can receive, but still the encoder
can send any allowed picture size that is bellow the decoder capability.
For example in H.261 if the decoder specifies it can receive a CIF
picture at 30 fps, the encoder can send a QCIF picture at 15 fps.=20
In H.264 there is no explicit resolution specified.

Roni Even



-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
Of Henning Schulzrinne
Sent: Monday, December 20, 2004 2:52 AM
To: avt@ietf.org; mmusic@ietf.org
Subject: [MMUSIC] Maximum non-scaled image size

Do any video payload formats specify, as SDP format attributes or=20
otherwise, the maximum image size supported natively (i.e., without=20
downscaling)?

For a draft we're working on, I'd like to re-use any existing=20
conventions. In general, it would seem useful to know this since there=20
isn't much point in sending at a higher resolution than the screen=20
resolution or the maximum size that an application can handle. This=20
seems like a natural extension to a=3Dframerate in SDP.

Henning


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

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


From avt-bounces@ietf.org  Mon Dec 20 16:57:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14658
	for <avt-archive@ietf.org>; Mon, 20 Dec 2004 16:57:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgVgF-000702-IB
	for avt-archive@ietf.org; Mon, 20 Dec 2004 17:07:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgVGy-0007Gp-4Y; Mon, 20 Dec 2004 16:40:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgV2k-0005h1-SY; Mon, 20 Dec 2004 16:26:14 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09647;
	Mon, 20 Dec 2004 16:26:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgVC5-0005GB-Ly; Mon, 20 Dec 2004 16:35:53 -0500
Received: from apache by megatron.ietf.org with local (Exim 4.32)
	id 1CgUka-0001gz-Uk; Mon, 20 Dec 2004 16:07:28 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1CgUka-0001gz-Uk@megatron.ietf.org>
Date: Mon, 20 Dec 2004 16:07:28 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48
Cc: avt chair <magnus.westerlund@ericsson.com>, avt chair <csp@csperkins.org>,
        Internet Architecture Board <iab@iab.org>,
        avt mailing list <avt@ietf.org>,
        RFC Editor <rfc-editor@rfc-editor.org>
Subject: [AVT] Protocol Action: 'RTP payload Format for H.264 Video' 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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ded6070f7eed56e10c4f4d0d5043d9c7

The IESG has approved the following document:

- 'RTP payload Format for H.264 Video '
   <draft-ietf-avt-rtp-h264-11.txt> as a Proposed Standard

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

The IESG contact persons are Allison Mankin and Jon Peterson.

Technical Summary
 
    This specification describes an RTP Payload format for the ITU-T
    Recommendation H.264 video codec and the technically identical
    ISO/IEC International Standard 14496-10 video codec.  The RTP
    payload format allows for packetization of one or more Network
    Abstraction Layer Units (NALUs), produced by an H.264 video encoder,
    in each RTP payload.  The payload format has wide applicability
    supporting from simple low-bit rate conversational usage to Internet
    video streaming with interleaved transmission, all the way to high
    bit-rate video-on-demand applications. 

    Congestion control can be supported by selective transition between
    rates, because the codec is so rate-agile.  

    Working Group Summary
 
    The working group supported advancing this specification.  The working
    group was made aware of an IPR disclosure by Nokia and determined
    that the standardization should proceed.

Protocol Quality
 
   Allison Mankin reviewed the document for the IESG.

RFC Editor Notes

Section 8.1, at the end:

OLD:
     Author/Change controller:
                          stewe@stewe.org
                          IETF Audio/Video transport working group

NEW:
     Author:
                          stewe@stewe.org
     Change controller:
                          IETF Audio/Video Transport working group
                          delegated from the IESG.

[Addresses Media Type Review]

-------

Section 9, second paragraph:
OLD:
     Therefore the usage of authentication of at least the
     RTP packet is RECOMMENDED, for example with SRTP [29].

NEW:
     Therefore the usage of data origin authentication and
     data integrity protection of at least the RTP packet
     is RECOMMENDED, for example with SRTP [29].


Section 9, Fourth paragraph:

OLD:
     As with any IP-based protocol, in some circumstances a receiver may
     be overloaded simply by the receipt of too many packets, either
     desired or undesired.  Network-layer authentication may be used to
     discard packets from undesired sources, but the processing cost of
     the authentication itself may be too high.  In a multicast
     environment, pruning of specific sources may be implemented in
     future versions of IGMP [19] and in multicast routing protocols to
     allow a receiver to select which sources are allowed to reach it.

NEW:

Remove the complete paragraph

[Addresses Sam Hartman's Discuss]

-------

Section 9 After the last paragraph 

Add the following new paragraph
NEW:

     End-to-End security with either authentication, integrity or
     confidentiality protection will prevent a MANE from performing
     media-aware operations other than discarding complete packets. And
     in the case of confidentiality protection it will even be prevented
     from performing discarding of packets in a media aware way. To allow
     any MANE to perform its operations, it will be required to be a
     trusted entity which is included in the security context
     establishment.

[Addresses AD Review]

Section 10 First Paragraph
OLD:
     Congestion control for RTP SHALL be used in accordance with RFC 3550
     [4], and any applicable RTP profile, e.g. RFC 3551 [18].  This means
     that congestion control is required for any transmission over
     unmanaged best-effort networks.


NEW:
     Congestion control for RTP SHALL be used in accordance with RFC 3550
     [4], and any applicable RTP profile, e.g. RFC 3551 [18].  An
     additional requirement if best-effort service is being used are:
     users of this payload format MUST monitor packet loss to ensure that
     the packet loss rate is within acceptable parameters.  Packet loss
     is considered acceptable if a TCP flow across the same network path,
     and experiencing the same network conditions, would achieve an
     average throughput, measured on a reasonable timescale, that is not
     less than the RTP flow is achieving. This condition can be satisfied
     by implementing congestion control mechanisms to adapt the
     transmission rate (or the number of layers subscribed for a layered
     multicast session), or by arranging for a receiver to leave the
     session if the loss rate is unacceptably high.

[Addresses AD Review]


Section 10, Second Paragraph
OLD:
                                                       Only if non-
     downgradable parameters, such as the profile part of the
     profile/level ID change, it becomes necessary to terminate and re-
     start the media stream, possibly using a different RTP payload type.

NEW:

     Only if non-downgradable parameters, such as the profile part of
     the profile/level ID is required to be changed, will it become
     necessary to terminate and re-start the media stream. This may be
     accomplished by using a different RTP payload type.

[Fixes ungrammatical sentence]


Section 9, first paragraph:
OLD:

            Because the data compression used with this payload format is
     applied end-to-end, encryption may be performed after compression so
     there is no conflict between the two operations.

NEW:
     Because the data compression used with this payload format is
     applied end-to-end, any encryption needs to be performed after
     compression.

[Addresses Russ Housley's Discuss]


Section "Author's Address" for the RFC editor to send Auth48 to the
right addresses.

OLD:
     Thomas Stockhammer                Phone: +49-89-28923474
     Institute for Communications Eng. Email: stockhammer@ei.tum.de
     Munich University of Technology
     D-80290 Munich
     Germany

NEW:
     Thomas Stockhammer                Phone: +49-89-28923474
     Institute for Communications Eng. Email: stockhammer@nomor.de
                                              ^^^^^^^^^^^^^^^^^^^^
     Munich University of Technology
     D-80290 Munich
     Germany


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


From avt-bounces@ietf.org  Mon Dec 20 17:30:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19449
	for <avt-archive@ietf.org>; Mon, 20 Dec 2004 17:30:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgWC5-0008HF-ME
	for avt-archive@ietf.org; Mon, 20 Dec 2004 17:39:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgVzK-0006kG-ON; Mon, 20 Dec 2004 17:26:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgVun-0005ik-JX
	for avt@megatron.ietf.org; Mon, 20 Dec 2004 17:22:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18774;
	Mon, 20 Dec 2004 17:22:02 -0500 (EST)
Received: from dns.packetdesign.com ([65.192.41.10]
	helo=mailman.packetdesign.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgW48-00083n-Fj; Mon, 20 Dec 2004 17:31:45 -0500
Received: from ash.packetdesign.com (ash.packetdesign.com [192.168.0.243])
	by mailman.packetdesign.com (8.12.8/8.12.8) with ESMTP id
	iBKML18s035593; Mon, 20 Dec 2004 14:21:01 -0800 (PST)
	(envelope-from casner@acm.org)
Date: Mon, 20 Dec 2004 14:21:01 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: The IESG <iesg-secretary@ietf.org>
Subject: Re: [AVT] Protocol Action: 'RTP payload Format for H.264 Video' to
	Proposed Standard 
In-Reply-To: <E1CgUka-0001gz-Uk@megatron.ietf.org>
Message-ID: <20041220141748.J34476@ash.packetdesign.com>
References: <E1CgUka-0001gz-Uk@megatron.ietf.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: avt chair <magnus.westerlund@ericsson.com>,
        RFC Editor <rfc-editor@rfc-editor.org>, avt chair <csp@csperkins.org>,
        avt mailing list <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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4

On Mon, 20 Dec 2004, The IESG wrote:

> The IESG has approved the following document:
>
> - 'RTP payload Format for H.264 Video '
>    <draft-ietf-avt-rtp-h264-11.txt> as a Proposed Standard

I'm glad this is approved.  In the RFC Editor Notes, there is a
grammar problem within the new text:

> Section 10 First Paragraph
> OLD:
>      Congestion control for RTP SHALL be used in accordance with RFC 3550
>      [4], and any applicable RTP profile, e.g. RFC 3551 [18].  This means
>      that congestion control is required for any transmission over
>      unmanaged best-effort networks.
>
>
> NEW:
>      Congestion control for RTP SHALL be used in accordance with RFC 3550
>      [4], and any applicable RTP profile, e.g. RFC 3551 [18].  An
>      additional requirement if best-effort service is being used are:
                                                                   ^^^ is
>      users of this payload format MUST monitor packet loss to ensure that
>      the packet loss rate is within acceptable parameters.  Packet loss
>      is considered acceptable if a TCP flow across the same network path,
>      and experiencing the same network conditions, would achieve an
>      average throughput, measured on a reasonable timescale, that is not
>      less than the RTP flow is achieving. This condition can be satisfied
>      by implementing congestion control mechanisms to adapt the
>      transmission rate (or the number of layers subscribed for a layered
>      multicast session), or by arranging for a receiver to leave the
>      session if the loss rate is unacceptably high.
>
> [Addresses AD Review]

                                                        -- Steve

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


From avt-bounces@ietf.org  Mon Dec 20 17:49:58 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20884
	for <avt-archive@ietf.org>; Mon, 20 Dec 2004 17:49:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgWVA-0000KR-RF
	for avt-archive@ietf.org; Mon, 20 Dec 2004 17:59:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgWKI-0002PD-HJ; Mon, 20 Dec 2004 17:48:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgWBp-0000bn-W1
	for avt@megatron.ietf.org; Mon, 20 Dec 2004 17:39:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20106
	for <avt@ietf.org>; Mon, 20 Dec 2004 17:39:39 -0500 (EST)
Message-Id: <200412202239.RAA20106@ietf.org>
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgWLB-000052-CM
	for avt@ietf.org; Mon, 20 Dec 2004 17:49:21 -0500
Received: from localhost ([127.0.0.1] helo=psg.com)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CgWBn-000AQx-4k; Mon, 20 Dec 2004 22:39:39 +0000
To: Stephen Casner <casner@acm.org>
Subject: Re: [AVT] Protocol Action: 'RTP payload Format for H.264 Video' to
	Proposed Standard 
In-Reply-To: Message from Stephen Casner <casner@acm.org> of "Mon,
	20 Dec 2004 14:21:01 PST." <20041220141748.J34476@ash.packetdesign.com>
Date: Mon, 20 Dec 2004 14:39:39 -0800
From: Allison Mankin <mankin@psg.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: avt chair <magnus.westerlund@ericsson.com>, avt chair <csp@csperkins.org>,
        avt@ietf.org, RFC Editor <rfc-editor@rfc-editor.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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4

Steve,

Thanks for the grammar catch!  I'm taking "IESG" off the cc
list - the Secretariat uses a ticket-generating address for some
reason, which isn't needed for this.  We can pass this fix to the
RFC Editor now.

Happy almost the New Year, everyone!

Allison

> 
> Date:    Mon, 20 Dec 2004 14:21:01 PST
> To:      The IESG <iesg-secretary@ietf.org>
> cc:      avt chair <magnus.westerlund@ericsson.com>,
> 	 RFC Editor <rfc-editor@rfc-editor.org>,
> 	 avt chair <csp@csperkins.org>, avt mailing list <avt@ietf.org>
> From:    Stephen Casner <casner@acm.org>
> Subject: Re: [AVT] Protocol Action: 'RTP payload Format for H.264 Video' to Pro
>      ***posed Standard 
> 
> 
> On Mon, 20 Dec 2004, The IESG wrote:
> 
> > The IESG has approved the following document:
> >
> > - 'RTP payload Format for H.264 Video '
> >    <draft-ietf-avt-rtp-h264-11.txt> as a Proposed Standard
> 
> I'm glad this is approved.  In the RFC Editor Notes, there is a
> grammar problem within the new text:
> 
> > Section 10 First Paragraph
> > OLD:
> >      Congestion control for RTP SHALL be used in accordance with RFC 3550
> >      [4], and any applicable RTP profile, e.g. RFC 3551 [18].  This means
> >      that congestion control is required for any transmission over
> >      unmanaged best-effort networks.
> >
> >
> > NEW:
> >      Congestion control for RTP SHALL be used in accordance with RFC 3550
> >      [4], and any applicable RTP profile, e.g. RFC 3551 [18].  An
> >      additional requirement if best-effort service is being used are:
>                                                                    ^^^ is
> >      users of this payload format MUST monitor packet loss to ensure that
> >      the packet loss rate is within acceptable parameters.  Packet loss
> >      is considered acceptable if a TCP flow across the same network path,
> >      and experiencing the same network conditions, would achieve an
> >      average throughput, measured on a reasonable timescale, that is not
> >      less than the RTP flow is achieving. This condition can be satisfied
> >      by implementing congestion control mechanisms to adapt the
> >      transmission rate (or the number of layers subscribed for a layered
> >      multicast session), or by arranging for a receiver to leave the
> >      session if the loss rate is unacceptably high.
> >
> > [Addresses AD Review]
> 
>                                                         -- Steve
> 
> _______________________________________________
> 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 Dec 21 05:13:53 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22485
	for <avt-archive@ietf.org>; Tue, 21 Dec 2004 05:13:53 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CghAw-0007c5-Rj
	for avt-archive@ietf.org; Tue, 21 Dec 2004 05:23:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CggyC-0001B4-OY; Tue, 21 Dec 2004 05:10:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CggxX-0000pa-4y
	for avt@megatron.ietf.org; Tue, 21 Dec 2004 05:09:39 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22202
	for <avt@ietf.org>; Tue, 21 Dec 2004 05:09:37 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cgh6n-0007X9-7N
	for avt@ietf.org; Tue, 21 Dec 2004 05:19:25 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBLA9PO6002174 for <avt@ietf.org>; Tue, 21 Dec 2004 11:09:25 +0100
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by
	esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 21 Dec 2004 11:09:25 +0100
Received: from [147.214.97.152] (RESEARCH-1FD0E1 [147.214.97.152]) by
	esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id ZAPCMN6K; Tue, 21 Dec 2004 11:09:25 +0100
Message-ID: <41C73B31.8010008@ericsson.com>
Date: Mon, 20 Dec 2004 21:50:57 +0100
X-Sybari-Trust: 5b1e4ab1 96d33411 0e19ce95 00000138
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: avt@ietf.org
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-amrwbplus-04.txt
References: <200412172030.PAA00516@ietf.org>
In-Reply-To: <200412172030.PAA00516@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Dec 2004 10:09:25.0973 (UTC)
	FILETIME=[269BF050:01C4E745]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit

Hi,

This update is basically editorial. It contains one real technical 
change, namely the creation of a normative table for number of RTP TS 
ticks per frame depending on used ISF.

We authors have the intention to go to WG last call after the christmas 
holidays. So please review and send us feedback so that we can get a 
great specification.

Cheers

Magnus

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		: Real-Time Transport Protocol (RTP) Payload Format 
> 			  for Extended AMR Wideband (AMR-WB+) Audio Codec
> 	Author(s)	: J. Sjoberg, et al.
> 	Filename	: draft-ietf-avt-rtp-amrwbplus-04.txt
> 	Pages		: 35
> 	Date		: 2004-12-17
> 	
> This document specifies a real-time transport protocol (RTP) payload
>     format to be used for Extended AMR Wideband (AMR-WB+) encoded audio
>     signals.  The AMR-WB+ codec is an audio extension of the AMR-WB
>     codec providing additional frame types designed to give higher
>     quality of music and speech than the original frame types.  A media
>     type registration is included for AMR-WB+.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-amrwbplus-04.txt
> 


-- 

Magnus Westerlund

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 Dec 21 11:15:28 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23338
	for <avt-archive@ietf.org>; Tue, 21 Dec 2004 11:15:28 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cgmp5-0007f8-Gl
	for avt-archive@ietf.org; Tue, 21 Dec 2004 11:25:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cgme7-0001Rp-5g; Tue, 21 Dec 2004 11:13:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgmYl-0000Lo-Fb
	for avt@megatron.ietf.org; Tue, 21 Dec 2004 11:08:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23156
	for <avt@ietf.org>; Tue, 21 Dec 2004 11:08:25 -0500 (EST)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgmiF-0007Yo-0j
	for avt@ietf.org; Tue, 21 Dec 2004 11:18:16 -0500
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id iBLGA7fL026453
	for <avt@ietf.org>; Tue, 21 Dec 2004 09:10:07 -0700 (MST)
Received: from zin24exm01.ap.mot.com (zin24exm01.ap.mot.com [10.232.25.1])
	by il06exr02.mot.com (Motorola/il06exr02) with ESMTP id iBLG73C4009585
	for <avt@ietf.org>; Tue, 21 Dec 2004 10:07:04 -0600
Received: by zin24exm01.ap.mot.com with Internet Mail Service (5.5.2657.72)
	id <WYWR0G9T>; Tue, 21 Dec 2004 21:37:23 +0530
Message-ID: <772BCEF88A1DD91191F80011856715F3245BA3@zin24exm01.ap.mot.com>
From: Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
To: avt@ietf.org
Date: Tue, 21 Dec 2004 21:37:17 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: "'Karl Norrman \\\\\(KI/EAB\\\\\)'" <karl.norrman@ericsson.com>,
        "David A. McGrew" <mcgrew@cisco.com>, mbaugher@cisco.com,
        "'Mats Naslund'" <mats.naslund@ericsson.com>
Subject: [AVT] MKI position in the received packet and Authentication tag
	length dependency
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a

Hi

RFC 3711 states the values of "n_tag" (and n_a, SRTP_PREFIX_LENGTH) MUST be
fixed for any particular fixed value of the key.

Does this mean that authentication tag length could be different for
different master keys in a SRTP session which uses more than one master key?

In such scenarios (i.e. a SRTP session using more than one master key and
using MKI mechanism to determine the master key), when a SRTP receiver
receives a packet, how does it determine the MKI value (or MKI position) in
the received packet, if auth tag length depends on the master key used at
the SRTP sender side? 

The MKI location in the received packet = 
Received packet start location + (received packet length - auth tag length -
MKI length)

Please clarify me.

Regards
Srikanth




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


From avt-bounces@ietf.org  Tue Dec 21 14:02:08 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08331
	for <avt-archive@ietf.org>; Tue, 21 Dec 2004 14:02:08 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgpQM-000489-VR
	for avt-archive@ietf.org; Tue, 21 Dec 2004 14:12:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgpEu-0002BZ-72; Tue, 21 Dec 2004 14:00:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cgp5t-0000OW-Dg
	for avt@megatron.ietf.org; Tue, 21 Dec 2004 13:50:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07639
	for <avt@ietf.org>; Tue, 21 Dec 2004 13:50:48 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgpEq-0003oc-CS
	for avt@ietf.org; Tue, 21 Dec 2004 14:00:39 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBLIoCO6009953 for <avt@ietf.org>; Tue, 21 Dec 2004 19:50:12 +0100
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 21 Dec 2004 19:50:12 +0100
Received: from ericsson.com (permit151.er.ki.sw.ericsson.se [147.214.97.151])
	by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id ZAPC38R4; Tue, 21 Dec 2004 19:50:11 +0100
Message-ID: <41C87062.7060301@ericsson.com>
Date: Tue, 21 Dec 2004 19:50:10 +0100
X-Sybari-Trust: d2696329 96d33411 ac6a41d7 00000138
From: =?ISO-8859-1?Q?Mats_N=E4slund?= <mats.naslund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
References: <772BCEF88A1DD91191F80011856715F3245BA3@zin24exm01.ap.mot.com>
In-Reply-To: <772BCEF88A1DD91191F80011856715F3245BA3@zin24exm01.ap.mot.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Dec 2004 18:50:12.0057 (UTC)
	FILETIME=[E6B9FC90:01C4E78D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit
Cc: "Karl Norrman \(KI/EAB\)" <karl.norrman@ericsson.com>,
        "David A. McGrew" <mcgrew@cisco.com>, avt@ietf.org, mbaugher@cisco.com
Subject: [AVT] Re: MKI position in the received packet and Authentication
 tag length dependency
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit

Hi

Vavilapalli Srikanth-A19563 wrote:

> RFC 3711 states the values of "n_tag" (and n_a, SRTP_PREFIX_LENGTH) MUST be
> fixed for any particular fixed value of the key.
> 
> Does this mean that authentication tag length could be different for
> different master keys in a SRTP session which uses more than one master 
> key?

Theoretically, yes. But, in practice it would require a
change of transform parameters in the middle of an ongoing session,
which I do not think many (if any) key mgmt protocols support(?)

> In such scenarios (i.e. a SRTP session using more than one master key and
> using MKI mechanism to determine the master key), when a SRTP receiver
> receives a packet, how does it determine the MKI value (or MKI position) in
> the received packet, if auth tag length depends on the master key used at
> the SRTP sender side?
> 
> The MKI location in the received packet =
> Received packet start location + (received packet length - auth tag 
> length -
> MKI length)
> 
> Please clarify me.

*If* you have a key mgmt protocol that can keep the SRTP cryptographic
context updated with dynamically varying auth tag lengths, then it
should be no problem to use your formula on a per packet basis.

I think the question is: if something is not explicitly forbidden,
does that imply that it is allowed/useful?

In this case, yes, it is allowed, but would be a bit complicated
to realize, but the complications are purely key mgmt issues, and
SRTP should not bother with it.

To motivate why we have the "MUST" as above, the reason is that the
only time when it seems at all feasible/secure to change those
parameters are in combination with a key managment operation. Still, it
does not imply that we recommend to change the parameters during the
session, but if for some reason somebody wants to (and can manage)...

Hope this answers

cheers

/Mats




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


From avt-bounces@ietf.org  Tue Dec 21 15:01:43 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13600
	for <avt-archive@ietf.org>; Tue, 21 Dec 2004 15:01:43 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgqLt-0005tr-Hs
	for avt-archive@ietf.org; Tue, 21 Dec 2004 15:11:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cgq9C-0004Kz-Dd; Tue, 21 Dec 2004 14:58:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cgq5x-0003Od-6e
	for avt@megatron.ietf.org; Tue, 21 Dec 2004 14:54:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11962
	for <avt@ietf.org>; Tue, 21 Dec 2004 14:54:55 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgqFJ-0005Tt-Ii
	for avt@ietf.org; Tue, 21 Dec 2004 15:04:48 -0500
Received: from esealmw128.eemea.ericsson.se ([153.88.254.121])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBLJshvD000039; Tue, 21 Dec 2004 20:54:43 +0100 (MET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 21 Dec 2004 20:54:41 +0100
Received: from ericsson.com ([147.214.97.151]) by esealmw128.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 21 Dec 2004 20:54:41 +0100
Message-ID: <41C87F7F.8070600@ericsson.com>
Date: Tue, 21 Dec 2004 20:54:39 +0100
From: =?ISO-8859-1?Q?Mats_N=E4slund?= <mats.naslund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Mats_N=E4slund?= <mats.naslund@ericsson.com>
References: <772BCEF88A1DD91191F80011856715F3245BA3@zin24exm01.ap.mot.com>
	<41C87062.7060301@ericsson.com>
In-Reply-To: <41C87062.7060301@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-OriginalArrivalTime: 21 Dec 2004 19:54:41.0339 (UTC)
	FILETIME=[E8FF90B0:01C4E796]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by albatross.ericsson.se
	id iBLJshvD000039
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Content-Transfer-Encoding: quoted-printable
Cc: "Karl Norrman \(KI/EAB\)" <karl.norrman@ericsson.com>,
        "David A. McGrew" <mcgrew@cisco.com>, avt@ietf.org, mbaugher@cisco.com
Subject: [AVT] Re: MKI position in the received packet and Authentication
 tag length dependency
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Content-Transfer-Encoding: quoted-printable

Hi again,

Just as I sent the previous mail (copied below), some things occurred to
me that are probably worth another mail...

In SRTP, the MKI is a bit different from e.g. an IPsec SPI, since
it is explicitly stated that the SRTP MKI identifies *only* the key,
and not the crypto context (as the SPI does in other protocols). Hence,
a conferment SRTP implementation *could* in principle be implemented in
such a way  that a change of MKI/key does not enable a simultaneous
change of transform parameters, simply because a change of MKI does not
imply anything to SRTP, except that it expects a new key. Conversely,
if you have a key mgmt protocol running in the background that keeps the
crypto context updated, you could in theory change the auth tag
length *without* simultaneous change of MKI. The MKI is not
synched with anything except the key(s).

For the same reason, the MKI is NOT needed to deduce the auth tag
length, so a "formula" (like the one you suggested) is still possible
to find. I.e. there is no "Catch-22" problem, which might have been
the case if the MKI had determined the tag length, and the tag length
in turn had determined the location of the MKI, etc...

Moreover, since SRTP supports varying tag lengths (at least from
session to session) a formula like the one you suggested is *needed*
in order to be able to correctly parse all possible SRTP packets.
Given that, I arrive at the same conclusion as before: if the key
mgmt can keep sender/reciver synched on auth. tag length, it is
in principle possible to let it vary during the session, but it does
not seem very useful(?)

Best,

/Mats

Mats N=E4slund wrote:
> Hi
>=20
> Vavilapalli Srikanth-A19563 wrote:
>=20
>> RFC 3711 states the values of "n_tag" (and n_a, SRTP_PREFIX_LENGTH)=20
>> MUST be
>> fixed for any particular fixed value of the key.
>>
>> Does this mean that authentication tag length could be different for
>> different master keys in a SRTP session which uses more than one=20
>> master key?
>=20
>=20
> Theoretically, yes. But, in practice it would require a
> change of transform parameters in the middle of an ongoing session,
> which I do not think many (if any) key mgmt protocols support(?)
>=20
>> In such scenarios (i.e. a SRTP session using more than one master key =
and
>> using MKI mechanism to determine the master key), when a SRTP receiver
>> receives a packet, how does it determine the MKI value (or MKI=20
>> position) in
>> the received packet, if auth tag length depends on the master key used=
 at
>> the SRTP sender side?
>>
>> The MKI location in the received packet =3D
>> Received packet start location + (received packet length - auth tag=20
>> length -
>> MKI length)
>>
>> Please clarify me.
>=20
>=20
> *If* you have a key mgmt protocol that can keep the SRTP cryptographic
> context updated with dynamically varying auth tag lengths, then it
> should be no problem to use your formula on a per packet basis.
>=20
> I think the question is: if something is not explicitly forbidden,
> does that imply that it is allowed/useful?
>=20
> In this case, yes, it is allowed, but would be a bit complicated
> to realize, but the complications are purely key mgmt issues, and
> SRTP should not bother with it.
>=20
> To motivate why we have the "MUST" as above, the reason is that the
> only time when it seems at all feasible/secure to change those
> parameters are in combination with a key managment operation. Still, it
> does not imply that we recommend to change the parameters during the
> session, but if for some reason somebody wants to (and can manage)...
>=20
> Hope this answers
>=20
> cheers
>=20
> /Mats
>=20


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


From avt-bounces@ietf.org  Tue Dec 21 15:43:04 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17849
	for <avt-archive@ietf.org>; Tue, 21 Dec 2004 15:43:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cgr05-0006zF-MH
	for avt-archive@ietf.org; Tue, 21 Dec 2004 15:52:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cgqp7-0006e8-LN; Tue, 21 Dec 2004 15:41:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgqnC-0005mO-8U; Tue, 21 Dec 2004 15:39:38 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17487;
	Tue, 21 Dec 2004 15:39:36 -0500 (EST)
Message-Id: <200412212039.PAA17487@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 21 Dec 2004 15:39:36 -0500
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rfc2032-bis-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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86

--NextPart

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

	Title		: RTP Payload Format for H.261 Video Streams
	Author(s)	: R. Even
	Filename	: draft-ietf-avt-rfc2032-bis-04.txt
	Pages		: 22
	Date		: 2004-12-21
	
This memo describes a scheme to packetize an H.261 video stream for
transport using the Real-time Transport Protocol, RTP, with any of
the underlying protocols that carry RTP.

This specification is a product of the Audio/Video Transport working
group within the Internet Engineering Task Force.  Comments are
solicited and should be addressed to the working group's mailing list
and/or the authors.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc2032-bis-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-rfc2032-bis-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-rfc2032-bis-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: <2004-12-21160803.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rfc2032-bis-04.txt

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

Content-Type: text/plain
Content-ID: <2004-12-21160803.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org  Wed Dec 22 03:48:13 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02146
	for <avt-archive@ietf.org>; Wed, 22 Dec 2004 03:48:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ch2Jx-0006Tg-8C
	for avt-archive@ietf.org; Wed, 22 Dec 2004 03:58:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ch25w-0004WU-LJ; Wed, 22 Dec 2004 03:43:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ch24T-00049N-G7
	for avt@megatron.ietf.org; Wed, 22 Dec 2004 03:42:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01814
	for <avt@ietf.org>; Wed, 22 Dec 2004 03:42:11 -0500 (EST)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ch2E7-0006Lf-0f
	for avt@ietf.org; Wed, 22 Dec 2004 03:52:11 -0500
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id iBM8hqfL015641
	for <avt@ietf.org>; Wed, 22 Dec 2004 01:43:52 -0700 (MST)
Received: from zin24exm01.ap.mot.com (zin24exm01.ap.mot.com [10.232.25.1])
	by il06exr04.mot.com (Motorola/il06exr04) with ESMTP id iBM8enNm032002
	for <avt@ietf.org>; Wed, 22 Dec 2004 02:40:50 -0600
Received: by zin24exm01.ap.mot.com with Internet Mail Service (5.5.2657.72)
	id <WYWR0R11>; Wed, 22 Dec 2004 14:11:07 +0530
Message-ID: <772BCEF88A1DD91191F80011856715F3245BA6@zin24exm01.ap.mot.com>
From: Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
To: =?iso-8859-1?Q?=27Mats_N=E4slund=27?= <mats.naslund@ericsson.com>
Date: Wed, 22 Dec 2004 14:11:00 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Content-Transfer-Encoding: quoted-printable
Cc: "Karl Norrman \(KI/EAB\)" <karl.norrman@ericsson.com>,
        "David A. McGrew" <mcgrew@cisco.com>, avt@ietf.org, mbaugher@cisco.com
Subject: [AVT] RE: MKI position in the received packet and Authentication
	tag le ngth dependency
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Content-Transfer-Encoding: quoted-printable

Mats

Thanks for your explanation.

In that case, can I assume that all the transform parameters (that are
associated to master key) described in the RFC 3711 (master-key length,
master-salt length, n_e, n_a, n_s, KDR, auth tag length) can be kept
constant through out the session unless (if any) key management modules =
has
some other means to sync up/communicate the sender and receiver of the
changes in these values?

Regards
Srikanth


-----Original Message-----
From: Mats N=E4slund [mailto:mats.naslund@ericsson.com]=20
Sent: Wednesday, December 22, 2004 1:25 AM
To: Mats N=E4slund
Cc: Vavilapalli Srikanth-A19563; avt@ietf.org; mbaugher@cisco.com; =
David A.
McGrew; Karl Norrman (KI/EAB)
Subject: Re: MKI position in the received packet and Authentication tag
length dependency

Hi again,

Just as I sent the previous mail (copied below), some things occurred =
to
me that are probably worth another mail...

In SRTP, the MKI is a bit different from e.g. an IPsec SPI, since
it is explicitly stated that the SRTP MKI identifies *only* the key,
and not the crypto context (as the SPI does in other protocols). Hence,
a conferment SRTP implementation *could* in principle be implemented in
such a way  that a change of MKI/key does not enable a simultaneous
change of transform parameters, simply because a change of MKI does not
imply anything to SRTP, except that it expects a new key. Conversely,
if you have a key mgmt protocol running in the background that keeps =
the
crypto context updated, you could in theory change the auth tag
length *without* simultaneous change of MKI. The MKI is not
synched with anything except the key(s).

For the same reason, the MKI is NOT needed to deduce the auth tag
length, so a "formula" (like the one you suggested) is still possible
to find. I.e. there is no "Catch-22" problem, which might have been
the case if the MKI had determined the tag length, and the tag length
in turn had determined the location of the MKI, etc...

Moreover, since SRTP supports varying tag lengths (at least from
session to session) a formula like the one you suggested is *needed*
in order to be able to correctly parse all possible SRTP packets.
Given that, I arrive at the same conclusion as before: if the key
mgmt can keep sender/reciver synched on auth. tag length, it is
in principle possible to let it vary during the session, but it does
not seem very useful(?)

Best,

/Mats

Mats N=E4slund wrote:
> Hi
>=20
> Vavilapalli Srikanth-A19563 wrote:
>=20
>> RFC 3711 states the values of "n_tag" (and n_a, SRTP_PREFIX_LENGTH)=20
>> MUST be
>> fixed for any particular fixed value of the key.
>>
>> Does this mean that authentication tag length could be different for
>> different master keys in a SRTP session which uses more than one=20
>> master key?
>=20
>=20
> Theoretically, yes. But, in practice it would require a
> change of transform parameters in the middle of an ongoing session,
> which I do not think many (if any) key mgmt protocols support(?)
>=20
>> In such scenarios (i.e. a SRTP session using more than one master =
key and
>> using MKI mechanism to determine the master key), when a SRTP =
receiver
>> receives a packet, how does it determine the MKI value (or MKI=20
>> position) in
>> the received packet, if auth tag length depends on the master key =
used at
>> the SRTP sender side?
>>
>> The MKI location in the received packet =3D
>> Received packet start location + (received packet length - auth tag=20
>> length -
>> MKI length)
>>
>> Please clarify me.
>=20
>=20
> *If* you have a key mgmt protocol that can keep the SRTP =
cryptographic
> context updated with dynamically varying auth tag lengths, then it
> should be no problem to use your formula on a per packet basis.
>=20
> I think the question is: if something is not explicitly forbidden,
> does that imply that it is allowed/useful?
>=20
> In this case, yes, it is allowed, but would be a bit complicated
> to realize, but the complications are purely key mgmt issues, and
> SRTP should not bother with it.
>=20
> To motivate why we have the "MUST" as above, the reason is that the
> only time when it seems at all feasible/secure to change those
> parameters are in combination with a key managment operation. Still, =
it
> does not imply that we recommend to change the parameters during the
> session, but if for some reason somebody wants to (and can manage)...
>=20
> Hope this answers
>=20
> cheers
>=20
> /Mats
>=20

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


From avt-bounces@ietf.org  Wed Dec 22 08:50:04 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23649
	for <avt-archive@ietf.org>; Wed, 22 Dec 2004 08:50:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ch71w-0006fG-AX
	for avt-archive@ietf.org; Wed, 22 Dec 2004 09:00:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ch6lp-00067r-DX; Wed, 22 Dec 2004 08:43:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ch6cL-0003eB-Dd
	for avt@megatron.ietf.org; Wed, 22 Dec 2004 08:33:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22092
	for <avt@ietf.org>; Wed, 22 Dec 2004 08:33:27 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ch6m1-0006Am-86
	for avt@ietf.org; Wed, 22 Dec 2004 08:43:29 -0500
Received: from esealmw126.eemea.ericsson.se ([153.88.254.123])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBMDXPh5018801; Wed, 22 Dec 2004 14:33:25 +0100 (MET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 22 Dec 2004 14:33:24 +0100
Received: from ericsson.com ([147.214.118.190]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 22 Dec 2004 14:33:24 +0100
Message-ID: <41C977A4.5070303@ericsson.com>
Date: Wed, 22 Dec 2004 14:33:24 +0100
From: =?ISO-8859-1?Q?Mats_N=E4slund?= <mats.naslund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
References: <772BCEF88A1DD91191F80011856715F3245BA6@zin24exm01.ap.mot.com>
In-Reply-To: <772BCEF88A1DD91191F80011856715F3245BA6@zin24exm01.ap.mot.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-OriginalArrivalTime: 22 Dec 2004 13:33:24.0850 (UTC)
	FILETIME=[CFF61D20:01C4E82A]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by penguin.ericsson.se id
	iBMDXPh5018801
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b7d60495f1a7f2e853e8cbae7e6dbfc
Content-Transfer-Encoding: quoted-printable
Cc: "Karl Norrman \(KI/EAB\)" <karl.norrman@ericsson.com>,
        "David A. McGrew" <mcgrew@cisco.com>, avt@ietf.org, mbaugher@cisco.com
Subject: [AVT] Re: MKI position in the received packet and Authentication
 tag length dependency
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bf422c85703d3d847fb014987125ac48
Content-Transfer-Encoding: quoted-printable

Hi Srikanth,

Before answering this, I spoke with our local SRTP implementors,
since I wanted to check how they interpreted the spec.

First, to go back to the original question on how to locate the
MKI in situations where tag length *could* vary, they suggested
a different approach: rather than computing an offset from the
start of the packet, compute a negative offset from the *end* of
the packet. The length of the packet (with SRTP overhead) should
be available from the UDP level. Thus, the formula is

MKI location in rcvd packet =3D rcvd packet length - MKI length.

The MKI length is static. (Quote: "the value of the MKI indicator
and length MUST be kept fixed for the lifetime of the context".)
This seems to completely remove all issues on this matter.

Now to your new question.

Vavilapalli Srikanth-A19563 wrote:

> In that case, can I assume that all the transform parameters (that are
> associated to master key) described in the RFC 3711 (master-key length,
> master-salt length, n_e, n_a, n_s, KDR, auth tag length) can be kept
> constant through out the session unless (if any) key management modules=
 has
> some other means to sync up/communicate the sender and receiver of the
> changes in these values?

The simple answer is yes, the transform parameters are either fixed,
or somehow, kept up-to-date/synched by key management. Clearly,
maintaining this synch may be non-trivial but it is not an issue for
SRTP.

Having said that, it could still have implications on the SRTP=20
implementation. As it turns out, our own SRTP implementation works
(somewhat simplified) like this:

- As the first SRTP packet arrives, the crypto context is consulted
   for keys, transform parameters, etc.

- After this, the context is, for the purpose of transform parameters,
   *never* consulted again, i.e. the transform parameters are "cached"
   locally in configuration of SRTP. Keys, etc, are of course still
   occasionally needed from the context (e.g. due to MKI change).

This means that our implementors have made the (not unreasonable)
interpretation that these parameters never change, although it is not
explicitly stated in the RFC. So, even if you run our implementation
with a key mgmt that does handle transform updates, transform changes
would not be noticed by SRTP. I can to some extent agree that the RFC
is a bit underspecified on this issue. OTOH, the only way for SRTP to
"notice" transform changes is to consult the crypto context/key
management ON EVERY SINGLE PACKET, which seems to imply quite a bit
of overhead, or, to introduce a "signal" mechanism to tell SRTP to
take a peek in the context after updates.

Therefore, the question is if a future update of the RFC should specify
this, or, if it should explicitly forbid dynamic changes of anything=20
except keys? I'm throwing out the question... I tried to think
of a scenario in which you would like to change e.g. encryption
algorithm in the middle of a session, but failed to do so. (Selective
encryption probably needs to be handled by other means, e.g. payload
format.) The only thing I could think of is some case where the end-user
moves from e.g. high bandwidth access to low bandwidth, in which case
there could be reason to decrease auth. tag size. Still, I have doubts
if this doesn't create more problems than it solves...

Best,

/Mats

> -----Original Message-----
> From: Mats N=E4slund [mailto:mats.naslund@ericsson.com]
> Sent: Wednesday, December 22, 2004 1:25 AM
> To: Mats N=E4slund
> Cc: Vavilapalli Srikanth-A19563; avt@ietf.org; mbaugher@cisco.com; Davi=
d A.
> McGrew; Karl Norrman (KI/EAB)
> Subject: Re: MKI position in the received packet and Authentication tag
> length dependency
>=20
> Hi again,
>=20
> Just as I sent the previous mail (copied below), some things occurred t=
o
> me that are probably worth another mail...
>=20
> In SRTP, the MKI is a bit different from e.g. an IPsec SPI, since
> it is explicitly stated that the SRTP MKI identifies *only* the key,
> and not the crypto context (as the SPI does in other protocols). Hence,
> a conferment SRTP implementation *could* in principle be implemented in
> such a way  that a change of MKI/key does not enable a simultaneous
> change of transform parameters, simply because a change of MKI does not
> imply anything to SRTP, except that it expects a new key. Conversely,
> if you have a key mgmt protocol running in the background that keeps th=
e
> crypto context updated, you could in theory change the auth tag
> length *without* simultaneous change of MKI. The MKI is not
> synched with anything except the key(s).
>=20
> For the same reason, the MKI is NOT needed to deduce the auth tag
> length, so a "formula" (like the one you suggested) is still possible
> to find. I.e. there is no "Catch-22" problem, which might have been
> the case if the MKI had determined the tag length, and the tag length
> in turn had determined the location of the MKI, etc...
>=20
> Moreover, since SRTP supports varying tag lengths (at least from
> session to session) a formula like the one you suggested is *needed*
> in order to be able to correctly parse all possible SRTP packets.
> Given that, I arrive at the same conclusion as before: if the key
> mgmt can keep sender/reciver synched on auth. tag length, it is
> in principle possible to let it vary during the session, but it does
> not seem very useful(?)
>=20
> Best,
>=20
> /Mats
>=20
> Mats N=E4slund wrote:
>  > Hi
>  >
>  > Vavilapalli Srikanth-A19563 wrote:
>  >
>  >> RFC 3711 states the values of "n_tag" (and n_a, SRTP_PREFIX_LENGTH)
>  >> MUST be
>  >> fixed for any particular fixed value of the key.
>  >>
>  >> Does this mean that authentication tag length could be different fo=
r
>  >> different master keys in a SRTP session which uses more than one
>  >> master key?
>  >
>  >
>  > Theoretically, yes. But, in practice it would require a
>  > change of transform parameters in the middle of an ongoing session,
>  > which I do not think many (if any) key mgmt protocols support(?)
>  >
>  >> In such scenarios (i.e. a SRTP session using more than one master=20
> key and
>  >> using MKI mechanism to determine the master key), when a SRTP recei=
ver
>  >> receives a packet, how does it determine the MKI value (or MKI
>  >> position) in
>  >> the received packet, if auth tag length depends on the master key=20
> used at
>  >> the SRTP sender side?
>  >>
>  >> The MKI location in the received packet =3D
>  >> Received packet start location + (received packet length - auth tag
>  >> length -
>  >> MKI length)
>  >>
>  >> Please clarify me.
>  >
>  >
>  > *If* you have a key mgmt protocol that can keep the SRTP cryptograph=
ic
>  > context updated with dynamically varying auth tag lengths, then it
>  > should be no problem to use your formula on a per packet basis.
>  >
>  > I think the question is: if something is not explicitly forbidden,
>  > does that imply that it is allowed/useful?
>  >
>  > In this case, yes, it is allowed, but would be a bit complicated
>  > to realize, but the complications are purely key mgmt issues, and
>  > SRTP should not bother with it.
>  >
>  > To motivate why we have the "MUST" as above, the reason is that the
>  > only time when it seems at all feasible/secure to change those
>  > parameters are in combination with a key managment operation. Still,=
 it
>  > does not imply that we recommend to change the parameters during the
>  > session, but if for some reason somebody wants to (and can manage)...
>  >
>  > Hope this answers
>  >
>  > cheers
>  >
>  > /Mats
>  >
>=20



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


From avt-bounces@ietf.org  Wed Dec 22 09:27:18 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26274
	for <avt-archive@ietf.org>; Wed, 22 Dec 2004 09:27:18 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ch7c8-0007jT-KS
	for avt-archive@ietf.org; Wed, 22 Dec 2004 09:37:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ch7Ec-0007zQ-AE; Wed, 22 Dec 2004 09:13:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ch79q-0004s0-66
	for avt@megatron.ietf.org; Wed, 22 Dec 2004 09:08:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24712
	for <avt@ietf.org>; Wed, 22 Dec 2004 09:08:04 -0500 (EST)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ch7JW-00076z-Ch
	for avt@ietf.org; Wed, 22 Dec 2004 09:18:06 -0500
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id iBME9hfL015867
	for <avt@ietf.org>; Wed, 22 Dec 2004 07:09:43 -0700 (MST)
Received: from zin24exm01.ap.mot.com (zin24exm01.ap.mot.com [10.232.25.1])
	by il06exr03.mot.com (Motorola/il06exr03) with ESMTP id iBME7uL6003712
	for <avt@ietf.org>; Wed, 22 Dec 2004 08:07:58 -0600
Received: by zin24exm01.ap.mot.com with Internet Mail Service (5.5.2657.72)
	id <WYWR0WR1>; Wed, 22 Dec 2004 19:36:58 +0530
Message-ID: <772BCEF88A1DD91191F80011856715F3245BA9@zin24exm01.ap.mot.com>
From: Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
To: =?iso-8859-1?Q?=27Mats_N=E4slund=27?= <mats.naslund@ericsson.com>
Date: Wed, 22 Dec 2004 19:36:52 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1e467ff145ef391eb7b594ef62b8301f
Content-Transfer-Encoding: quoted-printable
Cc: "Karl Norrman \(KI/EAB\)" <karl.norrman@ericsson.com>,
        "David A. McGrew" <mcgrew@cisco.com>, avt@ietf.org, mbaugher@cisco.com
Subject: [AVT] RE: MKI position in the received packet and Authentication
	tag le ngth dependency
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1f9797ba297220533cb8c3f4bc709a8
Content-Transfer-Encoding: quoted-printable

Mats

I am not arriving to the correct MKI location if I follow your formula.
Let's take a small example:

Let Sending RTP packet size =3D 12 byte header + 20 byte G729 payload + =
4 byte
MKI + 8 byte auth tag length =3D 44 bytes.

If a SRTP receiver receives this packet (let byte pointer pbStart is =
start
of the packet and pbEnd is the end of packet), the MKI location must be =
32
bytes after the start of the packet.

But according to your formula, MKI location will point to 4th byte in =
the
RTP packet.

MKI offset in the rcvd packet =3D 44 - 4 =3D 40
MKI location =3D compute a negative offset from the *end* of
the packet =3D (pbEnd - 40)

Am I missing some thing here?=20

Regards
Srikanth


-----Original Message-----
From: Mats N=E4slund [mailto:mats.naslund@ericsson.com]=20
Sent: Wednesday, December 22, 2004 7:03 PM
To: Vavilapalli Srikanth-A19563
Cc: avt@ietf.org; mbaugher@cisco.com; David A. McGrew; Karl Norrman =
(KI/EAB)
Subject: Re: MKI position in the received packet and Authentication tag
length dependency

Hi Srikanth,

Before answering this, I spoke with our local SRTP implementors,
since I wanted to check how they interpreted the spec.

First, to go back to the original question on how to locate the
MKI in situations where tag length *could* vary, they suggested
a different approach: rather than computing an offset from the
start of the packet, compute a negative offset from the *end* of
the packet. The length of the packet (with SRTP overhead) should
be available from the UDP level. Thus, the formula is

MKI location in rcvd packet =3D rcvd packet length - MKI length.

The MKI length is static. (Quote: "the value of the MKI indicator
and length MUST be kept fixed for the lifetime of the context".)
This seems to completely remove all issues on this matter.

Now to your new question.

Vavilapalli Srikanth-A19563 wrote:

> In that case, can I assume that all the transform parameters (that =
are
> associated to master key) described in the RFC 3711 (master-key =
length,
> master-salt length, n_e, n_a, n_s, KDR, auth tag length) can be kept
> constant through out the session unless (if any) key management =
modules
has
> some other means to sync up/communicate the sender and receiver of =
the
> changes in these values?

The simple answer is yes, the transform parameters are either fixed,
or somehow, kept up-to-date/synched by key management. Clearly,
maintaining this synch may be non-trivial but it is not an issue for
SRTP.

Having said that, it could still have implications on the SRTP=20
implementation. As it turns out, our own SRTP implementation works
(somewhat simplified) like this:

- As the first SRTP packet arrives, the crypto context is consulted
   for keys, transform parameters, etc.

- After this, the context is, for the purpose of transform parameters,
   *never* consulted again, i.e. the transform parameters are "cached"
   locally in configuration of SRTP. Keys, etc, are of course still
   occasionally needed from the context (e.g. due to MKI change).

This means that our implementors have made the (not unreasonable)
interpretation that these parameters never change, although it is not
explicitly stated in the RFC. So, even if you run our implementation
with a key mgmt that does handle transform updates, transform changes
would not be noticed by SRTP. I can to some extent agree that the RFC
is a bit underspecified on this issue. OTOH, the only way for SRTP to
"notice" transform changes is to consult the crypto context/key
management ON EVERY SINGLE PACKET, which seems to imply quite a bit
of overhead, or, to introduce a "signal" mechanism to tell SRTP to
take a peek in the context after updates.

Therefore, the question is if a future update of the RFC should specify
this, or, if it should explicitly forbid dynamic changes of anything=20
except keys? I'm throwing out the question... I tried to think
of a scenario in which you would like to change e.g. encryption
algorithm in the middle of a session, but failed to do so. (Selective
encryption probably needs to be handled by other means, e.g. payload
format.) The only thing I could think of is some case where the =
end-user
moves from e.g. high bandwidth access to low bandwidth, in which case
there could be reason to decrease auth. tag size. Still, I have doubts
if this doesn't create more problems than it solves...

Best,

/Mats

> -----Original Message-----
> From: Mats N=E4slund [mailto:mats.naslund@ericsson.com]
> Sent: Wednesday, December 22, 2004 1:25 AM
> To: Mats N=E4slund
> Cc: Vavilapalli Srikanth-A19563; avt@ietf.org; mbaugher@cisco.com; =
David
A.
> McGrew; Karl Norrman (KI/EAB)
> Subject: Re: MKI position in the received packet and Authentication =
tag
> length dependency
>=20
> Hi again,
>=20
> Just as I sent the previous mail (copied below), some things occurred =
to
> me that are probably worth another mail...
>=20
> In SRTP, the MKI is a bit different from e.g. an IPsec SPI, since
> it is explicitly stated that the SRTP MKI identifies *only* the key,
> and not the crypto context (as the SPI does in other protocols). =
Hence,
> a conferment SRTP implementation *could* in principle be implemented =
in
> such a way  that a change of MKI/key does not enable a simultaneous
> change of transform parameters, simply because a change of MKI does =
not
> imply anything to SRTP, except that it expects a new key. Conversely,
> if you have a key mgmt protocol running in the background that keeps =
the
> crypto context updated, you could in theory change the auth tag
> length *without* simultaneous change of MKI. The MKI is not
> synched with anything except the key(s).
>=20
> For the same reason, the MKI is NOT needed to deduce the auth tag
> length, so a "formula" (like the one you suggested) is still possible
> to find. I.e. there is no "Catch-22" problem, which might have been
> the case if the MKI had determined the tag length, and the tag length
> in turn had determined the location of the MKI, etc...
>=20
> Moreover, since SRTP supports varying tag lengths (at least from
> session to session) a formula like the one you suggested is *needed*
> in order to be able to correctly parse all possible SRTP packets.
> Given that, I arrive at the same conclusion as before: if the key
> mgmt can keep sender/reciver synched on auth. tag length, it is
> in principle possible to let it vary during the session, but it does
> not seem very useful(?)
>=20
> Best,
>=20
> /Mats
>=20
> Mats N=E4slund wrote:
>  > Hi
>  >
>  > Vavilapalli Srikanth-A19563 wrote:
>  >
>  >> RFC 3711 states the values of "n_tag" (and n_a, =
SRTP_PREFIX_LENGTH)
>  >> MUST be
>  >> fixed for any particular fixed value of the key.
>  >>
>  >> Does this mean that authentication tag length could be different =
for
>  >> different master keys in a SRTP session which uses more than one
>  >> master key?
>  >
>  >
>  > Theoretically, yes. But, in practice it would require a
>  > change of transform parameters in the middle of an ongoing =
session,
>  > which I do not think many (if any) key mgmt protocols support(?)
>  >
>  >> In such scenarios (i.e. a SRTP session using more than one master =

> key and
>  >> using MKI mechanism to determine the master key), when a SRTP =
receiver
>  >> receives a packet, how does it determine the MKI value (or MKI
>  >> position) in
>  >> the received packet, if auth tag length depends on the master key =

> used at
>  >> the SRTP sender side?
>  >>
>  >> The MKI location in the received packet =3D
>  >> Received packet start location + (received packet length - auth =
tag
>  >> length -
>  >> MKI length)
>  >>
>  >> Please clarify me.
>  >
>  >
>  > *If* you have a key mgmt protocol that can keep the SRTP =
cryptographic
>  > context updated with dynamically varying auth tag lengths, then it
>  > should be no problem to use your formula on a per packet basis.
>  >
>  > I think the question is: if something is not explicitly forbidden,
>  > does that imply that it is allowed/useful?
>  >
>  > In this case, yes, it is allowed, but would be a bit complicated
>  > to realize, but the complications are purely key mgmt issues, and
>  > SRTP should not bother with it.
>  >
>  > To motivate why we have the "MUST" as above, the reason is that =
the
>  > only time when it seems at all feasible/secure to change those
>  > parameters are in combination with a key managment operation. =
Still, it
>  > does not imply that we recommend to change the parameters during =
the
>  > session, but if for some reason somebody wants to (and can =
manage)...
>  >
>  > Hope this answers
>  >
>  > cheers
>  >
>  > /Mats
>  >
>=20


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


From avt-bounces@ietf.org  Wed Dec 22 10:10:52 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01039
	for <avt-archive@ietf.org>; Wed, 22 Dec 2004 10:10:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ch8IJ-00010E-2Z
	for avt-archive@ietf.org; Wed, 22 Dec 2004 10:20:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ch7ox-0007DK-9o; Wed, 22 Dec 2004 09:50:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ch7YH-0007mv-17
	for avt@megatron.ietf.org; Wed, 22 Dec 2004 09:33:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26931
	for <avt@ietf.org>; Wed, 22 Dec 2004 09:33:18 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ch7hw-0007zf-5C
	for avt@ietf.org; Wed, 22 Dec 2004 09:43:21 -0500
Received: from esealmw128.eemea.ericsson.se ([153.88.254.121])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBMEVAh7002645; Wed, 22 Dec 2004 15:31:11 +0100 (MET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 22 Dec 2004 15:31:10 +0100
Received: from ericsson.com ([147.214.118.190]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 22 Dec 2004 15:31:10 +0100
Message-ID: <41C9852E.8080700@ericsson.com>
Date: Wed, 22 Dec 2004 15:31:10 +0100
From: =?ISO-8859-1?Q?Mats_N=E4slund?= <mats.naslund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
References: <772BCEF88A1DD91191F80011856715F3245BA9@zin24exm01.ap.mot.com>
In-Reply-To: <772BCEF88A1DD91191F80011856715F3245BA9@zin24exm01.ap.mot.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Dec 2004 14:31:10.0174 (UTC)
	FILETIME=[E17497E0:01C4E832]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
Cc: "Karl Norrman \(KI/EAB\)" <karl.norrman@ericsson.com>,
        "David A. McGrew" <mcgrew@cisco.com>, avt@ietf.org, mbaugher@cisco.com
Subject: [AVT] Re: MKI position in the received packet and Authentication
 tag le ngth dependency
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit

Hi

Vavilapalli Srikanth-A19563 wrote:

> Mats
> 
> I am not arriving to the correct MKI location if I follow your formula.
> Let's take a small example:
> 
> Let Sending RTP packet size = 12 byte header + 20 byte G729 payload + 4 
> byte
> MKI + 8 byte auth tag length = 44 bytes.
> 
> If a SRTP receiver receives this packet (let byte pointer pbStart is start
> of the packet and pbEnd is the end of packet), the MKI location must be 32
> bytes after the start of the packet.
> 
> But according to your formula, MKI location will point to 4th byte in the
> RTP packet.
> 
> MKI offset in the rcvd packet = 44 - 4 = 40
> MKI location = compute a negative offset from the *end* of
> the packet = (pbEnd - 40)
> 
> Am I missing some thing here?

Sorry, I made a small misstake. In the formula, I reversed the order of
the auth tag and the MKI (the MKI comes *between* the payload and the
auth. tag, not the other way around). Thus you still do need to take
into consideration the tag size if you count "from the end".

Apologies for the confusion.


/Mats



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


From avt-bounces@ietf.org  Wed Dec 22 22:37:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14565
	for <avt-archive@ietf.org>; Wed, 22 Dec 2004 22:37:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChJx3-0004zT-8q
	for avt-archive@ietf.org; Wed, 22 Dec 2004 22:47:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChJki-0001fq-J9; Wed, 22 Dec 2004 22:35:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ChJiQ-0000zO-8i
	for avt@megatron.ietf.org; Wed, 22 Dec 2004 22:32:38 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14298
	for <avt@ietf.org>; Wed, 22 Dec 2004 22:32:35 -0500 (EST)
Received: from junkmail.cs.umd.edu ([128.8.128.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ChJsD-0004sK-P7
	for avt@ietf.org; Wed, 22 Dec 2004 22:42:46 -0500
Received: from utz.cs.umd.edu (utz.cs.umd.edu [128.8.129.122])
	by junkmail.cs.umd.edu (8.12.10/8.12.5) with ESMTP id iBN3W7Fs008188
	for <avt@ietf.org>; Wed, 22 Dec 2004 22:32:07 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by utz.cs.umd.edu (8.12.11/8.12.5) with ESMTP id iBN3W7Eq011704
	for <avt@ietf.org>; Wed, 22 Dec 2004 22:32:07 -0500
Date: Wed, 22 Dec 2004 22:32:07 -0500 (EST)
From: "Moustafa A. Youssef" <moustafa@cs.umd.edu>
To: avt@ietf.org
Message-ID: <Pine.LNX.4.58.0412222231330.11326@utz.cs.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Subject: [AVT] CFP:  IEEE WirelessCom Symposium on Mobile Computing, 2005
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1

(Our apologies if you receive multiple copies of this CFP)

-------------------------------------------------------------
                Call for Papers
           Symposium on Mobile Computing
  http://www.csee.umbc.edu/~younis/WC_MobCom05.htm
                  as part of
             IEEE WirelessCom 2005
Sheraton Maui Resort, Kaanapali Beach, Maui, Hawaii, USA
http://www.ece.queensu.ca/hpages/faculty/safwat/wirelesscom/05/
                 June 13-16, 2005
  Technical Sponsorship: IEEE TCCC, TCPC, and SSCTC


Recent years have witnessed an enormous growth in the development
and applications of mobile computing environments and devices.
Many practitioners envision a future empowered with context and
location aware computation and communication infrastructure that
allow users to access data and receive service at any place and
any time. Compared to conventional platforms, the mobility of
computing nodes introduces many challenges to the design of almost
all systems components.

This symposium will foster a forum for discussing and presenting
recent research results on mobile computer systems. Original
papers are invited in the broader area of mobile computing. Papers
must report high-quality and previously unpublished work. Topics
of interest include, but are not limited to, the following:

-  Architecture and infrastructure support
-  Middleware and operating systems services
-  Development platforms and environments
-  Adaptive resource management schemes
-  Pervasive and Context-aware Computing
-  Performance metrics and studies
-  Power aware computation and communication
-  Data consistency and synchronization protocols
-  Fault-tolerant architectural and operation models
-  Wearable computing devices and systems
-  Time constrained mobile systems
-  Robust ad-hoc networking techniques
-  Efficient localization techniques
-  Wireless sensor networks
-  Mobile peer to peer systems
-  Quality of service provisioning
-  Context-conscious computing
-  Web caching and services
-  Emerging applications and systems
-  Mobile agents
-  Mobile commerce
-  Security and privacy issues


Submission Guidelines
---------------------
Prospective authors should submit their paper electronically to
younis@csee.umbc.edu.  All papers are limited to 6 pages in MS-Word, PS
or PDF using standard IEEE double-column format. The first page should
include title, authors' contact information, an abstract and five
keywords. Authors should attach the paper abstract to their message.

Important Dates
---------------
Paper Submission Deadline:      March 15, 2005
Notification of Acceptance:     April 15, 2005
Camera-Ready Papers:            May 1, 2005

Symposium Co-Chairs
-------------------
Mohamed Younis
Department of Computer Science and Electrical Engineering
University of Maryland Baltimore County,
E-mail: younis@csee.umbc.edu

Hesham El-Rewini
Department of Computer Science and Engineering
Southern Methodist University
E-mail: rewini@engr.smu.edu


Publicity Chair
----------------
Moustafa Youssef
Department of Computer Science
University of Maryland at College Park,
E-mail: moustafa@cs.umd.edu



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


From avt-bounces@ietf.org  Thu Dec 23 05:50:59 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26372
	for <avt-archive@ietf.org>; Thu, 23 Dec 2004 05:50:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChQiO-0007B9-0A
	for avt-archive@ietf.org; Thu, 23 Dec 2004 06:01:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChQU8-0004g1-V4; Thu, 23 Dec 2004 05:46:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChQPD-0002ov-Cl; Thu, 23 Dec 2004 05:41:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25742;
	Thu, 23 Dec 2004 05:41:12 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChQYu-0006tP-B7; Thu, 23 Dec 2004 05:51:26 -0500
Received: from esealmw129.eemea.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBNAeYOi026235; Thu, 23 Dec 2004 11:41:03 +0100
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 23 Dec 2004 11:41:00 +0100
Received: from [153.88.8.195] ([153.88.8.195]) by esealmw127.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 23 Dec 2004 11:40:59 +0100
Message-ID: <41C9E759.8070807@ericsson.com>
Date: Wed, 22 Dec 2004 22:30:01 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>, rohc@ietf.org, mpls@ietf.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Dec 2004 10:40:59.0996 (UTC)
	FILETIME=[E45C69C0:01C4E8DB]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit
Subject: [AVT] Comments on draft-ash-avt-ecrtp-over-mpls-protocol-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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit

Hi,

Sorry for the crossposting, however this is something that I think needs
to be generally discussed between all 3 WGs. To me it looks like the
proposed solution for VoIP header compression across an MPLS network
contains a problematic demultiplexing mechanism. I don't think people 
has realized the issues with the proposed mechanism due to lack of 
communication between the header compression and MPLS folks. If it is my 
lack of knowledge please educate me, and the others. I would request 
that people providing input in this discussion is overly explaining as 
education seems necessary.

The current draft is available at:
http://www.watersprings.org/pub/id/draft-ash-avt-ecrtp-over-mpls-protocol-01.txt
it should also be available in the IETF repository if it hasn't expired.

The header compression mechanisms such as CRTP and ROHC to my 
understanding assumes that they have a lower link layer that carries 
their compressed messages between compressor and decompressor. This is 
due to that they are intended to be used with only a single link between 
the compressor and decompressor. In the case of CRTP, it also assumes 
that the link-layer can also provide the with identification of the 
packet types, while ROHC makes this identification internally.

The MPLS network uses one or more labels in the transport between 
ingress and egress from the MPLS network. Due to the possible relabeling 
in the middle of the network, it can't be generally assumed that packets 
arriving with the same label comes from the same ingress point. This 
makes the label not sufficient to identify the ingress for the egress, 
thus not making labels equal to a link.

The proposed solution has thought of the above MPLS problem and proposes 
that one uses the setup signalling to allow the decompressor point to 
select which parts of its context identifier (SCID) space that belongs 
to different ingress points that arrives over the same label. However my 
understanding is that this definitely not without problems for the 
header compression mechanisms. I would like the header compression guy 
to clarify what problems that would arise from such a solution. One 
thing I definitely can see would be an issue, the proposed change would 
prevent MPLS HC to use any standard implementation of the HC mechanism used.

I would also like to point out that the Header Compression mechanism 
needs a return path from the decompressor mechanism. However the draft 
does not seem to discuss this issue at all. Or is a MPLS label path 
automatically reversible?

It would be desirable if the MPLS people could consider if there exist 
other ways of providing for the standard assumption on link layers that 
header compression has? For these assumption please see chapter 2 of RFC 
2508, section 4.1 of RFC 3095, and RFC 3409.

For example, what would be the effects of requiring unique labels 
between ingress and egress and for the reverse path?

What effects would it have to put the multiplexing point in the layer 
two extension?

I would also like to see the draft be more header compression agnostic 
as has been agreed on in the requirements phase. There is no problem 
with using ECRTP as an example how one realize the solution, however the 
necessary hooks and signalling must be in place for any header 
compression mechanism.

So lets get the discussion going and hope that something good results.

Cheers

Magnus Westerlund
AVT Chair



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


From avt-bounces@ietf.org  Thu Dec 23 06:14:07 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27888
	for <avt-archive@ietf.org>; Thu, 23 Dec 2004 06:14:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChR4m-0007jz-1J
	for avt-archive@ietf.org; Thu, 23 Dec 2004 06:24:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChQgS-0007NY-43; Thu, 23 Dec 2004 05:59:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChQdZ-0006kL-37; Thu, 23 Dec 2004 05:56:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26900;
	Thu, 23 Dec 2004 05:56:02 -0500 (EST)
Received: from mail.riverstonenet.com ([63.113.148.10] helo=riverstonenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChQnF-0007IG-8Z; Thu, 23 Dec 2004 06:06:16 -0500
Received: from mgate1.riverstonenet.com by riverstonenet.com
	(8.9.3+Sun/SMI-SVR4-Yago)
	id CAA24022; Thu, 23 Dec 2004 02:55:21 -0800 (PST)
Received: (from daemon@localhost)
	by mgate1.riverstonenet.com (8.13.1/8.13.1) id iBNAtLSg007136;
	Thu, 23 Dec 2004 02:55:21 -0800 (PST)
X-Authentication-Warning: mgate1.riverstonenet.com: Processed by daemon with
	-C /etc/mail/sendmail-simple.cf
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by mgate1.riverstonenet.com (8.13.1/8.13.1) with ESMTP id
	iBNAtIqw007108; Thu, 23 Dec 2004 02:55:19 -0800 (PST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChQUA-0004hM-Sx; Thu, 23 Dec 2004 05:46:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChQPD-0002ov-Cl; Thu, 23 Dec 2004 05:41:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25742;
	Thu, 23 Dec 2004 05:41:12 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChQYu-0006tP-B7; Thu, 23 Dec 2004 05:51:26 -0500
Received: from esealmw129.eemea.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBNAeYOi026235; Thu, 23 Dec 2004 11:41:03 +0100
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 23 Dec 2004 11:41:00 +0100
Received: from [153.88.8.195] ([153.88.8.195]) by esealmw127.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 23 Dec 2004 11:40:59 +0100
Message-ID: <41C9E759.8070807@ericsson.com>
Date: Wed, 22 Dec 2004 22:30:01 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>, rohc@ietf.org, mpls@ietf.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Dec 2004 10:40:59.0996 (UTC)
	FILETIME=[E45C69C0:01C4E8DB]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Archive: <http://www1.ietf.org/pipermail/mpls>
X-Spam-Status: No, score=0.0 required=4.0 tests=none autolearn=failed 
	version=3.0.1
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on 
	mgate1.riverstonenet.com
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit
Subject: [AVT] [mpls] Comments on
	draft-ash-avt-ecrtp-over-mpls-protocol-01.txt
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: 7bit

Hi,

Sorry for the crossposting, however this is something that I think needs
to be generally discussed between all 3 WGs. To me it looks like the
proposed solution for VoIP header compression across an MPLS network
contains a problematic demultiplexing mechanism. I don't think people 
has realized the issues with the proposed mechanism due to lack of 
communication between the header compression and MPLS folks. If it is my 
lack of knowledge please educate me, and the others. I would request 
that people providing input in this discussion is overly explaining as 
education seems necessary.

The current draft is available at:
http://www.watersprings.org/pub/id/draft-ash-avt-ecrtp-over-mpls-protocol-01.txt
it should also be available in the IETF repository if it hasn't expired.

The header compression mechanisms such as CRTP and ROHC to my 
understanding assumes that they have a lower link layer that carries 
their compressed messages between compressor and decompressor. This is 
due to that they are intended to be used with only a single link between 
the compressor and decompressor. In the case of CRTP, it also assumes 
that the link-layer can also provide the with identification of the 
packet types, while ROHC makes this identification internally.

The MPLS network uses one or more labels in the transport between 
ingress and egress from the MPLS network. Due to the possible relabeling 
in the middle of the network, it can't be generally assumed that packets 
arriving with the same label comes from the same ingress point. This 
makes the label not sufficient to identify the ingress for the egress, 
thus not making labels equal to a link.

The proposed solution has thought of the above MPLS problem and proposes 
that one uses the setup signalling to allow the decompressor point to 
select which parts of its context identifier (SCID) space that belongs 
to different ingress points that arrives over the same label. However my 
understanding is that this definitely not without problems for the 
header compression mechanisms. I would like the header compression guy 
to clarify what problems that would arise from such a solution. One 
thing I definitely can see would be an issue, the proposed change would 
prevent MPLS HC to use any standard implementation of the HC mechanism used.

I would also like to point out that the Header Compression mechanism 
needs a return path from the decompressor mechanism. However the draft 
does not seem to discuss this issue at all. Or is a MPLS label path 
automatically reversible?

It would be desirable if the MPLS people could consider if there exist 
other ways of providing for the standard assumption on link layers that 
header compression has? For these assumption please see chapter 2 of RFC 
2508, section 4.1 of RFC 3095, and RFC 3409.

For example, what would be the effects of requiring unique labels 
between ingress and egress and for the reverse path?

What effects would it have to put the multiplexing point in the layer 
two extension?

I would also like to see the draft be more header compression agnostic 
as has been agreed on in the requirements phase. There is no problem 
with using ECRTP as an example how one realize the solution, however the 
necessary hooks and signalling must be in place for any header 
compression mechanism.

So lets get the discussion going and hope that something good results.

Cheers

Magnus Westerlund
AVT Chair



_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls

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


From avt-bounces@ietf.org  Thu Dec 23 06:16:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28096
	for <avt-archive@ietf.org>; Thu, 23 Dec 2004 06:16:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChR7K-0007oU-9U
	for avt-archive@ietf.org; Thu, 23 Dec 2004 06:26:50 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChQgV-0007P2-Df; Thu, 23 Dec 2004 05:59:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChQdk-0006ls-LM; Thu, 23 Dec 2004 05:56:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26929;
	Thu, 23 Dec 2004 05:56:13 -0500 (EST)
Received: from mail.riverstonenet.com ([63.113.148.10] helo=riverstonenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChQnR-0007Ij-IC; Thu, 23 Dec 2004 06:06:28 -0500
Received: from mgate1.riverstonenet.com by riverstonenet.com
	(8.9.3+Sun/SMI-SVR4-Yago)
	id CAA24043; Thu, 23 Dec 2004 02:55:34 -0800 (PST)
Received: (from daemon@localhost)
	by mgate1.riverstonenet.com (8.13.1/8.13.1) id iBNAtYkH007163;
	Thu, 23 Dec 2004 02:55:34 -0800 (PST)
X-Authentication-Warning: mgate1.riverstonenet.com: Processed by daemon with
	-C /etc/mail/sendmail-simple.cf
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by mgate1.riverstonenet.com (8.13.1/8.13.1) with ESMTP id
	iBNAtVqm007146; Thu, 23 Dec 2004 02:55:32 -0800 (PST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChQUA-0004hM-Ia; Thu, 23 Dec 2004 05:46:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChQPD-0002ov-Cl; Thu, 23 Dec 2004 05:41:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25742;
	Thu, 23 Dec 2004 05:41:12 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChQYu-0006tP-B7; Thu, 23 Dec 2004 05:51:26 -0500
Received: from esealmw129.eemea.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBNAeYOi026235; Thu, 23 Dec 2004 11:41:03 +0100
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 23 Dec 2004 11:41:00 +0100
Received: from [153.88.8.195] ([153.88.8.195]) by esealmw127.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 23 Dec 2004 11:40:59 +0100
Message-ID: <41C9E759.8070807@ericsson.com>
Date: Wed, 22 Dec 2004 22:30:01 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>, rohc@ietf.org, mpls@ietf.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Dec 2004 10:40:59.0996 (UTC)
	FILETIME=[E45C69C0:01C4E8DB]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Archive: <http://www1.ietf.org/pipermail/mpls>
X-Spam-Status: No, score=0.0 required=4.0 tests=none autolearn=failed 
	version=3.0.1
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on 
	mgate1.riverstonenet.com
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit
Subject: [AVT] [mpls] Comments on
	draft-ash-avt-ecrtp-over-mpls-protocol-01.txt
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: 7bit

Hi,

Sorry for the crossposting, however this is something that I think needs
to be generally discussed between all 3 WGs. To me it looks like the
proposed solution for VoIP header compression across an MPLS network
contains a problematic demultiplexing mechanism. I don't think people 
has realized the issues with the proposed mechanism due to lack of 
communication between the header compression and MPLS folks. If it is my 
lack of knowledge please educate me, and the others. I would request 
that people providing input in this discussion is overly explaining as 
education seems necessary.

The current draft is available at:
http://www.watersprings.org/pub/id/draft-ash-avt-ecrtp-over-mpls-protocol-01.txt
it should also be available in the IETF repository if it hasn't expired.

The header compression mechanisms such as CRTP and ROHC to my 
understanding assumes that they have a lower link layer that carries 
their compressed messages between compressor and decompressor. This is 
due to that they are intended to be used with only a single link between 
the compressor and decompressor. In the case of CRTP, it also assumes 
that the link-layer can also provide the with identification of the 
packet types, while ROHC makes this identification internally.

The MPLS network uses one or more labels in the transport between 
ingress and egress from the MPLS network. Due to the possible relabeling 
in the middle of the network, it can't be generally assumed that packets 
arriving with the same label comes from the same ingress point. This 
makes the label not sufficient to identify the ingress for the egress, 
thus not making labels equal to a link.

The proposed solution has thought of the above MPLS problem and proposes 
that one uses the setup signalling to allow the decompressor point to 
select which parts of its context identifier (SCID) space that belongs 
to different ingress points that arrives over the same label. However my 
understanding is that this definitely not without problems for the 
header compression mechanisms. I would like the header compression guy 
to clarify what problems that would arise from such a solution. One 
thing I definitely can see would be an issue, the proposed change would 
prevent MPLS HC to use any standard implementation of the HC mechanism used.

I would also like to point out that the Header Compression mechanism 
needs a return path from the decompressor mechanism. However the draft 
does not seem to discuss this issue at all. Or is a MPLS label path 
automatically reversible?

It would be desirable if the MPLS people could consider if there exist 
other ways of providing for the standard assumption on link layers that 
header compression has? For these assumption please see chapter 2 of RFC 
2508, section 4.1 of RFC 3095, and RFC 3409.

For example, what would be the effects of requiring unique labels 
between ingress and egress and for the reverse path?

What effects would it have to put the multiplexing point in the layer 
two extension?

I would also like to see the draft be more header compression agnostic 
as has been agreed on in the requirements phase. There is no problem 
with using ECRTP as an example how one realize the solution, however the 
necessary hooks and signalling must be in place for any header 
compression mechanism.

So lets get the discussion going and hope that something good results.

Cheers

Magnus Westerlund
AVT Chair



_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls

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


From avt-bounces@ietf.org  Thu Dec 23 09:43:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12111
	for <avt-archive@ietf.org>; Thu, 23 Dec 2004 09:43:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChULS-0004oA-7h
	for avt-archive@ietf.org; Thu, 23 Dec 2004 09:53:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChU9V-0007tR-Eb; Thu, 23 Dec 2004 09:41:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChU7N-0007Kj-Qx; Thu, 23 Dec 2004 09:39:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11812;
	Thu, 23 Dec 2004 09:39:03 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChUHH-0004hu-Lj; Thu, 23 Dec 2004 09:49:19 -0500
Received: from apache by megatron.ietf.org with local (Exim 4.32)
	id 1ChU1p-0006L6-LL; Thu, 23 Dec 2004 09:33:21 -0500
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1ChU1p-0006L6-LL@megatron.ietf.org>
Date: Thu, 23 Dec 2004 09:33:21 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: avt@ietf.org
Subject: [AVT] Last Call: 'RTP Payload Format for Uncompressed Video' to
 Proposed Standard 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f

The IESG has received a request from the Audio/Video Transport WG to consider 
the following document:

- 'RTP Payload Format for Uncompressed Video '
   <draft-ietf-avt-uncomp-video-06.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2005-01-13.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-avt-uncomp-video-06.txt


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


From avt-bounces@ietf.org  Thu Dec 23 15:39:11 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18531
	for <avt-archive@ietf.org>; Thu, 23 Dec 2004 15:39:11 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChZtq-0006fr-Em
	for avt-archive@ietf.org; Thu, 23 Dec 2004 15:49:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChZZK-0004W1-FR; Thu, 23 Dec 2004 15:28:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChZXP-0003HD-P3; Thu, 23 Dec 2004 15:26:19 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17532;
	Thu, 23 Dec 2004 15:26:17 -0500 (EST)
Message-Id: <200412232026.PAA17532@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 23 Dec 2004 15:26:17 -0500
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-3gpp-timed-text-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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e

--NextPart

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

	Title		: RTP Payload Format for 3GPP Timed Text
	Author(s)	: J. Rey, Y. Matsui
	Filename	: draft-ietf-avt-rtp-3gpp-timed-text-08.txt
	Pages		: 58
	Date		: 2004-12-23
	
This document specifies an RTP payload format for the transmission of 
3GPP (3rd Generation Partnership Project) timed text.  3GPP timed 
text is a time-lined decorated text media format with defined storage 
in a 3GP file.  Timed Text can be synchronised with audio/video 
contents.  As of today, 3GP files containing timed text contents can 
only be downloaded via HTTP.  There is no available mechanism for 
streaming 3GPP timed text contents neither out of 3GP files nor 
directly from live content.  In the following sections the problems 
of streaming timed text are addressed and a payload format for 
streaming 3GPP timed text over RTP is specified.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-3gpp-timed-text-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-rtp-3gpp-timed-text-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-rtp-3gpp-timed-text-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: <2004-12-23124603.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-3gpp-timed-text-08.txt

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

Content-Type: text/plain
Content-ID: <2004-12-23124603.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org  Tue Dec 28 00:10:41 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09032
	for <avt-archive@ietf.org>; Tue, 28 Dec 2004 00:10:41 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cj9nv-0006c7-GP
	for avt-archive@ietf.org; Tue, 28 Dec 2004 00:21:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cj9Q1-0001ET-Ta; Mon, 27 Dec 2004 23:57:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cj9M3-0008VC-Le
	for avt@megatron.ietf.org; Mon, 27 Dec 2004 23:53:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07919
	for <avt@ietf.org>; Mon, 27 Dec 2004 23:53:05 -0500 (EST)
Received: from relay0.eecs.berkeley.edu ([169.229.60.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cj9Wt-0006CL-QY
	for avt@ietf.org; Tue, 28 Dec 2004 00:04:20 -0500
Received: from gateway2.EECS (gateway2.EECS.Berkeley.EDU [169.229.60.39])
	by relay0.EECS.Berkeley.EDU (8.13.2/8.12.10) with ESMTP id
	iBS4r5tt023010
	for <avt@ietf.org>; Mon, 27 Dec 2004 20:53:05 -0800 (PST)
Received: from [128.32.34.73] (dhcp-34-73.CS.Berkeley.EDU [128.32.34.73])
	by gateway2.EECS.Berkeley.EDU
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTPSA id <0I9F004KG1KHQW@gateway2.EECS.Berkeley.EDU> for
	avt@ietf.org; Mon, 27 Dec 2004 20:53:05 -0800 (PST)
Date: Mon, 27 Dec 2004 20:53:04 -0800
From: lazzaro <lazzaro@eecs.berkeley.edu>
Subject: RE: [AVT] Working group last call: MIDI Payload Format and
	Implementation Guide
To: avt@ietf.org
Message-id: <5C1D3842-588C-11D9-816E-00039372C384@eecs.berkeley.edu>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7BIT
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 7BIT

Colin Perkins <csp@csperkins.org> writes:
> This is to announce a working group last call on the RTP Payload  
> Format for MIDI and the associated implementation guide:
>
> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-midi-format 
> -07.txt
> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-midi- 
> guidelines-07.txt
>
> Please send any final comments on these drafts to the <avt@ietf.org>  
> mailing list by 10th January 2005.

Spent a few weeks updating the sfront code base to reflect the normative
changes in RTP MIDI that appear in -05/-06/-07.txt.  Found one bug in  
-07.txt,
so there will be a -08.txt released after WG Last Call and before IETF  
Last Call.
(which will also include any changes necessitated by the WG Last Call  
responses).
Here is the change log entry for the bug that will appear in -08.txt:

---

[1] The normative text for computing the A-BUTTON and C-BUTTON fields
(Appendix A.4.2.1) has been slightly changed.  The -07.txt read:

    To compute and code the count value, initialize the count value to 0,
    add 1 for each qualifying Data Increment command, subtract 1 for each
    qualifying Data Decrement command, and limit the magnitude of the
    final count to 16383.

The revised text in -08.txt:

   To compute and code the count value, initialize the count value to 0,
   add 1 for each qualifying Data Increment command, and subtract 1 for
   each qualifying Data Decrement command.  After each add or subtract,
   limit the count magnitude to 16383.

---

In other news, there is now an RTP MIDI web page:

http://www.cs.berkeley.edu/~lazzaro/rtpmidi/index.html

The "To Learn More" section on the right has links to the code, papers,  
and
my local mirrors of the I-Ds.

---
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  Tue Dec 28 05:43:12 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13569
	for <avt-archive@ietf.org>; Tue, 28 Dec 2004 05:43:11 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjEzm-0006Ae-6v
	for avt-archive@ietf.org; Tue, 28 Dec 2004 05:54:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjEn4-0004Y3-Nm; Tue, 28 Dec 2004 05:41:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjEis-0003fY-9B
	for avt@megatron.ietf.org; Tue, 28 Dec 2004 05:37:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13229
	for <avt@ietf.org>; Tue, 28 Dec 2004 05:36:59 -0500 (EST)
Received: from web8203.mail.in.yahoo.com ([202.43.219.113])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CjEtk-00060a-OX
	for avt@ietf.org; Tue, 28 Dec 2004 05:48:18 -0500
Received: (qmail 85017 invoked by uid 60001); 28 Dec 2004 10:36:27 -0000
Message-ID: <20041228103627.85015.qmail@web8203.mail.in.yahoo.com>
Received: from [203.129.220.115] by web8203.mail.in.yahoo.com via HTTP;
	Tue, 28 Dec 2004 10:36:27 GMT
Date: Tue, 28 Dec 2004 10:36:27 +0000 (GMT)
From: rahul agrawal <voipthesis@yahoo.co.in>
To: avt@ietf.org
MIME-Version: 1.0
X-Spam-Score: 1.8 (+)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Subject: [AVT] Happy new year 
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="===============1458812753=="
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 1.8 (+)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69

--===============1458812753==
Content-Type: multipart/alternative; boundary="0-2116589248-1104230187=:84657"

--0-2116589248-1104230187=:84657
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

hi
wishing all, a  very happy new year, have all the happiness, success, life, & e...................................................................verything that everybody desired .
have a great time & year ahead
( with lots of best wishes)

 
 

		
---------------------------------
Do you Yahoo!?
 Yahoo! Mail - Easier than ever with enhanced search. Learn more.
--0-2116589248-1104230187=:84657
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<DIV>hi<BR>wishing&nbsp;all, a &nbsp;very happy new year, have all the happiness, success, life, &amp; e...................................................................verything that everybody desired .<BR>have a great time &amp; year ahead<BR>( with lots of best wishes)<BR></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV><p>
		<hr size=1>Do you Yahoo!?<br> 
Yahoo! Mail - Easier than ever with enhanced search. <a href="http://us.rd.yahoo.com/evt=29916/*http://info.mail.yahoo.com/mail_250">Learn more.</a>
--0-2116589248-1104230187=:84657--


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

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

--===============1458812753==--



From avt-bounces@ietf.org  Tue Dec 28 05:51:04 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14001
	for <avt-archive@ietf.org>; Tue, 28 Dec 2004 05:51:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjF7P-0006Lc-GG
	for avt-archive@ietf.org; Tue, 28 Dec 2004 06:02:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjEn6-0004YC-Gk; Tue, 28 Dec 2004 05:41:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjEjR-0003il-Qd
	for avt@megatron.ietf.org; Tue, 28 Dec 2004 05:37:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13246
	for <avt@ietf.org>; Tue, 28 Dec 2004 05:37:34 -0500 (EST)
Received: from web8206.mail.in.yahoo.com ([202.43.219.116])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CjEuJ-00062m-TT
	for avt@ietf.org; Tue, 28 Dec 2004 05:48:53 -0500
Received: (qmail 95487 invoked by uid 60001); 28 Dec 2004 10:37:03 -0000
Message-ID: <20041228103702.95485.qmail@web8206.mail.in.yahoo.com>
Received: from [203.129.220.115] by web8206.mail.in.yahoo.com via HTTP;
	Tue, 28 Dec 2004 10:37:02 GMT
Date: Tue, 28 Dec 2004 10:37:02 +0000 (GMT)
From: rahul agrawal <voipthesis@yahoo.co.in>
To: avt@ietf.org
MIME-Version: 1.0
X-Spam-Score: 2.3 (++)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Subject: [AVT] need help @sourcecodec(iLBC)
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="===============1163354466=="
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5

--===============1163354466==
Content-Type: multipart/alternative; boundary="0-509055904-1104230222=:95054"

--0-509055904-1104230222=:95054
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Please, help me.
                         i  get source codec (iLBC) from IETE site, but 
when i go to run it then some problem occur. it having many modules, so 
pls tell me that how should i run it, give me method to run this 
program.
 
 
one more query is that how coeffiecients vary in CELP, that is what is 
main criteria to change reflection coeffiecients of code book .
 
 
rahul agrawal
M.Tech (ELECTRONICS)
 
 


		
---------------------------------
Do you Yahoo!?
 Take Yahoo! Mail with you! Get it on your mobile phone.
--0-509055904-1104230222=:95054
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<DIV>
<DIV>Please, help me.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; i&nbsp; get source codec (iLBC) from IETE site, but <BR>when i go to run it then some problem occur. it having many modules, so <BR>pls tell me that how should i run it, give me method to run this <BR>program.<BR>&nbsp;<BR>&nbsp;<BR>one more query is that how coeffiecients vary in CELP, that is what is <BR>main criteria to change reflection coeffiecients of code book .<BR>&nbsp;<BR>&nbsp;<BR>rahul agrawal<BR>M.Tech (ELECTRONICS)</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></DIV><p>
		<hr size=1>Do you Yahoo!?<br> 
<a href="http://us.rd.yahoo.com/mail_us/taglines/mobile/*http://mobile.yahoo.com/maildemo">Take Yahoo! Mail with you!</a> Get it on your mobile phone.
--0-509055904-1104230222=:95054--


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

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

--===============1163354466==--



From avt-bounces@ietf.org  Tue Dec 28 08:25:37 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25700
	for <avt-archive@ietf.org>; Tue, 28 Dec 2004 08:25:37 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjHWx-00027h-N9
	for avt-archive@ietf.org; Tue, 28 Dec 2004 08:36:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjHHn-00072c-KN; Tue, 28 Dec 2004 08:21:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjHCW-0005dj-Om
	for avt@megatron.ietf.org; Tue, 28 Dec 2004 08:15:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24702
	for <avt@ietf.org>; Tue, 28 Dec 2004 08:15:47 -0500 (EST)
Received: from wproxy.gmail.com ([64.233.184.205])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjHNQ-0001qJ-SO
	for avt@ietf.org; Tue, 28 Dec 2004 08:27:06 -0500
Received: by wproxy.gmail.com with SMTP id 69so670294wri
	for <avt@ietf.org>; Tue, 28 Dec 2004 05:15:16 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding;
	b=jHlwiiloP5/4OVJlaAl9p8w8lkwkpTjdPj354FSRx/No9bqjqabao41NqAiZd2SEUuFwOjCl8rAxkIJzcBr9z8qyG5ooeJJ2vGvT9z3AjNmGKoIIszeTIwsuwD4/WBkDG+5PkHwbanXx6/0BKRlx4pprPT+4WkVvpr2jyBjXUUw=
Received: by 10.54.54.8 with SMTP id c8mr112095wra;
	Tue, 28 Dec 2004 05:15:16 -0800 (PST)
Received: by 10.54.46.55 with HTTP; Tue, 28 Dec 2004 05:15:16 -0800 (PST)
Message-ID: <6e5aff670412280515556e530d@mail.gmail.com>
Date: Tue, 28 Dec 2004 10:15:16 -0300
From: Alejandro Cabrera Obed <aco1967@gmail.com>
To: AVT Lista <avt@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
Subject: [AVT] Measure of network congestion
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Alejandro Cabrera Obed <aco1967@gmail.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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit

Dear People,

Suppose I'll develop an application of HDTV uncompressed on Internet2. 
Suppose I say the app will run only if the network congestion state is
appropriate (i.e., packet loss < 1%).
Suppose I'll use IPERF to measure the packet loss in order to take the
decision to run or not the app.

So, IPERF will measure the packet loss over a given path of the
network, but suppose once I run the app this network path change and
packet loss is greater than 1%.....I ask you: Is it possible to get a
measurement of packet loss with IPERF along all the possible paths of
the end-to-end video connection ??? Otherwise, is it correct to
measure the packet loss along one network path and then affect this
value with a given deviation coeficient I get through several
measurements ???

Thanks and happy new year to you !!!!

Alejandro Cabrera Obed

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


From avt-bounces@ietf.org  Tue Dec 28 13:08:57 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14426
	for <avt-archive@ietf.org>; Tue, 28 Dec 2004 13:08:57 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjLxD-0000o7-DJ
	for avt-archive@ietf.org; Tue, 28 Dec 2004 13:20:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjLjq-00073H-IH; Tue, 28 Dec 2004 13:06:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjLdN-0005xD-Hb
	for avt@megatron.ietf.org; Tue, 28 Dec 2004 12:59:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13685
	for <avt@ietf.org>; Tue, 28 Dec 2004 12:59:46 -0500 (EST)
Received: from ondar.cablelabs.com ([192.160.73.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjLoL-0000Yt-07
	for avt@ietf.org; Tue, 28 Dec 2004 13:11:09 -0500
Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20])
	by ondar.cablelabs.com (8.12.10/8.12.10) with ESMTP id iBSHxE1e021023
	for <avt@ietf.org>; Tue, 28 Dec 2004 10:59:14 -0700 (MST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: [AVT] rfc3611voip, RTP XR packet decoding in open source Ethereal
Date: Tue, 28 Dec 2004 10:59:14 -0700
Message-ID: <CD6CE349CFD30D40BF5E13B3E0D84804064389@srvxchg.cablelabs.com>
Thread-Topic: [AVT] rfc3611voip, RTP XR packet decoding in open source Ethereal
Thread-Index: AcToOH+9+CD6xfecTie10o893EMF5gAD6p7A
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: <avt@ietf.org>
X-Approved: ondar
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: quoted-printable
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: quoted-printable

Hi,

   I'm curious to know if some folks are interested in contributing to a
software development effort to add RTCP XR decoders to the open source
packet capture tool Ethereal (http://www.ethereal.com). Has anyone
started? Does anyone intend to submit some code to the main Ethereal
distribution soon?

Let me know asap, thanks,=20
Jean-Francois

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


From avt-bounces@ietf.org  Tue Dec 28 21:27:38 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24234
	for <avt-archive@ietf.org>; Tue, 28 Dec 2004 21:27:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjTjr-0006gz-MU
	for avt-archive@ietf.org; Tue, 28 Dec 2004 21:39:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjTSv-0001ii-2H; Tue, 28 Dec 2004 21:21:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjTN2-0000Og-Hr
	for avt@megatron.ietf.org; Tue, 28 Dec 2004 21:15:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22991
	for <avt@ietf.org>; Tue, 28 Dec 2004 21:15:26 -0500 (EST)
Received: from mx.cbeyond.net ([66.180.96.58] helo=mx.cbeyond.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjTY4-0006NC-E9
	for avt@ietf.org; Tue, 28 Dec 2004 21:26:52 -0500
Received: from [68.217.6.127] (port=1111 helo=telws116)
	by mx.cbeyond.com with asmtp (Exim 4.34)
	id 1CjTMt-0001D9-2p; Tue, 28 Dec 2004 21:15:19 -0500
From: "Alan Clark" <alan.d.clark@telchemy.com>
To: "Jean-Francois Mule" <jf.mule@cablelabs.com>, <avt@ietf.org>
Subject: RE: [AVT] rfc3611voip, RTP XR packet decoding in open source Ethereal
Date: Tue, 28 Dec 2004 21:15:29 -0500
Message-ID: <BGEKJNNFCPJKLLMMDMELKECBGBAA.alan.d.clark@telchemy.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
In-Reply-To: <CD6CE349CFD30D40BF5E13B3E0D84804064389@srvxchg.cablelabs.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit

Jean-Francois

I added this to the Ethereal Wiki list - that may also elicit a response.

Regards

Alan Clark


-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]On Behalf Of
Jean-Francois Mule
Sent: Tuesday, December 28, 2004 12:59 PM
To: avt@ietf.org
Subject: [AVT] rfc3611voip, RTP XR packet decoding in open source
Ethereal


Hi,

   I'm curious to know if some folks are interested in contributing to a
software development effort to add RTCP XR decoders to the open source
packet capture tool Ethereal (http://www.ethereal.com). Has anyone
started? Does anyone intend to submit some code to the main Ethereal
distribution soon?

Let me know asap, thanks, 
Jean-Francois

_______________________________________________
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 Dec 29 14:48:15 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04759
	for <avt-archive@ietf.org>; Wed, 29 Dec 2004 14:48:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cjjz3-0007BZ-VN
	for avt-archive@ietf.org; Wed, 29 Dec 2004 14:59:50 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cjji8-0003sf-RX; Wed, 29 Dec 2004 14:42:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjjfM-00031b-V1
	for avt@megatron.ietf.org; Wed, 29 Dec 2004 14:39:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04313
	for <avt@ietf.org>; Wed, 29 Dec 2004 14:39:27 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjjqX-0006zn-Av for avt@ietf.org; Wed, 29 Dec 2004 14:51:02 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 29 Dec 2004 11:45:43 -0800
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iBTJcqQS008146;
	Wed, 29 Dec 2004 11:38:52 -0800 (PST)
Received: from [10.32.245.152] (stealth-10-32-245-152.cisco.com
	[10.32.245.152])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id iBTJadGQ012167;
	Wed, 29 Dec 2004 11:36:39 -0800
In-Reply-To: <6e5aff670412280515556e530d@mail.gmail.com>
References: <6e5aff670412280515556e530d@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <42B5EF66-59D1-11D9-95E0-000A95C73842@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [AVT] Measure of network congestion
Date: Wed, 29 Dec 2004 14:38:48 -0500
To: Alejandro Cabrera Obed <aco1967@gmail.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1104348999.943430"; x:"432200"; a:"rsa-sha1"; b:"nofws:1724";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"QP5b2NeX2j6vp/gKL2zYAtr+SW47HAS96ICfp0HP+5oey0fKbFYiOG+oCrAF3"
	"h/I06xd0Kdvwfs36/kZlh1p9L5EC/BY0F8xEZE1AlkbzXlMFZx96YJKfyf6bp"
	"yRQJto5+eDvAkv8K4l8AdmrBkWksbKzKnnq74VdBJ/jDCHdcc=";
	c:"From: David R Oran <oran@cisco.com>";
	c:"Subject: Re: [AVT] Measure of network congestion";
	c:"Date: Wed, 29 Dec 2004 14:38:48 -0500"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
Cc: AVT Lista <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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit


On Dec 28, 2004, at 8:15 AM, Alejandro Cabrera Obed wrote:

> Dear People,
>
> Suppose I'll develop an application of HDTV uncompressed on Internet2.
> Suppose I say the app will run only if the network congestion state is
> appropriate (i.e., packet loss < 1%).
> Suppose I'll use IPERF to measure the packet loss in order to take the
> decision to run or not the app.
>
Why not run the app and have it generate the synthetic load and observe 
the RTCP feedback to decide whether to bother with the "important" 
bits? One danger with probes tis that they fail to mimic the real 
traffic with enough fidelity.

> So, IPERF will measure the packet loss over a given path of the
> network, but suppose once I run the app this network path change and
> packet loss is greater than 1%.....I ask you: Is it possible to get a
> measurement of packet loss with IPERF along all the possible paths of
> the end-to-end video connection ???
You realize that the number of possible paths is exponential in the 
number of links in the network, don't you?

> Otherwise, is it correct to
> measure the packet loss along one network path and then affect this
> value with a given deviation coeficient I get through several
> measurements ???
>
to the extent that the load and topology are stable, yes. But the 
interesting cases are when it's not.
> Thanks and happy new year to you !!!!
>
> Alejandro Cabrera Obed
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>
David R. Oran
Cisco Fellow
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720 USA
Tel: +1 978 264 2048
Email: oran@cisco.com

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


From avt-bounces@ietf.org  Wed Dec 29 15:51:32 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10315
	for <avt-archive@ietf.org>; Wed, 29 Dec 2004 15:51:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjkyJ-0000Ce-UY
	for avt-archive@ietf.org; Wed, 29 Dec 2004 16:03:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cjkj7-0005rc-5v; Wed, 29 Dec 2004 15:47:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjkY7-0001YD-Nf; Wed, 29 Dec 2004 15:36:03 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08914;
	Wed, 29 Dec 2004 15:36:01 -0500 (EST)
Message-Id: <200412292036.PAA08914@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 29 Dec 2004 15:36:01 -0500
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-ac3-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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db

--NextPart

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

	Title		: RTP Payload Format for AC-3 Streams
	Author(s)	: J. Flaks, et al.
	Filename	: draft-ietf-avt-rtp-ac3-01.txt
	Pages		: 9
	Date		: 2004-12-29
	
This document describes an RTP payload format for transporting AC-3 
encoded audio data.  AC-3 is a high quality, multichannel audio coding 
system used in US HDTV, DVD, cable and satellite television and other 
media.  The RTP payload format as presented in this document includes 
support for data fragmentation.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-ac3-01.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-ac3-01.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-ac3-01.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: <2004-12-29153920.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-ac3-01.txt

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

Content-Type: text/plain
Content-ID: <2004-12-29153920.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org  Wed Dec 29 15:57:44 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11067
	for <avt-archive@ietf.org>; Wed, 29 Dec 2004 15:57:44 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cjl4K-0000SR-IX
	for avt-archive@ietf.org; Wed, 29 Dec 2004 16:09:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjkjC-0005vO-5t; Wed, 29 Dec 2004 15:47:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjkYV-0004Qb-73; Wed, 29 Dec 2004 15:36:27 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08937;
	Wed, 29 Dec 2004 15:36:25 -0500 (EST)
Message-Id: <200412292036.PAA08937@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 29 Dec 2004 15:36:25 -0500
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-jpeg2000-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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86

--NextPart

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

	Title		: RTP Payload Format for JPEG 2000 Video Streams
	Author(s)	: S. Futemma, et al.
	Filename	: draft-ietf-avt-rtp-jpeg2000-07.txt
	Pages		: 22
	Date		: 2004-12-29
	
This memo describes an RTP payload format for the ISO/IEC
    International Standard 15444-1 | ITU-T Rec. T.800, JPEG 2000.
    JPEG 2000 features are considered and there are provisions in this
    payload format for scalability, prioritization of different parts
    of the codestream, and error recovery. JPEG 2000 is a truly
    scalable compression technology allowing applications to encode one
    way and decode many different ways. Extending from one image to a
    series of JPEG 2000 images, one has a JPEG 2000 video stream.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-jpeg2000-07.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-jpeg2000-07.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-jpeg2000-07.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: <2004-12-29153936.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-jpeg2000-07.txt

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

Content-Type: text/plain
Content-ID: <2004-12-29153936.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org  Thu Dec 30 15:41:52 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14774
	for <avt-archive@ietf.org>; Thu, 30 Dec 2004 15:41:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ck7Ij-0002bb-AG
	for avt-archive@ietf.org; Thu, 30 Dec 2004 15:53:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ck73y-0000N0-13; Thu, 30 Dec 2004 15:38:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ck6wp-0005MQ-AO; Thu, 30 Dec 2004 15:31:03 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14259;
	Thu, 30 Dec 2004 15:31:01 -0500 (EST)
Message-Id: <200412302031.PAA14259@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 30 Dec 2004 15:31:01 -0500
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rfc2429-bis-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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87

--NextPart

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

	Title		: RTP Payload Format for the 1998 Version of ITU-T 
			  Rec. H.263 Video (H.263+)
	Author(s)	: J. Ott, et al.
	Filename	: draft-ietf-avt-rfc2429-bis-04.txt
	Pages		: 33
	Date		: 2004-12-30
	
This document describes a scheme to packetize an H.263 video stream
for transport using the Real-time Transport Protocol, RTP, with any
of the underlying protocols that carry RTP.

The document also describe the syntax and semantics of the SDP
parameters needed to support the H.263 video codec.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc2429-bis-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-rfc2429-bis-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-rfc2429-bis-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: <2004-12-30144304.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rfc2429-bis-04.txt

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

Content-Type: text/plain
Content-ID: <2004-12-30144304.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





