From mmusic-bounces@ietf.org Fri Jun 02 08:26:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fm8jo-0002GF-1J; Fri, 02 Jun 2006 08:26:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fm8jl-0002BM-Sc
	for mmusic@ietf.org; Fri, 02 Jun 2006 08:26:45 -0400
Received: from szxga01-in.huawei.com ([61.144.161.53] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fm8ji-00069v-72
	for mmusic@ietf.org; Fri, 02 Jun 2006 08:26:45 -0400
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J0800C8OFDBX3@szxga01-in.huawei.com> for
	mmusic@ietf.org; Fri, 02 Jun 2006 20:15:12 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J08006XUFDBM6@szxga01-in.huawei.com> for
	mmusic@ietf.org; Fri, 02 Jun 2006 20:15:11 +0800 (CST)
Received: from w52438 ([10.164.5.32])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0J08007QTFCMNS@szxml03-in.huawei.com> for
	mmusic@ietf.org; Fri, 02 Jun 2006 20:14:54 +0800 (CST)
Date: Fri, 02 Jun 2006 20:13:50 +0800
From: Kylin Wei <weiqikun@huawei.com>
To: mmusic@ietf.org
Message-id: <000001c6863e$04e9bfc0$2005a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Subject: [MMUSIC] A question of Remote denial of Service Attack in RTSP 2.0
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

Dear mmusic experts:

I have a question of remote denial of service attack in RTSP 2.0.

>In rfc2326bis, section 20.1:
>The attacker may initiate traffic flows to one or more IP addresses
>by specifying them as the destination in SETUP requests. 
>The server SHOULD NOT allow the destination field to be set unless a
>mechanism exists in the system to authorize the request originator to
>direct streams to the recipient. It is preferred that this
>authorization be performed by the recipient itself and the
>credentials passed along to the server.

I don't understand how to perform this authorization by the recipient?
Will a server send a message to report the recipient and request its 
authorization?

Thanks.

Kylin Wei 




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



From mmusic-bounces@ietf.org Fri Jun 02 10:26:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FmAbh-00023R-1J; Fri, 02 Jun 2006 10:26:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FmAbf-00023M-Gz
	for mmusic@ietf.org; Fri, 02 Jun 2006 10:26:31 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FmAbd-0002rT-Lh
	for mmusic@ietf.org; Fri, 02 Jun 2006 10:26:31 -0400
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	830E54F0003; Fri,  2 Jun 2006 16:26:28 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 Jun 2006 16:26:27 +0200
Received: from [147.214.30.119] ([147.214.30.119]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 Jun 2006 16:26:27 +0200
Message-ID: <44804A92.5000603@ericsson.com>
Date: Fri, 02 Jun 2006 16:26:26 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Kylin Wei <weiqikun@huawei.com>
Subject: Re: [MMUSIC] A question of Remote denial of Service Attack in RTSP 2.0
References: <000001c6863e$04e9bfc0$2005a40a@china.huawei.com>
In-Reply-To: <000001c6863e$04e9bfc0$2005a40a@china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Jun 2006 14:26:27.0665 (UTC)
	FILETIME=[88C36410:01C68650]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
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 your cutting of the text made it a bit more cryptic than the 
complete one present in version 12:

20.1 Remote denial of Service Attack

    The attacker may initiate traffic flows to one or more IP addresses
    by specifying them as the destination in SETUP requests. While the
    attacker's IP address may be known in this case, this is not always
    useful in prevention of more attacks or ascertaining the attackers
    identity. Thus, an RTSP server MUST only allow client-specified
    destinations for RTSP-initiated traffic flows if the server has
    ensured that the specified destination address accepts receiving
    media through different security mechanisms. Security mechanism that
    are acceptable in an increased generality are; verification of the
    client's identity, either against a database of known users using
    RTSP authentication mechanisms (preferably digest authentication or
    stronger); a list of addresses that accept to be media destinations,
    especially considering user identity; and media path based
    verification.

    The server SHOULD NOT allow the destination field to be set unless a
    mechanism exists in the system to authorize the request originator to
    direct streams to the recipient. It is preferred that this
    authorization be performed by the recipient itself and the
    credentials passed along to the server. However, in certain cases,
    such as when recipient address is a multicast group, or when the
    recipient is unable to communicate with the server in an out-of-band
    manner, this may not be possible. In these cases server may chose
    another method such as a server-resident authorization list to ensure
    that the request originator has the proper credentials to request
    stream delivery to the recipient.


The intention with the following phrase:

   "It is preferred that this
    authorization be performed by the recipient itself and the
    credentials passed along to the server."

Is that the server should do the authorization directly with the media 
destination itself. The signalling client has no say in this as he is 
the attacker. Thus the server should send some type of authorization 
request to the client. The client if accepting media responds 
positively. Failure to respond or a negative response prevents delivery.

The foreseen mechanism to solve this, is to use STUN and ICE. In the ICE 
path verification the server will send STUN requests to the destination 
ports asking if there is someone there, including using a password and 
user ID that was only included in the SETUP request. Thus the media 
transport and signalling is bound and prevents the denial of service 
attack, unless the attacker is on the path and can respond himself.

I hope that clarifies the intentions. If you have a proposal for 
improved language of this paragraphs, please send it to me.

Cheers

Magnus

Kylin Wei wrote:
> Dear mmusic experts:
> 
> I have a question of remote denial of service attack in RTSP 2.0.
> 
>> In rfc2326bis, section 20.1:
>> The attacker may initiate traffic flows to one or more IP addresses
>> by specifying them as the destination in SETUP requests. 
>> The server SHOULD NOT allow the destination field to be set unless a
>> mechanism exists in the system to authorize the request originator to
>> direct streams to the recipient. It is preferred that this
>> authorization be performed by the recipient itself and the
>> credentials passed along to the server.
> 
> I don't understand how to perform this authorization by the recipient?
> Will a server send a message to report the recipient and request its 
> authorization?
> 
> Thanks.
> 
> Kylin Wei 
> 
> 
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 


-- 

Magnus Westerlund

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

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



From mmusic-bounces@ietf.org Mon Jun 05 17:11:46 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FnMMT-0004sV-6A; Mon, 05 Jun 2006 17:11:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FnMMR-0004sQ-TG
	for mmusic@ietf.org; Mon, 05 Jun 2006 17:11:43 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnMMR-0002Ys-Ro
	for mmusic@ietf.org; Mon, 05 Jun 2006 17:11:43 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FnML2-0007rM-Fk
	for mmusic@ietf.org; Mon, 05 Jun 2006 17:10:17 -0400
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k55LAEhv001182
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <mmusic@ietf.org>; Mon, 5 Jun 2006 14:10:15 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by crowley.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k55LACYl000030
	for <mmusic@ietf.org>; Mon, 5 Jun 2006 14:10:14 -0700 (PDT)
Received: from NAEX01.qualcomm.com ([129.46.51.60]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jun 2006 14:10:11 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 5 Jun 2006 14:10:09 -0700
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B0178B465@NAEX01.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Usage of stream bandwidth attribute in  SDP offer/answer
Thread-Index: AcaI5G03zN9xsRXfRJOEKNA5/iL5Ug==
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: <mmusic@ietf.org>
X-OriginalArrivalTime: 05 Jun 2006 21:10:11.0479 (UTC)
	FILETIME=[6E855270:01C688E4]
X-Spam-Score: -1.5 (-)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Subject: [MMUSIC] Usage of stream bandwidth attribute in  SDP offer/answer
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

Hello MMUSIC folks,

I am trying to build an SDP offer/answer for a point to point call using
RFC3264 SDP offer/answer model. The offerer (alice) would like to convey
that it would like to send and receive audio at 16000bps, send video at
64000 bps and receive video at 128000bps. The answerer(bob) would like
to receive video at 32000bps and send video at 64000bps. Below is the
SDP exchange between alice and bob.=20


[SDP offer]
      v=3D0
      o=3Dalice 2890844526 2890844526 IN IP4 host.sd.example.com
      s=3D=20
      c=3DIN IP4 host.sd.example.com
      t=3D0 0
      m=3Daudio 49170 RTP/AVP 0
      a=3Drtpmap:0 PCMU/8000
      b=3DAS:16000
      m=3Dvideo 51372 RTP/AVP 31
      a=3Drtpmap:31 H261/90000=20
      b=3DAS:64000
      a=3Dsendonly
      m=3Dvideo 51374 RTP/AVP 31
      a=3Drtpmap:31 H261/90000
      b=3DAS:128000
      a=3Drecvonly

[SDP answer]
      v=3D0
      o=3D bob 2808844564 2808844564 IN IP4 host.la.example.com
      s=3D=20
      c=3DIN IP4 host.la.example.com
      t=3D0 0
      m=3Daudio 52124 RTP/AVP 0
      a=3Drtpmap:0 PCMU/8000
      b=3DAS:16000
      m=3Dvideo 53212 RTP/AVP 31
      a=3Drtpmap:31 H261/90000
      b=3DAS:32000
      a=3Drecvonly
      m=3Dvideo 54416 RTP/AVP 31
      a=3Drtpmap:31 H261/90000
      b=3DAS:64000
      a=3Dsendonly     =20


Is the "b=3DAS" parameter allowed to be used this way to communicate =
that
the offerer would like to send/receive the stream with the specified
bandwidth?=20

RFC3264 (Sec 5.1, Page 7) states "If the bandwidth parameter is present
for a stream, it indicates the desired bandwidth that the offerer would
like to receive". From the RFC text, it is not clear whether the
bandwidth parameter can also be used to indicate the desired bandwidth
the offerer would like transmit (atleast when a=3Dsendonly)

Cheers,
Hari D

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



From mmusic-bounces@ietf.org Mon Jun 05 17:33:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FnMhe-0002ph-1c; Mon, 05 Jun 2006 17:33:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FnMhc-0002pc-C1
	for mmusic@ietf.org; Mon, 05 Jun 2006 17:33:36 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnMhZ-0003TU-RM
	for mmusic@ietf.org; Mon, 05 Jun 2006 17:33:36 -0400
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-5.cisco.com with ESMTP; 05 Jun 2006 14:33:33 -0700
X-IronPort-AV: i="4.05,211,1146466800"; 
	d="scan'208"; a="289149264:sNHT66997992"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id k55LXVI3016816; 
	Mon, 5 Jun 2006 14:33:31 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k55LWacn008333;
	Mon, 5 Jun 2006 14:33:26 -0700 (PDT)
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.211);
	Mon, 5 Jun 2006 14:33:09 -0700
Received: from jmpolk-wxp.cisco.com ([10.21.96.20]) by
	xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Mon, 5 Jun 2006 14:33:08 -0700
Message-Id: <4.3.2.7.2.20060605163129.03565c88@email.cisco.com>
X-Sender: jmpolk@email.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 05 Jun 2006 16:33:07 -0500
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>, <mmusic@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [MMUSIC] Usage of stream bandwidth attribute in  SDP offer/answer
In-Reply-To: <2CA3E1B6CEC064449CAA7D0FAB46079B0178B465@NAEX01.na.qualcom m.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 05 Jun 2006 21:33:09.0063 (UTC)
	FILETIME=[A39FF570:01C688E7]
DKIM-Signature: a=rsa-sha1; q=dns; l=2211; t=1149543211; x=1150407211;
	c=relaxed/simple; s=sjdkim7001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jmpolk@cisco.com;
	z=From:=22James=20M.=20Polk=22=20<jmpolk@cisco.com>
	|Subject:Re=3A=20[MMUSIC]=20Usage=20of=20stream=20bandwidth=20attribute=20in=20=2
	0SDP=0A=20=20offer/answer;
	X=v=3Dcisco.com=3B=20h=3Dpx86vo9W8EBCWW4Iov70o+v9LwY=3D;
	b=jjShfmK98mjU+j+ZtoeSIcFf43kOg+wR1x+0Bj+7hwyUP8sKIXut6D/f5bjRDfxJNV0pgnEK
	tc9XI0Eh0IgnJUzATtWMDIum2NGeOKgEms7Ks9HlLedqlUAuH9J75XMi;
Authentication-Results: sj-dkim-7.cisco.com; header.From=jmpolk@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
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

Asside from your BW question, how can Alice state in SDP what Bob's receive 
port number is?  Isn't that against the rules?

At 02:10 PM 6/5/2006 -0700, Desineni, Harikishan wrote:
>Hello MMUSIC folks,
>
>I am trying to build an SDP offer/answer for a point to point call using
>RFC3264 SDP offer/answer model. The offerer (alice) would like to convey
>that it would like to send and receive audio at 16000bps, send video at
>64000 bps and receive video at 128000bps. The answerer(bob) would like
>to receive video at 32000bps and send video at 64000bps. Below is the
>SDP exchange between alice and bob.
>
>
>[SDP offer]
>       v=0
>       o=alice 2890844526 2890844526 IN IP4 host.sd.example.com
>       s=
>       c=IN IP4 host.sd.example.com
>       t=0 0
>       m=audio 49170 RTP/AVP 0
>       a=rtpmap:0 PCMU/8000
>       b=AS:16000
>       m=video 51372 RTP/AVP 31
>       a=rtpmap:31 H261/90000
>       b=AS:64000
>       a=sendonly
>       m=video 51374 RTP/AVP 31
>       a=rtpmap:31 H261/90000
>       b=AS:128000
>       a=recvonly
>
>[SDP answer]
>       v=0
>       o= bob 2808844564 2808844564 IN IP4 host.la.example.com
>       s=
>       c=IN IP4 host.la.example.com
>       t=0 0
>       m=audio 52124 RTP/AVP 0
>       a=rtpmap:0 PCMU/8000
>       b=AS:16000
>       m=video 53212 RTP/AVP 31
>       a=rtpmap:31 H261/90000
>       b=AS:32000
>       a=recvonly
>       m=video 54416 RTP/AVP 31
>       a=rtpmap:31 H261/90000
>       b=AS:64000
>       a=sendonly
>
>
>Is the "b=AS" parameter allowed to be used this way to communicate that
>the offerer would like to send/receive the stream with the specified
>bandwidth?
>
>RFC3264 (Sec 5.1, Page 7) states "If the bandwidth parameter is present
>for a stream, it indicates the desired bandwidth that the offerer would
>like to receive". From the RFC text, it is not clear whether the
>bandwidth parameter can also be used to indicate the desired bandwidth
>the offerer would like transmit (atleast when a=sendonly)
>
>Cheers,
>Hari D
>
>_______________________________________________
>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 Jun 05 18:28:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FnNYX-0005pz-2F; Mon, 05 Jun 2006 18:28:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FnNYV-0005pt-34
	for mmusic@ietf.org; Mon, 05 Jun 2006 18:28:15 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnNYT-0001pB-LS
	for mmusic@ietf.org; Mon, 05 Jun 2006 18:28:15 -0400
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k55MSBGv009709
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 5 Jun 2006 15:28:12 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by crowley.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k55MS8Xl026142; Mon, 5 Jun 2006 15:28:11 -0700 (PDT)
Received: from NAEX01.qualcomm.com ([129.46.51.60]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jun 2006 15:28:07 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] Usage of stream bandwidth attribute in SDP offer/answer
Date: Mon, 5 Jun 2006 15:28:04 -0700
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B0178B4C4@NAEX01.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] Usage of stream bandwidth attribute in SDP offer/answer
Thread-Index: AcaI6DsM6JlTh0epRWugN7eZPpMNuwABk/VQ
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: "James M. Polk" <jmpolk@cisco.com>, <mmusic@ietf.org>
X-OriginalArrivalTime: 05 Jun 2006 22:28:07.0959 (UTC)
	FILETIME=[51EB8A70:01C688EF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
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

>From RFC3264, Sec 5.1, Page 6

"For sendonly RTP streams, the address and port number indirectly
indicate where the offerer wants to receive RTCP reports".=20

In the example given by me, Alice can receive RTCP receiver reports on
port 51373. The same applies to the sendonly stream in the response from
Bob (Bob can receive RTCP receiver reports on port 54417.

Cheers,
Hari D

> -----Original Message-----
> From: James M. Polk [mailto:jmpolk@cisco.com]
> Sent: Monday, June 05, 2006 2:33 PM
> To: Desineni, Harikishan; mmusic@ietf.org
> Subject: Re: [MMUSIC] Usage of stream bandwidth attribute in SDP
> offer/answer
>=20
> Asside from your BW question, how can Alice state in SDP what Bob's
> receive
> port number is?  Isn't that against the rules?
>=20
> At 02:10 PM 6/5/2006 -0700, Desineni, Harikishan wrote:
> >Hello MMUSIC folks,
> >
> >I am trying to build an SDP offer/answer for a point to point call
using
> >RFC3264 SDP offer/answer model. The offerer (alice) would like to
convey
> >that it would like to send and receive audio at 16000bps, send video
at
> >64000 bps and receive video at 128000bps. The answerer(bob) would
like
> >to receive video at 32000bps and send video at 64000bps. Below is the
> >SDP exchange between alice and bob.
> >
> >
> >[SDP offer]
> >       v=3D0
> >       o=3Dalice 2890844526 2890844526 IN IP4 host.sd.example.com
> >       s=3D
> >       c=3DIN IP4 host.sd.example.com
> >       t=3D0 0
> >       m=3Daudio 49170 RTP/AVP 0
> >       a=3Drtpmap:0 PCMU/8000
> >       b=3DAS:16000
> >       m=3Dvideo 51372 RTP/AVP 31
> >       a=3Drtpmap:31 H261/90000
> >       b=3DAS:64000
> >       a=3Dsendonly
> >       m=3Dvideo 51374 RTP/AVP 31
> >       a=3Drtpmap:31 H261/90000
> >       b=3DAS:128000
> >       a=3Drecvonly
> >
> >[SDP answer]
> >       v=3D0
> >       o=3D bob 2808844564 2808844564 IN IP4 host.la.example.com
> >       s=3D
> >       c=3DIN IP4 host.la.example.com
> >       t=3D0 0
> >       m=3Daudio 52124 RTP/AVP 0
> >       a=3Drtpmap:0 PCMU/8000
> >       b=3DAS:16000
> >       m=3Dvideo 53212 RTP/AVP 31
> >       a=3Drtpmap:31 H261/90000
> >       b=3DAS:32000
> >       a=3Drecvonly
> >       m=3Dvideo 54416 RTP/AVP 31
> >       a=3Drtpmap:31 H261/90000
> >       b=3DAS:64000
> >       a=3Dsendonly
> >
> >
> >Is the "b=3DAS" parameter allowed to be used this way to communicate
that
> >the offerer would like to send/receive the stream with the specified
> >bandwidth?
> >
> >RFC3264 (Sec 5.1, Page 7) states "If the bandwidth parameter is
present
> >for a stream, it indicates the desired bandwidth that the offerer
would
> >like to receive". From the RFC text, it is not clear whether the
> >bandwidth parameter can also be used to indicate the desired
bandwidth
> >the offerer would like transmit (atleast when a=3Dsendonly)
> >
> >Cheers,
> >Hari D
> >
> >_______________________________________________
> >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 Jun 06 02:22:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FnUxS-0007CQ-N7; Tue, 06 Jun 2006 02:22:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FnUxR-0007BA-G0
	for mmusic@ietf.org; Tue, 06 Jun 2006 02:22:29 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnUkT-00034f-Ts
	for mmusic@ietf.org; Tue, 06 Jun 2006 02:09:07 -0400
Content-class: urn:content-classes:message
Subject: RE: [MMUSIC] Usage of stream bandwidth attribute in SDP offer/answer
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 6 Jun 2006 09:07:00 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Message-ID: <144ED8561CE90C41A3E5908EDECE315C0393C63F@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] Usage of stream bandwidth attribute in SDP offer/answer
Thread-Index: AcaI5G03zN9xsRXfRJOEKNA5/iL5UgASmh0w
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>,
	<mmusic@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
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,
My understanding is that only the receive rate is important and it is a
maximum rate. The sender may send any rate up to the maximum rate
supported by the receiver.
Video does not have a fixed "frame" size. The size of the frame may
change based on the information. =20


Roni Even
=20

> -----Original Message-----
> From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> Sent: Tuesday, June 06, 2006 12:10 AM
> To: mmusic@ietf.org
> Subject: [MMUSIC] Usage of stream bandwidth attribute in SDP
offer/answer
>=20
> Hello MMUSIC folks,
>=20
> I am trying to build an SDP offer/answer for a point to point call
using
> RFC3264 SDP offer/answer model. The offerer (alice) would like to
convey
> that it would like to send and receive audio at 16000bps, send video
at
> 64000 bps and receive video at 128000bps. The answerer(bob) would like
> to receive video at 32000bps and send video at 64000bps. Below is the
> SDP exchange between alice and bob.
>=20
>=20
> [SDP offer]
>       v=3D0
>       o=3Dalice 2890844526 2890844526 IN IP4 host.sd.example.com
>       s=3D
>       c=3DIN IP4 host.sd.example.com
>       t=3D0 0
>       m=3Daudio 49170 RTP/AVP 0
>       a=3Drtpmap:0 PCMU/8000
>       b=3DAS:16000
>       m=3Dvideo 51372 RTP/AVP 31
>       a=3Drtpmap:31 H261/90000
>       b=3DAS:64000
>       a=3Dsendonly
>       m=3Dvideo 51374 RTP/AVP 31
>       a=3Drtpmap:31 H261/90000
>       b=3DAS:128000
>       a=3Drecvonly
>=20
> [SDP answer]
>       v=3D0
>       o=3D bob 2808844564 2808844564 IN IP4 host.la.example.com
>       s=3D
>       c=3DIN IP4 host.la.example.com
>       t=3D0 0
>       m=3Daudio 52124 RTP/AVP 0
>       a=3Drtpmap:0 PCMU/8000
>       b=3DAS:16000
>       m=3Dvideo 53212 RTP/AVP 31
>       a=3Drtpmap:31 H261/90000
>       b=3DAS:32000
>       a=3Drecvonly
>       m=3Dvideo 54416 RTP/AVP 31
>       a=3Drtpmap:31 H261/90000
>       b=3DAS:64000
>       a=3Dsendonly
>=20
>=20
> Is the "b=3DAS" parameter allowed to be used this way to communicate
that
> the offerer would like to send/receive the stream with the specified
> bandwidth?
>=20
> RFC3264 (Sec 5.1, Page 7) states "If the bandwidth parameter is
present
> for a stream, it indicates the desired bandwidth that the offerer
would
> like to receive". From the RFC text, it is not clear whether the
> bandwidth parameter can also be used to indicate the desired bandwidth
> the offerer would like transmit (atleast when a=3Dsendonly)
>=20
> Cheers,
> Hari D
>=20
> _______________________________________________
> 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 Jun 06 02:22:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FnUxV-0007HM-Vw; Tue, 06 Jun 2006 02:22:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FnUxK-00073G-DR
	for mmusic@ietf.org; Tue, 06 Jun 2006 02:22:22 -0400
Received: from szxga01-in.huawei.com ([61.144.161.53] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnUnd-00038E-33
	for mmusic@ietf.org; Tue, 06 Jun 2006 02:12:22 -0400
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J0F00835D75DE@szxga01-in.huawei.com> for
	mmusic@ietf.org; Tue, 06 Jun 2006 14:11:29 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J0F00EVKD756U@szxga01-in.huawei.com> for
	mmusic@ietf.org; Tue, 06 Jun 2006 14:11:29 +0800 (CST)
Received: from w52438 ([10.164.5.32])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0J0F001DLDM1JL@szxml04-in.huawei.com> for
	mmusic@ietf.org; Tue, 06 Jun 2006 14:20:34 +0800 (CST)
Date: Tue, 06 Jun 2006 14:10:02 +0800
From: Kylin Wei <weiqikun@huawei.com>
Subject: RE: [MMUSIC] Usage of stream bandwidth attribute in SDP offer/answer
In-reply-to: <2CA3E1B6CEC064449CAA7D0FAB46079B0178B465@NAEX01.na.qualcomm.com>
To: "'Desineni, Harikishan'" <hdesinen@qualcomm.com>
Message-id: <000001c6892f$dc11cc60$2005a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
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 Harikishan:
Desineni, Harikishan wrote: 
> Is the "b=AS" parameter allowed to be used this way to communicate
that
> the offerer would like to send/receive the stream with the specified
> bandwidth?

If Alice offers several alternative bandwidths by "a=alt" attribute, Bob
can 
select one of them to start with.
I think that it may be improper to use this way to indicate directly the
specified 
bandwidth.  

Kylin Wei 




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



From mmusic-bounces@ietf.org Tue Jun 06 17:01:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fnifd-0004ey-Ef; Tue, 06 Jun 2006 17:01:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fnifc-0004er-EK
	for mmusic@ietf.org; Tue, 06 Jun 2006 17:01:00 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fnifb-0007WF-2c
	for mmusic@ietf.org; Tue, 06 Jun 2006 17:01:00 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k56L0ePm023341
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 6 Jun 2006 14:00:41 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by magus.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k56L0Glm008082; Tue, 6 Jun 2006 14:00:38 -0700 (PDT)
Received: from NAEX01.qualcomm.com ([129.46.51.60]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 Jun 2006 14:00:14 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] Usage of stream bandwidth attribute in SDP offer/answer
Date: Tue, 6 Jun 2006 14:00:16 -0700
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B0178B65E@NAEX01.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] Usage of stream bandwidth attribute in SDP offer/answer
Thread-Index: AcaJMVCR4cYBad2eRhalm2T+nP9yswAemKaA
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: "Kylin Wei" <weiqikun@huawei.com>
X-OriginalArrivalTime: 06 Jun 2006 21:00:14.0967 (UTC)
	FILETIME=[35629070:01C689AC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
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

Is the "a=3Dalt" attribute already defined in some draft/RFC or are you
suggesting that this attribute be newly defined to handle the particular
scenario I am trying to address?


Cheers,
Hari

> -----Original Message-----
> From: Kylin Wei [mailto:weiqikun@huawei.com]
> Sent: Monday, June 05, 2006 11:10 PM
> To: Desineni, Harikishan
> Cc: mmusic@ietf.org
> Subject: RE: [MMUSIC] Usage of stream bandwidth attribute in SDP
> offer/answer
>=20
> Hi Harikishan:
> Desineni, Harikishan wrote:
> > Is the "b=3DAS" parameter allowed to be used this way to communicate
> that
> > the offerer would like to send/receive the stream with the specified
> > bandwidth?
>=20
> If Alice offers several alternative bandwidths by "a=3Dalt" attribute,
Bob
> can
> select one of them to start with.
> I think that it may be improper to use this way to indicate directly
the
> specified
> bandwidth.
>=20
> Kylin Wei
>=20
>=20


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



From mmusic-bounces@ietf.org Tue Jun 06 17:35:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FnjDP-0007bR-Kj; Tue, 06 Jun 2006 17:35:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FnjDN-0007bM-V0
	for mmusic@ietf.org; Tue, 06 Jun 2006 17:35:53 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnjDM-0004w7-6c
	for mmusic@ietf.org; Tue, 06 Jun 2006 17:35:53 -0400
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	58C244F0001; Tue,  6 Jun 2006 23:35:51 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 Jun 2006 23:35:50 +0200
Received: from [153.88.17.93] ([153.88.17.93]) by esealmw128.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 Jun 2006 23:35:50 +0200
Message-ID: <4485F536.5030706@ericsson.com>
Date: Tue, 06 Jun 2006 23:35:50 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>
Subject: Re: [MMUSIC] Usage of stream bandwidth attribute in SDP offer/answer
References: <2CA3E1B6CEC064449CAA7D0FAB46079B0178B65E@NAEX01.na.qualcomm.com>
In-Reply-To: <2CA3E1B6CEC064449CAA7D0FAB46079B0178B65E@NAEX01.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Jun 2006 21:35:50.0362 (UTC)
	FILETIME=[2E2DFBA0:01C689B1]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
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,

The a=alt is an attribute defined by 3GPP (TS 26.234) for use in 
streaming and have no defined behavior in an offer/answer exchange. I 
would propose staying away from doing that. It will get you into a mess.

Cheers

Magnus

Desineni, Harikishan wrote:
> Is the "a=alt" attribute already defined in some draft/RFC or are you
> suggesting that this attribute be newly defined to handle the particular
> scenario I am trying to address?
> 
> 
> Cheers,
> Hari
> 
>> -----Original Message-----
>> From: Kylin Wei [mailto:weiqikun@huawei.com]
>> Sent: Monday, June 05, 2006 11:10 PM
>> To: Desineni, Harikishan
>> Cc: mmusic@ietf.org
>> Subject: RE: [MMUSIC] Usage of stream bandwidth attribute in SDP
>> offer/answer
>>
>> Hi Harikishan:
>> Desineni, Harikishan wrote:
>>> Is the "b=AS" parameter allowed to be used this way to communicate
>> that
>>> the offerer would like to send/receive the stream with the specified
>>> bandwidth?
>> If Alice offers several alternative bandwidths by "a=alt" attribute,
> Bob
>> can
>> select one of them to start with.
>> I think that it may be improper to use this way to indicate directly
> the
>> specified
>> bandwidth.
>>
>> Kylin Wei
>>
>>
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 


-- 

Magnus Westerlund

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

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



From mmusic-bounces@ietf.org Tue Jun 06 21:34:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fnmw5-0007aA-Fs; Tue, 06 Jun 2006 21:34:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fnmw3-0007a5-V3
	for mmusic@ietf.org; Tue, 06 Jun 2006 21:34:15 -0400
Received: from nat1.alcatel-sbell.com.cn ([202.96.203.177]
	helo=mail.alcatel-sbell.com.cn)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fnmw2-0008Sv-7Y
	for mmusic@ietf.org; Tue, 06 Jun 2006 21:34:15 -0400
Received: from asbmail4.sbell.com.cn (localhost [127.0.0.1])
	by mail.alcatel-sbell.com.cn (8.12.11/8.12.11/Alcanet1.0) with ESMTP id
	k571Tg39024648 for <mmusic@ietf.org>; Wed, 7 Jun 2006 09:29:44 +0800
Received: from asbmail2.sbell.com.cn ([172.24.208.62]) by 
	asbmail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.6713); Wed, 7 Jun 
	2006 09:34:10 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset=gb2312
Content-Transfer-Encoding: quoted-printable
Date: Wed, 7 Jun 2006 09:34:10 +0800
Message-ID: <9570C1261494D54D9D3115BC2C83429A0BB834@asbmail2.sbell.com.cn>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: How to create a multicast session using SIP?
Thread-Index: AcaJCMbApG0NRQvhRKSm/M3jdjcKPwAyAjhQ
From: "CTO YAN Renxiang" <Renxiang.Yan@alcatel-sbell.com.cn>
To: <mmusic@ietf.org>
X-OriginalArrivalTime: 07 Jun 2006 01:34:11.0148 (UTC) 
	FILETIME=[7A1CC0C0:01C689D2]
X-imss-version: 2.040
X-imss-result: Passed
X-imss-approveListMatch: *@alcatel-sbell.com.cn
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: [MMUSIC] question about multicast and SIP?
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, all,

Two questions about multicast and SIP:
(1) How to join a multicast session using SIP? Is it possilbe?=20
and,
(2)How to limit unauthorized user to join a multicast session using SIP?

Regards,
Renxiang

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



From mmusic-bounces@ietf.org Wed Jun 07 17:24:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fo5Vo-0005SF-6q; Wed, 07 Jun 2006 17:24:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fo5Vm-0005SA-QQ
	for mmusic@ietf.org; Wed, 07 Jun 2006 17:24:22 -0400
Received: from tpamail2.verizon.com ([192.76.82.136])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fo5Vl-00054j-7v
	for mmusic@ietf.org; Wed, 07 Jun 2006 17:24:22 -0400
Received: from smtpftw3.verizon.com (smtpftw3.verizon.com [138.83.140.92])
	by tpamail2.verizon.com (8.13.3/8.13.3) with ESMTP id k57LOJEI027462
	for <mmusic@ietf.org>; Wed, 7 Jun 2006 17:24:19 -0400 (EDT)
Received: from irvp1cvmma01.vzh.ent.verizon.com (irvp1cvmma01.verizon.com
	[138.83.34.82])
	by smtpftw3.verizon.com (8.13.3/8.13.3) with ESMTP id k57LNmHX028018
	for <mmusic@ietf.org>; Wed, 7 Jun 2006 17:24:18 -0400 (EDT)
Received: from 138.83.34.48 by irvp1cvmma01.vzh.ent.verizon.com with
	ESMTP (SMTP Relay); Wed, 07 Jun 2006 17:24:08 -0400
X-Server-Uuid: 551EF313-C6C9-4803-9929-39830E3D7904
Received: from dwsmtp01.core.verizon.com (dwsmtp01.verizon.com
	[138.83.35.62]) by coregate2.verizon.com (8.13.3/8.13.3) with ESMTP id
	k57LO7mO023978 for <mmusic@ietf.org>; Wed, 7 Jun 2006 16:24:08 -0500 (
	CDT)
Date: Wed, 7 Jun 2006 17:24:04 -0400
MIME-Version: 1.0
To: mmusic@ietf.org
cc: 
From: steven.d.whitehead@verizon.com
X-Mailer: Microsoft Outlook v 11.00.6353, MSOC v 2.00.4007.00
Message-ID: <OF1ABD3D8F.566D4E60-ON04257186.0074C9A8@CORE.VERIZON.COM>
X-MIMETrack: Serialize by Router on DWSMTP01/HSVR/Verizon(Release
	6.5.4HF453 | August 4, 2005) at 06/07/2006 16:24:07, Serialize complete
	at 06/07/2006 16:24:07
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-WSS-ID: 68999C727J0258510-01-01
Content-Type: text/plain;
 charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Subject: [MMUSIC] Is RTSP a "control" media or an "application" media?
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

If I wanted to use SDP to create a session description that included one
or more "content" media streams that were to be managed by an "RTSP
control" media stream, what would be the best way to describe the RTSP
media stream, as a "control" or an "application".

That is, would it be something like this:
m=control <port> TCP RTSP

Or more like this:
m=application <port> TCP RTSP

Reading RFC 2327 it says in the section on Media Announcements:
	"control" is used to specify an additional 
       conference control channel for the session.

Is RTSP considered a "conference control channel"?

Thanks,

-Steve


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



From mmusic-bounces@ietf.org Thu Jun 08 23:45:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FoXvz-0006Kq-Kb; Thu, 08 Jun 2006 23:45:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FoXvy-0006Kl-Le
	for mmusic@ietf.org; Thu, 08 Jun 2006 23:45:18 -0400
Received: from szxga01-in.huawei.com ([61.144.161.53] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FoXvv-0003ke-OM
	for mmusic@ietf.org; Thu, 08 Jun 2006 23:45:18 -0400
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J0K004AQQGAPS@szxga01-in.huawei.com> for
	mmusic@ietf.org; Fri, 09 Jun 2006 11:45:46 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J0K00DXDQGA3C@szxga01-in.huawei.com> for
	mmusic@ietf.org; Fri, 09 Jun 2006 11:45:46 +0800 (CST)
Received: from w52438 ([10.164.5.32])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0J0K00NW1QFP32@szxml03-in.huawei.com> for
	mmusic@ietf.org; Fri, 09 Jun 2006 11:45:33 +0800 (CST)
Date: Fri, 09 Jun 2006 11:44:15 +0800
From: Kylin Wei <weiqikun@huawei.com>
Subject: RE: [MMUSIC] Is RTSP a "control" media or an "application" media?
In-reply-to: <OF1ABD3D8F.566D4E60-ON04257186.0074C9A8@CORE.VERIZON.COM>
To: steven.d.whitehead@verizon.com
Message-id: <000001c68b76$fdca6760$2005a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
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 Steve:

I don't know much about your question, but I expect my reply would be
helpful for you.
Follow example is origin text of rfc2326bis.

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
         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 172.16.2.93
         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"

Please note that " a=control: trackID=1" and " a=control: trackID=4" are
two RTSP URIs.
Their full descriptions are "rtsp://example.com/twister.3gp/trackID=1"
and "rtsp://example.com/twister.3gp/trackID=4.".
In RTSP the used URIs are as general rule in fact URL's as they gives a
location for the resource.

Kylin Wei 

> -----Original Message-----
> From: steven.d.whitehead@verizon.com
[mailto:steven.d.whitehead@verizon.com]
> Sent: Thursday, June 08, 2006 5:24 AM
> To: mmusic@ietf.org
> Subject: [MMUSIC] Is RTSP a "control" media or an "application" media?
> 
> If I wanted to use SDP to create a session description that included
one
> or more "content" media streams that were to be managed by an "RTSP
> control" media stream, what would be the best way to describe the RTSP
> media stream, as a "control" or an "application".
> 
> That is, would it be something like this:
> m=control <port> TCP RTSP
> 
> Or more like this:
> m=application <port> TCP RTSP
> 
> Reading RFC 2327 it says in the section on Media Announcements:
> 	"control" is used to specify an additional
>        conference control channel for the session.
> 
> Is RTSP considered a "conference control channel"?
> 
> Thanks,
> 
> -Steve
> 
> 
> _______________________________________________
> 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 Jun 13 11:40:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FqAzx-0003E2-4V; Tue, 13 Jun 2006 11:40:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FqAzv-0003Dx-3x
	for mmusic@ietf.org; Tue, 13 Jun 2006 11:40:07 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FqAzt-00085G-FE
	for mmusic@ietf.org; Tue, 13 Jun 2006 11:40:07 -0400
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	E5550500002; Tue, 13 Jun 2006 17:40:04 +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, 13 Jun 2006 17:40:04 +0200
Received: from [147.214.30.119] ([147.214.30.119]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 13 Jun 2006 17:40:03 +0200
Message-ID: <448EDC53.7090308@ericsson.com>
Date: Tue, 13 Jun 2006 17:40:03 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: steven.d.whitehead@verizon.com
Subject: Re: [MMUSIC] Is RTSP a "control" media or an "application" media?
References: <OF1ABD3D8F.566D4E60-ON04257186.0074C9A8@CORE.VERIZON.COM>
In-Reply-To: <OF1ABD3D8F.566D4E60-ON04257186.0074C9A8@CORE.VERIZON.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Jun 2006 15:40:03.0961 (UTC)
	FILETIME=[A39FEE90:01C68EFF]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
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 Steve,

One normally starts with an RTSP URI. Use that the go to the server with 
the content. Then request the media configuration information as an SDP 
using RTSP. As Wei pointed out that SDP will indicate the RTSP URI for 
the individual resources part of an aggregate.

Cheers

Magnus

steven.d.whitehead@verizon.com wrote:
> If I wanted to use SDP to create a session description that included one
> or more "content" media streams that were to be managed by an "RTSP
> control" media stream, what would be the best way to describe the RTSP
> media stream, as a "control" or an "application".
> 
> That is, would it be something like this:
> m=control <port> TCP RTSP
> 
> Or more like this:
> m=application <port> TCP RTSP
> 
> Reading RFC 2327 it says in the section on Media Announcements:
> 	"control" is used to specify an additional 
>        conference control channel for the session.
> 
> Is RTSP considered a "conference control channel"?
> 
> Thanks,
> 
> -Steve
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 


-- 

Magnus Westerlund

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

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



From mmusic-bounces@ietf.org Tue Jun 13 15:50:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FqEtw-0003Ek-2q; Tue, 13 Jun 2006 15:50:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FqEtn-0003De-N5; Tue, 13 Jun 2006 15:50:03 -0400
Received: from willow.neustar.com ([209.173.53.84])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FqEtm-0007L2-EJ; Tue, 13 Jun 2006 15:50:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k5DJo2Rx021307
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Tue, 13 Jun 2006 19:50:02 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FqEtm-0007gj-4C; Tue, 13 Jun 2006 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1FqEtm-0007gj-4C@stiedprstage1.ietf.org>
Date: Tue, 13 Jun 2006 15:50:02 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-connectivity-precon-02.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		: Connectivity Preconditions for Session Description Protocol Media Streams
	Author(s)	: F. Andreasen, et al.
	Filename	: draft-ietf-mmusic-connectivity-precon-02.txt
	Pages		: 18
	Date		: 2006-6-13
	
This document defines a new connectivity precondition for the Session
Description Protocol precondition framework described in RFC 3312
(and its update, RFC4032).  A connectivity precondition can be used
to delay session establishment or modification until media stream
connectivity has been verified successfully.  The method of
verification may vary depending on the type of transport used for the
media.  For reliable connection-oriented transports such as TCP
verification is achieved by successful connection establishment.  For
unreliable datagram transports such as UDP, verification involves
probing the stream with data or control packets.

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

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


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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-connectivity-precon-02.txt

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

Content-Type: text/plain
Content-ID: <2006-6-13144454.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 Jun 14 02:02:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FqOS8-0001ww-1v; Wed, 14 Jun 2006 02:02:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FqOS6-0001wr-7y
	for mmusic@ietf.org; Wed, 14 Jun 2006 02:02:06 -0400
Received: from mgw-ext12.nokia.com ([131.228.20.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FqOS4-0000Xl-IM
	for mmusic@ietf.org; Wed, 14 Jun 2006 02:02:06 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext12.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k5E622sN027780; Wed, 14 Jun 2006 09:02:03 +0300
Received: from esebh002.NOE.Nokia.com ([172.21.138.77]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 14 Jun 2006 09:02:02 +0300
Received: from [127.0.0.1] ([172.21.35.108]) by esebh002.NOE.Nokia.com with
	Microsoft SMTPSVC(5.0.2195.6881); Wed, 14 Jun 2006 09:02:02 +0300
Message-ID: <448FA65A.9080606@nokia.com>
Date: Wed, 14 Jun 2006 09:02:02 +0300
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: mmusic@ietf.org
Content-Type: multipart/mixed; boundary="------------020100070008040902010203"
X-OriginalArrivalTime: 14 Jun 2006 06:02:02.0221 (UTC)
	FILETIME=[0E1C21D0:01C68F78]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b6657e60309a1317174c9db2ae5f227
Cc: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	"Isomaki Markus \(Nokia-TP/Espoo\)" <Markus.Isomaki@nokia.com>
Subject: [MMUSIC] [Fwd: I-D
	ACTION:draft-garcia-mmusic-file-transfer-mech-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

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

As you may have noticed, we have just submitted an Internet-Draft that 
proposes an SDP offer/answer mechanism for file transfer.

This document was previously addressed to the SIPPING WG, but we 
realized we didn't extend SIP at all, but just SDP. We have tried to 
address all the comments we got in the past, so please, review this 
version and comment it.

Regards,

          Miguel


-- 
Miguel A. Garcia           tel:+358-50-4804586
sip:miguel.an.garcia@openlaboratory.net
Nokia Research Center      Helsinki, Finland

--------------020100070008040902010203
Content-Type: message/rfc822;
	name*0="I-D ACTION:draft-garcia-mmusic-file-transfer-mech-00.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
	filename*0="I-D ACTION:draft-garcia-mmusic-file-transfer-mech-00.txt"

Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebe104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 14 Jun 2006 01:50:57 +0300
Received: from esebh106.NOE.Nokia.com ([172.21.138.213]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 14 Jun 2006 01:50:56 +0300
Received: from esdks003.ntc.nokia.com ([172.21.138.158]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 14 Jun 2006 01:50:55 +0300
X-Scanned: Wed, 14 Jun 2006 01:50:41 +0300 Nokia Message Protector V1.3.35
	2005042208 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id k5DMofP8007400;
	Wed, 14 Jun 2006 01:50:41 +0300
Received: from mgw-ext01.nokia.com (131.228.20.93)
	by esdks003.ntc.nokia.com 00yiLw5s; Wed, 14 Jun 2006 01:50:41 EEST
Received: from megatron.ietf.org (stiedprmman1.ietf.org [156.154.16.145])
	by mgw-ext01.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k5DModV4001224
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 14 Jun 2006 01:50:40 +0300
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FqHiK-0006qA-Fp; Tue, 13 Jun 2006 18:50:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FqHi1-0006VX-6B
	for i-d-announce@ietf.org; Tue, 13 Jun 2006 18:50:05 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FqHi1-0003NE-1f
	for i-d-announce@ietf.org; Tue, 13 Jun 2006 18:50:05 -0400
Received: from chsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.24.129]
	helo=oak.neustar.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1FqHhy-0005XQ-Rc
	for i-d-announce@ietf.org; Tue, 13 Jun 2006 18:50:04 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k5DMo1WR006678
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <i-d-announce@ietf.org>; Tue, 13 Jun 2006 22:50:02 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FqHhx-0006dR-Jh
	for i-d-announce@ietf.org; Tue, 13 Jun 2006 18:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: 
From: "ext i-d-announce-bounces@ietf.org" <i-d-announce-bounces@ietf.org>
Message-Id: <E1FqHhx-0006dR-Jh@stiedprstage1.ietf.org>
Date: Tue, 13 Jun 2006 18:50:01 -0400
X-Spam-Score: -5.9 (-----)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Subject: I-D ACTION:draft-garcia-mmusic-file-transfer-mech-00.txt 
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: i-d-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/i-d-announce>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
Errors-To: i-d-announce-bounces@ietf.org
Return-Path: i-d-announce-bounces@ietf.org
X-OriginalArrivalTime: 13 Jun 2006 22:50:55.0852 (UTC)
	FILETIME=[D48D72C0:01C68F3B]

--NextPart

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


	Title		: Session Description Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer
	Author(s)	: M. Garcia-Martin, et al.
	Filename	: draft-garcia-mmusic-file-transfer-mech-00.txt
	Pages		: 27
	Date		: 2006-6-13
	
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.  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.
The transfer of files is initiated after a successful negotiation.
The Message Session Relay Protocol (MSRP) is defined to as the
default mechanism to actually carry the files between the endpoints.
The conventions on how to use MSRP are provided in the document.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-garcia-mmusic-file-transfer-mech-00.txt

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


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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-garcia-mmusic-file-transfer-mech-00.txt

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

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


--OtherAccess--

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

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

--NextPart--



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

--------------020100070008040902010203--





From mmusic-bounces@ietf.org Wed Jun 14 13:21:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FqZ3M-0004bd-QB; Wed, 14 Jun 2006 13:21:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FqZ3M-0004bV-9g
	for mmusic@ietf.org; Wed, 14 Jun 2006 13:21:16 -0400
Received: from ims.ku.edu.tr ([193.140.63.3] helo=ku.edu.tr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FqZ3K-0006o6-Vu
	for mmusic@ietf.org; Wed, 14 Jun 2006 13:21:16 -0400
Received: from CGURLER [172.18.2.64] by ku.edu.tr
	with NetMail ModWeb Module; Wed, 14 Jun 2006 20:47:10 +0300
From: "CIHAT GOKTUG GURLER" <CGURLER@KU.EDU.TR>
To: mmusic@ietf.org
Date: Wed, 14 Jun 2006 20:47:10 +0300
X-Mailer: NetMail ModWeb Module
X-Sender: CGURLER
MIME-Version: 1.0
Message-ID: <1150307230.bcf0c860CGURLER@KU.EDU.TR>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 1.3 (+)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Subject: [MMUSIC] Implementation of 301 Moved Permenantly
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 everyone,

I would like to build a dummy server that will forward the client to the op=
timum server for bandwidth consideration. What I do is to create a progra=
m that listens port 554. By looking at incoming ipnumber it generates a R=
TSP message in order to guide the client to the selected server. It is so=
mething like this.

For this example
Dummy server is at 172.18.2.64
Optimum server at 172.18.2.71

C-S>
DESCRIBE rtsp://172.18.2.64/audio.mp4 RTSP/1.0
CSeq: 1
Accept: application/sdp
Bandwidth: 384000
Accept-Language: en-US
User-Agent: xxxx/7.1

S-C>
Response: RTSP/1.0 301 Moved 
CSeq: 1
Location: rtsp://172.18.2.71/audi.mp4
Connection: Close


But the client useragent just hangs up instead of looking further in the ne=
w location.

It there a way which I can implement this differently?

Best wishes

C.Goktug Gurler
Koc University
Turkey



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



From mmusic-bounces@ietf.org Wed Jun 14 22:17:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FqhQ2-0005se-2C; Wed, 14 Jun 2006 22:17:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FqhQ1-0005sY-Hi
	for mmusic@ietf.org; Wed, 14 Jun 2006 22:17:13 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FqhQ0-0003fg-9x
	for mmusic@ietf.org; Wed, 14 Jun 2006 22:17:13 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12])
	by rtp-iport-2.cisco.com with ESMTP; 14 Jun 2006 22:17:13 -0400
X-IronPort-AV: i="4.06,133,1149480000"; 
	d="scan'208"; a="90082703:sNHT29901604"
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 k5F2HCYL002852; 
	Wed, 14 Jun 2006 22:17:12 -0400 (EDT)
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.211);
	Wed, 14 Jun 2006 22:17:12 -0400
Received: from [192.168.1.101] ([10.86.242.29]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 14 Jun 2006 22:17:11 -0400
Message-ID: <4490C327.4030000@cisco.com>
Date: Wed, 14 Jun 2006 22:17:11 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <4FCDEF7F-C121-49FB-AE3D-FF37A7CCAD00@magma.ca>
In-Reply-To: <4FCDEF7F-C121-49FB-AE3D-FF37A7CCAD00@magma.ca>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Jun 2006 02:17:11.0683 (UTC)
	FILETIME=[CF892530:01C69021]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: mmusic@ietf.org
Subject: [MMUSIC] Re: ICE - When to send the SIP ACK message?
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

RFC 3261 defines when to send ACK, and its sent on receipt of the 200 
OK. ICE doesn't change this, and its not clear to me why it would make 
any sense to do so.

Indeed I'd go so far as to say that it would be a mistake for the ICE 
spec to go and reconfirm the various things that are standardized and 
not changed by ICE....

Thanks,
Jonathan R.

Philip Matthews wrote:

> Jonathan:
> 
> In internal discussions on the use of ICE with SIP,
> the question of when to send the SIP ACK message came up.
> Assuming the Offer is contained in the SIP INVITE message
> and the Answer is contained in the 200 OK message,
> then should the Offerer wait to send the ACK until the connectivity
> checks complete or should it be sent immediately?
> 
> I couldn't find anything about this in the ICE spec.
> 
> My sense is that the right thing to do is to send the ACK immediately,
> since the connectivity checks may take some time to complete.
> Do you agree?
> Perhaps it would be worthwhile adding some words about this
> to the ICE spec?
> 
> - Philip
> 

-- 
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 Jun 14 23:47:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FqipA-0005TP-PX; Wed, 14 Jun 2006 23:47:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fqip9-0005TH-Sc
	for mmusic@ietf.org; Wed, 14 Jun 2006 23:47:15 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fqhg3-0004WN-21
	for mmusic@ietf.org; Wed, 14 Jun 2006 22:33:47 -0400
Received: from szxga02-in.huawei.com ([61.144.161.54] helo=huawei.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FqhOM-0006C1-Gk
	for mmusic@ietf.org; Wed, 14 Jun 2006 22:15:32 -0400
Received: from huawei.com (szxga02-in [172.24.2.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J0V00LRQQZV23@szxga02-in.huawei.com> for
	mmusic@ietf.org; Thu, 15 Jun 2006 10:31:07 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J0V00C57QZU3Q@szxga02-in.huawei.com> for
	mmusic@ietf.org; Thu, 15 Jun 2006 10:31:07 +0800 (CST)
Received: from w52438 ([10.164.5.32])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0J0V00FRAQBP3S@szxml03-in.huawei.com> for
	mmusic@ietf.org; Thu, 15 Jun 2006 10:16:41 +0800 (CST)
Date: Thu, 15 Jun 2006 10:15:14 +0800
From: Kylin Wei <weiqikun@huawei.com>
Subject: RE: [MMUSIC] Implementation of 301 Moved Permenantly
In-reply-to: <1150307230.bcf0c860CGURLER@KU.EDU.TR>
To: 'CIHAT GOKTUG GURLER' <CGURLER@KU.EDU.TR>, mmusic@ietf.org
Message-id: <000001c69021$8a14d760$2005a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcaP1xiYp444wUsMTgmzwmGfz+6CTgAScdsg
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
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 C.Goktug Gurler:

I think that you can use the "REDIRECT" method to solve this problem.
A redirect request informs the client that it must connect to another server

location.
Example:
S->C: REDIRECT rtsp://172.18.2.64/audio.mp4 RTSP/1.0
           CSeq: 1
           Location: rtsp://172.18.2.71/audi.mp4
           

Kylin Wei 

> -----Original Message-----
> From: CIHAT GOKTUG GURLER [mailto:CGURLER@KU.EDU.TR]
> Sent: Thursday, June 15, 2006 1:47 AM
> To: mmusic@ietf.org
> Subject: [MMUSIC] Implementation of 301 Moved Permenantly
> 
> Hi everyone,
> 
> I would like to build a dummy server that will forward the client to the
optimum
> server for bandwidth consideration. What I do is to create a program that
> listens port 554. By looking at incoming ipnumber it generates a RTSP
message
> in order to guide the client to the selected server. It is something like
this.
> 
> For this example
> Dummy server is at 172.18.2.64
> Optimum server at 172.18.2.71
> 
> C-S>
> DESCRIBE rtsp://172.18.2.64/audio.mp4 RTSP/1.0
> CSeq: 1
> Accept: application/sdp
> Bandwidth: 384000
> Accept-Language: en-US
> User-Agent: xxxx/7.1
> 
> S-C>
> Response: RTSP/1.0 301 Moved
> CSeq: 1
> Location: rtsp://172.18.2.71/audi.mp4
> Connection: Close
> 
> 
> But the client useragent just hangs up instead of looking further in the
new
> location.
> 
> It there a way which I can implement this differently?
> 
> Best wishes
> 
> C.Goktug Gurler
> Koc University
> Turkey
> 
> 
> 
> _______________________________________________
> 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 Jun 16 07:24:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FrCR7-0002vo-SL; Fri, 16 Jun 2006 07:24:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FrCR7-0002vj-1f
	for mmusic@ietf.org; Fri, 16 Jun 2006 07:24:25 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FrCR5-0004fi-7v
	for mmusic@ietf.org; Fri, 16 Jun 2006 07:24:25 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:62393)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1FrCR4-0006tr-SS
	for mmusic@ietf.org; Fri, 16 Jun 2006 12:24:22 +0100
Mime-Version: 1.0 (Apple Message framework v750)
Content-Transfer-Encoding: 7bit
Message-Id: <FFC8EBC1-3C4D-44B3-B9CC-2696C29A747C@csperkins.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: IETF MMUSIC WG <mmusic@ietf.org>
From: Colin Perkins <csp@csperkins.org>
Date: Fri, 16 Jun 2006 12:24:28 +0100
X-Mailer: Apple Mail (2.750)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Subject: [MMUSIC] =?iso-8859-1?q?Deadlines_and_scheduling_for_Montr=E9al_?=
	=?iso-8859-1?q?meeting?=
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,

The MMUSIC session at IETF 66 is currently scheduled for 09:00 -  
11:30 on Wednesday 12th July. This date is provisional, and may still  
change.

The cut-off date for initial (-00) draft submissions is 09:00 EDT  
(13:00 GMT) on Monday 19th June. The cut-off date for all other draft  
submissions is 09:00 EDT (13:00 GMT) on Monday 26th June. These are  
hard deadlines: no extensions will be given. You are reminded that  
the secretariat will reject submissions that don't match the I-D nits  
checklist, and are encouraged to use the validation tool at http:// 
tools.ietf.org/tools/idnits/ to check your draft before submission.

Colin

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



From mmusic-bounces@ietf.org Mon Jun 19 09:48:30 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FsK78-0008JI-RC; Mon, 19 Jun 2006 09:48:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FsK76-0008JC-T3
	for mmusic@ietf.org; Mon, 19 Jun 2006 09:48:24 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsK75-0005WA-JD
	for mmusic@ietf.org; Mon, 19 Jun 2006 09:48:24 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:52208)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1FsK74-0001uM-VQ; Mon, 19 Jun 2006 14:48:22 +0100
In-Reply-To: <FFC8EBC1-3C4D-44B3-B9CC-2696C29A747C@csperkins.org>
References: <FFC8EBC1-3C4D-44B3-B9CC-2696C29A747C@csperkins.org>
Mime-Version: 1.0 (Apple Message framework v750)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C19152A5-C040-46BF-9431-02916CA0E32D@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Mon, 19 Jun 2006 14:48:19 +0100
To: IETF MMUSIC WG <mmusic@ietf.org>
X-Mailer: Apple Mail (2.750)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: =?ISO-8859-1?Q?J=F6rg_Ott?= <jo@netlab.hut.fi>
Subject: [MMUSIC] =?iso-8859-1?q?Agenda_for_Montr=E9al_meeting?=
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 are now taking agenda slot requests for the MMUSIC meeting at IETF  
66.  Please send requests for slots to the chairs, indicating the  
name of the draft you wish to discuss and the amount of time required.

Colin



On 16 Jun 2006, at 12:24, Colin Perkins wrote:
> Folks,
>
> The MMUSIC session at IETF 66 is currently scheduled for 09:00 -  
> 11:30 on Wednesday 12th July. This date is provisional, and may  
> still change.
>
> The cut-off date for initial (-00) draft submissions is 09:00 EDT  
> (13:00 GMT) on Monday 19th June. The cut-off date for all other  
> draft submissions is 09:00 EDT (13:00 GMT) on Monday 26th June.  
> These are hard deadlines: no extensions will be given. You are  
> reminded that the secretariat will reject submissions that don't  
> match the I-D nits checklist, and are encouraged to use the  
> validation tool at http://tools.ietf.org/tools/idnits/ to check  
> your draft before submission.
>
> Colin
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic


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



From mmusic-bounces@ietf.org Mon Jun 19 10:39:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FsKu6-0005b7-In; Mon, 19 Jun 2006 10:39:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FsKu5-0005b2-Q7
	for mmusic@ietf.org; Mon, 19 Jun 2006 10:39:01 -0400
Received: from mx4-1.spamtrap.magma.ca ([209.217.78.176])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsKu4-0002w7-7G
	for mmusic@ietf.org; Mon, 19 Jun 2006 10:39:01 -0400
Received: from mail2.magma.ca (mail2.internal.magma.ca [10.0.10.12])
	by mx4-1.spamtrap.magma.ca (8.13.1/8.13.1) with ESMTP id k5JEcwLd022880;
	Mon, 19 Jun 2006 10:38:58 -0400
Received: from [10.1.5.219] ([216.13.42.126]) (authenticated bits=0)
	by mail2.magma.ca (Magma's Mail Server) with ESMTP id k5JEcu8L029513
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
	Mon, 19 Jun 2006 10:38:58 -0400
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <BE6AE8BF-C945-4799-BA3F-704FD0000389@magma.ca>
Content-Transfer-Encoding: 7bit
From: Philip Matthews <philip_matthews@magma.ca>
Date: Mon, 19 Jun 2006 10:39:01 -0400
To: mmusic@ietf.org
X-Mailer: Apple Mail (2.746.2)
X-magma-MailScanner-Information: Magma Mailscanner Service
X-magma-MailScanner: Clean
X-Spam-Status: 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: 
Subject: [MMUSIC] I-D on proposed modification to ICE
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:

Eric Cooper and I have written an I-D on a proposed modification to  
ICE that eliminates what we think are some duplicate connectivity  
checks. In brief, our proposal is to eliminate connectivity checks  
sent from candidates such as server-reflexive candidates, because we  
believe these are duplicates of checks sent from the candidates from  
which the server-reflexive candidates were derived.

To quote from first section of the I-D:
      "Eliminating checks in this manner has two advantages:

        o  It reduces the number of messages that need to be exchanged
           between endpoints; and

        o  The remaining checks start earlier, because there are  
fewer 50msec
           delays between the start of successive checks. This  
results in
           faster identification of desirable paths.

      Compared with [ICE-08], the modification described here typically
      results in 25% - 50% fewer messages when multiple NATs are  
involved.
      Similarly, the highest-priority working candidate can be  
promoted to
      the m/c line 25% - 50% faster. Since the savings are a result of
      eliminating checks from server-reflexive candidates, the  
reductions
      are less significant when one of the endpoints has a public IP
      address."

The I-D is available at

     http://www.ietf.org/internet-drafts/draft-matthews-mmusic-ice- 
eliminating-duplicates-00.txt

- Philip


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



From mmusic-bounces@ietf.org Mon Jun 19 16:59:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FsQqL-000364-Mo; Mon, 19 Jun 2006 16:59:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FsQqK-00035I-E1
	for mmusic@ietf.org; Mon, 19 Jun 2006 16:59:32 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FsQqI-0007vF-Vs
	for mmusic@ietf.org; Mon, 19 Jun 2006 16:59:32 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-2.cisco.com with ESMTP; 19 Jun 2006 13:59:31 -0700
X-IronPort-AV: i="4.06,152,1149490800"; 
	d="scan'208"; a="325293296:sNHT31230688"
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 k5JKxUjm021105; 
	Mon, 19 Jun 2006 13:59:30 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k5JKxKkq027004;
	Mon, 19 Jun 2006 13:59:28 -0700 (PDT)
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.211);
	Mon, 19 Jun 2006 16:59:25 -0400
Received: from [161.44.34.189] ([161.44.34.189]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 19 Jun 2006 16:59:24 -0400
Message-ID: <4497102B.4030606@cisco.com>
Date: Mon, 19 Jun 2006 16:59:23 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Guilherme Balena Versiani <guibv@comunip.com.br>
Subject: Re: [MMUSIC] ICE - Sending of a Subsequent Offer
References: <446B2FD5.4020107@comunip.com.br>
In-Reply-To: <446B2FD5.4020107@comunip.com.br>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Jun 2006 20:59:24.0471 (UTC)
	FILETIME=[3EA83C70:01C693E3]
DKIM-Signature: a=rsa-sha1; q=dns; l=1587; t=1150750770; x=1151614770;
	c=relaxed/simple; s=sjdkim1001; h=From:Subject;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:Re=3A=20[MMUSIC]=20ICE=20-=20Sending=20of=20a=20Subsequent=20Offer;
	X=v=3Dcisco.com=3B=20h=3Dko2j0xHcDoKChZ22uXiGB1VSSQM=3D;
	b=cB0bWm9JNNCn5TiLU9lSOW2sRQi1FeCbnncLzAtlyyHPook1RuzpWs7/xvjBjfuPff5QL365
	UgUFz8lQIANXc7sOfaL5Wz+MamFh3unjenc55amqtnjBSfLbm9iZDEUi;
Authentication-Results: sj-dkim-1.cisco.com; header.From=jdrosen@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
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

sorry for the REALLY delayed response... answers inline.

Guilherme Balena Versiani wrote:

> Hello,
> 
> When sending a subsequent offer, the draft-ietf-mmusic-ice-08.txt has 
> rules to retain/remove each of the current native candidates in the new 
> offer. But if the a=remote-candidate attribute is present in the offer, 
> what is the disposition of candidate pairs whose remote candidate was 
> not indicated in a=remote-candidate attribute?

This is a great question. According to the current text, the 
a=remote-candidate is used *only* to impact selection of a candidate in 
the m/c-line. However, as you point out, if things are running normally 
(meaning, this is not an attack), it will cause the answer to include 
candidates in the answer that need to be checked, when we know its just 
a matter of time for connectivity checks to finally verify the candidate 
that was placed in the m/c-line. It would require *another* offer in the 
reverse direction to clear those out, which is wasteful.

Consequently, I'll fix this in -09 so that a=remote-candidate causes a 
candidate to be considered valid NOT just for placement into m/c-line, 
but also for decisions about what other candidates to include.


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 Tue Jun 20 12:09:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fsimt-0006u2-Gc; Tue, 20 Jun 2006 12:09:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fsimr-0006tV-TQ
	for mmusic@ietf.org; Tue, 20 Jun 2006 12:09:09 -0400
Received: from co300216-ier2.net.avaya.com ([198.152.13.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsiYJ-0000Ec-9F
	for mmusic@ietf.org; Tue, 20 Jun 2006 11:54:08 -0400
Received: from ON0010AVEXU1.global.avaya.com (h135-20-128-12.avaya.com
	[135.20.128.12])
	by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP
	id k5KFpFdE005635
	for <mmusic@ietf.org>; Tue, 20 Jun 2006 11:51:15 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 20 Jun 2006 11:54:06 -0400
Message-ID: <5626D959080BBA49BBCA847DAE110FA4421498@ON0010AVEXU1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Minor comments on ICE-08
Thread-Index: AcaUgbpkx7FSg2AdRkqq5jV9Dg3PjQ==
From: "Cooper, Eric \(Eric\)" <ecooper@avaya.com>
To: <mmusic@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: 
Subject: [MMUSIC] Minor comments on ICE-08
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="===============0273396609=="
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0273396609==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C69481.C2B913FE"

This is a multi-part message in MIME format.

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

Here are some small things that I noticed when reviewing the examples in
ICE-08:

1) The binding requests for the examples in section 11 probably start
from R, rather than L.

2) The 'basic' example in section 11 is incomplete, in the sense that it
does not show the binding request transmissions for the candidate pair
(L-PRIV-1, R-PUB-1).

3) The offer for the basic example in section 11 (message 5) has a cut &
paste error:  The m & c lines indicate a STUN-PUB-1 address.  I believe
this should be NAT-PUB-1.

Best Regards,

Eric.


------_=_NextPart_001_01C69481.C2B913FE
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.0.6617.47">
<TITLE>Minor comments on ICE-08</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Courier New">Here are some small things that I =
noticed when reviewing the examples in ICE-08:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">1) The binding requests for the =
examples in section 11 probably start from R, rather than L.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">2) The 'basic' example in section =
11 is incomplete, in the sense that it does not show the binding request =
transmissions for the candidate pair (L-PRIV-1, R-PUB-1).</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">3) The offer for the basic =
example in section 11 (message 5) has a cut &amp; paste error:&nbsp; The =
m &amp; c lines indicate a STUN-PUB-1 address.&nbsp; I believe this =
should be NAT-PUB-1.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Best Regards,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Eric.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C69481.C2B913FE--


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

--===============0273396609==--




From mmusic-bounces@ietf.org Tue Jun 20 15:32:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fslxy-000065-MF; Tue, 20 Jun 2006 15:32:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fslxx-00005Y-L2
	for mmusic@ietf.org; Tue, 20 Jun 2006 15:32:49 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fslxv-0000rM-Jt
	for mmusic@ietf.org; Tue, 20 Jun 2006 15:32:49 -0400
Received: from sj-dkim-8.cisco.com ([171.68.10.93])
	by sj-iport-5.cisco.com with ESMTP; 20 Jun 2006 12:32:45 -0700
X-IronPort-AV: i="4.06,158,1149490800"; 
	d="scan'208"; a="297961012:sNHT1893125468"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-8.cisco.com (8.12.11/8.12.11) with ESMTP id k5KJWh1r007131
	for <mmusic@ietf.org>; Tue, 20 Jun 2006 12:32:43 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k5KJUxcx002295
	for <mmusic@ietf.org>; Tue, 20 Jun 2006 12:32:39 -0700 (PDT)
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.211);
	Tue, 20 Jun 2006 15:31:29 -0400
Received: from [192.168.1.101] ([10.86.243.91]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 20 Jun 2006 15:31:28 -0400
Message-ID: <44984D0F.5080808@cisco.com>
Date: Tue, 20 Jun 2006 15:31:27 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF MMUSIC WG <mmusic@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Jun 2006 19:31:28.0561 (UTC)
	FILETIME=[20620210:01C694A0]
DKIM-Signature: a=rsa-sha1; q=dns; l=25975; t=1150831963; x=1151695963;
	c=relaxed/simple; s=sjdkim8001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:much=20beefier=20tutorial=20in=20ICE=20-=20preview=20text;
	X=v=3Dcisco.com=3B=20h=3DDgNEYhaXUEX0VUVURSEU57cMP+o=3D;
	b=SCMTljaigcDp6dP2hHnLqB3UDj7uZziV4I40RSvHC6Vg7+f4MIquTE8XPNd68iqCc2vQ4G5N
	T4QxmP11q6hPBajJA48QD5KCdbaeYxAvHU/Ii4feDhQZBl9qRbu+BnZW;
Authentication-Results: sj-dkim-8.cisco.com; header.From=jdrosen@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 919970d5fe16e84197d564bf094e8b04
Subject: [MMUSIC] much beefier tutorial in ICE - preview text
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

So, its clear from the various comments on ICE-08 that ICE is still too 
hard to understand. One of the problems, it seems, is that it requires 
multiple passes to understand. One has to more or less get it in order 
to make any sense at all of the terminology section. The overview 
section is also really terse and doesn't explain enough of the core 
concepts.

So, I've taken a stab at substantially increasing the content in the 
overview section, which would then be moved prior to the terminology 
section as suggested. I'll be submitting ice-09 probably monday morning 
at 859am, so I figured I'd float the proposed text to get comments. I'm 
particularly looking for input on whether this tutorial is 
understandable starting only with a very high levle understanding of 
STUN and the problem to be solved (nat traversal for media).

Comments welcome:

<section title="Overview of ICE">

<t> A typical architecture for an ICE deployment is shown in <xref
target="fig:ice-ref-arch"/>. The figure shows two endpoints (known
as agents in RFC 3264 terminology) which we call L and R (for left and
right, which helps visualize call flows). Both L and R are behind a
NAT. The type of NAT and its properties are unknown. Indeed, it is not
known whether the agent is behind a NAT at all, or whether there are
multiple NATs between it and the network. Agents A and B
are capable of engaging in an offer/answer exchange <xref
target="RFC3264"/> by which they can exchange SDP messages, whose
purpose is to set up a media session between A and B. Of course, the
offer/answer exchange itself must be capable of traversing the
NAT. Such traversal is facilitated through signaling elements such as
SIP servers, and is outside the scope of this specification. Different
solutions are applied for traversal of the signaling that carries the
offer/answer exchange, and for the media set up by that offer/answer
exchange. This is because of the vastly different requirements on
latency, packet loss, and overall bandwidth between the signaling and
media. For example, usage of a signaling intermediary, such as a SIP
proxy, as a relay for all signaling at all times, is acceptable,
whereas usage of relays at all times for media is highly undesirable.
</t>

<t>
In addition to the agents, a SIP server and NATs, ICE is typically
used in concert with STUN servers in the network. Each agent can have
its own STUN server, or they can be the same.
</t>

<figure anchor="fig:ice-ref-arch"><artwork>
<![CDATA[

                            +-------+
                            | SIP   |
         +-------+          | Srvr  |          +-------+
         | STUN  |          |       |          | STUN  |
         | Srvr  |          +-------+          | Srvr  |
         |       |                             |       |
         +-------+                             +-------+







             +--------+                   +--------+
             |  NAT   |                   |  NAT   |
             +--------+                   +--------+



         +-------+                             +-------+
         | Agent |                             | Agent |
         |   L   |                             |   R   |
         |       |                             |       |
         +-------+                             +-------+
]]></artwork></figure>


<t>
Prior to initiating an offer, the offering agent (L in this example)
starts by performing a process known as address gathering. This
process allows the client to obtain one or more transport addresses,
one more of which might be viable addresses at which the agent can
receive incoming media packets from the other agent, which we call its
peer. A transport address is just the combination of an IP address and
port. With ICE, an agent will actually provide its peer with all of
its possible transport addresses, and ICE will figure out which one to
actually use.
</t>

<t>
Naturally, one viable transport address is one obtained directly from
a local interface the client has towards the network. Such a transport
address is called a local transport address. The local interface could
be one on a local layer 2 network technology, such as ethernet or
WiFi, or it could be one that is obtained through a tunnel mechanism,
such as a Virtual Private Network (VPN) or Mobile IP (MIP). In all
cases, these appear to the agent as a local interface from which ports
(and thus transport addresses) can be allocated.
</t>

<t> If an agent is multihomed, it can obtain a transport address from
each interface. Depending on the location of the peer on the IP
network, the agent may be reachable through one of those interfaces,
or through another. Consider, for example, an agent which has a local
interface to a private net 10 network, and also to the public
Internet. A transport address from the net10 interface will be
directly reachable when communicating with a peer on the same private
net 10 network, while a transport address from the public interface
will be directly reachable when communicating with a peer on the
public Internet. Rather than trying to guess which interface will work
prior to sending an offer, the offering agent includes both transport
addresses in its offer.
</t>

<t>
Indeed, when using a media technology like the Real Time Transport
Protocol (RTP), an agent needs two transport addresses on each
interface - one for the RTP, and one for the Real Time Control
Protocol (RTCP). Other media technologies may require a multiplicity
of transport addresses to be used and treated as a bundle. Each of
these transport addresses is called a component. There are two
components in an RTP stream - the RTP itself, and the RTCP. In ICE, the
set of transport addresses that represent an atomic grouping on which
communications is possible is called a candidate. In the example so
far, the agent would obtain two candidates - one from the net 10
interface, and one from the interface on the public Internet. Each
candidate would contain two transport addresses, corresponding to each
of the two components.
</t>

<t> Once the agent has obtained local transport addresses, it uses
STUN to obtain additional transport addresses. To do this, it would
send a STUN Binding Request, using the Binding Discovery Usage <xref
target="I-D.ietf-behave-rfc3489bis"/> or the Relay Usage <xref
target="I-D.ietf-behave-turn"/> from a local transport address, to its
STUN server. It is assumed that the address of the STUN server is
configured, or learned in some way. Indeed, an agent might even have
multiple STUN servers. As a consequence of communicating with the STUN
server, the agent can learn potentially two new types of transport
addresses - server reflexive transport addresses and relayed transport
addresses. The relationship of these addresses to the local transport
address is shown in <xref target="fig:address-types"/>.
</t>

<figure anchor="fig:address-types"><artwork>
<![CDATA[
               To Internet

                   |
                   |
                   |  /------------  Relayed
                   | /               Address
               +--------+
               |        |
               |  STUN  |
               | Server |
               |        |
               +--------+
                   |
                   |
                   | /------------  Server
                   |/               Reflexive
             +------------+         Address
             |    NAT     |
             +------------+
                   |
                   | /------------  Local
                   |/               Address
               +--------+
               |        |
               | Agent  |
               |        |
               +--------+
]]></artwork></figure>

<t>
The local transport address is resident on the agent itself. Through
either the Binding Discovery Usage or the Relay Usage, the agent can
discover its server reflexive transport address. This is the address on the
public side of the NAT, facing the STUN server. It is the transport
address allocated to the agent on the public side of the NAT as a
consequence of the transmission of the STUN request through the NAT,
to the STUN server. The NAT will allocate a binding, mapping this
server reflexive transport address to the local transport address. Packets
received at the NAT, targeted towards the server reflexive transport 
address,
will have their destination address rewritten to the local transport
address by the NAT, and then be forwarded to the agent. When there are
multiple NATs between the agent and the STUN server, the STUN request
will create a binding on each NAT, but only the outermost server reflexive
transport address will be discovered by the agent.
</t>

<t>
In addition, through the Relay Usage, the agent can request that the
STUN server itself allocate a transport address from one of its local
interfaces, and establish a binding that maps that transport address
(called a relayed transport address, naturally) towards the source
transport address of the STUN request, which will actually be equal to the
server reflexive transport address allocated by the outermost
NAT. Consequently, packets sent to the relayed transport address will
be routed by the IP network towards the STUN server. The STUN server
will receive them, rewrite the destination address to be equal to the
server reflexive transport address, and forward them. They will then arrive
at the NAT, where the destination address is rewritten once again, and
the packet forward finally to the agent at its local address.
</t>

<t>
Since the server reflexive transport addresses and relayed transport
addresses and obtained from a local transport address, they are said
to be derived transport addresses, since they are derived from (and
ultimately map to) their associated local transport address. During
the process of address gathering, the agent will obtain as many
transport addresses of a given type as are needed for the media
session. For example, with RTP, two transport addresses are needed for
a candidate. The agent will obtain two server reflexive transport
addresses (each derived from a local transport address), and they
would be used to constitute a server reflexive candidate. The local
transport addresses make up a local candidate, and the relayed
transport addresses make up a relayed candidate.
</t>

<figure anchor="fig:cand-relations"><artwork>
<![CDATA[


            Server                         Server
           Reflexive                      Reflexive
           Candidate                      Candidate
         ..............                 ..............
         .            .                 .            .
         .  +-+  +-+  .                 .  +-+  +-+  .
         .  | |  | |  .                 .  | |  | |  .
         .  +-+  +-+  .                 .  +-+  +-+  .
         .   ^    ^   .                 .   ^    ^   .
         ....|....|....                 ....|....|....
             |    |                         |    |
             |    |                         |    |
         ....|....|....                 ....|....|....
         .   |    |   .                 .   |    |   .
         .  +-+  +-+  .   Local         .  +-+  +-+  .   Local
         .  | |  | |  . Candidate       .  | |  | |  . Candidate
         .  +-+  +-+  .                 .  +-+  +-+  .
         .   |    |   .                 .   |    |   .
         ....|....|....                 ....|....|....
             |    |                         |    |
             |    |                         |    |
         ....|....|....                 ....|....|....
         .   V    V   .                 .   V    V   .
         .  +-+  +-+  .                 .  +-+  +-+  .
         .  | |  | |  .                 .  | |  | |  .
         .  +-+  +-+  .                 .  +-+  +-+  .
         .            .                 .            .
         ..............                 ..............
            Relayed                        Relayed
           Candidate                      Candidate


                                Legend
                                ------

                         +-+
                         | | Transport Address
                         +-+

                        ---> Derived From

                         ...
                         . . Candidate
                         ...

]]></artwork></figure>


<t>
The relationship between these various transport addresses and
candidates is shown pictorially in <xref
target="fig:cand-relations"/>. The figure shows our example agent with
two local interfaces, each of which provides two transport address
pairs to make up two candidates. From those two local candidates, a
server reflexive and relayed candidate are derived.
</t>

<t>
Once the agent has completed gathering its candidates, it assigns each
a candidate identifier, called the candidate ID. The candidate ID is a
random number used to uniquely identify each candidate, and is used in
the connectivity checks discussed below. The components of each
candidate are ordered numerically, starting at one, such that each
transport address has a component ID. For example, in an RTP candidate
there are two components, component ID 1 and component ID 2. Each
transport address pair is therefore uniquely identified by a
combination of its candidate ID and its component ID. The combination
of the two is called, unsurprisingly, a transport address ID, or tid
for short.
</t>

<t>
The agent will place all of its candidates in an offer, using a new
SDP attribute called the candidate attribute. This attribute contains
the actual transport address, the candidate ID and component ID, and a
q-value. The q-value is used for the agent to prioritize its
candidates. An agent will typically prefer to receive media at
particular candidates over other candidates, based on local
policy. For example, an agent would normally prefer to receive
interactive voice RTP packets at its local candidate as opposed to its
relayed candidate, due to the extra latency incurred by traveling
through the relay.
</t>

<t>
Finally, the agent chooses one of its candidates for inclusion in the
m and c lines (called the m/c-line collectively). Assuming that
candidate is verified as functional by the ICE connectivity checks
described below, this is the actual IP address and port to which media
will be sent. The candidate selected for inclusion in the m/c-line of
an offer (or an answer) is called the active candidate, since it is
the one that is the active destination for receipt of media traffic.
</t>

<t>
Once the active candidate is chosen, the agent sends the
offer. Through the wonders or SIP or other signaling protocols, this
offer is delivered to the peer, which must now select its answer. To
create the answer, the agent starts by gathering addresses, in exactly
the same way the offered did. It includes those as candidates in its
answer, and selects one as the active candidate, just like the offered
did. It then sends the answer.
</t>

<t>
Each agent then pairs up each of its candidates with the candidates of
its peer. From the perspective of the offerer, the set of candidates
it sent in its offer are called its native candidates, and the ones
received in the answer are the remote candidates. Similarly, from the
perspective of the answerer, the set of candidates it sent in its
answer are the native candidates, and the ones received in the offer
are the remote candidates. Both agents pair up each of their native
candidates with each of the remote candidates, producing a set of
candidate pairs. If there were N native candidates and M remote
candidates, there will be N*M candidate pairs. Within each candidate
pair, the transport addresses themselves are paired up one for one,
resulting in transport address pairs as well. The transport addresses
are paired up such that they have identical component IDs. Each
transport address pair has an ID, called the transport address pair
ID, formed by concatenating the tids of its two transport addresses.
</t>

<t>
Once the pairing is done, the transport address pairs are ordered in
such a way that both the offerer and answerer will end up with the
same order. This ordering is done by using the q-values each side
provided, along with the candidate IDs to help break ties. Then, each
side begins a process known as connectivity checks. Connectivity
checks are STUN transactions, using the connectivity check usage of
STUN, sent from the native transport address to the remote
transport address of a particular transport address pair. If an agent
sends a STUN request and gets a successful response, the transport
address pair is said to be Receive Valid, or Recv Valid for short,
since the agent knows that its peer was able to receive a packet. If
an agent receives a request and sends a response, the transport
address pair is said to be Send Valid, since the agent knows that its
peer was able to send it a packet. When transactions in both
directions complete, the transport address pair is said to be
Valid. The idea behind ICE is that if a transport address pair is
valid, it means that agents were able to succesfully exchange IP
packets in both directions. Consequently, any media packets, which are
sent to and from exactly the same IP addresses and ports, should also
work, since they don't differ in their IP addresses or ports.
</t>

<t>
Since there can be quite a few transport address pairs to check,
performing all of the connectivity checks in parallel can cause
substantial load on the network. Instead, each agent will start at the
top of the ordered list they each created, and every 50ms, begin a new
connectivity check.
</t>

<t>
In order to succesfully process a STUN connectivity check, an agent
must be able to correlate the STUN request or response with the
transport address pair whose connectivity the STUN message is meant to
validate. To perform this correlation, the STUN connectivity checks
contain a USERNAME attribute formed in a special way. In particular,
the USERNAME contains the actual transport address pair ID, which, as
described above, is formed by concatenating the tids of each of the
candidates. The USERNAME is used in conjunction with an authentication
and message integrity operation on the STUN message that requires a
password. This
password is conveyed in the offer/answer exchange, and is a random
number valid only for the duration of the media session. This ensures
that, if the signaling channel carrying the offer/answer
exchange is secure, the agent can be certain that its STUN
connectivity checks are taking place with the agent which responded to
the signaling.
</t>

<t>
Because each agent is receiving STUN requests on the same IP address
and port that media will later be sent to, each agent is effectively
acting as its own mini STUN server, implementing the connectivity
check usage described in <xref
target="I-D.ietf-behave-rfc3489bis"/>. Like all STUN servers, when the
agent sends a STUN response to a request, the response includes the
MAPPED-ADDRESS attribute that contains the source IP address and port
that the request came from. In certain deployment scenarios, and in
particular where one of the agents is behind a NAT whose address and
port mapping properties are address and port dependent, this source IP
address and port may differ from the server reflexive ones allocated
by the peer during the address gathering phase. This source IP address
and port, conveyed in the MAPPED-ADDRESS attribute of the STUN
response, therefore constitutes a new transport address, called a peer
reflexive transport address, which can be used for communications.
</t>

<figure anchor="fig:peer-example"><artwork>
<![CDATA[
                                    +-------+
                                    | STUN  |
                                    | Srvr  |
                                    |       |
                                    +-------+
                                         ^
                                         |
                                         |
                                         |
                                         |
           +--------------------------+  |
           |                     NAT-2|  |NAT-1
           |                      +-----------+
           |                      |  APD NAT  |
           |                      +-----------+
           |                          |  |
           |                           \ |
           VL1                          \|R1
       +-------+                    +-------+
       | Agent |                    | Agent |
       |   L   |                    |   R   |
       |       |                    |       |
       +-------+                    +-------+
]]></artwork></figure>

<t>
Consider the example of <xref target="fig:peer-example"/>. The agent
on the left, agent L, has a single interface and is not behind a
NAT. Consequently, it ends up with a single candidate with a single
transport address (normally two for RTP, but we'll consider just one
for ease of explanation), transport address L1. It sends an offer to
agent R, which is behind one of these Address and Port Dependent (APD)
mapping NATs. Agent R has a local transport address R1, and obtains a
server reflexive transport address from its STUN server, transport
address NAT-1. Now, when agent R sends a connectivity check from its
local transport address (R1) to L's local transport address (L1), this
check will traverse the NAT. The connectivity check itself will create
a new mapping in the NAT and be allocated a new binding on the NAT -
NAT-2. This STUN request arrives at L, which generates a STUN response
containing transport address NAT-2. Agent R, noticing that this is not
the same as its other two transport addresses, treats this as a new
peer reflexive transport address.
</t>

<t>
This new peer reflexive transport address is paired up with the remote
transport address containing the STUN server from which that transport
address was learned (transport address L1 in the example above). This
becomes a new transport address pair, and connectivity checks are run
on it as well.
</t>

<t>
Once all of the transport address pairs in a candidate pair have been
validated, that candidate pair is ready to be used. Media starts being
sent on it immediately, and the offerer will send an updated offer,
now containing the agents half of the validated candidate pair in the
m/c-line. This is called "promoting a candidate to active". The
updated offer only contains a single candidate attribute - the one for
the active candidate. It also contains an attribute, called the
remote-candidate attribute, which tells the answerer the remote
candidate in the
validated candidate pair. The answerer uses this attribute, along with
its own view on the states of the candidate pairs, to place a
candidate in the m/c-line and populate the candidate attributes in its
answer.
</t>

<t> It is important to understand that, when ICE is in use, media is
not sent to a candidate without validation, even if that candidate
appears in the m/c-line. This is in order to avoid denial-of-service
attacks. In particular, without ICE, an offerer can send an offer to
another agent, and list the IP address and port of a target in the
offer. If the agent is an automata that answers a call automatically,
it will do so and then proceed to send media to the target. This
provides substantial packet amplifications. ICE fixes this by
requiring that an agent never send media packets unless it has sent a
STUN message towards the target of the RTP packets, and received a
reply from that target <xref target="sec:send-media"/>. </t>


<t>
A summary of this overall behavior is shown in the basic call flow in
<xref target="fig:ice-model"/>.
</t>


<figure anchor="fig:ice-model"><artwork>
<![CDATA[
        Agent A              STUN Servers          Agent B
           |(1) Gather Addresses |                     |
           |-------------------->|                     |
           |(2) Offer            |                     |
           |------------------------------------------>|
           |                     |(3) Gather Addresses |
           |                     |<--------------------|
           |(4) Answer           |                     |
           |<------------------------------------------|
           |(5) STUN Check       |                     |
           |<------------------------------------------|
           |(6) STUN Check       |                     |
           |------------------------------------------>|
           |(7) Media            |                     |
           |<------------------------------------------|
           |(8) Media            |                     |
           |------------------------------------------>|
           |(9) Offer            |                     |
           |------------------------------------------>|
           |(10) Answer          |                     |
           |<------------------------------------------|

]]></artwork></figure>


</section>

-- 
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 Jun 20 15:58:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FsmMb-0004BL-3m; Tue, 20 Jun 2006 15:58:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FsmEh-0001U2-6r
	for mmusic@ietf.org; Tue, 20 Jun 2006 15:50:07 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsmEf-0003Ul-M0
	for mmusic@ietf.org; Tue, 20 Jun 2006 15:50:07 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12])
	by rtp-iport-1.cisco.com with ESMTP; 20 Jun 2006 12:50:05 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.06,158,1149490800"; 
	d="scan'208"; a="30069521:sNHT25641924"
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 k5KJo4YL012918; 
	Tue, 20 Jun 2006 15:50:04 -0400 (EDT)
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.211);
	Tue, 20 Jun 2006 15:50:04 -0400
Received: from [192.168.1.101] ([10.86.243.91]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 20 Jun 2006 15:50:04 -0400
Message-ID: <4498516B.8070401@cisco.com>
Date: Tue, 20 Jun 2006 15:50:03 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <44711429-AACA-40EF-86CE-507552900D39@magma.ca>
In-Reply-To: <44711429-AACA-40EF-86CE-507552900D39@magma.ca>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Jun 2006 19:50:04.0124 (UTC)
	FILETIME=[B94F69C0:01C694A2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a4a24b484706be629f915bfb1a3e4771
Cc: mmusic@ietf.org
Subject: [MMUSIC] Re: Some comments on draft-ietf-mmusic-ice-08
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

Thanks for the comments. Responses inline.

Philip Matthews wrote:

> Jonathan:
> 
> Here are some comments. They are mostly pretty minor.
> I am still re-reading the draft to more fully understand it,
> so more may follow.
> 
> General comments:
> - The grammar given in section 12 specifies that a colon (":") is to  
> immediately follow the word "candidate"
> in the "a=candidate" line. This is consistent with the SDP syntax for  
> an attribute with a value as specified in
> draft-ietf-mmusic-sdp-new-26.
> However, none of the examples given elsewhere in the document use a  colon.

Good catch. Fixed.

> 
> Section 1:
> - (First PP) Misspelling - "Descrption" should be "Description".

fixed.

> 
> Section 2:
> - I found it difficult to understand much of the terminology on my  
> first pass through
>   the document, even though I had a basic understanding of how ICE  
> works. In the end,
>   I just skipped over it and then came back later.
>   Perhaps consider placing the introductory sections before the  
> terminology section,
>   perhaps by making sections 3 - 6 subsections of section 1.  If you  
> did this,
>   then the terminology section would clearly divide the Informative  
> text from the Normative text.

I like the idea of moving the introduction before terminology, that is 
fine. Not so sure about the rest. I'm still noodling your proposed 
reorganization and Rohans, and will do the reorg last as I edit -09.

> - It would be nice if the definitions of Reflexive Transport Address  
> and Relayed Transport Address
>   could make it clearer that these are subclasses of Derived  Transport 
> Addresses
>   (for example, the definition text could start "A type of Derived  
> Transport Address where ...").

Done. Note that the definition of reflexive transport address did 
mention that it was derived; its just that the statement was at the end 
of the definition. I moved it to the beginning.

> - I found the definitions of the various Transport Address forms  
> difficult to understand
>   (I was familiar with the concepts, but hadn't see the terms  before, 
> and was uncertain for a while
>   which term matched which concept).
>   I might be useful to add a diagram (perhaps somewhere in sections  
> 3-6) that illustrates the
>   various forms  (Derived, Reflexive, etc...)

I think its clear that the terminology itself needs to really be 
introduced first in the introduction section, and the terminonology 
section more of a reference after that. As for a picture, I'll add this 
into the introduction:

  Please view in a fixed-width font such as
                   Courier.






               To Internet

                   |
                   |
                   |  /------------  Relayed
                   | /               Address
               +--------+
               |        |
               |  STUN  |
               | Server |
               |        |
               +--------+
                   |
                   |
                   | /------------  Reflexive
                   |/               Address
             +------------+
             |    NAT     |
             +------------+
                   |
                   | /------------  Local
                   |/               Address
               +--------+
               |        |
               | Agent  |
               |        |
               +--------+


> 
> Section 3:
> - "in addition to private networks connected to the public Internet  
> through NAT".
>   The wording here suggests  that the combination of the Internet  plus 
> various private networks
>   connected to it via NAT boxes is one realm.

I've revised the intro (see separate note) and removed these two 
paragraphs on realm, which don't lend any clarity at all I think.

> - (top of page 10) "reply from that target Section 7.13".
>   There is some sort of grammatical error here.

fixed.

> 
> Section 7.1:
> - In the case of a candidate whose components are all server- reflexive 
> or relayed, must the component
>   transport addresses all be derived from the same local address?
>   I suspect so, but you don't say this.

They are from the same candidate, matched component to component. There 
is a picture now in the overview which says this. I also added words to 
this extent at the top of 7.1, which say:

For server reflexive and
relayed candidates, each component MUST be derived from a component with the
same component ID, all of which come from a single local candidate.


> - (page 13)
>       "Local candidates are obtained by binding to ephemeral ports  on 
> an interface ..."
>    AND
>      "... obtain a set of candidates (one for each interface) by  
> binding to N ephemeral UDP ports ..."
>   This text seems to imply that the UDP ports must be ephemeral.  This 
> seems overly restrictive.
>   I believe that the specification will work fine if a well-known  port 
> is used instead.
>   I suggest replacing these with the following:
>       "Local candidates are obtained by binding to ports (typically  
> ephemeral ports) on an interface ..."
>   AND
>      "... obtain a set of candidates (one for each interface) by  
> binding to N UDP ports ..."

changed.

> - (page 14, indented paragraph)
>   "The ability to process STUN connectivity checks allows for  clients 
> to obtain peer reflexive transport
>    addresses that can be used by the network server to reach them  
> without a relay, even through NATs
>    with restrictive mapping and filtering policies."
>   I don't understand this sentence.
>   In general, I found the wording in this indented paragraph to be  much 
> below the very high standard
>   set by the rest of the document. Perhaps you might rewrite this  
> entire paragraph.

Rewritten to:

<list style="indent"> <t>Why would these types of endpoints even
bother to implement ICE?  The answer is that such an implementation
greatly facilitates NAT traversal for clients that connect to
it. Consider a PC softphone behind a NAT whose mapping policy is
address and port dependent. The softphone initiates a call through a
gateway that implements ICE. The gateway doesn't obtain any server
reflexive or relayed transport addresses, but it implements ICE, and
consequently, is prepared to receive STUN connectivity checks on its
local transport addresses. The softphone will send a STUN connectivity
to check to that local transport address, causing the NAT to allocate
a new binding for the softphone. The connectivity check will inform
the softphone of this address, allowing it to be used by the gateway
as a peer reflexive remote candidate. This allows direct media
transmission between the gateway and softphone, without the need for
relays. Furthermore, implementation of the STUN connectivity checks
allows for NAT bindings along the way to be kept open. ICE also
provides numerous security properties that are independent of NAT
traversal, and would benefit any multimedia endpoint. See <xref
target="sec:security"/> for a discussion on these benefits.
</t></list>


> - (page 15)
>    "... where there are multiple layers of NAT,  and that layering  is 
> known to the provider of the client."
>   Suggest adding an extra "where", so it reads
>    "... where there are multiple layers of NAT,  and where that  
> layering is known to the provider of the client."

added.

> 
> Section 7.8:
> -  "symmetric NAT". Replace with BEHAVE terminology?

fixed.

> 
> Section 12:
> - In addition to all the SDP examples in section 11, it would be nice  
> to see one or two examples of SDP
>   that do NOT use $L1, $L-PRIV-1.IP, $STUN-PUB-2.PORT, etc.
>   This would help the reader understand the grammar rules.

You mean with actual values? Sigh...

-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 Tue Jun 20 17:47:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fso3u-0004CT-4E; Tue, 20 Jun 2006 17:47:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fso3s-00047T-7y
	for mmusic@ietf.org; Tue, 20 Jun 2006 17:47:04 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsniA-0001yi-K6
	for mmusic@ietf.org; Tue, 20 Jun 2006 17:24:38 -0400
Received: from zcars04e.nortel.com ([47.129.242.56])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FsnVz-0008Cp-8V
	for mmusic@ietf.org; Tue, 20 Jun 2006 17:12:06 -0400
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	k5KL6Z403321; Tue, 20 Jun 2006 17:06:35 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] much beefier tutorial in ICE - preview text
Date: Tue, 20 Jun 2006 16:11:54 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF0ABDC967@zrc2hxm0.corp.nortel.com>
In-Reply-To: <44984D0F.5080808@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] much beefier tutorial in ICE - preview text
Thread-Index: AcaUoPzktiHc6vjSRiytV5h4zwHgcgACzcig
From: "Francois Audet" <audet@nortel.com>
To: "Jonathan Rosenberg" <jdrosen@cisco.com>,
	"IETF MMUSIC WG" <mmusic@ietf.org>
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 0aa23132abbc731e36938583486affe0
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 believe this text does help. Thanks for doing this.

Minor comments:
---------------

Your reference [37] should be draft-ietf-behave-nat-udp-07
instead of draft-ietf-behave-nat-udp-00.... (But really, it
is in final stages of being RFC so it should be updated
before publication). Might be worthwile to go through all the
refernces.

I find the use of "variable" for IP addresses and domain names
and others in SDP quite difficult to read. Also, I'm just having
visions of implementations in the wild putting $L1, $STUN-PUB-1.IP
and so forth in SDP... I'd much rather have examples with actual=20
IP addresses and real domain names.



> -----Original Message-----
> From: Jonathan Rosenberg [mailto:jdrosen@cisco.com]=20
> Sent: Tuesday, June 20, 2006 12:31
> To: IETF MMUSIC WG
> Subject: [MMUSIC] much beefier tutorial in ICE - preview text
>=20
>=20
> So, its clear from the various comments on ICE-08 that ICE is=20
> still too=20
> hard to understand. One of the problems, it seems, is that it=20
> requires=20
> multiple passes to understand. One has to more or less get it=20
> in order=20
> to make any sense at all of the terminology section. The overview=20
> section is also really terse and doesn't explain enough of the core=20
> concepts.
>=20
> So, I've taken a stab at substantially increasing the content in the=20
> overview section, which would then be moved prior to the terminology=20
> section as suggested. I'll be submitting ice-09 probably=20
> monday morning=20
> at 859am, so I figured I'd float the proposed text to get=20
> comments. I'm=20
> particularly looking for input on whether this tutorial is=20
> understandable starting only with a very high levle understanding of=20
> STUN and the problem to be solved (nat traversal for media).
>=20
> Comments welcome:
>=20
> <section title=3D"Overview of ICE">
>=20
> <t> A typical architecture for an ICE deployment is shown in=20
> <xref target=3D"fig:ice-ref-arch"/>. The figure shows two=20
> endpoints (known as agents in RFC 3264 terminology) which we=20
> call L and R (for left and right, which helps visualize call=20
> flows). Both L and R are behind a NAT. The type of NAT and=20
> its properties are unknown. Indeed, it is not known whether=20
> the agent is behind a NAT at all, or whether there are=20
> multiple NATs between it and the network. Agents A and B are=20
> capable of engaging in an offer/answer exchange <xref=20
> target=3D"RFC3264"/> by which they can exchange SDP messages,=20
> whose purpose is to set up a media session between A and B.=20
> Of course, the offer/answer exchange itself must be capable=20
> of traversing the NAT. Such traversal is facilitated through=20
> signaling elements such as SIP servers, and is outside the=20
> scope of this specification. Different solutions are applied=20
> for traversal of the signaling that carries the offer/answer=20
> exchange, and for the media set up by that offer/answer=20
> exchange. This is because of the vastly different=20
> requirements on latency, packet loss, and overall bandwidth=20
> between the signaling and media. For example, usage of a=20
> signaling intermediary, such as a SIP proxy, as a relay for=20
> all signaling at all times, is acceptable, whereas usage of=20
> relays at all times for media is highly undesirable. </t>
>=20
> <t>
> In addition to the agents, a SIP server and NATs, ICE is=20
> typically used in concert with STUN servers in the network.=20
> Each agent can have its own STUN server, or they can be the same. </t>
>=20
> <figure anchor=3D"fig:ice-ref-arch"><artwork>
> <![CDATA[
>=20
>                             +-------+
>                             | SIP   |
>          +-------+          | Srvr  |          +-------+
>          | STUN  |          |       |          | STUN  |
>          | Srvr  |          +-------+          | Srvr  |
>          |       |                             |       |
>          +-------+                             +-------+
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>              +--------+                   +--------+
>              |  NAT   |                   |  NAT   |
>              +--------+                   +--------+
>=20
>=20
>=20
>          +-------+                             +-------+
>          | Agent |                             | Agent |
>          |   L   |                             |   R   |
>          |       |                             |       |
>          +-------+                             +-------+
> ]]></artwork></figure>
>=20
>=20
> <t>
> Prior to initiating an offer, the offering agent (L in this=20
> example) starts by performing a process known as address=20
> gathering. This process allows the client to obtain one or=20
> more transport addresses, one more of which might be viable=20
> addresses at which the agent can receive incoming media=20
> packets from the other agent, which we call its peer. A=20
> transport address is just the combination of an IP address=20
> and port. With ICE, an agent will actually provide its peer=20
> with all of its possible transport addresses, and ICE will=20
> figure out which one to actually use. </t>
>=20
> <t>
> Naturally, one viable transport address is one obtained=20
> directly from a local interface the client has towards the=20
> network. Such a transport address is called a local transport=20
> address. The local interface could be one on a local layer 2=20
> network technology, such as ethernet or WiFi, or it could be=20
> one that is obtained through a tunnel mechanism, such as a=20
> Virtual Private Network (VPN) or Mobile IP (MIP). In all=20
> cases, these appear to the agent as a local interface from=20
> which ports (and thus transport addresses) can be allocated. </t>
>=20
> <t> If an agent is multihomed, it can obtain a transport=20
> address from each interface. Depending on the location of the=20
> peer on the IP network, the agent may be reachable through=20
> one of those interfaces, or through another. Consider, for=20
> example, an agent which has a local interface to a private=20
> net 10 network, and also to the public Internet. A transport=20
> address from the net10 interface will be directly reachable=20
> when communicating with a peer on the same private net 10=20
> network, while a transport address from the public interface=20
> will be directly reachable when communicating with a peer on=20
> the public Internet. Rather than trying to guess which=20
> interface will work prior to sending an offer, the offering=20
> agent includes both transport addresses in its offer. </t>
>=20
> <t>
> Indeed, when using a media technology like the Real Time=20
> Transport Protocol (RTP), an agent needs two transport=20
> addresses on each interface - one for the RTP, and one for=20
> the Real Time Control Protocol (RTCP). Other media=20
> technologies may require a multiplicity of transport=20
> addresses to be used and treated as a bundle. Each of these=20
> transport addresses is called a component. There are two=20
> components in an RTP stream - the RTP itself, and the RTCP.=20
> In ICE, the set of transport addresses that represent an=20
> atomic grouping on which communications is possible is called=20
> a candidate. In the example so far, the agent would obtain=20
> two candidates - one from the net 10 interface, and one from=20
> the interface on the public Internet. Each candidate would=20
> contain two transport addresses, corresponding to each of the=20
> two components. </t>
>=20
> <t> Once the agent has obtained local transport addresses, it=20
> uses STUN to obtain additional transport addresses. To do=20
> this, it would send a STUN Binding Request, using the Binding=20
> Discovery Usage <xref target=3D"I-D.ietf-behave-rfc3489bis"/>=20
> or the Relay Usage <xref target=3D"I-D.ietf-behave-turn"/> from=20
> a local transport address, to its STUN server. It is assumed=20
> that the address of the STUN server is configured, or learned=20
> in some way. Indeed, an agent might even have multiple STUN=20
> servers. As a consequence of communicating with the STUN=20
> server, the agent can learn potentially two new types of=20
> transport addresses - server reflexive transport addresses=20
> and relayed transport addresses. The relationship of these=20
> addresses to the local transport address is shown in <xref=20
> target=3D"fig:address-types"/>. </t>
>=20
> <figure anchor=3D"fig:address-types"><artwork>
> <![CDATA[
>                To Internet
>=20
>                    |
>                    |
>                    |  /------------  Relayed
>                    | /               Address
>                +--------+
>                |        |
>                |  STUN  |
>                | Server |
>                |        |
>                +--------+
>                    |
>                    |
>                    | /------------  Server
>                    |/               Reflexive
>              +------------+         Address
>              |    NAT     |
>              +------------+
>                    |
>                    | /------------  Local
>                    |/               Address
>                +--------+
>                |        |
>                | Agent  |
>                |        |
>                +--------+
> ]]></artwork></figure>
>=20
> <t>
> The local transport address is resident on the agent itself.=20
> Through either the Binding Discovery Usage or the Relay=20
> Usage, the agent can discover its server reflexive transport=20
> address. This is the address on the public side of the NAT,=20
> facing the STUN server. It is the transport address allocated=20
> to the agent on the public side of the NAT as a consequence=20
> of the transmission of the STUN request through the NAT, to=20
> the STUN server. The NAT will allocate a binding, mapping=20
> this server reflexive transport address to the local=20
> transport address. Packets received at the NAT, targeted=20
> towards the server reflexive transport=20
> address,
> will have their destination address rewritten to the local=20
> transport address by the NAT, and then be forwarded to the=20
> agent. When there are multiple NATs between the agent and the=20
> STUN server, the STUN request will create a binding on each=20
> NAT, but only the outermost server reflexive transport=20
> address will be discovered by the agent. </t>
>=20
> <t>
> In addition, through the Relay Usage, the agent can request=20
> that the STUN server itself allocate a transport address from=20
> one of its local interfaces, and establish a binding that=20
> maps that transport address (called a relayed transport=20
> address, naturally) towards the source transport address of=20
> the STUN request, which will actually be equal to the server=20
> reflexive transport address allocated by the outermost NAT.=20
> Consequently, packets sent to the relayed transport address=20
> will be routed by the IP network towards the STUN server. The=20
> STUN server will receive them, rewrite the destination=20
> address to be equal to the server reflexive transport=20
> address, and forward them. They will then arrive at the NAT,=20
> where the destination address is rewritten once again, and=20
> the packet forward finally to the agent at its local address. </t>
>=20
> <t>
> Since the server reflexive transport addresses and relayed=20
> transport addresses and obtained from a local transport=20
> address, they are said to be derived transport addresses,=20
> since they are derived from (and ultimately map to) their=20
> associated local transport address. During the process of=20
> address gathering, the agent will obtain as many transport=20
> addresses of a given type as are needed for the media=20
> session. For example, with RTP, two transport addresses are=20
> needed for a candidate. The agent will obtain two server=20
> reflexive transport addresses (each derived from a local=20
> transport address), and they would be used to constitute a=20
> server reflexive candidate. The local transport addresses=20
> make up a local candidate, and the relayed transport=20
> addresses make up a relayed candidate. </t>
>=20
> <figure anchor=3D"fig:cand-relations"><artwork>
> <![CDATA[
>=20
>=20
>             Server                         Server
>            Reflexive                      Reflexive
>            Candidate                      Candidate
>          ..............                 ..............
>          .            .                 .            .
>          .  +-+  +-+  .                 .  +-+  +-+  .
>          .  | |  | |  .                 .  | |  | |  .
>          .  +-+  +-+  .                 .  +-+  +-+  .
>          .   ^    ^   .                 .   ^    ^   .
>          ....|....|....                 ....|....|....
>              |    |                         |    |
>              |    |                         |    |
>          ....|....|....                 ....|....|....
>          .   |    |   .                 .   |    |   .
>          .  +-+  +-+  .   Local         .  +-+  +-+  .   Local
>          .  | |  | |  . Candidate       .  | |  | |  . Candidate
>          .  +-+  +-+  .                 .  +-+  +-+  .
>          .   |    |   .                 .   |    |   .
>          ....|....|....                 ....|....|....
>              |    |                         |    |
>              |    |                         |    |
>          ....|....|....                 ....|....|....
>          .   V    V   .                 .   V    V   .
>          .  +-+  +-+  .                 .  +-+  +-+  .
>          .  | |  | |  .                 .  | |  | |  .
>          .  +-+  +-+  .                 .  +-+  +-+  .
>          .            .                 .            .
>          ..............                 ..............
>             Relayed                        Relayed
>            Candidate                      Candidate
>=20
>=20
>                                 Legend
>                                 ------
>=20
>                          +-+
>                          | | Transport Address
>                          +-+
>=20
>                         ---> Derived From
>=20
>                          ...
>                          . . Candidate
>                          ...
>=20
> ]]></artwork></figure>
>=20
>=20
> <t>
> The relationship between these various transport addresses=20
> and candidates is shown pictorially in <xref=20
> target=3D"fig:cand-relations"/>. The figure shows our example=20
> agent with two local interfaces, each of which provides two=20
> transport address pairs to make up two candidates. From those=20
> two local candidates, a server reflexive and relayed=20
> candidate are derived. </t>
>=20
> <t>
> Once the agent has completed gathering its candidates, it=20
> assigns each a candidate identifier, called the candidate ID.=20
> The candidate ID is a random number used to uniquely identify=20
> each candidate, and is used in the connectivity checks=20
> discussed below. The components of each candidate are ordered=20
> numerically, starting at one, such that each transport=20
> address has a component ID. For example, in an RTP candidate=20
> there are two components, component ID 1 and component ID 2.=20
> Each transport address pair is therefore uniquely identified=20
> by a combination of its candidate ID and its component ID.=20
> The combination of the two is called, unsurprisingly, a=20
> transport address ID, or tid for short. </t>
>=20
> <t>
> The agent will place all of its candidates in an offer, using=20
> a new SDP attribute called the candidate attribute. This=20
> attribute contains the actual transport address, the=20
> candidate ID and component ID, and a q-value. The q-value is=20
> used for the agent to prioritize its candidates. An agent=20
> will typically prefer to receive media at particular=20
> candidates over other candidates, based on local policy. For=20
> example, an agent would normally prefer to receive=20
> interactive voice RTP packets at its local candidate as=20
> opposed to its relayed candidate, due to the extra latency=20
> incurred by traveling through the relay. </t>
>=20
> <t>
> Finally, the agent chooses one of its candidates for=20
> inclusion in the m and c lines (called the m/c-line=20
> collectively). Assuming that candidate is verified as=20
> functional by the ICE connectivity checks described below,=20
> this is the actual IP address and port to which media will be=20
> sent. The candidate selected for inclusion in the m/c-line of=20
> an offer (or an answer) is called the active candidate, since=20
> it is the one that is the active destination for receipt of=20
> media traffic. </t>
>=20
> <t>
> Once the active candidate is chosen, the agent sends the
> offer. Through the wonders or SIP or other signaling=20
> protocols, this offer is delivered to the peer, which must=20
> now select its answer. To create the answer, the agent starts=20
> by gathering addresses, in exactly the same way the offered=20
> did. It includes those as candidates in its answer, and=20
> selects one as the active candidate, just like the offered=20
> did. It then sends the answer. </t>
>=20
> <t>
> Each agent then pairs up each of its candidates with the=20
> candidates of its peer. From the perspective of the offerer,=20
> the set of candidates it sent in its offer are called its=20
> native candidates, and the ones received in the answer are=20
> the remote candidates. Similarly, from the perspective of the=20
> answerer, the set of candidates it sent in its answer are the=20
> native candidates, and the ones received in the offer are the=20
> remote candidates. Both agents pair up each of their native=20
> candidates with each of the remote candidates, producing a=20
> set of candidate pairs. If there were N native candidates and=20
> M remote candidates, there will be N*M candidate pairs.=20
> Within each candidate pair, the transport addresses=20
> themselves are paired up one for one, resulting in transport=20
> address pairs as well. The transport addresses are paired up=20
> such that they have identical component IDs. Each transport=20
> address pair has an ID, called the transport address pair ID,=20
> formed by concatenating the tids of its two transport addresses. </t>
>=20
> <t>
> Once the pairing is done, the transport address pairs are=20
> ordered in such a way that both the offerer and answerer will=20
> end up with the same order. This ordering is done by using=20
> the q-values each side provided, along with the candidate IDs=20
> to help break ties. Then, each side begins a process known as=20
> connectivity checks. Connectivity checks are STUN=20
> transactions, using the connectivity check usage of STUN,=20
> sent from the native transport address to the remote=20
> transport address of a particular transport address pair. If=20
> an agent sends a STUN request and gets a successful response,=20
> the transport address pair is said to be Receive Valid, or=20
> Recv Valid for short, since the agent knows that its peer was=20
> able to receive a packet. If an agent receives a request and=20
> sends a response, the transport address pair is said to be=20
> Send Valid, since the agent knows that its peer was able to=20
> send it a packet. When transactions in both directions=20
> complete, the transport address pair is said to be Valid. The=20
> idea behind ICE is that if a transport address pair is valid,=20
> it means that agents were able to succesfully exchange IP=20
> packets in both directions. Consequently, any media packets,=20
> which are sent to and from exactly the same IP addresses and=20
> ports, should also work, since they don't differ in their IP=20
> addresses or ports. </t>
>=20
> <t>
> Since there can be quite a few transport address pairs to=20
> check, performing all of the connectivity checks in parallel=20
> can cause substantial load on the network. Instead, each=20
> agent will start at the top of the ordered list they each=20
> created, and every 50ms, begin a new connectivity check. </t>
>=20
> <t>
> In order to succesfully process a STUN connectivity check, an=20
> agent must be able to correlate the STUN request or response=20
> with the transport address pair whose connectivity the STUN=20
> message is meant to validate. To perform this correlation,=20
> the STUN connectivity checks contain a USERNAME attribute=20
> formed in a special way. In particular, the USERNAME contains=20
> the actual transport address pair ID, which, as described=20
> above, is formed by concatenating the tids of each of the=20
> candidates. The USERNAME is used in conjunction with an=20
> authentication and message integrity operation on the STUN=20
> message that requires a password. This password is conveyed=20
> in the offer/answer exchange, and is a random number valid=20
> only for the duration of the media session. This ensures=20
> that, if the signaling channel carrying the offer/answer=20
> exchange is secure, the agent can be certain that its STUN=20
> connectivity checks are taking place with the agent which=20
> responded to the signaling. </t>
>=20
> <t>
> Because each agent is receiving STUN requests on the same IP=20
> address and port that media will later be sent to, each agent=20
> is effectively acting as its own mini STUN server,=20
> implementing the connectivity check usage described in <xref=20
> target=3D"I-D.ietf-behave-rfc3489bis"/>. Like all STUN servers,=20
> when the agent sends a STUN response to a request, the=20
> response includes the MAPPED-ADDRESS attribute that contains=20
> the source IP address and port that the request came from. In=20
> certain deployment scenarios, and in particular where one of=20
> the agents is behind a NAT whose address and port mapping=20
> properties are address and port dependent, this source IP=20
> address and port may differ from the server reflexive ones=20
> allocated by the peer during the address gathering phase.=20
> This source IP address and port, conveyed in the=20
> MAPPED-ADDRESS attribute of the STUN response, therefore=20
> constitutes a new transport address, called a peer reflexive=20
> transport address, which can be used for communications. </t>
>=20
> <figure anchor=3D"fig:peer-example"><artwork>
> <![CDATA[
>                                     +-------+
>                                     | STUN  |
>                                     | Srvr  |
>                                     |       |
>                                     +-------+
>                                          ^
>                                          |
>                                          |
>                                          |
>                                          |
>            +--------------------------+  |
>            |                     NAT-2|  |NAT-1
>            |                      +-----------+
>            |                      |  APD NAT  |
>            |                      +-----------+
>            |                          |  |
>            |                           \ |
>            VL1                          \|R1
>        +-------+                    +-------+
>        | Agent |                    | Agent |
>        |   L   |                    |   R   |
>        |       |                    |       |
>        +-------+                    +-------+
> ]]></artwork></figure>
>=20
> <t>
> Consider the example of <xref target=3D"fig:peer-example"/>.=20
> The agent on the left, agent L, has a single interface and is=20
> not behind a NAT. Consequently, it ends up with a single=20
> candidate with a single transport address (normally two for=20
> RTP, but we'll consider just one for ease of explanation),=20
> transport address L1. It sends an offer to agent R, which is=20
> behind one of these Address and Port Dependent (APD) mapping=20
> NATs. Agent R has a local transport address R1, and obtains a=20
> server reflexive transport address from its STUN server,=20
> transport address NAT-1. Now, when agent R sends a=20
> connectivity check from its local transport address (R1) to=20
> L's local transport address (L1), this check will traverse=20
> the NAT. The connectivity check itself will create a new=20
> mapping in the NAT and be allocated a new binding on the NAT=20
> - NAT-2. This STUN request arrives at L, which generates a=20
> STUN response containing transport address NAT-2. Agent R,=20
> noticing that this is not the same as its other two transport=20
> addresses, treats this as a new peer reflexive transport address. </t>
>=20
> <t>
> This new peer reflexive transport address is paired up with=20
> the remote transport address containing the STUN server from=20
> which that transport address was learned (transport address=20
> L1 in the example above). This becomes a new transport=20
> address pair, and connectivity checks are run on it as well. </t>
>=20
> <t>
> Once all of the transport address pairs in a candidate pair=20
> have been validated, that candidate pair is ready to be used.=20
> Media starts being sent on it immediately, and the offerer=20
> will send an updated offer, now containing the agents half of=20
> the validated candidate pair in the m/c-line. This is called=20
> "promoting a candidate to active". The updated offer only=20
> contains a single candidate attribute - the one for the=20
> active candidate. It also contains an attribute, called the=20
> remote-candidate attribute, which tells the answerer the=20
> remote candidate in the validated candidate pair. The=20
> answerer uses this attribute, along with its own view on the=20
> states of the candidate pairs, to place a candidate in the=20
> m/c-line and populate the candidate attributes in its answer. </t>
>=20
> <t> It is important to understand that, when ICE is in use,=20
> media is not sent to a candidate without validation, even if=20
> that candidate appears in the m/c-line. This is in order to=20
> avoid denial-of-service attacks. In particular, without ICE,=20
> an offerer can send an offer to another agent, and list the=20
> IP address and port of a target in the offer. If the agent is=20
> an automata that answers a call automatically, it will do so=20
> and then proceed to send media to the target. This provides=20
> substantial packet amplifications. ICE fixes this by=20
> requiring that an agent never send media packets unless it=20
> has sent a STUN message towards the target of the RTP=20
> packets, and received a reply from that target <xref=20
> target=3D"sec:send-media"/>. </t>
>=20
>=20
> <t>
> A summary of this overall behavior is shown in the basic call=20
> flow in <xref target=3D"fig:ice-model"/>. </t>
>=20
>=20
> <figure anchor=3D"fig:ice-model"><artwork>
> <![CDATA[
>         Agent A              STUN Servers          Agent B
>            |(1) Gather Addresses |                     |
>            |-------------------->|                     |
>            |(2) Offer            |                     |
>            |------------------------------------------>|
>            |                     |(3) Gather Addresses |
>            |                     |<--------------------|
>            |(4) Answer           |                     |
>            |<------------------------------------------|
>            |(5) STUN Check       |                     |
>            |<------------------------------------------|
>            |(6) STUN Check       |                     |
>            |------------------------------------------>|
>            |(7) Media            |                     |
>            |<------------------------------------------|
>            |(8) Media            |                     |
>            |------------------------------------------>|
>            |(9) Offer            |                     |
>            |------------------------------------------>|
>            |(10) Answer          |                     |
>            |<------------------------------------------|
>=20
> ]]></artwork></figure>
>=20
>=20
> </section>
>=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
>=20

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



From mmusic-bounces@ietf.org Tue Jun 20 18:30:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FsojP-00017k-IQ; Tue, 20 Jun 2006 18:29:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FsojO-00017a-C0
	for mmusic@ietf.org; Tue, 20 Jun 2006 18:29:58 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsojL-0000hr-Bm
	for mmusic@ietf.org; Tue, 20 Jun 2006 18:29:58 -0400
Received: from csperkins-dsl1.demon.co.uk ([62.49.4.249]:62495
	helo=[192.168.0.3])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1FsojJ-0000Xi-6G; Tue, 20 Jun 2006 23:29:54 +0100
In-Reply-To: <GLEFKJBKNILEBOELNIBIGELADOAA.gunnar.hellstrom@omnitor.se>
References: <GLEFKJBKNILEBOELNIBIGELADOAA.gunnar.hellstrom@omnitor.se>
Mime-Version: 1.0 (Apple Message framework v750)
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed
Message-Id: <F1C53414-D195-43F4-B1BB-A6BDB831EFBC@csperkins.org>
Content-Transfer-Encoding: quoted-printable
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Re: ietf-mmusic-sdp-media-content-03
Date: Tue, 20 Jun 2006 23:29:50 +0100
To: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>
X-Mailer: Apple Mail (2.750)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4863a9796402a44fdb52482f353618fe
Cc: Cullen Jennings <fluffy@cisco.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	IETF MMUSIC WG <mmusic@ietf.org>, degodefroi@gmail.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

Hi,

Just following up on this... did we ever get agreement on the right =20
way to proceed? If an updated draft is needed, I'd like to get it in =20
before the deadline. Cullen? Jani?

Colin




On 18 May 2006, at 22:25, Gunnar Hellstrom wrote:
> Hi,
> I agree that the content parameters "txp" and "user-floor" indicate =20=

> similar functionality.
>
> But I see nothing wrong in having them both in the specification =20
> anyway.
>
> The txp parameter value may be used to invoke some automated =20
> mechanism in a text capable gateway to support conversion between =20
> full duplex simultaneous multimedia communication and half-duplex =20
> turn-taking, alternating text - voice communication in PSTN. But it =20=

> can also be used just as a warning to the IP user to be aware of =20
> possible limitations in simultanity and duplex use of media.
>
> We could go deeper in specifying exactly what limitations are valid =20=

> at each moment, but I doubt that any manufacturer want to refine =20
> their gateway designs to that degree.
> If we want to go deeper, we could use the following parameters:
>
> -    voice-text-alternating    ( in fact influencing two media )
>
> -    half-duplex                  ( when strictly only one =20
> direction at a time can be used )
>
> -    half-duplex-interruptable  ( when only one direction at a time =20=

> should be used for contents, but it is possible to send an =20
> indication that the other party want the turn. )
>
>
> I think that txp is enough.
>
> I just participate in a discussion where we have tried to meet =20
> requirements to keep gateway resources low by allowing it to set up =20=

> a real-time text connection between a PSTN gateway and an IP =20
> terminal only when there are indications that text will be used. It =20=

> is a compromise that may be needed in reality.
>
> In the draft document from that discussion, we use both the =20
> a=3Dcontent:txp parameter, and the following parmeters from RFC 3840 =20=

> and 3841.
>
> Contact: duplex=3D"half",
>
> Contact: <uri>;text
>
> Accept-Contact: *;text;require
>
> Accept-Contact: *;text
>
>
> I would appreciate very much to get comments on the parameter =20
> values and logic we have drafted.
>
> ----------------------Proposed alternative to ITU-T V.151 Annex D, =20
> using caller and callee capabilities and preferences and media-=20
> contents to control gateway - IP text capable terminal =20
> communication---------------------------------------------------------=20=

> ---------------
>
> Alternative proposal for V.151 Annex D.
> ANNEX D2
>
> Interworking IP Text Devices with V.151 Gateways.
> Connect text channel when usage of real-time text is likely.
>
>
>
> D.1 Introduction
> Some non-Gateway IP devices in the network not having a means of =20
> modulating or demodulating PSTN textphone signals, such as IVR =20
> systems, voicemail systems, IP phones, Multimedia telephones or =20
> other devices, may support the transmission of real-time text over =20
> IP networks and, ideally, interwork with V.151-compliant Gateways =20
> in order to provide a means through which users of PSTN textphone =20
> devices can communicate with those IP devices.  This class of =20
> devices is referred to herein as an "IP Text Device=94 (ITD).  This =20=

> Annex defines the procedures that may be used in order to allow for =20=

> such interworking between V.151 Gateways and ITDs. The main =20
> principle is to use RFC 4103 as the default text transport method =20
> between gateways and ITD:s, and open text channels only when it is =20
> likely that the text channel will be used.
>
> D.2 Exchanging capabilities and opening media streams
> When establishing a call, an ITD may advertise support for real-=20
> time text  in accordance with IETF RFC 4103.
>
> In general, ITDs also transmit text characters when communicating =20
> with other ITDs using RFC 4103, which specifies the establishment =20
> of a separate RTP stream specifically for transmitting text =20
> characters.  However, since V.151 PSTN gateway devices interleave =20
> audio and text data when used for Gateway - to - gateway operation, =20=

> V.151 gateways need to support both RFC 4103 to interwork with ITDs =20=

> and RFC 4351 for communicating with other PSTN gateways.
>
> As such, V.151 gateways are Recommended to indicate support for =20
> both transport methods initially when exchanging capability =20
> information. However, relatively few calls use real-time text in =20
> the PSTN, and therefore it may be desirable for the gateway to not =20
> open the text channel until either party in the call explicitly =20
> acts to use real-time text.
>
> According to normal procedures in IP multimedia systems, it is =20
> allowable to indicate capability for other transport protocols for =20
> real-time text as well as RFC 4103 and connect such alternatives.
>
> ----
>
> D.2.2    SDP based systems
> Similar logic follows for SDP-based systems.
>
> In SIP-based systems, the terminal and gateway shall announce =20
> support for text in the Contact field according to RFC 3840, and =20
> may indicate preference for text according to RFC 3841.
>
> Contact: <uri>;text
>
> A calling SIP terminal who does not put priority to text may =20
> indicate an interest to use text by:
>
> Accept-Contact: *;text
>
> A calling SIP terminal who want to put priority to establishing a =20
> text connection shall indicate that by:
>
> Accept-Contact: *;text;require
>
> Most commonly, PSTN text telephones support alternating text and =20
> audio during the call, but not simultaneous text and audio. If the =20
> gateway only supports alternating text and audio during the PSTN =20
> text session, it may be beneficial to make the ITD user aware of =20
> this limitation. It is proposed to use the Duplex parameter of RFC =20
> 3840 for this purpose.
>
> Contact: duplex=3D"half"
>
> There is a parameter also for use in the text media description:
>
> a=3Dcontent:txp
>
> It should be used to indicate to the ITD user that the text channel =20=

> is half duplex and turn-taking habits should be used.
>
>
>
> Note that while the use of RFC 2198 redundancy or other fault =20
> tolerance scheme is not shown in the abbreviated examples below, =20
> appropriate mechanisms should be employed to protect the =20
> transmission of the text stream in accordance with the text =20
> transport specifications.
>
>
>
> D.2.2.1 Call from PSTN
> Consider the following abbreviated example SDP that might be found =20
> in an offer sent by a V.151 Gateway not offering RFC 4103 support =20
> initially, but indicating text support and that the text support is =20=

> alternating with audio:
>
>       Contact: <uri>;text;duplex=3D"half"
>
>        m=3Daudio 7200 RTP/AVP 0 98
>
>        a=3Drtpmap:98 t140c/8000
>
>        a=3Dfmtp:98 cps=3D20
>
> If the gateway at that time already knows that text will be needed =20
> in the call, a requirement for text shall be included, and a media =20
> line for text. The decision to include text when offering the call =20
> may be because textphone tones have already been detected on the =20
> PSTN line, the gateway may be configured to be a dedicated text =20
> gateway, or it may be known by subscription or any other external =20
> means that either user has preference for text.
>
>       Accept-Contact: *;text;require
>
>       Contact: <uri>;text;duplex=3D"half"
>
>        m=3Daudio 7200 RTP/AVP 0 98
>
>        a=3Drtpmap:98 t140c/8000
>
>        a=3Dfmtp:98 cps=3D20
>
>        m=3Dtext 7202 RTP/AVP 99
>
>        a=3Drtpmap:99 t140/1000
>
>       a=3Dcontent:txp
>
>
>
> If the answering device is an ITD, with no specific indication that =20=

> text would be used,  it would accept only the G.711 audio.
>
>       Contact: <uri>;text
>
>       m=3Daudio 7200 RTP/AVP 0
>
>
>
> If the answering device is an ITD where the user has indicated a =20
> preference for text, it would accept the text/t140 medium and =20
> optionally G.711 audio.
>
>       Contact: <uri>;text
>
>        m=3Daudio 7200 RTP/AVP 0
>
>        m=3Dtext 7202 RTP/AVP 99
>
>        a=3Drtpmap:99 t140/1000
>
> Note that this response is only possible when the gateway had =20
> included text/140 in the offer. For other cases, the terminal needs =20=

> to do a reinvite to add text to the call.
>
> D.2.2.2 Call from IP terminal
> A calling ITD could give a strong indication that it requires text =20
> support in the call by an INVITE according to this example:
>
>       Contact: <sip:terminal@host.example.com>;text
>
>       Accept-Contact: *;text;require
>
>        m=3Daudio 7200 RTP/AVP 0
>
>        m=3Dtext 7202 RTP/AVP 99
>
>        a=3Drtpmap:99 t140/1000
>
>
>
> The network would make efforts to connect to a text capable =20
> gateway, that may acknowledge the text channel initially, because =20
> of the indication that text is required. The gateway should also =20
> start text channel connection procedures on the PSTN side.
>
>       Contact: <gwy-uri>;text;duplex=3D"half"
>
>        m=3Daudio 7200 RTP/AVP 0
>
>        m=3Dtext 7202 RTP/AVP 99
>
>        a=3Drtpmap:99 t140/1000
>
>        a=3Dfmtp:99 cps=3D20
>
>       a=3Dcontent:txp
>
>
>
> If on the other hand, the ITD user is not depending on text, but =20
> want to have it available for occasional use, the ITD can be =20
> configured to make its INVITE as follows:
>
>
>
>       Contact: <sip:terminal@host.example.com>;text
>
>       Accept-Contact: *;text
>
>        m=3Daudio 7200 RTP/AVP 0
>
>        m=3Dtext 7202 RTP/AVP 99
>
>        a=3Drtpmap:99 t140/1000
>
>        a=3Dfmtp:99
>
>
>
> The network would try to connect to a text capable gateway, but may =20=

> connect through a non capable. The gateway may decide to not =20
> acknowledge the text channel initially, but indicates its text =20
> capability in the Contact header.
>
>       Contact: <gwy-uri>;text;duplex=3D"half"
>
>        m=3Daudio 7200 RTP/AVP 0
>
>
>
> D.2.2.3 Text channel establishment during a call
> If at a later stage in the call, either party in the call starts =20
> text activity, and no text channel was set up initially, a text =20
> channel should be added to the session by a REINVITE. .
>
> This is an example of how it would be expressed from the gateway,
>
>        Contact: <uri>;text;duplex=3D"half"
>
>        m=3Daudio 7200 RTP/AVP 0
>
>         m=3Dtext 7202 RTP/AVP 99
>
>         a=3Drtpmap:99 t140/1000
>
>         a=3Dfmtp:99 cps=3D20
>
>        a=3Dcontent:txp
>
> The other party should answer with a similar sdp.
>
>
>
> If instead it is the ITD user who starts text activity, a text =20
> channel should be added to the session by a REINVITE from the ITD =20
> according to the following example. .
>
>        Contact: <uri>;text
>
>        m=3Daudio 7200 RTP/AVP 0
>
>        m=3Dtext 7202 RTP/AVP 99
>
>        a=3Drtpmap:99 t140/1000
>
>        a=3Dfmtp:99 cps=3D20
>
>
>
> The gateway should answer with
>
>        Contact: <uri>;text;duplex=3D"half"
>
>        m=3Daudio 7200 RTP/AVP 0
>
>        m=3Dtext 7202 RTP/AVP 99
>
>        a=3Drtpmap:99 t140/1000
>
>        a=3Dfmtp:99 cps=3D20
>
>        a=3Dcontent:txp
>
> .
>
> The line "a=3Dcontent:txp" is sent from the gateway as an indication =20=

> that half duplex procedures should be applied by the users in the =20
> text stream.
>
> D.3 Procedure for terminals including both RFC 4103 and RFC 4351 =20
> support
> In the case when a terminal implements both RFC 4103 and RFC 4351 =20
> for text transport, the following procedures should be applied in =20
> the terminal.
>
> When establishing a call, an ITD may advertise support for ToIP in =20
> accordance with Annex B or Annex C, with one notable important =20
> exception: the ITD shall not include a list of supported =20
> modulations.  Absence of the list of modulations shall be used as =20
> an indicator to the V.151 Gateway that the remote side is an ITD.
>
> Further, ITD devices shall not utilize SSEs in order to control =20
> state transition to ToIP.  Rather, once a media flow is established =20=

> to transport T.140 characters, either the Gateway or the ITD may =20
> transmit text immediately and without further negotiation.  Payload =20=

> type switching is used to transition between AUDIO and Text Relay =20
> modes.
>
> D.4 State transition and text handling
> The following description assumes that a V.151-compliant Gateway is =20=

> in communication with an ITD and media flows have been established =20
> to transport text over IP in accordance with RFC 4103.
>
> When the gateway compliant to this annex detects a PSTN textphone =20
> that it supports using text relay, it shall autonomously connect to =20=

> the textphone.  After connection on the PSTN side, the gateway =20
> shall open the text channel to the ITD. It shall decode the =20
> characters received and transmit those to the ITD, giving proper =20
> respect to the maximum character-per-second (CPS) parameter =20
> advertised by the ITD.  Determining the type of PSTN textphone =20
> device in use is the responsibility of the Gateway and the ITD need =20=

> not concern itself with what kind of PSTN textphone device is =20
> connected to the Gateway.
>
> Likewise, when the ITD first has characters to send to the Gateway =20
> using text/140 payload type, the ITD opens the text channel if it =20
> was not opened before. Then the ITD transmits the characters to the =20=

> Gateway. The Gateway shall perform a probing, as necessary, to =20
> determine the type of PSTN device connected, if any.  While =20
> probing, the Gateway shall buffer any characters received and =20
> transmit those when probing completes and the gateway is connected =20
> to the text phone.  The size of the character buffer is a matter of =20=

> implementation, but should support the reception and buffering of =20
> characters for at least 60 seconds at the specified maximum =20
> character-per-second (CPS) value signaled to the ITD.
>
> If the Gateway does not support the modulation used by the PSTN =20
> textphone device, the Gateway may transmit the received textphone =20
> signals via VBD or the audio stream, depending on the capabilities =20
> of the ITD.  Further, the Gateway may simply discard characters =20
> received from the ITD or transmit them to the PSTN textphone device =20=

> using a pre-provisioned modulation.
>
>
> /
>
> Gunnar
> ----------------------------------------------------------------------=20=

> -------
> Gunnar Hellstr=F6m, Omnitor
> gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se>
> Mob: +46 708 204 288
> Phone: +46 8 556 002 03
> www.omnitor.se <http://www.omnitor.se>
>
>
> -----Original Message-----
> From: Jani Hautakorpi (JO/LMF) [mailto:jani.hautakorpi@ericsson.com]
> Sent: Wednesday, May 17, 2006 10:12 AM
> To: Cullen Jennings
> Cc: gunnar.hellstrom@omnitor.se; degodefroi@gmail.com; Gonzalo
> Camarillo; IETF MMUSIC WG
> Subject: [MMUSIC] Re: ietf-mmusic-sdp-media-content-03
>
>
> Hi Cullen,
>
> Cullen Jennings wrote:
> > I was just reviewing this document and I can't figure out  the
> > difference from user-floor and txp from the point of view describing
> > the content.
>
> Actually, there are no major differences between them, but Gunnar
> Hellstrom and Arnoud van Wijk (in the cc:) really wanted a value that
> was "txp". Gunnar and Arnoud can explain this better, but the main
> reason is that this way they can refer to and further describe the =20
> usage
> of "txp" from some other draft, e.g. ietf-draft-sipping-toip.
>
> > It seems like this might be better to indicate that the
> > content type was "simplex" as normal media is assumed to be =20
> "duplex".
>
> This is a matter of naming. Personally I believe that "user-floor" is
> more descriptive than "simplex", because there can also be such one-=20=

> way
> media that doesn't require user level floor control. What do you =20
> think?
>
> > I'm not sure I like what I am proposing here but I think we need to
> > improve on the definition for these two. The current description =20
> of  txt
> > does not seem to match the requirements for it on the email list  =20=

> and
> > the definition of user-floor I have no idea when to add to a stream.
>
> I would say that "txp" is exactly what was described on the mmusic's
> mailing list, please see the "[MMUSIC] I-D ACTION:
> draft-ietf-mmusic-sdp-media-content-01.txt" thread, starting 18th Feb.
>
> Regarding the addition of "user-floor" to media stream: The device =20
> that
> needs to add this value knows it by itself. For example, a new
> walkie-talkie type of device can know that it requires user level =20
> floor
> control. But of course we can try to elaborate this on the draft, =20
> if you
> want.
>
> > It also might be nice to provide more guidance on what is =20
> appropriate
> > to signal with "content" and what is not. For example, I would =20
> not  want
> > people signaling the mpeg profile using this. I think what we  =20
> want to
> > do here is something like signal the "semantic content" of  the =20
> stream
> > such that an application that is offered multiple streams  can =20
> pick the
> > right stream or map the streams to the users  preferences. Would =20
> it be
> > possible to add more text about what would  not be appropriate to =20=

> use
> > this registry for.
>
> I really can't see how somebody could try to signal the mpeg profile
> with this draft, because it just doesn't have enough features for
> signaling such information. I feel that the possible use scenarios are
> already quite limited, and it's hard for me to invent how anybody =20
> could
> misuse this draft. But, if you (or somebody else) can come up with =20
> some
> valid, non-appropriate use cases, I'm happy to add them to the draft.
>
>
> --
> Jani
>
> _______________________________________________
> 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 Tue Jun 20 22:08:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fss8T-00047k-Ov; Tue, 20 Jun 2006 22:08:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fss8S-00047Z-MU
	for mmusic@ietf.org; Tue, 20 Jun 2006 22:08:04 -0400
Received: from gura.nttv6.jp ([2001:218:1:1040::2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fss8P-0001c6-03
	for mmusic@ietf.org; Tue, 20 Jun 2006 22:08:04 -0400
Received: from nirvana.nttv6.jp (nirvana.nttv6.jp [IPv6:2001:218:1f01:1::2687])
	by gura.nttv6.jp (NTTv6MTA) with ESMTP id B756F1FE3F
	for <mmusic@ietf.org>; Wed, 21 Jun 2006 11:07:57 +0900 (JST)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by nirvana.nttv6.jp (NTTv6MTA) with ESMTP id 6ECB8128F6F
	for <mmusic@ietf.org>; Wed, 21 Jun 2006 11:07:57 +0900 (JST)
Message-ID: <4498A9FE.50904@nttv6.jp>
Date: Wed, 21 Jun 2006 11:07:58 +0900
From: Makoto Saito <ma.saito@nttv6.jp>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: mmusic@ietf.org
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.8 (--)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Subject: [MMUSIC] draft-saito-mmusic-sdes-ipsec-00
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

Hello everyone,

I'm thinking to use sdes extension for IPsec keying
for the use case of device-to-device communication
such as home appliances.

I submitted a draft,
http://www.ietf.org/internet-drafts/draft-saito-mmusic-sdes-ipsec-00.txt

and I'd like to discuss this direction in the ML, and also in Montreal.
Any comments or suggestions will be appreciated.

For reference, I also submitted a req draft before,
http://www.ietf.org/internet-drafts/draft-saito-mmusic-ipsec-negotiation-req-02.txt

And, several implementers actually need such a standard mechanism now,
http://www.ipv6style.jp/en/apps/20040224/index.shtml
http://uopf.org/en/

Thanks,

-- 
Makoto Saito

NTT Communications Corporation


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



From mmusic-bounces@ietf.org Tue Jun 20 23:21:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FstH6-0007cY-2Z; Tue, 20 Jun 2006 23:21:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FstH4-0007cT-Lv
	for mmusic@ietf.org; Tue, 20 Jun 2006 23:21:02 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FstH0-0008IZ-34
	for mmusic@ietf.org; Tue, 20 Jun 2006 23:21:02 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12])
	by rtp-iport-2.cisco.com with ESMTP; 20 Jun 2006 23:20:58 -0400
X-IronPort-AV: i="4.06,158,1149480000"; 
	d="scan'208"; a="90643233:sNHT36313292"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k5L3KvYL012458; 
	Tue, 20 Jun 2006 23:20:57 -0400 (EDT)
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.211);
	Tue, 20 Jun 2006 23:20:57 -0400
Received: from [192.168.1.101] ([10.86.243.91]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 20 Jun 2006 23:20:57 -0400
Message-ID: <4498BB18.8090603@cisco.com>
Date: Tue, 20 Jun 2006 23:20:56 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <4887547D-99F4-4F15-B36A-4A03C16B7BE2@magma.ca>
In-Reply-To: <4887547D-99F4-4F15-B36A-4A03C16B7BE2@magma.ca>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Jun 2006 03:20:57.0182 (UTC)
	FILETIME=[B63077E0:01C694E1]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 515708a075ffdf0a79d1c83b601e2afd
Cc: mmusic@ietf.org
Subject: [MMUSIC] Re: Some more questions and comments on
	draft-ietf-mmusic-ice-08
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

responses inline.

Philip Matthews wrote:

> Jonathan:
> 
> A few questions about the specification:
> 
> 1)  Can a single offer contain candidates for the same media stream  
> that use different transport protocols??
>      The spec seems to handle this case, but I could not find a  
> statement that this is allowed.

Its not allowed in base ICE, which is specific to UDP. But ice-tcp 
allows it, and that is explained there in more detail.

> 
> 2)  Must all components of a candidate use the same transport protocol?

Yes. Again in ICE there is no choice since its UDP only.


> 
> 3) Must the components of a candidate appear together in increasing  
> order in the SDP, or can they appear
>      in any order and intermixed with candidates from other components?

any order. I'll clarify.

> 
> And here are some comments. These are mostly editorial in nature.
> 
> General comments:
> -  Shouldn't this specification reference draft-ietf-mmusic-sdp-new  
> instead of RFC 2327?
>    (See, for example, the references in section 12)

Well, that depends. To date I've been keeping references to rfc2327 to 
avoid normative ref hold at rfc-ed. SDP-new has been a long time coming. 
Its finally approved now, and indeed looks like its in auth48 so we're 
close. I'll change the reference.

> 
> -  RFC 3264 (offer/answer model) and draft-ietf-mmusic-sdp-new state  
> that the address and port
>    in the m/c line is the one used to receive media on. However,  when 
> using ICE in the presence of NAT,
>    this must also be the address and port from which the media is  _sent_.
>    I think it would be helpful to state this explicitly somewhere  near 
> the  beginning of the specification.

Right. Indeed this is a critical aspect of the specification. I added a 
paragraph in the intro which reads:

It's important to point out that, when used with ICE, an agent will
always send and receive media on the same transport address. That is,
if an agent includes a transport address of 192.0.2.1:2444 in its SDP
for receiving RTP packets (and also STUN connectivity checks). It will
not only receive STUN requests and RTP packets on this transport
address, it will also send STUN requests and RTP packets from this
transport address. This property, known as symmetric RTP, is essential
for proper operation of ICE. Peer reflexive transport addresses,
discussed further below, will generally only work when symmetric RTP
is used. Symmetric RTP is also key for keeping NAT bindings alive.


> 
> Section 2:
> -  In the definition of a Relayed Transport Address, it might be  
> helpful to readers to mention TURN.

done.

> 
> 
> Section 7.1:
> -    "... transport addresses for each component of each component  match".
>    Delete "for each component" ?

done.

> 
> Section 7.2:
> 
> -   Must all the components of a given candidate have the same priority?

yes.

>     Section 7.3 says "yes", but I feel that, to a reader looking for  
> this information, section 7.2 would be the
>     logical place to look. Suggest mentioning this in section 7.2 as  well.

Well, I'll mention in 7.2 but it really doesn't belong there. 7.2 is 
quite explicitly about candidates, and not components. Not sure why 
someone would look in 7.2 for information about components.

> 
> -   I think it would be helpful to have a clear statement in this  
> section that the prioritization is between
>     all the candidates for a single media stream, regardless of  their  
> transport type, address type, port, etc.

I updated the first sentence of this section to read:

<t>The prioritization process takes the set of candidates for a
particular media stream and associates each with a priority. This


so its clear we're talking about a single media stream.

> 
> -       "If the active candidate pair in the initial offer is being  
> validated, media will flow to that pair once it is validated."
>    Suggest replacing with
>        "The active candidate pair in the initial offer is validated  
> first, and if that validation succeeds,
>          media will immediately begin to flow between the pair."

ok.

> 
> Section 7.3:
> -        "If there is no active candidate, the agent MUST include an  
> a=inactive attribute.
>           The RTP address and port in the m/c-line is  inconsequential, 
> since it won't be used."
>    In the second sentence, suggest replacing "RTP" by "media", to  make 
> the statement accurate
>    even if something other than RTP is used.

fixed.

> 
> -       "The candidate-id MUST be chosen randomly and contain at  least 
> 24 bits of randomness
>          (this does not mean that  the candidate-id is 24 bits long;  
> just that it has at least 24 bits
>          of randomness)."
>    I personally found this sentence very confusing the first couple  of 
> times I read it.
>    Suggest replacing this with the following text:
>         "The candidate ID MUST be chosen randomly and contain at  least 
> 24 bits of randomness.
>          This means that a candidate ID must be at least 4  characters 
> long, since each character
>          in the base64 alphabet used for candidate IDs contains at  most 
> 6 bits of randomness.
>          A candidate ID MAY be longer than 4 characters, and  different 
> candidate IDs MAY have
>          different lengths."

ok.

> 
> -       "It is needed only to prevent a possible simultaneous selection
>          by two agents within a private network for the useful  lifetime 
> of the
>          software or hardware."
>     This sentence meant nothing to me until I read the example two  
> pages later.
>     Perhaps add a note "(For more explanation, see the example later  in 
> this section)"?

I'd rathre avoid a forward reference. The beefier tutorial now mentions 
the ordering of the candidate pairs and indeed mentions the candidate ID 
for tie breaking. Thus, I can mention that in the explanation, which now 
reads:

same candidate MUST use the same candidate ID used previously. 24 bits
is sufficient because the candidate ID is not providing security (the
much more random password is). Its sole purpose is to make it highly
unlikely that both the offerer and answerer select the same value for
a candidate for the same media stream. Different values for the
candidate ID are required to break ties in the procedure that is used
to order the candidate pairs.
</t>



> 
> 
> -       "... a unique identifier, call the tid"
>   In this section, you use only the term "tid".
>   By contrast, in section 7.4 you always write "transport address ID".
>   Perhaps, in each section, say  "transport address ID or tid" the  
> first time the term appears in that section,
>   and then use tid from then on?

The convention I'm now using is that the only place "tid" is used is in 
the figures where it is too compact to expand it.

> 
> -     "The tid gets combined ... to form the username that is placed  in 
> the STUN checks ...".
>    Perhaps mention the "Transport Address Pair ID"? That is, perhaps  
> reword as follows:
>       "The tid gets combined ... to form the Transport Address Pair  ID 
> (see section 7.4)
>        which is used as the username in the STUN checks ...".

see above.

> 
> 
> Section 12:
> 
> - The rules DIGIT and SP are never defined.

They are defined in RFC 4234, which is referenced prior to the BNF as 
the source of the rules.

>   Suggest stating that they are from section 9 of draft-ietf-mmusic- 
> sdp-new
> 
> -      "   base64-char           = ALPHANUM / DIGIT / "+" / "/"   "
>    Because of the overlap between ALPHANUM and DIGIT,  I suggest it  
> would be less confusing to write this as
>        "   base64-char           = ALPHA  / DIGIT / "+" / "/"   "

agree - good catch.

>   where ALPHA is also defined in section 9 of draft-ietf-mmusic-sdp- new.

ALPHA is also defined in RFC 4234.

>   Alternatively, a rule for "base64-char" is defined explicitly in  
> section 9 of draft-ietf-mmusic-sdp-new
>   (albeit under the comment "      ; sub-rules of 'k='   ").

I think defining it here as using ALPHA and DIGIT is the clearest.

> 
> -  The rule "token" is never defined.
>    Presumably you mean "token" as defined in section 9 of draft-ietf- 
> mmusic-sdp-new?

no, from rfc 3261. The text below says that token is from rfc3261 but 
its not in the comments. I added a comment in the grammar.

> 
> -    "                       addr SP     ;addr from RFC 3266    "
>   Suggest instead using instead either "unicast-address" or  
> "connection-address"
>   both of which are defined in section 9 of draft-ietf-mmusic-sdp-new.

I'll use connection-address. ICE isn't defined for multicast but no 
reason to have the syntax rule it out.

-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 Tue Jun 20 23:29:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FstOn-0004ZY-Rs; Tue, 20 Jun 2006 23:29:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FstOm-0004ZT-Nv
	for mmusic@ietf.org; Tue, 20 Jun 2006 23:29:00 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FstOi-0008S6-8Z
	for mmusic@ietf.org; Tue, 20 Jun 2006 23:29:00 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12])
	by rtp-iport-2.cisco.com with ESMTP; 20 Jun 2006 23:28:56 -0400
X-IronPort-AV: i="4.06,158,1149480000"; 
	d="scan'208"; a="90643488:sNHT34399964"
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 k5L3SuYL013479; 
	Tue, 20 Jun 2006 23:28:56 -0400 (EDT)
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.211);
	Tue, 20 Jun 2006 23:28:55 -0400
Received: from [192.168.1.101] ([10.86.243.91]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 20 Jun 2006 23:28:55 -0400
Message-ID: <4498BCF6.3030602@cisco.com>
Date: Tue, 20 Jun 2006 23:28:54 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Rohan Mahy <rohan.mahy@gmail.com>
Subject: Re: [MMUSIC] quick WGLC comment on ICE
References: <953beacc0604261353g35db3534ld2076960cc780ab0@mail.gmail.com>
In-Reply-To: <953beacc0604261353g35db3534ld2076960cc780ab0@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Jun 2006 03:28:55.0562 (UTC)
	FILETIME=[D35376A0:01C694E2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd3fc8e909678b38737fc606dec187f0
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

I don't think its contradictory at all. 3261 is pretty clear that what 
comes in a provisional response is the same as will come in a 2xx. Its 
just not reliable so you need to send the same answer in the 2xx. Thus, 
if a UAC should receive a 18x with an SDP, even if the 18x is 
unreliable, that constitutes an answer. Where in RFC 3261 does it say 
that whats in the 18x is NOT an answer? Indeed, according to this:

     o  If the initial offer is in an INVITE, the answer MUST be in a
          reliable non-failure message from UAS back to UAC which is
          correlated to that INVITE.  For this specification, that is
          only the final 2xx response to that INVITE.  That same exact
          answer MAY also be placed in any provisional responses sent
          prior to the answer.  The UAC MUST treat the first session
          description it receives as the answer, and MUST ignore any
          session descriptions in subsequent responses to the initial
          INVITE.

If you receive SDP in a 18x you won't even look at the SDP in the 2xx. 
Pretty clear thats the answer.

Given that the entirety of ICE talks about offers and answers only, and 
these are the only concepts in RFC 3264, I don't think it makes sense to 
move away from offer/answer terminology.

Thanks,
Jonathan R.

Rohan Mahy wrote:

> Hi,
> 
> ICE -08 still refers to offers and answers using terminology which 
> contradicts Section 13.2.1 of RFC3261.  By my reading, a session 
> description in an unreliable 18x is never an offer or an answer.  I 
> often describe this as an "early session description" or "courtesy SDP".
> 
> Several places in ICE (particularly Section 8) talk about performing ICE 
> operations once you receive an answer and refer to courtesy SDP as if it 
> is an answer.
> 
> For example, the current wording of Section 8 para 2:
> 
>    ICE requires a series of STUN-based connectivity checks to take place
>    between endpoints.  These checks start from the answerer on
>    generation of its answer, and start from the offerer when it receives
> 
>    the answer.  These checks can take time to complete, and as such, the
>    selection of messages to use with offers and answers can effect
>    perceived user latency.  Two latency of figures are of particular
> 
>    interest.  These are the post-pickup delay and the post-dial delay.
>    The post-pickup delay refers to the time between when a user "answers
>    the phone" and when any speech they utter can be delivered to the
> 
>    caller.  The post-dial delay refers to the time between when a user
>    enters the destination address for the user, and ringback begins as a
>    consequence of having succesfully started ringing the phone of the
> 
>    called party.
> 
> 
> and my proposed rewording:
> 
>    ICE requires a series of STUN-based connectivity checks to take place
>    between endpoints.  These checks start from the answerer on
>    generation of its first session description sent after the offer, 
> 
>    and start from the offerer when it receives
>    this first session description.  If this first message arrives in 
>    an unreliable message, the actual answer will arrive in the first reliable
>    message after the offer.  
> 
> 
>    STUN connectivity checks can take time to complete, and as such, the
>    number and timing of messages used for these checks can affect
>    perceived user latency.  Two latency figures are of particular
> 
>    interest.  These are the post-pickup delay and the post-dial delay.
>    The post-pickup delay refers to the time between when a user "answers
>    the phone" and when any speech they utter can be delivered to the
> 
>    caller.  The post-dial delay refers to the time between when a user
>    enters the destination address for the user, and ringback begins as a
>    consequence of having succesfully started ringing the phone of the
> 
>    called party.
> 
> and also in the 5th paragraph (currently):
> 
>    For this reason, if an offer is received in an INVITE request, the
>    UAS SHOULD immediately gather its candidates and then generate an
> 
>    answer in a provisional response.  When reliable provisional
>    responses are not used, the SDP in the provisional response is not
>    formally the answer; the value in the 200 OK is the actual answer.
>    However, RFC 3261 allows for SDP to appear in an unreliable
> 
>    provisional response, in which case its value has to be identical to
>    the value placed in the 200 OK.  Thus, we refer to the SDP in the
>    provisional response, even when unreliable, as the answer.  To deal
> 
>    with possible losses of the provisional response, it SHOULD be
>    retransmitted until some indication of receipt.  This indication can
>    either be through PRACK [11], or through the receipt of a STUN
>    Binding Request with a correct username and password.  Even if PRACK
> 
>    is not used, the provisional response SHOULD be retransmitted using
>    the exponential backoff described in [11].  Furthermore, once the
>    answer has been sent, the agent SHOULD begin its connectivity checks.
> 
>    Once a candidate reaches the Valid or Recv-Valid state, the UAS has a
>    known-valid path for media packets towards the UAC.  This point is
>    called the connected point in ICE.
> 
> and my proposed rewording:
> 
>    For this reason, if an offer is received in an INVITE request, the
>    UAS SHOULD immediately gather its candidates and then generate a
>    session descripition in a provisional response.  When reliable provisional
> 
>    responses are not used, the SDP in the provisional response is not
>    formally the answer; the value in the 200 OK is the actual answer.
>    However, RFC 3261 encourages implementors to include this "courtesy SDP" 
> 
>    in an unreliable
>    provisional response, in which case its value has to be identical to
>    the value placed in the 200 OK.  To deal
>    with possible losses, the provisional response SHOULD be
>    retransmitted until the UAS receives some indication of receipt.  This indication can
> 
>    either be through PRACK [11], or through the receipt of a STUN
>    Binding Request with a correct username and password.  Even if PRACK
>    is not used, the provisional response SHOULD be retransmitted using
> 
>    the exponential backoff described in [11].  Furthermore, once the
>    session description has been sent, the agent SHOULD begin its connectivity checks.
>    Once a candidate reaches the Valid or Recv-Valid state, the UAS has a
> 
>    known-valid path for media packets towards the UAC.  This point is
>    called the connected point in ICE.
> 
> I can propose specific text for the other usages if other agree this 
> needs to be changed.
> 
> thanks,
> -rohan
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> 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 Wed Jun 21 09:19:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ft2bk-0001d2-6C; Wed, 21 Jun 2006 09:19:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ft2bj-0001cx-6L
	for mmusic@ietf.org; Wed, 21 Jun 2006 09:18:59 -0400
Received: from grerelbas01.net.external.hp.com ([192.6.111.85]
	helo=grerelbas01.bastion.europe.hp.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ft2bd-0002Kd-Sc
	for mmusic@ietf.org; Wed, 21 Jun 2006 09:18:59 -0400
Received: from IDAEXG12.emea.cpqcorp.net (idaexg12.emea.cpqcorp.net
	[16.16.5.39])
	by grerelbas01.bastion.europe.hp.com (Postfix) with ESMTP id 4ABE534083
	for <mmusic@ietf.org>; Wed, 21 Jun 2006 15:18:53 +0200 (CEST)
Received: from IDAEXC04.emea.cpqcorp.net ([16.16.5.63]) by
	IDAEXG12.emea.cpqcorp.net with Microsoft SMTPSVC(6.0.3790.1830);
	Wed, 21 Jun 2006 15:18:52 +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: Wed, 21 Jun 2006 15:18:52 +0200
Message-ID: <29160BFA3AC1A84E877783464A99A2720159F6D7@IDAEXC04.emea.cpqcorp.net>
In-Reply-To: <4498BCF6.3030602@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: ICE grammar and examples mismatch
Thread-Index: AcaU4uxnw9rYVUe2Q7qbVHE5QeFNwgAULVMg
From: "Anzile, Christophe" <christophe.anzile@hp.com>
To: <mmusic@ietf.org>
X-OriginalArrivalTime: 21 Jun 2006 13:18:52.0790 (UTC)
	FILETIME=[3DB7D160:01C69535]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Subject: [MMUSIC] ICE grammar and examples mismatch
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 all,

according
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-ice-08.txt grammar
in chapter 12,

candidate-attribute   =3D "candidate" ":" candidate-id SP ...

however, all examples in chapter 11 do not use the ":" after candidate
keyword.

Example:
a=3Dcandidate $L1 1 UDP 1.0 $L-PRIV-1.IP $L-PRIV-1.PORT
should be:
a=3Dcandidate:$L1 1 UDP 1.0 $L-PRIV-1.IP $L-PRIV-1.PORT

Please correct all the examples in order to conform to the standard SDP
syntax.

Christophe.

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



From mmusic-bounces@ietf.org Wed Jun 21 12:59:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ft63N-0006Cp-8r; Wed, 21 Jun 2006 12:59:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ft63L-00060L-IF
	for mmusic@ietf.org; Wed, 21 Jun 2006 12:59:43 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ft63J-0002Ol-RY
	for mmusic@ietf.org; Wed, 21 Jun 2006 12:59:43 -0400
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	15EF5500003
	for <mmusic@ietf.org>; Wed, 21 Jun 2006 18:59:41 +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, 21 Jun 2006 18:59:40 +0200
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 21 Jun 2006 18:59:40 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 21 Jun 2006 18:59:40 +0200
Message-ID: <5EB80D22825EEE42872083AD5BFFB594017F1166@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: ICE: Client supports, but network doesn't
Thread-Index: AcaVVBXPwYnrUnQhQoO5jnCkyhYnrw==
From: "Christer Holmberg \(JO/LMF\)" <christer.holmberg@ericsson.com>
To: <mmusic@ietf.org>
X-OriginalArrivalTime: 21 Jun 2006 16:59:40.0675 (UTC)
	FILETIME=[1612A530:01C69554]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Subject: [MMUSIC] ICE: Client supports, but network doesn't
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="===============1169414538=="
Errors-To: mmusic-bounces@ietf.org


This is a multi-part message in MIME format.

--===============1169414538==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C69554.15EBD329"


This is a multi-part message in MIME format.

------_=_NextPart_001_01C69554.15EBD329
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Hi,

Some questions on ICE:

1.	What happens if the c/m lines does not correspond to any active
a=3Dcandidate line? This could happen e.g. if you have a SDP modifying
B2BUA (which doesn't support ICE) in the path. One option would be to
say that the connectivity check shall be performed also for the c/m
lines in that case, but then we may need a "default priority", or
something...

2.	The ICE spec says that it is allowed for no a=3Dcandiate line, but
it does not describe what would happen in that case, and what the
expected UA behavior is in that case.

Regards,

Christer



------_=_NextPart_001_01C69554.15EBD329
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.7638.1">
<TITLE>ICE: Client supports, but network doesn't</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>

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

<P><FONT SIZE=3D2 FACE=3D"Courier New">Some questions on ICE:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
What happens if the c/m lines does not correspond to any active =
a=3Dcandidate line? This could happen e.g. if you have a SDP modifying =
B2BUA (which doesn't support ICE) in the path. One option would be to =
say that the connectivity check shall be performed also for the c/m =
lines in that case, but then we may need a &quot;default priority&quot;, =
or something...</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
The ICE spec says that it is allowed for no a=3Dcandiate line, but it =
does not describe what would happen in that case, and what the expected =
UA behavior is in that case.</FONT></P>

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

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

</BODY>
</HTML>
------_=_NextPart_001_01C69554.15EBD329--


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

--===============1169414538==--




From mmusic-bounces@ietf.org Wed Jun 21 16:11:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ft93I-0004Qo-Of; Wed, 21 Jun 2006 16:11:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ft93H-0004Qb-Dq
	for mmusic@ietf.org; Wed, 21 Jun 2006 16:11:51 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ft93G-0007DO-1y
	for mmusic@ietf.org; Wed, 21 Jun 2006 16:11:51 -0400
Received: from sj-dkim-6.cisco.com ([171.68.10.81])
	by sj-iport-4.cisco.com with ESMTP; 21 Jun 2006 13:11:49 -0700
X-IronPort-AV: i="4.06,163,1149490800"; 
	d="scan'208"; a="1830122348:sNHT44263972"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-6.cisco.com (8.12.11/8.12.11) with ESMTP id k5LKBndd018502
	for <mmusic@ietf.org>; Wed, 21 Jun 2006 13:11:49 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id k5LKBjJ4015670
	for <mmusic@ietf.org>; Wed, 21 Jun 2006 13:11:48 -0700 (PDT)
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.211);
	Wed, 21 Jun 2006 13:11:39 -0700
Received: from [10.21.113.175] ([10.21.113.175]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 21 Jun 2006 13:11:38 -0700
Message-ID: <4499A7F9.3090802@cisco.com>
Date: Wed, 21 Jun 2006 16:11:37 -0400
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
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: 21 Jun 2006 20:11:38.0637 (UTC)
	FILETIME=[E7502BD0:01C6956E]
DKIM-Signature: a=rsa-sha1; q=dns; l=2560; t=1150920709; x=1151784709;
	c=relaxed/simple; s=sjdkim6001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fandreas@cisco.com;
	z=From:Flemming=20Andreasen=20<fandreas@cisco.com>
	|Subject:SDP=20Capability=20Negotiation=20to=20address=20multiple=20RTP=20profile
	s=20and=20other=0A=20issues;
	X=v=3Dcisco.com=3B=20h=3DVKWV6f1ckEM6dD0f+ZdRi2OaV+Y=3D;
	b=sUg0Ekji8d29wOpTo0irQJbCqk2styo9reZRxiyOOAqwx04YX9BOYzliJiQzkZBVstQdMGI6
	7Llw6wIOiktobnZF2IAm+3ZPO5RtdLWFK4D/CRP99GJudhj1CB69tS/e;
Authentication-Results: sj-dkim-6.cisco.com; header.From=fandreas@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Subject: [MMUSIC] SDP Capability Negotiation to address multiple RTP
 profiles and other issues
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

Greetings.

Greetings

I have submitted a draft on adding capability negotiation to SDP which 
you can retrieve from (abstract below):

    
http://www.ietf.org/internet-drafts/draft-andreasen-mmusic-sdp-capability-negotiation-00.txt

The primary motivation for this is to address the proliferation of RTP 
profiles and the associated problem of negotiating which of possibly 
several supported RTP profiles to use for a given media stream. For 
example, an entity may support one or more of "vanilla" RTP (RTP/AVP), 
secure RTP (RTP/SAVP), RTP with RTCP-based feedback (RTP/AVPF) or secure 
RTP with RTCP-based feedback (RTP/SAVPF). This is not the only set of 
problems related to capability negotiation though. To that effect, the 
draft contains the following:

- A set of proposed requirements for SDP capability negotiation (not 
just limited to the alternative profile issue)
- Review of existing work related to SDP capability negotiation and 
evaluation of how suitable each is to address the above requirements.
- A proposal for extending SDP with a capability negotiation mechanism 
that addresses the above requirements.

Feedback is hereby solicited. In particular, it would be very helpful if 
people could take a look at the requirements and see if they agree with 
them (too much, too little, anything wrong/missing, etc.) before we get 
into detailed discussion around the proposed solution. Having said that, 
all comments are welcome.

Thanks

-- Flemming


<Abstract>
        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. SDP and its current extensions however do not 
have
        the ability to negotiate one or more alternative transport 
protocols
        (e.g. RTP profiles) which makes it particularly difficult to deploy
        new RTP profiles such as secure RTP and RTP with RTCP-based 
feedback.  
        The purpose of this document is to address that by identifying a 
set
        of requirements, evaluate existing work in this area, and provide a
        recommended solution for extending SDP with capability 
negotiation. 
</Abstract>



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



From mmusic-bounces@ietf.org Thu Jun 22 06:09:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtM7o-0004hg-Mx; Thu, 22 Jun 2006 06:09:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtM7o-0004hY-2T
	for mmusic@ietf.org; Thu, 22 Jun 2006 06:09:24 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtM7m-0001JB-7E
	for mmusic@ietf.org; Thu, 22 Jun 2006 06:09:24 -0400
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	34C474F0199; Thu, 22 Jun 2006 12:09:21 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 22 Jun 2006 12:09:21 +0200
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 22 Jun 2006 12:09:20 +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] How to put multiple ptimes in SDP?
Date: Thu, 22 Jun 2006 12:09:20 +0200
Message-ID: <5EB80D22825EEE42872083AD5BFFB594017F1178@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] How to put multiple ptimes in SDP?
Thread-Index: AcZzSk4gcYILPoZ6Sx+oQw/JdXMaQQimQqkg
From: "Christer Holmberg \(JO/LMF\)" <christer.holmberg@ericsson.com>
To: "Elwell, John" <john.elwell@siemens.com>,
	"Even, Roni" <roni.even@polycom.co.il>,
	"Magnus Westerlund \(KI/EAB\)" <magnus.westerlund@ericsson.com>,
	"Colin Perkins" <csp@csperkins.org>
X-OriginalArrivalTime: 22 Jun 2006 10:09:20.0653 (UTC)
	FILETIME=[EDCF2BD0:01C695E3]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d16ce744298aacf98517bc7c108bd198
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,

RFC3108 defines a "vsel" attribute defined, which allows you to per
codec (codec name is used instead of PT number, which MAY have some
limitations) to specify Packet Length and Packet Time. It does not allow
specifying max/min/list values, though.

Regards,

Christer

-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens.com]=20
Sent: 9. toukokuuta 2006 12:20
To: Even, Roni; Magnus Westerlund (KI/EAB); Colin Perkins
Cc: mmusic@ietf.org
Subject: RE: [MMUSIC] How to put multiple ptimes in SDP?

Roni,

Yes, you are probably right. The minimum packet time is likely to be
independent of codec type (except that obviously for framed codecs the
minimum packet time cannot be less than one frame). Although perhaps
some implementations could handle a slightly faster packet rate for
G.711, say, than for codecs that require more processing.

John=20

> -----Original Message-----
> From: Even, Roni [mailto:roni.even@polycom.co.il]
> Sent: 09 May 2006 09:05
> To: Elwell, John; Magnus Westerlund; Colin Perkins
> Cc: mmusic@ietf.org
> Subject: RE: [MMUSIC] How to put multiple ptimes in SDP?
>=20
> John,
> I understand this is like minptime, but is this per codec or per=20
> media. It looks to me that it is a media parameter.
> Roni
>=20
> > -----Original Message-----
> > From: Elwell, John [mailto:john.elwell@siemens.com]
> > Sent: Tuesday, May 09, 2006 11:01 AM
> > To: Even, Roni; Magnus Westerlund; Colin Perkins
> > Cc: mmusic@ietf.org
> > Subject: RE: [MMUSIC] How to put multiple ptimes in SDP?
> >=20
> > Roni,
> >=20
> > The range is needed in my opinion because of UAs that are unable to=20
> > process packets above a certain rate. I recall trying to test our
> UAs with devices
> > that fell over if we sent audio packets every 10ms.
> >=20
> > John
> >=20
> > > -----Original Message-----
> > > From: Even, Roni [mailto:roni.even@polycom.co.il]
> > > Sent: 09 May 2006 08:40
> > > To: Magnus Westerlund; Colin Perkins
> > > Cc: mmusic@ietf.org
> > > Subject: RE: [MMUSIC] How to put multiple ptimes in SDP?
> > >
> > > Hi,
> > > I also see the need for the ptime extension described in
> the draft.
> > >
> > > I prefer to see the extension to SDP for ptime per payload type=20
> > > but I am not sure why we need the range. The only requirement I=20
> > > saw is due to receiver buffer size, this is not a codec specific=20
> > > requirement and there is a maxptime parameter defined for media in

> > > the sdp draft.
> > >
> > > I am not sure about the usage of address per payload type, I=20
> > > understand the example given so if media security is also=20
> > > addressed I would not object to such an extension.
> > >
> > > Roni Even
> > >
> > > > -----Original Message-----
> > > > From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> > > > Sent: Thursday, May 04, 2006 3:08 PM
> > > > To: Colin Perkins
> > > > Cc: mmusic@ietf.org
> > > > Subject: Re: [MMUSIC] How to put multiple ptimes in SDP?
> > > >
> > > > Hi,
> > > >
> > > > As this discussion pops up again and again I think that is
> > > might be time
> > > > to fix it for people that really want to indicate a
> > > specific amount of
> > > > media for a packet. There is a draft:
> > > >
> > > http://www.ietf.org/internet-drafts/draft-xu-mmusic-sdp-codec-
> > > param-01.txt
> > > >
> > > > That contains a proposal for this together with some
> other things. I
> > > > think the general requirements for the the ptime
> > > replacement is pretty
> > > > good. I personally don't like the solution. I personally
> > > think a single
> > > > attribute for recommended amount of media time in the
> > > payload should be
> > > > defined. example: a=3Drptime:<pt> <value, values, or range>
> > > >
> > > > I am also quite questioning on the per payload transport
> > > addresses. This
> > > > is in my opinion not in line with the structure of the
> media block
> > > > structure and how it relate to RTP sessions etc.
> > > >
> > > > So I think people should review this draft and provide
> > > feedback on this
> > > > topic to possibly make some progress here.
> > > >
> > > > Cheers
> > > >
> > > > Magnus Westerlund
> > > >
> > > > Multimedia Technologies, Ericsson Research EAB/TVA/A
> > > >
> > >=20
> ----------------------------------------------------------------------
> > > > Ericsson AB                | Phone +46 8 4048287
> > > > Torshamsgatan 23           | Fax   +46 8 7575550
> > > > S-164 80 Stockholm, Sweden | mailto:=20
> 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
> > >
> >=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

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



From mmusic-bounces@ietf.org Thu Jun 22 13:00:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtSXw-0000WI-Aa; Thu, 22 Jun 2006 13:00:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtSXv-0000WD-O9
	for mmusic@ietf.org; Thu, 22 Jun 2006 13:00:47 -0400
Received: from mx5-3.spamtrap.magma.ca ([209.217.78.138])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtSXu-0000tF-9X
	for mmusic@ietf.org; Thu, 22 Jun 2006 13:00:47 -0400
Received: from mail2.magma.ca (mail2.internal.magma.ca [10.0.10.12])
	by mx5-3.spamtrap.magma.ca (8.13.1/8.13.1) with ESMTP id k5MH0hK7014168;
	Thu, 22 Jun 2006 13:00:44 -0400
Received: from [10.1.5.219] ([216.13.42.126]) (authenticated bits=0)
	by mail2.magma.ca (Magma's Mail Server) with ESMTP id k5MH0heY027417
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
	Thu, 22 Jun 2006 13:00:44 -0400
In-Reply-To: <4498516B.8070401@cisco.com>
References: <44711429-AACA-40EF-86CE-507552900D39@magma.ca>
	<4498516B.8070401@cisco.com>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <05C331FA-31F7-43E6-8DDB-0C3BA7CC6007@magma.ca>
Content-Transfer-Encoding: 7bit
From: Philip Matthews <philip_matthews@magma.ca>
Date: Thu, 22 Jun 2006 13:00:48 -0400
To: Jonathan Rosenberg <jdrosen@cisco.com>
X-Mailer: Apple Mail (2.746.2)
X-magma-MailScanner-Information: Magma Mailscanner Service
X-magma-MailScanner: Clean
X-Spam-Status: 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 21be852dc93f0971708678c18d38c096
Cc: mmusic@ietf.org
Subject: [MMUSIC] Re: Some comments on draft-ietf-mmusic-ice-08
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

Jonathan:

Thanks very much for your reply.

I am very happy with most of your suggested changes.
Just a few minor comments inline.
[To keep this short, I've trimmed most of your reply.]

Good luck getting out ICE-09!

- Philip


On 20-Jun-06, at 15:50 , Jonathan Rosenberg wrote:

> Thanks for the comments. Responses inline.
>
> Philip Matthews wrote:
>

[---SNIP---]

>> Section 2:
>> - I found it difficult to understand much of the terminology on  
>> my  first pass through
>>   the document, even though I had a basic understanding of how  
>> ICE  works. In the end,
>>   I just skipped over it and then came back later.
>>   Perhaps consider placing the introductory sections before the   
>> terminology section,
>>   perhaps by making sections 3 - 6 subsections of section 1.  If  
>> you  did this,
>>   then the terminology section would clearly divide the  
>> Informative  text from the Normative text.
>
> I like the idea of moving the introduction before terminology, that  
> is fine. Not so sure about the rest. I'm still noodling your  
> proposed reorganization and Rohans, and will do the reorg last as I  
> edit -09.

Ok. I'll wait and see what you come up with ...


[---SNIP---]


>> - I found the definitions of the various Transport Address forms   
>> difficult to understand
>>   (I was familiar with the concepts, but hadn't see the terms   
>> before, and was uncertain for a while
>>   which term matched which concept).
>>   I might be useful to add a diagram (perhaps somewhere in  
>> sections  3-6) that illustrates the
>>   various forms  (Derived, Reflexive, etc...)
>
> I think its clear that the terminology itself needs to really be  
> introduced first in the introduction section, and the terminonology  
> section more of a reference after that.

Great!

> As for a picture, I'll add this into the introduction:
>
>  Please view in a fixed-width font such as
>                   Courier.
>
>
>
>
>
>
>               To Internet
>
>                   |
>                   |
>                   |  /------------  Relayed
>                   | /               Address
>               +--------+
>               |        |
>               |  STUN  |
>               | Server |
>               |        |
>               +--------+
>                   |
>                   |
>                   | /------------  Reflexive
>                   |/               Address
>             +------------+
>             |    NAT     |
>             +------------+
>                   |
>                   | /------------  Local
>                   |/               Address
>               +--------+
>               |        |
>               | Agent  |
>               |        |
>               +--------+
>

Looks good.



[---SNIP---]

>
>
>> - (page 14, indented paragraph)
>>   "The ability to process STUN connectivity checks allows for   
>> clients to obtain peer reflexive transport
>>    addresses that can be used by the network server to reach them   
>> without a relay, even through NATs
>>    with restrictive mapping and filtering policies."
>>   I don't understand this sentence.
>>   In general, I found the wording in this indented paragraph to  
>> be  much below the very high standard
>>   set by the rest of the document. Perhaps you might rewrite this   
>> entire paragraph.
>
> Rewritten to:
>
> <list style="indent"> <t>Why would these types of endpoints even
> bother to implement ICE?  The answer is that such an implementation
> greatly facilitates NAT traversal for clients that connect to
> it. Consider a PC softphone behind a NAT whose mapping policy is
> address and port dependent. The softphone initiates a call through a
> gateway that implements ICE. The gateway doesn't obtain any server
> reflexive or relayed transport addresses, but it implements ICE, and
> consequently, is prepared to receive STUN connectivity checks on its
> local transport addresses. The softphone will send a STUN connectivity
> to check to that local transport address, causing the NAT to allocate
> a new binding for the softphone. The connectivity check will inform
> the softphone of this address, allowing it to be used by the gateway
> as a peer reflexive remote candidate. This allows direct media
> transmission between the gateway and softphone, without the need for
> relays. Furthermore, implementation of the STUN connectivity checks
> allows for NAT bindings along the way to be kept open. ICE also
> provides numerous security properties that are independent of NAT
> traversal, and would benefit any multimedia endpoint. See <xref
> target="sec:security"/> for a discussion on these benefits.
> </t></list>
>

This looks good in isolation. Once you have finished ICE-09,
I will re-read the entire document in detail and see how it looks
in context.

>
>
>> Section 12:
>> - In addition to all the SDP examples in section 11, it would be  
>> nice  to see one or two examples of SDP
>>   that do NOT use $L1, $L-PRIV-1.IP, $STUN-PUB-2.PORT, etc.
>>   This would help the reader understand the grammar rules.
>
> You mean with actual values? Sigh...
>

Yes, I do mean with actual values. I don't think it's that hard ...
(I suppose I could have sent suggested text instead. Sorry.
I'll try to do that next time.)






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



From mmusic-bounces@ietf.org Thu Jun 22 14:49:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtUEw-0000Ud-5N; Thu, 22 Jun 2006 14:49:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtUEv-0000UY-Pg
	for mmusic@ietf.org; Thu, 22 Jun 2006 14:49:17 -0400
Received: from mx2-1.spamtrap.magma.ca ([209.217.78.160])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtUEu-0000Mm-CG
	for mmusic@ietf.org; Thu, 22 Jun 2006 14:49:17 -0400
Received: from mail3.magma.ca (mail3.internal.magma.ca [10.0.10.13])
	by mx2-1.spamtrap.magma.ca (8.13.1/8.13.1) with ESMTP id k5MInCot028372;
	Thu, 22 Jun 2006 14:49:12 -0400
Received: from [10.1.5.219] ([216.13.42.126]) (authenticated bits=0)
	by mail3.magma.ca (Magma's Mail Server) with ESMTP id k5MInBn1007768
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT);
	Thu, 22 Jun 2006 14:49:12 -0400
In-Reply-To: <BE6AE8BF-C945-4799-BA3F-704FD0000389@magma.ca>
References: <BE6AE8BF-C945-4799-BA3F-704FD0000389@magma.ca>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <496BBCDD-93D3-4293-BE29-4F3A77C6B2C3@magma.ca>
Content-Transfer-Encoding: 7bit
From: Philip Matthews <philip_matthews@magma.ca>
Date: Thu, 22 Jun 2006 14:49:15 -0400
To: mmusic@ietf.org
X-Mailer: Apple Mail (2.746.2)
X-magma-MailScanner-Information: Magma Mailscanner Service
X-magma-MailScanner: Clean
X-Spam-Status: 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: 
Subject: [MMUSIC] Examples of our proposed modification to ICE
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 Cooper and I have created some examples comparing our proposed  
modification
(in http://www.ietf.org/internet-drafts/draft-matthews-mmusic-ice- 
eliminating-duplicates-00.txt)
to the processing described in the ICE-08 document.

These examples are available at:
      www.magma.ca/~philip_matthews/


- Philip


On 19-Jun-06, at 10:39 , Philip Matthews wrote:

> Folks:
>
> Eric Cooper and I have written an I-D on a proposed modification to  
> ICE that eliminates what we think are some duplicate connectivity  
> checks. In brief, our proposal is to eliminate connectivity checks  
> sent from candidates such as server-reflexive candidates, because  
> we believe these are duplicates of checks sent from the candidates  
> from which the server-reflexive candidates were derived.
>
> To quote from first section of the I-D:
>      "Eliminating checks in this manner has two advantages:
>
>        o  It reduces the number of messages that need to be exchanged
>           between endpoints; and
>
>        o  The remaining checks start earlier, because there are  
> fewer 50msec
>           delays between the start of successive checks. This  
> results in
>           faster identification of desirable paths.
>
>      Compared with [ICE-08], the modification described here typically
>      results in 25% - 50% fewer messages when multiple NATs are  
> involved.
>      Similarly, the highest-priority working candidate can be  
> promoted to
>      the m/c line 25% - 50% faster. Since the savings are a result of
>      eliminating checks from server-reflexive candidates, the  
> reductions
>      are less significant when one of the endpoints has a public IP
>      address."
>
> The I-D is available at
>
>     http://www.ietf.org/internet-drafts/draft-matthews-mmusic-ice- 
> eliminating-duplicates-00.txt
>
> - Philip
>
>
> _______________________________________________
> 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 Jun 22 14:54:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtUKF-0003dd-8v; Thu, 22 Jun 2006 14:54:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtUKD-0003dU-32
	for mmusic@ietf.org; Thu, 22 Jun 2006 14:54:45 -0400
Received: from mx2-1.spamtrap.magma.ca ([209.217.78.160])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtUKB-0000wH-PC
	for mmusic@ietf.org; Thu, 22 Jun 2006 14:54:45 -0400
Received: from mail4.magma.ca (mail4.internal.magma.ca [10.0.10.14])
	by mx2-1.spamtrap.magma.ca (8.13.1/8.13.1) with ESMTP id k5MIsYNf030662;
	Thu, 22 Jun 2006 14:54:34 -0400
Received: from [10.1.5.219] ([216.13.42.126]) (authenticated bits=0)
	by mail4.magma.ca (Magma's Mail Server) with ESMTP id k5MIsXrP024150
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT);
	Thu, 22 Jun 2006 14:54:34 -0400
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <DCA7E185-92EE-453F-A59E-6E62DF227FA5@magma.ca>
Content-Transfer-Encoding: 7bit
From: Philip Matthews <philip_matthews@magma.ca>
Date: Thu, 22 Jun 2006 14:54:37 -0400
To: mmusic@ietf.org
X-Mailer: Apple Mail (2.746.2)
X-magma-MailScanner-Information: Magma Mailscanner Service
X-magma-MailScanner: Clean
X-Spam-Status: 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: Joerg Ott <jo@acm.org>, Colin Perkins <csp@csperkins.org>
Subject: [MMUSIC] Learning Peer-Reflexive Candidates on BEHAVE-compliant NATs
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:

As previously noted, Eric Cooper and I have put up a web page  
containing examples
showing the differences between our proposed modification to ICE and  
[ICE-08].

One of these examples is particularly interesting because it gives an  
example of how
two endpoints can learn a peer-reflexive candidate on a BEHAVE- 
compliant NAT.
Previously, most people believed that peer-reflexive candidates were  
only associated
with symmetric NATs, but this example shows that is not true. In the  
example, there is
a cascaded NAT (or double NAT) situation, so a reflexive candidate  
that would normally
be learned through an exchange with a public STUN server must instead  
be learned through
the peer-reflexive procedures.

Note that this behavior is independent of our proposed modification.  
The peer-reflexive
candidate is learned under both [ICE-08] processing and our proposed  
modification.

The example is available at:

	www.magma.ca/~philip_matthews/

- Philip




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



From mmusic-bounces@ietf.org Thu Jun 22 16:23:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtViB-0000y6-VO; Thu, 22 Jun 2006 16:23:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtViA-0000xq-06
	for mmusic@ietf.org; Thu, 22 Jun 2006 16:23:34 -0400
Received: from web36408.mail.mud.yahoo.com ([209.191.85.143])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FtVi7-0008H0-MA
	for mmusic@ietf.org; Thu, 22 Jun 2006 16:23:33 -0400
Received: (qmail 59059 invoked by uid 60001); 22 Jun 2006 20:23:31 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=Cq4+ZIk/VJs67pySNvLYx/ss2P66HvKrW7z0vsHGcSh9wbJWDydviawUMBwQy82Jo9Up1Lq4V599HXAPG5P25GQoOZNiI45rmFs33I0BxjCkWOeqYiM1fFx7aL+UxNovyR/v+VuD7wFsIBMHBqi4fAUodRLuPrWbzJVtaelvlcE=
	; 
Message-ID: <20060622202331.59054.qmail@web36408.mail.mud.yahoo.com>
Received: from [86.214.130.92] by web36408.mail.mud.yahoo.com via HTTP;
	Thu, 22 Jun 2006 13:23:31 PDT
Date: Thu, 22 Jun 2006 13:23:31 -0700 (PDT)
From: Alan Bergmin <alan.bergmin@yahoo.com>
Subject: RE: [MMUSIC] Protocol Action: 'SDP: Session Description Protocol'
	-resolution declaration for video stream
To: mmusic@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1693626206=="
Errors-To: mmusic-bounces@ietf.org

--===============1693626206==
Content-Type: multipart/alternative; boundary="0-301224618-1151007811=:58555"
Content-Transfer-Encoding: 8bit

--0-301224618-1151007811=:58555
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

I have a similar remark: when I read the draft draft-shacham-sipping-session-mobility-02 (section 6.2), I think it would be nice for some applications to be able to advertize in the SDP the display size available (in pixels) on the terminal, not only for H.263 (as in draft-ietf-avt-rfc2429-bis-08.txt), but for every format. I understand that it would not always be possible to fully use the display capabilities of the terminal according to the different codecs but it can help in some cases of session mobility.
   
  > Hi, I'm looking for the resolution declaration for video
  > stream in SDP. I didn't find anything standard for
  > declaration of video resolution - like "CIF", "QCIF",...
> SHALL be it a part of the "a=fmtp" line of SDP? 
  > Is it any other standard option exists?
> Best regards
>
> Osher


   
   
   

 		
---------------------------------
Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.
--0-301224618-1151007811=:58555
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<div><FONT face=courier>I have a similar remark: when I read the draft draft-shacham-sipping-session-mobility-02 (section 6.2), I think it would be nice for&nbsp;some applications to be able to&nbsp;advertize in the SDP the display size available (in pixels) on the terminal, not only for H.263 (as in draft-ietf-avt-rfc2429-bis-08.txt), but for every format. I understand that it would not always be possible to fully use the display capabilities of the terminal&nbsp;according to the&nbsp;different&nbsp;codecs but it can help in some cases of session mobility.</FONT></div>  <div><FONT face=courier></FONT>&nbsp;</div>  <div><FONT face=courier>&gt; Hi, I'm looking for the resolution declaration for video</FONT></div>  <div><FONT face=courier>&gt; stream in SDP. I didn't find anything standard for</FONT></div>  <div><FONT face=courier>&gt; declaration of video resolution -&nbsp;like "CIF", "QCIF",...<BR>&gt; SHALL be it a part of the "a=fmtp" line of SDP? </FONT></div> 
 <div><FONT face=courier>&gt; Is it any other standard option exists?<BR>&gt; Best regards<BR>&gt;<BR>&gt; Osher<BR><BR></FONT></div>  <div><FONT face=courier></FONT>&nbsp;</div>  <div><FONT face=courier></FONT>&nbsp;</div>  <div><FONT face=courier></FONT>&nbsp;</div><p>&#32;
		<hr size=1><a href="http://us.rd.yahoo.com/mail_us/taglines/postman3/*http://us.rd.yahoo.com/evt=39666/*http://messenger.yahoo.com">Yahoo! Messenger with Voice.</a> PC-to-Phone calls for ridiculously low rates.
--0-301224618-1151007811=:58555--


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

--===============1693626206==--




From mmusic-bounces@ietf.org Thu Jun 22 16:39:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtVxW-00039g-5X; Thu, 22 Jun 2006 16:39:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtVxV-00038c-2A
	for mmusic@ietf.org; Thu, 22 Jun 2006 16:39:25 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtVxV-0001lf-06
	for mmusic@ietf.org; Thu, 22 Jun 2006 16:39:25 -0400
Received: from kal-el.real.com ([207.188.23.4])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FtVwr-0004nw-E1
	for mmusic@ietf.org; Thu, 22 Jun 2006 16:38:47 -0400
Received: from m24947 ([::ffff:192.168.129.50])
	(AUTH: LOGIN csteck, TLS: TLSv1/SSLv3,128bits,RC4-MD5)
	by kal-el.real.com with esmtp; Thu, 22 Jun 2006 13:38:39 -0700
	id 0007C084.449AFFCF.00004875
From: "Chris Steck" <csteck@real.com>
To: "'Alan Bergmin'" <alan.bergmin@yahoo.com>, mmusic@ietf.org
Subject: RE: [MMUSIC] Protocol Action: 'SDP: Session Description
	Protocol'-resolution declaration for video stream
Date: Thu, 22 Jun 2006 13:39:13 -0700
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Thread-Index: AcaWOdLDrMKpR+aCQqqjxaXVNQvK3wAAavZg
In-Reply-To: <20060622202331.59054.qmail@web36408.mail.mud.yahoo.com>
X-Spam-Score: -2.4 (--)
X-Scan-Signature: 93e7fb8fef2e780414389440f367c879
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>
Content-Type: multipart/mixed; boundary="===============0889266639=="
Errors-To: mmusic-bounces@ietf.org
Message-Id: <E1FtVxW-00039g-5X@megatron.ietf.org>

This is a multi-part message in MIME format.

--===============0889266639==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_006A_01C69601.3FD3D9E0"

This is a multi-part message in MIME format.

------=_NextPart_000_006A_01C69601.3FD3D9E0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

In a related veign, has any thought been given to formally employing UAProf
for this purpose, as is done in 3GPP PSS?
 

-Chris 

 


  _____  

From: Alan Bergmin [mailto:alan.bergmin@yahoo.com] 
Sent: Thursday, June 22, 2006 1:24 PM
To: mmusic@ietf.org
Subject: RE: [MMUSIC] Protocol Action: 'SDP: Session Description
Protocol'-resolution declaration for video stream


I have a similar remark: when I read the draft
draft-shacham-sipping-session-mobility-02 (section 6.2), I think it would be
nice for some applications to be able to advertize in the SDP the display
size available (in pixels) on the terminal, not only for H.263 (as in
draft-ietf-avt-rfc2429-bis-08.txt), but for every format. I understand that
it would not always be possible to fully use the display capabilities of the
terminal according to the different codecs but it can help in some cases of
session mobility.
 
> Hi, I'm looking for the resolution declaration for video
> stream in SDP. I didn't find anything standard for
> declaration of video resolution - like "CIF", "QCIF",...
> SHALL be it a part of the "a=fmtp" line of SDP? 
> Is it any other standard option exists?
> Best regards
>
> Osher


 
 
 



  _____  

Yahoo!
<http://us.rd.yahoo.com/mail_us/taglines/postman3/*http://us.rd.yahoo.com/ev
t=39666/*http://messenger.yahoo.com> Messenger with Voice. PC-to-Phone calls
for ridiculously low rates.


------=_NextPart_000_006A_01C69601.3FD3D9E0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2912" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D818093620-22062006><FONT =
face=3DVerdana=20
color=3D#0000ff size=3D2>In a related veign, has any thought been given =
to formally=20
employing UAProf for this purpose, as is done in 3GPP =
PSS?</FONT></SPAN></DIV>
<DIV>&nbsp;</DIV><!-- Converted from text/rtf format -->
<P><B><I><SPAN lang=3Den-us><FONT face=3DVerdana=20
color=3D#000000>-</FONT></SPAN></I></B><I><SPAN lang=3Den-us><FONT =
face=3DArial=20
color=3D#000000 size=3D4>Chris</FONT></SPAN></I><SPAN =
lang=3Den-us></SPAN> </P>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Alan Bergmin=20
  [mailto:alan.bergmin@yahoo.com] <BR><B>Sent:</B> Thursday, June 22, =
2006 1:24=20
  PM<BR><B>To:</B> mmusic@ietf.org<BR><B>Subject:</B> RE: [MMUSIC] =
Protocol=20
  Action: 'SDP: Session Description Protocol'-resolution declaration for =
video=20
  stream<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><FONT face=3Dcourier>I have a similar remark: when I read the =
draft=20
  draft-shacham-sipping-session-mobility-02 (section 6.2), I think it =
would be=20
  nice for&nbsp;some applications to be able to&nbsp;advertize in the =
SDP the=20
  display size available (in pixels) on the terminal, not only for H.263 =
(as in=20
  draft-ietf-avt-rfc2429-bis-08.txt), but for every format. I understand =
that it=20
  would not always be possible to fully use the display capabilities of =
the=20
  terminal&nbsp;according to the&nbsp;different&nbsp;codecs but it can =
help in=20
  some cases of session mobility.</FONT></DIV>
  <DIV><FONT face=3Dcourier></FONT>&nbsp;</DIV>
  <DIV><FONT face=3Dcourier>&gt; Hi, I'm looking for the resolution =
declaration=20
  for video</FONT></DIV>
  <DIV><FONT face=3Dcourier>&gt; stream in SDP. I didn't find anything =
standard=20
  for</FONT></DIV>
  <DIV><FONT face=3Dcourier>&gt; declaration of video resolution =
-&nbsp;like=20
  "CIF", "QCIF",...<BR>&gt; SHALL be it a part of the "a=3Dfmtp" line of =
SDP?=20
  </FONT></DIV>
  <DIV><FONT face=3Dcourier>&gt; Is it any other standard option =
exists?<BR>&gt;=20
  Best regards<BR>&gt;<BR>&gt; Osher<BR><BR></FONT></DIV>
  <DIV><FONT face=3Dcourier></FONT>&nbsp;</DIV>
  <DIV><FONT face=3Dcourier></FONT>&nbsp;</DIV>
  <DIV><FONT face=3Dcourier></FONT>&nbsp;</DIV>
  <P>
  <HR SIZE=3D1>
  <A=20
  =
href=3D"http://us.rd.yahoo.com/mail_us/taglines/postman3/*http://us.rd.ya=
hoo.com/evt=3D39666/*http://messenger.yahoo.com">Yahoo!=20
  Messenger with Voice.</A> PC-to-Phone calls for ridiculously low=20
rates.</BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_006A_01C69601.3FD3D9E0--



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

--===============0889266639==--





From mmusic-bounces@ietf.org Thu Jun 22 21:40:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtaeY-0001Wv-Dy; Thu, 22 Jun 2006 21:40:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtaeW-0001V5-N0
	for mmusic@ietf.org; Thu, 22 Jun 2006 21:40:08 -0400
Received: from szxga03-in.huawei.com ([61.144.161.55] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtaeU-0002GD-9J
	for mmusic@ietf.org; Thu, 22 Jun 2006 21:40:08 -0400
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J1A00L4GICY7U@szxga03-in.huawei.com> for
	mmusic@ietf.org; Fri, 23 Jun 2006 09:48:34 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J1A00M3JICYZL@szxga03-in.huawei.com> for
	mmusic@ietf.org; Fri, 23 Jun 2006 09:48:34 +0800 (CST)
Received: from w52438 ([10.164.5.32])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0J1A005XKI05PY@szxml03-in.huawei.com> for
	mmusic@ietf.org; Fri, 23 Jun 2006 09:40:57 +0800 (CST)
Date: Fri, 23 Jun 2006 09:39:18 +0800
From: Kylin Wei <weiqikun@huawei.com>
Subject: RE: [MMUSIC] Protocol Action: 'SDP: Session
	DescriptionProtocol'-resolution declaration for video stream
In-reply-to: <E1FtVxW-00039g-B4@megatron.ietf.org>
To: 'Chris Steck' <csteck@real.com>
Message-id: <000f01c69665$d84fa780$2005a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook 11
Thread-index: AcaWOdLDrMKpR+aCQqqjxaXVNQvK3wAAavZgAAoaa4A=
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 8e140a89d08e89747ee196e282ac2228
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="===============1535450481=="
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1535450481==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_MVapJOD2QK14erycvjYtGw)"

This is a multi-part message in MIME format.

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

 

Chris Steck wrote:

>In a related veign, has any thought been given to formally employing UAProf
for this purpose, as is done in 3GPP PSS?

 

 

In 3GPP PSS (TS 26.234) UAProf is used to indicate the capabilities of the
terminal.

For example, the "ScreenSize" attribute states the screen size in pixels.

Kylin Wei 


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

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

<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Dotum;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:SimHei;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"MS UI Gothic";
	panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
	{font-family:DotumChe;
	panose-1:2 11 6 9 0 1 1 1 1 1;}
@font-face
	{font-family:KaiTi_GB2312;
	panose-1:2 1 6 9 3 1 1 1 1 1;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimHei;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:KaiTi_GB2312;
	panose-1:2 1 6 9 3 1 1 1 1 1;}
@font-face
	{font-family:"\@Dotum";
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@DotumChe";
	panose-1:2 11 6 9 0 1 1 1 1 1;}
@font-face
	{font-family:"\@MS UI Gothic";
	panose-1:2 11 6 0 7 2 5 8 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
h1
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:21.6pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-21.6pt;
	page-break-after:avoid;
	mso-list:l1 level1 lfo1;
	font-size:16.0pt;
	font-family:Arial;
	font-weight:bold;}
h2
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:28.8pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-28.8pt;
	page-break-after:avoid;
	mso-list:l1 level2 lfo1;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:normal;}
h3
	{margin-top:13.0pt;
	margin-right:0cm;
	margin-bottom:13.0pt;
	margin-left:36.0pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-36.0pt;
	line-height:172%;
	page-break-after:avoid;
	mso-list:l1 level3 lfo1;
	font-size:12.0pt;
	font-family:"Times New Roman";
	font-weight:normal;}
p.MsoHeader, li.MsoHeader, div.MsoHeader
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	layout-grid-mode:char;
	font-size:9.0pt;
	font-family:Arial;}
p.MsoFooter, li.MsoFooter, div.MsoFooter
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:Arial;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.a, li.a, div.a
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:108.9pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:1.0gd;
	mso-para-margin-right:0cm;
	mso-para-margin-bottom:0cm;
	mso-para-margin-left:108.9pt;
	mso-para-margin-bottom:.0001pt;
	text-align:center;
	text-indent:-18.45pt;
	mso-list:l0 level9 lfo2;
	font-size:9.0pt;
	font-family:Arial;}
p.a0, li.a0, div.a0
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Arial;}
p.a1, li.a1, div.a1
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:center;
	font-size:10.5pt;
	font-family:Arial;
	font-weight:bold;}
p.a2, li.a2, div.a2
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:108.9pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:0cm;
	mso-para-margin-right:0cm;
	mso-para-margin-bottom:1.0gd;
	mso-para-margin-left:108.9pt;
	mso-para-margin-bottom:.0001pt;
	text-align:center;
	text-indent:-18.45pt;
	mso-list:l0 level8 lfo2;
	font-size:9.0pt;
	font-family:Arial;}
p.a3, li.a3, div.a3
	{margin-top:4.0pt;
	margin-right:0cm;
	margin-bottom:4.0pt;
	margin-left:0cm;
	text-align:center;
	page-break-after:avoid;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.a4, li.a4, div.a4
	{margin-top:15.0pt;
	margin-right:0cm;
	margin-bottom:15.0pt;
	margin-left:0cm;
	text-align:center;
	font-size:18.0pt;
	font-family:Arial;}
p.a5, li.a5, div.a5
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.a6, li.a6, div.a6
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	border:none;
	padding:0cm;
	font-size:9.0pt;
	font-family:Arial;}
p.a7, li.a7, div.a7
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:18.0pt;
	border:none;
	padding:0cm;
	font-size:9.0pt;
	font-family:Arial;}
p.a8, li.a8, div.a8
	{margin:0cm;
	margin-bottom:.0001pt;
	text-indent:21.0pt;
	font-size:12.0pt;
	font-family:Arial;
	color:blue;
	font-style:italic;}
span.a9
	{font-family:SimSun;
	color:black;
	font-weight:bold;}
span.aa
	{font-family:SimSun;
	color:black;
	font-weight:bold;}
span.EmailStyle34
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
 /* Page Definitions */
 @page
	{mso-endnote-separator:url("cid:header.htm\@01C696A8.E6077B80") es;
	mso-endnote-continuation-separator:url("cid:header.htm\@01C696A8.E6077B80") ecs;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:65.6pt 90.0pt 72.0pt 90.0pt;
	mso-footer:url("cid:header.htm\@01C696A8.E6077B80") f1;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1123964682;
	mso-list-template-ids:301907670;}
@list l0:level1
	{mso-level-suffix:none;
	mso-level-text:"%1  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:18.0pt;
	mso-bidi-font-size:18.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level2
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:15.0pt;
	mso-bidi-font-size:15.0pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level3
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:12.0pt;
	mso-bidi-font-size:12.0pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level4
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3\.%4  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level5
	{mso-level-tab-stop:2.0cm;
	mso-level-number-position:left;
	margin-left:2.0cm;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level6
	{mso-level-text:"%6\)";
	mso-level-tab-stop:2.0cm;
	mso-level-number-position:left;
	margin-left:2.0cm;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level7
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:2.0cm;
	mso-level-number-position:left;
	margin-left:2.0cm;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level8
	{mso-level-reset-level:level1;
	mso-level-style-link:\63D2\56FE\9898\6CE8;
	mso-level-suffix:space;
	mso-level-text:\56FE%8;
	mso-level-tab-stop:none;
	mso-level-number-position:center;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level9
	{mso-level-reset-level:level1;
	mso-level-style-link:\8868\683C\9898\6CE8;
	mso-level-suffix:space;
	mso-level-text:\8868%9;
	mso-level-tab-stop:none;
	mso-level-number-position:center;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l1
	{mso-list-id:1666475049;
	mso-list-template-ids:-28945502;}
@list l1:level1
	{mso-level-style-link:"\6807\9898 1";
	mso-level-text:%1;
	mso-level-tab-stop:21.6pt;
	mso-level-number-position:left;
	margin-left:21.6pt;
	text-indent:-21.6pt;}
@list l1:level2
	{mso-level-style-link:"\6807\9898 2";
	mso-level-text:"%1\.%2";
	mso-level-tab-stop:28.8pt;
	mso-level-number-position:left;
	margin-left:28.8pt;
	text-indent:-28.8pt;}
@list l1:level3
	{mso-level-style-link:"\6807\9898 3";
	mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	margin-left:36.0pt;
	text-indent:-36.0pt;}
@list l1:level4
	{mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l1:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l1:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l1:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l1:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	margin-left:72.0pt;
	text-indent:-72.0pt;}
@list l1:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:79.2pt;
	mso-level-number-position:left;
	margin-left:79.2pt;
	text-indent:-79.2pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="2078" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="2" />
  <o:regrouptable v:ext="edit">
   <o:entry new="1" old="0" />
   <o:entry new="1" old="0" />
  </o:regrouptable>
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=ZH-CN link=blue vlink=blue>

<div class=Section1>

<p class=MsoNormal><font size=1 color=navy face=Arial><span lang=EN-US
style='font-size:9.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=1 face=Arial><span lang=EN-US style='font-size:
9.0pt;font-family:Arial'>Chris Steck wrote:<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color=blue face=Verdana><span lang=EN-US
style='font-size:10.0pt;font-family:Verdana;color:blue'>&gt;In a related veign,
has any thought been given to formally employing UAProf for this purpose, as is
done in 3GPP PSS?</span></font><span lang=EN-US><o:p></o:p></span></p>

<p class=MsoNormal><font size=1 color=navy face=Arial><span lang=EN-US
style='font-size:9.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=1 color=navy face=Arial><span lang=EN-US
style='font-size:9.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=1 face=Arial><span
lang=EN-US style='font-size:9.0pt;font-family:Arial'>In 3GPP PSS (TS 26.234)
UAProf is used to indicate the capabilities of the terminal.<o:p></o:p></span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=1 face=Arial><span
lang=EN-US style='font-size:9.0pt;font-family:Arial'>For example,</span></font><span
lang=EN-US> </span><font size=1 face=Arial><span lang=EN-US style='font-size:
9.0pt;font-family:Arial'>the &#8220;ScreenSize&#8221; attribute states the
screen size in pixels.<o:p></o:p></span></font></p>

<div>

<p><font size=2 color=navy face="Times New Roman"><span lang=EN-US
style='font-size:10.0pt;color:navy'>Kylin Wei </span></font><span lang=EN-US><o:p></o:p></span></p>

</div>

</div>

</body>

</html>

--Boundary_(ID_MVapJOD2QK14erycvjYtGw)--


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

--===============1535450481==--




From mmusic-bounces@ietf.org Fri Jun 23 00:52:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtdeJ-0003O6-9p; Fri, 23 Jun 2006 00:52:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtdeH-0003O0-3Z
	for mmusic@ietf.org; Fri, 23 Jun 2006 00:52:05 -0400
Received: from kal-el.real.com ([207.188.23.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtdeF-0003f0-HB
	for mmusic@ietf.org; Fri, 23 Jun 2006 00:52:05 -0400
Received: from m24947 ([::ffff:67.42.102.229])
	(AUTH: LOGIN csteck, TLS: TLSv1/SSLv3,128bits,RC4-MD5)
	by kal-el.real.com with esmtp; Thu, 22 Jun 2006 21:51:51 -0700
	id 0007C032.449B7368.00007739
From: "Chris Steck" <csteck@real.com>
To: "'Kylin Wei'" <weiqikun@huawei.com>
Subject: RE: [MMUSIC] Protocol Action: 'SDP: Session
	DescriptionProtocol'-resolution declaration for video stream
Date: Thu, 22 Jun 2006 21:52:30 -0700
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <000f01c69665$d84fa780$2005a40a@china.huawei.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Thread-index: AcaWOdLDrMKpR+aCQqqjxaXVNQvK3wAAavZgAAoaa4AABzcUgA==
X-Spam-Score: 0.4 (/)
X-Scan-Signature: ca81a19b939ce054f98c8f830c2d7742
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="===============2084279395=="
Errors-To: mmusic-bounces@ietf.org
Message-Id: <E1FtdeJ-0003O6-9p@megatron.ietf.org>

This is a multi-part message in MIME format.

--===============2084279395==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0003_01C69646.2A12A560"

This is a multi-part message in MIME format.

------=_NextPart_000_0003_01C69646.2A12A560
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Right.  My question was has there been thought around leveraging the UAProf
formally as part of SDP rfc?
 

-Chris 

 


  _____  

From: Kylin Wei [mailto:weiqikun@huawei.com] 
Sent: Thursday, June 22, 2006 6:39 PM
To: 'Chris Steck'
Cc: 'Alan Bergmin'; mmusic@ietf.org
Subject: RE: [MMUSIC] Protocol Action: 'SDP: Session
DescriptionProtocol'-resolution declaration for video stream



 

Chris Steck wrote:

>In a related veign, has any thought been given to formally employing UAProf
for this purpose, as is done in 3GPP PSS?

 

 

In 3GPP PSS (TS 26.234) UAProf is used to indicate the capabilities of the
terminal.

For example, the "ScreenSize" attribute states the screen size in pixels.

Kylin Wei 


------=_NextPart_000_0003_01C69646.2A12A560
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2912" name=3DGENERATOR><!--[if !mso]>
<STYLE>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</STYLE>
<![endif]-->
<STYLE>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Dotum;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:SimHei;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"MS UI Gothic";
	panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
	{font-family:DotumChe;
	panose-1:2 11 6 9 0 1 1 1 1 1;}
@font-face
	{font-family:KaiTi_GB2312;
	panose-1:2 1 6 9 3 1 1 1 1 1;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimHei;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:KaiTi_GB2312;
	panose-1:2 1 6 9 3 1 1 1 1 1;}
@font-face
	{font-family:"\@Dotum";
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@DotumChe";
	panose-1:2 11 6 9 0 1 1 1 1 1;}
@font-face
	{font-family:"\@MS UI Gothic";
	panose-1:2 11 6 0 7 2 5 8 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
h1
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:21.6pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-21.6pt;
	page-break-after:avoid;
	mso-list:l1 level1 lfo1;
	font-size:16.0pt;
	font-family:Arial;
	font-weight:bold;}
h2
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:28.8pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-28.8pt;
	page-break-after:avoid;
	mso-list:l1 level2 lfo1;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:normal;}
h3
	{margin-top:13.0pt;
	margin-right:0cm;
	margin-bottom:13.0pt;
	margin-left:36.0pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-36.0pt;
	line-height:172%;
	page-break-after:avoid;
	mso-list:l1 level3 lfo1;
	font-size:12.0pt;
	font-family:"Times New Roman";
	font-weight:normal;}
p.MsoHeader, li.MsoHeader, div.MsoHeader
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	layout-grid-mode:char;
	font-size:9.0pt;
	font-family:Arial;}
p.MsoFooter, li.MsoFooter, div.MsoFooter
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:Arial;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.a, li.a, div.a
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:108.9pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:1.0gd;
	mso-para-margin-right:0cm;
	mso-para-margin-bottom:0cm;
	mso-para-margin-left:108.9pt;
	mso-para-margin-bottom:.0001pt;
	text-align:center;
	text-indent:-18.45pt;
	mso-list:l0 level9 lfo2;
	font-size:9.0pt;
	font-family:Arial;}
p.a0, li.a0, div.a0
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Arial;}
p.a1, li.a1, div.a1
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:center;
	font-size:10.5pt;
	font-family:Arial;
	font-weight:bold;}
p.a2, li.a2, div.a2
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:108.9pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:0cm;
	mso-para-margin-right:0cm;
	mso-para-margin-bottom:1.0gd;
	mso-para-margin-left:108.9pt;
	mso-para-margin-bottom:.0001pt;
	text-align:center;
	text-indent:-18.45pt;
	mso-list:l0 level8 lfo2;
	font-size:9.0pt;
	font-family:Arial;}
p.a3, li.a3, div.a3
	{margin-top:4.0pt;
	margin-right:0cm;
	margin-bottom:4.0pt;
	margin-left:0cm;
	text-align:center;
	page-break-after:avoid;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.a4, li.a4, div.a4
	{margin-top:15.0pt;
	margin-right:0cm;
	margin-bottom:15.0pt;
	margin-left:0cm;
	text-align:center;
	font-size:18.0pt;
	font-family:Arial;}
p.a5, li.a5, div.a5
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.a6, li.a6, div.a6
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	border:none;
	padding:0cm;
	font-size:9.0pt;
	font-family:Arial;}
p.a7, li.a7, div.a7
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:18.0pt;
	border:none;
	padding:0cm;
	font-size:9.0pt;
	font-family:Arial;}
p.a8, li.a8, div.a8
	{margin:0cm;
	margin-bottom:.0001pt;
	text-indent:21.0pt;
	font-size:12.0pt;
	font-family:Arial;
	color:blue;
	font-style:italic;}
span.a9
	{font-family:SimSun;
	color:black;
	font-weight:bold;}
span.aa
	{font-family:SimSun;
	color:black;
	font-weight:bold;}
span.EmailStyle34
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
 /* Page Definitions */
 @page
	{mso-endnote-separator:url("cid:header.htm\@01C696A8.E6077B80") es;
	=
mso-endnote-continuation-separator:url("cid:header.htm\@01C696A8.E6077B80=
") ecs;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:65.6pt 90.0pt 72.0pt 90.0pt;
	mso-footer:url("cid:header.htm\@01C696A8.E6077B80") f1;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1123964682;
	mso-list-template-ids:301907670;}
@list l0:level1
	{mso-level-suffix:none;
	mso-level-text:"%1  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:18.0pt;
	mso-bidi-font-size:18.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level2
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:15.0pt;
	mso-bidi-font-size:15.0pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level3
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:12.0pt;
	mso-bidi-font-size:12.0pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level4
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3\.%4  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level5
	{mso-level-tab-stop:2.0cm;
	mso-level-number-position:left;
	margin-left:2.0cm;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level6
	{mso-level-text:"%6\)";
	mso-level-tab-stop:2.0cm;
	mso-level-number-position:left;
	margin-left:2.0cm;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level7
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:2.0cm;
	mso-level-number-position:left;
	margin-left:2.0cm;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level8
	{mso-level-reset-level:level1;
	mso-level-style-link:\63D2\56FE\9898\6CE8;
	mso-level-suffix:space;
	mso-level-text:\56FE%8;
	mso-level-tab-stop:none;
	mso-level-number-position:center;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level9
	{mso-level-reset-level:level1;
	mso-level-style-link:\8868\683C\9898\6CE8;
	mso-level-suffix:space;
	mso-level-text:\8868%9;
	mso-level-tab-stop:none;
	mso-level-number-position:center;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l1
	{mso-list-id:1666475049;
	mso-list-template-ids:-28945502;}
@list l1:level1
	{mso-level-style-link:"\6807\9898 1";
	mso-level-text:%1;
	mso-level-tab-stop:21.6pt;
	mso-level-number-position:left;
	margin-left:21.6pt;
	text-indent:-21.6pt;}
@list l1:level2
	{mso-level-style-link:"\6807\9898 2";
	mso-level-text:"%1\.%2";
	mso-level-tab-stop:28.8pt;
	mso-level-number-position:left;
	margin-left:28.8pt;
	text-indent:-28.8pt;}
@list l1:level3
	{mso-level-style-link:"\6807\9898 3";
	mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	margin-left:36.0pt;
	text-indent:-36.0pt;}
@list l1:level4
	{mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l1:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l1:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l1:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l1:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	margin-left:72.0pt;
	text-indent:-72.0pt;}
@list l1:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:79.2pt;
	mso-level-number-position:left;
	margin-left:79.2pt;
	text-indent:-79.2pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"2078" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"2" />
  <o:regrouptable v:ext=3D"edit">
   <o:entry new=3D"1" old=3D"0" />
   <o:entry new=3D"1" old=3D"0" />
  </o:regrouptable>
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DZH-CN vLink=3Dblue link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D314455004-23062006><FONT =
face=3DVerdana=20
color=3D#0000ff size=3D2>Right.&nbsp; My question was has there been =
thought around=20
leveraging the UAProf&nbsp;formally as part of SDP<SPAN=20
class=3D495025204-23062006> rfc?</SPAN></FONT></SPAN></DIV>
<DIV>&nbsp;</DIV><!-- Converted from text/rtf format -->
<P><B><I><SPAN lang=3Den-us><FONT face=3DVerdana=20
color=3D#000000>-</FONT></SPAN></I></B><I><SPAN lang=3Den-us><FONT =
face=3DArial=20
color=3D#000000 size=3D4>Chris</FONT></SPAN></I><SPAN =
lang=3Den-us></SPAN> </P>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Kylin Wei =
[mailto:weiqikun@huawei.com]=20
  <BR><B>Sent:</B> Thursday, June 22, 2006 6:39 PM<BR><B>To:</B> 'Chris=20
  Steck'<BR><B>Cc:</B> 'Alan Bergmin'; =
mmusic@ietf.org<BR><B>Subject:</B> RE:=20
  [MMUSIC] Protocol Action: 'SDP: Session =
DescriptionProtocol'-resolution=20
  declaration for video stream<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">Chris Steck=20
  wrote:<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DVerdana color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Verdana">&gt;In a =
related=20
  veign, has any thought been given to formally employing UAProf for =
this=20
  purpose, as is done in 3GPP PSS?</SPAN></FONT><SPAN=20
  lang=3DEN-US><o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">In 3GPP PSS (TS 26.234) =
UAProf is=20
  used to indicate the capabilities of the=20
terminal.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">For =
example,</SPAN></FONT><SPAN=20
  lang=3DEN-US> </SPAN><FONT face=3DArial size=3D1><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">the =
&#8220;ScreenSize&#8221; attribute states=20
  the screen size in pixels.<o:p></o:p></SPAN></FONT></P>
  <DIV>
  <P><FONT face=3D"Times New Roman" color=3Dnavy size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy">Kylin Wei </SPAN></FONT><SPAN=20
  =
lang=3DEN-US><o:p></o:p></SPAN></P></DIV></DIV></BLOCKQUOTE></BODY></HTML=
>

------=_NextPart_000_0003_01C69646.2A12A560--



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

--===============2084279395==--





From mmusic-bounces@ietf.org Fri Jun 23 04:26:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtgzJ-0000Ri-8p; Fri, 23 Jun 2006 04:26:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtgzH-0000Rd-KL
	for mmusic@ietf.org; Fri, 23 Jun 2006 04:25:59 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtgzF-0000rh-Tv
	for mmusic@ietf.org; Fri, 23 Jun 2006 04:25:59 -0400
Received: from rtp-core-2.cisco.com ([64.102.124.13])
	by rtp-iport-2.cisco.com with ESMTP; 23 Jun 2006 04:25:57 -0400
X-IronPort-AV: i="4.06,168,1149480000"; 
	d="scan'208"; a="90847911:sNHT37809186"
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 k5N8Pvno026153; 
	Fri, 23 Jun 2006 04:25:57 -0400 (EDT)
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.211);
	Fri, 23 Jun 2006 04:25:57 -0400
Received: from [192.168.1.101] ([10.86.240.32]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 23 Jun 2006 04:25:56 -0400
Message-ID: <449BA594.1070505@cisco.com>
Date: Fri, 23 Jun 2006 04:25:56 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <E73A1B12-39D5-48B6-9955-5754A2858324@magma.ca>
In-Reply-To: <E73A1B12-39D5-48B6-9955-5754A2858324@magma.ca>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Jun 2006 08:25:57.0015 (UTC)
	FILETIME=[A690E270:01C6969E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8da0cbf8c1eef8eab03772f2044efec0
Cc: mmusic@ietf.org
Subject: [MMUSIC] Re: Still more questions and comments on
	draft-ietf-mmusic-ice-08
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

responses inline.

Philip Matthews wrote:

> Jonathan:
> 
> Below are some more questions and comments on draft-ietf-mmusic-ice-08.
> 
> - Philip
> 
> Technical comments and questions
> ============================
> 
> 1)  If there are three m/c lines in the SDP, does the agent construct  
> three candidate pair check orderings,
>      or just one ordering containing the candidates for all three  media 
> streams?

Just one. It has to be that way. The q-values are relative only to
candidates within the same media stream. There is no way to obtain a
relative ordering across media streams. I do think that section 7.5 is
pretty clear that these various lists are per media stream.



>      Viewed another way, is there just one Ta timer, or one Ta timer  
> per m/c line?

It would be one Ta timer per m/c line. I've clarified that:

<t>Every Ta seconds, the agent starts a new connectivity check for a
transport address pair, for each media stream. Thus, if there are 3
media streams, the checks will be paced out at 3/Ta checks per
second. The check is started for the first transport
address pair in the transport address pair check ordered list (which
will be part of the active candidate) that is in the Waiting



>      Taking this even farther, if the agent is taking to two or more  
> different remote agents (because it is
>      trying to establish two different call legs, perhaps for the  same 
> call or perhaps for different calls),
>      then is the result one or multiple candidate pair check orderings?
>      (It seems to me that, to reduce the load on intervening NATs,  
> there should be just one.)

There needs to be multiple timers, but you can keep the rate down by
reducing the value of Ta proportional to the number of media streams.
The draft doesn't say that, but I think its a good change to make. What
I did was define a separate timer Tb, used for connectivity checks. Ta
is the timer for gathering. Tb SHOULD scale with the number of media
streams, default is N*50ms.

That doesn't account for inter-dialog checks, but I think thats a
sufficiently rare case, and sufficiently complicated to do, that I'd
rather not specify that.

I also added a randomization factor in front of Tb, between .7 and 1.3.
Unless you do that, you are likely to get synchronization of
connectivity checks across media streams, which may interact badly with
NATs and who knows what else.


> 
> 2)  When an agent receives a STUN Request, section 7.8 seems to say  
> that the agent validates
>       the request and sends a reply based only on local information.  In 
> particular, the USERNAME
>       is validated by checking for a match on the local tid (and not  
> the remote tid).
>       The reason for this seems to be the case when an the offerer  
> receives a STUN Request but has
>       not yet received the answer from the remote agent. (This case  is 
> presumably pretty common since
>       STUN Requests go directly, but signaling goes indirectly).

Right.

>       In this case, the text seems to say that the STUN Request is  
> validated and a STUN response sent
>       immediately,  and information about the STUN Request is stored  
> for further processing once
>       the answer is received.

Right.

>       However, I can see implementations deciding instead to ignore  
> STUN Requests where there is not
>       an exact match for the USERNAME.  I can see them doing this  for 
> three reasons:
>       a) It is easier. In this case, there is no need to queue up  
> information about the STUN Request for
>           later processing when the answer arrives.

Sure, its easier not to do this. It also increases the latency big time.

>       b) For security. The agent might be acting as a STUN server  for 
> more than one STUN usage, and use the
>           USERNAME to differentiate the usages. For security and  
> because of DoS attacks, the agent
>           simply ignores STUN Requests with unknown USERNAMES.

No - this is a STUN server running on the rtp port. It makes no sense to
use it for other usages.

>       c) Better validity checking. If an agent just does a prefix  
> match, then USERNAMES corresponding
>           to illegal transport address combinations are not detected.
>           For example, a request with USERNAME "Lxx:1:Ryy: 2" 
> (mismatched component ids) or
>           a request where the candidates are from different media  
> streams, or use different transport addresses, etc.
>       My proposal is that:
>        - An agent always does an exact match against the USERNAME  when 
> a STUN Request arrives.
>        - The answerer waits some time (say 50 or 100 msec) before  
> starting its connectivity checks,
>          or waits until it receives a STUN Request from the offerer,
>          or doesn't bother waiting at all (because things will work  out 
> anyway after retries).

I strongly oppose this change. Latency has been a big issue for ICE, and
this is an automatic 100ms penalty. Also not clear that 100ms is big
enough. With the current text, you don't need a hard-to-tune timer here,
and it works as fast as it can. Sure, its a bit more complicated, but
this is hard stuff, what can I say.

> 
> 3) Another reason to do an exact match against the USERNAME might be  
> the following.
>     Consider two agents, L and R and a candidate pair Lxx:1:Ryy:2.
>     L sends a STUN Request for this pair and receives a success  
> response, and thus
>     moves its local state machine into the Recv-Wait state.
>     R sends a STUN Request for this pair, but due to some problem,
>     L does not like this request, and sends an error response,
>     which causes R to give up and move into the Invalid state.
>     At this point, L continues to send STUN Requests each Tr interval ,
>     and R replies with a success response, and the candidate pair  
> remains stuck
>     in the (RECV-WAIT, INVALID) state combination.
>     To avoid this problem, it might be appropriate for an agent to  
> return an error response,
>     when its local state machine is in the Invalid state.

This won't happen. The Tr interval is really only for the active
candidate once its promoted. That interval is HUGE - like 15s. 15s after
the first offer/answer exchange, we've either found a candidate pair
that works, promoted it, and removed the other candidates (including
this bad one), or the call has failed.

In any case, rejecting the stun requests because your own view of the
candidate pair is invalid is also a bad idea - it won't work with peer
reflexives, where this is likely to happen.

> 
> 4) According to section 7.10.1, when an agent receives a STUN request  
> and discovers a new
>     peer reflexive transport address, the agent generates a new  
> candidate id from candidate IDs
>     of the candidate pair specified by the USERNAME:
>           "In particular, the candidate ID is constructed by
>            concatenating the remote candidate ID with the native  
> candidate ID (without the colon)."
>     It is possible, due to routing changes or a glitch in the  
> intervening NAT(s),
>     that the same candidate pair might generate TWO or more peer  
> reflexive transport addresses.
>     For example, say L and R are the two agents. The network in  which R 
> resides is configured
>     to send packets through NAT box N1 in normal use, but if N1  fails, 
> packets are sent through
>     NAT box N2.
>     For a given candidate pair, R sends multiple STUN Requests to L.  It 
> may be that the first
>     STUN Request goes through N1, but the second goes through N2.  This 
> causes L to see
>     two different peer reflexive transport addresses for the same  
> USERNAME.
>     These two peer reflexive transport addresses will be assigned  the 
> same candidate ID by L,
>     violating the rule that candidate IDs must be unique.
>     I can see two possible ways to handle this situation:
>     a) Append a string to the candidate ID to ensure they are unique  
> (e.g., "1", "2", ...),  OR
>     b) Use the last (or the first) peer reflexive transport address  
> seen for this USERNAME.
>     Option (a) is may be tricky, especially when the remote  
> (generating) candidate has multiple components,
>     so I suggest option (b).

You need to split this into two different cases, since the two are
handled differently.

One case is where there is a nat failure mid-transaction, so that the
source IP address of two binding requests (which would be retransmits)
within the same transaction, as seen by the stun server, are different.
The second case is where the nat failure occurs between a pair of
successful checks.

The first case is challenging, and I basically agree with option (b) - 
using the first address in particular. I've added text in -09 to cover 
this case. Interestingly, there was a specific spot int he document 
where the condition where this might happen is mentioned, but the 
document said it was impossible to happen. I've changed that and 
described what to do.

The second case is actually handled well by ICE; it will properly notice 
the change in binding, revalidate and re-invite.


> 
> 
> 5)  How are two candidate IDs of different lengths compared? My  
> assumption is that the shorter
>      one is padded at the end with Null's (0x00) until the two IDs  have 
> the same length.
>      Is this correct?
>      If so, then am I just confused, or is there an error in the  
> following sentence?
>        "For example, the candidate with candidate ID agD is greater  
> than the candidate with ID ad7,
>         and both of those are greater than the candidate with ID zz."
>     I would have thought that, in reverse lexicographic order, the  IDs 
> would have be ordered as
>     zz, agD, ad7, since the "zz" is padded at the end with a Null  
> character.

No. zz is small since it has two 'digits'. Just like 99 is less than 
112. However, this is all still not that clear since ROhan complained 
about it too, so I will try to make it clearer.

> 
> 6) If agent L has two candidates with the same derived address (but  
> different local addresses)
>    and picks one of the candidates as the one to put in the m/c  line, 
> then as the spec points out,
>    the remote agent won't know which candidate the m/c line  corresponds 
> to. The spec recommends
>    the remote agent just guesses and picks one to move to the head  of 
> the check ordering.
>    Wouldn't it be better to:
>      - Move BOTH candidates to the head of the ordering, or
>      - Somehow indicate in the SDP which candidate was chosen?
>   In other words, this case breaks the requirement that both  endpoints 
> create the same
>   candidate pair check ordering.

Good point. I've changed it so both of them go to the head. This 
required some changes in the text which discusses when to promote, and 
I've come up with a better description of that also.


> 
> 
> 7)  Am I correct in saying that none of the example candidate IDs in  
> the document are actually legal?
>      Because they are all too short?
>      If so, it might be useful to use realistic candidate IDs or at  
> least say something about this.

I changed them to legal candidate IDs in cases where they weren't part 
of a figure, where four characters would make the figure too big. In 
that case, I called this out.

> 
> 8) In section 7.6, there is the sentence:
>           "The check is started for the first transport address pair  in 
> the transport address
>            pair check ordered list (which will be part of the active  
> candidate) that is
>            in the Waiting state"
>     I don't understand the part in parentheses.
>     Don't we check all the pairs, not just the pairs associated with  
> the active candidate?

Its a bug, leftover I think. Text in parentheses was deleted.

> 
> 
> Editorial comments
> ===============
> 
> General:
> 
> - In a number of places in the document, you use the phrase   "reflexive 
> or relayed"
>   where it would be more general and more accurate to say "derived".
>   (For example, "reflexive or relayed candidate", rather than  "derived 
> candidate", etc).

It makes sense in a couple, but not all. I changed a few of them.

> 
> - In the first part of the document, you use "NAT" to mean the  
> technology (i.e., "Network Address Translation"),
>   for example in "Numerous solutions have been proposed for allowing  
> these protocols to
>    operate through NAT" in section 1.  But later in the document,  you 
> start using "NAT" to
>    mean a single box (i.e., "Network Address Translator"), for example
>    "...when two agents are separated by a NAT ..."  in section 7.10.
>   It would be nice if you were consistent.
>   In my opinion, the most common usage is to use "NAT" to refer to a  
> single device and "NATs" when
>   referring to multiple devices. However, I would be happy with  another 
> solution as long as the usage
>   was consistent and made explicit.

The document uses the term "a NAT" or "the NAT" when referring to the 
box, and just "NAT" when referring to the technology. I believe that is 
consistent with common usage.

> 
> 
> Section 7.1:
> 
> - "... transport addresses for each component of each component  match 
> ...".
>    I suggest deleting "for each component".

fixed.

> 
> 
> Section 7.3:
> 
> -      "even if the transport address from a previous  session was  
> being recycled."
>   For consistency (in verb tense) with the rest of the sentence,  
> suggest changing "was" to "is".

ok.

> 
> -    "In this case, thats ...".
>   "thats" should be either "that's" or "that is".

ok.

> 
> -    "10.0.1.1:8866 and 8877".
>   I understand what you are trying to say here,  but you never  explain 
> this notation,
>   and this paragraph is the only place in the document where you use  it.
>   (It is not, for example, legal in the a=candidate lines).
>   Furthermore, you have just been talking about using a colon to  
> construct tids and usernames.

IP-addr:port is widely used notation. Anyway I have explained it on 
first usage.

>   Perhaps write this in a different way to make sure the reader  
> understands?
>   Note also that a few sentences later, you say
>          "A will send a STUN request to 10.0.1.1:8866 and 8877"
>   when what you really mean is
>          "A will send one STUN request to 10.0.1.1:8866 and another  
> STUN request to 10.0.1.1:8877".

fixed.

> 
> -     "To fix this, tid takes on ..."
>   For consistency with previous usage, I think there should be a  "the" 
> before "tid", so the sentence reads
>        "To fix this, the tid takes on ..."

ok.

> 
> - "ususally" should be "usually"

fixed.

> 
> 
> Section 7.4:
> 
> - (first two PPs) The intermixing of the running example and the  
> specification in these paragraphs
>   is a bit confusing, because it is not clear which statements are  
> normative and which just apply
>   to the example. Suggest splitting the example out into its own  
> paragraph.

done.

> 
> -      "If an offer/answer exchange took place for a session  comprised 
> of an audio
>          and a video stream, and each agent had two candidates per  media
>          stream, there would be 8 candidate pairs, 4 for audio and 4  
> for video."
>    If an offer or answer can have candidates with different  transport 
> protocols
>    (not sure if this is allowed -- I asked this question in my last  
> message),
>    then this assumes all candidates have the same transport protocol.

For ice alone, yes its all UDP.

> 
> -       "Returning to the previous example, for each of the 8  candidate 
> pairs,
>          there would be two transport address pairs - one for RTP,  and 
> one for
>          RTCP.  If one candidate has more components than the other,  those
>          extra components will not be part of a transport address  pair, 
> won't
>          be validated, and will effectively be treated as if they  weren't
>          included in the candidate pair in the first place."
>    The first sentence seems to assume that the audio and video  streams 
> will use RTCP,
>    and so both ends offered two components in each candidate.
>    The second sentence then confuses things further -- is this  supposed 
> to be a continuation
>    of the example, or a normative statement?

normative. Its been moved with the rest of the normative text, separate 
from the example as you suggested.

> 
> Section 7.6:
> 
> -       "The state machine has six states - waiting, testing, Recv- 
> Valid, Send-Valid, Valid and Invalid."
>     I think  "waiting" and "testing" should be capitalized.

fixed

> 
> - Immediately after the state transition diagram, I suggest giving a  
> brief description
>   of the meaning of each state.
>   Though there are some descriptions later on, I think it would be  nice 
> to have the descriptions
>   complete and all together in one place

ok.

> 
> -  The notation in the state diagram indicates that the state machine  
> moves from Waiting to Testing
>    when timer Ta expires. However, this is true only if the state  
> machine is the next in line to start testing.

right. changed it to the "selected" event.


> 
> -      "... captures the progress of connectivity checks."
>    Grammar: Insert a "the" before "connectivity"?

ok

> 
> -         "This is done by  computing the matching transport address  
> pair for each Binding
>             Request.  This is done by examining the USERNAME of the  
> incoming  Binding Request. "
>    Suggest rewording these sentences along the following lines:
>          "This is done by determining the matching transport address  
> pair for each incoming STUN message.
>           For an incoming Binding Request message, this is done by  ...
>           For an incoming response message, this is done by ...

fixed up.

> 
> 
> -        "Extensions to ICE that describe other transport protocols  SHOULD
>            describe the state machine and the procedures for  
> connectivity checks."
>     To be clearer and more precise, perhaps reword as follows?
>          "Extensions to ICE that describe other transport protocols  SHOULD
>           describe the state machine and procedures for those  protocols."

I think the original wording is fine, and consistent with how this 
statement is made throughout the rest of the document.

> 
> -     "... in Figure 5"
>    Missing period at end of sentence.
> 

fixed.

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 Fri Jun 23 04:27:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fth17-0001fj-Bd; Fri, 23 Jun 2006 04:27:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fth16-0001fe-20
	for mmusic@ietf.org; Fri, 23 Jun 2006 04:27:52 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fth14-0000uN-Pk
	for mmusic@ietf.org; Fri, 23 Jun 2006 04:27:52 -0400
Received: from rtp-core-2.cisco.com ([64.102.124.13])
	by rtp-iport-2.cisco.com with ESMTP; 23 Jun 2006 04:27:50 -0400
X-IronPort-AV: i="4.06,168,1149480000"; 
	d="scan'208"; a="90847949:sNHT29816648"
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 k5N8Rono026353; 
	Fri, 23 Jun 2006 04:27:50 -0400 (EDT)
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.211);
	Fri, 23 Jun 2006 04:27:50 -0400
Received: from [192.168.1.101] ([10.86.240.32]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 23 Jun 2006 04:27:49 -0400
Message-ID: <449BA605.8000906@cisco.com>
Date: Fri, 23 Jun 2006 04:27:49 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Anzile, Christophe" <christophe.anzile@hp.com>
Subject: Re: [MMUSIC] ICE grammar and examples mismatch
References: <29160BFA3AC1A84E877783464A99A2720159F6D7@IDAEXC04.emea.cpqcorp.net>
In-Reply-To: <29160BFA3AC1A84E877783464A99A2720159F6D7@IDAEXC04.emea.cpqcorp.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Jun 2006 08:27:50.0014 (UTC)
	FILETIME=[E9EB29E0:01C6969E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
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

Yes, this has been pointed out by others and I have already fixed it.

Thanks,
Jonathan R.

Anzile, Christophe wrote:

> Hi all,
> 
> according
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-ice-08.txt grammar
> in chapter 12,
> 
> candidate-attribute   = "candidate" ":" candidate-id SP ...
> 
> however, all examples in chapter 11 do not use the ":" after candidate
> keyword.
> 
> Example:
> a=candidate $L1 1 UDP 1.0 $L-PRIV-1.IP $L-PRIV-1.PORT
> should be:
> a=candidate:$L1 1 UDP 1.0 $L-PRIV-1.IP $L-PRIV-1.PORT
> 
> Please correct all the examples in order to conform to the standard SDP
> syntax.
> 
> Christophe.
> 
> _______________________________________________
> 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 Fri Jun 23 12:02:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fto7D-0003mn-07; Fri, 23 Jun 2006 12:02:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fto7B-0003mi-Cj
	for mmusic@ietf.org; Fri, 23 Jun 2006 12:02:37 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fto79-0006tq-Md
	for mmusic@ietf.org; Fri, 23 Jun 2006 12:02:37 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [MMUSIC] Protocol Action: 'SDP: Session Description
	Protocol'-resolution declaration for video stream
Date: Fri, 23 Jun 2006 19:02:34 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C03A3A989@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] Protocol Action: 'SDP: Session Description
	Protocol'-resolution declaration for video stream
Thread-Index: AcaWOcwyB0u3Q+lsQDqhG/ZstAqpwAAo4BoQ
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Alan Bergmin" <alan.bergmin@yahoo.com>,
	<mmusic@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 3b3709b7fb3320c78bd7b1555081f0fc
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>
Content-Type: multipart/mixed; boundary="===============1289677575=="
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1289677575==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C696DE.70706527"

This is a multi-part message in MIME format.

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

Hi,

Those parameters are defined are defined in the codec parameters. It is =
in H.261 and H.263; note that for H.261 it is only QCIF and CIF while =
H.263 has more defined resolutions as well as custom resolutions.=20

H.264 is slice based codec and not based on a specific resolution, this =
enables the creation of different geometries. The decoder must be able =
to scale the received picture to display.

Note that the resolution parameters in SDP are more for the receive =
capability and are not applicable to RTSP.=20

Roni Even

=20

=20

________________________________

From: Alan Bergmin [mailto:alan.bergmin@yahoo.com]=20
Sent: Thursday, June 22, 2006 11:24 PM
To: mmusic@ietf.org
Subject: RE: [MMUSIC] Protocol Action: 'SDP: Session Description =
Protocol'-resolution declaration for video stream

=20

I have a similar remark: when I read the draft =
draft-shacham-sipping-session-mobility-02 (section 6.2), I think it =
would be nice for some applications to be able to advertize in the SDP =
the display size available (in pixels) on the terminal, not only for =
H.263 (as in draft-ietf-avt-rfc2429-bis-08.txt), but for every format. I =
understand that it would not always be possible to fully use the display =
capabilities of the terminal according to the different codecs but it =
can help in some cases of session mobility.

=20

> Hi, I'm looking for the resolution declaration for video

> stream in SDP. I didn't find anything standard for

> declaration of video resolution - like "CIF", "QCIF",...
> SHALL be it a part of the "a=3Dfmtp" line of SDP?=20

> Is it any other standard option exists?
> Best regards
>
> Osher

=20

=20

=20

 =20

________________________________

Yahoo! Messenger with Voice. =
<http://us.rd.yahoo.com/mail_us/taglines/postman3/*http:/us.rd.yahoo.com/=
evt=3D39666/*http:/messenger.yahoo.com>  PC-to-Phone calls for =
ridiculously low rates.


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

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

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Those parameters are defined are =
defined
in the codec parameters. It is in H.261 and H.263; note that for H.261 =
it is
only QCIF and CIF while H.263 has more defined resolutions as well as =
custom resolutions.
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>H.264 is slice based codec and not =
based
on a specific resolution, this enables the creation of different =
geometries. The
decoder must be able to scale the received picture to =
display.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Note that the resolution parameters =
in SDP
are more for the receive capability and are not applicable to RTSP. =
<o:p></o:p></span></font></p>

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

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

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

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

<div>

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

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

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

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Alan =
Bergmin
[mailto:alan.bergmin@yahoo.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, June 22, =
2006
11:24 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> mmusic@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [MMUSIC] =
Protocol
Action: 'SDP: Session Description Protocol'-resolution declaration for =
video
stream</span></font><o:p></o:p></p>

</div>

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

<div>

<p class=3DMsoNormal><font size=3D3 face=3DCourier><span =
style=3D'font-size:12.0pt;
font-family:Courier'>I have a similar remark: when I read the draft
draft-shacham-sipping-session-mobility-02 (section 6.2), I think it =
would be
nice for&nbsp;some applications to be able to&nbsp;advertize in the SDP =
the
display size available (in pixels) on the terminal, not only for H.263 =
(as in
draft-ietf-avt-rfc2429-bis-08.txt), but for every format. I understand =
that it
would not always be possible to fully use the display capabilities of =
the
terminal&nbsp;according to the&nbsp;different&nbsp;codecs but it can =
help in
some cases of session mobility.</span></font><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3DCourier><span =
style=3D'font-size:12.0pt;
font-family:Courier'>&gt; Hi, I'm looking for the resolution declaration =
for
video</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3DCourier><span =
style=3D'font-size:12.0pt;
font-family:Courier'>&gt; stream in SDP. I didn't find anything standard =
for</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3DCourier><span =
style=3D'font-size:12.0pt;
font-family:Courier'>&gt; declaration of video resolution -&nbsp;like
&quot;CIF&quot;, &quot;QCIF&quot;,...<br>
&gt; SHALL be it a part of the &quot;a=3Dfmtp&quot; line of SDP? =
</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3 =
face=3DCourier><span
style=3D'font-size:12.0pt;font-family:Courier'>&gt; Is it any other =
standard
option exists?<br>
&gt; Best regards<br>
&gt;<br>
&gt; Osher</span></font><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

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

</div>

<div>

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

</div>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>=A0 <o:p></o:p></span></font></p>

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

<hr size=3D1 width=3D"100%" align=3Dcenter>

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

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><a
href=3D"http://us.rd.yahoo.com/mail_us/taglines/postman3/*http:/us.rd.yah=
oo.com/evt=3D39666/*http:/messenger.yahoo.com">Yahoo!
Messenger with Voice.</a> PC-to-Phone calls for ridiculously low =
rates.<o:p></o:p></span></font></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C696DE.70706527--


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

--===============1289677575==--




From mmusic-bounces@ietf.org Fri Jun 23 12:06:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtoBG-0007LL-Lq; Fri, 23 Jun 2006 12:06:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtoBF-0007LG-IT
	for mmusic@ietf.org; Fri, 23 Jun 2006 12:06:49 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtoBD-0007EH-TC
	for mmusic@ietf.org; Fri, 23 Jun 2006 12:06:49 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [MMUSIC] Protocol Action: 'SDP: Session Description
	Protocol'-resolution declaration for video stream
Date: Fri, 23 Jun 2006 19:05:45 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C03A3A98B@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] Protocol Action: 'SDP: Session Description
	Protocol'-resolution declaration for video stream
Thread-Index: AcaWOcwyB0u3Q+lsQDqhG/ZstAqpwAApMELw
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Alan Bergmin" <alan.bergmin@yahoo.com>,
	<mmusic@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4bb0e9e1ca9d18125bc841b2d8d77e24
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>
Content-Type: multipart/mixed; boundary="===============1417242636=="
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1417242636==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C696DE.E3A39FD3"

This is a multi-part message in MIME format.

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

Alan,

If you are talking about the physical display resolution (different from =
the stream resolution) in order to show advertise if it is an HD display =
to the encoder this is something which is relevant to H.264 and not to =
H.261.

Roni Even

=20

________________________________

From: Alan Bergmin [mailto:alan.bergmin@yahoo.com]=20
Sent: Thursday, June 22, 2006 11:24 PM
To: mmusic@ietf.org
Subject: RE: [MMUSIC] Protocol Action: 'SDP: Session Description =
Protocol'-resolution declaration for video stream

=20

I have a similar remark: when I read the draft =
draft-shacham-sipping-session-mobility-02 (section 6.2), I think it =
would be nice for some applications to be able to advertize in the SDP =
the display size available (in pixels) on the terminal, not only for =
H.263 (as in draft-ietf-avt-rfc2429-bis-08.txt), but for every format. I =
understand that it would not always be possible to fully use the display =
capabilities of the terminal according to the different codecs but it =
can help in some cases of session mobility.

=20

> Hi, I'm looking for the resolution declaration for video

> stream in SDP. I didn't find anything standard for

> declaration of video resolution - like "CIF", "QCIF",...
> SHALL be it a part of the "a=3Dfmtp" line of SDP?=20

> Is it any other standard option exists?
> Best regards
>
> Osher

=20

=20

=20

 =20

________________________________

Yahoo! Messenger with Voice. =
<http://us.rd.yahoo.com/mail_us/taglines/postman3/*http:/us.rd.yahoo.com/=
evt=3D39666/*http:/messenger.yahoo.com>  PC-to-Phone calls for =
ridiculously low rates.


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

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

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>If you are talking about the =
physical display
resolution (different from the stream resolution) in order to show =
advertise if
it is an HD display to the encoder this is something which is relevant =
to H.264
and not to H.261.<o:p></o:p></span></font></p>

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

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

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

<div>

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

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

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

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Alan =
Bergmin
[mailto:alan.bergmin@yahoo.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, June 22, =
2006
11:24 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> mmusic@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [MMUSIC] =
Protocol
Action: 'SDP: Session Description Protocol'-resolution declaration for =
video
stream</span></font><o:p></o:p></p>

</div>

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

<div>

<p class=3DMsoNormal><font size=3D3 face=3DCourier><span =
style=3D'font-size:12.0pt;
font-family:Courier'>I have a similar remark: when I read the draft
draft-shacham-sipping-session-mobility-02 (section 6.2), I think it =
would be
nice for&nbsp;some applications to be able to&nbsp;advertize in the SDP =
the
display size available (in pixels) on the terminal, not only for H.263 =
(as in
draft-ietf-avt-rfc2429-bis-08.txt), but for every format. I understand =
that it
would not always be possible to fully use the display capabilities of =
the
terminal&nbsp;according to the&nbsp;different&nbsp;codecs but it can =
help in
some cases of session mobility.</span></font><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3DCourier><span =
style=3D'font-size:12.0pt;
font-family:Courier'>&gt; Hi, I'm looking for the resolution declaration =
for
video</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3DCourier><span =
style=3D'font-size:12.0pt;
font-family:Courier'>&gt; stream in SDP. I didn't find anything standard =
for</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3DCourier><span =
style=3D'font-size:12.0pt;
font-family:Courier'>&gt; declaration of video resolution -&nbsp;like
&quot;CIF&quot;, &quot;QCIF&quot;,...<br>
&gt; SHALL be it a part of the &quot;a=3Dfmtp&quot; line of SDP? =
</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3 =
face=3DCourier><span
style=3D'font-size:12.0pt;font-family:Courier'>&gt; Is it any other =
standard
option exists?<br>
&gt; Best regards<br>
&gt;<br>
&gt; Osher</span></font><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

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

</div>

<div>

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

</div>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>=A0 <o:p></o:p></span></font></p>

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

<hr size=3D1 width=3D"100%" align=3Dcenter>

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

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><a
href=3D"http://us.rd.yahoo.com/mail_us/taglines/postman3/*http:/us.rd.yah=
oo.com/evt=3D39666/*http:/messenger.yahoo.com">Yahoo!
Messenger with Voice.</a> PC-to-Phone calls for ridiculously low =
rates.<o:p></o:p></span></font></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C696DE.E3A39FD3--


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

--===============1417242636==--




From mmusic-bounces@ietf.org Fri Jun 23 12:09:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtoDO-0007ut-1q; Fri, 23 Jun 2006 12:09:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtoDM-0007uW-LH
	for mmusic@ietf.org; Fri, 23 Jun 2006 12:09:00 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtoDK-0007IM-Nb
	for mmusic@ietf.org; Fri, 23 Jun 2006 12:09:00 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [MMUSIC] Protocol Action: 'SDP:
	SessionDescriptionProtocol'-resolution declaration for video stream
Date: Fri, 23 Jun 2006 19:08:57 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C03A3A98D@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] Protocol Action: 'SDP:
	SessionDescriptionProtocol'-resolution declaration for video
	stream
Thread-Index: AcaWOdLDrMKpR+aCQqqjxaXVNQvK3wAAavZgAAoaa4AABzcUgAAXlpdA
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Chris Steck" <csteck@real.com>,
	"Kylin Wei" <weiqikun@huawei.com>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: c52a6b2685a9a1f963a24bd74e30b072
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="===============0527470664=="
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0527470664==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C696DF.570BC1DB"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C696DF.570BC1DB
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Maybe this discussion should be on the AVT list. We have been thinking
about this parameter. It make sense for point to point calls but is a
bit difficult ofr multipoint calls or streaming applications.

Roni Even

=20

________________________________

From: Chris Steck [mailto:csteck@real.com]=20
Sent: Friday, June 23, 2006 7:53 AM
To: 'Kylin Wei'
Cc: mmusic@ietf.org
Subject: RE: [MMUSIC] Protocol Action: 'SDP:
SessionDescriptionProtocol'-resolution declaration for video stream

=20

Right.  My question was has there been thought around leveraging the
UAProf formally as part of SDP rfc?

=20

-Chris=20

=20

	=20

=09
________________________________


	From: Kylin Wei [mailto:weiqikun@huawei.com]=20
	Sent: Thursday, June 22, 2006 6:39 PM
	To: 'Chris Steck'
	Cc: 'Alan Bergmin'; mmusic@ietf.org
	Subject: RE: [MMUSIC] Protocol Action: 'SDP: Session
DescriptionProtocol'-resolution declaration for video stream

	=20

	Chris Steck wrote:

	>In a related veign, has any thought been given to formally
employing UAProf for this purpose, as is done in 3GPP PSS?

	=20

	=20

	In 3GPP PSS (TS 26.234) UAProf is used to indicate the
capabilities of the terminal.

	For example, the "ScreenSize" attribute states the screen size
in pixels.

	Kylin Wei=20


------_=_NextPart_001_01C696DF.570BC1DB
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimHei;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"\@SimHei";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
h1
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:21.6pt;
	text-align:justify;
	text-indent:-21.6pt;
	page-break-after:avoid;
	mso-list:l1 level1 lfo2;
	font-size:16.0pt;
	font-family:Arial;
	font-weight:bold;}
h2
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:28.8pt;
	text-align:justify;
	text-indent:-28.8pt;
	page-break-after:avoid;
	mso-list:l1 level2 lfo2;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:normal;}
h3
	{margin-top:13.0pt;
	margin-right:0cm;
	margin-bottom:13.0pt;
	margin-left:36.0pt;
	text-align:justify;
	text-indent:-36.0pt;
	line-height:171%;
	page-break-after:avoid;
	mso-list:l1 level3 lfo2;
	font-size:12.0pt;
	font-family:"Times New Roman";
	font-weight:normal;}
p.MsoHeader, li.MsoHeader, div.MsoHeader
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	layout-grid-mode:char;
	font-size:9.0pt;
	font-family:Arial;}
p.MsoFooter, li.MsoFooter, div.MsoFooter
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:Arial;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.a, li.a, div.a
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:217.8pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:1.0gd;
	mso-para-margin-right:0cm;
	mso-para-margin-bottom:0cm;
	mso-para-margin-left:217.8pt;
	mso-para-margin-bottom:.0001pt;
	text-align:center;
	text-indent:-18.45pt;
	mso-list:l0 level9 lfo4;
	font-size:9.0pt;
	font-family:Arial;}
p.a0, li.a0, div.a0
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Arial;}
p.a1, li.a1, div.a1
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:center;
	font-size:10.5pt;
	font-family:Arial;
	font-weight:bold;}
p.a2, li.a2, div.a2
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:217.8pt;
	margin-bottom:.0001pt;
	text-align:center;
	text-indent:-18.45pt;
	mso-list:l0 level8 lfo4;
	font-size:9.0pt;
	font-family:Arial;}
p.a3, li.a3, div.a3
	{margin-top:4.0pt;
	margin-right:0cm;
	margin-bottom:4.0pt;
	margin-left:0cm;
	text-align:center;
	page-break-after:avoid;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.a4, li.a4, div.a4
	{margin-top:15.0pt;
	margin-right:0cm;
	margin-bottom:15.0pt;
	margin-left:0cm;
	text-align:center;
	font-size:18.0pt;
	font-family:Arial;}
p.a5, li.a5, div.a5
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.a6, li.a6, div.a6
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:9.0pt;
	font-family:Arial;}
p.a7, li.a7, div.a7
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-indent:18.0pt;
	font-size:9.0pt;
	font-family:Arial;}
p.a8, li.a8, div.a8
	{margin:0cm;
	margin-bottom:.0001pt;
	text-indent:21.0pt;
	font-size:12.0pt;
	font-family:Arial;
	color:blue;
	font-style:italic;}
span.a9
	{font-family:SimSun;
	color:black;
	font-weight:bold;}
span.aa
	{font-family:SimSun;
	color:black;
	font-weight:bold;}
span.EmailStyle32
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle33
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:65.6pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1123964682;
	mso-list-template-ids:301907670;}
@list l0:level1
	{mso-level-suffix:none;
	mso-level-text:"%1  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:18.0pt;
	mso-bidi-font-size:18.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level2
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:15.0pt;
	mso-bidi-font-size:15.0pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level3
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:12.0pt;
	mso-bidi-font-size:12.0pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level4
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3\.%4  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level5
	{mso-level-tab-stop:2.0cm;
	mso-level-number-position:left;
	margin-left:2.0cm;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level6
	{mso-level-text:"%6\)";
	mso-level-tab-stop:2.0cm;
	mso-level-number-position:left;
	margin-left:2.0cm;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level7
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:2.0cm;
	mso-level-number-position:left;
	margin-left:2.0cm;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level8
	{mso-level-reset-level:level1;
	mso-level-suffix:space;
	mso-level-text:\56FE%8;
	mso-level-tab-stop:none;
	mso-level-number-position:center;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l0:level9
	{mso-level-reset-level:level1;
	mso-level-suffix:space;
	mso-level-text:\8868%9;
	mso-level-tab-stop:none;
	mso-level-number-position:center;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l1
	{mso-list-id:1666475049;
	mso-list-template-ids:-28945502;}
@list l1:level1
	{mso-level-text:%1;
	mso-level-tab-stop:21.6pt;
	mso-level-number-position:left;
	margin-left:21.6pt;
	text-indent:-21.6pt;}
@list l1:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:28.8pt;
	mso-level-number-position:left;
	margin-left:28.8pt;
	text-indent:-28.8pt;}
@list l1:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	margin-left:36.0pt;
	text-indent:-36.0pt;}
@list l1:level4
	{mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l1:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l1:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l1:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l1:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	margin-left:72.0pt;
	text-indent:-72.0pt;}
@list l1:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:79.2pt;
	mso-level-number-position:left;
	margin-left:79.2pt;
	text-indent:-79.2pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"2" />
  <o:regrouptable v:ext=3D"edit">
   <o:entry new=3D"1" old=3D"0" />
   <o:entry new=3D"1" old=3D"0" />
  </o:regrouptable>
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Maybe this discussion should be on =
the AVT
list. We have been thinking about this parameter. It make sense for =
point to
point calls but is a bit difficult ofr multipoint calls or streaming
applications.<o:p></o:p></span></font></p>

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

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

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

<div>

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

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

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

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Chris =
Steck
[mailto:csteck@real.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, June 23, =
2006 7:53
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Kylin Wei'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> mmusic@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [MMUSIC] =
Protocol
Action: 'SDP: SessionDescriptionProtocol'-resolution declaration for =
video
stream</span></font><o:p></o:p></p>

</div>

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

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DVerdana><span =
style=3D'font-size:
10.0pt;font-family:Verdana;color:blue'>Right.&nbsp; My question was has =
there
been thought around leveraging the UAProf&nbsp;formally as part of SDP =
rfc?</span></font><o:p></o:p></p>

<div>

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

</div>

<p><b><i><font size=3D3 color=3Dblack face=3DVerdana><span =
style=3D'font-size:12.0pt;
font-family:Verdana;color:black;font-weight:bold;font-style:italic'><!-- =
Converted from text/rtf format -->-</span></font></i></b><i><font
size=3D4 color=3Dblack face=3DArial><span =
style=3D'font-size:13.5pt;font-family:Arial;
color:black;font-style:italic'>Chris</span></font></i> <o:p></o:p></p>

<div>

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

</div>

<blockquote =
style=3D'margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt'>

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

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

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

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

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> Kylin Wei
[mailto:weiqikun@huawei.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, June 22, =
2006 6:39
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Chris Steck'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> 'Alan Bergmin';
mmusic@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [MMUSIC] =
Protocol
Action: 'SDP: Session DescriptionProtocol'-resolution declaration for =
video
stream</span></font><o:p></o:p></p>

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

<p class=3DMsoNormal><font size=3D1 face=3DArial><span =
style=3D'font-size:9.0pt;
font-family:Arial'>Chris Steck wrote:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DVerdana><span =
style=3D'font-size:
10.0pt;font-family:Verdana;color:blue'>&gt;In a related veign, has any =
thought
been given to formally employing UAProf for this purpose, as is done in =
3GPP
PSS?</span></font><o:p></o:p></p>

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

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

<p class=3DMsoNormal><font size=3D1 face=3DArial><span =
style=3D'font-size:9.0pt;
font-family:Arial'>In 3GPP PSS (TS 26.234) UAProf is used to indicate =
the
capabilities of the terminal.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span =
style=3D'font-size:9.0pt;
font-family:Arial'>For example,</span></font> <font size=3D1 =
face=3DArial><span
style=3D'font-size:9.0pt;font-family:Arial'>the &#8220;ScreenSize&#8221;
attribute states the screen size in pixels.<o:p></o:p></span></font></p>

<div>

<p><font size=3D2 color=3Dnavy face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:navy'>Kylin Wei </span></font><o:p></o:p></p>

</div>

</blockquote>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C696DF.570BC1DB--


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

--===============0527470664==--




From mmusic-bounces@ietf.org Fri Jun 23 12:58:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ftozd-00054t-El; Fri, 23 Jun 2006 12:58:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ftozb-00054n-Pd
	for mmusic@ietf.org; Fri, 23 Jun 2006 12:58:51 -0400
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ftozb-0004A5-Gb
	for mmusic@ietf.org; Fri, 23 Jun 2006 12:58:51 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Fri, 23 Jun 2006 12:59:43 -0400
To: mmusic@ietf.org
References: <4499AB3D.8060103@cisco.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Fri, 23 Jun 2006 12:58:49 -0400
In-Reply-To: <4499AB3D.8060103@cisco.com> (Flemming Andreasen's message of
	"Wed, 21 Jun 2006 16:25:33 -0400")
Message-ID: <ybur71fizau.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 23 Jun 2006 16:59:43.0913 (UTC)
	FILETIME=[6CD43990:01C696E6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: Flemming Andreasen <fandreas@cisco.com>, ietf-rtpsec <ietf-rtpsec@imc.org>,
	Doug Perham <dperham@wgate.com>
Subject: [MMUSIC] Re: SDP Capability Negotiation to address multiple RTP
 profiles and other issues
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

>I have submitted a draft on adding capability negotiation to SDP which you
>can retrieve from (abstract below):
>
>http://www.ietf.org/internet-drafts/draft-andreasen-mmusic-sdp-capability-negotiation-00.txt
>
>The primary motivation for this is to address the proliferation of RTP
>profiles and the associated problem of negotiating which of possibly
>several supported RTP profiles to use for a given media stream.
...
>Feedback is hereby solicited. In particular, it would be very helpful if
>people could take a look at the requirements and see if they agree with
>them (too much, too little, anything wrong/missing, etc.) before we get
>into detailed discussion around the proposed solution. Having said that,
>all comments are welcome.

REQ-10: there are other ways to deal with the example issue, especially
involving re-INVITE in SIP - though re-negotiation may not be possible in
some uses of SDP.  You may want to mention here or better in the Existing
Work section how re-INVITE/re-negotiation fit in (which applies to a lot of
the requirements, not just this one).

REQ-110: (ability to receive media immediately) and REQ-120 - see below.
These two seem redundant.

Overall, I find it interesting, if complex.  There is a major issue (see
below) to resolve.  The complexity may be such that getting interoperable
implementations may be a challenge.  An effective test suite and set of
examples will be critical.  The problem is a very real one.

It appears to not deal with two issues dealt with by the grouping spec,
which are defining valid combinations of media lines, and defining valid
combinations of codecs (on one media line or between lines).  This would
mean that those particular requirements would still need grouping or SDPng
or ???.  Perhaps at least the first (valid combinations of media lines)
can be worked into this approach?  As you mention, grouping (and even more
so multipart-alternative) have significant compatibility issues.


General issue with the approach:

It's dependant on the offerer receiving the answer in order to decode the
media.  For example, if the transport protocol can be RTP/AVP or RTP/SAVP
(regardless of which is the "actual" offer and which is potential), how
does the receiver process incoming media packets if it hasn't seen the
answer?  Especially if the packet types can't be intuited from something
like size (an example would be SRTP with encryption but no auth tag).  In
some cases this would cause static, could cause potential crashing or
problematic actions.  So the answerer may not be able to send media until
they see ACK (in SIP) if they accept a potential configuration.

This can cause clipping - you pick up the phone and start talking, but if
the answer is lost or delayed, or if the ACK is lost or delayed, your
"hello?" might be lost.

Now, this might be ok, though clipping is to be avoided where possible,
since people assume through experience that media channels are open as soon
as they answer.  Also, if the configuration accepted is the actual one,
the answerer can send media immediately.


Potential solutions:
a) Use different transport addresses for incompatible media/protocols.
   Could be problematic when combined with ICE/TURN/etc - more ports.
   Could cause some combinatoric expansion (especially with ICE/TURN).
b) Use alternative payload types to distinguish incompatible media types
   so that some level of decoding (or at least knowing to ignore packets) 
   can be done before the answer arrives.  This might tell the offerer
   enough to fully decode, though they still can't send until they get
   the answer (which is normal).  It may not tell enough in all cases
   without expansion, and perhaps there are backwards compatibility
   issues.  Also, there may be issues with the number of payload types
   listed (though perhaps the values could be inferred instead of
   explicit) and how that affects the size of the offer.

Discussion of clipping, when and how media is sent, and how packet
loss/delay affect this will be critical.

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


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



From mmusic-bounces@ietf.org Fri Jun 23 13:20:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtpKd-0004Zh-Nc; Fri, 23 Jun 2006 13:20:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtpKc-0004ZX-Cw
	for mmusic@ietf.org; Fri, 23 Jun 2006 13:20:34 -0400
Received: from mx2-1.spamtrap.magma.ca ([209.217.78.160])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtpKb-00072y-2I
	for mmusic@ietf.org; Fri, 23 Jun 2006 13:20:34 -0400
Received: from mail2.magma.ca (mail2.internal.magma.ca [10.0.10.12])
	by mx2-1.spamtrap.magma.ca (8.13.1/8.13.1) with ESMTP id k5NHKVNF004981;
	Fri, 23 Jun 2006 13:20:31 -0400
Received: from [10.1.5.219] ([216.13.42.126]) (authenticated bits=0)
	by mail2.magma.ca (Magma's Mail Server) with ESMTP id k5NHKTCM022810
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
	Fri, 23 Jun 2006 13:20:31 -0400
In-Reply-To: <4498BB18.8090603@cisco.com>
References: <4887547D-99F4-4F15-B36A-4A03C16B7BE2@magma.ca>
	<4498BB18.8090603@cisco.com>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <7C8CAC9A-9FFC-45F2-B4E4-86DDB6C0B7F6@magma.ca>
Content-Transfer-Encoding: 7bit
From: Philip Matthews <philip_matthews@magma.ca>
Date: Fri, 23 Jun 2006 13:20:29 -0400
To: Jonathan Rosenberg <jdrosen@cisco.com>
X-Mailer: Apple Mail (2.746.2)
X-magma-MailScanner-Information: Magma Mailscanner Service
X-magma-MailScanner: Clean
X-Spam-Status: 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: mmusic@ietf.org
Subject: [MMUSIC] Re: Some more questions and comments on
	draft-ietf-mmusic-ice-08
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

Jonathan:

Thanks for your reply.
I am quite happy with most of what you said.
Comments on a couple of points below.

- Philip


On 20-Jun-06, at 23:20 , Jonathan Rosenberg wrote:
>
> Philip Matthews wrote:
>
>> Jonathan:
>> A few questions about the specification:
>> 1)  Can a single offer contain candidates for the same media  
>> stream  that use different transport protocols??
>>      The spec seems to handle this case, but I could not find a   
>> statement that this is allowed.
>
> Its not allowed in base ICE, which is specific to UDP. But ice-tcp  
> allows it, and that is explained there in more detail.

This doesn't seem right to me.
In my opinion, draft-ietf-mmusic-ice is both the base specification  
for ICE and the specification that
defines the rules for UDP. In this regard, the general rules for  
mixing candidates with different transport protocols
belong in draft-ietf-mmusic-ice, and not in some extension document.
So why do you think they belong in ice-tcp instead?


[---SNIP---]



Regarding the following three exchanges:
>
>> Section 12:
>> - The rules DIGIT and SP are never defined.
>
> They are defined in RFC 4234, which is referenced prior to the BNF  
> as the source of the rules.

... and ...

>
>>   where ALPHA is also defined in section 9 of draft-ietf-mmusic- 
>> sdp- new.
>
> ALPHA is also defined in RFC 4234.

... and ...

>
>> -  The rule "token" is never defined.
>>    Presumably you mean "token" as defined in section 9 of draft- 
>> ietf- mmusic-sdp-new?
>
> no, from rfc 3261. The text below says that token is from rfc3261  
> but its not in the comments. I added a comment in the grammar.

Personally, I think that taking these rules from documents other than  
draft-ietf-mmusic-sdp-new is wrong.
ICE is an SDP extension, so it is bound by the rules of SDP.
Though it may not have an impact on the actual grammar, I think it is  
much clearer to the reader if it was
stated than the grammar of section 12 is just an extension of the  
grammar given in draft-ietf-mmusic-sdp-new
and that any rules not defined in the ICE document are defined there.



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



From mmusic-bounces@ietf.org Fri Jun 23 13:39:30 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ftpcm-00033R-46; Fri, 23 Jun 2006 13:39:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ftpck-0002zL-OJ
	for mmusic@ietf.org; Fri, 23 Jun 2006 13:39:18 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ftpcj-0007nt-1M
	for mmusic@ietf.org; Fri, 23 Jun 2006 13:39:18 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12])
	by rtp-iport-2.cisco.com with ESMTP; 23 Jun 2006 13:39:17 -0400
X-IronPort-AV: i="4.06,169,1149480000"; 
	d="scan'208"; a="90883768:sNHT37052272"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k5NHdGYL008833; 
	Fri, 23 Jun 2006 13:39:16 -0400 (EDT)
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.211);
	Fri, 23 Jun 2006 13:39:16 -0400
Received: from [192.168.1.101] ([10.86.240.32]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 23 Jun 2006 13:39:16 -0400
Message-ID: <449C2743.2050002@cisco.com>
Date: Fri, 23 Jun 2006 13:39:15 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <558A4552-361E-44EB-A4BA-B18D894CFD5D@magma.ca>
In-Reply-To: <558A4552-361E-44EB-A4BA-B18D894CFD5D@magma.ca>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Jun 2006 17:39:16.0237 (UTC)
	FILETIME=[F2D823D0:01C696EB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a9ddb14fac983e71b59f23b52a45b4e
Cc: mmusic@ietf.org
Subject: [MMUSIC] Re: Part 4 of questions/comments on
	draft-ietf-mmusic-ice-08
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.

Philip Matthews wrote:

> Jonathan:
> 
> Here are some more comments and questions about this draft.
> Hope they help.
> These are probably the last comments I will have time to send before
> the WGLC closes.
> 
> 
> And, BTW, it is clear that you have put a HUGE effort into this work.
> Many thanks for all this!!
> I think this stuff we be very useful.
> 
> - Philip
> 
> 
> Technical questions and comments
> ============================
> 
> 1) Perhaps I am just dense, but I am finding it difficult to  determine 
> which portions of
>     the procedures specified in the new STUN draft (draft-ietf- 
> behave-rfc3489bis-03)
>     actually apply when ICE is used. When I sat down to try to write  
> some pseudo-code
>     to handle the receipt of a STUN request, I found I had to weave  
> back and forth
>     between the two documents and take some guesses as to which  
> paragraphs in
>     rfc3489bis to ignore. For example, section 9.1.1 of rfc3489bis  says 
> that a server
>     should include a NONCE attribute in certain error responses, but  I 
> am guessing
>     that statement does not apply for ICE.
>     Would it be possible to give somewhere, perhaps in an appendix,  an 
> integrated
>     description of the STUN procedures for ICE (that is, an  integration 
> of the procedures
>     specified in rfc3489bis, plus sections 7.7 and 7.8 for sending  and 
> receiving STUN requests
>     for ordinary candidates, and sections 7.10.1 and 7.10.2 for  sending 
> and receiving
>     STUN requests for peer-reflexive candidates)?

I don't want to repeat whats in rfc3489bis. The version of rfc3489bis 
you are reading is the first revision that defines the connectivity 
usage, and it will take another rev (which is next after I finish ICE) 
to get it better aligned. THe theory goes that you would read rfc3489bis 
and the connectivity usage and it would be clear that you would be using 
all of it.

> 
> 
> 2) In section 7.10.1, the document says
>         The comparison of the source IP and port of the Binding  Request 
> and
>         the IP address and port of the remote transport address in the
>         matching transport address pair may indicate inequality.  In  that
>         case, the source IP and port of the Binding Request (and  again, 
> for
>         relayed transport address, this refers to the source IP  address 
> and
>         port of the packet when it arrived at the relay) are  compared 
> to the
>         IP address and ports across the transport address pairs in  *all*
>         remote candidates.
>    When you say "*all*" here, do you mean all candidates for the  same 
> media stream
>    which have the same transport protocol?

Same media stream and transport protocol. Will clarify.

> 
> 
> 3)  In section 7.10.1, the document talks about passing a "Get Req"  
> event to the state machine
>     of the (local candidate, peer-reflexive candidate) pair.
>     Is this in addition to the event passed to the state machine of  the 
> (local candidate, generating candidate) pair,
>     or instead of?  The last paragraph of section 7.10 suggests that  
> this is in addition to,
>     but it is not clear to me why the state machine for (local  
> candidate, generating candidate) should get this event.

Good question. I have revised the state machine to allow for the 
optimizatiosn you have suggested in your draft. In doing so, the text is 
now clear on this. A "miss" event gets fed into the state machine for 
(local,generating), which moves it instantly to invalid.

> 
> 4)  In section 7.10.1, the document says
>       "The agent SHOULD select the candidate
>         pair corresponding to the combination of the alternate remote
>         candidate and the native candidate from the original matching
>         candidate pair."
>     When you say SHOULD here, do you mean that the agent might  select a 
> different candidate pair,
>     or that the agent might elect not to send the "Get Req" to this  pair?
>     Would you explain why agent might choose to do something different?

This is a good point. SHOULDs are confusing to implementors, to be 
honest. Over time I have made an increasingly concerted effort to use 
them less, and when I use them, explain why its a SHOULD. ICE has far 
fewer SHOULDs, and this one in particular is out of place. Its basically 
a MUST. The description here is more concise now and this SHOULD is gone.

> 
> 5)  Is the timer described in section 7.13 "Sending Media" the same  as 
> the timer
>     for promoting a candidate to active (section 7.9)? The wording  used 
> is almost identical.

They're not identical, in fact, though very similar. The one in 7.9 is 
only used by offerers, the one in 7.13 for answerers. I'll clarify.


> 
> 6) In section 7.6, the document says
>           "If, while in the Testing state, the agent receives a  Binding 
> Request
>            matching that transport address pair, and this Binding  Request
>            generates a successful response, the transport address  pair 
> moves
>            into the Send-Valid state.  In addition, the agent  
> retransmits a
>            Binding Request for the transaction in progress."
>     How is this retransmission relate to the STUN client state  machine 
> for this address pair?

It doesn't impact the FSM in that section, if that is what you are 
asking. Its a forced retransmission, really, overriding the normal 
retransmit rules for STUN. I'll clarify that.


>     Section 7.1 of draft-ietf-behave-rfc3489bis-03 talks about  sending 
> a total of 9 requests
>     at exponentially increasing intervals. Does the above paragraph  
> mean that the retransmit
>     timer simply expires early? Or does this transmission have no  
> effect on the retransmit
>     timer and the retransmission count (thus potentially sending a  
> total of 10 requests)?

No effect, causing possibly 10 requests. I clarified that. THis is an 
optimization like so much of ICE; things will work without it, but ICE 
is faster if you do this.


> 
> 
> 
> Editorial comments
> ===============
> 
> Section 7.6:
> 
> -   Perhaps I am missing something, but aren't the names for the Send- 
> Valid and Recv-Valid states reversed?
>     That is:
>           - In Send-Valid, the local agent knows it can _receive_   on 
> that transport address pair
>           - In Recv-Valid, the local agent knows it can  _send_      on 
> that transport address pair

Its all a matter of perspective. Send-Valid also means that its peer can 
*send* to it. Per your other comment, I've added a sentence that 
describes each state and it expresses it in this way to make it clear.


> 
> -  Does an otherwise valid STUN request generate a success response  
> when received in any state?

yes.

>    As I stated in a previous message, I think it shouldn't in the  
> Invalid state, but whatever is decided,
>    perhaps a clear statement on this issue would be helpful?

I added a clear statement about this.

> 
> Section 7.7
> -     "ransport" should be "transport"?
> -     "reflesive" should be "reflexive"?
> -     "neccesarily" should be "necessarily"?
> -     "oferrer" should be "offerer"?

fixed. I'll do a full spell check before submitting the final rev.

> 
> 
> -    Specify processing of other error codes listed in draft-ietf- 
> behave-rfc3489bis?
>      Specifically: 300, 434, 435, 436, 437 are presumably all errors  
> because none of them are applicable
>      to this usage of STUN?

yes. rather than listing each response code I merely stated that its 
unrecoverable or inapplicable error responses.

> 
> -       " ... to launch DoS attacks Section 13.4.2"
>      Formatting:
>         "... to launch DoS attacks (see Section 13.4.2)."

fixed

> 
> -         "... contains a reflexive or relayed candidate derived from  a 
> local candidate with that local transport address."
>      This is true for any derived  candidate, not just reflexive or  
> relayed candidates.
>      Suggest  rewording as follows:
>               "... contains a  candidate derived from that local  
> transport address."

ok

> 
> -         "If the USERNAME was not valid, the agent generates a 430."
>    Do you perhaps mean 436 (Unknown Username) rather than 430 (Stale  
> Credentials)?

No - its 430. 436 was previously a turn-only error code, assocaited with 
digest authentication. We're not using digest here, so its not used.

>    Also, suggest changing "was" to "is" for consistency (in verb  tense) 
> with the surrounding sentences.
> 

done

> 
> Section 7.8:
> -    "The first is generation ..., and the second ICE-specific"
>       Suggest adding an "is" after "second" for consistency.

ok

> 
> -      "An agent will continue to receive periodic STUN connectivity  
> checks
>          on a local transport address as long as it had listed that  
> transport
>          address, or one derived from it, in an a=candidate  attribute 
> in its
>         most recent offer or answer, the state machine for that  transport
>         address is in the Recv-Valid or Valid states, and the transport
>         address is for UDP."
>     I think it is possible to continue to receive them even when the  
> local state machine
>     is in other states, for example, the Invalid state. See my  previous 
> message
>     on this subject.

Removed the bit about being state dependent.

> 
> 
> Section 7.9 "Promoting a Candidate to Active"
> 
> -  Since the retry interval for STUN is initially 100 milliseconds,  
> perhaps the default value for
>    timer Tws should be 120 milliseconds (rather than 100  milliseconds) 
> to allow time for a
>    retry to complete for the candidate pair that is two earlier in  the 
> check sequence?
>   Or perhaps even larger, if candidate pairs from different m/c  lines 
> are combined in a single
>   candidate pair check ordering.

I hadn't done much real analysis in coming up with this default. 
Considering it further, the problem actually goes away if the number of 
components is large. Say you have 20 components in a candidate pair, and 
you are trying all of the components in a higher priority pair before a 
lower one. Thus, 20*50ms after the LAST check on the higher priority 
candidate pair is the EARLIEST that a lower priority one can validate. 
Thats a full 1s after the completion of the last check for the higher 
priority one, enough for many retransmits.

So, if you want to allow for a single packet loss (the easier formula), 
you need:

Tws = max(0, 100ms + RTT - N*50ms)

where N is the number of components. Assuming a 100ms RTT and N=2 
actually gives you the 100ms figure, so my guesstimate seems OK ;)

The main thing though is you can decrease Tws to zero if you have lots 
of components, and thats worth adding. I'll add this formula in.


> 
> - Perhaps the document should specify some relationships that should  
> hold between the various timer intervals?

per above - done!

> 
> -     "When the agent behind such a NAT sends a Binding Request to  the 
> other agent (assuming it is reachable) ..."
>    For clarity, suggest replacing "it" by "the other agent".


> 
> 
> Section 7.10.1
> 
> -     " ... sees if a transport address with
>        that same component ID exists in the peer reflexive  candidate.  If
>        not (and it shouldn't),..."
>   There might be a remote transport address with the same tid if the
>   local agent had previously received a STUN Request for the same  
> USERNAME.

this has been fixed per another comment you made.

> 
> -      "   Newly created or not, the agent extracts the component ID  
> from the
>             matching transport address pair, and sees if a transport  
> address with
>             that same component ID exists in the peer reflexive  
> candidate.  If
>             not (and it shouldn't), the agent adds a transport  address 
> to the
>             peer reflexive candidate.  This transport address is  equal 
> to the
>             source IP address and port from the incoming STUN  Binding 
> Request
>            (and in the case of a relayed transport address, the one  
> seen by the
>            relay).  It is assigned the component ID equal to the  
> component ID in
>            the matching transport address pair.  This transport  address 
> will
>            have a tid, equal to the concatenation of the candidate  ID 
> for this
>            new candidate, and the component ID, separated by a colon."
>    Presumably, the transport protocol and qvalue of the peer  reflexive 
> candidate
>    are the same value as the corresponding values of the generating  
> candidate,
>    and the rules for setting the various optional (extension-attr-name,
>    extension-attr-value) pairs are specific to the transport protocol
>    (with none currently defined for UDP).

Correct on the transport protocol.
Q-value is derived from the candidate whose q-value processing is 
mentioned elsewhere.
I've specified rules for the three additional candidate attributes which 
are now defined in -09, and specified that extensiosn would need to 
define how other candidate attributes are inherited.

> 
> 
> 
> Section 7.11.1 Sending of a Subsequent Offer
> 
> -     "o  If the candidate in the m/c-line is valid, all other  candidates
>            SHOULD be removed.  This has the effect of stopping  
> connectivity
>            checks of other candidates.  This SHOULD would not be  
> followed if
>            an agent wanted to keep a candidate ready for usage  should, for
>            some reason, the active candidate later become invalid."
>    If the candidate in the m/c line is a low priority candidate  (e.g., 
> a STUN relay candidate)
>    and the connectivity checks for higher priority candidates have  not 
> yet finished,
>    then removing the other candidates would be bad.
>    This situation could occur if the subsequent offer was triggered  for 
> reasons
>    other than ICE processing.

Right. Added "lower priority" to this to fix it.

> 
> 
> Section 7.11.2  Receiving the Offer and Sending the Answer
> 
> -   When talking about removing candidate pairs, the spec says
>            "3.  If the agent receives a STUN Binding Request for  that 
> candidate
>                  pair, the agent SHOULD generate a 430 response."
>     The document currently states in section 7.8 that a STUN  response 
> is generated
>     based on just a prefix match on the USERNAME. The above sentence  seems
>     incompatible with this.
>     (I suggested in a previous message that the STUN Response should  be 
> based on an exact match
>     of the USERNAME, which would be consistent with this sentence).

Per my other note, I think the prefix match is needed. I've removed the 
bit about 430, and instead referenced the section on receiving stun 
requests. btw, if a candidate pair disappears its generally because a 
candidate disappeared, in which case the prefix match will in fact fail.



> 
> 
> 
> Section 8    Guidelines for Usage with  SIP
> 
> -       "Two latency of figures are of particular interest."
>     Perhaps you mean the following??
>           "Two latency values are of particular interest."

deleted extra 'of'

> 
> 
> Section 11.1
> -      "In this example, the NAT has the address and port independent  
> mapping property
>          and the address dependent permission property".
>     I believe the BEHAVE terminology is "endpoint-independent  mapping" and
>     "address-dependent filtering".

fixed.

> 
> - Is there is an error in the SDP for the first example?
>        v=0
>        o=jdoe 2890844526 2890842807 IN IP4 $L-PRIV-1.IP
>        s=
>        c=IN IP4 $STUN-PUB-1.IP
>        t=0 0
>        a=ice-pwd:$LPASS
>        m=audio $STUN-PUB-1.PORT RTP/AVP 0
>        a=rtpmap:0 PCMU/8000
>        a=candidate $L1 1 UDP 1.0 $L-PRIV-1.IP $L-PRIV-1.PORT
>        a=candidate $L2 1 UDP 0.7 $NAT-PUB-1.IP $NAT-PUB-1.PORT
>    Should the address and port in the m/c line be NAT-PUB-1.IP and  
> NAT-PUB-1.PORT?
> 

yes, this was pointed out by others also.

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 Fri Jun 23 14:30:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtqQK-0001HN-Vu; Fri, 23 Jun 2006 14:30:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtqQJ-0001HI-LZ
	for mmusic@ietf.org; Fri, 23 Jun 2006 14:30:31 -0400
Received: from mx3-2.spamtrap.magma.ca ([209.217.78.169])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtqQI-0002B6-9S
	for mmusic@ietf.org; Fri, 23 Jun 2006 14:30:31 -0400
Received: from mail1.magma.ca (mail1.internal.magma.ca [10.0.10.11])
	by mx3-2.spamtrap.magma.ca (8.13.0/8.13.1) with ESMTP id k5NIUSnu017295;
	Fri, 23 Jun 2006 14:30:28 -0400
Received: from [10.1.5.219] ([216.13.42.126]) (authenticated bits=0)
	by mail1.magma.ca (Magma's Mail Server) with ESMTP id k5NIUR6C019154
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT);
	Fri, 23 Jun 2006 14:30:28 -0400
In-Reply-To: <5EB80D22825EEE42872083AD5BFFB594017F1166@esealmw113.eemea.ericsson.se>
References: <5EB80D22825EEE42872083AD5BFFB594017F1166@esealmw113.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v746.2)
Message-Id: <C2E6E64E-5AEB-4D18-9944-2FA9360DBD9D@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
Subject: Re: [MMUSIC] ICE: Client supports, but network doesn't
Date: Fri, 23 Jun 2006 14:30:26 -0400
To: Christer Holmberg ((JO/LMF)) <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.746.2)
X-magma-MailScanner-Information: Magma Mailscanner Service
X-magma-MailScanner: Clean
X-Spam-Status: 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
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="===============1655712345=="
Errors-To: mmusic-bounces@ietf.org


--===============1655712345==
Content-Type: multipart/alternative; boundary=Apple-Mail-1-981534940


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


On 21-Jun-06, at 12:59 , Christer Holmberg ((JO/LMF)) wrote:

>
> Hi,
>
> Some questions on ICE:
>
> 1.      What happens if the c/m lines does not correspond to any  
> active a=candidate line? This could happen e.g. if you have a SDP  
> modifying B2BUA (which doesn't support ICE) in the path. One option  
> would be to say that the connectivity check shall be performed also  
> for the c/m lines in that case, but then we may need a "default  
> priority", or something...
What properties would we assume of such a SDP-modifying B2BUA?
For example, would the a-candidate lines still be present? Would they  
be modified by the B2BUA?
Can you cite the  behavior of some known products that do this?

> 2.      The ICE spec says that it is allowed for no a=candiate  
> line, but it does not describe what would happen in that case, and  
> what the expected UA behavior is in that case.
The only way to know that the remote client supports ICE is by the  
presence of a-candidate lines (well, I suppose a-remote-candidate and  
a-ice-pwd lines also count). If these lines are not present, then a  
client must assume the remote client does not support ICE, and thus  
the local client must fall back to normal pre-ICE behavior.
Or am I misunderstanding your comment?

- Philip
--Apple-Mail-1-981534940
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; "><BR><DIV><DIV>On 21-Jun-06, at =
12:59 , Christer Holmberg ((JO/LMF)) wrote:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE type=3D"cite"> =
<BR><P><FONT size=3D"2" face=3D"Courier New">Hi,</FONT> </P><P><FONT =
size=3D"2" face=3D"Courier New">Some questions on ICE:</FONT> =
</P><P><FONT size=3D"2" face=3D"Courier New">1.=A0=A0=A0=A0=A0 What =
happens if the c/m lines does not correspond to any active a=3Dcandidate =
line? This could happen e.g. if you have a SDP modifying B2BUA (which =
doesn't support ICE) in the path. One option would be to say that the =
connectivity check shall be performed also for the c/m lines in that =
case, but then we may need a "default priority", or =
something...</FONT></P></BLOCKQUOTE>What properties would we assume of =
such a SDP-modifying B2BUA?</DIV><DIV>For example, would the a-candidate =
lines still be present? Would they be modified by the =
B2BUA?</DIV><DIV>Can you cite the=A0 behavior of some known products =
that do this?</DIV><DIV><BR><BLOCKQUOTE type=3D"cite"><P><FONT size=3D"2" =
face=3D"Courier New">2.=A0=A0=A0=A0=A0 The ICE spec says that it is =
allowed for no a=3Dcandiate line, but it does not describe what would =
happen in that case, and what the expected UA behavior is in that =
case.</FONT></P></BLOCKQUOTE>The only way to know that the remote client =
supports ICE is by the presence of a-candidate lines (well, I suppose =
a-remote-candidate and a-ice-pwd lines also count). If these lines are =
not present, then a client must assume the remote client does not =
support ICE, and thus the local client must fall back to normal pre-ICE =
behavior.</DIV><DIV>Or am I misunderstanding your =
comment?<BR><BLOCKQUOTE type=3D"cite"></BLOCKQUOTE></DIV><BR =
class=3D"khtml-block-placeholder"><DIV>- Philip</DIV></BODY></HTML>=

--Apple-Mail-1-981534940--


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

--===============1655712345==--




From mmusic-bounces@ietf.org Fri Jun 23 14:58:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ftqrf-0003pU-PN; Fri, 23 Jun 2006 14:58:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ftqre-0003pP-8h
	for mmusic@ietf.org; Fri, 23 Jun 2006 14:58:46 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ftqrb-0002wg-Ig
	for mmusic@ietf.org; Fri, 23 Jun 2006 14:58:46 -0400
Received: from rtp-core-2.cisco.com ([64.102.124.13])
	by rtp-iport-1.cisco.com with ESMTP; 23 Jun 2006 11:58:41 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.06,169,1149490800"; 
	d="scan'208"; a="30356746:sNHT25871080"
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 k5NIwfno013644; 
	Fri, 23 Jun 2006 14:58:41 -0400 (EDT)
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.211);
	Fri, 23 Jun 2006 14:58:41 -0400
Received: from [192.168.1.101] ([10.86.240.43]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 23 Jun 2006 14:58:40 -0400
Message-ID: <449C39DF.7090204@cisco.com>
Date: Fri, 23 Jun 2006 14:58:39 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Rohan Mahy <rohan.mahy@gmail.com>
References: <953beacc0605040909w2fae4be4rc6effde58e9a387f@mail.gmail.com>
In-Reply-To: <953beacc0605040909w2fae4be4rc6effde58e9a387f@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Jun 2006 18:58:40.0623 (UTC)
	FILETIME=[0AA3BFF0:01C696F7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bcd240e64c427d3d3617cfc704e7fd7f
Cc: mmusic@ietf.org
Subject: [MMUSIC] Re: Substantive ICE WGLC comments
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.

Rohan Mahy wrote:

> Hi Folks,
> 
> I think ICE is looking quite good from a technical perspective.  I have
> a few  substantive comments which mostly have to do with terminology and
> clarity of  explaining the mechanism.  I'll send out my NITS in a
> separate email.
> 
> 1) I already sent out my comment that we should not be using the term
> "answer"  when we mean "early SDP" or "courtesy SDP".

I disagree here per my note.

> 
> 2) I also sent out a proposed outline, which I think would help readers
> and  particularly implementors digest and find their way through this
> necessarily  lengthy spec.

I'll address the reorg comments last.

> 
> 3) The term lexicographic is used in the text, and is NOT what we want,
> as it  implies "dictionary" search order, which is inherently language
> specific, and  definitely wrong for comparing candidate IDs made out of
> base64 characters.
> 
> lexicographic: "of or relating to lexicography"
> lexicography: "The process or work of writing, editing, or compiling a
> dictionary"
> 
> For example, in a real lexicographic sort in English upper and lower
> case are  sorted together ("a" comes before "B") and spaces are sorted
> after "z" ("basin  wrench" comes after "basinet"). Other languages are
> different. Some langauges  even have digraphs which are sorted in
> non-character code order (ex: "ch" comes  after "z").
> 
> We want reverse "ASCII sort order"
> 
> Proposed replacement text for Section 7.5 (2nd and 34rd para):
>   Recall that when each candidate is encoded into SDP, it contains a
>   qvalue between 1 and 0, with 1 being the highest priority.  Peer
>   reflexive candidates, learned through the procedures described in
>   Section 7.10 also have a priority between 0 and 1.  For each media
>   stream, the native candidates are ordered based on their qvalues,
>   with higher q-values coming first.  Amongst candidates with the same
>   qvalue, they are ordered based on candidate ID, using reverse
>   ASCII sort order.  For example, the candidate with candidate
>   ID "agD" sorts before the candidate with ID "ad7", and both of those
>   follow the candidate with ID "zz".
> 
>   The usage of a reverse ASCII sort order is important; as discussed
>   in Section 13, it allows peer-derived candidates to be preferred over
>   native ones.
> 
> and later in 7.5:
> s/Amongst those pairs that share
>   the same value for their smaller sequence number and the same value
>   for their larger sequence number, the larger of the two candidate IDs
>   in each pair are selected, and the pairs are lexicographically
>   ordered in reverse by that candidate ID, largest first.
> /Amongst those pairs that share
>   the same value for their smaller sequence number and the same value
>   for their larger sequence number, the larger of the two candidate IDs
>   in each pair are selected, and the pairs are ordered in reverse ASCII
> 
>   order of the candidate ID, largest first. /
> 
> and finally in Section 11.1
> 
> s/the ordering algorithm in Section 7.5 will use
>   the reverse lexicographic order of the candidate ID iself
> /the ordering algorithm in Section 7.5 will use
>   the reverse ASCII sort order of the candidate ID itself/

OK. Hopefully this is clearer.

> 
> 4) There are a few places which I point out in the NITS where the
> document talks about candidates, but should be talking about components
> or transport addresses.  We need to be careful about this.

Agree. I'll try to get a cereful pass through on this.

> 
> 5) The terminology section could be pretty overwhelming.  I think it
> would be useful to describe the terminology wrt to candidates in terms
> of candidate properties.  For example, the "derivation" of a candidate
> could be "local", "server", "relayed", or "derived".  The "sdp-active"
> property for a candidate is either true or false.  The "side" of a
> candidate is either "native" or "remote".  When we do ICE TCP a
> candidate can have a "direction" property as well ("active", "passive",
> "actpass", etc.)

I think the way to address this is to greatly expand the overview, which 
now defines all of these terms with examples through a natural 
progression of explaining the spec, and then the terminology section 
follows. I'm not sure changing from 'terms' to 'properties' would lend 
much more clarity by itself.

> 
> 6) Since our discussions about PRACK, I have been on the lookout for
> complexity added for corner cases. 

Ice has a bunch of that, no doubt. TO some degree ice is struggling to 
meet as many corner cases as possible so it makes voip just work. 90% of 
the cases is not good enough.

> I think some of the behavior around
> changing ICE Passwords falls into that category.  I think it will be
> extremely uncommon to change an ICE password, but I can see the use for it
> (for example for 3pcc controllers).  However, requiring agents that never
> update an ICE password themselves to accept old and new ICE passwords 
> and to
> run a timer for this case seems unnecessarily complex and puts the 
> burden of
> implementation in the wrong place.  I propose that if an ICE password is
> changed, the password is changed immediately with no Tpw timer.  I also
> propose that the only time the password is allowed to be changed is when 
> all
> the candidates for a particular m-line are new candidates.  This addresses
> Flemming's motivation (3pcc) without introducing badness.  I couldn't find
> any motivation for changing the password because it was compromised (I am
> assuming do to forking).  Even so, the only effective way to get out from
> under an attack due to a compromised ICE password is to abandon the 
> relevant
> candidates.
> 
> Proposed text to replace the last paragraph of 7.11.1:
> Subsequent offers MUST contain a=ice-pwd attributes that specify the
> password for the candidates for each media stream.  If any of the 
> candidates
> for a particular m-line are the same as the previous offer, the ICE 
> password
> for that m-line MUST be the same.  If all of the candidates for a 
> particular
> m-line are different from the previous offer, the ICE password for that
> m-line MAY be different.  Note that it is permissible to use a 
> session-level
> attribute in one offer, but to provide the same password as a media-level
> attribute in a subsequent offer.  This is not a change in password, just a
> change in its representation.

I don't feel that strongly on this. I do think it works with the basic 
3pcc case. Text accepted.

> 
> 7) In the last paragraph of Section 7.12 (keepalives), I think it is
> reasonable to send RTP No-op even if the other end does not support it, but
> I'd like to make it clear that if you shouldn't send comfort noise to your
> peer unless the peer agrees this is OK.  Dean actually has a very funny 
> poem
> reminiscent of the Dr Suess rhyme "Green Eggs and Ham".  Dean's poem is
> begins "I do not like your comfort noise..."

Yeah, I've seen the poem in fact :)

If my peer advertises support for NEITHER comfort-noise or rtp no-op 
though, I don't see why one is any better than the other. Both would 
either be discarded because of an unknown PT, or both would be accepted 
by a confused implementation. I actually would suggest maformed RTP 
packets; ie.., ones with an incorrect RTP version. These stand the best 
chance of getting kicked out by an implementation while still keeping 
the nat binding open.

Thats what I've put into the draft.

> 
> 8) I am worried about the 5th paragraph of Section 7.13.  This para says 
> you
> must stop using a candidate you were using for early media Tlo (5 secs)
> after an answer is reliably received.  First, I think this reinforces my
> beef about calling an early SDP an answer throughout the document, because
> in this paragraph you really do mean a *answer*.  Second, I am concerned
> that we are giving both ends 5 seconds to get through a new offer/answer
> exchange, when SIP allows 32 secs.  If a new offer arrives 6.5 seconds 
> after
> the answer, there will be a short gap in the media.  The text should at
> least mention that this can happen.  The tradeoff is between how long you
> use a non-active candidate that may be wrong and the risk of not using a
> working media stream that you just haven't gotten an offer for yet.

Well, you know I disagree on the early answer terminology bit.

That said, this section is still confusing around the term 'reliably', 
and I've changed it to be a bit clearer:

<t> If a candidate pair is selected for early media, an agent MAY send
media on that candidate pair, even if it is not the same as the active
candidate pair. However, to deal with cases in which the offerer and
answerer do not agree on the eventual selection of this candidate for
promotion to active (a rare but possible case), the agent MUST
discontinue using the candidate pair for sending media Tlo seconds
after the next opportunity its peer would have to send an updated
offer.  In the case of an answer delivered in a 200 OK to an offer in
a SIP INVITE (regardless of whether that same answer appeared in an
earlier unreliable provisional response), this would be Tlo seconds
after receipt of the ACK. Tlo SHOULD be configurable and SHOULD have a
default of 5 seconds. This time represents the amount of time it
should take the offerer to perform its connectivity checks, arrive at
the same conclusion about the viability of the early candidate, and
then generate an updated offer promoting it to active. If, after Tlo
seconds, no updated offer arrives, the answerer MUST cease using the
early candidate. Media MAY be sent to the active candidate pair if it
is in the Valid or Recv-Valid state.  </t>


> 
> 9) Section 7.14.  Please mention in the 2nd paragraph that you have to
> determine if a peer supports ICE on a *per-fork* basis.
> 

Good point. Added. This is unfortunate actually since it reduces the 
effectiveness of ICE. An agent may not know about all branches for a 
while, and it would have to accept media until it was sure none of them 
were ICE-unawares.

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 Fri Jun 23 15:05:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtqyU-0007Hk-SX; Fri, 23 Jun 2006 15:05:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtqyU-0007Hf-0d
	for mmusic@ietf.org; Fri, 23 Jun 2006 15:05:50 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtqyS-00039v-ON
	for mmusic@ietf.org; Fri, 23 Jun 2006 15:05:49 -0400
Received: from rtp-core-2.cisco.com ([64.102.124.13])
	by rtp-iport-1.cisco.com with ESMTP; 23 Jun 2006 12:05:48 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.06,169,1149490800"; 
	d="scan'208"; a="30357436:sNHT586871662"
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 k5NJ5lno015243; 
	Fri, 23 Jun 2006 15:05:47 -0400 (EDT)
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.211);
	Fri, 23 Jun 2006 15:05:47 -0400
Received: from [192.168.1.101] ([10.86.240.43]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 23 Jun 2006 15:05:47 -0400
Message-ID: <449C3B8A.3010903@cisco.com>
Date: Fri, 23 Jun 2006 15:05:46 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francois Audet <audet@nortel.com>
Subject: Re: [MMUSIC] much beefier tutorial in ICE - preview text
References: <1ECE0EB50388174790F9694F77522CCF0ABDC967@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF0ABDC967@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Jun 2006 19:05:47.0080 (UTC)
	FILETIME=[08D3EC80:01C696F8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
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

inline.

Francois Audet wrote:

> I believe this text does help. Thanks for doing this.
> 
> Minor comments:
> ---------------
> 
> Your reference [37] should be draft-ietf-behave-nat-udp-07
> instead of draft-ietf-behave-nat-udp-00.... (But really, it
> is in final stages of being RFC so it should be updated
> before publication). Might be worthwile to go through all the
> refernces.

I did. Thanks. This never went beyond -00 because I had hardcoded the 
reference when an earlier ICE draft came out, and the behave-nat draft 
hadn't quite appeared yet and so wasn't in my bibliography.

> 
> I find the use of "variable" for IP addresses and domain names
> and others in SDP quite difficult to read. Also, I'm just having
> visions of implementations in the wild putting $L1, $STUN-PUB-1.IP
> and so forth in SDP... I'd much rather have examples with actual 
> IP addresses and real domain names.

Yeah, Philip made this request too. I will do that.

-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 Fri Jun 23 15:28:30 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtrKN-0003zG-Rw; Fri, 23 Jun 2006 15:28:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtrKB-0003pK-0K
	for mmusic@ietf.org; Fri, 23 Jun 2006 15:28:15 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtrK9-00045I-Jy
	for mmusic@ietf.org; Fri, 23 Jun 2006 15:28:14 -0400
Received: from sj-dkim-5.cisco.com ([171.68.10.79])
	by sj-iport-4.cisco.com with ESMTP; 23 Jun 2006 12:28:13 -0700
X-IronPort-AV: i="4.06,169,1149490800"; 
	d="scan'208"; a="1831589178:sNHT462482392"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-5.cisco.com (8.12.11/8.12.11) with ESMTP id k5NJSCIH017354; 
	Fri, 23 Jun 2006 12:28:12 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k5NJSAcR021196;
	Fri, 23 Jun 2006 12:28:12 -0700 (PDT)
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.211);
	Fri, 23 Jun 2006 15:28:11 -0400
Received: from [192.168.1.101] ([10.86.240.43]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 23 Jun 2006 15:28:11 -0400
Message-ID: <449C40CA.9030604@cisco.com>
Date: Fri, 23 Jun 2006 15:28:10 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
Subject: Re: [MMUSIC] ICE: Client supports, but network doesn't
References: <5EB80D22825EEE42872083AD5BFFB594017F1166@esealmw113.eemea.ericsson.se>
	<C2E6E64E-5AEB-4D18-9944-2FA9360DBD9D@magma.ca>
In-Reply-To: <C2E6E64E-5AEB-4D18-9944-2FA9360DBD9D@magma.ca>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Jun 2006 19:28:11.0408 (UTC)
	FILETIME=[2A1C1900:01C696FB]
DKIM-Signature: a=rsa-sha1; q=dns; l=2822; t=1151090892; x=1151954892;
	c=relaxed/simple; s=sjdkim5001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:Re=3A=20[MMUSIC]=20ICE=3A=20Client=20supports,=20but=20network=20doesn't;
	X=v=3Dcisco.com=3B=20h=3DzOjsKUOh6TpWETQGieIwTDrK60I=3D;
	b=uB+ToFX2V/GmFBqiiWhIc732erJPHZCQmLh8QDnPdMonaITh8LqWHshE/VGMn7GPY6n/VUue
	4GNxpl754AL8I2n+RgQ2En3NHLvKM/mEBVHhHg9xRNmMC8hjKQIIDp3n;
Authentication-Results: sj-dkim-5.cisco.com; header.From=jdrosen@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: mmusic@ietf.org,
	"Christer Holmberg \(\(JO/LMF\)\)" <christer.holmberg@ericsson.com>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org



Philip Matthews wrote:
> 
> On 21-Jun-06, at 12:59 , Christer Holmberg ((JO/LMF)) wrote:
> 
>>
>> Hi,
>>
>> Some questions on ICE:
>>
>> 1.      What happens if the c/m lines does not correspond to any 
>> active a=candidate line? This could happen e.g. if you have a SDP 
>> modifying B2BUA (which doesn't support ICE) in the path. One option 
>> would be to say that the connectivity check shall be performed also 
>> for the c/m lines in that case, but then we may need a "default 
>> priority", or something...
>>
> What properties would we assume of such a SDP-modifying B2BUA?
> For example, would the a-candidate lines still be present? Would they be 
> modified by the B2BUA?
> Can you cite the  behavior of some known products that do this?

I had the same question. Of course, the problem is that since a b2bua is 
entirely undefined its not claer what it will do. But, I think we are 
safe in assuming its one of two things:

1. it modifies the m/c-lines but leaves the a=candidate attributes
2. it modifies the m/c-lines and removes all unknonwn attributes, 
including a=candidate attributes

I suspect (2) is much more likely from SBC products, but you never known.

Lets look at what happens in each of these cases. Case 2 is the easiest. 
  Both agents will think that the other side doesn't support ICE, and 
fallback to regular non-ICE behavior. So, things work as one would expect.

In case 1, with the current specification this will break badly. Because 
the m/c-line never appears as a candidate, the agents will never send 
media to it since it never validates. The way to fix this would be to 
change ice-09 to say that, if an agent doesn't see a cndidate for the 
m/c-line, it CAN send media to it without validating (kind of makes 
sense). Agents would also need to deal with cases where they get an 
updated offer and they can't find a matching candidate pair int he right 
state.

I think its worth adding the behavior needed to do this. I'd like ICE 
and SBC's to be 'compatible' in that, if you use ICE with an ICE-unaware 
SBC at least the call works the same as if the clients hadn't used ICE. 
Otherwise, there is disincetive to put ice into endpoints.

> 
>> 2.      The ICE spec says that it is allowed for no a=candiate line, 
>> but it does not describe what would happen in that case, and what the 
>> expected UA behavior is in that case.
>>

Agree, this is what needs to be described.

-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 Fri Jun 23 15:29:30 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtrLO-0004Uq-FA; Fri, 23 Jun 2006 15:29:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtrLM-0004Uj-NH
	for mmusic@ietf.org; Fri, 23 Jun 2006 15:29:28 -0400
Received: from mx2-1.spamtrap.magma.ca ([209.217.78.160])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtrLL-00046l-Dl
	for mmusic@ietf.org; Fri, 23 Jun 2006 15:29:28 -0400
Received: from mail2.magma.ca (mail2.internal.magma.ca [10.0.10.12])
	by mx2-1.spamtrap.magma.ca (8.13.1/8.13.1) with ESMTP id k5NJTKvO020872;
	Fri, 23 Jun 2006 15:29:20 -0400
Received: from [10.1.5.219] ([216.13.42.126]) (authenticated bits=0)
	by mail2.magma.ca (Magma's Mail Server) with ESMTP id k5NJTJbv015429
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
	Fri, 23 Jun 2006 15:29:20 -0400
In-Reply-To: <449C3B8A.3010903@cisco.com>
References: <1ECE0EB50388174790F9694F77522CCF0ABDC967@zrc2hxm0.corp.nortel.com>
	<449C3B8A.3010903@cisco.com>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A0066DC8-170A-4B99-B42B-4CBA7A7AF9A3@magma.ca>
Content-Transfer-Encoding: 7bit
From: Philip Matthews <philip_matthews@magma.ca>
Subject: Re: [MMUSIC] much beefier tutorial in ICE - preview text
Date: Fri, 23 Jun 2006 15:29:18 -0400
To: Jonathan Rosenberg <jdrosen@cisco.com>
X-Mailer: Apple Mail (2.746.2)
X-magma-MailScanner-Information: Magma Mailscanner Service
X-magma-MailScanner: Clean
X-Spam-Status: 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: Francois Audet <audet@nortel.com>, IETF MMUSIC WG <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org


On 23-Jun-06, at 15:05 , Jonathan Rosenberg wrote:

> inline.
>
> Francois Audet wrote:
>
>> I find the use of "variable" for IP addresses and domain names
>> and others in SDP quite difficult to read. Also, I'm just having
>> visions of implementations in the wild putting $L1, $STUN-PUB-1.IP
>> and so forth in SDP... I'd much rather have examples with actual  
>> IP addresses and real domain names.
>
> Yeah, Philip made this request too. I will do that.
>

Just to be clear, I just asked for ONE example with real candidate IDs.
The other examples can use  fake candidate IDs.

I fully understand why Jonathan uses fake IDs in his example,
and I do find fake IDs easy to read and work with.
My own preference is for IDs of the form L1, L2, L3, ...
and R1, R2, R3, ...  rather than $STUN-PUB-1, etc
because I find it easier to match things  up.

- Philip

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



From mmusic-bounces@ietf.org Fri Jun 23 16:37:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FtsOp-0000pt-SI; Fri, 23 Jun 2006 16:37:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FtsOo-0000eh-5Y
	for mmusic@ietf.org; Fri, 23 Jun 2006 16:37:06 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtsOm-0002Oi-Oy
	for mmusic@ietf.org; Fri, 23 Jun 2006 16:37:06 -0400
Received: from rtp-core-2.cisco.com ([64.102.124.13])
	by rtp-iport-1.cisco.com with ESMTP; 23 Jun 2006 13:37:04 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.06,170,1149490800"; 
	d="scan'208"; a="30363737:sNHT26979200"
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 k5NKb3nq000595; 
	Fri, 23 Jun 2006 16:37:04 -0400 (EDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Fri, 23 Jun 2006 16:37:03 -0400
Received: from [192.168.1.101] ([10.86.240.43]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 23 Jun 2006 16:37:03 -0400
Message-ID: <449C50EE.6030803@cisco.com>
Date: Fri, 23 Jun 2006 16:37:02 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
Subject: Re: [MMUSIC] much beefier tutorial in ICE - preview text
References: <1ECE0EB50388174790F9694F77522CCF0ABDC967@zrc2hxm0.corp.nortel.com>
	<449C3B8A.3010903@cisco.com>
	<A0066DC8-170A-4B99-B42B-4CBA7A7AF9A3@magma.ca>
In-Reply-To: <A0066DC8-170A-4B99-B42B-4CBA7A7AF9A3@magma.ca>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Jun 2006 20:37:03.0310 (UTC)
	FILETIME=[C8EA4EE0:01C69704]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: Francois Audet <audet@nortel.com>, IETF MMUSIC WG <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

inline.

Philip Matthews wrote:

> 
> On 23-Jun-06, at 15:05 , Jonathan Rosenberg wrote:
> 
>> inline.
>>
>> Francois Audet wrote:
>>
>>> I find the use of "variable" for IP addresses and domain names
>>> and others in SDP quite difficult to read. Also, I'm just having
>>> visions of implementations in the wild putting $L1, $STUN-PUB-1.IP
>>> and so forth in SDP... I'd much rather have examples with actual  IP 
>>> addresses and real domain names.
>>
>>
>> Yeah, Philip made this request too. I will do that.
>>
> 
> Just to be clear, I just asked for ONE example with real candidate IDs.
> The other examples can use  fake candidate IDs.

Yes, I understand. My plan is to take one of the SDP in the examples 
section and show it with the variables filled in. Trust me, I have 
neither the time nor the energy nor the interest to do more than one ;)

-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 Sat Jun 24 08:44:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fu7VG-0004w5-OV; Sat, 24 Jun 2006 08:44:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fu7VF-0004u1-Se
	for mmusic@ietf.org; Sat, 24 Jun 2006 08:44:45 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fu7VB-0007yF-0M
	for mmusic@ietf.org; Sat, 24 Jun 2006 08:44:45 -0400
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	38EA78E0001; Sat, 24 Jun 2006 14:44:22 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 24 Jun 2006 14:44:21 +0200
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 24 Jun 2006 14:44:21 +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: VS: [MMUSIC] ICE: Client supports, but network doesn't
Date: Sat, 24 Jun 2006 14:44:21 +0200
Message-ID: <5EB80D22825EEE42872083AD5BFFB594117CFE@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] ICE: Client supports, but network doesn't
Thread-Index: AcaW+ywVsD42rqmyTzaE7mQiM+/jqAAjpVC2
References: <5EB80D22825EEE42872083AD5BFFB594017F1166@esealmw113.eemea.ericsson.se>
	<C2E6E64E-5AEB-4D18-9944-2FA9360DBD9D@magma.ca>
	<449C40CA.9030604@cisco.com>
From: "Christer Holmberg \(JO/LMF\)" <christer.holmberg@ericsson.com>
To: "Jonathan Rosenberg" <jdrosen@cisco.com>,
	"Philip Matthews" <philip_matthews@magma.ca>
X-OriginalArrivalTime: 24 Jun 2006 12:44:21.0881 (UTC)
	FILETIME=[EA996E90:01C6978B]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
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,

>>> 1.      What happens if the c/m lines does not correspond to any
>>> active a=3Dcandidate line? This could happen e.g. if you have a SDP
>>> modifying B2BUA (which doesn't support ICE) in the path. One option
>>> would be to say that the connectivity check shall be performed also
>>> for the c/m lines in that case, but then we may need a "default
>>> priority", or something...
>>>
>> What properties would we assume of such a SDP-modifying B2BUA?
>> For example, would the a-candidate lines still be present? Would they =
be
>> modified by the B2BUA?
>> Can you cite the behavior of some known products that do this?

[CHH] I would assume that one could find products behaving in either =
way. IF the B2BUA removes the candiate attributes I guess we'll get the =
scenario described in my second question.=20

>I had the same question. Of course, the problem is that since a b2bua =
is
>entirely undefined its not claer what it will do. But, I think we are
>safe in assuming its one of two things:
>
>1. it modifies the m/c-lines but leaves the a=3Dcandidate attributes
>2. it modifies the m/c-lines and removes all unknonwn attributes,
>including a=3Dcandidate attributes

[CHH] Correct.=20

>I suspect (2) is much more likely from SBC products, but you never =
known.
>
>Lets look at what happens in each of these cases. Case 2 is the =
easiest.
>Both agents will think that the other side doesn't support ICE, and
>fallback to regular non-ICE behavior. So, things work as one would =
expect.

[CHH] As I said in my second question, ICE does allow for the case where =
there is no candidate attribute, and from the receivers perspective this =
would be such case, wouldn't it? But, if there are no candidate =
attributes, how does the receiver know that the sender supports ICE? Is =
there an option tag, or someting? Or, is it assumed that the other ICE =
related attributes (ice-pwd) are still present, to indicate the support =
of ICE?

>In case 1, with the current specification this will break badly. =
Because
>the m/c-line never appears as a candidate, the agents will never send
>media to it since it never validates. The way to fix this would be to
>change ice-09 to say that, if an agent doesn't see a cndidate for the
>m/c-line, it CAN send media to it without validating (kind of makes
>sense). Agents would also need to deal with cases where they get an
>updated offer and they can't find a matching candidate pair int he =
right
>state.

[CHH] Is there a reason why the m/c-lines couldn't be used for =
validation - at least in the case when there is no matching candiate?
=20
Regards,
=20
Christer
=20

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



From mmusic-bounces@ietf.org Sat Jun 24 14:12:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FuCcA-0002Q7-GN; Sat, 24 Jun 2006 14:12:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FuCc9-0002Q2-IO
	for mmusic@ietf.org; Sat, 24 Jun 2006 14:12:13 -0400
Received: from py-out-1112.google.com ([64.233.166.179])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FuCc8-0006Va-48
	for mmusic@ietf.org; Sat, 24 Jun 2006 14:12:13 -0400
Received: by py-out-1112.google.com with SMTP id x66so1036424pye
	for <mmusic@ietf.org>; Sat, 24 Jun 2006 11:11:38 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=A0Rwwgtpt+OAXrlWcid4dTa6TjitV7SwJG7CFZKPmTUnRXRXhAiGpcT/JIDH8nWVYu62U9+XJ0wdcpEdFhU5nXlqBJ6o6b/C+OU7q1wLmbdN/MGZBOWytGDutTDIidR5E3jyADdNfKfNLglFhul6AVa7vQPXNl+/F5RRzq7YJ50=
Received: by 10.35.94.2 with SMTP id w2mr3777738pyl;
	Sat, 24 Jun 2006 11:11:38 -0700 (PDT)
Received: by 10.35.81.17 with HTTP; Sat, 24 Jun 2006 11:11:38 -0700 (PDT)
Message-ID: <953beacc0606241111t26581ed3me29cf2a66e85ff51@mail.gmail.com>
Date: Sat, 24 Jun 2006 11:11:38 -0700
From: "Rohan Mahy" <rohan.mahy@gmail.com>
To: "Jonathan Rosenberg" <jdrosen@cisco.com>
Subject: Re: [MMUSIC] quick WGLC comment on ICE
In-Reply-To: <4498BCF6.3030602@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <953beacc0604261353g35db3534ld2076960cc780ab0@mail.gmail.com>
	<4498BCF6.3030602@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48
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,

IMO, the fundamentally interesting attribute of an answer is that it
closes an offer/answer exchange.  Once the answer is received, either
side can send a new offer.  This is what makes it special.  Early SDP
in an unreliable 18x does not meet that test. Not until the REAL
answer arrives in the 200, can you update your offer/answer state
machine.

thanks,
-rohan


On 6/20/06, Jonathan Rosenberg <jdrosen@cisco.com> wrote:
> I don't think its contradictory at all. 3261 is pretty clear that what
> comes in a provisional response is the same as will come in a 2xx. Its
> just not reliable so you need to send the same answer in the 2xx. Thus,
> if a UAC should receive a 18x with an SDP, even if the 18x is
> unreliable, that constitutes an answer. Where in RFC 3261 does it say
> that whats in the 18x is NOT an answer? Indeed, according to this:
>
>      o  If the initial offer is in an INVITE, the answer MUST be in a
>           reliable non-failure message from UAS back to UAC which is
>           correlated to that INVITE.  For this specification, that is
>           only the final 2xx response to that INVITE.  That same exact
>           answer MAY also be placed in any provisional responses sent
>           prior to the answer.  The UAC MUST treat the first session
>           description it receives as the answer, and MUST ignore any
>           session descriptions in subsequent responses to the initial
>           INVITE.
>
> If you receive SDP in a 18x you won't even look at the SDP in the 2xx.
> Pretty clear thats the answer.
>
> Given that the entirety of ICE talks about offers and answers only, and
> these are the only concepts in RFC 3264, I don't think it makes sense to
> move away from offer/answer terminology.
>
> Thanks,
> Jonathan R.
>
> Rohan Mahy wrote:
>
> > Hi,
> >
> > ICE -08 still refers to offers and answers using terminology which
> > contradicts Section 13.2.1 of RFC3261.  By my reading, a session
> > description in an unreliable 18x is never an offer or an answer.  I
> > often describe this as an "early session description" or "courtesy SDP".
> >
> > Several places in ICE (particularly Section 8) talk about performing ICE
> > operations once you receive an answer and refer to courtesy SDP as if it
> > is an answer.
> >
> > For example, the current wording of Section 8 para 2:
> >
> >    ICE requires a series of STUN-based connectivity checks to take place
> >    between endpoints.  These checks start from the answerer on
> >    generation of its answer, and start from the offerer when it receives
> >
> >    the answer.  These checks can take time to complete, and as such, the
> >    selection of messages to use with offers and answers can effect
> >    perceived user latency.  Two latency of figures are of particular
> >
> >    interest.  These are the post-pickup delay and the post-dial delay.
> >    The post-pickup delay refers to the time between when a user "answers
> >    the phone" and when any speech they utter can be delivered to the
> >
> >    caller.  The post-dial delay refers to the time between when a user
> >    enters the destination address for the user, and ringback begins as a
> >    consequence of having succesfully started ringing the phone of the
> >
> >    called party.
> >
> >
> > and my proposed rewording:
> >
> >    ICE requires a series of STUN-based connectivity checks to take place
> >    between endpoints.  These checks start from the answerer on
> >    generation of its first session description sent after the offer,
> >
> >    and start from the offerer when it receives
> >    this first session description.  If this first message arrives in
> >    an unreliable message, the actual answer will arrive in the first reliable
> >    message after the offer.
> >
> >
> >    STUN connectivity checks can take time to complete, and as such, the
> >    number and timing of messages used for these checks can affect
> >    perceived user latency.  Two latency figures are of particular
> >
> >    interest.  These are the post-pickup delay and the post-dial delay.
> >    The post-pickup delay refers to the time between when a user "answers
> >    the phone" and when any speech they utter can be delivered to the
> >
> >    caller.  The post-dial delay refers to the time between when a user
> >    enters the destination address for the user, and ringback begins as a
> >    consequence of having succesfully started ringing the phone of the
> >
> >    called party.
> >
> > and also in the 5th paragraph (currently):
> >
> >    For this reason, if an offer is received in an INVITE request, the
> >    UAS SHOULD immediately gather its candidates and then generate an
> >
> >    answer in a provisional response.  When reliable provisional
> >    responses are not used, the SDP in the provisional response is not
> >    formally the answer; the value in the 200 OK is the actual answer.
> >    However, RFC 3261 allows for SDP to appear in an unreliable
> >
> >    provisional response, in which case its value has to be identical to
> >    the value placed in the 200 OK.  Thus, we refer to the SDP in the
> >    provisional response, even when unreliable, as the answer.  To deal
> >
> >    with possible losses of the provisional response, it SHOULD be
> >    retransmitted until some indication of receipt.  This indication can
> >    either be through PRACK [11], or through the receipt of a STUN
> >    Binding Request with a correct username and password.  Even if PRACK
> >
> >    is not used, the provisional response SHOULD be retransmitted using
> >    the exponential backoff described in [11].  Furthermore, once the
> >    answer has been sent, the agent SHOULD begin its connectivity checks.
> >
> >    Once a candidate reaches the Valid or Recv-Valid state, the UAS has a
> >    known-valid path for media packets towards the UAC.  This point is
> >    called the connected point in ICE.
> >
> > and my proposed rewording:
> >
> >    For this reason, if an offer is received in an INVITE request, the
> >    UAS SHOULD immediately gather its candidates and then generate a
> >    session descripition in a provisional response.  When reliable provisional
> >
> >    responses are not used, the SDP in the provisional response is not
> >    formally the answer; the value in the 200 OK is the actual answer.
> >    However, RFC 3261 encourages implementors to include this "courtesy SDP"
> >
> >    in an unreliable
> >    provisional response, in which case its value has to be identical to
> >    the value placed in the 200 OK.  To deal
> >    with possible losses, the provisional response SHOULD be
> >    retransmitted until the UAS receives some indication of receipt.  This indication can
> >
> >    either be through PRACK [11], or through the receipt of a STUN
> >    Binding Request with a correct username and password.  Even if PRACK
> >    is not used, the provisional response SHOULD be retransmitted using
> >
> >    the exponential backoff described in [11].  Furthermore, once the
> >    session description has been sent, the agent SHOULD begin its connectivity checks.
> >    Once a candidate reaches the Valid or Recv-Valid state, the UAS has a
> >
> >    known-valid path for media packets towards the UAC.  This point is
> >    called the connected point in ICE.
> >
> > I can propose specific text for the other usages if other agree this
> > needs to be changed.
> >
> > thanks,
> > -rohan
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > 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 Sat Jun 24 15:56:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FuEEh-0001Se-PQ; Sat, 24 Jun 2006 15:56:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FuEEg-0001SZ-8H
	for mmusic@ietf.org; Sat, 24 Jun 2006 15:56:06 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FuEEe-0000X1-9H
	for mmusic@ietf.org; Sat, 24 Jun 2006 15:56:06 -0400
Received: from sj-dkim-8.cisco.com ([171.68.10.93])
	by sj-iport-5.cisco.com with ESMTP; 24 Jun 2006 12:56:02 -0700
X-IronPort-AV: i="4.06,172,1149490800"; 
	d="scan'208"; a="300509409:sNHT43404620"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-8.cisco.com (8.12.11/8.12.11) with ESMTP id k5OJu2kL003412; 
	Sat, 24 Jun 2006 12:56:02 -0700
Received: from [192.168.1.2] (sjc-vpn-hwcore-493.cisco.com [10.21.153.237])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k5OJu1cL007677;
	Sat, 24 Jun 2006 12:56:01 -0700 (PDT)
In-Reply-To: <F1C53414-D195-43F4-B1BB-A6BDB831EFBC@csperkins.org>
References: <GLEFKJBKNILEBOELNIBIGELADOAA.gunnar.hellstrom@omnitor.se>
	<F1C53414-D195-43F4-B1BB-A6BDB831EFBC@csperkins.org>
Mime-Version: 1.0 (Apple Message framework v750)
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed
Message-Id: <AE07A18A-F9DE-4961-A9ED-FDDB37CB43B2@cisco.com>
Content-Transfer-Encoding: quoted-printable
From: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [MMUSIC] Re: ietf-mmusic-sdp-media-content-03
Date: Sat, 24 Jun 2006 12:55:58 -0700
To: Colin Perkins <csp@csperkins.org>
X-Mailer: Apple Mail (2.750)
DKIM-Signature: a=rsa-sha1; q=dns; l=19583; t=1151178962; x=1152042962;
	c=relaxed/simple; s=sjdkim8001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fluffy@cisco.com;
	z=From:Cullen=20Jennings=20<fluffy@cisco.com>
	|Subject:Re=3A=20[MMUSIC]=20Re=3A=20ietf-mmusic-sdp-media-content-03;
	X=v=3Dcisco.com=3B=20h=3DlzSumHOAB+EMEtcep7BaKKzCUlA=3D;
	b=HzK1q5ZQDsKZ0Sha59sAXqDrPBCXxEPP2VviTneDJU1GmLczYy4HXrCMCWKE8ijNQ5USx6bB
	ID0whyJlh/D8VVxo9StM1vAoqC3ozoNmIrpY/2/iV8TLdrHWcNjvOzjb;
Authentication-Results: sj-dkim-8.cisco.com; header.From=fluffy@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b83962958e2d910ed948e2f9e138d171
Cc: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>,
	IETF MMUSIC WG <mmusic@ietf.org>, degodefroi@gmail.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


Ok, I just entered proper comments in tracker, bit more inline here.

On Jun 20, 2006, at 3:29 PM, Colin Perkins wrote:

> Hi,
>
> Just following up on this... did we ever get agreement on the right =20=

> way to proceed? If an updated draft is needed, I'd like to get it =20
> in before the deadline. Cullen? Jani?
>
> Colin
>
>
>
>
> On 18 May 2006, at 22:25, Gunnar Hellstrom wrote:
>> Hi,
>> I agree that the content parameters "txp" and "user-floor" =20
>> indicate similar functionality.
>>
>> But I see nothing wrong in having them both in the specification =20
>> anyway.

I've no problem with one, both, or three but it needs to be clear =20
what implementers need to do.

>>
>> The txp parameter value may be used to invoke some automated =20
>> mechanism in a text capable gateway to support conversion between =20
>> full duplex simultaneous multimedia communication and half-duplex =20
>> turn-taking, alternating text - voice communication in PSTN. But =20
>> it can also be used just as a warning to the IP user to be aware =20
>> of possible limitations in simultanity and duplex use of media.
>>
>> We could go deeper in specifying exactly what limitations are =20
>> valid at each moment, but I doubt that any manufacturer want to =20
>> refine their gateway designs to that degree.
>> If we want to go deeper, we could use the following parameters:
>>
>> -    voice-text-alternating    ( in fact influencing two media )
>>
>> -    half-duplex                  ( when strictly only one =20
>> direction at a time can be used )
>>
>> -    half-duplex-interruptable  ( when only one direction at a =20
>> time should be used for contents, but it is possible to send an =20
>> indication that the other party want the turn. )
>>
>>
>> I think that txp is enough.
>>
>> I just participate in a discussion where we have tried to meet =20
>> requirements to keep gateway resources low by allowing it to set =20
>> up a real-time text connection between a PSTN gateway and an IP =20
>> terminal only when there are indications that text will be used. =20
>> It is a compromise that may be needed in reality.

I agree this is needed - just want it to be clear.

>>
>> In the draft document from that discussion, we use both the =20
>> a=3Dcontent:txp parameter, and the following parmeters from RFC 3840 =20=

>> and 3841.
>>
>> Contact: duplex=3D"half",
>>
>> Contact: <uri>;text
>>
>> Accept-Contact: *;text;require
>>
>> Accept-Contact: *;text

It seems like the 3840 style stuff may be the way you want to signal =20
this.


>>
>>
>> I would appreciate very much to get comments on the parameter =20
>> values and logic we have drafted.
>>
>> ----------------------Proposed alternative to ITU-T V.151 Annex D, =20=

>> using caller and callee capabilities and preferences and media-=20
>> contents to control gateway - IP text capable terminal =20
>> communication--------------------------------------------------------=20=

>> ----------------
>>
>> Alternative proposal for V.151 Annex D.
>> ANNEX D2
>>
>> Interworking IP Text Devices with V.151 Gateways.
>> Connect text channel when usage of real-time text is likely.
>>
>>
>>
>> D.1 Introduction
>> Some non-Gateway IP devices in the network not having a means of =20
>> modulating or demodulating PSTN textphone signals, such as IVR =20
>> systems, voicemail systems, IP phones, Multimedia telephones or =20
>> other devices, may support the transmission of real-time text over =20=

>> IP networks and, ideally, interwork with V.151-compliant Gateways =20
>> in order to provide a means through which users of PSTN textphone =20
>> devices can communicate with those IP devices.  This class of =20
>> devices is referred to herein as an "IP Text Device=94 (ITD).  This =20=

>> Annex defines the procedures that may be used in order to allow =20
>> for such interworking between V.151 Gateways and ITDs. The main =20
>> principle is to use RFC 4103 as the default text transport method =20
>> between gateways and ITD:s, and open text channels only when it is =20=

>> likely that the text channel will be used.
>>
>> D.2 Exchanging capabilities and opening media streams
>> When establishing a call, an ITD may advertise support for real-=20
>> time text  in accordance with IETF RFC 4103.
>>
>> In general, ITDs also transmit text characters when communicating =20
>> with other ITDs using RFC 4103, which specifies the establishment =20
>> of a separate RTP stream specifically for transmitting text =20
>> characters.  However, since V.151 PSTN gateway devices interleave =20
>> audio and text data when used for Gateway - to - gateway =20
>> operation, V.151 gateways need to support both RFC 4103 to =20
>> interwork with ITDs and RFC 4351 for communicating with other PSTN =20=

>> gateways.
>>
>> As such, V.151 gateways are Recommended to indicate support for =20
>> both transport methods initially when exchanging capability =20
>> information. However, relatively few calls use real-time text in =20
>> the PSTN, and therefore it may be desirable for the gateway to not =20=

>> open the text channel until either party in the call explicitly =20
>> acts to use real-time text.
>>
>> According to normal procedures in IP multimedia systems, it is =20
>> allowable to indicate capability for other transport protocols for =20=

>> real-time text as well as RFC 4103 and connect such alternatives.
>>
>> ----
>>
>> D.2.2    SDP based systems
>> Similar logic follows for SDP-based systems.
>>
>> In SIP-based systems, the terminal and gateway shall announce =20
>> support for text in the Contact field according to RFC 3840, and =20
>> may indicate preference for text according to RFC 3841.
>>
>> Contact: <uri>;text
>>
>> A calling SIP terminal who does not put priority to text may =20
>> indicate an interest to use text by:
>>
>> Accept-Contact: *;text
>>
>> A calling SIP terminal who want to put priority to establishing a =20
>> text connection shall indicate that by:
>>
>> Accept-Contact: *;text;require
>>
>> Most commonly, PSTN text telephones support alternating text and =20
>> audio during the call, but not simultaneous text and audio. If the =20=

>> gateway only supports alternating text and audio during the PSTN =20
>> text session, it may be beneficial to make the ITD user aware of =20
>> this limitation. It is proposed to use the Duplex parameter of RFC =20=

>> 3840 for this purpose.
>>
>> Contact: duplex=3D"half"
>>
>> There is a parameter also for use in the text media description:
>>
>> a=3Dcontent:txp
>>
>> It should be used to indicate to the ITD user that the text =20
>> channel is half duplex and turn-taking habits should be used.
>>
>>
>>
>> Note that while the use of RFC 2198 redundancy or other fault =20
>> tolerance scheme is not shown in the abbreviated examples below, =20
>> appropriate mechanisms should be employed to protect the =20
>> transmission of the text stream in accordance with the text =20
>> transport specifications.
>>
>>
>>
>> D.2.2.1 Call from PSTN
>> Consider the following abbreviated example SDP that might be found =20=

>> in an offer sent by a V.151 Gateway not offering RFC 4103 support =20
>> initially, but indicating text support and that the text support =20
>> is alternating with audio:
>>
>>       Contact: <uri>;text;duplex=3D"half"
>>
>>        m=3Daudio 7200 RTP/AVP 0 98
>>
>>        a=3Drtpmap:98 t140c/8000
>>
>>        a=3Dfmtp:98 cps=3D20
>>
>> If the gateway at that time already knows that text will be needed =20=

>> in the call, a requirement for text shall be included, and a media =20=

>> line for text. The decision to include text when offering the call =20=

>> may be because textphone tones have already been detected on the =20
>> PSTN line, the gateway may be configured to be a dedicated text =20
>> gateway, or it may be known by subscription or any other external =20
>> means that either user has preference for text.
>>
>>       Accept-Contact: *;text;require
>>
>>       Contact: <uri>;text;duplex=3D"half"
>>
>>        m=3Daudio 7200 RTP/AVP 0 98
>>
>>        a=3Drtpmap:98 t140c/8000
>>
>>        a=3Dfmtp:98 cps=3D20
>>
>>        m=3Dtext 7202 RTP/AVP 99
>>
>>        a=3Drtpmap:99 t140/1000
>>
>>       a=3Dcontent:txp
>>
>>
>>
>> If the answering device is an ITD, with no specific indication =20
>> that text would be used,  it would accept only the G.711 audio.
>>
>>       Contact: <uri>;text
>>
>>       m=3Daudio 7200 RTP/AVP 0
>>
>>
>>
>> If the answering device is an ITD where the user has indicated a =20
>> preference for text, it would accept the text/t140 medium and =20
>> optionally G.711 audio.
>>
>>       Contact: <uri>;text
>>
>>        m=3Daudio 7200 RTP/AVP 0
>>
>>        m=3Dtext 7202 RTP/AVP 99
>>
>>        a=3Drtpmap:99 t140/1000
>>
>> Note that this response is only possible when the gateway had =20
>> included text/140 in the offer. For other cases, the terminal =20
>> needs to do a reinvite to add text to the call.
>>
>> D.2.2.2 Call from IP terminal
>> A calling ITD could give a strong indication that it requires text =20=

>> support in the call by an INVITE according to this example:
>>
>>       Contact: <sip:terminal@host.example.com>;text
>>
>>       Accept-Contact: *;text;require
>>
>>        m=3Daudio 7200 RTP/AVP 0
>>
>>        m=3Dtext 7202 RTP/AVP 99
>>
>>        a=3Drtpmap:99 t140/1000
>>
>>
>>
>> The network would make efforts to connect to a text capable =20
>> gateway, that may acknowledge the text channel initially, because =20
>> of the indication that text is required. The gateway should also =20
>> start text channel connection procedures on the PSTN side.
>>
>>       Contact: <gwy-uri>;text;duplex=3D"half"
>>
>>        m=3Daudio 7200 RTP/AVP 0
>>
>>        m=3Dtext 7202 RTP/AVP 99
>>
>>        a=3Drtpmap:99 t140/1000
>>
>>        a=3Dfmtp:99 cps=3D20
>>
>>       a=3Dcontent:txp
>>
>>
>>
>> If on the other hand, the ITD user is not depending on text, but =20
>> want to have it available for occasional use, the ITD can be =20
>> configured to make its INVITE as follows:
>>
>>
>>
>>       Contact: <sip:terminal@host.example.com>;text
>>
>>       Accept-Contact: *;text
>>
>>        m=3Daudio 7200 RTP/AVP 0
>>
>>        m=3Dtext 7202 RTP/AVP 99
>>
>>        a=3Drtpmap:99 t140/1000
>>
>>        a=3Dfmtp:99
>>
>>
>>
>> The network would try to connect to a text capable gateway, but =20
>> may connect through a non capable. The gateway may decide to not =20
>> acknowledge the text channel initially, but indicates its text =20
>> capability in the Contact header.
>>
>>       Contact: <gwy-uri>;text;duplex=3D"half"
>>
>>        m=3Daudio 7200 RTP/AVP 0
>>
>>
>>
>> D.2.2.3 Text channel establishment during a call
>> If at a later stage in the call, either party in the call starts =20
>> text activity, and no text channel was set up initially, a text =20
>> channel should be added to the session by a REINVITE. .
>>
>> This is an example of how it would be expressed from the gateway,
>>
>>        Contact: <uri>;text;duplex=3D"half"
>>
>>        m=3Daudio 7200 RTP/AVP 0
>>
>>         m=3Dtext 7202 RTP/AVP 99
>>
>>         a=3Drtpmap:99 t140/1000
>>
>>         a=3Dfmtp:99 cps=3D20
>>
>>        a=3Dcontent:txp
>>
>> The other party should answer with a similar sdp.
>>
>>
>>
>> If instead it is the ITD user who starts text activity, a text =20
>> channel should be added to the session by a REINVITE from the ITD =20
>> according to the following example. .
>>
>>        Contact: <uri>;text
>>
>>        m=3Daudio 7200 RTP/AVP 0
>>
>>        m=3Dtext 7202 RTP/AVP 99
>>
>>        a=3Drtpmap:99 t140/1000
>>
>>        a=3Dfmtp:99 cps=3D20
>>
>>
>>
>> The gateway should answer with
>>
>>        Contact: <uri>;text;duplex=3D"half"
>>
>>        m=3Daudio 7200 RTP/AVP 0
>>
>>        m=3Dtext 7202 RTP/AVP 99
>>
>>        a=3Drtpmap:99 t140/1000
>>
>>        a=3Dfmtp:99 cps=3D20
>>
>>        a=3Dcontent:txp
>>
>> .
>>
>> The line "a=3Dcontent:txp" is sent from the gateway as an indication =20=

>> that half duplex procedures should be applied by the users in the =20
>> text stream.
>>
>> D.3 Procedure for terminals including both RFC 4103 and RFC 4351 =20
>> support
>> In the case when a terminal implements both RFC 4103 and RFC 4351 =20
>> for text transport, the following procedures should be applied in =20
>> the terminal.
>>
>> When establishing a call, an ITD may advertise support for ToIP in =20=

>> accordance with Annex B or Annex C, with one notable important =20
>> exception: the ITD shall not include a list of supported =20
>> modulations.  Absence of the list of modulations shall be used as =20
>> an indicator to the V.151 Gateway that the remote side is an ITD.
>>
>> Further, ITD devices shall not utilize SSEs in order to control =20
>> state transition to ToIP.  Rather, once a media flow is =20
>> established to transport T.140 characters, either the Gateway or =20
>> the ITD may transmit text immediately and without further =20
>> negotiation.  Payload type switching is used to transition between =20=

>> AUDIO and Text Relay modes.
>>
>> D.4 State transition and text handling
>> The following description assumes that a V.151-compliant Gateway =20
>> is in communication with an ITD and media flows have been =20
>> established to transport text over IP in accordance with RFC 4103.
>>
>> When the gateway compliant to this annex detects a PSTN textphone =20
>> that it supports using text relay, it shall autonomously connect =20
>> to the textphone.  After connection on the PSTN side, the gateway =20
>> shall open the text channel to the ITD. It shall decode the =20
>> characters received and transmit those to the ITD, giving proper =20
>> respect to the maximum character-per-second (CPS) parameter =20
>> advertised by the ITD.  Determining the type of PSTN textphone =20
>> device in use is the responsibility of the Gateway and the ITD =20
>> need not concern itself with what kind of PSTN textphone device is =20=

>> connected to the Gateway.
>>
>> Likewise, when the ITD first has characters to send to the Gateway =20=

>> using text/140 payload type, the ITD opens the text channel if it =20
>> was not opened before. Then the ITD transmits the characters to =20
>> the Gateway. The Gateway shall perform a probing, as necessary, to =20=

>> determine the type of PSTN device connected, if any.  While =20
>> probing, the Gateway shall buffer any characters received and =20
>> transmit those when probing completes and the gateway is connected =20=

>> to the text phone.  The size of the character buffer is a matter =20
>> of implementation, but should support the reception and buffering =20
>> of characters for at least 60 seconds at the specified maximum =20
>> character-per-second (CPS) value signaled to the ITD.
>>
>> If the Gateway does not support the modulation used by the PSTN =20
>> textphone device, the Gateway may transmit the received textphone =20
>> signals via VBD or the audio stream, depending on the capabilities =20=

>> of the ITD.  Further, the Gateway may simply discard characters =20
>> received from the ITD or transmit them to the PSTN textphone =20
>> device using a pre-provisioned modulation.
>>
>>
>> /
>>
>> Gunnar
>> ---------------------------------------------------------------------=20=

>> --------
>> Gunnar Hellstr=F6m, Omnitor
>> gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se>
>> Mob: +46 708 204 288
>> Phone: +46 8 556 002 03
>> www.omnitor.se <http://www.omnitor.se>
>>
>>
>> -----Original Message-----
>> From: Jani Hautakorpi (JO/LMF) [mailto:jani.hautakorpi@ericsson.com]
>> Sent: Wednesday, May 17, 2006 10:12 AM
>> To: Cullen Jennings
>> Cc: gunnar.hellstrom@omnitor.se; degodefroi@gmail.com; Gonzalo
>> Camarillo; IETF MMUSIC WG
>> Subject: [MMUSIC] Re: ietf-mmusic-sdp-media-content-03
>>
>>
>> Hi Cullen,
>>
>> Cullen Jennings wrote:
>> > I was just reviewing this document and I can't figure out  the
>> > difference from user-floor and txp from the point of view =20
>> describing
>> > the content.
>>
>> Actually, there are no major differences between them, but Gunnar
>> Hellstrom and Arnoud van Wijk (in the cc:) really wanted a value that
>> was "txp". Gunnar and Arnoud can explain this better, but the main
>> reason is that this way they can refer to and further describe the =20=

>> usage
>> of "txp" from some other draft, e.g. ietf-draft-sipping-toip.
>>
>> > It seems like this might be better to indicate that the
>> > content type was "simplex" as normal media is assumed to be =20
>> "duplex".
>>
>> This is a matter of naming. Personally I believe that "user-floor" is
>> more descriptive than "simplex", because there can also be such =20
>> one-way
>> media that doesn't require user level floor control. What do you =20
>> think?
>>
>> > I'm not sure I like what I am proposing here but I think we need to
>> > improve on the definition for these two. The current description =20=

>> of  txt
>> > does not seem to match the requirements for it on the email =20
>> list  and
>> > the definition of user-floor I have no idea when to add to a =20
>> stream.
>>
>> I would say that "txp" is exactly what was described on the mmusic's
>> mailing list, please see the "[MMUSIC] I-D ACTION:
>> draft-ietf-mmusic-sdp-media-content-01.txt" thread, starting 18th =20
>> Feb.
>>
>> Regarding the addition of "user-floor" to media stream: The device =20=

>> that
>> needs to add this value knows it by itself. For example, a new
>> walkie-talkie type of device can know that it requires user level =20
>> floor
>> control. But of course we can try to elaborate this on the draft, =20
>> if you
>> want.
>>
>> > It also might be nice to provide more guidance on what is =20
>> appropriate
>> > to signal with "content" and what is not. For example, I would =20
>> not  want
>> > people signaling the mpeg profile using this. I think what we  =20
>> want to
>> > do here is something like signal the "semantic content" of  the =20
>> stream
>> > such that an application that is offered multiple streams  can =20
>> pick the
>> > right stream or map the streams to the users  preferences. Would =20=

>> it be
>> > possible to add more text about what would  not be appropriate =20
>> to use
>> > this registry for.
>>
>> I really can't see how somebody could try to signal the mpeg profile
>> with this draft, because it just doesn't have enough features for
>> signaling such information. I feel that the possible use scenarios =20=

>> are
>> already quite limited, and it's hard for me to invent how anybody =20
>> could
>> misuse this draft. But, if you (or somebody else) can come up with =20=

>> some
>> valid, non-appropriate use cases, I'm happy to add them to the draft.
>>
>>
>> --
>> Jani
>>
>> _______________________________________________
>> 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 Sat Jun 24 16:43:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FuEyu-0004Uc-SZ; Sat, 24 Jun 2006 16:43:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FuEyt-0004Rr-Uu
	for mmusic@ietf.org; Sat, 24 Jun 2006 16:43:51 -0400
Received: from py-out-1112.google.com ([64.233.166.183])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FuEyt-0002bn-4y
	for mmusic@ietf.org; Sat, 24 Jun 2006 16:43:51 -0400
Received: by py-out-1112.google.com with SMTP id b36so774440pyb
	for <mmusic@ietf.org>; Sat, 24 Jun 2006 13:43:50 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=fjuH8Zuc18QGw804C2B6h57UnncGmqj+t8FHKU6slnLYXERMczGSzEu56ILB1u41jtu6b7mE4ebpT0Y8+MR1yHxSW97N7W89kIusqmrJd29wYxXF3yrbtnz5/6ZVQEDb6EEeXgjrv5z+9Fmnq7BDTB8LC5Uj9l/a/7Fa88wxDms=
Received: by 10.35.34.18 with SMTP id m18mr3913677pyj;
	Sat, 24 Jun 2006 13:43:50 -0700 (PDT)
Received: by 10.35.81.17 with HTTP; Sat, 24 Jun 2006 13:43:50 -0700 (PDT)
Message-ID: <953beacc0606241343x29424613m990aeda0dd2930ea@mail.gmail.com>
Date: Sat, 24 Jun 2006 13:43:50 -0700
From: "Rohan Mahy" <rohan.mahy@gmail.com>
To: "Jonathan Rosenberg" <jdrosen@cisco.com>
Subject: Re: [MMUSIC] much beefier tutorial in ICE - preview text
In-Reply-To: <44984D0F.5080808@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <44984D0F.5080808@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7ddf3da2e36bf1816c08a54f16fcec30
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

Hi Jonathan,

I think this is a big improvement.  Its much easier for a first time
reader to get oriented.  I have several minor suggestions inline.

On 6/20/06, Jonathan Rosenberg <jdrosen@cisco.com> wrote:
> So, its clear from the various comments on ICE-08 that ICE is still too
> hard to understand. One of the problems, it seems, is that it requires
> multiple passes to understand. One has to more or less get it in order
> to make any sense at all of the terminology section. The overview
> section is also really terse and doesn't explain enough of the core
> concepts.
>
> So, I've taken a stab at substantially increasing the content in the
> overview section, which would then be moved prior to the terminology
> section as suggested. I'll be submitting ice-09 probably monday morning
> at 859am, so I figured I'd float the proposed text to get comments. I'm
> particularly looking for input on whether this tutorial is
> understandable starting only with a very high levle understanding of
> STUN and the problem to be solved (nat traversal for media).
>
> Comments welcome:
>
> <section title="Overview of ICE">
>
> <t> A typical architecture for an ICE deployment is shown in <xref
> target="fig:ice-ref-arch"/>. The figure shows two endpoints (known
> as agents in RFC 3264 terminology)

the reader doesn't care yet that we are using RFC3264 terminology.
Since "agent" is so fundamental, I propose:

The figure shows two endpoint known as "agents", which we call...

>which we call L and R (for left and
> right, which helps visualize call flows). Both L and R are behind a
> NAT. The type of NAT and its properties are unknown. Indeed, it is not
> known whether the agent is behind a NAT at all, or whether there are
> multiple NATs between it and the network. Agents A and B
> are capable of engaging in an offer/answer exchange <xref
> target="RFC3264"/> by which they can exchange SDP messages, whose
> purpose is to set up a media session between A and B. Of course, the
> offer/answer exchange itself must be capable of traversing the
> NAT. Such traversal is facilitated through signaling elements such as
> SIP servers, and is outside the scope of this specification. Different
> solutions are applied for traversal of the signaling that carries the
> offer/answer exchange, and for the media set up by that offer/answer
> exchange. This is because of the vastly different requirements on
> latency, packet loss, and overall bandwidth between the signaling and
> media. For example, usage of a signaling intermediary, such as a SIP
> proxy, as a relay for all signaling at all times, is acceptable,
> whereas usage of relays at all times for media is highly undesirable.
> </t>

Is there a reason to use both A/B and L/R?  I would stick with just one.

> <t>
> In addition to the agents, a SIP server and NATs, ICE is typically
> used in concert with STUN servers in the network. Each agent can have
> its own STUN server, or they can be the same.
> </t>
>
> <figure anchor="fig:ice-ref-arch"><artwork>
> <![CDATA[
>
>                             +-------+
>                             | SIP   |
>          +-------+          | Srvr  |          +-------+
>          | STUN  |          |       |          | STUN  |
>          | Srvr  |          +-------+          | Srvr  |
>          |       |                             |       |
>          +-------+                             +-------+
>
>
>
>
>
>
>
>              +--------+                   +--------+
>              |  NAT   |                   |  NAT   |
>              +--------+                   +--------+
>
>
>
>          +-------+                             +-------+
>          | Agent |                             | Agent |
>          |   L   |                             |   R   |
>          |       |                             |       |
>          +-------+                             +-------+
> ]]></artwork></figure>
>
>
> <t>
> Prior to initiating an offer, the offering agent (L in this example)
> starts by performing a process known as address gathering. This
> process allows the client to obtain one or more transport addresses,
> one

one or more of which...

> more of which might be viable addresses at which the agent can
> receive incoming media packets from the other agent, which we call its
> peer. A transport address is just the combination of an IP address and
> port.

and IP address family?

>With ICE, an agent will actually provide its peer with all of
> its possible transport addresses, and ICE will figure out which one to
> actually use.
> </t>
> <t>
> Naturally, one viable transport address is one obtained directly from
> a local interface the client has towards the network. Such a transport
> address is called a local transport address. The local interface could
> be one on a local layer 2 network technology, such as ethernet or
> WiFi, or it could be one that is obtained through a tunnel mechanism,
> such as a Virtual Private Network (VPN) or Mobile IP (MIP). In all
> cases, these appear to the agent as a local interface from which ports
> (and thus transport addresses) can be allocated.
> </t>
>
> <t> If an agent is multihomed, it can obtain a transport address from
> each interface. Depending on the location of the peer on the IP
> network, the agent may be reachable through one of those interfaces,
> or through another. Consider, for example, an agent which has a local
> interface to a private net 10 network, and also to the public
> Internet. A transport address from the net10 interface will be
> directly reachable when communicating with a peer on the same private
> net 10 network, while a transport address from the public interface
> will be directly reachable when communicating with a peer on the
> public Internet. Rather than trying to guess which interface will work
> prior to sending an offer, the offering agent includes both transport
> addresses in its offer.
> </t>
>
> <t>
> Indeed, when using a media technology like the Real Time Transport
> Protocol (RTP), an agent needs two transport addresses on each
> interface - one for the RTP, and one for the Real Time Control
> Protocol (RTCP). Other media technologies may require a multiplicity
> of transport addresses to be used and treated as a bundle. Each of
> these transport addresses is called a component. There are two
> components in an RTP stream - the RTP itself, and the RTCP. In ICE, the
> set of transport addresses that represent an atomic grouping on which
> communications is possible is called a candidate. In the example so
> far, the agent would obtain two candidates - one from the net 10
> interface, and one from the interface on the public Internet. Each
> candidate would contain two transport addresses, corresponding to each
> of the two components.
> </t>
>
> <t> Once the agent has obtained local transport addresses, it uses
> STUN to obtain additional transport addresses. To do this, it would
> send a STUN Binding Request, using the Binding Discovery Usage <xref
> target="I-D.ietf-behave-rfc3489bis"/> or the Relay Usage <xref
> target="I-D.ietf-behave-turn"/> from a local transport address, to its
> STUN server. It is assumed that the address of the STUN server is
> configured, or learned in some way. Indeed, an agent might even have
> multiple STUN servers. As a consequence of communicating with the STUN
> server, the agent can learn potentially two new types of transport
> addresses - server reflexive transport addresses and relayed transport
> addresses. The relationship of these addresses to the local transport
> address is shown in <xref target="fig:address-types"/>.
> </t>
>
> <figure anchor="fig:address-types"><artwork>
> <![CDATA[
>                To Internet
>
>                    |
>                    |
>                    |  /------------  Relayed
>                    | /               Address
>                +--------+
>                |        |
>                |  STUN  |
>                | Server |
>                |        |
>                +--------+
>                    |
>                    |
>                    | /------------  Server
>                    |/               Reflexive
>              +------------+         Address
>              |    NAT     |
>              +------------+
>                    |
>                    | /------------  Local
>                    |/               Address
>                +--------+
>                |        |
>                | Agent  |
>                |        |
>                +--------+
> ]]></artwork></figure>
>
> <t>
> The local transport address is resident on the agent itself. Through
> either the Binding Discovery Usage or the Relay Usage, the agent can
> discover its server reflexive transport address. This is the address on the
> public side of the NAT, facing the STUN server. It is the transport
> address allocated to the agent on the public side of the NAT as a
> consequence of the transmission of the STUN request through the NAT,
> to the STUN server. The NAT will allocate a binding, mapping this
> server reflexive transport address to the local transport address. Packets
> received at the NAT, targeted towards the server reflexive transport
> address,
> will have their destination address rewritten to the local transport
> address by the NAT, and then be forwarded to the agent. When there are
> multiple NATs between the agent and the STUN server, the STUN request
> will create a binding on each NAT, but only the outermost server reflexive
> transport address will be discovered by the agent.
> </t>
>
> <t>
> In addition, through the Relay Usage, the agent can request that the
> STUN server itself allocate a transport address from one of its local
> interfaces, and establish a binding that maps that transport address
> (called a relayed transport address, naturally) towards the source
> transport address of the STUN request, which will actually be equal to the
> server reflexive transport address allocated by the outermost
> NAT. Consequently, packets sent to the relayed transport address will
> be routed by the IP network towards the STUN server. The STUN server
> will receive them, rewrite the destination address to be equal to the
> server reflexive transport address, and forward them. They will then arrive
> at the NAT, where the destination address is rewritten once again, and
> the packet forward finally to the agent at its local address.
> </t>
>
> <t>
> Since the server reflexive transport addresses and relayed transport
> addresses and obtained from a local transport address, they are said
> to be derived transport addresses, since they are derived from (and
> ultimately map to) their associated local transport address. During
> the process of address gathering, the agent will obtain as many
> transport addresses of a given type as are needed for the media
> session. For example, with RTP, two transport addresses are needed for
> a candidate. The agent will obtain two server reflexive transport
> addresses (each derived from a local transport address), and they
> would be used to constitute a server reflexive candidate. The local
> transport addresses make up a local candidate, and the relayed
> transport addresses make up a relayed candidate.
> </t>
>
> <figure anchor="fig:cand-relations"><artwork>
> <![CDATA[
>
>
>             Server                         Server
>            Reflexive                      Reflexive
>            Candidate                      Candidate
>          ..............                 ..............
>          .            .                 .            .
>          .  +-+  +-+  .                 .  +-+  +-+  .
>          .  | |  | |  .                 .  | |  | |  .
>          .  +-+  +-+  .                 .  +-+  +-+  .
>          .   ^    ^   .                 .   ^    ^   .
>          ....|....|....                 ....|....|....
>              |    |                         |    |
>              |    |                         |    |
>          ....|....|....                 ....|....|....
>          .   |    |   .                 .   |    |   .
>          .  +-+  +-+  .   Local         .  +-+  +-+  .   Local
>          .  | |  | |  . Candidate       .  | |  | |  . Candidate
>          .  +-+  +-+  .                 .  +-+  +-+  .
>          .   |    |   .                 .   |    |   .
>          ....|....|....                 ....|....|....
>              |    |                         |    |
>              |    |                         |    |
>          ....|....|....                 ....|....|....
>          .   V    V   .                 .   V    V   .
>          .  +-+  +-+  .                 .  +-+  +-+  .
>          .  | |  | |  .                 .  | |  | |  .
>          .  +-+  +-+  .                 .  +-+  +-+  .
>          .            .                 .            .
>          ..............                 ..............
>             Relayed                        Relayed
>            Candidate                      Candidate
>
>
>                                 Legend
>                                 ------
>
>                          +-+
>                          | | Transport Address
>                          +-+
>
>                         ---> Derived From
>
>                          ...
>                          . . Candidate
>                          ...
>
> ]]></artwork></figure>
>
>
> <t>
> The relationship between these various transport addresses and
> candidates is shown pictorially in <xref
> target="fig:cand-relations"/>. The figure shows our example agent with
> two local interfaces, each of which provides two transport address
> pairs to make up two candidates. From those two local candidates, a
> server reflexive and relayed candidate are derived.
> </t>

I don't think this diagram or the paragraph immediately after it add
to the explanation before them.  I would remove them.

> <t>
> Once the agent has completed gathering its candidates, it assigns each
> a candidate identifier, called the candidate ID.

"it assigns each a candidate ID".

The candidate ID is a
> random number used to uniquely identify each candidate, and is used in
> the connectivity checks discussed below. The components of each
> candidate are ordered numerically, starting at one, such that each
> transport address has a component ID. For example, in an RTP candidate
> there are two components, component ID 1 and component ID 2. Each
> transport address pair is therefore uniquely identified by a
> combination of its candidate ID and its component ID. The combination
> of the two is called, unsurprisingly, a transport address ID, or tid
> for short.
> </t>
>
> <t>
> The agent will place all of its candidates in an offer, using a new
> SDP attribute called the candidate attribute. This attribute contains
> the actual transport address, the candidate ID and component ID, and a
> q-value. The q-value is used for the agent to prioritize its
> candidates. An agent will typically prefer to receive media at
> particular candidates over other candidates, based on local
> policy. For example, an agent would normally prefer to receive
> interactive voice RTP packets at its local candidate as opposed to its
> relayed candidate, due to the extra latency incurred by traveling
> through the relay.
> </t>
>
> <t>
> Finally, the agent chooses one of its candidates for inclusion in the
> m and c lines (called the m/c-line collectively). Assuming that
> candidate is verified as functional by the ICE connectivity checks
> described below, this is the actual IP address and port to which media
> will be sent. The candidate selected for inclusion in the m/c-line of
> an offer (or an answer) is called the active candidate, since it is
> the one that is the active destination for receipt of media traffic.
> </t>
>
> <t>
> Once the active candidate is chosen, the agent sends the
> offer. Through the wonders or SIP or other signaling protocols, this
> offer is delivered to the peer, which must now select its answer. To
> create the answer, the agent starts by gathering addresses, in exactly
> the same way the offered did. It includes those as candidates in its
> answer, and selects one as the active candidate, just like the offered
> did. It then sends the answer.
> </t>
>
> <t>
> Each agent then pairs up each of its candidates with the candidates of
> its peer. From the perspective of the offerer, the set of candidates
> it sent in its offer are called its native candidates, and the ones
> received in the answer are the remote candidates. Similarly, from the
> perspective of the answerer, the set of candidates it sent in its
> answer are the native candidates, and the ones received in the offer
> are the remote candidates. Both agents pair up each of their native
> candidates with each of the remote candidates, producing a set of
> candidate pairs. If there were N native candidates and M remote
> candidates, there will be N*M candidate pairs.

suggest a paragraph break here:

>Within each candidate
> pair, the transport addresses themselves are paired up one for one,
> resulting in transport address pairs as well. The transport addresses
> are paired up such that they have identical component IDs. Each
> transport address pair has an ID, called the transport address pair
> ID, formed by concatenating the tids of its two transport addresses.
> </t>

At this point, I think an example would be very useful.  How about
something like this:

</t>
For example, assume Agent A has three candidates: abcd, hijk, and
lmno, each with 2 components (one for RTP and one for RTCP), and Agent
B has two candidates: stuv and wxyz, each with 2 components (one for
RTP and one for RTCP). This yields a total of 6 candidate pairs, and
12 transport address pairs:
</t>
<figure><artwork>
  RTP pairs     RTCP pairs
abcd1:stuv1   abcd2:stuv2
abcd1:wxyz1   abcd2:wxyz2
hijk1:stuv1   hijk2:stuv2
hijk1:wxyz1   hijk2:wxyz2
lmno1:stuv1   lmno2:stuv2
lmno1:wxyz1   lmno2:wxyz2
</artwork></figure>


> <t>
> Once the pairing is done, the transport address pairs are ordered in
> such a way that both the offerer and answerer will end up with the
> same order. This ordering is done by using the q-values each side
> provided, along with the candidate IDs to help break ties. Then, each
> side begins a process known as connectivity checks. Connectivity
> checks are STUN transactions, using the connectivity check usage of
> STUN, sent from the native transport address to the remote
> transport address of a particular transport address pair.

new paragraph

> If an agent
> sends a STUN request and gets a successful response, the transport
> address pair is said to be Receive Valid, or Recv Valid for short,
> since the agent knows that its peer was able to receive a packet. If
> an agent receives a request and sends a response, the transport
> address pair is said to be Send Valid, since the agent knows that its
> peer was able to send it a packet. When transactions in both
> directions complete, the transport address pair is said to be
> Valid. The idea behind ICE is that if a transport address pair is
> valid, it means that agents were able to succesfully exchange IP
> packets in both directions. Consequently, any media packets, which are
> sent to and from exactly the same IP addresses and ports, should also
> work, since they don't differ in their IP addresses or ports.
> </t>
>
> <t>
> Since there can be quite a few transport address pairs to check,
> performing all of the connectivity checks in parallel can cause
> substantial load on the network. Instead, each agent will start at the
> top of the ordered list they each created, and every 50ms, begin a new
> connectivity check.
> </t>
>
> <t>
> In order to succesfully process a STUN connectivity check, an agent
> must be able to correlate the STUN request or response with the
> transport address pair whose connectivity the STUN message is meant to
> validate. To perform this correlation, the STUN connectivity checks
> contain a USERNAME attribute formed in a special way. In particular,
> the USERNAME contains the actual transport address pair ID, which, as
> described above, is formed by concatenating the tids of each of the
> candidates. The USERNAME is used in conjunction with an authentication
> and message integrity operation on the STUN message that requires a
> password. This
> password is conveyed in the offer/answer exchange, and is a random
> number valid only for the duration of the media session. This ensures
> that, if the signaling channel carrying the offer/answer
> exchange is secure, the agent can be certain that its STUN
> connectivity checks are taking place with the agent which responded to
> the signaling.
> </t>
>
> <t>
> Because each agent is receiving STUN requests on the same IP address
> and port that media will later be sent to, each agent is effectively
> acting as its own mini STUN server, implementing the connectivity
> check usage described in <xref
> target="I-D.ietf-behave-rfc3489bis"/>. Like all STUN servers, when the
> agent sends a STUN response to a request, the response includes the
> MAPPED-ADDRESS attribute that contains the source IP address and port
> that the request came from. In certain deployment scenarios, and in
> particular where one of the agents is behind a NAT whose address and
> port mapping properties are address and port dependent, this source IP
> address and port may differ from the server reflexive ones allocated
> by the peer during the address gathering phase. This source IP address
> and port, conveyed in the MAPPED-ADDRESS attribute of the STUN
> response, therefore constitutes a new transport address, called a peer
> reflexive transport address, which can be used for communications.
> </t>

I recommend moving the peer reflexive transport address discussion to
fall after the rest of the normal cases are described.

> <figure anchor="fig:peer-example"><artwork>
> <![CDATA[
>                                     +-------+
>                                     | STUN  |
>                                     | Srvr  |
>                                     |       |
>                                     +-------+
>                                          ^
>                                          |
>                                          |
>                                          |
>                                          |
>            +--------------------------+  |
>            |                     NAT-2|  |NAT-1
>            |                      +-----------+
>            |                      |  APD NAT  |
>            |                      +-----------+
>            |                          |  |
>            |                           \ |
>            VL1                          \|R1
>        +-------+                    +-------+
>        | Agent |                    | Agent |
>        |   L   |                    |   R   |
>        |       |                    |       |
>        +-------+                    +-------+
> ]]></artwork></figure>
>
> <t>
> Consider the example of <xref target="fig:peer-example"/>. The agent
> on the left, agent L, has a single interface and is not behind a
> NAT. Consequently, it ends up with a single candidate with a single
> transport address (normally two for RTP, but we'll consider just one
> for ease of explanation), transport address L1. It sends an offer to
> agent R, which is behind one of these Address and Port Dependent (APD)
> mapping NATs. Agent R has a local transport address R1, and obtains a
> server reflexive transport address from its STUN server, transport
> address NAT-1. Now, when agent R sends a connectivity check from its
> local transport address (R1) to L's local transport address (L1), this
> check will traverse the NAT. The connectivity check itself will create
> a new mapping in the NAT and be allocated a new binding on the NAT -
> NAT-2. This STUN request arrives at L, which generates a STUN response
> containing transport address NAT-2. Agent R, noticing that this is not
> the same as its other two transport addresses, treats this as a new
> peer reflexive transport address.
> </t>
>
> <t>
> This new peer reflexive transport address is paired up with the remote
> transport address containing the STUN server from which that transport
> address was learned (transport address L1 in the example above). This
> becomes a new transport address pair, and connectivity checks are run
> on it as well.
> </t>
>
> <t>
> Once all of the transport address pairs in a candidate pair have been
> validated, that candidate pair is ready to be used. Media starts being
> sent on it immediately, and the offerer will send an updated offer,
> now containing the agents half of the validated candidate pair in the
> m/c-line.

propose replacing this with:
Once all of the transport address pairs in a candidate pair have been
validated, that candidate pair is ready to be used. The Agent can
start sending media over the highest priority, valid candidate pair.
If the candidate pair being used is different than the active pair,
the offerer sends an updated offer with the newly selected candidate
pair in the m/c-line.

This is called "promoting a candidate to active". The
> updated offer only contains a single candidate attribute - the one for
> the active candidate.

I would move the peer reflexive discussion here, possibly as a subsection

This next paragraph is a pretty advanced detail.  I'm not sure this
needs to be mentioned in the Overview at all.
>It also contains an attribute, called the
> remote-candidate attribute, which tells the answerer the remote
> candidate in the
> validated candidate pair. The answerer uses this attribute, along with
> its own view on the states of the candidate pairs, to place a
> candidate in the m/c-line and populate the candidate attributes in its
> answer.
> </t>
>
> <t> It is important to understand that, when ICE is in use, media is
> not sent to a candidate without validation, even if that candidate
> appears in the m/c-line. This is in order to avoid denial-of-service
> attacks. In particular, without ICE, an offerer can send an offer to
> another agent, and list the IP address and port of a target in the
> offer. If the agent is an automata that answers a call automatically,
> it will do so and then proceed to send media to the target. This
> provides substantial packet amplifications. ICE fixes this by
> requiring that an agent never send media packets unless it has sent a
> STUN message towards the target of the RTP packets, and received a
> reply from that target <xref target="sec:send-media"/>. </t>
>
>
> <t>
> A summary of this overall behavior is shown in the basic call flow in
> <xref target="fig:ice-model"/>.
> </t>
>
>
> <figure anchor="fig:ice-model"><artwork>
> <![CDATA[
>         Agent A              STUN Servers          Agent B
>            |(1) Gather Addresses |                     |
>            |-------------------->|                     |
>            |(2) Offer            |                     |
>            |------------------------------------------>|
>            |                     |(3) Gather Addresses |
>            |                     |<--------------------|
>            |(4) Answer           |                     |
>            |<------------------------------------------|
>            |(5) STUN Check       |                     |
>            |<------------------------------------------|
>            |(6) STUN Check       |                     |
>            |------------------------------------------>|
>            |(7) Media            |                     |
>            |<------------------------------------------|
>            |(8) Media            |                     |
>            |------------------------------------------>|
>            |(9) Offer            |                     |
>            |------------------------------------------>|
>            |(10) Answer          |                     |
>            |<------------------------------------------|
>
> ]]></artwork></figure>
> </section>

The diagram also illustrates my concern with using the term Answer in
(4).  After an unreliable 18x, you can do STUN checks and send media,
but you can't send a new Offer (9) until the real answer  sent in the
200 is acknowledged with an ACK.  If we are sloppy on this point, we
will have non-interoperable ICE implementations.

thanks,
-rohan

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



From mmusic-bounces@ietf.org Sat Jun 24 19:02:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FuH9L-0004Gg-5Y; Sat, 24 Jun 2006 19:02:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FuH9K-0004Gb-8q
	for mmusic@ietf.org; Sat, 24 Jun 2006 19:02:46 -0400
Received: from pne-smtpout1-sn2.hy.skanova.net ([81.228.8.83])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FuH9I-0005hc-7b
	for mmusic@ietf.org; Sat, 24 Jun 2006 19:02:46 -0400
Received: from my (213.64.228.153) by pne-smtpout1-sn2.hy.skanova.net
	(7.2.072.1) id 449A7EFE00065EBC; Sun, 25 Jun 2006 01:02:39 +0200
From: "Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se>
To: "Colin Perkins" <csp@csperkins.org>, "Cullen Jennings" <fluffy@cisco.com>,
	<arnoud@annies.nl>
Subject: SV: [MMUSIC] Re: ietf-mmusic-sdp-media-content-03
Date: Sun, 25 Jun 2006 01:00:44 +0200
Message-ID: <NEEHLBJFCFOHFBNEOLMJAEKMCCAA.gunnar.hellstrom@omnitor.se>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
In-reply-to: <AE07A18A-F9DE-4961-A9ED-FDDB37CB43B2@cisco.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: Quoted-Printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8353da2fde044920180672209f5bf8a0
Cc: IETF MMUSIC WG <mmusic@ietf.org>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, degodefroi@gmail.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

Hi,

You want a more stringent text for the "txp" parameter.

The current one in -03 is:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

   txp: This indicates that the media stream is originated from a
      textphone, and it requires special behavior from the receiving
      application.  A typical use case for this is a connection where
      one endpoint is an analog textphone of a kind that cannot handle
      two-way simultaneous text communication, and the other one is a
      native IP based real time text capable terminal.  The human users
      normally need to apply formal turn-taking habits, and need to
      figure out to what extent it is possible to interrupt the other
      party if the need arises.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I looked back into the earlier discussion. I had a proposed line about
that the application should give an indication to the user. That was dele=
ted
with the motivation that application actions should not be documented in
this draft.
However, I see no other use of the "txp" parameter ( and also the
"user-floor" parameter ) than to convey it clearly to the user because it
requires different behaviour from the user.

So, I suggest to modify the wording to clearly indicate that "txp" is onl=
y
sent from a party knowing that its real-time text presentation capability=
 is
limited.

And I suggest to enter a few words of the intended usage of the parameter=
=2E
This is new text proposal:


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
   txp: This indicates that the media stream is originated from a
      textphone that is incapable of handling simultaneous
      two-way communication. This limitation requires special behavior
      from the user of a terminal receiving the indication. The
      indication should be used for an indication in the user interface.

      A typical use case is a connection where one endpoint
      is an analog textphone of a kind that cannot handle two-way
      simultaneous text communication, and the other one is a native
      IP based real time text capable terminal.  The human user
      need to change behaviour when this indication is received, and
      apply formal turn-taking habits. They may also need to figure
      out to what extent it is possible to interrupt the other
      party if the need arises.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

The earlier discussion indicated that there are too many variations in
capability to handle simultaneity and two-way communication in legacy
textphones for it to be realistic to give detailed info with txp
subparameters. So, I prefer to just indicate "txp" for all.

I would appreciate very much to get comments on the procedures described
below in proposed V.151 Annex D2 as well.

Regards
Gunnar


-----Ursprungligt meddelande-----
Fr=E5n: Cullen Jennings [mailto:fluffy@cisco.com]
Skickat: den 24 juni 2006 21:56
Till: Colin Perkins
Kopia: Gunnar Hellstrom; Jani Hautakorpi (JO/LMF); IETF MMUSIC WG;
degodefroi@gmail.com; Gonzalo Camarillo
=C4mne: Re: [MMUSIC] Re: ietf-mmusic-sdp-media-content-03



Ok, I just entered proper comments in tracker, bit more inline here.

On Jun 20, 2006, at 3:29 PM, Colin Perkins wrote:

> Hi,
>
> Just following up on this... did we ever get agreement on the right
> way to proceed? If an updated draft is needed, I'd like to get it
> in before the deadline. Cullen? Jani?
>
> Colin
>
>
>
>
> On 18 May 2006, at 22:25, Gunnar Hellstrom wrote:
>> Hi,
>> I agree that the content parameters "txp" and "user-floor"
>> indicate similar functionality.
>>
>> But I see nothing wrong in having them both in the specification
>> anyway.

I've no problem with one, both, or three but it needs to be clear
what implementers need to do.

>>
>> The txp parameter value may be used to invoke some automated
>> mechanism in a text capable gateway to support conversion between
>> full duplex simultaneous multimedia communication and half-duplex
>> turn-taking, alternating text - voice communication in PSTN. But
>> it can also be used just as a warning to the IP user to be aware
>> of possible limitations in simultanity and duplex use of media.
>>
>> We could go deeper in specifying exactly what limitations are
>> valid at each moment, but I doubt that any manufacturer want to
>> refine their gateway designs to that degree.
>> If we want to go deeper, we could use the following parameters:
>>
>> -    voice-text-alternating    ( in fact influencing two media )
>>
>> -    half-duplex                  ( when strictly only one
>> direction at a time can be used )
>>
>> -    half-duplex-interruptable  ( when only one direction at a
>> time should be used for contents, but it is possible to send an
>> indication that the other party want the turn. )
>>
>>
>> I think that txp is enough.
>>
>> I just participate in a discussion where we have tried to meet
>> requirements to keep gateway resources low by allowing it to set
>> up a real-time text connection between a PSTN gateway and an IP
>> terminal only when there are indications that text will be used.
>> It is a compromise that may be needed in reality.

I agree this is needed - just want it to be clear.

>>
>> In the draft document from that discussion, we use both the
>> a=3Dcontent:txp parameter, and the following parmeters from RFC 3840
>> and 3841.
>>
>> Contact: duplex=3D"half",
>>
>> Contact: <uri>;text
>>
>> Accept-Contact: *;text;require
>>
>> Accept-Contact: *;text

It seems like the 3840 style stuff may be the way you want to signal
this.


>>
>>
>> I would appreciate very much to get comments on the parameter
>> values and logic we have drafted.
>>
>> ----------------------Proposed alternative to ITU-T V.151 Annex D,
>> using caller and callee capabilities and preferences and media-
>> contents to control gateway - IP text capable terminal
>> communication--------------------------------------------------------
>> ----------------
>>
>> Alternative proposal for V.151 Annex D.
>> ANNEX D2
>>
>> Interworking IP Text Devices with V.151 Gateways.
>> Connect text channel when usage of real-time text is likely.
>>
>>
>>
>> D.1 Introduction
>> Some non-Gateway IP devices in the network not having a means of
>> modulating or demodulating PSTN textphone signals, such as IVR
>> systems, voicemail systems, IP phones, Multimedia telephones or
>> other devices, may support the transmission of real-time text over
>> IP networks and, ideally, interwork with V.151-compliant Gateways
>> in order to provide a means through which users of PSTN textphone
>> devices can communicate with those IP devices.  This class of
>> devices is referred to herein as an "IP Text Device=94 (ITD).  This
>> Annex defines the procedures that may be used in order to allow
>> for such interworking between V.151 Gateways and ITDs. The main
>> principle is to use RFC 4103 as the default text transport method
>> between gateways and ITD:s, and open text channels only when it is
>> likely that the text channel will be used.
>>
>> D.2 Exchanging capabilities and opening media streams
>> When establishing a call, an ITD may advertise support for real-
>> time text  in accordance with IETF RFC 4103.
>>
>> In general, ITDs also transmit text characters when communicating
>> with other ITDs using RFC 4103, which specifies the establishment
>> of a separate RTP stream specifically for transmitting text
>> characters.  However, since V.151 PSTN gateway devices interleave
>> audio and text data when used for Gateway - to - gateway
>> operation, V.151 gateways need to support both RFC 4103 to
>> interwork with ITDs and RFC 4351 for communicating with other PSTN
>> gateways.
>>
>> As such, V.151 gateways are Recommended to indicate support for
>> both transport methods initially when exchanging capability
>> information. However, relatively few calls use real-time text in
>> the PSTN, and therefore it may be desirable for the gateway to not
>> open the text channel until either party in the call explicitly
>> acts to use real-time text.
>>
>> According to normal procedures in IP multimedia systems, it is
>> allowable to indicate capability for other transport protocols for
>> real-time text as well as RFC 4103 and connect such alternatives.
>>
>> ----
>>
>> D.2.2    SDP based systems
>> Similar logic follows for SDP-based systems.
>>
>> In SIP-based systems, the terminal and gateway shall announce
>> support for text in the Contact field according to RFC 3840, and
>> may indicate preference for text according to RFC 3841.
>>
>> Contact: <uri>;text
>>
>> A calling SIP terminal who does not put priority to text may
>> indicate an interest to use text by:
>>
>> Accept-Contact: *;text
>>
>> A calling SIP terminal who want to put priority to establishing a
>> text connection shall indicate that by:
>>
>> Accept-Contact: *;text;require
>>
>> Most commonly, PSTN text telephones support alternating text and
>> audio during the call, but not simultaneous text and audio. If the
>> gateway only supports alternating text and audio during the PSTN
>> text session, it may be beneficial to make the ITD user aware of
>> this limitation. It is proposed to use the Duplex parameter of RFC
>> 3840 for this purpose.
>>
>> Contact: duplex=3D"half"
>>
>> There is a parameter also for use in the text media description:
>>
>> a=3Dcontent:txp
>>
>> It should be used to indicate to the ITD user that the text
>> channel is half duplex and turn-taking habits should be used.
>>
>>
>>
>> Note that while the use of RFC 2198 redundancy or other fault
>> tolerance scheme is not shown in the abbreviated examples below,
>> appropriate mechanisms should be employed to protect the
>> transmission of the text stream in accordance with the text
>> transport specifications.
>>
>>
>>
>> D.2.2.1 Call from PSTN
>> Consider the following abbreviated example SDP that might be found
>> in an offer sent by a V.151 Gateway not offering RFC 4103 support
>> initially, but indicating text support and that the text support
>> is alternating with audio:
>>
>>       Contact: <uri>;text;duplex=3D"half"
>>
>>        m=3Daudio 7200 RTP/AVP 0 98
>>
>>        a=3Drtpmap:98 t140c/8000
>>
>>        a=3Dfmtp:98 cps=3D20
>>
>> If the gateway at that time already knows that text will be needed
>> in the call, a requirement for text shall be included, and a media
>> line for text. The decision to include text when offering the call
>> may be because textphone tones have already been detected on the
>> PSTN line, the gateway may be configured to be a dedicated text
>> gateway, or it may be known by subscription or any other external
>> means that either user has preference for text.
>>
>>       Accept-Contact: *;text;require
>>
>>       Contact: <uri>;text;duplex=3D"half"
>>
>>        m=3Daudio 7200 RTP/AVP 0 98
>>
>>        a=3Drtpmap:98 t140c/8000
>>
>>        a=3Dfmtp:98 cps=3D20
>>
>>        m=3Dtext 7202 RTP/AVP 99
>>
>>        a=3Drtpmap:99 t140/1000
>>
>>       a=3Dcontent:txp
>>
>>
>>
>> If the answering device is an ITD, with no specific indication
>> that text would be used,  it would accept only the G.711 audio.
>>
>>       Contact: <uri>;text
>>
>>       m=3Daudio 7200 RTP/AVP 0
>>
>>
>>
>> If the answering device is an ITD where the user has indicated a
>> preference for text, it would accept the text/t140 medium and
>> optionally G.711 audio.
>>
>>       Contact: <uri>;text
>>
>>        m=3Daudio 7200 RTP/AVP 0
>>
>>        m=3Dtext 7202 RTP/AVP 99
>>
>>        a=3Drtpmap:99 t140/1000
>>
>> Note that this response is only possible when the gateway had
>> included text/140 in the offer. For other cases, the terminal
>> needs to do a reinvite to add text to the call.
>>
>> D.2.2.2 Call from IP terminal
>> A calling ITD could give a strong indication that it requires text
>> support in the call by an INVITE according to this example:
>>
>>       Contact: <sip:terminal@host.example.com>;text
>>
>>       Accept-Contact: *;text;require
>>
>>        m=3Daudio 7200 RTP/AVP 0
>>
>>        m=3Dtext 7202 RTP/AVP 99
>>
>>        a=3Drtpmap:99 t140/1000
>>
>>
>>
>> The network would make efforts to connect to a text capable
>> gateway, that may acknowledge the text channel initially, because
>> of the indication that text is required. The gateway should also
>> start text channel connection procedures on the PSTN side.
>>
>>       Contact: <gwy-uri>;text;duplex=3D"half"
>>
>>        m=3Daudio 7200 RTP/AVP 0
>>
>>        m=3Dtext 7202 RTP/AVP 99
>>
>>        a=3Drtpmap:99 t140/1000
>>
>>        a=3Dfmtp:99 cps=3D20
>>
>>       a=3Dcontent:txp
>>
>>
>>
>> If on the other hand, the ITD user is not depending on text, but
>> want to have it available for occasional use, the ITD can be
>> configured to make its INVITE as follows:
>>
>>
>>
>>       Contact: <sip:terminal@host.example.com>;text
>>
>>       Accept-Contact: *;text
>>
>>        m=3Daudio 7200 RTP/AVP 0
>>
>>        m=3Dtext 7202 RTP/AVP 99
>>
>>        a=3Drtpmap:99 t140/1000
>>
>>        a=3Dfmtp:99
>>
>>
>>
>> The network would try to connect to a text capable gateway, but
>> may connect through a non capable. The gateway may decide to not
>> acknowledge the text channel initially, but indicates its text
>> capability in the Contact header.
>>
>>       Contact: <gwy-uri>;text;duplex=3D"half"
>>
>>        m=3Daudio 7200 RTP/AVP 0
>>
>>
>>
>> D.2.2.3 Text channel establishment during a call
>> If at a later stage in the call, either party in the call starts
>> text activity, and no text channel was set up initially, a text
>> channel should be added to the session by a REINVITE. .
>>
>> This is an example of how it would be expressed from the gateway,
>>
>>        Contact: <uri>;text;duplex=3D"half"
>>
>>        m=3Daudio 7200 RTP/AVP 0
>>
>>         m=3Dtext 7202 RTP/AVP 99
>>
>>         a=3Drtpmap:99 t140/1000
>>
>>         a=3Dfmtp:99 cps=3D20
>>
>>        a=3Dcontent:txp
>>
>> The other party should answer with a similar sdp.
>>
>>
>>
>> If instead it is the ITD user who starts text activity, a text
>> channel should be added to the session by a REINVITE from the ITD
>> according to the following example. .
>>
>>        Contact: <uri>;text
>>
>>        m=3Daudio 7200 RTP/AVP 0
>>
>>        m=3Dtext 7202 RTP/AVP 99
>>
>>        a=3Drtpmap:99 t140/1000
>>
>>        a=3Dfmtp:99 cps=3D20
>>
>>
>>
>> The gateway should answer with
>>
>>        Contact: <uri>;text;duplex=3D"half"
>>
>>        m=3Daudio 7200 RTP/AVP 0
>>
>>        m=3Dtext 7202 RTP/AVP 99
>>
>>        a=3Drtpmap:99 t140/1000
>>
>>        a=3Dfmtp:99 cps=3D20
>>
>>        a=3Dcontent:txp
>>
>> .
>>
>> The line "a=3Dcontent:txp" is sent from the gateway as an indication
>> that half duplex procedures should be applied by the users in the
>> text stream.
>>
>> D.3 Procedure for terminals including both RFC 4103 and RFC 4351
>> support
>> In the case when a terminal implements both RFC 4103 and RFC 4351
>> for text transport, the following procedures should be applied in
>> the terminal.
>>
>> When establishing a call, an ITD may advertise support for ToIP in
>> accordance with Annex B or Annex C, with one notable important
>> exception: the ITD shall not include a list of supported
>> modulations.  Absence of the list of modulations shall be used as
>> an indicator to the V.151 Gateway that the remote side is an ITD.
>>
>> Further, ITD devices shall not utilize SSEs in order to control
>> state transition to ToIP.  Rather, once a media flow is
>> established to transport T.140 characters, either the Gateway or
>> the ITD may transmit text immediately and without further
>> negotiation.  Payload type switching is used to transition between
>> AUDIO and Text Relay modes.
>>
>> D.4 State transition and text handling
>> The following description assumes that a V.151-compliant Gateway
>> is in communication with an ITD and media flows have been
>> established to transport text over IP in accordance with RFC 4103.
>>
>> When the gateway compliant to this annex detects a PSTN textphone
>> that it supports using text relay, it shall autonomously connect
>> to the textphone.  After connection on the PSTN side, the gateway
>> shall open the text channel to the ITD. It shall decode the
>> characters received and transmit those to the ITD, giving proper
>> respect to the maximum character-per-second (CPS) parameter
>> advertised by the ITD.  Determining the type of PSTN textphone
>> device in use is the responsibility of the Gateway and the ITD
>> need not concern itself with what kind of PSTN textphone device is
>> connected to the Gateway.
>>
>> Likewise, when the ITD first has characters to send to the Gateway
>> using text/140 payload type, the ITD opens the text channel if it
>> was not opened before. Then the ITD transmits the characters to
>> the Gateway. The Gateway shall perform a probing, as necessary, to
>> determine the type of PSTN device connected, if any.  While
>> probing, the Gateway shall buffer any characters received and
>> transmit those when probing completes and the gateway is connected
>> to the text phone.  The size of the character buffer is a matter
>> of implementation, but should support the reception and buffering
>> of characters for at least 60 seconds at the specified maximum
>> character-per-second (CPS) value signaled to the ITD.
>>
>> If the Gateway does not support the modulation used by the PSTN
>> textphone device, the Gateway may transmit the received textphone
>> signals via VBD or the audio stream, depending on the capabilities
>> of the ITD.  Further, the Gateway may simply discard characters
>> received from the ITD or transmit them to the PSTN textphone
>> device using a pre-provisioned modulation.
>>
>>
>> /
>>
>> Gunnar
>> ---------------------------------------------------------------------
>> --------
>> Gunnar Hellstr=F6m, Omnitor
>> gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se>
>> Mob: +46 708 204 288
>> Phone: +46 8 556 002 03
>> www.omnitor.se <http://www.omnitor.se>
>>
>>
>> -----Original Message-----
>> From: Jani Hautakorpi (JO/LMF) [mailto:jani.hautakorpi@ericsson.com]
>> Sent: Wednesday, May 17, 2006 10:12 AM
>> To: Cullen Jennings
>> Cc: gunnar.hellstrom@omnitor.se; degodefroi@gmail.com; Gonzalo
>> Camarillo; IETF MMUSIC WG
>> Subject: [MMUSIC] Re: ietf-mmusic-sdp-media-content-03
>>
>>
>> Hi Cullen,
>>
>> Cullen Jennings wrote:
>> > I was just reviewing this document and I can't figure out  the
>> > difference from user-floor and txp from the point of view
>> describing
>> > the content.
>>
>> Actually, there are no major differences between them, but Gunnar
>> Hellstrom and Arnoud van Wijk (in the cc:) really wanted a value that
>> was "txp". Gunnar and Arnoud can explain this better, but the main
>> reason is that this way they can refer to and further describe the
>> usage
>> of "txp" from some other draft, e.g. ietf-draft-sipping-toip.
>>
>> > It seems like this might be better to indicate that the
>> > content type was "simplex" as normal media is assumed to be
>> "duplex".
>>
>> This is a matter of naming. Personally I believe that "user-floor" is
>> more descriptive than "simplex", because there can also be such
>> one-way
>> media that doesn't require user level floor control. What do you
>> think?
>>
>> > I'm not sure I like what I am proposing here but I think we need to
>> > improve on the definition for these two. The current description
>> of  txt
>> > does not seem to match the requirements for it on the email
>> list  and
>> > the definition of user-floor I have no idea when to add to a
>> stream.
>>
>> I would say that "txp" is exactly what was described on the mmusic's
>> mailing list, please see the "[MMUSIC] I-D ACTION:
>> draft-ietf-mmusic-sdp-media-content-01.txt" thread, starting 18th
>> Feb.
>>
>> Regarding the addition of "user-floor" to media stream: The device
>> that
>> needs to add this value knows it by itself. For example, a new
>> walkie-talkie type of device can know that it requires user level
>> floor
>> control. But of course we can try to elaborate this on the draft,
>> if you
>> want.
>>
>> > It also might be nice to provide more guidance on what is
>> appropriate
>> > to signal with "content" and what is not. For example, I would
>> not  want
>> > people signaling the mpeg profile using this. I think what we
>> want to
>> > do here is something like signal the "semantic content" of  the
>> stream
>> > such that an application that is offered multiple streams  can
>> pick the
>> > right stream or map the streams to the users  preferences. Would
>> it be
>> > possible to add more text about what would  not be appropriate
>> to use
>> > this registry for.
>>
>> I really can't see how somebody could try to signal the mpeg profile
>> with this draft, because it just doesn't have enough features for
>> signaling such information. I feel that the possible use scenarios
>> are
>> already quite limited, and it's hard for me to invent how anybody
>> could
>> misuse this draft. But, if you (or somebody else) can come up with
>> some
>> valid, non-appropriate use cases, I'm happy to add them to the draft.
>>
>>
>> --
>> Jani
>>
>> _______________________________________________
>> 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 Sun Jun 25 05:55:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FuRL1-0006LI-Ri; Sun, 25 Jun 2006 05:55:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FuRL1-0006LD-3R
	for mmusic@ietf.org; Sun, 25 Jun 2006 05:55:31 -0400
Received: from mx1.cambrium.nl ([217.19.16.130] helo=gollum.cambrium.nl)
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FuRKy-0005Q4-S9
	for mmusic@ietf.org; Sun, 25 Jun 2006 05:55:31 -0400
Received: (qmail 26071 invoked from network); 25 Jun 2006 09:55:24 -0000
Received: from 82-197-192-189.dsl.cambrium.nl (HELO solstice) (82.197.192.189)
	by gollum.cambrium.nl with SMTP; 25 Jun 2006 09:55:24 -0000
From: "Arnoud van Wijk" <arnoud@annies.nl>
To: "'Gunnar Hellstrom'" <gunnar.hellstrom@omnitor.se>,
	"'Colin Perkins'" <csp@csperkins.org>,
	"'Cullen Jennings'" <fluffy@cisco.com>
Subject: RE: [MMUSIC] Re: ietf-mmusic-sdp-media-content-03
Date: Sun, 25 Jun 2006 11:55:32 +0200
Message-ID: <000301c6983d$80092db0$1f00a8c0@solstice>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <NEEHLBJFCFOHFBNEOLMJAEKMCCAA.gunnar.hellstrom@omnitor.se>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Thread-Index: AcaX4kv+1xe++JD+RIKEnyhdvQW+uwAWtFPg
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c25c25eef92c03b403abac6c7c688517
Cc: 'Gonzalo Camarillo' <Gonzalo.Camarillo@ericsson.com>,
	'IETF MMUSIC WG' <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

The new proposal text as suggested by Gunnar covers the usage of txp in =
the
best way.
Note: The Dutch mobile textphone platform has already implemented the
parameter txp as in the proposed text. And it works very well.

Greetz

Arnoud

Arnoud A. T. van Wijk
AnnieS New Technology
www.AnnieS.nl
Mobile textphone (SIP): arnoud@annies.nl

> -----Original Message-----
> From: Gunnar Hellstrom [mailto:gunnar.hellstrom@omnitor.se]
> Sent: zondag 25 juni 2006 1:01
> To: Colin Perkins; Cullen Jennings; arnoud@annies.nl
> Cc: Gonzalo Camarillo; degodefroi@gmail.com; IETF MMUSIC WG; Jani
> Hautakorpi (JO/LMF)
> Subject: SV: [MMUSIC] Re: ietf-mmusic-sdp-media-content-03
>=20
> Hi,
>=20
> You want a more stringent text for the "txp" parameter.
>=20
> The current one in -03 is:
>=20
> =
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>=20
>    txp: This indicates that the media stream is originated from a
>       textphone, and it requires special behavior from the receiving
>       application.  A typical use case for this is a connection where
>       one endpoint is an analog textphone of a kind that cannot handle
>       two-way simultaneous text communication, and the other one is a
>       native IP based real time text capable terminal.  The human =
users
>       normally need to apply formal turn-taking habits, and need to
>       figure out to what extent it is possible to interrupt the other
>       party if the need arises.
> =
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> I looked back into the earlier discussion. I had a proposed line about
> that the application should give an indication to the user. That was
> deleted
> with the motivation that application actions should not be documented =
in
> this draft.
> However, I see no other use of the "txp" parameter ( and also the
> "user-floor" parameter ) than to convey it clearly to the user because =
it
> requires different behaviour from the user.
>=20
> So, I suggest to modify the wording to clearly indicate that "txp" is =
only
> sent from a party knowing that its real-time text presentation =
capability
> is
> limited.
>=20
> And I suggest to enter a few words of the intended usage of the =
parameter.
> This is new text proposal:
>=20
>=20
> =
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>    txp: This indicates that the media stream is originated from a
>       textphone that is incapable of handling simultaneous
>       two-way communication. This limitation requires special behavior
>       from the user of a terminal receiving the indication. The
>       indication should be used for an indication in the user =
interface.
>=20
>       A typical use case is a connection where one endpoint
>       is an analog textphone of a kind that cannot handle two-way
>       simultaneous text communication, and the other one is a native
>       IP based real time text capable terminal.  The human user
>       need to change behaviour when this indication is received, and
>       apply formal turn-taking habits. They may also need to figure
>       out to what extent it is possible to interrupt the other
>       party if the need arises.
> =
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++=

>=20
> The earlier discussion indicated that there are too many variations in
> capability to handle simultaneity and two-way communication in legacy
> textphones for it to be realistic to give detailed info with txp
> subparameters. So, I prefer to just indicate "txp" for all.
>=20
> I would appreciate very much to get comments on the procedures =
described
> below in proposed V.151 Annex D2 as well.
>=20
> Regards
> Gunnar
>=20
>=20
> -----Ursprungligt meddelande-----
> Fr=E5n: Cullen Jennings [mailto:fluffy@cisco.com]
> Skickat: den 24 juni 2006 21:56
> Till: Colin Perkins
> Kopia: Gunnar Hellstrom; Jani Hautakorpi (JO/LMF); IETF MMUSIC WG;
> degodefroi@gmail.com; Gonzalo Camarillo
> =C4mne: Re: [MMUSIC] Re: ietf-mmusic-sdp-media-content-03
>=20
>=20
>=20
> Ok, I just entered proper comments in tracker, bit more inline here.
>=20
> On Jun 20, 2006, at 3:29 PM, Colin Perkins wrote:
>=20
> > Hi,
> >
> > Just following up on this... did we ever get agreement on the right
> > way to proceed? If an updated draft is needed, I'd like to get it
> > in before the deadline. Cullen? Jani?
> >
> > Colin
> >
> >
> >
> >
> > On 18 May 2006, at 22:25, Gunnar Hellstrom wrote:
> >> Hi,
> >> I agree that the content parameters "txp" and "user-floor"
> >> indicate similar functionality.
> >>
> >> But I see nothing wrong in having them both in the specification
> >> anyway.
>=20
> I've no problem with one, both, or three but it needs to be clear
> what implementers need to do.
>=20
> >>
> >> The txp parameter value may be used to invoke some automated
> >> mechanism in a text capable gateway to support conversion between
> >> full duplex simultaneous multimedia communication and half-duplex
> >> turn-taking, alternating text - voice communication in PSTN. But
> >> it can also be used just as a warning to the IP user to be aware
> >> of possible limitations in simultanity and duplex use of media.
> >>
> >> We could go deeper in specifying exactly what limitations are
> >> valid at each moment, but I doubt that any manufacturer want to
> >> refine their gateway designs to that degree.
> >> If we want to go deeper, we could use the following parameters:
> >>
> >> -    voice-text-alternating    ( in fact influencing two media )
> >>
> >> -    half-duplex                  ( when strictly only one
> >> direction at a time can be used )
> >>
> >> -    half-duplex-interruptable  ( when only one direction at a
> >> time should be used for contents, but it is possible to send an
> >> indication that the other party want the turn. )
> >>
> >>
> >> I think that txp is enough.
> >>
> >> I just participate in a discussion where we have tried to meet
> >> requirements to keep gateway resources low by allowing it to set
> >> up a real-time text connection between a PSTN gateway and an IP
> >> terminal only when there are indications that text will be used.
> >> It is a compromise that may be needed in reality.
>=20
> I agree this is needed - just want it to be clear.
>=20
> >>
> >> In the draft document from that discussion, we use both the
> >> a=3Dcontent:txp parameter, and the following parmeters from RFC =
3840
> >> and 3841.
> >>
> >> Contact: duplex=3D"half",
> >>
> >> Contact: <uri>;text
> >>
> >> Accept-Contact: *;text;require
> >>
> >> Accept-Contact: *;text
>=20
> It seems like the 3840 style stuff may be the way you want to signal
> this.
>=20
>=20
> >>
> >>
> >> I would appreciate very much to get comments on the parameter
> >> values and logic we have drafted.
> >>
> >> ----------------------Proposed alternative to ITU-T V.151 Annex D,
> >> using caller and callee capabilities and preferences and media-
> >> contents to control gateway - IP text capable terminal
> >> =
communication--------------------------------------------------------
> >> ----------------
> >>
> >> Alternative proposal for V.151 Annex D.
> >> ANNEX D2
> >>
> >> Interworking IP Text Devices with V.151 Gateways.
> >> Connect text channel when usage of real-time text is likely.
> >>
> >>
> >>
> >> D.1 Introduction
> >> Some non-Gateway IP devices in the network not having a means of
> >> modulating or demodulating PSTN textphone signals, such as IVR
> >> systems, voicemail systems, IP phones, Multimedia telephones or
> >> other devices, may support the transmission of real-time text over
> >> IP networks and, ideally, interwork with V.151-compliant Gateways
> >> in order to provide a means through which users of PSTN textphone
> >> devices can communicate with those IP devices.  This class of
> >> devices is referred to herein as an "IP Text Device=94 (ITD).  This
> >> Annex defines the procedures that may be used in order to allow
> >> for such interworking between V.151 Gateways and ITDs. The main
> >> principle is to use RFC 4103 as the default text transport method
> >> between gateways and ITD:s, and open text channels only when it is
> >> likely that the text channel will be used.
> >>
> >> D.2 Exchanging capabilities and opening media streams
> >> When establishing a call, an ITD may advertise support for real-
> >> time text  in accordance with IETF RFC 4103.
> >>
> >> In general, ITDs also transmit text characters when communicating
> >> with other ITDs using RFC 4103, which specifies the establishment
> >> of a separate RTP stream specifically for transmitting text
> >> characters.  However, since V.151 PSTN gateway devices interleave
> >> audio and text data when used for Gateway - to - gateway
> >> operation, V.151 gateways need to support both RFC 4103 to
> >> interwork with ITDs and RFC 4351 for communicating with other PSTN
> >> gateways.
> >>
> >> As such, V.151 gateways are Recommended to indicate support for
> >> both transport methods initially when exchanging capability
> >> information. However, relatively few calls use real-time text in
> >> the PSTN, and therefore it may be desirable for the gateway to not
> >> open the text channel until either party in the call explicitly
> >> acts to use real-time text.
> >>
> >> According to normal procedures in IP multimedia systems, it is
> >> allowable to indicate capability for other transport protocols for
> >> real-time text as well as RFC 4103 and connect such alternatives.
> >>
> >> ----
> >>
> >> D.2.2    SDP based systems
> >> Similar logic follows for SDP-based systems.
> >>
> >> In SIP-based systems, the terminal and gateway shall announce
> >> support for text in the Contact field according to RFC 3840, and
> >> may indicate preference for text according to RFC 3841.
> >>
> >> Contact: <uri>;text
> >>
> >> A calling SIP terminal who does not put priority to text may
> >> indicate an interest to use text by:
> >>
> >> Accept-Contact: *;text
> >>
> >> A calling SIP terminal who want to put priority to establishing a
> >> text connection shall indicate that by:
> >>
> >> Accept-Contact: *;text;require
> >>
> >> Most commonly, PSTN text telephones support alternating text and
> >> audio during the call, but not simultaneous text and audio. If the
> >> gateway only supports alternating text and audio during the PSTN
> >> text session, it may be beneficial to make the ITD user aware of
> >> this limitation. It is proposed to use the Duplex parameter of RFC
> >> 3840 for this purpose.
> >>
> >> Contact: duplex=3D"half"
> >>
> >> There is a parameter also for use in the text media description:
> >>
> >> a=3Dcontent:txp
> >>
> >> It should be used to indicate to the ITD user that the text
> >> channel is half duplex and turn-taking habits should be used.
> >>
> >>
> >>
> >> Note that while the use of RFC 2198 redundancy or other fault
> >> tolerance scheme is not shown in the abbreviated examples below,
> >> appropriate mechanisms should be employed to protect the
> >> transmission of the text stream in accordance with the text
> >> transport specifications.
> >>
> >>
> >>
> >> D.2.2.1 Call from PSTN
> >> Consider the following abbreviated example SDP that might be found
> >> in an offer sent by a V.151 Gateway not offering RFC 4103 support
> >> initially, but indicating text support and that the text support
> >> is alternating with audio:
> >>
> >>       Contact: <uri>;text;duplex=3D"half"
> >>
> >>        m=3Daudio 7200 RTP/AVP 0 98
> >>
> >>        a=3Drtpmap:98 t140c/8000
> >>
> >>        a=3Dfmtp:98 cps=3D20
> >>
> >> If the gateway at that time already knows that text will be needed
> >> in the call, a requirement for text shall be included, and a media
> >> line for text. The decision to include text when offering the call
> >> may be because textphone tones have already been detected on the
> >> PSTN line, the gateway may be configured to be a dedicated text
> >> gateway, or it may be known by subscription or any other external
> >> means that either user has preference for text.
> >>
> >>       Accept-Contact: *;text;require
> >>
> >>       Contact: <uri>;text;duplex=3D"half"
> >>
> >>        m=3Daudio 7200 RTP/AVP 0 98
> >>
> >>        a=3Drtpmap:98 t140c/8000
> >>
> >>        a=3Dfmtp:98 cps=3D20
> >>
> >>        m=3Dtext 7202 RTP/AVP 99
> >>
> >>        a=3Drtpmap:99 t140/1000
> >>
> >>       a=3Dcontent:txp
> >>
> >>
> >>
> >> If the answering device is an ITD, with no specific indication
> >> that text would be used,  it would accept only the G.711 audio.
> >>
> >>       Contact: <uri>;text
> >>
> >>       m=3Daudio 7200 RTP/AVP 0
> >>
> >>
> >>
> >> If the answering device is an ITD where the user has indicated a
> >> preference for text, it would accept the text/t140 medium and
> >> optionally G.711 audio.
> >>
> >>       Contact: <uri>;text
> >>
> >>        m=3Daudio 7200 RTP/AVP 0
> >>
> >>        m=3Dtext 7202 RTP/AVP 99
> >>
> >>        a=3Drtpmap:99 t140/1000
> >>
> >> Note that this response is only possible when the gateway had
> >> included text/140 in the offer. For other cases, the terminal
> >> needs to do a reinvite to add text to the call.
> >>
> >> D.2.2.2 Call from IP terminal
> >> A calling ITD could give a strong indication that it requires text
> >> support in the call by an INVITE according to this example:
> >>
> >>       Contact: <sip:terminal@host.example.com>;text
> >>
> >>       Accept-Contact: *;text;require
> >>
> >>        m=3Daudio 7200 RTP/AVP 0
> >>
> >>        m=3Dtext 7202 RTP/AVP 99
> >>
> >>        a=3Drtpmap:99 t140/1000
> >>
> >>
> >>
> >> The network would make efforts to connect to a text capable
> >> gateway, that may acknowledge the text channel initially, because
> >> of the indication that text is required. The gateway should also
> >> start text channel connection procedures on the PSTN side.
> >>
> >>       Contact: <gwy-uri>;text;duplex=3D"half"
> >>
> >>        m=3Daudio 7200 RTP/AVP 0
> >>
> >>        m=3Dtext 7202 RTP/AVP 99
> >>
> >>        a=3Drtpmap:99 t140/1000
> >>
> >>        a=3Dfmtp:99 cps=3D20
> >>
> >>       a=3Dcontent:txp
> >>
> >>
> >>
> >> If on the other hand, the ITD user is not depending on text, but
> >> want to have it available for occasional use, the ITD can be
> >> configured to make its INVITE as follows:
> >>
> >>
> >>
> >>       Contact: <sip:terminal@host.example.com>;text
> >>
> >>       Accept-Contact: *;text
> >>
> >>        m=3Daudio 7200 RTP/AVP 0
> >>
> >>        m=3Dtext 7202 RTP/AVP 99
> >>
> >>        a=3Drtpmap:99 t140/1000
> >>
> >>        a=3Dfmtp:99
> >>
> >>
> >>
> >> The network would try to connect to a text capable gateway, but
> >> may connect through a non capable. The gateway may decide to not
> >> acknowledge the text channel initially, but indicates its text
> >> capability in the Contact header.
> >>
> >>       Contact: <gwy-uri>;text;duplex=3D"half"
> >>
> >>        m=3Daudio 7200 RTP/AVP 0
> >>
> >>
> >>
> >> D.2.2.3 Text channel establishment during a call
> >> If at a later stage in the call, either party in the call starts
> >> text activity, and no text channel was set up initially, a text
> >> channel should be added to the session by a REINVITE. .
> >>
> >> This is an example of how it would be expressed from the gateway,
> >>
> >>        Contact: <uri>;text;duplex=3D"half"
> >>
> >>        m=3Daudio 7200 RTP/AVP 0
> >>
> >>         m=3Dtext 7202 RTP/AVP 99
> >>
> >>         a=3Drtpmap:99 t140/1000
> >>
> >>         a=3Dfmtp:99 cps=3D20
> >>
> >>        a=3Dcontent:txp
> >>
> >> The other party should answer with a similar sdp.
> >>
> >>
> >>
> >> If instead it is the ITD user who starts text activity, a text
> >> channel should be added to the session by a REINVITE from the ITD
> >> according to the following example. .
> >>
> >>        Contact: <uri>;text
> >>
> >>        m=3Daudio 7200 RTP/AVP 0
> >>
> >>        m=3Dtext 7202 RTP/AVP 99
> >>
> >>        a=3Drtpmap:99 t140/1000
> >>
> >>        a=3Dfmtp:99 cps=3D20
> >>
> >>
> >>
> >> The gateway should answer with
> >>
> >>        Contact: <uri>;text;duplex=3D"half"
> >>
> >>        m=3Daudio 7200 RTP/AVP 0
> >>
> >>        m=3Dtext 7202 RTP/AVP 99
> >>
> >>        a=3Drtpmap:99 t140/1000
> >>
> >>        a=3Dfmtp:99 cps=3D20
> >>
> >>        a=3Dcontent:txp
> >>
> >> .
> >>
> >> The line "a=3Dcontent:txp" is sent from the gateway as an =
indication
> >> that half duplex procedures should be applied by the users in the
> >> text stream.
> >>
> >> D.3 Procedure for terminals including both RFC 4103 and RFC 4351
> >> support
> >> In the case when a terminal implements both RFC 4103 and RFC 4351
> >> for text transport, the following procedures should be applied in
> >> the terminal.
> >>
> >> When establishing a call, an ITD may advertise support for ToIP in
> >> accordance with Annex B or Annex C, with one notable important
> >> exception: the ITD shall not include a list of supported
> >> modulations.  Absence of the list of modulations shall be used as
> >> an indicator to the V.151 Gateway that the remote side is an ITD.
> >>
> >> Further, ITD devices shall not utilize SSEs in order to control
> >> state transition to ToIP.  Rather, once a media flow is
> >> established to transport T.140 characters, either the Gateway or
> >> the ITD may transmit text immediately and without further
> >> negotiation.  Payload type switching is used to transition between
> >> AUDIO and Text Relay modes.
> >>
> >> D.4 State transition and text handling
> >> The following description assumes that a V.151-compliant Gateway
> >> is in communication with an ITD and media flows have been
> >> established to transport text over IP in accordance with RFC 4103.
> >>
> >> When the gateway compliant to this annex detects a PSTN textphone
> >> that it supports using text relay, it shall autonomously connect
> >> to the textphone.  After connection on the PSTN side, the gateway
> >> shall open the text channel to the ITD. It shall decode the
> >> characters received and transmit those to the ITD, giving proper
> >> respect to the maximum character-per-second (CPS) parameter
> >> advertised by the ITD.  Determining the type of PSTN textphone
> >> device in use is the responsibility of the Gateway and the ITD
> >> need not concern itself with what kind of PSTN textphone device is
> >> connected to the Gateway.
> >>
> >> Likewise, when the ITD first has characters to send to the Gateway
> >> using text/140 payload type, the ITD opens the text channel if it
> >> was not opened before. Then the ITD transmits the characters to
> >> the Gateway. The Gateway shall perform a probing, as necessary, to
> >> determine the type of PSTN device connected, if any.  While
> >> probing, the Gateway shall buffer any characters received and
> >> transmit those when probing completes and the gateway is connected
> >> to the text phone.  The size of the character buffer is a matter
> >> of implementation, but should support the reception and buffering
> >> of characters for at least 60 seconds at the specified maximum
> >> character-per-second (CPS) value signaled to the ITD.
> >>
> >> If the Gateway does not support the modulation used by the PSTN
> >> textphone device, the Gateway may transmit the received textphone
> >> signals via VBD or the audio stream, depending on the capabilities
> >> of the ITD.  Further, the Gateway may simply discard characters
> >> received from the ITD or transmit them to the PSTN textphone
> >> device using a pre-provisioned modulation.
> >>
> >>
> >> /
> >>
> >> Gunnar
> >> =
---------------------------------------------------------------------
> >> --------
> >> Gunnar Hellstr=F6m, Omnitor
> >> gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se>
> >> Mob: +46 708 204 288
> >> Phone: +46 8 556 002 03
> >> www.omnitor.se <http://www.omnitor.se>
> >>
> >>
> >> -----Original Message-----
> >> From: Jani Hautakorpi (JO/LMF) =
[mailto:jani.hautakorpi@ericsson.com]
> >> Sent: Wednesday, May 17, 2006 10:12 AM
> >> To: Cullen Jennings
> >> Cc: gunnar.hellstrom@omnitor.se; degodefroi@gmail.com; Gonzalo
> >> Camarillo; IETF MMUSIC WG
> >> Subject: [MMUSIC] Re: ietf-mmusic-sdp-media-content-03
> >>
> >>
> >> Hi Cullen,
> >>
> >> Cullen Jennings wrote:
> >> > I was just reviewing this document and I can't figure out  the
> >> > difference from user-floor and txp from the point of view
> >> describing
> >> > the content.
> >>
> >> Actually, there are no major differences between them, but Gunnar
> >> Hellstrom and Arnoud van Wijk (in the cc:) really wanted a value =
that
> >> was "txp". Gunnar and Arnoud can explain this better, but the main
> >> reason is that this way they can refer to and further describe the
> >> usage
> >> of "txp" from some other draft, e.g. ietf-draft-sipping-toip.
> >>
> >> > It seems like this might be better to indicate that the
> >> > content type was "simplex" as normal media is assumed to be
> >> "duplex".
> >>
> >> This is a matter of naming. Personally I believe that "user-floor" =
is
> >> more descriptive than "simplex", because there can also be such
> >> one-way
> >> media that doesn't require user level floor control. What do you
> >> think?
> >>
> >> > I'm not sure I like what I am proposing here but I think we need =
to
> >> > improve on the definition for these two. The current description
> >> of  txt
> >> > does not seem to match the requirements for it on the email
> >> list  and
> >> > the definition of user-floor I have no idea when to add to a
> >> stream.
> >>
> >> I would say that "txp" is exactly what was described on the =
mmusic's
> >> mailing list, please see the "[MMUSIC] I-D ACTION:
> >> draft-ietf-mmusic-sdp-media-content-01.txt" thread, starting 18th
> >> Feb.
> >>
> >> Regarding the addition of "user-floor" to media stream: The device
> >> that
> >> needs to add this value knows it by itself. For example, a new
> >> walkie-talkie type of device can know that it requires user level
> >> floor
> >> control. But of course we can try to elaborate this on the draft,
> >> if you
> >> want.
> >>
> >> > It also might be nice to provide more guidance on what is
> >> appropriate
> >> > to signal with "content" and what is not. For example, I would
> >> not  want
> >> > people signaling the mpeg profile using this. I think what we
> >> want to
> >> > do here is something like signal the "semantic content" of  the
> >> stream
> >> > such that an application that is offered multiple streams  can
> >> pick the
> >> > right stream or map the streams to the users  preferences. Would
> >> it be
> >> > possible to add more text about what would  not be appropriate
> >> to use
> >> > this registry for.
> >>
> >> I really can't see how somebody could try to signal the mpeg =
profile
> >> with this draft, because it just doesn't have enough features for
> >> signaling such information. I feel that the possible use scenarios
> >> are
> >> already quite limited, and it's hard for me to invent how anybody
> >> could
> >> misuse this draft. But, if you (or somebody else) can come up with
> >> some
> >> valid, non-appropriate use cases, I'm happy to add them to the =
draft.
> >>
> >>
> >> --
> >> Jani
> >>
> >> _______________________________________________
> >> 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 Sun Jun 25 13:29:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FuYQS-0002tZ-Fh; Sun, 25 Jun 2006 13:29:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FuYQR-0002tU-KG
	for mmusic@ietf.org; Sun, 25 Jun 2006 13:29:35 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FuYQQ-0003vp-BU
	for mmusic@ietf.org; Sun, 25 Jun 2006 13:29:35 -0400
Received: from sj-dkim-6.cisco.com ([171.68.10.81])
	by sj-iport-5.cisco.com with ESMTP; 25 Jun 2006 10:29:33 -0700
X-IronPort-AV: i="4.06,173,1149490800"; 
	d="scan'208"; a="300665993:sNHT33414620"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-6.cisco.com (8.12.11/8.12.11) with ESMTP id k5PHTXIC003477; 
	Sun, 25 Jun 2006 10:29:33 -0700
Received: from [192.168.1.2] (sjc-vpn2-604.cisco.com [10.21.114.92])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k5PHTZcL012195;
	Sun, 25 Jun 2006 10:29:35 -0700 (PDT)
In-Reply-To: <000301c6983d$80092db0$1f00a8c0@solstice>
References: <000301c6983d$80092db0$1f00a8c0@solstice>
Mime-Version: 1.0 (Apple Message framework v750)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <D5461380-FB6E-4215-8976-6DCDE7E58031@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [MMUSIC] Re: ietf-mmusic-sdp-media-content-03
Date: Sun, 25 Jun 2006 10:29:30 -0700
To: Arnoud van Wijk <arnoud@annies.nl>
X-Mailer: Apple Mail (2.750)
DKIM-Signature: a=rsa-sha1; q=dns; l=1378; t=1151256573; x=1152120573;
	c=relaxed/simple; s=sjdkim6001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fluffy@cisco.com;
	z=From:Cullen=20Jennings=20<fluffy@cisco.com>
	|Subject:Re=3A=20[MMUSIC]=20Re=3A=20ietf-mmusic-sdp-media-content-03;
	X=v=3Dcisco.com=3B=20h=3D1YtowmGkqHetox0+NRyJbojq1D8=3D;
	b=nWAwaoMeZ4d3ySxOsfvfdC0HkWQTF3PLU4ovxpxTUASVwNpsLrsF9dVq5ZT0f+WrmQv3qbu7
	IEwzBMx+LVbd3E/Hh0s+24VuBSvW2MV64lsYbjyhgZxfz1GGQLvYNCXW;
Authentication-Results: sj-dkim-6.cisco.com; header.From=fluffy@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: 'IETF MMUSIC WG' <mmusic@ietf.org>,
	'Gunnar Hellstrom' <gunnar.hellstrom@omnitor.se>,
	'Colin Perkins' <csp@csperkins.org>,
	'Gonzalo Camarillo' <Gonzalo.Camarillo@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


On Jun 25, 2006, at 2:55 AM, Arnoud van Wijk wrote:

>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 
>> +++++
>>    txp: This indicates that the media stream is originated from a
>>       textphone that is incapable of handling simultaneous
>>       two-way communication. This limitation requires special  
>> behavior
>>       from the user of a terminal receiving the indication. The
>>       indication should be used for an indication in the user  
>> interface.
>>
>>       A typical use case is a connection where one endpoint
>>       is an analog textphone of a kind that cannot handle two-way
>>       simultaneous text communication, and the other one is a native
>>       IP based real time text capable terminal.  The human user
>>       need to change behaviour when this indication is received, and
>>       apply formal turn-taking habits. They may also need to figure
>>       out to what extent it is possible to interrupt the other
>>       party if the need arises.
>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 
>> ++++++

Ok - if this is the best we can define it, I'm ok with that as it is.  
If there is an good document that we could provide an formational  
referfrece to that defined a textphone, that would be good but if not  
we don't have to have a reference for this.

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



From mmusic-bounces@ietf.org Sun Jun 25 14:25:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FuZIr-0002m4-Pw; Sun, 25 Jun 2006 14:25:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FuZIp-0002eK-KL
	for mmusic@ietf.org; Sun, 25 Jun 2006 14:25:47 -0400
Received: from pne-smtpout1-sn1.fre.skanova.net ([81.228.11.98])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FuZIp-00059r-4L
	for mmusic@ietf.org; Sun, 25 Jun 2006 14:25:47 -0400
Received: from my (213.64.228.153) by pne-smtpout1-sn1.fre.skanova.net
	(7.2.072.1) id 449A7BB500083678; Sun, 25 Jun 2006 20:25:40 +0200
From: "Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se>
To: "Cullen Jennings" <fluffy@cisco.com>, "Arnoud van Wijk" <arnoud@annies.nl>
Subject: SV: [MMUSIC] Re: ietf-mmusic-sdp-media-content-03
Date: Sun, 25 Jun 2006 20:23:38 +0200
Message-ID: <NEEHLBJFCFOHFBNEOLMJGEOACDAA.gunnar.hellstrom@omnitor.se>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <D5461380-FB6E-4215-8976-6DCDE7E58031@cisco.com>
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac
Cc: 'IETF MMUSIC WG' <mmusic@ietf.org>, 'Colin Perkins' <csp@csperkins.org>,
	'Gonzalo Camarillo' <Gonzalo.Camarillo@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

Cullen,

First a small addition: The "human user" mentioned in the middle of the new
text should be extended to read: "the human user of the IP terminal"

Then, you asked for references for better understanding of the limitations
in PSTN textphone protocols.

ITU-T V.18 "Modem operation in the text telephone mode."
is the traditional source. Even if it mainly deals with modem
discrimination, it also tells for each legacy type if it is half duplex or
full duplex.


But more words around what to do when converting between the legacy types
and full duplex, simultaneous real-time text and voice is found in a couple
of other documents:

ITU-T H.248.2 Facsimile, text conversation and call discrimination packages.
Describes gateway procedures between PSTN textphones and SIP.

ETSI EG 202 320 Duplex Universal Speech and Text.
Has all standardised legacy textphone methods briefly described and also SIP
real-time text and gateway procedures between them.

If you want to stay within IETF, you may refer to RFC 2805, where section
11.2.4 gives a very brief insight in the requirements for interworking with
legacy textphones with the following words:

>From RFC 2805:
"11.2.4.  Trunking/Access Gateway with text telephone access ports

   An access gateway with ports capable of text telephone communication,
   must provide communication between text telephones in the SCN and
   text conversation channels in the packet network.

   Text telephone capability of ports is assumed to be possible to
   combine with other options for calls as described in section 11.2.6
   (e.) on "Adaptable NASes".

   The port is assumed to adjust for the differences in the supported
   text telephone protocols, so that the text media stream can be
   communicated T.140 coded in the packet network without further
   transcoding [7].

   The protocol must be capable of reporting the type of text telephone
   that is connected to the SCN port. The foreseen types are the same as
   the ones supported by ITU-T V.18:  DTMF, EDT, Baudot-45, Baudot-50,
   Bell, V.21, Minitel and V.18. It should be possible to control which
   protocols are supported. The SCN port is assumed to contain ITU-T
   V.18 functionality [8].

   The protocol must be able to control the following functionality
   levels of text telephone support:

   a.   Simple text-only support: The call is set into text mode from
        the beginning of the call, in order to conduct a text-only
        conversation.

   b.   Alternating text-voice support: The call may begin in voice mode
        or text mode and, at any moment during the call, change mode on
        request by the SCN user. On the packet side, the two media
        streams for voice and text must be opened, and it must be
        possible to control the feeding of each stream by the protocol.

   c.   Simultaneous text and voice support: The call is performed in a
        mode when simultaneous text and voice streams are supported. The
        call may start in voice mode and during the call change state to
        a text-and-voice call.

   A port may implement only level a, or any level combination of a, b
   and c, always including level a.

   The protocol must support:

   d.   A text based alternative to the interactive voice response, or
        audio resource functionality of the gateway when the port is
        used in text telephone mode.



Greene, et al.               Informational                     [Page 28]

RFC 2805            MG Control Protocol Requirements          April 2000


   e.   Selection of what national translation table to be used between
        the Unicode based T.140 and the 5-7 bit based text telephone
        protocols.

   f.   Control of the V.18 probe message to be used on incoming calls.
"

Since RFC 2805 refers to V.18, I suggest that you include a reference to RFC
2805.

/ Gunnar


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







-----Ursprungligt meddelande-----
Fran: Cullen Jennings [mailto:fluffy@cisco.com]
Skickat: den 25 juni 2006 19:30
Till: Arnoud van Wijk
Kopia: 'Gunnar Hellstrom'; 'Colin Perkins'; 'Gonzalo Camarillo'; 'IETF
MMUSIC WG'; 'Jani Hautakorpi (JO/LMF)'
Amne: Re: [MMUSIC] Re: ietf-mmusic-sdp-media-content-03



On Jun 25, 2006, at 2:55 AM, Arnoud van Wijk wrote:

>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> +++++
>>    txp: This indicates that the media stream is originated from a
>>       textphone that is incapable of handling simultaneous
>>       two-way communication. This limitation requires special
>> behavior
>>       from the user of a terminal receiving the indication. The
>>       indication should be used for an indication in the user
>> interface.
>>
>>       A typical use case is a connection where one endpoint
>>       is an analog textphone of a kind that cannot handle two-way
>>       simultaneous text communication, and the other one is a native
>>       IP based real time text capable terminal.  The human user
>>       need to change behaviour when this indication is received, and
>>       apply formal turn-taking habits. They may also need to figure
>>       out to what extent it is possible to interrupt the other
>>       party if the need arises.
>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> ++++++

Ok - if this is the best we can define it, I'm ok with that as it is.
If there is an good document that we could provide an formational
referfrece to that defined a textphone, that would be good but if not
we don't have to have a reference for this.



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



From mmusic-bounces@ietf.org Sun Jun 25 21:27:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fufsi-0002wk-QY; Sun, 25 Jun 2006 21:27:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fufsh-0002wf-3U
	for mmusic@ietf.org; Sun, 25 Jun 2006 21:27:15 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fufsf-0000ha-QE
	for mmusic@ietf.org; Sun, 25 Jun 2006 21:27:15 -0400
Received: from rtp-core-2.cisco.com ([64.102.124.13])
	by rtp-iport-1.cisco.com with ESMTP; 25 Jun 2006 18:27:14 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.06,173,1149490800"; 
	d="scan'208"; a="30445287:sNHT23782328"
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 k5Q1RDno011718; 
	Sun, 25 Jun 2006 21:27:13 -0400 (EDT)
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.211);
	Sun, 25 Jun 2006 21:27:13 -0400
Received: from [192.168.1.100] ([10.86.240.30]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Sun, 25 Jun 2006 21:27:12 -0400
Message-ID: <449F37EF.8010407@cisco.com>
Date: Sun, 25 Jun 2006 21:27:11 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com>
Subject: Re: VS: [MMUSIC] ICE: Client supports, but network doesn't
References: <5EB80D22825EEE42872083AD5BFFB594017F1166@esealmw113.eemea.ericsson.se>
	<C2E6E64E-5AEB-4D18-9944-2FA9360DBD9D@magma.ca>
	<449C40CA.9030604@cisco.com>
	<5EB80D22825EEE42872083AD5BFFB594117CFE@esealmw113.eemea.ericsson.se>
In-Reply-To: <5EB80D22825EEE42872083AD5BFFB594117CFE@esealmw113.eemea.ericsson.se>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Jun 2006 01:27:12.0723 (UTC)
	FILETIME=[A68F6A30:01C698BF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
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 (JO/LMF) wrote:

> Hi,
> 
> 
>>>> 1.      What happens if the c/m lines does not correspond to
>>>> any active a=candidate line? This could happen e.g. if you have
>>>> a SDP modifying B2BUA (which doesn't support ICE) in the path.
>>>> One option would be to say that the connectivity check shall be
>>>> performed also for the c/m lines in that case, but then we may
>>>> need a "default priority", or something...
>>>> 
>>> 
>>> What properties would we assume of such a SDP-modifying B2BUA? 
>>> For example, would the a-candidate lines still be present? Would
>>> they be modified by the B2BUA? Can you cite the behavior of some
>>> known products that do this?
> 
> 
> [CHH] I would assume that one could find products behaving in either
> way. IF the B2BUA removes the candiate attributes I guess we'll get
> the scenario described in my second question.
> 
> 
>> I had the same question. Of course, the problem is that since a
>> b2bua is entirely undefined its not claer what it will do. But, I
>> think we are safe in assuming its one of two things:
>> 
>> 1. it modifies the m/c-lines but leaves the a=candidate attributes 
>> 2. it modifies the m/c-lines and removes all unknonwn attributes, 
>> including a=candidate attributes
> 
> 
> [CHH] Correct.
> 
> 
>> I suspect (2) is much more likely from SBC products, but you never
>> known.
>> 
>> Lets look at what happens in each of these cases. Case 2 is the
>> easiest. Both agents will think that the other side doesn't support
>> ICE, and fallback to regular non-ICE behavior. So, things work as
>> one would expect.
> 
> 
> [CHH] As I said in my second question, ICE does allow for the case
> where there is no candidate attribute, and from the receivers
> perspective this would be such case, wouldn't it? 

Yes.

> But, if there are
> no candidate attributes, how does the receiver know that the sender
> supports ICE? 

It won't. This is the point. In case (2), each side will conclude that 
the other doesn't support ICE.


> Is there an option tag, or someting? Or, is it assumed
> that the other ICE related attributes (ice-pwd) are still present, to
> indicate the support of ICE?

candidate attributes are the indicator. There is no option tag. There is 
no need.

> 
> 
>> In case 1, with the current specification this will break badly.
>> Because the m/c-line never appears as a candidate, the agents will
>> never send media to it since it never validates. The way to fix
>> this would be to change ice-09 to say that, if an agent doesn't see
>> a cndidate for the m/c-line, it CAN send media to it without
>> validating (kind of makes sense). Agents would also need to deal
>> with cases where they get an updated offer and they can't find a
>> matching candidate pair int he right state.
> 
> 
> [CHH] Is there a reason why the m/c-lines couldn't be used for
> validation - at least in the case when there is no matching candiate?

Yes. There are actual use cases where an endpoint cannot mux STUN and 
RTP on the same port, in which case you could elect never to try and 
validate whats currently in use on the m/c-line.

The other problem is that you need more than an IP/port to do the stun 
validations. You need usernames, passwords, and several other 
parameters. Several (like username/password) are difficult and dangerous 
to try and derive algorithmically rather than signal.

-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 Sun Jun 25 23:11:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FuhVT-0005vO-Ab; Sun, 25 Jun 2006 23:11:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FuhVS-0005vB-8X
	for mmusic@ietf.org; Sun, 25 Jun 2006 23:11:22 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FuhVS-00088e-6F
	for mmusic@ietf.org; Sun, 25 Jun 2006 23:11:22 -0400
Received: from wip-ec-wd.wipro.com ([203.91.193.32])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FuhVQ-00067F-2C
	for mmusic@ietf.org; Sun, 25 Jun 2006 23:11:22 -0400
Received: from wip-ec-wd.wipro.com (localhost.wipro.com [127.0.0.1])
	by localhost (Postfix) with ESMTP id 3D3FD2063A
	for <mmusic@ietf.org>; Mon, 26 Jun 2006 08:38:50 +0530 (IST)
Received: from blr-ec-bh01.wipro.com (blr-ec-bh01.wipro.com [10.201.50.91])
	by wip-ec-wd.wipro.com (Postfix) with ESMTP id 28471205DB
	for <mmusic@ietf.org>; Mon, 26 Jun 2006 08:38:50 +0530 (IST)
Received: from blr-m2-msg.wipro.com ([10.116.50.99]) by blr-ec-bh01.wipro.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Jun 2006 08:41:09 +0530
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C698CE.162434C5"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Mon, 26 Jun 2006 08:40:32 +0530
Message-ID: <2B82DDF2CCFC3F4185C0D51A2E0A357A4B4FD4@blr-m2-msg.wipro.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: Comments: I-D
	ACTION:draft-whitehead-mmusic-sip-for-streaming-media-01.txt 
Thread-Index: AcaWTuOx7Vd000DOTL6bfZ+qVdLLswBQzBsA
From: <ravishankar.shiroor@wipro.com>
To: <steven.d.whitehead@verizon.com>, <xavier.marjou@francetelecom.com>,
	<mmontpetit@motorola.com>, <mmusic@ietf.org>
X-OriginalArrivalTime: 26 Jun 2006 03:11:09.0931 (UTC)
	FILETIME=[2C39D3B0:01C698CE]
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a
Cc: 
Subject: [MMUSIC] Comments: I-D
	ACTION:draft-whitehead-mmusic-sip-for-streaming-media-01.txt 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C698CE.162434C5
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Steve, Xavier, Marie,

Thanks for putting together the use case analysis and recommendations.
I feel this a very important area to be pursued to make the multimedia=20
streaming services richer.

Two comments on the requirement section:

Even though it has been mentioned at many places in the draft, I think=20
it is better to spell out the requirement on the trick plays and media
control
specifically.=20

Another requirement that can be considered is to provide the server the=20
ability to Teardown a session. In a pure RTSP session, a server can not=20
TEARDOWN a session by itself (at least not gracefully according to the
protocol).

Regards,
Ravi.=20

--
=20
Ravishankar. G. Shiroor
Wipro Technologies, Bangalore.

ravishankar.shiroor@wipro.com
--

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20
Sent: Friday, June 23, 2006 4:20 AM
To: i-d-announce@ietf.org
Subject: I-D
ACTION:draft-whitehead-mmusic-sip-for-streaming-media-01.txt=20

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


	Title		: An Evaluation of Session Initiation Protocol
                          (SIP) for use in Streaming Media Applications
	Author(s)	: S. Whitehead, et al.
	Filename	:
draft-whitehead-mmusic-sip-for-streaming-media-01.txt
	Pages		: 13
	Date		: 2006-6-22
=09
This draft summarizes a set of use-cases and their associated
   requirements that suggest a convergence between the Session
   Initiation Protocol (SIP) [2] and the Real Time Streaming Protocol
   (RTSP and RTSP v2) [3] and [4] that may be beneficial for streaming
   media applications.  This benefit is especially apparent in the
   context of converged/blended media services.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-whitehead-mmusic-sip-for-strea
ming-media-01.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of
the message. =20
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-whitehead-mmusic-sip-for-streaming-media-01.txt".

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE
/internet-drafts/draft-whitehead-mmusic-sip-for-streaming-media-01.txt".
=09
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant 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.
	=09
	=09
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

------_=_NextPart_001_01C698CE.162434C5
Content-Type: application/octet-stream;
	name="ATT1232837.TXT"
Content-Transfer-Encoding: base64
Content-Description: ATT1232837.TXT
Content-Disposition: attachment;
	filename="ATT1232837.TXT"

Q29udGVudC1UeXBlOiBNZXNzYWdlL0V4dGVybmFsLWJvZHk7IGFjY2Vzcy10eXBlPSJtYWlsLXNl
cnZlciI7DQoJc2VydmVyPSJtYWlsc2VydkBpZXRmLm9yZyINCg0KQ29udGVudC1UeXBlOiB0ZXh0
L3BsYWluDQpDb250ZW50LUlEOiA8MjAwNi02LTIyMTYxNTE2LkktREBpZXRmLm9yZz4NCg0KRU5D
T0RJTkcgbWltZQ0KRklMRSAvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LXdoaXRlaGVhZC1tbXVzaWMt
c2lwLWZvci1zdHJlYW1pbmctbWVkaWEtMDEudHh0DQo=

------_=_NextPart_001_01C698CE.162434C5
Content-Type: application/octet-stream;
	name="draft-whitehead-mmusic-sip-for-streaming-media-01.URL"
Content-Transfer-Encoding: base64
Content-Description: draft-whitehead-mmusic-sip-for-streaming-media-01.URL
Content-Disposition: attachment;
	filename="draft-whitehead-mmusic-sip-for-streaming-media-01.URL"

W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0
cy9kcmFmdC13aGl0ZWhlYWQtbW11c2ljLXNpcC1mb3Itc3RyZWFtaW5nLW1lZGlhLTAxLnR4dA0K

------_=_NextPart_001_01C698CE.162434C5
Content-Type: text/plain;
	name="ATT1232838.txt"
Content-Transfer-Encoding: base64
Content-Description: ATT1232838.txt
Content-Disposition: attachment;
	filename="ATT1232838.txt"

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkktRC1Bbm5v
dW5jZSBtYWlsaW5nIGxpc3QNCkktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cxLmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vaS1kLWFubm91bmNlDQo=

------_=_NextPart_001_01C698CE.162434C5
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_001_01C698CE.162434C5--




From mmusic-bounces@ietf.org Mon Jun 26 05:32:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FunS2-0008Hp-UH; Mon, 26 Jun 2006 05:32:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FunS1-0008Hb-M2
	for mmusic@ietf.org; Mon, 26 Jun 2006 05:32:13 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FunRz-0004PZ-TB
	for mmusic@ietf.org; Mon, 26 Jun 2006 05:32:13 -0400
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	22BBB4F0042
	for <mmusic@ietf.org>; Mon, 26 Jun 2006 11:32:11 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Jun 2006 11:32:10 +0200
Received: from [147.214.30.119] ([147.214.30.119]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Jun 2006 11:32:10 +0200
Message-ID: <449FA99B.8020402@ericsson.com>
Date: Mon, 26 Jun 2006 11:32:11 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: "mmusic (E-mail)" <mmusic@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Jun 2006 09:32:10.0617 (UTC)
	FILETIME=[6641AE90:01C69903]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Subject: [MMUSIC] RTSP: Optimizing setup and initial start delay
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 have received some feedback that wondered over the restriction on not 
piplining PLAY requests with any SETUP request after the first one.

11.4 PLAY

    The PLAY method tells the server to start sending data via the
    mechanism specified in SETUP. A client MUST NOT issue a PLAY request
    until any outstanding SETUP requests have been acknowledged as
    successful.

The above text prevents a client from sending the PLAY request until all 
SETUP requests have returned a response. That results in an extra RTT of 
delay when establishing a session. To my understanding this restriction 
is not necessary and there is substantial interest in trying to speed up 
the setup times for RTSP. My understanding of the restriction is that it 
is there to ensure that there is a known and consistent state that the 
client request to play.

The consequence of removing the restriction against pipelining the PLAY 
request is that if any of the SETUP request following the first one on 
an aggregated session fails the PLAY request acts on the state existing 
without the failed SETUP requests. This is both predictable and 
explicitly notified to the client. Thus I don't see a problem with it.

My proposal would be to change the first paragraph of section 11.4:

11.4 PLAY

    The PLAY method tells the server to start sending data via the
    mechanism specified in SETUP. PLAY requests are valid when the
    session is in READY or PLAY states. A PLAY request MUST include
    a Session header to indicate which session the request applies
    to.

    For aggregated sessions where the initial SETUP request (creating a 
session) is followed by one or more additional SETUP request, a PLAY 
request MAY be pipelined after those additional SETUP requests without 
awaiting their responses.  This can procedure can reduce the delay from 
start of session establishment until media play-out has started with one 
RTT. However an client needs to be aware that using this procedure will 
result in the playout of the server state established at the time of 
processing the PLAY, i.e. after the processing of all the requests prior 
to the PLAY request in the pipeline. This may not be the intended one 
due to failure of any of the prior requests. However a client easily 
determine this based on the responses from those requests. In case of 
failure the client can halt the media playout using PAUSE and try to 
establish the intended state again before issuing another PLAY request.

Comments?

Cheers

Magnus Westerlund

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

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



From mmusic-bounces@ietf.org Mon Jun 26 06:15:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fuo84-0007L3-2O; Mon, 26 Jun 2006 06:15:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fuo81-0007Ja-HR
	for mmusic@ietf.org; Mon, 26 Jun 2006 06:15:37 -0400
Received: from violet.upc.es ([147.83.2.51])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fuo7Y-0000I4-Ct
	for mmusic@ietf.org; Mon, 26 Jun 2006 06:15:10 -0400
Received: from localhost (localhost [127.0.0.1])
	by violet.upc.es (8.13.6/8.13.6) with SMTP id k5QAF09D018114;
	Mon, 26 Jun 2006 12:15:03 +0200
Received: from localhost (wmail-mat.upc.es [147.83.39.70])
	by violet.upc.es (8.13.6/8.13.6) with ESMTP id k5QACFbS017154;
	Mon, 26 Jun 2006 12:12:15 +0200
Received: from 130.206.43.77 ( [130.206.43.77])
	as user viamonte@mat.upc.es by wmail-mat.upc.es with HTTP;
	Mon, 26 Jun 2006 12:08:25 +0200
Message-ID: <1151316505.449fb21976557@wmail-mat.upc.es>
Date: Mon, 26 Jun 2006 12:08:25 +0200
From: David Viamonte <viamonte@entel.upc.edu>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Re: [MMUSIC] RTSP: Optimizing setup and initial start delay
References: <449FA99B.8020402@ericsson.com>
In-Reply-To: <449FA99B.8020402@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.1
X-Originating-IP: 130.206.43.77
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
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, and thanks for re-triggering this topic.

I think this could be a feasible alternative to reduce approx. 1 RTT in RTSP
session setup delay. I agree with you that, since the server must serve each
RTSP message in (CSeq) order, this leaves no room for uncertainty.

One comment is that in case the RTSP client needs to trigger some sort of QoS
reservation (e.g.: IntServ, 3G Secondary PDP-Context setup), the failure of one
of the SETUP requests means not only that RTSP session re-negotiation (PLAY -
PAUSE - PLAY) may be required, but also resource reservation is impacted.

In order to overcome this, would it be possible to think about a "condensed"
RTSP SETUP message? That is: to signal as many streams as required in one single
RTSP transaction. This has several advantages:

1. The reduction is not only 1 RTT but as many RTT's as streams to be requested
(minus one). This is only approximate, since the SETUP message size increases.

2. This aligns RTSP and SIP behavior, so that media negotiation is independent
of the number of streams to be requested.

3. If a media stream is not successfully allocated, the server may anyway
indicate the other successfully allocated streams, so the client/user may decide
whether to stream them or not (thus, avoiding the need to perform RTSP
re-negotiation). 

4. Resource reservation is always performed after successful RTSP SETUP request,
thus minimising the need for QoS renegotiation.

Of course, this has a (major?) issue: larger impact in RTSP.  Would this make
any sense? In case this is useful but represents major impact to the RTSP 2.0
I-D, it could be considered as a separate I-D describing the optimization.

Kind regards,

David



Mensaje citado por Magnus Westerlund <magnus.westerlund@ericsson.com>:

> Hi,
> 
> I have received some feedback that wondered over the restriction on not 
> piplining PLAY requests with any SETUP request after the first one.
> 
> 11.4 PLAY
> 
>     The PLAY method tells the server to start sending data via the
>     mechanism specified in SETUP. A client MUST NOT issue a PLAY request
>     until any outstanding SETUP requests have been acknowledged as
>     successful.
> 
> The above text prevents a client from sending the PLAY request until all 
> SETUP requests have returned a response. That results in an extra RTT of 
> delay when establishing a session. To my understanding this restriction 
> is not necessary and there is substantial interest in trying to speed up 
> the setup times for RTSP. My understanding of the restriction is that it 
> is there to ensure that there is a known and consistent state that the 
> client request to play.
> 
> The consequence of removing the restriction against pipelining the PLAY 
> request is that if any of the SETUP request following the first one on 
> an aggregated session fails the PLAY request acts on the state existing 
> without the failed SETUP requests. This is both predictable and 
> explicitly notified to the client. Thus I don't see a problem with it.
> 
> My proposal would be to change the first paragraph of section 11.4:
> 
> 11.4 PLAY
> 
>     The PLAY method tells the server to start sending data via the
>     mechanism specified in SETUP. PLAY requests are valid when the
>     session is in READY or PLAY states. A PLAY request MUST include
>     a Session header to indicate which session the request applies
>     to.
> 
>     For aggregated sessions where the initial SETUP request (creating a 
> session) is followed by one or more additional SETUP request, a PLAY 
> request MAY be pipelined after those additional SETUP requests without 
> awaiting their responses.  This can procedure can reduce the delay from 
> start of session establishment until media play-out has started with one 
> RTT. However an client needs to be aware that using this procedure will 
> result in the playout of the server state established at the time of 
> processing the PLAY, i.e. after the processing of all the requests prior 
> to the PLAY request in the pipeline. This may not be the intended one 
> due to failure of any of the prior requests. However a client easily 
> determine this based on the responses from those requests. In case of 
> failure the client can halt the media playout using PAUSE and try to 
> establish the intended state again before issuing another PLAY request.
> 
> Comments?
> 
> Cheers
> 
> Magnus Westerlund
> 
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 




-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/



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



From mmusic-bounces@ietf.org Mon Jun 26 06:50:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fuofd-0004K9-Of; Mon, 26 Jun 2006 06:50:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fuofc-0004K4-Gz
	for mmusic@ietf.org; Mon, 26 Jun 2006 06:50:20 -0400
Received: from mail.uni-ulm.de ([134.60.1.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fuofa-0003lh-RC
	for mmusic@ietf.org; Mon, 26 Jun 2006 06:50:20 -0400
Received: from uni-ulm.de (discovery.informatik.uni-ulm.de [134.60.77.113])
	(authenticated bits=0)
	by mail.uni-ulm.de (8.13.7/8.13.7) with ESMTP id k5QAoAsD011105
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 26 Jun 2006 12:50:10 +0200 (MEST)
Message-ID: <449FBBF6.8040106@uni-ulm.de>
Date: Mon, 26 Jun 2006 12:50:30 +0200
From: Teodora Guenkova-Luy <teodora.guenkova-luy@uni-ulm.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en, de-de, bg
MIME-Version: 1.0
To: mmusic@ietf.org, fandreas@cisco.com, rjesup@wgate.com
X-Spam-Score: 0.3 (/)
X-Scan-Signature: cdeeb24e6b743a852c396a4af0e53c8f
Cc: 
Subject: [MMUSIC] Re: SDP Capability Negotiation to address multiple RTP
 profiles and other issues
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="===============0663048580=="
Errors-To: mmusic-bounces@ietf.org

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

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

Hi,
I have also a comment to REQ-110 and REQ-120.
Since the potential configurations are pre-conditions for choosing and  
enforcing them as actual configurations, may be a better idea is to 
perform a negotiation with potential configurations in two stages: First 
the offerer and the anserer agree which potential configurations are 
applicable and secondly which are the chosen configurations to become 
actual (i.e. counter-offer and counter-answer). Solution for such 
behaviour can be RFC 3312.

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

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

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

e-Mail: teodora.guenkova-luy@uni-ulm.de

Home Page: http://www-vs.informatik.uni-ulm.de/dept/staff/guenkova/ 

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


>
>
>
>  
>
>>I have submitted a draft on adding capability negotiation to SDP which you
>>can retrieve from (abstract below):
>>
>>http://www.ietf.org/internet-drafts/draft-andreasen-mmusic-sdp-capability-negotiation-00.txt
>>
>>The primary motivation for this is to address the proliferation of RTP
>>profiles and the associated problem of negotiating which of possibly
>>several supported RTP profiles to use for a given media stream.
>>    
>>
>...
>  
>
>>Feedback is hereby solicited. In particular, it would be very helpful if
>>people could take a look at the requirements and see if they agree with
>>them (too much, too little, anything wrong/missing, etc.) before we get
>>into detailed discussion around the proposed solution. Having said that,
>>all comments are welcome.
>>    
>>
>
>REQ-10: there are other ways to deal with the example issue, especially
>involving re-INVITE in SIP - though re-negotiation may not be possible in
>some uses of SDP.  You may want to mention here or better in the Existing
>Work section how re-INVITE/re-negotiation fit in (which applies to a lot of
>the requirements, not just this one).
>
>REQ-110: (ability to receive media immediately) and REQ-120 - see below.
>These two seem redundant.
>
>Overall, I find it interesting, if complex.  There is a major issue (see
>below) to resolve.  The complexity may be such that getting interoperable
>implementations may be a challenge.  An effective test suite and set of
>examples will be critical.  The problem is a very real one.
>
>It appears to not deal with two issues dealt with by the grouping spec,
>which are defining valid combinations of media lines, and defining valid
>combinations of codecs (on one media line or between lines).  This would
>mean that those particular requirements would still need grouping or SDPng
>or ???.  Perhaps at least the first (valid combinations of media lines)
>can be worked into this approach?  As you mention, grouping (and even more
>so multipart-alternative) have significant compatibility issues.
>
>
>General issue with the approach:
>
>It's dependant on the offerer receiving the answer in order to decode the
>media.  For example, if the transport protocol can be RTP/AVP or RTP/SAVP
>(regardless of which is the "actual" offer and which is potential), how
>does the receiver process incoming media packets if it hasn't seen the
>answer?  Especially if the packet types can't be intuited from something
>like size (an example would be SRTP with encryption but no auth tag).  In
>some cases this would cause static, could cause potential crashing or
>problematic actions.  So the answerer may not be able to send media until
>they see ACK (in SIP) if they accept a potential configuration.
>
>This can cause clipping - you pick up the phone and start talking, but if
>the answer is lost or delayed, or if the ACK is lost or delayed, your
>"hello?" might be lost.
>
>Now, this might be ok, though clipping is to be avoided where possible,
>since people assume through experience that media channels are open as soon
>as they answer.  Also, if the configuration accepted is the actual one,
>the answerer can send media immediately.
>
>
>Potential solutions:
>a) Use different transport addresses for incompatible media/protocols.
>   Could be problematic when combined with ICE/TURN/etc - more ports.
>   Could cause some combinatoric expansion (especially with ICE/TURN).
>b) Use alternative payload types to distinguish incompatible media types
>   so that some level of decoding (or at least knowing to ignore packets) 
>   can be done before the answer arrives.  This might tell the offerer
>   enough to fully decode, though they still can't send until they get
>   the answer (which is normal).  It may not tell enough in all cases
>   without expansion, and perhaps there are backwards compatibility
>   issues.  Also, there may be issues with the number of payload types
>   listed (though perhaps the values could be inferred instead of
>   explicit) and how that affects the size of the offer.
>
>Discussion of clipping, when and how media is sent, and how packet
>loss/delay affect this will be critical.
>
>  
>


--------------040105050005020609080505
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Hi,<br>
I have also a comment to REQ-110 and REQ-120.<br>
Since the potential configurations are pre-conditions for choosing and&nbsp;
enforcing them as actual configurations, may be a better idea is to
perform a negotiation with potential configurations in two stages:
First the offerer and the anserer agree which potential configurations
are applicable and secondly which are the chosen configurations to
become actual (i.e. counter-offer and counter-answer). Solution for
such behaviour can be RFC 3312.<br>
<pre class="moz-signature" cols="72">-- 
-----------------------------------------
Teodora Guenkova-Luy

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

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

e-Mail: <a class="moz-txt-link-abbreviated" href="mailto:teodora.guenkova-luy@uni-ulm.de">teodora.guenkova-luy@uni-ulm.de</a>

Home Page: <a class="moz-txt-link-freetext" href="http://www-vs.informatik.uni-ulm.de/dept/staff/guenkova/">http://www-vs.informatik.uni-ulm.de/dept/staff/guenkova/</a> 

-----------------------------------------</pre>
<br>
<blockquote type="cite" cite="midE1FtqQM-0001Hm-ES@megatron.ietf.org">
  <pre wrap="">



  </pre>
  <blockquote type="cite">
    <pre wrap="">I have submitted a draft on adding capability negotiation to SDP which you
can retrieve from (abstract below):

<a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-andreasen-mmusic-sdp-capability-negotiation-00.txt">http://www.ietf.org/internet-drafts/draft-andreasen-mmusic-sdp-capability-negotiation-00.txt</a>

The primary motivation for this is to address the proliferation of RTP
profiles and the associated problem of negotiating which of possibly
several supported RTP profiles to use for a given media stream.
    </pre>
  </blockquote>
  <pre wrap=""><!---->...
  </pre>
  <blockquote type="cite">
    <pre wrap="">Feedback is hereby solicited. In particular, it would be very helpful if
people could take a look at the requirements and see if they agree with
them (too much, too little, anything wrong/missing, etc.) before we get
into detailed discussion around the proposed solution. Having said that,
all comments are welcome.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
REQ-10: there are other ways to deal with the example issue, especially
involving re-INVITE in SIP - though re-negotiation may not be possible in
some uses of SDP.  You may want to mention here or better in the Existing
Work section how re-INVITE/re-negotiation fit in (which applies to a lot of
the requirements, not just this one).

REQ-110: (ability to receive media immediately) and REQ-120 - see below.
These two seem redundant.

Overall, I find it interesting, if complex.  There is a major issue (see
below) to resolve.  The complexity may be such that getting interoperable
implementations may be a challenge.  An effective test suite and set of
examples will be critical.  The problem is a very real one.

It appears to not deal with two issues dealt with by the grouping spec,
which are defining valid combinations of media lines, and defining valid
combinations of codecs (on one media line or between lines).  This would
mean that those particular requirements would still need grouping or SDPng
or ???.  Perhaps at least the first (valid combinations of media lines)
can be worked into this approach?  As you mention, grouping (and even more
so multipart-alternative) have significant compatibility issues.


General issue with the approach:

It's dependant on the offerer receiving the answer in order to decode the
media.  For example, if the transport protocol can be RTP/AVP or RTP/SAVP
(regardless of which is the "actual" offer and which is potential), how
does the receiver process incoming media packets if it hasn't seen the
answer?  Especially if the packet types can't be intuited from something
like size (an example would be SRTP with encryption but no auth tag).  In
some cases this would cause static, could cause potential crashing or
problematic actions.  So the answerer may not be able to send media until
they see ACK (in SIP) if they accept a potential configuration.

This can cause clipping - you pick up the phone and start talking, but if
the answer is lost or delayed, or if the ACK is lost or delayed, your
"hello?" might be lost.

Now, this might be ok, though clipping is to be avoided where possible,
since people assume through experience that media channels are open as soon
as they answer.  Also, if the configuration accepted is the actual one,
the answerer can send media immediately.


Potential solutions:
a) Use different transport addresses for incompatible media/protocols.
   Could be problematic when combined with ICE/TURN/etc - more ports.
   Could cause some combinatoric expansion (especially with ICE/TURN).
b) Use alternative payload types to distinguish incompatible media types
   so that some level of decoding (or at least knowing to ignore packets) 
   can be done before the answer arrives.  This might tell the offerer
   enough to fully decode, though they still can't send until they get
   the answer (which is normal).  It may not tell enough in all cases
   without expansion, and perhaps there are backwards compatibility
   issues.  Also, there may be issues with the number of payload types
   listed (though perhaps the values could be inferred instead of
   explicit) and how that affects the size of the offer.

Discussion of clipping, when and how media is sent, and how packet
loss/delay affect this will be critical.

  </pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">
</pre>
</body>
</html>

--------------040105050005020609080505--



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

--===============0663048580==--





From mmusic-bounces@ietf.org Mon Jun 26 08:02:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fupnn-0001nh-4N; Mon, 26 Jun 2006 08:02:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fupnl-0001nV-Eb
	for mmusic@ietf.org; Mon, 26 Jun 2006 08:02:49 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fupnj-0002CS-O9
	for mmusic@ietf.org; Mon, 26 Jun 2006 08:02:49 -0400
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	E91434F0047; Mon, 26 Jun 2006 14:02:46 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Jun 2006 14:02:46 +0200
Received: from [147.214.30.119] ([147.214.30.119]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Jun 2006 14:02:45 +0200
Message-ID: <449FCCE6.2060202@ericsson.com>
Date: Mon, 26 Jun 2006 14:02:46 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: David Viamonte <viamonte@entel.upc.edu>
Subject: Re: [MMUSIC] RTSP: Optimizing setup and initial start delay
References: <449FA99B.8020402@ericsson.com>
	<1151316505.449fb21976557@wmail-mat.upc.es>
In-Reply-To: <1151316505.449fb21976557@wmail-mat.upc.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Jun 2006 12:02:45.0678 (UTC)
	FILETIME=[6F9294E0:01C69918]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
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 David,

I know that there been some interest in the general topic of optimizing 
the setup towards a single RTT setup. However as you correctly identify 
this is a major change. We should also consider what it means to update 
RTSP. The original intention with this work was to document RTSP 1.0 so 
it actually is possible to implement it in interoperable way. This has 
not gone as well as intended due to the brokenness of RTSP 1.0. There is 
also the issue with the lack of contributors to the RTSP update.

I have very few cycles to spend on RTSP and the update is significantly 
delayed compared to the intended finish date. Thus I try my best to 
finish up the last details to make it ready for WGLC and publication. So 
  I don't see your proposal happening without further serious commitment 
on actually doing work on this topic. I would think this requires a 
couple of hundred hours from several people to write a new proposal, 
review and debug it enough to be useful. I think large part of the 
specification would need to be changed to do what you propose.

I also have a couple of questions about the below.


David Viamonte wrote:
> Hi Magnus, and thanks for re-triggering this topic.
> 
> I think this could be a feasible alternative to reduce approx. 1 RTT in RTSP
> session setup delay. I agree with you that, since the server must serve each
> RTSP message in (CSeq) order, this leaves no room for uncertainty.
> 
> One comment is that in case the RTSP client needs to trigger some sort of QoS
> reservation (e.g.: IntServ, 3G Secondary PDP-Context setup), the failure of one
> of the SETUP requests means not only that RTSP session re-negotiation (PLAY -
> PAUSE - PLAY) may be required, but also resource reservation is impacted.

Yes, it might be impacted, however if the failure in setup is not 
related to the QoS flow specification, i.e. addresses and port change 
QoS reservation should most likely not be needed.

> 
> In order to overcome this, would it be possible to think about a "condensed"
> RTSP SETUP message? That is: to signal as many streams as required in one single
> RTSP transaction. This has several advantages:
> 
> 1. The reduction is not only 1 RTT but as many RTT's as streams to be requested
> (minus one). This is only approximate, since the SETUP message size increases.

No. I think you are making a mistake here. With the proposed change you 
would be able to go from an RTSP link to playing media in 3 RTT. 1 for 
describe, 1 for the first setup, 1 for the consecutive SETUP (1 or more 
pipelined) and the PLAY request. The only way you could gain a RTT with 
your proposal would be if you could in a single RTSP request do SETUP 
and start media playout. The initial DESCRIBE would still be needed.

> 
> 2. This aligns RTSP and SIP behavior, so that media negotiation is independent
> of the number of streams to be requested.

Yes, but here we come to the interesting question. Why not use SIP for 
the media stream configuration. Instead of re-inventing the media stream 
configuration step, why not re-use SIP for it.

> 
> 3. If a media stream is not successfully allocated, the server may anyway
> indicate the other successfully allocated streams, so the client/user may decide
> whether to stream them or not (thus, avoiding the need to perform RTSP
> re-negotiation). 

I don't see this as being different from what would happen today. In 
aggregated sessions only successfully negotiated streams are added to 
the session. A failure in the SETUP simply leaves the client with the 
choice of either fixing it or going forward with the established state 
and media streams.

> 
> 4. Resource reservation is always performed after successful RTSP SETUP request,
> thus minimising the need for QoS renegotiation.



cheers

Magnus Westerlund

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

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



From mmusic-bounces@ietf.org Mon Jun 26 10:05:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Furir-0000Sr-Mq; Mon, 26 Jun 2006 10:05:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Furiq-0000Sm-F8
	for mmusic@ietf.org; Mon, 26 Jun 2006 10:05:52 -0400
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Furip-0002P2-8R
	for mmusic@ietf.org; Mon, 26 Jun 2006 10:05:52 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 26 Jun 2006 10:06:44 -0400
To: Teodora Guenkova-Luy <teodora.guenkova-luy@uni-ulm.de>
References: <449FBBF6.8040106@uni-ulm.de>
From: Randell Jesup <rjesup@wgate.com>
Date: Mon, 26 Jun 2006 10:05:49 -0400
In-Reply-To: <449FBBF6.8040106@uni-ulm.de> (Teodora Guenkova-Luy's message
	of "Mon, 26 Jun 2006 12:50:30 +0200")
Message-ID: <ybuirmohv0i.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 26 Jun 2006 14:06:44.0927 (UTC)
	FILETIME=[C1B5E4F0:01C69929]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: fandreas@cisco.com, mmusic@ietf.org
Subject: [MMUSIC] Re: SDP Capability Negotiation to address multiple RTP
 profiles and other issues
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Teodora Guenkova-Luy <teodora.guenkova-luy@uni-ulm.de> writes:
>I have also a comment to REQ-110 and REQ-120.
>Since the potential configurations are pre-conditions for choosing and
>enforcing them as actual configurations, may be a better idea is to perform
>a negotiation with potential configurations in two stages: First the
>offerer and the anserer agree which potential configurations are applicable
>and secondly which are the chosen configurations to become actual
>(i.e. counter-offer and counter-answer). Solution for such behaviour can be
>RFC 3312.

This sounds like a minimum 1.5-round-trip negotiation
(offer/counter-offer/counter-answer).  That appears to violate REQ-100 (it
must work within the offer-answer model, specifically it must do a
negotiation within a single round-trip).  What you're proposing sounds more
like preconditions (though I'm not 100% up on the details of how
preconditions work).

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


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



From mmusic-bounces@ietf.org Mon Jun 26 10:08:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FurlC-0005DY-Ar; Mon, 26 Jun 2006 10:08:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FurlA-0005DT-NQ
	for mmusic@ietf.org; Mon, 26 Jun 2006 10:08:16 -0400
Received: from irvmail2.verizon.com ([192.76.80.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Furl8-0002Y4-Vi
	for mmusic@ietf.org; Mon, 26 Jun 2006 10:08:16 -0400
Received: from smtpftw.verizon.com (smtpftw.verizon.com [138.83.130.53])
	by irvmail2.verizon.com (8.13.3/8.13.3) with ESMTP id k5QE8PIT022792;
	Mon, 26 Jun 2006 09:08:25 -0500 (EST)
Received: from ftwintrmemf2.verizon.com (ftwintrmemf2.verizon.com
	[138.83.131.184])
	by smtpftw.verizon.com (8.13.3/8.13.3) with ESMTP id k5QE86MS010336;
	Mon, 26 Jun 2006 09:08:06 -0500 (EST)
Received: from coregate2.verizon.com (unknown [138.83.34.48])
	by ftwintrmemf2.verizon.com (Symantec Mail Security) with ESMTP id
	9266A44401B; Mon, 26 Jun 2006 10:08:01 -0400 (EDT)
Received: from dwsmtp01.core.verizon.com (dwsmtp01.verizon.com [138.83.35.62])
	by coregate2.verizon.com (8.13.3/8.13.3) with ESMTP id
	k5QE80cO028346; Mon, 26 Jun 2006 09:08:00 -0500 (CDT)
Date: Mon, 26 Jun 2006 10:08:01 -0400
MIME-Version: 1.0
To: ravishankar.shiroor@wipro.com, xavier.marjou@francetelecom.com,
	mmontpetit@motorola.com, mmusic@ietf.org
From: steven.d.whitehead@verizon.com
X-Mailer: Microsoft Outlook v 11.00.8000, MSOC v 2.00.4007.00
Message-ID: <OF03D8666F.2E260B0F-ON04257199.004D9B30@CORE.VERIZON.COM>
X-MIMETrack: Serialize by Router on DWSMTP01/HSVR/Verizon(Release 6.5.4HF453 |
	August 4, 2005) at 06/26/2006 09:08:00,
	Serialize complete at 06/26/2006 09:08:00
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a
Cc: 
Subject: [MMUSIC] RE: Comments: I-D
	ACTION:draft-whitehead-mmusic-sip-for-streaming-media-01.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Ravi, thanks for the feedback. Good points. -Steve

-----Original Message-----
From: ravishankar.shiroor@wipro.com [mailto:ravishankar.shiroor@wipro.com]

Sent: Sunday, June 25, 2006 11:11 PM
To: Steven D. Whitehead; xavier.marjou@francetelecom.com;
mmontpetit@motorola.com; mmusic@ietf.org
Subject: Comments: I-D
ACTION:draft-whitehead-mmusic-sip-for-streaming-media-01.txt


Steve, Xavier, Marie,

Thanks for putting together the use case analysis and recommendations.
I feel this a very important area to be pursued to make the multimedia

streaming services richer.

Two comments on the requirement section:

Even though it has been mentioned at many places in the draft, I think

it is better to spell out the requirement on the trick plays and media
control
specifically.


Another requirement that can be considered is to provide the server the

ability to Teardown a session. In a pure RTSP session, a server can not

TEARDOWN a session by itself (at least not gracefully according to the
protocol).

Regards,
Ravi.


--


Ravishankar. G. Shiroor
Wipro Technologies, Bangalore.

ravishankar.shiroor@wipro.com
--

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]

Sent: Friday, June 23, 2006 4:20 AM
To: i-d-announce@ietf.org
Subject: I-D
ACTION:draft-whitehead-mmusic-sip-for-streaming-media-01.txt


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


	Title		: An Evaluation of Session Initiation Protocol
                          (SIP) for use in Streaming Media Applications
	Author(s)	: S. Whitehead, et al.
	Filename	:
draft-whitehead-mmusic-sip-for-streaming-media-01.txt
	Pages		: 13
	Date		: 2006-6-22


This draft summarizes a set of use-cases and their associated
   requirements that suggest a convergence between the Session
   Initiation Protocol (SIP) [2] and the Real Time Streaming Protocol
   (RTSP and RTSP v2) [3] and [4] that may be beneficial for streaming
   media applications.  This benefit is especially apparent in the
   context of converged/blended media services.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-whitehead-mmusic-sip-for-strea
ming-media-01.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of
the message. 

You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.


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

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE
/internet-drafts/draft-whitehead-mmusic-sip-for-streaming-media-01.txt".


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

	

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



The information contained in this electronic message and any attachments
to this message are intended for the exclusive use of the addressee(s) and
may contain proprietary, confidential or privileged information. If you
are not the intended recipient, you should not disseminate, distribute or
copy this e-mail. Please notify the sender immediately and destroy all
copies of this message and any attachments.


WARNING: Computer viruses can be transmitted via email. The recipient
should check this email and any attachments for the presence of viruses.
The company accepts no liability for any damage caused by any virus
transmitted by this email.


www.wipro.com



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



From mmusic-bounces@ietf.org Mon Jun 26 10:54:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FusTg-0000xH-DZ; Mon, 26 Jun 2006 10:54:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FusTe-0000vo-JM
	for mmusic@ietf.org; Mon, 26 Jun 2006 10:54:14 -0400
Received: from mail.uni-ulm.de ([134.60.1.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FusTd-0007zj-1k
	for mmusic@ietf.org; Mon, 26 Jun 2006 10:54:14 -0400
Received: from uni-ulm.de (discovery.informatik.uni-ulm.de [134.60.77.113])
	(authenticated bits=0)
	by mail.uni-ulm.de (8.13.7/8.13.7) with ESMTP id k5QEs9Ia003467
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 26 Jun 2006 16:54:09 +0200 (MEST)
Message-ID: <449FF525.3090402@uni-ulm.de>
Date: Mon, 26 Jun 2006 16:54:29 +0200
From: Teodora Guenkova-Luy <teodora.guenkova-luy@uni-ulm.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en, de-de, bg
MIME-Version: 1.0
To: Randell Jesup <rjesup@wgate.com>
References: <449FBBF6.8040106@uni-ulm.de> <ybuirmohv0i.fsf@jesup.eng.wgate.com>
In-Reply-To: <ybuirmohv0i.fsf@jesup.eng.wgate.com>
X-Spam-Score: 0.6 (/)
X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985
Cc: fandreas@cisco.com, mmusic@ietf.org
Subject: [MMUSIC] Re: SDP Capability Negotiation to address multiple RTP
 profiles and other issues
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="===============1143467389=="
Errors-To: mmusic-bounces@ietf.org

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

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

Randell Jesup wrote:

>Teodora Guenkova-Luy <teodora.guenkova-luy@uni-ulm.de> writes:
>  
>
>>I have also a comment to REQ-110 and REQ-120.
>>Since the potential configurations are pre-conditions for choosing and
>>enforcing them as actual configurations, may be a better idea is to perform
>>a negotiation with potential configurations in two stages: First the
>>offerer and the anserer agree which potential configurations are applicable
>>and secondly which are the chosen configurations to become actual
>>(i.e. counter-offer and counter-answer). Solution for such behaviour can be
>>RFC 3312.
>>    
>>
>
>This sounds like a minimum 1.5-round-trip negotiation
>(offer/counter-offer/counter-answer).  That appears to violate REQ-100 (it
>must work within the offer-answer model, specifically it must do a
>negotiation within a single round-trip).  What you're proposing sounds more
>like preconditions (though I'm not 100% up on the details of how
>preconditions work).
>
>  
>
Hi,
If you look at REQ-100 the author seems also not to be sure if the 
negotiation of potential configurations should be limited to O/A model 
only. IMHO, you don't need to negotiate potential configurations if you 
are sure that the proposed actual configurations will work as they are. 
Hence, you don't need preconditions for your session. However, if only a 
limited amount of the actual configurations works, your session is also 
limited, and it can be enhaced only through a re-negotiation, but the 
re-negotiation is IMHO more expensive compared to the negotiation of 
potential configurations as it takes place during the media session. If 
you are proposing potential configurations this means that you are not 
sure what kind of answer you'll get and eventually the answerer may 
enhance the proposal of the offerer with further potential 
configurations in order to ease the decision of the offerer what 
configurations to take for the session. Furthermore, the offerer may 
propose potential configurations that might be too expensive for the 
offerer (e.g. in terms of resources), so the offerer has to wait the 
answer in oder to make its final decision. Consequently and due to such 
uncertainties, only after exchanging potential configurations, the 
offerer can decide which configurations can be taken as actual and 
signal them to the answerer. This is no more O/A model, as the proposals 
for potential configurations work as pre-conditions for the success of 
the following session.

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

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

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

e-Mail: teodora.guenkova-luy@uni-ulm.de

Home Page: http://www-vs.informatik.uni-ulm.de/dept/staff/guenkova/ 

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


--------------020400000006030809030904
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Randell Jesup wrote:<br>
<blockquote type="cite" cite="midybuirmohv0i.fsf@jesup.eng.wgate.com">
  <pre wrap="">Teodora Guenkova-Luy <a class="moz-txt-link-rfc2396E" href="mailto:teodora.guenkova-luy@uni-ulm.de">&lt;teodora.guenkova-luy@uni-ulm.de&gt;</a> writes:
  </pre>
  <blockquote type="cite">
    <pre wrap="">I have also a comment to REQ-110 and REQ-120.
Since the potential configurations are pre-conditions for choosing and
enforcing them as actual configurations, may be a better idea is to perform
a negotiation with potential configurations in two stages: First the
offerer and the anserer agree which potential configurations are applicable
and secondly which are the chosen configurations to become actual
(i.e. counter-offer and counter-answer). Solution for such behaviour can be
RFC 3312.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
This sounds like a minimum 1.5-round-trip negotiation
(offer/counter-offer/counter-answer).  That appears to violate REQ-100 (it
must work within the offer-answer model, specifically it must do a
negotiation within a single round-trip).  What you're proposing sounds more
like preconditions (though I'm not 100% up on the details of how
preconditions work).

  </pre>
</blockquote>
Hi,<br>
If you look at REQ-100 the author seems also not to be sure if the
negotiation of potential configurations should be limited to O/A model
only. IMHO, you don't need to negotiate potential configurations if you
are sure that the proposed actual configurations will work as they are.
Hence, you don't need preconditions for your session. However, if only
a limited amount of the actual configurations works, your session is
also limited, and it can be enhaced only through a re-negotiation, but
the re-negotiation is IMHO more expensive compared to the negotiation
of potential configurations as it takes place during the media session.
If you are proposing potential configurations this means that you are
not sure what kind of answer you'll get and eventually the answerer may
enhance the proposal of the offerer with further potential
configurations in order to ease the decision of the offerer what
configurations to take for the session. Furthermore, the offerer may
propose potential configurations that might be too expensive for the
offerer (e.g. in terms of resources), so the offerer has to wait the
answer in oder to make its final decision. Consequently and due to such
uncertainties, only after exchanging potential configurations, the
offerer can decide which configurations can be taken as actual and
signal them to the answerer. This is no more O/A model, as the
proposals for potential configurations work as pre-conditions for the
success of the following session. <br>
<pre class="moz-signature" cols="72">-- 
-----------------------------------------
Teodora Guenkova-Luy

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

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

e-Mail: <a class="moz-txt-link-abbreviated" href="mailto:teodora.guenkova-luy@uni-ulm.de">teodora.guenkova-luy@uni-ulm.de</a>

Home Page: <a class="moz-txt-link-freetext" href="http://www-vs.informatik.uni-ulm.de/dept/staff/guenkova/">http://www-vs.informatik.uni-ulm.de/dept/staff/guenkova/</a> 

-----------------------------------------</pre>
</body>
</html>

--------------020400000006030809030904--



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

--===============1143467389==--





From mmusic-bounces@ietf.org Mon Jun 26 10:57:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FusWg-0002KY-WA; Mon, 26 Jun 2006 10:57:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FusWg-0002KT-77
	for mmusic@ietf.org; Mon, 26 Jun 2006 10:57:22 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FusWe-0008KL-Mh
	for mmusic@ietf.org; Mon, 26 Jun 2006 10:57:22 -0400
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	EA5784F0001
	for <mmusic@ietf.org>; Mon, 26 Jun 2006 16:57:19 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Jun 2006 16:57:19 +0200
Received: from [147.214.30.119] ([147.214.30.119]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Jun 2006 16:57:18 +0200
Message-ID: <449FF5CE.8030402@ericsson.com>
Date: Mon, 26 Jun 2006 16:57:18 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: "mmusic (E-mail)" <mmusic@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Jun 2006 14:57:18.0502 (UTC)
	FILETIME=[D1DCB460:01C69930]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Subject: [MMUSIC] RTSP: draft-ietf-mmusic-rfc2326bis-13
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 have submitted an updated version of the RTSP specification. As usual 
I started to late with this work. What I managed to do was the following:

1. Integrate the text I received from John Lazzaro on using independent 
TCP connections for RTP transport (contrans).

2. Tried to clarity the DDoS protection for RTSP in the security 
consideration section.

3. Updated the transport specifications to match the syntax and how the 
complete combination strings should be registered with IANA.

4. Implemented the proposal for allowing the client to pipeline the PLAY 
request to any non-initial SETUP requests to gain a RTT.

Which means I didn't clean up the open issues list that remained after 
the Dallas meeting.

Cheers

Magnus Westerlund

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

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



From mmusic-bounces@ietf.org Mon Jun 26 12:11:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Futgn-0008DA-Pm; Mon, 26 Jun 2006 12:11:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Futgm-0008Ch-Pe
	for mmusic@ietf.org; Mon, 26 Jun 2006 12:11:52 -0400
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Futgk-0004l1-Hg
	for mmusic@ietf.org; Mon, 26 Jun 2006 12:11:52 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 26 Jun 2006 12:12:43 -0400
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Re: [MMUSIC] How big can SDP get
References: <0B1E407B-B882-4402-A22A-2F99B7C2062C@cisco.com>
	<446B22C9.2000206@ericsson.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Mon, 26 Jun 2006 12:11:48 -0400
In-Reply-To: <446B22C9.2000206@ericsson.com> (Magnus Westerlund's message of
	"Wed, 17 May 2006 15:19:05 +0200")
Message-ID: <ybuk673hp6j.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 26 Jun 2006 16:12:43.0989 (UTC)
	FILETIME=[5B433850:01C6993B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: Cullen Jennings <fluffy@cisco.com>, mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Magnus Westerlund <magnus.westerlund@ericsson.com> writes:
>One thing is obvious. It is easy to make a large SDP file. Attached is a
>10744 bytes large SDP.
>
>The SDP contains some errors as I have no interest of specifying unique
>ports for all ICE flows for example. However it should be possible to
>understand.
>
>The session is intended to be a offer from a transcoding gateway to a
>session receiver of a presentation session with a text chat session. So
>there is one video showing the presenter, protected by a separate FEC
>stream (ULP). There is a second video with retransmission for the document
>cam. There is one  audio stream protected by a second stream of FEC. Then
>there is a text session for chatting and a subtitle session. Add ICE, ANAT,
>SRTP with security description and few other small extension and you broke
>the 10k barrier.

And if we add something to allow for secure-or-non-secure connections (see
draft-andreasen-mmusic-sdp-capability-negotiation-00.txt) or grouping
(RFC-whatever) or mime multipart, SIP-level overhead (auth lines), etc and
you might be able to double or possibly triple that without adding more
codecs or streams.  Admittedly, it's a pretty nasty/odd variant you give,
but then again that's the point.

Good idea using H264 in all possible packetization modes, though the H264
stuff could be expanded quite a bit more with more optional parameters,
especially if there are variant payloads for different profiles (different
parameter sets for example).  And you didn't even both to offer "normal"
audio codecs like PCMU/A, 729, etc (and include the rtpmaps for all of
them), nor RFC2833 payloads.

I wonder if there's a way to mix TCP and UDP in SIP to get (some of) the
advantages of both.  This was/is a common trick in realtime IP stuff such
as online games (the first example I know of it was in 'netrek' back in
circa 1992-ish, before the web).  Or maybe to use TFRC-style congestion
avoidance in a reliable datagram service.  RDP (RFC's 908/1151) doesn't
seem to use a TCP-friendly congestion control from a quick look.

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


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



From mmusic-bounces@ietf.org Mon Jun 26 12:16:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Futla-0007FZ-M9; Mon, 26 Jun 2006 12:16:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FutlZ-0007FU-TV
	for mmusic@ietf.org; Mon, 26 Jun 2006 12:16:49 -0400
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254]
	helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FutlY-00052k-NW
	for mmusic@ietf.org; Mon, 26 Jun 2006 12:16:49 -0400
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 26 Jun 2006 12:17:42 -0400
To: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [MMUSIC] Usage of stream bandwidth attribute in  SDP offer/answer
References: <4.3.2.7.2.20060605163129.03565c88@email.cisco.com>
From: Randell Jesup <rjesup@wgate.com>
Date: Mon, 26 Jun 2006 12:16:47 -0400
In-Reply-To: <4.3.2.7.2.20060605163129.03565c88@email.cisco.com> (James M.
	Polk's message of "Mon, 05 Jun 2006 16:33:07 -0500")
Message-ID: <ybufyhrhoy8.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 26 Jun 2006 16:17:42.0586 (UTC)
	FILETIME=[0D3D81A0:01C6993C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

"James M. Polk" <jmpolk@cisco.com> writes:
>Asside from your BW question, how can Alice state in SDP what Bob's receive
>port number is?  Isn't that against the rules?

>>       m=video 51372 RTP/AVP 31
>>       a=rtpmap:31 H261/90000
>>       b=AS:64000
>>       a=sendonly

This specifies a port, but the RTP port (51372) is on Alice's end, and will
not be used barring re-INVITE.  The associated RTCP port (51373) will be
used.

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


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



From mmusic-bounces@ietf.org Mon Jun 26 12:36:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fuu4a-0006TL-8e; Mon, 26 Jun 2006 12:36:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fuu4Y-0006TG-O0
	for mmusic@ietf.org; Mon, 26 Jun 2006 12:36:26 -0400
Received: from nf-out-0910.google.com ([64.233.182.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fuu4X-0006hz-Fd
	for mmusic@ietf.org; Mon, 26 Jun 2006 12:36:26 -0400
Received: by nf-out-0910.google.com with SMTP id o63so862098nfa
	for <mmusic@ietf.org>; Mon, 26 Jun 2006 09:36:24 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
	b=AuZs2DSNYXL9IJGobFtRnF2yJLZy50+cHjXovc/ZIv7Ziab1tmYEA1E7cE6CNCYoKnfH0r+ZJH98p/MYs8lIk6DR85Snli8h9h5Ute1fkIBbdTRw4cK4uA9j7s3DEi1qkZZK0XHQRSmXIqaOmTNHty9Zf3yOPN2Xdl3EpsJ7nLk=
Received: by 10.48.233.18 with SMTP id f18mr4866870nfh;
	Mon, 26 Jun 2006 09:36:24 -0700 (PDT)
Received: by 10.48.218.8 with HTTP; Mon, 26 Jun 2006 09:36:24 -0700 (PDT)
Message-ID: <84a612dd0606260936v126745b5web8ae824910e0ecc@mail.gmail.com>
Date: Mon, 26 Jun 2006 17:36:24 +0100
From: "Mark Handley" <M.Handley@cs.ucl.ac.uk>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
Subject: Re: [MMUSIC] How big can SDP get
In-Reply-To: <446B22C9.2000206@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <0B1E407B-B882-4402-A22A-2F99B7C2062C@cisco.com>
	<446B22C9.2000206@ericsson.com>
X-Google-Sender-Auth: 6671a83373090910
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: Cullen Jennings <fluffy@cisco.com>, mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

On 5/17/06, Magnus Westerlund <magnus.westerlund@ericsson.com> wrote:
> Hi,
>
> One thing is obvious. It is easy to make a large SDP file. Attached is a
> 10744 bytes large SDP.

Although it still fits in a single 1500-byte UDP packet if you gzip it :-)

 - Mark

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



From mmusic-bounces@ietf.org Mon Jun 26 14:04:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FuvRa-0000ZN-FM; Mon, 26 Jun 2006 14:04:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FuvRZ-0000Vv-Jn
	for mmusic@ietf.org; Mon, 26 Jun 2006 14:04:17 -0400
Received: from mx6-1.spamtrap.magma.ca ([209.217.78.144])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FuvRZ-0006M7-7C
	for mmusic@ietf.org; Mon, 26 Jun 2006 14:04:17 -0400
Received: from mail2.magma.ca (mail2.internal.magma.ca [10.0.10.12])
	by mx6-1.spamtrap.magma.ca (8.13.1/8.13.1) with ESMTP id k5QI4Dcp028541;
	Mon, 26 Jun 2006 14:04:13 -0400
Received: from [10.1.5.219] ([216.13.42.126]) (authenticated bits=0)
	by mail2.magma.ca (Magma's Mail Server) with ESMTP id k5QI4DHD009931
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
	Mon, 26 Jun 2006 14:04:14 -0400
In-Reply-To: <449F37EF.8010407@cisco.com>
References: <5EB80D22825EEE42872083AD5BFFB594017F1166@esealmw113.eemea.ericsson.se>
	<C2E6E64E-5AEB-4D18-9944-2FA9360DBD9D@magma.ca>
	<449C40CA.9030604@cisco.com>
	<5EB80D22825EEE42872083AD5BFFB594117CFE@esealmw113.eemea.ericsson.se>
	<449F37EF.8010407@cisco.com>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <DFB3D7E3-AA91-4479-820D-0CF5BD975641@magma.ca>
Content-Transfer-Encoding: 7bit
From: Philip Matthews <philip_matthews@magma.ca>
Subject: Re: VS: [MMUSIC] ICE: Client supports, but network doesn't
Date: Mon, 26 Jun 2006 14:04:18 -0400
To: Jonathan Rosenberg <jdrosen@cisco.com>
X-Mailer: Apple Mail (2.746.2)
X-magma-MailScanner-Information: Magma Mailscanner Service
X-magma-MailScanner: Clean
X-Spam-Status: 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: mmusic@ietf.org,
	"Christer Holmberg \(JO/LMF\)" <christer.holmberg@ericsson.com>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org


On 25-Jun-06, at 21:27 , Jonathan Rosenberg wrote:

> inline.
>
> Christer Holmberg (JO/LMF) wrote:
>
>> Hi,
>>>>> 1.      What happens if the c/m lines does not correspond to
>>>>> any active a=candidate line? This could happen e.g. if you have
>>>>> a SDP modifying B2BUA (which doesn't support ICE) in the path.
>>>>> One option would be to say that the connectivity check shall be
>>>>> performed also for the c/m lines in that case, but then we may
>>>>> need a "default priority", or something...
>>>> What properties would we assume of such a SDP-modifying B2BUA?  
>>>> For example, would the a-candidate lines still be present? Would
>>>> they be modified by the B2BUA? Can you cite the behavior of some
>>>> known products that do this?
>> [CHH] I would assume that one could find products behaving in either
>> way. IF the B2BUA removes the candiate attributes I guess we'll get
>> the scenario described in my second question.
>>> I had the same question. Of course, the problem is that since a
>>> b2bua is entirely undefined its not claer what it will do. But, I
>>> think we are safe in assuming its one of two things:
>>> 1. it modifies the m/c-lines but leaves the a=candidate  
>>> attributes 2. it modifies the m/c-lines and removes all unknonwn  
>>> attributes, including a=candidate attributes
>> [CHH] Correct.
>>> I suspect (2) is much more likely from SBC products, but you never
>>> known.
>>> Lets look at what happens in each of these cases. Case 2 is the
>>> easiest. Both agents will think that the other side doesn't support
>>> ICE, and fallback to regular non-ICE behavior. So, things work as
>>> one would expect.
>> [CHH] As I said in my second question, ICE does allow for the case
>> where there is no candidate attribute, and from the receivers
>> perspective this would be such case, wouldn't it?
>
> Yes.
>
>> But, if there are
>> no candidate attributes, how does the receiver know that the sender
>> supports ICE?
>
> It won't. This is the point. In case (2), each side will conclude  
> that the other doesn't support ICE.
>
>
>> Is there an option tag, or someting? Or, is it assumed
>> that the other ICE related attributes (ice-pwd) are still present, to
>> indicate the support of ICE?
>
> candidate attributes are the indicator. There is no option tag.  
> There is no need.
>
>>> In case 1, with the current specification this will break badly.
>>> Because the m/c-line never appears as a candidate, the agents will
>>> never send media to it since it never validates. The way to fix
>>> this would be to change ice-09 to say that, if an agent doesn't see
>>> a cndidate for the m/c-line, it CAN send media to it without
>>> validating (kind of makes sense). Agents would also need to deal
>>> with cases where they get an updated offer and they can't find a
>>> matching candidate pair int he right state.
>> [CHH] Is there a reason why the m/c-lines couldn't be used for
>> validation - at least in the case when there is no matching candiate?
>
> Yes. There are actual use cases where an endpoint cannot mux STUN  
> and RTP on the same port, in which case you could elect never to  
> try and validate whats currently in use on the m/c-line.
>
> The other problem is that you need more than an IP/port to do the  
> stun validations. You need usernames, passwords, and several other  
> parameters. Several (like username/password) are difficult and  
> dangerous to try and derive algorithmically rather than signal.
>

Is it really that hard? I can think of ways to handle it. (E.g.,  
require endpoints
to always provide a password for the entire media-stream, and always  
provide
a "default" candidate id which is used if the m/c line does not match  
a candidate).
In some ways, this is similar to the way ICE-08 handles peer- 
reflexive candidates.

The only thing I am not complete sure of is: Is it worth it? But  
perhaps the goal is
to try to make ICE work in as many cases as possible, in which case  
the  answer
is probably "Yes".

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



From mmusic-bounces@ietf.org Mon Jun 26 15:53:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fux9G-0006Gw-4X; Mon, 26 Jun 2006 15:53:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fux9E-0006G8-UH
	for mmusic@ietf.org; Mon, 26 Jun 2006 15:53:28 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fux9D-00013D-LP
	for mmusic@ietf.org; Mon, 26 Jun 2006 15:53:28 -0400
Received: from rtp-core-2.cisco.com ([64.102.124.13])
	by rtp-iport-1.cisco.com with ESMTP; 26 Jun 2006 12:53:27 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.06,177,1149490800"; 
	d="scan'208"; a="30512726:sNHT23027416"
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 k5QJrRno004823; 
	Mon, 26 Jun 2006 15:53:27 -0400 (EDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Mon, 26 Jun 2006 15:53:27 -0400
Received: from [192.168.1.100] ([10.86.240.77]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 26 Jun 2006 15:53:26 -0400
Message-ID: <44A03B36.20808@cisco.com>
Date: Mon, 26 Jun 2006 15:53:26 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
Subject: Re: VS: [MMUSIC] ICE: Client supports, but network doesn't
References: <5EB80D22825EEE42872083AD5BFFB594017F1166@esealmw113.eemea.ericsson.se>
	<C2E6E64E-5AEB-4D18-9944-2FA9360DBD9D@magma.ca>
	<449C40CA.9030604@cisco.com>
	<5EB80D22825EEE42872083AD5BFFB594117CFE@esealmw113.eemea.ericsson.se>
	<449F37EF.8010407@cisco.com>
	<DFB3D7E3-AA91-4479-820D-0CF5BD975641@magma.ca>
In-Reply-To: <DFB3D7E3-AA91-4479-820D-0CF5BD975641@magma.ca>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Jun 2006 19:53:26.0719 (UTC)
	FILETIME=[308B74F0:01C6995A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: mmusic@ietf.org,
	"Christer Holmberg \(JO/LMF\)" <christer.holmberg@ericsson.com>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

inline.

Philip Matthews wrote:


>>> [CHH] Is there a reason why the m/c-lines couldn't be used for
>>> validation - at least in the case when there is no matching candiate?
>>
>>
>> Yes. There are actual use cases where an endpoint cannot mux STUN  and 
>> RTP on the same port, in which case you could elect never to  try and 
>> validate whats currently in use on the m/c-line.
>>
>> The other problem is that you need more than an IP/port to do the  
>> stun validations. You need usernames, passwords, and several other  
>> parameters. Several (like username/password) are difficult and  
>> dangerous to try and derive algorithmically rather than signal.
>>
> 
> Is it really that hard? I can think of ways to handle it. (E.g.,  
> require endpoints
> to always provide a password for the entire media-stream, and always  
> provide
> a "default" candidate id which is used if the m/c line does not match  a 
> candidate).
> In some ways, this is similar to the way ICE-08 handles peer- reflexive 
> candidates.
> 
> The only thing I am not complete sure of is: Is it worth it? But  
> perhaps the goal is
> to try to make ICE work in as many cases as possible, in which case  
> the  answer
> is probably "Yes".
> 

Generally, I agree with you. But this is a different case. This is the 
case where there is a b2bua that is stomping on the m/c-lines, because 
it wants to be in the way. I don't want to turn ICE into a protocol that 
purposefully bypasses service provider b2buas. If such a box gets in the 
way, ICE should fall back to normal usage without ICE. If the b2bua 
becomes ICE aware then the provider can do what it wants.

-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 Jun 26 17:19:07 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FuyU6-0006v7-Fc; Mon, 26 Jun 2006 17:19:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FuyU5-0006v2-HH
	for mmusic@ietf.org; Mon, 26 Jun 2006 17:19:05 -0400
Received: from mx2-1.spamtrap.magma.ca ([209.217.78.160])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FuyU4-0007xL-60
	for mmusic@ietf.org; Mon, 26 Jun 2006 17:19:05 -0400
Received: from mail3.magma.ca (mail3.internal.magma.ca [10.0.10.13])
	by mx2-1.spamtrap.magma.ca (8.13.1/8.13.1) with ESMTP id k5QLJ12s018924;
	Mon, 26 Jun 2006 17:19:01 -0400
Received: from [10.1.5.219] ([216.13.42.126]) (authenticated bits=0)
	by mail3.magma.ca (Magma's Mail Server) with ESMTP id k5QLIxNc019454
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT);
	Mon, 26 Jun 2006 17:19:00 -0400
In-Reply-To: <44A03B36.20808@cisco.com>
References: <5EB80D22825EEE42872083AD5BFFB594017F1166@esealmw113.eemea.ericsson.se>
	<C2E6E64E-5AEB-4D18-9944-2FA9360DBD9D@magma.ca>
	<449C40CA.9030604@cisco.com>
	<5EB80D22825EEE42872083AD5BFFB594117CFE@esealmw113.eemea.ericsson.se>
	<449F37EF.8010407@cisco.com>
	<DFB3D7E3-AA91-4479-820D-0CF5BD975641@magma.ca>
	<44A03B36.20808@cisco.com>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <99887A00-085E-40F0-858E-E2B0236F5A27@magma.ca>
Content-Transfer-Encoding: 7bit
From: Philip Matthews <philip_matthews@magma.ca>
Subject: Re: VS: [MMUSIC] ICE: Client supports, but network doesn't
Date: Mon, 26 Jun 2006 17:19:06 -0400
To: Jonathan Rosenberg <jdrosen@cisco.com>
X-Mailer: Apple Mail (2.746.2)
X-magma-MailScanner-Information: Magma Mailscanner Service
X-magma-MailScanner: Clean
X-Spam-Status: 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: mmusic@ietf.org,
	"Christer Holmberg \(JO/LMF\)" <christer.holmberg@ericsson.com>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

See below.

On 26-Jun-06, at 15:53 , Jonathan Rosenberg wrote:

> inline.
>
> Philip Matthews wrote:
>
>
>>>> [CHH] Is there a reason why the m/c-lines couldn't be used for
>>>> validation - at least in the case when there is no matching  
>>>> candiate?
>>>
>>>
>>> Yes. There are actual use cases where an endpoint cannot mux  
>>> STUN  and RTP on the same port, in which case you could elect  
>>> never to  try and validate whats currently in use on the m/c-line.
>>>
>>> The other problem is that you need more than an IP/port to do  
>>> the  stun validations. You need usernames, passwords, and several  
>>> other  parameters. Several (like username/password) are difficult  
>>> and  dangerous to try and derive algorithmically rather than signal.
>>>
>> Is it really that hard? I can think of ways to handle it. (E.g.,   
>> require endpoints
>> to always provide a password for the entire media-stream, and  
>> always  provide
>> a "default" candidate id which is used if the m/c line does not  
>> match  a candidate).
>> In some ways, this is similar to the way ICE-08 handles peer-  
>> reflexive candidates.
>> The only thing I am not complete sure of is: Is it worth it? But   
>> perhaps the goal is
>> to try to make ICE work in as many cases as possible, in which  
>> case  the  answer
>> is probably "Yes".
>
> Generally, I agree with you. But this is a different case. This is  
> the case where there is a b2bua that is stomping on the m/c-lines,  
> because it wants to be in the way. I don't want to turn ICE into a  
> protocol that purposefully bypasses service provider b2buas. If  
> such a box gets in the way, ICE should fall back to normal usage  
> without ICE. If the b2bua becomes ICE aware then the provider can  
> do what it wants.
>

Jonathan:
Are you saying that you want the media to always go via the B2BUA in  
this case (= the B2BUA acts as a form of relay server)?
Or am I misunderstanding your comment?

I guess my broader question is: Why is the box in the middle  
modifying the  m/c line?
I could postulate a number of reasons why (e.g. helping with NAT  
traversal, trying to impose policy, trying to provide some other  
service, etc).
Which ones do we think are valid and want to support?

- Philip


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



From mmusic-bounces@ietf.org Mon Jun 26 17:53:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fuz1m-0003DK-OR; Mon, 26 Jun 2006 17:53:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fuz1l-0003DE-3Y
	for mmusic@ietf.org; Mon, 26 Jun 2006 17:53:53 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fuz1j-0003Cs-Gy
	for mmusic@ietf.org; Mon, 26 Jun 2006 17:53:53 -0400
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-6.cisco.com with ESMTP; 26 Jun 2006 14:53:50 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id k5QLroe3009424; 
	Mon, 26 Jun 2006 14:53:50 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k5QLroCa029163;
	Mon, 26 Jun 2006 14:53:50 -0700 (PDT)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Mon, 26 Jun 2006 14:53:43 -0700
Received: from [10.21.81.24] ([10.21.81.24]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 26 Jun 2006 14:53:43 -0700
Message-ID: <44A05765.3000508@cisco.com>
Date: Mon, 26 Jun 2006 17:53:41 -0400
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Randell Jesup <rjesup@wgate.com>
References: <4499AB3D.8060103@cisco.com> <ybur71fizau.fsf@jesup.eng.wgate.com>
In-Reply-To: <ybur71fizau.fsf@jesup.eng.wgate.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Jun 2006 21:53:43.0543 (UTC)
	FILETIME=[FE1B6870:01C6996A]
DKIM-Signature: a=rsa-sha1; q=dns; l=7201; t=1151358830; x=1152222830;
	c=relaxed/simple; s=sjdkim7001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fandreas@cisco.com;
	z=From:Flemming=20Andreasen=20<fandreas@cisco.com>
	|Subject:Re=3A=20SDP=20Capability=20Negotiation=20to=20address=20multiple=20RTP=2
	0profiles=20and=0A=20other=20issues;
	X=v=3Dcisco.com=3B=20h=3DHP7AW2JPVSzKxKE/H2xTagEyD+c=3D;
	b=UJM5DQHjoKV7vOyoL44RugQfUgOx98b7jCUVUUOx61kVg+OAFOYGc4gOc66hs615JEGbK/kw
	mbTW0pYLQd3ISA3MK4o1XvS5mquaMnPBUhYrlVyakmERzfHbq7Dz8hq3;
Authentication-Results: sj-dkim-7.cisco.com; header.From=fandreas@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48
Cc: ietf-rtpsec <ietf-rtpsec@imc.org>, Doug Perham <dperham@wgate.com>,
	mmusic@ietf.org
Subject: [MMUSIC] Re: SDP Capability Negotiation to address multiple RTP
 profiles and other issues
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

Thanks for the feedback Randell

Some comments below....

Randell Jesup wrote:

>>I have submitted a draft on adding capability negotiation to SDP which you
>>can retrieve from (abstract below):
>>
>>http://www.ietf.org/internet-drafts/draft-andreasen-mmusic-sdp-capability-negotiation-00.txt
>>
>>The primary motivation for this is to address the proliferation of RTP
>>profiles and the associated problem of negotiating which of possibly
>>several supported RTP profiles to use for a given media stream.
>>    
>>
>...
>  
>
>>Feedback is hereby solicited. In particular, it would be very helpful if
>>people could take a look at the requirements and see if they agree with
>>them (too much, too little, anything wrong/missing, etc.) before we get
>>into detailed discussion around the proposed solution. Having said that,
>>all comments are welcome.
>>    
>>
>
>REQ-10: there are other ways to deal with the example issue, especially
>involving re-INVITE in SIP - though re-negotiation may not be possible in
>some uses of SDP.  You may want to mention here or better in the Existing
>Work section how re-INVITE/re-negotiation fit in (which applies to a lot of
>the requirements, not just this one).
>  
>
It's a band-aid, not a full solution since as soon as you issue an 
offer, you are supposed to be prepared to receive media encoded with any 
of the codecs offered. I can add some words to that effect.

>REQ-110: (ability to receive media immediately) and REQ-120 - see below.
>These two seem redundant.
>  
>
They describe two different things. REQ-110 talks about actual 
configurations, e.g. one or more codecs you are prepared to receive at 
this point in time. This is that we currently put in the "m=" line in an 
offer (if we are spec complicant at least). REQ-120 on the other hand 
talks about potential configurations, which would be alternatives we are 
not prepared to receive at this point in time. This could for example be 
things like RFC 3407 simple capability declarations. What REQ-120 adds 
on top of that is that you must be able to negotiate use of those 
potential configurations and be prepared to receive media accordingly 
once (but not before) you actually receive the answer.

>Overall, I find it interesting, if complex.  
>
Thanks. I'm certainly open to other suggestions. What seems most 
important at this point though is agreeing on the requirements. I 
personally think we need to look out for feature creep (don't want to 
replicate SDPng or H.245) so it will be a challenge to figure out where 
to draw the line. More discussion around requirements will be helpful here.

>There is a major issue (see
>below) to resolve.  The complexity may be such that getting interoperable
>implementations may be a challenge.  An effective test suite and set of
>examples will be critical.  
>
Good point. I'll make sure to add more examples.

>The problem is a very real one.
>
>It appears to not deal with two issues dealt with by the grouping spec,
>which are defining valid combinations of media lines, 
>
Right - there is currently no such requirement in the document, but if 
can of course be added if people believe it is important. Were you 
looking for just saying e.g. "can do audio and video", actual 
combinations of audio of video codecs, or something different ?

>and defining valid
>combinations of codecs (on one media line or between lines).  
>
You can define valid combinations of codecs within a media line with the 
current mechanism. REQ-10 probably needs to be  tighthened up to make it 
clear that allowable combinations within a media stream have to be 
supported as well. There is currently no similar requirement between 
media lines, but again, it can be added if people believe it is important.


>This would
>mean that those particular requirements would still need grouping or SDPng
>or ???.  Perhaps at least the first (valid combinations of media lines)
>can be worked into this approach?  
>
Certainly (again if the group is interested in doing so).

>As you mention, grouping (and even more
>so multipart-alternative) have significant compatibility issues.
>
>
>General issue with the approach:
>
>It's dependant on the offerer receiving the answer in order to decode the
>media.  For example, if the transport protocol can be RTP/AVP or RTP/SAVP
>(regardless of which is the "actual" offer and which is potential), how
>does the receiver process incoming media packets if it hasn't seen the
>answer?  
>
In general that is true if one of the potential configurations are 
accepted, however it is possible to use different transport addresses 
for each alternative (not that I recommend it). You could envision other 
ways of addressing this as well (all you need is to communicate the 
actual capability information back to the offerer's media part which is 
made somewhat easy by the use of scoped integers as references) .

>Especially if the packet types can't be intuited from something
>like size (an example would be SRTP with encryption but no auth tag).  In
>some cases this would cause static, could cause potential crashing or
>problematic actions.  So the answerer may not be able to send media until
>they see ACK (in SIP) if they accept a potential configuration.
>  
>
I'd rather say the offerer may not be able to process such media 
correctly until the answer is received.

>This can cause clipping - you pick up the phone and start talking, but if
>the answer is lost or delayed, or if the ACK is lost or delayed, your
>"hello?" might be lost.
>
>Now, this might be ok, though clipping is to be avoided where possible,
>since people assume through experience that media channels are open as soon
>as they answer.  Also, if the configuration accepted is the actual one,
>the answerer can send media immediately.
>
>  
>
Correct.


>Potential solutions:
>a) Use different transport addresses for incompatible media/protocols.
>   Could be problematic when combined with ICE/TURN/etc - more ports.
>   Could cause some combinatoric expansion (especially with ICE/TURN).
>  
>
Agreed.

>b) Use alternative payload types to distinguish incompatible media types
>   so that some level of decoding (or at least knowing to ignore packets) 
>   can be done before the answer arrives.  This might tell the offerer
>   enough to fully decode, though they still can't send until they get
>   the answer (which is normal).  It may not tell enough in all cases
>   without expansion, and perhaps there are backwards compatibility
>   issues.  Also, there may be issues with the number of payload types
>   listed (though perhaps the values could be inferred instead of
>   explicit) and how that affects the size of the offer.
>  
>
Right - this is another approach that may help in some cases. You could 
imagine ICE extensions, preconditions (sigh) and other potential 
solutions as well.

>Discussion of clipping, when and how media is sent, and how packet
>loss/delay affect this will be critical.
>
>  
>
Agreed.

Thanks for the comments.

-- Flemming

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



From mmusic-bounces@ietf.org Mon Jun 26 17:57:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fuz4s-000641-Qq; Mon, 26 Jun 2006 17:57:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fuz4r-00063w-1R
	for mmusic@ietf.org; Mon, 26 Jun 2006 17:57:05 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fuz4p-0003I3-OE
	for mmusic@ietf.org; Mon, 26 Jun 2006 17:57:05 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-5.cisco.com with ESMTP; 26 Jun 2006 14:57:02 -0700
X-IronPort-AV: i="4.06,178,1149490800"; 
	d="scan'208"; a="301282941:sNHT37930216"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id k5QLv3d7027515; 
	Mon, 26 Jun 2006 14:57:03 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k5QLv29s003179;
	Mon, 26 Jun 2006 14:57:02 -0700 (PDT)
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.211);
	Mon, 26 Jun 2006 14:56:56 -0700
Received: from [10.21.81.24] ([10.21.81.24]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 26 Jun 2006 14:56:54 -0700
Message-ID: <44A05824.3080500@cisco.com>
Date: Mon, 26 Jun 2006 17:56:52 -0400
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Randell Jesup <rjesup@wgate.com>
References: <449FBBF6.8040106@uni-ulm.de> <ybuirmohv0i.fsf@jesup.eng.wgate.com>
In-Reply-To: <ybuirmohv0i.fsf@jesup.eng.wgate.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Jun 2006 21:56:54.0645 (UTC)
	FILETIME=[70034250:01C6996B]
DKIM-Signature: a=rsa-sha1; q=dns; l=1297; t=1151359023; x=1152223023;
	c=relaxed/simple; s=sjdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fandreas@cisco.com;
	z=From:Flemming=20Andreasen=20<fandreas@cisco.com>
	|Subject:Re=3A=20SDP=20Capability=20Negotiation=20to=20address=20multiple=20RTP=2
	0profiles=20and=0A=20other=20issues;
	X=v=3Dcisco.com=3B=20h=3DHP7AW2JPVSzKxKE/H2xTagEyD+c=3D;
	b=YgWDctbUQS/rA/wrhHG9ZFlrYV6Bc6LhIiAJ5u+pVVnHckkxPtZB/vLUoLKAHZxufdoQgqhh
	NI931srugJ18R25aw5YnUdWRzslhI08LVmLIyv5y4Rit30HeHLRVejVn;
Authentication-Results: sj-dkim-2.cisco.com; header.From=fandreas@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: mmusic@ietf.org, Teodora Guenkova-Luy <teodora.guenkova-luy@uni-ulm.de>
Subject: [MMUSIC] Re: SDP Capability Negotiation to address multiple RTP
 profiles and other issues
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



Randell Jesup wrote:

>Teodora Guenkova-Luy <teodora.guenkova-luy@uni-ulm.de> writes:
>  
>
>>I have also a comment to REQ-110 and REQ-120.
>>Since the potential configurations are pre-conditions for choosing and
>>enforcing them as actual configurations, may be a better idea is to perform
>>a negotiation with potential configurations in two stages: First the
>>offerer and the anserer agree which potential configurations are applicable
>>and secondly which are the chosen configurations to become actual
>>(i.e. counter-offer and counter-answer). Solution for such behaviour can be
>>RFC 3312.
>>    
>>
>
>This sounds like a minimum 1.5-round-trip negotiation
>(offer/counter-offer/counter-answer).  That appears to violate REQ-100 (it
>must work within the offer-answer model, specifically it must do a
>negotiation within a single round-trip).  What you're proposing sounds more
>like preconditions (though I'm not 100% up on the details of how
>preconditions work).
>
>  
>
Right. Given the amount of negative feedback receved from implementers 
of preconditions, I don't think we can rely on that (which is not to say 
we can't define additional operations that can take advantage of such 
mechanisms and the extra half or full roundtrip).

-- Flemming




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



From mmusic-bounces@ietf.org Mon Jun 26 18:02:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FuzAV-0004GR-2s; Mon, 26 Jun 2006 18:02:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FuzAT-0004F6-68
	for mmusic@ietf.org; Mon, 26 Jun 2006 18:02:53 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FuzAQ-00048f-Em
	for mmusic@ietf.org; Mon, 26 Jun 2006 18:02:53 -0400
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-6.cisco.com with ESMTP; 26 Jun 2006 15:02:49 -0700
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id k5QM2nh9014980; 
	Mon, 26 Jun 2006 15:02:49 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id k5QM2fJ8006042;
	Mon, 26 Jun 2006 15:02:48 -0700 (PDT)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Mon, 26 Jun 2006 15:02:47 -0700
Received: from [10.21.81.24] ([10.21.81.24]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 26 Jun 2006 15:02:46 -0700
Message-ID: <44A05984.7010302@cisco.com>
Date: Mon, 26 Jun 2006 18:02:44 -0400
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Teodora Guenkova-Luy <teodora.guenkova-luy@uni-ulm.de>
References: <449FBBF6.8040106@uni-ulm.de> <ybuirmohv0i.fsf@jesup.eng.wgate.com>
	<449FF525.3090402@uni-ulm.de>
In-Reply-To: <449FF525.3090402@uni-ulm.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Jun 2006 22:02:46.0183 (UTC)
	FILETIME=[418BB370:01C6996C]
DKIM-Signature: a=rsa-sha1; q=dns; l=3653; t=1151359369; x=1152223369;
	c=relaxed/simple; s=sjdkim7001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fandreas@cisco.com;
	z=From:Flemming=20Andreasen=20<fandreas@cisco.com>
	|Subject:Re=3A=20SDP=20Capability=20Negotiation=20to=20address=20multiple=20RTP=2
	0profiles=20and=0A=20other=20issues;
	X=v=3Dcisco.com=3B=20h=3DHP7AW2JPVSzKxKE/H2xTagEyD+c=3D;
	b=Pd560JuWC7FTEc93kyGbu0SsugfVnUIa9KbBG+YP/CQM/SfAXg5CIBveN9JVjei6mV63iVFK
	UGAn21ZFGDzTPk7h41KDYBu9PQOuJBjJPCrMT8I/VZSfu/MZM+LgOiI5;
Authentication-Results: sj-dkim-7.cisco.com; header.From=fandreas@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: mmusic@ietf.org
Subject: [MMUSIC] Re: SDP Capability Negotiation to address multiple RTP
 profiles and other issues
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



Teodora Guenkova-Luy wrote:

> Randell Jesup wrote:
>
>>Teodora Guenkova-Luy <teodora.guenkova-luy@uni-ulm.de> writes:
>>  
>>
>>>I have also a comment to REQ-110 and REQ-120.
>>>Since the potential configurations are pre-conditions for choosing and
>>>enforcing them as actual configurations, may be a better idea is to perform
>>>a negotiation with potential configurations in two stages: First the
>>>offerer and the anserer agree which potential configurations are applicable
>>>and secondly which are the chosen configurations to become actual
>>>(i.e. counter-offer and counter-answer). Solution for such behaviour can be
>>>RFC 3312.
>>>    
>>>
>>
>>This sounds like a minimum 1.5-round-trip negotiation
>>(offer/counter-offer/counter-answer).  That appears to violate REQ-100 (it
>>must work within the offer-answer model, specifically it must do a
>>negotiation within a single round-trip).  What you're proposing sounds more
>>like preconditions (though I'm not 100% up on the details of how
>>preconditions work).
>>
>>  
>>
> Hi,
> If you look at REQ-100 the author seems also not to be sure if the 
> negotiation of potential configurations should be limited to O/A model 
> only. 

Correct, but I believe it is an absolute requirement that it does work 
within that model.

> IMHO, you don't need to negotiate potential configurations if you are 
> sure that the proposed actual configurations will work as they are. 
> Hence, you don't need preconditions for your session. However, if only 
> a limited amount of the actual configurations works, your session is 
> also limited, and it can be enhaced only through a re-negotiation, but 
> the re-negotiation is IMHO more expensive compared to the negotiation 
> of potential configurations as it takes place during the media session. 

Agreed - negotiation of the potential configurations should be an 
integral part of the initial negotation process and hence not require 
separate renegotation (we can more or less do that with existing 
mechanisms already, e.g. just include RFC 3407 capability information in 
both the offer and answer).

> If you are proposing potential configurations this means that you are 
> not sure what kind of answer you'll get and eventually the answerer 
> may enhance the proposal of the offerer with further potential 
> configurations in order to ease the decision of the offerer what 
> configurations to take for the session. Furthermore, the offerer may 
> propose potential configurations that might be too expensive for the 
> offerer (e.g. in terms of resources), so the offerer has to wait the 
> answer in oder to make its final decision. Consequently and due to 
> such uncertainties, only after exchanging potential configurations, 
> the offerer can decide which configurations can be taken as actual and 
> signal them to the answerer. This is no more O/A model, as the 
> proposals for potential configurations work as pre-conditions for the 
> success of the following session.

This sounds like more full fledged capability negotation ala SDPng and 
I'm not sure we want to take the proposal that far. We'll need to agree 
on the requirements first I guess.

-- Flemming

>-- 
>-----------------------------------------
>Teodora Guenkova-Luy
>
>Dept. Distributed Systems, University of Ulm, 
>Oberer Eselsberg, 89069 Ulm, Germany
>
>Tel.: +49 (0731) 502-4148 
>FAX: +49 (0731) 502-4142
>
>e-Mail: teodora.guenkova-luy@uni-ulm.de
>
>Home Page: http://www-vs.informatik.uni-ulm.de/dept/staff/guenkova/ 
>
>-----------------------------------------
>

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



From mmusic-bounces@ietf.org Mon Jun 26 19:02:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fv06W-0006eO-3W; Mon, 26 Jun 2006 19:02:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FuzuB-0004V2-Eh; Mon, 26 Jun 2006 18:50:07 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FuzuB-0007g1-CP; Mon, 26 Jun 2006 18:50:07 -0400
Received: from chsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.24.129]
	helo=willow.neustar.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1Fuzu6-0007nA-H7; Mon, 26 Jun 2006 18:50:07 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k5QMo2Rx004087
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 26 Jun 2006 22:50:02 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Fuzu6-000804-0I; Mon, 26 Jun 2006 18:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Fuzu6-000804-0I@stiedprstage1.ietf.org>
Date: Mon, 26 Jun 2006 18:50:02 -0400
X-Spam-Score: -5.9 (-----)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-media-loopback-03.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		: An Extension to the Session Description Protocol (SDP) for Media Loopback
	Author(s)	: K. Hedayat, et al.
	Filename	: draft-ietf-mmusic-media-loopback-03.txt
	Pages		: 17
	Date		: 2006-6-26
	
The wide deployment of Voice over IP (VoIP), Real-time Text and 
Video over IP services has introduced new challenges in managing 
and maintaining voice/real-time Text/video quality, reliability, 
and overall performance.  In particular, media delivery is an area 
that needs attention.  One method of meeting these challenges is 
monitoring the media delivery performance by looping media back to 
the transmitter.  This is typically referred to as "active 
monitoring" of services.   Media loopback is especially popular in 
ensuring the quality of transport to the edge of a given VoIP, 
Real-time Text or Video over IP service.  Today in networks that 
deliver real-time media, short of running 'ping' and 'traceroute' 
to the edge, service providers are left without the necessary tools 
to actively monitor, manage, and diagnose quality issues with their 
service.  The extension defined herein adds new SDP media 
attributes which enables establishment of media sessions where the 
media is looped back to the transmitter. Such media sessions will 
serve as monitoring and troubleshooting tools by providing the 
means for measurement of more advanced VoIP, Real-time Text and 
Video Over IP performance metrics.

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

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


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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-media-loopback-03.txt

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

Content-Type: text/plain
Content-ID: <2006-6-26164416.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 Tue Jun 27 02:36:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fv7Bu-0001Da-0l; Tue, 27 Jun 2006 02:36:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fv7Bs-0001DV-Hh
	for mmusic@ietf.org; Tue, 27 Jun 2006 02:36:52 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fv7Bp-0008KR-3i
	for mmusic@ietf.org; Tue, 27 Jun 2006 02:36:52 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] Usage of stream bandwidth attribute in SDP offer/answer
Date: Tue, 27 Jun 2006 09:36:44 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C03A3AE2C@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] Usage of stream bandwidth attribute in SDP offer/answer
Thread-Index: AcaI5G03zN9xsRXfRJOEKNA5/iL5UgQz2fJA
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>,
	<mmusic@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
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,
Noted that for the audio you specify b=3DAS:16000. I am not sure if it =
is
possible since PCMU/8000 is sampled at 8Khz and each sample is 8 bit
making it 64000 b/sec rate.=20
Roni Even

> -----Original Message-----
> From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> Sent: Tuesday, June 06, 2006 12:10 AM
> To: mmusic@ietf.org
> Subject: [MMUSIC] Usage of stream bandwidth attribute in SDP
offer/answer
>=20
> Hello MMUSIC folks,
>=20
> I am trying to build an SDP offer/answer for a point to point call
using
> RFC3264 SDP offer/answer model. The offerer (alice) would like to
convey
> that it would like to send and receive audio at 16000bps, send video
at
> 64000 bps and receive video at 128000bps. The answerer(bob) would like
> to receive video at 32000bps and send video at 64000bps. Below is the
> SDP exchange between alice and bob.
>=20
>=20
> [SDP offer]
>       v=3D0
>       o=3Dalice 2890844526 2890844526 IN IP4 host.sd.example.com
>       s=3D
>       c=3DIN IP4 host.sd.example.com
>       t=3D0 0
>       m=3Daudio 49170 RTP/AVP 0
>       a=3Drtpmap:0 PCMU/8000
>       b=3DAS:16000
>       m=3Dvideo 51372 RTP/AVP 31
>       a=3Drtpmap:31 H261/90000
>       b=3DAS:64000
>       a=3Dsendonly
>       m=3Dvideo 51374 RTP/AVP 31
>       a=3Drtpmap:31 H261/90000
>       b=3DAS:128000
>       a=3Drecvonly
>=20
> [SDP answer]
>       v=3D0
>       o=3D bob 2808844564 2808844564 IN IP4 host.la.example.com
>       s=3D
>       c=3DIN IP4 host.la.example.com
>       t=3D0 0
>       m=3Daudio 52124 RTP/AVP 0
>       a=3Drtpmap:0 PCMU/8000
>       b=3DAS:16000
>       m=3Dvideo 53212 RTP/AVP 31
>       a=3Drtpmap:31 H261/90000
>       b=3DAS:32000
>       a=3Drecvonly
>       m=3Dvideo 54416 RTP/AVP 31
>       a=3Drtpmap:31 H261/90000
>       b=3DAS:64000
>       a=3Dsendonly
>=20
>=20
> Is the "b=3DAS" parameter allowed to be used this way to communicate
that
> the offerer would like to send/receive the stream with the specified
> bandwidth?
>=20
> RFC3264 (Sec 5.1, Page 7) states "If the bandwidth parameter is
present
> for a stream, it indicates the desired bandwidth that the offerer
would
> like to receive". From the RFC text, it is not clear whether the
> bandwidth parameter can also be used to indicate the desired bandwidth
> the offerer would like transmit (atleast when a=3Dsendonly)
>=20
> Cheers,
> Hari D
>=20
> _______________________________________________
> 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 Jun 27 03:17:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fv7pB-0007dT-DJ; Tue, 27 Jun 2006 03:17:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fv7p9-0007dO-JL
	for mmusic@ietf.org; Tue, 27 Jun 2006 03:17:27 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fv7p8-0004Hc-5a
	for mmusic@ietf.org; Tue, 27 Jun 2006 03:17:27 -0400
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	98A0E520001; Tue, 27 Jun 2006 09:17:25 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.173]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 27 Jun 2006 09:17:25 +0200
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 27 Jun 2006 09:17:25 +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: VS: [MMUSIC] ICE: Client supports, but network doesn't
Date: Tue, 27 Jun 2006 09:17:24 +0200
Message-ID: <5EB80D22825EEE42872083AD5BFFB594017F119D@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: VS: [MMUSIC] ICE: Client supports, but network doesn't
Thread-Index: AcaZZicMF7LeBq3jTsiRBuSc4cRseQAUuCgg
From: "Christer Holmberg \(JO/LMF\)" <christer.holmberg@ericsson.com>
To: "Philip Matthews" <philip_matthews@magma.ca>,
	"Jonathan Rosenberg" <jdrosen@cisco.com>
X-OriginalArrivalTime: 27 Jun 2006 07:17:25.0214 (UTC)
	FILETIME=[BD64D7E0:01C699B9]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
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

>Jonathan:
>Are you saying that you want the media to always go via the B2BUA in
this case (=3D the B2BUA acts as a form of relay server)?
>Or am I misunderstanding your comment?
>
>I guess my broader question is: Why is the box in the middle modifying
the  m/c line?
>I could postulate a number of reasons why (e.g. helping with NAT
traversal, trying to impose policy, trying to provide some other
service, etc).
>Which ones do we think are valid and want to support?

For the scenario we're discussing, I am not sure we need to care about
WHY the c/m lines are modified. I think it's enough that we assume that
media sent towards the c/m address will reach the other user (otherwise
there is something wrong in the network).

Regards,

Christer



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



From mmusic-bounces@ietf.org Tue Jun 27 06:05:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FvARx-000715-OV; Tue, 27 Jun 2006 06:05:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FvARw-000710-6M
	for mmusic@ietf.org; Tue, 27 Jun 2006 06:05:40 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FvARu-0004BN-Di
	for mmusic@ietf.org; Tue, 27 Jun 2006 06:05:40 -0400
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	A6A604F006A
	for <mmusic@ietf.org>; Tue, 27 Jun 2006 12:05:37 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 27 Jun 2006 12:05:37 +0200
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 27 Jun 2006 12:05:37 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 27 Jun 2006 12:05:36 +0200
Message-ID: <5EB80D22825EEE42872083AD5BFFB594017F11A8@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: ICE and private addresses
Thread-Index: AcaZ0TyDsz1HgOdBRP+cxvWmaO+KEg==
From: "Christer Holmberg \(JO/LMF\)" <christer.holmberg@ericsson.com>
To: <mmusic@ietf.org>
X-OriginalArrivalTime: 27 Jun 2006 10:05:37.0254 (UTC)
	FILETIME=[3CB7F060:01C699D1]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Subject: [MMUSIC] ICE and private addresses
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="===============0020521703=="
Errors-To: mmusic-bounces@ietf.org


This is a multi-part message in MIME format.

--===============0020521703==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C699D1.3C755089"


This is a multi-part message in MIME format.

------_=_NextPart_001_01C699D1.3C755089
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Hi,

Assume client A and B are located in two separate private networks (with
a "public" network in between), which happen to have an overlapping
address space.

Now, when client A generates the candidate attributes the Local Candiate
is going to contain the local client A IP address/port.

When client B receives the candidate attributes is will initiate the
connectivity checks, as defined in ICE.

Now, due to the overlapping address space, the client A Local Candidate
address may actually point also to a third client (C), located in the
same network as client B, so the connectivity check messages will be
sent towards client C instead of client A.

I guess there, at least in theory, could also be a scenario where the
c/m line also contains the client A Local Candidate address, again also
pointing towards client C.

I am not sure whether the B2BUA issues discussed in another thread
(where the B2BUA modifies the c/m lines) have any impacts on this
scenario. Need to think about that...

Regards,

Christer


------_=_NextPart_001_01C699D1.3C755089
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.7638.1">
<TITLE>ICE and private addresses</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 client A and B are located in =
two separate private networks (with a &quot;public&quot; network in =
between), which happen to have an overlapping address space.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Now, when client A generates the =
candidate attributes the Local Candiate is going to contain the local =
client A IP address/port.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">When client B receives the candidate =
attributes is will initiate the connectivity checks, as defined in =
ICE.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Now, due to the overlapping address =
space, the client A Local Candidate address may actually point also to a =
third client (C), located in the same network as client B, so the =
connectivity check messages will be sent towards client C instead of =
client A.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I guess there, at least in theory, =
could also be a scenario where the c/m line also contains the client A =
Local Candidate address, again also pointing towards client =
C.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I am not sure whether the B2BUA issues =
discussed in another thread (where the B2BUA modifies the c/m lines) =
have any impacts on this scenario. Need to think about =
that...</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_01C699D1.3C755089--


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

--===============0020521703==--




From mmusic-bounces@ietf.org Tue Jun 27 07:56:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FvCBI-0006bz-3O; Tue, 27 Jun 2006 07:56:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FvCBH-0006bu-00
	for mmusic@ietf.org; Tue, 27 Jun 2006 07:56:35 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FvCBE-00071T-Ee
	for mmusic@ietf.org; Tue, 27 Jun 2006 07:56:34 -0400
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	9D459520001; Tue, 27 Jun 2006 13:56:31 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 27 Jun 2006 13:56:31 +0200
Received: from [147.214.30.119] ([147.214.30.119]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 27 Jun 2006 13:56:30 +0200
Message-ID: <44A11CEE.5080007@ericsson.com>
Date: Tue, 27 Jun 2006 13:56:30 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: "Even, Roni" <roni.even@polycom.co.il>
Subject: Re: [MMUSIC] Usage of stream bandwidth attribute in SDP offer/answer
References: <144ED8561CE90C41A3E5908EDECE315C03A3AE2C@IsrExch01.israel.polycom.com>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C03A3AE2C@IsrExch01.israel.polycom.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Jun 2006 11:56:30.0392 (UTC)
	FILETIME=[BA4C3B80:01C699E0]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
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

Even, Roni wrote:
> Hi,
> Noted that for the audio you specify b=AS:16000. I am not sure if it is
> possible since PCMU/8000 is sampled at 8Khz and each sample is 8 bit
> making it 64000 b/sec rate. 
> Roni Even

Actually it is possible. As AS is maxium session bandwidth, the offer 
simply tells the answerer that it is ready to receive 16 mbps, i.e. up 
to 250 simultaneous audio streams. :-)

However I guess that was not intended. Please be aware the AS is in kbps 
while TIAS, RS and RR are in bps.

Cheers

Magnus Westerlund

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

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



From mmusic-bounces@ietf.org Tue Jun 27 08:27:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FvCfH-0002Og-9Q; Tue, 27 Jun 2006 08:27:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FvCfG-0002Ob-10
	for mmusic@ietf.org; Tue, 27 Jun 2006 08:27:34 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FvCfD-0003TK-P2
	for mmusic@ietf.org; Tue, 27 Jun 2006 08:27:34 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12])
	by rtp-iport-2.cisco.com with ESMTP; 27 Jun 2006 08:27:31 -0400
X-IronPort-AV: i="4.06,179,1149480000"; 
	d="scan'208"; a="91093601:sNHT30533868"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k5RCRUYL028065; 
	Tue, 27 Jun 2006 08:27:30 -0400 (EDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Tue, 27 Jun 2006 08:27:30 -0400
Received: from [161.44.34.166] ([161.44.34.166]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 27 Jun 2006 08:27:30 -0400
Message-ID: <44A12432.10008@cisco.com>
Date: Tue, 27 Jun 2006 08:27:30 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Even, Roni" <roni.even@polycom.co.il>
References: <144ED8561CE90C41A3E5908EDECE315C037AEBB7@IsrExch01.israel.polycom.com>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C037AEBB7@IsrExch01.israel.polycom.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Jun 2006 12:27:30.0357 (UTC)
	FILETIME=[0EEC5E50:01C699E5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: IETF MMUSIC WG <mmusic@ietf.org>, Colin Perkins <csp@csperkins.org>
Subject: [MMUSIC] Re: Review of draft-ietf-mmusic-ice-tcp-00
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

Fixed.

Thanks,
Jonathan R.

Even, Roni wrote:

> Hi, Two more editorial comments:
> 
> 1. In section 9 second paragraph "successul" should be "successful"
> 
> 2. In section 7 " since it is the STUN requests identify the
> candidate pairs." I think that a "that" is missing after the "STUN
> requests"
> 
> Roni Even
> 

-- 
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 Jun 27 11:23:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FvFPc-0004OV-Vu; Tue, 27 Jun 2006 11:23:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FvFPb-0004LT-1J
	for mmusic@ietf.org; Tue, 27 Jun 2006 11:23:35 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FvDVj-0006q0-7s
	for mmusic@ietf.org; Tue, 27 Jun 2006 09:21:47 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FvDHZ-0005nx-HY
	for mmusic@ietf.org; Tue, 27 Jun 2006 09:07:11 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12])
	by rtp-iport-1.cisco.com with ESMTP; 27 Jun 2006 06:07:07 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.06,180,1149490800"; 
	d="scan'208"; a="30561246:sNHT23594128"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k5RD76YL006553; 
	Tue, 27 Jun 2006 09:07:06 -0400 (EDT)
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.211);
	Tue, 27 Jun 2006 09:07:06 -0400
Received: from [161.44.34.166] ([161.44.34.166]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 27 Jun 2006 09:07:06 -0400
Message-ID: <44A12D7A.1010203@cisco.com>
Date: Tue, 27 Jun 2006 09:07:06 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francois Audet <audet@nortel.com>
References: <1ECE0EB50388174790F9694F77522CCF08B20E1B@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF08B20E1B@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Jun 2006 13:07:06.0317 (UTC)
	FILETIME=[971B17D0:01C699EA]
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: IETF MMUSIC WG <mmusic@ietf.org>, Colin Perkins <csp@csperkins.org>
Subject: [MMUSIC] Re: Review of draft-ietf-mmusic-ice-tcp-00
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.

Francois Audet wrote:

> Jonathan,
> 
> As promised in Dallas, I have done a review of draft-ietf-mmusic-ice-tcp-00.
> 
> Most of my comments are editorial in nature, except perhaps a minor comment
> on section 3.
> 
> 
> Section 1
> 
> - 2nd paragraph, last line: change "communicatoins" to "communications".

fixed.


> 
> Section 2
> 
> - It would be much clearer if a reference to RFC 4145 be placed at the
>   very begining of this section (after the first paragraph). It is
>   very difficult to follow starting with the 2nd paragraph unless the
>   concepts described in RFC 4145 on active/passive/actpass are understood.

done.

> 
> - 4th paragraph, 4th line. Change "by the agent" to "by the remote agent" or
>   "by the other agent" to make it clear it is the other side you are talking
>   about.

changed to peer.

> 
> - 6th paragraph (top of p. 5). It is not clear what "specifications are 
>   being developped". Perhaps an informative reference to the draft is in 
>   order (http://www.ietf.org/internet-drafts/draft-ietf-behave-tcp-00.txt).

added.

> 
> Section 3
> 
> - Top of page 7. The sentence "Only in cases ... be omitted" probably should
>   be removed as it seems very restrictive. I understand what you are trying
>   to do, i.e., get people to implement ICE-TCP in UAs, which I am OK with. 
>   What I think is important is that UAs have the ability to have ICE-TCP
>   turned on or off depending on network preferences. For example, an 
>   enterprise may decide that ICE-TCP inside the network is unacceptable
>   and should be turned off: this could be communicated to the client through
>   Config-framework (so that it would work when the client is "nomad"). Or
>   maybe there is two configuration profiles for the client (one for inside
>   the enterprise, one for outside). In any case, I think the explanation, or
>   at least the last sentence, is overly restrictive and should be 
>   adjusted.

Changed to:

In
environments where mobility and user control are possible, a
multiplicity of techniques is essential for reliability.

> 
> Section 5
> 
> - First paragraph, first line. Change "procedurs" to "procedures".
> 
> - Second paragraph. Change "set to 9" to "set to 9 (i.e., Discard)" for 
>   clarity.

fixed both.

> 
> Section 6
> 
> - First paragraph, first line. Change "procedurs" to "procedures".

fixed.

> 
> Section 7
> 
> - First word of page 12. Change "Even Ta" to "Every Ta".
> 

fixed.

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 Tue Jun 27 11:43:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FvFj9-0000M1-SA; Tue, 27 Jun 2006 11:43:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FvFj9-0000Lq-Dx
	for mmusic@ietf.org; Tue, 27 Jun 2006 11:43:47 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FvE0H-0008PB-JG
	for mmusic@ietf.org; Tue, 27 Jun 2006 09:53:21 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FvDl8-0006KU-Th
	for mmusic@ietf.org; Tue, 27 Jun 2006 09:37:46 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-4.cisco.com with ESMTP; 27 Jun 2006 06:37:42 -0700
X-IronPort-AV: i="4.06,180,1149490800"; 
	d="scan'208"; a="1833356410:sNHT34958640"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id k5RDbgT3019263; 
	Tue, 27 Jun 2006 06:37:42 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k5RDbfCU000658;
	Tue, 27 Jun 2006 06:37:42 -0700 (PDT)
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.211);
	Tue, 27 Jun 2006 09:37:41 -0400
Received: from [161.44.34.166] ([161.44.34.166]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 27 Jun 2006 09:37:41 -0400
Message-ID: <44A134A3.4050507@cisco.com>
Date: Tue, 27 Jun 2006 09:37:39 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tim Moore <timmoore@exchange.microsoft.com>
Subject: Re: [MMUSIC] ice-tcp review
References: <4039D552ADAB094BB1EA670F3E96214E02089946@df-foxhound-msg.exchange.corp.microsoft.com>
In-Reply-To: <4039D552ADAB094BB1EA670F3E96214E02089946@df-foxhound-msg.exchange.corp.microsoft.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 27 Jun 2006 13:37:41.0217 (UTC)
	FILETIME=[DCCA9D10:01C699EE]
DKIM-Signature: a=rsa-sha1; q=dns; l=2293; t=1151415462; x=1152279462;
	c=relaxed/simple; s=sjdkim4001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:Re=3A=20[MMUSIC]=20ice-tcp=20review;
	X=v=3Dcisco.com=3B=20h=3DuZFompSzLwHb8EJHCeBD8qkab9U=3D;
	b=mL+gcGT6oLgd5V2MGPo2CulPKd4Rq/zmdERNuuoDEJ2EiCrhDtkKA8I8rb+zZvxDATwY7H7A
	yYxdEEaUt8g2mKH1BEp3shBM/1g3K2zgnZsaf275BDxkSaE3Db86NCza;
Authentication-Results: sj-dkim-4.cisco.com; header.From=jdrosen@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

thanks for the comments, Tim. Responses inline.

Tim Moore wrote:

>  
> 
> 11.  Binding Keepalives
> 
> This section contains
> 
> the definition of framing over tcp
> 
> how to demultiplex rtp/stun.
> 
>  
> 
> The framing is tcp specific.
> 
> The demultiplexing is generic to udp and tcp but I can’t find this 
> description in ice. Shouldn’t the demultiplex description be in the ice 
> draft

It is in there, but in an odd place (section 7.8 of ICE-08). I added the 
same demux rule to the binding keepalive section of ice-09 as well.

> 
> Note: This comment affects the ice draft as well if accepted
> 
>  
> 
> 5.  Encoding
> 
>    “Encoding of the m/c-line, however, requires special considerations
> 
>    for TCP.  If there is no active candidate, the media session MUST
> 
>    include an a=holdconn attribute as defined in RFC 4145 [3].”
> 
>  
> 
> I believe you mean if the m/c line is TCP and it is not active then 
> a=holdconn must be included but the wording isn’t very clear

reworded to say:

<t> Encoding of the m/c-line, however,
requires special considerations for TCP. If the m/c-line is TCP, and
there is no operating candidate, the a=holdconn attribute as defined
in RFC 4145 <xref target="RFC4145"/> MUST be included. This has the
effect of suspending opening of the


> 
>  
> 
> 7.  Performing the Connectivity Checks
> 
> I believe Erkki’s comment on MAPPED-ADDRESS should be XOR-MAPPED-ADDRESS 
> applies.

fixed.

> 
>  
> 
>  
> 
> The following are editing nits
> 
>  
> 
> 2 occurrences of “acpass” which should be actpass
> 
> 2 occurrences of “procedurs” which should be procedures
> 
fixed

>  
> 
> 7.  Performing the Connectivity Checks
> 
>   “Even Ta seconds, the agent performs a new connection attempt.  This”
> 
> Should be
> 
>   “Every Ta seconds, the agent performs a new connection attempt.  This”

fixed.

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 Tue Jun 27 13:46:07 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FvHdW-0001ma-Vt; Tue, 27 Jun 2006 13:46:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FvHdV-0001mV-Qf
	for mmusic@ietf.org; Tue, 27 Jun 2006 13:46:05 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FvHdU-0005X1-CE
	for mmusic@ietf.org; Tue, 27 Jun 2006 13:46:05 -0400
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:60283
	helo=[192.168.0.3])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1FvHdT-0001UI-7o
	for mmusic@ietf.org; Tue, 27 Jun 2006 18:46:03 +0100
Mime-Version: 1.0 (Apple Message framework v750)
In-Reply-To: <E1Fuzu6-000804-0I@stiedprstage1.ietf.org>
References: <E1Fuzu6-000804-0I@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A316FF33-FD43-42F9-B110-E944A4AE32A4@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] I-D ACTION:draft-ietf-mmusic-media-loopback-03.txt 
Date: Tue, 27 Jun 2006 18:45:58 +0100
To: IETF MMUSIC WG <mmusic@ietf.org>
X-Mailer: Apple Mail (2.750)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
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

On 26 Jun 2006, at 23:50, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts  
> directories.
> This draft is a work item of the Multiparty Multimedia Session  
> Control Working Group of the IETF.
>
> 	Title		: An Extension to the Session Description Protocol (SDP)  
> for Media Loopback
> 	Author(s)	: K. Hedayat, et al.
> 	Filename	: draft-ietf-mmusic-media-loopback-03.txt
> 	Pages		: 17
> 	Date		: 2006-6-26
...
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-media- 
> loopback-03.txt

I've reviewed this draft, and have some serious concerns about the  
rtp-pkt-loopback mode. Since RTP sequence numbers and timestamps are  
not regenerated, it is not possible to determine if loss/jitter  
occurs on the forward or reverse path, and difficult to generate  
appropriate RTCP reports. It would seem to me more appropriate to  
define an encapsulating payload format, and use that to loop back the  
media packets. The encapsulated loopback packets would have correct  
RTP sequence numbers and timestamps, representing the time at which  
they were looped back, so allowing the monitor to distinguish forward  
and reverse path loss. In addition, RTCP could be generated in the  
normal manner for the looped back stream, other RTP mechanisms (e.g.  
security, FEC, etc.) could be employed to protect the loopback  
stream, and the result would be fully compliant with the relevant RTP  
standards.

Section 6 recommends the loopback stream ignore congestion control,  
which I don't believe is acceptable in an standards track document.  
Use of an encapsulating payload format for looped back packets would  
allow thinning of the loopback stream as a means of congestion  
control, and allow the monitor to determine that thinning occurred on  
the reverse path (since the thinned stream would have missing RTP  
sequence numbers, separate to the sequence numbers of the  
encapsulated packets).

Finally, the ABNF in section 5.1 is unusual since rtp-start-loopback  
is included in both the loopback-type-choice and in loopback-type  
lines. This allows "a=loopback: rtp-start-loopback rtp-start-loopback  
rtp-start-loopback" which is probably not what was intended.

Colin


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



From mmusic-bounces@ietf.org Wed Jun 28 19:35:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fvj0J-0000ea-C4; Wed, 28 Jun 2006 18:59:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FvirO-0006EZ-TE; Wed, 28 Jun 2006 18:50:14 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FvirO-0000CX-Qe; Wed, 28 Jun 2006 18:50:14 -0400
Received: from chsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.24.129]
	helo=willow.neustar.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1FvirC-0000Fm-Md; Wed, 28 Jun 2006 18:50:14 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k5SMo29F006168
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Wed, 28 Jun 2006 22:50:02 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FvirC-0004ne-7N; Wed, 28 Jun 2006 18:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1FvirC-0004ne-7N@stiedprstage1.ietf.org>
Date: Wed, 28 Jun 2006 18:50:02 -0400
X-Spam-Score: -5.9 (-----)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-securityprecondition-02.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		: Security Preconditions for Session Description Protocol (SDP) Media Streams
	Author(s)	: F. Andreasen, D. Wing
	Filename	: draft-ietf-mmusic-securityprecondition-02.txt
	Pages		: 15
	Date		: 2006-6-28
	
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.

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

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


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

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


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

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

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

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

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

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

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

Content-Type: text/plain
Content-ID: <2006-6-28165000.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 Thu Jun 29 04:26:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fvrql-0005MD-5q; Thu, 29 Jun 2006 04:26:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fvrqj-0005M4-Nq; Thu, 29 Jun 2006 04:26:09 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FvqoD-0001fy-On; Thu, 29 Jun 2006 03:19:29 -0400
Received: from chsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.24.129]
	helo=willow.neustar.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1FvqLi-0002I4-Ij; Thu, 29 Jun 2006 02:50:07 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k5T6o29F017692
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Thu, 29 Jun 2006 06:50:02 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FvqLi-00007i-3h; Thu, 29 Jun 2006 02:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1FvqLi-00007i-3h@stiedprstage1.ietf.org>
Date: Thu, 29 Jun 2006 02:50:02 -0400
X-Spam-Score: -5.9 (-----)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-fec-grouping-05.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		: Forward Error Correction Grouping Semantics in
                          Session Description Protocol
	Author(s)	: A. Li
	Filename	: draft-ietf-mmusic-fec-grouping-05.txt
	Pages		: 7
	Date		: 2006-6-28
	
This document defines the semantics that allows for grouping of
   forward error correction (FEC) streams with the protected payload
   streams in Session Description Protocol (SDP). The semantics defined
   in this document is to be used with Grouping of Media Lines in the
   Session Description Protocol (RFC 3388) to group together "m" lines
   in the same session.

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

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


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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-fec-grouping-05.txt

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

Content-Type: text/plain
Content-ID: <2006-6-28214414.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 Thu Jun 29 05:42:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fvt2X-0005b8-0s; Thu, 29 Jun 2006 05:42:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fvt2V-0005YP-42
	for mmusic@ietf.org; Thu, 29 Jun 2006 05:42:23 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fvs8m-00077A-Fu
	for mmusic@ietf.org; Thu, 29 Jun 2006 04:44:48 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Fvs5I-0005mD-U2
	for mmusic@ietf.org; Thu, 29 Jun 2006 04:41:17 -0400
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:63667
	helo=[192.168.0.3])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1Fvs5F-0005mu-Pz; Thu, 29 Jun 2006 09:41:09 +0100
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <53B69FC6-4439-42E3-BA97-4ECF6F07F5CC@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Thu, 29 Jun 2006 09:41:05 +0100
To: IETF MMUSIC WG <mmusic@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: =?ISO-8859-1?Q?J=F6rg_Ott?= <jo@netlab.hut.fi>
Subject: [MMUSIC] =?iso-8859-1?q?Draft_agenda_for_Montr=E9al_meeting?=
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,

Enclosed is a draft agenda for MMUSIC at the 66th IETF meeting.  
Please send any comments, corrections or additions to the chairs. I  
note that our main focus at this meeting has to be to complete the  
work on ICE, and that later agenda items may be compressed if that  
discussion takes longer than anticipated.

Colin




Multiparty Multimedia Session Control (MMUSIC) Working Group
============================================================

CHAIRS:  Joerg Ott <jo@acm.org>
          Colin Perkins <csp@csperkins.org>

AGENDA

Wednesday, 12 July 2006  at 09:00-11:30
---------------------------------------
09:00   Introduction and progress report                    (Chairs, 10)

09:10   ICE                                              (Rosenberg, 40)
         draft-ietf-mmusic-ice-09.txt
         draft-ietf-mmusic-ice-tcp-01.txt
         draft-matthews-mmusic-ice-eliminating-duplicates-00.txt

09:50   SDP Capability Negotiation                       (Andreasen, 30)
         draft-andreasen-mmusic-sdp-capability-negotiation-00.txt

10:20   Signaling of media decoding dependency in SDP      (Schierl, 10)
         draft-schierl-mmusic-layered-codec-00

10:30   Security Descriptions Extension for IPsec            (Saito, 10)
         draft-saito-mmusic-ipsec-negotiation-req-02.txt
         draft-saito-mmusic-sdes-ipsec-00

10:40   An Evaluation of SIP for Streaming Media         (Montpetit, 10)
         draft-whitehead-sip-for-streaming-media-01

10:50   SDP Offer/Answer Mechanism to Enable File Transfer  (Garcia, 10)
         draft-garcia-mmusic-file-transfer-mech-00.txt

11:00   Multiple aggregated control URIs for RTSP        (Johansson, 10)
         draft-einarsson-mmusic-rtsp-macuri-00

11:10   Controlling FLUTE sessions with RTSP             (Johansson, 10)
         draft-lohmar-mmusic-rtsp-flute-00

11:20   Bitrate header in RTSP                                 (Wei, 10)
         draft-wei-mmusic-rtsp-bitrate-header-01

11:30   End


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



From mmusic-bounces@ietf.org Thu Jun 29 11:03:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fvy3I-0002DS-Uo; Thu, 29 Jun 2006 11:03:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fvy3H-0002DN-Kx
	for mmusic@ietf.org; Thu, 29 Jun 2006 11:03:31 -0400
Received: from mx4-1.spamtrap.magma.ca ([209.217.78.176])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fvy3F-0007BK-8M
	for mmusic@ietf.org; Thu, 29 Jun 2006 11:03:31 -0400
Received: from mail4.magma.ca (mail4.internal.magma.ca [10.0.10.14])
	by mx4-1.spamtrap.magma.ca (8.13.1/8.13.1) with ESMTP id k5TF3Qfc026789;
	Thu, 29 Jun 2006 11:03:26 -0400
Received: from [10.1.5.219] ([216.13.42.126]) (authenticated bits=0)
	by mail4.magma.ca (Magma's Mail Server) with ESMTP id k5TF3OO3021272
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT);
	Thu, 29 Jun 2006 11:03:26 -0400
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <0F5A84F9-8047-48D0-9CE2-E2A5A5A111CB@magma.ca>
Content-Transfer-Encoding: 7bit
From: Philip Matthews <philip_matthews@magma.ca>
Date: Thu, 29 Jun 2006 11:03:24 -0400
To: Jonathan Rosenberg <jdrosen@cisco.com>, IETF MMUSIC WG <mmusic@ietf.org>
X-Mailer: Apple Mail (2.746.2)
X-magma-MailScanner-Information: Magma Mailscanner Service
X-magma-MailScanner: Clean
X-Spam-Status: 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: 
Subject: [MMUSIC] Problem with Pairing Peer-Reflexive Candidates in ICE
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

Currently, the ICE specification states that a peer-reflexive candidate
is ONLY paired with the remote candidate that was involved in
discovering it. However, Eric and I have discovered an example where
this results in an optimal communication path NOT being discovered
(and where the optimal path WOULD be discovered if peer-reflexive
candidates were paired with other candidates).

We briefly summarize the example below. Full details can be found at
   www.magma.ca/~philip_matthews/Peer-Reflexive-Pairing-Problem.pdf

Consider the following network. Here the candidates are indicated with
stars (*) and labeled L1, L2, etc.

         +-------------+                  +------------+
         | STUN Server |                  | STUN/TURN  |
         |      S      |              R5  * Server ST  |
         +-------------+                  +------------+

              L2                               R4
           +----*-----------------------------*------+
           |               NAT  N                    |
           +-----------------------------------------+

                                             +------------+
                                             | STUN/TURN  |
                                         R3  * Server STR |
                                             +------------+

          L1R3                            R1L1R3     R2
+------*-+                                   +*----*--+
| NAT NL |                                   | NAT NR |
+--------+                                   +--------+

    /\                                            /\
   /  * L1                                       /  * R1
  /  L \                                        /  R \
+------+                                      +------+


Both L and R get internet access from a provider that NATs its
entire network using NAT N. NAT N is almost BEHAVE-compliant,
but does not support hairpinning.
L is a home phone whose owner has purchased a simple NAT which
happens to be BEHAVE-compliant. L came pre-configured to use
STUN server S.
R is a corporate phone. R is behind a symmetric NAT NR
(= address-and-port-dependent mapping, address-and-port-dependent
filtering). R is configured to use two STUN/TURN servers:
server ST has a public IP address, while server STR is located
inside the ISP's network.

During the initial gathering of candidates phase, L learns only
L1 and L2. It does NOT learn a server-reflexive candidate on NL
because L is not configured to use a STUN server that could give it
that information.

But, as the connectivity checks proceed, L and R learn a peer-reflexive
candidate for L on NL. This peer-reflexive candidate is learned while
checking candidate pair (L1, R3), and thus the rules
of [ICE-08] say that the peer-reflexive candidate is named L1R3 and
it is paired only with R3, which is the candidate that helped find it.

HOWEVER, if the rules of ICE were changed to pair this new candidate
with R1 as well, then the connectivity checks for (L1R3, R1) would find
a second peer-reflexive candidate, which would be named R1L1R3.
This would then give rise to the pair (L1R3, R1L1R3), which is the
optimal path.



The obvious fix for this problem is to pair native peer-reflexive  
candidates
with *ALL* remote candidates, not just the one that was involved in
discovering it. However, this fix has the side effect of almost doubling
the number of candidate pairs (from 10 to 18) -- a huge increase with
corresponding increase in messaging. It may be that it is sufficient
to pair the peer-reflexive candidate with just certain other candidates.
This needs more investigation.

- Philip


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



From mmusic-bounces@ietf.org Thu Jun 29 13:21:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fw0CZ-0007F7-B6; Thu, 29 Jun 2006 13:21:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fw0CX-0007F2-NE
	for mmusic@ietf.org; Thu, 29 Jun 2006 13:21:13 -0400
Received: from mx4-1.spamtrap.magma.ca ([209.217.78.176])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fw0CW-0002oi-Cm
	for mmusic@ietf.org; Thu, 29 Jun 2006 13:21:13 -0400
Received: from mail1.magma.ca (mail1.internal.magma.ca [10.0.10.11])
	by mx4-1.spamtrap.magma.ca (8.13.1/8.13.1) with ESMTP id k5THL872017625;
	Thu, 29 Jun 2006 13:21:08 -0400
Received: from [10.1.5.219] ([216.13.42.126]) (authenticated bits=0)
	by mail1.magma.ca (Magma's Mail Server) with ESMTP id k5THL7Kc005414
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT);
	Thu, 29 Jun 2006 13:21:08 -0400
In-Reply-To: <5EB80D22825EEE42872083AD5BFFB594017F119D@esealmw113.eemea.ericsson.se>
References: <5EB80D22825EEE42872083AD5BFFB594017F119D@esealmw113.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <DCC98A97-9578-449D-9260-7968168B3AA0@magma.ca>
Content-Transfer-Encoding: 7bit
From: Philip Matthews <philip_matthews@magma.ca>
Subject: Re: VS: [MMUSIC] ICE: Client supports, but network doesn't
Date: Thu, 29 Jun 2006 13:21:10 -0400
To: Christer Holmberg ((JO/LMF)) <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.746.2)
X-magma-MailScanner-Information: Magma Mailscanner Service
X-magma-MailScanner: Clean
X-Spam-Status: 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
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


On 27-Jun-06, at 03:17 , Christer Holmberg ((JO/LMF)) wrote:

>
> Hi,
>
>> Jonathan:
>> Are you saying that you want the media to always go via the B2BUA in
> this case (= the B2BUA acts as a form of relay server)?
>> Or am I misunderstanding your comment?
>>
>> I guess my broader question is: Why is the box in the middle  
>> modifying
> the  m/c line?
>> I could postulate a number of reasons why (e.g. helping with NAT
> traversal, trying to impose policy, trying to provide some other
> service, etc).
>> Which ones do we think are valid and want to support?
>
> For the scenario we're discussing, I am not sure we need to care about
> WHY the c/m lines are modified. I think it's enough that we assume  
> that
> media sent towards the c/m address will reach the other user  
> (otherwise
> there is something wrong in the network).
>

Sorry to be slow in replying.
If I understand this, then what you are saying is the following:

    If endpoint X receives an offer or answer containing one or more
    a-candidate lines, but where the address and port in the m/c line
    is NOT one of the candidates listed, then the endpoint should simply
    assume that sending media to the address in the m/c line will work.

Question:
Should endpoint X perform connectivity checks, or should
it just assume that the m/c line represents the most desirable path?

- Philip



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



From mmusic-bounces@ietf.org Thu Jun 29 15:58:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fw2eg-0007zo-VR; Thu, 29 Jun 2006 15:58:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fw2Wc-0004mS-2N; Thu, 29 Jun 2006 15:50:06 -0400
Received: from willow.neustar.com ([209.173.53.84])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fw2Wa-0001Z5-5g; Thu, 29 Jun 2006 15:50:06 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k5TJo39F012809
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Thu, 29 Jun 2006 19:50:03 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Fw2WZ-0003Vh-IV; Thu, 29 Jun 2006 15:50:03 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Fw2WZ-0003Vh-IV@stiedprstage1.ietf.org>
Date: Thu, 29 Jun 2006 15:50:03 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-rfc2326bis-13.txt 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
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		: Real Time Streaming Protocol 2.0 (RTSP)
	Author(s)	: H. Schulzrinne, et al.
	Filename	: draft-ietf-mmusic-rfc2326bis-13.txt
	Pages		: 191
	Date		: 2006-6-29
	
This memorandum defines RTSP version 2.0 which is a revision of the
Proposed Standard RTSP version 1.0 which is defined in RFC 2326.
The Real Time Streaming Protocol, or RTSP, is an application-level
protocol for control over the delivery of data with real-time
properties. RTSP provides an extensible framework to enable
controlled, on-demand delivery of real-time data, such as audio and
video. Sources of data can include both live data feeds and stored
clips. This protocol is intended to control multiple data delivery
sessions, provide a means for choosing delivery channels such as UDP,
multicast UDP and TCP, and provide a means for choosing delivery
mechanisms based upon RTP (RFC 3550).

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

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


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

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


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

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

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

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

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

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

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

Content-Type: text/plain
Content-ID: <2006-6-29135315.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 Thu Jun 29 16:14:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fw2cW-0005fn-Lz; Thu, 29 Jun 2006 15:56:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fw2Wa-0004lS-HU; Thu, 29 Jun 2006 15:50:04 -0400
Received: from willow.neustar.com ([209.173.53.84])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fw2WZ-0001Yk-8a; Thu, 29 Jun 2006 15:50:04 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k5TJo29F012781
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Thu, 29 Jun 2006 19:50:03 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Fw2WY-0003Us-Pa; Thu, 29 Jun 2006 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Fw2WY-0003Us-Pa@stiedprstage1.ietf.org>
Date: Thu, 29 Jun 2006 15:50:02 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-ice-tcp-01.txt 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
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		: TCP Candidates with Interactive Connectivity Establishment (ICE)
	Author(s)	: J. Rosenberg
	Filename	: draft-ietf-mmusic-ice-tcp-01.txt
	Pages		: 20
	Date		: 2006-6-29
	
Interactive Connectivity Establishment (ICE) defines a mechanism for
NAT traversal for multimedia communication protocols based on the
offer/answer model of session negotiation.  ICE works by providing a
set of candidate transport addresses for each media stream, which are
then validated with peer-to-peer connectivity checks based on Simple
Traversal of UDP over NAT (STUN).  ICE provides a general framework
for describing alternates, but only defines UDP-based transport
protocols.  This specification extends ICE to TCP-based media,
including the ability to offer a mix of TCP and UDP-based candidates
for a single stream.

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

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


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

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


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

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

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

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

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

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

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

Content-Type: text/plain
Content-ID: <2006-6-29120423.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 Thu Jun 29 18:08:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fw4gh-0008KL-5U; Thu, 29 Jun 2006 18:08:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fw4ga-0008Ao-KC; Thu, 29 Jun 2006 18:08:32 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fw3F8-0007Cp-BV; Thu, 29 Jun 2006 16:36:06 -0400
Received: from cypress.neustar.com ([209.173.57.84])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1Fw2lf-00030T-0I; Thu, 29 Jun 2006 16:05:43 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by cypress.neustar.com (8.12.8/8.12.8) with ESMTP id k5TJo2jx010177
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Thu, 29 Jun 2006 19:50:03 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Fw2WY-0003Up-Oq; Thu, 29 Jun 2006 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Fw2WY-0003Up-Oq@stiedprstage1.ietf.org>
Date: Thu, 29 Jun 2006 15:50:02 -0400
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-ice-09.txt 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
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 Methodology for Network Address Translator (NAT) Traversal for Offer/Answer Protocols
	Author(s)	: J. Rosenberg
	Filename	: draft-ietf-mmusic-ice-09.txt
	Pages		: 109
	Date		: 2006-6-29
	
This document describes a protocol for Network Address Translator
   (NAT) traversal for multimedia session signaling protocols based on
   the offer/answer model, such as the Session Initiation Protocol
   (SIP).  This protocol is called Interactive Connectivity
   Establishment (ICE).  ICE makes use of the Simple Traversal of UDP
   through NAT (STUN), applying its binding discovery, connectivity
   check and relay usages.

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

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


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

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


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

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

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

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

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

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

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

Content-Type: text/plain
Content-ID: <2006-6-29120232.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 Fri Jun 30 03:31:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FwDTO-0001hj-Vm; Fri, 30 Jun 2006 03:31:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FwDTM-0001he-QZ
	for mmusic@ietf.org; Fri, 30 Jun 2006 03:31:28 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FwDTI-00016e-8R
	for mmusic@ietf.org; Fri, 30 Jun 2006 03:31:28 -0400
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	ADD604F0049; Fri, 30 Jun 2006 09:31:23 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.173]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 30 Jun 2006 09:30:40 +0200
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 30 Jun 2006 09:30:40 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: VS: [MMUSIC] ICE: Client supports, but network doesn't
Date: Fri, 30 Jun 2006 09:30:39 +0200
Message-ID: <5EB80D22825EEE42872083AD5BFFB594017F1224@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: VS: [MMUSIC] ICE: Client supports, but network doesn't
Thread-Index: AcaboGwMz0V0iv9PTuO4GqfMbm4KAAAdU6LA
From: "Christer Holmberg \(JO/LMF\)" <christer.holmberg@ericsson.com>
To: "Philip Matthews" <philip_matthews@magma.ca>
X-OriginalArrivalTime: 30 Jun 2006 07:30:40.0367 (UTC)
	FILETIME=[1694CFF0:01C69C17]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
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

>>>Jonathan:
>>>Are you saying that you want the media to always go via the B2BUA in
>>>this case (=3D the B2BUA acts as a form of relay server)?
>>>Or am I misunderstanding your comment?
>>>
>>>I guess my broader question is: Why is the box in the middle=20
>>>modifying the  m/c line?
>>>I could postulate a number of reasons why (e.g. helping with NAT
>>>traversal, trying to impose policy, trying to provide some other=20
>>>service, etc).
>>>Which ones do we think are valid and want to support?
>>
>>For the scenario we're discussing, I am not sure we need to care about

>>WHY the c/m lines are modified. I think it's enough that we assume=20
>>that media sent towards the c/m address will reach the other user=20
>>(otherwise there is something wrong in the network).
>
>
>Sorry to be slow in replying.
>If I understand this, then what you are saying is the following:
>
>    If endpoint X receives an offer or answer containing one or more
>    a-candidate lines, but where the address and port in the m/c line
>    is NOT one of the candidates listed, then the endpoint should
simply
>    assume that sending media to the address in the m/c line will work.

What I am saying is that when a client receives a c/m line (even if it
has been modified by a B2BUA or not) it can generally be assumed that
media sent towards that address will reach the remote user. That has
nothing to do with ICE.

But, the question is how a client supporting ICE should interpret this.

>Question:
>Should endpoint X perform connectivity checks, or should it just assume
that the m/c line represents the most desirable path?

That's the question :)

One proposal was that the client should perform connectivity check also
on the c/m line, but I think Jonathan in one e-mail said that won't
work.


Regards,

Christer



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



From mmusic-bounces@ietf.org Fri Jun 30 17:41:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FwQjz-0005Yo-UG; Fri, 30 Jun 2006 17:41:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FwQjy-0005Y9-IR
	for mmusic@ietf.org; Fri, 30 Jun 2006 17:41:30 -0400
Received: from mx5-3.spamtrap.magma.ca ([209.217.78.138])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FwQjy-0001mH-59
	for mmusic@ietf.org; Fri, 30 Jun 2006 17:41:30 -0400
Received: from mail2.magma.ca (mail2.internal.magma.ca [10.0.10.12])
	by mx5-3.spamtrap.magma.ca (8.13.1/8.13.1) with ESMTP id k5ULfR4G026542;
	Fri, 30 Jun 2006 17:41:27 -0400
Received: from [10.1.5.219] ([216.13.42.126]) (authenticated bits=0)
	by mail2.magma.ca (Magma's Mail Server) with ESMTP id k5ULfQFs011899
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
	Fri, 30 Jun 2006 17:41:27 -0400
In-Reply-To: <5EB80D22825EEE42872083AD5BFFB594017F11A8@esealmw113.eemea.ericsson.se>
References: <5EB80D22825EEE42872083AD5BFFB594017F11A8@esealmw113.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v746.2)
Message-Id: <B1C7F266-F473-49B5-9424-3BB1A2EAC1B7@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
Subject: Re: [MMUSIC] ICE and private addresses
Date: Fri, 30 Jun 2006 17:41:21 -0400
To: Christer Holmberg ((JO/LMF)) <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.746.2)
X-magma-MailScanner-Information: Magma Mailscanner Service
X-magma-MailScanner: Clean
X-Spam-Status: 
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
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="===============1571346731=="
Errors-To: mmusic-bounces@ietf.org


--===============1571346731==
Content-Type: multipart/alternative; boundary=Apple-Mail-3--549693612


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


On 27-Jun-06, at 06:05 , Christer Holmberg ((JO/LMF)) wrote:

>
> Hi,
>
> Assume client A and B are located in two separate private networks  
> (with a "public" network in between), which happen to have an  
> overlapping address space.
>
> Now, when client A generates the candidate attributes the Local  
> Candiate is going to contain the local client A IP address/port.
>
> When client B receives the candidate attributes is will initiate  
> the connectivity checks, as defined in ICE.
>
> Now, due to the overlapping address space, the client A Local  
> Candidate address may actually point also to a third client (C),  
> located in the same network as client B, so the connectivity check  
> messages will be sent towards client C instead of client A.
This is correct. Binding Requests sent by B to A's local candidate  
will actually be delivered to C.
This is a known problem with the "UDP hole punching" technique (used  
by ICE and others).
The ICE spec discusses this situation. There are two cases of interest:
a) If C does not support ICE, then C just has to deal with  
unsolicited packets arriving on random ports.
b) If C does support ICE, then the 24 bits of randomness in the  
candidate id is intended to ensure that C can distinguish these  
packets from other Binding Request which is IS expecting.
> I guess there, at least in theory, could also be a scenario where  
> the c/m line also contains the client A Local Candidate address,  
> again also pointing towards client C.
Yes, this would happen if the A considered its local candidate to be  
the most likely to work. In this case, A would put the local  
candidate into the c/m lines.
The comments above about C still apply.
> I am not sure whether the B2BUA issues discussed in another thread  
> (where the B2BUA modifies the c/m lines) have any impacts on this  
> scenario. Need to think about that...
This is why it is important to assign a candidate id to the new  
transport address (= the new value in the c/m lines). In my last  
posting on that other thread, I had suggested including a "default"  
candidate id to use ("default" is not really the right term -- this  
candidate id would be used if and only if the c/m lines got modified).

- Philip



--Apple-Mail-3--549693612
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; "><BR><DIV><DIV>On 27-Jun-06, at =
06:05 , Christer Holmberg ((JO/LMF)) wrote:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE type=3D"cite"> =
<BR><P><FONT size=3D"2" face=3D"Arial">Hi,</FONT> </P><P><FONT size=3D"2" =
face=3D"Arial">Assume client A and B are located in two separate private =
networks (with a "public" network in between), which happen to have an =
overlapping address space.</FONT></P><P><FONT size=3D"2" =
face=3D"Arial">Now, when client A generates the candidate attributes the =
Local Candiate is going to contain the local client A IP =
address/port.</FONT></P><P><FONT size=3D"2" face=3D"Arial">When client B =
receives the candidate attributes is will initiate the connectivity =
checks, as defined in ICE.</FONT> </P><P><FONT size=3D"2" =
face=3D"Arial">Now, due to the overlapping address space, the client A =
Local Candidate address may actually point also to a third client (C), =
located in the same network as client B, so the connectivity check =
messages will be sent towards client C instead of client =
A.</FONT></P></BLOCKQUOTE>This is correct. Binding Requests sent by B to =
A's local candidate will actually be delivered to C.</DIV><DIV>This is a =
known problem with the "UDP hole punching" technique (used by ICE and =
others).</DIV><DIV>The ICE spec discusses this situation. There are two =
cases of interest:</DIV><DIV>a) If C does not support ICE, then C just =
has to deal with unsolicited packets arriving on random =
ports.</DIV><DIV>b) If C does support ICE, then the 24 bits of =
randomness in the candidate id is intended to ensure that C can =
distinguish these packets from=A0other Binding Request which is IS =
expecting.<BR><BLOCKQUOTE type=3D"cite"><P><FONT size=3D"2" =
face=3D"Arial">I guess there, at least in theory, could also be a =
scenario where the c/m line also contains the client A Local Candidate =
address, again also pointing towards client =
C.</FONT></P></BLOCKQUOTE>Yes, this would happen if the A considered its =
local candidate to be the most likely to work.=A0In this case, A would =
put the local candidate into the c/m lines.</DIV><DIV>The comments above =
about C still apply.<BR><BLOCKQUOTE type=3D"cite"><P><FONT size=3D"2" =
face=3D"Arial">I am not sure whether the B2BUA issues discussed in =
another thread (where the B2BUA modifies the c/m lines) have any impacts =
on this scenario. Need to think about =
that...</FONT></P></BLOCKQUOTE><DIV>This is why it is important to =
assign a candidate id to the new transport address (=3D the new value in =
the c/m lines). In my last posting on that other thread, I had suggested =
including a "default" candidate id to use ("default" is not really the =
right term -- this candidate id would be used if and only if the c/m =
lines got modified).</DIV><BR></DIV><DIV>- Philip</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV></BODY></HTML>=

--Apple-Mail-3--549693612--


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

--===============1571346731==--




From mmusic-bounces@ietf.org Fri Jun 30 18:09:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FwRB9-0005qZ-J5; Fri, 30 Jun 2006 18:09:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FwRB7-0005qU-IN
	for mmusic@ietf.org; Fri, 30 Jun 2006 18:09:33 -0400
Received: from mx1-5.spamtrap.magma.ca ([209.217.78.156]
	helo=mx1-4.spamtrap.magma.ca)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FwRB6-0003FO-7Y
	for mmusic@ietf.org; Fri, 30 Jun 2006 18:09:33 -0400
Received: from mail1.magma.ca (mail1.internal.magma.ca [10.0.10.11])
	by mx1-4.spamtrap.magma.ca (8.13.1/8.13.1) with ESMTP id k5UK7KtW008577;
	Fri, 30 Jun 2006 16:07:20 -0400
Received: from [10.1.5.219] ([216.13.42.126]) (authenticated bits=0)
	by mail1.magma.ca (Magma's Mail Server) with ESMTP id k5UK7IoU027840
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT);
	Fri, 30 Jun 2006 16:07:19 -0400
In-Reply-To: <5EB80D22825EEE42872083AD5BFFB594017F1224@esealmw113.eemea.ericsson.se>
References: <5EB80D22825EEE42872083AD5BFFB594017F1224@esealmw113.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <9D9F5C79-A2B2-4245-85C3-20CEE430E735@magma.ca>
Content-Transfer-Encoding: 7bit
From: Philip Matthews <philip_matthews@magma.ca>
Subject: Re: VS: [MMUSIC] ICE: Client supports, but network doesn't
Date: Fri, 30 Jun 2006 16:07:15 -0400
To: Christer Holmberg ((JO/LMF)) <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.746.2)
X-magma-MailScanner-Information: Magma Mailscanner Service
X-magma-MailScanner: Clean
X-Spam-Status: 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
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


On 30-Jun-06, at 03:30 , Christer Holmberg ((JO/LMF)) wrote:
>
> Hi,
>
>>>> Jonathan:
>>>> Are you saying that you want the media to always go via the  
>>>> B2BUA in
>>>> this case (= the B2BUA acts as a form of relay server)?
>>>> Or am I misunderstanding your comment?
>>>>
>>>> I guess my broader question is: Why is the box in the middle
>>>> modifying the  m/c line?
>>>> I could postulate a number of reasons why (e.g. helping with NAT
>>>> traversal, trying to impose policy, trying to provide some other
>>>> service, etc).
>>>> Which ones do we think are valid and want to support?
>>>
>>> For the scenario we're discussing, I am not sure we need to care  
>>> about
>
>>> WHY the c/m lines are modified. I think it's enough that we assume
>>> that media sent towards the c/m address will reach the other user
>>> (otherwise there is something wrong in the network).
>>
>>
>> Sorry to be slow in replying.
>> If I understand this, then what you are saying is the following:
>>
>>    If endpoint X receives an offer or answer containing one or more
>>    a-candidate lines, but where the address and port in the m/c line
>>    is NOT one of the candidates listed, then the endpoint should
> simply
>>    assume that sending media to the address in the m/c line will  
>> work.
>
> What I am saying is that when a client receives a c/m line (even if it
> has been modified by a B2BUA or not) it can generally be assumed that
> media sent towards that address will reach the remote user. That has
> nothing to do with ICE.
>
> But, the question is how a client supporting ICE should interpret  
> this.
>
>> Question:
>> Should endpoint X perform connectivity checks, or should it just  
>> assume
> that the m/c line represents the most desirable path?
>
> That's the question :)
>
> One proposal was that the client should perform connectivity check  
> also
> on the c/m line, but I think Jonathan in one e-mail said that won't
> work.
>


My colleague Eric Cooper and I thought a bit about this and came up  
with the following.

Why is the box in the middle  changing the m/c lines?
In our opinion, either:
1a)  It is trying to help with NAT traversal, OR
1b)  It is trying to force the packets to flow through it.

Also, the box is either:
2a) not ICE aware, OR
2b) is ICE aware.

Consider first the combination of (1a) and (2a) -- for example,
a box trying to help with NAT traversal that is not ICE aware.
In this case, the modified m/c line provides an alternative transport  
address.
This address may work, or it may not, depending on the network  
situation.
So it seems best if ICE consider this another candidate  and try to  
validate it.
To do this, each endpoint could, for example, include "default"  
candidate ids and passwords
in the offer or  answer that would be used by the remote end if the m/ 
c line gets changed.

Now consider the  combination (1a) and (2b) -- a box trying to help with
NAT traversal that is ICE aware. Here the solution of the previous  
paragraph still
works, and Eric and I could not think of anything better that an ICE- 
aware box could do.

Next, consider the combination (1b) and (2b) - an ICE-aware box that  
is trying to
force the media to flow through it.  In this case, the box can simply  
delete all the ICE-related
lines from the SDP, and the remote end will fall back to non-ICE  
behavior,
which will cause all traffic to flow through the box.

Finally, consider the combination (1b) and (2a) - a non-ICE aware box  
that is trying
to force media to flow through it. In this case ... well ... the  
endpoints, not realizing that
the box wants to be in the media path, will try other paths. If one  
of these succeeds,
then the box will be bypassed. Otherwise, if only the modified m/c  
transport address works,
then the media will flow through the box.  If this is not the desired  
behavior, well,
just upgrade the box to an ICE-aware version!


- Philip


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



