From mmusic-bounces@ietf.org Mon Oct 01 11:36:50 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IcNIm-000854-HT; Mon, 01 Oct 2007 11:35:20 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IcNIl-00084x-Fo
	for mmusic@ietf.org; Mon, 01 Oct 2007 11:35:19 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IcNIl-0005iJ-67
	for mmusic@ietf.org; Mon, 01 Oct 2007 11:35:19 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 01 Oct 2007 08:35:18 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l91FZIou029620; 
	Mon, 1 Oct 2007 08:35:18 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l91FZI1g028413;
	Mon, 1 Oct 2007 15:35:18 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 1 Oct 2007 08:35:18 -0700
Received: from [171.70.219.177] ([171.70.219.177]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 1 Oct 2007 08:35:18 -0700
Message-ID: <470113CC.2020408@cisco.com>
Date: Mon, 01 Oct 2007 11:35:40 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] ICE and MSRP
References: <CA9998CD4A020D418654FCDEF4E707DF0234F986@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0234F986@esealmw113.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Oct 2007 15:35:18.0275 (UTC)
	FILETIME=[AB8EF530:01C80440]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=993; t=1191252918;
	x=1192116918; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20[MMUSIC]=20ICE=20and=20MSRP |Sender:=20;
	bh=keledZOb0QBn4VutQU055hb4x5RtwwTIrLbt2KJwwvY=;
	b=Zutk0F8bwsMPje7hbVxJzFd7isto0zRJq9IrDow6CwdOO/k4hmoxlx7OyW366Wj3fuke+ATK
	bNznlmnS/PVS3BfpM9Xp/KhQHg3OS4MxnbTjqhCXEqShUm+WYp2incXA50ut4PpqATUSRuZTjH
	Y4rBeqPhKpFXJ6oFCNfO9lrx0=;
Authentication-Results: sj-dkim-1; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
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>
Errors-To: mmusic-bounces@ietf.org

This draft was written:
http://www.watersprings.org/pub/id/draft-niemi-simple-msrp-ice-00.txt

where TURN is used as an alternative to MSRP relays.

-Jonathan R.

Christer Holmberg wrote:
> 
> Hi,
> 
> Has there been any discussions/studies on how ICE works with MSRP, where 
> routing is not done based on SDP m/c/candidate information, but on 
> information in the MSRP messages themselves?
> 
> Regards,
> 
> Christer
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic

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

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



From mmusic-bounces@ietf.org Tue Oct 02 02:43:50 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IcbS3-0007me-Ng; Tue, 02 Oct 2007 02:41:51 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IcbS2-0007jq-02
	for mmusic@ietf.org; Tue, 02 Oct 2007 02:41:50 -0400
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IcbS1-00018C-Fa
	for mmusic@ietf.org; Tue, 02 Oct 2007 02:41:49 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l926fb1i005874; Tue, 2 Oct 2007 09:41:44 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 2 Oct 2007 09:41:44 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 2 Oct 2007 09:41:43 +0300
Received: from [10.144.22.123] ([10.144.22.123]) by esebh102.NOE.Nokia.com
	over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 2 Oct 2007 09:41:43 +0300
Message-ID: <4701E827.8090709@nsn.com>
Date: Tue, 02 Oct 2007 09:41:43 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@cisco.com>
Subject: Re: [MMUSIC] ICE and MSRP
References: <CA9998CD4A020D418654FCDEF4E707DF0234F986@esealmw113.eemea.ericsson.se>
	<470113CC.2020408@cisco.com>
In-Reply-To: <470113CC.2020408@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Oct 2007 06:41:43.0052 (UTC)
	FILETIME=[4B695CC0:01C804BF]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: mmusic@ietf.org, Christer Holmberg <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>
Errors-To: mmusic-bounces@ietf.org

You may also find this one of interest:

http://www.ietf.org/internet-drafts/draft-denis-simple-msrp-comedia-00.txt

/Miguel

Jonathan Rosenberg wrote:
> This draft was written:
> http://www.watersprings.org/pub/id/draft-niemi-simple-msrp-ice-00.txt
> 
> where TURN is used as an alternative to MSRP relays.
> 
> -Jonathan R.
> 
> Christer Holmberg wrote:
>>
>> Hi,
>>
>> Has there been any discussions/studies on how ICE works with MSRP, 
>> where routing is not done based on SDP m/c/candidate information, but 
>> on information in the MSRP messages themselves?
>>
>> Regards,
>>
>> Christer
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mmusic
> 

-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Espoo, Finland


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



From mmusic-bounces@ietf.org Tue Oct 02 18:39:38 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IcqMg-0006go-Ib; Tue, 02 Oct 2007 18:37:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IcqMd-0006bc-KW
	for mmusic@ietf.org; Tue, 02 Oct 2007 18:37:15 -0400
Received: from wa-out-1112.google.com ([209.85.146.183])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IcqMX-0007wu-Bj
	for mmusic@ietf.org; Tue, 02 Oct 2007 18:37:15 -0400
Received: by wa-out-1112.google.com with SMTP id k40so7196717wah
	for <mmusic@ietf.org>; Tue, 02 Oct 2007 15:36:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth;
	bh=WDGM5xaRP4I8vGwqj4D51uIZmP2EGfk2ypvW2bU2M5w=;
	b=cI44DRfYvPYuw2/LeI9wOV+o+3iy8scyfYxCpEMzZpfVMqiMB6v7Y95/RTfT1hvzjxjkPOmZW0vYsFC46Avv2YUkBqnLDLK/1btmCcc4MP4iIMs6isBjSr0tMZoPLGhkMiquAZzC1ek6uwEUJajID/tBnq5O3zAW1J0JxOjunY4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth;
	b=Vc/KO8uwqOO/0hBI0hFwuTFr5+MpEEYyncTI6ReRzEEpQiHOEHS35HQvs/d73VZiYZfu8TPWMlIVkFVrAMc9ngyydvusRfCaP0uZiUJ1zaAU3YICzjqH1FVo8zYjSIukLto+ljKU/nqIwzcXP8Y4rel1tB3CRqhygM956yAaaZM=
Received: by 10.115.17.1 with SMTP id u1mr1988077wai.1191364602111;
	Tue, 02 Oct 2007 15:36:42 -0700 (PDT)
Received: by 10.115.78.9 with HTTP; Tue, 2 Oct 2007 15:36:42 -0700 (PDT)
Message-ID: <f40963db0710021536o62015b51j40ee2c22a9f8b66f@mail.gmail.com>
Date: Tue, 2 Oct 2007 18:36:42 -0400
From: "Adam Fisk" <a@lastbamboo.org>
To: mmusic@ietf.org
Subject: [MMUSIC] ICE retransmitted Binding Request processing
MIME-Version: 1.0
X-Google-Sender-Auth: c5e00346440ada4d
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
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="===============1067153477=="
Errors-To: mmusic-bounces@ietf.org

--===============1067153477==
Content-Type: multipart/alternative; 
	boundary="----=_Part_19545_8826994.1191364602108"

------=_Part_19545_8826994.1191364602108
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I've noticed in my ICE tests that it's quite common for a peer to receive
multiple Binding Requests for the same STUN transaction as a result of STUN
retransmissions.

While this is to be expected, the processing of the request specified in ICE
18 section 7.2.1.4 "Triggered Checks" results in adding precisely the same
candidate pair to the triggered check queue multiple times, resulting in
multiple subsequent identical triggered checks and subsequent work.  Is this
the expected behavior, or am I missing something?  While it doesn't seem the
above will break anything, it doesn't appear optimal either.

Should the triggered check queue filter duplicates?  Should the STUN server
side in ICE ignore Binding Requests with transaction IDs it has already
processed (clearly still sending Binding Responses, just not forwarding the
request to the ICE procedures)?  I'd assume the latter, but it seems I must
be missing something in one of the specs if this is the case.

This is assuming the ICE STUN server side just reprocesses each Binding
Request and recomputes the Binding Response each time since the Binding
method is idempotent, as specified in draft-ietf-behave-rfc3489bis-10
section 7.3.1 "Processing a Request."

Thanks very much.

-Adam Fisk

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

I&#39;ve noticed in my ICE tests that it&#39;s quite common for a peer to receive multiple Binding Requests for the same STUN transaction as a result of STUN retransmissions.&nbsp; <br><br>While this is to be expected, the processing of the request specified in ICE 18 section 
<a href="http://7.2.1.4">7.2.1.4</a> &quot;Triggered Checks&quot; results in adding precisely the same candidate pair to the triggered check queue multiple times, resulting in multiple subsequent identical triggered checks and subsequent work.&nbsp; Is this the expected behavior, or am I missing something?&nbsp; While it doesn&#39;t seem the above will break anything, it doesn&#39;t appear optimal either.&nbsp; 
<br><br>Should the triggered check queue filter duplicates?&nbsp; Should the STUN server side in ICE ignore Binding Requests with transaction IDs it has already processed (clearly still sending Binding Responses, just not forwarding the request to the ICE procedures)?&nbsp; I&#39;d assume the latter, but it seems I must be missing something in one of the specs if this is the case.
<br><br>This is assuming the ICE STUN server side just reprocesses each Binding Request and recomputes the Binding Response each time since the Binding method is idempotent, as specified in draft-ietf-behave-rfc3489bis-10 section 
7.3.1 &quot;Processing a Request.&quot;<br><br>Thanks very much.<br><br>-Adam Fisk<br><a name="section-7.3.1"></a><pre><span class="h4"><h4></h4></span></pre>

------=_Part_19545_8826994.1191364602108--


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

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

--===============1067153477==--




From mmusic-bounces@ietf.org Wed Oct 03 03:45:21 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Icysb-0003fR-Hj; Wed, 03 Oct 2007 03:42:49 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Icysa-0003ar-RS
	for mmusic@ietf.org; Wed, 03 Oct 2007 03:42:48 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IcysX-0007MG-34
	for mmusic@ietf.org; Wed, 03 Oct 2007 03:42:45 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	475C820D0E; Wed,  3 Oct 2007 09:42:44 +0200 (CEST)
X-AuditID: c1b4fb3c-b067fbb0000007e1-da-470347f4955a
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	33C0A20C3D; Wed,  3 Oct 2007 09:42:44 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 3 Oct 2007 09:42:43 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 3 Oct 2007 09:42:43 +0200
Message-ID: <470347F3.9050908@ericsson.com>
Date: Wed, 03 Oct 2007 09:42:43 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Adam Fisk <a@lastbamboo.org>
Subject: Re: [MMUSIC] ICE retransmitted Binding Request processing
References: <f40963db0710021536o62015b51j40ee2c22a9f8b66f@mail.gmail.com>
In-Reply-To: <f40963db0710021536o62015b51j40ee2c22a9f8b66f@mail.gmail.com>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Oct 2007 07:42:43.0419 (UTC)
	FILETIME=[FB92CAB0:01C80590]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: draft-ietf-mmusic-ice@tools.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>
Errors-To: mmusic-bounces@ietf.org

Hi Adam,

In my opinion you should do the following.
- Always respond to binding requests, as the first response may not have
reached the requestor.

- Not perform the Triggered check for anything more than the first
request. No restart nor multiple queuing of the connectivity check for
that candidate pair.

I think there might be need for clarification on this in the ICE spec.

Cheers

Magnus

Adam Fisk skrev:
> I've noticed in my ICE tests that it's quite common for a peer to
> receive multiple Binding Requests for the same STUN transaction as a
> result of STUN retransmissions. 
> 
> While this is to be expected, the processing of the request specified in
> ICE 18 section 7.2.1.4 <http://7.2.1.4> "Triggered Checks" results in
> adding precisely the same candidate pair to the triggered check queue
> multiple times, resulting in multiple subsequent identical triggered
> checks and subsequent work.  Is this the expected behavior, or am I
> missing something?  While it doesn't seem the above will break anything,
> it doesn't appear optimal either. 
> 
> Should the triggered check queue filter duplicates?  Should the STUN
> server side in ICE ignore Binding Requests with transaction IDs it has
> already processed (clearly still sending Binding Responses, just not
> forwarding the request to the ICE procedures)?  I'd assume the latter,
> but it seems I must be missing something in one of the specs if this is
> the case.
> 
> This is assuming the ICE STUN server side just reprocesses each Binding
> Request and recomputes the Binding Response each time since the Binding
> method is idempotent, as specified in draft-ietf-behave-rfc3489bis-10
> section 7.3.1 "Processing a Request."
> 
> Thanks very much.
> 
> -Adam Fisk
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic


-- 

Magnus Westerlund

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

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



From mmusic-bounces@ietf.org Fri Oct 05 09:38:12 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IdnMS-0002D1-P9; Fri, 05 Oct 2007 09:37:00 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IdnMR-0002Cd-9d
	for mmusic@ietf.org; Fri, 05 Oct 2007 09:36:59 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IdnMQ-00059h-6M
	for mmusic@ietf.org; Fri, 05 Oct 2007 09:36:58 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id B71272800038D
	for <mmusic@ietf.org>; Fri,  5 Oct 2007 15:36:57 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gNf5LE5gIJLg for <mmusic@ietf.org>;
	Fri,  5 Oct 2007 15:36:57 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 983FB28000340
	for <mmusic@ietf.org>; Fri,  5 Oct 2007 15:36:52 +0200 (CEST)
Received: from mx1.office ([10.1.1.23]) by mx1.office with Microsoft
	SMTPSVC(6.0.3790.3959); Fri, 5 Oct 2007 15:36:51 +0200
Received: from [10.1.1.109] ([10.1.1.109]) by mx1.office over TLS secured
	channel with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 5 Oct 2007 15:36:51 +0200
Mime-Version: 1.0 (Apple Message framework v752.3)
To: mmusic@ietf.org
Message-Id: <E15B37C1-0020-4670-84EA-AB94509C2C15@netlab.nec.de>
From: Martin Stiemerling <stiemerling@netlab.nec.de>
Date: Fri, 5 Oct 2007 15:36:51 +0200
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 05 Oct 2007 13:36:51.0790 (UTC)
	FILETIME=[C96A66E0:01C80754]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Subject: [MMUSIC] RFC2326bis: A proposal about document size
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="===============1239880406=="
Errors-To: mmusic-bounces@ietf.org


--===============1239880406==
Content-Type: multipart/alternative; boundary=Apple-Mail-4-683330724


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

Hi all,

draft-ietf-mmusic-rfc2326bis has currently an overall page count of  
214 pages
(http://www.ietf.org/internet-drafts/draft-ietf-mmusic- 
rfc2326bis-15.txt)
and I doubt that many people have read the draft in the past as a  
whole... ;-)

After considering which part of the draft could shorten or moved to a  
different draft, I have have ended up with this as my personal  
conclusion:

Appendix B "Media Transport Alternatives" and Appendix C "Use of SDP  
for RTSP..." could be moved in separate drafts, as both are not  
necessarily part of RTSP itself, even though there somewhat required  
for operating RTSP.  However, this "required for operating RTSP"  
holds true in some environments, but not in all. For instance, in DVB  
network RTP is probably not used, but MPEG-2 TS. Same for SDP, as  
some might use it, some might not.

Appendix B could be moved to a draft "Using RTSP with RTP as media  
transport" and Appendix C "SDP usage in RTSP" (titles are just  
suggestions!)

This would reduce the size of the draft, but, even more important,  
would clearly separate between the RTSP protocol and further  
protocols required by some architecture to build media delivery  
platforms.

Any thoughts, suggestions, objections?

Thanks,

   Martin (draft-ietf-mmusic-rfc2326bis editor)

stiemerling@netlab.nec.de
NEC Laboratories Europe - Network Research Division

NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road,  
London W3 6BL | Registered in England 2832014



--Apple-Mail-4-683330724
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">Hi all,<DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>draft-ietf-mmusic-rfc2326bis =
has currently an overall page count of 214 pages</DIV><DIV>(<A =
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-mmusic-rfc2326bis-1=
5.txt">http://www.ietf.org/internet-drafts/draft-ietf-mmusic-rfc2326bis-15=
.txt</A>)</DIV><DIV>and I doubt that many people have read the draft in =
the past as a whole... ;-)</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>After considering which =
part of the draft could shorten or moved to a different draft, I have =
have ended up with this as my personal conclusion:</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Appendix B "Media Transport =
Alternatives" and Appendix C "Use of SDP for RTSP..." could be moved in =
separate drafts, as both are not necessarily part of RTSP itself, even =
though there somewhat required for operating RTSP.=A0 However, this =
"required for operating RTSP" holds true in some environments, but not =
in all. For instance, in DVB network RTP is probably not used, but =
MPEG-2 TS. Same for SDP, as some might use it, some might =
not.=A0</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Appendix B could be moved =
to a draft "Using RTSP with RTP as media transport" and Appendix C "SDP =
usage in RTSP" (titles are just suggestions!)</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>This would reduce the size =
of the draft, but, even more important, would clearly separate between =
the RTSP protocol and further protocols required by some architecture to =
build media delivery platforms.=A0</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Any thoughts, suggestions, =
objections?</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Thanks,</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>=A0 Martin =
(draft-ietf-mmusic-rfc2326bis editor)</DIV><DIV><BR><DIV> <SPAN =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Monaco; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; text-align: auto; =
-khtml-text-decorations-in-effect: none; text-indent: 0px; =
-apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><SPAN =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Monaco; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; text-align: auto; =
-khtml-text-decorations-in-effect: none; text-indent: 0px; =
-apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><SPAN =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Monaco; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; text-align: auto; =
-khtml-text-decorations-in-effect: none; text-indent: 0px; =
-apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"mailto:stiemerling@netlab.nec.de">stiemerling@netlab.nec.de</A></D=
IV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">NEC Laboratories Europe - Network Research =
Division</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><BR =
class=3D"khtml-block-placeholder"></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">NEC Europe =
Limited |=A0Registered Office: NEC House, 1 Victoria Road, London W3 6BL =
|=A0Registered in England 2832014</DIV><BR =
class=3D"Apple-interchange-newline"></SPAN></SPAN></SPAN> =
</DIV><BR></DIV></BODY></HTML>=

--Apple-Mail-4-683330724--


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

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

--===============1239880406==--




From mmusic-bounces@ietf.org Fri Oct 05 10:02:34 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IdnjV-0003Rx-W6; Fri, 05 Oct 2007 10:00:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IdnjT-0003Rc-8E
	for mmusic@ietf.org; Fri, 05 Oct 2007 10:00:47 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IdnjQ-0006s2-NG
	for mmusic@ietf.org; Fri, 05 Oct 2007 10:00:47 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l95E0K3X003849; Fri, 5 Oct 2007 17:00:42 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 5 Oct 2007 17:00:28 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 5 Oct 2007 17:00:27 +0300
Received: from esdhcp04330.research.nokia.com ([172.21.43.30]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 5 Oct 2007 17:00:27 +0300
From: =?utf-8?q?R=C3=A9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia TP-SP-SWD
To: mmusic@ietf.org, "ext Martin Stiemerling" <stiemerling@netlab.nec.de>
Subject: Re: [MMUSIC] RFC2326bis: A proposal about document size
Date: Fri, 5 Oct 2007 17:00:51 +0300
User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405)
References: <E15B37C1-0020-4670-84EA-AB94509C2C15@netlab.nec.de>
In-Reply-To: <E15B37C1-0020-4670-84EA-AB94509C2C15@netlab.nec.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200710051700.51590.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 05 Oct 2007 14:00:27.0435 (UTC)
	FILETIME=[1534AFB0:01C80758]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: 
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>
Errors-To: mmusic-bounces@ietf.org

Le Friday 05 October 2007 16:36:51 ext Martin Stiemerling, vous avez =C3=A9=
crit=C2=A0:
> Appendix B "Media Transport Alternatives" and Appendix C "Use of SDP
> for RTSP..." could be moved in separate drafts, as both are not
> necessarily part of RTSP itself, even though there somewhat required
> for operating RTSP.  However, this "required for operating RTSP"
> holds true in some environments, but not in all.

> For instance, in DVB=20
> network RTP is probably not used, but MPEG-2 TS.

Do you mean TS over RTP, or TS over plain UDP?

I know uses of both, though I think the second one should really be heavily=
=20
discouraged. Apparently, it screws up completely whenever there is packet=20
re-ordering.

> Same for SDP, as some might use it, some might not.

I agree that the spec is way too long, but removing essential parts may jus=
t=20
make matters worse. At the end of the day, it makes the entire thing even=20
longer, that's why... I mean, what's the use of an RTSP stack without RTP=20
(especially when raw TS over UDP is so broken).


I would have thought of moving all the proxying stuff to a separate documen=
t,=20
=C3=A0 la MSRP, perhaps.

=2D-=20
R=C3=A9mi Denis-Courmont

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



From mmusic-bounces@ietf.org Mon Oct 08 04:22:31 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ienqa-0002v0-J9; Mon, 08 Oct 2007 04:20:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IenqY-0002uc-T8
	for mmusic@ietf.org; Mon, 08 Oct 2007 04:20:14 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IenqW-00061P-42
	for mmusic@ietf.org; Mon, 08 Oct 2007 04:20:12 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	5639F2097B; Mon,  8 Oct 2007 10:19:48 +0200 (CEST)
X-AuditID: c1b4fb3c-af67dbb0000007e1-99-4709e8246ad7
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	36EBC20AD5; Mon,  8 Oct 2007 10:19:48 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 8 Oct 2007 10:19:46 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 8 Oct 2007 10:19:46 +0200
Message-ID: <4709E821.7010604@ericsson.com>
Date: Mon, 08 Oct 2007 10:19:45 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: =?UTF-8?B?UsOpbWkgRGVuaXMtQ291cm1vbnQ=?=
 <remi.denis-courmont@nokia.com>
Subject: Re: [MMUSIC] RFC2326bis: A proposal about document size
References: <E15B37C1-0020-4670-84EA-AB94509C2C15@netlab.nec.de>
	<200710051700.51590.remi.denis-courmont@nokia.com>
In-Reply-To: <200710051700.51590.remi.denis-courmont@nokia.com>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=UTF-8
X-OriginalArrivalTime: 08 Oct 2007 08:19:46.0150 (UTC)
	FILETIME=[FC7D6060:01C80983]
X-Brightmail-Tracker: AAAAAA==
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
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>
Errors-To: mmusic-bounces@ietf.org

Hi,

I think we should be careful of splitting of to much normative functions
into other documents. I think one of the more important things is to
make it more readable. I think the main problem is the initial sections.
I also think there is some informative text that could be moved into
some separate purely informative document. But I wonder if that really
can be moved in way that will make sense. I think we will need to look
into this more.


R=C3=A9mi Denis-Courmont skrev:
> Le Friday 05 October 2007 16:36:51 ext Martin Stiemerling, vous avez =C3=
=A9crit :
>> Appendix B "Media Transport Alternatives" and Appendix C "Use of SDP
>> for RTSP..." could be moved in separate drafts, as both are not
>> necessarily part of RTSP itself, even though there somewhat required
>> for operating RTSP.  However, this "required for operating RTSP"
>> holds true in some environments, but not in all.
>=20
>> For instance, in DVB=20
>> network RTP is probably not used, but MPEG-2 TS.
>=20
> Do you mean TS over RTP, or TS over plain UDP?

I don't think this matter as RTSP is intended to possible to use with
any media transport. However, that media transport must specify the
equivalent to Appendix B. But TS over RTP falls under the RTP usage, so
I think Martin meant MPEG-2 TS over UDP.

>=20
> I know uses of both, though I think the second one should really be hea=
vily=20
> discouraged. Apparently, it screws up completely whenever there is pack=
et=20
> re-ordering.
>=20
>> Same for SDP, as some might use it, some might not.
>=20
> I agree that the spec is way too long, but removing essential parts may=
 just=20
> make matters worse. At the end of the day, it makes the entire thing ev=
en=20
> longer, that's why... I mean, what's the use of an RTSP stack without R=
TP=20
> (especially when raw TS over UDP is so broken).

Well, this is actually a pluggable part. And I think this will make it
clearer that there is the signalling and then one or more media
transports being negotiated. But if this is a real benefit or not I
wouldn't say. The end result will be that there will be more pages to
read in total.

>=20
>=20
> I would have thought of moving all the proxying stuff to a separate doc=
ument,=20
> =C3=A0 la MSRP, perhaps.
>=20

I far from convinced that this is the right move. However, we probably
should look into this. The important is that we then must succeed to
only move functionality that really are valid for the proxy only. In
cases the client or server must be aware of the proxy, these functions
must be specified in the base spec. I don't know how easy this is.

Cheers

Magnus Westerlund

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

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



From mmusic-bounces@ietf.org Mon Oct 08 11:09:54 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IeuEB-0001BV-Uf; Mon, 08 Oct 2007 11:09:03 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IeuEA-0001Ae-3T; Mon, 08 Oct 2007 11:09:02 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IeuE9-0003La-DF; Mon, 08 Oct 2007 11:09:02 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	E0FAF2045E; Mon,  8 Oct 2007 17:09:00 +0200 (CEST)
X-AuditID: c1b4fb3e-ae831bb0000007e1-b6-470a480c4ad7
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	C898D21778; Mon,  8 Oct 2007 17:09:00 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 8 Oct 2007 17:09:00 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 8 Oct 2007 17:09:00 +0200
Message-ID: <470A480C.4040506@ericsson.com>
Date: Mon, 08 Oct 2007 17:09:00 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: TSV Area <tsv-area@ietf.org>, Behave WG <behave@ietf.org>, 
	"mmusic (E-mail)" <mmusic@ietf.org>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Oct 2007 15:09:00.0265 (UTC)
	FILETIME=[27E1FD90:01C809BD]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: 
Subject: [MMUSIC] BOF request under consideration: SAFE
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>
Errors-To: mmusic-bounces@ietf.org

Hi,

We ADs have received a request for a BOF in Vancouver: SAFE -
Self-Address Fixing Evolution. See description below. I would appreciate
any feedback on this. For public discussion please use the SAFE mailing
list.

Post: safe@ietf.org
Subscribe: https://www1.ietf.org/mailman/listinfo/safe

Draft:
http://www.ietf.org/internet-drafts/draft-wing-behave-nat-control-stun-usage-03.txt


SAFE - Self-Address Fixing Evolution
------------------------------------

Chairs:
  TBD


ICE and its companion protocol STUN have been successfully deployed on
the Internet for NAT traversal.  ICE and STUN have several characteristics
which contribute to their success:

  1. incremental deployment.  ICE and STUN are functional without any
     modifications to existing NATs.
  2. nested NATs.  ICE and STUN work when there are multiple NATs
     between a host and the Internet.
  3. topology unaware.  ICE and STUN are not configured with
     information about NATs, firewalls, or their locations -- only
     with the IP address of a server on the Internet.
  4. simple security model.  If a host behind a NAT is allowed to send
     a packet across the NAT, it is allowed to receive a response.
  5. works on routed networks, which allows operation in both
     enterprise networks and home networks.

Other NAT traversal protocols do not share these characteristics,
which hinders their widespread deployment.  Specifically,

  * incremental deployment is not possible with MIDCOM, NSIS-NSLP,
    UPnP, or Bonjour.  With all of these protocols, both the NAT
    and the endpoint have to support the same protocol.
  * nested NATs are not possible with UPnP or Bonjour.
  * topology awareness is required of MIDCOM.
  * security must be established between the controlling entity
    and the NAT for MIDCOM and NSIS-NSLP.
  * Both UPnP and Bonjour use broadcast packets which don't work
    well on routed networks.

However, a drawback of ICE/STUN is its chatty keepalive traffic,
which is a result of STUN not knowing the binding lifetime of its
on-path NATs.  This chattiness causes a burden on servers and
consumes network bandwidth, which is especially critical on wireless
networks.  It is desirable to reduce this chattiness while still
retaining the important characteristics of STUN and ICE.

This BoF is intended to discuss one proposed technique,
draft-wing-behave-nat-control-stun-usage, which nearly eliminates
STUN's keepalive chatter and still preserves the desirable
characteristics of STUN/ICE.

The purpose of this BoF is to create a working group for this effort.


Agenda:
  Introduction, Agenda ....................................  5
  Summary of existing NAT traversal techniques ............ 40
   (UPnP, NAT-PMP/Bonjour, MIDCOM techniques, NSIS-NSLP, ICE)
  draft-wing-behave-nat-control-stun-usage ................ 40
  Q&A ..................................................... 25
                                                    ----------
                                                    total: 110

Cheers

Magnus Westerlund

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

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



From mmusic-bounces@ietf.org Tue Oct 16 21:14:02 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IhxSG-0000OG-Fd; Tue, 16 Oct 2007 21:12:12 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IhxSA-0000MN-4U
	for mmusic-confirm+ok@megatron.ietf.org; Tue, 16 Oct 2007 21:12:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IhxS7-0000LI-V1; Tue, 16 Oct 2007 21:12:03 -0400
Received: from bosco.isi.edu ([128.9.168.207])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IhxS1-0007cy-PB; Tue, 16 Oct 2007 21:12:03 -0400
Received: by bosco.isi.edu (Postfix, from userid 70)
	id F0AB8E7CF3; Tue, 16 Oct 2007 18:06:44 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20071017010644.F0AB8E7CF3@bosco.isi.edu>
Date: Tue, 16 Oct 2007 18:06:44 -0700 (PDT)
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: mmusic@ietf.org, rfc-editor@rfc-editor.org
Subject: [MMUSIC] RFC 5027 on Security Preconditions for Session Description
	Protocol (SDP) Media Streams
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>
Errors-To: mmusic-bounces@ietf.org


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

        
        RFC 5027

        Title:      Security Preconditions for Session Description 
                    Protocol (SDP) Media Streams 
        Author:     F. Andreasen, D. Wing
        Status:     Standards Track
        Date:       October 2007
        Mailbox:    fandreas@cisco.com, 
                    dwing@cisco.com
        Pages:      16
        Characters: 37229
        Updates:    RFC3312
        See-Also:   

        I-D Tag:    draft-ietf-mmusic-securityprecondition-04.txt

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

This document defines a new security precondition for the Session
Description Protocol (SDP) precondition framework described in RFCs
3312 and 4032.  A security precondition can be used to delay session
establishment or modification until media stream security for a
secure media stream has been negotiated successfully.  [STANDARDS TRACK]

This document is a product of the Multiparty Multimedia Session Control
Working Group of the IETF.

This is now a Proposed Standard Protocol.

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

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

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

help: ways_to_get_rfcs. For example:

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

        help: ways_to_get_rfcs

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

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


The RFC Editor Team
USC/Information Sciences Institute

...




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



From mmusic-bounces@ietf.org Fri Oct 19 06:01:02 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Iioc2-0002Xd-Ij; Fri, 19 Oct 2007 05:57:50 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1Ieztn-0003OP-Qj
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 08 Oct 2007 17:12:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ieztn-0003OH-HB
	for mmusic@ietf.org; Mon, 08 Oct 2007 17:12:23 -0400
Received: from nz-out-0506.google.com ([64.233.162.228])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iezth-0004qf-9S
	for mmusic@ietf.org; Mon, 08 Oct 2007 17:12:23 -0400
Received: by nz-out-0506.google.com with SMTP id n1so736932nzf
	for <mmusic@ietf.org>; Mon, 08 Oct 2007 14:12:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth;
	bh=WaVY8Ta9SGSkvUJYbgdahg4ZUI6xEHtGZxAArXxCzBw=;
	b=VCiGwESKVjYUVkAOAEELrwMi0gj4fKmNMTlL5xbqMWktV0ch54EwhZD0Lf7eoaUZO/GGyFbTUmXcPhpB9xGWD6OsPm3Gayq6OtmcNtLym5rISZp2iKS4Min0e2JrPvxeI2Ps1A4ax+58U90qlaG+HMBxW+0J067yB8L8cs/fWQg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth;
	b=DG7aUc1Pfd5IGSrtM8mpCVbPkx+Gm4TxjFd4PgNqtUEDRh5+didfZcSUBwpEpcbOWcYpOHnO68OcK8CLuu9w+Du8jxPQw8krobqJc9wbaOgrHx1zvkyNuZIlN6Awyeb8ic5soX4JcOC2UT4M+NmP9aulPd8FS6cMkz/mXI7d+9I=
Received: by 10.115.17.1 with SMTP id u1mr10268932wai.1191877919664;
	Mon, 08 Oct 2007 14:11:59 -0700 (PDT)
Received: by 10.115.78.9 with HTTP; Mon, 8 Oct 2007 14:11:59 -0700 (PDT)
Message-ID: <f40963db0710081411y136a15d1h24db8e5417015764@mail.gmail.com>
Date: Mon, 8 Oct 2007 17:11:59 -0400
From: "Adam Fisk" <a@lastbamboo.org>
To: "IETF MMUSIC WG" <mmusic@ietf.org>
Subject: [MMUSIC] ICE-18 Nominating pairs on controlled agents
MIME-Version: 1.0
X-Google-Sender-Auth: e34ef5f4f0316db5
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
X-Mailman-Approved-At: Fri, 19 Oct 2007 05:57:25 -0400
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="===============0175790124=="
Errors-To: mmusic-bounces@ietf.org

--===============0175790124==
Content-Type: multipart/alternative; 
	boundary="----=_Part_1616_11176568.1191877919651"

------=_Part_1616_11176568.1191877919651
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Apologies for the comments so late in the game on the ICE drafts, but there
appears to be a minor error in the nominating of pairs on controlled agents.

Section 7.1.2.2.4 on performing STUN client connectivity checks reads:

"If the agent is the controlled agent, the response may result in the valid
pair having its nominated flag set. See section 7.2.1.5 for the procedure."
    -- http://tools.ietf.org/html/draft-ietf-mmusic-ice-18#section-7.1.2.2.4

7.2.1.5 then reads:

"If the Binding Request received by the agent had the USE-CANDIDATE attribute
set, and the agent is in the controlled role, the agent looks at the state
of the pair computed in Section 7.2.1.4:"
    -- http://tools.ietf.org/html/draft-ietf-mmusic-ice-18#section-7.2.1.5

Shouldn't the last part of 7.2.1.5 at least read: "the agent looks at the
state of the pair computed in Section 7.2.1.4 or in Section 7.1.2.2.4:"?
Otherwise, you'd just immediately ignore then whole of section 7.2.1.5 when
processing pairs computed from section 7.1.2.2.4.

That's it for the "error" -- almost more a nit really.  Digging a little
deeper, though, it seems to me that the nomination decision for the
controlled agent in 7.1.2.2.4 should be really simple and should not have to
reference section 7.2.1.5 at all.  Basically, if the pair received
USE-CANDIDATE in the past, it should be nominated.  This is because the pair
has just reached the successful state when we get to section 7.1.2.2.4, so
all we need to know is whether or not we've received USE-CANDIDATE yet or
not.

Does that make sense?  I think referencing 7.2.1.5 makes it seem like a more
complicated decision than it is, is much harder to understand, and breaks up
the document flow.  Those issues aside, though, it seems like the opening of
7.2.1.5 should at the very least acknowledge that the pair could have also
come from 7.1.2.2.4.

Again, I hate to bring this up so late in the game, but I only just noticed
it.

Thanks.

-Adam

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

Apologies for the comments so late in the game on the ICE drafts, but there appears to be a minor error in the nominating of pairs on controlled agents.<br><br>Section 7.1.2.2.4 on performing STUN client connectivity checks reads:
<br><br>&quot;If the agent is the controlled agent, the response may result in the<span style="font-family: monospace;"> </span>valid pair having its nominated flag set. See section <a href="http://7.2.1.5">7.2.1.5</a> for the procedure.&quot; 
<br>&nbsp;&nbsp;&nbsp; -- <a href="http://tools.ietf.org/html/draft-ietf-mmusic-ice-18#section-7.1.2.2.4">http://tools.ietf.org/html/draft-ietf-mmusic-ice-18#section-7.1.2.2.4</a><br><br><a href="http://7.2.1.5">7.2.1.5</a> then reads:<br>
<br>&quot;If the Binding Request received by the agent had the USE-CANDIDATE<span style="font-family: monospace;"> </span>attribute set, and the agent is in the controlled role, the agent<span style="font-family: monospace;">
 </span>looks at the state of the pair computed in Section 7.2.1.4:&quot;&nbsp; <br>&nbsp;&nbsp;&nbsp; -- <a href="http://tools.ietf.org/html/draft-ietf-mmusic-ice-18#section-7.2.1.5">http://tools.ietf.org/html/draft-ietf-mmusic-ice-18#section-7.2.1.5
</a><br><br>Shouldn&#39;t the last part of <a href="http://7.2.1.5">7.2.1.5</a> at least read: &quot;the agent<span style="font-family: monospace;"> </span>looks at the state of the pair computed in Section <a href="http://7.2.1.4">
7.2.1.4</a> or in Section 7.1.2.2.4:&quot;?&nbsp; Otherwise, you&#39;d just immediately ignore then whole of section <a href="http://7.2.1.5">7.2.1.5</a>  when processing pairs computed from section 7.1.2.2.4. <br><br>That&#39;s it for the &quot;error&quot; -- almost more a nit really.&nbsp; Digging a little deeper, though, it seems to me that the nomination decision for the controlled agent in 
7.1.2.2.4 should be really simple and should not have to reference section <a href="http://7.2.1.5">7.2.1.5</a> at all.&nbsp; Basically, if the pair received USE-CANDIDATE in the past, it should be nominated.&nbsp; This is because the pair has just reached the successful state when we get to section 
7.1.2.2.4, so all we need to know is whether or not we&#39;ve received USE-CANDIDATE yet or not.&nbsp; <br><br>Does that make sense?&nbsp; I think referencing <a href="http://7.2.1.5">7.2.1.5</a> makes it seem like a more complicated decision than it is, is much harder to understand, and breaks up the document flow.&nbsp; Those issues aside, though, it seems like the opening of 
<a href="http://7.2.1.5">7.2.1.5</a> should at the very least acknowledge that the pair could have also come from 7.1.2.2.4.<br><br>Again, I hate to bring this up so late in the game, but I only just noticed it.<br><br>Thanks.
<br><br>-Adam<br><br><br>

------=_Part_1616_11176568.1191877919651--



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

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

--===============0175790124==--





From mmusic-bounces@ietf.org Fri Oct 19 06:01:20 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IiofO-0006Oo-Q9; Fri, 19 Oct 2007 06:01:18 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IiofN-0006KS-1M
	for mmusic-confirm+ok@megatron.ietf.org; Fri, 19 Oct 2007 06:01:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IiofM-00068U-23
	for mmusic@ietf.org; Fri, 19 Oct 2007 06:01:16 -0400
Received: from keskus.netlab.hut.fi ([130.233.154.176] helo=smtp.netlab.hut.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IiofB-0008I3-G1
	for mmusic@ietf.org; Fri, 19 Oct 2007 06:01:11 -0400
Received: from localhost (webserver.netlab.hut.fi [130.233.154.187])
	by smtp.netlab.hut.fi (Postfix) with ESMTP id 7180AC50E2;
	Fri, 19 Oct 2007 13:00:57 +0300 (EET DST)
X-Virus-Scanned: Debian amavisd-new at TKK Netlab
Received: from smtp.netlab.hut.fi ([130.233.154.176])
	by localhost (webserver.netlab.hut.fi [130.233.154.187]) (amavisd-new,
	port 10024)
	with ESMTP id CWq9DfbVVpJT; Fri, 19 Oct 2007 13:00:50 +0300 (EEST)
Received: from [127.0.0.1] (keskus.netlab.hut.fi [130.233.154.176])
	by smtp.netlab.hut.fi (Postfix) with ESMTP id 1CEBEC50EA;
	Fri, 19 Oct 2007 13:00:46 +0300 (EET DST)
Message-ID: <47188049.3070200@netlab.hut.fi>
Date: Fri, 19 Oct 2007 13:00:41 +0300
From: Joerg Ott <jo@netlab.tkk.fi>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mmusic <mmusic@ietf.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: Jean-Francois Mule <jf.mule@cablelabs.com>
Subject: [MMUSIC] MMUSIC: Call for agenda items
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>
Errors-To: mmusic-bounces@ietf.org

Folks,

MMUSIC will be scheduled to meet twice at the Vancouver IETF
(the draft agenda does not yet show when)

Please send agenda requests to the co-chairs, keeping in mind
to

-- refer to the draft you will talk about
-- summarize the issues you intend to address/discuss
-- refer to mailing list discussions and open issues
-- tell us how much time you will need

We will collect the requests are create a draft agenda out
of them.  WG drafts and individual drafts that have seen mailing
list discussion and shown progress will be given preference.

Below are the Internet cut-off dates, just as a reminder.

Thanks,
Joerg

-------- Original Message --------
Subject: Internet-Drafts Submission Cutoff Dates for the 70th IETF 
Meeting in Vancouver, BC, Canada
Date: Fri, 19 Oct 2007 00:00:01 -0400
From: ietf-secretariat@ietf.org
To: ietf-announce@ietf.org

There are two (2) Internet-Draft cutoff dates for the 70th
IETF Meeting in Vancouver, BC, Canada:

November 12th: Cutoff Date for Initial (i.e., version -00)
Internet-Draft Submissions

All initial Internet-Drafts (version -00) must be submitted by Monday,
November 12th at 9:00 AM ET (14:00 UTC/GMT). As always, all initial 
submissions with a
filename beginning with "draft-ietf" must be approved by the
appropriate WG Chair before they can be processed or announced.  The
Secretariat would appreciate receiving WG Chair approval by Monday,
November 5th at 9:00 AM ET (14:00 UTC/GMT).

November  (14:00 UTC/GMT): Cutoff Date for Revised (i.e., version -01 
and higher)
Internet-Draft Submissions

All revised Internet-Drafts (version -01 and higher) must be submitted
by Monday, November 19th at 9:00 AM ET (14:00 UTC/GMT).

Initial and revised Internet-Drafts received after their respective
cutoff dates will not be made available in the Internet-Drafts
directory or announced until on or after Monday, December 3rd at 9:00
AM ET (14:00 UTC/GMT), when Internet-Draft posting resumes.  Please do 
not wait until
the last minute to submit.

The Secretariat encourages you to submit your Internet-Drafts via the 
Internet-Draft
Submission Tool (IDST) https://datatracker.ietf.org/idst/upload.cgi. If 
you are unable to do
so, then you may still submit your Internet-Drafts manually by sending 
them to internet-
drafts@ietf.org.  If you are submitting a version -00 WG draft that 
replaces non-WG draft,
then you must submit it manually as the current IDST cannot handle 
replacements.  Please be
sure to state that one draft replaces another in the cover note that 
accompanies your
submission.  Also, please note that the IDST will not accept drafts 
submitted after their
respective cutoff dates.

Thank you for your understanding and cooperation. If you have any
questions or concerns, then please send a message to
internet-drafts@ietf.org.

The IETF Secretariat

FYI: The Internet-Draft cutoff dates as well as other significant dates
for the 70th IETF Meeting can be found at 
http://www.ietf.org/meetings/cutoff_dates_70.html.

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



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



From mmusic-bounces@ietf.org Fri Oct 19 11:14:25 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IitW8-0004XD-MJ; Fri, 19 Oct 2007 11:12:04 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IitW6-0004PS-I0
	for mmusic-confirm+ok@megatron.ietf.org; Fri, 19 Oct 2007 11:12:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IitW5-0004Kr-OY
	for mmusic@ietf.org; Fri, 19 Oct 2007 11:12:01 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IitVx-00033R-He
	for mmusic@ietf.org; Fri, 19 Oct 2007 11:11:59 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	CDCD9207E6
	for <mmusic@ietf.org>; Fri, 19 Oct 2007 17:11:20 +0200 (CEST)
X-AuditID: c1b4fb3c-b0e80bb0000007e1-19-4718c9186eed
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	B8579207E4
	for <mmusic@ietf.org>; Fri, 19 Oct 2007 17:11:20 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 Oct 2007 17:11:20 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 Oct 2007 17:11:20 +0200
Message-ID: <4718C918.5020707@ericsson.com>
Date: Fri, 19 Oct 2007 17:11:20 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "mmusic (E-mail)" <mmusic@ietf.org>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Oct 2007 15:11:20.0084 (UTC)
	FILETIME=[4DC3ED40:01C81262]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Subject: [MMUSIC] RTSP 2.0: Issue [ 1701610 ] CR LF mitigations.
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>
Errors-To: mmusic-bounces@ietf.org

Hi,

Joe Pallas suggested that we remove this text. I am actually agreeing
with his proposal. Any objections?

"In RFC 2326, receivers were advised to be prepared to also interpret CR
and LF by themselves as line terminators in addition to CRLF. If a
server or client wishes to support RFC 2326, it should treat a CR or LF
by itself as a CRLF."

For seeing the whole issue text see:
http://sourceforge.net/tracker/index.php?func=detail&aid=1701610&group_id=23194&atid=377744

Cheers

Magnus Westerlund

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


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



From mmusic-bounces@ietf.org Sat Oct 20 10:48:34 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IjFb9-0003Pa-RM; Sat, 20 Oct 2007 10:46:43 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IjFb8-0003PS-4Z
	for mmusic-confirm+ok@megatron.ietf.org; Sat, 20 Oct 2007 10:46:42 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IjFb7-0003PK-BZ
	for mmusic@ietf.org; Sat, 20 Oct 2007 10:46:41 -0400
Received: from [74.95.2.169] (helo=delta.rtfm.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IjFb7-0003nD-0r
	for mmusic@ietf.org; Sat, 20 Oct 2007 10:46:41 -0400
Received: from delta.rtfm.com (localhost.rtfm.com [127.0.0.1])
	by delta.rtfm.com (Postfix) with ESMTP id 2B49A33C57;
	Sat, 20 Oct 2007 07:42:22 -0700 (PDT)
Date: Sat, 20 Oct 2007 07:42:21 -0700
From: Eric Rescorla <ekr@networkresonance.com>
To: Miguel Garcia <Miguel.Garcia@nsn.com>
Subject: Re: [MMUSIC] File transfer issue 50: Single hash
In-Reply-To: <46C04734.7080009@nsn.com>
References: <46C04734.7080009@nsn.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20071020144222.2B49A33C57@delta.rtfm.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: 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>
Errors-To: mmusic-bounces@ietf.org

At Mon, 13 Aug 2007 14:57:40 +0300,
Miguel Garcia wrote:
> 
> During the IETF meeting in Chicago, Jonathan indicated that the way the 
> draft allows multiple hash algorithms creates an extra unneeded 
> complexity. It would be easier to use a single hash algorithm, such as 
> SHA-1.
> 
> Background: The hash is used for a double purpose:
> a) unique file identification
> b) verification of the correct reception of the file.
> 
> Bearing in mind the current complexity the endpoints need to deal with, 
> when they support several hashing algorithms, I am ok with the 
> suggestion. So, I recommend to use SHA-1 as the only hashing algorithm. 
> Do people have concerns?

I think this is fine, but you'll need some text explaining why this is
not a security critical function and that if you want to protect
the integrity of the file you will need another mechanism.

-Ekr


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



From mmusic-bounces@ietf.org Sun Oct 21 14:57:41 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ijfxi-0001wT-0U; Sun, 21 Oct 2007 14:55:46 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1Ijfxf-0001vb-QE
	for mmusic-confirm+ok@megatron.ietf.org; Sun, 21 Oct 2007 14:55:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ijfxe-0001eX-Mn
	for mmusic@ietf.org; Sun, 21 Oct 2007 14:55:42 -0400
Received: from poy.chewa.net ([2002:c2f2:7249::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IjfxR-0003Iw-Ua
	for mmusic@ietf.org; Sun, 21 Oct 2007 14:55:35 -0400
Received: from basile.remlab.net (unknown
	[IPv6:2002:3e4e:969c:0:211:11ff:fe25:e6b4])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: remi)
	by poy.chewa.net (Postfix) with ESMTP id 587BE9678E
	for <mmusic@ietf.org>; Sun, 21 Oct 2007 20:55:01 +0200 (CEST)
From: =?utf-8?q?R=C3=A9mi_Denis-Courmont?= <rem@videolan.org>
Organization: VideoLAN project - www.videolan.org
To: mmusic@ietf.org
Subject: Re: [MMUSIC] RTSP 2.0: Issue [ 1701610 ] CR LF mitigations.
Date: Sun, 21 Oct 2007 21:54:59 +0300
User-Agent: KMail/1.9.7
References: <4718C918.5020707@ericsson.com>
In-Reply-To: <4718C918.5020707@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200710212154.59806.rem@videolan.org>
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
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>
Errors-To: mmusic-bounces@ietf.org

Le Friday 19 October 2007 18:11:20 Magnus Westerlund, vous avez =C3=A9crit=
=C2=A0:
> Joe Pallas suggested that we remove this text. I am actually agreeing
> with his proposal. Any objections?

I agree there is no need to recommend support for sole CR or LF. However, I=
=20
hope that receivers will not be explicitly forbidden from accepting sole CR=
=20
or sole LF. Lets face it, some developpers will still debug their RTSP stac=
k=20
with telnet, sending only LF, so they will want *their* stack to accept thi=
s,=20
whatever the spec says.

=2D-=20
R=C3=A9mi Denis-Courmont
http://www.remlab.net/


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



From mmusic-bounces@ietf.org Mon Oct 22 01:13:49 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ijpaa-00047p-1z; Mon, 22 Oct 2007 01:12:32 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IjpaX-000451-9T
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 22 Oct 2007 01:12:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IjpaV-00044B-It
	for mmusic@ietf.org; Mon, 22 Oct 2007 01:12:27 -0400
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IjpaU-0007M9-HY
	for mmusic@ietf.org; Mon, 22 Oct 2007 01:12:27 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l9M5CBKN023823; Mon, 22 Oct 2007 08:12:15 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 22 Oct 2007 08:12:11 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 22 Oct 2007 08:12:10 +0300
Received: from [10.162.95.10] ([10.162.95.10]) by esebh101.NOE.Nokia.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 22 Oct 2007 08:12:10 +0300
Message-ID: <471C312A.5050501@nsn.com>
Date: Mon, 22 Oct 2007 08:12:10 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Eric Rescorla <ekr@networkresonance.com>
Subject: Re: [MMUSIC] File transfer issue 50: Single hash
References: <46C04734.7080009@nsn.com>
	<20071020144222.2B49A33C57@delta.rtfm.com>
In-Reply-To: <20071020144222.2B49A33C57@delta.rtfm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Oct 2007 05:12:10.0878 (UTC)
	FILETIME=[199BA9E0:01C8146A]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: 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>
Errors-To: mmusic-bounces@ietf.org

Eric Rescorla wrote:
> At Mon, 13 Aug 2007 14:57:40 +0300,
> Miguel Garcia wrote:
>> During the IETF meeting in Chicago, Jonathan indicated that the way the 
>> draft allows multiple hash algorithms creates an extra unneeded 
>> complexity. It would be easier to use a single hash algorithm, such as 
>> SHA-1.
>>
>> Background: The hash is used for a double purpose:
>> a) unique file identification
>> b) verification of the correct reception of the file.
>>
>> Bearing in mind the current complexity the endpoints need to deal with, 
>> when they support several hashing algorithms, I am ok with the 
>> suggestion. So, I recommend to use SHA-1 as the only hashing algorithm. 
>> Do people have concerns?
> 
> I think this is fine, but you'll need some text explaining why this is
> not a security critical function and that if you want to protect
> the integrity of the file you will need another mechanism.
> 
> -Ekr

Thanks. I'll add such explanation. I have already made the changes to 
live with a single hash, so this should fairly simple.

I will be submitting a new version of the draft sometime this week.

/Miguel
-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Espoo, Finland



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



From mmusic-bounces@ietf.org Mon Oct 22 04:59:55 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ijt7X-0001sH-PR; Mon, 22 Oct 2007 04:58:47 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1Ijt7V-0001lY-Dc
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 22 Oct 2007 04:58:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ijt7U-0001Xh-Ha
	for mmusic@ietf.org; Mon, 22 Oct 2007 04:58:44 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ijt7I-0004Yz-Vm
	for mmusic@ietf.org; Mon, 22 Oct 2007 04:58:39 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	3421F20771; Mon, 22 Oct 2007 10:58:12 +0200 (CEST)
X-AuditID: c1b4fb3c-b1e82bb0000007e1-d8-471c6624cc69
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	1BAAF2077E; Mon, 22 Oct 2007 10:58:12 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 22 Oct 2007 10:58:11 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 22 Oct 2007 10:58:11 +0200
Message-ID: <471C6623.2090806@ericsson.com>
Date: Mon, 22 Oct 2007 10:58:11 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: =?UTF-8?B?UsOpbWkgRGVuaXMtQ291cm1vbnQ=?= <rem@videolan.org>
Subject: Re: [MMUSIC] RTSP 2.0: Issue [ 1701610 ] CR LF mitigations.
References: <4718C918.5020707@ericsson.com>
	<200710212154.59806.rem@videolan.org>
In-Reply-To: <200710212154.59806.rem@videolan.org>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=UTF-8
X-OriginalArrivalTime: 22 Oct 2007 08:58:11.0744 (UTC)
	FILETIME=[AC839A00:01C81489]
X-Brightmail-Tracker: AAAAAA==
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
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>
Errors-To: mmusic-bounces@ietf.org

R=C3=A9mi Denis-Courmont skrev:
> Le Friday 19 October 2007 18:11:20 Magnus Westerlund, vous avez =C3=A9c=
rit :
>> Joe Pallas suggested that we remove this text. I am actually agreeing
>> with his proposal. Any objections?
>=20
> I agree there is no need to recommend support for sole CR or LF. Howeve=
r, I=20
> hope that receivers will not be explicitly forbidden from accepting sol=
e CR=20
> or sole LF. Lets face it, some developpers will still debug their RTSP =
stack=20
> with telnet, sending only LF, so they will want *their* stack to accept=
 this,=20
> whatever the spec says.
>=20

Well, the standard says that one needs to send CRLF. However, if an
implementor likes to have support for receiving LF or CR individually,
that is fine, and their issue to deal with the potential problems.

cheers

Magnus Westerlund

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


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



From mmusic-bounces@ietf.org Mon Oct 22 06:58:46 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ijuxk-0000lL-Ng; Mon, 22 Oct 2007 06:56:48 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1Ijuxg-0000gL-1U
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 22 Oct 2007 06:56:44 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ijuxe-0000dn-Uz
	for mmusic@ietf.org; Mon, 22 Oct 2007 06:56:42 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ijuxe-0007d6-Jg
	for mmusic@ietf.org; Mon, 22 Oct 2007 06:56:42 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	DDFBA201BF
	for <mmusic@ietf.org>; Mon, 22 Oct 2007 12:56:41 +0200 (CEST)
X-AuditID: c1b4fb3e-af833bb0000007e1-a5-471c81e9a569
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	CFE3F2006B
	for <mmusic@ietf.org>; Mon, 22 Oct 2007 12:56:41 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 22 Oct 2007 12:56:41 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 22 Oct 2007 12:56:40 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF02A21742@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: ICE with media streams without candidates
Thread-Index: AcgUmjmht9fcVjG+Td+1pqf1XCTmYw==
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: <mmusic@ietf.org>
X-OriginalArrivalTime: 22 Oct 2007 10:56:41.0563 (UTC)
	FILETIME=[3A4BE2B0:01C8149A]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Subject: [MMUSIC] ICE with media streams without candidates
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>
Errors-To: mmusic-bounces@ietf.org


Hi,

Chapter 5.1 of the draft says:

"The agent will proceed with the ICE procedures defined in this
specification if, for each media stream in the SDP it received, the
default destination for each component of that media stream appears in a
candidate attribute."

Does this mean that if, for whatever reason, some of the media streams
(m=3D lines) do not contain any attributes ICE will NOT proceed?

Regards,

Christer


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



From mmusic-bounces@ietf.org Mon Oct 22 07:32:57 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IjvVo-0004yw-01; Mon, 22 Oct 2007 07:32:00 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IjvVl-0004ty-VL
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 22 Oct 2007 07:31:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IjvVk-0004tq-W7
	for mmusic@ietf.org; Mon, 22 Oct 2007 07:31:56 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IjvVe-0003Lv-KL
	for mmusic@ietf.org; Mon, 22 Oct 2007 07:31:56 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l9MBVbnK029537; Mon, 22 Oct 2007 14:31:38 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 22 Oct 2007 14:31:32 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 22 Oct 2007 14:30:20 +0300
Received: from esdhcp04061.research.nokia.com ([172.21.40.61]) by
	esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 22 Oct 2007 14:30:19 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia TP-SP-SWD
To: mmusic@ietf.org
Subject: Re: [MMUSIC] ICE with media streams without candidates
Date: Mon, 22 Oct 2007 14:31:08 +0300
User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405)
References: <CA9998CD4A020D418654FCDEF4E707DF02A21742@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF02A21742@esealmw113.eemea.ericsson.se>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200710221431.09094.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 22 Oct 2007 11:30:19.0800 (UTC)
	FILETIME=[ED426980:01C8149E]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: ext Christer Holmberg <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>
Errors-To: mmusic-bounces@ietf.org

Le Monday 22 October 2007 13:56:40 ext Christer Holmberg, vous avez =E9crit=
=A0:
> Hi,
>
> Chapter 5.1 of the draft says:
>
> "The agent will proceed with the ICE procedures defined in this
> specification if, for each media stream in the SDP it received, the
> default destination for each component of that media stream appears in a
> candidate attribute."
>
> Does this mean that if, for whatever reason, some of the media streams
> (m=3D lines) do not contain any attributes ICE will NOT proceed?

I think the next paragraph is pretty clear:

   If this condition is not met, the agent MUST process the SDP based on
   normal RFC 3264 procedures, without using any of the ICE mechanisms
   described in the remainder of this specification with the following
   exceptions:

   1.  The agent MUST follow the rules of Section 10, which describe
       keepalive procedures for all agents.

   2.  If the agent is not proceeding with ICE because there were
       a=3Dcandidate attributes, but none that matched the default
       destination of the media stream, the agent MUST include an a=3Dice-
       mismatch attribute in its answer.

=2D-=20
R=E9mi Denis-Courmont


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



From mmusic-bounces@ietf.org Mon Oct 22 07:48:07 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IjvkK-0006sm-W5; Mon, 22 Oct 2007 07:47:00 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IjvkJ-0006rE-9C
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 22 Oct 2007 07:46:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IjvkI-0006qq-Hz
	for mmusic@ietf.org; Mon, 22 Oct 2007 07:46:58 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IjvkB-00040w-9q
	for mmusic@ietf.org; Mon, 22 Oct 2007 07:46:57 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	95AC220762; Mon, 22 Oct 2007 13:46:40 +0200 (CEST)
X-AuditID: c1b4fb3c-b1e82bb0000007e1-6e-471c8da0c682
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	80B5820731; Mon, 22 Oct 2007 13:46:40 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 22 Oct 2007 13:46:40 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] ICE with media streams without candidates
Date: Mon, 22 Oct 2007 13:46:39 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF02A5D6FC@esealmw113.eemea.ericsson.se>
In-Reply-To: <200710221431.09094.remi.denis-courmont@nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] ICE with media streams without candidates
Thread-Index: AcgUn8eUubrUppUXS06MzjvMu6Q8VgAAMX3g
References: <CA9998CD4A020D418654FCDEF4E707DF02A21742@esealmw113.eemea.ericsson.se>
	<200710221431.09094.remi.denis-courmont@nokia.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: =?iso-8859-1?Q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>,
	<mmusic@ietf.org>
X-OriginalArrivalTime: 22 Oct 2007 11:46:40.0186 (UTC)
	FILETIME=[359D71A0:01C814A1]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: 
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>
Errors-To: mmusic-bounces@ietf.org


Hi,=20

>>"The agent will proceed with the ICE procedures defined in this=20
>>specification if, for each media stream in the SDP it received, the=20
>>default destination for each component of that media stream appears in =

>>a candidate attribute."
>>
>>Does this mean that if, for whatever reason, some of the media streams =

>>(m=3D lines) do not contain any attributes ICE will NOT proceed?
>=20
>I think the next paragraph is pretty clear:
>=20
>    If this condition is not met, the agent MUST process the SDP based =
on
>    normal RFC 3264 procedures, without using any of the ICE mechanisms
>    described in the remainder of this specification with the following
>    exceptions:
>=20
>    1.  The agent MUST follow the rules of Section 10, which describe
>        keepalive procedures for all agents.
>=20
>    2.  If the agent is not proceeding with ICE because there were
>        a=3Dcandidate attributes, but none that matched the default
>        destination of the media stream, the agent MUST include an =
a=3Dice-
>        mismatch attribute in its answer.

What is the reason for having this all-or-nothing restriction? Why can't =
I perform ICE on other media streams, with candidates, just because some =
media streams do not contain candidates?

Regards,

Christer


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



From mmusic-bounces@ietf.org Mon Oct 22 08:30:03 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IjwOo-0001Sk-My; Mon, 22 Oct 2007 08:28:50 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IjwOm-0001N0-8D
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 22 Oct 2007 08:28:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IjwOK-0000bx-7j
	for mmusic@ietf.org; Mon, 22 Oct 2007 08:28:20 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IjwOI-0006cM-6k
	for mmusic@ietf.org; Mon, 22 Oct 2007 08:28:20 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l9MCRhHk017344; Mon, 22 Oct 2007 15:28:16 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 22 Oct 2007 15:27:59 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 22 Oct 2007 15:27:52 +0300
Received: from esdhcp04061.research.nokia.com ([172.21.40.61]) by
	esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 22 Oct 2007 15:27:51 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia TP-SP-SWD
To: "ext Christer Holmberg" <christer.holmberg@ericsson.com>, mmusic@ietf.org
Subject: Re: [MMUSIC] ICE with media streams without candidates
Date: Mon, 22 Oct 2007 15:28:41 +0300
User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405)
References: <CA9998CD4A020D418654FCDEF4E707DF02A21742@esealmw113.eemea.ericsson.se>
	<200710221431.09094.remi.denis-courmont@nokia.com>
	<CA9998CD4A020D418654FCDEF4E707DF02A5D6FC@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF02A5D6FC@esealmw113.eemea.ericsson.se>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200710221528.41180.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 22 Oct 2007 12:27:51.0602 (UTC)
	FILETIME=[F6B19920:01C814A6]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: 
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>
Errors-To: mmusic-bounces@ietf.org

Le Monday 22 October 2007 14:46:39 ext Christer Holmberg, vous avez =E9crit=
=A0:
> What is the reason for having this all-or-nothing restriction? Why can't I
> perform ICE on other media streams, with candidates, just because some
> media streams do not contain candidates?

The text says, ICE is not run if a media has no candidate matching the m=3D=
=20
line. It also says agents must insert a candidate matching the m=3D line (w=
hich=20
acts as the fallback candidate if the other endpoint does not support ICE).

Why would there be a media without a matching candidate anyway? A conformin=
g=20
agent will never emit such a SDP. If there is an Application Layer Gateway,=
=20
then ICE would likely fail, so better fallback to pre-ICE behavior. I think=
=20
that was the rationale beyond these instructions.

=2D-=20
R=E9mi Denis-Courmont


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



From mmusic-bounces@ietf.org Mon Oct 22 09:15:35 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ijx6P-0002HJ-VW; Mon, 22 Oct 2007 09:13:53 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1Ijx6O-0002DC-OS
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 22 Oct 2007 09:13:52 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ijx5A-0000IY-NS
	for mmusic@ietf.org; Mon, 22 Oct 2007 09:12:36 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ijx58-0008D6-B9
	for mmusic@ietf.org; Mon, 22 Oct 2007 09:12:34 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	289B320843; Mon, 22 Oct 2007 15:12:29 +0200 (CEST)
X-AuditID: c1b4fb3c-aee7cbb0000007e1-98-471ca1bdc686
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	1623C2088E; Mon, 22 Oct 2007 15:12:29 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 22 Oct 2007 15:12:28 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] ICE with media streams without candidates
Date: Mon, 22 Oct 2007 15:12:27 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF02A5DAFC@esealmw113.eemea.ericsson.se>
In-Reply-To: <200710221528.41180.remi.denis-courmont@nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] ICE with media streams without candidates
Thread-Index: AcgUpwlnB28N8kzcRA2xe8RtHG62jQABeCJw
References: <CA9998CD4A020D418654FCDEF4E707DF02A21742@esealmw113.eemea.ericsson.se>
	<200710221431.09094.remi.denis-courmont@nokia.com>
	<CA9998CD4A020D418654FCDEF4E707DF02A5D6FC@esealmw113.eemea.ericsson.se>
	<200710221528.41180.remi.denis-courmont@nokia.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: =?iso-8859-1?Q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>,
	<mmusic@ietf.org>
X-OriginalArrivalTime: 22 Oct 2007 13:12:28.0236 (UTC)
	FILETIME=[321788C0:01C814AD]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: 
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>
Errors-To: mmusic-bounces@ietf.org


Hi,=20

>>What is the reason for having this all-or-nothing restriction? Why=20
>>can't I perform ICE on other media streams, with candidates, just=20
>>because some media streams do not contain candidates?
>
>The text says, ICE is not run if a media has no candidate=20
>matching the m=3D line.

Yes. I can understand that ICE is not run for that specific media, but =
why does it also mean that I can't run ICE for other medias?

Or, have I missunderstood?

Regards,

Christer


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



From mmusic-bounces@ietf.org Mon Oct 22 10:03:04 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ijxrh-0003IM-EB; Mon, 22 Oct 2007 10:02:45 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1Ijxre-0003Ek-SU
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 22 Oct 2007 10:02:42 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ijxrd-0003E4-D5
	for mmusic@ietf.org; Mon, 22 Oct 2007 10:02:41 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ijxrc-0002pY-Mz
	for mmusic@ietf.org; Mon, 22 Oct 2007 10:02:41 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	0DFB92009B; Mon, 22 Oct 2007 16:02:40 +0200 (CEST)
X-AuditID: c1b4fb3e-b0835bb0000007e1-14-471cad7fd5ca
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	E7DBD203CF; Mon, 22 Oct 2007 16:02:39 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 22 Oct 2007 16:02:40 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 22 Oct 2007 16:02:39 +0200
Message-ID: <471CAD7F.8090106@ericsson.com>
Date: Mon, 22 Oct 2007 16:02:39 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Joe Pallas <pallas@cs.stanford.edu>
Subject: Re: [MMUSIC] draft-ietf-mmusic-rfc2326bis-14.txt
References: <E2FF60D7-3230-4DD6-8A92-117007AC1FB1@cs.stanford.edu>
In-Reply-To: <E2FF60D7-3230-4DD6-8A92-117007AC1FB1@cs.stanford.edu>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Oct 2007 14:02:39.0437 (UTC)
	FILETIME=[34E857D0:01C814B4]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
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>
Errors-To: mmusic-bounces@ietf.org

Hi,

See some the issues addressed. I think the comments regarding the first
sections of the document will be addressed somehow when that part is
rewritten.

Joe Pallas skrev:
> 
> Section C.1.5 on SDP attributes sendrecv, recvonly, and sendonly is
> confusing.  In particular, the mention of '"PLAY" mode' is odd, since
> RECORD mode is explicitly undefined, so PLAY mode is the only mode
> defined.  For that matter, why isn't "RECORD" removed from the grammar
> for mode -- is there some value to making it reserved but undefined? 
> Also, section 13.4.2 mentions the RECORD request, which no longer exists.

I have fixed the occurances of RECORD and removed it from the grammar. I
have also updated the text for the SDP directionality attributes. Is the
following text clearer?

The SDP attributes "a=sendrecv", "a=recvonly" and "a=sendonly" provides
instructions on which direction the media streams flow within a session.
When using RTSP the SDP can be delivered to a client using either RTSP
DESCRIBE or a number of RTSP external methods, like HTTP, FTP, and
email. Based on this the SDP applies to how the RTSP client will see the
complete session. Thus for media streams delivered from the RTSP server
to the client would be given the "a=recvonly" attribute.

The direction attributes are not commonly used in SDPs for RTSP, but may
occur. "a=recvonly" in a SDP provided to the RTSP client SHALL indicate
that media delivery will only occur in the direction from the RTSP
server to the client. In SDP provided to the RTSP client that lacks any
of the directionality attributes (a=recvonly, a=sendonly, a=sendrecv)
SHALL behave as if the "a=recvonly" attribute was received. Note that
this overrules the normal default rule defined in SDP [RFC4566]. The
usage of "a=sendonly" or "a=sendrecv" is not defined, nor is the
interpretation of SDP by other entities than the RTSP client.


>

> 
> Section F introduces new language on the interpretation of CR and LF for
> backward compatibility.  The language in RFC2326 was a bad idea, since
> it can be paraphrased as "Receivers should be prepared for senders to
> violate this specification."  While this is always true, putting it into
> the specification itself is unwise, as it appears to give license to
> violators.  That said, the language that was added to section F uses the
> word "should" in a dangerous way.  The new instruction raises doubts
> about the correct interpretation of sequences like CR LF LF, LF CR, and
> CR CR LF.  If there are, in fact, any RTSP 1.0 clients still extant that
> take such liberties, maybe it would be best to pretend they don't exist.
> 

I have posted the other day on how I have propose to addressed this.
Basically removing the text in section F.

Cheers

Magnus Westerlund

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


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



From mmusic-bounces@ietf.org Mon Oct 22 11:18:46 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ijz2a-0004Vb-RT; Mon, 22 Oct 2007 11:18:04 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IjEqE-0004rU-6U
	for mmusic-confirm+ok@megatron.ietf.org; Sat, 20 Oct 2007 09:58:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IjEqD-0004lM-AO
	for mmusic@ietf.org; Sat, 20 Oct 2007 09:58:13 -0400
Received: from poy.chewa.net ([194.242.114.73])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IjEq3-0002TJ-4X
	for mmusic@ietf.org; Sat, 20 Oct 2007 09:58:09 -0400
Received: from basile.remlab.net (unknown
	[IPv6:2002:3e4e:969c:0:211:11ff:fe25:e6b4])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: remi)
	by poy.chewa.net (Postfix) with ESMTP id 8112696805
	for <mmusic@ietf.org>; Sat, 20 Oct 2007 15:57:01 +0200 (CEST)
From: =?utf-8?q?R=C3=A9mi_Denis-Courmont?= <rdenis@simphalempin.com>
Organization: Remlab.net
To: mmusic@ietf.org
Subject: Re: [MMUSIC] RTSP 2.0: Issue [ 1701610 ] CR LF mitigations.
Date: Sat, 20 Oct 2007 16:56:53 +0300
User-Agent: KMail/1.9.7
References: <4718C918.5020707@ericsson.com>
In-Reply-To: <4718C918.5020707@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200710201656.53528.rdenis@simphalempin.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
X-Mailman-Approved-At: Mon, 22 Oct 2007 11:18:03 -0400
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>
Errors-To: mmusic-bounces@ietf.org

Le Friday 19 October 2007 18:11:20 Magnus Westerlund, vous avez =C3=A9crit=
=C2=A0:
> Joe Pallas suggested that we remove this text. I am actually agreeing
> with his proposal. Any objections?

I don't mind, so long as receivers are not forbidden from accepting sole CR=
 or=20
sole LF.

=2D-=20
R=C3=A9mi Denis-Courmont
http://www.remlab.net/


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



From mmusic-bounces@ietf.org Tue Oct 23 03:15:03 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IkDv4-00081D-5y; Tue, 23 Oct 2007 03:11:18 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IkDv2-00080U-In
	for mmusic-confirm+ok@megatron.ietf.org; Tue, 23 Oct 2007 03:11:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IkDum-0007sm-Ox
	for mmusic@ietf.org; Tue, 23 Oct 2007 03:11:00 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IkDuh-0000dv-0t
	for mmusic@ietf.org; Tue, 23 Oct 2007 03:10:55 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	1CB7A2010C; Tue, 23 Oct 2007 09:10:54 +0200 (CEST)
X-AuditID: c1b4fb3e-b1837bb0000007e1-d7-471d9e7e4766
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	02F2B200FA; Tue, 23 Oct 2007 09:10:54 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 23 Oct 2007 09:10:53 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: [MMUSIC] ICE with media streams without candidates
Date: Tue, 23 Oct 2007 09:10:52 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF02A8B9C8@esealmw113.eemea.ericsson.se>
In-Reply-To: <200710221528.41180.remi.denis-courmont@nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] ICE with media streams without candidates
Thread-Index: AcgUpwlnB28N8kzcRA2xe8RtHG62jQAmzDTg
References: <CA9998CD4A020D418654FCDEF4E707DF02A5D6FC@esealmw113.eemea.ericsson.se>
	<200710221528.41180.remi.denis-courmont@nokia.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: =?iso-8859-1?Q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>,
	<mmusic@ietf.org>
X-OriginalArrivalTime: 23 Oct 2007 07:10:53.0886 (UTC)
	FILETIME=[D9AA2DE0:01C81543]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: 
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>
Errors-To: mmusic-bounces@ietf.org


Hi,=20

>>What is the reason for having this all-or-nothing restriction? Why=20
>>can't I perform ICE on other media streams, with candidates, just=20
>>because some media streams do not contain candidates?
>=20
>The text says, ICE is not run if a media has no candidate=20
>matching the m=3D line. It also says agents must insert a=20
>candidate matching the m=3D line (which acts as the fallback=20
>candidate if the other endpoint does not support ICE).
>=20
>Why would there be a media without a matching candidate=20
>anyway? A conforming agent will never emit such a SDP. If=20
>there is an Application Layer Gateway, then ICE would likely=20
>fail, so better fallback to pre-ICE behavior. I think that=20
>was the rationale beyond these instructions.

One example:=20

Assume A calls B, and includes SDP with the ICE candidate attributes etc =
for each media stream.

In the middle there is a B2BUA application server, which wants to add a =
stream towards B, so it modifies the SDP by adding an extra m=3D line. =
The application server, however, does not support ICE, so it does not =
include any candidate attributes.

B will now receive an SDP where the m=3D line added by the application =
server does not contain candidates, so it will disable ICE also for the =
streams that did contain candiates.


A                                   B2BUA                                =
B

----- SDP ---------------------------->
      m=3Daudio                         ------ SDP =
------------------------>
	<candidates>                            m=3Daudio
                                              <candidates>
                                              m=3Dvideo

Another example:

Assume A calls B, and includes SDP with the ICE candidate attributes etc =
for each media stream.

In the middle there is a B2BUA application server, which realizes that =
transcoding is needed for one of the streams, so it modifies that part =
of the SDP. Again, however, the application server does not support ICE, =
so it does not include any candidate attributes for the transcoded media =
stream (it may forward the candidates it received, but that will cause =
an ICE mismatch anyway).

B will now receive an SDP where the m=3D line modified by the =
application server does not contain candidates (or, it does, but they =
cause a mismatch), so it will disable ICE also for the streams that did =
contain valid candiates.


A                                   B2BUA                                =
B

----- SDP ---------------------------->
      m=3Daudio                         ------ SDP =
------------------------>
	<candidates>=20
      m=3Dvideo                                m=3Daudio
      <candidates>                           <candidates>
                                             m=3Dvideo transcoded



Another example when some specific streams use some kind of relays =
(non-TURN) for the NAT traversal, and don't need ICE. But, I haven't =
thought very much of those use-cases yet.

Regards,

Christer



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



From mmusic-bounces@ietf.org Tue Oct 23 05:34:26 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IkG8L-00033n-Hj; Tue, 23 Oct 2007 05:33:09 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IkG8J-0002yJ-LI
	for mmusic-confirm+ok@megatron.ietf.org; Tue, 23 Oct 2007 05:33:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IkG8I-0002y2-O7
	for mmusic@ietf.org; Tue, 23 Oct 2007 05:33:06 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IkG8D-0006TQ-5S
	for mmusic@ietf.org; Tue, 23 Oct 2007 05:33:06 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	805B92088E; Tue, 23 Oct 2007 11:32:42 +0200 (CEST)
X-AuditID: c1b4fb3c-b0e80bb0000007e1-a0-471dbfbacdb4
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	5D151207C7; Tue, 23 Oct 2007 11:32:42 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 23 Oct 2007 11:32:41 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 23 Oct 2007 11:32:41 +0200
Message-ID: <471DBFB9.6050405@ericsson.com>
Date: Tue, 23 Oct 2007 11:32:41 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "mmusic (E-mail)" <mmusic@ietf.org>, 
	Xavier Marjou <xavier.marjou@orange-ftgroup.com>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Oct 2007 09:32:41.0844 (UTC)
	FILETIME=[A8CD8B40:01C81557]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: 
Subject: [MMUSIC] RTSP 2.0: [ 1701558 ] Pause response to live streams
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>
Errors-To: mmusic-bounces@ietf.org

Xavier asked more than a year ago the following question:

"when a client sends a PAUSE request for a live content,
which value is sent back in the Range header by the server?"

This is in regards to the following text from section 11.5 Pause on page
63 in draft version 15:

  "The pause point after any PAUSE request SHALL be returned to the
   client by adding a Range header with what remains unplayed of the
   PLAY request's ranges, i.e. including all the remaining ranges part
   of multiple range specification.  If one desires to resume playing a
   ranged request, one simply includes the Range header from the PAUSE
   response."

To me it should indicate the point the server is ceasing to deliver
media on. Also the live media have some time line. Either expressed in
UTC or in NPT since session start. What ever is used needs to be
reported. I don't think "now-" would be particular good answer. For that
reason a clearer text on this would be good.

However, this leads me to another issue related to the content being
played back. It might be time to be more explicit about the content
properties related to playback. I don't think the RTSP specification is
particular clear regarding how to handle the different playback
properties that exist. To my knowledge there are major 3 types of
content currently available.

A. On-demand content: Can be freely played from any point in time of the
content.

B. Live: Can only be played at the currently served point.

C. Live with recording: Where you can't play beyond what has been served
and which advances in real-time during the sessions progress. However,
the client can request to jump back in time, or pause for a while and
then resume at the playback point it was at, rather then the sessions
"now" point.

I think there are a few additional restrictions for the content type
that would need to be expressed to provide better support for how
content can be handled in the client. But that I think is for future
discussion.

However, my question is: Should we define a new SDP attribute that
expresses the contents major properties to allow RTSP clients to know
what to handle?

I know this means more work, however I believe it would make the general
text more clear when one can refer to this different behaviors in the
specification text.

For example to tie it back into the original question: By having these
attributes we could define more clearly when time-line times should be
used. And for example when "now-" is to be converted into the actual
time-line point in the session.

Cheers

Magnus Westerlund

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


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



From mmusic-bounces@ietf.org Tue Oct 23 08:32:35 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IkIua-0002zI-8P; Tue, 23 Oct 2007 08:31:08 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IkIuX-0002yP-Vk
	for mmusic-confirm+ok@megatron.ietf.org; Tue, 23 Oct 2007 08:31:05 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IkIuW-0002o8-SK
	for mmusic@ietf.org; Tue, 23 Oct 2007 08:31:04 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IkIuQ-0004CY-Vz
	for mmusic@ietf.org; Tue, 23 Oct 2007 08:30:59 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	54871206FB
	for <mmusic@ietf.org>; Tue, 23 Oct 2007 14:30:58 +0200 (CEST)
X-AuditID: c1b4fb3c-b1e82bb0000007e1-ef-471de9826f79
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	3D9C520067
	for <mmusic@ietf.org>; Tue, 23 Oct 2007 14:30:58 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 23 Oct 2007 14:30:57 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 23 Oct 2007 14:30:57 +0200
Message-ID: <471DE980.8040207@ericsson.com>
Date: Tue, 23 Oct 2007 14:30:56 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Re: [MMUSIC] RTSP: Speed header
References: <462387E3.20600@ericsson.com>
In-Reply-To: <462387E3.20600@ericsson.com>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Oct 2007 12:30:57.0452 (UTC)
	FILETIME=[8FE1CEC0:01C81570]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
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>
Errors-To: mmusic-bounces@ietf.org

Hi,

See inline:

Magnus Westerlund skrev:
> Hi,
> 
> I while back received an email with some questions on how the Speed
> header works in RTSP. There where also the issue how it interacts with
> the Scale header and with bandwidth adaptation and buffer management.
> 
> Lets do a recap of what the different mechanisms do.
> 
> Scale: Changes the rate at which media is presented to the user. So
> Scale=0.5 would mean slow motion, while Scale=5 would be fast forward in
> the stream.
> 
> Speed: Changes the media delivery rate. Speed=2 would mean that for each
> second a client would receive media that takes it 2 seconds to play back
> to the user. It would also mean that using RTP with a 90kHz timestamp
> clock the RTP streams timestamp values would increase with 180k ticks
> per second.
> 
> Bit-rate adaptation: A way of ensuring that the media traffic does not
> use more bandwidth then what is available. Which means that the server
> would need to change the media bit-rate sent if there isn't enough
> available for the current media stream. This could be done in a number
> of ways but most commonly are done by bit-stream switching. Going from a
> stored/delivered media stream in one quality to another lower quality
> that requires less bit-rate.
> 
> Buffer Management: An attempt to keep the clients buffer in a healthy
> state, aiming at keeping a certain amount of media time present in
> buffer to safeguard against temporary or longer term changes of bit-rate
> capacity available to the streaming session. Thus giving the server time
> to react to the change before an buffer-underrun situation occurs. At
> the same time safe-guard against overflowing buffers. This is for
> example done in 3GPP Packet-based Streaming Service (26.234 Rel6) where
> additional feedback and configuration information is provided for the
> buffer status. Thus allowing a server to change media transmission rate
> on the fly. Which is equivalent to a client using Speed. However it also
> needs to be able to perform bit-rate adaptation so that one can lower
> the quality but increase the speed to refill the buffer.
> 
> The interactions between the different behaviors are interesting but can
> become quite complex. For example the total bit-rate is speed x normal
> bit-rate. It might also be influenced by the Scale used as fast
> forwarding could be accomplished by simple turning up the frame-rate for
> video and rewriting the timestamps compared to scale 1. Slow motion
> could also mean that the bit-rate gets lower. However if trans-coding is
> done to handle Scale then bit-rate may not change at all. If there are a
> limited amount of bit-rate this means that bit-rate adaptation needs to
> step in and do what it can to keep bit-rate within limitations. If that
> can only operate on the media stream or can also contradict speed or
> influence how scale is handled is quite undefined.
> 
> I do have a few question due to this:
> 
> 1. Are people implementing Speed?
> 
> 2. If you are using Speed, how are you doing that, as I have described
> or otherwise?
> 
> 3. Should we remove speed from base specification?
> 
> 4. If not, what do you think needs to be clarified and do you have text
> proposal?

Time to bring up this topic again and get some closure on it. I have
reviewed what people have written and have a number of comments and
considerations around this.

First of all is the general congestion control. To me Speed header shall
not be used for congesting controlling the flow from the server to the
client. To me the usage that seems okay are:

1. In combination with scale to tell how it should fulfill the request.
Here I think the two main cases are Scale=x Speed=x for x!=1 and Scale=x
Speed=1. In other words, realize a playout speedup by increasing the
delivery rate to the client or if the server should rescale the content
to maintain the bit-rate.

2. To indicate faster than normal delivery to fill up the receiver
buffers, i.e. scale=1 speed=x where x>1. Then when buffer reached the
desired level the client requests that speed goes back to 1.0.

Both these has interactions with the actual congestion control used. If
the available bit-rate is limited in both these case the content needs
to be adapted to fulfill.

Are these interesting enough that we actually should write them up so
that it is clear what they mean? The alternative is to remove speed for
now and have the behaviors being undefined in these cases.

Cheers

Magnus Westerlund

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


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



From mmusic-bounces@ietf.org Tue Oct 23 08:42:39 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IkJ5V-0001tn-Se; Tue, 23 Oct 2007 08:42:25 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IkJ5U-0001tF-Kh
	for mmusic-confirm+ok@megatron.ietf.org; Tue, 23 Oct 2007 08:42:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IkJ5T-0001sz-R4
	for mmusic@ietf.org; Tue, 23 Oct 2007 08:42:23 -0400
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IkJ5N-0005iV-EZ
	for mmusic@ietf.org; Tue, 23 Oct 2007 08:42:23 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l9NCfP16015729; Tue, 23 Oct 2007 15:42:09 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 23 Oct 2007 15:41:40 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 23 Oct 2007 15:28:01 +0300
Received: from esdhcp04179.research.nokia.com ([172.21.41.79]) by
	esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 23 Oct 2007 15:28:01 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia TP-SP-SWD
To: "ext Christer Holmberg" <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] ICE with media streams without candidates
Date: Tue, 23 Oct 2007 15:28:52 +0300
User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405)
References: <CA9998CD4A020D418654FCDEF4E707DF02A5D6FC@esealmw113.eemea.ericsson.se>
	<200710221528.41180.remi.denis-courmont@nokia.com>
	<CA9998CD4A020D418654FCDEF4E707DF02A8B9C8@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF02A8B9C8@esealmw113.eemea.ericsson.se>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200710231528.52224.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 23 Oct 2007 12:28:01.0060 (UTC)
	FILETIME=[26BE8640:01C81570]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
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>
Errors-To: mmusic-bounces@ietf.org

	Christer,

Le Tuesday 23 October 2007 10:10:52 ext Christer Holmberg, vous avez =E9cri=
t=A0:
> Assume A calls B, and includes SDP with the ICE candidate attributes etc
> for each media stream.
>
> In the middle there is a B2BUA application server, which wants to add a
> stream towards B, so it modifies the SDP by adding an extra m=3D line. The
> application server, however, does not support ICE, so it does not include
> any candidate attributes.

We can probably agree that if there is something that modifies this SDP eve=
n=20
though it does not terminate the SIP session, anything can happen. And=20
probably nobody wants to start a SBC flame war here ;)

As a developper, I would rather it had been per-media, or better yet, a=20
per-component process, because it would have been much simpler to implement=
=20
and integrate. There are however several valid reasons why ICE is a SIP=20
per-session process, as far as ICE is used with SIP.

I can think of plenty of loopholes if one media has ICE, but not another on=
e.=20
=46or instance, how would the UA know when to start sending media? But most=
=20
importantly, the decision to abort ICE when some inconsistency is detected =
is=20
all about maximizing backward compatibility with existing setups. If there =
is=20
some middlebox modifying the SDP in a way that breaks ICE, it is safest to=
=20
assume that ICE might not work. As such it should not be used at all. ICE w=
as=20
simply not meant to operate in such scenarios.

Also, in most scenarios where the SDP media information is modified, it is=
=20
most probably that all medias will be modified in a way that would make the=
m=20
ineligible for ICE: probably the original medias (those NOT coming from the=
=20
application server) would go through some kind of media proxying device=20
anyway. Right?

=2D-=20
R=E9mi Denis-Courmont


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



From mmusic-bounces@ietf.org Tue Oct 23 09:11:44 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IkJX6-0000mK-KH; Tue, 23 Oct 2007 09:10:56 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IkJX4-0000j0-V3
	for mmusic-confirm+ok@megatron.ietf.org; Tue, 23 Oct 2007 09:10:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IkJX3-0000fi-Ib
	for mmusic@ietf.org; Tue, 23 Oct 2007 09:10:53 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IkJWx-0006zE-7r
	for mmusic@ietf.org; Tue, 23 Oct 2007 09:10:53 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	A1D9220451; Tue, 23 Oct 2007 15:10:42 +0200 (CEST)
X-AuditID: c1b4fb3c-b0e80bb0000007e1-14-471df2d2cf90
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	92AE520066; Tue, 23 Oct 2007 15:10:42 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 23 Oct 2007 15:10:42 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] ICE with media streams without candidates
Date: Tue, 23 Oct 2007 15:10:41 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF02ABE439@esealmw113.eemea.ericsson.se>
In-Reply-To: <200710231528.52224.remi.denis-courmont@nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] ICE with media streams without candidates
Thread-Index: AcgVciJ+n1HcNJIDSHaexxX0QwOrNwAAyyuA
References: <CA9998CD4A020D418654FCDEF4E707DF02A5D6FC@esealmw113.eemea.ericsson.se>
	<200710221528.41180.remi.denis-courmont@nokia.com>
	<CA9998CD4A020D418654FCDEF4E707DF02A8B9C8@esealmw113.eemea.ericsson.se>
	<200710231528.52224.remi.denis-courmont@nokia.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: =?iso-8859-1?Q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 23 Oct 2007 13:10:42.0438 (UTC)
	FILETIME=[1D71CA60:01C81576]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
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>
Errors-To: mmusic-bounces@ietf.org


Hi,=20

>>Assume A calls B, and includes SDP with the ICE candidate attributes=20
>>etc for each media stream.
>>
>>In the middle there is a B2BUA application server, which wants to add=20
>>a stream towards B, so it modifies the SDP by adding an extra m=3D =
line.=20
>>The application server, however, does not support ICE, so it does not=20
>>include any candidate attributes.
>=20
>We can probably agree that if there is something that=20
>modifies this SDP even though it does not terminate the SIP=20
>session, anything can happen. And probably nobody wants to=20
>start a SBC flame war here ;)
>=20
>As a developper, I would rather it had been per-media, or=20
>better yet, a per-component process, because it would have=20
>been much simpler to implement and integrate. There are=20
>however several valid reasons why ICE is a SIP per-session=20
>process, as far as ICE is used with SIP.
>
>I can think of plenty of loopholes if one media has ICE, but=20
>not another one.=20
>For instance, how would the UA know when to start sending=20
>media? But most importantly, the decision to abort ICE when=20
>some inconsistency is detected is all about maximizing=20
>backward compatibility with existing setups. If there is some=20
>middlebox modifying the SDP in a way that breaks ICE, it is=20
>safest to assume that ICE might not work. As such it should=20
>not be used at all. ICE was simply not meant to operate in=20
>such scenarios.

I am not arguing against the mismatch rules as such, I am just wondering =
if there are technical reasons why they can't be done per media.

>Also, in most scenarios where the SDP media information is=20
>modified, it is most probably that all medias will be=20
>modified in a way that would make them ineligible for ICE:=20
>probably the original medias (those NOT coming from the=20
>application server) would go through some kind of media=20
>proxying device anyway. Right?

Not necessarily. In my examples the media NOT generated/transcoded by =
the application server does not need to go through any media proxying =
device.

Regards,

Christer


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



From mmusic-bounces@ietf.org Tue Oct 23 11:10:37 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IkLO3-00019o-Ol; Tue, 23 Oct 2007 11:09:43 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IkLO0-00015Y-Pa
	for mmusic-confirm+ok@megatron.ietf.org; Tue, 23 Oct 2007 11:09:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IkLNz-000138-Rg
	for mmusic@ietf.org; Tue, 23 Oct 2007 11:09:39 -0400
Received: from audl953.usa.alcatel.com ([143.209.238.162])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IkLNt-0004sD-L3
	for mmusic@ietf.org; Tue, 23 Oct 2007 11:09:39 -0400
Received: from srsdmail01.PVNS.COM (mail.pvnetsolutions.com [128.251.100.16])
	by audl953.usa.alcatel.com (ALCANET) with ESMTP id l9NF9Ltb014907;
	Tue, 23 Oct 2007 10:09:21 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] RTSP 2.0: [ 1701558 ] Pause response to live streams
Date: Tue, 23 Oct 2007 08:09:12 -0700
Message-ID: <758B5A159B385447B4F950DE72D7D7AD01AAC257@srsdmail01.PVNS.COM>
In-Reply-To: <471DBFB9.6050405@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] RTSP 2.0: [ 1701558 ] Pause response to live streams
Thread-Index: AcgVWMezozRGQapZRgaG2yEX6UtJ7AAKuA3A
References: <471DBFB9.6050405@ericsson.com>
From: "Mike Severa" <severa@pvnetsolutions.com>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>,
	"mmusic (E-mail)" <mmusic@ietf.org>,
	"Xavier Marjou" <xavier.marjou@orange-ftgroup.com>
X-Scanned-By: MIMEDefang 2.51 on 143.209.238.34
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Cc: 
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>
Errors-To: mmusic-bounces@ietf.org

I agree it would be good to be more explicit. I think this is
particularly important with something like 'live with recording' because
a PAUSE on such content should allow a client to behave differently upon
restarting (not with reposition) than for normal live (media data that
the streaming server has already sent, and thus is still in the
client-side jitter buffer, is still valid (contiguous in presentation
time), whereas in a 'true live' scenario that will not be the case).=20
I also tend to believe that there is a 4th type of content and that is
On-Demand content with an unknown end-time. However, from the standpoint
of distinction from the other content types, its properties are likely
no different than live with recording (unknown end time but still
randomly accessible).=20

Would the proposed new attribute also imply that the properties for
something like live vs On-Demand will no longer be distinguished by the
format of the range header? Or would the goal to be to try to add
something 'on top of' the current semantics?

Thanks,

Mike

-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]=20
Sent: Tuesday, October 23, 2007 2:33 AM
To: mmusic (E-mail); Xavier Marjou
Subject: [MMUSIC] RTSP 2.0: [ 1701558 ] Pause response to live streams

Xavier asked more than a year ago the following question:

"when a client sends a PAUSE request for a live content, which value is
sent back in the Range header by the server?"

This is in regards to the following text from section 11.5 Pause on page
63 in draft version 15:

  "The pause point after any PAUSE request SHALL be returned to the
   client by adding a Range header with what remains unplayed of the
   PLAY request's ranges, i.e. including all the remaining ranges part
   of multiple range specification.  If one desires to resume playing a
   ranged request, one simply includes the Range header from the PAUSE
   response."

To me it should indicate the point the server is ceasing to deliver
media on. Also the live media have some time line. Either expressed in
UTC or in NPT since session start. What ever is used needs to be
reported. I don't think "now-" would be particular good answer. For that
reason a clearer text on this would be good.

However, this leads me to another issue related to the content being
played back. It might be time to be more explicit about the content
properties related to playback. I don't think the RTSP specification is
particular clear regarding how to handle the different playback
properties that exist. To my knowledge there are major 3 types of
content currently available.

A. On-demand content: Can be freely played from any point in time of the
content.

B. Live: Can only be played at the currently served point.

C. Live with recording: Where you can't play beyond what has been served
and which advances in real-time during the sessions progress. However,
the client can request to jump back in time, or pause for a while and
then resume at the playback point it was at, rather then the sessions
"now" point.

I think there are a few additional restrictions for the content type
that would need to be expressed to provide better support for how
content can be handled in the client. But that I think is for future
discussion.

However, my question is: Should we define a new SDP attribute that
expresses the contents major properties to allow RTSP clients to know
what to handle?

I know this means more work, however I believe it would make the general
text more clear when one can refer to this different behaviors in the
specification text.

For example to tie it back into the original question: By having these
attributes we could define more clearly when time-line times should be
used. And for example when "now-" is to be converted into the actual
time-line point in the session.

Cheers

Magnus Westerlund

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


_______________________________________________
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 Tue Oct 23 11:22:13 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IkLZf-0002Xr-AW; Tue, 23 Oct 2007 11:21:43 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IkLZd-0002W1-OI
	for mmusic-confirm+ok@megatron.ietf.org; Tue, 23 Oct 2007 11:21:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IkLZc-0002UX-Bc
	for mmusic@ietf.org; Tue, 23 Oct 2007 11:21:40 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IkLZV-0005aK-Jc
	for mmusic@ietf.org; Tue, 23 Oct 2007 11:21:40 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	0D6FA207A9; Tue, 23 Oct 2007 17:21:28 +0200 (CEST)
X-AuditID: c1b4fb3c-afe7ebb0000007e1-1f-471e11771967
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	E7CAB2052A; Tue, 23 Oct 2007 17:21:27 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 23 Oct 2007 17:21:27 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 23 Oct 2007 17:21:27 +0200
Message-ID: <471E1177.3010906@ericsson.com>
Date: Tue, 23 Oct 2007 17:21:27 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Mike Severa <severa@pvnetsolutions.com>
Subject: Re: [MMUSIC] RTSP 2.0: [ 1701558 ] Pause response to live streams
References: <471DBFB9.6050405@ericsson.com>
	<758B5A159B385447B4F950DE72D7D7AD01AAC257@srsdmail01.PVNS.COM>
In-Reply-To: <758B5A159B385447B4F950DE72D7D7AD01AAC257@srsdmail01.PVNS.COM>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Oct 2007 15:21:27.0648 (UTC)
	FILETIME=[618DD600:01C81588]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: Xavier Marjou <xavier.marjou@orange-ftgroup.com>,
	"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>
Errors-To: mmusic-bounces@ietf.org

Mike Severa skrev:
> I agree it would be good to be more explicit. I think this is
> particularly important with something like 'live with recording' because
> a PAUSE on such content should allow a client to behave differently upon
> restarting (not with reposition) than for normal live (media data that
> the streaming server has already sent, and thus is still in the
> client-side jitter buffer, is still valid (contiguous in presentation
> time), whereas in a 'true live' scenario that will not be the case). 
> I also tend to believe that there is a 4th type of content and that is
> On-Demand content with an unknown end-time. However, from the standpoint
> of distinction from the other content types, its properties are likely
> no different than live with recording (unknown end time but still
> randomly accessible). 

Please consider if this fourth type really is having different
properties than live with recording. Now that you mention it I think
there is this other type of content where it could be dynamically
updated. Consider content that represents a playlist that is controlled
by some other protocol. That length could at any point in time be
changed. But I don't know if I really like to go there, because this
type of content has other implications.

> 
> Would the proposed new attribute also imply that the properties for
> something like live vs On-Demand will no longer be distinguished by the
> format of the range header? Or would the goal to be to try to add
> something 'on top of' the current semantics?
> 

I would propose to be explicit, I think both in request and in SDP to
indicate what properties the content actually have. That way the most
correct Range format and usage can be applied without consideration for
carrying extra semantics.

cheers

Magnus Westerlund

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


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



From mmusic-bounces@ietf.org Tue Oct 23 18:15:07 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IkS0H-0001qC-R4; Tue, 23 Oct 2007 18:13:37 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IkS0G-0001QC-94
	for mmusic-confirm+ok@megatron.ietf.org; Tue, 23 Oct 2007 18:13:36 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IkS0F-0001Jq-Pd
	for mmusic@ietf.org; Tue, 23 Oct 2007 18:13:35 -0400
Received: from de307622-de-outbound.net.avaya.com ([198.152.71.100])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IkS0F-0003cv-E3
	for mmusic@ietf.org; Tue, 23 Oct 2007 18:13:35 -0400
X-IronPort-AV: E=Sophos;i="4.21,320,1188792000"; d="scan'208";a="68124061"
Received: from unknown (HELO 306181ANEX3.global.avaya.com) ([135.9.6.105])
	by de307622-de-outbound.net.avaya.com with ESMTP;
	23 Oct 2007 18:13:34 -0400
Received: from [135.9.42.64] ([135.9.42.64]) by 306181ANEX3.global.avaya.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 23 Oct 2007 16:12:47 -0600
Message-ID: <471E71A4.70805@avaya.com>
Date: Tue, 23 Oct 2007 16:11:48 -0600
From: "Robert R. Gilman" <rrg@avaya.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: 'mmusic' <mmusic@ietf.org>, Flemming Andreasen <fandreas@cisco.com>
Subject: [MMUSIC] comments on
	draft-ietf-mmusic-sdp-capability-negotiation-06.txt
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Oct 2007 22:12:47.0615 (UTC)
	FILETIME=[D7F5F0F0:01C815C1]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: "Even, Roni" <roni.even@polycom.co.il>
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>
Errors-To: mmusic-bounces@ietf.org

Flemming-
I have one minor suggestion for the acap attribute definition.  Insofar as
the contents must be an attribute, why not omit the "a=" part?  Thus,
for example, the line
	a=acap:1 a=ptime:20
would become
	a=acap:1 ptime:20

Magnus Westerlund used the acap attribute in an example like
	a=acap:2 b=AS:128
when he was exploring the use of cap-neg for AMR parameter negotiation,
but I'd much prefer we define a different capability attribute - call
it bcap - that can be used to specify a bandwidth parameter for a pcfg
attribute.  Something like
	a=acap:1 ptime:20
	a=bcap:1 AS:128
	a=pcfg:1 a=1 b=1 ....
I believe we plan to define that in the upcoming version of the media-
capabilities draft (along with several other attributes.)
Comments?
-Bob
----------------------------------------------------
Bob Gilman       rrg@avaya.com      +1 303 538 3868



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



From mmusic-bounces@ietf.org Wed Oct 24 02:21:45 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IkZb4-0006mi-Ce; Wed, 24 Oct 2007 02:20:06 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IkZb1-0006mO-F2
	for mmusic-confirm+ok@megatron.ietf.org; Wed, 24 Oct 2007 02:20:03 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IkZb1-0006mF-3i; Wed, 24 Oct 2007 02:20:03 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IkZb0-000175-MU; Wed, 24 Oct 2007 02:20:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 923912AC81;
	Wed, 24 Oct 2007 06:20:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IkZaz-0003UQ-RS; Wed, 24 Oct 2007 02:20:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IkZaz-0003UQ-RS@stiedprstage1.ietf.org>
Date: Wed, 24 Oct 2007 02:20:01 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action:draft-ietf-mmusic-file-transfer-mech-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>
Errors-To: mmusic-bounces@ietf.org

--NextPart

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


	Title           : A Session Description Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer
	Author(s)       : M. Garcia-Martin, et al.
	Filename        : draft-ietf-mmusic-file-transfer-mech-04.txt
	Pages           : 45
	Date            : 2007-10-24

This document provides a mechanism to negotiate the transfer of one
or more files between two endpoints by using the Session Description
Protocol (SDP) offer/answer model specified in RFC 3264.  SDP is
extended to describe the attributes of the files to be transferred.
The offerer can either describe the files it wants to send, or the
files it would like to receive.  The answerer can either accept or
reject the offer separately for each individual file.  The transfer
of one or more files is initiated after a successful negotiation.
The Message Session Relay Protocol (MSRP) is defined as the default
mechanism to actually carry the files between the endpoints.  The
conventions on how to use MSRP for file transfer are also provided in
this document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-file-transfer-mech-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-file-transfer-mech-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-file-transfer-mech-04.txt".

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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-file-transfer-mech-04.txt

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

Content-Type: text/plain
Content-ID: <2007-10-24021022.I-D\@ietf.org>


--OtherAccess--

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

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

--NextPart--





From mmusic-bounces@ietf.org Wed Oct 24 02:24:25 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IkZfA-0006P6-ID; Wed, 24 Oct 2007 02:24:20 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IkZf8-0006P0-Ka
	for mmusic-confirm+ok@megatron.ietf.org; Wed, 24 Oct 2007 02:24:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IkZf8-0006Or-AJ
	for mmusic@ietf.org; Wed, 24 Oct 2007 02:24:18 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IkZez-0007kH-Gc
	for mmusic@ietf.org; Wed, 24 Oct 2007 02:24:18 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l9O6No0g032695; Wed, 24 Oct 2007 09:23:52 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 24 Oct 2007 09:23:32 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 24 Oct 2007 09:23:28 +0300
Received: from [10.144.23.50] ([10.144.23.50]) by esebh102.NOE.Nokia.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 24 Oct 2007 09:23:28 +0300
Message-ID: <471EE4E0.3040307@nsn.com>
Date: Wed, 24 Oct 2007 09:23:28 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: mmusic <mmusic@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Oct 2007 06:23:28.0166 (UTC)
	FILETIME=[63E58460:01C81606]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: "Salvatore Loreto \(SA/ERI\)" <Salvatore.Loreto@ericsson.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	"Isomaki Markus \(Nokia-SIR/Espoo\)" <Markus.Isomaki@nokia.com>
Subject: [MMUSIC] File transfer draft -04
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>
Errors-To: mmusic-bounces@ietf.org

As you probably noticed, I have just posted a new version of the file 
transfer draft. There is an HTML version and a diff at:

http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-04.html
http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-04-from-3.html

We are getting very close to finish the draft, so, I would like people 
to take a look at the list of changes (at least), and see if they have 
been properly documented.

List of changes:

- Added the notion of a file-transfer identifier, which is materialized
in the 'file-transfer-id' attribute. It contains a new identifier per
new file transfer. This is to avoid that a repetition of the SDP (due to
session timers, or adding new media streams) causes a new file transfer
and aborts the ongoing one. The 'file-transfer-id' attribute replaces
the existing 'file-transfer' attribute.

- The existing draft had a lot of complexity for dealing with several
hashing algorithms. Since we use the has just for file transfer
verification and file identification, just using a single algorithm
seems to serve the purpose. So, the current version uses SHA-1 and
leaves the door open for future extensions that can define new hashing
algorithms.

- Clarified the requirements that other protocol than MSRP should
fulfill in order to be used for the file transfer.

- Clarified that 'sendonly' and 'recvonly' refers to the direction of
MSRP SEND request, and does not preclude other MSRP messages (200, REPORT).

- The name selector syntax allows percent encoding.

- Fixed an error with the hash value syntax

- The 'file-range' attribute allows to signal the
"last-byte-of-the-file" with a "*" character (like in MSRP).

- The 'file-range' terminology has made it consistent: now the terms
"start range" and "end range" are used to refer to the two integers that
define the file range.

- Clarified that it is mandatory to implement message/cpim, but its
usage is negotiated in SDP.

- Clarified the use case that involves a non-supporting endpoint wwhich
does not also support multipart MIME and receives an SDP offer with a
side-by icon body.

- Noted that the hash is not used for strong integrity verification.

- Several other minor clarifications.

/Miguel
-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Espoo, Finland



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



From mmusic-bounces@ietf.org Wed Oct 24 13:05:58 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ikjdu-00034Q-Br; Wed, 24 Oct 2007 13:03:42 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1Ikjdt-00034I-IG
	for mmusic-confirm+ok@megatron.ietf.org; Wed, 24 Oct 2007 13:03:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ikjdt-00034A-8S; Wed, 24 Oct 2007 13:03:41 -0400
Received: from [74.95.2.169] (helo=delta.rtfm.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ikjdp-0005ut-Uz; Wed, 24 Oct 2007 13:03:41 -0400
Received: from delta.rtfm.com (localhost.rtfm.com [127.0.0.1])
	by delta.rtfm.com (Postfix) with ESMTP id CDB1B33C28;
	Wed, 24 Oct 2007 09:59:08 -0700 (PDT)
Date: Wed, 24 Oct 2007 09:59:08 -0700
From: Eric Rescorla <ekr@networkresonance.com>
To: avt@ietf.org, mmusic@ietf.org
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20071024165908.CDB1B33C28@delta.rtfm.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: 
Subject: [MMUSIC] Symmetry breaking for DTLS-SRTP
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>
Errors-To: mmusic-bounces@ietf.org

TLS (and by extension) DTLS-SRTP requires unambiguity about which side
is to be the client and which is the server. This isn't an issue of
credentials--DTLS-SRTP assumes that each side can take either
role--it's just that TLS requires that one side initiate the
handshake. My original intention had been to make this conditional on
which side was the offerer and which was the answerer, but JDR pointed
out in ORD that there are cases involving 3PCC where it's not
unambiguous which is which.

Here's the paradigmatic case, transcribed from a phone call with
JDR (so any errors are my fault):


Alice                        Controller                        Bob
------------------------------------------------------------------
INVITE + Offer ->
                              INVITE ->
                                                     <- OK + Offer
                      <- OK + Answer                              
                              ACK + Answer ->
ACK ->

Because the controller sends an INVITE with no offer, Bob is the
offererer, and of course Alice is. So, you can't use offerer
or answerer to break symmetry. 

This same problem occurs with ICE, which uses a random tiebreaker
value in the ICE messages to determine which side should take
which role (controlling vs. controlled). This works because
in ICE both sides are trying to transmit so they quickly 
detect conflicts. Unfortunately, in DTLS-SRTP, the server just
waits so if the rule we adopt allows both sides to think they
are the server then we get deadlock. The above exchange 
shows how both sides can be offerer so clearly we can't have
offerer=server, but it seems that we could make a new exchange
where both sides are answerer in which case we can't have
offerer=client. JDR tells me that we don't have an actual
use case like this yet but I would not want to count on that
unless we're very sure.

We could use exactly the trick that ICE uses but that requires
modifying DTLS to make the server send messages unprompted.
I don't think that's necessary here because we can break
the tie in the SDP where we announce the DTLS-SRTP capability
(however that's done).

The basic principle is this:
1. Each side generates a random tiebreaker value T.
2. In the SDP offer/answer, he indicates whether he wishes
   to be the TLS client or server (if you're the offerer
   you SHOULD ask to be the server since that's faster, 
   and vice versa).
3. If each side sees a consistent view (one client, one 
   server) then that is what is used.
4. If the views are inconsistent, then the side with the
   higher T is be the client.

This is basically the same algorithm as used with ICE, just
moving the tiebreaker into the SDP.

Does anyone see a problem with this?

-Ekr






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



From mmusic-bounces@ietf.org Wed Oct 24 15:17:48 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Iklib-0007Hu-Gg; Wed, 24 Oct 2007 15:16:41 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1Iklia-0007G5-NR
	for mmusic-confirm+ok@megatron.ietf.org; Wed, 24 Oct 2007 15:16:40 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Iklia-0007Fw-Bu; Wed, 24 Oct 2007 15:16:40 -0400
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=bemg01.siemenscomms.co.uk)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IkliZ-00070L-JE; Wed, 24 Oct 2007 15:16:40 -0400
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JQF00B3MK74H7@siemenscomms.co.uk>; Wed,
	24 Oct 2007 20:16:16 +0100 (BST)
Date: Wed, 24 Oct 2007 20:16:37 +0100
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [MMUSIC] Symmetry breaking for DTLS-SRTP
In-reply-to: <20071024165908.CDB1B33C28@delta.rtfm.com>
To: Eric Rescorla <ekr@networkresonance.com>, avt@ietf.org, mmusic@ietf.org
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D037D5E4@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Thread-Topic: [MMUSIC] Symmetry breaking for DTLS-SRTP
Thread-Index: AcgWYYUSDnaoYlqJS0+cdjPoIgDg1QADmipA
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <20071024165908.CDB1B33C28@delta.rtfm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: 
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>
Errors-To: mmusic-bounces@ietf.org

Ekr,

I don't have a problem with the solution, but I am doubtful whether it
is a problem we need to solve. The case illustrated is based on the
assumption that offer and answer are symmetrical, in the sense that an
offer can be reused as an answer (and vice versa). In this case the
offer from A becomes an answer to B and vice versa. There are two
extensions to SDP that I am aware of that break this, and therefore any
controller that misuses SDP in this way will screw things up. One
example is the key management extension when used to carry MIKEY,
because a MIKEY request (which always goes in the offer) is very
different in syntax and semantics from a MIKEY response (which always
goes in the answer). Of course, this will not apply when using DTLS-SRTP
as the means of key management. The second example is the SDP capability
negotiation draft, which certainly will be applicable with DTLS-SRTP.

I am not aware of how the particular flow shown would arise. It is not
documented in RFC 3725 (3PCC). It has similarities to flow II in RFC
3725, which the RFC does not recommend. The other 3PCC flows in RFC 3725
do not mix up offers and answers in this way.

I also questioned the need for the solution in ICE, but as it came
virtually for free, it was not worth arguing about.

If we continue this discussion, I would suggest we stick to the MMUSIC
list rather than AVT.

John

> -----Original Message-----
> From: Eric Rescorla [mailto:ekr@networkresonance.com] 
> Sent: 24 October 2007 17:59
> To: avt@ietf.org; mmusic@ietf.org
> Subject: [MMUSIC] Symmetry breaking for DTLS-SRTP
> 
> TLS (and by extension) DTLS-SRTP requires unambiguity about which side
> is to be the client and which is the server. This isn't an issue of
> credentials--DTLS-SRTP assumes that each side can take either
> role--it's just that TLS requires that one side initiate the
> handshake. My original intention had been to make this conditional on
> which side was the offerer and which was the answerer, but JDR pointed
> out in ORD that there are cases involving 3PCC where it's not
> unambiguous which is which.
> 
> Here's the paradigmatic case, transcribed from a phone call with
> JDR (so any errors are my fault):
> 
> 
> Alice                        Controller                        Bob
> ------------------------------------------------------------------
> INVITE + Offer ->
>                               INVITE ->
>                                                      <- OK + Offer
>                       <- OK + Answer                              
>                               ACK + Answer ->
> ACK ->
> 
> Because the controller sends an INVITE with no offer, Bob is the
> offererer, and of course Alice is. So, you can't use offerer
> or answerer to break symmetry. 
> 
> This same problem occurs with ICE, which uses a random tiebreaker
> value in the ICE messages to determine which side should take
> which role (controlling vs. controlled). This works because
> in ICE both sides are trying to transmit so they quickly 
> detect conflicts. Unfortunately, in DTLS-SRTP, the server just
> waits so if the rule we adopt allows both sides to think they
> are the server then we get deadlock. The above exchange 
> shows how both sides can be offerer so clearly we can't have
> offerer=server, but it seems that we could make a new exchange
> where both sides are answerer in which case we can't have
> offerer=client. JDR tells me that we don't have an actual
> use case like this yet but I would not want to count on that
> unless we're very sure.
> 
> We could use exactly the trick that ICE uses but that requires
> modifying DTLS to make the server send messages unprompted.
> I don't think that's necessary here because we can break
> the tie in the SDP where we announce the DTLS-SRTP capability
> (however that's done).
> 
> The basic principle is this:
> 1. Each side generates a random tiebreaker value T.
> 2. In the SDP offer/answer, he indicates whether he wishes
>    to be the TLS client or server (if you're the offerer
>    you SHOULD ask to be the server since that's faster, 
>    and vice versa).
> 3. If each side sees a consistent view (one client, one 
>    server) then that is what is used.
> 4. If the views are inconsistent, then the side with the
>    higher T is be the client.
> 
> This is basically the same algorithm as used with ICE, just
> moving the tiebreaker into the SDP.
> 
> Does anyone see a problem with this?
> 
> -Ekr
> 
> 
> 
> 
> 
> 
> _______________________________________________
> 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 Oct 24 15:41:11 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ikm68-0001Ar-Bv; Wed, 24 Oct 2007 15:41:00 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1Ikm67-0001AS-7N
	for mmusic-confirm+ok@megatron.ietf.org; Wed, 24 Oct 2007 15:40:59 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ikm66-0001AJ-St
	for mmusic@ietf.org; Wed, 24 Oct 2007 15:40:58 -0400
Received: from [74.95.2.169] (helo=delta.rtfm.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ikm66-0007eO-F4
	for mmusic@ietf.org; Wed, 24 Oct 2007 15:40:58 -0400
Received: from delta.rtfm.com (localhost.rtfm.com [127.0.0.1])
	by delta.rtfm.com (Postfix) with ESMTP id B0D3333C28;
	Wed, 24 Oct 2007 12:36:32 -0700 (PDT)
Date: Wed, 24 Oct 2007 12:36:31 -0700
From: Eric Rescorla <ekr@networkresonance.com>
To: "Elwell, John" <john.elwell@siemens.com>
Subject: Re: [MMUSIC] Symmetry breaking for DTLS-SRTP
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D037D5E4@GBNTHT12009MSX.gb002.siemens.net>
	<0D5F89FAC29E2C41B98A6A762007F5D037D5E4@GBNTHT12009MSX.gb002.siemens.net>
References: <20071024165908.CDB1B33C28@delta.rtfm.com>
	<0D5F89FAC29E2C41B98A6A762007F5D037D5E4@GBNTHT12009MSX.gb002.siemens.net>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20071024193632.B0D3333C28@delta.rtfm.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
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>
Errors-To: mmusic-bounces@ietf.org

At Wed, 24 Oct 2007 20:16:37 +0100,
Elwell, John wrote:
> 
> Ekr,
> 
> I don't have a problem with the solution, but I am doubtful whether it
> is a problem we need to solve. The case illustrated is based on the
> assumption that offer and answer are symmetrical, in the sense that an
> offer can be reused as an answer (and vice versa). In this case the
> offer from A becomes an answer to B and vice versa. There are two
> extensions to SDP that I am aware of that break this, and therefore any
> controller that misuses SDP in this way will screw things up. One
> example is the key management extension when used to carry MIKEY,
> because a MIKEY request (which always goes in the offer) is very
> different in syntax and semantics from a MIKEY response (which always
> goes in the answer). Of course, this will not apply when using DTLS-SRTP
> as the means of key management. The second example is the SDP capability
> negotiation draft, which certainly will be applicable with DTLS-SRTP.
> 
> I am not aware of how the particular flow shown would arise. It is not
> documented in RFC 3725 (3PCC). It has similarities to flow II in RFC
> 3725, which the RFC does not recommend. The other 3PCC flows in RFC 3725
> do not mix up offers and answers in this way.
>
> I also questioned the need for the solution in ICE, but as it came
> virtually for free, it was not worth arguing about.

For the record, I'm certainly happy not to have to solve this problem,
and I don't understand the use cases well enough to understand whether
it is something we need to solve. I'm basing this solely on the
discussion in ORD and a conversation with JDR. If the MMUSIC WG
feels this is a non-issue that's totally fine with me.


> If we continue this discussion, I would suggest we stick to the MMUSIC
> list rather than AVT.

Done.

-Ekr


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



From mmusic-bounces@ietf.org Wed Oct 24 15:44:53 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ikm9p-0005U7-1t; Wed, 24 Oct 2007 15:44:49 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1Ikm9n-0005S9-En
	for mmusic-confirm+ok@megatron.ietf.org; Wed, 24 Oct 2007 15:44:47 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ikm9n-0005S1-44
	for mmusic@ietf.org; Wed, 24 Oct 2007 15:44:47 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ikm9m-0007qA-Ny
	for mmusic@ietf.org; Wed, 24 Oct 2007 15:44:47 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 24 Oct 2007 12:44:46 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l9OJikdV012964; 
	Wed, 24 Oct 2007 12:44:46 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l9OJij75021514;
	Wed, 24 Oct 2007 19:44:45 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 24 Oct 2007 12:44:45 -0700
Received: from [10.21.121.136] ([10.21.121.136]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 24 Oct 2007 12:44:43 -0700
Message-ID: <471FA0A9.60709@cisco.com>
Date: Wed, 24 Oct 2007 15:44:41 -0400
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Thunderbird 1.5.0.13 (Windows/20070809)
MIME-Version: 1.0
To: "Robert R. Gilman" <rrg@avaya.com>
Subject: Re: [MMUSIC] comments on
	draft-ietf-mmusic-sdp-capability-negotiation-06.txt
References: <471E71A4.70805@avaya.com>
In-Reply-To: <471E71A4.70805@avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Oct 2007 19:44:43.0453 (UTC)
	FILETIME=[530026D0:01C81676]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1328; t=1193255086;
	x=1194119086; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fandreas@cisco.com;
	z=From:=20Flemming=20Andreasen=20<fandreas@cisco.com>
	|Subject:=20Re=3A=20[MMUSIC]=20comments=20on=20draft-ietf-mmusic-sdp-capa
	bility-negotiation-06.txt |Sender:=20;
	bh=aYNqi8jK1JufXTcZFzvB1jyXhFfEh9Tbwl93BPgju3w=;
	b=fR25a9F9PKbM0EqU1/WTLBUl7bxCrV4xo0ySuQYyPiT2dNOfkP73RMQwSqytjTdPHxUF9a+T
	Fo69d0mc3NXQV24nS3GyDiPAmYgOO3OoAIcH8V+/2fSKXxBOoJwdxvbxBbLch5l6z1FG89o5Wv
	hhOEz8y8VduVlcJjw5uKsKEq0=;
Authentication-Results: sj-dkim-1; header.From=fandreas@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: "Even, Roni" <roni.even@polycom.co.il>, '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>
Errors-To: mmusic-bounces@ietf.org

Hi Bob

I agree we should have different attributes for other types of 
capabilities (such as bandwidth) and hence the "a=" part of the "acap" 
attribute is redundant as you noted.

I'm fine with removing it, unless anybody has any objections (e.g. due 
to an existing deployed implementation). If so please let me know.

-- Flemming

 

Robert R. Gilman wrote:
> Flemming-
> I have one minor suggestion for the acap attribute definition.  
> Insofar as
> the contents must be an attribute, why not omit the "a=" part?  Thus,
> for example, the line
>     a=acap:1 a=ptime:20
> would become
>     a=acap:1 ptime:20
>
> Magnus Westerlund used the acap attribute in an example like
>     a=acap:2 b=AS:128
> when he was exploring the use of cap-neg for AMR parameter negotiation,
> but I'd much prefer we define a different capability attribute - call
> it bcap - that can be used to specify a bandwidth parameter for a pcfg
> attribute.  Something like
>     a=acap:1 ptime:20
>     a=bcap:1 AS:128
>     a=pcfg:1 a=1 b=1 ....
> I believe we plan to define that in the upcoming version of the media-
> capabilities draft (along with several other attributes.)
> Comments?
> -Bob
> ----------------------------------------------------
> Bob Gilman       rrg@avaya.com      +1 303 538 3868
>


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



From mmusic-bounces@ietf.org Thu Oct 25 05:45:57 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IkzG4-00049t-0i; Thu, 25 Oct 2007 05:44:08 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IkzG3-00049o-6E
	for mmusic-confirm+ok@megatron.ietf.org; Thu, 25 Oct 2007 05:44:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IkzG2-00049g-Sj
	for mmusic@ietf.org; Thu, 25 Oct 2007 05:44:06 -0400
Received: from mxs2.siemens.at ([194.138.12.133])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IkzFw-0005vr-As
	for mmusic@ietf.org; Thu, 25 Oct 2007 05:44:06 -0400
Received: from vies1k7x.sie.siemens.at ([158.226.129.83])
	by mxs2.siemens.at  with ESMTP id l9P9hhEc022442;
	Thu, 25 Oct 2007 11:43:43 +0200
Received: from nets138a.ww300.siemens.net ([158.226.129.97])
	by vies1k7x.sie.siemens.at (8.12.11.20060308/8.12.1) with ESMTP id
	l9P9hXlM028278; Thu, 25 Oct 2007 11:43:40 +0200
Received: from nets13ja.ww300.siemens.net ([158.226.250.79]) by
	nets138a.ww300.siemens.net with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 25 Oct 2007 11:43:33 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] comments
	ondraft-ietf-mmusic-sdp-capability-negotiation-06.txt
Date: Thu, 25 Oct 2007 11:43:24 +0200
Message-ID: <EC7423A1DA34E340978D0CC83F9120F0038FE617@nets13ja.ww300.siemens.net>
In-Reply-To: <471FA0A9.60709@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] comments
	ondraft-ietf-mmusic-sdp-capability-negotiation-06.txt
Thread-Index: AcgWdqN1/sZOAXz9Q3i7h7JxnHciZAAZl5SQ
References: <471E71A4.70805@avaya.com> <471FA0A9.60709@cisco.com>
From: "Stach, Thomas" <thomas.stach@siemens.com>
To: "Flemming Andreasen" <fandreas@cisco.com>,
	"Robert R. Gilman" <rrg@avaya.com>
X-OriginalArrivalTime: 25 Oct 2007 09:43:33.0238 (UTC)
	FILETIME=[81E3E160:01C816EB]
X-purgate: clean
X-purgate: This mail is considered clean
X-purgate-type: clean
X-purgate-Ad: Checked for Spam by eleven - eXpurgate www.eXpurgate.net
X-purgate-ID: 149917::071025114343-46EB4BB0-04E7F7CE/0-0/0-15
X-purgate-size: 2296/999999
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: "Even, Roni" <roni.even@polycom.co.il>, 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>
Errors-To: mmusic-bounces@ietf.org

Flemming, Bob,

I don't object but I remember some early discussion where it was claimed
that the a=3Dacap: attribute should carry the whole capability attribute
including the "a=3D".=20
I think the reason was to facilitate the construction of the SDP for
potential configurations.
If that really matters much is questionable.

Regards
Thomas


> -----Original Message-----
> From: Flemming Andreasen [mailto:fandreas@cisco.com]=20
> Sent: Wednesday, October 24, 2007 9:45 PM
> To: Robert R. Gilman
> Cc: Even, Roni; 'mmusic'
> Subject: Re: [MMUSIC] comments=20
> ondraft-ietf-mmusic-sdp-capability-negotiation-06.txt
>=20
> Hi Bob
>=20
> I agree we should have different attributes for other types of=20
> capabilities (such as bandwidth) and hence the "a=3D" part of=20
> the "acap"=20
> attribute is redundant as you noted.
>=20
> I'm fine with removing it, unless anybody has any objections=20
> (e.g. due=20
> to an existing deployed implementation). If so please let me know.
>=20
> -- Flemming
>=20
> =20
>=20
> Robert R. Gilman wrote:
> > Flemming-
> > I have one minor suggestion for the acap attribute definition. =20
> > Insofar as
> > the contents must be an attribute, why not omit the "a=3D"=20
> part?  Thus,
> > for example, the line
> >     a=3Dacap:1 a=3Dptime:20
> > would become
> >     a=3Dacap:1 ptime:20
> >
> > Magnus Westerlund used the acap attribute in an example like
> >     a=3Dacap:2 b=3DAS:128
> > when he was exploring the use of cap-neg for AMR parameter=20
> negotiation,
> > but I'd much prefer we define a different capability=20
> attribute - call
> > it bcap - that can be used to specify a bandwidth parameter=20
> for a pcfg
> > attribute.  Something like
> >     a=3Dacap:1 ptime:20
> >     a=3Dbcap:1 AS:128
> >     a=3Dpcfg:1 a=3D1 b=3D1 ....
> > I believe we plan to define that in the upcoming version of=20
> the media-
> > capabilities draft (along with several other attributes.)
> > Comments?
> > -Bob
> > ----------------------------------------------------
> > Bob Gilman       rrg@avaya.com      +1 303 538 3868
> >
>=20
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
>=20


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



From mmusic-bounces@ietf.org Thu Oct 25 10:46:38 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Il3xF-0001jS-Ut; Thu, 25 Oct 2007 10:45:01 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1Il3xB-0001Ux-3D
	for mmusic-confirm+ok@megatron.ietf.org; Thu, 25 Oct 2007 10:44:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Il3xA-0001Up-Pv
	for mmusic@ietf.org; Thu, 25 Oct 2007 10:44:56 -0400
Received: from vkimail.vidiator.com ([211.189.53.2]
	helo=kor1corpmail01.mediator.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Il3x3-00064t-Lo
	for mmusic@ietf.org; Thu, 25 Oct 2007 10:44:56 -0400
Subject: RE: [MMUSIC] RTSP: Speed header
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 25 Oct 2007 23:44:32 +0900
Message-ID: <FE6A9D3F2979884280CE0F5F5185517B5ACBB0@kor1corpmail01.mediator.com>
In-Reply-To: <471DE980.8040207@ericsson.com>
References: <462387E3.20600@ericsson.com> <471DE980.8040207@ericsson.com>
From: "Jaehwan Kim" <jaehwan@vidiator.com>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f
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>
Errors-To: mmusic-bounces@ietf.org

Hi Magnus,
To me, scale is also not easy because decoder controls speed of motion
or music in general, not by signaling protocol. What's more, some
decoders do not see RTP timestamp; they use bitstream's one; and
signaling layer should have the same timestamp as bitstream does. Or do
they violate RTP and RTSP?

Why don't we just remove this from base specification and make a
separate one? As you said, in 3GPP, we discuss FastStart, rate
adaptation, and client buffer. I don't mean we need to wait; just we
need to discuss with them and make a good universal solution together.
But if we add this to base, it might be much more difficult.

Cheers,
Jaehwan


-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]=20
Sent: Tuesday, October 23, 2007 1:31 PM
To: Magnus Westerlund
Cc: mmusic (E-mail)
Subject: Re: [MMUSIC] RTSP: Speed header

Hi,

See inline:

Magnus Westerlund skrev:
> Hi,
>=20
> I while back received an email with some questions on how the Speed
> header works in RTSP. There where also the issue how it interacts with
> the Scale header and with bandwidth adaptation and buffer management.
>=20
> Lets do a recap of what the different mechanisms do.
>=20
> Scale: Changes the rate at which media is presented to the user. So
> Scale=3D0.5 would mean slow motion, while Scale=3D5 would be fast =
forward
in
> the stream.
>=20
> Speed: Changes the media delivery rate. Speed=3D2 would mean that for
each
> second a client would receive media that takes it 2 seconds to play
back
> to the user. It would also mean that using RTP with a 90kHz timestamp
> clock the RTP streams timestamp values would increase with 180k ticks
> per second.
>=20
> Bit-rate adaptation: A way of ensuring that the media traffic does not
> use more bandwidth then what is available. Which means that the server
> would need to change the media bit-rate sent if there isn't enough
> available for the current media stream. This could be done in a number
> of ways but most commonly are done by bit-stream switching. Going from
a
> stored/delivered media stream in one quality to another lower quality
> that requires less bit-rate.
>=20
> Buffer Management: An attempt to keep the clients buffer in a healthy
> state, aiming at keeping a certain amount of media time present in
> buffer to safeguard against temporary or longer term changes of
bit-rate
> capacity available to the streaming session. Thus giving the server
time
> to react to the change before an buffer-underrun situation occurs. At
> the same time safe-guard against overflowing buffers. This is for
> example done in 3GPP Packet-based Streaming Service (26.234 Rel6)
where
> additional feedback and configuration information is provided for the
> buffer status. Thus allowing a server to change media transmission
rate
> on the fly. Which is equivalent to a client using Speed. However it
also
> needs to be able to perform bit-rate adaptation so that one can lower
> the quality but increase the speed to refill the buffer.
>=20
> The interactions between the different behaviors are interesting but
can
> become quite complex. For example the total bit-rate is speed x normal
> bit-rate. It might also be influenced by the Scale used as fast
> forwarding could be accomplished by simple turning up the frame-rate
for
> video and rewriting the timestamps compared to scale 1. Slow motion
> could also mean that the bit-rate gets lower. However if trans-coding
is
> done to handle Scale then bit-rate may not change at all. If there are
a
> limited amount of bit-rate this means that bit-rate adaptation needs
to
> step in and do what it can to keep bit-rate within limitations. If
that
> can only operate on the media stream or can also contradict speed or
> influence how scale is handled is quite undefined.
>=20
> I do have a few question due to this:
>=20
> 1. Are people implementing Speed?
>=20
> 2. If you are using Speed, how are you doing that, as I have described
> or otherwise?
>=20
> 3. Should we remove speed from base specification?
>=20
> 4. If not, what do you think needs to be clarified and do you have
text
> proposal?

Time to bring up this topic again and get some closure on it. I have
reviewed what people have written and have a number of comments and
considerations around this.

First of all is the general congestion control. To me Speed header shall
not be used for congesting controlling the flow from the server to the
client. To me the usage that seems okay are:

1. In combination with scale to tell how it should fulfill the request.
Here I think the two main cases are Scale=3Dx Speed=3Dx for x!=3D1 and =
Scale=3Dx
Speed=3D1. In other words, realize a playout speedup by increasing the
delivery rate to the client or if the server should rescale the content
to maintain the bit-rate.

2. To indicate faster than normal delivery to fill up the receiver
buffers, i.e. scale=3D1 speed=3Dx where x>1. Then when buffer reached =
the
desired level the client requests that speed goes back to 1.0.

Both these has interactions with the actual congestion control used. If
the available bit-rate is limited in both these case the content needs
to be adapted to fulfill.

Are these interesting enough that we actually should write them up so
that it is clear what they mean? The alternative is to remove speed for
now and have the behaviors being undefined in these cases.

Cheers

Magnus Westerlund

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


_______________________________________________
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 Oct 25 12:06:37 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Il5Cr-0002de-Pd; Thu, 25 Oct 2007 12:05:13 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1Il5Cq-0002dW-Hy
	for mmusic-confirm+ok@megatron.ietf.org; Thu, 25 Oct 2007 12:05:12 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Il5Cq-0002dO-5g
	for mmusic@ietf.org; Thu, 25 Oct 2007 12:05:12 -0400
Received: from audl952.usa.alcatel.com ([143.209.238.159])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Il5Cp-00044p-4X
	for mmusic@ietf.org; Thu, 25 Oct 2007 12:05:12 -0400
Received: from srsdmail01.PVNS.COM (mail.pvnetsolutions.com [128.251.100.16])
	by audl952.usa.alcatel.com (ALCANET) with ESMTP id l9PG58RH002028;
	Thu, 25 Oct 2007 11:05:09 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] RTSP: Speed header
Date: Thu, 25 Oct 2007 09:05:15 -0700
Message-ID: <758B5A159B385447B4F950DE72D7D7AD01AAC34F@srsdmail01.PVNS.COM>
In-Reply-To: <FE6A9D3F2979884280CE0F5F5185517B5ACBB0@kor1corpmail01.mediator.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] RTSP: Speed header
Thread-Index: AcgXFrMFL0RLJmSpTg2LFOrplEyz5AAAOBuA
References: <462387E3.20600@ericsson.com> <471DE980.8040207@ericsson.com>
	<FE6A9D3F2979884280CE0F5F5185517B5ACBB0@kor1corpmail01.mediator.com>
From: "Mike Severa" <severa@pvnetsolutions.com>
To: "Jaehwan Kim" <jaehwan@vidiator.com>,
	"Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-Scanned-By: MIMEDefang 2.51 on 143.209.238.34
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e367d58950869b6582535ddf5a673488
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>
Errors-To: mmusic-bounces@ietf.org

Hi Jaehwan,=20

I agree scale is not easy. And I'm not sure whether its germaine to your
argument, but I don't see how a streaming client could behave properly
without the RTP timestamp. It is surely required for A/V sync, and there
are a number of codecs that don't even have a "built-in" bitstream-level
timestamp, or others for which timestamps only have a kind of
"time-local" meaning. In addition, I do know that there are a number of
players that even ignore bitstream timestamps when they exist in favor
of RTP ones.

That said, I believe the behavior surrounding 3GPP faststart, rate
adaptation, buffer mgmt, etc, have more similarity with the speed header
than with the scale header. I believe the scale header was intended to
provide support for something that these other things being discussed in
3GPP currently do not, at least not directly.=20
Even so, while one could argue the speed header might be more similar, I
echo Magnus' opinion below in that I also don't think the intent of that
header was to provide the client a congestion control mechanism, but
that doesn't mean it would not be useful in the context of services that
make use of fast-start/switching, buffer mgmt, etc, even rate adaptation
in certain contexts. It should also be clear that regardless of how much
a 3GPP streamer server might be able to do as defined by those specs,
these headers allow *client control* over aspects of these behaviors for
which I don't believe there is any currently defined alternative
allowing a client this kind of control.=20

It has been my experience that in a fast switching, 3GPP streaming-based
environment, the availability of something like a speed header is a
requirement (it is my opinion that current 3GPP docs do not even address
this issue in their concept of "fast switching"). That said, we have not
implemented the speed header per se, but only because it was not yet
well enough defined, or widely enough implemented in our view. But the
server-side behavior is there, we simply use other means for controlling
it.

I also believe that the scale header can play a necessary part in a fast
switching environment as well (Magnus mentions some below), though I
believe it also has other uses.

Personally, I would love to see more explanation of and use cases for
these headers before a decision is made as to whether either can or
should be done away with. However, I admit that this isnt a trivial task
and perhaps that makes it unreasonable..?=20

Thanks for bringing this up Magnus, I think it's an important topic.

Mike

-----Original Message-----
From: Jaehwan Kim [mailto:jaehwan@vidiator.com]=20
Sent: Thursday, October 25, 2007 7:45 AM
To: Magnus Westerlund
Cc: mmusic (E-mail)
Subject: RE: [MMUSIC] RTSP: Speed header

Hi Magnus,
To me, scale is also not easy because decoder controls speed of motion
or music in general, not by signaling protocol. What's more, some
decoders do not see RTP timestamp; they use bitstream's one; and
signaling layer should have the same timestamp as bitstream does. Or do
they violate RTP and RTSP?

Why don't we just remove this from base specification and make a
separate one? As you said, in 3GPP, we discuss FastStart, rate
adaptation, and client buffer. I don't mean we need to wait; just we
need to discuss with them and make a good universal solution together.
But if we add this to base, it might be much more difficult.

Cheers,
Jaehwan


-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
Sent: Tuesday, October 23, 2007 1:31 PM
To: Magnus Westerlund
Cc: mmusic (E-mail)
Subject: Re: [MMUSIC] RTSP: Speed header

Hi,

See inline:

Magnus Westerlund skrev:
> Hi,
>=20
> I while back received an email with some questions on how the Speed=20
> header works in RTSP. There where also the issue how it interacts with

> the Scale header and with bandwidth adaptation and buffer management.
>=20
> Lets do a recap of what the different mechanisms do.
>=20
> Scale: Changes the rate at which media is presented to the user. So
> Scale=3D0.5 would mean slow motion, while Scale=3D5 would be fast =
forward
in
> the stream.
>=20
> Speed: Changes the media delivery rate. Speed=3D2 would mean that for
each
> second a client would receive media that takes it 2 seconds to play
back
> to the user. It would also mean that using RTP with a 90kHz timestamp=20
> clock the RTP streams timestamp values would increase with 180k ticks=20
> per second.
>=20
> Bit-rate adaptation: A way of ensuring that the media traffic does not

> use more bandwidth then what is available. Which means that the server

> would need to change the media bit-rate sent if there isn't enough=20
> available for the current media stream. This could be done in a number

> of ways but most commonly are done by bit-stream switching. Going from
a
> stored/delivered media stream in one quality to another lower quality=20
> that requires less bit-rate.
>=20
> Buffer Management: An attempt to keep the clients buffer in a healthy=20
> state, aiming at keeping a certain amount of media time present in=20
> buffer to safeguard against temporary or longer term changes of
bit-rate
> capacity available to the streaming session. Thus giving the server
time
> to react to the change before an buffer-underrun situation occurs. At=20
> the same time safe-guard against overflowing buffers. This is for=20
> example done in 3GPP Packet-based Streaming Service (26.234 Rel6)
where
> additional feedback and configuration information is provided for the=20
> buffer status. Thus allowing a server to change media transmission
rate
> on the fly. Which is equivalent to a client using Speed. However it
also
> needs to be able to perform bit-rate adaptation so that one can lower=20
> the quality but increase the speed to refill the buffer.
>=20
> The interactions between the different behaviors are interesting but
can
> become quite complex. For example the total bit-rate is speed x normal

> bit-rate. It might also be influenced by the Scale used as fast=20
> forwarding could be accomplished by simple turning up the frame-rate
for
> video and rewriting the timestamps compared to scale 1. Slow motion=20
> could also mean that the bit-rate gets lower. However if trans-coding
is
> done to handle Scale then bit-rate may not change at all. If there are
a
> limited amount of bit-rate this means that bit-rate adaptation needs
to
> step in and do what it can to keep bit-rate within limitations. If
that
> can only operate on the media stream or can also contradict speed or=20
> influence how scale is handled is quite undefined.
>=20
> I do have a few question due to this:
>=20
> 1. Are people implementing Speed?
>=20
> 2. If you are using Speed, how are you doing that, as I have described

> or otherwise?
>=20
> 3. Should we remove speed from base specification?
>=20
> 4. If not, what do you think needs to be clarified and do you have
text
> proposal?

Time to bring up this topic again and get some closure on it. I have
reviewed what people have written and have a number of comments and
considerations around this.

First of all is the general congestion control. To me Speed header shall
not be used for congesting controlling the flow from the server to the
client. To me the usage that seems okay are:

1. In combination with scale to tell how it should fulfill the request.
Here I think the two main cases are Scale=3Dx Speed=3Dx for x!=3D1 and =
Scale=3Dx
Speed=3D1. In other words, realize a playout speedup by increasing the
delivery rate to the client or if the server should rescale the content
to maintain the bit-rate.

2. To indicate faster than normal delivery to fill up the receiver
buffers, i.e. scale=3D1 speed=3Dx where x>1. Then when buffer reached =
the
desired level the client requests that speed goes back to 1.0.

Both these has interactions with the actual congestion control used. If
the available bit-rate is limited in both these case the content needs
to be adapted to fulfill.

Are these interesting enough that we actually should write them up so
that it is clear what they mean? The alternative is to remove speed for
now and have the behaviors being undefined in these cases.

Cheers

Magnus Westerlund

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


_______________________________________________
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 Oct 26 06:46:29 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IlMgY-000207-Kx; Fri, 26 Oct 2007 06:45:02 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IlMgX-0001yd-LE
	for mmusic-confirm+ok@megatron.ietf.org; Fri, 26 Oct 2007 06:45:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IlMgX-0001sM-BR
	for mmusic@ietf.org; Fri, 26 Oct 2007 06:45:01 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IlMgN-0007mJ-W5
	for mmusic@ietf.org; Fri, 26 Oct 2007 06:44:58 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	66EF020A9F
	for <mmusic@ietf.org>; Fri, 26 Oct 2007 12:44:42 +0200 (CEST)
X-AuditID: c1b4fb3c-afe7ebb0000007e1-af-4721c51a2048
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	4B7D0206FD
	for <mmusic@ietf.org>; Fri, 26 Oct 2007 12:44:42 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 26 Oct 2007 12:44:42 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 26 Oct 2007 12:44:41 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF02BC97B3@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: ICE: Clarification question when full ICE communciate with ICE
	lite and chooses host candidate
Thread-Index: AcgXvTa/HP8Nqi5rQmy/eSLM/Y8tRw==
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: <mmusic@ietf.org>
X-OriginalArrivalTime: 26 Oct 2007 10:44:42.0225 (UTC)
	FILETIME=[37309E10:01C817BD]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -1.0 (-)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Subject: [MMUSIC] ICE: Clarification question when full ICE communciate with
	ICE lite and chooses host candidate
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="===============1863206130=="
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1863206130==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C817BD.37105A69"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C817BD.37105A69
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Hi,

Assume the following scenario:

- User A is located behind a NAT, and implements full ICE.

- User A collects candidates, and send an INVITE

- The call is received by an MGCF, implementing ICE lite.

- User A starts doing connectivity checks, which the MGCF reply to
(being ICE lite, the MGCF does not generate checks itself)

- User A detects that the HOST_CANDIDATE checks work, so it sends an
UPDATE and tells the MGCF that the HOST_CANDIDATE will be used. The
Local Address information will be in the c/m line.


Now, the MGCF will start sending media towards the Local Address. But,
since User A, and the Local Address, is behind the NAT, the media will
not reach User A.


I guess this could be solved if User A in the UPDATE includes the Server
Reflexive Address it received in the STUN responses for the host
candidate, instead of the Local Address. But, I can't find any text in
the ICE spec indicating that.


Or, have I missunderstood something?


Regards,

Christer







------_=_NextPart_001_01C817BD.37105A69
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>ICE: Clarification question when full ICE communciate with ICE =
lite and chooses host candidate</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hi,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Assume the following scenario:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">- User A is located behind a NAT, and =
implements full ICE.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">- User A collects candidates, and send =
an INVITE</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">- The call is received by an MGCF, =
implementing ICE lite.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">- User A starts doing connectivity =
checks, which the MGCF reply to (being ICE lite, the MGCF does not =
generate checks itself)</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">- User A detects that the =
HOST_CANDIDATE checks work, so it sends an UPDATE and tells the MGCF =
that the HOST_CANDIDATE will be used. The Local Address information will =
be in the c/m line.</FONT></P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Now, the MGCF will start sending media =
towards the Local Address. But, since User A, and the Local Address, is =
behind the NAT, the media will not reach User A.</FONT></P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">I guess this could be solved if User A =
in the UPDATE includes the Server Reflexive Address it received in the =
STUN responses for the host candidate, instead of the Local Address. =
But, I can't find any text in the ICE spec indicating that.</FONT></P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Or, have I missunderstood =
something?</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Regards,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Christer</FONT>
</P>
<BR>
<BR>
<BR>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C817BD.37105A69--



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

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

--===============1863206130==--





From mmusic-bounces@ietf.org Fri Oct 26 06:48:06 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IlMj9-0005Rb-WF; Fri, 26 Oct 2007 06:47:44 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IlMj8-0005RW-Vs
	for mmusic-confirm+ok@megatron.ietf.org; Fri, 26 Oct 2007 06:47:42 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IlMj8-0005RN-L3
	for mmusic@ietf.org; Fri, 26 Oct 2007 06:47:42 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IlMj8-00065Z-3J
	for mmusic@ietf.org; Fri, 26 Oct 2007 06:47:42 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	52C1B2124E
	for <mmusic@ietf.org>; Fri, 26 Oct 2007 12:47:41 +0200 (CEST)
X-AuditID: c1b4fb3e-b0034bb0000007e1-a0-4721c5cd2cfa
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	3F81C207AD
	for <mmusic@ietf.org>; Fri, 26 Oct 2007 12:47:41 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 26 Oct 2007 12:47:41 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 26 Oct 2007 12:47:40 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF02BC97CB@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: ICE-TCP: Why isn't passive enough for ICE lite
Thread-Index: AcgXvaFml8P9k95ORiKjgWEXthJnzg==
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: <mmusic@ietf.org>
X-OriginalArrivalTime: 26 Oct 2007 10:47:41.0144 (UTC)
	FILETIME=[A1D57D80:01C817BD]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Subject: [MMUSIC] ICE-TCP: Why isn't passive enough for ICE lite
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="===============1206710371=="
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1206710371==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C817BD.A1ABF408"

This is a multi-part message in MIME format.

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


Hi,

The ICE-TCP draft says that all entities supporting ICE for TCP must be
full ICE compliant.

My question is: why can't an ICE lite entity (ie an entity which knows
it's not located behind a NAT) simply send a single TCP passive
candidate, and tell the other party (possibly located behind a NAT) to
establish that TCP connection. That should work with all NATs, shouldn't
it?

Regards,

Christer

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>ICE-TCP: Why isn't passive enough for ICE lite</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hi,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The ICE-TCP draft says that all =
entities supporting ICE for TCP must be full ICE compliant.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">My question is: why can't an ICE lite =
entity (ie an entity which knows it's not located behind a NAT) simply =
send a single TCP passive candidate, and tell the other party (possibly =
located behind a NAT) to establish that TCP connection. That should work =
with all NATs, shouldn't it?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Regards,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Christer</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C817BD.A1ABF408--



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

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

--===============1206710371==--





From mmusic-bounces@ietf.org Fri Oct 26 09:23:43 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IlP8V-0004Sy-Pu; Fri, 26 Oct 2007 09:22:03 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IlP8S-0004RA-J5
	for mmusic-confirm+ok@megatron.ietf.org; Fri, 26 Oct 2007 09:22:00 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IlP8S-0004R2-7k
	for mmusic@ietf.org; Fri, 26 Oct 2007 09:22:00 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IlP8R-0001X4-Iz
	for mmusic@ietf.org; Fri, 26 Oct 2007 09:22:00 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	0E9D32131E; Fri, 26 Oct 2007 15:21:59 +0200 (CEST)
X-AuditID: c1b4fb3e-af833bb0000007e1-a1-4721e9f70e03
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	0288C21319; Fri, 26 Oct 2007 15:21:59 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 26 Oct 2007 15:21:58 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] ICE with media streams without candidates
Date: Fri, 26 Oct 2007 15:21:57 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF02BFD73A@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF02ABE439@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] ICE with media streams without candidates
Thread-Index: AcgVciJ+n1HcNJIDSHaexxX0QwOrNwAAyyuAAJdiBMA=
References: <CA9998CD4A020D418654FCDEF4E707DF02A5D6FC@esealmw113.eemea.ericsson.se><200710221528.41180.remi.denis-courmont@nokia.com><CA9998CD4A020D418654FCDEF4E707DF02A8B9C8@esealmw113.eemea.ericsson.se><200710231528.52224.remi.denis-courmont@nokia.com>
	<CA9998CD4A020D418654FCDEF4E707DF02ABE439@esealmw113.eemea.ericsson.se>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: =?iso-8859-1?Q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 26 Oct 2007 13:21:58.0928 (UTC)
	FILETIME=[2FE73900:01C817D3]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
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>
Errors-To: mmusic-bounces@ietf.org


Hi,=20

>>>Assume A calls B, and includes SDP with the ICE candidate attributes=20
>>>etc for each media stream.
>>>In the middle there is a B2BUA application server, which wants to add =

>>>a stream towards B, so it modifies the SDP by adding an extra m=3D =
line.
>>>The application server, however, does not support ICE, so it does not =

>>>include any candidate attributes.
>>=20
>>We can probably agree that if there is something that modifies this =
SDP=20
>>even though it does not terminate the SIP session, anything can =
happen.=20
>>And probably nobody wants to start a SBC flame war here ;)
>>=20
>>As a developper, I would rather it had been per-media, or better yet, =
a=20
>>per-component process, because it would have been much simpler to=20
>>implement and integrate. There are however several valid reasons why=20
>>ICE is a SIP per-session process, as far as ICE is used with SIP.
>>
>>I can think of plenty of loopholes if one media has ICE, but not =
another one.
>>For instance, how would the UA know when to start sending media? But=20
>>most importantly, the decision to abort ICE when some inconsistency is =

>>detected is all about maximizing backward compatibility with existing=20
>>setups. If there is some middlebox modifying the SDP in a way that=20
>>breaks ICE, it is safest to assume that ICE might not work. As such it =

>>should not be used at all. ICE was simply not meant to operate in such =

>>scenarios.
>=20
>I am not arguing against the mismatch rules as such, I am=20
>just wondering if there are technical reasons why they can't=20
>be done per media.
>=20
>>Also, in most scenarios where the SDP media information is modified, =
it=20
>>is most probably that all medias will be modified in a way that would=20
>>make them ineligible for ICE: robably the original medias (those NOT =
coming from the application=20
>>server) would go through some kind of media proxying device anyway.=20
>>Right?
>=20
>Not necessarily. In my examples the media NOT=20
>generated/transcoded by the application server does not need=20
>to go through any media proxying device.

Also, chapter 9.1.1.3 allows ICE-per-stream when a new stream is added, =
so I see no reason why ICE-per-stream (ICEstream :) can't be used also =
in the beginning of the session.

Regards,

Christer


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



From mmusic-bounces@ietf.org Fri Oct 26 12:28:36 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IlS2B-0001WR-7l; Fri, 26 Oct 2007 12:27:43 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IlS26-0001UV-Al
	for mmusic-confirm+ok@megatron.ietf.org; Fri, 26 Oct 2007 12:27:38 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IlS25-0001Jm-MU
	for mmusic@ietf.org; Fri, 26 Oct 2007 12:27:37 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IlS1z-0007wa-3X
	for mmusic@ietf.org; Fri, 26 Oct 2007 12:27:32 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	71E202020E
	for <mmusic@ietf.org>; Fri, 26 Oct 2007 18:27:30 +0200 (CEST)
X-AuditID: c1b4fb3e-b1036bb0000007e1-55-472215729603
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	4FC34203A8
	for <mmusic@ietf.org>; Fri, 26 Oct 2007 18:27:30 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 26 Oct 2007 18:27:29 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 26 Oct 2007 18:27:29 +0200
Message-ID: <47221571.3070003@ericsson.com>
Date: Fri, 26 Oct 2007 18:27:29 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "mmusic (E-mail)" <mmusic@ietf.org>
X-Enigmail-Version: 0.95.4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Oct 2007 16:27:29.0650 (UTC)
	FILETIME=[1A549D20:01C817ED]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4bb0e9e1ca9d18125bc841b2d8d77e24
Subject: [MMUSIC] RTSP 2.0: Allowing pipelining for the session creation
	phase
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>
Errors-To: mmusic-bounces@ietf.org

3GPP already has defined a way to allow for pipelining at session
creation. I think the method works fine and proposes that we actually
adopt it for RTSP 2.0. Because of this I have written it up for the
draft. Here is the major additions in text that I am proposing.

I think the major difference of this definition compared to what is in
section 5.5.3 of 3GPP TS 26.234
http://www.3gpp.org/ftp/Specs/archive/26_series/26.234/26234-740.zip
is that I changed to ABNF to allow white spaces around the ":" the same
way as all the other headers in this spec. This allow the 3GPP defined
header to be valid within our spec, but that something following the
IETF spec may be invalid according the 3GPP spec.

So please review and comment


5.  General Header Fields

   See [H4.5], except that the Pragma, Trailer, Transfer-Encoding,
   Upgrade, and Warning headers are not defined.  RTSP further defines
   the CSeq, Pipelined-Requests, Proxy-Supported and Timestamp headers.
   The general headers are listed in Table 1:

                +--------------------+--------------------+
                | Header Name        | Defined in Section |
                +--------------------+--------------------+
                | Cache-Control      | Section 15.10      |
                |                    |                    |
                | Connection         | Section 15.11      |
                |                    |                    |
                | CSeq               | Section 15.19      |
                |                    |                    |
                | Date               | Section 15.20      |
                |                    |                    |
                | Pipelined-Requests | Section 15.29      |
                |                    |                    |
                | Proxy-Supported    | Section 15.33      |
                |                    |                    |
                | Supported          | Section 15.44      |
                |                    |                    |
                | Timestamp          | Section 15.45      |
                |                    |                    |
                | Via                | Section 15.50      |
                +--------------------+--------------------+

                 Table 1: The general headers used in RTSP



11.  Pipelining Support

   Pipelining is a general method to improve performance of request
   response protocols by allowing the requesting entity to have more
   than one request outstanding and send them over the same persistent
   connection.  For RTSP where the relative order of requests will
   matter it is important to maintain the order of the requests.
   Because of this the the responding entity SHALL process the incoming
   requests in their sending order.  The sending order can be determined
   by the CSeq header and its sequence number.  For TCP the delivery
   order will be the same as the sending order.  The processing of the
   request SHALL also have been finished before processing the next
   request from the same entity.  The responses MUST be sent in the
   order the requests was processed.

   RTSP 2.0 has extended support for pipelining compared to RTSP 1.0.
   The major improvement is to allow all requests to setup and initiate
   media playback to be pipelined after each other.  This is
   accomplished by the utilization of the Pipelined-Requests header (See
   Section 15.29).  This header allows a client to request that two or
   more requests is to be processed in the same RTSP session context
   which the first request creates.  In other words a client can request
   that two or more media streams are set-up and then played without
   needing to wait for a single response.  This speeds up the initial
   startup time for an RTSP session with at least one RTT.

   When pipelining requests care must be taken.  If a pipelined request
   builds on the succesful completion of one or more prior requests the
   requestor must verify that all requests was executed as expected.  O
   common example will be two SETUP requests and a PLAY request.  In
   case one of the SETUP fails unexpectedly, the PLAY request can still
   be succesfully executed.  However, not as expected by the requesting
   client as only a single media instead of two will be played.  In this
   case the client can send a PAUSE request, correct the failing SETUP
   request and then request it to be played.




     Table 9: Overview of RTSP header fields (A-L) related to methods
           DESCRIBE, OPTIONS, SETUP, PLAY, PAUSE, and TEARDOWN.

   +------------+-------+------+----+-----+-------+------+-------+-----+
   | Header     | Where | Prox | DE | OPT | SETUP | PLAY | PAUSE | TRD |
   |            |       | y    | S  |     |       |      |       |     |
   +------------+-------+------+----+-----+-------+------+-------+-----+
   | Pipelined- |       | amdr | -  | o   | o     | o    | o     | o   |
   | Requests   |       |      |    |     |       |      |       |     |
   |            |       |      |    |     |       |      |       |     |

     Table 10: Overview of RTSP header fields (P-W) related to methods
           DESCRIBE, OPTIONS, SETUP, PLAY, PAUSE, and TEARDOWN.

      +------------------------+---------+-------+-----+-----+-----+
      | Header                 | Where   | Proxy | GPR | SPR | RDR |
      +------------------------+---------+-------+-----+-----+-----+

      | Pipelined-Requests     |         | amdr  | o   | o   | o   |



15.29.  Pipelined-Requests

   The Pipelined-Requests general header is used to indicate that a
   request is to be executed in the context created by previous
   requests.  The primary usage of this header is to allow pipelining of
   SETUP requests so that any additional SETUP request after the first
   one doesn't need to wait for the session ID to be sent back to the
   requesting entity.  The header contains a unique identifier that is
   scoped by thepersistent connection used to send the requests.

   Upon receiving a request with the Pipelined-Requests the responding
   entity SHALL look up if there exist a binding between this Pipelined-
   Requests identifier for the current persistent connection and an RTSP
   session ID.  If that exist then the received request is processed the
   same way as if it did contain the Session header with the looked up
   session ID.  If there doesn't exist a mapping and no Session header
   is included in the request, the responding entity SHALL create a
   binding upon the succesful completion of a session creating request,
   i.e.  SETUP.  If the request failed to create an RTSP session no
   binding SHALL be created.  In case the request contains both a
   Session header and the Pipelined-Requests header the Pipelined-
   Requests SHALL be ignored.

   Note: Based on the above definition at least the first request
   containing a new unique Pipelined-Requests will be required to be a
   SETUP request (unless the protocol is extended with new methods of
   creating a session).  After that first one, additional SETUP requests
   or request of any type using the RTSP session context may includ the
   Pipelined-Requests header.

   For all responses to request that contained the Pipelined-Requests,
   the Session header and the Pipelined-Requests SHALL both be included,
   assuming that it is allowed for that response and that the binding
   between the header values exist.  Pipelined-Requests SHOULD NOT be
   used in requests after that the client has received the RTSP Session
   ID.  This as using the real session ID allows the request to be used
   also in cases the persistent connection has been terminated and a new
   connection is needed.

   It is the sender of the request that is responsible for using a
   previously unused identifier within this transport connection scope
   when a new RTSP session is to be cretated with this method.  A server
   side binding SHALL be deleted upon the termination of the related
   RTSP session.  Note: Although this definition would allow for reusing
   previously used pipelining identifiers, this is NOT RECOMMENDED to
   allow for better error handling and logging.

   RTSP Proxies may need to translate Pipelined-Requests identifier
   values from incoming request to outgoing to allow for aggregation of
   requests onto a persistent connection.

18.2.  Media on Demand using Pipelining

   This example is basically the example above ( Section 18.1) but now
   utilizing pipelining to speed up the setup.  Into requiring only two
   round trip times until media starts flowing.  First getting the
   session description to determine what media resources need to be
   setup.  In the second one send the necessary SETUP requests and the
   PLAY request to initiate media delivery.

   Client C requests a presentation from media server M. The movie is
   stored in a container file.  The client has obtained an RTSP URI to
   the container file.

   C->M: DESCRIBE rtsp://example.com/twister.3gp RTSP/2.0
         CSeq: 1
         User-Agent: PhonyClient/1.2

   M->C: RTSP/2.0 200 OK



Schulzrinne, et al.      Expires April 28, 2008               [Page 124]

Internet-Draft   Real Time Streaming Protocol 2.0 (RTSP)    October 2007


         CSeq: 1
         Server: PhonyServer/1.0
         Date: 23 Jan 1997 15:35:06 GMT
         Content-Type: application/sdp
         Content-Length: 257
         Content-Base: rtsp://example.com/twister.3gp/
         Expires: 24 Jan 1997 15:35:06 GMT

         v=0
         o=- 2890844256 2890842807 IN IP4 192.0.2.5
         s=RTSP Session
         i=An Example of RTSP Session Usage
         e=adm@example.com
         a=control: *
         a=range: npt=0-0:10:34.10
         t=0 0
         m=audio 0 RTP/AVP 0
         a=control: trackID=1
         m=video 0 RTP/AVP 26
         a=control: trackID=4

   C->M: SETUP rtsp://example.com/twister.3gp/trackID=1 RTSP/2.0
         CSeq: 2
         User-Agent: PhonyClient/1.2
         Require: play.basic
         Transport: RTP/AVP;unicast;dest_addr=":8000"/":8001"
         Accept-Ranges: NPT, SMPTE, UTC
         Pipelined-Requests: 7654

   C->M: SETUP rtsp://example.com/twister.3gp/trackID=4 RTSP/2.0
         CSeq: 3
         User-Agent: PhonyClient/1.2
         Require: play.basic
         Transport: RTP/AVP;unicast;dest_addr=":8002"/":8003"
         Accept-Ranges: NPT, SMPTE, UTC
         Pipelined-Requests: 7654

   C->M: PLAY rtsp://example.com/twister.3gp/ RTSP/2.0
         CSeq: 4
         User-Agent: PhonyClient/1.2
         Range: npt=0-10, npt=30-
         Session: 12345678
         Pipelined-Requests: 7654

   M->C: RTSP/2.0 200 OK
         CSeq: 2
         Server: PhonyServer/1.0
         Transport: RTP/AVP;unicast;dest_addr=":8000"/":8001;



Schulzrinne, et al.      Expires April 28, 2008               [Page 125]

Internet-Draft   Real Time Streaming Protocol 2.0 (RTSP)    October 2007


                    src_addr="192.0.2.5:9000"/"192.0.2.5:9001"
                    ssrc=93CB001E
         Session: 12345678
         Expires: 24 Jan 1997 15:35:12 GMT
         Date: 23 Jan 1997 15:35:12 GMT
         Accept-Ranges: NPT
         Pipelined-Requests: 7654

   M->C: RTSP/2.0 200 OK
         CSeq: 3
         Server: PhonyServer/1.0
         Transport: RTP/AVP;unicast;dest_addr=":8002"/":8003;
                    src_addr="192.0.2.5:9002"/"192.0.2.5:9003";
                    ssrc=A813FC13
         Session: 12345678
         Expires: 24 Jan 1997 15:35:13 GMT
         Date: 23 Jan 1997 15:35:13 GMT
         Accept-Range: NPT
         Pipelined-Requests: 7654

   M->C: RTSP/2.0 200 OK
         CSeq: 4
         Server: PhonyServer/1.0
         Date: 23 Jan 1997 15:35:14 GMT
         Session: 12345678
         Range: npt=0-10, npt=30-623.10
         RTP-Info: url="rtsp://example.com/twister.3gp/trackID=4"
            ssrc=0D12F123:seq=12345;rtptime=3450012,
           url="rtsp://example.com/twister.3gp/trackID=1";
            ssrc=4F312DD8:seq=54321;rtptime=2876889
         Pipelined-Requests: 7654


20.2.2 Message Syntax

  general-header  =  Cache-Control
                   /  Connection
                   /  CSeq
                   /  Date
                   /  Pipelined-Requests
                   /  Proxy-Supported
                   /  Supported
                   /  Timestamp
                   /  Via
                   /  extension-header


20.2.3 Header Syntax

Pipelined-Requests = "Pipelined-Requests" HCOLON startup-id
 startup-id  = 1*8DIGIT

Appendix H. Changes

   o  RTSP message handling has been changed in the following way:

      *  RTSP messages now uses URIs rather then URLs.

      *  It has been clarified that a 4xx message due to missing CSeq
         header shall be returned without a CSeq header.

      *  Rules for how to handle timing out RTSP messages has been
         added.

      *  Extended Pipelining rules allowing for quick session
         startup.


-- 

Magnus Westerlund

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


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



From mmusic-bounces@ietf.org Fri Oct 26 13:32:10 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IlT1v-0003L7-QD; Fri, 26 Oct 2007 13:31:31 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IlT1u-0003JC-I6
	for mmusic-confirm+ok@megatron.ietf.org; Fri, 26 Oct 2007 13:31:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IlT1t-0003GG-3b; Fri, 26 Oct 2007 13:31:29 -0400
Received: from lancia.electric.net ([216.129.90.248])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IlT1k-0001Re-G3; Fri, 26 Oct 2007 13:31:20 -0400
Received: from 1IlT1g-0006XI-UN by lancia.electric.net with emc1-ok (Exim 4.67)
	(envelope-from <raihan@eyeball.com>)
	id 1IlT1h-0006ZA-TP; Fri, 26 Oct 2007 10:31:17 -0700
Received: by emcmailer; Fri, 26 Oct 2007 10:31:17 -0700
Received: from 64-85-36-161.ip.van.radiant.net ([64.85.36.161]
	helo=[127.0.0.1]) by lancia.electric.net with esmtpa (Exim 4.67)
	(envelope-from <raihan@eyeball.com>)
	id 1IlT1g-0006XI-UN; Fri, 26 Oct 2007 10:31:16 -0700
Message-ID: <47222589.7060903@eyeball.com>
Date: Fri, 26 Oct 2007 10:36:09 -0700
From: Raihan <raihan@eyeball.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5
MIME-Version: 1.0
To: livio.torrero@polito.it
Subject: Re: [MMUSIC] Looking for UAs supporting ICE
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Outbound-IP: 64.85.36.161
X-Env-From: raihan@eyeball.com
X-Virus-Status: Scanned by VirusSMART (c)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: behave@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>
Errors-To: mmusic-bounces@ietf.org

Hi Livio,

Sorry for the late response.

My employer, Eyeball Networks, has a user-agent and other NAT-traversal
solutions that support recent drafts of STUN, TURN and ICE.  We have three
products of interest:
 
- Eyeball Messenger: A soft-client or user-agent that provides voice, video
and IM features with NAT traversal using STUN, TURN and ICE. 

- AnyFirewall Engine: Industry's leading firewall and NAT traversal SDK
offering a comprehensive implementation of STUN, TURN and ICE (along with
optional support for UPnP gateways and HTTP-tunneling), and

- AnyFirewall Server: A carrier-grade STUN and TURN server ready for mass
deployment.

Eyeball white-paper titled, "NAT Traversal using ICE for VoIP
and Internet Communications"  provides a high level overview of how
NAT-traversal using ICE works, and how Eyeball solutions can help.
(http://www.eyeball.com/technology/whitepapers/NAT_Traversal_Using_ICE.pdf) 

Hope this helps.  Please let me know if you need additional information.

Regards,
Raihan


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

   Date: Thu, 23 Aug 2007 16:45:23 +0200
>> From: Livio Torrero <livio.torrero@polito.it>
>> Subject: [MMUSIC] Looking for UAs supporting ICE
>> To: MMUSIC <mmusic@ietf.org>
>> Message-ID: <46CD9D83.6090305@polito.it>
>> Content-Type: text/plain; charset=ISO-8859-15; format=flowed
>>
>> I'm currently investigating NAT traversal techniques for SIP User
>>  Agents
>> and I've read all the ICE-related drafts. I'm very interested in it and
>>
>> I would like to try a UA supporting ICE. Could you please suggest me if
>>
>> and where I can download a free UA supporting ICE? If it is not
>> possible, can you please suggest me commercial UAs supporting it? I've
>> just tried Counterpath X-lite but it seems to me that the ICE version
>> included is out of date. Is there any chance to have an UA supporting a
>>
>> more recent version?
>>
>> Best regards,
>> Livio Torrero



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



From mmusic-bounces@ietf.org Fri Oct 26 14:44:34 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IlU9o-0000eK-K3; Fri, 26 Oct 2007 14:43:44 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IlU9m-0000cl-Li
	for mmusic-confirm+ok@megatron.ietf.org; Fri, 26 Oct 2007 14:43:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IlU9m-0000cd-Bz
	for mmusic@ietf.org; Fri, 26 Oct 2007 14:43:42 -0400
Received: from quinthar.com ([64.62.221.66])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IlU9g-00085y-24
	for mmusic@ietf.org; Fri, 26 Oct 2007 14:43:42 -0400
Received: from lappy ([98.207.96.5]) by quinthar.com for <mmusic@ietf.org>;
	Fri, 26 Oct 2007 11:43:15 -0700
From: "David Barrett" <dbarrett@quinthar.com>
To: "'Raihan'" <raihan@eyeball.com>,
	<livio.torrero@polito.it>
Subject: RE: [BEHAVE] Re: [MMUSIC] Looking for UAs supporting ICE
Date: Fri, 26 Oct 2007 11:43:14 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <47222589.7060903@eyeball.com>
Thread-Index: AcgX9nFINjOKLs9JSUmzqcfHaF0blQACXkwA
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Message-Id: <E1IlU9m-0000cl-Li@megatron.ietf.org>
Cc: behave@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>
Errors-To: mmusic-bounces@ietf.org

That's great!  Do you have any test results showing the effectiveness of the
NAT penetration technology?  Specifically, what is the success rate of
direct peer connectivity (non-TURN), and how long does it take to set up a
connection?

-david

> -----Original Message-----
> From: Raihan [mailto:raihan@eyeball.com]
> Sent: Friday, October 26, 2007 10:36 AM
> To: livio.torrero@polito.it
> Cc: behave@ietf.org; mmusic@ietf.org
> Subject: [BEHAVE] Re: [MMUSIC] Looking for UAs supporting ICE
> 
> Hi Livio,
> 
> Sorry for the late response.
> 
> My employer, Eyeball Networks, has a user-agent and other NAT-traversal
> solutions that support recent drafts of STUN, TURN and ICE.  We have three
> products of interest:
> 
> - Eyeball Messenger: A soft-client or user-agent that provides voice,
> video
> and IM features with NAT traversal using STUN, TURN and ICE.
> 
> - AnyFirewall Engine: Industry's leading firewall and NAT traversal SDK
> offering a comprehensive implementation of STUN, TURN and ICE (along with
> optional support for UPnP gateways and HTTP-tunneling), and
> 
> - AnyFirewall Server: A carrier-grade STUN and TURN server ready for mass
> deployment.
> 
> Eyeball white-paper titled, "NAT Traversal using ICE for VoIP
> and Internet Communications"  provides a high level overview of how
> NAT-traversal using ICE works, and how Eyeball solutions can help.
> (http://www.eyeball.com/technology/whitepapers/NAT_Traversal_Using_ICE.pdf
> )
> 
> Hope this helps.  Please let me know if you need additional information.
> 
> Regards,
> Raihan
> 
> 
> -------------------
> 
>    Date: Thu, 23 Aug 2007 16:45:23 +0200
> >> From: Livio Torrero <livio.torrero@polito.it>
> >> Subject: [MMUSIC] Looking for UAs supporting ICE
> >> To: MMUSIC <mmusic@ietf.org>
> >> Message-ID: <46CD9D83.6090305@polito.it>
> >> Content-Type: text/plain; charset=ISO-8859-15; format=flowed
> >>
> >> I'm currently investigating NAT traversal techniques for SIP User
> >>  Agents
> >> and I've read all the ICE-related drafts. I'm very interested in it and
> >>
> >> I would like to try a UA supporting ICE. Could you please suggest me if
> >>
> >> and where I can download a free UA supporting ICE? If it is not
> >> possible, can you please suggest me commercial UAs supporting it? I've
> >> just tried Counterpath X-lite but it seems to me that the ICE version
> >> included is out of date. Is there any chance to have an UA supporting a
> >>
> >> more recent version?
> >>
> >> Best regards,
> >> Livio Torrero
> 
> 
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www1.ietf.org/mailman/listinfo/behave



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



From mmusic-bounces@ietf.org Fri Oct 26 16:26:25 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IlVjJ-0003R3-H2; Fri, 26 Oct 2007 16:24:29 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IlVjI-0003Qw-8D
	for mmusic-confirm+ok@megatron.ietf.org; Fri, 26 Oct 2007 16:24:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IlVjH-0003Qo-Ug
	for mmusic@ietf.org; Fri, 26 Oct 2007 16:24:27 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IlVjB-00030d-Ix
	for mmusic@ietf.org; Fri, 26 Oct 2007 16:24:27 -0400
X-IronPort-AV: E=Sophos;i="4.21,335,1188792000"; d="scan'208";a="78390307"
Received: from unknown (HELO 306181ANEX3.global.avaya.com) ([135.9.6.105])
	by co300216-co-outbound.avaya.com with ESMTP; 26 Oct 2007 16:24:16 -0400
Received: from [135.9.42.64] ([135.9.42.64]) by 306181ANEX3.global.avaya.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 26 Oct 2007 14:23:36 -0600
Message-ID: <47224C8B.2050804@avaya.com>
Date: Fri, 26 Oct 2007 14:22:35 -0600
From: "Robert R. Gilman" <rrg@avaya.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens.com>, 
	Eric Rescorla <ekr@networkresonance.com>
Subject: Re: [MMUSIC] Symmetry breaking for DTLS-SRTP
References: <20071024165908.CDB1B33C28@delta.rtfm.com>
	<0D5F89FAC29E2C41B98A6A762007F5D037D5E4@GBNTHT12009MSX.gb002.siemens.net>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D037D5E4@GBNTHT12009MSX.gb002.siemens.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Oct 2007 20:23:36.0034 (UTC)
	FILETIME=[16274420:01C8180E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
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>
Errors-To: mmusic-bounces@ietf.org

John-
I think such flows can arise from a case in which one party, rather than
the controller, intiates the call.  But, as you point out, the controller
cannot blindly pass one offer through to serve as an answer; it must
modify the SDP in some cases.  For DTLS, in accord with the rules in
section 4.1 of RFC 4145, the offeror, assuming it can act as either a
server or a client, should use
	a=setup-attr: actpass
and should be prepared to receive a client_hello before it receives the
answer.  In the two-party case, the answer would normally include
	a=setup: active
and the answerer would go ahead and send the client_hello in the media
path.  This permits the controller (indeed, it requires the controller)
to break the symmetry by modifying the SDP, hence we don't need any
random numbers (which remind me too much of the H.245 master/slave
resolution scheme).  If, for some reason, an endpoint can only act as
a server, say, then in must send passive, and the controller can adjust
which end it selects to be active - or it can refuse the call (or
terminate the media on a media server) if both endpoints insist on the
same role.  I believe this scheme is compatible with Dan Wing's draft:
draft-wing-sip-identity-media-00.

The exchange might look something like this:

Alice                        Controller                        Bob
------------------------------------------------------------------
INVITE + Offer(actpass) ->
                                     INVITE ->
                                              <- OK + Offer(actpass)
           <- OK + Answer(active)    ACK + Answer(passive) ->
       <- - - - - - - - - - - client_hello - - - - - - - - - -
ACK ->
                               ....
Does this make sense?
-Bob
----------------------------------------------------
Bob Gilman       rrg@avaya.com      +1 303 538 3868

Elwell, John wrote:
> Ekr,
> 
> I don't have a problem with the solution, but I am doubtful whether it
> is a problem we need to solve. The case illustrated is based on the
> assumption that offer and answer are symmetrical, in the sense that an
> offer can be reused as an answer (and vice versa). In this case the
> offer from A becomes an answer to B and vice versa. There are two
> extensions to SDP that I am aware of that break this, and therefore any
> controller that misuses SDP in this way will screw things up. One
> example is the key management extension when used to carry MIKEY,
> because a MIKEY request (which always goes in the offer) is very
> different in syntax and semantics from a MIKEY response (which always
> goes in the answer). Of course, this will not apply when using DTLS-SRTP
> as the means of key management. The second example is the SDP capability
> negotiation draft, which certainly will be applicable with DTLS-SRTP.
> 
> I am not aware of how the particular flow shown would arise. It is not
> documented in RFC 3725 (3PCC). It has similarities to flow II in RFC
> 3725, which the RFC does not recommend. The other 3PCC flows in RFC 3725
> do not mix up offers and answers in this way.
> 
> I also questioned the need for the solution in ICE, but as it came
> virtually for free, it was not worth arguing about.
> 
> If we continue this discussion, I would suggest we stick to the MMUSIC
> list rather than AVT.
> 
> John
> 
> 
>>-----Original Message-----
>>From: Eric Rescorla [mailto:ekr@networkresonance.com] 
>>Sent: 24 October 2007 17:59
>>To: avt@ietf.org; mmusic@ietf.org
>>Subject: [MMUSIC] Symmetry breaking for DTLS-SRTP
>>
>>TLS (and by extension) DTLS-SRTP requires unambiguity about which side
>>is to be the client and which is the server. This isn't an issue of
>>credentials--DTLS-SRTP assumes that each side can take either
>>role--it's just that TLS requires that one side initiate the
>>handshake. My original intention had been to make this conditional on
>>which side was the offerer and which was the answerer, but JDR pointed
>>out in ORD that there are cases involving 3PCC where it's not
>>unambiguous which is which.
>>
>>Here's the paradigmatic case, transcribed from a phone call with
>>JDR (so any errors are my fault):
>>
>>
>>Alice                        Controller                        Bob
>>------------------------------------------------------------------
>>INVITE + Offer ->
>>                              INVITE ->
>>                                                     <- OK + Offer
>>                      <- OK + Answer                              
>>                              ACK + Answer ->
>>ACK ->
>>
>>Because the controller sends an INVITE with no offer, Bob is the
>>offererer, and of course Alice is. So, you can't use offerer
>>or answerer to break symmetry. 
>>
>>This same problem occurs with ICE, which uses a random tiebreaker
>>value in the ICE messages to determine which side should take
>>which role (controlling vs. controlled). This works because
>>in ICE both sides are trying to transmit so they quickly 
>>detect conflicts. Unfortunately, in DTLS-SRTP, the server just
>>waits so if the rule we adopt allows both sides to think they
>>are the server then we get deadlock. The above exchange 
>>shows how both sides can be offerer so clearly we can't have
>>offerer=server, but it seems that we could make a new exchange
>>where both sides are answerer in which case we can't have
>>offerer=client. JDR tells me that we don't have an actual
>>use case like this yet but I would not want to count on that
>>unless we're very sure.
>>
>>We could use exactly the trick that ICE uses but that requires
>>modifying DTLS to make the server send messages unprompted.
>>I don't think that's necessary here because we can break
>>the tie in the SDP where we announce the DTLS-SRTP capability
>>(however that's done).
>>
>>The basic principle is this:
>>1. Each side generates a random tiebreaker value T.
>>2. In the SDP offer/answer, he indicates whether he wishes
>>   to be the TLS client or server (if you're the offerer
>>   you SHOULD ask to be the server since that's faster, 
>>   and vice versa).
>>3. If each side sees a consistent view (one client, one 
>>   server) then that is what is used.
>>4. If the views are inconsistent, then the side with the
>>   higher T is be the client.
>>
>>This is basically the same algorithm as used with ICE, just
>>moving the tiebreaker into the SDP.
>>
>>Does anyone see a problem with this?
>>
>>-Ekr
>>
>>
>>
>>
>>
>>
>>_______________________________________________
>>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 Oct 26 18:40:34 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IlXp9-0006gN-CR; Fri, 26 Oct 2007 18:38:39 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1IlXp6-0006fU-RN
	for mmusic-confirm+ok@megatron.ietf.org; Fri, 26 Oct 2007 18:38:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IlXp6-0006bC-HR
	for mmusic@ietf.org; Fri, 26 Oct 2007 18:38:36 -0400
Received: from nz-out-0506.google.com ([64.233.162.226])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IlXoz-0007Yh-Cz
	for mmusic@ietf.org; Fri, 26 Oct 2007 18:38:30 -0400
Received: by nz-out-0506.google.com with SMTP id n1so867173nzf
	for <mmusic@ietf.org>; Fri, 26 Oct 2007 15:37:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth;
	bh=5s62EqJnlG16dDaAtxGCpD6xLB4rsCQvBV2k19wjUqA=;
	b=ayxSrJp3CD0qKTIo3XfmvfzBzJSRHOmHuyWFA/ruoXLK0WtgExE5L/NzWro/Wsq4lKxf0sqH2sBL7iyE82N1vE2fT4hbaFK1/838OhQj8Gbs64jtn12uAfeN4utGHfVZFjIu7ZTXI0huqN5qvI9Qme8jqK65zcP+9ljS5EuPBA0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth;
	b=KCOL9ccNmasRjGqoTymLOB0oR4mAL8tFV72J0YRCJf0+3hQJtsvKyEfLJQINm63AcunhTk7U0uBImyAbvikUZTO/QowdCoXiCwCSIVAAYcP+mtiTXbpR9Dj9AEBiXEwDpb+RQDGbX/w2nKWLU1jtwm77Gbfzj+nNI4XGOAHxJfY=
Received: by 10.142.255.14 with SMTP id c14mr1018943wfi.1193438276474;
	Fri, 26 Oct 2007 15:37:56 -0700 (PDT)
Received: by 10.142.78.20 with HTTP; Fri, 26 Oct 2007 15:37:56 -0700 (PDT)
Message-ID: <4d0605c20710261537x240f6ac0xc993fb0e834700d6@mail.gmail.com>
Date: Fri, 26 Oct 2007 15:37:56 -0700
From: "Joseph Pallas" <pallas@cs.stanford.edu>
To: mmusic@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Google-Sender-Auth: dcf5f96e5f76faea
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Subject: [MMUSIC] Re: RTSP 2.0: [ 1701558 ] Pause response to live streams
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>
Errors-To: mmusic-bounces@ietf.org

> To me it should indicate the point the server is ceasing to deliver
> media on. Also the live media have some time line. Either expressed in
> UTC or in NPT since session start. What ever is used needs to be
> reported. I don't think "now-" would be particular good answer. For that
> reason a clearer text on this would be good.

A simple way to do that is to say that "now" can only be used in
requests, not in responses.

> However, this leads me to another issue related to the content being
> played back. It might be time to be more explicit about the content
> properties related to playback.
...
> However, my question is: Should we define a new SDP attribute that
> expresses the contents major properties to allow RTSP clients to know
> what to handle?

It might be wise to separate that into two questions: (1) should there
be a way to express these properties, and (2) should the properties be
expressed in SDP or in RTSP itself.  I'm kind of biased against SDP
here, because it is generally information about how to interpret the
stream, not how to control it.

Just a thought.
joe


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



From mmusic-bounces@ietf.org Mon Oct 29 04:09:23 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ImPeE-00062I-O9; Mon, 29 Oct 2007 04:06:58 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1ImPeB-000616-Fn
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 29 Oct 2007 04:06:55 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ImPe6-00060A-F0
	for mmusic@ietf.org; Mon, 29 Oct 2007 04:06:50 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ImPe5-0006Af-WC
	for mmusic@ietf.org; Mon, 29 Oct 2007 04:06:50 -0400
Received: from relay12.apple.com (relay12.apple.com [17.128.113.53])
	by mail-out3.apple.com (Postfix) with ESMTP id 67E12169CA30;
	Mon, 29 Oct 2007 01:06:49 -0700 (PDT)
Received: from relay12.apple.com (unknown [127.0.0.1])
	by relay12.apple.com (Symantec Mail Security) with ESMTP id 4DC0D28090; 
	Mon, 29 Oct 2007 01:06:49 -0700 (PDT)
X-AuditID: 11807135-a4dd1bb000006eba-68-47259498373b
Received: from [17.66.41.15] (vpn1p005.euro.apple.com [17.66.41.15])
	by relay12.apple.com (Apple SCV relay) with ESMTP id 100C92808D;
	Mon, 29 Oct 2007 01:06:46 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p06240883c3473eef104c@[17.84.23.140]>
In-Reply-To: <758B5A159B385447B4F950DE72D7D7AD01AAC34F@srsdmail01.PVNS.COM>
References: <462387E3.20600@ericsson.com> <471DE980.8040207@ericsson.com>
	<FE6A9D3F2979884280CE0F5F5185517B5ACBB0@kor1corpmail01.mediator.com>
	<758B5A159B385447B4F950DE72D7D7AD01AAC34F@srsdmail01.PVNS.COM>
Date: Sun, 28 Oct 2007 05:50:40 +0100
To: Mike Severa <severa@pvnetsolutions.com>,
	Jaehwan Kim <jaehwan@vidiator.com>,
	Magnus Westerlund <magnus.westerlund@ericsson.com>
From: Dave Singer <singer@apple.com>
Subject: RE: [MMUSIC] RTSP: Speed header
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
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>
Errors-To: mmusic-bounces@ietf.org

We've had some quite long discussions about these headers in various 
groups.  Most people find them confusing, and there are also problems 
in the model.

First, it does seem that there is a reasonable need for 'VCR' 
controls in a control protocol:  "send me the media at twice rate 
(fast forward), -1 (play reverse) and so on."

Second, the protocol should also accomodate being able to control 
bandwidth;  "send me at twice rate and you also may use twice the 
normal bandwidth".  I (and others) have thought in the past that RTSP 
had this (I can never remember which is scale and which is speed).

It seems fairly clear that in this case the usual link between RTP 
timestamp and transmission time is maintained (modulo traffic 
smoothing).

RTSP has a control to *detach* these two from each other, so you can 
ask for media at say, twice its *playout* rate according to its 
timestamps.  The use cases I have heard tend to center around buffer 
management, but I believe that that is more correctly handled in RTP 
using a protocol such as that defined by 3GPP.

Finally, when playing at non-unitary rates, the concept that the RTP 
receiver is unaware is very hard to maintain.  Double-speed video is 
fairly easily done (if the bandwidth is there) by spacing the RTP 
timestamps closer and therefore playing the frames closer in time. 
This does not work for audio;  a frame there lasts for say 1024 
samples, and it really doesn't achieve any useful effect to get them 
at 512 sample intervals.  Usually, one treats the new stream as being 
at double the sample rate, and you either play it at that rate, or 
down-sample it again, optionally also pitch-shifting.  These 
operations on the  decoded media are obviously well away from the RTP 
stack.

We have seen some interesting experiments in ISMA with dropping 
frames from compressed audio streams, and they work better than you 
might expect for at least the codecs tried, but it can hardly be 
considered a general technique.

So, in summary, should perhaps RTSP have
a) a command to set the playout rate to non-unity; with the default 
that the same bandwidth should be used;
b) a command to set the bandwidth limit for the stream, compared to 
what the normal stream would use at a normal play rate.
c) documentation that the media stack below RTP is necessarily aware 
of non-unity rates and does the appropriate media management;
d) pointers to buffer and bandwidth management systems such as 3GPP 
for fast buffer-fill and other considerations.

?
-- 
David Singer
Apple/QuickTime


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



From mmusic-bounces@ietf.org Mon Oct 29 05:55:56 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ImRHL-0004SL-18; Mon, 29 Oct 2007 05:51:27 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1ImRHJ-0004S7-88
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 29 Oct 2007 05:51:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ImRHI-0004RH-9Y
	for mmusic@ietf.org; Mon, 29 Oct 2007 05:51:24 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ImRH1-0004hF-Us
	for mmusic@ietf.org; Mon, 29 Oct 2007 05:51:14 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	5359F2149A; Mon, 29 Oct 2007 10:50:59 +0100 (CET)
X-AuditID: c1b4fb3e-b1036bb0000007e1-ab-4725ad032589
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	403F2212E0; Mon, 29 Oct 2007 10:50:59 +0100 (CET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Oct 2007 10:50:14 +0100
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Oct 2007 10:50:14 +0100
Message-ID: <4725ACD6.90100@ericsson.com>
Date: Mon, 29 Oct 2007 10:50:14 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Joseph Pallas <pallas@cs.stanford.edu>
Subject: Re: [MMUSIC] Re: RTSP 2.0: [ 1701558 ] Pause response to live streams
References: <4d0605c20710261537x240f6ac0xc993fb0e834700d6@mail.gmail.com>
In-Reply-To: <4d0605c20710261537x240f6ac0xc993fb0e834700d6@mail.gmail.com>
X-Enigmail-Version: 0.95.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Oct 2007 09:50:14.0593 (UTC)
	FILETIME=[1AC4CB10:01C81A11]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
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>
Errors-To: mmusic-bounces@ietf.org

Joseph Pallas skrev:
>> To me it should indicate the point the server is ceasing to deliver
>> media on. Also the live media have some time line. Either expressed in
>> UTC or in NPT since session start. What ever is used needs to be
>> reported. I don't think "now-" would be particular good answer. For that
>> reason a clearer text on this would be good.
> 
> A simple way to do that is to say that "now" can only be used in
> requests, not in responses.
> 
>> However, this leads me to another issue related to the content being
>> played back. It might be time to be more explicit about the content
>> properties related to playback.
> ...
>> However, my question is: Should we define a new SDP attribute that
>> expresses the contents major properties to allow RTSP clients to know
>> what to handle?
> 
> It might be wise to separate that into two questions: (1) should there
> be a way to express these properties, and (2) should the properties be
> expressed in SDP or in RTSP itself.  I'm kind of biased against SDP
> here, because it is generally information about how to interpret the
> stream, not how to control it.
> 

Hi Joe,

Yes, you are right that it should be split into two questions. Regarding
number two. I agree that we should be as explicit as possible and where
it is suitable. I agree that it is good that we express as much as
possible in RTSP. However, that will create issues. First it makes it
problematic to do optimized pipelined setups unless the client knows
these properties before sending its requests. Secondly, I would notice
that at least most what at least I consider are actually properties of
the content rather than the control session and therefore belongs in the
content description which SDP is one protocol instance of. This of
course leads to the interesting question if one should indicate it in
only one place or both for covering all potential cases?

cheers

Magnus Westerlund

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


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



From mmusic-bounces@ietf.org Mon Oct 29 06:35:53 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ImRw8-0004q6-Vh; Mon, 29 Oct 2007 06:33:36 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1ImRw7-0004oc-Jh
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 29 Oct 2007 06:33:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ImRw7-0004oT-A7
	for mmusic@ietf.org; Mon, 29 Oct 2007 06:33:35 -0400
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=bemg01.siemenscomms.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ImRvu-0006ZU-VX
	for mmusic@ietf.org; Mon, 29 Oct 2007 06:33:35 -0400
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JQO004665A4HL@siemenscomms.co.uk> for mmusic@ietf.org;
	Mon, 29 Oct 2007 10:32:28 +0000 (GMT)
Date: Mon, 29 Oct 2007 10:32:50 +0000
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [MMUSIC] Symmetry breaking for DTLS-SRTP
In-reply-to: <47224C8B.2050804@avaya.com>
To: "Robert R. Gilman" <rrg@avaya.com>,
	Eric Rescorla <ekr@networkresonance.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D037D850@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Thread-Topic: [MMUSIC] Symmetry breaking for DTLS-SRTP
Thread-Index: AcgYDi1CpmAyCKrzSLW7mDqR4mIJRwCCGEfQ
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <20071024165908.CDB1B33C28@delta.rtfm.com>
	<0D5F89FAC29E2C41B98A6A762007F5D037D5E4@GBNTHT12009MSX.gb002.siemens.net>
	<47224C8B.2050804@avaya.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93df555cbdbcdae9621e5b95d44b301e
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>
Errors-To: mmusic-bounces@ietf.org

OK, but to take my example of SDP capability negotiation, the controller
would have to resolve it somehow, i.e., for each leg, select a
configuration that is compatible with one of the proposed configurations
from Alice and with one of the proposed configurations from Bob, and
include this in the answers to Alice and Bob respectively. Ugly.

John

> -----Original Message-----
> From: Robert R. Gilman [mailto:rrg@avaya.com] 
> Sent: 26 October 2007 21:23
> To: Elwell, John; Eric Rescorla
> Cc: mmusic@ietf.org
> Subject: Re: [MMUSIC] Symmetry breaking for DTLS-SRTP
> 
> John-
> I think such flows can arise from a case in which one party, 
> rather than
> the controller, intiates the call.  But, as you point out, 
> the controller
> cannot blindly pass one offer through to serve as an answer; it must
> modify the SDP in some cases.  For DTLS, in accord with the rules in
> section 4.1 of RFC 4145, the offeror, assuming it can act as either a
> server or a client, should use
> 	a=setup-attr: actpass
> and should be prepared to receive a client_hello before it 
> receives the
> answer.  In the two-party case, the answer would normally include
> 	a=setup: active
> and the answerer would go ahead and send the client_hello in the media
> path.  This permits the controller (indeed, it requires the 
> controller)
> to break the symmetry by modifying the SDP, hence we don't need any
> random numbers (which remind me too much of the H.245 master/slave
> resolution scheme).  If, for some reason, an endpoint can only act as
> a server, say, then in must send passive, and the controller 
> can adjust
> which end it selects to be active - or it can refuse the call (or
> terminate the media on a media server) if both endpoints insist on the
> same role.  I believe this scheme is compatible with Dan Wing's draft:
> draft-wing-sip-identity-media-00.
> 
> The exchange might look something like this:
> 
> Alice                        Controller                        Bob
> ------------------------------------------------------------------
> INVITE + Offer(actpass) ->
>                                      INVITE ->
>                                               <- OK + Offer(actpass)
>            <- OK + Answer(active)    ACK + Answer(passive) ->
>        <- - - - - - - - - - - client_hello - - - - - - - - - -
> ACK ->
>                                ....
> Does this make sense?
> -Bob
> ----------------------------------------------------
> Bob Gilman       rrg@avaya.com      +1 303 538 3868
> 
> Elwell, John wrote:
> > Ekr,
> > 
> > I don't have a problem with the solution, but I am doubtful 
> whether it
> > is a problem we need to solve. The case illustrated is based on the
> > assumption that offer and answer are symmetrical, in the 
> sense that an
> > offer can be reused as an answer (and vice versa). In this case the
> > offer from A becomes an answer to B and vice versa. There are two
> > extensions to SDP that I am aware of that break this, and 
> therefore any
> > controller that misuses SDP in this way will screw things up. One
> > example is the key management extension when used to carry MIKEY,
> > because a MIKEY request (which always goes in the offer) is very
> > different in syntax and semantics from a MIKEY response 
> (which always
> > goes in the answer). Of course, this will not apply when 
> using DTLS-SRTP
> > as the means of key management. The second example is the 
> SDP capability
> > negotiation draft, which certainly will be applicable with 
> DTLS-SRTP.
> > 
> > I am not aware of how the particular flow shown would 
> arise. It is not
> > documented in RFC 3725 (3PCC). It has similarities to flow II in RFC
> > 3725, which the RFC does not recommend. The other 3PCC 
> flows in RFC 3725
> > do not mix up offers and answers in this way.
> > 
> > I also questioned the need for the solution in ICE, but as it came
> > virtually for free, it was not worth arguing about.
> > 
> > If we continue this discussion, I would suggest we stick to 
> the MMUSIC
> > list rather than AVT.
> > 
> > John
> > 
> > 
> >>-----Original Message-----
> >>From: Eric Rescorla [mailto:ekr@networkresonance.com] 
> >>Sent: 24 October 2007 17:59
> >>To: avt@ietf.org; mmusic@ietf.org
> >>Subject: [MMUSIC] Symmetry breaking for DTLS-SRTP
> >>
> >>TLS (and by extension) DTLS-SRTP requires unambiguity about 
> which side
> >>is to be the client and which is the server. This isn't an issue of
> >>credentials--DTLS-SRTP assumes that each side can take either
> >>role--it's just that TLS requires that one side initiate the
> >>handshake. My original intention had been to make this 
> conditional on
> >>which side was the offerer and which was the answerer, but 
> JDR pointed
> >>out in ORD that there are cases involving 3PCC where it's not
> >>unambiguous which is which.
> >>
> >>Here's the paradigmatic case, transcribed from a phone call with
> >>JDR (so any errors are my fault):
> >>
> >>
> >>Alice                        Controller                        Bob
> >>------------------------------------------------------------------
> >>INVITE + Offer ->
> >>                              INVITE ->
> >>                                                     <- OK + Offer
> >>                      <- OK + Answer                              
> >>                              ACK + Answer ->
> >>ACK ->
> >>
> >>Because the controller sends an INVITE with no offer, Bob is the
> >>offererer, and of course Alice is. So, you can't use offerer
> >>or answerer to break symmetry. 
> >>
> >>This same problem occurs with ICE, which uses a random tiebreaker
> >>value in the ICE messages to determine which side should take
> >>which role (controlling vs. controlled). This works because
> >>in ICE both sides are trying to transmit so they quickly 
> >>detect conflicts. Unfortunately, in DTLS-SRTP, the server just
> >>waits so if the rule we adopt allows both sides to think they
> >>are the server then we get deadlock. The above exchange 
> >>shows how both sides can be offerer so clearly we can't have
> >>offerer=server, but it seems that we could make a new exchange
> >>where both sides are answerer in which case we can't have
> >>offerer=client. JDR tells me that we don't have an actual
> >>use case like this yet but I would not want to count on that
> >>unless we're very sure.
> >>
> >>We could use exactly the trick that ICE uses but that requires
> >>modifying DTLS to make the server send messages unprompted.
> >>I don't think that's necessary here because we can break
> >>the tie in the SDP where we announce the DTLS-SRTP capability
> >>(however that's done).
> >>
> >>The basic principle is this:
> >>1. Each side generates a random tiebreaker value T.
> >>2. In the SDP offer/answer, he indicates whether he wishes
> >>   to be the TLS client or server (if you're the offerer
> >>   you SHOULD ask to be the server since that's faster, 
> >>   and vice versa).
> >>3. If each side sees a consistent view (one client, one 
> >>   server) then that is what is used.
> >>4. If the views are inconsistent, then the side with the
> >>   higher T is be the client.
> >>
> >>This is basically the same algorithm as used with ICE, just
> >>moving the tiebreaker into the SDP.
> >>
> >>Does anyone see a problem with this?
> >>
> >>-Ekr
> >>
> >>
> >>
> >>
> >>
> >>
> >>_______________________________________________
> >>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 Mon Oct 29 09:46:17 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ImUwI-0003Hp-8O; Mon, 29 Oct 2007 09:45:58 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1ImUwH-0003Gx-BF
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 29 Oct 2007 09:45:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ImUwH-0003Gn-0m
	for mmusic@ietf.org; Mon, 29 Oct 2007 09:45:57 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ImUwF-0007SJ-EN
	for mmusic@ietf.org; Mon, 29 Oct 2007 09:45:57 -0400
X-IronPort-AV: E=Sophos;i="4.21,342,1188802800"; d="scan'208";a="13689180"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by sj-iport-4.cisco.com with ESMTP; 29 Oct 2007 06:45:47 -0700
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l9TDjlrL029942; 
	Mon, 29 Oct 2007 09:45:47 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l9TDjedQ020527; 
	Mon, 29 Oct 2007 13:45:45 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Oct 2007 09:45:45 -0400
Received: from [10.82.211.73] ([10.82.211.73]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Oct 2007 09:45:44 -0400
Message-ID: <4725107D.90503@cisco.com>
Date: Sun, 28 Oct 2007 18:43:09 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Re: [MMUSIC] ICE retransmitted Binding Request processing
References: <f40963db0710021536o62015b51j40ee2c22a9f8b66f@mail.gmail.com>
	<470347F3.9050908@ericsson.com>
In-Reply-To: <470347F3.9050908@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Oct 2007 13:45:44.0688 (UTC)
	FILETIME=[00F62F00:01C81A32]
X-TM-AS-Product-Ver: SMEX-8.0.0.1181-5.000.1023-15508.000
X-TM-AS-Result: No--41.317800-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3803; t=1193665547;
	x=1194529547; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20[MMUSIC]=20ICE=20retransmitted=20Binding=20Request=20
	processing |Sender:=20
	|To:=20Magnus=20Westerlund=20<magnus.westerlund@ericsson.com>;
	bh=1TYxSdyk7bKcgWQMKks45LGntZPr6vaVyqhsfOGq6Jg=;
	b=RBKp7dpgk/wyX1EX15xWWr1y/Io80r8WsvACvX4jRl4D64XSvRMoojYhqSVrnB74/g5THu4B
	G05y73TfA8bSEXtbW/cpXc0tLpLw/m7DRK4jPMsFFQwVh/Glz0rx8Sbp;
Authentication-Results: rtp-dkim-2; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: -2.2 (--)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: Adam Fisk <a@lastbamboo.org>, draft-ietf-mmusic-ice@tools.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>
Errors-To: mmusic-bounces@ietf.org

Yes, this is a bug. I had in mind an implementation which implemented 
transaction state, and thus silently absorbed retransmits. For such an 
implementation you would not see this. However Adam is correct that such 
an implementation is certainly allowed. I changed the text from:

o  If the pair is already on the check list:

       *  If the state of that pair is Waiting or Frozen, a check for
          that pair is enqueued into the triggered check queue.

to:

o  If the pair is already on the check list:

       *  If the state of that pair is Waiting or Frozen, a check for
          that pair is enqueued into the triggered check queue if not 
already present.


I believe that fixes the problem.

Thanks,
Jonathan R.

Magnus Westerlund wrote:
> Hi Adam,
> 
> In my opinion you should do the following.
> - Always respond to binding requests, as the first response may not have
> reached the requestor.
> 
> - Not perform the Triggered check for anything more than the first
> request. No restart nor multiple queuing of the connectivity check for
> that candidate pair.
> 
> I think there might be need for clarification on this in the ICE spec.
> 
> Cheers
> 
> Magnus
> 
> Adam Fisk skrev:
>  > I've noticed in my ICE tests that it's quite common for a peer to
>  > receive multiple Binding Requests for the same STUN transaction as a
>  > result of STUN retransmissions.
>  >
>  > While this is to be expected, the processing of the request specified in
>  > ICE 18 section 7.2.1.4 <http://7.2.1.4> "Triggered Checks" results in
>  > adding precisely the same candidate pair to the triggered check queue
>  > multiple times, resulting in multiple subsequent identical triggered
>  > checks and subsequent work.  Is this the expected behavior, or am I
>  > missing something?  While it doesn't seem the above will break anything,
>  > it doesn't appear optimal either.
>  >
>  > Should the triggered check queue filter duplicates?  Should the STUN
>  > server side in ICE ignore Binding Requests with transaction IDs it has
>  > already processed (clearly still sending Binding Responses, just not
>  > forwarding the request to the ICE procedures)?  I'd assume the latter,
>  > but it seems I must be missing something in one of the specs if this is
>  > the case.
>  >
>  > This is assuming the ICE STUN server side just reprocesses each Binding
>  > Request and recomputes the Binding Response each time since the Binding
>  > method is idempotent, as specified in draft-ietf-behave-rfc3489bis-10
>  > section 7.3.1 "Processing a Request."
>  >
>  > Thanks very much.
>  >
>  > -Adam Fisk
>  >
>  >
>  >
>  > ------------------------------------------------------------------------
>  >
>  > _______________________________________________
>  > mmusic mailing list
>  > mmusic@ietf.org
>  > https://www1.ietf.org/mailman/listinfo/mmusic
> 
> 
> --
> 
> Magnus Westerlund
> 
> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM/M
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
> 

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


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



From mmusic-bounces@ietf.org Mon Oct 29 09:46:17 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ImUwG-0003Gj-TI; Mon, 29 Oct 2007 09:45:56 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1ImUwF-0003GX-HO
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 29 Oct 2007 09:45:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ImUwF-0003GM-7l
	for mmusic@ietf.org; Mon, 29 Oct 2007 09:45:55 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ImUw9-0007SJ-Va
	for mmusic@ietf.org; Mon, 29 Oct 2007 09:45:55 -0400
X-IronPort-AV: E=Sophos;i="4.21,342,1188802800"; d="scan'208";a="13689178"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by sj-iport-4.cisco.com with ESMTP; 29 Oct 2007 06:45:45 -0700
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l9TDjjiE029930; 
	Mon, 29 Oct 2007 09:45:45 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l9TDjedM020527; 
	Mon, 29 Oct 2007 13:45:40 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Oct 2007 09:45:39 -0400
Received: from [10.82.211.73] ([10.82.211.73]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Oct 2007 09:45:39 -0400
Message-ID: <47250EF3.6000606@cisco.com>
Date: Sun, 28 Oct 2007 18:36:35 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Adam Fisk <a@lastbamboo.org>
Subject: Re: [MMUSIC] ICE-18 Nominating pairs on controlled agents
References: <f40963db0710081411y136a15d1h24db8e5417015764@mail.gmail.com>
In-Reply-To: <f40963db0710081411y136a15d1h24db8e5417015764@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Oct 2007 13:45:39.0656 (UTC)
	FILETIME=[FDF65C80:01C81A31]
X-TM-AS-Product-Ver: SMEX-8.0.0.1181-5.000.1023-15508.000
X-TM-AS-Result: No--33.093800-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3193; t=1193665545;
	x=1194529545; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20[MMUSIC]=20ICE-18=20Nominating=20pairs=20on=20control
	led=20agents |Sender:=20
	|To:=20Adam=20Fisk=20<a@lastbamboo.org>;
	bh=U8mVedTCm5Ug0EBQppuJ0hTGob+/x5YtHqdi6bK7QCQ=;
	b=cKsVDpHgFdFfZ6DcwsCUIrJi8lbGLbw6UuPBTXAqJfD8yp7Ux3kxDcWL+BQfS7nzy3MOtLvE
	V8sOHal/p5BmGpNzMDo7PTv7W6Oxu+vc5OgRbCo0nJs9h8PyGHELvluf;
Authentication-Results: rtp-dkim-2; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: -2.2 (--)
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>
Errors-To: mmusic-bounces@ietf.org



Adam Fisk wrote:
> Apologies for the comments so late in the game on the ICE drafts, but 
> there appears to be a minor error in the nominating of pairs on 
> controlled agents.
> 
> Section 7.1.2.2.4 on performing STUN client connectivity checks reads:
> 
> "If the agent is the controlled agent, the response may result in the 
> valid pair having its nominated flag set. See section 7.2.1.5 
> <http://7.2.1.5> for the procedure."
>     -- http://tools.ietf.org/html/draft-ietf-mmusic-ice-18#section-7.1.2.2.4
> 
> 7.2.1.5 <http://7.2.1.5> then reads:
> 
> "If the Binding Request received by the agent had the USE-CANDIDATE 
> attribute set, and the agent is in the controlled role, the agent looks 
> at the state of the pair computed in Section 7.2.1.4:" 
>     -- 
> http://tools.ietf.org/html/draft-ietf-mmusic-ice-18#section-7.2.1.5 
> <http://tools.ietf.org/html/draft-ietf-mmusic-ice-18#section-7.2.1.5>
> 
> Shouldn't the last part of 7.2.1.5 <http://7.2.1.5> at least read: "the 
> agent looks at the state of the pair computed in Section 7.2.1.4 
> <http://7.2.1.4> or in Section 7.1.2.2.4:"?  Otherwise, you'd just 
> immediately ignore then whole of section 7.2.1.5 <http://7.2.1.5> when 
> processing pairs computed from section 7.1.2.2.4.

I agree this is confusing, though it is correct. The case here is this. 
An agent is controlled. It gets a request with a USE-CANDIDATE. This 
causes the triggered check (7.2.1.4). That check produces a response. 
Once that response arrives, the pair from the *original request* now has 
its nominated flag set. So 7.1.2.2.4 is trying to say, "hey, this 
response might be for a triggered check that you sent as a result of the 
processing of 7.2.1.5, so you may need to follow its directions now". 
I'll make that more clear.


> 
> That's it for the "error" -- almost more a nit really.  Digging a little 
> deeper, though, it seems to me that the nomination decision for the 
> controlled agent in 7.1.2.2.4 should be really simple and should not 
> have to reference section 7.2.1.5 <http://7.2.1.5> at all.  Basically, 
> if the pair received USE-CANDIDATE in the past, it should be nominated.  
> This is because the pair has just reached the successful state when we 
> get to section 7.1.2.2.4, so all we need to know is whether or not we've 
> received USE-CANDIDATE yet or not. 

And this is what the text is saying (or trying to at least). Hopefully 
this text is clearer now:

<t>
If the agent is the controlled agent, the response may be the result
of a triggered check which was sent in response to a request which 
itself had
the USE-CANDIDATE attribute. This case is described in
<xref target="sec-up-fav"/>, and may now result in setting the
nominated flag for the pair learned from the original request.
</t>

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


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



From mmusic-bounces@ietf.org Mon Oct 29 09:46:17 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ImUw7-0003Fc-3b; Mon, 29 Oct 2007 09:45:47 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1ImUw6-0003Da-3D
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 29 Oct 2007 09:45:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ImUw5-0003DS-Pq
	for mmusic@ietf.org; Mon, 29 Oct 2007 09:45:45 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ImUvz-0007Re-LD
	for mmusic@ietf.org; Mon, 29 Oct 2007 09:45:45 -0400
X-IronPort-AV: E=Sophos;i="4.21,342,1188792000"; d="scan'208";a="74902698"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 29 Oct 2007 09:45:33 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l9TDjWwb006991; 
	Mon, 29 Oct 2007 09:45:33 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l9TDiuds020153; 
	Mon, 29 Oct 2007 13:45:32 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Oct 2007 09:45:32 -0400
Received: from [10.82.211.73] ([10.82.211.73]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Oct 2007 09:45:29 -0400
Message-ID: <47250BB6.5000608@cisco.com>
Date: Sun, 28 Oct 2007 18:22:46 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] ICE: Clarification question when full ICE communciate
	with	ICE lite and chooses host candidate
References: <CA9998CD4A020D418654FCDEF4E707DF02BC97B3@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF02BC97B3@esealmw113.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Oct 2007 13:45:31.0859 (UTC)
	FILETIME=[F950A230:01C81A31]
X-TM-AS-Product-Ver: SMEX-8.0.0.1181-5.000.1023-15508.000
X-TM-AS-Result: No--22.011800-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1563; t=1193665533;
	x=1194529533; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20[MMUSIC]=20ICE=3A=20Clarification=20question=20when=2
	0full=20ICE=20communciate=0A=20with=09ICE=20lite=20and=20chooses=20host=20
	candidate |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.com>;
	bh=IIBWCtXhNoWH8C+MqnZ7aPOSI5fTA/Y8zuypVMWXhGs=;
	b=rabW0J1y9DjxlRZxuFdGYUHExO8MHI3unORK5vehU0U9zwsmD+EEYmfcAlbcV7eFSDSq7oeQ
	NMGu8Nhu5bv39WlG57mZrRUi2KuNPByRBVOnjYks+NBrDT0cWM38YdNs;
Authentication-Results: rtp-dkim-1; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
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>
Errors-To: mmusic-bounces@ietf.org

inline.

Christer Holmberg wrote:
> 
> Hi,
> 
> Assume the following scenario:
> 
> - User A is located behind a NAT, and implements full ICE.
> 
> - User A collects candidates, and send an INVITE
> 
> - The call is received by an MGCF, implementing ICE lite.
> 
> - User A starts doing connectivity checks, which the MGCF reply to 
> (being ICE lite, the MGCF does not generate checks itself)
> 
> - User A detects that the HOST_CANDIDATE checks work, so it sends an 
> UPDATE and tells the MGCF that the HOST_CANDIDATE will be used. The 
> Local Address information will be in the c/m line.
> 
> 
> Now, the MGCF will start sending media towards the Local Address. But, 
> since User A, and the Local Address, is behind the NAT, the media will 
> not reach User A.

No, this is not what will happen. The candidate pair learned from the 
checks sent by A are based on the mapped address from the connectivity 
checks. Quoting fro 7.1.2.2.2:

7.1.2.2.2.  Constructing a Valid Pair

    The agent constructs a candidate pair whose local candidate equals
    the mapped address of the response, and whose remote candidate equals
    the destination address to which the request was sent.


-Jonathan R.

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


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



From mmusic-bounces@ietf.org Mon Oct 29 09:46:17 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ImUvr-000302-NZ; Mon, 29 Oct 2007 09:45:31 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1ImUvq-0002zx-Ov
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 29 Oct 2007 09:45:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ImUvq-0002zp-DX
	for mmusic@ietf.org; Mon, 29 Oct 2007 09:45:30 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ImUvp-0000vy-SY
	for mmusic@ietf.org; Mon, 29 Oct 2007 09:45:30 -0400
X-IronPort-AV: E=Sophos;i="4.21,342,1188792000"; d="scan'208";a="135782325"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 29 Oct 2007 09:45:29 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l9TDjTCf006893; 
	Mon, 29 Oct 2007 09:45:29 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l9TDj3Be020323; 
	Mon, 29 Oct 2007 13:45:29 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Oct 2007 09:45:25 -0400
Received: from [10.82.211.73] ([10.82.211.73]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Oct 2007 09:45:24 -0400
Message-ID: <4724FE3B.8040702@cisco.com>
Date: Sun, 28 Oct 2007 17:25:15 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] ICE with media streams without candidates
References: <CA9998CD4A020D418654FCDEF4E707DF02A5D6FC@esealmw113.eemea.ericsson.se><200710221528.41180.remi.denis-courmont@nokia.com><CA9998CD4A020D418654FCDEF4E707DF02A8B9C8@esealmw113.eemea.ericsson.se><200710231528.52224.remi.denis-courmont@nokia.com>	<CA9998CD4A020D418654FCDEF4E707DF02ABE439@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF02BFD73A@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF02BFD73A@esealmw113.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Oct 2007 13:45:24.0719 (UTC)
	FILETIME=[F50F27F0:01C81A31]
X-TM-AS-Product-Ver: SMEX-8.0.0.1181-5.000.1023-15508.000
X-TM-AS-Result: No--24.161600-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3713; t=1193665529;
	x=1194529529; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20[MMUSIC]=20ICE=20with=20media=20streams=20without=20c
	andidates |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.com>;
	bh=6oEXKiE3dsCVVHT5yUfgIhL5pXN70YBDJdT0PaEh1ng=;
	b=QJ4OeJQ0vd6HGBKmFIVoMaF/ij7wGdvGFniQJY2Ti9Pw/BzT1tufiZG4Uqba0kBp0TpmPl8b
	UPRnZBQXclUvBDtIH5+LwG5r7D5dqbZKXgMBSE3zcgJnzEaLQP6fM03k;
Authentication-Results: rtp-dkim-1; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
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>
Errors-To: mmusic-bounces@ietf.org

This section does not in any way adding a new media stream that is not 
utilizing ICE. It simply says that you can add one and ICE processing 
for it begins when you do.

To answer your original question, the reason we elected to make it all 
or nothing was because of the unpredictability of ICE through SBCs. For 
example an SBC that is not ICE-aware, adds a media stream, but allows 
ICE parameters through, is actually very likely to have some kind of 
firewalling behavior associated with it, that blocks the media stream 
unless it behaves the way it expects. So in the interests of 
reliability, ICE backs off whenever it sees anything resembling a 
non-ICE aware intermediary.

This is something that was discussed quite a bit previously and I don't 
see any reason to re-evaluate our previous decision on this.

Thanks,
Jonathan R.

Christer Holmberg wrote:
> Hi, 
> 
>>>> Assume A calls B, and includes SDP with the ICE candidate attributes 
>>>> etc for each media stream.
>>>> In the middle there is a B2BUA application server, which wants to add 
>>>> a stream towards B, so it modifies the SDP by adding an extra m= line.
>>>> The application server, however, does not support ICE, so it does not 
>>>> include any candidate attributes.
>>> We can probably agree that if there is something that modifies this SDP 
>>> even though it does not terminate the SIP session, anything can happen. 
>>> And probably nobody wants to start a SBC flame war here ;)
>>>
>>> As a developper, I would rather it had been per-media, or better yet, a 
>>> per-component process, because it would have been much simpler to 
>>> implement and integrate. There are however several valid reasons why 
>>> ICE is a SIP per-session process, as far as ICE is used with SIP.
>>>
>>> I can think of plenty of loopholes if one media has ICE, but not another one.
>>> For instance, how would the UA know when to start sending media? But 
>>> most importantly, the decision to abort ICE when some inconsistency is 
>>> detected is all about maximizing backward compatibility with existing 
>>> setups. If there is some middlebox modifying the SDP in a way that 
>>> breaks ICE, it is safest to assume that ICE might not work. As such it 
>>> should not be used at all. ICE was simply not meant to operate in such 
>>> scenarios.
>> I am not arguing against the mismatch rules as such, I am 
>> just wondering if there are technical reasons why they can't 
>> be done per media.
>>
>>> Also, in most scenarios where the SDP media information is modified, it 
>>> is most probably that all medias will be modified in a way that would 
>>> make them ineligible for ICE: robably the original medias (those NOT coming from the application 
>>> server) would go through some kind of media proxying device anyway. 
>>> Right?
>> Not necessarily. In my examples the media NOT 
>> generated/transcoded by the application server does not need 
>> to go through any media proxying device.
> 
> Also, chapter 9.1.1.3 allows ICE-per-stream when a new stream is added, so I see no reason why ICE-per-stream (ICEstream :) can't be used also in the beginning of the session.
> 
> Regards,
> 
> Christer
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 

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


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



From mmusic-bounces@ietf.org Mon Oct 29 09:56:16 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ImV5n-0007PG-Cd; Mon, 29 Oct 2007 09:55:47 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1ImV5l-0007OU-P0
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 29 Oct 2007 09:55:45 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ImV5l-0007OL-DV
	for mmusic@ietf.org; Mon, 29 Oct 2007 09:55:45 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ImV5k-0001MJ-IW
	for mmusic@ietf.org; Mon, 29 Oct 2007 09:55:45 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	EFF5A208A2; Mon, 29 Oct 2007 14:55:43 +0100 (CET)
X-AuditID: c1b4fb3c-af67dbb0000007e1-5c-4725e65f6db2
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	D2A8A20855; Mon, 29 Oct 2007 14:55:43 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Oct 2007 14:55:43 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] ICE with media streams without candidates
Date: Mon, 29 Oct 2007 14:55:42 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF02C80625@esealmw113.eemea.ericsson.se>
In-Reply-To: <4724FE3B.8040702@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] ICE with media streams without candidates
Thread-Index: AcgaMgBAp0jj6a4aTOq7Hrx9hb1u2AAAGSgA
References: <CA9998CD4A020D418654FCDEF4E707DF02A5D6FC@esealmw113.eemea.ericsson.se><200710221528.41180.remi.denis-courmont@nokia.com><CA9998CD4A020D418654FCDEF4E707DF02A8B9C8@esealmw113.eemea.ericsson.se><200710231528.52224.remi.denis-courmont@nokia.com>	<CA9998CD4A020D418654FCDEF4E707DF02ABE439@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF02BFD73A@esealmw113.eemea.ericsson.se>
	<4724FE3B.8040702@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Jonathan Rosenberg" <jdrosen@cisco.com>
X-OriginalArrivalTime: 29 Oct 2007 13:55:43.0785 (UTC)
	FILETIME=[660D2190:01C81A33]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
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>
Errors-To: mmusic-bounces@ietf.org


Hi Jonathan,=20

>This section does not in any way adding a new media stream=20
>that is not utilizing ICE. It simply says that you can add=20
>one and ICE processing for it begins when you do.

Yes, that is what I meant. You do ICE per-stream.

>To answer your original question, the reason we elected to=20
>make it all or nothing was because of the unpredictability of=20
>ICE through SBCs. For example an SBC that is not ICE-aware,=20
>adds a media stream, but allows ICE parameters through, is=20
>actually very likely to have some kind of firewalling=20
>behavior associated with it, that blocks the media stream=20
>unless it behaves the way it expects. So in the interests of=20
>reliability, ICE backs off whenever it sees anything=20
>resembling a non-ICE aware intermediary.

Even if the SBC does not add a media stream, it can still have such kind =
of firewalling behaviour.

>This is something that was discussed quite a bit previously=20
>and I don't see any reason to re-evaluate our previous=20
>decision on this.

I admit I am late, but I would really ask you to do that re-evalutation, =
if there are no technical reasons why it can't be done.

Yes, we can add some text talking about potential issues when all =
streams do not contain ICE candidates, but I still think we should allow =
such cases.

This has come up in 3GPP, where we currently are looking at ICE support =
when there are SBCs in the network.

Regards,

Christer






> Christer Holmberg wrote:
> > Hi,
> >=20
> >>>> Assume A calls B, and includes SDP with the ICE candidate=20
> >>>> attributes etc for each media stream.
> >>>> In the middle there is a B2BUA application server, which=20
> wants to=20
> >>>> add a stream towards B, so it modifies the SDP by adding=20
> an extra m=3D line.
> >>>> The application server, however, does not support ICE,=20
> so it does=20
> >>>> not include any candidate attributes.
> >>> We can probably agree that if there is something that=20
> modifies this=20
> >>> SDP even though it does not terminate the SIP session,=20
> anything can happen.
> >>> And probably nobody wants to start a SBC flame war here ;)
> >>>
> >>> As a developper, I would rather it had been per-media, or better=20
> >>> yet, a per-component process, because it would have been much=20
> >>> simpler to implement and integrate. There are however=20
> several valid=20
> >>> reasons why ICE is a SIP per-session process, as far as=20
> ICE is used with SIP.
> >>>
> >>> I can think of plenty of loopholes if one media has ICE,=20
> but not another one.
> >>> For instance, how would the UA know when to start sending=20
> media? But=20
> >>> most importantly, the decision to abort ICE when some=20
> inconsistency=20
> >>> is detected is all about maximizing backward compatibility with=20
> >>> existing setups. If there is some middlebox modifying the=20
> SDP in a=20
> >>> way that breaks ICE, it is safest to assume that ICE=20
> might not work.=20
> >>> As such it should not be used at all. ICE was simply not meant to=20
> >>> operate in such scenarios.
> >> I am not arguing against the mismatch rules as such, I am just=20
> >> wondering if there are technical reasons why they can't be=20
> done per=20
> >> media.
> >>
> >>> Also, in most scenarios where the SDP media information=20
> is modified,=20
> >>> it is most probably that all medias will be modified in a=20
> way that=20
> >>> would make them ineligible for ICE: robably the original medias=20
> >>> (those NOT coming from the application
> >>> server) would go through some kind of media proxying=20
> device anyway.=20
> >>> Right?
> >> Not necessarily. In my examples the media NOT=20
> generated/transcoded by=20
> >> the application server does not need to go through any=20
> media proxying=20
> >> device.
> >=20
> > Also, chapter 9.1.1.3 allows ICE-per-stream when a new=20
> stream is added, so I see no reason why ICE-per-stream=20
> (ICEstream :) can't be used also in the beginning of the session.
> >=20
> > Regards,
> >=20
> > Christer
> >=20
> >=20
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mmusic
> >=20
>=20
> --=20
> Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
> Cisco Fellow                                   Parsippany, NJ=20
> 07054-2711
> Cisco Systems
> jdrosen@cisco.com                              FAX:   (973) 952-5050
> http://www.jdrosen.net                         PHONE: (973) 952-5000
> http://www.cisco.com
>=20


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



From mmusic-bounces@ietf.org Mon Oct 29 09:59:44 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ImV9Y-0000aH-5H; Mon, 29 Oct 2007 09:59:40 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1ImV9X-0000a6-DL
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 29 Oct 2007 09:59:39 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ImV9X-0000Zw-1y
	for mmusic@ietf.org; Mon, 29 Oct 2007 09:59:39 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ImV9W-0001Wg-Dl
	for mmusic@ietf.org; Mon, 29 Oct 2007 09:59:38 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	CD0FE20403; Mon, 29 Oct 2007 14:59:37 +0100 (CET)
X-AuditID: c1b4fb3e-b2038bb0000007e1-2c-4725e7498b05
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	BEC872014C; Mon, 29 Oct 2007 14:59:37 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Oct 2007 14:59:37 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] ICE: Clarification question when full ICE communciate
	with	ICE lite and chooses host candidate
Date: Mon, 29 Oct 2007 14:59:31 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF02C8065E@esealmw113.eemea.ericsson.se>
In-Reply-To: <47250BB6.5000608@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] ICE: Clarification question when full ICE communciate
	with	ICE lite and chooses host candidate
Thread-Index: AcgaMzfokOrmeoSWR/S4LDU8iGo5NQAAGMfA
References: <CA9998CD4A020D418654FCDEF4E707DF02BC97B3@esealmw113.eemea.ericsson.se>
	<47250BB6.5000608@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Jonathan Rosenberg" <jdrosen@cisco.com>
X-OriginalArrivalTime: 29 Oct 2007 13:59:37.0516 (UTC)
	FILETIME=[F15DA6C0:01C81A33]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
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>
Errors-To: mmusic-bounces@ietf.org


Hi,

Thanks for the clarification!

So, does this mean that an UPDATE will be sent EVEN if HOST_CANDIDATE
was the default candidate and is then chosen to be used, since the SDP
address information does change?

INVITE c/m =3D local address (HOST_CANDIDATE)
UPDATE c/m =3D mapped address (HOST_CANDIDATE)

Regards,

Christer

=20

> -----Original Message-----
> From: Jonathan Rosenberg [mailto:jdrosen@cisco.com]=20
> Sent: 29. lokakuuta 2007 0:23
> To: Christer Holmberg
> Cc: mmusic@ietf.org
> Subject: Re: [MMUSIC] ICE: Clarification question when full=20
> ICE communciate with ICE lite and chooses host candidate
>=20
> inline.
>=20
> Christer Holmberg wrote:
> >=20
> > Hi,
> >=20
> > Assume the following scenario:
> >=20
> > - User A is located behind a NAT, and implements full ICE.
> >=20
> > - User A collects candidates, and send an INVITE
> >=20
> > - The call is received by an MGCF, implementing ICE lite.
> >=20
> > - User A starts doing connectivity checks, which the MGCF reply to=20
> > (being ICE lite, the MGCF does not generate checks itself)
> >=20
> > - User A detects that the HOST_CANDIDATE checks work, so it=20
> sends an=20
> > UPDATE and tells the MGCF that the HOST_CANDIDATE will be used. The=20
> > Local Address information will be in the c/m line.
> >=20
> >=20
> > Now, the MGCF will start sending media towards the Local=20
> Address. But,=20
> > since User A, and the Local Address, is behind the NAT, the=20
> media will=20
> > not reach User A.
>=20
> No, this is not what will happen. The candidate pair learned=20
> from the checks sent by A are based on the mapped address=20
> from the connectivity checks. Quoting fro 7.1.2.2.2:
>=20
> 7.1.2.2.2.  Constructing a Valid Pair
>=20
>     The agent constructs a candidate pair whose local candidate equals
>     the mapped address of the response, and whose remote=20
> candidate equals
>     the destination address to which the request was sent.
>=20
>=20
> -Jonathan R.
>=20
> --=20
> Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
> Cisco Fellow                                   Parsippany, NJ=20
> 07054-2711
> Cisco Systems
> jdrosen@cisco.com                              FAX:   (973) 952-5050
> http://www.jdrosen.net                         PHONE: (973) 952-5000
> http://www.cisco.com
>=20


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



From mmusic-bounces@ietf.org Mon Oct 29 11:11:05 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ImWFh-0005XR-OA; Mon, 29 Oct 2007 11:10:05 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1ImWFf-0005Um-Qk
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 29 Oct 2007 11:10:03 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ImWFf-0005Ue-Fu; Mon, 29 Oct 2007 11:10:03 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1ImWFf-0004WK-36; Mon, 29 Oct 2007 11:10:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id F2D262AC75;
	Mon, 29 Oct 2007 15:10:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1ImWFd-0001TL-Uz; Mon, 29 Oct 2007 11:10:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1ImWFd-0001TL-Uz@stiedprstage1.ietf.org>
Date: Mon, 29 Oct 2007 11:10:01 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action:draft-ietf-mmusic-ice-19.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>
Errors-To: mmusic-bounces@ietf.org

--NextPart

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


	Title           : Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols
	Author(s)       : J. Rosenberg
	Filename        : draft-ietf-mmusic-ice-19.txt
	Pages           : 119
	Date            : 2007-10-29

This document describes a protocol for Network Address Translator
(NAT) traversal for UDP-based multimedia sessions established with
the offer/answer model.  This protocol is called Interactive
Connectivity Establishment (ICE).  ICE makes use of the Session
Traversal Utilities for NAT (STUN) protocol and its extension,
Traversal Using Relay NAT (TURN).  ICE can be used by any protocol
utilizing the offer/answer model, such as the Session Initiation
Protocol (SIP).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-ice-19.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-19.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-19.txt".

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

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

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

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

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

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

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

Content-Type: text/plain
Content-ID: <2007-10-29110857.I-D\@ietf.org>


--OtherAccess--

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

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

--NextPart--





From mmusic-bounces@ietf.org Mon Oct 29 11:28:32 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ImWWf-000143-LM; Mon, 29 Oct 2007 11:27:37 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1ImWWe-00013q-G6
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 29 Oct 2007 11:27:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ImWWe-00013i-6R
	for mmusic@ietf.org; Mon, 29 Oct 2007 11:27:36 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ImWWX-0004mY-7A
	for mmusic@ietf.org; Mon, 29 Oct 2007 11:27:36 -0400
X-IronPort-AV: E=Sophos;i="4.21,343,1188792000"; d="scan'208";a="79060957"
Received: from unknown (HELO 306181ANEX3.global.avaya.com) ([135.9.6.104])
	by co300216-co-outbound.avaya.com with ESMTP; 29 Oct 2007 11:27:10 -0400
Received: from [135.148.69.131] ([135.148.69.131]) by
	306181ANEX3.global.avaya.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Oct 2007 09:26:30 -0600
Message-ID: <4725FB6B.8080506@avaya.com>
Date: Mon, 29 Oct 2007 09:25:31 -0600
From: "Robert R. Gilman" <rrg@avaya.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens.com>
Subject: Re: [MMUSIC] Symmetry breaking for DTLS-SRTP
References: <20071024165908.CDB1B33C28@delta.rtfm.com>
	<0D5F89FAC29E2C41B98A6A762007F5D037D5E4@GBNTHT12009MSX.gb002.siemens.net>
	<47224C8B.2050804@avaya.com>
	<0D5F89FAC29E2C41B98A6A762007F5D037D850@GBNTHT12009MSX.gb002.siemens.net>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D037D850@GBNTHT12009MSX.gb002.siemens.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Oct 2007 15:26:30.0615 (UTC)
	FILETIME=[149D6E70:01C81A40]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6a45e05c1e4343200aa6b327df2c43fc
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>
Errors-To: mmusic-bounces@ietf.org

My example shows the same thing: the Controller has to (at least) turn
"a=setup: actpass" into "a=setup: active" in one direction and "a=setup:
passive" in the other.  It could also "harmonize" codec parameters, etc.,
(possibly the reason the Controller bothered to intervene in the first
place.)  I don't think anyone would call it "pretty", but I can't say
someone won't find a good use for it.  The "solution" costs us almost
nothing if the Controller is absent: the endpoint always responds to an
offer with "a=setup:active" unless it has a good reason not to  The
typical endpoint will know how to act as either a client and a server,
and those that can't (e.g., an answer-only endpoint that demands to
be "active") must say so in their offers.  As you point out, it's
the job of the Controller to make sense of what it's created (if it
can.)
-Bob
----------------------------------------------------
Bob Gilman       rrg@avaya.com      +1 303 538 3868

Elwell, John wrote:
> OK, but to take my example of SDP capability negotiation, the controller
> would have to resolve it somehow, i.e., for each leg, select a
> configuration that is compatible with one of the proposed configurations
> from Alice and with one of the proposed configurations from Bob, and
> include this in the answers to Alice and Bob respectively. Ugly.
> 
> John
> 
> 
>>-----Original Message-----
>>From: Robert R. Gilman [mailto:rrg@avaya.com] 
>>Sent: 26 October 2007 21:23
>>To: Elwell, John; Eric Rescorla
>>Cc: mmusic@ietf.org
>>Subject: Re: [MMUSIC] Symmetry breaking for DTLS-SRTP
>>
>>John-
>>I think such flows can arise from a case in which one party, 
>>rather than
>>the controller, intiates the call.  But, as you point out, 
>>the controller
>>cannot blindly pass one offer through to serve as an answer; it must
>>modify the SDP in some cases.  For DTLS, in accord with the rules in
>>section 4.1 of RFC 4145, the offeror, assuming it can act as either a
>>server or a client, should use
>>	a=setup-attr: actpass
>>and should be prepared to receive a client_hello before it 
>>receives the
>>answer.  In the two-party case, the answer would normally include
>>	a=setup: active
>>and the answerer would go ahead and send the client_hello in the media
>>path.  This permits the controller (indeed, it requires the 
>>controller)
>>to break the symmetry by modifying the SDP, hence we don't need any
>>random numbers (which remind me too much of the H.245 master/slave
>>resolution scheme).  If, for some reason, an endpoint can only act as
>>a server, say, then in must send passive, and the controller 
>>can adjust
>>which end it selects to be active - or it can refuse the call (or
>>terminate the media on a media server) if both endpoints insist on the
>>same role.  I believe this scheme is compatible with Dan Wing's draft:
>>draft-wing-sip-identity-media-00.
>>
>>The exchange might look something like this:
>>
>>Alice                        Controller                        Bob
>>------------------------------------------------------------------
>>INVITE + Offer(actpass) ->
>>                                     INVITE ->
>>                                              <- OK + Offer(actpass)
>>           <- OK + Answer(active)    ACK + Answer(passive) ->
>>       <- - - - - - - - - - - client_hello - - - - - - - - - -
>>ACK ->
>>                               ....
>>Does this make sense?
>>-Bob
>>----------------------------------------------------
>>Bob Gilman       rrg@avaya.com      +1 303 538 3868
>>
>>Elwell, John wrote:
>>
>>>Ekr,
>>>
>>>I don't have a problem with the solution, but I am doubtful 
>>
>>whether it
>>
>>>is a problem we need to solve. The case illustrated is based on the
>>>assumption that offer and answer are symmetrical, in the 
>>
>>sense that an
>>
>>>offer can be reused as an answer (and vice versa). In this case the
>>>offer from A becomes an answer to B and vice versa. There are two
>>>extensions to SDP that I am aware of that break this, and 
>>
>>therefore any
>>
>>>controller that misuses SDP in this way will screw things up. One
>>>example is the key management extension when used to carry MIKEY,
>>>because a MIKEY request (which always goes in the offer) is very
>>>different in syntax and semantics from a MIKEY response 
>>
>>(which always
>>
>>>goes in the answer). Of course, this will not apply when 
>>
>>using DTLS-SRTP
>>
>>>as the means of key management. The second example is the 
>>
>>SDP capability
>>
>>>negotiation draft, which certainly will be applicable with 
>>
>>DTLS-SRTP.
>>
>>>I am not aware of how the particular flow shown would 
>>
>>arise. It is not
>>
>>>documented in RFC 3725 (3PCC). It has similarities to flow II in RFC
>>>3725, which the RFC does not recommend. The other 3PCC 
>>
>>flows in RFC 3725
>>
>>>do not mix up offers and answers in this way.
>>>
>>>I also questioned the need for the solution in ICE, but as it came
>>>virtually for free, it was not worth arguing about.
>>>
>>>If we continue this discussion, I would suggest we stick to 
>>
>>the MMUSIC
>>
>>>list rather than AVT.
>>>
>>>John
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: Eric Rescorla [mailto:ekr@networkresonance.com] 
>>>>Sent: 24 October 2007 17:59
>>>>To: avt@ietf.org; mmusic@ietf.org
>>>>Subject: [MMUSIC] Symmetry breaking for DTLS-SRTP
>>>>
>>>>TLS (and by extension) DTLS-SRTP requires unambiguity about 
>>
>>which side
>>
>>>>is to be the client and which is the server. This isn't an issue of
>>>>credentials--DTLS-SRTP assumes that each side can take either
>>>>role--it's just that TLS requires that one side initiate the
>>>>handshake. My original intention had been to make this 
>>
>>conditional on
>>
>>>>which side was the offerer and which was the answerer, but 
>>
>>JDR pointed
>>
>>>>out in ORD that there are cases involving 3PCC where it's not
>>>>unambiguous which is which.
>>>>
>>>>Here's the paradigmatic case, transcribed from a phone call with
>>>>JDR (so any errors are my fault):
>>>>
>>>>
>>>>Alice                        Controller                        Bob
>>>>------------------------------------------------------------------
>>>>INVITE + Offer ->
>>>>                             INVITE ->
>>>>                                                    <- OK + Offer
>>>>                     <- OK + Answer                              
>>>>                             ACK + Answer ->
>>>>ACK ->
>>>>
>>>>Because the controller sends an INVITE with no offer, Bob is the
>>>>offererer, and of course Alice is. So, you can't use offerer
>>>>or answerer to break symmetry. 
>>>>
>>>>This same problem occurs with ICE, which uses a random tiebreaker
>>>>value in the ICE messages to determine which side should take
>>>>which role (controlling vs. controlled). This works because
>>>>in ICE both sides are trying to transmit so they quickly 
>>>>detect conflicts. Unfortunately, in DTLS-SRTP, the server just
>>>>waits so if the rule we adopt allows both sides to think they
>>>>are the server then we get deadlock. The above exchange 
>>>>shows how both sides can be offerer so clearly we can't have
>>>>offerer=server, but it seems that we could make a new exchange
>>>>where both sides are answerer in which case we can't have
>>>>offerer=client. JDR tells me that we don't have an actual
>>>>use case like this yet but I would not want to count on that
>>>>unless we're very sure.
>>>>
>>>>We could use exactly the trick that ICE uses but that requires
>>>>modifying DTLS to make the server send messages unprompted.
>>>>I don't think that's necessary here because we can break
>>>>the tie in the SDP where we announce the DTLS-SRTP capability
>>>>(however that's done).
>>>>
>>>>The basic principle is this:
>>>>1. Each side generates a random tiebreaker value T.
>>>>2. In the SDP offer/answer, he indicates whether he wishes
>>>>  to be the TLS client or server (if you're the offerer
>>>>  you SHOULD ask to be the server since that's faster, 
>>>>  and vice versa).
>>>>3. If each side sees a consistent view (one client, one 
>>>>  server) then that is what is used.
>>>>4. If the views are inconsistent, then the side with the
>>>>  higher T is be the client.
>>>>
>>>>This is basically the same algorithm as used with ICE, just
>>>>moving the tiebreaker into the SDP.
>>>>
>>>>Does anyone see a problem with this?
>>>>
>>>>-Ekr
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>_______________________________________________
>>>>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 Mon Oct 29 15:16:17 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ima4s-0002Qv-H4; Mon, 29 Oct 2007 15:15:10 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1Ima4l-0002KJ-G8
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 29 Oct 2007 15:15:03 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ima4k-0002HL-Pe; Mon, 29 Oct 2007 15:15:02 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1Ima4k-0007n8-Ae; Mon, 29 Oct 2007 15:15:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id F1411175CD;
	Mon, 29 Oct 2007 19:15:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Ima4j-00062h-Gs; Mon, 29 Oct 2007 15:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Ima4j-00062h-Gs@stiedprstage1.ietf.org>
Date: Mon, 29 Oct 2007 15:15:01 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D
	ACTION:draft-ietf-mmusic-sdp-capability-negotiation-07.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>
Errors-To: mmusic-bounces@ietf.org

--NextPart

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

	Title		: SDP Capability Negotiation
	Author(s)	: F. Andreasen
	Filename	: draft-ietf-mmusic-sdp-capability-negotiation-07.txt
	Pages		: 79
	Date		: 2007-10-29
	
The Session Description Protocol (SDP) was intended for describing 
   multimedia sessions for the purposes of session announcement, 
   session invitation, and other forms of multimedia session 
   initiation. SDP was not intended to provide capability indication or 
   capability negotiation, however over the years, SDP has seen 
   widespread adoption and as a result it has been gradually extended 
   to provide limited support for these, notably in the form of the 
   offer/answer model defined in RFC 3264. SDP and its current 
   extensions do not define how to negotiate one or more alternative 
   transport protocols (e.g. RTP profiles) or attributes. This makes it 
   difficult to deploy new RTP profiles such as secure RTP or RTP with 
   RTCP-based feedback, negotiate use of different security keying 
   mechanisms, etc. It also presents problems for some forms of media 
   negotiation.  

   The purpose of this document is to address these shortcomings by 
   extending SDP with capability negotiation parameters and associated 
   offer/answer procedures to use those parameters in a backwards 
   compatible manner.  

   The document defines a general SDP Capability Negotiation framework. 
   It also specifies how to provide attributes and transport protocols 
   as capabilities and negotiate them using the framework. Extensions 
   for other types of capabilities (e.g. media types and media formats) 
   may be provided in other documents.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-capability-negotiation-07.txt

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

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

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

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

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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-sdp-capability-negotiation-07.txt

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

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


--OtherAccess--

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

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

--NextPart--






From mmusic-bounces@ietf.org Mon Oct 29 16:29:44 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ImbDV-0005SV-DA; Mon, 29 Oct 2007 16:28:09 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1ImbDU-0005SP-9x
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 29 Oct 2007 16:28:08 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ImbDT-0005SG-VP
	for mmusic@ietf.org; Mon, 29 Oct 2007 16:28:08 -0400
Received: from audl952.usa.alcatel.com ([143.209.238.159])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ImbDT-00052y-Cd
	for mmusic@ietf.org; Mon, 29 Oct 2007 16:28:07 -0400
Received: from srsdmail01.PVNS.COM (mail.pvnetsolutions.com [128.251.100.16])
	by audl952.usa.alcatel.com (ALCANET) with ESMTP id l9TKS0No007644;
	Mon, 29 Oct 2007 14:28:00 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] Re: RTSP 2.0: [ 1701558 ] Pause response to live streams
Date: Mon, 29 Oct 2007 13:28:09 -0700
Message-ID: <758B5A159B385447B4F950DE72D7D7AD01AAC611@srsdmail01.PVNS.COM>
In-Reply-To: <4725ACD6.90100@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] Re: RTSP 2.0: [ 1701558 ] Pause response to live streams
Thread-Index: AcgaE3GRy+xinNlPSxOBJi913ZuaFAASnAtA
References: <4d0605c20710261537x240f6ac0xc993fb0e834700d6@mail.gmail.com>
	<4725ACD6.90100@ericsson.com>
From: "Mike Severa" <severa@pvnetsolutions.com>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>,
	"Joseph Pallas" <pallas@cs.stanford.edu>
X-Scanned-By: MIMEDefang 2.51 on 143.209.238.34
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
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>
Errors-To: mmusic-bounces@ietf.org

While this may again be something slightly outside the domain of RTSP,
I'll mention it anyway because it may be relevant for this discussion..

I would argue that it is possible to mix content that has different
properties in this regard within a single session. One could always
argue that if that were so then additional SDP should be required (even
if all that changed were this property). However, I could envision
scenarios where the client may not be the one requesting/controlling
this kind of multiplexing and as such there would be nothing but RTSP to
rely on wrt signalling (i.e., at PAUSE, PLAY time). Whether RTSP needs
to provide support for a use case in which it may not be the primary
means of session control (at least related to this very specific
behavior) is an entirely different (and valid) question.=20

Again, I'm not sure of the relevance of this other than it relates to
the behavior and signalling associated with the content properties under
discussion in this thread. The use cases will exist imho, whether they
are more appropriately supported by RTSP or some other means is unclear.

Thanks,

Mike


-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]=20
Sent: Monday, October 29, 2007 2:50 AM
To: Joseph Pallas
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] Re: RTSP 2.0: [ 1701558 ] Pause response to live
streams

Joseph Pallas skrev:
>> To me it should indicate the point the server is ceasing to deliver=20
>> media on. Also the live media have some time line. Either expressed=20
>> in UTC or in NPT since session start. What ever is used needs to be=20
>> reported. I don't think "now-" would be particular good answer. For=20
>> that reason a clearer text on this would be good.
>=20
> A simple way to do that is to say that "now" can only be used in=20
> requests, not in responses.
>=20
>> However, this leads me to another issue related to the content being=20
>> played back. It might be time to be more explicit about the content=20
>> properties related to playback.
> ...
>> However, my question is: Should we define a new SDP attribute that=20
>> expresses the contents major properties to allow RTSP clients to know

>> what to handle?
>=20
> It might be wise to separate that into two questions: (1) should there

> be a way to express these properties, and (2) should the properties be

> expressed in SDP or in RTSP itself.  I'm kind of biased against SDP=20
> here, because it is generally information about how to interpret the=20
> stream, not how to control it.
>=20

Hi Joe,

Yes, you are right that it should be split into two questions. Regarding
number two. I agree that we should be as explicit as possible and where
it is suitable. I agree that it is good that we express as much as
possible in RTSP. However, that will create issues. First it makes it
problematic to do optimized pipelined setups unless the client knows
these properties before sending its requests. Secondly, I would notice
that at least most what at least I consider are actually properties of
the content rather than the control session and therefore belongs in the
content description which SDP is one protocol instance of. This of
course leads to the interesting question if one should indicate it in
only one place or both for covering all potential cases?

cheers

Magnus Westerlund

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


_______________________________________________
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 Mon Oct 29 22:17:23 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Imgcq-0000cE-Hs; Mon, 29 Oct 2007 22:14:40 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1Imgco-0000bz-8W
	for mmusic-confirm+ok@megatron.ietf.org; Mon, 29 Oct 2007 22:14:38 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Imgcn-0000bq-T6
	for mmusic@ietf.org; Mon, 29 Oct 2007 22:14:37 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Imgcn-0007Ke-CD
	for mmusic@ietf.org; Mon, 29 Oct 2007 22:14:37 -0400
X-IronPort-AV: E=Sophos;i="4.21,345,1188792000"; d="scan'208";a="74953148"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 29 Oct 2007 21:49:18 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l9U1nICk026629; 
	Mon, 29 Oct 2007 21:49:18 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l9U1nABI000422; 
	Tue, 30 Oct 2007 01:49:14 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Oct 2007 21:49:10 -0400
Received: from [10.82.211.73] ([10.82.211.73]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 29 Oct 2007 21:49:09 -0400
Message-ID: <47268DAF.2080600@cisco.com>
Date: Mon, 29 Oct 2007 21:49:35 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] ICE: Clarification question when full ICE communciate
	with	ICE lite and chooses host candidate
References: <CA9998CD4A020D418654FCDEF4E707DF02BC97B3@esealmw113.eemea.ericsson.se>
	<47250BB6.5000608@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF02C8065E@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF02C8065E@esealmw113.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 30 Oct 2007 01:49:10.0187 (UTC)
	FILETIME=[10A7B7B0:01C81A97]
X-TM-AS-Product-Ver: SMEX-8.0.0.1181-5.000.1023-15508.000
X-TM-AS-Result: No--23.611900-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3718; t=1193708958;
	x=1194572958; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20[MMUSIC]=20ICE=3A=20Clarification=20question=20when=2
	0full=20ICE=20communciate=0A=20with=09ICE=20lite=20and=20chooses=20host=20
	candidate |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.com>;
	bh=WxnbcRrv8KMwkl65yx52mWphmfX2uWbJ5Q1H2/vtfZk=;
	b=dtGLjktAyTeG+gsaeu29E4cz6Hp7K489x4FMEtYkAxMVhztsjgWtv6dI50FXsA5vHUX/OyoB
	JYZEsdu3XfMdHYvn1CMlD/PcfYrBS+1ntK395SM4rTpij/hO1SPnMBGX;
Authentication-Results: rtp-dkim-1; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
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>
Errors-To: mmusic-bounces@ietf.org

No, an UPDATE is sent only if the default does not match the selected 
candidate:

(Section 8.1.2)

o  Once the state of each check list is Completed:

       *  The agent sets the state of ICE processing overall to
          Completed.

       *  If an agent is controlling, it examines the highest priority
          nominated candidate pair for each component of each media
          stream.  If any of those candidate pairs differ from the
          default candidate pairs in the most recent offer/answer
          exchange, the controlling agent MUST generate an updated offer
          as described in Section 9.  If the controlling agent is using
          an aggressive nomination algorithm, this may result in several
          updated offers as the pairs selected for media change.  An
          agent MAY delay sending the offer for a brief interval (one
          second is RECOMMENDED) in order to allow the selected pairs to
          stabilize.


-Jonathan R.


Christer Holmberg wrote:
> Hi,
> 
> Thanks for the clarification!
> 
> So, does this mean that an UPDATE will be sent EVEN if HOST_CANDIDATE
> was the default candidate and is then chosen to be used, since the SDP
> address information does change?
> 
> INVITE c/m = local address (HOST_CANDIDATE)
> UPDATE c/m = mapped address (HOST_CANDIDATE)
> 
> Regards,
> 
> Christer
> 
>  
> 
>> -----Original Message-----
>> From: Jonathan Rosenberg [mailto:jdrosen@cisco.com] 
>> Sent: 29. lokakuuta 2007 0:23
>> To: Christer Holmberg
>> Cc: mmusic@ietf.org
>> Subject: Re: [MMUSIC] ICE: Clarification question when full 
>> ICE communciate with ICE lite and chooses host candidate
>>
>> inline.
>>
>> Christer Holmberg wrote:
>>> Hi,
>>>
>>> Assume the following scenario:
>>>
>>> - User A is located behind a NAT, and implements full ICE.
>>>
>>> - User A collects candidates, and send an INVITE
>>>
>>> - The call is received by an MGCF, implementing ICE lite.
>>>
>>> - User A starts doing connectivity checks, which the MGCF reply to 
>>> (being ICE lite, the MGCF does not generate checks itself)
>>>
>>> - User A detects that the HOST_CANDIDATE checks work, so it 
>> sends an 
>>> UPDATE and tells the MGCF that the HOST_CANDIDATE will be used. The 
>>> Local Address information will be in the c/m line.
>>>
>>>
>>> Now, the MGCF will start sending media towards the Local 
>> Address. But, 
>>> since User A, and the Local Address, is behind the NAT, the 
>> media will 
>>> not reach User A.
>> No, this is not what will happen. The candidate pair learned 
>> from the checks sent by A are based on the mapped address 
>> from the connectivity checks. Quoting fro 7.1.2.2.2:
>>
>> 7.1.2.2.2.  Constructing a Valid Pair
>>
>>     The agent constructs a candidate pair whose local candidate equals
>>     the mapped address of the response, and whose remote 
>> candidate equals
>>     the destination address to which the request was sent.
>>
>>
>> -Jonathan R.
>>
>> -- 
>> Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
>> Cisco Fellow                                   Parsippany, NJ 
>> 07054-2711
>> Cisco Systems
>> jdrosen@cisco.com                              FAX:   (973) 952-5050
>> http://www.jdrosen.net                         PHONE: (973) 952-5000
>> http://www.cisco.com
>>
> 

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


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



From mmusic-bounces@ietf.org Tue Oct 30 13:41:13 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Imv3j-0006gI-IC; Tue, 30 Oct 2007 13:39:23 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1Imv3i-0006cb-GY
	for mmusic-confirm+ok@megatron.ietf.org; Tue, 30 Oct 2007 13:39:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Imv3i-0006cR-6t
	for mmusic@ietf.org; Tue, 30 Oct 2007 13:39:22 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Imv3h-00051N-0M
	for mmusic@ietf.org; Tue, 30 Oct 2007 13:39:22 -0400
X-IronPort-AV: E=Sophos;i="4.21,348,1188802800"; d="scan'208";a="244557482"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 30 Oct 2007 10:39:20 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l9UHdKtH031841; 
	Tue, 30 Oct 2007 10:39:20 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l9UHcwU4015376;
	Tue, 30 Oct 2007 17:39:19 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Oct 2007 13:39:08 -0400
Received: from [161.44.174.216] ([161.44.174.216]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Oct 2007 13:39:08 -0400
Message-ID: <47276C3C.1000902@cisco.com>
Date: Tue, 30 Oct 2007 13:39:08 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF MMUSIC WG <mmusic@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 30 Oct 2007 17:39:08.0553 (UTC)
	FILETIME=[C6542790:01C81B1B]
X-TM-AS-Product-Ver: SMEX-8.0.0.1181-5.000.1023-15514.002
X-TM-AS-Result: No--12.553900-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2098; t=1193765960;
	x=1194629960; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20draft-ietf-mmusic-file-transfer-mech-04
	|Sender:=20; bh=fuAidU8k/AJ6gNK2Y+grUzm6w/c9faQlgxjmel/Smtw=;
	b=pob6Kwd3mEAnSpmt4zYL1dWYyfONkRx1T8DJMGbSvFBs5aProvbYqMEF0Bmj2KHN7c8cDI9D
	6/5Y4FEhHGbYLFUOPBWAWoBjNX6bCfbvOTPlqPyYD3mUj98XpwS9qwl+lkq7e9WWQx1RqxVTWu
	kt/BRCfrABw4IXDqZhAdVdZs0=;
Authentication-Results: sj-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: Miguel Garcia <Miguel.Garcia@nsn.com>
Subject: [MMUSIC] Re: draft-ietf-mmusic-file-transfer-mech-04
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>
Errors-To: mmusic-bounces@ietf.org

I started reviewing this version with the expectation that all issues 
were now resolved. But as I started thinking about the mechanism for 
handling subsequent o/a when no new transfer is required, and began to 
see potential problems - some new ones and some that have been there.

First, 4975 still is operable here, right? (This just provides layered 
behavior on top of that.) That means that the o/a rules for 4975 still 
apply. IIUC this means that in a subsequent o/a (after previously 
negotiating an MSRP session) its possible that the connection will be 
replaced with a new one. In fact, if the new o/a is in the opposite 
direction, its mandated that a new connection be made in the opposite 
direction.

(I just posted a question to SIMPLE about how MSRP is supposed to behave 
in this case.)

Now, getting on to the draft, the file-transfer-id is dealing with 
instances of file transfers, not of MSRP sessions. I *assume* that a 
file transfer will be completed on one connection - that it won't be 
split across multiple connections - or is that a bad assumption? (I 
think if it can't be completed in a single connection then it will need 
to be restarted, perhaps with a file-range.)

So, suppose a file transfer is started, and then before it completes 
there is need to send a new o/a. (Perhaps because of session timer.) 
This could conceivably result in a new MSRP session being established in 
the other direction. Does that cause the file transfer to abort in the 
middle? Or does the file transfer continue on the original connection 
until it is complete or until the connection fails?

If the transfer continues until complete, then a clean way to handle a 
new offer that doesn't want to initiate a new transfer would simply be 
to set the port=0 in the m-line, avoiding creating a new connection that 
isn't needed.

But if the old connection must be torn down before transfer is complete, 
then we have a bigger problem.

I've got some lesser issues, but will defer discussing them until this 
is clarified.

	Thanks,
	Paul


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



From mmusic-bounces@ietf.org Tue Oct 30 15:35:23 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Imwqz-00088q-QX; Tue, 30 Oct 2007 15:34:21 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1ImwpE-0005lS-Mk
	for mmusic-confirm+ok@megatron.ietf.org; Tue, 30 Oct 2007 15:32:32 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ImwpE-0005lF-8b
	for mmusic@ietf.org; Tue, 30 Oct 2007 15:32:32 -0400
Received: from zcars04f.nortel.com ([47.129.242.57])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ImwpD-0006i2-IT
	for mmusic@ietf.org; Tue, 30 Oct 2007 15:32:32 -0400
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l9UJWTW07278; Tue, 30 Oct 2007 19:32:29 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC]
	I-D	ACTION:draft-ietf-mmusic-sdp-capability-negotiation-07.txt
Date: Tue, 30 Oct 2007 14:31:55 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF12DC42D0@zrc2hxm0.corp.nortel.com>
In-Reply-To: <E1Ima4j-00062h-Gs@stiedprstage1.ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC]
	I-D	ACTION:draft-ietf-mmusic-sdp-capability-negotiation-07.txt
Thread-Index: AcgaYS1HArvV/j+FSLqDNVfdvG1GOwAyVWGA
References: <E1Ima4j-00062h-Gs@stiedprstage1.ietf.org>
From: "Francois Audet" <audet@nortel.com>
To: <mmusic@ietf.org>, "Flemming Andreasen" <fandreas@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003
Cc: 
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>
Errors-To: mmusic-bounces@ietf.org

Hi Flemming,

There seem to be some inconsistencies with the Best-Effort example in
section 3.2
and the one in section 4.1, which appears to be identical.

Most of the text and SDP is the same, but with some key differences:

- In the first example, the tcap includes RTP/SAVP only (the m-line has
RTP/AVP), but
  in the second example, the tcap includes both RTP/SAVP and RTP/AVP
(even if m-line
  is also RTP/AVP). Is this a typo? Which one is correct?

- In the first example, there is only one Offer/Answer exchange. In the
second
  example, there is a second-round of Offer/Answer exchange to "lock-it
down" to
  a plain SAVP offer for the benefits of middle boxes. Again, which one
is correct?
  PS: Personally, I prefer the first one. I don't see why the we would
need a second
  one for middleboxes, and the single offer/answer should work. And from
a philosophical
  perspective, I don't think we should complicate unduly the protocols
just for the=20
  benefits of sub-standard middleboxes...

Can you clarify?

> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20
> Sent: Monday, October 29, 2007 12:15
> To: i-d-announce@ietf.org
> Cc: mmusic@ietf.org
> Subject: [MMUSIC] I-D=20
> ACTION:draft-ietf-mmusic-sdp-capability-negotiation-07.txt
>=20
> A New Internet-Draft is available from the on-line=20
> Internet-Drafts directories.
> This draft is a work item of the Multiparty Multimedia=20
> Session Control Working Group of the IETF.
>=20
> 	Title		: SDP Capability Negotiation
> 	Author(s)	: F. Andreasen
> 	Filename	:=20
> draft-ietf-mmusic-sdp-capability-negotiation-07.txt
> 	Pages		: 79
> 	Date		: 2007-10-29
> =09
> The Session Description Protocol (SDP) was intended for describing=20
>    multimedia sessions for the purposes of session announcement,=20
>    session invitation, and other forms of multimedia session=20
>    initiation. SDP was not intended to provide capability=20
> indication or=20
>    capability negotiation, however over the years, SDP has seen=20
>    widespread adoption and as a result it has been gradually extended=20
>    to provide limited support for these, notably in the form of the=20
>    offer/answer model defined in RFC 3264. SDP and its current=20
>    extensions do not define how to negotiate one or more alternative=20
>    transport protocols (e.g. RTP profiles) or attributes.=20
> This makes it=20
>    difficult to deploy new RTP profiles such as secure RTP or=20
> RTP with=20
>    RTCP-based feedback, negotiate use of different security keying=20
>    mechanisms, etc. It also presents problems for some forms of media=20
>    negotiation. =20
>=20
>    The purpose of this document is to address these shortcomings by=20
>    extending SDP with capability negotiation parameters and=20
> associated=20
>    offer/answer procedures to use those parameters in a backwards=20
>    compatible manner. =20
>=20
>    The document defines a general SDP Capability Negotiation=20
> framework.=20
>    It also specifies how to provide attributes and transport=20
> protocols=20
>    as capabilities and negotiate them using the framework. Extensions=20
>    for other types of capabilities (e.g. media types and=20
> media formats)=20
>    may be provided in other documents.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-capa
> bility-negotiation-07.txt
>=20
> To remove yourself from the I-D Announcement list, send a=20
> message to i-d-announce-request@ietf.org with the word=20
> unsubscribe in the body of the message.=20
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>=20
> Internet-Drafts are also available by anonymous FTP. Login=20
> with the username "anonymous" and a password of your e-mail=20
> address. After logging in, type "cd internet-drafts" and then=20
> "get draft-ietf-mmusic-sdp-capability-negotiation-07.txt".
>=20
> A list of Internet-Drafts directories can be found in=20
> http://www.ietf.org/shadow.html or=20
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
> Internet-Drafts can also be obtained by e-mail.
>=20
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE=20
> /internet-drafts/draft-ietf-mmusic-sdp-capability-negotiation-07.txt".
> =09
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant=20
> mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>=20
> Below is the data which will enable a MIME compliant mail=20
> reader implementation to automatically retrieve the ASCII=20
> version of the Internet-Draft.
>=20


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



From mmusic-bounces@ietf.org Tue Oct 30 16:53:43 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Imy3a-0001u4-Co; Tue, 30 Oct 2007 16:51:26 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1Imy3Y-0001tl-VT
	for mmusic-confirm+ok@megatron.ietf.org; Tue, 30 Oct 2007 16:51:24 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Imy3Y-0001qI-In; Tue, 30 Oct 2007 16:51:24 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1Imy3Y-00022e-8s; Tue, 30 Oct 2007 16:51:24 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 2A37A2ACE0;
	Tue, 30 Oct 2007 20:50:54 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Imy33-0001fl-UG; Tue, 30 Oct 2007 16:50:53 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1Imy33-0001fl-UG@stiedprstage1.ietf.org>
Date: Tue, 30 Oct 2007 16:50:53 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: mmusic chair <mmusic-chairs@tools.ietf.org>,
	Internet Architecture Board <iab@iab.org>,
	mmusic mailing list <mmusic@ietf.org>,
	RFC Editor <rfc-editor@rfc-editor.org>
Subject: [MMUSIC] Protocol Action: 'Interactive Connectivity 
 Establishment (ICE): A Protocol for Network Address Translator 
 (NAT) Traversal for Offer/Answer Protocols' to Proposed Standard 
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>
Errors-To: mmusic-bounces@ietf.org

The IESG has approved the following document:

- 'Interactive Connectivity Establishment (ICE): A Protocol for Network 
   Address Translator (NAT) Traversal for Offer/Answer Protocols '
   <draft-ietf-mmusic-ice-19.txt> as a Proposed Standard

This document is the product of the Multiparty Multimedia Session Control 
Working Group. 

The IESG contact persons are Cullen Jennings and Jon Peterson.

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

         Technical Summary
This document defines a protocol for Network Address Translator (NAT)
traversal for multimedia sessions established with the offer/answer
model.  This protocol is called Interactive Connectivity Establishment
(ICE).  ICE makes use of the Session Traversal Utilities for NAT (STUN)
protocol and its extension, Traversal Using Relay NAT (TURN).  ICE can
be used by any protocol utilizing the offer/answer model, such as the
Session Initiation Protocol (SIP).

          Working Group Summary
The MMUSIC Working Group has consensus to publish this document as a
Proposed Standard.

          Document Quality
Previous versions of this protocol have been implemented. A number of
implementers have indicated plans to support this protocol once
published.

      Personnel
The Document Shepherd is Jean-Francois Mule, and the Responsible Area
Director is Cullen Jennings.


Note to RFC Editor
 
Please change the header so that it obsoletes both 4091 and 4092.
OLD
     Obsoletes: RFC 4091
NEW
     Obsoletes: RFC 4091, 4092



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



From mmusic-bounces@ietf.org Tue Oct 30 22:13:41 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1In32q-0000Jo-4v; Tue, 30 Oct 2007 22:11:00 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1In32o-0000JR-2x
	for mmusic-confirm+ok@megatron.ietf.org; Tue, 30 Oct 2007 22:10:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1In32n-0000JJ-BB
	for mmusic@ietf.org; Tue, 30 Oct 2007 22:10:57 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1In32g-0002hX-P6
	for mmusic@ietf.org; Tue, 30 Oct 2007 22:10:57 -0400
X-IronPort-AV: E=Sophos;i="4.21,349,1188802800"; d="scan'208,217";a="13959260"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-4.cisco.com with ESMTP; 30 Oct 2007 19:10:45 -0700
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l9V2Ajfn011122; 
	Tue, 30 Oct 2007 19:10:45 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l9V2AYnM026777;
	Wed, 31 Oct 2007 02:10:44 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Oct 2007 19:10:36 -0700
Received: from [10.21.69.117] ([10.21.69.117]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Oct 2007 19:10:35 -0700
Message-ID: <4727E41A.3020803@cisco.com>
Date: Tue, 30 Oct 2007 22:10:34 -0400
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Thunderbird 1.5.0.13 (Windows/20070809)
MIME-Version: 1.0
To: Francois Audet <audet@nortel.com>
Subject: Re: [MMUSIC]
	I-D	ACTION:draft-ietf-mmusic-sdp-capability-negotiation-07.txt
References: <E1Ima4j-00062h-Gs@stiedprstage1.ietf.org>
	<1ECE0EB50388174790F9694F77522CCF12DC42D0@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF12DC42D0@zrc2hxm0.corp.nortel.com>
X-OriginalArrivalTime: 31 Oct 2007 02:10:36.0103 (UTC)
	FILETIME=[3988AD70:01C81B63]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=14746; t=1193796645;
	x=1194660645; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fandreas@cisco.com;
	z=From:=20Flemming=20Andreasen=20<fandreas@cisco.com>
	|Subject:=20Re=3A=20[MMUSIC]=20I-D=09ACTION=3Adraft-ietf-mmusic-sdp-capab
	ility-negotiation-07.txt |Sender:=20;
	bh=UPnIkJ1B5npcL2GxYlvAT5kjc431Q1Cg5LzdPADB/yo=;
	b=fmuDf4L6wCw3jeqm1dM0Daa3mocYfYGq4bdu5lB+qo5qpnjuqbraOBQ+3TKtYk5Nwa/Fn1Yb
	5TmnoIFLfSfdHEMrSRRst2r57n1fpFMyO8e6lBxuibDv5zmz3Eojr5O6;
Authentication-Results: sj-dkim-4; header.From=fandreas@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 07e9b4af03a165a413ec6e4d37ae537b
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>
Content-Type: multipart/mixed; boundary="===============1405317434=="
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.
--===============1405317434==
Content-Type: multipart/alternative;
	boundary="------------090805040005050200060409"

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



Francois Audet wrote:
> Hi Flemming,
>
> There seem to be some inconsistencies with the Best-Effort example in
> section 3.2
> and the one in section 4.1, which appears to be identical.
>
> Most of the text and SDP is the same, but with some key differences:
>
> - In the first example, the tcap includes RTP/SAVP only (the m-line has
> RTP/AVP), but
>   in the second example, the tcap includes both RTP/SAVP and RTP/AVP
> (even if m-line
>   is also RTP/AVP). Is this a typo? Which one is correct?
>   
They are both correct. The second example (4.1) includes an extra 
transport protocol capability (RTP/AVP), but doesn't use it in any of 
the potential configurations. In either case, if the potential 
configuration cannot be supported, the (least preferred) actual 
configuration, i.e. the RTP/AVP profile will be negotiated.

> - In the first example, there is only one Offer/Answer exchange. In the
> second
>   example, there is a second-round of Offer/Answer exchange to "lock-it
> down" to
>   a plain SAVP offer for the benefits of middle boxes. Again, which one
> is correct?
>   
They are both correct. The second offer/answer exchange is not required 
but recommended when you think there might be a middle-box in place.

The reason the two examples differ is that the 3.1. example is a very 
quick introduction that is trying to give an overview of the key 
concepts in the framework. The section 4 examples are a bit more 
elaborate, however they are all valid.

>   PS: Personally, I prefer the first one. 
I know :-)
> I don't see why the we would
> need a second
>   one for middleboxes, and the single offer/answer should work. And from
> a philosophical
>   perspective, I don't think we should complicate unduly the protocols
> just for the 
>   benefits of sub-standard middleboxes...
>
> Can you clarify?
>   
We've had that discussion before (look for thread titled "SDPCapNeg 
Issue #6: Second Offer/Answer exchange" on 6/25/07), and the consensus 
was that we did not want to require the second offer/answer exchange, 
however it is still useful to address some potential middlebox issues, 
so we wanted to include it as an option. ICE has a second offer/answer 
exchange (REQUIRED if I recall correctly).

Thanks

-- Flemming

>   
>> -----Original Message-----
>> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] 
>> Sent: Monday, October 29, 2007 12:15
>> To: i-d-announce@ietf.org
>> Cc: mmusic@ietf.org
>> Subject: [MMUSIC] I-D 
>> ACTION:draft-ietf-mmusic-sdp-capability-negotiation-07.txt
>>
>> 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 Capability Negotiation
>> 	Author(s)	: F. Andreasen
>> 	Filename	: 
>> draft-ietf-mmusic-sdp-capability-negotiation-07.txt
>> 	Pages		: 79
>> 	Date		: 2007-10-29
>> 	
>> The Session Description Protocol (SDP) was intended for describing 
>>    multimedia sessions for the purposes of session announcement, 
>>    session invitation, and other forms of multimedia session 
>>    initiation. SDP was not intended to provide capability 
>> indication or 
>>    capability negotiation, however over the years, SDP has seen 
>>    widespread adoption and as a result it has been gradually extended 
>>    to provide limited support for these, notably in the form of the 
>>    offer/answer model defined in RFC 3264. SDP and its current 
>>    extensions do not define how to negotiate one or more alternative 
>>    transport protocols (e.g. RTP profiles) or attributes. 
>> This makes it 
>>    difficult to deploy new RTP profiles such as secure RTP or 
>> RTP with 
>>    RTCP-based feedback, negotiate use of different security keying 
>>    mechanisms, etc. It also presents problems for some forms of media 
>>    negotiation.  
>>
>>    The purpose of this document is to address these shortcomings by 
>>    extending SDP with capability negotiation parameters and 
>> associated 
>>    offer/answer procedures to use those parameters in a backwards 
>>    compatible manner.  
>>
>>    The document defines a general SDP Capability Negotiation 
>> framework. 
>>    It also specifies how to provide attributes and transport 
>> protocols 
>>    as capabilities and negotiate them using the framework. Extensions 
>>    for other types of capabilities (e.g. media types and 
>> media formats) 
>>    may be provided in other documents.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-capa
>> bility-negotiation-07.txt
>>
>> To remove yourself from the I-D Announcement list, send a 
>> message to i-d-announce-request@ietf.org with the word 
>> unsubscribe in the body of the message. 
>> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
>> to change your subscription settings.
>>
>> Internet-Drafts are also available by anonymous FTP. Login 
>> with the username "anonymous" and a password of your e-mail 
>> address. After logging in, type "cd internet-drafts" and then 
>> "get draft-ietf-mmusic-sdp-capability-negotiation-07.txt".
>>
>> A list of Internet-Drafts directories can be found in 
>> http://www.ietf.org/shadow.html or 
>> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>> Internet-Drafts can also be obtained by e-mail.
>>
>> Send a message to:
>> 	mailserv@ietf.org.
>> In the body type:
>> 	"FILE 
>> /internet-drafts/draft-ietf-mmusic-sdp-capability-negotiation-07.txt".
>> 	
>> NOTE:	The mail server at ietf.org can return the document in
>> 	MIME-encoded form by using the "mpack" utility.  To use this
>> 	feature, insert the command "ENCODING mime" before the "FILE"
>> 	command.  To decode the response(s), you will need "munpack" or
>> 	a MIME-compliant mail reader.  Different MIME-compliant 
>> mail readers
>> 	exhibit different behavior, especially when dealing with
>> 	"multipart" MIME messages (i.e. documents which have been split
>> 	up into multiple messages), so check your local documentation on
>> 	how to manipulate these messages.
>>
>> Below is the data which will enable a MIME compliant mail 
>> reader implementation to automatically retrieve the ASCII 
>> version of the Internet-Draft.
>>
>>     
>
>   

--------------090805040005050200060409
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Francois Audet wrote:
<blockquote
 cite="mid1ECE0EB50388174790F9694F77522CCF12DC42D0@zrc2hxm0.corp.nortel.com"
 type="cite">
  <pre wrap="">Hi Flemming,

There seem to be some inconsistencies with the Best-Effort example in
section 3.2
and the one in section 4.1, which appears to be identical.

Most of the text and SDP is the same, but with some key differences:

- In the first example, the tcap includes RTP/SAVP only (the m-line has
RTP/AVP), but
  in the second example, the tcap includes both RTP/SAVP and RTP/AVP
(even if m-line
  is also RTP/AVP). Is this a typo? Which one is correct?
  </pre>
</blockquote>
They are both correct. The second example (4.1) includes an extra
transport protocol capability (RTP/AVP), but doesn't use it in any of
the potential configurations. In either case, if the potential
configuration cannot be supported, the (least preferred) actual
configuration, i.e. the RTP/AVP profile will be negotiated. <br>
<br>
<blockquote
 cite="mid1ECE0EB50388174790F9694F77522CCF12DC42D0@zrc2hxm0.corp.nortel.com"
 type="cite">
  <pre wrap="">
- In the first example, there is only one Offer/Answer exchange. In the
second
  example, there is a second-round of Offer/Answer exchange to "lock-it
down" to
  a plain SAVP offer for the benefits of middle boxes. Again, which one
is correct?
  </pre>
</blockquote>
They are both correct. The second offer/answer exchange is not required
but recommended when you think there might be a middle-box in place. <br>
<br>
The reason the two examples differ is that the 3.1. example is a very
quick introduction that is trying to give an overview of the key
concepts in the framework. The section 4 examples are a bit more
elaborate, however they are all valid. <br>
<br>
<blockquote
 cite="mid1ECE0EB50388174790F9694F77522CCF12DC42D0@zrc2hxm0.corp.nortel.com"
 type="cite">
  <pre wrap="">  PS: Personally, I prefer the first one. </pre>
</blockquote>
I know :-)<br>
<blockquote
 cite="mid1ECE0EB50388174790F9694F77522CCF12DC42D0@zrc2hxm0.corp.nortel.com"
 type="cite">
  <pre wrap="">I don't see why the we would
need a second
  one for middleboxes, and the single offer/answer should work. And from
a philosophical
  perspective, I don't think we should complicate unduly the protocols
just for the 
  benefits of sub-standard middleboxes...

Can you clarify?
  </pre>
</blockquote>
We've had that discussion before (look for thread titled "SDPCapNeg
Issue #6: Second Offer/Answer exchange" on 6/25/07), and the consensus
was that we did not want to require the second offer/answer exchange,
however it is still useful to address some potential middlebox issues,
so we wanted to include it as an option. ICE has a second offer/answer
exchange (REQUIRED if I recall correctly). <br>
<br>
Thanks <br>
<br>
-- Flemming <br>
<br>
<blockquote
 cite="mid1ECE0EB50388174790F9694F77522CCF12DC42D0@zrc2hxm0.corp.nortel.com"
 type="cite">
  <pre wrap="">
  </pre>
  <blockquote type="cite">
    <pre wrap="">-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:Internet-Drafts@ietf.org">mailto:Internet-Drafts@ietf.org</a>] 
Sent: Monday, October 29, 2007 12:15
To: <a class="moz-txt-link-abbreviated" href="mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:mmusic@ietf.org">mmusic@ietf.org</a>
Subject: [MMUSIC] I-D 
ACTION:draft-ietf-mmusic-sdp-capability-negotiation-07.txt

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 Capability Negotiation
	Author(s)	: F. Andreasen
	Filename	: 
draft-ietf-mmusic-sdp-capability-negotiation-07.txt
	Pages		: 79
	Date		: 2007-10-29
	
The Session Description Protocol (SDP) was intended for describing 
   multimedia sessions for the purposes of session announcement, 
   session invitation, and other forms of multimedia session 
   initiation. SDP was not intended to provide capability 
indication or 
   capability negotiation, however over the years, SDP has seen 
   widespread adoption and as a result it has been gradually extended 
   to provide limited support for these, notably in the form of the 
   offer/answer model defined in RFC 3264. SDP and its current 
   extensions do not define how to negotiate one or more alternative 
   transport protocols (e.g. RTP profiles) or attributes. 
This makes it 
   difficult to deploy new RTP profiles such as secure RTP or 
RTP with 
   RTCP-based feedback, negotiate use of different security keying 
   mechanisms, etc. It also presents problems for some forms of media 
   negotiation.  

   The purpose of this document is to address these shortcomings by 
   extending SDP with capability negotiation parameters and 
associated 
   offer/answer procedures to use those parameters in a backwards 
   compatible manner.  

   The document defines a general SDP Capability Negotiation 
framework. 
   It also specifies how to provide attributes and transport 
protocols 
   as capabilities and negotiate them using the framework. Extensions 
   for other types of capabilities (e.g. media types and 
media formats) 
   may be provided in other documents.

A URL for this Internet-Draft is:
<a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-capa">http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-capa</a>
bility-negotiation-07.txt

To remove yourself from the I-D Announcement list, send a 
message to <a class="moz-txt-link-abbreviated" href="mailto:i-d-announce-request@ietf.org">i-d-announce-request@ietf.org</a> with the word 
unsubscribe in the body of the message. 
You can also visit <a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/I-D-announce">https://www1.ietf.org/mailman/listinfo/I-D-announce</a>
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-capability-negotiation-07.txt".

A list of Internet-Drafts directories can be found in 
<a class="moz-txt-link-freetext" href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a> or 
<a class="moz-txt-link-freetext" href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a>

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

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

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

    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
</blockquote>
</body>
</html>

--------------090805040005050200060409--



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

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

--===============1405317434==--





From mmusic-bounces@ietf.org Wed Oct 31 03:16:01 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1In7n3-0005wb-NL; Wed, 31 Oct 2007 03:15:01 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1In7n2-0005vs-Ai
	for mmusic-confirm+ok@megatron.ietf.org; Wed, 31 Oct 2007 03:15:00 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1In7mx-0005uk-C7
	for mmusic@ietf.org; Wed, 31 Oct 2007 03:14:55 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1In7mu-0005fV-GQ
	for mmusic@ietf.org; Wed, 31 Oct 2007 03:14:53 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	B0EF920E70; Wed, 31 Oct 2007 08:14:49 +0100 (CET)
X-AuditID: c1b4fb3c-b1681bb0000007e1-f0-47282b696d47
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	9805220604; Wed, 31 Oct 2007 08:14:49 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 31 Oct 2007 08:14:49 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] ICE: Clarification question when full ICE communciate
	with	ICE lite and chooses host candidate
Date: Wed, 31 Oct 2007 08:14:45 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF02D12922@esealmw113.eemea.ericsson.se>
In-Reply-To: <47268DAF.2080600@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] ICE: Clarification question when full ICE communciate
	with	ICE lite and chooses host candidate
Thread-Index: AcgalxdZR7ZloULPRFqfCQb0OgX3gAA9l/0g
References: <CA9998CD4A020D418654FCDEF4E707DF02BC97B3@esealmw113.eemea.ericsson.se>
	<47250BB6.5000608@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF02C8065E@esealmw113.eemea.ericsson.se>
	<47268DAF.2080600@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Jonathan Rosenberg" <jdrosen@cisco.com>
X-OriginalArrivalTime: 31 Oct 2007 07:14:49.0319 (UTC)
	FILETIME=[B94C6770:01C81B8D]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
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>
Errors-To: mmusic-bounces@ietf.org


Hi Jonathan,=20

>No, an UPDATE is sent only if the default does not match the selected
>candidate:

In my example the candidate "type" (HOST_CANDIDATE) DOES match, but the
local address doesn't so I guess that mean an UPDATE will be sent,
right?

Regards,

Christer






>=20
> (Section 8.1.2)
>=20
> o  Once the state of each check list is Completed:
>=20
>        *  The agent sets the state of ICE processing overall to
>           Completed.
>=20
>        *  If an agent is controlling, it examines the highest priority
>           nominated candidate pair for each component of each media
>           stream.  If any of those candidate pairs differ from the
>           default candidate pairs in the most recent offer/answer
>           exchange, the controlling agent MUST generate an=20
> updated offer
>           as described in Section 9.  If the controlling=20
> agent is using
>           an aggressive nomination algorithm, this may result=20
> in several
>           updated offers as the pairs selected for media change.  An
>           agent MAY delay sending the offer for a brief interval (one
>           second is RECOMMENDED) in order to allow the=20
> selected pairs to
>           stabilize.
>=20
>=20
> -Jonathan R.
>=20
>=20
> Christer Holmberg wrote:
> > Hi,
> >=20
> > Thanks for the clarification!
> >=20
> > So, does this mean that an UPDATE will be sent EVEN if=20
> HOST_CANDIDATE=20
> > was the default candidate and is then chosen to be used,=20
> since the SDP=20
> > address information does change?
> >=20
> > INVITE c/m =3D local address (HOST_CANDIDATE) UPDATE c/m =3D mapped=20
> > address (HOST_CANDIDATE)
> >=20
> > Regards,
> >=20
> > Christer
> >=20
> > =20
> >=20
> >> -----Original Message-----
> >> From: Jonathan Rosenberg [mailto:jdrosen@cisco.com]
> >> Sent: 29. lokakuuta 2007 0:23
> >> To: Christer Holmberg
> >> Cc: mmusic@ietf.org
> >> Subject: Re: [MMUSIC] ICE: Clarification question when full ICE=20
> >> communciate with ICE lite and chooses host candidate
> >>
> >> inline.
> >>
> >> Christer Holmberg wrote:
> >>> Hi,
> >>>
> >>> Assume the following scenario:
> >>>
> >>> - User A is located behind a NAT, and implements full ICE.
> >>>
> >>> - User A collects candidates, and send an INVITE
> >>>
> >>> - The call is received by an MGCF, implementing ICE lite.
> >>>
> >>> - User A starts doing connectivity checks, which the MGCF=20
> reply to=20
> >>> (being ICE lite, the MGCF does not generate checks itself)
> >>>
> >>> - User A detects that the HOST_CANDIDATE checks work, so it
> >> sends an
> >>> UPDATE and tells the MGCF that the HOST_CANDIDATE will be=20
> used. The=20
> >>> Local Address information will be in the c/m line.
> >>>
> >>>
> >>> Now, the MGCF will start sending media towards the Local
> >> Address. But,
> >>> since User A, and the Local Address, is behind the NAT, the
> >> media will
> >>> not reach User A.
> >> No, this is not what will happen. The candidate pair=20
> learned from the=20
> >> checks sent by A are based on the mapped address from the=20
> >> connectivity checks. Quoting fro 7.1.2.2.2:
> >>
> >> 7.1.2.2.2.  Constructing a Valid Pair
> >>
> >>     The agent constructs a candidate pair whose local=20
> candidate equals
> >>     the mapped address of the response, and whose remote candidate=20
> >> equals
> >>     the destination address to which the request was sent.
> >>
> >>
> >> -Jonathan R.
> >>
> >> --=20
> >> Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
> >> Cisco Fellow                                   Parsippany, NJ=20
> >> 07054-2711
> >> Cisco Systems
> >> jdrosen@cisco.com                              FAX:  =20
> (973) 952-5050
> >> http://www.jdrosen.net                         PHONE:=20
> (973) 952-5000
> >> http://www.cisco.com
> >>
> >=20
>=20
> --=20
> Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
> Cisco Fellow                                   Parsippany, NJ=20
> 07054-2711
> Cisco Systems
> jdrosen@cisco.com                              FAX:   (973) 952-5050
> http://www.jdrosen.net                         PHONE: (973) 952-5000
> http://www.cisco.com
>=20


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



From mmusic-bounces@ietf.org Wed Oct 31 08:15:03 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1InCRZ-0005wP-8W; Wed, 31 Oct 2007 08:13:09 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1InCRY-0005rH-7W
	for mmusic-confirm+ok@megatron.ietf.org; Wed, 31 Oct 2007 08:13:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1InCRX-0005r5-Q2
	for mmusic@ietf.org; Wed, 31 Oct 2007 08:13:07 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1InCRV-0001dT-Qu
	for mmusic@ietf.org; Wed, 31 Oct 2007 08:13:07 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l9VCChOj022903; Wed, 31 Oct 2007 14:12:59 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 31 Oct 2007 14:12:27 +0200
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 31 Oct 2007 14:12:27 +0200
Received: from [10.144.23.61] ([10.144.23.61]) by esebh101.NOE.Nokia.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 31 Oct 2007 14:12:27 +0200
Message-ID: <47287129.8040308@nsn.com>
Date: Wed, 31 Oct 2007 14:12:25 +0200
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
References: <47276C3C.1000902@cisco.com>
In-Reply-To: <47276C3C.1000902@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Oct 2007 12:12:27.0307 (UTC)
	FILETIME=[4D7D1FB0:01C81BB7]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Cc: IETF MMUSIC WG <mmusic@ietf.org>
Subject: [MMUSIC] Re: draft-ietf-mmusic-file-transfer-mech-04
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>
Errors-To: mmusic-bounces@ietf.org

Hi Paul:

Thanks for your comments. See inline.

Paul Kyzivat wrote:
> I started reviewing this version with the expectation that all issues 
> were now resolved. But as I started thinking about the mechanism for 
> handling subsequent o/a when no new transfer is required, and began to 
> see potential problems - some new ones and some that have been there.
> 
> First, 4975 still is operable here, right? 

Yes, correct. MSRP (RFC 4975) is the foundation for this draft.

> (This just provides layered 
> behavior on top of that.) That means that the o/a rules for 4975 still 
> apply. IIUC this means that in a subsequent o/a (after previously 
> negotiating an MSRP session) its possible that the connection will be 
> replaced with a new one. In fact, if the new o/a is in the opposite 
> direction, its mandated that a new connection be made in the opposite 
> direction.

Certainly we need to clarify the MSRP behavior in SIMPLE. My 
understanding is that TCP connections are decoupled from MSRP sessions. 
I based this comment on the fact that several MSRP sessions can share a 
single TCP connection, something that wouldn't be possible if we follow 
your assumptions.

> 
> (I just posted a question to SIMPLE about how MSRP is supposed to behave 
> in this case.)
> 
> Now, getting on to the draft, the file-transfer-id is dealing with 
> instances of file transfers, not of MSRP sessions. I *assume* that a 
> file transfer will be completed on one connection - that it won't be 
> split across multiple connections - or is that a bad assumption? (I 
> think if it can't be completed in a single connection then it will need 
> to be restarted, perhaps with a file-range.)

What you said is correct. A file transfer will complete on a single TCP 
connection. As you mentioned, file transfers can be interrupted. If the 
file transfer is resumed at a later time, it will be a different one and 
the file-range will signal the starting point.

> 
> So, suppose a file transfer is started, and then before it completes 
> there is need to send a new o/a. (Perhaps because of session timer.) 
> This could 2result in a new MSRP session being established in 
> the other direction. 

Hang on... If it is a new O/A due to session timer, or adding additional 
media streams, the SDP-for-MRSP won't change. Thus, the MSRP session 
will remain as with previous O/A

However, if the SDP-for-MSRP changes the MSRP session, then it implies a 
different file transfer. This is covered in the first paragraph of 
Section 8.6 of the file transfer draft.

> Does that cause the file transfer to abort in the 
> middle? Or does the file transfer continue on the original connection 
> until it is complete or until the connection fails?

Did the 'file-transfer-id' change or not?
This is discussed in Section 8.3 of the draft.

- If the file-transfer-id changed and the MSRP session did not change, 
then it means "abort the current transfer and restart".

- If the both the file-transfer-id the MSRP session changed, then it 
means "abort the current transfer and start a new file transfer". So, 
the file descriptor has changed as well.

- If neither the file-transfer-id nor the MSRP session changed, then it 
means "do nothing, continue as we are currently doing".

- If the file-transfer-id did not change, but the MSRP session changed, 
then is also means "do nothing, continue as we are currently doing". 
This is because MSRP allows to do a new SDP o/a, change the MSRP 
sessions, and continue as if nothing had happened. I don't know what is 
the real use case behind, but this seems to be how MSRP works.

> 
> If the transfer continues until complete, then a clean way to handle a 
> new offer that doesn't want to initiate a new transfer would simply be 
> to set the port=0 in the m-line, avoiding creating a new connection that 
> isn't needed.

We still allow port=0, but this is a mechanism used, for example, to 
reject a media stream. Port=0 means "I don't want to establish this 
media stream", and applies for MSRP as well. So, we shouldn't overload 
the term to say "I want to remain the media stream (MSRP session) but 
don't send me media (the file)."


> 
> But if the old connection must be torn down before transfer is complete, 
> then we have a bigger problem.

Well, I think the file-transfer-id serves for that purpose.

> 
> I've got some lesser issues, but will defer discussing them until this 
> is clarified.
> 
>     Thanks,
>     Paul

/Miguel

-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Espoo, Finland



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



From mmusic-bounces@ietf.org Wed Oct 31 11:11:58 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1InFDX-0002Lk-E3; Wed, 31 Oct 2007 11:10:51 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1InFDW-0002Lf-Nv
	for mmusic-confirm+ok@megatron.ietf.org; Wed, 31 Oct 2007 11:10:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1InFDW-0002LW-Dn
	for mmusic@ietf.org; Wed, 31 Oct 2007 11:10:50 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1InFDV-0002Yg-0i
	for mmusic@ietf.org; Wed, 31 Oct 2007 11:10:50 -0400
X-IronPort-AV: E=Sophos;i="4.21,351,1188802800"; d="scan'208";a="541742514"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 31 Oct 2007 08:10:46 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l9VFAjdS007289; 
	Wed, 31 Oct 2007 08:10:45 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l9VFAIAj008210;
	Wed, 31 Oct 2007 15:10:45 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 31 Oct 2007 08:10:44 -0700
Received: from [10.32.241.148] ([10.32.241.148]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 31 Oct 2007 08:10:44 -0700
Message-ID: <47289B10.5080201@cisco.com>
Date: Wed, 31 Oct 2007 11:11:12 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] ICE: Clarification question when full ICE communciate
	with	ICE lite and chooses host candidate
References: <CA9998CD4A020D418654FCDEF4E707DF02BC97B3@esealmw113.eemea.ericsson.se>
	<47250BB6.5000608@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF02C8065E@esealmw113.eemea.ericsson.se>
	<47268DAF.2080600@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF02D12922@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF02D12922@esealmw113.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Oct 2007 15:10:44.0167 (UTC)
	FILETIME=[35506D70:01C81BD0]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4672; t=1193843445;
	x=1194707445; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20[MMUSIC]=20ICE=3A=20Clarification=20question=20when=2
	0full=20ICE=20communciate=0A=20with=09ICE=20lite=20and=20chooses=20host=20
	candidate |Sender:=20;
	bh=x3pC/RVSTrmIA8/bkFM1QV19QvD/gUR6EdGO9gw8IX8=;
	b=CSMUc+ILlp+AN4NAGHCbFQXY1W0zYXnIEFuqKCz+fdefEyCEKa4gXvTzt+tK8i4/74sLCU8F
	838PA4c3B2hxJ1q2pBmW1ZWELrvgnxyMxoco7p+kcbKvQPeSRc5ekabZU7YHoAhaZDewcWtRBB
	MNwzeq6ILRQI7cgW7Y/2DwVgc=;
Authentication-Results: sj-dkim-1; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78
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>
Errors-To: mmusic-bounces@ietf.org

No - the candidate is not HOST, its server reflexive.

-Jonathan R.

Christer Holmberg wrote:
> Hi Jonathan, 
> 
>> No, an UPDATE is sent only if the default does not match the selected
>> candidate:
> 
> In my example the candidate "type" (HOST_CANDIDATE) DOES match, but the
> local address doesn't so I guess that mean an UPDATE will be sent,
> right?
> 
> Regards,
> 
> Christer
> 
> 
> 
> 
> 
> 
>> (Section 8.1.2)
>>
>> o  Once the state of each check list is Completed:
>>
>>        *  The agent sets the state of ICE processing overall to
>>           Completed.
>>
>>        *  If an agent is controlling, it examines the highest priority
>>           nominated candidate pair for each component of each media
>>           stream.  If any of those candidate pairs differ from the
>>           default candidate pairs in the most recent offer/answer
>>           exchange, the controlling agent MUST generate an 
>> updated offer
>>           as described in Section 9.  If the controlling 
>> agent is using
>>           an aggressive nomination algorithm, this may result 
>> in several
>>           updated offers as the pairs selected for media change.  An
>>           agent MAY delay sending the offer for a brief interval (one
>>           second is RECOMMENDED) in order to allow the 
>> selected pairs to
>>           stabilize.
>>
>>
>> -Jonathan R.
>>
>>
>> Christer Holmberg wrote:
>>> Hi,
>>>
>>> Thanks for the clarification!
>>>
>>> So, does this mean that an UPDATE will be sent EVEN if 
>> HOST_CANDIDATE 
>>> was the default candidate and is then chosen to be used, 
>> since the SDP 
>>> address information does change?
>>>
>>> INVITE c/m = local address (HOST_CANDIDATE) UPDATE c/m = mapped 
>>> address (HOST_CANDIDATE)
>>>
>>> Regards,
>>>
>>> Christer
>>>
>>>  
>>>
>>>> -----Original Message-----
>>>> From: Jonathan Rosenberg [mailto:jdrosen@cisco.com]
>>>> Sent: 29. lokakuuta 2007 0:23
>>>> To: Christer Holmberg
>>>> Cc: mmusic@ietf.org
>>>> Subject: Re: [MMUSIC] ICE: Clarification question when full ICE 
>>>> communciate with ICE lite and chooses host candidate
>>>>
>>>> inline.
>>>>
>>>> Christer Holmberg wrote:
>>>>> Hi,
>>>>>
>>>>> Assume the following scenario:
>>>>>
>>>>> - User A is located behind a NAT, and implements full ICE.
>>>>>
>>>>> - User A collects candidates, and send an INVITE
>>>>>
>>>>> - The call is received by an MGCF, implementing ICE lite.
>>>>>
>>>>> - User A starts doing connectivity checks, which the MGCF 
>> reply to 
>>>>> (being ICE lite, the MGCF does not generate checks itself)
>>>>>
>>>>> - User A detects that the HOST_CANDIDATE checks work, so it
>>>> sends an
>>>>> UPDATE and tells the MGCF that the HOST_CANDIDATE will be 
>> used. The 
>>>>> Local Address information will be in the c/m line.
>>>>>
>>>>>
>>>>> Now, the MGCF will start sending media towards the Local
>>>> Address. But,
>>>>> since User A, and the Local Address, is behind the NAT, the
>>>> media will
>>>>> not reach User A.
>>>> No, this is not what will happen. The candidate pair 
>> learned from the 
>>>> checks sent by A are based on the mapped address from the 
>>>> connectivity checks. Quoting fro 7.1.2.2.2:
>>>>
>>>> 7.1.2.2.2.  Constructing a Valid Pair
>>>>
>>>>     The agent constructs a candidate pair whose local 
>> candidate equals
>>>>     the mapped address of the response, and whose remote candidate 
>>>> equals
>>>>     the destination address to which the request was sent.
>>>>
>>>>
>>>> -Jonathan R.
>>>>
>>>> -- 
>>>> Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
>>>> Cisco Fellow                                   Parsippany, NJ 
>>>> 07054-2711
>>>> Cisco Systems
>>>> jdrosen@cisco.com                              FAX:   
>> (973) 952-5050
>>>> http://www.jdrosen.net                         PHONE: 
>> (973) 952-5000
>>>> http://www.cisco.com
>>>>
>> -- 
>> Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
>> Cisco Fellow                                   Parsippany, NJ 
>> 07054-2711
>> Cisco Systems
>> jdrosen@cisco.com                              FAX:   (973) 952-5050
>> http://www.jdrosen.net                         PHONE: (973) 952-5000
>> http://www.cisco.com
>>
> 

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


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



From mmusic-bounces@ietf.org Wed Oct 31 12:27:48 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1InGOl-0001g7-Cq; Wed, 31 Oct 2007 12:26:31 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1InGOj-0001Lm-Um
	for mmusic-confirm+ok@megatron.ietf.org; Wed, 31 Oct 2007 12:26:29 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1InGOj-0001Lc-9w
	for mmusic@ietf.org; Wed, 31 Oct 2007 12:26:29 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1InGOi-0004Yf-Ah
	for mmusic@ietf.org; Wed, 31 Oct 2007 12:26:29 -0400
X-IronPort-AV: E=Sophos;i="4.21,352,1188792000"; d="scan'208";a="135904456"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 31 Oct 2007 12:26:27 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l9VGQRtd001410; 
	Wed, 31 Oct 2007 12:26:27 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l9VGQP5c022482; 
	Wed, 31 Oct 2007 16:26:27 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 31 Oct 2007 12:26:20 -0400
Received: from [161.44.174.216] ([161.44.174.216]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 31 Oct 2007 12:26:19 -0400
Message-ID: <4728ACA9.6000105@cisco.com>
Date: Wed, 31 Oct 2007 12:26:17 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Miguel Garcia <Miguel.Garcia@nsn.com>
References: <47276C3C.1000902@cisco.com> <47287129.8040308@nsn.com>
In-Reply-To: <47287129.8040308@nsn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Oct 2007 16:26:19.0625 (UTC)
	FILETIME=[C4A86590:01C81BDA]
X-TM-AS-Product-Ver: SMEX-8.0.0.1181-5.000.1023-15516.002
X-TM-AS-Result: No--25.904500-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=8304; t=1193847987;
	x=1194711987; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20draft-ietf-mmusic-file-transfer-mech-04
	|Sender:=20 |To:=20Miguel=20Garcia=20<Miguel.Garcia@nsn.com>;
	bh=YOLTFMdgn0M75BuZgcdp95zGJuWnWVv8ReKXwSV6Tgk=;
	b=xuCIjFsBgVbZ6QwSNaIctpcxb/fVJBCrCjBu0pC7S5Suj3u/yNFZ0I9PgaR/F+rPPFH3nQnI
	+fn5BNOcGCZPObQ7gVC/gQd1O1B1eHdG8dkdTPJRtzecvAdktuo3MTh2;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93df555cbdbcdae9621e5b95d44b301e
Cc: IETF MMUSIC WG <mmusic@ietf.org>
Subject: [MMUSIC] Re: draft-ietf-mmusic-file-transfer-mech-04
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>
Errors-To: mmusic-bounces@ietf.org

Miguel - inline.

Miguel Garcia wrote:
> Hi Paul:
> 
> Thanks for your comments. See inline.
> 
> Paul Kyzivat wrote:
>> I started reviewing this version with the expectation that all issues 
>> were now resolved. But as I started thinking about the mechanism for 
>> handling subsequent o/a when no new transfer is required, and began to 
>> see potential problems - some new ones and some that have been there.
>>
>> First, 4975 still is operable here, right? 
> 
> Yes, correct. MSRP (RFC 4975) is the foundation for this draft.
> 
>> (This just provides layered behavior on top of that.) That means that 
>> the o/a rules for 4975 still apply. IIUC this means that in a 
>> subsequent o/a (after previously negotiating an MSRP session) its 
>> possible that the connection will be replaced with a new one. In fact, 
>> if the new o/a is in the opposite direction, its mandated that a new 
>> connection be made in the opposite direction.
> 
> Certainly we need to clarify the MSRP behavior in SIMPLE. My 
> understanding is that TCP connections are decoupled from MSRP sessions. 
> I based this comment on the fact that several MSRP sessions can share a 
> single TCP connection, something that wouldn't be possible if we follow 
> your assumptions.

Yes, I know this has been asserted, and its certainly desirable. I'm 
just having difficulty finding an explanation of this behavior. All I 
can find is a statement that the offerer is expected to initiate the 
connection. It doesn't say (AFAIK) that it should only do so if there 
isn't already a connection.

>> (I just posted a question to SIMPLE about how MSRP is supposed to 
>> behave in this case.)

I haven't gotten any responses there yet. Hopefully I've just missed 
something, or else a clarification will deal with it.

Its reasonable to assume that there must be some way to do another o/a 
without disturbing an existing MSRP session.

>> Now, getting on to the draft, the file-transfer-id is dealing with 
>> instances of file transfers, not of MSRP sessions. I *assume* that a 
>> file transfer will be completed on one connection - that it won't be 
>> split across multiple connections - or is that a bad assumption? (I 
>> think if it can't be completed in a single connection then it will 
>> need to be restarted, perhaps with a file-range.)
> 
> What you said is correct. A file transfer will complete on a single TCP 
> connection. As you mentioned, file transfers can be interrupted. If the 
> file transfer is resumed at a later time, it will be a different one and 
> the file-range will signal the starting point.
> 
>>
>> So, suppose a file transfer is started, and then before it completes 
>> there is need to send a new o/a. (Perhaps because of session timer.) 
>> This could 2result in a new MSRP session being established in the 
>> other direction. 
> 
> Hang on... If it is a new O/A due to session timer, or adding additional 
> media streams, the SDP-for-MRSP won't change. Thus, the MSRP session 
> will remain as with previous O/A
> 
> However, if the SDP-for-MSRP changes the MSRP session, then it implies a 
> different file transfer. This is covered in the first paragraph of 
> Section 8.6 of the file transfer draft.

I don't see how to draw that conclusion from the paragraph. It says that 
you can only send one file using the MSRP session, nothing more. (The 
*end* of section 8.6 says that the MSRP session should be closed when 
the transfer is complete, which of course precludes reusing it for an 
additional transfer.)

I see nothing addressing the behavior if the MSRP parameters should 
change but the file transfer id remains unchanged. I can imagine three 
possibilities:

1) the transfer is aborted if it hasn't already completed. The use of 
the same file transfer id with a different session is ignored.

2) the use of the same file transfer id with a different session is 
considered an error. The request carrying the offer is rejected. The 
transfer continues on the same session if it hasn't already completed.

3) the transfer is continued transparently on the new MSRP session.

Of those, (3) seems most desirable, but I expect it is fraught with 
implementation problems. (1) is probably the easiest to implement.

If this behavior is considered an error case then perhaps we don't need 
to concern ourselves with how it is handled. But if doing a new O/A 
without a change to SDP can still result in a new session then that has 
the same resolutions as above and isn't an error case.


>> Does that cause the file transfer to abort in the middle? Or does the 
>> file transfer continue on the original connection until it is complete 
>> or until the connection fails?

Assume the original INVITE that established the file transfer was from 
Alice to Bob, and the offer was in the invite.

What I had in mind was:

- The new INVITE, and offer, is from Bob to Alice

- The part of the offer from Bob relating to the file transfer is
   identical to what Bob sent in his prior answer.

- The part of the answer from Alice relating to the file transfer
   is identical to what Alice sent Bob in her prior offer.

> Did the 'file-transfer-id' change or not?

No.

> This is discussed in Section 8.3 of the draft.
> 
> - If the file-transfer-id changed and the MSRP session did not change, 
> then it means "abort the current transfer and restart".
> 
> - If the both the file-transfer-id the MSRP session changed, then it 
> means "abort the current transfer and start a new file transfer". So, 
> the file descriptor has changed as well.
> 
> - If neither the file-transfer-id nor the MSRP session changed, then it 
> means "do nothing, continue as we are currently doing".

In my scenario this all works IF the session doesn't have to be 
reestablished in the other direction because the new offer came from Bob 
while the old offer came from Alice. Its really an MSRP question. You 
have assumed that no new session is required. Its a reasonable 
expectation. I just want to get clarification on it over in SIMPLE.

> - If the file-transfer-id did not change, but the MSRP session changed, 
> then is also means "do nothing, continue as we are currently doing". 
> This is because MSRP allows to do a new SDP o/a, change the MSRP 
> sessions, and continue as if nothing had happened. I don't know what is 
> the real use case behind, but this seems to be how MSRP works.

Hmm. Where did you find that in MSRP?

With media sessions in general, viewed as streams, I think it is 
generally the case that you can continue doing what you were doing 
across a change as long as the two endpoints remain unchanged.

If you and I are talking, it is possible that our phones might need to 
negotiate a new RTP stream, but we can keep talking across the change, 
though there might be a glitch. Presumably the same is true for an 
interactive MSRP session. During the switch it is again possible that 
there might be a glitch and a message be lost or duplicated, but the 
users will probably grumble and cope.

What will happen with a file transfer? Will it manage, without losing 
any of the file? Or is this case just declared illegal for file transfer?

>> If the transfer continues until complete, then a clean way to handle a 
>> new offer that doesn't want to initiate a new transfer would simply be 
>> to set the port=0 in the m-line, avoiding creating a new connection 
>> that isn't needed.
> 
> We still allow port=0, but this is a mechanism used, for example, to 
> reject a media stream. Port=0 means "I don't want to establish this 
> media stream", and applies for MSRP as well. So, we shouldn't overload 
> the term to say "I want to remain the media stream (MSRP session) but 
> don't send me media (the file)."

Yes, this was a bad suggestion.

	Thanks,
	Paul

>>
>> But if the old connection must be torn down before transfer is 
>> complete, then we have a bigger problem.
> 
> Well, I think the file-transfer-id serves for that purpose.
> 
>>
>> I've got some lesser issues, but will defer discussing them until this 
>> is clarified.
>>
>>     Thanks,
>>     Paul
> 
> /Miguel
> 


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



From mmusic-bounces@ietf.org Wed Oct 31 14:23:41 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1InID9-0004mn-Kr; Wed, 31 Oct 2007 14:22:39 -0400
Received: from mmusic by megatron.ietf.org with local (Exim 4.43)
	id 1InID8-0004mg-Ka
	for mmusic-confirm+ok@megatron.ietf.org; Wed, 31 Oct 2007 14:22:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1InID8-0004mY-At
	for mmusic@ietf.org; Wed, 31 Oct 2007 14:22:38 -0400
Received: from keskus.netlab.hut.fi ([130.233.154.176] helo=smtp.netlab.hut.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1InID2-0003dn-0I
	for mmusic@ietf.org; Wed, 31 Oct 2007 14:22:38 -0400
Received: from localhost (webserver.netlab.hut.fi [130.233.154.187])
	by smtp.netlab.hut.fi (Postfix) with ESMTP id 97D6BC51D1;
	Wed, 31 Oct 2007 20:22:25 +0200 (EET)
X-Virus-Scanned: Debian amavisd-new at TKK Netlab
Received: from smtp.netlab.hut.fi ([130.233.154.176])
	by localhost (webserver.netlab.hut.fi [130.233.154.187]) (amavisd-new,
	port 10024)
	with ESMTP id 3Tvm-+vKCGFY; Wed, 31 Oct 2007 20:22:19 +0200 (EET)
Received: from [127.0.0.1] (keskus.netlab.hut.fi [130.233.154.176])
	by smtp.netlab.hut.fi (Postfix) with ESMTP id D7C86C51DC;
	Wed, 31 Oct 2007 20:22:18 +0200 (EET)
Message-ID: <4728C7DD.5030701@netlab.hut.fi>
Date: Wed, 31 Oct 2007 20:22:21 +0200
From: Joerg Ott <jo@netlab.tkk.fi>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <470246D8.7080703@ericsson.com> <472859EE.7090100@netlab.hut.fi>
	<9AAEDF491EF7CA48AB587781B8F5D7C67DA3A5@srvxchg3.cablelabs.com>
	<472885F5.6070701@ericsson.com>
In-Reply-To: <472885F5.6070701@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: Cullen Jennings <fluffy@cisco.com>, mmusic <mmusic@ietf.org>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	Joerg Ott <jo@netlab.tkk.fi>, Jean-Francois Mule <jf.mule@cablelabs.com>,
	"James M. Polk" <jmpolk@cisco.com>
Subject: [MMUSIC] WGLC: draft-ietf-mmusic-qos-identification-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>
Errors-To: mmusic-bounces@ietf.org

Folks,

this is to announce WGLC ending on 15 November 2007 for
draft-ietf-mmusic-qos-identification-00.txt

The document is targeted for publication as Proposed Standard.

Please note that, while being a -00 draft, it has seen
multiple revisions as an individual contribution before
(draft-polk-mmusic-qos-mechanism-identification-03.txt)
and has received the necessary discussion.

Please send your WGLC comments to the MMUSIC list, the
chairs, and the authors.

The closing date will allow to authors to incorporate
minor changes (if any) prior to the I-D deadline.

Joerg



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



