From avt-bounces@ietf.org Mon Jul 02 02:32:15 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5FS7-0004md-GL; Mon, 02 Jul 2007 02:32:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5FS6-0004mU-Lv
	for avt@ietf.org; Mon, 02 Jul 2007 02:32:02 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5FS2-0006ec-6a
	for avt@ietf.org; Mon, 02 Jul 2007 02:32:02 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 2 Jul 2007 09:33:11 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04AFCE9A@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AVT WG meeting in Chicago - Time slot requests - fixed typo
Thread-Index: Ace6G5kUXPewTIUmSEOal7jbUHOgDQ==
From: "Even, Roni" <roni.even@polycom.co.il>
To: <avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: tom.taylor@rogers.com, Colin Perkins <csp@csperkins.org>
Subject: [AVT] AVT WG meeting in Chicago - Time slot requests - fixed typo
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi,

If you wish to have agenda time at the upcoming meeting in Chicago, =
please send an agenda request to the chairs, but no later than July 9th.

We have requested two time slots:
1. Monday July 23rd 15:20-17:20
2. Thursday July 26st 15.10-16.10=20

Please note that those times are not final and may change. The final =
agenda for the meeting will; be published on July 2nd.



This meeting time is intended for the following:

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

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

A. Presentation Title:

B. Name of presenter:

C. Draft Reference(s):

D. Requested amount of time in minutes:




Thanks
Roni Even

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



From avt-bounces@ietf.org Mon Jul 02 11:29:03 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5NpW-0002K2-R5; Mon, 02 Jul 2007 11:28:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5NpU-0002D4-Ij
	for avt@ietf.org; Mon, 02 Jul 2007 11:28:44 -0400
Received: from [2001:630:241:204:203:baff:fe9a:8c9b] (helo=erg.abdn.ac.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5NoV-0005wu-4Y
	for avt@ietf.org; Mon, 02 Jul 2007 11:28:44 -0400
Received: from [139.133.204.42] (ra-gorry.erg.abdn.ac.uk [139.133.204.42])
	(authenticated bits=0)
	by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id l62FPa14006492
	(version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT);
	Mon, 2 Jul 2007 16:25:39 +0100 (BST)
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Mon, 02 Jul 2007 17:25:36 +0200
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
To: <avt@ietf.org>
Message-ID: <C2AEE590.7492%gorry@erg.abdn.ac.uk>
Thread-Topic: Comments on draft-ietf-avt-tfrc-profile-08.txt
Thread-Index: Ace8vTzne1wz8SiwEdy+OgAKlc/qXg==
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-Spam-Status: No
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: gorry@erg.abdn.ac.uk
Subject: [AVT] Comments on draft-ietf-avt-tfrc-profile-08.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org


Ladan

I enclose some comments after reading your latest rev of
draft-ietf-avt-tfrc-profile.  These comments concern questions on RFC
keywords, and some other queries. I will send editorial comments separately.
 
Please do keep me in the loop on further revisions, I'd be happy to read.
 
 Best wishes,
 
 Gorry Fairhurst

----

Questions: 
Section 7., paragraph 3:
OLD:
    Based on initial assumptions on round trip time if more than the
    recommended 5% is needed for RTCP bandwidth, the applications should
    use the SDP bandwidth modifiers RS and RR [3556] to signal the amount
    of RTCP bandwidth needed. Should this assumptions change once the RTP
    flows are running, the application can recalculate the amount of RTCP
    bandwidth needed and resignal this new value using its signaling
    protocol of choice.
= The phrase "should take into account" needs some clarification
(a) Is this a RFC2119 "SHOULD"?
(b) Please clarify "take into account", what does this imply, is it just a
matter of increasing the advertised bandwidth value?
 
- The phrase "should use the SDP bandwidth modifiers RS and RR"
Is this a RFC2119 "SHOULD"?

Section 7.

- The phrase "the application can recalculate the amount of RTCP bandwidth"
- Is this a RFC2119 "MAY" or "SHOULD"

Section 8., paragraph 0:
- The phrase: "the AVPF T_rr_interval variable must not be set"
- Is this a RFC2119 "MUST NOT"?


Section 8., paragraph 2:
- The phrase: "must signal their use of the AVPF profile"
- Is this a RFC2119 "MUST"?
 
- The phrase: "and optionally an initial"
-  Consider changing to "and optionally MAY sends an initial"

Please add (informative) References:

 [RFC4336] Floyd, S., Handley, M., and E. Kohler, "Problem Statement for the
Datagram Congestion Control Protocol (DCCP)", RFC 4336, March 2006.
 
 [RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram Congestion
Control Protocol (DCCP)", RFC 4340, March 2006.
 
 [RFC4341] Floyd, S. and E. Kohler, "Profile for Datagram Congestion Control
Protocol (DCCP) Congestion Control ID 2: TCP-like Congestion Control", RFC
4341, March 2006.
 
 [RFC4342]  Floyd, S., Kohler, E., and J. Padhye, "Profile for Datagram
Congestion Control Protocol (DCCP) Congestion Control ID 3: TCP-Friendly
Rate Control (TFRC)", RFC 4342, March 2006.
 
 [RFCxRTP] C. Perkins, "RTP and the Datagram Congestion Control
          Protocol (DCCP)", IETF Work in Progress, draft-ietf-dccp-
          rtp-xx.txt.
 
 [ID.DTLS] T.Phelan, "Datagram Transport Layer Security (DTLS)
          over the Datagram Congestion Control Protocol (DCCP)", IETF
          Work in Progress, draft-phelan-dccp-dtls-xx.txt.

---




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



From avt-bounces@ietf.org Mon Jul 02 12:58:27 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5PED-0003OA-Vt; Mon, 02 Jul 2007 12:58:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5PEC-0003O5-5w
	for avt@ietf.org; Mon, 02 Jul 2007 12:58:20 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5PE1-0007IZ-VA
	for avt@ietf.org; Mon, 02 Jul 2007 12:58:20 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:56950)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1I5PE0-0006NC-6Z; Mon, 02 Jul 2007 17:58:08 +0100
In-Reply-To: <4680C859.8050900@ericsson.com>
References: <7634542FB03DC747813D67560802AEED9EB379@rennsmail05.eu.thmulti.com>
	<465D8C51.4080805@ericsson.com>
	<p06240817c28360afcce1@[17.202.35.52]>
	<465E8514.9080503@ericsson.com> <4666DD9A.4161A698@erols.com>
	<p06240887c28f9648fa12@[17.202.35.52]>
	<61DDFB8A-8EA0-4F26-9610-9FCA7FD3633C@csperkins.org>
	<46757295.C62C43BF@erols.com> <46767822.1060308@ericsson.com>
	<p06240843c29d41cb741b@[17.202.35.52]>
	<46779487.5060308@ericsson.com>
	<85FF4F5B-138E-4788-8009-515DD4C17EBF@csperkins.org>
	<4680C859.8050900@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <56F5C792-E7D8-4BA3-BA95-237AE487D937@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Working group last call: JPEG-2000 payload format
Date: Mon, 2 Jul 2007 17:58:09 +0100
To: Satoshi Futemma <satosi-f@sm.sony.co.jp>,
	Andrew Leung <andrew@ualberta.net>,
	ITAKURA Eisaburo <itakura@sm.sony.co.jp>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On 26 Jun 2007, at 09:03, Magnus Westerlund wrote:
> Colin Perkins skrev:
>> Wrapping up, I believe the rough consensus is that the JPEG-2000  
>> draft should be updated to allow non-90kHz timestamp rates, as  
>> follows:
>> - Senders and receivers MUST support a 90kHz RTP timestamp rate,  
>> and MAY
>>   support other rates.
>> - Senders SHOULD use 90kHz timestamp where possible, and the draft  
>> needs to
>>   be updated to include strong guidance on choosing the timestamp  
>> rate, and
>>   the implications of using a rate other than 90kHz.
>> - The timestamp rate MUST be negotiated. The offer/answer  
>> considerations
>>   should explain how this is done.
>> - Senders that wish to use a non-90kHz rate SHOULD also offer the  
>> same stream
>>   using a 90kHz timestamp rate, with a different RTP payload type,  
>> e.g.:
>>     m=video 5004 RTP/AVP 98 99
>>     a=rtpmap:98 jpeg2000/90000
>>     a=rtpmap:99 jpeg2000/27000000
>>   allowing graceful fallback to 90kHz if the receiver doesn't  
>> support the high
>>   rate.
>> To check the consensus, please reply to this message by the end of  
>> this week, stating if you agree or disagree with this proposal,  
>> and giving your reasons. Please do this even if you believe you  
>> have already stated your preference.
>
> I am fine with this. However, I think the SDP example should switch  
> the priority order of the two payload formats to indicate that one  
> does like to use 27 MHz rather then 90k. So if including an example  
> with this, change the m= line to:
> m=video 5004 RTP/AVP 99 98

There seems to be consensus that more flexibility should be allowed  
in the choice of timestamp rate for the JPEG2000 payload format.   
Authors, could you please therefore submit an update reflecting this.

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



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



From avt-bounces@ietf.org Mon Jul 02 13:01:30 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5PHF-0008Ii-0n; Mon, 02 Jul 2007 13:01:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5PHD-0008Ax-Jx
	for avt@ietf.org; Mon, 02 Jul 2007 13:01:27 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5PH0-0007vn-N8
	for avt@ietf.org; Mon, 02 Jul 2007 13:01:27 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:56951)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1I5PGz-0007O1-Qp; Mon, 02 Jul 2007 18:01:13 +0100
In-Reply-To: <p062408a3c2a679e3bba1@[17.202.35.52]>
References: <7634542FB03DC747813D67560802AEED9EB379@rennsmail05.eu.thmulti.com>
	<465D8C51.4080805@ericsson.com>
	<p06240817c28360afcce1@[17.202.35.52]>
	<465E8514.9080503@ericsson.com> <4666DD9A.4161A698@erols.com>
	<p06240887c28f9648fa12@[17.202.35.52]>
	<61DDFB8A-8EA0-4F26-9610-9FCA7FD3633C@csperkins.org>
	<46757295.C62C43BF@erols.com> <46767822.1060308@ericsson.com>
	<p06240843c29d41cb741b@[17.202.35.52]>
	<46779487.5060308@ericsson.com>
	<85FF4F5B-138E-4788-8009-515DD4C17EBF@csperkins.org>
	<4680C859.8050900@ericsson.com>
	<p062408a3c2a679e3bba1@[17.202.35.52]>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <CBAEB8AB-6848-41F1-8F53-417380A61B75@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Timestamp rates [was Re: [AVT] Working group last call: JPEG-2000
	payload format]
Date: Mon, 2 Jul 2007 18:01:15 +0100
To: Dave Singer <singer@apple.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Dave, all,

I don't believe there is consensus to allow this much timestamp rate  
flexibility with the JPEG-2000 payload format, but I'd like to hear  
opinions from the group on how RTP timestamp rates should be  
specified in future payload formats. Should we be adding text to the  
"how to write an RTP payload format" draft to recommend that future  
video formats allow a wider choice of timestamp rates than just  
90kHz?  If so, what range?

Colin



On 26 Jun 2007, at 10:00, Dave Singer wrote:
> OK, most of this isn't really a point about JPEG 2000, but about  
> the evolution of RTP, and perhaps it needs to be disconnected from  
> the JPEG 2000 draft.
>
> * * * *
>
> The problem with the proposed text is that it is SIP-centric;  it  
> assumes negotiation and choice, neither of which are present in SAP  
> or RTSP (for example).  In a multicast or RTSP context, can I rely  
> on using the correct non-90kHz rate for my 7 fps stream, or not?   
> The requirement "must be negotiated" and "alternatives must be  
> offered" are not always achievable.
>
>
>
> The consequences of doing timestamp conversion badly vary greatly  
> between the sender and receiver, also.  If a receiver does poor  
> timestamp conversion (e.g. it introduces drift as a result of round- 
> off), it affects only itself.  If a sender does it badly, the RTP  
> packets have poorly formed timestamps and all receivers are  
> affected (e.g. in a multicast).
>
> Also, if the sender does conversion correctly for something that  
> isn't an integer division of 90kHz, the delta between successive  
> timestamps will vary, suggesting that the frame rate is variable,  
> when it is, in fact, constant.
>
> I still question the whole principle that RTP payload formats  
> should mandate anything at all about clock rates.  RTP receivers  
> are supposed to cope with arbitrary, suitable, clock rates, and the  
> RTP spec. has a statement that the resolution must be high enough  
> for the desired synchronization accuracy and for measuring packet  
> arrival jitter.
>
> Way back when a payload type (small number) was all you needed to  
> know to decode an RTP session (you didn't need an SDP file or  
> anything), it was necessary that the clockrate for a given payload  
> format be statically defined.  We don't have static payload types  
> any more and we don't need to statically associate clockrates with  
> payloads.
>
> The MPEG payload format uses 90 kHz because that clock rate is  
> mandated in the MPEG spec., so the payload format reasonably says  
> that it should match.  Not all applications of JPEG2000 RTP come  
> from a 90 kHz source, so that does not apply here.
>
> At 10:03  +0200 26/06/07, Magnus Westerlund wrote:
>> Colin Perkins skrev:
>>> Wrapping up, I believe the rough consensus is that the JPEG-2000  
>>> draft should be updated to allow non-90kHz timestamp rates, as  
>>> follows:
>>>
>>> - Senders and receivers MUST support a 90kHz RTP timestamp rate,  
>>> and MAY
>>>   support other rates.
>>>
>>> - Senders SHOULD use 90kHz timestamp where possible, and the  
>>> draft needs to
>>>   be updated to include strong guidance on choosing the timestamp  
>>> rate, and
>>>   the implications of using a rate other than 90kHz.
>>>
>>> - The timestamp rate MUST be negotiated. The offer/answer  
>>> considerations
>>>   should explain how this is done.
>>>
>>> - Senders that wish to use a non-90kHz rate SHOULD also offer the  
>>> same stream
>>>   using a 90kHz timestamp rate, with a different RTP payload  
>>> type, e.g.:
>>>
>>>     m=video 5004 RTP/AVP 98 99
>>>     a=rtpmap:98 jpeg2000/90000
>>>     a=rtpmap:99 jpeg2000/27000000
>>>
>>>   allowing graceful fallback to 90kHz if the receiver doesn't  
>>> support the high
>>>   rate.
>>>
>>> To check the consensus, please reply to this message by the end  
>>> of this week, stating if you agree or disagree with this  
>>> proposal, and giving your reasons. Please do this even if you  
>>> believe you have already stated your preference.
>>>
>>
>> I am fine with this. However, I think the SDP example should  
>> switch the priority order of the two payload formats to indicate  
>> that one does like to use 27 MHz rather then 90k. So if including  
>> an example with this, change the m= line to:
>> m=video 5004 RTP/AVP 99 98
>>
>> Cheers
>>
>> Magnus Westerlund
>>
>> IETF Transport Area Director & TSVWG Chair
>> --------------------------------------------------------------------- 
>> -
>> Multimedia Technologies, Ericsson Research EAB/TVM/M
>> --------------------------------------------------------------------- 
>> -
>> Ericsson AB                | Phone +46 8 4048287
>> Torshamsgatan 23           | Fax   +46 8 7575550
>> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>> --------------------------------------------------------------------- 
>> -
>
>
> -- 
> David Singer
> Apple/QuickTime
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt



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



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



From avt-bounces@ietf.org Mon Jul 02 17:05:19 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5T57-0006hy-9X; Mon, 02 Jul 2007 17:05:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5T55-0006di-Dr; Mon, 02 Jul 2007 17:05:11 -0400
Received: from mx.cbeyond.com ([66.180.96.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I5T3r-0006Nd-HG; Mon, 02 Jul 2007 17:05:11 -0400
Received: from [69.15.238.196] (port=2809 helo=TELCHADCPC)
	by mx.cbeyond.com with esmtpa (Exim 4.62)
	(envelope-from <alan.d.clark@telchemy.com>)
	id 1I5T3q-0004cR-Cx; Mon, 02 Jul 2007 17:03:55 -0400
From: "Alan Clark" <alan.d.clark@telchemy.com>
To: <internet-drafts@ietf.org>
Date: Mon, 2 Jul 2007 17:02:55 -0400
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0091_01C7BCCA.D75C8910"
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
thread-index: Ace87Fjt3NovjxVFRWGwh09M2WFLFg==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 85e99493ec37f9acef29c7843dbf2e68
Cc: "'Even, Roni'" <roni.even@polycom.co.il>, avt@ietf.org,
	'Colin Perkins' <csp@csperkins.org>
Subject: [AVT] draft-ietf-avt-rtcpxr-audio-00.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org
Message-Id: <E1I5T57-0006hy-9X@megatron.ietf.org>

This is a multi-part message in MIME format.

------=_NextPart_000_0091_01C7BCCA.D75C8910
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0092_01C7BCCA.D75C8910"


------=_NextPart_001_0092_01C7BCCA.D75C8910
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Title: draft-ietf-avt-rtcpxr-audio-00.txt
 
Authors: Alan Clark, Amy Pendleton
 
Abstract: This memo defines an RTCP XR report block type for reporting the
performance of audio streams sent over RTP.  This was formerly a sub-block
of draft-ietf-avt-rtcpxr-video-00.txt
 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D187315920-02072007><FONT size=3D2>Title:=20
draft-ietf-avt-rtcpxr-audio-00.txt</FONT></SPAN></DIV>
<DIV><SPAN class=3D187315920-02072007><FONT =
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D187315920-02072007><FONT size=3D2>Authors: Alan =
Clark, Amy=20
Pendleton</FONT></SPAN></DIV>
<DIV><SPAN class=3D187315920-02072007><FONT =
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D187315920-02072007><FONT size=3D2>Abstract: This memo =
defines an=20
RTCP XR report block type for reporting the performance of audio streams =
sent=20
over RTP.&nbsp; This was formerly a sub-block of=20
draft-ietf-avt-rtcpxr-video-00.txt</FONT></SPAN></DIV>
<DIV><SPAN class=3D187315920-02072007></SPAN>&nbsp;</DIV></BODY></HTML>

------=_NextPart_001_0092_01C7BCCA.D75C8910--

------=_NextPart_000_0091_01C7BCCA.D75C8910
Content-Type: text/plain;
	name="draft-ietf-avt-rtcpxr-audio-00.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment; filename="draft-ietf-avt-rtcpxr-audio-00.txt"


Internet Engineering Task Force                                 A. Clark
Internet-Draft                                     Telchemy Incorporated
Expires: 29th December 2007                                 A. Pendleton
                                                                  Nortel
                                                               July 2007






                RTCP XR - Audio Metrics Report Block
                 draft-ietf-avt-rtcpxr-audio-00.txt

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on 29th December 2007.

Copyright Notice


   Copyright (C) The IETF Trust (2007).

Abstract

   This document defines extensions to the RTCP XR extended report
   packet type blocks to support the performance monitoring of audio
   streams transmitted using RTP.=20
   This draft is one of a set of four that replace the -00 version
   of the ietf-avt-rtcpxr-video-00.txt draft.




Clark                                                          [Page  1]
=0C
draft-ietf-avt-rtcpxr-audio-00.txt                             July 2007



Table of Contents

   1.   Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
   2.   Definitions  . . . . . . . . . . . . . . . . . . . . . . . . 2
   3.   Audio Metrics Report Block . . . . . . . . . . . . . . . . . X
   4.   Summary  . . . . . . . . . . . . . . . . . . . . . . . . . . X
   5.   Security Considerations  . . . . . . . . . . . . . . . . . . 13
   6.   IANA Considerations  . . . . . . . . . . . . . . . . . . . . 13
   7.   Acknowledgements . . . . . . . . . . . . . . . . . . . . . . X
   8.   Informative References . . . . . . . . . . . . . . . . . . . 13
        Authors' Addresses . . . . . . . . . . . . . . . . . . . . .=20
        Intellectual Property and Copyright Statements . . . . . . .=20




1.  Introduction

   This draft defines a block type to augment those defined
   in RFC3611 for use in Quality of Service reporting for audio over IP.
   The new block type defined in this draft is the IP Audio Metrics=20
   Report Block. This is intended to support both the identification of
   problems affecting performance and the collection of data that may
   be useful in optimizing system configuration.

   Audio performance may be measured using zero (no) reference, partial
   (reduced) reference or full reference.  The primary application of
   this draft is to support the reporting of real-time, in-service
   performance obtained using a zero or partial reference model however
   this approach could also be used to support the remote reporting of
   metrics from a full reference test.


2.  Definitions



3  Audio Metrics Report Block

3.1 Block Description

    0               1               2               3
    0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7=20
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     BT=3DN      |   Reserved    |         block length          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                             SSRC                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |0 0 0|       Program ID        |           Reserved            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                       Report Timestamp                        |

Clark                                                          [Page  2]
=0C
draft-ietf-avt-rtcpxr-audio-00.txt                             July 2007

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  Measurement Interval (ms)                    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   MOS-A - Audio Quality (M/L) |    MOS-A Audio Quality (R)    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  Mean Audio bit rate (bits/sec)               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Round Trip Delay        |    A-V Delay (Video I/F)      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |    Playout Interrupt Count    |  Mean Playout Interrupt Size  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Audio Playout buffer size    |        Mean buffer level      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

3.2 Definition of Metrics

  3.2.1 Header
  The header comprises:
    (i) Block Type for this report block
    (ii) Reserved (set to 0xFF)
    (iii) Block length in words (set to 0x0009)
    (iv) SSRC of the received RTP stream that this report refers to
    (v) Program ID (PID) for the audio stream (if MPEG Transport
        encapsulation is used)
    (vi) Reserved (set to 0xFFFF)

  3.2.2 Report Timestamp
  The time at which this report was generated (format?)

  3.2.3 Measurement Interval
  The interval of time over which these metrics were measured,
  expressed in milliseconds.

  3.2.4 MOS-A (M/L) and MOS-A (R)
  An estimate of the quality of the received audio stream expressed
  as a Mean Opinion Score.=20
 =20
     (i) MOS-A (M/L).  The quality score for a monophonic stream or
         the Left channel for a stereophonic stream

     (ii) MOS-A (R).   The quality score for the Right channel of a
         stereophonic stream

  3.2.5 Mean Audio Bit Rate
  The average bit rate of the audio stream expressed in bits per
  second.

  3.2.6 Round Trip Delay
  The Round Trip Delay between the originating and terminating ends
  of this RTP stream, expressed in millseconds.  In unicast or
  multicast applications this parameter may be set to "undefined"
  (0xFFFF).


Clark                                                          [Page  3]
=0C
draft-ietf-avt-rtcpxr-audio-00.txt                             July 2007

  3.2.7 A-V Delay
  The relative delay between decoded audio and video streams expressed
  in milliseconds. =20

  3.2.8 Playout Interrupt Count
  The number of interruptions that occurred during playout, due to=20
  either packet loss or buffer underrun.

  3.2.9 Mean Playout Interrupt Size
  The mean duration of interruptions in playout expressed in
  milliseconds.

  3.2.10 Audio Playout Buffer Size
  The available playout buffer size, expressed in milliseconds.

  3.2.11 Mean Buffer Level
  The mean playout buffer size, expressed in milliseconds.



4. Summary

  This draft defines an RTCP XR block for audio quality reporting.
  This is intended for in-service monitoring of audio streaming, IPTV
  and IP videoconferencing services to provide real time performance
  feedback and support performance management.=20


5. IANA Considerations

  The block type "mmm" will need to be replaced with an IANA assigned
  number within those allocated for RTCP XR report blocks (RFC 3611).

6.  Security Considerations

   RTCP reports can contain sensitive information since they can provide
   information about the nature and duration of a session established
   between two endpoints.  As a result, any third party wishing to
   obtain this information should be properly authenticated and the
   information transferred securely.

7. Acknowledgments


8.  Informative References

   [1]  Bradner, S., "Key words for use in RFCs to Indicate Requirement
        Levels", BCP 14, RFC 2119, March 1997.

   [2]  Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson,
        "RTP: A Transport Protocol for Real-Time Applications", STD 64,
        RFC 3550, July 2003.


Clark                                                          [Page  4]
=0C
draft-ietf-avt-rtcpxr-audio-00.txt                             July 2007

   [3]  Friedman, T., Caceres, R. and A. Clark, "RTP Control Protocol
        Extended Reports (RTCP XR)", RFC 3611, November 2003.

Authors' Addresses

   Alan Clark
   Telchemy Incorporated
   2905 Premiere Parkway, Suite 280
   Duluth, GA 30097
   Email: alan@telchemy.com

   Amy Pendleton
   Nortel
   2380 Performance Drive
   Richardson, TX  75081
   Email: aspen@nortel.com

Full Copyright Statement

   Copyright (C) The IETF Trust (2007).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.




Clark                                                          [Page  5]
=0C
draft-ietf-avt-rtcpxr-audio-00.txt                             July 2007



   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at ietf-
   ipr@ietf.org.

Acknowledgement

   Funding for the RFC Editor function is provided by the IETF
   Administrative Support Activity (IASA).









































Clark                                                        [Page  6]

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

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

------=_NextPart_000_0091_01C7BCCA.D75C8910--





From avt-bounces@ietf.org Mon Jul 02 18:15:46 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5UBD-0000Q5-UC; Mon, 02 Jul 2007 18:15:35 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5UBA-0000Ms-Qb; Mon, 02 Jul 2007 18:15:32 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I5UBA-000705-Jf; Mon, 02 Jul 2007 18:15:32 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 4BFB717622;
	Mon,  2 Jul 2007 22:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I5UAf-0004rW-QS; Mon, 02 Jul 2007 18:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I5UAf-0004rW-QS@stiedprstage1.ietf.org>
Date: Mon, 02 Jul 2007 18:15:01 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-h264-params-00.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: Parameters for Static Macroblocks and Aspect Ratio in the RTP Payload Format for H.264 Video
	Author(s)	: T. Kristensen, R. Even
	Filename	: draft-ietf-avt-rtp-h264-params-00.txt
	Pages		: 9
	Date		: 2007-7-2
	
   This document updates RFC 3984.  It defines new optional parameters
   addressing recent extensions currently supported in H.323 systems:
   The signalling of the maximum rate of static macroblocks a decoder is
   able to process.  The signalling of the sample aspect ratio supported
   by the sender or the receiver.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-h264-params-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-rtp-h264-params-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-rtp-h264-params-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-h264-params-00.txt

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

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


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org Mon Jul 02 21:30:49 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5XE6-0004gi-Im; Mon, 02 Jul 2007 21:30:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5FlH-00047r-So
	for avt@ietf.org; Mon, 02 Jul 2007 02:51:51 -0400
Received: from sniper.kisa.or.kr ([211.252.150.22] helo=spam.kisa.or.kr)
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1I5FlC-000107-8J
	for avt@ietf.org; Mon, 02 Jul 2007 02:51:51 -0400
Received: (snipe 32237 invoked by alias); 2 Jul 2007 15:36:18 +0900
Received: from seokung@kisa.or.kr with Spamsniper 2.83.29 (Processed in
	0.050395 secs); 
Received: from unknown (HELO kisarang2) (211.252.150.47)
	by unknown with SMTP; 2 Jul 2007 15:36:18 +0900
X-RCPTTO: avt@ietf.org
Received: from kisarang2 (kisarang2 [211.252.150.47])
	by webmail.kisa.or.kr (iPlanet Messaging Server 5.2 Patch 2 (built Jul
	14 2004)) with ESMTP id <0JKJ00DA4HUSU4@webmail.kisa.or.kr> for
	avt@ietf.org; Mon, 02 Jul 2007 15:54:28 +0900 (KST)
Date: Mon, 02 Jul 2007 15:54:28 +0900 (KST)
From: =?ks_c_5601-1987?B?wLG8rr/1?= <seokung@kisa.or.kr>
In-reply-to: <144ED8561CE90C41A3E5908EDECE315C04AFCEAB@IsrExch01.israel.polycom.com>
To: Roni <roni.even@polycom.co.il>, avt@ietf.org
Message-id: <22153427.1183359268810.JavaMail.jeus@kisarang2>
MIME-version: 1.0
X-Mailer: WINipMail2.5.1
Content-type: multipart/mixed;
	boundary="----=_Part_8038_25109992.1183359268364"
X-Priority: 3
X-UserInfo: =?ks_c_5601-1987?B?wLG8rr/1L0lUseK53bq4yKO03C+8scDTL3M=?=
	=?ks_c_5601-1987?B?ZW9rdW5nQGtpc2Eub3Iua3I=?=
X-UserUID: A0600
X-Identifier: acb3-11385b5760c-7c38-kisarang2
X-Spam-Score: 3.3 (+++)
X-Scan-Signature: 0634ec58aad05a6aa9ac7d4670be9c6c
X-Mailman-Approved-At: Mon, 02 Jul 2007 21:30:45 -0400
Cc: 
Subject: [AVT] Re: RE: RE: Time-slot request on AVT WG
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org


------=_Part_8038_25109992.1183359268364
Content-Type: text/html; charset=ks_c_5601-1987
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<META http-equiv=3DContent-Type content=3D'text/html; charset=3Dks_c_5601-1=
987'>
<title>WINiPMail Mail</title>
<style>
BODY {font-family:Arial, arial; font-size:10pt;}
P, td, li {font-family:Arial, arial; font-size:10pt; margin-top:2px;margin-=
bottom:2px;}
</style>=20
<title>WINiPMail Mail</title>
<style>
BODY {font-family:=B1=BC=B8=B2=C3=BC, arial; font-size:10pt;}
P, td, li {font-family:=B1=BC=B8=B2=C3=BC, arial; font-size:10pt; margin-to=
p:2px;margin-bottom:2px;}
</style>=20
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<title>WINiPMail Mail</title>
<style>
<!--
 /* Font Definitions */
 @font-face
=09{font-family:Gulim;
=09panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
=09{font-family:Tahoma;
=09panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
=09{font-family:"\@Gulim";
=09panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
=09{margin:0cm;
=09margin-bottom:.0001pt;
=09font-size:12.0pt;
=09font-family:Gulim;}
a:link, span.MsoHyperlink
=09{color:blue;
=09text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
=09{color:purple;
=09text-decoration:underline;}
p
=09{margin-top:1.5pt;
=09margin-right:0cm;
=09margin-bottom:1.5pt;
=09margin-left:0cm;
=09font-size:10.0pt;
=09font-family:Arial;}
span.EmailStyle18
=09{mso-style-type:personal-reply;
=09font-family:Arial;
=09color:navy;}
@page Section1
=09{size:612.0pt 792.0pt;
=09margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
=09{page:Section1;}
-->
</style>
</head>

<body>
<p>Dear Roni,</p>
<p>&nbsp;</p>
<p>Actually, I submitted my initial draft one hour ago.</p>
<p>That's why you couldn't find it</p>
<p>&nbsp;</p>
<p>Here is my initial draft.</p>
<p>&nbsp;</p>
<p>BR,</p>
<p>Seokung</p>
<DIV>&nbsp;</DIV>-----=09=B8=DE=C0=CF=C0=C7 =BF=F8=B9=AE=09-----
<br><DIV style=3D"BACKGROUND: #e4e4e4; font-color: black">
<b>From: </b>Even, Roni &lt;roni.even@polycom.co.il&gt;</DIV>
<b>Sent:=09</b>Mon Jul 02 15:46:26 KST 2007
<br><b>To:  </b>=C0=B1=BC=AE=BF=F5 &lt;seokung@kisa.or.kr&gt;, Colin Perkin=
s &lt;csp@csperkins.org&gt;, Tom Taylor &lt;tom.taylor@rogers.com&gt;
<br><b>Subject:  </b>RE: RE: Time-slot request on AVT WG
<br><p><!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City" />
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"country-region" />
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place" />
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName" />
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
<div class=3DSection1>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Is this draft posted already, what is =
its
name.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I suggest you send an email to the AVT
mailing list <a href=3D"mailto:avt@ietf.org">avt@ietf.org</a> with a link t=
o the
draft.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><st1:PersonName ProductID=3D"Roni Even" w:st=3D"on"><f=
ont
 size=3D2 color=3Dnavy face=3DArial><span style=3D'font-size:10.0pt;font-fa=
mily:Arial;
 color:navy'>Roni Even</span></font></st1:PersonName><font size=3D2 color=
=3Dnavy
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial;color:navy'>=
<o:p></o:p></span></font></p>

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

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

<div>

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

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

</div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span style=3D'font-si=
ze:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> </span><=
/font><font
size=3D2><span lang=3DKO style=3D'font-size:10.0pt'>=C0=B1=BC=AE=BF=F5</spa=
n></font><font size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
[mailto:seokung@kisa.or.kr] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, July 02, 2007 =
9:27
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> <st1:PersonName
ProductID=3D"Colin Perkins" w:st=3D"on">Colin Perkins</st1:PersonName>; Eve=
n, Roni;
Tom Taylor<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: RE: Time-slot r=
equest
on AVT WG</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3DGulim><span style=3D'font-size:1=
2.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p><font size=3D2 face=3DArial><span style=3D'font-size:10.0pt'>Dear Chairs=
<o:p></o:p></span></font></p>

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

<p><font size=3D2 face=3DArial><span style=3D'font-size:10.0pt'>I submitted=
 initial
draft to internet-drafts@ietf.org.<o:p></o:p></span></font></p>

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

<p><font size=3D2 face=3DArial><span style=3D'font-size:10.0pt'>Actually, I=
 am not
sure that my draft will meet the needs of AVT WG.<o:p></o:p></span></font><=
/p>

<p><font size=3D2 face=3DArial><span style=3D'font-size:10.0pt'>So, I want =
to discuss
my draft on AVT WG on 69th IETF.<o:p></o:p></span></font></p>

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

<p><font size=3D2 face=3DArial><span style=3D'font-size:10.0pt'>If you give=
 me a
time-slot, I really appreciate it.<o:p></o:p></span></font></p>

<p><font size=3D2 face=3DArial><span style=3D'font-size:10.0pt'>If not, ple=
ase help
me with guidance on how to proceed with my work.<o:p></o:p></span></font></=
p>

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

<p><font size=3D2 face=3DArial><span style=3D'font-size:10.0pt'>See you soo=
n.<o:p></o:p></span></font></p>

<p><font size=3D2 face=3DArial><span style=3D'font-size:10.0pt'>BR,<o:p></o=
:p></span></font></p>

<p><font size=3D2 face=3DArial><span style=3D'font-size:10.0pt'>Seokung<o:p=
></o:p></span></font></p>

<div>

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

</div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>----- </span></font><font size=3D2><span lang=3DKO
style=3D'font-size:10.0pt'>=B8=DE=C0=CF=C0=C7</span></font><font size=3D2 f=
ace=3DArial><span
lang=3DKO style=3D'font-size:10.0pt;font-family:Arial'> </span></font><font=
 size=3D2><span
lang=3DKO style=3D'font-size:10.0pt'>=BF=F8=B9=AE</span></font><font size=
=3D2 face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'> ----- <o:p></o:p></span></fon=
t></p>

<div style=3D'font-color:black'>

<p class=3DMsoNormal style=3D'background:#E4E4E4'><b><font size=3D2 face=3D=
Arial><span
style=3D'font-size:10.0pt;font-family:Arial;font-weight:bold'>From: </span>=
</font></b><font
size=3D2 face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'>Ev=
en, Roni
&lt;roni.even@polycom.co.il&gt;<o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><b><font size=3D2 face=3DArial><span style=3D'font-siz=
e:10.0pt;
font-family:Arial;font-weight:bold'>Sent: </span></font></b><font size=3D2
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'>Fri Jun 29 =
19:07:50
KST 2007 <br>
<b><span style=3D'font-weight:bold'>To: </span></b></span></font><font size=
=3D2><span
lang=3DKO style=3D'font-size:10.0pt'>=C0=B1=BC=AE=BF=F5</span></font><font =
size=3D2 face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'> &lt;seokung@kisa.or.kr&gt;, <=
st1:PersonName
ProductID=3D"Colin Perkins" w:st=3D"on">Colin Perkins</st1:PersonName> &lt;=
csp@csperkins.org&gt;,
Tom Taylor &lt;tom.taylor@rogers.com&gt; <br>
<b><span style=3D'font-weight:bold'>Subject: </span></b>RE: Time-slot reque=
st on
AVT WG <o:p></o:p></span></font></p>

<p><font size=3D2 face=3DArial><span style=3D'font-size:10.0pt'><br>
<br>
Seokung,<br>
<br>
We noted your request. In the IETF meeting we may make presentation based o=
n
available drafts (personal or WG). I could not find any draft that addresse=
s
the topic.<br>
<br>
We suggest that you will prepare an initial draft describing the issue you =
want
to address. The draft name may be draft-seokung-avt-seed-srtp-00.txt<br>
Note that the deadline for draft submission is July 2, Monday by 09:00 ET
(13:00 UTC/GMT).<br>
<br>
Regardless if you have a draft or not, the chairs will be happy to meet you
during the <st1:City w:st=3D"on"><st1:place w:st=3D"on">Chicago</st1:place>=
</st1:City>
meeting and help you with guidance on how to proceed with your work.<br>
<br>
Regards<br>
<st1:PersonName ProductID=3D"Roni Even" w:st=3D"on">Roni Even</st1:PersonNa=
me><br>
AVT co-chair<br>
<br>
<br>
<br>
<br>
<br>
<br>
________________________________________<br>
From: </span></font><font face=3DGulim><span lang=3DKO style=3D'font-family=
:Gulim'>=C0=B1=BC=AE=BF=F5</span></font>
[mailto:seokung@kisa.or.kr] <br>
Sent: Friday, June 29, 2007 4:38 AM<br>
To: <st1:PersonName ProductID=3D"Colin Perkins" w:st=3D"on">Colin Perkins</=
st1:PersonName>;
Even, Roni; Tom Taylor<br>
Subject: Time-slot request on AVT WG<br>
<br>
Dear Chairs<br>
<br>
My name is Seokung Yoon and I works for KISA(Korea Information Security
Agency).<br>
<br>
I am responsible for developing VoIP security.<br>
<br>
In <st1:country-region w:st=3D"on"><st1:place w:st=3D"on">korea</st1:place>=
</st1:country-region>,
many enterprises already started VoIP service and their market share is
increasing gradually.<br>
<br>
Actually, we are developing VoIP Phone including secure functions to protec=
t
subscriber's privacies.<br>
<br>
Our phone use SRTP for multimedia data encryption and support encryption
algorithms such as AES and SEED<br>
<br>
SEED is a standard algorithm in <st1:country-region w:st=3D"on"><st1:place =
w:st=3D"on">korea</st1:place></st1:country-region>
and IETF(RFC 4269) and adopted in TLS(RFC 4162) and IPSec(RFC 4196).<br>
<br>
So, I want to extend the SRTP or STRCP with SEED algorithm for interoperbil=
ity.<br>
<br>
Would you comment my proposal and allot time-slot on AVT WG in 69th IETF ??=
<br>
<br>
I will introduce the present condition of VoIP service in <st1:country-regi=
on
w:st=3D"on"><st1:place w:st=3D"on">korea</st1:place></st1:country-region> a=
nd my
proposal.<br>
<br>
Please reply to me.<br>
<br>
BR,<br>
Seokung<br>
<br>
 <o:p></o:p></p>

</div>

</div>

=20




<img border=3D"0" height=3D"0" width=3D"0" src=3D"http://webmail.kisa.or.kr=
:8880/servlet/ReadConfirmer?confirmidacb3-11385b5760c-7c38-kisarang2"></bod=
y>
</html>
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=
=00=00=00=00=00
------=_Part_8038_25109992.1183359268364
Content-Type: application/octet-stream; 
	name=draft-seokung-avt-seed-srtp-00.txt
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="draft-seokung-avt-seed-srtp-00.txt"

QVZUIFdvcmtpbmcgR3JvdXAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IFNlb2t1bmcgWW9vbiANCkludGVybmV0IERyYWZ0ICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICBKb29uZ21hbiBLaW0gDQpFeHBpcmVzOiBKYW51YXJ5IDIwMDggICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBZb29qYWUgV29uIA0KICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIEtvcmVhIEluZm9ybWF0aW9uIFNlY3VyaXR5IEFn
ZW5jeSANCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICBKdWx5IDIsIDIwMDcgDQogDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIA0KICAgICAgVGhlIFNFRUQgQ2lwaGVyIEFsZ29yaXRobSBhbmQgSXRzIFVzZSB3aXRo
IHRoZSBTZWN1cmUgUmVhbC10aW1lIA0KICAgICAgICAgICAgICAgICAgICAgICAgIFRyYW5zcG9y
dCBQcm90b2NvbCAoU1JUUCkgDQogICAgICAgICAgICAgICAgICAgIGRyYWZ0LXNlb2t1bmctYXZ0
LXNlZWQtc3J0cC0wMC50eHQgDQoNCg0KU3RhdHVzIG9mIHRoaXMgTWVtbyANCg0KICAgQnkgc3Vi
bWl0dGluZyB0aGlzIEludGVybmV0LURyYWZ0LCBlYWNoIGF1dGhvciByZXByZXNlbnRzIHRoYXQg
ICAgICAgDQogICBhbnkgYXBwbGljYWJsZSBwYXRlbnQgb3Igb3RoZXIgSVBSIGNsYWltcyBvZiB3
aGljaCBoZSBvciBzaGUgaXMgICAgICAgDQogICBhd2FyZSBoYXZlIGJlZW4gb3Igd2lsbCBiZSBk
aXNjbG9zZWQsIGFuZCBhbnkgb2Ygd2hpY2ggaGUgb3Igc2hlICAgICAgIA0KICAgYmVjb21lcyBh
d2FyZSB3aWxsIGJlIGRpc2Nsb3NlZCwgaW4gYWNjb3JkYW5jZSB3aXRoIFNlY3Rpb24gNiBvZiAg
ICAgICANCiAgIEJDUCA3OS4gDQoNCiAgIEludGVybmV0LURyYWZ0cyBhcmUgd29ya2luZyBkb2N1
bWVudHMgb2YgdGhlIEludGVybmV0IEVuZ2luZWVyaW5nIA0KICAgVGFzayBGb3JjZSAoSUVURiks
IGl0cyBhcmVhcywgYW5kIGl0cyB3b3JraW5nIGdyb3Vwcy4gIE5vdGUgdGhhdCANCiAgIG90aGVy
IGdyb3VwcyBtYXkgYWxzbyBkaXN0cmlidXRlIHdvcmtpbmcgZG9jdW1lbnRzIGFzIEludGVybmV0
LSANCiAgIERyYWZ0cy4gDQoNCiAgIEludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRz
IHZhbGlkIGZvciBhIG1heGltdW0gb2Ygc2l4IG1vbnRocyANCiAgIGFuZCBtYXkgYmUgdXBkYXRl
ZCwgcmVwbGFjZWQsIG9yIG9ic29sZXRlZCBieSBvdGhlciBkb2N1bWVudHMgYXQgYW55IA0KICAg
dGltZS4gIEl0IGlzIGluYXBwcm9wcmlhdGUgdG8gdXNlIEludGVybmV0LURyYWZ0cyBhcyByZWZl
cmVuY2UgDQogICBtYXRlcmlhbCBvciB0byBjaXRlIHRoZW0gb3RoZXIgdGhhbiBhcyAid29yayBp
biBwcm9ncmVzcy4iIA0KDQogICBUaGUgbGlzdCBvZiBjdXJyZW50IEludGVybmV0LURyYWZ0cyBj
YW4gYmUgYWNjZXNzZWQgYXQgDQogICBodHRwOi8vd3d3LmlldGYub3JnL2lldGYvMWlkLWFic3Ry
YWN0cy50eHQgDQoNCiAgIFRoZSBsaXN0IG9mIEludGVybmV0LURyYWZ0IFNoYWRvdyBEaXJlY3Rv
cmllcyBjYW4gYmUgYWNjZXNzZWQgYXQgDQogICBodHRwOi8vd3d3LmlldGYub3JnL3NoYWRvdy5o
dG1sIA0KDQogICBUaGlzIEludGVybmV0LURyYWZ0IHdpbGwgZXhwaXJlIG9uIEphbnVhcnkgMiwg
MjAwOC4gDQoNCkNvcHlyaWdodCBOb3RpY2UgDQoNCiAgIENvcHlyaWdodCAoQykgVGhlIElFVEYg
VHJ1c3QgKDIwMDcpLiANCg0KQWJzdHJhY3QgDQoNCiAgIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVz
IHRoZSB1c2Ugb2YgU0VFRCBibG9jayBjaXBoZXIgYWxnb3JpdGhtIGluIHRoZSANCiAgIFNlY3Vy
ZSBSZWFsLXRpbWUgVHJhbnNwb3J0IFByb3RvY29sIFszXSBmb3IgY29uZmlkZW50aWFsaXR5IHRv
IHRoZSANCiAgIFJUUCB0cmFmZmljIGFuZCB0byB0aGUgY29udHJvbCB0cmFmZmljIGZvciBSVFAs
IHRoZSBSZWFsLXRpbWUgDQogICBUcmFuc3BvcnQgQ29udHJvbCBQcm90b2NvbCAoUlRDUCkuIA0K
IA0KIA0KIA0KWW9vbiwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEphbnVhcnkgMiwgMjAwOCAg
ICAgICAgICAgICAgICBbUGFnZSAxXSANCgwNCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICBB
VlQtU0VFRC1TUlRQICAgICAgICAgICAgICAgICBKdWx5IDIsIDIwMDcgDQogICAgDQoNClRhYmxl
IG9mIENvbnRlbnRzIA0KDQogICAgDQogICAxLiBJbnRyb2R1Y3Rpb24uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjIgDQogICAgICAxLjEuIFNFRUQuLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjIgDQogICAg
ICAxLjIuIFRlcm1pbm9sb2d5Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLjMgDQogICAyLiBUaGUgU0VFRCBDaXBoZXIgQWxnb3JpdGhtLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLjMgDQogICAgICAyLjEuIE1vZGUuLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjMgDQogICAgICAyLjIuIEtleSBT
aXplIGFuZCBOdW1iZXIgb2YgUm91bmRzLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjMgDQog
ICAgICAyLjMuIEJsb2NrIFNpemUgYW5kIFBhZGRpbmcuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLjMgDQogICAgICAyLjQuIFBlcmZvcm1hbmNlLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjMgDQogICAzLiBTZWN1cml0eSBDb25zaWRlcmF0aW9u
cy4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjMgDQogICA0LiBJQU5BIENv
bnNpZGVyYXRpb25zLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjQg
DQogICA1LiBSZWZlcmVuY2VzLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLjQgDQogICAgICA1LjEuIE5vcm1hdGl2ZSBSZWZlcmVuY2VzLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjQgDQogICAgICA1LjIuIEluZm9ybWF0aXZlIFJl
ZmVyZW5jZXMuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjQgDQogICBBdXRob3In
cyBBZGRyZXNzZXMuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
LjUgDQogICBJbnRlbGxlY3R1YWwgUHJvcGVydHkgU3RhdGVtZW50Li4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLjUgDQogICBEaXNjbGFpbWVyIG9mIFZhbGlkaXR5Li4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjYgDQogICAgDQogICAgDQoNCjEuIEludHJv
ZHVjdGlvbiANCg0KMS4xLiBTRUVEIA0KDQogICBTRUVEIFsyXSBpcyBhIG5hdGlvbmFsIGluZHVz
dHJpYWwgYXNzb2NpYXRpb24gc3RhbmRhcmQgWzddIGFuZCBpcyANCiAgIHdpZGVseSB1c2VkIGlu
IFNvdXRoIEtvcmVhIGZvciBlbGVjdHJvbmljIGNvbW1lcmNlIGFuZCBmaW5hbmNpYWwgDQogICBz
ZXJ2aWNlcyB0aGF0IGFyZSBvcGVyYXRlZCBvbiB3aXJlZCBhbmQgd2lyZWxlc3MgY29tbXVuaWNh
dGlvbnMuIA0KDQogICBTRUVEIGlzIGEgMTI4LWJpdCBzeW1tZXRyaWMga2V5IGJsb2NrIGNpcGhl
ciB0aGF0IGhhZCBiZWVuIGRldmVsb3BlZCANCiAgIGJ5IEtJU0EoS29yZWEgSW5mb3JtYXRpb24g
U2VjdXJpdHkgQWdlbmN5KSBhbmQgYSBncm91cCBvZiBleHBlcnRzIA0KICAgc2luY2UgMTk5OC4g
VGhlIGlucHV0L291dHB1dCBibG9jayBzaXplIG9mIFNFRUQgaXMgMTI4LWJpdCBhbmQgdGhlIA0K
ICAga2V5IGxlbmd0aCBpcyBhbHNvIDEyOC1iaXQuIFNFRUQgaGFzIHRoZSAxNi1yb3VuZCBGZWlz
dGVsIHN0cnVjdHVyZS4gDQogICBBIDEyOC1iaXQgaW5wdXQgaXMgZGl2aWRlZCBpbnRvIHR3byA2
NC1iaXQgYmxvY2tzIGFuZCB0aGUgcmlnaHQgNjQtDQogICBiaXQgYmxvY2sgaXMgYW4gaW5wdXQg
dG8gdGhlIHJvdW5kIGZ1bmN0aW9uIHdpdGggYSA2NC1iaXQgc3Via2V5IA0KICAgZ2VuZXJhdGVk
IGZyb20gdGhlIGtleSBzY2hlZHVsaW5nLiANCg0KICAgU0VFRCBpcyBlYXNpbHkgaW1wbGVtZW50
ZWQgaW4gdmFyaW91cyBzb2Z0d2FyZSBhbmQgaGFyZHdhcmUgYmVjYXVzZSANCiAgIGl0IGlzIGRl
c2lnbmVkIHRvIGluY3JlYXNlIHRoZSBlZmZpY2llbmN5IG9mIG1lbW9yeSBzdG9yYWdlIGFuZCB0
aGUgDQogICBzaW1wbGljaXR5IGluIGdlbmVyYXRpbmcga2V5cyB3aXRob3V0IGRlZ3JhZGluZyB0
aGUgc2VjdXJpdHkgb2YgdGhlIA0KICAgYWxnb3JpdGhtLiBJbiBwYXJ0aWN1bGFyLCBpdCBjYW4g
YmUgZWZmZWN0aXZlbHkgYWRhcHRlZCB0byBhIA0KICAgY29tcHV0aW5nIGVudmlyb25tZW50IHdp
dGggcmVzdHJpY3RlZCByZXNvdXJjZXMgc3VjaCBhcyBtb2JpbGUgDQogICBkZXZpY2VzLCBzbWFy
dCBjYXJkcyBhbmQgc28gb24uIA0KDQoNCg0KIA0KIA0KWW9vbiwgZXQgYWwuICAgICAgICAgICBF
eHBpcmVzIEphbnVhcnkgMiwgMjAwOCAgICAgICAgICAgICAgICBbUGFnZSAyXSANCgwNCkludGVy
bmV0LURyYWZ0ICAgICAgICAgICAgICBBVlQtU0VFRC1TUlRQICAgICAgICAgICAgICAgICBKdWx5
IDIsIDIwMDcgDQogICAgDQoNCjEuMi4gVGVybWlub2xvZ3kgDQoNCiAgIFRoZSBrZXkgd29yZHMg
Ik1VU1QiLCAiTVVTVCBOT1QiLCAiUkVRVUlSRUQiLCAiU0hBTEwiLCAiU0hBTEwgTk9UIiwgDQog
ICAiU0hPVUxEIiwgIlNIT1VMRCBOT1QiLCAiUkVDT01NRU5ERUQiLCAiTUFZIiwgYW5kICJPUFRJ
T05BTCIgaW4gdGhpcyANCiAgIGRvY3VtZW50IGFyZSB0byBiZSBpbnRlcnByZXRlZCBhcyBkZXNj
cmliZWQgaW4gUkZDLTIxMTkgWzFdLiANCg0KICAgIA0KDQoyLiBUaGUgU0VFRCBDaXBoZXIgQWxn
b3JpdGhtIA0KDQogICBUaGUgYWxnb3JpdGhtIHNwZWNpZmljYXRpb24gYW5kIG9iamVjdCBpZGVu
dGlmaWVycyBhcmUgZGVzY3JpYmVkIGluIA0KICAgWzVdIFszXS4gVGhlIFNFRUQgaG9tZXBhZ2Us
IGh0dHA6Ly93d3cua2lzYS5vci5rci9zZWVkL3NlZWRfZW5nLmh0bWwsIA0KICAgY29udGFpbnMg
YSB3ZWFsdGggb2YgaW5mb3JtYXRpb24gYWJvdXQgU0VFRCwgaW5jbHVkaW5nIGEgZGV0YWlsZWQg
DQogICBzcGVjaWZpY2F0aW9uLCBldmFsdWF0aW9uIHJlcG9ydCwgdGVzdCB2ZWN0b3JzLCBhbmQg
c28gb24uIA0KDQoyLjEuIE1vZGUgDQoNCiAgIFRoaXMgZG9jdW1lbnQgc3BlY2lmaWVzIHRoZSB1
c2Ugb2YgdGhlIFNFRUQgY2lwaGVyIGluIHRoZSBDQkMgKENpcGhlciANCiAgIEJsb2NrIENoYWlu
aW5nKSBtb2RlLiBUaGlzIG1vZGUgcmVxdWlyZXMgYW4gSW5pdGlhbGl6YXRpb24gVmVjdG9yIElW
IA0KICAgdGhhdCBpcyB0aGUgc2FtZSBzaXplIGFzIHRoZSBibG9jayBzaXplLiBUaGUgSVYgTVVT
VCBiZSBjaG9zZW4gYXQgDQogICByYW5kb20gYW5kIE1VU1QgYmUgdW5wcmVkaWN0YWJsZS4gDQoN
CjIuMi4gS2V5IFNpemUgYW5kIE51bWJlciBvZiBSb3VuZHMgDQoNCiAgIFNFRUQgc3VwcG9ydHMg
MTI4LWJpdCBrZXkgYW5kIGhhcyB0aGUgMTYtcm91bmQgRmVpc3RlbCBzdHJ1Y3R1cmUuIA0KDQoy
LjMuIEJsb2NrIFNpemUgYW5kIFBhZGRpbmcgDQoNCiAgIFNFRUQgdXNlcyBhIGJsb2NrIHNpemUg
b2YgMTYgb2N0ZXRzICgxMjggYml0cykuIA0KDQogICBQYWRkaW5nIGlzIHJlcXVpcmVkIGJ5IFNF
RUQgdG8gbWFpbnRhaW4gYSAxNi1vY3RldCAoMTI4LWJpdCkgDQogICBibG9ja3NpemUuIFBhZGRp
bmcgbXVzdCBiZSBhZGRlZCBzdWNoIHRoYXQgdGhlIGRhdGEgdG8gYmUgZW5jcnlwdGVkIA0KICAg
aGFzIGEgbGVuZ3RoIHRoYXQgaXMgYSBtdWx0aXBsZSBvZiAxNiBvY3RldHMuIA0KDQoyLjQuIFBl
cmZvcm1hbmNlIA0KDQogICBQZXJmb3JtYW5jZSBmaWd1cmVzIG9mIFNFRUQgYXJlIGF2YWlsYWJs
ZSBhdCANCiAgIGh0dHA6Ly93d3cua2lzYS5vci5rci9zZWVkL3NlZWRfZW5nLmh0bWwuIA0KDQog
ICAgDQoNCjMuIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zIA0KDQogICBObyBzZWN1cml0eSBwcm9i
bGVtIGhhcyBiZWVuIGZvdW5kIG9uIFNFRUQuIFNFRUQgaXMgc2VjdXJlIGFnYWluc3QgDQogICBh
bGwga25vd24gYXR0YWNrcyBpbmNsdWRpbmcgRGlmZmVyZW50aWFsIGNyeXB0YW5hbHlzaXMsIGxp
bmVhciANCiAgIGNyeXB0YW5hbHlzaXMsIGFuZCByZWxhdGVkIGtleSBhdHRhY2tzLiBUaGUgYmVz
dCBrbm93biBhdHRhY2sgaXMgb25seSANCg0KIA0KIA0KWW9vbiwgZXQgYWwuICAgICAgICAgICBF
eHBpcmVzIEphbnVhcnkgMiwgMjAwOCAgICAgICAgICAgICAgICBbUGFnZSAzXSANCgwNCkludGVy
bmV0LURyYWZ0ICAgICAgICAgICAgICBBVlQtU0VFRC1TUlRQICAgICAgICAgICAgICAgICBKdWx5
IDIsIDIwMDcgDQogICAgDQoNCiAgIGFuIGV4aGF1c3RpdmUgc2VhcmNoIGZvciB0aGUga2V5IChi
eSBbNF0pLiBGb3IgZnVydGhlciBzZWN1cml0eSANCiAgIGNvbnNpZGVyYXRpb25zLCB0aGUgcmVh
ZGVyIGlzIGVuY291cmFnZWQgdG8gcmVhZCBbNF0sIFs1XSwgYW5kIFs2XS4gDQoNCiAgICANCg0K
NC4gSUFOQSBDb25zaWRlcmF0aW9ucyANCg0KIA0KDQo1LiBSZWZlcmVuY2VzIA0KDQo1LjEuIE5v
cm1hdGl2ZSBSZWZlcmVuY2VzIA0KDQogICBbMV0gIEJyYWRuZXIsIFMuLCAiS2V5IHdvcmRzIGZv
ciB1c2UgaW4gUkZDcyB0byBJbmRpY2F0ZSBSZXF1aXJlbWVudCANCiAgICAgICAgIExldmVscyIs
IEJDUCAxNCwgUkZDIDIxMTksIE1hcmNoIDE5OTcuIA0KDQogICBbMl0gIEtJU0EsICJTRUVEIEFs
Z29yaXRobSBTcGVjaWZpY2F0aW9uIiwgDQogICAgICAgICBodHRwOi8vd3d3Lmtpc2Eub3Iua3Iv
c2VlZC9zZWVkX2VuZy5odG1sLiANCg0KICAgWzNdICBNLiBCYXVnaGVyLCBELiBNY0dyZXcsIE0u
IE5hc2x1bmQsIEUuQ2FycmFyYSwgSy4gTm9ycm1hbiwgICAgICAgICAgICAgIA0KICAgICAgICAg
IlRoZSBTZWN1cmUgUmVhbC10aW1lIFRyYW5zcG9ydCBQcm90b2NvbCAoU1JUUCkiLCAgICAgICAg
ICAgIA0KICAgICAgICAgUkZDIDM3MTEsIE1hcmNoIDIwMDQuIA0KDQo1LjIuIEluZm9ybWF0aXZl
IFJlZmVyZW5jZXMgDQoNCiAgIFs0XSAgSW5mb3JtYXRpb24tdGVjaG5vbG9neSBQcm9tb3Rpb24g
QWdlbmN5IChJUEEpLCBKYXBhbiwgQ1JZUFRSRUMuIA0KICAgICAgICAgIlNFRUQgRXZhbHVhdGlv
biBSZXBvcnQiLCBGZWJydWFyeSwgMjAwMiANCiAgICAgICAgIGh0dHA6Ly93d3cua2lzYS5vci5r
ci9zZWVkL3NlZWRfZW5nLmh0bWwuIA0KDQogICBbNV0gIElTTy9JRUMgSlRDIDEvU0MgMjcsICJO
YXRpb25hbCBCb2R5IGNvbnRyaWJ1dGlvbnMgb24gTlAgMTgwMzMgDQogICAgICAgICAiRW5jcnlw
dGlvbiBBbGdvcml0aG1zIiBpbiBSZXNwb25zZSB0byBTQyAyNyBOMjU2MyAoQVRULjMgS29yZWEg
DQogICAgICAgICBDb250cmlidXRpb24pIiwgSVNPL0lFQyBKVEMgMS9TQyAyNyBOMjY1NnIxIChu
MjY1Nl8zLnppcCksIA0KICAgICAgICAgT2N0b2JlciwgMjAwMC4gDQoNCiAgIFs2XSAgS0lTQSwg
IlNlbGYgRXZhbHVhdGlvbiBSZXBvcnQiLCANCiAgICAgICAgIGh0dHA6Ly93d3cua2lzYS5vci5r
ci9zZWVkL3NlZWRfZW5nLmh0bWwuIA0KDQogICBbN10gIFRlbGVjb21tdW5pY2F0aW9ucyBUZWNo
bm9sb2d5IEFzc29jaWF0aW9uIChUVEEpLCBTb3V0aCBLb3JlYSwgDQogICAgICAgICAiMTI4LWJp
dCBTeW1tZXRyaWMgQmxvY2sgQ2lwaGVyIChTRUVEKSIsIFRUQVMuS08tMTIuMDAwNCwgDQogICAg
ICAgICBTZXB0ZW1iZXIsIDE5OTggKEluIEtvcmVhbikgDQogICAgICAgICBodHRwOi8vd3d3LnR0
YS5vci5rci9FbmdsaXNoL25ldy9tYWluL2luZGV4Lmh0bS4gDQoNCiANCg0KDQoNCg0KIA0KIA0K
WW9vbiwgZXQgYWwuICAgICAgICAgICBFeHBpcmVzIEphbnVhcnkgMiwgMjAwOCAgICAgICAgICAg
ICAgICBbUGFnZSA0XSANCgwNCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICBBVlQtU0VFRC1T
UlRQICAgICAgICAgICAgICAgICBKdWx5IDIsIDIwMDcgDQogICAgDQoNCkF1dGhvcidzIEFkZHJl
c3NlcyANCg0KICAgU2Vva3VuZyBZb29uIA0KICAgS29yZWEgSW5mb3JtYXRpb24gU2VjdXJpdHkg
QWdlbmN5IA0KICAgNzgsIEthcmFrLWRvbmcsIFNvbmdwYS1HdSANCiAgIFNlb3VsIDEzOC0xNjAg
DQogICBLT1JFQSANCiAgIFBob25lOiArODItMi00MDUtNTM2MSANCiAgIEZBWCAgOiArODItMi00
MDUtNTMxOSANCiAgIEVtYWlsOiBzZW9rdW5nQGtpc2Eub3Iua3IgDQogICAgDQoNCiAgIEpvb25n
bWFuIEtpbSANCiAgIEtvcmVhIEluZm9ybWF0aW9uIFNlY3VyaXR5IEFnZW5jeSANCiAgIDc4LCBL
YXJhay1kb25nLCBTb25ncGEtR3UgDQogICBTZW91bCAxMzgtMTYwIA0KICAgS09SRUEgDQogICBQ
aG9uZTogKzgyLTItNDA1LTUzMTQgDQogICBGQVggIDogKzgyLTItNDA1LTUzMTkgDQogICBFbWFp
bDogc2VvcG9Aa2lzYS5vci5rciANCiAgICANCg0KICAgWW9vamFlIFdvbiANCiAgIEtvcmVhIElu
Zm9ybWF0aW9uIFNlY3VyaXR5IEFnZW5jeSANCiAgIDc4LCBLYXJhay1kb25nLCBTb25ncGEtR3Ug
DQogICBTZW91bCAxMzgtMTYwIA0KICAgS09SRUEgDQogICBQaG9uZTogKzgyLTItNDA1LTUzNjAg
DQogICBGQVggIDogKzgyLTItNDA1LTUzMTkgDQogICBFbWFpbDogeWp3b25Aa2lzYS5vci5rciAN
CiAgICANCg0KSW50ZWxsZWN0dWFsIFByb3BlcnR5IFN0YXRlbWVudCANCg0KICAgVGhlIElFVEYg
dGFrZXMgbm8gcG9zaXRpb24gcmVnYXJkaW5nIHRoZSB2YWxpZGl0eSBvciBzY29wZSBvZiBhbnkg
DQogICBJbnRlbGxlY3R1YWwgUHJvcGVydHkgUmlnaHRzIG9yIG90aGVyIHJpZ2h0cyB0aGF0IG1p
Z2h0IGJlIGNsYWltZWQgdG8gDQogICBwZXJ0YWluIHRvIHRoZSBpbXBsZW1lbnRhdGlvbiBvciB1
c2Ugb2YgdGhlIHRlY2hub2xvZ3kgZGVzY3JpYmVkIGluIA0KICAgdGhpcyBkb2N1bWVudCBvciB0
aGUgZXh0ZW50IHRvIHdoaWNoIGFueSBsaWNlbnNlIHVuZGVyIHN1Y2ggcmlnaHRzIA0KICAgbWln
aHQgb3IgbWlnaHQgbm90IGJlIGF2YWlsYWJsZTsgbm9yIGRvZXMgaXQgcmVwcmVzZW50IHRoYXQg
aXQgaGFzIA0KICAgbWFkZSBhbnkgaW5kZXBlbmRlbnQgZWZmb3J0IHRvIGlkZW50aWZ5IGFueSBz
dWNoIHJpZ2h0cy4gIEluZm9ybWF0aW9uIA0KICAgb24gdGhlIHByb2NlZHVyZXMgd2l0aCByZXNw
ZWN0IHRvIHJpZ2h0cyBpbiBSRkMgZG9jdW1lbnRzIGNhbiBiZSANCiAgIGZvdW5kIGluIEJDUCA3
OCBhbmQgQkNQIDc5LiANCg0KICAgQ29waWVzIG9mIElQUiBkaXNjbG9zdXJlcyBtYWRlIHRvIHRo
ZSBJRVRGIFNlY3JldGFyaWF0IGFuZCBhbnkgDQogICBhc3N1cmFuY2VzIG9mIGxpY2Vuc2VzIHRv
IGJlIG1hZGUgYXZhaWxhYmxlLCBvciB0aGUgcmVzdWx0IG9mIGFuIA0KICAgYXR0ZW1wdCBtYWRl
IHRvIG9idGFpbiBhIGdlbmVyYWwgbGljZW5zZSBvciBwZXJtaXNzaW9uIGZvciB0aGUgdXNlIG9m
IA0KICAgc3VjaCBwcm9wcmlldGFyeSByaWdodHMgYnkgaW1wbGVtZW50ZXJzIG9yIHVzZXJzIG9m
IHRoaXMgDQogDQogDQpZb29uLCBldCBhbC4gICAgICAgICAgIEV4cGlyZXMgSmFudWFyeSAyLCAy
MDA4ICAgICAgICAgICAgICAgIFtQYWdlIDVdIA0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICAg
ICAgIEFWVC1TRUVELVNSVFAgICAgICAgICAgICAgICAgIEp1bHkgMiwgMjAwNyANCiAgICANCg0K
ICAgc3BlY2lmaWNhdGlvbiBjYW4gYmUgb2J0YWluZWQgZnJvbSB0aGUgSUVURiBvbi1saW5lIElQ
UiByZXBvc2l0b3J5IGF0IA0KICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pcHIuIA0KDQogICBUaGUg
SUVURiBpbnZpdGVzIGFueSBpbnRlcmVzdGVkIHBhcnR5IHRvIGJyaW5nIHRvIGl0cyBhdHRlbnRp
b24gYW55IA0KICAgY29weXJpZ2h0cywgcGF0ZW50cyBvciBwYXRlbnQgYXBwbGljYXRpb25zLCBv
ciBvdGhlciBwcm9wcmlldGFyeSANCiAgIHJpZ2h0cyB0aGF0IG1heSBjb3ZlciB0ZWNobm9sb2d5
IHRoYXQgbWF5IGJlIHJlcXVpcmVkIHRvIGltcGxlbWVudCANCiAgIHRoaXMgc3RhbmRhcmQuICBQ
bGVhc2UgYWRkcmVzcyB0aGUgaW5mb3JtYXRpb24gdG8gdGhlIElFVEYgYXQgDQogICBpZXRmLWlw
ckBpZXRmLm9yZy4gDQoNCkRpc2NsYWltZXIgb2YgVmFsaWRpdHkgDQoNCiAgIFRoaXMgZG9jdW1l
bnQgYW5kIHRoZSBpbmZvcm1hdGlvbiBjb250YWluZWQgaGVyZWluIGFyZSBwcm92aWRlZCBvbiBh
biANCiAgICJBUyBJUyIgYmFzaXMgYW5kIFRIRSBDT05UUklCVVRPUiwgVEhFIE9SR0FOSVpBVElP
TiBIRS9TSEUgUkVQUkVTRU5UUyANCiAgIE9SIElTIFNQT05TT1JFRCBCWSAoSUYgQU5ZKSwgVEhF
IElOVEVSTkVUIFNPQ0lFVFksIFRIRSBJRVRGIFRSVVNUIEFORCANCiAgIFRIRSBJTlRFUk5FVCBF
TkdJTkVFUklORyBUQVNLIEZPUkNFIERJU0NMQUlNIEFMTCBXQVJSQU5USUVTLCBFWFBSRVNTIA0K
ICAgT1IgSU1QTElFRCwgSU5DTFVESU5HIEJVVCBOT1QgTElNSVRFRCBUTyBBTlkgV0FSUkFOVFkg
VEhBVCBUSEUgVVNFIE9GIA0KICAgVEhFIElORk9STUFUSU9OIEhFUkVJTiBXSUxMIE5PVCBJTkZS
SU5HRSBBTlkgUklHSFRTIE9SIEFOWSBJTVBMSUVEIA0KICAgV0FSUkFOVElFUyBPRiBNRVJDSEFO
VEFCSUxJVFkgT1IgRklUTkVTUyBGT1IgQSBQQVJUSUNVTEFSIFBVUlBPU0UuIA0KDQpDb3B5cmln
aHQgU3RhdGVtZW50IA0KDQogICBDb3B5cmlnaHQgKEMpIFRoZSBJRVRGIFRydXN0ICgyMDA3KS4g
DQoNCiAgIFRoaXMgZG9jdW1lbnQgaXMgc3ViamVjdCB0byB0aGUgcmlnaHRzLCBsaWNlbnNlcyBh
bmQgcmVzdHJpY3Rpb25zIA0KICAgY29udGFpbmVkIGluIEJDUCA3OCwgYW5kIGV4Y2VwdCBhcyBz
ZXQgZm9ydGggdGhlcmVpbiwgdGhlIGF1dGhvcnMgDQogICByZXRhaW4gYWxsIHRoZWlyIHJpZ2h0
cy4gDQoNCkFja25vd2xlZGdtZW50IA0KDQogICBGdW5kaW5nIGZvciB0aGUgUkZDIEVkaXRvciBm
dW5jdGlvbiBpcyBjdXJyZW50bHkgcHJvdmlkZWQgYnkgdGhlIA0KICAgSW50ZXJuZXQgU29jaWV0
eS4gDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQogDQogDQpZb29uLCBldCBhbC4gICAg
ICAgICAgIEV4cGlyZXMgSmFudWFyeSAyLCAyMDA4ICAgICAgICAgICAgICAgIFtQYWdlIDZdIA0K
DA0K
------=_Part_8038_25109992.1183359268364
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

------=_Part_8038_25109992.1183359268364--





From avt-bounces@ietf.org Mon Jul 02 22:04:46 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5Xky-0007Lv-BA; Mon, 02 Jul 2007 22:04:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5Xkw-0007Ld-JT
	for avt@ietf.org; Mon, 02 Jul 2007 22:04:42 -0400
Received: from mgw4.sony.co.jp ([137.153.0.46])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5Xk2-0007NR-M3
	for avt@ietf.org; Mon, 02 Jul 2007 22:04:42 -0400
Received: from mail2.sony.co.jp ([43.0.1.202])
Received: from mail2.sony.co.jp (localhost [127.0.0.1])
	by mail2.sony.co.jp (R8/Sony) with ESMTP id l6323in1010230;
	Tue, 3 Jul 2007 11:03:44 +0900 (JST)
Received: from bourbon.sm.sony.co.jp ([43.13.14.16])
	by mail2.sony.co.jp (R8/Sony) with ESMTP id l6323hg6010219;
	Tue, 3 Jul 2007 11:03:44 +0900 (JST)
Received: from [43.11.238.2] ([43.11.238.2])
	by bourbon.sm.sony.co.jp (8.14.1/8.14.1) with ESMTP id l632OrxJ004449; 
	Tue, 3 Jul 2007 11:24:53 +0900
Message-ID: <4689AE58.3040202@sm.sony.co.jp>
Date: Tue, 03 Jul 2007 11:03:04 +0900
From: Satoshi Futemma <satosi-f@sm.sony.co.jp>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Working group last call: JPEG-2000 payload format
References: <7634542FB03DC747813D67560802AEED9EB379@rennsmail05.eu.thmulti.com>	<465D8C51.4080805@ericsson.com>	<p06240817c28360afcce1@[17.202.35.52]>	<465E8514.9080503@ericsson.com>
	<4666DD9A.4161A698@erols.com>	<p06240887c28f9648fa12@[17.202.35.52]>	<61DDFB8A-8EA0-4F26-9610-9FCA7FD3633C@csperkins.org>	<46757295.C62C43BF@erols.com>
	<46767822.1060308@ericsson.com>	<p06240843c29d41cb741b@[17.202.35.52]>	<46779487.5060308@ericsson.com>	<85FF4F5B-138E-4788-8009-515DD4C17EBF@csperkins.org>	<4680C859.8050900@ericsson.com>
	<56F5C792-E7D8-4BA3-BA95-237AE487D937@csperkins.org>
In-Reply-To: <56F5C792-E7D8-4BA3-BA95-237AE487D937@csperkins.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: Andrew Leung <andrew@ualberta.net>, IETF AVT WG <avt@ietf.org>,
	ITAKURA Eisaburo <itakura@sm.sony.co.jp>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Dear Colin,

Thank you for the wrapping up.
I agree with you.

All right, I will submit a new draft soon.

Best Regards,

Futemma

Colin Perkins wrote:
> On 26 Jun 2007, at 09:03, Magnus Westerlund wrote:
>> Colin Perkins skrev:
>>> Wrapping up, I believe the rough consensus is that the JPEG-2000 
>>> draft should be updated to allow non-90kHz timestamp rates, as follows:
>>> - Senders and receivers MUST support a 90kHz RTP timestamp rate, and MAY
>>>   support other rates.
>>> - Senders SHOULD use 90kHz timestamp where possible, and the draft 
>>> needs to
>>>   be updated to include strong guidance on choosing the timestamp 
>>> rate, and
>>>   the implications of using a rate other than 90kHz.
>>> - The timestamp rate MUST be negotiated. The offer/answer considerations
>>>   should explain how this is done.
>>> - Senders that wish to use a non-90kHz rate SHOULD also offer the 
>>> same stream
>>>   using a 90kHz timestamp rate, with a different RTP payload type, e.g.:
>>>     m=video 5004 RTP/AVP 98 99
>>>     a=rtpmap:98 jpeg2000/90000
>>>     a=rtpmap:99 jpeg2000/27000000
>>>   allowing graceful fallback to 90kHz if the receiver doesn't support 
>>> the high
>>>   rate.
>>> To check the consensus, please reply to this message by the end of 
>>> this week, stating if you agree or disagree with this proposal, and 
>>> giving your reasons. Please do this even if you believe you have 
>>> already stated your preference.
>>
>> I am fine with this. However, I think the SDP example should switch 
>> the priority order of the two payload formats to indicate that one 
>> does like to use 27 MHz rather then 90k. So if including an example 
>> with this, change the m= line to:
>> m=video 5004 RTP/AVP 99 98
> 
> There seems to be consensus that more flexibility should be allowed in 
> the choice of timestamp rate for the JPEG2000 payload format.  Authors, 
> could you please therefore submit an update reflecting this.
> 
> Thanks,

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



From avt-bounces@ietf.org Tue Jul 03 03:56:22 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5dFC-0006HR-7A; Tue, 03 Jul 2007 03:56:18 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5dFB-00069z-Ac
	for avt@ietf.org; Tue, 03 Jul 2007 03:56:17 -0400
Received: from wa-out-1112.google.com ([209.85.146.180])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I5dFB-0003O8-1q
	for avt@ietf.org; Tue, 03 Jul 2007 03:56:17 -0400
Received: by wa-out-1112.google.com with SMTP id k17so3009197waf
	for <avt@ietf.org>; Tue, 03 Jul 2007 00:56:00 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=cX9s4mSyMa59VCTpgNSn/DZWfL3BMpO2cVEcdyuqduE5U7F5ftXiFm/Wi3y33Zru2wglsngrK6XmyF+SDS0eGe6HeVqRe51u49xZ1WRYiXhLOJM3rMJAUJ2UFZzFIQbpHnEM8to+FXKmP6XtUxjQhm4nYCaj5LRX/m7sQk+b/DU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=cMJOsAVGegYOZf9+Bw2fMmOxftslro8Qmzo99mDMvrO3YHIQVNdWQH3DMgVQM3NS5aR9+6TYUyl76hy9pvsIB4/vZ5qDPVUg7VzSNmjVWKqJ4IoKfrbPDpYYs6iP5yVgD8351lTXvAzP62MnUL3w6/DGDbKg0NW+ovHLlrM4vkw=
Received: by 10.114.178.1 with SMTP id a1mr5882265waf.1183449360105;
	Tue, 03 Jul 2007 00:56:00 -0700 (PDT)
Received: by 10.114.145.6 with HTTP; Tue, 3 Jul 2007 00:56:00 -0700 (PDT)
Message-ID: <7e4b541c0707030056j6e689a67i59515ae5d0440e45@mail.gmail.com>
Date: Tue, 3 Jul 2007 09:56:00 +0200
From: "Tom Kristensen" <2mkristensen@gmail.com>
To: avt@ietf.org
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-h264-params-00.txt
In-Reply-To: <E1I5UAf-0004rW-QS@stiedprstage1.ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <E1I5UAf-0004rW-QS@stiedprstage1.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On 03/07/07, Internet-Drafts@ietf.org <Internet-Drafts@ietf.org> wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Audio/Video Transport Working Group of the IETF.
>
>         Title           : Parameters for Static Macroblocks and Aspect Ratio
>                             in the RTP Payload Format for H.264 Video
>         Author(s)       : T. Kristensen, R. Even
>         Filename        : draft-ietf-avt-rtp-h264-params-00.txt
>         Pages           : 9
>         Date            : 2007-7-2
>
>    This document updates RFC 3984.  It defines new optional parameters
>    addressing recent extensions currently supported in H.323 systems:
>    The signalling of the maximum rate of static macroblocks a decoder is
>    able to process.  The signalling of the sample aspect ratio supported
>    by the sender or the receiver.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-h264-params-00.txt
[...]

AVT WG,

Changes from the predecessor draft-kristensen-avt-rtp-h264-params-00
was editorial changes to clarify and tighten the text. Also, the term
Picture Aspect Ratio (PAR) was introduced to explicitly distinguish
this aspect ratio from the Sample Aspect Ratio (SAR).

No specific open issues to address are known. However, comments on
clarity of the text and the structure of the specification are
welcome.

Section 4.3 will include som examples to guide the reader in upcoming versions.

-- Tom

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

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



From avt-bounces@ietf.org Tue Jul 03 08:02:31 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5h5O-000887-8H; Tue, 03 Jul 2007 08:02:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5h5N-00087p-29
	for avt@ietf.org; Tue, 03 Jul 2007 08:02:25 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5h4o-0007Fl-3q
	for avt@ietf.org; Tue, 03 Jul 2007 08:02:25 -0400
Received: from vpn14.dcs.gla.ac.uk ([130.209.254.14]:60028)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1I5h4n-0007ur-Nm for avt@ietf.org; Tue, 03 Jul 2007 13:01:49 +0100
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <76F8978B-FE49-4AA3-B366-0436C42A408D@csperkins.org>
References: <E1I3JrG-0001QD-6Q@stiedprstage1.ietf.org>
	<76F8978B-FE49-4AA3-B366-0436C42A408D@csperkins.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <CB20FA2E-1A0B-4DA1-9C0E-571F44B1132B@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Working group last call: draft-ietf-avt-rtp-vorbis-06.txt 
Date: Tue, 3 Jul 2007 13:01:51 +0100
To: AVT WG <avt@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On 27 Jun 2007, at 12:08, Colin Perkins wrote:
> On 26 Jun 2007, at 23:50, Internet-Drafts@ietf.org wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Audio/Video Transport Working  
>> Group of the IETF.
>>
>> 	Title		: RTP Payload Format for Vorbis Encoded Audio
>> 	Author(s)	: L. Barbato
>> 	Filename	: draft-ietf-avt-rtp-vorbis-06.txt
>> 	Pages		: 25
>> 	Date		: 2007-6-26
>> 	
>> This document describes an RTP payload format for transporting Vorbis
>>    encoded audio.  It details the RTP encapsulation mechanism for raw
>>    Vorbis data and details the delivery mechanisms for the decoder
>>    probability model, referred to as a codebook and other setup
>>    information.
>>
>>    Also included within this memo are media type registrations,  
>> and the
>>    details necessary for the use of Vorbis with the Session  
>> Description
>>    Protocol (SDP).
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-vorbis-06.txt
>
> We believe this addresses the last call comments received on the  
> -05 draft. If you made comments on that draft, please confirm that  
> they have been addressed. Also, if there are any other final  
> comments, please send them to the list. If there are no objections,  
> we will send this draft to the IESG to consider for publication as  
> a proposed standard RFC on 3rd July.

There were no objections, so we will now request the IESG publish  
this draft as a proposed standard RFC.

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



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



From avt-bounces@ietf.org Tue Jul 03 08:04:17 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5h7A-000362-7c; Tue, 03 Jul 2007 08:04:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5dbj-0006po-65
	for avt@ietf.org; Tue, 03 Jul 2007 04:19:35 -0400
Received: from mail5.audiocodes.com ([212.25.125.21] helo=imss.audiocodes.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5db4-00040i-PP
	for avt@ietf.org; Tue, 03 Jul 2007 04:19:34 -0400
Received: from aclcas.corp.audiocodes.com ([10.1.0.13]) by imss with InterScan
	Messaging Security Suite; Tue, 03 Jul 2007 10:28:11 +0200
Received: from aclmailbox.corp.audiocodes.com ([10.1.1.48]) by
	aclcas.corp.audiocodes.com ([10.1.0.13]) with mapi;
	Tue, 3 Jul 2007 11:19:24 +0300
From: Shahaf Rozanski <Shahaf.Rozanski@audiocodes.com>
To: "avt@ietf.org" <avt@ietf.org>
Date: Tue, 3 Jul 2007 11:16:47 +0300
Thread-Topic: Determining the desired transmitted resolution and frame rate
	when using H.264 
Thread-Index: Ace9Sn+py2yb0KK4QwWYjr7tSMXIMg==
Message-ID: <270A8A26F088AE4DA76B5B7EC6B1CD1A06D74E35@aclmailbox.corp.audiocodes.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
X-Mailman-Approved-At: Tue, 03 Jul 2007 08:04:14 -0400
Cc: Yuval Nissan <Yuval.Nissan@audiocodes.com>,
	Keren Malachi <Keren.Malachi@audiocodes.com>
Subject: [AVT] Determining the desired transmitted resolution and frame rate
 when using H.264 
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="===============0929720983=="
Errors-To: avt-bounces@ietf.org

--===============0929720983==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_270A8A26F088AE4DA76B5B7EC6B1CD1A06D74E35aclmailboxcorpa_"

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

Hi,

In the SDP negotiation each agent declares it supported receive capabilitie=
s. For H.264 it can be done using the profile-level-id mechanism suggested =
in RFC 3984.
Let's assume that the offerer declared baseline profile level 1.1. As a res=
ult he is willing to receive different configuration e.g. up to CIF resolut=
ion with 7.5 FPS or up to QCIF with 30 FPS.
Is there a method for the offerer to hint the answerer that he would like t=
o receive in a specific configuration (e.g. QCIF 30FPS)?
This can be useful if the offerer is a UE that is best suited for QCIF reso=
lutions.

Thanks,
Shahaf

--_000_270A8A26F088AE4DA76B5B7EC6B1CD1A06D74E35aclmailboxcorpa_
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:sc=
hemas-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";}
p.MsoToc1, li.MsoToc1, div.MsoToc1
	{margin:0in;
	margin-bottom:.0001pt;
	line-height:150%;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:bold;}
p.MsoToc2, li.MsoToc2, div.MsoToc2
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:12.0pt;
	margin-bottom:.0001pt;
	line-height:150%;
	font-size:12.0pt;
	font-family:Arial;}
p.MsoToc3, li.MsoToc3, div.MsoToc3
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:24.0pt;
	margin-bottom:.0001pt;
	line-height:150%;
	font-size:12.0pt;
	font-family:Arial;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle20
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:1.0in 1.25in 1.0in 81.35pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1 dir=3DRTL>

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

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

<p class=3DMsoNormal dir=3DLTR><font size=3D2 face=3DArial><span style=3D'f=
ont-size:10.0pt;
font-family:Arial'>In the SDP negotiation each agent declares it supported =
receive
capabilities. For H.264 it can be done using the profile-level-id mechanism
suggested in RFC 3984.<o:p></o:p></span></font></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 face=3DArial><span style=3D'f=
ont-size:10.0pt;
font-family:Arial'>Let&#8217;s assume that the offerer declared baseline
profile level 1.1. As a result he is willing to receive different configura=
tion
e.g. up to CIF resolution with 7.5 FPS or up to QCIF with 30 FPS.<o:p></o:p=
></span></font></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 face=3DArial><span style=3D'f=
ont-size:10.0pt;
font-family:Arial'>Is there a method for the offerer to hint the answerer t=
hat
he would like to receive in a specific configuration (e.g. QCIF 30FPS)?<o:p=
></o:p></span></font></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 face=3DArial><span style=3D'f=
ont-size:10.0pt;
font-family:Arial'>This can be useful if the offerer is a UE that is best
suited for QCIF resolutions. <o:p></o:p></span></font></p>

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

<p class=3DMsoNormal dir=3DLTR><font size=3D2 face=3DArial><span style=3D'f=
ont-size:10.0pt;
font-family:Arial'>Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 face=3DArial><span style=3D'f=
ont-size:10.0pt;
font-family:Arial'>Shahaf<o:p></o:p></span></font></p>

</div>

</body>

</html>

--_000_270A8A26F088AE4DA76B5B7EC6B1CD1A06D74E35aclmailboxcorpa_--


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

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

--===============0929720983==--




From avt-bounces@ietf.org Tue Jul 03 08:48:33 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5ho0-0004KX-5f; Tue, 03 Jul 2007 08:48:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5hnx-0004KJ-W8; Tue, 03 Jul 2007 08:48:30 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I5hnt-0007gq-85; Tue, 03 Jul 2007 08:48:29 -0400
Received: from vpn14.dcs.gla.ac.uk ([130.209.254.14]:60112)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1I5hnr-0008OO-Kt; Tue, 03 Jul 2007 13:48:23 +0100
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <EF51BD62-164D-4606-98BB-F0B708BDD400@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Tue, 3 Jul 2007 13:48:24 +0100
To: Cullen Jennings <fluffy@cisco.com>,
 via RT <iesg-secretary@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 86f85b2f88b0d50615aed44a7f9e33c7
Cc: Roni Even <roni.even@polycom.co.il>, Tom Taylor <tom.taylor@rogers.com>,
	AVT WG <avt@ietf.org>
Subject: [AVT] Request to publish draft-ietf-avt-vorbis-rtp-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>
Errors-To: avt-bounces@ietf.org

The Audio/Video Transport working group requests that the RTP Payload  
Format for Vorbis Encoded Audio <draft-ietf-avt-rtp-vorbis-06.txt> be  
published as a Proposed Standard RFC.

Document Shepherd Write-Up:

    (1.a)  Who is the Document Shepherd for this document?  Has the
           Document Shepherd personally reviewed this version of the
           document and, in particular, does he or she believe this
           version is ready for forwarding to the IESG for publication?

The document shepherd is Colin Perkins. He believes this version is  
ready for publication.

    (1.b)  Has the document had adequate review both from key WG members
           and from key non-WG members?  Does the Document Shepherd have
           any concerns about the depth or breadth of the reviews that
           have been performed?

The document has had adequate review.

    (1.c)  Does the Document Shepherd have concerns that the document
           needs more review from a particular or broader perspective,
           e.g., security, operational complexity, someone familiar with
           AAA, internationalization or XML?

No concerns.

    (1.d)  Does the Document Shepherd have any specific concerns or
           issues with this document that the Responsible Area Director
           and/or the IESG should be aware of?  For example, perhaps he
           or she is uncomfortable with certain parts of the  
document, or
           has concerns whether there really is a need for it.  In any
           event, if the WG has discussed those issues and has indicated
           that it still wishes to advance the document, detail those
           concerns here.  Has an IPR disclosure related to this  
document
           been filed?  If so, please include a reference to the
           disclosure and summarize the WG discussion and conclusion on
           this issue.

No concerns. No IPR disclosures.

    (1.e)  How solid is the WG consensus behind this document?  Does it
           represent the strong concurrence of a few individuals, with
           others being silent, or does the WG as a whole understand and
           agree with it?

There is solid consensus.

    (1.f)  Has anyone threatened an appeal or otherwise indicated  
extreme
           discontent?  If so, please summarise the areas of conflict in
           separate email messages to the Responsible Area Director.   
(It
           should be in a separate email because this questionnaire is
           entered into the ID Tracker.)

No.

    (1.g)  Has the Document Shepherd personally verified that the
           document satisfies all ID nits?  (See
           http://www.ietf.org/ID-Checklist.html and
           http://tools.ietf.org/tools/idnits/).  Boilerplate checks are
           not enough; this check needs to be thorough.  Has the  
document
           met all formal review criteria it needs to, such as the MIB
           Doctor, media type and URI type reviews?

The document satisfies all ID nits. A media type review was conducted.

    (1.h)  Has the document split its references into normative and
           informative?  Are there normative references to documents  
that
           are not ready for advancement or are otherwise in an unclear
           state?  If such normative references exist, what is the
           strategy for their completion?  Are there normative  
references
           that are downward references, as described in [RFC3967]?  If
           so, list these downward references to support the Area
           Director in the Last Call procedure for them [RFC3967].

References have been split. There are no normative references to  
internet drafts, and no normative down-references.

    (1.i)  Has the Document Shepherd verified that the document IANA
           consideration section exists and is consistent with the body
           of the document?  If the document specifies protocol
           extensions, are reservations requested in appropriate IANA
           registries?  Are the IANA registries clearly identified?  If
           the document creates a new registry, does it define the
           proposed initial contents of the registry and an allocation
           procedure for future registrations?  Does it suggest a
           reasonable name for the new registry?  See [RFC2434].  If the
           document describes an Expert Review process has Shepherd
           conferred with the Responsible Area Director so that the IESG
           can appoint the needed Expert during the IESG Evaluation?

The IANA considerations section exists, and is consistent with the  
rest of the draft. Registrations are in the appropriate registry.

    (1.j)  Has the Document Shepherd verified that sections of the
           document that are written in a formal language, such as XML
           code, BNF rules, MIB definitions, etc., validate correctly in
           an automated checker?

n/a

    (1.k)  The IESG approval announcement includes a Document
           Announcement Write-Up.  Please provide such a Document
           Announcement Write-Up?  Recent examples can be found in the
           "Action" announcements for approved documents.  The approval
           announcement contains the following sections:

           Technical Summary
              Relevant content can frequently be found in the abstract
              and/or introduction of the document.  If not, this may be
              an indication that there are deficiencies in the abstract
              or introduction.

    This document describes an RTP payload format for transporting  
Vorbis
    encoded audio.  It details the RTP encapsulation mechanism for raw
    Vorbis data and details the delivery mechanisms for the decoder
    probability model, referred to as a codebook and other setup
    information.

    Also included within this memo are media type registrations, and the
    details necessary for the use of Vorbis with the Session Description
    Protocol (SDP).


           Working Group Summary
              Was there anything in WG process that is worth noting?   
For
              example, was there controversy about particular points or
              were there decisions where the consensus was particularly
              rough?

The RTP payload format for Vorbis has been under discussion since the  
50th IETF meeting and has changed author several times (which has  
delayed its progress). The main technical issue has been transport of  
configuration headers: Vorbis doesn't use statically configured code  
books, and must receive a configuration header containing appropriate  
code books for a stream before it can begin decoding. This is  
problematic for RTP sessions using unreliable transports with limited  
packet size, and required definition of both in-band and out-of-band  
access methods for configuration headers, to ensure the configured  
data can be retrieved.

           Document Quality
              Are there existing implementations of the protocol?   
Have a
              significant number of vendors indicated their plan to
              implement the specification?  Are there any reviewers that
              merit special mention as having done a thorough review,
              e.g., one that resulted in important changes or a
              conclusion that the document had no substantive  
issues?  If
              there was a MIB Doctor, Media Type or other expert review,
              what was its course (briefly)?  In the case of a Media  
Type
              review, on what date was the request posted?

I understand that there are a number of implementations.

The media type review request was posted 11 June 2007. During the  
media type review, Bjoern Hoehrmann and Chris Lilley expressed  
concern that this draft registers the audio/vorbis media type for use  
only with RTP. We believe this concern is misplaced, since Vorbis  
data must be framed (the application/ogg container provides the  
framing for non-RTP use) and the registration of an RTP-only media  
type is consistent with current practice, as documented in RFC 4855.

           Personnel
              Who is the Document Shepherd for this document?  Who is  
the
              Responsible Area Director?

Colin Perkins is the document shepherd. Cullen Jennings is a  
responsible area director.

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



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



From avt-bounces@ietf.org Tue Jul 03 09:54:48 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5iq6-0005nA-R7; Tue, 03 Jul 2007 09:54:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5iq4-0005ee-JS; Tue, 03 Jul 2007 09:54:44 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I5ipa-0007jZ-4p; Tue, 03 Jul 2007 09:54:44 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 0C67026EC0;
	Tue,  3 Jul 2007 13:54:14 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I5ipZ-0005Xx-U5; Tue, 03 Jul 2007 09:54:13 -0400
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1I5ipZ-0005Xx-U5@stiedprstage1.ietf.org>
Date: Tue, 03 Jul 2007 09:54:13 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: avt@ietf.org
Subject: [AVT] Last Call: draft-ietf-avt-rtp-and-rtcp-mux (Multiplexing RTP 
 Data and Control Packets on a Single Port) to Proposed Standard 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ietf@ietf.org
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

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

- 'Multiplexing RTP Data and Control Packets on a Single Port '
   <draft-ietf-avt-rtp-and-rtcp-mux-05.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 substantive comments to the
ietf@ietf.org mailing lists by 2007-07-17. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-and-rtcp-mux-05.txt



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


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



From avt-bounces@ietf.org Tue Jul 03 10:15:45 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5jAN-0002BD-FV; Tue, 03 Jul 2007 10:15:43 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5jAH-0001wv-57; Tue, 03 Jul 2007 10:15:37 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I5jAG-0007hA-Tk; Tue, 03 Jul 2007 10:15:37 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id CB8AB2AC75;
	Tue,  3 Jul 2007 14:15:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I5j9h-0006IA-Hu; Tue, 03 Jul 2007 10:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I5j9h-0006IA-Hu@stiedprstage1.ietf.org>
Date: Tue, 03 Jul 2007 10:15:01 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-dtls-srtp-00.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: Datagram Transport Layer Security (DTLS) Extension to Establish Keys for Secure Real-time Transport Protocol (SRTP)
	Author(s)	: D. McGrew, E. Rescorla
	Filename	: draft-ietf-avt-dtls-srtp-00.txt
	Pages		: 24
	Date		: 2007-7-3
	
   The Secure Real-time Transport Protocol (SRTP) is a profile of the
   Real-time Transport Protocol that can provide confidentiality,
   message authentication, and replay protection to the RTP traffic and
   to the control traffic for RTP, the Real-time Transport Control
   Protocol (RTCP).  This document describes a method of using DTLS key
   management for SRTP by using a new extension that indicates that SRTP
   is to be used for data protection, and which establishes SRTP keys.




A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-dtls-srtp-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-dtls-srtp-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-dtls-srtp-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

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

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

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

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

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

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


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org Tue Jul 03 11:32:04 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5kMC-0001nD-Cn; Tue, 03 Jul 2007 11:32:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5kMB-0001n5-L6
	for avt@ietf.org; Tue, 03 Jul 2007 11:31:59 -0400
Received: from pne-smtpout2-sn1.fre.skanova.net ([81.228.11.159])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5kLw-00060y-5W
	for avt@ietf.org; Tue, 03 Jul 2007 11:31:59 -0400
Received: from GunnarH (213.64.232.214) by pne-smtpout2-sn1.fre.skanova.net
	(7.2.075) id 4668007E005DBEC8; Tue, 3 Jul 2007 17:31:43 +0200
Message-ID: <4668007E005DBEC8@pne-smtpout2-sn1.fre.skanova.net> (added by
	postmaster@pne.skanova.net)
From: =?iso-8859-1?Q?Gunnar_Hellstr=F6m?= <gunnar.hellstrom@omnitor.se>
To: "'Shahaf Rozanski'" <Shahaf.Rozanski@audiocodes.com>,
	<avt@ietf.org>
Subject: RE: [AVT] Determining the desired transmitted resolution and frame
	rate when using H.264 
Date: Tue, 3 Jul 2007 17:31:48 +0200
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
thread-index: Ace9Sn+py2yb0KK4QwWYjr7tSMXIMgAPA7KA
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
In-Reply-To: <270A8A26F088AE4DA76B5B7EC6B1CD1A06D74E35@aclmailbox.corp.audiocodes.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8a4bcf8f67063cac573319207fe3db35
Cc: 'Yuval Nissan' <Yuval.Nissan@audiocodes.com>,
	'Keren Malachi' <Keren.Malachi@audiocodes.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>
Content-Type: multipart/mixed; boundary="===============0311815593=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0311815593==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_05F5_01C7BD98.09539620"

This is a multi-part message in MIME format.

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

Shahaf,
This is an important question.=20
Not only for the UA, but for the user.
For example a sign language user will experience CIF 7.5 fps totally
unusable, while QCIF 30 fps is quite good and conveys everything except =
the
most fine expressions of sign language.
=20
So, it is very desirable that UA:s are configurable to express the
preference.
=20
I rapidly checked RFC 4629 for H.263, and found in section 8.2.1 about =
the
Offer-answer model, the following sentence:
=20
"=20

   Parameters offered first are the most preferred picture mode to be
   received.
"

Please check RFC 3984 for a similar statement. I guess it is there.

=20

/Gunnar

=20
-------------------------------------------------------------------
Gunnar Hellstr=F6m
Omnitor
gunnar.hellstrom@omnitor.se
  _____ =20

From: Shahaf Rozanski [mailto:Shahaf.Rozanski@audiocodes.com]=20
Sent: Tuesday, July 03, 2007 10:17 AM
To: avt@ietf.org
Cc: Yuval Nissan; Keren Malachi
Subject: [AVT] Determining the desired transmitted resolution and frame =
rate
when using H.264=20



Hi,

=20

In the SDP negotiation each agent declares it supported receive
capabilities. For H.264 it can be done using the profile-level-id =
mechanism
suggested in RFC 3984.

Let=92s assume that the offerer declared baseline profile level 1.1. As =
a
result he is willing to receive different configuration e.g. up to CIF
resolution with 7.5 FPS or up to QCIF with 30 FPS.

Is there a method for the offerer to hint the answerer that he would =
like to
receive in a specific configuration (e.g. QCIF 30FPS)?

This can be useful if the offerer is a UE that is best suited for QCIF
resolutions.=20

=20

Thanks,

Shahaf



__________ NOD32 2372 (20070703) Information __________

Detta meddelande dr genomsvkt av NOD32 Antivirus.
http://www.nod32.com


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR>
<STYLE>@page Section1 {size: 595.3pt 841.9pt; margin: 1.0in 1.25in 1.0in =
81.35pt; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
P.MsoToc1 {
	FONT-WEIGHT: bold; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: =
150%; FONT-FAMILY: Arial
}
LI.MsoToc1 {
	FONT-WEIGHT: bold; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: =
150%; FONT-FAMILY: Arial
}
DIV.MsoToc1 {
	FONT-WEIGHT: bold; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: =
150%; FONT-FAMILY: Arial
}
P.MsoToc2 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt 12pt; LINE-HEIGHT: 150%; =
FONT-FAMILY: Arial
}
LI.MsoToc2 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt 12pt; LINE-HEIGHT: 150%; =
FONT-FAMILY: Arial
}
DIV.MsoToc2 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt 12pt; LINE-HEIGHT: 150%; =
FONT-FAMILY: Arial
}
P.MsoToc3 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt 24pt; LINE-HEIGHT: 150%; =
FONT-FAMILY: Arial
}
LI.MsoToc3 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt 24pt; LINE-HEIGHT: 150%; =
FONT-FAMILY: Arial
}
DIV.MsoToc3 {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt 24pt; LINE-HEIGHT: 150%; =
FONT-FAMILY: Arial
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle20 {
	COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D968412615-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Shahaf,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D968412615-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>This is an important question. =
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D968412615-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Not only for the UA, but for the =
user.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D968412615-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>For example a sign language user will =
experience CIF 7.5=20
fps totally unusable, while QCIF 30 fps is quite good and conveys =
everything=20
except the most fine expressions of sign language.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D968412615-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D968412615-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>So, it is very desirable that UA:s are =
configurable to=20
express the preference.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D968412615-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D968412615-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I rapidly checked RFC 4629 for H.263, and found =
in section=20
8.2.1 about the Offer-answer model, the following =
sentence:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D968412615-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D968412615-03072007><FONT =
color=3D#0000ff><FONT=20
face=3DArial size=3D2>"</FONT>
<P class=3DMsoPlainText style=3D"MARGIN: 0cm 0cm 0pt"><SPAN =
lang=3DEN-GB><FONT=20
face=3DArial><FONT size=3D2><FONT color=3D#000000><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp; </SPAN>Parameters offered first =
are the=20
most preferred picture mode to be<BR><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>received.</FONT><BR><SPAN=20
class=3D968412615-03072007>"</SPAN></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0cm 0cm 0pt"><SPAN =
lang=3DEN-GB><FONT=20
face=3DArial><FONT size=3D2><SPAN class=3D968412615-03072007>Please =
check RFC 3984 for=20
a similar statement. I guess it is =
there.</SPAN></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0cm 0cm 0pt"><SPAN =
lang=3DEN-GB><FONT=20
face=3DArial><FONT size=3D2><SPAN=20
class=3D968412615-03072007></SPAN></FONT></FONT></SPAN>&nbsp;</P>
<P class=3DMsoPlainText style=3D"MARGIN: 0cm 0cm 0pt"><SPAN =
lang=3DEN-GB><FONT=20
face=3DArial><FONT size=3D2><SPAN=20
class=3D968412615-03072007>/Gunnar</SPAN></FONT></FONT></SPAN></P></FONT>=
</SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial=20
size=3D2>----------------------------------------------------------------=
---</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Gunnar =
Hellstr=F6m</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Omnitor</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><A=20
href=3D"mailto:gunnar.hellstrom@omnitor.se">gunnar.hellstrom@omnitor.se</=
A></FONT></DIV>
<DIV class=3DOutlookMessageHeader lang=3Dsv dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Shahaf Rozanski=20
[mailto:Shahaf.Rozanski@audiocodes.com] <BR><B>Sent:</B> Tuesday, July =
03, 2007=20
10:17 AM<BR><B>To:</B> avt@ietf.org<BR><B>Cc:</B> Yuval Nissan; Keren=20
Malachi<BR><B>Subject:</B> [AVT] Determining the desired transmitted =
resolution=20
and frame rate when using H.264 <BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1 dir=3Drtl>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Hi,<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">In the SDP negotiation =
each agent=20
declares it supported receive capabilities. For H.264 it can be done =
using the=20
profile-level-id mechanism suggested in RFC =
3984.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Let=92s assume that the =
offerer=20
declared baseline profile level 1.1. As a result he is willing to =
receive=20
different configuration e.g. up to CIF resolution with 7.5 FPS or up to =
QCIF=20
with 30 FPS.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Is there a method for the =
offerer to=20
hint the answerer that he would like to receive in a specific =
configuration=20
(e.g. QCIF 30FPS)?<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">This can be useful if the =
offerer is=20
a UE that is best suited for QCIF resolutions. =
<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Thanks,<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Shahaf<o:p></o:p></SPAN></FONT></P></DIV><BR><BR>__________=20
NOD32 2372 (20070703) Information __________<BR><BR>Detta meddelande dr=20
genomsvkt av NOD32 Antivirus.<BR><A=20
href=3D"http://www.nod32.com">http://www.nod32.com</A><BR></BODY></HTML>

------=_NextPart_000_05F5_01C7BD98.09539620--



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

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

--===============0311815593==--





From avt-bounces@ietf.org Tue Jul 03 11:55:56 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5kjK-0007bX-0z; Tue, 03 Jul 2007 11:55:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5kjI-0007bI-3C
	for avt@ietf.org; Tue, 03 Jul 2007 11:55:52 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5kiJ-0001h7-2V
	for avt@ietf.org; Tue, 03 Jul 2007 11:55:52 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [AVT] Determining the desired transmitted resolution and frame
	rate when using H.264 
Date: Tue, 3 Jul 2007 18:55:42 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04B8F502@IsrExch01.israel.polycom.com>
In-Reply-To: <270A8A26F088AE4DA76B5B7EC6B1CD1A06D74E35@aclmailbox.corp.audiocodes.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Determining the desired transmitted resolution and frame
	rate when using H.264 
Thread-Index: Ace9Sn+py2yb0KK4QwWYjr7tSMXIMgAPzomA
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Shahaf Rozanski" <Shahaf.Rozanski@audiocodes.com>,
	<avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e16ce0269ccb2f59707d16700199d13b
Cc: Yuval Nissan <Yuval.Nissan@audiocodes.com>,
	Keren Malachi <Keren.Malachi@audiocodes.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>
Content-Type: multipart/mixed; boundary="===============0129877972=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0129877972==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7BD8A.B2F4A6D8"

This is a multi-part message in MIME format.

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

Hi,

H.264 does not have the definition of fixed frame sizes. The level gives
some maximum values which enable you to estimate the maximum size of the
frame and the frame rate.

Using max-mbps, max-fs you can override the level parameters. Still this
does not allow you to request a specific resolution or number of macro
b;ocks per second.

There is currently work done at the ITU on defining additional
parameters to H.241 in order to allow such functionality and after it is
done there I assume we will try to update RFC 3984 with this
functionality.

=20

BTW: there are some new parameters now in
draft-ietf-avt-rtp-h264-params-00 and you should look at it.

Roni Even

=20

________________________________

From: Shahaf Rozanski [mailto:Shahaf.Rozanski@audiocodes.com]=20
Sent: Tuesday, July 03, 2007 11:17 AM
To: avt@ietf.org
Cc: Yuval Nissan; Keren Malachi
Subject: [AVT] Determining the desired transmitted resolution and frame
rate when using H.264=20

=20

Hi,

=20

In the SDP negotiation each agent declares it supported receive
capabilities. For H.264 it can be done using the profile-level-id
mechanism suggested in RFC 3984.

Let's assume that the offerer declared baseline profile level 1.1. As a
result he is willing to receive different configuration e.g. up to CIF
resolution with 7.5 FPS or up to QCIF with 30 FPS.

Is there a method for the offerer to hint the answerer that he would
like to receive in a specific configuration (e.g. QCIF 30FPS)?

This can be useful if the offerer is a UE that is best suited for QCIF
resolutions.=20

=20

Thanks,

Shahaf


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoToc1, li.MsoToc1, div.MsoToc1
	{margin:0cm;
	margin-bottom:.0001pt;
	line-height:150%;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:bold;}
p.MsoToc2, li.MsoToc2, div.MsoToc2
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:12.0pt;
	margin-bottom:.0001pt;
	line-height:150%;
	font-size:12.0pt;
	font-family:Arial;}
p.MsoToc3, li.MsoToc3, div.MsoToc3
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:24.0pt;
	margin-bottom:.0001pt;
	line-height:150%;
	font-size:12.0pt;
	font-family:Arial;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:72.0pt 90.0pt 72.0pt 81.35pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1 dir=3DRTL>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Hi,<o:p></o:p></s=
pan></font></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>H.264 does not =
have the
definition of fixed frame sizes. The level gives some maximum values =
which
enable you to estimate the maximum size of the frame and the frame =
rate.<o:p></o:p></span></font></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Using =
</span></font>max-mbps,
max-fs you can override the level parameters. Still this does not allow =
you to
request a specific resolution or number of macro b;ocks per =
second.<o:p></o:p></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D3 face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt'>There is currently work done at the ITU on =
defining
additional parameters to H.241 in order to allow such functionality and =
after
it is done there I assume we will try to update RFC 3984 with this
functionality.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal dir=3DLTR><font size=3D3 face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt'>BTW: there are some new parameters now in =
draft-ietf-avt-rtp-h264-params-00
and you should look at it.<o:p></o:p></span></font></p>

<p class=3DMsoNormal dir=3DLTR><st1:PersonName ProductID=3D"Roni Even" =
w:st=3D"on"><font
 size=3D3 face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>Roni =
Even</span></font></st1:PersonName><o:p></o:p></p>

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

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

<div>

<div class=3DMsoNormal align=3Dcenter dir=3DLTR =
style=3D'text-align:center'><font
size=3D3 face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

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

</span></font></div>

<p class=3DMsoNormal dir=3DLTR><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> Shahaf
Rozanski [mailto:Shahaf.Rozanski@audiocodes.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, July 03, =
2007 11:17
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> avt@ietf.org<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> Yuval Nissan; Keren =
Malachi<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [AVT] =
Determining the
desired transmitted resolution and frame rate when using H.264 =
</span></font><o:p></o:p></p>

</div>

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

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

<p class=3DMsoNormal dir=3DLTR><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 dir=3DLTR><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>In the SDP negotiation each agent declares it =
supported
receive capabilities. For H.264 it can be done using the =
profile-level-id
mechanism suggested in RFC 3984.<o:p></o:p></span></font></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Let&#8217;s assume that the offerer declared baseline
profile level 1.1. As a result he is willing to receive different =
configuration
e.g. up to CIF resolution with 7.5 FPS or up to QCIF with 30 =
FPS.<o:p></o:p></span></font></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Is there a method for the offerer to hint the =
answerer that
he would like to receive in a specific configuration (e.g. QCIF =
30FPS)?<o:p></o:p></span></font></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>This can be useful if the offerer is a UE that is =
best
suited for QCIF resolutions. <o:p></o:p></span></font></p>

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

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

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C7BD8A.B2F4A6D8--


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

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

--===============0129877972==--




From avt-bounces@ietf.org Tue Jul 03 14:03:47 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5mix-0005lI-GY; Tue, 03 Jul 2007 14:03:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5miv-0005l7-SE
	for avt@ietf.org; Tue, 03 Jul 2007 14:03:37 -0400
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I5mir-0002yS-J0 for avt@ietf.org; Tue, 03 Jul 2007 14:03:37 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 3 Jul 2007 14:03:33 -0400
To: "Even, Roni" <roni.even@polycom.co.il>
Subject: Re: [AVT] Determining the desired transmitted resolution and frame
	rate when using H.264
References: <144ED8561CE90C41A3E5908EDECE315C04B8F502@IsrExch01.israel.polycom.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Tue, 03 Jul 2007 14:03:30 -0400
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C04B8F502@IsrExch01.israel.polycom.com>
	(Roni Even's message of "Tue, 3 Jul 2007 18:55:42 +0300")
Message-ID: <ybu8x9xcqkt.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 03 Jul 2007 18:03:33.0025 (UTC)
	FILETIME=[78109910:01C7BD9C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: Keren Malachi <Keren.Malachi@audiocodes.com>,
	Yuval Nissan <Yuval.Nissan@audiocodes.com>, avt@ietf.org,
	Shahaf Rozanski <Shahaf.Rozanski@audiocodes.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

"Even, Roni" <roni.even@polycom.co.il> writes:
>H.264 does not have the definition of fixed frame sizes. The level gives
>some maximum values which enable you to estimate the maximum size of the
>frame and the frame rate.

The problem (as Roni states) is that while the profile/etc may determine
the base ability to decode (horsepower, memory, etc), often the decoded
video is fed to devices that cannot render/display arbitrary resolutions
(and not just the aspect ratio issue which is currently under discussion).
In theory, a device can probably always display the video in some manner,
but it may not be a usable/useful manner (cropping or adding (large) areas
of black).  Not all devices will have an arbitrary scaler, or even a scaler
at all, or they may only have fixed scalers to choose from, or may not have
the horsepower to run a scaler while doing max-mbps encode/decode.

>Using max-mbps, max-fs you can override the level parameters. Still this
>does not allow you to request a specific resolution or number of macro
>b;ocks per second.

Right, not even to express a preference or tradeoff.  MAYBE you could do a
little of it using capability negotiation - if the other side understood
what you're trying to do.

>There is currently work done at the ITU on defining additional
>parameters to H.241 in order to allow such functionality and after it is
>done there I assume we will try to update RFC 3984 with this
>functionality.

Where is this being done?  Wouldn't it make sense to add input from the
IETF side now, so that when everyone is done there's a reasonable mapping
back and forth?

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


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



From avt-bounces@ietf.org Tue Jul 03 15:08:27 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5njc-0000PP-2i; Tue, 03 Jul 2007 15:08:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5nja-0000Le-V4
	for avt@ietf.org; Tue, 03 Jul 2007 15:08:22 -0400
Received: from maildialog.com ([195.159.98.119])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5njS-0000XV-Cc
	for avt@ietf.org; Tue, 03 Jul 2007 15:08:22 -0400
Received: from cm-84.215.127.238.chello.no ([84.215.127.238] helo=[10.0.0.4])
	by maildialog.com with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.51-maildialog)
	id 1I5njR-0000N9-QV; Tue, 03 Jul 2007 19:08:14 +0000
Message-ID: <468A9F0D.3080203@db.org>
Date: Tue, 03 Jul 2007 21:10:05 +0200
From: "Alfred E. Heggestad" <aeh@db.org>
User-Agent: Icedove 1.5.0.12 (X11/20070606)
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] draft-ietf-avt-rtp-speex-02.txt
References: <E1Hxptq-000574-Cb@stiedprstage1.ietf.org>	<1DE870BB-8980-46E8-A43D-5377BD6106CD@csperkins.org>	<46752BBE.5090802@db.org>
	<ybutzt4ldb7.fsf@jesup.eng.wgate.com>	<Pine.LNX.4.63.0706191043000.28061@sip2>	<Pine.LNX.4.63.0706191055210.28061@sip2>	<DD8DDC46-4F18-4D66-939B-45C23209F855@csperkins.org>
	<7594FE67-7B87-4856-B462-0087E32F0B39@csperkins.org>
In-Reply-To: <7594FE67-7B87-4856-B462-0087E32F0B39@csperkins.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: IETF AVT WG <avt@ietf.org>, jean-marc.valin@usherbrooke.ca
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Colin Perkins wrote:
> On 19 Jun 2007, at 10:51, Colin Perkins wrote:
>> On 19 Jun 2007, at 10:15, Aymeric Moizard wrote:
>>> There is an issue with section:
>>> "    4.1.1. Registration of media type audio/speex"
>>>
>>> First, the mode parameter text is defined using the same text as for 
>>> the SDP usage text: It sounds clear to me that in case "mode" is used 
>>> as a
>>> media parameter, it cannot be possible to specify several "mode".
>>>
>>> Although, I don't know much about media type.
>>>
>>> Thus, I think we have to keep the definition of mode in the SDP
>>> usage section.
>>
>> There shouldn't be any parameter definitions in the SDP usage section. 
>> That section is only used to specify how the media type parameters are 
>> represented in SDP.
> 
> Having now had time to read the draft in detail, what's needed is 
> something like:
> 
>    The information carried in the media type specification has a
>    specific mapping to fields in the Session Description Protocol (SDP)
>    [5], which is commonly used to describe RTP sessions.  When SDP is
>    used to specify sessions employing the Speex codec, the mapping is
>    as follows:
> 
>    o  The media type ("audio") goes in SDP "m=" as the media name.
> 
>    o  The media subtype ("speex") goes in SDP "a=rtpmap" as the encoding
>       name. The required parameter "rate" also goes in "a=rtpmap" as the
>       clock rate.
> 
>    o  The parameters "ptime" and "maxptime" go in the SDP "a=ptime" and
>       "a=maxptime" attributes, respectively.
> 
>    o  Any remaining parameters go in the SDP "a=fmtp" attribute by
>       copying them directly from the media type string as a semicolon
>       separated list of parameter=value pairs.
> 
>    Some example SDP session descriptions utilizing Speex encodings
>    follow.
> 
> To replace much of the existing text in the first half of Section 5. The 
> rationale is that all parameters are defined as parameters of the media 
> type, and the SDP usage just describes how those media type parameters 
> are encoded into SDP.
> 

Colin,

thanks for your input. I will update the draft with your suggestions and
include it in -03


/alfred

> --Colin Perkins
> http://csperkins.org/
> 
> 
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt


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



From avt-bounces@ietf.org Tue Jul 03 18:01:30 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5qR6-000860-57; Tue, 03 Jul 2007 18:01:28 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5qR4-00085s-D9
	for avt@ietf.org; Tue, 03 Jul 2007 18:01:26 -0400
Received: from pne-smtpout2-sn2.hy.skanova.net ([81.228.8.164])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I5qR3-0002oS-LQ
	for avt@ietf.org; Tue, 03 Jul 2007 18:01:26 -0400
Received: from GunnarH (213.64.232.214) by pne-smtpout2-sn2.hy.skanova.net
	(7.2.075) id 46245DE1012F7458; Wed, 4 Jul 2007 00:00:52 +0200
Message-ID: <46245DE1012F7458@pne-smtpout2-sn2.hy.skanova.net> (added by
	postmaster@pne.skanova.net)
From: =?iso-8859-1?Q?Gunnar_Hellstr=F6m?= <gunnar.hellstrom@omnitor.se>
To: "'Even, Roni'" <roni.even@polycom.co.il>,
	"'Shahaf Rozanski'" <Shahaf.Rozanski@audiocodes.com>, <avt@ietf.org>
Subject: RE: [AVT] Determining the desired transmitted resolution and
	framerate when using H.264 
Date: Wed, 4 Jul 2007 00:01:00 +0200
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Thread-Index: Ace9Sn+py2yb0KK4QwWYjr7tSMXIMgAPzomAAAgmhyA=
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C04B8F502@IsrExch01.israel.polycom.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82b297dca242a35ee50ccecf5bf2e37f
Cc: 'Yuval Nissan' <Yuval.Nissan@audiocodes.com>,
	'Keren Malachi' <Keren.Malachi@audiocodes.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>
Content-Type: multipart/mixed; boundary="===============0218795675=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0218795675==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0106_01C7BDCE.67E7B6E0"

This is a multi-part message in MIME format.

------=_NextPart_000_0106_01C7BDCE.67E7B6E0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

The order of the payload types in the m-line should reflect the order of
preference to receive the difference payload types.
=20
Different H.264 parameter sets are combined under different payload =
types as
specified in RFC 4629.
=20
This seems to me to offer a possibility to indicate your preferences.
=20
Is it not right that you would indicate QCIF preference over CIF by
declaring the following sdp parameters:
=20
 m=3Dvideo 49170 RTP/AVP 100 101
     a=3Drtpmap:100 H264/90000
     a=3Dfmtp:100 profile-level-id=3D42A00C;maxfs=3D99
     a=3Drtpmap:101 H264/90000
     a=3Dfmtp:101 profile-level-id=3D42A00B;maxfs=3D396;maxmbps=3D2900

=20
=20
=20
/Gunnar
-------------------------------------------------------------------
Gunnar Hellstr=F6m
Omnitor
gunnar.hellstrom@omnitor.se
=20

  _____ =20

From: Even, Roni [mailto:roni.even@polycom.co.il]=20
Sent: Tuesday, July 03, 2007 5:56 PM
To: Shahaf Rozanski; avt@ietf.org
Cc: Yuval Nissan; Keren Malachi
Subject: RE: [AVT] Determining the desired transmitted resolution and
framerate when using H.264=20



Hi,

H.264 does not have the definition of fixed frame sizes. The level gives
some maximum values which enable you to estimate the maximum size of the
frame and the frame rate.

Using max-mbps, max-fs you can override the level parameters. Still this
does not allow you to request a specific resolution or number of macro
b;ocks per second.

There is currently work done at the ITU on defining additional =
parameters to
H.241 in order to allow such functionality and after it is done there I
assume we will try to update RFC 3984 with this functionality.

=20

BTW: there are some new parameters now in =
draft-ietf-avt-rtp-h264-params-00
and you should look at it.

Roni Even

=20

  _____ =20

From: Shahaf Rozanski [mailto:Shahaf.Rozanski@audiocodes.com]=20
Sent: Tuesday, July 03, 2007 11:17 AM
To: avt@ietf.org
Cc: Yuval Nissan; Keren Malachi
Subject: [AVT] Determining the desired transmitted resolution and frame =
rate
when using H.264=20

=20

Hi,

=20

In the SDP negotiation each agent declares it supported receive
capabilities. For H.264 it can be done using the profile-level-id =
mechanism
suggested in RFC 3984.

Let=92s assume that the offerer declared baseline profile level 1.1. As =
a
result he is willing to receive different configuration e.g. up to CIF
resolution with 7.5 FPS or up to QCIF with 30 FPS.

Is there a method for the offerer to hint the answerer that he would =
like to
receive in a specific configuration (e.g. QCIF 30FPS)?

This can be useful if the offerer is a UE that is best suited for QCIF
resolutions.=20

=20

Thanks,

Shahaf



__________ NOD32 2372 (20070703) Information __________

Detta meddelande dr genomsvkt av NOD32 Antivirus.
http://www.nod32.com


------=_NextPart_000_0106_01C7BDCE.67E7B6E0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 72.0pt 90.0pt 72.0pt =
81.35pt; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
P.MsoToc1 {
	FONT-WEIGHT: bold; FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; LINE-HEIGHT: =
150%; FONT-FAMILY: Arial
}
LI.MsoToc1 {
	FONT-WEIGHT: bold; FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; LINE-HEIGHT: =
150%; FONT-FAMILY: Arial
}
DIV.MsoToc1 {
	FONT-WEIGHT: bold; FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; LINE-HEIGHT: =
150%; FONT-FAMILY: Arial
}
P.MsoToc2 {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt 12pt; LINE-HEIGHT: 150%; =
FONT-FAMILY: Arial
}
LI.MsoToc2 {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt 12pt; LINE-HEIGHT: 150%; =
FONT-FAMILY: Arial
}
DIV.MsoToc2 {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt 12pt; LINE-HEIGHT: 150%; =
FONT-FAMILY: Arial
}
P.MsoToc3 {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt 24pt; LINE-HEIGHT: 150%; =
FONT-FAMILY: Arial
}
LI.MsoToc3 {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt 24pt; LINE-HEIGHT: 150%; =
FONT-FAMILY: Arial
}
DIV.MsoToc3 {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt 24pt; LINE-HEIGHT: 150%; =
FONT-FAMILY: Arial
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle20 {
	COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle21 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D328454219-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The order of the payload types in the m-line =
should reflect=20
the order of preference to receive the difference payload=20
types.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D328454219-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D328454219-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Different H.264 parameter sets are combined =
under different=20
payload types as specified in RFC 4629.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D328454219-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D328454219-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>This seems to me to offer a possibility to =
indicate your=20
preferences.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D328454219-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D328454219-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Is it not right that you would indicate QCIF =
preference=20
over CIF by declaring the following sdp parameters:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D328454219-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D328454219-03072007><FONT=20
face=3DArial>&nbsp;m=3Dvideo 49170 RTP/AVP =
100&nbsp;101<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
a=3Drtpmap:100 H264/90000<BR>&nbsp;&nbsp;&nbsp;&nbsp; a=3Dfmtp:100=20
profile-level-id=3D42A00C;maxfs=3D99</FONT></SPAN><SPAN=20
class=3D328454219-03072007><FONT =
face=3DArial><BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
a=3Drtpmap:101 H264/90000<BR>&nbsp;&nbsp;&nbsp;&nbsp; a=3Dfmtp:101=20
profile-level-id=3D42A00B;maxfs=3D396;maxmbps=3D2900<BR></DIV></FONT></SP=
AN><SPAN=20
class=3D328454219-03072007><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D328454219-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D328454219-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D328454219-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D328454219-03072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>/Gunnar</FONT></SPAN></DIV>
<DIV align=3Dleft><FONT face=3DArial=20
size=3D2>----------------------------------------------------------------=
---</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Gunnar =
Hellstr=F6m</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Omnitor</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><A=20
href=3D"mailto:gunnar.hellstrom@omnitor.se">gunnar.hellstrom@omnitor.se</=
A></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Dsv dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Even, Roni=20
[mailto:roni.even@polycom.co.il] <BR><B>Sent:</B> Tuesday, July 03, 2007 =
5:56=20
PM<BR><B>To:</B> Shahaf Rozanski; avt@ietf.org<BR><B>Cc:</B> Yuval =
Nissan; Keren=20
Malachi<BR><B>Subject:</B> RE: [AVT] Determining the desired transmitted =

resolution and framerate when using H.264 <BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1 dir=3Drtl>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Hi,<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">H.264 does =
not have the=20
definition of fixed frame sizes. The level gives some maximum values =
which=20
enable you to estimate the maximum size of the frame and the frame=20
rate.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Using=20
</SPAN></FONT>max-mbps, max-fs you can override the level parameters. =
Still this=20
does not allow you to request a specific resolution or number of macro =
b;ocks=20
per second.<o:p></o:p></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">There is currently work done at the ITU on =
defining=20
additional parameters to H.241 in order to allow such functionality and =
after it=20
is done there I assume we will try to update RFC 3984 with this=20
functionality.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">BTW: there are some new parameters now in=20
draft-ietf-avt-rtp-h264-params-00 and you should look at=20
it.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><st1:PersonName w:st=3D"on" =
ProductID=3D"Roni Even"><FONT=20
face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">Roni=20
Even</SPAN></FONT></st1:PersonName><o:p></o:p></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV=20
style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0cm; BORDER-BOTTOM: medium none">
<DIV>
<DIV class=3DMsoNormal dir=3Dltr style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal dir=3Dltr><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma"> Shahaf=20
Rozanski [mailto:Shahaf.Rozanski@audiocodes.com] <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, July 03, 2007 =
11:17=20
AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
avt@ietf.org<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Yuval Nissan; Keren =
Malachi<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> [AVT] Determining the =
desired=20
transmitted resolution and frame rate when using H.264=20
</SPAN></FONT><o:p></o:p></P></DIV>
<P class=3DMsoNormal dir=3Dltr><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Hi,<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">In the SDP negotiation =
each agent=20
declares it supported receive capabilities. For H.264 it can be done =
using the=20
profile-level-id mechanism suggested in RFC =
3984.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Let=92s assume that the =
offerer=20
declared baseline profile level 1.1. As a result he is willing to =
receive=20
different configuration e.g. up to CIF resolution with 7.5 FPS or up to =
QCIF=20
with 30 FPS.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Is there a method for the =
offerer to=20
hint the answerer that he would like to receive in a specific =
configuration=20
(e.g. QCIF 30FPS)?<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">This can be useful if the =
offerer is=20
a UE that is best suited for QCIF resolutions. =
<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Thanks,<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Shahaf<o:p></o:p></SPAN></FONT></P></DIV></DIV><BR><BR>__________ =

NOD32 2372 (20070703) Information __________<BR><BR>Detta meddelande dr=20
genomsvkt av NOD32 Antivirus.<BR><A=20
href=3D"http://www.nod32.com">http://www.nod32.com</A><BR></BODY></HTML>

------=_NextPart_000_0106_01C7BDCE.67E7B6E0--



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

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

--===============0218795675==--





From avt-bounces@ietf.org Tue Jul 03 22:45:09 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5urb-0008C6-Cg; Tue, 03 Jul 2007 22:45:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5urZ-0008Bv-KO
	for avt@ietf.org; Tue, 03 Jul 2007 22:45:05 -0400
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I5urV-0006cQ-CW for avt@ietf.org; Tue, 03 Jul 2007 22:45:05 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 3 Jul 2007 22:45:01 -0400
To: =?iso-8859-15?q?Gunnar_Hellstr=F6m?= <gunnar.hellstrom@omnitor.se>
Subject: Re: [AVT] Determining the desired transmitted resolution and
	framerate when using H.264
References: <46245DE1012F7458@pne-smtpout2-sn2.hy.skanova.net>
From: Randell Jesup <rjesup@wgate.com>
Date: Tue, 03 Jul 2007 22:44:58 -0400
In-Reply-To: <46245DE1012F7458@pne-smtpout2-sn2.hy.skanova.net> (added by
	postmaster@pne.skanova.net) (Gunnar =?iso-8859-15?q?Hellstr=F6m's?=
	message of "Wed, 4 Jul 2007 00:01:00 +0200")
Message-ID: <ybu4pkkevkl.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 04 Jul 2007 02:45:01.0052 (UTC)
	FILETIME=[512EA3C0:01C7BDE5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: 'Yuval Nissan' <Yuval.Nissan@audiocodes.com>,
	'Keren Malachi' <Keren.Malachi@audiocodes.com>, "'Even,
	Roni'" <roni.even@polycom.co.il>, avt@ietf.org,
	'Shahaf Rozanski' <Shahaf.Rozanski@audiocodes.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Gunnar Hellström <gunnar.hellstrom@omnitor.se> writes:
>The order of the payload types in the m-line should reflect the order of
>preference to receive the difference payload types.
> 
>Different H.264 parameter sets are combined under different payload types as
>specified in RFC 4629.
> 
>This seems to me to offer a possibility to indicate your preferences.
> 
>Is it not right that you would indicate QCIF preference over CIF by
>declaring the following sdp parameters:
> 
> m=video 49170 RTP/AVP 100 101
>     a=rtpmap:100 H264/90000
>     a=fmtp:100 profile-level-id=42A00C;maxfs=99
>     a=rtpmap:101 H264/90000
>     a=fmtp:101 profile-level-id=42A00B;maxfs=396;maxmbps=2900

Good point, though this is a form of capability negotation possible within
the original SDP/offer-answer framework.  Also, since H.264 fmtp lines can
get *long*, this might add to the fun for SIP over UDP.

That would prefer QCIF (or so, depending on aspect ratio) over CIF (or
so) - but they could accept 101 and send QCIF (or anything with <= 396
MB/frame).  Perhaps the aspect-ratio drafts would help here, but they can
still send smaller frames.

It's worth considering promoting this as a way to negotiate that, if there
aren't any "gotchas".  Note that some UAs might not handle this well, but
if they really implement all of the RFC it should.

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


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



From avt-bounces@ietf.org Wed Jul 04 01:06:45 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5x4e-0001gg-83; Wed, 04 Jul 2007 01:06:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5x4c-0001gW-5K
	for avt@ietf.org; Wed, 04 Jul 2007 01:06:42 -0400
Received: from pne-smtpout1-sn2.hy.skanova.net ([81.228.8.83])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5x3q-0002K6-99
	for avt@ietf.org; Wed, 04 Jul 2007 01:06:42 -0400
Received: from GunnarH (213.64.232.214) by pne-smtpout1-sn2.hy.skanova.net
	(7.2.075) id 4656A9900094E392; Wed, 4 Jul 2007 07:05:53 +0200
Message-ID: <4656A9900094E392@pne-smtpout1-sn2.hy.skanova.net> (added by
	postmaster@pne.skanova.net)
From: =?iso-8859-1?Q?Gunnar_Hellstr=F6m?= <gunnar.hellstrom@omnitor.se>
To: "'Randell Jesup'" <rjesup@wgate.com>
Subject: RE: [AVT] Determining the desired transmitted resolution andframerate
	when using H.264
Date: Wed, 4 Jul 2007 07:05:59 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Thread-Index: Ace95WOgCUQvI5VCRGW5LxMnVhksLgADsHsw
In-Reply-To: <ybu4pkkevkl.fsf@jesup.eng.wgate.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: 'Shahaf Rozanski' <Shahaf.Rozanski@audiocodes.com>, "'Even,
	Roni'" <roni.even@polycom.co.il>,
	'Yuval Nissan' <Yuval.Nissan@audiocodes.com>, avt@ietf.org,
	'Keren Malachi' <Keren.Malachi@audiocodes.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

OK, so we found that it seems possible to express some order of =
preference
for video parameters for H.264 by the order of payload types in the =
m-line.

Next question is if it is possible to compose parameter collections that
correspond to what I want to express.

Shahaf may have had a slightly different need when starting this =
discussion.
I continue on my example with the hope that it has similarities.

Assume that I have a capable receiver and transmitter, that can receive =
and
transmit CIF 30 fps.
In calls with other capable UAs, I of course want to get CIF 30 fps.
But in calls with a weaker UA, I want to express preference for getting =
QCIF
30 rather than CIF 15.

Can I collect three sets of parameters in different PTs, expressing:

CIF - 30 , QCIF - 30, CIF - 15.

I am afraid that with my previous example, it might have been perceived =
as
if I had a total preference for QCIF (or so).

This is an important need from sign language communication. We need to
discourage frame rates lower than 20 fps. If this method is too clumsy, =
we
should start on some other method.=20

/gunnar
=20
--------------------------------------------------------

Gunnar Hellstr=F6m <gunnar.hellstrom@omnitor.se> writes:
>The order of the payload types in the m-line should reflect the order=20
>of preference to receive the difference payload types.
>=20
>Different H.264 parameter sets are combined under different payload=20
>types as specified in RFC 4629.
>=20
>This seems to me to offer a possibility to indicate your preferences.
>=20
>Is it not right that you would indicate QCIF preference over CIF by=20
>declaring the following sdp parameters:
>=20
> m=3Dvideo 49170 RTP/AVP 100 101
>     a=3Drtpmap:100 H264/90000
>     a=3Dfmtp:100 profile-level-id=3D42A00C;maxfs=3D99
>     a=3Drtpmap:101 H264/90000
>     a=3Dfmtp:101 profile-level-id=3D42A00B;maxfs=3D396;maxmbps=3D2900

Good point, though this is a form of capability negotation possible =
within
the original SDP/offer-answer framework.  Also, since H.264 fmtp lines =
can
get *long*, this might add to the fun for SIP over UDP.

That would prefer QCIF (or so, depending on aspect ratio) over CIF (or
so) - but they could accept 101 and send QCIF (or anything with <=3D 396
MB/frame).  Perhaps the aspect-ratio drafts would help here, but they =
can
still send smaller frames.

It's worth considering promoting this as a way to negotiate that, if =
there
aren't any "gotchas".  Note that some UAs might not handle this well, =
but if
they really implement all of the RFC it should.

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


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

__________ NOD32 2372 (20070703) Information __________

Detta meddelande =E4r genoms=F6kt av NOD32 Antivirus.
http://www.nod32.com



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



From avt-bounces@ietf.org Wed Jul 04 02:44:54 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5ybc-0003Ep-AQ; Wed, 04 Jul 2007 02:44:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5yba-00039t-QS
	for avt@ietf.org; Wed, 04 Jul 2007 02:44:50 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5ybP-0002yV-7Q
	for avt@ietf.org; Wed, 04 Jul 2007 02:44:50 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] Determining the desired transmitted resolution and frame
	rate when using H.264
Date: Wed, 4 Jul 2007 09:45:28 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04B8F5CB@IsrExch01.israel.polycom.com>
In-Reply-To: <ybu8x9xcqkt.fsf@jesup.eng.wgate.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Determining the desired transmitted resolution and frame
	rate when using H.264
Thread-Index: Ace9nLwt1DDpy5ZwThiChVv9er34AgAad+yA
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Randell Jesup" <rjesup@wgate.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: Keren Malachi <Keren.Malachi@audiocodes.com>,
	Yuval Nissan <Yuval.Nissan@audiocodes.com>, avt@ietf.org,
	Shahaf Rozanski <Shahaf.Rozanski@audiocodes.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Randell,
The work is done in Q1 of study group 16. I will try to write a draft
explaining the problem and the suggested solution. It is still a work in
process with the intention to have a proposal in beginning of 2008.
Roni

> -----Original Message-----
> From: Randell Jesup [mailto:rjesup@wgate.com]
> Sent: Tuesday, July 03, 2007 9:04 PM
> To: Even, Roni
> Cc: Shahaf Rozanski; avt@ietf.org; Yuval Nissan; Keren Malachi
> Subject: Re: [AVT] Determining the desired transmitted resolution and
> frame rate when using H.264
>=20
> "Even, Roni" <roni.even@polycom.co.il> writes:
> >H.264 does not have the definition of fixed frame sizes. The level
gives
> >some maximum values which enable you to estimate the maximum size of
the
> >frame and the frame rate.
>=20
> The problem (as Roni states) is that while the profile/etc may
determine
> the base ability to decode (horsepower, memory, etc), often the
decoded
> video is fed to devices that cannot render/display arbitrary
resolutions
> (and not just the aspect ratio issue which is currently under
discussion).
> In theory, a device can probably always display the video in some
manner,
> but it may not be a usable/useful manner (cropping or adding (large)
areas
> of black).  Not all devices will have an arbitrary scaler, or even a
> scaler
> at all, or they may only have fixed scalers to choose from, or may not
> have
> the horsepower to run a scaler while doing max-mbps encode/decode.
>=20
> >Using max-mbps, max-fs you can override the level parameters. Still
this
> >does not allow you to request a specific resolution or number of
macro
> >b;ocks per second.
>=20
> Right, not even to express a preference or tradeoff.  MAYBE you could
do a
> little of it using capability negotiation - if the other side
understood
> what you're trying to do.
>=20
> >There is currently work done at the ITU on defining additional
> >parameters to H.241 in order to allow such functionality and after it
is
> >done there I assume we will try to update RFC 3984 with this
> >functionality.
>=20
> Where is this being done?  Wouldn't it make sense to add input from
the
> IETF side now, so that when everyone is done there's a reasonable
mapping
> back and forth?
>=20
> --
> Randell Jesup, Worldgate (developers of the Ojo videophone), ex-Amiga
OS
> team
> rjesup@wgate.com
> "The fetters imposed on liberty at home have ever been forged out of
the
> weapons
> provided for defence against real, pretended, or imaginary dangers
from
> abroad."
> 		- James Madison, 4th US president (1751-1836)


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



From avt-bounces@ietf.org Wed Jul 04 02:50:49 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5yhL-0002bG-LX; Wed, 04 Jul 2007 02:50:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5yhK-0002aa-NV
	for avt@ietf.org; Wed, 04 Jul 2007 02:50:46 -0400
Received: from [212.25.125.1] (helo=aclmsg.corp.audiocodes.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5yhF-0004wD-PZ
	for avt@ietf.org; Wed, 04 Jul 2007 02:50:46 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] Determining the desired transmitted resolution and frame
	rate when using H.264
Date: Wed, 4 Jul 2007 09:51:11 +0300
Message-ID: <79B4F738DDD4EF4F85A4641A0FE5EFD602CA8D88@aclmsg.corp.audiocodes.com>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C04B8F5CB@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Determining the desired transmitted resolution and frame
	rate when using H.264
Thread-Index: Ace9nLwt1DDpy5ZwThiChVv9er34AgAad+yAAAAg7hA=
From: "Yuval Nissan" <Yuval.Nissan@audiocodes.com>
To: "Even, Roni" <roni.even@polycom.co.il>, "Randell Jesup" <rjesup@wgate.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: Keren Malachi <Keren.Malachi@audiocodes.com>, avt@ietf.org,
	Shahaf Rozanski <Shahaf.Rozanski@audiocodes.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Roni,

I think the ability to negotiate desirable working point (inside the
envelope of the level) should be general method for all video coders and
not specific (and different today) for each one of them. Do you see any
technical reason why it can't be that way?

(Take for example transcoder server that need to support few video
coders...)

Regards,
Yuval   =20


-----Original Message-----
From: Even, Roni [mailto:roni.even@polycom.co.il]=20
Sent: Wednesday, July 04, 2007 9:45 AM
To: Randell Jesup
Cc: Shahaf Rozanski; avt@ietf.org; Yuval Nissan; Keren Malachi
Subject: RE: [AVT] Determining the desired transmitted resolution and
frame rate when using H.264

Randell,
The work is done in Q1 of study group 16. I will try to write a draft
explaining the problem and the suggested solution. It is still a work in
process with the intention to have a proposal in beginning of 2008.
Roni

> -----Original Message-----
> From: Randell Jesup [mailto:rjesup@wgate.com]
> Sent: Tuesday, July 03, 2007 9:04 PM
> To: Even, Roni
> Cc: Shahaf Rozanski; avt@ietf.org; Yuval Nissan; Keren Malachi
> Subject: Re: [AVT] Determining the desired transmitted resolution and
> frame rate when using H.264
>=20
> "Even, Roni" <roni.even@polycom.co.il> writes:
> >H.264 does not have the definition of fixed frame sizes. The level
gives
> >some maximum values which enable you to estimate the maximum size of
the
> >frame and the frame rate.
>=20
> The problem (as Roni states) is that while the profile/etc may
determine
> the base ability to decode (horsepower, memory, etc), often the
decoded
> video is fed to devices that cannot render/display arbitrary
resolutions
> (and not just the aspect ratio issue which is currently under
discussion).
> In theory, a device can probably always display the video in some
manner,
> but it may not be a usable/useful manner (cropping or adding (large)
areas
> of black).  Not all devices will have an arbitrary scaler, or even a
> scaler
> at all, or they may only have fixed scalers to choose from, or may not
> have
> the horsepower to run a scaler while doing max-mbps encode/decode.
>=20
> >Using max-mbps, max-fs you can override the level parameters. Still
this
> >does not allow you to request a specific resolution or number of
macro
> >b;ocks per second.
>=20
> Right, not even to express a preference or tradeoff.  MAYBE you could
do a
> little of it using capability negotiation - if the other side
understood
> what you're trying to do.
>=20
> >There is currently work done at the ITU on defining additional
> >parameters to H.241 in order to allow such functionality and after it
is
> >done there I assume we will try to update RFC 3984 with this
> >functionality.
>=20
> Where is this being done?  Wouldn't it make sense to add input from
the
> IETF side now, so that when everyone is done there's a reasonable
mapping
> back and forth?
>=20
> --
> Randell Jesup, Worldgate (developers of the Ojo videophone), ex-Amiga
OS
> team
> rjesup@wgate.com
> "The fetters imposed on liberty at home have ever been forged out of
the
> weapons
> provided for defence against real, pretended, or imaginary dangers
from
> abroad."
> 		- James Madison, 4th US president (1751-1836)

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



From avt-bounces@ietf.org Wed Jul 04 02:51:41 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5yiC-0004SO-Nb; Wed, 04 Jul 2007 02:51:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5yiB-0004MH-Lc
	for avt@ietf.org; Wed, 04 Jul 2007 02:51:39 -0400
Received: from [212.25.125.1] (helo=aclmsg.corp.audiocodes.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5yhv-0005ck-E7
	for avt@ietf.org; Wed, 04 Jul 2007 02:51:39 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [AVT] Determining the desired transmitted resolution and frame
	rate when using H.264 
Date: Wed, 4 Jul 2007 09:51:54 +0300
Message-ID: <79B4F738DDD4EF4F85A4641A0FE5EFD602CA8D89@aclmsg.corp.audiocodes.com>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C04B8F502@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Determining the desired transmitted resolution and frame
	rate when using H.264 
Thread-Index: Ace9Sn+py2yb0KK4QwWYjr7tSMXIMgAPzomAAB6SZtA=
From: "Yuval Nissan" <Yuval.Nissan@audiocodes.com>
To: "Even, Roni" <roni.even@polycom.co.il>,
	"Shahaf Rozanski" <Shahaf.Rozanski@audiocodes.com>, <avt@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fbe0995f04cc21309ef8614a2838e306
Cc: Keren Malachi <Keren.Malachi@audiocodes.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>
Content-Type: multipart/mixed; boundary="===============1177879911=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1177879911==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7BE07.CEDD1E27"

This is a multi-part message in MIME format.

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

Hi,

=20

I think the ability to negotiate desirable working point (inside the
envelope of the level) should be general method for all video coders and
not specific (and different today) for each one of them. Do you see any
technical reason why it can't be that way?

=20

(Take for example transcoder server that need to support few video
coders...)

=20

Regards,

Yuval   =20

=20

=20

________________________________

From: Even, Roni [mailto:roni.even@polycom.co.il]=20
Sent: Tuesday, July 03, 2007 6:56 PM
To: Shahaf Rozanski; avt@ietf.org
Cc: Yuval Nissan; Keren Malachi
Subject: RE: [AVT] Determining the desired transmitted resolution and
frame rate when using H.264=20

=20

Hi,

H.264 does not have the definition of fixed frame sizes. The level gives
some maximum values which enable you to estimate the maximum size of the
frame and the frame rate.

Using max-mbps, max-fs you can override the level parameters. Still this
does not allow you to request a specific resolution or number of macro
b;ocks per second.

There is currently work done at the ITU on defining additional
parameters to H.241 in order to allow such functionality and after it is
done there I assume we will try to update RFC 3984 with this
functionality.

=20

BTW: there are some new parameters now in
draft-ietf-avt-rtp-h264-params-00 and you should look at it.

Roni Even

=20

________________________________

From: Shahaf Rozanski [mailto:Shahaf.Rozanski@audiocodes.com]=20
Sent: Tuesday, July 03, 2007 11:17 AM
To: avt@ietf.org
Cc: Yuval Nissan; Keren Malachi
Subject: [AVT] Determining the desired transmitted resolution and frame
rate when using H.264=20

=20

Hi,

=20

In the SDP negotiation each agent declares it supported receive
capabilities. For H.264 it can be done using the profile-level-id
mechanism suggested in RFC 3984.

Let's assume that the offerer declared baseline profile level 1.1. As a
result he is willing to receive different configuration e.g. up to CIF
resolution with 7.5 FPS or up to QCIF with 30 FPS.

Is there a method for the offerer to hint the answerer that he would
like to receive in a specific configuration (e.g. QCIF 30FPS)?

This can be useful if the offerer is a UE that is best suited for QCIF
resolutions.=20

=20

Thanks,

Shahaf


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

<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@Batang";
	panose-1:2 3 6 0 0 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoToc1, li.MsoToc1, div.MsoToc1
	{margin:0in;
	margin-bottom:.0001pt;
	line-height:150%;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:bold;}
p.MsoToc2, li.MsoToc2, div.MsoToc2
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:12.0pt;
	margin-bottom:.0001pt;
	line-height:150%;
	font-size:12.0pt;
	font-family:Arial;}
p.MsoToc3, li.MsoToc3, div.MsoToc3
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:24.0pt;
	margin-bottom:.0001pt;
	line-height:150%;
	font-size:12.0pt;
	font-family:Arial;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle20
	{font-family:Arial;
	color:windowtext;}
span.EmailStyle21
	{font-family:Arial;
	color:navy;}
span.EmailStyle22
	{font-family:Arial;
	color:navy;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:1.0in 1.25in 1.0in 81.35pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1 dir=3DRTL>

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

<p class=3DMsoNormal dir=3DLTR><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;</span></fo=
nt></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>I think the =
ability to negotiate
desirable working point (inside the envelope of the level) should be =
general method
for all video coders and not specific (and different today) for each one =
of
them. Do you see any technical reason why it can&#8217;t be that =
way?</span></font></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;</span></fo=
nt></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>(Take for =
example
transcoder server that need to support few video =
coders&#8230;)</span></font></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;</span></fo=
nt></p>

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

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

<p class=3DMsoNormal dir=3DLTR><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;</span></fo=
nt></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;</span></fo=
nt></p>

<div>

<div class=3DMsoNormal align=3Dcenter dir=3DLTR =
style=3D'text-align:center'><font
size=3D3 face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

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

</span></font></div>

<p class=3DMsoNormal dir=3DLTR><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> Even,
Roni [mailto:roni.even@polycom.co.il] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, July 03, =
2007 6:56
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Shahaf Rozanski; =
avt@ietf.org<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> Yuval Nissan; Keren =
Malachi<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [AVT] =
Determining the
desired transmitted resolution and frame rate when using H.264 =
</span></font></p>

</div>

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

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

<p class=3DMsoNormal dir=3DLTR><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>H.264 does not =
have the
definition of fixed frame sizes. The level gives some maximum values =
which
enable you to estimate the maximum size of the frame and the frame =
rate.</span></font></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Using =
</span></font>max-mbps,
max-fs you can override the level parameters. Still this does not allow =
you to
request a specific resolution or number of macro b;ocks per second.</p>

<p class=3DMsoNormal dir=3DLTR><font size=3D3 face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt'>There is currently work done at the ITU on =
defining
additional parameters to H.241 in order to allow such functionality and =
after
it is done there I assume we will try to update RFC 3984 with this
functionality.</span></font></p>

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

<p class=3DMsoNormal dir=3DLTR><font size=3D3 face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt'>BTW: there are some new parameters now in
draft-ietf-avt-rtp-h264-params-00 and you should look at =
it.</span></font></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D3 face=3D"Times New =
Roman"><span
 style=3D'font-size:12.0pt'>Roni Even</span></font></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;</span></fo=
nt></p>

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

<div>

<div class=3DMsoNormal align=3Dcenter dir=3DLTR =
style=3D'text-align:center'><font
size=3D3 face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

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

</span></font></div>

<p class=3DMsoNormal dir=3DLTR><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> Shahaf Rozanski =
[mailto:Shahaf.Rozanski@audiocodes.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, July 03, =
2007 11:17
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> avt@ietf.org<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> Yuval Nissan; Keren =
Malachi<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [AVT] =
Determining the
desired transmitted resolution and frame rate when using H.264 =
</span></font></p>

</div>

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

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

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

<p class=3DMsoNormal dir=3DLTR><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>In the SDP negotiation each agent declares it =
supported
receive capabilities. For H.264 it can be done using the =
profile-level-id
mechanism suggested in RFC 3984.</span></font></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Let&#8217;s assume that the offerer declared baseline
profile level 1.1. As a result he is willing to receive different =
configuration
e.g. up to CIF resolution with 7.5 FPS or up to QCIF with 30 =
FPS.</span></font></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Is there a method for the offerer to hint the =
answerer that
he would like to receive in a specific configuration (e.g. QCIF =
30FPS)?</span></font></p>

<p class=3DMsoNormal dir=3DLTR><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>This can be useful if the offerer is a UE that is =
best
suited for QCIF resolutions. </span></font></p>

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

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

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

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C7BE07.CEDD1E27--


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

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

--===============1177879911==--




From avt-bounces@ietf.org Wed Jul 04 02:53:33 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5yk0-00007G-V6; Wed, 04 Jul 2007 02:53:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5yk0-00007B-8x
	for avt@ietf.org; Wed, 04 Jul 2007 02:53:32 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5yjc-00067n-Qa
	for avt@ietf.org; Wed, 04 Jul 2007 02:53:32 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] Determining the desired transmitted resolution
	andframeratewhen using H.264
Date: Wed, 4 Jul 2007 09:54:00 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04B8F5D8@IsrExch01.israel.polycom.com>
In-Reply-To: <4656A9900094E392@pne-smtpout1-sn2.hy.skanova.net>A(addedAbypostmaster@pne.skanova.net)
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Determining the desired transmitted resolution
	andframeratewhen using H.264
Thread-Index: Ace95WOgCUQvI5VCRGW5LxMnVhksLgADsHswAATmKbA=
From: "Even, Roni" <roni.even@polycom.co.il>
To: =?iso-8859-1?Q?Gunnar_Hellstr=F6m?= <gunnar.hellstrom@omnitor.se>,
	"Randell Jesup" <rjesup@wgate.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Cc: Keren Malachi <Keren.Malachi@audiocodes.com>,
	Yuval Nissan <Yuval.Nissan@audiocodes.com>, avt@ietf.org,
	Shahaf Rozanski <Shahaf.Rozanski@audiocodes.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Gunnar,
The frame rate is dependent on the content. If the input in a meeting =
room it may be better to favor high frame rate on resolution. On the =
other hand if you send a presentation (like H.239 content) it is better =
to have high resolution and low frame rate.
Roni=20

> -----Original Message-----
> From: Gunnar Hellstr=F6m [mailto:gunnar.hellstrom@omnitor.se]
> Sent: Wednesday, July 04, 2007 8:06 AM
> To: 'Randell Jesup'
> Cc: 'Shahaf Rozanski'; Even, Roni; 'Yuval Nissan'; avt@ietf.org; =
'Keren
> Malachi'
> Subject: RE: [AVT] Determining the desired transmitted resolution
> andframeratewhen using H.264
>=20
> OK, so we found that it seems possible to express some order of =
preference
> for video parameters for H.264 by the order of payload types in the m-
> line.
>=20
> Next question is if it is possible to compose parameter collections =
that
> correspond to what I want to express.
>=20
> Shahaf may have had a slightly different need when starting this
> discussion.
> I continue on my example with the hope that it has similarities.
>=20
> Assume that I have a capable receiver and transmitter, that can =
receive
> and
> transmit CIF 30 fps.
> In calls with other capable UAs, I of course want to get CIF 30 fps.
> But in calls with a weaker UA, I want to express preference for =
getting
> QCIF
> 30 rather than CIF 15.
>=20
> Can I collect three sets of parameters in different PTs, expressing:
>=20
> CIF - 30 , QCIF - 30, CIF - 15.
>=20
> I am afraid that with my previous example, it might have been =
perceived as
> if I had a total preference for QCIF (or so).
>=20
> This is an important need from sign language communication. We need to
> discourage frame rates lower than 20 fps. If this method is too =
clumsy, we
> should start on some other method.
>=20
> /gunnar
>=20
> --------------------------------------------------------
>=20
> Gunnar Hellstr=F6m <gunnar.hellstrom@omnitor.se> writes:
> >The order of the payload types in the m-line should reflect the order
> >of preference to receive the difference payload types.
> >
> >Different H.264 parameter sets are combined under different payload
> >types as specified in RFC 4629.
> >
> >This seems to me to offer a possibility to indicate your preferences.
> >
> >Is it not right that you would indicate QCIF preference over CIF by
> >declaring the following sdp parameters:
> >
> > m=3Dvideo 49170 RTP/AVP 100 101
> >     a=3Drtpmap:100 H264/90000
> >     a=3Dfmtp:100 profile-level-id=3D42A00C;maxfs=3D99
> >     a=3Drtpmap:101 H264/90000
> >     a=3Dfmtp:101 =
profile-level-id=3D42A00B;maxfs=3D396;maxmbps=3D2900
>=20
> Good point, though this is a form of capability negotation possible =
within
> the original SDP/offer-answer framework.  Also, since H.264 fmtp lines =
can
> get *long*, this might add to the fun for SIP over UDP.
>=20
> That would prefer QCIF (or so, depending on aspect ratio) over CIF (or
> so) - but they could accept 101 and send QCIF (or anything with <=3D =
396
> MB/frame).  Perhaps the aspect-ratio drafts would help here, but they =
can
> still send smaller frames.
>=20
> It's worth considering promoting this as a way to negotiate that, if =
there
> aren't any "gotchas".  Note that some UAs might not handle this well, =
but
> if
> they really implement all of the RFC it should.
>=20
> --
> Randell Jesup, Worldgate (developers of the Ojo videophone), ex-Amiga =
OS
> team rjesup@wgate.com "The fetters imposed on liberty at home have =
ever
> been
> forged out of the weapons provided for defence against real, =
pretended, or
> imaginary dangers from abroad."
> 		- James Madison, 4th US president (1751-1836)
>=20
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>=20
> __________ NOD32 2372 (20070703) Information __________
>=20
> Detta meddelande =E4r genoms=F6kt av NOD32 Antivirus.
> http://www.nod32.com
>=20
>=20
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

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



From avt-bounces@ietf.org Wed Jul 04 02:58:34 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5yor-000174-3x; Wed, 04 Jul 2007 02:58:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5yop-00016t-7Z
	for avt@ietf.org; Wed, 04 Jul 2007 02:58:31 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5yol-0007dg-PU
	for avt@ietf.org; Wed, 04 Jul 2007 02:58:31 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] Determining the desired transmitted resolution and frame
	rate when using H.264
Date: Wed, 4 Jul 2007 09:59:19 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04B8F5E1@IsrExch01.israel.polycom.com>
In-Reply-To: <79B4F738DDD4EF4F85A4641A0FE5EFD602CA8D88@aclmsg.corp.audiocodes.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Determining the desired transmitted resolution and frame
	rate when using H.264
Thread-Index: Ace9nLwt1DDpy5ZwThiChVv9er34AgAad+yAAAAg7hAAAEPYkA==
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Yuval Nissan" <Yuval.Nissan@audiocodes.com>,
	"Randell Jesup" <rjesup@wgate.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Cc: Keren Malachi <Keren.Malachi@audiocodes.com>, avt@ietf.org,
	Shahaf Rozanski <Shahaf.Rozanski@audiocodes.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Yuval,
You can do it today in H.263 and H.261. The problem is that H.264 does
not define fixed resolutions so using the max-fs gives the number of
macro blocks and not the geometry.=20
If you read the thread and saw Randell text you will notice that picture
aspect ratio is only part of the information needed in order to create a
picture that is not distorted. The video input today (camera) is
different than in the past, you have 4:3 or 16:9 cameras and they create
different geometry.
This is why I suggested you look also at the new h264 parameters draft.

Roni

> -----Original Message-----
> From: Yuval Nissan [mailto:Yuval.Nissan@audiocodes.com]
> Sent: Wednesday, July 04, 2007 9:51 AM
> To: Even, Roni; Randell Jesup
> Cc: Shahaf Rozanski; avt@ietf.org; Keren Malachi
> Subject: RE: [AVT] Determining the desired transmitted resolution and
> frame rate when using H.264
>=20
> Roni,
>=20
> I think the ability to negotiate desirable working point (inside the
> envelope of the level) should be general method for all video coders
and
> not specific (and different today) for each one of them. Do you see
any
> technical reason why it can't be that way?
>=20
> (Take for example transcoder server that need to support few video
> coders...)
>=20
> Regards,
> Yuval
>=20
>=20
> -----Original Message-----
> From: Even, Roni [mailto:roni.even@polycom.co.il]
> Sent: Wednesday, July 04, 2007 9:45 AM
> To: Randell Jesup
> Cc: Shahaf Rozanski; avt@ietf.org; Yuval Nissan; Keren Malachi
> Subject: RE: [AVT] Determining the desired transmitted resolution and
> frame rate when using H.264
>=20
> Randell,
> The work is done in Q1 of study group 16. I will try to write a draft
> explaining the problem and the suggested solution. It is still a work
in
> process with the intention to have a proposal in beginning of 2008.
> Roni
>=20
> > -----Original Message-----
> > From: Randell Jesup [mailto:rjesup@wgate.com]
> > Sent: Tuesday, July 03, 2007 9:04 PM
> > To: Even, Roni
> > Cc: Shahaf Rozanski; avt@ietf.org; Yuval Nissan; Keren Malachi
> > Subject: Re: [AVT] Determining the desired transmitted resolution
and
> > frame rate when using H.264
> >
> > "Even, Roni" <roni.even@polycom.co.il> writes:
> > >H.264 does not have the definition of fixed frame sizes. The level
> gives
> > >some maximum values which enable you to estimate the maximum size
of
> the
> > >frame and the frame rate.
> >
> > The problem (as Roni states) is that while the profile/etc may
> determine
> > the base ability to decode (horsepower, memory, etc), often the
> decoded
> > video is fed to devices that cannot render/display arbitrary
> resolutions
> > (and not just the aspect ratio issue which is currently under
> discussion).
> > In theory, a device can probably always display the video in some
> manner,
> > but it may not be a usable/useful manner (cropping or adding (large)
> areas
> > of black).  Not all devices will have an arbitrary scaler, or even a
> > scaler
> > at all, or they may only have fixed scalers to choose from, or may
not
> > have
> > the horsepower to run a scaler while doing max-mbps encode/decode.
> >
> > >Using max-mbps, max-fs you can override the level parameters. Still
> this
> > >does not allow you to request a specific resolution or number of
> macro
> > >b;ocks per second.
> >
> > Right, not even to express a preference or tradeoff.  MAYBE you
could
> do a
> > little of it using capability negotiation - if the other side
> understood
> > what you're trying to do.
> >
> > >There is currently work done at the ITU on defining additional
> > >parameters to H.241 in order to allow such functionality and after
it
> is
> > >done there I assume we will try to update RFC 3984 with this
> > >functionality.
> >
> > Where is this being done?  Wouldn't it make sense to add input from
> the
> > IETF side now, so that when everyone is done there's a reasonable
> mapping
> > back and forth?
> >
> > --
> > Randell Jesup, Worldgate (developers of the Ojo videophone),
ex-Amiga
> OS
> > team
> > rjesup@wgate.com
> > "The fetters imposed on liberty at home have ever been forged out of
> the
> > weapons
> > provided for defence against real, pretended, or imaginary dangers
> from
> > abroad."
> > 		- James Madison, 4th US president (1751-1836)

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



From avt-bounces@ietf.org Wed Jul 04 05:49:39 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I61UJ-0006qx-Mc; Wed, 04 Jul 2007 05:49:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I61UI-0006qs-9X
	for avt@ietf.org; Wed, 04 Jul 2007 05:49:30 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I61UD-0000kH-UE
	for avt@ietf.org; Wed, 04 Jul 2007 05:49:30 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 4 Jul 2007 12:50:22 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04B8F660@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AVT WG meeting in Chicago - Agenda Time slot requests - reminder
Thread-Index: Ace+IL0DjGybYaCqSy2C/g8dyNM8eA==
From: "Even, Roni" <roni.even@polycom.co.il>
To: <avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: "Even, Roni" <roni.even@polycom.co.il>, Colin Perkins <csp@csperkins.org>,
	tom.taylor@rogers.com
Subject: [AVT] AVT WG meeting in Chicago - Agenda Time slot requests -
	reminder
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi,

If you wish to have agenda time at the upcoming meeting in Chicago, =
please send an agenda request to the chairs, but no later than July 9th.

We have requested two time slots:
1. Monday July 23rd 15:20-17:20
2. Thursday July 26th 15:10-16:10=20

Please note that those times are not final and may change. The final =
agenda for the meeting will; be published on July 2nd.



This meeting time is intended for the following:

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

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

A. Presentation Title:

B. Name of presenter:

C. Draft Reference(s):

D. Requested amount of time in minutes:




Thanks
Roni Even


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



From avt-bounces@ietf.org Wed Jul 04 06:06:51 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I61l3-0004uh-TP; Wed, 04 Jul 2007 06:06:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I61l1-0004uc-VA
	for avt@ietf.org; Wed, 04 Jul 2007 06:06:47 -0400
Received: from an-out-0708.google.com ([209.85.132.243])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I61kx-0003m2-I9
	for avt@ietf.org; Wed, 04 Jul 2007 06:06:47 -0400
Received: by an-out-0708.google.com with SMTP id c17so470587anc
	for <avt@ietf.org>; Wed, 04 Jul 2007 03:06:43 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=TijtHeAGUoz5FOWNeEYVde0Fy6N8papjVT2/UJS01JB4QVT4CXiYF5fsyzvD3kYs8aEqOUnbh7k7Jl9McQXfXDZg9sJDBzRHWQmWPqWjdrBEQqF4K44HErknPkh1rK3pn1iEXZOSHnCjC41vhJJ9DIfXi9bOJh/wmn9BTtn1KNw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=mqkQhUaZjbF+2Yqp3AjoXMSu2CW1fJXPbOG8rVd2hcZoUhfRk1hh3X1Jd2UQiQpBsoIXTtmm4x5Mdh/XyRy3xWccmqMg630wepw7efRshwCjI5BzSrkkiabS3slEtEhOfFi4JACnlFUss7JzweV1rCV8J8RpzNm5ekAq0uuR0Bc=
Received: by 10.100.141.13 with SMTP id o13mr4749866and.1183543602791;
	Wed, 04 Jul 2007 03:06:42 -0700 (PDT)
Received: by 10.100.177.19 with HTTP; Wed, 4 Jul 2007 03:06:42 -0700 (PDT)
Message-ID: <54e41b4b0707040306m61aa139cq1e6b4a11ed34cad1@mail.gmail.com>
Date: Wed, 4 Jul 2007 11:06:42 +0100
From: "Mark Brown" <broonie@gmail.com>
To: "Randell Jesup" <rjesup@wgate.com>
Subject: Re: [AVT] RFC 2833/RFC 4733 and timestamps
In-Reply-To: <ybu7ipor8pb.fsf@jesup.eng.wgate.com>
MIME-Version: 1.0
References: <D6831742F069304FB1924B4160A493510226971B@ZMY16EXM66.ds.mot.com>
	<ybuy7i5scem.fsf@jesup.eng.wgate.com>
	<54e41b4b0706271014p39d0e6f3sf5d2e902f2046b0f@mail.gmail.com>
	<ybu7ipor8pb.fsf@jesup.eng.wgate.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0758103299=="
Errors-To: avt-bounces@ietf.org

--===============0758103299==
Content-Type: multipart/alternative; 
	boundary="----=_Part_192838_8338900.1183543602674"

------=_Part_192838_8338900.1183543602674
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 6/28/07, Randell Jesup <rjesup@wgate.com> wrote:
>
> Ok, thanks.  My preference would be to send both, but that's me.  Sounds
> like "not sending both" is likely to be better tested.  Do they round
> start/end times to packet boundaries?


Usually to at least 10ms boundaries - I'd say 10ms was more common than a
full audio frame.

>In practice it seems much more reliable to transmit with no overlap. The
> >case that tends to break is that where the RTP stream is converted into
> >audio and DTMF detection is then performed on the result. This is
> especially
> >problematic if there is a possibility that there may be DTMF encoded as
> >audio outside the RFC 2833/4733 frames. It also helps DTMF detectors to
> >leave some time after the event before restarting audio.
>
> Ick.  My guess is the above is more focused on RFC 2833 generated from
> audio data (such as an ATA attached to a POTS phone), as opposed to a pure
> digital SIP phone, which knows exactly when DMTF events are generated.


Even without gatewaying some devices choose to inject DTMF into the audio
stream when doing simultaneous RFC2833 and audio.

This also implies that start times would get delayed by up to one audio
> frame time, and durations might be rounded (up I assume) to a multiple of
> frame time.  So a 40ms tone might become a 60ms tone (with a 30ms
> packetization).  If you don't delay, but round start down and end up (to
> avoid overlaps with audio packets) you could end up with a 40ms tone
> becoming a 90ms tone.  It could also eat a lot into inter-tone gaps.


IME the tone lengths are usually accurate to at least 10ms which is
generally good enough.

When you say "more reliable", do you mean when DTMF is generated by
> detection in an audio stream (ATA+POTS example), or that "it's less likely
> to blow up or confuse someone receiving it"?  In my case, there's no POTS
> phone or detection to be done.


The issues are receiver side rather than transmission side. In a gatewaying
situation like the ATA+POTS one the transmitter doesn't care that much about
what it sends so long as the result at the remote end is what it expects.
It's something like an ATA+POTS (or even ISDN for that matter) receiver that
will have trouble with mixed audio and DTMF.

------=_Part_192838_8338900.1183543602674
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 6/28/07, <b class="gmail_sendername">Randell Jesup</b> &lt;<a href="mailto:rjesup@wgate.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">rjesup@wgate.com</a>&gt; wrote:<div><span class="gmail_quote">
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ok, thanks.&nbsp;&nbsp;My preference would be to send both, but that&#39;s me.&nbsp;&nbsp;Sounds<br>like &quot;not sending both&quot; is likely to be better tested.&nbsp;&nbsp;Do they round<br>start/end times to packet boundaries?</blockquote><div><br>

Usually to at least 10ms boundaries - I&#39;d say 10ms was more common than a full audio frame.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
&gt;In practice it seems much more reliable to transmit with no overlap. The
<br>&gt;case that tends to break is that where the RTP stream is converted into<br>&gt;audio and DTMF detection is then performed on the result. This is especially<br>&gt;problematic if there is a possibility that there may be DTMF encoded as
<br>&gt;audio outside the RFC 2833/4733 frames. It also helps DTMF detectors to<br>&gt;leave some time after the event before restarting audio.<br><br>Ick.&nbsp;&nbsp;My guess is the above is more focused on RFC 2833 generated from
<br>audio data (such as an ATA attached to a POTS phone), as opposed to a pure<br>digital SIP phone, which knows exactly when DMTF events are generated.</blockquote><div><br>Even without gatewaying some devices choose to inject DTMF into the audio stream when doing simultaneous RFC2833 and audio.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">This also implies that start times would get delayed by up to one audio<br>frame time, and durations might be rounded (up I assume) to a multiple of
<br>frame time.&nbsp;&nbsp;So a 40ms tone might become a 60ms tone (with a 30ms<br>packetization).&nbsp;&nbsp;If you don&#39;t delay, but round start down and end up (to<br>avoid overlaps with audio packets) you could end up with a 40ms tone
<br>becoming a 90ms tone.&nbsp;&nbsp;It could also eat a lot into inter-tone gaps.</blockquote><div><br>IME the tone lengths are usually accurate to at least 10ms which is generally good enough.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">

When you say &quot;more reliable&quot;, do you mean when DTMF is generated by<br>detection in an audio stream (ATA+POTS example), or that &quot;it&#39;s less likely<br>to blow up or confuse someone receiving it&quot;?&nbsp;&nbsp;In my case, there&#39;s no POTS
<br>phone or detection to be done.</blockquote><div><br>The issues are receiver side rather than transmission side. In a gatewaying situation like the ATA+POTS one the transmitter doesn&#39;t care that much about what it sends so long as the result at the remote end is what it expects. It&#39;s something like an ATA+POTS (or even ISDN for that matter) receiver that will have trouble with mixed audio and DTMF.
<br></div></div><br>

------=_Part_192838_8338900.1183543602674--


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

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

--===============0758103299==--




From avt-bounces@ietf.org Wed Jul 04 10:59:26 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I66K1-0006bU-6l; Wed, 04 Jul 2007 10:59:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I66K0-0006bP-Fz
	for avt@ietf.org; Wed, 04 Jul 2007 10:59:12 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I66Jw-0007oG-3v
	for avt@ietf.org; Wed, 04 Jul 2007 10:59:12 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 4 Jul 2007 18:00:06 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04B8F725@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Draft agenda for AVT session in Chicago
Thread-Index: Ace+TAHolJzDMJ1eQd+TMJjHstm6Og==
From: "Even, Roni" <roni.even@polycom.co.il>
To: <avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: Colin Perkins <csp@csperkins.org>, tom.taylor@rogers.com
Subject: [AVT] Draft agenda for AVT session in Chicago
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org




I uploaded the initial agenda.

Roni Even

Audio/Video Transport (AVT) Working Group
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

CHAIRS:  Colin Perkins     <csp@csperkins.org>
         Tom Taylor        <taylor@nortel.com>
         Roni Even         <roni.even@polycom.co.il>

AGENDA

Monday, 23 July 2007 at 15:20-17:20 (State Ballroom)
----------------------------------------------------
15:20   Introduction and Status Update                      (Chairs, 15)

15:35   DTLS Extension to Establish Keys for SRTP          (McGrew , 15)
        draft-ietf-avt-dtls-srtp-00.txt

15:50   Non-Compound RTCP Packets                        (Johansson, 25)
        draft-johansson-avt-rtcp-avpf-non-compound-02

16:15   H.264 Payload optional parameters              (Kristensen , 15)
        draf-ietf-avt-rtp-h264-params-00

16:30   End


Thursday, 26 July 2007 at 15:10-16:10 (Red Lacquar)
---------------------------------------------------
15:10   Using SEED Cipher Algorithm with SRTP              (Seokung, 10)
        draft-seokung-avt-seed-srtp-00

15:20   End


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



From avt-bounces@ietf.org Wed Jul 04 20:50:47 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6FYM-00050C-QL; Wed, 04 Jul 2007 20:50:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6FYM-000507-57
	for avt@ietf.org; Wed, 04 Jul 2007 20:50:38 -0400
Received: from smtp106.rog.mail.re2.yahoo.com ([68.142.225.204])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1I6FYI-0008NY-S1
	for avt@ietf.org; Wed, 04 Jul 2007 20:50:38 -0400
Received: (qmail 98741 invoked from network); 5 Jul 2007 00:50:34 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com;
	h=Received:X-YMail-OSG:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding;
	b=ND8prqMqvTc1ca7U5SRlHUxvlKGjHrIKFj8iSf2+RZtl2daPJoc7zuM0cLhmNTuj04smOLJMMjB12KMQvq4ueDDmFLeo3G45hnrFhAi5jis0udAm1qmzTDlMusJn7gMbN4X0VUEWQQPvvtpZ7Ozb7cvwM68P65Y8cnQ+gOEoVFE=
	; 
Received: from unknown (HELO ?192.168.0.100?)
	(tom.taylor@rogers.com@74.105.35.229 with plain)
	by smtp106.rog.mail.re2.yahoo.com with SMTP; 5 Jul 2007 00:50:34 -0000
X-YMail-OSG: jF7_lr8VM1mNtV4fAjxedXO5yBq4pfJ.a6R00BNl1L9tBZ69lJagf2ovm2jgs7x9XA--
Message-ID: <468C40FB.60505@rogers.com>
Date: Wed, 04 Jul 2007 20:53:15 -0400
From: Tom Taylor <tom.taylor@rogers.com>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: jo@acm.org,  Julian.chesterfield@cl.cam.ac.uk,  eve_schooler@acm.org, 
	IETF AVT WG <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: 97adf591118a232206bdb5a27b217034
Cc: 
Subject: [AVT] Comments on draft-ietf-avt-rtcpssm-13 part 1
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

These comments come way too late given the looming I-D deadline, but they may be 
helpful.

1. I suggest putting the Definitions section before the section describing basic 
operation, so the latter can build on the definitions without repeating them.

2. I found some points in the architecture were unclear. In particular, do the 
Media Senders send their RTCP sender reports to the Distribution Source or to 
Feedback Target instances?  The reason I ask this is because I wasn't sure why 
the the Media Senders needed to be configured with the transport addresses of 
the Feedback Target instances.

3. Is the following paragraph a correct summary of basic operation? If so, it 
might be considered as a replacement for much of the "Basic Operation" section.

(Editorial note: capitalization of "Media Sender", Distribution Source", and 
Feedback Target" needs to be made consistent throughout the document.  I show 
the terms captialized, but the alternative is equally acceptable.]

"One or Media Senders send RTP and RTCP sessions to the Distribution Source. 
The Distribution Source relays the RTP sessions to the receivers using a 
source-specific multicast arrangement.  In the reverse direction, each receiver 
transmits a unicast RTCP stream to a specific instance of the Feedback Target. 
Each Feedback Target instance sends either the original RTCP reports (the Simple 
Feedback Model) or summaries of these reports (the Summary Feedback model) to 
the Distribution Source, using unicast transport if it is not actually 
co-located with the Distribution Source.  The Distribution Source in turn relays 
the RTCP reports and/or summaries to the Media Sender(s). The Distribution 
Source also transmits the RTCP sender reports and receiver reports or summaries 
back out to the receivers, using source-specific multicast."

More later.

Tom

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



From avt-bounces@ietf.org Thu Jul 05 18:09:57 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6ZWJ-0004ZP-1s; Thu, 05 Jul 2007 18:09:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6ZWH-0004Z9-07
	for avt@ietf.org; Thu, 05 Jul 2007 18:09:49 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6ZWC-0004ul-6d
	for avt@ietf.org; Thu, 05 Jul 2007 18:09:48 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-4.cisco.com with ESMTP; 05 Jul 2007 15:09:43 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CABcJjUarR7MV/2dsb2JhbAA
X-IronPort-AV: i="4.16,505,1175497200"; d="scan'208"; a="6407243:sNHT19871868"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l65M9hQh006974; 
	Thu, 5 Jul 2007 15:09:43 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l65M9cXJ008767;
	Thu, 5 Jul 2007 22:09:42 GMT
Received: from xmb-sjc-222.amer.cisco.com ([128.107.191.106]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 5 Jul 2007 15:09:32 -0700
Received: from klantz-wxp.cisco.com ([10.32.139.133]) by
	xmb-sjc-222.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 5 Jul 2007 15:09:31 -0700
Message-Id: <6.2.3.4.2.20070705134916.03f86770@xmb-sjc-222.amer.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4
Date: Thu, 05 Jul 2007 15:09:27 -0700
To: "Even, Roni" <roni.even@polycom.co.il>, stewe@stewe.org,
	umesh.chandra@nokia.com, magnus.westerlund@ericsson.com,
	bo.burman@ericsson.com
From: Keith Lantz <klantz@cisco.com>
Subject: Re: [AVT] Working group last call: draft-ietf-avt-avpf-ccm-07
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C04A70650@IsrExch01.israel.
	polycom.com>
References: <144ED8561CE90C41A3E5908EDECE315C04A70650@IsrExch01.israel.polycom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 05 Jul 2007 22:09:31.0334 (UTC)
	FILETIME=[29875660:01C7BF51]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=10274; t=1183673383;
	x=1184537383; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=klantz@cisco.com;
	z=From:=20Keith=20Lantz=20<klantz@cisco.com>
	|Subject:=20Re=3A=20[AVT]=20Working=20group=20last=20call=3A=20draft-ietf
	-avt-avpf-ccm-07 |Sender:=20;
	bh=jXEmGAZz8xKa5qgKJuZub5ZFFAxdshF0V4zI2idnNd8=;
	b=u5Rmv3tTpUS1EGJKfGwZ5kqYVWErt6NBfIAmFjFQCpUEVQqwZenhFd3wafD0AnddhsZa1T4M
	VmIMbO3zkQ1F2qG2sUK2E2+faNNgpRQddKZWcIdXQpXskZ/t8A2Gf/2PhSmDiTv+B/v4JlFZ0w
	J5Bo1xgzeOYlnXbW8eZzZ1LCQ=;
Authentication-Results: sj-dkim-1; header.From=klantz@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 65bc4909d78e8b10349def623cf7a1d1
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

As promised, here are my comments on the latest draft:

- First and foremost, this is *much* improved since the last version 
I reviewed (version 03). The result is that these comments are almost 
exclusively minor editorial nits. My compliments to the authors (and 
anyone else who contributed to that improvement)!

- Arguably the only non-editorial comment is this: In Section 4.3.3.2 
it says that if the recipient of a TSTR receives several TSTRs with 
different sequence numbers, it "SHALL" only respond to the request 
with the highest sequence number. Unfortunately, the sequence numbers 
are modulo 256, which means there will be occasions where the 
recipient will respond to an *older* request -- when a more recent 
request wraps back to 0. Is this not a problem?


Now for the editorial comments:

- The "header" on the 2nd and subsequent pages contains a fairly 
non-descriptive title: "AVPF RTCP-RR Extensions". Something like 
"Codec Control Messages in AVPF" would seem much more appropriate.

- Section 2.1 and elsewhere: "AMID" --> "AIMD".

- Section 2.2, defn. of stream thinning: "when subject to" --> "when 
subjected to"

- Section 2.3, defn. of Topo-Multicast: consider deleting "as in RFC 3550"

         defn. of Topo-Translator: "translator based as" --> 
"translator-based communication" & consider deleting "as in RFC 3550"

         defn. of Topo-Mixer: "mixer based as" --> "mixer-based 
communication" & consider deleting "as in RFC 3550"

         defn. of Topo-Video-switch-MCU: eliminate the closing comma

         defn. of Topo-RTCP-terminating MCU: replace with 
"RTCP-terminating, mixer-based communication"

- Section 3.1, item 7: "AMID" --> AIMD"

         "does generally result" --> "generally results"

- Section 3.5.1, 2nd paragraph: Given the widespread use of "FVU" for 
this functionality, add "fast video update" to the list of "also known as".

         3rd paragraph: "MPEG-4" --> "MPEG-4 Part 2"

         5th paragraph: Restructure 2nd sentence as "A receiver that 
receives a request closely after sending a decoder refresh point -- 
within 2 times the longest Round Trip Time (RTT) known, plus and 
AVPF-induced RTCP packet sending delays -- should await ..."

- Section 3.5.2, 3rd paragraph: "finally the new trade-off is 
selected" --> "the new trade-off is finally selected"

         4th paragraph: "translator, mixer or endpoint's" --> 
"translator's, mixer's or endpoint's"

- Section 3.5.2.3, 2nd paragraph: Remove comma after "(and bit rate)".

- Section 3.5.2.4: Consider replacing "request-sender" with "requester".

- Section 3.5.3: "oversimplifying" --> "oversimplified"

         p. 19: Insert comma after "messages" in "In response to the 
opaqueness of the H.271 messages"

- Section 3.5.3.1: Remove the closing period from "clause 3.5.1.1.". 
(This is the case for several other cross-references as well. Then 
too, several cross-references have line breaks inserted -- e.g. the 
reference to section 3.5.4.2 at the top of p. 40.)

- Section 3.5.4, 3rd paragraph: Restructure last sentence as "... 
because calculations are carried out in terms of variables that have 
the same value at the sender as at the receiver -- for example, 
packet rate and net media rate."

- Section 3.5.4.2, 2nd paragraph: Insert commas after "First" and 
"Fortunately".

         p. 26, the "basic idea" paragraph: This discussion should 
probably make explicit that the X and Y axes comprise two sides of 
the "polygon" under discussion. Perhaps "The lower envelope of the 
set of lines corresponding to the complete set of TMMR tuples, 
together with the X and Y axes, defines a polygon."

- Section 3.5.4.3, 2nd paragraph: Restructure as "In practice, 
unfortunately, media-aware streaming thinning is a very ..."

- Section 4.2, opening paragraph: Note that the syntax used here is 
not identical to that used in Section 4.3. Here you write "RTCP 
packet type value RTPFB", whereas in Section 4.3 you write "RTCP 
packet type value PT=PSFB" -- i.e. you insert the "PT=". Either way 
works, but you should be consistent.

- Section 4.2.1.1, defn. of Measured Overhead: "according to 
description" --> "according to the description"

- Section 4.2.1.1 (& also 4.2.2.1): Similar to the next to previous 
comment, the structure used here is not identical to that used in 
Sections 4.3.1, 4.3.2 and 4.3.3. In the latter sections you include 
sentences that specify the PT and FMT values -- e.g. "The FIR message 
is identified by RTCP packet type value PT=PSFB and FMT=4." Here (and 
in 4.2.2.1) you do *not* include such sentences. Again, either way 
works, but you should be consistent.

- Section 4.2.1.2: As per a similar comment above, "See section 5." 
--> "See section 5".

- Section 4.3: As noted above, the syntax used here is not identical 
to that used in Section 4.2. Here you write "RTCP packet type 
value  PT=PSFB", whereas in Section 4.3 you write "RTCP packet type 
value RTPFB" -- i.e. *without* the "PT=". Either way works, but you 
should be consistent.

- Section 4.3.1: Similarly, the structure use here (and in Sections 
4.3.2 and 4.3.3) is not the same as that used in Sections 4.2.1.1 and 
4.2.2.1. See the comment on Section 4.2.1.1 above for further clarification.

- Section 4.3.1.2: There are a *lot* of "Notes" in this section that 
really impair readability. Strongly suggest that this section be 
rewritten/restructured to incorporate most of that content in the 
body of the section itself.

         Also, in the 2nd note: "However a session" --> "However, a 
session". (This happens elsewhere as well. I just didn't flag them all.)

         And "reasons, such an application SHOULD also be capable to 
receive and react" --> "reasons such an application SHOULD also be 
capable of receiving and reacting".

- Section 4.3.1.5: "Hence waiting" --> "Hence, waiting". (Ditto for 
similar sentences elsewhere.)

- Section 4.3.2: See comment on Section 4.2.1.1 above.

         Defn. of Index (& elsewhere): "trade off" --> "trade-off"
                 "value of 0 index" --> "value of 0 indicates"

- Section 4.3.2.2: "to which the TSTR applies to" --> "to which the 
TSTR applies"

- Section 4.3.2.3: "requires a quick feedback" --> "requires quick feedback"

- Section 4.3.2.4: Contains another of several cross-references where 
line breaks have been erroneously inserted.

- Section 4.3.2.5: "refer to the resolution, measured" --> "refer to 
resolution as measured"

- Section 4.3.3: See comment on Section 4.2.1.1 above.

- Section 4.3.3.2: The second sentence is really hard to follow. The 
following might be at least marginally better: "One TSTN entry in a 
TSTN feedback message SHALL be sent for each TSTR entry targeted at 
the sender (of the TSTN message) -- i.e., each TSTR entry that 
contains the sender in its SSRC field."

- Section 4.3.4: See comment on Section 4.2.1.1 above.

- Section 4.2.4.5: Contains another of cross-reference where a line 
break has been erroneously inserted.

- Section 5 (& elsewhere): "Thus modified" --> "Thus, modified"

         "reduced transmission bit rate thus" --> "reduced 
transmission bit rate, thus"

- Section 6, enumerated list: The structure of these bullets is 
inconsistent -- with the first three being structured as if they were 
all part of the same sentence, separated by semi-colons, and the 
fourth being its own sentence. They should all be structured as 
self-standing sentences or the fourth should incorporated into the 
same "sentence" as the previous three.

- Section 7: Drop the "protocol" from "codec control protocol".

         first paragraph on p. 59: Insert comma after "For example".

         Rewrite the two sentences preceding the bullet list as 
follows: 'The "ccm" feedback value SHOULD be used with parameters 
that indicate the specific codec control commands supported. In this 
draft we define four such parameters, namely:"

         Then, in every bullet: "indicates the support" --> "indicates support"

- Section 7.2: "are similar those" --> "are similar to those"

         "parameters which it does" --> "parameters that it does"

         "everyone shall use" --> "everyone SHALL use"

- Section 7.3, last sentence: "So in the above example only" --> "So, 
in the above example, only".


That's it!

Regards, Keith


At 02:51 AM 6/20/2007, Even, Roni wrote:

>This is to announce a working group last call on the Codec Control 
>Messages in the RTP Audio-Visual Profile with Feedback (AVPF).
>
>This is a second last call after the authors addressed comments in the list
>
>Please send any final comments to the mailing list by July 6th 2007.
>
>If no issues are raised, we will request the IESG consider this for 
>publication as a Proposed Standard RFC.
>
>Thanks
>Roni Even - AVT co-chair
>
>
>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           : Codec Control Messages in the RTP 
> Audio-Visual Profile with Feedback (AVPF)
>         Author(s)       : S. Wenger, et al.
>         Filename        : draft-ietf-avt-avpf-ccm-07.txt
>         Pages           : 71
>         Date            : 2007-6-1
>
>This document specifies a few extensions to the messages defined
>    in the Audio-Visual Profile with Feedback (AVPF).  They are
>    helpful primarily in conversational multimedia scenarios where
>    centralized multipoint functionalities are in use.  However some
>    are also usable in smaller multicast environments and point-to-
>    point calls.  The extensions discussed are messages related to the
>    ITU-T H.271 Video Back Channel, Full Intra Request, Temporary
>    Maximum Media Stream Bit Rate and Temporal Spatial Trade-off.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-avt-avpf-ccm-07.txt
>
>
>_______________________________________________
>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 Jul 05 18:44:01 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6a3L-0000BP-E6; Thu, 05 Jul 2007 18:43:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6a3K-0000BE-K0; Thu, 05 Jul 2007 18:43:58 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I6a3K-0005ix-Bk; Thu, 05 Jul 2007 18:43:58 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id B9FD032932;
	Thu,  5 Jul 2007 22:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I6ZbK-0006Hf-Kk; Thu, 05 Jul 2007 18:15:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I6ZbK-0006Hf-Kk@stiedprstage1.ietf.org>
Date: Thu, 05 Jul 2007 18:15:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rfc3119bis-04.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: A More Loss-Tolerant RTP Payload Format for MP3 Audio
	Author(s)	: R. Finlayson
	Filename	: draft-ietf-avt-rfc3119bis-04.txt
	Pages		: 0
	Date		: 2007-7-5
	
This document describes a RTP (Real-Time Protocol) payload format for
    transporting MPEG (Moving Picture Experts Group) 1 or 2, layer III
    audio (commonly known as "MP3").  This format is an alternative to
    that described in RFC 2250, and performs better if there is packet
    loss.  (This document updates RFC 3119, correcting typographical
    errors in the "SDP usage" section and pseudo-code appendices.)

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc3119bis-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-rfc3119bis-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-rfc3119bis-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

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

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

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

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

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

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


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org Thu Jul 05 18:46:02 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6a5J-000449-Rl; Thu, 05 Jul 2007 18:46:01 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6a5I-00043u-Er
	for avt@ietf.org; Thu, 05 Jul 2007 18:46:00 -0400
Received: from porter.east.isi.edu ([65.114.168.19])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6a5I-0002mS-6e
	for avt@ietf.org; Thu, 05 Jul 2007 18:46:00 -0400
Received: from [192.168.1.108] (pool-141-156-217-195.washdc.east.verizon.net
	[141.156.217.195])
	by porter.east.isi.edu (Postfix) with ESMTP id 7D2A61FB6;
	Thu,  5 Jul 2007 18:45:27 -0400 (EDT)
In-Reply-To: <C2AEE590.7492%gorry@erg.abdn.ac.uk>
References: <C2AEE590.7492%gorry@erg.abdn.ac.uk>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <DB5273EF-BDE4-4414-B4C2-A860CACF989D@isi.edu>
Content-Transfer-Encoding: 7bit
From: Ladan Gharai <ladan@isi.edu>
Subject: Re: [AVT] Comments on draft-ietf-avt-tfrc-profile-08.txt
Date: Thu, 5 Jul 2007 18:45:23 -0400
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org


On Jul 2, 2007, at 11:25 AM, Gorry Fairhurst wrote:

>
> Ladan
>
> I enclose some comments after reading your latest rev of
> draft-ietf-avt-tfrc-profile.  These comments concern questions on RFC
> keywords, and some other queries. I will send editorial comments  
> separately.

    Thank you for raising the point of the RFC keyword usage in the  
draft,  as it was somewhat lax, particularly in Section 7.  I have  
addressed them below and welcome more feedback.
>
> Please do keep me in the loop on further revisions, I'd be happy to  
> read.

    Thank you, I will be submitting a revised draft before the monday  
deadline.
>
>  Best wishes,
>
>  Gorry Fairhurst
>
> ----
>
> Questions:
> Section 7., paragraph 3:
> OLD:
>     Based on initial assumptions on round trip time if more than the
>     recommended 5% is needed for RTCP bandwidth, the applications  
> should
>     use the SDP bandwidth modifiers RS and RR [3556] to signal the  
> amount
>     of RTCP bandwidth needed. Should this assumptions change once  
> the RTP
>     flows are running, the application can recalculate the amount  
> of RTCP
>     bandwidth needed and resignal this new value using its signaling
>     protocol of choice.
> = The phrase "should take into account" needs some clarification
> (a) Is this a RFC2119 "SHOULD"?
> (b) Please clarify "take into account", what does this imply, is it  
> just a
> matter of increasing the advertised bandwidth value?

     This paragraph seems to be a mine field of RFC keywords! below  
is a slightly rewritten one, which I hope is less ambiguous.
>
> - The phrase "should use the SDP bandwidth modifiers RS and RR"
> Is this a RFC2119 "SHOULD"?
>
> Section 7.
>
> - The phrase "the application can recalculate the amount of RTCP  
> bandwidth"
> - Is this a RFC2119 "MAY" or "SHOULD"


     Based on initial assumptions on round trip time if more than the
     recommended 5% is needed for RTCP bandwidth, the applications  
SHOULD
     use the SDP bandwidth modifiers RS and RR [3556] to signal the  
amount
     of RTCP bandwidth needed. If the round trip time assumptions  
change after the RTP
     flows start running, the application MAY recalculate the amount  
of RTCP
     bandwidth needed and resignal this new value using its signaling
     protocol of choice.

>
> Section 8., paragraph 0:
> - The phrase: "the AVPF T_rr_interval variable must not be set"
> - Is this a RFC2119 "MUST NOT"?

      This should be a MUST NOT - as setting T_rr_interval to a value  
higher than the current RTT will disrupt the TFRC timing requirements
>
>
> Section 8., paragraph 2:
> - The phrase: "must signal their use of the AVPF profile"
> - Is this a RFC2119 "MUST"?

       Yes.
>
> - The phrase: "and optionally an initial"
> -  Consider changing to "and optionally MAY sends an initial"

      This should probably be consistent with para 3 of section 7 -  
which says SHOULD


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



From avt-bounces@ietf.org Thu Jul 05 20:15:35 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6bTV-0005jj-0w; Thu, 05 Jul 2007 20:15:05 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6bTS-0005jL-O9; Thu, 05 Jul 2007 20:15:02 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I6bTS-0007Dl-Ha; Thu, 05 Jul 2007 20:15:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 431EB175E7;
	Fri,  6 Jul 2007 00:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I6bTR-0008Qd-Qw; Thu, 05 Jul 2007 20:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I6bTR-0008Qd-Qw@stiedprstage1.ietf.org>
Date: Thu, 05 Jul 2007 20:15:01 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtcpxr-audio-00.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: RTCP XR - Audio Metrics Report Block
	Author(s)	: A. Clark, A. Pendleton
	Filename	: draft-ietf-avt-rtcpxr-audio-00.txt
	Pages		: 
	Date		: 2007-7-5
	
   This document defines extensions to the RTCP XR extended report
   packet type blocks to support the performance monitoring of audio
   streams transmitted using RTP. 
   This draft is one of a set of four that replace the -00 version
   of the ietf-avt-rtcpxr-video-00.txt draft.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcpxr-audio-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-rtcpxr-audio-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-rtcpxr-audio-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

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

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

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

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

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

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


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org Thu Jul 05 23:39:43 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6efT-0007Rz-LH; Thu, 05 Jul 2007 23:39:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6efR-0007R6-UB
	for avt@ietf.org; Thu, 05 Jul 2007 23:39:37 -0400
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I6efM-0001Dm-So for avt@ietf.org; Thu, 05 Jul 2007 23:39:37 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 5 Jul 2007 23:39:32 -0400
To: Keith Lantz <klantz@cisco.com>
Subject: Re: [AVT] Working group last call: draft-ietf-avt-avpf-ccm-07
References: <144ED8561CE90C41A3E5908EDECE315C04A70650@IsrExch01.israel.polycom.com>
	<6.2.3.4.2.20070705134916.03f86770@xmb-sjc-222.amer.cisco.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Thu, 05 Jul 2007 23:39:30 -0400
In-Reply-To: <6.2.3.4.2.20070705134916.03f86770@xmb-sjc-222.amer.cisco.com>
	(Keith Lantz's message of "Thu, 05 Jul 2007 15:09:27 -0700")
Message-ID: <ybu8x9u19ql.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 06 Jul 2007 03:39:32.0427 (UTC)
	FILETIME=[43E659B0:01C7BF7F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: magnus.westerlund@ericsson.com, stewe@stewe.org, "Even,
	Roni" <roni.even@polycom.co.il>, avt@ietf.org,
	umesh.chandra@nokia.com, bo.burman@ericsson.com
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Keith Lantz <klantz@cisco.com> writes:
>- Arguably the only non-editorial comment is this: In Section 4.3.3.2 it
>says that if the recipient of a TSTR receives several TSTRs with different
>sequence numbers, it "SHALL" only respond to the request with the highest
>sequence number. Unfortunately, the sequence numbers are modulo 256, which
>means there will be occasions where the recipient will respond to an
>*older* request -- when a more recent request wraps back to 0. Is this not
>a problem?

Not if you use "normal" unsigned-sequence-number math, and define 'older'
and 'newer' to be ranges of around +- 127/128 modulo 256 from the current
value.  This math is used all the time in sequence number and timestamp
comparisons.  So long as 1/2 the sequence bits is enough time in the
forward and backward directions to avoid realistic packet reordering/loss
issues, you're ok.

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


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



From avt-bounces@ietf.org Fri Jul 06 06:40:13 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6lEM-0003Mq-QY; Fri, 06 Jul 2007 06:40:06 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6lEL-0003Mf-AS
	for avt@ietf.org; Fri, 06 Jul 2007 06:40:05 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6lEL-00070Y-0V
	for avt@ietf.org; Fri, 06 Jul 2007 06:40:05 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:52386)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1I6lDI-0006dZ-95; Fri, 06 Jul 2007 11:39:00 +0100
In-Reply-To: <0MKpCa-1I2qYK1rf9-0001br@mrelay.perfora.net>
References: <0MKp8S-1I10wF3BuK-0002si@mrelay.perfora.net>
	<FC7B9B6B-15D8-4B2F-82CD-3E1092F92E77@csperkins.org>
	<p0624088fc2a52a180bde@[17.202.35.52]>
	<0MKpCa-1I2qYK1rf9-0001br@mrelay.perfora.net>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <6B8A5826-4920-4340-8C2A-A99FF749A17B@csperkins.org>
Content-Transfer-Encoding: quoted-printable
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] draft-ietf-avt-hdrext-12
Date: Fri, 6 Jul 2007 11:39:04 +0100
To: Michael A Dolan <md.1@newtbt.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Mike,

On 25 Jun 2007, at 16:32, Michael A Dolan wrote:
> In review of the actual sub-extensions in use, they could =20
> theoretically have been implemented with the design in the ID. =20
> There is evidence that their work pre-dated hdrext-00, so it =20
> appears purely a historical accident.
>
> FYI, I have been retained by the implementers to publicly document =20
> their work, and am beginning that process.  So, this is not =20
> research project or informational report.

Without knowing the community of support for this mechanism, would it =20=

make sense to document it as an Informational RFC, with the =20
recommendation that implementations move to using Dave's draft over =20
time (i.e. in much the way draft-hunt-avt-rtcpxnq-00.txt documents =20
BT's RTCP XR extensions)?

> I don't have any data on how widely deployed the system is - I =20
> could inquire. Although I understand the rationale for the =20
> question, I hesitate to enter into a debate over relative =20
> "deployedness".  Regardless of the measure used (# units, #sites, =20
> #independent implementations), I need to document what they did (at =20=

> least in a compatible way).  I have therefore personally leapt to =20
> the state of mind of both designs being fait =E0 compli, so my intent =20=

> was to capture the two variants in one place as the next best thing =20=

> to a single design.  FYI, it is possible to discriminate the two =20
> easily and unambiguously without altering Dave's design.
>
> Would it be helpful to see the details?

Probably.

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



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



From avt-bounces@ietf.org Fri Jul 06 07:09:56 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6lhC-0003cg-3C; Fri, 06 Jul 2007 07:09:54 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6lhA-0003SK-6B
	for avt@ietf.org; Fri, 06 Jul 2007 07:09:52 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6lh9-0000Ol-Oc
	for avt@ietf.org; Fri, 06 Jul 2007 07:09:52 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	17BCE2167D; Fri,  6 Jul 2007 13:09:43 +0200 (CEST)
X-AuditID: c1b4fb3e-b2038bb0000007e1-fb-468e22f741a1
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	F2AB6204B6; Fri,  6 Jul 2007 13:09:42 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 6 Jul 2007 13:09:42 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 6 Jul 2007 13:09:41 +0200
Message-ID: <468E22F6.6070504@ericsson.com>
Date: Fri, 06 Jul 2007 13:09:42 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: Keith Lantz <klantz@cisco.com>
Subject: Re: [AVT] Working group last call: draft-ietf-avt-avpf-ccm-07
References: <144ED8561CE90C41A3E5908EDECE315C04A70650@IsrExch01.israel.polycom.com>
	<6.2.3.4.2.20070705134916.03f86770@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <6.2.3.4.2.20070705134916.03f86770@xmb-sjc-222.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Jul 2007 11:09:41.0874 (UTC)
	FILETIME=[26C8E520:01C7BFBE]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: stewe@stewe.org, "Even, Roni" <roni.even@polycom.co.il>,
	bo.burman@ericsson.com, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Thanks for the comments.

Keith Lantz skrev:
> As promised, here are my comments on the latest draft:
> 
> - First and foremost, this is *much* improved since the last version I 
> reviewed (version 03). The result is that these comments are almost 
> exclusively minor editorial nits. My compliments to the authors (and 
> anyone else who contributed to that improvement)!

Thanks, and a lot of gratefulness from us authors goes to Tom Taylor 
that made a significant contribution on rewriting the worst part.

> 
> - Arguably the only non-editorial comment is this: In Section 4.3.3.2 it 
> says that if the recipient of a TSTR receives several TSTRs with 
> different sequence numbers, it "SHALL" only respond to the request with 
> the highest sequence number. Unfortunately, the sequence numbers are 
> modulo 256, which means there will be occasions where the recipient will 
> respond to an *older* request -- when a more recent request wraps back 
> to 0. Is this not a problem?
> 

I think the easiest resolution is to be clear that this is in modulo 
arithmetic. Sure some carefullnes are needed.

I will try to address the editorial comments before the deadline. If 
there are any unclarities or disagreemetns I will send a reply about this.

Thanks

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
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 Jul 06 11:30:40 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6plT-0006BB-Cm; Fri, 06 Jul 2007 11:30:35 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6plR-00067c-1l; Fri, 06 Jul 2007 11:30:33 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I6plQ-0004Ut-QH; Fri, 06 Jul 2007 11:30:32 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 83046175CD;
	Fri,  6 Jul 2007 15:30:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I6pkw-0000Gy-3P; Fri, 06 Jul 2007 11:30:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I6pkw-0000Gy-3P@stiedprstage1.ietf.org>
Date: Fri, 06 Jul 2007 11:30:02 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-topologies-05.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

                                                                                           
        Title           : RTP Topologies
        Author(s)       : M. Westerlund, S. Wenger
        Filename        : draft-ietf-avt-topologies-05.txt
        Pages           : 21
        Date            : 2007-07-06
                                                                                           
This document discucsses multi-endpoint topologies used in RTP
based environments.  In particular, centralized topologies commonly
employed in the video conferencing industry are mapped to the RTP
terminology.
                                                                                           
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-topologies-05.txt
                                                                                           
To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.
                                                                                           
                                                                                           
Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
        "get draft-ietf-avt-topologies-05.txt".
                                                                                           
A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
                                                                                           
                                                                                           
Internet-Drafts can also be obtained by e-mail.
                                                                                           
Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE /internet-drafts/draft-ietf-avt-topologies-05.txt".
                                                                                           
NOTE:   The mail server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" utility.  To use this
        feature, insert the command "ENCODING mime" before the "FILE"
        command.  To decode the response(s), you will need "munpack" or
        a MIME-compliant mail reader.  Different MIME-compliant mail readers
        exhibit different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have been split
        up into multiple messages), so check your local documentation on
        how to manipulate these messages.
                                                                                           
                                                                                           
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
                                                                                           
--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"
Content-Type: text/plain
Content-ID: <2007-07-06112855.I-D@ietf.org>


ENCODING mime
FILE /internet-drafts/draft-ietf-avt-topologies-05.txt
                                                                                           
--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-avt-topologies-05.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"
Content-Type: text/plain
Content-ID: <2007-07-06112855.I-D\@ietf.org>



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

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

--NextPart--




From avt-bounces@ietf.org Fri Jul 06 12:06:31 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6qKB-0007SB-IT; Fri, 06 Jul 2007 12:06:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6qKA-0007S0-HK
	for avt@ietf.org; Fri, 06 Jul 2007 12:06:26 -0400
Received: from mout.perfora.net ([74.208.4.194])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6qKA-0000Jy-79
	for avt@ietf.org; Fri, 06 Jul 2007 12:06:26 -0400
Received: from [71.136.175.166] (helo=TBT-Laptop.newtbt.com)
	by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis),
	id 0MKpCa-1I6qJF0mlZ-0001ce; Fri, 06 Jul 2007 12:05:53 -0400
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 06 Jul 2007 08:38:49 -0700
To: AVT WG <avt@ietf.org>
From: Michael A Dolan <md.1@newtbt.com>
Subject: Re: [AVT] draft-ietf-avt-hdrext-12
In-Reply-To: <6B8A5826-4920-4340-8C2A-A99FF749A17B@csperkins.org>
References: <0MKp8S-1I10wF3BuK-0002si@mrelay.perfora.net>
	<FC7B9B6B-15D8-4B2F-82CD-3E1092F92E77@csperkins.org>
	<p0624088fc2a52a180bde@[17.202.35.52]>
	<0MKpCa-1I2qYK1rf9-0001br@mrelay.perfora.net>
	<6B8A5826-4920-4340-8C2A-A99FF749A17B@csperkins.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Message-ID: <0MKpCa-1I6qJF0mlZ-0001ce@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX18iIeLCnc1alRVV55ZP6EUnQo6MsHLHa15XB4D
	BZsYauymYPdAVmVegOHj+dJfbW0KlrZIlW2gLVJW1PODMxHS9J
	kXdbcGhHTmjUiOjH5l6Yg==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Colin-

A 2nd Informational RFC was my "plan B".  But=20
before we abandon the idea of a single document,=20
let me explain more details and how the two could=20
be merged.  I'll do this in a brief email (rather=20
than an ID) under separate cover.

Regards,

         Mike

At 03:39 AM 7/6/2007, Colin Perkins wrote:
>Mike,
>
>On 25 Jun 2007, at 16:32, Michael A Dolan wrote:
>>In review of the actual sub-extensions in use, they could
>>theoretically have been implemented with the design in the ID.
>>There is evidence that their work pre-dated hdrext-00, so it
>>appears purely a historical accident.
>>
>>FYI, I have been retained by the implementers to publicly document
>>their work, and am beginning that process.  So, this is not
>>research project or informational report.
>
>Without knowing the community of support for this mechanism, would it
>make sense to document it as an Informational RFC, with the
>recommendation that implementations move to using Dave's draft over
>time (i.e. in much the way draft-hunt-avt-rtcpxnq-00.txt documents
>BT's RTCP XR extensions)?
>
>>I don't have any data on how widely deployed the system is - I
>>could inquire. Although I understand the rationale for the
>>question, I hesitate to enter into a debate over relative
>>"deployedness".  Regardless of the measure used (# units, #sites,
>>#independent implementations), I need to document what they did (at
>>least in a compatible way).  I have therefore personally leapt to
>>the state of mind of both designs being fait =E0 compli, so my intent
>>was to capture the two variants in one place as the next best thing
>>to a single design.  FYI, it is possible to discriminate the two
>>easily and unambiguously without altering Dave's design.
>>
>>Would it be helpful to see the details?
>
>Probably.
>
>Cheers,
>--
>Colin Perkins
>http://csperkins.org/
>


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



From avt-bounces@ietf.org Fri Jul 06 14:44:36 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6sn7-000308-8Q; Fri, 06 Jul 2007 14:44:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6sn6-0002x5-Dq; Fri, 06 Jul 2007 14:44:28 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I6sn6-000517-5z; Fri, 06 Jul 2007 14:44:28 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 31F1332934;
	Fri,  6 Jul 2007 18:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I6sKc-0002uK-2R; Fri, 06 Jul 2007 14:15:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I6sKc-0002uK-2R@stiedprstage1.ietf.org>
Date: Fri, 06 Jul 2007 14:15:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-atrac-family-09.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: RTP Payload Format for Adaptive TRansform Acoustic Coding (ATRAC) Family
	Author(s)	: J. Matsumoto, M. Hatanaka
	Filename	: draft-ietf-avt-rtp-atrac-family-09.txt
	Pages		: 29
	Date		: 2007-7-6
	
This document describes an RTP payload format for efficient and
   flexible transporting of audio data encoded with the Adaptive
   TRansform Audio Coding (ATRAC) family of codecs.  Recent enhancements
   to the ATRAC family of codecs support high quality audio coding with
   multiple channels.  The RTP payload format as presented in this
   document also includes support for data fragmentation, elementary
   redundancy measures, and a variation on scalable streaming.

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

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

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

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

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

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

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

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

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

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

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

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

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


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org Fri Jul 06 16:21:37 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6uJ5-000273-28; Fri, 06 Jul 2007 16:21:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6uJ3-00026x-NA
	for avt@ietf.org; Fri, 06 Jul 2007 16:21:33 -0400
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.43)
	id 1I6uIz-0003aT-AS for avt@ietf.org; Fri, 06 Jul 2007 16:21:33 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-2.cisco.com with ESMTP; 06 Jul 2007 13:21:29 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAFZAjkarR7MVZmdsb2JhbACPNgsO
X-IronPort-AV: i="4.16,509,1175497200"; 
	d="scan'208"; a="384103611:sNHT27115836"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l66KLSEG001913
	for <avt@ietf.org>; Fri, 6 Jul 2007 13:21:28 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l66KLSka009783
	for <avt@ietf.org>; Fri, 6 Jul 2007 20:21:28 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 6 Jul 2007 13:21:28 -0700
Received: from [10.32.241.146] ([10.32.241.146]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 6 Jul 2007 13:21:28 -0700
Message-ID: <468EA44B.1020305@cisco.com>
Date: Fri, 06 Jul 2007 16:21:31 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: "'avt@ietf.org'" <avt@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Jul 2007 20:21:28.0213 (UTC)
	FILETIME=[3BB35450:01C7C00B]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1629; t=1183753288;
	x=1184617288; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20ICE=20tutorial=20in=20Chicago=20[DO=20NOT=20REPLY]
	|Sender:=20; bh=/a2gGbj9z3uAeaOyVraQo7NcVcWVa35n/rdAvyWYEgQ=;
	b=UQKPgDh0KBvDtciCyrRKQTPIF7i57Q/Slc3IbQKetXA7p89+6+fHMN3N13k4+uG8Xf2vIuyG
	yDjqvB7RS6pxZqh8VqztbZ+Ak06nO7ZisgKDShENTvl4PD0K43YvE/BoH1vl4kfJ9RXK99UbyY
	xaZbqXRWv8Cz+1xOuO9ZwNa5o=;
Authentication-Results: sj-dkim-1; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Subject: [AVT] ICE tutorial in Chicago [DO NOT REPLY]
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

(Apologies to multiple recipients)
(DO NOT REPLY)

WHAT:     Tutorial on Interactive Connectivity Establishment (ICE)
       (http://www.ietf.org/internet-drafts/draft-ietf-mmusic-ice-16.txt)
           [-17 should be available shortly]

WHEN:     Tuesday, July 24, 2007, 1145-1245
           (lunch logistics are in progress and will be announced ASAP)

WHERE:    Red Lacquar

WHO:      Anyone that would like to learn more about ICE.

WHY:      ICE, developed by the mmusic working group, has been
           defined as the IETF tool for NAT traversal for SIP-based
           media. It is also seeing increased usage for traversal
           for other kinds of application traffic - anything worrying
           about any-to-any communications. In this tutorial, we will
           overview the background of the problem, consider the
           requirements driving ICE, and provide an overview of
           how ICE works. An understanding of SIP is not required.
           The tutorial will be based on the pending -17 version.

RSVP:     Please send a note to me with the Subject line "ice-is-nice"
           (mailto:jdrosen@cisco.com?Subject=ice-is-nice) so I can get a
           count of the number of participants for lunch purposes.


!DO NOT REPLY TO THIS NOTE!
-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Cisco Fellow                                   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com






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



From avt-bounces@ietf.org Fri Jul 06 17:32:09 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6vPB-0001Sb-Eo; Fri, 06 Jul 2007 17:31:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6vPA-0001QJ-Bq
	for avt@ietf.org; Fri, 06 Jul 2007 17:31:56 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6vP5-00026C-Tw
	for avt@ietf.org; Fri, 06 Jul 2007 17:31:56 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 7 Jul 2007 00:32:47 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04B8F936@IsrExch01.israel.polycom.com>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C04A70650@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Review draft-ietf-avt-avpf-ccm-07
Thread-Index: AcezIJhcq7jJrzUZSrayJm9ow4zxcAM7ZHJw
From: "Even, Roni" <roni.even@polycom.co.il>
To: <avt@ietf.org>,
	"Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Cc: bo.burman@ericsson.com, stewe@stewe.org, avt-chairs@tools.ietf.org
Subject: [AVT] Review draft-ietf-avt-avpf-ccm-07
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi
It took me some time but I have some comments and nits

1. In section 3.5.2 I suggest to delete "(as it is common in =
state-of-the-art video conferencing systems). I am not sure that it adds =
value and voice an opinion.

2. In 4.2.1.2 " If the media sender concludes that it can increase the =
maximum total media bit rate value, it SHALL wait before actually doing =
so, for a period long enough to allow a media receiver to respond to the =
TMMBN if it determines that its tuple belongs in the bounding set."

I was wondering if the SHALL is also true for unicast point to point =
case.

3. In 4.2.2.2
"As indicated in section 4.2.1.2, when a media sender determines
   that an "owner" of a bounding tuple has left the session, then
   that tuple is removed from the bounding set, and the media sender
   SHALL send a TMMBN message indicating the remaining bounding
   tuples.  If there are no remaining bounding tuples a TMMBN without
   any FCI SHALL be sent to indicate this."

If there are no remaining bounding set what is the current bit rate. =
Does it mean that the sender may raise the bit rate to the negotiated =
rate in the signaling.


4. In 4.3.1.2

Do we need the note bellow in the final version.

"Note: Mandating a maximum delay for completing the sending of a decoder =
refresh point would be desirable from an application     viewpoint, but =
is problematic from a congestion control point of view.  "As soon as =
possible" as mentioned above appears to be a reasonable compromise"


5. in section 7.1 " MaxPacketRateValue =3D 1*15DIGIT" what are the units =
for this parameter. I think that based on the example it is in 1000's of =
bits per second but please clarify.
Fix the value in example 3 based on the units, currently it say 120 and =
I assumed 120*1000 bits/s


6. In the 7.2 " The offerer MAY indicate the capability to support =
selected codec commands and indications.  The answerer MUST remove all =
ccm parameters which it does not understand or does not wish to use in =
this particular media session."
I am not sure what you mean do not want to use, is it does not want to =
send or just does not want to receive but may send.=20
Based on your response the text for the answer in example 3 should have =
the same semantics.
=20







Nits:

1. Bounding set definition in 2.2 "such as that in section 3   " there =
is a linefeed that should not be there.

Same in 4.2.1.2 " corresponding algorithm defined in section
   3.5.4.2."

Same in the end of 4.3.2.4

Same in the beginning 0f 4.3.4.5




2. In 2.3 "topo-video-switch-mcu" should be "topo-rtp-switch-mcu" also =
change the other video-swicth in the same line

3. in 3.5.1.1

"An RTP mixer that receives an FIR from a media receiver is"
Suggset change to=20
"An RTP mixer or RTP switching MCU that receives a FIR from a media =
receiver is"

4. The last paragraph of 3.5.2 " four TSTR/TSTN scenarios need to be =
distinguished, based on the topologies described in [Topologies].  The =
scenarios are described in the following sub-clauses."
I think you have only three and not four scenarios

5. In 4.2.1.2 in the discussion section
 " it does not matter which if either tuple" I think it should be of =
instead of "if"

6. In 4.3.1.2 last sentence " A TSTR message MAY contain requests to =
multiple media senders, using one FCI entry per target media sender."

Should be FIR and not TSTR

7. In 4.3.3.1 "Seq. nr (8 bits): The sequence number value from the =
TSTN" Should be TSTR

8. In 4.3.4.2 "Note: There are possible overlaps between the VBCM sub-
          messages and CCM/AVPF feedback messages, such FIR."=20
Should be "such as FIR"=20

9. In 4.3.4.5 " Note: There has been some discussion whether the payload =
type field in this message is needed." I suggest changing to "the RTP =
payload type" since there are two definition to payload type in this =
section.

Also in the same note you have twice "TSTS" instead of "TSTR"




Regards
Roni

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



From avt-bounces@ietf.org Fri Jul 06 19:46:20 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6xVB-0002YG-8i; Fri, 06 Jul 2007 19:46:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6xV9-0002Y8-C3
	for avt@ietf.org; Fri, 06 Jul 2007 19:46:15 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6xV2-0005Cd-S8
	for avt@ietf.org; Fri, 06 Jul 2007 19:46:15 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-5.cisco.com with ESMTP; 06 Jul 2007 16:46:06 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAN9wjkarR7O6h2dsb2JhbACPNwEBCQ4s
X-IronPort-AV: i="4.16,510,1175497200"; 
	d="scan'208"; a="165915537:sNHT35956152"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l66Nk6np003253; 
	Fri, 6 Jul 2007 16:46:06 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l66Nk5mo018811;
	Fri, 6 Jul 2007 23:46:06 GMT
Received: from xmb-sjc-222.amer.cisco.com ([128.107.191.106]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 6 Jul 2007 16:46:05 -0700
Received: from klantz-wxp.cisco.com ([10.32.139.133]) by
	xmb-sjc-222.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 6 Jul 2007 16:46:05 -0700
Message-Id: <6.2.3.4.2.20070706160335.03e206b0@xmb-sjc-222.amer.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4
Date: Fri, 06 Jul 2007 16:45:42 -0700
To: magnus.westerlund@ericsson.com, stewe@stewe.org
From: Keith Lantz <klantz@cisco.com>
Subject: Re: [AVT] I-D Action:draft-ietf-avt-topologies-05.txt 
In-Reply-To: <E1I6pkw-0000Gy-3P@stiedprstage1.ietf.org>
References: <E1I6pkw-0000Gy-3P@stiedprstage1.ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 06 Jul 2007 23:46:05.0143 (UTC)
	FILETIME=[D1522E70:01C7C027]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=8008; t=1183765566;
	x=1184629566; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=klantz@cisco.com;
	z=From:=20Keith=20Lantz=20<klantz@cisco.com>
	|Subject:=20Re=3A=20[AVT]=20I-D=20Action=3Adraft-ietf-avt-topologies-05.t
	xt=20 |Sender:=20;
	bh=/d6ZN8r3CyMZzPwJpkQp2SoHR65O/rF4U5teiyIFhs0=;
	b=xy1njvu98X2YBXyzAfV7uD/7xizIhBEKj/kIG0v32czDPK79iKS0xdv3QumXfs9tdpMuYkm/
	dQZ9pE1SfFJyIPTzkvIpKWzHkg3lbMEQDZjWH6vNX4Rz4zJHH21S8w/X;
Authentication-Results: sj-dkim-2; header.From=klantz@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: df9edf1223802dd4cf213867a3af6121
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

As with draft-ietf-avt-avpf-ccm, my compliments on having 
accommodated everyone's comments on previous drafts -- including 
addressing the various concerns about which topologies were more "common".

Some remaining/additional nits, though:

- Abstract: "discucsses" --> "discusses"

         "RTP based" --> "RTP-based"

- Section 1, first paragraph: "Messages [CCM], a considerable 
confusion was noticed in the community, with respect to" -->
         "Messages [CCM] considerable confusion was noticed in the 
community with respect to"

         2nd paragraph: Remove the comma from "was developed, the 
main emphasis".

- Section 3: First, I don't quite understand what you're trying to 
say with "and no direct RTP or RTCP SSRC related information is 
forwarded to the other participants". What do you mean by "direct"? 
What do you mean by "RTCP SSRC related information"?

         Also, the cross-reference to Section 3.7 should now be to Section 3.8.

- Section 3.3: Remove the commas following "(to bridge different 
domains)" and "Of the transport translators".

         "non-RTP based media transport, one crucial factor consists in"
         --> "non-RTP-based media transport one crucial factor is"

         "for example when Transport translators just need to adjust 
IP addresses -- and"
         --> "for example, when Transport translators just need to 
adjust IP addresses -- or"

         p. 8: "multicast capable" --> "multicast-capable"

         Remove comma following "requests a bandwidth reduction".

- Section 3.4, p. 9, bottom: "generate sender report" --> "generate 
sender reports"

         p. 10, first sentence: Replace the semi-colon with a colon.

         2nd paragraph: "simplesr to implement and avoid" --> 
"simpler to implement and avoids"

- Section 3.5: "bit-rate, encoding, or resolution, however it" --> 
"bit-rate, encoding or resolution. However, it"

         bottom of p. 11: "at any given time, often"
         --> "at any given time -- often"

         p. 12: "two aspects. First it" --> "two features. First, it"
                 "The second is" --> "Second, the MCU needs"
                 "one implements" --> "one implement"

- Section 3.6, enumerated list: Lower-case the leading "A" and "The".

         following paragraph: Remove the comma following "different 
SSRC", and "is negotiated individually" --> "being negotiated independently".

         penultimate paragraph, on p. 13: "contributing sources, for 
example a" --> "contributing sources -- for example, a"

- Section 3.7, first paragraph: Lots of glitches here. Replace in its 
entirety with:

         "It is theoretically possible to construct an MCU that is a 
mixer in one direction and a translator in another. The main reason 
to consider this would be to allow topologies similar to Figure 5, 
where the mixer does not need to mix in the direction from B or D 
towards the multicast domains with A and C. Instead, the media 
streams from B and D are forwarded without changes. Avoiding this 
mixing would save media processing resources that perform the mixing 
in cases where it isn't needed. However, there would still be a need 
to mix B's stream towards D. Only in the direction B -> multicast 
domain or D -> multicast domain would it be possible to work as a 
translator. In all other directions it would function as a mixer."

         next paragraph: "Thus any" --> "Thus, any"

         next paragraph: "topologny" --> "topology"

- Section 3.8: Another bunch of small glitches. Replace in its entirety with:

         "Topologies can be combined and linked to each other using 
mixers or translators. However, care must be taken in handling the 
SSRC/CSRC space. A mixer will not forward RTCP from sources in other 
domains, but will instead generate its own RTCP packets for each 
domain it mixes into, including the necessary SDES information for 
both the CSRCs and the SSRCs. Thus, in a mixed domain the only SSRCs 
seen will be the ones present in the domain, while there can be CSRCs 
from all the domains connected together with a combination of mixers 
and translators. The combined SSRC and CSRC space is common over any 
translator or mixer. This is important to facilitate loop detection 
-- something that is likely to be even more important in combined 
topologies due to the mixed behavior between the domains. Any hybrid, 
like the Topo-Video-switch-MCU or Topo-Asymmetric, requires 
considerable thought on how RTCP is dealt with."

- Section 4.1, heading: "Proporties" --> "Properties"

- Section 4.1.1, 2nd paragraph: Insert comma after "IP-multicast-based".

         3rd paragraph: Insert comma after "Otherwise".
                 "Receiver Reports" --> "Receiver Reports"

- Section 4.1.2: "RTCP terminating" --> "RTCP-terminating"

- Section 4.1.4: "in that not even a minimal acceptable media quality 
is accomplished"
         --> "in a situation where even a minimal acceptable media 
quality cannot be accomplished"

- Section 4.1.5: "The MCUs described in Section 3.5" --> "The MCU 
described in Section 3.5"

- Section 5, p. 19: "wherein N is the total of number of SSRCs part 
of the joint SSRC space over all domains, and"
         --> "where N is the total number of SSRCs used over all domains and"


Regards, Keith

At 08:30 AM 7/6/2007, 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           : RTP Topologies
>         Author(s)       : M. Westerlund, S. Wenger
>         Filename        : draft-ietf-avt-topologies-05.txt
>         Pages           : 21
>         Date            : 2007-07-06
> 
>
>This document discucsses multi-endpoint topologies used in RTP
>based environments.  In particular, centralized topologies commonly
>employed in the video conferencing industry are mapped to the RTP
>terminology.
> 
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-avt-topologies-05.txt
> 
>
>To remove yourself from the I-D Announcement list, send a message to
>i-d-announce-request@ietf.org with the word unsubscribe in the body of
>the message.
>You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
>to change your subscription settings.
> 
>
> 
>
>Internet-Drafts are also available by anonymous FTP. Login with the
>username "anonymous" and a password of your e-mail address. After
>logging in, type "cd internet-drafts" and then
>         "get draft-ietf-avt-topologies-05.txt".
> 
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
>
> 
>
>Internet-Drafts can also be obtained by e-mail.
> 
>
>Send a message to:
>         mailserv@ietf.org.
>In the body type:
>         "FILE /internet-drafts/draft-ietf-avt-topologies-05.txt".
> 
>
>NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
> 
>
> 
>
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
> 
>
>
>
>ENCODING mime
>FILE /internet-drafts/draft-ietf-avt-topologies-05.txt
> 
>
>

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



From avt-bounces@ietf.org Fri Jul 06 23:51:35 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I71KS-0003ix-BZ; Fri, 06 Jul 2007 23:51:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I71KP-0003Z8-Tn
	for avt@ietf.org; Fri, 06 Jul 2007 23:51:25 -0400
Received: from mgw4.sony.co.jp ([137.153.0.46])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I71KK-0005bk-Sa
	for avt@ietf.org; Fri, 06 Jul 2007 23:51:25 -0400
Received: from mail5.sony.co.jp ([43.0.1.204])
Received: from mail5.sony.co.jp (localhost [127.0.0.1])
	by mail5.sony.co.jp (R8/Sony) with ESMTP id l673pHBs010695
	for <avt@ietf.org>; Sat, 7 Jul 2007 12:51:17 +0900 (JST)
Received: from jptkyxim01.jp.sony.com (jptkyxim01.jp.sony.com [43.15.17.87])
	by mail5.sony.co.jp (R8/Sony) with ESMTP id l673pHbd010690
	for <avt@ietf.org>; Sat, 7 Jul 2007 12:51:17 +0900 (JST)
Received: from jptkyxwa06.jp.sony.com ([43.15.31.6]) by jptkyxim01.jp.sony.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Sat, 7 Jul 2007 12:51:17 +0900
Received: from avhta.av.crl.sony.co.jp ([43.22.182.119]) by
	jptkyxwa06.jp.sony.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Sat, 7 Jul 2007 12:51:16 +0900
Message-Id: <5.1.1.9.2.20070707124752.00d13210@pop.jp.sony.com>
X-Sender: jp\jp05992@pop.jp.sony.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1-Jr4
Date: Sat, 07 Jul 2007 12:51:06 +0900
To: avt@ietf.org
From: Mitsuyuki Hatanaka <actech@jp.sony.com>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-atrac-family-09.txt 
In-Reply-To: <E1I6sKc-0002uK-2R@stiedprstage1.ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Jul 2007 03:51:16.0768 (UTC)
	FILETIME=[12220200:01C7C04A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Dear AVT member,

We have submitted our revised internet draft as "draft-ietf-avt-rtp-atracx-family-09.txt".
You will be able to get it from the on-line Internet-Drafts directories.

In this draft we modified the draft based on the issues which Mr.Perkins 
pointed out in 17 June.
(refer to: http://www1.ietf.org/mail-archive/web/avt/current/msg08465.html)

In addition, we corrected some typos regarding on figure number's mismatch.

The revised points are:
(1) added the descriptions which refer to each figure explicitly for figure 4, 5, 6.
(2) modified the descriptions about "Padding", "Extension" and "Marker" in RTP 
    header fields.
    We consider these parameters are should be defined in RTP profile layer which 
    uses this payload format.
(3) corrected some typos of figure number's mismatch.
(4) changed the Subtype name for each codec of ATRAC family in section 7.1, 7.2, 7.3.
(5) reconsidered about referenced documents in section 10.
(6) checked the editorial issues by using idnits tool and corrected.

Best regards,
Mitsuyuki Hatanaka

>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 Adaptive TRansform Acoustic Coding (ATRAC) 
>Family
>	Author(s)	: J. Matsumoto, M. Hatanaka
>	Filename	: draft-ietf-avt-rtp-atrac-family-09.txt
>	Pages		: 29
>	Date		: 2007-7-6
>	
>This document describes an RTP payload format for efficient and
>   flexible transporting of audio data encoded with the Adaptive
>   TRansform Audio Coding (ATRAC) family of codecs.  Recent enhancements
>   to the ATRAC family of codecs support high quality audio coding with
>   multiple channels.  The RTP payload format as presented in this
>   document also includes support for data fragmentation, elementary
>   redundancy measures, and a variation on scalable streaming.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-atrac-family-09.txt
>


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



From avt-bounces@ietf.org Sat Jul 07 18:25:41 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7IiD-00064Q-FV; Sat, 07 Jul 2007 18:25:10 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7IiC-000609-E1
	for avt@ietf.org; Sat, 07 Jul 2007 18:25:08 -0400
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7Ihx-0004t4-3L
	for avt@ietf.org; Sat, 07 Jul 2007 18:25:08 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Sat, 7 Jul 2007 18:24:20 -0400
To: "Even, Roni" <roni.even@polycom.co.il>
Subject: Re: [AVT] Review draft-ietf-avt-avpf-ccm-07
References: <144ED8561CE90C41A3E5908EDECE315C04B8F936@IsrExch01.israel.polycom.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Sat, 07 Jul 2007 18:24:19 -0400
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C04B8F936@IsrExch01.israel.polycom.com>
	(Roni Even's message of "Sat, 7 Jul 2007 00:32:47 +0300")
Message-ID: <ybud4z397jg.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 07 Jul 2007 22:24:20.0686 (UTC)
	FILETIME=[90732EE0:01C7C0E5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: stewe@stewe.org, Magnus Westerlund <magnus.westerlund@ericsson.com>,
	bo.burman@ericsson.com, avt@ietf.org, avt-chairs@tools.ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

"Even, Roni" <roni.even@polycom.co.il> writes:
>5. in section 7.1 " MaxPacketRateValue = 1*15DIGIT" what are the units for
>   this parameter. I think that based on the example it is in 1000's of
>   bits per second but please clarify. 
>Fix the value in example 3 based on the units, currently it say 120 and I
>assumed 120*1000 bits/s 

I'd assume that's in packets-per-second, but it should be spelled out.

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


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



From avt-bounces@ietf.org Sun Jul 08 01:38:42 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7PT6-0003Em-6y; Sun, 08 Jul 2007 01:38:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7PT4-0003Eh-B7
	for avt@ietf.org; Sun, 08 Jul 2007 01:37:58 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7PSz-0006Rb-Uu
	for avt@ietf.org; Sun, 08 Jul 2007 01:37:58 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] Review draft-ietf-avt-avpf-ccm-07
Date: Sun, 8 Jul 2007 08:38:51 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04B8F973@IsrExch01.israel.polycom.com>
In-Reply-To: <ybud4z397jg.fsf@jesup.eng.wgate.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Review draft-ietf-avt-avpf-ccm-07
Thread-Index: AcfA5ZxVRiGdpbOrQEyFuSf6tna5HQAPFvWg
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Randell Jesup" <rjesup@wgate.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: stewe@stewe.org, Magnus Westerlund <magnus.westerlund@ericsson.com>,
	bo.burman@ericsson.com, avt@ietf.org, avt-chairs@tools.ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Randell,
Packet per second is not a precise number for video. It is also
dependent on MTU size and how the sender breaks a big frame to packets
smaller than MTU size.

Roni

> -----Original Message-----
> From: Randell Jesup [mailto:rjesup@wgate.com]
> Sent: Sunday, July 08, 2007 1:24 AM
> To: Even, Roni
> Cc: avt@ietf.org; Magnus Westerlund; bo.burman@ericsson.com;
> stewe@stewe.org; avt-chairs@tools.ietf.org
> Subject: Re: [AVT] Review draft-ietf-avt-avpf-ccm-07
>=20
> "Even, Roni" <roni.even@polycom.co.il> writes:
> >5. in section 7.1 " MaxPacketRateValue =3D 1*15DIGIT" what are the
units
> for
> >   this parameter. I think that based on the example it is in 1000's
of
> >   bits per second but please clarify.
> >Fix the value in example 3 based on the units, currently it say 120
and I
> >assumed 120*1000 bits/s
>=20
> I'd assume that's in packets-per-second, but it should be spelled out.
>=20
> --
> Randell Jesup, Worldgate (developers of the Ojo videophone), ex-Amiga
OS
> team
> rjesup@wgate.com
> "The fetters imposed on liberty at home have ever been forged out of
the
> weapons
> provided for defence against real, pretended, or imaginary dangers
from
> abroad."
> 		- James Madison, 4th US president (1751-1836)


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



From avt-bounces@ietf.org Sun Jul 08 03:48:46 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7RVY-0001Yr-1H; Sun, 08 Jul 2007 03:48:40 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7RVW-0001Ye-B1
	for avt@ietf.org; Sun, 08 Jul 2007 03:48:38 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7RVV-00080I-To
	for avt@ietf.org; Sun, 08 Jul 2007 03:48:38 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 8 Jul 2007 10:49:09 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04B8F9AF@IsrExch01.israel.polycom.com>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C04A70650@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: End of working group last call: draft-ietf-avt-avpf-ccm-07
Thread-Index: AcezIJhcq7jJrzUZSrayJm9ow4zxcAOEu8lg
From: "Even, Roni" <roni.even@polycom.co.il>
To: <avt@ietf.org>,
	"Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: bo.burman@ericsson.com, stewe@stewe.org, avt-chairs@tools.ietf.org
Subject: [AVT] End of working group last call: draft-ietf-avt-avpf-ccm-07
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi,
The working group last call has ended. It was reviewed and most of the =
comments are editorial.
Thanks to Keith Lantz for his review.

Since there were no technical issues, I suggest that after fixing the =
editorial changes it will go to publication. The authors should also =
fixed the nits listed in =
http://tools.ietf.org/wg/avt/draft-ietf-avt-avpf-ccm/

Thanks
Roni Even


> -----Original Message-----
> From: Even, Roni [mailto:roni.even@polycom.co.il]
> Sent: Wednesday, June 20, 2007 12:52 PM
> To: avt@ietf.org
> Cc: avt-chairs@tools.ietf.org
> Subject: Working group last call: draft-ietf-avt-avpf-ccm-07
>=20
>=20
> This is to announce a working group last call on the Codec Control
> Messages in the RTP Audio-Visual Profile with Feedback (AVPF).
>=20
> This is a second last call after the authors addressed comments in the
> list
>=20
> Please send any final comments to the mailing list by July 6th 2007.
>=20
> If no issues are raised, we will request the IESG consider this for
> publication as a Proposed Standard RFC.
>=20
> Thanks
> Roni Even - AVT co-chair
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Audio/Video Transport Working Group =
of
> the IETF.
>=20
> 	Title		: Codec Control Messages in the RTP Audio-Visual Profile
> with Feedback (AVPF)
> 	Author(s)	: S. Wenger, et al.
> 	Filename	: draft-ietf-avt-avpf-ccm-07.txt
> 	Pages		: 71
> 	Date		: 2007-6-1
>=20
> This document specifies a few extensions to the messages defined
>    in the Audio-Visual Profile with Feedback (AVPF).  They are
>    helpful primarily in conversational multimedia scenarios where
>    centralized multipoint functionalities are in use.  However some
>    are also usable in smaller multicast environments and point-to-
>    point calls.  The extensions discussed are messages related to the
>    ITU-T H.271 Video Back Channel, Full Intra Request, Temporary
>    Maximum Media Stream Bit Rate and Temporal Spatial Trade-off.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-avpf-ccm-07.txt


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



From avt-bounces@ietf.org Sun Jul 08 03:54:08 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7Ral-0001kg-Oi; Sun, 08 Jul 2007 03:54:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7Rak-0001dA-6c
	for avt@ietf.org; Sun, 08 Jul 2007 03:54:02 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7Rag-0003Z4-PH
	for avt@ietf.org; Sun, 08 Jul 2007 03:54:02 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 8 Jul 2007 10:55:16 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04B8F9B7@IsrExch01.israel.polycom.com>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C04A70653@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: end of working group last call on
	draft-ietf-avt-topologies-04.txt
Thread-Index: AcezIWIOnTVu3oN1T0iyh1yL9usKoAOE0ErA
From: "Even, Roni" <roni.even@polycom.co.il>
To: <avt@ietf.org>,
	"Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: bo.burman@ericsson.com, stewe@stewe.org, avt-chairs@tools.ietf.org
Subject: [AVT] end of working group last call on
	draft-ietf-avt-topologies-04.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi,
The working group last call has ended.
A new revision 05 was posted but there were more comments.

Thanks to Geoff Hunt and Keith Lantz for reviewing the document.

The comments are editorial so after addressing them I suggest sending =
the document for publication.

Regards
Roni Even

> -----Original Message-----
> From: Even, Roni [mailto:roni.even@polycom.co.il]
> Sent: Wednesday, June 20, 2007 12:57 PM
> To: avt@ietf.org
> Cc: avt-chairs@tools.ietf.org
> Subject: working group last call on draft-ietf-avt-topologies-04.txt
>=20
> This is to announce a working group last call on the RTP Topologies.
>=20
> Version 03 of the document went through last call and this one will be
> shorter
>=20
> Please send any final comments to the mailing list by June 29th 2007.
>=20
> If no issues are raised, we will request the IESG consider this for
> publication as an Informational RFC.
>=20
> Thanks
> Roni Even - AVT co-chair
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Audio/Video Transport Working Group =
of
> the IETF.
>=20
> 	Title		: RTP Topologies
> 	Author(s)	: M. Westerlund, S. Wenger
> 	Filename	: 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.
>=20
> 	Title		: RTP Topologies
> 	Author(s)	: M. Westerlund, S. Wenger
> 	Filename	: draft-ietf-avt-topologies-04.txt
> 	Pages		: 20
> 	Date		: 2007-2-23
>=20
> This document discucsses multi-endpoint topologies used in RTP
>    based environments.  In particular, centralized topologies commonly
>    employed in the video conferencing industry are mapped to the RTP
>    terminology.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-topologies-04.txt
> 	Pages		: 20
> 	Date		: 2007-2-23
>=20
> This document discucsses multi-endpoint topologies used in RTP
>    based environments.  In particular, centralized topologies commonly
>    employed in the video conferencing industry are mapped to the RTP
>    terminology.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-topologies-04.txt

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



From avt-bounces@ietf.org Sun Jul 08 09:35:45 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7WvK-0003gn-1d; Sun, 08 Jul 2007 09:35:38 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7WvI-0003gf-VI
	for avt@ietf.org; Sun, 08 Jul 2007 09:35:36 -0400
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7Wus-0003cU-Ks
	for avt@ietf.org; Sun, 08 Jul 2007 09:35:36 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Sun, 8 Jul 2007 09:34:38 -0400
To: "Even, Roni" <roni.even@polycom.co.il>
Subject: Re: [AVT] Review draft-ietf-avt-avpf-ccm-07
References: <144ED8561CE90C41A3E5908EDECE315C04B8F973@IsrExch01.israel.polycom.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Sun, 08 Jul 2007 09:34:36 -0400
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C04B8F973@IsrExch01.israel.polycom.com>
	(Roni Even's message of "Sun, 8 Jul 2007 08:38:51 +0300")
Message-ID: <ybuhcof6mtv.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 08 Jul 2007 13:34:38.0124 (UTC)
	FILETIME=[BAFAD6C0:01C7C164]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: stewe@stewe.org, Magnus Westerlund <magnus.westerlund@ericsson.com>,
	bo.burman@ericsson.com, avt@ietf.org, avt-chairs@tools.ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

"Even, Roni" <roni.even@polycom.co.il> writes:
>Packet per second is not a precise number for video. It is also
>dependent on MTU size and how the sender breaks a big frame to packets
>smaller than MTU size.

Sure, actual packet rate is dependant on a lot of things.  But (correct me
if I'm wrong) SMAXPR is how you signal a maximum packet rate for use in the
TMMBR algorithm above, and so should be in some variation of packets per
unit time, and my assumption is that we don't need any higher resolution
than integer packets per second.

I don't understand how it could be in bits per second...

>> "Even, Roni" <roni.even@polycom.co.il> writes:
>> >5. in section 7.1 " MaxPacketRateValue = 1*15DIGIT" what are the units
>> >   for this parameter. I think that based on the example it is in
>> >   1000's of bits per second but please clarify.
>> >Fix the value in example 3 based on the units, currently it say 120 and
>> >I assumed 120*1000 bits/s
>> 
>> I'd assume that's in packets-per-second, but it should be spelled out.

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


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



From avt-bounces@ietf.org Sun Jul 08 10:01:45 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7XKT-0008Ln-Kc; Sun, 08 Jul 2007 10:01:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7XKS-0008FH-2a
	for avt@ietf.org; Sun, 08 Jul 2007 10:01:36 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7XKO-0004Fk-MX
	for avt@ietf.org; Sun, 08 Jul 2007 10:01:36 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] Review draft-ietf-avt-avpf-ccm-07
Date: Sun, 8 Jul 2007 17:03:46 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04B8FA7E@IsrExch01.israel.polycom.com>
In-Reply-To: <ybuhcof6mtv.fsf@jesup.eng.wgate.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Review draft-ietf-avt-avpf-ccm-07
Thread-Index: AcfBZPepmBwe57RAS5G7lThfVaDuLgAAqWHA
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Randell Jesup" <rjesup@wgate.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: stewe@stewe.org, Magnus Westerlund <magnus.westerlund@ericsson.com>,
	bo.burman@ericsson.com, avt@ietf.org, avt-chairs@tools.ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Randell,
Thanks, you are right about the parameter.=20

I assume that the default of infinity to this parameter make sense. This
parameter is not important for a unicast point to point call where the
MTU is fixed but for multiple receivers that may have different path MTU
sizes and different overhead.

Roni



> -----Original Message-----
> From: Randell Jesup [mailto:rjesup@wgate.com]
> Sent: Sunday, July 08, 2007 4:35 PM
> To: Even, Roni
> Cc: avt@ietf.org; Magnus Westerlund; bo.burman@ericsson.com;
> stewe@stewe.org; avt-chairs@tools.ietf.org
> Subject: Re: [AVT] Review draft-ietf-avt-avpf-ccm-07
>=20
> "Even, Roni" <roni.even@polycom.co.il> writes:
> >Packet per second is not a precise number for video. It is also
> >dependent on MTU size and how the sender breaks a big frame to
packets
> >smaller than MTU size.
>=20
> Sure, actual packet rate is dependant on a lot of things.  But
(correct me
> if I'm wrong) SMAXPR is how you signal a maximum packet rate for use
in
> the
> TMMBR algorithm above, and so should be in some variation of packets
per
> unit time, and my assumption is that we don't need any higher
resolution
> than integer packets per second.
>=20
> I don't understand how it could be in bits per second...
>=20
> >> "Even, Roni" <roni.even@polycom.co.il> writes:
> >> >5. in section 7.1 " MaxPacketRateValue =3D 1*15DIGIT" what are the
units
> >> >   for this parameter. I think that based on the example it is in
> >> >   1000's of bits per second but please clarify.
> >> >Fix the value in example 3 based on the units, currently it say
120
> and
> >> >I assumed 120*1000 bits/s
> >>
> >> I'd assume that's in packets-per-second, but it should be spelled
out.
>=20
> --
> Randell Jesup, Worldgate (developers of the Ojo videophone), ex-Amiga
OS
> team
> rjesup@wgate.com
> "The fetters imposed on liberty at home have ever been forged out of
the
> weapons
> provided for defence against real, pretended, or imaginary dangers
from
> abroad."
> 		- James Madison, 4th US president (1751-1836)


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



From avt-bounces@ietf.org Sun Jul 08 11:50:29 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7Z1Z-0007US-T2; Sun, 08 Jul 2007 11:50:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7Z1Y-0007R9-GZ
	for avt@ietf.org; Sun, 08 Jul 2007 11:50:12 -0400
Received: from [2001:200:601:12:230:48ff:fe22:3a84] (helo=mandala.kddilabs.jp)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7Z1X-0007Vc-7K
	for avt@ietf.org; Sun, 08 Jul 2007 11:50:12 -0400
Received: from localhost (localhost [127.0.0.1])
	by mandala.kddilabs.jp (Postfix) with ESMTP id A3F71ECAE1
	for <avt@ietf.org>; Mon,  9 Jul 2007 00:50:08 +0900 (JST)
Received: from mail.cn.kddilabs.jp (yellow.lan.kddilabs.jp
	[2001:200:601:1a00::10])
	by mandala.kddilabs.jp (Postfix) with ESMTP id 25A10ECA53
	for <avt@ietf.org>; Mon,  9 Jul 2007 00:50:07 +0900 (JST)
Received: from R1 (c018.vpn.kddilabs.jp [172.19.87.18])
	by mail.cn.kddilabs.jp (Postfix) with ESMTP id 1B94F1E0002
	for <avt@ietf.org>; Mon,  9 Jul 2007 00:50:07 +0900 (JST)
From: "Hideaki YAMADA" <hd-yamada@kddilabs.jp>
To: "'AVT WG'" <avt@ietf.org>
Date: Mon, 9 Jul 2007 00:49:42 +0900
Organization: R&D
Message-ID: <002701c7c177$9d6b6a80$f00d10ac@R1>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
Thread-Index: AcfBd5Zsov2byYrfQd22bIo37Pc6IA==
X-Virus-Scanned: by amavisd-new
X-Spam-Score: -1.8 (-)
X-Scan-Signature: d008c19e97860b8641c1851f84665a75
Subject: [AVT] Comments on the Global reporting mode of the RTCP-HR
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: hd-yamada@kddilabs.jp
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Dear Sirs,

As you know, most multimedia speech sessions over IP-based networks use =
RTP/RTCP. However, the feedback mechanism provided on an end-to-end =
network basis is insufficient for controlling the service sessions in =
FMC (Fixed and Mobile Convergence) networks since the fluctuant quality =
of end-to-end networks depends on that of both IP-based mobile and fixed =
networks, and it is difficult to separate the quality of individual =
networks from the observation of overall quality of end-to-end networks. =

I also believe that the RTCP-HR reports provide useful monitoring =
information and a diagnosis of VoIP performance between the RTP end =
systems.

I think that the measurement modes involving translators described in =
this RTCP-HR draft. The translators are able to provide informative =
reports of packet loss, round trip delay, and packet delay variation and =
so on.
Considering the several disadvantages indicated in the draft, I would =
like to provide following scheme to ease the disadvantages.=20

As you pointed out, RTCP traffic in every link is proportional to the =
number of translators in the connection in the Global reporting mode as =
shown in Figure 1.
Considering the situation in Figure 1, I think that the multiplexing =
scheme of RTCP report blocks by the translators is useful to reduce the =
RTCP traffic as shown in Figure 2.=20
The RTCP traffic might be the same that of the Local reporting mode as =
shown Figure 3.
The multiplexing scheme is a realistic approach by choosing a proper =
sending interval of the RTCP reports and the number of metrics blocks =
measured in the translators.


A.R/A.T------>J.1R/J.2T---->K.1R/K.2T---->L.1R/L.2T------>Z.R/Z.T

    |     RTP     |             |             |              |
    |<------------|-------------|-------------|------------->|
    |             |             |             |              |
    | RTCP(A.R)   | RTCP(A.R)   | RTCP(A.R)   | RTCP(A.R)    |
    |- - - - - - >|- - - - - - >|- - - - - - >|- - - - - - > |
    |             | RTCP(J.1R)  | RTCP(J.1R)  | RTCP(J.1R)   |
    |             |- - - - - - >|- - - - - - >|- - - - - - > |
    |             | RTCP(J.2R)  | RTCP(J.2R)  | RTCP(J.2R)   |
    |             |- - - - - - >|- - - - - - >|- - - - - - > |
    |             |             | RTCP(K.1R)  | RTCP(K.1R)   |
    |             |             |- - - - - - >|- - - - - - > |
    |             |             | RTCP(K.2R)  | RTCP(K.2R)   |
    |             |             |- - - - - - >|- - - - - - > |
    |             |             |             | RTCP(L.2R)   |
    |             |             |             |- - - - - - > |
    |             |             |             | RTCP(L.2R)   |
    |             |             |             |- - - - - - > |
    |             |             |             |              |

A.T/A.R<------J.1T/J.2R<----K.1T/K.2R<----L.1T/L.2R<------Z.T/Z.R

    |     RTP     |             |             |              |
    |<------------|-------------|-------------|------------->|
    |             |             |             |              |
    | RTCP(Z.R)   | RTCP(Z.R)   | RTCP(Z.R)   | RTCP(Z.R)    |
    |< - - - - - -|< - - - - - -|< - - - - - -|< - - - - - - |
    | RTCP(L.1R)  | RTCP(L.1R)  | RTCP(L.1R)  |              |
    |< - - - - - -|< - - - - - -|< - - - - - -|              |
    | RTCP(L.2R)  | RTCP(L.2R)  | RTCP(L.2R)  |              |
    |< - - - - - -|< - - - - - -|< - - - - - -|              |
    | RTCP(K.1R)  | RTCP(K.1R)  |             |              |
    |< - - - - - -|< - - - - - -|             |              |
    | RTCP(K.2R)  | RTCP(K.2R)  |             |              |
    |< - - - - - -|< - - - - - -|             |              |
    | RTCP(J.1R)  |             |             |              |
    |< - - - - - -|             |             |              |
    | RTCP(J.2R)  |             |             |              |
    |< - - - - - -|             |             |              |
    |             |             |             |              |
                 =20
               Figure 1 The Global reporting mode



A.R/A.T------>J.1R/J.2T---->K.1R/K.2T---->L.1R/L.2T------>Z.R/Z.T

    |     RTP     |             |             |              |
    |<------------|-------------|-------------|------------->|
    |             |             |             |              |
    | RTCP(A.R)   | RTCP(A.R)   | RTCP(A.R)   | RTCP(A.R)    |
    |- - - - - - >|- - - - - - >|- - - - - - >|- - - - - - > |
    |             |             |             | RTCP(J.1R,   |
    |             |             | RTCP(J.1R,  |      K.1R,   |
    |             | RTCP(J.1R)  |      K.1R)  |      L.1R)   |
    |             |- - - - - - >|- - - - - - >|- - - - - - > |
    |             |             |             | RTCP(J.2R,   |
    |             |             | RTCP(J.2R,  |      K.2R,   |
    |             | RTCP(J.2R)  |      K.2R)  |      L.2R)   |
    |             |- - - - - - >|- - - - - - >|- - - - - - > |

A.T/A.R<------J.1T/J.2R<----K.1T/K.2R<----L.1T/L.2R<------Z.T/Z.R

    |     RTP     |             |             |              |
    |<------------|-------------|-------------|------------->|
    |             |             |             |              |
    | RTCP(Z.R)   | RTCP(Z.R)   | RTCP(Z.R)   | RTCP(Z.R)    |
    |< - - - - - -|< - - - - - -|< - - - - - -|< - - - - - - |
    | RTCP(L.1R,  |             |             |              |
    |      K.1R,  | RTCP(L.1R,  |             |              |
    |      J.1R)  |      K.1R)  | RTCP(L.1R)  |              |
    |< - - - - - -|< - - - - - -|< - - - - - -|              |
    | RTCP(L.2R,  |             |             |              |
    |      K.2R,  | RTCP(L.2R,  |             |              |
    |      J.2R)  |      K.2R)  | RTCP(L.2R)  |              |
    |< - - - - - -|< - - - - - -|< - - - - - -|              |
    |             |             |             |              |

Figure 2 Proposed multiplexing scheme of the Global reporting mode



A.R/A.T------>J.1R/J.2T---->K.1R/K.2T---->L.1R/L.2T------>Z.R/Z.T

    |     RTP     |             |             |              |
    |<------------|-------------|-------------|------------->|
    |             |             |             |              |
    | RTCP(A.R)   | RTCP(A.R)   | RTCP(A.R)   | RTCP(A.R)    |
    |- - - - - - >|- - - - - - >|- - - - - - >|- - - - - - > |
    |             | RTCP(J.1R)  | RTCP(K.1R)  | RTCP(L.1R)   |
    |             |- - - - - - >|- - - - - - >|- - - - - - > |
    |             | RTCP(J.2R)  | RTCP(K.2R)  | RTCP(L.2R)   |
    |             |- - - - - - >|- - - - - - >|- - - - - - > |
    |             |             |             |              |
    |             |             |             |              |

A.T/A.R<------J.1T/J.2R<----K.1T/K.2R<----L.1T/L.2R<------Z.T/Z.R

    |     RTP     |             |             |              |
    |<------------|-------------|-------------|------------->|
    |             |             |             |              |
    | RTCP(Z.R)   | RTCP(Z.R)   | RTCP(Z.R)   | RTCP(Z.R)    |
    |< - - - - - -|< - - - - - -|< - - - - - -|< - - - - - - |
    | RTCP(J.1R)  | RTCP(K.1R)  | RTCP(L.1R)  |              |
    |< - - - - - -|< - - - - - -|< - - - - - -|              |
    | RTCP(J.2R)  | RTCP(K.2R)  | RTCP(L.2R)  |              |
    |< - - - - - -|< - - - - - -|< - - - - - -|              |
    |             |             |             |              |

                  Figure 3 Local reporting mode



Figure 4 depicts an example of the RTCP reports configuration of the =
proposed multiplexing scheme.

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                             Header                            |
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=
=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
|                          Sender info                          |
|                                                               |
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=
=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
|                       Report block of SSRC 1                  |
|                                                               |
|                                                               |
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=
=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
|                            Chunk 1                            |
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=
=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
|                          =E3=80=80HR header                          |
|                                                               |
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=
=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
|                      Report blocks (Chunk 1)                  |
|                                                               |
|                                                               |
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=
=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
|                                                               |
|                             =E2=80=A6                                 =
|
|                                                               |
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=
=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
|                            Chunk N                            |
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=
=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
|                          =E3=80=80HR header                          |
|                                                               |
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=
=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
|                      Report blocks (Chunk N)                  |
|                                                               |
|                                                               |
+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=
=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+=3D+
 Figure 4 An example of the multiplexed RTCP reports =
packet=EF=BC=88SR=EF=BC=89

The report blocks are the same as for the standard RTCP XR reports.
The "last SR (LSR)" and "delay since last are used for calculating the=20
RTT with the local time of sending RTCP report and receiving RTCP=20
reports.

I am happy if I could have your comments.
Best regards,
Yama

***********************************
Hideaki YAMADA,
KDDI R&D Labs. Inc.
Tel/Fax : +81-49-278-7356/7510
hd-yamada@kddilabs.jp
***********************************




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



From avt-bounces@ietf.org Sun Jul 08 17:16:12 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7e6t-0000ve-8i; Sun, 08 Jul 2007 17:16:03 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7e6o-0000om-A9; Sun, 08 Jul 2007 17:15:58 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I7e6i-0006Bs-6F; Sun, 08 Jul 2007 17:15:58 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 0F9AA2AC77;
	Sun,  8 Jul 2007 21:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I7e5t-0006wp-Q4; Sun, 08 Jul 2007 17:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I7e5t-0006wp-Q4@stiedprstage1.ietf.org>
Date: Sun, 08 Jul 2007 17:15:01 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-avpf-ccm-08.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF)
	Author(s)	: S. Wenger, et al.
	Filename	: draft-ietf-avt-avpf-ccm-08.txt
	Pages		: 68
	Date		: 2007-7-8
	
This document specifies a few extensions to the messages defined in
   the Audio-Visual Profile with Feedback (AVPF).  They are helpful
   primarily in conversational multimedia scenarios where centralized
   multipoint functionalities are in use.  However, some are also
   usable in smaller multicast environments and point-to-point calls.
   The extensions discussed are messages related to the ITU-T H.271
   Video Back Channel, Full Intra Request, Temporary Maximum Media
   Stream Bit Rate and Temporal Spatial Trade-off.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-avpf-ccm-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-avpf-ccm-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-avpf-ccm-08.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-avpf-ccm-08.txt

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

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


--OtherAccess--

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

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

--NextPart--




From avt-bounces@ietf.org Mon Jul 09 03:17:48 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7nV7-0007Ut-Si; Mon, 09 Jul 2007 03:17:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7nV6-0007PU-AX
	for avt@ietf.org; Mon, 09 Jul 2007 03:17:40 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7nV1-00060f-UF
	for avt@ietf.org; Mon, 09 Jul 2007 03:17:40 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 9 Jul 2007 10:18:34 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04B8FB41@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Draft agenda for AVT session in Chicago - Update
Thread-Index: AcfB+VxxSNq22k0XRLmFasE1Mxdrlg==
From: "Even, Roni" <roni.even@polycom.co.il>
To: <avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: Colin Perkins <csp@csperkins.org>, tom.taylor@rogers.com
Subject: [AVT] Draft agenda for AVT session in Chicago - Update
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi,
I updated the draft agenda for the Chicago meeting.=20

Roni


Monday, 23 July 2007 at 15:20-17:20 (State Ballroom)
----------------------------------------------------
15:20   Introduction and Status Update                      (Chairs, 15)

15:35   DTLS Extension to Establish Keys for SRTP          (McGrew , 15)
        draft-ietf-avt-dtls-srtp-00

15:50   High Resolution VoIP Metrics                         (Clark, 10)
        draft-ietf-avt-rtcphr-01

16:00   Video Metrics Report Blocks                          (Clark, 10)
        draft-ietf-avt-rtcpxr-video-01

16:10   Report Block for IPTV Metrics                       (Kaynam, 10)
        draft-venna-avt-rtcpxr-iptv-01=20

16:20   H.264 Payload optional parameters              (Kristensen , 15)
        draf-ietf-avt-rtp-h264-params-00

16:35   Non-Compound RTCP Packets                        (Johansson, 25)
        draft-johansson-avt-rtcp-avpf-non-compound-02

17:00   End



Thursday, 26 July 2007 at 15:10-16:10 (Red Lacquar)
---------------------------------------------------
15:10   RTP keepalive                                       (Marjou, 10)
        draft-ietf-avt-app-rtp-keepalive-00

15:20   RTP Payload Format for SVC Video                   (Schierl, 15)
        draft-ietf-avt-rtp-svc-01

15:35   Using SEED Cipher Algorithm with SRTP              (Seokung, 10)
        draft-seokung-avt-seed-srtp-00

15:45   End


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



From avt-bounces@ietf.org Mon Jul 09 03:52:12 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7o2R-0005BP-UP; Mon, 09 Jul 2007 03:52:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7o2P-00059f-P3
	for avt@ietf.org; Mon, 09 Jul 2007 03:52:05 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7o2K-0006dL-Pm
	for avt@ietf.org; Mon, 09 Jul 2007 03:52:05 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	2C09520226 for <avt@ietf.org>; Mon,  9 Jul 2007 09:52:00 +0200 (CEST)
X-AuditID: c1b4fb3e-b0034bb0000007e1-47-4691e91fb57b
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	F233B20142 for <avt@ietf.org>; Mon,  9 Jul 2007 09:51:59 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Jul 2007 09:51:59 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Jul 2007 09:51:59 +0200
Message-ID: <4691E923.4000505@ericsson.com>
Date: Mon, 09 Jul 2007 09:52:03 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>
Subject: Re: [AVT] I-D Action:draft-ietf-avt-topologies-05.txt
References: <E1I6pkw-0000Gy-3P@stiedprstage1.ietf.org>
In-Reply-To: <E1I6pkw-0000Gy-3P@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Jul 2007 07:51:59.0533 (UTC)
	FILETIME=[07848DD0:01C7C1FE]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi,

Thanks to Keith for his review on the new version.

All other please take a look on the new section 3.7 that discusses 
non-symmetric mixer/translators. This was an result of comments from 
Geoff Hunt. I am going to address Keith's comments and submit updates 
when the submission opens again. So if you have any more comments please 
provide me with them before the meeting.

A diff from the previous version:
http://tools.ietf.org/wg/avt/draft-ietf-avt-topologies/draft-ietf-avt-topologies-05-from-04.diff.html

Cheers

Magnus


Internet-Drafts@ietf.org skrev:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Audio/Video Transport Working Group of the IETF.
> 
>                                                                                            
>         Title           : RTP Topologies
>         Author(s)       : M. Westerlund, S. Wenger
>         Filename        : draft-ietf-avt-topologies-05.txt
>         Pages           : 21
>         Date            : 2007-07-06
>                                                                                            
> This document discucsses multi-endpoint topologies used in RTP
> based environments.  In particular, centralized topologies commonly
> employed in the video conferencing industry are mapped to the RTP
> terminology.
>                                                                                            
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-topologies-05.txt
>                                                                                            
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of 
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>                                                                                            
>                                                                                            
> Internet-Drafts are also available by anonymous FTP. Login with the 
> username "anonymous" and a password of your e-mail address. After 
> logging in, type "cd internet-drafts" and then
>         "get draft-ietf-avt-topologies-05.txt".
>                                                                                            
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>                                                                                            
>                                                                                            
> Internet-Drafts can also be obtained by e-mail.
>                                                                                            
> Send a message to:
>         mailserv@ietf.org.
> In the body type:
>         "FILE /internet-drafts/draft-ietf-avt-topologies-05.txt".
>                                                                                            
> NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
>                                                                                            
>                                                                                            
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>                                                                                            
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt


-- 

Magnus Westerlund

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

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



From avt-bounces@ietf.org Mon Jul 09 04:50:41 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7owt-0007xi-MV; Mon, 09 Jul 2007 04:50:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7ows-0007vQ-Ol
	for avt@ietf.org; Mon, 09 Jul 2007 04:50:26 -0400
Received: from dmzraw3.extranet.thmulti.com ([141.11.234.71])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7ows-0000VZ-0y
	for avt@ietf.org; Mon, 09 Jul 2007 04:50:26 -0400
Received: from boulvss3.eu.thmulti.com (unknown [141.11.234.56])
	by dmzraw3.extranet.thmulti.com (Postfix) with ESMTP id 30AFC297B
	for <avt@ietf.org>; Mon,  9 Jul 2007 08:49:32 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
	by boulvss3.eu.thmulti.com (Postfix) with ESMTP id 6AAE51209
	for <avt@ietf.org>; Mon,  9 Jul 2007 08:54:37 +0000 (GMT)
Received: from boulvss3.eu.thmulti.com ([127.0.0.1])
	by localhost (boulvss3.eu.thmulti.com [127.0.0.1]) (amavisd-new,
	port 10024) with LMTP id 26345-03-52 for <avt@ietf.org>;
	Mon,  9 Jul 2007 08:54:28 +0000 (GMT)
Received: from boulsmailfe01.eu.thmulti.com (boulsmailfe01.eu.thmulti.com
	[141.11.192.237])
	by boulvss3.eu.thmulti.com (Postfix) with ESMTP id 8A357120B
	for <avt@ietf.org>; Mon,  9 Jul 2007 08:54:28 +0000 (GMT)
Received: from rennsmail05.eu.thmulti.com ([141.11.159.141]) by
	boulsmailfe01.eu.thmulti.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Jul 2007 10:49:23 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 9 Jul 2007 10:49:06 +0200
Message-ID: <7634542FB03DC747813D67560802AEEDB638F5@rennsmail05.eu.thmulti.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Scalable Video (JPEG-2000 & SVC) 
Thread-Index: Aceg+wQRjFDbAf1ATgia9RgBHhkw4Agn+Qbg
From: "Boudani Ali" <Ali.Boudani@thomson.net>
To: "IETF AVT WG" <avt@ietf.org>
X-OriginalArrivalTime: 09 Jul 2007 08:49:23.0673 (UTC)
	FILETIME=[0C629C90:01C7C206]
X-Virus-Scanned: amavisd-new at thomson.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ec7c6dab5a62df223002ae71b5179d41
Subject: [AVT] Scalable Video (JPEG-2000 & SVC) 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hello,
1- In the SVC draft that describes the RTP Payload Format for SVC Video,
each RTP packet stream can carry NAL units belonging to one or more
layers.=20
When multiple RTP packet streams are in use, they are session
multiplexed and form their own RTP session and therefore have their own
SSRC, PT, and Sequence numbering space. What about the timestamp (same
sampling instant)?=20
Now, for the JPEG2K Codestream when transmitting layers in different RTP
sessions, do we have the same timestamp for all these packets (because
of the same sampling instant) and what about the sequence number? The
multiple RTP packet streams in use are session multiplexed, do they have
their own Sequence numbering space?.

For example what would be the values for this JPEG2K Codestream?
+----------+----+----+----+----------+----+----+----+----------+----
|Tile 0 Hdr| L0 | L1 | L2 |Tile 1 Hdr| L0 | L1 | L2 |Tile 2 Hdr| ...
+----------+----+----+----+----------+----+----+----+----------+----
RTP session 1
+----------+----+         +----------+----+        +----------+----
|Tile 0 Hdr| L0 |         |Tile 1 Hdr| L0 |        |Tile 2 Hdr| L0
+----------+----+         +----------+----+        +----------+----
RTP session 2
                +----+                    +----+
                | L1 |                    | L1 |             ....
                +----+                    +----+
RTP session 3=20
                     +----+                    +----+
                     | L2 |                    | L2 |        ....
                     +----+                    +----+

2- What about using a fragment offset with SVC? The SVC draft has also
layers (like JPEG2K) but doesn't use any offset! In the other hand, the
JPEG2K draft, says that a fragment offset value MUST be set to the byte
offset of the current payload in relation to the very beginning of each
JPEG 2000 codestream (JPEG 2000 frame). Is the "MUST" is the best
keyword here. I may need it only if I am sending the different layers of
the same codestream over multiple sessions.=20

Thanks,
Ali
-----Original Message-----
From: Satoshi Futemma [mailto:satosi-f@sm.sony.co.jp]=20
Sent: lundi 28 mai 2007 09:37
To: Boudani Ali
Cc: IETF AVT WG; Colin Perkins; Andrew Leung; ITAKURA Eisaburo
Subject: Re: [AVT] Working group last call: JPEG-2000 payload format

Dear Ali,

Thank you for the comments.
Please see inline.

Boudani Ali wrote:
> Hello,
> I read the two drafts. Before going to the IESG, It will be better if
> the authors clarify some issues.
> Here are my comments:
>=20
> 1- How can we identify the packets belonging to the same Codestream
> (frame) (especially when using multiple RTP sessions). Don't you think
> that we need to add a frame_id identifier?.

RTP timestamp can be used for that purpose.

> 2- In section 4.1 of Draft-ietf-avt-rtp-jpeg2000-15.txt: you consider
90
> KHz for the Timestamp, this is not enough for professional video using
> JPEG2K: isn't better to leave this to the implementers?=20

RTP timestamp is a presentation timestamp.
Same frame has same rtp timestamp and timestamp difference
between frames is constant. Therefore 90KHz timestamp is enough.

How many clock rate would you consider for RTP timestamp ?
If there is a strong incentive, I feel no reluctance to
select different clock using rtpmap.

> 3- Adding a payload header is an overhead, so smaller payload header
> size is better. Now, why do we need "T" and "tile number" fields? You
> said that many tiles may exist in the same packet, so in this case no
> meaning of "tile number" and "T" fields?

As you pointed, "tile number" and "T" may not be necessary when
many tiles exists in the same packet, but if no tile header exists
in a packet, which may be more possible, "tile number" and "T"
is needed for receiver to clarify which tile the codestream
is belonging to.

> 4- Is the tp (type) field necessary?. The RTP payload has already the
> payload type (PT) and we can use it instead of tp? If not this
> information can be communicated out of band and can be optional as the
> width and height in section 8.1!

We believe it is necessary because the receiver identify whether
the received codestream is odd or even field's.

"tp" can be used for determining the reciever's action.
For example, if it receives odd field continuously, it can interpolate
even field in some way, or simply discard the duplicated odd field.

> 5- Why do you use the fragment offset?. Isn't (for one RTP session)
the
> sequence number of the RTP packet enough?=20
> When using multiple RTP sessions for layered video, the parser that
> extracted the data for a particular layer (for a particular RTP
session)
> may be transmitted out of band also (the index file is stored either
as
> a separate file or as meta-data). The index file is transmitted to the
> receiver also, so the receiver can rebuild the codestream.

When using multiple RTP session for layered video,=09
JPEG2000 codestream may be split with interleaving.

For example,

Codestream
+----------+----+----+----+----------+----+----+----+----------+----
|Tile 0 Hdr| L0 | L1 | L2 |Tile 1 Hdr| L0 | L1 | L2 |Tile 2 Hdr| ...
+----------+----+----+----+----------+----+----+----+----------+----


RTP 1
+----------+----+         +----------+----+        +----------+----
|Tile 0 Hdr| L0 |         |Tile 1 Hdr| L0 |        |Tile 2 Hdr| L0
+----------+----+         +----------+----+        +----------+----

RTP 2           +----+                    +----+
                | L1 |                    | L1 |             ....
                +----+                    +----+

RTP 3                +----+                    +----+
                     | L2 |                    | L2 |        ....
                     +----+                    +----+
In that case,
interleaved codestream doesn't alwasy arrive at the receiver
in original order.
Fragment offset helps the receiver to rebuild the codestream.

Also, if the fragment offset exist, the receiver need less
memory because it doesn't need de-intgerleave buffer to
rebuilt codestream. It can use same memory space to rebulit it.

> 6- Do we really need to have an MHD flag? The size of main header may
be
> about 300 bytes so is there any chance that this packet will be
> fragmented?

Typical main header may be at most 300 bytes long, but if some JPEG2000
coding options are used, it may be longer.
So MHF flag is neccessary for such situation.

> 7- For the priority field use (the example in section 1.3.1): the
> receiver can select which parts of the codestream to decode without
> using the priority field. It can rebuild the codestream and extract
the
> parts to decode by reading the main header?.=20

Main header contains the progression order information, but it doesn't
include the address information (start position) of each priority level.

Priority field helps the receiver to select the codestream to put into
decoder easily. Without priority field, the receives needs more memory
to rebuild it and has to parse the codestream.


Best Regards,

Futemma


> Cheers,
> Ali=20
> -----Original Message-----
> From: Colin Perkins [mailto:csp@csperkins.org]=20
> Sent: lundi 14 mai 2007 13:59
> To: IETF AVT WG
> Cc: Roni Even; Tom-PT Taylor
> Subject: [AVT] Working group last call: JPEG-2000 payload format
>=20
> This is to announce a working group last call on the RTP Payload =20
> Format for JPEG-2000:
>=20
> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-jpeg2000-15.txt
> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-jpeg2000-=20
> beam-06.txt
>=20
> Please send any final comments on these drafts to the <avt@ietf.org> =20
> mailing list by 28 May 2007. If no substantive comments are received =20
> by that time, we will ask the IESG to consider these drafts for =20
> publication as Proposed Standard RFCs.
>=20
> Note that there is declared IPR on the "beam" draft:
> https://datatracker.ietf.org/public/ipr_detail_show.cgi?ipr_id=3D697
>=20

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



From avt-bounces@ietf.org Mon Jul 09 05:17:42 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7pND-0008OB-Vr; Mon, 09 Jul 2007 05:17:39 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7pNC-0008O2-AA
	for avt@ietf.org; Mon, 09 Jul 2007 05:17:38 -0400
Received: from mail.hhi.fraunhofer.de ([193.174.67.45])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7pN4-00017L-SP
	for avt@ietf.org; Mon, 09 Jul 2007 05:17:38 -0400
Received: by mail.hhi.fraunhofer.de (Postfix, from userid 65534)
	id B638B1D88F87; Mon,  9 Jul 2007 11:16:57 +0200 (CEST)
Received: from [172.19.40.140] (unknown [172.19.40.140])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(Client did not present a certificate)
	by mail.hhi.fraunhofer.de (Postfix) with ESMTP id 9CB6C1D88F82;
	Mon,  9 Jul 2007 11:16:50 +0200 (CEST)
In-Reply-To: <7634542FB03DC747813D67560802AEEDB638F5@rennsmail05.eu.thmulti.com>
References: <7634542FB03DC747813D67560802AEEDB638F5@rennsmail05.eu.thmulti.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <23746892-5149-45DB-9069-690EED0CE8BC@hhi.de>
Content-Transfer-Encoding: 7bit
From: Thomas Wiegand <wiegand@hhi.de>
Subject: Re: [AVT] Scalable Video (JPEG-2000 & SVC) 
Date: Mon, 9 Jul 2007 11:16:49 +0200
To: Boudani Ali <Ali.Boudani@thomson.net>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on 
	mail.hhi.fraunhofer.de
X-Spam-Level: 
X-Spam-Status: No, hits=-104.0 required=5.0 tests=AWL,BAYES_00,
	USER_IN_WHITELIST autolearn=ham version=2.64
X-alterMIME: Yes
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2b2ad76aced9b1d558e34a970a85c027
Cc: IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hello Ali,

Wrt your 1. question, please note that all NAL units within one  
access unit in SVC share the same relative time stamp (in progressive  
pictures) as the pictures they are representing are assumed to be  
sampled/displayed at the same time.

Wrt your 2. question, there are no fragments in SVC like in JPEG2K.  
All scalability in SVC is achieved by dropping complete NAL units (==  
packets).

Best Regards,
Thomas

---
Dr.-Ing. Thomas Wiegand
Head, Image Communication Group
Image Processing Department
Fraunhofer Inst. for Telecommunications - HHI
Einsteinufer 37, D-10587 Berlin, Germany
Phone: +49 30 31002 617,
Mobile: +49 172 381 3814
http: iphome.hhi.de/wiegand
---


On Jul 9, 2007, at 10:49 AM, Boudani Ali wrote:

> Hello,
> 1- In the SVC draft that describes the RTP Payload Format for SVC  
> Video,
> each RTP packet stream can carry NAL units belonging to one or more
> layers.
> When multiple RTP packet streams are in use, they are session
> multiplexed and form their own RTP session and therefore have their  
> own
> SSRC, PT, and Sequence numbering space. What about the timestamp (same
> sampling instant)?
> Now, for the JPEG2K Codestream when transmitting layers in  
> different RTP
> sessions, do we have the same timestamp for all these packets (because
> of the same sampling instant) and what about the sequence number? The
> multiple RTP packet streams in use are session multiplexed, do they  
> have
> their own Sequence numbering space?.
>
> For example what would be the values for this JPEG2K Codestream?
> +----------+----+----+----+----------+----+----+----+----------+----
> |Tile 0 Hdr| L0 | L1 | L2 |Tile 1 Hdr| L0 | L1 | L2 |Tile 2 Hdr| ...
> +----------+----+----+----+----------+----+----+----+----------+----
> RTP session 1
> +----------+----+         +----------+----+        +----------+----
> |Tile 0 Hdr| L0 |         |Tile 1 Hdr| L0 |        |Tile 2 Hdr| L0
> +----------+----+         +----------+----+        +----------+----
> RTP session 2
>                 +----+                    +----+
>                 | L1 |                    | L1 |             ....
>                 +----+                    +----+
> RTP session 3
>                      +----+                    +----+
>                      | L2 |                    | L2 |        ....
>                      +----+                    +----+
>
> 2- What about using a fragment offset with SVC? The SVC draft has also
> layers (like JPEG2K) but doesn't use any offset! In the other hand,  
> the
> JPEG2K draft, says that a fragment offset value MUST be set to the  
> byte
> offset of the current payload in relation to the very beginning of  
> each
> JPEG 2000 codestream (JPEG 2000 frame). Is the "MUST" is the best
> keyword here. I may need it only if I am sending the different  
> layers of
> the same codestream over multiple sessions.
>
> Thanks,
> Ali
> -----Original Message-----
> From: Satoshi Futemma [mailto:satosi-f@sm.sony.co.jp]
> Sent: lundi 28 mai 2007 09:37
> To: Boudani Ali
> Cc: IETF AVT WG; Colin Perkins; Andrew Leung; ITAKURA Eisaburo
> Subject: Re: [AVT] Working group last call: JPEG-2000 payload format
>
> Dear Ali,
>
> Thank you for the comments.
> Please see inline.
>
> Boudani Ali wrote:
>> Hello,
>> I read the two drafts. Before going to the IESG, It will be better if
>> the authors clarify some issues.
>> Here are my comments:
>>
>> 1- How can we identify the packets belonging to the same Codestream
>> (frame) (especially when using multiple RTP sessions). Don't you  
>> think
>> that we need to add a frame_id identifier?.
>
> RTP timestamp can be used for that purpose.
>
>> 2- In section 4.1 of Draft-ietf-avt-rtp-jpeg2000-15.txt: you consider
> 90
>> KHz for the Timestamp, this is not enough for professional video  
>> using
>> JPEG2K: isn't better to leave this to the implementers?
>
> RTP timestamp is a presentation timestamp.
> Same frame has same rtp timestamp and timestamp difference
> between frames is constant. Therefore 90KHz timestamp is enough.
>
> How many clock rate would you consider for RTP timestamp ?
> If there is a strong incentive, I feel no reluctance to
> select different clock using rtpmap.
>
>> 3- Adding a payload header is an overhead, so smaller payload header
>> size is better. Now, why do we need "T" and "tile number" fields? You
>> said that many tiles may exist in the same packet, so in this case no
>> meaning of "tile number" and "T" fields?
>
> As you pointed, "tile number" and "T" may not be necessary when
> many tiles exists in the same packet, but if no tile header exists
> in a packet, which may be more possible, "tile number" and "T"
> is needed for receiver to clarify which tile the codestream
> is belonging to.
>
>> 4- Is the tp (type) field necessary?. The RTP payload has already the
>> payload type (PT) and we can use it instead of tp? If not this
>> information can be communicated out of band and can be optional as  
>> the
>> width and height in section 8.1!
>
> We believe it is necessary because the receiver identify whether
> the received codestream is odd or even field's.
>
> "tp" can be used for determining the reciever's action.
> For example, if it receives odd field continuously, it can interpolate
> even field in some way, or simply discard the duplicated odd field.
>
>> 5- Why do you use the fragment offset?. Isn't (for one RTP session)
> the
>> sequence number of the RTP packet enough?
>> When using multiple RTP sessions for layered video, the parser that
>> extracted the data for a particular layer (for a particular RTP
> session)
>> may be transmitted out of band also (the index file is stored either
> as
>> a separate file or as meta-data). The index file is transmitted to  
>> the
>> receiver also, so the receiver can rebuild the codestream.
>
> When using multiple RTP session for layered video,	
> JPEG2000 codestream may be split with interleaving.
>
> For example,
>
> Codestream
> +----------+----+----+----+----------+----+----+----+----------+----
> |Tile 0 Hdr| L0 | L1 | L2 |Tile 1 Hdr| L0 | L1 | L2 |Tile 2 Hdr| ...
> +----------+----+----+----+----------+----+----+----+----------+----
>
>
> RTP 1
> +----------+----+         +----------+----+        +----------+----
> |Tile 0 Hdr| L0 |         |Tile 1 Hdr| L0 |        |Tile 2 Hdr| L0
> +----------+----+         +----------+----+        +----------+----
>
> RTP 2           +----+                    +----+
>                 | L1 |                    | L1 |             ....
>                 +----+                    +----+
>
> RTP 3                +----+                    +----+
>                      | L2 |                    | L2 |        ....
>                      +----+                    +----+
> In that case,
> interleaved codestream doesn't alwasy arrive at the receiver
> in original order.
> Fragment offset helps the receiver to rebuild the codestream.
>
> Also, if the fragment offset exist, the receiver need less
> memory because it doesn't need de-intgerleave buffer to
> rebuilt codestream. It can use same memory space to rebulit it.
>
>> 6- Do we really need to have an MHD flag? The size of main header may
> be
>> about 300 bytes so is there any chance that this packet will be
>> fragmented?
>
> Typical main header may be at most 300 bytes long, but if some  
> JPEG2000
> coding options are used, it may be longer.
> So MHF flag is neccessary for such situation.
>
>> 7- For the priority field use (the example in section 1.3.1): the
>> receiver can select which parts of the codestream to decode without
>> using the priority field. It can rebuild the codestream and extract
> the
>> parts to decode by reading the main header?.
>
> Main header contains the progression order information, but it doesn't
> include the address information (start position) of each priority  
> level.
>
> Priority field helps the receiver to select the codestream to put into
> decoder easily. Without priority field, the receives needs more memory
> to rebuild it and has to parse the codestream.
>
>
> Best Regards,
>
> Futemma
>
>
>> Cheers,
>> Ali
>> -----Original Message-----
>> From: Colin Perkins [mailto:csp@csperkins.org]
>> Sent: lundi 14 mai 2007 13:59
>> To: IETF AVT WG
>> Cc: Roni Even; Tom-PT Taylor
>> Subject: [AVT] Working group last call: JPEG-2000 payload format
>>
>> This is to announce a working group last call on the RTP Payload
>> Format for JPEG-2000:
>>
>> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp- 
>> jpeg2000-15.txt
>> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-jpeg2000-
>> beam-06.txt
>>
>> Please send any final comments on these drafts to the <avt@ietf.org>
>> mailing list by 28 May 2007. If no substantive comments are received
>> by that time, we will ask the IESG to consider these drafts for
>> publication as Proposed Standard RFCs.
>>
>> Note that there is declared IPR on the "beam" draft:
>> https://datatracker.ietf.org/public/ipr_detail_show.cgi?ipr_id=697
>>
>
> _______________________________________________
> 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 Jul 09 07:20:10 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7rHi-0006DO-Sg; Mon, 09 Jul 2007 07:20:06 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7rHf-0006Cm-7x; Mon, 09 Jul 2007 07:20:03 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I7rHe-00045C-V1; Mon, 09 Jul 2007 07:20:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id A7E08175E3;
	Mon,  9 Jul 2007 11:20:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I7rHe-00028z-96; Mon, 09 Jul 2007 07:20:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I7rHe-00028z-96@stiedprstage1.ietf.org>
Date: Mon, 09 Jul 2007 07:20:02 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: avt@ietf.org
Subject: [AVT] I-D Action:draft-ietf-avt-rtp-howto-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>
Errors-To: avt-bounces@ietf.org

--NextPart

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

                                                                                           
        Title           : How to Write an RTP Payload Format
        Author(s)       : M. Westerlund
        Filename        : draft-ietf-avt-rtp-howto-02.txt
        Pages           : 52
        Date            : 2007-07-09
                                                                                           
This document contains information on how to best write an RTP
payload format.  Reading tips, design practices, and practical tips
on how to quickly and with good results produce an RTP payload format
specification.  A template is also included with instructions that
can be used when writing an RTP payload format.
                                                                                           
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-howto-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-howto-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-howto-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: <2007-07-09071522.I-D@ietf.org>


ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-howto-02.txt
                                                                                           
--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-avt-rtp-howto-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"
Content-Type: text/plain
Content-ID: <2007-07-09071522.I-D\@ietf.org>



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

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

--NextPart--




From avt-bounces@ietf.org Mon Jul 09 11:48:33 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7vT9-00081M-Oh; Mon, 09 Jul 2007 11:48:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7vT8-00080v-Af
	for avt@ietf.org; Mon, 09 Jul 2007 11:48:10 -0400
Received: from lumisoft.ee ([84.50.104.142] helo=mail.lumisoft.ee)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7vT3-0003PD-W2
	for avt@ietf.org; Mon, 09 Jul 2007 11:48:10 -0400
Received: from 192.168.1.1 (192.168.1.1)
	by mail.lumisoft.ee with SMTP; Mon, 09 Jul 2007 15:27:52 GMT
Message-ID: <469254BA.2010802@lumisoft.ee>
Date: Mon, 09 Jul 2007 18:31:06 +0300
From: Ivar <ivar@lumisoft.ee>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: avt@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Subject: [AVT] Rtp session with multiple sender streams.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi,

RFC 3550 3. says that session may have multiple sending streams, but all 
must have it's own SSRC.

Now for example session is receiver and there are 2 sending streams, how 
compound RTCP packet is composed ?
Has 2 SR reports if both sender streams have sent data, has 1 SR if only 
1 stream sent data ? (each SR report has reported sender stream SSRC)
And what SSRC is used for RR, if there are more than 31 remote senders 
or no local RTP sent during last RTCP interval? (generate local receiver 
SSRC for that ?)
Also how all this affects SDES, because there are more than 1 SSRC for 
RTP session ?
(One of the SSRC will send all sdes items, other SSRCs only CNAME(which 
will map SSRC to participant))

Thanks,




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



From avt-bounces@ietf.org Mon Jul 09 16:14:57 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7zd7-0007L8-Rw; Mon, 09 Jul 2007 16:14:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7zd5-0006wk-2B; Mon, 09 Jul 2007 16:14:43 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I7zd0-0004wG-KM; Mon, 09 Jul 2007 16:14:43 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 09 Jul 2007 13:14:35 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CACA0kkarR7PE/2dsb2JhbAA
X-IronPort-AV: i="4.16,518,1175497200"; 
	d="scan'208"; a="179087494:sNHT3047388453"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l69KEZDc016783; 
	Mon, 9 Jul 2007 13:14:35 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l69KEZvv027138;
	Mon, 9 Jul 2007 20:14:35 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Jul 2007 13:14:35 -0700
Received: from [10.32.241.146] ([10.32.241.146]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Jul 2007 13:14:35 -0700
Message-ID: <4692972F.8050003@cisco.com>
Date: Mon, 09 Jul 2007 16:14:39 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: IETF MMUSIC WG <mmusic@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Jul 2007 20:14:35.0111 (UTC)
	FILETIME=[C4B63770:01C7C265]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2604; t=1184012075;
	x=1184876075; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20ICE-TCP=20issue=3A=20DTLS-SRTP=20over=20TCP?
	|Sender:=20; bh=quxDGBmUa2M4CCehx25LqvAtEFvuYerLTdfDiaoG7d4=;
	b=HMdMVb/0rx85ba016beR5m8NNR0aa5yvW3k3xHCtNhHJDVH96cWKq0SItSQGWOx9AnjoyUIt
	PWppvx6C9MeAGslkGC+neXd1LAguJq6nq95ml7+emPmLA2qB0uEe6cIL;
Authentication-Results: sj-dkim-4; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: "'avt@ietf.org'" <avt@ietf.org>
Subject: [AVT] ICE-TCP issue: DTLS-SRTP over TCP?
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

My apologies for cc'ing AVT. However this is a cross-WG issue that 
impacts ICE and its usage with DTLS-SRTP.

ICE-tcp:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-ice-tcp-04.txt
DTLS-srtp:
http://www.ietf.org/internet-drafts/draft-ietf-avt-dtls-srtp-00.txt


One of the really nice features of ICE-tcp is that you can offer, for an 
RTP-based media stream, either UDP or TCP candidates. The TCP ones are 
tried as a last resort, so that you get RTP over UDP when it works, and 
RTP over TCP when it doesn't. This choice is made dynamically based on 
the results of the connectivity checks.

So, the interesting question is, what happens if the media is secure? 
Well, clearly if UDP is selected, we end up with DTLS-SRTP. In that 
case, the SDP offer would contain the fingerprint and setup attributes. 
What happens if ICE selects TCP instead? There are two things this could 
mean:

1. the media is secured using RTP over a TCP/TLS connection using 
RFC4571. This is *not* SRTP; the RTP packets are fully encrypted.

2. the media is secured using DTLS-SRTP, run over the RFC4571 shim that 
is ontop of TCP when ICE is in use. In this case, the media packets are 
SRTP and the RTP headers are in the clear as normal.


In many ways, #2 is a far preferable solution. It means that the 
mechanism for securing the media, and the associated SDP parameters and 
their meaning, are independent of the transport protocol and apply for 
UDP or TCP. With #1, the agent needs to run different protocols (TLS vs. 
DTLS) for security, depending on the transport protocol selected. That 
also has interactions with SDP capability negotiation, and it gets 
really messy.

So, #2 is what is specified in ice-tcp. However, AFAIK, DTLS-SRTP is not 
defined over TCP. I don't think it needs to change any per se; but it 
does need to be recognized as a valid mode.

Similarly, even ignoring a mix of UDP and TCP candidates, if we are just 
offering TCP candidates, does the media get secured using #1 or #2? Do 
we allow both? Right now ICE-tcp is allowing both. However, I think its 
bad to have two ways of doing this. I'd rather settle on DTLS-SRTP over 
TCP as the one and only way of securing RTP over TCP.

Comments?
-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Cisco Fellow                                   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

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



From avt-bounces@ietf.org Mon Jul 09 17:15:16 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I80ZV-00082F-1r; Mon, 09 Jul 2007 17:15:05 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I80ZS-00081B-Cx; Mon, 09 Jul 2007 17:15:02 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I80ZS-0002I3-5V; Mon, 09 Jul 2007 17:15:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 1275B2ACA7;
	Mon,  9 Jul 2007 21:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I80ZR-0008SA-Qn; Mon, 09 Jul 2007 17:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I80ZR-0008SA-Qn@stiedprstage1.ietf.org>
Date: Mon, 09 Jul 2007 17:15:01 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtcpxr-video-01.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: RTCP XR - Video Metrics Report Blocks
	Author(s)	: A. Clark, A. Pendleton
	Filename	: draft-ietf-avt-rtcpxr-video-01.txt
	Pages		: 0
	Date		: 2007-7-9
	
This document defines extensions to the RTCP XR extended report
   packet type blocks to support the monitoring of video over IP 
   for IPTV and videoconferencing endpoint reporting.
   [Note that the audio and transport metric report blocks contained
   in the -00 draft have been moved to separate drafts.]

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcpxr-video-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-rtcpxr-video-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-rtcpxr-video-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: <2007-7-9160207.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtcpxr-video-01.txt

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

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


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org Tue Jul 10 06:58:12 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8DPU-0005ll-Vj; Tue, 10 Jul 2007 06:57:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7zma-0004Zn-5m
	for avt@ietf.org; Mon, 09 Jul 2007 16:24:32 -0400
Received: from loki.cs.umass.edu ([128.119.243.168] helo=mail.cs.umass.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7zmH-0005ZE-SZ
	for avt@ietf.org; Mon, 09 Jul 2007 16:24:32 -0400
Received: from [128.119.245.44] (bansuri.cs.umass.edu [128.119.245.44])
	(authenticated bits=0 authid=zink)
	by mail.cs.umass.edu (8.13.7/8.13.1) with ESMTP id l69KOCEl001616
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT)
	for <avt@ietf.org>; Mon, 9 Jul 2007 16:24:12 -0400
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: quoted-printable
Message-Id: <096D1ACB-EC41-40F6-884A-EB04D4E9A7B0@cs.umass.edu>
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed
To: avt@ietf.org
From: Michael Zink <zink@cs.umass.edu>
Date: Mon, 9 Jul 2007 16:25:28 -0400
X-Mailer: Apple Mail (2.752.3)
X-Spam-Net-Tests: NO (loki, relay 128.119.245.44 auth=site-local)
X-Spam-Checked: This message probably not SPAM
X-Spam-Score: 0, Required: 5
X-Scanned-By: MIMEDefang 2.62 on 128.119.243.168
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
X-Mailman-Approved-At: Tue, 10 Jul 2007 06:57:35 -0400
Subject: [AVT] Call for papers: SPIE/ACM MMCN 2008
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

                 Call for Papers and Announcement

                        SPIE/ACM MMCN 2008
             Multimedia Computing and Networking 2008

               http://mirage.cs.uoregon.edu/mmcn2008

              In cooperation with: ACM SIG Multimedia
  Part of the IS&T/SPIE International Symposium on Electronic Imaging
                       30 and 31 January 2008

            San Jose Marriott and San Jose Convention Center
                        San Jose, CA, USA

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

For 15 years, the multimedia computing and networking conference has =20
brought
together researchers, practitioners and developers to contribute new =20
ideas in
all facets of multimedia systems, networking, applications, and other =20=

related
areas of computing.  Traditionally the conference features =20
presentations of full
and short papers, a keynote talk, and a panel of experts.  Presenters =20=

are
encouraged to make multimedia presentations and demonstrate their =20
proposed
solutions.  Authors of a few accepted papers with the highest quality =20=

are
invited to submit the extended version of their papers to a special =20
issue of
ACM/Springer Multimedia Systems Journal.

Original papers on all emerging technologies and traditional
areas of multimedia, including but not limited to:

Multimedia Computing
. multimedia OS services
. power-aware systems
. video-on-demand services
. mixed and augmented reality systems

Measurement and Modeling
. performance measurement of multimedia systems
. statistical modeling of server traffic and server software
. multimedia system simulations and benchmark comparisons

Multimedia Networking
. home, mobile and broadband networks
. QoS control and scheduling
. push technologies and content distribution
. peer-to-peer media systems
. Internet data streaming, delivery and wide-area caching
. multimedia security and rights management

Case Studies and Applications
. multimedia search engines
. entertainment and networked games
. distributed augmented and virtual reality
. multimedia authoring

Authors are invited to submit both research and industrial papers on =20
original,
unpublished work that is not currently under submission at any other =20
conference.
Papers whose contributions are supported by experimental evaluations are
strongly encouraged.  Both full and short papers are considered.  =20
Full paper
submissions should not exceed 12 single-spaced, single column pages =20
including
figures, tables, and references, using a typeface no smaller than 10 =20
points.
Short paper submissions should not exceed 8 pages.  All papers must be
electronically submitted to the conference website at
http://www.electronicimaging.org.  Please also submit a 500-word text =20=

abstract
with your paper submission that includes your topic area.  Further =20
information
about MMCN'08 can be found at http://mirage.cs.uoregon.edu/mmcn2008.

| Full Paper for Review Due:  16 July 2007                     |
| Short Paper for Review Due: 16 July 2007                     |
| Final Manuscript Due:       12 November 2007                 |
| 200-word Final Summary Due: 19 November 2007                 |
| Proceedings of this conference will be published and         |
| available at the meeting.                                    |


Conference Chairs:
  Reza Rejaje, Univ. of Oregon (USA)
  Roger Zimmermann, National Univ. of Singapore (Singapore)

Publicity Co-Chairs:
  Wei Tsang Ooi, National Univ. of Singapore (Singapore)
  Andreas Mauthe, Lancaster Univ. (UK)
  Michael Zink, Univ. of Massachusetts/Amherst (USA)

Program Committee:
  Tarek Abdelzaher, Univ. of Illinois/Urbana-Champaign (USA)
  Kevin Almeroth, Univ. of California/Santa Barbara (USA)
  Scott A. Brandt, Univ. of California/Santa Cruz (USA)
  Surendar Chandra, Univ. of Notre Dame (USA)
  Mark Claypool, Worcester Polytechnic Institute (USA)
  David Hung-Chang Du, Univ. of Minnesota (USA)
  Wu-chi Feng, Portland State Univ. (USA)
  Pascal Frossard, Swiss Federal Institute of Technology/Lausanne =20
(Switzerland)
  Christos Gkantsidis, Microsoft Research (UK)
  Carsten Griwodz, Univ. of Oslo (Norway)
  Yang Guo, Thomson Lab (USA)
  Ahsan Habib, Siemens TTB Center/Berkeley (USA)
  Mohamed Hefeeda, Simon Fraser University (Canada)
  P=86l Halvorsen, Simula Research Laboratory (Norway)
  Seon Ho Kim, Univ. of Denver (USA)
  Baochun Li, Univ. of Toronto (Canada)
  Kang Li, Univ. of Georgia (USA)
  Andreas Mauthe, Lancaster Univ. (UK)
  Ketan Mayer-Patel, Univ. of North Carolina/Chapel Hill (USA)
  Klara Nahrstedt, Univ. of Illinois/Urbana-Champaign (USA)
  Wei Tsang Ooi, National Univ. of Singapore (Singapore)
  Karsten Schwan, Georgia Institute of Technology (USA)
  Subhabrata Sen, AT&T Labs-Research (USA)
  Nalini Venkatasubramanian, Univ. of California/Irvine (USA)
  Dongyan Xu, Purdue Univ. (USA)
  Zhi-Li Zhang, Univ. of Minnessotta (USA)
  Michael Zink, Univ. of Massachusetts/Amherst (USA)=

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



From avt-bounces@ietf.org Tue Jul 10 07:29:20 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8Du6-0006x0-3N; Tue, 10 Jul 2007 07:29:14 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8Du4-0006wN-BP
	for avt@ietf.org; Tue, 10 Jul 2007 07:29:12 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8Dtd-0002ce-Sd
	for avt@ietf.org; Tue, 10 Jul 2007 07:29:12 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	2C9F1214E9; Tue, 10 Jul 2007 13:28:13 +0200 (CEST)
X-AuditID: c1b4fb3e-ae831bb0000007e1-41-46936d4d0bf2
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	062C42175C; Tue, 10 Jul 2007 13:28:13 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 10 Jul 2007 13:28:12 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 10 Jul 2007 13:28:12 +0200
Message-ID: <46936D4C.6020800@ericsson.com>
Date: Tue, 10 Jul 2007 13:28:12 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: Ivar <ivar@lumisoft.ee>
Subject: Re: [AVT] Rtp session with multiple sender streams.
References: <469254BA.2010802@lumisoft.ee>
In-Reply-To: <469254BA.2010802@lumisoft.ee>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 Jul 2007 11:28:12.0521 (UTC)
	FILETIME=[666F2D90:01C7C2E5]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Ivar skrev:
> Hi,
> 
> RFC 3550 3. says that session may have multiple sending streams, but all 
> must have it's own SSRC.
> 
> Now for example session is receiver and there are 2 sending streams, how 
> compound RTCP packet is composed ?
> Has 2 SR reports if both sender streams have sent data, has 1 SR if only 
> 1 stream sent data ? (each SR report has reported sender stream SSRC)

Each source needs to send its own RTCP compound packets with an SR for 
itself an containing reports on all the other sources it currently 
receives data from. To avoid throwing off any quality report user, also 
SSRCs co-located in the same host needs to include report blocks on each 
other.

> And what SSRC is used for RR, if there are more than 31 remote senders 
> or no local RTP sent during last RTCP interval? 

All senders or receivers have their own SSRC. That is always used as 
reporting the source of the RR. The content of the report block is 
round-robined in case there are more than 31 active sources.

(generate local receiver SSRC for that ?)

Not certain what you mean with this. But if you mean that a receiver 
that isn't sending media, it still needs to have an SSRC. Any sender or 
receiver do need to have an SSRC. The only one that can live without an 
SSRC is a completely passive receiver, i.e. do not send RTCP or RTP.


> Also how all this affects SDES, because there are more than 1 SSRC for 
> RTP session ?

As each session participant sends its own compound packets they shall 
include the SDES CNAME item for themselves. In addition mixers may 
include SDES items from contributing sources.

> (One of the SSRC will send all sdes items, other SSRCs only CNAME(which 
> will map SSRC to participant))

Well this is allowed but doesn't make much sense. As the SDES item 
describe the indicated SSRC, and says nothing about the others. No 
assumption can really be made with the possible exception between 
different media streams and for the SSRCs in the different sessions that 
indicate the same CNAME value.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
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 Jul 10 08:56:59 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8FGr-0001Cj-CQ; Tue, 10 Jul 2007 08:56:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8DgB-0005P6-Td
	for avt@ietf.org; Tue, 10 Jul 2007 07:14:51 -0400
Received: from pigwidgeon.lancs.ac.uk ([148.88.0.67])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8DgB-0000bH-BY
	for avt@ietf.org; Tue, 10 Jul 2007 07:14:51 -0400
Received: from mail02.lancs.ac.uk ([148.88.1.54])
	by pigwidgeon.lancs.ac.uk with esmtp (Exim 4.60)
	(envelope-from <andreas@comp.lancs.ac.uk>) id 1I8DgA-0000Z9-OI
	for avt@ietf.org; Tue, 10 Jul 2007 12:14:50 +0100
Received: from ind013000002.lancs.ac.uk ([148.88.225.132] helo=[127.0.0.1])
	by mail02.lancs.ac.uk with esmtp (Exim 4.66)
	(envelope-from <andreas@comp.lancs.ac.uk>)
	id 1I8DgA-0008Et-E1; Tue, 10 Jul 2007 12:14:50 +0100
Message-ID: <46936A2A.5010207@comp.lancs.ac.uk>
Date: Tue, 10 Jul 2007 12:14:50 +0100
From: "Dr. Andreas Mauthe" <andreas@comp.lancs.ac.uk>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: avt@ietf.org,  conferencesx@comsocconferences.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1
X-Mailman-Approved-At: Tue, 10 Jul 2007 08:56:47 -0400
Cc: 
Subject: [AVT] MMCN 07
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org



Submission Deadline Approaching!!!

>
>
> =====================================================================
>
> Call for Papers and Announcement
>
> SPIE/ACM MMCN 2008
> Multimedia Computing and Networking 2008
>
> http://mirage.cs.uoregon.edu/mmcn2008
>
> In cooperation with: ACM SIG Multimedia
> Part of the IS&T/SPIE International Symposium on Electronic Imaging
> 30 and 31 January 2008
>
> San Jose Marriott and San Jose Convention Center
> San Jose, CA, USA
>
> =====================================================================
>
> For 15 years, the multimedia computing and networking conference has 
> brought
> together researchers, practitioners and developers to contribute new 
> ideas in
> all facets of multimedia systems, networking, applications, and other 
> related
> areas of computing. Traditionally the conference features 
> presentations of full
> and short papers, a keynote talk, and a panel of experts. Presenters are
> encouraged to make multimedia presentations and demonstrate their 
> proposed
> solutions. Authors of a few accepted papers with the highest quality are
> invited to submit the extended version of their papers to a special 
> issue of
> ACM/Springer Multimedia Systems Journal.
>
> Original papers on all emerging technologies and traditional
> areas of multimedia, including but not limited to:
>
> Multimedia Computing
> . multimedia OS services
> . power-aware systems
> . video-on-demand services
> . mixed and augmented reality systems
>
> Measurement and Modeling
> . performance measurement of multimedia systems
> . statistical modeling of server traffic and server software
> . multimedia system simulations and benchmark comparisons
>
> Multimedia Networking
> . home, mobile and broadband networks
> . QoS control and scheduling
> . push technologies and content distribution
> . peer-to-peer media systems
> . Internet data streaming, delivery and wide-area caching
> . multimedia security and rights management
>
> Case Studies and Applications
> . multimedia search engines
> . entertainment and networked games
> . distributed augmented and virtual reality
> . multimedia authoring
>
> Authors are invited to submit both research and industrial papers on 
> original,
> unpublished work that is not currently under submission at any other 
> conference.
> Papers whose contributions are supported by experimental evaluations are
> strongly encouraged. Both full and short papers are considered. Full 
> paper
> submissions should not exceed 12 single-spaced, single column pages 
> including
> figures, tables, and references, using a typeface no smaller than 10 
> points.
> Short paper submissions should not exceed 8 pages. All papers must be
> electronically submitted to the conference website at
> http://www.electronicimaging.org. Please also submit a 500-word text 
> abstract
> with your paper submission that includes your topic area. Further 
> information
> about MMCN'08 can be found at http://mirage.cs.uoregon.edu/mmcn2008.
>
> | Full Paper for Review Due: 16 July 2007 |
> | Short Paper for Review Due: 16 July 2007 |
> | Final Manuscript Due: 12 November 2007 |
> | 200-word Final Summary Due: 19 November 2007 |
> | Proceedings of this conference will be published and |
> | available at the meeting. |
>
>
> Conference Chairs:
> Reza Rejaje, Univ. of Oregon (USA)
> Roger Zimmermann, National Univ. of Singapore (Singapore)
>
> Publicity Co-Chairs:
> Wei Tsang Ooi, National Univ. of Singapore (Singapore)
> Andreas Mauthe, Lancaster Univ. (UK)
> Michael Zink, Univ. of Massachusetts/Amherst (USA)
>
> Program Committee:
> Tarek Abdelzaher, Univ. of Illinois/Urbana-Champaign (USA)
> Kevin Almeroth, Univ. of California/Santa Barbara (USA)
> Scott A. Brandt, Univ. of California/Santa Cruz (USA)
> Surendar Chandra, Univ. of Notre Dame (USA)
> Mark Claypool, Worcester Polytechnic Institute (USA)
> David Hung-Chang Du, Univ. of Minnesota (USA)
> Wu-chi Feng, Portland State Univ. (USA)
> Pascal Frossard, Swiss Federal Institute of Technology/Lausanne 
> (Switzerland)
> Christos Gkantsidis, Microsoft Research (UK)
> Carsten Griwodz, Univ. of Oslo (Norway)
> Yang Guo, Thomson Lab (USA)
> Ahsan Habib, Siemens TTB Center/Berkeley (USA)
> Mohamed Hefeeda, Simon Fraser University (Canada)
> Pï¿½l Halvorsen, Simula Research Laboratory (Norway)
> Seon Ho Kim, Univ. of Denver (USA)
> Baochun Li, Univ. of Toronto (Canada)
> Kang Li, Univ. of Georgia (USA)
> Andreas Mauthe, Lancaster Univ. (UK)
> Ketan Mayer-Patel, Univ. of North Carolina/Chapel Hill (USA)
> Klara Nahrstedt, Univ. of Illinois/Urbana-Champaign (USA)
> Wei Tsang Ooi, National Univ. of Singapore (Singapore)
> Karsten Schwan, Georgia Institute of Technology (USA)
> Subhabrata Sen, AT&T Labs-Research (USA)
> Nalini Venkatasubramanian, Univ. of California/Irvine (USA)
> Dongyan Xu, Purdue Univ. (USA)
> Zhi-Li Zhang, Univ. of Minnessotta (USA)
> Michael Zink, Univ. of Massachusetts/Amherst (US
> A)


-- 
__________________________________________________________________________
Dr Andreas U. Mauthe

Computing Department
InfoLab 21
South Drive
Lancaster University			Phone:   +44/1524/5 10485
Lancaster LA1 4WA			   Fax:     +44/1524/5 10492
United Kingdom				  E-mail: andreas@comp.lancs.ac.uk

http://www.comp.lancs.ac.uk/computing/users/andreas/
__________________________________________________________________________


_______________________________________________
All mailing list
All@ist-content.eu
https://www.ist-content.eu:448/cgi-bin/mailman/listinfo/all



-- 
__________________________________________________________________________
Dr Andreas U. Mauthe

Computing Department
InfoLab 21
South Drive
Lancaster University			Phone:   +44/1524/5 10485
Lancaster LA1 4WA			   Fax:     +44/1524/5 10492
United Kingdom				  E-mail: andreas@comp.lancs.ac.uk

http://www.comp.lancs.ac.uk/computing/users/andreas/
__________________________________________________________________________



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



From avt-bounces@ietf.org Tue Jul 10 09:10:01 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8FTZ-0003dH-NL; Tue, 10 Jul 2007 09:09:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8FTY-0003XM-4X
	for avt@ietf.org; Tue, 10 Jul 2007 09:09:56 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8FTX-00041p-Az
	for avt@ietf.org; Tue, 10 Jul 2007 09:09:56 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	8A5CF216A1; Tue, 10 Jul 2007 15:09:54 +0200 (CEST)
X-AuditID: c1b4fb3e-b0034bb0000007e1-b1-469385227006
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	5BED921617; Tue, 10 Jul 2007 15:09:54 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 10 Jul 2007 15:09:53 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 10 Jul 2007 15:09:53 +0200
Message-ID: <46938521.7080607@ericsson.com>
Date: Tue, 10 Jul 2007 15:09:53 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: Ivar <ivar@lumisoft.ee>
Subject: Re: [AVT] Rtp session with multiple sender streams.
References: <469254BA.2010802@lumisoft.ee> <46936D4C.6020800@ericsson.com>
	<469379E4.107@lumisoft.ee>
In-Reply-To: <469379E4.107@lumisoft.ee>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 Jul 2007 13:09:53.0681 (UTC)
	FILETIME=[9B025010:01C7C2F3]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ec7c6dab5a62df223002ae71b5179d41
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi,

I think you are a bit confused over the basics and I think the only 
reasonable approach to answer this is to have include a short tutorial 
over how things connects together. Then you can follow up with any 
remaining questions after having gone back and read RFC 3550 once more.

An RTP session consists of a SSRC (Sender Source) space. Each SSRC 
indicates an entity sending packets, either RTP and/or RTCP. Thus both 
senders and receivers need to have a SSRC (I call the joint group of 
senders and receivers for participants). For an host sending media, it 
might require multiple SSRCs to represent different sources of the 
media. Like from two different video cameras or microphones. Each media 
stream of RTP packets will indicate which SSRC it comes from.

RTCP is used for a number of different purposes and that is why each 
sent RTCP packet is a compound packet to allow for the necesary parts to 
be included. A media sender will send Sender Reports to incidicate that 
it is sending media and how that is progressing. A Receiver will send 
Receiver reports to indicate which RTP streams from which SSRC it is 
receiving. As media senders commonly also are media receivers the Sender 
Reports include the same receiver reporting as the receiver reports.

The CNAME (Canonical Name) exist to provide two features. 1) To provide 
a binding between different RTP sessions for media that should be 
synchronized. 2) To be an better unique identifier to detect collisions 
with than the SSRC itself. Thus each SSRC has its own unique CNAME in 
the session.

Everything in RTP and RTCP is built around that each entity doing 
something is identified with its SSRC. From that one can add additional 
information like the SDES information on a per SSRC basis. The receiver 
reporting provides information from each receiver on how they see the 
reception quality of all the sources seen.

I also think you can benefit from reviewing two drafts:

- The RTP topologies draft that will probably make you think a bit more 
about the different usages RTP can be applied in:
http://www.ietf.org/internet-drafts/draft-ietf-avt-topologies-05.txt

- The HOW TO write RTP payload formats that contain some of the basic 
concepts written in somewhat other terms than what is written in RFC 3550.
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-howto-02.txt

You could also consider buying Colin Perkins book "RTP: Audio and Video 
for the Internet" that explains most aspects of RTP.

Best Regards

Magnus

Ivar skrev:
> 
> Thakns for the answer.
> 
> But i need some more confirmations, before i get the whole picture.
> (I have most RTP implementation done (packets parsing,interval 
> calculation,...), but i can't relate some object dependencies)
> 
>  >Each source needs to send its own RTCP compound packets with an SR for 
> itself an containing reports on all the other sources it currently 
> receives data from.
> Ok dummy question what is source ? If RTP sesion has 2 sending streams 
> and receives data from xxx count of sources, then we have 3 sources (2 
> sending source and 1 receiving source) ?
> Does RTP session may have only 1 receiver SSRC what will be added to RR 
> reports ?
> Has each sending source has own CNAME ?
> 
> The problem is can't relate source,participant relation ship.
> The confusing parts are like:
>    Each source needs to send its own RTCP compound packets
>    and now
>    As each session participant sends its own compound packets
> Even the term participant is some how confusing, like participant may 
> have multiple streams, may be in multiple sessions, ... .
> I have readed rfc 3550 over and over during 2 weeks,  i can't get such 
> simple stuff.
> 
> I need to idea of this simple case:
> SSRC are just exmples, in realife randoms.
> 
> RTP_Session
>    SendStreams
>       SendStream1  SSRC   = 1 (source in your term if i get right)
>       SendStream2  SSRSC = 2
> 
>    ReceiveStreams - Receive streams is like receiver and has SSRC = 3 
> .... ?
>      ReceiveStream1 SSRC = 100 (source in your term if i get right)
>      ReceiveStream2 SSRC = 101
> 
> Now RTCP interval reaches, Both sending streams has sent data.
> What actually happnes what we must compose here ?
> 
> 2 x SR ?
> RR 1 -  SSRC = 1
> ... no report blocks
> RR 2 -  SSRC = 2
> ... no report blocks
> 
> Ok probably RR
> SSRC = 3
> report block 1
> SSRC = 100
> ... report block data
> report block 2
> SSRC = 101
> ... report block data
> 
> now SDES ... ?
> 
> 
> Thanks
> 
> 
> Magnus Westerlund wrote:
>> Ivar skrev:
>>> Hi,
>>>
>>> RFC 3550 3. says that session may have multiple sending streams, but 
>>> all must have it's own SSRC.
>>>
>>> Now for example session is receiver and there are 2 sending streams, 
>>> how compound RTCP packet is composed ?
>>> Has 2 SR reports if both sender streams have sent data, has 1 SR if 
>>> only 1 stream sent data ? (each SR report has reported sender stream 
>>> SSRC)
>>
>> Each source needs to send its own RTCP compound packets with an SR for 
>> itself an containing reports on all the other sources it currently 
>> receives data from. To avoid throwing off any quality report user, 
>> also SSRCs co-located in the same host needs to include report blocks 
>> on each other.
>>
>>> And what SSRC is used for RR, if there are more than 31 remote 
>>> senders or no local RTP sent during last RTCP interval? 
>>
>> All senders or receivers have their own SSRC. That is always used as 
>> reporting the source of the RR. The content of the report block is 
>> round-robined in case there are more than 31 active sources.
>>
>> (generate local receiver SSRC for that ?)
>>
>> Not certain what you mean with this. But if you mean that a receiver 
>> that isn't sending media, it still needs to have an SSRC. Any sender 
>> or receiver do need to have an SSRC. The only one that can live 
>> without an SSRC is a completely passive receiver, i.e. do not send 
>> RTCP or RTP.
>>
>>
>>> Also how all this affects SDES, because there are more than 1 SSRC 
>>> for RTP session ?
>>
>> As each session participant sends its own compound packets they shall 
>> include the SDES CNAME item for themselves. In addition mixers may 
>> include SDES items from contributing sources.
>>
>>> (One of the SSRC will send all sdes items, other SSRCs only 
>>> CNAME(which will map SSRC to participant))
>>
>> Well this is allowed but doesn't make much sense. As the SDES item 
>> describe the indicated SSRC, and says nothing about the others. No 
>> assumption can really be made with the possible exception between 
>> different media streams and for the SSRCs in the different sessions 
>> that indicate the same CNAME value.
>>
>> Cheers
>>
>> Magnus Westerlund
>>
>> IETF Transport Area Director & TSVWG Chair
>> ----------------------------------------------------------------------
>> Multimedia Technologies, Ericsson Research EAB/TVM/M
>> ----------------------------------------------------------------------
>> Ericsson AB                | Phone +46 8 4048287
>> Torshamsgatan 23           | Fax   +46 8 7575550
>> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>> ----------------------------------------------------------------------
> 
> 


-- 

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
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 Jul 10 09:42:30 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8Fyu-0000If-5b; Tue, 10 Jul 2007 09:42:20 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8Fys-0000Bd-Js
	for avt@ietf.org; Tue, 10 Jul 2007 09:42:18 -0400
Received: from mgw3.sony.co.jp ([137.153.0.15])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8Fyr-0005gt-QZ
	for avt@ietf.org; Tue, 10 Jul 2007 09:42:18 -0400
Received: from mail5.sony.co.jp ([43.0.1.204])
Received: from mail5.sony.co.jp (localhost [127.0.0.1])
	by mail5.sony.co.jp (R8/Sony) with ESMTP id l6ADfpBs005233;
	Tue, 10 Jul 2007 22:41:51 +0900 (JST)
Received: from bourbon.sm.sony.co.jp ([43.13.14.16])
	by mail5.sony.co.jp (R8/Sony) with ESMTP id l6ADfpbd005229;
	Tue, 10 Jul 2007 22:41:51 +0900 (JST)
Received: from [43.11.236.90] ([43.11.236.90])
	by bourbon.sm.sony.co.jp (8.14.1/8.14.1) with ESMTP id l6AE3Sc8029151; 
	Tue, 10 Jul 2007 23:03:28 +0900
Message-ID: <46938C6E.1080404@sm.sony.co.jp>
Date: Tue, 10 Jul 2007 22:41:02 +0900
From: Satoshi Futemma <satosi-f@sm.sony.co.jp>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: Boudani Ali <Ali.Boudani@thomson.net>
Subject: Re: [AVT] Scalable Video (JPEG-2000 & SVC)
References: <7634542FB03DC747813D67560802AEEDB638F5@rennsmail05.eu.thmulti.com>
In-Reply-To: <7634542FB03DC747813D67560802AEEDB638F5@rennsmail05.eu.thmulti.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f884eb1d4ec5a230688d7edc526ea665
Cc: IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Dear Ali,

Boudani Ali wrote:
> 1- In the SVC draft that describes the RTP Payload Format for SVC Video,
> each RTP packet stream can carry NAL units belonging to one or more
> layers. 
> When multiple RTP packet streams are in use, they are session
> multiplexed and form their own RTP session and therefore have their own
> SSRC, PT, and Sequence numbering space. What about the timestamp (same
> sampling instant)? 

> Now, for the JPEG2K Codestream when transmitting layers in different RTP
> sessions, do we have the same timestamp for all these packets (because
> of the same sampling instant) and what about the sequence number? The
> multiple RTP packet streams in use are session multiplexed, do they have
> their own Sequence numbering space?.

In J2K codestream, same clock rate must be used
when one codestream is tranfered in multiple RTP sessions.

About sequence number, there is no no relations between rtp sessions,
so each rtp session follows its own numbering.

For example,
   RTP session 1: 3560 3561 3562 ...
   RTP session 2: 103  104  105 ...
   RTP session 3: 65538 65539 65540 ...

 > For example what would be the values for this JPEG2K Codestream?
 > +----------+----+----+----+----------+----+----+----+----------+----
 > |Tile 0 Hdr| L0 | L1 | L2 |Tile 1 Hdr| L0 | L1 | L2 |Tile 2 Hdr| ...
 > +----------+----+----+----+----------+----+----+----+----------+----
 > RTP session 1
 > +----------+----+         +----------+----+        +----------+----
 > |Tile 0 Hdr| L0 |         |Tile 1 Hdr| L0 |        |Tile 2 Hdr| L0
 > +----------+----+         +----------+----+        +----------+----
 > RTP session 2
 >                 +----+                    +----+
 >                 | L1 |                    | L1 |             ....
 >                 +----+                    +----+
 > RTP session 3
 >                      +----+                    +----+
 >                      | L2 |                    | L2 |        ....
 >                      +----+                    +----+

Best Regards,

Futemma

> 2- What about using a fragment offset with SVC? The SVC draft has also
> layers (like JPEG2K) but doesn't use any offset! In the other hand, the
> JPEG2K draft, says that a fragment offset value MUST be set to the byte
> offset of the current payload in relation to the very beginning of each
> JPEG 2000 codestream (JPEG 2000 frame). Is the "MUST" is the best
> keyword here. I may need it only if I am sending the different layers of
> the same codestream over multiple sessions. 
> 
> Thanks,
> Ali
> -----Original Message-----
> From: Satoshi Futemma [mailto:satosi-f@sm.sony.co.jp] 
> Sent: lundi 28 mai 2007 09:37
> To: Boudani Ali
> Cc: IETF AVT WG; Colin Perkins; Andrew Leung; ITAKURA Eisaburo
> Subject: Re: [AVT] Working group last call: JPEG-2000 payload format
> 
> Dear Ali,
> 
> Thank you for the comments.
> Please see inline.
> 
> Boudani Ali wrote:
>> Hello,
>> I read the two drafts. Before going to the IESG, It will be better if
>> the authors clarify some issues.
>> Here are my comments:
>>
>> 1- How can we identify the packets belonging to the same Codestream
>> (frame) (especially when using multiple RTP sessions). Don't you think
>> that we need to add a frame_id identifier?.
> 
> RTP timestamp can be used for that purpose.
> 
>> 2- In section 4.1 of Draft-ietf-avt-rtp-jpeg2000-15.txt: you consider
> 90
>> KHz for the Timestamp, this is not enough for professional video using
>> JPEG2K: isn't better to leave this to the implementers? 
> 
> RTP timestamp is a presentation timestamp.
> Same frame has same rtp timestamp and timestamp difference
> between frames is constant. Therefore 90KHz timestamp is enough.
> 
> How many clock rate would you consider for RTP timestamp ?
> If there is a strong incentive, I feel no reluctance to
> select different clock using rtpmap.
> 
>> 3- Adding a payload header is an overhead, so smaller payload header
>> size is better. Now, why do we need "T" and "tile number" fields? You
>> said that many tiles may exist in the same packet, so in this case no
>> meaning of "tile number" and "T" fields?
> 
> As you pointed, "tile number" and "T" may not be necessary when
> many tiles exists in the same packet, but if no tile header exists
> in a packet, which may be more possible, "tile number" and "T"
> is needed for receiver to clarify which tile the codestream
> is belonging to.
> 
>> 4- Is the tp (type) field necessary?. The RTP payload has already the
>> payload type (PT) and we can use it instead of tp? If not this
>> information can be communicated out of band and can be optional as the
>> width and height in section 8.1!
> 
> We believe it is necessary because the receiver identify whether
> the received codestream is odd or even field's.
> 
> "tp" can be used for determining the reciever's action.
> For example, if it receives odd field continuously, it can interpolate
> even field in some way, or simply discard the duplicated odd field.
> 
>> 5- Why do you use the fragment offset?. Isn't (for one RTP session)
> the
>> sequence number of the RTP packet enough? 
>> When using multiple RTP sessions for layered video, the parser that
>> extracted the data for a particular layer (for a particular RTP
> session)
>> may be transmitted out of band also (the index file is stored either
> as
>> a separate file or as meta-data). The index file is transmitted to the
>> receiver also, so the receiver can rebuild the codestream.
> 
> When using multiple RTP session for layered video,	
> JPEG2000 codestream may be split with interleaving.
> 
> For example,
> 
> Codestream
> +----------+----+----+----+----------+----+----+----+----------+----
> |Tile 0 Hdr| L0 | L1 | L2 |Tile 1 Hdr| L0 | L1 | L2 |Tile 2 Hdr| ...
> +----------+----+----+----+----------+----+----+----+----------+----
> 
> 
> RTP 1
> +----------+----+         +----------+----+        +----------+----
> |Tile 0 Hdr| L0 |         |Tile 1 Hdr| L0 |        |Tile 2 Hdr| L0
> +----------+----+         +----------+----+        +----------+----
> 
> RTP 2           +----+                    +----+
>                 | L1 |                    | L1 |             ....
>                 +----+                    +----+
> 
> RTP 3                +----+                    +----+
>                      | L2 |                    | L2 |        ....
>                      +----+                    +----+
> In that case,
> interleaved codestream doesn't alwasy arrive at the receiver
> in original order.
> Fragment offset helps the receiver to rebuild the codestream.
> 
> Also, if the fragment offset exist, the receiver need less
> memory because it doesn't need de-intgerleave buffer to
> rebuilt codestream. It can use same memory space to rebulit it.
> 
>> 6- Do we really need to have an MHD flag? The size of main header may
> be
>> about 300 bytes so is there any chance that this packet will be
>> fragmented?
> 
> Typical main header may be at most 300 bytes long, but if some JPEG2000
> coding options are used, it may be longer.
> So MHF flag is neccessary for such situation.
> 
>> 7- For the priority field use (the example in section 1.3.1): the
>> receiver can select which parts of the codestream to decode without
>> using the priority field. It can rebuild the codestream and extract
> the
>> parts to decode by reading the main header?. 
> 
> Main header contains the progression order information, but it doesn't
> include the address information (start position) of each priority level.
> 
> Priority field helps the receiver to select the codestream to put into
> decoder easily. Without priority field, the receives needs more memory
> to rebuild it and has to parse the codestream.
> 
> 
> Best Regards,
> 
> Futemma
> 
> 
>> Cheers,
>> Ali 
>> -----Original Message-----
>> From: Colin Perkins [mailto:csp@csperkins.org] 
>> Sent: lundi 14 mai 2007 13:59
>> To: IETF AVT WG
>> Cc: Roni Even; Tom-PT Taylor
>> Subject: [AVT] Working group last call: JPEG-2000 payload format
>>
>> This is to announce a working group last call on the RTP Payload  
>> Format for JPEG-2000:
>>
>> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-jpeg2000-15.txt
>> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-jpeg2000- 
>> beam-06.txt
>>
>> Please send any final comments on these drafts to the <avt@ietf.org>  
>> mailing list by 28 May 2007. If no substantive comments are received  
>> by that time, we will ask the IESG to consider these drafts for  
>> publication as Proposed Standard RFCs.
>>
>> Note that there is declared IPR on the "beam" draft:
>> https://datatracker.ietf.org/public/ipr_detail_show.cgi?ipr_id=697
>>
> 
> _______________________________________________
> 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 Jul 10 12:14:22 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8IM0-0006Kv-2l; Tue, 10 Jul 2007 12:14:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8ILy-0006J5-If
	for avt@ietf.org; Tue, 10 Jul 2007 12:14:18 -0400
Received: from dmzraw4.extranet.thmulti.com ([141.11.234.72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8ILx-0001O3-OI
	for avt@ietf.org; Tue, 10 Jul 2007 12:14:18 -0400
Received: from boulvss2.eu.thmulti.com (proxy.thmulti.com [141.11.234.62])
	by dmzraw4.extranet.thmulti.com (Postfix) with ESMTP id 8C3A3243C;
	Tue, 10 Jul 2007 16:14:03 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
	by boulvss2.eu.thmulti.com (Postfix) with ESMTP id DE87B1215;
	Tue, 10 Jul 2007 16:21:52 +0000 (GMT)
Received: from boulvss2.eu.thmulti.com ([127.0.0.1])
	by localhost (boulvss2.eu.thmulti.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with LMTP id 08469-03-41; Tue, 10 Jul 2007 16:21:43 +0000 (GMT)
Received: from boulsmailfe02.eu.thmulti.com (boulasmtp.eu.thmulti.com
	[141.11.196.14])
	by boulvss2.eu.thmulti.com (Postfix) with ESMTP id 8DDC011EB;
	Tue, 10 Jul 2007 16:21:43 +0000 (GMT)
Received: from rennsmail05.eu.thmulti.com ([141.11.159.141]) by
	boulsmailfe02.eu.thmulti.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 10 Jul 2007 18:13:54 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] Scalable Video (JPEG-2000 & SVC)
Date: Tue, 10 Jul 2007 18:13:33 +0200
Message-ID: <7634542FB03DC747813D67560802AEEDB63CC6@rennsmail05.eu.thmulti.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Scalable Video (JPEG-2000 & SVC)
Thread-Index: AcfC+BunFDeJQyMNRWupL1Jz/h3suAACt0zQ
From: "Boudani Ali" <Ali.Boudani@thomson.net>
To: "Satoshi Futemma" <satosi-f@sm.sony.co.jp>
X-OriginalArrivalTime: 10 Jul 2007 16:13:54.0110 (UTC)
	FILETIME=[4F9E15E0:01C7C30D]
X-Virus-Scanned: amavisd-new at thomson.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 578c2c9d0cb01ffe6e1ca36540edd070
Cc: IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Dear Futemma,
Thanks for the clarification. What about the offset?
1- Is putting an offset in the payload header is a "MUST". Is it the
best keyword? I may need the offset only if I am sending the different
layers of the same Codestream over multiple sessions. But, if I am
sending all the layers within the same session (which is IMHO the main
common use of JPEG2K over RTP), sequence number is enough. So is it
possible to put "all bits zero" (in the fragment offset field) and use
only the sequence number in that case?.=20
It may be useful then you put a bit to tell if the offset is used or
not.

2- What would be the media representation in SDP when sending over
multiple RTP sessions? Can you include an example in the draft about
this please?

Regards,
Ali

-----Original Message-----
From: Satoshi Futemma [mailto:satosi-f@sm.sony.co.jp]=20
Sent: mardi 10 juillet 2007 15:41
To: Boudani Ali
Cc: IETF AVT WG
Subject: Re: [AVT] Scalable Video (JPEG-2000 & SVC)

Dear Ali,

Boudani Ali wrote:
> 1- In the SVC draft that describes the RTP Payload Format for SVC
Video,
> each RTP packet stream can carry NAL units belonging to one or more
> layers.=20
> When multiple RTP packet streams are in use, they are session
> multiplexed and form their own RTP session and therefore have their
own
> SSRC, PT, and Sequence numbering space. What about the timestamp (same
> sampling instant)?=20

> Now, for the JPEG2K Codestream when transmitting layers in different
RTP
> sessions, do we have the same timestamp for all these packets (because
> of the same sampling instant) and what about the sequence number? The
> multiple RTP packet streams in use are session multiplexed, do they
have
> their own Sequence numbering space?.

In J2K codestream, same clock rate must be used
when one codestream is tranfered in multiple RTP sessions.

About sequence number, there is no no relations between rtp sessions,
so each rtp session follows its own numbering.

For example,
   RTP session 1: 3560 3561 3562 ...
   RTP session 2: 103  104  105 ...
   RTP session 3: 65538 65539 65540 ...

 > For example what would be the values for this JPEG2K Codestream?
 > +----------+----+----+----+----------+----+----+----+----------+----
 > |Tile 0 Hdr| L0 | L1 | L2 |Tile 1 Hdr| L0 | L1 | L2 |Tile 2 Hdr| ...
 > +----------+----+----+----+----------+----+----+----+----------+----
 > RTP session 1
 > +----------+----+         +----------+----+        +----------+----
 > |Tile 0 Hdr| L0 |         |Tile 1 Hdr| L0 |        |Tile 2 Hdr| L0
 > +----------+----+         +----------+----+        +----------+----
 > RTP session 2
 >                 +----+                    +----+
 >                 | L1 |                    | L1 |             ....
 >                 +----+                    +----+
 > RTP session 3
 >                      +----+                    +----+
 >                      | L2 |                    | L2 |        ....
 >                      +----+                    +----+

Best Regards,

Futemma

> 2- What about using a fragment offset with SVC? The SVC draft has also
> layers (like JPEG2K) but doesn't use any offset! In the other hand,
the
> JPEG2K draft, says that a fragment offset value MUST be set to the
byte
> offset of the current payload in relation to the very beginning of
each
> JPEG 2000 codestream (JPEG 2000 frame). Is the "MUST" is the best
> keyword here. I may need it only if I am sending the different layers
of
> the same codestream over multiple sessions.=20
>=20
> Thanks,
> Ali
> -----Original Message-----
> From: Satoshi Futemma [mailto:satosi-f@sm.sony.co.jp]=20
> Sent: lundi 28 mai 2007 09:37
> To: Boudani Ali
> Cc: IETF AVT WG; Colin Perkins; Andrew Leung; ITAKURA Eisaburo
> Subject: Re: [AVT] Working group last call: JPEG-2000 payload format
>=20
> Dear Ali,
>=20
> Thank you for the comments.
> Please see inline.
>=20
> Boudani Ali wrote:
>> Hello,
>> I read the two drafts. Before going to the IESG, It will be better if
>> the authors clarify some issues.
>> Here are my comments:
>>
>> 1- How can we identify the packets belonging to the same Codestream
>> (frame) (especially when using multiple RTP sessions). Don't you
think
>> that we need to add a frame_id identifier?.
>=20
> RTP timestamp can be used for that purpose.
>=20
>> 2- In section 4.1 of Draft-ietf-avt-rtp-jpeg2000-15.txt: you consider
> 90
>> KHz for the Timestamp, this is not enough for professional video
using
>> JPEG2K: isn't better to leave this to the implementers?=20
>=20
> RTP timestamp is a presentation timestamp.
> Same frame has same rtp timestamp and timestamp difference
> between frames is constant. Therefore 90KHz timestamp is enough.
>=20
> How many clock rate would you consider for RTP timestamp ?
> If there is a strong incentive, I feel no reluctance to
> select different clock using rtpmap.
>=20
>> 3- Adding a payload header is an overhead, so smaller payload header
>> size is better. Now, why do we need "T" and "tile number" fields? You
>> said that many tiles may exist in the same packet, so in this case no
>> meaning of "tile number" and "T" fields?
>=20
> As you pointed, "tile number" and "T" may not be necessary when
> many tiles exists in the same packet, but if no tile header exists
> in a packet, which may be more possible, "tile number" and "T"
> is needed for receiver to clarify which tile the codestream
> is belonging to.
>=20
>> 4- Is the tp (type) field necessary?. The RTP payload has already the
>> payload type (PT) and we can use it instead of tp? If not this
>> information can be communicated out of band and can be optional as
the
>> width and height in section 8.1!
>=20
> We believe it is necessary because the receiver identify whether
> the received codestream is odd or even field's.
>=20
> "tp" can be used for determining the reciever's action.
> For example, if it receives odd field continuously, it can interpolate
> even field in some way, or simply discard the duplicated odd field.
>=20
>> 5- Why do you use the fragment offset?. Isn't (for one RTP session)
> the
>> sequence number of the RTP packet enough?=20
>> When using multiple RTP sessions for layered video, the parser that
>> extracted the data for a particular layer (for a particular RTP
> session)
>> may be transmitted out of band also (the index file is stored either
> as
>> a separate file or as meta-data). The index file is transmitted to
the
>> receiver also, so the receiver can rebuild the codestream.
>=20
> When using multiple RTP session for layered video,=09
> JPEG2000 codestream may be split with interleaving.
>=20
> For example,
>=20
> Codestream
> +----------+----+----+----+----------+----+----+----+----------+----
> |Tile 0 Hdr| L0 | L1 | L2 |Tile 1 Hdr| L0 | L1 | L2 |Tile 2 Hdr| ...
> +----------+----+----+----+----------+----+----+----+----------+----
>=20
>=20
> RTP 1
> +----------+----+         +----------+----+        +----------+----
> |Tile 0 Hdr| L0 |         |Tile 1 Hdr| L0 |        |Tile 2 Hdr| L0
> +----------+----+         +----------+----+        +----------+----
>=20
> RTP 2           +----+                    +----+
>                 | L1 |                    | L1 |             ....
>                 +----+                    +----+
>=20
> RTP 3                +----+                    +----+
>                      | L2 |                    | L2 |        ....
>                      +----+                    +----+
> In that case,
> interleaved codestream doesn't alwasy arrive at the receiver
> in original order.
> Fragment offset helps the receiver to rebuild the codestream.
>=20
> Also, if the fragment offset exist, the receiver need less
> memory because it doesn't need de-intgerleave buffer to
> rebuilt codestream. It can use same memory space to rebulit it.
>=20
>> 6- Do we really need to have an MHD flag? The size of main header may
> be
>> about 300 bytes so is there any chance that this packet will be
>> fragmented?
>=20
> Typical main header may be at most 300 bytes long, but if some
JPEG2000
> coding options are used, it may be longer.
> So MHF flag is neccessary for such situation.
>=20
>> 7- For the priority field use (the example in section 1.3.1): the
>> receiver can select which parts of the codestream to decode without
>> using the priority field. It can rebuild the codestream and extract
> the
>> parts to decode by reading the main header?.=20
>=20
> Main header contains the progression order information, but it doesn't
> include the address information (start position) of each priority
level.
>=20
> Priority field helps the receiver to select the codestream to put into
> decoder easily. Without priority field, the receives needs more memory
> to rebuild it and has to parse the codestream.
>=20
>=20
> Best Regards,
>=20
> Futemma
>=20
>=20
>> Cheers,
>> Ali=20
>> -----Original Message-----
>> From: Colin Perkins [mailto:csp@csperkins.org]=20
>> Sent: lundi 14 mai 2007 13:59
>> To: IETF AVT WG
>> Cc: Roni Even; Tom-PT Taylor
>> Subject: [AVT] Working group last call: JPEG-2000 payload format
>>
>> This is to announce a working group last call on the RTP Payload =20
>> Format for JPEG-2000:
>>
>>
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-jpeg2000-15.txt
>> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-jpeg2000-=20
>> beam-06.txt
>>
>> Please send any final comments on these drafts to the <avt@ietf.org>

>> mailing list by 28 May 2007. If no substantive comments are received

>> by that time, we will ask the IESG to consider these drafts for =20
>> publication as Proposed Standard RFCs.
>>
>> Note that there is declared IPR on the "beam" draft:
>> https://datatracker.ietf.org/public/ipr_detail_show.cgi?ipr_id=3D697
>>
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>=20
>=20
>=20

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



From avt-bounces@ietf.org Tue Jul 10 13:15:09 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8JIm-00039D-3X; Tue, 10 Jul 2007 13:15:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8JIk-00038B-L6; Tue, 10 Jul 2007 13:15:02 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I8JIk-000395-ER; Tue, 10 Jul 2007 13:15:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 662DD329BE;
	Tue, 10 Jul 2007 17:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I8JIk-0006Cs-6P; Tue, 10 Jul 2007 13:15:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I8JIk-0006Cs-6P@stiedprstage1.ietf.org>
Date: Tue, 10 Jul 2007 13:15:02 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-tfrc-profile-09.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: RTP with TCP Friendly Rate Control
	Author(s)	: L. Gharai
	Filename	: draft-ietf-avt-tfrc-profile-09.txt
	Pages		: 11
	Date		: 2007-7-10
	
This memo specifies how the TCP Friendly Rate Control (TFRC) of RTP
   flows can be supported using the RTP/AVPF profile and the general RTP
   header extension mechanism.  AVPF feedback packets and RTP header
   extensions are defined to support the exchange of control information
   between RTP TFRC senders and receivers. TFRC is an equation-based
   congestion control scheme for unicast flows operating in a best
   effort Internet environment.

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

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

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

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

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

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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-tfrc-profile-09.txt

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

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


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org Tue Jul 10 14:49:16 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8Klb-0005m5-ON; Tue, 10 Jul 2007 14:48:55 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8Kla-0005kZ-E2; Tue, 10 Jul 2007 14:48:54 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I8KlR-0006AG-JC; Tue, 10 Jul 2007 14:48:54 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 3F6AD2ACB8;
	Tue, 10 Jul 2007 18:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I8KEn-0000Wh-Un; Tue, 10 Jul 2007 14:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I8KEn-0000Wh-Un@stiedprstage1.ietf.org>
Date: Tue, 10 Jul 2007 14:15:01 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtcphr-01.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

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

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcphr-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-rtcphr-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-rtcphr-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: <2007-7-10132145.I-D@ietf.org>

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

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

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


--OtherAccess--

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

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

--NextPart--




From avt-bounces@ietf.org Wed Jul 11 03:49:26 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8Wwq-0004yZ-UN; Wed, 11 Jul 2007 03:49:20 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8Wwp-0004yD-AG
	for avt@ietf.org; Wed, 11 Jul 2007 03:49:19 -0400
Received: from mgw4.sony.co.jp ([137.153.0.46])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8WwZ-0000YW-Ly
	for avt@ietf.org; Wed, 11 Jul 2007 03:49:19 -0400
Received: from mail3.sony.co.jp ([43.0.1.203])
Received: from mail3.sony.co.jp (localhost [127.0.0.1])
	by mail3.sony.co.jp (R8/Sony) with ESMTP id l6B7mWJ1013451;
	Wed, 11 Jul 2007 16:48:32 +0900 (JST)
Received: from bourbon.sm.sony.co.jp ([43.13.14.16])
	by mail3.sony.co.jp (R8/Sony) with ESMTP id l6B7mVqF013435;
	Wed, 11 Jul 2007 16:48:31 +0900 (JST)
Received: from [43.11.236.90] ([43.11.236.90])
	by bourbon.sm.sony.co.jp (8.14.1/8.14.1) with ESMTP id l6B8ABlR031299; 
	Wed, 11 Jul 2007 17:10:11 +0900
Message-ID: <46948B1C.9090000@sm.sony.co.jp>
Date: Wed, 11 Jul 2007 16:47:40 +0900
From: Satoshi Futemma <satosi-f@sm.sony.co.jp>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: Boudani Ali <Ali.Boudani@thomson.net>
Subject: Re: [AVT] Scalable Video (JPEG-2000 & SVC)
References: <7634542FB03DC747813D67560802AEEDB63CC6@rennsmail05.eu.thmulti.com>
In-Reply-To: <7634542FB03DC747813D67560802AEEDB63CC6@rennsmail05.eu.thmulti.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: IETF AVT WG <avt@ietf.org>, Andrew Leung <andrew@ualberta.net>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Dear Ali,

Thank you for the useful comment.

Boudani Ali wrote:
> 1- Is putting an offset in the payload header is a "MUST". Is it the
> best keyword? I may need the offset only if I am sending the different
> layers of the same Codestream over multiple sessions. But, if I am
> sending all the layers within the same session (which is IMHO the main
> common use of JPEG2K over RTP), sequence number is enough. So is it
> possible to put "all bits zero" (in the fragment offset field) and use
> only the sequence number in that case?. 
> It may be useful then you put a bit to tell if the offset is used or
> not.

Yes.

If you send whole codestream in one RTP session,
it may be possible to rebuild the codestream by checking RTP
sequence.

But as I wrote:
 > interleaved codestream doesn't alwasy arrive at the receiver
 > in original order.
 > Fragment offset helps the receiver to rebuild the codestream.

When the j2k codestream is sent in multiple RTP sessions,
the offset is necessary.

> 2- What would be the media representation in SDP when sending over
> multiple RTP sessions? Can you include an example in the draft about
> this please?

If you want to use two RTP session, which is not unique to JPEG 2000,
you can set SDP parameters in accordance with RFC 4566 "SDP: Session
Decription Protocol" as follow:

   m=video 49170/2 RTP/AVP 98
   a=rtpmap:98 jpeg2000/90000
   a=fmtp:98 ...


Best Regards,


Satoshi Futemma



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



From avt-bounces@ietf.org Wed Jul 11 09:18:10 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8c4b-0006tS-K4; Wed, 11 Jul 2007 09:17:41 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8c4a-0006tG-77
	for avt@ietf.org; Wed, 11 Jul 2007 09:17:40 -0400
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=bemg01.siemenscomms.co.uk)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8c4K-0008PM-KQ
	for avt@ietf.org; Wed, 11 Jul 2007 09:17:40 -0400
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JL000M7YNJLRO@siemenscomms.co.uk> for avt@ietf.org; Wed,
	11 Jul 2007 14:16:33 +0100 (BST)
Date: Wed, 11 Jul 2007 14:16:46 +0100
From: "Elwell, John" <john.elwell@siemens.com>
To: avt@ietf.org, mcgrew@cisco.com, ekr@networkresonance.com
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D020567F@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-Topic: Comments on draft-ietf-avt-dtls-srtp-00
Thread-Index: AcfDvbszOPh1dDOyQm+RYgqvaUuL3w==
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: 
Subject: [AVT] Comments on draft-ietf-avt-dtls-srtp-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

1. Obviously the ideal situation is that symmetric RTP and multiplexed
RTP/RTCP are used, in which case only a single DTLS-SRTP is needed per
medium. Symmetric RTP is, I think, quite common now, but multiplexed
RTP/RTCP is not. I guess anyone implementing DTLS-SRTP could implement
multiplexed RTP/RTCP at the same time. However, I am curious to know why
it is necessary to have two DTLS-SRTP sessions when RTP and RTCP are on
different ports.

2. "In order to negotiate the use of SRTP data protection, clients MAY
   include an extension of type "use_srtp" in the extended client
hello."
Shouldn't the "MAY" be a "MUST", i.e., how can it be negotiated without
including this extension?

3. "Once the "use_srtp" extension is negotiated, packets of type
   "application_data" in the newly negotiated association (i.e., after
   the change_cipher_spec) MUST be protected using SRTP and packets of
   type "application_data" MUST NOT be sent."
This seems to be contradictory - it first says how to send such packets
and then says you must not send them. Is the latter half of the sentence
supposed to say that they must not use ordinary DTLS framing?

4. Figure 6 has a line missing - SRTP is shown only in one direction
(yet SRTCP is shown in both directions).

John

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



From avt-bounces@ietf.org Thu Jul 12 03:16:46 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8sum-0000AQ-E7; Thu, 12 Jul 2007 03:16:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8suk-0000AL-Qm
	for avt@ietf.org; Thu, 12 Jul 2007 03:16:38 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8sug-0001IX-6X
	for avt@ietf.org; Thu, 12 Jul 2007 03:16:38 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	7C0C5203C2 for <avt@ietf.org>; Thu, 12 Jul 2007 09:16:33 +0200 (CEST)
X-AuditID: c1b4fb3e-b2038bb0000007e1-cd-4695d5517f2b
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	52FE82115D for <avt@ietf.org>; Thu, 12 Jul 2007 09:16:33 +0200 (CEST)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Jul 2007 09:16:32 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 12 Jul 2007 09:14:53 +0200
Message-ID: <026F8EEDAD2C4342A993203088C1FC0505545A81@esealmw109.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Non-compound RTCP
Thread-Index: AcfEVFfZQNHUXnHkRlSHu/I2N3EHvg==
From: "Ingemar Johansson S (LU/EAB)" <ingemar.s.johansson@ericsson.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 12 Jul 2007 07:16:32.0824 (UTC)
	FILETIME=[9323C380:01C7C454]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: "Ingemar Johansson S \(LU/EAB\)" <ingemar.s.johansson@ericsson.com>
Subject: [AVT] Non-compound RTCP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi

This is to announce that the ID
draft-johansson-avt-rtcp-avpf-non-compound
Has been updated, the direct link is
http://tools.ietf.org/wg/avt/draft-johansson-avt-rtcp-avpf-non-compound-0=
2.txt
Since the last update Non-compound RTCP has been adopted by 3GPP, more =
specific details are found in ch. 1.=20
An outline for an algorithm that controls the use of Non-compound RTCP =
is given in ch. 5.1.

Regards
Ingemar


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

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



From avt-bounces@ietf.org Thu Jul 12 12:16:50 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I91LR-0005yA-Pp; Thu, 12 Jul 2007 12:16:46 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I91K7-0003Sf-Jm; Thu, 12 Jul 2007 12:15:23 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I91K7-0005j7-At; Thu, 12 Jul 2007 12:15:23 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 321112AC81;
	Thu, 12 Jul 2007 16:15:13 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I91Jw-0003GI-3D; Thu, 12 Jul 2007 12:15:12 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I91Jw-0003GI-3D@stiedprstage1.ietf.org>
Date: Thu, 12 Jul 2007 12:15:12 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-svc-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>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: RTP Payload Format for SVC Video
	Author(s)	: S. Wenger, et al.
	Filename	: draft-ietf-avt-rtp-svc-02.txt
	Pages		: 0
	Date		: 2007-7-12
	
This memo describes an RTP payload format for the scalable extension
   of the ITU-T Recommendation H.264 video codec which is technically
   identical to ISO/IEC International Standard 14496-10.  The RTP
   payload format allows for packetization of one or more Network
   Abstraction Layer (NAL) units, produced by the video encoder, in
   each RTP payload.  The payload format has wide applicability, such
   as low bit-rate conversational, Internet video streaming, or high
   bit-rate entertainment quality video.

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

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

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

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


--OtherAccess--

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

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

--NextPart--




From avt-bounces@ietf.org Fri Jul 13 01:08:49 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I9DOK-0006QB-QM; Fri, 13 Jul 2007 01:08:32 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I9DOJ-0006Pu-5g
	for avt@ietf.org; Fri, 13 Jul 2007 01:08:31 -0400
Received: from mail.tataelxsi.co.in ([203.200.1.48])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I9DO2-00041S-Rp
	for avt@ietf.org; Fri, 13 Jul 2007 01:08:31 -0400
Received: from vinodjoshi (59.160.207.5.ill-bgl.static.vsnl.net.in
	[59.160.207.5] (may be forged))
	by mail.tataelxsi.co.in (MOS 3.8.4-GA)
	with ESMTP id ABH49103 (AUTH vinodjoshi);
	Fri, 13 Jul 2007 10:37:39 +0530 (IST)
From: Vinod Madhav Joshi <vinodjoshi@tataelxsi.co.in>
To: <avt@ietf.org>
Date: Fri, 13 Jul 2007 10:39:21 +0530
Message-ID: <002701c7c50b$f9db00e0$022a320a@telxsi.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 CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Junkmail-Status: score=10/50, host=mail.tataelxsi.co.in
X-Junkmail-SD-Raw: score=unknown,
	refid=str=0001.0A090209.4697089B.00FD,ss=1,fgs=0,
	ip=59.160.207.5, so=2007-03-13 10:31:19,
	dmn=5.3.14/2007-05-31
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Subject: [AVT] Synchronisation of Audio and Video
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi all,

   We are receiving MPEG2 demuxed elementary audio and video streams
   from streaming server on the set top box.
   The source for audio and video is the same.
   I want to know how to synchronise this audio and video data using
   RTP timestamps.
   Timestamp does not increase monitonically as the data was sampled.
   So how to generate Presentation Timestamps for audio and video?
   

   Please help me.
   

   Thank You.
  

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



From avt-bounces@ietf.org Sat Jul 14 15:18:51 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I9n8a-0004DL-3y; Sat, 14 Jul 2007 15:18:40 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I9n8Y-0004DC-Od
	for avt@ietf.org; Sat, 14 Jul 2007 15:18:38 -0400
Received: from mail5.audiocodes.com ([212.25.125.21] helo=imss.audiocodes.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I9n8Y-0000h3-2a
	for avt@ietf.org; Sat, 14 Jul 2007 15:18:38 -0400
Received: from aclcas.corp.audiocodes.com ([10.1.0.13]) by imss with InterScan
	Messaging Security Suite; Sat, 14 Jul 2007 21:27:29 +0200
Received: from aclmailbox.corp.audiocodes.com ([10.1.1.48]) by
	aclcas.corp.audiocodes.com ([10.1.0.13]) with mapi;
	Sat, 14 Jul 2007 22:18:18 +0300
From: Amit Yedidia <Amit.Yedidia@audiocodes.com>
To: "avt@ietf.org" <avt@ietf.org>
Date: Sat, 14 Jul 2007 22:18:17 +0300
Thread-Topic: avt Digest, Vol 39, Issue 20
Thread-Index: AcfFZxIZm7ptLbIzRmmeBpoCUhqZIQA4Rt4W
Message-ID: <C7507220AA34614FB456FA5EA7D8AE2E09A4B8EA@aclmailbox.corp.audiocodes.com>
References: <E1I9NZ4-0006l8-4K@megatron.ietf.org>
In-Reply-To: <E1I9NZ4-0006l8-4K@megatron.ietf.org>
Accept-Language: en-US
Content-Language: he-IL
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92
Subject: [AVT] =?windows-1255?q?=FE=FERE=3A_avt_Digest=2C_Vol_39=2C_Issue?=
	=?windows-1255?q?_20?=
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

There are basicly two methods. one with RTCP and the one without.
1. without RTCP - you must assume that the two streams (audio and video) we=
re started at the same time.
now for example we are using MPEG4 (90khz) for video and AMR-NB (8Khz).
lets mark the first Video RTP timestamp as RTPv_base and the first Audio RT=
P timestamp as RTPa_base.
for every video rtp packet ( i ) that arrived its presentation time in msec=
 is:
Tvid =3D (RTPv_i -RTPv_base)/90
and the same for audio:
Taud =3D (RTPa_i -RTPa_base)/8
2. when you have RTCP on both streams you can get an additional info on bot=
h strems in the sender report, which allow you to sync the streams even if =
they not started in the same time.
for each streams you get a timestamp and an NTP timestamp. The NTP timestam=
p is common (from the same source) to both streams, so yo can make adjustme=
nts.
diff =3D (NTPaud_rtcp-NTPvid_rtcp) - (RTPaud_rtcp/8 -RTPvid_rtcp/90)

Tvid =3D (RTPv_i -RTPv_base)/90
Taud =3D (RTPa_i -RTPa_base)/8 - diff

hope it helps

Amit Yeidida
AudioCodes Ltd.




________________________________________
=FE=FE=EE=E0=FA: avt-request@ietf.org [avt-request@ietf.org]
=FE=FE=F0=F9=EC=E7: =FE=FE=E9=E5=ED =F9=E9=F9=E9 13 =E9=E5=EC=E9 2007 19:00
=FE=FE=E0=EC: avt@ietf.org
=FE=FE=F0=E5=F9=E0: avt Digest, Vol 39, Issue 20

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-svc-02.txt
      (Internet-Drafts@ietf.org)
   2. Synchronisation of Audio and Video (Vinod Madhav Joshi)


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

Message: 1
Date: Thu, 12 Jul 2007 12:15:12 -0400
From: Internet-Drafts@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-svc-02.txt
To: i-d-announce@ietf.org
Cc: avt@ietf.org
Message-ID: <E1I91Jw-0003GI-3D@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=3D"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 Format for SVC Video
        Author(s)       : S. Wenger, et al.
        Filename        : draft-ietf-avt-rtp-svc-02.txt
        Pages           : 0
        Date            : 2007-7-12

This memo describes an RTP payload format for the scalable extension
   of the ITU-T Recommendation H.264 video codec which is technically
   identical to ISO/IEC International Standard 14496-10.  The RTP
   payload format allows for packetization of one or more Network
   Abstraction Layer (NAL) units, produced by the video encoder, in
   each RTP payload.  The payload format has wide applicability, such
   as low bit-rate conversational, Internet video streaming, or high
   bit-rate entertainment quality video.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-svc-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-svc-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-svc-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 reader=
s
        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: 2
Date: Fri, 13 Jul 2007 10:39:21 +0530
From: Vinod Madhav Joshi <vinodjoshi@tataelxsi.co.in>
Subject: [AVT] Synchronisation of Audio and Video
To: <avt@ietf.org>
Message-ID: <002701c7c50b$f9db00e0$022a320a@telxsi.com>
Content-Type: text/plain;       charset=3D"iso-8859-1"

Hi all,

   We are receiving MPEG2 demuxed elementary audio and video streams
   from streaming server on the set top box.
   The source for audio and video is the same.
   I want to know how to synchronise this audio and video data using
   RTP timestamps.
   Timestamp does not increase monitonically as the data was sampled.
   So how to generate Presentation Timestamps for audio and video?


   Please help me.


   Thank You.




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

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


End of avt Digest, Vol 39, Issue 20
***********************************

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



From avt-bounces@ietf.org Sun Jul 15 03:00:11 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I9y59-0000QN-Tk; Sun, 15 Jul 2007 02:59:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I9y58-0000QF-F3
	for avt@ietf.org; Sun, 15 Jul 2007 02:59:50 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I9y54-0006mk-38
	for avt@ietf.org; Sun, 15 Jul 2007 02:59:50 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 15 Jul 2007 10:00:46 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04B90337@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Updated AVT agenda for Chicago meeting
Thread-Index: AcfGrd5dounzlFwBTNKCXvoaeJp63w==
From: "Even, Roni" <roni.even@polycom.co.il>
To: <avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Cc: Colin Perkins <csp@csperkins.org>, tom.taylor@rogers.com
Subject: [AVT] Updated AVT agenda for Chicago meeting
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi,
I hope this is the final revision.

http://www3.ietf.org/proceedings/07jul/agenda/avt.html


Regards

Roni Even


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



From avt-bounces@ietf.org Mon Jul 16 06:16:59 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IANdH-00039h-Jp; Mon, 16 Jul 2007 06:16:47 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IANdF-00037U-PT
	for avt@ietf.org; Mon, 16 Jul 2007 06:16:45 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IANdF-0000ds-De
	for avt@ietf.org; Mon, 16 Jul 2007 06:16:45 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 16 Jul 2007 13:16:54 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04C22875@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Agenda for Chicago text version
Thread-Index: AcfHkm8QSIWbkN07Rg6L1LgUEgJspA==
From: "Even, Roni" <roni.even@polycom.co.il>
To: <avt@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Subject: [AVT] Agenda for Chicago text version
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi,
This is the same agenda.

http://www3.ietf.org/proceedings/07jul/agenda/avt.html




Audio/Video Transport (AVT) Working Group
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

CHAIRS:  Colin Perkins     <csp@csperkins.org>
         Tom Taylor        <taylor@nortel.com>
         Roni Even         <roni.even@polycom.co.il>

AGENDA

Monday, 23 July 2007 at 15:20-17:20 (State Ballroom)
----------------------------------------------------
15:20   Introduction and Status Update                      (Chairs, 15)

15:35   DTLS Extension to Establish Keys for SRTP          (McGrew , 15)
        draft-ietf-avt-dtls-srtp-00

15:50   Video Metrics Report Blocks                          (Clark, 10)
        draft-ietf-avt-rtcpxr-video-01

16:00   Report Block for IPTV Metrics                       (Kaynam, 10)
        draft-venna-avt-rtcpxr-iptv-01=20

16:10   Audio Metrics Report Block                           (Clark, 10)
        draft-ietf-avt-rtcpxr-audio-00

16:20   H.264 Payload optional parameters              (Kristensen , 15)
        draf-ietf-avt-rtp-h264-params-00

16:35   Non-Compound RTCP Packets                        (Johansson, 25)
        draft-johansson-avt-rtcp-avpf-non-compound-02

17:00   End



Thursday, 26 July 2007 at 15:10-16:10 (Red Lacquar)
---------------------------------------------------
15:10   RTP keepalive                                       (Marjou, 10)
        draft-ietf-avt-app-rtp-keepalive-00

15:20   RTP Payload Format for SVC Video                   (Schierl, 15)
        draft-ietf-avt-rtp-svc-02

15:35   Source-Specific Media Attributes                     (Lennox, 5)
        draft-lennox-mmusic-sdp-source-attributes-01

15:40   High Resolution VoIP Metrics                         (Clark, 10)
        draft-ietf-avt-rtcphr-01

15:50   Using SEED Cipher Algorithm with SRTP              (Seokung, 10)

16:00   End


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



From avt-bounces@ietf.org Mon Jul 16 21:24:48 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAbn5-0003eZ-KI; Mon, 16 Jul 2007 21:23:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAbmy-0003Ut-DQ; Mon, 16 Jul 2007 21:23:44 -0400
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.43)
	id 1IAbmt-0000YJ-W2; Mon, 16 Jul 2007 21:23:44 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 16 Jul 2007 18:23:39 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CANO2m0arR7O6/2dsb2JhbAA
X-IronPort-AV: i="4.16,544,1175497200"; 
	d="scan'208"; a="503820034:sNHT29354616"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6H1Nc7k013165; 
	Mon, 16 Jul 2007 18:23:38 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l6H1NcTb021446;
	Tue, 17 Jul 2007 01:23:38 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 16 Jul 2007 18:23:38 -0700
Received: from [10.32.241.147] ([10.32.241.147]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 16 Jul 2007 18:23:38 -0700
Message-ID: <469C1A1F.2090102@cisco.com>
Date: Mon, 16 Jul 2007 21:23:43 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: IETF SIP List <sip@ietf.org>, IETF Sipping List <sipping@ietf.org>,
	IETF MMUSIC WG <mmusic@ietf.org>, Behave WG <behave@ietf.org>,
	P2PSIP WG <p2psip@ietf.org>, rai@ietf.org, "'avt@ietf.org'" <avt@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 17 Jul 2007 01:23:38.0346 (UTC)
	FILETIME=[1A3B94A0:01C7C811]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1845; t=1184635418;
	x=1185499418; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20ICE=20tutorial=20in=20Chicago=20[DO=20NOT=20REPLY]=20-=20PLEA
	SE=20ADVISE=20IF=20YOU=20WILL=0A=20ATTEND! |Sender:=20;
	bh=2mEMezIhgSd4fQtdetbfRv0w1jcLg1hf4bgHjST7IQc=;
	b=E8JzvIKOXdm/coVCa8PMIpZSSHcW1xP7WCAHJJydd1KTAo4rHvwnnmQbFu0sgmYA2MXhXiTZ
	5mrrLKb6+K2doFKdUhVSQSvfLQ1cG+MRM5jN63ABURvqDhDJUyb32NZD;
Authentication-Results: sj-dkim-2; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: 
Subject: [AVT] ICE tutorial in Chicago [DO NOT REPLY] - PLEASE ADVISE IF YOU
 WILL ATTEND!
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

I've gotten very few responses indicating interest. If I don't get more 
acceptances I'll have to cancel. Please, if you do plan on attending, 
send me mail per the instructions below if you have not done so.


(Apologies to multiple recipients)
(DO NOT REPLY)

WHAT:     Tutorial on Interactive Connectivity Establishment (ICE)
       (http://www.ietf.org/internet-drafts/draft-ietf-mmusic-ice-16.txt)
           [-17 should be available shortly]

WHEN:     Tuesday, July 24, 2007, 1145-1245
           (lunch logistics are in progress and will be announced ASAP)

WHERE:    Red Lacquar

WHO:      Anyone that would like to learn more about ICE.

WHY:      ICE, developed by the mmusic working group, has been
           defined as the IETF tool for NAT traversal for SIP-based
           media. It is also seeing increased usage for traversal
           for other kinds of application traffic - anything worrying
           about any-to-any communications. In this tutorial, we will
           overview the background of the problem, consider the
           requirements driving ICE, and provide an overview of
           how ICE works. An understanding of SIP is not required.
           The tutorial will be based on the pending -17 version.

RSVP:     Please send a note to me with the Subject line "ice-is-nice"
           (mailto:jdrosen@cisco.com?Subject=ice-is-nice) so I can get a
           count of the number of participants for lunch purposes.


!DO NOT REPLY TO THIS NOTE!
-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Cisco Fellow                                   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

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



From avt-bounces@ietf.org Wed Jul 18 09:33:08 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IB9eH-00061G-Jd; Wed, 18 Jul 2007 09:33:01 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IB9eF-0005sR-Mx
	for avt@ietf.org; Wed, 18 Jul 2007 09:32:59 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IB9eD-00022b-AW
	for avt@ietf.org; Wed, 18 Jul 2007 09:32:59 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 18 Jul 2007 16:33:57 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04C22D0B@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Presentations for the AVT sessions in Chicago
Thread-Index: AcfJQEsAlYZfJDg8T+eXu9vyiPqdPA==
From: "Even, Roni" <roni.even@polycom.co.il>
To: <avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: Colin Perkins <csp@csperkins.org>, tom.taylor@rogers.com
Subject: [AVT] Presentations for the AVT sessions in Chicago
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi,
The AVT first session is on Monday.=20

In order to allow the chairs to upload the presentations before the =
session, I would like to ask all presenters (At least those presenting =
on Monday) to email the chairs their presentation by 5:00PM *GMT* on =
Saturday, July 21st

Thanks

Roni Even =20

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



From avt-bounces@ietf.org Wed Jul 18 17:43:47 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBHJ8-0008EA-LN; Wed, 18 Jul 2007 17:43:42 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBHIk-00080u-4y
	for avt@ietf.org; Wed, 18 Jul 2007 17:43:19 -0400
Received: from mail121.messagelabs.com ([216.82.241.195])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBHIj-0000Ih-R9
	for avt@ietf.org; Wed, 18 Jul 2007 17:43:18 -0400
X-VirusChecked: Checked
X-Env-Sender: acmorton@att.com
X-Msg-Ref: server-4.tower-121.messagelabs.com!1184794996!11222944!1
X-StarScan-Version: 5.5.12.11; banners=-,-,-
X-Originating-IP: [144.160.128.149]
Received: (qmail 13991 invoked from network); 18 Jul 2007 21:43:16 -0000
Received: from sbcsmtp9.sbc.com (HELO flph024.enaf.ffdc.sbc.com)
	(144.160.128.149)
	by server-4.tower-121.messagelabs.com with AES256-SHA encrypted SMTP;
	18 Jul 2007 21:43:16 -0000
Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1])
	by flph024.enaf.ffdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	l6ILhGeH021551 for <avt@ietf.org>; Wed, 18 Jul 2007 14:43:16 -0700
Received: from flph023.ffdc.sbc.com (flph023.ffdc.sbc.com [150.234.117.36])
	by flph024.enaf.ffdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	l6ILhAk8021540 for <avt@ietf.org>; Wed, 18 Jul 2007 14:43:11 -0700
Received: from ffdc.sbc.com (localhost.localdomain [127.0.0.1])
	by flph023.ffdc.sbc.com (8.14.0/8.14.0) with ESMTP id l6ILhA8T027733
	for <avt@ietf.org>; Wed, 18 Jul 2007 14:43:10 -0700
Received: from maillennium.att.com (dns.maillennium.att.com [135.25.114.99])
	by flph023.ffdc.sbc.com (8.14.0/8.14.0) with ESMTP id l6ILh80j027722
	for <avt@ietf.org>; Wed, 18 Jul 2007 14:43:08 -0700
Message-Id: <200707182143.l6ILh80j027722@flph023.ffdc.sbc.com>
Received: from acmt.att.com (acmt.mt.att.com[135.16.251.94](misconfigured
	sender)) by maillennium.att.com (mailgw1) with SMTP
	id <20070718214307gw10010gv1e>; Wed, 18 Jul 2007 21:43:07 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 18 Jul 2007 17:43:04 -0400
To: avt@ietf.org
From: Al Morton <acmorton@att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 1.5 (+)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Subject: [AVT] Application Performance Metrics BOF
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Folks in avt, bmwg, ccamp, ippm, and sipping,

If you're interested in performance metrics,
please join in this BOF and give your opinion
on future directions for this work.

http://www3.ietf.org/proceedings/07jul/agenda/apm.txt

regards,
Al Morton
Alan Clark


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



From avt-bounces@ietf.org Thu Jul 19 17:40:46 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBdjn-00055e-DA; Thu, 19 Jul 2007 17:40:43 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBdjm-000554-Bx
	for avt@ietf.org; Thu, 19 Jul 2007 17:40:42 -0400
Received: from mout.perfora.net ([74.208.4.195])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBdjl-00061l-M9
	for avt@ietf.org; Thu, 19 Jul 2007 17:40:42 -0400
Received: from [216.138.88.2] (helo=TBT-Laptop.newtbt.com)
	by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis),
	id 0MKp8S-1IBdjj1WsP-0005qc; Thu, 19 Jul 2007 17:40:40 -0400
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 19 Jul 2007 14:33:02 -0700
To: AVT WG <avt@ietf.org>
From: Michael A Dolan <md.1@newtbt.com>
Subject: Re: [AVT] draft-ietf-avt-hdrext-12
In-Reply-To: <6B8A5826-4920-4340-8C2A-A99FF749A17B@csperkins.org>
References: <0MKp8S-1I10wF3BuK-0002si@mrelay.perfora.net>
	<FC7B9B6B-15D8-4B2F-82CD-3E1092F92E77@csperkins.org>
	<p0624088fc2a52a180bde@[17.202.35.52]>
	<0MKpCa-1I2qYK1rf9-0001br@mrelay.perfora.net>
	<6B8A5826-4920-4340-8C2A-A99FF749A17B@csperkins.org>
Mime-Version: 1.0
Message-ID: <0MKp8S-1IBdjj1WsP-0005qc@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX1+0LzNLtSGxISx6GBHReu0IwL2mwpSNoF++wR8
	VzvxjHqYgcu5xaJSVba1HHQwoVrUZaNKUQ8KqvRH6Y8swGRVVM
	HlrqseL/UOcP5IeIb+zOw==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985
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="===============0756843469=="
Errors-To: avt-bounces@ietf.org

--===============0756843469==
Content-Type: multipart/alternative;
	boundary="=====================_194683109==.ALT"

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

At 03:39 AM 7/6/2007, Colin Perkins wrote:
>>On 25 Jun 2007, at 16:32, Michael A Dolan wrote:
>>Would it be helpful to see the details?
>
>Probably.

Colin, Dave and all-

Here's a way to merge the two along with the syntax for the alternate
sub-extension:

  0                   1                   2                   3
  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |  ver  |  application-defined  |           length              |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The ver field indicates the version of the syntax that follows for
the sub-headers. Values 1 and 0xB are defined here.  The other values
are reserved by IETF.

The application-defined field is 12 bits that are application-dependent
and may be defined to be any value or meaning and are outside the scope of
this specification.

For the current ID (ver=0xB), they are set to 0xEDE.  For the alternate
encoding (ver=1), they are set to 0x100x, where x is application-defined.

For ver=1, the bytes following the length field consist of a series of
ID/LEN/VAL (like the current ID) except that the first two fields are
each 8 bits (not 4 bits) as follows:

  0                   1
  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |       ID      |     length    |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

FYI, in the actual sub-extensions that are defined, field alignment
requirements completely outweigh any savings from using 4 bit fields.
That is, the same number of bytes are used to encode the extensions
using either 4- or 8-bit ID/LEN fields since the extension fields
need to be field-size aligned and thus padding out to 16 or 32 bits
is nearly always required in both designs.  I.e. 4-bit ID/LEN fields
just doesn't save anything in current practice.  That's not to say
they couldn't be more efficient in some application - just not one
I've seen.

Comments?

Regards,

         Mike


-----------------------------------
Michael DOLAN
Television Broadcast Technology, Inc. (TBT)
PO Box 190, Del Mar, CA 92014 USA
+1-858-755-6661    FAX: +1-858-755-6669
URL:http://www.newtbt.com 
--=====================_194683109==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
At 03:39 AM 7/6/2007, Colin Perkins wrote:<br>
<blockquote type=cite class=cite cite="">
<blockquote type=cite class=cite cite="">On 25 Jun 2007, at 16:32,
Michael A Dolan wrote:<br>
Would it be helpful to see the details?</blockquote><br>
Probably.</blockquote><br>
Colin, Dave and all-<br><br>
Here's a way to merge the two along with the syntax for the
alternate<br>
sub-extension:<br><br>
<font face="Courier, Courier">
&nbsp;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
3<br>
&nbsp;0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0
1<br>
&nbsp;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&nbsp;|&nbsp; ver&nbsp; |&nbsp; application-defined&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&nbsp;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
<br>
</font>The ver field indicates the version of the syntax that follows
for<br>
the sub-headers. Values 1 and 0xB are defined here.&nbsp; The other
values<br>
are reserved by IETF.<br><br>
The application-defined field is 12 bits that are
application-dependent<br>
and may be defined to be any value or meaning and are outside the scope
of<br>
this specification.<br><br>
For the current ID (ver=0xB), they are set to 0xEDE.&nbsp; For the
alternate<br>
encoding (ver=1), they are set to 0x100x, where x is
application-defined.<br><br>
For ver=1, the bytes following the length field consist of a series
of<br>
ID/LEN/VAL (like the current ID) except that the first two fields
are<br>
each 8 bits (not 4 bits) as follows:<br><br>
<font face="Courier, Courier">
&nbsp;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<br>
&nbsp;0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 <br>
&nbsp;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
ID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;
length&nbsp;&nbsp;&nbsp; |<br>
&nbsp;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br><br>
</font>FYI, in the actual sub-extensions that are defined, field
alignment<br>
requirements completely outweigh any savings from using 4 bit
fields.<br>
That is, the same number of bytes are used to encode the extensions<br>
using either 4- or 8-bit ID/LEN fields since the extension fields<br>
need to be field-size aligned and thus padding out to 16 or 32 bits<br>
is nearly always required in both designs.&nbsp; I.e. 4-bit ID/LEN
fields<br>
just doesn't save anything in current practice.&nbsp; That's not to
say<br>
they couldn't be more efficient in some application - just not one<br>
I've seen.<br><br>
Comments?<br><br>
Regards,<br><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mike<br><br>
<x-sigsep><p></x-sigsep>
-----------------------------------<br>
Michael DOLAN<br>
Television Broadcast Technology, Inc. (TBT)<br>
PO Box 190, Del Mar, CA 92014 USA<br>
+1-858-755-6661&nbsp;&nbsp;&nbsp; FAX: +1-858-755-6669<br>
<a href="url:http:%2F%2Fwww.newtbt.com" eudora="autourl">
URL:http://www.newtbt.com</a></body>
</html>

--=====================_194683109==.ALT--



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

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

--===============0756843469==--





From avt-bounces@ietf.org Thu Jul 19 19:08:21 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBf6Y-00041I-Sb; Thu, 19 Jul 2007 19:08:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBf6X-000410-Ln
	for avt@ietf.org; Thu, 19 Jul 2007 19:08:17 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBf6W-00056C-8A
	for avt@ietf.org; Thu, 19 Jul 2007 19:08:17 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l6JN8EfC032408
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 19 Jul 2007 16:08:14 -0700
Received: from SANEXCAS02.na.qualcomm.com (sanexcas02.qualcomm.com
	[172.30.36.176])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l6JN8DOc030396; Thu, 19 Jul 2007 16:08:14 -0700
Received: from NAEX01.qualcomm.com ([129.46.51.61]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Jul 2007 16:08:04 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] draft-ietf-avt-hdrext-12
Date: Thu, 19 Jul 2007 16:08:12 -0700
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B03100F09@NAEX01.na.qualcomm.com>
In-Reply-To: <0MKp8S-1IBdjj1WsP-0005qc@mrelay.perfora.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] draft-ietf-avt-hdrext-12
Thread-Index: AcfKTuiuHuYLeiIPSmyQVFQqH65zxAACGrHQ
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: "Michael A Dolan" <md.1@newtbt.com>, "AVT WG" <avt@ietf.org>
X-OriginalArrivalTime: 19 Jul 2007 23:08:04.0862 (UTC)
	FILETIME=[A989A9E0:01C7CA59]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

>using either 4- or 8-bit ID/LEN fields since the extension fields
>need to be field-size aligned and thus padding out to 16 or 32 bits
>is nearly always required in both designs.

May not be correct, might have to disagree here. It depends on the
number and size of extensions.=20

Note that the scope of 0xBEDE profile extension is RTP/AVP profile and
all its extensions. I see your proposal as a new (0x100x) header
extension format for the same RTP profiles (RTP/AVP and extensions).=20

I think the question that needs to be answered is "Is there is a need
for standardizing multiple header extensions for a given (or set of) RTP
profile(s)?"

I am comfortable to see just one header extension format per RTP
profile. I prefer to keep 0xBEDE as the RECOMMENDED header extension
format for RTP/AVP profile and its extensions.=20

At this time, I think that taking the informational RFC route for 0x100x
would be a better approach.


--Hari

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



From avt-bounces@ietf.org Thu Jul 19 19:47:45 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBfif-0002Jo-KF; Thu, 19 Jul 2007 19:47:41 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBfie-0002Gg-3r
	for avt@ietf.org; Thu, 19 Jul 2007 19:47:40 -0400
Received: from mout.perfora.net ([74.208.4.194])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBfid-0000Od-K6
	for avt@ietf.org; Thu, 19 Jul 2007 19:47:40 -0400
Received: from [216.138.88.2] (helo=TBT-Laptop.newtbt.com)
	by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis),
	id 0MKp8S-1IBfib2mC2-0005q2; Thu, 19 Jul 2007 19:47:39 -0400
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 19 Jul 2007 16:47:37 -0700
To: "AVT WG" <avt@ietf.org>
From: Michael A Dolan <md.1@newtbt.com>
Subject: RE: [AVT] draft-ietf-avt-hdrext-12
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <0MKp8S-1IBfib2mC2-0005q2@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX1+whx2v07IA/j9MTzz6j7LlPq/xdqbIR+uYgv/
	5iFyFjaJbspt9yMvop7GluQgeSJDyPnMh8+liI5WaQy5Agmo4r
	f/f+ElzqDs7wfPE9j3F1Q==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi Hari-

Thank you for your thoughts.

In my survey of extensions (which was certainly not exhaustive) in 
all cases, the 4 bit fields save nothing due to field alignment being 
more important than bit savings.  Of course, potential extensions 
such as byte strings would save one byte per sub-extension in the 
current design.  But all field-aligned 16-byte and 32-byte extension 
fields save nothing.  If this is the basis of the objection, then I 
think we'd need to survey the extensions in use and anticipated and 
form a more technical comparison of the bit savings of 4 versus 8, 
which I maintain is negligible.

My thinking in the proposal below was that it would be better to 
capture the recommended and alternate ID/LEN sizes in one 
document.  I can of course create a 2nd Informational RFC (discussed 
as an option earlier in this thread), but before I did that I would 
poke at the 4-bit design further.  The "defined by profile" field 
value is, of course, arbitrary.

The need comes from the design below being deployed in commercial 
products.  We *do* agree that it is desirable to have only one 
recommended design. So, the question is how best to achieve 
that?  How important is it to preserve a 4-bit design (why, exactly?) 
and the (arbitrary) value 0xBEDE?

Regards,

         Mike

At 04:08 PM 7/19/2007, Desineni, Harikishan wrote:
> >using either 4- or 8-bit ID/LEN fields since the extension fields
> >need to be field-size aligned and thus padding out to 16 or 32 bits
> >is nearly always required in both designs.
>
>May not be correct, might have to disagree here. It depends on the
>number and size of extensions.
>
>Note that the scope of 0xBEDE profile extension is RTP/AVP profile and
>all its extensions. I see your proposal as a new (0x100x) header
>extension format for the same RTP profiles (RTP/AVP and extensions).
>
>I think the question that needs to be answered is "Is there is a need
>for standardizing multiple header extensions for a given (or set of) RTP
>profile(s)?"
>
>I am comfortable to see just one header extension format per RTP
>profile. I prefer to keep 0xBEDE as the RECOMMENDED header extension
>format for RTP/AVP profile and its extensions.
>
>At this time, I think that taking the informational RFC route for 0x100x
>would be a better approach.
>
>
>--Hari

-----------------------------------
Michael DOLAN
Television Broadcast Technology, Inc. (TBT)
PO Box 190, Del Mar, CA 92014 USA
+1-858-755-6661    FAX: +1-858-755-6669
URL:http://www.newtbt.com 


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



From avt-bounces@ietf.org Thu Jul 19 19:52:26 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBfnF-0006uN-Od; Thu, 19 Jul 2007 19:52:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBfnE-0006uE-Ec
	for avt@ietf.org; Thu, 19 Jul 2007 19:52:24 -0400
Received: from mout.perfora.net ([74.208.4.195])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBfnD-0006Lk-Q5
	for avt@ietf.org; Thu, 19 Jul 2007 19:52:24 -0400
Received: from [216.138.88.2] (helo=TBT-Laptop.newtbt.com)
	by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis),
	id 0MKp8S-1IBfnC09fV-0005me; Thu, 19 Jul 2007 19:52:23 -0400
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 19 Jul 2007 16:52:17 -0700
To: "AVT WG" <avt@ietf.org>
From: Michael A Dolan <md.1@newtbt.com>
Subject: RE: [AVT] draft-ietf-avt-hdrext-12
In-Reply-To: <0MKp8S-1IBfib2mC2-0005q2@mrelay.perfora.net>
References: <0MKp8S-1IBfib2mC2-0005q2@mrelay.perfora.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <0MKp8S-1IBfnC09fV-0005me@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX1/RbxoYlI7BTPfMic5fssivjCNrbQi3uE17L5l
	bqAKvJSQ7bJQniutHqwtkmsaxWuEPwYg4JEMaSMOOr8pCdnOIa
	Sn5ancEP3T/wn37UVikBA==
X-Spam-Score: -0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Sorry. "...16-bit and 32-bit..." below.

At 04:47 PM 7/19/2007, Michael A Dolan wrote:
>Hi Hari-
>
>Thank you for your thoughts.
>
>In my survey of extensions (which was certainly not exhaustive) in 
>all cases, the 4 bit fields save nothing due to field alignment 
>being more important than bit savings.  Of course, potential 
>extensions such as byte strings would save one byte per 
>sub-extension in the current design.  But all field-aligned 16-byte 
>and 32-byte extension fields save nothing.  If this is the basis of 
>the objection, then I think we'd need to survey the extensions in 
>use and anticipated and form a more technical comparison of the bit 
>savings of 4 versus 8, which I maintain is negligible.
>
>My thinking in the proposal below was that it would be better to 
>capture the recommended and alternate ID/LEN sizes in one 
>document.  I can of course create a 2nd Informational RFC (discussed 
>as an option earlier in this thread), but before I did that I would 
>poke at the 4-bit design further.  The "defined by profile" field 
>value is, of course, arbitrary.
>
>The need comes from the design below being deployed in commercial 
>products.  We *do* agree that it is desirable to have only one 
>recommended design. So, the question is how best to achieve 
>that?  How important is it to preserve a 4-bit design (why, 
>exactly?) and the (arbitrary) value 0xBEDE?
>
>Regards,
>
>         Mike
>
>At 04:08 PM 7/19/2007, Desineni, Harikishan wrote:
>> >using either 4- or 8-bit ID/LEN fields since the extension fields
>> >need to be field-size aligned and thus padding out to 16 or 32 bits
>> >is nearly always required in both designs.
>>
>>May not be correct, might have to disagree here. It depends on the
>>number and size of extensions.
>>
>>Note that the scope of 0xBEDE profile extension is RTP/AVP profile and
>>all its extensions. I see your proposal as a new (0x100x) header
>>extension format for the same RTP profiles (RTP/AVP and extensions).
>>
>>I think the question that needs to be answered is "Is there is a need
>>for standardizing multiple header extensions for a given (or set of) RTP
>>profile(s)?"
>>
>>I am comfortable to see just one header extension format per RTP
>>profile. I prefer to keep 0xBEDE as the RECOMMENDED header extension
>>format for RTP/AVP profile and its extensions.
>>
>>At this time, I think that taking the informational RFC route for 0x100x
>>would be a better approach.
>>
>>
>>--Hari
>
>-----------------------------------
>Michael DOLAN
>Television Broadcast Technology, Inc. (TBT)
>PO Box 190, Del Mar, CA 92014 USA
>+1-858-755-6661    FAX: +1-858-755-6669
>URL:http://www.newtbt.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



From avt-bounces@ietf.org Fri Jul 20 04:06:05 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBnUx-0000QX-9l; Fri, 20 Jul 2007 04:06:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBnUv-0000QN-DW
	for avt@ietf.org; Fri, 20 Jul 2007 04:06:01 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBnUu-00008d-1C
	for avt@ietf.org; Fri, 20 Jul 2007 04:06:01 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 20 Jul 2007 11:06:59 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04C22F98@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: comments on draft-ietf-avt-rtp-svc-02.txt
Thread-Index: AcfKpPJ3Asusyo/HReGPqPtQWiAFAg==
From: "Even, Roni" <roni.even@polycom.co.il>
To: <avt@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69ad46fbd0e474a7c7f3312d9e320336
Subject: [AVT] comments on draft-ietf-avt-rtp-svc-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>
Content-Type: multipart/mixed; boundary="===============0975340344=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0975340344==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7CAA4.F23616E3"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7CAA4.F23616E3
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

=20

Since H.264 annex G was consented at the last meeting I assume that this =
work can now address a stable payload.

I have some questions and comments on the document

=20

1. In section 1.1 you say "and deprecate the single NAL unit =
packetization mode of RFC 3984." I believe that you are not suggesting =
deprecating the usage of single NAL unit for H264 media subtype but only =
suggesting that it will not be used for the SVC payload type.=20

=20

2. If you suggest using SVC instead of H264 payload type as in section =
6.1 than I would strongly object to take out single NAL unit since this =
is the modes used in all video conferencing shipping products!!!! If you =
want to have interoperability with what you call "legacy" systems you =
must leave this mode. I also do not see any reason in section 6.5 why to =
take this mode out except saying that STAP is easy to implement.=20

Further mode, the single NAL unit mode was agreed by the H.264 expert in =
order to expedite implementation support.=20

=20

3. I also question the claim in the introduction calling SVC a superset =
of H.264 since it is an annex in H.264 and does not cover all the modes =
of H.264. It does not encompass all the H.264 modes

=20

4. In the definition section I find the following definition very =
confusing. "scalable bitstream:  A bitstream with the property that one =
or more bitstream subsets that are not identical to the scalable =
bitstream form another bitstream that conforms to the SVC =
specification."

=20

5. In section 6.1 in order to achieve the design goal of having a full =
compatibility between a SVC full base layer and RFC 3984 encapsulation I =
suggest that the document will explain how to build such a packet and =
maybe recommend that systems that support SVC will be able to accept an =
H264 payload type.

=20

6. In 6.2 " The following applies in addition", there is nothing else in =
the section following the above sentence.

=20

7. About the editor note in 6.6 I suggest explaining it in the SDP =
usage. In the IANA registration these are optional parameters.

=20

8. In section 6.9 you define a new NAL unit type PACSI, is the purpose =
only for MANE devices. How does it go with section 13.6

=20

9. The PACSI NAL unit type is assigned a value (30) in this document. I =
did not see in H.264 or in any other place how you manage the allocation =
of the unspecified values preventing other applications from using this =
value.

=20

10 in section 7 " Informative note: When either the prefix NAL unit or =
the   associated NAL unit containing an H.264/AVC coded slice is lost, =
the remaining one would be hardly useful in SVC context"

I thought that you can decode without the prefix NAL unit. I also =
thought that its usage is optional.

=20

11. In section 7 "When Layers of a SVC bitstream are transported in more =
than one RTP session, the interleaved packetization mode MUST be used"

Why is that, can you explain.

=20

12 in 9.1 what do you mean by " The receiver MUST ignore any unspecified =
parameter"

=20

13. in 9.1 you mention all optional parameters from RFC3984. There are =
now new parameters being specified.

=20

14. You define two new optional parameters sprop-scalability-info and =
sprop-layer-ids. What is the reason for these parameters, it looks to me =
that they duplicate information from the payload header. Also are =
thought parameters fixed during the session. Are they only for =
informational purposes.

=20

15. The payload type is defined as SVC, maybe it should be H264-SVC.

=20

16. Please replace the term MIME with payload type in the document.

=20

Thanks

Roni Even=20

=20

=20

=20

=20


------_=_NextPart_001_01C7CAA4.F23616E3
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"metricconverter"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 77.95pt 72.0pt 77.95pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Hi,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Since H.264 annex G was consented at the last meeting I assume =
that
this work can now address a stable payload.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>I have some questions and comments on the =
document<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><st1:metricconverter ProductID=3D"1. In" =
w:st=3D"on"><font
 size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>1. =
In</span></font></st1:metricconverter>
section 1.1 you say &quot;and deprecate the single NAL unit =
packetization mode
of RFC 3984.&quot; I believe that you are not suggesting deprecating the =
usage
of single NAL unit for H264 media subtype but only suggesting that it =
will not
be used for the SVC payload type. <o:p></o:p></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>2. If you suggest using SVC instead of H264 payload type as in =
section
6.1 than I would strongly object to take out single NAL unit since this =
is the
modes used in all video conferencing shipping products!!!! If you want =
to have interoperability
with what you call &quot;legacy&quot; systems you must leave this mode. =
I also
do not see any reason in section 6.5 why to take this mode out except =
saying
that STAP is easy to implement. <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Further mode, the single NAL unit mode was agreed by the H.264 =
expert
in order to expedite implementation support. =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>3. I also question the claim in the introduction calling SVC a =
superset
of H.264 since it is an annex in H.264 and does not cover all the modes =
of H.264.
It does not encompass all the H.264 modes<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><st1:metricconverter ProductID=3D"4. In" =
w:st=3D"on"><font
 size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>4. =
In</span></font></st1:metricconverter>
the definition section I find the following definition very confusing. =
&quot;scalable
bitstream:=A0 A bitstream with the property that one or more bitstream =
subsets
that are not identical to the scalable bitstream form another bitstream =
that
conforms to the SVC specification.&quot;<o:p></o:p></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><st1:metricconverter ProductID=3D"5. In" =
w:st=3D"on"><font
 size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>5. =
In</span></font></st1:metricconverter>
section <st1:metricconverter ProductID=3D"6.1 in" w:st=3D"on">6.1 =
in</st1:metricconverter>
order to achieve the design goal of having a full compatibility between =
a SVC
full base layer and RFC 3984 encapsulation I suggest that the document =
will
explain how to build such a packet and maybe recommend that systems that
support SVC will be able to accept an H264 payload type.<o:p></o:p></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><st1:metricconverter ProductID=3D"6. In" =
w:st=3D"on"><font
 size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>6. =
In</span></font></st1:metricconverter>
6.2 &quot; The following applies in addition&quot;, there is nothing =
else in
the section following the above sentence.<o:p></o:p></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>7. About the editor note in 6.6 I suggest explaining it in the =
SDP
usage. In the IANA registration these are optional =
parameters.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><st1:metricconverter ProductID=3D"8. In" =
w:st=3D"on"><font
 size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>8. =
In</span></font></st1:metricconverter>
section 6.9 you define a new NAL unit type PACSI, is the purpose only =
for MANE
devices. How does it go with section 13.6<o:p></o:p></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>9. The PACSI NAL unit type is assigned a value (30) in this =
document. I
did not see in H.264 or in any other place how you manage the allocation =
of the
unspecified values preventing other applications from using this =
value.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><st1:metricconverter ProductID=3D"10 in" =
w:st=3D"on"><font
 size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>10 =
in</span></font></st1:metricconverter>
section 7 &quot; Informative note: When either the prefix NAL unit or =
the=A0=A0
associated NAL unit containing an H.264/AVC coded slice is lost, the =
remaining
one would be hardly useful in SVC context&quot;<o:p></o:p></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>I thought that you can decode without the prefix NAL unit. I =
also
thought that its usage is optional.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><st1:metricconverter ProductID=3D"11. In" =
w:st=3D"on"><font
 size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>11. =
In</span></font></st1:metricconverter>
section 7 &quot;When Layers of a SVC bitstream are transported in more =
than one
RTP session, the interleaved packetization mode MUST be =
used&quot;<o:p></o:p></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Why is that, can you explain.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><st1:metricconverter ProductID=3D"12 in" =
w:st=3D"on"><font
 size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>12 =
in</span></font></st1:metricconverter>
9.1 what do you mean by &quot; The receiver MUST ignore any unspecified
parameter&quot;<o:p></o:p></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><st1:metricconverter ProductID=3D"13. in" =
w:st=3D"on"><font
 size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>13. =
in</span></font></st1:metricconverter>
9.1 you mention all optional parameters from RFC3984. There are now new
parameters being specified.<o:p></o:p></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>14. You define two new optional parameters =
sprop-scalability-info and sprop-layer-ids.
What is the reason for these parameters, it looks to me that they =
duplicate information
from the payload header. Also are thought parameters fixed during the =
session.
Are they only for informational purposes.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>15. The payload type is defined as SVC, maybe it should be =
H264-SVC.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>16. Please replace the term MIME with payload type in the =
document.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Thanks<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><st1:PersonName ProductID=3D"Roni Even" =
w:st=3D"on"><font
 size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Roni =
Even</span></font></st1:PersonName>
<o:p></o:p></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>=A0<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C7CAA4.F23616E3--


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

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

--===============0975340344==--




From avt-bounces@ietf.org Fri Jul 20 05:19:37 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBoe7-0003lu-0J; Fri, 20 Jul 2007 05:19:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBoe5-0003lp-1k
	for avt@ietf.org; Fri, 20 Jul 2007 05:19:33 -0400
Received: from mail.hhi.fraunhofer.de ([193.174.67.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBoe3-0001rr-DZ
	for avt@ietf.org; Fri, 20 Jul 2007 05:19:33 -0400
Received: by mail.hhi.fraunhofer.de (Postfix, from userid 65534)
	id 7A8CD1D88F8C; Fri, 20 Jul 2007 11:19:30 +0200 (CEST)
Received: from mail.hhi.fraunhofer.de (localhost [127.0.0.1])
	by mail.hhi.fraunhofer.de (Postfix) with ESMTP id 9544D1D88FED;
	Fri, 20 Jul 2007 11:19:26 +0200 (CEST)
Message-ID: <25218858.481184923166593.OPEN-XCHANGE.WebMail.tomcat@mail.hhi.fraunhofer.de>
Date: Fri, 20 Jul 2007 11:19:26 +0200 (CEST)
From: Thomas Schierl <schierl@hhi.fhg.de>
To: "Even, Roni" <roni.even@polycom.co.il>
Subject: Re: [AVT] comments on draft-ietf-avt-rtp-svc-02.txt
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C04C22F98@IsrExch01.israel.polycom.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (normal)
X-Mailer: OPEN-XCHANGE 5333 - WebMail
Organization: Fraunhofer-Institut fuer Nachrichtentechnik
	Heinrich-Hertz-Institut
References: <144ED8561CE90C41A3E5908EDECE315C04C22F98@IsrExch01.israel.polycom.com>
X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on 
	mail.hhi.fraunhofer.de
X-Spam-Level: 
X-Spam-Status: No, hits=-104.6 required=5.0 tests=AWL,BAYES_00,
	USER_IN_WHITELIST autolearn=ham version=2.64
X-alterMIME: Yes
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cdb443e3957ca9b4c5b55e78cfcf4b26
Cc: stewe@stewe.org, avt@ietf.org, Ye-Kui.Wang@nokia.com
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi Roni,

Thanks for the feedback on the draft. Please, find my comments inline.

Thomas


On Jul 20, 2007 10:06 AM, "Even, Roni" <roni.even@polycom.co.il> wrote:

>1. In section 1.1 you say "and deprecate the single NAL unit
>packetization mode of RFC 3984." I believe that you are not suggesting
>deprecating the usage of single NAL unit for H264 media subtype but
>only suggesting that it will not be used for the SVC payload type.

Yes, when using H.264 in context with SVC, e.g. a SVC stream separated
in its H.264 base layer and the SVC enhancements. But for plain H.264,
we do not want to deprecate it, since it is a part of RFC3984.

>
>
>
>2. If you suggest using SVC instead of H264 payload type as in section
>6.1 than I would strongly object to take out single NAL unit since this
>is the modes used in all video conferencing shipping products!!!! If
>you want to have interoperability with what you call "legacy" systems
>you must leave this mode. I also do not see any reason in section 6.5
>why to take this mode out except saying that STAP is easy to implement.
>
>Further mode, the single NAL unit mode was agreed by the H.264 expert
>in order to expedite implementation support.
>

I am ok with your suggestion.


>
>
>3. I also question the claim in the introduction calling SVC a superset
>of H.264 since it is an annex in H.264 and does not cover all the modes
>of H.264. It does not encompass all the H.264 modes
>
>
You are right.

>
>4. In the definition section I find the following definition very
>confusing. "scalable bitstream: A bitstream with the property that one
>or more bitstream subsets that are not identical to the scalable
>bitstream form another bitstream that conforms to the SVC
>specification."
>

In H.264, there are the following definitions:

bitstream: A sequence of bits that forms the representation of coded
pictures and associated data forming one or more coded video sequences.
Bitstream is a collective term used to refer either to a NAL unit stream
or a byte stream.

bitstream subset: A bitstream that is derived as a subset from a
bitstream by discarding zero or more NAL units

Maybe, we use these definitions for more clarity.

>
>5. In section 6.1 in order to achieve the design goal of having a full
>compatibility between a SVC full base layer and RFC 3984 encapsulation
>I suggest that the document will explain how to build such a packet and
>maybe recommend that systems that support SVC will be able to accept an
>H264 payload type.
>

Good, we will incorporate that. But there may be also the case, where no
backward compatibility is required. In that case, I would not like to
force the receiver supporting full RFC3984.

>
>
>6. In 6.2 " The following applies in addition", there is nothing else
>in the section following the above sentence.
>
Yes, you are right, there was a note in the last draft about:
=C2=A0=C2=A0When layers of an SVC scalable bitstream are transported in mor=
e
=C2=A0=C2=A0than one RTP session, e.g. in layered multicast for which the u=
se
=C2=A0=C2=A0case is given in 13.2, session multiplexing MUST be used only a=
s RTP
=C2=A0=C2=A0multiplexing technique.

We found that not helpful anymore. So, we may need to remove 6.2.

>
>
>7. About the editor note in 6.6 I suggest explaining it in the SDP
>usage. In the IANA registration these are optional parameters.
>
Good.

>
>
>8. In section 6.9 you define a new NAL unit type PACSI, is the purpose
>only for MANE devices. How does it go with section 13.6
>
I think section 13.6 can be removed anyway. That was useful for
explaining IETF philosophy but is not required for the final payload
draft.


>
>9. The PACSI NAL unit type is assigned a value (30) in this document. I
>did not see in H.264 or in any other place how you manage the
>allocation of the unspecified values preventing other applications from
>using this value.
>
In H.264, these types are left open for application usage:
In Table 7-1 the H.264 standard says these types are unspecified.

>
>
>10 in section 7 " Informative note: When either the prefix NAL unit or
>the associated NAL unit containing an H.264/AVC coded slice is lost,
>the remaining one would be hardly useful in SVC context"
>
>I thought that you can decode without the prefix NAL unit. I also
>thought that its usage is optional.
>

Exactly, you can decode it but you may not be able to use it as
reference for a SVC enhancement layer.

>
>
>11. In section 7 "When Layers of a SVC bitstream are transported in
>more than one RTP session, the interleaved packetization mode MUST be
>used"
>
>Why is that, can you explain.

We tried to explain that in section 14 of
draft-wenger-avt-rtp-svc-01.txt . In that section we tried to solve the
problem of re-interleaving NAL untis from different RTP sessions to one
SVC bistream. We found that this may be very complicated. On the other
hand it is very simple if using an extended cross-layer DON.

>
>
>
>12 in 9.1 what do you mean by " The receiver MUST ignore any
>unspecified parameter"
>
Maybe, Stephan can reply on that.

>
>
>13. in 9.1 you mention all optional parameters from RFC3984. There are
>now new parameters being specified.
>
>
>
>14. You define two new optional parameters sprop-scalability-info and
>sprop-layer-ids. What is the reason for these parameters, it looks to
>me that they duplicate information from the payload header. Also are
>thought parameters fixed during the session. Are they only for
>informational purposes.
>

The scalability SEI (sprop-scalability-info) is useful, if someone wants
to understand the whole SVC bitstream, e.g., which layers are available
at which resolution or framerate. It also connects the NAL unti header
scalability identifier (PRID, DID, QID, TID) with such values.
The second parameter sprop-layer-ids is useful to describe in the
layered Multicast case which scalability levels of the whole bitstream
(described by sprop-scalability-info) are contained in an RTP session.

>
>
>15. The payload type is defined as SVC, maybe it should be H264-SVC.
>
I have no preference.

>
>
>16. Please replace the term MIME with payload type in the document.
>

Ok.

>
>
>Thanks
>
>Roni Even
>
>
>
>
>
>
>
>
>




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



From avt-bounces@ietf.org Fri Jul 20 07:16:18 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBqT0-00075B-T2; Fri, 20 Jul 2007 07:16:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBqSz-000751-Er
	for avt@ietf.org; Fri, 20 Jul 2007 07:16:13 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBqSy-0004Ii-Eh
	for avt@ietf.org; Fri, 20 Jul 2007 07:16:13 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [AVT] comments on draft-ietf-avt-rtp-svc-02.txt
Date: Fri, 20 Jul 2007 14:17:14 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04C22FA3@IsrExch01.israel.polycom.com>
In-Reply-To: <25218858.481184923166593.OPEN-XCHANGE.WebMail.tomcat@mail.hhi.fraunhofer.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] comments on draft-ietf-avt-rtp-svc-02.txt
Thread-Index: AcfKrzv1Rb8l5hnFQp+Tx0CWVTvlLwAD33NA
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Thomas Schierl" <schierl@hhi.fhg.de>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f
Cc: stewe@stewe.org, avt@ietf.org, Ye-Kui.Wang@nokia.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>
Content-Type: multipart/mixed; boundary="===============0289564661=="
Errors-To: avt-bounces@ietf.org

--===============0289564661==
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

VGhvbWFzLA0KVGhhbmtzLA0KDQpBYm91dCB0aGUgUEFDU0kgTkFMIHVuaXQgdHlwZS4gTXkgcXVl
c3Rpb24gd2FzIGFib3V0IHRoZSBhbGxvY2F0aW9uIG1lY2hhbmlzbSBmb3IgdGhlIHVuc3BlY2lm
aWVkIHZhbHVlcyBpbiBILjI2NC4gWW91IGFyZSBhbGxvY2F0aW5nIDMwIGluIHRoaXMgZG9jdW1l
bnQgZm9yIFBBQ1NJLiBXaGF0IHByZXZlbnRzIHNvbWVvbmUgZWxzZSwgZm9yIGV4YW1wbGUgaW4g
M0dQUCwgdG8gZGVmaW5lIGFub3RoZXIgTkFMIHVuaXQgdHlwZSBhbmQgZ2l2ZSBpdCBhbHNvIHRo
ZSBudW1iZXIgMzAuIA0KDQpBcyBmb3IgdGhlIG5ldyBvcHRpb25hbCBwYXJhbWV0ZXJzLCBJIHVu
ZGVyc3RhbmQgdGhhdCB0aGV5IGFyZSBvZiBpbmZvcm1hdGlvbmFsIHZhbHVlIGFuZCBJIHdhcyB3
b25kZXJpbmcgaWYgdGhlIGVuaGFuY2VtZW50IGxheWVycyBjYW4gYmUgY2hhbmdlZCB3aXRob3V0
IHNpZ25hbGluZyBhbmQgaG93IG9mdGVuIGNhbiB5b3UgY2hhbmdlIHRoZW0uDQoNClJvbmkgDQoN
Cj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogVGhvbWFzIFNjaGllcmwgW21h
aWx0bzpzY2hpZXJsQGhoaS5maGcuZGVdDQo+IFNlbnQ6IEZyaWRheSwgSnVseSAyMCwgMjAwNyAx
MjoxOSBQTQ0KPiBUbzogRXZlbiwgUm9uaQ0KPiBDYzogYXZ0QGlldGYub3JnOyBzdGV3ZUBzdGV3
ZS5vcmc7IFllLUt1aS5XYW5nQG5va2lhLmNvbQ0KPiBTdWJqZWN0OiBSZTogW0FWVF0gY29tbWVu
dHMgb24gZHJhZnQtaWV0Zi1hdnQtcnRwLXN2Yy0wMi50eHQNCj4gDQo+IEhpIFJvbmksDQo+IA0K
PiBUaGFua3MgZm9yIHRoZSBmZWVkYmFjayBvbiB0aGUgZHJhZnQuIFBsZWFzZSwgZmluZCBteSBj
b21tZW50cyBpbmxpbmUuDQo+IA0KPiBUaG9tYXMNCj4gDQo+IA0KPiBPbiBKdWwgMjAsIDIwMDcg
MTA6MDYgQU0sICJFdmVuLCBSb25pIiA8cm9uaS5ldmVuQHBvbHljb20uY28uaWw+IHdyb3RlOg0K
PiANCj4gPjEuIEluIHNlY3Rpb24gMS4xIHlvdSBzYXkgImFuZCBkZXByZWNhdGUgdGhlIHNpbmds
ZSBOQUwgdW5pdA0KPiA+cGFja2V0aXphdGlvbiBtb2RlIG9mIFJGQyAzOTg0LiIgSSBiZWxpZXZl
IHRoYXQgeW91IGFyZSBub3Qgc3VnZ2VzdGluZw0KPiA+ZGVwcmVjYXRpbmcgdGhlIHVzYWdlIG9m
IHNpbmdsZSBOQUwgdW5pdCBmb3IgSDI2NCBtZWRpYSBzdWJ0eXBlIGJ1dA0KPiA+b25seSBzdWdn
ZXN0aW5nIHRoYXQgaXQgd2lsbCBub3QgYmUgdXNlZCBmb3IgdGhlIFNWQyBwYXlsb2FkIHR5cGUu
DQo+IA0KPiBZZXMsIHdoZW4gdXNpbmcgSC4yNjQgaW4gY29udGV4dCB3aXRoIFNWQywgZS5nLiBh
IFNWQyBzdHJlYW0gc2VwYXJhdGVkDQo+IGluIGl0cyBILjI2NCBiYXNlIGxheWVyIGFuZCB0aGUg
U1ZDIGVuaGFuY2VtZW50cy4gQnV0IGZvciBwbGFpbiBILjI2NCwNCj4gd2UgZG8gbm90IHdhbnQg
dG8gZGVwcmVjYXRlIGl0LCBzaW5jZSBpdCBpcyBhIHBhcnQgb2YgUkZDMzk4NC4NCj4gDQo+ID4N
Cj4gPg0KPiA+DQo+ID4yLiBJZiB5b3Ugc3VnZ2VzdCB1c2luZyBTVkMgaW5zdGVhZCBvZiBIMjY0
IHBheWxvYWQgdHlwZSBhcyBpbiBzZWN0aW9uDQo+ID42LjEgdGhhbiBJIHdvdWxkIHN0cm9uZ2x5
IG9iamVjdCB0byB0YWtlIG91dCBzaW5nbGUgTkFMIHVuaXQgc2luY2UgdGhpcw0KPiA+aXMgdGhl
IG1vZGVzIHVzZWQgaW4gYWxsIHZpZGVvIGNvbmZlcmVuY2luZyBzaGlwcGluZyBwcm9kdWN0cyEh
ISEgSWYNCj4gPnlvdSB3YW50IHRvIGhhdmUgaW50ZXJvcGVyYWJpbGl0eSB3aXRoIHdoYXQgeW91
IGNhbGwgImxlZ2FjeSIgc3lzdGVtcw0KPiA+eW91IG11c3QgbGVhdmUgdGhpcyBtb2RlLiBJIGFs
c28gZG8gbm90IHNlZSBhbnkgcmVhc29uIGluIHNlY3Rpb24gNi41DQo+ID53aHkgdG8gdGFrZSB0
aGlzIG1vZGUgb3V0IGV4Y2VwdCBzYXlpbmcgdGhhdCBTVEFQIGlzIGVhc3kgdG8gaW1wbGVtZW50
Lg0KPiA+DQo+ID5GdXJ0aGVyIG1vZGUsIHRoZSBzaW5nbGUgTkFMIHVuaXQgbW9kZSB3YXMgYWdy
ZWVkIGJ5IHRoZSBILjI2NCBleHBlcnQNCj4gPmluIG9yZGVyIHRvIGV4cGVkaXRlIGltcGxlbWVu
dGF0aW9uIHN1cHBvcnQuDQo+ID4NCj4gDQo+IEkgYW0gb2sgd2l0aCB5b3VyIHN1Z2dlc3Rpb24u
DQo+IA0KPiANCj4gPg0KPiA+DQo+ID4zLiBJIGFsc28gcXVlc3Rpb24gdGhlIGNsYWltIGluIHRo
ZSBpbnRyb2R1Y3Rpb24gY2FsbGluZyBTVkMgYSBzdXBlcnNldA0KPiA+b2YgSC4yNjQgc2luY2Ug
aXQgaXMgYW4gYW5uZXggaW4gSC4yNjQgYW5kIGRvZXMgbm90IGNvdmVyIGFsbCB0aGUgbW9kZXMN
Cj4gPm9mIEguMjY0LiBJdCBkb2VzIG5vdCBlbmNvbXBhc3MgYWxsIHRoZSBILjI2NCBtb2Rlcw0K
PiA+DQo+ID4NCj4gWW91IGFyZSByaWdodC4NCj4gDQo+ID4NCj4gPjQuIEluIHRoZSBkZWZpbml0
aW9uIHNlY3Rpb24gSSBmaW5kIHRoZSBmb2xsb3dpbmcgZGVmaW5pdGlvbiB2ZXJ5DQo+ID5jb25m
dXNpbmcuICJzY2FsYWJsZSBiaXRzdHJlYW06IEEgYml0c3RyZWFtIHdpdGggdGhlIHByb3BlcnR5
IHRoYXQgb25lDQo+ID5vciBtb3JlIGJpdHN0cmVhbSBzdWJzZXRzIHRoYXQgYXJlIG5vdCBpZGVu
dGljYWwgdG8gdGhlIHNjYWxhYmxlDQo+ID5iaXRzdHJlYW0gZm9ybSBhbm90aGVyIGJpdHN0cmVh
bSB0aGF0IGNvbmZvcm1zIHRvIHRoZSBTVkMNCj4gPnNwZWNpZmljYXRpb24uIg0KPiA+DQo+IA0K
PiBJbiBILjI2NCwgdGhlcmUgYXJlIHRoZSBmb2xsb3dpbmcgZGVmaW5pdGlvbnM6DQo+IA0KPiBi
aXRzdHJlYW06IEEgc2VxdWVuY2Ugb2YgYml0cyB0aGF0IGZvcm1zIHRoZSByZXByZXNlbnRhdGlv
biBvZiBjb2RlZA0KPiBwaWN0dXJlcyBhbmQgYXNzb2NpYXRlZCBkYXRhIGZvcm1pbmcgb25lIG9y
IG1vcmUgY29kZWQgdmlkZW8gc2VxdWVuY2VzLg0KPiBCaXRzdHJlYW0gaXMgYSBjb2xsZWN0aXZl
IHRlcm0gdXNlZCB0byByZWZlciBlaXRoZXIgdG8gYSBOQUwgdW5pdCBzdHJlYW0NCj4gb3IgYSBi
eXRlIHN0cmVhbS4NCj4gDQo+IGJpdHN0cmVhbSBzdWJzZXQ6IEEgYml0c3RyZWFtIHRoYXQgaXMg
ZGVyaXZlZCBhcyBhIHN1YnNldCBmcm9tIGENCj4gYml0c3RyZWFtIGJ5IGRpc2NhcmRpbmcgemVy
byBvciBtb3JlIE5BTCB1bml0cw0KPiANCj4gTWF5YmUsIHdlIHVzZSB0aGVzZSBkZWZpbml0aW9u
cyBmb3IgbW9yZSBjbGFyaXR5Lg0KPiANCj4gPg0KPiA+NS4gSW4gc2VjdGlvbiA2LjEgaW4gb3Jk
ZXIgdG8gYWNoaWV2ZSB0aGUgZGVzaWduIGdvYWwgb2YgaGF2aW5nIGEgZnVsbA0KPiA+Y29tcGF0
aWJpbGl0eSBiZXR3ZWVuIGEgU1ZDIGZ1bGwgYmFzZSBsYXllciBhbmQgUkZDIDM5ODQgZW5jYXBz
dWxhdGlvbg0KPiA+SSBzdWdnZXN0IHRoYXQgdGhlIGRvY3VtZW50IHdpbGwgZXhwbGFpbiBob3cg
dG8gYnVpbGQgc3VjaCBhIHBhY2tldCBhbmQNCj4gPm1heWJlIHJlY29tbWVuZCB0aGF0IHN5c3Rl
bXMgdGhhdCBzdXBwb3J0IFNWQyB3aWxsIGJlIGFibGUgdG8gYWNjZXB0IGFuDQo+ID5IMjY0IHBh
eWxvYWQgdHlwZS4NCj4gPg0KPiANCj4gR29vZCwgd2Ugd2lsbCBpbmNvcnBvcmF0ZSB0aGF0LiBC
dXQgdGhlcmUgbWF5IGJlIGFsc28gdGhlIGNhc2UsIHdoZXJlIG5vDQo+IGJhY2t3YXJkIGNvbXBh
dGliaWxpdHkgaXMgcmVxdWlyZWQuIEluIHRoYXQgY2FzZSwgSSB3b3VsZCBub3QgbGlrZSB0bw0K
PiBmb3JjZSB0aGUgcmVjZWl2ZXIgc3VwcG9ydGluZyBmdWxsIFJGQzM5ODQuDQo+IA0KPiA+DQo+
ID4NCj4gPjYuIEluIDYuMiAiIFRoZSBmb2xsb3dpbmcgYXBwbGllcyBpbiBhZGRpdGlvbiIsIHRo
ZXJlIGlzIG5vdGhpbmcgZWxzZQ0KPiA+aW4gdGhlIHNlY3Rpb24gZm9sbG93aW5nIHRoZSBhYm92
ZSBzZW50ZW5jZS4NCj4gPg0KPiBZZXMsIHlvdSBhcmUgcmlnaHQsIHRoZXJlIHdhcyBhIG5vdGUg
aW4gdGhlIGxhc3QgZHJhZnQgYWJvdXQ6DQo+IMKgwqBXaGVuIGxheWVycyBvZiBhbiBTVkMgc2Nh
bGFibGUgYml0c3RyZWFtIGFyZSB0cmFuc3BvcnRlZCBpbiBtb3JlDQo+IMKgwqB0aGFuIG9uZSBS
VFAgc2Vzc2lvbiwgZS5nLiBpbiBsYXllcmVkIG11bHRpY2FzdCBmb3Igd2hpY2ggdGhlIHVzZQ0K
PiDCoMKgY2FzZSBpcyBnaXZlbiBpbiAxMy4yLCBzZXNzaW9uIG11bHRpcGxleGluZyBNVVNUIGJl
IHVzZWQgb25seSBhcyBSVFANCj4gwqDCoG11bHRpcGxleGluZyB0ZWNobmlxdWUuDQo+IA0KPiBX
ZSBmb3VuZCB0aGF0IG5vdCBoZWxwZnVsIGFueW1vcmUuIFNvLCB3ZSBtYXkgbmVlZCB0byByZW1v
dmUgNi4yLg0KPiANCj4gPg0KPiA+DQo+ID43LiBBYm91dCB0aGUgZWRpdG9yIG5vdGUgaW4gNi42
IEkgc3VnZ2VzdCBleHBsYWluaW5nIGl0IGluIHRoZSBTRFANCj4gPnVzYWdlLiBJbiB0aGUgSUFO
QSByZWdpc3RyYXRpb24gdGhlc2UgYXJlIG9wdGlvbmFsIHBhcmFtZXRlcnMuDQo+ID4NCj4gR29v
ZC4NCj4gDQo+ID4NCj4gPg0KPiA+OC4gSW4gc2VjdGlvbiA2LjkgeW91IGRlZmluZSBhIG5ldyBO
QUwgdW5pdCB0eXBlIFBBQ1NJLCBpcyB0aGUgcHVycG9zZQ0KPiA+b25seSBmb3IgTUFORSBkZXZp
Y2VzLiBIb3cgZG9lcyBpdCBnbyB3aXRoIHNlY3Rpb24gMTMuNg0KPiA+DQo+IEkgdGhpbmsgc2Vj
dGlvbiAxMy42IGNhbiBiZSByZW1vdmVkIGFueXdheS4gVGhhdCB3YXMgdXNlZnVsIGZvcg0KPiBl
eHBsYWluaW5nIElFVEYgcGhpbG9zb3BoeSBidXQgaXMgbm90IHJlcXVpcmVkIGZvciB0aGUgZmlu
YWwgcGF5bG9hZA0KPiBkcmFmdC4NCj4gDQo+IA0KPiA+DQo+ID45LiBUaGUgUEFDU0kgTkFMIHVu
aXQgdHlwZSBpcyBhc3NpZ25lZCBhIHZhbHVlICgzMCkgaW4gdGhpcyBkb2N1bWVudC4gSQ0KPiA+
ZGlkIG5vdCBzZWUgaW4gSC4yNjQgb3IgaW4gYW55IG90aGVyIHBsYWNlIGhvdyB5b3UgbWFuYWdl
IHRoZQ0KPiA+YWxsb2NhdGlvbiBvZiB0aGUgdW5zcGVjaWZpZWQgdmFsdWVzIHByZXZlbnRpbmcg
b3RoZXIgYXBwbGljYXRpb25zIGZyb20NCj4gPnVzaW5nIHRoaXMgdmFsdWUuDQo+ID4NCj4gSW4g
SC4yNjQsIHRoZXNlIHR5cGVzIGFyZSBsZWZ0IG9wZW4gZm9yIGFwcGxpY2F0aW9uIHVzYWdlOg0K
PiBJbiBUYWJsZSA3LTEgdGhlIEguMjY0IHN0YW5kYXJkIHNheXMgdGhlc2UgdHlwZXMgYXJlIHVu
c3BlY2lmaWVkLg0KPiANCj4gPg0KPiA+DQo+ID4xMCBpbiBzZWN0aW9uIDcgIiBJbmZvcm1hdGl2
ZSBub3RlOiBXaGVuIGVpdGhlciB0aGUgcHJlZml4IE5BTCB1bml0IG9yDQo+ID50aGUgYXNzb2Np
YXRlZCBOQUwgdW5pdCBjb250YWluaW5nIGFuIEguMjY0L0FWQyBjb2RlZCBzbGljZSBpcyBsb3N0
LA0KPiA+dGhlIHJlbWFpbmluZyBvbmUgd291bGQgYmUgaGFyZGx5IHVzZWZ1bCBpbiBTVkMgY29u
dGV4dCINCj4gPg0KPiA+SSB0aG91Z2h0IHRoYXQgeW91IGNhbiBkZWNvZGUgd2l0aG91dCB0aGUg
cHJlZml4IE5BTCB1bml0LiBJIGFsc28NCj4gPnRob3VnaHQgdGhhdCBpdHMgdXNhZ2UgaXMgb3B0
aW9uYWwuDQo+ID4NCj4gDQo+IEV4YWN0bHksIHlvdSBjYW4gZGVjb2RlIGl0IGJ1dCB5b3UgbWF5
IG5vdCBiZSBhYmxlIHRvIHVzZSBpdCBhcw0KPiByZWZlcmVuY2UgZm9yIGEgU1ZDIGVuaGFuY2Vt
ZW50IGxheWVyLg0KPiANCj4gPg0KPiA+DQo+ID4xMS4gSW4gc2VjdGlvbiA3ICJXaGVuIExheWVy
cyBvZiBhIFNWQyBiaXRzdHJlYW0gYXJlIHRyYW5zcG9ydGVkIGluDQo+ID5tb3JlIHRoYW4gb25l
IFJUUCBzZXNzaW9uLCB0aGUgaW50ZXJsZWF2ZWQgcGFja2V0aXphdGlvbiBtb2RlIE1VU1QgYmUN
Cj4gPnVzZWQiDQo+ID4NCj4gPldoeSBpcyB0aGF0LCBjYW4geW91IGV4cGxhaW4uDQo+IA0KPiBX
ZSB0cmllZCB0byBleHBsYWluIHRoYXQgaW4gc2VjdGlvbiAxNCBvZg0KPiBkcmFmdC13ZW5nZXIt
YXZ0LXJ0cC1zdmMtMDEudHh0IC4gSW4gdGhhdCBzZWN0aW9uIHdlIHRyaWVkIHRvIHNvbHZlIHRo
ZQ0KPiBwcm9ibGVtIG9mIHJlLWludGVybGVhdmluZyBOQUwgdW50aXMgZnJvbSBkaWZmZXJlbnQg
UlRQIHNlc3Npb25zIHRvIG9uZQ0KPiBTVkMgYmlzdHJlYW0uIFdlIGZvdW5kIHRoYXQgdGhpcyBt
YXkgYmUgdmVyeSBjb21wbGljYXRlZC4gT24gdGhlIG90aGVyDQo+IGhhbmQgaXQgaXMgdmVyeSBz
aW1wbGUgaWYgdXNpbmcgYW4gZXh0ZW5kZWQgY3Jvc3MtbGF5ZXIgRE9OLg0KPiANCj4gPg0KPiA+
DQo+ID4NCj4gPjEyIGluIDkuMSB3aGF0IGRvIHlvdSBtZWFuIGJ5ICIgVGhlIHJlY2VpdmVyIE1V
U1QgaWdub3JlIGFueQ0KPiA+dW5zcGVjaWZpZWQgcGFyYW1ldGVyIg0KPiA+DQo+IE1heWJlLCBT
dGVwaGFuIGNhbiByZXBseSBvbiB0aGF0Lg0KPiANCj4gPg0KPiA+DQo+ID4xMy4gaW4gOS4xIHlv
dSBtZW50aW9uIGFsbCBvcHRpb25hbCBwYXJhbWV0ZXJzIGZyb20gUkZDMzk4NC4gVGhlcmUgYXJl
DQo+ID5ub3cgbmV3IHBhcmFtZXRlcnMgYmVpbmcgc3BlY2lmaWVkLg0KPiA+DQo+ID4NCj4gPg0K
PiA+MTQuIFlvdSBkZWZpbmUgdHdvIG5ldyBvcHRpb25hbCBwYXJhbWV0ZXJzIHNwcm9wLXNjYWxh
YmlsaXR5LWluZm8gYW5kDQo+ID5zcHJvcC1sYXllci1pZHMuIFdoYXQgaXMgdGhlIHJlYXNvbiBm
b3IgdGhlc2UgcGFyYW1ldGVycywgaXQgbG9va3MgdG8NCj4gPm1lIHRoYXQgdGhleSBkdXBsaWNh
dGUgaW5mb3JtYXRpb24gZnJvbSB0aGUgcGF5bG9hZCBoZWFkZXIuIEFsc28gYXJlDQo+ID50aG91
Z2h0IHBhcmFtZXRlcnMgZml4ZWQgZHVyaW5nIHRoZSBzZXNzaW9uLiBBcmUgdGhleSBvbmx5IGZv
cg0KPiA+aW5mb3JtYXRpb25hbCBwdXJwb3Nlcy4NCj4gPg0KPiANCj4gVGhlIHNjYWxhYmlsaXR5
IFNFSSAoc3Byb3Atc2NhbGFiaWxpdHktaW5mbykgaXMgdXNlZnVsLCBpZiBzb21lb25lIHdhbnRz
DQo+IHRvIHVuZGVyc3RhbmQgdGhlIHdob2xlIFNWQyBiaXRzdHJlYW0sIGUuZy4sIHdoaWNoIGxh
eWVycyBhcmUgYXZhaWxhYmxlDQo+IGF0IHdoaWNoIHJlc29sdXRpb24gb3IgZnJhbWVyYXRlLiBJ
dCBhbHNvIGNvbm5lY3RzIHRoZSBOQUwgdW50aSBoZWFkZXINCj4gc2NhbGFiaWxpdHkgaWRlbnRp
ZmllciAoUFJJRCwgRElELCBRSUQsIFRJRCkgd2l0aCBzdWNoIHZhbHVlcy4NCj4gVGhlIHNlY29u
ZCBwYXJhbWV0ZXIgc3Byb3AtbGF5ZXItaWRzIGlzIHVzZWZ1bCB0byBkZXNjcmliZSBpbiB0aGUN
Cj4gbGF5ZXJlZCBNdWx0aWNhc3QgY2FzZSB3aGljaCBzY2FsYWJpbGl0eSBsZXZlbHMgb2YgdGhl
IHdob2xlIGJpdHN0cmVhbQ0KPiAoZGVzY3JpYmVkIGJ5IHNwcm9wLXNjYWxhYmlsaXR5LWluZm8p
IGFyZSBjb250YWluZWQgaW4gYW4gUlRQIHNlc3Npb24uDQo+IA0KPiA+DQo+ID4NCj4gPjE1LiBU
aGUgcGF5bG9hZCB0eXBlIGlzIGRlZmluZWQgYXMgU1ZDLCBtYXliZSBpdCBzaG91bGQgYmUgSDI2
NC1TVkMuDQo+ID4NCj4gSSBoYXZlIG5vIHByZWZlcmVuY2UuDQo+IA0KPiA+DQo+ID4NCj4gPjE2
LiBQbGVhc2UgcmVwbGFjZSB0aGUgdGVybSBNSU1FIHdpdGggcGF5bG9hZCB0eXBlIGluIHRoZSBk
b2N1bWVudC4NCj4gPg0KPiANCj4gT2suDQo+IA0KPiA+DQo+ID4NCj4gPlRoYW5rcw0KPiA+DQo+
ID5Sb25pIEV2ZW4NCj4gPg0KPiA+DQo+ID4NCj4gPg0KPiA+DQo+ID4NCj4gPg0KPiA+DQo+ID4N
Cj4gDQo+IA0KDQo=


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

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

--===============0289564661==--



From avt-bounces@ietf.org Fri Jul 20 08:02:51 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBrC4-0002UJ-Uz; Fri, 20 Jul 2007 08:02:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBrC2-0002Td-W6
	for avt@ietf.org; Fri, 20 Jul 2007 08:02:47 -0400
Received: from mail.hhi.fraunhofer.de ([193.174.67.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBrC1-0005JX-Gg
	for avt@ietf.org; Fri, 20 Jul 2007 08:02:46 -0400
Received: by mail.hhi.fraunhofer.de (Postfix, from userid 65534)
	id BC3BB1D88FCC; Fri, 20 Jul 2007 14:02:44 +0200 (CEST)
Received: from mail.hhi.fraunhofer.de (localhost [127.0.0.1])
	by mail.hhi.fraunhofer.de (Postfix) with ESMTP id A12AC1D88F7A;
	Fri, 20 Jul 2007 14:02:39 +0200 (CEST)
Message-ID: <2326550.1061184932959567.OPEN-XCHANGE.WebMail.tomcat@mail.hhi.fraunhofer.de>
Date: Fri, 20 Jul 2007 14:02:39 +0200 (CEST)
From: Thomas Schierl <schierl@hhi.fhg.de>
To: "Even, Roni" <roni.even@polycom.co.il>
Subject: RE: [AVT] comments on draft-ietf-avt-rtp-svc-02.txt
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C04C22FA3@IsrExch01.israel.polycom.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (normal)
X-Mailer: OPEN-XCHANGE 5333 - WebMail
Organization: Fraunhofer-Institut fuer Nachrichtentechnik
	Heinrich-Hertz-Institut
References: <144ED8561CE90C41A3E5908EDECE315C04C22FA3@IsrExch01.israel.polycom.com>
X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on 
	mail.hhi.fraunhofer.de
X-Spam-Level: 
X-Spam-Status: No, hits=-104.6 required=5.0 tests=AWL,BAYES_00,
	USER_IN_WHITELIST autolearn=ham version=2.64
X-alterMIME: Yes
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f8ee348dcc4be4a59bc395f7cd6343ad
Cc: stewe@stewe.org, avt@ietf.org, Ye-Kui.Wang@nokia.com
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi Roni,

Please find my comments inline.

Thomas

On Jul 20, 2007 01:17 PM, "Even, Roni" <roni.even@polycom.co.il> wrote:

>About the PACSI NAL unit type. My question was about the allocation
>mechanism for the unspecified values in H.264. You are allocating 30 in
>this document for PACSI. What prevents someone else, for example in
>3GPP, to define another NAL unit type and give it also the number 30.

There is no coordination for the usage of user space NAL units, thus
only the specification in question can rely on such a number.

>
>As for the new optional parameters, I understand that they are of
>informational value and I was wondering if the enhancement layers can
>be changed without signaling and how often can you change them.

Enhancement layers can be changed on a frame by frame basis. Since the
signaling must be still correct within a RTP session, the idea is to
signal the highest operation point of the RTP session. So that, the
receiver=C2=A0 is prepared for receiving that and all lower operation point=
s.
Does that answer your question?


>
>Roni
>
>>-----Original Message-----
>>From: Thomas Schierl [mailto:schierl@hhi.fhg.de]
>>Sent: Friday, July 20, 2007 12:19 PM
>>To: Even, Roni
>>Cc: avt@ietf.org; stewe@stewe.org; Ye-Kui.Wang@nokia.com
>>Subject: Re: [AVT] comments on draft-ietf-avt-rtp-svc-02.txt
>>
>>Hi Roni,
>>
>>Thanks for the feedback on the draft. Please, find my comments inline.
>>
>>Thomas
>>
>>
>>On Jul 20, 2007 10:06 AM, "Even, Roni" <roni.even@polycom.co.il>
>>wrote:
>>
>>>1. In section 1.1 you say "and deprecate the single NAL unit
>>>packetization mode of RFC 3984." I believe that you are not
>>>suggesting
>>>deprecating the usage of single NAL unit for H264 media subtype but
>>>only suggesting that it will not be used for the SVC payload type.
>>
>>Yes, when using H.264 in context with SVC, e.g. a SVC stream separated
>>in its H.264 base layer and the SVC enhancements. But for plain H.264,
>>we do not want to deprecate it, since it is a part of RFC3984.
>>
>>>
>>>
>>>
>>>2. If you suggest using SVC instead of H264 payload type as in
>>>section
>>>6.1 than I would strongly object to take out single NAL unit since
>>>this
>>>is the modes used in all video conferencing shipping products!!!! If
>>>you want to have interoperability with what you call "legacy" systems
>>>you must leave this mode. I also do not see any reason in section 6.5
>>>why to take this mode out except saying that STAP is easy to
>>>implement.
>>>
>>>Further mode, the single NAL unit mode was agreed by the H.264 expert
>>>in order to expedite implementation support.
>>>
>>
>>I am ok with your suggestion.
>>
>>
>>>
>>>
>>>3. I also question the claim in the introduction calling SVC a
>>>superset
>>>of H.264 since it is an annex in H.264 and does not cover all the
>>>modes
>>>of H.264. It does not encompass all the H.264 modes
>>>
>>>
>>You are right.
>>
>>>
>>>4. In the definition section I find the following definition very
>>>confusing. "scalable bitstream: A bitstream with the property that
>>>one
>>>or more bitstream subsets that are not identical to the scalable
>>>bitstream form another bitstream that conforms to the SVC
>>>specification."
>>>
>>
>>In H.264, there are the following definitions:
>>
>>bitstream: A sequence of bits that forms the representation of coded
>>pictures and associated data forming one or more coded video
>>sequences.
>>Bitstream is a collective term used to refer either to a NAL unit
>>stream
>>or a byte stream.
>>
>>bitstream subset: A bitstream that is derived as a subset from a
>>bitstream by discarding zero or more NAL units
>>
>>Maybe, we use these definitions for more clarity.
>>
>>>
>>>5. In section 6.1 in order to achieve the design goal of having a
>>>full
>>>compatibility between a SVC full base layer and RFC 3984
>>>encapsulation
>>>I suggest that the document will explain how to build such a packet
>>>and
>>>maybe recommend that systems that support SVC will be able to accept
>>>an
>>>H264 payload type.
>>>
>>
>>Good, we will incorporate that. But there may be also the case, where
>>no
>>backward compatibility is required. In that case, I would not like to
>>force the receiver supporting full RFC3984.
>>
>>>
>>>
>>>6. In 6.2 " The following applies in addition", there is nothing else
>>>in the section following the above sentence.
>>>
>>Yes, you are right, there was a note in the last draft about:
>>=C2=A0=C2=A0When layers of an SVC scalable bitstream are transported in m=
ore
>>=C2=A0=C2=A0than one RTP session, e.g. in layered multicast for which the=
 use
>>=C2=A0=C2=A0case is given in 13.2, session multiplexing MUST be used only=
 as RTP
>>=C2=A0=C2=A0multiplexing technique.
>>
>>We found that not helpful anymore. So, we may need to remove 6.2.
>>
>>>
>>>
>>>7. About the editor note in 6.6 I suggest explaining it in the SDP
>>>usage. In the IANA registration these are optional parameters.
>>>
>>Good.
>>
>>>
>>>
>>>8. In section 6.9 you define a new NAL unit type PACSI, is the
>>>purpose
>>>only for MANE devices. How does it go with section 13.6
>>>
>>I think section 13.6 can be removed anyway. That was useful for
>>explaining IETF philosophy but is not required for the final payload
>>draft.
>>
>>
>>>
>>>9. The PACSI NAL unit type is assigned a value (30) in this document.
>>>I
>>>did not see in H.264 or in any other place how you manage the
>>>allocation of the unspecified values preventing other applications
>>>from
>>>using this value.
>>>
>>In H.264, these types are left open for application usage:
>>In Table 7-1 the H.264 standard says these types are unspecified.
>>
>>>
>>>
>>>10 in section 7 " Informative note: When either the prefix NAL unit
>>>or
>>>the associated NAL unit containing an H.264/AVC coded slice is lost,
>>>the remaining one would be hardly useful in SVC context"
>>>
>>>I thought that you can decode without the prefix NAL unit. I also
>>>thought that its usage is optional.
>>>
>>
>>Exactly, you can decode it but you may not be able to use it as
>>reference for a SVC enhancement layer.
>>
>>>
>>>
>>>11. In section 7 "When Layers of a SVC bitstream are transported in
>>>more than one RTP session, the interleaved packetization mode MUST be
>>>used"
>>>
>>>Why is that, can you explain.
>>
>>We tried to explain that in section 14 of
>>draft-wenger-avt-rtp-svc-01.txt . In that section we tried to solve
>>the
>>problem of re-interleaving NAL untis from different RTP sessions to
>>one
>>SVC bistream. We found that this may be very complicated. On the other
>>hand it is very simple if using an extended cross-layer DON.
>>
>>>
>>>
>>>
>>>12 in 9.1 what do you mean by " The receiver MUST ignore any
>>>unspecified parameter"
>>>
>>Maybe, Stephan can reply on that.
>>
>>>
>>>
>>>13. in 9.1 you mention all optional parameters from RFC3984. There
>>>are
>>>now new parameters being specified.
>>>
>>>
>>>
>>>14. You define two new optional parameters sprop-scalability-info and
>>>sprop-layer-ids. What is the reason for these parameters, it looks to
>>>me that they duplicate information from the payload header. Also are
>>>thought parameters fixed during the session. Are they only for
>>>informational purposes.
>>>
>>
>>The scalability SEI (sprop-scalability-info) is useful, if someone
>>wants
>>to understand the whole SVC bitstream, e.g., which layers are
>>available
>>at which resolution or framerate. It also connects the NAL unti header
>>scalability identifier (PRID, DID, QID, TID) with such values.
>>The second parameter sprop-layer-ids is useful to describe in the
>>layered Multicast case which scalability levels of the whole bitstream
>>(described by sprop-scalability-info) are contained in an RTP session.
>>
>>>
>>>
>>>15. The payload type is defined as SVC, maybe it should be H264-SVC.
>>>
>>I have no preference.
>>
>>>
>>>
>>>16. Please replace the term MIME with payload type in the document.
>>>
>>
>>Ok.
>>
>>>
>>>
>>>Thanks
>>>
>>>Roni Even
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>


________________________________________________________
Thomas Schierl, Dipl.-Ing.
Fraunhofer HHI
Senior Research Engineer
Image Processing Dept. / Multimedia Streaming Tech.
Einsteinufer 37, 10587 Berlin, Germany
PHONE: +49 30 31002 227, FAX: +49 30 392 7200, WEB: ip.hhi.de
EMAIL: thomas.schierl@hhi.fraunhofer.de, SKYPE: thomas.schierl


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



From avt-bounces@ietf.org Sat Jul 21 09:06:10 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICEel-0001K3-04; Sat, 21 Jul 2007 09:05:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICEej-0001Jt-KS
	for avt@ietf.org; Sat, 21 Jul 2007 09:05:57 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ICEei-0008AG-3D
	for avt@ietf.org; Sat, 21 Jul 2007 09:05:57 -0400
Received: from [80.187.147.117] (port=50611 helo=[10.113.51.115])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1ICEeh-0005zM-1n; Sat, 21 Jul 2007 14:05:55 +0100
In-Reply-To: <E1I8JIk-0006Cs-6P@stiedprstage1.ietf.org>
References: <E1I8JIk-0006Cs-6P@stiedprstage1.ietf.org>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <2CD7768D-70A2-4149-9FD4-80096D8BD564@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-tfrc-profile-09.txt 
Date: Sat, 21 Jul 2007 10:14:58 +0100
To: Ladan Gharai <ladan@isi.edu>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On 10 Jul 2007, at 18:15, 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		: RTP with TCP Friendly Rate Control
> 	Author(s)	: L. Gharai
> 	Filename	: draft-ietf-avt-tfrc-profile-09.txt
> 	Pages		: 11
> 	Date		: 2007-7-10
> 	
> This memo specifies how the TCP Friendly Rate Control (TFRC) of RTP
>    flows can be supported using the RTP/AVPF profile and the  
> general RTP
>    header extension mechanism.  AVPF feedback packets and RTP header
>    extensions are defined to support the exchange of control  
> information
>    between RTP TFRC senders and receivers. TFRC is an equation-based
>    congestion control scheme for unicast flows operating in a best
>    effort Internet environment.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-tfrc-profile-09.txt

Reading this, I was surprised that timestamps are specified in  
microseconds, rather than RTP timestamp units. Is there a reason for  
this choice? Using RTP timestamp units would seem easier, since it  
requires only a single clock, and would also allow delta-coding of  
timestamp relative to the timestamp in the RTP header, to reduce  
packet sizes.

The IANA considerations section outlines what is needed in general,  
but needs to be specific about exactly what changes are needed to the  
registries.

The discussion of SDP usage is very limited. I think the draft needs  
to include an Offer/Answer considerations section, explaining how  
this is used in both negotiated and declarative modes. Examples of  
session setup messages using both SIP and (especially) RTSP would be  
useful.

Finally, the idnits tools finds a number of problems, which must be  
fixed before we can progress this draft:

   Checking nits according to http://www.ietf.org/ietf/1id- 
guidelines.txt:
   - No 'Intended status' indicated for this document; assuming Proposed
     Standard

   Checking references for intended status: Proposed Standard
   - Unused Reference: 'RFC2434' is defined on line 391, but not  
referenced
   - Unused Reference: 'RFC3551' is defined on line 400, but not  
referenced
   - Unused Reference: 'RFC4342' is defined on line 423, but not  
referenced
   * Obsolete Normative Reference: RFC 2327
   * Downref: Informational Normative Reference: RFC 4336
   - No information found for draft-ietf-avt-profile-savpf-xx - is  
the name
     correct?
   - Possible downref: Draft Normative Reference: ref. 'SAVPF'
   - No information found for draft-phelan-dccp-dtls-xx - is the name  
correct?
   - Possible downref: Draft Normative Reference: ref. 'ID.DTLS'

     Summary: 2 errors, 8 warnings

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



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



From avt-bounces@ietf.org Sun Jul 22 11:57:57 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICdod-00071M-JK; Sun, 22 Jul 2007 11:57:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICdob-0006tM-Nq
	for avt@ietf.org; Sun, 22 Jul 2007 11:57:49 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ICdoa-0008Bm-AB
	for avt@ietf.org; Sun, 22 Jul 2007 11:57:49 -0400
Received: from [67.97.210.2] (port=52767 helo=[172.28.171.181])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1ICdoY-0006lP-DX; Sun, 22 Jul 2007 16:57:46 +0100
In-Reply-To: <25218858.481184923166593.OPEN-XCHANGE.WebMail.tomcat@mail.hhi.fraunhofer.de>
References: <144ED8561CE90C41A3E5908EDECE315C04C22F98@IsrExch01.israel.polycom.com>
	<25218858.481184923166593.OPEN-XCHANGE.WebMail.tomcat@mail.hhi.fraunhofer.de>
Mime-Version: 1.0 (Apple Message framework v752.2)
X-Priority: 3 (normal)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <4C7938FB-D5C0-4262-A6EE-809199A9EDDB@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] comments on draft-ietf-avt-rtp-svc-02.txt
Date: Sun, 22 Jul 2007 10:57:09 -0500
To: Thomas Schierl <schierl@hhi.fhg.de>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: stewe@stewe.org, "Even, Roni" <roni.even@polycom.co.il>, avt@ietf.org,
	Ye-Kui.Wang@nokia.com
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On 20 Jul 2007, at 04:19, Thomas Schierl wrote:
...
> I think section 13.6 can be removed anyway. That was useful for
> explaining IETF philosophy but is not required for the final payload
> draft.

I think it's important to document bad ideas, and why they are a bad  
idea, so I would strongly prefer to keep that discussion in the final  
RFC.

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



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



From avt-bounces@ietf.org Sun Jul 22 14:48:04 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICgTF-0002By-08; Sun, 22 Jul 2007 14:47:57 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICgTE-0002BJ-F6
	for avt@ietf.org; Sun, 22 Jul 2007 14:47:56 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ICgTD-0007zN-W7
	for avt@ietf.org; Sun, 22 Jul 2007 14:47:56 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	51E53212A8; Sun, 22 Jul 2007 20:47:14 +0200 (CEST)
X-AuditID: c1b4fb3e-b1036bb0000007e1-73-46a3a632bc9d
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	2F3C120156; Sun, 22 Jul 2007 20:47:14 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 22 Jul 2007 20:47:13 +0200
Received: from [138.85.4.58] ([138.85.4.58]) by esealmw127.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 22 Jul 2007 20:47:12 +0200
Message-ID: <46A3A62E.5070701@ericsson.com>
Date: Sun, 22 Jul 2007 20:47:10 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-tfrc-profile-09.txt
References: <E1I8JIk-0006Cs-6P@stiedprstage1.ietf.org>
	<2CD7768D-70A2-4149-9FD4-80096D8BD564@csperkins.org>
In-Reply-To: <2CD7768D-70A2-4149-9FD4-80096D8BD564@csperkins.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Jul 2007 18:47:13.0040 (UTC)
	FILETIME=[B7906900:01C7CC90]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: Ladan Gharai <ladan@isi.edu>, AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Colin Perkins skrev:
> 
> Reading this, I was surprised that timestamps are specified in 
> microseconds, rather than RTP timestamp units. Is there a reason for 
> this choice? Using RTP timestamp units would seem easier, since it 
> requires only a single clock, and would also allow delta-coding of 
> timestamp relative to the timestamp in the RTP header, to reduce packet 
> sizes.

Actually I think using this is correct choice. Delta coding put 
restriction on how much difference there can be between the display and 
transport time can be or force a variable field length. having fixed 
length and delta codiding is not robust unless it is 32 bits.

Having one fixed timestamp rate avoids the whole issues with payload 
type switching resulting in clock rate changes. Thus avoiding to create 
additional issue with changing used payload types.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
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 Sun Jul 22 15:09:24 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICgnz-00033s-Bq; Sun, 22 Jul 2007 15:09:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICgnx-00033m-UH
	for avt@ietf.org; Sun, 22 Jul 2007 15:09:21 -0400
Received: from firewall-gw-dirty-n.packetdesign.com ([65.87.20.98]
	helo=mailman.packetdesign.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ICgnw-0003Bs-Em
	for avt@ietf.org; Sun, 22 Jul 2007 15:09:21 -0400
Received: from packetdesign.com (dns.packetdesign.com [192.168.0.254])
	by mailman.packetdesign.com (8.13.1/8.13.1) with ESMTP id
	l6MJ95Aw010242; Sun, 22 Jul 2007 12:09:06 -0700
Date: Sun, 22 Jul 2007 12:09:07 -0700 (PDT)
From: Stephen Casner <casner@acm.org>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-tfrc-profile-09.txt
In-Reply-To: <46A3A62E.5070701@ericsson.com>
Message-ID: <20070722120739.S3620@kao.packetdesign.com>
References: <E1I8JIk-0006Cs-6P@stiedprstage1.ietf.org>
	<2CD7768D-70A2-4149-9FD4-80096D8BD564@csperkins.org>
	<46A3A62E.5070701@ericsson.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: Ladan Gharai <ladan@isi.edu>, Colin Perkins <csp@csperkins.org>,
	AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On Sun, 22 Jul 2007, Magnus Westerlund wrote:

> Colin Perkins skrev:
> > 
> > Reading this, I was surprised that timestamps are specified in microseconds,
> > rather than RTP timestamp units. Is there a reason for this choice? Using
> > RTP timestamp units would seem easier, since it requires only a single
> > clock, and would also allow delta-coding of timestamp relative to the
> > timestamp in the RTP header, to reduce packet sizes.
> 
> Actually I think using this is correct choice. Delta coding put restriction on
> how much difference there can be between the display and transport time can be
> or force a variable field length. having fixed length and delta codiding is
> not robust unless it is 32 bits.
> 
> Having one fixed timestamp rate avoids the whole issues with payload type
> switching resulting in clock rate changes. Thus avoiding to create additional
> issue with changing used payload types.

On the other hand, having a clock rate unrelated to the media clock
introduces the problem of arithmetic errors.  We had a major debate
about this in the design of RTPv2 after RTPv1.

                                                        -- Steve

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



From avt-bounces@ietf.org Sun Jul 22 20:46:52 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICm4X-0008H7-NF; Sun, 22 Jul 2007 20:46:49 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICm4V-0008Fm-J6
	for avt@ietf.org; Sun, 22 Jul 2007 20:46:47 -0400
Received: from porter.east.isi.edu ([65.114.168.19])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ICm4V-0006Av-0M
	for avt@ietf.org; Sun, 22 Jul 2007 20:46:47 -0400
Received: from [192.168.1.101] (pool-70-108-44-91.res.east.verizon.net
	[70.108.44.91])
	by porter.east.isi.edu (Postfix) with ESMTP id 51A071CAC;
	Sun, 22 Jul 2007 20:46:46 -0400 (EDT)
In-Reply-To: <2CD7768D-70A2-4149-9FD4-80096D8BD564@csperkins.org>
References: <E1I8JIk-0006Cs-6P@stiedprstage1.ietf.org>
	<2CD7768D-70A2-4149-9FD4-80096D8BD564@csperkins.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <BC29FF89-8508-4D9D-876B-2312897C456C@ISI.EDU>
Content-Transfer-Encoding: 7bit
From: Ladan Gharai <ladan@ISI.EDU>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-tfrc-profile-09.txt
Date: Sun, 22 Jul 2007 20:46:41 -0400
To: Colin Perkins <csp@csperkins.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Colin:

Thank you for your comments. I have just submitted newer version  
incorporating all the comments I have received. Regarding the  
timestamps please see inline:

Ladan

On Jul 21, 2007, at 5:14 AM, Colin Perkins wrote:

> On 10 Jul 2007, at 18:15, 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		: RTP with TCP Friendly Rate Control
>> 	Author(s)	: L. Gharai
>> 	Filename	: draft-ietf-avt-tfrc-profile-09.txt
>> 	Pages		: 11
>> 	Date		: 2007-7-10
>> 	
>> This memo specifies how the TCP Friendly Rate Control (TFRC) of RTP
>>    flows can be supported using the RTP/AVPF profile and the  
>> general RTP
>>    header extension mechanism.  AVPF feedback packets and RTP header
>>    extensions are defined to support the exchange of control  
>> information
>>    between RTP TFRC senders and receivers. TFRC is an equation-based
>>    congestion control scheme for unicast flows operating in a best
>>    effort Internet environment.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-avt-tfrc- 
>> profile-09.txt
>
> Reading this, I was surprised that timestamps are specified in  
> microseconds, rather than RTP timestamp units. Is there a reason  
> for this choice? Using RTP timestamp units would seem easier, since  
> it requires only a single clock, and would also allow delta-coding  
> of timestamp relative to the timestamp in the RTP header, to reduce  
> packet sizes.

    The reasoning for using  microseconds timestamps is that these  
timestamps are used to measure the RTT time,  determine when a lost  
packet would/should have arrived, etc - essentially, these timestamps  
have really been added for  the "transport domain" rather than the  
"media domain". If the timestamps were is RTP timestamp units, a  
conversion to seconds would be needed before being used in the  
"transport domain", and so the logic is to avoid having to convert  
the timestamp in the main domain for which it will be used.

>
> The IANA considerations section outlines what is needed in general,  
> but needs to be specific about exactly what changes are needed to  
> the registries.

    I have added more specifics here.
>
> The discussion of SDP usage is very limited. I think the draft  
> needs to include an Offer/Answer considerations section, explaining  
> how this is used in both negotiated and declarative modes. Examples  
> of session setup messages using both SIP and (especially) RTSP  
> would be useful.

    I will add text on this in the next revision.
>
> Finally, the idnits tools finds a number of problems, which must be  
> fixed before we can progress this draft:

    done
>
>   Checking nits according to http://www.ietf.org/ietf/1id- 
> guidelines.txt:
>   - No 'Intended status' indicated for this document; assuming  
> Proposed
>     Standard
>
>   Checking references for intended status: Proposed Standard
>   - Unused Reference: 'RFC2434' is defined on line 391, but not  
> referenced
>   - Unused Reference: 'RFC3551' is defined on line 400, but not  
> referenced
>   - Unused Reference: 'RFC4342' is defined on line 423, but not  
> referenced
>   * Obsolete Normative Reference: RFC 2327
>   * Downref: Informational Normative Reference: RFC 4336
>   - No information found for draft-ietf-avt-profile-savpf-xx - is  
> the name
>     correct?
>   - Possible downref: Draft Normative Reference: ref. 'SAVPF'
>   - No information found for draft-phelan-dccp-dtls-xx - is the  
> name correct?
>   - Possible downref: Draft Normative Reference: ref. 'ID.DTLS'
>
>     Summary: 2 errors, 8 warnings
>
> -- 
> Colin Perkins
> http://csperkins.org/
>
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>


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



From avt-bounces@ietf.org Mon Jul 23 09:45:13 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICyDc-0006SP-EA; Mon, 23 Jul 2007 09:45:00 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICyDb-0006SE-76
	for avt@ietf.org; Mon, 23 Jul 2007 09:44:59 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ICyDa-0005Sh-Iw
	for avt@ietf.org; Mon, 23 Jul 2007 09:44:59 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	5B0CE21724; Mon, 23 Jul 2007 15:44:57 +0200 (CEST)
X-AuditID: c1b4fb3e-ae831bb0000007e1-16-46a4b0d9f0cc
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	3A1C32104B; Mon, 23 Jul 2007 15:44:57 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 23 Jul 2007 15:44:56 +0200
Received: from [138.85.4.117] ([138.85.4.117]) by esealmw127.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 23 Jul 2007 15:44:55 +0200
Message-ID: <46A4B0D6.5030607@ericsson.com>
Date: Mon, 23 Jul 2007 15:44:54 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: Stephen Casner <casner@acm.org>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-tfrc-profile-09.txt
References: <E1I8JIk-0006Cs-6P@stiedprstage1.ietf.org>
	<2CD7768D-70A2-4149-9FD4-80096D8BD564@csperkins.org>
	<46A3A62E.5070701@ericsson.com>
	<20070722120739.S3620@kao.packetdesign.com>
In-Reply-To: <20070722120739.S3620@kao.packetdesign.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Jul 2007 13:44:56.0244 (UTC)
	FILETIME=[A79AB740:01C7CD2F]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: Ladan Gharai <ladan@isi.edu>, Colin Perkins <csp@csperkins.org>,
	AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Stephen Casner skrev:
> On Sun, 22 Jul 2007, Magnus Westerlund wrote:
> 
>> Colin Perkins skrev:
>>> Reading this, I was surprised that timestamps are specified in microseconds,
>>> rather than RTP timestamp units. Is there a reason for this choice? Using
>>> RTP timestamp units would seem easier, since it requires only a single
>>> clock, and would also allow delta-coding of timestamp relative to the
>>> timestamp in the RTP header, to reduce packet sizes.
>> Actually I think using this is correct choice. Delta coding put restriction on
>> how much difference there can be between the display and transport time can be
>> or force a variable field length. having fixed length and delta codiding is
>> not robust unless it is 32 bits.
>>
>> Having one fixed timestamp rate avoids the whole issues with payload type
>> switching resulting in clock rate changes. Thus avoiding to create additional
>> issue with changing used payload types.
> 
> On the other hand, having a clock rate unrelated to the media clock
> introduces the problem of arithmetic errors.  We had a major debate
> about this in the design of RTPv2 after RTPv1.
> 

But, the usage of this clock is not related to the media. It is used to 
determine if you can send a packet or not. So I am wondering if the 
arithmetic error has any real impact.

Cheers

Magnus Westerlund

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

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



From avt-bounces@ietf.org Mon Jul 23 10:23:29 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICyoo-00005w-Pk; Mon, 23 Jul 2007 10:23:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICyon-00005j-Dl
	for avt@ietf.org; Mon, 23 Jul 2007 10:23:25 -0400
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.43)
	id 1ICyom-0007mK-GT for avt@ietf.org; Mon, 23 Jul 2007 10:23:25 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-2.cisco.com with ESMTP; 23 Jul 2007 07:23:24 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aq4HACpWpEarR7PE/2dsb2JhbACQQg
X-IronPort-AV: i="4.16,570,1175497200"; 
	d="scan'208"; a="387420417:sNHT35237950"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l6NENN59016091
	for <avt@ietf.org>; Mon, 23 Jul 2007 07:23:23 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l6NEMjSx020989
	for <avt@ietf.org>; Mon, 23 Jul 2007 14:23:23 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 23 Jul 2007 07:23:22 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 23 Jul 2007 07:22:52 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D5404D3ED7C@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <E1I80ZR-0008SA-Qn@stiedprstage1.ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-ietf-avt-rtcpxr-video-01.txt 
Thread-Index: AcfCbkRoiH7gZOylRoCcTKkC3S33BQKxhbTQ
References: <E1I80ZR-0008SA-Qn@stiedprstage1.ietf.org>
From: "Ali Begen \(abegen\)" <abegen@cisco.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 23 Jul 2007 14:23:22.0669 (UTC)
	FILETIME=[06573DD0:01C7CD35]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5507; t=1185200603;
	x=1186064603; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=abegen@cisco.com;
	z=From:=20=22Ali=20Begen=20\(abegen\)=22=20<abegen@cisco.com>
	|Subject:=20Comments=20on=20draft-ietf-avt-rtcpxr-video-01.txt=20
	|Sender:=20; bh=hy7SzHRjv7TLrbdfIfYGMozhd5nAdFkf/Q/fLa7cgto=;
	b=WAb87WHN899E50z2u2kAcoEHucMaP9mplX1sYh6SPp8vvvn34Y1JhmP/ahyZeulfH4FfSTIy
	ibXQPgdvF1HQUZ3HDpL7FOcoov79YBmwJ/Ft0fRgI3GxNGXaKGeJ1shY;
Authentication-Results: sj-dkim-4; header.From=abegen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: -3.6 (---)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Subject: [AVT] Comments on draft-ietf-avt-rtcpxr-video-01.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hello,

I have some questions and suggestions for the RTCP XR video draft. I am
hoping to discuss these in today's session.

Questions Regarding Existing Fields:

1) Proportion of impaired I/BP frames:
It should be made clear how the proportion of impaired frames is defined
and can be computed.=20
Example: Assume that the measurement interval is one GOP duration, and
the I-frame for the current GOP is lost.=20
- Is the proportion of impaired B and P frames (denoted by X) 100%?
- Does the value of X depend on the successful and on-time arrival of B
or P frames? Or, as they cannot be decoded already in case of an I-frame
loss, is X 100%?

2) Loss rate within BP frames:
Is this the absolute loss rate within BP frames or does it include the
discarded frames/slices due to missing ancestor frames? (Related to the
previous question)

3) Max GOP length:
This is computed in a way such that it is a non-decreasing function of
time. Thus, it keeps the value of the largest GOP size that has been
seen since it was reset.
- Does MGOP span the whole session or only the interval during which the
measurement is made?
Knowing the value of the largest GOP size that has been seen since the
beginning of the session might give the decoder an idea of how the
encoder is working, although an information from several hours ago won't
say much.=20
- Similarly, is mean GOP length reset at some point?

4) Proportion of time below MOS threshold:
MOS can be calculated over an observation interval (which can be the
measurement interval). It is difficult to define/compute MOS over very
short intervals (e.g., per frame). Thus, it is even more difficult to
find the proportion of time below MOS threshold. How can we compute this
value?

5) PSNR fields:
What is the suggested way to "estimate" the PSNR without the reference
frames?


Possible Field Additions:

1) Proportion of total frame losses:
Some decoder hardware chips do not support reporting individual B/P
frame loss rates. For such cases, we should support a field that reports
the aggregated loss rate for whole frame types.

2) PCR discontinuity counter: (aggregate number of discontinuities seen)
Maybe useful when tracking is lost due to open loop NLL.

3) Separate fields for video playout underrun and overrun counts:
Playout interrupt count field only counts the number of interrupts due
to buffer underrun. Some hardware chips flush out the buffer when an
overrun occurs. Having a separate field for overruns may signal the
encoder/transmitter to adjust the encoding/transmission rate.

Thanks,
-Ali

--
Ali C. Begen, Ph.D.

Software Engineer
Video Content & Networking Business Unit
Cisco Systems, Inc.
San Jose, CA 95134 USA
w. +1 (408) 525-7308


> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20
> Sent: Monday, July 09, 2007 2:15 PM
> To: i-d-announce@ietf.org
> Cc: avt@ietf.org
> Subject: [AVT] I-D ACTION:draft-ietf-avt-rtcpxr-video-01.txt=20
>=20
> A New Internet-Draft is available from the on-line=20
> Internet-Drafts directories.
> This draft is a work item of the Audio/Video Transport=20
> Working Group of the IETF.
>=20
> 	Title		: RTCP XR - Video Metrics Report Blocks
> 	Author(s)	: A. Clark, A. Pendleton
> 	Filename	: draft-ietf-avt-rtcpxr-video-01.txt
> 	Pages		: 0
> 	Date		: 2007-7-9
> =09
> This document defines extensions to the RTCP XR extended report
>    packet type blocks to support the monitoring of video over IP=20
>    for IPTV and videoconferencing endpoint reporting.
>    [Note that the audio and transport metric report blocks contained
>    in the -00 draft have been moved to separate drafts.]
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcpxr-video-01.txt
>=20
> To remove yourself from the I-D Announcement list, send a=20
> message to i-d-announce-request@ietf.org with the word=20
> unsubscribe in the body of the message.=20
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>=20
> Internet-Drafts are also available by anonymous FTP. Login=20
> with the username "anonymous" and a password of your e-mail=20
> address. After logging in, type "cd internet-drafts" and then=20
> "get draft-ietf-avt-rtcpxr-video-01.txt".
>=20
> A list of Internet-Drafts directories can be found in=20
> http://www.ietf.org/shadow.html or=20
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
> Internet-Drafts can also be obtained by e-mail.
>=20
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-avt-rtcpxr-video-01.txt".
> =09
> 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=20
> 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.
>=20
> Below is the data which will enable a MIME compliant mail=20
> reader implementation to automatically retrieve the ASCII=20
> version of the Internet-Draft.
>=20

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



From avt-bounces@ietf.org Mon Jul 23 11:08:33 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICzWS-0002A2-8v; Mon, 23 Jul 2007 11:08:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICzWQ-000239-LW
	for avt@ietf.org; Mon, 23 Jul 2007 11:08:30 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ICzWP-0000Hz-7o
	for avt@ietf.org; Mon, 23 Jul 2007 11:08:30 -0400
Received: from dhcp-1398.ietf69.org ([130.129.19.152]:53696)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1ICzWO-0003EP-Il for avt@ietf.org; Mon, 23 Jul 2007 16:08:28 +0100
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: 7bit
Message-Id: <E463373A-A94D-4EC9-A2BD-A5CBBEE55F88@csperkins.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: AVT WG <avt@ietf.org>
From: Colin Perkins <csp@csperkins.org>
Date: Mon, 23 Jul 2007 10:08:29 -0500
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: [AVT] Meeting today
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

The AVT working group will meet at 3:20pm today in the State  
Ballroom. Copies of the presentation materials that will be used are  
now available from the IETF web site: https://datatracker.ietf.org/ 
meeting/69/materials.html

A jabber chat room is available (avt@jabber.ietf.org). Details of the  
Jabber service can be found at http://www.ietf.org/meetings/ 
text_conf.html

Audio from the meeting will be recorded, and made available for  
streaming via http://videolab.uoregon.edu/events/ietf/ (channel 1)

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



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



From avt-bounces@ietf.org Mon Jul 23 15:15:19 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID3NC-0001fD-Ru; Mon, 23 Jul 2007 15:15:14 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID3N1-0000t6-6M; Mon, 23 Jul 2007 15:15:03 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1ID3N0-00073Z-Fu; Mon, 23 Jul 2007 15:15:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 30B4917606;
	Mon, 23 Jul 2007 19:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1ID3Mz-0005Oi-PL; Mon, 23 Jul 2007 15:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1ID3Mz-0005Oi-PL@stiedprstage1.ietf.org>
Date: Mon, 23 Jul 2007 15:15:01 -0400
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtcpxr-mpts-00.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: RTCP XR - MPEG Transport Metrics Report Block
	Author(s)	: A. Clark
	Filename	: draft-ietf-avt-rtcpxr-mpts-00.txt
	Pages		: 
	Date		: 2007-7-23
	

   This document defines an extension to the RTCP XR extended report
   packet type blocks to support the monitoring of video over IP 
   and the associated audio streams, if present, for video encapsulated
   in MPEG Transport carried over RTP.
   [Note: this draft contains the MPEG transport metrics that were
   formerly in the draft-ietf-avt-rtcpxr-video-00.txt draft, which has
   now been divided into four drafts]


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcpxr-mpts-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-rtcpxr-mpts-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-rtcpxr-mpts-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

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

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

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

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

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

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


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org Mon Jul 23 15:47:08 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID3s2-0008Vb-UT; Mon, 23 Jul 2007 15:47:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID3s1-0008Po-Sw
	for avt@ietf.org; Mon, 23 Jul 2007 15:47:05 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ID3s0-0001RJ-Ex
	for avt@ietf.org; Mon, 23 Jul 2007 15:47:05 -0400
Received: from dhcp-17ed.ietf69.org ([130.129.23.237]:54307)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1ID3rz-0004Dm-G0; Mon, 23 Jul 2007 20:47:03 +0100
In-Reply-To: <BC29FF89-8508-4D9D-876B-2312897C456C@ISI.EDU>
References: <E1I8JIk-0006Cs-6P@stiedprstage1.ietf.org>
	<2CD7768D-70A2-4149-9FD4-80096D8BD564@csperkins.org>
	<BC29FF89-8508-4D9D-876B-2312897C456C@ISI.EDU>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <D6D7945A-EB54-4386-B2A4-4697607A1E08@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-tfrc-profile-09.txt
Date: Mon, 23 Jul 2007 14:47:04 -0500
To: Ladan Gharai <ladan@ISI.EDU>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On 22 Jul 2007, at 19:46, Ladan Gharai wrote:
...
>> Reading this, I was surprised that timestamps are specified in  
>> microseconds, rather than RTP timestamp units. Is there a reason  
>> for this choice? Using RTP timestamp units would seem easier,  
>> since it requires only a single clock, and would also allow delta- 
>> coding of timestamp relative to the timestamp in the RTP header,  
>> to reduce packet sizes.
>
>    The reasoning for using  microseconds timestamps is that these  
> timestamps are used to measure the RTT time,  determine when a lost  
> packet would/should have arrived, etc - essentially, these  
> timestamps have really been added for  the "transport domain"  
> rather than the "media domain". If the timestamps were is RTP  
> timestamp units, a conversion to seconds would be needed before  
> being used in the "transport domain", and so the logic is to avoid  
> having to convert the timestamp in the main domain for which it  
> will be used.

But the RTT can be derived from RTCP SR packets, and determining when  
a packet should have arrived is a feature of the playout buffer,  
which derives from the RTP timestamp. It seems that using  
microseconds just forces the implementation to use an additional  
clock for little reason (rather than implement all the TFRC timing  
logic using the RTP clock).

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



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



From avt-bounces@ietf.org Mon Jul 23 15:56:17 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID40s-00014v-5b; Mon, 23 Jul 2007 15:56:14 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID40m-0000t9-2B; Mon, 23 Jul 2007 15:56:08 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1ID40l-0000LV-JA; Mon, 23 Jul 2007 15:56:07 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 23 Jul 2007 15:56:07 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CACalpEZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,572,1175486400"; 
	d="scan'208"; a="126801974:sNHT29190148"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6NJu6Zx023742; 
	Mon, 23 Jul 2007 15:56:06 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6NJtvWs017987; 
	Mon, 23 Jul 2007 19:56:06 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 23 Jul 2007 15:55:41 -0400
Received: from [10.86.242.144] ([10.86.242.144]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 23 Jul 2007 15:55:41 -0400
Message-ID: <46A507C5.5060206@cisco.com>
Date: Mon, 23 Jul 2007 15:55:49 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: IETF SIP List <sip@ietf.org>, IETF Sipping List <sipping@ietf.org>,
	IETF MMUSIC WG <mmusic@ietf.org>, Behave WG <behave@ietf.org>,
	P2PSIP WG <p2psip@ietf.org>, rai@ietf.org, "'avt@ietf.org'" <avt@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Jul 2007 19:55:41.0404 (UTC)
	FILETIME=[72C0C1C0:01C7CD63]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1840; t=1185220566;
	x=1186084566; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20ICE=20tutorial=20in=20Chicago=20is=20CONFIRMED=20[DO=20NOT=20
	REPLY]=20-=20lunch=20logistics=0A=20below |Sender:=20
	|To:=20IETF=20SIP=20List=20<sip@ietf.org>,
	=20IETF=20Sipping=20List=20<sip ping@ietf.org>,
	=0A=20=20=20=20=20=20=20=20IETF=20MMUSIC=20WG=20<mmusic@iet
	f.org>, =20Behave=20WG=20<behave@ietf.org>,
	=0A=20=20=20=20=20=20=20=20P2PSI
	P=20WG=20<p2psip@ietf.org>, =20rai@ietf.org,
	=0A=20=20=20=20=20=20=20=20=22'
	avt@ietf.org'=22=20<avt@ietf.org>;
	bh=KpxqDxUhtprUSwrX98Ct3c1X0mBsvpY4gzyMN2aH5Go=;
	b=Ncyw7y256jwE7lC5Q5QuZfDCdjVn1oabrjGvlOL+VyhF0ZalmP15rKSMhRmaAGHHsSvG2PuK
	zZyuKd5iE8415bdWZIZuxeIGqTOje15E+zSKCePNlEj5RGkZbwjUABDm;
Authentication-Results: rtp-dkim-2; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: 
Subject: [AVT] ICE tutorial in Chicago is CONFIRMED [DO NOT REPLY] - lunch
 logistics below
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org



(Apologies to multiple recipients)
(DO NOT REPLY)

WHAT:     Tutorial on Interactive Connectivity Establishment (ICE)
      (http://www.ietf.org/internet-drafts/draft-ietf-mmusic-ice-17.txt)

           Slides:
           http://www.jdrosen.net/papers/ice-ietf-tutorial2.ppt

WHEN:     Tuesday, July 24, 2007, 1145-1245
           lunch will be available to those who RSVPd previously
           sandwiches, chips, salad and drinks
           $20/head - please pay Jonathan R. after the tutorial

WHERE:    Red Lacquar
           MP3 streaming hopefully available at:
           http://videolab.uoregon.edu/events/ietf/ietf694.m3u

WHO:      Anyone that would like to learn more about ICE.

WHY:      ICE, developed by the mmusic working group, has been
           defined as the IETF tool for NAT traversal for SIP-based
           media. It is also seeing increased usage for traversal
           for other kinds of application traffic - anything worrying
           about any-to-any communications. In this tutorial, we will
           overview the background of the problem, consider the
           requirements driving ICE, and provide an overview of
           how ICE works. An understanding of SIP is not required.
           The tutorial will be based on the pending -17 version.

RSVP:     Anyone may attend without RSVP, but lunch may not be
           there for you if you have not RSVPd previously. I've ordered
           a few extra


!DO NOT REPLY TO THIS NOTE!
-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Cisco Fellow                                   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com


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



From avt-bounces@ietf.org Mon Jul 23 16:32:31 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID4Zt-0004dO-Fq; Mon, 23 Jul 2007 16:32:25 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID4Zs-0004dD-E7
	for avt@ietf.org; Mon, 23 Jul 2007 16:32:24 -0400
Received: from mx.cbeyond.com ([66.180.96.58])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ID4Zr-0001dT-Ok
	for avt@ietf.org; Mon, 23 Jul 2007 16:32:24 -0400
Received: from [130.129.20.96] (port=4452 helo=TELCHADCPC)
	by mx.cbeyond.com with asmtp (Exim 4.34)
	id 1ID4Zp-0001Y0-6l; Mon, 23 Jul 2007 16:32:23 -0400
From: "Alan Clark" <alan.d.clark@telchemy.com>
To: "'Ali Begen \(abegen\)'" <abegen@cisco.com>
Subject: RE: [AVT] Comments on draft-ietf-avt-rtcpxr-video-01.txt 
Date: Mon, 23 Jul 2007 16:31:07 -0400
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.2962
Thread-Index: AcfCbkRoiH7gZOylRoCcTKkC3S33BQKxhbTQAAyjK0A=
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D5404D3ED7C@xmb-sjc-215.amer.cisco.com>
X-Spam-Score: 1.6 (+)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org
Message-Id: <E1ID4Zt-0004dO-Fq@megatron.ietf.org>

Hi Ali

I look forward to answering your questions this afternoon in the meeting
however:-


1) Proportion of impaired I/BP frames:
It should be made clear how the proportion of impaired frames is defined and
can be computed. 
Example: Assume that the measurement interval is one GOP duration, and the
I-frame for the current GOP is lost. 
- Is the proportion of impaired B and P frames (denoted by X) 100%?
- Does the value of X depend on the successful and on-time arrival of B or P
frames? Or, as they cannot be decoded already in case of an I-frame loss, is
X 100%?

> An interval would be at least a typical inter-RTCP gap, which may be 5-20
seconds and hence would not normally span a single GoP.  This metric does
not consider error propagation through the GoP.  The expectation is that a
high proportion of impaired I frames would lead to extensive error
propagation.


2) Loss rate within BP frames:
Is this the absolute loss rate within BP frames or does it include the
discarded frames/slices due to missing ancestor frames? (Related to the
previous question)

> This is the loss rate in received frames, and does not take into account
propagation.  The loss rate in I and BP frames is intended to support
network problem identification (e.g. high I frame loss rate may indicate
self induced congestion)

3) Max GOP length:
This is computed in a way such that it is a non-decreasing function of time.
Thus, it keeps the value of the largest GOP size that has been seen since it
was reset.
- Does MGOP span the whole session or only the interval during which the
measurement is made?
Knowing the value of the largest GOP size that has been seen since the
beginning of the session might give the decoder an idea of how the encoder
is working, although an information from several hours ago won't say much. 
- Similarly, is mean GOP length reset at some point?

> This would be the largest GoP seen during the measurement interval.  

4) Proportion of time below MOS threshold:
MOS can be calculated over an observation interval (which can be the
measurement interval). It is difficult to define/compute MOS over very short
intervals (e.g., per frame). Thus, it is even more difficult to find the
proportion of time below MOS threshold. How can we compute this value?

> It is possible to compute an estimated short term MOS - although
subjective tests do use typically 10-20 second samples.  

5) PSNR fields:
What is the suggested way to "estimate" the PSNR without the reference
frames?

> I'll explain in more detail later - however to provide an example - a
decoder does know what proportion of the macroblocks in the decoded image
needed to be concealed, and does know what concealment method was used -
this does enable an approximation to PSNR to be computed.  This approach is
already used by some video decoders.

Possible Field Additions:

1) Proportion of total frame losses:
Some decoder hardware chips do not support reporting individual B/P frame
loss rates. For such cases, we should support a field that reports the
aggregated loss rate for whole frame types.

> Agreed

2) PCR discontinuity counter: (aggregate number of discontinuities seen)
Maybe useful when tracking is lost due to open loop NLL.

> There is a separate draft on MPEG Transport metrics which includes this
(draft-ietf-avt-rtcpxr-mpts-00.txt)

3) Separate fields for video playout underrun and overrun counts:
Playout interrupt count field only counts the number of interrupts due to
buffer underrun. Some hardware chips flush out the buffer when an overrun
occurs. Having a separate field for overruns may signal the
encoder/transmitter to adjust the encoding/transmission rate.

> I'd like to discuss this further however it seems reasonable

Regards

Alan




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



From avt-bounces@ietf.org Mon Jul 23 16:36:03 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID4dM-00015S-Qk; Mon, 23 Jul 2007 16:36:00 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID4dL-00015N-Eo
	for avt@ietf.org; Mon, 23 Jul 2007 16:35:59 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ID4dL-0001kr-2U
	for avt@ietf.org; Mon, 23 Jul 2007 16:35:59 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-5.cisco.com with ESMTP; 23 Jul 2007 13:35:58 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aq4HAEqupEarR7MV/2dsb2JhbACQQg
X-IronPort-AV: i="4.16,572,1175497200"; 
	d="scan'208"; a="167894678:sNHT24698925"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6NKZwU4009509; 
	Mon, 23 Jul 2007 13:35:58 -0700
Received: from [130.129.87.120] (sjc-vpn3-532.cisco.com [10.21.66.20])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l6NKZv4w008484;
	Mon, 23 Jul 2007 20:35:57 GMT
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <E1BDD6A6-D6A3-4A5A-8760-28F86E92ABFD@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Date: Mon, 23 Jul 2007 16:35:46 -0400
To: Alan Clark <alan.d.clark@telchemy.com>
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=400; t=1185222958;
	x=1186086958; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=oran@cisco.com;
	z=From:=20David=20R=20Oran=20<oran@cisco.com>
	|Subject:=20Real=20dumb=20nit=20on=20draft-ietf-avt-rtcpxr-mpts-00
	|Sender:=20; bh=Ek4Lf/yov+2PYMiObDCdfwBg+lz1L6loow7xoS1uYeo=;
	b=bv4X8zYRRG6aTC5kx6bhGcFNshwBnZ+aO/rEDNRRvzb6hckQW08scWRhiMYG+OpILzrfxpda
	Ss1UoTwRcjKJZRNjNSdwbZWxDg8FHTQVvsLtOxYR6miKPnDSaX5Q4gxI0qVwhyXI77OljODjf0
	YJCddqHu8NOvbUHh1MOhM7bdg=;
Authentication-Results: sj-dkim-1; header.From=oran@cisco.com; dkim=pass (si
	g from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Cc: AVT WG <avt@ietf.org>
Subject: [AVT] Real dumb nit on draft-ietf-avt-rtcpxr-mpts-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

the Title is "RTCP XR - MPEG Transport Metrics Report Block"

but the file name says "mpts", which could be easily construed to  
have things only apply to MPTSs (multi-program transport streams) and  
not to SPTSs (single-program transport streams) as well.

I was all ready to complain about the content based on this, and was  
relieved that there was nothing restricting the use to mpts.

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



From avt-bounces@ietf.org Mon Jul 23 16:44:42 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID4lg-0001ks-3g; Mon, 23 Jul 2007 16:44:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID4lf-0001kl-E6
	for avt@ietf.org; Mon, 23 Jul 2007 16:44:35 -0400
Received: from mx.cbeyond.com ([66.180.96.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ID4lf-0003Bk-4A
	for avt@ietf.org; Mon, 23 Jul 2007 16:44:35 -0400
Received: from [130.129.20.96] (port=4539 helo=TELCHADCPC)
	by mx.cbeyond.com with esmtpa (Exim 4.62)
	(envelope-from <alan.d.clark@telchemy.com>)
	id 1ID4le-0003Dw-Lf; Mon, 23 Jul 2007 16:44:34 -0400
From: "Alan Clark" <alan.d.clark@telchemy.com>
To: "'David R Oran'" <oran@cisco.com>
Subject: RE: [AVT] Real dumb nit on draft-ietf-avt-rtcpxr-mpts-00
Date: Mon, 23 Jul 2007 16:43:23 -0400
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.2962
Thread-Index: AcfNaRdUZXNgHY/aQv6fVCDphHbWtAAAO8hw
In-Reply-To: <E1BDD6A6-D6A3-4A5A-8760-28F86E92ABFD@cisco.com>
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: 'AVT WG' <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org
Message-Id: <E1ID4lg-0001ks-3g@megatron.ietf.org>


Would it help if the draft were renamed "-rtcpxr-mpegts-" ?

Alan
 

-----Original Message-----
From: David R Oran [mailto:oran@cisco.com] 
Sent: Monday, July 23, 2007 4:36 PM
To: Alan Clark
Cc: AVT WG
Subject: [AVT] Real dumb nit on draft-ietf-avt-rtcpxr-mpts-00

the Title is "RTCP XR - MPEG Transport Metrics Report Block"

but the file name says "mpts", which could be easily construed to have
things only apply to MPTSs (multi-program transport streams) and not to
SPTSs (single-program transport streams) as well.

I was all ready to complain about the content based on this, and was
relieved that there was nothing restricting the use to mpts.

_______________________________________________
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 Jul 23 17:51:58 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID5oq-000140-Kp; Mon, 23 Jul 2007 17:51:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID5oo-00013v-PM
	for avt@ietf.org; Mon, 23 Jul 2007 17:51:54 -0400
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.43)
	id 1ID5oo-0004eV-6p for avt@ietf.org; Mon, 23 Jul 2007 17:51:54 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-3.cisco.com with ESMTP; 23 Jul 2007 14:51:37 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aq4HAHq/pEarR7PD/2dsb2JhbACQQQ
X-IronPort-AV: i="4.16,572,1175497200"; 
	d="scan'208"; a="506150311:sNHT547390856"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l6NLpajM006270
	for <avt@ietf.org>; Mon, 23 Jul 2007 14:51:36 -0700
Received: from [130.129.87.120] (sjc-vpn3-532.cisco.com [10.21.66.20])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6NLpaA0027702
	for <avt@ietf.org>; Mon, 23 Jul 2007 21:51:36 GMT
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <85C414B9-E725-40F0-B27C-19BB1F200041@cisco.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: AVT WG <avt@ietf.org>
From: David R Oran <oran@cisco.com>
Date: Mon, 23 Jul 2007 17:51:25 -0400
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2186; t=1185227496;
	x=1186091496; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=oran@cisco.com;
	z=From:=20David=20R=20Oran=20<oran@cisco.com>
	|Subject:=20Suggestion=20for=20how=20to=20handle=20derived/computed=20met
	ric=20in=20draft-avt-rtcpxr-* |Sender:=20;
	bh=1FrEGTLlYRNTMM8iIdvLEinNZZrx+P81k0shqpBgC/E=;
	b=A6stGMPhYGVPuTqcqLpwo3gFqC0x5vAsFXSx2/euFnQO6UZjabVDHTRFEGEdy2mQRROA41uK
	W/msmTuBNf6c/DJxyEvY8wxXwZtQPM97Dy2tAoq22BXauVZJ71f68dUJ;
Authentication-Results: sj-dkim-3; header.From=oran@cisco.com; dkim=pass (si
	g from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: -3.6 (---)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: [AVT] Suggestion for how to handle derived/computed metric in
	draft-avt-rtcpxr-*
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

At the Mic during the AVT session I sketched a vague idea for how to  
resolve the conflict between the desire on the part of many folks to  
only carry raw/primitive instrumented measurements in RTCP-XR, and  
other equally vocal, who argued for carrying the derived/computed  
metrics as well.

I won't repeat the pro/con arguments here. Let's assume we want to  
carry both.

The chairs asked me to write up my vague thoughts as the beginnings  
of a concrete proposal.

Some particular technical difficulties with the derived metrics that  
makes them different from the primitive measurements is:
- there are competing standards for how to compute them
- the results are not generally aggregatable, comparable, or self- 
describing.
- the set of interesting derived metrics is not small and seems to be  
growing, so it will be difficult to nail these down for stable RTCP  
reporting.

This makes it problematic to mix primitive and derived metrics in the  
same metric blocks in RTCP.

So, my suggestion is to do the following.

- A standards body who defines one or more consistent derived metrics  
may create (by bringing a draft to IETF) a separate metric block for  
those metrics.
- The block and its contained derived/computed metrics would be  
completely self-describing in terms of exactly what version of what  
standard defines the block.
- The definition of the metric would explicit contain the input  
variables, in order to ensure that those inputs are separately  
available as primitive metrics in the RTCP-XR. This increases the  
probability that any metric that is computable by the endpoint is  
also computable by a central element receiving and processing RTCP-XR  
reports.
- If there are competing/overlapping blocks, an endpoint need not do  
all of them and there would be no confusion about exactly which  
(e.g."video MOS") calculation was done.

As an aside, I would rather not see further updates to the existing  
drafts until we resolve this issue, since this is in fact major  
surgery to the documents that is best done before polishing the text  
and individual metric definitions.

Dave Oran.

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



From avt-bounces@ietf.org Mon Jul 23 18:03:20 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID5zr-0002dP-FU; Mon, 23 Jul 2007 18:03:19 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID5zq-0002dK-Cq
	for avt@ietf.org; Mon, 23 Jul 2007 18:03:18 -0400
Received: from expint.psytechnics.com ([217.33.106.234])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ID5zp-0003k7-V2
	for avt@ietf.org; Mon, 23 Jul 2007 18:03:18 -0400
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
Date: Mon, 23 Jul 2007 23:05:08 +0100
Message-ID: <257B18BFF522214E92EB52F3478B014EA0A357@psy01exch.intra.psytechnics.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Reporting blocks
thread-index: AcfNc/ypmcfKd1aXRnm3SVFEB8oxawAAE8sg
From: "Ravi Raviraj" <ravi.raviraj@psytechnics.com>
To: "AVT WG" <avt@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Subject: [AVT] Reporting blocks
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Further to the discussion this afternoon on metrics and MOS blocks.
Yes, there are confusions on what is reported.
I suggest the following
- We separate the MOS and keep it as a separate block. We could carry
other metrics as one mo more blocks (based on some logical grouping).
- Furthermore, all items reported should be items well defined by a
standard group. We should not define any new parameters within IETF
(unless it is something very trivial and obvious like total number of
packets or number of packets lost).

Ravi.
Ravi Raviraj.



This email and attachment are confidential. If you have received this =
message in error, please notify the sender immediately and delete the =
message from your computer. Psytechnics Ltd has taken steps to ensure =
that this email is virus free but the recipient should take necessary =
steps to make certain.

Company Name : Psytechnics Ltd
Registered Number : 4110724
Registered Office : Fraser House, 23 Museum St, Ipswich, Suffolk, IP1 =
1HN, UK
Registration : England and Wales


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



From avt-bounces@ietf.org Mon Jul 23 18:09:39 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID65x-0007yS-Vo; Mon, 23 Jul 2007 18:09:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID65u-0007yD-Mg
	for avt@ietf.org; Mon, 23 Jul 2007 18:09:34 -0400
Received: from mx.cbeyond.com ([66.180.96.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ID65u-00057x-5R
	for avt@ietf.org; Mon, 23 Jul 2007 18:09:34 -0400
Received: from [130.129.16.53] (port=4752 helo=TELCHADCPC)
	by mx.cbeyond.com with esmtpa (Exim 4.62)
	(envelope-from <alan.d.clark@telchemy.com>)
	id 1ID6AX-0004bP-6V; Mon, 23 Jul 2007 18:14:23 -0400
From: "Alan Clark" <alan.d.clark@telchemy.com>
To: "'David R Oran'" <oran@cisco.com>,
	"'AVT WG'" <avt@ietf.org>
Subject: RE: [AVT] Suggestion for how to handle derived/computed metric
	indraft-avt-rtcpxr-*
Date: Mon, 23 Jul 2007 18:08:18 -0400
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.2962
Thread-Index: AcfNc7oRbzj6yFgLRoiVoFylGITe4AAAYpsw
In-Reply-To: <85C414B9-E725-40F0-B27C-19BB1F200041@cisco.com>
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org
Message-Id: <E1ID65x-0007yS-Vo@megatron.ietf.org>

Dave

I agree with the general tenor of your thoughts.  I also agree that we
should not mandate that endpoints have to implement any particular set of
derived metrics - these should be optional and should be implemented based
on their usefulness.

For cases in which there is a fairly well defined metric class (e.g. MOS for
speech) then I suggest that we do define a separate draft for that with a
registry of algorithms that could be (optionally) used - it is easier to
update a registry with information that a new version of ITU-T G.xxx is
available than it would be to generate a new draft.

Regards

Alan
 

-----Original Message-----
From: David R Oran [mailto:oran@cisco.com] 
Sent: Monday, July 23, 2007 5:51 PM
To: AVT WG
Subject: [AVT] Suggestion for how to handle derived/computed metric
indraft-avt-rtcpxr-*

At the Mic during the AVT session I sketched a vague idea for how to resolve
the conflict between the desire on the part of many folks to only carry
raw/primitive instrumented measurements in RTCP-XR, and other equally vocal,
who argued for carrying the derived/computed metrics as well.

I won't repeat the pro/con arguments here. Let's assume we want to carry
both.

The chairs asked me to write up my vague thoughts as the beginnings of a
concrete proposal.

Some particular technical difficulties with the derived metrics that makes
them different from the primitive measurements is:
- there are competing standards for how to compute them
- the results are not generally aggregatable, comparable, or self-
describing.
- the set of interesting derived metrics is not small and seems to be
growing, so it will be difficult to nail these down for stable RTCP
reporting.

This makes it problematic to mix primitive and derived metrics in the same
metric blocks in RTCP.

So, my suggestion is to do the following.

- A standards body who defines one or more consistent derived metrics may
create (by bringing a draft to IETF) a separate metric block for those
metrics.
- The block and its contained derived/computed metrics would be completely
self-describing in terms of exactly what version of what standard defines
the block.
- The definition of the metric would explicit contain the input variables,
in order to ensure that those inputs are separately available as primitive
metrics in the RTCP-XR. This increases the probability that any metric that
is computable by the endpoint is also computable by a central element
receiving and processing RTCP-XR reports.
- If there are competing/overlapping blocks, an endpoint need not do all of
them and there would be no confusion about exactly which (e.g."video MOS")
calculation was done.

As an aside, I would rather not see further updates to the existing drafts
until we resolve this issue, since this is in fact major surgery to the
documents that is best done before polishing the text and individual metric
definitions.

Dave Oran.

_______________________________________________
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 Jul 23 18:17:03 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID6D8-000351-7A; Mon, 23 Jul 2007 18:17:02 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID6D6-00034q-Oe
	for avt@ietf.org; Mon, 23 Jul 2007 18:17:00 -0400
Received: from smtp4.smtp.bt.com ([217.32.164.151])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ID6D6-000424-68
	for avt@ietf.org; Mon, 23 Jul 2007 18:17:00 -0400
Received: from E03MVB1-UKBR.domain1.systemhost.net ([193.113.197.107]) by
	smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 23 Jul 2007 23:16:59 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 23 Jul 2007 23:16:59 +0100
Message-ID: <20B524BAC1567F48AE039F74BD294D19EDC48B@E03MVB1-UKBR.domain1.systemhost.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Additional requirement in Congestion control for the
	"draft-kristensen-avt-rtp-h264-rcdo-00"
Thread-Index: AcfNdzAVGvfEkTrwSyaeBV3jbgUl2A==
From: <steve.norreys@bt.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 23 Jul 2007 22:16:59.0199 (UTC)
	FILETIME=[2FE99CF0:01C7CD77]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Subject: [AVT] Additional requirement in Congestion control for the
	"draft-kristensen-avt-rtp-h264-rcdo-00"
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0647217366=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0647217366==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7CD77.2FE2CBB4"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7CD77.2FE2CBB4
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi

I just skimmed the draft-kristensen-avt-rtp-h264-rcdo-00 draft and
section 6 that deals with congestion control puzzled me somewhat. The
reference to the main congestion control in RFC3550 in the first
sentence is fine but I don't understand the relationship to the rest of
the paragraph. As the media in a sip sense has been 'offered and
answered' therefore congestion techniques will not apply to this
'session' as congestion control traditionally only applies to the setup
of new 'sessions'.=20

The packet loss could be as a result of congestion and could be used as
a indicator to apply congestion control at this entity that is suffering
the packet loss but this is not the only indication of congestion.
Presumably one of the entities monitoring the packet loss is the UE
which I hope is not under congestion but could still be suffering from
packet loss does it then report this loss to the entity sending the
higher resolution video. I think that some clarification of what the
additional requirement to monitor packet loss is needed.

Regards

Steve Norreys



------_=_NextPart_001_01C7CD77.2FE2CBB4
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>Additional requirement in Congestion control for the =
&quot;draft-kristensen-avt-rtp-h264-rcdo-00&quot;</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">Hi</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I just skimmed the</FONT><SPAN =
LANG=3D"de"> <FONT SIZE=3D2 FACE=3D"Courier =
New">draft-kristensen-avt-rtp-h264-rcdo-00 draft and section 6 that =
deals with congestion control puzzled me somewhat. The reference to the =
main congestion control in RFC3550 in the first sentence is fine but I =
don't understand the relationship to the rest of the paragraph. As the =
media in a sip sense has been 'offered and answered' therefore =
congestion techniques will not apply to this 'session' as congestion =
control traditionally only applies to the setup of new 'sessions'. =
</FONT></SPAN></P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Courier New">The packet loss =
could be as a result of congestion and could be used as a indicator to =
apply congestion control at this entity that is suffering the packet =
loss but this is not the only indication of congestion. Presumably one =
of the entities monitoring the packet loss is the UE which I hope is not =
under congestion but could still be suffering from packet loss does it =
then report this loss to the entity sending the higher resolution video. =
I think that some clarification of what the additional requirement to =
monitor packet loss is needed.</FONT></SPAN></P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Courier =
New">Regards</FONT></SPAN>
</P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Courier New">Steve =
Norreys</FONT></SPAN>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C7CD77.2FE2CBB4--


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

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

--===============0647217366==--




From avt-bounces@ietf.org Mon Jul 23 18:36:37 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID6W4-0006lm-1P; Mon, 23 Jul 2007 18:36:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID6W2-0006lf-Kx
	for avt@ietf.org; Mon, 23 Jul 2007 18:36:34 -0400
Received: from nz-out-0506.google.com ([64.233.162.225])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ID6W1-0005kh-Fu
	for avt@ietf.org; Mon, 23 Jul 2007 18:36:34 -0400
Received: by nz-out-0506.google.com with SMTP id n1so1221496nzf
	for <avt@ietf.org>; Mon, 23 Jul 2007 15:36:32 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=pyM+GpwLQGfgMpXHMyqkeqVQCLtLGfbCBqzW+X9PFExsLkgIFKYYBRqyto1tq/pYEJ2dQ7nuYDnzYsMW64jP8sOL2XNtGHZwGlPS4KWCyIkNB1NmP8mscCKzY562P4Zues4kTmXUZeYatfg1U8sjECHf76UOZoIrASXKEPJX2NQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=jXnkaECc7Mq72eW6d7s6+RV1lvhtRNPgtqDzCstu81NdwXNIC2coc5giFDhEMrb892+YFAuTuK3eXH919MGt2DUDBsx93mFTbB4T4RXJvUhm/gpA+fKlBUgSa3iPWK8nQTBNzrvVdAvyoIgyZ/cglClC8qXvylZPlCMyk8s1uiM=
Received: by 10.114.199.1 with SMTP id w1mr3444923waf.1185230191788;
	Mon, 23 Jul 2007 15:36:31 -0700 (PDT)
Received: by 10.114.145.6 with HTTP; Mon, 23 Jul 2007 15:36:31 -0700 (PDT)
Message-ID: <7e4b541c0707231536s2ff21497p5c5a23a0f6806048@mail.gmail.com>
Date: Tue, 24 Jul 2007 00:36:31 +0200
From: "Tom Kristensen" <2mkristensen@gmail.com>
To: "steve.norreys@bt.com" <steve.norreys@bt.com>
Subject: Re: [AVT] Additional requirement in Congestion control for the
	"draft-kristensen-avt-rtp-h264-rcdo-00"
In-Reply-To: <20B524BAC1567F48AE039F74BD294D19EDC48B@E03MVB1-UKBR.domain1.systemhost.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20B524BAC1567F48AE039F74BD294D19EDC48B@E03MVB1-UKBR.domain1.systemhost.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On 24/07/07, steve.norreys@bt.com <steve.norreys@bt.com> wrote:
> Hi
>
> I just skimmed the draft-kristensen-avt-rtp-h264-rcdo-00
> draft and section 6 that deals with congestion control puzzled me somewhat.
> The reference to the main congestion control in RFC3550 in the first
> sentence is fine but I don't understand the relationship to the rest of the
> paragraph. As the media in a sip sense has been 'offered and answered'
> therefore congestion techniques will not apply to this 'session' as
> congestion control traditionally only applies to the setup of new
> 'sessions'.

The text in section 6 is stolen from the draft "How to Write an RTP
Payload Format" (draft-ietf-avt-rtp-howto-01) - where the text is
proposed as an initial text for this section in the template provided.
However, an RTP payload format specification is not written solely for
SIP applications - so other scenarios apply as well.

> The packet loss could be as a result of congestion and could be used as a
> indicator to apply congestion control at this entity that is suffering the
> packet loss but this is not the only indication of congestion. Presumably
> one of the entities monitoring the packet loss is the UE which I hope is not
> under congestion but could still be suffering from packet loss does it then
> report this loss to the entity sending the higher resolution video. I think
> that some clarification of what the additional requirement to monitor packet
> loss is needed.

Thanks for the input, it's possible to expand and elaborate the text
in the H264-RCDO RTP payload format draft.

-- Tom

-- 
# TANDBERG R&D
## http://www.tandberg.com

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



From avt-bounces@ietf.org Mon Jul 23 19:01:48 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID6uN-0000US-Cc; Mon, 23 Jul 2007 19:01:43 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID6uL-0000UN-OR
	for avt@ietf.org; Mon, 23 Jul 2007 19:01:41 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ID6uL-00052V-5Z
	for avt@ietf.org; Mon, 23 Jul 2007 19:01:41 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 23 Jul 2007 19:01:40 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aq4HAEbQpEZAZnmf/2dsb2JhbACQQQ
X-IronPort-AV: i="4.16,572,1175486400"; 
	d="scan'208"; a="126818635:sNHT31203028"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6NN1eNf004025; 
	Mon, 23 Jul 2007 19:01:40 -0400
Received: from [130.129.87.120] (rtp-vpn3-831.cisco.com [10.82.219.67])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6NN1eWI023085; 
	Mon, 23 Jul 2007 23:01:40 GMT
In-Reply-To: <5v6mls$j9as8@sj-inbound-e.cisco.com>
References: <5v6mls$j9as8@sj-inbound-e.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <7C6AF2D7-AA81-4B29-8948-47C5E7EC139A@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [AVT] Suggestion for how to handle derived/computed metric
	indraft-avt-rtcpxr-*
Date: Mon, 23 Jul 2007 19:01:29 -0400
To: "Alan Clark" <alan.d.clark@telchemy.com>
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3617; t=1185231700;
	x=1186095700; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=oran@cisco.com;
	z=From:=20David=20R=20Oran=20<oran@cisco.com>
	|Subject:=20Re=3A=20[AVT]=20Suggestion=20for=20how=20to=20handle=20derive
	d/computed=20metric=20indraft-avt-rtcpxr-* |Sender:=20
	|To:=20=22Alan=20Clark=22=20<alan.d.clark@telchemy.com>;
	bh=JRh2fLMCJrwwzOFTDIE9Scr4wH5Qex9aA3o5YTq/Y5s=;
	b=mGmCbwI4PBZK2c50XKGxmshFmKGtirozvHzADEQYtuaTof/L0BHTtc8EQiRg/LHGiF/yAGFX
	wvQQ+2QQkKBIj4MThN4f6gSCFbuwWzffdOqwMLAqwB0rVaQemfBY376A;
Authentication-Results: rtp-dkim-2; header.From=oran@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: 'AVT WG' <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org


On Jul 23, 2007, at 6:08 PM, Alan Clark wrote:

> Dave
>
> I agree with the general tenor of your thoughts.  I also agree that we
> should not mandate that endpoints have to implement any particular  
> set of
> derived metrics - these should be optional and should be  
> implemented based
> on their usefulness.
>
OK, thanks.

> For cases in which there is a fairly well defined metric class  
> (e.g. MOS for
> speech) then I suggest that we do define a separate draft for that  
> with a
> registry of algorithms that could be (optionally) used - it is  
> easier to
> update a registry with information that a new version of ITU-T  
> G.xxx is
> available than it would be to generate a new draft.
>
Sure, regisries are a good idea, as long as the registered value is  
explicitly carried in the protocol so the bits on the wire are  
completely self-describing.

> Regards
>
> Alan
>
>
> -----Original Message-----
> From: David R Oran [mailto:oran@cisco.com]
> Sent: Monday, July 23, 2007 5:51 PM
> To: AVT WG
> Subject: [AVT] Suggestion for how to handle derived/computed metric
> indraft-avt-rtcpxr-*
>
> At the Mic during the AVT session I sketched a vague idea for how  
> to resolve
> the conflict between the desire on the part of many folks to only  
> carry
> raw/primitive instrumented measurements in RTCP-XR, and other  
> equally vocal,
> who argued for carrying the derived/computed metrics as well.
>
> I won't repeat the pro/con arguments here. Let's assume we want to  
> carry
> both.
>
> The chairs asked me to write up my vague thoughts as the beginnings  
> of a
> concrete proposal.
>
> Some particular technical difficulties with the derived metrics  
> that makes
> them different from the primitive measurements is:
> - there are competing standards for how to compute them
> - the results are not generally aggregatable, comparable, or self-
> describing.
> - the set of interesting derived metrics is not small and seems to be
> growing, so it will be difficult to nail these down for stable RTCP
> reporting.
>
> This makes it problematic to mix primitive and derived metrics in  
> the same
> metric blocks in RTCP.
>
> So, my suggestion is to do the following.
>
> - A standards body who defines one or more consistent derived  
> metrics may
> create (by bringing a draft to IETF) a separate metric block for those
> metrics.
> - The block and its contained derived/computed metrics would be  
> completely
> self-describing in terms of exactly what version of what standard  
> defines
> the block.
> - The definition of the metric would explicit contain the input  
> variables,
> in order to ensure that those inputs are separately available as  
> primitive
> metrics in the RTCP-XR. This increases the probability that any  
> metric that
> is computable by the endpoint is also computable by a central element
> receiving and processing RTCP-XR reports.
> - If there are competing/overlapping blocks, an endpoint need not  
> do all of
> them and there would be no confusion about exactly which  
> (e.g."video MOS")
> calculation was done.
>
> As an aside, I would rather not see further updates to the existing  
> drafts
> until we resolve this issue, since this is in fact major surgery to  
> the
> documents that is best done before polishing the text and  
> individual metric
> definitions.
>
> Dave Oran.
>
> _______________________________________________
> 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 Jul 23 19:25:17 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID7H9-0001TS-K2; Mon, 23 Jul 2007 19:25:15 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID7H8-0001TM-9j
	for avt@ietf.org; Mon, 23 Jul 2007 19:25:14 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ID7H7-0005Xh-JY
	for avt@ietf.org; Mon, 23 Jul 2007 19:25:14 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	BC27B20A6B; Tue, 24 Jul 2007 01:24:56 +0200 (CEST)
X-AuditID: c1b4fb3c-af67dbb0000007e1-97-46a538c84d45
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	A6671203D1; Tue, 24 Jul 2007 01:24:56 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Jul 2007 01:24:56 +0200
Received: from [138.85.12.20] ([138.85.12.20]) by esealmw127.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Jul 2007 01:24:55 +0200
Message-ID: <46A538C6.5030105@ericsson.com>
Date: Tue, 24 Jul 2007 01:24:54 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: steve.norreys@bt.com
Subject: Re: [AVT] Additional requirement in Congestion control for
	the	"draft-kristensen-avt-rtp-h264-rcdo-00"
References: <20B524BAC1567F48AE039F74BD294D19EDC48B@E03MVB1-UKBR.domain1.systemhost.net>
In-Reply-To: <20B524BAC1567F48AE039F74BD294D19EDC48B@E03MVB1-UKBR.domain1.systemhost.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Jul 2007 23:24:56.0049 (UTC)
	FILETIME=[ADE78E10:01C7CD80]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

steve.norreys@bt.com skrev:
> 
> 
> Hi
> 
> I just skimmed the draft-kristensen-avt-rtp-h264-rcdo-00 draft and 
> section 6 that deals with congestion control puzzled me somewhat. The 
> reference to the main congestion control in RFC3550 in the first 
> sentence is fine but I don't understand the relationship to the rest of 
> the paragraph. As the media in a sip sense has been 'offered and 
> answered' therefore congestion techniques will not apply to this 
> 'session' as congestion control traditionally only applies to the setup 
> of new 'sessions'.

Here you are wrong. Congestion control is needed for the complete 
session in any best-effort network. Only in cases when you have end to 
end QoS agreements with the network can you avoid doing congestion 
control. Even when using QoS should you monitor that the agreement is 
fullfilled by the network.

Please read RFC 2914 to understand why congestion control is needed in 
the internet.


> 
> The packet loss could be as a result of congestion and could be used as 
> a indicator to apply congestion control at this entity that is suffering 
> the packet loss but this is not the only indication of congestion. 
> Presumably one of the entities monitoring the packet loss is the UE 
> which I hope is not under congestion but could still be suffering from 
> packet loss does it then report this loss to the entity sending the 
> higher resolution video. I think that some clarification of what the 
> additional requirement to monitor packet loss is needed.
> 

Normally you will not get any feedback from any entity within the 
network. That is why receivers need to report to the sender about losses 
so that the sender can react to the congestion that is somewhere on the 
path from the sender to the receiver.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
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 Jul 24 09:55:05 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDKqF-0006CY-KR; Tue, 24 Jul 2007 09:54:23 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID3Fy-0000wd-9g
	for avt@ietf.org; Mon, 23 Jul 2007 15:07:46 -0400
Received: from omr4.networksolutionsemail.com ([205.178.146.54])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ID3Fv-0006vp-Qn
	for avt@ietf.org; Mon, 23 Jul 2007 15:07:44 -0400
Received: from mail.networksolutionsemail.com (ns-omr4.mgt.netsol.com
	[10.49.6.67])
	by omr4.networksolutionsemail.com (8.13.6/8.13.6) with SMTP id
	l6NJ7g1P025234 for <avt@ietf.org>; Mon, 23 Jul 2007 15:07:43 -0400
Received: (qmail 19801 invoked by uid 78); 23 Jul 2007 19:07:42 -0000
Received: from unknown (HELO ?192.168.1.101?) (ladan@gharai.org@70.108.44.91)
	by ns-omr4.lb.hosting.dc2.netsol.com with SMTP;
	23 Jul 2007 19:07:42 -0000
In-Reply-To: <46A4B0D6.5030607@ericsson.com>
References: <E1I8JIk-0006Cs-6P@stiedprstage1.ietf.org>
	<2CD7768D-70A2-4149-9FD4-80096D8BD564@csperkins.org>
	<46A3A62E.5070701@ericsson.com>
	<20070722120739.S3620@kao.packetdesign.com>
	<46A4B0D6.5030607@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <E5B507BD-8A3E-4165-86C9-B22BB6DFB538@gharai.org>
Content-Transfer-Encoding: 7bit
From: Ladan Gharai <ladan@gharai.org>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-tfrc-profile-09.txt
Date: Mon, 23 Jul 2007 15:07:36 -0400
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
X-Mailman-Approved-At: Tue, 24 Jul 2007 09:54:22 -0400
Cc: Stephen Casner <casner@acm.org>, AVT WG <avt@ietf.org>,
	Colin Perkins <csp@csperkins.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org


On Jul 23, 2007, at 9:44 AM, Magnus Westerlund wrote:

> Stephen Casner skrev:
>> On Sun, 22 Jul 2007, Magnus Westerlund wrote:
>>> Colin Perkins skrev:
>>>> Reading this, I was surprised that timestamps are specified in  
>>>> microseconds,
>>>> rather than RTP timestamp units. Is there a reason for this  
>>>> choice? Using
>>>> RTP timestamp units would seem easier, since it requires only a  
>>>> single
>>>> clock, and would also allow delta-coding of timestamp relative  
>>>> to the
>>>> timestamp in the RTP header, to reduce packet sizes.
>>> Actually I think using this is correct choice. Delta coding put  
>>> restriction on
>>> how much difference there can be between the display and  
>>> transport time can be
>>> or force a variable field length. having fixed length and delta  
>>> codiding is
>>> not robust unless it is 32 bits.
>>>
>>> Having one fixed timestamp rate avoids the whole issues with  
>>> payload type
>>> switching resulting in clock rate changes. Thus avoiding to  
>>> create additional
>>> issue with changing used payload types.
>> On the other hand, having a clock rate unrelated to the media clock
>> introduces the problem of arithmetic errors.  We had a major debate
>> about this in the design of RTPv2 after RTPv1.
>
> But, the usage of this clock is not related to the media. It is  
> used to determine if you can send a packet or not. So I am  
> wondering if the arithmetic error has any real impact.

     Correct. The send timestamp added via  a header extension is  
used to compute the RTT (also in microseconds), the send rate, the  
lost event rate, etc. Expressing the send timestamp in RTP  timestamp  
units will require a conversion to seconds to be done, before the  
timestamp can be used for transport related usage.

>
> Cheers
>
> Magnus Westerlund
>
> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM/M
> ----------------------------------------------------------------------
> 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 Jul 24 13:15:47 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDNz4-0006g5-W5; Tue, 24 Jul 2007 13:15:42 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDNyv-00063K-DA; Tue, 24 Jul 2007 13:15:33 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IDNyu-0000rj-Rv; Tue, 24 Jul 2007 13:15:33 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 811CC175EB;
	Tue, 24 Jul 2007 17:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IDNyP-0008MS-SX; Tue, 24 Jul 2007 13:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IDNyP-0008MS-SX@stiedprstage1.ietf.org>
Date: Tue, 24 Jul 2007 13:15:01 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-speex-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>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: RTP Payload Format for the Speex Codec
	Author(s)	: G. Herlein, et al.
	Filename	: draft-ietf-avt-rtp-speex-03.txt
	Pages		: 23
	Date		: 2007-7-24
	
Speex is an open-source voice codec suitable for use in Voice over IP
   (VoIP) type applications.  This document describes the payload format
   for Speex generated bit streams within an RTP packet.  Also included
   here are the necessary details for the use of Speex with the Session
   Description Protocol (SDP).

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

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

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

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


--OtherAccess--

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

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

--NextPart--




From avt-bounces@ietf.org Tue Jul 24 16:34:59 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDR5p-0001b9-Q9; Tue, 24 Jul 2007 16:34:53 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDR5o-0001ak-Mq
	for avt@ietf.org; Tue, 24 Jul 2007 16:34:52 -0400
Received: from omr8.networksolutionsemail.com ([205.178.146.58])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDR5o-0006Dm-5N
	for avt@ietf.org; Tue, 24 Jul 2007 16:34:52 -0400
Received: from mail.networksolutionsemail.com (ns-omr8.mgt.netsol.com
	[10.49.6.71])
	by omr8.networksolutionsemail.com (8.13.6/8.13.6) with SMTP id
	l6OKYnPv008704 for <avt@ietf.org>; Tue, 24 Jul 2007 16:34:49 -0400
Received: (qmail 13254 invoked by uid 78); 24 Jul 2007 20:34:49 -0000
Received: from unknown (HELO ?192.168.1.101?) (ladan@gharai.org@70.108.44.91)
	by ns-omr8.lb.hosting.dc2.netsol.com with SMTP;
	24 Jul 2007 20:34:49 -0000
In-Reply-To: <D6D7945A-EB54-4386-B2A4-4697607A1E08@csperkins.org>
References: <E1I8JIk-0006Cs-6P@stiedprstage1.ietf.org>
	<2CD7768D-70A2-4149-9FD4-80096D8BD564@csperkins.org>
	<BC29FF89-8508-4D9D-876B-2312897C456C@ISI.EDU>
	<D6D7945A-EB54-4386-B2A4-4697607A1E08@csperkins.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F479E650-21FC-484F-86DE-5401859AA3C5@gharai.org>
Content-Transfer-Encoding: 7bit
From: Ladan Gharai <ladan@gharai.org>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-tfrc-profile-09.txt
Date: Tue, 24 Jul 2007 16:34:40 -0400
To: Colin Perkins <csp@csperkins.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org


On Jul 23, 2007, at 3:47 PM, Colin Perkins wrote:

> On 22 Jul 2007, at 19:46, Ladan Gharai wrote:
> ...
>>> Reading this, I was surprised that timestamps are specified in  
>>> microseconds, rather than RTP timestamp units. Is there a reason  
>>> for this choice? Using RTP timestamp units would seem easier,  
>>> since it requires only a single clock, and would also allow delta- 
>>> coding of timestamp relative to the timestamp in the RTP header,  
>>> to reduce packet sizes.
>>
>>    The reasoning for using  microseconds timestamps is that these  
>> timestamps are used to measure the RTT time,  determine when a  
>> lost packet would/should have arrived, etc - essentially, these  
>> timestamps have really been added for  the "transport domain"  
>> rather than the "media domain". If the timestamps were is RTP  
>> timestamp units, a conversion to seconds would be needed before  
>> being used in the "transport domain", and so the logic is to avoid  
>> having to convert the timestamp in the main domain for which it  
>> will be used.
>
> But the RTT can be derived from RTCP SR packets, and determining  
> when a packet should have

     Are you saying its OK to have the RTT is seconds/microseconds  
(the RTT calculated using the SR and RR reports is in seconds)

> arrived is a feature of the playout buffer, which derives from the  
> RTP timestamp. It seems that

    right, but TFRC determines the loss intervals by comparing  
arrival times and the RTT - so if the RTT is already in seconds? then  
it be easier to compare the send or arrival time in seconds too

> using microseconds just forces the implementation to use an  
> additional clock for little reason (rather than implement all the  
> TFRC timing logic using the RTP clock).

    But the NTP timestamp used is the SR is wall clock time -  
therefore is the system not already using two clocks?

>
> -- 
> Colin Perkins
> http://csperkins.org/
>
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>


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



From avt-bounces@ietf.org Wed Jul 25 11:15:19 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDiZx-0000cV-OK; Wed, 25 Jul 2007 11:15:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDiZq-0000bZ-KW; Wed, 25 Jul 2007 11:15:02 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IDiZq-00014U-7a; Wed, 25 Jul 2007 11:15:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 11F5126E9A;
	Wed, 25 Jul 2007 15:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IDiZp-0001uv-S9; Wed, 25 Jul 2007 11:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IDiZp-0001uv-S9@stiedprstage1.ietf.org>
Date: Wed, 25 Jul 2007 11:15:01 -0400
X-Spam-Score: -1.4 (-)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-jpeg2000-beam-07.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--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		: Payload Format for JPEG 2000 Video: Extensions for Scalability and Main Header Recovery
	Author(s)	: A. Leung, et al.
	Filename	: draft-ietf-avt-rtp-jpeg2000-beam-07.txt
	Pages		: 34
	Date		: 2007-7-25
	
This memo describes extended uses for payload header in RFC document:
   "RTP Payload Format for JPEG 2000 Video Streams."  For better support
   of JPEG 2000 features such as scalability and includes a main header
   recovery method.

   This memo must be accompanied with a complete implementation of "RTP
   Payload Format for JPEG 2000 Video Streams."  That document is a
   complete description of the payload header and signaling, this
   document only describes additional processing for the payload header.
   There is an additional media type and SDP marker signaling for
   implementations of this document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-jpeg2000-beam-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-beam-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-beam-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 multFrom avt-bounces@ietf.org Wed Jul 25 11:15:19 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDiZx-0000cV-OK; Wed, 25 Jul 2007 11:15:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDiZq-0000bZ-KW; Wed, 25 Jul 2007 11:15:02 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IDiZq-00014U-7a; Wed, 25 Jul 2007 11:15:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 11F5126E9A;
	Wed, 25 Jul 2007 15:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IDiZp-0001uv-S9; Wed, 25 Jul 2007 11:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IDiZp-0001uv-S9@stiedprstage1.ietf.org>
Date: Wed, 25 Jul 2007 11:15:01 -0400
X-Spam-Score: -1.4 (-)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-jpeg2000-beam-07.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--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		: Payload Format for JPEG 2000 Video: Extensions for Scalability and Main Header Recovery
	Author(s)	: A. Leung, et al.
	Filename	: draft-ietf-avt-rtp-jpeg2000-beam-07.txt
	Pages		: 34
	Date		: 2007-7-25
	
This memo describes extended uses for payload header in RFC document:
   "RTP Payload Format for JPEG 2000 Video Streams."  For better support
   of JPEG 2000 features such as scalability and includes a main header
   recovery method.

   This memo must be accompanied with a complete implementation of "RTP
   Payload Format for JPEG 2000 Video Streams."  That document is a
   complete description of the payload header and signaling, this
   document only describes additional processing for the payload header.
   There is an additional media type and SDP marker signaling for
   implementations of this document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-jpeg2000-beam-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-beam-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-beam-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: <2007-7-25105643.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-jpeg2000-beam-07.txt

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

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


--OtherAccess--

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

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

--NextPart--


From avt-bounces@ietf.org Wed Jul 25 11:15:19 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDiZy-0000cw-CY; Wed, 25 Jul 2007 11:15:10 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDiZq-0000bY-Kj; Wed, 25 Jul 2007 11:15:02 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IDiZq-0005ej-7I; Wed, 25 Jul 2007 11:15:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 1FCC62ACB7;
	Wed, 25 Jul 2007 15:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IDiZp-0001us-RW; Wed, 25 Jul 2007 11:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IDiZp-0001us-RW@stiedprstage1.ietf.org>
Date: Wed, 25 Jul 2007 11:15:01 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-jpeg2000-16.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: RTP Payload Format for JPEG 2000 Video Streams
	Author(s)	: S. Futemma, et al.
	Filename	: draft-ietf-avt-rtp-jpeg2000-16.txt
	Pages		: 36
	Date		: 2007-7-25
	
This memo describes an RTP payload format for the ISO/IEC
   International Standard 15444-1 | ITU-T Rec. T.800, otherwise better
   known as: JPEG 2000.  JPEG 2000 features are considered in the design
   of this payload format.  JPEG 2000 is a truly scalable compression
   technology allowing applications to encode once and decode many
   different ways.  JPEG 2000 video stream is formed by extending from a
   single image to a series of JPEG 2000 images.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-jpeg2000-16.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 aiple messages), so check your local documentation on
	how to manipulate these messages.

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-jpeg2000-beam-07.txt

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

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


--OtherAccess--

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

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

--NextPart--


From avt-bounces@ietf.org Wed Jul 25 11:15:19 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDiZy-0000cw-CY; Wed, 25 Jul 2007 11:15:10 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDiZq-0000bY-Kj; Wed, 25 Jul 2007 11:15:02 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IDiZq-0005ej-7I; Wed, 25 Jul 2007 11:15:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 1FCC62ACB7;
	Wed, 25 Jul 2007 15:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IDiZp-0001us-RW; Wed, 25 Jul 2007 11:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IDiZp-0001us-RW@stiedprstage1.ietf.org>
Date: Wed, 25 Jul 2007 11:15:01 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-jpeg2000-16.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: RTP Payload Format for JPEG 2000 Video Streams
	Author(s)	: S. Futemma, et al.
	Filename	: draft-ietf-avt-rtp-jpeg2000-16.txt
	Pages		: 36
	Date		: 2007-7-25
	
This memo describes an RTP payload format for the ISO/IEC
   International Standard 15444-1 | ITU-T Rec. T.800, otherwise better
   known as: JPEG 2000.  JPEG 2000 features are considered in the design
   of this payload format.  JPEG 2000 is a truly scalable compression
   technology allowing applications to encode once and decode many
   different ways.  JPEG 2000 video stream is formed by extending from a
   single image to a series of JPEG 2000 images.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-jpeg2000-16.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-16.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-16.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-jpeg2000-16.txt

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

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


--OtherAccess--

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

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

--NextPart--






 password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-avt-rtp-jpeg2000-16.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-16.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-jpeg2000-16.txt

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

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


--OtherAccess--

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

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

--NextPart--






From avt-bounces@ietf.org Wed Jul 25 12:15:11 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDjVz-0004rS-QY; Wed, 25 Jul 2007 12:15:07 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDjVv-0004q4-56; Wed, 25 Jul 2007 12:15:03 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IDjVu-0007zM-O2; Wed, 25 Jul 2007 12:15:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 73ADD175F6;
	Wed, 25 Jul 2007 16:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IDjVu-0005PQ-1C; Wed, 25 Jul 2007 12:15:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IDjVu-0005PQ-1C@stiedprstage1.ietf.org>
Date: Wed, 25 Jul 2007 12:15:02 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-tfrc-profile-10.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: RTP with TCP Friendly Rate Control
	Author(s)	: L. Gharai
	Filename	: draft-ietf-avt-tfrc-profile-10.txt
	Pages		: 12
	Date		: 2007-7-25
	
This memo specifies how the TCP Friendly Rate Control (TFRC) of RTP
   flows can be supported using the RTP/AVPF profile and the general RTP
   header extension mechanism.  AVPF feedback packets and RTP header
   extensions are defined to support the exchange of control information
   between RTP TFRC senders and receivers. TFRC is an equation-based
   congestion control scheme for unicast flows operating in a best
   effort Internet environment.

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

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

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

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

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

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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-tfrc-profile-10.txt

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

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


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org Wed Jul 25 12:53:34 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDk72-0006lM-OK; Wed, 25 Jul 2007 12:53:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDk71-0006lF-Gn
	for avt@ietf.org; Wed, 25 Jul 2007 12:53:23 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDk6z-0004wF-Uy
	for avt@ietf.org; Wed, 25 Jul 2007 12:53:23 -0400
Received: from dhcp-14f7.ietf69.org ([130.129.20.247]:57893)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1IDk6y-0003qA-UZ; Wed, 25 Jul 2007 17:53:21 +0100
In-Reply-To: <F479E650-21FC-484F-86DE-5401859AA3C5@gharai.org>
References: <E1I8JIk-0006Cs-6P@stiedprstage1.ietf.org>
	<2CD7768D-70A2-4149-9FD4-80096D8BD564@csperkins.org>
	<BC29FF89-8508-4D9D-876B-2312897C456C@ISI.EDU>
	<D6D7945A-EB54-4386-B2A4-4697607A1E08@csperkins.org>
	<F479E650-21FC-484F-86DE-5401859AA3C5@gharai.org>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <7B03E158-CA2B-416F-AA9B-0A8BF69AF765@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-tfrc-profile-09.txt
Date: Wed, 25 Jul 2007 11:53:23 -0500
To: Ladan Gharai <ladan@gharai.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

This is why I'm suggesting you use the RTP timestamp rate: it avoids  
all these issues with multiple clocks.

Colin



On 24 Jul 2007, at 15:34, Ladan Gharai wrote:
> On Jul 23, 2007, at 3:47 PM, Colin Perkins wrote:
>> On 22 Jul 2007, at 19:46, Ladan Gharai wrote:
>> ...
>>>> Reading this, I was surprised that timestamps are specified in  
>>>> microseconds, rather than RTP timestamp units. Is there a reason  
>>>> for this choice? Using RTP timestamp units would seem easier,  
>>>> since it requires only a single clock, and would also allow  
>>>> delta-coding of timestamp relative to the timestamp in the RTP  
>>>> header, to reduce packet sizes.
>>>
>>>    The reasoning for using  microseconds timestamps is that these  
>>> timestamps are used to measure the RTT time,  determine when a  
>>> lost packet would/should have arrived, etc - essentially, these  
>>> timestamps have really been added for  the "transport domain"  
>>> rather than the "media domain". If the timestamps were is RTP  
>>> timestamp units, a conversion to seconds would be needed before  
>>> being used in the "transport domain", and so the logic is to  
>>> avoid having to convert the timestamp in the main domain for  
>>> which it will be used.
>>
>> But the RTT can be derived from RTCP SR packets, and determining  
>> when a packet should have
>
>     Are you saying its OK to have the RTT is seconds/microseconds  
> (the RTT calculated using the SR and RR reports is in seconds)
>
>> arrived is a feature of the playout buffer, which derives from the  
>> RTP timestamp. It seems that
>
>    right, but TFRC determines the loss intervals by comparing  
> arrival times and the RTT - so if the RTT is already in seconds?  
> then it be easier to compare the send or arrival time in seconds too
>
>> using microseconds just forces the implementation to use an  
>> additional clock for little reason (rather than implement all the  
>> TFRC timing logic using the RTP clock).
>
>    But the NTP timestamp used is the SR is wall clock time -  
> therefore is the system not already using two clocks?
>
>>
>> -- 
>> Colin Perkins
>> http://csperkins.org/
>>
>>
>>
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/avt
>>
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt



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



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



From avt-bounces@ietf.org Wed Jul 25 13:15:13 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDkS0-0002gV-IT; Wed, 25 Jul 2007 13:15:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDkRy-0002fv-PA; Wed, 25 Jul 2007 13:15:02 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IDkRy-0005Xo-Aj; Wed, 25 Jul 2007 13:15:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 0CEE826E85;
	Wed, 25 Jul 2007 17:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IDkRx-0008NY-Tw; Wed, 25 Jul 2007 13:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IDkRx-0008NY-Tw@stiedprstage1.ietf.org>
Date: Wed, 25 Jul 2007 13:15:01 -0400
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-and-rtcp-mux-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>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: Multiplexing RTP Data and Control Packets on a Single Port
	Author(s)	: C. Perkins, M. Westerlund
	Filename	: draft-ietf-avt-rtp-and-rtcp-mux-06.txt
	Pages		: 15
	Date		: 2007-7-25
	
This memo discusses issues that arise when multiplexing RTP data
   packets and RTP control protocol (RTCP) packets on a single UDP port.
   It updates RFC 3550 to describe when such multiplexing is, and is
   not, appropriate, and explains how the Session Description Protocol
   (SDP) can be used to signal multiplexed sessions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-and-rtcp-mux-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-and-rtcp-mux-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-and-rtcp-mux-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: <2007-7-25120521.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-and-rtcp-mux-06.txt

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

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


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org Wed Jul 25 13:17:39 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDkUP-0006ov-6i; Wed, 25 Jul 2007 13:17:33 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDkUO-0006lg-1U
	for avt@ietf.org; Wed, 25 Jul 2007 13:17:32 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDkUN-0002Af-8y
	for avt@ietf.org; Wed, 25 Jul 2007 13:17:31 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	B7DB92083E; Wed, 25 Jul 2007 19:17:30 +0200 (CEST)
X-AuditID: c1b4fb3c-ae67bbb0000007e1-28-46a785aab862
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	9B1A920759; Wed, 25 Jul 2007 19:17:30 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 25 Jul 2007 19:17:30 +0200
Received: from [138.85.12.150] ([138.85.12.150]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 25 Jul 2007 19:17:29 +0200
Message-ID: <46A785A7.70100@ericsson.com>
Date: Wed, 25 Jul 2007 19:17:27 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: "Even, Roni" <roni.even@polycom.co.il>
References: <144ED8561CE90C41A3E5908EDECE315C04B8F936@IsrExch01.israel.polycom.com>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C04B8F936@IsrExch01.israel.polycom.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Jul 2007 17:17:29.0993 (UTC)
	FILETIME=[AE41DF90:01C7CEDF]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: bo.burman@ericsson.com, stewe@stewe.org, avt@ietf.org
Subject: [AVT] Re: Review draft-ietf-avt-avpf-ccm-07
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Thanks for the review.

Even, Roni skrev:
> Hi
> It took me some time but I have some comments and nits
> 
> 1. In section 3.5.2 I suggest to delete "(as it is common in state-of-the-art video conferencing systems). I am not sure that it adds value and voice an opinion.

Agreed

> 
> 2. In 4.2.1.2 " If the media sender concludes that it can increase the maximum total media bit rate value, it SHALL wait before actually doing so, for a period long enough to allow a media receiver to respond to the TMMBN if it determines that its tuple belongs in the bounding set."
> 
> I was wondering if the SHALL is also true for unicast point to point case.
> 

Yes, this also applies to point to point. The reason is that one can't 
really reliably know which topology you are in. Thus, it is safest to do 
this also in point to point cases. Do you think we need to add any text 
on this?

> 3. In 4.2.2.2
> "As indicated in section 4.2.1.2, when a media sender determines
>    that an "owner" of a bounding tuple has left the session, then
>    that tuple is removed from the bounding set, and the media sender
>    SHALL send a TMMBN message indicating the remaining bounding
>    tuples.  If there are no remaining bounding tuples a TMMBN without
>    any FCI SHALL be sent to indicate this."
> 
> If there are no remaining bounding set what is the current bit rate. Does it mean that the sender may raise the bit rate to the negotiated rate in the signaling.

Yes, we have clarified this by adding the following sentence:

"Without a remaining bounding tuple, the maximum media bit rate and 
maximum packet rate negotiated in session signaling, if any, apply."

> 
> 
> 4. In 4.3.1.2
> 
> Do we need the note bellow in the final version.
> 
> "Note: Mandating a maximum delay for completing the sending of a decoder refresh point would be desirable from an application     viewpoint, but is problematic from a congestion control point of view.  "As soon as possible" as mentioned above appears to be a reasonable compromise"
> 

No, but this has been moved into Section 4.3.2.5 (Remarks) where it 
makes more sense to have it as explanation.

> 
> 5. in section 7.1 " MaxPacketRateValue = 1*15DIGIT" what are the units for this parameter. I think that based on the example it is in 1000's of bits per second but please clarify.
> Fix the value in example 3 based on the units, currently it say 120 and I assumed 120*1000 bits/s

We added clarification that this is packets per second.

> 
> 
> 6. In the 7.2 " The offerer MAY indicate the capability to support selected codec commands and indications.  The answerer MUST remove all ccm parameters which it does not understand or does not wish to use in this particular media session."
> I am not sure what you mean do not want to use, is it does not want to send or just does not want to receive but may send. 
> Based on your response the text for the answer in example 3 should have the same semantics.
>  
> 

The intention is that you must have the capability to receive such CCM 
requests and in cases, like TSTR to send the response. A agent is not 
required to initiate CCM messages, but expected I would say. Thus I 
propose the following addition to section 7.2:

Note, that including a CCM parameter in an offer or answer indicates 
that the agent (offerer or answerer) is at least capable of receiving 
the corresponding CCM message(s) and act upon them. In cases when the 
reception of a negotiated CCM messages mandates the agent to respond 
with another CCM message, it also must have that capability. Although 
not mandated to initiate CCM messages of any negotiated type it is 
generally expected that the agent will initiate CCM messages when suitable.


Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
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 Jul 25 13:21:14 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDkXu-00032Q-0u; Wed, 25 Jul 2007 13:21:10 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDkXp-0002xW-Ez
	for avt@ietf.org; Wed, 25 Jul 2007 13:21:05 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDkXo-00032u-VB
	for avt@ietf.org; Wed, 25 Jul 2007 13:21:05 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	5D85020433; Wed, 25 Jul 2007 19:21:04 +0200 (CEST)
X-AuditID: c1b4fb3e-b1036bb0000007e1-94-46a786805fad
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	39395200B5; Wed, 25 Jul 2007 19:21:04 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 25 Jul 2007 19:21:04 +0200
Received: from [138.85.12.150] ([138.85.12.150]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 25 Jul 2007 19:21:03 +0200
Message-ID: <46A7867F.30105@ericsson.com>
Date: Wed, 25 Jul 2007 19:21:03 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: Keith Lantz <klantz@cisco.com>
Subject: Re: [AVT] I-D Action:draft-ietf-avt-topologies-05.txt
References: <E1I6pkw-0000Gy-3P@stiedprstage1.ietf.org>
	<6.2.3.4.2.20070706160335.03e206b0@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <6.2.3.4.2.20070706160335.03e206b0@xmb-sjc-222.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Jul 2007 17:21:03.0907 (UTC)
	FILETIME=[2DC28F30:01C7CEE0]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: stewe@stewe.org, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi,

Thanks once more for these comments. We have incorporaed them into a 
version we intended to submit soon.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
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 Jul 25 13:35:31 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDklk-00083r-Lh; Wed, 25 Jul 2007 13:35:28 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDkli-00083E-Sc
	for avt@ietf.org; Wed, 25 Jul 2007 13:35:26 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDklh-0003d7-H2
	for avt@ietf.org; Wed, 25 Jul 2007 13:35:26 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 25 Jul 2007 20:36:20 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04C236A6@IsrExch01.israel.polycom.com>
In-Reply-To: <46A785A7.70100@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Review draft-ietf-avt-avpf-ccm-07
Thread-Index: AcfO352dk45OybTnQqeS9Kd4iKYBPQAAUrsA
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ca81a19b939ce054f98c8f830c2d7742
Cc: bo.burman@ericsson.com, stewe@stewe.org, avt@ietf.org
Subject: [AVT] RE: Review draft-ietf-avt-avpf-ccm-07
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="===============1867130468=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1867130468==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7CEE2.1A14CB83"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7CEE2.1A14CB83
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Thanks,

Inline

=20

> > 2. In 4.2.1.2 " If the media sender concludes that it can increase =
the

> maximum total media bit rate value, it SHALL wait before actually =
doing

> so, for a period long enough to allow a media receiver to respond to =
the

> TMMBN if it determines that its tuple belongs in the bounding set."

> >

> > I was wondering if the SHALL is also true for unicast point to point

> case.

> >

>=20

> Yes, this also applies to point to point. The reason is that one can't

> really reliably know which topology you are in. Thus, it is safest to =
do

> this also in point to point cases. Do you think we need to add any =
text

> on this?

>=20

[RE:] I think a clarification will make sense.=20

> >

> >

> >

> >

> > 6. In the 7.2 " The offerer MAY indicate the capability to support

> selected codec commands and indications.  The answerer MUST remove all =
ccm

> parameters which it does not understand or does not wish to use in =
this

> particular media session."

> > I am not sure what you mean do not want to use, is it does not want =
to

> send or just does not want to receive but may send.

> > Based on your response the text for the answer in example 3 should =
have

> the same semantics.

> >

> >

>=20

> The intention is that you must have the capability to receive such CCM

> requests and in cases, like TSTR to send the response. A agent is not

> required to initiate CCM messages, but expected I would say. Thus I

> propose the following addition to section 7.2:

>=20

> Note, that including a CCM parameter in an offer or answer indicates

> that the agent (offerer or answerer) is at least capable of receiving

> the corresponding CCM message(s) and act upon them. In cases when the

> reception of a negotiated CCM messages mandates the agent to respond

> with another CCM message, it also must have that capability. Although

> not mandated to initiate CCM messages of any negotiated type it is

> generally expected that the agent will initiate CCM messages when

> suitable.

>=20

[RE:] I am still not sure I understand. Example the offer includes =
tmmbr, tstr and fir. The answer responds with tstr only.

Does it mean that the answerer may send tmmbr, tstr and fir but the =
offerer can only send tstr.=20

Also if the above is right it will mean the answerer sending tmmbr will =
be able to process the response.

=20

=20

=20

=20

=20

>=20

> Cheers

>=20

> Magnus Westerlund

>=20

> IETF Transport Area Director & TSVWG Chair

> ----------------------------------------------------------------------

> Multimedia Technologies, Ericsson Research EAB/TVM/M

> ----------------------------------------------------------------------

> Ericsson AB                | Phone +46 8 4048287

> Torshamsgatan 23           | Fax   +46 8 7575550

> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com

> ----------------------------------------------------------------------


------_=_NextPart_001_01C7CEE2.1A14CB83
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"metricconverter"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 77.95pt 72.0pt 77.95pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Inline<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &gt; <st1:metricconverter ProductID=3D"2. In" =
w:st=3D"on">2. In</st1:metricconverter>
4.2.1.2 &quot; If the media sender concludes that it can increase =
the</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; maximum total media bit rate value, it SHALL wait before =
actually
doing</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; so, for a period long enough to allow a media receiver to =
respond
to the</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; TMMBN if it determines that its tuple belongs in the =
bounding
set.&quot;</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &gt;</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &gt; I was wondering if the SHALL is also true for unicast =
point
to point</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; case.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &gt;</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Yes, this also applies to point to point. The reason is =
that one
can't</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; really reliably know which topology you are in. Thus, it is =
safest
to do</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; this also in point to point cases. Do you think we need to =
add any
text</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; on this?</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><b><i><font size=3D2 color=3Dblack =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;color:black;font-weight:bold;font-style:italic'=
>[RE:] I
think a clarification will make sense. </span></font></i></b><font =
color=3Dblack><span
style=3D'color:black'><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &gt;</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &gt;</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &gt;</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &gt;</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &gt; <st1:metricconverter ProductID=3D"6. In" =
w:st=3D"on">6. In</st1:metricconverter>
the 7.2 &quot; The offerer MAY indicate the capability to =
support</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; selected codec commands and indications.=A0 The answerer =
MUST remove
all ccm</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; parameters which it does not understand or does not wish to =
use in
this</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; particular media session.&quot;</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &gt; I am not sure what you mean do not want to use, is it =
does
not want to</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; send or just does not want to receive but may =
send.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &gt; Based on your response the text for the answer in =
example 3
should have</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; the same semantics.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &gt;</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &gt;</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; The intention is that you must have the capability to =
receive such
CCM</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; requests and in cases, like TSTR to send the response. A =
agent is
not</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; required to initiate CCM messages, but expected I would =
say. Thus
I</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; propose the following addition to section =
7.2:</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Note, that including a CCM parameter in an offer or answer
indicates</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; that the agent (offerer or answerer) is at least capable of
receiving</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; the corresponding CCM message(s) and act upon them. In =
cases when
the</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; reception of a negotiated CCM messages mandates the agent =
to
respond</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; with another CCM message, it also must have that =
capability.
Although</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; not mandated to initiate CCM messages of any negotiated =
type it is</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; generally expected that the agent will initiate CCM =
messages when</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; suitable.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;<o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><b><i><font size=3D2 face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-weight:bold;font-style:italic'>[RE:] I am =
still
not sure I understand. Example the offer includes tmmbr, tstr and fir. =
The answer
responds with tstr only.<o:p></o:p></span></font></i></b></p>

<p class=3DMsoPlainText><b><i><font size=3D2 face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-weight:bold;font-style:italic'>Does it =
mean that
the answerer may send tmmbr, tstr and fir but the offerer can only send =
tstr. <o:p></o:p></span></font></i></b></p>

<p class=3DMsoPlainText><b><i><font size=3D2 face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-weight:bold;font-style:italic'>Also if =
the above
is right it will mean the answerer sending tmmbr will be able to process =
the
response.<o:p></o:p></span></font></i></b></p>

<p class=3DMsoPlainText><b><i><font size=3D2 face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-weight:bold;font-style:italic'><o:p>&nbsp;=
</o:p></span></font></i></b></p>

<p class=3DMsoPlainText><b><i><font size=3D2 face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-weight:bold;font-style:italic'>=A0<o:p></o=
:p></span></font></i></b></p>

<p class=3DMsoPlainText><b><i><font size=3D2 face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-weight:bold;font-style:italic'><o:p>&nbsp;=
</o:p></span></font></i></b></p>

<p class=3DMsoPlainText><b><i><font size=3D2 face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-weight:bold;font-style:italic'><o:p>&nbsp;=
</o:p></span></font></i></b></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>=A0</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Cheers</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; <st1:PersonName ProductID=3D"Magnus Westerlund" =
w:st=3D"on">Magnus
 Westerlund</st1:PersonName></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; IETF Transport Area Director &amp; TSVWG =
Chair</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; =
----------------------------------------------------------------------</s=
pan></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Multimedia Technologies, Ericsson Research =
EAB/TVM/M</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; =
----------------------------------------------------------------------</s=
pan></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Ericsson AB=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 | =
Phone +46 8 4048287</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Torshamsgatan 23=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 | Fax=A0=A0 =
+46 8 7575550</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; S-164 80 Stockholm, Sweden | mailto: =
magnus.westerlund@ericsson.com</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; =
----------------------------------------------------------------------</s=
pan></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C7CEE2.1A14CB83--


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

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

--===============1867130468==--




From avt-bounces@ietf.org Wed Jul 25 14:15:09 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDlO5-0004ok-IT; Wed, 25 Jul 2007 14:15:05 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDlO2-0004lu-Er; Wed, 25 Jul 2007 14:15:02 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IDlO2-0004ob-2F; Wed, 25 Jul 2007 14:15:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id E4FA02ACB2;
	Wed, 25 Jul 2007 18:15:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IDlO1-00031Q-KF; Wed, 25 Jul 2007 14:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IDlO1-00031Q-KF@stiedprstage1.ietf.org>
Date: Wed, 25 Jul 2007 14:15:01 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-profile-savpf-11.txt 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: Extended Secure RTP Profile for RTCP-based Feedback (RTP/SAVPF)
	Author(s)	: J. Ott, E. Carrara
	Filename	: draft-ietf-avt-profile-savpf-11.txt
	Pages		: 17
	Date		: 2007-7-25
	
An RTP profile (SAVP) is defined for secure real-time 
   communications, and another profile (AVPF) is specified to provide 
   timely feedback from the receivers to a sender.  This memo defines 
   the combination of both profiles to enable secure RTP 
   communications with feedback.

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

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

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

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

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

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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-profile-savpf-11.txt

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

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


--OtherAccess--

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

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

--NextPart--





From avt-bounces@ietf.org Wed Jul 25 15:02:25 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDm7s-0008Ue-9q; Wed, 25 Jul 2007 15:02:24 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDm7q-0008UV-Vq
	for avt@ietf.org; Wed, 25 Jul 2007 15:02:23 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDm7q-0006p3-40
	for avt@ietf.org; Wed, 25 Jul 2007 15:02:22 -0400
Received: from relay8.apple.com (relay8.apple.com [17.128.113.38])
	by mail-out3.apple.com (Postfix) with ESMTP id 8E2DFCC4C29;
	Wed, 25 Jul 2007 12:02:21 -0700 (PDT)
Received: from relay8.apple.com (unknown [127.0.0.1])
	by relay8.apple.com (Symantec Mail Security) with ESMTP id 7A1DA4044D; 
	Wed, 25 Jul 2007 12:02:21 -0700 (PDT)
X-AuditID: 11807126-a7448bb0000007e3-7f-46a79e3dacb8
Received: from [17.202.35.52] (singda.apple.com [17.202.35.52])
	by relay8.apple.com (Apple SCV relay) with ESMTP id 2234340079;
	Wed, 25 Jul 2007 12:02:21 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p06240803c2cd4d282cd9@[17.202.35.52]>
In-Reply-To: <0MKp8S-1IBfib2mC2-0005q2@mrelay.perfora.net>
References: <0MKp8S-1IBfib2mC2-0005q2@mrelay.perfora.net>
Date: Wed, 25 Jul 2007 12:01:35 -0700
To: Michael A Dolan <md.1@newtbt.com>, AVT WG <avt@ietf.org>
From: Dave Singer <singer@apple.com>
Subject: RE: [AVT] draft-ietf-avt-hdrext-12
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

At 16:47  -0700 19/07/07, Michael A Dolan wrote:
>Hi Hari-
>
>Thank you for your thoughts.
>
>In my survey of extensions (which was certainly not exhaustive) in 
>all cases, the 4 bit fields save nothing due to field alignment 
>being more important than bit savings.  Of course, potential 
>extensions such as byte strings would save one byte per 
>sub-extension in the current design.  But all field-aligned 16-byte 
>and 32-byte extension fields save nothing.  If this is the basis of 
>the objection, then I think we'd need to survey the extensions in 
>use and anticipated and form a more technical comparison of the bit 
>savings of 4 versus 8, which I maintain is negligible.
>
>My thinking in the proposal below was that it would be better to 
>capture the recommended and alternate ID/LEN sizes in one document. 
>I can of course create a 2nd Informational RFC (discussed as an 
>option earlier in this thread), but before I did that I would poke 
>at the 4-bit design further.  The "defined by profile" field value 
>is, of course, arbitrary.
>
>The need comes from the design below being deployed in commercial 
>products.  We *do* agree that it is desirable to have only one 
>recommended design. So, the question is how best to achieve that? 
>How important is it to preserve a 4-bit design (why, exactly?) and 
>the (arbitrary) value 0xBEDE?

OK

The transmission offset is carefully 24 bits, so it fits into a long 
with its 4+4 header.

Similarly the compact form of the SMPTE time-code is 24 bits.

So, the only two I have defined do, in fact, fit.  If I went to an 
8+8 I'd have to fit these into 16 bits (which is clearly too small 
for SMPTE TC), or use padding.

I used the 4+4 design because of a general sense that header 
extensions shouldn't 'swamp' the packet, and to be compact;  just 
general caution, no more.

BEDE was clearly an arbitrary number.  I have no problems changing it.

Choices:

a) go with just 4+4 or just 8+8, and drop one.  I am aware of 
implementations of both, so this isn't ideal.

b) in the same document, require support for both.

c) in the same document, require support for one, and recommend 
support for the other.

d) publish one separately, as an informational RFC.

Personally, I prefer (b) or (c), with a slight preference for (c).

>
>Regards,
>
>         Mike
>
>At 04:08 PM 7/19/2007, Desineni, Harikishan wrote:
>>  >using either 4- or 8-bit ID/LEN fields since the extension fields
>>>need to be field-size aligned and thus padding out to 16 or 32 bits
>>>is nearly always required in both designs.
>>
>>May not be correct, might have to disagree here. It depends on the
>>number and size of extensions.
>>
>>Note that the scope of 0xBEDE profile extension is RTP/AVP profile and
>>all its extensions. I see your proposal as a new (0x100x) header
>>extension format for the same RTP profiles (RTP/AVP and extensions).
>>
>>I think the question that needs to be answered is "Is there is a need
>>for standardizing multiple header extensions for a given (or set of) RTP
>>profile(s)?"
>>
>>I am comfortable to see just one header extension format per RTP
>>profile. I prefer to keep 0xBEDE as the RECOMMENDED header extension
>>format for RTP/AVP profile and its extensions.
>>
>>At this time, I think that taking the informational RFC route for 0x100x
>>would be a better approach.
>>
>>
>>--Hari
>
>-----------------------------------
>Michael DOLAN
>Television Broadcast Technology, Inc. (TBT)
>PO Box 190, Del Mar, CA 92014 USA
>+1-858-755-6661    FAX: +1-858-755-6669
>URL:http://www.newtbt.com
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>https://www1.ietf.org/mailman/listinfo/avt


-- 
David Singer
Apple/QuickTime

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



From avt-bounces@ietf.org Wed Jul 25 20:07:47 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDqtN-0003Jy-04; Wed, 25 Jul 2007 20:07:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDqtL-0003Jp-Uo
	for avt@ietf.org; Wed, 25 Jul 2007 20:07:43 -0400
Received: from mout.perfora.net ([74.208.4.194])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDqtK-0007hx-IY
	for avt@ietf.org; Wed, 25 Jul 2007 20:07:43 -0400
Received: from [70.212.247.222] (helo=TBT-Laptop.newtbt.com)
	by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis),
	id 0MKpCa-1IDqsy0MRm-0006V5; Wed, 25 Jul 2007 20:07:41 -0400
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 25 Jul 2007 17:06:51 -0700
To: AVT WG <avt@ietf.org>
From: Michael A Dolan <md.1@newtbt.com>
Subject: RE: [AVT] draft-ietf-avt-hdrext-12
In-Reply-To: <p06240803c2cd4d282cd9@[17.202.35.52]>
References: <0MKp8S-1IBfib2mC2-0005q2@mrelay.perfora.net>
	<p06240803c2cd4d282cd9@[17.202.35.52]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <0MKpCa-1IDqsy0MRm-0006V5@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX19zlm5rVSrMSVlWR4t5GFJmbyx4jfRG390SxjF
	ORNreuiTryzy7sqVkDaCsExK+hCjiDWYkOOuhWIpL6dlo3t1En
	RhzClz9Lqats/lF53aC9A==
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Dave and all-

I was hoping to avoid a debate on relative deployment and the value 
of 4 bits versus 8 bits by proposing option (c) below (which is what 
I tried to articulate in last week's post).  In a perfect world, we 
would drive to (a), but I don't see how to get there in any 
reasonable timeline.  Mean-time the world moves on making more of 
these deployments, and worse, more non-conformant variants we don't 
even know about....

Can everyone live with option (c)?

Regards,

         Mike

At 12:01 PM 7/25/2007, Dave Singer wrote:
>At 16:47  -0700 19/07/07, Michael A Dolan wrote:
>>Hi Hari-
>>
>>Thank you for your thoughts.
>>
>>In my survey of extensions (which was certainly not exhaustive) in 
>>all cases, the 4 bit fields save nothing due to field alignment 
>>being more important than bit savings.  Of course, potential 
>>extensions such as byte strings would save one byte per 
>>sub-extension in the current design.  But all field-aligned 16-byte 
>>and 32-byte extension fields save nothing.  If this is the basis of 
>>the objection, then I think we'd need to survey the extensions in 
>>use and anticipated and form a more technical comparison of the bit 
>>savings of 4 versus 8, which I maintain is negligible.
>>
>>My thinking in the proposal below was that it would be better to 
>>capture the recommended and alternate ID/LEN sizes in one document. 
>>I can of course create a 2nd Informational RFC (discussed as an 
>>option earlier in this thread), but before I did that I would poke 
>>at the 4-bit design further.  The "defined by profile" field value 
>>is, of course, arbitrary.
>>
>>The need comes from the design below being deployed in commercial 
>>products.  We *do* agree that it is desirable to have only one 
>>recommended design. So, the question is how best to achieve that? 
>>How important is it to preserve a 4-bit design (why, exactly?) and 
>>the (arbitrary) value 0xBEDE?
>
>OK
>
>The transmission offset is carefully 24 bits, so it fits into a long 
>with its 4+4 header.
>
>Similarly the compact form of the SMPTE time-code is 24 bits.
>
>So, the only two I have defined do, in fact, fit.  If I went to an 
>8+8 I'd have to fit these into 16 bits (which is clearly too small 
>for SMPTE TC), or use padding.
>
>I used the 4+4 design because of a general sense that header 
>extensions shouldn't 'swamp' the packet, and to be compact;  just 
>general caution, no more.
>
>BEDE was clearly an arbitrary number.  I have no problems changing it.
>
>Choices:
>
>a) go with just 4+4 or just 8+8, and drop one.  I am aware of 
>implementations of both, so this isn't ideal.
>
>b) in the same document, require support for both.
>
>c) in the same document, require support for one, and recommend 
>support for the other.
>
>d) publish one separately, as an informational RFC.
>
>Personally, I prefer (b) or (c), with a slight preference for (c).
>
>>
>>Regards,
>>
>>         Mike
>>
>>At 04:08 PM 7/19/2007, Desineni, Harikishan wrote:
>>>  >using either 4- or 8-bit ID/LEN fields since the extension fields
>>>>need to be field-size aligned and thus padding out to 16 or 32 bits
>>>>is nearly always required in both designs.
>>>
>>>May not be correct, might have to disagree here. It depends on the
>>>number and size of extensions.
>>>
>>>Note that the scope of 0xBEDE profile extension is RTP/AVP profile and
>>>all its extensions. I see your proposal as a new (0x100x) header
>>>extension format for the same RTP profiles (RTP/AVP and extensions).
>>>
>>>I think the question that needs to be answered is "Is there is a need
>>>for standardizing multiple header extensions for a given (or set of) RTP
>>>profile(s)?"
>>>
>>>I am comfortable to see just one header extension format per RTP
>>>profile. I prefer to keep 0xBEDE as the RECOMMENDED header extension
>>>format for RTP/AVP profile and its extensions.
>>>
>>>At this time, I think that taking the informational RFC route for 0x100x
>>>would be a better approach.
>>>
>>>
>>>--Hari
>>
>>-----------------------------------
>>Michael DOLAN
>>Television Broadcast Technology, Inc. (TBT)
>>PO Box 190, Del Mar, CA 92014 USA
>>+1-858-755-6661    FAX: +1-858-755-6669
>>URL:http://www.newtbt.com
>>
>>_______________________________________________
>>Audio/Video Transport Working Group
>>avt@ietf.org
>>https://www1.ietf.org/mailman/listinfo/avt
>
>
>--
>David Singer
>Apple/QuickTime


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



From avt-bounces@ietf.org Thu Jul 26 00:26:29 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDuvU-0004Nh-Rc; Thu, 26 Jul 2007 00:26:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDuvT-0004Nc-Ai
	for avt@ietf.org; Thu, 26 Jul 2007 00:26:11 -0400
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IDuvS-0003EM-5u for avt@ietf.org; Thu, 26 Jul 2007 00:26:11 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 26 Jul 2007 00:26:09 -0400
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-tfrc-profile-09.txt
References: <E1I8JIk-0006Cs-6P@stiedprstage1.ietf.org>
	<2CD7768D-70A2-4149-9FD4-80096D8BD564@csperkins.org>
	<BC29FF89-8508-4D9D-876B-2312897C456C@ISI.EDU>
	<D6D7945A-EB54-4386-B2A4-4697607A1E08@csperkins.org>
	<F479E650-21FC-484F-86DE-5401859AA3C5@gharai.org>
	<7B03E158-CA2B-416F-AA9B-0A8BF69AF765@csperkins.org>
From: Randell Jesup <rjesup@wgate.com>
Date: Thu, 26 Jul 2007 00:26:08 -0400
In-Reply-To: <7B03E158-CA2B-416F-AA9B-0A8BF69AF765@csperkins.org> (Colin
	Perkins's message of "Wed, 25 Jul 2007 11:53:23 -0500")
Message-ID: <ybuejivu6xr.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 26 Jul 2007 04:26:09.0796 (UTC)
	FILETIME=[1785FC40:01C7CF3D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: Ladan Gharai <ladan@gharai.org>, AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Colin Perkins <csp@csperkins.org> writes:
>This is why I'm suggesting you use the RTP timestamp rate: it avoids  all
>these issues with multiple clocks.

But can't the RTP timestamp rate change in mid-stream?  (See the
discussions here in the last few months, plus a few other times over the
last few years).  You can't tell exactly when it changed in the face of
packet loss in some situations.  Plus even if you can tell when, it greatly
complicates conversion to real-time deltas if the time crosses a
payload-induced timestamp rate change.

Example:
m=audio 6543 RTP/AVP 99 98 97
a=rtpmap 99 iLBC/8000
a=rtpmap 98 G722/16000
a=rtpmap 97 DVI4_22050 22050

And then the stream switches from payload 99 to 98 to 97 over time (or
even flop/flops back and forth - legal, though incredibly cruel/stupid/silly).

This is a real-world scenario, too - a call may start G722/16000, and
switch to iLBC/8000 if the loss is too high.

(When discussing DTMF/RFC2833/4877 here in the last few months, it was
proposed that to handle DTMF in this situation, excluding the "crosses the
transition" case, just have two payloads defined, one with /8000 and one
with /16000 (or three in the case above).

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


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



From avt-bounces@ietf.org Thu Jul 26 12:19:36 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE63j-0007Fb-KI; Thu, 26 Jul 2007 12:19:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE63c-000759-H3; Thu, 26 Jul 2007 12:19:20 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IE63b-0002lR-B9; Thu, 26 Jul 2007 12:19:20 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 26 Jul 2007 12:19:19 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CANxlqEZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,584,1175486400"; 
	d="scan'208"; a="127119221:sNHT26802332"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6QGJIaP025436; 
	Thu, 26 Jul 2007 12:19:18 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6QGIsWk003600; 
	Thu, 26 Jul 2007 16:19:18 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 12:19:06 -0400
Received: from [10.86.241.65] ([10.86.241.65]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 12:19:06 -0400
Message-ID: <46A8C983.4060302@cisco.com>
Date: Thu, 26 Jul 2007 12:19:15 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: IETF SIP List <sip@ietf.org>, IETF Sipping List <sipping@ietf.org>,
	IETF MMUSIC WG <mmusic@ietf.org>, Behave WG <behave@ietf.org>,
	P2PSIP WG <p2psip@ietf.org>, rai@ietf.org, "'avt@ietf.org'" <avt@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Jul 2007 16:19:06.0078 (UTC)
	FILETIME=[B02C9FE0:01C7CFA0]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=740; t=1185466758;
	x=1186330758; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20ICE=20tutorial=20in=20Chicago=20=20-=20PLEASE=20PAY=20IF=20YO
	U=20ATE=20LUNCH |Sender:=20
	|To:=20IETF=20SIP=20List=20<sip@ietf.org>,
	=20IETF=20Sipping=20List=20<sip ping@ietf.org>,
	=0A=20=20=20=20=20=20=20=20IETF=20MMUSIC=20WG=20<mmusic@iet
	f.org>, =20Behave=20WG=20<behave@ietf.org>,
	=0A=20=20=20=20=20=20=20=20P2PSI
	P=20WG=20<p2psip@ietf.org>, =20rai@ietf.org,
	=0A=20=20=20=20=20=20=20=20=22'
	avt@ietf.org'=22=20<avt@ietf.org>;
	bh=Zrtno2xh1JufqqypXQrJG3eaM0QxnaFVcCRKizkJRlU=;
	b=EAbRlhLzYaOy4oHUNIotoEwBXwvoS8Zp1gyIR9U0ZLbsLNA0SW2PWFoOvExi7DXio14brEfh
	Ctw1A+j6KiaWFP+lwWplEuOmXoKwNKI3GCkheAO1e18guOsiXHEOunJT;
Authentication-Results: rtp-dkim-1; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: 
Subject: [AVT] ICE tutorial in Chicago  - PLEASE PAY IF YOU ATE LUNCH
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Lunch during the tutorial was paid out of my pocket, and I was expecting 
to get re-imbursed by everyone that took a sandwich. Though all of the 
food was taken by the end of the tutorial, I am several hundred dollars 
short. Please, if you took lunch and did not give me $20, give it to me 
before you leave, and if you have not, contact me privately and we can 
arrange for paper mail.

Thanks,
Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Cisco Fellow                                   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com


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



From avt-bounces@ietf.org Thu Jul 26 14:55:05 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE8UE-0002KW-U1; Thu, 26 Jul 2007 14:54:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE8UD-0002I5-73; Thu, 26 Jul 2007 14:54:57 -0400
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IE8UB-0006NM-SI; Thu, 26 Jul 2007 14:54:57 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 26 Jul 2007 14:54:54 -0400
To: Internet-Drafts@ietf.org
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-and-rtcp-mux-06.txt
References: <E1IDkRx-0008NY-Tw@stiedprstage1.ietf.org>
From: Randell Jesup <rjesup@wgate.com>
Date: Thu, 26 Jul 2007 14:54:53 -0400
In-Reply-To: <E1IDkRx-0008NY-Tw@stiedprstage1.ietf.org>
	(Internet-Drafts@ietf.org's
	message of "Wed, 25 Jul 2007 13:15:01 -0400")
Message-ID: <ybu1wevxaf6.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 26 Jul 2007 18:54:54.0525 (UTC)
	FILETIME=[74486ED0:01C7CFB6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: avt@ietf.org, i-d-announce@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Internet-Drafts@ietf.org writes:
>Title		: Multiplexing RTP Data and Control Packets on a Single Port
>Filename	: draft-ietf-avt-rtp-and-rtcp-mux-06.txt

>      Note: since all RTCP packets MUST be sent as compound packets
>      beginning with an SR or an RR packet ([1] Section 6.1), one might
>      wonder why RTP payload types other than 72 and 73 are prohibited
>      when multiplexing RTP and RTCP.  This is done to ensure robustness
>      against broken nodes which send non-compliant RTCP packets, which
>      might otherwise be confused with multiplexed RTP packets.

This should mention that relaxing that restriction is under consideration,
(I forget the exact draft name) and that by including the PT restrictions
in this draft we avoid a potential conflict with the other draft (i.e. it
may not be only "broken nodes").  I also would remove the word "broken",
it's misleading.  They are non-compliant with 3261 (until that draft is
approved).

>   When the Session Description Protocol (SDP) [8] is used to negotiate
>   RTP sessions following the offer/answer model [9], the "a=rtcp-mux"
>   attribute (see Section 8) indicates the desire to multiplex RTP and
>   RTCP onto a single port.

We should also discuss interaction with offering both "a=rtcp-mux" and
"a=rtcp <port>".  I can see an endpoint wanting (or needing) to include
both.  The answer selects between rtcp-mux and "normal" rtcp handling
(including a=rtcp, though there's no direct way to know if the answerer
supports it).

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


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



From avt-bounces@ietf.org Thu Jul 26 15:04:00 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE8cx-0003an-N2; Thu, 26 Jul 2007 15:03:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE8cv-0003RM-Fv
	for avt@ietf.org; Thu, 26 Jul 2007 15:03:57 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE8cu-0006XI-0q
	for avt@ietf.org; Thu, 26 Jul 2007 15:03:57 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	387882044F; Thu, 26 Jul 2007 21:03:55 +0200 (CEST)
X-AuditID: c1b4fb3c-af67dbb0000007e1-79-46a8f01bc4da
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	2091A203E4; Thu, 26 Jul 2007 21:03:55 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 21:03:54 +0200
Received: from [138.85.13.64] ([138.85.13.64]) by esealmw128.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 21:03:53 +0200
Message-ID: <46A8F01A.8040809@ericsson.com>
Date: Thu, 26 Jul 2007 21:03:54 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: Michael A Dolan <md.1@newtbt.com>
Subject: Re: [AVT] draft-ietf-avt-hdrext-12
References: <0MKp8S-1IBfib2mC2-0005q2@mrelay.perfora.net>	<p06240803c2cd4d282cd9@[17.202.35.52]>
	<0MKpCa-1IDqsy0MRm-0006V5@mrelay.perfora.net>
In-Reply-To: <0MKpCa-1IDqsy0MRm-0006V5@mrelay.perfora.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Jul 2007 19:03:54.0135 (UTC)
	FILETIME=[B5EA6270:01C7CFB7]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Michael A Dolan skrev:
> Dave and all-
> 
> I was hoping to avoid a debate on relative deployment and the value of 4 
> bits versus 8 bits by proposing option (c) below (which is what I tried 
> to articulate in last week's post).  In a perfect world, we would drive 
> to (a), but I don't see how to get there in any reasonable timeline.  
> Mean-time the world moves on making more of these deployments, and 
> worse, more non-conformant variants we don't even know about....
> 
> Can everyone live with option (c)?

Preferably no, this is a core extension that we are likely to see quite 
a lot of use in the future. I think 4+4 has a good tradeoff. I would 
like to go with a) because of this to avoid confusing things. If there 
are "proprieatery" deployment as it is of 8+8 that is not different from 
other "proprieatery" extensions in this field.

>> Choices:
>>
>> a) go with just 4+4 or just 8+8, and drop one.  I am aware of 
>> implementations of both, so this isn't ideal.
>>
>> b) in the same document, require support for both.
>>
>> c) in the same document, require support for one, and recommend 
>> support for the other.
>>
>> d) publish one separately, as an informational RFC.
>>

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
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 Jul 26 15:29:00 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE919-0001ii-AE; Thu, 26 Jul 2007 15:28:59 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE917-0001cT-AW
	for avt@ietf.org; Thu, 26 Jul 2007 15:28:57 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE916-0005ya-Ja
	for avt@ietf.org; Thu, 26 Jul 2007 15:28:57 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] Suggestion for how to handle derived/computed
	metricindraft-avt-rtcpxr-*
Date: Thu, 26 Jul 2007 22:29:48 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04CB2830@IsrExch01.israel.polycom.com>
In-Reply-To: <E1ID65y-0007yS-87@megatron.ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Suggestion for how to handle derived/computed
	metricindraft-avt-rtcpxr-*
Thread-Index: AcfNc7oRbzj6yFgLRoiVoFylGITe4AAAYpswAJEyAsA=
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Alan Clark" <alan.d.clark@telchemy.com>, "David R Oran" <oran@cisco.com>,
	"AVT WG" <avt@ietf.org>
X-Spam-Score: 0.4 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Alan,
What bothers me is that in my view many people building audio and video
EPs will use codecs that come from the DSP manufacturer or from a open
source library. It will be difficult to them to choose the right
metrics. I am not the biggest expert on quality assessments but I think
that there is a difference between the current voice codecs (3, 7Khz)
and the new audio ones (14 and 20Khz) which are now used in video
conferencing and are coming to VOIP applications in term of the quality
assessment.=20

Now how do you expect a non-educated EP developer to know what is the
right way to calculate the quality. How will he calculate quality if his
system may use G.711 in one call and AAC-LD in a second call. It needs
either to be very easy to understand or just ask him for raw data.

Roni=20

> -----Original Message-----
> From: Alan Clark [mailto:alan.d.clark@telchemy.com]
> Sent: Tuesday, July 24, 2007 1:08 AM
> To: 'David R Oran'; 'AVT WG'
> Subject: RE: [AVT] Suggestion for how to handle derived/computed
> metricindraft-avt-rtcpxr-*
>=20
> Dave
>=20
> I agree with the general tenor of your thoughts.  I also agree that we
> should not mandate that endpoints have to implement any particular set
of
> derived metrics - these should be optional and should be implemented
based
> on their usefulness.
>=20
> For cases in which there is a fairly well defined metric class (e.g.
MOS
> for
> speech) then I suggest that we do define a separate draft for that
with a
> registry of algorithms that could be (optionally) used - it is easier
to
> update a registry with information that a new version of ITU-T G.xxx
is
> available than it would be to generate a new draft.
>=20
> Regards
>=20
> Alan
>=20
>=20
> -----Original Message-----
> From: David R Oran [mailto:oran@cisco.com]
> Sent: Monday, July 23, 2007 5:51 PM
> To: AVT WG
> Subject: [AVT] Suggestion for how to handle derived/computed metric
> indraft-avt-rtcpxr-*
>=20
> At the Mic during the AVT session I sketched a vague idea for how to
> resolve
> the conflict between the desire on the part of many folks to only
carry
> raw/primitive instrumented measurements in RTCP-XR, and other equally
> vocal,
> who argued for carrying the derived/computed metrics as well.
>=20
> I won't repeat the pro/con arguments here. Let's assume we want to
carry
> both.
>=20
> The chairs asked me to write up my vague thoughts as the beginnings of
a
> concrete proposal.
>=20
> Some particular technical difficulties with the derived metrics that
makes
> them different from the primitive measurements is:
> - there are competing standards for how to compute them
> - the results are not generally aggregatable, comparable, or self-
> describing.
> - the set of interesting derived metrics is not small and seems to be
> growing, so it will be difficult to nail these down for stable RTCP
> reporting.
>=20
> This makes it problematic to mix primitive and derived metrics in the
same
> metric blocks in RTCP.
>=20
> So, my suggestion is to do the following.
>=20
> - A standards body who defines one or more consistent derived metrics
may
> create (by bringing a draft to IETF) a separate metric block for those
> metrics.
> - The block and its contained derived/computed metrics would be
completely
> self-describing in terms of exactly what version of what standard
defines
> the block.
> - The definition of the metric would explicit contain the input
variables,
> in order to ensure that those inputs are separately available as
primitive
> metrics in the RTCP-XR. This increases the probability that any metric
> that
> is computable by the endpoint is also computable by a central element
> receiving and processing RTCP-XR reports.
> - If there are competing/overlapping blocks, an endpoint need not do
all
> of
> them and there would be no confusion about exactly which (e.g."video
MOS")
> calculation was done.
>=20
> As an aside, I would rather not see further updates to the existing
drafts
> until we resolve this issue, since this is in fact major surgery to
the
> documents that is best done before polishing the text and individual
> metric
> definitions.
>=20
> Dave Oran.
>=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

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



From avt-bounces@ietf.org Thu Jul 26 16:00:04 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE9V8-0006sW-QZ; Thu, 26 Jul 2007 15:59:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE9V7-0006sQ-NY
	for avt@ietf.org; Thu, 26 Jul 2007 15:59:57 -0400
Received: from mx.cbeyond.com ([66.180.96.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE9V6-0007oW-8c
	for avt@ietf.org; Thu, 26 Jul 2007 15:59:57 -0400
Received: from [130.129.19.169] (port=3322 helo=TELCHADCPC)
	by mx.cbeyond.com with asmtp (Exim 4.34)
	id 1IE9V5-0002Ed-Or; Thu, 26 Jul 2007 15:59:55 -0400
From: "Alan Clark" <alan.d.clark@telchemy.com>
To: "'Even, Roni'" <roni.even@polycom.co.il>,
	"'David R Oran'" <oran@cisco.com>, "'AVT WG'" <avt@ietf.org>
Subject: RE: [AVT] Suggestion for how to handle
	derived/computedmetricindraft-avt-rtcpxr-*
Date: Thu, 26 Jul 2007 15:58:44 -0400
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.2962
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C04CB2830@IsrExch01.israel.polycom.com>
Thread-Index: AcfNc7oRbzj6yFgLRoiVoFylGITe4AAAYpswAJEyAsAAANad0A==
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 4b7d60495f1a7f2e853e8cbae7e6dbfc
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org
Message-Id: <E1IE9V8-0006sW-QZ@megatron.ietf.org>


Roni

Certainly there is a difference between voice and audio codecs. In the case
of voice codecs (both narrowband and wideband) the methods for objectively
measuring the quality of the call and for taking codec characteristics into
account is well understood - there are admittedly several approaches however
there are existing standards that address means for calculating objective
estimates of MOS and even for conformance testing of algorithms that do
this.  

The approach used for voice quality is fairly straightforward.  There are
several parameters that are defined on a codec specific basis - notably Ie
and Bpl, where Ie identifies the quality degradation due to the encoder and
Bpl the robustness of the PLC algorithm against packet loss/ discard.  The
endpoint incorporates a small table of these values for each voice codec
that it supports.  Based on the codec selected for the call - the
appropriate parameters are used.  Some other parameters, for example signal
level, noise level, echo, delay, are less codec dependant.  A good source of
information on how to do this using G.107 is ITU-T Recommendation G.799.1,
which is a VoIP trunking gateway standard that incorporates a clear
definition of how to compute the R factors and MOS scores required by RTCP
XR.

Methods for measuring audio quality are less heavily standardized at this
time, although there are ITU standards such as G.1070 (for IP
videoconferencing) that incorporate voice, video and multimedia quality
metrics and ITU-R BS-1387 (which is a PESQ-like algorithm for audio).  There
is ongoing work within the industry related to IPTV audio stream measurement
that is occurring in at least three different standards organizations.

I'd be happy to put together an informational document that outlines
existing approaches to objective voice/ audio/ video performance measurement
and reviews some of the current industry activities - if that would be
useful?

Regards

Alan





-----Original Message-----
From: Even, Roni [mailto:roni.even@polycom.co.il] 
Sent: Thursday, July 26, 2007 3:30 PM
To: Alan Clark; David R Oran; AVT WG
Subject: RE: [AVT] Suggestion for how to handle
derived/computedmetricindraft-avt-rtcpxr-*

Alan,
What bothers me is that in my view many people building audio and video EPs
will use codecs that come from the DSP manufacturer or from a open source
library. It will be difficult to them to choose the right metrics. I am not
the biggest expert on quality assessments but I think that there is a
difference between the current voice codecs (3, 7Khz) and the new audio ones
(14 and 20Khz) which are now used in video conferencing and are coming to
VOIP applications in term of the quality assessment. 

Now how do you expect a non-educated EP developer to know what is the right
way to calculate the quality. How will he calculate quality if his system
may use G.711 in one call and AAC-LD in a second call. It needs either to be
very easy to understand or just ask him for raw data.

Roni 

> -----Original Message-----
> From: Alan Clark [mailto:alan.d.clark@telchemy.com]
> Sent: Tuesday, July 24, 2007 1:08 AM
> To: 'David R Oran'; 'AVT WG'
> Subject: RE: [AVT] Suggestion for how to handle derived/computed
> metricindraft-avt-rtcpxr-*
> 
> Dave
> 
> I agree with the general tenor of your thoughts.  I also agree that we 
> should not mandate that endpoints have to implement any particular set
of
> derived metrics - these should be optional and should be implemented
based
> on their usefulness.
> 
> For cases in which there is a fairly well defined metric class (e.g.
MOS
> for
> speech) then I suggest that we do define a separate draft for that
with a
> registry of algorithms that could be (optionally) used - it is easier
to
> update a registry with information that a new version of ITU-T G.xxx
is
> available than it would be to generate a new draft.
> 
> Regards
> 
> Alan
> 
> 
> -----Original Message-----
> From: David R Oran [mailto:oran@cisco.com]
> Sent: Monday, July 23, 2007 5:51 PM
> To: AVT WG
> Subject: [AVT] Suggestion for how to handle derived/computed metric
> indraft-avt-rtcpxr-*
> 
> At the Mic during the AVT session I sketched a vague idea for how to 
> resolve the conflict between the desire on the part of many folks to 
> only
carry
> raw/primitive instrumented measurements in RTCP-XR, and other equally 
> vocal, who argued for carrying the derived/computed metrics as well.
> 
> I won't repeat the pro/con arguments here. Let's assume we want to
carry
> both.
> 
> The chairs asked me to write up my vague thoughts as the beginnings of
a
> concrete proposal.
> 
> Some particular technical difficulties with the derived metrics that
makes
> them different from the primitive measurements is:
> - there are competing standards for how to compute them
> - the results are not generally aggregatable, comparable, or self- 
> describing.
> - the set of interesting derived metrics is not small and seems to be 
> growing, so it will be difficult to nail these down for stable RTCP 
> reporting.
> 
> This makes it problematic to mix primitive and derived metrics in the
same
> metric blocks in RTCP.
> 
> So, my suggestion is to do the following.
> 
> - A standards body who defines one or more consistent derived metrics
may
> create (by bringing a draft to IETF) a separate metric block for those 
> metrics.
> - The block and its contained derived/computed metrics would be
completely
> self-describing in terms of exactly what version of what standard
defines
> the block.
> - The definition of the metric would explicit contain the input
variables,
> in order to ensure that those inputs are separately available as
primitive
> metrics in the RTCP-XR. This increases the probability that any metric 
> that is computable by the endpoint is also computable by a central 
> element receiving and processing RTCP-XR reports.
> - If there are competing/overlapping blocks, an endpoint need not do
all
> of
> them and there would be no confusion about exactly which (e.g."video
MOS")
> calculation was done.
> 
> As an aside, I would rather not see further updates to the existing
drafts
> until we resolve this issue, since this is in fact major surgery to
the
> documents that is best done before polishing the text and individual 
> metric definitions.
> 
> Dave Oran.
> 
> _______________________________________________
> 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


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



From avt-bounces@ietf.org Thu Jul 26 16:02:29 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE9XY-0001s2-KS; Thu, 26 Jul 2007 16:02:28 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE9XW-0001rm-Ri
	for avt@ietf.org; Thu, 26 Jul 2007 16:02:26 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE9XV-0006pv-NT
	for avt@ietf.org; Thu, 26 Jul 2007 16:02:26 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] Suggestion for how to handle
	derived/computedmetricindraft-avt-rtcpxr-*
Date: Thu, 26 Jul 2007 23:03:20 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04CB2834@IsrExch01.israel.polycom.com>
In-Reply-To: <20070726195516.96D39181C1F@mailmr.polycom.co.il>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Suggestion for how to handle
	derived/computedmetricindraft-avt-rtcpxr-*
Thread-Index: AcfNc7oRbzj6yFgLRoiVoFylGITe4AAAYpswAJEyAsAAANad0AAAmbYA
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Alan Clark" <alan.d.clark@telchemy.com>, "David R Oran" <oran@cisco.com>,
	"AVT WG" <avt@ietf.org>
X-Spam-Score: 0.4 (/)
X-Scan-Signature: ce732c7d36989a1bd55104ba259c40a1
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Alan,
This will be helpful.
Still my concern is that EP implementers will not know what to calculate
since their product may use different types of codecs.
Roni

> -----Original Message-----
> From: Alan Clark [mailto:alan.d.clark@telchemy.com]
> Sent: Thursday, July 26, 2007 10:59 PM
> To: Even, Roni; 'David R Oran'; 'AVT WG'
> Subject: RE: [AVT] Suggestion for how to handle
> derived/computedmetricindraft-avt-rtcpxr-*
>=20
>=20
> Roni
>=20
> Certainly there is a difference between voice and audio codecs. In the
> case
> of voice codecs (both narrowband and wideband) the methods for
objectively
> measuring the quality of the call and for taking codec characteristics
> into
> account is well understood - there are admittedly several approaches
> however
> there are existing standards that address means for calculating
objective
> estimates of MOS and even for conformance testing of algorithms that
do
> this.
>=20
> The approach used for voice quality is fairly straightforward.  There
are
> several parameters that are defined on a codec specific basis -
notably Ie
> and Bpl, where Ie identifies the quality degradation due to the
encoder
> and
> Bpl the robustness of the PLC algorithm against packet loss/ discard.
The
> endpoint incorporates a small table of these values for each voice
codec
> that it supports.  Based on the codec selected for the call - the
> appropriate parameters are used.  Some other parameters, for example
> signal
> level, noise level, echo, delay, are less codec dependant.  A good
source
> of
> information on how to do this using G.107 is ITU-T Recommendation
G.799.1,
> which is a VoIP trunking gateway standard that incorporates a clear
> definition of how to compute the R factors and MOS scores required by
RTCP
> XR.
>=20
> Methods for measuring audio quality are less heavily standardized at
this
> time, although there are ITU standards such as G.1070 (for IP
> videoconferencing) that incorporate voice, video and multimedia
quality
> metrics and ITU-R BS-1387 (which is a PESQ-like algorithm for audio).
> There
> is ongoing work within the industry related to IPTV audio stream
> measurement
> that is occurring in at least three different standards organizations.
>=20
> I'd be happy to put together an informational document that outlines
> existing approaches to objective voice/ audio/ video performance
> measurement
> and reviews some of the current industry activities - if that would be
> useful?
>=20
> Regards
>=20
> Alan
>=20
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: Even, Roni [mailto:roni.even@polycom.co.il]
> Sent: Thursday, July 26, 2007 3:30 PM
> To: Alan Clark; David R Oran; AVT WG
> Subject: RE: [AVT] Suggestion for how to handle
> derived/computedmetricindraft-avt-rtcpxr-*
>=20
> Alan,
> What bothers me is that in my view many people building audio and
video
> EPs
> will use codecs that come from the DSP manufacturer or from a open
source
> library. It will be difficult to them to choose the right metrics. I
am
> not
> the biggest expert on quality assessments but I think that there is a
> difference between the current voice codecs (3, 7Khz) and the new
audio
> ones
> (14 and 20Khz) which are now used in video conferencing and are coming
to
> VOIP applications in term of the quality assessment.
>=20
> Now how do you expect a non-educated EP developer to know what is the
> right
> way to calculate the quality. How will he calculate quality if his
system
> may use G.711 in one call and AAC-LD in a second call. It needs either
to
> be
> very easy to understand or just ask him for raw data.
>=20
> Roni
>=20
> > -----Original Message-----
> > From: Alan Clark [mailto:alan.d.clark@telchemy.com]
> > Sent: Tuesday, July 24, 2007 1:08 AM
> > To: 'David R Oran'; 'AVT WG'
> > Subject: RE: [AVT] Suggestion for how to handle derived/computed
> > metricindraft-avt-rtcpxr-*
> >
> > Dave
> >
> > I agree with the general tenor of your thoughts.  I also agree that
we
> > should not mandate that endpoints have to implement any particular
set
> of
> > derived metrics - these should be optional and should be implemented
> based
> > on their usefulness.
> >
> > For cases in which there is a fairly well defined metric class (e.g.
> MOS
> > for
> > speech) then I suggest that we do define a separate draft for that
> with a
> > registry of algorithms that could be (optionally) used - it is
easier
> to
> > update a registry with information that a new version of ITU-T G.xxx
> is
> > available than it would be to generate a new draft.
> >
> > Regards
> >
> > Alan
> >
> >
> > -----Original Message-----
> > From: David R Oran [mailto:oran@cisco.com]
> > Sent: Monday, July 23, 2007 5:51 PM
> > To: AVT WG
> > Subject: [AVT] Suggestion for how to handle derived/computed metric
> > indraft-avt-rtcpxr-*
> >
> > At the Mic during the AVT session I sketched a vague idea for how to
> > resolve the conflict between the desire on the part of many folks to
> > only
> carry
> > raw/primitive instrumented measurements in RTCP-XR, and other
equally
> > vocal, who argued for carrying the derived/computed metrics as well.
> >
> > I won't repeat the pro/con arguments here. Let's assume we want to
> carry
> > both.
> >
> > The chairs asked me to write up my vague thoughts as the beginnings
of
> a
> > concrete proposal.
> >
> > Some particular technical difficulties with the derived metrics that
> makes
> > them different from the primitive measurements is:
> > - there are competing standards for how to compute them
> > - the results are not generally aggregatable, comparable, or self-
> > describing.
> > - the set of interesting derived metrics is not small and seems to
be
> > growing, so it will be difficult to nail these down for stable RTCP
> > reporting.
> >
> > This makes it problematic to mix primitive and derived metrics in
the
> same
> > metric blocks in RTCP.
> >
> > So, my suggestion is to do the following.
> >
> > - A standards body who defines one or more consistent derived
metrics
> may
> > create (by bringing a draft to IETF) a separate metric block for
those
> > metrics.
> > - The block and its contained derived/computed metrics would be
> completely
> > self-describing in terms of exactly what version of what standard
> defines
> > the block.
> > - The definition of the metric would explicit contain the input
> variables,
> > in order to ensure that those inputs are separately available as
> primitive
> > metrics in the RTCP-XR. This increases the probability that any
metric
> > that is computable by the endpoint is also computable by a central
> > element receiving and processing RTCP-XR reports.
> > - If there are competing/overlapping blocks, an endpoint need not do
> all
> > of
> > them and there would be no confusion about exactly which (e.g."video
> MOS")
> > calculation was done.
> >
> > As an aside, I would rather not see further updates to the existing
> drafts
> > until we resolve this issue, since this is in fact major surgery to
> the
> > documents that is best done before polishing the text and individual
> > metric definitions.
> >
> > Dave Oran.
> >
> > _______________________________________________
> > 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
> _______________________________________________
> 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 Jul 26 16:27:16 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE9vR-0007LY-4D; Thu, 26 Jul 2007 16:27:09 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE9vQ-0007LT-I9
	for avt@ietf.org; Thu, 26 Jul 2007 16:27:08 -0400
Received: from mx.cbeyond.com ([66.180.96.58])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE9vP-0007IK-IN
	for avt@ietf.org; Thu, 26 Jul 2007 16:27:08 -0400
Received: from [130.129.19.169] (port=3333 helo=TELCHADCPC)
	by mx.cbeyond.com with esmtpa (Exim 4.62)
	(envelope-from <alan.d.clark@telchemy.com>)
	id 1IE9vO-0000CV-HB; Thu, 26 Jul 2007 16:27:07 -0400
From: "Alan Clark" <alan.d.clark@telchemy.com>
To: "'Even, Roni'" <roni.even@polycom.co.il>,
	"'David R Oran'" <oran@cisco.com>, "'AVT WG'" <avt@ietf.org>
Subject: RE: [AVT] Suggestion for how to
	handlederived/computedmetricindraft-avt-rtcpxr-*
Date: Thu, 26 Jul 2007 16:25:55 -0400
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.2962
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C04CB2834@IsrExch01.israel.polycom.com>
Thread-Index: AcfNc7oRbzj6yFgLRoiVoFylGITe4AAAYpswAJEyAsAAANad0AAAmbYAAAB5N5A=
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a4e5f67c5e230eddf754446d1a2201a4
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org
Message-Id: <E1IE9vR-0007LY-4D@megatron.ietf.org>


Roni

Well ... for voice codecs it is well specified how this can be done, there
are published tables of codec parameters and even published standards on the
process used to characterize codecs.  The informational document could
provide both subject matter background and annotated references to the
relevant standards.

BTW - some of the codec vendors are directly incorporating voice quality
monitoring functions, which makes it trivially easy for implementors.
Amongst the codec vendors I'm aware of - this would account for 70-80% of
the codec chipsets/ software supplied to the industry.  

Regards

Alan




 

-----Original Message-----
From: Even, Roni [mailto:roni.even@polycom.co.il] 
Sent: Thursday, July 26, 2007 4:03 PM
To: Alan Clark; David R Oran; AVT WG
Subject: RE: [AVT] Suggestion for how to
handlederived/computedmetricindraft-avt-rtcpxr-*

Alan,
This will be helpful.
Still my concern is that EP implementers will not know what to calculate
since their product may use different types of codecs.
Roni

> -----Original Message-----
> From: Alan Clark [mailto:alan.d.clark@telchemy.com]
> Sent: Thursday, July 26, 2007 10:59 PM
> To: Even, Roni; 'David R Oran'; 'AVT WG'
> Subject: RE: [AVT] Suggestion for how to handle
> derived/computedmetricindraft-avt-rtcpxr-*
> 
> 
> Roni
> 
> Certainly there is a difference between voice and audio codecs. In the 
> case of voice codecs (both narrowband and wideband) the methods for
objectively
> measuring the quality of the call and for taking codec characteristics 
> into account is well understood - there are admittedly several 
> approaches however there are existing standards that address means for 
> calculating
objective
> estimates of MOS and even for conformance testing of algorithms that
do
> this.
> 
> The approach used for voice quality is fairly straightforward.  There
are
> several parameters that are defined on a codec specific basis -
notably Ie
> and Bpl, where Ie identifies the quality degradation due to the
encoder
> and
> Bpl the robustness of the PLC algorithm against packet loss/ discard.
The
> endpoint incorporates a small table of these values for each voice
codec
> that it supports.  Based on the codec selected for the call - the 
> appropriate parameters are used.  Some other parameters, for example 
> signal level, noise level, echo, delay, are less codec dependant.  A 
> good
source
> of
> information on how to do this using G.107 is ITU-T Recommendation
G.799.1,
> which is a VoIP trunking gateway standard that incorporates a clear 
> definition of how to compute the R factors and MOS scores required by
RTCP
> XR.
> 
> Methods for measuring audio quality are less heavily standardized at
this
> time, although there are ITU standards such as G.1070 (for IP
> videoconferencing) that incorporate voice, video and multimedia
quality
> metrics and ITU-R BS-1387 (which is a PESQ-like algorithm for audio).
> There
> is ongoing work within the industry related to IPTV audio stream 
> measurement that is occurring in at least three different standards 
> organizations.
> 
> I'd be happy to put together an informational document that outlines 
> existing approaches to objective voice/ audio/ video performance 
> measurement and reviews some of the current industry activities - if 
> that would be useful?
> 
> Regards
> 
> Alan
> 
> 
> 
> 
> 
> -----Original Message-----
> From: Even, Roni [mailto:roni.even@polycom.co.il]
> Sent: Thursday, July 26, 2007 3:30 PM
> To: Alan Clark; David R Oran; AVT WG
> Subject: RE: [AVT] Suggestion for how to handle
> derived/computedmetricindraft-avt-rtcpxr-*
> 
> Alan,
> What bothers me is that in my view many people building audio and
video
> EPs
> will use codecs that come from the DSP manufacturer or from a open
source
> library. It will be difficult to them to choose the right metrics. I
am
> not
> the biggest expert on quality assessments but I think that there is a 
> difference between the current voice codecs (3, 7Khz) and the new
audio
> ones
> (14 and 20Khz) which are now used in video conferencing and are coming
to
> VOIP applications in term of the quality assessment.
> 
> Now how do you expect a non-educated EP developer to know what is the 
> right way to calculate the quality. How will he calculate quality if 
> his
system
> may use G.711 in one call and AAC-LD in a second call. It needs either
to
> be
> very easy to understand or just ask him for raw data.
> 
> Roni
> 
> > -----Original Message-----
> > From: Alan Clark [mailto:alan.d.clark@telchemy.com]
> > Sent: Tuesday, July 24, 2007 1:08 AM
> > To: 'David R Oran'; 'AVT WG'
> > Subject: RE: [AVT] Suggestion for how to handle derived/computed
> > metricindraft-avt-rtcpxr-*
> >
> > Dave
> >
> > I agree with the general tenor of your thoughts.  I also agree that
we
> > should not mandate that endpoints have to implement any particular
set
> of
> > derived metrics - these should be optional and should be implemented
> based
> > on their usefulness.
> >
> > For cases in which there is a fairly well defined metric class (e.g.
> MOS
> > for
> > speech) then I suggest that we do define a separate draft for that
> with a
> > registry of algorithms that could be (optionally) used - it is
easier
> to
> > update a registry with information that a new version of ITU-T G.xxx
> is
> > available than it would be to generate a new draft.
> >
> > Regards
> >
> > Alan
> >
> >
> > -----Original Message-----
> > From: David R Oran [mailto:oran@cisco.com]
> > Sent: Monday, July 23, 2007 5:51 PM
> > To: AVT WG
> > Subject: [AVT] Suggestion for how to handle derived/computed metric
> > indraft-avt-rtcpxr-*
> >
> > At the Mic during the AVT session I sketched a vague idea for how to 
> > resolve the conflict between the desire on the part of many folks to 
> > only
> carry
> > raw/primitive instrumented measurements in RTCP-XR, and other
equally
> > vocal, who argued for carrying the derived/computed metrics as well.
> >
> > I won't repeat the pro/con arguments here. Let's assume we want to
> carry
> > both.
> >
> > The chairs asked me to write up my vague thoughts as the beginnings
of
> a
> > concrete proposal.
> >
> > Some particular technical difficulties with the derived metrics that
> makes
> > them different from the primitive measurements is:
> > - there are competing standards for how to compute them
> > - the results are not generally aggregatable, comparable, or self- 
> > describing.
> > - the set of interesting derived metrics is not small and seems to
be
> > growing, so it will be difficult to nail these down for stable RTCP 
> > reporting.
> >
> > This makes it problematic to mix primitive and derived metrics in
the
> same
> > metric blocks in RTCP.
> >
> > So, my suggestion is to do the following.
> >
> > - A standards body who defines one or more consistent derived
metrics
> may
> > create (by bringing a draft to IETF) a separate metric block for
those
> > metrics.
> > - The block and its contained derived/computed metrics would be
> completely
> > self-describing in terms of exactly what version of what standard
> defines
> > the block.
> > - The definition of the metric would explicit contain the input
> variables,
> > in order to ensure that those inputs are separately available as
> primitive
> > metrics in the RTCP-XR. This increases the probability that any
metric
> > that is computable by the endpoint is also computable by a central 
> > element receiving and processing RTCP-XR reports.
> > - If there are competing/overlapping blocks, an endpoint need not do
> all
> > of
> > them and there would be no confusion about exactly which (e.g."video
> MOS")
> > calculation was done.
> >
> > As an aside, I would rather not see further updates to the existing
> drafts
> > until we resolve this issue, since this is in fact major surgery to
> the
> > documents that is best done before polishing the text and individual 
> > metric definitions.
> >
> > Dave Oran.
> >
> > _______________________________________________
> > 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


_______________________________________________
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 Jul 26 16:43:49 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEABT-0007GK-VN; Thu, 26 Jul 2007 16:43:43 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEABS-00078h-EX
	for avt@ietf.org; Thu, 26 Jul 2007 16:43:42 -0400
Received: from expint.psytechnics.com ([217.33.106.234])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEABR-0007iI-B9
	for avt@ietf.org; Thu, 26 Jul 2007 16:43:42 -0400
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
Subject: RE: [AVT] Suggestion for how to
	handlederived/computedmetricindraft-avt-rtcpxr-*[Scanned]
Date: Thu, 26 Jul 2007 21:45:31 +0100
Message-ID: <257B18BFF522214E92EB52F3478B014EA0A608@psy01exch.intra.psytechnics.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Suggestion for how to
	handlederived/computedmetricindraft-avt-rtcpxr-*[Scanned]
thread-index: AcfNc7oRbzj6yFgLRoiVoFylGITe4AAAYpswAJEyAsAAANad0AAAmbYAAAEqMSA=
From: "Ravi Raviraj" <ravi.raviraj@psytechnics.com>
To: "Even, Roni" <roni.even@polycom.co.il>,
	"Alan Clark" <alan.d.clark@telchemy.com>, "David R Oran" <oran@cisco.com>,
	"AVT WG" <avt@ietf.org>
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a4cdc653ecdd96665f2aa1c1af034c9e
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Roni,
When the EP reports MOS values, it should identify exactly which
standard it used to generate the MOS value and any variation within it.
In this way there won't be any confusion.
As in any other standard, when an EP implementer claims compliance to a
specific standard, they will(should) know what they are talking about.

My draft
https://datatracker.ietf.org/drafts/draft-raviraj-sipping-endpoint-mos/
shows the number of variations one could have with perceptual MOS. I
will bring a draft next time to identify the standards we should
identify.=20

Ravi.


-----Original Message-----
From: Even, Roni [mailto:roni.even@polycom.co.il]=20
Sent: 26 July 2007 21:03
To: Alan Clark; David R Oran; AVT WG
Subject: RE: [AVT] Suggestion for how to
handlederived/computedmetricindraft-avt-rtcpxr-*[Scanned]

Alan,
This will be helpful.
Still my concern is that EP implementers will not know what to calculate
since their product may use different types of codecs.
Roni

> -----Original Message-----
> From: Alan Clark [mailto:alan.d.clark@telchemy.com]
> Sent: Thursday, July 26, 2007 10:59 PM
> To: Even, Roni; 'David R Oran'; 'AVT WG'
> Subject: RE: [AVT] Suggestion for how to handle
> derived/computedmetricindraft-avt-rtcpxr-*
>=20
>=20
> Roni
>=20
> Certainly there is a difference between voice and audio codecs. In the
> case
> of voice codecs (both narrowband and wideband) the methods for
objectively
> measuring the quality of the call and for taking codec characteristics
> into
> account is well understood - there are admittedly several approaches
> however
> there are existing standards that address means for calculating
objective
> estimates of MOS and even for conformance testing of algorithms that
do
> this.
>=20
> The approach used for voice quality is fairly straightforward.  There
are
> several parameters that are defined on a codec specific basis -
notably Ie
> and Bpl, where Ie identifies the quality degradation due to the
encoder
> and
> Bpl the robustness of the PLC algorithm against packet loss/ discard.
The
> endpoint incorporates a small table of these values for each voice
codec
> that it supports.  Based on the codec selected for the call - the
> appropriate parameters are used.  Some other parameters, for example
> signal
> level, noise level, echo, delay, are less codec dependant.  A good
source
> of
> information on how to do this using G.107 is ITU-T Recommendation
G.799.1,
> which is a VoIP trunking gateway standard that incorporates a clear
> definition of how to compute the R factors and MOS scores required by
RTCP
> XR.
>=20
> Methods for measuring audio quality are less heavily standardized at
this
> time, although there are ITU standards such as G.1070 (for IP
> videoconferencing) that incorporate voice, video and multimedia
quality
> metrics and ITU-R BS-1387 (which is a PESQ-like algorithm for audio).
> There
> is ongoing work within the industry related to IPTV audio stream
> measurement
> that is occurring in at least three different standards organizations.
>=20
> I'd be happy to put together an informational document that outlines
> existing approaches to objective voice/ audio/ video performance
> measurement
> and reviews some of the current industry activities - if that would be
> useful?
>=20
> Regards
>=20
> Alan
>=20
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: Even, Roni [mailto:roni.even@polycom.co.il]
> Sent: Thursday, July 26, 2007 3:30 PM
> To: Alan Clark; David R Oran; AVT WG
> Subject: RE: [AVT] Suggestion for how to handle
> derived/computedmetricindraft-avt-rtcpxr-*
>=20
> Alan,
> What bothers me is that in my view many people building audio and
video
> EPs
> will use codecs that come from the DSP manufacturer or from a open
source
> library. It will be difficult to them to choose the right metrics. I
am
> not
> the biggest expert on quality assessments but I think that there is a
> difference between the current voice codecs (3, 7Khz) and the new
audio
> ones
> (14 and 20Khz) which are now used in video conferencing and are coming
to
> VOIP applications in term of the quality assessment.
>=20
> Now how do you expect a non-educated EP developer to know what is the
> right
> way to calculate the quality. How will he calculate quality if his
system
> may use G.711 in one call and AAC-LD in a second call. It needs either
to
> be
> very easy to understand or just ask him for raw data.
>=20
> Roni
>=20
> > -----Original Message-----
> > From: Alan Clark [mailto:alan.d.clark@telchemy.com]
> > Sent: Tuesday, July 24, 2007 1:08 AM
> > To: 'David R Oran'; 'AVT WG'
> > Subject: RE: [AVT] Suggestion for how to handle derived/computed
> > metricindraft-avt-rtcpxr-*
> >
> > Dave
> >
> > I agree with the general tenor of your thoughts.  I also agree that
we
> > should not mandate that endpoints have to implement any particular
set
> of
> > derived metrics - these should be optional and should be implemented
> based
> > on their usefulness.
> >
> > For cases in which there is a fairly well defined metric class (e.g.
> MOS
> > for
> > speech) then I suggest that we do define a separate draft for that
> with a
> > registry of algorithms that could be (optionally) used - it is
easier
> to
> > update a registry with information that a new version of ITU-T G.xxx
> is
> > available than it would be to generate a new draft.
> >
> > Regards
> >
> > Alan
> >
> >
> > -----Original Message-----
> > From: David R Oran [mailto:oran@cisco.com]
> > Sent: Monday, July 23, 2007 5:51 PM
> > To: AVT WG
> > Subject: [AVT] Suggestion for how to handle derived/computed metric
> > indraft-avt-rtcpxr-*
> >
> > At the Mic during the AVT session I sketched a vague idea for how to
> > resolve the conflict between the desire on the part of many folks to
> > only
> carry
> > raw/primitive instrumented measurements in RTCP-XR, and other
equally
> > vocal, who argued for carrying the derived/computed metrics as well.
> >
> > I won't repeat the pro/con arguments here. Let's assume we want to
> carry
> > both.
> >
> > The chairs asked me to write up my vague thoughts as the beginnings
of
> a
> > concrete proposal.
> >
> > Some particular technical difficulties with the derived metrics that
> makes
> > them different from the primitive measurements is:
> > - there are competing standards for how to compute them
> > - the results are not generally aggregatable, comparable, or self-
> > describing.
> > - the set of interesting derived metrics is not small and seems to
be
> > growing, so it will be difficult to nail these down for stable RTCP
> > reporting.
> >
> > This makes it problematic to mix primitive and derived metrics in
the
> same
> > metric blocks in RTCP.
> >
> > So, my suggestion is to do the following.
> >
> > - A standards body who defines one or more consistent derived
metrics
> may
> > create (by bringing a draft to IETF) a separate metric block for
those
> > metrics.
> > - The block and its contained derived/computed metrics would be
> completely
> > self-describing in terms of exactly what version of what standard
> defines
> > the block.
> > - The definition of the metric would explicit contain the input
> variables,
> > in order to ensure that those inputs are separately available as
> primitive
> > metrics in the RTCP-XR. This increases the probability that any
metric
> > that is computable by the endpoint is also computable by a central
> > element receiving and processing RTCP-XR reports.
> > - If there are competing/overlapping blocks, an endpoint need not do
> all
> > of
> > them and there would be no confusion about exactly which (e.g."video
> MOS")
> > calculation was done.
> >
> > As an aside, I would rather not see further updates to the existing
> drafts
> > until we resolve this issue, since this is in fact major surgery to
> the
> > documents that is best done before polishing the text and individual
> > metric definitions.
> >
> > Dave Oran.
> >
> > _______________________________________________
> > 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
> _______________________________________________
> 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

This email and attachment are confidential. If you have received this =
message in error, please notify the sender immediately and delete the =
message from your computer. Psytechnics Ltd has taken steps to ensure =
that this email is virus free but the recipient should take necessary =
steps to make certain.

Company Name : Psytechnics Ltd
Registered Number : 4110724
Registered Office : Fraser House, 23 Museum St, Ipswich, Suffolk, IP1 =
1HN, UK
Registration : England and Wales


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



From avt-bounces@ietf.org Thu Jul 26 16:54:19 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEALi-0000cr-Ed; Thu, 26 Jul 2007 16:54:18 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEALh-0000cl-Dh
	for avt@ietf.org; Thu, 26 Jul 2007 16:54:17 -0400
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEALh-0007vS-0D
	for avt@ietf.org; Thu, 26 Jul 2007 16:54:17 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 26 Jul 2007 16:54:16 -0400
To: "Alan Clark" <alan.d.clark@telchemy.com>
Subject: Re: [AVT] Suggestion for how to handle
	derived/computedmetricindraft-avt-rtcpxr-*
References: <E1IE9V8-0006sW-Vd@megatron.ietf.org>
From: Randell Jesup <rjesup@wgate.com>
Date: Thu, 26 Jul 2007 16:54:14 -0400
In-Reply-To: <E1IE9V8-0006sW-Vd@megatron.ietf.org> (Alan Clark's message of
	"Thu, 26 Jul 2007 15:58:44 -0400")
Message-ID: <ybuodhyx4w9.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 26 Jul 2007 20:54:16.0647 (UTC)
	FILETIME=[213D8570:01C7CFC7]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: "'Even, Roni'" <roni.even@polycom.co.il>, 'David R Oran' <oran@cisco.com>,
	'AVT WG' <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

"Alan Clark" <alan.d.clark@telchemy.com> writes:
>The approach used for voice quality is fairly straightforward.  There are
>several parameters that are defined on a codec specific basis - notably Ie
>and Bpl, where Ie identifies the quality degradation due to the encoder and
>Bpl the robustness of the PLC algorithm against packet loss/ discard.  The
>endpoint incorporates a small table of these values for each voice codec
>that it supports.  Based on the codec selected for the call - the
>appropriate parameters are used.  Some other parameters, for example signal
>level, noise level, echo, delay, are less codec dependant.  A good source of
>information on how to do this using G.107 is ITU-T Recommendation G.799.1,
>which is a VoIP trunking gateway standard that incorporates a clear
>definition of how to compute the R factors and MOS scores required by RTCP
>XR.

I read G.799.1, and I saw no reference on how to calculate R or MOS.  Even
if they're elsewhere or in an appendix I missed, those may not (properly)
handle things like adaptive jitter buffers (G.799.1 mentions jitter buffers
briefly, but implies the delay must be chosen according to the goals of
the network - implying a fixed jitter buffer).  Given all the ways an
adaptive jitter buffer can deal with lengthening and shrinking the buffer,
I don't think any objective algorithm is going to do a good job of
measuring the effect of that operation, certainly not from outside the
jitter buffer/codec code.

Roni's point was that UA developers generally get black-box codecs to play
with.  They generally know about packet loss, jitter (going into the jitter
buffer), codec, etc , but PLC may well be hidden from them.  Also, a loss
of a packet when someone is listening (i.e. silence) has far less effect
than a loss at the start of a word (witness the Neil Armstrong moon
landing, sort of), and the UA developer probably doesn't know if the
packets on either side of the loss indicate that there was talking or not.

This is doubly the case for video.

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


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



From avt-bounces@ietf.org Thu Jul 26 19:00:44 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IECK0-0000cg-M0; Thu, 26 Jul 2007 19:00:40 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IECJz-0000ca-PX
	for avt@ietf.org; Thu, 26 Jul 2007 19:00:39 -0400
Received: from mx.cbeyond.com ([66.180.96.58])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IECJz-0001u0-6q
	for avt@ietf.org; Thu, 26 Jul 2007 19:00:39 -0400
Received: from [72.110.34.183] (port=3494 helo=TELCHADCPC)
	by mx.cbeyond.com with esmtpa (Exim 4.62)
	(envelope-from <alan.d.clark@telchemy.com>)
	id 1IECOh-0006k8-Q7; Thu, 26 Jul 2007 19:05:32 -0400
From: "Alan Clark" <alan.d.clark@telchemy.com>
To: "'Randell Jesup'" <rjesup@wgate.com>
Subject: RE: [AVT] Suggestion for how to
	handlederived/computedmetricindraft-avt-rtcpxr-*
Date: Thu, 26 Jul 2007 18:59:23 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcfPxyUG+bEGnALqQeOou0mYLhwDfAADcdsg
In-Reply-To: <ybuodhyx4w9.fsf@jesup.eng.wgate.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: "'Even, Roni'" <roni.even@polycom.co.il>, 'David R Oran' <oran@cisco.com>,
	'AVT WG' <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org
Message-Id: <E1IECK0-0000cg-M0@megatron.ietf.org>

>I read G.799.1, and I saw no reference on how to calculate R or MOS.  Even
if they're elsewhere or in an appendix I missed, 

You should look again - Appendix IV to G.799.1 (2004) is entitled "Mapping
of E Model (G.107) Parameters from RFC3611 Metrics". 

>those may not (properly) handle things like adaptive jitter buffers
(G.799.1 mentions jitter buffers briefly, but implies the delay must be
chosen according to the goals of the network - implying a fixed jitter
buffer).  Given all the ways an adaptive jitter buffer can deal with
lengthening and shrinking the buffer, I don't think any objective algorithm
is going to do a good job of measuring the effect of that operation,
certainly not from outside the jitter buffer/codec code.

Actually - I don't quite agree with you.  A jitter buffer essentially
replaces jitter with additional packet loss and delay.  The combined effects
of network packet loss and packets discarded by the jitter buffer due to
late arrival lead to the same result.  The added delay due to the jitter
buffer increases overall delay as seen by the user, however this effect is
generally perceived over a longer time period due to conversational
interaction problems (unless of course there is a high level of echo on the
call)

> Roni's point was that UA developers generally get black-box codecs to play
with.  They generally know about packet loss, jitter (going into the jitter
buffer), codec, etc , but PLC may well be hidden from them.  

This functionality could of course be implemented by the codec.  In
addition, many commercial codecs have APIs that allow metrics to be
retrieved - in some cases a fairly prolific set of metrics.  This does
typically include information related to both packet processing (i.e. loss,
discard, jitter buffer depth) and signal processing (signal levels, noise
levels, echo levels).

> Also, a loss of a packet when someone is listening (i.e. silence) has far
less effect than a loss at the start of a word (witness the Neil Armstrong
moon landing, sort of), and the UA developer probably doesn't know if the
packets on either side of the loss indicate that there was talking or not.

Several answers to this one!!

(i) Objective quality measurement generally does not take into account
emotional or semantic content, but generally tries to be robust over a wide
range of types of content (e.g. testing using content in multiple
languages).  A good analogy was explained to me by a subjective test expert
from a major US service provider - apparently they used to conduct state by
state phone surveys of subscribers to fulfil FCC reporting requirements.
One survey indicated that the (subjective) quality of service in that state
had dropped significantly, which caused considerable concern to senior
management; they found out however that the unemployment rate in the state
had just increased significantly - you can imagine if someone had just lost
their job and the phone company called to say "how happy are you with our
service" that the response may be less than complementary!!

(ii) You can take into account whether packet loss affects silence or speech
however from a service quality perspective this is not necessarily good.  If
there is an apparent dip in service quality at some point as losses (for
some strange reason) are tending to impact talkspurts more than silence then
the service provider may view this as the metric describing service quality
dropping when the service they are delivering is essentially unchanged.

In some senses, a reported MOS score is not a prediction of what this
specific user would say about this specific call but a measure of the
"service quality" of this call expressed in terms of MOS.  The reason for
doing this is that service providers understand what MOS is, it is providing
a language to describe service quality in terms that relate to the user
experience.  

Regards

Alan




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



From avt-bounces@ietf.org Thu Jul 26 20:58:53 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEEA7-0002BD-0B; Thu, 26 Jul 2007 20:58:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEEA5-0002B7-Sd
	for avt@ietf.org; Thu, 26 Jul 2007 20:58:33 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEEA4-000569-EJ
	for avt@ietf.org; Thu, 26 Jul 2007 20:58:33 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	C48A22058A; Fri, 27 Jul 2007 02:58:31 +0200 (CEST)
X-AuditID: c1b4fb3c-aee7cbb0000007e1-38-46a943370523
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	9CBA02045F; Fri, 27 Jul 2007 02:58:31 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 27 Jul 2007 02:58:31 +0200
Received: from [138.85.15.32] ([138.85.15.32]) by esealmw126.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 27 Jul 2007 02:58:30 +0200
Message-ID: <46A94335.1090104@ericsson.com>
Date: Fri, 27 Jul 2007 02:58:29 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: "Even, Roni" <roni.even@polycom.co.il>
References: <144ED8561CE90C41A3E5908EDECE315C04C236A6@IsrExch01.israel.polycom.com>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C04C236A6@IsrExch01.israel.polycom.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Jul 2007 00:58:30.0766 (UTC)
	FILETIME=[3FC6A0E0:01C7CFE9]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: bo.burman@ericsson.com, stewe@stewe.org, avt@ietf.org
Subject: [AVT] Re: Review draft-ietf-avt-avpf-ccm-07
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi Roni,

Please see inline.

Even, Roni skrev:
>>  > 2. In 4.2.1.2 " If the media sender concludes that it can increase the
> 
> */ [RE:] I think a clarification will make sense. /*
> 

Okay, I will include the following:

This should be done also for point-to-point sessions, as it not 
guaranteed that a participant can determine correctly if the sources are 
present in a single node and co-ordinated.


Is that okay? I only use should as it is strictly not needed if you are 
convinced that you can correctly determine that the back-off is not needed.



>>   
> 
> */ [RE:] I am still not sure I understand. Example the offer includes 
> tmmbr, tstr and fir. The answer responds with tstr only. /*
> 
> */ Does it mean that the answerer may send tmmbr, tstr and fir but the 
> offerer can only send tstr. /*
> 
> */ Also if the above is right it will mean the answerer sending tmmbr 
> will be able to process the response. /*
> 

Okay, I think there might be missing some word in there that these are 
symmetric and both side need to announce support for it to be possible 
to use it. These parameter does not make sense as declarative ones.

Now the complete sectiond reads:

7.2. Offer-Answer

The Offer/Answer [RFC3264] implications for codec control protocol 
feedback messages are similar to those described in [RFC4585].  The 
offerer MAY indicate the capability to support selected codec commands 
and indications.  The answerer MUST remove all ccm parameters 
corresponding to the CCM messages that it does not support or does not 
desire to be used in this particular media session.  The answerer MUST 
NOT add new ccm parameters in addition to what has been offered.  The 
answer is binding for the media session and both offerer and answerer 
MUST only use feedback messages that both sides have explicitely 
indicated in the messages.  In others words only the joint subset of CCM 
parameters from the offer and answer may be used.

Note, that including a CCM parameter in an offer or answer indicates 
that the agent (offerer or answerer) is at least capable of receiving 
the corresponding CCM message(s) and act upon them. In cases when the 
reception of a negotiated CCM messages mandates the agent to respond 
with another CCM message, it also must have that capability. Although 
not mandated to initiate CCM messages of any negotiated type it is 
generally expected that the agent will initiate CCM messages when suitable.

The session maximum packet rate parameter part of the TMMBR indication 
is declarative and everyone SHALL use the highest value indicated in a 
response.  If the session maximum packet rate parameter is not present 
in an offer it SHALL NOT be included by the answerer.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
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 Jul 26 22:08:06 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEFFB-0003oG-Bk; Thu, 26 Jul 2007 22:07:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEFF9-0003kH-Ou
	for avt@ietf.org; Thu, 26 Jul 2007 22:07:51 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEFF8-0006Kt-Am
	for avt@ietf.org; Thu, 26 Jul 2007 22:07:51 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	97C30200ED for <avt@ietf.org>; Fri, 27 Jul 2007 04:07:49 +0200 (CEST)
X-AuditID: c1b4fb3e-b1837bb0000007e1-3f-46a953752965
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	7749C20081 for <avt@ietf.org>; Fri, 27 Jul 2007 04:07:49 +0200 (CEST)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 27 Jul 2007 04:07:48 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 27 Jul 2007 04:07:47 +0200
Message-ID: <026F8EEDAD2C4342A993203088C1FC05055B9B35@esealmw109.eemea.ericsson.se>
In-Reply-To: <E1IECK1-0000cw-AS@megatron.ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Suggestion for how to handle
	derived/computedmetricindraft-avt-rtcpxr-*
Thread-Index: AcfP2NlfMo8Uc39QTrWPd7UcRMspowAF0jAg
References: <E1IECK1-0000cw-AS@megatron.ietf.org>
From: "Ingemar Johansson S (LU/EAB)" <ingemar.s.johansson@ericsson.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 27 Jul 2007 02:07:48.0820 (UTC)
	FILETIME=[EE2B5140:01C7CFF2]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Subject: [AVT] RE: Suggestion for how to handle
	derived/computedmetricindraft-avt-rtcpxr-*
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi

Coming from the area to speech and audio compression I can only second =
the opinion that you really must specify what algrithm you are using. =
Lots of work has been done to try to pair subjective quality =
measurements against objective measurements and the results are not =
always straightforward. One typical problem is impact of longer packet =
loss where the models and what people actually perceive differs.

Another big problem is that I cannot see how you account for =
jitterbuffer adaptation in this case, especially if you use adaptive =
jitterbuffering. My fear is that you only get to a point where you =
compare apples and oranges. But I wont argue more about the applications =
and the reliability.=20

Besides all this I find it a bit too static to specify binary RTCP =
report blocks for every kind of computed metric that one can come up =
with. A better solution would be some kind of an XML structure that =
allows for more dynamics. I know it is probably/maybe not doable for =
bandwidth reasons but extensibility would be alot easier then.=20

Why use RTCP at all for this ?, I sort of get the feeling that these are =
reports that are sent by the clients when he hangs up and the clients =
gather up all the statistics.

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

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



From avt-bounces@ietf.org Thu Jul 26 23:16:30 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEGJJ-0005ST-Rk; Thu, 26 Jul 2007 23:16:13 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEGJH-0005SI-Tz
	for avt@ietf.org; Thu, 26 Jul 2007 23:16:11 -0400
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEGJH-0007SY-5U
	for avt@ietf.org; Thu, 26 Jul 2007 23:16:11 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 26 Jul 2007 23:16:10 -0400
To: "Alan Clark" <alan.d.clark@telchemy.com>
Subject: Re: [AVT] Suggestion for how to
	handlederived/computedmetricindraft-avt-rtcpxr-*
References: <E1IECK1-0000cg-0x@megatron.ietf.org>
From: Randell Jesup <rjesup@wgate.com>
Date: Thu, 26 Jul 2007 23:16:09 -0400
In-Reply-To: <E1IECK1-0000cg-0x@megatron.ietf.org> (Alan Clark's message of
	"Thu, 26 Jul 2007 18:59:23 -0400")
Message-ID: <ybuhcnqv8na.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 27 Jul 2007 03:16:10.0709 (UTC)
	FILETIME=[7B15E850:01C7CFFC]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Cc: "'Even, Roni'" <roni.even@polycom.co.il>, 'David R Oran' <oran@cisco.com>,
	'AVT WG' <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

"Alan Clark" <alan.d.clark@telchemy.com> writes:
>>I read G.799.1, and I saw no reference on how to calculate R or MOS.  Even
>if they're elsewhere or in an appendix I missed, 
>
>You should look again - Appendix IV to G.799.1 (2004) is entitled "Mapping
>of E Model (G.107) Parameters from RFC3611 Metrics". 

Ah.  The .doc I found online didn't have that appendix.

>>those may not (properly) handle things like adaptive jitter buffers
>>(G.799.1 mentions jitter buffers briefly, but implies the delay must be
>>chosen according to the goals of the network - implying a fixed jitter
>>buffer).  Given all the ways an adaptive jitter buffer can deal with
>>lengthening and shrinking the buffer, I don't think any objective algorithm
>>is going to do a good job of measuring the effect of that operation,
>>certainly not from outside the jitter buffer/codec code.
>
>Actually - I don't quite agree with you.  A jitter buffer essentially
>replaces jitter with additional packet loss and delay.  The combined effects
>of network packet loss and packets discarded by the jitter buffer due to
>late arrival lead to the same result.  The added delay due to the jitter
>buffer increases overall delay as seen by the user, however this effect is
>generally perceived over a longer time period due to conversational
>interaction problems (unless of course there is a high level of echo on the
>call)

Sorry, that's wrong (IMHO), depending on the jitter buffer.  An adaptive
jitter buffer has to in some manner speed up and slow down.  This could be
by throwing away or adding entire frames (which would look mostly like
packet loss or unexpected repetition), or by much fancier mechanisms that
expand and contract time during speech by less than a frame (which would be
very unlike packet loss or repetition, and very tricky to compute an MOS
for, unless you have a way to do it from *only* the reconstructed sample
stream).  (Note: I haven't read that G.799.1 appendix.)

Your comments would apply to a static jitter buffer, however.

>> Roni's point was that UA developers generally get black-box codecs to play
>>with.  They generally know about packet loss, jitter (going into the jitter
>>buffer), codec, etc , but PLC may well be hidden from them.  
>
>This functionality could of course be implemented by the codec.  In
>addition, many commercial codecs have APIs that allow metrics to be
>retrieved - in some cases a fairly prolific set of metrics.  This does
>typically include information related to both packet processing (i.e. loss,
>discard, jitter buffer depth) and signal processing (signal levels, noise
>levels, echo levels).

Sure, some do - and more don't, from what I've seen.  The ones I've seen
have no metrics, or they have just enough for plain RTCP SR/RR.

>> Also, a loss of a packet when someone is listening (i.e. silence) has far
>>less effect than a loss at the start of a word (witness the Neil Armstrong
>>moon landing, sort of), and the UA developer probably doesn't know if the
>>packets on either side of the loss indicate that there was talking or not.
>
>Several answers to this one!!
>
>(i) Objective quality measurement generally does not take into account
>emotional or semantic content, but generally tries to be robust over a wide
>range of types of content (e.g. testing using content in multiple
>languages).  A good analogy was explained to me by a subjective test expert
>from a major US service provider - apparently they used to conduct state by
>state phone surveys of subscribers to fulfil FCC reporting requirements.
>One survey indicated that the (subjective) quality of service in that state
>had dropped significantly, which caused considerable concern to senior
>management; they found out however that the unemployment rate in the state
>had just increased significantly - you can imagine if someone had just lost
>their job and the phone company called to say "how happy are you with our
>service" that the response may be less than complementary!!

Ok - though my point was that automated MOS scoring could/should take
into account the content of the packets lost, at least to the level of
determining if there was (likely) any speech coded within the lost packet.
(look at the packets on either side of the loss - if they have significant
speech-like qualities, then this packet almost certainly coded speech too).
If it likely coded silence, it has much less impact on subjective MOS
and so objective MOS should try to model that (when it can).

>(ii) You can take into account whether packet loss affects silence or speech
>however from a service quality perspective this is not necessarily good.  If
>there is an apparent dip in service quality at some point as losses (for
>some strange reason) are tending to impact talkspurts more than silence then
>the service provider may view this as the metric describing service quality
>dropping when the service they are delivering is essentially unchanged.
>
>In some senses, a reported MOS score is not a prediction of what this
>specific user would say about this specific call but a measure of the
>"service quality" of this call expressed in terms of MOS.  The reason for
>doing this is that service providers understand what MOS is, it is providing
>a language to describe service quality in terms that relate to the user
>experience.  

No, MOS ("real MOS") is what specific user(s) would rate the call as.
"reported MOS" is something different - it's NOT "real" MOS.  It may be an
approximation of real MOS, but if so then it could be calculated in all
sorts of different ways.  It sounds like you're looking at it as something
related to but not the same as real MOS; something that is more useful to a
service provider than "real" MOS is, and therefore you (or whomever) would
prefer not to make the "reported MOS" any closer to "real MOS" as judged by
a human.  Which is fine, but it means we should move away from calling it
MOS.  If I want to know how the listener would rate that exact call, then I
want something as close to "real MOS" as possible.

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


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



From avt-bounces@ietf.org Fri Jul 27 08:00:51 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEOUh-0002kk-Mg; Fri, 27 Jul 2007 08:00:31 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEOUf-0002gM-OI
	for avt@ietf.org; Fri, 27 Jul 2007 08:00:29 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEOUf-0002Ty-9r
	for avt@ietf.org; Fri, 27 Jul 2007 08:00:29 -0400
Received: from vpn10.dcs.gla.ac.uk ([130.209.254.10]:61605)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1IEOUe-0006PC-3x; Fri, 27 Jul 2007 13:00:28 +0100
In-Reply-To: <026F8EEDAD2C4342A993203088C1FC05055B9B35@esealmw109.eemea.ericsson.se>
References: <E1IECK1-0000cw-AS@megatron.ietf.org>
	<026F8EEDAD2C4342A993203088C1FC05055B9B35@esealmw109.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <BCE5D36D-6CC7-4656-ADAA-C874666D9833@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] RE: Suggestion for how to handle
	derived/computedmetricindraft-avt-rtcpxr-*
Date: Fri, 27 Jul 2007 07:00:31 -0500
To: Ingemar Johansson S (LU/EAB) <ingemar.s.johansson@ericsson.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi,

On 26 Jul 2007, at 21:07, Ingemar Johansson S (LU/EAB) wrote:
> Coming from the area to speech and audio compression I can only  
> second the opinion that you really must specify what algrithm you  
> are using. Lots of work has been done to try to pair subjective  
> quality measurements against objective measurements and the results  
> are not always straightforward. One typical problem is impact of  
> longer packet loss where the models and what people actually  
> perceive differs.
>
> Another big problem is that I cannot see how you account for  
> jitterbuffer adaptation in this case, especially if you use  
> adaptive jitterbuffering. My fear is that you only get to a point  
> where you compare apples and oranges. But I wont argue more about  
> the applications and the reliability.
>
> Besides all this I find it a bit too static to specify binary RTCP  
> report blocks for every kind of computed metric that one can come  
> up with. A better solution would be some kind of an XML structure  
> that allows for more dynamics. I know it is probably/maybe not  
> doable for bandwidth reasons but extensibility would be alot easier  
> then.

I'm not sure we want this to be too easily extensible. A limited set  
of well defined metrics probably makes analysis easier than a very  
extensible and flexible system, filled with "metric of the day"  
parameters.

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



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



From avt-bounces@ietf.org Fri Jul 27 10:30:00 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEQpC-0005YK-EY; Fri, 27 Jul 2007 10:29:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEQpA-0005YE-UY
	for avt@ietf.org; Fri, 27 Jul 2007 10:29:48 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEQp9-0005Tj-FX
	for avt@ietf.org; Fri, 27 Jul 2007 10:29:48 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	9E51B21181; Fri, 27 Jul 2007 16:29:46 +0200 (CEST)
X-AuditID: c1b4fb3e-ae831bb0000007e1-c1-46aa015a1c1e
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	7FC7B21160; Fri, 27 Jul 2007 16:29:46 +0200 (CEST)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 27 Jul 2007 16:29:46 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] RE: Suggestion for how to handle
	derived/computedmetricindraft-avt-rtcpxr-*
Date: Fri, 27 Jul 2007 16:29:45 +0200
Message-ID: <026F8EEDAD2C4342A993203088C1FC05055B9C6C@esealmw109.eemea.ericsson.se>
In-Reply-To: <BCE5D36D-6CC7-4656-ADAA-C874666D9833@csperkins.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] RE: Suggestion for how to handle
	derived/computedmetricindraft-avt-rtcpxr-*
Thread-Index: AcfQRbpSaZ46EC6cTZCqFkpW9bjSTAAEsu8g
References: <E1IECK1-0000cw-AS@megatron.ietf.org>
	<026F8EEDAD2C4342A993203088C1FC05055B9B35@esealmw109.eemea.ericsson.se>
	<BCE5D36D-6CC7-4656-ADAA-C874666D9833@csperkins.org>
From: "Ingemar Johansson S (LU/EAB)" <ingemar.s.johansson@ericsson.com>
To: "Colin Perkins" <csp@csperkins.org>
X-OriginalArrivalTime: 27 Jul 2007 14:29:46.0235 (UTC)
	FILETIME=[949DC4B0:01C7D05A]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.4 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi

Understand the "metric of the day" concern but I don't believe that this
will happen as the addition of metrics will need to be standardized
anyway. It is however possible that this standardization is done in
other fora such as TISPAN or 3GPP as I believe that detailed speech
quality metrics is not IETF's cup of tea. What IETF can do is to specify
a framework for this that is expected to work well in the packet
switched environment.

Just to second my "why use RTCP".=20
RTCP is, as I understand it, to a great extent a means to send signaling
and metrics end to end, possibly modified by a middle box. These more
elaborate metrics are in my opinion mostly of value for an operator but
of lesser value for the user.=20
Therefore it is something that the client can transmit to the ISP or
operator in a number of different (more relaible) ways after the call is
completed or during a call if needed. The need to make the whole thing a
binary bit field is then also less important.

Just my 0.05 EUR

Regards
Ingemar

=20

> -----Original Message-----
> From: Colin Perkins [mailto:csp@csperkins.org]=20
> Sent: den 27 juli 2007 07:01
> To: Ingemar Johansson S (LU/EAB)
> Cc: avt@ietf.org
> Subject: Re: [AVT] RE: Suggestion for how to handle=20
> derived/computedmetricindraft-avt-rtcpxr-*
>=20
> Hi,
>=20
> On 26 Jul 2007, at 21:07, Ingemar Johansson S (LU/EAB) wrote:
> > Coming from the area to speech and audio compression I can=20
> only second=20
> > the opinion that you really must specify what algrithm you=20
> are using.=20
> > Lots of work has been done to try to pair subjective quality=20
> > measurements against objective measurements and the results are not=20
> > always straightforward. One typical problem is impact of=20
> longer packet=20
> > loss where the models and what people actually perceive differs.
> >
> > Another big problem is that I cannot see how you account for=20
> > jitterbuffer adaptation in this case, especially if you use=20
> adaptive=20
> > jitterbuffering. My fear is that you only get to a point where you=20
> > compare apples and oranges. But I wont argue more about the=20
> > applications and the reliability.
> >
> > Besides all this I find it a bit too static to specify binary RTCP=20
> > report blocks for every kind of computed metric that one=20
> can come up=20
> > with. A better solution would be some kind of an XML structure that=20
> > allows for more dynamics. I know it is probably/maybe not=20
> doable for=20
> > bandwidth reasons but extensibility would be alot easier then.
>=20
> I'm not sure we want this to be too easily extensible. A=20
> limited set of well defined metrics probably makes analysis=20
> easier than a very extensible and flexible system, filled=20
> with "metric of the day" =20
> parameters.
>=20
> --=20
> Colin Perkins
> http://csperkins.org/
>=20
>=20
>=20

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



From avt-bounces@ietf.org Fri Jul 27 12:25:21 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEScu-00019O-LO; Fri, 27 Jul 2007 12:25:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IESct-00019H-7t
	for avt@ietf.org; Fri, 27 Jul 2007 12:25:15 -0400
Received: from cluster-f.mailcontrol.com ([85.119.2.190])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEScr-0008Ji-Qt
	for avt@ietf.org; Fri, 27 Jul 2007 12:25:15 -0400
Received: from exsmtp01.nasstar-t1.net (exsmtp01.nasstar-t1.net [89.28.233.12])
	by rly34f.srv.mailcontrol.com (MailControl) with ESMTP id
	l6RGP7nH014980 for <avt@ietf.org>; Fri, 27 Jul 2007 17:25:12 +0100
Received: from ExBE03.nasstar-t1.net ([10.2.10.102]) by
	exsmtp01.nasstar-t1.net with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 27 Jul 2007 17:25:22 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 27 Jul 2007 17:25:02 +0100
Message-ID: <165288C2C3E29449AFDE022DD10CC4710635507B@ExBE03.nasstar-t1.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: SRTP help - how to generate a master key (AES-CM)?
Thread-Index: AcfQReZsNTUbDzHBSnikH7Cq7qwVfwAIou0g
From: "Attila Sipos" <attila.sipos@vegastream.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 27 Jul 2007 16:25:22.0629 (UTC)
	FILETIME=[BB077F50:01C7D06A]
X-Scanned-By: MailControl A-07-08-00 (www.mailcontrol.com) on 10.70.0.144
X-Spam-Score: -0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: [AVT] SRTP help - how to generate a master key (AES-CM)?
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org


Hi,
>From what I can see, when generating a keys,
you need a master key and a salt key.

I can see that the salt key can be any value but
it seems that the master key needs to be generated
somehow - it can't just be random.

Can anyone tell me how to generate this when using AES-CM?
Or point me to some open-source code to do it?

Regards,

Attila



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



From avt-bounces@ietf.org Fri Jul 27 14:42:18 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEUlL-0003zl-Qm; Fri, 27 Jul 2007 14:42:07 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEUlL-0003zg-4V
	for avt@ietf.org; Fri, 27 Jul 2007 14:42:07 -0400
Received: from mail128.messagelabs.com ([216.82.250.131])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IEUlK-00043C-Nf
	for avt@ietf.org; Fri, 27 Jul 2007 14:42:07 -0400
X-VirusChecked: Checked
X-Env-Sender: Qiaobing.Xie@motorola.com
X-Msg-Ref: server-8.tower-128.messagelabs.com!1185561725!14718497!1
X-StarScan-Version: 5.5.12.11; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 26876 invoked from network); 27 Jul 2007 18:42:05 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-8.tower-128.messagelabs.com with SMTP;
	27 Jul 2007 18:42:05 -0000
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l6RIg5Lk003589
	for <avt@ietf.org>; Fri, 27 Jul 2007 11:42:05 -0700 (MST)
Received: from il06vts02.mot.com (il06vts02.mot.com [129.188.137.142])
	by il06exr01.mot.com (8.13.5/Vontu) with SMTP id l6RIg4FM029504
	for <avt@ietf.org>; Fri, 27 Jul 2007 13:42:04 -0500 (CDT)
Received: from [192.168.15.2] (mvp-10-31-8-50.am.mot.com [10.31.8.50])
	by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id l6RIg3EX029474;
	Fri, 27 Jul 2007 13:42:03 -0500 (CDT)
Message-ID: <46AA3C7B.2090003@motorola.com>
Date: Fri, 27 Jul 2007 13:42:03 -0500
From: Qiaobing Xie <Qiaobing.Xie@motorola.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: AVT List <avt@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Vontu: Pass
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Subject: [AVT] review and WI request:
	draft-xie-avt-forward-shifted-red-01.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

All,

I'd appreciate for your review and comments on 
draft-xie-avt-forward-shifted-red-01.txt. It has been out there for 
several months now. List comments I received from -00 have been 
incorporated in this -01 version already.

Chairs:

I'd like to request this draft being made a working group item.

regards,
-Qiaobing Xie

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



From avt-bounces@ietf.org Sun Jul 29 22:02:55 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFKao-00086d-Pl; Sun, 29 Jul 2007 22:02:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFKan-00086K-6z
	for avt@ietf.org; Sun, 29 Jul 2007 22:02:41 -0400
Received: from mout.perfora.net ([74.208.4.194])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFKam-0003rL-GY
	for avt@ietf.org; Sun, 29 Jul 2007 22:02:41 -0400
Received: from [65.122.14.237] (helo=TBT-Laptop.newtbt.com)
	by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis),
	id 0MKp8S-1IFKak0Stn-0005t6; Sun, 29 Jul 2007 22:02:39 -0400
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sun, 29 Jul 2007 19:02:03 -0700
To: AVT WG <avt@ietf.org>
From: Michael A Dolan <md.1@newtbt.com>
Subject: Re: [AVT] draft-ietf-avt-hdrext-12
In-Reply-To: <46A8F01A.8040809@ericsson.com>
References: <0MKp8S-1IBfib2mC2-0005q2@mrelay.perfora.net>
	<p06240803c2cd4d282cd9@[17.202.35.52]>
	<0MKpCa-1IDqsy0MRm-0006V5@mrelay.perfora.net>
	<46A8F01A.8040809@ericsson.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <0MKp8S-1IFKak0Stn-0005t6@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX18IevKcl31YPjgYMR8OxJzKx5DsSU1b/K3yMyf
	Kg/JsRBAgN4nCQZspK5NOUqIOd5sr3F6mwe/4pfbdb+s7mIoOv
	bxGJ6azGWHRrSw3J4eecw==
X-Spam-Score: -0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Magnus-

We all agree the preferable choice is option (a), but how do we get 
there?  The management of the RTP header extensions is not ideal due 
to circumstances now behind us.  I don't see how we can make existing 
conformant practice (nearly anything) non-conformant upon publication 
of this ID.  At best, all a STDs track publication can say is 
"SHOULD" at this point in my personal view.  It is not likely to be 
as simple as managing the "defined by profile" field as an enumerated 
field by IANA or explicit RFC publication as some have suggested, 
since 3350 gave no indication at all how to manage this field or even 
if it was a constant (which some presume incorrectly).

IETF AVT WG is an open process. All other existing current extension 
syntax authors are invited to try and make the effort to merge them 
into a single compatible standard design as part of the 
process.  Although I wish I was aware of this other design sooner in 
the process, I tried to craft the proposal in this thread so that 
both could exist concurrently in a well-structured manner.  I would 
welcome other uses to come forward so we could craft a single overall 
mechanism.  We all *know* there are other uses (I found a new one 
last week), but the burden is on those authors to come forward and 
make the effort. Lacking other contributions, the WG should make an 
effort to make the published ones (minimally these two) work as best we can.

I am still trying to avoid an evaluation ("bake-off") of the two 
designs since it will alienate one of them after the fact, but....you 
cite "tradeoff" and "proprietary" evaluation criteria to support the 
4/4-bit design alone in pursuit of option (a).  So if the path 
forward is to have a technical evaluation of tradeoffs and relative 
"propriety" to reach option (a), then I would like to understand your 
conclusions better, especially the one about one being more 
proprietary than another.

But before we enter into a "bake-off", it is still my view that the 
best we can accomplish under the circumstances of how 3350 left 
things is to document what practices we know about (via authors 
willing to bring them forward) in a clearly discriminating manner, 
concurrent with a recommendation for all new designs.  Please note 
that I did not try to assert that the other design in this thread as 
the preferred one - the contrary in fact, deferring to the existing 
ID's proposal for future designs.

Regards,

         Mike

At 12:03 PM 7/26/2007, Magnus Westerlund wrote:
>Michael A Dolan skrev:
>>Dave and all-
>>I was hoping to avoid a debate on relative deployment and the value 
>>of 4 bits versus 8 bits by proposing option (c) below (which is 
>>what I tried to articulate in last week's post).  In a perfect 
>>world, we would drive to (a), but I don't see how to get there in 
>>any reasonable timeline.
>>Mean-time the world moves on making more of these deployments, and 
>>worse, more non-conformant variants we don't even know about....
>>Can everyone live with option (c)?
>
>Preferably no, this is a core extension that we are likely to see 
>quite a lot of use in the future. I think 4+4 has a good tradeoff. I 
>would like to go with a) because of this to avoid confusing things. 
>If there are "proprieatery" deployment as it is of 8+8 that is not 
>different from other "proprieatery" extensions in this field.
>
>>>Choices:
>>>
>>>a) go with just 4+4 or just 8+8, and drop one.  I am aware of 
>>>implementations of both, so this isn't ideal.
>>>
>>>b) in the same document, require support for both.
>>>
>>>c) in the same document, require support for one, and recommend 
>>>support for the other.
>>>
>>>d) publish one separately, as an informational RFC.
>
>Cheers
>
>Magnus Westerlund
>
>IETF Transport Area Director & TSVWG Chair
>----------------------------------------------------------------------
>Multimedia Technologies, Ericsson Research EAB/TVM/M
>----------------------------------------------------------------------
>Ericsson AB                | Phone +46 8 4048287
>Torshamsgatan 23           | Fax   +46 8 7575550
>S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>----------------------------------------------------------------------


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



From avt-bounces@ietf.org Mon Jul 30 02:05:31 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFONg-00064M-Hv; Mon, 30 Jul 2007 02:05:24 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFONb-00064A-Vw; Mon, 30 Jul 2007 02:05:21 -0400
Received: from [202.99.23.227] (helo=people.com.cn)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1IFONb-00089c-0Q; Mon, 30 Jul 2007 02:05:19 -0400
Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id jm2a46ad890b; Mon, 30 Jul 2007 14:17:11 +0800
Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC
	2.9.5.8) with SMTP id jm6f46a773c1; Wed, 25 Jul 2007 20:00:09 +0800
Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC
	2.9.5.8) with SMTP id AISP action; Wed, 25 Jul 2007 20:00:07 +0800
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID3NL-0001xA-CJ; Mon, 23 Jul 2007 15:15:23 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID3N1-0000t6-6M; Mon, 23 Jul 2007 15:15:03 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1ID3N0-00073Z-Fu; Mon, 23 Jul 2007 15:15:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 30B4917606;
	Mon, 23 Jul 2007 19:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1ID3Mz-0005Oi-PL; Mon, 23 Jul 2007 15:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1ID3Mz-0005Oi-PL@stiedprstage1.ietf.org>
Date: Mon, 23 Jul 2007 15:15:01 -0400
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Archive: <http://www1.ietf.org/pipermail/i-d-announce>
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: i-d-announce-bounces@ietf.org
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: Internet-Drafts@ietf.org
X-Auto-Forward: jaglee@people.com.cn
 jag@kw.com.cn
X-Spam-Score: 3.2 (+++)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtcpxr-mpts-00.txt 
X-BeenThere: avt@ietf.org
Reply-To: internet-drafts@ietf.org
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--NextPart

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

	Title		: RTCP XR - MPEG Transport Metrics Report Block
	Author(s)	: A. Clark
	Filename	: draft-ietf-avt-rtcpxr-mpts-00.txt
	Pages		: 
	Date		: 2007-7-23
	

   This document defines an extension to the RTCP XR extended report
   packet type blocks to support the monitoring of video over IP 
   and the associated audio streams, if present, for video encapsulated
   in MPEG Transport carried over RTP.
   [Note: this draft contains the MPEG transport metrics that were
   formerly in the draft-ietf-avt-rtcpxr-video-00.txt draft, which has
   now been divided into four drafts]


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcpxr-mpts-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-rtcpxr-mpts-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-rtcpxr-mpts-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

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

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

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

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

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

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


--OtherAccess--

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

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

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

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

--NextPart--






From avt-bounces@ietf.org Mon Jul 30 02:07:15 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFOPQ-0006l0-K1; Mon, 30 Jul 2007 02:07:12 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFOPO-0006ko-D5; Mon, 30 Jul 2007 02:07:10 -0400
Received: from [202.99.23.227] (helo=people.com.cn)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1IFOPN-0008Bp-Dy; Mon, 30 Jul 2007 02:07:10 -0400
Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id jmd346ad8c87; Mon, 30 Jul 2007 14:19:01 +0800
Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC
	2.9.5.8) with SMTP id jm9046a7933e; Thr, 26 Jul 2007 01:31:13 +0800
Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC
	2.9.5.8) with SMTP id AISP action; Thr, 26 Jul 2007 01:31:13 +0800
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDkS2-0002gb-NO; Wed, 25 Jul 2007 13:15:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDkRy-0002fv-PA; Wed, 25 Jul 2007 13:15:02 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IDkRy-0005Xo-Aj; Wed, 25 Jul 2007 13:15:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 0CEE826E85;
	Wed, 25 Jul 2007 17:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IDkRx-0008NY-Tw; Wed, 25 Jul 2007 13:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IDkRx-0008NY-Tw@stiedprstage1.ietf.org>
Date: Wed, 25 Jul 2007 13:15:01 -0400
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Archive: <http://www1.ietf.org/pipermail/i-d-announce>
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: i-d-announce-bounces@ietf.org
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: Internet-Drafts@ietf.org
X-Auto-Forward: jaglee@people.com.cn
 jag@kw.com.cn
X-Spam-Score: 2.8 (++)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-and-rtcp-mux-06.txt 
X-BeenThere: avt@ietf.org
Reply-To: internet-drafts@ietf.org
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

--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		: Multiplexing RTP Data and Control Packets on a Single Port
	Author(s)	: C. Perkins, M. Westerlund
	Filename	: draft-ietf-avt-rtp-and-rtcp-mux-06.txt
	Pages		: 15
	Date		: 2007-7-25
	
This memo discusses issues that arise when multiplexing RTP data
   packets and RTP control protocol (RTCP) packets on a single UDP port.
   It updates RFC 3550 to describe when such multiplexing is, and is
   not, appropriate, and explains how the Session Description Protocol
   (SDP) can be used to signal multiplexed sessions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-and-rtcp-mux-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-and-rtcp-mux-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-and-rtcp-mux-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: <2007-7-25120521.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-and-rtcp-mux-06.txt

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

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


--OtherAccess--

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

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

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

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

--NextPart--






From avt-bounces@ietf.org Mon Jul 30 04:11:57 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFQLs-0007oW-5U; Mon, 30 Jul 2007 04:11:40 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFPcp-0001rc-VN
	for avt@ietf.org; Mon, 30 Jul 2007 03:25:08 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFPcn-0001Y2-LR
	for avt@ietf.org; Mon, 30 Jul 2007 03:25:07 -0400
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:61621
	helo=[192.168.0.4])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1IFPck-0000W0-ID; Mon, 30 Jul 2007 08:25:03 +0100
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F21E8576-5002-4B3C-B64F-0542A51538DD@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Mon, 30 Jul 2007 08:25:00 +0100
To: AVT WG <avt@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dae47ebd0d959deee2d6f67621ddb2e3
X-Mailman-Approved-At: Mon, 30 Jul 2007 04:11:38 -0400
Cc: Roni Even <roni.even@polycom.co.il>, Tom Taylor <tom.taylor@rogers.com>
Subject: [AVT] Draft minutes from Chicago meeting
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Draft minutes from the Chicago AVT meetings are enclosed. Please send  
any comments or corrections to the chairs.

Colin






Audio/Video Transport (AVT) Working Group Minutes
=================================================

Reported by Colin Perkins

    The Audio/Video Transport working group met twice at the 69th IETF
    meeting (Chicago, 23-27 July 2007). Subjects under discussion  
included
    DTLS extensions for keying SRTP sessions, extended reception quality
    reports for RTCP, non-compound RTCP, RTP keep alives, source  
specific
    media attributes, and various RTP payload formats.  The meeting was
    chaired by Colin Perkins, Roni Even and Tom Taylor. The blue sheets
    were signed by 94 people in the first session, and 70 in the second
    session.


Introduction and Status Update

    The working group chairs introduced the meeting, and reviewed the  
status
    of the group. Two RFCs have been published since the last meeting  
(draft-
    ietf-avt-rtp-amr-bis-06.txt as RFC 4867, and draft-ietf-avt-hc- 
over-mpls-
    protocol-08.txt as RFC 4901). The RTP payload formats for EVRC-WB  
and
    Vorbis are in IESG review, as is the SAVPF profile, the drafts  
defining
    a general RTP header extension mechanism, and the draft on the  
ULP FEC
    scheme. The draft on RTP and RTCP multiplexing is in IETF last call.

    The Codec Control Messages and Topologies drafts have completed  
working
    group last call, with some comments being made. The chairs called  
for
    reviewers to ensure these specifications can be implemented, and are
    clearly written, before we request their publication as RFCs.


DTLS Extension to Establish Keys for SRTP

    draft-ietf-avt-dtls-srtp-00

    David McGrew presented the DTLS extension to establish keys for  
SRTP.
    This is based on draft-mcgrew-tls-srtp-02.txt, which has been  
discussed
    extensively in the RTPSEC BoF, and has been adopted as an AVT  
work item
    after the discussion at the 68th IETF. It protects point-to-point  
RTP
    sessions, using a DTLS handshake on the media path to establish  
keys,
    and it defines DTLS SRTP packet processing for RTP and RTCP.

    Recent changes include a clarification that only one DTLS  
handshake is
    needed in the symmetric RTP case, the elimination of a duplicate  
list of
    SRTP profiles, and the correction of various editorial nits.  
There are a
    number of open issues:

    Open issue #1 is whether the "TLS extractor" should be used  
instead of a
    purpose-built extension to TLS KDF. This would require rewriting  
section
    3.3 of the draft. Hannes Tschofenig queried the status of the  
extractor
    in the TLS working group, and Eric Rescorla replied that his  
impression
    (without speaking for the TLS working group chairs) was that it  
would
    become a TLS work item if there was interest. Hannes also asked  
if the
    extractor is general purpose, or limited to use with DTLS SRTP -  
it is
    general purpose. Discussion was moved to the mailing list.

    Open issue #2 is whether we need a symmetry breaking rule (see  
section
    3.6.2.1 of the draft) to define what should happen when a device  
that
    sent a clientHello receives a clientHello. This would also handle  
cases
    in which the signalling can't tell which device should act as  
client and
    which as server. Colin Perkins asked if you can't solve this by  
defining
    the SIP offerer as the server, and Eric Rescorla replied that he had
    thought so initially, but there are call flows where that doesn't  
work.
    Roni Even noted that there are MCU-related call flows that  
require this
    symmetry breaking, and Jonathan Rosenberg noted that ICE has a  
similar
    feature to address this problem.  Eric Rescorla asked if the  
symmetry
    breaking tag can be included in the SDP - no, it has to be in the  
media
    path because you can't do an updated offer until after the media  
begins
    to flow, unless you also do reliable provisional responses. Jonathan
    Rosenberg spoke clearly in favour of including symmetry breaking,  
and
    David McGrew agreed to work on this in the TLS working group.

    Open issue #3 is whether a single DTLS session should be used per  
SRTP
    session (appendix B of the draft). The advantages of this are lower
    computation and latency, and a better match for the SRTP policy  
model.
    The disadvantage is that it differs from standard TLS practice.  
Jonathan
    Rosenberg asked if this is just for RTP and RTCP flows of a  
single RTP
    session, or if it can also work across audio and video RTP sessions.
    Eric Rescorla replied that it could in theory work across RTP  
sessions,
    but isn't currently specified that way. David McGrew noted that  
this is
    currently just sharing the DTLS handshake between RTP and RTCP  
flows.
    Colin Perkins asked if if might be simpler to mandate  
multiplexing RTP
    and RTCP on the same port when DTLS is used? Eric Rescorla and  
Jonathan
    Rosenberg enthusiastically supported this, but Flemming Andreasen  
noted
    some quality of service issues with multiplexing, and suggested  
that the
    correct solution was to encourage multiplexing, avoiding the  
issues with
    using a single DTLS session for multiple flows, and to accept  
that two
    DTLS handshakes will be required when non-multiplexed flows are  
used.

    Jonathan Rosenberg raised the issue that ICE-TCP is currently  
specified
    to send DTLS over a TCP connection in parallel to STUN, and asked if
    this caused any problems? Eric Rescorla explained that there is  
no issue
    from the DTLS perspective, provided there is an underlying packet  
framing
    protocol used over the TCP connection (which is the case in ICE- 
TCP).

    Finally, Colin Perkins noted that while the draft is progressing  
well
    technically, it is difficult to read for someone who is not a DTLS
    security expert. He will provide comments to help improve the draft
    editorially, and he encouraged others to do the same.


Audio and Video Metrics Report Blocks

    draft-ietf-avt-rtcpxr-video-01
    draft-ietf-avt-rtcpxr-audio-00

    Alan Clark presented the RTCP XR audio and video metrics drafts. The
    previous RTCP XR video draft has been split into four parts  
following
    the discussion at the Prague IETF meeting; two parts were  
discussed in
    the meeting, the other two missed the deadline and will be available
    shortly.

    Alan explained that the RTCP XR video draft has aimed for  
consistency
    with ATIS IIF WT014 and DSL Forum WT135 definitions (both in final
    closure). It included an EPSNR metric defined using a packet-based
    estimation that is being evaluated by ATIS IIF group, and a MOS-V
    metric defined in ATIS IIF WT014, and zero reference algorithm due
    to be evaluated by VQEG over the coming months. The RTCP XR audio  
draft
    contains PEAQ - ITU BS.1387 and G.1070 metric, along with others  
being
    evaluation by VQEG.

    Steve Casner asked where the ATIS IIF and DSL forum expect their  
metrics
    to be used, and Alan replied that he's kept them informed, and  
this is
    one of the transports they expect to be used.

    Kaynam Hedayat reminded Alan that the consensus of the Prague  
meeting
    was that we agreed to report raw data, rather than processed  
metrics,
    but that the metrics defined here are processed metric, derived from
    the raw data. Roni Even noted that the group doesn't have the  
expertise
    to evaluate metrics, and suggested that the RTCP XR blocks should  
report
    metrics defined by other standards bodies, rather than defining  
any new
    metrics. Alan Clark noted that there are a number of ITU, and other,
    standards that exist in this area, but that these evolve, hence  
the need
    to include new(er) metrics in the RTCP XR reports.

    Dave Oran also remembered the agreement from the Prague meeting to
    transport raw metrics, rather than processed values derived from  
those
    raw metrics, noting that, e.g., if there's a standard for  
computing MOS
    the RTCP XR reports should transport the information that would  
allow a
    monitor to perform that computation, rather than transporting the  
pre-
    calculated MOS value. He justified this by noting that raw data  
is more
    stable in the long term, since recommended algorithms change.  
Alan Clark
    explained that he doesn't think this is possible, since only the end
    system has the information it needs to compute the metrics. Dave
    disagreed.

    There was considerable discussion on the issue, with Cullen  
Jennings,
    Joerg Ott, and Tom Taylor supporting the consensus from the Prague
    meeting to transport raw metrics, for similar reasons. Ravi Raviraj
    dissented, agreeing with Alan Clark that there is a need for both  
raw
    and processed metrics, and commenting that, provided the processed
    metrics are well defined, he doesn't see an issue with including  
them.
    Dave Oran concluded the discussion by noting that he doesn't see  
this
    argument coming to closure, and suggested that both raw and computed
    metrics be transported, but in separate report blocks, with computed
    metrics being defined only by explicit reference to dated standards
    produced by other standards bodies. The chairs agreed that this is a
    reasonable compromise, and emphasised the need for strict separation
    of raw and processed metrics, and clear, unambiguous, references to
    the standards defining the processed metrics.



Report Block for IPTV Metrics

    draft-venna-avt-rtcpxr-iptv-01

    Nagarjuna Venna presented the draft defining RTCP XR report  
blocks for
    IPTV metrics. He summarised the draft, noting that it relates to RTP
    streams as specified in RFC 2250, and contains sub-blocks for MPEG
    programme and elementary streams. Feedback was solicited, and it was
    asked if there was interest in taking this as a working group draft.

    Colin Perkins, as chair, asked if anyone in the group has read the
    draft? Cullen Jennings had, but had only trivial comments, but few
    others seemed to have read the draft. Accordingly, the chairs  
deferred
    on taking this as a working group item until there was more  
interest.

    Alan Clark asked about alignment with other industry standards,  
and Roni
    Even noted that multiple overlapping drafts are not desirable.  
Kaynam
    Hedayat noted that this is similar to the MPTS draft, and that  
the two
    should perhaps be merged.

    Someone asked about drafts proposing metrics for scalable video.  
Colin
    Perkins noted that there are none yet, but the group will  
consider them
    if any are submitted. Stephan Wenger cautioned that such drafts are
    likely premature, given his understanding of the state of scalable
    coding work.


H.264 Payload optional parameters

    draft-ietf-avt-rtp-h264-params-00

    Tom Kristensen discussed new media parameters for static  
macroblocks and
    aspect ratio for the RTP payload format for H.264. This was  
previously
    discussed as draft-kristensen-avt-rtp-h264-extension-00.txt in  
Prague;
    that has been split into draft-kristensen-avt-rtp-h264- 
rcdo-00.txt and
    this draft (the RCDO draft was not discussed).

    After briefly outlining the contents of the draft, Tom noted that  
the
    ITU has ongoing work on video submode control, which will result in
    additions to this draft. The authors therefore proposed to keep this
    draft in the working group for now, and to incorporate the additions
    when the work is complete in ITU.


Non-Compound RTCP Packets

    draft-johansson-avt-rtcp-avpf-non-compound-02.txt

    Ingemar Johansson presented the draft proposing that non-compound  
RTCP
    packets be allowed in some circumstances. He noted that non-compound
    RTCP has been adopted by 3GPP (in 26.114 section 7.3.5). It can  
be used
    with both voice and video, for either RTCP APP packets, generic NACK
    packets, and for CCM TMMBR and TMMBN packets. The main open  
issues are
    how to do the bandwidth computation, and the allow_early flag in  
AVPF.

    There are two alternatives for RTCP bandwidth computation: either  
let
    both compound and non-compound RTCP packets update avg_rtcp_size, or
    only allow regular (compound) RTCP to update avg_rtcp_size. The  
latter
    is simple to implement, but risks that regular RTCP doesn't get it's
    fair share of the bandwidth (which can be alleviated using  
allow_early
    flag) and, due to the size difference between compound and non- 
compound
    packets, requires modification to the 1/16 averaging factor in  
RFC 3550.
    The other approach is more complex, but gives an opportunity to  
ensure
    that compound RTCP gets its fair share, while still enabling  
frequent
    feedback when needed.

    The allow_early flag (RFC 4585 section 3.4 (k)) limits the  
potential for
    using non-compound RTCP as a generic NACK, since it puts a limit  
on the
    early non-compound RTCP sending rate. It was suggested to allow  
this to
    be overridden, when combined with a robust bandwidth computation
    algorithm to guarantee the regular RTCP report interval. Joerg  
Ott noted
    that RFC 4585 doesn't specify compound RTCP packets, just regularly
    scheduled packets, so there may not be a need to override  
allow_early
    if the RTCP bandwidth is increased (this is option 1 from the  
slides,
    for how to do this). Magnus Westerlund agreed that this probably  
is a
    solution to this issue, and will do some analysis to confirm.

    It was asked if the draft might be appropriate to accept as an  
AVT work
    item. Steve Casner noted that the purpose of requiring all RTCP  
packets
    to be compound packets was for multicast sessions, which are now  
less
    widely used, so he thought this reasonable, provided strong  
guidance is
    given on when it is appropriate. The sense of the room was in  
agreement,
    so the chairs agreed to pursue taking this as a work item (which  
will
    need a charter update).



RTP Keep Alive

    draft-ietf-avt-app-rtp-keepalive-00

    Xavier Marjou presented the draft on RTP keep alive. This draft  
gives a
    list of mechanisms used to keep alive NAT bindings, and details  
the pros
    and cons of each. Mechanisms surveyed include 0 byte UDP packet,  
RTCP
    multiplexed on the RTP port, STUN packets, RTP packets with  
incorrect
    version number, RTP packets with comfort noise, RTP packets with  
a no-op
    payload, and RTP packets with unknown payload type. Xavier asked  
if any
    other mechanism were known (perhaps RTSP transport of RTP), and  
if we
    want to recommend one mechanism.

    Magnus Westerlund noted that RTSP encapsulation of RTP is TCP- 
based, so
    the usual TCP keep alive mechanism will be used to maintain NAT  
bindings,
    out of the scope of this document. Jonathan Lennox noted that  
there are
    often codec specific keep alive mechanisms, in addition to  
comfort noise.
    Tom Phelan noted that 0-length DCCP packets may also be used.

    Jonathan Rosenberg noted that keep alive is only one part of the NAT
    traversal problem, and it's unclear how this draft relates to the  
full
    problem. He believes that some of the recommendations conflict  
with ICE,
    and asked that the draft be updated to much more clearly specify  
how it
    fits the big picture.

    Jonathan Rosenberg also noted that multiple options for keeping NAT
    bindings alive are bad, and requested that rather than keep  
documenting
    potential methods, the draft pick one. Xavier agreed with the  
goal, but
    noted that there is no consensus on which mechanism to pick. Lars  
Eggert
    replied that perhaps this is a sign that the draft is premature.  
Steve
    Casner dissented slightly, commenting that a draft which explains  
why
    certain mechanisms don't work is valid, and that suggesting a single
    standard mechanism isn't the only use for this draft. Magnus  
Westerlund
    agreed, and commented that the draft needs much more work on the  
pros
    and cons of the alternative mechanisms, since some of these clearly
    should be documented as one "SHOULD NOT do this".



RTP Payload Format for SVC Video

    draft-ietf-avt-rtp-svc-02

    Thomas Schierl presented the RTP payload format for SVC video.  
The SVC
    codec is now essentially stable and done, as of the Geneva JVT  
meeting
    in June 2007, so there is now a need to complete this draft. Thomas
    summarised the draft, outlined the changes since the -01 version,  
and
    the mailing list discussion (see slides). The authors' to-do list
    includes fixing the packetization rules, adding signalling, and work
    on the security consideration.

    A plea for review of the congestion control section was made.

    Roni Even, Colin Perkins, Stephan Wenger, and Jonathan Lennox  
discussed
    the use of NALU type 30, and whether it might clash with future NALU
    type allocations made by JVT. It will not, since it's in "user  
space"
    intended for unregistered allocations, and is private to this  
payload
    format. It was requested that some words be added to the draft to
    explain this status.

    The main open issue is removal of the DON ordering section,  
allowing all
    modes for the base layer, and specifying a re-sequencing  
algorithm without
    the DON. This is needed for backwards compatibility with a standard
    H.264 base layer. Stephan Wenger thinks this is the right thing  
to do,
    but cautions that it will make the draft more complex, in a way  
which
    will be difficult for non-SVC experts to understand. There are some
    discussion about how to ensure backwards compatibility with Roni  
Even,
    but no objections to this approach. Colin Perkins asked if this  
change
    will impact the IPR status of the payload format, since the DON  
ordering
    was covered by Nokia IPR. Stephan Wenger explained that it would  
not -
    the encumbered technology is still present, but is not optional  
to use.



Source-Specific Media Attributes

    draft-lennox-mmusic-sdp-source-attributes-01

    Jonathan Lennox briefly presented the source-specific SDP  
attributes.
    This is an MMUSIC draft, and is being presented in AVT to ensure  
there
    are no RTP architectural issues or problems that have been missed.
    Review is solicited.



High Resolution VoIP Metrics

   draft-ietf-avt-rtcphr-01.txt

   Geoff Hunt presented the RTCP HR VoIP metrics draft, outlining  
changes
   since the previous version, and discussing how report multiplexing  
can
   be achieved.

   Colin Perkins suggested that, while the report multiplexing  
section has
   value, it is more widely applicable than this draft.  He proposed  
that
   it would be better split into a separate draft, leaving this to  
simply
   define new metrics.

   Geoff noted that control by SDP is an open issue, especially when  
talking
   to middleboxes. Colin Perkins agreed, but suggested MMUSIC and/or  
SIPPING
   need to review that, since they have the relevant expertise.

   Geoff asked about the implications of concatenation of reports,  
problems
   with long packets, and the behaviour of HR-unaware translators. Colin
   Perkins pointed to sections in RFC 3550 describing this, and  
suggested
   that the standard behaviour should be sufficient.



Using SEED Cipher Algorithm with SRTP

    (no draft)

    Seokung Yoon presented a proposal to use the SEED cipher  
algorithm with
    SRTP. SEED is a 128 bit symmetric block cipher developed by KISA  
in 1999
    and published in TTAS.KO-12.0004 and JTC1/SC 27 N3979. It is  
defined for
    use with IPsec, TLS, etc. (see slides for RFC references).

    Dan Wing and Magnus Westerlund asked how key exchange is done,  
and noted
    that there may be a need for work in MMUSIC to define the  
appropriate
    SDP signalling to use this cipher with MIKEY and/or sdescriptions.

    Hadriel Kaplan noticed that this cipher operates on fixed block  
sizes,
    and asked if RTP padding is required to pad packets to the  
correct size
    before they can be encrypted.

    It was asked that the group consider this as a work item. The chairs
    noted that new modes of operation for SRTP are in scope, so they  
don't
    see any problem with taking this as a work item, but requested an
    individual draft be submitted initially for the group to review.


Concluding Remarks

    After the published agenda had been completed, Qiaobing Xie asked  
if the
    draft on forward shifted redundancy could be taken as a working  
group
    draft. The chairs were unwilling to make such a call with no time  
for
    the group to review the draft, and suggested it be discussed on  
the list
    over the coming weeks.

				   - + -



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



From avt-bounces@ietf.org Mon Jul 30 04:56:48 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFR3R-0004wh-EO; Mon, 30 Jul 2007 04:56:41 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFR3Q-0004wW-Dz
	for avt@ietf.org; Mon, 30 Jul 2007 04:56:40 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFR3Q-0004dx-3p
	for avt@ietf.org; Mon, 30 Jul 2007 04:56:40 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12])
	by co300216-co-outbound.avaya.com with ESMTP; 30 Jul 2007 04:56:39 -0400
X-IronPort-AV: i="4.19,197,1183348800"; d="scan'208"; a="48042119:sNHT7908912"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] Draft minutes from Chicago meeting
Date: Mon, 30 Jul 2007 10:55:57 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0428FA68@307622ANEX5.global.avaya.com>
In-Reply-To: <F21E8576-5002-4B3C-B64F-0542A51538DD@csperkins.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Draft minutes from Chicago meeting
Thread-Index: AcfSgYkEG9PckJL5RGKMGdm6zYU/xQABZwxg
References: <F21E8576-5002-4B3C-B64F-0542A51538DD@csperkins.org>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Colin Perkins" <csp@csperkins.org>,
	"AVT WG" <avt@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org


I am sorry that I could not attend the sessions in Chicago because of
scheduling conflicts.=20
=20
I have a question - what is the status of draft-ietf-avt-rtcp-xr-mib? It
looks like it was not on the agenda, and there is no mention of it in
the status slides.=20

Dan


> -----Original Message-----
> From: Colin Perkins [mailto:csp@csperkins.org]=20
> Sent: Monday, July 30, 2007 10:25 AM
> To: AVT WG
> Cc: Roni Even; Tom Taylor
> Subject: [AVT] Draft minutes from Chicago meeting
>=20
> Draft minutes from the Chicago AVT meetings are enclosed.=20
> Please send any comments or corrections to the chairs.
>=20
> Colin
>=20
>=20
>=20
>=20
>=20
>=20
> Audio/Video Transport (AVT) Working Group Minutes=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> Reported by Colin Perkins
>=20

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



From avt-bounces@ietf.org Mon Jul 30 05:24:26 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFRUH-0002T4-44; Mon, 30 Jul 2007 05:24:25 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFRUG-0002NP-8m
	for avt@ietf.org; Mon, 30 Jul 2007 05:24:24 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFRUF-0005kn-SO
	for avt@ietf.org; Mon, 30 Jul 2007 05:24:24 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:51011)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1IFRUD-0000xM-8J; Mon, 30 Jul 2007 10:24:21 +0100
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0428FA68@307622ANEX5.global.avaya.com>
References: <F21E8576-5002-4B3C-B64F-0542A51538DD@csperkins.org>
	<EDC652A26FB23C4EB6384A4584434A0428FA68@307622ANEX5.global.avaya.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <7C1D7AB6-B790-4479-918D-0517EF90C10E@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Draft minutes from Chicago meeting
Date: Mon, 30 Jul 2007 10:24:19 +0100
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On 30 Jul 2007, at 09:55, Romascanu, Dan (Dan) wrote:
> I have a question - what is the status of draft-ietf-avt-rtcp-xr- 
> mib? It
> looks like it was not on the agenda, and there is no mention of it in
> the status slides.

There were significant technical issues raised at IETF 65, with a  
resolution proposed at IETF 66 (see the minutes for details). We're  
waiting for a draft implementing that resolution.

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



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



From avt-bounces@ietf.org Mon Jul 30 05:51:52 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFRup-0000cs-Fj; Mon, 30 Jul 2007 05:51:51 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFRun-0000Xt-FH
	for avt@ietf.org; Mon, 30 Jul 2007 05:51:49 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFRum-0006l0-9O
	for avt@ietf.org; Mon, 30 Jul 2007 05:51:48 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 30 Jul 2007 12:52:48 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04CB2B00@IsrExch01.israel.polycom.com>
In-Reply-To: <46A94335.1090104@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Review draft-ietf-avt-avpf-ccm-07
Thread-Index: AcfP6Y4Qx9TZN6+aREav2tgwpZLd2ACpcz2g
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: bo.burman@ericsson.com, stewe@stewe.org, avt@ietf.org
Subject: [AVT] RE: Review draft-ietf-avt-avpf-ccm-07
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Magnus,
Looks OK.
Thanks
Roni

> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> Sent: Friday, July 27, 2007 3:58 AM
> To: Even, Roni
> Cc: avt@ietf.org; stewe@stewe.org; bo.burman@ericsson.com
> Subject: Re: Review draft-ietf-avt-avpf-ccm-07
>=20
> Hi Roni,
>=20
> Please see inline.
>=20
> Even, Roni skrev:
> >>  > 2. In 4.2.1.2 " If the media sender concludes that it can =
increase
> the
> >
> > */ [RE:] I think a clarification will make sense. /*
> >
>=20
> Okay, I will include the following:
>=20
> This should be done also for point-to-point sessions, as it not
> guaranteed that a participant can determine correctly if the sources =
are
> present in a single node and co-ordinated.
>=20
>=20
> Is that okay? I only use should as it is strictly not needed if you =
are
> convinced that you can correctly determine that the back-off is not
> needed.
>=20
>=20
>=20
> >>
> >
> > */ [RE:] I am still not sure I understand. Example the offer =
includes
> > tmmbr, tstr and fir. The answer responds with tstr only. /*
> >
> > */ Does it mean that the answerer may send tmmbr, tstr and fir but =
the
> > offerer can only send tstr. /*
> >
> > */ Also if the above is right it will mean the answerer sending =
tmmbr
> > will be able to process the response. /*
> >
>=20
> Okay, I think there might be missing some word in there that these are
> symmetric and both side need to announce support for it to be possible
> to use it. These parameter does not make sense as declarative ones.
>=20
> Now the complete sectiond reads:
>=20
> 7.2. Offer-Answer
>=20
> The Offer/Answer [RFC3264] implications for codec control protocol
> feedback messages are similar to those described in [RFC4585].  The
> offerer MAY indicate the capability to support selected codec commands
> and indications.  The answerer MUST remove all ccm parameters
> corresponding to the CCM messages that it does not support or does not
> desire to be used in this particular media session.  The answerer MUST
> NOT add new ccm parameters in addition to what has been offered.  The
> answer is binding for the media session and both offerer and answerer
> MUST only use feedback messages that both sides have explicitely
> indicated in the messages.  In others words only the joint subset of =
CCM
> parameters from the offer and answer may be used.
>=20
> Note, that including a CCM parameter in an offer or answer indicates
> that the agent (offerer or answerer) is at least capable of receiving
> the corresponding CCM message(s) and act upon them. In cases when the
> reception of a negotiated CCM messages mandates the agent to respond
> with another CCM message, it also must have that capability. Although
> not mandated to initiate CCM messages of any negotiated type it is
> generally expected that the agent will initiate CCM messages when
> suitable.
>=20
> The session maximum packet rate parameter part of the TMMBR indication
> is declarative and everyone SHALL use the highest value indicated in a
> response.  If the session maximum packet rate parameter is not present
> in an offer it SHALL NOT be included by the answerer.
>=20
> Cheers
>=20
> Magnus Westerlund
>=20
> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM/M
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------

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



From avt-bounces@ietf.org Mon Jul 30 07:40:28 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFTbo-0005td-VH; Mon, 30 Jul 2007 07:40:20 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFTbk-0005qx-Vl; Mon, 30 Jul 2007 07:40:17 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IFTbk-0002FI-LT; Mon, 30 Jul 2007 07:40:16 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12])
	by co300216-co-outbound.avaya.com with ESMTP; 30 Jul 2007 07:40:14 -0400
X-IronPort-AV: i="4.19,198,1183348800"; 
	d="scan'208"; a="48073947:sNHT762615636"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 30 Jul 2007 13:39:33 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0428FB1D@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Creation of the Performance Monitoring at Other Layers
	pmol@ietf.org list
Thread-Index: AcfSnkxL4wVbXYfnQk6Wb0Q09TJw3Q==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ippm@ietf.org>, <bmwg@ietf.org>, <ops-area@ietf.org>, <iesg@ietf.org>,
	<iab@ietf.org>, "AVT WG" <avt@ietf.org>, <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: 
Subject: [AVT] Creation of the Performance Monitoring at Other Layers
	pmol@ietf.org list
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

I have created a mail list to continue the discussions following the APM
BOF at IETF 69.=20

The name of the list is Performance Metrics at Other Layers
pmol@ietf.com list. This list hosts discussions about the process of
defining in the IETF performance metrics at other layers than IP (which
are covered by the scope of the IPPM WG) and related work items. This is
a continuation of the discussions at the APM BOF at IETF 69.

To post to this list, send your email to:

  pmol@ietf.org

General information about the mailing list is at:

  https://www1.ietf.org/mailman/listinfo/pmol
=20

Dan
=20

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



From avt-bounces@ietf.org Mon Jul 30 07:42:34 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFTdw-0006dg-RV; Mon, 30 Jul 2007 07:42:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFTdr-0006Vk-Vz; Mon, 30 Jul 2007 07:42:27 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IFTdr-0003lc-JS; Mon, 30 Jul 2007 07:42:27 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12])
	by co300216-co-outbound.avaya.com with ESMTP; 30 Jul 2007 07:42:25 -0400
X-IronPort-AV: i="4.19,198,1183348800"; d="scan'208"; a="48074383:sNHT7187580"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 30 Jul 2007 13:41:54 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0428FB1F@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Creation of the Performance Metrics at Other Layers -
	pmol@ietf.org list
Thread-Index: AcfSnkxL4wVbXYfnQk6Wb0Q09TJw3Q==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ippm@ietf.org>, <bmwg@ietf.org>, <ops-area@ietf.org>, <iesg@ietf.org>,
	<iab@ietf.org>, "AVT WG" <avt@ietf.org>, <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: 
Subject: [AVT] Creation of the Performance Metrics at Other Layers -
	pmol@ietf.org list
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

I have created a mail list to continue the discussions following the APM
BOF at IETF 69.=20

The name of the list is Performance Metrics at Other Layers
pmol@ietf.com list. This list hosts discussions about the process of
defining in the IETF performance metrics at other layers than IP (which
are covered by the scope of the IPPM WG) and related work items. This is
a continuation of the discussions at the APM BOF at IETF 69.

To post to this list, send your email to:

  pmol@ietf.org

General information about the mailing list is at:

  https://www1.ietf.org/mailman/listinfo/pmol
=20

Dan
=20

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



From avt-bounces@ietf.org Mon Jul 30 13:14:46 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFYpN-0004Ip-UN; Mon, 30 Jul 2007 13:14:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFYpM-0004Gv-Lb
	for avt@ietf.org; Mon, 30 Jul 2007 13:14:40 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFYpL-0002pj-4z
	for avt@ietf.org; Mon, 30 Jul 2007 13:14:40 -0400
Received: from relay8.apple.com (relay8.apple.com [17.128.113.38])
	by mail-out4.apple.com (Postfix) with ESMTP id 63D83D76C1F;
	Mon, 30 Jul 2007 10:14:38 -0700 (PDT)
Received: from relay8.apple.com (unknown [127.0.0.1])
	by relay8.apple.com (Symantec Mail Security) with ESMTP id 4FCCB400F3; 
	Mon, 30 Jul 2007 10:14:38 -0700 (PDT)
X-AuditID: 11807126-a844abb0000007e3-ea-46ae1c7e8dc2
Received: from [10.0.1.8] (singda.apple.com [17.202.35.52])
	by relay8.apple.com (Apple SCV relay) with ESMTP id 00C1440080;
	Mon, 30 Jul 2007 10:14:37 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p06240807c2d3cb0b797a@[10.0.1.8]>
In-Reply-To: <0MKp8S-1IFKak0Stn-0005t6@mrelay.perfora.net>
References: <0MKp8S-1IBfib2mC2-0005q2@mrelay.perfora.net>
	<p06240803c2cd4d282cd9@[17.202.35.52]>
	<0MKpCa-1IDqsy0MRm-0006V5@mrelay.perfora.net>
	<46A8F01A.8040809@ericsson.com>
	<0MKp8S-1IFKak0Stn-0005t6@mrelay.perfora.net>
Date: Mon, 30 Jul 2007 10:13:21 -0700
To: Michael A Dolan <md.1@newtbt.com>, AVT WG <avt@ietf.org>
From: Dave Singer <singer@apple.com>
Subject: Re: [AVT] draft-ietf-avt-hdrext-12
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -4.0 (----)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

At 19:02  -0700 29/07/07, Michael A Dolan wrote:
>Magnus-
>
>We all agree the preferable choice is option (a), but how do we get 
>there?  The management of the RTP header extensions is not ideal due 
>to circumstances now behind us.  I don't see how we can make 
>existing conformant practice (nearly anything) non-conformant upon 
>publication of this ID.

I want to be very clear;  neither my draft, nor any of the options 
outlined below, would make any previously conformant practice 
non-conformant.  No matter what we do with this draft, existing legal 
practices should stay legal, in my opinion.  We are only debating the 
degree and location of their documentation.

So, really (a) and (d) are a pair;  if we go (a), Mike is always free 
to do an informational RFC.

Which is why I think I would like to document them in one document, 
with 4+4 support required and 8+8 documented and mentioned and 
support for it optional.

p.s. I thought we had solved all remaining issues, includiing IANA, 
until this came up.  I really want to close this out.  My fear is 
that the 8+8 variant is enough of a technical change to the document 
that I'd have to go back through WG last call, IESG review, and all 
that.  I'm not sure I have the energy.

If that is a problem, how about we add a sentence to the 4+4 spec. 
saying "A variant of this design, using 8-bit length and tag fields, 
also exists, using a different value for the field that takes the 
value 0xBEDE here."?

>At best, all a STDs track publication can say is "SHOULD" at this 
>point in my personal view.  It is not likely to be as simple as 
>managing the "defined by profile" field as an enumerated field by 
>IANA or explicit RFC publication as some have suggested, since 3350 
>gave no indication at all how to manage this field or even if it was 
>a constant (which some presume incorrectly).
>
>IETF AVT WG is an open process. All other existing current extension 
>syntax authors are invited to try and make the effort to merge them 
>into a single compatible standard design as part of the process. 
>Although I wish I was aware of this other design sooner in the 
>process, I tried to craft the proposal in this thread so that both 
>could exist concurrently in a well-structured manner.  I would 
>welcome other uses to come forward so we could craft a single 
>overall mechanism.  We all *know* there are other uses (I found a 
>new one last week), but the burden is on those authors to come 
>forward and make the effort. Lacking other contributions, the WG 
>should make an effort to make the published ones (minimally these 
>two) work as best we can.
>
>I am still trying to avoid an evaluation ("bake-off") of the two 
>designs since it will alienate one of them after the fact, 
>but....you cite "tradeoff" and "proprietary" evaluation criteria to 
>support the 4/4-bit design alone in pursuit of option (a).  So if 
>the path forward is to have a technical evaluation of tradeoffs and 
>relative "propriety" to reach option (a), then I would like to 
>understand your conclusions better, especially the one about one 
>being more proprietary than another.
>
>But before we enter into a "bake-off", it is still my view that the 
>best we can accomplish under the circumstances of how 3350 left 
>things is to document what practices we know about (via authors 
>willing to bring them forward) in a clearly discriminating manner, 
>concurrent with a recommendation for all new designs.  Please note 
>that I did not try to assert that the other design in this thread as 
>the preferred one - the contrary in fact, deferring to the existing 
>ID's proposal for future designs.
>
>Regards,
>
>         Mike
>
>At 12:03 PM 7/26/2007, Magnus Westerlund wrote:
>>Michael A Dolan skrev:
>>>Dave and all-
>>>I was hoping to avoid a debate on relative deployment and the 
>>>value of 4 bits versus 8 bits by proposing option (c) below (which 
>>>is what I tried to articulate in last week's post).  In a perfect 
>>>world, we would drive to (a), but I don't see how to get there in 
>>>any reasonable timeline.
>>>Mean-time the world moves on making more of these deployments, and 
>>>worse, more non-conformant variants we don't even know about....
>>>Can everyone live with option (c)?
>>
>>Preferably no, this is a core extension that we are likely to see 
>>quite a lot of use in the future. I think 4+4 has a good tradeoff. 
>>I would like to go with a) because of this to avoid confusing 
>>things. If there are "proprieatery" deployment as it is of 8+8 that 
>>is not different from other "proprieatery" extensions in this field.
>>
>>>>Choices:
>>>>
>>>>a) go with just 4+4 or just 8+8, and drop one.  I am aware of 
>>>>implementations of both, so this isn't ideal.
>>>>
>>>>b) in the same document, require support for both.
>>>>
>>>>c) in the same document, require support for one, and recommend 
>>>>support for the other.
>>>>
>>>>d) publish one separately, as an informational RFC.
>>
>>Cheers
>>
>>Magnus Westerlund
>>
>>IETF Transport Area Director & TSVWG Chair
>>----------------------------------------------------------------------
>>Multimedia Technologies, Ericsson Research EAB/TVM/M
>>----------------------------------------------------------------------
>>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 Singer
Apple/QuickTime

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



From avt-bounces@ietf.org Tue Jul 31 07:26:12 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFprO-0000IJ-Nm; Tue, 31 Jul 2007 07:25:54 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFprN-0000Hg-4s
	for avt@ietf.org; Tue, 31 Jul 2007 07:25:53 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFprM-0004r6-Gn
	for avt@ietf.org; Tue, 31 Jul 2007 07:25:53 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	29A0221101; Tue, 31 Jul 2007 13:25:51 +0200 (CEST)
X-AuditID: c1b4fb3e-ae831bb0000007e1-e9-46af1c3fabda
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	F0A96210DD; Tue, 31 Jul 2007 13:25:50 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jul 2007 13:25:50 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jul 2007 13:25:50 +0200
Message-ID: <46AF1C3E.5070101@ericsson.com>
Date: Tue, 31 Jul 2007 13:25:50 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Draft minutes from Chicago meeting
References: <F21E8576-5002-4B3C-B64F-0542A51538DD@csperkins.org>
In-Reply-To: <F21E8576-5002-4B3C-B64F-0542A51538DD@csperkins.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Jul 2007 11:25:50.0456 (UTC)
	FILETIME=[8C6E8780:01C7D365]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: Roni Even <roni.even@polycom.co.il>, AVT WG <avt@ietf.org>,
	Tom Taylor <tom.taylor@rogers.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

One comment on the minutes.

Colin Perkins skrev:

> 
> RTP Keep Alive
> 
>    draft-ietf-avt-app-rtp-keepalive-00
> 
>    Xavier Marjou presented the draft on RTP keep alive. This draft gives a
>    list of mechanisms used to keep alive NAT bindings, and details the pros
>    and cons of each. Mechanisms surveyed include 0 byte UDP packet, RTCP
>    multiplexed on the RTP port, STUN packets, RTP packets with incorrect
>    version number, RTP packets with comfort noise, RTP packets with a no-op
>    payload, and RTP packets with unknown payload type. Xavier asked if any
>    other mechanism were known (perhaps RTSP transport of RTP), and if we
>    want to recommend one mechanism.
> 
>    Magnus Westerlund noted that RTSP encapsulation of RTP is TCP-based, so
>    the usual TCP keep alive mechanism will be used to maintain NAT 
> bindings,
>    out of the scope of this document. Jonathan Lennox noted that there are
>    often codec specific keep alive mechanisms, in addition to comfort 
> noise.

I think I actually said that the RTSP session keep-alive over the same 
TCP connection is what will keep it alive. In addition that timeouts on 
TCP is much less of a problem.

cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
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 Jul 31 08:25:20 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFqmn-0008Sx-6J; Tue, 31 Jul 2007 08:25:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFqml-0008Sr-8U
	for avt@ietf.org; Tue, 31 Jul 2007 08:25:11 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFqmk-00064x-9u
	for avt@ietf.org; Tue, 31 Jul 2007 08:25:11 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	A2F0120661; Tue, 31 Jul 2007 14:24:43 +0200 (CEST)
X-AuditID: c1b4fb3c-aee7cbb0000007e1-b0-46af2a0b7f2d
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	83D592054C; Tue, 31 Jul 2007 14:24:43 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jul 2007 14:24:43 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jul 2007 14:24:43 +0200
Message-ID: <46AF2A0A.8070407@ericsson.com>
Date: Tue, 31 Jul 2007 14:24:42 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: Dave Singer <singer@apple.com>
Subject: Re: [AVT] draft-ietf-avt-hdrext-12
References: <0MKp8S-1IBfib2mC2-0005q2@mrelay.perfora.net>	<p06240803c2cd4d282cd9@[17.202.35.52]>	<0MKpCa-1IDqsy0MRm-0006V5@mrelay.perfora.net>	<46A8F01A.8040809@ericsson.com>	<0MKp8S-1IFKak0Stn-0005t6@mrelay.perfora.net>
	<p06240807c2d3cb0b797a@[10.0.1.8]>
In-Reply-To: <p06240807c2d3cb0b797a@[10.0.1.8]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Jul 2007 12:24:43.0076 (UTC)
	FILETIME=[C6099040:01C7D36D]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi,

IETF standards track documents are strong recommendations on how to 
solve a problem. In many case that doesn't rule out the existence of 
other solutions. However, it may hurt interoperability and/or complicate 
  implementations. There is no protocol police that goes ut and stop 
usage that doesn't follow IETF. In addition the header extension 
mechanism in RTP is free to use by anyone. So 8+8 is definitely 
conformant to RFC 3550. One has only to be aware of the limitations they 
result in. But the desirable future is that anyone in the future that 
needs this functionality will use RFC XXX (what ever the number will be 
for draft-ietf-avt-hdrext).

As I see it the best we can do for the future is to select one solution 
and go forward. And hope that most future users out there uses that 
single solution. That is in my view the best way and will maximize 
interoperability in the future. I can also hope that some that uses 
their own extension mechanism will move to the IETF defined one.

> Which is why I think I would like to document them in one document, 
 > with 4+4 support required and 8+8 documented and mentioned and
 > support for it optional.

I hope that it is clearer why I propose to select only a single one and 
stick with that. I don't want to have two of them in the document 
because that will result in that everyone will have to implement both. 
IETF has become worse and worse at selecting a single solution and 
sticking with it. I asked the question about deployement, because as I 
see it there are some difference in the technical tradeoff but if you 
had a large deployement that would still be compatible with the tag 
value mechanism in the current WG document then I think it would have 
been reasonable to switch to the 8+8 tradeoff. However, as you aren't 
forthcomming with that information there is no data to for determinging 
that 8+8 would be a more reasonable choice then 4+4. I am also worried 
about the ID numberspace and control over that.

I am worried about the 8+8 ID namespace that may make it difficult to 
adopt. draft-ietf-avt-hdrext contains a larger namespace that is mapped 
onto the ID values. This as 16 values would never last. But the same is 
also true for 256 values. Thus the same rule could be applied. However, 
that requires that IETF gets full control of at least a substantial 
block of the field values. There must be full agreement between the 
original definers and IETF that control is transfered. In addition it 
must be known which values are used and already handed out. The only 
alternative for a 8+8 solutio would be to go with another header 
extension identifier.

Because of that I would propose that we go forward with a document that 
only provides the 4+4 solution.

Dave Singer skrev:
> 
> If that is a problem, how about we add a sentence to the 4+4 spec. 
> saying "A variant of this design, using 8-bit length and tag fields, 
> also exists, using a different value for the field that takes the value 
> 0xBEDE here."?
> 

There might be value in pointing out that there exist similar but not 
IETF defined solutions for the header extension field. However, I wonder 
if it would confuse more then any benefit it gives. But my attempt is 
the following:

"At least one similar solution is known to exist for solving the first 
drawback.  That solution uses different field lengths, but also another 
16-bit identifier value, thus no risk of misstake between them exist. 
The resolution of the second drawback and slightly differnt tradebacks 
resulted in the solution present in this document."

The above is written based on that the solution you documents did not 
try to resolve the namespace issues to provide an basically unlimited 
number of header extensions.

I might have not given the impression before that there is benefit in 
document the 8+8 solutions that are in use. I think it would be best 
that it is documented in an informational RFC. However, I would like to 
see good wording in there that this is a documentation of something that 
is used, but that it is prefered to use draft-ietf-avt-hdrext.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
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 Jul 31 10:18:08 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFsXn-0002GT-Pm; Tue, 31 Jul 2007 10:17:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFsXm-0002Fw-6R
	for avt@ietf.org; Tue, 31 Jul 2007 10:17:50 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFsXk-0001ck-PA
	for avt@ietf.org; Tue, 31 Jul 2007 10:17:50 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:54561)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1IFsXk-0002J6-65 for avt@ietf.org; Tue, 31 Jul 2007 15:17:48 +0100
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: 7bit
Message-Id: <68147E97-4D45-40F7-B5C3-0F12195CB753@csperkins.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: AVT WG <avt@ietf.org>
From: Colin Perkins <csp@csperkins.org>
Date: Tue, 31 Jul 2007 15:17:46 +0100
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Subject: [AVT] Non-compound RTCP as work item?
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

The consensus of the meeting in Chicago was to take the draft on non- 
compound RTCP (draft-johansson-avt-rtcp-avpf-non-compound-02.txt) as  
an AVT work item. This would involve adding the following text to the  
charter:

  - to specify how the RFC 3550 requirement on RTCP senders to always
    send compound packets can be relaxed to allow for non-compound
    packets. The specification need to define under which criteria
    non-compound RTCP packets may be sent while maintaining the
    functionality that motivated the usage of compound RTCP packets
    and keep the bandwidth within specified limits.

with a milestone of:

  - Sep 2008 Submit Non-Compound usage specification for Proposed  
Standard

Since not all working group members attended the Chicago meeting,  
this note is to solicit input on this proposal from the wider group.  
Please comment on this to the mailing list by 7th August 2007.

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



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



From avt-bounces@ietf.org Tue Jul 31 14:24:57 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFwOk-0006dG-B3; Tue, 31 Jul 2007 14:24:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFwOj-0006dB-SC
	for avt@ietf.org; Tue, 31 Jul 2007 14:24:45 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFwOi-0001MP-E0
	for avt@ietf.org; Tue, 31 Jul 2007 14:24:45 -0400
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:61082
	helo=[192.168.0.4])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1IFwOh-0008KA-Nm for avt@ietf.org; Tue, 31 Jul 2007 19:24:43 +0100
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: 7bit
Message-Id: <CB420C21-34F0-41E5-8EE9-36929AD23FAA@csperkins.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: AVT WG <avt@ietf.org>
From: Colin Perkins <csp@csperkins.org>
Date: Tue, 31 Jul 2007 19:24:40 +0100
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Subject: [AVT] Non-compound RTCP and Early AVPF feedback
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

One of the open issues with the non-compound RTCP draft is whether  
multiple non-compound early packets can be sent between regularly  
scheduled packets, when the RTP/AVPF profile is used. The draft  
notes, in section 5.1, that:

    In order to get as much as possible out of of the non-compound RTCP
    concept, it is necessary to relax the sending rules in RFC 4585
    [RFC4585] in such a way that it is possible to transmit more that  
one
    early feedback RTCP between regular RTCP, presently this is
    controlled by means of the allow_early flag which has the effect  
that
    only one early feedback message is allowed between the regularly
    scheduled RTCP.  The proposed relaxation is reasonable as the  
size of
    the non-compound RTCP is expected to be small compared to the  
regular
    RTCP.  The relaxation however needs to be done in a way that it is
    both bandwidth conservative and robust/scalable for an increased
    number of users.  A possible outline of an algorithm that does this
    overrides the allow_early flag to the value TRUE if the bandwith
    consumed by non-compound RTCP is within some predefined limits, one
    such limit may be that non-compound RTCP should not be allowed to
    consume more than a predefiend fraction of the total RTCP bandwidth.
    Another option may be to use the SDP attribute "trr-int" as limiting
    factor.

While relaxing the sending rules for non-compound early feedback  
packets might be an appropriate thing to do, it is important to  
remember that the AVPF rules were chosen after considerable  
discussion, to address certain requirements. Any decision to relax  
those rules would have to be accompanied by a discussion of how and  
why the requirements have changed since RFC 4585 was under  
discussion, and a justification why the existing mechanisms are not  
sufficient.

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



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



From avt-bounces@ietf.org Tue Jul 31 14:50:24 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFwnX-0006aJ-Uq; Tue, 31 Jul 2007 14:50:23 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFwnW-0006aD-F7
	for avt@ietf.org; Tue, 31 Jul 2007 14:50:22 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFwnW-0003hX-00
	for avt@ietf.org; Tue, 31 Jul 2007 14:50:22 -0400
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:61159
	helo=[192.168.0.4])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1IFwnV-0003Js-4k for avt@ietf.org; Tue, 31 Jul 2007 19:50:21 +0100
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: 7bit
Message-Id: <335974CC-2E34-439B-AB39-EE382435CB9D@csperkins.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: AVT WG <avt@ietf.org>
From: Colin Perkins <csp@csperkins.org>
Date: Tue, 31 Jul 2007 19:50:17 +0100
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Subject: [AVT] SVC - congestion control
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

At the meeting last week, Stephan Wenger asked for review of the  
congestion control section of draft-ietf-avt-rtp-svc-02.txt. I have  
reviewed this, and think it appropriate, in so far as it goes. It  
might be useful, however, to reference some of the literature on  
congestion control using layered coding, giving some pointers to  
algorithms for managing multiple layers in the presence of congestion  
(RFC 3450 is perhaps the most relevant IETF work; there are also many  
research papers, of course - a recent survey paper might an  
appropriate reference).

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



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



From avt-bounces@ietf.org Tue Jul 31 17:47:38 2007
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFzYw-0002wZ-EC; Tue, 31 Jul 2007 17:47:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFzYu-0002wS-Qq
	for avt@ietf.org; Tue, 31 Jul 2007 17:47:28 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFzYt-0006WN-DJ
	for avt@ietf.org; Tue, 31 Jul 2007 17:47:28 -0400
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:62373
	helo=[192.168.0.4])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1IFzYs-0002dU-1H; Tue, 31 Jul 2007 22:47:26 +0100
In-Reply-To: <46AF1C3E.5070101@ericsson.com>
References: <F21E8576-5002-4B3C-B64F-0542A51538DD@csperkins.org>
	<46AF1C3E.5070101@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <8BA31874-63E8-4FB5-9843-17C06FD0EF55@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Draft minutes from Chicago meeting
Date: Tue, 31 Jul 2007 22:47:24 +0100
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: Roni Even <roni.even@polycom.co.il>, AVT WG <avt@ietf.org>,
	Tom Taylor <tom.taylor@rogers.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On 31 Jul 2007, at 12:25, Magnus Westerlund wrote:
> Colin Perkins skrev:
>> RTP Keep Alive
>>    draft-ietf-avt-app-rtp-keepalive-00
>>    Xavier Marjou presented the draft on RTP keep alive. This draft  
>> gives a
>>    list of mechanisms used to keep alive NAT bindings, and details  
>> the pros
>>    and cons of each. Mechanisms surveyed include 0 byte UDP  
>> packet, RTCP
>>    multiplexed on the RTP port, STUN packets, RTP packets with  
>> incorrect
>>    version number, RTP packets with comfort noise, RTP packets  
>> with a no-op
>>    payload, and RTP packets with unknown payload type. Xavier  
>> asked if any
>>    other mechanism were known (perhaps RTSP transport of RTP), and  
>> if we
>>    want to recommend one mechanism.
>>    Magnus Westerlund noted that RTSP encapsulation of RTP is TCP- 
>> based, so
>>    the usual TCP keep alive mechanism will be used to maintain NAT  
>> bindings,
>>    out of the scope of this document. Jonathan Lennox noted that  
>> there are
>>    often codec specific keep alive mechanisms, in addition to  
>> comfort noise.
>
> I think I actually said that the RTSP session keep-alive over the  
> same TCP connection is what will keep it alive. In addition that  
> timeouts on TCP is much less of a problem.

Thanks - I'll fix and upload a revised version for the proceedings.

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



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



