From avt-bounces@ietf.org Fri Jun 01 13:17: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 1HuAkL-0006a0-0b; Fri, 01 Jun 2007 13:17:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HuAio-0004h2-A1; Fri, 01 Jun 2007 13:15:30 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HuAin-0008Gv-1H; Fri, 01 Jun 2007 13:15:30 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:56988)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HuAig-0007Vf-Ez; Fri, 01 Jun 2007 18:15:22 +0100
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <289643F2-2529-4C24-B430-B9967B5DADD4@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Fri, 1 Jun 2007 18:15:23 +0100
To: IETF AVT WG <avt@ietf.org>,
 behave@ietf.org,
 mmusic <mmusic@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
X-Mailman-Approved-At: Fri, 01 Jun 2007 13:17:03 -0400
Cc: Cullen Jennings <fluffy@cisco.com>,
	Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Xavier Marjou <xavier.marjou@orange-ft.com>,
	Roni Even <roni.even@polycom.co.il>,
	Tom Taylor <tom.taylor@rogers.com>, Joerg Ott <jo@acm.org>,
	Jean-Francois Mule <jf.mule@cablelabs.com>,
	"Dan Wing \(\(dwing\)\)" <dwing@cisco.com>
Subject: [AVT] Moving draft-marjou-behave-app-rtp-keepalive to AVT
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

There has been some private discussion on adopting the draft on  
Application Mechanisms for maintaining alive NAT mappings associated  
with RTP flows (draft-marjou-behave-app-rtp-keepalive-01.txt) as an  
AVT working group draft. This has previously been discussed in AVT,  
BEHAVE and MMUSIC. Opinions on whether this draft should become a  
working group draft, and on the appropriate home for it, are  
solicited by 8 June 2007.

Colin (as AVT co-chair)

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



From avt-bounces@ietf.org Fri Jun 01 13:47: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 1HuBDc-0002mo-2r; Fri, 01 Jun 2007 13:47:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HuBDa-0002mi-7c
	for avt@ietf.org; Fri, 01 Jun 2007 13:47:18 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HuBDY-0003Jk-Ul
	for avt@ietf.org; Fri, 01 Jun 2007 13:47:18 -0400
Received: from relay7.apple.com (relay7.apple.com [17.128.113.37])
	by mail-out4.apple.com (Postfix) with ESMTP id 685FC7C360C
	for <avt@ietf.org>; Fri,  1 Jun 2007 10:47:16 -0700 (PDT)
Received: from relay7.apple.com (unknown [127.0.0.1])
	by relay7.apple.com (Symantec Mail Security) with ESMTP id 58545300AA
	for <avt@ietf.org>; Fri,  1 Jun 2007 10:47:16 -0700 (PDT)
X-AuditID: 11807125-a1767bb000000801-e2-46605ba231e1
Received: from [17.202.35.52] (singda.apple.com [17.202.35.52])
	by relay7.apple.com (Apple SCV relay) with ESMTP id B43A830434
	for <avt@ietf.org>; Fri,  1 Jun 2007 10:47:14 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p06240806c2860b7f7f98@[17.202.35.52]>
In-Reply-To: <1042C828-2B8E-499F-B7CD-3B5977F14C12@csperkins.org>
References: <1042C828-2B8E-499F-B7CD-3B5977F14C12@csperkins.org>
Date: Fri, 1 Jun 2007 10:47:04 -0700
To: IETF AVT WG <avt@ietf.org>
From: Dave Singer <singer@apple.com>
Subject: Re: [AVT] IPR statement on draft-ietf-avt-rtp-no-op-04
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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:58  +0100 31/05/07, Colin Perkins wrote:
>The secretariat informs us that an updated IPR disclosure has been 
>submitted pertaining to the RTP no-op payload format:
>
>https://datatracker.ietf.org/public/ipr_detail_show.cgi?ipr_id=854
>

Could the authors say a little about this?  I have a lot of respect 
for (and my company pays a lot of money to license) truly inventive 
techniques, and so on.

But here we have an IPR statement for packets which by definition 
contain nothing useful, and can be discarded by the recipient.
-- 
David Singer
Apple/QuickTime

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



From avt-bounces@ietf.org Fri Jun 01 15: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 1HuD5m-0000el-2q; Fri, 01 Jun 2007 15:47:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HuBYx-0005pV-Ae; Fri, 01 Jun 2007 14:09:23 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HuBYx-0006XO-1f; Fri, 01 Jun 2007 14:09:23 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 01 Jun 2007 11:09:22 -0700
X-IronPort-AV: i="4.16,373,1175497200"; 
	d="scan'208"; a="157623593:sNHT46360602"
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 l51I9M8m025733; 
	Fri, 1 Jun 2007 11:09:22 -0700
Received: from dwingwxp ([10.32.240.194])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l51I9G20023088;
	Fri, 1 Jun 2007 18:09:16 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Colin Perkins'" <csp@csperkins.org>, "'IETF AVT WG'" <avt@ietf.org>,
	<behave@ietf.org>, "'mmusic'" <mmusic@ietf.org>
Date: Fri, 1 Jun 2007 11:09:16 -0700
Message-ID: <089301c7a477$fadbf0d0$10676b80@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcekcHgB7Z2/vHEaSLOivZMtDF4I4gABfTZQ
In-Reply-To: <289643F2-2529-4C24-B430-B9967B5DADD4@csperkins.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1760; t=1180721362;
	x=1181585362; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20Moving=20draft-marjou-behave-app-rtp-keepalive=20to=2
	0AVT |Sender:=20;
	bh=27wsY7m54nhgtgcQ6ZG99GA7h+ssM7bK44h6cpMNfGU=;
	b=tw4mAUjhG6RgV9K9h4gq66cbC8jALyBSZ+EXUrkAlqp0weiOOUl7Zdw8G4td11XmyQrg2OvO
	wj5eQ9tk1howHHa3ac5eaBOgn+ymsnOPhV1oyXM15oBtGOggOUvpA+8D;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (s
	ig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
X-Mailman-Approved-At: Fri, 01 Jun 2007 15:47:20 -0400
Cc: 'Cullen Jennings' <fluffy@cisco.com>,
	'Magnus Westerlund' <magnus.westerlund@ericsson.com>,
	'Xavier Marjou' <xavier.marjou@orange-ft.com>,
	'Roni Even' <roni.even@polycom.co.il>,
	'Tom Taylor' <tom.taylor@rogers.com>, 'Joerg Ott' <jo@acm.org>,
	'Jean-Francois Mule' <jf.mule@cablelabs.com>
Subject: [AVT] RE: Moving draft-marjou-behave-app-rtp-keepalive to AVT
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

> There has been some private discussion on adopting the draft on  
> Application Mechanisms for maintaining alive NAT mappings associated  
> with RTP flows (draft-marjou-behave-app-rtp-keepalive-01.txt) as an  
> AVT working group draft. This has previously been discussed in AVT,  
> BEHAVE and MMUSIC. Opinions on whether this draft should become a  
> working group draft, and on the appropriate home for it, are  
> solicited by 8 June 2007.
> 
> Colin (as AVT co-chair)

We need a document that consolidates NAT keepalive mechanisms for
UDP-based protocols, most notably RTP (and, to a lesser extent,
SIP).  Currently this is spread in various documents and there
is no consolidated guidance to implementtors on the strength
or weakness of various approaches.  Section 4 of Xavier's 
document shows the current state of the art -- 7 different
keepalive techniques are in various levels of active use.

Most of the keepalive techniques apply to RTP, and thus AVT seems
the best home.  There are a few exceptions which don't fit into
AVT, such as the keepalive technique used by SIP Outbound 
(draft-ietf-sip-outbound), but I don't see the exceptions as
significant enough to resist making this an AVT WG item.  If we 
had an "RAIWG" (akin to TSVWG), it might fit best there, but we 
don't have one.  It doesn't quite fit into BEHAVE, as NATs only
care to see a UDP packet is occasionally sent to the peer and 
NATs don't care what sort of UDP packet is sent; however, the
receiving peer may very much care if it's a STUN packet, a
0-byte packet, or the 5 other types of packets described in
Xavier's document.

I support adding a milestone to AVT for keepalives, and adopting 
that document to meet that milestone.

-d

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



From avt-bounces@ietf.org Fri Jun 01 15:50: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 1HuD8a-0002rk-Ph; Fri, 01 Jun 2007 15:50:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HuD8N-0002it-2U; Fri, 01 Jun 2007 15:50:03 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HuD8M-0003Qp-FY; Fri, 01 Jun 2007 15:50:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 567A83299D;
	Fri,  1 Jun 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HuD8M-0003k1-7f; Fri, 01 Jun 2007 15:50: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: <E1HuD8M-0003k1-7f@stiedprstage1.ietf.org>
Date: Fri, 01 Jun 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-avpf-ccm-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		: 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

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-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-avpf-ccm-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-6-1104912.I-D@ietf.org>

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

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

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


--OtherAccess--

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

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

--NextPart--




From avt-bounces@ietf.org Sat Jun 02 14:07: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 1HuY0y-0004Fv-GX; Sat, 02 Jun 2007 14:07:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HuY0x-0004Eh-0z
	for avt@ietf.org; Sat, 02 Jun 2007 14:07:47 -0400
Received: from gateway0.eecs.berkeley.edu ([169.229.60.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HuY0t-0006nE-KC
	for avt@ietf.org; Sat, 02 Jun 2007 14:07:47 -0400
Received: from [128.32.34.73] (dhcp-34-73.CS.Berkeley.EDU [128.32.34.73])
	(authenticated bits=0)
	by gateway0.EECS.Berkeley.EDU (8.14.1/8.13.5) with ESMTP id
	l52I7ZLw013927
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Sat, 2 Jun 2007 11:07:37 -0700 (PDT)
In-Reply-To: <E1HuW1P-0002us-7W@megatron.ietf.org>
References: <E1HuW1P-0002us-7W@megatron.ietf.org>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <DF39FF80-5735-4967-A762-9B58A720F144@eecs.berkeley.edu>
Content-Transfer-Encoding: 7bit
From: lazzaro <lazzaro@eecs.berkeley.edu>
Subject: Re: [AVT] IPR statement on draft-ietf-avt-rtp-no-op-04 
Date: Sat, 2 Jun 2007 11:07:34 -0700
To: avt@ietf.org
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: lazzaro <lazzaro@eecs.berkeley.edu>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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 Jun 2, 2007, at 9:00 AM, Dave Singer <singer@apple.com> wrote:

> But here we have an IPR statement for packets which by definition
> contain nothing useful, and can be discarded by the recipient.


I agree with David.


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



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



From avt-bounces@ietf.org Sun Jun 03 22:04: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 1Hv1vd-0000Tm-Jh; Sun, 03 Jun 2007 22:04:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hv1vc-0000TO-Ee; Sun, 03 Jun 2007 22:04:16 -0400
Received: from [202.99.23.227] (helo=people.com.cn)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1Hv1vb-0002mR-Hx; Sun, 03 Jun 2007 22:04:16 -0400
Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id jm804663b381; Mon, 04 Jun 2007 10:12:10 +0800
Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC
	2.9.5.8) with SMTP id jm9d465c8f9c; Wed, 30 May 2007 04:06:49 +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, 30 May 2007 04:06:49 +0800
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ht7hr-0000ZV-ML; Tue, 29 May 2007 15:50:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ht7hi-0000Xf-Or; Tue, 29 May 2007 15:50:02 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ht7hi-0006hh-Fn; Tue, 29 May 2007 15:50:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 721393289E;
	Tue, 29 May 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Ht7hi-0007Mg-AL; Tue, 29 May 2007 15:50: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: <E1Ht7hi-0007Mg-AL@stiedprstage1.ietf.org>
Date: Tue, 29 May 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
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.2 (++)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-avpf-ccm-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		: Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF)
	Author(s)	: S. Wenger, et al.
	Filename	: draft-ietf-avt-avpf-ccm-06.txt
	Pages		: 68
	Date		: 2007-5-29
	
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-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-avpf-ccm-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-avpf-ccm-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-5-29120427.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2007-5-29120427.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 Jun 04 04:24: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 1Hv7rJ-0003ED-Au; Mon, 04 Jun 2007 04:24:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hv79t-0005k1-9o; Mon, 04 Jun 2007 03:39:21 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hv79r-00067C-GX; Mon, 04 Jun 2007 03:39:21 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l547cvtY029761; Mon, 4 Jun 2007 10:39:07 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Jun 2007 10:38:53 +0300
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by
	esebh103.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 4 Jun 2007 10:38:52 +0300
Received: from [172.21.34.187] (esdhcp034187.research.nokia.com
	[172.21.34.187])
	by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l547coL1003802; Mon, 4 Jun 2007 10:38:50 +0300
In-Reply-To: <089301c7a477$fadbf0d0$10676b80@amer.cisco.com>
References: <089301c7a477$fadbf0d0$10676b80@amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <273FB34D-25A1-4A12-937B-1AAE5B35F9DA@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
Date: Mon, 4 Jun 2007 10:38:39 +0300
To: ext Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 04 Jun 2007 07:38:52.0837 (UTC)
	FILETIME=[66270550:01C7A67B]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
X-Mailman-Approved-At: Mon, 04 Jun 2007 04:24:12 -0400
Cc: Godred Fairhurst <gorry@erg.abdn.ac.uk>, Behave WG <behave@ietf.org>,
	mmusic <mmusic@ietf.org>, Xavier Marjou <xavier.marjou@orange-ft.com>,
	Tom Taylor <tom.taylor@rogers.com>, Joerg Ott <jo@acm.org>,
	IETF AVT WG <avt@ietf.org>, Jean-Francois Mule <jf.mule@cablelabs.com>,
	Colin Perkins <csp@csperkins.org>,
	tsvwg chair <tsvwg-chairs@tools.ietf.org>
Subject: [AVT] Re: [BEHAVE] RE: Moving draft-marjou-behave-app-rtp-keepalive
	to AVT
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-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="===============1919478564=="
Errors-To: avt-bounces@ietf.org


--===============1919478564==
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-31-772056426;
	protocol="application/pkcs7-signature"


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

On 2007-6-1, at 21:09, ext Dan Wing wrote:
> We need a document that consolidates NAT keepalive mechanisms for
> UDP-based protocols, most notably RTP (and, to a lesser extent,
> SIP).  Currently this is spread in various documents and there
> is no consolidated guidance to implementtors on the strength
> or weakness of various approaches.

I'm wondering if it'd make sense to add this guidance as a section in  
http://tools.ietf.org/html/draft-ietf-tsvwg-udp-guidelines?

Lars



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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGQDCCAvkw
ggJioAMCAQICEGtxkLFHQu1g67hlmYfwPuIwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDEwNDE2MTE1NFoXDTA4MDEwNDE2MTE1
NFowXDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2Vy
dDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9raWEuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEA26hjntVPZMiwh4d8tyuk9KiucvG92BVUGArk5zO1jhmq7tLFgU1mqcIg
VGumfQqjkAzIuh83kxIiqBrB05Wvxp85apwt4sUCvzMe8mQWzZZZYp0rBzwpOj+VC5pxsMRYtYW+
BaTFBEmvFr7D7C7roZUk0lDppS5SZFs4SQbEe9ykB9aeUf1iTiw2+ikyP2+JEYto14WYCoxFWbms
FbQ1uaaK+yn1WH2YHhyMfi0IOxuT0jtbsngjHJMpWIqq334zBhj+rPSUug47YBHr41FCDMHbbbjv
WbyTyDYneOW3WY8LY8bGWVlAknQGB7lgduShe6e0RI/7SL/VE6X27lM9LwIDAQABozIwMDAgBgNV
HREEGTAXgRVsYXJzLmVnZ2VydEBub2tpYS5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUF
AAOBgQCx3nxxTg/WowobVTRXBiXUEEZj4LBiunWbuAnR0UbJIgijvq3JbiJvZo2gUGiW9LPaHSBz
4oxT1VR/S/6O0a4e87oV5cOQm6ReB68o9rDfUzxHTwoCfv2wwMwBrXyzQMjyQK4Lt8siV41gmZpm
rSXMhjTJdd9uYYNoZKQLq+VM+TCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgG
A1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMg
RGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3
DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3
MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5
KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzAN
BgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9
fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+
uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMB
Af8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3
dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgG
A1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcP
f6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH
2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8x
ggMQMIIDDAIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAo
UHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ
a3GQsUdC7WDruGWZh/A+4jAJBgUrDgMCGgUAoIIBbzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcB
MBwGCSqGSIb3DQEJBTEPFw0wNzA2MDQwNzM4MzlaMCMGCSqGSIb3DQEJBDEWBBQ3AprJIczkdHUp
ni8ajjCJeBImUDCBhQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0ECEGtxkLFHQu1g67hlmYfwPuIwgYcGCyqGSIb3DQEJEAILMXigdjBiMQsw
CQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UE
AxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEGtxkLFHQu1g67hlmYfwPuIw
DQYJKoZIhvcNAQEBBQAEggEAGyyaVzI2wBbZlEYPdD/0EdWeZlAEAjaelavKYe5hZGBbxm9hroSL
ZOkkqUjEwbge+A0fQTTLEr4o1aMAipM8jYdq8jxKzAjc7KEwYliu64EAUCtaRX9sYPK93Juf/ZwX
X0i5Oo1m78WjfqMgmJbTC0LRc2urWWB2w1SoYTMACvdm1WE0d00mb7QM5jP4tLbkpawq5bDj8djO
EBbP1oqYfDZj+jHS+qc8jGzzNJtQRPBUwK4WQNRSELzsEShAV9fDVxcJ0Rv5SsE+v/hSxtyevVqx
4UF2mqWuer4H4p1s4YJ7ufyKSO+qiwXlcihAe0l4c8CcY0P1zxPYLOPU91ZM5QAAAAAAAA==

--Apple-Mail-31-772056426--


--===============1919478564==
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

--===============1919478564==--




From avt-bounces@ietf.org Mon Jun 04 12:21: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 1HvFIi-000841-F4; Mon, 04 Jun 2007 12:21:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvFIh-00083N-Aw; Mon, 04 Jun 2007 12:20:59 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvFIY-0006xf-LC; Mon, 04 Jun 2007 12:20:51 -0400
Received: from relay7.apple.com (relay7.apple.com [17.128.113.37])
	by mail-out3.apple.com (Postfix) with ESMTP id 511EA7D3D2A;
	Mon,  4 Jun 2007 09:19:57 -0700 (PDT)
Received: from relay7.apple.com (unknown [127.0.0.1])
	by relay7.apple.com (Symantec Mail Security) with ESMTP id F0215300A9; 
	Mon,  4 Jun 2007 09:20:49 -0700 (PDT)
X-AuditID: 11807125-9ef62bb000000801-90-46643be11b81
Received: from [17.202.35.52] (singda.apple.com [17.202.35.52])
	by relay7.apple.com (Apple SCV relay) with ESMTP id A0E81300A6;
	Mon,  4 Jun 2007 09:20:49 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p0624081dc289eb45c3bf@[17.202.35.52]>
In-Reply-To: <7374777208BDC7449D5620EF9423256704991181@esealmw113.eemea.ericsson.se>
	<289643F2-2529-4C24-B430-B9967B5DADD4@csperkins.org>
References: <465C0342.3010602@nsn.com>
	<7374777208BDC7449D5620EF9423256704991181@esealmw113.eemea.ericsson.se>
	<289643F2-2529-4C24-B430-B9967B5DADD4@csperkins.org>
Date: Mon, 4 Jun 2007 09:19:15 -0700
To: mmusic <mmusic@ietf.org>, IETF AVT WG <avt@ietf.org>
From: Dave Singer <singer@apple.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: "Clinton Priddle \(KI/EAB\)" <clinton.priddle@ericsson.com>
Subject: [AVT] questions about grouping media streams in RTP and SDP (RFC3388
 etc), advice needed
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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

we have a need to group together two media streams, in the style of RFC
3388 <http://www.ietf.org/rfc/rfc3388.txt> but we're unsure whether an
existing group type is suitable or not, and if it's not, we'd like to
agree on a new one, and document it (presumably in an RFC).

What we have is a normal media stream, and a separate 'repair' or
'entry' stream, that can be used when tuning in, or after loss, but is
otherwise un-needed.  An example might be a video stream with a low
I-frame interval (say every 15 seconds), with a repair stream which has
only I-frames that are equivalent to the time-parallel non-I frame, at a
frequency of say 1 per second.

It's not clear to us whether this is "one media flow" in the sense of
FID, or not.  The example offers AMR and GSM audio, which are
alternatives, and DTMF tones along with audio, which are supplementary
to each other.  Perhaps we fall afoul of this restriction:

"An application that encodes the same media using different codecs
simultaneously MUST NOT use FID to group those media lines."

or this one, for layered encoding:

"FID MUST NOT be used to group "m" lines that do not represent the same
information."  (Though how DTMF tones and their associated audio pass
this test is not clear).

Nor is it clear that the FEC group of RFC 4756 is right, either.  For a
start, we may wish to use this new ID in combination with FEC, and
secondly this tune-in stream has different characteristics.  For
example, one can typically ignore all FEC and (as long as there are no
errors) decode the stream correctly.  Ignoring the tune-in stream
entirely may mean that you will never find a tune-in point, making the
normal stream useless.

So, can we use FID for associating a repair stream with its base (we tag
the streams so we know which is which, of course)?

p.s. RFC 4756 claims in the IANA section that the FEC group is 
registered under SDP characteristics, but actually I can find no 
registry anywhere in IANA of group types.


-- 
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 Jun 05 02:28:32 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 1HvSWY-0006ve-9E; Tue, 05 Jun 2007 02:28:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvSWX-0006vS-Fu
	for avt@ietf.org; Tue, 05 Jun 2007 02:28:09 -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 1HvSWW-0003dK-0O
	for avt@ietf.org; Tue, 05 Jun 2007 02:28:09 -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: Tue, 5 Jun 2007 09:28:50 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C049E76BC@IsrExch01.israel.polycom.com>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C0495BD06@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: End of Working group last call on draft-ietf-avt-rtp-evrc-wb-02
	- 
Thread-Index: Aced34qQZg+MSwPKRm2znyNWTydbZQJWvnlw
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Even, Roni" <roni.even@polycom.co.il>,
	<avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: Colin Perkins <csp@csperkins.org>, Tom-PT Taylor <taylor@nortel.com>
Subject: [AVT] End of Working group last call on
	draft-ietf-avt-rtp-evrc-wb-02 - 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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 is done. There were no comments on the =
current version.
I will move it for publishing
Thanks
Roni Even

> -----Original Message-----
> From: Even, Roni [mailto:roni.even@polycom.co.il]
> Sent: Thursday, May 24, 2007 11:43 AM
> To: avt@ietf.org
> Cc: Colin Perkins; Tom-PT Taylor
> Subject: [AVT] Short Working group last call on =
draft-ietf-avt-rtp-evrc-
> wb-02
>=20
>=20
>=20
>=20
> Hi,
>=20
> We had draft-ietf-avt-rtp-evrc-wb-01 go through last call. There were =
some
> editorial changes and clarifications so we will have a short work =
group
> last call for draft-ietf-avt-rtp-evrc-wb-02,
>=20
> RTP payload format for EVRC-WB codec and MIME updates for EVRC-B codec
>=20
>=20
>=20
> The last call period will be 1 week expiring on Thursday, May 31 2007.
>=20
>=20
>=20
> Roni Even will be the PROTO Shepherd for this document
>=20
> Thanks
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

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



From avt-bounces@ietf.org Tue Jun 05 03:02: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 1HvT4B-0002Hl-LZ; Tue, 05 Jun 2007 03:02:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvT49-0002H6-09; Tue, 05 Jun 2007 03:02:53 -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 1HvT48-0002ip-AK; Tue, 05 Jun 2007 03:02:52 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 5 Jun 2007 10:03:31 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C049E76DA@IsrExch01.israel.polycom.com>
In-Reply-To: <p0624081dc289eb45c3bf@[17.202.35.52]>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] questions about grouping media streams in RTP and SDP
	(RFC3388 etc), advice needed
Thread-Index: AcemxHiQHUF4zzUiTS2DsZiVU+iS5gAd0gDQ
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Dave Singer" <singer@apple.com>, "mmusic" <mmusic@ietf.org>,
	"IETF AVT WG" <avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Cc: "Clinton Priddle \(KI/EAB\)" <clinton.priddle@ericsson.com>
Subject: [AVT] RE: [MMUSIC] questions about grouping media streams in RTP
	and SDP (RFC3388 etc), advice needed
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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,
For layered encoding there is a proposal for a new grouping attribute in
http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered-codec-03.tx
t

I looked at RFC3388 and I think that FID is not the answer to your
requirement as you mentioned

To me it looks like what you are looking for is a way to specify
alternate offers. If this is the case I have similar requirements and
would be happy to support such work.

You also need a way to give semantics to the "repair" stream, this can
be done based on the content attribute from RFC 4796 or using a
dependency attribute see in Schierl's draft. The mid tag is not enough
for the receiver to know what you meant by this offer and which stream
is the repair.

Here is an example for a solution using a new Alternatives grouping
attribute and giving semantics to the repair stream=20

By using the grouping attribute in the offer you can know if the
answerer understood the grouping since if he does not than he will send
an answer with no a=3Dgroup

v=3D0=20
o=3Dbob 280744730 28977631 IN IP4 host.example.com=20
s=3D=20
t=3D0 0=20

a=3Dgroup:ALTS 1 2=20
a=3Dgroup:ALTS 1 3=20

m=3Daudio 6886 RTP/AVP 0=20
c=3DIN IP6 2001:0600::1=20
a=3Dmid:1=20

m=3Dvideo 9000 RTP/AVP 100
c=3DIN IP4 192.0.2.2=20
a=3Drtpmap:100 H263-1998=20
a=3Dmid:2=20

m=3Dvideo 9002 RTP/AVP 101=20
c=3DIN IP4 192.0.2.2=20
a=3Drtpmap:101 H263-1998=20
a=3Dmid:3
a=3Dcontent:repair=3D2 or a=3Ddepend:repair=3D2


Roni Even

> -----Original Message-----
> From: Dave Singer [mailto:singer@apple.com]
> Sent: Monday, June 04, 2007 7:19 PM
> To: mmusic; IETF AVT WG
> Cc: Clinton Priddle (KI/EAB)
> Subject: [MMUSIC] questions about grouping media streams in RTP and
SDP
> (RFC3388 etc), advice needed
>=20
> Hi
>=20
> we have a need to group together two media streams, in the style of
RFC
> 3388 <http://www.ietf.org/rfc/rfc3388.txt> but we're unsure whether an
> existing group type is suitable or not, and if it's not, we'd like to
> agree on a new one, and document it (presumably in an RFC).
>=20
> What we have is a normal media stream, and a separate 'repair' or
> 'entry' stream, that can be used when tuning in, or after loss, but is
> otherwise un-needed.  An example might be a video stream with a low
> I-frame interval (say every 15 seconds), with a repair stream which
has
> only I-frames that are equivalent to the time-parallel non-I frame, at
a
> frequency of say 1 per second.
>=20
> It's not clear to us whether this is "one media flow" in the sense of
> FID, or not.  The example offers AMR and GSM audio, which are
> alternatives, and DTMF tones along with audio, which are supplementary
> to each other.  Perhaps we fall afoul of this restriction:
>=20
> "An application that encodes the same media using different codecs
> simultaneously MUST NOT use FID to group those media lines."
>=20
> or this one, for layered encoding:
>=20
> "FID MUST NOT be used to group "m" lines that do not represent the
same
> information."  (Though how DTMF tones and their associated audio pass
> this test is not clear).
>=20
> Nor is it clear that the FEC group of RFC 4756 is right, either.  For
a
> start, we may wish to use this new ID in combination with FEC, and
> secondly this tune-in stream has different characteristics.  For
> example, one can typically ignore all FEC and (as long as there are no
> errors) decode the stream correctly.  Ignoring the tune-in stream
> entirely may mean that you will never find a tune-in point, making the
> normal stream useless.
>=20
> So, can we use FID for associating a repair stream with its base (we
tag
> the streams so we know which is which, of course)?
>=20
> p.s. RFC 4756 claims in the IANA section that the FEC group is
> registered under SDP characteristics, but actually I can find no
> registry anywhere in IANA of group types.
>=20
>=20
> --
> David Singer
> Apple/QuickTime
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic

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



From avt-bounces@ietf.org Tue Jun 05 05:59: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 1HvVoz-0000CA-NB; Tue, 05 Jun 2007 05:59:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvVoy-00009D-SA; Tue, 05 Jun 2007 05:59:24 -0400
Received: from mxs1.siemens.at ([194.138.12.131] helo=atvies1zqx.siemens.at)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvVou-0005kr-Mm; Tue, 05 Jun 2007 05:59:24 -0400
Received: from vies1kbx.sie.siemens.at ([158.226.129.82])
	by atvies1zqx.siemens.at  with ESMTP id l559xF3g000331;
	Tue, 5 Jun 2007 11:59:15 +0200
Received: from nets138a.ww300.siemens.net ([158.226.129.98])
	by vies1kbx.sie.siemens.at (8.12.11.20060308/8.12.1) with ESMTP id
	l559xAPn013789; Tue, 5 Jun 2007 11:59:15 +0200
Received: from nets13ka.ww300.siemens.net ([158.226.250.80]) by
	nets138a.ww300.siemens.net with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 5 Jun 2007 11:59:12 +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
Subject: AW: [AVT] RE: [MMUSIC] questions about grouping media streams in
	RTPand SDP (RFC3388 etc), advice needed
Date: Tue, 5 Jun 2007 11:54:20 +0200
Message-ID: <AE99B7B733E1BB49B019CAA0F806D7A704DB1FF1@nets13ka.ww300.siemens.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] questions about grouping media streams in RTP and
	SDP(RFC3388 etc), advice needed
Thread-Index: AcemxHiQHUF4zzUiTS2DsZiVU+iS5gAd0gDQAAbvC4w=
References: <144ED8561CE90C41A3E5908EDECE315C049E76DA@IsrExch01.israel.polycom.com>
From: "Kalleitner, Franz" <franz.kalleitner@siemens.com>
To: "Even, Roni" <roni.even@polycom.co.il>, "Dave Singer" <singer@apple.com>, 
	"mmusic" <mmusic@ietf.org>, "IETF AVT WG" <avt@ietf.org>
X-OriginalArrivalTime: 05 Jun 2007 09:59:12.0727 (UTC)
	FILETIME=[2B360670:01C7A758]
X-purgate: clean
X-purgate: This mail is considered clean
X-purgate-type: clean
X-purgate-Ad: Checked for Spam by eleven - eXpurgate www.eXpurgate.net
X-purgate-ID: 149917::070605115915-6ED2FBB0-3E5039F0/0-0/0-15
X-purgate-size: 4660/0
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8
Cc: "Clinton Priddle \(KI/EAB\)" <clinton.priddle@ericsson.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, dave,
=20
you can find some work and ideas on how to handle a "repair" stream in =
parallel to an orignal RTP stream in RFC4588 too.
=20
cheers, franz

________________________________

Von: Even, Roni [mailto:roni.even@polycom.co.il]
Gesendet: Di 05.06.2007 09:03
An: Dave Singer; mmusic; IETF AVT WG
Cc: Clinton Priddle (KI/EAB)
Betreff: [AVT] RE: [MMUSIC] questions about grouping media streams in =
RTPand SDP (RFC3388 etc), advice needed



Dave,
For layered encoding there is a proposal for a new grouping attribute in
http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered-codec-03.tx
t

I looked at RFC3388 and I think that FID is not the answer to your
requirement as you mentioned

To me it looks like what you are looking for is a way to specify
alternate offers. If this is the case I have similar requirements and
would be happy to support such work.

You also need a way to give semantics to the "repair" stream, this can
be done based on the content attribute from RFC 4796 or using a
dependency attribute see in Schierl's draft. The mid tag is not enough
for the receiver to know what you meant by this offer and which stream
is the repair.

Here is an example for a solution using a new Alternatives grouping
attribute and giving semantics to the repair stream

By using the grouping attribute in the offer you can know if the
answerer understood the grouping since if he does not than he will send
an answer with no a=3Dgroup

v=3D0
o=3Dbob 280744730 28977631 IN IP4 host.example.com
s=3D
t=3D0 0

a=3Dgroup:ALTS 1 2
a=3Dgroup:ALTS 1 3

m=3Daudio 6886 RTP/AVP 0
c=3DIN IP6 2001:0600::1
a=3Dmid:1

m=3Dvideo 9000 RTP/AVP 100
c=3DIN IP4 192.0.2.2
a=3Drtpmap:100 H263-1998
a=3Dmid:2

m=3Dvideo 9002 RTP/AVP 101
c=3DIN IP4 192.0.2.2
a=3Drtpmap:101 H263-1998
a=3Dmid:3
a=3Dcontent:repair=3D2 or a=3Ddepend:repair=3D2


Roni Even

> -----Original Message-----
> From: Dave Singer [mailto:singer@apple.com]
> Sent: Monday, June 04, 2007 7:19 PM
> To: mmusic; IETF AVT WG
> Cc: Clinton Priddle (KI/EAB)
> Subject: [MMUSIC] questions about grouping media streams in RTP and
SDP
> (RFC3388 etc), advice needed
>
> Hi
>
> we have a need to group together two media streams, in the style of
RFC
> 3388 <http://www.ietf.org/rfc/rfc3388.txt> but we're unsure whether an
> existing group type is suitable or not, and if it's not, we'd like to
> agree on a new one, and document it (presumably in an RFC).
>
> What we have is a normal media stream, and a separate 'repair' or
> 'entry' stream, that can be used when tuning in, or after loss, but is
> otherwise un-needed.  An example might be a video stream with a low
> I-frame interval (say every 15 seconds), with a repair stream which
has
> only I-frames that are equivalent to the time-parallel non-I frame, at
a
> frequency of say 1 per second.
>
> It's not clear to us whether this is "one media flow" in the sense of
> FID, or not.  The example offers AMR and GSM audio, which are
> alternatives, and DTMF tones along with audio, which are supplementary
> to each other.  Perhaps we fall afoul of this restriction:
>
> "An application that encodes the same media using different codecs
> simultaneously MUST NOT use FID to group those media lines."
>
> or this one, for layered encoding:
>
> "FID MUST NOT be used to group "m" lines that do not represent the
same
> information."  (Though how DTMF tones and their associated audio pass
> this test is not clear).
>
> Nor is it clear that the FEC group of RFC 4756 is right, either.  For
a
> start, we may wish to use this new ID in combination with FEC, and
> secondly this tune-in stream has different characteristics.  For
> example, one can typically ignore all FEC and (as long as there are no
> errors) decode the stream correctly.  Ignoring the tune-in stream
> entirely may mean that you will never find a tune-in point, making the
> normal stream useless.
>
> So, can we use FID for associating a repair stream with its base (we
tag
> the streams so we know which is which, of course)?
>
> p.s. RFC 4756 claims in the IANA section that the FEC group is
> registered under SDP characteristics, but actually I can find no
> registry anywhere in IANA of group types.
>
>
> --
> David Singer
> Apple/QuickTime
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic

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



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



From avt-bounces@ietf.org Tue Jun 05 08:07: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 1HvXog-0003DC-CK; Tue, 05 Jun 2007 08:07:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvHhQ-000087-Br
	for avt@ietf.org; Mon, 04 Jun 2007 14:54:40 -0400
Received: from mailgw2a.lmco.com ([192.91.147.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvHhO-0002cP-Tr
	for avt@ietf.org; Mon, 04 Jun 2007 14:54:40 -0400
Received: from emss01g01.ems.lmco.com (relay1.ems.lmco.com
	[137.249.139.141])by mailgw2a.lmco.com (LM-6) with ESMTP id
	l54IsaOT016130for <avt@ietf.org>;
	Mon, 4 Jun 2007 14:54:38 -0400 (EDT)
Received: from CONVERSION-DAEMON.lmco.com by lmco.com (PMDF V6.3-x3 #31239) id
	<0JJ400D01KIVV4@lmco.com> for avt@ietf.org; 
	Mon, 04 Jun 2007 11:54:35 -0700 (PDT)
Received: from EMSS04I00.us.lmco.com ([166.17.13.135]) by lmco.com (PMDF
	V6.3-x3 #31239)
	with ESMTP id <0JJ400M9EKIIX6@lmco.com> for avt@ietf.org;
	Mon, 04 Jun 2007 11:54:24 -0700 (PDT)
Received: from EMSS35M05.us.lmco.com ([158.187.107.141]) by
	EMSS04I00.us.lmco.com with Microsoft SMTPSVC(5.0.2195.6713); Mon,
	04 Jun 2007 14:54:21 -0400
Date: Mon, 04 Jun 2007 14:54:18 -0400
From: "Mucilli, Dario" <dario.mucilli@lmco.com>
To: avt@ietf.org
Message-id: <2E1BF997C0B306448C691ABE593D24CA1157CB35@emss35m05.us.lmco.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: RFC4175 Mailing List
Thread-Index: Acem2cEl4gMBofJlSKyMXl8ueB+WAg==
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-OriginalArrivalTime: 04 Jun 2007 18:54:21.0224 (UTC)
	FILETIME=[C2F41A80:01C7A6D9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
X-Mailman-Approved-At: Tue, 05 Jun 2007 08:07:12 -0400
Subject: [AVT] RFC4175 Mailing 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>
Content-Type: multipart/mixed; boundary="===============1422601927=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1422601927==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_ZnTl4RxseLZhiLZ2GWUjbg)"
Content-class: urn:content-classes:message

This is a multi-part message in MIME format.

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

Hello,

Colin Perkins referred me to this mailing list as a good reference for
information/questions regarding RFC4175 - "RTP Payload Format for
Uncompressed Video".  What is the process/criteria for getting on this
mailing list?  Is there a web site with useful information, also?  Any
help is appreciated.  Thank you.




Dario Mucilli

Lockheed Martin Systems Integration - Owego
Advanced Computer Applications
E-Mail: dario.mucilli@lmco.com
Phone:  (607) 751-6117     Fax:  (607) 751-2397



--Boundary_(ID_ZnTl4RxseLZhiLZ2GWUjbg)
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>RFC4175 Mailing List</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Arial">Hello,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Colin =
Perkins referred me to this</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">mailing list as a good reference for =
information/questions regarding RFC4175</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">&#8211;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial"></FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">&#8220;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">RTP</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">Payload Format</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial"> for Uncompressed Video</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&#8221;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp; What is the process</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">/criteria</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial"> for getting on this =
mailing list?</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp; Is there a web site =
with useful information, also?</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp; Any help is appreciated.&nbsp; Thank =
you.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>
<BR>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B><I></I></B></SPAN><B><I><SPAN =
LANG=3D"en-us"></SPAN></I></B><A NAME=3D""><B><I><SPAN =
LANG=3D"en-us"><FONT FACE=3D"Arial">Dario =
Mucilli</FONT></SPAN></I></B></A><SPAN =
LANG=3D"en-us"><B><I></I></B></SPAN><SPAN =
LANG=3D"en-us"><B><I></I></B></SPAN><B><I><SPAN =
LANG=3D"en-us"></SPAN></I></B></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><I></I></SPAN><SPAN =
LANG=3D"en-us"><I></I></SPAN><I><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Lockheed Martin Systems Integration - =
Owego</FONT></SPAN></I></P>

<P DIR=3DLTR><I><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Advanced Computer Applications</FONT></SPAN></I></P>

<P DIR=3DLTR><I><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">E-Mail: dario.mucilli@lmco.com</FONT></SPAN></I></P>

<P DIR=3DLTR><I><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Phone:&nbsp; (607) 751-6117&nbsp;&nbsp;&nbsp;&nbsp; =
Fax:&nbsp; (607) 751-2397</FONT></SPAN></I></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>=

--Boundary_(ID_ZnTl4RxseLZhiLZ2GWUjbg)--


--===============1422601927==
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

--===============1422601927==--




From avt-bounces@ietf.org Tue Jun 05 08:10: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 1HvXrU-0003hR-Jq; Tue, 05 Jun 2007 08:10:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvXrT-0003hC-CT
	for avt@ietf.org; Tue, 05 Jun 2007 08:10:07 -0400
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvXrS-0001NQ-01
	for avt@ietf.org; Tue, 05 Jun 2007 08:10:07 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 5 Jun 2007 14:09:58 +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
Subject: RE: [AVT] RFC4175 Mailing List
Date: Tue, 5 Jun 2007 14:10:02 +0200
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD10385C043@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <2E1BF997C0B306448C691ABE593D24CA1157CB35@emss35m05.us.lmco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] RFC4175 Mailing List
Thread-Index: Acem2cEl4gMBofJlSKyMXl8ueB+WAgAkJiVg
References: <2E1BF997C0B306448C691ABE593D24CA1157CB35@emss35m05.us.lmco.com>
From: "SOLLAUD Aurelien RD-TECH-LAN" <aurelien.sollaud@orange-ftgroup.com>
To: "Mucilli, Dario" <dario.mucilli@lmco.com>
X-OriginalArrivalTime: 05 Jun 2007 12:09:58.0656 (UTC)
	FILETIME=[6FBFC800:01C7A76A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
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

go to
https://www1.ietf.org/mailman//listinfo/avt=20


________________________________

	De : Mucilli, Dario [mailto:dario.mucilli@lmco.com]=20
	Envoy=E9 : lundi 4 juin 2007 20:54
	=C0 : avt@ietf.org
	Objet : [AVT] RFC4175 Mailing List
=09
=09

	Hello,

	Colin Perkins referred me to this mailing list as a good reference for =
information/questions regarding RFC4175 - "RTP Payload Format for =
Uncompressed Video".  What is the process/criteria for getting on this =
mailing list?  Is there a web site with useful information, also?  Any =
help is appreciated.  Thank you.


		Dario Mucilli

	Lockheed Martin Systems Integration - Owego

	Advanced Computer Applications

	E-Mail: dario.mucilli@lmco.com

	Phone:  (607) 751-6117     Fax:  (607) 751-2397


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



From avt-bounces@ietf.org Tue Jun 05 08:11: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 1HvXsk-0003ym-JG; Tue, 05 Jun 2007 08:11:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvJa0-0000iK-3J; Mon, 04 Jun 2007 16:55:08 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvJZS-0006AJ-CT; Mon, 04 Jun 2007 16:54:35 -0400
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-5.cisco.com with ESMTP; 04 Jun 2007 13:54:33 -0700
X-IronPort-AV: i="4.16,382,1175497200"; 
	d="scan'208"; a="160777649:sNHT49214277"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id l54KsX4t009539; 
	Mon, 4 Jun 2007 13:54:33 -0700
Received: from dwingwxp ([10.32.240.194])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l54KsVV1009178;
	Mon, 4 Jun 2007 20:54:32 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Lars Eggert'" <lars.eggert@nokia.com>
Date: Mon, 4 Jun 2007 13:54:29 -0700
Message-ID: <05cf01c7a6ea$8cb552c0$c2f0200a@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <273FB34D-25A1-4A12-937B-1AAE5B35F9DA@nokia.com>
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: Aceme3lSljjfwKCrSgiInEGwlxLVWAAbigQw
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1085; t=1180990473;
	x=1181854473; c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20RE=3A=20Moving=20draft-marjou-behave-app-r
	tp-keepalive=20to=20AVT |Sender:=20;
	bh=v4oCKRhZr00gXsdQY/MtUNXXVDumdNrVvvNytpt7ZdM=;
	b=boi1Bs5fnaQIZ88Zh7QNPMZYVQeya5lmGY6yOE6MrzgobkTIQ5qze3yKsX90uSuxu4usQMka
	mQSsbYYpYbLmRoQB+9wWWYkvK0fTwtG3kTVHSdSUAfG9VdHvWfaEw8Ec;
Authentication-Results: sj-dkim-7; header.From=dwing@cisco.com; dkim=pass (s
	ig from cisco.com/sjdkim7002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
X-Mailman-Approved-At: Tue, 05 Jun 2007 08:11:25 -0400
Cc: 'Godred Fairhurst' <gorry@erg.abdn.ac.uk>,
	draft-ford-behave-app@tools.ietf.org,
	'Behave WG' <behave@ietf.org>, 'mmusic' <mmusic@ietf.org>,
	'Xavier Marjou' <xavier.marjou@orange-ft.com>,
	'Tom Taylor' <tom.taylor@rogers.com>, 'Joerg Ott' <jo@acm.org>,
	'IETF AVT WG' <avt@ietf.org>, 'Jean-Francois Mule' <jf.mule@cablelabs.com>,
	'Colin Perkins' <csp@csperkins.org>,
	'tsvwg chair' <tsvwg-chairs@tools.ietf.org>
Subject: [AVT] RE: [BEHAVE] RE: Moving draft-marjou-behave-app-rtp-keepalive
	to AVT
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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 2007-6-1, at 21:09, ext Dan Wing wrote:
> > We need a document that consolidates NAT keepalive mechanisms for
> > UDP-based protocols, most notably RTP (and, to a lesser extent,
> > SIP).  Currently this is spread in various documents and there
> > is no consolidated guidance to implementtors on the strength
> > or weakness of various approaches.
> 
> I'm wondering if it'd make sense to add this guidance as a 
> section in  
> http://tools.ietf.org/html/draft-ietf-tsvwg-udp-guidelines?

I agree "send periodic UDP traffic" would be good in that
document.  REQ-6 of draft-ford-behave-app-05 may provide the 
beginnings of some useful text (CC'ing the authors of that 
document).

As with all applications on today's Internet, an RTP 
application needs to be robust and able to deal with whatever 
is sent to it, so perhaps you're right -- an application-
specific keepalive document may well be overly specific and
we should, rather, document what any UDP-based application
should do to prevent middleboxes (such as NATs) from 
clobbering a flow.

-d

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



From avt-bounces@ietf.org Tue Jun 05 08:12: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 1HvXu2-0004Iy-Pl; Tue, 05 Jun 2007 08:12:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvJMQ-0001wO-Ij; Mon, 04 Jun 2007 16:41:06 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvJMQ-00045w-6c; Mon, 04 Jun 2007 16:41:06 -0400
Received: from sj-dkim-6.cisco.com ([171.68.10.81])
	by sj-iport-5.cisco.com with ESMTP; 04 Jun 2007 13:41:05 -0700
X-IronPort-AV: i="4.16,382,1175497200"; 
	d="scan'208"; a="160770180:sNHT54685206"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-6.cisco.com (8.12.11/8.12.11) with ESMTP id l54Kf5Ov005235; 
	Mon, 4 Jun 2007 13:41:05 -0700
Received: from [192.168.4.177] (sjc-fluffy-vpn1.cisco.com [10.25.236.82])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with SMTP id l54Kex07029042;
	Mon, 4 Jun 2007 20:41:00 GMT
In-Reply-To: <089301c7a477$fadbf0d0$10676b80@amer.cisco.com>
References: <089301c7a477$fadbf0d0$10676b80@amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <0DE8B4B0-B579-4FAA-9AB2-82E397AD13F9@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [AVT] RE: Moving draft-marjou-behave-app-rtp-keepalive to AVT
Date: Mon, 4 Jun 2007 13:40:11 -0700
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2500; t=1180989665;
	x=1181853665; c=relaxed/simple; s=sjdkim6002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fluffy@cisco.com;
	z=From:=20Cullen=20Jennings=20<fluffy@cisco.com>
	|Subject:=20Re=3A=20[AVT]=20RE=3A=20Moving=20draft-marjou-behave-app-rtp-
	keepalive=20to=20AVT |Sender:=20;
	bh=NWWhTaNLaS5PTFm+5mpf/qMbRp7zk2g0mkob446KcQk=;
	b=O+5Q1Fa0xI0DzjAAaXIhf8fTWnjMSg+EuwO/2pg9IGm79x09tLz+siD8v1YmGfh+1lcBkCx3
	4zBEc8l/s7XVCz1EjPBfvSWnveuYM+jOnFj6EEv6h5AjTC/G70V6oiCY;
Authentication-Results: sj-dkim-6; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim6002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
X-Mailman-Approved-At: Tue, 05 Jun 2007 08:12:44 -0400
Cc: 'Magnus Westerlund' <magnus.westerlund@ericsson.com>, behave@ietf.org,
	'mmusic' <mmusic@ietf.org>, 'Xavier Marjou' <xavier.marjou@orange-ft.com>,
	'Roni Even' <roni.even@polycom.co.il>,
	'IETF AVT WG' <avt@ietf.org>, 'Joerg Ott' <jo@acm.org>,
	'Tom Taylor' <tom.taylor@rogers.com>,
	'Jean-Francois Mule' <jf.mule@cablelabs.com>,
	'Colin Perkins' <csp@csperkins.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org


I think that the AVT WG has the right people to review and recommend  
way(s) to do keep alive for RTP flows - so if we are doing this work  
anywhere, AVT  would be my preferred WG to do it in. Now that Behave  
has published, RFC 4787, I think it is easy for the AVT group to  
ensure that whatever the recommendation is,  it will work with NATs  
that are compliant with BEHAVE. This helps resolve the issues of  
making sure that enough NAT people are involved with the discussion.


On Jun 1, 2007, at 11:09 AM, Dan Wing wrote:

>> There has been some private discussion on adopting the draft on
>> Application Mechanisms for maintaining alive NAT mappings associated
>> with RTP flows (draft-marjou-behave-app-rtp-keepalive-01.txt) as an
>> AVT working group draft. This has previously been discussed in AVT,
>> BEHAVE and MMUSIC. Opinions on whether this draft should become a
>> working group draft, and on the appropriate home for it, are
>> solicited by 8 June 2007.
>>
>> Colin (as AVT co-chair)
>
> We need a document that consolidates NAT keepalive mechanisms for
> UDP-based protocols, most notably RTP (and, to a lesser extent,
> SIP).  Currently this is spread in various documents and there
> is no consolidated guidance to implementtors on the strength
> or weakness of various approaches.  Section 4 of Xavier's
> document shows the current state of the art -- 7 different
> keepalive techniques are in various levels of active use.
>
> Most of the keepalive techniques apply to RTP, and thus AVT seems
> the best home.  There are a few exceptions which don't fit into
> AVT, such as the keepalive technique used by SIP Outbound
> (draft-ietf-sip-outbound), but I don't see the exceptions as
> significant enough to resist making this an AVT WG item.  If we
> had an "RAIWG" (akin to TSVWG), it might fit best there, but we
> don't have one.  It doesn't quite fit into BEHAVE, as NATs only
> care to see a UDP packet is occasionally sent to the peer and
> NATs don't care what sort of UDP packet is sent; however, the
> receiving peer may very much care if it's a STUN packet, a
> 0-byte packet, or the 5 other types of packets described in
> Xavier's document.
>
> I support adding a milestone to AVT for keepalives, and adopting
> that document to meet that milestone.
>
> -d
>
> _______________________________________________
> 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 Jun 05 08:57:07 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 1HvYao-0002tH-FT; Tue, 05 Jun 2007 08:56:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvYam-0002by-EK; Tue, 05 Jun 2007 08:56: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 1HvYak-0007KH-So; Tue, 05 Jun 2007 08:56: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="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 5 Jun 2007 15:57:45 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C049E77B3@IsrExch01.israel.polycom.com>
In-Reply-To: <289643F2-2529-4C24-B430-B9967B5DADD4@csperkins.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Moving draft-marjou-behave-app-rtp-keepalive to AVT
Thread-Index: AcekcI3nU1nGOa0RQoq47/CcfLvnbgC/3a7Q
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Colin Perkins" <csp@csperkins.org>, "IETF AVT WG" <avt@ietf.org>,
	<behave@ietf.org>, "mmusic" <mmusic@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: 
Subject: [AVT] RE: Moving draft-marjou-behave-app-rtp-keepalive to AVT
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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 that defining the keepalive for RTP that will not break RTP is
an important work and can be done in AVT.=20
I read the draft and it looks like a good start. I support as having it
an AVT working group draft


Roni Even=20

> -----Original Message-----
> From: Colin Perkins [mailto:csp@csperkins.org]
> Sent: Friday, June 01, 2007 8:15 PM
> To: IETF AVT WG; behave@ietf.org; mmusic
> Cc: Even, Roni; Tom Taylor; Dan Wing ((dwing)); Cullen Jennings; Joerg
> Ott; Xavier Marjou; Jean-Francois Mule; Magnus Westerlund
> Subject: Moving draft-marjou-behave-app-rtp-keepalive to AVT
>=20
> There has been some private discussion on adopting the draft on
> Application Mechanisms for maintaining alive NAT mappings associated
> with RTP flows (draft-marjou-behave-app-rtp-keepalive-01.txt) as an
> AVT working group draft. This has previously been discussed in AVT,
> BEHAVE and MMUSIC. Opinions on whether this draft should become a
> working group draft, and on the appropriate home for it, are
> solicited by 8 June 2007.
>=20
> Colin (as AVT co-chair)

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



From avt-bounces@ietf.org Tue Jun 05 11:07: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 1HvadX-0000c5-46; Tue, 05 Jun 2007 11:07:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvabC-0008WP-7M; Tue, 05 Jun 2007 11:05:30 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hvab9-0005eW-SC; Tue, 05 Jun 2007 11:05:30 -0400
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:62774
	helo=[192.168.0.4])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1Hvab7-00056S-V8; Tue, 05 Jun 2007 16:05:26 +0100
In-Reply-To: <05cf01c7a6ea$8cb552c0$c2f0200a@amer.cisco.com>
References: <05cf01c7a6ea$8cb552c0$c2f0200a@amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B830F329-78B5-491D-A64C-1B54A35C8364@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Tue, 5 Jun 2007 16:05:29 +0100
To: Lars Eggert <lars.eggert@nokia.com>,
 Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
X-Mailman-Approved-At: Tue, 05 Jun 2007 11:07:54 -0400
Cc: Godred Fairhurst <gorry@erg.abdn.ac.uk>,
	draft-ford-behave-app@tools.ietf.org,
	Behave WG <behave@ietf.org>, mmusic <mmusic@ietf.org>,
	Xavier Marjou <xavier.marjou@orange-ft.com>,
	Tom Taylor <tom.taylor@rogers.com>, Joerg Ott <jo@acm.org>,
	IETF AVT WG <avt@ietf.org>, Jean-Francois Mule <jf.mule@cablelabs.com>,
	tsvwg chair <tsvwg-chairs@tools.ietf.org>
Subject: [AVT] Re: [BEHAVE] RE: Moving draft-marjou-behave-app-rtp-keepalive
	to AVT
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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 4 Jun 2007, at 21:54, Dan Wing wrote:
>> On 2007-6-1, at 21:09, ext Dan Wing wrote:
>>> We need a document that consolidates NAT keepalive mechanisms for
>>> UDP-based protocols, most notably RTP (and, to a lesser extent,
>>> SIP).  Currently this is spread in various documents and there
>>> is no consolidated guidance to implementtors on the strength
>>> or weakness of various approaches.
>>
>> I'm wondering if it'd make sense to add this guidance as a
>> section in
>> http://tools.ietf.org/html/draft-ietf-tsvwg-udp-guidelines?
>
> I agree "send periodic UDP traffic" would be good in that
> document.  REQ-6 of draft-ford-behave-app-05 may provide the
> beginnings of some useful text (CC'ing the authors of that
> document).
>
> As with all applications on today's Internet, an RTP
> application needs to be robust and able to deal with whatever
> is sent to it, so perhaps you're right -- an application-
> specific keepalive document may well be overly specific and
> we should, rather, document what any UDP-based application
> should do to prevent middleboxes (such as NATs) from
> clobbering a flow.

The udp-guidelines draft should probably outline what sort of keep  
alive mechanism is needed, but the implementation is likely protocol  
specific, and should be done by the group designing that protocol, I  
think.

-- 
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 Jun 05 11:28: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 1HvaxZ-0000GB-I0; Tue, 05 Jun 2007 11:28:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvagN-0001Gb-0u; Tue, 05 Jun 2007 11:10:51 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvagL-0006bI-J4; Tue, 05 Jun 2007 11:10:50 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l55FAITB020666; Tue, 5 Jun 2007 18:10:37 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 5 Jun 2007 18:10:34 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 5 Jun 2007 18:10:33 +0300
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by
	esebh101.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 5 Jun 2007 18:10:33 +0300
Received: from [172.21.39.184] (esdhcp039184.research.nokia.com
	[172.21.39.184])
	by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l55FAVKK006865; Tue, 5 Jun 2007 18:10:31 +0300
In-Reply-To: <B830F329-78B5-491D-A64C-1B54A35C8364@csperkins.org>
References: <05cf01c7a6ea$8cb552c0$c2f0200a@amer.cisco.com>
	<B830F329-78B5-491D-A64C-1B54A35C8364@csperkins.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <73F566CA-38E1-4E83-958F-147D56283036@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
Date: Tue, 5 Jun 2007 18:10:19 +0300
To: "ext Colin Perkins" <csp@csperkins.org>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 05 Jun 2007 15:10:33.0232 (UTC)
	FILETIME=[A9A8E100:01C7A783]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
X-Mailman-Approved-At: Tue, 05 Jun 2007 11:28:36 -0400
Cc: Godred Fairhurst <gorry@erg.abdn.ac.uk>,
	draft-ford-behave-app@tools.ietf.org,
	Behave WG <behave@ietf.org>, mmusic <mmusic@ietf.org>,
	Xavier Marjou <xavier.marjou@orange-ft.com>,
	Tom Taylor <tom.taylor@rogers.com>, Joerg Ott <jo@acm.org>,
	IETF AVT WG <avt@ietf.org>, Jean-Francois Mule <jf.mule@cablelabs.com>,
	Dan Wing <dwing@cisco.com>, tsvwg chair <tsvwg-chairs@tools.ietf.org>
Subject: [AVT] Re: [BEHAVE] RE: Moving draft-marjou-behave-app-rtp-keepalive
	to AVT
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-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="===============0992222240=="
Errors-To: avt-bounces@ietf.org


--===============0992222240==
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-66-885556731;
	protocol="application/pkcs7-signature"


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

On 2007-6-5, at 18:05, ext Colin Perkins wrote:
> The udp-guidelines draft should probably outline what sort of keep  
> alive mechanism is needed, but the implementation is likely  
> protocol specific, and should be done by the group designing that  
> protocol, I think.

Makes sense to me.

Lars



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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGQDCCAvkw
ggJioAMCAQICEGtxkLFHQu1g67hlmYfwPuIwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDEwNDE2MTE1NFoXDTA4MDEwNDE2MTE1
NFowXDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2Vy
dDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9raWEuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEA26hjntVPZMiwh4d8tyuk9KiucvG92BVUGArk5zO1jhmq7tLFgU1mqcIg
VGumfQqjkAzIuh83kxIiqBrB05Wvxp85apwt4sUCvzMe8mQWzZZZYp0rBzwpOj+VC5pxsMRYtYW+
BaTFBEmvFr7D7C7roZUk0lDppS5SZFs4SQbEe9ykB9aeUf1iTiw2+ikyP2+JEYto14WYCoxFWbms
FbQ1uaaK+yn1WH2YHhyMfi0IOxuT0jtbsngjHJMpWIqq334zBhj+rPSUug47YBHr41FCDMHbbbjv
WbyTyDYneOW3WY8LY8bGWVlAknQGB7lgduShe6e0RI/7SL/VE6X27lM9LwIDAQABozIwMDAgBgNV
HREEGTAXgRVsYXJzLmVnZ2VydEBub2tpYS5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUF
AAOBgQCx3nxxTg/WowobVTRXBiXUEEZj4LBiunWbuAnR0UbJIgijvq3JbiJvZo2gUGiW9LPaHSBz
4oxT1VR/S/6O0a4e87oV5cOQm6ReB68o9rDfUzxHTwoCfv2wwMwBrXyzQMjyQK4Lt8siV41gmZpm
rSXMhjTJdd9uYYNoZKQLq+VM+TCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgG
A1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMg
RGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3
DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3
MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5
KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzAN
BgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9
fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+
uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMB
Af8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3
dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgG
A1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcP
f6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH
2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8x
ggMQMIIDDAIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAo
UHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ
a3GQsUdC7WDruGWZh/A+4jAJBgUrDgMCGgUAoIIBbzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcB
MBwGCSqGSIb3DQEJBTEPFw0wNzA2MDUxNTEwMjBaMCMGCSqGSIb3DQEJBDEWBBRbj05Hu7iAJBLQ
7bGQRy7UcNWDWzCBhQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0ECEGtxkLFHQu1g67hlmYfwPuIwgYcGCyqGSIb3DQEJEAILMXigdjBiMQsw
CQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UE
AxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEGtxkLFHQu1g67hlmYfwPuIw
DQYJKoZIhvcNAQEBBQAEggEAp1uwyPmKHMl8siPcSELxzVj6XfhFRWcVSxcaft3yD+5QNVuJ2rab
ASyq+rULH1fzS81a6jW+A9g4YaKnexx8PvHYWQ6UAF1FHfqmnPL7D2exGYUUxpfqCtXjgVYu1UaD
HUPRn50xzIm4bmQsnD59RBacjOQfNl3qEGsBjwJBYNpbcIEs3DR0XBIYqyqfntSuILFhQHaq1cHa
PptT12kZEcPQ4+l1/r+ObHhMTKvIdH3muQtiCEuLx5MmZRji8NkQO+S2pGvdBJGcfwkCRBDnKhN+
RE1JU7AzsnN1lhTf5Zr5GJ3rqT4PUaFj4/S/mHJEWfCrPJ+2Il/5NBRlbs55XwAAAAAAAA==

--Apple-Mail-66-885556731--


--===============0992222240==
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

--===============0992222240==--




From avt-bounces@ietf.org Tue Jun 05 11: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 1Hvb4E-0005RA-20; Tue, 05 Jun 2007 11:35:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hvb4C-0005Lw-Un; Tue, 05 Jun 2007 11:35:28 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hvb4C-0005Zz-Ce; Tue, 05 Jun 2007 11:35:28 -0400
Received: from relay5.apple.com (relay5.apple.com [17.128.113.35])
	by mail-out3.apple.com (Postfix) with ESMTP id AED427F511F;
	Tue,  5 Jun 2007 08:34:33 -0700 (PDT)
Received: from relay5.apple.com (unknown [127.0.0.1])
	by relay5.apple.com (Symantec Mail Security) with ESMTP id E632329C002; 
	Tue,  5 Jun 2007 08:35:27 -0700 (PDT)
X-AuditID: 11807123-9d01cbb000000a23-7a-466582bf36d2
Received: from [17.202.35.52] (unknown [17.151.66.148])
	by relay5.apple.com (Apple SCV relay) with ESMTP id 58E4830400E;
	Tue,  5 Jun 2007 08:35:27 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p0624081ac28b3247e073@[17.202.35.52]>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C049E76DA@IsrExch01.israel.polycom.com>
References: <144ED8561CE90C41A3E5908EDECE315C049E76DA@IsrExch01.israel.polycom.com>
Date: Tue, 5 Jun 2007 08:34:08 -0700
To: "Even, Roni" <roni.even@polycom.co.il>, mmusic <mmusic@ietf.org>,
	IETF AVT WG <avt@ietf.org>
From: Dave Singer <singer@apple.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Cc: "Clinton Priddle \(KI/EAB\)" <clinton.priddle@ericsson.com>
Subject: [AVT] RE: [MMUSIC] questions about grouping media streams in RTP and
 SDP  (RFC3388 etc), advice needed
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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 10:03  +0300 5/06/07, Even, Roni wrote:
>Dave,
>For layered encoding there is a proposal for a new grouping attribute in
>http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered-codec-03.tx
>t

I don't think this is a layered coding issue, either, alas.

>I looked at RFC3388 and I think that FID is not the answer to your
>requirement as you mentioned
>
>To me it looks like what you are looking for is a way to specify
>alternate offers.

No, these streams are not alternatives to each other in the regular 
sense.  Nor is this really used in offer/answer;  it's more an issue 
for multicast.  In multicast, you open the tune-in stream and the 
base stream, grab the first I-frame that arrives (in either) and then 
drop the tune-in stream.

Yes, we're aware that the recipient needs to be able to tell which is 
the base and which is the tune-in.

>If this is the case I have similar requirements and
>would be happy to support such work.
>
>You also need a way to give semantics to the "repair" stream, this can
>be done based on the content attribute from RFC 4796 or using a
>dependency attribute see in Schierl's draft. The mid tag is not enough
>for the receiver to know what you meant by this offer and which stream
>is the repair.
>
>Here is an example for a solution using a new Alternatives grouping
>attribute and giving semantics to the repair stream
>
>By using the grouping attribute in the offer you can know if the
>answerer understood the grouping since if he does not than he will send
>an answer with no a=group
>
>v=0
>o=bob 280744730 28977631 IN IP4 host.example.com
>s=
>t=0 0
>
>a=group:ALTS 1 2
>a=group:ALTS 1 3
>
>m=audio 6886 RTP/AVP 0
>c=IN IP6 2001:0600::1
>a=mid:1
>
>m=video 9000 RTP/AVP 100
>c=IN IP4 192.0.2.2
>a=rtpmap:100 H263-1998
>a=mid:2
>
>m=video 9002 RTP/AVP 101
>c=IN IP4 192.0.2.2
>a=rtpmap:101 H263-1998
>a=mid:3
>a=content:repair=2 or a=depend:repair=2
>
>
>Roni Even
>
>>  -----Original Message-----
>>  From: Dave Singer [mailto:singer@apple.com]
>>  Sent: Monday, June 04, 2007 7:19 PM
>>  To: mmusic; IETF AVT WG
>>  Cc: Clinton Priddle (KI/EAB)
>>  Subject: [MMUSIC] questions about grouping media streams in RTP and
>SDP
>>  (RFC3388 etc), advice needed
>>
>>  Hi
>>
>>  we have a need to group together two media streams, in the style of
>RFC
>>  3388 <http://www.ietf.org/rfc/rfc3388.txt> but we're unsure whether an
>>  existing group type is suitable or not, and if it's not, we'd like to
>>  agree on a new one, and document it (presumably in an RFC).
>>
>>  What we have is a normal media stream, and a separate 'repair' or
>>  'entry' stream, that can be used when tuning in, or after loss, but is
>>  otherwise un-needed.  An example might be a video stream with a low
>>  I-frame interval (say every 15 seconds), with a repair stream which
>has
>>  only I-frames that are equivalent to the time-parallel non-I frame, at
>a
>>  frequency of say 1 per second.
>>
>>  It's not clear to us whether this is "one media flow" in the sense of
>>  FID, or not.  The example offers AMR and GSM audio, which are
>>  alternatives, and DTMF tones along with audio, which are supplementary
>>  to each other.  Perhaps we fall afoul of this restriction:
>>
>>  "An application that encodes the same media using different codecs
>>  simultaneously MUST NOT use FID to group those media lines."
>>
>>  or this one, for layered encoding:
>>
>>  "FID MUST NOT be used to group "m" lines that do not represent the
>same
>>  information."  (Though how DTMF tones and their associated audio pass
>>  this test is not clear).
>>
>>  Nor is it clear that the FEC group of RFC 4756 is right, either.  For
>a
>>  start, we may wish to use this new ID in combination with FEC, and
>>  secondly this tune-in stream has different characteristics.  For
>>  example, one can typically ignore all FEC and (as long as there are no
>>  errors) decode the stream correctly.  Ignoring the tune-in stream
>  > entirely may mean that you will never find a tune-in point, making the
>>  normal stream useless.
>>
>>  So, can we use FID for associating a repair stream with its base (we
>tag
>>  the streams so we know which is which, of course)?
>>
>>  p.s. RFC 4756 claims in the IANA section that the FEC group is
>>  registered under SDP characteristics, but actually I can find no
>>  registry anywhere in IANA of group types.
>>
>>
>>  --
>>  David Singer
>>  Apple/QuickTime
>>
>>  _______________________________________________
>>  mmusic mailing list
>>  mmusic@ietf.org
>>  https://www1.ietf.org/mailman/listinfo/mmusic


-- 
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 Jun 05 15:50: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 1Hvf2f-0007En-5q; Tue, 05 Jun 2007 15:50:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hvf2Z-00070M-IJ; Tue, 05 Jun 2007 15:50:04 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hvf2Y-0002Yx-AD; Tue, 05 Jun 2007 15:50:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 4672232A7D;
	Tue,  5 Jun 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Hvf2Y-0005sk-54; Tue, 05 Jun 2007 15:50: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: <E1Hvf2Y-0005sk-54@stiedprstage1.ietf.org>
Date: Tue, 05 Jun 2007 15:50: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-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		: RTP Payload Format for Adaptive TRansform Acoustic Coding (ATRAC) Family
	Author(s)	: M. Romaine, J. Matsumoto
	Filename	: draft-ietf-avt-rtp-atrac-family-08.txt
	Pages		: 24
	Date		: 2007-6-5
	
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-08.txt

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

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

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

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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-avt-rtp-atrac-family-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-6-5144819.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2007-6-5144819.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 Jun 06 02:33: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 1Hvp5O-0004VQ-3e; Wed, 06 Jun 2007 02:33:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hvp5L-0004KH-FT; Wed, 06 Jun 2007 02:33:35 -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 1Hvp5J-0004r1-2W; Wed, 06 Jun 2007 02:33:35 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 6 Jun 2007 09:34:12 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C049E78C5@IsrExch01.israel.polycom.com>
In-Reply-To: <p0624081ac28b3247e073@[17.202.35.52]>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] questions about grouping media streams in RTP and SDP
	(RFC3388 etc), advice needed
Thread-Index: Acenh0L0V4NbyfevQQuzIOSQ/dMA4AAevHPg
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Dave Singer" <singer@apple.com>, "mmusic" <mmusic@ietf.org>,
	"IETF AVT WG" <avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 17e5edc4dfd335965c1d21372171c01c
Cc: "Clinton Priddle \(KI/EAB\)" <clinton.priddle@ericsson.com>
Subject: [AVT] RE: [MMUSIC] questions about grouping media streams in RTP
	and SDP (RFC3388 etc), advice needed
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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,
 From your response:

"No, these streams are not alternatives to each other in the regular
sense.  Nor is this really used in offer/answer;  it's more an issue for
multicast.  In multicast, you open the tune-in stream and the base
stream, grab the first I-frame that arrives (in either) and then drop
the tune-in stream.

Yes, we're aware that the recipient needs to be able to tell which is
the base and which is the tune-in."

Reading your application I will try to generalize it. To me you have two
streams that have a relationship and there is semantics for the relation
between the streams.

You say that typically a user will only use the tune-in stream for
synchronization; I would think that this can happen when joining the
session or when losing synchronization.=20
In the general case these two streams are coming from the same source
and the user may use one or the other. This is why I called them
alternate streams

After specifying the two streams (as alternate since the receiver may
chose one or the other), you want to apply a specific semantics to the
content of one stream (a repair stream). Again, I think that we need to
specify the general mechanism for semantics to enable implementations
from different vendors to understand what to do with the streams coming
from the same source.

In the current work at MMUSIC, the Label attribute (RFC 4574) define
tags to a stream but with no semantics. The content attribute RFC 4796
defines semantic to a stream. I think that we now have a requirement for
adding semantics to the relationship between streams; examples are the
repair streams and the layered codecs.

I think that by using grouping and dependency attributes we can define a
general framework that will enable these general requirements and use
them for the specific applications like repair stream, layered codecs
and just alternate offers.

Roni



> -----Original Message-----
> From: Dave Singer [mailto:singer@apple.com]
> Sent: Tuesday, June 05, 2007 6:34 PM
> To: Even, Roni; mmusic; IETF AVT WG
> Cc: Clinton Priddle (KI/EAB)
> Subject: RE: [MMUSIC] questions about grouping media streams in RTP
and
> SDP (RFC3388 etc), advice needed
>=20
> At 10:03  +0300 5/06/07, Even, Roni wrote:
> >Dave,
> >For layered encoding there is a proposal for a new grouping attribute
in
>
>http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered-codec-03.t
x
> >t
>=20
> I don't think this is a layered coding issue, either, alas.
>=20
> >I looked at RFC3388 and I think that FID is not the answer to your
> >requirement as you mentioned
> >
> >To me it looks like what you are looking for is a way to specify
> >alternate offers.
>=20
> No, these streams are not alternatives to each other in the regular
> sense.  Nor is this really used in offer/answer;  it's more an issue
> for multicast.  In multicast, you open the tune-in stream and the
> base stream, grab the first I-frame that arrives (in either) and then
> drop the tune-in stream.
>=20
> Yes, we're aware that the recipient needs to be able to tell which is
> the base and which is the tune-in.
>=20
> >If this is the case I have similar requirements and
> >would be happy to support such work.
> >
> >You also need a way to give semantics to the "repair" stream, this
can
> >be done based on the content attribute from RFC 4796 or using a
> >dependency attribute see in Schierl's draft. The mid tag is not
enough
> >for the receiver to know what you meant by this offer and which
stream
> >is the repair.
> >
> >Here is an example for a solution using a new Alternatives grouping
> >attribute and giving semantics to the repair stream
> >
> >By using the grouping attribute in the offer you can know if the
> >answerer understood the grouping since if he does not than he will
send
> >an answer with no a=3Dgroup
> >
> >v=3D0
> >o=3Dbob 280744730 28977631 IN IP4 host.example.com
> >s=3D
> >t=3D0 0
> >
> >a=3Dgroup:ALTS 1 2
> >a=3Dgroup:ALTS 1 3
> >
> >m=3Daudio 6886 RTP/AVP 0
> >c=3DIN IP6 2001:0600::1
> >a=3Dmid:1
> >
> >m=3Dvideo 9000 RTP/AVP 100
> >c=3DIN IP4 192.0.2.2
> >a=3Drtpmap:100 H263-1998
> >a=3Dmid:2
> >
> >m=3Dvideo 9002 RTP/AVP 101
> >c=3DIN IP4 192.0.2.2
> >a=3Drtpmap:101 H263-1998
> >a=3Dmid:3
> >a=3Dcontent:repair=3D2 or a=3Ddepend:repair=3D2
> >
> >
> >Roni Even
> >
> >>  -----Original Message-----
> >>  From: Dave Singer [mailto:singer@apple.com]
> >>  Sent: Monday, June 04, 2007 7:19 PM
> >>  To: mmusic; IETF AVT WG
> >>  Cc: Clinton Priddle (KI/EAB)
> >>  Subject: [MMUSIC] questions about grouping media streams in RTP
and
> >SDP
> >>  (RFC3388 etc), advice needed
> >>
> >>  Hi
> >>
> >>  we have a need to group together two media streams, in the style
of
> >RFC
> >>  3388 <http://www.ietf.org/rfc/rfc3388.txt> but we're unsure
whether an
> >>  existing group type is suitable or not, and if it's not, we'd like
to
> >>  agree on a new one, and document it (presumably in an RFC).
> >>
> >>  What we have is a normal media stream, and a separate 'repair' or
> >>  'entry' stream, that can be used when tuning in, or after loss,
but is
> >>  otherwise un-needed.  An example might be a video stream with a
low
> >>  I-frame interval (say every 15 seconds), with a repair stream
which
> >has
> >>  only I-frames that are equivalent to the time-parallel non-I
frame, at
> >a
> >>  frequency of say 1 per second.
> >>
> >>  It's not clear to us whether this is "one media flow" in the sense
of
> >>  FID, or not.  The example offers AMR and GSM audio, which are
> >>  alternatives, and DTMF tones along with audio, which are
supplementary
> >>  to each other.  Perhaps we fall afoul of this restriction:
> >>
> >>  "An application that encodes the same media using different codecs
> >>  simultaneously MUST NOT use FID to group those media lines."
> >>
> >>  or this one, for layered encoding:
> >>
> >>  "FID MUST NOT be used to group "m" lines that do not represent the
> >same
> >>  information."  (Though how DTMF tones and their associated audio
pass
> >>  this test is not clear).
> >>
> >>  Nor is it clear that the FEC group of RFC 4756 is right, either.
For
> >a
> >>  start, we may wish to use this new ID in combination with FEC, and
> >>  secondly this tune-in stream has different characteristics.  For
> >>  example, one can typically ignore all FEC and (as long as there
are no
> >>  errors) decode the stream correctly.  Ignoring the tune-in stream
> >  > entirely may mean that you will never find a tune-in point,
making
> the
> >>  normal stream useless.
> >>
> >>  So, can we use FID for associating a repair stream with its base
(we
> >tag
> >>  the streams so we know which is which, of course)?
> >>
> >>  p.s. RFC 4756 claims in the IANA section that the FEC group is
> >>  registered under SDP characteristics, but actually I can find no
> >>  registry anywhere in IANA of group types.
> >>
> >>
> >>  --
> >>  David Singer
> >>  Apple/QuickTime
> >>
> >>  _______________________________________________
> >>  mmusic mailing list
> >>  mmusic@ietf.org
> >>  https://www1.ietf.org/mailman/listinfo/mmusic
>=20
>=20
> --
> 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 Jun 06 04:45: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 1Hvr92-0003Px-5E; Wed, 06 Jun 2007 04:45:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hvr90-0003O3-3r
	for avt@ietf.org; Wed, 06 Jun 2007 04:45:30 -0400
Received: from mgw3.sony.co.jp ([137.153.0.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hvr8z-0003xc-4t
	for avt@ietf.org; Wed, 06 Jun 2007 04:45:30 -0400
Received: from mail34.sony.co.jp ([43.0.1.230])
Received: from mail34.sony.co.jp (localhost [127.0.0.1])
	by mail34.sony.co.jp (R8/Sony) with ESMTP id l568jRmf008977
	for <avt@ietf.org>; Wed, 6 Jun 2007 17:45:27 +0900 (JST)
Received: from jptkyxim02.jp.sony.com (jptkyxim02.jp.sony.com [43.15.17.88])
	by mail34.sony.co.jp (R8/Sony) with ESMTP id l568jRe3008973
	for <avt@ietf.org>; Wed, 6 Jun 2007 17:45:27 +0900 (JST)
Received: from jptkyxwa03.jp.sony.com ([43.15.31.3]) by jptkyxim02.jp.sony.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 6 Jun 2007 17:45:27 +0900
Received: from avhta.av.crl.sony.co.jp ([43.4.241.227]) by
	jptkyxwa03.jp.sony.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 6 Jun 2007 17:45:25 +0900
Message-Id: <5.1.1.9.2.20070606172828.047a43a0@pop.jp.sony.com>
X-Sender: jp\jp05992@pop.jp.sony.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1-Jr4
Date: Wed, 06 Jun 2007 17:45:20 +0900
To: avt@ietf.org
From: Mitsuyuki Hatanaka <actech@jp.sony.com>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-atrac-family-08.txt 
In-Reply-To: <E1Hvf2Y-0005sk-54@stiedprstage1.ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Jun 2007 08:45:25.0746 (UTC)
	FILETIME=[06F01520:01C7A817]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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-08.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 issue that Mr.Perkins pointed out 
(refer to: http://www1.ietf.org/mail-archive/web/avt/current/msg06933.html).
In addition, we changed some items regarding on SDP usage and definition.

The revised points are:
(1) expanded the acronym "ATRAC" to "Adaptive TRansform Acoustic Coding" in title.
(2) moved the sentense in Section 1 which describes about codec details to Section 3.
(3) moved the sentense in Section 4.5 which decsribes about global structure of ATRAC payload 
 to Section 5.1, and re-ordering the section number.
(4) appended more precise description about the parameter in RTP header.
(5) removed the description about "FrameOffset" because it is not used in current
 version of this draft.
(6) corrected the referenced figure number in section 5.2.3.1.
(7) modified the Figure 7 and added the Figure 8 to explain the redundant data structure.
(8) changed the referenced document number from RFC 2327 to RFC 4566 in section 7.
(9) changed the term from "unspecified" to "unknown" in section 7.1 to 7.3.
(10) added the unit of "kbps" for bit-rate parameter in section 7.1 to 7.3.
(11) changed the explanation of ptime and  maxptime in section 7.1 to 7.3.
(12) corrected the referenced figure number for ChannelID in section 7.2 and 7.3.
(13) changed the explanation about "baseLayer" in Section 7.3.
(14) changed the definition of "blockLength" of SDP in section 7.3 and 7.5.3, and 
 offer/answer example description for lossless codec in section 7.9 .
(15) corrected the number of media types from "two" to "three" in section 8.
 
Best Regards,
Mitsuyuki Hatanaka

At 15:50 07/06/05 -0400, you 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 Adaptive TRansform Acoustic Coding (ATRAC) 
>Family
>	Author(s)	: M. Romaine, J. Matsumoto
>	Filename	: draft-ietf-avt-rtp-atrac-family-08.txt
>	Pages		: 24
>	Date		: 2007-6-5
>	
>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-08.txt


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



From avt-bounces@ietf.org Wed Jun 06 05:38: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 1HvryD-0006rH-Mz; Wed, 06 Jun 2007 05:38:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvryB-0006qf-Oi
	for avt@ietf.org; Wed, 06 Jun 2007 05:38:24 -0400
Received: from ns4.sony.co.jp ([137.153.0.44])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvryA-0004Xn-0z
	for avt@ietf.org; Wed, 06 Jun 2007 05:38:23 -0400
Received: from mail7.sony.co.jp ([43.0.1.209])
Received: from mail7.sony.co.jp (localhost [127.0.0.1])
	by mail7.sony.co.jp (R8/Sony) with ESMTP id l569cFW5016496;
	Wed, 6 Jun 2007 18:38:15 +0900 (JST)
Received: from bourbon.sm.sony.co.jp ([43.13.14.16])
	by mail7.sony.co.jp (R8/Sony) with ESMTP id l569cFVR016484;
	Wed, 6 Jun 2007 18:38:15 +0900 (JST)
Received: from [43.13.14.197] ([43.13.14.197])
	by bourbon.sm.sony.co.jp (8.14.1/8.14.1) with ESMTP id l569vnHF023081; 
	Wed, 6 Jun 2007 18:57:49 +0900
Message-ID: <46668077.1070003@sm.sony.co.jp>
Date: Wed, 06 Jun 2007 18:37:59 +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: <7634542FB03DC747813D67560802AEED9EB8C2@rennsmail05.eu.thmulti.com>
	<5D82C04F-D389-4C9C-9564-64391254BB78@csperkins.org>
In-Reply-To: <5D82C04F-D389-4C9C-9564-64391254BB78@csperkins.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: Boudani Ali <Ali.Boudani@thomson.net>, 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,

We, authors, think all issues would be solved.
How should we do next ?


About timestamp issues, I can understand Dave's claim,
but I think most case we can imagine now may be covered
by 90 kHz clock rate.

Even if it occurs to send media files with another clock rate,
all senders should convert its clock rate to 90 kHz in some way,
which is beyond the scope of the draft.

So, I don't feel it is necessary to change the draft.

Best Regards,

Futemma

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



From avt-bounces@ietf.org Wed Jun 06 11:58: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 1HvxtJ-0000Q5-6G; Wed, 06 Jun 2007 11:57:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvxtG-0000Pt-CM
	for avt@ietf.org; Wed, 06 Jun 2007 11:57:43 -0400
Received: from smtp108.rog.mail.re2.yahoo.com ([68.142.225.206])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HvxtE-0006Yq-2G
	for avt@ietf.org; Wed, 06 Jun 2007 11:57:42 -0400
Received: (qmail 23468 invoked from network); 6 Jun 2007 15:57:39 -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=WBtKvOdtR8pElgmpfmXyyENqHLA7dK16+cZ/N+2Kb0CC1vrb0C8xhKQCxi0t/ZNytwHtpinKz4BXdCZmRJ2EwM45+bCenWdCxAKPUKTF3pQps8hsogYu14zgNSAGVvWle1sj0aWrS7HotfJfpWVUQWslj1YYFNEXDfLoVsPYdMQ=
	; 
Received: from unknown (HELO ?192.168.0.100?)
	(tom.taylor@rogers.com@74.105.35.229 with plain)
	by smtp108.rog.mail.re2.yahoo.com with SMTP; 6 Jun 2007 15:57:39 -0000
X-YMail-OSG: jCkKcyAVM1n4o3YuLJleIxixlh2FdpX3dj.tvcpUEH56Txh3xs8NCczxINFStaDRHg--
Message-ID: <4666D981.5060008@rogers.com>
Date: Wed, 06 Jun 2007 11:57:53 -0400
From: Tom Taylor <tom.taylor@rogers.com>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: 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: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Subject: [AVT] [Fwd: Last Call: draft-ietf-dccp-rtp (RTP and the Datagram
 Congestion Control Protocol (DCCP)) to Proposed Standard]
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

FYI

-------- Original Message --------
Subject: Last Call: draft-ietf-dccp-rtp (RTP and the Datagram Congestion 
  Control Protocol (DCCP)) to Proposed Standard
Date: Wed, 06 Jun 2007 10:18:36 -0400
From: The IESG <iesg-secretary@ietf.org>
Reply-To: ietf@ietf.org
To: IETF-Announce <ietf-announce@ietf.org>
CC: dccp@ietf.org

The IESG has received a request from the Datagram Congestion Control
Protocol WG (dccp) to consider the following document:

- 'RTP and the Datagram Congestion Control Protocol (DCCP) '
    <draft-ietf-dccp-rtp-06.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2007-06-20. 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-dccp-rtp-06.txt


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


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



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



From avt-bounces@ietf.org Wed Jun 06 12:17: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 1HvyCX-0002Xq-4O; Wed, 06 Jun 2007 12:17:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvyCV-0002Xk-WB
	for avt@ietf.org; Wed, 06 Jun 2007 12:17:36 -0400
Received: from smtp02.lnh.mail.rcn.net ([207.172.157.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvyCV-0003UF-LJ
	for avt@ietf.org; Wed, 06 Jun 2007 12:17:35 -0400
Received: from mr02.lnh.mail.rcn.net ([207.172.157.22])
	by smtp02.lnh.mail.rcn.net with ESMTP; 06 Jun 2007 12:17:35 -0400
Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11])
	by mr02.lnh.mail.rcn.net (MOS 3.8.3-GA) with ESMTP id NKK82436;
	Wed, 6 Jun 2007 12:17:35 -0400 (EDT)
Received: from 162-144-2.cortland.com.144.162.209.in-addr.arpa (HELO
	erols.com) ([209.162.144.2])
	by smtp01.lnh.mail.rcn.net with ESMTP; 06 Jun 2007 12:17:29 -0400
Message-ID: <4666DD9A.4161A698@erols.com>
Date: Wed, 06 Jun 2007 09:15:22 -0700
From: Chuck Harrison <cfharr@erols.com>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
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>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Junkmail-Whitelist: YES (by domain whitelist at mr02.lnh.mail.rcn.net)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: Boudani Ali <Ali.Boudani@thomson.net>, Dave Singer <singer@apple.com>,
	Le Dantec Claude <Claude.Le-Dantec@thomson.net>, 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

Suppose

1. A compliant J2K receiver MUST accept 90kHz timestamps
2. A compliant J2K receiver MAY accept other timestamp rates
3. A compliant J2K sender SHOULD transmit 90kHz timestamps
4. The RFC warns that senders violating the SHOULD of item 3
    risk interoperability problems.

Then Dave is permitted to send a stream between matching
compliant applications using an 89999 Hz media clock, 12857
ticks per frame, exactly 7 frames per second. Or: a 70000 Hz
clock, 10000 ticks per frame.

An alternate video source, playing nice and sending at
90 kHz, is guaranteed to be able to talk successfully to
Dave's receiver application.

Dave's special source may not be able to send successfully
to the majority of J2K receiver applications.

Is this a high enough level of interoperability?

Regards,
  Chuck


Magnus Westerlund wrote:
> 
> Dave Singer skrev:
> > RTP payload formats may be used for all sorts of purposes and (varying)
> > frame rates.  I disagree that we in the AVT group 'know best' and that
> > any payload format should mandate a particular clock frequency.  It's
> > perfectly legitimate for me to send material at say 7 fps, and 90000 is
> > not suitable for that -- the frames would appear to have varying
> > duration, and there is risk of round-off.
> 
> I know that AVT is not knowing best. However, I asked this questions so
> that we could be educated and take an informed decision. However I think
> there are definitely an trade-off between using a fixed timestamp clock
> rate and allow any rate to be used.
> 
> >
> > Any payload format should recommend ('should') something, but mention
> > that other possibilities exist.
> 
> As this have shown to create problems in implementations. For example it
> showed up in an interop test creating problems for the packet-based
> streaming service where people sent MPEG-4 content using RFC3016
> packetization using non 90kHz clock. This occurs because the wiggle room
> was given and most implementors do no understand the implications of
> using another clock. Sure, we didn't document well enough all the
> downsides with choosing something else. Also we really should provide
> some lower and upper boundaries on these values.
> 
> >
> > Very high clock frequencies (e.g. 27 MHz) bring their own problems
> > (frequent wrap-around being one).  For a given program, it is usually
> > the case that one can easily find a number that
> > a) doesn't wrap around too often
> > b) is high enough for accurate jitter calculations
> > c) is an integer multiple of the frame rate, or, for variable frame
> > rate, allows each frame to have an integer timestamp which has not been
> > rounded-off
> >
> 
> Yes, and that have so far been 90kHz to satisfy this. If there are cases
> when this is not true I would like to know about them. But I think we
> should be clear on why we are allowing any wiggle room at all. 90kHz do
> support quite a lot of different frame rates. I am not saying that there
> doesn't exist such rate. But given a blank card on what rate to use adds
> complexities. If we rather could enumerate a small set of possible rates
> to cover the known cases that would make me much happier.
> 
> But Ali's example is not something that can be solved using the RTP
> timestamp rate if I understand this correctly. Simply because 27 MHz
> gets us into the problem with frequent wrap around.
> 
> 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

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



From avt-bounces@ietf.org Wed Jun 06 16:11: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 1Hw1rC-0002Uj-VJ; Wed, 06 Jun 2007 16:11:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hw1dA-0005pf-NC; Wed, 06 Jun 2007 15:57:20 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hw1W6-0004Pl-Ak; Wed, 06 Jun 2007 15:50:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 4A53A328B9;
	Wed,  6 Jun 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Hw1W6-0003xh-5e; Wed, 06 Jun 2007 15:50: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: <E1Hw1W6-0003xh-5e@stiedprstage1.ietf.org>
Date: Wed, 06 Jun 2007 15:50: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-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		: RTP Payload Format for Adaptive TRansform Acoustic Coding (ATRAC) Family
	Author(s)	: J. Matsumoto, M. Hatanaka
	Filename	: draft-ietf-avt-rtp-atrac-family-08.txt
	Pages		: 24
	Date		: 2007-6-5
	
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-08.txt

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

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

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

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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-avt-rtp-atrac-family-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-6-6123244.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2007-6-6123244.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 Jun 07 07:24: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 1HwG68-0004qP-UW; Thu, 07 Jun 2007 07:24:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwG67-0004q4-4C
	for avt@ietf.org; Thu, 07 Jun 2007 07:24:11 -0400
Received: from lon-del-02.spheriq.net ([195.46.50.98])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwG64-0008BR-JY
	for avt@ietf.org; Thu, 07 Jun 2007 07:24:11 -0400
Received: from lon-out-02.spheriq.net ([195.46.50.130])
	by lon-del-02.spheriq.net with ESMTP id l57BP2vk020443
	for <avt@ietf.org>; Thu, 7 Jun 2007 12:25:02 +0100
Received: from lon-cus-01.spheriq.net (lon-cus-01.spheriq.net [195.46.50.37])
	by lon-out-02.spheriq.net with ESMTP id l57BO5xj031245
	for <avt@ietf.org>; Thu, 7 Jun 2007 11:24:07 GMT
Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35])
	by lon-cus-01.spheriq.net with ESMTP id l57BO3nK001954
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK);
	Thu, 7 Jun 2007 11:24:04 GMT
Received: from zeta.dmz-eu.st.com (ns2.st.com [164.129.230.9])
	by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP
	id C3564DA43; Thu,  7 Jun 2007 11:24:02 +0000 (GMT)
Received: from mail4.agr.st.com (mail4.agr.st.com [164.130.4.70])
	by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 2F9754BE92;
	Thu,  7 Jun 2007 11:24:02 +0000 (GMT)
Received: from [10.50.13.10] (agr2261.agr.st.com [10.50.13.10])
	by mail4.agr.st.com (MOS 3.7.5a-GA)
	with ESMTP id BEW00847 (AUTH "andrea vitali");
	Thu, 7 Jun 2007 13:24:00 +0200 (CEST)
Message-ID: <4667EAD0.9020803@st.com>
Date: Thu, 07 Jun 2007 13:24:00 +0200
From: Andrea Lorenzo VITALI <andrea.vitali@st.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Dave Singer <singer@apple.com>
Subject: Re: [AVT] questions about grouping media streams in RTP and SDP
	(RFC3388 etc), advice needed
References: <465C0342.3010602@nsn.com>	<7374777208BDC7449D5620EF9423256704991181@esealmw113.eemea.ericsson.se>	<289643F2-2529-4C24-B430-B9967B5DADD4@csperkins.org>
	<p0624081dc289eb45c3bf@[17.202.35.52]>
In-Reply-To: <p0624081dc289eb45c3bf@[17.202.35.52]>
X-Enigmail-Version: 0.94.0.0
Content-Type: multipart/mixed; boundary="------------010307080304080600030909"
X-O-Spoofed: Not Scanned
X-O-General-Status: No
X-O-Spam1-Status: Not Scanned
X-O-Spam2-Status: Not Scanned
X-O-URL-Status: Not Scanned
X-O-Virus1-Status: No
X-O-Virus2-Status: Not Scanned
X-O-Virus3-Status: No
X-O-Virus4-Status: No
X-O-Virus5-Status: Not Scanned
X-O-Image-Status: Not Scanned
X-O-Attach-Status: Not Scanned
X-SpheriQ-Ver: 4.2.04
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Cc: "Clinton Priddle \(KI/EAB\)" <clinton.priddle@ericsson.com>,
	mmusic <mmusic@ietf.org>, IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

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


RFC3388 tagging/grouping cannot be used

  - simultaneous encoding is explicitly forbidden (no Multiple
Description Coding)

  - grouping of layers explicitly forbidden (no Layered Coding)


I talked about this in my presentation at IETF (page 6):
http://www3.ietf.org/proceedings/05nov/slides/avt-3.pdf

My presentation was about standard-compatible Multiple Description
Coding (MDC). You can find the draft here:
http://tools.ietf.org/tools/rfcmarkup/rfcmarkup.cgi?draft=draft-vitali-ietf-avt-mdc-lc-00.txt

Your scheme is in fact an unbalanced multiple description coding scheme,
isn't it? You transmit the full video and a low-resolution video to be
used for concealment (1+1/4).

The question of dependency between streams has also been raised for the
new Scalable Video Codec (SVC).

  Andrea


Dave Singer wrote:
> Hi
> 
> we have a need to group together two media streams, in the style of RFC
> 3388 <http://www.ietf.org/rfc/rfc3388.txt> but we're unsure whether an
> existing group type is suitable or not, and if it's not, we'd like to
> agree on a new one, and document it (presumably in an RFC).
> 
> What we have is a normal media stream, and a separate 'repair' or
> 'entry' stream, that can be used when tuning in, or after loss, but is
> otherwise un-needed.  An example might be a video stream with a low
> I-frame interval (say every 15 seconds), with a repair stream which has
> only I-frames that are equivalent to the time-parallel non-I frame, at a
> frequency of say 1 per second.
> 
> It's not clear to us whether this is "one media flow" in the sense of
> FID, or not.  The example offers AMR and GSM audio, which are
> alternatives, and DTMF tones along with audio, which are supplementary
> to each other.  Perhaps we fall afoul of this restriction:
> 
> "An application that encodes the same media using different codecs
> simultaneously MUST NOT use FID to group those media lines."
> 
> or this one, for layered encoding:
> 
> "FID MUST NOT be used to group "m" lines that do not represent the same
> information."  (Though how DTMF tones and their associated audio pass
> this test is not clear).
> 
> Nor is it clear that the FEC group of RFC 4756 is right, either.  For a
> start, we may wish to use this new ID in combination with FEC, and
> secondly this tune-in stream has different characteristics.  For
> example, one can typically ignore all FEC and (as long as there are no
> errors) decode the stream correctly.  Ignoring the tune-in stream
> entirely may mean that you will never find a tune-in point, making the
> normal stream useless.
> 
> So, can we use FID for associating a repair stream with its base (we tag
> the streams so we know which is which, of course)?
> 
> p.s. RFC 4756 claims in the IANA section that the FEC group is
> registered under SDP characteristics, but actually I can find no
> registry anywhere in IANA of group types.
> 
> 

-- 
 ______________________________________________________________

  Andrea VITALI                            andrea.vitali@st.com

  tel (+39) 039 603 7244             mobile (+39) 347 93 08 433
  fax (+39) 039 603 6129

  STMicroelectronics
  Centro Direzionale COLLEONI - Palazzo "DIALETTICA"
  20041 Agrate Brianza (MI) ITALY
 ______________________________________________________________

--------------010307080304080600030909
Content-Type: text/x-vcard; charset=utf-8;
 name="andrea.vitali.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="andrea.vitali.vcf"

begin:vcard
fn:Andrea Vitali
n:Vitali;Andrea
email;internet:andrea.vitali@st.com
tel;work:+39 039 603 7244
tel;fax:+39 039 603 6129
tel;home:+39 035 34 08 14
tel;cell:+39 347 93 08 433
x-mozilla-html:FALSE
version:2.1
end:vcard


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

--------------010307080304080600030909--




From avt-bounces@ietf.org Thu Jun 07 08:36: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 1HwHED-0002PB-AJ; Thu, 07 Jun 2007 08:36:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwHEB-0002P6-U2
	for avt@ietf.org; Thu, 07 Jun 2007 08:36:35 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwHEB-0000F2-9Y
	for avt@ietf.org; Thu, 07 Jun 2007 08:36:35 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	99978200CA for <avt@ietf.org>; Thu,  7 Jun 2007 14:36:34 +0200 (CEST)
X-AuditID: c1b4fb3e-b01efbb0000061ca-ed-4667fbd24177 
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	708E020224 for <avt@ietf.org>; Thu,  7 Jun 2007 14:36:34 +0200 (CEST)
Received: from eseldmw101.eemea.ericsson.se ([136.225.228.103]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 7 Jun 2007 14:36:34 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 7 Jun 2007 14:36:33 +0200
Message-ID: <DA392F15190F9D40BF916AD7146E972E06802F2D@eseldmw101.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: 'States' in RFC4733
Thread-Index: AcepAHswNKQv4wRnQAyL5oJlW5NAnw==
From: "Gert Olsson (LD/EAB)" <gert.olsson@ericsson.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 07 Jun 2007 12:36:34.0043 (UTC)
	FILETIME=[7B8004B0:01C7A900]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176
Subject: [AVT] 'States' in RFC4733
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-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="===============0738809369=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0738809369==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7A900.7B83615E"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7A900.7B83615E
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,
I'm trying to understand RFC4733, the 'named events' part mostly chapter
2 and wonder about the definition of 'state'. For a state you send with
duration=3D0, but this is not the definition of 'state', is it?
For DTMF,  is it 'Type' in table 3 that defines that DTMF events are not
'states' or what ?

3.2.  DTMF Events

   Table 3 shows the DTMF-related event codes within the telephone-event
   payload format.  The DTMF digits 0-9 and * and # are commonly
   supported.  DTMF digits A through D are less frequently encountered,
   typically in special applications such as military networks.

                    +-------+--------+------+---------+
                    | Event | Code   | Type | Volume? |
                    +-------+--------+------+---------+
                    | 0--9  | 0--9   | tone | yes     |
                    | *     | 10     | tone | yes     |
                    | #     | 11     | tone | yes     |
                    | A--D  | 12--15 | tone | yes     |
                    +-------+--------+------+---------+

                        Table 3: DTMF Named Events


(In 1.4.  Events, States, Tone Patterns, and Voice-Encoded Tones
'states' are only mentioned in the heading nowhere in the text,
something missing ?? )

BR

/GO
__________________________________________________________________|
Gert Olsson   /  phone: +46 46  23 24 97   /  e-mail:
gert.olsson@ericsson.com
Ericsson AB - Business Unit Mobile Platforms, SE-221 83  Lund, Sweden


------_=_NextPart_001_01C7A900.7B83615E
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>'States' in RFC4733</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT COLOR=3D"#800000" FACE=3D"Comic Sans MS">Hi,</FONT>

<BR><FONT COLOR=3D"#800000" FACE=3D"Comic Sans MS">I'm trying to =
understand RFC4733, the 'named events' part mostly chapter 2 and wonder =
about the definition of 'state'. For a state you send with duration=3D0, =
but this is not the definition of 'state', is it?</FONT></P>

<P><FONT COLOR=3D"#800000" FACE=3D"Comic Sans MS">For DTMF,&nbsp; is it =
'Type' in table 3 that defines that DTMF events are<I> not</I> 'states' =
or what ?</FONT>
</P>

<P><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier New">3.2.&nbsp; DTMF =
Events</FONT>
</P>

<P><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier New">&nbsp;&nbsp; =
Table 3 shows the DTMF-related event codes within the =
telephone-event</FONT>

<BR><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier New">&nbsp;&nbsp; =
payload format.&nbsp; The DTMF digits 0-9 and * and # are =
commonly</FONT>

<BR><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier New">&nbsp;&nbsp; =
supported.&nbsp; DTMF digits A through D are less frequently =
encountered,</FONT>

<BR><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier New">&nbsp;&nbsp; =
typically in special applications such as military networks.</FONT>
</P>

<P><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier =
New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
+-------+--------+------+---------+</FONT>

<BR><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier =
New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Event | =
Code&nbsp;&nbsp; | Type | Volume? |</FONT>

<BR><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier =
New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
+-------+--------+------+---------+</FONT>

<BR><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier =
New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | 0--9&nbsp; | =
0--9&nbsp;&nbsp; | tone | yes&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>

<BR><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier =
New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
*&nbsp;&nbsp;&nbsp;&nbsp; | 10&nbsp;&nbsp;&nbsp;&nbsp; | tone | =
yes&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>

<BR><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier =
New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
#&nbsp;&nbsp;&nbsp;&nbsp; | 11&nbsp;&nbsp;&nbsp;&nbsp; | tone | =
yes&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>

<BR><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier =
New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | A--D&nbsp; | 12--15 | =
tone | yes&nbsp;&nbsp;&nbsp;&nbsp; |</FONT>

<BR><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier =
New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
+-------+--------+------+---------+</FONT>
</P>

<P><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier =
New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Table 3: DTMF Named Events</FONT>
</P>
<BR>

<P><FONT COLOR=3D"#800000" FACE=3D"Comic Sans MS">(In</FONT> <FONT =
COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier New">1.4.&nbsp; Events, =
States, Tone Patterns, and Voice-Encoded Tones</FONT>

<BR><FONT COLOR=3D"#800000" FACE=3D"Comic Sans MS">'states' are only =
mentioned in the heading nowhere in the text, something missing ?? =
)</FONT>
</P>

<P><FONT COLOR=3D"#800000" FACE=3D"Comic Sans MS">BR</FONT>
</P>

<P><I><FONT COLOR=3D"#800000" FACE=3D"Comic Sans MS">/GO</FONT></I>

<BR><FONT COLOR=3D"#000080" SIZE=3D1 =
FACE=3D"Arial">__________________________________________________________=
________|</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D1 FACE=3D"Arial">Gert =
Olsson&nbsp;&nbsp; /&nbsp; phone: +46 46&nbsp; 23 24 97&nbsp;&nbsp; =
/&nbsp; e-mail: gert.olsson@ericsson.com</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D1 FACE=3D"Arial">Ericsson AB - =
Business Unit Mobile Platforms, SE-221 83&nbsp; Lund, Sweden</FONT><SPAN =
LANG=3D"en-gb"></SPAN>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7A900.7B83615E--


--===============0738809369==
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

--===============0738809369==--




From avt-bounces@ietf.org Thu Jun 07 09:56: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 1HwITM-0006PY-GW; Thu, 07 Jun 2007 09:56:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwITL-0006PF-0g
	for avt@ietf.org; Thu, 07 Jun 2007 09:56:19 -0400
Received: from ik-out-1112.google.com ([66.249.90.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwITJ-0007mj-J8
	for avt@ietf.org; Thu, 07 Jun 2007 09:56:19 -0400
Received: by ik-out-1112.google.com with SMTP id b32so436086ika
	for <avt@ietf.org>; Thu, 07 Jun 2007 06:56:16 -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:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=l1qGBDUEK/bCwKs6uyM6l5PDYKG0KYfSddbVBNknyqIErW6AeOu5y2/1ziaqoneQ7vJ7wN0H8WW7YQazgO1AW/tIWxYHZQAWu6VmB7u9Vry3r94KhbH1G3x+x3GmYkkqlA3FOZNQbeMYP8MDw6HFZN118EvKvOafrZ0Id7DdyMs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=fUz/hMHZVi95OBEcHHjEIR804jSoBV48eAUHAqITLIdOB3Hqs7xsSS3j+4W13iUjb7Q+BbLubbvlCh9KxDqz3lU0xaPRNA0aw0HcPwl7SpHi+jtTVewJ/Vz4crc9jkCeU0ciebw3SQraX1WOgpXDBcpr7Jz9s8JyMWFn7/lnJhk=
Received: by 10.78.134.12 with SMTP id h12mr746467hud.1181224576531;
	Thu, 07 Jun 2007 06:56:16 -0700 (PDT)
Received: by 10.78.140.8 with HTTP; Thu, 7 Jun 2007 06:56:16 -0700 (PDT)
Message-ID: <4e5a3720706070656v5767ff71i261f2a3a2583929f@mail.gmail.com>
Date: Thu, 7 Jun 2007 16:56:16 +0300
From: "Murat Artun" <artunmurat@gmail.com>
To: avt@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Subject: [AVT] transmitting g729 bitstream in RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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 want to ask how the 80-bits long (assume G729B is disabled for
experimental purposes) G729 coded voice data is transmitted using RTP.

ITU test code encoder outputs 11 short integers (parameter vector)
where these 80-bits are packed following the below scheme:

/*----------------------------------------------------------------------------
 * prm2bits_ld8k -converts encoder parameter vector into vector of serial bits
 * bits2prm_ld8k - converts serial received bits to  encoder parameter vector
 *
 * The transmitted parameters are:
 *
 *     LPC:     1st codebook           7+1 bit
 *              2nd codebook           5+5 bit
 *
 *     1st subframe:
 *          pitch period                 8 bit
 *          parity check on 1st period   1 bit
 *          codebook index1 (positions) 13 bit
 *          codebook index2 (signs)      4 bit
 *          pitch and codebook gains   4+3 bit
 *
 *     2nd subframe:
 *          pitch period (relative)      5 bit
 *          codebook index1 (positions) 13 bit
 *          codebook index2 (signs)      4 bit
 *          pitch and codebook gains   4+3 bit
 *----------------------------------------------------------------------------
 */ (from BITS.C of ITU test code)

However, as I have followed the ethereal trace of a G729 voice
exchange, I see that only 8-bytes are transmitted for each G729 coded
10 ms voice data.

Considering the above parameter scheme that was specified to be
transmitted in the ITU test code, what is the true packing scheme for
each 10 ms G729 coded coice data?

Thanks in advice...

-- 
M u r at  A r t u n, MSc.
   Software Engineer

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



From avt-bounces@ietf.org Thu Jun 07 11:20: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 1HwJmT-0003eg-LG; Thu, 07 Jun 2007 11:20:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwJmR-0003UY-1G
	for avt@ietf.org; Thu, 07 Jun 2007 11:20:07 -0400
Received: from smtp101.rog.mail.re2.yahoo.com ([206.190.36.79])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HwJmP-0005KE-9U
	for avt@ietf.org; Thu, 07 Jun 2007 11:20:07 -0400
Received: (qmail 85357 invoked from network); 7 Jun 2007 15:20:01 -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:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
	b=KdABboY2FIf0VrRVswjBMIAa+9oFy1RRBaf2Y9JK3hS8UO9lJe6GidcE5irVAZLr089VcAURRhfo9TFrXR6kbloaNwZppA+AHHnklpf6BteO54QjpyLU6nuMw/TGNGnGVe1eRpIYN92lWbK3BSraUhb7lpAEXTsxuro99S731PQ=
	; 
Received: from unknown (HELO ?192.168.0.100?)
	(tom.taylor@rogers.com@74.105.35.229 with plain)
	by smtp101.rog.mail.re2.yahoo.com with SMTP; 7 Jun 2007 15:20:01 -0000
X-YMail-OSG: UE8LeHkVM1knWS1xT3w6po15gtGnZpG3nZzeI5qxOi6Td62Hsv3gz14YYzqGi90A9w--
Message-ID: <46682244.4030900@rogers.com>
Date: Thu, 07 Jun 2007 11:20:36 -0400
From: Tom Taylor <tom.taylor@rogers.com>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: "Gert Olsson (LD/EAB)" <gert.olsson@ericsson.com>
Subject: Re: [AVT] 'States' in RFC4733
References: <DA392F15190F9D40BF916AD7146E972E06802F2D@eseldmw101.eemea.ericsson.se>
In-Reply-To: <DA392F15190F9D40BF916AD7146E972E06802F2D@eseldmw101.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
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. Responses below marked with [PTT].

Gert Olsson (LD/EAB) wrote:
> Hi,
> I'm trying to understand RFC4733, the 'named events' part mostly chapter
> 2 and wonder about the definition of 'state'. For a state you send with
> duration=0, but this is not the definition of 'state', is it?

[PTT] The definition of state is a condition that persists until it 
times out (soft state, non-zero duration) or is replaced by a new 
mutually exclusive state. Unfortunately it looks like I lost the text 
that provides this definition, other than where it is implied in section 
2.3.5 "Duration". For concrete examples of state events, see ABCD bit 
signalling (section 2.4) and the Trunk Unavailable event (section 2.6) 
in draft-ietf-avt-rfc2833biscas "Definition of Events For 
Channel-Oriented Telephony Signalling".

> For DTMF,  is it 'Type' in table 3 that defines that DTMF events are not
> 'states' or what ?

[PTT] Type is indeed the place where the distinction is made.
> 
> 3.2.  DTMF Events
> 
>    Table 3 shows the DTMF-related event codes within the telephone-event
>    payload format.  The DTMF digits 0-9 and * and # are commonly
>    supported.  DTMF digits A through D are less frequently encountered,
>    typically in special applications such as military networks.
> 
>                     +-------+--------+------+---------+
>                     | Event | Code   | Type | Volume? |
>                     +-------+--------+------+---------+
>                     | 0--9  | 0--9   | tone | yes     |
>                     | *     | 10     | tone | yes     |
>                     | #     | 11     | tone | yes     |
>                     | A--D  | 12--15 | tone | yes     |
>                     +-------+--------+------+---------+
> 
>                         Table 3: DTMF Named Events
> 
> 
> (In 1.4.  Events, States, Tone Patterns, and Voice-Encoded Tones
> 'states' are only mentioned in the heading nowhere in the text,
> something missing ?? )

[PTT] Yes. As I say, lost the text dealing with states somewhere between 
versions, and never noticed.
> 
> BR
> 
> /GO
> __________________________________________________________________|
> Gert Olsson   /  phone: +46 46  23 24 97   /  e-mail:
> gert.olsson@ericsson.com
> Ericsson AB - Business Unit Mobile Platforms, SE-221 83  Lund, Sweden
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> 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 Jun 07 11:39: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 1HwK5K-00025l-4r; Thu, 07 Jun 2007 11:39:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwK5I-00025g-Ao
	for avt@ietf.org; Thu, 07 Jun 2007 11:39:36 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwK5F-0003SS-TG
	for avt@ietf.org; Thu, 07 Jun 2007 11:39:36 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 7 Jun 2007 17:39:27 +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
Subject: RE: [AVT] transmitting g729 bitstream in RTP
Date: Thu, 7 Jun 2007 17:39:25 +0200
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD1038B8358@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <4e5a3720706070656v5767ff71i261f2a3a2583929f@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] transmitting g729 bitstream in RTP
Thread-Index: AcepC66CjWELPDgIR7e27wbZruDNRwADfL0g
References: <4e5a3720706070656v5767ff71i261f2a3a2583929f@mail.gmail.com>
From: "SOLLAUD Aurelien RD-TECH-LAN" <aurelien.sollaud@orange-ftgroup.com>
To: "Murat Artun" <artunmurat@gmail.com>
X-OriginalArrivalTime: 07 Jun 2007 15:39:27.0868 (UTC)
	FILETIME=[0868D3C0:01C7A91A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi

A 10 ms G.729 frame =3D 10 bytes.
You can have a look at RFC 3551, section 4.5.6.

Aurelien=20

> -----Message d'origine-----
> De : Murat Artun [mailto:artunmurat@gmail.com]=20
> Envoy=E9 : jeudi 7 juin 2007 15:56
> =C0 : avt@ietf.org
> Objet : [AVT] transmitting g729 bitstream in RTP
>=20
> Hello,
>=20
> I want to ask how the 80-bits long (assume G729B is disabled=20
> for experimental purposes) G729 coded voice data is=20
> transmitted using RTP.
>=20
> ITU test code encoder outputs 11 short integers (parameter=20
> vector) where these 80-bits are packed following the below scheme:
>=20
> /*------------------------------------------------------------
> ----------------
>  * prm2bits_ld8k -converts encoder parameter vector into=20
> vector of serial bits
>  * bits2prm_ld8k - converts serial received bits to  encoder=20
> parameter vector
>  *
>  * The transmitted parameters are:
>  *
>  *     LPC:     1st codebook           7+1 bit
>  *              2nd codebook           5+5 bit
>  *
>  *     1st subframe:
>  *          pitch period                 8 bit
>  *          parity check on 1st period   1 bit
>  *          codebook index1 (positions) 13 bit
>  *          codebook index2 (signs)      4 bit
>  *          pitch and codebook gains   4+3 bit
>  *
>  *     2nd subframe:
>  *          pitch period (relative)      5 bit
>  *          codebook index1 (positions) 13 bit
>  *          codebook index2 (signs)      4 bit
>  *          pitch and codebook gains   4+3 bit
> =20
> *-------------------------------------------------------------
> ---------------
>  */ (from BITS.C of ITU test code)
>=20
> However, as I have followed the ethereal trace of a G729=20
> voice exchange, I see that only 8-bytes are transmitted for=20
> each G729 coded 10 ms voice data.
>=20
> Considering the above parameter scheme that was specified to=20
> be transmitted in the ITU test code, what is the true packing=20
> scheme for each 10 ms G729 coded coice data?
>=20
> Thanks in advice...
>=20
> --
> M u r at  A r t u n, MSc.
>    Software Engineer
>=20
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>=20

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



From avt-bounces@ietf.org Thu Jun 07 11:49: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 1HwKEQ-0006lA-QV; Thu, 07 Jun 2007 11:49:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwKEP-0006l4-EF
	for avt@ietf.org; Thu, 07 Jun 2007 11:49:01 -0400
Received: from relay1.mentorg.com ([192.94.38.131])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwKEO-00062p-01
	for avt@ietf.org; Thu, 07 Jun 2007 11:49:01 -0400
Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58])
	by relay1.mentorg.com with esmtp 
	id 1HwKEN-0001Xx-6H from Humayun_Ajmal@mentor.com 
	for avt@ietf.org; Thu, 07 Jun 2007 08:48:59 -0700
Received: from svr-pkl-exc-01.mgc.mentorg.com ([137.202.156.22]) by
	SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 7 Jun 2007 08:48:58 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 7 Jun 2007 20:48:55 +0500
Message-ID: <67BF5F17CF3CF9419CFFEDC4F76E053A027B62BA@svr-pkl-exc-01.mgc.mentorg.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: H264 Frame rate
Thread-Index: AcepG1p22g3wx5ITTjWk+ngVXhTBew==
From: "Ajmal, Humayun" <Humayun_Ajmal@mentor.com>
To: <avt@ietf.org>
X-OriginalArrivalTime: 07 Jun 2007 15:48:58.0634 (UTC)
	FILETIME=[5C9CCEA0:01C7A91B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Subject: [AVT] H264 Frame rate
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-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="===============1042635022=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1042635022==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7A91B.5A9FAB81"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7A91B.5A9FAB81
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi list,=20

H264 codec information received in SDP don't provide frame rate. With
given parameters (clock rate and bandwidth or another), is there anyway
frame rate can be calculated?

=20

Thanks=20

Humayun


------_=_NextPart_001_01C7A91B.5A9FAB81
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>H264 codec information received in SDP don&#8217;t =
provide
frame rate. With given parameters (clock rate and bandwidth or another), =
is
there anyway frame rate can be calculated?<o:p></o:p></span></font></p>

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

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

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

</div>

</body>

</html>

------_=_NextPart_001_01C7A91B.5A9FAB81--


--===============1042635022==
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

--===============1042635022==--




From avt-bounces@ietf.org Thu Jun 07 12:22: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 1HwKkJ-00049G-CQ; Thu, 07 Jun 2007 12:21:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwKkH-000444-Cv
	for avt@ietf.org; Thu, 07 Jun 2007 12:21:57 -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 1HwKkF-0005Cl-LV
	for avt@ietf.org; Thu, 07 Jun 2007 12:21:57 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [AVT] H264 Frame rate
Date: Thu, 7 Jun 2007 19:22:34 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C049E7C2B@IsrExch01.israel.polycom.com>
In-Reply-To: <67BF5F17CF3CF9419CFFEDC4F76E053A027B62BA@svr-pkl-exc-01.mgc.mentorg.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] H264 Frame rate
Thread-Index: AcepG1p22g3wx5ITTjWk+ngVXhTBewABHlzQ
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Ajmal, Humayun" <Humayun_Ajmal@mentor.com>,
	<avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 501044f827b673024f6a4cb1d46e67d2
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0733677378=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0733677378==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7A920.14F673C8"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7A920.14F673C8
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Look at max-mbps, max-fs attributes. Using the maximum macro blocks per
second and maximum frame size you can calculate the frame rate

Roni Even

=20

________________________________

From: Ajmal, Humayun [mailto:Humayun_Ajmal@mentor.com]=20
Sent: Thursday, June 07, 2007 6:49 PM
To: avt@ietf.org
Subject: [AVT] H264 Frame rate

=20

Hi list,=20

H264 codec information received in SDP don't provide frame rate. With
given parameters (clock rate and bandwidth or another), is there anyway
frame rate can be calculated?

=20

Thanks=20

Humayun


------_=_NextPart_001_01C7A920.14F673C8
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";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<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'>Hi,<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'>Look at </span></font>max-mbps, =
max-fs
attributes. Using the maximum macro blocks per second and maximum frame =
size you
can calculate the frame rate<o:p></o:p></p>

<p class=3DMsoNormal><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><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'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

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

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

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Ajmal, Humayun
[mailto:Humayun_Ajmal@mentor.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, June 07, =
2007 6:49
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> avt@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [AVT] H264 Frame =
rate</span></font><o:p></o:p></p>

</div>

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>H264 codec information received in SDP don&#8217;t =
provide
frame rate. With given parameters (clock rate and bandwidth or another), =
is
there anyway frame rate can be calculated?<o:p></o:p></span></font></p>

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

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

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

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C7A920.14F673C8--


--===============0733677378==
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

--===============0733677378==--




From avt-bounces@ietf.org Thu Jun 07 12:25: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 1HwKnx-0008In-Qo; Thu, 07 Jun 2007 12:25:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwKnw-0008Fu-T3; Thu, 07 Jun 2007 12:25:44 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HwKnv-0006Bt-V2; Thu, 07 Jun 2007 12:25:44 -0400
Received: from relay5.apple.com (relay5.apple.com [17.128.113.35])
	by mail-out3.apple.com (Postfix) with ESMTP id E5E4582199C;
	Thu,  7 Jun 2007 09:24:45 -0700 (PDT)
Received: from relay5.apple.com (unknown [127.0.0.1])
	by relay5.apple.com (Symantec Mail Security) with ESMTP id 7AA8429C002; 
	Thu,  7 Jun 2007 09:25:43 -0700 (PDT)
X-AuditID: 11807123-9d81dbb000000a23-7c-466831860d72
Received: from [17.202.35.52] (unknown [17.219.197.38])
	by relay5.apple.com (Apple SCV relay) with ESMTP id 130A030400B;
	Thu,  7 Jun 2007 09:25:41 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p06240847c28de03017ba@[17.202.35.52]>
In-Reply-To: <4667EAD0.9020803@st.com>
References: <465C0342.3010602@nsn.com>
	<7374777208BDC7449D5620EF9423256704991181@esealmw113.eemea.ericsson.se>
	<289643F2-2529-4C24-B430-B9967B5DADD4@csperkins.org>
	<p0624081dc289eb45c3bf@[17.202.35.52]> <4667EAD0.9020803@st.com>
Date: Thu, 7 Jun 2007 09:24:42 -0700
To: Andrea Lorenzo VITALI <andrea.vitali@st.com>
From: Dave Singer <singer@apple.com>
Subject: Re: [AVT] questions about grouping media streams in RTP and SDP 
	(RFC3388 etc), advice needed
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.3 (/)
X-Scan-Signature: b5299d0955d21ceeb18e25a232290fec
Cc: "Clinton Priddle \(KI/EAB\)" <clinton.priddle@ericsson.com>,
	mmusic <mmusic@ietf.org>, IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1985491660=="
Errors-To: avt-bounces@ietf.org

--===============1985491660==
Content-Type: multipart/alternative;
	boundary="============_-1030888954==_ma============"

--============_-1030888954==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

At 13:24  +0200 7/06/07, Andrea Lorenzo VITALI wrote:
>RFC3388 tagging/grouping cannot be used
>
>   - simultaneous encoding is explicitly forbidden (no Multiple
>Description Coding)
>
>   - grouping of layers explicitly forbidden (no Layered Coding)

Yes, I think it does seem that FID can't be used, though frankly the 
reasons for these restrictions are really unclear to me.  It's also 
not clear to me how DTMF tones pass their own tests (see below), but 
that's not terribly relevant.

>
>I talked about this in my presentation at IETF (page 6):
>http://www3.ietf.org/proceedings/05nov/slides/avt-3.pdf
>
>My presentation was about standard-compatible Multiple Description
>Coding (MDC). You can find the draft here:
>http://tools.ietf.org/tools/rfcmarkup/rfcmarkup.cgi?draft=draft-vitali-ietf-avt-mdc-lc-00.txt
>
>Your scheme is in fact an unbalanced multiple description coding scheme,
>isn't it? You transmit the full video and a low-resolution video to be
>used for concealment (1+1/4).

It's similar;  we're actually in a different coding system (not 
video), but the video is a good analog.

>
>The question of dependency between streams has also been raised for the
>new Scalable Video Codec (SVC).

Yes, I work on that too.

Is it possible we can agree fairly soon on the group ID for grouping 
media lines of the same codec, where the client terminal chooses 
which of the media streams it needs, and when, by examining their 
other characteristics?  Examples would be layered coding, or repair 
coding.

Here's an example:

v=0
o=adam 289083124 289083124 IN IP4 host.example.com
t=0 0
c=IN IP4 131.160.1.112
a=group:group_name 1 2
m=video 30000 RTP/AVP 97
a=rtpmap:97 coding-system/90000
a=fmtp:97 contains-redundant="normal"
a=mid:1
m=video 30002 RTP/AVP 98
a=rtpmap:98 coding-system/90000
a=fmtp:98 contains-redundant="redundant"
a=mid:2

The question is, what is the "group_name" here?  And once we agree on 
the code, do we need an RFC?

Is the space of covered applications just these two:  repair and 
layered coding?


>
>   Andrea
>
>
>Dave Singer wrote:
>>  Hi
>>
>>  we have a need to group together two media streams, in the style of RFC
>>  3388 <http://www.ietf.org/rfc/rfc3388.txt> but we're unsure whether an
>>  existing group type is suitable or not, and if it's not, we'd like to
>>  agree on a new one, and document it (presumably in an RFC).
>>
>>  What we have is a normal media stream, and a separate 'repair' or
>>  'entry' stream, that can be used when tuning in, or after loss, but is
>>  otherwise un-needed.  An example might be a video stream with a low
>>  I-frame interval (say every 15 seconds), with a repair stream which has
>>  only I-frames that are equivalent to the time-parallel non-I frame, at a
>>  frequency of say 1 per second.
>>
>>  It's not clear to us whether this is "one media flow" in the sense of
>>  FID, or not.  The example offers AMR and GSM audio, which are
>>  alternatives, and DTMF tones along with audio, which are supplementary
>>  to each other.  Perhaps we fall afoul of this restriction:
>>
>>  "An application that encodes the same media using different codecs
>>  simultaneously MUST NOT use FID to group those media lines."
>>
>>  or this one, for layered encoding:
>>
>>  "FID MUST NOT be used to group "m" lines that do not represent the same
>>  information."  (Though how DTMF tones and their associated audio pass
>>  this test is not clear).
>>
>>  Nor is it clear that the FEC group of RFC 4756 is right, either.  For a
>>  start, we may wish to use this new ID in combination with FEC, and
>>  secondly this tune-in stream has different characteristics.  For
>>  example, one can typically ignore all FEC and (as long as there are no
>>  errors) decode the stream correctly.  Ignoring the tune-in stream
>>  entirely may mean that you will never find a tune-in point, making the
>  > normal stream useless.
>>
>>  So, can we use FID for associating a repair stream with its base (we tag
>>  the streams so we know which is which, of course)?
>>
>>  p.s. RFC 4756 claims in the IANA section that the FEC group is
>>  registered under SDP characteristics, but actually I can find no
>>  registry anywhere in IANA of group types.
>>
>>
>
>--
>  ______________________________________________________________
>
>   Andrea VITALI                            andrea.vitali@st.com
>
>   tel (+39) 039 603 7244             mobile (+39) 347 93 08 433
>   fax (+39) 039 603 6129
>
>   STMicroelectronics
>   Centro Direzionale COLLEONI - Palazzo "DIALETTICA"
>   20041 Agrate Brianza (MI) ITALY
>  ______________________________________________________________
>
>Attachment converted: DaveG49:andrea.vitali.vcf (TEXT/ttxt) (000CDBBA)


-- 
David Singer
Apple/QuickTime
--============_-1030888954==_ma============
Content-Type: text/html; charset="us-ascii"

<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
 --></style><title>Re: [AVT] questions about grouping media streams in
RTP an</title></head><body>
<div>At 13:24&nbsp; +0200 7/06/07, Andrea Lorenzo VITALI wrote:</div>
<blockquote type="cite" cite>RFC3388 tagging/grouping cannot be
used<br>
<br>
&nbsp; - simultaneous encoding is explicitly forbidden (no
Multiple<br>
Description Coding)<br>
<br>
&nbsp; - grouping of layers explicitly forbidden (no Layered
Coding)</blockquote>
<div><br></div>
<div>Yes, I think it does seem that FID can't be used, though frankly
the reasons for these restrictions are really unclear to me.&nbsp;
It's also not clear to me how DTMF tones pass their own tests (see
below), but that's not terribly relevant.</div>
<div><br></div>
<blockquote type="cite" cite><br>
I talked about this in my presentation at IETF (page 6):</blockquote>
<blockquote type="cite"
cite>http://www3.ietf.org/proceedings/05nov/slides/avt-3.pdf<br>
<br>
My presentation was about standard-compatible Multiple Description<br>
Coding (MDC). You can find the draft here:<br>
http://tools.ietf.org/tools/rfcmarkup/rfcmarkup.cgi?draft=draft-vital<span
></span>i-ietf-avt-mdc-lc-00.txt<br>
<br>
Your scheme is in fact an unbalanced multiple description coding
scheme,<br>
isn't it? You transmit the full video and a low-resolution video to
be<br>
used for concealment (1+1/4).</blockquote>
<div><br></div>
<div>It's similar;&nbsp; we're actually in a different coding system
(not video), but the video is a good analog.</div>
<div><br></div>
<blockquote type="cite" cite><br>
The question of dependency between streams has also been raised for
the<br>
new Scalable Video Codec (SVC).</blockquote>
<div><br>
Yes, I work on that too.</div>
<div><br></div>
<div>Is it possible we can agree fairly soon on the group ID for
grouping media lines of the same codec, where the client terminal
chooses which of the media streams it needs, and when, by examining
their other characteristics?&nbsp; Examples would be layered coding,
or repair coding.</div>
<div><br></div>
<div>Here's an example:</div>
<div><br></div>
<div><font face="Courier" size="+1" color="#000000">v=0<br>
o=adam 289083124 289083124 IN IP4 host.example.com<br>
t=0 0<br>
c=IN IP4 131.160.1.112</font></div>
<div><font face="Courier" size="+1"
color="#000000">a=group:</font><font face="Courier" size="+1"
color="#C24343"><u>group_name</u></font><font face="Courier"
size="+1" color="#000000"> 1 2</font></div>
<div><font face="Courier" size="+1" color="#000000">m=video 30000
RTP/AVP 97</font></div>
<div><font face="Courier" size="+1" color="#000000">a=rtpmap:97
coding-system/90000</font></div>
<div><font face="Courier" size="+1" color="#000000">a=fmtp:97
contains-redundant="normal"</font></div>
<div><font face="Courier" size="+1" color="#000000">a=mid:1<br>
m=video 30002 RTP/AVP 98</font></div>
<div><font face="Courier" size="+1" color="#000000">a=rtpmap:98
coding-system/90000</font></div>
<div><font face="Courier" size="+1" color="#000000">a=fmtp:98
contains-redundant="redundant"</font></div>
<div><font face="Courier" size="+1" color="#000000">a=mid:2</font><br>
<font face="Courier" size="+1" color="#000000"></font></div>
<div>The question is, what is the &quot;group_name&quot; here?&nbsp;
And once we agree on the code, do we need an RFC?</div>
<div><br></div>
<div>Is the space of covered applications just these two:&nbsp; repair
and layered coding?</div>
<div><br></div>
<div><br></div>
<blockquote type="cite" cite><br>
&nbsp; Andrea<br>
<br>
<br>
Dave Singer wrote:<br>
&gt; Hi<br>
&gt;<br>
&gt; we have a need to group together two media streams, in the style
of RFC<br>
&gt; 3388 &lt;http://www.ietf.org/rfc/rfc3388.txt&gt; but we're unsure
whether an<br>
&gt; existing group type is suitable or not, and if it's not, we'd
like to<br>
&gt; agree on a new one, and document it (presumably in an RFC).<br>
&gt;<br>
&gt; What we have is a normal media stream, and a separate 'repair'
or<br>
&gt; 'entry' stream, that can be used when tuning in, or after loss,
but is<br>
&gt; otherwise un-needed.&nbsp; An example might be a video stream
with a low<br>
&gt; I-frame interval (say every 15 seconds), with a repair stream
which has<br>
&gt; only I-frames that are equivalent to the time-parallel non-I
frame, at a<br>
&gt; frequency of say 1 per second.<br>
&gt;<br>
&gt; It's not clear to us whether this is &quot;one media flow&quot;
in the sense of<br>
&gt; FID, or not.&nbsp; The example offers AMR and GSM audio, which
are<br>
&gt; alternatives, and DTMF tones along with audio, which are
supplementary<br>
&gt; to each other.&nbsp; Perhaps we fall afoul of this
restriction:<br>
&gt;<br>
&gt; &quot;An application that encodes the same media using different
codecs<br>
&gt; simultaneously MUST NOT use FID to group those media
lines.&quot;<br>
&gt;<br>
&gt; or this one, for layered encoding:<br>
&gt;<br>
&gt; &quot;FID MUST NOT be used to group &quot;m&quot; lines that do
not represent the same<br>
&gt; information.&quot;&nbsp; (Though how DTMF tones and their
associated audio pass<br>
&gt; this test is not clear).<br>
&gt;<br>
&gt; Nor is it clear that the FEC group of RFC 4756 is right, either.&nbsp;
For a<br>
&gt; start, we may wish to use this new ID in combination with FEC,
and<br>
&gt; secondly this tune-in stream has different characteristics.&nbsp;
For<br>
&gt; example, one can typically ignore all FEC and (as long as there
are no<br>
&gt; errors) decode the stream correctly.&nbsp; Ignoring the tune-in
stream<br>
&gt; entirely may mean that you will never find a tune-in point,
making the</blockquote>
<blockquote type="cite" cite>&gt; normal stream useless.<br>
&gt;<br>
&gt; So, can we use FID for associating a repair stream with its base
(we tag<br>
&gt; the streams so we know which is which, of course)?<br>
&gt;<br>
&gt; p.s. RFC 4756 claims in the IANA section that the FEC group
is<br>
&gt; registered under SDP characteristics, but actually I can find
no<br>
&gt; registry anywhere in IANA of group types.<br>
&gt;<br>
&gt;<br>
<br>
--<br>
&nbsp;______________________________________________________________<br
>
<br>
&nbsp; Andrea
VITALI&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span
></span
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span
></span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; andrea.vitali@st.com<br>
<br>
&nbsp; tel (+39) 039 603
7244&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span
></span>&nbsp;&nbsp; mobile (+39) 347 93 08 433<br>
&nbsp; fax (+39) 039 603 6129<br>
<br>
&nbsp; STMicroelectronics<br>
&nbsp; Centro Direzionale COLLEONI - Palazzo
&quot;DIALETTICA&quot;<br>
&nbsp; 20041 Agrate Brianza (MI) ITALY<br>
&nbsp;______________________________________________________________<br
>
<br>
Attachment converted: DaveG49:andrea.vitali.vcf (TEXT/ttxt)
(000CDBBA)</blockquote>
<div><br></div>
<div><br></div>
<x-sigsep><pre>-- 
</pre></x-sigsep>
<div>David Singer<br>
Apple/QuickTime</div>
</body>
</html>
--============_-1030888954==_ma============--


--===============1985491660==
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

--===============1985491660==--




From avt-bounces@ietf.org Thu Jun 07 13:46: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 1HwM45-0001Js-JH; Thu, 07 Jun 2007 13:46:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwM43-0001Jk-Sw; Thu, 07 Jun 2007 13:46:27 -0400
Received: from mail.hhi.fraunhofer.de ([193.174.67.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HwM43-0002X7-A6; Thu, 07 Jun 2007 13:46:27 -0400
Received: by mail.hhi.fraunhofer.de (Postfix, from userid 65534)
	id CBF521D88F70; Thu,  7 Jun 2007 19:46:26 +0200 (CEST)
Received: from ipam040189 (ipam189.Stanford.EDU [171.64.92.89])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(Client did not present a certificate)
	by mail.hhi.fraunhofer.de (Postfix) with ESMTP id 69A991D88F50;
	Thu,  7 Jun 2007 19:46:22 +0200 (CEST)
From: "Thomas Schierl" <schierl@hhi.fhg.de>
To: "'Dave Singer'" <singer@apple.com>,
	"'Even, Roni'" <roni.even@polycom.co.il>,
	"'mmusic'" <mmusic@ietf.org>, "'IETF AVT WG'" <avt@ietf.org>
References: <144ED8561CE90C41A3E5908EDECE315C049E76DA@IsrExch01.israel.polycom.com>
	<p0624081ac28b3247e073@[17.202.35.52]>
Subject: RE: [AVT] RE: [MMUSIC] questions about grouping media streams in RTP
	andSDP (RFC3388 etc), advice needed
Date: Thu, 7 Jun 2007 10:46:11 -0700
Organization: HHI/FhG
Message-ID: <000101c7a92b$c4752d50$595c40ab@ipam040189>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcenhyxcbwKgryeQTM2S+JPzrTemewBpEXzg
In-Reply-To: <p0624081ac28b3247e073@[17.202.35.52]>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on 
	mail.hhi.fraunhofer.de
X-Spam-Level: 
X-Spam-Status: No, hits=-104.9 required=5.0 tests=BAYES_00, USER_IN_WHITELIST 
	autolearn=ham version=2.64
X-alterMIME: Yes
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1449ead51a2ff026dcb23465f5379250
Cc: "'Clinton Priddle \(KI/EAB\)'" <clinton.priddle@ericsson.com>,
	Stephan.Wenger@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 Dave, 

I think there is a strong relation of your problem and the
http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered-codec-03.txt
In this draft, we described media dependency in general, not only for
scalable video. Currently, two types of dependencies are defined: layered
and mdc assuming the media is partially transported in different RTP
sessions. There is not requirement, that the part of the media is
independently decodable. It would be easy to integrate your needs, if they
should not be already covered.


Thomas

> -----Original Message-----
> From: Dave Singer [mailto:singer@apple.com]
> Sent: Tuesday, June 05, 2007 8:34 AM
> To: Even, Roni; mmusic; IETF AVT WG
> Cc: Clinton Priddle (KI/EAB)
> Subject: [AVT] RE: [MMUSIC] questions about grouping media streams in RTP
> andSDP (RFC3388 etc), advice needed
> 
> At 10:03  +0300 5/06/07, Even, Roni wrote:
> >Dave,
> >For layered encoding there is a proposal for a new grouping attribute in
> >http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered-codec-03.tx
> >t
> 
> I don't think this is a layered coding issue, either, alas.
> 
> >I looked at RFC3388 and I think that FID is not the answer to your
> >requirement as you mentioned
> >
> >To me it looks like what you are looking for is a way to specify
> >alternate offers.
> 
> No, these streams are not alternatives to each other in the regular
> sense.  Nor is this really used in offer/answer;  it's more an issue
> for multicast.  In multicast, you open the tune-in stream and the
> base stream, grab the first I-frame that arrives (in either) and then
> drop the tune-in stream.
> 
> Yes, we're aware that the recipient needs to be able to tell which is
> the base and which is the tune-in.
> 
> >If this is the case I have similar requirements and
> >would be happy to support such work.
> >
> >You also need a way to give semantics to the "repair" stream, this can
> >be done based on the content attribute from RFC 4796 or using a
> >dependency attribute see in Schierl's draft. The mid tag is not enough
> >for the receiver to know what you meant by this offer and which stream
> >is the repair.
> >
> >Here is an example for a solution using a new Alternatives grouping
> >attribute and giving semantics to the repair stream
> >
> >By using the grouping attribute in the offer you can know if the
> >answerer understood the grouping since if he does not than he will send
> >an answer with no a=group
> >
> >v=0
> >o=bob 280744730 28977631 IN IP4 host.example.com
> >s=
> >t=0 0
> >
> >a=group:ALTS 1 2
> >a=group:ALTS 1 3
> >
> >m=audio 6886 RTP/AVP 0
> >c=IN IP6 2001:0600::1
> >a=mid:1
> >
> >m=video 9000 RTP/AVP 100
> >c=IN IP4 192.0.2.2
> >a=rtpmap:100 H263-1998
> >a=mid:2
> >
> >m=video 9002 RTP/AVP 101
> >c=IN IP4 192.0.2.2
> >a=rtpmap:101 H263-1998
> >a=mid:3
> >a=content:repair=2 or a=depend:repair=2
> >
> >
> >Roni Even
> >
> >>  -----Original Message-----
> >>  From: Dave Singer [mailto:singer@apple.com]
> >>  Sent: Monday, June 04, 2007 7:19 PM
> >>  To: mmusic; IETF AVT WG
> >>  Cc: Clinton Priddle (KI/EAB)
> >>  Subject: [MMUSIC] questions about grouping media streams in RTP and
> >SDP
> >>  (RFC3388 etc), advice needed
> >>
> >>  Hi
> >>
> >>  we have a need to group together two media streams, in the style of
> >RFC
> >>  3388 <http://www.ietf.org/rfc/rfc3388.txt> but we're unsure whether an
> >>  existing group type is suitable or not, and if it's not, we'd like to
> >>  agree on a new one, and document it (presumably in an RFC).
> >>
> >>  What we have is a normal media stream, and a separate 'repair' or
> >>  'entry' stream, that can be used when tuning in, or after loss, but is
> >>  otherwise un-needed.  An example might be a video stream with a low
> >>  I-frame interval (say every 15 seconds), with a repair stream which
> >has
> >>  only I-frames that are equivalent to the time-parallel non-I frame, at
> >a
> >>  frequency of say 1 per second.
> >>
> >>  It's not clear to us whether this is "one media flow" in the sense of
> >>  FID, or not.  The example offers AMR and GSM audio, which are
> >>  alternatives, and DTMF tones along with audio, which are supplementary
> >>  to each other.  Perhaps we fall afoul of this restriction:
> >>
> >>  "An application that encodes the same media using different codecs
> >>  simultaneously MUST NOT use FID to group those media lines."
> >>
> >>  or this one, for layered encoding:
> >>
> >>  "FID MUST NOT be used to group "m" lines that do not represent the
> >same
> >>  information."  (Though how DTMF tones and their associated audio pass
> >>  this test is not clear).
> >>
> >>  Nor is it clear that the FEC group of RFC 4756 is right, either.  For
> >a
> >>  start, we may wish to use this new ID in combination with FEC, and
> >>  secondly this tune-in stream has different characteristics.  For
> >>  example, one can typically ignore all FEC and (as long as there are no
> >>  errors) decode the stream correctly.  Ignoring the tune-in stream
> >  > entirely may mean that you will never find a tune-in point, making
> the
> >>  normal stream useless.
> >>
> >>  So, can we use FID for associating a repair stream with its base (we
> >tag
> >>  the streams so we know which is which, of course)?
> >>
> >>  p.s. RFC 4756 claims in the IANA section that the FEC group is
> >>  registered under SDP characteristics, but actually I can find no
> >>  registry anywhere in IANA of group types.
> >>
> >>
> >>  --
> >>  David Singer
> >>  Apple/QuickTime
> >>
> >>  _______________________________________________
> >>  mmusic mailing list
> >>  mmusic@ietf.org
> >>  https://www1.ietf.org/mailman/listinfo/mmusic
> 
> 
> --
> David Singer
> Apple/QuickTime
> 
> _______________________________________________
> 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 Jun 07 13:49: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 1HwM79-0001ws-Mk; Thu, 07 Jun 2007 13:49:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwM78-0001wk-0o; Thu, 07 Jun 2007 13:49:38 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HwM77-0003DB-E8; Thu, 07 Jun 2007 13:49:38 -0400
Received: from relay7.apple.com (relay7.apple.com [17.128.113.37])
	by mail-out3.apple.com (Postfix) with ESMTP id 5F3CB82384E;
	Thu,  7 Jun 2007 10:48:39 -0700 (PDT)
Received: from relay7.apple.com (unknown [127.0.0.1])
	by relay7.apple.com (Symantec Mail Security) with ESMTP id 12EA8300AE; 
	Thu,  7 Jun 2007 10:49:37 -0700 (PDT)
X-AuditID: 11807125-9f763bb000000801-29-4668453059cf
Received: from [17.202.35.52] (unknown [17.219.197.38])
	by relay7.apple.com (Apple SCV relay) with ESMTP id 4F5B730044;
	Thu,  7 Jun 2007 10:49:36 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p0624084bc28df52e0342@[17.202.35.52]>
In-Reply-To: <000001c7a92a$f3aefac0$595c40ab@ipam040189>
References: <144ED8561CE90C41A3E5908EDECE315C049E76DA@IsrExch01.israel.polycom.com>
	<p0624081ac28b3247e073@[17.202.35.52]>
	<000001c7a92a$f3aefac0$595c40ab@ipam040189>
Date: Thu, 7 Jun 2007 10:49:08 -0700
To: Thomas Schierl <thomas.schierl@hhi.fraunhofer.de>
From: Dave Singer <singer@apple.com>
Subject: RE: [AVT] RE: [MMUSIC] questions about grouping media streams in
	RTP  andSDP  (RFC3388 etc), advice needed
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48
Cc: "'Even, Roni'" <roni.even@polycom.co.il>, Stephan.Wenger@nokia.com,
	mmusic@ietf.org, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

At 10:40  -0700 7/06/07, Thomas Schierl wrote:
>Hi Dave,
>
>I think there is a strong relation of your problem and the
>http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered-codec-03.txt .
>In this draft, we described media dependency in general, not only for
>scalable video. Currently, two types of dependencies are defined: layered
>and mdc assuming the media is partially transported in different RTP
>sessions. It would be easy to integrate your needs, if they should not be
>already covered.
>
>
>Thomas

Thank you.  I agree the problems are identical, or close to it.

Do you think we should use 'lay' or 'mdc', or a new dependency type? 
Or integrate a new group type into the draft (is 'DDP' right for our 
application)?

>
>>  -----Original Message-----
>>  From: Dave Singer [mailto:singer@apple.com]
>>  Sent: Tuesday, June 05, 2007 8:34 AM
>>  To: Even, Roni; mmusic; IETF AVT WG
>>  Cc: Clinton Priddle (KI/EAB)
>>  Subject: [AVT] RE: [MMUSIC] questions about grouping media streams in RTP
>>  andSDP (RFC3388 etc), advice needed
>>
>>  At 10:03  +0300 5/06/07, Even, Roni wrote:
>>  >Dave,
>>  >For layered encoding there is a proposal for a new grouping attribute in
>>  >http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered-codec-03.tx
>>  >t
>>
>>  I don't think this is a layered coding issue, either, alas.
>>
>>  >I looked at RFC3388 and I think that FID is not the answer to your
>>  >requirement as you mentioned
>>  >
>>  >To me it looks like what you are looking for is a way to specify
>>  >alternate offers.
>>
>>  No, these streams are not alternatives to each other in the regular
>>  sense.  Nor is this really used in offer/answer;  it's more an issue
>>  for multicast.  In multicast, you open the tune-in stream and the
>>  base stream, grab the first I-frame that arrives (in either) and then
>>  drop the tune-in stream.
>>
>>  Yes, we're aware that the recipient needs to be able to tell which is
>>  the base and which is the tune-in.
>>
>>  >If this is the case I have similar requirements and
>>  >would be happy to support such work.
>>  >
>>  >You also need a way to give semantics to the "repair" stream, this can
>>  >be done based on the content attribute from RFC 4796 or using a
>>  >dependency attribute see in Schierl's draft. The mid tag is not enough
>>  >for the receiver to know what you meant by this offer and which stream
>>  >is the repair.
>>  >
>>  >Here is an example for a solution using a new Alternatives grouping
>>  >attribute and giving semantics to the repair stream
>>  >
>>  >By using the grouping attribute in the offer you can know if the
>>  >answerer understood the grouping since if he does not than he will send
>>  >an answer with no a=group
>>  >
>>  >v=0
>>  >o=bob 280744730 28977631 IN IP4 host.example.com
>>  >s=
>>  >t=0 0
>>  >
>>  >a=group:ALTS 1 2
>>  >a=group:ALTS 1 3
>>  >
>>  >m=audio 6886 RTP/AVP 0
>>  >c=IN IP6 2001:0600::1
>>  >a=mid:1
>>  >
>>  >m=video 9000 RTP/AVP 100
>>  >c=IN IP4 192.0.2.2
>>  >a=rtpmap:100 H263-1998
>>  >a=mid:2
>>  >
>>  >m=video 9002 RTP/AVP 101
>>  >c=IN IP4 192.0.2.2
>>  >a=rtpmap:101 H263-1998
>>  >a=mid:3
>>  >a=content:repair=2 or a=depend:repair=2
>>  >
>>  >
>>  >Roni Even
>>  >
>>  >>  -----Original Message-----
>>  >>  From: Dave Singer [mailto:singer@apple.com]
>>  >>  Sent: Monday, June 04, 2007 7:19 PM
>>  >>  To: mmusic; IETF AVT WG
>>  >>  Cc: Clinton Priddle (KI/EAB)
>>  >>  Subject: [MMUSIC] questions about grouping media streams in RTP and
>>  >SDP
>>  >>  (RFC3388 etc), advice needed
>>  >>
>>  >>  Hi
>>  >>
>>  >>  we have a need to group together two media streams, in the style of
>>  >RFC
>>  >>  3388 <http://www.ietf.org/rfc/rfc3388.txt> but we're unsure whether an
>>  >>  existing group type is suitable or not, and if it's not, we'd like to
>>  >>  agree on a new one, and document it (presumably in an RFC).
>>  >>
>>  >>  What we have is a normal media stream, and a separate 'repair' or
>  > >>  'entry' stream, that can be used when tuning in, or after loss, but is
>>  >>  otherwise un-needed.  An example might be a video stream with a low
>>  >>  I-frame interval (say every 15 seconds), with a repair stream which
>>  >has
>>  >>  only I-frames that are equivalent to the time-parallel non-I frame, at
>>  >a
>>  >>  frequency of say 1 per second.
>>  >>
>>  >>  It's not clear to us whether this is "one media flow" in the sense of
>>  >>  FID, or not.  The example offers AMR and GSM audio, which are
>>  >>  alternatives, and DTMF tones along with audio, which are supplementary
>>  >>  to each other.  Perhaps we fall afoul of this restriction:
>>  >>
>>  >>  "An application that encodes the same media using different codecs
>>  >>  simultaneously MUST NOT use FID to group those media lines."
>>  >>
>>  >>  or this one, for layered encoding:
>>  >>
>>  >>  "FID MUST NOT be used to group "m" lines that do not represent the
>>  >same
>>  >>  information."  (Though how DTMF tones and their associated audio pass
>>  >>  this test is not clear).
>>  >>
>>  >>  Nor is it clear that the FEC group of RFC 4756 is right, either.  For
>>  >a
>>  >>  start, we may wish to use this new ID in combination with FEC, and
>>  >>  secondly this tune-in stream has different characteristics.  For
>>  >>  example, one can typically ignore all FEC and (as long as there are no
>>  >>  errors) decode the stream correctly.  Ignoring the tune-in stream
>>  >  > entirely may mean that you will never find a tune-in point, making
>>  the
>>  >>  normal stream useless.
>>  >>
>>  >>  So, can we use FID for associating a repair stream with its base (we
>>  >tag
>>  >>  the streams so we know which is which, of course)?
>>  >>
>>  >>  p.s. RFC 4756 claims in the IANA section that the FEC group is
>>  >>  registered under SDP characteristics, but actually I can find no
>>  >>  registry anywhere in IANA of group types.
>>  >>
>>  >>
>>  >>  --
>>  >>  David Singer
>>  >>  Apple/QuickTime
>>  >>
>>  >>  _______________________________________________
>>  >>  mmusic mailing list
>>  >>  mmusic@ietf.org
>>  >>  https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>
>>  --
>>  David Singer
>>  Apple/QuickTime
>>
>>  _______________________________________________
>>  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 Jun 07 13:58: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 1HwMFT-0007rb-FT; Thu, 07 Jun 2007 13:58:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwMFS-0007rN-Be
	for avt@ietf.org; Thu, 07 Jun 2007 13:58:14 -0400
Received: from smtp.mitel.com ([216.191.234.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwMFQ-0005ag-QL
	for avt@ietf.org; Thu, 07 Jun 2007 13:58:14 -0400
Received: from localhost (smtp.mitel.com [127.0.0.1])
	by smtp.mitel.com (Postfix) with ESMTP id 82B9420093;
	Thu,  7 Jun 2007 13:58:12 -0400 (EDT)
Received: from smtp.mitel.com ([127.0.0.1])
	by localhost (smtp.mitel.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 09344-01; Thu,  7 Jun 2007 13:58:11 -0400 (EDT)
Received: from kanmta01.mitel.com (kanmta01 [134.199.37.58])
	by smtp.mitel.com (Postfix) with ESMTP id ACAE92007A;
	Thu,  7 Jun 2007 13:58:11 -0400 (EDT)
To: "Murat Artun" <artunmurat@gmail.com>
Subject: Re: [AVT] transmitting g729 bitstream in RTP
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OFCA814CF8.2685D3DC-ON852572F3.00628CB2-852572F3.0062B5D3@mitel.com>
From: dieter_schulz@Mitel.COM
Date: Thu, 7 Jun 2007 13:58:10 -0400
X-MIMETrack: Serialize by Router on kanmta01/Mitel(Release 5.0.12 |February 13,
	2003) at 06/07/2007 01:58:09 PM,
	Serialize complete at 06/07/2007 01:58:09 PM
X-Virus-Scanned: by amavisd-new (virusonly) at mitel.com
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 21be852dc93f0971708678c18d38c096
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="===============1628012119=="
Errors-To: avt-bounces@ietf.org

This is a multipart message in MIME format.
--===============1628012119==
Content-Type: multipart/alternative;
	boundary="=_alternative 0062B5D2852572F3_="

This is a multipart message in MIME format.
--=_alternative 0062B5D2852572F3_=
Content-Type: text/plain; charset="us-ascii"

I think you have to check your ethereal. 10 ms G729 has 10 bytes (80 bits) 
of payload.

Regards,
Dieter
------------------------------------------------------------
Dieter Schulz
Manager: DSP & Media Processing
Mitel Networks
Tel: 613-592-2122
Fax: 613-592-4784




"Murat Artun" <artunmurat@gmail.com>
06/07/2007 09:56 AM

 
        To:     avt@ietf.org
        cc: 
        Subject:        [AVT] transmitting g729 bitstream in RTP


Hello,

I want to ask how the 80-bits long (assume G729B is disabled for
experimental purposes) G729 coded voice data is transmitted using RTP.

ITU test code encoder outputs 11 short integers (parameter vector)
where these 80-bits are packed following the below scheme:

/*----------------------------------------------------------------------------
 * prm2bits_ld8k -converts encoder parameter vector into vector of serial 
bits
 * bits2prm_ld8k - converts serial received bits to  encoder parameter 
vector
 *
 * The transmitted parameters are:
 *
 *     LPC:     1st codebook           7+1 bit
 *              2nd codebook           5+5 bit
 *
 *     1st subframe:
 *          pitch period                 8 bit
 *          parity check on 1st period   1 bit
 *          codebook index1 (positions) 13 bit
 *          codebook index2 (signs)      4 bit
 *          pitch and codebook gains   4+3 bit
 *
 *     2nd subframe:
 *          pitch period (relative)      5 bit
 *          codebook index1 (positions) 13 bit
 *          codebook index2 (signs)      4 bit
 *          pitch and codebook gains   4+3 bit
 
*----------------------------------------------------------------------------
 */ (from BITS.C of ITU test code)

However, as I have followed the ethereal trace of a G729 voice
exchange, I see that only 8-bytes are transmitted for each G729 coded
10 ms voice data.

Considering the above parameter scheme that was specified to be
transmitted in the ITU test code, what is the true packing scheme for
each 10 ms G729 coded coice data?

Thanks in advice...

-- 
M u r at  A r t u n, MSc.
   Software Engineer

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



--=_alternative 0062B5D2852572F3_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">I think you have to check your ethereal. 10 ms G729 has 10 bytes (80 bits) of payload.</font>
<br>
<br><font size=2 face="sans-serif">Regards,</font>
<br><font size=2 face="sans-serif">Dieter</font>
<br><font size=2 face="sans-serif">------------------------------------------------------------<br>
Dieter Schulz<br>
Manager: DSP &amp; Media Processing<br>
Mitel Networks<br>
Tel: 613-592-2122<br>
Fax: 613-592-4784</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>&quot;Murat Artun&quot; &lt;artunmurat@gmail.com&gt;</b></font>
<p><font size=1 face="sans-serif">06/07/2007 09:56 AM</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;avt@ietf.org</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;[AVT] transmitting g729 bitstream in RTP</font></table>
<br>
<br>
<br><font size=2 face="Courier New">Hello,<br>
<br>
I want to ask how the 80-bits long (assume G729B is disabled for<br>
experimental purposes) G729 coded voice data is transmitted using RTP.<br>
<br>
ITU test code encoder outputs 11 short integers (parameter vector)<br>
where these 80-bits are packed following the below scheme:<br>
<br>
/*----------------------------------------------------------------------------<br>
 * prm2bits_ld8k -converts encoder parameter vector into vector of serial bits<br>
 * bits2prm_ld8k - converts serial received bits to &nbsp;encoder parameter vector<br>
 *<br>
 * The transmitted parameters are:<br>
 *<br>
 * &nbsp; &nbsp; LPC: &nbsp; &nbsp; 1st codebook &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 7+1 bit<br>
 * &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2nd codebook &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 5+5 bit<br>
 *<br>
 * &nbsp; &nbsp; 1st subframe:<br>
 * &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;pitch period &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 8 bit<br>
 * &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;parity check on 1st period &nbsp; 1 bit<br>
 * &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;codebook index1 (positions) 13 bit<br>
 * &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;codebook index2 (signs) &nbsp; &nbsp; &nbsp;4 bit<br>
 * &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;pitch and codebook gains &nbsp; 4+3 bit<br>
 *<br>
 * &nbsp; &nbsp; 2nd subframe:<br>
 * &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;pitch period (relative) &nbsp; &nbsp; &nbsp;5 bit<br>
 * &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;codebook index1 (positions) 13 bit<br>
 * &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;codebook index2 (signs) &nbsp; &nbsp; &nbsp;4 bit<br>
 * &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;pitch and codebook gains &nbsp; 4+3 bit<br>
 *----------------------------------------------------------------------------<br>
 */ (from BITS.C of ITU test code)<br>
<br>
However, as I have followed the ethereal trace of a G729 voice<br>
exchange, I see that only 8-bytes are transmitted for each G729 coded<br>
10 ms voice data.<br>
<br>
Considering the above parameter scheme that was specified to be<br>
transmitted in the ITU test code, what is the true packing scheme for<br>
each 10 ms G729 coded coice data?<br>
<br>
Thanks in advice...<br>
<br>
-- <br>
M u r at &nbsp;A r t u n, MSc.<br>
 &nbsp; Software Engineer<br>
<br>
_______________________________________________<br>
Audio/Video Transport Working Group<br>
avt@ietf.org<br>
https://www1.ietf.org/mailman/listinfo/avt<br>
</font>
<br>
<br>
--=_alternative 0062B5D2852572F3_=--


--===============1628012119==
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

--===============1628012119==--




From avt-bounces@ietf.org Thu Jun 07 15:50: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 1HwO0R-0000au-Go; Thu, 07 Jun 2007 15:50:51 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwO09-0008Km-4I; Thu, 07 Jun 2007 15:50:33 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HwO08-0005xr-MR; Thu, 07 Jun 2007 15:50:32 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 575C52ACC8;
	Thu,  7 Jun 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HwNze-0002Un-3K; Thu, 07 Jun 2007 15:50: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: <E1HwNze-0002Un-3K@stiedprstage1.ietf.org>
Date: Thu, 07 Jun 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rfc2833biscas-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		: Definition of Events For Channel-Oriented Telephony Signalling
	Author(s)	: T. Taylor, H. Schulzrinne
	Filename	: draft-ietf-avt-rfc2833biscas-05.txt
	Pages		: 26
	Date		: 2007-6-7
	
This memo updates RFC 4733 to add event codes for telephony signals
   used for channel-associated signalling when carried in the telephony
   event RTP payload.  It supersedes and adds to the original assignment
   of event codes for this purpose in RFC 2833 section 3.14.  As
   documented in Appendix A of RFC 4733, certain of the RFC 2833 events
   have been deprecated, because their specification was ambiguous,
   erroneous or redundant.  In fact, the degree of change from RFC 2833
   section 3.14 is such that implementations of the present document
   will be fully backward compatible with RFC 2833 implementations only
   in the case of full ABCD-bit signalling.  The positive benefits of
   the present document are an expanded coverage of signalling systems
   and a more carefully specified and documented coverage of signalling
   systems covered by RFC 2833.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc2833biscas-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-rfc2833biscas-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-rfc2833biscas-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-6-7111425.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2007-6-7111425.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 Jun 07 16:06:07 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 1HwOF8-0005Xb-Ue; Thu, 07 Jun 2007 16:06:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwOF6-0005XM-Rm; Thu, 07 Jun 2007 16:06:00 -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 1HwOF5-0000lX-Oh; Thu, 07 Jun 2007 16:06:00 -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] RE: [MMUSIC] questions about grouping media streams in RTP
	andSDP (RFC3388 etc), advice needed
Date: Thu, 7 Jun 2007 23:06:45 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C049E7C50@IsrExch01.israel.polycom.com>
In-Reply-To: <000101c7a92b$c4752d50$595c40ab@ipam040189>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] RE: [MMUSIC] questions about grouping media streams in RTP
	andSDP (RFC3388 etc), advice needed
Thread-Index: AcenhyxcbwKgryeQTM2S+JPzrTemewBpEXzgAATpg+A=
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Thomas Schierl" <schierl@hhi.fhg.de>, "Dave Singer" <singer@apple.com>,
	"mmusic" <mmusic@ietf.org>, "IETF AVT WG" <avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 76c7db407a166e4c39f35d8215d8dd32
Cc: "Clinton Priddle \(KI/EAB\)" <clinton.priddle@ericsson.com>,
	Stephan.Wenger@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,
My view is that you have similarity in the need for dependencies between
streams but the grouping logic is different.
In the layered codec the grouping is for a group that you can use all or
part of while in the repair case you may take one or the other.

Roni Even

> -----Original Message-----
> From: Thomas Schierl [mailto:schierl@hhi.fhg.de]
> Sent: Thursday, June 07, 2007 8:46 PM
> To: 'Dave Singer'; Even, Roni; 'mmusic'; 'IETF AVT WG'
> Cc: Stephan.Wenger@nokia.com; 'Clinton Priddle (KI/EAB)'
> Subject: RE: [AVT] RE: [MMUSIC] questions about grouping media streams
in
> RTP andSDP (RFC3388 etc), advice needed
>=20
> Hi Dave,
>=20
> I think there is a strong relation of your problem and the
>
http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered-codec-03.tx
t
> In this draft, we described media dependency in general, not only for
> scalable video. Currently, two types of dependencies are defined:
layered
> and mdc assuming the media is partially transported in different RTP
> sessions. There is not requirement, that the part of the media is
> independently decodable. It would be easy to integrate your needs, if
they
> should not be already covered.
>=20
>=20
> Thomas
>=20
> > -----Original Message-----
> > From: Dave Singer [mailto:singer@apple.com]
> > Sent: Tuesday, June 05, 2007 8:34 AM
> > To: Even, Roni; mmusic; IETF AVT WG
> > Cc: Clinton Priddle (KI/EAB)
> > Subject: [AVT] RE: [MMUSIC] questions about grouping media streams
in
> RTP
> > andSDP (RFC3388 etc), advice needed
> >
> > At 10:03  +0300 5/06/07, Even, Roni wrote:
> > >Dave,
> > >For layered encoding there is a proposal for a new grouping
attribute
> in
> > >http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered-codec-
> 03.tx
> > >t
> >
> > I don't think this is a layered coding issue, either, alas.
> >
> > >I looked at RFC3388 and I think that FID is not the answer to your
> > >requirement as you mentioned
> > >
> > >To me it looks like what you are looking for is a way to specify
> > >alternate offers.
> >
> > No, these streams are not alternatives to each other in the regular
> > sense.  Nor is this really used in offer/answer;  it's more an issue
> > for multicast.  In multicast, you open the tune-in stream and the
> > base stream, grab the first I-frame that arrives (in either) and
then
> > drop the tune-in stream.
> >
> > Yes, we're aware that the recipient needs to be able to tell which
is
> > the base and which is the tune-in.
> >
> > >If this is the case I have similar requirements and
> > >would be happy to support such work.
> > >
> > >You also need a way to give semantics to the "repair" stream, this
can
> > >be done based on the content attribute from RFC 4796 or using a
> > >dependency attribute see in Schierl's draft. The mid tag is not
enough
> > >for the receiver to know what you meant by this offer and which
stream
> > >is the repair.
> > >
> > >Here is an example for a solution using a new Alternatives grouping
> > >attribute and giving semantics to the repair stream
> > >
> > >By using the grouping attribute in the offer you can know if the
> > >answerer understood the grouping since if he does not than he will
send
> > >an answer with no a=3Dgroup
> > >
> > >v=3D0
> > >o=3Dbob 280744730 28977631 IN IP4 host.example.com
> > >s=3D
> > >t=3D0 0
> > >
> > >a=3Dgroup:ALTS 1 2
> > >a=3Dgroup:ALTS 1 3
> > >
> > >m=3Daudio 6886 RTP/AVP 0
> > >c=3DIN IP6 2001:0600::1
> > >a=3Dmid:1
> > >
> > >m=3Dvideo 9000 RTP/AVP 100
> > >c=3DIN IP4 192.0.2.2
> > >a=3Drtpmap:100 H263-1998
> > >a=3Dmid:2
> > >
> > >m=3Dvideo 9002 RTP/AVP 101
> > >c=3DIN IP4 192.0.2.2
> > >a=3Drtpmap:101 H263-1998
> > >a=3Dmid:3
> > >a=3Dcontent:repair=3D2 or a=3Ddepend:repair=3D2
> > >
> > >
> > >Roni Even
> > >
> > >>  -----Original Message-----
> > >>  From: Dave Singer [mailto:singer@apple.com]
> > >>  Sent: Monday, June 04, 2007 7:19 PM
> > >>  To: mmusic; IETF AVT WG
> > >>  Cc: Clinton Priddle (KI/EAB)
> > >>  Subject: [MMUSIC] questions about grouping media streams in RTP
and
> > >SDP
> > >>  (RFC3388 etc), advice needed
> > >>
> > >>  Hi
> > >>
> > >>  we have a need to group together two media streams, in the style
of
> > >RFC
> > >>  3388 <http://www.ietf.org/rfc/rfc3388.txt> but we're unsure
whether
> an
> > >>  existing group type is suitable or not, and if it's not, we'd
like
> to
> > >>  agree on a new one, and document it (presumably in an RFC).
> > >>
> > >>  What we have is a normal media stream, and a separate 'repair'
or
> > >>  'entry' stream, that can be used when tuning in, or after loss,
but
> is
> > >>  otherwise un-needed.  An example might be a video stream with a
low
> > >>  I-frame interval (say every 15 seconds), with a repair stream
which
> > >has
> > >>  only I-frames that are equivalent to the time-parallel non-I
frame,
> at
> > >a
> > >>  frequency of say 1 per second.
> > >>
> > >>  It's not clear to us whether this is "one media flow" in the
sense
> of
> > >>  FID, or not.  The example offers AMR and GSM audio, which are
> > >>  alternatives, and DTMF tones along with audio, which are
> supplementary
> > >>  to each other.  Perhaps we fall afoul of this restriction:
> > >>
> > >>  "An application that encodes the same media using different
codecs
> > >>  simultaneously MUST NOT use FID to group those media lines."
> > >>
> > >>  or this one, for layered encoding:
> > >>
> > >>  "FID MUST NOT be used to group "m" lines that do not represent
the
> > >same
> > >>  information."  (Though how DTMF tones and their associated audio
> pass
> > >>  this test is not clear).
> > >>
> > >>  Nor is it clear that the FEC group of RFC 4756 is right, either.
> For
> > >a
> > >>  start, we may wish to use this new ID in combination with FEC,
and
> > >>  secondly this tune-in stream has different characteristics.  For
> > >>  example, one can typically ignore all FEC and (as long as there
are
> no
> > >>  errors) decode the stream correctly.  Ignoring the tune-in
stream
> > >  > entirely may mean that you will never find a tune-in point,
making
> > the
> > >>  normal stream useless.
> > >>
> > >>  So, can we use FID for associating a repair stream with its base
(we
> > >tag
> > >>  the streams so we know which is which, of course)?
> > >>
> > >>  p.s. RFC 4756 claims in the IANA section that the FEC group is
> > >>  registered under SDP characteristics, but actually I can find no
> > >>  registry anywhere in IANA of group types.
> > >>
> > >>
> > >>  --
> > >>  David Singer
> > >>  Apple/QuickTime
> > >>
> > >>  _______________________________________________
> > >>  mmusic mailing list
> > >>  mmusic@ietf.org
> > >>  https://www1.ietf.org/mailman/listinfo/mmusic
> >
> >
> > --
> > David Singer
> > Apple/QuickTime
> >
> > _______________________________________________
> > 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 Jun 07 16:53: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 1HwOyj-00081W-MB; Thu, 07 Jun 2007 16:53:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwOyi-00080p-GP
	for avt@ietf.org; Thu, 07 Jun 2007 16:53:08 -0400
Received: from smtp105.rog.mail.re2.yahoo.com ([206.190.36.83])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HwOyh-0006Hh-76
	for avt@ietf.org; Thu, 07 Jun 2007 16:53:08 -0400
Received: (qmail 78833 invoked from network); 7 Jun 2007 20:53:07 -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:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
	b=PBc2ypTP4aYa5FYg77XHtk8eCrVN081+NK9tdWSj8IoZR16k1jAD/IKc2vWV2PMVfAZtZhhT1GoeBauEky8Bmj2LRrrLs/6N+keZFZogQiPqYa0jc3HbBTxtJbHZKQkkgLehf+0EGyjz9NYIRuLXeToxnnobDlK+NJhKk+Mp0VU=
	; 
Received: from unknown (HELO ?192.168.0.100?)
	(tom.taylor@rogers.com@74.105.35.229 with plain)
	by smtp105.rog.mail.re2.yahoo.com with SMTP; 7 Jun 2007 20:53:07 -0000
X-YMail-OSG: _XBRlu4VM1njGwmWv53_Yh9W02WvMKmbwByKqw6ufbJ1TOrGzfYy3glnsNBI65qH7Q--
Message-ID: <46687056.2020309@rogers.com>
Date: Thu, 07 Jun 2007 16:53:42 -0400
From: Tom Taylor <tom.taylor@rogers.com>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
CC: avt@ietf.org
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rfc2833biscas-05.txt
References: <E1HwNze-0002Un-3K@stiedprstage1.ietf.org>
In-Reply-To: <E1HwNze-0002Un-3K@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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 was a trivial update.  My attempt at a URL reference for meter 
pulse turned out badly, so I put the URL in the body of the text. Also, 
I also forgot to update the date when I submitted the previous version.

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		: Definition of Events For Channel-Oriented Telephony Signalling
> 	Author(s)	: T. Taylor, H. Schulzrinne
> 	Filename	: draft-ietf-avt-rfc2833biscas-05.txt
> 	Pages		: 26
> 	Date		: 2007-6-7
> 	
> This memo updates RFC 4733 to add event codes for telephony signals
>    used for channel-associated signalling when carried in the telephony
>    event RTP payload.  It supersedes and adds to the original assignment
>    of event codes for this purpose in RFC 2833 section 3.14.  As
>    documented in Appendix A of RFC 4733, certain of the RFC 2833 events
>    have been deprecated, because their specification was ambiguous,
>    erroneous or redundant.  In fact, the degree of change from RFC 2833
>    section 3.14 is such that implementations of the present document
>    will be fully backward compatible with RFC 2833 implementations only
>    in the case of full ABCD-bit signalling.  The positive benefits of
>    the present document are an expanded coverage of signalling systems
>    and a more carefully specified and documented coverage of signalling
>    systems covered by RFC 2833.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc2833biscas-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.
> 

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



From avt-bounces@ietf.org Thu Jun 07 17:33: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 1HwPby-0006qw-4E; Thu, 07 Jun 2007 17:33:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwPbw-0006qn-RX; Thu, 07 Jun 2007 17:33:40 -0400
Received: from mail.hhi.fraunhofer.de ([193.174.67.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HwPbu-0005kf-4t; Thu, 07 Jun 2007 17:33:40 -0400
Received: by mail.hhi.fraunhofer.de (Postfix, from userid 65534)
	id 7C4C91D88F65; Thu,  7 Jun 2007 23:33:37 +0200 (CEST)
Received: from ipam040189 (DNab423247.Stanford.EDU [171.66.50.71])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(Client did not present a certificate)
	by mail.hhi.fraunhofer.de (Postfix) with ESMTP id BA85C1D88F74;
	Thu,  7 Jun 2007 23:33:33 +0200 (CEST)
From: "Thomas Schierl" <schierl@hhi.fhg.de>
To: "'Dave Singer'" <singer@apple.com>
References: <144ED8561CE90C41A3E5908EDECE315C049E76DA@IsrExch01.israel.polycom.com><p0624081ac28b3247e073@[17.202.35.52]><000001c7a92a$f3aefac0$595c40ab@ipam040189>
	<p0624084bc28df52e0342@[17.202.35.52]>
Subject: RE: [AVT] RE: [MMUSIC] questions about grouping media streams inRTP
	andSDP (RFC3388 etc), advice needed
Date: Thu, 7 Jun 2007 14:33:30 -0700
Organization: HHI/FhG
Message-ID: <009501c7a94b$807c7570$473242ab@ipam040189>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AcepLDjNiJ1Dz8PBQVaRnZeaFE0EbAAHmvmQ
In-Reply-To: <p0624084bc28df52e0342@[17.202.35.52]>
X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on 
	mail.hhi.fraunhofer.de
X-Spam-Level: 
X-Spam-Status: No, hits=-104.9 required=5.0 tests=BAYES_00, USER_IN_WHITELIST 
	autolearn=ham version=2.64
X-alterMIME: Yes
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff0adf256e4dd459cc25215cfa732ac1
Cc: "'Even, Roni'" <roni.even@polycom.co.il>, Stephan.Wenger@nokia.com,
	mmusic@ietf.org, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi Dave,

I think the grouping type DDP fits, but we should talk about an extra type
of dependency for that. 

Thomas



> -----Original Message-----
> From: Dave Singer [mailto:singer@apple.com]
> Sent: Thursday, June 07, 2007 10:49 AM
> To: Thomas Schierl
> Cc: Stephan.Wenger@nokia.com; mmusic@ietf.org; 'Even, Roni'; avt@ietf.org
> Subject: RE: [AVT] RE: [MMUSIC] questions about grouping media streams
> inRTP andSDP (RFC3388 etc), advice needed
> 
> At 10:40  -0700 7/06/07, Thomas Schierl wrote:
> >Hi Dave,
> >
> >I think there is a strong relation of your problem and the
> >http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered-codec-03.txt
> .
> >In this draft, we described media dependency in general, not only for
> >scalable video. Currently, two types of dependencies are defined: layered
> >and mdc assuming the media is partially transported in different RTP
> >sessions. It would be easy to integrate your needs, if they should not be
> >already covered.
> >
> >
> >Thomas
> 
> Thank you.  I agree the problems are identical, or close to it.
> 
> Do you think we should use 'lay' or 'mdc', or a new dependency type?
> Or integrate a new group type into the draft (is 'DDP' right for our
> application)?
> 
> >
> >>  -----Original Message-----
> >>  From: Dave Singer [mailto:singer@apple.com]
> >>  Sent: Tuesday, June 05, 2007 8:34 AM
> >>  To: Even, Roni; mmusic; IETF AVT WG
> >>  Cc: Clinton Priddle (KI/EAB)
> >>  Subject: [AVT] RE: [MMUSIC] questions about grouping media streams in
> RTP
> >>  andSDP (RFC3388 etc), advice needed
> >>
> >>  At 10:03  +0300 5/06/07, Even, Roni wrote:
> >>  >Dave,
> >>  >For layered encoding there is a proposal for a new grouping attribute
> in
> >>  >http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered-codec-
> 03.tx
> >>  >t
> >>
> >>  I don't think this is a layered coding issue, either, alas.
> >>
> >>  >I looked at RFC3388 and I think that FID is not the answer to your
> >>  >requirement as you mentioned
> >>  >
> >>  >To me it looks like what you are looking for is a way to specify
> >>  >alternate offers.
> >>
> >>  No, these streams are not alternatives to each other in the regular
> >>  sense.  Nor is this really used in offer/answer;  it's more an issue
> >>  for multicast.  In multicast, you open the tune-in stream and the
> >>  base stream, grab the first I-frame that arrives (in either) and then
> >>  drop the tune-in stream.
> >>
> >>  Yes, we're aware that the recipient needs to be able to tell which is
> >>  the base and which is the tune-in.
> >>
> >>  >If this is the case I have similar requirements and
> >>  >would be happy to support such work.
> >>  >
> >>  >You also need a way to give semantics to the "repair" stream, this
> can
> >>  >be done based on the content attribute from RFC 4796 or using a
> >>  >dependency attribute see in Schierl's draft. The mid tag is not
> enough
> >>  >for the receiver to know what you meant by this offer and which
> stream
> >>  >is the repair.
> >>  >
> >>  >Here is an example for a solution using a new Alternatives grouping
> >>  >attribute and giving semantics to the repair stream
> >>  >
> >>  >By using the grouping attribute in the offer you can know if the
> >>  >answerer understood the grouping since if he does not than he will
> send
> >>  >an answer with no a=group
> >>  >
> >>  >v=0
> >>  >o=bob 280744730 28977631 IN IP4 host.example.com
> >>  >s=
> >>  >t=0 0
> >>  >
> >>  >a=group:ALTS 1 2
> >>  >a=group:ALTS 1 3
> >>  >
> >>  >m=audio 6886 RTP/AVP 0
> >>  >c=IN IP6 2001:0600::1
> >>  >a=mid:1
> >>  >
> >>  >m=video 9000 RTP/AVP 100
> >>  >c=IN IP4 192.0.2.2
> >>  >a=rtpmap:100 H263-1998
> >>  >a=mid:2
> >>  >
> >>  >m=video 9002 RTP/AVP 101
> >>  >c=IN IP4 192.0.2.2
> >>  >a=rtpmap:101 H263-1998
> >>  >a=mid:3
> >>  >a=content:repair=2 or a=depend:repair=2
> >>  >
> >>  >
> >>  >Roni Even
> >>  >
> >>  >>  -----Original Message-----
> >>  >>  From: Dave Singer [mailto:singer@apple.com]
> >>  >>  Sent: Monday, June 04, 2007 7:19 PM
> >>  >>  To: mmusic; IETF AVT WG
> >>  >>  Cc: Clinton Priddle (KI/EAB)
> >>  >>  Subject: [MMUSIC] questions about grouping media streams in RTP
> and
> >>  >SDP
> >>  >>  (RFC3388 etc), advice needed
> >>  >>
> >>  >>  Hi
> >>  >>
> >>  >>  we have a need to group together two media streams, in the style
> of
> >>  >RFC
> >>  >>  3388 <http://www.ietf.org/rfc/rfc3388.txt> but we're unsure
> whether an
> >>  >>  existing group type is suitable or not, and if it's not, we'd like
> to
> >>  >>  agree on a new one, and document it (presumably in an RFC).
> >>  >>
> >>  >>  What we have is a normal media stream, and a separate 'repair' or
> >  > >>  'entry' stream, that can be used when tuning in, or after loss,
> but is
> >>  >>  otherwise un-needed.  An example might be a video stream with a
> low
> >>  >>  I-frame interval (say every 15 seconds), with a repair stream
> which
> >>  >has
> >>  >>  only I-frames that are equivalent to the time-parallel non-I
> frame, at
> >>  >a
> >>  >>  frequency of say 1 per second.
> >>  >>
> >>  >>  It's not clear to us whether this is "one media flow" in the sense
> of
> >>  >>  FID, or not.  The example offers AMR and GSM audio, which are
> >>  >>  alternatives, and DTMF tones along with audio, which are
> supplementary
> >>  >>  to each other.  Perhaps we fall afoul of this restriction:
> >>  >>
> >>  >>  "An application that encodes the same media using different codecs
> >>  >>  simultaneously MUST NOT use FID to group those media lines."
> >>  >>
> >>  >>  or this one, for layered encoding:
> >>  >>
> >>  >>  "FID MUST NOT be used to group "m" lines that do not represent the
> >>  >same
> >>  >>  information."  (Though how DTMF tones and their associated audio
> pass
> >>  >>  this test is not clear).
> >>  >>
> >>  >>  Nor is it clear that the FEC group of RFC 4756 is right, either.
> For
> >>  >a
> >>  >>  start, we may wish to use this new ID in combination with FEC, and
> >>  >>  secondly this tune-in stream has different characteristics.  For
> >>  >>  example, one can typically ignore all FEC and (as long as there
> are no
> >>  >>  errors) decode the stream correctly.  Ignoring the tune-in stream
> >>  >  > entirely may mean that you will never find a tune-in point,
> making
> >>  the
> >>  >>  normal stream useless.
> >>  >>
> >>  >>  So, can we use FID for associating a repair stream with its base
> (we
> >>  >tag
> >>  >>  the streams so we know which is which, of course)?
> >>  >>
> >>  >>  p.s. RFC 4756 claims in the IANA section that the FEC group is
> >>  >>  registered under SDP characteristics, but actually I can find no
> >>  >>  registry anywhere in IANA of group types.
> >>  >>
> >>  >>
> >>  >>  --
> >>  >>  David Singer
> >>  >>  Apple/QuickTime
> >>  >>
> >>  >>  _______________________________________________
> >>  >>  mmusic mailing list
> >>  >>  mmusic@ietf.org
> >>  >>  https://www1.ietf.org/mailman/listinfo/mmusic
> >>
> >>
> >>  --
> >>  David Singer
> >>  Apple/QuickTime
> >>
> >>  _______________________________________________
> >>  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 Jun 07 17:47: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 1HwPpG-0003P8-Bh; Thu, 07 Jun 2007 17:47:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwPpF-0003Nx-S2; Thu, 07 Jun 2007 17:47:25 -0400
Received: from mail.hhi.fraunhofer.de ([193.174.67.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HwPpE-0002p2-LW; Thu, 07 Jun 2007 17:47:25 -0400
Received: by mail.hhi.fraunhofer.de (Postfix, from userid 65534)
	id BD4E71D88F82; Thu,  7 Jun 2007 23:47:23 +0200 (CEST)
Received: from ipam040189 (DNab423247.Stanford.EDU [171.66.50.71])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(Client did not present a certificate)
	by mail.hhi.fraunhofer.de (Postfix) with ESMTP id 8E49B1D88F5A;
	Thu,  7 Jun 2007 23:47:15 +0200 (CEST)
From: "Thomas Schierl" <schierl@hhi.fhg.de>
To: "'Even, Roni'" <roni.even@polycom.co.il>,
	"'Dave Singer'" <singer@apple.com>, "'mmusic'" <mmusic@ietf.org>,
	"'IETF AVT WG'" <avt@ietf.org>
References: <000101c7a92b$c4752d50$595c40ab@ipam040189>
	<144ED8561CE90C41A3E5908EDECE315C049E7C50@IsrExch01.israel.polycom.com>
Subject: RE: [AVT] RE: [MMUSIC] questions about grouping media streams in RTP
	andSDP (RFC3388 etc), advice needed
Date: Thu, 7 Jun 2007 14:47:12 -0700
Organization: HHI/FhG
Message-ID: <009701c7a94d$6a4bb1b0$473242ab@ipam040189>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AcenhyxcbwKgryeQTM2S+JPzrTemewBpEXzgAATpg+AAAz/K0A==
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C049E7C50@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.9 required=5.0 tests=BAYES_00, USER_IN_WHITELIST 
	autolearn=ham version=2.64
X-alterMIME: Yes
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 17bdfcaea25d1444baef0e24abc38874
Cc: "'Clinton Priddle \(KI/EAB\)'" <clinton.priddle@ericsson.com>,
	Stephan.Wenger@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,

Then it would be something like we call 'mdc'. But I would like to put that
into an extra dependency type, since the characteristics of the streams are
different, even if they could be used exchangeable. But there is one main
stream, let us say. And that one should be identifiable.

Thomas

> -----Original Message-----
> From: Even, Roni [mailto:roni.even@polycom.co.il]
> Sent: Thursday, June 07, 2007 1:07 PM
> To: Thomas Schierl; Dave Singer; mmusic; IETF AVT WG
> Cc: Stephan.Wenger@nokia.com; Clinton Priddle (KI/EAB)
> Subject: RE: [AVT] RE: [MMUSIC] questions about grouping media streams in
> RTP andSDP (RFC3388 etc), advice needed
> 
> Hi,
> My view is that you have similarity in the need for dependencies between
> streams but the grouping logic is different.
> In the layered codec the grouping is for a group that you can use all or
> part of while in the repair case you may take one or the other.
> 
> Roni Even
> 
> > -----Original Message-----
> > From: Thomas Schierl [mailto:schierl@hhi.fhg.de]
> > Sent: Thursday, June 07, 2007 8:46 PM
> > To: 'Dave Singer'; Even, Roni; 'mmusic'; 'IETF AVT WG'
> > Cc: Stephan.Wenger@nokia.com; 'Clinton Priddle (KI/EAB)'
> > Subject: RE: [AVT] RE: [MMUSIC] questions about grouping media streams
> in
> > RTP andSDP (RFC3388 etc), advice needed
> >
> > Hi Dave,
> >
> > I think there is a strong relation of your problem and the
> >
> http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered-codec-03.tx
> t
> > In this draft, we described media dependency in general, not only for
> > scalable video. Currently, two types of dependencies are defined:
> layered
> > and mdc assuming the media is partially transported in different RTP
> > sessions. There is not requirement, that the part of the media is
> > independently decodable. It would be easy to integrate your needs, if
> they
> > should not be already covered.
> >
> >
> > Thomas
> >
> > > -----Original Message-----
> > > From: Dave Singer [mailto:singer@apple.com]
> > > Sent: Tuesday, June 05, 2007 8:34 AM
> > > To: Even, Roni; mmusic; IETF AVT WG
> > > Cc: Clinton Priddle (KI/EAB)
> > > Subject: [AVT] RE: [MMUSIC] questions about grouping media streams
> in
> > RTP
> > > andSDP (RFC3388 etc), advice needed
> > >
> > > At 10:03  +0300 5/06/07, Even, Roni wrote:
> > > >Dave,
> > > >For layered encoding there is a proposal for a new grouping
> attribute
> > in
> > > >http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered-codec-
> > 03.tx
> > > >t
> > >
> > > I don't think this is a layered coding issue, either, alas.
> > >
> > > >I looked at RFC3388 and I think that FID is not the answer to your
> > > >requirement as you mentioned
> > > >
> > > >To me it looks like what you are looking for is a way to specify
> > > >alternate offers.
> > >
> > > No, these streams are not alternatives to each other in the regular
> > > sense.  Nor is this really used in offer/answer;  it's more an issue
> > > for multicast.  In multicast, you open the tune-in stream and the
> > > base stream, grab the first I-frame that arrives (in either) and
> then
> > > drop the tune-in stream.
> > >
> > > Yes, we're aware that the recipient needs to be able to tell which
> is
> > > the base and which is the tune-in.
> > >
> > > >If this is the case I have similar requirements and
> > > >would be happy to support such work.
> > > >
> > > >You also need a way to give semantics to the "repair" stream, this
> can
> > > >be done based on the content attribute from RFC 4796 or using a
> > > >dependency attribute see in Schierl's draft. The mid tag is not
> enough
> > > >for the receiver to know what you meant by this offer and which
> stream
> > > >is the repair.
> > > >
> > > >Here is an example for a solution using a new Alternatives grouping
> > > >attribute and giving semantics to the repair stream
> > > >
> > > >By using the grouping attribute in the offer you can know if the
> > > >answerer understood the grouping since if he does not than he will
> send
> > > >an answer with no a=group
> > > >
> > > >v=0
> > > >o=bob 280744730 28977631 IN IP4 host.example.com
> > > >s=
> > > >t=0 0
> > > >
> > > >a=group:ALTS 1 2
> > > >a=group:ALTS 1 3
> > > >
> > > >m=audio 6886 RTP/AVP 0
> > > >c=IN IP6 2001:0600::1
> > > >a=mid:1
> > > >
> > > >m=video 9000 RTP/AVP 100
> > > >c=IN IP4 192.0.2.2
> > > >a=rtpmap:100 H263-1998
> > > >a=mid:2
> > > >
> > > >m=video 9002 RTP/AVP 101
> > > >c=IN IP4 192.0.2.2
> > > >a=rtpmap:101 H263-1998
> > > >a=mid:3
> > > >a=content:repair=2 or a=depend:repair=2
> > > >
> > > >
> > > >Roni Even
> > > >
> > > >>  -----Original Message-----
> > > >>  From: Dave Singer [mailto:singer@apple.com]
> > > >>  Sent: Monday, June 04, 2007 7:19 PM
> > > >>  To: mmusic; IETF AVT WG
> > > >>  Cc: Clinton Priddle (KI/EAB)
> > > >>  Subject: [MMUSIC] questions about grouping media streams in RTP
> and
> > > >SDP
> > > >>  (RFC3388 etc), advice needed
> > > >>
> > > >>  Hi
> > > >>
> > > >>  we have a need to group together two media streams, in the style
> of
> > > >RFC
> > > >>  3388 <http://www.ietf.org/rfc/rfc3388.txt> but we're unsure
> whether
> > an
> > > >>  existing group type is suitable or not, and if it's not, we'd
> like
> > to
> > > >>  agree on a new one, and document it (presumably in an RFC).
> > > >>
> > > >>  What we have is a normal media stream, and a separate 'repair'
> or
> > > >>  'entry' stream, that can be used when tuning in, or after loss,
> but
> > is
> > > >>  otherwise un-needed.  An example might be a video stream with a
> low
> > > >>  I-frame interval (say every 15 seconds), with a repair stream
> which
> > > >has
> > > >>  only I-frames that are equivalent to the time-parallel non-I
> frame,
> > at
> > > >a
> > > >>  frequency of say 1 per second.
> > > >>
> > > >>  It's not clear to us whether this is "one media flow" in the
> sense
> > of
> > > >>  FID, or not.  The example offers AMR and GSM audio, which are
> > > >>  alternatives, and DTMF tones along with audio, which are
> > supplementary
> > > >>  to each other.  Perhaps we fall afoul of this restriction:
> > > >>
> > > >>  "An application that encodes the same media using different
> codecs
> > > >>  simultaneously MUST NOT use FID to group those media lines."
> > > >>
> > > >>  or this one, for layered encoding:
> > > >>
> > > >>  "FID MUST NOT be used to group "m" lines that do not represent
> the
> > > >same
> > > >>  information."  (Though how DTMF tones and their associated audio
> > pass
> > > >>  this test is not clear).
> > > >>
> > > >>  Nor is it clear that the FEC group of RFC 4756 is right, either.
> > For
> > > >a
> > > >>  start, we may wish to use this new ID in combination with FEC,
> and
> > > >>  secondly this tune-in stream has different characteristics.  For
> > > >>  example, one can typically ignore all FEC and (as long as there
> are
> > no
> > > >>  errors) decode the stream correctly.  Ignoring the tune-in
> stream
> > > >  > entirely may mean that you will never find a tune-in point,
> making
> > > the
> > > >>  normal stream useless.
> > > >>
> > > >>  So, can we use FID for associating a repair stream with its base
> (we
> > > >tag
> > > >>  the streams so we know which is which, of course)?
> > > >>
> > > >>  p.s. RFC 4756 claims in the IANA section that the FEC group is
> > > >>  registered under SDP characteristics, but actually I can find no
> > > >>  registry anywhere in IANA of group types.
> > > >>
> > > >>
> > > >>  --
> > > >>  David Singer
> > > >>  Apple/QuickTime
> > > >>
> > > >>  _______________________________________________
> > > >>  mmusic mailing list
> > > >>  mmusic@ietf.org
> > > >>  https://www1.ietf.org/mailman/listinfo/mmusic
> > >
> > >
> > > --
> > > David Singer
> > > Apple/QuickTime
> > >
> > > _______________________________________________
> > > 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 Jun 07 18:01: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 1HwQ3G-0002Do-RN; Thu, 07 Jun 2007 18:01:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwQ3F-0002Da-7c
	for avt@ietf.org; Thu, 07 Jun 2007 18:01:53 -0400
Received: from stewe.org ([85.214.23.117] helo=h665227.serverkompetenz.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwQ3E-0007YT-8s
	for avt@ietf.org; Thu, 07 Jun 2007 18:01:53 -0400
Received: (qmail 24503 invoked by uid 60000); 7 Jun 2007 20:39:17 -0000
Received: from 75.60.27.134 by h665227 (envelope-from <stewe@stewe.org>,
	uid 60004) with qmail-scanner-1.24st visas (spamassassin: 2.64.  
	Clear:RC:0(75.60.27.134):SA:0(0.0/20.0):. 
	Processed in 0.916741 secs); 07 Jun 2007 20:39:17 -0000
X-Spam-Status: No, hits=0.0 required=20.0
X-Envelope-From: stewe@stewe.org
Received: from adsl-75-60-27-134.dsl.pltn13.sbcglobal.net (HELO
	?192.168.1.100?) (stewe@stewe.org@75.60.27.134)
	by stewe.org with SMTP; 7 Jun 2007 20:39:16 -0000
In-Reply-To: <009701c7a94d$6a4bb1b0$473242ab@ipam040189>
References: <000101c7a92b$c4752d50$595c40ab@ipam040189>
	<144ED8561CE90C41A3E5908EDECE315C049E7C50@IsrExch01.israel.polycom.com>
	<009701c7a94d$6a4bb1b0$473242ab@ipam040189>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <66A2BDF7-0556-47C5-84A1-2CCE959A264A@stewe.org>
Content-Transfer-Encoding: 7bit
From: Stephan Wenger <stewe@stewe.org>
Subject: Re: [AVT] RE: [MMUSIC] questions about grouping media streams in RTP
	andSDP (RFC3388 etc), advice needed
Date: Thu, 7 Jun 2007 15:01:42 -0700
To: Thomas Schierl <schierl@hhi.fhg.de>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on 
	h665227.serverkompetenz.net
X-Spam-Level: 
X-Qmail-Scanner-MOVED-X-Spam-Status: No, hits=0.0 required=20.0 tests=none
	autolearn=no version=2.64
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 27ec2ff0f5c3b18b49c722f4f1748838
Cc: "'Clinton Priddle \(KI/EAB\)'" <clinton.priddle@ericsson.com>, "'Even,
	Roni'" <roni.even@polycom.co.il>,
	'Dave Singer' <singer@apple.com>, 'IETF AVT WG' <avt@ietf.org>,
	'mmusic' <mmusic@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Yes, and if this were a non-exotic use case, we would need such a  
type.  As it IS an exotic use case, I guess we can survive with 3GPP  
specifying the "normal" stream having a lower port number than the  
"repair" stream, or something like this.
(Now go out and blast me for unclean design choices. :-)
Stephan

On Jun 7, 2007, at 2:47 PM, Thomas Schierl wrote:

> Hi Roni,
>
> Then it would be something like we call 'mdc'. But I would like to  
> put that
> into an extra dependency type, since the characteristics of the  
> streams are
> different, even if they could be used exchangeable. But there is  
> one main
> stream, let us say. And that one should be identifiable.
>
> Thomas
>
>> -----Original Message-----
>> From: Even, Roni [mailto:roni.even@polycom.co.il]
>> Sent: Thursday, June 07, 2007 1:07 PM
>> To: Thomas Schierl; Dave Singer; mmusic; IETF AVT WG
>> Cc: Stephan.Wenger@nokia.com; Clinton Priddle (KI/EAB)
>> Subject: RE: [AVT] RE: [MMUSIC] questions about grouping media  
>> streams in
>> RTP andSDP (RFC3388 etc), advice needed
>>
>> Hi,
>> My view is that you have similarity in the need for dependencies  
>> between
>> streams but the grouping logic is different.
>> In the layered codec the grouping is for a group that you can use  
>> all or
>> part of while in the repair case you may take one or the other.
>>
>> Roni Even
>>
>>> -----Original Message-----
>>> From: Thomas Schierl [mailto:schierl@hhi.fhg.de]
>>> Sent: Thursday, June 07, 2007 8:46 PM
>>> To: 'Dave Singer'; Even, Roni; 'mmusic'; 'IETF AVT WG'
>>> Cc: Stephan.Wenger@nokia.com; 'Clinton Priddle (KI/EAB)'
>>> Subject: RE: [AVT] RE: [MMUSIC] questions about grouping media  
>>> streams
>> in
>>> RTP andSDP (RFC3388 etc), advice needed
>>>
>>> Hi Dave,
>>>
>>> I think there is a strong relation of your problem and the
>>>
>> http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered- 
>> codec-03.tx
>> t
>>> In this draft, we described media dependency in general, not only  
>>> for
>>> scalable video. Currently, two types of dependencies are defined:
>> layered
>>> and mdc assuming the media is partially transported in different RTP
>>> sessions. There is not requirement, that the part of the media is
>>> independently decodable. It would be easy to integrate your  
>>> needs, if
>> they
>>> should not be already covered.
>>>
>>>
>>> Thomas
>>>
>>>> -----Original Message-----
>>>> From: Dave Singer [mailto:singer@apple.com]
>>>> Sent: Tuesday, June 05, 2007 8:34 AM
>>>> To: Even, Roni; mmusic; IETF AVT WG
>>>> Cc: Clinton Priddle (KI/EAB)
>>>> Subject: [AVT] RE: [MMUSIC] questions about grouping media streams
>> in
>>> RTP
>>>> andSDP (RFC3388 etc), advice needed
>>>>
>>>> At 10:03  +0300 5/06/07, Even, Roni wrote:
>>>>> Dave,
>>>>> For layered encoding there is a proposal for a new grouping
>> attribute
>>> in
>>>>> http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered- 
>>>>> codec-
>>> 03.tx
>>>>> t
>>>>
>>>> I don't think this is a layered coding issue, either, alas.
>>>>
>>>>> I looked at RFC3388 and I think that FID is not the answer to your
>>>>> requirement as you mentioned
>>>>>
>>>>> To me it looks like what you are looking for is a way to specify
>>>>> alternate offers.
>>>>
>>>> No, these streams are not alternatives to each other in the regular
>>>> sense.  Nor is this really used in offer/answer;  it's more an  
>>>> issue
>>>> for multicast.  In multicast, you open the tune-in stream and the
>>>> base stream, grab the first I-frame that arrives (in either) and
>> then
>>>> drop the tune-in stream.
>>>>
>>>> Yes, we're aware that the recipient needs to be able to tell which
>> is
>>>> the base and which is the tune-in.
>>>>
>>>>> If this is the case I have similar requirements and
>>>>> would be happy to support such work.
>>>>>
>>>>> You also need a way to give semantics to the "repair" stream, this
>> can
>>>>> be done based on the content attribute from RFC 4796 or using a
>>>>> dependency attribute see in Schierl's draft. The mid tag is not
>> enough
>>>>> for the receiver to know what you meant by this offer and which
>> stream
>>>>> is the repair.
>>>>>
>>>>> Here is an example for a solution using a new Alternatives  
>>>>> grouping
>>>>> attribute and giving semantics to the repair stream
>>>>>
>>>>> By using the grouping attribute in the offer you can know if the
>>>>> answerer understood the grouping since if he does not than he will
>> send
>>>>> an answer with no a=group
>>>>>
>>>>> v=0
>>>>> o=bob 280744730 28977631 IN IP4 host.example.com
>>>>> s=
>>>>> t=0 0
>>>>>
>>>>> a=group:ALTS 1 2
>>>>> a=group:ALTS 1 3
>>>>>
>>>>> m=audio 6886 RTP/AVP 0
>>>>> c=IN IP6 2001:0600::1
>>>>> a=mid:1
>>>>>
>>>>> m=video 9000 RTP/AVP 100
>>>>> c=IN IP4 192.0.2.2
>>>>> a=rtpmap:100 H263-1998
>>>>> a=mid:2
>>>>>
>>>>> m=video 9002 RTP/AVP 101
>>>>> c=IN IP4 192.0.2.2
>>>>> a=rtpmap:101 H263-1998
>>>>> a=mid:3
>>>>> a=content:repair=2 or a=depend:repair=2
>>>>>
>>>>>
>>>>> Roni Even
>>>>>
>>>>>>  -----Original Message-----
>>>>>>  From: Dave Singer [mailto:singer@apple.com]
>>>>>>  Sent: Monday, June 04, 2007 7:19 PM
>>>>>>  To: mmusic; IETF AVT WG
>>>>>>  Cc: Clinton Priddle (KI/EAB)
>>>>>>  Subject: [MMUSIC] questions about grouping media streams in RTP
>> and
>>>>> SDP
>>>>>>  (RFC3388 etc), advice needed
>>>>>>
>>>>>>  Hi
>>>>>>
>>>>>>  we have a need to group together two media streams, in the style
>> of
>>>>> RFC
>>>>>>  3388 <http://www.ietf.org/rfc/rfc3388.txt> but we're unsure
>> whether
>>> an
>>>>>>  existing group type is suitable or not, and if it's not, we'd
>> like
>>> to
>>>>>>  agree on a new one, and document it (presumably in an RFC).
>>>>>>
>>>>>>  What we have is a normal media stream, and a separate 'repair'
>> or
>>>>>>  'entry' stream, that can be used when tuning in, or after loss,
>> but
>>> is
>>>>>>  otherwise un-needed.  An example might be a video stream with a
>> low
>>>>>>  I-frame interval (say every 15 seconds), with a repair stream
>> which
>>>>> has
>>>>>>  only I-frames that are equivalent to the time-parallel non-I
>> frame,
>>> at
>>>>> a
>>>>>>  frequency of say 1 per second.
>>>>>>
>>>>>>  It's not clear to us whether this is "one media flow" in the
>> sense
>>> of
>>>>>>  FID, or not.  The example offers AMR and GSM audio, which are
>>>>>>  alternatives, and DTMF tones along with audio, which are
>>> supplementary
>>>>>>  to each other.  Perhaps we fall afoul of this restriction:
>>>>>>
>>>>>>  "An application that encodes the same media using different
>> codecs
>>>>>>  simultaneously MUST NOT use FID to group those media lines."
>>>>>>
>>>>>>  or this one, for layered encoding:
>>>>>>
>>>>>>  "FID MUST NOT be used to group "m" lines that do not represent
>> the
>>>>> same
>>>>>>  information."  (Though how DTMF tones and their associated audio
>>> pass
>>>>>>  this test is not clear).
>>>>>>
>>>>>>  Nor is it clear that the FEC group of RFC 4756 is right, either.
>>> For
>>>>> a
>>>>>>  start, we may wish to use this new ID in combination with FEC,
>> and
>>>>>>  secondly this tune-in stream has different characteristics.  For
>>>>>>  example, one can typically ignore all FEC and (as long as there
>> are
>>> no
>>>>>>  errors) decode the stream correctly.  Ignoring the tune-in
>> stream
>>>>>> entirely may mean that you will never find a tune-in point,
>> making
>>>> the
>>>>>>  normal stream useless.
>>>>>>
>>>>>>  So, can we use FID for associating a repair stream with its base
>> (we
>>>>> tag
>>>>>>  the streams so we know which is which, of course)?
>>>>>>
>>>>>>  p.s. RFC 4756 claims in the IANA section that the FEC group is
>>>>>>  registered under SDP characteristics, but actually I can find no
>>>>>>  registry anywhere in IANA of group types.
>>>>>>
>>>>>>
>>>>>>  --
>>>>>>  David Singer
>>>>>>  Apple/QuickTime
>>>>>>
>>>>>>  _______________________________________________
>>>>>>  mmusic mailing list
>>>>>>  mmusic@ietf.org
>>>>>>  https://www1.ietf.org/mailman/listinfo/mmusic
>>>>
>>>>
>>>> --
>>>> David Singer
>>>> Apple/QuickTime
>>>>
>>>> _______________________________________________
>>>> 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 Jun 07 21:37: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 1HwTPK-00049X-N9; Thu, 07 Jun 2007 21:36:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwTPJ-00049D-G6
	for avt@ietf.org; Thu, 07 Jun 2007 21:36:53 -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 1HwTOL-0002Sr-1v for avt@ietf.org; Thu, 07 Jun 2007 21:35:54 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 7 Jun 2007 21:35:52 -0400
To: "Even, Roni" <roni.even@polycom.co.il>
Subject: Re: [AVT] H264 Frame rate
References: <144ED8561CE90C41A3E5908EDECE315C049E7C2B@IsrExch01.israel.polycom.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Thu, 07 Jun 2007 21:35:51 -0400
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C049E7C2B@IsrExch01.israel.polycom.com>
	(Roni Even's message of "Thu, 7 Jun 2007 19:22:34 +0300")
Message-ID: <ybuejknmdmw.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 Jun 2007 01:35:52.0740 (UTC)
	FILETIME=[59DAF640:01C7A96D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: "Ajmal, Humayun" <Humayun_Ajmal@mentor.com>, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

"Even, Roni" <roni.even@polycom.co.il> writes:
>Look at max-mbps, max-fs attributes. Using the maximum macro blocks per
>second and maximum frame size you can calculate the frame rate

Not the actual frame rate, but the maximum possible frame rate at the
maximum frame size.  A receiver may support a higher frame rate at a lower
frame size, and it may be proportional to max-mbps/actual-frame-size, but
nothing directly tells you the frame rate that can be displayed.

I.e., with an implementation that supports 30fps @CIF, in theory it may
support 120fps @ QCIF, but there's no guarantee it will be able to display
120fps.  Also, there's undoubtably per-frame overhead, so max-mbps is only
a rough approximation of the decoders capabilities.

-- 
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 Jun 08 03:38: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 1HwZ36-0008OP-G4; Fri, 08 Jun 2007 03:38:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwZ34-0008J6-Ro; Fri, 08 Jun 2007 03:38:18 -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 1HwZ30-00047R-AF; Fri, 08 Jun 2007 03:38:18 -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] RE: [MMUSIC] questions about grouping media streams in RTP
	andSDP (RFC3388 etc), advice needed
Date: Fri, 8 Jun 2007 10:39:02 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C049E7C74@IsrExch01.israel.polycom.com>
In-Reply-To: <009701c7a94d$6a4bb1b0$473242ab@ipam040189>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] RE: [MMUSIC] questions about grouping media streams in RTP
	andSDP (RFC3388 etc), advice needed
Thread-Index: AcenhyxcbwKgryeQTM2S+JPzrTemewBpEXzgAATpg+AAAz/K0AAUeDVw
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Thomas Schierl" <schierl@hhi.fhg.de>, "Dave Singer" <singer@apple.com>,
	"mmusic" <mmusic@ietf.org>, "IETF AVT WG" <avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9c7d7a899dc8f3389bf7ace6f0ad8e29
Cc: "Clinton Priddle \(KI/EAB\)" <clinton.priddle@ericsson.com>,
	Stephan.Wenger@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

Thomas,
I already wrote that we need to look at the general case before going to
a specific solution.

Currently for a media stream we have a way to mark a stream using the
label attribute. We have a way to apply semantics to a single stream
using the content attribute. What we are doing here is defining
semantics to a group of streams by using dependency attribute. The
parameter for the dependency does not have to be the same for all cases
and depends on what you want. As for tagging the dependencies it may be
the mid number or use a label.

Now the second part that is needed is to specify the grouping, we have a
grouping attribute but it lacks some parameters for the layered codecs
and the repair stream.=20
I would like to add to this the case of simple alternate attributes. For
example I can do G.711 with two H.263 video streams or G.711 with one
H.264 video stream.

I see two cases for the group, one for alternate streams and the other
for a set of streams. The advantage of using the group attribute is that
if the other side does not support it, he will remove it from the
answer.

Here are examples for both

Alternate: here you may use 1 and 2  or 1 and 3


a=3Dgroup:ALTS:1 1 2
a=3Dgroup:ALTS:1 1 3=20

m=3Daudio 6886 RTP/AVP 0
c=3DIN IP6 2001:0600::1
a=3Dmid:1=20

m=3Dvideo 9000 RTP/AVP 100
c=3DIN IP4 192.0.2.2
a=3Drtpmap:100 H263-1998
a=3Dmid:2=20

m=3Dvideo 9002 RTP/AVP 101
c=3DIN IP4 192.0.2.2
a=3Drtpmap:101 H263-1998
a=3Dmid:3


For a SET here you say that 2 and 3 are a set for layering

a=3Dgroup:SET 2 3


m=3Daudio 6886 RTP/AVP 0
c=3DIN IP6 2001:0600::1
a=3Dmid:1=20

m=3Dvideo 9000 RTP/AVP 100
c=3DIN IP4 192.0.2.2
a=3Drtpmap:100 H263-1998
a=3Dmid:2=20

m=3Dvideo 9002 RTP/AVP 101
c=3DIN IP4 192.0.2.2
a=3Drtpmap:101 H263-1998
a=3Dmid:3
a=3Dcontent:repair=3D2 or a=3Ddepend:repair=3D2

Roni

> -----Original Message-----
> From: Thomas Schierl [mailto:schierl@hhi.fhg.de]
> Sent: Friday, June 08, 2007 12:47 AM
> To: Even, Roni; 'Dave Singer'; 'mmusic'; 'IETF AVT WG'
> Cc: Stephan.Wenger@nokia.com; 'Clinton Priddle (KI/EAB)'
> Subject: RE: [AVT] RE: [MMUSIC] questions about grouping media streams
in
> RTP andSDP (RFC3388 etc), advice needed
>=20
> Hi Roni,
>=20
> Then it would be something like we call 'mdc'. But I would like to put
> that
> into an extra dependency type, since the characteristics of the
streams
> are
> different, even if they could be used exchangeable. But there is one
main
> stream, let us say. And that one should be identifiable.
>=20
> Thomas
>=20
> > -----Original Message-----
> > From: Even, Roni [mailto:roni.even@polycom.co.il]
> > Sent: Thursday, June 07, 2007 1:07 PM
> > To: Thomas Schierl; Dave Singer; mmusic; IETF AVT WG
> > Cc: Stephan.Wenger@nokia.com; Clinton Priddle (KI/EAB)
> > Subject: RE: [AVT] RE: [MMUSIC] questions about grouping media
streams
> in
> > RTP andSDP (RFC3388 etc), advice needed
> >
> > Hi,
> > My view is that you have similarity in the need for dependencies
between
> > streams but the grouping logic is different.
> > In the layered codec the grouping is for a group that you can use
all or
> > part of while in the repair case you may take one or the other.
> >
> > Roni Even
> >
> > > -----Original Message-----
> > > From: Thomas Schierl [mailto:schierl@hhi.fhg.de]
> > > Sent: Thursday, June 07, 2007 8:46 PM
> > > To: 'Dave Singer'; Even, Roni; 'mmusic'; 'IETF AVT WG'
> > > Cc: Stephan.Wenger@nokia.com; 'Clinton Priddle (KI/EAB)'
> > > Subject: RE: [AVT] RE: [MMUSIC] questions about grouping media
streams
> > in
> > > RTP andSDP (RFC3388 etc), advice needed
> > >
> > > Hi Dave,
> > >
> > > I think there is a strong relation of your problem and the
> > >
> >
http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered-codec-03.tx
> > t
> > > In this draft, we described media dependency in general, not only
for
> > > scalable video. Currently, two types of dependencies are defined:
> > layered
> > > and mdc assuming the media is partially transported in different
RTP
> > > sessions. There is not requirement, that the part of the media is
> > > independently decodable. It would be easy to integrate your needs,
if
> > they
> > > should not be already covered.
> > >
> > >
> > > Thomas
> > >
> > > > -----Original Message-----
> > > > From: Dave Singer [mailto:singer@apple.com]
> > > > Sent: Tuesday, June 05, 2007 8:34 AM
> > > > To: Even, Roni; mmusic; IETF AVT WG
> > > > Cc: Clinton Priddle (KI/EAB)
> > > > Subject: [AVT] RE: [MMUSIC] questions about grouping media
streams
> > in
> > > RTP
> > > > andSDP (RFC3388 etc), advice needed
> > > >
> > > > At 10:03  +0300 5/06/07, Even, Roni wrote:
> > > > >Dave,
> > > > >For layered encoding there is a proposal for a new grouping
> > attribute
> > > in
> > > >
>http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered-codec-
> > > 03.tx
> > > > >t
> > > >
> > > > I don't think this is a layered coding issue, either, alas.
> > > >
> > > > >I looked at RFC3388 and I think that FID is not the answer to
your
> > > > >requirement as you mentioned
> > > > >
> > > > >To me it looks like what you are looking for is a way to
specify
> > > > >alternate offers.
> > > >
> > > > No, these streams are not alternatives to each other in the
regular
> > > > sense.  Nor is this really used in offer/answer;  it's more an
issue
> > > > for multicast.  In multicast, you open the tune-in stream and
the
> > > > base stream, grab the first I-frame that arrives (in either) and
> > then
> > > > drop the tune-in stream.
> > > >
> > > > Yes, we're aware that the recipient needs to be able to tell
which
> > is
> > > > the base and which is the tune-in.
> > > >
> > > > >If this is the case I have similar requirements and
> > > > >would be happy to support such work.
> > > > >
> > > > >You also need a way to give semantics to the "repair" stream,
this
> > can
> > > > >be done based on the content attribute from RFC 4796 or using a
> > > > >dependency attribute see in Schierl's draft. The mid tag is not
> > enough
> > > > >for the receiver to know what you meant by this offer and which
> > stream
> > > > >is the repair.
> > > > >
> > > > >Here is an example for a solution using a new Alternatives
grouping
> > > > >attribute and giving semantics to the repair stream
> > > > >
> > > > >By using the grouping attribute in the offer you can know if
the
> > > > >answerer understood the grouping since if he does not than he
will
> > send
> > > > >an answer with no a=3Dgroup
> > > > >
> > > > >v=3D0
> > > > >o=3Dbob 280744730 28977631 IN IP4 host.example.com
> > > > >s=3D
> > > > >t=3D0 0
> > > > >
> > > > >a=3Dgroup:ALTS 1 2
> > > > >a=3Dgroup:ALTS 1 3
> > > > >
> > > > >m=3Daudio 6886 RTP/AVP 0
> > > > >c=3DIN IP6 2001:0600::1
> > > > >a=3Dmid:1
> > > > >
> > > > >m=3Dvideo 9000 RTP/AVP 100
> > > > >c=3DIN IP4 192.0.2.2
> > > > >a=3Drtpmap:100 H263-1998
> > > > >a=3Dmid:2
> > > > >
> > > > >m=3Dvideo 9002 RTP/AVP 101
> > > > >c=3DIN IP4 192.0.2.2
> > > > >a=3Drtpmap:101 H263-1998
> > > > >a=3Dmid:3
> > > > >a=3Dcontent:repair=3D2 or a=3Ddepend:repair=3D2
> > > > >
> > > > >
> > > > >Roni Even
> > > > >
> > > > >>  -----Original Message-----
> > > > >>  From: Dave Singer [mailto:singer@apple.com]
> > > > >>  Sent: Monday, June 04, 2007 7:19 PM
> > > > >>  To: mmusic; IETF AVT WG
> > > > >>  Cc: Clinton Priddle (KI/EAB)
> > > > >>  Subject: [MMUSIC] questions about grouping media streams in
RTP
> > and
> > > > >SDP
> > > > >>  (RFC3388 etc), advice needed
> > > > >>
> > > > >>  Hi
> > > > >>
> > > > >>  we have a need to group together two media streams, in the
style
> > of
> > > > >RFC
> > > > >>  3388 <http://www.ietf.org/rfc/rfc3388.txt> but we're unsure
> > whether
> > > an
> > > > >>  existing group type is suitable or not, and if it's not,
we'd
> > like
> > > to
> > > > >>  agree on a new one, and document it (presumably in an RFC).
> > > > >>
> > > > >>  What we have is a normal media stream, and a separate
'repair'
> > or
> > > > >>  'entry' stream, that can be used when tuning in, or after
loss,
> > but
> > > is
> > > > >>  otherwise un-needed.  An example might be a video stream
with a
> > low
> > > > >>  I-frame interval (say every 15 seconds), with a repair
stream
> > which
> > > > >has
> > > > >>  only I-frames that are equivalent to the time-parallel non-I
> > frame,
> > > at
> > > > >a
> > > > >>  frequency of say 1 per second.
> > > > >>
> > > > >>  It's not clear to us whether this is "one media flow" in the
> > sense
> > > of
> > > > >>  FID, or not.  The example offers AMR and GSM audio, which
are
> > > > >>  alternatives, and DTMF tones along with audio, which are
> > > supplementary
> > > > >>  to each other.  Perhaps we fall afoul of this restriction:
> > > > >>
> > > > >>  "An application that encodes the same media using different
> > codecs
> > > > >>  simultaneously MUST NOT use FID to group those media lines."
> > > > >>
> > > > >>  or this one, for layered encoding:
> > > > >>
> > > > >>  "FID MUST NOT be used to group "m" lines that do not
represent
> > the
> > > > >same
> > > > >>  information."  (Though how DTMF tones and their associated
audio
> > > pass
> > > > >>  this test is not clear).
> > > > >>
> > > > >>  Nor is it clear that the FEC group of RFC 4756 is right,
either.
> > > For
> > > > >a
> > > > >>  start, we may wish to use this new ID in combination with
FEC,
> > and
> > > > >>  secondly this tune-in stream has different characteristics.
For
> > > > >>  example, one can typically ignore all FEC and (as long as
there
> > are
> > > no
> > > > >>  errors) decode the stream correctly.  Ignoring the tune-in
> > stream
> > > > >  > entirely may mean that you will never find a tune-in point,
> > making
> > > > the
> > > > >>  normal stream useless.
> > > > >>
> > > > >>  So, can we use FID for associating a repair stream with its
base
> > (we
> > > > >tag
> > > > >>  the streams so we know which is which, of course)?
> > > > >>
> > > > >>  p.s. RFC 4756 claims in the IANA section that the FEC group
is
> > > > >>  registered under SDP characteristics, but actually I can
find no
> > > > >>  registry anywhere in IANA of group types.
> > > > >>
> > > > >>
> > > > >>  --
> > > > >>  David Singer
> > > > >>  Apple/QuickTime
> > > > >>
> > > > >>  _______________________________________________
> > > > >>  mmusic mailing list
> > > > >>  mmusic@ietf.org
> > > > >>  https://www1.ietf.org/mailman/listinfo/mmusic
> > > >
> > > >
> > > > --
> > > > David Singer
> > > > Apple/QuickTime
> > > >
> > > > _______________________________________________
> > > > 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 Jun 08 03:52: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 1HwZGB-0005U4-R7; Fri, 08 Jun 2007 03:51:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwZGB-0005Tw-1n
	for avt@ietf.org; Fri, 08 Jun 2007 03:51:51 -0400
Received: from ug-out-1314.google.com ([66.249.92.168])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwZG9-00086x-Cg
	for avt@ietf.org; Fri, 08 Jun 2007 03:51:51 -0400
Received: by ug-out-1314.google.com with SMTP id j30so2320767ugc
	for <avt@ietf.org>; Fri, 08 Jun 2007 00:51:48 -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=Z7/yT4joizvlljdxLCrdqnz2TyCNQZw34XXZupSDHOKJGADEVuvKSjG/6T1Nhq7gjBoVWTR/RxdJQyGwKZmSDzxMNXsiqwF0+RKtNioDESLM62kHIdKrG7FFhXZj2y/ZTvXPmffFB1x8xMylQz9MQVLwqaobu255RfAQqJLOg+c=
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=m0RGmgbbinTdz9vnmyyjWnZan9oMEeMczAN0HH1oVVu1IEHYYOJFXCETPAUjIsWxRpXOVQVpKWTt5qpRyWy5N1eHdq3XMHHoC8HWXIhE2ts2P6Am7jnrhMi7NQrFaP2V3RylXBH7zUWGYDqxS4mtIlX0M7FZB0Rt+dae7WTsYgA=
Received: by 10.78.142.14 with SMTP id p14mr1064262hud.1181289108383;
	Fri, 08 Jun 2007 00:51:48 -0700 (PDT)
Received: by 10.78.140.8 with HTTP; Fri, 8 Jun 2007 00:51:48 -0700 (PDT)
Message-ID: <4e5a3720706080051i72a2af6di52e3e9a65feefe1f@mail.gmail.com>
Date: Fri, 8 Jun 2007 10:51:48 +0300
From: "Murat Artun" <artunmurat@gmail.com>
To: "dieter_schulz@mitel.com" <dieter_schulz@mitel.com>
Subject: Re: [AVT] transmitting g729 bitstream in RTP
In-Reply-To: <OFCA814CF8.2685D3DC-ON852572F3.00628CB2-852572F3.0062B5D3@mitel.com>
MIME-Version: 1.0
References: <OFCA814CF8.2685D3DC-ON852572F3.00628CB2-852572F3.0062B5D3@mitel.com>
X-Spam-Score: 0.8 (/)
X-Scan-Signature: ccfb4541e989aa743998098cd315d0fd
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="===============1537114423=="
Errors-To: avt-bounces@ietf.org

--===============1537114423==
Content-Type: multipart/alternative; 
	boundary="----=_Part_47957_15443235.1181289108357"

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

Sorry, I should have written 10-bytes. Of course, I observe 10-bytes for 10
ms G729 coded voice data.

On 6/7/07, dieter_schulz@mitel.com <dieter_schulz@mitel.com> wrote:
>
>
> I think you have to check your ethereal. 10 ms G729 has 10 bytes (80 bits)
> of payload.
>
> Regards,
> Dieter
> ------------------------------------------------------------
> Dieter Schulz
> Manager: DSP & Media Processing
> Mitel Networks
> Tel: 613-592-2122
> Fax: 613-592-4784
>
>
>
> *"Murat Artun" <artunmurat@gmail.com>*
>
> 06/07/2007 09:56 AM
>
>         To:        avt@ietf.org
>         cc:
>         Subject:        [AVT] transmitting g729 bitstream in RTP
>
>
> Hello,
>
> I want to ask how the 80-bits long (assume G729B is disabled for
> experimental purposes) G729 coded voice data is transmitted using RTP.
>
> ITU test code encoder outputs 11 short integers (parameter vector)
> where these 80-bits are packed following the below scheme:
>
>
> /*----------------------------------------------------------------------------
> * prm2bits_ld8k -converts encoder parameter vector into vector of serial
> bits
> * bits2prm_ld8k - converts serial received bits to  encoder parameter
> vector
> *
> * The transmitted parameters are:
> *
> *     LPC:     1st codebook           7+1 bit
> *              2nd codebook           5+5 bit
> *
> *     1st subframe:
> *          pitch period                 8 bit
> *          parity check on 1st period   1 bit
> *          codebook index1 (positions) 13 bit
> *          codebook index2 (signs)      4 bit
> *          pitch and codebook gains   4+3 bit
> *
> *     2nd subframe:
> *          pitch period (relative)      5 bit
> *          codebook index1 (positions) 13 bit
> *          codebook index2 (signs)      4 bit
> *          pitch and codebook gains   4+3 bit
>
> *----------------------------------------------------------------------------
> */ (from BITS.C of ITU test code)
>
> However, as I have followed the ethereal trace of a G729 voice
> exchange, I see that only 8-bytes are transmitted for each G729 coded
> 10 ms voice data.
>
> Considering the above parameter scheme that was specified to be
> transmitted in the ITU test code, what is the true packing scheme for
> each 10 ms G729 coded coice data?
>
> Thanks in advice...
>
> --
> M u r at  A r t u n, MSc.
>   Software Engineer
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
>
>
>


-- 
M u r at  A r t u n, MSc.
   Software Engineer

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

Sorry, I should have written 10-bytes. Of course, I observe 10-bytes for 10 ms G729 coded voice data.<br><br><div><span class="gmail_quote">On 6/7/07, <b class="gmail_sendername"><a href="mailto:dieter_schulz@mitel.com">dieter_schulz@mitel.com
</a></b> &lt;<a href="mailto:dieter_schulz@mitel.com">dieter_schulz@mitel.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">

<br><font face="sans-serif" size="2">I think you have to check your ethereal. 10 ms G729 has 10 bytes (80 bits) of payload.</font>
<br>
<br><font face="sans-serif" size="2">Regards,</font>
<br><font face="sans-serif" size="2">Dieter</font>
<br><font face="sans-serif" size="2">------------------------------------------------------------<br>
Dieter Schulz<br>
Manager: DSP &amp; Media Processing<br>
Mitel Networks<br>
Tel: 613-592-2122<br>
Fax: 613-592-4784</font>
<br>
<br>
<br>
<table width="100%">
<tbody><tr valign="top">
<td>
<br></td><td><font face="sans-serif" size="1"><b>&quot;Murat Artun&quot; &lt;<a href="mailto:artunmurat@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">artunmurat@gmail.com</a>&gt;</b></font>

<p><font face="sans-serif" size="1">06/07/2007 09:56 AM</font>
<br>
</p></td><td><font face="Arial" size="1">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font face="sans-serif" size="1">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;<a href="mailto:avt@ietf.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">avt@ietf.org</a></font>
<br><font face="sans-serif" size="1">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;</font>
<br><font face="sans-serif" size="1">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;[AVT] transmitting g729 bitstream in RTP</font></td></tr></tbody></table><div><span class="e" id="q_113075628a2be26b_1">
<br>
<br>
<br><font face="Courier New" size="2">Hello,<br>
<br>
I want to ask how the 80-bits long (assume G729B is disabled for<br>
experimental purposes) G729 coded voice data is transmitted using RTP.<br>
<br>
ITU test code encoder outputs 11 short integers (parameter vector)<br>
where these 80-bits are packed following the below scheme:<br>
<br>
/*----------------------------------------------------------------------------<br>
 * prm2bits_ld8k -converts encoder parameter vector into vector of serial bits<br>
 * bits2prm_ld8k - converts serial received bits to &nbsp;encoder parameter vector<br>
 *<br>
 * The transmitted parameters are:<br>
 *<br>
 * &nbsp; &nbsp; LPC: &nbsp; &nbsp; 1st codebook &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 7+1 bit<br>
 * &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2nd codebook &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 5+5 bit<br>
 *<br>
 * &nbsp; &nbsp; 1st subframe:<br>
 * &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;pitch period &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 8 bit<br>
 * &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;parity check on 1st period &nbsp; 1 bit<br>
 * &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;codebook index1 (positions) 13 bit<br>
 * &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;codebook index2 (signs) &nbsp; &nbsp; &nbsp;4 bit<br>
 * &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;pitch and codebook gains &nbsp; 4+3 bit<br>
 *<br>
 * &nbsp; &nbsp; 2nd subframe:<br>
 * &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;pitch period (relative) &nbsp; &nbsp; &nbsp;5 bit<br>
 * &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;codebook index1 (positions) 13 bit<br>
 * &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;codebook index2 (signs) &nbsp; &nbsp; &nbsp;4 bit<br>
 * &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;pitch and codebook gains &nbsp; 4+3 bit<br>
 *----------------------------------------------------------------------------<br>
 */ (from BITS.C of ITU test code)<br>
<br>
However, as I have followed the ethereal trace of a G729 voice<br>
exchange, I see that only 8-bytes are transmitted for each G729 coded<br>
10 ms voice data.<br>
<br>
Considering the above parameter scheme that was specified to be<br>
transmitted in the ITU test code, what is the true packing scheme for<br>
each 10 ms G729 coded coice data?<br>
<br>
Thanks in advice...<br>
<br>
-- <br>
M u r at &nbsp;A r t u n, MSc.<br>
 &nbsp; Software Engineer<br>
<br>
_______________________________________________<br>
Audio/Video Transport Working Group<br>
<a href="mailto:avt@ietf.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">avt@ietf.org</a><br>
<a href="https://www1.ietf.org/mailman/listinfo/avt" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">https://www1.ietf.org/mailman/listinfo/avt</a><br>
</font>
<br>
<br></span></div></blockquote></div><br><br clear="all"><br>-- <br>M u r at&nbsp;&nbsp;A r t u n, MSc.<br>&nbsp;&nbsp; Software Engineer

------=_Part_47957_15443235.1181289108357--


--===============1537114423==
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

--===============1537114423==--




From avt-bounces@ietf.org Fri Jun 08 08:26: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 1HwdXq-00013O-Oe; Fri, 08 Jun 2007 08:26:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwLyP-0004qn-UX; Thu, 07 Jun 2007 13:40:37 -0400
Received: from mail.hhi.fraunhofer.de ([193.174.67.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HwLyP-0001iz-D1; Thu, 07 Jun 2007 13:40:37 -0400
Received: by mail.hhi.fraunhofer.de (Postfix, from userid 65534)
	id 7CF901D88F5D; Thu,  7 Jun 2007 19:40:36 +0200 (CEST)
Received: from ipam040189 (ipam189.Stanford.EDU [171.64.92.89])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(Client did not present a certificate)
	by mail.hhi.fraunhofer.de (Postfix) with ESMTP id DD3E81D88F62;
	Thu,  7 Jun 2007 19:40:32 +0200 (CEST)
From: "Thomas Schierl" <thomas.schierl@hhi.fraunhofer.de>
To: "'Dave Singer'" <singer@apple.com>
References: <144ED8561CE90C41A3E5908EDECE315C049E76DA@IsrExch01.israel.polycom.com>
	<p0624081ac28b3247e073@[17.202.35.52]>
Subject: RE: [AVT] RE: [MMUSIC] questions about grouping media streams in RTP
	andSDP (RFC3388 etc), advice needed
Date: Thu, 7 Jun 2007 10:40:15 -0700
Organization: HHI/FhG
Message-ID: <000001c7a92a$f3aefac0$595c40ab@ipam040189>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcenhyxcbwKgryeQTM2S+JPzrTemewBon4FQ
In-Reply-To: <p0624081ac28b3247e073@[17.202.35.52]>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on 
	mail.hhi.fraunhofer.de
X-Spam-Level: 
X-Spam-Status: No, hits=-104.4 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: 20f22c03b5c66958bff5ef54fcda6e48
X-Mailman-Approved-At: Fri, 08 Jun 2007 08:26:21 -0400
Cc: "'Even, Roni'" <roni.even@polycom.co.il>, Stephan.Wenger@nokia.com,
	mmusic@ietf.org, avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi Dave, 

I think there is a strong relation of your problem and the
http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered-codec-03.txt .
In this draft, we described media dependency in general, not only for
scalable video. Currently, two types of dependencies are defined: layered
and mdc assuming the media is partially transported in different RTP
sessions. It would be easy to integrate your needs, if they should not be
already covered.


Thomas

> -----Original Message-----
> From: Dave Singer [mailto:singer@apple.com]
> Sent: Tuesday, June 05, 2007 8:34 AM
> To: Even, Roni; mmusic; IETF AVT WG
> Cc: Clinton Priddle (KI/EAB)
> Subject: [AVT] RE: [MMUSIC] questions about grouping media streams in RTP
> andSDP (RFC3388 etc), advice needed
> 
> At 10:03  +0300 5/06/07, Even, Roni wrote:
> >Dave,
> >For layered encoding there is a proposal for a new grouping attribute in
> >http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered-codec-03.tx
> >t
> 
> I don't think this is a layered coding issue, either, alas.
> 
> >I looked at RFC3388 and I think that FID is not the answer to your
> >requirement as you mentioned
> >
> >To me it looks like what you are looking for is a way to specify
> >alternate offers.
> 
> No, these streams are not alternatives to each other in the regular
> sense.  Nor is this really used in offer/answer;  it's more an issue
> for multicast.  In multicast, you open the tune-in stream and the
> base stream, grab the first I-frame that arrives (in either) and then
> drop the tune-in stream.
> 
> Yes, we're aware that the recipient needs to be able to tell which is
> the base and which is the tune-in.
> 
> >If this is the case I have similar requirements and
> >would be happy to support such work.
> >
> >You also need a way to give semantics to the "repair" stream, this can
> >be done based on the content attribute from RFC 4796 or using a
> >dependency attribute see in Schierl's draft. The mid tag is not enough
> >for the receiver to know what you meant by this offer and which stream
> >is the repair.
> >
> >Here is an example for a solution using a new Alternatives grouping
> >attribute and giving semantics to the repair stream
> >
> >By using the grouping attribute in the offer you can know if the
> >answerer understood the grouping since if he does not than he will send
> >an answer with no a=group
> >
> >v=0
> >o=bob 280744730 28977631 IN IP4 host.example.com
> >s=
> >t=0 0
> >
> >a=group:ALTS 1 2
> >a=group:ALTS 1 3
> >
> >m=audio 6886 RTP/AVP 0
> >c=IN IP6 2001:0600::1
> >a=mid:1
> >
> >m=video 9000 RTP/AVP 100
> >c=IN IP4 192.0.2.2
> >a=rtpmap:100 H263-1998
> >a=mid:2
> >
> >m=video 9002 RTP/AVP 101
> >c=IN IP4 192.0.2.2
> >a=rtpmap:101 H263-1998
> >a=mid:3
> >a=content:repair=2 or a=depend:repair=2
> >
> >
> >Roni Even
> >
> >>  -----Original Message-----
> >>  From: Dave Singer [mailto:singer@apple.com]
> >>  Sent: Monday, June 04, 2007 7:19 PM
> >>  To: mmusic; IETF AVT WG
> >>  Cc: Clinton Priddle (KI/EAB)
> >>  Subject: [MMUSIC] questions about grouping media streams in RTP and
> >SDP
> >>  (RFC3388 etc), advice needed
> >>
> >>  Hi
> >>
> >>  we have a need to group together two media streams, in the style of
> >RFC
> >>  3388 <http://www.ietf.org/rfc/rfc3388.txt> but we're unsure whether an
> >>  existing group type is suitable or not, and if it's not, we'd like to
> >>  agree on a new one, and document it (presumably in an RFC).
> >>
> >>  What we have is a normal media stream, and a separate 'repair' or
> >>  'entry' stream, that can be used when tuning in, or after loss, but is
> >>  otherwise un-needed.  An example might be a video stream with a low
> >>  I-frame interval (say every 15 seconds), with a repair stream which
> >has
> >>  only I-frames that are equivalent to the time-parallel non-I frame, at
> >a
> >>  frequency of say 1 per second.
> >>
> >>  It's not clear to us whether this is "one media flow" in the sense of
> >>  FID, or not.  The example offers AMR and GSM audio, which are
> >>  alternatives, and DTMF tones along with audio, which are supplementary
> >>  to each other.  Perhaps we fall afoul of this restriction:
> >>
> >>  "An application that encodes the same media using different codecs
> >>  simultaneously MUST NOT use FID to group those media lines."
> >>
> >>  or this one, for layered encoding:
> >>
> >>  "FID MUST NOT be used to group "m" lines that do not represent the
> >same
> >>  information."  (Though how DTMF tones and their associated audio pass
> >>  this test is not clear).
> >>
> >>  Nor is it clear that the FEC group of RFC 4756 is right, either.  For
> >a
> >>  start, we may wish to use this new ID in combination with FEC, and
> >>  secondly this tune-in stream has different characteristics.  For
> >>  example, one can typically ignore all FEC and (as long as there are no
> >>  errors) decode the stream correctly.  Ignoring the tune-in stream
> >  > entirely may mean that you will never find a tune-in point, making
> the
> >>  normal stream useless.
> >>
> >>  So, can we use FID for associating a repair stream with its base (we
> >tag
> >>  the streams so we know which is which, of course)?
> >>
> >>  p.s. RFC 4756 claims in the IANA section that the FEC group is
> >>  registered under SDP characteristics, but actually I can find no
> >>  registry anywhere in IANA of group types.
> >>
> >>
> >>  --
> >>  David Singer
> >>  Apple/QuickTime
> >>
> >>  _______________________________________________
> >>  mmusic mailing list
> >>  mmusic@ietf.org
> >>  https://www1.ietf.org/mailman/listinfo/mmusic
> 
> 
> --
> David Singer
> Apple/QuickTime
> 
> _______________________________________________
> 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 Jun 08 08:26: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 1HwdXr-00013T-6l; Fri, 08 Jun 2007 08:26:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwPkQ-0000U7-NA
	for avt@ietf.org; Thu, 07 Jun 2007 17:42:26 -0400
Received: from stewe.org ([85.214.23.117] helo=h665227.serverkompetenz.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwPkP-0000M8-LY
	for avt@ietf.org; Thu, 07 Jun 2007 17:42:26 -0400
Received: (qmail 24038 invoked by uid 60000); 7 Jun 2007 20:19:51 -0000
Received: from 75.60.27.134 by h665227 (envelope-from
	<stephan.wenger@nokia.com>,
	uid 60004) with qmail-scanner-1.24st visas (spamassassin: 2.64.  
	Clear:RC:0(75.60.27.134):SA:0(0.0/20.0):. 
	Processed in 0.921716 secs); 07 Jun 2007 20:19:51 -0000
X-Spam-Status: No, hits=0.0 required=20.0
X-Envelope-From: stephan.wenger@nokia.com
Received: from adsl-75-60-27-134.dsl.pltn13.sbcglobal.net (HELO
	?192.168.1.100?) (stewe@stewe.org@75.60.27.134)
	by stewe.org with SMTP; 7 Jun 2007 20:19:50 -0000
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C049E7C50@IsrExch01.israel.polycom.com>
References: <144ED8561CE90C41A3E5908EDECE315C049E7C50@IsrExch01.israel.polycom.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A9685D16-0DF7-4FCF-A012-CA86207FEEAC@nokia.com>
Content-Transfer-Encoding: 7bit
From: Stephan Wenger <Stephan.Wenger@nokia.com>
Subject: Re: [AVT] RE: [MMUSIC] questions about grouping media streams in RTP
	andSDP (RFC3388 etc), advice needed
Date: Thu, 7 Jun 2007 14:42:15 -0700
To: "Even, Roni" <roni.even@polycom.co.il>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on 
	h665227.serverkompetenz.net
X-Spam-Level: 
X-Qmail-Scanner-MOVED-X-Spam-Status: No, hits=0.0 required=20.0 tests=none
	autolearn=no version=2.64
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 71f780ffdd80c541d3e75aa5f2710d3d
X-Mailman-Approved-At: Fri, 08 Jun 2007 08:26:21 -0400
Cc: "Clinton Priddle \(KI/EAB\)" <clinton.priddle@ericsson.com>,
	mmusic <mmusic@ietf.org>, IETF AVT WG <avt@ietf.org>,
	Dave Singer <singer@apple.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi all,
Yes, i agree with Roni: This is not a layered codec case in any  
sense, as there is no directed use hierarchy between those two  
flows.  Under certain conditions (i.e. in the absence of packet  
loss), both are valid, usable streams.
But, IMHO, this may be not a bad example for multiple description  
coding.  The two streams represent essentially the same media, and  
(under certain conditions such as packet loss) it is advantageous to  
use both of them, not only one.  It may not be a direct hit on the  
Schierl draft MDC use case, but it's close enough to be documentable  
in a 3GPP spec.
I'm not sure that the use case in question warrants a new I-D.  If  
the analogy to video transmission would be a bit more solid, I would  
have a different view.  But, a it stands, you could not use the  
mechanism envisioned with any predictive video codec (possible  
exception: H.264 extended profile, utilizing SI/SP technology), as it  
is at present close to impossible to generate identical reference  
pictures from two different streams, using different encoding methods.
Finally, I'm unsure whether 3GPP's intended timing would allow for  
yet another draft.  Even the Schierl draft comes kind of late for  
this work.
Regards,
Stephan


On Jun 7, 2007, at 1:06 PM, Even, Roni wrote:

> Hi,
> My view is that you have similarity in the need for dependencies  
> between
> streams but the grouping logic is different.
> In the layered codec the grouping is for a group that you can use  
> all or
> part of while in the repair case you may take one or the other.
>
> Roni Even
>
>> -----Original Message-----
>> From: Thomas Schierl [mailto:schierl@hhi.fhg.de]
>> Sent: Thursday, June 07, 2007 8:46 PM
>> To: 'Dave Singer'; Even, Roni; 'mmusic'; 'IETF AVT WG'
>> Cc: Stephan.Wenger@nokia.com; 'Clinton Priddle (KI/EAB)'
>> Subject: RE: [AVT] RE: [MMUSIC] questions about grouping media  
>> streams
> in
>> RTP andSDP (RFC3388 etc), advice needed
>>
>> Hi Dave,
>>
>> I think there is a strong relation of your problem and the
>>
> http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered- 
> codec-03.tx
> t
>> In this draft, we described media dependency in general, not only for
>> scalable video. Currently, two types of dependencies are defined:
> layered
>> and mdc assuming the media is partially transported in different RTP
>> sessions. There is not requirement, that the part of the media is
>> independently decodable. It would be easy to integrate your needs, if
> they
>> should not be already covered.
>>
>>
>> Thomas
>>
>>> -----Original Message-----
>>> From: Dave Singer [mailto:singer@apple.com]
>>> Sent: Tuesday, June 05, 2007 8:34 AM
>>> To: Even, Roni; mmusic; IETF AVT WG
>>> Cc: Clinton Priddle (KI/EAB)
>>> Subject: [AVT] RE: [MMUSIC] questions about grouping media streams
> in
>> RTP
>>> andSDP (RFC3388 etc), advice needed
>>>
>>> At 10:03  +0300 5/06/07, Even, Roni wrote:
>>>> Dave,
>>>> For layered encoding there is a proposal for a new grouping
> attribute
>> in
>>>> http://tools.ietf.org/wg/mmusic/draft-schierl-mmusic-layered-codec-
>> 03.tx
>>>> t
>>>
>>> I don't think this is a layered coding issue, either, alas.
>>>
>>>> I looked at RFC3388 and I think that FID is not the answer to your
>>>> requirement as you mentioned
>>>>
>>>> To me it looks like what you are looking for is a way to specify
>>>> alternate offers.
>>>
>>> No, these streams are not alternatives to each other in the regular
>>> sense.  Nor is this really used in offer/answer;  it's more an issue
>>> for multicast.  In multicast, you open the tune-in stream and the
>>> base stream, grab the first I-frame that arrives (in either) and
> then
>>> drop the tune-in stream.
>>>
>>> Yes, we're aware that the recipient needs to be able to tell which
> is
>>> the base and which is the tune-in.
>>>
>>>> If this is the case I have similar requirements and
>>>> would be happy to support such work.
>>>>
>>>> You also need a way to give semantics to the "repair" stream, this
> can
>>>> be done based on the content attribute from RFC 4796 or using a
>>>> dependency attribute see in Schierl's draft. The mid tag is not
> enough
>>>> for the receiver to know what you meant by this offer and which
> stream
>>>> is the repair.
>>>>
>>>> Here is an example for a solution using a new Alternatives grouping
>>>> attribute and giving semantics to the repair stream
>>>>
>>>> By using the grouping attribute in the offer you can know if the
>>>> answerer understood the grouping since if he does not than he will
> send
>>>> an answer with no a=group
>>>>
>>>> v=0
>>>> o=bob 280744730 28977631 IN IP4 host.example.com
>>>> s=
>>>> t=0 0
>>>>
>>>> a=group:ALTS 1 2
>>>> a=group:ALTS 1 3
>>>>
>>>> m=audio 6886 RTP/AVP 0
>>>> c=IN IP6 2001:0600::1
>>>> a=mid:1
>>>>
>>>> m=video 9000 RTP/AVP 100
>>>> c=IN IP4 192.0.2.2
>>>> a=rtpmap:100 H263-1998
>>>> a=mid:2
>>>>
>>>> m=video 9002 RTP/AVP 101
>>>> c=IN IP4 192.0.2.2
>>>> a=rtpmap:101 H263-1998
>>>> a=mid:3
>>>> a=content:repair=2 or a=depend:repair=2
>>>>
>>>>
>>>> Roni Even
>>>>
>>>>>  -----Original Message-----
>>>>>  From: Dave Singer [mailto:singer@apple.com]
>>>>>  Sent: Monday, June 04, 2007 7:19 PM
>>>>>  To: mmusic; IETF AVT WG
>>>>>  Cc: Clinton Priddle (KI/EAB)
>>>>>  Subject: [MMUSIC] questions about grouping media streams in RTP
> and
>>>> SDP
>>>>>  (RFC3388 etc), advice needed
>>>>>
>>>>>  Hi
>>>>>
>>>>>  we have a need to group together two media streams, in the style
> of
>>>> RFC
>>>>>  3388 <http://www.ietf.org/rfc/rfc3388.txt> but we're unsure
> whether
>> an
>>>>>  existing group type is suitable or not, and if it's not, we'd
> like
>> to
>>>>>  agree on a new one, and document it (presumably in an RFC).
>>>>>
>>>>>  What we have is a normal media stream, and a separate 'repair'
> or
>>>>>  'entry' stream, that can be used when tuning in, or after loss,
> but
>> is
>>>>>  otherwise un-needed.  An example might be a video stream with a
> low
>>>>>  I-frame interval (say every 15 seconds), with a repair stream
> which
>>>> has
>>>>>  only I-frames that are equivalent to the time-parallel non-I
> frame,
>> at
>>>> a
>>>>>  frequency of say 1 per second.
>>>>>
>>>>>  It's not clear to us whether this is "one media flow" in the
> sense
>> of
>>>>>  FID, or not.  The example offers AMR and GSM audio, which are
>>>>>  alternatives, and DTMF tones along with audio, which are
>> supplementary
>>>>>  to each other.  Perhaps we fall afoul of this restriction:
>>>>>
>>>>>  "An application that encodes the same media using different
> codecs
>>>>>  simultaneously MUST NOT use FID to group those media lines."
>>>>>
>>>>>  or this one, for layered encoding:
>>>>>
>>>>>  "FID MUST NOT be used to group "m" lines that do not represent
> the
>>>> same
>>>>>  information."  (Though how DTMF tones and their associated audio
>> pass
>>>>>  this test is not clear).
>>>>>
>>>>>  Nor is it clear that the FEC group of RFC 4756 is right, either.
>> For
>>>> a
>>>>>  start, we may wish to use this new ID in combination with FEC,
> and
>>>>>  secondly this tune-in stream has different characteristics.  For
>>>>>  example, one can typically ignore all FEC and (as long as there
> are
>> no
>>>>>  errors) decode the stream correctly.  Ignoring the tune-in
> stream
>>>>> entirely may mean that you will never find a tune-in point,
> making
>>> the
>>>>>  normal stream useless.
>>>>>
>>>>>  So, can we use FID for associating a repair stream with its base
> (we
>>>> tag
>>>>>  the streams so we know which is which, of course)?
>>>>>
>>>>>  p.s. RFC 4756 claims in the IANA section that the FEC group is
>>>>>  registered under SDP characteristics, but actually I can find no
>>>>>  registry anywhere in IANA of group types.
>>>>>
>>>>>
>>>>>  --
>>>>>  David Singer
>>>>>  Apple/QuickTime
>>>>>
>>>>>  _______________________________________________
>>>>>  mmusic mailing list
>>>>>  mmusic@ietf.org
>>>>>  https://www1.ietf.org/mailman/listinfo/mmusic
>>>
>>>
>>> --
>>> David Singer
>>> Apple/QuickTime
>>>
>>> _______________________________________________
>>> Audio/Video Transport Working Group
>>> avt@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/avt
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic


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



From avt-bounces@ietf.org Fri Jun 08 10:31:23 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 1HwfUo-0006WK-2A; Fri, 08 Jun 2007 10:31:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwfTg-0004dJ-Qm; Fri, 08 Jun 2007 10:30:12 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HwfTf-0004vH-HW; Fri, 08 Jun 2007 10:30:12 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:60721)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HwfTZ-0000o3-Pg; Fri, 08 Jun 2007 15:30:05 +0100
In-Reply-To: <289643F2-2529-4C24-B430-B9967B5DADD4@csperkins.org>
References: <289643F2-2529-4C24-B430-B9967B5DADD4@csperkins.org>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <58FFB38C-B79B-4C13-A8D9-2CC7A5FC2EC0@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Moving draft-marjou-behave-app-rtp-keepalive to AVT
Date: Fri, 8 Jun 2007 15:30:13 +0100
To: mmusic <mmusic@ietf.org>, Behave WG <behave@ietf.org>,
	IETF AVT WG <avt@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
X-Mailman-Approved-At: Fri, 08 Jun 2007 10:31:20 -0400
Cc: Cullen Jennings <fluffy@cisco.com>,
	Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Xavier Marjou <xavier.marjou@orange-ftgroup.com>,
	Roni Even <roni.even@polycom.co.il>,
	Tom Taylor <tom.taylor@rogers.com>, Joerg Ott <jo@acm.org>,
	Jean-Francois Mule <jf.mule@cablelabs.com>,
	"Dan Wing \(\(\(\(dwing\)\)\)\)" <dwing@cisco.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 1 Jun 2007, at 18:15, Colin Perkins wrote:
> There has been some private discussion on adopting the draft on  
> Application Mechanisms for maintaining alive NAT mappings  
> associated with RTP flows (draft-marjou-behave-app-rtp- 
> keepalive-01.txt) as an AVT working group draft. This has  
> previously been discussed in AVT, BEHAVE and MMUSIC. Opinions on  
> whether this draft should become a working group draft, and on the  
> appropriate home for it, are solicited by 8 June 2007.

There were several comments in favour of this proposal, and no  
objections. Accordingly, we will take this draft as an AVT work item.

-- 
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 Jun 08 10:40: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 1Hwfe3-0004lJ-TJ; Fri, 08 Jun 2007 10:40:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hwfe3-0004lD-1V
	for avt@ietf.org; Fri, 08 Jun 2007 10:40:55 -0400
Received: from web42104.mail.mud.yahoo.com ([209.191.86.237])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Hwfe1-0001BU-Az
	for avt@ietf.org; Fri, 08 Jun 2007 10:40:55 -0400
Received: (qmail 50261 invoked by uid 60001); 8 Jun 2007 14:40:52 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=j7ocsUMJPHwsdVqtND1z707PcAwCOZ01oRZin4JYRwBF4J9Wb8RbRuBilYhe+fCJuqdDy0t6X83dZJnvrRsq6mDVb3SYhccuveJ2yneMJJJ6XbQNPzBMsvB0ScP6acoAZ/cypw6MHNBX8SWZcd89UoQSag6yxZq4FKFYtg9uwqw=;
X-YMail-OSG: LcWRMcoVM1kdP7kFq8QfXo0ShNpK_7YB.xrkWn7HsEHrtQLbTFu8Qn7xCzAadPZhQcceL6me0R1xu7FVpQPjCr2cjp4QHtULhGRwzbg2Lg913Hk3GnGp96whXBbQRA--
Received: from [202.84.165.220] by web42104.mail.mud.yahoo.com via HTTP;
	Fri, 08 Jun 2007 07:40:52 PDT
Date: Fri, 8 Jun 2007 07:40:52 -0700 (PDT)
From: sona chalam <sona_kk@yahoo.com>
To: Randell Jesup <rjesup@wgate.com>, "Even, Roni" <roni.even@polycom.co.il>
In-Reply-To: <ybuejknmdmw.fsf@jesup.eng.wgate.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <805902.49658.qm@web42104.mail.mud.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: "Ajmal, Humayun" <Humayun_Ajmal@mentor.com>, avt@ietf.org
Subject: [AVT] H264 identifying a complete frame from NAL units
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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

How to identify a Start  and End of a FRAME in H264
using NAL units.

I am performing H264 streaming  and  extracting NAL
units from RTP packets .

My understanding is one Access unit is called as a
FRAME.

In my streaming session I am receiving FUA and SNAL
only.  I am not geting any other NAL unit types  other
than 1 and 5).

So how to construct access unit in this case?







       
____________________________________________________________________________________
Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase.
http://farechase.yahoo.com/

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



From avt-bounces@ietf.org Fri Jun 08 18:56: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 1HwnNy-0006tV-Ti; Fri, 08 Jun 2007 18:56:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwnNx-0006t5-UR; Fri, 08 Jun 2007 18:56:49 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HwnNx-0001H1-Hz; Fri, 08 Jun 2007 18:56:49 -0400
Received: from relay6.apple.com (relay6.apple.com [17.128.113.36])
	by mail-out4.apple.com (Postfix) with ESMTP id 1E22086FF98;
	Fri,  8 Jun 2007 15:56:49 -0700 (PDT)
Received: from relay6.apple.com (unknown [127.0.0.1])
	by relay6.apple.com (Symantec Mail Security) with ESMTP id EAF75100C6; 
	Fri,  8 Jun 2007 15:56:48 -0700 (PDT)
X-AuditID: 11807124-9fec6bb000000801-ca-4669deaf6740
Received: from [17.202.35.52] (singda.apple.com [17.202.35.52])
	by relay6.apple.com (Apple SCV relay) with ESMTP id 463E310192;
	Fri,  8 Jun 2007 15:56:47 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p0624087fc28f8ce7c740@[17.202.35.52]>
In-Reply-To: <AE99B7B733E1BB49B019CAA0F806D7A704DB1FF1@nets13ka.ww300.siemens.net>
References: <144ED8561CE90C41A3E5908EDECE315C049E76DA@IsrExch01.israel.polycom.com>
	<AE99B7B733E1BB49B019CAA0F806D7A704DB1FF1@nets13ka.ww300.siemens.net>
Date: Fri, 8 Jun 2007 15:56:13 -0700
To: "Kalleitner, Franz" <franz.kalleitner@siemens.com>,
	"Even, Roni" <roni.even@polycom.co.il>, mmusic <mmusic@ietf.org>,
	IETF AVT WG <avt@ietf.org>
From: Dave Singer <singer@apple.com>
Subject: Re: AW: [AVT] RE: [MMUSIC] questions about grouping media streams
	in  RTPand SDP (RFC3388 etc), advice needed
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: "Clinton Priddle \(KI/EAB\)" <clinton.priddle@ericsson.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

At 11:54  +0200 5/06/07, Kalleitner, Franz wrote:
>hi, dave,
>
>you can find some work and ideas on how to handle a "repair" stream 
>in parallel to an orignal RTP stream in RFC4588 too.
>
>cheers, franz

Thank you.  This has the rather useful paragraph:

    A special case of the SDP description is a description that contains
    only one original session "m" line and one retransmission session "m"
    line, the grouping is then obvious and FID semantics MAY be omitted
    in this special case only.

Since this exactly describes our current situation -- the normal and 
repair streams are indeed easily identified, and we currently only 
allow one normal stream per session -- perhaps we will take this 
route, and let the standards catch up to where we need to be, if 
anyone has a need for multiple base streams in the future.

And indeed, not doing grouping means avoiding having to insist that 
any audio or video streams in the same SDP also have a media ID (as 
the grouping RFC requires)., even though those IDs are not grouped.

At 14:42  -0700 7/06/07, Stephan Wenger wrote:
>Hi all,
>Yes, i agree with Roni: This is not a layered codec case in any 
>sense, as there is no directed use hierarchy between those two 
>flows.  Under certain conditions (i.e. in the absence of packet 
>loss), both are valid, usable streams.

Is an SI AVC stream really a usable stream in its own right?

>But, IMHO, this may be not a bad example for multiple description 
>coding.  The two streams represent essentially the same media, and 
>(under certain conditions such as packet loss) it is advantageous to 
>use both of them, not only one.  It may not be a direct hit on the 
>Schierl draft MDC use case, but it's close enough to be documentable 
>in a 3GPP spec.
>I'm not sure that the use case in question warrants a new I-D.  If 
>the analogy to video transmission would be a bit more solid, I would 
>have a different view.  But, a it stands, you could not use the 
>mechanism envisioned with any predictive video codec (possible 
>exception: H.264 extended profile, utilizing SI/SP technology), as 
>it is at present close to impossible to generate identical reference 
>pictures from two different streams, using different encoding 
>methods.

Actually I would have agreed with you until I found someone doing it 
in AVC successfully using I frames, not SI frames.

At 14:47  -0700 7/06/07, Thomas Schierl wrote:
>Then it would be something like we call 'mdc'. But I would like to put that
>into an extra dependency type, since the characteristics of the streams are
>different, even if they could be used exchangeable. But there is one main
>stream, let us say. And that one should be identifiable.

As I say, the rtpmap declarations and parameters identify the two 
streams, we have that in hand.  We just wondered how we should group 
them -- and all that is needed is a group.  Happily the quote above 
provides the short-term answer -- don't!
-- 
David Singer
Apple/QuickTime

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



From avt-bounces@ietf.org Fri Jun 08 19:32: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 1Hwnwk-0001Jk-4Z; Fri, 08 Jun 2007 19:32:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hwnwi-0001Jf-Ez
	for avt@ietf.org; Fri, 08 Jun 2007 19:32:44 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hwnwh-0008Cd-U5
	for avt@ietf.org; Fri, 08 Jun 2007 19:32:44 -0400
Received: from relay5.apple.com (relay5.apple.com [17.128.113.35])
	by mail-out3.apple.com (Postfix) with ESMTP id 8FEEC84531B;
	Fri,  8 Jun 2007 16:31:43 -0700 (PDT)
Received: from relay5.apple.com (unknown [127.0.0.1])
	by relay5.apple.com (Symantec Mail Security) with ESMTP id 5114C29C002; 
	Fri,  8 Jun 2007 16:32:43 -0700 (PDT)
X-AuditID: 11807123-9e81fbb000000a23-81-4669e71b41fc
Received: from [17.202.35.52] (singda.apple.com [17.202.35.52])
	by relay5.apple.com (Apple SCV relay) with ESMTP id 0D41830400B;
	Fri,  8 Jun 2007 16:32:42 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p06240887c28f9648fa12@[17.202.35.52]>
In-Reply-To: <4666DD9A.4161A698@erols.com>
References: <7634542FB03DC747813D67560802AEED9EB379@rennsmail05.eu.thmulti.com>
	<465D8C51.4080805@ericsson.com> <p06240817c28360afcce1@[17.202.35.52]>
	<465E8514.9080503@ericsson.com> <4666DD9A.4161A698@erols.com>
Date: Fri, 8 Jun 2007 16:30:50 -0700
To: Chuck Harrison <cfharr@erols.com>,
	Magnus Westerlund <magnus.westerlund@ericsson.com>
From: Dave Singer <singer@apple.com>
Subject: Re: [AVT] Working group last call: JPEG-2000 payload format
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Cc: Boudani Ali <Ali.Boudani@thomson.net>,
	Le Dantec Claude <Claude.Le-Dantec@thomson.net>, 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

At 9:15  -0700 6/06/07, Chuck Harrison wrote:
>Suppose
>
>1. A compliant J2K receiver MUST accept 90kHz timestamps
>2. A compliant J2K receiver MAY accept other timestamp rates
>3. A compliant J2K sender SHOULD transmit 90kHz timestamps
>4. The RFC warns that senders violating the SHOULD of item 3
>     risk interoperability problems.

I think timestamp conversion tends to be a common function in an RTP 
stack, doesn't it?  Be that as it may, it's no good allowing me to 
send non-90KHz if I can't know it'll work -- standards are about 
interoperability.  So I think that it should say

* a 90 KHz clockrate is recommended (you could even use SHOULD be 
used) for JPEG 2000 streams
* receivers MUST be able to handle other clock rates

The RFC warns that if you choose an unsuitable rate, or a rate whose 
conversion is difficult, error-prone (e.g. to round-off errors), or 
even unusual, you risk playability problems.

>
>Then Dave is permitted to send a stream between matching
>compliant applications using an 89999 Hz media clock, 12857
>ticks per frame, exactly 7 frames per second. Or: a 70000 Hz
>clock, 10000 ticks per frame.
>
>An alternate video source, playing nice and sending at
>90 kHz, is guaranteed to be able to talk successfully to
>Dave's receiver application.
>
>Dave's special source may not be able to send successfully
>to the majority of J2K receiver applications.
>
>Is this a high enough level of interoperability?
>
>Regards,
>   Chuck
>
>
>Magnus Westerlund wrote:
>>
>>  Dave Singer skrev:
>>  > RTP payload formats may be used for all sorts of purposes and (varying)
>>  > frame rates.  I disagree that we in the AVT group 'know best' and that
>>  > any payload format should mandate a particular clock frequency.  It's
>>  > perfectly legitimate for me to send material at say 7 fps, and 90000 is
>>  > not suitable for that -- the frames would appear to have varying
>>  > duration, and there is risk of round-off.
>>
>>  I know that AVT is not knowing best. However, I asked this questions so
>>  that we could be educated and take an informed decision. However I think
>>  there are definitely an trade-off between using a fixed timestamp clock
>>  rate and allow any rate to be used.
>>
>>  >
>>  > Any payload format should recommend ('should') something, but mention
>>  > that other possibilities exist.
>>
>>  As this have shown to create problems in implementations. For example it
>>  showed up in an interop test creating problems for the packet-based
>>  streaming service where people sent MPEG-4 content using RFC3016
>>  packetization using non 90kHz clock. This occurs because the wiggle room
>>  was given and most implementors do no understand the implications of
>>  using another clock. Sure, we didn't document well enough all the
>>  downsides with choosing something else. Also we really should provide
>>  some lower and upper boundaries on these values.
>>
>>  >
>>  > Very high clock frequencies (e.g. 27 MHz) bring their own problems
>>  > (frequent wrap-around being one).  For a given program, it is usually
>>  > the case that one can easily find a number that
>>  > a) doesn't wrap around too often
>>  > b) is high enough for accurate jitter calculations
>>  > c) is an integer multiple of the frame rate, or, for variable frame
>>  > rate, allows each frame to have an integer timestamp which has not been
>>  > rounded-off
>>  >
>>
>>  Yes, and that have so far been 90kHz to satisfy this. If there are cases
>>  when this is not true I would like to know about them. But I think we
>>  should be clear on why we are allowing any wiggle room at all. 90kHz do
>>  support quite a lot of different frame rates. I am not saying that there
>>  doesn't exist such rate. But given a blank card on what rate to use adds
>>  complexities. If we rather could enumerate a small set of possible rates
>>  to cover the known cases that would make me much happier.
>  >
>>  But Ali's example is not something that can be solved using the RTP
>>  timestamp rate if I understand this correctly. Simply because 27 MHz
>>  gets us into the problem with frequent wrap around.
>>
>>  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 Sat Jun 09 17:03: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 1Hx85q-0006Tp-KY; Sat, 09 Jun 2007 17:03:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hx85p-0006Tk-3F
	for avt@ietf.org; Sat, 09 Jun 2007 17:03:29 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hx85n-0005Sd-Gp
	for avt@ietf.org; Sat, 09 Jun 2007 17:03:29 -0400
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:60588
	helo=[192.168.0.4])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1Hx85k-0005M9-K5; Sat, 09 Jun 2007 22:03:24 +0100
In-Reply-To: <p06240887c28f9648fa12@[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]>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <5CDA4C57-9EA3-494A-8DA9-F5B3B9BC51E6@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Video timestamp rates (was Re: [AVT] Working group last call:
	JPEG-2000 payload format)
Date: Sat, 9 Jun 2007 22:03:31 +0100
To: Dave Singer <singer@apple.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 202a3ece0492a8c7e7c8672d5214398f
Cc: Chuck Harrison <cfharr@erols.com>,
	Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Boudani Ali <Ali.Boudani@thomson.net>,
	Le Dantec Claude <Claude.Le-Dantec@thomson.net>, 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

Okay, some questions for the working group, since this issue is  
broader than just the JPEG-2000 payload format:

1) Is there utility in allowing non-90kHz clock rates for video  
payload formats, and if so, does this utility out-weigh potential  
interoperability problems with existing code which assumes the common  
case of a 90kHz clock? Why?

2) Is there something special about the JPEG-2000 payload format,  
requiring it to use a different clock rate to other formats (e.g. as  
RFC 3497 uses an usual clock rate)?

Cheers,
Colin







On 9 Jun 2007, at 00:30, Dave Singer wrote:
> At 9:15  -0700 6/06/07, Chuck Harrison wrote:
>> Suppose
>>
>> 1. A compliant J2K receiver MUST accept 90kHz timestamps
>> 2. A compliant J2K receiver MAY accept other timestamp rates
>> 3. A compliant J2K sender SHOULD transmit 90kHz timestamps
>> 4. The RFC warns that senders violating the SHOULD of item 3
>>     risk interoperability problems.
>
> I think timestamp conversion tends to be a common function in an  
> RTP stack, doesn't it?  Be that as it may, it's no good allowing me  
> to send non-90KHz if I can't know it'll work -- standards are about  
> interoperability.  So I think that it should say
>
> * a 90 KHz clockrate is recommended (you could even use SHOULD be  
> used) for JPEG 2000 streams
> * receivers MUST be able to handle other clock rates
>
> The RFC warns that if you choose an unsuitable rate, or a rate  
> whose conversion is difficult, error-prone (e.g. to round-off  
> errors), or even unusual, you risk playability problems.
>
>>
>> Then Dave is permitted to send a stream between matching
>> compliant applications using an 89999 Hz media clock, 12857
>> ticks per frame, exactly 7 frames per second. Or: a 70000 Hz
>> clock, 10000 ticks per frame.
>>
>> An alternate video source, playing nice and sending at
>> 90 kHz, is guaranteed to be able to talk successfully to
>> Dave's receiver application.
>>
>> Dave's special source may not be able to send successfully
>> to the majority of J2K receiver applications.
>>
>> Is this a high enough level of interoperability?
>>
>> Regards,
>>   Chuck
>>
>>
>> Magnus Westerlund wrote:
>>>
>>>  Dave Singer skrev:
>>>  > RTP payload formats may be used for all sorts of purposes and  
>>> (varying)
>>>  > frame rates.  I disagree that we in the AVT group 'know best'  
>>> and that
>>>  > any payload format should mandate a particular clock  
>>> frequency.  It's
>>>  > perfectly legitimate for me to send material at say 7 fps, and  
>>> 90000 is
>>>  > not suitable for that -- the frames would appear to have varying
>>>  > duration, and there is risk of round-off.
>>>
>>>  I know that AVT is not knowing best. However, I asked this  
>>> questions so
>>>  that we could be educated and take an informed decision. However  
>>> I think
>>>  there are definitely an trade-off between using a fixed  
>>> timestamp clock
>>>  rate and allow any rate to be used.
>>>
>>>  >
>>>  > Any payload format should recommend ('should') something, but  
>>> mention
>>>  > that other possibilities exist.
>>>
>>>  As this have shown to create problems in implementations. For  
>>> example it
>>>  showed up in an interop test creating problems for the packet-based
>>>  streaming service where people sent MPEG-4 content using RFC3016
>>>  packetization using non 90kHz clock. This occurs because the  
>>> wiggle room
>>>  was given and most implementors do no understand the  
>>> implications of
>>>  using another clock. Sure, we didn't document well enough all the
>>>  downsides with choosing something else. Also we really should  
>>> provide
>>>  some lower and upper boundaries on these values.
>>>
>>>  >
>>>  > Very high clock frequencies (e.g. 27 MHz) bring their own  
>>> problems
>>>  > (frequent wrap-around being one).  For a given program, it is  
>>> usually
>>>  > the case that one can easily find a number that
>>>  > a) doesn't wrap around too often
>>>  > b) is high enough for accurate jitter calculations
>>>  > c) is an integer multiple of the frame rate, or, for variable  
>>> frame
>>>  > rate, allows each frame to have an integer timestamp which has  
>>> not been
>>>  > rounded-off
>>>  >
>>>
>>>  Yes, and that have so far been 90kHz to satisfy this. If there  
>>> are cases
>>>  when this is not true I would like to know about them. But I  
>>> think we
>>>  should be clear on why we are allowing any wiggle room at all.  
>>> 90kHz do
>>>  support quite a lot of different frame rates. I am not saying  
>>> that there
>>>  doesn't exist such rate. But given a blank card on what rate to  
>>> use adds
>>>  complexities. If we rather could enumerate a small set of  
>>> possible rates
>>>  to cover the known cases that would make me much happier.
>>  >
>>>  But Ali's example is not something that can be solved using the RTP
>>>  timestamp rate if I understand this correctly. Simply because 27  
>>> MHz
>>>  gets us into the problem with frequent wrap around.
>>>
>>>  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



-- 
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 Jun 10 03:10: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 1HxHYf-0001Xf-O4; Sun, 10 Jun 2007 03:09:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxHYd-0001XS-Ds; Sun, 10 Jun 2007 03:09:51 -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 1HxHYc-0006rB-Py; Sun, 10 Jun 2007 03:09:51 -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: AW: [AVT] RE: [MMUSIC] questions about grouping media streams in
	RTPand SDP (RFC3388 etc), advice needed
Date: Sun, 10 Jun 2007 10:10:50 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C049E7CE9@IsrExch01.israel.polycom.com>
In-Reply-To: <p0624087fc28f8ce7c740@[17.202.35.52]>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AW: [AVT] RE: [MMUSIC] questions about grouping media streams in
	RTPand SDP (RFC3388 etc), advice needed
Thread-Index: AceqIGRW96FPkNzNR6+W8yMpOMfO8ABDcURQ
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Dave Singer" <singer@apple.com>,
	"Kalleitner, Franz" <franz.kalleitner@siemens.com>,
	"mmusic" <mmusic@ietf.org>, "IETF AVT WG" <avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: "Clinton Priddle \(KI/EAB\)" <clinton.priddle@ericsson.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

Dave,
I understand that you intend to send two media streams using two m lines
without grouping and any specific semantics to identify the stream.
Our experience is that if you have two video m lines you can not know
which one the other will pick if he does not understand the relation
between the streams.
Roni

> -----Original Message-----
> From: Dave Singer [mailto:singer@apple.com]
> Sent: Saturday, June 09, 2007 1:56 AM
> To: Kalleitner, Franz; Even, Roni; mmusic; IETF AVT WG
> Cc: Clinton Priddle (KI/EAB)
> Subject: Re: AW: [AVT] RE: [MMUSIC] questions about grouping media
streams
> in RTPand SDP (RFC3388 etc), advice needed
>=20
> At 11:54  +0200 5/06/07, Kalleitner, Franz wrote:
> >hi, dave,
> >
> >you can find some work and ideas on how to handle a "repair" stream
> >in parallel to an orignal RTP stream in RFC4588 too.
> >
> >cheers, franz
>=20
> Thank you.  This has the rather useful paragraph:
>=20
>     A special case of the SDP description is a description that
contains
>     only one original session "m" line and one retransmission session
"m"
>     line, the grouping is then obvious and FID semantics MAY be
omitted
>     in this special case only.
>=20
> Since this exactly describes our current situation -- the normal and
> repair streams are indeed easily identified, and we currently only
> allow one normal stream per session -- perhaps we will take this
> route, and let the standards catch up to where we need to be, if
> anyone has a need for multiple base streams in the future.
>=20
> And indeed, not doing grouping means avoiding having to insist that
> any audio or video streams in the same SDP also have a media ID (as
> the grouping RFC requires)., even though those IDs are not grouped.
>=20
> At 14:42  -0700 7/06/07, Stephan Wenger wrote:
> >Hi all,
> >Yes, i agree with Roni: This is not a layered codec case in any
> >sense, as there is no directed use hierarchy between those two
> >flows.  Under certain conditions (i.e. in the absence of packet
> >loss), both are valid, usable streams.
>=20
> Is an SI AVC stream really a usable stream in its own right?
>=20
> >But, IMHO, this may be not a bad example for multiple description
> >coding.  The two streams represent essentially the same media, and
> >(under certain conditions such as packet loss) it is advantageous to
> >use both of them, not only one.  It may not be a direct hit on the
> >Schierl draft MDC use case, but it's close enough to be documentable
> >in a 3GPP spec.
> >I'm not sure that the use case in question warrants a new I-D.  If
> >the analogy to video transmission would be a bit more solid, I would
> >have a different view.  But, a it stands, you could not use the
> >mechanism envisioned with any predictive video codec (possible
> >exception: H.264 extended profile, utilizing SI/SP technology), as
> >it is at present close to impossible to generate identical reference
> >pictures from two different streams, using different encoding
> >methods.
>=20
> Actually I would have agreed with you until I found someone doing it
> in AVC successfully using I frames, not SI frames.
>=20
> At 14:47  -0700 7/06/07, Thomas Schierl wrote:
> >Then it would be something like we call 'mdc'. But I would like to
put
> that
> >into an extra dependency type, since the characteristics of the
streams
> are
> >different, even if they could be used exchangeable. But there is one
main
> >stream, let us say. And that one should be identifiable.
>=20
> As I say, the rtpmap declarations and parameters identify the two
> streams, we have that in hand.  We just wondered how we should group
> them -- and all that is needed is a group.  Happily the quote above
> provides the short-term answer -- don't!
> --
> David Singer
> Apple/QuickTime

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



From avt-bounces@ietf.org Mon Jun 11 09:33: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 1Hxk1U-0004Iy-2H; Mon, 11 Jun 2007 09:33:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hxk1S-0004In-Ch
	for avt@ietf.org; Mon, 11 Jun 2007 09:33:30 -0400
Received: from cedar.ugent.be ([157.193.49.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hxk1Q-0001Hd-W4
	for avt@ietf.org; Mon, 11 Jun 2007 09:33:30 -0400
Received: from bonobo.ugent.be (HELO localhost) ([157.193.71.53])
	by cedar.ugent.be with ESMTP; 11 Jun 2007 15:33:28 +0200
Received: from cedar.ugent.be ([157.193.49.14])
	by localhost (bonobo.UGent.be [157.193.43.11]) (amavisd-new, port 10024)
	with ESMTP id 12781-02 for <avt@ietf.org>;
	Mon, 11 Jun 2007 15:33:28 +0200 (CEST)
Received: from mail-tech.intec.ugent.be ([157.193.172.4])
	by cedar.ugent.be with ESMTP; 11 Jun 2007 15:33:28 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAHDrbEadwawE/2dsb2JhbAA
Received: from localhost (localhost [127.0.0.1])
	by mail-tech.intec.ugent.be (Postfix) with ESMTP id 9127310016
	for <avt@ietf.org>; Mon, 11 Jun 2007 15:33:27 +0200 (CEST)
Received: from mail-tech.intec.ugent.be ([127.0.0.1])
	by localhost (mail-tech [157.193.172.4]) (amavisd-new, port 10024)
	with LMTP id 04681-10 for <avt@ietf.org>;
	Mon, 11 Jun 2007 15:33:27 +0200 (CEST)
Received: from [157.193.173.63] (pcdesign52.intec.ugent.be [157.193.173.63])
	by mail-tech.intec.ugent.be (Postfix) with ESMTP id 7E10810009
	for <avt@ietf.org>; Mon, 11 Jun 2007 15:33:27 +0200 (CEST)
Message-ID: <466D4F36.2020409@intec.ugent.be>
Date: Mon, 11 Jun 2007 15:33:42 +0200
From: "pieter.demuytere" <pieter.demuytere@intec.ugent.be>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: avt@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at intec.ugent.be
X-Virus-Scanned: by UGent DICT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Subject: [AVT] RTP - Last sequence number vs highest sequence number
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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,

In RFC 3550, the number of packets expected is defined to be the 
extended last sequence number received less the initial sequence number 
received. However, in the example code given in appendix A.1, the 
(extended) highest sequence number is used, and not the (extended) last 
sequence number. My feeling is that the last sequence number received is 
not automatically equal to the highest sequence number received, due to 
packet reordering. Is it allowed to use the (extended) highest sequence 
number for the calculation of the number of packets expected?

Thanks
Pieter Demuytere

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



From avt-bounces@ietf.org Mon Jun 11 10:04: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 1HxkVm-00047W-Em; Mon, 11 Jun 2007 10:04:50 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HxkVl-0003zx-BL
	for avt@ietf.org; Mon, 11 Jun 2007 10:04:49 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HxkVj-0007mX-TV
	for avt@ietf.org; Mon, 11 Jun 2007 10:04:49 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:52195)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HxkVh-0004YL-2K; Mon, 11 Jun 2007 15:04:45 +0100
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <38558EBB-DD0F-4D33-8AF9-2AB26C475F24@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Mon, 11 Jun 2007 15:04:55 +0100
To: IETF AVT WG <avt@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: Roni Even <roni.even@polycom.co.il>, Tom Taylor <tom.taylor@rogers.com>
Subject: [AVT] Working group last call: draft-ietf-avt-rtp-vorbis-05
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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 to announce a working group last call on the RTP Payload  
Format for Vorbis Encoded Audio (http://www.ietf.org/internet-drafts/ 
draft-ietf-avt-rtp-vorbis-05.txt). Please send any final comments on  
this draft to the avt@ietf.org mailing list by 25th June 2007. If no  
substantive comments are received by that time, we will request the  
IESG consider this draft for publication as a proposed standard RFC.

Colin (as chair)



-- 
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 Jun 11 11:02: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 1HxlPd-0007Av-Pe; Mon, 11 Jun 2007 11:02:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HxlPc-00075n-9v
	for avt@ietf.org; Mon, 11 Jun 2007 11:02:32 -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 1HxlPa-0005dk-UI
	for avt@ietf.org; Mon, 11 Jun 2007 11:02:32 -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
	l5BF2RYT020729; Mon, 11 Jun 2007 08:02:27 -0700
Date: Mon, 11 Jun 2007 08:08:50 -0700 (PDT)
From: Stephen Casner <casner@acm.org>
To: "pieter.demuytere" <pieter.demuytere@intec.ugent.be>
Subject: Re: [AVT] RTP - Last sequence number vs highest sequence number
In-Reply-To: <466D4F36.2020409@intec.ugent.be>
Message-ID: <20070611075803.B18400@oak.packetdesign.com>
References: <466D4F36.2020409@intec.ugent.be>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
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

On Mon, 11 Jun 2007, pieter.demuytere wrote:

> In RFC 3550, the number of packets expected is defined to be the extended last
> sequence number received less the initial sequence number received. However,
> in the example code given in appendix A.1, the (extended) highest sequence
> number is used, and not the (extended) last sequence number. My feeling is
> that the last sequence number received is not automatically equal to the
> highest sequence number received, due to packet reordering. Is it allowed to
> use the (extended) highest sequence number for the calculation of the number
> of packets expected?

This appears to be the result of incomplete editing on my part.  I had
not noticed the problem before your question, and it did not come up
during the revision from RFC1889 to RFC3550.  An earlier version of
the text may have used "last" everywhere, then to clarify exactly the
point you raise, the word "last" was changed to "highest", but not
everywhere.

If you'll notice, the definition of "cumulative number of packets
lost" says, in part:

      The number of packets expected is defined to be the extended
      last sequence number received, as defined next, less the initial
      sequence number received.  This may be calculated as shown in
      Appendix A.3.

The next definition is "extended highest sequence number received",
not "extended last sequence number received".  Thus, these phrases are
both intended to mean the same thing, i.e., the highest number.

Furthermore, Appendix A.3 calculates "extended_max", which is the
highest sequence number received.

                                                        -- Steve

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



From avt-bounces@ietf.org Mon Jun 11 14:51: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 1HxozL-0006Cr-Ew; Mon, 11 Jun 2007 14:51:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxozJ-00068U-CR; Mon, 11 Jun 2007 14:51:37 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HxozI-0004iG-1m; Mon, 11 Jun 2007 14:51:37 -0400
Received: from relay8.apple.com (relay8.apple.com [17.128.113.38])
	by mail-out4.apple.com (Postfix) with ESMTP id C1B558B4466;
	Mon, 11 Jun 2007 11:51:35 -0700 (PDT)
Received: from relay8.apple.com (unknown [127.0.0.1])
	by relay8.apple.com (Symantec Mail Security) with ESMTP id 8062C40101; 
	Mon, 11 Jun 2007 11:51:35 -0700 (PDT)
X-AuditID: 11807126-a0085bb00000081c-eb-466d99b70f0d
Received: from [17.202.35.52] (unknown [17.219.198.136])
	by relay8.apple.com (Apple SCV relay) with ESMTP id 1550840103;
	Mon, 11 Jun 2007 11:51:35 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p0624089fc2934983424f@[17.202.35.52]>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C049E7CE9@IsrExch01.israel.polycom.com>
References: <144ED8561CE90C41A3E5908EDECE315C049E7CE9@IsrExch01.israel.polycom.com>
Date: Mon, 11 Jun 2007 11:51:24 -0700
To: "Even, Roni" <roni.even@polycom.co.il>,
	"Kalleitner, Franz" <franz.kalleitner@siemens.com>,
	mmusic <mmusic@ietf.org>, IETF AVT WG <avt@ietf.org>
From: Dave Singer <singer@apple.com>
Subject: RE: AW: [AVT] RE: [MMUSIC] questions about grouping media streams
	in  RTPand SDP (RFC3388 etc), advice needed
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: "Clinton Priddle \(KI/EAB\)" <clinton.priddle@ericsson.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

At 10:10  +0300 10/06/07, Even, Roni wrote:
>Dave,
>I understand that you intend to send two media streams using two m lines
>without grouping and any specific semantics to identify the stream.
>Our experience is that if you have two video m lines you can not know
>which one the other will pick if he does not understand the relation
>between the streams.
>Roni

Roni

you keep missing that the streams have attributes that tell me which is which.

m=video
a=fmtp: yes this is a foobar primary stream
m=video
a=fmtp:yes this is a foobar repair stream

if I see such an SDP with only one foobar primary and only one foobar 
repair, it's fairly clear that the foobar repair stream is associated 
with the foobar primary stream, without needing grouping.

I only need grouping if I have two primary streams, and that use case 
is not yet in our requirements.  It would be nice to document, but 
we're not in a hurry.
-- 
David Singer
Apple/QuickTime

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



From avt-bounces@ietf.org Mon Jun 11 15: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 1HxpuB-00029V-9A; Mon, 11 Jun 2007 15:50:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hxptr-000116-Bk; Mon, 11 Jun 2007 15:50:03 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hxptq-0007Vf-N5; Mon, 11 Jun 2007 15:50:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 7F31826EBD;
	Mon, 11 Jun 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Hxptq-000574-Cb; Mon, 11 Jun 2007 15:50: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: <E1Hxptq-000574-Cb@stiedprstage1.ietf.org>
Date: Mon, 11 Jun 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-speex-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		: RTP Payload Format for the Speex Codec
	Author(s)	: G. Herlein, et al.
	Filename	: draft-ietf-avt-rtp-speex-01.txt
	Pages		: 21
	Date		: 2007-6-11
	
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-01.txt

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

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

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

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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-avt-rtp-speex-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-6-11105638.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-rtp-speex-01.txt

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

Content-Type: text/plain
Content-ID: <2007-6-11105638.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 Jun 12 00:01: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 1HxxYy-00012T-0n; Tue, 12 Jun 2007 00:01:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxxYw-000114-R5; Tue, 12 Jun 2007 00:00:58 -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 1HxxYu-0001LE-Jl; Tue, 12 Jun 2007 00:00:58 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 12 Jun 2007 00:00:56 -0400
To: Dave Singer <singer@apple.com>
Subject: Re: AW: [AVT] RE: [MMUSIC] questions about grouping media streams
	in  RTPand SDP (RFC3388 etc), advice needed
References: <144ED8561CE90C41A3E5908EDECE315C049E7CE9@IsrExch01.israel.polycom.com>
	<p0624089fc2934983424f@[17.202.35.52]>
From: Randell Jesup <rjesup@wgate.com>
Date: Tue, 12 Jun 2007 00:00:54 -0400
In-Reply-To: <p0624089fc2934983424f@[17.202.35.52]> (Dave Singer's message
	of "Mon, 11 Jun 2007 11:51:24 -0700")
Message-ID: <ybumyz5keix.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 12 Jun 2007 04:00:56.0287 (UTC)
	FILETIME=[4739D6F0:01C7ACA6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: "Clinton Priddle \(KI/EAB\)" <clinton.priddle@ericsson.com>, "Even,
	Roni" <roni.even@polycom.co.il>, mmusic <mmusic@ietf.org>,
	IETF 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

Dave Singer <singer@apple.com> writes:
>At 10:10  +0300 10/06/07, Even, Roni wrote:
>>I understand that you intend to send two media streams using two m lines
>>without grouping and any specific semantics to identify the stream.
>>Our experience is that if you have two video m lines you can not know
>>which one the other will pick if he does not understand the relation
>>between the streams.

>you keep missing that the streams have attributes that tell me which is which.
>
>m=video
>a=fmtp: yes this is a foobar primary stream
>m=video
>a=fmtp:yes this is a foobar repair stream
>
>if I see such an SDP with only one foobar primary and only one foobar
>repair, it's fairly clear that the foobar repair stream is associated with
>the foobar primary stream, without needing grouping.

Roni's point was really not that *you* wouldn't be able to tell, but that
some other UA (which "does not understand the relation beween the streams")
could/would mis-interpret the SDP.  This of course assumes they think at
least one payload for each stream is something they know how to
send/receive.

That's also a problem with the current grouping RFC (along with the
chicken-and-egg syndrome).

-- 
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 Jun 12 00:59: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 1HxyTA-0003Ic-8t; Tue, 12 Jun 2007 00:59:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxyT9-0003IU-M4; Tue, 12 Jun 2007 00:59:03 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HxyT9-0003nK-9T; Tue, 12 Jun 2007 00:59:03 -0400
Received: from relay5.apple.com (relay5.apple.com [17.128.113.35])
	by mail-out4.apple.com (Postfix) with ESMTP id E18998C0EFC;
	Mon, 11 Jun 2007 21:59:02 -0700 (PDT)
Received: from relay5.apple.com (unknown [127.0.0.1])
	by relay5.apple.com (Symantec Mail Security) with ESMTP id C965D29C003; 
	Mon, 11 Jun 2007 21:59:02 -0700 (PDT)
X-AuditID: 11807123-9e01ebb000000a23-1a-466e2816fffe
Received: from [17.202.35.52] (unknown [17.151.73.94])
	by relay5.apple.com (Apple SCV relay) with ESMTP id 4A2DE30400B;
	Mon, 11 Jun 2007 21:59:02 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p062408c1c293d7cf643f@[17.202.35.52]>
In-Reply-To: <ybumyz5keix.fsf@jesup.eng.wgate.com>
References: <144ED8561CE90C41A3E5908EDECE315C049E7CE9@IsrExch01.israel.polycom.com>
	<p0624089fc2934983424f@[17.202.35.52]>
	<ybumyz5keix.fsf@jesup.eng.wgate.com>
Date: Mon, 11 Jun 2007 21:57:38 -0700
To: Randell Jesup <rjesup@wgate.com>
From: Dave Singer <singer@apple.com>
Subject: Re: AW: [AVT] RE: [MMUSIC] questions about grouping media streams
	in  RTPand SDP (RFC3388 etc), advice needed
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: "Clinton Priddle \(KI/EAB\)" <clinton.priddle@ericsson.com>, "Even,
	Roni" <roni.even@polycom.co.il>, mmusic <mmusic@ietf.org>,
	IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

At 0:00  -0400 12/06/07, Randell Jesup wrote:
>Dave Singer <singer@apple.com> writes:
>>At 10:10  +0300 10/06/07, Even, Roni wrote:
>>>I understand that you intend to send two media streams using two m lines
>>>without grouping and any specific semantics to identify the stream.
>>>Our experience is that if you have two video m lines you can not know
>>>which one the other will pick if he does not understand the relation
>>>between the streams.
>
>>you keep missing that the streams have attributes that tell me 
>>which is which.
>>
>>m=video
>>a=fmtp: yes this is a foobar primary stream
>>m=video
>>a=fmtp:yes this is a foobar repair stream
>>
>>if I see such an SDP with only one foobar primary and only one foobar
>>repair, it's fairly clear that the foobar repair stream is associated with
>>the foobar primary stream, without needing grouping.
>
>Roni's point was really not that *you* wouldn't be able to tell, but that
>some other UA (which "does not understand the relation beween the streams")
>could/would mis-interpret the SDP.  This of course assumes they think at
>least one payload for each stream is something they know how to
>send/receive.

Ah, OK.  Sure, if I was introducing this for an existing media type, 
and the payload type of the repair stream was recognizable (maybe the 
same), that would be a problem.

My immediate need is for a new codec, and anyone who can decode 
either stream will have read the document that contains the media 
tagging, so I think I dodge that bullet also.

>
>That's also a problem with the current grouping RFC (along with the
>chicken-and-egg syndrome).
>
>--
>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)
>
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www1.ietf.org/mailman/listinfo/mmusic


-- 
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 Jun 12 03:00: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 1Hy0N4-00006e-Bf; Tue, 12 Jun 2007 03:00:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hy0N2-0008VP-0r; Tue, 12 Jun 2007 03:00: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 1Hy0N0-0005Bb-F2; Tue, 12 Jun 2007 03:00:52 -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: AW: [AVT] RE: [MMUSIC] questions about grouping media streamsin
	RTPand SDP (RFC3388 etc), advice needed
Date: Tue, 12 Jun 2007 10:01:26 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04A6FB61@IsrExch01.israel.polycom.com>
In-Reply-To: <p062408c1c293d7cf643f@[17.202.35.52]>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AW: [AVT] RE: [MMUSIC] questions about grouping media streamsin
	RTPand SDP (RFC3388 etc), advice needed
Thread-Index: Acesroucu/Kdm0wfTYSUcgd633mKcAAEJ9Og
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Dave Singer" <singer@apple.com>,
	"Randell Jesup" <rjesup@wgate.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: "Clinton Priddle \(KI/EAB\)" <clinton.priddle@ericsson.com>,
	mmusic <mmusic@ietf.org>, IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Dave,
Now we are going to a different topic.
Is this a specific codec topic or a general media repair stream.=20
I thought that we are addressing a general dependency problem and not a
one specific codec problem.
Roni

> -----Original Message-----
> From: Dave Singer [mailto:singer@apple.com]
> Sent: Tuesday, June 12, 2007 7:58 AM
> To: Randell Jesup
> Cc: Clinton Priddle (KI/EAB); Kalleitner,Franz; Even, Roni; mmusic;
IETF
> AVT WG
> Subject: Re: AW: [AVT] RE: [MMUSIC] questions about grouping media
> streamsin RTPand SDP (RFC3388 etc), advice needed
>=20
> At 0:00  -0400 12/06/07, Randell Jesup wrote:
> >Dave Singer <singer@apple.com> writes:
> >>At 10:10  +0300 10/06/07, Even, Roni wrote:
> >>>I understand that you intend to send two media streams using two m
> lines
> >>>without grouping and any specific semantics to identify the stream.
> >>>Our experience is that if you have two video m lines you can not
know
> >>>which one the other will pick if he does not understand the
relation
> >>>between the streams.
> >
> >>you keep missing that the streams have attributes that tell me
> >>which is which.
> >>
> >>m=3Dvideo
> >>a=3Dfmtp: yes this is a foobar primary stream
> >>m=3Dvideo
> >>a=3Dfmtp:yes this is a foobar repair stream
> >>
> >>if I see such an SDP with only one foobar primary and only one
foobar
> >>repair, it's fairly clear that the foobar repair stream is
associated
> with
> >>the foobar primary stream, without needing grouping.
> >
> >Roni's point was really not that *you* wouldn't be able to tell, but
that
> >some other UA (which "does not understand the relation beween the
> streams")
> >could/would mis-interpret the SDP.  This of course assumes they think
at
> >least one payload for each stream is something they know how to
> >send/receive.
>=20
> Ah, OK.  Sure, if I was introducing this for an existing media type,
> and the payload type of the repair stream was recognizable (maybe the
> same), that would be a problem.
>=20
> My immediate need is for a new codec, and anyone who can decode
> either stream will have read the document that contains the media
> tagging, so I think I dodge that bullet also.
>=20
> >
> >That's also a problem with the current grouping RFC (along with the
> >chicken-and-egg syndrome).
> >
> >--
> >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)
> >
> >
> >_______________________________________________
> >mmusic mailing list
> >mmusic@ietf.org
> >https://www1.ietf.org/mailman/listinfo/mmusic
>=20
>=20
> --
> David Singer
> Apple/QuickTime
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic

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



From avt-bounces@ietf.org Tue Jun 12 03:06: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 1Hy0Sa-0002ln-2N; Tue, 12 Jun 2007 03:06:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hy0SY-0002lE-6M; Tue, 12 Jun 2007 03:06:34 -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 1Hy0SX-0007hf-GZ; Tue, 12 Jun 2007 03:06:34 -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: AW: [AVT] RE: [MMUSIC] questions about grouping media streams in
	RTPand SDP (RFC3388 etc), advice needed
Date: Tue, 12 Jun 2007 10:07:09 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04A6FB67@IsrExch01.israel.polycom.com>
In-Reply-To: <ybumyz5keix.fsf@jesup.eng.wgate.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AW: [AVT] RE: [MMUSIC] questions about grouping media streams in
	RTPand SDP (RFC3388 etc), advice needed
Thread-Index: AcespnQuxIz3v3tWQVGzi83gVe89awAGS9CQ
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Randell Jesup" <rjesup@wgate.com>,
	"Dave Singer" <singer@apple.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: "Clinton Priddle \(KI/EAB\)" <clinton.priddle@ericsson.com>,
	mmusic <mmusic@ietf.org>, IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Randell,

I think that using grouping gives a better hint to the offerer if the
answer do not support this group semantics by excluding the group
attribute in the answer=20
If you just give two m-lines the answer does not tell if the answerer
support two streams and decided for the moment to do one or if it does
not support/understand the meaning of the offer.

BTW: I think that this may have some relation also to the service tag
work but this may open a can of worms
Roni =20

> -----Original Message-----
> From: Randell Jesup [mailto:rjesup@wgate.com]
> Sent: Tuesday, June 12, 2007 7:01 AM
> To: Dave Singer
> Cc: Even, Roni; Kalleitner, Franz; mmusic; IETF AVT WG; Clinton
Priddle
> (KI/EAB)
> Subject: Re: AW: [AVT] RE: [MMUSIC] questions about grouping media
streams
> in RTPand SDP (RFC3388 etc), advice needed
>=20
> Dave Singer <singer@apple.com> writes:
> >At 10:10  +0300 10/06/07, Even, Roni wrote:
> >>I understand that you intend to send two media streams using two m
lines
> >>without grouping and any specific semantics to identify the stream.
> >>Our experience is that if you have two video m lines you can not
know
> >>which one the other will pick if he does not understand the relation
> >>between the streams.
>=20
> >you keep missing that the streams have attributes that tell me which
is
> which.
> >
> >m=3Dvideo
> >a=3Dfmtp: yes this is a foobar primary stream
> >m=3Dvideo
> >a=3Dfmtp:yes this is a foobar repair stream
> >
> >if I see such an SDP with only one foobar primary and only one foobar
> >repair, it's fairly clear that the foobar repair stream is associated
> with
> >the foobar primary stream, without needing grouping.
>=20
> Roni's point was really not that *you* wouldn't be able to tell, but
that
> some other UA (which "does not understand the relation beween the
> streams")
> could/would mis-interpret the SDP.  This of course assumes they think
at
> least one payload for each stream is something they know how to
> send/receive.
>=20
> That's also a problem with the current grouping RFC (along with the
> chicken-and-egg syndrome).
>=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 Tue Jun 12 04:01: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 1Hy1JW-0001P4-3I; Tue, 12 Jun 2007 04:01:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hy1JS-0001OL-8z; Tue, 12 Jun 2007 04:01:14 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hy1JQ-0007HB-It; Tue, 12 Jun 2007 04:01:14 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l5C80i90007537; Tue, 12 Jun 2007 11:01:10 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 12 Jun 2007 11:01:08 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 12 Jun 2007 11:01:08 +0300
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by
	esebh101.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 12 Jun 2007 11:01:08 +0300
Received: from [172.21.35.94] (esdhcp03594.research.nokia.com [172.21.35.94])
	by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l5C816jm023828; Tue, 12 Jun 2007 11:01:07 +0300
In-Reply-To: <BCE00CA9-168D-43CE-95D2-C1FE454160B1@nokia.com>
References: <E1Ht7hi-0007MN-6P@stiedprstage1.ietf.org>
	<BCE00CA9-168D-43CE-95D2-C1FE454160B1@nokia.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <FA3205C2-4DBC-4161-A6FE-BB9F5F3067E7@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
Date: Tue, 12 Jun 2007 11:01:04 +0300
To: tsvwg WG <tsvwg@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 12 Jun 2007 08:01:08.0418 (UTC)
	FILETIME=[D5868220:01C7ACC7]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: Behave WG <behave@ietf.org>, IETF AVT WG <avt@ietf.org>,
	mmusic <mmusic@ietf.org>
Subject: [AVT] draft-ietf-tsvwg-udp-guidelines-01
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: tsvwg WG <tsvwg@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>
Content-Type: multipart/mixed; boundary="===============1578307547=="
Errors-To: avt-bounces@ietf.org


--===============1578307547==
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-9--682882164;
	protocol="application/pkcs7-signature"


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

Hi,

Gorry and me just submitted a new -01 version of the "UDP Usage  
Guidelines for Application Designers" draft that TSVWG is putting  
together as a BCP.

Compared to the -00 version, this draft adds a new Section 3.5 that  
gives middlebox traversal guidelines.

(I'm cross-posting to AVT, MMUSIC and BEHAVE, because this addition  
was triggered by the recent discussion around draft-marjou-behave-app- 
rtp-keepalive. Please discuss draft-ietf-tsvwg-udp-guidelines on the  
TSVWG list; I'm setting the reply-to accordingly.)

We'd be interested in comments, both from TSV folks but especially  
from RAI people, who might not have had this on their radar.

Lars

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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGQDCCAvkw
ggJioAMCAQICEGtxkLFHQu1g67hlmYfwPuIwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDEwNDE2MTE1NFoXDTA4MDEwNDE2MTE1
NFowXDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2Vy
dDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9raWEuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEA26hjntVPZMiwh4d8tyuk9KiucvG92BVUGArk5zO1jhmq7tLFgU1mqcIg
VGumfQqjkAzIuh83kxIiqBrB05Wvxp85apwt4sUCvzMe8mQWzZZZYp0rBzwpOj+VC5pxsMRYtYW+
BaTFBEmvFr7D7C7roZUk0lDppS5SZFs4SQbEe9ykB9aeUf1iTiw2+ikyP2+JEYto14WYCoxFWbms
FbQ1uaaK+yn1WH2YHhyMfi0IOxuT0jtbsngjHJMpWIqq334zBhj+rPSUug47YBHr41FCDMHbbbjv
WbyTyDYneOW3WY8LY8bGWVlAknQGB7lgduShe6e0RI/7SL/VE6X27lM9LwIDAQABozIwMDAgBgNV
HREEGTAXgRVsYXJzLmVnZ2VydEBub2tpYS5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUF
AAOBgQCx3nxxTg/WowobVTRXBiXUEEZj4LBiunWbuAnR0UbJIgijvq3JbiJvZo2gUGiW9LPaHSBz
4oxT1VR/S/6O0a4e87oV5cOQm6ReB68o9rDfUzxHTwoCfv2wwMwBrXyzQMjyQK4Lt8siV41gmZpm
rSXMhjTJdd9uYYNoZKQLq+VM+TCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgG
A1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMg
RGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3
DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3
MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5
KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzAN
BgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9
fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+
uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMB
Af8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3
dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgG
A1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcP
f6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH
2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8x
ggMQMIIDDAIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAo
UHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ
a3GQsUdC7WDruGWZh/A+4jAJBgUrDgMCGgUAoIIBbzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcB
MBwGCSqGSIb3DQEJBTEPFw0wNzA2MTIwODAxMDRaMCMGCSqGSIb3DQEJBDEWBBTioSuoUwcZjUaQ
E3XWTcgn3290IzCBhQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0ECEGtxkLFHQu1g67hlmYfwPuIwgYcGCyqGSIb3DQEJEAILMXigdjBiMQsw
CQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UE
AxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEGtxkLFHQu1g67hlmYfwPuIw
DQYJKoZIhvcNAQEBBQAEggEAyElFq8OXQqqtH/+fJytFT+6ri6pRz9Ze1P+nXrBA2Qhk6TZ8QvLN
TJC21TB4NrgZ696G002aUbwLNB0/6J/pGmOtGdWANUyNU5hn/kbs3a5JfDUMLDAZsDm/EZ5QiaE5
eQs+u0qI1GeHWzJuEmgdnx8RVP8Pup/sqMkyX+2QIS4ZCpZRFlAIEpGwZhswpcA5CO9Ag0hENMg7
kZp2sGkZD5zLzNBCd2MnmklRuSsn2D7c1wOcUdffSJ1p8Gy7jVk7ZxtYcGm5m8wLJpQSDBpxC1zI
kJyhXvgedxXFpZU+yfYjtxCsQLmG0bpF+uPVLYGtnHWIUSzD8zQu2QiHYW4geAAAAAAAAA==

--Apple-Mail-9--682882164--


--===============1578307547==
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

--===============1578307547==--




From avt-bounces@ietf.org Tue Jun 12 08:43: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 1Hy5iL-0006xb-8n; Tue, 12 Jun 2007 08:43:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy5iK-0006xO-6q
	for avt@ietf.org; Tue, 12 Jun 2007 08:43:12 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hy5iH-0005Z4-RI
	for avt@ietf.org; Tue, 12 Jun 2007 08:43:12 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:56164)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1Hy5iE-0007Xs-Co; Tue, 12 Jun 2007 13:43:06 +0100
In-Reply-To: <E1Hxptq-000574-Cb@stiedprstage1.ietf.org>
References: <E1Hxptq-000574-Cb@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: <1DE870BB-8980-46E8-A43D-5377BD6106CD@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-speex-01.txt 
Date: Tue, 12 Jun 2007 13:43:17 +0100
To: Greg Herlein <gherlein@herlein.com>, jean-marc.valin@usherbrooke.ca,
	"Alfred E. Heggestad" <aeh@db.org>, jack@atosc.org
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
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 11 Jun 2007, at 20:50, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Audio/Video Transport Working  
> Group of the IETF.
>
> 	Title		: RTP Payload Format for the Speex Codec
> 	Author(s)	: G. Herlein, et al.
> 	Filename	: draft-ietf-avt-rtp-speex-01.txt
> 	Pages		: 21
> 	Date		: 2007-6-11
> 	
> 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-01.txt

This looks to be in pretty good shape, the main issue being mapping  
parameters to the "a=fmtp:" line in SDP. Detailed comments follow:

Marker bit "to indicate that the RTP packet contains at least one  
complete frame" is unusual for audio (although typical for video). It  
would be better used to indicate first packet after a silent period,  
as is usual for audio codecs.

Section 3.3: "Sampling rate values of 8000, 16000 or 32000 Hz MUST be  
used.  Any other sampling rates MUST NOT be used" is confusing.  
Better to say "The sampling rate MUST be either 8000 Hz, 16000 Hz, or  
32000 Hz".

Section 4.1.1: "rate" needs to be listed a required parameter, since  
the codec supports several sampling rates.

Section 5: the "a=fmtp:" attribute is for media type parameters only.  
If you wish to define vbr, cng, and mode parameters, they must be  
defined as media type parameters in the IANA considerations, and then  
mapped into the "a=fmtp:" line. Section 6.2 of RFC 4749 is a good  
example of how to do this.

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 Tue Jun 12 08:52: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 1Hy5r8-0001Yp-Ja; Tue, 12 Jun 2007 08:52:18 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy5r6-0001YQ-6I
	for avt@ietf.org; Tue, 12 Jun 2007 08:52:16 -0400
Received: from smtp-out4.libero.it ([212.52.84.46])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Hy5r3-0005P8-Kj
	for avt@ietf.org; Tue, 12 Jun 2007 08:52:16 -0400
Received: from localhost (172.31.0.42) by smtp-out4.libero.it (7.3.120)
	id 4611FF5204C8ECC2; Tue, 12 Jun 2007 14:51:44 +0200
X-Scanned: with antispam and antivirus automated system at libero.it
Received: from smtp-out4.libero.it ([172.31.0.40])
	by localhost (asav-out2.libero.it [192.168.32.30]) (amavisd-new,
	port 10024)
	with ESMTP id E4pT2AADeWBA; Tue, 12 Jun 2007 14:51:44 +0200 (CEST)
Received: from [192.168.0.6] (151.43.234.61) by smtp-out4.libero.it (7.3.120)
	id 4611FEBC0525F789; Tue, 12 Jun 2007 14:51:44 +0200
Message-ID: <466E979A.2010603@gentoo.org>
Date: Tue, 12 Jun 2007 14:54:50 +0200
From: Luca Barbato <lu_zero@gentoo.org>
User-Agent: Thunderbird 2.0.0.0 (X11/20070607)
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-speex-01.txt
References: <E1Hxptq-000574-Cb@stiedprstage1.ietf.org>
	<1DE870BB-8980-46E8-A43D-5377BD6106CD@csperkins.org>
In-Reply-To: <1DE870BB-8980-46E8-A43D-5377BD6106CD@csperkins.org>
X-Enigmail-Version: 0.95.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: jack@atosc.org, 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:
> Section 4.1.1: "rate" needs to be listed a required parameter, since the
> codec supports several sampling rates.

Isn't it delivered in band/bitstream and subject to change every 20ms?

lu

-- 

Luca Barbato

Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero


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



From avt-bounces@ietf.org Tue Jun 12 11:35: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 1Hy8Og-0002mk-8I; Tue, 12 Jun 2007 11:35:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hy8Oe-0002ib-Tq; Tue, 12 Jun 2007 11:35:04 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hy8Od-0001hM-7k; Tue, 12 Jun 2007 11:35:04 -0400
Received: from relay6.apple.com (relay6.apple.com [17.128.113.36])
	by mail-out4.apple.com (Postfix) with ESMTP id CF9E58CBED9;
	Tue, 12 Jun 2007 08:35:02 -0700 (PDT)
Received: from relay6.apple.com (unknown [127.0.0.1])
	by relay6.apple.com (Symantec Mail Security) with ESMTP id BDF58101A6; 
	Tue, 12 Jun 2007 08:35:02 -0700 (PDT)
X-AuditID: 11807124-a16c9bb000000801-cc-466ebd268213
Received: from [17.202.35.52] (unknown [17.151.68.83])
	by relay6.apple.com (Apple SCV relay) with ESMTP id 4CDAB100AB;
	Tue, 12 Jun 2007 08:35:02 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p062408c5c2946d5970b2@[17.202.35.52]>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C04A6FB61@IsrExch01.israel.polycom.com>
References: <144ED8561CE90C41A3E5908EDECE315C04A6FB61@IsrExch01.israel.polycom.com>
Date: Tue, 12 Jun 2007 08:34:39 -0700
To: "Even, Roni" <roni.even@polycom.co.il>,
 Randell Jesup <rjesup@wgate.com>
From: Dave Singer <singer@apple.com>
Subject: RE: AW: [AVT] RE: [MMUSIC] questions about grouping media
	streamsin  RTPand SDP (RFC3388 etc), advice needed
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: "Clinton Priddle \(KI/EAB\)" <clinton.priddle@ericsson.com>,
	mmusic <mmusic@ietf.org>, IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

At 10:01  +0300 12/06/07, Even, Roni wrote:
>Dave,
>Now we are going to a different topic.
>Is this a specific codec topic or a general media repair stream.
>I thought that we are addressing a general dependency problem and not a
>one specific codec problem.
>Roni

If there was a solution to the general problem available, then I 
would have used it.  But the immediate need is for a specific, new, 
codec and payload format;  the example I gave of a video codec was 
just an example (and simpler to explain).


-- 
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 Jun 12 12:29: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 1Hy9FR-0003Be-Ie; Tue, 12 Jun 2007 12:29:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy8q7-0000qX-B5
	for avt@ietf.org; Tue, 12 Jun 2007 12:03:27 -0400
Received: from anode.atosc.org ([195.154.245.166])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hy8q2-0008NX-Kv
	for avt@ietf.org; Tue, 12 Jun 2007 12:03:27 -0400
Received: from anode.atosc.org (localhost.localdomain [127.0.0.1])
	by internal.atosc.org (Postfix) with ESMTP
	id D6BF2FC06; Tue, 12 Jun 2007 17:56:51 +0200 (CEST)
Received: from antisip.antisip.com (unknown [77.193.2.49])
	by anode.atosc.org (Postfix) with ESMTP
	id 56E9EFB1D; Tue, 12 Jun 2007 17:56:51 +0200 (CEST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by antisip.antisip.com (Postfix) with ESMTP id A7DB81FEC8;
	Tue, 12 Jun 2007 18:03:29 +0200 (CEST)
X-Virus-Scanned: by hand at fauche.org
Received: from antisip.antisip.com ([127.0.0.1])
	by localhost (antisip.antisip.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ysgLr2QyrB8Y; Tue, 12 Jun 2007 18:03:23 +0200 (CEST)
Received: by antisip.antisip.com (Postfix, from userid 1000)
	id 2AAD920016; Tue, 12 Jun 2007 18:03:23 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
	by antisip.antisip.com (Postfix) with ESMTP id 2507C1FF0A;
	Tue, 12 Jun 2007 18:03:23 +0200 (CEST)
Date: Tue, 12 Jun 2007 18:03:23 +0200 (CEST)
From: Aymeric Moizard <jack@atosc.org>
X-X-Sender: jack@sip2
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-speex-01.txt
In-Reply-To: <1DE870BB-8980-46E8-A43D-5377BD6106CD@csperkins.org>
Message-ID: <Pine.LNX.4.63.0706121744110.11297@sip2>
References: <E1Hxptq-000574-Cb@stiedprstage1.ietf.org>
	<1DE870BB-8980-46E8-A43D-5377BD6106CD@csperkins.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on anode.atosc.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.8 required=3.0 tests=ALL_TRUSTED,AWL 
	autolearn=failed version=3.0.3
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
X-Mailman-Approved-At: Tue, 12 Jun 2007 12:29:35 -0400
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



On Tue, 12 Jun 2007, Colin Perkins wrote:

>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-speex-01.txt
>
> This looks to be in pretty good shape, the main issue being mapping 
> parameters to the "a=fmtp:" line in SDP. Detailed comments follow:
>
> Marker bit "to indicate that the RTP packet contains at least one complete 
> frame" is unusual for audio (although typical for video). It would be better 
> used to indicate first packet after a silent period, as is usual for audio 
> codecs.

Right that is confusing.

Marker (M) bit: The M bit is set to one on the first packet received 
after a silent period.

> Section 3.3: "Sampling rate values of 8000, 16000 or 32000 Hz MUST be used. 
> Any other sampling rates MUST NOT be used" is confusing. Better to say "The 
> sampling rate MUST be either 8000 Hz, 16000 Hz, or 32000 Hz".

I agree.

> Section 4.1.1: "rate" needs to be listed a required parameter, since the 
> codec supports several sampling rates.

agree too.

> Section 5: the "a=fmtp:" attribute is for media type parameters only. If you 
> wish to define vbr, cng, and mode parameters, they must be defined as media 
> type parameters in the IANA considerations, and then mapped into the 
> "a=fmtp:" line. Section 6.2 of RFC 4749 is a good example of how to do this.

But that's definitly what is being said in section 5: in the following
text, we wanted to inform that you MUST use a=fmtp for mode, vbr and cng:

    An other way to make recommendations to the remote Speex encoder is
    to use its specific parameters via the a=fmtp: directive.  The
    following parameters are defined for use in this way:

Would you advise to change it to this text?:

    An other way to make recommendations to the remote Speex encoder is
    to use its specific parameters via the a=fmtp: directive.  "mode",
    "cng" and "vbr" parameter MUST be specified using this directive. The
    parameters are defined for use in this way:

As I understand your comment, you mean that "mode", "vbr" and "cng" should
appear in the section "4.1.1.  Registration of media type audio/speex"? 
Right?

tks,
Aymeric MOIZARD / ANTISIP
amsip - http://www.antisip.com
osip2 - http://www.osip.org
eXosip2 - http://savannah.nongnu.org/projects/exosip/

> 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 Tue Jun 12 16:55: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 1HyDOL-0002hB-PM; Tue, 12 Jun 2007 16:55:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyDOJ-0002h3-BM
	for avt@ietf.org; Tue, 12 Jun 2007 16:55:03 -0400
Received: from dencfw1.jabber.com ([207.182.164.5] helo=roundabout.local)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyDOH-0008CT-2n
	for avt@ietf.org; Tue, 12 Jun 2007 16:55:03 -0400
Received: from roundabout.local (localhost [127.0.0.1])
	by roundabout.local (Postfix) with ESMTP id 838FD61DF9E
	for <avt@ietf.org>; Tue, 12 Jun 2007 14:56:25 -0600 (MDT)
Message-ID: <466F0878.4090700@jabber.org>
Date: Tue, 12 Jun 2007 14:56:24 -0600
From: Peter Saint-Andre <stpeter@jabber.org>
Organization: XMPP Standards Foundation
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.8.1.3) Gecko/20070326 Thunderbird/2.0.0.0 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: avt@ietf.org
Jabber-ID: stpeter@jabber.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 16c9da4896bf5539ae3547c6c25f06a0
Subject: [AVT] draft-ietf-avt-rtp-vorbis: configuration-uri
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-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="===============0265377117=="
Errors-To: avt-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--===============0265377117==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms050602020307000303010505"

This is a cryptographically signed message in MIME format.

--------------ms050602020307000303010505
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

In draft-ietf-avt-rtp-vorbis-05 we find:

       configuration-uri:  the URI of the configuration headers in case
          of out of band transmission.  In the form of
          "protocol://path/to/resource/".

This assumes that URIs have a certain structure and that there is a 
resource with a certain media type available at the URI. While that is 
true of many URI schemes (e.g., http: and rtsp:), it is not true of 
other URI schemes (e.g., mailto: and xmpp:). Unless you have a good 
reason for thinking that a configuration-uri must be of the form you 
specify, I think it would be best to generalize the format so that any 
URI that conforms to RFC 3986 can be used.

As an example, we might define a way to retrieve configuration headers 
via XMPP, for which the URI might be something like this:

xmpp:user@example.com?config;header=resource

The spec goes on to say:

                                           Depending on the specific
          method, a single configuration packet could be retrived by its
          number, or multiple packets could be aggregated in a single
          stream.  Such aggregates MAY be compressed using either bzip2
          [15] or gzip [13].  A sha1 [9] checksum MAY be provided for
          aggregates.  In this latter case the URI will end with the
          aggregate name, followed by its compressed extension if
          applies, a "!" and the base64 [8] representation of the
          sha1hash of the above mentioned compressed aggregated as in:
          "protocol://path/to/resource/aggregated.bz2!sha1hash".  The
          trailing '/' discriminates which of two methods are in use.  It
          MUST follow the associated delivery method parameter (either
          "in_band" or "out_band").

Do you mean that if the URI ends with a trailing slash, then the method 
in use is "simple configuration packet" but if the URI does not end in a 
trailing slash then the method in use is "multiple packets aggregated in 
a single stream"? Again, this seems limited to a specific URI structure, 
since in the XMPP example above we might do something like the following 
for multiple aggregated packets:

xmpp:user@example.com?config;header=resource;aggregate=aggregated.bz2;hash=sha1hash

Finally, must the configuration-uri be a URI or may it be an IRI?

Peter

-- 
Peter Saint-Andre
XMPP Standards Foundation
http://www.xmpp.org/xsf/people/stpeter.shtml


--------------ms050602020307000303010505
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIYVDCC
B3AwggbZoAMCAQICAQkwDQYJKoZIhvcNAQEEBQAwgbAxCzAJBgNVBAYTAklMMQ8wDQYDVQQI
EwZJc3JhZWwxDjAMBgNVBAcTBUVpbGF0MRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMRowGAYD
VQQLExFDQSBBdXRob3JpdHkgRGVwLjEpMCcGA1UEAxMgRnJlZSBTU0wgQ2VydGlmaWNhdGlv
biBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEmFkbWluQHN0YXJ0Y29tLm9yZzAeFw0wNTA0
MDUxNDUxMDNaFw0xMDA0MDQxNDUxMDNaMIGvMQswCQYDVQQGEwJJTDEPMA0GA1UECBMGSXNy
YWVsMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSMwIQYDVQQLExpTZWN1cmUgQ2VydGlmaWNh
dGUgU2lnbmluZzEvMC0GA1UEAxMmU3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IEVtYWlsIEZy
ZWUgQ0ExITAfBgkqhkiG9w0BCQEWEmFkbWluQHN0YXJ0Y29tLm9yZzCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAOOY75tn3YhiCOsNXQn9/4WfpNrX8HLIUlBTLrGtMINvcYJ0
3Nlr9kJyOF5Z8g+2G9Zg+zN8iWGBEpl37bgjYdea3q0AaO9uyZOMLa0rztjFeo7Uw8AjdDmW
kaJQU1c6q9OoieOT6Tf4MvHMGqtbnaOL3Xvz4o6XnH+Ek9h8zPgYgiUw2tIF0ueLayTGiInH
dWM5eYMoz7OnVlUeIurDweT4C9V1TtwplnhWZ7bilcuN4w3/8hndqryqqflbCMlLZWn+1uaT
21d12cdpjBOaqtg6hqiTY4S4+wVAmGrAiOPQ3Z574gljhUKf5ehz7p9xtsb+mjvM1I4yPP8/
vjKZoRUCAwEAAaOCBBMwggQPMA8GA1UdEwEB/wQFMAMBAf8wCwYDVR0PBAQDAgHmMB0GA1Ud
DgQWBBS4Zr17owi6irSy+USIcU+li0GzUTCB3QYDVR0jBIHVMIHSgBQcicOWzL3+MtUNjIEx
tpidjShkjaGBtqSBszCBsDELMAkGA1UEBhMCSUwxDzANBgNVBAgTBklzcmFlbDEOMAwGA1UE
BxMFRWlsYXQxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xGjAYBgNVBAsTEUNBIEF1dGhvcml0
eSBEZXAuMSkwJwYDVQQDEyBGcmVlIFNTTCBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEhMB8G
CSqGSIb3DQEJARYSYWRtaW5Ac3RhcnRjb20ub3JnggEAMB0GA1UdEQQWMBSBEmFkbWluQHN0
YXJ0Y29tLm9yZzAdBgNVHRIEFjAUgRJhZG1pbkBzdGFydGNvbS5vcmcwYgYDVR0fBFswWTAp
oCegJYYjaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL2NhLWNybC5jcmwwLKAqoCiGJmh0dHA6
Ly9jcmwuc3RhcnRjb20ub3JnL2NybC9jYS1jcmwuY3JsMIIBSgYDVR0gBIIBQTCCAT0wggE5
BgsrBgEEAYG1NwEBATCCASgwLwYIKwYBBQUHAgEWI2h0dHA6Ly9jZXJ0LnN0YXJ0Y29tLm9y
Zy9wb2xpY3kucGRmMDUGCCsGAQUFBwIBFilodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvaW50
ZXJtZWRpYXRlLnBkZjCBvQYIKwYBBQUHAgIwgbAwFBYNU3RhcnRDb20gTHRkLjADAgEBGoGX
TGltaXRlZCBMaWFiaWxpdHksIHJlYWQgdGhlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25z
KiBvZiB0aGUgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWls
YWJsZSBhdCBodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvcG9saWN5LnBkZjARBglghkgBhvhC
AQEEBAMCAAcwUAYJYIZIAYb4QgENBEMWQVN0YXJ0Q29tIENsYXNzIDIgUHJpbWFyeSBJbnRl
cm1lZGlhdGUgRnJlZSBTU0wgRW1haWwgQ2VydGlmaWNhdGVzMDIGCWCGSAGG+EIBBAQlFiNo
dHRwOi8vY2VydC5zdGFydGNvbS5vcmcvY2EtY3JsLmNybDAzBglghkgBhvhCAQMEJhYkaHR0
cDovL2NlcnQuc3RhcnRjb20ub3JnL2NydC1jcmwuY3JsMDIGCWCGSAGG+EIBCAQlFiNodHRw
Oi8vY2VydC5zdGFydGNvbS5vcmcvcG9saWN5LnBkZjANBgkqhkiG9w0BAQQFAAOBgQDss9KK
Fx/bCifYjAQTmBtRoHFsdR5ZQ1nlagXKoyJ+IwmdGdiYqAKeaDfjT6bTXHfQvK8kp5xSoz0I
PcpSwztY7UKtylgJwplu1q6vjj4BGB621sD60qzirAhLSqxmpBgjl8HMMMoiM28DCLsshihl
g7wG7Oi/rPIuR8dawiaDejCCCGwwggdUoAMCAQICAwDocDANBgkqhkiG9w0BAQUFADCBrzEL
MAkGA1UEBhMCSUwxDzANBgNVBAgTBklzcmFlbDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEj
MCEGA1UECxMaU2VjdXJlIENlcnRpZmljYXRlIFNpZ25pbmcxLzAtBgNVBAMTJlN0YXJ0Q29t
IENsYXNzIDIgUHJpbWFyeSBFbWFpbCBGcmVlIENBMSEwHwYJKoZIhvcNAQkBFhJhZG1pbkBz
dGFydGNvbS5vcmcwHhcNMDYwNzA3MTYwNTAwWhcNMDcwNzA3MTYwNTAwWjCBvjELMAkGA1UE
BhMCVVMxCzAJBgNVBAgTAkNPMQ8wDQYDVQQHEwZEZW52ZXIxIzAhBgNVBAoTGkphYmJlciBT
b2Z0d2FyZSBGb3VuZGF0aW9uMS0wKwYDVQQLEyRTdGFydENvbSBWZXJpZmllZCBDZXJ0aWZp
Y2F0ZSBNZW1iZXIxGjAYBgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkB
FhJzdHBldGVyQGphYmJlci5vcmcwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCr
zNmM5bxrSxV81PynU608wdGBJaKs0I7Y93//cyNPaooH0M1P20FAkmVjNZ2DhHsb4J4H6Koz
XDJWVpY04lIS7JIhcmy1pL2Aac0ZvPaGANVRexbuxToFF0q3YoO/NLIQXiuIu8BbNl0BHmZz
BHKgsofvKlsLDTQjen85U5GY2Rgg0yRd5/RIRZJwnflJF50VJi8rxYpL6H9W5q9zYtLurjAd
0SSdtCY98YG73vYJyZ5V0ARBUAkc4tg50/XJvubdpmCVJMy6X2zGtKoPfo7LdoOEWbTSCEVu
bA0EQSTlybkGnnkG97Kn44lqm7UGpMWx76IGZQ3IrM/dYDnuUaQpAgMBAAGjggR+MIIEejAM
BgNVHRMEBTADAgEAMAsGA1UdDwQEAwIE8DAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUH
AwQwHQYDVR0OBBYEFGvThDnN4P4ucEfDmnKw2an31COrMIHdBgNVHSMEgdUwgdKAFLhmvXuj
CLqKtLL5RIhxT6WLQbNRoYG2pIGzMIGwMQswCQYDVQQGEwJJTDEPMA0GA1UECBMGSXNyYWVs
MQ4wDAYDVQQHEwVFaWxhdDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEaMBgGA1UECxMRQ0Eg
QXV0aG9yaXR5IERlcC4xKTAnBgNVBAMTIEZyZWUgU1NMIENlcnRpZmljYXRpb24gQXV0aG9y
aXR5MSEwHwYJKoZIhvcNAQkBFhJhZG1pbkBzdGFydGNvbS5vcmeCAQkwggFABgNVHSAEggE3
MIIBMzCCAS8GCysGAQQBgbU3AQECMIIBHjA1BggrBgEFBQcCARYpaHR0cDovL2NlcnQuc3Rh
cnRjb20ub3JnL2ludGVybWVkaWF0ZS5wZGYwLwYIKwYBBQUHAgEWI2h0dHA6Ly9jZXJ0LnN0
YXJ0Y29tLm9yZy9wb2xpY3kucGRmMIGzBggrBgEFBQcCAjCBpjAUFg1TdGFydENvbSBMdGQu
MAMCAQEagY1MaW1pdGVkIExpYWJpbGl0eSwgcmVhZCB0aGUgc2VjdGlvbiAqTGVnYWwgTGlt
aXRhdGlvbnMqIG9mIHRoZSBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIFBvbGljeSBhdmFpbGFi
bGUgYXQgaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL3BvbGljeS5wZGYwZAYDVR0fBF0wWzAs
oCqgKIYmaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwK6ApoCeGJWh0
dHA6Ly9jcmwuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwgYQGCCsGAQUFBwEBBHgwdjA3
BggrBgEFBQcwAYYraHR0cDovL29jc3Auc3RhcnRjb20ub3JnL3N1Yi9jbGFzczIvdXNlci9j
YTA7BggrBgEFBQcwAoYvaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL3N1Yi5jbGFzczIudXNl
ci5jYS5jcnQwEQYJYIZIAYb4QgEBBAQDAgWgMDcGCWCGSAGG+EIBDQQqFihTdGFydENvbSBB
dXRoZW50aWNhdGVkIEVtYWlsIENlcnRpZmljYXRlMDIGCWCGSAGG+EIBBAQlFiNodHRwOi8v
Y2VydC5zdGFydGNvbS5vcmcvY2EtY3JsLmNybDA1BglghkgBhvhCAQMEKBYmaHR0cDovL2Nl
cnQuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwMgYJYIZIAYb4QgEIBCUWI2h0dHA6Ly9j
ZXJ0LnN0YXJ0Y29tLm9yZy9wb2xpY3kucGRmMCMGA1UdEgQcMBqGGGh0dHA6Ly9jZXJ0LnN0
YXJ0Y29tLm9yZzANBgkqhkiG9w0BAQUFAAOCAQEAi8Q3OPqmaAnBgIBm/7dSnbT+613ejmlb
DG6f00pgf+PVLyidelTcCbZckHJvH/Q2tQweEtMVluY5NhELU/gwL9VD0Yn4/aPJpgm4bxJn
0/GeWmqcASfcBwb1XgrZDe17rD22YniJdSP4E6VXWxcS2elHdD08yTPlX+Cab9zLrAv0CVxh
BOYdDX6aNqY5/YxIfdaJKWClkAz+/GRUI24HSMly9SLEz2Lhvz2WitBflWE4+aOIJx7+UPKM
LTSSQfk4WjwTOrQgpc9kjja0q7RdNXOPzOV7WehZo9sUncrIDDg5RkcoclifwOWXe66l6HKZ
uYJCLgc0S5jgHntNU6X/STCCCGwwggdUoAMCAQICAwDocDANBgkqhkiG9w0BAQUFADCBrzEL
MAkGA1UEBhMCSUwxDzANBgNVBAgTBklzcmFlbDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEj
MCEGA1UECxMaU2VjdXJlIENlcnRpZmljYXRlIFNpZ25pbmcxLzAtBgNVBAMTJlN0YXJ0Q29t
IENsYXNzIDIgUHJpbWFyeSBFbWFpbCBGcmVlIENBMSEwHwYJKoZIhvcNAQkBFhJhZG1pbkBz
dGFydGNvbS5vcmcwHhcNMDYwNzA3MTYwNTAwWhcNMDcwNzA3MTYwNTAwWjCBvjELMAkGA1UE
BhMCVVMxCzAJBgNVBAgTAkNPMQ8wDQYDVQQHEwZEZW52ZXIxIzAhBgNVBAoTGkphYmJlciBT
b2Z0d2FyZSBGb3VuZGF0aW9uMS0wKwYDVQQLEyRTdGFydENvbSBWZXJpZmllZCBDZXJ0aWZp
Y2F0ZSBNZW1iZXIxGjAYBgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkB
FhJzdHBldGVyQGphYmJlci5vcmcwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCr
zNmM5bxrSxV81PynU608wdGBJaKs0I7Y93//cyNPaooH0M1P20FAkmVjNZ2DhHsb4J4H6Koz
XDJWVpY04lIS7JIhcmy1pL2Aac0ZvPaGANVRexbuxToFF0q3YoO/NLIQXiuIu8BbNl0BHmZz
BHKgsofvKlsLDTQjen85U5GY2Rgg0yRd5/RIRZJwnflJF50VJi8rxYpL6H9W5q9zYtLurjAd
0SSdtCY98YG73vYJyZ5V0ARBUAkc4tg50/XJvubdpmCVJMy6X2zGtKoPfo7LdoOEWbTSCEVu
bA0EQSTlybkGnnkG97Kn44lqm7UGpMWx76IGZQ3IrM/dYDnuUaQpAgMBAAGjggR+MIIEejAM
BgNVHRMEBTADAgEAMAsGA1UdDwQEAwIE8DAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUH
AwQwHQYDVR0OBBYEFGvThDnN4P4ucEfDmnKw2an31COrMIHdBgNVHSMEgdUwgdKAFLhmvXuj
CLqKtLL5RIhxT6WLQbNRoYG2pIGzMIGwMQswCQYDVQQGEwJJTDEPMA0GA1UECBMGSXNyYWVs
MQ4wDAYDVQQHEwVFaWxhdDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEaMBgGA1UECxMRQ0Eg
QXV0aG9yaXR5IERlcC4xKTAnBgNVBAMTIEZyZWUgU1NMIENlcnRpZmljYXRpb24gQXV0aG9y
aXR5MSEwHwYJKoZIhvcNAQkBFhJhZG1pbkBzdGFydGNvbS5vcmeCAQkwggFABgNVHSAEggE3
MIIBMzCCAS8GCysGAQQBgbU3AQECMIIBHjA1BggrBgEFBQcCARYpaHR0cDovL2NlcnQuc3Rh
cnRjb20ub3JnL2ludGVybWVkaWF0ZS5wZGYwLwYIKwYBBQUHAgEWI2h0dHA6Ly9jZXJ0LnN0
YXJ0Y29tLm9yZy9wb2xpY3kucGRmMIGzBggrBgEFBQcCAjCBpjAUFg1TdGFydENvbSBMdGQu
MAMCAQEagY1MaW1pdGVkIExpYWJpbGl0eSwgcmVhZCB0aGUgc2VjdGlvbiAqTGVnYWwgTGlt
aXRhdGlvbnMqIG9mIHRoZSBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIFBvbGljeSBhdmFpbGFi
bGUgYXQgaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL3BvbGljeS5wZGYwZAYDVR0fBF0wWzAs
oCqgKIYmaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwK6ApoCeGJWh0
dHA6Ly9jcmwuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwgYQGCCsGAQUFBwEBBHgwdjA3
BggrBgEFBQcwAYYraHR0cDovL29jc3Auc3RhcnRjb20ub3JnL3N1Yi9jbGFzczIvdXNlci9j
YTA7BggrBgEFBQcwAoYvaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL3N1Yi5jbGFzczIudXNl
ci5jYS5jcnQwEQYJYIZIAYb4QgEBBAQDAgWgMDcGCWCGSAGG+EIBDQQqFihTdGFydENvbSBB
dXRoZW50aWNhdGVkIEVtYWlsIENlcnRpZmljYXRlMDIGCWCGSAGG+EIBBAQlFiNodHRwOi8v
Y2VydC5zdGFydGNvbS5vcmcvY2EtY3JsLmNybDA1BglghkgBhvhCAQMEKBYmaHR0cDovL2Nl
cnQuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwMgYJYIZIAYb4QgEIBCUWI2h0dHA6Ly9j
ZXJ0LnN0YXJ0Y29tLm9yZy9wb2xpY3kucGRmMCMGA1UdEgQcMBqGGGh0dHA6Ly9jZXJ0LnN0
YXJ0Y29tLm9yZzANBgkqhkiG9w0BAQUFAAOCAQEAi8Q3OPqmaAnBgIBm/7dSnbT+613ejmlb
DG6f00pgf+PVLyidelTcCbZckHJvH/Q2tQweEtMVluY5NhELU/gwL9VD0Yn4/aPJpgm4bxJn
0/GeWmqcASfcBwb1XgrZDe17rD22YniJdSP4E6VXWxcS2elHdD08yTPlX+Cab9zLrAv0CVxh
BOYdDX6aNqY5/YxIfdaJKWClkAz+/GRUI24HSMly9SLEz2Lhvz2WitBflWE4+aOIJx7+UPKM
LTSSQfk4WjwTOrQgpc9kjja0q7RdNXOPzOV7WehZo9sUncrIDDg5RkcoclifwOWXe66l6HKZ
uYJCLgc0S5jgHntNU6X/STGCBCwwggQoAgEBMIG3MIGvMQswCQYDVQQGEwJJTDEPMA0GA1UE
CBMGSXNyYWVsMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSMwIQYDVQQLExpTZWN1cmUgQ2Vy
dGlmaWNhdGUgU2lnbmluZzEvMC0GA1UEAxMmU3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IEVt
YWlsIEZyZWUgQ0ExITAfBgkqhkiG9w0BCQEWEmFkbWluQHN0YXJ0Y29tLm9yZwIDAOhwMAkG
BSsOAwIaBQCgggJJMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8X
DTA3MDYxMjIwNTYyNFowIwYJKoZIhvcNAQkEMRYEFJWB33bompih2tKHmrIYzBEi5UQ4MFIG
CSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMC
AgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIHIBgkrBgEEAYI3EAQxgbowgbcwga8xCzAJ
BgNVBAYTAklMMQ8wDQYDVQQIEwZJc3JhZWwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xIzAh
BgNVBAsTGlNlY3VyZSBDZXJ0aWZpY2F0ZSBTaWduaW5nMS8wLQYDVQQDEyZTdGFydENvbSBD
bGFzcyAyIFByaW1hcnkgRW1haWwgRnJlZSBDQTEhMB8GCSqGSIb3DQEJARYSYWRtaW5Ac3Rh
cnRjb20ub3JnAgMA6HAwgcoGCyqGSIb3DQEJEAILMYG6oIG3MIGvMQswCQYDVQQGEwJJTDEP
MA0GA1UECBMGSXNyYWVsMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSMwIQYDVQQLExpTZWN1
cmUgQ2VydGlmaWNhdGUgU2lnbmluZzEvMC0GA1UEAxMmU3RhcnRDb20gQ2xhc3MgMiBQcmlt
YXJ5IEVtYWlsIEZyZWUgQ0ExITAfBgkqhkiG9w0BCQEWEmFkbWluQHN0YXJ0Y29tLm9yZwID
AOhwMA0GCSqGSIb3DQEBAQUABIIBAEIcAiGKwq9BHOau+8xzzbTRyVx6hbqnko504rhG6X5n
DEUliTaCP/QDlYh0SBS1VtxENSel9yoR18B0jufK6WWoJA7wraODAYJdkdk9geABGFEtk8cP
Ui0HkjiWhLZ2LNoVOReGtOhh8b8BkwAJMVIZh1hh/BmIKTUFmBqm/U8b11jKB2XyGwDkR2m9
YHHdED1mPgvazFs6zTSc00KS3AvG8ndsgq9Q3gDv701W0mti+ZdLddhiI0KKglToAg2so5jE
w9RGEy1OLJXu8LXdu61rxLwZ5t8V54Fqd+1FauUbwzJSIHgYnYxo+VpCR8mzxtYlY93eZ4JH
BmWuYtzpWRQAAAAAAAA=
--------------ms050602020307000303010505--


--===============0265377117==
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

--===============0265377117==--




From avt-bounces@ietf.org Tue Jun 12 20:39: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 1HyGtO-0007rJ-Jt; Tue, 12 Jun 2007 20:39:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyGtM-0007kW-VK
	for avt@ietf.org; Tue, 12 Jun 2007 20:39:20 -0400
Received: from smtp-out4.libero.it ([212.52.84.46])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyGtM-0004ro-GN
	for avt@ietf.org; Tue, 12 Jun 2007 20:39:20 -0400
Received: from localhost (172.31.0.48) by smtp-out4.libero.it (7.3.120)
	id 4611FF5204D54B7F; Wed, 13 Jun 2007 02:39:17 +0200
X-Scanned: with antispam and antivirus automated system at libero.it
Received: from smtp-out3.libero.it ([172.31.0.39])
	by localhost (asav-out7.libero.it [192.168.32.35]) (amavisd-new,
	port 10024)
	with ESMTP id IeS6ZYlg1KAp; Wed, 13 Jun 2007 02:39:17 +0200 (CEST)
Received: from [192.168.0.6] (151.43.234.61) by smtp-out3.libero.it (7.3.120)
	id 4611FDB60530DF28; Wed, 13 Jun 2007 02:39:17 +0200
Message-ID: <466F3D7E.1090409@gentoo.org>
Date: Wed, 13 Jun 2007 02:42:38 +0200
From: Luca Barbato <lu_zero@gentoo.org>
User-Agent: Thunderbird 2.0.0.0 (X11/20070607)
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@jabber.org>
Subject: Re: [AVT] draft-ietf-avt-rtp-vorbis: configuration-uri
References: <466F0878.4090700@jabber.org>
In-Reply-To: <466F0878.4090700@jabber.org>
X-Enigmail-Version: 0.95.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
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

Peter Saint-Andre wrote:
> In draft-ietf-avt-rtp-vorbis-05 we find:
> 
>       configuration-uri:  the URI of the configuration headers in case
>          of out of band transmission.  In the form of
>          "protocol://path/to/resource/".
> 
> This assumes that URIs have a certain structure and that there is a
> resource with a certain media type available at the URI. While that is
> true of many URI schemes (e.g., http: and rtsp:), it is not true of
> other URI schemes (e.g., mailto: and xmpp:). Unless you have a good
> reason for thinking that a configuration-uri must be of the form you
> specify, I think it would be best to generalize the format so that any
> URI that conforms to RFC 3986 can be used.

The rationale for picking this restricted form is just simplicity, I can
relax the spec so it is RECOMMENDED to structure the configuration-uri
this way.

> 
> As an example, we might define a way to retrieve configuration headers
> via XMPP, for which the URI might be something like this:
> 
> xmpp:user@example.com?config;header=resource

I see a problem

> 
> Do you mean that if the URI ends with a trailing slash, then the method
> in use is "simple configuration packet" but if the URI does not end in a
> trailing slash then the method in use is "multiple packets aggregated in
> a single stream"?

Yes.

> Again, this seems limited to a specific URI structure,
> since in the XMPP example above we might do something like the following
> for multiple aggregated packets:
> 
> xmpp:user@example.com?config;header=resource;aggregate=aggregated.bz2;hash=sha1hash

";" has a particular use in sdp, this string cannot be delivered in sdp.

What about mapping the former to

xmpp://user@example.com/aggregated.bz2!sha1hash

and let the application convert it to the format xmpp expect?

Probably xmpp configuration uri would be used just in conjunction with
Jingle and never with sdp so the issue won't happen.

> 
> Finally, must the configuration-uri be a URI or may it be an IRI?
> 

Again I privileged simplicity over features of limited usage. Given that
the URI should be machine generated and machine parsed the IRI
motivation ceases to exist.

BTW I found an error in the SDP example: the first delivery method is
"inline".

It has been fixed already on the xiph svn.

Thank you for the comment.

lu

-- 

Luca Barbato

Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero


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



From avt-bounces@ietf.org Wed Jun 13 03:35: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 1HyNNf-0005DM-Ei; Wed, 13 Jun 2007 03:35:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyNNd-00055f-TX
	for avt@ietf.org; Wed, 13 Jun 2007 03:35:01 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyNNc-0000GB-I7
	for avt@ietf.org; Wed, 13 Jun 2007 03:35:01 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Jun 2007 09:34:56 +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
Subject: RE: [AVT] I-D ACTION:draft-ietf-avt-rtp-speex-01.txt
Date: Wed, 13 Jun 2007 09:34:53 +0200
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD10390E097@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <Pine.LNX.4.63.0706121744110.11297@sip2>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] I-D ACTION:draft-ietf-avt-rtp-speex-01.txt
Thread-Index: AcetDupQLpBrtkAqRuqt0VgNzblFpwAfUe4g
References: <E1Hxptq-000574-Cb@stiedprstage1.ietf.org><1DE870BB-8980-46E8-A43D-5377BD6106CD@csperkins.org>
	<Pine.LNX.4.63.0706121744110.11297@sip2>
From: "SOLLAUD Aurelien RD-TECH-LAN" <aurelien.sollaud@orange-ftgroup.com>
To: "Aymeric Moizard" <jack@atosc.org>,
	"Colin Perkins" <csp@csperkins.org>
X-OriginalArrivalTime: 13 Jun 2007 07:34:56.0234 (UTC)
	FILETIME=[56D804A0:01C7AD8D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
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

> > Marker bit "to indicate that the RTP packet contains at least one=20
> > complete frame" is unusual for audio (although typical for=20
> video). It=20
> > would be better used to indicate first packet after a=20
> silent period,=20
> > as is usual for audio codecs.
>=20
> Right that is confusing.
>=20
> Marker (M) bit: The M bit is set to one on the first packet=20
> received after a silent period.

Hi

I'd rather say:

   The M bit is set to one on the first packet _sent_ after a silent =
period=20

because the M bit is set by the sender

In addition, you should precise
-> a silence period during which packets have not been transmitted =
contiguously


See RFC 3551 =A74.1
   For applications which send either no packets or occasional comfort-
   noise packets during silence, the first packet of a talkspurt, that
   is, the first packet after a silence period during which packets have
   not been transmitted contiguously, SHOULD be distinguished by setting
   the marker bit in the RTP data header to one.  The marker bit in all
   other packets is zero.  The beginning of a talkspurt MAY be used to
   adjust the playout delay to reflect changing network delays.
   Applications without silence suppression MUST set the marker bit to
   zero.


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



From avt-bounces@ietf.org Wed Jun 13 09:41: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 1HyT6A-0003Kc-JV; Wed, 13 Jun 2007 09:41:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyT68-0002xJ-K4
	for avt@ietf.org; Wed, 13 Jun 2007 09:41:20 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyT67-0003Br-6I
	for avt@ietf.org; Wed, 13 Jun 2007 09:41:20 -0400
Received: from vpn8.dcs.gla.ac.uk ([130.209.254.8]:58747)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HyT66-0005qk-Hd; Wed, 13 Jun 2007 14:41:18 +0100
In-Reply-To: <466F3D7E.1090409@gentoo.org>
References: <466F0878.4090700@jabber.org> <466F3D7E.1090409@gentoo.org>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B157CFB8-A0C3-4234-8DEC-FBCEFE682F69@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] draft-ietf-avt-rtp-vorbis: configuration-uri
Date: Wed, 13 Jun 2007 14:41:29 +0100
To: Luca Barbato <lu_zero@gentoo.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

On 13 Jun 2007, at 01:42, Luca Barbato wrote:
> Peter Saint-Andre wrote:
>> In draft-ietf-avt-rtp-vorbis-05 we find:
>>
>>       configuration-uri:  the URI of the configuration headers in  
>> case
>>          of out of band transmission.  In the form of
>>          "protocol://path/to/resource/".
>>
>> This assumes that URIs have a certain structure and that there is a
>> resource with a certain media type available at the URI. While  
>> that is
>> true of many URI schemes (e.g., http: and rtsp:), it is not true of
>> other URI schemes (e.g., mailto: and xmpp:). Unless you have a good
>> reason for thinking that a configuration-uri must be of the form you
>> specify, I think it would be best to generalize the format so that  
>> any
>> URI that conforms to RFC 3986 can be used.
>
> The rationale for picking this restricted form is just simplicity,  
> I can
> relax the spec so it is RECOMMENDED to structure the configuration-uri
> this way.
>
>>
>> As an example, we might define a way to retrieve configuration  
>> headers
>> via XMPP, for which the URI might be something like this:
>>
>> xmpp:user@example.com?config;header=resource
>
> I see a problem
>
>>
>> Do you mean that if the URI ends with a trailing slash, then the  
>> method
>> in use is "simple configuration packet" but if the URI does not  
>> end in a
>> trailing slash then the method in use is "multiple packets  
>> aggregated in
>> a single stream"?
>
> Yes.
>
>> Again, this seems limited to a specific URI structure,
>> since in the XMPP example above we might do something like the  
>> following
>> for multiple aggregated packets:
>>
>> xmpp:user@example.com? 
>> config;header=resource;aggregate=aggregated.bz2;hash=sha1hash
>
> ";" has a particular use in sdp, this string cannot be delivered in  
> sdp.
>
> What about mapping the former to
>
> xmpp://user@example.com/aggregated.bz2!sha1hash
>
> and let the application convert it to the format xmpp expect?

We should probably mandate a standard encoding scheme for all types  
of URI, rather than something specific to XMPP. Does the usual URL  
encoding (with % codes) work?

-- 
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 Jun 13 09:47: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 1HyTCG-000414-Kn; Wed, 13 Jun 2007 09:47:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyTCF-00040z-M2
	for avt@ietf.org; Wed, 13 Jun 2007 09:47:39 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyTCF-00052K-CF
	for avt@ietf.org; Wed, 13 Jun 2007 09:47:39 -0400
Received: from vpn8.dcs.gla.ac.uk ([130.209.254.8]:58761)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HyTCC-0006OO-Jv; Wed, 13 Jun 2007 14:47:36 +0100
In-Reply-To: <Pine.LNX.4.63.0706121744110.11297@sip2>
References: <E1Hxptq-000574-Cb@stiedprstage1.ietf.org>
	<1DE870BB-8980-46E8-A43D-5377BD6106CD@csperkins.org>
	<Pine.LNX.4.63.0706121744110.11297@sip2>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <86C45FFA-8CDC-4A61-B881-A7FE2DAF7EF6@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-speex-01.txt
Date: Wed, 13 Jun 2007 14:47:47 +0100
To: Aymeric Moizard <jack@atosc.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
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

On 12 Jun 2007, at 17:03, Aymeric Moizard wrote:
> On Tue, 12 Jun 2007, Colin Perkins wrote:
...
>> Section 5: the "a=fmtp:" attribute is for media type parameters  
>> only. If you wish to define vbr, cng, and mode parameters, they  
>> must be defined as media type parameters in the IANA  
>> considerations, and then mapped into the "a=fmtp:" line. Section  
>> 6.2 of RFC 4749 is a good example of how to do this.
>
> But that's definitly what is being said in section 5: in the following
> text, we wanted to inform that you MUST use a=fmtp for mode, vbr  
> and cng:
>
>    An other way to make recommendations to the remote Speex encoder is
>    to use its specific parameters via the a=fmtp: directive.  The
>    following parameters are defined for use in this way:
>
> Would you advise to change it to this text?:
>
>    An other way to make recommendations to the remote Speex encoder is
>    to use its specific parameters via the a=fmtp: directive.  "mode",
>    "cng" and "vbr" parameter MUST be specified using this  
> directive. The
>    parameters are defined for use in this way:
>
> As I understand your comment, you mean that "mode", "vbr" and "cng"  
> should
> appear in the section "4.1.1.  Registration of media type audio/ 
> speex"? Right?

The problem is that this sounds, due to "An other way to make  
recommendations", that the "a=fmtp:" parameters are different from  
the media type parameters. In fact the "a=fmtp:" line is an encoding  
of (some of) the media type parameters. All the parameters should be  
listed in the media type registration for audio/speex, and the  
section on SDP usage should explain how to code those in "a=fmtp:"  
and/or other SDP attributes, rather than defining new parameters.

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 Wed Jun 13 09:49: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 1HyTDr-0004Zl-At; Wed, 13 Jun 2007 09:49:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyTDp-0004XF-RL
	for avt@ietf.org; Wed, 13 Jun 2007 09:49:17 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyTDo-0005PY-IA
	for avt@ietf.org; Wed, 13 Jun 2007 09:49:17 -0400
Received: from vpn8.dcs.gla.ac.uk ([130.209.254.8]:58762)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HyTDo-0006Xy-5m; Wed, 13 Jun 2007 14:49:16 +0100
In-Reply-To: <466E979A.2010603@gentoo.org>
References: <E1Hxptq-000574-Cb@stiedprstage1.ietf.org>
	<1DE870BB-8980-46E8-A43D-5377BD6106CD@csperkins.org>
	<466E979A.2010603@gentoo.org>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <1D1656D0-0233-401B-9509-526C864E71AC@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-speex-01.txt
Date: Wed, 13 Jun 2007 14:49:26 +0100
To: Luca Barbato <lu_zero@gentoo.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
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

On 12 Jun 2007, at 13:54, Luca Barbato wrote:
> Colin Perkins wrote:
>> Section 4.1.1: "rate" needs to be listed a required parameter,  
>> since the
>> codec supports several sampling rates.
>
> Isn't it delivered in band/bitstream and subject to change every 20ms?

That should probably be signalled by a change in payload type number,  
with several types being offered if the sender wants the ability to  
change codecs. Doing that has the advantage that the receiver can  
reject sample rates it doesn't support during session setup.

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 Wed Jun 13 10:10: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 1HyTXt-0006zT-Dc; Wed, 13 Jun 2007 10:10:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyTXq-0006zL-VR
	for avt@ietf.org; Wed, 13 Jun 2007 10:09:58 -0400
Received: from atlas.jabber.org ([208.245.212.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyTXl-0002XH-L6
	for avt@ietf.org; Wed, 13 Jun 2007 10:09:58 -0400
Received: by atlas.jabber.org (Postfix, from userid 1005)
	id 5A05421A64E; Wed, 13 Jun 2007 09:15:06 -0500 (CDT)
Date: Wed, 13 Jun 2007 09:15:06 -0500
From: Peter Saint-Andre <stpeter@jabber.org>
To: Luca Barbato <lu_zero@gentoo.org>
Subject: Re: [AVT] draft-ietf-avt-rtp-vorbis: configuration-uri
Message-ID: <20070613141506.GB17886@jabber.org>
References: <466F0878.4090700@jabber.org> <466F3D7E.1090409@gentoo.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <466F3D7E.1090409@gentoo.org>
Jabber-ID: stpeter@jabber.org
User-Agent: Mutt/1.5.6+20040907i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
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 Wed, Jun 13, 2007 at 02:42:38AM +0200, Luca Barbato wrote:
> Peter Saint-Andre wrote:
> > In draft-ietf-avt-rtp-vorbis-05 we find:
> > 
> >       configuration-uri:  the URI of the configuration headers in case
> >          of out of band transmission.  In the form of
> >          "protocol://path/to/resource/".
> > 
> > This assumes that URIs have a certain structure and that there is a
> > resource with a certain media type available at the URI. While that is
> > true of many URI schemes (e.g., http: and rtsp:), it is not true of
> > other URI schemes (e.g., mailto: and xmpp:). Unless you have a good
> > reason for thinking that a configuration-uri must be of the form you
> > specify, I think it would be best to generalize the format so that any
> > URI that conforms to RFC 3986 can be used.
> 
> The rationale for picking this restricted form is just simplicity, I can
> relax the spec so it is RECOMMENDED to structure the configuration-uri
> this way.

That's fine with me.

> > As an example, we might define a way to retrieve configuration headers
> > via XMPP, for which the URI might be something like this:
> > 
> > xmpp:user@example.com?config;header=resource
> 
> I see a problem
> 
> > 
> > Do you mean that if the URI ends with a trailing slash, then the method
> > in use is "simple configuration packet" but if the URI does not end in a
> > trailing slash then the method in use is "multiple packets aggregated in
> > a single stream"?
> 
> Yes.
> 
> > Again, this seems limited to a specific URI structure,
> > since in the XMPP example above we might do something like the following
> > for multiple aggregated packets:
> > 
> > xmpp:user@example.com?config;header=resource;aggregate=aggregated.bz2;hash=sha1hash
> 
> ";" has a particular use in sdp, this string cannot be delivered in sdp.
> 
> What about mapping the former to
> 
> xmpp://user@example.com/aggregated.bz2!sha1hash

xmpp://user@example.com means "authenticate as user@example.com". Also
XMP URIs are not "hierarchical" in the way that HTTP URIs are. So
xmpp:user@example.com/aggregated.bz2!sha1hash doesn't mean what you
think it means -- i.e., it doesn't mean "obtain the resource (file)
'aggregated.bz2' with SHA1 hash 'sha1hash' from the XMPP entity 
identified by user@example.com". XMPP URIs are structured differently
(though they still conform to RFC 3986).

> and let the application convert it to the format xmpp expect?

That's what XMPP URIs do -- we don't use them natively. But IMHO the
original URI should conform to RFC 4622.

> Probably xmpp configuration uri would be used just in conjunction with
> Jingle and never with sdp so the issue won't happen.

Right.

As long as the text is changed to say that the format you describe is
recommmended, I'm fine (because we would specify the XMPP URI format in
a different spec anyway).

Peter

-- 
Peter Saint-Andre
XMPP Standards Foundation
http://www.xmpp.org/xsf/people/stpeter.shtml


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



From avt-bounces@ietf.org Fri Jun 15 14:04: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 1HzG9T-0006cL-Oc; Fri, 15 Jun 2007 14:04:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzG9Q-0006an-Kn; Fri, 15 Jun 2007 14:04:00 -0400
Received: from nit.isi.edu ([128.9.160.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HzG9O-0000xX-6j; Fri, 15 Jun 2007 14:04:00 -0400
Received: from nit.isi.edu (loopback [127.0.0.1])
	by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id l5FI3vvJ001851; 
	Fri, 15 Jun 2007 11:03:57 -0700
Received: (from apache@localhost)
	by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id l5FI3vsO001850;
	Fri, 15 Jun 2007 11:03:57 -0700
Date: Fri, 15 Jun 2007 11:03:57 -0700
Message-Id: <200706151803.l5FI3vsO001850@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: avt@ietf.org, rfc-editor@rfc-editor.org
Subject: [AVT] RFC 4901 on Protocol Extensions for Header Compression over
	MPLS
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org


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

        
        RFC 4901

        Title:      Protocol Extensions for Header Compression 
                    over MPLS 
        Author:     J. Ash, Ed., J. Hand, Ed.,
                    A. Malis, Ed.
        Status:     Standards Track
        Date:       June 2007
        Mailbox:    gash5107@yahoo.com, 
                    jameshand@att.com, 
                    andrew.g.malis@verizon.com
        Pages:      34
        Characters: 78801
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avt-hc-over-mpls-protocol-08.txt

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

This specification defines how to use Multi-Protocol Label Switching
(MPLS) to route Header-Compressed (HC) packets over an MPLS label
switched path.  HC can significantly reduce packet-header overhead
and, in combination with MPLS, can also increases bandwidth
efficiency and processing scalability in terms of the maximum number
of simultaneous compressed flows that use HC at each router).  Here
we define how MPLS pseudowires are used to transport the HC context
and control messages between the ingress and egress MPLS label
switching routers.  This is defined for a specific set of existing HC
mechanisms that might be used, for example, to support voice over IP.
This specification also describes extension mechanisms to allow
support for future, as yet to be defined, HC protocols.  In this
specification, each HC protocol operates independently over a single
pseudowire instance, very much as it would over a single
point-to-point link.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

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

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

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

help: ways_to_get_rfcs. For example:

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

        help: ways_to_get_rfcs

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

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


The RFC Editor Team
USC/Information Sciences Institute

...



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



From avt-bounces@ietf.org Fri Jun 15 22:48: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 1HzOKx-000270-6w; Fri, 15 Jun 2007 22:48:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzOKv-00026r-S1
	for avt@ietf.org; Fri, 15 Jun 2007 22:48:25 -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 1HzOKu-0006vp-Li for avt@ietf.org; Fri, 15 Jun 2007 22:48:25 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Fri, 15 Jun 2007 22:48:24 -0400
To: Aymeric Moizard <jack@atosc.org>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-speex-01.txt
References: <E1Hxptq-000574-Cb@stiedprstage1.ietf.org>
	<1DE870BB-8980-46E8-A43D-5377BD6106CD@csperkins.org>
	<Pine.LNX.4.63.0706121744110.11297@sip2>
From: Randell Jesup <rjesup@wgate.com>
Date: Fri, 15 Jun 2007 22:48:22 -0400
In-Reply-To: <Pine.LNX.4.63.0706121744110.11297@sip2> (Aymeric Moizard's
	message of "Tue, 12 Jun 2007 18:03:23 +0200 (CEST)")
Message-ID: <ybubqfgd37t.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: 16 Jun 2007 02:48:24.0337 (UTC)
	FILETIME=[CEE9F810:01C7AFC0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: jean-marc.valin@usherbrooke.ca, Colin Perkins <csp@csperkins.org>,
	IETF 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

Aymeric Moizard <jack@atosc.org> writes:
>> Section 3.3: "Sampling rate values of 8000, 16000 or 32000 Hz MUST be
>> used. Any other sampling rates MUST NOT be used" is confusing. Better to
>> say "The sampling rate MUST be either 8000 Hz, 16000 Hz, or 32000 Hz".
>
>I agree.

The rate from rtpmap is not (necessarily) the sampling rate (witness
video); it's the rate for timestamp values, and typically (not always) will
be an integer multiple of the sampling rate or lowest common multiple of
the sampling rates, more or less.  I would dislike having the rtpmap rate
be a true codec parameter; there may be reasons for using values other than
the hardware sample rate.

Since another message indicated that the encoding could change on a
per-packet level (whether signalled in-bitstream and/or by payload value
change), it may make sense to use 32000 for the timestamp rate always.  It
is *really* problematic when the timestamp rate changes when you switch
payloads.  The only other value I can see making sense would be 8000, and
then only if you wanted to make it easier to switch between speex and
things like G.711 on the fly.

-- 
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 Sat Jun 16 10:54: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 1HzZfZ-0004DP-Dh; Sat, 16 Jun 2007 10:54:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzPmh-0002us-61
	for avt@ietf.org; Sat, 16 Jun 2007 00:21:11 -0400
Received: from 142.163.233.220.exetel.com.au ([220.233.163.142]
	helo=idefix.homelinux.org) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HzPmf-0000M8-Nf for avt@ietf.org; Sat, 16 Jun 2007 00:21:11 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by idefix.homelinux.org (Postfix) with ESMTP id E5B16200059;
	Sat, 16 Jun 2007 14:20:40 +1000 (EST)
Message-ID: <46736518.9010202@usherbrooke.ca>
Date: Sat, 16 Jun 2007 14:20:40 +1000
From: Jean-Marc Valin <jean-marc.valin@usherbrooke.ca>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: Randell Jesup <rjesup@wgate.com>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-speex-01.txt
References: <E1Hxptq-000574-Cb@stiedprstage1.ietf.org>	<1DE870BB-8980-46E8-A43D-5377BD6106CD@csperkins.org>	<Pine.LNX.4.63.0706121744110.11297@sip2>
	<ybubqfgd37t.fsf@jesup.eng.wgate.com>
In-Reply-To: <ybubqfgd37t.fsf@jesup.eng.wgate.com>
X-Enigmail-Version: 0.94.2.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
X-Mailman-Approved-At: Sat, 16 Jun 2007 10:54:28 -0400
Cc: Colin Perkins <csp@csperkins.org>, IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

> Since another message indicated that the encoding could change on a
> per-packet level (whether signalled in-bitstream and/or by payload value
> change), it may make sense to use 32000 for the timestamp rate always.  It
> is *really* problematic when the timestamp rate changes when you switch
> payloads.  The only other value I can see making sense would be 8000, and
> then only if you wanted to make it easier to switch between speex and
> things like G.711 on the fly.

Only the *bitrate* can change on a per-packet. The sampling rate has
always been fixed for a stream. In theory, a constant timestamp rate of
8000 would work even at 32 kHz because the frames have a multiple of 4
samples, but I think it's cleaner to just use the sampling rate as the
timestamp rate.

	Jean-Marc

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



From avt-bounces@ietf.org Sun Jun 17 00:42: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 1Hzmau-0002yg-N2; Sun, 17 Jun 2007 00:42:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hzmat-0002yb-8f
	for avt@ietf.org; Sun, 17 Jun 2007 00:42:31 -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 1Hzmas-0001e9-1D for avt@ietf.org; Sun, 17 Jun 2007 00:42:31 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Sun, 17 Jun 2007 00:42:29 -0400
To: Jean-Marc Valin <jean-marc.valin@usherbrooke.ca>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-speex-01.txt
References: <E1Hxptq-000574-Cb@stiedprstage1.ietf.org>
	<1DE870BB-8980-46E8-A43D-5377BD6106CD@csperkins.org>
	<Pine.LNX.4.63.0706121744110.11297@sip2>
	<ybubqfgd37t.fsf@jesup.eng.wgate.com>
	<46736518.9010202@usherbrooke.ca>
From: Randell Jesup <rjesup@wgate.com>
Date: Sun, 17 Jun 2007 00:42:28 -0400
In-Reply-To: <46736518.9010202@usherbrooke.ca> (Jean-Marc Valin's message of
	"Sat, 16 Jun 2007 14:20:40 +1000")
Message-ID: <ybuodjfp4y3.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: 17 Jun 2007 04:42:29.0680 (UTC)
	FILETIME=[E9782B00:01C7B099]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: Colin Perkins <csp@csperkins.org>, IETF 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

Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> writes:
>> Since another message indicated that the encoding could change on a
>> per-packet level (whether signalled in-bitstream and/or by payload value
>> change), it may make sense to use 32000 for the timestamp rate always.  It
>> is *really* problematic when the timestamp rate changes when you switch
>> payloads.  The only other value I can see making sense would be 8000, and
>> then only if you wanted to make it easier to switch between speex and
>> things like G.711 on the fly.
>
>Only the *bitrate* can change on a per-packet. The sampling rate has
>always been fixed for a stream. In theory, a constant timestamp rate of
>8000 would work even at 32 kHz because the frames have a multiple of 4
>samples, but I think it's cleaner to just use the sampling rate as the
>timestamp rate.

The timestamp rate *can* change on a per-packet basis if you have something
like this:

m=audio 4321 RTP/AVP 99 98 97
a=rtpmap:99 foo/8000
a=rtpmap:98 foo/16000
a=rtpmap:97 foo/32000

If you get a packet of 99, then a packet of 98, then a packet of 97, life
is *interesting*.  And note that this says nothing about the sampling
rate, which might (or might not) change.  I know this draft allows for
different timestamp rates; if there's no restriction about mixing them in
a media line, any implementation must be ready to deal with the above
scenario (per-packet payload changes).  

Of course, anyone offering more than one payload and more than one
timestamp rate (even for different codecs, like G.711 and G.722 offered
in the same line) has to be able to deal (in some manner) with timestamp
rates changes in mid-stream.  Or they have to deal with it in theory; I
doubt many deal well with it, and most (at best) work by basically punting
the problem.

Not to mention the ever-so-fun edge cases like where an RFC 2833 packet
crosses the boundary between different timestamp rates....  I have *no*
idea there, other than you have to assume that the timestamps are in the
rate of the audio codec otherwise in use at the time.  You can't really use
the timestamp rate of the RFC 2833's rtpmap line.

-- 
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 Jun 17 08:40: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 1Hzu3K-0007ty-Fo; Sun, 17 Jun 2007 08:40:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hzu3I-0007ts-IL
	for avt@ietf.org; Sun, 17 Jun 2007 08:40:20 -0400
Received: from maildialog.com ([195.159.98.119])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hzu3G-0007fv-WA
	for avt@ietf.org; Sun, 17 Jun 2007 08:40:20 -0400
Received: from cm-84.209.225.083.chello.no ([84.209.225.83] helo=[10.0.0.4])
	by maildialog.com with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.51-maildialog)
	id 1Hzu36-0003Hf-I3; Sun, 17 Jun 2007 12:40:08 +0000
Message-ID: <46752BBE.5090802@db.org>
Date: Sun, 17 Jun 2007 14:40:30 +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] I-D ACTION:draft-ietf-avt-rtp-speex-01.txt
References: <E1Hxptq-000574-Cb@stiedprstage1.ietf.org>
	<1DE870BB-8980-46E8-A43D-5377BD6106CD@csperkins.org>
In-Reply-To: <1DE870BB-8980-46E8-A43D-5377BD6106CD@csperkins.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
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,

many thanks for your comments. see inline..

Colin Perkins wrote:
> On 11 Jun 2007, at 20:50, Internet-Drafts@ietf.org wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Audio/Video Transport Working Group 
>> of the IETF.
>>
>>     Title        : RTP Payload Format for the Speex Codec
>>     Author(s)    : G. Herlein, et al.
>>     Filename    : draft-ietf-avt-rtp-speex-01.txt
>>     Pages        : 21
>>     Date        : 2007-6-11
>>     
>> 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-01.txt
> 
> This looks to be in pretty good shape, the main issue being mapping 
> parameters to the "a=fmtp:" line in SDP. Detailed comments follow:
> 
> Marker bit "to indicate that the RTP packet contains at least one 
> complete frame" is unusual for audio (although typical for video). It 
> would be better used to indicate first packet after a silent period, as 
> is usual for audio codecs.
> 

fixed in my working copy of -02

I looked in some other RFCs/I-Ds and found this:

   http://www.ietf.org/rfc/rfc4749.txt
   "The M bit MUST be set to zero in all packets."

   http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc3047-bis-04.txt
   "The M bit is set to zero."


> Section 3.3: "Sampling rate values of 8000, 16000 or 32000 Hz MUST be 
> used.  Any other sampling rates MUST NOT be used" is confusing. Better 
> to say "The sampling rate MUST be either 8000 Hz, 16000 Hz, or 32000 Hz".
> 

fixed in my working copy of -02


> Section 4.1.1: "rate" needs to be listed a required parameter, since the 
> codec supports several sampling rates.
> 

I assume that you mean "rate=sampling rate" here. Not sure how to formulate
it in the best way, but I ended up with this:


       rate: The sampling rate MUST be either 8000 Hz, 16000 Hz, or 32000
       Hz.



in other wideband codec specs I found this:


http://www.ietf.org/rfc/rfc4749.txt
"Required parameters: none"

http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc3047-bis-04.txt

   Required parameters:

       bitrate: the data rate for the audio bit stream.  This parameter
       is mandatory because the bit rate is not signaled within the
       G.722.1 bit stream.  At the standard G.722.1 bit rates, the value
       MUST be either 24000 or 32000 at 16 Khz sample rate, and 24000,
       32000 or 48000 at 32 Khz sample rate.  If using the non-standard
       bit rates, then it is RECOMMENDED that values in the range 16000
       to 48000 be used.  Non standard rates MUST have a value that is a
       multiple of 400 (this maintains octet alignment and does not then
       require (undefined) padding bits for each frame if not octet
       aligned).


> Section 5: the "a=fmtp:" attribute is for media type parameters only. If 
> you wish to define vbr, cng, and mode parameters, they must be defined 
> as media type parameters in the IANA considerations, and then mapped 
> into the "a=fmtp:" line. Section 6.2 of RFC 4749 is a good example of 
> how to do this.
> 

thanks for this comment. I have moved the definition of the fmtp parameters
to the "IANA Considerations" section, which is then referenced from the
"SDP Usage" section.


unless there are any more comments, I will publish -02 within the next
few days.



/alfred

> 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 Sun Jun 17 12:41: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 1Hzxo2-0002D0-9i; Sun, 17 Jun 2007 12:40:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hzxo0-0002Cu-99
	for avt@ietf.org; Sun, 17 Jun 2007 12:40:48 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hzxny-0002OG-Vp
	for avt@ietf.org; Sun, 17 Jun 2007 12:40:48 -0400
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:60869
	helo=[192.168.0.4])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1Hzxnv-0006oB-SZ; Sun, 17 Jun 2007 17:40:44 +0100
In-Reply-To: <p06240887c28f9648fa12@[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]>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <61DDFB8A-8EA0-4F26-9610-9FCA7FD3633C@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Working group last call: JPEG-2000 payload format
Date: Sun, 17 Jun 2007 17:40:56 +0100
To: Dave Singer <singer@apple.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: Chuck Harrison <cfharr@erols.com>,
	Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Boudani Ali <Ali.Boudani@thomson.net>,
	Le Dantec Claude <Claude.Le-Dantec@thomson.net>, 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 9 Jun 2007, at 00:30, Dave Singer wrote:
> At 9:15  -0700 6/06/07, Chuck Harrison wrote:
>> Suppose
>>
>> 1. A compliant J2K receiver MUST accept 90kHz timestamps
>> 2. A compliant J2K receiver MAY accept other timestamp rates
>> 3. A compliant J2K sender SHOULD transmit 90kHz timestamps
>> 4. The RFC warns that senders violating the SHOULD of item 3
>>     risk interoperability problems.
>
> I think timestamp conversion tends to be a common function in an  
> RTP stack, doesn't it?  Be that as it may, it's no good allowing me  
> to send non-90KHz if I can't know it'll work -- standards are about  
> interoperability.

Right - this is the problem with allowing multiple rates.

> So I think that it should say
>
> * a 90 KHz clockrate is recommended (you could even use SHOULD be  
> used) for JPEG 2000 streams

SHOULD, I think.

> * receivers MUST be able to handle other clock rates
>
> The RFC warns that if you choose an unsuitable rate, or a rate  
> whose conversion is difficult, error-prone (e.g. to round-off  
> errors), or even unusual, you risk playability problems.

...and the offer/answer considerations section in the draft explains  
how to negotiate the desired rate, and how to interact with receivers  
that only support 90 kHz.

-- 
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 Jun 17 12:50: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 1HzxxZ-0004ot-Je; Sun, 17 Jun 2007 12:50:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzxxY-0004oo-Vl
	for avt@ietf.org; Sun, 17 Jun 2007 12:50:40 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzxxY-0004hQ-G3
	for avt@ietf.org; Sun, 17 Jun 2007 12:50:40 -0400
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:60956
	helo=[192.168.0.4])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HzxxX-0008OS-GN; Sun, 17 Jun 2007 17:50:39 +0100
In-Reply-To: <46752BBE.5090802@db.org>
References: <E1Hxptq-000574-Cb@stiedprstage1.ietf.org>
	<1DE870BB-8980-46E8-A43D-5377BD6106CD@csperkins.org>
	<46752BBE.5090802@db.org>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <553C5EF6-8426-4BAB-B6B7-33106EF40580@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-speex-01.txt
Date: Sun, 17 Jun 2007 17:50:54 +0100
To: Alfred E. Heggestad <aeh@db.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
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

Alfred,

On 17 Jun 2007, at 13:40, Alfred E. Heggestad wrote:
...
>> Marker bit "to indicate that the RTP packet contains at least one  
>> complete frame" is unusual for audio (although typical for video).  
>> It would be better used to indicate first packet after a silent  
>> period, as is usual for audio codecs.
>
> fixed in my working copy of -02
>
> I looked in some other RFCs/I-Ds and found this:
>
>   http://www.ietf.org/rfc/rfc4749.txt
>   "The M bit MUST be set to zero in all packets."
>
>   http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc3047- 
> bis-04.txt
>   "The M bit is set to zero."

The usual rules for audio are: if the codec doesn't support silence  
suppression, the marker should always be set to zero; otherwise, set  
the marker bit to one on the first packet after a silent period.

>> Section 4.1.1: "rate" needs to be listed a required parameter,  
>> since the codec supports several sampling rates.
>
> I assume that you mean "rate=sampling rate" here. Not sure how to  
> formulate
> it in the best way, but I ended up with this:
>
>
>       rate: The sampling rate MUST be either 8000 Hz, 16000 Hz, or  
> 32000
>       Hz.
>
>
>
> in other wideband codec specs I found this:
>
>
> http://www.ietf.org/rfc/rfc4749.txt
> "Required parameters: none"
>
> http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc3047-bis-04.txt
>
>   Required parameters:
>
>       bitrate: the data rate for the audio bit stream.  This parameter
>       is mandatory because the bit rate is not signaled within the
>       G.722.1 bit stream.  At the standard G.722.1 bit rates, the  
> value
>       MUST be either 24000 or 32000 at 16 Khz sample rate, and 24000,
>       32000 or 48000 at 32 Khz sample rate.  If using the non-standard
>       bit rates, then it is RECOMMENDED that values in the range 16000
>       to 48000 be used.  Non standard rates MUST have a value that  
> is a
>       multiple of 400 (this maintains octet alignment and does not  
> then
>       require (undefined) padding bits for each frame if not octet
>       aligned).

The current guidelines are in RFC 4855 section 2. You should use  
something like:

Required parameters:
	rate: RTP timestamp clock rate, which is equal to the sampling rate  
in Hz.
	The sampling rate MUST be either 8000, 16000, or 32000.

>> Section 5: the "a=fmtp:" attribute is for media type parameters  
>> only. If you wish to define vbr, cng, and mode parameters, they  
>> must be defined as media type parameters in the IANA  
>> considerations, and then mapped into the "a=fmtp:" line. Section  
>> 6.2 of RFC 4749 is a good example of how to do this.
>
> thanks for this comment. I have moved the definition of the fmtp  
> parameters
> to the "IANA Considerations" section, which is then referenced from  
> the
> "SDP Usage" section.

Not sure what you mean by this?

> unless there are any more comments, I will publish -02 within the next
> few days.

Okay - I'll re-read and comment when -02 is submitted.

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 Sun Jun 17 13:08: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 1HzyEw-0002aW-60; Sun, 17 Jun 2007 13:08:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzyEv-0002aR-2h
	for avt@ietf.org; Sun, 17 Jun 2007 13:08:37 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzyEt-0008R2-Nr
	for avt@ietf.org; Sun, 17 Jun 2007 13:08:37 -0400
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:61136
	helo=[192.168.0.4])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HzyEp-0001QH-C2; Sun, 17 Jun 2007 18:08:31 +0100
In-Reply-To: <5.1.1.9.2.20070606172828.047a43a0@pop.jp.sony.com>
References: <5.1.1.9.2.20070606172828.047a43a0@pop.jp.sony.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <417E320D-1A0C-4608-A866-E16696BB816C@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-atrac-family-08.txt 
Date: Sun, 17 Jun 2007 18:08:46 +0100
To: Mitsuyuki Hatanaka <actech@jp.sony.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
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 6 Jun 2007, at 09:45, Mitsuyuki Hatanaka wrote:
> We have submitted our revised internet draft as "draft-ietf-avt-rtp- 
> atracx-family-08.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 issue that  
> Mr.Perkins pointed out
> (refer to: http://www1.ietf.org/mail-archive/web/avt/current/ 
> msg06933.html).
> In addition, we changed some items regarding on SDP usage and  
> definition.

Thanks for submitting this update; it looks to have addressed most of  
the issues with the previous draft. There are, however, a number of  
problems remaining:

- Figures 4, 5, and 6 don't seem to be referenced from the text. You  
need to explicitly refer to the figure, by number, in the  
introduction to the appropriate section.

- Section 5.2: it's not appropriate for a payload format to prohibit  
the use of RTP padding or header extensions. The draft should  
indicate that padding is support according to RFC 3550, and header  
extensions can be used according to the rules defined by the relevant  
RTP profile (e.g. RFC 3551).

- Section 5.2: the interpretation of the marker bit needs to be  
specified. The usual rules for video are that the market bit is set  
to one of the last packet of a frame, and set to zero in all other  
packets.

In addition, the automated checker (http://tools.ietf.org/tools/ 
idnits/) finds a number of problems with the draft. We cannot submit  
drafts to the IESG for publication unless they pass the checker, so  
please correct these issues also.
http://tools.ietf.org/wg/avt/draft-ietf-avt-rtp-atrac-family/draft- 
ietf-avt-rtp-atrac-family-08.nits.txt

Regards,
-- 
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 Jun 17 13: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 1Hzynm-0007EX-Lw; Sun, 17 Jun 2007 13:44:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hzynk-0007EO-Td
	for avt@ietf.org; Sun, 17 Jun 2007 13:44:36 -0400
Received: from smtp02.lnh.mail.rcn.net ([207.172.157.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hzyni-0006Fr-Jx
	for avt@ietf.org; Sun, 17 Jun 2007 13:44:36 -0400
Received: from mr08.lnh.mail.rcn.net ([207.172.157.28])
	by smtp02.lnh.mail.rcn.net with ESMTP; 17 Jun 2007 13:44:35 -0400
Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11])
	by mr08.lnh.mail.rcn.net (MOS 3.8.3-GA) with ESMTP id IUH10344;
	Sun, 17 Jun 2007 13:44:34 -0400 (EDT)
Received: from 162-144-2.cortland.com.144.162.209.in-addr.arpa (HELO
	erols.com) ([209.162.144.2])
	by smtp01.lnh.mail.rcn.net with ESMTP; 17 Jun 2007 13:44:31 -0400
Message-ID: <46757295.C62C43BF@erols.com>
Date: Sun, 17 Jun 2007 10:42:45 -0700
From: Chuck Harrison <cfharr@erols.com>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
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>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Junkmail-Whitelist: YES (by domain whitelist at mr08.lnh.mail.rcn.net)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Boudani Ali <Ali.Boudani@thomson.net>, Dave Singer <singer@apple.com>,
	Le Dantec Claude <Claude.Le-Dantec@thomson.net>, IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org



Colin Perkins wrote:
> 
> On 9 Jun 2007, at 00:30, Dave Singer wrote:
> > At 9:15  -0700 6/06/07, Chuck Harrison wrote:
> >> Suppose
> >>
> >> 1. A compliant J2K receiver MUST accept 90kHz timestamps
> >> 2. A compliant J2K receiver MAY accept other timestamp rates
> >> 3. A compliant J2K sender SHOULD transmit 90kHz timestamps
> >> 4. The RFC warns that senders violating the SHOULD of item 3
> >>     risk interoperability problems.
> >
> > I think timestamp conversion tends to be a common function in an
> > RTP stack, doesn't it?  Be that as it may, it's no good allowing me
> > to send non-90KHz if I can't know it'll work -- standards are about
> > interoperability.
> 
> Right - this is the problem with allowing multiple rates.
> 
> > So I think that it should say
> >
> > * a 90 KHz clockrate is recommended (you could even use SHOULD be
> > used) for JPEG 2000 streams
> 
> SHOULD, I think.
> 
> > * receivers MUST be able to handle other clock rates

The trouble with a MUST like this is that it is untestable;
therefore although compliance with the RFC *in theory*
guarantees interoperability, i.e. that a receiver will be
able to handle anything you throw at it, this may not
occur in practice. Also untestable compliance MUSTs could
interfere with progressing the document to standard (is
that so, chairs?)

If we choose a small number of specific alternate clock rates,
then the MUST becomes testable. But I do not think this is
what Dave was asking for.

> >
> > The RFC warns that if you choose an unsuitable rate, or a rate
> > whose conversion is difficult, error-prone (e.g. to round-off
> > errors), or even unusual, you risk playability problems.
> 
> ...and the offer/answer considerations section in the draft explains
> how to negotiate the desired rate, and how to interact with receivers
> that only support 90 kHz.

If 90kHz capability is made a MUST at both senders and
receivers, then there is a baseline rate at which two
compliant implementations are guaranteed to interoperate.
This capability can be tested.

If a sender and receiver are able to negotiate (e.g. thru
offer/answer) an alternate rate that is more suitable to
the particular application environment, so much the better.

But I do not think Dave's original proposal -- that a sender
can choose an arbitrary rate and be guaranteed that any
compliant receiving implementation will handle it -- is
viable.

So is the drift of the proposal currently on the table as
follows?

- clockrate is considered as an SDP offer/answer parameter
- receiver MUST be capable of 90kHz
- sender MUST be capable of 90hKz 
- sender SHOULD use 90kHz
- receiver SHOULD accept other clockrates

Some guidance on possible alternate clockrates (e.g. a range
for the SHOULD) would make it more likely that interoperability
of independent implementations might occur. Any suggestions
for a range, Dave?

Cheers,
  Chuck

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



From avt-bounces@ietf.org Mon Jun 18 08:36: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 1I0GSv-0003ui-P9; Mon, 18 Jun 2007 08:36:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0GGL-0006SG-3q
	for avt@ietf.org; Mon, 18 Jun 2007 08:23:17 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0GBv-0005i2-Sg
	for avt@ietf.org; Mon, 18 Jun 2007 08:18:45 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	358572046E; Mon, 18 Jun 2007 14:18:43 +0200 (CEST)
X-AuditID: c1b4fb3e-b2038bb0000007e1-19-46767823323b
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	1E35020453; Mon, 18 Jun 2007 14:18:43 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 18 Jun 2007 14:18:42 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 18 Jun 2007 14:18:42 +0200
Message-ID: <46767822.1060308@ericsson.com>
Date: Mon, 18 Jun 2007 14:18:42 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Chuck Harrison <cfharr@erols.com>
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>
In-Reply-To: <46757295.C62C43BF@erols.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Jun 2007 12:18:42.0643 (UTC)
	FILETIME=[CF709A30:01C7B1A2]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: Boudani Ali <Ali.Boudani@thomson.net>, IETF AVT WG <avt@ietf.org>,
	Colin Perkins <csp@csperkins.org>,
	Le Dantec Claude <Claude.Le-Dantec@thomson.net>,
	Dave Singer <singer@apple.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Chuck Harrison skrev:

> So is the drift of the proposal currently on the table as
> follows?
> 
> - clockrate is considered as an SDP offer/answer parameter
> - receiver MUST be capable of 90kHz
> - sender MUST be capable of 90hKz 
> - sender SHOULD use 90kHz
> - receiver SHOULD accept other clockrates
> 

I think so. I would prefer that the last SHOULD to be a MAY. That makes 
it 90kHz is normative to support, you may support others if you have 
reasons for it. Without good reasons, I don't see the need to support 
other clockrates, thus I am in favor of only a MAY.

> Some guidance on possible alternate clockrates (e.g. a range
> for the SHOULD) would make it more likely that interoperability
> of independent implementations might occur. Any suggestions
> for a range, Dave?
> 

Yes, it is important to be clear about how one does negotiate this and 
the impact this negotiation has.

I would also include a range for possible values. The lower limit I 
would say is 1kHz. This due to that RTCP would starting to get into the 
range where the actual useful measurement resolution is affected.

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 Jun 18 16:14: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 1I0NcC-0005uj-M7; Mon, 18 Jun 2007 16:14:20 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0NFf-000718-Py; Mon, 18 Jun 2007 15:51:05 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I0NFf-0004lV-Fd; Mon, 18 Jun 2007 15:51:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 2CE352ACAC;
	Mon, 18 Jun 2007 19:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I0NEg-00088t-Lp; Mon, 18 Jun 2007 15:50: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: <E1I0NEg-00088t-Lp@stiedprstage1.ietf.org>
Date: Mon, 18 Jun 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-speex-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 the Speex Codec
	Author(s)	: G. Herlein, et al.
	Filename	: draft-ietf-avt-rtp-speex-02.txt
	Pages		: 22
	Date		: 2007-6-18
	
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-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-speex-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-speex-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-6-18135540.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2007-6-18135540.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 Jun 19 01:32:23 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 1I0WK7-0003f6-5M; Tue, 19 Jun 2007 01:32:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0WK6-0003ey-50
	for avt@ietf.org; Tue, 19 Jun 2007 01:32:14 -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 1I0WK5-0003u1-Rq for avt@ietf.org; Tue, 19 Jun 2007 01:32:14 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 19 Jun 2007 01:32:13 -0400
To: "Alfred E. Heggestad" <aeh@db.org>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-speex-01.txt
References: <E1Hxptq-000574-Cb@stiedprstage1.ietf.org>
	<1DE870BB-8980-46E8-A43D-5377BD6106CD@csperkins.org>
	<46752BBE.5090802@db.org>
From: Randell Jesup <rjesup@wgate.com>
Date: Tue, 19 Jun 2007 01:32:12 -0400
In-Reply-To: <46752BBE.5090802@db.org> (Alfred E. Heggestad's message of
	"Sun, 17 Jun 2007 14:40:30 +0200")
Message-ID: <ybutzt4ldb7.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: 19 Jun 2007 05:32:13.0545 (UTC)
	FILETIME=[30D15590:01C7B233]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: jean-marc.valin@usherbrooke.ca, Colin Perkins <csp@csperkins.org>,
	IETF 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

"Alfred E. Heggestad" <aeh@db.org> writes:
>> Section 3.3: "Sampling rate values of 8000, 16000 or 32000 Hz MUST be
>> used.  Any other sampling rates MUST NOT be used" is confusing. Better to
>> say "The sampling rate MUST be either 8000 Hz, 16000 Hz, or 32000 Hz".
>
>> Section 4.1.1: "rate" needs to be listed a required parameter, since the
>> codec supports several sampling rates.
>
>I assume that you mean "rate=sampling rate" here. Not sure how to formulate
>it in the best way, but I ended up with this:
>
>    rate: The sampling rate MUST be either 8000 Hz, 16000 Hz, or 32000 Hz.

The overloading of sample rate onto the timestamp rate for RTP for (most)
audio codecs causes some real problems with certain cases.  

Switching (in-call) between codecs with different sample rates -
overloading means that playout time is tricky to calculate, and doubly so
if there was a lost packet at the boundary.  (It also could significantly
upset jitter buffers and the like, unless you do a full reset on codec
shift.)  It may also complicate related RFCs like 2833, since 2833 is
normally intermixed with regular codecs:

m=audio 4321 RTP/AVP 98 99 100 101
a=rtpmap:98 ILBC/8000
a=rtpmap:99  G7221/16000
a=rtpmap:100 G7221/32000
a=rtpmap:101 telephone-event/8000
(a=fmtp's would be needed too)

Ok: what's the timestamp rate?  :-)  And when can it change?

Note 2833 encodes offsets and durations using timestamp values.  The
receiver *may* not be able to accurately determine the point of switching.
In some cases, the multiple switches could be missed in a burst loss (even
of 2 packets).

For example consider an application that offers and agrees to G.722.1 and
G.711 (it doesn't matter if this particular set is smart), and switches
between them based on apparent bandwidth or even based on the apparent
audio content (G.711 in quiet/silence periods, G.722.1 in
noisy/speaking/music).  You might see multiple shifts within an even fairly
short burst loss, and twice in 2 packets at the extreme.

The base problem is that timestamp in an RTP packet is both a presentation
time, and a sample time, and the rate isn't fixed (per the SDP above).
RTCP indicates current timestamp and current time, but says nothing
(directly) about rate.

It probably would have made more sense if (long ago), the timestamp rate
had been set on the media line, with a suggestion that something like the
smallest value that can (sufficiently) accurately encode the presentation
time be selected.  (Example: for 8000 and 16000, choose 16000.  For 7000
and 8000, you might need to choose 56000.)  In some cases, a rate that's
not an exact multiple of the sample rate might need to be used, to avoid
needing to use a Very Large timestamp rate.

So - What *should* an application do?  Full reset on codec rate shift,
which may imply a short gap in playout, but may let you ignore packet loss?
What about 2833/etc?  Only allow codecs with identical timestamp rates on a
single media line?  (Causes all sorts of problems if someone wants to use
(for example) G.722).

-- 
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 Jun 19 04:21: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 1I0YxS-00027z-Uk; Tue, 19 Jun 2007 04:21:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0YxR-00022w-10
	for avt@ietf.org; Tue, 19 Jun 2007 04:21:01 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0YxO-0008QF-Nj
	for avt@ietf.org; Tue, 19 Jun 2007 04:21:01 -0400
Received: from relay7.apple.com (relay7.apple.com [17.128.113.37])
	by mail-out4.apple.com (Postfix) with ESMTP id 4C62197A7A4;
	Tue, 19 Jun 2007 01:20:58 -0700 (PDT)
Received: from relay7.apple.com (unknown [127.0.0.1])
	by relay7.apple.com (Symantec Mail Security) with ESMTP id 3592C3004A; 
	Tue, 19 Jun 2007 01:20:58 -0700 (PDT)
X-AuditID: 11807125-a1d8dbb000006c02-d4-467791e9f85b
Received: from [17.202.35.52] (vpn2p006.euro.apple.com [17.66.41.132])
	by relay7.apple.com (Apple SCV relay) with ESMTP id 7F13B30041;
	Tue, 19 Jun 2007 01:20:56 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p06240843c29d41cb741b@[17.202.35.52]>
In-Reply-To: <46767822.1060308@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>
Date: Tue, 19 Jun 2007 10:19:14 +0200
To: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Chuck Harrison <cfharr@erols.com>
From: Dave Singer <singer@apple.com>
Subject: Re: [AVT] Working group last call: JPEG-2000 payload format
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: Boudani Ali <Ali.Boudani@thomson.net>, Colin Perkins <csp@csperkins.org>,
	Le Dantec Claude <Claude.Le-Dantec@thomson.net>, 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

At 14:18  +0200 18/06/07, Magnus Westerlund wrote:
>Chuck Harrison skrev:
>
>>So is the drift of the proposal currently on the table as
>>follows?
>>
>>- clockrate is considered as an SDP offer/answer parameter
>>- receiver MUST be capable of 90kHz
>>- sender MUST be capable of 90hKz - sender SHOULD use 90kHz
>>- receiver SHOULD accept other clockrates
>>
>
>I think so. I would prefer that the last SHOULD to be a MAY. That 
>makes it 90kHz is normative to support, you may support others if 
>you have reasons for it. Without good reasons, I don't see the need 
>to support other clockrates, thus I am in favor of only a MAY.

you cannot have anything other than a MUST for receivers if you want 
interoperability.  Unless I am required to use SIP and negotiate 
always.

>
>>Some guidance on possible alternate clockrates (e.g. a range
>>for the SHOULD) would make it more likely that interoperability
>>of independent implementations might occur. Any suggestions
>>for a range, Dave?
>>
>
>Yes, it is important to be clear about how one does negotiate this 
>and the impact this negotiation has.
>
>I would also include a range for possible values. The lower limit I 
>would say is 1kHz. This due to that RTCP would starting to get into 
>the range where the actual useful measurement resolution is affected.
>
>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



From avt-bounces@ietf.org Tue Jun 19 04:32: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 1I0Z8F-00043U-Fo; Tue, 19 Jun 2007 04:32:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0Z8E-00043E-BQ
	for avt@ietf.org; Tue, 19 Jun 2007 04:32:10 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0Z8D-0003fH-Er
	for avt@ietf.org; Tue, 19 Jun 2007 04:32:10 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	CF57E20784; Tue, 19 Jun 2007 10:32:08 +0200 (CEST)
X-AuditID: c1b4fb3c-afe7ebb0000007e1-2b-4677948881f4
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	B306320490; Tue, 19 Jun 2007 10:32:08 +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, 19 Jun 2007 10:32:08 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Jun 2007 10:32:07 +0200
Message-ID: <46779487.5060308@ericsson.com>
Date: Tue, 19 Jun 2007 10:32:07 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Dave Singer <singer@apple.com>
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]>
In-Reply-To: <p06240843c29d41cb741b@[17.202.35.52]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Jun 2007 08:32:07.0999 (UTC)
	FILETIME=[52D04CF0:01C7B24C]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: Chuck Harrison <cfharr@erols.com>, Boudani Ali <Ali.Boudani@thomson.net>,
	Colin Perkins <csp@csperkins.org>,
	Le Dantec Claude <Claude.Le-Dantec@thomson.net>, 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 Singer skrev:
> At 14:18  +0200 18/06/07, Magnus Westerlund wrote:
>> Chuck Harrison skrev:
>>
>>> So is the drift of the proposal currently on the table as
>>> follows?
>>>
>>> - clockrate is considered as an SDP offer/answer parameter
>>> - receiver MUST be capable of 90kHz
>>> - sender MUST be capable of 90hKz - sender SHOULD use 90kHz
>>> - receiver SHOULD accept other clockrates
>>>
>>
>> I think so. I would prefer that the last SHOULD to be a MAY. That 
>> makes it 90kHz is normative to support, you may support others if you 
>> have reasons for it. Without good reasons, I don't see the need to 
>> support other clockrates, thus I am in favor of only a MAY.
> 
> you cannot have anything other than a MUST for receivers if you want 
> interoperability.  Unless I am required to use SIP and negotiate always.
> 

Yes, either you use negotiation through SIP or other ways. Other ways 
include capability declarations from client towards RTSP servers for 
example. But sure, there are cases when you like to have this 
functionality for certain use cases. But I think it is very reasonable 
in these cases to have the specific usage requirements then to upgrade 
this requirement to a MUST. This is something that people writing 
umbrella standards can do when they need it. But the fact is that we do 
have some negotiation possibilities in most cases, except 
broadcast/multicast scenarios.

The reason I have this point of view is that you still haven't explained 
why it is important for everyone to support something else than 90kHz. 
Based on the lack of concrete motivation or complaints from the industry 
of the missing support in other video codecs, like H.264, I think this 
is a requirement of limited need. And until you provide a more 
convincing case, that this is something that really everyone needs, I 
think it is fine providing one guaranteed interoperability point (90kHz) 
and then allow others.

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 Jun 19 04:39: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 1I0ZEv-0003Iy-6b; Tue, 19 Jun 2007 04:39:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0ZEu-0003Ib-I4
	for avt@ietf.org; Tue, 19 Jun 2007 04:39:04 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0ZEt-0006xs-Or
	for avt@ietf.org; Tue, 19 Jun 2007 04:39:04 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	79A4D20818; Tue, 19 Jun 2007 10:38:45 +0200 (CEST)
X-AuditID: c1b4fb3c-ae67bbb0000007e1-c8-467796154515
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	59A342080B; Tue, 19 Jun 2007 10:38:45 +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, 19 Jun 2007 10:38:45 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Jun 2007 10:38:44 +0200
Message-ID: <46779614.2010404@ericsson.com>
Date: Tue, 19 Jun 2007 10:38:44 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Randell Jesup <rjesup@wgate.com>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-speex-01.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>
In-Reply-To: <ybutzt4ldb7.fsf@jesup.eng.wgate.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Jun 2007 08:38:44.0754 (UTC)
	FILETIME=[3F4C4F20:01C7B24D]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: Colin Perkins <csp@csperkins.org>, 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

Randell Jesup skrev:
> "Alfred E. Heggestad" <aeh@db.org> writes:
>>> Section 3.3: "Sampling rate values of 8000, 16000 or 32000 Hz MUST be
>>> used.  Any other sampling rates MUST NOT be used" is confusing. Better to
>>> say "The sampling rate MUST be either 8000 Hz, 16000 Hz, or 32000 Hz".
>>> Section 4.1.1: "rate" needs to be listed a required parameter, since the
>>> codec supports several sampling rates.
>> I assume that you mean "rate=sampling rate" here. Not sure how to formulate
>> it in the best way, but I ended up with this:
>>
>>    rate: The sampling rate MUST be either 8000 Hz, 16000 Hz, or 32000 Hz.
> 
> The overloading of sample rate onto the timestamp rate for RTP for (most)
> audio codecs causes some real problems with certain cases.  
> 
> Switching (in-call) between codecs with different sample rates -
> overloading means that playout time is tricky to calculate, and doubly so
> if there was a lost packet at the boundary.  (It also could significantly
> upset jitter buffers and the like, unless you do a full reset on codec
> shift.)  It may also complicate related RFCs like 2833, since 2833 is
> normally intermixed with regular codecs:
> 
> m=audio 4321 RTP/AVP 98 99 100 101
> a=rtpmap:98 ILBC/8000
> a=rtpmap:99  G7221/16000
> a=rtpmap:100 G7221/32000
> a=rtpmap:101 telephone-event/8000
> (a=fmtp's would be needed too)
> 
> Ok: what's the timestamp rate?  :-)  And when can it change?

For this case to have a chance to work you need three telephone-event 
lines like this:
  a=rtpmap:101 telephone-event/8000
  a=rtpmap:102 telephone-event/16000
  a=rtpmap:103 telephone-event/32000

So that the packets sent is sent at the same timestamp rate as used by 
the main codec.

> 
> Note 2833 encodes offsets and durations using timestamp values.  The
> receiver *may* not be able to accurately determine the point of switching.
> In some cases, the multiple switches could be missed in a burst loss (even
> of 2 packets).
> 
> For example consider an application that offers and agrees to G.722.1 and
> G.711 (it doesn't matter if this particular set is smart), and switches
> between them based on apparent bandwidth or even based on the apparent
> audio content (G.711 in quiet/silence periods, G.722.1 in
> noisy/speaking/music).  You might see multiple shifts within an even fairly
> short burst loss, and twice in 2 packets at the extreme.
> 
> The base problem is that timestamp in an RTP packet is both a presentation
> time, and a sample time, and the rate isn't fixed (per the SDP above).
> RTCP indicates current timestamp and current time, but says nothing
> (directly) about rate.
> 
> It probably would have made more sense if (long ago), the timestamp rate
> had been set on the media line, with a suggestion that something like the
> smallest value that can (sufficiently) accurately encode the presentation
> time be selected.  (Example: for 8000 and 16000, choose 16000.  For 7000
> and 8000, you might need to choose 56000.)  In some cases, a rate that's
> not an exact multiple of the sample rate might need to be used, to avoid
> needing to use a Very Large timestamp rate.
> 
> So - What *should* an application do?  Full reset on codec rate shift,
> which may imply a short gap in playout, but may let you ignore packet loss?
> What about 2833/etc?  Only allow codecs with identical timestamp rates on a
> single media line?  (Causes all sorts of problems if someone wants to use
> (for example) G.722).
> 

I agree that timestamp rate switching is problematic. And if you have 
the sampling rate switching capability integrated into the codec, then I 
would recommend that you actually use the highest sample rate as RTP 
timestamp rate and ensure that it always provide integer timestamp ticks 
per frame. But for 8, 16 and 32k that is not an issue. Then you include 
a separate parameter to negotiate which sampling rates that really are 
allowed. But if the case really is that you anyway is reseting the codec 
between sample rate switching I think using the timestamp rate would be 
more correct.

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 Jun 19 04:45: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 1I0ZLY-0007q5-1l; Tue, 19 Jun 2007 04:45:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0ZLW-0007q0-AL
	for avt@ietf.org; Tue, 19 Jun 2007 04:45:54 -0400
Received: from anode.atosc.org ([195.154.245.166])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0ZLT-00088y-VL
	for avt@ietf.org; Tue, 19 Jun 2007 04:45:54 -0400
Received: from anode.atosc.org (localhost.localdomain [127.0.0.1])
	by internal.atosc.org (Postfix) with ESMTP
	id 274A3FAF8; Tue, 19 Jun 2007 10:38:53 +0200 (CEST)
Received: from antisip.antisip.com (179.76.97-84.rev.gaoland.net
	[84.97.76.179]) by anode.atosc.org (Postfix) with ESMTP
	id CA992FAB9; Tue, 19 Jun 2007 10:38:52 +0200 (CEST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by antisip.antisip.com (Postfix) with ESMTP id 83F3A1FE88;
	Tue, 19 Jun 2007 10:45:45 +0200 (CEST)
X-Virus-Scanned: by hand at fauche.org
Received: from antisip.antisip.com ([127.0.0.1])
	by localhost (antisip.antisip.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id W0cbcssccqBb; Tue, 19 Jun 2007 10:45:41 +0200 (CEST)
Received: by antisip.antisip.com (Postfix, from userid 1000)
	id ABD7E1FEF8; Tue, 19 Jun 2007 10:45:41 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
	by antisip.antisip.com (Postfix) with ESMTP id A8C031FE88;
	Tue, 19 Jun 2007 10:45:41 +0200 (CEST)
Date: Tue, 19 Jun 2007 10:45:41 +0200 (CEST)
From: Aymeric Moizard <jack@atosc.org>
X-X-Sender: jack@sip2
To: Randell Jesup <rjesup@wgate.com>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-speex-01.txt
In-Reply-To: <ybutzt4ldb7.fsf@jesup.eng.wgate.com>
Message-ID: <Pine.LNX.4.63.0706191043000.28061@sip2>
References: <E1Hxptq-000574-Cb@stiedprstage1.ietf.org>
	<1DE870BB-8980-46E8-A43D-5377BD6106CD@csperkins.org>
	<46752BBE.5090802@db.org> <ybutzt4ldb7.fsf@jesup.eng.wgate.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on anode.atosc.org
X-Spam-Level: 
X-Spam-Status: No, score=0.3 required=3.0 tests=AWL,FORGED_RCVD_HELO,
	RCVD_IN_NJABL_DUL,RCVD_IN_SORBS_DUL autolearn=no version=3.0.3
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: Colin Perkins <csp@csperkins.org>, 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



On Tue, 19 Jun 2007, Randell Jesup wrote:

> The overloading of sample rate onto the timestamp rate for RTP for (most)
> audio codecs causes some real problems with certain cases.

I understand your point, but I don't think the speex draft can solve this!
right?

Aymeric MOIZARD / ANTISIP
amsip - http://www.antisip.com
osip2 - http://www.osip.org
eXosip2 - http://savannah.nongnu.org/projects/exosip/


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



From avt-bounces@ietf.org Tue Jun 19 05:16: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 1I0Zoj-0005k4-Lp; Tue, 19 Jun 2007 05:16:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0Zoi-0005jt-AG
	for avt@ietf.org; Tue, 19 Jun 2007 05:16:04 -0400
Received: from anode.atosc.org ([195.154.245.166])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0Zog-0005gA-PY
	for avt@ietf.org; Tue, 19 Jun 2007 05:16:04 -0400
Received: from anode.atosc.org (localhost.localdomain [127.0.0.1])
	by internal.atosc.org (Postfix) with ESMTP
	id 4EB55FA41; Tue, 19 Jun 2007 11:09:01 +0200 (CEST)
Received: from antisip.antisip.com (179.76.97-84.rev.gaoland.net
	[84.97.76.179]) by anode.atosc.org (Postfix) with ESMTP
	id 4BA2FFB10; Tue, 19 Jun 2007 11:08:49 +0200 (CEST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by antisip.antisip.com (Postfix) with ESMTP id DA5F51FE88;
	Tue, 19 Jun 2007 11:15:41 +0200 (CEST)
X-Virus-Scanned: by hand at fauche.org
Received: from antisip.antisip.com ([127.0.0.1])
	by localhost (antisip.antisip.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id woM3b2rSSIwW; Tue, 19 Jun 2007 11:15:37 +0200 (CEST)
Received: by antisip.antisip.com (Postfix, from userid 1000)
	id D9DB81FEF8; Tue, 19 Jun 2007 11:15:37 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
	by antisip.antisip.com (Postfix) with ESMTP id D79EE1FE88;
	Tue, 19 Jun 2007 11:15:37 +0200 (CEST)
Date: Tue, 19 Jun 2007 11:15:37 +0200 (CEST)
From: Aymeric Moizard <jack@atosc.org>
X-X-Sender: jack@sip2
To: IETF AVT WG <avt@ietf.org>
In-Reply-To: <Pine.LNX.4.63.0706191043000.28061@sip2>
Message-ID: <Pine.LNX.4.63.0706191055210.28061@sip2>
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>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on anode.atosc.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=3.0 tests=AWL,FORGED_RCVD_HELO,
	RCVD_IN_NJABL_DUL,RCVD_IN_SORBS_DUL autolearn=no version=3.0.3
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: jean-marc.valin@usherbrooke.ca
Subject: [AVT] draft-ietf-avt-rtp-speex-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


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.

Because cng has also dissapeared from section SDP usage, we should
add an example (or complete the existing ones) so that at least one
SDP example include the cvg parameter.

tks,
Aymeric MOIZARD / ANTISIP
amsip - http://www.antisip.com
osip2 - http://www.osip.org
eXosip2 - http://savannah.nongnu.org/projects/exosip/


On Tue, 19 Jun 2007, Aymeric Moizard wrote:

>
>
> On Tue, 19 Jun 2007, Randell Jesup wrote:
>
>> The overloading of sample rate onto the timestamp rate for RTP for (most)
>> audio codecs causes some real problems with certain cases.
>
> I understand your point, but I don't think the speex draft can solve this!
> right?
>
> Aymeric MOIZARD / ANTISIP
> amsip - http://www.antisip.com
> osip2 - http://www.osip.org
> eXosip2 - http://savannah.nongnu.org/projects/exosip/
>
>
> _______________________________________________
> 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 Jun 19 05:51:07 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 1I0aMU-0006lj-Uk; Tue, 19 Jun 2007 05:50:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0aMT-0006kM-Pq
	for avt@ietf.org; Tue, 19 Jun 2007 05:50:57 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0aMS-000417-Gv
	for avt@ietf.org; Tue, 19 Jun 2007 05:50:57 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:58599)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1I0aMR-0008E2-Jv; Tue, 19 Jun 2007 10:50:55 +0100
In-Reply-To: <Pine.LNX.4.63.0706191055210.28061@sip2>
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>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <DD8DDC46-4F18-4D66-939B-45C23209F855@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] draft-ietf-avt-rtp-speex-02.txt
Date: Tue, 19 Jun 2007 10:51:12 +0100
To: Aymeric Moizard <jack@atosc.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
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

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.

-- 
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 Jun 19 19:04: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 1I0mkj-0003EF-Ef; Tue, 19 Jun 2007 19:04:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0mkh-0003Db-LZ
	for avt@ietf.org; Tue, 19 Jun 2007 19:04:47 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0mkh-0007m7-A0
	for avt@ietf.org; Tue, 19 Jun 2007 19:04:47 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 19 Jun 2007 16:04:47 -0700
X-IronPort-AV: i="4.16,440,1175497200"; 
	d="scan'208"; a="168347528:sNHT54179460"
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 l5JN4k0J021496; 
	Tue, 19 Jun 2007 16:04:46 -0700
Received: from [192.168.4.177] (sjc-fluffy-vpn1.cisco.com [10.25.236.82])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with SMTP id l5JN4ktW005657;
	Tue, 19 Jun 2007 23:04:46 GMT
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <0A609728-183A-4181-B5A8-DA35BBAE09E9@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Date: Tue, 19 Jun 2007 16:03:51 -0700
To: avt@ietf.org
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3909; t=1182294286;
	x=1183158286; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fluffy@cisco.com;
	z=From:=20Cullen=20Jennings=20<fluffy@cisco.com>
	|Subject:=20Registration=20procedures=20for=20RTP=20header=20extensions
	|Sender:=20; bh=K6uLbGguI+bT0//S+4K4D9NhbfGtQpjLxTDM35MayKc=;
	b=COVDyiBf0aJu/OMhdPMXIVThR8nIXN8RXoMgPvAbyqNzzGUmhueZJ2SZmWVWKNJ05yHnuhrN
	zlQIr2wFSOBdt6jC6K3PcHfOEJPGdOPkGkrY1b6liLJML5yXwI0nmXOTsCk9Mc5OE33WDH6jxR
	yBxSseqbn+n3PQQ3bJa1cO+nI=;
Authentication-Results: sj-dkim-1; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: Stephen Casner <casner@acm.org>, Dave Singer <singer@apple.com>,
	Colin Perkins <csp@csperkins.org>
Subject: [AVT] Registration procedures for RTP header extensions
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org


In processing the draft-ietf-avt-rtp-hdrex, the topic came up of what  
sort of restriction do we want to have to the registrations process  
for  getting a new RTP header extension. There are an infinite number  
of possibilities but let me list a few common ones we could choose from:

1) First Come First Serve - this would ensure that there are no  
collisions and perhaps encourage traceability to a document that  
defines the extension but there is no requirement for traceability in  
this option. There are lots of ways to set up a FCFS system. XML  
Namespace are one, IANA allocated is another.

2) Stable Document Required - to get a code point you have to be  
willing to describe your extension in some specification published  
somewhere (does not have to be an RFC but has to be real)

3) Requires an IETF approved RFC - this would include Informational  
and Experimental RFC as well as standards track.

4) Requires an Standards Track RFC

RTP header extensions are currently defined by a 16-bit RTP-profile  
specific code, with an unspecified code point allocation procedure.  
It does not matter much for this conversation but I had (perhaps  
mistakenly) interpreted the lack of a defined policy to imply that an  
document updating the document that defined the registry was required  
to allocate a new code point.  The hdrext draft registers a single  
code point (0xbede) for a generic extension header, and uses signaled  
URNs to distinguish particular uses of that generic extension. This  
is essentially a First Come First Serve policy, based on URN names.  
What I need from the working group is some idea whether this is  
appropriate, or whether some more controlled policy is required.

Now a few things to consider about selecting this. The code point  
space we are selecting from is for all practical purposes infinite so  
there is no need to worry about it getting "used up". The reasons for  
using something more like option 4 than 1 is so that the WG gets a  
change to comment on and possible approve a extension that changes  
RTP before it get allocated a code point.  In the past, I have seen  
more than one proposed extenuation to RTP where most people involved  
with the AVT would want to say "uh, that looks like a really bad  
idea, let us help you".  Often the only reasons that vendors bother  
to even describe what they are doing is to get a code point  
allocated. There are also arguments to be made that forcing people to  
form a full standards track document to get a code point is killing  
innovation and experimentation in AVT. As an standards organization,  
part of our goal is to enable different vendors to build  
interoperable devices - at times we are pushed to define things so  
that vendors can say their product is standards compliant but others  
can not actually interoperate with the features it provides. All the  
approaches other than 1) result in some difficulty of what do  
implementors do before the code point is approved - however in  
practice, this usually (but not always) turns out not to be a big deal.

How this registry is defined is key to what level of review the WG  
gets about changes done to RTP though the header extensions  
mechanism. The options 1 to 4 above corresponds to 1) no notification  
of what is going on 2) you can at least see what is happen and send  
email which may or may not be ignored 3) low bar to easily get an  
experimental but really crazy stuff can be stopped 4) WG needs to  
agree. Clearly we can have finer nuances than this but I would like  
to get the feedback from folks on roughly what range of options they  
would find acceptable and other things that should be taken into  
consideration in selecting this.

Please send responses before the end of July 4th.

Thank you,

Cullen <with my AD hat on>

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



From avt-bounces@ietf.org Tue Jun 19 20:46:32 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 1I0oL9-0001D5-A6; Tue, 19 Jun 2007 20:46:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0oL8-0001D0-95
	for avt@ietf.org; Tue, 19 Jun 2007 20:46:30 -0400
Received: from nz-out-0506.google.com ([64.233.162.234])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0oL6-0007lB-Pf
	for avt@ietf.org; Tue, 19 Jun 2007 20:46:30 -0400
Received: by nz-out-0506.google.com with SMTP id z31so20460nzd
	for <avt@ietf.org>; Tue, 19 Jun 2007 17:46:28 -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=TMQzzB4kSellsagsKInwaW9bfWIK2gmJTWMVtQkTiayccDdnLxw22WnO+zjrOIomasblZ48lSSLV5J+xbFWkGpB+TzeEV7suRf9iyOoJr+wRJtBgzvfzM7x3WuiV+MZY8Dcwhklg12+F1BRmL4Tj55XKOvwbwTVqElic1hNZPZU=
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=B8C3iqGREONGgtt1/RS8hpVP5K2zMaUE5g5cXl/+5GMCEUOrr1wI3byBAmDc/BNOn5/ia6exRICZqyy/aMQA/WkI93yExiWnDj3Rdi3T5ScLady69GptWAUJCUJXz99REbVP0zAfUy1NRcNZrFZnG/PRs2oM/fOEH6mOR30YNUc=
Received: by 10.65.214.2 with SMTP id r2mr146891qbq.1182300388423;
	Tue, 19 Jun 2007 17:46:28 -0700 (PDT)
Received: by 10.64.149.2 with HTTP; Tue, 19 Jun 2007 17:46:28 -0700 (PDT)
Message-ID: <4bb1b4060706191746s69864f47o4205faf69e36bbfc@mail.gmail.com>
Date: Wed, 20 Jun 2007 02:46:28 +0200
From: "Tiago Junqueira" <tiago.junkeira@gmail.com>
To: avt@ietf.org
In-Reply-To: <4bb1b4060706191648t6e40cf14mc268e29af156ef43@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4bb1b4060706191648t6e40cf14mc268e29af156ef43@mail.gmail.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Subject: [AVT] Method to Measure the Queue Size for this topology
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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 have this configuration (SS-Wimax Subscriber Station and BS-Wimax
Base Station)):
 (PC1)----100mbs---(SS)----3mbs----(BS)----100mbs----(PC2)

 When i measure the RTT with the ping command from the PC1 to the PC2,
i'm measuring approximately the packet service time of the station SS
= 1/u2, and also the time of the BS when the reply comes, that can be
more or less 1/u2. The time of processing from the computers in not
significant.
  If i use iperf to send a flow of 6mbs from the PC1 to the PC2, the
Wimax queue of the SS will built up and if i run the ping command with
the same packet size, and with 1 second of interval (that is not
significant when compared to the iperf), the time of processing of the
SS=X.(1/u2) because the packet sent by ping will reach the last place
of the queue. When it return has 1/u2 additional from the BS.
  So if I divide, I'll get X, that is approximately the queue size of
the SS. Do you think that it gives a notion about the size of the
buffer of the SS?

  By the way, i didn't use thrulay, because the delay is high, maybe
because of the time synchronization between the PC1 and PC2. Is easy
to synchronize the both computers, having one as server and another
receiving the synchronization?

  kindly, and thanks for the precious help given
 Tiago Junqueira

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



From avt-bounces@ietf.org Wed Jun 20 02:39: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 1I0tqg-0001r8-CL; Wed, 20 Jun 2007 02:39:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0tqf-0001qO-7d
	for avt@ietf.org; Wed, 20 Jun 2007 02:39:25 -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 1I0tqe-0008W8-SD for avt@ietf.org; Wed, 20 Jun 2007 02:39:25 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 20 Jun 2007 02:39:24 -0400
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-speex-01.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>
	<46779614.2010404@ericsson.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Wed, 20 Jun 2007 02:39:23 -0400
Message-ID: <ybuzm2vxh7o.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: 20 Jun 2007 06:39:24.0515 (UTC)
	FILETIME=[BDE04B30:01C7B305]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: jean-marc.valin@usherbrooke.ca, Colin Perkins <csp@csperkins.org>,
	IETF 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

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

>Randell Jesup skrev:
>> "Alfred E. Heggestad" <aeh@db.org> writes:
>>>> Section 3.3: "Sampling rate values of 8000, 16000 or 32000 Hz MUST be
>>>> used.  Any other sampling rates MUST NOT be used" is confusing. Better to
>>>> say "The sampling rate MUST be either 8000 Hz, 16000 Hz, or 32000 Hz".
>>>> Section 4.1.1: "rate" needs to be listed a required parameter, since the
>>>> codec supports several sampling rates.
>>> I assume that you mean "rate=sampling rate" here. Not sure how to formulate
>>> it in the best way, but I ended up with this:
>>>
>>>    rate: The sampling rate MUST be either 8000 Hz, 16000 Hz, or 32000 Hz.
>> The overloading of sample rate onto the timestamp rate for RTP for (most)
>> audio codecs causes some real problems with certain cases.  Switching
>> (in-call) between codecs with different sample rates -
>> overloading means that playout time is tricky to calculate, and doubly so
>> if there was a lost packet at the boundary.  (It also could significantly
>> upset jitter buffers and the like, unless you do a full reset on codec
>> shift.)  It may also complicate related RFCs like 2833, since 2833 is
>> normally intermixed with regular codecs:
>> m=audio 4321 RTP/AVP 98 99 100 101
>> a=rtpmap:98 ILBC/8000
>> a=rtpmap:99  G7221/16000
>> a=rtpmap:100 G7221/32000
>> a=rtpmap:101 telephone-event/8000
>> (a=fmtp's would be needed too)
>> Ok: what's the timestamp rate?  :-)  And when can it change?
>
>For this case to have a chance to work you need three telephone-event lines
>like this:
>  a=rtpmap:101 telephone-event/8000
>  a=rtpmap:102 telephone-event/16000
>  a=rtpmap:103 telephone-event/32000
>
>So that the packets sent is sent at the same timestamp rate as used by the
>main codec.

So long as none of the events span a timestamp rate change...

I have a strong suspicion that including the above is likely to cause
compatibility problems in practice (in addition to being lengthy, plus the
related fmtp lines, and so adding to the overall SIP/UDP problem).

Perhaps the real issue here comes down to a media stream is really a form
of multiplexed channel.  Some payload "switches" are real switches, others
are just passing additional streams of related data (like 2833 DTMF data).
There are no limits on when payloads can switch, or on overlap between
different payloads.  You *could* create a stream with 10 G.711 payloads,
with all 10 arriving at all times, and each one being a different language.
This might even be useful for RTSP, IPTV, etc.

Now in practice devices won't overlap or even switch often, at least for
VoIP devices, with rare exceptions like 2833.  Switches are usually to
respond to network (or processor) impairments, quality, etc.  The probably
works moderately well today in narrowband VoIP devices.  Mixing wideband
(G.722/etc) into the mix really does confuse things if the device doesn't
pick one at call setup and stick with it (or others of the same timestamp
rate).

Either we need to provide guidance on how to handle timestamp shifts, or
we need to move away from them (tough), or we need to move away from
timestamp rate == sample rate.  (Tough, but will help us in the long run.)

>> It probably would have made more sense if (long ago), the timestamp rate
>> had been set on the media line, with a suggestion that something like the
>> smallest value that can (sufficiently) accurately encode the presentation
>> time be selected.  (Example: for 8000 and 16000, choose 16000.  For 7000
>> and 8000, you might need to choose 56000.)  In some cases, a rate that's
>> not an exact multiple of the sample rate might need to be used, to avoid
>> needing to use a Very Large timestamp rate.
>> So - What *should* an application do?  Full reset on codec rate shift,
>> which may imply a short gap in playout, but may let you ignore packet loss?
>> What about 2833/etc?  Only allow codecs with identical timestamp rates on a
>> single media line?  (Causes all sorts of problems if someone wants to use
>> (for example) G.722).
>>
>
>I agree that timestamp rate switching is problematic. And if you have the
>sampling rate switching capability integrated into the codec, then I would
>recommend that you actually use the highest sample rate as RTP timestamp
>rate and ensure that it always provide integer timestamp ticks per
>frame. But for 8, 16 and 32k that is not an issue. Then you include a
>separate parameter to negotiate which sampling rates that really are
>allowed. But if the case really is that you anyway is reseting the codec
>between sample rate switching I think using the timestamp rate would be
>more correct.

You can only use the "highest" timestamp rate if the RFC for that encoding
allows it.  As an example, the Speex draft that started this does not allow
that.

Note: by "codec rate shift" I was planning to refer to the general case of
"shift from codec with sample rate N to codec with sample rate M", whether
the two codecs are the same or not.  For example, G.711 to G.722.1.

Full reset is something to avoid if possible, since users of VoIP want to
switch codecs on the fly in mid-call based on network conditions, etc.  You
want to be able to (fairly) seamlessly have a call be G.711 up to 1999ms,
and G.722.1 starting at 2000ms, if possible, and play with little or no gap
or artifacts.  The user might have just pressed a DTMF button before this
happened, and still be holding it down.

-- 
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 Jun 20 04:45: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 1I0voT-00065M-5q; Wed, 20 Jun 2007 04:45:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0voR-00065E-MX
	for avt@ietf.org; Wed, 20 Jun 2007 04:45:15 -0400
Received: from ug-out-1314.google.com ([66.249.92.168])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I0voQ-00028l-BA
	for avt@ietf.org; Wed, 20 Jun 2007 04:45:15 -0400
Received: by ug-out-1314.google.com with SMTP id k3so769255ugf
	for <avt@ietf.org>; Wed, 20 Jun 2007 01:45:13 -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:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=gT246wHAPnNPmysq8wsvdPt6w808fJKOGxjzU69Lirh2BlZf1Yt2TMt/wPb+dUITAf7NoQo91nTfgO713OpZSfQGmfTa5TNrWclQKNJkxdmmJTP3eD4sTqiCM8k0tb4kWnv3kUFraNV1x/e4kZ7IM6Rz5lDkXROdLx2HheI7XyM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=YTURZq22NcL+iDKm8vpJO1sNljsrQmbXxwfiID/AZEplb1+hN+7b+s3WgRaoyw+TIVScfCnZ28eChdng69YqNhM7ofNkwoIgaK7vXJj2JMcVuwZ4C82zQJaIXLx+Az2iADMi4SxmrJsMjA5WUGR8XqX1CvfegerdOMLexP3AGrE=
Received: by 10.78.140.17 with SMTP id n17mr153256hud.1182329112894;
	Wed, 20 Jun 2007 01:45:12 -0700 (PDT)
Received: by 10.78.140.19 with HTTP; Wed, 20 Jun 2007 01:45:12 -0700 (PDT)
Message-ID: <4e5a3720706200145k4f983112wd80ed7e224ae1675@mail.gmail.com>
Date: Wed, 20 Jun 2007 11:45:12 +0300
From: "Murat Artun" <artunmurat@gmail.com>
To: avt@ietf.org, sip-implementors@cs.columbia.edu
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: 
Subject: [AVT] DTMF interoperability: In-band, RFC 2833 or SIP INFO
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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 all,

I want to ask about the interoperability issues for DTMF sending.

There exist three ways for DTMF sending: In-band (I use this term
meaning in audio as a voice data), RFC 2833 (currently 4733 obsoletes,
but no change to previous procedure exists) and SIP INFO.

Among these three ways, I know that only RFC 2833 is announced in the
SDP of a VoIP application when it is ready to receive DTMF events as
RFC 2833 packets.

I have a few points to be clarified in the sense of interoperability issues:

- Is it preferred that DTMF is also sent in-band and as SIP INFO when
the remote VoIP application announces that it is ready to receive RFC
2833 packets?

- What if the remote VoIP application does not announce that it is
ready to receive RFC 2833 packets? Which method should be preferred,
In-band or SIP INFO, or both for reliability purposes?

- I have observed that sending DTMF as RFC 2833 packets is mostly
preferred considering that sending DTMF In-band requires the remote
VoIP application to perform tone detection in RTP level which requires
considerable processing overhead as RFC also states. Is there a known
issue about SIP INFO method for DTMF sending?

Thanks in advice...

-- 
M u r at  A r t u n, MSc.
   Design Engineer

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



From avt-bounces@ietf.org Wed Jun 20 05:09:32 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 1I0wBs-0004cz-GG; Wed, 20 Jun 2007 05:09:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0wBq-0004cf-DN
	for avt@ietf.org; Wed, 20 Jun 2007 05:09:26 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0wBo-00073B-Lw
	for avt@ietf.org; Wed, 20 Jun 2007 05:09:26 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	0D8F021171; Wed, 20 Jun 2007 11:09:24 +0200 (CEST)
X-AuditID: c1b4fb3e-ae831bb0000007e1-d6-4678eec3db17
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	E79E921164; Wed, 20 Jun 2007 11:09:23 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Jun 2007 11:09:23 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Jun 2007 11:09:22 +0200
Message-ID: <4678EEC2.9000702@ericsson.com>
Date: Wed, 20 Jun 2007 11:09:22 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [AVT] Registration procedures for RTP header extensions
References: <0A609728-183A-4181-B5A8-DA35BBAE09E9@cisco.com>
In-Reply-To: <0A609728-183A-4181-B5A8-DA35BBAE09E9@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Jun 2007 09:09:23.0002 (UTC)
	FILETIME=[B16471A0:01C7B31A]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Cc: Dave Singer <singer@apple.com>, Colin Perkins <csp@csperkins.org>,
	avt@ietf.org, Stephen Casner <casner@acm.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 Cullen,

Sorry, but I get confused by this message. Which issue are you discussing?

A. The policy for AVP (and by inheritance the other profiles) for the 
first 16-bits in the header extension. Which currently RFC 3551 says 
should be managed but doesn't define a policy or a registry for.

B. Header extensions signaled using the mechanism defined in 
draft-ietf-avt-rtp-hdrext. Which currently is the equivalent of FCFS and 
with the addition of a registry for keeping track of RFC defined ones.

I think you are talking about B and like to have confirmation of the WG 
be okay with this.

In the case of B my personal opinion is the following:

1. Per design using URIs as signalling names, this is impossible to 
control. The only way of fix this would be to change the identifier used 
for a mechanism into something a registration can keep track and assign. 
However that also increases the chance of borrowing a name without 
registering creating issues.

2. I think the IANA section as currently written needs to be improved it 
is not easy to understand for someone desiring to register a name in the 
URN space that it is under specification required. I think a better 
separation of what is the rule for registration within the space and the 
details needed to have the URN space itself created is needed.

I think there might be some benefit in changing the rules for the URN 
space to Expert Review and then have the Expert reviewer guidelines 
require a specification as one of the criteria for acceptance.

However, the reality is that header extensions (16-bit field) have been 
totally unmanaged and been in FCFS since day one. Only the limitation on 
single ones have prevented an explosion in the usage. So it is probably 
a great improvement to have an Expert Reviewed or specification required 
  policy on the URN space for header extensions.

Cheers

Magnus
(With his AD hat very much off)


Cullen Jennings skrev:
> 
> In processing the draft-ietf-avt-rtp-hdrex, the topic came up of what 
> sort of restriction do we want to have to the registrations process for  
> getting a new RTP header extension. There are an infinite number of 
> possibilities but let me list a few common ones we could choose from:
> 
> 1) First Come First Serve - this would ensure that there are no 
> collisions and perhaps encourage traceability to a document that defines 
> the extension but there is no requirement for traceability in this 
> option. There are lots of ways to set up a FCFS system. XML Namespace 
> are one, IANA allocated is another.
> 
> 2) Stable Document Required - to get a code point you have to be willing 
> to describe your extension in some specification published somewhere 
> (does not have to be an RFC but has to be real)
> 
> 3) Requires an IETF approved RFC - this would include Informational and 
> Experimental RFC as well as standards track.
> 
> 4) Requires an Standards Track RFC
> 
> RTP header extensions are currently defined by a 16-bit RTP-profile 
> specific code, with an unspecified code point allocation procedure. It 
> does not matter much for this conversation but I had (perhaps 
> mistakenly) interpreted the lack of a defined policy to imply that an 
> document updating the document that defined the registry was required to 
> allocate a new code point.  The hdrext draft registers a single code 
> point (0xbede) for a generic extension header, and uses signaled URNs to 
> distinguish particular uses of that generic extension. This is 
> essentially a First Come First Serve policy, based on URN names. What I 
> need from the working group is some idea whether this is appropriate, or 
> whether some more controlled policy is required.
> 
> Now a few things to consider about selecting this. The code point space 
> we are selecting from is for all practical purposes infinite so there is 
> no need to worry about it getting "used up". The reasons for using 
> something more like option 4 than 1 is so that the WG gets a change to 
> comment on and possible approve a extension that changes RTP before it 
> get allocated a code point.  In the past, I have seen more than one 
> proposed extenuation to RTP where most people involved with the AVT 
> would want to say "uh, that looks like a really bad idea, let us help 
> you".  Often the only reasons that vendors bother to even describe what 
> they are doing is to get a code point allocated. There are also 
> arguments to be made that forcing people to form a full standards track 
> document to get a code point is killing innovation and experimentation 
> in AVT. As an standards organization, part of our goal is to enable 
> different vendors to build interoperable devices - at times we are 
> pushed to define things so that vendors can say their product is 
> standards compliant but others can not actually interoperate with the 
> features it provides. All the approaches other than 1) result in some 
> difficulty of what do implementors do before the code point is approved 
> - however in practice, this usually (but not always) turns out not to be 
> a big deal.
> 
> How this registry is defined is key to what level of review the WG gets 
> about changes done to RTP though the header extensions mechanism. The 
> options 1 to 4 above corresponds to 1) no notification of what is going 
> on 2) you can at least see what is happen and send email which may or 
> may not be ignored 3) low bar to easily get an experimental but really 
> crazy stuff can be stopped 4) WG needs to agree. Clearly we can have 
> finer nuances than this but I would like to get the feedback from folks 
> on roughly what range of options they would find acceptable and other 
> things that should be taken into consideration in selecting this.
> 
> Please send responses before the end of July 4th.
> 
> Thank you,
> 
> Cullen <with my AD hat on>
> 
> _______________________________________________
> 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 Wed Jun 20 05:47: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 1I0wmY-0002PT-8U; Wed, 20 Jun 2007 05:47:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0wmW-0002PN-EI
	for avt@ietf.org; Wed, 20 Jun 2007 05:47:20 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0wmT-0007Ld-QB
	for avt@ietf.org; Wed, 20 Jun 2007 05:47:20 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	96D6E201A6; Wed, 20 Jun 2007 11:47:04 +0200 (CEST)
X-AuditID: c1b4fb3e-b2038bb0000007e1-ec-4678f7988d0a
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	7ED6E21023; Wed, 20 Jun 2007 11:47:04 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Jun 2007 11:47:04 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Jun 2007 11:47:03 +0200
Message-ID: <4678F797.3080004@ericsson.com>
Date: Wed, 20 Jun 2007 11:47:03 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>, Dave Singer <singer@apple.com>, 
	Cullen Jennings <fluffy@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Jun 2007 09:47:03.0575 (UTC)
	FILETIME=[F4CC8270:01C7B31F]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Cc: 
Subject: [AVT] Technical comments on draft-ietf-avt-rtp-hdrext-12
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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,

Sorry for not having read this in WGLC. However I think there is a 
serious error in the spec that needs to be fixed before this going further.

7.  BNF Syntax

    The syntax element 'URI-reference' is as defined in [RFC3986], except
    that only absolute URIs are permitted here.  The syntax element
    'extmap' is an attribute as defined in [RFC4566].
    Extensionattributes are not defined here, but by the specification
    that defines a specific extension name; there may be several.

      digit = "0"/"1"/"2"/"3"/"4"/"5"/"6"/"7"/"8"/"9"

      integer = 1*digit

      space = " "

      extensionname = URI-reference

      direction = "sendonly" / "recvonly" / "sendrecv" / "inactive"

      mapentry = "extmap:" integer ["/" direction]

      mapattrs = [space extensionattributes]

      extmap = mapentry space extensionname mapattrs


There are two serious issues with this. First RFC 4234 is not referenced 
to define that your using that type of BNF. Secondly and really 
seriously, the "extensionattributes" syntax is not defined. Unless one 
defines the form of it this exercise is useless as no parsers pre 
extension can handle and ignore the extension anyway.

I would propose to rewrite this section to the following:

7.  ABNF Syntax

The below syntax definition uses ABNF according to [RFC4234]. The syntax 
element 'URI' is as defined in [RFC3986]. The syntax element 'extmap' is 
an SDP attribute as defined in [RFC4566], i.e "a=" precede the extmap 
definition.

      extmap = mapentry SP extensionname mapattrs

      extensionname = URI

      URI = <Defined in RFC 3986>

      direction = "sendonly" / "recvonly" / "sendrecv" / "inactive"

      mapentry = "extmap:" 1*5DIGIT ["/" direction]

      mapattrs = *(SP extensionattribute)

      extensionattribute = non-ws-string

      non-ws-string = <Defined in RFC 4566>

      SP = <Defined in RFC 4234>

      DIGIT = <Defined in RFC 4234>

Some comments on this ABNF compared to the original one.
1. It limits the number of digits for the temporary identifier to 5, 
i.e. up to 16 bits supported if this ever is extended.

2. The extension can now be basically any string as long as it doesn't 
contain spaces. In addition there might be multiple additions with 
spaces in between them. The alternative would be to demand a space and 
then use byte-string (from rfc4566) to allow for any separators.

3. Uses RFC 4234 base syntax.

4. Uses URI rule instead of URI-Reference so that relative ones are not 
possible.


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 Jun 20 05:47: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 1I0wn3-0002v7-3F; Wed, 20 Jun 2007 05:47:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0wn1-0002um-1S
	for avt@ietf.org; Wed, 20 Jun 2007 05:47:51 -0400
Received: from smtpauth00.csee.onr.siteprotect.com ([64.26.60.144])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0wmz-0007TO-FO
	for avt@ietf.org; Wed, 20 Jun 2007 05:47:51 -0400
Received: from gauravk (unknown [221.134.154.130])
	(Authenticated sender: gkheterpal@ismartpanache.com)
	by smtpauth00.csee.onr.siteprotect.com (Postfix) with ESMTP id
	73D37758059; Wed, 20 Jun 2007 04:47:47 -0500 (CDT)
From: "Gaurav Kheterpal" <gkheterpal@ismartpanache.com>
To: "'Murat Artun'" <artunmurat@gmail.com>, <avt@ietf.org>,
	<sip-implementors@cs.columbia.edu>
Date: Wed, 20 Jun 2007 15:19:24 +0530
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.3028
In-Reply-To: <4e5a3720706200145k4f983112wd80ed7e224ae1675@mail.gmail.com>
Thread-Index: AcezF5gNcV97RcuYSSKbTIO2Rps/LwABbP/A
Message-Id: <20070620094747.73D37758059@smtpauth00.csee.onr.siteprotect.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: 
Subject: [AVT] RE: [Sip-implementors] DTMF interoperability: In-band,
	RFC 2833 or SIP INFO
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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 comments below:-

> - Is it preferred that DTMF is also sent in-band and as SIP INFO when
> the remote VoIP application announces that it is ready to receive RFC
> 2833 packets?

GK>> I believe that if you advertise RFC 2833 in SDP & it is negotiated
successfully, you should send/receive DTMF as RFC 2833. However,
theoretically speaking, nothing prohibits you from using SIP INFO or in-band
mechanisms. It's merely a waste of negotiating something that you would not
eventually use.

- What if the remote VoIP application does not announce that it is
> ready to receive RFC 2833 packets? Which method should be preferred,
> In-band or SIP INFO, or both for reliability purposes?

GK>> SIP INFO marks a textual way of sending DTMF so it provides codec
independence. Moreover, it provides transport of DTMF digits along with
signaling path as opposed to the media path.

SIP INFO was primarily introduced to support the transport of mid-call ISUP
messages which could not be mapped to any other SIP request. OTOH, it's also
believed that its "content-free framework" is the root cause to discourage
the use of SIP INFO (see draft-rosenberg-sip-info-harmful-00). So, SIP INFO
has it's share of pros & cons.

> - I have observed that sending DTMF as RFC 2833 packets is mostly
> preferred considering that sending DTMF In-band requires the remote
> VoIP application to perform tone detection in RTP level which requires
> considerable processing overhead as RFC also states. Is there a known
> issue about SIP INFO method for DTMF sending?

GK>> You are right that with in-band DTMF, you need to perform tone
detection at RTP level which isn't exactly an ideal scenario.

KPML is another mechanism for DTMF processing that you may want to explore.

>From an interoperability stand point, it's good to support at least RFC 2833
& in-band modes.

My 2 cents,
Gaurav

> -----Original Message-----
> From: sip-implementors-bounces@lists.cs.columbia.edu [mailto:sip-
> implementors-bounces@lists.cs.columbia.edu] On Behalf Of Murat Artun
> Sent: Wednesday, June 20, 2007 2:15 PM
> To: avt@ietf.org; sip-implementors@cs.columbia.edu
> Subject: [Sip-implementors] DTMF interoperability: In-band,RFC 2833 or SIP
> INFO
> 
> Hello all,
> 
> I want to ask about the interoperability issues for DTMF sending.
> 
> There exist three ways for DTMF sending: In-band (I use this term
> meaning in audio as a voice data), RFC 2833 (currently 4733 obsoletes,
> but no change to previous procedure exists) and SIP INFO.
> 
> Among these three ways, I know that only RFC 2833 is announced in the
> SDP of a VoIP application when it is ready to receive DTMF events as
> RFC 2833 packets.
> 
> I have a few points to be clarified in the sense of interoperability
> issues:
> 
> - Is it preferred that DTMF is also sent in-band and as SIP INFO when
> the remote VoIP application announces that it is ready to receive RFC
> 2833 packets?
> 
> - What if the remote VoIP application does not announce that it is
> ready to receive RFC 2833 packets? Which method should be preferred,
> In-band or SIP INFO, or both for reliability purposes?
> 
> - I have observed that sending DTMF as RFC 2833 packets is mostly
> preferred considering that sending DTMF In-band requires the remote
> VoIP application to perform tone detection in RTP level which requires
> considerable processing overhead as RFC also states. Is there a known
> issue about SIP INFO method for DTMF sending?
> 
> Thanks in advice...
> 
> --
> M u r at  A r t u n, MSc.
>    Design Engineer
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors


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



From avt-bounces@ietf.org Wed Jun 20 05:50: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 1I0wpX-0006ey-DY; Wed, 20 Jun 2007 05:50:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0wpW-0006et-IM
	for avt@ietf.org; Wed, 20 Jun 2007 05:50:26 -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 1I0wpV-00081q-30
	for avt@ietf.org; Wed, 20 Jun 2007 05:50: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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 20 Jun 2007 12:51:38 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04A70650@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Working group last call: draft-ietf-avt-avpf-ccm-07
Thread-Index: AcezIJhcq7jJrzUZSrayJm9ow4zxcA==
From: "Even, Roni" <roni.even@polycom.co.il>
To: <avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: avt-chairs@tools.ietf.org
Subject: [AVT] 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


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. =20

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
=09
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



From avt-bounces@ietf.org Wed Jun 20 05:56: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 1I0wux-0000no-Q7; Wed, 20 Jun 2007 05:56:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0wuw-0000mS-Av
	for avt@ietf.org; Wed, 20 Jun 2007 05:56: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 1I0wuu-0000XB-QA
	for avt@ietf.org; Wed, 20 Jun 2007 05:56: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: Wed, 20 Jun 2007 12:57:16 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04A70653@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: working group last call on draft-ietf-avt-topologies-04.txt
Thread-Index: AcezIWIOnTVu3oN1T0iyh1yL9usKoA==
From: "Even, Roni" <roni.even@polycom.co.il>
To: <avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: avt-chairs@tools.ietf.org
Subject: [AVT] 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

This is to announce a working group last call on the RTP Topologies.

Version 03 of the document went through last call and this one will be =
shorter

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.

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		: 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.

	Title		: RTP Topologies
	Author(s)	: M. Westerlund, S. Wenger
	Filename	: draft-ietf-avt-topologies-04.txt
	Pages		: 20
	Date		: 2007-2-23
=09
This document discucsses multi-endpoint topologies used in RTP
   based environments.  In particular, centralized topologies commonly
   employed in the video conferencing industry are mapped to the RTP
   terminology.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-topologies-04.txt
	Pages		: 20
	Date		: 2007-2-23
=09
This document discucsses multi-endpoint topologies used in RTP
   based environments.  In particular, centralized topologies commonly
   employed in the video conferencing industry are mapped to the RTP
   terminology.

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

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



From avt-bounces@ietf.org Wed Jun 20 06:05: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 1I0x45-0003eT-H9; Wed, 20 Jun 2007 06:05:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0x44-0003eO-QN
	for avt@ietf.org; Wed, 20 Jun 2007 06:05:28 -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 1I0x43-0002cK-ES
	for avt@ietf.org; Wed, 20 Jun 2007 06:05:28 -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, 20 Jun 2007 13:06:43 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04A70655@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Request for volunteer reviewers for the ccm and topologies drafts
Thread-Index: AcezIrPpQcE+k/vgQryLwgDDbK2G9A==
From: "Even, Roni" <roni.even@polycom.co.il>
To: <avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: Colin Perkins <csp@csperkins.org>, tom.taylor@rogers.com
Subject: [AVT] Request for volunteer reviewers for the ccm and topologies
	drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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,
We announced a working group last call on two documents with intention =
to publish them.

draft-ietf-avt-topologies-04

draft-ietf-avt-avpf-ccm-07

The documents were reviewed in the past and we would like to send them =
to publication before the Chicago meeting.

I am looking for volunteers for reviewing these documents.

If you are willing to review at least one of them please send me an =
email.

Any help will be appreciated.

Thanks

Roni Even


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



From avt-bounces@ietf.org Wed Jun 20 06:11: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 1I0x9o-0003p1-Jk; Wed, 20 Jun 2007 06:11:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0x9n-0003om-6c
	for avt@ietf.org; Wed, 20 Jun 2007 06:11:23 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0x9l-0003ua-N1
	for avt@ietf.org; Wed, 20 Jun 2007 06:11:23 -0400
Received: from relay5.apple.com (relay5.apple.com [17.128.113.35])
	by mail-out3.apple.com (Postfix) with ESMTP id 345A1976A92;
	Wed, 20 Jun 2007 03:11:21 -0700 (PDT)
Received: from relay5.apple.com (unknown [127.0.0.1])
	by relay5.apple.com (Symantec Mail Security) with ESMTP id 2231D29C024; 
	Wed, 20 Jun 2007 03:11:21 -0700 (PDT)
X-AuditID: 11807123-a011dbb000007da1-1d-4678fd489436
Received: from [17.202.35.52] (vpn1p048.euro.apple.com [17.66.41.58])
	by relay5.apple.com (Apple SCV relay) with ESMTP id B147130400B;
	Wed, 20 Jun 2007 03:11:19 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p06240863c29ead2032b0@[17.202.35.52]>
In-Reply-To: <4678F797.3080004@ericsson.com>
References: <4678F797.3080004@ericsson.com>
Date: Wed, 20 Jun 2007 12:10:37 +0200
To: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	IETF AVT WG <avt@ietf.org>, Cullen Jennings <fluffy@cisco.com>
From: Dave Singer <singer@apple.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Cc: 
Subject: [AVT] Re: Technical comments on draft-ietf-avt-rtp-hdrext-12
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

At 11:47  +0200 20/06/07, Magnus Westerlund wrote:
>Hi,
>
>Sorry for not having read this in WGLC. However I think there is a 
>serious error in the spec that needs to be fixed before this going 
>further.

Thank you;  I do not claim BNF expertise...

>
>7.  BNF Syntax
>
>    The syntax element 'URI-reference' is as defined in [RFC3986], except
>    that only absolute URIs are permitted here.  The syntax element
>    'extmap' is an attribute as defined in [RFC4566].
>    Extensionattributes are not defined here, but by the specification
>    that defines a specific extension name; there may be several.
>
>      digit = "0"/"1"/"2"/"3"/"4"/"5"/"6"/"7"/"8"/"9"
>
>      integer = 1*digit
>
>      space = " "
>
>      extensionname = URI-reference
>
>      direction = "sendonly" / "recvonly" / "sendrecv" / "inactive"
>
>      mapentry = "extmap:" integer ["/" direction]
>
>      mapattrs = [space extensionattributes]
>
>      extmap = mapentry space extensionname mapattrs
>
>
>There are two serious issues with this. First RFC 4234 is not 
>referenced to define that your using that type of BNF.

OK

>Secondly and really seriously, the "extensionattributes" syntax is 
>not defined.

well, it consumes everything to end of line.  we could make it 
tighter, I guess.

>Unless one defines the form of it this exercise is useless as no 
>parsers pre extension can handle and ignore the extension anyway.
>
>I would propose to rewrite this section to the following:
>
>7.  ABNF Syntax
>
>The below syntax definition uses ABNF according to [RFC4234]. The 
>syntax element 'URI' is as defined in [RFC3986]. The syntax element 
>'extmap' is an SDP attribute as defined in [RFC4566], i.e "a=" 
>precede the extmap definition.
>
>      extmap = mapentry SP extensionname mapattrs
>
>      extensionname = URI
>
>      URI = <Defined in RFC 3986>
>
>      direction = "sendonly" / "recvonly" / "sendrecv" / "inactive"
>
>      mapentry = "extmap:" 1*5DIGIT ["/" direction]
>
>      mapattrs = *(SP extensionattribute)
>
>      extensionattribute = non-ws-string
>
>      non-ws-string = <Defined in RFC 4566>
>
>      SP = <Defined in RFC 4234>
>
>      DIGIT = <Defined in RFC 4234>
>
>Some comments on this ABNF compared to the original one.
>1. It limits the number of digits for the temporary identifier to 5, 
>i.e. up to 16 bits supported if this ever is extended.
>
>2. The extension can now be basically any string as long as it 
>doesn't contain spaces. In addition there might be multiple 
>additions with spaces in between them. The alternative would be to 
>demand a space and then use byte-string (from rfc4566) to allow for 
>any separators.
>
>3. Uses RFC 4234 base syntax.
>
>4. Uses URI rule instead of URI-Reference so that relative ones are 
>not possible.
>
>
>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



From avt-bounces@ietf.org Wed Jun 20 06:11: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 1I0x9o-0003pS-UI; Wed, 20 Jun 2007 06:11:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0x9n-0003ow-Uj
	for avt@ietf.org; Wed, 20 Jun 2007 06:11:23 -0400
Received: from an-out-0708.google.com ([209.85.132.247])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0x9n-0003vR-Ig
	for avt@ietf.org; Wed, 20 Jun 2007 06:11:23 -0400
Received: by an-out-0708.google.com with SMTP id c17so26787anc
	for <avt@ietf.org>; Wed, 20 Jun 2007 03:11:23 -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:mime-version:content-type;
	b=TjhHr6DfnhKeVwp9GDxwX7a3FHZjHdx24sGRQa2xsBs0pu7sOqR2sgdisI1bclvTBVcTtO2FaY9p7/1xB7bpEdYPdDflkKGR+atv/gAPie2zOaFKbKxqOuMErDVb2+TQ3kDkFCYOcX4Jv0IXyQ3uWudElrL6vjtICUQbqKnOqA4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=X85aZr2ejbM0lqYxU1MTpg7i/k2NzUqSQ6K42FiVhR8XqLrdb8jJEG9QsXXkvFsxX8y5Z5NeWvdqGF3mjsMVhFcGo/vQ6X+GlDA4QA6B4JGmeNs8gtghskJxBtjg/C4gUbgPywxn1KXCfuoYqolsrY/kSBwn1BsdfW+chyYv3ZA=
Received: by 10.100.14.19 with SMTP id 19mr297198ann.1182334283194;
	Wed, 20 Jun 2007 03:11:23 -0700 (PDT)
Received: by 10.100.143.7 with HTTP; Wed, 20 Jun 2007 03:11:22 -0700 (PDT)
Message-ID: <ce8208420706200311t34ef554ft3f47a2e4cd638b52@mail.gmail.com>
Date: Wed, 20 Jun 2007 12:11:22 +0200
From: "Cesc Santa" <cesc.santa@gmail.com>
To: avt@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Subject: [AVT] RTP Multicast conferencing & SSRC
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-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="===============0033250619=="
Errors-To: avt-bounces@ietf.org

--===============0033250619==
Content-Type: multipart/alternative; 
	boundary="----=_Part_129575_2From avt-bounces@ietf.org Wed Jun 20 06:11: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 1I0x9o-0003p1-Jk; Wed, 20 Jun 2007 06:11:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0x9n-0003om-6c
	for avt@ietf.org; Wed, 20 Jun 2007 06:11:23 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0x9l-0003ua-N1
	for avt@ietf.org; Wed, 20 Jun 2007 06:11:23 -0400
Received: from relay5.apple.com (relay5.apple.com [17.128.113.35])
	by mail-out3.apple.com (Postfix) with ESMTP id 345A1976A92;
	Wed, 20 Jun 2007 03:11:21 -0700 (PDT)
Received: from relay5.apple.com (unknown [127.0.0.1])
	by relay5.apple.com (Symantec Mail Security) with ESMTP id 2231D29C024; 
	Wed, 20 Jun 2007 03:11:21 -0700 (PDT)
X-AuditID: 11807123-a011dbb000007da1-1d-4678fd489436
Received: from [17.202.35.52] (vpn1p048.euro.apple.com [17.66.41.58])
	by relay5.apple.com (Apple SCV relay) with ESMTP id B147130400B;
	Wed, 20 Jun 2007 03:11:19 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p06240863c29ead2032b0@[17.202.35.52]>
In-Reply-To: <4678F797.3080004@ericsson.com>
References: <4678F797.3080004@ericsson.com>
Date: Wed, 20 Jun 2007 12:10:37 +0200
To: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	IETF AVT WG <avt@ietf.org>, Cullen Jennings <fluffy@cisco.com>
From: Dave Singer <singer@apple.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Cc: 
Subject: [AVT] Re: Technical comments on draft-ietf-avt-rtp-hdrext-12
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

At 11:47  +0200 20/06/07, Magnus Westerlund wrote:
>Hi,
>
>Sorry for not having read this in WGLC. However I think there is a 
>serious error in the spec that needs to be fixed before this going 
>further.

Thank you;  I do not claim BNF expertise...

>
>7.  BNF Syntax
>
>    The syntax element 'URI-reference' is as defined in [RFC3986], except
>    that only absolute URIs are permitted here.  The syntax element
>    'extmap' is an attribute as defined in [RFC4566].
>    Extensionattributes are not defined here, but by the specification
>    that defines a specific extension name; there may be several.
>
>      digit = "0"/"1"/"2"/"3"/"4"/"5"/"6"/"7"/"8"/"9"
>
>      integer = 1*digit
>
>      space = " "
>
>      extensionname = URI-reference
>
>      direction = "sendonly" / "recvonly" / "sendrecv" / "inactive"
>
>      mapentry = "extmap:" integer ["/" direction]
>
>      mapattrs = [space extensionattributes]
>
>      extmap = mapentry space extensionname mapattrs
>
>
>There are two serious issues with this. First RFC 4234 is not 
>referenced to define that your using that type of BNF.

OK

>Secondly and really seriously, the "extensionattributes" syntax is 
>not defined.

well, it consumes everything to end of line.  we could make it 
tighter, I guess.

>Unless one defines the form of it this exercise is useless as no 
>parsers pre extension can handle and ignore the extension anyway.
>
>I would propose to rewrite this section to the following:
>
>7.  ABNF Syntax
>
>The below syntax definition uses ABNF according to [RFC4234]. The 
>syntax element 'URI' is as defined in [RFC3986]. The syntax element 
>'extmap' is an SDP attribute as defined in [RFC4566], i.e "a=" 
>precede the extmap definition.
>
>      extmap = mapentry SP extensionname mapattrs
>
>      extensionname = URI
>
>      URI = <Defined in RFC 3986>
>
>      direction = "sendonly" 0549329.1182334282725"

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

Hello,

If this is not the appropriate forum, please let me know where shall I send
this query to.

I am testing two RTP multicast conferencing implementations and I came
across a problem.

Lets say I have:
- 1 units of MCU-type-A
- 3 units of MCU-type-B
Each of these units runs on a separate PC, all connected by a multicast
network (a hub? :D ).

Now, they are statically configured to dump audio in a multicast channel.

The problem is that the 3 units of MCU-type-B they all choose the same SSRC
for their RTP streams
(they are mixers, mixing the audio from unicast SIP phones) for that
conference/mcast channel.

What happens is that the one unit of MCU-type-A gets severely confused: it
uses only the SSRC
to "mix" the received multicast streams (of course, each "multicast
channel"/conference has a
separate SSRC-list). The 3 received streams have the same SSRC (and codec),
but different sequence
numbers, so the mixer thinks that is receiving ONE stream with huuuuge
jitter and also old packets
and dropping most of the packets.

My question is: is the behavior of the MCU-type-B (same SSRC) correct?
* if yes, this means that the mixer on MCU-type-A should take into
consideration the source transport
  address when mixing multicast streams. This seems a lot of extra work
(processing power) on the mixer.
* if no, I agree with you :)

I read the RFC but it was not clear to me if such a setup
would fall into the definition of ONE "RTP Session" (and thus SSRC
uniqueness needs to be enforced)
or we'd be talking about 3 rtp sessions. It would seem to me that only
destination transport (pair)
address is considered, and this being a multicast session, it is the same
for all participants and
thus it is to be considered ONE rtp session and thus SSRC uniqueness MUST be
enforced.

I don't know if it is important, but RTCP is not supported by neither of the
MCU types ...

Regards,

Cesc

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

Hello,<br><br>If this is not the appropriate forum, please let me know where shall I send this query to.<br><br>I am testing two RTP multicast conferencing implementations and I came across a problem.<br><br>Lets say I have:
<br>- 1 units of MCU-type-A<br>- 3 units of MCU-type-B<br>Each of these units runs on a separate PC, all connected by a multicast network (a hub? :D ).<br><br>Now, they are statically configured to dump audio in a multicast channel.
<br><br>The problem is that the 3 units of MCU-type-B they all choose the same SSRC for their RTP streams<br>(they are mixers, mixing the audio from unicast SIP phones) for that conference/mcast channel.<br><br>What happens is that the one unit of MCU-type-A gets severely confused: it uses only the SSRC
<br>to &quot;mix&quot; the received multicast streams (of course, each &quot;multicast channel&quot;/conference has a <br>separate SSRC-list). The 3 received streams have the same SSRC (and codec), but different sequence<br>
numbers, so the mixer thinks that is receiving ONE stream with huuuuge jitter and also old packets<br>and dropping most of the packets.<br><br>My question is: is the behavior of the MCU-type-B (same SSRC) correct? <br>* if yes, this means that the mixer on MCU-type-A should take into consideration the source transport
<br>&nbsp; address when mixing multicast streams. This seems a lot of extra work (processing power) on the mixer.<br>* if no, I agree with you :)<br><br>I read the RFC but it was not clear to me if such a setup<br>would fall into the definition of ONE &quot;RTP Session&quot; (and thus SSRC uniqueness needs to be enforced)
<br>or we&#39;d be talking about 3 rtp sessions. It would seem to me that only destination transport (pair) <br>address is considered, and this being a multicast session, it is the same for all participants and <br>thus it is t/ "recvonly" / "sendrecv" / "inactive"
>
>      mapentry = "extmap:" 1*5DIGIT ["/" direction]
>
>      mapattrs = *(SP extensionattribute)
>
>      extensionattribute = non-ws-string
>
>      non-ws-string = <Defined in RFC 4566>
>
>      SP = <Defined in RFC 4234>
>
>      DIGIT = <Defined in RFC 4234>
>
>Some comments on this ABNF compared to the original one.
>1. It limits the number of digits for the temporary identifier to 5, 
>i.e. up to 16 bits supported if this ever is extended.
>
>2. The extension can now be basically any string as long as it 
>doesn't contain spaces. In addition there might be multiple 
>additions with spaces in between them. The alternative would be to 
>demand a space and then use byte-string (from rfc4566) to allow for 
>any separators.
>
>3. Uses RFC 4234 base syntax.
>
>4. Uses URI rule instead of URI-Reference so that relative ones are 
>not possible.
>
>
>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



From avt-bounces@ietf.org Wed Jun 20 06:11: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 1I0x9o-0003pS-UI; Wed, 20 Jun 2007 06:11:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0x9n-0003ow-Uj
	for avt@ietf.org; Wed, 20 Jun 2007 06:11:23 -0400
Received: from an-out-0708.google.com ([209.85.132.247])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0x9n-0003vR-Ig
	for avt@ietf.org; Wed, 20 Jun 2007 06:11:23 -0400
Received: by an-out-0708.google.com with SMTP id c17so26787anc
	for <avt@ietf.org>; Wed, 20 Jun 2007 03:11:23 -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:mime-version:content-type;
	b=TjhHr6DfnhKeVwp9GDxwX7a3FHZjHdx24sGRQa2xsBs0pu7sOqR2sgdisI1bclvTBVcTtO2FaY9p7/1xB7bpEdYPdDflkKGR+atv/gAPie2zOaFKbKxqOuMErDVb2+TQ3kDkFCYOcX4Jv0IXyQ3uWudElrL6vjtICUQbqKnOqA4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=X85aZr2ejbM0lqYxU1MTpg7i/k2NzUqSQ6K42FiVhR8XqLrdb8jJEG9QsXXkvFsxX8y5Z5NeWvdqGF3mjsMVhFcGo/vQ6X+GlDA4QA6B4JGmeNs8gtghskJxBtjg/C4gUbgPywxn1KXCfuoYqolsrY/kSBwn1BsdfW+chyYv3ZA=
Received: by 10.100.14.19 with SMTP id 19mr297198ann.1182334283194;
	Wed, 20 Jun 2007 03:11:23 -0700 (PDT)
Received: by 10.100.143.7 with HTTP; Wed, 20 Jun 2007 03:11:22 -0700 (PDT)
Message-ID: <ce8208420706200311t34ef554ft3f47a2e4cd638b52@mail.gmail.com>
Date: Wed, 20 Jun 2007 12:11:22 +0200
From: "Cesc Santa" <cesc.santa@gmail.com>
To: avt@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Subject: [AVT] RTP Multicast conferencing & SSRC
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-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="===============0033250619=="
Errors-To: avt-bounces@ietf.org

--===============0033250619==
Content-Type: multipart/alternative; 
	boundary="----=_Part_129575_2o be considered ONE rtp session and thus SSRC uniqueness MUST be enforced.
<br><br>I don&#39;t know if it is important, but RTCP is not supported by neither of the MCU types ... <br><br>Regards,<br><br>Cesc<br><br>

------=_Part_129575_20549329.1182334282725--


--===============0033250619==
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

--===============0033250619==--




0549329.1182334282725"

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

Hello,

If this is not the appropriate forum, please let me know where shall I send
this query to.

I am testing two RTP multicast conferencing implementations and I came
across a problem.

Lets say I have:
- 1 units of MCU-type-A
- 3 units of MCU-type-B
Each of these units runs on a separate PC, all connected by a multicast
network (a hub? :D ).

Now, they are statically configured to dump audio in a multicast channel.

The problem is that the 3 units of MCU-type-B they all choose the same SSRC
for their RTP streams
(they are mixers, mixing the audio from unicast SIP phones) for that
conference/mcast channel.

What happens is that the one unit of MCU-type-A gets severely confused: it
uses only the SSRC
to "mix" the received multicast streams (of course, each "multicast
channel"/conference has a
separate SSRC-list). The 3 received streams have the same SSRC (and codec),
but different sequence
numbers, so the mixer thinks that is receiving ONE stream with huuuuge
jitter and also old packets
and dropping most of the packets.

My question is: is the behavior of the MCU-type-B (same SSRC) correct?
* if yes, this means that the mixer on MCU-type-A should take into
consideration the source transport
  address when mixing multicast streams. This seems a lot of extra work
(processing power) on the mixer.
* if no, I agree with you :)

I read the RFC but it was not clear to me if such a setup
would fall into the definition of ONE "RTP Session" (and thus SSRC
uniqueness needs to be enforced)
or we'd be talking about 3 rtp sessions. It would seem to me that only
destination transport (pair)
address is considered, and this being a multicast session, it is the same
for all participants and
thus it is to be considered ONE rtp session and thus SSRC uniqueness MUST be
enforced.

I don't know if it is important, but RTCP is not supported by neither of the
MCU types ...

Regards,

Cesc

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

Hello,<br><br>If this is not the appropriate forum, please let me know where shall I send this query to.<br><br>I am testing two RTP multicast conferencing implementations and I came across a problem.<br><br>Lets say I have:
<br>- 1 units of MCU-type-A<br>- 3 units of MCU-type-B<br>Each of these units runs on a separate PC, all connected by a multicast network (a hub? :D ).<br><br>Now, they are statically configured to dump audio in a multicast channel.
<br><br>The problem is that the 3 units of MCU-type-B they all choose the same SSRC for their RTP streams<br>(they are mixers, mixing the audio from unicast SIP phones) for that conference/mcast channel.<br><br>What happens is that the one unit of MCU-type-A gets severely confused: it uses only the SSRC
<br>to &quot;mix&quot; the received multicast streams (of course, each &quot;multicast channel&quot;/conference has a <br>separate SSRC-list). The 3 received streams have the same SSRC (and codec), but different sequence<br>
numbers, so the mixer thinks that is receiving ONE stream with huuuuge jitter and also old packets<br>and dropping most of the packets.<br><br>My question is: is the behavior of the MCU-type-B (same SSRC) correct? <br>* if yes, this means that the mixer on MCU-type-A should take into consideration the source transport
<br>&nbsp; address when mixing multicast streams. This seems a lot of extra work (processing power) on the mixer.<br>* if no, I agree with you :)<br><br>I read the RFC but it was not clear to me if such a setup<br>would fall into the definition of ONE &quot;RTP Session&quot; (and thus SSRC uniqueness needs to be enforced)
<br>or we&#39;d be talking about 3 rtp sessions. It would seem to me that only destination transport (pair) <br>address is considered, and this being a multicast session, it is the same for all participants and <br>thus it is to be considered ONE rtp session and thus SSRC uniqueness MUST be enforced.
<br><br>I don&#39;t know if it is important, but RTCP is not supported by neither of the MCU types ... <br><br>Regards,<br><br>Cesc<br><br>

------=_Part_129575_20549329.1182334282725--


--===============0033250619==
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

--===============0033250619==--




From avt-bounces@ietf.org Wed Jun 20 06:28: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 1I0xQ2-0001kD-EQ; Wed, 20 Jun 2007 06:28:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0xQ1-0001k0-5G
	for avt@ietf.org; Wed, 20 Jun 2007 06:28:09 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0xPz-0008BS-Nz
	for avt@ietf.org; Wed, 20 Jun 2007 06:28:09 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:51294)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1I0xPz-0003nT-37; Wed, 20 Jun 2007 11:28:07 +0100
In-Reply-To: <ce8208420706200311t34ef554ft3f47a2e4cd638b52@mail.gmail.com>
References: <ce8208420706200311t34ef554ft3f47a2e4cd638b52@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <8C3230AD-1F74-43ED-A58B-D85FE4FA472C@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] RTP Multicast conferencing & SSRC
Date: Wed, 20 Jun 2007 11:28:06 +0100
To: Cesc Santa <cesc.santa@gmail.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
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 20 Jun 2007, at 11:11, Cesc Santa wrote:
> If this is not the appropriate forum, please let me know where  
> shall I send this query to.

This list is the correct place.

> I am testing two RTP multicast conferencing implementations and I  
> came across a problem.
>
> Lets say I have:
> - 1 units of MCU-type-A
> - 3 units of MCU-type-B
> Each of these units runs on a separate PC, all connected by a  
> multicast network (a hub? :D ).
>
> Now, they are statically configured to dump audio in a multicast  
> channel.
>
> The problem is that the 3 units of MCU-type-B they all choose the  
> same SSRC for their RTP streams (they are mixers, mixing the audio  
> from unicast SIP phones) for that conference/mcast channel.
>
> What happens is that the one unit of MCU-type-A gets severely  
> confused: it uses only the SSRC to "mix" the received multicast  
> streams (of course, each "multicast channel"/conference has a  
> separate SSRC-list). The 3 received streams have the same SSRC (and  
> codec), but different sequence numbers, so the mixer thinks that is  
> receiving ONE stream with huuuuge jitter and also old packets and  
> dropping most of the packets.
>
> My question is: is the behavior of the MCU-type-B (same SSRC) correct?

No - see RFC 3550 section 5.1 (the description of the SSRC).

> * if yes, this means that the mixer on MCU-type-A should take into  
> consideration the source transport address when mixing multicast  
> streams. This seems a lot of extra work (processing power) on the  
> mixer.
> * if no, I agree with you :)
>
> I read the RFC but it was not clear to me if such a setup would  
> fall into the definition of ONE "RTP Session" (and thus SSRC  
> uniqueness needs to be enforced) or we'd be talking about 3 rtp  
> sessions. It would seem to me that only destination transport  
> (pair) address is considered, and this being a multicast session,  
> it is the same for all participants and thus it is to be considered  
> ONE rtp session and thus SSRC uniqueness MUST be enforced.

Correct. It's a single RTP session, so the SSRC values must be unique.

> I don't know if it is important, but RTCP is not supported by  
> neither of the MCU types ...

It hinders the SSRC collision resolution mechanism, and makes it  
impossible to know which original sources are being mixed, amongst  
other problems.

-- 
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 Jun 20 07:08: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 1I0y30-0008LY-Oy; Wed, 20 Jun 2007 07:08:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0y2y-00089E-Am
	for avt@ietf.org; Wed, 20 Jun 2007 07:08:24 -0400
Received: from an-out-0708.google.com ([209.85.132.240])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0y2s-0001pl-Gm
	for avt@ietf.org; Wed, 20 Jun 2007 07:08:24 -0400
Received: by an-out-0708.google.com with SMTP id c17so29465anc
	for <avt@ietf.org>; Wed, 20 Jun 2007 04:08:18 -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=XG0B9jX2djV6cUvdtH0GPD7VNPJcOYrSpNf6wSBUDP7BuUKEHv8Wu57hSQAKVoMsB2UUNvprTonqVyIOpNLr/D9lJYpqFfREF7iDbfeR3pCvCn9ppuYR93JUpf5OPYaqs8H5HdfbF5Rmc9uE0zZ+ESgbKGI8/q7Z1M7CcGH0VkU=
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=Yyf7jPmOK3GrRitaV6OC8PhKUxqfHiIr3Zsc1w2hOE6I54mV8HIAux692POlX4aiJE3Tu91chpYYJF//6gYQ+ScUBraQu5/nNH311iU6A6UMjWdBPor2EAOAsN9wlcqaH1pqYu0kTFK/k5J43Ks07fPZHVg9iOOFovVXq1evpn0=
Received: by 10.100.123.9 with SMTP id v9mr280299anc.1182337698245;
	Wed, 20 Jun 2007 04:08:18 -0700 (PDT)
Received: by 10.100.143.7 with HTTP; Wed, 20 Jun 2007 04:08:18 -0700 (PDT)
Message-ID: <ce8208420706200408r57a04794pe0890b98677af1f9@mail.gmail.com>
Date: Wed, 20 Jun 2007 13:08:18 +0200
From: "Cesc Santa" <cesc.santa@gmail.com>
To: "Colin Perkins" <csp@csperkins.org>
Subject: Re: [AVT] RTP Multicast conferencing & SSRC
In-Reply-To: <8C3230AD-1F74-43ED-A58B-D85FE4FA472C@csperkins.org>
MIME-Version: 1.0
References: <ce8208420706200311t34ef554ft3f47a2e4cd638b52@mail.gmail.com>
	<8C3230AD-1F74-43ED-A58B-D85FE4FA472C@csperkins.org>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
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="===============0041640689=="
Errors-To: avt-bounces@ietf.org

--===============0041640689==
Content-Type: multipart/alternative; 
	boundary="----=_Part_130155_4626713.1182337698203"

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

Thanks!
I will notify the vendor.

Cesc

On 6/20/07, Colin Perkins <csp@csperkins.org> wrote:
>
> Hi,
>
> On 20 Jun 2007, at 11:11, Cesc Santa wrote:
> > If this is not the appropriate forum, please let me know where
> > shall I send this query to.
>
> This list is the correct place.
>
> > I am testing two RTP multicast conferencing implementations and I
> > came across a problem.
> >
> > Lets say I have:
> > - 1 units of MCU-type-A
> > - 3 units of MCU-type-B
> > Each of these units runs on a separate PC, all connected by a
> > multicast network (a hub? :D ).
> >
> > Now, they are statically configured to dump audio in a multicast
> > channel.
> >
> > The problem is that the 3 units of MCU-type-B they all choose the
> > same SSRC for their RTP streams (they are mixers, mixing the audio
> > from unicast SIP phones) for that conference/mcast channel.
> >
> > What happens is that the one unit of MCU-type-A gets severely
> > confused: it uses only the SSRC to "mix" the received multicast
> > streams (of course, each "multicast channel"/conference has a
> > separate SSRC-list). The 3 received streams have the same SSRC (and
> > codec), but different sequence numbers, so the mixer thinks that is
> > receiving ONE stream with huuuuge jitter and also old packets and
> > dropping most of the packets.
> >
> > My question is: is the behavior of the MCU-type-B (same SSRC) correct?
>
> No - see RFC 3550 section 5.1 (the description of the SSRC).
>
> > * if yes, this means that the mixer on MCU-type-A should take into
> > consideration the source transport address when mixing multicast
> > streams. This seems a lot of extra work (processing power) on the
> > mixer.
> > * if no, I agree with you :)
> >
> > I read the RFC but it was not clear to me if such a setup would
> > fall into the definition of ONE "RTP Session" (and thus SSRC
> > uniqueness needs to be enforced) or we'd be talking about 3 rtp
> > sessions. It would seem to me that only destination transport
> > (pair) address is considered, and this being a multicast session,
> > it is the same for all participants and thus it is to be considered
> > ONE rtp session and thus SSRC uniqueness MUST be enforced.
>
> Correct. It's a single RTP session, so the SSRC values must be unique.
>
> > I don't know if it is important, but RTCP is not supported by
> > neither of the MCU types ...
>
> It hinders the SSRC collision resolution mechanism, and makes it
> impossible to know which original sources are being mixed, amongst
> other problems.
>
> --
> Colin Perkins
> http://csperkins.org/
>
>
>

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

Thanks!<br>I will notify the vendor.<br><br>Cesc<br><br><div><span class="gmail_quote">On 6/20/07, <b class="gmail_sendername">Colin Perkins</b> &lt;<a href="mailto:csp@csperkins.org">csp@csperkins.org</a>&gt; wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br><br>On 20 Jun 2007, at 11:11, Cesc Santa wrote:<br>&gt; If this is not the appropriate forum, please let me know where
<br>&gt; shall I send this query to.<br><br>This list is the correct place.<br><br>&gt; I am testing two RTP multicast conferencing implementations and I<br>&gt; came across a problem.<br>&gt;<br>&gt; Lets say I have:<br>
&gt; - 1 units of MCU-type-A<br>&gt; - 3 units of MCU-type-B<br>&gt; Each of these units runs on a separate PC, all connected by a<br>&gt; multicast network (a hub? :D ).<br>&gt;<br>&gt; Now, they are statically configured to dump audio in a multicast
<br>&gt; channel.<br>&gt;<br>&gt; The problem is that the 3 units of MCU-type-B they all choose the<br>&gt; same SSRC for their RTP streams (they are mixers, mixing the audio<br>&gt; from unicast SIP phones) for that conference/mcast channel.
<br>&gt;<br>&gt; What happens is that the one unit of MCU-type-A gets severely<br>&gt; confused: it uses only the SSRC to &quot;mix&quot; the received multicast<br>&gt; streams (of course, each &quot;multicast channel&quot;/conference has a
<br>&gt; separate SSRC-list). The 3 received streams have the same SSRC (and<br>&gt; codec), but different sequence numbers, so the mixer thinks that is<br>&gt; receiving ONE stream with huuuuge jitter and also old packets and
<br>&gt; dropping most of the packets.<br>&gt;<br>&gt; My question is: is the behavior of the MCU-type-B (same SSRC) correct?<br><br>No - see RFC 3550 section 5.1 (the description of the SSRC).<br><br>&gt; * if yes, this means that the mixer on MCU-type-A should take into
<br>&gt; consideration the source transport address when mixing multicast<br>&gt; streams. This seems a lot of extra work (processing power) on the<br>&gt; mixer.<br>&gt; * if no, I agree with you :)<br>&gt;<br>&gt; I read the RFC but it was not clear to me if such a setup would
<br>&gt; fall into the definition of ONE &quot;RTP Session&quot; (and thus SSRC<br>&gt; uniqueness needs to be enforced) or we&#39;d be talking about 3 rtp<br>&gt; sessions. It would seem to me that only destination transport
<br>&gt; (pair) address is considered, and this being a multicast session,<br>&gt; it is the same for all participants and thus it is to be considered<br>&gt; ONE rtp session and thus SSRC uniqueness MUST be enforced.<br>
<br>Correct. It&#39;s a single RTP session, so the SSRC values must be unique.<br><br>&gt; I don&#39;t know if it is important, but RTCP is not supported by<br>&gt; neither of the MCU types ...<br><br>It hinders the SSRC collision resolution mechanism, and makes it
<br>impossible to know which original sources are being mixed, amongst<br>other problems.<br><br>--<br>Colin Perkins<br><a href="http://csperkins.org/">http://csperkins.org/</a><br><br><br></blockquote></div><br>

------=_Part_130155_4626713.1182337698203--


--===============0041640689==
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

--===============0041640689==--




From avt-bounces@ietf.org Wed Jun 20 08:00: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 1I0yqs-00020d-Vo; Wed, 20 Jun 2007 07:59:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0yqs-00020S-8c
	for avt@ietf.org; Wed, 20 Jun 2007 07:59:58 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0yqq-0003fh-Hg
	for avt@ietf.org; Wed, 20 Jun 2007 07:59:58 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	DB20C211B5; Wed, 20 Jun 2007 13:59:55 +0200 (CEST)
X-AuditID: c1b4fb3e-b1036bb0000007e1-42-467916bb00f5
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	C8D45207A9; Wed, 20 Jun 2007 13:59:55 +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, 20 Jun 2007 13:59:55 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Jun 2007 13:59:55 +0200
Message-ID: <467916BA.2010702@ericsson.com>
Date: Wed, 20 Jun 2007 13:59:54 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Dave Singer <singer@apple.com>
References: <4678F797.3080004@ericsson.com>
	<p06240863c29ead2032b0@[17.202.35.52]>
In-Reply-To: <p06240863c29ead2032b0@[17.202.35.52]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Jun 2007 11:59:55.0275 (UTC)
	FILETIME=[844D65B0:01C7B332]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: Cullen Jennings <fluffy@cisco.com>, IETF AVT WG <avt@ietf.org>
Subject: [AVT] Re: Technical comments on draft-ietf-avt-rtp-hdrext-12
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Dave Singer skrev:

> 
>> Secondly and really seriously, the "extensionattributes" syntax is not 
>> defined.
> 
> well, it consumes everything to end of line.  we could make it tighter, 
> I guess.
> 

No, it didn't because the label "extensionattributes" was not defined. 
It needs to be either explicitly or by an explicit import.

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 Jun 20 10:13: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 1I10wJ-0006Di-UQ; Wed, 20 Jun 2007 10:13:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I10wJ-0006DX-38
	for avt@ietf.org; Wed, 20 Jun 2007 10:13:43 -0400
Received: from mout.perfora.net ([74.208.4.194])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I10wH-0005lg-QC
	for avt@ietf.org; Wed, 20 Jun 2007 10:13:43 -0400
Received: from [71.136.175.166] (helo=TBT-Laptop.newtbt.com)
	by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis),
	id 0MKp8S-1I10wF3BuK-0002si; Wed, 20 Jun 2007 10:13:41 -0400
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 20 Jun 2007 07:10:12 -0700
To: avt@ietf.org
From: Michael A Dolan <md.1@newtbt.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <0MKp8S-1I10wF3BuK-0002si@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX1/umIYCu7OSKYOdvj8/VbjddXR3ZltcxcyaeMQ
	tEQJCmzkbSbVBEJtqdqAvBz1qlKvqOsFC2JyamcknF2OG0Wy3K
	G+WHERIFB1JTjeZ7cwnGQ==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Subject: [AVT] draft-ietf-avt-hdrext-12
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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, Tom and all-

I'm not sure where this work stands since Tom's recommendation in 
March, but I notice a few people have commented lately so thought I'd 
speak up....

I discovered a deployed system the other day that did the header 
extensions in a very similar (but not identical) way.  In this other 
system, the "defined by profile" field has several defined values and 
the multi-sub-field technique is present, using an ID and LEN 
fields.  But these fields are a different size (not 4 and 4 
bits).  It was basically the same design, though.

I need to get this other practice documented for use by another 
standards body.  I'd prefer to document it in IETF rather than elsewhere.

Because the design is so similar, I was thinking one approach would 
be to augment this ID?  I realize this is very late in what's been a 
long process for this ID (with my apologies to Dave).  Nevertheless, 
finding a deployed system so similar, it might be worth capturing 
them both in the same document with a clear way to discriminate them 
(which would be more difficult to explain if they were in separate documents).

I'm prepared to promptly contribute a proposed revision to this ID if 
folks are open to the idea.

Comments?

Best regards,

         Mike


-----------------------------------
Michael DOLAN
Television Broadcast Technology, Inc. (TBT)
PO Box 190, Del Mar, CA 92014 USA


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



From avt-bounces@ietf.org Wed Jun 20 14:12: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 1I14el-0000aN-1Z; Wed, 20 Jun 2007 14:11:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I14ej-0000Uo-Jf
	for avt@ietf.org; Wed, 20 Jun 2007 14:11:49 -0400
Received: from atlas.jabber.org ([208.245.212.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I14ee-0004Nj-Ai
	for avt@ietf.org; Wed, 20 Jun 2007 14:11:49 -0400
Received: by atlas.jabber.org (Postfix, from userid 1005)
	id 7FFA221B349; Wed, 20 Jun 2007 13:17:08 -0500 (CDT)
Date: Wed, 20 Jun 2007 13:17:08 -0500
From: Peter Saint-Andre <stpeter@jabber.org>
To: Murat Artun <artunmurat@gmail.com>
Subject: Re: [AVT] DTMF interoperability: In-band, RFC 2833 or SIP INFO
Message-ID: <20070620181708.GA24569@jabber.org>
References: <4e5a3720706200145k4f983112wd80ed7e224ae1675@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4e5a3720706200145k4f983112wd80ed7e224ae1675@mail.gmail.com>
Jabber-ID: stpeter@jabber.org
User-Agent: Mutt/1.5.6+20040907i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: sip-implementors@cs.columbia.edu, 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 Wed, Jun 20, 2007 at 11:45:12AM +0300, Murat Artun wrote:

> I want to ask about the interoperability issues for DTMF sending.
> 
> There exist three ways for DTMF sending: In-band (I use this term
> meaning in audio as a voice data), RFC 2833 (currently 4733 obsoletes,
> but no change to previous procedure exists) and SIP INFO.

FWIW, in Jingle we use an XML format for DTMF information:

http://www.xmpp.org/extensions/xep-0181.html

However, use of RFC 2833 (RFC 4733) can be negotiated.

The XML format should be interoperable (through a gateway or other
transformational agent) with the SIP INFO method. We'll document that
when we write the forthcoming specification on SIP-Jingle interworking.

Peter

-- 
Peter Saint-Andre
XMPP Standards Foundation
http://www.xmpp.org/xsf/people/stpeter.shtml


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



From avt-bounces@ietf.org Wed Jun 20 16:54: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 1I17CT-0005jx-B5; Wed, 20 Jun 2007 16:54:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I17CR-0005jq-HZ
	for avt@ietf.org; Wed, 20 Jun 2007 16:54:47 -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 1I17CR-000672-6z for avt@ietf.org; Wed, 20 Jun 2007 16:54:47 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-3.cisco.com with ESMTP; 20 Jun 2007 13:54:46 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAAoxeUarR7PD/2dsb2JhbAA
X-IronPort-AV: i="4.16,444,1175497200"; 
	d="scan'208"; a="496221836:sNHT651327248"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l5KKskfn008208; 
	Wed, 20 Jun 2007 13:54:46 -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 l5KKsj06021249;
	Wed, 20 Jun 2007 20:54:45 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Jun 2007 13:54:44 -0700
Received: from [10.32.254.210] ([10.32.254.210]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Jun 2007 13:54:44 -0700
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A5148FAE-9197-4824-87C4-EF54767552F3@cisco.com>
Content-Transfer-Encoding: 7bit
From: David McGrew <mcgrew@cisco.com>
Date: Wed, 20 Jun 2007 13:54:49 -0700
To: Colin Perkins <csp@csperkins.org>, Roni Even <roni.even@polycom.co.il>,
	tom.taylor@rogers.com, AVT <avt@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 20 Jun 2007 20:54:44.0553 (UTC)
	FILETIME=[3B00A390:01C7B37D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1704; t=1182372886;
	x=1183236886; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mcgrew@cisco.com;
	z=From:=20David=20McGrew=20<mcgrew@cisco.com>
	|Subject:=20TLS-SRTP=20internet=20draft=20as=20a=20WG=20item=20in=20AVT
	|Sender:=20; bh=G1Xtzl0X2S/CQfKu/+MqzZJv+o6DZxK6Jm1ratJireU=;
	b=ZYYW1p0ZfPTOQ5m5epXaAwSEZ6r9j94Aj8oqWIIrzbho87lU+zTdZBHgjyGdEzwS4/k2ONrw
	MDmg5aAcmsVjCK20hJkpEFQ1ur/KHheXt+HSfgIVzNCbCjZTIe4h8Yaj;
Authentication-Results: sj-dkim-3; header.From=mcgrew@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: Cullen Jennings <fluffy@cisco.com>, Dan Wing <dwing@cisco.com>
Subject: [AVT] TLS-SRTP internet draft as a WG item in AVT
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi Colin, Roni, and Tom,

I would like to ask that draft-mcgrew-tls-srtp be taken up as a  
working group action item in AVT, as part the plan for carrying  
forward the RTPSEC work (as per Cullen's email of May 11 to the  
rtpsec list).   I would like to continue on as an author of this  
work, and Eric as agreed to do the same.  There are a small number of  
minor open issues which I expect can be wrapped up quickly:

1.  The draft needs to be clarified so that, in the Symmetric RTP  
case, only one handshake is needed.

2.  Section 3.6.2.1 needs to be resolved to either decide on a  
"symmetry breaking" rule or not.  It may be desirable to have such a  
rule to handle cases in which the signaling system can't tell a  
device which should act as client and which should act as server.    
This would allow opportunistic probing, i.e. a TLS-SRTP  
implementation could attempt to find out whether another RTP  
implementation supports TLS-SRTP, absent any help from signaling.

3.  The "single DTLS session per SRTP session" issue needs to be  
decided, and Appendix A should then be removed from the draft.

4.  It should be decided to use, or not to use the "TLS Extractor",  
and Section 3.3 should be rewritten accordingly.

5.  The duplicate list of srtp profiles needs to be eliminated.

Best regards,

David

--

p.s. - here's the AVT-specific part of Cullen note, so that you don't  
need to dig it out of your mailbox: "AVT - Describe how DTLS is used  
to key SRTP and how SRTP is used in combination with DTLS. This  
includes the issues of multiplexing DTLS and SRTP on one port. draft- 
mcgrew-tls-srtp will be the starting draft for this."

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



From avt-bounces@ietf.org Wed Jun 20 17:13: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 1I17Ui-0008NO-Jp; Wed, 20 Jun 2007 17:13:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I17Uh-0008I1-13
	for avt@ietf.org; Wed, 20 Jun 2007 17:13:39 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I17Ug-0002lQ-KM
	for avt@ietf.org; Wed, 20 Jun 2007 17:13:39 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 20 Jun 2007 17:13:38 -0400
X-IronPort-AV: i="4.16,444,1175486400"; 
	d="scan'208"; a="124172512:sNHT58800392"
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 l5KLDc9s020736; 
	Wed, 20 Jun 2007 17:13:38 -0400
Received: from [192.168.1.2] (rtp-vpn2-746.cisco.com [10.82.242.234])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5KLDbBe001457; 
	Wed, 20 Jun 2007 21:13:37 GMT
In-Reply-To: <4678EEC2.9000702@ericsson.com>
References: <0A609728-183A-4181-B5A8-DA35BBAE09E9@cisco.com>
	<4678EEC2.9000702@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <0B0FC93B-8BF6-4CB3-AE4E-CB83C26AFD12@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [AVT] Registration procedures for RTP header extensions
Date: Wed, 20 Jun 2007 14:12:42 -0700
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7322; t=1182374018;
	x=1183238018; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fluffy@cisco.com;
	z=From:=20Cullen=20Jennings=20<fluffy@cisco.com>
	|Subject:=20Re=3A=20[AVT]=20Registration=20procedures=20for=20RTP=20heade
	r=20extensions |Sender:=20
	|To:=20Magnus=20Westerlund=20<magnus.westerlund@ericsson.com>;
	bh=rkplzuzPQ3K5G/L+NxPehSDg7dwictXhV9xNnn3Gh0Y=;
	b=TYHpqdRaZ17P/txrvGLpQ865pWfiWTZy62cv4cpGUSiBL+tfFMO8JuARgLOGLXd8Patepro/
	MU+0yTbaR3km+rHZSyB1hOF/WFdLidOlltLN+f6mQIL80WhxWibJnzMJ;
Authentication-Results: rtp-dkim-2; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f
Cc: Dave Singer <singer@apple.com>, Colin Perkins <csp@csperkins.org>,
	avt@ietf.org, Stephen Casner <casner@acm.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 Jun 20, 2007, at 2:09 AM, Magnus Westerlund wrote:

> Hi Cullen,
>
> Sorry, but I get confused by this message. Which issue are you  
> discussing?
>
> A. The policy for AVP (and by inheritance the other profiles) for  
> the first 16-bits in the header extension. Which currently RFC 3551  
> says should be managed but doesn't define a policy or a registry for.
>
> B. Header extensions signaled using the mechanism defined in draft- 
> ietf-avt-rtp-hdrext. Which currently is the equivalent of FCFS and  
> with the addition of a registry for keeping track of RFC defined ones.
>
> I think you are talking about B and like to have confirmation of  
> the WG be okay with this.
Yes - I am talking about B but A is effectively being replaced by B  
for all practical purposes so they are closely related.

>
> In the case of B my personal opinion is the following:
>
> 1. Per design using URIs as signalling names, this is impossible to  
> control. The only way of fix this would be to change the identifier  
> used for a mechanism into something a registration can keep track  
> and assign. However that also increases the chance of borrowing a  
> name without registering creating issues.

I was not really asking about if we should use URI or not, I was  
looking for opinion on what level of control the WG thought they  
should have from 1 to 4 - once we have a better idea of that, we can  
propose an appropriate mechanism. Thoughts on this?


>
> 2. I think the IANA section as currently written needs to be  
> improved it is not easy to understand for someone desiring to  
> register a name in the URN space that it is under specification  
> required. I think a better separation of what is the rule for  
> registration within the space and the details needed to have the  
> URN space itself created is needed.
>
> I think there might be some benefit in changing the rules for the  
> URN space to Expert Review and then have the Expert reviewer  
> guidelines require a specification as one of the criteria for  
> acceptance.
>
> However, the reality is that header extensions (16-bit field) have  
> been totally unmanaged and been in FCFS since day one.

interesting - which extension numbers are defined?

> Only the limitation on single ones have prevented an explosion in  
> the usage. So it is probably a great improvement to have an Expert  
> Reviewed or specification required  policy on the URN space for  
> header extensions.
>
> Cheers
>
> Magnus
> (With his AD hat very much off)
>
>
> Cullen Jennings skrev:
>> In processing the draft-ietf-avt-rtp-hdrex, the topic came up of  
>> what sort of restriction do we want to have to the registrations  
>> process for  getting a new RTP header extension. There are an  
>> infinite number of possibilities but let me list a few common ones  
>> we could choose from:
>> 1) First Come First Serve - this would ensure that there are no  
>> collisions and perhaps encourage traceability to a document that  
>> defines the extension but there is no requirement for traceability  
>> in this option. There are lots of ways to set up a FCFS system.  
>> XML Namespace are one, IANA allocated is another.
>> 2) Stable Document Required - to get a code point you have to be  
>> willing to describe your extension in some specification published  
>> somewhere (does not have to be an RFC but has to be real)
>> 3) Requires an IETF approved RFC - this would include  
>> Informational and Experimental RFC as well as standards track.
>> 4) Requires an Standards Track RFC
>> RTP header extensions are currently defined by a 16-bit RTP- 
>> profile specific code, with an unspecified code point allocation  
>> procedure. It does not matter much for this conversation but I had  
>> (perhaps mistakenly) interpreted the lack of a defined policy to  
>> imply that an document updating the document that defined the  
>> registry was required to allocate a new code point.  The hdrext  
>> draft registers a single code point (0xbede) for a generic  
>> extension header, and uses signaled URNs to distinguish particular  
>> uses of that generic extension. This is essentially a First Come  
>> First Serve policy, based on URN names. What I need from the  
>> working group is some idea whether this is appropriate, or whether  
>> some more controlled policy is required.
>> Now a few things to consider about selecting this. The code point  
>> space we are selecting from is for all practical purposes infinite  
>> so there is no need to worry about it getting "used up". The  
>> reasons for using something more like option 4 than 1 is so that  
>> the WG gets a change to comment on and possible approve a  
>> extension that changes RTP before it get allocated a code point.   
>> In the past, I have seen more than one proposed extenuation to RTP  
>> where most people involved with the AVT would want to say "uh,  
>> that looks like a really bad idea, let us help you".  Often the  
>> only reasons that vendors bother to even describe what they are  
>> doing is to get a code point allocated. There are also arguments  
>> to be made that forcing people to form a full standards track  
>> document to get a code point is killing innovation and  
>> experimentation in AVT. As an standards organization, part of our  
>> goal is to enable different vendors to build interoperable devices  
>> - at times we are pushed to define things so that vendors can say  
>> their product is standards compliant but others can not actually  
>> interoperate with the features it provides. All the approaches  
>> other than 1) result in some difficulty of what do implementors do  
>> before the code point is approved - however in practice, this  
>> usually (but not always) turns out not to be a big deal.
>> How this registry is defined is key to what level of review the WG  
>> gets about changes done to RTP though the header extensions  
>> mechanism. The options 1 to 4 above corresponds to 1) no  
>> notification of what is going on 2) you can at least see what is  
>> happen and send email which may or may not be ignored 3) low bar  
>> to easily get an experimental but really crazy stuff can be  
>> stopped 4) WG needs to agree. Clearly we can have finer nuances  
>> than this but I would like to get the feedback from folks on  
>> roughly what range of options they would find acceptable and other  
>> things that should be taken into consideration in selecting this.
>> Please send responses before the end of July 4th.
>> Thank you,
>> Cullen <with my AD hat on>
>> _______________________________________________
>> 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 Wed Jun 20 18:50: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 1I1905-0007aq-4r; Wed, 20 Jun 2007 18:50:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I18zy-0007CJ-SS; Wed, 20 Jun 2007 18:50:02 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I18zy-0005Ha-H1; Wed, 20 Jun 2007 18:50:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 63ED626E95;
	Wed, 20 Jun 2007 22:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I18zy-0005i1-5x; Wed, 20 Jun 2007 18:50: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: <E1I18zy-0005i1-5x@stiedprstage1.ietf.org>
Date: Wed, 20 Jun 2007 18:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION: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

--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-08.txt
	Pages		: 11
	Date		: 2007-6-20
	
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-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-tfrc-profile-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-tfrc-profile-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-6-20161306.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-tfrc-profile-08.txt

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

Content-Type: text/plain
Content-ID: <2007-6-20161306.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 Jun 21 03:37: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 1I1HEV-0003Mb-Ef; Thu, 21 Jun 2007 03:37:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1HET-0003MW-E6
	for avt@ietf.org; Thu, 21 Jun 2007 03:37:33 -0400
Received: from eracle.polito.it ([130.192.3.44] helo=polito.it)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1HER-0002vR-2r
	for avt@ietf.org; Thu, 21 Jun 2007 03:37:33 -0400
X-ExtScanner: Niversoft's FindAttachments (free)
Received: from [130.192.86.166] (HELO [192.168.99.134])
	by eracle.polito.it (CommuniGate Pro SMTP 5.1.9)
	with ESMTPS id 7458253; Thu, 21 Jun 2007 09:37:30 +0200
Message-ID: <467A2B7C.5030105@gentoo.org>
Date: Thu, 21 Jun 2007 09:40:44 +0200
From: Luca Barbato <lu_zero@gentoo.org>
User-Agent: Thunderbird 2.0.0.0 (X11/20070607)
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@jabber.org>
Subject: Re: [AVT] draft-ietf-avt-rtp-vorbis: configuration-uri
References: <466F0878.4090700@jabber.org> <466F3D7E.1090409@gentoo.org>
	<20070613141506.GB17886@jabber.org>
In-Reply-To: <20070613141506.GB17886@jabber.org>
X-Enigmail-Version: 0.95.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
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

Peter Saint-Andre wrote:
> As long as the text is changed to say that the format you describe is
> recommmended, I'm fine (because we would specify the XMPP URI format in
> a different spec anyway).

This is the proposed clarification, I'm tempted to ditch the
delivery_method since:

* every implementation MUST handle in_band delivery.
* inline delivery is defined by "configuration"
* out_band delivery is defined by "configuration-uri"

That would make the fmtp smaller.

-      configuration-uri:  the URI of the configuration headers in case
-         of out of band transmission.  In the form of
-         "protocol://path/to/resource/".  Depending on the specific
+      configuration-uri:  the URI [4] of the configuration headers in
+         case of out of band transmission.  In the form of
+         "protocol://path/to/resource/", depending on the specific
          method, a single configuration packet could be retrived by its
-         number, or multiple packets could be aggregated in a single
-         stream.  Such aggregates MAY be compressed using either bzip2
-         [15] or gzip [13].  A sha1 [9] checksum MAY be provided for
-         aggregates.  In this latter case the URI will end with the
+         Ident number, or multiple packets could be aggregated in a
+         single stream.  Such aggregates MAY be compressed using either
+         bzip2 [16] or gzip [14].  A sha1 [10] checksum MAY be provided
+         for aggregates.  In this latter case the URI will end with the
          aggregate name, followed by its compressed extension if
-         applies, a "!" and the base64 [8] representation of the
+         applies, a "!" and the base64 [9] representation of the
          sha1hash of the above mentioned compressed aggregated as in:
          "protocol://path/to/resource/aggregated.bz2!sha1hash".  The
-         trailing '/' discriminates which of two methods are in use.  It
-         MUST follow the associated delivery method parameter (either
-         "in_band" or "out_band").
+         trailing '/' discriminates which of two methods are in use.
+         The configuration-uri MUST follow the associated delivery
+         method parameter ("out_band").  Non hierarchical protocols and
+         protocols using for special purposes the '!' separator MAY
+         point just to a resource aggregate using their specific syntax.

I hope it addresses the xmpp issue.

-- 

Luca Barbato

Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero


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



From avt-bounces@ietf.org Thu Jun 21 04:12: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 1I1Hm8-0008Ux-AQ; Thu, 21 Jun 2007 04:12:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1Hm7-0008Uf-Mp
	for avt@ietf.org; Thu, 21 Jun 2007 04:12:19 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1Hm6-0008PT-Ti
	for avt@ietf.org; Thu, 21 Jun 2007 04:12:19 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	943EF209C4; Thu, 21 Jun 2007 10:12:17 +0200 (CEST)
X-AuditID: c1b4fb3c-b1e82bb0000007e1-64-467a32e1e8a9
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	6CA3520813; Thu, 21 Jun 2007 10:12:17 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 21 Jun 2007 10:12:16 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 21 Jun 2007 10:12:16 +0200
Message-ID: <467A32E0.9030606@ericsson.com>
Date: Thu, 21 Jun 2007 10:12:16 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [AVT] Registration procedures for RTP header extensions
References: <0A609728-183A-4181-B5A8-DA35BBAE09E9@cisco.com>
	<4678EEC2.9000702@ericsson.com>
	<0B0FC93B-8BF6-4CB3-AE4E-CB83C26AFD12@cisco.com>
In-Reply-To: <0B0FC93B-8BF6-4CB3-AE4E-CB83C26AFD12@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Jun 2007 08:12:16.0590 (UTC)
	FILETIME=[E18136E0:01C7B3DB]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: Dave Singer <singer@apple.com>, Colin Perkins <csp@csperkins.org>,
	avt@ietf.org, Stephen Casner <casner@acm.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

Cullen Jennings skrev:
> 
> 
> 
> On Jun 20, 2007, at 2:09 AM, Magnus Westerlund wrote:
> 
>> Hi Cullen,
>>
>> Sorry, but I get confused by this message. Which issue are you 
>> discussing?
>>
>> A. The policy for AVP (and by inheritance the other profiles) for the 
>> first 16-bits in the header extension. Which currently RFC 3551 says 
>> should be managed but doesn't define a policy or a registry for.
>>
>> B. Header extensions signaled using the mechanism defined in 
>> draft-ietf-avt-rtp-hdrext. Which currently is the equivalent of FCFS 
>> and with the addition of a registry for keeping track of RFC defined 
>> ones.
>>
>> I think you are talking about B and like to have confirmation of the 
>> WG be okay with this.
> Yes - I am talking about B but A is effectively being replaced by B for 
> all practical purposes so they are closely related.
> 

Thanks for the clarification.

>>
>> In the case of B my personal opinion is the following:
>>
>> 1. Per design using URIs as signalling names, this is impossible to 
>> control. The only way of fix this would be to change the identifier 
>> used for a mechanism into something a registration can keep track and 
>> assign. However that also increases the chance of borrowing a name 
>> without registering creating issues.
> 
> I was not really asking about if we should use URI or not, I was looking 
> for opinion on what level of control the WG thought they should have 
> from 1 to 4 - once we have a better idea of that, we can propose an 
> appropriate mechanism. Thoughts on this?
> 

My personal opinion is that for the URN space there should be at least 
expert review and specification required. We might consider that the bar 
for what is considered a specification is. I think it must be above a 
white paper but any industry forum or standards body that produce a 
permanent documents should be okay.  That way the ones existing in the 
formal registry are available to read. They will also receive some 
sanity check through the expert review. Going further to require an RFC 
only reduced the utility of the registry as a common gathering point for 
standardized solutions.

> 
>>
>> 2. I think the IANA section as currently written needs to be improved 
>> it is not easy to understand for someone desiring to register a name 
>> in the URN space that it is under specification required. I think a 
>> better separation of what is the rule for registration within the 
>> space and the details needed to have the URN space itself created is 
>> needed.
>>
>> I think there might be some benefit in changing the rules for the URN 
>> space to Expert Review and then have the Expert reviewer guidelines 
>> require a specification as one of the criteria for acceptance.
>>
>> However, the reality is that header extensions (16-bit field) have 
>> been totally unmanaged and been in FCFS since day one.
> 
> interesting - which extension numbers are defined?
> 

Well, that is the issue. I don't have any bodies/specifications that I 
can point at. But I have herd rumors about people using them, by simply 
picking a random number.

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 Jun 21 06: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 1I1JWP-0002Ek-IR; Thu, 21 Jun 2007 06:04:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1JWO-0002Cz-GS
	for avt@ietf.org; Thu, 21 Jun 2007 06:04:12 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1JWM-0003Bo-V7
	for avt@ietf.org; Thu, 21 Jun 2007 06:04:12 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:49235)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1I1JWK-0005Ch-3u; Thu, 21 Jun 2007 11:04:08 +0100
In-Reply-To: <DD8DDC46-4F18-4D66-939B-45C23209F855@csperkins.org>
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>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <7594FE67-7B87-4856-B462-0087E32F0B39@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] draft-ietf-avt-rtp-speex-02.txt
Date: Thu, 21 Jun 2007 11:04:08 +0100
To: jean-marc.valin@usherbrooke.ca,
 Aymeric Moizard <jack@atosc.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
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 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 Perkins
http://csperkins.org/



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



From avt-bounces@ietf.org Thu Jun 21 07:16: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 1I1Kdi-0001kQ-UG; Thu, 21 Jun 2007 07:15:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1Kdi-0001kK-AB
	for avt@ietf.org; Thu, 21 Jun 2007 07:15:50 -0400
Received: from anode.atosc.org ([195.154.245.166])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1Kdf-0007bL-NX
	for avt@ietf.org; Thu, 21 Jun 2007 07:15:50 -0400
Received: from anode.atosc.org (localhost.localdomain [127.0.0.1])
	by internal.atosc.org (Postfix) with ESMTP
	id 4EE88FB3E; Thu, 21 Jun 2007 13:08:43 +0200 (CEST)
Received: from antisip.antisip.com (unknown [77.197.73.102])
	by anode.atosc.org (Postfix) with ESMTP
	id E82A7FB14; Thu, 21 Jun 2007 13:08:42 +0200 (CEST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by antisip.antisip.com (Postfix) with ESMTP id BD95A1FE4D;
	Thu, 21 Jun 2007 13:15:43 +0200 (CEST)
X-Virus-Scanned: by hand at fauche.org
Received: from antisip.antisip.com ([127.0.0.1])
	by localhost (antisip.antisip.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id HLbYPrV55V9g; Thu, 21 Jun 2007 13:15:40 +0200 (CEST)
Received: by antisip.antisip.com (Postfix, from userid 1000)
	id 236031FE9E; Thu, 21 Jun 2007 13:15:40 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
	by antisip.antisip.com (Postfix) with ESMTP id 224561FE4D;
	Thu, 21 Jun 2007 13:15:40 +0200 (CEST)
Date: Thu, 21 Jun 2007 13:15:40 +0200 (CEST)
From: Aymeric Moizard <jack@atosc.org>
X-X-Sender: jack@sip2
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] draft-ietf-avt-rtp-speex-02.txt
In-Reply-To: <7594FE67-7B87-4856-B462-0087E32F0B39@csperkins.org>
Message-ID: <Pine.LNX.4.63.0706211306430.28061@sip2>
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>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on anode.atosc.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.8 required=3.0 tests=ALL_TRUSTED autolearn=failed 
	version=3.0.3
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
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



On Thu, 21 Jun 2007, Colin Perkins wrote:

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

The text you proposed seems fine to me: However, there is one point where
you could probably help again.

Is it acceptable for section defining media type and parameters that
"mode" parameter can be specified several times? I wanted this to
be possible for SDP usage but I'm not sure it is authorized to allow
multiple "mode" to appear in section 4.1.1.

tks,
Aymeric

> 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 Perkins
> http://csperkins.org/
>


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



From avt-bounces@ietf.org Thu Jun 21 07: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 1I1Kfw-0002Kd-8C; Thu, 21 Jun 2007 07:18:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0woS-0005a2-T0
	for avt@ietf.org; Wed, 20 Jun 2007 05:49:20 -0400
Received: from [212.25.80.121] (helo=VRZIL-MR.il.veraznetworks.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0woR-0007jc-BE
	for avt@ietf.org; Wed, 20 Jun 2007 05:49:20 -0400
Received: from VRZIL-EX01.il.veraznetworks.com ([172.29.1.6]) by
	VRZIL-MR.il.veraznetworks.com with InterScan Message Security
	Suite; Wed, 20 Jun 2007 12:53:36 +0300
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: Wed, 20 Jun 2007 12:51:53 +0300
Message-ID: <30F0D7625E0DEC4E83A2A94596BC18B701CFB8C0@VRZIL-EX01.il.veraznetworks.com>
In-Reply-To: <4e5a3720706200145k4f983112wd80ed7e224ae1675@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip-implementors] DTMF interoperability: In-band,
	RFC 2833 or SIP INFO
Thread-Index: AcezGyWG8bW8bY7pQ9GI0Cdbec7P8gABIbxw
References: <4e5a3720706200145k4f983112wd80ed7e224ae1675@mail.gmail.com>
From: "Meir Leshem" <Meir.Leshem@veraznetworks.com>
To: "Murat Artun" <artunmurat@gmail.com>, <avt@ietf.org>,
	<sip-implementors@cs.columbia.edu>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
X-Mailman-Approved-At: Thu, 21 Jun 2007 07:18:07 -0400
Cc: 
Subject: [AVT] RE: [Sip-implementors] DTMF interoperability: In-band,
	RFC 2833 or SIP INFO
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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 Murat,
Note that the in-band method for DTMF tones transfer through the VoIP
network has additional significant drawback:  the classification of DTMF
digits which are received in-band is not reliable when compressed voice
codec is used (different than G.711).

Regards
---------------------------------------
Meir Leshem
System Engineer
Veraz Networks
---------------------------------------=20

-----Original Message-----
From: sip-implementors-bounces@lists.cs.columbia.edu
[mailto:sip-implementors-bounces@lists.cs.columbia.edu] On Behalf Of
Murat Artun
Sent: Wednesday, June 20, 2007 11:45 AM
To: avt@ietf.org; sip-implementors@cs.columbia.edu
Subject: [Sip-implementors] DTMF interoperability: In-band,RFC 2833 or
SIP INFO

Hello all,

I want to ask about the interoperability issues for DTMF sending.

There exist three ways for DTMF sending: In-band (I use this term
meaning in audio as a voice data), RFC 2833 (currently 4733 obsoletes,
but no change to previous procedure exists) and SIP INFO.

Among these three ways, I know that only RFC 2833 is announced in the
SDP of a VoIP application when it is ready to receive DTMF events as
RFC 2833 packets.

I have a few points to be clarified in the sense of interoperability
issues:

- Is it preferred that DTMF is also sent in-band and as SIP INFO when
the remote VoIP application announces that it is ready to receive RFC
2833 packets?

- What if the remote VoIP application does not announce that it is
ready to receive RFC 2833 packets? Which method should be preferred,
In-band or SIP INFO, or both for reliability purposes?

- I have observed that sending DTMF as RFC 2833 packets is mostly
preferred considering that sending DTMF In-band requires the remote
VoIP application to perform tone detection in RTP level which requires
considerable processing overhead as RFC also states. Is there a known
issue about SIP INFO method for DTMF sending?

Thanks in advice...

--=20
M u r at  A r t u n, MSc.
   Design Engineer
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

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

From avt-bounces@ietf.org Thu Jun 21 07: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 1I1Kfw-0002L3-Ik; Thu, 21 Jun 2007 07:18:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0y9U-00005Y-E7
	for avt@ietf.org; Wed, 20 Jun 2007 07:15:08 -0400
Received: from extu-mxob-2.symantec.com ([216.10.194.135])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0y9S-0003Yf-Va
	for avt@ietf.org; Wed, 20 Jun 2007 07:15:08 -0400
Received: from tus1opsmtapin01.ges.symantec.com ([192.168.214.43])
	by extu-mxob-2.symantec.com with esmtp (Exim 4.66)
	(envelope-from <Vishal_Mathur@symantec.com>)
	id 1I0y9R-0001s6-U2; Wed, 20 Jun 2007 04:15:06 -0700
Received: from reserved-155-64-230-19.ges.symantec.com ([155.64.230.19]
	helo=TUS1XCHECNPIN02.enterprise.veritas.com)
	by tus1opsmtapin01.ges.symantec.com with esmtp (Exim 4.67)
	(envelope-from <Vishal_Mathur@symantec.com>)
	id 1I0y9R-0002vt-OW; Wed, 20 Jun 2007 04:15:05 -0700
Received: from PUNAXCHECNPIN02.enterprise.veritas.com ([10.217.161.22]) by
	TUS1XCHECNPIN02.enterprise.veritas.com with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 20 Jun 2007 04:15:00 -0700
Received: from PUNAXCHEMBPIN01.enterprise.veritas.com ([10.217.161.1]) by
	PUNAXCHECNPIN02.enterprise.veritas.com with Microsoft
	SMTPSVC(6.0.3790.1433); Wed, 20 Jun 2007 16:45:01 +0530
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: Wed, 20 Jun 2007 16:44:28 +0530
Message-ID: <2BFF9B0595E88342A00368623209B132C056FF@PUNAXCHEMBPIN01.enterprise.veritas.com>
In-Reply-To: <4e5a3720706200145k4f983112wd80ed7e224ae1675@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip-implementors] DTMF interoperability: In-band,
	RFC 2833 or SIP INFO
Thread-Index: AcezH1kSMoMRkQ28Tx+exOMw89/n2wADDI4g
References: <4e5a3720706200145k4f983112wd80ed7e224ae1675@mail.gmail.com>
From: "Vishal Mathur" <Vishal_Mathur@symantec.com>
To: "Murat Artun" <artunmurat@gmail.com>, <avt@ietf.org>,
	<sip-implementors@cs.columbia.edu>
X-OriginalArrivalTime: 20 Jun 2007 11:15:01.0157 (UTC)
	FILETIME=[3E7B9D50:01C7B32C]
X-Brightmail-Verdict: VlJEQwAAAAIAAAABAAAAAAAAAAEAAAAAAAAAA2luYm94AGF2dEBpZXRmLm9yZwBzaXAtaW1wbGVtZW50b3JzQGNzLmNvbHVtYmlhLmVkdQBhcnR1bm11cmF0QGdtYWlsLmNvbQA=
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
X-Mailman-Approved-At: Thu, 21 Jun 2007 07:18:07 -0400
Cc: 
Subject: [AVT] RE: [Sip-implementors] DTMF interoperability: In-band,
	RFC 2833 or SIP INFO
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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 Murat,

SIP INFO based DTMF is useful when state full proxy want to take some
action if DTMF digits are pressed by the parties. So if the call is By
pass mode (media is not passing thru server) and user press any DTMF
digit, both the method (in band and TFC 2833) will be passing this
information directly between UAC and UAS. Even in this case SIP INFO
will still be pass thru state full proxy and hence proxy can take
certain decision like forwarding, conference initiation etc.

Regards,

Vishal Mathur
Symantec Corporation
www.symantec.com
_________________________________
Office: +91-20-66067655

-----Original Message-----
From: sip-implementors-bounces@lists.cs.columbia.edu
[mailto:sip-implementors-bounces@lists.cs.columbia.edu] On Behalf Of
Murat Artun
Sent: Wednesday, June 20, 2007 2:15 PM
To: avt@ietf.org; sip-implementors@cs.columbia.edu
Subject: [Sip-implementors] DTMF interoperability: In-band,RFC 2833 or
SIP INFO

Hello all,

I want to ask about the interoperability issues for DTMF sending.

There exist three ways for DTMF sending: In-band (I use this term
meaning in audio as a voice data), RFC 2833 (currently 4733 obsoletes,
but no change to previous procedure exists) and SIP INFO.

Among these three ways, I know that only RFC 2833 is announced in the
SDP of a VoIP application when it is ready to receive DTMF events as
RFC 2833 packets.

I have a few points to be clarified in the sense of interoperability
issues:

- Is it preferred that DTMF is also sent in-band and as SIP INFO when
the remote VoIP application announces that it is ready to receive RFC
2833 packets?

- What if the remote VoIP application does not announce that it is
ready to receive RFC 2833 packets? Which method should be preferred,
In-band or SIP INFO, or both for reliability purposes?

- I have observed that sending DTMF as RFC 2833 packets is mostly
preferred considering that sending DTMF In-band requires the remote
VoIP application to perform tone detection in RTP level which requires
considerable processing overhead as RFC also states. Is there a known
issue about SIP INFO method for DTMF sending?

Thanks in advice...

--=20
M u r at  A r t u n, MSc.
   Design Engineer
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

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





From avt-bounces@ietf.org Thu Jun 21 07: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 1I1Kfw-0002Kd-8C; Thu, 21 Jun 2007 07:18:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0woS-0005a2-T0
	for avt@ietf.org; Wed, 20 Jun 2007 05:49:20 -0400
Received: from [212.25.80.121] (helo=VRZIL-MR.il.veraznetworks.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0woR-0007jc-BE
	for avt@ietf.org; Wed, 20 Jun 2007 05:49:20 -0400
Received: from VRZIL-EX01.il.veraznetworks.com ([172.29.1.6]) by
	VRZIL-MR.il.veraznetworks.com with InterScan Message Security
	Suite; Wed, 20 Jun 2007 12:53:36 +0300
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: Wed, 20 Jun 2007 12:51:53 +0300
Message-ID: <30F0D7625E0DEC4E83A2A94596BC18B701CFB8C0@VRZIL-EX01.il.veraznetworks.com>
In-Reply-To: <4e5a3720706200145k4f983112wd80ed7e224ae1675@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip-implementors] DTMF interoperability: In-band,
	RFC 2833 or SIP INFO
Thread-Index: AcezGyWG8bW8bY7pQ9GI0Cdbec7P8gABIbxw
References: <4e5a3720706200145k4f983112wd80ed7e224ae1675@mail.gmail.com>
From: "Meir Leshem" <Meir.Leshem@veraznetworks.com>
To: "Murat Artun" <artunmurat@gmail.com>, <avt@ietf.org>,
	<sip-implementors@cs.columbia.edu>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
X-Mailman-Approved-At: Thu, 21 Jun 2007 07:18:07 -0400
Cc: 
Subject: [AVT] RE: [Sip-implementors] DTMF interoperability: In-band,
	RFC 2833 or SIP INFO
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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 Murat,
Note that the in-band method for DTMF tones transfer through the VoIP
network has additional significant drawback:  the classification of DTMF
digits which are received in-band is not reliable when compressed voice
codec is used (different than G.711).

Regards
---------------------------------------
Meir Leshem
System Engineer
Veraz Networks
---------------------------------------=20

-----Original Message-----
From: sip-implementors-bounces@lists.cs.columbia.edu
[mailto:sip-implementors-bounces@lists.cs.columbia.edu] On Behalf Of
Murat Artun
Sent: Wednesday, June 20, 2007 11:45 AM
To: avt@ietf.org; sip-implementors@cs.columbia.edu
Subject: [Sip-implementors] DTMF interoperability: In-band,RFC 2833 or
SIP INFO

Hello all,

I want to ask about the interoperability issues for DTMF sending.

There exist three ways for DTMF sending: In-band (I use this term
meaning in audio as a voice data), RFC 2833 (currently 4733 obsoletes,
but no change to previous procedure exists) and SIP INFO.

Among these three ways, I know that only RFC 2833 is announced in the
SDP of a VoIP application when it is ready to receive DTMF events as
RFC 2833 packets.

I have a few points to be clarified in the sense of interoperability
issues:

- Is it preferred that DTMF is also sent in-band and as SIP INFO when
the remote VoIP application announces that it is ready to receive RFC
2833 packets?

- What if the remote VoIP application does not announce that it is
ready to receive RFC 2833 packets? Which method should be preferred,
In-band or SIP INFO, or both for reliability purposes?

- I have observed that sending DTMF as RFC 2833 packets is mostly
preferred considering that sending DTMF In-band requires the remote
VoIP application to perform tone detection in RTP level which requires
considerable processing overhead as RFC also states. Is there a known
issue about SIP INFO method for DTMF sending?

Thanks in advice...

--=20
M u r at  A r t u n, MSc.
   Design Engineer
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

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

From avt-bounces@ietf.org Thu Jun 21 07: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 1I1Kfw-0002L3-Ik; Thu, 21 Jun 2007 07:18:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0y9U-00005Y-E7
	for avt@ietf.org; Wed, 20 Jun 2007 07:15:08 -0400
Received: from extu-mxob-2.symantec.com ([216.10.194.135])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0y9S-0003Yf-Va
	for avt@ietf.org; Wed, 20 Jun 2007 07:15:08 -0400
Received: from tus1opsmtapin01.ges.symantec.com ([192.168.214.43])
	by extu-mxob-2.symantec.com with esmtp (Exim 4.66)
	(envelope-from <Vishal_Mathur@symantec.com>)
	id 1I0y9R-0001s6-U2; Wed, 20 Jun 2007 04:15:06 -0700
Received: from reserved-155-64-230-19.ges.symantec.com ([155.64.230.19]
	helo=TUS1XCHECNPIN02.enterprise.veritas.com)
	by tus1opsmtapin01.ges.symantec.com with esmtp (Exim 4.67)
	(envelope-from <Vishal_Mathur@symantec.com>)
	id 1I0y9R-0002vt-OW; Wed, 20 Jun 2007 04:15:05 -0700
Received: from PUNAXCHECNPIN02.enterprise.veritas.com ([10.217.161.22]) by
	TUS1XCHECNPIN02.enterprise.veritas.com with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 20 Jun 2007 04:15:00 -0700
Received: from PUNAXCHEMBPIN01.enterprise.veritas.com ([10.217.161.1]) by
	PUNAXCHECNPIN02.enterprise.veritas.com with Microsoft
	SMTPSVC(6.0.3790.1433); Wed, 20 Jun 2007 16:45:01 +0530
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: Wed, 20 Jun 2007 16:44:28 +0530
Message-ID: <2BFF9B0595E88342A00368623209B132C056FF@PUNAXCHEMBPIN01.enterprise.veritas.com>
In-Reply-To: <4e5a3720706200145k4f983112wd80ed7e224ae1675@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip-implementors] DTMF interoperability: In-band,
	RFC 2833 or SIP INFO
Thread-Index: AcezH1kSMoMRkQ28Tx+exOMw89/n2wADDI4g
References: <4e5a3720706200145k4f983112wd80ed7e224ae1675@mail.gmail.com>
From: "Vishal Mathur" <Vishal_Mathur@symantec.com>
To: "Murat Artun" <artunmurat@gmail.com>, <avt@ietf.org>,
	<sip-implementors@cs.columbia.edu>
X-OriginalArrivalTime: 20 Jun 2007 11:15:01.0157 (UTC)
	FILETIME=[3E7B9D50:01C7B32C]
X-Brightmail-Verdict: VlJEQwAAAAIAAAABAAAAAAAAAAEAAAAAAAAAA2luYm94AGF2dEBpZXRmLm9yZwBzaXAtaW1wbGVtZW50b3JzQGNzLmNvbHVtYmlhLmVkdQBhcnR1bm11cmF0QGdtYWlsLmNvbQA=
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
X-Mailman-Approved-At: Thu, 21 Jun 2007 07:18:07 -0400
Cc: 
Subject: [AVT] RE: [Sip-implementors] DTMF interoperability: In-band,
	RFC 2833 or SIP INFO
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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 Murat,

SIP INFO based DTMF is useful when state full proxy want to take some
action if DTMF digits are pressed by the parties. So if the call is By
pass mode (media is not passing thru server) and user press any DTMF
digit, both the method (in band and TFC 2833) will be passing this
information directly between UAC and UAS. Even in this case SIP INFO
will still be pass thru state full proxy and hence proxy can take
certain decision like forwarding, conference initiation etc.

Regards,

Vishal Mathur
Symantec Corporation
www.symantec.com
_________________________________
Office: +91-20-66067655

-----Original Message-----
From: sip-implementors-bounces@lists.cs.columbia.edu
[mailto:sip-implementors-bounces@lists.cs.columbia.edu] On Behalf Of
Murat Artun
Sent: Wednesday, June 20, 2007 2:15 PM
To: avt@ietf.org; sip-implementors@cs.columbia.edu
Subject: [Sip-implementors] DTMF interoperability: In-band,RFC 2833 or
SIP INFO

Hello all,

I want to ask about the interoperability issues for DTMF sending.

There exist three ways for DTMF sending: In-band (I use this term
meaning in audio as a voice data), RFC 2833 (currently 4733 obsoletes,
but no change to previous procedure exists) and SIP INFO.

Among these three ways, I know that only RFC 2833 is announced in the
SDP of a VoIP application when it is ready to receive DTMF events as
RFC 2833 packets.

I have a few points to be clarified in the sense of interoperability
issues:

- Is it preferred that DTMF is also sent in-band and as SIP INFO when
the remote VoIP application announces that it is ready to receive RFC
2833 packets?

- What if the remote VoIP application does not announce that it is
ready to receive RFC 2833 packets? Which method should be preferred,
In-band or SIP INFO, or both for reliability purposes?

- I have observed that sending DTMF as RFC 2833 packets is mostly
preferred considering that sending DTMF In-band requires the remote
VoIP application to perform tone detection in RTP level which requires
considerable processing overhead as RFC also states. Is there a known
issue about SIP INFO method for DTMF sending?

Thanks in advice...

--=20
M u r at  A r t u n, MSc.
   Design Engineer
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

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





From avt-bounces@ietf.org Thu Jun 21 07:23: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 1I1KlO-000355-A5; Thu, 21 Jun 2007 07:23:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1KlM-00034z-Bn
	for avt@ietf.org; Thu, 21 Jun 2007 07:23:44 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1KlK-0000np-2O
	for avt@ietf.org; Thu, 21 Jun 2007 07:23:44 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:49488)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1I1KlJ-0001l7-6M; Thu, 21 Jun 2007 12:23:41 +0100
In-Reply-To: <Pine.LNX.4.63.0706211306430.28061@sip2>
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>
	<Pine.LNX.4.63.0706211306430.28061@sip2>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <40D6D796-89A4-4992-97E3-417D3C4A1387@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] draft-ietf-avt-rtp-speex-02.txt
Date: Thu, 21 Jun 2007 12:23:39 +0100
To: Aymeric Moizard <jack@atosc.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
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

On 21 Jun 2007, at 12:15, Aymeric Moizard wrote:
> On Thu, 21 Jun 2007, Colin Perkins wrote:
>>> 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.
>
> The text you proposed seems fine to me: However, there is one point  
> where
> you could probably help again.
>
> Is it acceptable for section defining media type and parameters that
> "mode" parameter can be specified several times? I wanted this to
> be possible for SDP usage but I'm not sure it is authorized to allow
> multiple "mode" to appear in section 4.1.1.

I'm not sure why you'd want to include multiple mode parameters, each  
containing a single list. Why not define a single mode parameter,  
supporting multiple lists of modes?

Colin

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



From avt-bounces@ietf.org Thu Jun 21 07:41: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 1I1L2Q-00038t-PZ; Thu, 21 Jun 2007 07:41:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1L2P-00038n-6B
	for avt@ietf.org; Thu, 21 Jun 2007 07:41:21 -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 1I1L2N-0004ck-OW
	for avt@ietf.org; Thu, 21 Jun 2007 07:41:21 -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: Thu, 21 Jun 2007 14:42:36 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04AFC18B@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: new draft-kristensen-avt-rtp-h264-params-00.txt
Thread-Index: Acez+UNtUCLEvQ+8RRm0WsIgRmOI1A==
From: "Even, Roni" <roni.even@polycom.co.il>
To: <avt@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Subject: [AVT] new draft-kristensen-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

Hi,
This new draft is based on the consensus from the Prague meeting to =
divide the H264 new parameters to a separate draft.

This draft specifies new H264 subtype optional parameters currently =
supported and used in H.32x (0,3,4) systems.
The parameters address static macro blocks and sample aspect ratio of =
the receiver.

Thanks
Roni Even=20





A New Internet-Draft is available from the on-line Internet-Drafts=20
directories.


	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-kristensen-avt-rtp-h264-params-00.txt
	Pages		: 8
	Date		: 2007-6-19
=09
   This document updates RFC 3984.  It defines new optional parameters
   addressing new 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-kristensen-avt-rtp-h264-params-=
00.txt

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



From avt-bounces@ietf.org Thu Jun 21 08:40: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 1I1LxM-0003Or-MK; Thu, 21 Jun 2007 08:40:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1LxL-0003NN-VF
	for avt@ietf.org; Thu, 21 Jun 2007 08:40:11 -0400
Received: from anode.atosc.org ([195.154.245.166])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1LxJ-00055E-Sn
	for avt@ietf.org; Thu, 21 Jun 2007 08:40:11 -0400
Received: from anode.atosc.org (localhost.localdomain [127.0.0.1])
	by internal.atosc.org (Postfix) with ESMTP
	id EE127FC22; Thu, 21 Jun 2007 14:32:37 +0200 (CEST)
Received: from antisip.antisip.com (unknown [77.197.73.102])
	by anode.atosc.org (Postfix) with ESMTP
	id 57A2CFC0C; Thu, 21 Jun 2007 14:32:37 +0200 (CEST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by antisip.antisip.com (Postfix) with ESMTP id 625801FE4D;
	Thu, 21 Jun 2007 14:39:38 +0200 (CEST)
X-Virus-Scanned: by hand at fauche.org
Received: from antisip.antisip.com ([127.0.0.1])
	by localhost (antisip.antisip.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Y17QYykVZLK6; Thu, 21 Jun 2007 14:39:31 +0200 (CEST)
Received: by antisip.antisip.com (Postfix, from userid 1000)
	id 70C841FE9E; Thu, 21 Jun 2007 14:39:31 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
	by antisip.antisip.com (Postfix) with ESMTP id 6D3FE1FE4D;
	Thu, 21 Jun 2007 14:39:31 +0200 (CEST)
Date: Thu, 21 Jun 2007 14:39:31 +0200 (CEST)
From: Aymeric Moizard <jack@atosc.org>
X-X-Sender: jack@sip2
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] draft-ietf-avt-rtp-speex-02.txt
In-Reply-To: <40D6D796-89A4-4992-97E3-417D3C4A1387@csperkins.org>
Message-ID: <Pine.LNX.4.63.0706211434431.28061@sip2>
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>
	<Pine.LNX.4.63.0706211306430.28061@sip2>
	<40D6D796-89A4-4992-97E3-417D3C4A1387@csperkins.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on anode.atosc.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.8 required=3.0 tests=ALL_TRUSTED autolearn=failed 
	version=3.0.3
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
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



On Thu, 21 Jun 2007, Colin Perkins wrote:

> On 21 Jun 2007, at 12:15, Aymeric Moizard wrote:
>> On Thu, 21 Jun 2007, Colin Perkins wrote:
>>>> 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.
>> 
>> The text you proposed seems fine to me: However, there is one point where
>> you could probably help again.
>> 
>> Is it acceptable for section defining media type and parameters that
>> "mode" parameter can be specified several times? I wanted this to
>> be possible for SDP usage but I'm not sure it is authorized to allow
>> multiple "mode" to appear in section 4.1.1.
>
> I'm not sure why you'd want to include multiple mode parameters, each 
> containing a single list.

Each mode only contains ONE value. This is what should be understood
from the draft.

> Why not define a single mode parameter, supporting multiple lists of 
> modes?

I find it easier to have several "mode=X;mode=Y" rather than a "mode=X|Y".

What only question is about the meaning of "mode=X;mode=Y" -> It's usefull
for SDP usage (some speex implementation will support only mode X and Y), 
For media type registration? I don't know what could be the meaning: I'm
only a SDP offer/answer user and have no knowledge on media type use.

Aymeric

> Colin
>


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



From avt-bounces@ietf.org Thu Jun 21 10:54: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 1I1O2k-0003bs-UO; Thu, 21 Jun 2007 10:53:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1O2j-0003ay-TQ
	for avt@ietf.org; Thu, 21 Jun 2007 10:53:53 -0400
Received: from atlas.jabber.org ([208.245.212.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1O2h-0006Uk-8u
	for avt@ietf.org; Thu, 21 Jun 2007 10:53:53 -0400
Received: by atlas.jabber.org (Postfix, from userid 1005)
	id E0AE821A287; Thu, 21 Jun 2007 09:59:14 -0500 (CDT)
Date: Thu, 21 Jun 2007 09:59:14 -0500
From: Peter Saint-Andre <stpeter@jabber.org>
To: Luca Barbato <lu_zero@gentoo.org>
Subject: Re: [AVT] draft-ietf-avt-rtp-vorbis: configuration-uri
Message-ID: <20070621145914.GD2739@jabber.org>
References: <466F0878.4090700@jabber.org> <466F3D7E.1090409@gentoo.org>
	<20070613141506.GB17886@jabber.org> <467A2B7C.5030105@gentoo.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <467A2B7C.5030105@gentoo.org>
Jabber-ID: stpeter@jabber.org
User-Agent: Mutt/1.5.6+20040907i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
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 Thu, Jun 21, 2007 at 09:40:44AM +0200, Luca Barbato wrote:
> Peter Saint-Andre wrote:
> > As long as the text is changed to say that the format you describe is
> > recommmended, I'm fine (because we would specify the XMPP URI format in
> > a different spec anyway).
> 
> This is the proposed clarification

<snip/>

That looks fine to me.

/psa


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



From avt-bounces@ietf.org Thu Jun 21 12:46: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 1I1Pmt-0004r4-Ou; Thu, 21 Jun 2007 12:45:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1Pmt-0004qz-2M
	for avt@ietf.org; Thu, 21 Jun 2007 12:45:39 -0400
Received: from smtp108.rog.mail.re2.yahoo.com ([68.142.225.206])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1I1Pmr-0003Y6-K1
	for avt@ietf.org; Thu, 21 Jun 2007 12:45:39 -0400
Received: (qmail 26820 invoked from network); 21 Jun 2007 16:45:37 -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=SsAEFQlOmMA9fawpYLvvh5NzptB2rut3kKeeJICdt5gCVj0wt+5gysuPGae8GX+EuYYJPgTnRaVaETQEzKwjp6L3j2w73OsHpH5KilHWZp6oG4EUa0KNN7tL395abbHLlZ3MYFYY3rr5T0P1C24qBgHClj3c5j/rgEuUG8mqS9c=
	; 
Received: from unknown (HELO ?192.168.0.100?)
	(tom.taylor@rogers.com@74.105.35.229 with plain)
	by smtp108.rog.mail.re2.yahoo.com with SMTP; 21 Jun 2007 16:45:37 -0000
X-YMail-OSG: DlS.PaYVM1k.oE4CL8ljLN.D0M1pi91GO6xgF2osjj.LJXpN7DbqKrJnbbXLq9.ZIQ--
Message-ID: <467AAB39.80104@rogers.com>
Date: Thu, 21 Jun 2007 12:45:45 -0400
From: Tom Taylor <tom.taylor@rogers.com>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: 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: 8ac499381112328dd60aea5b1ff596ea
Subject: [AVT] draft-kristensen-avt-rtp-h264-params-00 as AVT 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 authors of draft-kristensen-avt-rtp-h264-params-00 have asked that 
it become an AVT work item.  This draft comes out of discussion in Prague.

Comments are invited.  Are there any objections to making this a work item?

Tom Taylor

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



From avt-bounces@ietf.org Thu Jun 21 22:30: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 1I1Yv5-0003su-Al; Thu, 21 Jun 2007 22:30:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1Yv3-0003qp-2M
	for avt@ietf.org; Thu, 21 Jun 2007 22:30:41 -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 1I1Yv1-0004eF-SS for avt@ietf.org; Thu, 21 Jun 2007 22:30:41 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 21 Jun 2007 22:30:39 -0400
To: "Even, Roni" <roni.even@polycom.co.il>
Subject: Re: [AVT] new draft-kristensen-avt-rtp-h264-params-00.txt
References: <144ED8561CE90C41A3E5908EDECE315C04AFC18B@IsrExch01.israel.polycom.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Thu, 21 Jun 2007 22:30:38 -0400
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C04AFC18B@IsrExch01.israel.polycom.com>
	(Roni Even's message of "Thu, 21 Jun 2007 14:42:36 +0300")
Message-ID: <ybuk5twlnzl.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 22 Jun 2007 02:30:39.0546 (UTC)
	FILETIME=[52BA41A0:01C7B475]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

"Even, Roni" <roni.even@polycom.co.il> writes:
>This draft specifies new H264 subtype optional parameters currently
>supported and used in H.32x (0,3,4) systems.  The parameters address
>static macro blocks and sample aspect ratio of the receiver.

The draft references several tables in specs that aren't always easily
available (or weren't last I know - ITU tends to charge for final versions
of specs).  This makes this draft tougher to evaluate, and tougher to use.

In recvonly and sendrecv streams, sar and esar represent what they are
willing to receive.  It's not clear from this draft how to know what's
being sent for sar (though I assume it's somewhere in the H.264 parameter
sets).  This draft should mention where the actual aspect ratio comes from
for sar (it mentions it for esar - H.264 VUI).

-- 
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 Jun 22 03:20: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 1I1dRN-0000qk-Au; Fri, 22 Jun 2007 03:20:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1dRL-0000ir-Ck
	for avt@ietf.org; Fri, 22 Jun 2007 03:20:19 -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 1I1dRJ-0007B2-TY
	for avt@ietf.org; Fri, 22 Jun 2007 03:20:19 -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] new draft-kristensen-avt-rtp-h264-params-00.txt
Date: Fri, 22 Jun 2007 10:21:08 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04AFC28A@IsrExch01.israel.polycom.com>
In-Reply-To: <ybuk5twlnzl.fsf@jesup.eng.wgate.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] new draft-kristensen-avt-rtp-h264-params-00.txt
Thread-Index: Ace0dXTPkwYAJLafRYmW8Ag2+KPeugAJxN6A
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Randell Jesup" <rjesup@wgate.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Randell,
The ITU has opened free access to ITU specifications in pdf format. You
can try the ITU web site and see that you can now download
recommendations.

See H series in the link

http://www.itu.int/rec/T-REC-H/e

and for H.241 inside that web page.

http://www.itu.int/rec/T-REC-H.241-200605-I/en


As for VUI I will add some more text. The sample aspect ratio in H.264
is inside the data stream. In order to decode H.264 you need to
understand the data format since even the geometry is in the parameter
sets message inside the media stream, this is different from H.261 and
H.263 that has pre-defines resolutions.

Roni

> -----Original Message-----
> From: Randell Jesup [mailto:rjesup@wgate.com]
> Sent: Friday, June 22, 2007 5:31 AM
> To: Even, Roni
> Cc: avt@ietf.org
> Subject: Re: [AVT] new draft-kristensen-avt-rtp-h264-params-00.txt
>=20
> "Even, Roni" <roni.even@polycom.co.il> writes:
> >This draft specifies new H264 subtype optional parameters currently
> >supported and used in H.32x (0,3,4) systems.  The parameters address
> >static macro blocks and sample aspect ratio of the receiver.
>=20
> The draft references several tables in specs that aren't always easily
> available (or weren't last I know - ITU tends to charge for final
versions
> of specs).  This makes this draft tougher to evaluate, and tougher to
use.
>=20
> In recvonly and sendrecv streams, sar and esar represent what they are
> willing to receive.  It's not clear from this draft how to know what's
> being sent for sar (though I assume it's somewhere in the H.264
parameter
> sets).  This draft should mention where the actual aspect ratio comes
from
> for sar (it mentions it for esar - H.264 VUI).
>=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 Fri Jun 22 16:36: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 1I1pF3-0006Tm-DH; Fri, 22 Jun 2007 15:56:26 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1p9u-0008CT-EG; Fri, 22 Jun 2007 15:51:06 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I1p9q-0007ym-W3; Fri, 22 Jun 2007 15:51:06 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id BD2372ACB2;
	Fri, 22 Jun 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I1p8s-0008Ru-9H; Fri, 22 Jun 2007 15:50: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: <E1I1p8s-0008Ru-9H@stiedprstage1.ietf.org>
Date: Fri, 22 Jun 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-app-rtp-keepalive-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		: Application Mechanism for maintaining alive the Network Address Translator (NAT) mappings associated to RTP flows.
	Author(s)	: X. Marjou, A. Sollaud
	Filename	: draft-ietf-avt-app-rtp-keepalive-00.txt
	Pages		: 9
	Date		: 2007-6-22
	

   This document lists the different mechanisms that enable applications
   using Real-time Transport Protocol (RTP) to maintain their RTP
   Network Address Translator (NAT) mappings alive.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-app-rtp-keepalive-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-app-rtp-keepalive-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-app-rtp-keepalive-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-6-22135922.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-avt-app-rtp-keepalive-00.txt

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

Content-Type: text/plain
Content-ID: <2007-6-22135922.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 Sun Jun 24 14:00: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 1I2WO3-000483-22; Sun, 24 Jun 2007 14:00:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2WO2-00047x-Fv
	for avt@ietf.org; Sun, 24 Jun 2007 14:00:34 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2WO1-0004v2-5V
	for avt@ietf.org; Sun, 24 Jun 2007 14:00:34 -0400
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:63013
	helo=[192.168.0.4])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1I2WNz-0004UP-Ow; Sun, 24 Jun 2007 19:00:31 +0100
In-Reply-To: <0MKp8S-1I10wF3BuK-0002si@mrelay.perfora.net>
References: <0MKp8S-1I10wF3BuK-0002si@mrelay.perfora.net>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <FC7B9B6B-15D8-4B2F-82CD-3E1092F92E77@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] draft-ietf-avt-hdrext-12
Date: Sun, 24 Jun 2007 19:00:27 +0100
To: Michael A Dolan <md.1@newtbt.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
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 20 Jun 2007, at 15:10, Michael A Dolan wrote:
> I'm not sure where this work stands since Tom's recommendation in  
> March, but I notice a few people have commented lately so thought  
> I'd speak up....
>
> I discovered a deployed system the other day that did the header  
> extensions in a very similar (but not identical) way.  In this  
> other system, the "defined by profile" field has several defined  
> values and the multi-sub-field technique is present, using an ID  
> and LEN fields.  But these fields are a different size (not 4 and 4  
> bits).  It was basically the same design, though.

Are there reasons, other than historical accident, for the  
differences in the two designs? How widely deployed is this system?

> I need to get this other practice documented for use by another  
> standards body.  I'd prefer to document it in IETF rather than  
> elsewhere.
>
> Because the design is so similar, I was thinking one approach would  
> be to augment this ID?  I realize this is very late in what's been  
> a long process for this ID (with my apologies to Dave).   
> Nevertheless, finding a deployed system so similar, it might be  
> worth capturing them both in the same document with a clear way to  
> discriminate them (which would be more difficult to explain if they  
> were in separate documents).
>
> I'm prepared to promptly contribute a proposed revision to this ID  
> if folks are open to the idea.
>
> Comments?

I'd prefer to converge on one mechanism, rather than documenting that  
two similar (but incompatible) variants exist, if possible.

-- 
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 Jun 24 14:59: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 1I2XId-0003JM-NN; Sun, 24 Jun 2007 14:59:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2XIc-0003JE-RJ
	for avt@ietf.org; Sun, 24 Jun 2007 14:59:02 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2XIb-0002pD-AP
	for avt@ietf.org; Sun, 24 Jun 2007 14:59:02 -0400
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:63236
	helo=[192.168.0.4])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1I2XIa-0006Dz-CA; Sun, 24 Jun 2007 19:59:00 +0100
In-Reply-To: <Pine.LNX.4.63.0706211434431.28061@sip2>
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>
	<Pine.LNX.4.63.0706211306430.28061@sip2>
	<40D6D796-89A4-4992-97E3-417D3C4A1387@csperkins.org>
	<Pine.LNX.4.63.0706211434431.28061@sip2>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <87538AE5-6CFB-470D-9DF4-F0425275BFD9@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] draft-ietf-avt-rtp-speex-02.txt
Date: Sun, 24 Jun 2007 19:58:56 +0100
To: Aymeric Moizard <jack@atosc.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
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

On 21 Jun 2007, at 13:39, Aymeric Moizard wrote:
> On Thu, 21 Jun 2007, Colin Perkins wrote:
>> On 21 Jun 2007, at 12:15, Aymeric Moizard wrote:
>>> On Thu, 21 Jun 2007, Colin Perkins wrote:
>>>>> 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.
>>> The text you proposed seems fine to me: However, there is one  
>>> point where
>>> you could probably help again.
>>> Is it acceptable for section defining media type and parameters that
>>> "mode" parameter can be specified several times? I wanted this to
>>> be possible for SDP usage but I'm not sure it is authorized to allow
>>> multiple "mode" to appear in section 4.1.1.
>>
>> I'm not sure why you'd want to include multiple mode parameters,  
>> each containing a single list.
>
> Each mode only contains ONE value. This is what should be understood
> from the draft.
>
>> Why not define a single mode parameter, supporting multiple lists  
>> of modes?
>
> I find it easier to have several "mode=X;mode=Y" rather than a  
> "mode=X|Y".

The former is generally easier to specify, and understand, in the  
ABNF, so I'd recommend that, rather than duplicating the parameter.

-- 
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 Jun 25 04:18: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 1I2jmF-0007tc-8C; Mon, 25 Jun 2007 04:18:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2jmD-0007nf-Di
	for avt@ietf.org; Mon, 25 Jun 2007 04:18:25 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2jmB-00085B-3s
	for avt@ietf.org; Mon, 25 Jun 2007 04:18:25 -0400
Received: from relay6.apple.com (relay6.apple.com [17.128.113.36])
	by mail-out4.apple.com (Postfix) with ESMTP id 608A1A641B1;
	Mon, 25 Jun 2007 01:18:22 -0700 (PDT)
Received: from relay6.apple.com (unknown [127.0.0.1])
	by relay6.apple.com (Symantec Mail Security) with ESMTP id 4BA2D10085; 
	Mon, 25 Jun 2007 01:18:22 -0700 (PDT)
X-AuditID: 11807124-a14dfbb0000007e2-5b-467f7a4d3774
Received: from [17.202.35.52] (int-si-a.apple.com [17.128.113.41])
	by relay6.apple.com (Apple SCV relay) with ESMTP id C186C10044;
	Mon, 25 Jun 2007 01:18:20 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p0624088fc2a52a180bde@[17.202.35.52]>
In-Reply-To: <FC7B9B6B-15D8-4B2F-82CD-3E1092F92E77@csperkins.org>
References: <0MKp8S-1I10wF3BuK-0002si@mrelay.perfora.net>
	<FC7B9B6B-15D8-4B2F-82CD-3E1092F92E77@csperkins.org>
Date: Mon, 25 Jun 2007 11:17:00 +0300
To: Colin Perkins <csp@csperkins.org>, Michael A Dolan <md.1@newtbt.com>
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: 769a46790fb42fbb0b0cc700c82f7081
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

At 19:00  +0100 24/06/07, Colin Perkins wrote:
>On 20 Jun 2007, at 15:10, Michael A Dolan wrote:
>>I'm not sure where this work stands since Tom's recommendation in 
>>March, but I notice a few people have commented lately so thought 
>>I'd speak up....
>>
>>I discovered a deployed system the other day that did the header 
>>extensions in a very similar (but not identical) way.  In this 
>>other system, the "defined by profile" field has several defined 
>>values and the multi-sub-field technique is present, using an ID 
>>and LEN fields.  But these fields are a different size (not 4 and 4 
>>bits).  It was basically the same design, though.
>
>Are there reasons, other than historical accident, for the 
>differences in the two designs? How widely deployed is this system?
>
>>I need to get this other practice documented for use by another 
>>standards body.  I'd prefer to document it in IETF rather than 
>>elsewhere.
>>
>>Because the design is so similar, I was thinking one approach would 
>>be to augment this ID?  I realize this is very late in what's been 
>>a long process for this ID (with my apologies to Dave).  
>>Nevertheless, finding a deployed system so similar, it might be 
>>worth capturing them both in the same document with a clear way to 
>>discriminate them (which would be more difficult to explain if they 
>>were in separate documents).
>>
>>I'm prepared to promptly contribute a proposed revision to this ID 
>>if folks are open to the idea.
>>
>>Comments?
>
>I'd prefer to converge on one mechanism, rather than documenting 
>that two similar (but incompatible) variants exist, if possible.

I guess I should say at this point that I am also aware of an 
implementation of my drafts;  though, just like Mike's report, this 
is a "hearsay" rather than a statement by the implementors themselves.

Mike, what was the intent of the company you know of?  Did they 
intend to make a public specification?

I find it surprising that they did something independently which is 
so close to what I created!
-- 
David Singer
Apple/QuickTime

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



From avt-bounces@ietf.org Mon Jun 25 11:32: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 1I2qYO-0008Ss-Hm; Mon, 25 Jun 2007 11:32:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2qYM-0008Sm-WD
	for avt@ietf.org; Mon, 25 Jun 2007 11:32:35 -0400
Received: from mout.perfora.net ([74.208.4.194])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2qYM-0000QR-Fi
	for avt@ietf.org; Mon, 25 Jun 2007 11:32:34 -0400
Received: from [71.136.175.166] (helo=TBT-Laptop.newtbt.com)
	by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis),
	id 0MKpCa-1I2qYK1rf9-0001br; Mon, 25 Jun 2007 11:32:34 -0400
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 25 Jun 2007 08:32:17 -0700
To: avt@ietf.org
From: Michael A Dolan <md.1@newtbt.com>
Subject: Re: [AVT] draft-ietf-avt-hdrext-12
In-Reply-To: <p0624088fc2a52a180bde@[17.202.35.52]>
References: <0MKp8S-1I10wF3BuK-0002si@mrelay.perfora.net>
	<FC7B9B6B-15D8-4B2F-82CD-3E1092F92E77@csperkins.org>
	<p0624088fc2a52a180bde@[17.202.35.52]>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Message-ID: <0MKpCa-1I2qYK1rf9-0001br@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX184ItRm2aEyEfV2OaE17tjxJxWUsZNEIY78SNE
	VU4G1cYJQ4ICrYpQDzac4l7nprTeuiPAKJHLKOL2nvMecGL3e6
	qN9t8ei7jjyFMMo1ku/sA==
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

Colin, Dave and all-

In review of the actual sub-extensions in use,=20
they could theoretically have been implemented=20
with the design in the ID. There is evidence that=20
their work pre-dated hdrext-00, so it appears purely a historical accident.

FYI, I have been retained by the implementers to=20
publicly document their work, and am beginning=20
that process.  So, this is not research project or informational report.

I don't have any data on how widely deployed the=20
system is - I could inquire. Although I=20
understand the rationale for the question, I=20
hesitate to enter into a debate over relative=20
"deployedness".  Regardless of the measure used=20
(# units, #sites, #independent implementations),=20
I need to document what they did (at least in a=20
compatible way).  I have therefore personally=20
leapt to the state of mind of both designs being=20
fait =E0 compli, so my intent was to capture the=20
two variants in one place as the next best thing=20
to a single design.  FYI, it is possible to=20
discriminate the two easily and unambiguously without altering Dave's=
 design.

Would it be helpful to see the details?

Regards,

         Mike

At 01:17 AM 6/25/2007, Dave Singer wrote:
>At 19:00  +0100 24/06/07, Colin Perkins wrote:
>>On 20 Jun 2007, at 15:10, Michael A Dolan wrote:
>>>I'm not sure where this work stands since=20
>>>Tom's recommendation in March, but I notice a=20
>>>few people have commented lately so thought I'd speak up....
>>>
>>>I discovered a deployed system the other day=20
>>>that did the header extensions in a very=20
>>>similar (but not identical) way.  In this=20
>>>other system, the "defined by profile" field=20
>>>has several defined values and the=20
>>>multi-sub-field technique is present, using an=20
>>>ID and LEN fields.  But these fields are a=20
>>>different size (not 4 and 4 bits).  It was basically the same design,=
 though.
>>
>>Are there reasons, other than historical=20
>>accident, for the differences in the two=20
>>designs? How widely deployed is this system?
>>
>>>I need to get this other practice documented=20
>>>for use by another standards body.  I'd prefer=20
>>>to document it in IETF rather than elsewhere.
>>>
>>>Because the design is so similar, I was=20
>>>thinking one approach would be to augment this=20
>>>ID?  I realize this is very late in what's=20
>>>been a long process for this ID (with my apologies to Dave).
>>>Nevertheless, finding a deployed system so=20
>>>similar, it might be worth capturing them both=20
>>>in the same document with a clear way to=20
>>>discriminate them (which would be more=20
>>>difficult to explain if they were in separate documents).
>>>
>>>I'm prepared to promptly contribute a proposed=20
>>>revision to this ID if folks are open to the idea.
>>>
>>>Comments?
>>
>>I'd prefer to converge on one mechanism, rather=20
>>than documenting that two similar (but=20
>>incompatible) variants exist, if possible.
>
>I guess I should say at this point that I am=20
>also aware of an implementation of my=20
>drafts;  though, just like Mike's report, this=20
>is a "hearsay" rather than a statement by the implementors themselves.
>
>Mike, what was the intent of the company you=20
>know of?  Did they intend to make a public specification?
>
>I find it surprising that they did something=20
>independently which is so close to what I created!
>--
>David Singer
>Apple/QuickTime


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



From avt-bounces@ietf.org Mon Jun 25 17:29: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 1I2w7W-0007ON-O7; Mon, 25 Jun 2007 17:29:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2w7V-0007M6-G6
	for avt@ietf.org; Mon, 25 Jun 2007 17:29:13 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2w7T-0002S0-5Y
	for avt@ietf.org; Mon, 25 Jun 2007 17:29:13 -0400
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:61327
	helo=[192.168.0.4])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1I2w7R-0007HO-ET; Mon, 25 Jun 2007 22:29:09 +0100
In-Reply-To: <38558EBB-DD0F-4D33-8AF9-2AB26C475F24@csperkins.org>
References: <38558EBB-DD0F-4D33-8AF9-2AB26C475F24@csperkins.org>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <E2470C64-F2FB-477B-B265-7E9C7F714465@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Working group last call: draft-ietf-avt-rtp-vorbis-05
Date: Mon, 25 Jun 2007 22:29:07 +0100
To: IETF AVT WG <avt@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: Roni Even <roni.even@polycom.co.il>, 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 11 Jun 2007, at 15:04, Colin Perkins wrote:
> This is to announce a working group last call on the RTP Payload  
> Format for Vorbis Encoded Audio (http://www.ietf.org/internet- 
> drafts/draft-ietf-avt-rtp-vorbis-05.txt). Please send any final  
> comments on this draft to the avt@ietf.org mailing list by 25th  
> June 2007. If no substantive comments are received by that time, we  
> will request the IESG consider this draft for publication as a  
> proposed standard RFC.

This working group last call has finished. There were a number of  
comments, which the -06 draft should address. We will reissue the  
working group last call when the updated draft becomes available.

-- 
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 Jun 25 18:15: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 1I2wpt-00040t-FI; Mon, 25 Jun 2007 18:15:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2wpp-0003st-Dy
	for avt@ietf.org; Mon, 25 Jun 2007 18:15:01 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2wpj-0003iK-JE
	for avt@ietf.org; Mon, 25 Jun 2007 18:14:57 -0400
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:61365
	helo=[192.168.0.4])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1I2wpf-00061k-7o; Mon, 25 Jun 2007 23:14:51 +0100
In-Reply-To: <46779487.5060308@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>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <85FF4F5B-138E-4788-8009-515DD4C17EBF@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, 25 Jun 2007 23:14:49 +0100
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: Chuck Harrison <cfharr@erols.com>, Boudani Ali <Ali.Boudani@thomson.net>,
	Dave Singer <singer@apple.com>,
	Le Dantec Claude <Claude.Le-Dantec@thomson.net>, 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

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.

Colin (as chair)






On 19 Jun 2007, at 09:32, Magnus Westerlund wrote:
> Dave Singer skrev:
>> At 14:18  +0200 18/06/07, Magnus Westerlund wrote:
>>> Chuck Harrison skrev:
>>>
>>>> So is the drift of the proposal currently on the table as
>>>> follows?
>>>>
>>>> - clockrate is considered as an SDP offer/answer parameter
>>>> - receiver MUST be capable of 90kHz
>>>> - sender MUST be capable of 90hKz - sender SHOULD use 90kHz
>>>> - receiver SHOULD accept other clockrates
>>>>
>>>
>>> I think so. I would prefer that the last SHOULD to be a MAY. That  
>>> makes it 90kHz is normative to support, you may support others if  
>>> you have reasons for it. Without good reasons, I don't see the  
>>> need to support other clockrates, thus I am in favor of only a MAY.
>> you cannot have anything other than a MUST for receivers if you  
>> want interoperability.  Unless I am required to use SIP and  
>> negotiate always.
>
> Yes, either you use negotiation through SIP or other ways. Other  
> ways include capability declarations from client towards RTSP  
> servers for example. But sure, there are cases when you like to  
> have this functionality for certain use cases. But I think it is  
> very reasonable in these cases to have the specific usage  
> requirements then to upgrade this requirement to a MUST. This is  
> something that people writing umbrella standards can do when they  
> need it. But the fact is that we do have some negotiation  
> possibilities in most cases, except broadcast/multicast scenarios.
>
> The reason I have this point of view is that you still haven't  
> explained why it is important for everyone to support something  
> else than 90kHz. Based on the lack of concrete motivation or  
> complaints from the industry of the missing support in other video  
> codecs, like H.264, I think this is a requirement of limited need.  
> And until you provide a more convincing case, that this is  
> something that really everyone needs, I think it is fine providing  
> one guaranteed interoperability point (90kHz) and then allow others.
>
> 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
> ----------------------------------------------------------------------

-- 
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 Jun 25 19:18:07 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 1I2xok-0007M1-Tu; Mon, 25 Jun 2007 19:17:58 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2xoj-0007Lq-BV
	for avt@ietf.org; Mon, 25 Jun 2007 19:17:57 -0400
Received: from porter.east.isi.edu ([65.114.168.19])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I2xoh-0004LV-K2
	for avt@ietf.org; Mon, 25 Jun 2007 19:17:57 -0400
Received: from [65.123.202.246] (wireless246.east.isi.edu [65.123.202.246])
	by porter.east.isi.edu (Postfix) with ESMTP id 2D6FD1C32
	for <avt@ietf.org>; Mon, 25 Jun 2007 19:17:52 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
To: IETF AVT Working Group <avt@ietf.org>
Message-Id: <88FE8678-4F2D-4C49-AC79-4520488E31BF@isi.edu>
References: <E1I18zy-0005i1-5x@stiedprstage1.ietf.org>
From: Ladan Gharai <ladan@isi.edu>
Subject: Fwd: [AVT] I-D ACTION:draft-ietf-avt-tfrc-profile-08.txt
Date: Mon, 25 Jun 2007 19:24:00 -0400
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6b519fb0ef66258f34533f52ff46aedf
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-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="===============0297332256=="
Errors-To: avt-bounces@ietf.org


--===============0297332256==
Content-Type: multipart/alternative; boundary=Apple-Mail-1-495693923


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

Dear Avt'ers:

Please read and comment on the latest version of  the draft "RTP with  
TCP Friendly Rate Control".

Main changes to the draft include:

1. Guidelines for how to deal signal RTCP bandwidth requirements in  
Section 7.
2. Use of 1 header extension for both RTT and send timestamps  
(Section 5).

thank you,
Ladan

Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Date: June 20, 2007 6:50:02 PM EDT
> To: i-d-announce@ietf.org
> Cc: avt@ietf.org
> Subject: [AVT] I-D ACTION:draft-ietf-avt-tfrc-profile-08.txt
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Audio/Video Transport Working  
> Group of the IETF.
>
> 	Title		: RTP with TCP Friendly Rate Control
> 	Author(s)	: L. Gharai
> 	Filename	: draft-ietf-avt-tfrc-profile-08.txt
> 	Pages		: 11
> 	Date		: 2007-6-20
> 	
> 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-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-tfrc-profile-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-tfrc-profile-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.
> Content-Type: text/plain
> Content-ID: <2007-6-20161306.I-D@ietf.org>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt


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

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">Dear Avt'ers:<DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Please read and comment on =
the latest version of=A0 the draft "RTP with TCP Friendly Rate =
Control".=A0=A0</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Main changes to the draft =
include:</DIV><DIV><BR class=3D"khtml-block-placeholder"></DIV><DIV>1. =
Guidelines for how to deal signal RTCP bandwidth requirements in Section =
7.</DIV><DIV>2. Use of 1 header extension for both RTT and send =
timestamps (Section 5).</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>thank =
you,</DIV><DIV>Ladan</DIV><DIV><DIV><BR><DIV>Begin forwarded =
message:</DIV><BR class=3D"Apple-interchange-newline"><BLOCKQUOTE =
type=3D"cite"><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><FONT face=3D"Helvetica" =
size=3D"3" color=3D"#000000" style=3D"font: 12.0px Helvetica; color: =
#000000"><B>From: </B></FONT><FONT face=3D"Helvetica" size=3D"3" =
style=3D"font: 12.0px Helvetica"><A =
href=3D"mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</A></FON=
T></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"3" =
color=3D"#000000" style=3D"font: 12.0px Helvetica; color: =
#000000"><B>Date: </B></FONT><FONT face=3D"Helvetica" size=3D"3" =
style=3D"font: 12.0px Helvetica">June 20, 2007 6:50:02 PM =
EDT</FONT></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><FONT face=3D"Helvetica" =
size=3D"3" color=3D"#000000" style=3D"font: 12.0px Helvetica; color: =
#000000"><B>To: </B></FONT><FONT face=3D"Helvetica" size=3D"3" =
style=3D"font: 12.0px Helvetica"><A =
href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</A></FONT></DI=
V><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"3" color=3D"#000000" =
style=3D"font: 12.0px Helvetica; color: #000000"><B>Cc: </B></FONT><FONT =
face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px Helvetica"><A =
href=3D"mailto:avt@ietf.org">avt@ietf.org</A></FONT></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"3" color=3D"#000000" =
style=3D"font: 12.0px Helvetica; color: #000000"><B>Subject: =
</B></FONT><FONT face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px =
Helvetica"><B>[AVT] I-D =
ACTION:draft-ietf-avt-tfrc-profile-08.txt</B></FONT></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV> <DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">A New =
Internet-Draft is available from the on-line Internet-Drafts<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">directories.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">This draft is a work item of the =
Audio/Video Transport Working Group of the IETF.</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>Title<SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN><SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>: RTP with TCP Friendly Rate Control</DIV><DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>Author(s)<SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>: L. Gharai</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>Filename<SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>: draft-ietf-avt-tfrc-profile-08.txt</DIV><DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>Pages<SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN><SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>: 11</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>Date<SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>: 2007-6-20</DIV><P =
style=3D"margin: 0.0px 0.0px 0.0px 0.0px; min-height: 14.0px"><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN><BR =
class=3D"khtml-block-placeholder"></P><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">This memo =
specifies how the TCP Friendly Rate Control (TFRC) of RTP</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>flows can be supported using the RTP/AVPF profile and the general =
RTP</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>header extension =
mechanism.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>AVPF feedback =
packets and RTP header</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>extensions are defined to =
support the exchange of control information</DIV><DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>between RTP TFRC senders =
and receivers. TFRC is an equation based</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>congestion control scheme =
for unicast flows operating in a best</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>effort Internet =
environment.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">A URL for this Internet-Draft is:</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-avt-tfrc-profile-08=
.txt">http://www.ietf.org/internet-drafts/draft-ietf-avt-tfrc-profile-08.t=
xt</A></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">To remove yourself from the I-D Announcement list, =
send a message to<SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DI=
V style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"mailto:i-d-announce-request@ietf.org">i-d-announce-request@ietf.or=
g</A> with the word unsubscribe in the body of<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">the =
message.<SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">You can also visit <A =
href=3D"https://www1.ietf.org/mailman/listinfo/I-D-announce">https://www1.=
ietf.org/mailman/listinfo/I-D-announce</A><SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">to =
change your subscription settings.</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Internet-Drafts are also =
available by anonymous FTP. Login with the<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">username =
"anonymous" and a password of your e-mail address. After<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">logging =
in, type "cd internet-drafts" and then<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">"get =
draft-ietf-avt-tfrc-profile-08.txt".</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">A list of Internet-Drafts =
directories can be found in</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</=
A><SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">or <A =
href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf=
/1shadow-sites.txt</A></DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Internet-Drafts can also be =
obtained by e-mail.</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Send a message to:</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN><A =
href=3D"mailto:mailserv@ietf.org">mailserv@ietf.org</A>.</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">In the body type:</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>"FILE =
/internet-drafts/draft-ietf-avt-tfrc-profile-08.txt".</DIV><P =
style=3D"margin: 0.0px 0.0px 0.0px 0.0px; min-height: 14.0px"><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN><BR =
class=3D"khtml-block-placeholder"></P><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">NOTE:<SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>The mail =
server at ietf.org can return the document in</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>MIME-encoded form by using the =
"mpack" utility.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>To use =
this</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>feature, insert the command =
"ENCODING mime" before the "FILE"</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>command.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>To =
decode the response(s), you will need "munpack" or</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>a MIME-compliant mail =
reader.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>Different =
MIME-compliant mail readers</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>exhibit =
different behavior, especially when dealing with</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>"multipart" MIME messages (i.e. =
documents which have been split</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>up into =
multiple messages), so check your local documentation on</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>how to manipulate these =
messages.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Below is the data which will enable a MIME compliant =
mail reader</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">implementation to automatically =
retrieve the ASCII version of the</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">Internet-Draft.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Content-Type: =
text/plain</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Content-ID: &lt;<A =
href=3D"mailto:2007-6-20161306.I-D@ietf.org">2007-6-20161306.I-D@ietf.org<=
/A>&gt;</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; =
">_______________________________________________</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Audio/Video Transport Working Group</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"mailto:avt@ietf.org">avt@ietf.org</A></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"https://www1.ietf.org/mailman/listinfo/avt">https://www1.ietf.org/=
mailman/listinfo/avt</A></DIV> =
</BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>=

--Apple-Mail-1-495693923--


--===============0297332256==
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

--===============0297332256==--




From avt-bounces@ietf.org Tue Jun 26 04:04: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 1I3621-00039S-84; Tue, 26 Jun 2007 04:04:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I361z-00039F-If
	for avt@ietf.org; Tue, 26 Jun 2007 04:04:11 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I361T-0002GR-7h
	for avt@ietf.org; Tue, 26 Jun 2007 04:04:11 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	2D8B120083; Tue, 26 Jun 2007 10:03:38 +0200 (CEST)
X-AuditID: c1b4fb3e-ae831bb0000007e1-31-4680c85a2980
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	100DF206F2; Tue, 26 Jun 2007 10:03:38 +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, 26 Jun 2007 10:03:37 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Jun 2007 10:03:37 +0200
Message-ID: <4680C859.8050900@ericsson.com>
Date: Tue, 26 Jun 2007 10:03:37 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
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>
In-Reply-To: <85FF4F5B-138E-4788-8009-515DD4C17EBF@csperkins.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Jun 2007 08:03:37.0514 (UTC)
	FILETIME=[802D40A0:01C7B7C8]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: Chuck Harrison <cfharr@erols.com>, Boudani Ali <Ali.Boudani@thomson.net>,
	Dave Singer <singer@apple.com>,
	Le Dantec Claude <Claude.Le-Dantec@thomson.net>, IETF AVT WG <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

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

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



From avt-bounces@ietf.org Tue Jun 26 04: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 1I36CZ-0002p7-2G; Tue, 26 Jun 2007 04:15:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I36CX-0002p2-PP
	for avt@ietf.org; Tue, 26 Jun 2007 04:15:05 -0400
Received: from dmzraw3.extranet.thmulti.com ([141.11.234.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I36CE-0003PA-OC
	for avt@ietf.org; Tue, 26 Jun 2007 04:15:05 -0400
Received: from boulvss2.eu.thmulti.com (proxy.thmulti.com [141.11.234.62])
	by dmzraw3.extranet.thmulti.com (Postfix) with ESMTP id 7E9E029A8;
	Tue, 26 Jun 2007 08:14:41 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
	by boulvss2.eu.thmulti.com (Postfix) with ESMTP id B6CB51279;
	Tue, 26 Jun 2007 08:22:18 +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 07046-01-9; Tue, 26 Jun 2007 08:22:17 +0000 (GMT)
Received: from boulsmailfe01.eu.thmulti.com (boulsmailfe01.eu.thmulti.com
	[141.11.192.237])
	by boulvss2.eu.thmulti.com (Postfix) with ESMTP id DF9991278;
	Tue, 26 Jun 2007 08:22:17 +0000 (GMT)
Received: from rennsmail05.eu.thmulti.com ([141.11.159.141]) by
	boulsmailfe01.eu.thmulti.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Jun 2007 10:14:40 +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] Working group last call: JPEG-2000 payload format
Date: Tue, 26 Jun 2007 10:14:38 +0200
Message-ID: <7634542FB03DC747813D67560802AEEDB0A5EE@rennsmail05.eu.thmulti.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Working group last call: JPEG-2000 payload format
Thread-Index: Ace3yIcx8OH243zlRfK3s8mk2bbLegAAO5gA
From: "Boudani Ali" <Ali.Boudani@thomson.net>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>,
	"Colin Perkins" <csp@csperkins.org>
X-OriginalArrivalTime: 26 Jun 2007 08:14:40.0350 (UTC)
	FILETIME=[0B41FFE0:01C7B7CA]
X-Virus-Scanned: amavisd-new at thomson.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: Chuck Harrison <cfharr@erols.com>, Dave Singer <singer@apple.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

That seems fine to me.=20

-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]=20
Sent: mardi 26 juin 2007 10:04
To: Colin Perkins
Cc: Dave Singer; Chuck Harrison; Boudani Ali; Le Dantec Claude; IETF AVT
WG
Subject: Re: [AVT] Working group last call: JPEG-2000 payload format

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:
>=20
> - Senders and receivers MUST support a 90kHz RTP timestamp rate, and
MAY
>   support other rates.
>=20
> - 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.
>=20
> - The timestamp rate MUST be negotiated. The offer/answer
considerations
>   should explain how this is done.
>=20
> - 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.:
>=20
>     m=3Dvideo 5004 RTP/AVP 98 99
>     a=3Drtpmap:98 jpeg2000/90000
>     a=3Drtpmap:99 jpeg2000/27000000
>=20
>   allowing graceful fallback to 90kHz if the receiver doesn't support=20
> the high
>   rate.
>=20
> To check the consensus, please reply to this message by the end of
this=20
> week, stating if you agree or disagree with this proposal, and giving=20
> your reasons. Please do this even if you believe you have already
stated=20
> your preference.
>=20

I am fine with this. However, I think the SDP example should switch the=20
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,=20
change the m=3D line to:
m=3Dvideo 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
----------------------------------------------------------------------

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



From avt-bounces@ietf.org Tue Jun 26 05:02: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 1I36w4-0008TJ-39; Tue, 26 Jun 2007 05:02:08 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I36w1-0008T0-ES
	for avt@ietf.org; Tue, 26 Jun 2007 05:02:05 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I36w0-0005Ff-Vk
	for avt@ietf.org; Tue, 26 Jun 2007 05:02:05 -0400
Received: from relay5.apple.com (relay5.apple.com [17.128.113.35])
	by mail-out4.apple.com (Postfix) with ESMTP id 232DCA7D93A;
	Tue, 26 Jun 2007 02:01:16 -0700 (PDT)
Received: from relay5.apple.com (unknown [127.0.0.1])
	by relay5.apple.com (Symantec Mail Security) with ESMTP id 1107529C002; 
	Tue, 26 Jun 2007 02:01:16 -0700 (PDT)
X-AuditID: 11807123-a5020bb000000a55-e1-4680d5db1131
Received: from [17.202.35.52] (int-si-a.apple.com [17.128.113.41])
	by relay5.apple.com (Apple SCV relay) with ESMTP id 786B330400B;
	Tue, 26 Jun 2007 02:01:14 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p062408a3c2a679e3bba1@[17.202.35.52]>
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>
Date: Tue, 26 Jun 2007 12:00:55 +0300
To: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Colin Perkins <csp@csperkins.org>
From: Dave Singer <singer@apple.com>
Subject: Re: [AVT] Working group last call: JPEG-2000 payload format
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
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

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



From avt-bounces@ietf.org Tue Jun 26 05:22: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 1I37G8-0002Xy-4e; Tue, 26 Jun 2007 05:22:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I36JB-0000bi-NT
	for avt@ietf.org; Tue, 26 Jun 2007 04:21:57 -0400
Received: from dmzraw4.extranet.thmulti.com ([141.11.234.72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I36J6-0005aC-3u
	for avt@ietf.org; Tue, 26 Jun 2007 04:21:57 -0400
Received: from boulvss2.eu.thmulti.com (proxy.thmulti.com [141.11.234.62])
	by dmzraw4.extranet.thmulti.com (Postfix) with ESMTP id 6E5662457;
	Tue, 26 Jun 2007 08:21:38 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
	by boulvss2.eu.thmulti.com (Postfix) with ESMTP id 9E9EA1278;
	Tue, 26 Jun 2007 08:29:15 +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 28793-06-20; Tue, 26 Jun 2007 08:29:14 +0000 (GMT)
Received: from boulsmailfe01.eu.thmulti.com (boulsmailfe01.eu.thmulti.com
	[141.11.192.237])
	by boulvss2.eu.thmulti.com (Postfix) with ESMTP id 3DDB311C9;
	Tue, 26 Jun 2007 08:29:14 +0000 (GMT)
Received: from rennsmail04.eu.thmulti.com ([141.11.159.175]) by
	boulsmailfe01.eu.thmulti.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Jun 2007 10:21:36 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [AVT] Working group last call: JPEG-2000 payload format
Date: Tue, 26 Jun 2007 10:21:32 +0200
Message-ID: <8BB9F3CCFFE936478EF04BF93615A9BA6F2B55@rennsmail04.eu.thmulti.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AVT] Working group last call: JPEG-2000 payload format
thread-index: Ace3yJjVZcu8tVccRXmEEVyZFSGKFgAAfMtA
X-Priority: 1
Priority: Urgent
Importance: high
From: "Le Dantec Claude" <Claude.Le-Dantec@thomson.net>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>,
	"Colin Perkins" <csp@csperkins.org>, "Dave Singer" <singer@apple.com>,
	"Chuck Harrison" <cfharr@erols.com>,
	"Boudani Ali" <Ali.Boudani@thomson.net>, "IETF AVT WG" <avt@ietf.org>
X-OriginalArrivalTime: 26 Jun 2007 08:21:36.0498 (UTC)
	FILETIME=[034D2520:01C7B7CB]
X-Virus-Scanned: amavisd-new at thomson.net
X-Spam-Score: 0.1 (/)
X-Scan-Signature: be922d419820e291bde1362184dc32fd
X-Mailman-Approved-At: Tue, 26 Jun 2007 05:22:51 -0400
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1605046079=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1605046079==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7B7CB.02DDF5A4"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7B7CB.02DDF5A4
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear All,

An email mentionning my address has been sent by mistake some weeks ago
.
As I am still receiving associated emails, please delete my name from
your distribution list.

Best regards,

Claude Le Dantec
=20

-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]=20
Sent: mardi 26 juin 2007 10:04
To: Colin Perkins
Cc: Dave Singer; Chuck Harrison; Boudani Ali; Le Dantec Claude; IETF AVT
WG
Subject: Re: [AVT] Working group last call: JPEG-2000 payload format

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:
>=20
> - Senders and receivers MUST support a 90kHz RTP timestamp rate, and
MAY
>   support other rates.
>=20
> - 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.
>=20
> - The timestamp rate MUST be negotiated. The offer/answer
considerations
>   should explain how this is done.
>=20
> - 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.:
>=20
>     m=3Dvideo 5004 RTP/AVP 98 99
>     a=3Drtpmap:98 jpeg2000/90000
>     a=3Drtpmap:99 jpeg2000/27000000
>=20
>   allowing graceful fallback to 90kHz if the receiver doesn't support=20
> the high
>   rate.
>=20
> To check the consensus, please reply to this message by the end of=20
> this week, stating if you agree or disagree with this proposal, and=20
> giving your reasons. Please do this even if you believe you have=20
> already stated your preference.
>=20

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=3D line to:
m=3Dvideo 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
----------------------------------------------------------------------

------_=_NextPart_001_01C7B7CB.02DDF5A4
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.7650.5">
<TITLE>RE: [AVT] Working group last call: JPEG-2000 payload =
format</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Dear =
All,</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">An email mentionning =
my address has been sent by mistake</FONT><FONT SIZE=3D2 =
FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">some weeks ago =
.</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">As I am still =
receiving</FONT> <FONT SIZE=3D2 FACE=3D"Arial">associated</FONT> <FONT =
SIZE=3D2 FACE=3D"Arial">emails,<B> please delete my name from your =
distribution list</B>.</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Best =
regards,</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Claude Le =
Dantec</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">-----Original =
Message-----</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">From: Magnus =
Westerlund [</FONT></SPAN><A =
HREF=3D"mailto:magnus.westerlund@ericsson.com"><SPAN =
LANG=3D"fr"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">mailto:magnus.westerlund@ericsson.com</FONT></U></SPAN></A=
><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">] </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Sent: mardi 26 juin =
2007 10:04</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">To: Colin =
Perkins</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Cc: Dave Singer; =
Chuck Harrison; Boudani Ali; Le Dantec Claude; IETF AVT WG</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Subject: Re: [AVT] =
Working group last call: JPEG-2000 payload format</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Colin Perkins =
skrev:</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; Wrapping up, I =
believe the rough consensus is that the JPEG-2000 draft </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; should be =
updated to allow non-90kHz timestamp rates, as follows:</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; - Senders and =
receivers MUST support a 90kHz RTP timestamp rate, and MAY</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&nbsp;&nbsp; =
support other rates.</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; - Senders =
SHOULD use 90kHz timestamp where possible, and the draft needs =
to</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&nbsp;&nbsp; be =
updated to include strong guidance on choosing the timestamp rate, =
and</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&nbsp;&nbsp; the =
implications of using a rate other than 90kHz.</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; - The timestamp =
rate MUST be negotiated. The offer/answer considerations</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&nbsp;&nbsp; =
should explain how this is done.</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; - Senders that =
wish to use a non-90kHz rate SHOULD also offer the same </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
stream</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&nbsp;&nbsp; =
using a 90kHz timestamp rate, with a different RTP payload type, =
e.g.:</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;&nbsp;&nbsp;&nbsp;&nbsp; m=3Dvideo 5004 RTP/AVP 98 =
99</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;&nbsp;&nbsp;&nbsp;&nbsp; a=3Drtpmap:98 =
jpeg2000/90000</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;&nbsp;&nbsp;&nbsp;&nbsp; a=3Drtpmap:99 =
jpeg2000/27000000</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&nbsp;&nbsp; =
allowing graceful fallback to 90kHz if the receiver doesn't support =
</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; the =
high</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&nbsp;&nbsp; =
rate.</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; To check the =
consensus, please reply to this message by the end of </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; this week, =
stating if you agree or disagree with this proposal, and </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; giving your =
reasons. Please do this even if you believe you have </FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; already stated =
your preference.</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">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=3D line =
to:</FONT></SPAN></P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">m=3Dvideo 5004 =
RTP/AVP 99 98</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Cheers</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Magnus =
Westerlund</FONT></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">IETF Transport Area =
Director &amp; TSVWG Chair</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">----------------------------------------------------------=
------------</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Multimedia =
Technologies, Ericsson Research EAB/TVM/M</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">----------------------------------------------------------=
------------</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Ericsson =
AB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; | Phone +46 8 4048287</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Torshamsgatan =
23&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
Fax&nbsp;&nbsp; +46 8 7575550</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">S-164 80 Stockholm, =
Sweden | mailto: magnus.westerlund@ericsson.com</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 =
FACE=3D"Arial">----------------------------------------------------------=
------------</FONT></SPAN>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7B7CB.02DDF5A4--


--===============1605046079==
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

--===============1605046079==--




From avt-bounces@ietf.org Tue Jun 26 07:01: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 1I38n4-0006hs-1N; Tue, 26 Jun 2007 07:00:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I38n2-0006gR-Cu
	for avt@ietf.org; Tue, 26 Jun 2007 07:00:56 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I38mx-0002LR-7p
	for avt@ietf.org; Tue, 26 Jun 2007 07:00:56 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:57102)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1I38mv-0002Uz-63; Tue, 26 Jun 2007 12:00:49 +0100
In-Reply-To: <A5148FAE-9197-4824-87C4-EF54767552F3@cisco.com>
References: <A5148FAE-9197-4824-87C4-EF54767552F3@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <18CAE473-3A37-49E0-8F68-CC30629DB2EA@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Tue, 26 Jun 2007 12:00:47 +0100
To: David McGrew <mcgrew@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: Cullen Jennings <fluffy@cisco.com>, Roni Even <roni.even@polycom.co.il>,
	tom.taylor@rogers.com, AVT <avt@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: [AVT] Re: TLS-SRTP internet draft as a WG item in AVT
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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 David,

What milestone(s) do you see this work adding to the AVT charter, if  
accepted?

Colin




On 20 Jun 2007, at 21:54, David McGrew wrote:
> Hi Colin, Roni, and Tom,
>
> I would like to ask that draft-mcgrew-tls-srtp be taken up as a  
> working group action item in AVT, as part the plan for carrying  
> forward the RTPSEC work (as per Cullen's email of May 11 to the  
> rtpsec list).   I would like to continue on as an author of this  
> work, and Eric as agreed to do the same.  There are a small number  
> of minor open issues which I expect can be wrapped up quickly:
>
> 1.  The draft needs to be clarified so that, in the Symmetric RTP  
> case, only one handshake is needed.
>
> 2.  Section 3.6.2.1 needs to be resolved to either decide on a  
> "symmetry breaking" rule or not.  It may be desirable to have such  
> a rule to handle cases in which the signaling system can't tell a  
> device which should act as client and which should act as server.    
> This would allow opportunistic probing, i.e. a TLS-SRTP  
> implementation could attempt to find out whether another RTP  
> implementation supports TLS-SRTP, absent any help from signaling.
>
> 3.  The "single DTLS session per SRTP session" issue needs to be  
> decided, and Appendix A should then be removed from the draft.
>
> 4.  It should be decided to use, or not to use the "TLS Extractor",  
> and Section 3.3 should be rewritten accordingly.
>
> 5.  The duplicate list of srtp profiles needs to be eliminated.
>
> Best regards,
>
> David
>
> --
>
> p.s. - here's the AVT-specific part of Cullen note, so that you  
> don't need to dig it out of your mailbox: "AVT - Describe how DTLS  
> is used to key SRTP and how SRTP is used in combination with DTLS.  
> This includes the issues of multiplexing DTLS and SRTP on one port.  
> draft-mcgrew-tls-srtp will be the starting draft for this."



-- 
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 Jun 26 13:26: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 1I3EoB-0006oy-Uy; Tue, 26 Jun 2007 13:26:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3EoA-0006on-Qe
	for avt@ietf.org; Tue, 26 Jun 2007 13:26:30 -0400
Received: from web42109.mail.mud.yahoo.com ([209.191.86.242])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1I3Enq-0004go-9M
	for avt@ietf.org; Tue, 26 Jun 2007 13:26:30 -0400
Received: (qmail 16308 invoked by uid 60001); 26 Jun 2007 13:26:08 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=QRJvoCroNqDr0sQFld8wko1RL/gFUO2EshLM304SP2XVDxZLF/NkNReDiuXIcOhcZSPGdi69OOvY25lp8/9l+/Ko0s6ABOTPqx+SHDj0dGOJO/uTemdrO0XlO+X/zi4Fgt2jBPqwKvNFzchbtGSc9hIyis6hEui1xz+ZIJhsVZQ=;
X-YMail-OSG: BMNhjfIVM1mp8pTwMcw14qHV3u0PDIsN7xfZ3GXO78NIXg_inNUimoXvWfxOoMimVfkEdICWNdZX2Kj2qx_8p6ggnK_5LEUueaDRq0B1hYel0D4DxvwlIJWuQP2fJA--
Received: from [203.126.136.220] by web42109.mail.mud.yahoo.com via HTTP;
	Tue, 26 Jun 2007 06:26:08 PDT
Date: Tue, 26 Jun 2007 06:26:08 -0700 (PDT)
From: sona chalam <sona_kk@yahoo.com>
To: IETF AVT WG <avt@ietf.org>
In-Reply-To: <p062408a3c2a679e3bba1@[17.202.35.52]>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <317911.16047.qm@web42109.mail.mud.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Subject: [AVT] Identifying a Frame from the NAL units
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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
 
How to identify a start and end of  Frame in H264.
 
 
In RTSP streaming session I will get the SPS and PPS
NAL in sdp itself.
 
And in the  RTP payload has either the VCL
NAlunits(Nal type 1 or 5) or the Filler data
filler_data(Nal type 12). 
 
How to identify the Start and End of Frame from the
NALs?.






      ____________________________________________________________________________________
Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center.
http://autos.yahoo.com/green_center/ 

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



From avt-bounces@ietf.org Tue Jun 26 14:01: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 1I3FM4-0006VY-NC; Tue, 26 Jun 2007 14:01:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3FM3-0006Tv-JE
	for avt@ietf.org; Tue, 26 Jun 2007 14:01:31 -0400
Received: from mout.perfora.net ([74.208.4.194])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3FLm-0001ad-Fw
	for avt@ietf.org; Tue, 26 Jun 2007 14:01:31 -0400
Received: from [71.136.175.166] (helo=TBT-Laptop.newtbt.com)
	by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis),
	id 0MKpCa-1I3FLk1Et3-0001bR; Tue, 26 Jun 2007 14:01:14 -0400
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 26 Jun 2007 10:55:55 -0700
To: IETF AVT <avt@ietf.org>
From: Michael A Dolan <md.1@newtbt.com>
Subject: Re: [AVT] Registration procedures for RTP header extensions
In-Reply-To: <467A32E0.9030606@ericsson.com>
References: <0A609728-183A-4181-B5A8-DA35BBAE09E9@cisco.com>
	<4678EEC2.9000702@ericsson.com>
	<0B0FC93B-8BF6-4CB3-AE4E-CB83C26AFD12@cisco.com>
	<467A32E0.9030606@ericsson.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <0MKpCa-1I3FLk1Et3-0001bR@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX18ebV9FexZ+55liMbI2oa6da4adU6NgMdCzQ3u
	st55Gtj31rVT7624Y/p0dGQm48KqY9y7NboAIphc/VG6Uj0wDR
	Z9rUUUfC7hU4MUIisDgWw==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org


>>>However, the reality is that header extensions (16-bit field) have 
>>>been totally unmanaged and been in FCFS since day one.
>>interesting - which extension numbers are defined?
>Well, that is the issue. I don't have any bodies/specifications that 
>I can point at. But I have herd rumors about people using them, by 
>simply picking a random number.

And, more interesting - non-static definitions, since there is also 
no requirement today that it be entirely a constant.

Regards,

         Mike


At 01:12 AM 6/21/2007, Magnus Westerlund wrote:
>Cullen Jennings skrev:
>>
>>On Jun 20, 2007, at 2:09 AM, Magnus Westerlund wrote:
>>
>>>Hi Cullen,
>>>
>>>Sorry, but I get confused by this message. Which issue are you discussing?
>>>
>>>A. The policy for AVP (and by inheritance the other profiles) for 
>>>the first 16-bits in the header extension. Which currently RFC 
>>>3551 says should be managed but doesn't define a policy or a registry for.
>>>
>>>B. Header extensions signaled using the mechanism defined in 
>>>draft-ietf-avt-rtp-hdrext. Which currently is the equivalent of 
>>>FCFS and with the addition of a registry for keeping track of RFC defined ones.
>>>
>>>I think you are talking about B and like to have confirmation of 
>>>the WG be okay with this.
>>Yes - I am talking about B but A is effectively being replaced by B 
>>for all practical purposes so they are closely related.
>
>Thanks for the clarification.
>
>>>
>>>In the case of B my personal opinion is the following:
>>>
>>>1. Per design using URIs as signalling names, this is impossible 
>>>to control. The only way of fix this would be to change the 
>>>identifier used for a mechanism into something a registration can 
>>>keep track and assign. However that also increases the chance of 
>>>borrowing a name without registering creating issues.
>>I was not really asking about if we should use URI or not, I was 
>>looking for opinion on what level of control the WG thought they 
>>should have from 1 to 4 - once we have a better idea of that, we 
>>can propose an appropriate mechanism. Thoughts on this?
>
>My personal opinion is that for the URN space there should be at 
>least expert review and specification required. We might consider 
>that the bar for what is considered a specification is. I think it 
>must be above a white paper but any industry forum or standards body 
>that produce a permanent documents should be okay.  That way the 
>ones existing in the formal registry are available to read. They 
>will also receive some sanity check through the expert review. Going 
>further to require an RFC only reduced the utility of the registry 
>as a common gathering point for standardized solutions.
>
>>
>>>
>>>2. I think the IANA section as currently written needs to be 
>>>improved it is not easy to understand for someone desiring to 
>>>register a name in the URN space that it is under specification 
>>>required. I think a better separation of what is the rule for 
>>>registration within the space and the details needed to have the 
>>>URN space itself created is needed.
>>>
>>>I think there might be some benefit in changing the rules for the 
>>>URN space to Expert Review and then have the Expert reviewer 
>>>guidelines require a specification as one of the criteria for acceptance.
>>>
>>>However, the reality is that header extensions (16-bit field) have 
>>>been totally unmanaged and been in FCFS since day one.
>>interesting - which extension numbers are defined?
>
>Well, that is the issue. I don't have any bodies/specifications that 
>I can point at. But I have herd rumors about people using them, by 
>simply picking a random number.
>
>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


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



From avt-bounces@ietf.org Tue Jun 26 17:05: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 1I3IE9-000358-WC; Tue, 26 Jun 2007 17:05:34 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3IE8-000351-Mh
	for avt@ietf.org; Tue, 26 Jun 2007 17:05:32 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3IE8-0004KL-DC
	for avt@ietf.org; Tue, 26 Jun 2007 17:05:32 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 26 Jun 2007 14:05:31 -0700
X-IronPort-AV: i="4.16,464,1175497200"; 
	d="scan'208"; a="5041296:sNHT206054280"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5QL5VCB020366; 
	Tue, 26 Jun 2007 14:05:31 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l5QL5QlA003941;
	Tue, 26 Jun 2007 21:05:28 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); 
	Tue, 26 Jun 2007 14:05:14 -0700
Received: from [10.32.254.213] ([10.32.254.213]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Jun 2007 14:05:14 -0700
In-Reply-To: <18CAE473-3A37-49E0-8F68-CC30629DB2EA@csperkins.org>
References: <A5148FAE-9197-4824-87C4-EF54767552F3@cisco.com>
	<18CAE473-3A37-49E0-8F68-CC30629DB2EA@csperkins.org>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <BC4EE9F5-5F44-4BCC-9CA2-4CB3E684DF71@cisco.com>
Content-Transfer-Encoding: 7bit
From: David McGrew <mcgrew@cisco.com>
Date: Tue, 26 Jun 2007 14:05:27 -0700
To: Colin Perkins <csp@csperkins.org>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 26 Jun 2007 21:05:14.0185 (UTC)
	FILETIME=[B0C55B90:01C7B835]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2350; t=1182891931;
	x=1183755931; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mcgrew@cisco.com;
	z=From:=20David=20McGrew=20<mcgrew@cisco.com>
	|Subject:=20Re=3A=20TLS-SRTP=20internet=20draft=20as=20a=20WG=20item=20in
	=20AVT |Sender:=20;
	bh=pgU55tS+0Lkyu5PCsAH/J3KA17kxdjTxkbwWYsJpRsc=;
	b=gmLnRrqpfJ0IsDJflKivY4fquIO88J9wtg3NkvlWz85g8PtyRr4KF3GCcOuycdDl18WHjDDf
	QNUVS2EkezACyADiA8vvMzFIy59S15jV1h2nmUHd66fvkBhnDprARApB;
Authentication-Results: sj-dkim-2; header.From=mcgrew@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: Cullen Jennings <fluffy@cisco.com>, Roni Even <roni.even@polycom.co.il>,
	tom.taylor@rogers.com, AVT <avt@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: [AVT] Re: TLS-SRTP internet draft as a WG item in AVT
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi Colin,

how does this milestone sound?  "December 2007 Submit TLS-SRTP for  
Proposed Standard"   Perhaps I'm aggressive in expecting us to have  
the draft ready before the Vancouver meeting; we could push it back  
to March 2008.

David

On Jun 26, 2007, at 4:00 AM, Colin Perkins wrote:

> Hi David,
>
> What milestone(s) do you see this work adding to the AVT charter,  
> if accepted?
>
> Colin
>
>
>
>
> On 20 Jun 2007, at 21:54, David McGrew wrote:
>> Hi Colin, Roni, and Tom,
>>
>> I would like to ask that draft-mcgrew-tls-srtp be taken up as a  
>> working group action item in AVT, as part the plan for carrying  
>> forward the RTPSEC work (as per Cullen's email of May 11 to the  
>> rtpsec list).   I would like to continue on as an author of this  
>> work, and Eric as agreed to do the same.  There are a small number  
>> of minor open issues which I expect can be wrapped up quickly:
>>
>> 1.  The draft needs to be clarified so that, in the Symmetric RTP  
>> case, only one handshake is needed.
>>
>> 2.  Section 3.6.2.1 needs to be resolved to either decide on a  
>> "symmetry breaking" rule or not.  It may be desirable to have such  
>> a rule to handle cases in which the signaling system can't tell a  
>> device which should act as client and which should act as  
>> server.   This would allow opportunistic probing, i.e. a TLS-SRTP  
>> implementation could attempt to find out whether another RTP  
>> implementation supports TLS-SRTP, absent any help from signaling.
>>
>> 3.  The "single DTLS session per SRTP session" issue needs to be  
>> decided, and Appendix A should then be removed from the draft.
>>
>> 4.  It should be decided to use, or not to use the "TLS  
>> Extractor", and Section 3.3 should be rewritten accordingly.
>>
>> 5.  The duplicate list of srtp profiles needs to be eliminated.
>>
>> Best regards,
>>
>> David
>>
>> --
>>
>> p.s. - here's the AVT-specific part of Cullen note, so that you  
>> don't need to dig it out of your mailbox: "AVT - Describe how DTLS  
>> is used to key SRTP and how SRTP is used in combination with DTLS.  
>> This includes the issues of multiplexing DTLS and SRTP on one  
>> port. draft-mcgrew-tls-srtp will be the starting draft for this."
>
>
>
> -- 
> 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 Jun 26 18:18: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 1I3JMy-0000d5-CS; Tue, 26 Jun 2007 18:18:44 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3JMx-0000cD-21
	for avt@ietf.org; Tue, 26 Jun 2007 18:18:43 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3JMw-0001yZ-OQ
	for avt@ietf.org; Tue, 26 Jun 2007 18:18:42 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 26 Jun 2007 15:14:58 -0700
X-IronPort-AV: i="4.16,464,1175497200"; 
	d="scan'208"; a="172602287:sNHT28919551122"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l5QMEwk9025603; 
	Tue, 26 Jun 2007 15:14:58 -0700
Received: from [192.168.4.177] (sjc-fluffy-vpn1.cisco.com [10.25.236.82])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with SMTP id l5QMEump013796;
	Tue, 26 Jun 2007 22:14:56 GMT
In-Reply-To: <BC4EE9F5-5F44-4BCC-9CA2-4CB3E684DF71@cisco.com>
References: <A5148FAE-9197-4824-87C4-EF54767552F3@cisco.com>
	<18CAE473-3A37-49E0-8F68-CC30629DB2EA@csperkins.org>
	<BC4EE9F5-5F44-4BCC-9CA2-4CB3E684DF71@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <DA7BAB1B-335A-4193-BE13-8EB565C7DD47@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Date: Tue, 26 Jun 2007 15:13:59 -0700
To: David McGrew ((mcgrew)) <mcgrew@cisco.com>
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2797; t=1182896098;
	x=1183760098; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fluffy@cisco.com;
	z=From:=20Cullen=20Jennings=20<fluffy@cisco.com>
	|Subject:=20Re=3A=20TLS-SRTP=20internet=20draft=20as=20a=20WG=20item=20in
	=20AVT |Sender:=20;
	bh=1ebVVlOLyCu6yGwcvQAWrhibQYzBfzcomR1s2o+jj0g=;
	b=a3VLfDy15UAesdO0MfACjff2olyoG8mXzFxqz28ovAifwuW/Zaw4mFkVZVouk0lAsTFaqvcA
	9hcSnbMbWJcWZxxoT/YKF4Dou7n4OzlnDMi0RKJI19EUR5ODRmbsElGg;
Authentication-Results: sj-dkim-3; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: Roni Even <roni.even@polycom.co.il>, AVT <avt@ietf.org>,
	tom.taylor@rogers.com, "Dan Wing \(dwing\)" <dwing@cisco.com>,
	Colin Perkins <csp@csperkins.org>
Subject: [AVT] Re: TLS-SRTP internet draft as a WG item in AVT
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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 no problem with that milestone if that is what you decide on ...

One question about it - would calling it "DTLS-SRTP" be better than  
"TLS-SRTP"? I don't care but if we were going to change the name,  
this would be the right time to do that.

Cullen <with my AD hat on>


On Jun 26, 2007, at 2:05 PM, David McGrew ((mcgrew)) wrote:

> Hi Colin,
>
> how does this milestone sound?  "December 2007 Submit TLS-SRTP for
> Proposed Standard"   Perhaps I'm aggressive in expecting us to have
> the draft ready before the Vancouver meeting; we could push it back
> to March 2008.
>
> David
>
> On Jun 26, 2007, at 4:00 AM, Colin Perkins wrote:
>
> > Hi David,
> >
> > What milestone(s) do you see this work adding to the AVT charter,
> > if accepted?
> >
> > Colin
> >
> >
> >
> >
> > On 20 Jun 2007, at 21:54, David McGrew wrote:
> >> Hi Colin, Roni, and Tom,
> >>
> >> I would like to ask that draft-mcgrew-tls-srtp be taken up as a
> >> working group action item in AVT, as part the plan for carrying
> >> forward the RTPSEC work (as per Cullen's email of May 11 to the
> >> rtpsec list).   I would like to continue on as an author of this
> >> work, and Eric as agreed to do the same.  There are a small number
> >> of minor open issues which I expect can be wrapped up quickly:
> >>
> >> 1.  The draft needs to be clarified so that, in the Symmetric RTP
> >> case, only one handshake is needed.
> >>
> >> 2.  Section 3.6.2.1 needs to be resolved to either decide on a
> >> "symmetry breaking" rule or not.  It may be desirable to have such
> >> a rule to handle cases in which the signaling system can't tell a
> >> device which should act as client and which should act as
> >> server.   This would allow opportunistic probing, i.e. a TLS-SRTP
> >> implementation could attempt to find out whether another RTP
> >> implementation supports TLS-SRTP, absent any help from signaling.
> >>
> >> 3.  The "single DTLS session per SRTP session" issue needs to be
> >> decided, and Appendix A should then be removed from the draft.
> >>
> >> 4.  It should be decided to use, or not to use the "TLS
> >> Extractor", and Section 3.3 should be rewritten accordingly.
> >>
> >> 5.  The duplicate list of srtp profiles needs to be eliminated.
> >>
> >> Best regards,
> >>
> >> David
> >>
> >> --
> >>
> >> p.s. - here's the AVT-specific part of Cullen note, so that you
> >> don't need to dig it out of your mailbox: "AVT - Describe how DTLS
> >> is used to key SRTP and how SRTP is used in combination with DTLS.
> >> This includes the issues of multiplexing DTLS and SRTP on one
> >> port. draft-mcgrew-tls-srtp will be the starting draft for this."
> >
> >
> >
> > --
> > 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 Jun 26 19:35: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 1I3KYu-0005LL-Fq; Tue, 26 Jun 2007 19:35:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3KYt-0005LD-DG
	for avt@ietf.org; Tue, 26 Jun 2007 19:35:07 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3KYB-0007qN-Rn
	for avt@ietf.org; Tue, 26 Jun 2007 19:35:07 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-4.cisco.com with ESMTP; 26 Jun 2007 16:34:23 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAM4+gUarR7O6/2dsb2JhbAA
X-IronPort-AV: i="4.16,465,1175497200"; d="scan'208"; a="5635634:sNHT15139506"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5QNYNAS000521; 
	Tue, 26 Jun 2007 16:34:23 -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 l5QNYKka014325;
	Tue, 26 Jun 2007 23:34:20 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Jun 2007 16:34:20 -0700
Received: from [10.32.254.213] ([10.32.254.213]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Jun 2007 16:34:19 -0700
In-Reply-To: <DA7BAB1B-335A-4193-BE13-8EB565C7DD47@cisco.com>
References: <A5148FAE-9197-4824-87C4-EF54767552F3@cisco.com>
	<18CAE473-3A37-49E0-8F68-CC30629DB2EA@csperkins.org>
	<BC4EE9F5-5F44-4BCC-9CA2-4CB3E684DF71@cisco.com>
	<DA7BAB1B-335A-4193-BE13-8EB565C7DD47@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C2F65CF3-897D-49CC-B631-9B5EFD7A50B1@cisco.com>
Content-Transfer-Encoding: 7bit
From: David McGrew <mcgrew@cisco.com>
Date: Tue, 26 Jun 2007 16:34:34 -0700
To: Cullen Jennings <fluffy@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 26 Jun 2007 23:34:19.0681 (UTC)
	FILETIME=[84B3B910:01C7B84A]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3202; t=1182900863;
	x=1183764863; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mcgrew@cisco.com;
	z=From:=20David=20McGrew=20<mcgrew@cisco.com>
	|Subject:=20Re=3A=20TLS-SRTP=20internet=20draft=20as=20a=20WG=20item=20in
	=20AVT |Sender:=20;
	bh=eTlvV9i2J7eEBG2bEP22A1y3W0bonZmsilJuaK2YW3c=;
	b=P/rIfLjB+eq/9dzBd19rIqRJgKP+7QiV2on1iKMJmQ6SS3H5Oc8oO0AM+Q9oJcP6p+Z7L623
	afJuhPEXAy4tcoHqqbbQiQyUl0mhCGh/c4JDIcBXx5n37KrCIyS8zUxm;
Authentication-Results: sj-dkim-2; header.From=mcgrew@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: Roni Even <roni.even@polycom.co.il>, AVT <avt@ietf.org>,
	tom.taylor@rogers.com, "Dan Wing \(dwing\)" <dwing@cisco.com>,
	Colin Perkins <csp@csperkins.org>
Subject: [AVT] Re: TLS-SRTP internet draft as a WG item in AVT
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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 Cullen,

On Jun 26, 2007, at 3:13 PM, Cullen Jennings wrote:

>
> I have no problem with that milestone if that is what you decide  
> on ...
>
> One question about it - would calling it "DTLS-SRTP" be better than  
> "TLS-SRTP"? I don't care but if we were going to change the name,  
> this would be the right time to do that.

I'm name agnostic.  Whatever Eric and/or the TLS folks say is the  
right TLS terminology.   I said TLS-SRTP here because that's the name  
of the current draft, though lots of people (including me) have used  
the other name.

David

>
> Cullen <with my AD hat on>
>
>
> On Jun 26, 2007, at 2:05 PM, David McGrew ((mcgrew)) wrote:
>
>> Hi Colin,
>>
>> how does this milestone sound?  "December 2007 Submit TLS-SRTP for
>> Proposed Standard"   Perhaps I'm aggressive in expecting us to have
>> the draft ready before the Vancouver meeting; we could push it back
>> to March 2008.
>>
>> David
>>
>> On Jun 26, 2007, at 4:00 AM, Colin Perkins wrote:
>>
>> > Hi David,
>> >
>> > What milestone(s) do you see this work adding to the AVT charter,
>> > if accepted?
>> >
>> > Colin
>> >
>> >
>> >
>> >
>> > On 20 Jun 2007, at 21:54, David McGrew wrote:
>> >> Hi Colin, Roni, and Tom,
>> >>
>> >> I would like to ask that draft-mcgrew-tls-srtp be taken up as a
>> >> working group action item in AVT, as part the plan for carrying
>> >> forward the RTPSEC work (as per Cullen's email of May 11 to the
>> >> rtpsec list).   I would like to continue on as an author of this
>> >> work, and Eric as agreed to do the same.  There are a small number
>> >> of minor open issues which I expect can be wrapped up quickly:
>> >>
>> >> 1.  The draft needs to be clarified so that, in the Symmetric RTP
>> >> case, only one handshake is needed.
>> >>
>> >> 2.  Section 3.6.2.1 needs to be resolved to either decide on a
>> >> "symmetry breaking" rule or not.  It may be desirable to have such
>> >> a rule to handle cases in which the signaling system can't tell a
>> >> device which should act as client and which should act as
>> >> server.   This would allow opportunistic probing, i.e. a TLS-SRTP
>> >> implementation could attempt to find out whether another RTP
>> >> implementation supports TLS-SRTP, absent any help from signaling.
>> >>
>> >> 3.  The "single DTLS session per SRTP session" issue needs to be
>> >> decided, and Appendix A should then be removed from the draft.
>> >>
>> >> 4.  It should be decided to use, or not to use the "TLS
>> >> Extractor", and Section 3.3 should be rewritten accordingly.
>> >>
>> >> 5.  The duplicate list of srtp profiles needs to be eliminated.
>> >>
>> >> Best regards,
>> >>
>> >> David
>> >>
>> >> --
>> >>
>> >> p.s. - here's the AVT-specific part of Cullen note, so that you
>> >> don't need to dig it out of your mailbox: "AVT - Describe how DTLS
>> >> is used to key SRTP and how SRTP is used in combination with DTLS.
>> >> This includes the issues of multiplexing DTLS and SRTP on one
>> >> port. draft-mcgrew-tls-srtp will be the starting draft for this."
>> >
>> >
>> >
>> > --
>> > 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 Jun 26 19:45: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 1I3KiU-0006Li-By; Tue, 26 Jun 2007 19:45:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3KiM-00069K-3J; Tue, 26 Jun 2007 19:44:54 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I3KhT-00019S-HR; Tue, 26 Jun 2007 19:44:54 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 4B9233296C;
	Tue, 26 Jun 2007 22:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I3JrG-0001QD-6Q; Tue, 26 Jun 2007 18:50: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: <E1I3JrG-0001QD-6Q@stiedprstage1.ietf.org>
Date: Tue, 26 Jun 2007 18:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: avt@ietf.org
Subject: [AVT] I-D ACTION:draft-ietf-avt-rtp-vorbis-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		: 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

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-vorbis-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-vorbis-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-6-26170632.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2007-6-26170632.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 Jun 27 02:42: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 1I3REZ-0005K5-Uu; Wed, 27 Jun 2007 02:42:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3REZ-0005Jx-5P
	for avt@ietf.org; Wed, 27 Jun 2007 02:42:35 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3REV-0001nt-Ib
	for avt@ietf.org; Wed, 27 Jun 2007 02:42:35 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 26 Jun 2007 23:42:31 -0700
X-IronPort-AV: i="4.16,465,1175497200"; 
	d="scan'208"; a="172803361:sNHT46707093"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l5R6gUL4026298; 
	Tue, 26 Jun 2007 23:42:30 -0700
Received: from dwingwxp ([10.21.87.212])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l5R6gTvv006058;
	Wed, 27 Jun 2007 06:42:29 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Cullen Jennings'" <fluffy@cisco.com>,
	"'David McGrew \(\(mcgrew\)\)'" <mcgrew@cisco.com>
Date: Tue, 26 Jun 2007 23:42:29 -0700
Message-ID: <090901c7b886$55e66740$b978150a@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
In-Reply-To: <DA7BAB1B-335A-4193-BE13-8EB565C7DD47@cisco.com>
Thread-Index: Ace4P/xgcf8HMLyPTzyq9QK/GQqnVwARjnyw
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3461; t=1182926550;
	x=1183790550; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20TLS-SRTP=20internet=20draft=20as=20a=20WG=20item=20in
	=20AVT |Sender:=20;
	bh=kq5gi/FT7TFD8XTpagCyv4dxeXmdt80WGtN7bDmDyqY=;
	b=SR0PVLcE+GnatYYuEWoYUVkTM7H3VyQl4jIf9/EBW8xBvq+vGck3ARUVL9OoJgG0cWKFw3fl
	qV7Nv4kmVhubNGuW/H9qnqZCmf1k1lNfTH6D4F/8k/Ay08QmejU9GS8s;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (s
	ig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: 'Roni Even' <roni.even@polycom.co.il>, 'Colin Perkins' <csp@csperkins.org>,
	'AVT' <avt@ietf.org>, tom.taylor@rogers.com
Subject: [AVT] RE: TLS-SRTP internet draft as a WG item in AVT
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

If we're taking votes, I would also prefer DTLS-SRTP.  For all we know, we
might want or need TLS (over TCP) with SRTP later (streaming video,
perhaps?).

-d
 

> -----Original Message-----
> From: Cullen Jennings [mailto:fluffy@cisco.com] 
> Sent: Tuesday, June 26, 2007 3:14 PM
> To: David McGrew ((mcgrew))
> Cc: Colin Perkins; Roni Even; tom.taylor@rogers.com; AVT; Dan 
> Wing (dwing); Eric Rescorla
> Subject: Re: TLS-SRTP internet draft as a WG item in AVT
> 
> 
> I have no problem with that milestone if that is what you 
> decide on ...
> 
> One question about it - would calling it "DTLS-SRTP" be better than  
> "TLS-SRTP"? I don't care but if we were going to change the name,  
> this would be the right time to do that.
> 
> Cullen <with my AD hat on>
> 
> 
> On Jun 26, 2007, at 2:05 PM, David McGrew ((mcgrew)) wrote:
> 
> > Hi Colin,
> >
> > how does this milestone sound?  "December 2007 Submit TLS-SRTP for
> > Proposed Standard"   Perhaps I'm aggressive in expecting us to have
> > the draft ready before the Vancouver meeting; we could push it back
> > to March 2008.
> >
> > David
> >
> > On Jun 26, 2007, at 4:00 AM, Colin Perkins wrote:
> >
> > > Hi David,
> > >
> > > What milestone(s) do you see this work adding to the AVT charter,
> > > if accepted?
> > >
> > > Colin
> > >
> > >
> > >
> > >
> > > On 20 Jun 2007, at 21:54, David McGrew wrote:
> > >> Hi Colin, Roni, and Tom,
> > >>
> > >> I would like to ask that draft-mcgrew-tls-srtp be taken up as a
> > >> working group action item in AVT, as part the plan for carrying
> > >> forward the RTPSEC work (as per Cullen's email of May 11 to the
> > >> rtpsec list).   I would like to continue on as an author of this
> > >> work, and Eric as agreed to do the same.  There are a 
> small number
> > >> of minor open issues which I expect can be wrapped up quickly:
> > >>
> > >> 1.  The draft needs to be clarified so that, in the Symmetric RTP
> > >> case, only one handshake is needed.
> > >>
> > >> 2.  Section 3.6.2.1 needs to be resolved to either decide on a
> > >> "symmetry breaking" rule or not.  It may be desirable to 
> have such
> > >> a rule to handle cases in which the signaling system can't tell a
> > >> device which should act as client and which should act as
> > >> server.   This would allow opportunistic probing, i.e. a TLS-SRTP
> > >> implementation could attempt to find out whether another RTP
> > >> implementation supports TLS-SRTP, absent any help from signaling.
> > >>
> > >> 3.  The "single DTLS session per SRTP session" issue needs to be
> > >> decided, and Appendix A should then be removed from the draft.
> > >>
> > >> 4.  It should be decided to use, or not to use the "TLS
> > >> Extractor", and Section 3.3 should be rewritten accordingly.
> > >>
> > >> 5.  The duplicate list of srtp profiles needs to be eliminated.
> > >>
> > >> Best regards,
> > >>
> > >> David
> > >>
> > >> --
> > >>
> > >> p.s. - here's the AVT-specific part of Cullen note, so that you
> > >> don't need to dig it out of your mailbox: "AVT - 
> Describe how DTLS
> > >> is used to key SRTP and how SRTP is used in combination 
> with DTLS.
> > >> This includes the issues of multiplexing DTLS and SRTP on one
> > >> port. draft-mcgrew-tls-srtp will be the starting draft for this."
> > >
> > >
> > >
> > > --
> > > 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 Jun 27 06:00: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 1I3UJy-0006Db-Pp; Wed, 27 Jun 2007 06:00:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3UJx-0006Ai-3M
	for avt@ietf.org; Wed, 27 Jun 2007 06:00:21 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3UJZ-0003Iu-6B
	for avt@ietf.org; Wed, 27 Jun 2007 06:00:21 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:59643)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1I3UJW-0005HZ-1Y; Wed, 27 Jun 2007 10:59:54 +0100
In-Reply-To: <BC4EE9F5-5F44-4BCC-9CA2-4CB3E684DF71@cisco.com>
References: <A5148FAE-9197-4824-87C4-EF54767552F3@cisco.com>
	<18CAE473-3A37-49E0-8F68-CC30629DB2EA@csperkins.org>
	<BC4EE9F5-5F44-4BCC-9CA2-4CB3E684DF71@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B38DDC63-4950-4909-999B-4F22EABEBC6B@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Re: TLS-SRTP internet draft as a WG item in AVT
Date: Wed, 27 Jun 2007 10:59:52 +0100
To: David McGrew <mcgrew@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: Cullen Jennings <fluffy@cisco.com>, Roni Even <roni.even@polycom.co.il>,
	tom.taylor@rogers.com, Dan Wing <dwing@cisco.com>, AVT <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

David, All,

That's fine. We therefore propose to accept this draft as an AVT work  
item, with the milestone listed. If there are any objections to this  
plan, please state them by 29th June 2007.

Colin





On 26 Jun 2007, at 22:05, David McGrew wrote:
> Hi Colin,
>
> how does this milestone sound?  "December 2007 Submit TLS-SRTP for  
> Proposed Standard"   Perhaps I'm aggressive in expecting us to have  
> the draft ready before the Vancouver meeting; we could push it back  
> to March 2008.
>
> David
>
> On Jun 26, 2007, at 4:00 AM, Colin Perkins wrote:
>
>> Hi David,
>>
>> What milestone(s) do you see this work adding to the AVT charter,  
>> if accepted?
>>
>> Colin
>>
>>
>>
>>
>> On 20 Jun 2007, at 21:54, David McGrew wrote:
>>> Hi Colin, Roni, and Tom,
>>>
>>> I would like to ask that draft-mcgrew-tls-srtp be taken up as a  
>>> working group action item in AVT, as part the plan for carrying  
>>> forward the RTPSEC work (as per Cullen's email of May 11 to the  
>>> rtpsec list).   I would like to continue on as an author of this  
>>> work, and Eric as agreed to do the same.  There are a small  
>>> number of minor open issues which I expect can be wrapped up  
>>> quickly:
>>>
>>> 1.  The draft needs to be clarified so that, in the Symmetric RTP  
>>> case, only one handshake is needed.
>>>
>>> 2.  Section 3.6.2.1 needs to be resolved to either decide on a  
>>> "symmetry breaking" rule or not.  It may be desirable to have  
>>> such a rule to handle cases in which the signaling system can't  
>>> tell a device which should act as client and which should act as  
>>> server.   This would allow opportunistic probing, i.e. a TLS-SRTP  
>>> implementation could attempt to find out whether another RTP  
>>> implementation supports TLS-SRTP, absent any help from signaling.
>>>
>>> 3.  The "single DTLS session per SRTP session" issue needs to be  
>>> decided, and Appendix A should then be removed from the draft.
>>>
>>> 4.  It should be decided to use, or not to use the "TLS  
>>> Extractor", and Section 3.3 should be rewritten accordingly.
>>>
>>> 5.  The duplicate list of srtp profiles needs to be eliminated.
>>>
>>> Best regards,
>>>
>>> David
>>>
>>> --
>>>
>>> p.s. - here's the AVT-specific part of Cullen note, so that you  
>>> don't need to dig it out of your mailbox: "AVT - Describe how  
>>> DTLS is used to key SRTP and how SRTP is used in combination with  
>>> DTLS. This includes the issues of multiplexing DTLS and SRTP on  
>>> one port. draft-mcgrew-tls-srtp will be the starting draft for  
>>> this."
>>
>>
>>
>> -- 
>> Colin Perkins
>> http://csperkins.org/
>
> _______________________________________________
> 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 Jun 27 07:09: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 1I3VP7-0006oA-0e; Wed, 27 Jun 2007 07:09:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3VP4-0006ng-Tr
	for avt@ietf.org; Wed, 27 Jun 2007 07:09:42 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3VO6-0004Tx-ID
	for avt@ietf.org; Wed, 27 Jun 2007 07:09:42 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:59826)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1I3VO6-0001wA-3a for avt@ietf.org; Wed, 27 Jun 2007 12:08:42 +0100
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <E1I3JrG-0001QD-6Q@stiedprstage1.ietf.org>
References: <E1I3JrG-0001QD-6Q@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <76F8978B-FE49-4AA3-B366-0436C42A408D@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Wed, 27 Jun 2007 12:08:40 +0100
To: AVT WG <avt@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Subject: [AVT] Working group last call: draft-ietf-avt-rtp-vorbis-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

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.

-- 
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 Jun 27 08:00: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 1I3WCF-0004wB-Ms; Wed, 27 Jun 2007 08:00:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3CmS-0002tM-MF
	for avt@ietf.org; Tue, 26 Jun 2007 11:16:36 -0400
Received: from mail119.messagelabs.com ([216.82.241.179])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1I3CmO-0001Xq-9L
	for avt@ietf.org; Tue, 26 Jun 2007 11:16:36 -0400
X-VirusChecked: Checked
X-Env-Sender: sona@motorola.com
X-Msg-Ref: server-14.tower-119.messagelabs.com!1182864589!23437958!1
X-StarScan-Version: 5.5.12.11; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 16698 invoked from network); 26 Jun 2007 13:29:50 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-14.tower-119.messagelabs.com with SMTP;
	26 Jun 2007 13:29:50 -0000
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l5QDTnIt018150
	for <avt@ietf.org>; Tue, 26 Jun 2007 06:29:49 -0700 (MST)
Received: from il06vts04.mot.com (il06vts04.mot.com [129.188.137.144])
	by il06exr04.mot.com (8.13.1/Vontu) with SMTP id l5QDTnO8001083
	for <avt@ietf.org>; Tue, 26 Jun 2007 08:29:49 -0500 (CDT)
Received: from ZMY16EXM66.ds.mot.com (zmy16exm66.ap.mot.com [10.179.4.26])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id l5QDTlZX001052
	for <avt@ietf.org>; Tue, 26 Jun 2007 08:29:48 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 26 Jun 2007 21:29:43 +0800
Message-ID: <D6831742F069304FB1924B4160A493510226971B@ZMY16EXM66.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: H264 Frame identification
Thread-Index: Ace3vIcKFRPxIjEdRVuLdnQKn++enwAKSt6wAAFKaAAAAgV1IAAAviJA
From: "K Sonachalam-a22339" <sona@motorola.com>
To: <avt@ietf.org>
X-Vontu: Pass
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e5bfa71b340354e384155def5e70b13b
X-Mailman-Approved-At: Wed, 27 Jun 2007 08:00:30 -0400
Subject: [AVT] FW: H264 Frame identification
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-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="===============0840759405=="
Errors-To: avt-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0840759405==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7B7F6.0ED3D8ED"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7B7F6.0ED3D8ED
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all
=20
How to identify a start and end of  Frame in H264.
=20
=20
In RTSP streaming session I will get the SPS and PPS NAL in sdp itself.
=20
And in the  RTP payload has either the VCL NAlunits(Nal type 1 or 5) or
the Filler data
filler_data(Nal type 12).=20
=20
How to identify the Start and End of Frame from the NALs?.
=20
Thanks
Regards
Sona
=20
=20
=20

------_=_NextPart_001_01C7B7F6.0ED3D8ED
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=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"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3132" 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]-->
<STYLE>@font-face {
	font-family: MS Mincho;
}
@font-face {
	font-family: Tahoma;
}
@font-face {
	font-family: @MS Mincho;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
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"
}
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
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle19 {
	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><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D290270713-26062007>Hi all</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D290270713-26062007></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D290270713-26062007>How to identify a start and end of&nbsp; =
Frame in=20
H264.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D290270713-26062007></SPAN></FONT><FONT face=3DArial =
color=3D#0000ff=20
size=3D2><SPAN class=3D290270713-26062007></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D290270713-26062007></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D290270713-26062007>In&nbsp;RTSP streaming session&nbsp;I will =
get the SPS=20
and PPS NAL in sdp itself.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2><SPAN =
class=3D290270713-26062007><FONT=20
face=3DArial color=3D#0000ff></FONT></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2><SPAN =
class=3D290270713-26062007><FONT=20
face=3DArial color=3D#0000ff>And&nbsp;in the &nbsp;RTP payload has =
either the VCL=20
NAlunits<FONT color=3D#ff0000>(Nal type 1 or 5)</FONT>&nbsp;or the =
</FONT><SPAN=20
lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT=20
face=3DArial color=3D#0000ff>Filler data<BR>filler_data(<FONT =
color=3D#ff0000>Nal type=20
12).</FONT> </FONT></SPAN></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2><SPAN =
class=3D290270713-26062007><SPAN=20
lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT=20
face=3DArial color=3D#0000ff></FONT></SPAN></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2><SPAN =
class=3D290270713-26062007><SPAN=20
lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT=20
face=3DArial color=3D#0000ff>How to identify the Start and End of Frame =
from the=20
NALs?.</FONT></SPAN></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D290270713-26062007><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA"></SPAN></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff><SPAN =
class=3D290270713-26062007><SPAN=20
lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><SPAN=20
class=3D250432813-26062007>Thanks</SPAN></SPAN></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff><SPAN =
class=3D290270713-26062007><SPAN=20
lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><SPAN=20
class=3D250432813-26062007>Regards</SPAN></SPAN></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff><SPAN =
class=3D290270713-26062007><SPAN=20
lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><SPAN=20
class=3D250432813-26062007>Sona</SPAN></SPAN></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D290270713-26062007><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA"></SPAN></SPAN></FONT><FONT=20
face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D290270713-26062007><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA"></SPAN></SPAN></FONT><FONT=20
face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D290270713-26062007><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA"></SPAN></SPAN></FONT><FONT=20
face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D290270713-26062007><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA"></SPAN></SPAN></FONT><FONT=20
face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D290270713-26062007><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA"></SPAN></SPAN></FONT><FONT=20
face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D290270713-26062007><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA"></SPAN></SPAN></FONT><FONT=20
face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D290270713-26062007><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA"></SPAN></SPAN></FONT><FONT=20
face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D290270713-26062007><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA"></SPAN></SPAN></FONT><FONT=20
face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D290270713-26062007></SPAN></FONT><FONT face=3DArial =
color=3D#0000ff=20
size=3D2><SPAN class=3D290270713-26062007></SPAN></FONT><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><SPAN =
class=3D290270713-26062007></SPAN></FONT><FONT=20
face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D290270713-26062007></SPAN></FONT><FONT face=3DArial =
color=3D#0000ff=20
size=3D2><SPAN class=3D290270713-26062007></SPAN></FONT><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><SPAN =
class=3D290270713-26062007></SPAN></FONT><FONT=20
face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D290270713-26062007></SPAN></FONT><FONT face=3DArial=20
size=3D2></FONT>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C7B7F6.0ED3D8ED--


--===============0840759405==
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

--===============0840759405==--




From avt-bounces@ietf.org Wed Jun 27 10:01: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 1I3Y5g-0004cZ-Jl; Wed, 27 Jun 2007 10:01:52 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3Y5e-0004aI-QG
	for avt@ietf.org; Wed, 27 Jun 2007 10:01:50 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3Y5e-0002B1-GX
	for avt@ietf.org; Wed, 27 Jun 2007 10:01:50 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	77D8920820; Wed, 27 Jun 2007 16:01:33 +0200 (CEST)
X-AuditID: c1b4fb3c-b067fbb0000007e1-fe-46826dbdb1e9
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	5C61320B1F; Wed, 27 Jun 2007 16:01:33 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 27 Jun 2007 16:01:33 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 27 Jun 2007 16:01:32 +0200
Message-ID: <46826DBC.7080707@ericsson.com>
Date: Wed, 27 Jun 2007 16:01:32 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Re: TLS-SRTP internet draft as a WG item in AVT
References: <A5148FAE-9197-4824-87C4-EF54767552F3@cisco.com>	<18CAE473-3A37-49E0-8F68-CC30629DB2EA@csperkins.org>	<BC4EE9F5-5F44-4BCC-9CA2-4CB3E684DF71@cisco.com>
	<B38DDC63-4950-4909-999B-4F22EABEBC6B@csperkins.org>
In-Reply-To: <B38DDC63-4950-4909-999B-4F22EABEBC6B@csperkins.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Jun 2007 14:01:32.0676 (UTC)
	FILETIME=[AAC8AC40:01C7B8C3]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: Cullen Jennings <fluffy@cisco.com>, Roni Even <roni.even@polycom.co.il>,
	tom.taylor@rogers.com, AVT <avt@ietf.org>,
	David McGrew <mcgrew@cisco.com>, Dan Wing <dwing@cisco.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

Colin Perkins skrev:
> David, All,
> 
> That's fine. We therefore propose to accept this draft as an AVT work 
> item, with the milestone listed. If there are any objections to this 
> plan, please state them by 29th June 2007.
> 
> Colin

Hi,

Are you of the opinion that the following item in the charter covers this?

- to maintain and enhance the SRTP Profile, with review and input from
the Security Area


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 Jun 27 10:25: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 1I3YSX-0007Vb-8K; Wed, 27 Jun 2007 10:25:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3YSV-0007Jm-3Z
	for avt@ietf.org; Wed, 27 Jun 2007 10:25:27 -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 1I3YRu-0000pC-TL for avt@ietf.org; Wed, 27 Jun 2007 10:25:27 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 27 Jun 2007 10:24:50 -0400
To: avt@ietf.org
From: Randell Jesup <rjesup@wgate.com>
Date: Wed, 27 Jun 2007 10:24:49 -0400
In-Reply-To: <D6831742F069304FB1924B4160A493510226971B@ZMY16EXM66.ds.mot.com>
	(K. Sonachalam-a's message of "Tue, 26 Jun 2007 21:29:43 +0800")
Message-ID: <ybuy7i5scem.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
References: <D6831742F069304FB1924B4160A493510226971B@ZMY16EXM66.ds.mot.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 27 Jun 2007 14:24:50.0566 (UTC)
	FILETIME=[EBFDC260:01C7B8C6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Subject: [AVT] RFC 2833/RFC 4733 and timestamps
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

While investigating some RFC 2833/4733 stuff, I ran across this discussion
at the Asterisk bug system.  The relevant piece is the discussion exerpted
from email with a "major PBX vendor" about simultaneous 2833 and audio
packets (which is explicitly allowed by RFC 2833).  

http://bugs.digium.com/view.php?id=6667

Search for this message, about 1/2-way down:
(0042832)
damin - manager
03-17-06 11:07

There's a bunch more from the engineers at this "Major PBX Vendor", but
this is the summary:

> We checked the RFC 2833, it dose not work, because your DTMF event and
> voice event has the same time stamp. In this case, we are going to drop
> the "duplicate" packets. I have several email exchanges with our
> engineers. They think logically, DMTF events and voice packets should not
> have the same time stamps. We have been in SIPIT events and test with 10+
> vendors, we don't have problems to recieve DTMF through RFC 2833. I don't
> know if it's easy to change some implementation in your side. Attatched
> are some email exchanges among our engineers.

My reading of 2833 and 4733 is that duplicate timestamps between audio
packets and 2833/4733 packets *are* allowed.  Encoded audio and Events
are allowed to overlap, and from the below I'd assume they can overlap
for the entire event.

>From RFC 2833:
   3.2 Simultaneous Generation of Audio and Events

   A source MAY send events and coded audio packets for the same time
   instants, using events as the redundant encoding for the audio
   stream, or it MAY block outgoing audio while event tones are active
   and only send named events as both the primary and redundant
   encodings.

   Note that a period covered by an encoded tone may overlap in time
   with a period of audio encoded by other means. This is likely to
   occur at the onset of a tone and is necessary to avoid possible
   errors in the interpretation of the reproduced tone at the remote
   end.  Implementations supporting this payload format must be prepared
   to handle the overlap. It is RECOMMENDED that gateways only render
   the encoded tone since the audio may contain spurious tones
   introduced by the audio compression algorithm. However, it is
   anticipated that these extra tones in general should not interfere
   with recognition at the far end.

I also note that this paragraph has been removed from RFC 4733, which makes
no direct comment on simultaneous/overlapping audio and Event payloads.
(It does imply in the DTMF discussion that commonly devices will send
DTMF events interspersed with audio, and Events allow them to avoid codec
mangling and they don't have to generate precise tone waveforms.)


So....
1) Can I have 2833/4733 Events with the same timestamp(s) as coded audio
   packets (G711/etc)?  Both in theory (per the RFC), and in practice (will
   receiving devices in the real world break on it, per the PBX vendor
   above)?  If it breaks gateways/PBXs to have packets with the same
   timestamp (BAD jitter-buffer implementation - should use sequence
   numbers for duplicate detection), can I increment the timestamp of
   the Event by (say) 1?  Or do I need to increment it by a packetization-
   interval?  (Such that, barring re-ordering(!), the evil jitter-buffer
   will throw away the coded audio pakcet instead of the Event.)
2) What do other devices do?  Do they send both in-band (tones in audio)
   and out-of-band (RFC 2833/4733) continuously when there's a press?
3) If a device doesn't send both throughout, what about overlap between the
   last audio codec packet and first DTMF packet?  and the same at the end
   of the DTMF sequence?  (In both theory and practice - for example, it
   would seem to be valid in theory to overlap at the start, and at the end
   restart the audio codec at a point which would be in the "middle" of
   a frame from the pre-Event timing.  However, many receivers might get
   upset at that, even if it's legal.)
4) (not really related to the above)
   RFC 4733 (and 2833) say:
       An audio source SHOULD start transmitting event packets as soon as
       it recognizes an event and continue to send updates until the event
       has ended. 
   But the examples show transmission of the Start packet for the Event
   occurring 50ms after the Event started, with a duration of 50ms.  I
   know Cisco (and others) send a start packet with a duration of 0ms,
   then increase the duration in future packets.  Per RFC 4733, 0 for 
   duration is a special value only allowed for "states", and DTMF events
   are "tones".  RFC 2833 seems to allow a 0 duration at the start of
   a DTMF event.

The RFC 4733 example doesn't show coded audio or overlaps.  It does
strongly imply that the starting timestamp is the time the button is
pressed, with no caveats expressed.

-- 
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 Jun 27 10:58: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 1I3YyT-0004eY-Is; Wed, 27 Jun 2007 10:58:29 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3YyQ-0004ZK-RP
	for avt@ietf.org; Wed, 27 Jun 2007 10:58:26 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3YyQ-0005rS-7a
	for avt@ietf.org; Wed, 27 Jun 2007 10:58:26 -0400
Received: from postgrad1.arts.gla.ac.uk ([130.209.98.104]:60394
	helo=[192.168.3.119])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1I3Yxp-0002Xy-27; Wed, 27 Jun 2007 15:57:49 +0100
In-Reply-To: <46826DBC.7080707@ericsson.com>
References: <A5148FAE-9197-4824-87C4-EF54767552F3@cisco.com>	<18CAE473-3A37-49E0-8F68-CC30629DB2EA@csperkins.org>	<BC4EE9F5-5F44-4BCC-9CA2-4CB3E684DF71@cisco.com>
	<B38DDC63-4950-4909-999B-4F22EABEBC6B@csperkins.org>
	<46826DBC.7080707@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C5ADFAA2-E3B5-4158-AF8A-FB0DF27A64B7@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Re: TLS-SRTP internet draft as a WG item in AVT
Date: Wed, 27 Jun 2007 15:57:47 +0100
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: Cullen Jennings <fluffy@cisco.com>, Roni Even <roni.even@polycom.co.il>,
	tom.taylor@rogers.com, AVT <avt@ietf.org>,
	David McGrew <mcgrew@cisco.com>, Dan Wing <dwing@cisco.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 27 Jun 2007, at 15:01, Magnus Westerlund wrote:
> Colin Perkins skrev:
>> That's fine. We therefore propose to accept this draft as an AVT  
>> work item, with the milestone listed. If there are any objections  
>> to this plan, please state them by 29th June 2007.
>> Colin
>
> Are you of the opinion that the following item in the charter  
> covers this?
>
> - to maintain and enhance the SRTP Profile, with review and input from
> the Security Area

That, and the charter item "to provide a framing mechanism for RTP  
over TCP and TLS", and an explicit request from our area director to  
take this draft... If that's not sufficient, we can propose  
additional text (since a charter update will be needed to add the new  
milestone anyway).

-- 
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 Jun 27 13:16: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 1I3b7W-0001UT-Mn; Wed, 27 Jun 2007 13:15:58 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3b7V-0001MV-JQ
	for avt@ietf.org; Wed, 27 Jun 2007 13:15:57 -0400
Received: from an-out-0708.google.com ([209.85.132.248])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3b7V-00061B-81
	for avt@ietf.org; Wed, 27 Jun 2007 13:15:57 -0400
Received: by an-out-0708.google.com with SMTP id c17so53845anc
	for <avt@ietf.org>; Wed, 27 Jun 2007 10:14:44 -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=NNPUeIGTBicCFSGzyTiOSj1ki+EG3q38d475qImvChb4rIcSDhh/65ZRgI9ZdwiKl/g6oQ7KizAA3RuNX43C0X3nhSrVwp7OjQssDBv7QNrMYI4aJRosZwRqPyFHBnJsqciix+WfhVukB5eJAbDoUUx0O4D7/5gNl7CVW1jHmsw=
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=YBjHR6tX2jopXOtIpd5cxKbQvFvOyFJX9tg58qMmRtH+9FxPxY85TN0NS1ojBTdlhRfSICRaeYPegCgbdKGfFRS3b8Q+I4EK/P2JcpzLWnQwktMtm+Y9sAyAodl0sYcC2A8aOEfVabxhipNH+OyHmd0mikg8siKyG39eg3K3Byw=
Received: by 10.100.9.19 with SMTP id 19mr498767ani.1182964483965;
	Wed, 27 Jun 2007 10:14:43 -0700 (PDT)
Received: by 10.100.177.19 with HTTP; Wed, 27 Jun 2007 10:14:43 -0700 (PDT)
Message-ID: <54e41b4b0706271014p39d0e6f3sf5d2e902f2046b0f@mail.gmail.com>
Date: Wed, 27 Jun 2007 18:14:43 +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: <ybuy7i5scem.fsf@jesup.eng.wgate.com>
MIME-Version: 1.0
References: <D6831742F069304FB1924B4160A493510226971B@ZMY16EXM66.ds.mot.com>
	<ybuy7i5scem.fsf@jesup.eng.wgate.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
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="===============0006128230=="
Errors-To: avt-bounces@ietf.org

--===============0006128230==
Content-Type: multipart/alternative; 
	boundary="----=_Part_60950_680118.1182964483924"

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

On 6/27/07, Randell Jesup <rjesup@wgate.com> wrote:
>
> 2) What do other devices do?  Do they send both in-band (tones in audio)
>    and out-of-band (RFC 2833/4733) continuously when there's a press?


I've seen both choices but it is very much more common to suppress the audio
when RFC2833/4733 is being transmitted.

3) If a device doesn't send both throughout, what about overlap between the
>    last audio codec packet and first DTMF packet?  and the same at the end
>    of the DTMF sequence?  (In both theory and practice - for example, it
>    would seem to be valid in theory to overlap at the start, and at the
> end
>    restart the audio codec at a point which would be in the "middle" of
>    a frame from the pre-Event timing.  However, many receivers might get
>    upset at that, even if it's legal.)


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.

4) (not really related to the above)
>    RFC 4733 (and 2833) say:
>        An audio source SHOULD start transmitting event packets as soon as
>        it recognizes an event and continue to send updates until the event
>        has ended.
>    But the examples show transmission of the Start packet for the Event
>    occurring 50ms after the Event started, with a duration of 50ms.


The example is specifically referring to a gateway - the 50ms delay looks
like the time taken to identify that the audio stream contains a DTMF tone
and start encoding it as such.

 Per RFC 4733, 0 for
>   duration is a special value only allowed for "states", and DTMF events
>   are "tones".  RFC 2833 seems to allow a 0 duration at the start of
>   a DTMF event.


Section 2.3.5 does explicitly state that zero length durations ought to be
ignored for no states.

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

On 6/27/07, <b class="gmail_sendername">Randell Jesup</b> &lt;<a href="mailto:rjesup@wgate.com">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;">
2) What do other devices do?&nbsp;&nbsp;Do they send both in-band (tones in audio)<br>&nbsp;&nbsp; and out-of-band (RFC 2833/4733) continuously when there&#39;s a press?</blockquote><div><br>I&#39;ve seen both choices but it is very much more common to suppress the audio when RFC2833/4733 is being transmitted.
<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;">3) If a device doesn&#39;t send both throughout, what about overlap between the
<br>&nbsp;&nbsp; last audio codec packet and first DTMF packet?&nbsp;&nbsp;and the same at the end<br>&nbsp;&nbsp; of the DTMF sequence?&nbsp;&nbsp;(In both theory and practice - for example, it<br>&nbsp;&nbsp; would seem to be valid in theory to overlap at the start, and at the end
<br>&nbsp;&nbsp; restart the audio codec at a point which would be in the &quot;middle&quot; of<br>&nbsp;&nbsp; a frame from the pre-Event timing.&nbsp;&nbsp;However, many receivers might get<br>&nbsp;&nbsp; upset at that, even if it&#39;s legal.)</blockquote><div>
<br>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.
<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;">4) (not really related to the above)<br>&nbsp;&nbsp; RFC 4733 (and 2833) say:<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; An audio source SHOULD start transmitting event packets as soon as
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; it recognizes an event and continue to send updates until the event<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; has ended.<br>&nbsp;&nbsp; But the examples show transmission of the Start packet for the Event<br>&nbsp;&nbsp; occurring 50ms after the Event started, with a duration of 50ms. 
</blockquote><div><br>The example is specifically referring to a gateway - the 50ms
delay looks like the time taken to identify that the audio stream
contains a DTMF tone and start encoding it as such.&nbsp;</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">&nbsp;Per RFC 4733, 0 for<br> &nbsp; duration is a special value only allowed for &quot;states&quot;, and DTMF events
<br> &nbsp; are &quot;tones&quot;. &nbsp;RFC 2833 seems to allow a 0 duration at the start of<br> &nbsp; a DTMF event.</blockquote><div><br>Section 2.3.5 does explicitly state that zero length durations ought to be ignored for no states.
<br></div></div>

------=_Part_60950_680118.1182964483924--


--===============0006128230==
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

--===============0006128230==--




From avt-bounces@ietf.org Wed Jun 27 13:31: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 1I3bMH-000676-J0; Wed, 27 Jun 2007 13:31:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3bMF-000671-O4
	for avt@ietf.org; Wed, 27 Jun 2007 13:31:11 -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 1I3bMB-0001m1-2W for avt@ietf.org; Wed, 27 Jun 2007 13:31:11 -0400
Received: from sjc12-sbr-sw3-3f5.cisco.com (HELO imail.cisco.com)
	([172.19.96.182])
	by sj-iport-2.cisco.com with ESMTP; 27 Jun 2007 10:31:07 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAADs7gkasE2C2/2dsb2JhbAANiDU
X-IronPort-AV: i="4.16,467,1175497200"; 
	d="scan'208"; a="382180053:sNHT40132704"
Received: from [10.32.245.150] ([10.32.245.150])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id l5RH3U7S024139;
	Wed, 27 Jun 2007 10:03:30 -0700
In-Reply-To: <ybuy7i5scem.fsf@jesup.eng.wgate.com>
References: <D6831742F069304FB1924B4160A493510226971B@ZMY16EXM66.ds.mot.com>
	<ybuy7i5scem.fsf@jesup.eng.wgate.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <8CA8312C-E636-4F4D-BF35-A6A29AE28824@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [AVT] RFC 2833/RFC 4733 and timestamps
Date: Wed, 27 Jun 2007 13:31:02 -0400
To: Randell Jesup <rjesup@wgate.com>
X-Mailer: Apple Mail (2.752.2)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5824; t=1182963810;
	x=1183827810; c=relaxed/simple; s=oregon;
	h=To: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]=20RFC=202833/RFC=204733=20and=20timestamps
	|Sender:=20 |To:=20Randell=20Jesup=20<rjesup@wgate.com>;
	bh=vbdupDJ/97YVPMWKl0fTK3quxa1aVUI9VfhEk1gEI1E=;
	b=p5d1673vaI8H6SGrA1gfx5aALQeiOrGkZOG/WH63w4U/9QuUkEo+gaYCQ33x3J6fLvMpbVoV
	cqKlBZ8tJf4AW4/amWd540m16H3VQ74OP8CPASRXCTgb0Wbr8MMRsDCj;
Authentication-Results: imail.cisco.com; header.From=oran@cisco.com;
	dkim=pass ( sig from cisco.com/oregon verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
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 Jun 27, 2007, at 10:24 AM, Randell Jesup wrote:

> While investigating some RFC 2833/4733 stuff, I ran across this  
> discussion
> at the Asterisk bug system.  The relevant piece is the discussion  
> exerpted
> from email with a "major PBX vendor" about simultaneous 2833 and audio
> packets (which is explicitly allowed by RFC 2833).

In fact, this can be used to advantage. Check out US Patent 6,775,265.

>
>
> http://bugs.digium.com/view.php?id=6667
>
> Search for this message, about 1/2-way down:
> (0042832)
> damin - manager
> 03-17-06 11:07
>
> There's a bunch more from the engineers at this "Major PBX Vendor",  
> but
> this is the summary:
>
>> We checked the RFC 2833, it dose not work, because your DTMF event  
>> and
>> voice event has the same time stamp. In this case, we are going to  
>> drop
>> the "duplicate" packets. I have several email exchanges with our
>> engineers. They think logically, DMTF events and voice packets  
>> should not
>> have the same time stamps. We have been in SIPIT events and test  
>> with 10+
>> vendors, we don't have problems to recieve DTMF through RFC 2833.  
>> I don't
>> know if it's easy to change some implementation in your side.  
>> Attatched
>> are some email exchanges among our engineers.
>
> My reading of 2833 and 4733 is that duplicate timestamps between audio
> packets and 2833/4733 packets *are* allowed.  Encoded audio and Events
> are allowed to overlap, and from the below I'd assume they can overlap
> for the entire event.
>
>> From RFC 2833:
>    3.2 Simultaneous Generation of Audio and Events
>
>    A source MAY send events and coded audio packets for the same time
>    instants, using events as the redundant encoding for the audio
>    stream, or it MAY block outgoing audio while event tones are active
>    and only send named events as both the primary and redundant
>    encodings.
>
>    Note that a period covered by an encoded tone may overlap in time
>    with a period of audio encoded by other means. This is likely to
>    occur at the onset of a tone and is necessary to avoid possible
>    errors in the interpretation of the reproduced tone at the remote
>    end.  Implementations supporting this payload format must be  
> prepared
>    to handle the overlap. It is RECOMMENDED that gateways only render
>    the encoded tone since the audio may contain spurious tones
>    introduced by the audio compression algorithm. However, it is
>    anticipated that these extra tones in general should not interfere
>    with recognition at the far end.
>
> I also note that this paragraph has been removed from RFC 4733,  
> which makes
> no direct comment on simultaneous/overlapping audio and Event  
> payloads.
> (It does imply in the DTMF discussion that commonly devices will send
> DTMF events interspersed with audio, and Events allow them to avoid  
> codec
> mangling and they don't have to generate precise tone waveforms.)
>
>
> So....
> 1) Can I have 2833/4733 Events with the same timestamp(s) as coded  
> audio
>    packets (G711/etc)?  Both in theory (per the RFC), and in  
> practice (will
>    receiving devices in the real world break on it, per the PBX vendor
>    above)?  If it breaks gateways/PBXs to have packets with the same
>    timestamp (BAD jitter-buffer implementation - should use sequence
>    numbers for duplicate detection), can I increment the timestamp of
>    the Event by (say) 1?  Or do I need to increment it by a  
> packetization-
>    interval?  (Such that, barring re-ordering(!), the evil jitter- 
> buffer
>    will throw away the coded audio pakcet instead of the Event.)
> 2) What do other devices do?  Do they send both in-band (tones in  
> audio)
>    and out-of-band (RFC 2833/4733) continuously when there's a press?
> 3) If a device doesn't send both throughout, what about overlap  
> between the
>    last audio codec packet and first DTMF packet?  and the same at  
> the end
>    of the DTMF sequence?  (In both theory and practice - for  
> example, it
>    would seem to be valid in theory to overlap at the start, and at  
> the end
>    restart the audio codec at a point which would be in the  
> "middle" of
>    a frame from the pre-Event timing.  However, many receivers  
> might get
>    upset at that, even if it's legal.)
> 4) (not really related to the above)
>    RFC 4733 (and 2833) say:
>        An audio source SHOULD start transmitting event packets as  
> soon as
>        it recognizes an event and continue to send updates until  
> the event
>        has ended.
>    But the examples show transmission of the Start packet for the  
> Event
>    occurring 50ms after the Event started, with a duration of 50ms.  I
>    know Cisco (and others) send a start packet with a duration of 0ms,
>    then increase the duration in future packets.  Per RFC 4733, 0 for
>    duration is a special value only allowed for "states", and DTMF  
> events
>    are "tones".  RFC 2833 seems to allow a 0 duration at the start of
>    a DTMF event.
>
> The RFC 4733 example doesn't show coded audio or overlaps.  It does
> strongly imply that the starting timestamp is the time the button is
> pressed, with no caveats expressed.
>
> -- 
> Randell Jesup, Worldgate (developers of the Ojo videophone), ex- 
> Amiga OS team
> rjesup@wgate.com
> "The fetters imposed on liberty at home have ever been forged out  
> of the weapons
> provided for defence against real, pretended, or imaginary dangers  
> from abroad."
> 		- James Madison, 4th US president (1751-1836)
>
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

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



From avt-bounces@ietf.org Thu Jun 28 00:23: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 1I3lWj-0003hG-3Z; Thu, 28 Jun 2007 00:22:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3lWg-0003hB-28
	for avt@ietf.org; Thu, 28 Jun 2007 00:22:38 -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 1I3lWb-0006w4-Pu for avt@ietf.org; Thu, 28 Jun 2007 00:22:38 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 28 Jun 2007 00:22:33 -0400
To: David R Oran <oran@cisco.com>
Subject: Re: [AVT] RFC 2833/RFC 4733 and timestamps
References: <D6831742F069304FB1924B4160A493510226971B@ZMY16EXM66.ds.mot.com>
	<ybuy7i5scem.fsf@jesup.eng.wgate.com>
	<8CA8312C-E636-4F4D-BF35-A6A29AE28824@cisco.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Thu, 28 Jun 2007 00:22:32 -0400
In-Reply-To: <8CA8312C-E636-4F4D-BF35-A6A29AE28824@cisco.com> (David R.
	Oran's message of "Wed, 27 Jun 2007 13:31:02 -0400")
Message-ID: <ybubqf0r9mf.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: 28 Jun 2007 04:22:33.0475 (UTC)
	FILETIME=[F3050530:01C7B93B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

David R Oran <oran@cisco.com> writes:
>On Jun 27, 2007, at 10:24 AM, Randell Jesup wrote:
>
>> While investigating some RFC 2833/4733 stuff, I ran across this
>> discussion at the Asterisk bug system.  The relevant piece is the
>> discussion exerpted from email with a "major PBX vendor" about
>> simultaneous 2833 and audio packets (which is explicitly allowed by RFC
>> 2833).
>
>In fact, this can be used to advantage. Check out US Patent 6,775,265.

Hmmpf.  Hardly patentable, IMHO, and in fact I'd say it was forecast by
the 2833 draft itself.  Not to mention many of the claims are "the world is
ours!" claims.  :-/

For example, this claim:
    13. A method for processing signaling in a packet telephony system,
        comprising: encoding a telephony data stream into voice packets;
        identifying signaling in the telephony data stream; transmitting
        the voice packets regardless of whether the voice packets contain
        signaling; encoding identified signaling into signaling packets and
        transmitting the signaling packets and the voice packets; and
        encoding and transmitting the voice packets and the signaling
        packets for the same time reference values.

Is pretty much "we implement 2833, which allows us to send both audio and
DTMF for the same time period".  And it's pretty darn obvious.  Some of the
others are a little stronger, but overall it's pretty weak - like most
software patents.

Ah well.

-- 
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 Jun 28 00:43: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 1I3lqo-0001bX-3A; Thu, 28 Jun 2007 00:43:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3lqn-0001bN-An
	for avt@ietf.org; Thu, 28 Jun 2007 00:43:25 -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 1I3lpq-0001gA-4L for avt@ietf.org; Thu, 28 Jun 2007 00:43:25 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 28 Jun 2007 00:42:25 -0400
To: "Mark Brown" <broonie@gmail.com>
Subject: Re: [AVT] RFC 2833/RFC 4733 and timestamps
References: <D6831742F069304FB1924B4160A493510226971B@ZMY16EXM66.ds.mot.com>
	<ybuy7i5scem.fsf@jesup.eng.wgate.com>
	<54e41b4b0706271014p39d0e6f3sf5d2e902f2046b0f@mail.gmail.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Thu, 28 Jun 2007 00:42:24 -0400
In-Reply-To: <54e41b4b0706271014p39d0e6f3sf5d2e902f2046b0f@mail.gmail.com>
	(Mark Brown's message of "Wed, 27 Jun 2007 18:14:43 +0100")
Message-ID: <ybu7ipor8pb.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: 28 Jun 2007 04:42:25.0991 (UTC)
	FILETIME=[B9D08570:01C7B93E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

"Mark Brown" <broonie@gmail.com> writes:
>On 6/27/07, Randell Jesup <rjesup@wgate.com> wrote:
>>
>> 2) What do other devices do?  Do they send both in-band (tones in audio)
>>    and out-of-band (RFC 2833/4733) continuously when there's a press?
>
>I've seen both choices but it is very much more common to suppress the audio
>when RFC2833/4733 is being transmitted.

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?

>3) If a device doesn't send both throughout, what about overlap between the
>>    last audio codec packet and first DTMF packet?  and the same at the end
>>    of the DTMF sequence?  (In both theory and practice - for example, it
>>    would seem to be valid in theory to overlap at the start, and at the
>> end
>>    restart the audio codec at a point which would be in the "middle" of
>>    a frame from the pre-Event timing.  However, many receivers might get
>>    upset at that, even if it's legal.)
>
>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.

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.

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.

> Per RFC 4733, 0 for
>>   duration is a special value only allowed for "states", and DTMF events
>>   are "tones".  RFC 2833 seems to allow a 0 duration at the start of
>>   a DTMF event.
>
>Section 2.3.5 does explicitly state that zero length durations ought to be
>ignored for no states.

Which would be a slight problem if they did this, since if you ignore the
start-packet, you'd have to notice a later packet (with non-0 duration),
and decide that the start packet had been "lost" (really it was ignored),
and back-fill the tone.  It should work, in most cases, but it increases
vulnerability to packet loss (i.e. if the first update packet gets really
lost or delayed, for example).

This really is just a case of something valid (if unmentioned) in RFC 2833
that's invalid in RFC 4733, but if you do something "reasonable" there's
not likely to be a bad side-effect (per above, though with additional
risk).

-- 
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 Jun 28 02:58: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 1I3nxE-0007f9-Ua; Thu, 28 Jun 2007 02:58:12 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3nxD-0007eu-62
	for avt@ietf.org; Thu, 28 Jun 2007 02:58:11 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3nxC-0000HH-Uo
	for avt@ietf.org; Thu, 28 Jun 2007 02:58:11 -0400
Received: from relay6.apple.com (relay6.apple.com [17.128.113.36])
	by mail-out3.apple.com (Postfix) with ESMTP id A4BCAA721FE;
	Wed, 27 Jun 2007 23:57:21 -0700 (PDT)
Received: from relay6.apple.com (unknown [127.0.0.1])
	by relay6.apple.com (Symantec Mail Security) with ESMTP id 8DF9E100C7; 
	Wed, 27 Jun 2007 23:57:21 -0700 (PDT)
X-AuditID: 11807124-a2ce2bb0000007e2-9b-46835bd06af6
Received: from [17.202.35.52] (int-si-a.apple.com [17.128.113.41])
	by relay6.apple.com (Apple SCV relay) with ESMTP id 74C5F100A4;
	Wed, 27 Jun 2007 23:57:20 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p062408c8c2a90be9b7f9@[17.202.35.52]>
In-Reply-To: <317911.16047.qm@web42109.mail.mud.yahoo.com>
References: <317911.16047.qm@web42109.mail.mud.yahoo.com>
Date: Thu, 28 Jun 2007 09:56:33 +0300
To: sona chalam <sona_kk@yahoo.com>, IETF AVT WG <avt@ietf.org>
From: Dave Singer <singer@apple.com>
Subject: Re: [AVT] Identifying a Frame from the NAL units
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
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

At 6:26  -0700 26/06/07, sona chalam wrote:
>Hi all
>
>How to identify a start and end of  Frame in H264.
>
>
>In RTSP streaming session I will get the SPS and PPS
>NAL in sdp itself.
>
>And in the  RTP payload has either the VCL
>NAlunits(Nal type 1 or 5) or the Filler data
>filler_data(Nal type 12).
>
>How to identify the Start and End of Frame from the
>NALs?.

You follow the marker bit, check for lost packets by looking at 
sequence numbers, and look at the timestamp changes:

Marker bit (M): 1 bit : Set for the very last packet of the access 
unit indicated by the RTP timestamp
-- 
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 Jun 28 12:47: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 1I3x8y-0005O6-EO; Thu, 28 Jun 2007 12:46:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3x8w-00059I-3O
	for avt@ietf.org; Thu, 28 Jun 2007 12:46:54 -0400
Received: from lumisoft.ee ([84.50.104.142] helo=mail.lumisoft.ee)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3x8v-0006W9-KO
	for avt@ietf.org; Thu, 28 Jun 2007 12:46:54 -0400
Received: from 192.168.1.1 (192.168.1.1)
	by mail.lumisoft.ee with SMTP; Thu, 28 Jun 2007 16:43:44 GMT
Message-ID: <4683E5A8.7050905@lumisoft.ee>
Date: Thu, 28 Jun 2007 19:45:28 +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: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Subject: [AVT] RTP general
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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,

After reading several days rfc 3550, i can't figure out some stuff.

For example rfc 3550 6.3 RTCP Packet Send and Receive Rules
********************************************************
To execute these rules, a session participant must maintain several
   pieces of state:

   tp: the last time an RTCP packet was transmitted;

   tc: the current time;

....
...
*********************************************************

Ok, am i right if i say:
RTP session may have many participants and all store that state ?



Now if BYE packet received, isn't participant disposed ?
Or why then tn,tp(reverse  reconsideration) values recalculated ?

Thanks,

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



From avt-bounces@ietf.org Fri Jun 29 01:39: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 1I49CT-0006sa-Ei; Fri, 29 Jun 2007 01:39:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I49CN-0006TY-Qq
	for avt@ietf.org; Fri, 29 Jun 2007 01:39:16 -0400
Received: from [211.189.53.2] (helo=kor1corpmail01.mediator.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I49CH-0002lh-1g
	for avt@ietf.org; Fri, 29 Jun 2007 01:39:15 -0400
Subject: RE: [AVT] Identifying a Frame from the NAL units
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 29 Jun 2007 14:39:06 +0900
Message-ID: <FE6A9D3F2979884280CE0F5F5185517B50182A@kor1corpmail01.mediator.com>
In-Reply-To: <p062408c8c2a90be9b7f9@[17.202.35.52]>
References: <317911.16047.qm@web42109.mail.mud.yahoo.com>
	<p062408c8c2a90be9b7f9@[17.202.35.52]>
From: "Jaehwan Kim" <jaehwan@vidiator.com>
To: "Dave Singer" <singer@apple.com>, "sona chalam" <sona_kk@yahoo.com>,
	"IETF AVT WG" <avt@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi,
Yes, generally Market is like that.
However, for H.264 RTPPayload format and RTP marker bit:

A few years ago in IMTC, we had informal technical discussion about
this:

   In case of H.264, the meaning of RTP Marker bit seems unclear.
   Rather than following legacy, we should follow H.264 payload format.

If we make a future H.264 RFC, this should be clarified.

Cheers,
Jaehwan
Vidiator

-----Original Message-----
From: Dave Singer [mailto:singer@apple.com]=20
Sent: Thursday, June 28, 2007 3:57 PM
To: sona chalam; IETF AVT WG
Subject: Re: [AVT] Identifying a Frame from the NAL units

At 6:26  -0700 26/06/07, sona chalam wrote:
>Hi all
>
>How to identify a start and end of  Frame in H264.
>
>
>In RTSP streaming session I will get the SPS and PPS
>NAL in sdp itself.
>
>And in the  RTP payload has either the VCL
>NAlunits(Nal type 1 or 5) or the Filler data
>filler_data(Nal type 12).
>
>How to identify the Start and End of Frame from the
>NALs?.

You follow the marker bit, check for lost packets by looking at=20
sequence numbers, and look at the timestamp changes:

Marker bit (M): 1 bit : Set for the very last packet of the access=20
unit indicated by the RTP timestamp
--=20
David Singer
Apple/QuickTime

_______________________________________________
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 Jun 29 03:02: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 1I4AV8-0007b7-RM; Fri, 29 Jun 2007 03:02:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4AV7-0007b2-Ed
	for avt@ietf.org; Fri, 29 Jun 2007 03:02:41 -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 1I4AV2-00071E-T2
	for avt@ietf.org; Fri, 29 Jun 2007 03:02:41 -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: Fri, 29 Jun 2007 10:03:29 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C04AFCBCD@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AVT WG meeting in Chicago - Time slot requests
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
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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 March 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 Fri Jun 29 05: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 1I4D78-0002TO-8s; Fri, 29 Jun 2007 05:50:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4D76-0002T2-Dt
	for avt@ietf.org; Fri, 29 Jun 2007 05:50:04 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4D72-000347-1v
	for avt@ietf.org; Fri, 29 Jun 2007 05:50:04 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	80B5820D6C; Fri, 29 Jun 2007 11:49:59 +0200 (CEST)
X-AuditID: c1b4fb3c-af67dbb0000007e1-87-4684d5c7cae0
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	6EB3420BF6; Fri, 29 Jun 2007 11:49:59 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Jun 2007 11:49:59 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Jun 2007 11:49:59 +0200
Message-ID: <4684D5C7.9060804@ericsson.com>
Date: Fri, 29 Jun 2007 11:49:59 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Jaehwan Kim <jaehwan@vidiator.com>
Subject: Re: [AVT] Identifying a Frame from the NAL units
References: <317911.16047.qm@web42109.mail.mud.yahoo.com>	<p062408c8c2a90be9b7f9@[17.202.35.52]>
	<FE6A9D3F2979884280CE0F5F5185517B50182A@kor1corpmail01.mediator.com>
In-Reply-To: <FE6A9D3F2979884280CE0F5F5185517B50182A@kor1corpmail01.mediator.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Jun 2007 09:49:59.0142 (UTC)
	FILETIME=[DB29A860:01C7BA32]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: Dave Singer <singer@apple.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

Jaehwan Kim skrev:
> Hi,
> Yes, generally Market is like that.
> However, for H.264 RTPPayload format and RTP marker bit:
> 
> A few years ago in IMTC, we had informal technical discussion about
> this:
> 
>    In case of H.264, the meaning of RTP Marker bit seems unclear.
>    Rather than following legacy, we should follow H.264 payload format.
> 
> If we make a future H.264 RFC, this should be clarified.
> 

Hi,

Please, explain which part of the text in RFC 3984 that is unclear.

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 Fri Jun 29 07:39: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 1I4EpN-00067m-9E; Fri, 29 Jun 2007 07:39:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4EpL-00065W-OE
	for avt@ietf.org; Fri, 29 Jun 2007 07:39:51 -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 1I4Eoc-0006nx-D7 for avt@ietf.org; Fri, 29 Jun 2007 07:39:51 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Fri, 29 Jun 2007 07:39:06 -0400
To: "Jaehwan Kim" <jaehwan@vidiator.com>
Subject: Re: [AVT] Identifying a Frame from the NAL units
References: <317911.16047.qm@web42109.mail.mud.yahoo.com>
	<p062408c8c2a90be9b7f9@[17.202.35.52]>
	<FE6A9D3F2979884280CE0F5F5185517B50182A@kor1corpmail01.mediator.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Fri, 29 Jun 2007 07:39:04 -0400
In-Reply-To: <FE6A9D3F2979884280CE0F5F5185517B50182A@kor1corpmail01.mediator.com>
	(Jaehwan Kim's message of "Fri, 29 Jun 2007 14:39:06 +0900")
Message-ID: <ybu8xa37zxj.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: 29 Jun 2007 11:39:06.0087 (UTC)
	FILETIME=[19722F70:01C7BA42]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: Dave Singer <singer@apple.com>, IETF 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

"Jaehwan Kim" <jaehwan@vidiator.com> writes:
>Hi,
>Yes, generally Market is like that.
>However, for H.264 RTPPayload format and RTP marker bit:
>
>A few years ago in IMTC, we had informal technical discussion about
>this:
>
>   In case of H.264, the meaning of RTP Marker bit seems unclear.
>   Rather than following legacy, we should follow H.264 payload format.
>
>If we make a future H.264 RFC, this should be clarified.

I don't see any unclarity:

>Marker bit (M): 1 bit : Set for the very last packet of the access 
>unit indicated by the RTP timestamp

However, you don't *need* to use the Mark bit to reassemble H.264 RTP
packets into NALUs to pass to a decoder (certainly not for packetization
modes 0 or 1), at least if the de-packetizer knows it's H.264.  Mode 0 is
particularly easy.

-- 
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 Jun 29 08:04: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 1I4FDB-00071z-41; Fri, 29 Jun 2007 08:04:29 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3wng-0007xS-OU
	for avt@ietf.org; Thu, 28 Jun 2007 12:24:56 -0400
Received: from lumisoft.ee ([84.50.104.142] helo=mail.lumisoft.ee)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3wng-0004xd-9X
	for avt@ietf.org; Thu, 28 Jun 2007 12:24:56 -0400
Received: from 192.168.1.1 (192.168.1.1)
	by mail.lumisoft.ee with SMTP; Thu, 28 Jun 2007 16:12:17 GMT
Message-ID: <4683DE49.7080409@lumisoft.ee>
Date: Thu, 28 Jun 2007 19:14:01 +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: 8ac499381112328dd60aea5b1ff596ea
X-Mailman-Approved-At: Fri, 29 Jun 2007 08:04:27 -0400
Subject: [AVT] RTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?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,

Is this right place to ask RTP rfc 3550 related questions ?

Thanks

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



From avt-bounces@ietf.org Fri Jun 29 09:46: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 1I4Gnq-0000me-3U; Fri, 29 Jun 2007 09:46:26 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Gno-0000mU-Bi
	for avt@ietf.org; Fri, 29 Jun 2007 09:46:24 -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 1I4Gno-0004C0-0d
	for avt@ietf.org; Fri, 29 Jun 2007 09:46:24 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Fri, 29 Jun 2007 09:45:50 -0400
To: avt@ietf.org
Subject: Re: [AVT] RFC 2833/RFC 4733 and timestamps
References: <D6831742F069304FB1924B4160A493510226971B@ZMY16EXM66.ds.mot.com>
	<ybuy7i5scem.fsf@jesup.eng.wgate.com>
	<54e41b4b0706271014p39d0e6f3sf5d2e902f2046b0f@mail.gmail.com>
	<ybu7ipor8pb.fsf@jesup.eng.wgate.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Fri, 29 Jun 2007 09:45:50 -0400
In-Reply-To: <ybu7ipor8pb.fsf@jesup.eng.wgate.com> (Randell Jesup's message
	of "Thu, 28 Jun 2007 00:42:24 -0400")
Message-ID: <ybuzm2i7u29.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: 29 Jun 2007 13:45:50.0744 (UTC)
	FILETIME=[CE2CC180:01C7BA53]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
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

One other thing about RFC 2833/4733:

There's a bunch of implications that there can't be an overlap between DTMF
events, and other implications that they can.  Which is correct?  I realize
that in the analog DTMF world, two (or especially more) simultaneous DTMF
digits may not be possible to (properly) recognize.  But with a direct IP
endpoint, overlapping digits certainly can be recognized and sent.

My guess is that sending overlapped DTMF events would seriously confuse
many gateways and IVR systems, though others might happen to handle it.

>From RFC 4733:

   Typically, rather than a series of tone signals each with its own
   meaning, the content will consist of a single tone played out
   continuously or a single sequence of tones and possibly silence,
   repeated cyclically for some period of time.
(implies no overlap)

   Sending of a packet with the E bit set is OPTIONAL if the packet
   reports two events that are defined as mutually exclusive states, or
   if the final packet for one state is immediately followed by a packet
   reporting a mutually exclusive state.  (For events defined as states,
   the appearance of a mutually exclusive state implies the end of the
   previous state.)

(Note that DTMF digits are not states, they are type "tone").  Implies
overlap for tones.

   2.5.1.5.  Packing Multiple Events into One Packet

   Multiple named events can be packed into a single RTP packet if and
   only if the events are consecutive and contiguous, i.e., occur
   without overlap and without pause between them, and if the last event
   packed into a packet occurs quickly enough to avoid excessive delays
   at the receiver.

   This approach is similar to having multiple frames of frame-based
   audio in one RTP packet.

   The constraint that packed events not overlap implies that events
   designated as states can be followed in a packet only by other state
   events that are mutually exclusive to them.  The constraint itself is
   needed so that the beginning time of each event can be calculated at
   the receiver.

Implies overlap

   In the first algorithm, the receiver simply places a tone of the
   given duration in the audio playout buffer at the location indicated
   by the timestamp.  As additional packets are received that extend the
   same tone, the waveform in the playout buffer is extended
   accordingly. 

Implies no overlap

   Alternatively, the receiver can start a tone and play it until one of
   the following occurs:

   o  it receives a packet with the E bit set;

   o  it receives the next tone, distinguished by a different timestamp
      value (noting that new segments of long-duration events also
      appear with a new timestamp value);

   o  it receives an alternative non-event media stream (assuming none
      was being received while the event stream was active); or

Strongly implies no overlap

   2.5.2.3.  Long-Duration Events

   If an event report is received with duration equal to the maximum
   duration expressible in the duration field (0xFFFF) and the E bit for
   the report is not set, the event report may mark the end of a segment
   generated according to the procedures of Section 2.5.1.3.  If another
   report for the same event type is received, the receiver MUST compare
   the RTP timestamp for the new event with the sum of the RTP timestamp
   of the previous report plus the duration (0xFFFF).  The receiver uses
   the absence of a gap between the events to detect that it is
   receiving a single long-duration event.

Implies overlap

-- 
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 Jun 29 11:49: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 1I4IiS-0005dL-W4; Fri, 29 Jun 2007 11:49:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4IiR-0005b3-1G
	for avt@ietf.org; Fri, 29 Jun 2007 11:48:59 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4Ihw-0006fy-M2
	for avt@ietf.org; Fri, 29 Jun 2007 11:48:59 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:49455)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1I4Iht-0000jK-Sn; Fri, 29 Jun 2007 16:48:25 +0100
In-Reply-To: <B38DDC63-4950-4909-999B-4F22EABEBC6B@csperkins.org>
References: <A5148FAE-9197-4824-87C4-EF54767552F3@cisco.com>
	<18CAE473-3A37-49E0-8F68-CC30629DB2EA@csperkins.org>
	<BC4EE9F5-5F44-4BCC-9CA2-4CB3E684DF71@cisco.com>
	<B38DDC63-4950-4909-999B-4F22EABEBC6B@csperkins.org>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <1D0B4CF4-4A9E-4720-B227-6330641C749E@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Re: TLS-SRTP internet draft as a WG item in AVT
Date: Fri, 29 Jun 2007 16:48:24 +0100
To: AVT WG <avt@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Cc: Cullen Jennings <fluffy@cisco.com>, Roni Even <roni.even@polycom.co.il>,
	David McGrew <mcgrew@cisco.com>,
	Tom Taylor <tom.taylor@rogers.com>, Dan Wing <dwing@cisco.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

There were no objections, therefore this draft is accepted as an AVT  
work item.
Colin



On 27 Jun 2007, at 10:59, Colin Perkins wrote:
> David, All,
>
> That's fine. We therefore propose to accept this draft as an AVT  
> work item, with the milestone listed. If there are any objections  
> to this plan, please state them by 29th June 2007.
>
> Colin
>
>
>
>
>
> On 26 Jun 2007, at 22:05, David McGrew wrote:
>> Hi Colin,
>>
>> how does this milestone sound?  "December 2007 Submit TLS-SRTP for  
>> Proposed Standard"   Perhaps I'm aggressive in expecting us to  
>> have the draft ready before the Vancouver meeting; we could push  
>> it back to March 2008.
>>
>> David
>>
>> On Jun 26, 2007, at 4:00 AM, Colin Perkins wrote:
>>
>>> Hi David,
>>>
>>> What milestone(s) do you see this work adding to the AVT charter,  
>>> if accepted?
>>>
>>> Colin
>>>
>>>
>>>
>>>
>>> On 20 Jun 2007, at 21:54, David McGrew wrote:
>>>> Hi Colin, Roni, and Tom,
>>>>
>>>> I would like to ask that draft-mcgrew-tls-srtp be taken up as a  
>>>> working group action item in AVT, as part the plan for carrying  
>>>> forward the RTPSEC work (as per Cullen's email of May 11 to the  
>>>> rtpsec list).   I would like to continue on as an author of this  
>>>> work, and Eric as agreed to do the same.  There are a small  
>>>> number of minor open issues which I expect can be wrapped up  
>>>> quickly:
>>>>
>>>> 1.  The draft needs to be clarified so that, in the Symmetric  
>>>> RTP case, only one handshake is needed.
>>>>
>>>> 2.  Section 3.6.2.1 needs to be resolved to either decide on a  
>>>> "symmetry breaking" rule or not.  It may be desirable to have  
>>>> such a rule to handle cases in which the signaling system can't  
>>>> tell a device which should act as client and which should act as  
>>>> server.   This would allow opportunistic probing, i.e. a TLS- 
>>>> SRTP implementation could attempt to find out whether another  
>>>> RTP implementation supports TLS-SRTP, absent any help from  
>>>> signaling.
>>>>
>>>> 3.  The "single DTLS session per SRTP session" issue needs to be  
>>>> decided, and Appendix A should then be removed from the draft.
>>>>
>>>> 4.  It should be decided to use, or not to use the "TLS  
>>>> Extractor", and Section 3.3 should be rewritten accordingly.
>>>>
>>>> 5.  The duplicate list of srtp profiles needs to be eliminated.
>>>>
>>>> Best regards,
>>>>
>>>> David
>>>>
>>>> --
>>>>
>>>> p.s. - here's the AVT-specific part of Cullen note, so that you  
>>>> don't need to dig it out of your mailbox: "AVT - Describe how  
>>>> DTLS is used to key SRTP and how SRTP is used in combination  
>>>> with DTLS. This includes the issues of multiplexing DTLS and  
>>>> SRTP on one port. draft-mcgrew-tls-srtp will be the starting  
>>>> draft for this."
>>>
>>>
>>>
>>> -- 
>>> Colin Perkins
>>> http://csperkins.org/
>>
>> _______________________________________________
>> 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



-- 
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 Jun 29 13:51: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 1I4Kct-0000k8-Iw; Fri, 29 Jun 2007 13:51:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Kcs-0000jI-JZ
	for avt@ietf.org; Fri, 29 Jun 2007 13:51:22 -0400
Received: from smtp108.rog.mail.re2.yahoo.com ([68.142.225.206])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1I4Kby-0003r0-0f
	for avt@ietf.org; Fri, 29 Jun 2007 13:51:22 -0400
Received: (qmail 17877 invoked from network); 29 Jun 2007 17:50:25 -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;
	b=qpuaK2738hKV6WwTJ+JrsKMs/vuFuAbSHmF75yLE7mdAtIMvOeoEaozQyUQT7pAxi4YQ7QfxwWHC4QrbT+78GsxYWIEhs0Tmy8qYUtTRGlf+7YprjdW/xt66+Hq2ne4K4UcgexYTQ3SyOIDOkR0J6oXuF/Ht5yaxTNwCQAw2Fqc=
	; 
Received: from unknown (HELO ?192.168.0.100?)
	(tom.taylor@rogers.com@74.105.35.229 with plain)
	by smtp108.rog.mail.re2.yahoo.com with SMTP; 29 Jun 2007 17:50:25 -0000
X-YMail-OSG: x3swonEVM1nij9XlHwvCoWrESWS0BP75AbjZAoc3MRzM_kkDtBcUtuRCMBdqtUA6vA--
Message-ID: <468546CB.1090608@rogers.com>
Date: Fri, 29 Jun 2007 13:52:11 -0400
From: Tom Taylor <tom.taylor@rogers.com>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>
Content-Type: multipart/mixed; boundary="------------040909020706040101040408"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9e5c23589e6cce06555030c0194c9e2b
Subject: [AVT] PROTO writeup for draft-ietf-avt-rtp-and-rtcp-mux-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

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

Attached.  A request for publication is being forwarded to the IESG.

Tom Taylor

--------------040909020706040101040408
Content-Type: text/plain;
 name="RTP-RTCP Mux PROTO-upd.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="RTP-RTCP Mux PROTO-upd.txt"

PROTO Writeup for draft-ietf-avt-rtp-and-rtcp-mux-05.txt

Document history: see end of this writeup.

   (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?

       Tom Taylor. I believe this version is ready.

   (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 was announced informally to the BEHAVE and MMUSIC Working
       Groups. Prior to that announcement, an MMUSIC Chair commented on the draft,
       ICE from version 14 onwards has mentioned it, and the Chair of the BEHAVE
       Working Group has been aware of it. Because RTP/RTCP multiplexing could
       affect current QoS procedures developed by other SDOs, it is recommended
       that these SDOs (ETSI TISPAN, ITU-T Q. 5/11, PacketCable) be formally
       advised of the work.

   (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.

   (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 specific concerns. The issues raised during WG discussion (as
       enumerated below under "Document History") have all been dealt with.
       No related IPR disclosure.

   (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?

       The list and meeting discussions involved a satisfactory number of people,
       and did their job in raising and resolving issues. The document brought
       about a discussion of architectural principles in San Diego, since it
       represents a change to the RTP/RTCP architecture. The discussion concluded
       that the potential benefits were worth the change. The document drew no
       comments in AVT Working Group Last Call, but the issues raised in earlier
       discussion had already been dealt with at that point. 

   (1.f)  Has anyone threatened an appeal or otherwise indicated extreme
          discontent?  If so, please summarize 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?  If the document
          does not already indicate its intended status at the top of
          the first page, please indicate the intended status here.

       Nits noted on the tools /avt page for this draft:

         ** Obsolete normative reference: RFC 2032 (ref. '3') (Obsoleted by RFC 4587)
            The reference to RFC 2032 is intentional.
            
            A later version of draft-ietf-mmusic-ice exists.

   (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 are split as required. There is a normative dependency on
       draft-ietf-avt-rtcpssm, which is supposed to be ready but needs further
       editorial work. The Chairs will work to bring this into WGLC ASAP.

   (1.i)  Has the Document Shepherd verified that the document's IANA
          Considerations 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 the Document
          Shepherd conferred with the Responsible Area Director so that
          the IESG can appoint the needed Expert during IESG Evaluation?

       One new SDP attribute registered, properly referred to RFC 4566 for
       the registry and procedurtes. 

   (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
             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.

          Working Group Summary
             This document represents a solid consensus of the AVT Working Group,
             with informal concurrence of the MMUSIC and BEHAVE Working Groups.
             Following the initial proposal, the major issue subsequently considered
             and resolved was how to negotiate the multiplexing capability and
             achieve fail-safe behaviour.  The decision was to provide a new SDP
             attribute to signal the multiplexing capability explicitly. There was
             also some discussion of how to signal bandwidth requirements.  The
             outcome was a decision to include allowance for RTCP traffic in the
             b=AS: value. 

          Document Quality
             The document has attracted considerable interest because it makes NAT
             traversal easier.  Jonathan Rosenberg, author of the ICE document,
             reviewed the proposal in terms of its interaction with ICE and provided
             related text.  Randell Jesup deserves special mention for his careful
             reviews of successive versions of the document and persistence in
             analysis of the associated signalling issues.

          Personnel
             Document Shepherd was Tom Taylor.
             Responsible Area Director was Cullen Jennings.

---------------------------
Document history:

       draft-perkins-dccp-rtp-00.txt, published 17-10-2005, mentions possibility
       of multiplexing RTP and RTCP onto the same port, but notes that care
       would be required to do it right.

       draft-perkins-avt-rtp-and-rtcp-mux-00.txt published 8-9-2006.

         Hadriel Kaplan <HKaplan@acmepacket.com> had specific comments (thread
         "Comments on draft-perkins-avt-rtp-and-rtcp-mux-00.txt" beginning 
         11-9-2006) on the following points:
          -- why caution needed on PT values;
          -- effect on bandwidth values coded in b=AS line.
         Randell Jesup <rjesup@wgate.com> agreed with the relevance of these
         points and had a general suggestion on the bandwidth issue. Harikishan
         Desineni<hdesinen@qualcomm.com> made a more specific suggestion. Colin
         Perkins agreed to clarify his concern over potential payload type 
         clashes and proposed to accept the essence of Harikishan's proposal for 
         calculation of the b=AS value.

         Discussion between Randell Jesup and Hadriel Kaplan (main thread 
         "Fwd: I-D ACTION:draft-perkins-avt-rtp-and-rtcp-mux-00.txt" beginning 
         with Colin's announcement 8-9-2006) on issues with the overloading of 
         the a=rtcp: attribute in SDP signalling when middleboxes fail to 
         understand the signalling. Randell urged a more explicit signalling of
         the proposed use of multiplexing.

         A comment by Gunnar Hellstrom (main thread) on the additional need to 
         multiplex different media streams over the same port to further 
         simplify NAT traversal generated a side discussion not related to the 
         specific topic of the draft. Gunnar asked that the draft make clear
         that it did not cover this point.

         New thread ("Comments on draft-perkins-avt-rtp-and-rtcp-mux-00.txt"
         beginning 21-9-2006) initiated by Roni Even. Points made:
          -- advantage of multiplexing is that RTCP messages serve as NAT 
             keep-alive;
          -- need to address case of one-way RTP flows;
          -- may be an use case for multiplexing at one end only;
          -- will it be possible to move in and out of the multiplexing state 
             through appropriate exchange of signalling?
          -- prefers that b=AS and b=TIAS just specify RTP, not RTCP bandwidth;
          -- separation of RTP and RTCP on different ports facilitates network
             giving of priority treatment to RTP over RTCP.
         Randell Jesup responded, suggesting that one-way RTP flows did not need 
         special treatment, discussing the single-ended case and whether it 
         could happen, and agreeing that it should be possible to renegotiate 
         the use or non-use of multiplexing in mid-session. Colin agreed with 
         Randell that one-way RTP flows did not need special treatment. He was 
         of the opinion that symmetric use of multiplexing should be forced, 
         bearing in mind the problems already posed by asymmetric RTP.

         In an unrelated point on the same thread, Stephan Wenger 
         <stewe@stewe.org> wondered whether RTCP multiplexing would have a 
         negative impact on compression (RoHC). Colin responded that he would 
         add something on this topic in the next version of the draft.

       draft-perkins-avt-rtp-and-rtcp-mux-01.txt published 25-9-2006.

         Gunnar Hellstrom pronounced himself content with the clarification of 
         scope provided in the new version.

         Randell Jesup again questioned why it was worth restricting payload 
         type numbers. He also noted that when a=rtcp: is returned but shows a 
         different port number than the RTP stream, "rejecting" the session as 
         required by the draft involves killing the session or doing an 
         UPDATE/re-INVITE. Finally, he made alternative suggestions for setting 
         the b=AS: value, pointing out that mid-stream devices unaware of RTCP 
         multiplexing would reserve too little bandwidth with the procedure 
         Desineni asked for clarification of Randell's comments on the QOS 
         issue, and Randell gave an example involving DOCSIS-controlled cable
         bandwidth.
         
         Colin responded to Randell, agreeing that the payload type restrictions
         did not buy much, but suggesting areas where implementations based on
         misinterpretion of the specifications might send non-compound packets.
         He agreed there was a signalling problem when the far end failed to act
         correctly, and this was an open issue. He was concerned that including
         RTCP bandwidth in the b=AS: value as Randell suggested would break
         compatibility.

         Behind the scenes: agreed as a charter item (Cullen Jennings,
         20-9-2006).

       draft-ietf-avt-rtp-and-rtcp-mux-00.txt published 2-10-2006.

         Randell Jessup (2-10-2006) continued his analysis of the proper 
         procedure when the far end fails to assign the same port to RTP and 
         RTCP. He also continued to argue for inclusion of RTCP bandwidth in the 
         b=AS: value. [In fact, the new -00 version and subsequent versions do
         so.]
 
       draft-ietf-avt-rtp-and-rtcp-mux-01.txt published 26-10-2006. 

         Colin Perkins noted (27-10-2006) that it covered:
           -- implications when the device receiving the offer understands
              the a=rtcp: attribute, but does not understand RTCP multiplexing;
           -- expanded discussion of interactions with ICE;
           -- expanded discussion of SIP forking;
           -- clarified failure behaviour during offer/answer negotiation;
           -- added "Interactions with Header Compression" section.
        

         Discussion in San Diego (7-11-2006) resulted in a resolution of the 
         signalling issue. A new attribute would be sent in the offer to 
         indicate use of multiplexing (as originally proposed by Randell Jesup). 
         If this attribute is understood, the receiver would ignore the a=rtcp: 
         attribute. The latter would be restricted to a fallback role. 
         Discussion also examined the broader question of whether RTCP 
         multiplexing offered real value. It was agreed that its main value 
         would be in port savings on the TURN server.

       draft-ietf-avt-rtp-and-rtcp-mux-02.txt published 20-11-2006.

         Signalling section updated as agreed in San Diego. ICE discussion
         considerably expanded. Improvements in other sections.

       draft-ietf-avt-rtp-and-rtcp-mux-03.txt published 12-5-2006.
         
         Editorial changes only.

       draft-ietf-avt-rtp-and-rtcp-mux-04.txt published 8-3-2007.

         Added requirement that multiplexing be done for unicast sessions only 
         when previously signalled. Changed SHOULD NOT to MUST NOT multiplex if 
         answer does not indicate acceptance of multiplexing.

       Working Group Last Call announced 18-3-2007, to conclude 7-4-2007. No 
       comments received. Notice extended to the BEHAVE and MMUSIC Working 
       Groups prior to completion of this writeup. No comments received in the
       ensuing week. 

       draft-ietf-avt-rtp-and-rtcp-mux-05.txt published 21-5-2007.

         Fixed some nits.


                                        -30-

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

--------------040909020706040101040408--




From avt-bounces@ietf.org Fri Jun 29 17:17: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 1I4Nqf-0006VD-IL; Fri, 29 Jun 2007 17:17:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Nqd-0006Rw-R0
	for avt@ietf.org; Fri, 29 Jun 2007 17:17:47 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4NpT-0000wL-7W
	for avt@ietf.org; Fri, 29 Jun 2007 17:17:47 -0400
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:62255
	helo=[192.168.0.4])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1I4NpS-0006EV-JS for avt@ietf.org; Fri, 29 Jun 2007 22:16:34 +0100
Mime-Version: 1.0 (Apple Message framework v752.2)
References: <E1I47eL-0004eM-K8@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <DF01455B-E392-4E30-921B-685DC6A7B0C6@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Fri, 29 Jun 2007 22:16:33 +0100
To: AVT WG <avt@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Subject: [AVT] Fwd: Internet-Drafts Submission Cutoff Dates for the 69th
	IETF Meeting in Chicago, IL, USA 
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

FYI.

Begin forwarded message:
> Date: 29 June 2007 05:00:01 BDT
> To: ietf-announce@ietf.org
>
> There are two (2) Internet-Draft cutoff dates for the 69th
> IETF Meeting in Chicago, IL, USA:
>
> July 2nd: Cutoff Date for Initial (i.e., version -00)
> Internet-Draft Submissions
>
> All initial Internet-Drafts (version -00) must be submitted by Monday,
> July 2nd at 9:00 AM ET. As always, all initial submissions with a
> filename beginning with "draft-ietf" must be approved by the
> appropriate WG Chair before they can be processed or announced.  The
> Secretariat would appreciate receiving WG Chair approval by Monday,
> June 25th at 9:00 AM ET.
>
> July 9th: Cutoff Date for Revised (i.e., version -01 and higher)
> Internet-Draft Submissions
>
> All revised Internet-Drafts (version -01 and higher) must be submitted
> by Monday, July 9th at 9:00 AM ET.
>
> Initial and revised Internet-Drafts received after their respective
> cutoff dates will not be made available in the Internet-Drafts
> directory or announced until on or after Monday, July 23rd at 9:00
> AM ET, when Internet-Draft posting resumes.  Please do not wait until
> the last minute to submit.
>
> Thank you for your understanding and cooperation. If you have any
> questions or concerns, then please send a message to
> internet-drafts@ietf.org.
>
> The IETF Secretariat
>
> FYI: The Internet-Draft cutoff dates as well as other significant  
> dates
> for the 69th IETF Meeting can be found at http://www.ietf.org/ 
> meetings/cutoff_dates_69.html.



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



