From mmusic-bounces@ietf.org  Tue Feb  1 04:20:40 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06072
	for <mmusic-web-archive@ietf.org>; Tue, 1 Feb 2005 04:20:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CvuVJ-0003ay-FU
	for mmusic-web-archive@ietf.org; Tue, 01 Feb 2005 04:39:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CvuBJ-0005oM-Sp; Tue, 01 Feb 2005 04:18:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cvu8m-0005Qr-9R
	for mmusic@megatron.ietf.org; Tue, 01 Feb 2005 04:16:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05863
	for <mmusic@ietf.org>; Tue, 1 Feb 2005 04:16:07 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CvuQt-0003US-A2
	for mmusic@ietf.org; Tue, 01 Feb 2005 04:34:52 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:62286
	helo=[192.168.0.2])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1Cvu8F-00031L-Ql; Tue, 01 Feb 2005 09:15:35 +0000
In-Reply-To: <EB5072E4-67E8-11D9-B484-000A957FC5F2@csperkins.org>
References: <EB5072E4-67E8-11D9-B484-000A957FC5F2@csperkins.org>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <02d9fc4c87d6e0cffb65cf41fd63fa93@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Working group last call:
	draft-ietf-mmusic-connection-precon-01.txt
Date: Tue, 1 Feb 2005 09:15:27 +0000
To: IETF MMUSIC Working Group <mmusic@ietf.org>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit
Cc: =?ISO-8859-1?Q?J=F6rg_Ott?= <jo@tzi.uni-bremen.de>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit

On 16 Jan 2005, at 18:03, Colin Perkins wrote:
> This is to announce a working group last call on the 
> Connection-Establishment Preconditions work 
> <draft-ietf-mmusic-connection-precon-01.txt>. Please send any final 
> comments to the mailing list by 31 January 2005. If no substantive 
> technical issues are raised by this time, we intend to request the 
> IESG to publish this as a proposed standard RFC.

This working group last call period has ended. There were no 
objections, so we will request the IESG publish the draft.

Colin


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


From mmusic-bounces@ietf.org  Tue Feb  1 16:45:37 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00497
	for <mmusic-web-archive@ietf.org>; Tue, 1 Feb 2005 16:45:36 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cw68K-0000Dh-S6
	for mmusic-web-archive@ietf.org; Tue, 01 Feb 2005 17:04:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cw5Oh-0001aX-Gn; Tue, 01 Feb 2005 16:17:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cw4yB-0004Ht-AE; Tue, 01 Feb 2005 15:49:55 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18280;
	Tue, 1 Feb 2005 15:49:52 -0500 (EST)
Message-Id: <200502012049.PAA18280@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 01 Feb 2005 15:49:52 -0500
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdescriptions-09.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

	Title		: Session Description Protocol Security Descriptions 
			  for Media Streams
	Author(s)	: F. Andreasen, et al. 
	Filename	: draft-ietf-mmusic-sdescriptions-09.txt
	Pages		: 37
	Date		: 2005-2-1
	
This document defines a Session Description Protocol (SDP) 
   cryptographic attribute for unicast media streams.  The attribute 
   describes a cryptographic key and other parameters, which serve to 
   configure security for a unicast media stream in either a single 
   message or a roundtrip exchange.  The attribute can be used with a 
   variety of SDP media transports and this document defines how to use 
   it for the Secure Real-time Transport Protocol (SRTP) unicast media 
   streams.  The SDP crypto attribute requires the services of a data 
   security protocol to secure the SDP message.

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

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


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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-sdescriptions-09.txt

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

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


--OtherAccess--

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

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

--NextPart--





From mmusic-bounces@ietf.org  Tue Feb  1 19:50:25 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23833
	for <mmusic-web-archive@ietf.org>; Tue, 1 Feb 2005 19:50:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cw91D-0006I0-Rg
	for mmusic-web-archive@ietf.org; Tue, 01 Feb 2005 20:09:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cw8hn-0000m0-G9; Tue, 01 Feb 2005 19:49:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cw8gI-0000NL-6M
	for mmusic@megatron.ietf.org; Tue, 01 Feb 2005 19:47:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23667
	for <mmusic@ietf.org>; Tue, 1 Feb 2005 19:47:39 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cw8yY-0006Dx-0w
	for mmusic@ietf.org; Tue, 01 Feb 2005 20:06:34 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j120l7X16575; Tue, 1 Feb 2005 19:47:07 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <Y0S03PPW>; Tue, 1 Feb 2005 19:46:59 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF016F45D7@zrc2hxm0.corp.nortel.com>
From: "Francois Audet" <audet@nortel.com>
To: "'Jonathan Rosenberg'" <jdrosen@cisco.com>,
        "'IETF MMUSIC WG'"
	<mmusic@ietf.org>
Subject: RE: [MMUSIC] ICE feature - TCP alternates for a UDP stream
Date: Tue, 1 Feb 2005 19:46:45 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 6907f330301e69261fa73bed91449a20
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1805315327=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: f8184d7d4d1b986353eb58ea3e887935

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

--===============1805315327==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C508C0.AC63B529"

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

------_=_NextPart_001_01C508C0.AC63B529
Content-Type: text/plain

So you are saying that the media would be transported over RTP/TCP
to the TURN relay, and then to the other endpoint using another RTP/TCP
session, right?

And not and end-to-end RTP/TCP session between the two peers, right?




> -----Original Message-----
> From: mmusic-bounces@ietf.org 
> [mailto:mmusic-bounces@ietf.org] On Behalf Of Jonathan Rosenberg
> Sent: Thursday, January 27, 2005 10:43
> To: IETF MMUSIC WG
> Subject: [MMUSIC] ICE feature - TCP alternates for a UDP stream
> 
> 
> Folks,
> 
> In the past, we had considered whether or not to also apply 
> ICE to allow 
> a TCP session to be an alternate for a UDP one. We decided to 
> keep the 
> scope narrow, and not consider this.
> 
> However, in reality, I think there is an extremely pressing need for 
> this. In particular, there are many deployments where we 
> would like to 
> support SIP, but (for better or for worse), networks are only 
> allowing 
> outbound TCP connections. This is not a NAT issue so much as 
> a firewall 
> issue, but in this case the firewall is introducing a connectivity 
> problem of the sort that ICE was designed to address. As 
> such, I think 
> its in scope. If we defer this to a future document, I fear 
> we will get 
> implementations missing this feature and thus SIP/ICE clients 
> will find 
> themselves in situations where it STILL doesnt "just work", 
> despite the 
> fact that ICE is supposed to make it "just work".
> 
> Now, all of us agree, no doubt, that RTP over UDP is far 
> preferable to 
> RTP over TCP, but if TCP is all you can get working, TCP is 
> better than 
> nothing. ICE can serve a crucial role of figuring out, dynamically, 
> whether or not UDP can be made to work, and thus whether the lower 
> priority alternative of TCP, should be used.
> 
> So, here's how it would work. A client would include UDP local 
> addresses, STUn derived addresses, TURN derived (using UDP), and ALSO 
> TURN derived using TCP (recall that TURN supports TCP 
> connections). We 
> have a spec for RTP over TCP (draft-ietf-avt-rtp-framing-contrans), 
> which makes use of the comedia spec. The client would specify 
> that it is 
> passive. The INVITE is sent. The peer connects to this 
> (indicating that 
> it is active in its answer); that connection terminates on the TURN 
> relay used by the caller. The peer, as with any other 
> session, uses STUN 
> to check connectivity. The caller can then use STUN itself to verify 
> connectivity in its direction (presumably it would always 
> work in both 
> directions).
> 
> The nice thing is, by setting the priorities appropriately, this 
> connection would only get used if the other UDP choices fail. 
> That gives 
> us even further robustness.
> 
> Presumably this could also work for TLS, in which case the 
> TURN server 
> would terminate the TLS connection from the caller and from 
> the callee.
> 
> Specifying this isn't really hard. The main issue is just a grouping 
> one. We need to be able to apply the comedia parameters to 
> candidates. 
> You can't just include them under the m-line, since then you 
> don't know 
> to what they apply. In any case, we don't really need or even want a 
> generic grouping framework here; I would HATE for this to be 
> used as an 
> alternative for negotiating codec parameters in yet another way. As 
> such, I would suggest merely extending the candidate line to 
> include the 
> transports and comedia information when needed.
> 
> Comments?
> 
> -Jonathan R.
> 
> 
> 
> -- 
> Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
> Director, Service Provider VoIP Architecture   Parsippany, NJ 
> 07054-2711
> Cisco Systems
> jdrosen@cisco.com                              FAX:   (973) 952-5050
> http://www.jdrosen.net                         PHONE: (973) 952-5000
> http://www.cisco.com
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 
> 

------_=_NextPart_001_01C508C0.AC63B529
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2658.2">
<TITLE>RE: [MMUSIC] ICE feature - TCP alternates for a UDP stream</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>So you are saying that the media would be transported over RTP/TCP</FONT>
<BR><FONT SIZE=2>to the TURN relay, and then to the other endpoint using another RTP/TCP</FONT>
<BR><FONT SIZE=2>session, right?</FONT>
</P>

<P><FONT SIZE=2>And not and end-to-end RTP/TCP session between the two peers, right?</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: mmusic-bounces@ietf.org </FONT>
<BR><FONT SIZE=2>&gt; [<A HREF="mailto:mmusic-bounces@ietf.org">mailto:mmusic-bounces@ietf.org</A>] On Behalf Of Jonathan Rosenberg</FONT>
<BR><FONT SIZE=2>&gt; Sent: Thursday, January 27, 2005 10:43</FONT>
<BR><FONT SIZE=2>&gt; To: IETF MMUSIC WG</FONT>
<BR><FONT SIZE=2>&gt; Subject: [MMUSIC] ICE feature - TCP alternates for a UDP stream</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Folks,</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; In the past, we had considered whether or not to also apply </FONT>
<BR><FONT SIZE=2>&gt; ICE to allow </FONT>
<BR><FONT SIZE=2>&gt; a TCP session to be an alternate for a UDP one. We decided to </FONT>
<BR><FONT SIZE=2>&gt; keep the </FONT>
<BR><FONT SIZE=2>&gt; scope narrow, and not consider this.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; However, in reality, I think there is an extremely pressing need for </FONT>
<BR><FONT SIZE=2>&gt; this. In particular, there are many deployments where we </FONT>
<BR><FONT SIZE=2>&gt; would like to </FONT>
<BR><FONT SIZE=2>&gt; support SIP, but (for better or for worse), networks are only </FONT>
<BR><FONT SIZE=2>&gt; allowing </FONT>
<BR><FONT SIZE=2>&gt; outbound TCP connections. This is not a NAT issue so much as </FONT>
<BR><FONT SIZE=2>&gt; a firewall </FONT>
<BR><FONT SIZE=2>&gt; issue, but in this case the firewall is introducing a connectivity </FONT>
<BR><FONT SIZE=2>&gt; problem of the sort that ICE was designed to address. As </FONT>
<BR><FONT SIZE=2>&gt; such, I think </FONT>
<BR><FONT SIZE=2>&gt; its in scope. If we defer this to a future document, I fear </FONT>
<BR><FONT SIZE=2>&gt; we will get </FONT>
<BR><FONT SIZE=2>&gt; implementations missing this feature and thus SIP/ICE clients </FONT>
<BR><FONT SIZE=2>&gt; will find </FONT>
<BR><FONT SIZE=2>&gt; themselves in situations where it STILL doesnt &quot;just work&quot;, </FONT>
<BR><FONT SIZE=2>&gt; despite the </FONT>
<BR><FONT SIZE=2>&gt; fact that ICE is supposed to make it &quot;just work&quot;.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Now, all of us agree, no doubt, that RTP over UDP is far </FONT>
<BR><FONT SIZE=2>&gt; preferable to </FONT>
<BR><FONT SIZE=2>&gt; RTP over TCP, but if TCP is all you can get working, TCP is </FONT>
<BR><FONT SIZE=2>&gt; better than </FONT>
<BR><FONT SIZE=2>&gt; nothing. ICE can serve a crucial role of figuring out, dynamically, </FONT>
<BR><FONT SIZE=2>&gt; whether or not UDP can be made to work, and thus whether the lower </FONT>
<BR><FONT SIZE=2>&gt; priority alternative of TCP, should be used.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; So, here's how it would work. A client would include UDP local </FONT>
<BR><FONT SIZE=2>&gt; addresses, STUn derived addresses, TURN derived (using UDP), and ALSO </FONT>
<BR><FONT SIZE=2>&gt; TURN derived using TCP (recall that TURN supports TCP </FONT>
<BR><FONT SIZE=2>&gt; connections). We </FONT>
<BR><FONT SIZE=2>&gt; have a spec for RTP over TCP (draft-ietf-avt-rtp-framing-contrans), </FONT>
<BR><FONT SIZE=2>&gt; which makes use of the comedia spec. The client would specify </FONT>
<BR><FONT SIZE=2>&gt; that it is </FONT>
<BR><FONT SIZE=2>&gt; passive. The INVITE is sent. The peer connects to this </FONT>
<BR><FONT SIZE=2>&gt; (indicating that </FONT>
<BR><FONT SIZE=2>&gt; it is active in its answer); that connection terminates on the TURN </FONT>
<BR><FONT SIZE=2>&gt; relay used by the caller. The peer, as with any other </FONT>
<BR><FONT SIZE=2>&gt; session, uses STUN </FONT>
<BR><FONT SIZE=2>&gt; to check connectivity. The caller can then use STUN itself to verify </FONT>
<BR><FONT SIZE=2>&gt; connectivity in its direction (presumably it would always </FONT>
<BR><FONT SIZE=2>&gt; work in both </FONT>
<BR><FONT SIZE=2>&gt; directions).</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; The nice thing is, by setting the priorities appropriately, this </FONT>
<BR><FONT SIZE=2>&gt; connection would only get used if the other UDP choices fail. </FONT>
<BR><FONT SIZE=2>&gt; That gives </FONT>
<BR><FONT SIZE=2>&gt; us even further robustness.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Presumably this could also work for TLS, in which case the </FONT>
<BR><FONT SIZE=2>&gt; TURN server </FONT>
<BR><FONT SIZE=2>&gt; would terminate the TLS connection from the caller and from </FONT>
<BR><FONT SIZE=2>&gt; the callee.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Specifying this isn't really hard. The main issue is just a grouping </FONT>
<BR><FONT SIZE=2>&gt; one. We need to be able to apply the comedia parameters to </FONT>
<BR><FONT SIZE=2>&gt; candidates. </FONT>
<BR><FONT SIZE=2>&gt; You can't just include them under the m-line, since then you </FONT>
<BR><FONT SIZE=2>&gt; don't know </FONT>
<BR><FONT SIZE=2>&gt; to what they apply. In any case, we don't really need or even want a </FONT>
<BR><FONT SIZE=2>&gt; generic grouping framework here; I would HATE for this to be </FONT>
<BR><FONT SIZE=2>&gt; used as an </FONT>
<BR><FONT SIZE=2>&gt; alternative for negotiating codec parameters in yet another way. As </FONT>
<BR><FONT SIZE=2>&gt; such, I would suggest merely extending the candidate line to </FONT>
<BR><FONT SIZE=2>&gt; include the </FONT>
<BR><FONT SIZE=2>&gt; transports and comedia information when needed.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Comments?</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; -Jonathan R.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; -- </FONT>
<BR><FONT SIZE=2>&gt; Jonathan D. Rosenberg, Ph.D.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 600 Lanidex Plaza</FONT>
<BR><FONT SIZE=2>&gt; Director, Service Provider VoIP Architecture&nbsp;&nbsp; Parsippany, NJ </FONT>
<BR><FONT SIZE=2>&gt; 07054-2711</FONT>
<BR><FONT SIZE=2>&gt; Cisco Systems</FONT>
<BR><FONT SIZE=2>&gt; jdrosen@cisco.com&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FAX:&nbsp;&nbsp; (973) 952-5050</FONT>
<BR><FONT SIZE=2>&gt; <A HREF="http://www.jdrosen.net" TARGET="_blank">http://www.jdrosen.net</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PHONE: (973) 952-5000</FONT>
<BR><FONT SIZE=2>&gt; <A HREF="http://www.cisco.com" TARGET="_blank">http://www.cisco.com</A></FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; _______________________________________________</FONT>
<BR><FONT SIZE=2>&gt; mmusic mailing list</FONT>
<BR><FONT SIZE=2>&gt; mmusic@ietf.org</FONT>
<BR><FONT SIZE=2>&gt; <A HREF="https://www1.ietf.org/mailman/listinfo/mmusic" TARGET="_blank">https://www1.ietf.org/mailman/listinfo/mmusic</A></FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C508C0.AC63B529--


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

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

--===============1805315327==--



From mmusic-bounces@ietf.org  Wed Feb  2 01:48:02 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05937
	for <mmusic-web-archive@ietf.org>; Wed, 2 Feb 2005 01:48:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CwEbL-0005XC-Ba
	for mmusic-web-archive@ietf.org; Wed, 02 Feb 2005 02:06:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CwEHc-0005rq-W0; Wed, 02 Feb 2005 01:46:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CwEHF-0005gf-28
	for mmusic@megatron.ietf.org; Wed, 02 Feb 2005 01:46:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05777
	for <mmusic@ietf.org>; Wed, 2 Feb 2005 01:46:11 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwEZX-0005Sx-Ez
	for mmusic@ietf.org; Wed, 02 Feb 2005 02:05:08 -0500
Received: from sj-core-4.cisco.com (171.68.223.138)
	by sj-iport-5.cisco.com with ESMTP; 01 Feb 2005 22:48:11 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j126jb82027418;
	Tue, 1 Feb 2005 22:45:38 -0800 (PST)
Received: from [192.168.1.100] (che-vpn-cluster-1-107.cisco.com
	[10.86.240.107]) by mira-sjc5-d.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AHL43175; Tue, 1 Feb 2005 22:45:36 -0800 (PST)
Message-ID: <4200770F.5000509@cisco.com>
Date: Wed, 02 Feb 2005 01:45:35 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francois Audet <audet@nortel.com>
Subject: Re: [MMUSIC] ICE feature - TCP alternates for a UDP stream
References: <1ECE0EB50388174790F9694F77522CCF016F45D7@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF016F45D7@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit
Cc: "'IETF MMUSIC WG'" <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit



Francois Audet wrote:

> So you are saying that the media would be transported over RTP/TCP
> to the TURN relay, and then to the other endpoint using another RTP/TCP
> session, right?

Yes.

> 
> And not and end-to-end RTP/TCP session between the two peers, right?

One could offer that up as an additional alternate, yes. In other words, 
just like the client would offer UDP alternates learned from STUN, TURN 
and local interfaces, so too they could offer TCP alternates learned 
from TURN and local interfaces. The latter, if it works, would result in 
a direct TCP connection from one user to the other. The former would end 
up with clients connecting through the TURN server.

-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

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


From mmusic-bounces@ietf.org  Wed Feb  2 02:58:23 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12517
	for <mmusic-web-archive@ietf.org>; Wed, 2 Feb 2005 02:58:23 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CwFhR-0007Er-D8
	for mmusic-web-archive@ietf.org; Wed, 02 Feb 2005 03:17:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CwFGQ-0001nx-1Z; Wed, 02 Feb 2005 02:49:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CwFEO-0001MT-D6
	for mmusic@megatron.ietf.org; Wed, 02 Feb 2005 02:47:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11242
	for <mmusic@ietf.org>; Wed, 2 Feb 2005 02:47:18 -0500 (EST)
Received: from goliath.siemens.de ([192.35.17.28])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwFWh-0006xA-R6
	for mmusic@ietf.org; Wed, 02 Feb 2005 03:06:16 -0500
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by goliath.siemens.de (8.12.6/8.12.6) with ESMTP id j127lDJH015127;
	Wed, 2 Feb 2005 08:47:13 +0100
Received: from MCHN070C (mhpaba5c.mchp.siemens.de [139.23.204.46])
	by mail3.siemens.de (8.12.6/8.12.6) with ESMTP id j127lCfs004781;
	Wed, 2 Feb 2005 08:47:13 +0100
From: "Steffen Fries" <steffen.fries@siemens.com>
Organization: Siemens AG
To: msec@securemulticast.org, mmusic@ietf.org
Date: Wed, 02 Feb 2005 08:47:05 +0100
MIME-Version: 1.0
Message-ID: <42009389.29093.181F2DF2@localhost>
Priority: normal
In-reply-to: <41FE4CAC.8060406@nortelnetworks.com>
X-mailer: Pegasus Mail for Windows (4.21c)
Content-description: Mail message body
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Cc: hannes Tschofenig <Hannes.Tschofenig@siemens.com>
Subject: [MMUSIC] Re: [MSEC] [Fwd: I-D
	ACTION:draft-ignjatic-msec-mikey-rsa-r-00.txt]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: steffen.fries@siemens.com
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0623562462=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d

--===============0623562462==
Content-type: text/html; charset=US-ASCII
Content-description: Mail message body
Content-Transfer-Encoding: 7BIT

<?xml  version="1.0" ?><html>
<head>
<title></title>
</head>
<body>
<div align="left"><font face="Courier New"><span style="font-size:10pt">Hi,</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">Hannes and me submitted a revision of the Bootstrapping TESLA 
Draft. We updated some text regarding the synchronization and 
added the IANA section. Feel free to send comments.</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">Regards</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160;&#160;Steffen</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">----------------------------------------------------------------</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">A New Internet-Draft is available from the on-line Internet-
Drafts directories.</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">This draft is a work item of the Multicast Security Working 
Group of the IETF.</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160;&#160;Title&#160;&#160;&#160;&#160;&#160;&#160;&#160;: Bootstrapping TESLA</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160;&#160;Author(s)&#160;&#160;&#160;: S. Fries, H. Tschofenig</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160;&#160;Filename&#160;&#160;&#160;&#160;: draft-ietf-msec-bootstrapping-tesla-00.txt</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160;&#160;Pages&#160;&#160;&#160;&#160;&#160;&#160;&#160;: 13</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160;&#160;Date&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;: 2005-1-18</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160;&#160;</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">With the Timed Efficient Stream Loss-tolerant Authentication 
protocol (TESLA) a protocol for providing source authentication 
in multicast scenarios was introduced.&#160; A mapping for TESLA to 
the Secure Real-time Transport Protocol (SRTP) has been 
published which assumes that some TESLA parameters are made 
available by out-of-band mechanisms.&#160; This document describes 
payloads for bootstrapping these parameters with the help of the 
Multimedia Internet KEYing (MIKEY) protocol.</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">A URL for this Internet-Draft is:</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">http://www.ietf.org/internet-drafts/draft-ietf-msec-
bootstrapping-tesla-00.txt</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">To remove yourself from the I-D Announcement list, send a 
message to i-d-announce-request at ietf.org with the word 
unsubscribe in the body of the message.&#160; </span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">You can also visit https://www1.ietf.org/mailman/listinfo/I-D-
announce to change your subscription settings.</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><br/>
</div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">Internet-Drafts are also available by anonymous FTP. Login with 
the username &quot;anonymous&quot; and a password of your e-mail address. 
After logging in, type &quot;cd internet-drafts&quot; and then &quot;get draft-
ietf-msec-bootstrapping-tesla-00.txt&quot;.</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">A list of Internet-Drafts directories can be found in</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">http://www.ietf.org/shadow.html </span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">or ftp://ftp.ietf.org/ietf/1shadow-sites.txt</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><br/>
</div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">Internet-Drafts can also be obtained by e-mail.</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">Send a message to:</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160;&#160;mailserv at ietf.org.</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">In the body type:</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160;&#160;&quot;FILE /internet-drafts/draft-ietf-msec-bootstrapping-
tesla-00.txt&quot;.</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160;&#160;</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">NOTE:&#160;The mail server at ietf.org can return the document in</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160;&#160;MIME-encoded form by using the &quot;mpack&quot; utility.&#160; To 
use </span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160; this feature, insert the command &quot;ENCODING mime&quot; before</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160; the &quot;FILE&quot;&#160;&#160;command.&#160; To decode the response(s), 
you will</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160; need &quot;munpack&quot; or MIME-compliant mail reader.&#160; Different</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160; MIME-compliant mail readers</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160;&#160;exhibit different behavior, especially when dealing with</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160;&#160;&quot;multipart&quot; MIME messages (i.e. documents which have been</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160; split&#160;up into multiple messages), so check your local</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160; documentation on&#160;&#160;how to manipulate these messages.</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">Below is the data which will enable a MIME compliant mail reader</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">implementation to automatically retrieve the ASCII version of 
the Internet-Draft.</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&lt;ftp://ftp.ietf.org/internet-drafts/draft-ietf-msec-
bootstrapping-tesla-00.txt&gt;</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">_______________________________________________</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">I-D-Announce mailing list</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">I-D-Announce at ietf.org</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">https://www1.ietf.org/mailman/listinfo/i-d-announce</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><br/></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">-----------------------------------------------------------</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160; Steffen Fries,&#160;&#160;&#160;&#160; Siemens AG, CT IC 3&#160;&#160;&#160;&#160;&#160;&#160;</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160; Otto-Hahn-Ring 6,&#160; D-81730 Munich, Germany </span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160; Phone:&#160; (+49) 89 / 636-53403,&#160;&#160;&#160; </span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160; Fax&#160; :&#160; (+49) 89 / 636-48000</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">&#160;&#160;&#160; Email:&#160; Steffen.Fries@siemens.com</span></font></div>
<div align="left"><font face="Courier New"><span style="font-size:10pt">-----------------------------------------------------------</span></font></div>
</body>
</html>


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

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

--===============0623562462==--


From mmusic-bounces@ietf.org  Wed Feb  2 03:03:33 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13151
	for <mmusic-web-archive@ietf.org>; Wed, 2 Feb 2005 03:03:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CwFmQ-0007OL-N1
	for mmusic-web-archive@ietf.org; Wed, 02 Feb 2005 03:22:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CwFSa-0004jO-Og; Wed, 02 Feb 2005 03:02:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CwFGk-0001u3-Nv
	for mmusic@megatron.ietf.org; Wed, 02 Feb 2005 02:49:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11447
	for <mmusic@ietf.org>; Wed, 2 Feb 2005 02:49:45 -0500 (EST)
Received: from goliath.siemens.de ([192.35.17.28])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwFZ4-00071u-F9
	for mmusic@ietf.org; Wed, 02 Feb 2005 03:08:42 -0500
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by goliath.siemens.de (8.12.6/8.12.6) with ESMTP id j127njJH017084;
	Wed, 2 Feb 2005 08:49:45 +0100
Received: from MCHN070C (mhpaba5c.mchp.siemens.de [139.23.204.46])
	by mail3.siemens.de (8.12.6/8.12.6) with ESMTP id j127nifs007163;
	Wed, 2 Feb 2005 08:49:44 +0100
From: "Steffen Fries" <steffen.fries@siemens.com>
Organization: Siemens AG
To: msec@securemulticast.org, mmusic@ietf.org
Date: Wed, 02 Feb 2005 08:49:37 +0100
MIME-Version: 1.0
Message-ID: <42009421.27826.18217F57@localhost>
Priority: normal
In-reply-to: <42009389.29093.181F2DF2@localhost>
References: <41FE4CAC.8060406@nortelnetworks.com>
X-mailer: Pegasus Mail for Windows (4.21c)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Content-Transfer-Encoding: 7BIT
Cc: hannes Tschofenig <Hannes.Tschofenig@siemens.com>
Subject: [MMUSIC] Resent: draft-ietf-msec-bootstrapping-tesla-00.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: steffen.fries@siemens.com
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Content-Transfer-Encoding: 7BIT

> Hi,
> 
> Hannes and me submitted a revision of the Bootstrapping TESLA Draft.
> We updated some text regarding the synchronization and added the IANA
> section. Feel free to send comments.
> 
> Regards
> Steffen
> 
> ----------------------------------------------------------------
> 
> A New Internet-Draft is available from the on-line Internet- Drafts
> directories. This draft is a work item of the Multicast Security
> Working Group of the IETF.
> 
> Title: Bootstrapping TESLA
> Author(s): S. Fries, H. Tschofenig
> Filename: draft-ietf-msec-bootstrapping-tesla-00.txt
> Pages: 13
> Date: 2005-1-18
> 
> With the Timed Efficient Stream Loss-tolerant Authentication protocol
> (TESLA) a protocol for providing source authentication in multicast
> scenarios was introduced. A mapping for TESLA to the Secure Real-time
> Transport Protocol (SRTP) has been published which assumes that some
> TESLA parameters are made available by out-of-band mechanisms. This
> document describes payloads for bootstrapping these parameters with
> the help of the Multimedia Internet KEYing (MIKEY) protocol.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-msec- bootstrapping-
> tesla-00.txt
> 
> To remove yourself from the I-D Announcement list, send a message to
> i- d-announce-request at 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-msec-
> bootstrapping-tesla-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 at ietf.org.
> In the body type:
> "FILE /internet-drafts/draft-ietf-msec-bootstrapping- tesla-
> 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 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
>  splitup into multiple messages), so check your local
>  documentation onhow 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.
> 
> <ftp://ftp.ietf.org/internet-drafts/draft-ietf-msec- bootstrapping-
> tesla-00.txt>
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce at ietf.org
> https://www1.ietf.org/mailman/listinfo/i-d-announce
> 
> 
> -----------------------------------------------------------
>  Steffen Fries, Siemens AG, CT IC 3
>  Otto-Hahn-Ring 6, D-81730 Munich, Germany 
>  Phone: (+49) 89 / 636-53403, 
>  Fax : (+49) 89 / 636-48000
>  Email: Steffen.Fries@siemens.com
> -----------------------------------------------------------



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


From mmusic-bounces@ietf.org  Wed Feb  2 12:53:47 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05509
	for <mmusic-web-archive@ietf.org>; Wed, 2 Feb 2005 12:53:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CwOzm-0007TA-Bh
	for mmusic-web-archive@ietf.org; Wed, 02 Feb 2005 13:12:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CwOeu-0007e7-RW; Wed, 02 Feb 2005 12:51:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CwOWX-0005Ld-6w
	for mmusic@megatron.ietf.org; Wed, 02 Feb 2005 12:42:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04046
	for <mmusic@ietf.org>; Wed, 2 Feb 2005 12:42:30 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwOon-000725-B7
	for mmusic@ietf.org; Wed, 02 Feb 2005 13:01:37 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j12HfhD04485; Wed, 2 Feb 2005 12:41:43 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <Y0S0PNL8>; Wed, 2 Feb 2005 12:41:44 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF016F48DB@zrc2hxm0.corp.nortel.com>
From: "Francois Audet" <audet@nortel.com>
To: "'Jonathan Rosenberg'" <jdrosen@cisco.com>
Subject: RE: [MMUSIC] ICE feature - TCP alternates for a UDP stream
Date: Wed, 2 Feb 2005 12:41:40 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Cc: "'IETF MMUSIC WG'" <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1770665852=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c

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

--===============1770665852==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C5094E.740EAC1C"

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

------_=_NextPart_001_01C5094E.740EAC1C
Content-Type: text/plain

OK. I guess for the latter, you are not defining procedures
for verifying connectivity (akin to the peer-to-peer STUN in
ICE), correct? It is outside the scope of what you are proposing, 
right?

I assume the RTP/TCP transport option will NOT be made mandatory in ICE?


> -----Original Message-----
> From: mmusic-bounces@ietf.org 
> [mailto:mmusic-bounces@ietf.org] On Behalf Of Jonathan Rosenberg
> Sent: Wednesday, February 02, 2005 02:16
> To: Audet, Francois [SC100:9T51:EXCH]
> Cc: 'IETF MMUSIC WG'
> Subject: Re: [MMUSIC] ICE feature - TCP alternates for a UDP stream
> 
> 
> 
> 
> Francois Audet wrote:
> 
> > So you are saying that the media would be transported over 
> RTP/TCP to 
> > the TURN relay, and then to the other endpoint using 
> another RTP/TCP 
> > session, right?
> 
> Yes.
> 
> > 
> > And not and end-to-end RTP/TCP session between the two peers, right?
> 
> One could offer that up as an additional alternate, yes. In 
> other words, 
> just like the client would offer UDP alternates learned from 
> STUN, TURN 
> and local interfaces, so too they could offer TCP alternates learned 
> from TURN and local interfaces. The latter, if it works, 
> would result in 
> a direct TCP connection from one user to the other. The 
> former would end 
> up with clients connecting through the TURN server.
> 
> -Jonathan R.

------_=_NextPart_001_01C5094E.740EAC1C
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2658.2">
<TITLE>RE: [MMUSIC] ICE feature - TCP alternates for a UDP stream</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>OK. I guess for the latter, you are not defining procedures</FONT>
<BR><FONT SIZE=2>for verifying connectivity (akin to the peer-to-peer STUN in</FONT>
<BR><FONT SIZE=2>ICE), correct? It is outside the scope of what you are proposing, </FONT>
<BR><FONT SIZE=2>right?</FONT>
</P>

<P><FONT SIZE=2>I assume the RTP/TCP transport option will NOT be made mandatory in ICE?</FONT>
</P>
<BR>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: mmusic-bounces@ietf.org </FONT>
<BR><FONT SIZE=2>&gt; [<A HREF="mailto:mmusic-bounces@ietf.org">mailto:mmusic-bounces@ietf.org</A>] On Behalf Of Jonathan Rosenberg</FONT>
<BR><FONT SIZE=2>&gt; Sent: Wednesday, February 02, 2005 02:16</FONT>
<BR><FONT SIZE=2>&gt; To: Audet, Francois [SC100:9T51:EXCH]</FONT>
<BR><FONT SIZE=2>&gt; Cc: 'IETF MMUSIC WG'</FONT>
<BR><FONT SIZE=2>&gt; Subject: Re: [MMUSIC] ICE feature - TCP alternates for a UDP stream</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Francois Audet wrote:</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; So you are saying that the media would be transported over </FONT>
<BR><FONT SIZE=2>&gt; RTP/TCP to </FONT>
<BR><FONT SIZE=2>&gt; &gt; the TURN relay, and then to the other endpoint using </FONT>
<BR><FONT SIZE=2>&gt; another RTP/TCP </FONT>
<BR><FONT SIZE=2>&gt; &gt; session, right?</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Yes.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; And not and end-to-end RTP/TCP session between the two peers, right?</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; One could offer that up as an additional alternate, yes. In </FONT>
<BR><FONT SIZE=2>&gt; other words, </FONT>
<BR><FONT SIZE=2>&gt; just like the client would offer UDP alternates learned from </FONT>
<BR><FONT SIZE=2>&gt; STUN, TURN </FONT>
<BR><FONT SIZE=2>&gt; and local interfaces, so too they could offer TCP alternates learned </FONT>
<BR><FONT SIZE=2>&gt; from TURN and local interfaces. The latter, if it works, </FONT>
<BR><FONT SIZE=2>&gt; would result in </FONT>
<BR><FONT SIZE=2>&gt; a direct TCP connection from one user to the other. The </FONT>
<BR><FONT SIZE=2>&gt; former would end </FONT>
<BR><FONT SIZE=2>&gt; up with clients connecting through the TURN server.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; -Jonathan R.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C5094E.740EAC1C--


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

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

--===============1770665852==--



From mmusic-bounces@ietf.org  Wed Feb  2 23:15:29 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21292
	for <mmusic-web-archive@ietf.org>; Wed, 2 Feb 2005 23:15:29 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CwYhV-0006de-0h
	for mmusic-web-archive@ietf.org; Wed, 02 Feb 2005 23:34:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CwYNh-0002eJ-Np; Wed, 02 Feb 2005 23:14:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CwYJ8-0001Ti-2D
	for mmusic@megatron.ietf.org; Wed, 02 Feb 2005 23:09:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20719
	for <mmusic@ietf.org>; Wed, 2 Feb 2005 23:09:25 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CwYbc-0006RQ-KE
	for mmusic@ietf.org; Wed, 02 Feb 2005 23:28:36 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 02 Feb 2005 20:16:24 -0800
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j1348pHo024114;
	Wed, 2 Feb 2005 20:08:51 -0800 (PST)
Received: from [192.168.1.100] (che-vpn-cluster-2-136.cisco.com
	[10.86.242.136]) by mira-sjc5-d.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AHM20586; Wed, 2 Feb 2005 20:08:55 -0800 (PST)
Message-ID: <4201A3D7.1040906@cisco.com>
Date: Wed, 02 Feb 2005 23:08:55 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francois Audet <audet@nortel.com>
Subject: Re: [MMUSIC] ICE feature - TCP alternates for a UDP stream
References: <1ECE0EB50388174790F9694F77522CCF016F48DB@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF016F48DB@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
Cc: "'IETF MMUSIC WG'" <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit



Francois Audet wrote:

> OK. I guess for the latter, you are not defining procedures
> for verifying connectivity (akin to the peer-to-peer STUN in
> ICE), correct? It is outside the scope of what you are proposing,
> right?

My first inclination was that you would still use STUN for the 
connectivity check over TCP; irregardless of whether that tcp is through 
a TURN relay or direct (indeed, the peer in the call won't normally even 
know whether the tcp connection it will make is direct or through a 
relay). Recall that stun can run over tcp.

However, it is less useful here since establishment of the connection 
itself could be considered a connectivity check. As such, I could go 
either way.

Do you have a preference here, and if so, why?

> 
> I assume the RTP/TCP transport option will NOT be made mandatory in ICE?

No, in that we concluded that nothing in particular was mandatory, not 
even TURN/UDP. However I will add motivation text for this which 
explains why it might be a good idea.


-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

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


From mmusic-bounces@ietf.org  Thu Feb  3 04:18:51 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02573
	for <mmusic-web-archive@ietf.org>; Thu, 3 Feb 2005 04:18:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CwdR5-0007DZ-8q
	for mmusic-web-archive@ietf.org; Thu, 03 Feb 2005 04:38:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cwd35-00030I-H2; Thu, 03 Feb 2005 04:13:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cwcyu-0001ye-TL
	for mmusic@megatron.ietf.org; Thu, 03 Feb 2005 04:08:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01907
	for <mmusic@ietf.org>; Thu, 3 Feb 2005 04:08:53 -0500 (EST)
Received: from mailserv.intranet.gr ([146.124.14.106])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwdHQ-0006wg-0S
	for mmusic@ietf.org; Thu, 03 Feb 2005 04:28:05 -0500
Received: from mailserv.intranet.gr (localhost [127.0.0.1])
	by mailserv.intranet.gr (8.13.1/8.13.1) with ESMTP id j139B9Yv005173
	for <mmusic@ietf.org>; Thu, 3 Feb 2005 11:11:09 +0200 (EET)
Received: from aiolos.intranet.gr (aiolos.intranet.GR [146.124.6.7])
	by mailserv.intranet.gr (8.13.1/8.13.1) with ESMTP id j139B85e005163
	for <mmusic@ietf.org>; Thu, 3 Feb 2005 11:11:08 +0200 (EET)
Received: from pcnt189 (pcnt189 [146.124.44.189])
	by aiolos.intranet.gr (8.11.7p1+Sun/8.11.7) with SMTP id j139DHF00994
	for <mmusic@ietf.org>; Thu, 3 Feb 2005 11:13:17 +0200 (EET)
From: "Spiros Spirou" <spis@intracom.gr>
To: "IETF mmusic WG list" <mmusic@ietf.org>
Date: Thu, 3 Feb 2005 11:09:23 +0100
Message-ID: <PPEPKGOKJJGOIIEBKKOEGEFODAAA.spis@intracom.gr>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-7"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] End of movie signalling
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit

Hi,

In a VoD scenario, I am trying to find a STANDARD way to detect the end of a
movie in the client in order to free the associated resources for control
(RTSP), transport (RTP) and play-out.

RFC 2326 states that when the server reaches the end of the movie it "...
reverts from state Playing ... to state Ready ...". From there "... it MAY
revert to Init and tear down the RTSP session if it has not received
\"wellness\" information, such as RTCP reports or RTSP commands, from the client
for a defined interval, with a default of one minute." Both of these state
changes happen without sending any notification to the client.

Now, the client could detect the end of movie on its own by maintaining a
presentation clock, set initially by the Range header in the PLAY reply.
However, this would probably involve polling, which seems incorrect given the
usual scarcity of resources in the client platform. A variant of this method
would be to poll the server by sending PLAY requests without a Range header and
reading the current presentation time in the Range header of the reply. This
adds waste of bandwidth to the waste of local resources.

Any ideas?

Spiros


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


From mmusic-bounces@ietf.org  Thu Feb  3 04:36:22 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03643
	for <mmusic-web-archive@ietf.org>; Thu, 3 Feb 2005 04:36:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cwdhz-0007ew-Fk
	for mmusic-web-archive@ietf.org; Thu, 03 Feb 2005 04:55:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CwdHu-0006h0-F1; Thu, 03 Feb 2005 04:28:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CwdD9-0005ak-Nx
	for mmusic@megatron.ietf.org; Thu, 03 Feb 2005 04:23:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02850
	for <mmusic@ietf.org>; Thu, 3 Feb 2005 04:23:37 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwdVf-0007LL-Ta
	for mmusic@ietf.org; Thu, 03 Feb 2005 04:42:49 -0500
Received: from rubin.informatik.uni-bremen.de (rubin.informatik.uni-bremen.de
	[134.102.224.59])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	j139NLeV006997
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 3 Feb 2005 10:23:22 +0100 (MET)
Received: (from jo@localhost)
	by rubin.informatik.uni-bremen.de (8.12.8/8.12.8/Submit) id
	j139NJAF028885; Thu, 3 Feb 2005 10:23:19 +0100
From: Joerg Ott <jo@informatik.uni-bremen.de>
Message-Id: <200502030923.j139NJAF028885@rubin.informatik.uni-bremen.de>
Subject: Re: [MMUSIC] End of movie signalling
To: spis@intracom.gr (Spiros Spirou)
Date: Thu, 3 Feb 2005 10:23:19 +0100 (MET)
In-Reply-To: <PPEPKGOKJJGOIIEBKKOEGEFODAAA.spis@intracom.gr> from "Spiros
	Spirou" at Feb 03, 2005 11:09:23 AM
X-Mailer: ELM [version 2.5 PL6]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
Cc: Joerg Ott <jo@informatik.uni-bremen.de>,
        IETF mmusic WG list <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit

Hi Spiros,

what you are looking for is being addressed in an addition to the
revised RTSP spec: draft-ietf-mmusic-rtsp-announce-00.txt defines
a generic announcement mechanism that, among other uses, the server
can use to signal end-of-stream to the client.

Please also take a look draft-ietf-mmusic-rfc2326bis-08.txt,
the updated RTSP spec that is supposed to override RFC 2326 in the
not too distant future.

Joerg

> 
> Hi,
> 
> In a VoD scenario, I am trying to find a STANDARD way to detect the end of a
> movie in the client in order to free the associated resources for control
> (RTSP), transport (RTP) and play-out.
> 
> RFC 2326 states that when the server reaches the end of the movie it "...
> reverts from state Playing ... to state Ready ...". From there "... it MAY
> revert to Init and tear down the RTSP session if it has not received
> \"wellness\" information, such as RTCP reports or RTSP commands, from the client
> for a defined interval, with a default of one minute." Both of these state
> changes happen without sending any notification to the client.
> 
> Now, the client could detect the end of movie on its own by maintaining a
> presentation clock, set initially by the Range header in the PLAY reply.
> However, this would probably involve polling, which seems incorrect given the
> usual scarcity of resources in the client platform. A variant of this method
> would be to poll the server by sending PLAY requests without a Range header and
> reading the current presentation time in the Range header of the reply. This
> adds waste of bandwidth to the waste of local resources.
> 
> Any ideas?
> 
> Spiros
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 


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


From mmusic-bounces@ietf.org  Thu Feb  3 06:12:49 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10817
	for <mmusic-web-archive@ietf.org>; Thu, 3 Feb 2005 06:12:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CwfDO-0001r2-OP
	for mmusic-web-archive@ietf.org; Thu, 03 Feb 2005 06:32:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cwesw-0003bX-9L; Thu, 03 Feb 2005 06:10:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cweq7-0002nJ-KH
	for mmusic@megatron.ietf.org; Thu, 03 Feb 2005 06:07:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10427
	for <mmusic@ietf.org>; Thu, 3 Feb 2005 06:07:56 -0500 (EST)
Received: from mailserv.intranet.gr ([146.124.14.106])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cwf8d-0001ia-MO
	for mmusic@ietf.org; Thu, 03 Feb 2005 06:27:10 -0500
Received: from mailserv.intranet.gr (localhost [127.0.0.1])
	by mailserv.intranet.gr (8.13.1/8.13.1) with ESMTP id j13BAGET011362
	for <mmusic@ietf.org>; Thu, 3 Feb 2005 13:10:16 +0200 (EET)
Received: from aiolos.intranet.gr (aiolos.intranet.GR [146.124.6.7])
	by mailserv.intranet.gr (8.13.1/8.13.1) with ESMTP id j13BAFub011345;
	Thu, 3 Feb 2005 13:10:15 +0200 (EET)
Received: from pcnt189 (pcnt189 [146.124.44.189])
	by aiolos.intranet.gr (8.11.7p1+Sun/8.11.7) with SMTP id j13BCNF07405; 
	Thu, 3 Feb 2005 13:12:24 +0200 (EET)
From: "Spiros Spirou" <spis@intracom.gr>
To: "Joerg Ott" <jo@informatik.uni-bremen.de>
Subject: RE: [MMUSIC] End of movie signalling
Date: Thu, 3 Feb 2005 13:08:29 +0100
Message-ID: <PPEPKGOKJJGOIIEBKKOEMEGADAAA.spis@intracom.gr>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
In-Reply-To: <200502030923.j139NJAF028885@rubin.informatik.uni-bremen.de>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit
Cc: IETF mmusic WG list <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit

Hi Joerg,

Thanks for the pointers. Reading between the lines, I would say that there is no
provisioned mechanism for signaling end-of-stream using RFC2326 means only.
Implementations wishing to be backwards compatible should probably revert to
costly tricks. Is this correct?

Spiros

-----Original Message-----
From: Joerg Ott [mailto:jo@informatik.uni-bremen.de]
Sent: Thursday, February 03, 2005 10:23 AM
To: Spiros Spirou
Cc: IETF mmusic WG list; Joerg Ott
Subject: Re: [MMUSIC] End of movie signalling


Hi Spiros,

what you are looking for is being addressed in an addition to the
revised RTSP spec: draft-ietf-mmusic-rtsp-announce-00.txt defines
a generic announcement mechanism that, among other uses, the server
can use to signal end-of-stream to the client.

Please also take a look draft-ietf-mmusic-rfc2326bis-08.txt,
the updated RTSP spec that is supposed to override RFC 2326 in the
not too distant future.

Joerg

>
> Hi,
>
> In a VoD scenario, I am trying to find a STANDARD way to detect the end of a
> movie in the client in order to free the associated resources for control
> (RTSP), transport (RTP) and play-out.
>
> RFC 2326 states that when the server reaches the end of the movie it "...
> reverts from state Playing ... to state Ready ...". From there "... it MAY
> revert to Init and tear down the RTSP session if it has not received
> \"wellness\" information, such as RTCP reports or RTSP commands, from the
client
> for a defined interval, with a default of one minute." Both of these state
> changes happen without sending any notification to the client.
>
> Now, the client could detect the end of movie on its own by maintaining a
> presentation clock, set initially by the Range header in the PLAY reply.
> However, this would probably involve polling, which seems incorrect given the
> usual scarcity of resources in the client platform. A variant of this method
> would be to poll the server by sending PLAY requests without a Range header
and
> reading the current presentation time in the Range header of the reply. This
> adds waste of bandwidth to the waste of local resources.
>
> Any ideas?
>
> Spiros
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
>



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


From mmusic-bounces@ietf.org  Thu Feb  3 12:57:55 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20604
	for <mmusic-web-archive@ietf.org>; Thu, 3 Feb 2005 12:57:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CwlXU-0006r6-Pq
	for mmusic-web-archive@ietf.org; Thu, 03 Feb 2005 13:17:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cwl5E-00030p-QZ; Thu, 03 Feb 2005 12:48:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cwl2Y-0001mZ-Fm
	for mmusic@megatron.ietf.org; Thu, 03 Feb 2005 12:45:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19741
	for <mmusic@ietf.org>; Thu, 3 Feb 2005 12:45:11 -0500 (EST)
Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwlL9-0006We-UU
	for mmusic@ietf.org; Thu, 03 Feb 2005 13:04:28 -0500
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by mx2.foretec.com with esmtp (Exim 4.24) id 1Cwl1j-0001R1-Bi
	for mmusic@ietf.org; Thu, 03 Feb 2005 12:44:23 -0500
Received: from srsdmail01.PVNS.COM (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id
	j13HhMfa004629; Thu, 3 Feb 2005 11:43:22 -0600 (CST)
X-MIMEOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] End of movie signalling
Date: Thu, 3 Feb 2005 09:43:21 -0800
Message-ID: <758B5A159B385447B4F950DE72D7D7AD678C71@srsdmail01.PVNS.COM>
Thread-Topic: [MMUSIC] End of movie signalling
Thread-Index: AcUJ4VvTMxw5Od8gTRW1nQFA6xQRewANj0hQ
From: "Thomas Zeng" <zeng@pvnetsolutions.com>
To: "Spiros Spirou" <spis@intracom.gr>,
        "Joerg Ott" <jo@informatik.uni-bremen.de>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Content-Transfer-Encoding: quoted-printable
Cc: IETF mmusic WG list <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Content-Transfer-Encoding: quoted-printable

Hi  Spiros:

Your transport is RTP, right? Can you not use RTCP BYE to signal =
end-of-stream until draft-ietf-mmusic-rfc2326bis-08.txt and =
draft-ietf-mmusic-rtsp-announce-00.txt are ratified?

Cheers,
-thomas

-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org]On Behalf
Of Spiros Spirou
Sent: Thursday, February 03, 2005 4:08 AM
To: Joerg Ott
Cc: IETF mmusic WG list
Subject: RE: [MMUSIC] End of movie signalling


Hi Joerg,

Thanks for the pointers. Reading between the lines, I would say that =
there is no
provisioned mechanism for signaling end-of-stream using RFC2326 means =
only.
Implementations wishing to be backwards compatible should probably =
revert to
costly tricks. Is this correct?

Spiros

-----Original Message-----
From: Joerg Ott [mailto:jo@informatik.uni-bremen.de]
Sent: Thursday, February 03, 2005 10:23 AM
To: Spiros Spirou
Cc: IETF mmusic WG list; Joerg Ott
Subject: Re: [MMUSIC] End of movie signalling


Hi Spiros,

what you are looking for is being addressed in an addition to the
revised RTSP spec: draft-ietf-mmusic-rtsp-announce-00.txt defines
a generic announcement mechanism that, among other uses, the server
can use to signal end-of-stream to the client.

Please also take a look draft-ietf-mmusic-rfc2326bis-08.txt,
the updated RTSP spec that is supposed to override RFC 2326 in the
not too distant future.

Joerg

>
> Hi,
>
> In a VoD scenario, I am trying to find a STANDARD way to detect the =
end of a
> movie in the client in order to free the associated resources for =
control
> (RTSP), transport (RTP) and play-out.
>
> RFC 2326 states that when the server reaches the end of the movie it =
"...
> reverts from state Playing ... to state Ready ...". From there "... it =
MAY
> revert to Init and tear down the RTSP session if it has not received
> \"wellness\" information, such as RTCP reports or RTSP commands, from =
the
client
> for a defined interval, with a default of one minute." Both of these =
state
> changes happen without sending any notification to the client.
>
> Now, the client could detect the end of movie on its own by =
maintaining a
> presentation clock, set initially by the Range header in the PLAY =
reply.
> However, this would probably involve polling, which seems incorrect =
given the
> usual scarcity of resources in the client platform. A variant of this =
method
> would be to poll the server by sending PLAY requests without a Range =
header
and
> reading the current presentation time in the Range header of the =
reply. This
> adds waste of bandwidth to the waste of local resources.
>
> Any ideas?
>
> Spiros
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
>



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

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


From mmusic-bounces@ietf.org  Thu Feb  3 17:31:59 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29735
	for <mmusic-web-archive@ietf.org>; Thu, 3 Feb 2005 17:31:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cwpok-00028A-O5
	for mmusic-web-archive@ietf.org; Thu, 03 Feb 2005 17:51:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CwpHI-0007s0-5u; Thu, 03 Feb 2005 17:16:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cworl-0008P8-Va
	for mmusic@megatron.ietf.org; Thu, 03 Feb 2005 16:50:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18750
	for <mmusic@ietf.org>; Thu, 3 Feb 2005 16:50:18 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwpAO-0007aH-0r
	for mmusic@ietf.org; Thu, 03 Feb 2005 17:09:37 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j13Lngf06247; Thu, 3 Feb 2005 16:49:43 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <Y0S0RZRN>; Thu, 3 Feb 2005 16:49:43 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF016F50E2@zrc2hxm0.corp.nortel.com>
From: "Francois Audet" <audet@nortel.com>
To: "'Jonathan Rosenberg'" <jdrosen@cisco.com>
Subject: RE: [MMUSIC] ICE feature - TCP alternates for a UDP stream
Date: Thu, 3 Feb 2005 16:49:28 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: "'IETF MMUSIC WG'" <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1667646263=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168

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

--===============1667646263==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C50A3A.3CBBE40C"

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

------_=_NextPart_001_01C50A3A.3CBBE40C
Content-Type: text/plain

> > I assume the RTP/TCP transport option will NOT be made mandatory in 
> > ICE?
> 
> No, in that we concluded that nothing in particular was 
> mandatory, not 
> even TURN/UDP. However I will add motivation text for this which 
> explains why it might be a good idea.

I think we should be a bit careful on what we say on RTP/TCP
transport.

While I understand that it may make sense in some cases
to "recommend" using RTP/TCP if everything else fails. 

However, there are environments where this may NOT make sense.
For example, in an Enterprise, you may not want to allow
RTP/TCP at all because of quality issues.

So I would say it needs some qualifiers along the lines of
"if RTP/TCP transport is acceptable for the application, it
is recommended that bla bla bla".

------_=_NextPart_001_01C50A3A.3CBBE40C
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2658.2">
<TITLE>RE: [MMUSIC] ICE feature - TCP alternates for a UDP stream</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>&gt; &gt; I assume the RTP/TCP transport option will NOT be made mandatory in </FONT>
<BR><FONT SIZE=2>&gt; &gt; ICE?</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; No, in that we concluded that nothing in particular was </FONT>
<BR><FONT SIZE=2>&gt; mandatory, not </FONT>
<BR><FONT SIZE=2>&gt; even TURN/UDP. However I will add motivation text for this which </FONT>
<BR><FONT SIZE=2>&gt; explains why it might be a good idea.</FONT>
</P>

<P><FONT SIZE=2>I think we should be a bit careful on what we say on RTP/TCP</FONT>
<BR><FONT SIZE=2>transport.</FONT>
</P>

<P><FONT SIZE=2>While I understand that it may make sense in some cases</FONT>
<BR><FONT SIZE=2>to &quot;recommend&quot; using RTP/TCP if everything else fails. </FONT>
</P>

<P><FONT SIZE=2>However, there are environments where this may NOT make sense.</FONT>
<BR><FONT SIZE=2>For example, in an Enterprise, you may not want to allow</FONT>
<BR><FONT SIZE=2>RTP/TCP at all because of quality issues.</FONT>
</P>

<P><FONT SIZE=2>So I would say it needs some qualifiers along the lines of</FONT>
<BR><FONT SIZE=2>&quot;if RTP/TCP transport is acceptable for the application, it</FONT>
<BR><FONT SIZE=2>is recommended that bla bla bla&quot;.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C50A3A.3CBBE40C--


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

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

--===============1667646263==--



From mmusic-bounces@ietf.org  Thu Feb  3 17:47:36 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01812
	for <mmusic-web-archive@ietf.org>; Thu, 3 Feb 2005 17:47:36 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cwq3q-0002kZ-JP
	for mmusic-web-archive@ietf.org; Thu, 03 Feb 2005 18:06:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CwpQo-00044K-UI; Thu, 03 Feb 2005 17:26:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CwpAj-0003eO-Vy
	for mmusic@megatron.ietf.org; Thu, 03 Feb 2005 17:09:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26198
	for <mmusic@ietf.org>; Thu, 3 Feb 2005 17:09:55 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CwpTM-0000rY-M4
	for mmusic@ietf.org; Thu, 03 Feb 2005 17:29:14 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 03 Feb 2005 14:18:50 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j13M9IHo001944;
	Thu, 3 Feb 2005 14:09:18 -0800 (PST)
Received: from [161.44.55.58] (dhcp-161-44-55-58.cisco.com [161.44.55.58])
	by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id AHM75516;
	Thu, 3 Feb 2005 14:09:19 -0800 (PST)
Message-ID: <4202A10E.5080609@cisco.com>
Date: Thu, 03 Feb 2005 17:09:18 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francois Audet <audet@nortel.com>
Subject: Re: [MMUSIC] ICE feature - TCP alternates for a UDP stream
References: <1ECE0EB50388174790F9694F77522CCF016F50E2@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF016F50E2@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit
Cc: "'IETF MMUSIC WG'" <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit



Francois Audet wrote:

>  > > I assume the RTP/TCP transport option will NOT be made mandatory in
>  > > ICE?
>  >
>  > No, in that we concluded that nothing in particular was
>  > mandatory, not
>  > even TURN/UDP. However I will add motivation text for this which
>  > explains why it might be a good idea.
> 
> I think we should be a bit careful on what we say on RTP/TCP
> transport.
> 
> While I understand that it may make sense in some cases
> to "recommend" using RTP/TCP if everything else fails.
> 
> However, there are environments where this may NOT make sense.
> For example, in an Enterprise, you may not want to allow
> RTP/TCP at all because of quality issues.
> 
> So I would say it needs some qualifiers along the lines of
> "if RTP/TCP transport is acceptable for the application, it
> is recommended that bla bla bla".
> 

Certainly I think it is reasonable to allow an endpoint to not even 
offer RTP/TCP if that is appropriate for the environment.

The question is about whether an endpoint has to implement it. THere, I 
think its like TURN. We don't make it a MUST. We specify that you SHOULD 
implement something that provides media transport over TCP and I will 
explain the motivations for why this is a good idea.

-Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

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


From mmusic-bounces@ietf.org  Thu Feb  3 17:48:31 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01900
	for <mmusic-web-archive@ietf.org>; Thu, 3 Feb 2005 17:48:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cwq4g-0002m5-7H
	for mmusic-web-archive@ietf.org; Thu, 03 Feb 2005 18:07:50 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CwpRC-0004sk-Im; Thu, 03 Feb 2005 17:26:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CwpDy-0005JV-Cb
	for mmusic@megatron.ietf.org; Thu, 03 Feb 2005 17:13:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27050
	for <mmusic@ietf.org>; Thu, 3 Feb 2005 17:13:15 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwpWb-00019h-MQ
	for mmusic@ietf.org; Thu, 03 Feb 2005 17:32:34 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j13MCgr19902; Thu, 3 Feb 2005 17:12:43 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <Y0S0R6F1>; Thu, 3 Feb 2005 17:12:43 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF016F5119@zrc2hxm0.corp.nortel.com>
From: "Francois Audet" <audet@nortel.com>
To: "'Jonathan Rosenberg'" <jdrosen@cisco.com>
Subject: RE: [MMUSIC] ICE feature - TCP alternates for a UDP stream
Date: Thu, 3 Feb 2005 17:12:32 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 202a3ece0492a8c7e7c8672d5214398f
Cc: "'IETF MMUSIC WG'" <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0202979231=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9

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

--===============0202979231==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C50A3D.75B05F74"

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

------_=_NextPart_001_01C50A3D.75B05F74
Content-Type: text/plain

I'm OK with that.

> -----Original Message-----
> From: Jonathan Rosenberg [mailto:jdrosen@cisco.com] 
> Sent: Thursday, February 03, 2005 14:09
> To: Audet, Francois [SC100:9T51:EXCH]
> Cc: 'IETF MMUSIC WG'
> Subject: Re: [MMUSIC] ICE feature - TCP alternates for a UDP stream
> 
> 
> 
> 
> Francois Audet wrote:
> 
> >  > > I assume the RTP/TCP transport option will NOT be made 
> mandatory 
> > in  > > ICE?  >
> >  > No, in that we concluded that nothing in particular was
> >  > mandatory, not
> >  > even TURN/UDP. However I will add motivation text for this which
> >  > explains why it might be a good idea.
> > 
> > I think we should be a bit careful on what we say on RTP/TCP 
> > transport.
> > 
> > While I understand that it may make sense in some cases
> > to "recommend" using RTP/TCP if everything else fails.
> > 
> > However, there are environments where this may NOT make sense. For 
> > example, in an Enterprise, you may not want to allow RTP/TCP at all 
> > because of quality issues.
> > 
> > So I would say it needs some qualifiers along the lines of 
> "if RTP/TCP 
> > transport is acceptable for the application, it is recommended that 
> > bla bla bla".
> > 
> 
> Certainly I think it is reasonable to allow an endpoint to not even 
> offer RTP/TCP if that is appropriate for the environment.
> 
> The question is about whether an endpoint has to implement 
> it. THere, I 
> think its like TURN. We don't make it a MUST. We specify that 
> you SHOULD 
> implement something that provides media transport over TCP and I will 
> explain the motivations for why this is a good idea.
> 
> -Jonathan R.
> -- 
> Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
> Director, Service Provider VoIP Architecture   Parsippany, NJ 
> 07054-2711
> Cisco Systems
> jdrosen@cisco.com                              FAX:   (973) 952-5050
> http://www.jdrosen.net                         PHONE: (973) 952-5000
> http://www.cisco.com
> 
> 

------_=_NextPart_001_01C50A3D.75B05F74
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: [MMUSIC] ICE feature - TCP alternates for a UDP =
stream</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I'm OK with that.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Jonathan Rosenberg [<A =
HREF=3D"mailto:jdrosen@cisco.com">mailto:jdrosen@cisco.com</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Thursday, February 03, 2005 14:09</FONT>
<BR><FONT SIZE=3D2>&gt; To: Audet, Francois [SC100:9T51:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: 'IETF MMUSIC WG'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [MMUSIC] ICE feature - TCP =
alternates for a UDP stream</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Francois Audet wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; &gt; I assume the RTP/TCP =
transport option will NOT be made </FONT>
<BR><FONT SIZE=3D2>&gt; mandatory </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; in&nbsp; &gt; &gt; ICE?&nbsp; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; No, in that we concluded that =
nothing in particular was</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; mandatory, not</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; even TURN/UDP. However I will =
add motivation text for this which</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; explains why it might be a good =
idea.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I think we should be a bit careful on what =
we say on RTP/TCP </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; transport.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; While I understand that it may make sense =
in some cases</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; to &quot;recommend&quot; using RTP/TCP if =
everything else fails.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; However, there are environments where this =
may NOT make sense. For </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; example, in an Enterprise, you may not =
want to allow RTP/TCP at all </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; because of quality issues.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; So I would say it needs some qualifiers =
along the lines of </FONT>
<BR><FONT SIZE=3D2>&gt; &quot;if RTP/TCP </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; transport is acceptable for the =
application, it is recommended that </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; bla bla bla&quot;.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Certainly I think it is reasonable to allow an =
endpoint to not even </FONT>
<BR><FONT SIZE=3D2>&gt; offer RTP/TCP if that is appropriate for the =
environment.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The question is about whether an endpoint has =
to implement </FONT>
<BR><FONT SIZE=3D2>&gt; it. THere, I </FONT>
<BR><FONT SIZE=3D2>&gt; think its like TURN. We don't make it a MUST. =
We specify that </FONT>
<BR><FONT SIZE=3D2>&gt; you SHOULD </FONT>
<BR><FONT SIZE=3D2>&gt; implement something that provides media =
transport over TCP and I will </FONT>
<BR><FONT SIZE=3D2>&gt; explain the motivations for why this is a good =
idea.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -Jonathan R.</FONT>
<BR><FONT SIZE=3D2>&gt; -- </FONT>
<BR><FONT SIZE=3D2>&gt; Jonathan D. Rosenberg, =
Ph.D.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 600 Lanidex Plaza</FONT>
<BR><FONT SIZE=3D2>&gt; Director, Service Provider VoIP =
Architecture&nbsp;&nbsp; Parsippany, NJ </FONT>
<BR><FONT SIZE=3D2>&gt; 07054-2711</FONT>
<BR><FONT SIZE=3D2>&gt; Cisco Systems</FONT>
<BR><FONT SIZE=3D2>&gt; =
jdrosen@cisco.com&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FAX:&nbsp;&nbsp; (973) =
952-5050</FONT>
<BR><FONT SIZE=3D2>&gt; <A HREF=3D"http://www.jdrosen.net" =
TARGET=3D"_blank">http://www.jdrosen.net</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PHONE: (973) =
952-5000</FONT>
<BR><FONT SIZE=3D2>&gt; <A HREF=3D"http://www.cisco.com" =
TARGET=3D"_blank">http://www.cisco.com</A></FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C50A3D.75B05F74--


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

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

--===============0202979231==--



From mmusic-bounces@ietf.org  Thu Feb  3 17:49:00 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01964
	for <mmusic-web-archive@ietf.org>; Thu, 3 Feb 2005 17:48:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cwq5C-0002nf-Ls
	for mmusic-web-archive@ietf.org; Thu, 03 Feb 2005 18:08:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CwpSx-00063n-1k; Thu, 03 Feb 2005 17:28:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CwpF9-0006JF-I3
	for mmusic@megatron.ietf.org; Thu, 03 Feb 2005 17:14:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27482
	for <mmusic@ietf.org>; Thu, 3 Feb 2005 17:14:28 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwpXm-0001Kf-TE
	for mmusic@ietf.org; Thu, 03 Feb 2005 17:33:47 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j13MDvr20162; Thu, 3 Feb 2005 17:13:57 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <Y0S0R62C>; Thu, 3 Feb 2005 17:13:57 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF016F511D@zrc2hxm0.corp.nortel.com>
From: "Francois Audet" <audet@nortel.com>
To: "'Jonathan Rosenberg'" <jdrosen@cisco.com>
Subject: RE: [MMUSIC] ICE feature - TCP alternates for a UDP stream
Date: Thu, 3 Feb 2005 17:13:41 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: "'IETF MMUSIC WG'" <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2057758274=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5

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

--===============2057758274==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C50A3D.9EE18F23"

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

------_=_NextPart_001_01C50A3D.9EE18F23
Content-Type: text/plain


> My first inclination was that you would still use STUN for the 
> connectivity check over TCP; irregardless of whether that tcp 
> is through 
> a TURN relay or direct (indeed, the peer in the call won't 
> normally even 
> know whether the tcp connection it will make is direct or through a 
> relay). Recall that stun can run over tcp.

Hum. If we are to use STUN on TCP, I think we need to clarify in 
draft-ietf-behave-rfc3489bis how it works. There are a number of
statements in there that sort of imply that it doesn't work with TCP.

Are you saying that you would send the binding requests on TCP?

Can you clarify what you mean by STUN over TCP?

> However, it is less useful here since establishment of the connection 
> itself could be considered a connectivity check. As such, I could go 
> either way.
> 
> Do you have a preference here, and if so, why?

I would have tought that the connection itself would be sufficient, but
maybe I'm missing some advantage that the STUN/TCP option would have. 

Anything in mind?

------_=_NextPart_001_01C50A3D.9EE18F23
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2658.2">
<TITLE>RE: [MMUSIC] ICE feature - TCP alternates for a UDP stream</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=2>&gt; My first inclination was that you would still use STUN for the </FONT>
<BR><FONT SIZE=2>&gt; connectivity check over TCP; irregardless of whether that tcp </FONT>
<BR><FONT SIZE=2>&gt; is through </FONT>
<BR><FONT SIZE=2>&gt; a TURN relay or direct (indeed, the peer in the call won't </FONT>
<BR><FONT SIZE=2>&gt; normally even </FONT>
<BR><FONT SIZE=2>&gt; know whether the tcp connection it will make is direct or through a </FONT>
<BR><FONT SIZE=2>&gt; relay). Recall that stun can run over tcp.</FONT>
</P>

<P><FONT SIZE=2>Hum. If we are to use STUN on TCP, I think we need to clarify in </FONT>
<BR><FONT SIZE=2>draft-ietf-behave-rfc3489bis how it works. There are a number of</FONT>
<BR><FONT SIZE=2>statements in there that sort of imply that it doesn't work with TCP.</FONT>
</P>

<P><FONT SIZE=2>Are you saying that you would send the binding requests on TCP?</FONT>
</P>

<P><FONT SIZE=2>Can you clarify what you mean by STUN over TCP?</FONT>
</P>

<P><FONT SIZE=2>&gt; However, it is less useful here since establishment of the connection </FONT>
<BR><FONT SIZE=2>&gt; itself could be considered a connectivity check. As such, I could go </FONT>
<BR><FONT SIZE=2>&gt; either way.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Do you have a preference here, and if so, why?</FONT>
</P>

<P><FONT SIZE=2>I would have tought that the connection itself would be sufficient, but</FONT>
<BR><FONT SIZE=2>maybe I'm missing some advantage that the STUN/TCP option would have. </FONT>
</P>

<P><FONT SIZE=2>Anything in mind?</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C50A3D.9EE18F23--


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

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

--===============2057758274==--



From mmusic-bounces@ietf.org  Fri Feb  4 02:29:42 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28658
	for <mmusic-web-archive@ietf.org>; Fri, 4 Feb 2005 02:29:42 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CwyDB-0008RP-R2
	for mmusic-web-archive@ietf.org; Fri, 04 Feb 2005 02:49:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CwxsA-0004Wu-GP; Fri, 04 Feb 2005 02:27:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cwxlx-0000wy-9U
	for mmusic@megatron.ietf.org; Fri, 04 Feb 2005 02:20:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27975
	for <mmusic@ietf.org>; Fri, 4 Feb 2005 02:20:55 -0500 (EST)
Received: from mailserv.intranet.gr ([146.124.14.106])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cwy4d-0008GC-ON
	for mmusic@ietf.org; Fri, 04 Feb 2005 02:40:18 -0500
Received: from mailserv.intranet.gr (localhost [127.0.0.1])
	by mailserv.intranet.gr (8.13.1/8.13.1) with ESMTP id j147NBbB000538
	for <mmusic@ietf.org>; Fri, 4 Feb 2005 09:23:11 +0200 (EET)
Received: from aiolos.intranet.gr (aiolos.intranet.GR [146.124.6.7])
	by mailserv.intranet.gr (8.13.1/8.13.1) with ESMTP id j147N8QM000492;
	Fri, 4 Feb 2005 09:23:08 +0200 (EET)
Received: from pcnt189 (pcnt189 [146.124.44.189])
	by aiolos.intranet.gr (8.11.7p1+Sun/8.11.7) with SMTP id j147PGF22030; 
	Fri, 4 Feb 2005 09:25:16 +0200 (EET)
From: "Spiros Spirou" <spis@intracom.gr>
To: "Thomas Zeng" <zeng@pvnetsolutions.com>,
        "Joerg Ott" <jo@informatik.uni-bremen.de>
Subject: RE: [MMUSIC] End of movie signalling
Date: Fri, 4 Feb 2005 09:21:19 +0100
Message-ID: <PPEPKGOKJJGOIIEBKKOEEEGKDAAA.spis@intracom.gr>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
In-Reply-To: <758B5A159B385447B4F950DE72D7D7AD678C71@srsdmail01.PVNS.COM>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Content-Transfer-Encoding: 7bit
Cc: IETF mmusic WG list <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
Content-Transfer-Encoding: 7bit

Hi Thomas,

Thanks for the suggestion. I had thought about that but I am trying to cover
cases where the server is not implementing RTCP as well (oh yes, these heathens
do exist). Anyway, the four reasons you are mentioning in Appendix A of
draft-ietf-mmusic-rtsp-announce-00.txt against the use of RTCP BYE as an
end-of-stream signaling mechanism are certainly valid in general.

I am oriented towards maintaining a presentation clock (npt) in the client for
detecting EOS locally in the case of RFC2326 servers. This has the added feature
of being able to display to the user the running play time, remaining time etc.
just like DVD players can. I could add support for
draft-ietf-mmusic-rtsp-announce-00.txt as it progresses in order to be forwards
compatible.

Spiros

-----Original Message-----
From: Thomas Zeng [mailto:zeng@pvnetsolutions.com]
Sent: Thursday, February 03, 2005 6:43 PM
To: Spiros Spirou; Joerg Ott
Cc: IETF mmusic WG list
Subject: RE: [MMUSIC] End of movie signalling


Hi  Spiros:

Your transport is RTP, right? Can you not use RTCP BYE to signal end-of-stream
until draft-ietf-mmusic-rfc2326bis-08.txt and
draft-ietf-mmusic-rtsp-announce-00.txt are ratified?

Cheers,
-thomas

-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org]On Behalf
Of Spiros Spirou
Sent: Thursday, February 03, 2005 4:08 AM
To: Joerg Ott
Cc: IETF mmusic WG list
Subject: RE: [MMUSIC] End of movie signalling


Hi Joerg,

Thanks for the pointers. Reading between the lines, I would say that there is no
provisioned mechanism for signaling end-of-stream using RFC2326 means only.
Implementations wishing to be backwards compatible should probably revert to
costly tricks. Is this correct?

Spiros

-----Original Message-----
From: Joerg Ott [mailto:jo@informatik.uni-bremen.de]
Sent: Thursday, February 03, 2005 10:23 AM
To: Spiros Spirou
Cc: IETF mmusic WG list; Joerg Ott
Subject: Re: [MMUSIC] End of movie signalling


Hi Spiros,

what you are looking for is being addressed in an addition to the
revised RTSP spec: draft-ietf-mmusic-rtsp-announce-00.txt defines
a generic announcement mechanism that, among other uses, the server
can use to signal end-of-stream to the client.

Please also take a look draft-ietf-mmusic-rfc2326bis-08.txt,
the updated RTSP spec that is supposed to override RFC 2326 in the
not too distant future.

Joerg

>
> Hi,
>
> In a VoD scenario, I am trying to find a STANDARD way to detect the end of a
> movie in the client in order to free the associated resources for control
> (RTSP), transport (RTP) and play-out.
>
> RFC 2326 states that when the server reaches the end of the movie it "...
> reverts from state Playing ... to state Ready ...". From there "... it MAY
> revert to Init and tear down the RTSP session if it has not received
> \"wellness\" information, such as RTCP reports or RTSP commands, from the
client
> for a defined interval, with a default of one minute." Both of these state
> changes happen without sending any notification to the client.
>
> Now, the client could detect the end of movie on its own by maintaining a
> presentation clock, set initially by the Range header in the PLAY reply.
> However, this would probably involve polling, which seems incorrect given the
> usual scarcity of resources in the client platform. A variant of this method
> would be to poll the server by sending PLAY requests without a Range header
and
> reading the current presentation time in the Range header of the reply. This
> adds waste of bandwidth to the waste of local resources.
>
> Any ideas?
>
> Spiros
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
>



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



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


From mmusic-bounces@ietf.org  Fri Feb  4 04:29:43 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05964
	for <mmusic-web-archive@ietf.org>; Fri, 4 Feb 2005 04:29:43 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cx05M-0002yJ-FH
	for mmusic-web-archive@ietf.org; Fri, 04 Feb 2005 04:49:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cwzjc-0008Ve-6S; Fri, 04 Feb 2005 04:26:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cwzaz-00062O-Rm
	for mmusic@megatron.ietf.org; Fri, 04 Feb 2005 04:17:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05156
	for <mmusic@ietf.org>; Fri, 4 Feb 2005 04:17:43 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cwzti-0002f8-2k
	for mmusic@ietf.org; Fri, 04 Feb 2005 04:37:08 -0500
Received: from esealmw127.eemea.ericsson.se ([153.88.254.122])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j149HSOA028811; Fri, 4 Feb 2005 10:17:38 +0100
Received: from esealmw129.eemea.ericsson.se ([153.88.254.173]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 4 Feb 2005 10:17:52 +0100
Received: from [147.214.237.66] ([147.214.237.66]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 4 Feb 2005 10:17:51 +0100
Message-ID: <42033DAD.6090401@ericsson.com>
Date: Fri, 04 Feb 2005 10:17:33 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Thomas Zeng <zeng@pvnetsolutions.com>
Subject: Re: [MMUSIC] End of movie signalling
References: <758B5A159B385447B4F950DE72D7D7AD678C71@srsdmail01.PVNS.COM>
In-Reply-To: <758B5A159B385447B4F950DE72D7D7AD678C71@srsdmail01.PVNS.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Feb 2005 09:17:51.0700 (UTC)
	FILETIME=[66DE1940:01C50A9A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
Cc: Spiros Spirou <spis@intracom.gr>, IETF mmusic WG list <mmusic@ietf.org>,
        Joerg Ott <jo@informatik.uni-bremen.de>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit

Hi,

Thomas Zeng wrote:
> Hi  Spiros:
> 
> Your transport is RTP, right? Can you not use RTCP BYE to signal end-of-stream until draft-ietf-mmusic-rfc2326bis-08.txt and draft-ietf-mmusic-rtsp-announce-00.txt are ratified?
> 

I would like to point out that if one sends a RTCP BYE, that means that 
the SSRC sending the BYE is leaving the session. Thus you get some 
semantics that is not desirable by using RTCP BYE for end of stream 
notification. I know that it occurs, but in my eyes it is not a correct 
behavior and should not be endorsed.

The RTCP BYE message should comes as a result of a TEARDOWN of that RTP 
session. A SETUP that changes the RTP session, like new ports should 
also result in RTCP BYE on the old session.

Cheers

Magnus Westerlund

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

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


From mmusic-bounces@ietf.org  Fri Feb  4 04:52:47 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07480
	for <mmusic-web-archive@ietf.org>; Fri, 4 Feb 2005 04:52:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cx0Re-0003cR-Nv
	for mmusic-web-archive@ietf.org; Fri, 04 Feb 2005 05:12:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cx06Z-0006ib-Gm; Fri, 04 Feb 2005 04:50:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cwzzc-0003xq-9f
	for mmusic@megatron.ietf.org; Fri, 04 Feb 2005 04:43:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06775
	for <mmusic@ietf.org>; Fri, 4 Feb 2005 04:43:09 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cx0IM-0003Lg-Gu
	for mmusic@ietf.org; Fri, 04 Feb 2005 05:02:35 -0500
Received: from esealmw128.eemea.ericsson.se ([153.88.254.121])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j149g7OE003469; Fri, 4 Feb 2005 10:42:09 +0100
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 4 Feb 2005 10:42:26 +0100
Received: from [147.214.237.66] ([147.214.237.66]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 4 Feb 2005 10:42:25 +0100
Message-ID: <4203436B.7040106@ericsson.com>
Date: Fri, 04 Feb 2005 10:42:03 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@cisco.com>
Subject: Re: [MMUSIC] ICE feature - TCP alternates for a UDP stream
References: <41F9361B.1030206@cisco.com>
In-Reply-To: <41F9361B.1030206@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Feb 2005 09:42:25.0881 (UTC)
	FILETIME=[D58C4490:01C50A9D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
Cc: IETF MMUSIC WG <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit

Hi Jonathan,

Some questions.

The first problem I see is the signalling:

m=audio 49170 RTP/AVP 0
a=candidate 1 0.4 adsasda 9as8dasd 1.2.3.4 49170 10.0.1.1 8700
a=candidate 1 0.4 asf9fdf8 00d-ffas 1.2.3.4 49171 10.0.1.1 8765

As you need a "m=" line with
m=audio 9 TCP/RTP/AVP 0

to indicate that contrans framing should be used over TCP. Thus you need 
a binding attribute to bind the media blocks together, much like the 
grouping of media lines grouping semantic "ANAT" but now for different 
protocol identifiers.

I know that you proposed another way, however we do need to use explicit 
protocol identifiers for this in my opinion. If I would like to use 
another framing mechanism, or run protocol foo over foo with ICE your 
proposal would block it. Also there is certain mechanism like security 
and that are transport dependent and which parameters are specified on 
media block level. If you group things under the candidate attribute you 
create huge problem deploying current and future mechanism.

Also isn't there a uncertainty in the demultiplexing of contrans frames 
and STUN packets if sent over the same TCP connection. In contrans it is 
quite likely that the first byte is 0, this will be true for all RTP 
packets smaller than 255 bytes, which is most audio. Have you worked out 
if you can end up with a reliable demultiplexing in this case.

I also don't know about standardizing firewall circumvention techniques. 
I do understand most would consider this a solution for the homes that 
run a FW without the knowledge to configure it correctly. However it is 
still going into a questionable land.

Cheers

Magnus Westerlund

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

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


From mmusic-bounces@ietf.org  Fri Feb  4 09:46:51 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02240
	for <mmusic-web-archive@ietf.org>; Fri, 4 Feb 2005 09:46:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cx52I-0003P6-MG
	for mmusic-web-archive@ietf.org; Fri, 04 Feb 2005 10:06:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cx4ga-0007vb-Cl; Fri, 04 Feb 2005 09:43:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx4aV-0006W5-Li
	for mmusic@megatron.ietf.org; Fri, 04 Feb 2005 09:37:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01543
	for <mmusic@ietf.org>; Fri, 4 Feb 2005 09:37:33 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cx4tH-00038x-Ju
	for mmusic@ietf.org; Fri, 04 Feb 2005 09:57:01 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 04 Feb 2005 06:44:45 -0800
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j14Eb0F1012206;
	Fri, 4 Feb 2005 06:37:01 -0800 (PST)
Received: from [192.168.1.100] (che-vpn-cluster-1-149.cisco.com
	[10.86.240.149]) by mira-sjc5-d.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AHN18709; Fri, 4 Feb 2005 06:36:59 -0800 (PST)
Message-ID: <4203888A.5020406@cisco.com>
Date: Fri, 04 Feb 2005 09:36:58 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Re: [MMUSIC] ICE feature - TCP alternates for a UDP stream
References: <41F9361B.1030206@cisco.com> <4203436B.7040106@ericsson.com>
In-Reply-To: <4203436B.7040106@ericsson.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Content-Transfer-Encoding: 7bit
Cc: IETF MMUSIC WG <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Content-Transfer-Encoding: 7bit



Magnus Westerlund wrote:

> Hi Jonathan,
> 
> Some questions.
> 
> The first problem I see is the signalling:
> 
> m=audio 49170 RTP/AVP 0
> a=candidate 1 0.4 adsasda 9as8dasd 1.2.3.4 49170 10.0.1.1 8700
> a=candidate 1 0.4 asf9fdf8 00d-ffas 1.2.3.4 49171 10.0.1.1 8765
> 
> As you need a "m=" line with
> m=audio 9 TCP/RTP/AVP 0

The m line would be for UDP. The candidate would be the thing that 
indicates TCP:

m=audio 49170 RTP/AVP 0
a=candidate 1 0.4 adsasda 9as8dasd 1.2.3.4 49170 TCP 10.0.1.1 passive
a=candidate 1 0.4 asf9fdf8 00d-ffas 1.2.3.4 49171 UDP 10.0.1.1 8765

where the first candidate lists a TCP alternative to the UDP "primary" 
stream, and the second candidate lists a UDP alternative.

I
> 
> to indicate that contrans framing should be used over TCP. Thus you need 
> a binding attribute to bind the media blocks together, much like the 
> grouping of media lines grouping semantic "ANAT" but now for different 
> protocol identifiers.

The idea is that any information about the candidate will go in the line 
that defines the candidate. As such, I don't think there is a need for 
the grouping framework.


> 
> I know that you proposed another way, however we do need to use explicit 
> protocol identifiers for this in my opinion. If I would like to use 
> another framing mechanism, or run protocol foo over foo with ICE your 
> proposal would block it. Also there is certain mechanism like security 
> and that are transport dependent and which parameters are specified on 
> media block level. If you group things under the candidate attribute you 
> create huge problem deploying current and future mechanism.

OK, I understand your point. I think that it really depends on how much 
of the information that needs to be conveyed is actually transport 
dependent. You mention security. Are the SRTP parameters transport 
dependent? I didnt think so....

> 
> Also isn't there a uncertainty in the demultiplexing of contrans frames 
> and STUN packets if sent over the same TCP connection. In contrans it is 
> quite likely that the first byte is 0, this will be true for all RTP 
> packets smaller than 255 bytes, which is most audio. Have you worked out 
> if you can end up with a reliable demultiplexing in this case.

I havent considered it fully yet. I will say, per the discussion with 
Francois, it is not clear that the STUN connectivity checks are really 
needed over TCP, so it may be a moot point.

> 
> I also don't know about standardizing firewall circumvention techniques. 
> I do understand most would consider this a solution for the homes that 
> run a FW without the knowledge to configure it correctly. However it is 
> still going into a questionable land.

Its not a circumvention technique at all. Circumvention is when you try 
to make one protocol look like another in order to get traffic through a 
more permissive policy that is associated with the other protocol. Here, 
we aren't making RTP look like anything it already isn't. We already 
HAVE a way of transporting RTP over TCP. What we don't have is a way for 
me to usefully figure out whether I should use that mechanism or use RTP 
over UDP. ICE provides that part of the solution.

-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

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


From mmusic-bounces@ietf.org  Fri Feb  4 10:42:54 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07825
	for <mmusic-web-archive@ietf.org>; Fri, 4 Feb 2005 10:42:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cx5uY-0004ft-2q
	for mmusic-web-archive@ietf.org; Fri, 04 Feb 2005 11:02:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cx5Sb-0001QP-Mx; Fri, 04 Feb 2005 10:33:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx5Kh-0006Ql-UT
	for mmusic@megatron.ietf.org; Fri, 04 Feb 2005 10:25:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06295
	for <mmusic@ietf.org>; Fri, 4 Feb 2005 10:25:17 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cx5dU-0004Ft-3N
	for mmusic@ietf.org; Fri, 04 Feb 2005 10:44:45 -0500
Received: from sj-core-3.cisco.com (171.68.223.137)
	by sj-iport-5.cisco.com with ESMTP; 04 Feb 2005 07:25:01 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j14FOhPA017709;
	Fri, 4 Feb 2005 07:24:44 -0800 (PST)
Received: from [192.168.1.100] (che-vpn-cluster-1-149.cisco.com
	[10.86.240.149]) by mira-sjc5-d.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AHN21061; Fri, 4 Feb 2005 07:24:42 -0800 (PST)
Message-ID: <420393BA.9080407@cisco.com>
Date: Fri, 04 Feb 2005 10:24:42 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francois Audet <audet@nortel.com>
Subject: Re: [MMUSIC] ICE feature - TCP alternates for a UDP stream
References: <1ECE0EB50388174790F9694F77522CCF016F511D@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF016F511D@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
Cc: "'IETF MMUSIC WG'" <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit

inline.

Francois Audet wrote:

>
>  > My first inclination was that you would still use STUN for the
>  > connectivity check over TCP; irregardless of whether that tcp
>  > is through
>  > a TURN relay or direct (indeed, the peer in the call won't
>  > normally even
>  > know whether the tcp connection it will make is direct or through a
>  > relay). Recall that stun can run over tcp.
> 
> Hum. If we are to use STUN on TCP, I think we need to clarify in
> draft-ietf-behave-rfc3489bis how it works. There are a number of
> statements in there that sort of imply that it doesn't work with TCP.

Binding allocation won't work, but you can send a request and get a 
response. Remember that the shared secret allocation messages all run 
over tcp.

> 
> Are you saying that you would send the binding requests on TCP?

Yes, but they would do nothing more than checking liveness of the tcp 
connection.


> I would have tought that the connection itself would be sufficient, but
> maybe I'm missing some advantage that the STUN/TCP option would have.
> 
> Anything in mind?
> 

I had in mind some bizarre cases where the connection does get set up, 
but somehow the nat discards state and data can't actually get 
transmitted. Not sure this is worth worrying about.

-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

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


From mmusic-bounces@ietf.org  Fri Feb  4 11:27:40 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12011
	for <mmusic-web-archive@ietf.org>; Fri, 4 Feb 2005 11:27:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cx6br-0005jB-EV
	for mmusic-web-archive@ietf.org; Fri, 04 Feb 2005 11:47:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cx6Fw-0008K7-C7; Fri, 04 Feb 2005 11:24:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx6CF-0007Ox-SD
	for mmusic@megatron.ietf.org; Fri, 04 Feb 2005 11:20:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11443
	for <mmusic@ietf.org>; Fri, 4 Feb 2005 11:20:37 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cx6V0-0005YQ-8P
	for mmusic@ietf.org; Fri, 04 Feb 2005 11:40:06 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j14GKVh5029582
	for <mmusic@ietf.org>; Fri, 4 Feb 2005 17:20:31 +0100 (MET)
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 4 Feb 2005 17:20:48 +0100
Received: from [147.214.237.66] (minint-9ey8rh [147.214.237.66]) by
	esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id DT1QW126; Fri, 4 Feb 2005 17:20:30 +0100
Message-ID: <4203A0CE.1050703@ericsson.com>
Date: Fri, 04 Feb 2005 17:20:30 +0100
X-Sybari-Trust: 05573376 b8ec86c7 fcbbd1d7 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@cisco.com>
Subject: Re: [MMUSIC] ICE feature - TCP alternates for a UDP stream
References: <4203888A.5020406@cisco.com>
In-Reply-To: <4203888A.5020406@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Feb 2005 16:20:48.0347 (UTC)
	FILETIME=[7C8722B0:01C50AD5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Content-Transfer-Encoding: 7bit
Cc: IETF MMUSIC WG <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Content-Transfer-Encoding: 7bit

Hi,

See inline

Jonathan Rosenberg wrote:
> 
> Magnus Westerlund wrote:
> 
> 
>>Hi Jonathan,
>>
>>Some questions.
>>
>>The first problem I see is the signalling:
>>
>>m=audio 49170 RTP/AVP 0
>>a=candidate 1 0.4 adsasda 9as8dasd 1.2.3.4 49170 10.0.1.1 8700
>>a=candidate 1 0.4 asf9fdf8 00d-ffas 1.2.3.4 49171 10.0.1.1 8765
>>
>>As you need a "m=" line with
>>m=audio 9 TCP/RTP/AVP 0
> 
> 
> The m line would be for UDP. The candidate would be the thing that 
> indicates TCP:
> 
> m=audio 49170 RTP/AVP 0
> a=candidate 1 0.4 adsasda 9as8dasd 1.2.3.4 49170 TCP 10.0.1.1 passive
> a=candidate 1 0.4 asf9fdf8 00d-ffas 1.2.3.4 49171 UDP 10.0.1.1 8765
> 
> where the first candidate lists a TCP alternative to the UDP "primary" 
> stream, and the second candidate lists a UDP alternative.
> 

Yes, I assumed already before that something like this what was you 
talked about. However the problem is that it is not obvious that you can 
use the same RTP profiles over different transports. For example there 
might not be the same need for AVPF if you use TCP (In fact we don't 
have AVPF for TCP currently). So if I like to primarily use UDP/RTP/AVPF 
and if that fails TCP/RTP/AVP. That can't be expressed with you 
proposal. I would also like to point out that you need different 
parameters for the different cases.

We have in AVT been burned by how the RFC 2733 FEC session was done. For 
the moment it is impossible to use security or feedback with RFC 2733 
FEC because we can't specify the parameters for it due to the embedding 
of a session instance within the media block. It really creates a real 
problem as soon as you develop new things that can be used in 
conjunction. The whole signalling in SDP is defined around the fact that 
different streams have different "m=" lines. I know that SDP is a 
horrible mess, but it becomes even a bigger one if we don't follow its 
structure and just put things in there without thought.


> 
>>I know that you proposed another way, however we do need to use explicit 
>>protocol identifiers for this in my opinion. If I would like to use 
>>another framing mechanism, or run protocol foo over foo with ICE your 
>>proposal would block it. Also there is certain mechanism like security 
>>and that are transport dependent and which parameters are specified on 
>>media block level. If you group things under the candidate attribute you 
>>create huge problem deploying current and future mechanism.
> 
> 
> OK, I understand your point. I think that it really depends on how much 
> of the information that needs to be conveyed is actually transport 
> dependent. You mention security. Are the SRTP parameters transport 
> dependent? I didnt think so....

I think security is a good example. Currently we don't know what 
security to do over TCP. We haven't defined TCP/RTP/SAVP and 
TCP/TLS/RTP/AVP is proposed. So there is definitely risk that there will 
be different parameters depending on transport. I also hinted on 
feedback related difference. From a RTP perspective TCP isn't quite the 
same as UDP and needs to be handled differently in an implementation. 
For example the handling of the congestion control is a bit different.

> 
> 
>>Also isn't there a uncertainty in the demultiplexing of contrans frames 
>>and STUN packets if sent over the same TCP connection. In contrans it is 
>>quite likely that the first byte is 0, this will be true for all RTP 
>>packets smaller than 255 bytes, which is most audio. Have you worked out 
>>if you can end up with a reliable demultiplexing in this case.
> 
> 
> I havent considered it fully yet. I will say, per the discussion with 
> Francois, it is not clear that the STUN connectivity checks are really 
> needed over TCP, so it may be a moot point.
> 

Okay.

> 
>>I also don't know about standardizing firewall circumvention techniques. 
>>I do understand most would consider this a solution for the homes that 
>>run a FW without the knowledge to configure it correctly. However it is 
>>still going into a questionable land.
> 
> 
> Its not a circumvention technique at all. Circumvention is when you try 
> to make one protocol look like another in order to get traffic through a 
> more permissive policy that is associated with the other protocol. Here, 
> we aren't making RTP look like anything it already isn't. We already 
> HAVE a way of transporting RTP over TCP. What we don't have is a way for 
> me to usefully figure out whether I should use that mechanism or use RTP 
> over UDP. ICE provides that part of the solution.
> 

I do not fully agree, about if it is circumvention or not. I do 
understand the interest in developing a solution for this. The 
proprietary solutions do handle these cases, and the standard will be 
die if it doesn't work in the same scenarios. What I don't want is a 
short term hack that will cause us twice the amount of problems down the 
road as the original problem.


Cheers


Magnus Westerlund

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

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


From mmusic-bounces@ietf.org  Fri Feb  4 17:36:06 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14708
	for <mmusic-web-archive@ietf.org>; Fri, 4 Feb 2005 17:36:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CxCMV-0006dX-81
	for mmusic-web-archive@ietf.org; Fri, 04 Feb 2005 17:55:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CxByJ-0006v3-VM; Fri, 04 Feb 2005 17:30:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CxBxA-0006gz-2c
	for mmusic@megatron.ietf.org; Fri, 04 Feb 2005 17:29:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14233
	for <mmusic@ietf.org>; Fri, 4 Feb 2005 17:29:25 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxCG0-0006TO-A1
	for mmusic@ietf.org; Fri, 04 Feb 2005 17:48:57 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j14MSo806133; Fri, 4 Feb 2005 17:28:50 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <1J5AMXNP>; Fri, 4 Feb 2005 17:28:50 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF0174B3DB@zrc2hxm0.corp.nortel.com>
From: "Francois Audet" <audet@nortel.com>
To: "'Jonathan Rosenberg'" <jdrosen@cisco.com>
Subject: RE: [MMUSIC] ICE feature - TCP alternates for a UDP stream
Date: Fri, 4 Feb 2005 17:28:43 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.8 (/)
X-Scan-Signature: f2984bf50fb52a9e56055f779793d783
Cc: "'IETF MMUSIC WG'" <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0070093210=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: d008c19e97860b8641c1851f84665a75

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

--===============0070093210==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C50B08.E2AE98F8"

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

------_=_NextPart_001_01C50B08.E2AE98F8
Content-Type: text/plain

OK. I understand. It would just need to be documented in more 
details.

> -----Original Message-----
> From: Jonathan Rosenberg [mailto:jdrosen@cisco.com] 
> Sent: Friday, February 04, 2005 07:25
> To: Audet, Francois [SC100:9T51:EXCH]
> Cc: 'IETF MMUSIC WG'
> Subject: Re: [MMUSIC] ICE feature - TCP alternates for a UDP stream
> 
> 
> inline.
> 
> Francois Audet wrote:
> 
> >
> >  > My first inclination was that you would still use STUN 
> for the  > 
> > connectivity check over TCP; irregardless of whether that tcp  > is 
> > through  > a TURN relay or direct (indeed, the peer in the 
> call won't
> >  > normally even
> >  > know whether the tcp connection it will make is direct 
> or through a
> >  > relay). Recall that stun can run over tcp.
> > 
> > Hum. If we are to use STUN on TCP, I think we need to clarify in 
> > draft-ietf-behave-rfc3489bis how it works. There are a number of 
> > statements in there that sort of imply that it doesn't work 
> with TCP.
> 
> Binding allocation won't work, but you can send a request and get a 
> response. Remember that the shared secret allocation messages all run 
> over tcp.
> 
> > 
> > Are you saying that you would send the binding requests on TCP?
> 
> Yes, but they would do nothing more than checking liveness of the tcp 
> connection.
> 
> 
> > I would have tought that the connection itself would be sufficient, 
> > but maybe I'm missing some advantage that the STUN/TCP option would 
> > have.
> > 
> > Anything in mind?
> > 
> 
> I had in mind some bizarre cases where the connection does 
> get set up, 
> but somehow the nat discards state and data can't actually get 
> transmitted. Not sure this is worth worrying about.
> 
> -Jonathan R.
> 
> -- 
> Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
> Director, Service Provider VoIP Architecture   Parsippany, NJ 
> 07054-2711
> Cisco Systems
> jdrosen@cisco.com                              FAX:   (973) 952-5050
> http://www.jdrosen.net                         PHONE: (973) 952-5000
> http://www.cisco.com
> 
> 

------_=_NextPart_001_01C50B08.E2AE98F8
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: [MMUSIC] ICE feature - TCP alternates for a UDP =
stream</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>OK. I understand. It would just need to be documented =
in more </FONT>
<BR><FONT SIZE=3D2>details.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Jonathan Rosenberg [<A =
HREF=3D"mailto:jdrosen@cisco.com">mailto:jdrosen@cisco.com</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Friday, February 04, 2005 07:25</FONT>
<BR><FONT SIZE=3D2>&gt; To: Audet, Francois [SC100:9T51:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: 'IETF MMUSIC WG'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [MMUSIC] ICE feature - TCP =
alternates for a UDP stream</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; inline.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Francois Audet wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; My first inclination was that =
you would still use STUN </FONT>
<BR><FONT SIZE=3D2>&gt; for the&nbsp; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; connectivity check over TCP; irregardless =
of whether that tcp&nbsp; &gt; is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; through&nbsp; &gt; a TURN relay or direct =
(indeed, the peer in the </FONT>
<BR><FONT SIZE=3D2>&gt; call won't</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; normally even</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; know whether the tcp connection =
it will make is direct </FONT>
<BR><FONT SIZE=3D2>&gt; or through a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; &gt; relay). Recall that stun can =
run over tcp.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Hum. If we are to use STUN on TCP, I think =
we need to clarify in </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; draft-ietf-behave-rfc3489bis how it works. =
There are a number of </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; statements in there that sort of imply =
that it doesn't work </FONT>
<BR><FONT SIZE=3D2>&gt; with TCP.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Binding allocation won't work, but you can send =
a request and get a </FONT>
<BR><FONT SIZE=3D2>&gt; response. Remember that the shared secret =
allocation messages all run </FONT>
<BR><FONT SIZE=3D2>&gt; over tcp.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Are you saying that you would send the =
binding requests on TCP?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Yes, but they would do nothing more than =
checking liveness of the tcp </FONT>
<BR><FONT SIZE=3D2>&gt; connection.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I would have tought that the connection =
itself would be sufficient, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; but maybe I'm missing some advantage that =
the STUN/TCP option would </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; have.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Anything in mind?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I had in mind some bizarre cases where the =
connection does </FONT>
<BR><FONT SIZE=3D2>&gt; get set up, </FONT>
<BR><FONT SIZE=3D2>&gt; but somehow the nat discards state and data =
can't actually get </FONT>
<BR><FONT SIZE=3D2>&gt; transmitted. Not sure this is worth worrying =
about.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -Jonathan R.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -- </FONT>
<BR><FONT SIZE=3D2>&gt; Jonathan D. Rosenberg, =
Ph.D.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 600 Lanidex Plaza</FONT>
<BR><FONT SIZE=3D2>&gt; Director, Service Provider VoIP =
Architecture&nbsp;&nbsp; Parsippany, NJ </FONT>
<BR><FONT SIZE=3D2>&gt; 07054-2711</FONT>
<BR><FONT SIZE=3D2>&gt; Cisco Systems</FONT>
<BR><FONT SIZE=3D2>&gt; =
jdrosen@cisco.com&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FAX:&nbsp;&nbsp; (973) =
952-5050</FONT>
<BR><FONT SIZE=3D2>&gt; <A HREF=3D"http://www.jdrosen.net" =
TARGET=3D"_blank">http://www.jdrosen.net</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PHONE: (973) =
952-5000</FONT>
<BR><FONT SIZE=3D2>&gt; <A HREF=3D"http://www.cisco.com" =
TARGET=3D"_blank">http://www.cisco.com</A></FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C50B08.E2AE98F8--


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

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

--===============0070093210==--



From mmusic-bounces@ietf.org  Fri Feb  4 17:40:19 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15016
	for <mmusic-web-archive@ietf.org>; Fri, 4 Feb 2005 17:40:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CxCQX-0006jp-Pn
	for mmusic-web-archive@ietf.org; Fri, 04 Feb 2005 17:59:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CxC6F-0008Ls-VI; Fri, 04 Feb 2005 17:38:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CxC1g-0007KG-Ck
	for mmusic@megatron.ietf.org; Fri, 04 Feb 2005 17:34:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14590
	for <mmusic@ietf.org>; Fri, 4 Feb 2005 17:34:05 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxCKW-0006bb-TE
	for mmusic@ietf.org; Fri, 04 Feb 2005 17:53:38 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j14MXSk00176; Fri, 4 Feb 2005 17:33:28 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <1J5AMXTW>; Fri, 4 Feb 2005 17:33:28 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF0174B3E3@zrc2hxm0.corp.nortel.com>
From: "Francois Audet" <audet@nortel.com>
To: "'Magnus Westerlund'" <magnus.westerlund@ericsson.com>,
        "'Jonathan Rosenberg'" <jdrosen@cisco.com>
Subject: RE: [MMUSIC] ICE feature - TCP alternates for a UDP stream
Date: Fri, 4 Feb 2005 17:33:21 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: "'IETF MMUSIC WG'" <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0680523530=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b

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

--===============0680523530==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C50B09.889418AF"

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

------_=_NextPart_001_01C50B09.889418AF
Content-Type: text/plain



> I do not fully agree, about if it is circumvention or not. I do 
> understand the interest in developing a solution for this. The 
> proprietary solutions do handle these cases, and the standard will be 
> die if it doesn't work in the same scenarios. What I don't want is a 
> short term hack that will cause us twice the amount of 
> problems down the 
> road as the original problem.

Yeah, I'm also somewhat ambivalent on this. 

Is it really worthwile to have a back-off to TCP mechanism? Or should
we really instead take the stance that if the Firewall blocks UDP,
it is either because:

(1) They do NOT want to "real time media" going through. This may
    be the case for example on an Enterprise Firewall. In that
    particular case, then I think it is a circumvention.

(2) Always blocking UDP is essentially a feature deficiency of
    the Firewall, or a misconfiguration. Do we need to work around
    this or not is the question. 

I don't have a particularly strong opinion either way. 


------_=_NextPart_001_01C50B09.889418AF
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2658.2">
<TITLE>RE: [MMUSIC] ICE feature - TCP alternates for a UDP stream</TITLE>
</HEAD>
<BODY>
<BR>
<BR>

<P><FONT SIZE=2>&gt; I do not fully agree, about if it is circumvention or not. I do </FONT>
<BR><FONT SIZE=2>&gt; understand the interest in developing a solution for this. The </FONT>
<BR><FONT SIZE=2>&gt; proprietary solutions do handle these cases, and the standard will be </FONT>
<BR><FONT SIZE=2>&gt; die if it doesn't work in the same scenarios. What I don't want is a </FONT>
<BR><FONT SIZE=2>&gt; short term hack that will cause us twice the amount of </FONT>
<BR><FONT SIZE=2>&gt; problems down the </FONT>
<BR><FONT SIZE=2>&gt; road as the original problem.</FONT>
</P>

<P><FONT SIZE=2>Yeah, I'm also somewhat ambivalent on this. </FONT>
</P>

<P><FONT SIZE=2>Is it really worthwile to have a back-off to TCP mechanism? Or should</FONT>
<BR><FONT SIZE=2>we really instead take the stance that if the Firewall blocks UDP,</FONT>
<BR><FONT SIZE=2>it is either because:</FONT>
</P>

<P><FONT SIZE=2>(1) They do NOT want to &quot;real time media&quot; going through. This may</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; be the case for example on an Enterprise Firewall. In that</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; particular case, then I think it is a circumvention.</FONT>
</P>

<P><FONT SIZE=2>(2) Always blocking UDP is essentially a feature deficiency of</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; the Firewall, or a misconfiguration. Do we need to work around</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; this or not is the question. </FONT>
</P>

<P><FONT SIZE=2>I don't have a particularly strong opinion either way. </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C50B09.889418AF--


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

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

--===============0680523530==--



From mmusic-bounces@ietf.org  Sat Feb  5 08:25:37 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29782
	for <mmusic-web-archive@ietf.org>; Sat, 5 Feb 2005 08:25:37 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CxQFO-0007sc-Te
	for mmusic-web-archive@ietf.org; Sat, 05 Feb 2005 08:45:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CxPvP-0004x9-Px; Sat, 05 Feb 2005 08:24:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CxPtD-0004P8-J9
	for mmusic@megatron.ietf.org; Sat, 05 Feb 2005 08:22:19 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29627
	for <mmusic@ietf.org>; Sat, 5 Feb 2005 08:22:18 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxQCB-0007o6-QV
	for mmusic@ietf.org; Sat, 05 Feb 2005 08:41:57 -0500
Received: from sj-core-4.cisco.com (171.68.223.138)
	by sj-iport-4.cisco.com with ESMTP; 05 Feb 2005 05:22:13 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j15DLiYO019322;
	Sat, 5 Feb 2005 05:21:44 -0800 (PST)
Received: from [192.168.1.100] (che-vpn-cluster-1-108.cisco.com
	[10.86.240.108]) by mira-sjc5-d.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AHN84566; Sat, 5 Feb 2005 05:21:42 -0800 (PST)
Message-ID: <4204C866.5050300@cisco.com>
Date: Sat, 05 Feb 2005 08:21:42 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francois Audet <audet@nortel.com>
Subject: Re: [MMUSIC] ICE feature - TCP alternates for a UDP stream
References: <1ECE0EB50388174790F9694F77522CCF0174B3E3@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF0174B3E3@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit
Cc: "'Magnus Westerlund'" <magnus.westerlund@ericsson.com>,
        "'IETF MMUSIC WG'" <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: 7bit

inline.

Francois Audet wrote:

> 
> 
>  > I do not fully agree, about if it is circumvention or not. I do
>  > understand the interest in developing a solution for this. The
>  > proprietary solutions do handle these cases, and the standard will be
>  > die if it doesn't work in the same scenarios. What I don't want is a
>  > short term hack that will cause us twice the amount of
>  > problems down the
>  > road as the original problem.
> 
> Yeah, I'm also somewhat ambivalent on this.
> 
> Is it really worthwile to have a back-off to TCP mechanism? Or should
> we really instead take the stance that if the Firewall blocks UDP,
> it is either because:
> 
> (1) They do NOT want to "real time media" going through. This may
>     be the case for example on an Enterprise Firewall. In that
>     particular case, then I think it is a circumvention.
> 
> (2) Always blocking UDP is essentially a feature deficiency of
>     the Firewall, or a misconfiguration. Do we need to work around
>     this or not is the question.

Case (2) is the one I am worried about. In particular, it appears that 
there are numerous firewalls that do, in fact, allow outbound UDP, but 
they aren't capable of maintaining state to correlate in incoming UDP 
packet with the previous outgoing one. As a result, the incoming UDP 
packet is dropped.

Other enterprises block UDP not because of a desire to block multimedia 
traffic, but because UDP lacks the notion of a connection that can be 
tracked and terminated if needed.

I'll once again re-iterate that all of this is primarily around the 
issue of whether or not to run RTP over TCP. That is already a decision 
we have made. ICE is merely helping figure out if that option should be 
used or not.

-Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

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


From mmusic-bounces@ietf.org  Sun Feb  6 07:23:48 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17013
	for <mmusic-web-archive@ietf.org>; Sun, 6 Feb 2005 07:23:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CxllK-00045Q-On
	for mmusic-web-archive@ietf.org; Sun, 06 Feb 2005 07:43:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CxlR1-00008I-Nw; Sun, 06 Feb 2005 07:22:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CxlPl-0008GK-FK
	for mmusic@megatron.ietf.org; Sun, 06 Feb 2005 07:21:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16893
	for <mmusic@ietf.org>; Sun, 6 Feb 2005 07:21:20 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cxliw-00042E-DT
	for mmusic@ietf.org; Sun, 06 Feb 2005 07:41:10 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:62937
	helo=[192.168.0.2])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1CxlPF-0005It-1m; Sun, 06 Feb 2005 12:20:49 +0000
In-Reply-To: <41ED03F2.2090405@ericsson.com>
References: <41BECE64.3040401@ericsson.com> <41C0354C.5080403@ericsson.com>
	<6843E474-502D-11D9-8152-000A957FC5F2@csperkins.org>
	<41ED03F2.2090405@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <0ba148bda1217515d4291cb1376ecea4@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Working group last
	call:	draft-ietf-mmusic-sdp-media-label-00.txt
Date: Sun, 6 Feb 2005 12:20:45 +0000
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Content-Transfer-Encoding: 7bit
Cc: Orit Levin <oritl@microsoft.com>, Joerg Ott <jo@tzi.uni-bremen.de>,
        IETF MMUSIC Working Group <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Content-Transfer-Encoding: 7bit

There have been no objections to the revision, so we will assume that  
it addresses the last call comments.  Accordingly, we will request the  
IESG publish this draft as a proposed standard RFC.

Colin


On 18 Jan 2005, at 12:41, Gonzalo Camarillo wrote:

> Colin,
>
> a new revision of the draft that addresses the comments received  
> during its WGLC is already in the archives:
>
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-media-label 
> -01.txt
>
> Feel free to request its publication as an RFC whenever you wish.
>
> Thanks,
>
> Gonzalo
>
> Colin Perkins wrote:
>
>> This last call ends today. It looks like there are minor issues to be  
>> resolved in an updated draft. Once the revised draft is available,  
>> we'll allow a short time to check that all comments have been  
>> addressed, then advance the draft.
>> Colin
>> On 15 Dec 2004, at 12:59, Magnus Westerlund wrote:
>>> Hi Gonzalo,
>>>
>>> The proposed changes looks fine. See below about point 3.
>>>
>>> Gonzalo Camarillo (JO/LMF) wrote:
>>>
>>>>  > 3. Section 5. I am a bit worried about the offer/answer section.  
>>>> It is
>>>>  > very unclear on the handling of this attribute. Can we really  
>>>> trust
>>>>  > applications to define such behavior? From my work with  
>>>> Offer/Answer I
>>>>  > sometimes find it difficult to get the right behavior out of SDP  
>>>> in
>>>>  > offer/answer usage. If this behavior is left to the application  
>>>> then
>>>>  > there is need for a much more explicit section that explains the
>>>>  > different choices. Also I think using application defined  
>>>> behavior will
>>>>  > result in quite divergent behavior.
>>>> If this was an attribute that had any influence in the offer/answer
>>>> behabior I would agree with you. But this attribute, from the
>>>> offer/answer point of view, is just informational. That's why  
>>>> offerers
>>>> and answerers can use it as the wish. It does not have any  
>>>> influence in
>>>> the session being established.
>>>> The behavior we expect applications to define would be something  
>>>> like,
>>>> "use the same label in the media line as in the XML document you are
>>>> using to describe your conference". Note that this attribute is  
>>>> always
>>>> for the remote's UA information, so, the values that this attribute
>>>> takes in an answer is completely independent from the value it  
>>>> takes in
>>>> the offer.
>>>
>>>
>>> Okay, I do understand. I think it is okay with the current text.
>>>
>>>
>>> Cheers
>>>
>>> Magnus Westerlund
>>>
>>> Multimedia Technologies, Ericsson Research EAB/TVA/A
>>> --------------------------------------------------------------------- 
>>> -
>>> Ericsson AB                | Phone +46 8 4048287
>>> Torshamsgatan 23           | Fax   +46 8 7575550
>>> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mmusic
>>>
>
> -- 
> Gonzalo Camarillo         Phone :  +358  9 299 33 71
> Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> Telecom R&D               Fax   :  +358  9 299 30 52
> FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> Finland                   http://www.hut.fi/~gonzalo
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
>


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


From mmusic-bounces@ietf.org  Sun Feb  6 12:15:27 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09750
	for <mmusic-web-archive@ietf.org>; Sun, 6 Feb 2005 12:15:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CxqJd-0001c4-MW
	for mmusic-web-archive@ietf.org; Sun, 06 Feb 2005 12:35:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cxpxj-00062f-Qf; Sun, 06 Feb 2005 12:12:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CxprI-0004EB-RZ
	for mmusic@megatron.ietf.org; Sun, 06 Feb 2005 12:06:07 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08841
	for <mmusic@ietf.org>; Sun, 6 Feb 2005 12:06:02 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxqAV-0001Iv-Qn
	for mmusic@ietf.org; Sun, 06 Feb 2005 12:25:57 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:61148
	helo=[192.168.0.2])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1Cxpq1-0003wX-B4; Sun, 06 Feb 2005 17:04:45 +0000
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF01347A35@zrc2hxm0.corp.nortel.com>
References: <1ECE0EB50388174790F9694F77522CCF01347A35@zrc2hxm0.corp.nortel.com>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <104341bd2bf70038c38aa72ea4084364@csperkins.org>
Content-Transfer-Encoding: quoted-printable
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] WGLC: draft-ietf-mmusic-sdp-new-23.txt
Date: Sun, 6 Feb 2005 17:04:41 +0000
To: "Francois Audet" <audet@nortelnetworks.com>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: quoted-printable
Cc: "'Cullen Jennings'" <fluffy@cisco.com>,
        "'mmusic@ietf.org'" <mmusic@ietf.org>,
        "'M.Handley@cs.ucl.ac.uk'" <M.Handley@cs.ucl.ac.uk>,
        "'Joerg Ott'" <jo@tzi.uni-bremen.de>,
        "'van@packetdesign.com'" <van@packetdesign.com>,
        "'Stephen Casner'" <casner@acm.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: quoted-printable

Francois,

[Apologies for the slow response...]

On 20 Dec 2004, at 00:33, Francois Audet wrote:
> I would like to request a clarification in section 5.14 of
>  draft-ietf-mmusic-sdp-new-23.
>
> As we discovered in BEHAVE, certain SDP implementations are=20
> misinterpretting RFC 3550 section 11 2nd paragraph. In a SIP=20
> Offer/Answer for example, these implementations unilaterally change an=20=

> odd RTP port indicated in an SDP (from the other end) with to the even=20=

> port that one lower. In other words, if the other end indicates an RTP=20=

> port of 5201, these implemenations will send RTP to 5200, which will=20=

> be a big problem.
>
> Note that this issue is slightly orthogonal to the use of the rtcp=20
> attribute of RFC 3605. For example, if an application discovers (with=20=

> STUN or ICE) that its RTP port is 5201, it may then discover that it's=20=

> RTCP port is 5202 (which would satisfy the contiguity rule). This is=20=

> very likely to happen because NATs typically assign ports=20
> sequentially. An application could (somewhat foolishlingly) not use=20
> RFC 3605 in this case because it follows the contiguity rule (but not=20=

> the parity rule).
>
> Another issue is for implementations that do not support RTCP in the=20=

> first place.
>
> In order to avoid these problems, I propose that we explicitly state=20=

> that  the <port> for RTP indicates the actual port and MUST not be=20
> changed regardless of parity (i.e., DO NOT substract 1 if it is odd).
>
> I believe that would finally put to rest this parity issue for all SDP=20=

> based protocols.

What is the *exact* wording change you are proposing?

> Also, on a similar note, would it make sense to incorporate RFC 3605=20=

> (the=A0 directly into sdp-new, instead of having it stand as a =
separate=20
> RFC) and make its support mandatory? The biggest problem with RFC 3605=20=

> is that I can do the best SIP/SDP implementation possible, support=20
> STUN, ICE, 3605 and all, but if the other end doesn't support 3605=20
> (because they don't even know of NATs), the problem above will still=20=

> occur.

We don't mandate support for any of the attributes in SDP-new, so I=20
don't see any real benefit to including the RFC 3605 ("a=3Drtcp:")=20
attribute into the main SDP specification at this time.

Colin=


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


From mmusic-bounces@ietf.org  Sun Feb  6 12:16:21 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09853
	for <mmusic-web-archive@ietf.org>; Sun, 6 Feb 2005 12:16:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CxqKW-0001dd-9h
	for mmusic-web-archive@ietf.org; Sun, 06 Feb 2005 12:36:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cxpxk-00063Q-K5; Sun, 06 Feb 2005 12:12:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cxps7-0004Je-0j
	for mmusic@megatron.ietf.org; Sun, 06 Feb 2005 12:06:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08878
	for <mmusic@ietf.org>; Sun, 6 Feb 2005 12:06:52 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxqBL-0001K9-52
	for mmusic@ietf.org; Sun, 06 Feb 2005 12:26:47 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:61159
	helo=[192.168.0.2])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1Cxpra-00043p-Sl; Sun, 06 Feb 2005 17:06:23 +0000
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF013B8050@zrc2hxm0.corp.nortel.com>
References: <1ECE0EB50388174790F9694F77522CCF013B8050@zrc2hxm0.corp.nortel.com>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <3800c36dde4bc285c41f8e5775375f8c@csperkins.org>
Content-Transfer-Encoding: quoted-printable
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] WGLC: draft-ietf-mmusic-sdp-new-23.txt
Date: Sun, 6 Feb 2005 17:06:18 +0000
To: "Francois Audet" <audet@nortelnetworks.com>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: quoted-printable
Cc: "'Joerg Ott'" <jo@tzi.uni-bremen.de>,
        "'mmusic@ietf.org'" <mmusic@ietf.org>,
        "'Christer Holmberg \(JO/LMF\)'" <christer.holmberg@ericsson.com>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: quoted-printable

Christer, Francois,

My reading of this discussion is that there is no change needed to=20
SDP-new.
Colin


On 22 Dec 2004, at 19:16, Francois Audet wrote:
> > Hi,
> >
> > I have a small question.
> >
> > The sdp-new draft says that "inactive" is used to put users
> > on hold, while RFC3264(offer/answer) says that "sendonly" is used.
> >
> > Now, in the original SDP RFC, which RFC3246 refers to,
> > "inactive" was not defined, so I wonder if RFC3264 is to be updated?
> >
> > Or, are both hold mechanisms "according to the standard"?
>
> Yes.
>
> They are slighly different forms of "hold".
>
> SIP/SDP doesn't really have a concept of "hold" in the traditional=20
> telephony
> sense.
>
>  sendonly means that you can not receive media.
>
> inactive means that you can not receive media and that you are not=20
> sending
> either.
>
> They could both mean that you are "on hold". You can think of a Music=20=

> On Hold
> service,=A0 versus a normal Hold service. But neither necessarily =
means=20
> "hold" as per
> traditional telephony. You could send inactive or sendonly for reasons=20=

> that are
> not a logical hold, but just plain media pausing.
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic


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


From mmusic-bounces@ietf.org  Sun Feb  6 12:18:39 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10042
	for <mmusic-web-archive@ietf.org>; Sun, 6 Feb 2005 12:18:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CxqMj-0001gr-SJ
	for mmusic-web-archive@ietf.org; Sun, 06 Feb 2005 12:38:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cxq2Z-0008Es-Fi; Sun, 06 Feb 2005 12:17:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cxpyq-0006Wx-Du
	for mmusic@megatron.ietf.org; Sun, 06 Feb 2005 12:13:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09550
	for <mmusic@ietf.org>; Sun, 6 Feb 2005 12:13:50 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxqI3-0001Wz-K5
	for mmusic@ietf.org; Sun, 06 Feb 2005 12:33:44 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:61209
	helo=[192.168.0.2])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1CxpyK-0004x2-Bx; Sun, 06 Feb 2005 17:13:20 +0000
In-Reply-To: <41C5B167.1050203@tzi.uni-bremen.de>
References: <41C5B167.1050203@tzi.uni-bremen.de>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <1a95115a4a5f578089b5c76de4ec3204@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] WGLC: draft-ietf-mmusic-sdp-new-23.txt
Date: Sun, 6 Feb 2005 17:13:16 +0000
To: Joerg Ott <jo@tzi.uni-bremen.de>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit
Cc: mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit

Folks,

On 19 Dec 2004, at 16:50, Joerg Ott wrote:
> This is to announce Working Group Last Call on the revised
> SDP specification "SDP: Session Description Protocol"
> recently published as
>
>     draft-ietf-mmusic-sdp-new-23.txt
>
> The document shall be advanced to Proposed Standard (PS).
>
> The WGLC is to end on 9 January 2005.
>
> Please review the latest draft carefully and direct all comments
> to the MMUSIC list and the authors.

This last call period ended, with only minor comments (to which I have 
just responded). I propose to make the clarification change proposed by 
Francois Audet, provided we can quickly agree on wording, but make no 
other changes. If this is acceptable to the working group, I will make 
a -24 revision with this change, which will then be sent to the IESG.

Colin


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


From mmusic-bounces@ietf.org  Mon Feb  7 13:25:48 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26790
	for <mmusic-web-archive@ietf.org>; Mon, 7 Feb 2005 13:25:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CyDtV-0007Tt-9e
	for mmusic-web-archive@ietf.org; Mon, 07 Feb 2005 13:45:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CyDUs-0007Az-4F; Mon, 07 Feb 2005 13:20:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CyDPz-0006Jh-4c
	for mmusic@megatron.ietf.org; Mon, 07 Feb 2005 13:15:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25805
	for <mmusic@ietf.org>; Mon, 7 Feb 2005 13:15:23 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyDjP-0007Ei-E3
	for mmusic@ietf.org; Mon, 07 Feb 2005 13:35:32 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j17IEWW03167; Mon, 7 Feb 2005 13:14:32 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <1J5A3JJK>; Mon, 7 Feb 2005 13:14:33 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF0174B85D@zrc2hxm0.corp.nortel.com>
From: "Francois Audet" <audet@nortel.com>
To: "'Colin Perkins'" <csp@csperkins.org>,
        "'Francois Audet'"
	<audet@nortelnetworks.com>
Subject: RE: [MMUSIC] WGLC: draft-ietf-mmusic-sdp-new-23.txt
Date: Mon, 7 Feb 2005 13:14:24 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 202a3ece0492a8c7e7c8672d5214398f
Cc: "'Joerg Ott'" <jo@tzi.uni-bremen.de>,
        "'mmusic@ietf.org'" <mmusic@ietf.org>,
        "'Christer Holmberg \(JO/LMF\)'" <christer.holmberg@ericsson.com>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1128061806=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9

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

--===============1128061806==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C50D40.DB3F9982"

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

------_=_NextPart_001_01C50D40.DB3F9982
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Correct.

> -----Original Message-----
> From: Colin Perkins [mailto:csp@csperkins.org]=20
> Sent: Sunday, February 06, 2005 09:06
> To: Francois Audet
> Cc: 'Christer Holmberg (JO/LMF)'; 'Joerg Ott'; 'mmusic@ietf.org'
> Subject: Re: [MMUSIC] WGLC: draft-ietf-mmusic-sdp-new-23.txt
>=20
>=20
> Christer, Francois,
>=20
> My reading of this discussion is that there is no change needed to=20
> SDP-new.
> Colin
>=20
>=20
> On 22 Dec 2004, at 19:16, Francois Audet wrote:
> > > Hi,
> > >
> > > I have a small question.
> > >
> > > The sdp-new draft says that "inactive" is used to put=20
> users on hold,=20
> > > while RFC3264(offer/answer) says that "sendonly" is used.
> > >
> > > Now, in the original SDP RFC, which RFC3246 refers to, "inactive" =

> > > was not defined, so I wonder if RFC3264 is to be updated?
> > >
> > > Or, are both hold mechanisms "according to the standard"?
> >
> > Yes.
> >
> > They are slighly different forms of "hold".
> >
> > SIP/SDP doesn't really have a concept of "hold" in the traditional
> > telephony
> > sense.
> >
> >  sendonly means that you can not receive media.
> >
> > inactive means that you can not receive media and that you are not
> > sending
> > either.
> >
> > They could both mean that you are "on hold". You can think=20
> of a Music
> > On Hold
> > service,=A0 versus a normal Hold service. But neither=20
> necessarily means=20
> > "hold" as per
> > traditional telephony. You could send inactive or sendonly=20
> for reasons=20
> > that are
> > not a logical hold, but just plain media pausing.
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mmusic
>=20
>=20
>=20

------_=_NextPart_001_01C50D40.DB3F9982
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: [MMUSIC] WGLC: draft-ietf-mmusic-sdp-new-23.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Correct.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Colin Perkins [<A =
HREF=3D"mailto:csp@csperkins.org">mailto:csp@csperkins.org</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Sunday, February 06, 2005 09:06</FONT>
<BR><FONT SIZE=3D2>&gt; To: Francois Audet</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: 'Christer Holmberg (JO/LMF)'; 'Joerg Ott'; =
'mmusic@ietf.org'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [MMUSIC] WGLC: =
draft-ietf-mmusic-sdp-new-23.txt</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Christer, Francois,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; My reading of this discussion is that there is =
no change needed to </FONT>
<BR><FONT SIZE=3D2>&gt; SDP-new.</FONT>
<BR><FONT SIZE=3D2>&gt; Colin</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; On 22 Dec 2004, at 19:16, Francois Audet =
wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Hi,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; I have a small question.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; The sdp-new draft says that =
&quot;inactive&quot; is used to put </FONT>
<BR><FONT SIZE=3D2>&gt; users on hold, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; while RFC3264(offer/answer) says that =
&quot;sendonly&quot; is used.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Now, in the original SDP RFC, which =
RFC3246 refers to, &quot;inactive&quot; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; was not defined, so I wonder if =
RFC3264 is to be updated?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Or, are both hold mechanisms =
&quot;according to the standard&quot;?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Yes.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; They are slighly different forms of =
&quot;hold&quot;.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; SIP/SDP doesn't really have a concept of =
&quot;hold&quot; in the traditional</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; telephony</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; sense.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; sendonly means that you can not =
receive media.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; inactive means that you can not receive =
media and that you are not</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; sending</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; either.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; They could both mean that you are &quot;on =
hold&quot;. You can think </FONT>
<BR><FONT SIZE=3D2>&gt; of a Music</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; On Hold</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; service,=A0 versus a normal Hold service. =
But neither </FONT>
<BR><FONT SIZE=3D2>&gt; necessarily means </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &quot;hold&quot; as per</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; traditional telephony. You could send =
inactive or sendonly </FONT>
<BR><FONT SIZE=3D2>&gt; for reasons </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that are</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; not a logical hold, but just plain media =
pausing.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; mmusic mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; mmusic@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/mmusic" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/mmusic</A></FON=
T>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C50D40.DB3F9982--


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

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

--===============1128061806==--



From mmusic-bounces@ietf.org  Mon Feb  7 13:59:41 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00329
	for <mmusic-web-archive@ietf.org>; Mon, 7 Feb 2005 13:59:41 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CyEQG-0008FK-U8
	for mmusic-web-archive@ietf.org; Mon, 07 Feb 2005 14:19:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CyE3N-0005Lh-AX; Mon, 07 Feb 2005 13:56:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CyDzJ-0004c0-JI
	for mmusic@megatron.ietf.org; Mon, 07 Feb 2005 13:52:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29539
	for <mmusic@ietf.org>; Mon, 7 Feb 2005 13:51:53 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyEId-00084v-Uv
	for mmusic@ietf.org; Mon, 07 Feb 2005 14:12:01 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j17IouW09911; Mon, 7 Feb 2005 13:50:56 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <1J5A3MDW>; Mon, 7 Feb 2005 13:50:54 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF0174B8C7@zrc2hxm0.corp.nortel.com>
From: "Francois Audet" <audet@nortel.com>
To: "'Colin Perkins'" <csp@csperkins.org>
Subject: RE: [MMUSIC] WGLC: draft-ietf-mmusic-sdp-new-23.txt
Date: Mon, 7 Feb 2005 13:50:43 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 83e9494d829b08cc3f644ef6ac1b9bd4
Cc: "'Cullen Jennings'" <fluffy@cisco.com>,
        "'mmusic@ietf.org'" <mmusic@ietf.org>,
        "'M.Handley@cs.ucl.ac.uk'" <M.Handley@cs.ucl.ac.uk>,
        "'Joerg Ott'" <jo@tzi.uni-bremen.de>,
        "'van@packetdesign.com'" <van@packetdesign.com>,
        "'Stephen Casner'" <casner@acm.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0381094286=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 025f8c5000216988bfe31585db759250

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

--===============0381094286==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C50D45.EE0606F8"

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

------_=_NextPart_001_01C50D45.EE0606F8
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Here is the exact proposal. Changes starts at line with the "->".

In the definition of <port>, add the following text to the fist =
paragraph,
after the reference to [21]:

	If non-contiguous ports are used or if they don't follow the parity=20
	rule of even RTP ports and odd RTCP ports, the "a=3Drtcp:" attribute=20
      MUST be used. Applications that are requested to send media to a
<port>=20
	that is odd and where the "a=3Drtcp:" is present MUST NOT substract 1=20
	to the RTP port: i.e, they MUST send the RTP to the port indicated=20
	in <port> and send the RTCP to the port indicated in the "a=3Drtcp"=20
	attribute.
    =20
Cheers.
=20

> -----Original Message-----
> From: Colin Perkins [mailto:csp@csperkins.org]=20
> Sent: Sunday, February 06, 2005 09:05
> To: Francois Audet
> Cc: 'M.Handley@cs.ucl.ac.uk'; 'Cullen Jennings'; 'Joerg Ott';=20
> 'van@packetdesign.com'; 'Stephen Casner'; 'mmusic@ietf.org'
> Subject: Re: [MMUSIC] WGLC: draft-ietf-mmusic-sdp-new-23.txt
>=20
>=20
> Francois,
>=20
> [Apologies for the slow response...]
>=20
> On 20 Dec 2004, at 00:33, Francois Audet wrote:
> > I would like to request a clarification in section 5.14 of =20
> > draft-ietf-mmusic-sdp-new-23.
> >
> > As we discovered in BEHAVE, certain SDP implementations are
> > misinterpretting RFC 3550 section 11 2nd paragraph. In a SIP=20
> > Offer/Answer for example, these implementations=20
> unilaterally change an=20
> > odd RTP port indicated in an SDP (from the other end) with=20
> to the even=20
> > port that one lower. In other words, if the other end=20
> indicates an RTP=20
> > port of 5201, these implemenations will send RTP to 5200,=20
> which will=20
> > be a big problem.
> >
> > Note that this issue is slightly orthogonal to the use of the rtcp
> > attribute of RFC 3605. For example, if an application=20
> discovers (with=20
> > STUN or ICE) that its RTP port is 5201, it may then=20
> discover that it's=20
> > RTCP port is 5202 (which would satisfy the contiguity=20
> rule). This is=20
> > very likely to happen because NATs typically assign ports=20
> > sequentially. An application could (somewhat foolishlingly) not use =

> > RFC 3605 in this case because it follows the contiguity=20
> rule (but not=20
> > the parity rule).
> >
> > Another issue is for implementations that do not support RTCP in =
the
> > first place.
> >
> > In order to avoid these problems, I propose that we explicitly =
state
> > that  the <port> for RTP indicates the actual port and MUST not be=20
> > changed regardless of parity (i.e., DO NOT substract 1 if=20
> it is odd).
> >
> > I believe that would finally put to rest this parity issue=20
> for all SDP
> > based protocols.
>=20
> What is the *exact* wording change you are proposing?
>=20
> > Also, on a similar note, would it make sense to incorporate RFC =
3605
> > (the=A0 directly into sdp-new, instead of having it stand as=20
> a separate=20
> > RFC) and make its support mandatory? The biggest problem=20
> with RFC 3605=20
> > is that I can do the best SIP/SDP implementation possible, support=20
> > STUN, ICE, 3605 and all, but if the other end doesn't support 3605=20
> > (because they don't even know of NATs), the problem above=20
> will still=20
> > occur.
>=20
> We don't mandate support for any of the attributes in SDP-new, so I=20
> don't see any real benefit to including the RFC 3605 ("a=3Drtcp:")=20
> attribute into the main SDP specification at this time.
>=20
> Colin
>=20
>=20

------_=_NextPart_001_01C50D45.EE0606F8
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: [MMUSIC] WGLC: draft-ietf-mmusic-sdp-new-23.txt</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>Here is the exact proposal. Changes starts at line =
with the &quot;-&gt;&quot;.</FONT>
</P>

<P><FONT SIZE=3D2>In the definition of &lt;port&gt;, add the following =
text to the fist paragraph,</FONT>
<BR><FONT SIZE=3D2>after the reference to [21]:</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>If =
non-contiguous ports are used or if they don't follow the parity =
</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>rule of =
even RTP ports and odd RTCP ports, the &quot;a=3Drtcp:&quot; attribute =
</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MUST be used. =
Applications that are requested to send media to a &lt;port&gt; </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>that is =
odd and where the &quot;a=3Drtcp:&quot; is present MUST NOT substract 1 =
</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>to the =
RTP port: i.e, they MUST send the RTP to the port indicated </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>in =
&lt;port&gt; and send the RTCP to the port indicated in the =
&quot;a=3Drtcp&quot; </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>attribute.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=3D2>Cheers.</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Colin Perkins [<A =
HREF=3D"mailto:csp@csperkins.org">mailto:csp@csperkins.org</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Sunday, February 06, 2005 09:05</FONT>
<BR><FONT SIZE=3D2>&gt; To: Francois Audet</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: 'M.Handley@cs.ucl.ac.uk'; 'Cullen =
Jennings'; 'Joerg Ott'; </FONT>
<BR><FONT SIZE=3D2>&gt; 'van@packetdesign.com'; 'Stephen Casner'; =
'mmusic@ietf.org'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [MMUSIC] WGLC: =
draft-ietf-mmusic-sdp-new-23.txt</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Francois,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; [Apologies for the slow response...]</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; On 20 Dec 2004, at 00:33, Francois Audet =
wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I would like to request a clarification in =
section 5.14 of&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; draft-ietf-mmusic-sdp-new-23.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; As we discovered in BEHAVE, certain SDP =
implementations are</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; misinterpretting RFC 3550 section 11 2nd =
paragraph. In a SIP </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Offer/Answer for example, these =
implementations </FONT>
<BR><FONT SIZE=3D2>&gt; unilaterally change an </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; odd RTP port indicated in an SDP (from the =
other end) with </FONT>
<BR><FONT SIZE=3D2>&gt; to the even </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; port that one lower. In other words, if =
the other end </FONT>
<BR><FONT SIZE=3D2>&gt; indicates an RTP </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; port of 5201, these implemenations will =
send RTP to 5200, </FONT>
<BR><FONT SIZE=3D2>&gt; which will </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; be a big problem.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Note that this issue is slightly =
orthogonal to the use of the rtcp</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; attribute of RFC 3605. For example, if an =
application </FONT>
<BR><FONT SIZE=3D2>&gt; discovers (with </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; STUN or ICE) that its RTP port is 5201, it =
may then </FONT>
<BR><FONT SIZE=3D2>&gt; discover that it's </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; RTCP port is 5202 (which would satisfy the =
contiguity </FONT>
<BR><FONT SIZE=3D2>&gt; rule). This is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; very likely to happen because NATs =
typically assign ports </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; sequentially. An application could =
(somewhat foolishlingly) not use </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; RFC 3605 in this case because it follows =
the contiguity </FONT>
<BR><FONT SIZE=3D2>&gt; rule (but not </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the parity rule).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Another issue is for implementations that =
do not support RTCP in the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; first place.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; In order to avoid these problems, I =
propose that we explicitly state</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that&nbsp; the &lt;port&gt; for RTP =
indicates the actual port and MUST not be </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; changed regardless of parity (i.e., DO NOT =
substract 1 if </FONT>
<BR><FONT SIZE=3D2>&gt; it is odd).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I believe that would finally put to rest =
this parity issue </FONT>
<BR><FONT SIZE=3D2>&gt; for all SDP</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; based protocols.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; What is the *exact* wording change you are =
proposing?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Also, on a similar note, would it make =
sense to incorporate RFC 3605</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; (the=A0 directly into sdp-new, instead of =
having it stand as </FONT>
<BR><FONT SIZE=3D2>&gt; a separate </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; RFC) and make its support mandatory? The =
biggest problem </FONT>
<BR><FONT SIZE=3D2>&gt; with RFC 3605 </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; is that I can do the best SIP/SDP =
implementation possible, support </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; STUN, ICE, 3605 and all, but if the other =
end doesn't support 3605 </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; (because they don't even know of NATs), =
the problem above </FONT>
<BR><FONT SIZE=3D2>&gt; will still </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; occur.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; We don't mandate support for any of the =
attributes in SDP-new, so I </FONT>
<BR><FONT SIZE=3D2>&gt; don't see any real benefit to including the RFC =
3605 (&quot;a=3Drtcp:&quot;) </FONT>
<BR><FONT SIZE=3D2>&gt; attribute into the main SDP specification at =
this time.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Colin</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C50D45.EE0606F8--


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

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

--===============0381094286==--



From mmusic-bounces@ietf.org  Tue Feb  8 16:31:36 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26158
	for <mmusic-web-archive@ietf.org>; Tue, 8 Feb 2005 16:31:36 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CydH4-0001GY-J7
	for mmusic-web-archive@ietf.org; Tue, 08 Feb 2005 16:51:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CycAt-0006CT-QH; Tue, 08 Feb 2005 15:41:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cyc75-0003gD-GJ; Tue, 08 Feb 2005 15:37:36 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14914;
	Tue, 8 Feb 2005 15:37:33 -0500 (EST)
Message-Id: <200502082037.PAA14914@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 08 Feb 2005 15:37:33 -0500
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-kmgmt-ext-13.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

	Title		: Key Management Extensions for Session Description
			  Protocol (SDP) and Real Time Streaming Protocol (RTSP)
	Author(s)	: J. Arkko, et al.
	Filename	: draft-ietf-mmusic-kmgmt-ext-13.txt
	Pages		: 27
	Date		: 2005-2-8
	
This document defines general extensions for SDP and RTSP to carry
messages, as specified by a key management protocol, in order to
secure the media. These extensions are presented as a framework, to
be used by one or more key management protocols. As such, their use
is meaningful only when complemented by an appropriate key management
protocol.

General guidelines are also given on how the framework should be used
together with SIP and RTSP. The usage with the MIKEY key management
protocol is also defined.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-kmgmt-ext-13.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-mmusic-kmgmt-ext-13.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-mmusic-kmgmt-ext-13.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: <2005-2-8160433.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-kmgmt-ext-13.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-mmusic-kmgmt-ext-13.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

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

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

--NextPart--





From mmusic-bounces@ietf.org  Wed Feb  9 10:49:31 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12226
	for <mmusic-web-archive@ietf.org>; Wed, 9 Feb 2005 10:49:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CyuPi-0001sK-1p
	for mmusic-web-archive@ietf.org; Wed, 09 Feb 2005 11:10:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cyu43-0005By-Of; Wed, 09 Feb 2005 10:47:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CyeGC-0002hD-L5; Tue, 08 Feb 2005 17:55:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11858;
	Tue, 8 Feb 2005 17:55:06 -0500 (EST)
Received: from magus.nostrum.com ([69.5.195.2] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CyeZr-0006EA-EY; Tue, 08 Feb 2005 18:15:29 -0500
Received: from [127.0.0.1] (adam@magus.nostrum.com [10.10.10.2])
	(authenticated bits=0)
	by magus.nostrum.com (8.12.11/8.12.11) with ESMTP id j18MspIj038836
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 8 Feb 2005 16:54:58 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <4209433A.2000005@nostrum.com>
Date: Tue, 08 Feb 2005 16:54:50 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: XCON-IETF <xcon@ietf.org>
X-Enigmail-Version: 0.89.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 09 Feb 2005 10:47:37 -0500
Cc: mmusic@ietf.org
Subject: [MMUSIC] BFCP: SDP usage and k=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: XCON-IETF <xcon@ietf.org>
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: 7bit

[as XCON chair]

I am copying the MMUSIC mailing list on this message, since I believe 
there may be individuals in MMUSIC who are willing and able to assist in 
a decision that the XCON working group must make. Fundamentally, though, 
I believe this is an XCON issue, so I believe any ensuing discussion 
should take place on the XCON mailing list.

Currently, the SDP document for BFCP (draft-ietf-mmusic-sdp-bfcp-00.txt) 
talks about using the k= line for calculation of DIGEST TLV values.

During review of sdp-new (not sdp-ng -- but the 2327bis document), the 
IESG commented that the use of k= for key exchange is not a sufficient 
solution for key exchange; the resultant change to the SDP document is 
as follows:

>   If transported over a secure and trusted channel, the session
>   description protocol MAY be used to convey encryption keys.  A simple
>   mechanism for key exchange is provided by the key field ("k=")
>   although this is primarily supported for compatibility with older
>   implementations and its use is NOT RECOMMENDED.  Work is in progress
>   to define new key exchange mechanisms for use with SDP [26][27] and
>   it is expected that new applications will use those mechanisms.
>  
>

Given this NOT RECOMMENDED strength provision, XCON needs to consider 
whether we continue to use the k= field as described, or if we need to 
instead use draft-ietf-mmusic-kmgmt-ext (which is just about to be ready 
for IESG review) or some similar mechanism.

If we decide to continue to use k=, then the BFCP SDP document needs to 
justify that decision. Questions to answer include:

    * Why is the k= mechanism sufficient for floor control despite its
      use being NOT RECOMMENDED?

    * In what ways does floor control or our usage of the k= line differ
      from other media that we have grounds for contravening the
      recommendations of sdp-new?

    * Are there specific reasons that the draft-ietf-mmusic-kmgmt-ext is
      not appropriate for BFCP?


One notable difference is that BFCP does not use this key to encrypt the 
actual floor control; it uses it for shared secret exchange for the 
purposes of digest authentication. It may well be that using k= for this 
purpose (that is, keys used for purposes other than stream encryption) 
is sufficiently outside the traditional meaning of k= that we should 
instead choose (e.g.) an a= attribute for digest key exchange.

Follow ups to the XCON working group only, please.

/a

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


From mmusic-bounces@ietf.org  Wed Feb  9 10:53:31 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12608
	for <mmusic-web-archive@ietf.org>; Wed, 9 Feb 2005 10:53:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CyuTb-0001yA-A5
	for mmusic-web-archive@ietf.org; Wed, 09 Feb 2005 11:14:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cyu44-0005CD-8x; Wed, 09 Feb 2005 10:47:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CytmV-000124-Dv
	for mmusic@megatron.ietf.org; Wed, 09 Feb 2005 10:29:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10657
	for <mmusic@ietf.org>; Wed, 9 Feb 2005 10:29:29 -0500 (EST)
Received: from mx2.scansoft.com ([198.71.64.82])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cyu6L-0001QP-26
	for mmusic@ietf.org; Wed, 09 Feb 2005 10:50:01 -0500
Received: from pb-exchcon.pb.scansoft.com ([10.1.4.73]) by mx2.scansoft.com
	with InterScan Messaging Security Suite;
	Wed, 09 Feb 2005 10:32:22 -0500
Received: by pb-exchcon.pb.scansoft.com with Internet Mail Service
	(5.5.2653.19) id <DSP9CYXF>; Wed, 9 Feb 2005 10:28:46 -0500
Message-ID: <BBF29C9B95E52E4DB5C29A0ACC94E83B016A9D7A@ac-exch1.eu.scansoft.com>
From: "Reifenrath, Klaus" <Klaus.Reifenrath@Scansoft.com>
To: "'M.Handley@cs.ucl.ac.uk'" <M.Handley@cs.ucl.ac.uk>,
        "'van@packetdesign.com'" <van@packetdesign.com>,
        "'csp@csperkins.org'"
	<csp@csperkins.org>
Date: Wed, 9 Feb 2005 10:28:46 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3fbd9b434023f8abfcb1532abaec7a21
X-Mailman-Approved-At: Wed, 09 Feb 2005 10:47:37 -0500
Cc: "'mmusic@ietf.org'" <mmusic@ietf.org>
Subject: [MMUSIC] FW: [Speechsc] IANA considerations for group feedback
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48

Hi mmusic WG!

For MRCPv2 the speechsc WG likes to use the media type "control" and
believes to have a good use case for it.  
>From my understanding of
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-new-23.txt we do
not need to register "control", but would still need to have an IANA section
on this in our spec. What do you think?

Thanks,
Klaus

 
-----Original Message-----
From: Dan Burnett [mailto:dan_burnett2000@yahoo.com]
Sent: Mittwoch, 9. Februar 2005 16:02
To: David R Oran; Sarvi Shanmugham
Cc: 'ThomasGal@LumenVox.com'; speechsc@ietf.org; Reifenrath, Klaus
Subject: Re: [Speechsc] IANA considerations for group feedback


Just to be clear, there are no IANA considerations
here, right?  The "control" type exists and we do not
need to request any sort of registration because of
our documented use, right?

--- David R Oran <oran@cisco.com> wrote:

> 
> On Jan 27, 2005, at 12:57 PM, Sarvi Shanmugham
> wrote:
> 
> >  Which is exactly what is being done here.
> >
> >  So we are fine.
> >
> Yes, I agree this is fine.
> 
> >  Sarvi
> >  Reifenrath, Klaus wrote:
> > Quoting from
> > 
>
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-new-23.txt:
> >    Note: The media types "control" and "data" were
> listed as valid in
> >    the previous version of this specification [6],
> however their
> >    semantics were never fully specified and they
> are not widely used.
> >    These media types have been removed in this
> specification, although
> >    they still remain valid media type capabilities
> for a SIP user agent
> >    as defined in RFC 3840 [23].  If these media
> types are considered
> >    useful in future, a Standards Track RFC MUST be
> produced to document
> >    their use.  Until that is done, applications
> SHOULD NOT use these
> >    types and SHOULD NOT declare support for them
> in SIP capabilities
> >    declarations (even though they exist in the
> registry created by RFC
> >    3840).
> >
> > -----Original Message-----
> > From: Thomas Gal [ mailto:ThomasGal@LumenVox.com ]
> > Sent: Mittwoch, 26. Januar 2005 20:48
> > To: 'Dan Burnett'; 'Reifenrath, Klaus'
> > Cc: speechsc@ietf.org
> > Subject: RE: [Speechsc] IANA considerations for
> group feedback
> >
> >
> >  inlinemmusic@ietf.org
> >
> > -Tom
> >
> >  thomasgal@lumenvox.com
> >
> >
> > -----Original Message-----
> > From: speechsc-bounces@ietf.org
> > [ mailto:speechsc-bounces@ietf.org ] On Behalf Of
> Dan Burnett
> > Sent: Wednesday, January 26, 2005 10:15 AM
> > To: Reifenrath, Klaus
> > Cc: speechsc@ietf.org
> > Subject: RE: [Speechsc] IANA considerations for
> group feedback
> >
> > I agree that there needs to be an registration of
> > application/x-nlsml (or, as an email from Tom
> pointed out,
> > application/nlsml).  Technically it should be in a
> separate
> > RFC from MRCP, but I can include it in the draft
> if there are
> > no objections.
> >
> >
> > I would certainly agree with not using
> "application/nlsml" but 
> > something
> > similar to obviate confusion, even mrcp-nlsml or
> something.
> >
> >
> > If "control" is already registered, do we need to
> do it?  In
> > short, it's not clear to me in which
> > namespace(s) the SDP items you mention should be
> registered.
> > Are they new namespaces for MRCP or are there
> existing
> > namespaces to which the items should be added?
> >
> >
> > Isn't MRCPv2 "control"? I would guess control is
> too ambiguous and 
> > probably
> > why it's being deprecated.
> >
> > -Tom
> >
> > _______________________________________________
> > Speechsc mailing list
> >  Speechsc@ietf.org
> >  https://www1.ietf.org/mailman/listinfo/speechsc
> >
> >
> >
> >  _______________________________________________
> > Speechsc mailing list
> > Speechsc@ietf.org
> > https://www1.ietf.org/mailman/listinfo/speechsc
> >
> David R. Oran
> Cisco Fellow
> Cisco Systems
> 7 Ladyslipper Lane
> Acton, MA 01720 USA
> Tel: +1 978 264 2048
> Email: oran@cisco.com
> 
> _______________________________________________
> Speechsc mailing list
> Speechsc@ietf.org
> https://www1.ietf.org/mailman/listinfo/speechsc
> 



		
__________________________________ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.com 
 

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


From mmusic-bounces@ietf.org  Wed Feb  9 11:32:29 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15169
	for <mmusic-web-archive@ietf.org>; Wed, 9 Feb 2005 11:32:29 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cyv5K-0002mV-6t
	for mmusic-web-archive@ietf.org; Wed, 09 Feb 2005 11:53:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CyuiI-0006Jw-S4; Wed, 09 Feb 2005 11:29:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cyudv-0005nW-2M; Wed, 09 Feb 2005 11:24:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14711;
	Wed, 9 Feb 2005 11:24:40 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cyuxj-0002c3-Vv; Wed, 09 Feb 2005 11:45:13 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 09 Feb 2005 09:35:54 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.88,190,1102291200"; 
	d="scan'208"; a="224752964:sNHT23372132"
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j19GO7uC020510;
	Wed, 9 Feb 2005 08:24:08 -0800 (PST)
Received: from [192.168.0.10] (sjc-vpn6-276.cisco.com [10.21.121.20])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j19GJO7R015370;
	Wed, 9 Feb 2005 08:19:24 -0800
In-Reply-To: <4209433A.2000005@nostrum.com>
References: <4209433A.2000005@nostrum.com>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <3d298d2cf5c4d747f4326f93220e2b63@cisco.com>
Content-Transfer-Encoding: 7bit
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [MMUSIC] BFCP: SDP usage and k=
Date: Wed, 9 Feb 2005 08:24:03 -0800
To: XCON-IETF <xcon@ietf.org>
X-Mailer: Apple Mail (2.619.2)
IIM-SIG: v:"1.1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1107965964.853025"; x:"432200"; a:"rsa-sha1"; b:"nofws:2768";
	e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2p"
	"XIweAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRUtW+c43sl9jC"
	"50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"hLyzCcFn16dy8DTOzMIj7EccseAOdEhsa6Rv9xCT2hTI03Ep0BINM4kqSzScCNZbjLDA9ihB"
	"ZqEcym7Pa+9lHRdIUFL0Rm3KVJiIgGTNIfMCaYsGF2onamHScqgdZIzPtitYQgYE4gWabjg3cQF"
	"yBkTHUh60bD3Xgr1wZZimXIc=";
	c:"From: Mark Baugher <mbaugher@cisco.com>";
	c:"Subject: Re: [MMUSIC] BFCP: SDP usage and k=3D";
	c:"Date: Wed, 9 Feb 2005 08:24:03 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Content-Transfer-Encoding: 7bit
Cc: mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Content-Transfer-Encoding: 7bit


On Feb 8, 2005, at 2:54 PM, Adam Roach wrote:

> [as XCON chair]
>
> I am copying the MMUSIC mailing list on this message, since I believe 
> there may be individuals in MMUSIC who are willing and able to assist 
> in a decision that the XCON working group must make. Fundamentally, 
> though, I believe this is an XCON issue, so I believe any ensuing 
> discussion should take place on the XCON mailing list.
>
> Currently, the SDP document for BFCP 
> (draft-ietf-mmusic-sdp-bfcp-00.txt) talks about using the k= line for 
> calculation of DIGEST TLV values.

I glanced at the usage of k= in this I-D, which says that it encodes a 
shared secret.  But where does it specify what kind of shared secret?  
What algorithm is used for computing the digest?  I did not study the 
draft and may be missing something.  If it is completely specified then 
it avoids the general problem that we found with k= in the past, namely 
that there is no way to identify the transform to be used and pass 
additional cryptographic and session parameters that practically always 
need to be communicated with a cryptographic key.  If 
draft-ietf-mmusic-sdp-bfcp-00.txt does not have these problems and k= 
signals all needed information, then there may be no problem.

Mark
>
> During review of sdp-new (not sdp-ng -- but the 2327bis document), the 
> IESG commented that the use of k= for key exchange is not a sufficient 
> solution for key exchange; the resultant change to the SDP document is 
> as follows:
>
>>   If transported over a secure and trusted channel, the session
>>   description protocol MAY be used to convey encryption keys.  A 
>> simple
>>   mechanism for key exchange is provided by the key field ("k=")
>>   although this is primarily supported for compatibility with older
>>   implementations and its use is NOT RECOMMENDED.  Work is in progress
>>   to define new key exchange mechanisms for use with SDP [26][27] and
>>   it is expected that new applications will use those mechanisms.
>>
>
> Given this NOT RECOMMENDED strength provision, XCON needs to consider 
> whether we continue to use the k= field as described, or if we need to 
> instead use draft-ietf-mmusic-kmgmt-ext (which is just about to be 
> ready for IESG review) or some similar mechanism.
>
> If we decide to continue to use k=, then the BFCP SDP document needs 
> to justify that decision. Questions to answer include:
>
>    * Why is the k= mechanism sufficient for floor control despite its
>      use being NOT RECOMMENDED?
>
>    * In what ways does floor control or our usage of the k= line differ
>      from other media that we have grounds for contravening the
>      recommendations of sdp-new?
>
>    * Are there specific reasons that the draft-ietf-mmusic-kmgmt-ext is
>      not appropriate for BFCP?
>
>
> One notable difference is that BFCP does not use this key to encrypt 
> the actual floor control; it uses it for shared secret exchange for 
> the purposes of digest authentication. It may well be that using k= 
> for this purpose (that is, keys used for purposes other than stream 
> encryption) is sufficiently outside the traditional meaning of k= that 
> we should instead choose (e.g.) an a= attribute for digest key 
> exchange.
>
> Follow ups to the XCON working group only, please.
>
> /a
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
>

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


From mmusic-bounces@ietf.org  Wed Feb  9 15:41:12 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12113
	for <mmusic-web-archive@ietf.org>; Wed, 9 Feb 2005 15:41:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cyyy1-00028o-MX
	for mmusic-web-archive@ietf.org; Wed, 09 Feb 2005 16:01:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CyySX-0003Li-NR; Wed, 09 Feb 2005 15:29:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CyyOh-0000e9-Gw
	for mmusic@megatron.ietf.org; Wed, 09 Feb 2005 15:25:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09715
	for <mmusic@ietf.org>; Wed, 9 Feb 2005 15:25:13 -0500 (EST)
Received: from crufty.research.bell-labs.com ([204.178.16.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyyiY-0001N1-Hx
	for mmusic@ietf.org; Wed, 09 Feb 2005 15:45:47 -0500
Received: from scummy.research.bell-labs.com
	(H-135-104-2-10.research.bell-labs.com [135.104.2.10])
	by crufty.research.bell-labs.com (8.12.10/8.12.10) with ESMTP id
	j19KPD1O039890
	for <mmusic@ietf.org>; Wed, 9 Feb 2005 15:25:13 -0500 (EST)
Received: from bronx.dnrc.bell-labs.com (bronx.dnrc.bell-labs.com
	[135.180.160.8])
	by scummy.research.bell-labs.com (8.12.9/8.12.9) with ESMTP id
	j19KP77d021089
	for <mmusic@ietf.org>; Wed, 9 Feb 2005 15:25:07 -0500 (EST)
Received: from [135.180.180.121] (romana-1 [135.180.180.121])
	by bronx.dnrc.bell-labs.com (8.12.9/8.12.9) with ESMTP id
	j19KP7oC020446
	for <mmusic@ietf.org>; Wed, 9 Feb 2005 15:25:07 -0500 (EST)
Message-ID: <420A71A7.2050903@lucent.com>
Date: Wed, 09 Feb 2005 15:25:11 -0500
From: Bob Gaglianello <rdg@lucent.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.5) Gecko/20041217
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mmusic@ietf.org
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by
	crufty.research.bell-labs.com id j19KPD1O039890
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: quoted-printable
Subject: [MMUSIC] Distributing "requests" to call/conference participants
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: quoted-printable

Hello,

I am looking for guidance as to what is an =93appropriate=94 or =93accept=
able=94=20
mechanism for signaling all the SIP clients within a call/conference to=20
=93start-up=94 an additional conferencing application such as a shared=20
presentation tool or a shared Web Browser. I assume all clients have the=20
ability to execute the app and have a copy to execute on their local=20
machine. I need some way of distributing a message like: =93Start up=20
conferencing application XYZ=94. This needs to work for two parties in a=20
point-to-point call as well as a multiple parties connected through a=20
conference bridge.

I would greatly appreciate any help and thoughts on this.

Cheers,
Bobg


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


From mmusic-bounces@ietf.org  Wed Feb  9 16:27:41 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24698
	for <mmusic-web-archive@ietf.org>; Wed, 9 Feb 2005 16:27:41 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cyzh2-0006Cr-2d
	for mmusic-web-archive@ietf.org; Wed, 09 Feb 2005 16:48:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cyyoj-0001ho-Gm; Wed, 09 Feb 2005 15:52:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CyyUs-0004nX-IL; Wed, 09 Feb 2005 15:31:38 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10434;
	Wed, 9 Feb 2005 15:31:36 -0500 (EST)
Message-Id: <200502092031.PAA10434@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 09 Feb 2005 15:31:36 -0500
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-rtsp-announce-01.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

	Title		: RTSP Announce Method
	Author(s)	: T. Zeng, G. Sherwood
	Filename	: draft-ietf-mmusic-rtsp-announce-01.txt
	Pages		: 0
	Date		: 2005-2-9
	
This memo describes an extension RTSP request, ANNOUNCE, which 
   extends the core RTSP protocol [RTSP_NEW] to allow one end to 
   push to the other end various types of information by RTSP
   means.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-rtsp-announce-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-mmusic-rtsp-announce-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-mmusic-rtsp-announce-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: <2005-2-9150429.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-rtsp-announce-01.txt

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

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


--OtherAccess--

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

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

--NextPart--





From mmusic-bounces@ietf.org  Thu Feb 10 11:55:17 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16115
	for <mmusic-web-archive@ietf.org>; Thu, 10 Feb 2005 11:55:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CzHv8-0008Nr-Lc
	for mmusic-web-archive@ietf.org; Thu, 10 Feb 2005 12:16:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CzHVX-00008g-H5; Thu, 10 Feb 2005 11:49:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CzHPy-0006tx-2J
	for mmusic@megatron.ietf.org; Thu, 10 Feb 2005 11:43:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15170
	for <mmusic@ietf.org>; Thu, 10 Feb 2005 11:43:47 -0500 (EST)
Received: from vs.informatik.uni-ulm.de ([134.60.77.243])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzHk1-000841-3r
	for mmusic@ietf.org; Thu, 10 Feb 2005 12:04:33 -0500
Received: from localhost (sikanda [127.0.0.1])
	by vs.informatik.uni-ulm.de (Postfix) with ESMTP id CF0713E4318
	for <mmusic@ietf.org>; Thu, 10 Feb 2005 17:43:18 +0100 (CET)
Received: from vs.informatik.uni-ulm.de ([127.0.0.1])
	by localhost (sikanda [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 23748-04 for <mmusic@ietf.org>;
	Thu, 10 Feb 2005 17:43:16 +0100 (CET)
Received: from vs.informatik.uni-ulm.de (discovery.informatik.uni-ulm.de
	[134.60.77.113])
	by vs.informatik.uni-ulm.de (Postfix) with ESMTP id 5FFCC3E4317
	for <mmusic@ietf.org>; Thu, 10 Feb 2005 17:43:16 +0100 (CET)
Message-ID: <420B90AD.3030506@vs.informatik.uni-ulm.de>
Date: Thu, 10 Feb 2005 17:49:49 +0100
From: Teodora Guenkova-Luy <guenkova@vs.informatik.uni-ulm.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, de
MIME-Version: 1.0
To: mmusic@ietf.org
X-Priority: 1 (highest)
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at
	vs.informatik.uni-ulm.de
X-Spam-Score: 1.3 (+)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] "draft-guenkova-mmusic-sdp-ng-streamtrack-00" submitted
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 1.3 (+)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit

Dear MMUSIC Folks

We submitted to IETF the draft "draft-guenkova-mmusic-sdp-ng-streamtrack-00"

The title of this draft is: "Stream Tracking Description for Resource 
Management Guarantees in the Network".

The draft treats the following topic:
"This document defines an extension to the Session Description
Protocol (SDP) and to Session Description Protocol new generation
(SDPng - work in progress). The intention of this draft is to provide
descriptions in SDP and SDPng that specify the source port of media
streams. Such specification within the session description is
required in many network quality of service (QoS) management systems
in order to be able to track the media streams from their source to
their destination. Thus the QoS management system can differentiate
the stream tracks end-to-end and guarantee QoS for every single
media."

Until it appears on the IETF server, you can find our contribution under:
http://www-vs.informatik.uni-ulm.de/proj/qos/drafts/draft-guenkova-mmusic-sdp-ng-streamtrack-00.txt

Best Regards,
Teodora Guenkova-Luy



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


From mmusic-bounces@ietf.org  Thu Feb 10 15:42:40 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05373
	for <mmusic-web-archive@ietf.org>; Thu, 10 Feb 2005 15:42:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CzLTC-00059w-6Z
	for mmusic-web-archive@ietf.org; Thu, 10 Feb 2005 16:03:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CzL21-0003ZO-0y; Thu, 10 Feb 2005 15:35:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CzKzs-0001eJ-6Y
	for mmusic@megatron.ietf.org; Thu, 10 Feb 2005 15:33:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04709
	for <mmusic@ietf.org>; Thu, 10 Feb 2005 15:33:06 -0500 (EST)
Received: from webadmin.keyvoice.com ([12.153.69.6] helo=home.ringle.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzLJu-0004nJ-6H
	for mmusic@ietf.org; Thu, 10 Feb 2005 15:53:53 -0500
Received: by home.ringle.org (Postfix, from userid 501)
	id 5B51DB8702; Thu, 10 Feb 2005 15:31:06 -0500 (EST)
From: Jon Ringle <ml-mmusic@ringle.org>
To: mmusic@ietf.org
Date: Thu, 10 Feb 2005 15:31:05 -0500
User-Agent: KMail/1.5
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200502101531.05593.ml-mmusic@ringle.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Dissecting rtp.version==0 packets as STUN with ethereal
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ml-mmusic@ringle.org
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit

Hello list,

I just wanted to let this list know that I have checked in code to the 
ethereal svn repository that supports dissecting rtp.version==0 packets as 
STUN packets to help analyze ICE implementations. The code was checked in 
after ethereal 0.10.9 was released. From the Ethereal menu go to 
"edit/preferences", then "protocols/RTP", "Treat RTP version 0 packets as 
STUN packet".

Jon

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


From mmusic-bounces@ietf.org  Fri Feb 11 08:51:08 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28450
	for <mmusic-web-archive@ietf.org>; Fri, 11 Feb 2005 08:51:08 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CzbWd-0007FZ-2J
	for mmusic-web-archive@ietf.org; Fri, 11 Feb 2005 09:12:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Czb2F-0007cw-OW; Fri, 11 Feb 2005 08:40:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Czarb-0004ll-PY
	for mmusic@megatron.ietf.org; Fri, 11 Feb 2005 08:29:39 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27152
	for <mmusic@ietf.org>; Fri, 11 Feb 2005 08:29:38 -0500 (EST)
Received: from vs.informatik.uni-ulm.de ([134.60.77.243])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzbBo-0006o5-NN
	for mmusic@ietf.org; Fri, 11 Feb 2005 08:50:34 -0500
Received: from localhost (sikanda [127.0.0.1])
	by vs.informatik.uni-ulm.de (Postfix) with ESMTP id 88E903E4313
	for <mmusic@ietf.org>; Fri, 11 Feb 2005 14:29:07 +0100 (CET)
Received: from vs.informatik.uni-ulm.de ([127.0.0.1])
	by localhost (sikanda [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 32023-05 for <mmusic@ietf.org>;
	Fri, 11 Feb 2005 14:29:03 +0100 (CET)
Received: from vs.informatik.uni-ulm.de (discovery.informatik.uni-ulm.de
	[134.60.77.113])
	by vs.informatik.uni-ulm.de (Postfix) with ESMTP id 429653E430C
	for <mmusic@ietf.org>; Fri, 11 Feb 2005 14:29:03 +0100 (CET)
Message-ID: <420CB4A9.20106@vs.informatik.uni-ulm.de>
Date: Fri, 11 Feb 2005 14:35:37 +0100
From: Teodora Guenkova-Luy <guenkova@vs.informatik.uni-ulm.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, de
MIME-Version: 1.0
To: mmusic@ietf.org
References: <420B90AD.3030506@vs.informatik.uni-ulm.de>
In-Reply-To: <420B90AD.3030506@vs.informatik.uni-ulm.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at
	vs.informatik.uni-ulm.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] "draft-guenkova-mmusic-mpeg21-sdpng-00" submitted
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit

Dear MMUSIC Folks

We submitted to IETF the draft "draft-guenkova-mmusic-mpeg21-sdpng-00"

The title of this draft is: "Harmonization of Session and Capability 
Descriptions between SDPng and MPEG-21 Digital Item Adaptation".

The draft treats the following topic:
"The delivery and the adaptation of multimedia content in distributed,
heterogeneous environments, involving device and/or application
mobility, require flexible control and management mechanisms in the
terminals and/or in media gateways. MPEG-21 Digital Item Adaptation
(DIA) provides normative description formats supporting the
adaptation of so-called Digital Items, but it does not define
interactions with existing transport and control technologies, in
order to remain independent. This draft presents a practical approach
for harmonizing MPEG-21 DIA application with Session Description
Protocol next generation (SDPng). The proposed mechanism allows the
definition of system configurations, performance constraints and
adaptation information within the scope of SDPng using the format of
MPEG-21 DIA. Furthermore, the converged format enables the
integration of session management and negotiation protocols (e.g.
Session Initiation Protocol - SIP) that use such enhanced SDPng
descriptions within an MPEG-21 conformant environment."

Until it appears on the IETF server, you can find our contribution under:
http://www-vs.informatik.uni-ulm.de/proj/qos/drafts/draft-guenkova-mmusic-mpeg21-sdpng-00.txt

Best Regards,
Teodora Guenkova-Luy

-- 
-----------------------------------------
Teodora Guenkova-Luy

Dept. Distributed Systems, University of Ulm, 
Oberer Eselsberg, 89069 Ulm, Germany

Tel.: +49 (0731) 502-4148 
FAX: +49 (0731) 502-4142

e-Mail: guenkova@vs.informatik.uni-ulm.de

Home Page: http://www-vs.informatik.uni-ulm.de/~Guenkova/ 

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



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


From mmusic-bounces@ietf.org  Fri Feb 11 17:14:32 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01393
	for <mmusic-web-archive@ietf.org>; Fri, 11 Feb 2005 17:14:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CzjNt-0000pU-Vj
	for mmusic-web-archive@ietf.org; Fri, 11 Feb 2005 17:35:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Czir9-00040i-Gf; Fri, 11 Feb 2005 17:01:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CziSe-0004l7-51
	for mmusic@megatron.ietf.org; Fri, 11 Feb 2005 16:36:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22765
	for <mmusic@ietf.org>; Fri, 11 Feb 2005 16:36:22 -0500 (EST)
From: Vlad.Stirbu@nokia.com
Received: from mgw-x2.nokia.com ([131.228.20.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Czimv-0006XE-AV
	for mmusic@ietf.org; Fri, 11 Feb 2005 16:57:22 -0500
Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158])
	by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	j1BLaKc21201
	for <mmusic@ietf.org>; Fri, 11 Feb 2005 23:36:20 +0200 (EET)
X-Scanned: Fri, 11 Feb 2005 23:36:12 +0200 Nokia Message Protector V1.3.34
	2004121512 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id j1BLaCT7021511
	for <mmusic@ietf.org>; Fri, 11 Feb 2005 23:36:12 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks003.ntc.nokia.com 00Mh2iVQ; Fri, 11 Feb 2005 23:36:11 EET
Received: from esebh003.NOE.Nokia.com (esebh003.ntc.nokia.com [172.21.138.82])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	j1BLa6M13364
	for <mmusic@ietf.org>; Fri, 11 Feb 2005 23:36:06 +0200 (EET)
Received: from esebe016.NOE.Nokia.com ([172.21.138.55]) by
	esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Fri, 11 Feb 2005 23:35:53 +0200
Received: from trebe051.NOE.Nokia.com ([172.22.124.60]) by
	esebe016.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Fri, 11 Feb 2005 23:35:53 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 11 Feb 2005 23:35:51 +0200
Message-ID: <859FD8CF5299024EA90CA4E8B79D730D14C2B3@trebe051.ntc.nokia.com>
Thread-Topic: New I-D submitted for Requirements for Scalable Remote Access to
	Applications
Thread-Index: AcUQgaieQCNskCmcS++NhzCIKyZY9A==
To: <mmusic@ietf.org>
X-OriginalArrivalTime: 11 Feb 2005 21:35:53.0221 (UTC)
	FILETIME=[A99A3B50:01C51081]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: quoted-printable
Subject: [MMUSIC] New I-D submitted for Requirements for Scalable Remote
	Access to Applications
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: quoted-printable

Hello,

The new draft is available at =
http://www.kolumbus.fi/vlad.stirbu/draft-stirbu-mmusic-scal-sharing-00.tx=
t until it appears in the Drafts Directory.

Abstract:

   This memo describes the requirements for accessing graphical user
   interface (GUI) applications remotely, so that devices with different
   form factors and UI capabilities can scale and adapt the exported UI
   to their local platform UI look and feel (LAF).


Regards,
Vlad

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


From mmusic-bounces@ietf.org  Fri Feb 11 18:03:48 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06186
	for <mmusic-web-archive@ietf.org>; Fri, 11 Feb 2005 18:03:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Czk9Y-0002C8-Lr
	for mmusic-web-archive@ietf.org; Fri, 11 Feb 2005 18:24:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CzjmI-0005Ho-3R; Fri, 11 Feb 2005 18:00:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Czjfc-0002td-Q7; Fri, 11 Feb 2005 17:53:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05359;
	Fri, 11 Feb 2005 17:53:50 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Czjzu-0001zY-Tg; Fri, 11 Feb 2005 18:14:52 -0500
Received: from sj-core-4.cisco.com (171.68.223.138)
	by sj-iport-4.cisco.com with ESMTP; 11 Feb 2005 14:54:13 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from vtg-um-e2k1.sj21ad.cisco.com (vtg-um-e2k1.cisco.com
	[171.70.93.55])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j1BMrHYO019314;
	Fri, 11 Feb 2005 14:53:18 -0800 (PST)
Received: from klantz-w2k02.cisco.com ([128.107.142.38]) by
	vtg-um-e2k1.sj21ad.cisco.com with Microsoft SMTPSVC(5.0.2195.6713); 
	Fri, 11 Feb 2005 14:53:12 -0800
Message-Id: <6.2.0.14.2.20050211145031.03260dd0@vtg-um-e2k1.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
Date: Fri, 11 Feb 2005 14:53:09 -0800
To: Vlad.Stirbu@nokia.com
From: Keith Lantz <klantz@cisco.com>
In-Reply-To: <859FD8CF5299024EA90CA4E8B79D730DE662D8@trebe051.ntc.nokia. com>
References: <859FD8CF5299024EA90CA4E8B79D730DE662D8@trebe051.ntc.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 11 Feb 2005 22:53:12.0397 (UTC)
	FILETIME=[76C44FD0:01C5108C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: avt@ietf.org, mmusic@ietf.org
Subject: [MMUSIC] Re: [AVT] New I-D for The Lightweight Remote Display
	Protocol
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5

Can you clarify why the requirements are being submitted to mmusic but the 
protocol itself to avt?

Keith

At 01:38 PM 2/11/2005, you wrote:
>Hello,
>
>The new draft is available at 
>http://www.kolumbus.fi/vlad.stirbu/draft-stirbu-avt-lrdp-00.txt until it 
>appears in the Drafts Directory.
>
>Abstract:
>
>    This memo describes an application layer protocol for a framework
>    that enables accessing graphical user interface (GUI) applications
>    remotely, so that devices with different form factors and UI
>    capabilities can scale and adapt the exported UI to their local
>    platform UI look and feel (LAF).  Specified in the Extensible Markup
>    Language (XML), the protocol defines generic user interface (UI)
>    operations and a mechanism for extending these operations for
>    specific application needs.
>
>
>Regards,
>Vlad
>
>_______________________________________________
>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


From mmusic-bounces@ietf.org  Sat Feb 12 16:04:19 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00824
	for <mmusic-web-archive@ietf.org>; Sat, 12 Feb 2005 16:04:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D04ld-0002m8-HN
	for mmusic-web-archive@ietf.org; Sat, 12 Feb 2005 16:25:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D04Q2-00049D-QF; Sat, 12 Feb 2005 16:03:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D04Pr-0003x1-OK; Sat, 12 Feb 2005 16:02:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00781;
	Sat, 12 Feb 2005 16:02:57 -0500 (EST)
Received: from cyber.robotics.net ([209.150.98.82] helo=barney.robotics.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D04kK-0002kl-BY; Sat, 12 Feb 2005 16:24:10 -0500
Received: from barney.robotics.net (barney.robotics.net [209.150.98.82])
	by barney.robotics.net (8.12.10/8.12.10) with ESMTP id j1CL1rCO005278; 
	Sat, 12 Feb 2005 16:01:53 -0500
Date: Sat, 12 Feb 2005 16:01:53 -0500 (EST)
From: Nathan Allen Stratton <nathan@robotics.net>
To: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [MMUSIC] BFCP: SDP usage and k=
In-Reply-To: <3d298d2cf5c4d747f4326f93220e2b63@cisco.com>
Message-ID: <Pine.LNX.4.58.0502121558580.5194@barney.robotics.net>
References: <4209433A.2000005@nostrum.com>
	<3d298d2cf5c4d747f4326f93220e2b63@cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: XCON-IETF <xcon@ietf.org>, mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb

On Wed, 9 Feb 2005, Mark Baugher wrote:

> On Feb 8, 2005, at 2:54 PM, Adam Roach wrote:
>
> > [as XCON chair]
> >
> > I am copying the MMUSIC mailing list on this message, since I believe
> > there may be individuals in MMUSIC who are willing and able to assist
> > in a decision that the XCON working group must make. Fundamentally,
> > though, I believe this is an XCON issue, so I believe any ensuing
> > discussion should take place on the XCON mailing list.
> >
> > Currently, the SDP document for BFCP
> > (draft-ietf-mmusic-sdp-bfcp-00.txt) talks about using the k= line for
> > calculation of DIGEST TLV values.
>
> I glanced at the usage of k= in this I-D, which says that it encodes a
> shared secret.  But where does it specify what kind of shared secret?
> What algorithm is used for computing the digest?  I did not study the
> draft and may be missing something.  If it is completely specified then
> it avoids the general problem that we found with k= in the past, namely
> that there is no way to identify the transform to be used and pass
> additional cryptographic and session parameters that practically always
> need to be communicated with a cryptographic key.  If
> draft-ietf-mmusic-sdp-bfcp-00.txt does not have these problems and k=
> signals all needed information, then there may be no problem.

My understanding of mmusic-kmgmt-ext-13 is that it is open to using many
different key management protocols. I however am in the dark as to what
the draft use of mikey is, I think based on RFC 7311 it is AES, but I am
not sure.

><>
Nathan Stratton                                   BroadVoice, Inc.
nathan at robotics.net                                 Talk IS Cheap
http://www.robotics.net                           http://www.broadvoice.com

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


From mmusic-bounces@ietf.org  Sat Feb 12 16:37:17 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03098
	for <mmusic-web-archive@ietf.org>; Sat, 12 Feb 2005 16:37:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D05Ha-0003Pm-N1
	for mmusic-web-archive@ietf.org; Sat, 12 Feb 2005 16:58:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D04w2-0002ry-CT; Sat, 12 Feb 2005 16:36:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D04s5-00028s-Ov; Sat, 12 Feb 2005 16:32:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02662;
	Sat, 12 Feb 2005 16:32:07 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D05CZ-0003K1-SN; Sat, 12 Feb 2005 16:53:21 -0500
Received: from sj-core-4.cisco.com (171.68.223.138)
	by sj-iport-4.cisco.com with ESMTP; 12 Feb 2005 13:31:40 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j1CLVYYO018733;
	Sat, 12 Feb 2005 13:31:35 -0800 (PST)
Received: from [192.168.0.10] (sjc-vpn7-559.cisco.com [10.21.146.47])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j1CLQdro012353;
	Sat, 12 Feb 2005 13:26:39 -0800
In-Reply-To: <Pine.LNX.4.58.0502121558580.5194@barney.robotics.net>
References: <4209433A.2000005@nostrum.com>
	<3d298d2cf5c4d747f4326f93220e2b63@cisco.com>
	<Pine.LNX.4.58.0502121558580.5194@barney.robotics.net>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <55271b57c6fc428057a547b9ac761839@cisco.com>
Content-Transfer-Encoding: 7bit
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [MMUSIC] BFCP: SDP usage and k=
Date: Sat, 12 Feb 2005 13:31:29 -0800
To: Nathan Allen Stratton <nathan@robotics.net>
X-Mailer: Apple Mail (2.619.2)
IIM-SIG: v:"1.1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1108243599.694004"; x:"432200"; a:"rsa-sha1"; b:"nofws:1449";
	e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2p"
	"XIweAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRUtW+c43sl9jC"
	"50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"ga28o0D69itOhrXfNVVwAck34gf7y5FZYripccAM+jy2L55zapP6w7/bjth5Rc7cYoCkqLwS"
	"b0dCVdSv7omnLeFFkeDsgPkz9pu5nYrowsRLJhGwQCa7Sbin9ChnJe6d9TGgBYcvUH4hSf1sq6T"
	"rmnf9NJr2Rt4bVJoVsWTZouY=";
	c:"From: Mark Baugher <mbaugher@cisco.com>";
	c:"Subject: Re: [MMUSIC] BFCP: SDP usage and k=3D";
	c:"Date: Sat, 12 Feb 2005 13:31:29 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
Cc: XCON-IETF <xcon@ietf.org>, mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit


On Feb 12, 2005, at 1:01 PM, Nathan Allen Stratton wrote:
>>
...
>> I glanced at the usage of k= in this I-D, which says that it encodes a
>> shared secret.  But where does it specify what kind of shared secret?
>> What algorithm is used for computing the digest?  I did not study the
>> draft and may be missing something.  If it is completely specified 
>> then
>> it avoids the general problem that we found with k= in the past, 
>> namely
>> that there is no way to identify the transform to be used and pass
>> additional cryptographic and session parameters that practically 
>> always
>> need to be communicated with a cryptographic key.  If
>> draft-ietf-mmusic-sdp-bfcp-00.txt does not have these problems and k=
>> signals all needed information, then there may be no problem.
>
> My understanding of mmusic-kmgmt-ext-13 is that it is open to using 
> many
> different key management protocols. I however am in the dark as to what
> the draft use of mikey is, I think based on RFC 7311 it is AES, but I 
> am
> not sure.

The specification that we're discussing makes no mention of MIKEY or 
the kmgmt I-D.  k= is a much different approach than kmgmt.   If the 
authors were to replace k= with something more expressive, then I'd 
expect that they would use sdescriptions.

The question that I have raised and that I don't think has been 
answered is whether k= is sufficient for carrying a digest key.  The 
authors could choose to use MIKEY/kmgmt or they could use 
sdescriptions.  Maybe k= meets the application requirements.  I don't 
know, which is why I asked the question: Is there a need to specify the 
algorithm with the key?

Mark

Mark
>
>> <>
> Nathan Stratton                                   BroadVoice, Inc.
> nathan at robotics.net                                 Talk IS Cheap
> http://www.robotics.net                           
> http://www.broadvoice.com
>

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


From mmusic-bounces@ietf.org  Sat Feb 12 17:44:26 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06669
	for <mmusic-web-archive@ietf.org>; Sat, 12 Feb 2005 17:44:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D06Ka-0004fG-E3
	for mmusic-web-archive@ietf.org; Sat, 12 Feb 2005 18:05:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D05yj-0007Qq-9U; Sat, 12 Feb 2005 17:43:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D05y3-0007H7-P6; Sat, 12 Feb 2005 17:42:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06574;
	Sat, 12 Feb 2005 17:42:21 -0500 (EST)
Received: from cyber.robotics.net ([209.150.98.82] helo=barney.robotics.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D06IZ-0004dn-Jq; Sat, 12 Feb 2005 18:03:35 -0500
Received: from barney.robotics.net (barney.robotics.net [209.150.98.82])
	by barney.robotics.net (8.12.10/8.12.10) with ESMTP id j1CMgOCO007122; 
	Sat, 12 Feb 2005 17:42:24 -0500
Date: Sat, 12 Feb 2005 17:42:24 -0500 (EST)
From: Nathan Allen Stratton <nathan@robotics.net>
To: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [MMUSIC] BFCP: SDP usage and k=
In-Reply-To: <55271b57c6fc428057a547b9ac761839@cisco.com>
Message-ID: <Pine.LNX.4.58.0502121659060.6114@barney.robotics.net>
References: <4209433A.2000005@nostrum.com>
	<3d298d2cf5c4d747f4326f93220e2b63@cisco.com>
	<Pine.LNX.4.58.0502121558580.5194@barney.robotics.net>
	<55271b57c6fc428057a547b9ac761839@cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: XCON-IETF <xcon@ietf.org>, mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44

On Sat, 12 Feb 2005, Mark Baugher wrote:

> The specification that we're discussing makes no mention of MIKEY or
> the kmgmt I-D.  k= is a much different approach than kmgmt.   If the
> authors were to replace k= with something more expressive, then I'd
> expect that they would use sdescriptions.
>
> The question that I have raised and that I don't think has been
> answered is whether k= is sufficient for carrying a digest key.  The
> authors could choose to use MIKEY/kmgmt or they could use
> sdescriptions.  Maybe k= meets the application requirements.  I don't
> know, which is why I asked the question: Is there a need to specify the
> algorithm with the key?

I am working with a number of hardware vendors and need to propose what
they implement in their devices. As a service provider I am looking for
someting like the Sipura SRTP implementation. A service provider has a
master cert and builds a private and public cert for each UA device with
name, phone number and exp date. The keys are stored in the user config
and the config is securely loaded into the device.

Ok, so now the fun part, I am just getting into this security game, so
please forgive me if I am totally missing someting. The problem I have
with the Sipura implementation is that they exchange public keys SIP INFO
and don't have plans to make that public so I can't use it between
vendors. So are any of these systems based on public/private keys where
the public key can be exchanged clear text and the voice encrypted with
the endpoint secret key and the remote endpoint public key?

It looks like the AES implementations are build around one key that is
based64 encoded and sent in plain text required TLS or some other trusted
communication between endpoints.

Now if I want to have a few vendors implement a standard sway to support
SRTP I don't see why I would need anything other then SDPnew k=, I would
have them use it to exchange the public keys. However, the two vendors I
am working with will do this, but I am wondering if there is a better way.
It would work with k=, but as you pointed out, other endpoints would have
no clue what algorithm was used to encrypt the keys. It could be the
public key of a RSA key pair or full AES key.

I need a system that is not proprietary and can be used among many vendors,
is based on a master key so that I can decrypt any voice call if required
to by law enforcement.

Any pointers as to what I should have them implement?

><>
Nathan Stratton                                   BroadVoice, Inc.
nathan at robotics.net                                 Talk IS Cheap
http://www.robotics.net                           http://www.broadvoice.com

> Mark

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


From mmusic-bounces@ietf.org  Sat Feb 12 19:34:13 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13774
	for <mmusic-web-archive@ietf.org>; Sat, 12 Feb 2005 19:34:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D082r-0006Xj-BD
	for mmusic-web-archive@ietf.org; Sat, 12 Feb 2005 19:55:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D07hB-0000Uw-PW; Sat, 12 Feb 2005 19:33:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D07gB-0000J6-3A; Sat, 12 Feb 2005 19:32:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13578;
	Sat, 12 Feb 2005 19:32:00 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D080h-0006UC-GL; Sat, 12 Feb 2005 19:53:16 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-3.cisco.com with ESMTP; 12 Feb 2005 17:43:55 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.88,197,1102291200"; 
	d="scan'208"; a="225443641:sNHT22154392"
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j1D0VSq8004608;
	Sat, 12 Feb 2005 16:31:29 -0800 (PST)
Received: from [192.168.0.10] (sjc-vpn6-459.cisco.com [10.21.121.203])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j1D0QXaA012782;
	Sat, 12 Feb 2005 16:26:33 -0800
In-Reply-To: <Pine.LNX.4.58.0502121659060.6114@barney.robotics.net>
References: <4209433A.2000005@nostrum.com>
	<3d298d2cf5c4d747f4326f93220e2b63@cisco.com>
	<Pine.LNX.4.58.0502121558580.5194@barney.robotics.net>
	<55271b57c6fc428057a547b9ac761839@cisco.com>
	<Pine.LNX.4.58.0502121659060.6114@barney.robotics.net>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <f8c4bdaafbf3e711eb46a382d014c305@cisco.com>
Content-Transfer-Encoding: 7bit
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [MMUSIC] BFCP: SDP usage and k=
Date: Sat, 12 Feb 2005 16:31:24 -0800
To: Nathan Allen Stratton <nathan@robotics.net>
X-Mailer: Apple Mail (2.619.2)
IIM-SIG: v:"1.1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1108254393.600040"; x:"432200"; a:"rsa-sha1"; b:"nofws:3380";
	e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2p"
	"XIweAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRUtW+c43sl9jC"
	"50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"OdvRrUYzM6LwvdSabuoFnOjhuErvpvQkTdctIaS5P0jvGlfn0Ta5qCsPBpk04lxfP4TB97ty"
	"13dn18l8RZ+zZ6cFChlGDUWP3ylDOoz9Eyt/QCzWfLgTVeZA7TM6hZNVIXbuBOD9/mKoDCVcsoB"
	"Jti37pcwVAWOvWqg3CqMNGd8=";
	c:"From: Mark Baugher <mbaugher@cisco.com>";
	c:"Subject: Re: [MMUSIC] BFCP: SDP usage and k=3D";
	c:"Date: Sat, 12 Feb 2005 16:31:24 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Content-Transfer-Encoding: 7bit
Cc: XCON-IETF <xcon@ietf.org>, mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Content-Transfer-Encoding: 7bit

Nathan
   I don't know if your questions are related to this particular thread  
or not.  If not, then I apologize for going off topic, but I comment  
below.

On Feb 12, 2005, at 2:42 PM, Nathan Allen Stratton wrote:

> On Sat, 12 Feb 2005, Mark Baugher wrote:
>
>> The specification that we're discussing makes no mention of MIKEY or
>> the kmgmt I-D.  k= is a much different approach than kmgmt.   If the
>> authors were to replace k= with something more expressive, then I'd
>> expect that they would use sdescriptions.
>>
>> The question that I have raised and that I don't think has been
>> answered is whether k= is sufficient for carrying a digest key.  The
>> authors could choose to use MIKEY/kmgmt or they could use
>> sdescriptions.  Maybe k= meets the application requirements.  I don't
>> know, which is why I asked the question: Is there a need to specify  
>> the
>> algorithm with the key?
>
> I am working with a number of hardware vendors and need to propose what
> they implement in their devices. As a service provider I am looking for
> someting like the Sipura SRTP implementation. A service provider has a
> master cert and builds a private and public cert

I don't know what a private cert is.  I expect that there is some kind  
of
X.509 certificate in the solution and that the certificate contains the
public key of the subject, e.g. the phone.  I can't guess who the
issuer would be.

> for each UA device with
> name, phone number and exp date. The keys are stored in the user config
> and the config is securely loaded into the device.
>
> Ok, so now the fun part, I am just getting into this security game, so
> please forgive me if I am totally missing someting. The problem I have
> with the Sipura implementation is that they exchange public keys SIP  
> INFO
> and don't have plans to make that public so I can't use it between
> vendors.

They may not have plans to make their proprietary solution public, but
they may have plans to migrate to a standard solution when the industry
settles on one.  I think they can use MIKEY with kmgmt, or they can
use sdescriptions[1] with sip certificates[2].

[1]  
(http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-mmusic- 
sdescriptions-09.txt)
[2]  
(http://www1.ietf.org/internet-drafts/draft-ietf-sipping-certs-00.txt)
> So are any of these systems based on public/private keys where
> the public key can be exchanged clear text and the voice encrypted with
> the endpoint secret key and the remote endpoint public key?

Both sets of solutions use public key cryptography, at least as an  
option.
draft-ietf-sipping certs uses S/MIME.
>
> It looks like the AES implementations are build around one key that is
> based64 encoded and sent in plain text required TLS or some other  
> trusted
> communication between endpoints.

draft-ietf-mmusic-sdescriptions does this.  MIKEY does it differently.
>
> Now if I want to have a few vendors implement a standard sway to  
> support
> SRTP I don't see why I would need anything other then SDPnew k=, I  
> would
> have them use it to exchange the public keys. However, the two vendors  
> I
> am working with will do this, but I am wondering if there is a better  
> way.
> It would work with k=, but as you pointed out, other endpoints would  
> have
> no clue what algorithm was used to encrypt the keys. It could be the
> public key of a RSA key pair or full AES key.

Since you're the service provider, the vendor might suggest which
of the standards they plan to offer for sale.
>
> I need a system that is not proprietary and can be used among many  
> vendors,
> is based on a master key so that I can decrypt any voice call if  
> required
> to by law enforcement.

Most products will be using proprietary solutions for key establishment
since SRTP came out before the standards that key it.  I would expect
that the astute product team will have a roadmap for inter-operable
key establishment.
>
> Any pointers as to what I should have them implement?

Just the ones I mentioned above.

Mark
>
>> <>
> Nathan Stratton                                   BroadVoice, Inc.
> nathan at robotics.net                                 Talk IS Cheap
> http://www.robotics.net                            
> http://www.broadvoice.com
>
>> Mark
>

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


From mmusic-bounces@ietf.org  Sat Feb 12 23:00:17 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26985
	for <mmusic-web-archive@ietf.org>; Sat, 12 Feb 2005 23:00:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D0BGI-0001qa-8n
	for mmusic-web-archive@ietf.org; Sat, 12 Feb 2005 23:21:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D0Auc-0006cW-Ja; Sat, 12 Feb 2005 22:59:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D0Au2-0006Tt-Kj; Sat, 12 Feb 2005 22:58:34 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26875;
	Sat, 12 Feb 2005 22:58:32 -0500 (EST)
Received: from cyber.robotics.net ([209.150.98.82] helo=barney.robotics.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D0BEb-0001o1-8B; Sat, 12 Feb 2005 23:19:49 -0500
Received: from barney.robotics.net (barney.robotics.net [209.150.98.82])
	by barney.robotics.net (8.12.10/8.12.10) with ESMTP id j1D3vXrg012357; 
	Sat, 12 Feb 2005 22:57:33 -0500
Date: Sat, 12 Feb 2005 22:57:33 -0500 (EST)
From: Nathan Allen Stratton <nathan@robotics.net>
To: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [MMUSIC] BFCP: SDP usage and k=
In-Reply-To: <f8c4bdaafbf3e711eb46a382d014c305@cisco.com>
Message-ID: <Pine.LNX.4.58.0502122242230.12182@barney.robotics.net>
References: <4209433A.2000005@nostrum.com>
	<3d298d2cf5c4d747f4326f93220e2b63@cisco.com>
	<Pine.LNX.4.58.0502121558580.5194@barney.robotics.net>
	<55271b57c6fc428057a547b9ac761839@cisco.com>
	<Pine.LNX.4.58.0502121659060.6114@barney.robotics.net>
	<f8c4bdaafbf3e711eb46a382d014c305@cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: XCON-IETF <xcon@ietf.org>, mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955

On Sat, 12 Feb 2005, Mark Baugher wrote:

> Nathan
>    I don't know if your questions are related to this particular thread
> or not.  If not, then I apologize for going off topic, but I comment
> below.

: )

> On Feb 12, 2005, at 2:42 PM, Nathan Allen Stratton wrote:

> I don't know what a private cert is.  I expect that there is some kind
> of X.509 certificate in the solution and that the certificate contains
> the public key of the subject, e.g. the phone.  I can't guess who the
> issuer would be.

Correct, so what I am looking for is a way to exchange X.509 public certs,
I could just do this with k=, but I think that a key-mgmt-att-field may
make more sense. Since as a service provider I will already have private
keys in the UAs. I just need to worry about exchanging public keys.

> They may not have plans to make their proprietary solution public, but
> they may have plans to migrate to a standard solution when the industry
> settles on one.  I think they can use MIKEY with kmgmt, or they can
> use sdescriptions[1] with sip certificates[2].

So MIKEY is way overkill for what I need, since I am the service provider,
I have the ability to securely load the devices with private and public
keys, I just need a way for the devices to exchange public keys and start
SRTP (I still can't tell if SRTP is compatible with X.509 cert based
encryption).

> Since you're the service provider, the vendor might suggest which
> of the standards they plan to offer for sale.

Hehe, ya, one would think, but the vendors I am working with are launching
with us as a service provider and then will sell to other service
providers. They are open to doing whatever I need so I want to put them on
the right track of what I would like implemented for SRTP. It needs to be
standards or at least drafts based. I need to be able to build private and
public certs (could be X.509) off my CA. This should give me the ability
to decrypt any voice call on my network if law enforcement requires.

> Most products will be using proprietary solutions for key establishment
> since SRTP came out before the standards that key it.  I would expect
> that the astute product team will have a roadmap for inter-operable
> key establishment.

Yep, SNOM looks the closest to standards, based on AES using k= in SDP.
The problem I have with this is that it is totally secure and I as a
service provider can't decrypt streams if required to by law enforcement.
Sipura also has SRTP based on public/private certs loaded by the config
file. However they use SIP INFO to exchange keys and don't plan to open
that to the public.

So now I am back at square one. I could propose something to my vendors
based on X.509 certs and SRTP, but now how to I exchange public keys in a
non proprietary way while still having private keys stored in config files
not exchanged over the connection, thus not requiring TLS or the like.


><>
Nathan Stratton                                   BroadVoice, Inc.
nathan at robotics.net                                 Talk IS Cheap
http://www.robotics.net                           http://www.broadvoice.com

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


From mmusic-bounces@ietf.org  Mon Feb 14 08:52:17 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03855
	for <mmusic-web-archive@ietf.org>; Mon, 14 Feb 2005 08:52:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D0gz1-0002WY-HN
	for mmusic-web-archive@ietf.org; Mon, 14 Feb 2005 09:13:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D0gd5-0005ad-T1; Mon, 14 Feb 2005 08:51:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D0gb1-0005PL-1G
	for mmusic@megatron.ietf.org; Mon, 14 Feb 2005 08:49:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03706
	for <mmusic@ietf.org>; Mon, 14 Feb 2005 08:49:01 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0gvq-0002TO-CH
	for mmusic@ietf.org; Mon, 14 Feb 2005 09:10:35 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j1EDn0O6032753 for <mmusic@ietf.org>; Mon, 14 Feb 2005 14:49:00 +0100
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 14 Feb 2005 14:49:29 +0100
Received: from [147.214.237.66] (vmclient-50 [147.214.237.66]) by
	esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id 18XJ7SFV; Mon, 14 Feb 2005 14:51:59 +0100
Message-ID: <4210AC4C.1030409@ericsson.com>
Date: Mon, 14 Feb 2005 14:49:00 +0100
X-Sybari-Trust: 09f62a90 b8ec86c7 c050e4db 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "mmusic (E-mail)" <mmusic@ietf.org>,
        =?UTF-8?B?IlBlciBGcsO2amRoIChLSS8=?=
	=?UTF-8?B?RUFCKSI=?= <per.frojdh@ericsson.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Feb 2005 13:49:29.0948 (UTC)
	FILETIME=[0182E1C0:01C5129C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] New draft: draft-westerlund-mmusic-3gpp-sdp-rtsp-00.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit

Hi,

I and my colleague Per has written and submitted a draft that intends to 
register the SDP attributes that 3GPP has created for the 
Packet-switched Streaming Service. It does also contain a informational 
description of the RTSP headers, which will be directly registered in 
the new specification. Until the draft becomes available, you can fetch 
it here:
http://standards.ericsson.net/westerlund/draft-westerlund-mmusic-3gpp-sdp-rtsp-00.txt

The draft is intended to become an individual publication, however it is 
hereby presented to MMUSIC for information and feedback.

Cheers

Magnus Westerlund

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

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


From mmusic-bounces@ietf.org  Mon Feb 14 20:45:58 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13836
	for <mmusic-web-archive@ietf.org>; Mon, 14 Feb 2005 20:45:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D0s7n-0006Pz-D8
	for mmusic-web-archive@ietf.org; Mon, 14 Feb 2005 21:07:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D0rkf-0000Pg-Cg; Mon, 14 Feb 2005 20:43:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D0riy-0000E8-P4
	for mmusic@megatron.ietf.org; Mon, 14 Feb 2005 20:42:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13652
	for <mmusic@ietf.org>; Mon, 14 Feb 2005 20:41:58 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0s3v-0006LH-7f
	for mmusic@ietf.org; Mon, 14 Feb 2005 21:03:40 -0500
Received: from sj-core-3.cisco.com (171.68.223.137)
	by sj-iport-5.cisco.com with ESMTP; 14 Feb 2005 17:43:05 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.90,85,1107763200"; 
	d="scan'208,217"; a="161471018:sNHT49321232"
Received: from vtg-um-e2k4.sj21ad.cisco.com (vtg-um-e2k4.cisco.com
	[171.70.93.57])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j1F1fQwN005361;
	Mon, 14 Feb 2005 17:41:27 -0800 (PST)
Received: e2k4.cisco.com 171.70.93.57 from 10.32.131.11 10.32.131.11 via HTTP
	with MS-WebStorage 6.5.6944
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Mon, 14 Feb 2005 17:41:27 -0800
Subject: Re: [MMUSIC] ICE feature - TCP alternates for a UDP stream
From: Cullen Jennings <fluffy@cisco.com>
To: Francois Audet <audet@nortel.com>, Jonathan Rosenberg <jdrosen@cisco.com>,
        "mmusic@ietf.org" <mmusic@ietf.org>
Message-ID: <BE369347.2863C%fluffy@cisco.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF016F45D7@zrc2hxm0.corp.nortel.com>
Mime-version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 913ee11e7c554f7d4da75d500826397e
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0616783112=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 872695ea777a517bf5717e5acc69f8be

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

--===============0616783112==
Content-type: multipart/alternative;
	boundary="B_3191247687_1718776"

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

--B_3191247687_1718776
Content-type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit


I think I am a little lost. RTP over TCP seems ok for streaming media but a
really bad idea for interactive (ie low latency media). However ICE is
primarily for where two clients want to connect which I generally think of a
interactive media.

Do we have a use case where we want to do streaming media between two
clients where ICE would be appropriate or are we thinking of this being used
with interactive media?

Cullen



On 2/1/05 4:46 PM, "Francois Audet" <audet@nortel.com> wrote:

> So you are saying that the media would be transported over RTP/TCP
> to the TURN relay, and then to the other endpoint using another RTP/TCP
> session, right? 
> 
> And not and end-to-end RTP/TCP session between the two peers, right?
> 
> 
> 
> 
>> > -----Original Message-----
>> > From: mmusic-bounces@ietf.org
>> > [mailto:mmusic-bounces@ietf.org] On Behalf Of Jonathan Rosenberg
>> > Sent: Thursday, January 27, 2005 10:43
>> > To: IETF MMUSIC WG
>> > Subject: [MMUSIC] ICE feature - TCP alternates for a UDP stream
>> > 
>> > 
>> > Folks, 
>> > 
>> > In the past, we had considered whether or not to also apply
>> > ICE to allow 
>> > a TCP session to be an alternate for a UDP one. We decided to
>> > keep the 
>> > scope narrow, and not consider this.
>> > 
>> > However, in reality, I think there is an extremely pressing need for
>> > this. In particular, there are many deployments where we
>> > would like to 
>> > support SIP, but (for better or for worse), networks are only
>> > allowing 
>> > outbound TCP connections. This is not a NAT issue so much as
>> > a firewall 
>> > issue, but in this case the firewall is introducing a connectivity
>> > problem of the sort that ICE was designed to address. As
>> > such, I think 
>> > its in scope. If we defer this to a future document, I fear
>> > we will get 
>> > implementations missing this feature and thus SIP/ICE clients
>> > will find 
>> > themselves in situations where it STILL doesnt "just work",
>> > despite the 
>> > fact that ICE is supposed to make it "just work".
>> > 
>> > Now, all of us agree, no doubt, that RTP over UDP is far
>> > preferable to 
>> > RTP over TCP, but if TCP is all you can get working, TCP is
>> > better than 
>> > nothing. ICE can serve a crucial role of figuring out, dynamically,
>> > whether or not UDP can be made to work, and thus whether the lower
>> > priority alternative of TCP, should be used.
>> > 
>> > So, here's how it would work. A client would include UDP local
>> > addresses, STUn derived addresses, TURN derived (using UDP), and ALSO
>> > TURN derived using TCP (recall that TURN supports TCP
>> > connections). We
>> > have a spec for RTP over TCP (draft-ietf-avt-rtp-framing-contrans),
>> > which makes use of the comedia spec. The client would specify
>> > that it is 
>> > passive. The INVITE is sent. The peer connects to this
>> > (indicating that
>> > it is active in its answer); that connection terminates on the TURN
>> > relay used by the caller. The peer, as with any other
>> > session, uses STUN
>> > to check connectivity. The caller can then use STUN itself to verify
>> > connectivity in its direction (presumably it would always
>> > work in both 
>> > directions). 
>> > 
>> > The nice thing is, by setting the priorities appropriately, this
>> > connection would only get used if the other UDP choices fail.
>> > That gives 
>> > us even further robustness.
>> > 
>> > Presumably this could also work for TLS, in which case the
>> > TURN server 
>> > would terminate the TLS connection from the caller and from
>> > the callee. 
>> > 
>> > Specifying this isn't really hard. The main issue is just a grouping
>> > one. We need to be able to apply the comedia parameters to
>> > candidates. 
>> > You can't just include them under the m-line, since then you
>> > don't know 
>> > to what they apply. In any case, we don't really need or even want a
>> > generic grouping framework here; I would HATE for this to be
>> > used as an 
>> > alternative for negotiating codec parameters in yet another way. As
>> > such, I would suggest merely extending the candidate line to
>> > include the 
>> > transports and comedia information when needed.
>> > 
>> > Comments? 
>> > 
>> > -Jonathan R. 
>> > 
>> > 
>> > 
>> > -- 
>> > Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
>> > Director, Service Provider VoIP Architecture   Parsippany, NJ
>> > 07054-2711 
>> > Cisco Systems 
>> > jdrosen@cisco.com                              FAX:   (973) 952-5050
>> > http://www.jdrosen.net                         PHONE: (973) 952-5000
>> > http://www.cisco.com
>> > 
>> > _______________________________________________
>> > mmusic mailing list
>> > mmusic@ietf.org
>> > https://www1.ietf.org/mailman/listinfo/mmusic
>> > 
>> > 
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic



--B_3191247687_1718776
Content-type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [MMUSIC] ICE feature - TCP alternates for a UDP stream</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:12.0px'><BR>
I think I am a little lost. RTP over TCP seems ok for streaming media but a=
 really bad idea for interactive (ie low latency media). However ICE is prim=
arily for where two clients want to connect which I generally think of a int=
eractive media.<BR>
<BR>
Do we have a use case where we want to do streaming media between two clien=
ts where ICE would be appropriate or are we thinking of this being used with=
 interactive media?<BR>
<BR>
Cullen<BR>
<BR>
<BR>
<BR>
On 2/1/05 4:46 PM, &quot;Francois Audet&quot; &lt;audet@nortel.com&gt; wrot=
e:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'>So you are saying that the media would be transported o=
ver RTP/TCP <BR>
to the TURN relay, and then to the other endpoint using another RTP/TCP <BR=
>
session, right? <BR>
<BR>
And not and end-to-end RTP/TCP session between the two peers, right? <BR>
<BR>
<BR>
<BR>
<BR>
&gt; -----Original Message----- <BR>
&gt; From: mmusic-bounces@ietf.org <BR>
&gt; [<a href=3D"mailto:mmusic-bounces@ietf.org]">mailto:mmusic-bounces@ietf.=
org]</a> On Behalf Of Jonathan Rosenberg <BR>
&gt; Sent: Thursday, January 27, 2005 10:43 <BR>
&gt; To: IETF MMUSIC WG <BR>
&gt; Subject: [MMUSIC] ICE feature - TCP alternates for a UDP stream <BR>
&gt; <BR>
&gt; <BR>
&gt; Folks, <BR>
&gt; <BR>
&gt; In the past, we had considered whether or not to also apply <BR>
&gt; ICE to allow <BR>
&gt; a TCP session to be an alternate for a UDP one. We decided to <BR>
&gt; keep the <BR>
&gt; scope narrow, and not consider this. <BR>
&gt; <BR>
&gt; However, in reality, I think there is an extremely pressing need for <=
BR>
&gt; this. In particular, there are many deployments where we <BR>
&gt; would like to <BR>
&gt; support SIP, but (for better or for worse), networks are only <BR>
&gt; allowing <BR>
&gt; outbound TCP connections. This is not a NAT issue so much as <BR>
&gt; a firewall <BR>
&gt; issue, but in this case the firewall is introducing a connectivity <BR=
>
&gt; problem of the sort that ICE was designed to address. As <BR>
&gt; such, I think <BR>
&gt; its in scope. If we defer this to a future document, I fear <BR>
&gt; we will get <BR>
&gt; implementations missing this feature and thus SIP/ICE clients <BR>
&gt; will find <BR>
&gt; themselves in situations where it STILL doesnt &quot;just work&quot;, =
<BR>
&gt; despite the <BR>
&gt; fact that ICE is supposed to make it &quot;just work&quot;. <BR>
&gt; <BR>
&gt; Now, all of us agree, no doubt, that RTP over UDP is far <BR>
&gt; preferable to <BR>
&gt; RTP over TCP, but if TCP is all you can get working, TCP is <BR>
&gt; better than <BR>
&gt; nothing. ICE can serve a crucial role of figuring out, dynamically, <B=
R>
&gt; whether or not UDP can be made to work, and thus whether the lower <BR=
>
&gt; priority alternative of TCP, should be used. <BR>
&gt; <BR>
&gt; So, here's how it would work. A client would include UDP local <BR>
&gt; addresses, STUn derived addresses, TURN derived (using UDP), and ALSO =
<BR>
&gt; TURN derived using TCP (recall that TURN supports TCP <BR>
&gt; connections). We <BR>
&gt; have a spec for RTP over TCP (draft-ietf-avt-rtp-framing-contrans), <B=
R>
&gt; which makes use of the comedia spec. The client would specify <BR>
&gt; that it is <BR>
&gt; passive. The INVITE is sent. The peer connects to this <BR>
&gt; (indicating that <BR>
&gt; it is active in its answer); that connection terminates on the TURN <B=
R>
&gt; relay used by the caller. The peer, as with any other <BR>
&gt; session, uses STUN <BR>
&gt; to check connectivity. The caller can then use STUN itself to verify <=
BR>
&gt; connectivity in its direction (presumably it would always <BR>
&gt; work in both <BR>
&gt; directions). <BR>
&gt; <BR>
&gt; The nice thing is, by setting the priorities appropriately, this <BR>
&gt; connection would only get used if the other UDP choices fail. <BR>
&gt; That gives <BR>
&gt; us even further robustness. <BR>
&gt; <BR>
&gt; Presumably this could also work for TLS, in which case the <BR>
&gt; TURN server <BR>
&gt; would terminate the TLS connection from the caller and from <BR>
&gt; the callee. <BR>
&gt; <BR>
&gt; Specifying this isn't really hard. The main issue is just a grouping <=
BR>
&gt; one. We need to be able to apply the comedia parameters to <BR>
&gt; candidates. <BR>
&gt; You can't just include them under the m-line, since then you <BR>
&gt; don't know <BR>
&gt; to what they apply. In any case, we don't really need or even want a <=
BR>
&gt; generic grouping framework here; I would HATE for this to be <BR>
&gt; used as an <BR>
&gt; alternative for negotiating codec parameters in yet another way. As <B=
R>
&gt; such, I would suggest merely extending the candidate line to <BR>
&gt; include the <BR>
&gt; transports and comedia information when needed. <BR>
&gt; <BR>
&gt; Comments? <BR>
&gt; <BR>
&gt; -Jonathan R. <BR>
&gt; <BR>
&gt; <BR>
&gt; <BR>
&gt; -- <BR>
&gt; Jonathan D. Rosenberg, Ph.D. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;600 Lanid=
ex Plaza <BR>
&gt; Director, Service Provider VoIP Architecture &nbsp;&nbsp;Parsippany, N=
J <BR>
&gt; 07054-2711 <BR>
&gt; Cisco Systems <BR>
&gt; jdrosen@cisco.com &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FAX: &nbsp;&nbsp;(973) 952-505=
0 <BR>
&gt; <a href=3D"http://www.jdrosen.net">http://www.jdrosen.net</a> &nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PHONE: (973) 952-5=
000 <BR>
&gt; <a href=3D"http://www.cisco.com">http://www.cisco.com</a> <BR>
&gt; <BR>
&gt; _______________________________________________ <BR>
&gt; mmusic mailing list <BR>
&gt; mmusic@ietf.org <BR>
&gt; https://www1.ietf.org/mailman/listinfo/mmusic <BR>
&gt; <BR>
&gt; <BR>
<BR>
<HR ALIGN=3DCENTER SIZE=3D"3" WIDTH=3D"95%"></SPAN></FONT><FONT SIZE=3D"2"><FONT FA=
CE=3D"Monaco, Courier New"><SPAN STYLE=3D'font-size:10.0px'>____________________=
___________________________<BR>
mmusic mailing list<BR>
mmusic@ietf.org<BR>
https://www1.ietf.org/mailman/listinfo/mmusic<BR>
</SPAN></FONT></FONT></BLOCKQUOTE><FONT SIZE=3D"2"><FONT FACE=3D"Monaco, Courie=
r New"><SPAN STYLE=3D'font-size:10.0px'><BR>
</SPAN></FONT></FONT>
</BODY>
</HTML>


--B_3191247687_1718776--


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

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

--===============0616783112==--



From mmusic-bounces@ietf.org  Tue Feb 15 03:25:25 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAB05607
	for <mmusic-web-archive@ietf.org>; Tue, 15 Feb 2005 03:25:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D0yMO-0006CH-Lo
	for mmusic-web-archive@ietf.org; Tue, 15 Feb 2005 03:47:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D0y0E-0002YW-EA; Tue, 15 Feb 2005 03:24:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D0xxf-0002Et-4T
	for mmusic@megatron.ietf.org; Tue, 15 Feb 2005 03:21:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05386
	for <mmusic@ietf.org>; Tue, 15 Feb 2005 03:21:33 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0yIe-00066u-B0
	for mmusic@ietf.org; Tue, 15 Feb 2005 03:43:17 -0500
Received: from esealmw129.eemea.ericsson.se ([153.88.254.120])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j1F8KPh5015062; Tue, 15 Feb 2005 09:20:25 +0100 (MET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 15 Feb 2005 09:20:56 +0100
Received: from [147.214.237.66] ([147.214.237.66]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 15 Feb 2005 09:21:03 +0100
Message-ID: <4211B0C9.7030902@ericsson.com>
Date: Tue, 15 Feb 2005 09:20:25 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [MMUSIC] ICE feature - TCP alternates for a UDP stream
References: <BE369347.2863C%fluffy@cisco.com>
In-Reply-To: <BE369347.2863C%fluffy@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Feb 2005 08:21:03.0889 (UTC)
	FILETIME=[4A32A810:01C51337]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
Cc: Francois Audet <audet@nortel.com>, mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit

Hi Cullen,

I can at least answer that having streaming between arbitrary placed 
servers and clients is a valid use case. Think, home surveillance camera 
and you end up with a potentially NATed and FWed streaming server.

Cheers

Magnus

Cullen Jennings wrote:
> I think I am a little lost. RTP over TCP seems ok for streaming media but a really bad idea for interactive (ie low latency media). However ICE is primarily for where two clients want to connect which I generally think of a interactive media.
> 
> Do we have a use case where we want to do streaming media between two clients where ICE would be appropriate or are we thinking of this being used with interactive media?
> 


-- 

Magnus Westerlund

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

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


From mmusic-bounces@ietf.org  Tue Feb 15 07:40:15 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25606
	for <mmusic-web-archive@ietf.org>; Tue, 15 Feb 2005 07:40:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D12L3-0003UU-GS
	for mmusic-web-archive@ietf.org; Tue, 15 Feb 2005 08:02:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D11yb-0005ax-U0; Tue, 15 Feb 2005 07:38:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D11ti-00053P-QB
	for mmusic@megatron.ietf.org; Tue, 15 Feb 2005 07:33:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24954
	for <mmusic@ietf.org>; Tue, 15 Feb 2005 07:33:45 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D12Ek-0003B5-8e
	for mmusic@ietf.org; Tue, 15 Feb 2005 07:55:31 -0500
Received: from esealmw126.eemea.ericsson.se ([153.88.254.123])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j1FCXchD015081
	for <mmusic@ietf.org>; Tue, 15 Feb 2005 13:33:44 +0100 (MET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 15 Feb 2005 13:34:08 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.13]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 15 Feb 2005 13:34:08 +0100
Received: from ericsson.com (EFO9N000L5C7100.lmf.ericsson.se [131.160.37.196])
	by mail.lmf.ericsson.se (Postfix) with ESMTP
	id 08F3C18A90; Tue, 15 Feb 2005 14:33:37 +0200 (EET)
Message-ID: <4211EC3F.1060200@ericsson.com>
Date: Tue, 15 Feb 2005 14:34:07 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mmusic <mmusic@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Feb 2005 12:34:08.0367 (UTC)
	FILETIME=[A4DA1FF0:01C5135A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Draft: Content labels
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit

Folks,

we have put together a draft that defines an SDP attribute to carry the
contents of a media stream in a way that is meaningful to applications.
That is, the labels used here are intended for automata. For example,
they allow to label a video stream as signed language, or as the output
of the main camera.

Until the draft appears in the archives, you can fetch it from:

http://users.piuha.net/gonzalo/temp/draft-hautakorpi-mmusic-sdp-media-content-00.txt

Comments are welcome,

Gonzalo


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


From mmusic-bounces@ietf.org  Wed Feb 16 03:48:12 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13049
	for <mmusic-web-archive@ietf.org>; Wed, 16 Feb 2005 03:48:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1LCD-0004xZ-JX
	for mmusic-web-archive@ietf.org; Wed, 16 Feb 2005 04:10:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1KiL-0003FV-9V; Wed, 16 Feb 2005 03:39:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1KgJ-0002er-RU; Wed, 16 Feb 2005 03:37:12 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12024;
	Wed, 16 Feb 2005 03:37:09 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1L1U-0004F1-Bn; Wed, 16 Feb 2005 03:59:07 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j1G8b4O6005691; Wed, 16 Feb 2005 09:37:04 +0100
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 16 Feb 2005 09:37:36 +0100
Received: from [147.214.34.56] (research-1fd0e1.ki.sw.ericsson.se
	[147.214.34.56]) by esealnt611.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id 1ZVYS4L4; Wed, 16 Feb 2005 09:39:29 +0100
Message-ID: <4213062F.8080004@ericsson.com>
Date: Wed, 16 Feb 2005 09:37:03 +0100
X-Sybari-Trust: 555f0bb2 b8ec86c7 90c04c48 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Shailendra.Singh@skyworksinc.com
References: <OF3AA406DD.EB827A4C-ON65256FAA.00275213-65256FAA.00277762@noida.skyworksinc.com>
In-Reply-To: <OF3AA406DD.EB827A4C-ON65256FAA.00275213-65256FAA.00277762@noida.skyworksinc.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
X-OriginalArrivalTime: 16 Feb 2005 08:37:36.0185 (UTC)
	FILETIME=[C410C290:01C51402]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by eagle.ericsson.se id
	j1G8b4O6005691
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: quoted-printable
Cc: avt@ietf.org, "mmusic \(E-mail\)" <mmusic@ietf.org>
Subject: [MMUSIC] Re: [AVT] RTSP and negotiation about Codec's capabilities
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: quoted-printable

Hi,

This discussion belongs to the MMUSIC list, not AVT. Anyone responding=20
to this email, please remove AVT.


Shailendra.Singh@skyworksinc.com wrote:
> Hi,=20
>         Could some please clarify:=20
>         With RTSP as the control protocol for a streamed multimedia ses=
sion, how does the Server determine if the Player has the capability to d=
ecode the content it receives? In other words, how does the Player specif=
y the capabilities of the codecs available with it?=20
>         An example might clarify the information I am looking for. Supp=
ose the streamed content contains a MPEG-4 video bitstream (Simple Profil=
e and level L3). Now the Server needs to check if the MPEG-4 video decode=
r available with the Player has the capability to decode this bitstream o=
r not. Conceptually, it needs to query the Profile and Level supported by=
 the MPEG-4 video decoder, and that can help it decide whether the Player=
 can decode this particular MPEG-4 video bitstream or not.=20
>         How is this handled in a generic sense (the decoder could be a =
MP3 decoder, MPEG-4 video decoder, AAC decoder ...) ? Is there standard s=
et of parameters about each codec=E2=80=99s capability that the Player wo=
uld inform the Server ?=20

RTSP doesn't have any support for capability exchange. However this is=20
resolved in for example 3GPP PSS, where it is specified that one can=20
include UAProf profiles in the DESCRIBE request. See 3GPP TS 26.234 for=20
the specification.

Cheers


Magnus Westerlund

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

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


From mmusic-bounces@ietf.org  Wed Feb 16 04:29:16 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17381
	for <mmusic-web-archive@ietf.org>; Wed, 16 Feb 2005 04:29:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1Lpz-000679-59
	for mmusic-web-archive@ietf.org; Wed, 16 Feb 2005 04:51:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1LSz-0007dX-Ou; Wed, 16 Feb 2005 04:27:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1LP6-0006XU-DO
	for mmusic@megatron.ietf.org; Wed, 16 Feb 2005 04:23:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17090
	for <mmusic@ietf.org>; Wed, 16 Feb 2005 04:23:24 -0500 (EST)
From: Shailendra.Singh@skyworksinc.com
Received: from skysmtp01.skyworksinc.com ([66.161.70.247]
	helo=skysmtp01.irvine.skyworksinc.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1LkI-00060U-LW
	for mmusic@ietf.org; Wed, 16 Feb 2005 04:45:23 -0500
Received: from ivnlnhub01.nb.skyworksinc.com (ivnlnhub01.ad.skynet
	[10.18.8.30])
	by skysmtp01.irvine.skyworksinc.com (8.12.9+Sun/8.12.9) with ESMTP id
	j1G9LLUu026001
	for <mmusic@ietf.org>; Wed, 16 Feb 2005 01:21:21 -0800 (PST)
Received: from noiskydm1.noida.skyworksinc.com ([10.16.236.13])
	by ivnlnhub01.nb.skyworksinc.com (Lotus Domino Release 5.0.12)
	with ESMTP id 2005021601225372:525363 ;
	Wed, 16 Feb 2005 01:22:53 -0800 
To: mmusic@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.3 September 14, 2004
Message-ID: <OF407CDE06.DF4B46AD-ON65256FAA.00337771-65256FAA.0033880E@noida.skyworksinc.com>
Date: Wed, 16 Feb 2005 14:52:51 +0530
X-MIMETrack: Serialize by Router on NOISKYDM1/Server/Skyworks(Release 5.0.12
	|February 13, 2003) at 02/16/2005 02:52:53 PM,
	Serialize complete at 02/16/2005 02:52:53 PM,
	Itemize by SMTP Server on IVNLNHUB01/Server/Skyworks(Release 5.0.12
	|February 13, 2003) at 02/16/2005 01:22:54 AM,
	Serialize by Router on IVNLNHUB01/Server/Skyworks(Release 5.0.12
	|February 13, 2003) at 02/16/2005 01:22:55 AM,
	Serialize complete at 02/16/2005 01:22:55 AM
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Subject: [MMUSIC] RTSP and negotiation about Codec's capabilities
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0628733655=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36

This is a multipart message in MIME format.
--===============0628733655==
Content-Type: multipart/alternative;
	boundary="=_alternative 0033880E65256FAA_="

This is a multipart message in MIME format.
--=_alternative 0033880E65256FAA_=
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64

SGksDQogICAgICAgIENvdWxkIHNvbWUgcGxlYXNlIGNsYXJpZnk6DQogICAgICAgIFdpdGggUlRT
UCBhcyB0aGUgY29udHJvbCBwcm90b2NvbCBmb3IgYSBzdHJlYW1lZCBtdWx0aW1lZGlhIA0Kc2Vz
c2lvbiwgaG93IGRvZXMgdGhlIFNlcnZlciBkZXRlcm1pbmUgaWYgdGhlIFBsYXllciBoYXMgdGhl
IGNhcGFiaWxpdHkgdG8gDQpkZWNvZGUgdGhlIGNvbnRlbnQgaXQgcmVjZWl2ZXM/IEluIG90aGVy
IHdvcmRzLCBob3cgZG9lcyB0aGUgUGxheWVyIA0Kc3BlY2lmeSB0aGUgY2FwYWJpbGl0aWVzIG9m
IHRoZSBjb2RlY3MgYXZhaWxhYmxlIHdpdGggaXQ/DQogICAgICAgIEFuIGV4YW1wbGUgbWlnaHQg
Y2xhcmlmeSB0aGUgaW5mb3JtYXRpb24gSSBhbSBsb29raW5nIGZvci4gU3VwcG9zZSANCnRoZSBz
dHJlYW1lZCBjb250ZW50IGNvbnRhaW5zIGEgTVBFRy00IHZpZGVvIGJpdHN0cmVhbSAoU2ltcGxl
IFByb2ZpbGUgYW5kIA0KbGV2ZWwgTDMpLiBOb3cgdGhlIFNlcnZlciBuZWVkcyB0byBjaGVjayBp
ZiB0aGUgTVBFRy00IHZpZGVvIGRlY29kZXIgDQphdmFpbGFibGUgd2l0aCB0aGUgUGxheWVyIGhh
cyB0aGUgY2FwYWJpbGl0eSB0byBkZWNvZGUgdGhpcyBiaXRzdHJlYW0gb3IgDQpub3QuIENvbmNl
cHR1YWxseSwgaXQgbmVlZHMgdG8gcXVlcnkgdGhlIFByb2ZpbGUgYW5kIExldmVsIHN1cHBvcnRl
ZCBieSANCnRoZSBNUEVHLTQgdmlkZW8gZGVjb2RlciwgYW5kIHRoYXQgY2FuIGhlbHAgaXQgZGVj
aWRlIHdoZXRoZXIgdGhlIFBsYXllciANCmNhbiBkZWNvZGUgdGhpcyBwYXJ0aWN1bGFyIE1QRUct
NCB2aWRlbyBiaXRzdHJlYW0gb3Igbm90Lg0KICAgICAgICBIb3cgaXMgdGhpcyBoYW5kbGVkIGlu
IGEgZ2VuZXJpYyBzZW5zZSAodGhlIGRlY29kZXIgY291bGQgYmUgYSBNUDMgDQpkZWNvZGVyLCBN
UEVHLTQgdmlkZW8gZGVjb2RlciwgQUFDIGRlY29kZXIgLi4uKSA/IElzIHRoZXJlIHN0YW5kYXJk
IHNldCBvZiANCnBhcmFtZXRlcnMgYWJvdXQgZWFjaCBjb2RlY+KAmXMgY2FwYWJpbGl0eSB0aGF0
IHRoZSBQbGF5ZXIgd291bGQgaW5mb3JtIHRoZSANClNlcnZlciA/DQoNClRoYW5rcywNClNoYWls
ZW5kcmENCg==
--=_alternative 0033880E65256FAA_=
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkhpLDwvZm9udD4NCjxicj48Zm9u
dCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IENv
dWxkDQpzb21lIHBsZWFzZSBjbGFyaWZ5OjwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0i
c2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IFdpdGgNClJUU1AgYXMgdGhl
IGNvbnRyb2wgcHJvdG9jb2wgZm9yIGEgc3RyZWFtZWQgbXVsdGltZWRpYSBzZXNzaW9uLCBob3cg
ZG9lcw0KdGhlIFNlcnZlciBkZXRlcm1pbmUgaWYgdGhlIFBsYXllciBoYXMgdGhlIGNhcGFiaWxp
dHkgdG8gZGVjb2RlIHRoZSBjb250ZW50DQppdCByZWNlaXZlcz8gSW4gb3RoZXIgd29yZHMsIGhv
dyBkb2VzIHRoZSBQbGF5ZXIgc3BlY2lmeSB0aGUgY2FwYWJpbGl0aWVzDQpvZiB0aGUgY29kZWNz
IGF2YWlsYWJsZSB3aXRoIGl0PzwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1z
ZXJpZiI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IEFuDQpleGFtcGxlIG1pZ2h0IGNsYXJp
ZnkgdGhlIGluZm9ybWF0aW9uIEkgYW0gbG9va2luZyBmb3IuIFN1cHBvc2UgdGhlIHN0cmVhbWVk
DQpjb250ZW50IGNvbnRhaW5zIGEgTVBFRy00IHZpZGVvIGJpdHN0cmVhbSAoU2ltcGxlIFByb2Zp
bGUgYW5kIGxldmVsIEwzKS4NCk5vdyB0aGUgU2VydmVyIG5lZWRzIHRvIGNoZWNrIGlmIHRoZSBN
UEVHLTQgdmlkZW8gZGVjb2RlciBhdmFpbGFibGUgd2l0aA0KdGhlIFBsYXllciBoYXMgdGhlIGNh
cGFiaWxpdHkgdG8gZGVjb2RlIHRoaXMgYml0c3RyZWFtIG9yIG5vdC4gQ29uY2VwdHVhbGx5LA0K
aXQgbmVlZHMgdG8gcXVlcnkgdGhlIFByb2ZpbGUgYW5kIExldmVsIHN1cHBvcnRlZCBieSB0aGUg
TVBFRy00IHZpZGVvIGRlY29kZXIsDQphbmQgdGhhdCBjYW4gaGVscCBpdCBkZWNpZGUgd2hldGhl
ciB0aGUgUGxheWVyIGNhbiBkZWNvZGUgdGhpcyBwYXJ0aWN1bGFyDQpNUEVHLTQgdmlkZW8gYml0
c3RyZWFtIG9yIG5vdC48L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYi
PiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBIb3cNCmlzIHRoaXMgaGFuZGxlZCBpbiBhIGdl
bmVyaWMgc2Vuc2UgKHRoZSBkZWNvZGVyIGNvdWxkIGJlIGEgTVAzIGRlY29kZXIsDQpNUEVHLTQg
dmlkZW8gZGVjb2RlciwgQUFDIGRlY29kZXIgLi4uKSA/IElzIHRoZXJlIHN0YW5kYXJkIHNldCBv
ZiBwYXJhbWV0ZXJzDQphYm91dCBlYWNoIGNvZGVj4oCZcyBjYXBhYmlsaXR5IHRoYXQgdGhlIFBs
YXllciB3b3VsZCBpbmZvcm0gdGhlIFNlcnZlcg0KPzwvZm9udD4NCjxicj4NCjxicj48Zm9udCBz
aXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+VGhhbmtzLDwvZm9udD4NCjxicj48Zm9udCBzaXplPTIg
ZmFjZT0ic2Fucy1zZXJpZiI+U2hhaWxlbmRyYTwvZm9udD4NCg==
--=_alternative 0033880E65256FAA_=--


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

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

--===============0628733655==--



From mmusic-bounces@ietf.org  Wed Feb 16 06:52:42 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28732
	for <mmusic-web-archive@ietf.org>; Wed, 16 Feb 2005 06:52:42 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1O4o-0001GX-77
	for mmusic-web-archive@ietf.org; Wed, 16 Feb 2005 07:14:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1Nge-0000Pa-LQ; Wed, 16 Feb 2005 06:49:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1NZN-0006aV-Pd
	for mmusic@megatron.ietf.org; Wed, 16 Feb 2005 06:42:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27794
	for <mmusic@ietf.org>; Wed, 16 Feb 2005 06:42:10 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1Nub-0000wq-Hc
	for mmusic@ietf.org; Wed, 16 Feb 2005 07:04:11 -0500
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:53681)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1D1NYi-0006Gn-1D; Wed, 16 Feb 2005 11:41:32 +0000
In-Reply-To: <BBF29C9B95E52E4DB5C29A0ACC94E83B016A9D7A@ac-exch1.eu.scansoft.com>
References: <BBF29C9B95E52E4DB5C29A0ACC94E83B016A9D7A@ac-exch1.eu.scansoft.com>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <a75ad535f522895f6dfa57d06942a6c6@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] FW: [Speechsc] IANA considerations for group feedback
Date: Wed, 16 Feb 2005 11:41:28 +0000
To: "Reifenrath, Klaus" <Klaus.Reifenrath@Scansoft.com>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 43317e64100dd4d87214c51822b582d1
Content-Transfer-Encoding: 7bit
Cc: "'van@packetdesign.com'" <van@packetdesign.com>,
        "'M.Handley@cs.ucl.ac.uk'" <M.Handley@cs.ucl.ac.uk>,
        "'mmusic@ietf.org'" <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b8f3559805f7873076212d6f63ee803e
Content-Transfer-Encoding: 7bit

Section 8.2.1 of sdp-new-23 states that the "control" top-level media 
type is not registered, and SHOULD NOT be used:

    Note: The media types "control" and "data" were listed as valid in
    the previous version of this specification [6], however their
    semantics were never fully specified and they are not widely used.
    These media types have been removed in this specification, although
    they still remain valid media type capabilities for a SIP user agent
    as defined in RFC 3840 [23].  If these media types are considered
    useful in future, a Standards Track RFC MUST be produced to document
    their use.  Until that is done, applications SHOULD NOT use these
    types and SHOULD NOT declare support for them in SIP capabilities
    declarations (even though they exist in the registry created by RFC
    3840).

If you wish to use a subtype of the "control" media type, then you will 
need to produce a standards track RFC defining the "control" top-level 
MIME type, then register a subtype for MRCPv2 in the IANA 
considerations section of the MRCPv2 draft.

Colin


On 9 Feb 2005, at 15:28, Reifenrath, Klaus wrote:
> Hi mmusic WG!
>
> For MRCPv2 the speechsc WG likes to use the media type "control" and
> believes to have a good use case for it.
>> From my understanding of
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-new-23.txt 
> we do
> not need to register "control", but would still need to have an IANA 
> section on this in our spec. What do you think?
>
> Thanks,
> Klaus
>
>
> -----Original Message-----
> From: Dan Burnett [mailto:dan_burnett2000@yahoo.com]
> Sent: Mittwoch, 9. Februar 2005 16:02
> To: David R Oran; Sarvi Shanmugham
> Cc: 'ThomasGal@LumenVox.com'; speechsc@ietf.org; Reifenrath, Klaus
> Subject: Re: [Speechsc] IANA considerations for group feedback
>
>
> Just to be clear, there are no IANA considerations
> here, right?  The "control" type exists and we do not
> need to request any sort of registration because of
> our documented use, right?
>
> --- David R Oran <oran@cisco.com> wrote:
>
>>
>> On Jan 27, 2005, at 12:57 PM, Sarvi Shanmugham
>> wrote:
>>
>>>  Which is exactly what is being done here.
>>>
>>>  So we are fine.
>>>
>> Yes, I agree this is fine.
>>
>>>  Sarvi
>>>  Reifenrath, Klaus wrote:
>>> Quoting from
>>>
>>
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-new-23.txt:
>>>    Note: The media types "control" and "data" were
>> listed as valid in
>>>    the previous version of this specification [6],
>> however their
>>>    semantics were never fully specified and they
>> are not widely used.
>>>    These media types have been removed in this
>> specification, although
>>>    they still remain valid media type capabilities
>> for a SIP user agent
>>>    as defined in RFC 3840 [23].  If these media
>> types are considered
>>>    useful in future, a Standards Track RFC MUST be
>> produced to document
>>>    their use.  Until that is done, applications
>> SHOULD NOT use these
>>>    types and SHOULD NOT declare support for them
>> in SIP capabilities
>>>    declarations (even though they exist in the
>> registry created by RFC
>>>    3840).
>>>
>>> -----Original Message-----
>>> From: Thomas Gal [ mailto:ThomasGal@LumenVox.com ]
>>> Sent: Mittwoch, 26. Januar 2005 20:48
>>> To: 'Dan Burnett'; 'Reifenrath, Klaus'
>>> Cc: speechsc@ietf.org
>>> Subject: RE: [Speechsc] IANA considerations for
>> group feedback
>>>
>>>
>>>  inlinemmusic@ietf.org
>>>
>>> -Tom
>>>
>>>  thomasgal@lumenvox.com
>>>
>>>
>>> -----Original Message-----
>>> From: speechsc-bounces@ietf.org
>>> [ mailto:speechsc-bounces@ietf.org ] On Behalf Of
>> Dan Burnett
>>> Sent: Wednesday, January 26, 2005 10:15 AM
>>> To: Reifenrath, Klaus
>>> Cc: speechsc@ietf.org
>>> Subject: RE: [Speechsc] IANA considerations for
>> group feedback
>>>
>>> I agree that there needs to be an registration of
>>> application/x-nlsml (or, as an email from Tom
>> pointed out,
>>> application/nlsml).  Technically it should be in a
>> separate
>>> RFC from MRCP, but I can include it in the draft
>> if there are
>>> no objections.
>>>
>>>
>>> I would certainly agree with not using
>> "application/nlsml" but
>>> something
>>> similar to obviate confusion, even mrcp-nlsml or
>> something.
>>>
>>>
>>> If "control" is already registered, do we need to
>> do it?  In
>>> short, it's not clear to me in which
>>> namespace(s) the SDP items you mention should be
>> registered.
>>> Are they new namespaces for MRCP or are there
>> existing
>>> namespaces to which the items should be added?
>>>
>>>
>>> Isn't MRCPv2 "control"? I would guess control is
>> too ambiguous and
>>> probably
>>> why it's being deprecated.
>>>
>>> -Tom
>>>
>>> _______________________________________________
>>> Speechsc mailing list
>>>  Speechsc@ietf.org
>>>  https://www1.ietf.org/mailman/listinfo/speechsc
>>>
>>>
>>>
>>>  _______________________________________________
>>> Speechsc mailing list
>>> Speechsc@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/speechsc
>>>
>> David R. Oran
>> Cisco Fellow
>> Cisco Systems
>> 7 Ladyslipper Lane
>> Acton, MA 01720 USA
>> Tel: +1 978 264 2048
>> Email: oran@cisco.com
>>
>> _______________________________________________
>> Speechsc mailing list
>> Speechsc@ietf.org
>> https://www1.ietf.org/mailman/listinfo/speechsc
>>
>
>
>
> 		
> __________________________________
> Do you Yahoo!?
> Meet the all-new My Yahoo! - Try it today!
> http://my.yahoo.com
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
>


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


From mmusic-bounces@ietf.org  Wed Feb 16 07:02:36 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29753
	for <mmusic-web-archive@ietf.org>; Wed, 16 Feb 2005 07:02:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1OEN-0001Wx-FV
	for mmusic-web-archive@ietf.org; Wed, 16 Feb 2005 07:24:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1Ngt-0000Qv-Of; Wed, 16 Feb 2005 06:49:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1NdX-0007ow-GJ
	for mmusic@megatron.ietf.org; Wed, 16 Feb 2005 06:46:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28135
	for <mmusic@ietf.org>; Wed, 16 Feb 2005 06:46:28 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1Nym-00014U-F6
	for mmusic@ietf.org; Wed, 16 Feb 2005 07:08:28 -0500
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:53704)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1D1Nci-0006pr-Aw; Wed, 16 Feb 2005 11:45:40 +0000
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF0174B8C7@zrc2hxm0.corp.nortel.com>
References: <1ECE0EB50388174790F9694F77522CCF0174B8C7@zrc2hxm0.corp.nortel.com>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <f912a344a7d9f3ceefcbe8a2512b447c@csperkins.org>
Content-Transfer-Encoding: quoted-printable
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] WGLC: draft-ietf-mmusic-sdp-new-23.txt
Date: Wed, 16 Feb 2005 11:45:35 +0000
To: "Francois Audet" <audet@nortel.com>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Content-Transfer-Encoding: quoted-printable
Cc: "'Cullen Jennings'" <fluffy@cisco.com>,
        "'mmusic@ietf.org'" <mmusic@ietf.org>,
        "'M.Handley@cs.ucl.ac.uk'" <M.Handley@cs.ucl.ac.uk>,
        "'Joerg Ott'" <jo@tzi.uni-bremen.de>,
        "'van@packetdesign.com'" <van@packetdesign.com>,
        "'Stephen Casner'" <casner@acm.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Content-Transfer-Encoding: quoted-printable

There have been no objections, so I will make this change and submit=20
-24 before the deadline.

Colin


On 7 Feb 2005, at 18:50, Francois Audet wrote:

>
>
> Here is the exact proposal. Changes starts at line with the "->".
>
> In the definition of <port>, add the following text to the fist=20
> paragraph,
> after the reference to [21]:
>
> =A0=A0=A0=A0=A0=A0=A0 If non-contiguous ports are used or if they =
don't follow the=20
> parity
> =A0=A0=A0=A0=A0=A0=A0 rule of even RTP ports and odd RTCP ports, the =
"a=3Drtcp:"=20
> attribute
> =A0=A0=A0=A0=A0 MUST be used. Applications that are requested to send =
media to a=20
> <port>
> =A0=A0=A0=A0=A0=A0=A0 that is odd and where the "a=3Drtcp:" is present =
MUST NOT=20
> substract 1
> =A0=A0=A0=A0=A0=A0=A0 to the RTP port: i.e, they MUST send the RTP to =
the port=20
> indicated
> =A0=A0=A0=A0=A0=A0=A0 in <port> and send the RTCP to the port =
indicated in the=20
> "a=3Drtcp"
> =A0=A0=A0=A0=A0=A0=A0 attribute.
> =A0=A0=A0=A0
> Cheers.
> =A0
>
> > -----Original Message-----
> > From: Colin Perkins [mailto:csp@csperkins.org]
> > Sent: Sunday, February 06, 2005 09:05
> > To: Francois Audet
> > Cc: 'M.Handley@cs.ucl.ac.uk'; 'Cullen Jennings'; 'Joerg Ott';
> > 'van@packetdesign.com'; 'Stephen Casner'; 'mmusic@ietf.org'
> > Subject: Re: [MMUSIC] WGLC: draft-ietf-mmusic-sdp-new-23.txt
> >
> >
> > Francois,
> >
> > [Apologies for the slow response...]
> >
> > On 20 Dec 2004, at 00:33, Francois Audet wrote:
> > > I would like to request a clarification in section 5.14 of=A0
> > > draft-ietf-mmusic-sdp-new-23.
> > >
> > > As we discovered in BEHAVE, certain SDP implementations are
> > > misinterpretting RFC 3550 section 11 2nd paragraph. In a SIP
> > > Offer/Answer for example, these implementations
>  > unilaterally change an
> > > odd RTP port indicated in an SDP (from the other end) with
> > to the even
> > > port that one lower. In other words, if the other end
> > indicates an RTP
> > > port of 5201, these implemenations will send RTP to 5200,
> > which will
> > > be a big problem.
> > >
> > > Note that this issue is slightly orthogonal to the use of the rtcp
> > > attribute of RFC 3605. For example, if an application
> > discovers (with
> > > STUN or ICE) that its RTP port is 5201, it may then
> > discover that it's
> > > RTCP port is 5202 (which would satisfy the contiguity
> > rule). This is
>  > > very likely to happen because NATs typically assign ports
> > > sequentially. An application could (somewhat foolishlingly) not =
use
> > > RFC 3605 in this case because it follows the contiguity
> > rule (but not
>  > > the parity rule).
> > >
> > > Another issue is for implementations that do not support RTCP in=20=

> the
> > > first place.
> > >
> > > In order to avoid these problems, I propose that we explicitly=20
> state
> > > that=A0 the <port> for RTP indicates the actual port and MUST not =
be
> > > changed regardless of parity (i.e., DO NOT substract 1 if
> > it is odd).
> > >
> > > I believe that would finally put to rest this parity issue
> > for all SDP
> > > based protocols.
> >
> > What is the *exact* wording change you are proposing?
> >
> > > Also, on a similar note, would it make sense to incorporate RFC=20
> 3605
> > > (the=A0 directly into sdp-new, instead of having it stand as
> > a separate
> > > RFC) and make its support mandatory? The biggest problem
> > with RFC 3605
> > > is that I can do the best SIP/SDP implementation possible, support
> > > STUN, ICE, 3605 and all, but if the other end doesn't support 3605
> > > (because they don't even know of NATs), the problem above
> > will still
> > > occur.
> >
> > We don't mandate support for any of the attributes in SDP-new, so I
> > don't see any real benefit to including the RFC 3605 ("a=3Drtcp:")
> > attribute into the main SDP specification at this time.
> >
> > Colin
> >
> >
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic


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


From mmusic-bounces@ietf.org  Wed Feb 16 09:58:48 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17530
	for <mmusic-web-archive@ietf.org>; Wed, 16 Feb 2005 09:58:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1Qyv-0006U0-9b
	for mmusic-web-archive@ietf.org; Wed, 16 Feb 2005 10:20:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1Qcf-00055d-MS; Wed, 16 Feb 2005 09:57:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1QUF-0002b3-JZ
	for mmusic@megatron.ietf.org; Wed, 16 Feb 2005 09:49:07 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15926
	for <mmusic@ietf.org>; Wed, 16 Feb 2005 09:49:02 -0500 (EST)
Received: from mailhost1.aepona.com ([194.46.24.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1QpS-00060z-JG
	for mmusic@ietf.org; Wed, 16 Feb 2005 10:11:03 -0500
Received: from gyda ([10.10.12.242])
	by mailhost1.aepona.com with esmtp (Exim 4.24) id 1D1QU7-0008E7-2A
	for mmusic@ietf.org; Wed, 16 Feb 2005 14:48:59 +0000
Message-ID: <42135D5B.7050402@aepona.com>
Date: Wed, 16 Feb 2005 14:48:59 +0000
From: Steven Egan <Steven.Egan@aepona.com>
Organization: Aepona Ltd.
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.7.2) Gecko/20040805 Netscape/7.2
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mmusic@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] 3PCC mute of call leg
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit

Hi,
I am looking to implement the following:

1. Application initiates 2 party call (3PCC)
2. Both UA1 and UA2 are in a voice call
3. Application mutes UA2 (so it cannot send or receive media)
4. Application allows UA2 back into the call

Everything for step 1 and 2 works fine.  With step 3, I am sending a 
re-invite to UA2 containing an SDP of the format:


v=0
o=UserAgent 2462 2442 IN IP4 192.168.25.13
s=SIP Call
c=IN IP4 192.168.25.13
t=0 0
m=audio 18302 RTP/AVP 0 19
c=IN IP4 0.0.0.0
a=rtpmap:0 PCMU/8000
a=rtpmap:19 CN/8000
a=ptime:20

When I send this to a Cisco 7960 SIP phone, it puts the UA on hold (so 
it neither receives or sends media), which is what I am looking for. 
However, when I use the same method to mute a user agent using the Cisco 
AS5350, the UA cannot transmit but can receive media.
What is the standard method of muting a UA in 3PCC, so that the UA 
cannot send or receive media.
Cheers,
Steven


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


From mmusic-bounces@ietf.org  Wed Feb 16 14:49:25 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10690
	for <mmusic-web-archive@ietf.org>; Wed, 16 Feb 2005 14:49:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1VWB-000738-Kf
	for mmusic-web-archive@ietf.org; Wed, 16 Feb 2005 15:11:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1TY7-0002Sf-7x; Wed, 16 Feb 2005 13:05:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1S1P-0008Ek-2h
	for mmusic@megatron.ietf.org; Wed, 16 Feb 2005 11:27:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11297
	for <mmusic@ietf.org>; Wed, 16 Feb 2005 11:27:23 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1SMf-0004s9-U4
	for mmusic@ietf.org; Wed, 16 Feb 2005 11:49:26 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 16 Feb 2005 08:38:26 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.90,89,1107763200"; 
	d="scan'208"; a="614996805:sNHT27505396"
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j1GGQfTj029156;
	Wed, 16 Feb 2005 08:26:41 -0800 (PST)
Received: from cisco.com ([161.44.79.182]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id APE19061; Wed, 16 Feb 2005 11:26:40 -0500 (EST)
Message-ID: <4213743F.8080007@cisco.com>
Date: Wed, 16 Feb 2005 11:26:39 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Steven Egan <Steven.Egan@aepona.com>
Subject: Re: [MMUSIC] 3PCC mute of call leg
References: <42135D5B.7050402@aepona.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit
Cc: mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit



Steven Egan wrote:
> Hi,
> I am looking to implement the following:
> 
> 1. Application initiates 2 party call (3PCC)
> 2. Both UA1 and UA2 are in a voice call
> 3. Application mutes UA2 (so it cannot send or receive media)
> 4. Application allows UA2 back into the call
> 
> Everything for step 1 and 2 works fine.  With step 3, I am sending a 
> re-invite to UA2 containing an SDP of the format:
> 
> 
> v=0
> o=UserAgent 2462 2442 IN IP4 192.168.25.13
> s=SIP Call
> c=IN IP4 192.168.25.13
> t=0 0
> m=audio 18302 RTP/AVP 0 19
> c=IN IP4 0.0.0.0
> a=rtpmap:0 PCMU/8000
> a=rtpmap:19 CN/8000
> a=ptime:20
> 
> When I send this to a Cisco 7960 SIP phone, it puts the UA on hold (so 
> it neither receives or sends media), which is what I am looking for. 
> However, when I use the same method to mute a user agent using the Cisco 
> AS5350, the UA cannot transmit but can receive media.

The offer and the answer each specify one direction. Your offer prevents 
media from flowing in one direction - in this case from the AS5350. It 
does not prevent it from flowing toward the AS5350, nor does it say what 
that device should do with any media it might receive.

If you want to prevent a flow in the other direction, you will need to 
send a reinvite to the other endpoint, blocking the flow from it.

> What is the standard method of muting a UA in 3PCC, so that the UA 
> cannot send or receive media.

The use of "c=IN IP4 0.0.0.0" is no longer preferred for hold. The 
preferred for one-way hold is to a=sendonly to one side and a=recvonly 
to the other side. For a two-way hold, a=inactive to both sides would be 
preferred. You *might* get away with sending a=inactive to one side, but 
I wouldn't count on it.

That of course depends on whether the devices you are using support 
that. I don't know if these particular devices do.

	Paul

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


From mmusic-bounces@ietf.org  Wed Feb 16 17:50:41 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06443
	for <mmusic-web-archive@ietf.org>; Wed, 16 Feb 2005 17:50:41 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1YLe-0005m7-Jg
	for mmusic-web-archive@ietf.org; Wed, 16 Feb 2005 18:12:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1Xpc-0004tb-Nh; Wed, 16 Feb 2005 17:39:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1XkM-0002N0-Mc
	for mmusic@megatron.ietf.org; Wed, 16 Feb 2005 17:34:14 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04985
	for <mmusic@ietf.org>; Wed, 16 Feb 2005 17:34:11 -0500 (EST)
Received: from smtp107.mail.sc5.yahoo.com ([66.163.169.227])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D1Y5g-0005JE-Fq
	for mmusic@ietf.org; Wed, 16 Feb 2005 17:56:17 -0500
Received: from unknown (HELO ?127.0.0.1?) (arvy?n@68.36.202.68 with plain)
	by smtp107.mail.sc5.yahoo.com with SMTP; 16 Feb 2005 22:34:11 -0000
Message-ID: <4213CA76.9050807@yahoo.com>
Date: Wed, 16 Feb 2005 17:34:30 -0500
From: Aravind Narasimhan <arvy_n@yahoo.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.8a5) Gecko/20041122
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mmusic@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] RTSP connections question.
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit

Section 9.3 of rtsp-bis08 indicates the following:

> A server SHOULD NOT initiate a close of a connection directly after 
> responding to a TEARDOWN request for the whole session. A server 
> SHOULD NOT close the connection as a result of responding to a request 
> with an error code. Doing this would prevent or result in extra 
> overhead for the client when testing advanced or special types of 
> requests.


But this seems like a DoS security risk.  If a malicious user decided to 
send gibberish request or request that are almost correct and but not 
quite, the server may respond with an error code because it can't parse 
the request.  But if it cannot close its connection to the client, then 
the client may overload the server with many gibberish requests and 
eventually cause the server to not accept valid connections. 

What is the purpose of saying that the server SHOULD NOT close the 
connection as a result of responding to a request with an error code?  
It seems like it would be the right thing to do, no?

Aravind




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


From mmusic-bounces@ietf.org  Wed Feb 16 18:42:14 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12800
	for <mmusic-web-archive@ietf.org>; Wed, 16 Feb 2005 18:42:14 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1Z9X-0007Iq-VV
	for mmusic-web-archive@ietf.org; Wed, 16 Feb 2005 19:04:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1Yjw-0003aj-LZ; Wed, 16 Feb 2005 18:37:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1YbV-0008Uh-LS
	for mmusic@megatron.ietf.org; Wed, 16 Feb 2005 18:29:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11233
	for <mmusic@ietf.org>; Wed, 16 Feb 2005 18:29:06 -0500 (EST)
Received: from auds953.usa.alcatel.com ([143.209.238.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1Ywp-0006qf-Ty
	for mmusic@ietf.org; Wed, 16 Feb 2005 18:51:13 -0500
Received: from srsdmail01.PVNS.COM (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id
	j1GNSZfp023693; Wed, 16 Feb 2005 17:28:36 -0600 (CST)
X-MIMEOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] RTSP connections question.
Date: Wed, 16 Feb 2005 15:28:35 -0800
Message-ID: <758B5A159B385447B4F950DE72D7D7AD678CC5@srsdmail01.PVNS.COM>
Thread-Topic: [MMUSIC] RTSP connections question.
Thread-Index: AcUUefuM3la0Esf3SBOUq44JavmB2wAADS2Q
From: "Thomas Zeng" <zeng@pvnetsolutions.com>
To: "Aravind Narasimhan" <arvy_n@yahoo.com>, <mmusic@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: quoted-printable
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: quoted-printable



-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org]On Behalf
Of Aravind Narasimhan
Sent: Wednesday, February 16, 2005 2:35 PM
To: mmusic@ietf.org
Subject: [MMUSIC] RTSP connections question.


Section 9.3 of rtsp-bis08 indicates the following:

> A server SHOULD NOT initiate a close of a connection directly after=20
> responding to a TEARDOWN request for the whole session. A server=20
> SHOULD NOT close the connection as a result of responding to a request =

> with an error code. Doing this would prevent or result in extra=20
> overhead for the client when testing advanced or special types of=20
> requests.


But this seems like a DoS security risk.  If a malicious user decided to =

send gibberish request or request that are almost correct and but not=20
quite, the server may respond with an error code because it can't parse=20
the request.  But if it cannot close its connection to the client, then=20
the client may overload the server with many gibberish requests and=20
eventually cause the server to not accept valid connections.=20

[tz] My understanding is that the server has the freedom to include the =
"Connection: close" header if it suspects that the client is launching a =
DoS attack and wants to close the connection after the current =
request/response is complete. See Section 12.10 of RFC2326.

What is the purpose of saying that the server SHOULD NOT close the=20
connection as a result of responding to a request with an error code? =20
It seems like it would be the right thing to do, no?

Aravind




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

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


From mmusic-bounces@ietf.org  Wed Feb 16 20:26:53 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22375
	for <mmusic-web-archive@ietf.org>; Wed, 16 Feb 2005 20:26:53 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1amp-0001ff-Dh
	for mmusic-web-archive@ietf.org; Wed, 16 Feb 2005 20:49:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1aQO-0003Uw-AK; Wed, 16 Feb 2005 20:25:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1aP8-00033n-Ky
	for mmusic@megatron.ietf.org; Wed, 16 Feb 2005 20:24:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22207
	for <mmusic@ietf.org>; Wed, 16 Feb 2005 20:24:27 -0500 (EST)
Received: from [220.117.193.39] (helo=lapis1.nextreaming.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1akT-0001bu-5r
	for mmusic@ietf.org; Wed, 16 Feb 2005 20:46:34 -0500
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] RTSP connections question.
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Thu, 17 Feb 2005 10:24:18 +0900
Message-ID: <F288EC559B515A43816F0ED831EBE50AD30865@lapis1.nextreaming.com>
Thread-Topic: [MMUSIC] RTSP connections question.
thread-index: AcUUefuM3la0Esf3SBOUq44JavmB2wAADS2QAAThbKA=
From: "Jae-Hwan Kim" <kjh1905m@nextreaming.com>
To: "Thomas Zeng" <zeng@pvnetsolutions.com>,
        "Aravind Narasimhan" <arvy_n@yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: quoted-printable
Cc: mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: quoted-printable

> Section 9.3 of rtsp-bis08 indicates the following:
> > A server SHOULD NOT initiate a close of a connection directly after
> > responding to a TEARDOWN request for the whole session. A server
> > SHOULD NOT close the connection as a result of responding to a
request
> > with an error code. Doing this would prevent or result in extra
> > overhead for the client when testing advanced or special types of
> > requests.
>=20
> But this seems like a DoS security risk.  If a malicious user decided
to
> send gibberish request or request that are almost correct and but not
> quite, the server may respond with an error code because it can't
parse
> the request.  But if it cannot close its connection to the client,
then
> the client may overload the server with many gibberish requests and
> eventually cause the server to not accept valid connections.
>=20
> [tz] My understanding is that the server has the freedom to include
the
> "Connection: close" header if it suspects that the client is launching
a DoS
> attack and wants to close the connection after the current
request/response is
> complete. See Section 12.10 of RFC2326.
[Jae-Hwan Kim] "Connection: close" seems to be used, even when the
server waits RTSP timeout after the completion of TEARDOWN response; it
seems not to mean direct disconnection. In case of DoS, IMO, this is
good point-out and the above context of rtsp-bis08 is a recommendation
so that server may behave bravely.
>=20
> What is the purpose of saying that the server SHOULD NOT close the
> connection as a result of responding to a request with an error code?
> It seems like it would be the right thing to do, no?
[Jae-Hwan Kim] I think "460 Only aggregate operation allowed" is a good
example. There is no way for client to know whether server supports
non-aggregate control except negotiation.
>=20
> Aravind


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


From mmusic-bounces@ietf.org  Thu Feb 17 10:02:03 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02142
	for <mmusic-web-archive@ietf.org>; Thu, 17 Feb 2005 10:02:03 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1nVn-0005dO-AK
	for mmusic-web-archive@ietf.org; Thu, 17 Feb 2005 10:24:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1mv0-0000H9-7q; Thu, 17 Feb 2005 09:46:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1mnT-00056i-BY
	for mmusic@megatron.ietf.org; Thu, 17 Feb 2005 09:38:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29215
	for <mmusic@ietf.org>; Thu, 17 Feb 2005 09:38:26 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1n8w-0004wv-0r
	for mmusic@ietf.org; Thu, 17 Feb 2005 10:00:39 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j1HEcOh5015915
	for <mmusic@ietf.org>; Thu, 17 Feb 2005 15:38:24 +0100 (MET)
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 17 Feb 2005 15:38:57 +0100
Received: from [147.214.237.66] (pci [147.214.237.66]) by
	esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id 1ZVZ810H; Thu, 17 Feb 2005 15:38:24 +0100
Message-ID: <4214AC5F.9000707@ericsson.com>
Date: Thu, 17 Feb 2005 15:38:23 +0100
X-Sybari-Trust: dd263448 b8ec86c7 2ba70a45 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Aravind Narasimhan <arvy_n@yahoo.com>
Subject: Re: [MMUSIC] RTSP connections question.
References: <4213CA76.9050807@yahoo.com>
In-Reply-To: <4213CA76.9050807@yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 17 Feb 2005 14:38:57.0609 (UTC)
	FILETIME=[699D4390:01C514FE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
Cc: mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit

Aravind Narasimhan wrote:
> Section 9.3 of rtsp-bis08 indicates the following:
> 
>> A server SHOULD NOT initiate a close of a connection directly after 
>> responding to a TEARDOWN request for the whole session. A server 
>> SHOULD NOT close the connection as a result of responding to a request 
>> with an error code. Doing this would prevent or result in extra 
>> overhead for the client when testing advanced or special types of 
>> requests.
> 
> 
> 
> But this seems like a DoS security risk.  If a malicious user decided to 
> send gibberish request or request that are almost correct and but not 
> quite, the server may respond with an error code because it can't parse 
> the request.  But if it cannot close its connection to the client, then 
> the client may overload the server with many gibberish requests and 
> eventually cause the server to not accept valid connections.
> What is the purpose of saying that the server SHOULD NOT close the 
> connection as a result of responding to a request with an error code?  
> It seems like it would be the right thing to do, no?
> 

I agree that this is a risk, however there is a clearly trade off here. 
If you are very aggressive and treats all errors as an attack and boots 
the client, then you could easily boot clients that is trying something 
special that the server doesn't understand but is correct. If you go the 
other way then, you will be more vulnerable to attacks.

This is very similar to the TCP overload attack. You need to accept a 
TCP connections to be able to serve anyone, however if someone is trying 
to overload you using TCP connects, the server will need to block some 
of the request.

So this is something that needs to be included in the security 
consideration section as a possible venue of attack that needs to be 
handled by the server implementation.

Cheers

Magnus Westerlund

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

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


From mmusic-bounces@ietf.org  Thu Feb 17 13:08:22 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09819
	for <mmusic-web-archive@ietf.org>; Thu, 17 Feb 2005 13:08:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1qQA-0000On-4e
	for mmusic-web-archive@ietf.org; Thu, 17 Feb 2005 13:30:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1nPP-0004b2-Dn; Thu, 17 Feb 2005 10:17:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1nCQ-0007aq-6r; Thu, 17 Feb 2005 10:04:14 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02449;
	Thu, 17 Feb 2005 10:04:12 -0500 (EST)
Message-Id: <200502171504.KAA02449@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 17 Feb 2005 10:04:12 -0500
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-securityprecondition-00.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

	Title		: Security Preconditions for Session Description Protocol Media Streams
	Author(s)	: F. Andreasen, D. Wing
	Filename	: draft-ietf-mmusic-securityprecondition-00.txt
	Pages		: 13
	Date		: 2005-2-16
	
This document defines a new security precondition for the Session 
   Description Protocol precondition framework described in RFC 3312.  
   A security precondition can be used to delay session establishment 
   or modification until media stream security has been negotiated 
   successfully.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-securityprecondition-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-mmusic-securityprecondition-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-mmusic-securityprecondition-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: <2005-2-17102522.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-securityprecondition-00.txt

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

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


--OtherAccess--

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

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

--NextPart--





From mmusic-bounces@ietf.org  Thu Feb 17 17:01:31 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12861
	for <mmusic-web-archive@ietf.org>; Thu, 17 Feb 2005 17:01:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1u3l-0001Yd-Lv
	for mmusic-web-archive@ietf.org; Thu, 17 Feb 2005 17:23:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1sMe-0008Fv-K3; Thu, 17 Feb 2005 15:35:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1qea-0000r3-89
	for mmusic@megatron.ietf.org; Thu, 17 Feb 2005 13:45:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18600
	for <mmusic@ietf.org>; Thu, 17 Feb 2005 13:45:29 -0500 (EST)
Received: from smtp102.mail.sc5.yahoo.com ([216.136.174.140])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D1r05-00030Y-JQ
	for mmusic@ietf.org; Thu, 17 Feb 2005 14:07:46 -0500
Received: from unknown (HELO ?127.0.0.1?) (arvy?n@68.36.202.68 with plain)
	by smtp102.mail.sc5.yahoo.com with SMTP; 17 Feb 2005 18:45:29 -0000
Message-ID: <4214E651.9040205@yahoo.com>
Date: Thu, 17 Feb 2005 13:45:37 -0500
From: Aravind Narasimhan <arvy_n@yahoo.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.8a5) Gecko/20041122
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mmusic@ietf.org
Subject: Re: [MMUSIC] RTSP connections question.
References: <4213CA76.9050807@yahoo.com> <4214AC5F.9000707@ericsson.com>
In-Reply-To: <4214AC5F.9000707@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: 7bit
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: 7bit

Great answers folks.  I will try to work some of the background and 
rationale for the recommendation into the spec.  Now I wonder if we need 
to do something to try to actively prevent DoS in this scenario?  I'll 
think about this a bit, but I dont have an answer yet.

Aravind

Magnus Westerlund wrote:

> Aravind Narasimhan wrote:
>
>> Section 9.3 of rtsp-bis08 indicates the following:
>>
>>> A server SHOULD NOT initiate a close of a connection directly after 
>>> responding to a TEARDOWN request for the whole session. A server 
>>> SHOULD NOT close the connection as a result of responding to a 
>>> request with an error code. Doing this would prevent or result in 
>>> extra overhead for the client when testing advanced or special types 
>>> of requests.
>>
>>
>>
>>
>> But this seems like a DoS security risk.  If a malicious user decided 
>> to send gibberish request or request that are almost correct and but 
>> not quite, the server may respond with an error code because it can't 
>> parse the request.  But if it cannot close its connection to the 
>> client, then the client may overload the server with many gibberish 
>> requests and eventually cause the server to not accept valid 
>> connections.
>> What is the purpose of saying that the server SHOULD NOT close the 
>> connection as a result of responding to a request with an error 
>> code?  It seems like it would be the right thing to do, no?
>>
>
> I agree that this is a risk, however there is a clearly trade off 
> here. If you are very aggressive and treats all errors as an attack 
> and boots the client, then you could easily boot clients that is 
> trying something special that the server doesn't understand but is 
> correct. If you go the other way then, you will be more vulnerable to 
> attacks.
>
> This is very similar to the TCP overload attack. You need to accept a 
> TCP connections to be able to serve anyone, however if someone is 
> trying to overload you using TCP connects, the server will need to 
> block some of the request.
>
> So this is something that needs to be included in the security 
> consideration section as a possible venue of attack that needs to be 
> handled by the server implementation.
>
> Cheers
>
> Magnus Westerlund
>
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>
>



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


From mmusic-bounces@ietf.org  Thu Feb 17 17:10:44 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14488
	for <mmusic-web-archive@ietf.org>; Thu, 17 Feb 2005 17:10:44 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1uCj-000245-Ch
	for mmusic-web-archive@ietf.org; Thu, 17 Feb 2005 17:33:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1teO-0002Ng-3h; Thu, 17 Feb 2005 16:57:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1rs1-00006n-2H
	for mmusic@megatron.ietf.org; Thu, 17 Feb 2005 15:03:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27782
	for <mmusic@ietf.org>; Thu, 17 Feb 2005 15:03:27 -0500 (EST)
Received: from smtp107.mail.sc5.yahoo.com ([66.163.169.227])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D1sDV-0005qW-8a
	for mmusic@ietf.org; Thu, 17 Feb 2005 15:25:42 -0500
Received: from unknown (HELO ?127.0.0.1?) (arvy?n@68.36.202.68 with plain)
	by smtp107.mail.sc5.yahoo.com with SMTP; 17 Feb 2005 20:03:23 -0000
Message-ID: <4214F897.4040909@yahoo.com>
Date: Thu, 17 Feb 2005 15:03:35 -0500
From: Aravind Narasimhan <arvy_n@yahoo.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.8a5) Gecko/20041122
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mmusic@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Another RTSP Connection close question
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit

Hey folks,

rtsp-bis08, section 9.3 says the following:

> A server SHOULD NOT initiate a close of a connection directly after 
> responding to a TEARDOWN request for the whole session.

Does anybody have a suggestion for what a server SHOULD do?  Should it 
wait for the RTSP session timeout period (60s)?  That doesn't make sense 
to me because the session doesn't exist after the TEARDOWN request is 
complete.  Should it wait for 10s?  It's a random number but has its 
basis in the amount of time a client should wait before it should expect 
the server to not answer (Section 9.4).  Should the server reply back 
somehow with at header which indicates how long the server is willing to 
wait before it closes the connection?  The Session header w/ timeout 
parameter is not going to be useful, because no session would exist.

Two more issues:

    * A client may be using the same connection to control multiple RTSP
      sessions on the server.  So we need to be careful about wording
      that implicitly indicates a one-to-one relationship between
      connections and RTSP sessions where there is none.
    * What happens if a client tries to establish another RTSP session
      through the same connection while the server is about to close the
      connection.  There is a  race condition here that could
      potentially lead to incompatibilities. 

I'm of the opinion that the wording should be the following:

A server SHOULD NOT close a connection immediately after responding to a 
session-level TEARDOWN request for the last RTSP session being 
controlled through the connection.  Instead, it should wait for a 
reasonable amount of time for the client to receive the TEARDOWN 
response, take appropriate action, and initiate the connection closing.  
The server SHOULD wait a default amount of 10s after the TEARDOWN 
response to close the connection.

Alternatively,  I think it's best if the server closes the connection 
after a TEARDOWN when it realizes that the last RTSP session on the 
connection has been destroyed.

Thoughts?

Aravind




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


From mmusic-bounces@ietf.org  Thu Feb 17 17:37:32 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18651
	for <mmusic-web-archive@ietf.org>; Thu, 17 Feb 2005 17:37:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1uce-000361-K4
	for mmusic-web-archive@ietf.org; Thu, 17 Feb 2005 17:59:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1tkz-000898-3x; Thu, 17 Feb 2005 17:04:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1tJD-0000sz-VM
	for mmusic@megatron.ietf.org; Thu, 17 Feb 2005 16:35:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07762
	for <mmusic@ietf.org>; Thu, 17 Feb 2005 16:35:38 -0500 (EST)
Received: from smtp106.mail.sc5.yahoo.com ([66.163.169.226])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D1tej-00006c-PF
	for mmusic@ietf.org; Thu, 17 Feb 2005 16:57:55 -0500
Received: from unknown (HELO ?127.0.0.1?) (arvy?n@68.36.202.68 with plain)
	by smtp106.mail.sc5.yahoo.com with SMTP; 17 Feb 2005 21:35:35 -0000
Message-ID: <42150E33.4020105@yahoo.com>
Date: Thu, 17 Feb 2005 16:35:47 -0500
From: Aravind Narasimhan <arvy_n@yahoo.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.8a5) Gecko/20041122
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jae-Hwan Kim <kjh1905m@nextreaming.com>
Subject: Re: [MMUSIC] RTSP connections question.
References: <F288EC559B515A43816F0ED831EBE50AD30865@lapis1.nextreaming.com>
In-Reply-To: <F288EC559B515A43816F0ED831EBE50AD30865@lapis1.nextreaming.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Content-Transfer-Encoding: 7bit
Cc: mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Content-Transfer-Encoding: 7bit

Jae-Hwan Kim wrote:

>>Section 9.3 of rtsp-bis08 indicates the following:
>>    
>>
>>>A server SHOULD NOT initiate a close of a connection directly after
>>>responding to a TEARDOWN request for the whole session. A server
>>>SHOULD NOT close the connection as a result of responding to a
>>>      
>>>
>request
>  
>
>>>with an error code. Doing this would prevent or result in extra
>>>overhead for the client when testing advanced or special types of
>>>requests.
>>>      
>>>
>>But this seems like a DoS security risk.  If a malicious user decided
>>    
>>
>to
>  
>
>>send gibberish request or request that are almost correct and but not
>>quite, the server may respond with an error code because it can't
>>    
>>
>parse
>  
>
>>the request.  But if it cannot close its connection to the client,
>>    
>>
>then
>  
>
>>the client may overload the server with many gibberish requests and
>>eventually cause the server to not accept valid connections.
>>
>>[tz] My understanding is that the server has the freedom to include
>>    
>>
>the
>  
>
>>"Connection: close" header if it suspects that the client is launching
>>    
>>
>a DoS
>  
>
>>attack and wants to close the connection after the current
>>    
>>
>request/response is
>  
>
>>complete. See Section 12.10 of RFC2326.
>>    
>>
>[Jae-Hwan Kim] "Connection: close" seems to be used, even when the
>server waits RTSP timeout after the completion of TEARDOWN response; it
>seems not to mean direct disconnection. In case of DoS, IMO, this is
>good point-out and the above context of rtsp-bis08 is a recommendation
>so that server may behave bravely.
>  
>
I will point this out in the spec.

>>What is the purpose of saying that the server SHOULD NOT close the
>>connection as a result of responding to a request with an error code?
>>It seems like it would be the right thing to do, no?
>>    
>>
>[Jae-Hwan Kim] I think "460 Only aggregate operation allowed" is a good
>example. There is no way for client to know whether server supports
>non-aggregate control except negotiation.
>  
>
I do agree that some error messages may require a server to keep the 
connection open, so that the users may try again, but I think we need to 
be more specific about them, so that mainstream servers can protect 
themselves from DoS.

>>Aravind
>>    
>>
>
>
>
>  
>



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


From mmusic-bounces@ietf.org  Thu Feb 17 18:43:45 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25581
	for <mmusic-web-archive@ietf.org>; Thu, 17 Feb 2005 18:43:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1vem-0004kL-FB
	for mmusic-web-archive@ietf.org; Thu, 17 Feb 2005 19:06:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1uMj-0004GG-AY; Thu, 17 Feb 2005 17:43:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1tyE-0006ih-JR
	for mmusic@megatron.ietf.org; Thu, 17 Feb 2005 17:18:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15520
	for <mmusic@ietf.org>; Thu, 17 Feb 2005 17:18:00 -0500 (EST)
Received: from smtp101.mail.sc5.yahoo.com ([216.136.174.139])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D1uJk-0002JN-K5
	for mmusic@ietf.org; Thu, 17 Feb 2005 17:40:18 -0500
Received: from unknown (HELO ?127.0.0.1?) (arvy?n@68.36.202.68 with plain)
	by smtp101.mail.sc5.yahoo.com with SMTP; 17 Feb 2005 22:17:59 -0000
Message-ID: <42151829.90106@yahoo.com>
Date: Thu, 17 Feb 2005 17:18:17 -0500
From: Aravind Narasimhan <arvy_n@yahoo.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.8a5) Gecko/20041122
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Re: [MMUSIC] RTSP connections question.
References: <4213CA76.9050807@yahoo.com> <4214AC5F.9000707@ericsson.com>
In-Reply-To: <4214AC5F.9000707@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit
Cc: mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit

Magnus Westerlund wrote:

> Aravind Narasimhan wrote:
>
>> Section 9.3 of rtsp-bis08 indicates the following:
>>
>>> A server SHOULD NOT initiate a close of a connection directly after 
>>> responding to a TEARDOWN request for the whole session. A server 
>>> SHOULD NOT close the connection as a result of responding to a 
>>> request with an error code. Doing this would prevent or result in 
>>> extra overhead for the client when testing advanced or special types 
>>> of requests.
>>
>>
>>
>>
>> But this seems like a DoS security risk.  If a malicious user decided 
>> to send gibberish request or request that are almost correct and but 
>> not quite, the server may respond with an error code because it can't 
>> parse the request.  But if it cannot close its connection to the 
>> client, then the client may overload the server with many gibberish 
>> requests and eventually cause the server to not accept valid 
>> connections.
>> What is the purpose of saying that the server SHOULD NOT close the 
>> connection as a result of responding to a request with an error 
>> code?  It seems like it would be the right thing to do, no?
>>
>
> I agree that this is a risk, however there is a clearly trade off 
> here. If you are very aggressive and treats all errors as an attack 
> and boots the client, then you could easily boot clients that is 
> trying something special that the server doesn't understand but is 
> correct. If you go the other way then, you will be more vulnerable to 
> attacks.

Maybe the right way to approach this is to have something that indicates 
to the server that you are trying to do something special and that the 
server may not understand it. . .  But I think that with the OPTIONS 
request, and support for feature tags, it should be easy to indicate 
this without having to put a recommendation that the server should not 
close a connection on an error response.  I think it would be better to 
let the server decide what to do on a error response, but indicate the 
pros and cons.  My point is that a "SHOULD NOT" seems too strong.

> This is very similar to the TCP overload attack. You need to accept a 
> TCP connections to be able to serve anyone, however if someone is 
> trying to overload you using TCP connects, the server will need to 
> block some of the request.
>
> So this is something that needs to be included in the security 
> consideration section as a possible venue of attack that needs to be 
> handled by the server implementation.

The question is what does a server do about this?  What is our 
recommendation?

Aravind


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


From mmusic-bounces@ietf.org  Fri Feb 18 03:43:05 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05716
	for <mmusic-web-archive@ietf.org>; Fri, 18 Feb 2005 03:43:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D244l-0001PW-Im
	for mmusic-web-archive@ietf.org; Fri, 18 Feb 2005 04:05:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D23bV-0003GQ-S2; Fri, 18 Feb 2005 03:35:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D23YI-0002CP-N9
	for mmusic@megatron.ietf.org; Fri, 18 Feb 2005 03:31:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04943
	for <mmusic@ietf.org>; Fri, 18 Feb 2005 03:31:53 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D23tu-00012L-Ac
	for mmusic@ietf.org; Fri, 18 Feb 2005 03:54:15 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j1I8VpO6016376 for <mmusic@ietf.org>; Fri, 18 Feb 2005 09:31:51 +0100
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 18 Feb 2005 09:32:26 +0100
Received: from [147.214.34.56] (research-1fd0e1.ki.sw.ericsson.se
	[147.214.34.56]) by esealnt610.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id 18XKRFVA; Fri, 18 Feb 2005 09:35:05 +0100
Message-ID: <4215A7F7.5040108@ericsson.com>
Date: Fri, 18 Feb 2005 09:31:51 +0100
X-Sybari-Trust: 27fd414f b8ec86c7 5fb16dbe 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Aravind Narasimhan <arvy_n@yahoo.com>
Subject: Re: [MMUSIC] RTSP connections question.
References: <42151829.90106@yahoo.com>
In-Reply-To: <42151829.90106@yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Feb 2005 08:32:26.0055 (UTC)
	FILETIME=[600A2D70:01C51594]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit
Cc: mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: 7bit

Hi Aravind

Aravind Narasimhan wrote:
> Magnus Westerlund wrote:
> 
> Maybe the right way to approach this is to have something that indicates 
> to the server that you are trying to do something special and that the 
> server may not understand it. . .  But I think that with the OPTIONS 
> request, and support for feature tags, it should be easy to indicate 
> this without having to put a recommendation that the server should not 
> close a connection on an error response.  I think it would be better to 
> let the server decide what to do on a error response, but indicate the 
> pros and cons.  My point is that a "SHOULD NOT" seems too strong.
>

I agree that we have procedures to check if certain things will happen. 
The problem is that there is a big difference between different types of 
error messages, if some one includes a Require header and you don't 
support a feature and respond with 551 (Option not supported), that is 
clearly a valid usage. However if you respond using the 400 "Bad 
Request" you have a higher risk that you are under attack. I think 
SHOULD NOT is the correct level. However I think we should include a 
reference to the security issues with this recommendation.

> 
>>This is very similar to the TCP overload attack. You need to accept a 
>>TCP connections to be able to serve anyone, however if someone is 
>>trying to overload you using TCP connects, the server will need to 
>>block some of the request.
>>
>>So this is something that needs to be included in the security 
>>consideration section as a possible venue of attack that needs to be 
>>handled by the server implementation.
> 
> 
> The question is what does a server do about this?  What is our 
> recommendation?
> 

I think the common case, is that a server should monitor the situation, 
and if it determines if it is under a deliberate attack, in particular 
if there is many different sessions that receives garbage messages, then 
the server can be more harsh against errors. The server should also 
consider the strength of different error messages, as I pointed out in 
the above paragraph.

Cheers

Magnus Westerlund

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

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


From mmusic-bounces@ietf.org  Fri Feb 18 12:12:18 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08732
	for <mmusic-web-archive@ietf.org>; Fri, 18 Feb 2005 12:12:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2C1c-0002AX-Pw
	for mmusic-web-archive@ietf.org; Fri, 18 Feb 2005 12:34:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D2BFP-0001rR-Mo; Fri, 18 Feb 2005 11:44:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D2ApN-0005DQ-La
	for mmusic@megatron.ietf.org; Fri, 18 Feb 2005 11:18:01 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29159
	for <mmusic@ietf.org>; Fri, 18 Feb 2005 11:17:59 -0500 (EST)
Received: from smtp111.mail.sc5.yahoo.com ([66.163.170.9])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D2BB4-0007mm-Ca
	for mmusic@ietf.org; Fri, 18 Feb 2005 11:40:26 -0500
Received: from unknown (HELO ?127.0.0.1?) (arvy?n@68.36.202.68 with plain)
	by smtp111.mail.sc5.yahoo.com with SMTP; 18 Feb 2005 16:17:58 -0000
Message-ID: <4216154A.1010600@yahoo.com>
Date: Fri, 18 Feb 2005 11:18:18 -0500
From: Aravind Narasimhan <arvy_n@yahoo.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.8a5) Gecko/20041122
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Re: [MMUSIC] RTSP connections question.
References: <42151829.90106@yahoo.com> <4215A7F7.5040108@ericsson.com>
In-Reply-To: <4215A7F7.5040108@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: 7bit
Cc: mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Content-Transfer-Encoding: 7bit

That works for me.  I'll work this into the spec if there are no objections.

Aravind

Magnus Westerlund wrote:

> Hi Aravind
>
> Aravind Narasimhan wrote:
>
>> Magnus Westerlund wrote:
>>
>> Maybe the right way to approach this is to have something that 
>> indicates to the server that you are trying to do something special 
>> and that the server may not understand it. . .  But I think that with 
>> the OPTIONS request, and support for feature tags, it should be easy 
>> to indicate this without having to put a recommendation that the 
>> server should not close a connection on an error response.  I think 
>> it would be better to let the server decide what to do on a error 
>> response, but indicate the pros and cons.  My point is that a "SHOULD 
>> NOT" seems too strong.
>>
>
> I agree that we have procedures to check if certain things will 
> happen. The problem is that there is a big difference between 
> different types of error messages, if some one includes a Require 
> header and you don't support a feature and respond with 551 (Option 
> not supported), that is clearly a valid usage. However if you respond 
> using the 400 "Bad Request" you have a higher risk that you are under 
> attack. I think SHOULD NOT is the correct level. However I think we 
> should include a reference to the security issues with this 
> recommendation.
>
>>
>>> This is very similar to the TCP overload attack. You need to accept 
>>> a TCP connections to be able to serve anyone, however if someone is 
>>> trying to overload you using TCP connects, the server will need to 
>>> block some of the request.
>>>
>>> So this is something that needs to be included in the security 
>>> consideration section as a possible venue of attack that needs to be 
>>> handled by the server implementation.
>>
>>
>>
>> The question is what does a server do about this?  What is our 
>> recommendation?
>>
>
> I think the common case, is that a server should monitor the 
> situation, and if it determines if it is under a deliberate attack, in 
> particular if there is many different sessions that receives garbage 
> messages, then the server can be more harsh against errors. The server 
> should also consider the strength of different error messages, as I 
> pointed out in the above paragraph.
>
> Cheers
>
> Magnus Westerlund
>
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>
>



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


From mmusic-bounces@ietf.org  Fri Feb 18 12:35:30 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11245
	for <mmusic-web-archive@ietf.org>; Fri, 18 Feb 2005 12:35:30 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2CO6-0002vL-S6
	for mmusic-web-archive@ietf.org; Fri, 18 Feb 2005 12:57:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D2BhV-0008Bp-VV; Fri, 18 Feb 2005 12:13:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D2BKO-0005hx-8r
	for mmusic@megatron.ietf.org; Fri, 18 Feb 2005 11:50:04 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05213
	for <mmusic@ietf.org>; Fri, 18 Feb 2005 11:50:01 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2Bg4-000186-89
	for mmusic@ietf.org; Fri, 18 Feb 2005 12:12:28 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j1IGo1O6024829 for <mmusic@ietf.org>; Fri, 18 Feb 2005 17:50:01 +0100
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 18 Feb 2005 17:50:35 +0100
Received: from [147.214.237.66] (pci [147.214.237.66]) by
	esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id 18XKTZY7; Fri, 18 Feb 2005 17:53:16 +0100
Message-ID: <42161CB8.8090305@ericsson.com>
Date: Fri, 18 Feb 2005 17:50:00 +0100
X-Sybari-Trust: 1a2b3f76 b8ec86c7 5fb16dbe 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Aravind Narasimhan <arvy_n@yahoo.com>
Subject: Re: [MMUSIC] Another RTSP Connection close question
References: <4214F897.4040909@yahoo.com>
In-Reply-To: <4214F897.4040909@yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Feb 2005 16:50:35.0851 (UTC)
	FILETIME=[F7BF19B0:01C515D9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Content-Transfer-Encoding: 7bit
Cc: mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Content-Transfer-Encoding: 7bit

Aravind Narasimhan wrote:
> Hey folks,
> 
> rtsp-bis08, section 9.3 says the following:
> 
> 
>>A server SHOULD NOT initiate a close of a connection directly after 
>>responding to a TEARDOWN request for the whole session.
> 
> 
> Does anybody have a suggestion for what a server SHOULD do?  Should it 
> wait for the RTSP session timeout period (60s)?  That doesn't make sense 
> to me because the session doesn't exist after the TEARDOWN request is 
> complete.  Should it wait for 10s?  It's a random number but has its 
> basis in the amount of time a client should wait before it should expect 
> the server to not answer (Section 9.4).  Should the server reply back 
> somehow with at header which indicates how long the server is willing to 
> wait before it closes the connection?  The Session header w/ timeout 
> parameter is not going to be useful, because no session would exist.
> 

The reason for this recommendation is to ensure that the client has time 
to setup a new session after having teardown the old one. So this time 
should give the client a decent chance to get his message through. I 
think we can follow our current rules for timing out messages. Thus I 
would say that the server should wait at least 10 seconds.

> Two more issues:
> 
>     * A client may be using the same connection to control multiple RTSP
>       sessions on the server.  So we need to be careful about wording
>       that implicitly indicates a one-to-one relationship between
>       connections and RTSP sessions where there is none.

>     * What happens if a client tries to establish another RTSP session
>       through the same connection while the server is about to close the
>       connection.  There is a  race condition here that could
>       potentially lead to incompatibilities. 

Okay, it might require some clarification, that if the server has 
initiated a close of the TCP connection during the time the client has 
tried to send a request, the client will have to close the connection, 
set up a new one and try again. Which is what one can expect with the 
rule that the server can't close without a serious timeout with an 
outstanding request received.

> 
> I'm of the opinion that the wording should be the following:
> 
> A server SHOULD NOT close a connection immediately after responding to a 
> session-level TEARDOWN request for the last RTSP session being 
> controlled through the connection.  Instead, it should wait for a 
> reasonable amount of time for the client to receive the TEARDOWN 
> response, take appropriate action, and initiate the connection closing.  
> The server SHOULD wait a default amount of 10s after the TEARDOWN 
> response to close the connection.

Seems good, except I would like to change the last sentence to:
"The server SHOULD wait at least 10s after the TEARDOWN response to 
close the connection.


> 
> Alternatively,  I think it's best if the server closes the connection 
> after a TEARDOWN when it realizes that the last RTSP session on the 
> connection has been destroyed.
> 

As I pointed out, there should be some guard time as proposed in the 
above sentence before the server closes the connection. In most cases, 
the client would initiate the close of the connection after having 
received the response.

Cheers

Magnus Westerlund

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


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


From mmusic-bounces@ietf.org  Fri Feb 18 16:51:40 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29498
	for <mmusic-web-archive@ietf.org>; Fri, 18 Feb 2005 16:51:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2GO1-0007ry-Nz
	for mmusic-web-archive@ietf.org; Fri, 18 Feb 2005 17:14:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D2EtQ-00087A-OM; Fri, 18 Feb 2005 15:38:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D2EiH-0003Bm-58; Fri, 18 Feb 2005 15:26:58 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08946;
	Fri, 18 Feb 2005 15:26:55 -0500 (EST)
Message-Id: <200502182026.PAA08946@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 18 Feb 2005 15:26:55 -0500
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-new-24.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

	Title		: SDP: Session Description Protocol
	Author(s)	: M. Handley, et al.
	Filename	: draft-ietf-mmusic-sdp-new-24.txt
	Pages		: 48
	Date		: 2005-2-18
	
This memo defines the Session Description Protocol (SDP). SDP is
intended for describing multimedia sessions for the purposes of
session announcement, session invitation, and other forms of
multimedia session initiation.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-new-24.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-mmusic-sdp-new-24.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-mmusic-sdp-new-24.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: <2005-2-18144515.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-sdp-new-24.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-mmusic-sdp-new-24.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

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

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

--NextPart--





From mmusic-bounces@ietf.org  Sun Feb 20 08:01:19 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00754
	for <mmusic-web-archive@ietf.org>; Sun, 20 Feb 2005 08:01:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2r4C-0004yJ-H5
	for mmusic-web-archive@ietf.org; Sun, 20 Feb 2005 08:24:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D2pN9-0006Gt-H5; Sun, 20 Feb 2005 06:35:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D2FsE-00032p-DR
	for mmusic@megatron.ietf.org; Fri, 18 Feb 2005 16:41:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25981
	for <mmusic@ietf.org>; Fri, 18 Feb 2005 16:41:16 -0500 (EST)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2GDw-0006fA-3h
	for mmusic@ietf.org; Fri, 18 Feb 2005 17:03:46 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-1.cisco.com with ESMTP; 18 Feb 2005 16:53:41 -0500
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.90,100,1107752400"; 
	d="scan'208"; a="37560120:sNHT17658168"
Received: from cisco.com (dhcp-64-102-92-206.cisco.com [64.102.92.206])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j1ILebhF007843
	for <mmusic@ietf.org>; Fri, 18 Feb 2005 16:40:43 -0500 (EST)
Message-ID: <421660D5.8030204@cisco.com>
Date: Fri, 18 Feb 2005 16:40:37 -0500
From: Sanjay Sinha <sanjsinh@cisco.com>
Organization: Cisco Systems
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mmusic@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sun, 20 Feb 2005 06:35:33 -0500
Subject: [MMUSIC] Realtime fax draft
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit

There were some emails on sipping list about moving the realtime-fax 
draft to mmusic group. Was it ever submitted to it? If it was, please 
send me a link or the rfc #, if it has become an rfc now.

Thanks,
Sanjay

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


From mmusic-bounces@ietf.org  Mon Feb 21 06:21:31 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12967
	for <mmusic-web-archive@ietf.org>; Mon, 21 Feb 2005 06:21:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D3BzM-0005sn-0E
	for mmusic-web-archive@ietf.org; Mon, 21 Feb 2005 06:44:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D3AzL-0006Sj-QO; Mon, 21 Feb 2005 05:40:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D3AN6-0007b8-FN
	for mmusic@megatron.ietf.org; Mon, 21 Feb 2005 05:00:56 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05932
	for <mmusic@ietf.org>; Mon, 21 Feb 2005 05:00:49 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3AjH-0003qc-6m
	for mmusic@ietf.org; Mon, 21 Feb 2005 05:23:51 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j1LA0nO6029181 for <mmusic@ietf.org>; Mon, 21 Feb 2005 11:00:49 +0100
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 21 Feb 2005 11:01:26 +0100
Received: from [147.214.237.66] (vm-client1 [147.214.237.66]) by
	esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id FLYKXV2K; Mon, 21 Feb 2005 11:03:28 +0100
Message-ID: <4219B14F.2040400@ericsson.com>
Date: Mon, 21 Feb 2005 11:00:47 +0100
X-Sybari-Trust: fb4353c9 b8ec86c7 308572d6 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "mmusic (E-mail)" <mmusic@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Feb 2005 10:01:26.0297 (UTC)
	FILETIME=[4E4FB090:01C517FC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] RTSP: Updated text in RTP-Info
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Content-Transfer-Encoding: 7bit

Hi,

In November I received some comments on the RTP-Info text that it is 
often misinterpreted regarding what values should be put into the 
"rtptime" parameter. In trying to address this and also the requirement 
to include the different parameters I have tried to rephrase the 
sentence. Please provide comments.

Cheers

Magnus

In Section 14.38 the following text is proposed.

    The header can carry the following parameters:


         url: Indicates the stream URI which for which the following RTP
              parameters correspond, this URI MUST be the same used in
              the SETUP request for this media stream. Any relative URI
              SHALL use the Request-URI as base URI. This parameter SHALL
              be present.

         seq: Indicates the sequence number of the first packet of the
              stream that is direct result of the request. This allows
              clients to gracefully deal with packets when seeking. The
              client uses this value to differentiate packets that
              originated before the seek from packets that originated
              after the seek. Note that a client may not receive the
              packet with the expressed sequence number, and instead
              packets with a higher sequence number, due to packet loss
              or reordering. This parameter is RECOMMENDED to be present.

         rtptime: SHALL indicate the RTP timestamp value corresponding to
              the start time value in the Range response header, or if
              not explicitly given the implied start point. The client
              uses this value to calculate the mapping of RTP time to NPT
              or other media timescale. This parameter SHOULD be present
              to ensure inter-media synchronization is achieved. There
              exist no requirement that any received RTP packet will have
              the same RTP timestamp value as the one in the parameter
              used to establish synchronization.


         A mapping from RTP timestamps to NTP timestamps (wall
         clock) is available via RTCP. However, this information is
         not sufficient to generate a mapping from RTP timestamps to
         media clock time (NPT, etc.). Furthermore, in order to
         ensure that this information is available at the necessary
         time (immediately at startup or after a seek), and that it
         is delivered reliably, this mapping is placed in the RTSP
         control channel.

    In order to compensate for drift for long, uninterrupted
    presentations, RTSP clients should additionally map NPT to NTP, using
    initial RTCP sender reports to do the mapping, and later reports to
    check drift against the mapping.

    Example:

    Range:npt=3.25-15
    RTP-Info:url=rtsp://example.com/foo/audio;seq=45102;rtptime=12345678,
             url=rtsp://example.com/foo/video;seq=30211;rtptime=29567112

    Lets assume that audio uses a 16kHz RTP timestamp clock and Video
    a 90kHz RTP timestamp clock. Then the media synchronization is
    depicted in the following way.

    NPT    3.0---3.1---3.2-X-3.3---3.4---3.5---3.6
    Audio               PA A
    Video                  V    PV

    X: NPT time value = 3.25, from Range header.
    A: RTP timestamp value for Audio from RTP-Info header (12345678).
    V: RTP timestamp value for Video from RTP-Info header (29567112).
    PA: RTP audio packet carrying an RTP timestamp of 12344878. Which
        corresponds to NPT = (12344878 - A) / 16000 + 3.25 = 3.2
    PV: RTP video packet carrying an RTP timestamp of 29573412. Which
        corresponds to NPT = (29573412 - V) / 90000 + 3.25 = 3.32



-- 

Magnus Westerlund

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

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


From mmusic-bounces@ietf.org  Mon Feb 21 10:04:01 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04666
	for <mmusic-web-archive@ietf.org>; Mon, 21 Feb 2005 10:04:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D3FSi-0003sZ-JQ
	for mmusic-web-archive@ietf.org; Mon, 21 Feb 2005 10:27:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D3ED8-0000gJ-CD; Mon, 21 Feb 2005 09:06:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D3Daz-0001qS-TE
	for mmusic@megatron.ietf.org; Mon, 21 Feb 2005 08:27:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24873
	for <mmusic@ietf.org>; Mon, 21 Feb 2005 08:27:23 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3DxC-0000xh-HJ
	for mmusic@ietf.org; Mon, 21 Feb 2005 08:50:27 -0500
Received: from esealmw127.eemea.ericsson.se ([153.88.254.122])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j1LDRFfm008275; Mon, 21 Feb 2005 14:27:17 +0100 (MET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 21 Feb 2005 14:27:51 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.13]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 21 Feb 2005 14:27:51 +0100
Received: from ericsson.com (EFO9N000L5C7100.lmf.ericsson.se [131.160.37.196])
	by mail.lmf.ericsson.se (Postfix) with ESMTP
	id 0E254189CC; Mon, 21 Feb 2005 15:27:13 +0200 (EET)
Message-ID: <4219E1D7.3060906@ericsson.com>
Date: Mon, 21 Feb 2005 15:27:51 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mmusic <mmusic@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Feb 2005 13:27:51.0744 (UTC)
	FILETIME=[249CEC00:01C51819]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
Cc: Flemming Andreasen <fandreas@cisco.com>, Joerg Ott <jo@tzi.uni-bremen.de>,
        Adam Roach <adam@nostrum.com>, Keith Drage <drage@lucent.com>,
        Colin Perkins <csp@csperkins.org>
Subject: [MMUSIC] Key delivery to BFCP clients
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit

Folks,

the following draft proposes that BFCP floor control servers use the SDP
'k' line to deliver a key to BFCP clients.

http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-bfcp-00.txt

However, SDPnew states the following on the use of the 'k' line:

    A simple
    mechanism for key exchange is provided by the key field ("k=")
    although this is primarily supported for compatibility with older
    implementations and its use is NOT RECOMMENDED.

SDPnew lists as alternatives to the 'k' line MIKEY and the following draft:

http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions-09.txt

This draft allows a server to send crypto stuff (e.g., algorithm to be
used) in addition to the key.


The thing is that BFCP clients will not use the key received in the SDP
to encrypt traffic and therefore, they do not need any additional crypto
stuff. They will use it to perform a digest-based authentication. That
is, they will compute a hash of a BFCP message and the key and send it
to the server to prove that the client sending the BFCP message is the
same as the one that received the SDP session description.

So, the key received in the SDP is used as a digest password. We need to
figure out how to transport this password from the server to the client.
The choices are:

1) we use the 'k' line and explain why the considerations against its
use do not apply in this case.

2) we define a new SDP parameter to carry shared secrets, as opposed to
encryption keys, in SDP.

My proposal is to go for 1). Any comments or objections?

Thanks,

Gonzalo



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


From mmusic-bounces@ietf.org  Wed Feb 23 00:25:48 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11748
	for <mmusic-web-archive@ietf.org>; Wed, 23 Feb 2005 00:25:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D3pOc-0002Jr-3x
	for mmusic-web-archive@ietf.org; Wed, 23 Feb 2005 00:49:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D3kfM-0004MG-SP; Tue, 22 Feb 2005 19:46:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D3cYR-0005Aq-5a
	for mmusic@megatron.ietf.org; Tue, 22 Feb 2005 11:06:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15753
	for <mmusic@ietf.org>; Tue, 22 Feb 2005 11:06:23 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3cuo-0001Ab-St
	for mmusic@ietf.org; Tue, 22 Feb 2005 11:29:40 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j1MG6IO6020271 for <mmusic@ietf.org>; Tue, 22 Feb 2005 17:06:20 +0100
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 22 Feb 2005 17:06:57 +0100
Received: from [147.214.237.66] (vietas [147.214.237.66]) by
	esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id FLYCJ9GR; Tue, 22 Feb 2005 17:09:47 +0100
Message-ID: <421B5877.2080001@ericsson.com>
Date: Tue, 22 Feb 2005 17:06:15 +0100
X-Sybari-Trust: a007c969 b8ec86c7 6fd9df5c 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Thomas Zeng <zeng@pvnetsolutions.com>
Subject: Re: [MMUSIC] RTSP: Updated text in RTP-Info
References: <758B5A159B385447B4F950DE72D7D7AD678CE3@srsdmail01.PVNS.COM>
In-Reply-To: <758B5A159B385447B4F950DE72D7D7AD678CE3@srsdmail01.PVNS.COM>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Feb 2005 16:06:57.0049 (UTC)
	FILETIME=[8878A090:01C518F8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
Cc: "mmusic \(E-mail\)" <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit

Hi Thomas,

Thanks for the comments and corrections.


Thomas Zeng wrote:
> [tz] The last two paragraphes, along with the example below, seem to fit better in the section: B.1.8 Maintaining NPT synchronization with RTP timestamps.
> 

I don't know, people seem to misinterpret this frequently, and having an 
motivation and example near the specification text will hopefully make 
it so much clearer. However I haven't review the new text in light of 
B.1.8.

Cheers

Magnus Westerlund

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

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


From mmusic-bounces@ietf.org  Wed Feb 23 20:07:24 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06977
	for <mmusic-web-archive@ietf.org>; Wed, 23 Feb 2005 20:07:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D47qH-0007d8-TD
	for mmusic-web-archive@ietf.org; Wed, 23 Feb 2005 20:31:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D3kly-00066Q-JL; Tue, 22 Feb 2005 19:53:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D3OEc-0003Zc-2G
	for mmusic@megatron.ietf.org; Mon, 21 Feb 2005 19:49:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06083
	for <mmusic@ietf.org>; Mon, 21 Feb 2005 19:48:57 -0500 (EST)
Received: from auds953.usa.alcatel.com ([143.209.238.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3Oas-00023G-PF
	for mmusic@ietf.org; Mon, 21 Feb 2005 20:12:09 -0500
Received: from srsdmail01.PVNS.COM (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id
	j1M0mMfp000264; Mon, 21 Feb 2005 18:48:23 -0600 (CST)
X-MIMEOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [MMUSIC] RTSP: Updated text in RTP-Info
Date: Mon, 21 Feb 2005 16:48:22 -0800
Message-ID: <758B5A159B385447B4F950DE72D7D7AD678CE3@srsdmail01.PVNS.COM>
Thread-Topic: [MMUSIC] RTSP: Updated text in RTP-Info
Thread-Index: AcUYDCy5HY6wOroPSg60iXv60z4caAAalZ4g
From: "Thomas Zeng" <zeng@pvnetsolutions.com>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>,
        "mmusic \(E-mail\)" <mmusic@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2060926562=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e

--===============2060926562==
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

TWFnbnVzOg0KDQpDb21tZW50cywgbW9zdGx5IGVkaXRvcmlhbCwgYXJlIGlubGluZWQuDQoNCkJl
c3QgcmVnYXJkcywNCi10aG9tYXMNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206
IG1tdXNpYy1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86bW11c2ljLWJvdW5jZXNAaWV0Zi5vcmdd
T24gQmVoYWxmDQpPZiBNYWdudXMgV2VzdGVybHVuZA0KU2VudDogTW9uZGF5LCBGZWJydWFyeSAy
MSwgMjAwNSAyOjAxIEFNDQpUbzogbW11c2ljIChFLW1haWwpDQpTdWJqZWN0OiBbTU1VU0lDXSBS
VFNQOiBVcGRhdGVkIHRleHQgaW4gUlRQLUluZm8NCg0KDQpIaSwNCg0KSW4gTm92ZW1iZXIgSSBy
ZWNlaXZlZCBzb21lIGNvbW1lbnRzIG9uIHRoZSBSVFAtSW5mbyB0ZXh0IHRoYXQgaXQgaXMgDQpv
ZnRlbiBtaXNpbnRlcnByZXRlZCByZWdhcmRpbmcgd2hhdCB2YWx1ZXMgc2hvdWxkIGJlIHB1dCBp
bnRvIHRoZSANCiJydHB0aW1lIiBwYXJhbWV0ZXIuIEluIHRyeWluZyB0byBhZGRyZXNzIHRoaXMg
YW5kIGFsc28gdGhlIHJlcXVpcmVtZW50IA0KdG8gaW5jbHVkZSB0aGUgZGlmZmVyZW50IHBhcmFt
ZXRlcnMgSSBoYXZlIHRyaWVkIHRvIHJlcGhyYXNlIHRoZSANCnNlbnRlbmNlLiBQbGVhc2UgcHJv
dmlkZSBjb21tZW50cy4NCg0KQ2hlZXJzDQoNCk1hZ251cw0KDQpJbiBTZWN0aW9uIDE0LjM4IHRo
ZSBmb2xsb3dpbmcgdGV4dCBpcyBwcm9wb3NlZC4NCg0KICAgIFRoZSBoZWFkZXIgY2FuIGNhcnJ5
IHRoZSBmb2xsb3dpbmcgcGFyYW1ldGVyczoNCg0KDQogICAgICAgICB1cmw6IEluZGljYXRlcyB0
aGUgc3RyZWFtIFVSSSB3aGljaCBmb3Igd2hpY2ggdGhlIGZvbGxvd2luZyBSVFANClt0el0gICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIGNoYW5nZSAgICAgIndoaWNoIGZvciB3aGljaCIgPT09
PiAidG8gd2hpY2giDQogICAgICAgICAgICAgIHBhcmFtZXRlcnMgY29ycmVzcG9uZCwgdGhpcyBV
UkkgTVVTVCBiZSB0aGUgc2FtZSB1c2VkIGluDQogICAgICAgICAgICAgIHRoZSBTRVRVUCByZXF1
ZXN0IGZvciB0aGlzIG1lZGlhIHN0cmVhbS4gQW55IHJlbGF0aXZlIFVSSQ0KICAgICAgICAgICAg
ICBTSEFMTCB1c2UgdGhlIFJlcXVlc3QtVVJJIGFzIGJhc2UgVVJJLiBUaGlzIHBhcmFtZXRlciBT
SEFMTA0KICAgICAgICAgICAgICBiZSBwcmVzZW50Lg0KDQogICAgICAgICBzZXE6IEluZGljYXRl
cyB0aGUgc2VxdWVuY2UgbnVtYmVyIG9mIHRoZSBmaXJzdCBwYWNrZXQgb2YgdGhlDQogICAgICAg
ICAgICAgIHN0cmVhbSB0aGF0IGlzIHRoZSBkaXJlY3QgcmVzdWx0IG9mIHRoZSBQTEFZIHJlcXVl
c3QuIFRoaXMgYWxsb3dzDQoJICAgICAgICAgICAgICAgICAgICAgICBeXl4gW3R6XSBhZGQgICAg
ICAgICAgICAgXl5eXiAgW3R6XSBhZGQNCiAgICAgICAgICAgICAgY2xpZW50cyB0byBncmFjZWZ1
bGx5IGRlYWwgd2l0aCBwYWNrZXRzIHdoZW4gc2Vla2luZy4gVGhlDQogICAgICAgICAgICAgIGNs
aWVudCB1c2VzIHRoaXMgdmFsdWUgdG8gZGlmZmVyZW50aWF0ZSBwYWNrZXRzIHRoYXQNCiAgICAg
ICAgICAgICAgb3JpZ2luYXRlZCBiZWZvcmUgdGhlIHNlZWsgZnJvbSBwYWNrZXRzIHRoYXQgb3Jp
Z2luYXRlZA0KICAgICAgICAgICAgICBhZnRlciB0aGUgc2Vlay4gTm90ZSB0aGF0IGEgY2xpZW50
IG1heSBub3QgcmVjZWl2ZSB0aGUNCiAgICAgICAgICAgICAgcGFja2V0IHdpdGggdGhlIGV4cHJl
c3NlZCBzZXF1ZW5jZSBudW1iZXIsIGFuZCBpbnN0ZWFkDQogICAgICAgICAgICAgIHBhY2tldHMg
d2l0aCBhIGhpZ2hlciBzZXF1ZW5jZSBudW1iZXIsIGR1ZSB0byBwYWNrZXQgbG9zcw0KICAgICAg
ICAgICAgICBvciByZW9yZGVyaW5nLiBUaGlzIHBhcmFtZXRlciBpcyBSRUNPTU1FTkRFRCB0byBi
ZSBwcmVzZW50Lg0KDQogICAgICAgICBydHB0aW1lOiBTSEFMTCBpbmRpY2F0ZSB0aGUgUlRQIHRp
bWVzdGFtcCB2YWx1ZSBjb3JyZXNwb25kaW5nIHRvDQogICAgICAgICAgICAgIHRoZSBzdGFydCB0
aW1lIHZhbHVlIGluIHRoZSBSYW5nZSByZXNwb25zZSBoZWFkZXIsIG9yIGlmIHRoZSBSYW5nZSBo
ZWFkZXINCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgW3R6XSAgXl5eXl5eXl5eXl5eXl5eXiAgW3R6XSBhZGQNCiAgICAgICAg
ICAgICAgbm90IGV4cGxpY2l0bHkgZ2l2ZW4sIHRoZSBpbXBsaWVkIHN0YXJ0IHBvaW50LiBUaGUg
Y2xpZW50DQogICAgICAgICAgICAgICAgICAgICAgW3R6XSAgICAgICAgXiBbdHpdIGFkZA0KICAg
ICAgICAgICAgICB1c2VzIHRoaXMgdmFsdWUgdG8gY2FsY3VsYXRlIHRoZSBtYXBwaW5nIG9mIFJU
UCB0aW1lIHRvIE5QVA0KICAgICAgICAgICAgICBvciBvdGhlciBtZWRpYSB0aW1lc2NhbGUuIFRo
aXMgcGFyYW1ldGVyIFNIT1VMRCBiZSBwcmVzZW50DQogICAgICAgICAgICAgIHRvIGVuc3VyZSBp
bnRlci1tZWRpYSBzeW5jaHJvbml6YXRpb24gaXMgYWNoaWV2ZWQuIFRoZXJlDQogICAgICAgICAg
ICAgIGV4aXN0IG5vIHJlcXVpcmVtZW50IHRoYXQgYW55IHJlY2VpdmVkIFJUUCBwYWNrZXQgd2ls
bCBoYXZlDQogICAgICAgICAgICAgIHRoZSBzYW1lIFJUUCB0aW1lc3RhbXAgdmFsdWUgYXMgdGhl
IG9uZSBpbiB0aGUgcGFyYW1ldGVyDQogICAgICAgICAgICAgIHVzZWQgdG8gZXN0YWJsaXNoIHN5
bmNocm9uaXphdGlvbi4NCg0KDQogICAgICAgICBBIG1hcHBpbmcgZnJvbSBSVFAgdGltZXN0YW1w
cyB0byBOVFAgdGltZXN0YW1wcyAod2FsbA0KICAgICAgICAgY2xvY2spIGlzIGF2YWlsYWJsZSB2
aWEgUlRDUC4gSG93ZXZlciwgdGhpcyBpbmZvcm1hdGlvbiBpcw0KICAgICAgICAgbm90IHN1ZmZp
Y2llbnQgdG8gZ2VuZXJhdGUgYSBtYXBwaW5nIGZyb20gUlRQIHRpbWVzdGFtcHMgdG8NCiAgICAg
ICAgIG1lZGlhIGNsb2NrIHRpbWUgKE5QVCwgZXRjLikuIEZ1cnRoZXJtb3JlLCBpbiBvcmRlciB0
bw0KICAgICAgICAgZW5zdXJlIHRoYXQgdGhpcyBpbmZvcm1hdGlvbiBpcyBhdmFpbGFibGUgYXQg
dGhlIG5lY2Vzc2FyeQ0KICAgICAgICAgdGltZSAoaW1tZWRpYXRlbHkgYXQgc3RhcnR1cCBvciBh
ZnRlciBhIHNlZWspLCBhbmQgdGhhdCBpdA0KICAgICAgICAgaXMgZGVsaXZlcmVkIHJlbGlhYmx5
LCB0aGlzIG1hcHBpbmcgaXMgcGxhY2VkIGluIHRoZSBSVFNQDQogICAgICAgICBjb250cm9sIGNo
YW5uZWwuDQoNCg0KICAgIEluIG9yZGVyIHRvIGNvbXBlbnNhdGUgZm9yIGRyaWZ0IGZvciBsb25n
LCB1bmludGVycnVwdGVkDQogICAgcHJlc2VudGF0aW9ucywgUlRTUCBjbGllbnRzIHNob3VsZCBh
ZGRpdGlvbmFsbHkgbWFwIE5QVCB0byBOVFAsIHVzaW5nDQogICAgaW5pdGlhbCBSVENQIHNlbmRl
ciByZXBvcnRzIHRvIGRvIHRoZSBtYXBwaW5nLCBhbmQgbGF0ZXIgcmVwb3J0cyB0bw0KICAgIGNo
ZWNrIGRyaWZ0IGFnYWluc3QgdGhlIG1hcHBpbmcuDQpbdHpdIFRoZSBsYXN0IHR3byBwYXJhZ3Jh
cGhlcywgYWxvbmcgd2l0aCB0aGUgZXhhbXBsZSBiZWxvdywgc2VlbSB0byBmaXQgYmV0dGVyIGlu
IHRoZSBzZWN0aW9uOiBCLjEuOCBNYWludGFpbmluZyBOUFQgc3luY2hyb25pemF0aW9uIHdpdGgg
UlRQIHRpbWVzdGFtcHMuDQoNCiAgICBFeGFtcGxlOg0KDQogICAgUmFuZ2U6bnB0PTMuMjUtMTUN
CiAgICBSVFAtSW5mbzp1cmw9cnRzcDovL2V4YW1wbGUuY29tL2Zvby9hdWRpbztzZXE9NDUxMDI7
cnRwdGltZT0xMjM0NTY3OCwNCiAgICAgICAgICAgICB1cmw9cnRzcDovL2V4YW1wbGUuY29tL2Zv
by92aWRlbztzZXE9MzAyMTE7cnRwdGltZT0yOTU2NzExMg0KDQogICAgTGV0cyBhc3N1bWUgdGhh
dCBhdWRpbyB1c2VzIGEgMTZrSHogUlRQIHRpbWVzdGFtcCBjbG9jayBhbmQgVmlkZW8NCiAgICBh
IDkwa0h6IFJUUCB0aW1lc3RhbXAgY2xvY2suIFRoZW4gdGhlIG1lZGlhIHN5bmNocm9uaXphdGlv
biBpcw0KICAgIGRlcGljdGVkIGluIHRoZSBmb2xsb3dpbmcgd2F5Lg0KDQogICAgTlBUICAgIDMu
MC0tLTMuMS0tLTMuMi1YLTMuMy0tLTMuNC0tLTMuNS0tLTMuNg0KICAgIEF1ZGlvICAgICAgICAg
ICAgICAgUEEgQQ0KICAgIFZpZGVvICAgICAgICAgICAgICAgICAgViAgICBQVg0KDQogICAgWDog
TlBUIHRpbWUgdmFsdWUgPSAzLjI1LCBmcm9tIFJhbmdlIGhlYWRlci4NCiAgICBBOiBSVFAgdGlt
ZXN0YW1wIHZhbHVlIGZvciBBdWRpbyBmcm9tIFJUUC1JbmZvIGhlYWRlciAoMTIzNDU2NzgpLg0K
ICAgIFY6IFJUUCB0aW1lc3RhbXAgdmFsdWUgZm9yIFZpZGVvIGZyb20gUlRQLUluZm8gaGVhZGVy
ICgyOTU2NzExMikuDQogICAgUEE6IFJUUCBhdWRpbyBwYWNrZXQgY2FycnlpbmcgYW4gUlRQIHRp
bWVzdGFtcCBvZiAxMjM0NDg3OC4gV2hpY2gNCiAgICAgICAgY29ycmVzcG9uZHMgdG8gTlBUID0g
KDEyMzQ0ODc4IC0gQSkgLyAxNjAwMCArIDMuMjUgPSAzLjINCiAgICBQVjogUlRQIHZpZGVvIHBh
Y2tldCBjYXJyeWluZyBhbiBSVFAgdGltZXN0YW1wIG9mIDI5NTczNDEyLiBXaGljaA0KICAgICAg
ICBjb3JyZXNwb25kcyB0byBOUFQgPSAoMjk1NzM0MTIgLSBWKSAvIDkwMDAwICsgMy4yNSA9IDMu
MzINCg0KDQoNCi0tIA0KDQpNYWdudXMgV2VzdGVybHVuZA0KDQpNdWx0aW1lZGlhIFRlY2hub2xv
Z2llcywgRXJpY3Nzb24gUmVzZWFyY2ggRUFCL1RWQS9BDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpFcmljc3Nv
biBBQiAgICAgICAgICAgICAgICB8IFBob25lICs0NiA4IDQwNDgyODcNClRvcnNoYW1zZ2F0YW4g
MjMgICAgICAgICAgIHwgRmF4ICAgKzQ2IDggNzU3NTU1MA0KUy0xNjQgODAgU3RvY2tob2xtLCBT
d2VkZW4gfCBtYWlsdG86IG1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29uLmNvbQ0KDQpfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KbW11c2ljIG1haWxpbmcg
bGlzdA0KbW11c2ljQGlldGYub3JnDQpodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9tbXVzaWMNCg==


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

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

--===============2060926562==--


From mmusic-bounces@ietf.org  Wed Feb 23 20:15:15 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08867
	for <mmusic-web-archive@ietf.org>; Wed, 23 Feb 2005 20:15:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D47xr-0008Fr-Cv
	for mmusic-web-archive@ietf.org; Wed, 23 Feb 2005 20:38:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D43Ts-0007Mg-T3; Wed, 23 Feb 2005 15:51:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D43To-0007M3-Gc; Wed, 23 Feb 2005 15:51:32 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14950;
	Wed, 23 Feb 2005 15:51:30 -0500 (EST)
Message-Id: <200502232051.PAA14950@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 23 Feb 2005 15:51:30 -0500
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-ice-04.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

	Title		: Interactive Connectivity Establishment (ICE): 
			  A Methodology for Network Address Translator (NAT) 
			  Traversal for Multimedia Session Establishment Protocols
	Author(s)	: J. Rosenberg
	Filename	: draft-ietf-mmusic-ice-04.txt
	Pages		: 46
	Date		: 2005-2-23
	
This document describes a methodology for Network Address Translator
   (NAT) traversal for multimedia session signaling protocols, such as
   the Session Initiation Protocol (SIP).  This methodology is called
   Interactive Connectivity Establishment (ICE).  ICE makes use of
   existing protocols, such as Simple Traversal of UDP Through NAT
   (STUN) and Traversal Using Relay NAT (TURN).  ICE makes use of STUN
   in peer-to-peer cooperative fashion, allowing participants to
   discover, create and verify mutual connectivity.

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

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


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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-ice-04.txt

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

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


--OtherAccess--

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

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

--NextPart--





From mmusic-bounces@ietf.org  Wed Feb 23 22:14:37 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22659
	for <mmusic-web-archive@ietf.org>; Wed, 23 Feb 2005 22:14:37 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D49pO-0004Qk-88
	for mmusic-web-archive@ietf.org; Wed, 23 Feb 2005 22:38:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D3klE-0005u2-6e; Tue, 22 Feb 2005 19:52:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D3ilO-00008r-Kh
	for mmusic@megatron.ietf.org; Tue, 22 Feb 2005 17:44:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02915
	for <mmusic@ietf.org>; Tue, 22 Feb 2005 17:44:07 -0500 (EST)
Received: from flawless.real.com ([207.188.23.141])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3j7p-0005Qm-U8
	for mmusic@ietf.org; Tue, 22 Feb 2005 18:07:30 -0500
Received: from d845pebt2_xp.real.com ([::ffff:172.22.143.254])
	(AUTH: LOGIN rmathew, SSL: TLSv1/SSLv3,168bits,DES-CBC3-SHA)
	by flawless.real.com with esmtp; Tue, 22 Feb 2005 14:43:34 -0800
	id 0004F9AB.421BB596.00000186
Message-Id: <6.2.1.2.2.20050222144242.03e85028@mailone.real.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2
Date: Tue, 22 Feb 2005 14:43:38 -0800
To: Magnus Westerlund <magnus.westerlund@ericsson.com>,
        "mmusic (E-mail)" <mmusic@ietf.org>
From: Rishi Mathew <rmathew@real.com>
Subject: Re: [MMUSIC] RTSP: Updated text in RTP-Info
In-Reply-To: <4219B14F.2040400@ericsson.com>
References: <4219B14F.2040400@ericsson.com>
Mime-Version: 1.0
X-Spam-Score: 0.6 (/)
X-Scan-Signature: fe105289edd72640d9f392da880eefa2
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0693130346=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 918f4bd8440e8de4700bcf6d658bc801

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--===============0693130346==
Content-Type: multipart/alternative;
	boundary="=_flawless.real.com-390-1109112214-0001-2"

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_flawless.real.com-390-1109112214-0001-2
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hey Magnus,

This proposed text looks good to us.

Thanks for looking into this..
-Rishi.

At 02:00 AM 2/21/2005, Magnus Westerlund wrote:
>Hi,
>
>In November I received some comments on the RTP-Info text that it is often 
>misinterpreted regarding what values should be put into the "rtptime" 
>parameter. In trying to address this and also the requirement to include 
>the different parameters I have tried to rephrase the sentence. Please 
>provide comments.
>
>Cheers
>
>Magnus
>
>In Section 14.38 the following text is proposed.
>
>    The header can carry the following parameters:
>
>
>         url: Indicates the stream URI which for which the following RTP
>              parameters correspond, this URI MUST be the same used in
>              the SETUP request for this media stream. Any relative URI
>              SHALL use the Request-URI as base URI. This parameter SHALL
>              be present.
>
>         seq: Indicates the sequence number of the first packet of the
>              stream that is direct result of the request. This allows
>              clients to gracefully deal with packets when seeking. The
>              client uses this value to differentiate packets that
>              originated before the seek from packets that originated
>              after the seek. Note that a client may not receive the
>              packet with the expressed sequence number, and instead
>              packets with a higher sequence number, due to packet loss
>              or reordering. This parameter is RECOMMENDED to be present.
>
>         rtptime: SHALL indicate the RTP timestamp value corresponding to
>              the start time value in the Range response header, or if
>              not explicitly given the implied start point. The client
>              uses this value to calculate the mapping of RTP time to NPT
>              or other media timescale. This parameter SHOULD be present
>              to ensure inter-media synchronization is achieved. There
>              exist no requirement that any received RTP packet will have
>              the same RTP timestamp value as the one in the parameter
>              used to establish synchronization.
>
>
>         A mapping from RTP timestamps to NTP timestamps (wall
>         clock) is available via RTCP. However, this information is
>         not sufficient to generate a mapping from RTP timestamps to
>         media clock time (NPT, etc.). Furthermore, in order to
>         ensure that this information is available at the necessary
>         time (immediately at startup or after a seek), and that it
>         is delivered reliably, this mapping is placed in the RTSP
>         control channel.
>
>    In order to compensate for drift for long, uninterrupted
>    presentations, RTSP clients should additionally map NPT to NTP, using
>    initial RTCP sender reports to do the mapping, and later reports to
>    check drift against the mapping.
>
>    Example:
>
>    Range:npt=3.25-15
>    RTP-Info:url=rtsp://example.com/foo/audio;seq=45102;rtptime=12345678,
>             url=rtsp://example.com/foo/video;seq=30211;rtptime=29567112
>
>    Lets assume that audio uses a 16kHz RTP timestamp clock and Video
>    a 90kHz RTP timestamp clock. Then the media synchronization is
>    depicted in the following way.
>
>    NPT    3.0---3.1---3.2-X-3.3---3.4---3.5---3.6
>    Audio               PA A
>    Video                  V    PV
>
>    X: NPT time value = 3.25, from Range header.
>    A: RTP timestamp value for Audio from RTP-Info header (12345678).
>    V: RTP timestamp value for Video from RTP-Info header (29567112).
>    PA: RTP audio packet carrying an RTP timestamp of 12344878. Which
>        corresponds to NPT = (12344878 - A) / 16000 + 3.25 = 3.2
>    PV: RTP video packet carrying an RTP timestamp of 29573412. Which
>        corresponds to NPT = (29573412 - V) / 90000 + 3.25 = 3.32
>
>
>
>--
>
>Magnus Westerlund
>
>Multimedia Technologies, Ericsson Research EAB/TVA/A
>----------------------------------------------------------------------
>Ericsson AB                | Phone +46 8 4048287
>Torshamsgatan 23           | Fax   +46 8 7575550
>S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www1.ietf.org/mailman/listinfo/mmusic


Rishi Mathew
Software Development Engineer
Helix Development Support Group
RealNetworks, Inc.
rmathew@real.com
206.892.6126
http://www.helixcommunity.org
http://www.realnetworks.com/products/support/devsupport.html

--=_flawless.real.com-390-1109112214-0001-2
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<html>
<body>
Hey Magnus,<br><br>
This proposed text looks good to us.<br><br>
Thanks for looking into this..<br>
-Rishi.<br><br>
At 02:00 AM 2/21/2005, Magnus Westerlund wrote:<br>
<blockquote type=cite class=cite cite="">Hi,<br><br>
In November I received some comments on the RTP-Info text that it is
often misinterpreted regarding what values should be put into the
&quot;rtptime&quot; parameter. In trying to address this and also the
requirement to include the different parameters I have tried to rephrase
the sentence. Please provide comments.<br><br>
Cheers<br><br>
Magnus<br><br>
In Section 14.38 the following text is proposed.<br><br>
&nbsp;&nbsp; The header can carry the following parameters:<br><br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; url: Indicates the stream URI
which for which the following RTP<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
parameters correspond, this URI MUST be the same used in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
the SETUP request for this media stream. Any relative URI<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SHALL use the Request-URI as base URI. This parameter SHALL<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
be present.<br><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; seq: Indicates the sequence
number of the first packet of the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
stream that is direct result of the request. This allows<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
clients to gracefully deal with packets when seeking. The<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
client uses this value to differentiate packets that<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
originated before the seek from packets that originated<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
after the seek. Note that a client may not receive the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
packet with the expressed sequence number, and instead<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
packets with a higher sequence number, due to packet loss<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
or reordering. This parameter is RECOMMENDED to be present.<br><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; rtptime: SHALL indicate the
RTP timestamp value corresponding to<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
the start time value in the Range response header, or if<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
not explicitly given the implied start point. The client<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
uses this value to calculate the mapping of RTP time to NPT<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
or other media timescale. This parameter SHOULD be present<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
to ensure inter-media synchronization is achieved. There<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
exist no requirement that any received RTP packet will have<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
the same RTP timestamp value as the one in the parameter<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
used to establish synchronization.<br><br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A mapping from RTP timestamps
to NTP timestamps (wall<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; clock) is available via RTCP.
However, this information is<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; not sufficient to generate a
mapping from RTP timestamps to<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; media clock time (NPT, etc.).
Furthermore, in order to<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ensure that this information
is available at the necessary<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; time (immediately at startup
or after a seek), and that it<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is delivered reliably, this
mapping is placed in the RTSP<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; control channel.<br><br>
&nbsp;&nbsp; In order to compensate for drift for long,
uninterrupted<br>
&nbsp;&nbsp; presentations, RTSP clients should additionally map NPT to
NTP, using<br>
&nbsp;&nbsp; initial RTCP sender reports to do the mapping, and later
reports to<br>
&nbsp;&nbsp; check drift against the mapping.<br><br>
&nbsp;&nbsp; Example:<br><br>
&nbsp;&nbsp; Range:npt=3.25-15<br>
&nbsp;&nbsp;
RTP-Info:url=<a href="rtsp://example.com/foo/audio;seq=45102;rtptime=12345678" eudora="autourl">
rtsp://example.com/foo/audio;seq=45102;rtptime=12345678</a>,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
url=<a href="rtsp://example.com/foo/video;seq=30211;rtptime=29567112" eudora="autourl">
rtsp://example.com/foo/video;seq=30211;rtptime=29567112</a><br><br>
&nbsp;&nbsp; Lets assume that audio uses a 16kHz RTP timestamp clock and
Video<br>
&nbsp;&nbsp; a 90kHz RTP timestamp clock. Then the media synchronization
is<br>
&nbsp;&nbsp; depicted in the following way.<br><br>
&nbsp;&nbsp; NPT&nbsp;&nbsp;&nbsp;
3.0---3.1---3.2-X-3.3---3.4---3.5---3.6<br>
&nbsp;&nbsp;
Audio&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
PA A<br>
&nbsp;&nbsp;
Video&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
V&nbsp;&nbsp;&nbsp; PV<br><br>
&nbsp;&nbsp; X: NPT time value = 3.25, from Range header.<br>
&nbsp;&nbsp; A: RTP timestamp value for Audio from RTP-Info header
(12345678).<br>
&nbsp;&nbsp; V: RTP timestamp value for Video from RTP-Info header
(29567112).<br>
&nbsp;&nbsp; PA: RTP audio packet carrying an RTP timestamp of 12344878.
Which<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; corresponds to NPT = (12344878 - A)
/ 16000 + 3.25 = 3.2<br>
&nbsp;&nbsp; PV: RTP video packet carrying an RTP timestamp of 29573412.
Which<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; corresponds to NPT = (29573412 - V)
/ 90000 + 3.25 = 3.32<br><br>
<br><br>
-- <br><br>
Magnus Westerlund<br><br>
Multimedia Technologies, Ericsson Research EAB/TVA/A<br>
----------------------------------------------------------------------<br>
Ericsson
AB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
| Phone +46 8 4048287<br>
Torshamsgatan
23&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
Fax&nbsp;&nbsp; +46 8 7575550<br>
S-164 80 Stockholm, Sweden | mailto:
magnus.westerlund@ericsson.com<br><br>
_______________________________________________<br>
mmusic mailing list<br>
mmusic@ietf.org<br>
<a href="https://www1.ietf.org/mailman/listinfo/mmusic" eudora="autourl">
https://www1.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote>
<x-sigsep><p></x-sigsep>
<br>
<font size=2><b>Rishi Mathew<br>
</b>Software Development Engineer<br>
Helix Development Support Group<br>
</font><font size=2 color="#0000FF"><b>Real</b></font><font size=2>
Networks, Inc. <br>
rmathew@real.com <br>
206.892.6126 <br>
</font><font size=2 color="#0000FF"><u>
<a href="http://www.helixcommunity.org/" eudora="autourl">
http://www.helixcommunity.org<br>
</a>
<a href="http://www.realnetworks.com/products/support/devsupport.html" eudora="autourl">
http://www.realnetworks.com/products/support/devsupport.html<br>
</a></font></u></body>
</html>

--=_flawless.real.com-390-1109112214-0001-2--


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

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

--===============0693130346==--



From mmusic-bounces@ietf.org  Wed Feb 23 22:40:43 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02364
	for <mmusic-web-archive@ietf.org>; Wed, 23 Feb 2005 22:40:42 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D4AEe-0007IY-Gk
	for mmusic-web-archive@ietf.org; Wed, 23 Feb 2005 23:04:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D43UD-0007Oa-3j; Wed, 23 Feb 2005 15:51:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D43U9-0007NN-3O; Wed, 23 Feb 2005 15:51:53 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14983;
	Wed, 23 Feb 2005 15:51:50 -0500 (EST)
Message-Id: <200502232051.PAA14983@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 23 Feb 2005 15:51:50 -0500
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-rfc2326bis-09.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

	Title		: Real Time Streaming Protocol (RTSP)
	Author(s)	: H. Schulzrinne, et al.
	Filename	: draft-ietf-mmusic-rfc2326bis-09.txt
	Pages		: 178
	Date		: 2005-2-23
	
This memorandum is a revision of RFC 2326, which is currently a
   Proposed Standard.

   The Real Time Streaming Protocol, or RTSP, is an application-level
   protocol for control over the delivery of data with real-time
   properties. RTSP provides an extensible framework to enable
   controlled, on-demand delivery of real-time data, such as audio and
   video. Sources of data can include both live data feeds and stored
   clips. This protocol is intended to control multiple data delivery
   sessions, provide a means for choosing delivery channels such as UDP,
   multicast UDP and TCP, and provide a means for choosing delivery
   mechanisms based upon RTP (RFC 3550).

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

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


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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-rfc2326bis-09.txt

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

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


--OtherAccess--

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

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

--NextPart--





From mmusic-bounces@ietf.org  Wed Feb 23 22:52:14 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07237
	for <mmusic-web-archive@ietf.org>; Wed, 23 Feb 2005 22:52:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D4APn-0000BD-8Z
	for mmusic-web-archive@ietf.org; Wed, 23 Feb 2005 23:15:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D3z7s-0000HZ-4Y; Wed, 23 Feb 2005 11:12:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D3z7p-0000G2-RC
	for mmusic@megatron.ietf.org; Wed, 23 Feb 2005 11:12:33 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03572
	for <mmusic@ietf.org>; Wed, 23 Feb 2005 11:12:25 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3zUR-0006YD-Gc
	for mmusic@ietf.org; Wed, 23 Feb 2005 11:35:57 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j1NGCOh5022915
	for <mmusic@ietf.org>; Wed, 23 Feb 2005 17:12:24 +0100 (MET)
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by
	esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 23 Feb 2005 17:13:05 +0100
Received: from [147.214.237.66] (vmclient-50 [147.214.237.66]) by
	esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id F3XNWX6G; Wed, 23 Feb 2005 17:12:24 +0100
Message-ID: <421CAB67.2020805@ericsson.com>
Date: Wed, 23 Feb 2005 17:12:23 +0100
X-Sybari-Trust: c3edb8d5 b8ec86c7 a29e4f76 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "mmusic (E-mail)" <mmusic@ietf.org>
Content-Type: multipart/mixed; boundary="------------050609030701080902050101"
X-OriginalArrivalTime: 23 Feb 2005 16:13:05.0131 (UTC)
	FILETIME=[8E473BB0:01C519C2]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 21be852dc93f0971708678c18d38c096
Subject: [MMUSIC] [Fwd: I-D
	ACTION:draft-westerlund-mmusic-3gpp-sdp-rtsp-00.txt]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e8c5db863102a3ada84e0cd52a81a79e

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

This draft is now available from IETF.

Cheers

Magnus Westerlund

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

--------------050609030701080902050101
Content-Type: message/rfc822;
	name="I-D ACTION:draft-westerlund-mmusic-3gpp-sdp-rtsp-00.txt"
Content-Disposition: inline;
	filename="I-D ACTION:draft-westerlund-mmusic-3gpp-sdp-rtsp-00.txt"

Received: from esealmw111.eemea.ericsson.se ([130.100.184.156]) by
	esealmw103.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 16 Feb 2005 18:57:16 +0100
Received: from esealmw129.eemea.ericsson.se ([130.100.184.164]) by
	esealmw111.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 16 Feb 2005 18:57:15 +0100
Received: from esealmw127.eemea.ericsson.se ([130.100.184.162]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 16 Feb 2005 18:57:15 +0100
Received: from falcon.ericsson.se ([193.180.251.52]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 16 Feb 2005 18:57:14 +0100
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by falcon.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id
	j1GHueeL016666; Wed, 16 Feb 2005 18:56:40 +0100
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1RXL-0002pV-Qy; Wed, 16 Feb 2005 10:56:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1Qw7-0002Xg-Bu
	for i-d-announce@megatron.ietf.org; Wed, 16 Feb 2005 10:17:55 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21509
	for <i-d-announce@ietf.org>; Wed, 16 Feb 2005 10:17:52 -0500 (EST)
Message-Id: <200502161517.KAA21509@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 16 Feb 2005 10:17:52 -0500
Subject: I-D ACTION:draft-westerlund-mmusic-3gpp-sdp-rtsp-00.txt
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: i-d-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
Sender: i-d-announce-bounces@ietf.org
Errors-To: i-d-announce-bounces@ietf.org
Return-Path: i-d-announce-bounces@ietf.org
X-OriginalArrivalTime: 16 Feb 2005 17:57:14.0959 (UTC)
	FILETIME=[F2930DF0:01C51450]

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: SDP and RTSP extensions defined for 3GPP 
			  Packet-switched Streaming Service
	Author(s)	: M. Westerlund, P. Frojdh
	Filename	: draft-westerlund-mmusic-3gpp-sdp-rtsp-00.txt
	Pages		: 12
	Date		: 2005-2-15
	
3GPP has defined a packet-switched streaming service that uses SDP
   and RTSP with some extensions. This document provides information
   about these extensions and registers the SDP extensions with IANA.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-westerlund-mmusic-3gpp-sdp-rtsp-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-westerlund-mmusic-3gpp-sdp-rtsp-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-westerlund-mmusic-3gpp-sdp-rtsp-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: <2005-2-16102423.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-westerlund-mmusic-3gpp-sdp-rtsp-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-westerlund-mmusic-3gpp-sdp-rtsp-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

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

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

--NextPart--





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

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

--------------050609030701080902050101--



From mmusic-bounces@ietf.org  Wed Feb 23 23:20:27 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16327
	for <mmusic-web-archive@ietf.org>; Wed, 23 Feb 2005 23:20:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D4Ar7-0002s2-I9
	for mmusic-web-archive@ietf.org; Wed, 23 Feb 2005 23:44:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D3zCp-0001MI-2J; Wed, 23 Feb 2005 11:17:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D3zCo-0001M2-38
	for mmusic@megatron.ietf.org; Wed, 23 Feb 2005 11:17:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04197
	for <mmusic@ietf.org>; Wed, 23 Feb 2005 11:17:33 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3zZQ-0006je-Ao
	for mmusic@ietf.org; Wed, 23 Feb 2005 11:41:05 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j1NGHXfm024030
	for <mmusic@ietf.org>; Wed, 23 Feb 2005 17:17:33 +0100 (MET)
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 23 Feb 2005 17:18:12 +0100
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <F3X3DFYR>; Wed, 23 Feb 2005 17:21:05 +0100
Message-ID: <F8EFC4B4A8C016428BC1F589296D4FBF0C6A8914@esealnt630.al.sw.ericsson.se>
From: "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com>
To: "'Sanjay Sinha'" <sanjsinh@cisco.com>, mmusic@ietf.org
Subject: RE: [MMUSIC] Realtime fax draft
Date: Wed, 23 Feb 2005 17:16:56 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 23 Feb 2005 16:18:12.0282 (UTC)
	FILETIME=[455AC1A0:01C519C3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5


Hi,

This has been discussed many times, and at one time I was personally willing to do that (the editor at that time indicated that he would not have the time to do it). However, procedures have been added to one of the T.38 annexes, and the agreement seemed to be that those are enough.

Regards,

Christer Holmberg
Ericsson Finlan

> -----Original Message-----
> From: mmusic-bounces@ietf.org 
> [mailto:mmusic-bounces@ietf.org]On Behalf
> Of Sanjay Sinha
> Sent: 18. helmikuuta 2005 23:41
> To: mmusic@ietf.org
> Subject: [MMUSIC] Realtime fax draft
> 
> 
> There were some emails on sipping list about moving the realtime-fax 
> draft to mmusic group. Was it ever submitted to it? If it was, please 
> send me a link or the rfc #, if it has become an rfc now.
> 
> Thanks,
> Sanjay
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 

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


From mmusic-bounces@ietf.org  Thu Feb 24 01:17:22 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28242
	for <mmusic-web-archive@ietf.org>; Thu, 24 Feb 2005 01:17:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D4CgB-00072S-Uf
	for mmusic-web-archive@ietf.org; Thu, 24 Feb 2005 01:40:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D4Bco-0007wt-3x; Thu, 24 Feb 2005 00:33:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D4Bcl-0007tj-EW
	for mmusic@megatron.ietf.org; Thu, 24 Feb 2005 00:33:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13648
	for <mmusic@ietf.org>; Thu, 24 Feb 2005 00:33:15 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4Bza-0002a5-CZ
	for mmusic@ietf.org; Thu, 24 Feb 2005 00:56:55 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-5.cisco.com with ESMTP; 23 Feb 2005 21:35:16 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.90,111,1107763200"; 
	d="scan'208"; a="162991828:sNHT22191108"
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j1O5X5ZV015032;
	Wed, 23 Feb 2005 21:33:06 -0800 (PST)
Received: from [192.168.0.10] (sjc-vpn4-707.cisco.com [10.21.82.195])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j1O5RTrF011679;
	Wed, 23 Feb 2005 21:27:29 -0800
In-Reply-To: <421CF1FF.3030507@cisco.com>
References: <4219E1D7.3060906@ericsson.com> <421CF1FF.3030507@cisco.com>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <50efcb262597719ff3745f4349296adc@cisco.com>
Content-Transfer-Encoding: 7bit
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [MMUSIC] Key delivery to BFCP clients
Date: Wed, 23 Feb 2005 21:33:03 -0800
To: Flemming Andreasen <fandreas@cisco.com>
X-Mailer: Apple Mail (2.619.2)
IIM-SIG: v:"1.1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1109222849.776964"; x:"432200"; a:"rsa-sha1"; b:"nofws:1172";
	e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2p"
	"XIweAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRUtW+c43sl9jC"
	"50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"PDIYXF8o+KbrP32VZPcBltX5wffKt0jyS8cXb3NtP7ASODi4M4lqZJdm6F5wfen2aZnqJDPB"
	"SpBzDsxLbOkY3vRhoJKclgaihLH9xp5ZOr1L/iBYLa5226TZTn/y/ucaTHNqNnT42jG0LJU4q/C"
	"8hc6Ikuarx7r98OvY5MlZVzU=";
	c:"From: Mark Baugher <mbaugher@cisco.com>";
	c:"Subject: Re: [MMUSIC] Key delivery to BFCP clients";
	c:"Date: Wed, 23 Feb 2005 21:33:03 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
Cc: Keith Drage <drage@lucent.com>, Adam Roach <adam@nostrum.com>,
        mmusic <mmusic@ietf.org>, Joerg Ott <jo@tzi.uni-bremen.de>,
        Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
        Colin Perkins <csp@csperkins.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit

Flemming,

On Feb 23, 2005, at 1:13 PM, Flemming Andreasen wrote:
>
...
> using eithe sdescriptions or kmgmt for this seems like an overkill.
>
> Given that we already have a "k=" attribute defined that seems to 
> satisfy the requirements we have here,

I don't believe that k= satisfied the requirements of keying any 
application and that's why it is being deprecated.  Take SHA-1 for 
example, k= lacks any means to declare what type of key is being used 
and the first key is SHA-1.  But SHA-1 should probably not be the only 
hash function available since it now has reportedly been broken.

Mark
> I don't see any particular reason to come up with another BFCP 
> specific parameter either, but I don't feel strongly about it. If we 
> do use the "k=" field, it should probably be clarified which of the 
> four forms can be used (just "base64" I presume ?). I would also 
> suggest, that the "k=" line can only be used at the session level in 
> case the SDP contains BFCP media streams only, or (simpler and 
> preferred) only allow it to be used at the media layer for BFCP.
>
> -- Flemming
>
>
>
>> Thanks,
>>
>> Gonzalo
>>
>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
>

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


From mmusic-bounces@ietf.org  Thu Feb 24 01:21:32 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29717
	for <mmusic-web-archive@ietf.org>; Thu, 24 Feb 2005 01:21:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D4CkH-0007Y0-KB
	for mmusic-web-archive@ietf.org; Thu, 24 Feb 2005 01:45:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D49MW-0005uB-Vr; Wed, 23 Feb 2005 22:08:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D49MV-0005tP-8W
	for mmusic@megatron.ietf.org; Wed, 23 Feb 2005 22:08:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19776
	for <mmusic@ietf.org>; Wed, 23 Feb 2005 22:08:20 -0500 (EST)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D49jK-0003c0-2H
	for mmusic@ietf.org; Wed, 23 Feb 2005 22:31:58 -0500
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by rtp-iport-1.cisco.com with ESMTP; 23 Feb 2005 22:22:07 -0500
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.90,111,1107752400"; 
	d="scan'208"; a="38166890:sNHT21863964"
Received: from [10.82.240.170] (rtp-vpn2-170.cisco.com [10.82.240.170])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j1O38A1j004733; 
	Wed, 23 Feb 2005 22:08:10 -0500 (EST)
Message-ID: <421CF1FF.3030507@cisco.com>
Date: Wed, 23 Feb 2005 16:13:35 -0500
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [MMUSIC] Key delivery to BFCP clients
References: <4219E1D7.3060906@ericsson.com>
In-Reply-To: <4219E1D7.3060906@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.7 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Content-Transfer-Encoding: 7bit
Cc: Joerg Ott <jo@tzi.uni-bremen.de>, Adam Roach <adam@nostrum.com>,
        mmusic <mmusic@ietf.org>, Keith Drage <drage@lucent.com>,
        Colin Perkins <csp@csperkins.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Content-Transfer-Encoding: 7bit



Gonzalo Camarillo wrote:

> Folks,
>
> the following draft proposes that BFCP floor control servers use the SDP
> 'k' line to deliver a key to BFCP clients.
>
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-bfcp-00.txt
>
> However, SDPnew states the following on the use of the 'k' line:
>
>    A simple
>    mechanism for key exchange is provided by the key field ("k=")
>    although this is primarily supported for compatibility with older
>    implementations and its use is NOT RECOMMENDED.
>
> SDPnew lists as alternatives to the 'k' line MIKEY and the following 
> draft:
>
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions-09.txt 
>
>
> This draft allows a server to send crypto stuff (e.g., algorithm to be
> used) in addition to the key.
>
> The thing is that BFCP clients will not use the key received in the SDP
> to encrypt traffic and therefore, they do not need any additional crypto
> stuff. They will use it to perform a digest-based authentication. That
> is, they will compute a hash of a BFCP message and the key and send it
> to the server to prove that the client sending the BFCP message is the
> same as the one that received the SDP session description.
>
> So, the key received in the SDP is used as a digest password. We need to
> figure out how to transport this password from the server to the client.
> The choices are:
>
> 1) we use the 'k' line and explain why the considerations against its
> use do not apply in this case.
>
> 2) we define a new SDP parameter to carry shared secrets, as opposed to
> encryption keys, in SDP.
>
> My proposal is to go for 1). Any comments or objections?
>
I've only skimmed BFCP, so let me know if I missed anything here, but as 
I understand it, BFCP defines all the parameters associated with the 
cipher and has no options that can be either negotiated or advertised to 
the party that needs to authenticate; all configuration is fixed based 
on the BFCP specification itself. If so, the only thing you need to 
convey is the key to use, and, as you note, we have at least three 
existing options that can be used for that, namely sdescriptions, kmgmt, 
and the "k=" line. Given that :
1) we are looking at something that is completely BFCP specific,
2) both sdescriptions and kmgmt only provide a framework and you would 
need to define specific profiles for use with BFCP (which would use very 
little of their general capabilities)

using eithe sdescriptions or kmgmt for this seems like an overkill.

Given that we already have a "k=" attribute defined that seems to 
satisfy the requirements we have here, I don't see any particular reason 
to come up with another BFCP specific parameter either, but I don't feel 
strongly about it. If we do use the "k=" field, it should probably be 
clarified which of the four forms can be used (just "base64" I presume 
?). I would also suggest, that the "k=" line can only be used at the 
session level in case the SDP contains BFCP media streams only, or 
(simpler and preferred) only allow it to be used at the media layer for 
BFCP.

-- Flemming



> Thanks,
>
> Gonzalo
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
>

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


From mmusic-bounces@ietf.org  Thu Feb 24 01:35:26 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05410
	for <mmusic-web-archive@ietf.org>; Thu, 24 Feb 2005 01:35:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D4Cxk-0000sy-83
	for mmusic-web-archive@ietf.org; Thu, 24 Feb 2005 01:59:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D43Uh-0007bM-Ie; Wed, 23 Feb 2005 15:52:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D43Ua-0007aU-Gk; Wed, 23 Feb 2005 15:52:20 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15029;
	Wed, 23 Feb 2005 15:52:18 -0500 (EST)
Message-Id: <200502232052.PAA15029@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 23 Feb 2005 15:52:17 -0500
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdpng-08.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

	Title		: Session Description and Capability Negotiation
	Author(s)	: D. Kutscher, et al.
	Filename	: draft-ietf-mmusic-sdpng-08.txt
	Pages		: 61
	Date		: 2005-2-23
	
This document defines a language for describing multimedia sessions
   with respect to configuration parameters and capabilities of
   end-systems. The description language is independent of specific
   application scenarios (session announcement, session setup for
   interactive communication etc.) and is not limited to specific media
   types, capabilities, or configuration parameters.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdpng-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-mmusic-sdpng-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-mmusic-sdpng-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: <2005-2-23155818.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-sdpng-08.txt

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

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


--OtherAccess--

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

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

--NextPart--





From mmusic-bounces@ietf.org  Thu Feb 24 02:37:33 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11597
	for <mmusic-web-archive@ietf.org>; Thu, 24 Feb 2005 02:37:33 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D4Dvs-0005M1-3r
	for mmusic-web-archive@ietf.org; Thu, 24 Feb 2005 03:01:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D4DYn-0002dQ-TM; Thu, 24 Feb 2005 02:37:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D4DYY-0002Rj-O0
	for mmusic@megatron.ietf.org; Thu, 24 Feb 2005 02:37:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11571
	for <mmusic@ietf.org>; Thu, 24 Feb 2005 02:37:05 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4DvP-0005KX-Ds
	for mmusic@ietf.org; Thu, 24 Feb 2005 03:00:44 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j1O7b4fm011687
	for <mmusic@ietf.org>; Thu, 24 Feb 2005 08:37:04 +0100 (MET)
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 24 Feb 2005 08:37:44 +0100
Received: from mail.lmf.ericsson.se (dossier.lmf.ericsson.se [131.160.11.13])
	by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id F3X3FPZA; Thu, 24 Feb 2005 08:40:39 +0100
Received: from [131.160.37.196] (EFO9N000L5C7100.lmf.ericsson.se
	[131.160.37.196]) by mail.lmf.ericsson.se (Postfix) with ESMTP
	id 108D718A90; Thu, 24 Feb 2005 09:37:02 +0200 (EET)
Message-ID: <421D8447.5080905@ericsson.com>
Date: Thu, 24 Feb 2005 09:37:43 +0200
X-Sybari-Trust: 93109676 b8ec86c7 779c2aa9 00000139
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [MMUSIC] Key delivery to BFCP clients
References: <50efcb262597719ff3745f4349296adc@cisco.com>
In-Reply-To: <50efcb262597719ff3745f4349296adc@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Feb 2005 07:37:44.0224 (UTC)
	FILETIME=[BA650200:01C51A43]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit
Cc: Flemming Andreasen <fandreas@cisco.com>, Keith Drage <drage@lucent.com>,
        Adam Roach <adam@nostrum.com>, mmusic <mmusic@ietf.org>,
        Joerg Ott <jo@tzi.uni-bremen.de>, Colin Perkins <csp@csperkins.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit

Hi,

given that we have agreed to build support for different hashing
algorithms in BFCP (see email thread in XCON), the 'k' line will not
meet our requirements anymore. I believe we will go for Security
Descriptions.

Thanks,

Gonzalo

Mark Baugher wrote:
> Flemming,
> 
> On Feb 23, 2005, at 1:13 PM, Flemming Andreasen wrote:
> 
> ...
> 
>> using eithe sdescriptions or kmgmt for this seems like an overkill.
>> 
>> 
>> 
>> Given that we already have a "k=" attribute defined that seems to 
>> satisfy the requirements we have here,
> 
> 
> I don't believe that k= satisfied the requirements of keying any 
> application and that's why it is being deprecated.  Take SHA-1 for 
> example, k= lacks any means to declare what type of key is being used
>  and the first key is SHA-1.  But SHA-1 should probably not be the 
> only hash function available since it now has reportedly been broken.
> 
> 
> 
> Mark
> 
>> I don't see any particular reason to come up with another BFCP 
>> specific parameter either, but I don't feel strongly about it. If 
>> we do use the "k=" field, it should probably be clarified which of 
>> the four forms can be used (just "base64" I presume ?). I would 
>> also suggest, that the "k=" line can only be used at the session 
>> level in case the SDP contains BFCP media streams only, or (simpler
>>  and preferred) only allow it to be used at the media layer for 
>> BFCP.
>> 
>> -- Flemming
>> 
>> 
>> 
>> 
>>> Thanks,
>>> 
>>> Gonzalo
>>> 
>>> 
>>> 
>>> _______________________________________________ mmusic mailing 
>>> list mmusic@ietf.org 
>>> https://www1.ietf.org/mailman/listinfo/mmusic
>>> 
>> 
>> _______________________________________________ mmusic mailing list
>>  mmusic@ietf.org https://www1.ietf.org/mailman/listinfo/mmusic
>> 

-- 
Gonzalo Camarillo         Phone :  +358  9 299 33 71
Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
Telecom R&D               Fax   :  +358  9 299 30 52
FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
Finland                   http://www.hut.fi/~gonzalo

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


From mmusic-bounces@ietf.org  Thu Feb 24 09:24:00 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23983
	for <mmusic-web-archive@ietf.org>; Thu, 24 Feb 2005 09:24:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D4KHH-00071a-CG
	for mmusic-web-archive@ietf.org; Thu, 24 Feb 2005 09:47:43 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D4Jr8-0007Tg-J4; Thu, 24 Feb 2005 09:20:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D4Jr7-0007SK-JW
	for mmusic@megatron.ietf.org; Thu, 24 Feb 2005 09:20:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23420
	for <mmusic@ietf.org>; Thu, 24 Feb 2005 09:20:39 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4KE0-0006ti-TF
	for mmusic@ietf.org; Thu, 24 Feb 2005 09:44:22 -0500
Received: from tzi.uni-bremen.de (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	j1OEK8W5007069; Thu, 24 Feb 2005 15:20:20 +0100 (MET)
Message-ID: <421DE298.3090506@tzi.uni-bremen.de>
Date: Thu, 24 Feb 2005 15:20:08 +0100
From: Joerg Ott <jo@tzi.uni-bremen.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mmusic@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit
Cc: Colin Perkins <csp@csperkins.org>
Subject: [MMUSIC] MMUSIC at 62nd IETF
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit

Folks,

MMUSIC is scheduled to meet once at the next IETF:

----------------------------------------------------------
THURSDAY, March 10, 2005
1530-1630 Afternoon Sessions II
TSV  mmusic     Multiparty Multimedia Session Control WG

1645-1745 Afternoon Sessions III
TSV  mmusic     Multiparty Multimedia Session Control WG
----------------------------------------------------------

We have already collected several agenda requests.

If you have an active Internet Draft in the scope of the
MMUSIC charter with issues warranting face-to-face discussion,
please drop an email to Colin and myself so that we can
finalize the agenda soon.

In your request, please note the I-D you are referring to
and list the most important aspects to be discussed during
the meeting.

And, of course, remember the "Note well" statement.

Thanks,
Joerg




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


From mmusic-bounces@ietf.org  Thu Feb 24 10:45:22 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04714
	for <mmusic-web-archive@ietf.org>; Thu, 24 Feb 2005 10:45:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D4LY0-0000qO-TC
	for mmusic-web-archive@ietf.org; Thu, 24 Feb 2005 11:09:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D4L8h-0004X4-A2; Thu, 24 Feb 2005 10:42:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D4L8f-0004Wt-Ki
	for mmusic@megatron.ietf.org; Thu, 24 Feb 2005 10:42:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04399
	for <mmusic@ietf.org>; Thu, 24 Feb 2005 10:42:51 -0500 (EST)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4LVb-0000m8-0n
	for mmusic@ietf.org; Thu, 24 Feb 2005 11:06:35 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-1.cisco.com with ESMTP; 24 Feb 2005 10:56:43 -0500
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.90,114,1107752400"; 
	d="scan'208"; a="38229432:sNHT20217310"
Received: from [10.82.240.170] (rtp-vpn2-170.cisco.com [10.82.240.170])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j1OFgehF017076; 
	Thu, 24 Feb 2005 10:42:41 -0500 (EST)
Message-ID: <421DF5F0.20608@cisco.com>
Date: Thu, 24 Feb 2005 10:42:40 -0500
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [MMUSIC] Key delivery to BFCP clients
References: <50efcb262597719ff3745f4349296adc@cisco.com>
	<421D8447.5080905@ericsson.com>
In-Reply-To: <421D8447.5080905@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Content-Transfer-Encoding: 7bit
Cc: Keith Drage <drage@lucent.com>, Adam Roach <adam@nostrum.com>,
        Mark Baugher <mbaugher@cisco.com>, Joerg Ott <jo@tzi.uni-bremen.de>,
        Colin Perkins <csp@csperkins.org>, mmusic <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Content-Transfer-Encoding: 7bit



Gonzalo Camarillo wrote:

> Hi,
>
> given that we have agreed to build support for different hashing
> algorithms in BFCP (see email thread in XCON), the 'k' line will not
> meet our requirements anymore. I believe we will go for Security
> Descriptions.

OK. I presume the offer will then contain one or more hashing algorithms 
and associated data, and the answerer will choose one of them. One 
problem we found when doing sdescriptions here was the race between the 
answer coming back, and a media packet that was secured according to 
parameters provided in the answer. Security preconditions have been 
defined to address that, but they add to overall session setup delay. If 
you have the option of making the BFCP digest attributes self-contained 
inasmuch as they can completely identify which of the offered options 
was actually chosen, you can avoid this race.

-- Flemming


>
> Thanks,
>
> Gonzalo
>
> Mark Baugher wrote:
>
>> Flemming,
>>
>> On Feb 23, 2005, at 1:13 PM, Flemming Andreasen wrote:
>>
>> ...
>>
>>> using eithe sdescriptions or kmgmt for this seems like an overkill.
>>>
>>>
>>>
>>> Given that we already have a "k=" attribute defined that seems to 
>>> satisfy the requirements we have here,
>>
>>
>>
>> I don't believe that k= satisfied the requirements of keying any 
>> application and that's why it is being deprecated.  Take SHA-1 for 
>> example, k= lacks any means to declare what type of key is being used
>>  and the first key is SHA-1.  But SHA-1 should probably not be the 
>> only hash function available since it now has reportedly been broken.
>>
>>
>>
>> Mark
>>
>>> I don't see any particular reason to come up with another BFCP 
>>> specific parameter either, but I don't feel strongly about it. If we 
>>> do use the "k=" field, it should probably be clarified which of the 
>>> four forms can be used (just "base64" I presume ?). I would also 
>>> suggest, that the "k=" line can only be used at the session level in 
>>> case the SDP contains BFCP media streams only, or (simpler
>>>  and preferred) only allow it to be used at the media layer for BFCP.
>>>
>>> -- Flemming
>>>
>>>
>>>
>>>
>>>> Thanks,
>>>>
>>>> Gonzalo
>>>>
>>>>
>>>>
>>>> _______________________________________________ mmusic mailing list 
>>>> mmusic@ietf.org https://www1.ietf.org/mailman/listinfo/mmusic
>>>>
>>>
>>> _______________________________________________ mmusic mailing list
>>>  mmusic@ietf.org https://www1.ietf.org/mailman/listinfo/mmusic
>>>
>

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


From mmusic-bounces@ietf.org  Fri Feb 25 02:08:23 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25485
	for <mmusic-web-archive@ietf.org>; Fri, 25 Feb 2005 02:08:23 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D4ZaP-0000sc-UU
	for mmusic-web-archive@ietf.org; Fri, 25 Feb 2005 02:08:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D4ZXM-0006Bm-A6; Fri, 25 Feb 2005 02:05:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D4ZWi-0005IW-Bh
	for mmusic@megatron.ietf.org; Fri, 25 Feb 2005 02:04:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22081
	for <mmusic@ietf.org>; Fri, 25 Feb 2005 02:04:38 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4ZWm-0000pC-N4
	for mmusic@ietf.org; Fri, 25 Feb 2005 02:04:45 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j1P74ZO6022928 for <mmusic@ietf.org>; Fri, 25 Feb 2005 08:04:35 +0100
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by
	esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 25 Feb 2005 08:05:17 +0100
Received: from mail.lmf.ericsson.se (dossier.lmf.ericsson.se [131.160.11.13])
	by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id FLYLJX4S; Fri, 25 Feb 2005 08:07:27 +0100
Received: from [131.160.37.196] (EFO9N000L5C7100.lmf.ericsson.se
	[131.160.37.196]) by mail.lmf.ericsson.se (Postfix) with ESMTP
	id C08D0189CC; Fri, 25 Feb 2005 09:04:34 +0200 (EET)
Message-ID: <421ECE2B.20508@ericsson.com>
Date: Fri, 25 Feb 2005 09:05:15 +0200
X-Sybari-Trust: 053126ed b8ec86c7 113fe2bc 00000139
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Flemming Andreasen <fandreas@cisco.com>
Subject: Re: [MMUSIC] Key delivery to BFCP clients
References: <50efcb262597719ff3745f4349296adc@cisco.com>
	<421D8447.5080905@ericsson.com> <421DF5F0.20608@cisco.com>
In-Reply-To: <421DF5F0.20608@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Feb 2005 07:05:17.0962 (UTC)
	FILETIME=[5CBEBEA0:01C51B08]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Content-Transfer-Encoding: 7bit
Cc: Keith Drage <drage@lucent.com>, Adam Roach <adam@nostrum.com>,
        Mark Baugher <mbaugher@cisco.com>, Joerg Ott <jo@tzi.uni-bremen.de>,
        Colin Perkins <csp@csperkins.org>, mmusic <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Content-Transfer-Encoding: 7bit

Hi Flemming,

yes, the BFCP attribute carrying the digest will be self-contained. It 
will carry the actual digest plus an algorithm identifier.

Thanks,

Gonzalo

Flemming Andreasen wrote:
> 
> 
> Gonzalo Camarillo wrote:
> 
>> Hi,
>>
>> given that we have agreed to build support for different hashing
>> algorithms in BFCP (see email thread in XCON), the 'k' line will not
>> meet our requirements anymore. I believe we will go for Security
>> Descriptions.
> 
> 
> OK. I presume the offer will then contain one or more hashing algorithms 
> and associated data, and the answerer will choose one of them. One 
> problem we found when doing sdescriptions here was the race between the 
> answer coming back, and a media packet that was secured according to 
> parameters provided in the answer. Security preconditions have been 
> defined to address that, but they add to overall session setup delay. If 
> you have the option of making the BFCP digest attributes self-contained 
> inasmuch as they can completely identify which of the offered options 
> was actually chosen, you can avoid this race.
> 
> -- Flemming
> 
> 
>>
>> Thanks,
>>
>> Gonzalo
>>
>> Mark Baugher wrote:
>>
>>> Flemming,
>>>
>>> On Feb 23, 2005, at 1:13 PM, Flemming Andreasen wrote:
>>>
>>> ...
>>>
>>>> using eithe sdescriptions or kmgmt for this seems like an overkill.
>>>>
>>>>
>>>>
>>>> Given that we already have a "k=" attribute defined that seems to 
>>>> satisfy the requirements we have here,
>>>
>>>
>>>
>>>
>>> I don't believe that k= satisfied the requirements of keying any 
>>> application and that's why it is being deprecated.  Take SHA-1 for 
>>> example, k= lacks any means to declare what type of key is being used
>>>  and the first key is SHA-1.  But SHA-1 should probably not be the 
>>> only hash function available since it now has reportedly been broken.
>>>
>>>
>>>
>>> Mark
>>>
>>>> I don't see any particular reason to come up with another BFCP 
>>>> specific parameter either, but I don't feel strongly about it. If we 
>>>> do use the "k=" field, it should probably be clarified which of the 
>>>> four forms can be used (just "base64" I presume ?). I would also 
>>>> suggest, that the "k=" line can only be used at the session level in 
>>>> case the SDP contains BFCP media streams only, or (simpler
>>>>  and preferred) only allow it to be used at the media layer for BFCP.
>>>>
>>>> -- Flemming
>>>>
>>>>
>>>>
>>>>
>>>>> Thanks,
>>>>>
>>>>> Gonzalo
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________ mmusic mailing list 
>>>>> mmusic@ietf.org https://www1.ietf.org/mailman/listinfo/mmusic
>>>>>
>>>>
>>>> _______________________________________________ mmusic mailing list
>>>>  mmusic@ietf.org https://www1.ietf.org/mailman/listinfo/mmusic
>>>>
>>

-- 
Gonzalo Camarillo         Phone :  +358  9 299 33 71
Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
Telecom R&D               Fax   :  +358  9 299 30 52
FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
Finland                   http://www.hut.fi/~gonzalo

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


From mmusic-bounces@ietf.org  Fri Feb 25 03:49:25 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17340
	for <mmusic-web-archive@ietf.org>; Fri, 25 Feb 2005 03:49:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D4bAB-0002uO-Sy
	for mmusic-web-archive@ietf.org; Fri, 25 Feb 2005 03:49:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D4b9x-0005j4-87; Fri, 25 Feb 2005 03:49:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D4b9v-0005iy-Kp
	for mmusic@megatron.ietf.org; Fri, 25 Feb 2005 03:49:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17332
	for <mmusic@ietf.org>; Fri, 25 Feb 2005 03:49:13 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4b9z-0002uA-VR
	for mmusic@ietf.org; Fri, 25 Feb 2005 03:49:21 -0500
Received: from esealmw128.eemea.ericsson.se ([153.88.254.121])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j1P8lVTm017210 for <mmusic@ietf.org>; Fri, 25 Feb 2005 09:49:11 +0100
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 25 Feb 2005 09:48:24 +0100
Received: from [147.214.237.66] ([147.214.237.66]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 25 Feb 2005 09:48:24 +0100
Message-ID: <421EE629.7000207@ericsson.com>
Date: Fri, 25 Feb 2005 09:47:37 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mmusic@ietf.org
References: <200502232051.PAA14983@ietf.org>
In-Reply-To: <200502232051.PAA14983@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Feb 2005 08:48:24.0353 (UTC)
	FILETIME=[C41F1910:01C51B16]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Re: I-D ACTION:draft-ietf-mmusic-rfc2326bis-09.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit

Hi,

A new version of the RTSP core spec is available.

> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-rfc2326bis-09.txt
> 

The major updates in this version are:

- Explicit spacing rules for the ABNF Syntax.
- Update of the text in the connection section. Some text has been moved 
to other chapters.

Unfortunately there is a number of editing task still not done.

Cheers

Magnus Westerlund

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

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


From mmusic-bounces@ietf.org  Fri Feb 25 04:17:06 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21371
	for <mmusic-web-archive@ietf.org>; Fri, 25 Feb 2005 04:17:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D4bb0-0003hb-Fl
	for mmusic-web-archive@ietf.org; Fri, 25 Feb 2005 04:17:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D4bZC-0002e2-IP; Fri, 25 Feb 2005 04:15:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D4bYy-0002KK-1q
	for mmusic@megatron.ietf.org; Fri, 25 Feb 2005 04:15:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21231
	for <mmusic@ietf.org>; Fri, 25 Feb 2005 04:15:05 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4bZ3-0003fm-PV
	for mmusic@ietf.org; Fri, 25 Feb 2005 04:15:14 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j1P9F5O6025559 for <mmusic@ietf.org>; Fri, 25 Feb 2005 10:15:06 +0100
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 25 Feb 2005 10:15:48 +0100
Received: from [147.214.237.66] (minint-gdmfmb [147.214.237.66]) by
	esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id FLYLKH67; Fri, 25 Feb 2005 10:17:57 +0100
Message-ID: <421EEC99.6060004@ericsson.com>
Date: Fri, 25 Feb 2005 10:15:05 +0100
X-Sybari-Trust: 3dae806d b8ec86c7 113fe2bc 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "mmusic (E-mail)" <mmusic@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Feb 2005 09:15:48.0365 (UTC)
	FILETIME=[98076BD0:01C51B1A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] RTSP: Explicit white spacing in ABNF Syntax
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 7bit

Hi,

I have in the latest version worked on the ABNF syntax. I added explicit 
white spacing rules and also tried running it through an ABNF validator. 
The version in the draft contains some short comings, like missing rules 
etc which is being worked to be fixed. So do note that it contains some 
known errors. However to be able to complete the work I need your input 
on a few things. So lets walk through the major changes and potential 
issues with the explicit white spacing rules.


A. It is intended that all RTSP headers has the following base syntax:
message-header  =  field-name HCOLON [ field-value ] CRLF
Where HCOLON is:
    LWS            =  [CRLF] 1*( SP / HT )
    SWS            =  [LWS] ; sep whitespace
    HCOLON         =  *( SP / HTAB ) ":" SWS

This shouldn't be a problem and follows also SIP.

B. The changing of the comma separated list, which was 1# and then was 
written as RULE 1*("," RULE), which is now RULE 1*(COMMA RULE) where 
COMMA is:
COMMA   =  SWS "," SWS ; comma

Thus is allows white spaces on both sides of the comma. This shouldn't 
be a problem either.

C. What could be more problematic is the usage of the EQUAL rule:
EQUAL   =  SWS "=" SWS ; equal
This rules has been used to replace basically all "=" in the syntax with 
the exception of the range headers.
So for example the transport header parameter:
"source" "=" host
has become
"source" EQUAL host

D. Replacement of ";" in most places with the rule:
SEMI    =  SWS ";" SWS ; semicolon

Please do consider especially in the transport header where it now would 
explicit that spacing can be inserted on either side of the ";".

Please provide comments on this or other things in the syntax.

Cheers

Magnus Westerlund

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

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


From mmusic-bounces@ietf.org  Sat Feb 26 08:23:25 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29208
	for <mmusic-web-archive@ietf.org>; Sat, 26 Feb 2005 08:23:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D51v9-0003Mi-VL
	for mmusic-web-archive@ietf.org; Sat, 26 Feb 2005 08:23:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D51rs-0003jr-RS; Sat, 26 Feb 2005 08:20:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D4Ql2-0001fz-UT
	for mmusic@megatron.ietf.org; Thu, 24 Feb 2005 16:42:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24992
	for <mmusic@ietf.org>; Thu, 24 Feb 2005 16:42:50 -0500 (EST)
Received: from vreme.yubc.net ([212.124.160.13])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4Ql1-0005Cm-Cp
	for mmusic@ietf.org; Thu, 24 Feb 2005 16:42:52 -0500
Received: from vreme.yubc.net (localhost.localdomain [127.0.0.1])
	by vreme.yubc.net (8.12.11/8.12.11) with ESMTP id j1OLgf8V021214
	for <mmusic@ietf.org>; Thu, 24 Feb 2005 22:42:41 +0100
Received: (from root@localhost)
	by vreme.yubc.net (8.12.11/8.12.11/Submit) id j1OLgfo8021212
	for mmusic@ietf.org; Thu, 24 Feb 2005 22:42:41 +0100
Date: Thu, 24 Feb 2005 22:42:41 +0100
From: IPSI Transactions Special Issues <ipsitrans@vreme.yubc.net>
Message-Id: <200502242142.j1OLgfo8021212@vreme.yubc.net>
To: mmusic@ietf.org
X-Spam-Score: 2.2 (++)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
X-Mailman-Approved-At: Sat, 26 Feb 2005 08:20:23 -0500
Subject: [MMUSIC] Call for IPSI Transactions Special Issues in 2005/6; c/ba
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 2.2 (++)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

Dear potential Speaker:

We are pleased to inform you that both IPSI Transactions journals are planing some special issues in late 2005 and early 2006, and you are welcome to submit your paper(s), until the deadlines listed below!

IPSI Transactions on Internet Research:

March 31, 2005 -
Special Issue on E-Education: Concepts and Infrastructure

June 30, 2005 -
Special Issue on E-Business: Concepts and Infrastructure


IPSI Transactions on Advanced Research:

March 31, 2005 -
Special Issue on the Research with Multidisciplinary Elements

June 30, 2005 -
Special Issue on the Research with Interdisciplinary Elements

Each submitted paper first undergoes the editor review, and those who pass this first stage are sent to 12 external experts for a rigorous review; decisions are made after at least 6 external reviewers respond! The review is free of charge, but the authors of the accepted papers ar expected to pay the publication fee of E400 per paper (if 4 or 5 or 6 pages of the TIR/TAR format), and the additional fee of E100 per page, for each extra page, till the maximum of 10 pages.

Rigorous reviewing is the major strength of IPSI journals, which is the major contributor to their high quality! Soft copies of the existing issues of TIR and TAR can be seen at the web, and hard copies can be obtained on a special request by email, as indicated on the web, where can find all information!

Sincerely yours,

Prof. Dr. Veljko Milutinovic, Editor-in-Chief

P.S. If you need aditional information, please reply to this e-mail.

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


From mmusic-bounces@ietf.org  Sat Feb 26 08:25:28 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29377
	for <mmusic-web-archive@ietf.org>; Sat, 26 Feb 2005 08:25:28 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D51x6-0003PO-Rm
	for mmusic-web-archive@ietf.org; Sat, 26 Feb 2005 08:25:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D51rs-0003j5-H1; Sat, 26 Feb 2005 08:20:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D40Ey-00040d-6R
	for mmusic@megatron.ietf.org; Wed, 23 Feb 2005 12:24:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15045
	for <mmusic@ietf.org>; Wed, 23 Feb 2005 12:23:52 -0500 (EST)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D40bb-0001Mb-QI
	for mmusic@ietf.org; Wed, 23 Feb 2005 12:47:25 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-2.cisco.com with ESMTP; 23 Feb 2005 12:23:45 -0500
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from cisco.com (dhcp-64-102-92-206.cisco.com [64.102.92.206])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j1NHNhhF027334; 
	Wed, 23 Feb 2005 12:23:43 -0500 (EST)
Message-ID: <421CBC1E.9020503@cisco.com>
Date: Wed, 23 Feb 2005 12:23:42 -0500
From: Sanjay Sinha <sanjsinh@cisco.com>
Organization: Cisco Systems
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Realtime fax draft
References: <F8EFC4B4A8C016428BC1F589296D4FBF0C6A8914@esealnt630.al.sw.ericsson.se>
In-Reply-To: <F8EFC4B4A8C016428BC1F589296D4FBF0C6A8914@esealnt630.al.sw.ericsson.se>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sat, 26 Feb 2005 08:20:23 -0500
Cc: mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit

Hi Christer,

Thanks for your response. I was looking for some refrences to fallback 
to passthrogh if T.38 fails and there were some examples in sec. 6.2.1 
of the realtimefax draft. I did not find any mention of it in T.38 
specification. Can you point me to the annex which has it?

Sanjay

Christer Holmberg (JO/LMF) wrote:

>Hi,
>
>This has been discussed many times, and at one time I was personally willing to do that (the editor at that time indicated that he would not have the time to do it). However, procedures have been added to one of the T.38 annexes, and the agreement seemed to be that those are enough.
>
>Regards,
>
>Christer Holmberg
>Ericsson Finlan
>
>  
>
>>-----Original Message-----
>>From: mmusic-bounces@ietf.org 
>>[mailto:mmusic-bounces@ietf.org]On Behalf
>>Of Sanjay Sinha
>>Sent: 18. helmikuuta 2005 23:41
>>To: mmusic@ietf.org
>>Subject: [MMUSIC] Realtime fax draft
>>
>>
>>There were some emails on sipping list about moving the realtime-fax 
>>draft to mmusic group. Was it ever submitted to it? If it was, please 
>>send me a link or the rfc #, if it has become an rfc now.
>>
>>Thanks,
>>Sanjay
>>
>>_______________________________________________
>>mmusic mailing list
>>mmusic@ietf.org
>>https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>    
>>

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


From mmusic-bounces@ietf.org  Sun Feb 27 13:41:12 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21462
	for <mmusic-web-archive@ietf.org>; Sun, 27 Feb 2005 13:41:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D5TMV-00038Q-IP
	for mmusic-web-archive@ietf.org; Sun, 27 Feb 2005 13:41:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D5TLR-0002yP-Fe; Sun, 27 Feb 2005 13:40:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D5TLP-0002y7-6v
	for mmusic@megatron.ietf.org; Sun, 27 Feb 2005 13:40:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21411
	for <mmusic@ietf.org>; Sun, 27 Feb 2005 13:40:40 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D5TLz-00037r-LC
	for mmusic@ietf.org; Sun, 27 Feb 2005 13:41:20 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j1RIefO6029197 for <mmusic@ietf.org>; Sun, 27 Feb 2005 19:40:41 +0100
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Sun, 27 Feb 2005 19:41:25 +0100
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <F3X3S14A>; Sun, 27 Feb 2005 19:44:29 +0100
Message-ID: <F8EFC4B4A8C016428BC1F589296D4FBF0C6A8952@esealnt630.al.sw.ericsson.se>
From: "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com>
To: "'Sanjay Sinha'" <sanjsinh@cisco.com>
Subject: RE: [MMUSIC] Realtime fax draft
Date: Sun, 27 Feb 2005 19:40:02 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 27 Feb 2005 18:41:25.0360 (UTC)
	FILETIME=[F0E16700:01C51CFB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8


Hi Sanjay,

I am not sure if the specific use-case you mention exist in any document (I don't have the annex in front of me at the moment). My answer was more generic about why it was decided not to update the T.38 call-flows draft.

Regards,

Christer Holmberg
Ericsson Finland

> -----Original Message-----
> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org]
> Sent: 23. helmikuuta 2005 19:24
> To: Christer Holmberg (JO/LMF)
> Cc: mmusic@ietf.org
> Subject: Re: [MMUSIC] Realtime fax draft
> 
> 
> Hi Christer,
> 
> Thanks for your response. I was looking for some refrences to 
> fallback 
> to passthrogh if T.38 fails and there were some examples in 
> sec. 6.2.1 
> of the realtimefax draft. I did not find any mention of it in T.38 
> specification. Can you point me to the annex which has it?
> 
> Sanjay
> 
> Christer Holmberg (JO/LMF) wrote:
> 
> >Hi,
> >
> >This has been discussed many times, and at one time I was 
> personally willing to do that (the editor at that time 
> indicated that he would not have the time to do it). However, 
> procedures have been added to one of the T.38 annexes, and 
> the agreement seemed to be that those are enough.
> >
> >Regards,
> >
> >Christer Holmberg
> >Ericsson Finlan
> >
> >  
> >
> >>-----Original Message-----
> >>From: mmusic-bounces@ietf.org 
> >>[mailto:mmusic-bounces@ietf.org]On Behalf
> >>Of Sanjay Sinha
> >>Sent: 18. helmikuuta 2005 23:41
> >>To: mmusic@ietf.org
> >>Subject: [MMUSIC] Realtime fax draft
> >>
> >>
> >>There were some emails on sipping list about moving the 
> realtime-fax 
> >>draft to mmusic group. Was it ever submitted to it? If it 
> was, please 
> >>send me a link or the rfc #, if it has become an rfc now.
> >>
> >>Thanks,
> >>Sanjay
> >>
> >>_______________________________________________
> >>mmusic mailing list
> >>mmusic@ietf.org
> >>https://www1.ietf.org/mailman/listinfo/mmusic
> >>
> >>    
> >>
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 

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


